HP StorageWorks 2.128 SAN Director Switch - Manual (Page 98)

98 Routing traffic
You must disable the switch before changing the routing policy, and reenable it afterward.
In the following example, the routing policy for a SAN Switch 4/32 is changed from exchange-based to
device-based:
Assigning a static route
A static route can be assigned only when the active routing policy is port-based. When device-based or
exchange-based routing is active, you cannot assign static routes. Thus, the 4/256 SAN Director using
configuration option 5 does not support static routing.
To assign a static route, use the
uRouteConfig
command. To remove a static route, use the
uRouteRemove
command.
NOTE: For the SAN Switch 2/32, Core Switch 2/64, SAN Director 2/128, and 4/256 SAN Director
(using configuration options 1 through 4):
When you issue the
uRouteConfig
command, two similar warning messages might be displayed if a
platform conflict occurs. The first message is displayed when the static routing feature detects the conflict.
The second message is displayed when the DLS feature detects the condition as it tries to rebalance the
route.
A platform conflict occurs if a static route was configured with a destination port that is currently down.
The static route is ignored in this case, in favor of a normal dynamic route. When the configured
destination port comes back up, the system attempts to reestablish the static route, potentially causing a
conflict.
Specifying frame order delivery
The order of delivery of frames is maintained within a switch and determined by the routing policy in
effect. Following are the frame delivery behaviors for each routing policy.
• Port-based routing: All frames received on an ingress port destined for a destination domain are
guaranteed to exit the switch in the same order in which they were received.
• Device-based routing: All frames received on an ingress port between the same two fabric devices are
guaranteed to exit the switch in the same order in which they were received. This policy maintains the
order of frames across exchanges between the fabric devices as well.
• Exchange-based routing: All frames received on an ingress port for a given exchange are guaranteed
to exit the switch in the same order in which they were received. Because different paths are chosen
for different exchanges, this policy does not maintain the order of frames across exchanges.
If even one switch in the fabric delivers out-of-order exchanges, exchanges are then delivered to the target
out-of-order, regardless of the policy configured on other switches in the fabric.
switch:admin> aptpolicy
Current Policy: 3
3: Default Policy
1: Port Based Routing Policy
2: Device Based Routing Policy
3: Exchange Based Routing Policy
switch:admin> switchdisable
switch:admin> aptpolicy 2
Policy updated successfully.
switch:admin> switchenable
switch:admin> aptpolicy
Current Policy: 2