cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1759
Views
0
Helpful
2
Replies

CISCO-STACKWISE-MIB Output Unexpected Behavior

jtrohm
Level 1
Level 1

Has anyone noticed weird behavior on the 3850s with the CISCO-STACKWISE-MIB? In particular, I'm trying to monitor for individual device down scenarios and find that, in some cases, when a stack member drops out, the MIB simply fails to report the stack member as existing rather than showing it as missing.

 

I believe this to be a bug, but before I go down that road, I want to confirm this isn't expected behavior for some reason I don't understand.

 

I can consistently reproduce this problem by reloading a single member.

 

When it is up I see the following in the CLI and SNMP respectively:

 

                                             H/W   Current
Switch#   Role    Mac Address     Priority Version  State
------------------------------------------------------------
*1       Active   c4b9.cd4b.ac00     1      V02     Ready
 2       Member   c4b9.cd95.1280     1      V02     Ready
SNMPv2-SMI::enterprises.9.9.500.1.2.1.1.6.1000 = INTEGER: 4
SNMPv2-SMI::enterprises.9.9.500.1.2.1.1.6.2000 = INTEGER: 4

However, if I reboot switch 2, I would expect to see it in a state of 1,2,8,9, or 11 depending on where it is in the reboot cycle. Instead, it just disappears from SNMP as shown below:

                                             H/W   Current
Switch#   Role    Mac Address     Priority Version  State
------------------------------------------------------------
*1       Active   c4b9.cd4b.ac00     1      V02     Ready
 2       Member   0000.0000.0000     0      0       Removed
SNMPv2-SMI::enterprises.9.9.500.1.2.1.1.6.1000 = INTEGER: 4

I have previously been able to see devices in a 9 (provisioned) state in SNMP when the stack physically rebooted but one member failed to come up, so the behavior isn't 100% consistent across outage types.

 

All of my testing devices are WS-C3850-12X48U running 03.07.4E code 

1 Accepted Solution

Accepted Solutions

After digging a little more, this is a known-bug CSCuu18093 that does not currently have a fix or workaround. 

 

Bug Finder Link

View solution in original post

2 Replies 2

jtrohm
Level 1
Level 1

Additional info:

 

The command I'm using to test the MIB is:

snmpwalk -v2c -c <COMMUNITY> <IP_ADDRESS> 1.3.6.1.4.1.9.9.500.1.2.1.1.6

The expected output when I reboot stack member 2 is:

SNMPv2-SMI::enterprises.9.9.500.1.2.1.1.6.1000 = INTEGER: 4
SNMPv2-SMI::enterprises.9.9.500.1.2.1.1.6.2000 = INTEGER: 11

.

I have confirmed that rebooting stack member 1 will produce similar output, meaning that unit 1 (index 1000) simply is missing from the table.

After digging a little more, this is a known-bug CSCuu18093 that does not currently have a fix or workaround. 

 

Bug Finder Link

Review Cisco Networking for a $25 gift card