HP Brocade 8/12c Fabric OS Troubleshooting and Diagnostics Guide v6.4.0 (53-10 - Page 27

Switch boot issues, Rolling Reboot Detection

Get HP Brocade 8/12c PDF manuals and user guides View all HP Brocade 8/12c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 27 highlights

Switch boot issues 2 Symptom 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. 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 Switch boot issues Symptom The enterprise-class platform model rebooted again after an initial bootup. Probable cause and recommended action This issue can occur during an enterprise-class platform boot up with two CPs. If any failure occurs on active CP, before the standby CP is fully functional and has obtained HA sync, the Standby CP may not be able to take on the active role to perform failover successfully. In this case, both CPs will reboot to recover from the failure. Rolling Reboot Detection A rolling reboot occurs when a switch or enterprise-class platform has continuously experienced unexpected reboots. This behavior is continuous until the rolling reboot is detected by the system. Once the Rolling Reboot Detection (RRD) occurs, the switch is put into a stable state so that a minimal supportSave can be collected and sent to your service support provider for analysis. Not every reboot activates the Rolling Reboot Detection feature. ATTENTION If a rolling reboot is caused by a panic inside Linux kernel, then the RRD feature will not be activated. Reboot classification There are two types of reboots that occur on a switch and enterprise-class platform, expected and unexpected. Expected reboots occur when the reboots are initialized by commands, these types of reboots are ignored by the RRD feature. They include the following: Fabric OS Troubleshooting and Diagnostics Guide 13 53-1001769-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
Fabric OS Troubleshooting and Diagnostics Guide
13
53-1001769-01
Switch boot issues
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
Switch boot issues
Symptom
The enterprise-class platform model rebooted again after an initial bootup.
Probable cause and recommended action
This issue can occur during an enterprise-class platform boot up with two CPs. If any failure occurs
on active CP, before the standby CP is fully functional and has obtained HA sync, the Standby CP
may not be able to take on the active role to perform failover successfully.
In this case, both CPs will reboot to recover from the failure.
Rolling Reboot Detection
A rolling reboot occurs when a switch or enterprise-class platform has continuously experienced
unexpected reboots. This behavior is continuous until the rolling reboot is detected by the system.
Once the Rolling Reboot Detection (RRD) occurs, the switch is put into a stable state so that a
minimal
supportSave
can be collected and sent to your service support provider for analysis. Not
every reboot activates the Rolling Reboot Detection feature.
ATTENTION
If a rolling reboot is caused by a panic inside Linux kernel, then the RRD feature will not be activated.
Reboot classification
There are two types of reboots that occur on a switch and enterprise-class platform, expected and
unexpected. Expected reboots occur when the reboots are initialized by commands, these types of
reboots are ignored by the RRD feature. They include the following: