118 Fabric OS Administrator’s Guide
53-1002745-02
Routing policies
4
Configuring a link through a gateway
1. Connect to the switch at one end of the gateway and log in using an account assigned to the
admin role.
2. Enter the portCfgIISLMode command.
3. Repeat steps 1 and 2 for any additional ports that are connected to the gateway.
4. Repeat this procedure on the switch at the other end of the gateway.
Example of enabling a gateway link on slot 2, port 3
ecp:admin> portcfgislmode 2/3, 1
Committing configuration...done.
ISL R_RDY Mode is enabled for port 3. Please make sure the PID
formats are consistent across the entire fabric.
Routing policies
By default, all routing protocols place their routes into a routing table. You can control the routes
that a protocol places into each table and the routes from that table that the protocol advertises by
defining one or more routing policies and then applying them to the specific routing protocol.
The routing policy is responsible for selecting a route based on one of two user-selected routing
policies:
• Port-based routing
• Exchange-based routing
Notes
• On the Brocade 300, 5100, 5300, 5410, 5430, 5450, 5460, 5470, 5480, 6505, 6510, 6520,
7800, 8000, and VA-40FC switches, and also the Brocade DCX and DCX 8510 Backbone
families, routing is handled by the FSPF protocol and either the port-based or exchange-based
routing policy.
• Each switch can have its own routing policy and different policies can exist in the same fabric.
For most configurations, the default routing policy is optimal and provides the best performance. You
should change the routing policy only if there is a significant performance issue, or a particular fabric
configuration or application requires it.
To Next Page
Loading...
Need help?
General