MIB for determining SecureStack switch stack attributes

  • 0
  • 1
  • Article
  • Updated 5 years ago
  • (Edited)
Article ID: 7483 

Products
SecureStack C3
SecureStack C2
SecureStack B3
SecureStack B2
SecureStack A2 

Goals
MIB for monitoring SecureStack switch stack unit status. 
MIB for determining serial number.
MIB for determining firmware version. 

Symptoms 
Entity MIB 

Solution 
In terms of snapshot SNMP monitoring of stack member status, there is no MIB location which is less than cryptic for this purpose. However, entPhysicalTable (within the entityMIB) is at least workable, while serving the multiple purposes of also being a source of the serial numbers, firmware versions, and other data for each of the stacked switches. 

To demonstrate this, here is a view of a sample SecureStack C2 three-stack:
 C2(ro)->show switch
Management Preconfig Plugged-in Switch Code
Switch Status Model ID Model ID Status Version
------ ------------ ----------- ----------- --------------------- --------------
1 Mgmt Switch C2H124-48P C2H124-48P OK 05.02.01.0006
2 Stack Member C2G170-24 C2G170-24 OK 05.02.01.0006
3 Stack Member C2K122-24 C2K122-24 OK 05.02.01.0006
C2(ro)->show version

Copyright (c) 2007 by Enterasys Networks, Inc.

Model Serial # Versions
-------------- ----------------- -------------------

C2H124-48P 06491507905B Hw:BCM5665 REV 18
Bp:01.00.46
Fw:05.02.01.0006
BuFw:05.01.03.0007
PoE:500_3

C2G170-24 07440918905F Hw:BCM5695 REV 17
Bp:01.00.40
Fw:05.02.01.0006
BuFw:05.01.03.0007

C2K122-24 041800339041 Hw:BCM5695 REV 17
Bp:01.00.40
Fw:05.02.01.0006
BuFw:05.01.03.0007

C2(ro)->

A SNMP query of the entityMIB branch renders entries for miscellaneous stack components, including each port. Scan for eachentPhysicalClass entry which has a value of "module (9)", then add 1 to the index and review the contents of the various fields outlined below. In this example, entPhysicalClass indexes 10, 77, and 106 contain the trigger value; and indexes 11, 78, and 107 contain the target information for this example three-stack. 

The following layout takes liberties with the MIB order, for the purpose of best presenting related MIB information:
               entityMIB=1.3.6.1.2.1.47
entityMIBObjects=1.3.6.1.2.1.47.1
entityPhysical=1.3.6.1.2.1.47.1.1
entPhysicalTable=1.3.6.1.2.1.47.1.1.1
entPhysicalEntry=1.3.6.1.2.1.47.1.1.1.1

