Foundry Configuration Guide for the FESX, FSX, and FWSX
21 - 48 © Foundry Networks, Inc. December 2005
The <name-or-num> parameter specifies the name or number of a standard, extended, or named ACL.
The in | out parameter specifies whether the distribute list applies to inbound or outbound routes:
• in – controls the routes the Layer 3 Switch will accept from the neighbor.
• out – controls the routes sent to the neighbor.
NOTE: The command syntax shown above is new. However, the neighbor <ip-addr> distribute-list in | out
<num> command (where the direction is specified before the filter number) is the same as in earlier software
releases. Use the new syntax when you are using an IP ACL with the distribute list. Use the old syntax when you
are using a BGP4 address filter with the distribute list.
Defining Route Maps
A route map is a named set of match conditions and parameter settings that the router can use to modify route
attributes and to control redistribution of the routes into other protocols. A route map consists of a sequence of up
to 50 instances. If you think of a route map as a table, an instance is a row in that table. The router evaluates a
route according to a route map’s instances in ascending numerical order. The route is first compared against
instance 1, then against instance 2, and so on. As soon as a match is found, the router stops evaluating the route
against the route map instances.
Route maps can contain match statements and set statements. Each route map contains a “permit” or “deny”
action for routes that match the match statements.
• If the route map contains a permit action, a route that matches a match statement is permitted; otherwise, the
route is denied.
• If the route map contains a deny action, a route that matches a match statement is denied.
• If a route does not match any match statements in the route map, the route is denied. This is the default
action. To change the default action, configure the last match statement in the last instance of the route map
to “permit any any”.
• If there is no match statement, the software considers the route to be a match.
• For route maps that contain address filters, AS-path filters, or community filters, if the action specified by a
filter conflicts with the action specified by the route map, the route map’s action takes precedence over the
individual filter’s action.
If the route map contains set statements, routes that are permitted by the route map’s match statements are
modified according to the set statements.
Match statements compare the route against one or more of the following:
• The route’s BGP4 MED (metric)
• A sequence of AS-path filters
• A sequence of community filters
• A sequence of address filters
• The IP address of the next hop router
• The route’s tag
• For OSPF routes only, the route’s type (internal, external type-1, or external type-2)
• An AS-path ACL
• A community ACL
• An IP prefix list
•An IP ACL
To Next Page
Loading...
Need help?
General
