Dell Brocade G620 Brocade 8.0.1 Fabric OS Troubleshooting and Diagnostics Guid - Page 26

Restrictions, Software Fault: Kernel Panic

Get Dell Brocade G620 PDF manuals and user guides View all Dell Brocade G620 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 26 highlights

General Troubleshooting ∙ haFailover ∙ fastBoot ∙ firmwareDownload The RRD feature is activated and halts rebooting when an unexpected reboot reason is shown continuously in the reboot history within a certain period of time. For example, the switch re-boots five times in 300 seconds. The period of time depends on the switch. The following reboots are considered unexpected reboots: ∙ Reset A reset reboot may be caused by one of the following: - Power-cycle of the switch or CP - Linux reboot command - Hardware watchdog timeout - Heartbeat loss-related reboot ∙ Software Fault: Kernel Panic - If the system detects an internal fatal error from which it cannot safely recover, it outputs an error message to the console, dumps a stack trace for debugging, and then performs an automatic reboot. - After a kernel panic, the system may not have enough time to write the reboot reason, causing the reboot reason to be empty. This is treated as a reset case. ∙ Software fault - Software Watchdog - ASSERT ∙ Software recovery failure This is an HA bootup-related issue and happens when a switch is unable to recover to a stable state. The HASM log contains more details and specific information on this type of failure, such as one of the following: - Failover recovery failed: Occurs when failover recovery fails and the CP must reboot. - Failover when standby CP unready: Occurs when the active CP must fail over, but the standby CP is not ready to take over mastership. - Failover when LS trans incomplete: Takes place when a logical switch transaction is incomplete. ∙ Software bootup failure - System bring up timed out: The CP failed to come up within the time allotted. - LS configuration timed out and failed: The logical switch configuration failed and timed out. After RRD is activated, the admin-level permission is required to log in. Enter the supportShow or supportSave command to collect a limited amount of data to resolve the issue. Restrictions The following restrictions are applicable on the RRD feature: ∙ RRD works only on CFOS-based systems and is not available on AP blades. ∙ If FIPS mode is enabled, then the RRD feature works in record-only mode. ∙ RRD only works during the 30 minutes immediately after the switch boots. If the switch does not reboot for 30 minutes, then RRD is deactivated. Brocade Fabric OS Troubleshooting and Diagnostics Guide 26 53-1004126-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
∙
haFailover
∙
fastBoot
∙
firmwareDownload
The RRD feature is activated and halts rebooting when an unexpected reboot reason is shown continuously in the reboot history within a
certain period of time. For example, the switch re-boots five times in 300 seconds. The period of time depends on the switch. The
following reboots are considered unexpected reboots:
∙
Reset
A reset reboot may be caused by one of the following:
–
Power-cycle of the switch or CP
–
Linux reboot command
–
Hardware watchdog timeout
–
Heartbeat loss-related reboot
∙
Software Fault: Kernel Panic
–
If the system detects an internal fatal error from which it cannot safely recover, it outputs an error message to the console,
dumps a stack trace for debugging, and then performs an automatic reboot.
–
After a kernel panic, the system may not have enough time to write the reboot reason, causing the reboot reason to be
empty. This is treated as a reset case.
∙
Software fault
–
Software Watchdog
–
ASSERT
∙
Software recovery failure
This is an HA bootup-related issue and happens when a switch is unable to recover to a stable state. The HASM log contains
more details and specific information on this type of failure, such as one of the following:
–
Failover recovery failed: Occurs when failover recovery fails and the CP must reboot.
–
Failover when standby CP unready: Occurs when the active CP must fail over, but the standby CP is not ready to take over
mastership.
–
Failover when LS trans incomplete: Takes place when a logical switch transaction is incomplete.
∙
Software bootup failure
–
System bring up timed out: The CP failed to come up within the time allotted.
–
LS configuration timed out and failed: The logical switch configuration failed and timed out.
After RRD is activated, the admin-level permission is required to log in. Enter the
supportShow
or
supportSave
command to collect a
limited amount of data to resolve the issue.
Restrictions
The following restrictions are applicable on the RRD feature:
∙
RRD works only on CFOS-based systems and is not available on AP blades.
∙
If FIPS mode is enabled, then the RRD feature works in
record-only
mode.
∙
RRD only works during the 30 minutes immediately after the switch boots. If the switch does not reboot for 30 minutes, then
RRD is deactivated.
General Troubleshooting
Brocade Fabric OS Troubleshooting and Diagnostics Guide
26
53-1004126-01