13.07.2015 Views

Brocade MLX Series and Brocade NetIron XMR Hardware ...

Brocade MLX Series and Brocade NetIron XMR Hardware ...

Brocade MLX Series and Brocade NetIron XMR Hardware ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

7Managing the device• all - enables power to all interface modules• disables power to the interface module in the specified slot. You can specify1-4 for 4-slot routers, 1-8 for 8-slot routers, 1-16 for 16-slot routers, <strong>and</strong> 1-32 for 32-slotrouters.Monitoring I2C failures on management modulesThe management module accesses temperature sensors, fan controllers, power supplies, serialPROMs, <strong>and</strong> other devices are all accessed through the I2C serial bus. When I2C devices areinaccessible, generic (<strong>and</strong> uninformative) error messages are displayed on the managementmodule console interface. If you do not keep a record of the console messages before themanagement module resets or reloads, these error messages will be lost.At the first occurrence of an I2C failure, the Global I2C Error Indicator (GIEI) flag severity is set tomajor. The GIEI flag is cleared only when the management module is able to access the samephysical device successfully. The GIEI severity flag is set to minor only if other I2C devices areaccessible. A set of static <strong>and</strong> dynamic Syslog messages are generated when any or all of thefollowing events occur:• When an I2C failure is first detected• When the GIEI severity is changed from major to minor• When the GIEI flag is clearedThese Syslog messages are generated in both the static <strong>and</strong> dynamic sections of the show loggingcomm<strong>and</strong> output. A Syslog message is also sent to the SNMP log server.When the GIEI is set to major, the first Syslog message displayed is an Alert. The following exampleshows an Alert Syslog message where the GIEI is set to major:<strong>Brocade</strong># show loggingSysloglogging: enabled (0 messages dropped, 0 flushes, 1 overruns)Buffer logging: level ACDMEINW, 50 messages loggedlevel code: A=alert C=critical D=debugging M=emergency E=errorI=informational N=notification W=warningStatic 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:21:25:A:System: bad i2c access (GIEI = set), Severity Major, Muxindex 0, Muxtap 4, ID 0x4, Addr0x5, (FANTRAY4)Apr 16 18:21:25:I:System: last good i2c access, Muxindex 0, Muxtap 1, ID0x9, Addr0x1, (SNM1TEMP)Dynamic Log Buffer (50 lines):Apr 16 18:21:25:A:System: bad i2c access (GIEI = set), Severity Major, Muxindex 0, Mux tap 4, ID 0x4, Addr 0x5, (FANTRAY4)Apr 16 18:21:25:I:System: last good i2c access, Mux index 0, Mux tap 1, ID0x9, Addr 0x1, (SNM1TEMP)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%)The Syslog message shows the last successful I2C access by the management module <strong>and</strong> alsocontains the following information about the failed device:• Current state of the GIEI flag• Severity of the failure: major or minor322 <strong>Brocade</strong> <strong>MLX</strong> <strong>Series</strong> <strong>and</strong> <strong>Brocade</strong> <strong>NetIron</strong> <strong>XMR</strong> <strong>Hardware</strong> Installation Guide53-1002373-02

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!