EasyManuals Logo

Foundry Networks FESX User Manual

Foundry Networks FESX
820 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #623 background imageLoading...
Page #623 background image
Configuring BGP4
December 2005 © Foundry Networks, Inc. 21 - 51
The route-type internal | external-type1 | external-type2 parameter applies only to OSPF routes. This
parameter compares the route’s type to the specified value.
The tag <tag-value> parameter compares the route’s tag to the specified value.
Match Examples Using ACLs
The following sections show some detailed examples of how to configure route maps that include match
statements that match on ACLs.
Matching Based on AS-Path ACL
To construct a route map that matches based on AS-path ACL 1, enter the following commands:
FESX424 Router(config)# route-map PathMap permit 1
FESX424 Router(config-routemap PathMap)# match as-path 1
Syntax: match as-path <num>
The <num> parameter specifies an AS-path ACL and can be a number from 1 – 199. You can specify up to five
AS-path ACLs. To configure an AS-path ACL, use the ip as-path access-list command. See “Defining an AS-
Path ACL” on page 21-42.
Matching Based on Community ACL
To construct a route map that matches based on community ACL 1, enter the following commands:
FESX424 Router(config)# ip community-list 1 permit 123:2
FESX424 Router(config)# route-map CommMap permit 1
FESX424 Router(config-routemap CommMap)# match community 1
Syntax: match community <string>
The <string> parameter specifies a community list ACL. To configure a community list ACL, use the ip
community-list command. See “Defining a Community ACL” on page 21-46.
Matching Based on Destination Network
To construct match statements for a route map that match based on destination network, use the following
method. You can use the results of an IP ACL or an IP prefix list as the match condition.
FESX424 Router(config)# route-map NetMap permit 1
FESX424 Router(config-routemap NetMap)# match ip address 1
Syntax: match ip address <name-or-num>
Syntax: match ip address prefix-list <name>
The <name-or-num> parameter with the first command specifies an IP ACL and can be a number from 1 – 199 or
the ACL name if it is a named ACL. To configure an IP ACL, use the ip access-list or access-list command. See
“Software-Based IP Access Control Lists (ACLs)” on page 12-1.
The <name> parameter with the second command specifies an IP prefix list name. To configure an IP prefix list,
see “Defining IP Prefix Lists” on page 21-47.
Matching Based on Next-Hop Router
To construct match statements for a route map that match based on the IP address of the next-hop router, use
either of the following methods. You can use the results of an IP ACL or an IP prefix list as the match condition.
To construct a route map that matches based on the next-hop router, enter commands such as the following:
FESX424 Router(config)# route-map HopMap permit 1
FESX424 Router(config-routemap HopMap)# match ip next-hop 2
Syntax: match ip next-hop <num>
Syntax: match ip next-hop prefix-list <name>
The <num> parameter with the first command specifies an IP ACL and can be a number from 1 – 199 or the ACL
name if it is a named ACL. To configure an IP ACL, use the ip access-list or access-list command. See
“Software-Based IP Access Control Lists (ACLs)” on page 12-1.

Table of Contents

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the Foundry Networks FESX and is the answer not in the manual?

Foundry Networks FESX Specifications

General IconGeneral
BrandFoundry Networks
ModelFESX
CategorySwitch
LanguageEnglish

Related product manuals