HP Brocade 8/12c Brocade Fabric OS Troubleshooting and Diagnostics Guide v6.2. - Page 29

Checking fan components, Checking the switch temperature, Fabric OS Message Reference

Page 29 highlights

Switch message logs 2 Symptom I2C bus errors are appearing in the switch log. Probable cause and recommended action I2C bus errors generally indicate defective hardware or poorly seated devices or blades; the specific item is listed in the error message. See the Fabric OS Message Reference for information specific to the error that was received. Some Chip-Port (CPT) and Environmental Monitor (EM) messages contain I2C-related information. If the I2C message does not indicate the specific hardware that may be failing, begin debugging the hardware, as this is the most likely cause. The next sections provide procedures for debugging the hardware. Symptom Core file or FFDC warning messages appear on the serial console or in the system log. Probable cause and recommended action Issue the supportSave command. The messages can be dismissed by issuing the supportSave -R command after all data is confirmed to be collected properly. Error example: *** CORE FILES WARNING (10/22/08 - 05:00:01 ) *** 3416 KBytes in 1 file(s) use "supportsave" command to upload Checking fan components 1. Log in to the switch as user. 2. Enter the fanShow command. 3. Check the fan status and speed output. OK absent below minimum above minimum unknown faulty Fan is functioning correctly. Fan is not present. Fan is present but rotating too slowly or stopped. Fan is rotating too quickly. Unknown fan unit installed. Fan has exceeded hardware tolerance and has stopped. In this case, the last known fan speed is displayed. The output from this command varies depending on switch type and number of fans present. Refer to the appropriate hardware reference manual for details regarding the fan status. You may first consider re-seating the fan (unplug it and plug it back in). Checking the switch temperature 1. Log in to the switch as user. 2. Enter the tempShow command. 3. Check the temperature output. Refer to the hardware reference manual for your switch to determine the normal temperature range. Fabric OS Troubleshooting and Diagnostics Guide 13 53-1001187-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

Fabric OS Troubleshooting and Diagnostics Guide
13
53-1001187-01
Switch message logs
2
Symptom
I2C bus errors are appearing in the switch log.
Probable cause and recommended action
I
2
C bus errors generally indicate defective hardware or poorly seated devices or blades; the specific
item is listed in the error message. See the
Fabric OS Message Reference
for information specific
to the error that was received. Some Chip-Port (CPT) and Environmental Monitor (EM) messages
contain I
2
C-related information.
If the I
2
C message does not indicate the specific hardware that may be failing, begin debugging the
hardware, as this is the most likely cause. The next sections provide procedures for debugging the
hardware.
Symptom
Core file or FFDC warning messages appear on the serial console or in the system log.
Probable cause and recommended action
Issue the supportSave command. The messages can be dismissed by issuing the supportSave -R
command after all data is confirmed to be collected properly.
Error example:
*** CORE FILES WARNING (10/22/08 - 05:00:01 ) ***
3416 KBytes in 1 file(s)
use "supportsave" command to upload
Checking fan components
1.
Log in to the switch as user.
2.
Enter the
fanShow
command.
3.
Check the fan status and speed output.
The output from this command varies depending on switch type and number of fans present.
Refer to the appropriate hardware reference manual for details regarding the fan status. You
may first consider re-seating the fan (unplug it and plug it back in).
Checking the switch temperature
1.
Log in to the switch as user.
2.
Enter the
tempShow
command.
3.
Check the temperature output.
Refer to the hardware reference manual for your switch to determine the normal temperature
range.
OK
Fan is functioning correctly.
absent
Fan is not present.
below minimum
Fan is present but rotating too slowly or stopped.
above minimum
Fan is rotating too quickly.
unknown
Unknown fan unit installed.
faulty
Fan has exceeded hardware tolerance and has stopped. In this case, the last known
fan speed is displayed.