Home » Dell Manuals » Hubs & Switches » Dell PowerConnect B - MLXe 16 » Manual Viewer

Dell PowerConnect B - MLXe 16 Hardware Installation Guide - Page 112

Monitoring I2C failures on management modules, Apr 16 18:21:25:A:System: bad i2c access GIEI = set

View all Dell PowerConnect B - MLXe 16 manuals

Add to My Manuals
Save this manual to your list of manuals

Page 112 highlights

5 Managing the device Monitoring I2C failures on management modules The management module accesses temperature sensors, fan controllers, power supplies, serial PROMs, and other devices are all accessed through the I2C serial bus. When I2C devices are inaccessible, generic (and uninformative) error messages are displayed on the management module console interface. If you do not keep a record of the console messages before the management 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 to major. The GIEI flag is cleared only when the management module is able to access the same physical device successfully. The GIEI severity flag is set to minor only if other I2C devices are accessible. A set of static and dynamic Syslog messages are generated when any or all of the following events occur: • When an I2C failure is first detected • When the GIEI severity is changed from major to minor • When the GIEI flag is cleared These Syslog messages are generated in both the static and dynamic sections of the show logging command 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 example shows an Alert Syslog message where the GIEI is set to major: PowerConnect# show logging Sysloglogging: 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:21:25:A:System: bad i2c access (GIEI = set), Severity Major, Mux index 0, Muxtap 4, ID 0x4, Addr0x5, (FANTRAY4) Apr 16 18:21:25:I:System: last good i2c access, Muxindex 0, Muxtap 1, ID 0x9, Addr0x1, (SNM1TEMP) Dynamic Log Buffer (50 lines): 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:25:I:System: last good i2c access, Mux index 0, Mux tap 1, ID 0x9, 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 and also contains the following information about the failed device: • Current state of the GIEI flag • Severity of the failure: major or minor • MUX index number: - The MUX index is always zero in 4-, 8-, and 16-slot MLX devices 100 PowerConnect B-MLXe Hardware Installation Guide 53-1002111-01

