• Route Access Lists - The basic building block of a routing policy. Route access lists filter routes based upon a specified range of IP addresses.
• IP Prefix Lists - A more advanced element of a routing policy. An IP Prefix list filters routes based upon IP prefixes.
• AS Path Access Lists - A basic building block used for Border Gateway Protocol (BGP) routing. These lists filter Autonomous System (AS) paths.
• Route Maps - Route-maps provide detailed control over routes during route selection or route advertisement by a routing protocol, and in route redistribution between routing protocols. For this level 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.context <context_name>route-access-list standard identifier { permit | deny } {<ip_address> <wildcard_mask> | any | host <network_address> }[ local ]< host_name > #show ip interfacecontext <context_name>ip route { < ip_address | ip_mask > | < ip_addr_mask_combo > } { next-hop } < next_hop_address > | < egress_name > [ precedence ] < precedence > [ cost ] < cost >context context_nameno ip route { < ip_address > < ip_mask > | < ip_addr_mask_combo > } < next_hop_address > < egress_name > [ precedence < precedence > ] [ cost < cost > ]Important: During system task recovery, it is possible for a dynamically-learned forwarding entry to incorrectly remain in the system forwarding table if that forwarding entry has been removed from the dynamic routing protocol during the recovery.
Important: The default cost for OSPF on the system is 10. To change the cost, refer to the ip ospf cost command in the Ethernet Interface Configuration mode. For detailed information on this command refer to the Cisco ASR 5000 Series Command Line Interface Reference.
This example shows sample output of the command, show ip route.[local]host_name# show ip route
![]() |
Cisco Systems Inc. |
Tel: 408-526-4000 |
Fax: 408-527-0883 |