<?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 RE: Monitoring Chassis and Module Status with SNMP of EOS (Enterasys) Devices in ExtremeSwitching (EOS)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57599#M1094</link>
    <description>Hi all,&lt;BR /&gt;
You have stumbled on a piece of deficiency that I have grumbled about before.   Not only do stackables not tell you when a stack member does not come up from a power down/reset, chassis have the same issue.    Worse, they forget to tell you about failed power supplies and failed fans.      I got Extreme to put in traps for failing blades/stack members in newer code, so maybe with a little push and shove, we as a community can get them to do something a little smarter at reboot/restart time.&lt;BR /&gt;
&lt;BR /&gt;
I would propose that a management module (on any type of device, red or purple) scan its hardware looking for objects that are configured but not operational.   These objects should include fans, power supplies, blades, stack units, stacking cables,  and anything else that only produces a single trap/log entry when that object fails.   (Note that this is not a definitive list, feel free to add.)&lt;BR /&gt;
Upon finding such (apparently) broken objects, send an alert  (trap/log/syslog) message out indicating same.     The gotcha here is you might need to do this a couple of times spaced say a minute apart in order to have a reasonable chance of getting through to your favorite network management system.  (The uplinks need to be online to get anywhere!)&lt;BR /&gt;
&lt;BR /&gt;
Reasonable?&lt;BR /&gt;
   James&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Mon, 09 Nov 2015 15:19:00 GMT</pubDate>
    <dc:creator>JAMES_WIEDEL</dc:creator>
    <dc:date>2015-11-09T15:19:00Z</dc:date>
    <item>
      <title>Monitoring Chassis and Module Status with SNMP of EOS (Enterasys) Devices</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57592#M1087</link>
      <description>I like to use PRTG for status polling of Enterasys switches, especially S-Series and Secure Stacks.&lt;BR /&gt;
Are there any SNMP OIDs which represent the status of modules in a chassis or the global status of a chassis or switch?&lt;BR /&gt;
&lt;BR /&gt;
Especially, I'm interested in module or stack member failures.&lt;BR /&gt;
&lt;BR /&gt;
Kind regrads&lt;BR /&gt;
Christoph&lt;BR /&gt;</description>
      <pubDate>Fri, 06 Nov 2015 20:45:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57592#M1087</guid>
      <dc:creator>Christoph</dc:creator>
      <dc:date>2015-11-06T20:45:00Z</dc:date>
    </item>
    <item>
      <title>RE: Monitoring Chassis and Module Status with SNMP of EOS (Enterasys) Devices</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57593#M1088</link>
      <description>I would review the the following.&lt;BR /&gt;
entityMIB=1.3.6.1.2.1.47&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 06 Nov 2015 20:59:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57593#M1088</guid>
      <dc:creator>Mike_Thomas</dc:creator>
      <dc:date>2015-11-06T20:59:00Z</dc:date>
    </item>
    <item>
      <title>RE: Monitoring Chassis and Module Status with SNMP of EOS (Enterasys) Devices</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57594#M1089</link>
      <description>These should be helpful... &lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/MIBs-for-N-S-Series-Power-Supply-and-Fan-Tray-Status" target="_blank" rel="nofollow noreferrer noopener"&gt;MIBs for N/S-Series Power Supply and Fan Tray Status&lt;/A&gt; &lt;BR /&gt;
&lt;A href="https://community.extremenetworks.com/extreme/topics/displaying_the_cpu_utilization_of_the_n_s_series" target="_blank" rel="nofollow noreferrer noopener"&gt;Displaying the CPU Utilization of the N/S-Series&lt;/A&gt; &lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://community.extremenetworks.com/extreme/topics/mib_for_determining_securestack_switch_stack_attributes" target="_blank" rel="nofollow noreferrer noopener"&gt;MIB for determining SecureStack switch stack attributes&lt;/A&gt; &lt;BR /&gt;
&lt;A href="https://community.extremenetworks.com/extreme/topics/viewing_system_utilization_on_the_securestacks" target="_blank" rel="nofollow noreferrer noopener"&gt;Viewing System Utilization on the SecureStacks&lt;/A&gt;</description>
      <pubDate>Fri, 06 Nov 2015 21:40:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57594#M1089</guid>
      <dc:creator>Paul_Poyant</dc:creator>
      <dc:date>2015-11-06T21:40:00Z</dc:date>
    </item>
    <item>
      <title>RE: Monitoring Chassis and Module Status with SNMP of EOS (Enterasys) Devices</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57595#M1090</link>
      <description>Hello Mike,&lt;BR /&gt;
