Guest

Preview Tool

Cisco Bug: CSCvu64522 - Enhancement for snmp context mapping with MST instance in N9k

Last Modified

Jun 16, 2020

Products (1)

  • Cisco Nexus 9000 Series Switches

Known Affected Releases

7.0(3)IFE7(2.41) 9.3(3)III9(0.38) 9.3(4.173) 9.3(4.174)

Description (partial)

Symptom:
Enhancement for snmp context mapping with MST instance in N9k.

Currently, snmp can retrieve TCN counter/values for MST-02 instance only by default. This is due top fact vlan 1 is part of MST-02. If we need to retrieve all MST instance TCN counter value, need to context vlan- instance number part of MST instance. Thus, need lot change to alter monitoring tool configuration and if vlan- instance moves from one MST instance to other, value returned would be for new MST instance TCN. Henceforth, snmp polling with vlan indexing is not at all a reliable method for TCN counter data collection for MST instances.

Need to add MST instance number as snmp context  so that snmp polling with MST instance number as indexing can retrieve TCN counter value for specific MST instance instead of indexing with  vlan associated with MST instance.

Conditions:
Enhancement for snmp context mapping with MST instance in N9k.

Currently, snmp can retrieve TCN counter/values for MST-02 instance only by default. This is due top fact vlan 1 is part of MST-02. If we need to retrieve all MST instance TCN counter value, need to context vlan- instance number part of MST instance. Thus, need lot change to alter monitoring tool configuration and if vlan- instance moves from one MST instance to other, value returned would be for new MST instance TCN. Henceforth, snmp polling with vlan indexing is not at all a reliable method for TCN counter data collection for MST instances.

Need to add MST instance number as snmp context  so that snmp polling with MST instance number as indexing can retrieve TCN counter value for specific MST instance instead of indexing with  vlan associated with MST instance.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.