Creating Route Maps
Use the following configuration example to create a Route Map:
config
context context_name
route-map map_name { deny | permit } seq_number
Notes:
•
Use the
match
and
set
commands in Route Map Configuration mode to configure the route map. Refer
to the
Command Line Interface Reference
for more information on these commands.
•
Save your configuration as described in the
Verifying and Saving Your Configuration
chapter.
Sample Configuration
The example below shows a configuration that creates two route access lists, applies them to a route map,
and uses that route map for a BGP router neighbor.
The example below shows a configuration that creates two route access lists, applies them to a route map,
and uses that route map for a BGP router neighbor.
config
context isp1
route-access-list named RACLin1a permit 88.151.1.0/30
route-access-list named RACLin1a permit 88.151.1.4/30
route-access-list named RACLany permit any
route-map RMnet1 deny 100
match ip address route-access-list RACLin 1 a
#exit
route-map RMnet1 deny 200
match ip address route-access-list RACLin 1 b
#exit
route-map RMnet1 permit 1000
match ip address route-access-list RACLany
#exit
router bgp 1
neighbor 152.20.1.99 as-path 101
neighbor 152.20.1.99 route-map RMnet1
Static Routing
The system supports static network route configuration on a per context basis. Define network routes by
specifying the:
•
IP address and mask for the route
•
Name of the interface in the current context that the route must use
•
Next hop IP address
On the ASR 5500, static routes with IPv6 prefix lengths less than /12 and between the range of /64 and
/128 are not supported.
Important
ASR 5500 System Administration Guide, StarOS Release 21.5
209
Routing
Creating Route Maps
