Creating Ip Prefix Lists; Creating Route Access Lists; Creating As Path Access Lists - Cisco ASR 5500 Administration Manual

Creating IP Prefix Lists

Creating IP Prefix Lists
Use the following configuration example to create IP Prefix Lists:
config
context context_name
ip prefix-list name list_name { deny | permit } network_address/net_mask
Notes:
• Set the IP prefix list to deny, permit or match any prefix.
• IPv4 dotted-decimal and IPv6 colon-separated-hexadecimal addresses are supported.
• Save your configuration as described in the Verifying and Saving Your Configuration chapter.

Creating Route Access Lists

Use the following procedure to create a Route Access List:
config
context context_name
route-access-list
standard identifier { permit | deny ) { ip_address
wildcard_mask | any
Notes:
• A maximum of 64 access lists are supported per context.
• A maximum of 16 entries can defined for each route-access-list.
• Save your configuration as described in the Verifying and Saving Your Configuration chapter.

Creating AS Path Access Lists

Use the following procedure to create an AS Path Access List:
config
context context_name
Notes:
• Save your configuration as described in the Verifying and Saving Your Configuration chapter.
ASR 5500 System Administration Guide, StarOS Release 19
208
of control you use IP Prefix Lists, Route Access Lists and AS Path Access Lists to specify IP addresses,
address ranges, and Autonomous System paths.
route-access-list { extended identifier } { deny | permit } [ ip address ip_address ]
route-access-list named list_name { deny
network_address }
|
ip as-path access-list list_name [ { deny | permit } reg_expr ]
permit } { ip_address/mask | any } [ exact-match ]
|
Routing