hello Paul,&lt;BR /&gt;
&lt;BR /&gt;
thanks for your answers. Unfortunately, it's not exactly what I'm looking for.&lt;BR /&gt;
I have searched through the MIBs, but I was not able to find an OID which shows whether all line cards, fabrics or stacking members are online and working.&lt;BR /&gt;
&lt;BR /&gt;
For example the entityMIB shows all stack members even though I disconnected one.&lt;BR /&gt;
&lt;BR /&gt;
Maybe I'm able monitor a defect by polling the serial numbers and if the value is empty to trigger an alarm. But I'm not sure whether all kind of hardware failures could be discovered with such a workaround...?&lt;BR /&gt;
&lt;BR /&gt;
Kind regards&lt;BR /&gt;
Christoph &lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Mon, 09 Nov 2015 15:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57595#M1090</guid>
      <dc:creator>Christoph</dc:creator>
      <dc:date>2015-11-09T15:19:00Z</dc:date>
    </item>
    <item>
      <title>RE: Monitoring Chassis and Module Status with SNMP of EOS (Enterasys) Devices</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57596#M1091</link>
      <description>We use SNMP traps to detect the loss of stack members and modules.</description>
      <pubDate>Mon, 09 Nov 2015 15:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57596#M1091</guid>
      <dc:creator>Curtis_Parish1</dc:creator>
      <dc:date>2015-11-09T15:19:00Z</dc:date>
    </item>
    <item>
      <title>RE: Monitoring Chassis and Module Status with SNMP of EOS (Enterasys) Devices</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57597#M1092</link>
      <description>Hey Curtis, thank for your suggestion.&lt;BR /&gt;
I also use traps, but with PRTG it's not the very best solution. And traps are not sent if line card or stack members don't come up after a reboot or power loss.&lt;BR /&gt;</description>
      <pubDate>Mon, 09 Nov 2015 15:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57597#M1092</guid>
      <dc:creator>Christoph</dc:creator>
      <dc:date>2015-11-09T15:19:00Z</dc:date>
    </item>
    <item>
      <title>RE: Monitoring Chassis and Module Status with SNMP of EOS (Enterasys) Devices</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57598#M1093</link>
      <description>I personally do not think Netsight even handles stacks and modules well when it comes to loss of a card or member.    Unless an alarm is generated by the device  Netsight is blissfully unaware of a problem. Of course if the stack member or card never powers up at boot then an alarm is not generated.</description>
      <pubDate>Mon, 09 Nov 2015 15:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57598#M1093</guid>
      <dc:creator>Curtis_Parish1</dc:creator>
      <dc:date>2015-11-09T15:19:00Z</dc:date>
    </item>
    <item>
      <title>RE: Monitoring Chassis and Module Status with SNMP of EOS (Enterasys) Devices</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57599#M1094</link>
      <description>Hi all,&lt;BR /&gt;
You have stumbled on a piece of deficiency that I have grumbled about before.   Not only do stackables not tell you when a stack member does not come up from a power down/reset, chassis have the same issue.    Worse, they forget to tell you about failed power supplies and failed fans.      I got Extreme to put in traps for failing blades/stack members in newer code, so maybe with a little push and shove, we as a community can get them to do something a little smarter at reboot/restart time.&lt;BR /&gt;
&lt;BR /&gt;
I would propose that a management module (on any type of device, red or purple) scan its hardware looking for objects that are configured but not operational.   These objects should include fans, power supplies, blades, stack units, stacking cables,  and anything else that only produces a single trap/log entry when that object fails.   (Note that this is not a definitive list, feel free to add.)&lt;BR /&gt;
Upon finding such (apparently) broken objects, send an alert  (trap/log/syslog) message out indicating same.     The gotcha here is you might need to do this a couple of times spaced say a minute apart in order to have a reasonable chance of getting through to your favorite network management system.  (The uplinks need to be online to get anywhere!)&lt;BR /&gt;
&lt;BR /&gt;
Reasonable?&lt;BR /&gt;
   James&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Mon, 09 Nov 2015 15:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57599#M1094</guid>
      <dc:creator>JAMES_WIEDEL</dc:creator>
      <dc:date>2015-11-09T15:19:00Z</dc:date>
    </item>
    <item>
      <title>RE: Monitoring Chassis and Module Status with SNMP of EOS (Enterasys) Devices</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57600#M1095</link>
      <description>Netsight can tell you if there is a change in configuration by comparing current vs backed up config.  Would be nice if it would tell you if there was a change in hardware configuration.  That would catch the devices and modules that fail at power up.</description>
      <pubDate>Mon, 09 Nov 2015 15:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57600#M1095</guid>
      <dc:creator>Curtis_Parish1</dc:creator>
      <dc:date>2015-11-09T15:19:00Z</dc:date>
    </item>
    <item>
      <title>RE: Monitoring Chassis and Module Status with SNMP of EOS (Enterasys) Devices</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57601#M1096</link>
      <description>Lets make sure that we have the following basics covered. This is helpful only for Netsight, but may be able to utilize the concepts in other network management apps using traps.&lt;BR /&gt;
&lt;BR /&gt;
Make sure that traps are configured first in Netsight.&lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-Configure-SNMPv3-Traps-via-NetSight-Console" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-Configure-SNMPv3-Traps-via-NetSight...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
Then make sure we got traps for switch loss enabled.&lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-create-an-alarm-in-NetSight-to-show-when-a-SecureStack-member-switch-has-failed" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-create-an-alarm-in-NetSight-to-show...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Nov 2015 01:59:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/monitoring-chassis-and-module-status-with-snmp-of-eos-enterasys/m-p/57601#M1096</guid>
      <dc:creator>Mike_Thomas</dc:creator>
      <dc:date>2015-11-11T01:59:00Z</dc:date>
    </item>
  </channel>
</rss>

