-
-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cisco fabric interconnect 6332 doesn't return vlans #419
Comments
most likely an issue with the device firmware for that particular hardware model, even snmpwalk doesn't return usefull info: old:
new:
|
newer nx-os versions seem to have had several fixes in this area. putting this on hold until i have time to upgrade the ucs stuff. |
newer os versions have not fixed this. while a fabric interconnect 6332 is a nexus 9332pq in disguise hardware-wise, that's not the case for the os. after checking the ucs specific mibs i haven't found a way to access this info. (cisco ucs mibs: netdisco/netdisco-mibs#218 ) related: #520 vlan id 16777216 seems to come from the 802.1ad addendum to 802.1q, for which we don't yet have support iirc. |
we have 2 cisco blade chassis setups. cisco blades & chassis are managed by fabric inconnects. we are upgrading our systems from 6248up to 6332 fabric interconnects. 1 datacenter has been upgraded, the second one will follow soon.
we run the same software version on both datacenters: 4.04i (on both 6248up & 6332)
the second datacenter will be upgraded in 10 days, so troubleshooting time is limited.
Expected Behavior
return all configured vlans
Current Behavior
returns only a few vlans (and 1 invalid).
Possible Solution
Steps to Reproduce (for bugs)
Context
upgraded cisco blade chassis from 6248up fabric interconnects with iom 2208xp to 6332 with iom 2304. this was an online upgrade (replace passive, failover, replace old active).
since these devices manage a lot of counters we have the following in our settings so they don't time out:
Your Device
old: 6248up (not upgraded)
new: 6332 (upgraded)
the systems are clustered.
i might have mixed active & passive nodes in the following output but that doesn't make a difference, both nodes return the same info (correct for the old ones, incorrect for the new ones)
output of device_vlan table included.
old
new
Your Environment
The text was updated successfully, but these errors were encountered: