HP Brocade 8/12c Brocade Fabric OS Troubleshooting and Diagnostics Guide - Sup - Page 71

Firmware Download Errors, In this Blade troubleshooting tips - brocade 8510 icl

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 71 highlights

Firmware Download Errors Chapter 5 In this chapter •Blade troubleshooting tips 51 •Firmware download issues 52 •Troubleshooting the firmwareDownload command 55 •USB error handling 55 •Considerations for downgrading firmware 56 Blade troubleshooting tips This chapter refers to the following specific types of blades inserted into either the Brocade DCX, DCX 8510 family, and DCX-4S enterprise-class platforms: • FC blades or port blades contain only Fibre Channel ports: Brocade FC10-6, and FC8-16/32/48/64. • AP blades contain extra processors and some have specialized ports: Brocade FR4-18i, FCOE10-24, and FX8-24. • CP blades have a control processor (CP) used to control the entire switch; they can be inserted only into slots 6 and 7 on the Brocade DCX, and slots 4 and 5 on the Brocade DCX-4S. • CORE8 and CR4S-8 core blades provide ICL functionality between two Brocade DCX Backbones. CORE8 blades can be inserted only into slots 5 and 8 on the Brocade DCX. CR4S-8 blades can be inserted only into slots 3 and 6 on the Brocade DCX-4S. Typically, issues detected during firmware download to AP blades do not require recovery actions on your part. If you experience frequent failovers between CPs that have different versions of firmware, then you may notice multiple blade firmware downloads and a longer startup time. ATTENTION Brocade DCX Director with FC8-16/32/48 blades: If you are running Fabric v6.1.0, then you cannot downgrade to pre-Fabric OS v6.0.0 versions as they are not supported on this director. Symptom Relocation of internal image times out on CP8 core blade. Probable cause and recommended action This can be caused by issues in the co-CPU. If this happens, the firmware download process synchronizes the partitions in the main-CPU and co-CPU by starting a firmware commit operation. Wait at least 15 minutes for the commit operation to complete, issue the firmwareShow command to verify the partitions are synchronized, and reissue the firmwareDownload command. If the problem persists, you must contact the switch service provider. Fabric OS Troubleshooting and Diagnostics Guide 51 53-1002150-02

  • 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
Fabric OS Troubleshooting and Diagnostics Guide
51
53-1002150-02
Chapter
5
Firmware Download Errors
In this chapter
•
Blade troubleshooting tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
•
Firmware download issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
52
•
Troubleshooting the firmwareDownload command . . . . . . . . . . . . . . . . . . .
55
•
USB error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55
•
Considerations for downgrading firmware. . . . . . . . . . . . . . . . . . . . . . . . . . .
56
Blade troubleshooting tips
This chapter refers to the following specific types of blades inserted into either the Brocade DCX,
DCX 8510 family, and DCX-4S enterprise-class platforms:
•
FC blades or port blades contain only Fibre Channel ports: Brocade FC10-6, and
FC8-16/32/48/64.
•
AP blades contain extra processors and some have specialized ports: Brocade FR4-18i,
FCOE10-24, and FX8-24.
•
CP blades have a control processor (CP) used to control the entire switch; they can be inserted
only into slots 6 and 7 on the Brocade DCX, and slots 4 and 5 on the Brocade DCX-4S.
•
CORE8 and CR4S-8 core blades provide ICL functionality between two Brocade DCX
Backbones. CORE8 blades can be inserted only into slots 5 and 8 on the Brocade DCX. CR4S-8
blades can be inserted only into slots 3 and 6 on the Brocade DCX-4S.
Typically, issues detected during firmware download to AP blades do not require recovery actions
on your part.
If you experience frequent failovers between CPs that have different versions of firmware, then you
may notice multiple blade firmware downloads and a longer startup time.
ATTENTION
Brocade DCX Director with FC8-16/32/48 blades:
If you are running Fabric v6.1.0, then you cannot
downgrade to pre-Fabric OS v6.0.0 versions as they are not supported on this director.
Symptom
Relocation of internal image times out on CP8 core blade.
Probable cause and recommended action
This can be caused by issues in the co-CPU. If this happens, the firmware download process
synchronizes the partitions in the main-CPU and co-CPU by starting a firmware commit operation.
Wait at least 15 minutes for the commit operation to complete, issue the
firmwareShow
command
to verify the partitions are synchronized, and reissue the
firmwareDownload
command. If the
problem persists, you must contact the switch service provider.