entPhysicalIndex=1.3.6.1.2.1.47.1.1.1.1.1 11
entPhysicalDescr=1.3.6.1.2.1.47.1.1.1.1.2
entPhysicalVendorType=1.3.6.1.2.1.47.1.1.1.1.3
entPhysicalContainedIn=1.3.6.1.2.1.47.1.1.1.1.4
entPhysicalClass=1.3.6.1.2.1.47.1.1.1.1.5 module (9) [ module designator ]
entPhysicalParentRelPos=1.3.6.1.2.1.47.1.1.1.1.6
entPhysicalName=1.3.6.1.2.1.47.1.1.1.1.7 unit-1 [ from index 10 ]
entPhysicalHardwareRev=1.3.6.1.2.1.47.1.1.1.1.8 BCM5665 REV 18 [ hardware ]
entPhysicalFirmwareRev=1.3.6.1.2.1.47.1.1.1.1.9 01.00.46 [ bootprom version ]
entPhysicalSoftwareRev=1.3.6.1.2.1.47.1.1.1.1.10 05.01.03.0007 [ firmware version ]
entPhysicalSerialNum=1.3.6.1.2.1.47.1.1.1.1.11 06491507905B [ serial# ]
entPhysicalMfgName=1.3.6.1.2.1.47.1.1.1.1.12 Enterasys Networks, Inc. [ manufacturer ]
entPhysicalModelName=1.3.6.1.2.1.47.1.1.1.1.13 C2H124-48P [ model# ]
entPhysicalAlias=1.3.6.1.2.1.47.1.1.1.1.14
entPhysicalAssetID=1.3.6.1.2.1.47.1.1.1.1.15
entPhysicalIsFRU=1.3.6.1.2.1.47.1.1.1.1.16

entPhysicalIndex=1.3.6.1.2.1.47.1.1.1.1.1 78
entPhysicalDescr=1.3.6.1.2.1.47.1.1.1.1.2
entPhysicalVendorType=1.3.6.1.2.1.47.1.1.1.1.3
entPhysicalContainedIn=1.3.6.1.2.1.47.1.1.1.1.4
entPhysicalClass=1.3.6.1.2.1.47.1.1.1.1.5 module (9) [ module designator ]
entPhysicalParentRelPos=1.3.6.1.2.1.47.1.1.1.1.6
entPhysicalName=1.3.6.1.2.1.47.1.1.1.1.7 unit-2 [ from index 77 ]
entPhysicalHardwareRev=1.3.6.1.2.1.47.1.1.1.1.8 BCM5695 REV 17 [ hardware ]
entPhysicalFirmwareRev=1.3.6.1.2.1.47.1.1.1.1.9 01.00.40 [ bootprom version ]
entPhysicalSoftwareRev=1.3.6.1.2.1.47.1.1.1.1.10 05.01.03.0007 [ firmware version ]
entPhysicalSerialNum=1.3.6.1.2.1.47.1.1.1.1.11 07440918905F [ serial# ]
entPhysicalMfgName=1.3.6.1.2.1.47.1.1.1.1.12 Enterasys Networks, Inc. [ manufacturer ]
entPhysicalModelName=1.3.6.1.2.1.47.1.1.1.1.13 C2G170-24 [ model# ]
entPhysicalAlias=1.3.6.1.2.1.47.1.1.1.1.14
entPhysicalAssetID=1.3.6.1.2.1.47.1.1.1.1.15
entPhysicalIsFRU=1.3.6.1.2.1.47.1.1.1.1.16

entPhysicalIndex=1.3.6.1.2.1.47.1.1.1.1.1 107
entPhysicalDescr=1.3.6.1.2.1.47.1.1.1.1.2
entPhysicalVendorType=1.3.6.1.2.1.47.1.1.1.1.3
entPhysicalContainedIn=1.3.6.1.2.1.47.1.1.1.1.4
entPhysicalClass=1.3.6.1.2.1.47.1.1.1.1.5 module (9) [ module designator ]
entPhysicalParentRelPos=1.3.6.1.2.1.47.1.1.1.1.6
entPhysicalName=1.3.6.1.2.1.47.1.1.1.1.7 unit-3 [ from index 106 ]
entPhysicalHardwareRev=1.3.6.1.2.1.47.1.1.1.1.8 BCM5695 REV 17 [ hardware ]
entPhysicalFirmwareRev=1.3.6.1.2.1.47.1.1.1.1.9 01.00.40 [ bootprom version ]
entPhysicalSoftwareRev=1.3.6.1.2.1.47.1.1.1.1.10 05.01.03.0007 [ firmware version ]
entPhysicalSerialNum=1.3.6.1.2.1.47.1.1.1.1.11 041800339041 [ serial# ]
entPhysicalMfgName=1.3.6.1.2.1.47.1.1.1.1.12 Enterasys Networks, Inc. [ manufacturer ]
entPhysicalModelName=1.3.6.1.2.1.47.1.1.1.1.13 C2K122-24 [ model# ]
entPhysicalAlias=1.3.6.1.2.1.47.1.1.1.1.14
entPhysicalAssetID=1.3.6.1.2.1.47.1.1.1.1.15
entPhysicalIsFRU=1.3.6.1.2.1.47.1.1.1.1.16

A form of the above information may be queried from the entityMIB=1.3.6.1.2.1.47 branch using NetSight Console, may be reported using the Entity MIB flexview from NetSight Console, or may be pulled from the Custom Attributes tab within NetSight Inventory Manager (12686). 

For third-party NMS use, the IETF Entity-mib (part of MIB-2) may be found within the mibs.zip file. 

If it is merely necessary to monitor for changes in the status of stack members, traps may be used for this purpose. With more recent firmware (C3 f/w all, C2 f/w 3.02.30+, B3 f/w all, B2 f/w 3.01.16+, A2 f/w 1.03.17+): 
Support has been added for the ctEntStateOperEnabled and ctEntStateOperDisabled traps. These traps announce if a unit has dropped from the stack due to a failure or if a unit has joined to the stack.
Photo of FAQ User

FAQ User, Official Rep

  • 13,620 Points 10k badge 2x thumb

Posted 5 years ago

  • 0
  • 1

There are no replies.

This conversation is no longer open for comments or replies.