Installation Guide

• MUX tap number:
– 0-7 - there are total of 8 MUX taps connected to a MUX device.
– 15 - MUX tap is non applicable
• Device ID
• Device address
• Description of the load
If the GIEI severity changes from the time the GIEI is set to major, the rst Syslog message in the static section of the log is updated to
reect this change. A copy of this updated message is generated in the dynamic section of the log and a copy is sent to SNMP log
server.
When an I2C failure is rst detected, a second Syslog message is generated containing information about the last successful I2C access
before the GIEI error ag was set. The last successful access information remains unchanged until the GIEI is cleared. A copy of the
second Syslog message is also sent to the SNMP log server.
The second Syslog message is always displayed as an informational Syslog. The following example shows an informational Syslog
message:
device# show logging
Syslog logging: enabled (0 messages dropped, 0 flushes, 1 overruns)
Buffer logging: level ACDMEINW, 50 messages logged
level code: A=alert C=critical D=debugging M=emergency E=error
I=informational N=notification W=warning
Static Log Buffer:
Apr 16 18:21:25:A:System: Power Supply 2 , middle, Not Installed
(FAILED)
Apr 16 18:21:25:A:System: Power Supply 3 , top, Not Installed (FAILED)
Apr 16 18:22:12:I:System: i2c recovered (GIEI = clear), Severity Minor,
Mux index 0, Mux tap 4, ID 0x4, Addr 0x5, (FANTRAY4)
Dynamic Log Buffer (50 lines):
Apr 16 18:22:12:I:System: i2c recovered (GIEI = clear), Severity Minor,
Mux index 0, Mux tap 4, ID 0x4, Addr 0x5, (FANTRAY4)
Apr 16 18:21:27:I:System: bad i2c access (GIEI = set), Severity Minor,
Mux index 0, Mux tap 4, ID 0x4, Addr 0x5, (FANTRAY4)
Apr 16 18:21:25:A:System: bad i2c access (GIEI = set), Severity Major,
Mux index 0, Mux tap 4, ID 0x4, Addr 0x5, (FANTRAY4)
Apr 16 18:21:24:I:System: last good i2c access, Mux index 0, Mux tap 1,
ID 0x9, Addr 0x1, (SNM1TEMP)
When the GIEI
ag is cleared, the rst Syslog message in the static section of the log is updated to show that the GIEI is set to clear. The
second Syslog message in the static section is removed. A copy of the updated rst Syslog message is also generated in the dynamic
section of the log and in SNMP log server.
When a problematic device is removed from the system, the GIEI is cleared and all Syslog messages are updated to show that the GIEI is
set to clear.
If an I2C failure has not occurred, there will be no I2C messages in the static log, dynamic log, or SNMP log server. The following
example shows output from the show logging command when there is no I2C failure.
device# show logging
Syslog logging: enabled (0 messages dropped, 0 flushes, 1 overruns)
Buffer logging: level ACDMEINW, 50 messages logged
level code: A=alert C=critical D=debugging M=emergency E=error
I=informational N=notification W=warning
Static Log Buffer:
Apr 16 18:21:25:A:System: Power Supply 2 , middle, Not Installed (FAILED)
Apr 16 18:21:25:A:System: Power Supply 3 , top, Not Installed (FAILED)
Dynamic Log Buffer (50 lines):
Mar 28 12:36:47:A:System: Set fan speed to MED (75%)
Mar 25 21:40:47:A:System: Set fan speed to MED-HI (90%)
Mar 25 16:30:47:A:System: Set fan speed to MED (75%)
Mar 23 23:12:07:A:System: Set fan speed to MED-HI (90%)
Managing the device
Extreme Routing MLX Series Hardware Installation Guide
53-1004203-04 203