
192 Installing and maintaining firmware
Execute the
chassisConfig
command with a supported option (1, 2, or 5 for SAN Director 2/128 and
1 or 5 for 4/256 SAN Director), and then retry the firmware download operation. The supported options
are described briefly below:
Message
Cannot download to 5.1 because Device Based routing policy is not supported by 5.1. Use
aptPolicy
to
change the routing policy before proceeding.
Probable Cause and Recommended Action
The firmware download operation was attempting to upgrade a system to Fabric OS v5.1.0 with
device-based routing policy selected. Device-based routing policy is not supported in firmware v5.1.0, so
the firmware download operation was aborted.
Disable the switch and change the routing policy selection to one of the following supported selections on
firmware v5.1.0 using the
aptPolicy
command, and then retry the firmware download operation. The
supported selections include:
option 1 One 128-port switch with the following configuration:
FC2-16 (blade ID 4), FC4-16 (blade ID 17) on slots 1–4 and 7–10;
CP2 (blade ID 5), CP4 (blade ID 16) on slots 5–6
option 2 Two 64-port switches with the following configuration:
FC2-16 (blade ID 4) on slots 1–4 and 7–10; CP2 (blade ID 5) on slots 5–6)
option 5 One 256-port switch with the following configuration:
FC4-16 (blade ID 17), FC4-32 (blade ID 18) on slots 1–4 and 7–10;
CP4 (blade ID 16) on slots 5–6
policy 1 Port-based routing policy
With this policy, the path chosen for an ingress frame is based on:
1. Ingress port on which the frame was received
2. Destination domain for the frame
The chosen path remains the same if Dynamic Load Sharing (DLS feature is not
enabled. If DLS is enabled, then a different path might be chosen on a fabric event.
Refer to the
dlsSet
command for the definition of a fabric event.
This policy may provide better ISL utilization when there is little or no oversubscription
of the ISLs.
NOTE:
Static routes are supported only with this policy.
policy 3 Exchange-based routing policy
With this policy, the path chosen for an ingress frame is based on:
1. Ingress port on which the frame was received
2. FC address of the SID for this frame
3. FC address of the DID for this frame
4. FC Originator Exchange ID (OXID) for this frame
This policy allows for optimal utilization of the available paths as I/O traffic between
different (SID, DID, OXID) pairs can use different paths. All frames received on a
ingress port with the same (SID, DID, OXID) parameters takes the same path unless
there is a fabric event. Refer to the
dlsSet
command for the definition of a fabric
event.
This policy does not support static routes. DLS always is enabled and the DLS setting
cannot change with this policy.
Summary of Contents for AA979A - StorageWorks SAN Switch 2/8V
Page 1: ...HP StorageWorks Fabric OS 5 3 x administrator guide Part number 5697 0244 November 2009 ...
Page 16: ...16 ...
Page 20: ...18 ...
Page 24: ...24 Introducing Fabric OS CLI procedures ...
Page 116: ...118 Maintaining configurations ...
Page 170: ...172 Managing administrative domains ...
Page 200: ...202 Installing and maintaining firmware ...
Page 222: ...224 Routing traffic ...
Page 274: ...286 Administering FICON fabrics ...
Page 294: ...306 Working with diagnostic features ...
Page 350: ...362 Administering Extended Fabrics ...
Page 438: ...440 Configuring the PID format ...
Page 444: ...446 Configuring McData Open Fabric mode ...
Page 450: ...452 Understanding legacy password behaviour ...