<?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 Determining the Failing SecureStack Unit from a Fan Failure Trap in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/determining-the-failing-securestack-unit-from-a-fan-failure-trap/m-p/50379#M655</link>
    <description>Article ID: 13323 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
SecureStack C3, C2, B3, B2, A2&lt;BR /&gt;
NetSight Console &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Discussion&lt;/B&gt;&lt;BR /&gt;
Determining the failing unit from a fan failure &lt;I&gt;syslog&lt;/I&gt; message is explained in &lt;A href="http://bit.ly/1cpN7UG" target="_blank" rel="nofollow noreferrer noopener"&gt;5743&lt;/A&gt;. &lt;BR /&gt;
&lt;BR /&gt;
Fan failure &lt;I&gt;traps&lt;/I&gt; are not specifically controllable but may be generated from the fanFail section of the cabletron-traps MIB, when traps are enabled and a fan has failed. &lt;BR /&gt;
&lt;BR /&gt;
In NetSight Console, the trap summary line looks something like: Notice  SNMP v2  09/09/2010 01:28:27 PM  10.20.109.50  ---  SNMP Trap  Trap  fanFail  Fan Failure.Double-clicking on a summary line to pull up event details looks something like: Timestamp:   09/09/2010 01:28:27 PM      Acknowledged: No&lt;BR /&gt;
 Type:        Trap                        Source:       10.20.109.50&lt;BR /&gt;
 Event Name:  fanFail                     Client:       ---&lt;BR /&gt;
 Severity:    Notice                      User:         SNMP Trap&lt;BR /&gt;
 Category:    SNMP v2&lt;BR /&gt;
 &lt;BR /&gt;
 Information: Fan Failure.&lt;BR /&gt;
 &lt;BR /&gt;
 Enterprise:  Cabletron                   Trap Number:  .1.3.6.1.4.1.52.0.286&lt;BR /&gt;
 &lt;BR /&gt;
 Description: This trap is generated when the device detects that&lt;BR /&gt;
              the system fans have failed.Such traps are not formulated to provide detailed information of the failing unit within a stacked topology, however do serve the purpose of alerting the network administrator to look in the syslog for more detailed diagnostic information. &lt;BR /&gt;
&lt;BR /&gt;
If a current syslog repository is not available in NetSight or some other network management application, a current.log (&lt;A href="http://bit.ly/1pOU3VK" target="_blank" rel="nofollow noreferrer noopener"&gt;5487&lt;/A&gt;) file would provide fan failure information for a standalone or a stack, with any firmware version. A simpler approach that would work for this purpose is to issue a 'show support' command while running "higher firmware". The items listed at the end of that output - as read from the manager unit - may be interpreted as explained in &lt;A href="http://bit.ly/1cpN7UG" target="_blank" rel="nofollow noreferrer noopener"&gt;5743&lt;/A&gt;.</description>
    <pubDate>Tue, 26 Nov 2013 21:06:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-11-26T21:06:00Z</dc:date>
    <item>
      <title>Determining the Failing SecureStack Unit from a Fan Failure Trap</title>
      <link>https://community.extremenetworks.com/t5/faqs/determining-the-failing-securestack-unit-from-a-fan-failure-trap/m-p/50379#M655</link>
      <description>Article ID: 13323 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
SecureStack C3, C2, B3, B2, A2&lt;BR /&gt;
NetSight Console &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Discussion&lt;/B&gt;&lt;BR /&gt;
Determining the failing unit from a fan failure &lt;I&gt;syslog&lt;/I&gt; message is explained in &lt;A href="http://bit.ly/1cpN7UG" target="_blank" rel="nofollow noreferrer noopener"&gt;5743&lt;/A&gt;. &lt;BR /&gt;
&lt;BR /&gt;
Fan failure &lt;I&gt;traps&lt;/I&gt; are not specifically controllable but may be generated from the fanFail section of the cabletron-traps MIB, when traps are enabled and a fan has failed. &lt;BR /&gt;
&lt;BR /&gt;
In NetSight Console, the trap summary line looks something like: Notice  SNMP v2  09/09/2010 01:28:27 PM  10.20.109.50  ---  SNMP Trap  Trap  fanFail  Fan Failure.Double-clicking on a summary line to pull up event details looks something like: Timestamp:   09/09/2010 01:28:27 PM      Acknowledged: No&lt;BR /&gt;
 Type:        Trap                        Source:       10.20.109.50&lt;BR /&gt;
 Event Name:  fanFail                     Client:       ---&lt;BR /&gt;
 Severity:    Notice                      User:         SNMP Trap&lt;BR /&gt;
 Category:    SNMP v2&lt;BR /&gt;
 &lt;BR /&gt;
 Information: Fan Failure.&lt;BR /&gt;
 &lt;BR /&gt;
 Enterprise:  Cabletron                   Trap Number:  .1.3.6.1.4.1.52.0.286&lt;BR /&gt;
 &lt;BR /&gt;
 Description: This trap is generated when the device detects that&lt;BR /&gt;
              the system fans have failed.Such traps are not formulated to provide detailed information of the failing unit within a stacked topology, however do serve the purpose of alerting the network administrator to look in the syslog for more detailed diagnostic information. &lt;BR /&gt;
&lt;BR /&gt;
If a current syslog repository is not available in NetSight or some other network management application, a current.log (&lt;A href="http://bit.ly/1pOU3VK" target="_blank" rel="nofollow noreferrer noopener"&gt;5487&lt;/A&gt;) file would provide fan failure information for a standalone or a stack, with any firmware version. A simpler approach that would work for this purpose is to issue a 'show support' command while running "higher firmware". The items listed at the end of that output - as read from the manager unit - may be interpreted as explained in &lt;A href="http://bit.ly/1cpN7UG" target="_blank" rel="nofollow noreferrer noopener"&gt;5743&lt;/A&gt;.</description>
      <pubDate>Tue, 26 Nov 2013 21:06:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/determining-the-failing-securestack-unit-from-a-fan-failure-trap/m-p/50379#M655</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-11-26T21:06:00Z</dc:date>
    </item>
  </channel>
</rss>