Section	Page
Audience	9
How this document is organized	9
Supported hardware	10
What’s new in this document	10
Document conventions	10
Text formatting	10
Command syntax conventions	10
Command examples	11
Notes, cautions, and danger notices	11
Notice to the reader	11
Getting technical help or reporting errors	12
Contacting Dell	12
Product Overview	13
Dell router overview	13
Router applications	13
Hardware features	13
PowerConnect B-MLXe routers	13
Router modules	18
Management modules	18
Interface modules	20
Switch fabric modules	27
High-speed switch fabric modules	29
Power supplies	29
Rack mounting brackets	30
Cooling system for PowerConnect B-MLXe routers	30
NIBI-16-FAN-EXH-A high-speed fan assemblies	32
Rack mount kit	33
Supported software features	33
Installing a PowerConnect B-MLXe Core Router	35
Installation precautions	35
General precautions	35
Power precautions	36
Installing a PowerConnect B-MLXe-4 router	37
Preparing the installation site	38
Unpacking a PowerConnect B-MLXe-4 router	38
Installing a PowerConnect B-MLXe-4 router in a rack or cabinet	38
Installing PowerConnect B-MLXe-4 modules	46
Installing power supplies in a PowerConnect B-MLXe-4 router	50
Connecting AC power	51
Final steps	52
Installing a PowerConnect B-MLXe-8 router	52
Preparing the installation site	52
Unpacking a PowerConnect B-MLXe-8 router	52
Installing a PowerConnect B-MLXe-8 router in a rack	53
Mounting your device in a cabinet	55
Installing PowerConnect B-MLXe-8 modules	60
Installing power supplies in the PowerConnect B-MLXe-8 router	63
Connecting AC power	64
Final steps	65
Installing a PowerConnect B-MLXe-16 router	65
Preparing the installation site	65
Unpacking a PowerConnect B-MLXe-16 router	66
Installing a PowerConnect B-MLXe-16 router in a rack	66
Installing modules in a PowerConnect B-MLXe 16-slot router	74
Installing power supplies in a PowerConnect B-MLXe-16 router	78
Final steps	80
Attaching a management station	80
Attaching a PC or terminal to the console port or Ethernet port	80
Activating the power source	81
Verifying proper operation	82
Observing the LEDs	82
Displaying the module status	84
Using the Dell Structured Cabling Components	87
Cable cinch overview	87
MRJ21 procedures	88
Cable cinch with two mRJ21 cables	88
Cable cinch with three mRJ21 cables	89
Cable cinch with four mRJ21 cables	90
Cable cinch with five mRJ21 cables	91
Cable cinch with six mRJ21 cables	92
Cable cinch with seven mRJ21 cables	93
Cable cinch with eight mRJ21 cables	94
RJ45 procedures	95
Cable cinch with one group of RJ45 cables	95
Cable cinch with two groups of RJ45 cables	96
Cable cinch with three groups of RJ45 cables	97
Cable cinch with four groups of RJ45 cables	98
Cable cinch with five groups of RJ45 cables	99
Cable cinch with six groups of RJ45 cables	100
Cable cinch with seven groups of RJ45 cables	101
Cable cinch with eight groups of RJ45 cables	102
Connecting a Router to a Network Device	103
Assigning permanent passwords	103
Configuring IP addresses	104
Support of subnet masks	104
Assigning an IP address to a management interface	105
Assigning IP addresses to an interface, virtual interface, or loopback interface	106
Enabling and disabling the interfaces	107
Understanding management port functions	107
Connecting the router to a network device	107
Installing a fiber-optic transceiver	108
Cabling a fiber-optic transceiver	108
Cleaning fiber-optic ports and connectors	108
Troubleshooting network connections	109
Testing network connectivity	109
Pinging an IP address	109
Tracing a route	110
Managing Routers and Modules	111
Managing the device	111
Disabling and re-enabling power to interface modules	111
Monitoring I2C failures on management modules	112
Displaying device status and temperature readings	114
Displaying the Syslog configuration and static and dynamic buffers	116
Managing switch fabric modules	118
Forcing HSF modules to operate in normal mode	118
Managing the cooling system	119
Configuring the cooling system	119
Manually setting the fan speed	123
Monitoring the cooling system	123
Temperature log reduction	124
Managing interface modules	125
Configuring interface module boot parameters	125
Changing priority of slots for interface modules	130
Disabling and re-enabling power to interface modules	131
Enabling and disabling management module CPU usage calculations	132
Displaying CPU usage	132
Displaying management module CPU usage	134
Removing MAC address entries	135
Upgrading Software Images and Configuration Files	137
Upgrading Software Images and Configuration Files	137
Important software upgrade considerations	138
General upgrade considerations	139
Special upgrade information for PowerConnect B-MLXe routers	139
Interface module software upgrade considerations	139
Important memory requirement information	140
CLI upgrade commands for R05.1.00	142
Software upgrade procedures	142
Determining current software image versions	143
Upgrading the combined IronWare Application Image on management modules	143
Upgrading the monitor image on a management module	143
Upgrading the boot image on a management module	144
Upgrading the boot and monitor images on interface modules	144
Upgrading interface modules using the combined FPGA image	145
Additional upgrade steps	146
Upgrading MBRIDGE images on management modules	146
Upgrading individual FPGA images on interface modules	147
Rebooting the management module	148
Performing a Hitless OS upgrade	149
Performing an image coherence check	149
Performing a coherence check without a reload	150
Displaying image versions	150
Using the show flash command	150
Configurations conditions specific to NI-MLX-1Gx48-T modules	157
Loading and saving configuration files	158
Configuring file size for startup and running configuration	158
Configuration buffers	159
Replacing the startup configuration with the running configuration	160
Replacing the startup configuration with the running configuration	160
Retaining the current startup configuration	160
Copying a configuration file to or from a TFTP server	161
Making local copies of the startup configuration file	161
Hitless OS upgrade	162
Dynamic configuration loading	164
Loading configuration information into the running-config file	166
Using SNMP to save and load configuration information	166
Erasing image and configuration files	167
File synchronization	167
File synchronization between active and standby management modules	167
File synchronization between management and interface modules	168
Scheduling a system reload	169
Reloading at a specific time	170
Reloading after a specific amount of time	170
Displaying the amount of time before a scheduled reload	170
Canceling a scheduled reload	170
Diagnostic error codes and remedies for TFTP transfers	170
Router Maintenance	173
Hardware maintenance schedule	173
Replacing a management module	173
Replacing an interface module	173
Removing and replacing an interface module	174
Replacing a switch fabric module	174
Replacing a fiber-optic transceiver	174
Cabling a fiber-optic transceiver	175
Replacing a power supply	175
Determining which power supply failed	175
Setting the threshold for power supply monitoring	176
Clearing power supply failure timestamps	176
Displaying power supply monitoring timestamps	177
Enabling a power supply shutdown	177
Powering on the power supply through the CLI	177
Replacing a power supply	178
Replacing fan assemblies	179
Replacing fan assemblies in a 16-slot router	179
Replacing the fan tray assembly in 4-slot and 8-slot routers	182
Replacing the air filters	184
Hardware Specifications	187
Hardware specifications for PowerConnect B-MLXe routers	187
Power specifications	187
Physical dimensions for PowerConnect B-MLXe routers	189
Operating environment specifications for PowerConnect B-MLXe routers	189
Storage environment specifications for PowerConnect B-MLXe routers	189
Safety agency approvals	189
Electromagnetic approvals	189
Port specifications for all router models	190
Console port pin assignments	190
Management port pin assignments	191
Power cords	191
Regulatory Statements	195
U.S.A.	195
Industry Canada statement	195
Europe and Australia	195
Germany	195
Japan	196
Power cords (Japan Denan)	196
China	197
Korea	197
Russia	197
Caution and Danger Notices	199
Cautions	199

