<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic MIB for determining SecureStack switch stack attributes in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/mib-for-determining-securestack-switch-stack-attributes/m-p/51388#M717</link>
    <description>Article ID: 7483 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
SecureStack C3&lt;BR /&gt;
SecureStack C2&lt;BR /&gt;
SecureStack B3&lt;BR /&gt;
SecureStack B2&lt;BR /&gt;
SecureStack A2 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Goals&lt;/B&gt;&lt;BR /&gt;
MIB for monitoring SecureStack switch stack unit status. &lt;BR /&gt;
MIB for determining serial number.&lt;BR /&gt;
MIB for determining firmware version. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt; &lt;BR /&gt;
Entity MIB &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt; &lt;BR /&gt;
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. &lt;BR /&gt;
&lt;BR /&gt;
To demonstrate this, here is a view of a sample SecureStack C2 three-stack: C2(ro)-&amp;gt;show switch&lt;BR /&gt;
         Management   Preconfig   Plugged-in        Switch             Code&lt;BR /&gt;
 Switch    Status     Model ID    Model ID          Status            Version&lt;BR /&gt;
 ------ ------------ ----------- ----------- --------------------- --------------&lt;BR /&gt;
 1      Mgmt Switch  C2H124-48P  C2H124-48P  OK                    05.02.01.0006&lt;BR /&gt;
 2      Stack Member C2G170-24   C2G170-24   OK                    05.02.01.0006&lt;BR /&gt;
 3      Stack Member C2K122-24   C2K122-24   OK                    05.02.01.0006&lt;BR /&gt;
 C2(ro)-&amp;gt;show version&lt;BR /&gt;
 &lt;BR /&gt;
 Copyright (c) 2007 by Enterasys Networks, Inc.&lt;BR /&gt;
 &lt;BR /&gt;
  Model            Serial #             Versions&lt;BR /&gt;
 --------------  -----------------  -------------------&lt;BR /&gt;
 &lt;BR /&gt;
 C2H124-48P        06491507905B      Hw:BCM5665 REV 18&lt;BR /&gt;
                                     Bp:01.00.46&lt;BR /&gt;
                                     Fw:05.02.01.0006&lt;BR /&gt;
                                     BuFw:05.01.03.0007&lt;BR /&gt;
                                     PoE:500_3&lt;BR /&gt;
 &lt;BR /&gt;
 C2G170-24         07440918905F      Hw:BCM5695 REV 17&lt;BR /&gt;
                                     Bp:01.00.40&lt;BR /&gt;
                                     Fw:05.02.01.0006&lt;BR /&gt;
                                     BuFw:05.01.03.0007&lt;BR /&gt;
 &lt;BR /&gt;
 C2K122-24         041800339041      Hw:BCM5695 REV 17&lt;BR /&gt;
                                     Bp:01.00.40&lt;BR /&gt;
                                     Fw:05.02.01.0006&lt;BR /&gt;
                                     BuFw:05.01.03.0007&lt;BR /&gt;
 &lt;BR /&gt;
 C2(ro)-&amp;gt;&lt;BR /&gt;
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. &lt;BR /&gt;
&lt;BR /&gt;
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&lt;BR /&gt;
        entityMIBObjects=1.3.6.1.2.1.47.1&lt;BR /&gt;
          entityPhysical=1.3.6.1.2.1.47.1.1&lt;BR /&gt;
        entPhysicalTable=1.3.6.1.2.1.47.1.1.1&lt;BR /&gt;
        entPhysicalEntry=1.3.6.1.2.1.47.1.1.1.1&lt;BR /&gt;
 &lt;BR /&gt;
        entPhysicalIndex=1.3.6.1.2.1.47.1.1.1.1.1   11&lt;BR /&gt;
        entPhysicalDescr=1.3.6.1.2.1.47.1.1.1.1.2&lt;BR /&gt;
   entPhysicalVendorType=1.3.6.1.2.1.47.1.1.1.1.3&lt;BR /&gt;
  entPhysicalContainedIn=1.3.6.1.2.1.47.1.1.1.1.4&lt;BR /&gt;
        entPhysicalClass=1.3.6.1.2.1.47.1.1.1.1.5   module (9)  [ module designator ]&lt;BR /&gt;
 entPhysicalParentRelPos=1.3.6.1.2.1.47.1.1.1.1.6&lt;BR /&gt;
         entPhysicalName=1.3.6.1.2.1.47.1.1.1.1.7   unit-1  [ from index 10 ]&lt;BR /&gt;
  entPhysicalHardwareRev=1.3.6.1.2.1.47.1.1.1.1.8   BCM5665 REV 18  [ hardware ]&lt;BR /&gt;
  entPhysicalFirmwareRev=1.3.6.1.2.1.47.1.1.1.1.9   01.00.46  [ bootprom version ]&lt;BR /&gt;
  entPhysicalSoftwareRev=1.3.6.1.2.1.47.1.1.1.1.10  05.01.03.0007  [ firmware version ]&lt;BR /&gt;
    entPhysicalSerialNum=1.3.6.1.2.1.47.1.1.1.1.11  06491507905B  [ serial# ]&lt;BR /&gt;
      entPhysicalMfgName=1.3.6.1.2.1.47.1.1.1.1.12  Enterasys Networks, Inc. [ manufacturer ]&lt;BR /&gt;
    entPhysicalModelName=1.3.6.1.2.1.47.1.1.1.1.13  C2H124-48P  [ model# ]&lt;BR /&gt;
        entPhysicalAlias=1.3.6.1.2.1.47.1.1.1.1.14&lt;BR /&gt;
      entPhysicalAssetID=1.3.6.1.2.1.47.1.1.1.1.15&lt;BR /&gt;
        entPhysicalIsFRU=1.3.6.1.2.1.47.1.1.1.1.16&lt;BR /&gt;
 &lt;BR /&gt;
        entPhysicalIndex=1.3.6.1.2.1.47.1.1.1.1.1   78&lt;BR /&gt;
        entPhysicalDescr=1.3.6.1.2.1.47.1.1.1.1.2&lt;BR /&gt;
   entPhysicalVendorType=1.3.6.1.2.1.47.1.1.1.1.3&lt;BR /&gt;
  entPhysicalContainedIn=1.3.6.1.2.1.47.1.1.1.1.4&lt;BR /&gt;
        entPhysicalClass=1.3.6.1.2.1.47.1.1.1.1.5   module (9)  [ module designator ]&lt;BR /&gt;
 entPhysicalParentRelPos=1.3.6.1.2.1.47.1.1.1.1.6&lt;BR /&gt;
         entPhysicalName=1.3.6.1.2.1.47.1.1.1.1.7   unit-2  [ from index 77 ]&lt;BR /&gt;
  entPhysicalHardwareRev=1.3.6.1.2.1.47.1.1.1.1.8   BCM5695 REV 17  [ hardware ]&lt;BR /&gt;
  entPhysicalFirmwareRev=1.3.6.1.2.1.47.1.1.1.1.9   01.00.40  [ bootprom version ]&lt;BR /&gt;
  entPhysicalSoftwareRev=1.3.6.1.2.1.47.1.1.1.1.10  05.01.03.0007  [ firmware version ]&lt;BR /&gt;
    entPhysicalSerialNum=1.3.6.1.2.1.47.1.1.1.1.11  07440918905F  [ serial# ]&lt;BR /&gt;
      entPhysicalMfgName=1.3.6.1.2.1.47.1.1.1.1.12  Enterasys Networks, Inc.  [ manufacturer ]&lt;BR /&gt;
    entPhysicalModelName=1.3.6.1.2.1.47.1.1.1.1.13  C2G170-24  [ model# ]&lt;BR /&gt;
        entPhysicalAlias=1.3.6.1.2.1.47.1.1.1.1.14&lt;BR /&gt;
      entPhysicalAssetID=1.3.6.1.2.1.47.1.1.1.1.15&lt;BR /&gt;
        entPhysicalIsFRU=1.3.6.1.2.1.47.1.1.1.1.16&lt;BR /&gt;
 &lt;BR /&gt;
        entPhysicalIndex=1.3.6.1.2.1.47.1.1.1.1.1   107&lt;BR /&gt;
        entPhysicalDescr=1.3.6.1.2.1.47.1.1.1.1.2&lt;BR /&gt;
   entPhysicalVendorType=1.3.6.1.2.1.47.1.1.1.1.3&lt;BR /&gt;
  entPhysicalContainedIn=1.3.6.1.2.1.47.1.1.1.1.4&lt;BR /&gt;
        entPhysicalClass=1.3.6.1.2.1.47.1.1.1.1.5   module (9)  [ module designator ]&lt;BR /&gt;
 entPhysicalParentRelPos=1.3.6.1.2.1.47.1.1.1.1.6&lt;BR /&gt;
         entPhysicalName=1.3.6.1.2.1.47.1.1.1.1.7   unit-3  [ from index 106 ]&lt;BR /&gt;
  entPhysicalHardwareRev=1.3.6.1.2.1.47.1.1.1.1.8   BCM5695 REV 17  [ hardware ]&lt;BR /&gt;
  entPhysicalFirmwareRev=1.3.6.1.2.1.47.1.1.1.1.9   01.00.40  [ bootprom version ]&lt;BR /&gt;
  entPhysicalSoftwareRev=1.3.6.1.2.1.47.1.1.1.1.10  05.01.03.0007  [ firmware version ]&lt;BR /&gt;
    entPhysicalSerialNum=1.3.6.1.2.1.47.1.1.1.1.11  041800339041  [ serial# ]&lt;BR /&gt;
      entPhysicalMfgName=1.3.6.1.2.1.47.1.1.1.1.12  Enterasys Networks, Inc.  [ manufacturer ]&lt;BR /&gt;
    entPhysicalModelName=1.3.6.1.2.1.47.1.1.1.1.13  C2K122-24  [ model# ]&lt;BR /&gt;
        entPhysicalAlias=1.3.6.1.2.1.47.1.1.1.1.14&lt;BR /&gt;
      entPhysicalAssetID=1.3.6.1.2.1.47.1.1.1.1.15&lt;BR /&gt;
        entPhysicalIsFRU=1.3.6.1.2.1.47.1.1.1.1.16&lt;BR /&gt;
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 (&lt;A href="http://bit.ly/1uj4tNL" target="_blank" rel="nofollow noreferrer noopener"&gt;12686&lt;/A&gt;). &lt;BR /&gt;
&lt;BR /&gt;
For third-party NMS use, the IETF Entity-mib (part of MIB-2) may be found within the mibs.zip file. &lt;BR /&gt;
&lt;BR /&gt;
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+): &lt;BR /&gt;
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.</description>
    <pubDate>Tue, 19 Nov 2013 02:26:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-11-19T02:26:00Z</dc:date>
    <item>
      <title>MIB for determining SecureStack switch stack attributes</title>
      <link>https://community.extremenetworks.com/t5/faqs/mib-for-determining-securestack-switch-stack-attributes/m-p/51388#M717</link>
      <description>Article ID: 7483 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
SecureStack C3&lt;BR /&gt;
SecureStack C2&lt;BR /&gt;
SecureStack B3&lt;BR /&gt;
SecureStack B2&lt;BR /&gt;
SecureStack A2 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Goals&lt;/B&gt;&lt;BR /&gt;
MIB for monitoring SecureStack switch stack unit status. &lt;BR /&gt;
MIB for determining serial number.&lt;BR /&gt;
MIB for determining firmware version. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt; &lt;BR /&gt;
Entity MIB &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt; &lt;BR /&gt;
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. &lt;BR /&gt;
&lt;BR /&gt;
To demonstrate this, here is a view of a sample SecureStack C2 three-stack: C2(ro)-&amp;gt;show switch&lt;BR /&gt;
         Management   Preconfig   Plugged-in        Switch             Code&lt;BR /&gt;
 Switch    Status     Model ID    Model ID          Status            Version&lt;BR /&gt;
 ------ ------------ ----------- ----------- --------------------- --------------&lt;BR /&gt;
 1      Mgmt Switch  C2H124-48P  C2H124-48P  OK                    05.02.01.0006&lt;BR /&gt;
 2      Stack Member C2G170-24   C2G170-24   OK                    05.02.01.0006&lt;BR /&gt;
 3      Stack Member C2K122-24   C2K122-24   OK                    05.02.01.0006&lt;BR /&gt;
 C2(ro)-&amp;gt;show version&lt;BR /&gt;
 &lt;BR /&gt;
 Copyright (c) 2007 by Enterasys Networks, Inc.&lt;BR /&gt;
 &lt;BR /&gt;
  Model            Serial #             Versions&lt;BR /&gt;
 --------------  -----------------  -------------------&lt;BR /&gt;
 &lt;BR /&gt;
 C2H124-48P        06491507905B      Hw:BCM5665 REV 18&lt;BR /&gt;
                                     Bp:01.00.46&lt;BR /&gt;
                                     Fw:05.02.01.0006&lt;BR /&gt;
                                     BuFw:05.01.03.0007&lt;BR /&gt;
                                     PoE:500_3&lt;BR /&gt;
 &lt;BR /&gt;
 C2G170-24         07440918905F      Hw:BCM5695 REV 17&lt;BR /&gt;
                                     Bp:01.00.40&lt;BR /&gt;
                                     Fw:05.02.01.0006&lt;BR /&gt;
                                     BuFw:05.01.03.0007&lt;BR /&gt;
 &lt;BR /&gt;
 C2K122-24         041800339041      Hw:BCM5695 REV 17&lt;BR /&gt;
                                     Bp:01.00.40&lt;BR /&gt;
                                     Fw:05.02.01.0006&lt;BR /&gt;
                                     BuFw:05.01.03.0007&lt;BR /&gt;
 &lt;BR /&gt;
 C2(ro)-&amp;gt;&lt;BR /&gt;
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. &lt;BR /&gt;
&lt;BR /&gt;
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&lt;BR /&gt;
        entityMIBObjects=1.3.6.1.2.1.47.1&lt;BR /&gt;
          entityPhysical=1.3.6.1.2.1.47.1.1&lt;BR /&gt;
        entPhysicalTable=1.3.6.1.2.1.47.1.1.1&lt;BR /&gt;
        entPhysicalEntry=1.3.6.1.2.1.47.1.1.1.1&lt;BR /&gt;
 &lt;BR /&gt;
        entPhysicalIndex=1.3.6.1.2.1.47.1.1.1.1.1   11&lt;BR /&gt;
        entPhysicalDescr=1.3.6.1.2.1.47.1.1.1.1.2&lt;BR /&gt;
   entPhysicalVendorType=1.3.6.1.2.1.47.1.1.1.1.3&lt;BR /&gt;
  entPhysicalContainedIn=1.3.6.1.2.1.47.1.1.1.1.4&lt;BR /&gt;
        entPhysicalClass=1.3.6.1.2.1.47.1.1.1.1.5   module (9)  [ module designator ]&lt;BR /&gt;
 entPhysicalParentRelPos=1.3.6.1.2.1.47.1.1.1.1.6&lt;BR /&gt;
         entPhysicalName=1.3.6.1.2.1.47.1.1.1.1.7   unit-1  [ from index 10 ]&lt;BR /&gt;
  entPhysicalHardwareRev=1.3.6.1.2.1.47.1.1.1.1.8   BCM5665 REV 18  [ hardware ]&lt;BR /&gt;
  entPhysicalFirmwareRev=1.3.6.1.2.1.47.1.1.1.1.9   01.00.46  [ bootprom version ]&lt;BR /&gt;
  entPhysicalSoftwareRev=1.3.6.1.2.1.47.1.1.1.1.10  05.01.03.0007  [ firmware version ]&lt;BR /&gt;
    entPhysicalSerialNum=1.3.6.1.2.1.47.1.1.1.1.11  06491507905B  [ serial# ]&lt;BR /&gt;
      entPhysicalMfgName=1.3.6.1.2.1.47.1.1.1.1.12  Enterasys Networks, Inc. [ manufacturer ]&lt;BR /&gt;
    entPhysicalModelName=1.3.6.1.2.1.47.1.1.1.1.13  C2H124-48P  [ model# ]&lt;BR /&gt;
        entPhysicalAlias=1.3.6.1.2.1.47.1.1.1.1.14&lt;BR /&gt;
      entPhysicalAssetID=1.3.6.1.2.1.47.1.1.1.1.15&lt;BR /&gt;
        entPhysicalIsFRU=1.3.6.1.2.1.47.1.1.1.1.16&lt;BR /&gt;
 &lt;BR /&gt;
        entPhysicalIndex=1.3.6.1.2.1.47.1.1.1.1.1   78&lt;BR /&gt;
        entPhysicalDescr=1.3.6.1.2.1.47.1.1.1.1.2&lt;BR /&gt;
   entPhysicalVendorType=1.3.6.1.2.1.47.1.1.1.1.3&lt;BR /&gt;
  entPhysicalContainedIn=1.3.6.1.2.1.47.1.1.1.1.4&lt;BR /&gt;
        entPhysicalClass=1.3.6.1.2.1.47.1.1.1.1.5   module (9)  [ module designator ]&lt;BR /&gt;
 entPhysicalParentRelPos=1.3.6.1.2.1.47.1.1.1.1.6&lt;BR /&gt;
         entPhysicalName=1.3.6.1.2.1.47.1.1.1.1.7   unit-2  [ from index 77 ]&lt;BR /&gt;
  entPhysicalHardwareRev=1.3.6.1.2.1.47.1.1.1.1.8   BCM5695 REV 17  [ hardware ]&lt;BR /&gt;
  entPhysicalFirmwareRev=1.3.6.1.2.1.47.1.1.1.1.9   01.00.40  [ bootprom version ]&lt;BR /&gt;
  entPhysicalSoftwareRev=1.3.6.1.2.1.47.1.1.1.1.10  05.01.03.0007  [ firmware version ]&lt;BR /&gt;
    entPhysicalSerialNum=1.3.6.1.2.1.47.1.1.1.1.11  07440918905F  [ serial# ]&lt;BR /&gt;
      entPhysicalMfgName=1.3.6.1.2.1.47.1.1.1.1.12  Enterasys Networks, Inc.  [ manufacturer ]&lt;BR /&gt;
    entPhysicalModelName=1.3.6.1.2.1.47.1.1.1.1.13  C2G170-24  [ model# ]&lt;BR /&gt;
        entPhysicalAlias=1.3.6.1.2.1.47.1.1.1.1.14&lt;BR /&gt;
      entPhysicalAssetID=1.3.6.1.2.1.47.1.1.1.1.15&lt;BR /&gt;
        entPhysicalIsFRU=1.3.6.1.2.1.47.1.1.1.1.16&lt;BR /&gt;
 &lt;BR /&gt;
        entPhysicalIndex=1.3.6.1.2.1.47.1.1.1.1.1   107&lt;BR /&gt;
        entPhysicalDescr=1.3.6.1.2.1.47.1.1.1.1.2&lt;BR /&gt;
   entPhysicalVendorType=1.3.6.1.2.1.47.1.1.1.1.3&lt;BR /&gt;
  entPhysicalContainedIn=1.3.6.1.2.1.47.1.1.1.1.4&lt;BR /&gt;
        entPhysicalClass=1.3.6.1.2.1.47.1.1.1.1.5   module (9)  [ module designator ]&lt;BR /&gt;
 entPhysicalParentRelPos=1.3.6.1.2.1.47.1.1.1.1.6&lt;BR /&gt;
         entPhysicalName=1.3.6.1.2.1.47.1.1.1.1.7   unit-3  [ from index 106 ]&lt;BR /&gt;
  entPhysicalHardwareRev=1.3.6.1.2.1.47.1.1.1.1.8   BCM5695 REV 17  [ hardware ]&lt;BR /&gt;
  entPhysicalFirmwareRev=1.3.6.1.2.1.47.1.1.1.1.9   01.00.40  [ bootprom version ]&lt;BR /&gt;
  entPhysicalSoftwareRev=1.3.6.1.2.1.47.1.1.1.1.10  05.01.03.0007  [ firmware version ]&lt;BR /&gt;
    entPhysicalSerialNum=1.3.6.1.2.1.47.1.1.1.1.11  041800339041  [ serial# ]&lt;BR /&gt;
      entPhysicalMfgName=1.3.6.1.2.1.47.1.1.1.1.12  Enterasys Networks, Inc.  [ manufacturer ]&lt;BR /&gt;
    entPhysicalModelName=1.3.6.1.2.1.47.1.1.1.1.13  C2K122-24  [ model# ]&lt;BR /&gt;
        entPhysicalAlias=1.3.6.1.2.1.47.1.1.1.1.14&lt;BR /&gt;
      entPhysicalAssetID=1.3.6.1.2.1.47.1.1.1.1.15&lt;BR /&gt;
        entPhysicalIsFRU=1.3.6.1.2.1.47.1.1.1.1.16&lt;BR /&gt;
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 (&lt;A href="http://bit.ly/1uj4tNL" target="_blank" rel="nofollow noreferrer noopener"&gt;12686&lt;/A&gt;). &lt;BR /&gt;
&lt;BR /&gt;
For third-party NMS use, the IETF Entity-mib (part of MIB-2) may be found within the mibs.zip file. &lt;BR /&gt;
&lt;BR /&gt;
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+): &lt;BR /&gt;
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.</description>
      <pubDate>Tue, 19 Nov 2013 02:26:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/mib-for-determining-securestack-switch-stack-attributes/m-p/51388#M717</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-11-19T02:26:00Z</dc:date>
    </item>
  </channel>
</rss>

