Brocade Multi-Service IronWare Routing Configuration Guide (Supporting R05.6.00) - Manual (Page 412)

384 Multi-Service IronWare Routing Configuration Guide
53-1003033-02
Configuration considerations
TABLE 63 IPv4 Route-map handling
TABLE 64 IPv6 Route-map handling
Configuration considerations
These are the things to consider while configuring the Brocade device:
• Import configuration commands allow specifying a non-existing source VRF. Routes will be
imported dynamically when the source VRF is created.
• If the route-map is empty, then no course of actions are applied while importing the routes.
• If you change the configuration of a route-map, then all the VRFs which are configured to use
this route-map will be processed again.
Tie breaker rules
The rules in the sequence below apply to break the tie when the same routes are imported from
multiple VRFs including the local route:
• If routes are originated from different protocols, then the protocol with the best administrative
distance will be used to break the tie.
• If the routes’ origin (protocol) are the same, then the metric value will be used to break the tie.
Attributes used for filtering routes Attributes set using a route map
IP address (Prefix list, Access list)
Next hop (Prefix list, Access list) Metric value
Metric value Nexthop
Tag type Distance
Route type Tag
BGP attributes (AS path, Community, Ext
community access list)
Interface type
Protocol type
Attributes used for filtering routes Attributes set using a route map
IP address (Prefix list)
Next hop (Prefix list) Metric value
Metric value Nexthop
Tag type Distance
Route type Tag
BGP attributes (AS path, Community, Ext
community access list)
Interface type
Protocol type