Match case Limit results 1 per page

100

PowerConnect B-MLXe Hardware Installation Guide

53-1002111-01

Managing the device

Monitoring I2C failures on management modules

The management module accesses temperature sensors, fan controllers, power supplies, serial

PROMs, and other devices are all accessed through the I2C serial bus. When I2C devices are

inaccessible, generic (and uninformative) error messages are displayed on the management

module console interface. If you do not keep a record of the console messages before the

management 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 to

major. The GIEI flag is cleared only when the management module is able to access the same

physical device successfully. The GIEI severity flag is set to minor only if other I2C devices are

accessible. A set of static and dynamic Syslog messages are generated when any or all of the

following events occur:

•

When an I2C failure is first detected

•

When the GIEI severity is changed from major to minor

•

When the GIEI flag is cleared

These Syslog messages are generated in both the static and dynamic sections of the

show logging

command 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 example

shows an Alert Syslog message where the GIEI is set to major:

The Syslog message shows the last successful I2C access by the management module and also

contains the following information about the failed device:

•

Current state of the GIEI flag

•

Severity of the failure: major or minor

•

MUX index number:

The MUX index is always zero in 4-, 8-, and 16-slot MLX devices

PowerConnect# show logging

Sysloglogging: 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:21:25:A:System: bad i2c access (GIEI = set), Severity Major

, Mux

index 0, Muxtap 4, ID 0x4, Addr0x5, (FANTRAY4)

Apr 16 18:21:25:I:System: last good i2c access, Muxindex 0, Muxtap 1, ID

0x9, Addr0x1, (SNM1TEMP)

Dynamic Log Buffer (50 lines):

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:25:I:System: last good i2c access, Mux index 0, Mux tap 1, ID

0x9, 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%)