HP StorageWorks 8/80 HP StorageWorks Fabric OS 6.2 administrator guide (5697-0 - Page 290

Instead, you can use the traffic isolation feature to create a dedicated path for interswitch traffic. See "Traffic Isolation Routing" on page 339 for information about this feature. Assigning a static route 1. Connect to the switch and log in as admin. 2. Enter the uRouteConfig command. urouteconfig in_area domain out_area where: in_area domain out_area The input port to be statically routed, either an F_Port or an E_Port. The destination domain. The output port to which traffic is forwarded. If the out_area port is associated with a valid minimum-cost path, all frames coming in from the in_area port addressed to domain are forwarded through the out_area port. If the out_area port is not associated with such a path, the routing assignment is not immediately affected by this command. However, the static route is remembered so that it can be enforced if this port becomes part of a valid path in the future. See the Fabric OS Command Reference for more details on the uRouteConfig command. Removing a static route 1. Connect to the switch and log in as admin. 2. Enter the uRouteRemove command. urouteremove in_area domain where: in_area domain The input port of the static route to remove, either an F_Port or an E_Port. The destination domain of the static route to remove. See the Fabric OS Command Reference for more details on the uRouteRemove command. Frame order delivery The order of delivery of frames is maintained within a switch and determined by the routing policy in effect. The frame delivery behaviors for each routing policy are: • Port-based routing All frames received on an incoming port destined for a destination domain are guaranteed to exit the switch in the same order in which they were received. • Exchange-based routing All frames received on an incoming 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. NOTE: If even one switch in the fabric delivers out-of-order exchanges, exchanges are delivered to the target out-of-order, regardless of the policy configured on other switches in the fabric. IMPORTANT: Some devices do not tolerate out-of-order exchanges; in such cases, use the port-based routing policy. 288 Routing traffic