Dell Brocade 5100 Fabric OS v7.0.2 Release Notes v1.0 - Page 14

FOS Upgrade and Downgrade Special Considerations

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

Page 14 highlights

FOS Upgrade and Downgrade Special Considerations The DCX/DCX-4S units running any FOS v6.4.x can be non-disruptively upgraded to FOS v7.0.2. This upgrade is non-disruptive to FC traffic only. When loading FOS v7.0.2 to a DCX chassis with FCOE10-24 blades with Brocade Network Advisor v11.1.1/11.1.1a, there is no warning flagging FCoE traffic disruption. The DCX/DCX-4S units running FOS v6.4.1_fcoe1 can be non-disruptively upgraded to FOS v7.0.2. This upgrade is non-disruptive to both FCoE traffic through FCOE10-24 blades and FC traffic. Non-disruptive upgrade to FOS v7.0.2 on 8G switches is allowed from FOSv6.4.1a or later. Disruptive upgrades to Fabric OS 7.0.2 are allowed and supported from FOS 6.3 (up to a two-level migration) using the optional "-s" parameter with the firmwaredownload command. If there are multiple node EGs (encryption groups) in a fabric, please complete firmwaredownload on one node at a time before downloading on another node. The Brocade 8000 does not support non-disruptive hot code loads (HCL). Upgrading the Brocade 8000 to FOS v7.0 .1 will be disruptive to the I/O through the switch. FC FastWrite , EX_Ports, and TCP byte streaming on FR4-18i must be disabled prior to upgrading to FOS v7.0.2. Failure to do so will cause the upgrade to be blocked. Upgrading a switch currently operating in interopmode 2 or 3 to FOS v7.0.2 is disruptive. The interopmode must be changed to 0 prior to upgrading to FOS v7.0.2, as interopmodes 2 and 3 are not supported on FOS v7.0.2. Changing the interopmode is an offline operation. Fabric OS v7.0.2 Release Notes v1.0 Page 14 of 99

  • 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
Fabric OS v7.0.2 Release Notes v1.0
Page 14 of 99
FOS Upgrade and Downgrade Special Considerations
The DCX/DCX-4S units running any FOS v6.4.x can be non-disruptively upgraded to FOS v7.0.2. This upgrade is
non-disruptive to FC traffic only.
When loading FOS v7.0.2 to a DCX chassis with FCOE10-24 blades with
Brocade Network Advisor v11.1.1/11.1.1a, there is no warning flagging FCoE traffic disruption.
The DCX/DCX-4S units running
FOS v6.4.1_fcoe1 can be non-disruptively upgraded to FOS v7.0.2.
This
upgrade is non-disruptive to both FCoE traffic through FCOE10-24 blades and FC traffic.
Non-disruptive upgrade to FOS v7.0.2 on 8G switches is allowed from FOS
FOS
FOS
FOSv6.4.1
v6.4.1
v6.4.1
v6.4.1a or later.
Disruptive
Disruptive
Disruptive
Disruptive upgrades to Fabric OS 7.0.2 are allowed and supported from FOS 6.3 (up to a two-level migration)
using the optional “-s” parameter with the
firmwaredownload
command.
If there are multiple node EGs (encryption groups) in a fabric, please complete firmwaredownload on one node
at a time before downloading on another node.
The Brocade 8000 does not support non-disruptive hot code loads (HCL).
Upgrading the Brocade 8000 to FOS
v7.0 .1 will be disruptive to the I/O through the switch.
FC FastWrite , EX_Ports, and TCP byte streaming on FR4-18i must be disabled prior to upgrading to FOS v7.0.2.
Failure to do so will cause the upgrade to be blocked.
Upgrading a switch currently operating in interopmode 2 or 3 to FOS v7.0.2 is disruptive.
The interopmode
must be changed to 0 prior to upgrading to FOS v7.0.2, as interopmodes 2 and 3 are not supported on FOS
v7.0.2.
Changing the interopmode is an offline operation.