|
|
This chapter describes the function and displays the syntax for IP routing protocol-independent commands. For more information about defaults and usage guidelines, see the corresponding chapter of the Network Protocols Command Reference, Part 1.
To set the time period during which the authentication key on a key chain is received as valid, use the accept-lifetime key chain key configuration command. To revert to the default value, use the no form of this command.
accept-lifetime start-time {infinite | end-time | duration seconds}| start-time | Beginning time that the key specified by the key command is valid to be received. The syntax can be either of the following:
hh:mm:ss Month date year hh:mm:ss date Month year hh--hours mm--minutes ss--seconds date--date (1-31) Month--first three letters of the month year--year (four digits) The default start time and the earliest acceptable date is January 1, 1993. |
| infinite | Key is valid to be received from the start-time on. |
| end-time | Key is valid to be received from the start-time until end-time. The end-time must be after the start-time. The syntax is the same as that for start-time. The default end time is an infinite time period. |
| duration seconds | Length of time (in seconds) that the key is valid to be received. |
To remove one or more routes from the IP routing table, use the clear ip route EXEC command.
clear ip route {network [mask] | *}| network | Network or subnet address to remove. |
| mask | (Optional) Network mask associated with the IP address you wish to remove. |
| * | Removes all entries. |
To define an administrative distance, use the distance router configuration command. To remove a distance definition, use the no form of this command.
distance weight [address mask [access-list-number | name]] [ip]| weight | Administrative distance. This can be an integer from 10 to 255. (The values 0 to 9 are reserved for internal use.) Used alone, the argument weight specifies a default administrative distance that the Cisco IOS software uses when no other specification exists for a routing information source. Routes with a distance of 255 are not installed in the routing table. |
| address | (Optional) IP address in four-part, dotted notation. |
| mask | (Optional) IP address mask in four-part, dotted-decimal format. A bit set to 1 in the mask argument instructs the software to ignore the corresponding bit in the address value. |
| access-list-number | name | (Optional) Number or name of a standard IP access list to be applied to incoming routing updates. |
| ip | (Optional) IP-derived routes for IS-IS. It can be applied independently for IP routes and ISO CLNS routes. |
To filter networks received in updates, use the distribute-list in router configuration command. To change or cancel the filter, use the no form of this command.
distribute-list {access-list-number | name} in [type number]| access-list-number | name | Standard IP access list number or name. The list defines which networks are to be received and which are to be suppressed in routing updates. |
| in | Applies the access list to incoming routing updates. |
| type | (Optional) Interface type. |
| number | (Optional) Interface number on which the access list should be applied to incoming updates. If no interface is specified, the access list will be applied to all incoming updates. |
To suppress networks from being advertised in updates, use the distribute-list out router configuration command. To cancel this function, use the no form of this command.
distribute-list {access-list-number | name} out [interface-name | routing-process || access-list-number | name | Standard IP access list number or name. The list defines which networks are to be sent and which are to be suppressed in routing updates. |
| out | Applies the access list to outgoing routing updates. |
| interface-name | (Optional) Name of a particular interface. |
| routing-process | (Optional) Name of a particular routing process, or the keyword static or connected. |
| autonomous-system-number | (Optional) Autonomous system number. |
To select a network as a candidate route for computing the gateway of last resort, use the ip default-network global configuration command. To remove a route, use the no form of this command.
ip default-network network-number| network-number | Number of the network. |
To identify a route map to use for local policy routing, use the ip local policy route-map global configuration command. To disable local policy routing, use the no form of this command.
ip local policy route-map map-tag| map-tag | Name of the route map to use for local policy routing. The name must match a map-tag specified by a route-map command. |
To identify a route map to use for policy routing on an interface, use the ip policy route-map interface configuration command. To disable policy routing on the interface, use the no form of this command.
ip policy route-map map-tag| map-tag | Name of the route map to use for policy routing. Must match a map-tag specified by a route-map command. |
To establish static routes, use the ip route global configuration command. To remove static routes, use the no form of this command.
ip route prefix mask {address | interface} [distance] [tag tag] [permanent]| prefix | IP route prefix for the destination. |
| mask | Prefix mask for the destination. |
| address | IP address of the next hop that can be used to reach that network. |
| interface | Network interface to use. |
| distance | (Optional) An administrative distance. |
| tag tag | (Optional) Tag value that can be used as a "match" value for controlling redistribution via route maps. |
| permanent | (Optional) Specifies that the route will not be removed, even if the interface shuts down. |
To identify an authentication key on a key chain, use the key key chain configuration command. To remove the key from the key chain, use the no form of this command.
key number| number | Identification number of an authentication key on a key chain. The range of keys is 0 to 2147483647. The key identification numbers need not be consecutive. |
To enable authentication for routing protocols, identify a group of authentication keys by using the key chain global configuration command. To remove the key chain, use the no form of this command.
key chain name-of-chain| name-of-chain | Name of a key chain. A key chain must have at least one key and can have up to 2147483647 keys. |
To specify the authentication string for a key, use the key-string key chain key configuration command. To remove the authentication string, use the no form of this command.
key-string text| text | Authentication string that must be sent and received in the packets using the routing protocol being authenticated. The string can contain from 1 to 80 uppercase and lowercase alphanumeric characters, except that the first character cannot be a number. |
To distribute any routes that have their next hop out one of the interfaces specified, use the match interface route-map configuration command. To remove the match interface entry, use the no form of this command.
match interface type number [...type number]| type | Interface type. |
| number | Interface number. |
To distribute any routes that have a destination network number address that is permitted by a standard or extended access list, or to perform policy routing on packets, use the match ip address route-map configuration command. To remove the match ip address entry, use the no form of this command.
match ip address {access-list-number | name} [...access-list-number | name]| access-list-number | name | Number or name of a standard or extended access list. It can be an integer from 1 to 199. |
To redistribute any routes that have a next-hop router address passed by one of the access lists specified, use the match ip next-hop route-map configuration command. To remove the next-hop entry, use the no form of this command.
match ip next-hop {access-list-number | name}[...access-list-number | name]| access-list-number | name | Number or name of a standard or extended access list. It can be an integer from 1 to 199. |
To redistribute routes that have been advertised by routers and access servers at the address specified by the access lists, use the match ip route-source route-map configuration command. To remove the route-source entry, use the no form of this command.
match ip route-source {access-list-number | name}[...access-list-number | name]| access-list-number | name | Number or name of a standard or extended access list. It can be an integer from 1 to 199. |
To base policy routing on the Level 3 length of a packet, use the match length route-map configuration command. To remove the entry, use the no form of this command.
match length min max| min | Minimum Level 3 length of the packet, inclusive, allowed for a match. Range is 0 to 0x7FFFFFFF. |
| max | Maximum Level 3 length of the packet, inclusive, allowed for a match. Range is 0 to 0x7FFFFFFF. |
To redistribute routes with the metric specified, use the match metric route-map configuration command. To remove the entry, use the no form of this command.
match metric metric-value| metric-value | Route metric, which can be an IGRP five-part metric. It is a metric value from 0 to 4294967295. |
To redistribute routes of the specified type, use the match route-type route-map configuration command. To remove the route-type entry, use the no form of this command.
match route-type {local | internal | external [type-1 | type-2] | level-1 | level-2}| local | Locally generated BGP routes. |
| internal | OSPF intra-area and interarea routes or enhanced IGRP internal routes. |
| external [type-1 | type-2] | OSPF external routes, or enhanced IGRP external routes. For OSPF, external type-1 matches only Type 1 external routes and external type-2 matches only Type 2 external routes. |
| level-1 | IS-IS Level 1 routes. |
| level-2 | IS-IS Level 2 routes. |
To redistribute routes in the routing table that match the specified tags, use the match tag route-map configuration command. To remove the tag entry, use the no form of this command.
match tag tag-value [...tag-value]| tag-value | List of one or more route tag values. Each can be an integer from 0 to 4294967295. |
To control the maximum number of parallel routes an IP routing protocol can support, use the maximum-paths router configuration command. To restore the default value, use the no form of this command.
maximum-paths maximum| maximum | Maximum number of parallel routes an IP routing protocol installs in a routing table, in the range 1 to 6. |
To disable sending routing updates on an interface, use the passive-interface router configuration command. To reenable the sending of routing updates, use the no form of this command.
passive-interface type number| type | Interface type. |
| number | Interface number. |
To redistribute routes from one routing domain into another routing domain, use the redistribute router configuration command. To disable redistribution, use the no form of this command.
redistribute protocol [process-id] {level-1 | level-1-2 | level-2} [metric metric-value]| protocol | Source protocol from which routes are being redistributed. It can be one of the following keywords: bgp, egp, igrp, isis, ospf, static [ip], connected, and rip.
The keyword static [ip] is used to redistribute IP static routes. The optional ip keyword is used when redistributing into IS-IS. The keyword connected refers to routes which are established automatically by virtue of having enabled IP on an interface. For routing protocols such as OSPF and IS-IS, these routes will be redistributed as external to the autonomous system. |
| process-id | (Optional) For bgp, egp, or igrp, this is an autonomous system number, which is a 16-bit decimal number. For isis, this is an optional tag that defines a meaningful name for a routing process. You can specify only one IS-IS process per router. Creating a name for a routing process means that you use names when configuring routing. For ospf, this is an appropriate OSPF process ID from which routes are to be redistributed. This identifies the routing process. This value takes the form of a nonzero decimal number. For rip, no process-id value is needed. |
| level-1 | For IS-IS, Level 1 routes are redistributed into other IP routing protocols independently. |
| level-1-2 | For IS-IS, both Level 1 and Level 2 routes are redistributed into other IP routing protocols. |
| level-2 | For IS-IS, Level 2 routes are redistributed into other IP routing protocols independently. |
| metric metric-value | (Optional) Metric used for the redistributed route. If a value is not specified for this option, and no value is specified using the default-metric command, the default metric value is 0. Use a value consistent with the destination protocol. |
| metric-type type-value | (Optional) For OSPF, the external link type associated with the default route advertised into the OSPF routing domain. It can be one of two values:
1--Type 1 external route 2--Type 2 external route If a metric-type is not specified, the Cisco IOS software adopts a Type 2 external route. For IS-IS, it can be one of two values: internal--IS-IS metric which is < 63. external--IS-IS metric which is > 64 < 128. The default is internal. |
| match {internal | external 1 | external 2} | (Optional) For OPSF, the criteria by which OSPF routes are redistributed into other routing domains. It an be one of the following:
internal--Routes that are internal to a specific autonomous system. external 1--Routes that are external to the autonomous system, but are imported into OSPF as type 1 external route. external 2--Routes that are external to the autonomous system, but are imported into OSPF as type 2 external route. |
| tag tag-value | (Optional) 32-bit decimal value attached to each external route. This is not used by the OSPF protocol itself. It may be used to communicate information between Autonomous System Boundary Routers. If none is specified, then the remote autonomous system number is used for routes from BGP and EGP; for other protocols, zero (0) is used. |
| route-map | (Optional) Route map should be interrogated to filter the importation of routes from this source routing protocol to the current routing protocol. If not specified, all routes are redistributed. If this keyword is specified, but no route map tags are listed, no routes will be imported. |
| map-tag | (Optional) Identifier of a configured route map. |
| weight weight | (Optional) Network weight when redistributing into BGP. An integer from 0 to 65535. |
| subnets | (Optional) For redistributing routes into OSPF, the scope of redistribution for the specified protocol. |
To define the conditions for redistributing routes from one routing protocol into another, or to enable policy routing, use the route-map global configuration command and the match and set route-map configuration commands. To delete an entry, use the no form of this command.
route-map map-tag [permit | deny] [sequence-number]| map-tag | Defines a meaningful name for the route map. The redistribute router configuration command uses this name to reference this route map. Multiple route maps may share the same map tag name. |
| permit | (Optional) If the match criteria are met for this route map, and permit is specified, the route is redistributed as controlled by the set actions. In the case of policy routing, the packet is policy routed.
If the match criteria are not met, and permit is specified, the next route map with the same map tag is tested. If a route passes none of the match criteria for the set of route maps sharing the same name, it is not redistributed by that set. The permit keyword is the default. |
| deny | (Optional) If the match criteria are met for the route map, and deny is specified, the route is not redistributed or in the case of policy routing, the packet is not policy routed, and no further route maps sharing the same map tag name will be examined. If the packet is not policy-routed, it reverts to the normal forwarding algorithm. |
| sequence-number | (Optional) Number that indicates the position a new route map is to have in the list of route maps already configured with the same name. If given with the no form of this command, it specifies the position of the route map that should be deleted. |
To set the time period during which an authentication key on a key chain is valid to be sent, use the send-lifetime key chain key configuration command. To revert to the default value, use the no form of this command.
send-lifetime start-time {infinite | end-time | duration seconds}| start-time | Beginning time that the key specified by the key command is valid to be sent. The syntax can be either of the following:
hh:mm:ss Month date year hh:mm:ss date Month year hh--hours mm--minutes ss--seconds date--date (1-31) Month--first three letters of the month year--year (four digits) The default start time and the earliest acceptable date is January 1, 1993. |
| infinite | Key is valid to be sent from the start-time on. |
| end-time | Key is valid to be sent from the start-time until end-time. The syntax is the same as that for start-time. The end-time must be after the start-time. The default end time is an infinite time period. |
| duration seconds | Length of time in seconds that the key is valid to be sent. |
To automatically compute the tag value, use the set automatic-tag route-map configuration command. To disable this function, use the no form of this command.
set automatic-tagTo indicate where to output packets that pass a match clause of a route map for policy routing and have no explicit route to the destination, use the set default interface route-map configuration command. To delete an entry, use the no form of this command.
set default interface type number [... type number]| type | Interface type, used with the interface number, to which packets are output. |
| number | Interface number, used with the interface type, to which packets are output. |
To indicate where to output packets that pass a match clause of route map for policy routing, use the set interface route-map configuration command. To delete an entry, use the no form of this command.
set interface type number [...type number]| type | Interface type, used with the interface number, to which packets are output. |
| number | Interface number, used with the interface type, to which packets are output. |
To indicate where to output packets that pass a match clause of a route map for policy routing and for which the Cisco IOS software has no explicit route to a destination, use the set ip default next-hop route-map configuration command. To delete an entry, use the no form of this command.
set ip default next-hop ip-address [...ip-address]| ip-address | IP address of the next hop to which packets are output. It need not be an adjacent router. |
To indicate where to output packets that pass a match clause of a route map for policy routing, use the set ip next-hop route-map configuration command. To delete an entry, use the no form of this command.
set ip next-hop ip-address [...ip-address]| ip-address | IP address of the next hop to which packets are output. It need not be an adjacent router. |
To indicate where to import routes, use the set level route-map configuration command. To delete an entry, use the no form of this command.
set level {level-1 | level-2 | level-1-2 | stub-area | backbone}| level-1 | Imports routes into a Level-1 area. |
| level-2 | Imports routes into Level-2 subdomain. |
| level-1-2 | Imports routes into Level-1 and Level-2. |
| stub-area | Imports routes into OSPF NSSA area. |
| backbone | Imports routes into OSPF backbone area. |
To specify a preference value for the autonomous system path, use the set local-preference route-map configuration command. To delete an entry, use the no form of this command.
set local-preference value| value | Preference value. An integer from 0 to 4294967295. |
To set the metric value for a routing protocol, use the set metric route-map configuration command. To return to the default metric value, use the no form of this command.
set metric metric-value| metric-value | Metric value; an integer from -294967295 to 294967295. This argument applies to all routing protocols except IGRP and IP Enhanced IGRP. |
To set the metric type for the destination routing protocol, use the set metric-type route-map configuration command. To return to the default, use the no form of this command.
set metric-type {internal | external | type-1 | type-2}| internal | IS-IS internal metric. |
| external | IS-IS external metric. |
| type-1 | OSPF external type 1 metric. |
| type-2 | OSPF external type 2 metric. |
To specify the address of the next hop, use the set next-hop route-map configuration command. To delete an entry, use the no form of this command.
set next-hop next-hop| next-hop | IP address of the next hop router. |
To set the BGP origin code, use the set origin route-map configuration command. To delete an entry, use the no form of this command.
set origin {igp | egp autonomous-system | incomplete}| igp | Remote IGP. |
| egp | Local EGP. |
| autonomous-system | Remote autonomous system. This is an integer from 0 to 65535. |
| incomplete | Unknown heritage. |
To set a tag value of the destination routing protocol, use the set tag route-map configuration command. To delete the entry, use the no form of this command.
set tag tag-value| tag-value | Name for the tag. Integer from 0 to 4294967295. |
To display the cache entries in the policy route-cache, use the show ip cache policy EXEC command.
show ip cache policyTo display the route map used for local policy routing, if any, use the show ip local policy EXEC command.
show ip local policyTo display the route map used for policy routing, use the show ip policy EXEC command.
show ip policyTo display the parameters and current state of the active routing protocol process, use the show ip protocols EXEC command.
show ip protocolsUse the show ip route EXEC command to display the current state of the routing table.
show ip route [address [mask] [longer-prefixes]] | [protocol [process-id]]| address | (Optional) Address about which routing information should be displayed. |
| mask | (Optional) Argument for a subnet mask. |
| longer-prefixes | (Optional) The address and mask pair becomes a prefix and any routes that match that prefix are displayed. |
| protocol | (Optional) Name of a routing protocol; or the keyword connected, static, or summary. If you specify a routing protocol, use one of the following keywords: bgp, egp, eigrp, hello, igrp, isis, ospf, or rip. |
| process-id | (Optional) Number used to identify a process of the specified protocol. |
To display the current state of the routing table, use the show ip route summary EXEC command.
show ip route summaryTo display information about supernets, use the show ip route supernets-only privileged EXEC command.
show ip route supernets-onlyTo display authentication key information, use the show key chain EXEC command.
show key chain [name-of-chain]| name-of-chain | (Optional) Name of the key chain to display, as named in the key chain command. |
To display configured route-maps, use the show route-map EXEC command.
show route-map [map-name]| map-name | (Optional) Name of a specific route-map. |
|
|