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

When the GIEI flag is cleared, the first Syslog message in the static of the log is updated

Get Dell PowerConnect B - MLXe 16 PDF manuals and user guides View all Dell PowerConnect B - MLXe 16 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 113 highlights

Managing the device 5 • 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 first Syslog message in the static section of the log is updated to reflect 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 first detected, a second Syslog message is generated containing information about the last successful I2C access before the GIEI error flag 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: PowerConnect# 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 flag is cleared, the first 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 first 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. PowerConnect B-MLXe Hardware Installation Guide 101 53-1002111-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
PowerConnect B-MLXe Hardware Installation Guide
101
53-1002111-01
Managing the device
5
•
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 first Syslog message in the
static section of the log is updated to reflect 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 first detected, a second Syslog message is generated containing information
about the last successful I2C access before the GIEI error flag 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:
When the GIEI flag is cleared, the first 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 first 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.
PowerConnect# 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)