|
|
Cisco's implementation of the Internet Protocol (IP) suite provides all major services contained in the Transmission Control Protocol/IP (TCP/IP) specifications.
Use the commands in this chapter to configure and monitor the IP routing protocols. For IP routing protocol configuration information and examples, refer to the "Configuring IP Routing Protocols" chapter of the Access and Communication Servers Configuration Guide.
Use the aggregate-address router configuration command to create an aggregate entry in a BGP routing table. Use the no form of this command to disable this feature.
aggregate-address address mask [as-set] [summary-only] [suppress-map map-name]| address | Aggregate address. |
| mask | Aggregate mask. |
| as-set | (Optional) Generates autonomous system set path information. |
| summary-only | (Optional) Filters more specific routes from updates. |
| suppress-map map-name | (Optional) Name of route-map to suppress. |
| advertise-map map-name | (Optional) Name of route map used to select the routes to create AS-SET origin communities. |
| attribute-map map-name | (Optional) Name of route map used to set the attribute of the aggregate route. |
Disabled
Router configuration
You can implement aggregate routing in BGP either by redistributing an aggregate route into BGP or by using this conditional aggregate routing feature.
Using the aggregate-address command with no arguments will create an aggregate entry in the BGP routing table if there are any more-specific routes available that fall in the specified range. The aggregate route will be advertised as coming from your autonomous system and has the atomic aggregate attribute set to show that information might be missing. (By default, the atomic aggregate attribute is set unless you specify the as-set keyword in the aggregate-address command.)
Using the as-set keyword creates an aggregate entry using the same rules that the command follows without this keyword, but the path advertised for this route will be an AS_SET consisting of all elements contained in all paths that are being summarized. Do not use this form of aggregate-address when aggregating many paths, because this route must be continually withdrawn and re-updated as autonomous system path reachability information for the summarized routes changes.
Using the summary-only keyword not only creates the aggregate route (for example, 193.*.*.*) but will also suppress advertisements of more specific routes to all neighbors. If you only want to suppress advertisements to certain neighbors, you may use the neighbor distribute-list command, with caution. If a more-specific route leaks out, all BGP speakers will prefer that route over the less- specific aggregate you are generating (using longest-match routing).
Using the suppress-map keyword creates the aggregate route but suppresses advertisement of specified route maps. You can use the match clauses of route maps to selectively suppress some more specific routes of the aggregate and leave others unsuppressed. IP access lists and autonomous system path access lists match clauses are supported.
In the following example, an aggregate address is created. The path advertised for this route will be an AS_SET consisting of all elements contained in all paths that are being summarized.
router bgp 5aggregate-address 192.168.0.0 255.0.0.0 as-set
match as-path
match ip address
route-map
Use the area authentication router configuration command to enable authentication for an OSPF area. Use the no form of this command with the authentication keyword to remove the area's authentication specification. Use the command no area area-id (with no other keywords) to remove the specified area from the access server's configuration.
area area-id authentication [message-digest]Type 0 authentication (no authentication)
Router configuration
Specifying authentication for an area sets the authentication to Type 1 (simple password) as specified in RFC 1247. If this command is not included in the configuration file, authentication of Type 0 (no authentication) is assumed.
The authentication type must be the same for all access servers in an area. The authentication password for all OSPF access servers on a network must be the same if they are to communicate with each other via OSPF. Use the ip ospf authentication-key interface configuration command to specify this password.
If you enable MD5 authentication with the message-digest keyword, you must configure a password with the ip ospf message-digest-key command.
To remove the area's authentication specification, use the no form of this command with the authentication keyword. To remove the specified area from the router's configuration, use the command no area area-id (with no other keywords).
The following example mandates authentication for areas 0 and 10.0.0.0 of OSPF routing process 201. Authentication keys are also provided.
interface ethernet 0 ip address 172.19.251.201 255.255.255.0 ip ospf authentication-key adcdefgh ! interface ethernet 1 ip address 10.56.0.201 255.255.0.0 ip ospf authentication-key ijklmnop ! router ospf 201 network 10.0.0.0 0.255.255.255 area 10.0.0.0 network 172.19.0.0 0.0.255.255 area 0 area 10.0.0.0 authentication area 0 authentication
area default-cost
area stub
ip ospf authentication-key
Use the area default-cost router configuration command to specify a cost for the default summary route sent into a stub area. Use the no form of this command to remove the assigned default route cost.
area area-id default-cost cost| area-id | Identifier for the stub area. The identifier can be specified as either a decimal value or as an IP address. |
| cost | Cost for the default summary route used for a stub area. The acceptable value is a 24-bit number. |
Cost of 1
Router configuration
This command is used only on an Area Border Router (ABR) attached to a stub area.
There are two stub area router configuration commands: the stub and default-cost options of the area command. In all access servers attached to the stub area, the area should be configured as a stub area using the stub option of the area command. Use the default-cost option only on an ABR attached to the stub area. The default-cost option provides the metric for the summary default route generated by the ABR into the stub area.
The following example assigns a default-cost of 20 to stub network 10.0.0.0:
interface ethernet 0 ip address 10.56.0.201 255.255.0.0 ! router ospf 201 network 10.0.0.0 0.255.255.255 area 10.0.0.0 area 10.0.0.0 stub area 10.0.0.0 default-cost 20
area authentication
area stub
To configure the IS-IS area authentication password, use the area-password router configuration command. To disable the password, use the no form of this command.
area-password password| password | Password you assign. |
No area password is defined.
Router configuration
This password is inserted in Level 1 (station router level) link state PDUs (LSPs), complete sequence number PDUs (CSNPs), and partial sequence number PDUs (PSNP).
The following example assigns an area authentication password:
router isisarea-password angel
Use the area range router configuration command to consolidate and summarize routes at an area boundary. Use the no form of this command to disable this function for the specified area.
area area-id range address mask| area-id | Identifier of the area about which routes are to be summarized. It can be specified as either a decimal value or as an IP address. |
| address | IP address. |
| mask | IP mask. |
Disabled
Router configuration
This command is only used with access servers acting as Area Border Routers (ABRs). It is used to consolidate or summarize routes for an area. The result is that a single summary route is advertised to other areas by the ABR. Routing information is condensed at area boundaries. External to the area, a single route is advertised for each address range. This is called route summarization.
Multiple area router configuration commands specifying the range option can be configured. Thus, OSPF can summarize addresses for many different sets of address ranges.
The following example specifies one summary route to be advertised by the access server acting as an ABR to other areas for all subnets on network 10.0.0.0 and for all hosts on network 192.168.110.0:
interface ethernet 0 ip address 192.168.110.201 255.255.255.0 ! interface ethernet 1 ip address 10.56.0.201 255.255.0.0 ! router ospf 201 network 10.0.0.0 0.255.255.255 area 10.0.0.0 network 192.168.110.0 0.0.0.255 area 0 area 10.0.0.0 range 10.0.0.0 255.0.0.0 area 0 range 192.168.110.0 255.255.255.0
Use the area stub router configuration command to define an area as a stub area. Use the no form of this command to disable this function for the specified area.
area area-id stub| area-id | Identifier for the stub area. The identifier can be either a decimal value or an IP address. |
| no-summary | (Optional) Prevents an Area Border Router from sending summary link advertisements into the stub area. |
No stub area is defined.
Router configuration
This command must be configured on all access servers in the stub area. Use the area router configuration command with the default-cost option to specify the cost of a default internal access server sent into a stub area by an access server acting as an Area Border Router (ABR).
There are two stub area router configuration commands: the stub and default-cost options of the area router configuration command. In all access servers attached to the stub area, the area should be configured as a stub area using the stub option of the area command. Use the default-cost option only on an ABR attached to the stub area. The default-cost option provides the metric for the summary default route generated by the Area Border Router (ABR) into the stub area.
The following example assigns a default cost of 20 to stub network 10.0.0.0:
interface ethernet 0 ip address 10.56.0.201 255.255.0.0 ! router ospf 201 network 10.0.0.0 0.255.255.255 area 10.0.0.0 area 10.0.0.0 stub area 10.0.0.0 default-cost 20
area authentication
area default-cost
To define an OSPF virtual link, use the area virtual-link router configuration command with the optional parameters. To remove a virtual link, use the no form of this command.
area area-id virtual-link router-id [hello-interval seconds] [retransmit-interval seconds]| area-id | Area ID assigned to the transit area for the virtual link. This can be either a decimal value or a valid IP address. There is no default. |
| router-id | Router ID associated with the virtual link neighbor. The router ID appears in the show ip ospf display. It is internally derived by each access server from the access server's interface IP addresses. This value must be entered in the format of an IP address. There is no default. |
| hello-interval seconds | (Optional) Time in seconds between the Hello packets that the router sends on an interface. Unsigned integer value to be advertised in the router's Hello packets. The value must be the same for all routers attached to a common network. The default is 10 seconds. |
| retransmit-interval seconds | (Optional) Time in seconds between link state advertisement retransmissions for adjacencies belonging to the interface. Expected round-trip delay between any two routers on the attached network. The value must be greater than the expected round-trip delay. The default is 5 seconds. |
| transmit-delay seconds | (Optional) Estimated time in seconds it takes to transmit a link state update packet on the interface. Integer value that must be greater than zero. Link state advertisements in the update packet have their age incremented by this amount before transmission. The default value is 1 second. |
| dead-interval seconds | (Optional) Time in seconds that a router's Hello packets are not seen before its neighbors declare the router down. Unsigned integer value. The default is four times the Hello interval, or 40 seconds. As with the Hello interval, this value must be the same for all routers attached to a common network. |
| authentication-key key | (Optional) Password to be used by neighboring routers. Any continuous string of characters that you can enter from the keyboard up to 8 bytes long. This string acts as a key that will allow the authentication procedure to generate or verify the authentication field in the OSPF header. This key is inserted directly into the OSPF header when originating routing protocol packets. A separate password can be assigned to each network on a per-interface basis. All neighboring routers on the same network must have the same password to be able to route OSPF traffic. The password is encrypted in the configuration file if the service password-encryption command is enabled. There is no default value. |
| message-digest-key keyid md5 key | (Optional) Key identifier and password to be used by neighboring routers and this router for MD5 authentication. The keyid is a number in the range 1 through 255. The key is an alphanumeric string of up to 16 characters. All neighboring routers on the same network must have the same key identifier and key to be able to route OSPF traffic. There is no default value. |
area-id: No area ID is predefined.
router-id: No router ID is predefined.
hello-interval seconds: 10 seconds
retransmit-interval seconds: 10 seconds
transmit-delay seconds: 1 second
dead-interval seconds: 40 seconds
authentication-key password: No password is predefined.
message-digest-key keyid md5 key: No key is predefined.
Router configuration
In OSPF, all areas must be connected to a backbone area. If the connection to the backbone is lost, it can be repaired by establishing a virtual link.
The smaller the Hello interval, the faster topological changes will be detected, but more routing traffic will ensue.
The setting of the retransmit interval should be conservative, or needless retransmissions will result. The value should be larger for serial lines and virtual links.
The transmit delay value should take into account the transmission and propagation delays for the interface.
An access server will use the specified authentication key only when authentication is enabled for the backbone with the area area-id authentication router configuration command.
The two authentication schemes, simple text and MD5 authentication, are mutually exclusive. You can specify one or the other or neither. Any keywords and arguments you specify after authentication-key key or message-digest-key keyid md5 key are ignored. Therefore, specify any optional arguments before such a keyword-argument combination.
The following example establishes a virtual link with default values for all optional parameters:
router ospf 201 network 10.0.0.0 0.255.255.255 area 10.0.0.0 area 10.0.0.0 virtual-link 36.3.4.5
The following example establishes a virtual link with MD5 authentication:
router ospf 201 network 10.0.0.0 0.255.255.255 area 10.0.0.0 area 10.0.0.0 virtual-link 10.3.4.5 message-digest-key 3 md5 sa5721bk47
A dagger (+) indicates that the command is documented in another chapter.
area authentication
service password-encryption +
show ip ospf
Use the autonomous-system global configuration command to specify the local autonomous system that the access server resides in for EGP. Use the no form of this command to remove the autonomous system number.
autonomous-system local-as| local-as | Local autonomous system number to which the access server belongs |
No local autonomous system is specified.
Global configuration
Before you can set up EGP routing, you must specify an autonomous system number. The local autonomous system number will be included in EGP messages sent by the access server.
The following sample configuration specifies an autonomous system number of 110:
autonomous-system 110
To restore the default behavior of automatic summarization of subnet routes into network-level routes, use the use the auto-summary router configuration command. To disable this feature, use the no form of this command.
auto-summaryThis command has no arguments or keywords.
Enabled
Router configuration
By default, BGP does not accept subnets redistributed from IGP. To advertise and carry subnet routes in BGP, use an explicit network command or the no auto-summary command. If you disable auto-summarization and have not entered a network command, you will not advertise network routes for networks with subnet routes unless they contain a summary route.
IP Enhanced IGRP summary routes are given an administrative distance value of 5. You cannot configure this value.
In the following example, network numbers are not summarized automatically:
router bgp 6 no auto-summary
The following example disables automatic summarization for router process eigrp 109:
router eigrp 109 no auto-summary
To allow the comparison of the Multi Exit Discriminator (MED) for paths from neighbors in different autonomous systems, use the bgp always-compare-med router configuration command. To disallow the comparison, use the no form of this command.
bgp always-compare-medThis command has no arguments or keywords.
The router does not compare MEDs for paths from neighbors in different autonomous systems.
Router configuration
The MED is one of the parameters that is considered when selecting the best path among many alternative paths. The path with a lower MED is preferred over a path with a higher MED.
By default, during the best path selection process, MED comparision is done only among paths from the same autonomous system. This command changes the default behavior by allowing comparision of MEDs among paths regardless of the autonomous system from which the paths are received.
In the following example, the BGP speaker in autonomous system 100 is configured to compare MEDs among alternative paths, regardless of the autonomous system from which the paths are received:
router bgp 109 bgp always-compare-med
To specify a BGP confederation identifier, use the bgp confederation identifier router configuration command. To remove the confederation identifier, use the no form of this command.
bgp confederation identifier autonomous-system| autonomous-system | Autonomous system number that internally includes multiple autonomous systems. |
No confederation identifier is configured.
Router configuration
Another way to reduce the IBGP mesh is to divide an autonomous system into multiple autonomous systems and group them into a single confederation. Each autonomous system is fully meshed within itself, and has a few connections to another autonomous system in the same confederation. Even though the peers in different autonomous systems have EBGP sessions, they exchange routing information as if they are IBGP peers. Specifically, the next-hop and local preference information is preserved. This enables to you to retain a single Interior Gateway Protocol (IGP) for all of the autonomous systems. To the outside world, the confederation looks like a single autonomous system.
In the following example, the autonomous system is divided into autonomous systems 4001, 4002, 4003, 4004, 4005, 4006, and 4007 and identified by the confederation identifier 5. Neighbor 1.2.3.4 is someone inside your routing domain confederation. Neighbor 3.4.5.6 is someone outside your routing domain confederation. To the outside world, there appears to be a single autonomous system with the number 5.
router bgp 4001 bgp confederation identifier 5 bgp confederation peers 4002 4003 4004 4005 4006 4007 neighbor 1.2.3.4 remote-as 4002 neighbor 3.4.5.6 remote-as 510
To configure the autonomous systems that belong to the confederation, use the bgp confederation peers router configuration command. To remove an autonomous system from the confederation, use the no form of this command.
bgp confederation peers autonomous-system [autonomous-system]| autonomous-system | Autonomous system number. |
No confederation peers are configured.
Router configuration
The autonomous systems specified in this command are visible internally to a confederation. Each autonomous system is fully meshed within itself. The bgp confederation identifier command specifies the confederation that the autonomous systems belong to.
The following example specifies that autonomous systems 1090, 1091, 1092, and 1093 belong to a single confederation:
router bgp 1090 bgp confederation peers 1091 1092 1093
Use the bgp default local-preference router configuration command to change the default local preference value of 100. Use the no form of this command to revert to the default setting.
bgp default local-preference value| value | Local preference value. Higher is more preferred. Integer from 0 through 4294967295. |
Local preference value of 100
Router configuration
Generally, the default value of 100 allows you to easily define a particular path as less preferable than paths with no local preference attribute. The preference is sent to all access servers in the local autonomous system.
In the following example, the default local preference value is raised from the default of 100 to 200:
router bgp 200 bgp default local-preference 200
Use the bgp fast-external-fallover router configuration command to immediately reset the BGP sessions of any directly adjacent external peers if the link used to reach them goes down. Use the no form of this command to disable this feature.
bgp fast-external-falloverThis command has no arguments or keywords.
Enabled
Router configuration
In the following example, the automatic resetting of BGP sessions is disabled:
router bgp 109 no bgp fast-external-fallover
Use the clear arp-cache EXEC command to remove all dynamic entries from the ARP cache and to clear the fast-switching cache.
clear arp-cacheThis command has no arguments or keywords.
EXEC
The following example removes all dynamic entries from the ARP cache and clears the fast-switching cache:
clear arp-cache
To reset a BGP connection, use the clear ip bgp EXEC command at the system prompt.
clear ip bgp {* | address}| * | Resets all current BGP sessions. |
| address | Resets only the identified BGP neighbor. |
EXEC
Use this command whenever any of the following changes occur:
The following example resets all current BGP sessions:
clear ip bgp *
To remove all of the members of a BGP peer group, use the clear ip bgp peer-group EXEC command.
clear ip bgp peer-group tag| tag | Name of the BGP peer group to clear. |
EXEC
The following example removes all members from the BGP peer group internal:
clear ip bgp peer-group internal
neighbor peer-group (assigning members)
To delete routes from the DVMRP routing table, use the clear ip dvmrp route EXEC command.
clear ip dvmrp route {* | route}| * | Clears all routes. |
| route | Clears the longest matched route. Can be an IP address, a network number, or an IP DNS name. |
EXEC
The following example deletes route 10.1.1.1 from the DVMRP routing table:
clear ip dvmrp route 10.1.1.1
The following example deletes network 10.0.0.0 from the DVMRP routing table:
clear ip dvmrp route 10.0.0.0
To delete entries from the neighbor table, use the clear ip eigrp neighbors EXEC command.
clear ip eigrp neighbors [ip-address | type number]| ip-address | (Optional) Address of the neighbor. |
| type number | (Optional) Interface type and number. Specifying these arguments removes from the neighbor table all entries learned via this interface. |
EXEC
The following example removes the neighbor whose address is 172.20.8.3:
clear ip eigrp neighbors 172.20.8.3
To delete entries from the IGMP cache, use the clear ip igmp group EXEC command.
clear ip igmp group [group-name | group-address | type number]| group-name | (Optional) Name of the multicast group, as defined in the DNS hosts table or with the ip host command. |
| group-address | (Optional) Address of the multicast group. This is a multicast IP address in four-part dotted notation. |
| type number | (Optional) Interface type and number. |
EXEC
The IGMP cache contains a list of the multicast groups of which hosts on the directly connected LAN are members. If the access server has joined a group, it is also listed in the cache.
To delete all entries from the IGMP cache, specify the clear ip igmp group command with no arguments.
The following example clears entries for the multicast group 172.16.255.1 from the IGMP cache:
clear ip igmp group 172.16.255.1
A dagger (+) indicates that the command is documented in another chapter.
ip host +
show ip igmp groups
show ip igmp interface
To delete entries from the IP multicast routing table, use the clear ip mroute EXEC command.
clear ip mroute * | {group-name [source-address] | group-address [source-address]}| * | Deletes all entries from the IP multicast routing table. |
| group-name | Name of the multicast group, as defined in the DNS hosts table or with the ip host command. |
| group-address | Address of the multicast group. This is a multicast IP address in four-part dotted notation. |
| source-address | (Optional) Address of a multicast source that is transmitting to the group. A source does not need to be a member of the group. If you specify source-address, you must specify either group-name or group-address. |
EXEC
The following example deletes all entries from the IP multicast routing table:
clear ip mroute *
The following example deletes from the IP multicast routing table all sources on the 10.3.0.0 subnet that are transmitting to the multicast group 172.22.205.42. Note that this example deletes all sources on network 10.3, not individual sources.
clear ip mroute 172.22.205.42 10.3.0.0
A dagger (+) indicates that the command is documented in another chapter.
ip host +
show ip mroute
Use the clear ip route EXEC command to remove one or more routes from the IP routing table.
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. |
EXEC
The following example removes a route to network 172.30.0.0 from the IP routing table:
clear ip route 172.30.0.0
show ip route
To delete a session directory cache entry, use the clear ip sd EXEC command.
clear ip sd [group-address | "session-name"]| group-address | (Optional) All sessions associated with the IP group address are deleted. |
| "session-name" | (Optional) Only the session directory entry by this name is deleted. The session name is enclosed in quotation marks and is not case-sensitive. |
EXEC
If neither argument is specified, the entire session directory cache is deleted.
The following example deletes the entire session directory cache:
clear ip sd
The following example deletes sessions with the group address 224.2.0.1 from the session directory cache:
clear ip sd 224.2.0.1
The following example deletes the session entry called mbone audio from the session directory cache:
clear ip sd "mbone audio"
To control the redistribution of routing information between IGRP or IP Enhanced IGRP processes, use the default-information allowed router configuration command. To suppress IGRP or IP Enhanced IGRP exterior or default routes when they are received by an IP Enhanced IGRP process, use the no default-information allowed in command. To suppress IGRP or IP Enhanced IGRP exterior routes in updates, use the no default-information allowed out command.
default-information allowed {in | out} [route-map map-tag]| in | Allows IP Enhanced IGRP exterior or default routes to be received by an IP Enhanced IGRP process. |
| out | Allows IP Enhanced IGRP exterior routes to be advertised in updates. |
| route-map map-tag | (Optional) Indicates that the route map should be interrogated to filter the importation of routes from this source routing protocol to the current routing protocol. The argument map-tag is the identifier of a configured route map. If you specify route-map without specifying map-tag, no routes are imported. If you omit route-map, all routes are redistributed. |
Normally, exterior routes are always accepted and default information is passed between IGRP processes when doing redistribution.
Router configuration
The default network of 0.0.0.0 used by RIP cannot be redistributed by IGRP or IP Enhanced IGRP.
The following example allows IGRP exterior or default routes to be received by the IGRP process in autonomous system 23:
router igrp 23 default-information allowed in
The following example allows IP Enhanced IGRP exterior or default routes to be received by the IP Enhanced IGRP process in autonomous system 23:
router eigrp 23 default-information allowed in
Use the default-information originate router configuration command to allow the redistribution of network 0.0.0.0 into BGP. Use the no form of this command to prevent the redistribution of network 0.0.0.0 into BGP.
default-information originateThis command has no arguments or keywords.
Disabled
Router configuration
The same functionality will result from the network 0.0.0.0 command, using the network router configuration command.
The following example configures BGP to redistribute network 0.0.0.0 into BGP:
router bgp 164 default-information originate
Use the default-information originate router configuration command to explicitly configure EGP to generate a default route. Use the no form of this command to disable this function.
default-information originateThis command has no arguments or keywords.
Disabled
Router configuration
Because EGP can use network 0.0.0.0 as a default route, EGP must be explicitly configured to generate a default route. If the next hop for the default route can be advertised as a third party, it will be included as a third party.
The following example configures EGP to generate a default route:
autonomous system 109 router egp 164 network 172.16.0.0 network 192.168.7.0 neighbor 10.2.0.2 default-information originate
Use the default-information originate router configuration command to generate a default route into an OSPF routing domain. Use the no form of this command to disable generation of a default route into the specified OSPF routing domain.
default-information originate [always] [metric metric-value] [metric-type type-value]| originate | For OSPF, causes the access server to generate a default external route into an OSPF domain if the access server already has a default route and you want to propagate to other access servers. |
| always | (Optional) For OSPF, the default route always will be advertised whether or not the access server has a default route. |
| metric metric-value | (Optional) Metric used for generating the default route. If a value is not specified for this option, and no value is specified using the default-metric router configuration command, the default metric value is 10. The value used is specific to the 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 access server adopts a Type 2 external route. |
| route-map map-name | (Optional) Routing process will generate the default route if the route-map is satisfied. |
Disabled
Router configuration
Whenever you use the redistribute or the default-information router configuration commands to redistribute routes into an OSPF routing domain, the access server automatically becomes an Autonomous System Boundary Router. However, an Autonomous System Boundary Router does not, by default, generate a default route into the OSPF routing domain. The access server still needs to have a default route for itself before it generates one, except when you have specified the always keyword.
When you use this command for the OSPF process, the default network must reside in the routing table and you must satisfy the route-map map-name keyword. Use the default-information originate always route-map map-name form of the command when you do not want the dependency on the default network in the routing table.
The following example specifies a metric of 100 for the default route redistributed into the OSPF routing domain and an external metric type of Type 1:
router ospf 109 redistribute igrp 108 metric 100 subnets default-information originate metric 100 metric-type 1
Use the default-metric router configuration command to set default metric values for the RIP, EGP, IGRP, Enhanced IGRP, and BGP routing protocols. Use the no form of this command to remove the metric value and return to the default state.
default-metric number| number | Default metric value appropriate for the specified routing protocol. |
Built-in, automatic metric translations, as appropriate for each routing protocol
Router configuration
This command is used in conjunction with the redistribute router configuration command to cause the current routing protocol to use the same metric value for all redistributed routes. A default metric helps solve the problem of redistributing routes with incompatible metrics. Whenever metrics do not convert, using a default metric provides a reasonable substitute and enables the redistribution to proceed.
In BGP, this sets the MULTI_EXIT_DISC metric. (The name of this metric for BGP Versions 2 and 3 is INTER_AS.)
The following example shows an access server in autonomous system 109 using both the RIP and the IGRP routing protocols. The example advertises IGRP-derived routes using the RIP protocol and assigns the IGRP-derived routes a RIP metric of 10.
router rip default-metric 10 redistribute igrp 109
To set default metric values for the BGP, EGP, OSPF, and RIP routing protocols, use this form of the default-metric router configuration command. To return to the default state, use the no form of this command.
default-metric number| number | Default metric value appropriate for the specified routing protocol. |
Built-in, automatic metric translations, as appropriate for each routing protocol
Router configuration
The default-metric command is used in conjunction with the redistribute router configuration command to cause the current routing protocol to use the same metric value for all redistributed routes. A default metric helps solve the problem of redistributing routes with incompatible metrics. Whenever metrics do not convert, using a default metric provides a reasonable substitute and enables the redistribution to proceed.
In BGP, this sets the multiple exit discriminator (MED) metric. (The name of this metric for BGP Versions 2 and 3 is INTER_AS.)
The following example shows a router in autonomous system 109 using both the RIP and the OSPF routing protocols. The example advertises OSPF-derived routes using the RIP protocol and assigns the IGRP-derived routes a RIP metric of 10.
router rip default-metric 10 redistribute ospf 109
Use this form of the default-metric router configuration command to set metrics for IGRP. Use the no form of this command to remove the metric value and return to the default state.
default-metric bandwidth delay reliability loading mtu| bandwidth | Minimum bandwidth of the route in kilobits per second |
| delay | Route delay in tens of microseconds |
| reliability | Likelihood of successful packet transmission expressed as a number between 0 and 255 (255 is 100 percent reliability) |
| loading | Effective bandwidth of the route expressed as a number between 0 and 255 (255 is 100 percent loading) |
| mtu | Minimum Maximum Transmission Unit (MTU) size for the route |
Built-in, automatic metric translations
Router configuration
IGRP metric defaults have been carefully set to work for a wide variety of networks. Take great care in changing these values.
Automatic metric translations for IGRP are only supported when redistributing from IGRP or static.
The following example takes redistributed RIP metrics and translates them into IGRP metrics with values as follows: bandwidth = 1000, delay = 100, reliability = 250, loading = 100, and mtu =1500.
router igrp 109 network 172.16.0.0 redistribute rip default-metric 1000 100 250 100 1500
redistribute
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]] [ip]| weight | Administrative distance. This can be an integer from 10 to 255. (The values 0 through 9 are reserved for internal use.) Used alone, the argument weight specifies a default administrative distance that the access server 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 access server to ignore the corresponding bit in the address value. |
| access-list-number | (Optional) Number of a standard IP access list to be applied to incoming routing updates. |
| ip | (Optional) IP-derived routes for IS-IS. Can be applied independently for IP routes and ISO CLNS routes. |
Default administrative distances are shown in Table 19-1.
| Route Source | Default Distance |
|---|---|
| Connected interface | 0 |
| Static route | 1 |
| External BGP | 20 |
| IGRP | 100 |
| OSPF | 110 |
| RIP | 120 |
| EGP | 140 |
| Internal BGP | 200 |
| Unknown | 255 |
Router configuration
Numerically, an administrative distance is an integer between 0 and 255. In general, the higher the value, the lower the trust rating. An administrative distance of 255 means the routing information source cannot be trusted at all and should be ignored.
When the optional access list number is used with this command, it is applied when a network is being inserted into the routing table. This behavior allows filtering of networks according to the IP address of the access server supplying the routing information. This could be used, as an example, to filter out possibly incorrect routing information from access servers not under your administrative control.
The order in which you enter distance commands can affect the assigned administrative distances in unexpected ways (see "Example" for further clarification).
Weight values are also subjective; there is no quantitative method for choosing weight values.
For BGP, the distance command sets the administrative distance of the External BGP route.
Theshow ip protocols EXEC command displays the default administrative distance for a specified routing process.
In the following example, the router igrp global configuration command sets up IGRP routing in autonomous system number 109. The network router configuration commands specify IGRP routing on networks 192.168.7.0 and 172.28.0.0. The first distance router configuration command sets the default administrative distance to 255, which instructs the access server to ignore all routing updates from access servers for which an explicit distance has not been set. The second distance command sets the administrative distance for all access servers on the Class C network 192.168.7.0 to 90. The third distance command sets the administrative distance for the access server with the address 172.28.1.3 to 120.
router igrp 109 network 192.168.7.0 network 172.28.0.0 distance 255 distance 90 192.168.7.0 0.0.0.255 distance 120 172.28.1.3 0.0.0.0
distance bgp
To allow the use of external, internal, and local administrative distances that could be a better route to a node, use the distance bgp router configuration command. To return to the default values, use the no form of this command.
distance bgp external-distance internal-distance local-distance| external-distance | Administrative distance for BGP external routes. External routes are routes for which the best path is learned from a neighbor external to the autonomous system. Acceptable values are from 1 to 255. The default is 20. Routes with a distance of 255 are not installed in the routing table. |
| internal-distance | Administrative distance for BGP internal routes. Internal routes are those routes that are learned from another BGP entity within the same autonomous system. Acceptable values are from 1 to 255. The default is 200. Routes with a distance of 255 are not installed in the routing table. |
| local-distance | Administrative distance for BGP local routes. Local routes are those networks listed with a network router configuration command, often as back doors, for that access server or for networks that are being redistributed from another process. Acceptable values are from 1 to 255. The default is 200. Routes with a distance of 255 are not installed in the routing table. |
external-distance: 20
internal-distance: 200
local-distance: 200
Router configuration
An administrative distance is a rating of the trustworthiness of a routing information source, such as an individual access server or a group of access servers. Numerically, an administrative distance is an integer between 0 and 255. In general, the higher the value, the lower the trust rating. An administrative distance of 255 means the routing information source cannot be trusted at all and should be ignored.
Use this command if another protocol is known to be able to provide a better route to a node than was actually learned via external BGP, or if some internal routes should really be preferred by BGP.
In the following example, internal routes are known to be preferable to those learned through the IGP, so the administrative distance values are set accordingly:
router bgp 109 network 172.16.0.0 neighbor 172.29.6.6 remote-as 123 neighbor 172.28.1.1 remote-as 47 distance bgp 20 20 200
To allow the use of internal and external administrative distances that could be a better route to a node, use the distance eigrp router configuration command. To reset these values to their defaults, use the no form of this command.
distance eigrp internal-distance external-distance| internal-distance | Administrative distance for IP Enhanced IGRP internal routes. Internal routes are those that are learned from another entity within the same autonomous system. It can be a value from 1 to 255. The default is 90. |
| external-distance | Administrative distance for IP Enhanced IGRP external routes. External routes are those for which the best path is learned from a neighbor external to the autonomous system. It can be a value from 1 to 255. The default is 170. |
internal-distance: 90
external-distance: 170
Router configuration
An administrative distance is a rating of the trustworthiness of a routing information source, such as an individual access server or a group of access servers. Numerically, an administrative distance is an integer between 0 and 255. In general, the higher the value, the lower the trust rating. An administrative distance of 255 means the routing information source cannot be trusted at all and should be ignored.
Use the distance eigrp command if another protocol is known to be able to provide a better route to a node than was actually learned via external IP Enhanced IGRP or if some internal routes should really be preferred by IP Enhanced IGRP.
Table 19-2 lists the default administrative distances.
| Route Source | Default Distance |
|---|---|
| Connected interface | 0 |
| Static route | 1 |
| Enhanced IGRP summary route | 5 |
| External BGP | 20 |
| Internal Enhanced IGRP | 90 |
| IGRP | 100 |
| OSPF | 110 |
| IS-IS | 115 |
| RIP | 120 |
| EGP | 140 |
| External Enhanced IGRP | 170 |
| Internal BGP | 200 |
| Unknown | 255 |
To display the default administrative distance for a specified routing process, use the show ip protocols EXEC command.
In the following example, the router eigrp global configuration command sets up IP Enhanced IGRP routing in autonomous system number 109. The network router configuration commands specify IP Enhanced IGRP routing on networks 192.168.7.0 and 172.28.0.0. The first distance router configuration command sets the default administrative distance to 255, which instructs the access server to ignore all routing updates from access servers for which an explicit distance has not been set. The second distance router configuration command sets the administrative distance for all access servers on the Class C network 192.168.7.0 to 90. The third distance router configuration command sets the administrative distance for the access server with the address 172.28.1.3 to 120.
router eigrp 109 network 192.168.7.0 network 172.28.0.0 distance 255 ! ! use caution when executing the next two commands! ! distance 90 192.168.7.0 0.0.0.255 distance 120 172.28.1.3 0.0.0.0
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 in [type number]| access-list-number | Standard IP access list number. The list defines which networks are to be received and which are to be suppressed in routing updates. |
| type | (Optional) Interface type. |
| number | (Optional) Interface number. |
Disabled
Router configuration
If no interface is specified, the access list will be applied to all incoming updates.
The following example causes only two networks to be accepted by a RIP routing process: network 0.0.0.0 (the RIP default) and network 172.16.0.0.
access-list 1 permit 0.0.0.0 access-list 1 permit 172.16.0.0 access-list 1 deny 0.0.0.0 255.255.255.255 router rip network 172.16.0.0 distribute-list 1 in
A dagger (+) indicates that the command is documented in another chapter.
access-list +
distribute-list out
redistribute
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 out [interface-name | routing-process || access-list-number | Standard IP access list number. The list defines which networks are to be sent and which are to be suppressed in routing updates. |
| interface-name | (Optional) Name of a particular interface. Does not apply to OSPF. |
| routing-process | (Optional) Name of a particular routing process, or the keyword static or connected. |
| autonomous-system-number | A decimal number between 1 and 65535. |
Disabled
Router configuration
When redistributing networks, a routing process name can be specified as an optional trailing argument to the distribute-list command. This causes the access list to be applied to only those routes derived from the specified routing process. After this access list is applied, any access list specified by a distribute-list command without a process name argument will be applied. Addresses not specified in the distribute-list command will not be advertised in outgoing routing updates.
To filter networks received in updates, use the distribute-list in command.
The following example would cause only one network to be advertised by a RIP routing process: network 172.16.0.0.
access-list 1 permit 172.16.0.0 access-list 1 deny 0.0.0.0 255.255.255.255 router rip network 172.16.0.0 distribute-list 1 out
A dagger (+) indicates that the command is documented in another chapter.
access-list +
distribute-list in
redistribute
Use the ip address interface configuration command to specify the IP address on an interface. Use the no form of this command to remove the specified secondary address.
ip address address mask [secondary]| address mask | IP address and mask. |
| secondary | (Optional) Address to be added as a secondary address. |
Disabled
Interface configuration
The optional keyword secondary allows an unlimited number of secondary addresses to be specified. Secondary addresses are treated like primary addresses, except that the system never generates datagrams other than routing updates with secondary source addresses. IP broadcasts and ARP requests are handled properly, as are interface routes in the IP routing table.
Secondary IP addresses can be used in many situations. The following are common applications:
The following example specifies 172.16.1.27 as the primary address and 192.168.7.17 as a secondary address for Ethernet interface 0:
interface ethernet 0 ip address 172.16.1.27 255.255.255.0 ip address 192.168.7.17 255.255.255.0 secondary
Use the ip as-path access-list global configuration command to define a BGP-related access list. Use the no form of this command to disable use of the access list.
ip as-path access-list access-list-number {permit | deny} as-regular-expression| access-list-number | Integer from 1 to 199 that indicates the regular expression access list number. |
| permit | Permits access for matching conditions. |
| deny | Denies access to matching conditions. |
| as-regular-expression | Autonomous system in the access list using a regular expression. See the "Regular Expressions" appendix for information on forming regular expressions. |
No access lists are defined.
Global configuration
You can specify an access list filter on both inbound and outbound BGP routes. In addition, you can assign weights based on a set of filters. Each filter is an access list based on regular expressions. If the regular expression matches the representation of the autonomous system path of the route as an ASCII string, then the permit or deny condition applies. The autonomous system path does not contain the local autonomous system number. Use the ip as-path access-list global configuration command to define an BGP access list, and the neighbor router configuration command to apply a specific access list.
See the "Regular Expressions" appendix for information on forming regular expressions.
The following example specifies that the BGP neighbor with IP address 172.28.1.1 is not sent advertisements about any path through or from the adjacent autonomous system 123:
ip as-path access-list 1 deny _123_ ip as-path access-list 1 deny ^123 .* ! The space in the above expression (^123.*) is required. router bgp 109 network 172.16.0.0 neighbor 172.29.6.6 remote-as 123 neighbor 172.28.1.1 remote-as 47 neighbor 172.28.1.1 filter-list 1 out
neighbor distribute-list
neighbor filter-list
To create a community list for BGP and control access to it, use the ip community-list global configuration command. To delete the community list, use the no form of this command.
ip community-list community-list-number {permit | deny} community-number| community-list-number | Integer 1 through 99 that identifies one or more permit or deny groups of communities. |
| permit | Permits access for a matching condition. |
| deny | Denies access for a matching condition. |
| community-number | Community number configured by a set community command. Valid value is one of the following:
· 1 through 4294967200. You can specify a single number or multiple numbers separated by a space. · internet--The Internet community. · no-export--Do not advertise this route to an EBGP peer. · no-advertise--Do not advertise this route to any peer (internal or external). |
Once you permit a value for the community number, the community list defaults to an implicit deny for everything else that has not been permitted.
Global configuration
In the following example, the access server permits all routes except the routes with the communities 5 and 10 or 10 and 15:
ip community-list 1 deny 5 10 ip community-list 1 deny 10 15 ip community-list 1 permit internet
set community
Use the ip default-network global configuration command to select a network as a candidate route for computing the gateway of last resort. Use the no form of this command to remove the route.
ip default-network network-number| network-number | Number of the network |
If the access server has a directly connected interface onto the specified network, the dynamic routing protocols running on that access server will generate (or source) a default route. For RIP, this is flagged as the pseudonetwork 0.0.0.0; for IGRP, it is the network itself, flagged as an exterior route.
Global configuration
The access server uses both administrative distance and metric information to determine the default route. Multiple ip default-network commands can be given. All candidate default routes, both static (that is, flagged by ip default-network) and dynamic, appear in the routing table preceded by an asterisk.
If the IP routing table indicates that the specified network number is subnetted and a non-zero subnet number is specified, then the system will automatically configure a static summary route. This static summary route is configured instead of a default network. The effect of the static summary route is to cause traffic destined for subnets that are not explicitly listed in the IP routing table to be routed using the specified subnet.
The following example defines a static route to network 10.0.0.0 as the static default route:
ip route 10.0.0.0 255.0.0.0 172.16.3.4 ip default-network 10.0.0.0
If the following command was issued on an access server not connected to network 172.29.0.0, the access server might choose the path to that network as a default route when the network appeared in the routing table:
ip default-network 172.29.0.0
To configure an acceptance filter for incoming DVMRP reports, use the ip dvmrp accept-filter interface configuration command. To disable this feature, use the no form of this command.
ip dvmrp accept-filter access-list-number [distance]| access-list-number | Number of a standard IP access list. This can be a number from 1 to 99. A value of 0 means that all sources are accepted with the configured distance. |
| distance | (Optional) Administrative distance to the destination. |
All destinations are accepted with a distance of 0.
Interface configuration
Any sources that match the access list are stored in the DVMRP routing table.
The distance is used to compare with the same source in the unicast routing table. The route with the lower distance (either the route in the unicast or DVMRP routing table) takes precedence when computing the Reverse Path Forwarding (RPF) interface for a source of a multicast packet.
By default, the administrative distance for DVMRP routes is 0. This means that they always take precedence over unicast routing table routes. If you have two paths to a source, one through unicast routing (using PIM as the multicast routing protocol) and another path using DVMRP (unicast and multicast routing), and if you want to use the PIM path, use the ip dvmrp accept-filter command to increase the administrative distance for DVMRP routes. For example, if the unicast routing protocol is Enhanced IGRP, which has a default administrative distance of 90, you could define and apply the following access list so the RPF interface used to accept multicast packets will be through the Enhanced IGRP/PIM path:
ip dvmrp accept-filter 1 100 access-list 1 permit 0.0.0.0 255.255.255.255
The following example applies access list 57 to the interface and sets a distance of 4:
access-list 57 permit 172.16.0.0 0.0.255.255 access-list 57 permit 192.168.37.0 0.0.0.255 access-list 57 deny 0.0.0.0 255.255.255.255 ip dvmrp accept-filter 57 4
distance
ip dvmrp metric
show ip dvmrp route
To advertise network 0.0.0.0 to DVMRP neighbors on an interface, use the ip dvmrp default-information interface configuration command. To prevent the advertisement, use the no form of this command.
ip dvmrp default-information {originate | only}| originate | Other routes more specific than 0.0.0.0 can also be advertised. |
| only | No DVMRP routes other than 0.0.0.0 are advertised. |
Disabled
Interface configuration
This command should only be used when the access server is a neighbor to mrouted version 3.6 machines. The mrouted protocol is a public domain implementation of DVMRP.
You can use the ip dvmrp metric command with the ip dvmrp default-information command to tailor the metric used when advertising the default route 0.0.0.0. By default, metric 1 is used.
The following example configures the access server to advertise network 0.0.0.0, in addition to other networks, to DVMRP neighbors:
ip dvmrp default-information originate
To configure the metric associated with a set of destinations for DVMRP reports, use the ip dvmrp metric interface configuration command. To disable this function, use the no form of this command.
ip dvmrp metric metric [list access-list-number] [protocol process-id] | [dvmrp]| metric | Metric associated with a set of destinations for DVMRP reports. It can be a value from 0 to 32. A value of 0 means that the route is not advertised. A value of 32 is equivalent to infinity (unreachable). |
| list access-list-number | (Optional) Number of an access list. If you specify this argument, only the multicast destinations that match the access list are reported with the configured metric. Any destinations not advertised because of split horizon do not use the configured metric. |
| protocol | (Optional) Name of unicast routing protocol. It can be bgp, egp, eigrp, igrp, isis, ospf, rip, or static. (Note that these are the protocol names you can specify with a router protocol command.)
If you specify these arguments, only routes learned by the specified routing protocol are advertised in DVMRP report messages. |
| process-id | (Optional) Process ID number of the unicast routing protocol. |
| dvmrp | (Optional) Allows routes from the DVMRP routing table to be advertised with the configured metric or filtered. |
No metric is preconfigured. Only directly connected subnets and networks are advertised to neighboring DVMRP access servers.
Interface configuration
When PIM is configured on an interface and DVMRP neighbors are discovered, the access server sends DVMRP report messages for directly connected networks. The ip dvmrp metric command enables DVMRP report messages for multicast destinations that match the access list. Usually, the metric for these routes is 1. Under certain circumstances, it may be desirable to tailor the metric used for various unicast routes.
Use the access-list-number argument in conjunction with the protocol process-id arguments to selectively list the destinations learned from a given routing protocol.
If you do not specify this command, only directly connected subnets are advertised via DVMRP.
To display DVMRP activity, use the debug ip dvmrp command.
The following example connects a PIM cloud to a DVMRP cloud. Access list 1 permits the sending of DVMRP reports to the DVMRP access servers advertising all sources in the 192.168.35.0 network with a metric of 1. Access list 2 permits all other destinations, but the metric of 0 means that no DVMRP reports are sent for these destinations.
access-list 1 permit 192.168.35.0 0.0.0.255 access-list 1 deny 0.0.0.0 255.255.255.255 access-list 2 permit 0.0.0.0 255.255.255.255 interface tunnel 0 ip dvmrp metric 1 list 1 ip dvmrp metric 0 list 2
A dagger (+) indicates that the command is documented in the Debug Command Reference publication.
debug ip dvmrp +
ip dvmrp accept-filter
Use the ip gdp interface configuration command to enable GDP routing on an interface. Use the no form of this command to disable GDP routing, with all default parameters.
ip gdp [priority number | reporttime seconds | holdtime seconds]| priority number | (Optional) Alters the GDP priority; default is a priority of 100. A larger number indicates a higher priority. |
| reporttime seconds | (Optional) Alters the GDP reporting interval; the default is 5 seconds for broadcast media such as Ethernets, and never for nonbroadcast media such as X.25. |
| holdtime seconds | (Optional) Alters the GDP default hold time of 15 seconds. |
priority = 100
reporttime = 5 seconds for broadcast media; 0 for nonbroadcast media
holdtime = 15 seconds
Interface configuration
When enabled on an interface, GDP updates report the primary and secondary IP addresses of that interface.
In the following example, GDP is enabled on Ethernet interface 1 with a report time of 10 seconds, and priority and hold time set to their defaults (because none are specified):
interface ethernet 1 ip gdp reporttime 10
To configure the hello interval for the IP Enhanced IGRP routing process designated by an autonomous system number, use the ip hello-interval eigrp interface configuration command. To restore the default value, use the no form of this command.
ip hello-interval eigrp autonomous-system-number seconds| autonomous-system-number | A decimal number between 1 and 65535. |
| seconds | Hello interval, in seconds |
For slow-speed, NBMA networks: 60 seconds
For all other networks: 5 seconds
Interface configuration
The default of 60 seconds applies only to nonbroadcast, multiaccess (NBMA) media. Low speed is considered to be a rate of T1 or slower, as specified with the bandwidth interface configuration command. Note that for the purposes of Enhanced IGRP, Frame Relay and SMDS networks may or may not be considered to be NBMA. These networks are considered NBMA if the interface has not been configured to use physical multicasting; otherwise they are considered not to be NBMA.
The following example sets the hello interval for Ethernet interface 0 to 10 seconds:
interface ethernet 0 ip hello-interval eigrp 109 10
To configure the hold time for a particular Enhanced IGRP routing process designated by the autonomous system number, use the ip hold-time eigrp interface configuration command. To restore the default value, use the no form of this command.
ip hold-time eigrp autonomous-system-number seconds| autonomous-system-number | A decimal number between 1 and 65535. |
| seconds | Hold time, in seconds. |
For slow-speed, NBMA networks: 180 seconds
For all other networks: 15 seconds
Interface configuration
On very congested and large networks, the default hold time might not be sufficient time for all routers to receive hello packets from their neighbors. In this case, you may want to increase the hold time.
The hold time is three times the hello interval. If the current value for the hold time is less than two times the hello interval, the hold time is reset.
If an access server does not receive a hello packet within the specified hold time, routes through the access server are considered available.
Increasing the hold time delays route convergence across the network.
The default of 180 seconds applies only to low speed, nonbroadcase, multiaccess (NBMA) media. Low speed is considered to be a rate of T1 or slower, as specified with the bandwidth interface configuration command.
The following example sets the hold time for Ethernet interface 0 to 40 seconds:
interface ethernet 0 ip hold-time eigrp 109 40
To control the multicast groups that hosts on the subnet serviced on an interface can join, use the ip igmp access-group interface configuration command. To disable groups on an interface, use the no form of this command.
ip igmp access-group access-list-number| access-list-number | Number of a standard IP access list. This can be a number from 1 to 99. |
All groups are allowed on an interface.
Interface configuration
In the following example, host services by Ethernet interface 0 can join the group 172.25.2.2 only:
access-list 1 172.25.2.2 0.0.0.0 interface ethernet 0 ip igmp access-group 1
To have the access server join a multicast group, use the ip igmp join-group interface configuration command. To cancel membership in a multicast group, use the no form of this command.
ip igmp join-group group-address| group-address | Address of the multicast group. This is a multicast IP address in four-part dotted notation. |
No multicast group memberships are predefined.
Interface configuration
IP packets that are addressed to the group address are passed to the IP client process in the access server.
If all the multicast-capable access servers that you administer are members of a multicast group, pinging that group causes all access servers to respond. This can be a useful administrative and debugging tool.
Another reason to have an access server join a multicast group is when other hosts on the network have a bug in IGRP that prevents them from correctly answering IGMP queries. Having the access server join the multicast group causes upstream access servers to maintain multicast routing table information for that group and keeps the paths for that group active.
In the following example, the access server joins multicast group 172.25.2.2:
ip igmp join-group 172.25.2.2
A dagger (+) indicates that the command is documented in another chapter.
ip igmp access-group
ping +
To configure the frequency at which the access server sends IGMP host-query messages, use the ip igmp query-interval interface configuration command. To return to the default frequency, use the no form of this command.
ip igmp query-interval seconds| seconds | Frequency, in seconds, at which to transmit IGMP host-query messages. The can be a value from 0 to 65535. The default is 60 seconds. |
60 seconds
Interface configuration
Multicast access servers send host membership query messages (referred to as host-query messages) to discover which multicast groups have members on the access server's attached networks. Hosts respond with IGMP report messages indicating that they wish to receive multicast packets for specific groups (that is, indicating that the host wants to become a member of the group). Host-query messages are addresses to the all-hosts multicast group, which has the address 172.24.0.1, and have an IP TTL value of 1.
The designated router for a LAN is the only access server that sends IGMP host-query messages. The designated router is elected according to the multicast routing protocol that runs on the LAN.
The following example changes the frequency at which the designated router sends IGMP host-query messages to 2 minutes:
interface tunnel 0 ip igmp query-interval 120
ip pim query-interval
show ip igmp groups
Use the ip irdp interface configuration command to enable ICMP Router Discovery Protocol (IRDP) processing on an interface. Use the no form of this command to disable IRDP routing on the specified interface.
ip irdp [multicast | holdtime seconds | maxadvertinterval seconds | minadvertinterval| multicast | (Optional) Use the multicast address (172.24.0.1) instead of IP broadcasts. |
| holdtime seconds | (Optional) Length of time in seconds advertisements are held valid. Default is three times the maxadvertinterval value. Must be greater than maxadvertinterval and cannot be greater than 9000 seconds. |
| maxadvertinterval seconds | (Optional) Maximum interval in seconds between advertisements. The default is 600 seconds. |
| minadvertinterval seconds | (Optional) Minimum interval in seconds between advertisements. The default is 0.75 times the maxadvertinterval. If you change the maxadvertinterval value, this value defaults to three-quarters of the new value. |
| preference number | (Optional) Access server's preference value. The allowed range is -231 to 231. The default is 0. A higher value increases the access server's preference level. You can modify a particular access server so that it will be the preferred access server to which others home. |
| address address [number] | (Optional) IP address (address) to proxy advertise, and optionally, its preference value (number). |
Disabled
When enabled, IRDP uses these defaults:
Interface configuration
If you change maxadvertinterval, the other two values also change, so it is important to change maxadvertinterval first before changing either holdtime or minadvertinterval.
The ip irdp multicast command allows for compatibility with Sun Microsystems Solaris, which requires IRDP packets to be sent out as multicasts. Many implementations cannot receive these multicasts; ensure end host ability before using this command.
The following example illustrates how to set the various IRDP processes:
! enable irdp on interface Ethernet 0 interface ethernet 0 ip irdp ! send IRDP advertisements to the multicast address ip irdp multicast ! increase access server preference from 100 to 50 ip irdp preference 50 ! set maximum time between advertisements to 400 secs ip irdp maxadvertinterval 400 ! set minimum time between advertisements to 100 secs ip irdp minadvertinterval 100 ! advertisements are good for 6000 seconds ip irdp holdtime 6000 ! proxy-advertise 172.16.14.5 with default access server preference ip irdp address 172.16.14.5 ! 0 proxy-advertise 172.16.14.6 with preference of 50 ip irdp address 172.16.14.6 50
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. |
Packets that are generated by the router are not policy routed.
Global configuration
Packets that are generated by the router are not normally policy routed. However, you can use this command to policy route such packets. You might enable local policy routing if you want packets originated at the router to take a route other than the obvious shortest path.
The ip local policy route-map command identifies a route map to use for local policy routing. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which packets should be policy routed. The set commands specify the set actions--the particular policy routing actions to perform if the criteria enforced by the match commands are met. The no ip local policy route-map command deletes the reference to the route map and disables local policy routing.
In the following example, packets with a destination IP address matching that allowed by extended access list 131 are sent to the router at IP address 174.21.3.20:
ip local policy route-map xxx ! route-map xxx match ip address 131 set ip next-hop 174.21.3.20
match ip address
match length
route-map
set default interface
set interface
set ip default next-hop
set ip next-hop
show ip local policy
To configure a multicast static route (mroute), use the ip mroute global configuration command. To remove the route, use the no form of this command.
ip mroute source mask [protocol as-number] {rpf-address | type number} [distance]| source | IP address of the multicast source. |
| mask | Mask on the IP address of the multicast source. |
| protocol | (Optional) Unicast routing procotol that you are using. |
| as-number | (Optional) Autonomous system number of the routing protocol you are using, if applicable. |
| rpf-address | Incoming interface for the mroute. If the Reverse Path Forwarding address rpf-address is a PIM neighbor, PIM Joins, Grafts, and Prunes are sent to it. The rpf-address can be a host IP address of a directly connected system or a network/subnet number. When it is a route, a recursive lookup is done from the unicast routing table to find a directly connected system. If rpf-address is not specified, the interface type number is used as the incoming interface. |
| type number | Interface type and number for the mroute. |
| distance | (Optional) Determines whether a unicast route, DVMRP route, or static mroute should be used for RPF lookup. The lower distances have better preference. If static has the same distance as the other two RPF sources, the static mroute takes precedence. The default is 0. |
distance: 0
Global configuration
This command allows you to statically configure where multicast sources are located (even though the unicast routing table says something different).
When a source range is specified, the rpf-address applies only to those sources.
The following example configures all sources via a single interface (in this case, a tunnel):
ip mroute 0.0.0.0 255.255.255.255 tunnel0
The following example configures all specific sources within a network number are reachable through 171.68.10.13:
ip mroute 171.69.0.0 255.255.0.0 171.68.10.13
The following example causes this multicast static route to take effect if the unicast routes for any given destination go away:
ip mroute 0.0.0.0 255.255.255.255 serial0 200
To configure IP multicast fast switching, use the ip mroute-cache interface configuration command. To disable IP multicast fast switching, use the no form of this command.
ip mroute-cacheThis command has no arguments or keywords.
Enabled
Interface configuration
If fast switching is disabled on an incoming interface for a multicast routing table entry, the packet will be sent at process level for all interfaces in the outgoing interface list.
If fast switching is disabled on an outgoing interface for a multicast routing table entry, the packet is process level switched for that interface, but might be fast-switched for other interfaces in the outgoing interface list.
When fast switching is enabled (like unicast routing), debug messages are not logged. If you want to log debug messages, disable fast switching.
The following example disables IP multicast fast switching on the interface:
no ip mroute-cache
To control the rate a sender from the source-list can send to a multicast group in the group-list, use the ip multicast rate-limit interface configuration command. To remove the control, use the no form of this command.
ip multicast rate-limit {in | out} [group-list access-list] [source-list access-list] kbps| in | Only packets at the rate of kbps or slower are accepted on the interface. |
| out | Only a maximum of kbps will be transmitted on the interface. |
| group-list access-list | (Optional) Specifies the access list number that controls which multicast groups are subject to the rate limit. |
| source-list access-list | (Optional) Specifies the access list number that controls which senders are subject to the rate limit. |
| kbps | Kilobits per second transmission rate. |
kbps = 0, meaning that there is no limit on the rate traffic is sent.
Interface configuration
If a router receives a packet and in the last second the user has sent over the limit, the packet is dropped; otherwise, it is forwarded.
In the following example, packets to any group from sources in network 171.69.0.0 will have their packets rate-limited to 64 kilobits per second:
interface serial 0 ip multicast rate-limit out group-list 1 source-list 2 64 access-list 1 permit 0.0.0.0 255.255.255.255 access-list 2 permit 171.69.0.0 0.0.255.255
To enable IP multicast routing on the access server, use the ip multicast-routing global configuration command. To disable IP multicast routing, use the no form of this command.
ip multicast-routingThis command has no keywords or arguments.
IP multicast routing is disabled.
Global configuration
When IP multicast routing is disabled, the access server does not forward any multicast packets.
The following example enables IP multicast routing on the access server:
ip multicast-routing
To configure the time-to-live (TTL) threshold of packets being forwarded out an interface, use the ip multicast ttl-threshold interface configuration command. To return to the default TTL threshold, use the no form of this command.
ip multicast ttl-threshold ttl| ttl | Time-to-live value, in hops. It can be a value from 0 to 255. The default value is 0, which means that all multicast packets are forwarded out the interface. |
0, which means that all multicast packets are forwarded on the interface.
Interface configuration
Any multicast packets with a TTL value less than the threshold are not forwarded out the interface.
You should configure the TTL threshold only on border routers. Conversely, access servers on which you configure a TTL threshold value automatically become border routers.
This command replaces the ip multicast-threshold command, which is obsolete.
In the following example, you set the TTL threshold on a border router to 200, which is a very high value. This means that multicast packets must have a TTL greater than 200 in order to be forwarded out this interface. Multicast applications generally set this value well below 200. Therefore, setting a value of 200 means that no packets will be forwarded out the interface.
interface tunnel 0 ip multicast ttl-threshold 200
Use the ip ospf authentication-key interface configuration command to assign a password to be used by neighboring access servers that are using OSPF's simple password authentication. Use the no form of this command to remove any previously assigned OSPF password.
ip ospf authentication-key password| password | Any continuous string of characters that can be entered from the keyboard up to 8 bytes in length. |
No password is specified.
Interface configuration
The password created by this command is used as a "key" that is inserted directly into the OSPF header when the access server originates routing protocol packets. A separate password can be assigned to each network on a per-interface basis. All neighboring access servers on the same network must have the same password to be able to exchange OSPF information.
In the following example, the authentication key is enabled with the string yourpass:
ip ospf authentication-key yourpass
To explicitly specify the cost of sending a packet on an interface, use the ip ospf cost interface configuration command. To reset the path cost to the default value, use the no form of this command.
ip ospf cost cost| cost | Unsigned integer value expressed as the link state metric. It can be a value in the range 1 to 65535. |
No default cost is predefined.
Interface configuration
Unlike IGRP, you must set this metric manually using this command, if you need to change the default. Changing the bandwidth does not change the link cost.
The link state metric is advertised as the link cost in the access server's router link advertisement. We do not support Type of Service (TOS), so you can assign only one cost per interface.
In general, the path cost is calculated as follows:
108 ³ Bandwidth
Using the above formula, the default path costs were calculated as noted in the following list. If these values do not suit your network, you can use your own method of calculating path costs.
The following example sets the interface cost value to 65:
ip ospf cost 65
Use the ip ospf dead-interval interface configuration command to set the number of seconds that an access server's Hello packets must not have been seen before its neighbors declare the access server down. Use the no form of this command to reset the length of time to the default value.
ip ospf dead-interval seconds| seconds | Unsigned integer that specifies the interval in seconds; the value must be the same for all nodes on the network. |
Four times the interval set for the ip ospf hello-interval command
Interface configuration
The interval is advertised in the access server's Hello packets. This value must be the same for all access servers on a specific network.
The following example sets the OSPF dead interval to 60 seconds:
interface ethernet 1 ip ospf dead-interval 60
Use the ip ospf hello-interval interface configuration command to specify the interval between Hello packets that the access server sends on the interface. Use the no form of this command to reset the interval to the default value.
ip ospf hello-interval seconds| seconds | Unsigned integer that specifies the interval in seconds. The value must be the same for all nodes on a specific network. |
10 seconds
Interface configuration
This value is advertised in the access server's Hello packets. The smaller the Hello interval, the faster topological changes will be detected, but more routing traffic will ensue. This value must be the same for all access servers on a specific network.
The following example sets the interval between Hello packets to 15 seconds:
interface ethernet 1 ip ospf hello-interval 15
To enable OSPF MD5 authentication, use the ip ospf message-digest-key interface configuration command. To remove an old MD5 key, use the no form of this command.
ip ospf message-digest-key keyid md5 key| keyid | An identifier in the range 1 through 255. |
| key | Alphanumeric password of up to 16 bytes. |
OSPF MD5 authentication is disabled.
Interface configuration
Usually there is one key per interface, which is used to generate authentication information when sending packets and to authenticate incoming packets. The same key identifier on the neighbor router must have the same key value.
The process of changing keys is as follows. Suppose the current configuration is as follows:
interface ethernet 1 ip ospf message-digest-key 100 md5 OLD
You change the configuration to the following:
interface ethernet 1 ip ospf message-digest-key 101 md5 NEW
The system assumes its neighbors do not have the new key yet, so it begins a rollover process. It sends multiple copies of the same packet, each authenticated by different keys. In this example, the system sends out two copies of the same packet--the first one authenticated by key 100 and the second one authenticated by key 101.
Rollover allows neighboring routers to continue communication while the network administrator is updating them with the new key. Rollover stops once the local system finds that all its neighbors know the new key. The system detects that a neighbor has the new key when it receives packets from the neighbor authenticated by the new key.
After all neighbors have been updated with the new key, the old key should be removed. In this example, you would enter the following:
interface ethernet 1 no ip ospf message-digest-key 100
Then, only key 101 is used for authentication on Ethernet interface 1.
We recommend that you not keep more than one key per interface. Every time you add a new key, you should remove the old key to prevent the local system from continuing to communicate with a hostile system that knows the old key. Removing the old key also reduces overhead during rollover.
The following example sets a new key 19 with the password 8ry4222:
interface ethernet 1 ip ospf message-digest-key 10 md5 xvv560qle ip ospf message-digest-key 19 md5 8ry4222
area authentication
Use the ip ospf network interface configuration command to configure the OSPF network type to a type other than the default for a given media. Use the no form of this command to restore the default.
ip ospf network {broadcast | non-broadcast}| broadcast | Sets the network type to broadcast. |
| non-broadcast | Sets the network type to nonbroadcast. |
Depends on the network type
Interface configuration
Using this feature, you can configure broadcast networks as nonbroadcast multiaccess networks when, for example, you have access servers in your network that do not support multicast addressing. You can also configure nonbroadcast multiaccess networks, such as X.25, Frame Relay, and SMDS, as broadcast networks. This feature saves you from having to configure neighbors.
If this command is issued on an interface that does not allow it, it will be ignored.
The following example sets your OSPF network as a broadcast network:
interface serial 0 ip address 192.168.77.17 255.255.255.0 ip ospf network broadcast encapsulation frame-relay
A dagger (+) indicates that the command is documented in another chapter.
frame-relay map +
neighbor (OSPF)
x25-map +
Use the ip ospf priority interface configuration command to set the access server's priority, which helps determine the designated access server for this network. Use the no form of this command to reset the access server priority to the default value.
ip ospf priority number| number | 8-bit unsigned integer that specifies the priority. The range is from 0 to 255. |
Priority of 1
Interface configuration
When two access servers attached to a network both attempt to become the designated access server; the one with the higher priority takes precedence. If there is a tie, the access server with the higher ID takes precedence. A access server with a priority set to zero is ineligible to become the designated access server or backup designated access server. Access server priority is only configured for interfaces to multiaccess networks (in other words, not point-to-point networks).
This priority value is used when you configure OSPF for nonbroadcast networks using the neighbor router configuration command for OSPF.
The following example sets the access server priority value to 4:
interface ethernet 0 ip ospf priority 4
ip ospf network
neighbor (OSPF)
To specify the number of seconds between link state advertisement retransmissions for adjacencies belonging to the interface, use the ip ospf retransmit-interval interface configuration command. Use the no form of this command to reset the link state advertisement retransmission interval to the default value.
ip ospf retransmit-interval seconds| seconds | Number of seconds between retransmissions; it must be greater than the expected round-trip delay between any two access servers on the attached network. The range is 1 to 65535 seconds. The default is 5 seconds. |
5 seconds
Interface configuration
When an access server sends a link state advertisement (LSA) to its neighbor, it keeps the LSA until it receives back the acknowledgment. If it receives no acknowledgment in seconds, it will retransmit the LSA.
The setting of this parameter should be conservative, or needless retransmission will result. The value should be larger for serial lines and virtual links.
The following example sets the retransmit-interval value to 8 seconds:
interface ethernet 2 ip ospf retransmit-interval 8
Use the ip ospf transmit-delay interface configuration command to set the estimated number of seconds it takes to transmit a link state update packet on the interface. Use the no form of this command to reset the estimated transmission time to the default value.
ip ospf transmit-delay seconds| seconds | Integer that specifies the number of seconds it takes to transmit a link state update. The range is 1 to 65535 seconds. |
1 second
Interface configuration
Link state advertisements in the update packet must have their age incremented by the amount specified in the seconds argument before transmission. The value assigned should take into account the transmission and propagation delays for the interface.
If the delay is not added before transmission over a link, the time in which the LSA propagates over the link is not considered. This setting has more significance on very low speed links.
The following example sets the retransmit-delay value to 3 seconds:
interface ethernet 0 ip ospf transmit-delay 3
Use the ip ospf-name-lookup global configuration command to configure OSPF to look up Domain Name System (DNS) names for use in all OSPF show EXEC command displays. Use the no form of this command to disable the feature.
ip ospf-name-lookupThis command has no arguments or keywords.
Disabled
Global configuration
This feature makes it easier to identify an access server because it is displayed by name rather than by its access server ID or neighbor ID.
The following example configures OSPF to look up DNS names for use in all OSPF show EXEC command displays:
ip ospf-name-lookup
The following is sample output of the show ip ospf database EXEC command, for example, once you have enabled the DNS name lookup feature.
Router# show ip ospf database
OSPF Router with id (192.168.41.1) (Autonomous system 109)
Router Link States (Area 0.0.0.0)
Link ID ADV Router Age Seq# Checksum Link count
192.168.41.1 cs 381 0x80000003 0x93BB 4
192.168.34.2 neon 380 0x80000003 0xD5C8 2
Net Link States (Area 0.0.0.0)
Link ID ADV Router Age Seq# Checksum
192.168.32.1 cs 381 0x80000001 0xC117
To enable PIM on an interface, use the ip pim interface configuration command. To disable PIM on the interface, use the no form of this command.
ip pim [dense-mode | sparse-mode]| dense-mode | (Optional) Enables dense mode of operation. |
| sparse-mode | (Optional) Enables sparse mode of operation. |
IP multicast routing is disabled on all interfaces.
There is no default mode setting.
Interface configuration
Enabling PIM on an interface also enables IGMP operation on that interface. An interface can be configured to be in dense mode or sparse mode. The mode describes how the access server populates its multicast routing table and how the access server forwards multicast packets it receives from its directly connected LANs. In populating the multicast routing table, dense-mode interfaces are always added to the table. Sparse-mode interfaces are added to the table only when periodic join messages are received from downstream access servers or there is a directly connected member on the interface.
Initially, a dense-mode interface forwards multicast packets until the access server determines that there are group members or downstream access servers, or until a prune message is received from a downstream access server. Then, the dense-mode interface will periodically forward multicast packets out the interface until the same conditions occur. Dense mode assumes that there are multicast group members present. Dense-mode access servers never send a join message. They do send prune messages as soon as they determine they have no members or downstream PIM access servers.
A sparse-mode interface is used only for multicast forwarding if a join message is received from a downstream access server or if there are group members directly connected to the interface. Sparse mode assumes that there are no other multicast group members present. When sparse-mode access servers want to join the shared path, they periodically send join messages toward the RP. When sparse-mode access servers want to join the source path, they periodically send join messages toward the source; they also send periodic prune messages toward to RP to prune the shared path.
The following command enables sparse-mode PIM on tunnel interface 0 and sets the address of the RP access server to 192.168.0.8:
interface tunnel 0 ip pim sparse-mode ip pim rp-address 192.168.0.8
The following commands enable dense-mode PIM multicast routing on Ethernet interface 1:
interface ethernet 1 ip pim dense-mode
ip multicast-routing
ip pim rp-address
show ip igmp interface
To configure the frequency at which a sparse-mode PIM access server sends periodic sparse-mode
join/prune PIM messages, use the ip pim message-interval global configuration command. To return to the default interval, use the no form of this command.
| seconds | Interval, in seconds, at which periodic sparse-mode join and prune PIM messages are sent. It can be a number from 1 to 65535. The default is 60 seconds. |
60 seconds
Global configuration
The join-and-prune message interval should be the same for all access servers in the internetwork.
A access server is pruned from a group if a join message is not heard from it in three times the message interval specified by the seconds argument. By default, this is 3 minutes.
The following example changes the PIM message interval to 90 seconds:
ip pim message-interval 90
ip igmp query-interval
ip pim query-interval
To configure a multiaccess WAN interface to be in nonbroadcast, multiaccess mode, use the ip pim nbma-mode interface configuration command. To disable this feature, use the no form of this command.
ip pim nbma-modeThis command has no arguments or keywords.
Disabled
Interface configuration
Use this command on Frame Relay, SMDS, or ATM only, especially when these media do not have native multicast available. Do not use this command on multicast-capable LANs such as Ethernet or FDDI.
When this command is configured, each PIM Join message is kept track of in the outgoing interface list of a multicast routing table entry. Therefore, only PIM WAN neighbors that have joined for the group will get packets sent as data link unicasts. This command should only be used when ip pim sparse-mode is configured on the interface. This command is not recommended for LANs that have natural multicast capabilities.
The following example configures an interface to be in nonbroadcast, multiaccess mode:
ip pim nbma-mode
ip pim sparse-mode
To configure the frequency of PIM router-query messages, use the ip pim query-interval interface configuration command. To return to the default interval, use the no form of this command.
ip pim query-interval seconds| seconds | Interval, in seconds, at which periodic PIM router-query messages are sent. It can be a number from 1 to 65535. The default is 30 seconds. |
30 seconds
Interface configuration
Routers that are configured for IP multicast send PIM router-query messages to determine which access server will be the designated router for each LAN segment (subnet). The designated router is responsible for sending IGMP host-query messages to all hosts on the directly connected LAN. When operating in sparse mode, the designated router is responsible for sending source registration messages to the RP. The designated router is the access server with the largest IP address.
The following example changes the PIM router-query message interval to 45 seconds:
interface tunnel 0 ip pim query-interval 45
ip igmp query-interval
ip pim message-interval
To configure the address of a PIM rendezvous point (RP) for a particular group, use the ip pim rp-address global configuration command. To remove an RP address, use the no form of this command.
ip pim rp-address ip-address [access-list-number]| ip-address | IP address of an access server to be a PIM RP. This is a unicast IP address in four-part dotted notation. |
| access-list-number | (Optional) Access list number; defines which multicast groups the RP should be used for. Standard IP access list. The number can be in the range 1 to 100. |
No PIM RPs are preconfigured.
Global configuration
You must configure the IP address of RPs in leaf routers only. Leaf routers are those access servers that are directly connected either to a multicast group member or to a sender of multicast messages.
The RP address is used by first-hop access servers to send register packets on behalf of source multicast hosts to the RP. This address is also used by access servers on behalf of multicast hosts that want to become members of a group to send join messages towards the RP. The RP must be a PIM access server; however, it does not require any special configuration to recognize that it is the RP. Also, RPs are not members of the multicast group; rather, they serve as a "meeting place" for multicast sources and group members.
Choosing the access server that will be an RP requires prior coordination between the people who want to be members of the multicast group. You should examine the length of the paths between members and sources. Remember that most multicast members will eventually want to join to the source tree that is the shortest route between the source and the group member.
You can configure an access server to use a single RP for more than one group. The conditions specified by the access list determine which groups the RP can be used for. If no access list is configured, the RP is used for all groups.
A PIM access server can use multiple RPs.
First-hop access servers for multicast sources send register packets to all configured RPs. First-hop access servers for multicast group members send join packets to one RP at a time. Once this access server begins receiving multicast packets for the group, it will have joined one RP tree. Because the access server does not want to receive multiple copies of the same packet, it joins only one RP tree.
The following example sets the PIM RP address to 192.168.37.33 for all multicast groups:
ip pim rp-address 192.168.37.33
The following example sets the PIM RP address to 192.168.6.22 for the multicast group 172.25.2.2 only:
access list 1 172.25.2.2 0.0.0.0 pi pim rp-address 192.168.6.22 1
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. |
No policy routing occurs on the interface.
Interface configuration
You might enable policy routing if you want your packets to take a route other than the obvious shortest path.
The ip policy route-map command identifies a route map to use for policy routing. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which policy routing is allowed for the interface. The set commands specify the set actions--the particular policy routing actions to perform if the criteria enforced by the match commands are met. The no ip policy route-map command deletes the pointer to the route map.
In the following example, packets with the destination IP address of 174.95.16.18 are sent to the router at IP address 174.21.3.20:
interface serial 0 ip policy route-map wethersfield ! route-map wethersfield match ip address 174.95.16.18 set ip next-hop 174.21.3.20
match ip address
match length
route-map
set default interface
set interface
set ip default next-hop
set ip next-hop
Use the ip route global configuration command to establish static routes. Use the no form of this command to remove the static routes.
ip route network [mask] {address | interface} [distance]| network | Internet address of the target network or subnet |
| mask | (Optional) Network mask that lets you mask network and subnetwork bits |
| address | Internet address of the next hop that can be used to reach that network |
| interface | Network interface to use |
| distance | (Optional) An administrative distance |
No static routes are established.
Global configuration
A static route is appropriate when the access server cannot dynamically build a route to the destination.
If you specify an administrative distance, you are flagging a static route that can be overridden by dynamic information. For example, IGRP-derived routes have a default administrative distance of 100. To have a static route that would be overridden by an IGRP dynamic route, specify an administrative distance greater than 100. Static routes have a default administrative distance of 1.
Static routes that point to an interface will be advertised via RIP, IGRP, and other dynamic routing protocols, regardless of whether redistribute static commands were specified for those routing protocols. This is because static routes that point to an interface are considered in the routing table to be connected and hence lose their static nature. However, if you define a static route to an interface that is not one of the networks defined in a network command, no dynamic routing protocols will advertise the route unless a redistribute static command is specified for these protocols.
In the following example, an administrative distance of 110 was chosen. In this case, packets for network 10.0.0.0 will be routed through to the access server at 172.16.3.4 if dynamic information with administrative distance less than 110 is not available.
ip route 10.0.0.0 255.0.0.0 172.16.3.4 110
In the following example, packets for network 172.16.0.0 will be routed to the access server at 172.16.6.6:
ip route 172.16.0.0 255.255.0.0 172.16.6.6
To enable the router to listen to session directory advertisements, use the ip sd listen interface configuration command. To disable this feature, use the no form of this command.
ip sd listenThis command has no arguments or keywords.
Disabled
Interface configuration
Session Directory Protocol is a multicast application for creating desktop conferencing sessions. It creates group addresses and allows the user to specify the scope of the group and whether audio, video, or whiteboard applications will be invoked when others open the session.
The ip sd listen command merely enables the router to listen to session directory advertisements. The router joins the default session directory group (group 224.2.127.255) on the interface. Use this command to get contact information.
The following example enables the router to listen to session directory advertisements:
ip sd listen
Use the ip split-horizon interface configuration command to enable the split-horizon mechanism. Use the no form of this command to turn off the split-horizon mechanism.
ip split-horizonThis command has no arguments or keywords.
Varies with media
Interface configuration
For all interfaces, except those for which either Frame Relay or SMDS encapsulation is enabled, the default condition for this command is ip split-horizon; in other words, the split horizon feature is active. If the interface configuration includes either the encapsulation frame-relay or encapsulation smds interface configuration commands, then the default is for split horizon to be disabled by default. Split horizon is not disabled by default for interfaces using any of the X.25 encapsulations.
If split horizon has been disabled on an interface and you wish to enable it, use the ip split-horizon command to restore the split horizon mechanism.
The following example illustrates a simple example of disabling split horizon on a serial link. In this example, the serial link is connected to an X.25 network:
interface serial 0 encapsulation x25 no ip split-horizon
To enable IP Enhanced IGRP split horizon, use the ip split-horizon eigrp interface configuration command. To disable split horizon, use the no form of this command.
ip split-horizon eigrp autonomous-system-number| autonomous-system-number | A decimal number between 1 and 65535. |
Enabled
Interface configuration
For networks that include links over X.25 PSNs, you can use the neighbor router configuration command to defeat the split horizon feature. As an alternative, you can explicitly specify the no ip split-horizon eigrp command in your configuration. However, if you do so, you must similarly disable split horizon for all access servers in any relevant multicast groups on that network.
Do not change the default state of split horizon unless you are certain that your application requires the change to properly advertise routes. Remember that if split horizon is disabled on a serial interface and that interface is attached to a packet-switched network, you must disable split horizon for all access servers in any relevant multicast groups on that network.
The following example disables split horizon on a serial link connected to an X.25 network:
interface serial 0 encapsulation x25 no ip split-horizon eigrp
ip split-horizon
neighbor
To configure a summary aggregate address for a specified interface, use the ip summary-address eigrp interface configuration command. To disable a configuration, use the no form of this command.
ip summary-address eigrp autonomous-system-number address mask| autonomous-system-number | A decimal number between 1 and 65535. |
| address | IP summary aggregate address to apply to an interface. |
| mask | Subnet mask. |
No summary aggregate addresses are predefined.
Interface configuration
IP Enhanced IGRP summary routes are given an administrative distance value of 5. You cannot configure this value.
The following example sets the IP summary aggregate address for Ethernet interface 0:
interface ethernet 0 ip summary-address eigrp 109 192.168.0.0 255.255.0.0
Use the match as-path route-map configuration command to match a BGP autonomous system path access list. Use the no form of this command to remove the path list entry.
match as-path path-list-number| path-list-number | Autonomous system path access list. An integer from 1 through 199. |
No path lists are defined.
Route-map configuration
The values set by the match and set commands override global values. For example, the weights assigned with the match as-path and set weight route-map commands override the weights assigned using the neighbor weight and neighbor filter-list commands.
A route map can have several parts. Any route that does not match at least one match clause relating to a route-map command will be ignored; that is, the route will not be advertised for outbound route maps and will not be accepted for inbound route maps. If you want o modify only some data, you must configure second route-map section with an explicit match specified.
The implemented weight is based on the first matched autonomous system path.
In the following example, the autonomous system path is set to match BGP autonomous system path access list 20:
route-map igp2bgp match as-path 20
To match a BGP community, use the match community-list route-map configuration command. To remove the community list entry, use the no form of this command.
match community-list community-list-number [exact]| community-list-number | Community list number in the range from 1 through 99. |
| exact | (Optional) Indicates an exact match is required. |
No community list is defined.
Route-map configuration
A route map can have several parts. Any route that does not match at least one match clause relating to a route-map command will be ignored; that is, the route will not be advertised for outbound route maps and will not be accepted for inbound route maps. If you want to modify only some data, you must configure a second route-map section with an explicit match specified.
Matching based on community list is one of the types of match clauses applicable to BGP.
In the following example, the routes that match community list 1 will have the weight set to 100. Any route that has community 109 will have the weight set to 100.
ip community-list 1 permit 109 ! route-map set_weight match community-list 1 set weight 100
In the following example, the routes that match community list 1 will have the weight set to 200. Any route that has community 109 alone will have the weight set to 200.
ip community-list 1 permit 109 ! route-map set_weight match community-list 1 exact set weight 200
ip community-list
route-map
set weight
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 |
No match interfaces are defined.
Route-map configuration
Use the route-map global configuration command, and the route-map configuration commands match and set, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which redistribution is allowed for the current route-map. The set commands specify the set actions--the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The match route-map configuration command has multiple formats. The match commands may be given in any order, and all match commands must "pass" to cause the route to be redistributed according to the set actions given with the set commands. The no forms of the match commands remove the specified match criteria.
A route map can have several parts. Any route that does not match at least one match clause relating to a route-map command will be ignored; that is, the route will not be advertised for outbound route maps and will not be accepted for inbound route maps. If you want o modify only some data, you must configure second route-map section with an explicit match specified.
In the following example, routes that have their next hop out Ethernet interface 0 will be distributed:
route-map name match interface ethernet 0
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...access-list-number| access-list-number | Number of a standard or extended access list. It can be an integer from 1 through 199. |
No access list numbers are specified.
Route-map configuration
Use route maps to redistribute routes or to subject packets to policy routing. Both purposes are described in this section.
In the following example, routes that have addresses specified by access list numbers 5 or 80 will be distributed:
route-map name match ip address 5 80
In the following policy routing example, packets that have addresses specified by access list numbers 6 or 25 will be routed to Ethernet interface 0:
interface serial 0 ip policy route-map chicago ! route-map chicago match ip address 6 25 set interface ethernet 0
match as-path
match community-list
match interface
match ip next-hop
match ip route-source
match metric
match route-type
match tag
route-map
set as-path
set automatic-tag
set community
set level
set local-preference
set metric
set metric-type
set next-hop
set origin
set tag
set weight
ip policy route-map
match length
route-map
set default interface
set interface
set ip default next-hop
set ip next-hop
Use the match ip next-hop route-map configuration command to redistribute any routes that have a next-hop access server address passed by one of the access lists specified. Use the no form of this command to remove the next-hop entry.
match ip next-hop access-list-number...access-list-number| access-list-number | Number of an access list. It can be an integer from 1 through 99. |
Routes are distributed freely, without being required to match a next-hop address.
Route-map configuration
Use the route-map global configuration command, and the route-map configuration commands match and set, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which redistribution is allowed for the current route-map. The set commands specify the set actions--the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The match route-map configuration command has multiple formats. The match commands may be given in any order, and all match commands must "pass" to cause the route to be redistributed according to the set actions given with the set commands. The no forms of the match commands remove the specified match criteria.
A route map can have several parts. Any route that does not match at least one match clause relating to a route-map command will be ignored; that is, the route will not be advertised for outbound route maps and will not be accepted for inbound route maps. If you want o modify only some data, you must configure second route-map section with an explicit match specified.
In the following example, routes that have a next-hop access server address passed by access list 5 or 80 will be distributed:
route-map name match ip next-hop 5 80
match as-path
match community-list
match interface
match ip address
match ip route-source
match metric
match route-type
match tag
route-map
set as-path
set automatic-tag
set community
set level
set local-preference
set metric
set metric-type
set next-hop
set origin
set tag
set weight
Use the match ip route-source route-map configuration command for any routes that have been advertised by access servers at the address specified by the access lists. Use the no form of this command to remove the route-source entry.
match ip route-source access-list-number...access-list-number| access-list-number | Number of an access list. It can be an integer from 1 through 99. |
No filtering on route source.
Route-map configuration
Use the route-map global configuration command, and the route-map configuration commands match and set, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria-- the conditions under which redistribution is allowed for the current route-map. The set commands specify the set actions--the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The match route-map configuration command has multiple formats. The match commands may be given in any order, and all match commands must "pass" to cause the route to be redistributed according to the set actions given with the set commands. The no forms of the match commands remove the specified match criteria.
A route map can have several parts. Any route that does not match at least one match clause relating to a route-map command will be ignored; that is, the route will not be advertised for outbound route maps and will not be accepted for inbound route maps. If you want o modify only some data, you must configure second route-map section with an explicit match specified.
There are situations in which a route's next hop and source access server address are not the same.
In the following example, routes that have been advertised by access servers at the addresses specified by access lists 5 and 80 will be distributed:
route-map name match ip route-source 5 80
match as-path
match community-list
match interface
match ip address
match ip next-hop
match metric
match route-type
match tag
route-map
set as-path
set automatic-tag
set community
set level
set local-preference
set metric
set metric-type
set next-hop
set origin
set tag
set weight
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 through 0x7FFFFFFF. |
| max | Maximum Level 3 length of the packet, inclusive, allowed for a match. Range is 0 through 0x7FFFFFFF. |
No policy routing on the length of a packet.
Route-map configuration
Use the ip policy route-map interface configuration command, the route-map global configuration command, and the match and set route-map configuration commands, to define the conditions for policy routing packets. The ip policy route-map command identifies a route map by name. Each route-map has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which policy routing occurs. The set commands specify the set actions--the particular routing actions to perform if the criteria enforced by the match commands are met.
The match route-map configuration command has multiple formats. The match commands can be given in any order, and all match commands must "pass" to cause the packet to be routed according to the set actions given with the set commands. The no forms of the match commands remove the specified match criteria.
You might want to base your policy routing on the length of packets so that your interactive traffic and bulk traffic are directed to different routers.
In the following example, packets 3 to 200 bytes long, inclusive, will be routed to FDDI interface 0.
interface serial 0 ip policy route-map interactive ! route-map interactive match length 3 200 set interface fddi 0
ip policy route-map
match ip address
route-map
set default interface
set interface
set ip default next-hop
set ip next-hop
Use the match metric route-map configuration command for any routes with the metric specified. Use the no form of this command to remove the entry.
match metric metric-value| metric-value | Route metric. This may be an IGRP five-part metric. A metric value from 0 through 4294967295. |
No filtering on a metric value.
Route-map configuration
Use the route-map global configuration command, and the route-map configuration commands match and set, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which redistribution is allowed for the current route-map. The set commands specify the set actions--the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The match route-map configuration command has multiple formats. The match commands may be given in any order, and all match commands must "pass" to cause the route to be redistributed according to the set actions given with the set commands. The no forms of the match commands remove the specified match criteria.
A route map can have several parts. Any route that does not match at least one match clause relating to a route-map command will be ignored; that is, the route will not be advertised for outbound route maps and will not be accepted for inbound route maps. If you want o modify only some data, you must configure second route-map section with an explicit match specified.
In the following example, routes with the metric 5 will be redistributed.
route-map name match metric 5
match as-path
match community-list
match interface
match ip address
match ip next-hop
match route-type
match tag
route-map
set as-path
set automatic-tag
set community
set level
set local-preference
set metric
set metric-type
set next-hop
set origin
set tag
set weight
Use the match route-type route-map configuration command for any routes that are of the specified type. Use the no form of this command to remove the route-type entry.
match route-type {local | internal | external [type-1 | type-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. |
Disabled
Route-map configuration
Use the route-map global configuration command, and the route-map configuration commands match and set, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which redistribution is allowed for the current route-map. The set commands specify the set actions--the particular redistribution actions that you should perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The match route-map configuration command has multiple formats. The match commands may be given in any order, and all match commands must "pass" to cause the route to be redistributed according to the set actions given with the set commands. The no forms of the match commands remove the specified match criteria.
A route map can have several parts. Any route that does not match at least one match clause relating to a route-map command will be ignored; that is, the route will not be advertised for outbound route maps and will not be accepted for inbound route maps. If you want to modify only some data, you must configure second route-map section with an explicit match specified.
In the following example, internal routes will be redistributed:
route-map name match route-type internal
match as-path
match community-list
match interface
match ip address
match ip next-hop
match ip route-source
match metric
match tag
route-map
set as-path
set automatic-tag
set community
set level
set local-preference
set metric
set metric-type
set next-hop
set origin
set tag
set weight
Use the match tag command for any routes stored in the routing table with one of the tags specified. Use the no form of this command to remove the tag entry.
match tag tag-value...tag-value| tag-value | List of one or more route tag values. An integer from 0 through 4294967295. |
No match tag values are defined.
Route-map configuration
Use the route-map global configuration command, and the route-map configuration commands match and set, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which redistribution is allowed for the current route-map. The set commands specify the set actions--the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The match route-map configuration command has multiple formats. The match commands may be given in any order, and all match commands must "pass" to cause the route to be redistributed according to the set actions given with the set commands. The no forms of the match commands remove the specified match criteria.
A route map can have several parts. Any route that does not match at least one match clause relating to a route-map command will be ignored; that is, the route will not be advertised for outbound route maps and will not be accepted for inbound route maps. If you want o modify only some data, you must configure second route-map section with an explicit match specified.
In the following example, routes stored in the routing table with tag 5 will be redistributed:
route-map name match tag 5
match as-path
match community-list
match interface
match ip address
match ip next-hop
match ip route-source
match metric
match route-type
route-map
set as-path
set automatic-tag
set community
set level
set local-preference
set metric
set metric-type
set next-hop
set origin
set tag
set weight
To trace a branch of a multicast tree for a specific group, use the mbranch EXEC command.
mbranch {group-address | group-name} branch-address [ttl]| group-address | Address of the multicast group. This is a multicast IP address in four-part dotted notation. |
| group-name | Name of the multicast group, as defined in the DNS hosts table or with the ip host command. |
| branch-address | Address of an access server that is on the tree branch. This is a unicast IP address in four-part dotted notation. |
| ttl | (Optional) Time-to-live value, in hops, that is used in trace request packets sent to the branch access server. The default value is 30. |
EXEC
The mbranch command sends multicast IGMP trace request packets to the specified branch access server. It displays information about the branch starting with the local (requesting) access server and ending with the branch access server. This is considered to be the forward direction.
The information returned shows how a multicast packet sourced by this access server will be forwarded by each access server on the path to the access server with the branch address.
The access server with the address branch-address is the only access server that responds to the trace request packets. The response is unicast to the source.
It is important to specify a value for the ttl argument if you are tracing through an access server on which a multicast threshold has been set with the ip multicast-threshold interface configuration command.
The following is sample output from the mbranch command. This trace is between the same access servers as shown in the example for the mrbranch command. Note the order of responses. Also note that the outgoing interface list is the same.
PIM2# mbranch 172.24.255.2 192.168.118.2
Type escape sequence to abort.
Tracing route to group CBONE-WB (172.24.255.2) to 192.168.118.2
Response from 10.17.118.10, 76 msec
1 PIM9 (10.1.22.9) <- PIM2 (10.1.37.2)
Interface list: 172.16.62.0/24 172.16.22.0/24 10.7.0.0/16
2 PIM-CR (172.16.62.18) <- PIM9 (172.16.62.52)
Interface list: 172.16.20.0/24 172.16.53.0/24 172.16.50.0/24
10.16.0.0/16 10.17.0.0/16
3 10.17.118.10 <- 10.17.20.31
Interface list: 192.168.118.0/26 192.168.118.192/26
The mbranch command is interactive if you specify only the word mbranch. The following output shows sample responses to the system prompts:
Router#mbranchTarget IP group address or name:224.0.255.1Target IP router address or name:sj-eng-f2Ttl [30]:10Source address or name:<CR>Interface:ethernet0Type escape sequence to abort. Tracing route to group cbone-audio.cisco.com (224.0.255.1) to 171.69.4.139 Response from sj-eng-f2.cisco.com (171.69.4.139), 4 msec 1 sj-eng-cc2.cisco.com (171.69.121.2)<- 0.0.0.0 Interface list: 171.69.4.0/24 2 sj-eng-f2.cisco.com (171.69.4.139)<- sj-eng-cc2.cisco.com (171.69.4.135) Interface list: 171.69.60.128/26
Table 19-3 describes the fields shown in the display.
| Field | Description |
|---|---|
| Response from 10.17.118.10 | Address of the access server from which the response to the trace request packets came. This is a different interface on the access server to which you sent the packet. |
| 76 msec | How long it took to receive the response. |
| 1 | Order number of access servers in the trace path. In this example, the request went through 3 access servers to reach the access server that responded to the request. |
| PIM9 (10.1.22.9) <- PIM2 (10.1.37.2) | Route of the trace request. In this example, the request went from the access server PIM2 to the access server PIM9 (PIM2 is considered to be PIM9's RPF neighbor), then from PIM9 to PIM-CR, and finally to the access server at 10.17.118.10. |
| Interface list: 172.16.62.0/24 172.16.22.0/24 10.7.0.0/16 | Interfaces out which a multicast packet forwarded by the access server listed on the right side of the previous line (here, PIM2) will be forwarded. In this example, you interpret this line as follows: When the trace packet reached PIM9, it was replicated three times and one copy was sent out each of the three interfaces listed (172.16.62.0, 172.16.22.0, and 10.7.0.0). The interface list shows the subnet number and the mask rather than the interface name. This allows you to more easily figure out the packet's path because you can connect all like-numbered subnets together as a tree in order to detect loops. The source of the multicast packet is always the address of the access server that started the mbranch (in this case, 10.1.37.2). The list does not include interfaces that failed access list conditions or TTL threshold criteria. |
ip multicast ttl-threshold
mbranch
Use the metric holddown router configuration command to keep new IGRP routing information from being used for a certain period of time. Use the no form of this command to disable metric holddown.
metric holddownThis command has no arguments or keywords.
Disabled
Router configuration
Holddown keeps new routing information from being used for a certain period of time. This can prevent routing loops caused by slow convergence. It is sometimes advantageous to disable holddown to increase the network's ability to quickly respond to topology changes; this command provides this function.
Use the metric holddown command if other access servers within the IGRP autonomous system are not configured with no metric holddown. If all access servers are not configured the same way, you increase the possibility of routing loops.
The following example disables metric holddown:
router igrp 15 network 172.16.0.0 network 192.168.7.0 no metric holddown
metric maximum-hops
metric weights
timers basic (EGP, RIP, IGRP)
Use the metric maximum-hops router configuration command to cause the IP routing software to advertise those routes with a hop count higher than is specified by the command (IGRP only) as unreachable. Use the no form of this command to reset the value to the default.
metric maximum-hops hops| hops | Maximum hop count (in decimal). The default value is 100 hops; the maximum number of hops that can be specified is 255. |
100 hops
Router configuration
This command provides a safety mechanism that breaks any potential count-to-infinity problems. It causes the IP routing software to advertise routes with a hop count greater than the value assigned to the hops argument as unreachable.
In the following example, an access server in autonomous system 71 attached to network 10.15.0.0 wants a maximum hop count of 200, doubling the default. The network administrators decided to do this because they have a complex WAN that can generate a large hop count under normal (nonlooping) operations.
router igrp 71 network 10.15.0.0 metric maximum-hops 200
Use the metric weights router configuration command to allow the tuning of the IGRP metric calculations. Use the no form of this command to reset the values to their defaults.
metric weights tos k1 k2 k3 k4 k5| tos | Type of service. Currently it must always be zero. |
| k1-k5 | Constants that convert an IGRP metric vector into a scalar quantity. |
tos=0
k1 = 1
k2 = 0
k3 = 1
k4 = 0
k5 = 0
Router configuration
Use this command to alter the default behavior of IGRP routing and metric computation and allow the tuning of the IGRP metric calculation for a particular type of service (TOS).
If k5 equals 0, the composite IGRP metric is computed according to the following formula:
metric = [k1 * bandwidth + (k2 * bandwidth)/(256 - load) + k3 * delay]
If k5 does not equal zero, an additional operation is done:
metric = metric * [k5 / (reliability + k4)]
Bandwidth is inverse minimum bandwidth of the path in bits per second scaled by a factor of 10*1010. The range is from a 1200 bps line to 10 Gbps.
Delay is in units of 10 microseconds. This gives a range of 10 microseconds to 168 seconds. A delay of all ones indicates that the network is unreachable.
The delay parameter is stored in a 24-bit field, in tens of microseconds. Hence, the delay can be from 1 (10 microseconds) to hex FFFFFF (decimal 16777215), which corresponds to 167.77215 seconds. A delay of all ones (that is, a delay of 16777215) indicates that the network is unreachable.
Table 19-4 lists the default values used for several common media.
| Media Type | Delay | Bandwidth |
|---|---|---|
| Satellite | 200,000 (2 sec) | 20 (500 Mbit) |
| Ethernet | 100 (1 ms) | 1,000 |
| 1.544 Mbps | 2000 (20 ms) | 6,476 |
| 64 kbps | 2000 | 156,250 |
| 56 kbps | 2000 | 178,571 |
| 10 kbps | 2000 | 1,000,000 |
| 1 kbps | 2000 | 10,000,000 |
Reliability is given as a fraction of 255. That is, 255 is 100 percent reliability or a perfectly stable link.
Load is given as a fraction of 255. A load of 255 indicates a completely saturated link.
The following example sets the metric weights to slightly different values than the defaults:
router igrp 109 network 172.16.0.0 metric weights 0 2 0 2 0 0
A dagger (+) indicates that the command is documented in another chapter.
bandwidth +
delay +
metric holddown
metric maximum-hops
To trace a branch of a multicast tree for a group in the reverse direction, use the mrbranch EXEC command.
mrbranch {group-address | group-name} branch-address [ttl]| group-address | Address of the multicast group. This is a multicast IP address in four-part dotted notation. |
| group-name | Name of the multicast group, as defined in the DNS hosts table or with the ip host command. |
| branch-address | Address of an access server on the tree branch. This is a unicast IP address in four-part dotted notation. |
| ttl | (Optional) Time-to-live value, in hops, that is used in trace request packets sent to the branch access server. The default value is 30. |
EXEC
The mrbranch command sends trace request packets to the specified branch access server. Queries are sent recursively to all the access servers in the branch. This command displays information about the branch starting with the access server farthest away and working towards the requesting access server. This is considered to be the reverse direction.
The information returned shows how a multicast packet sourced by this access server will be forwarded by each access server along the branch.
The access server with the address branch-address responds to the trace request packets. The requesting access server then sends a query to the access server that is the first access server's RPF neighbor. Both the request and response packets have unicast addresses.
The number of packets generated by this command is two times the number of access servers between the source access server and the specified branch access server.
The following is sample output from the mrbranch command. This example is between the same access server as shown in the mbranch command. Note the order of the responses. Also note that the outgoing interface list is the same.
PIM2# mrbranch 172.24.255.2 10.17.118.10
Type escape sequence to abort.
Tracing route to group CBONE-WB (172.24.255.2) from 10.17.118.10
Response from 10.17.118.10, 68 msec
1 10.17.118.10 <- 10.17.20.31
Interface list: 192.168.118.0/26 192.168.118.192/26
Response from PIM-CR (172.16.62.18), 12 msec
1 PIM-CR (172.16.62.18) <- PIM9 (172.16.62.52)
Interface list: 172.16.20.0/24 172.16.53.0/24 172.16.50.0/24
10.16.0.0/16 10.17.0.0/16
Response from PIM9 (172.16.62.52), 8 msec
1 PIM9 (172.16.62.52) <- PIM2 (10.1.37.2)
Interface list: 172.16.22.0/24 172.16.62.0/24 10.7.0.0/16
The mrbranch command is interactive if you specify only the word mrbranch. The following output shows sample responses to the system prompts:
Router#mrbranchTarget IP group address or name:224.0.255.1Target IP router address or name:sj-eng-f2Ttl [30]:10Source address or name:<CR>Interface:ethernet0Type escape sequence to abort. Tracing route to group cbone-audio.cisco.com (224.0.255.1) to 171.69.4.139 Response from sj-eng-f2.cisco.com (171.69.4.139), 4 msec 1 sj-eng-f2.cisco.com (171.69.4.139)<- sj-eng-cc2.cisco.com (171.69.4.135) Interface list: 171.69.60.128/26 Response from sj-eng-f2.cisco.com (171.69.121.2), 4 msec 1 sj-eng-cc2.cisco.com (171.69.121.2)<- 0.0.0.0 Interface list: 171.69.4.0/24
Table 19-5 describes the fields shown in the display.
| Field | Description |
|---|---|
| Tracing route to group CBONE-WB (172.24.255.2) from 10.17.118.10 | Route that is being traced. |
| 68 msec | How long it took to receive the response. |
| Response from 10.17.118.10 | Address of the access server from which the response to the trace request packets came. |
| 1 | Order number of access servers in the trace path. |
| 10.17.118.10 <- 10.17.20.31 | RPF (reverse path forwarding) neighbor information. The first response in this example indicates that a multicast packet sent from the access server PIM2 will be received on interface 10.17.118.10. This multicast packet should have been forwarded from 10.17.20.31 because that is the address that this access server would use as the next-hop access server (found in the IP routing table) to send a unicast packet back to the original source (PIM2) of the multicast packet. |
| Interface list: 192.168.118.0/26 192.168.118.192/26 | Interfaces out which a multicast packet from the access server listed on the right side of the previous line (here, for the group 172.24.255.2 that had been forwarded by 10.17.20.31) will be forwarded. The list does not include interfaces that failed access list conditions or TTL threshold criteria. |
To trace the entire multicast tree for the specified group, use the mtrace user EXEC command.
mtrace {group-address | group-name} [ttl]| group-address | Address of the multicast group. This is a multicast IP address in four-part dotted notation. |
| group-name | Name of the multicast group, as defined in the DNS hosts table or with the ip host command. |
| ttl | (Optional) Time-to-live value. Access servers at a distance of ttl hops from the local access server respond with a record of the path to each of them. The ttl argument can be a number from 0 to 32. The default value is 1, which generates responses from all access servers directly connected to the local access server. |
EXEC
The trace request generated by the mtrace command is multicast to the multicast group. Responses are unicast to the source access server.
Responses are delayed by the responders.
The following is sample output from the mtrace command:
Router> mtrace 172.24.255.1
Type escape sequence to abort.
Tracing route to group CBONE-AUDIO (172.24.255.1)
Response from PIM4 (192.168.36.131), 7 msec
1 PIM4 (192.168.36.131) <- 0.0.0.0
Interface list: 192.168.37.0/24 10.20.0.0/16
Response from PIM3 (192.168.36.130), 4 msec
1 PIM3 (192.168.36.130) <- 0.0.0.0
Interface list: 192.168.35.160/27
Response from PIM4 (192.168.37.33), 2 msec
1 PIM4 (192.168.37.33) <- 0.0.0.0
Interface list: 10.20.0.0/16
Response from PIM9 (10.1.22.9), 20 msec
1 PIM9 (10.1.22.9) <- PIM2 (10.1.37.2)
Interface list: 172.16.62.0/24 172.16.22.0/24 10.7.0.0/16
Response from ITCHY (192.168.37.2), 3 msec
1 ITCHY (192.168.37.2) <- 0.0.0.0
Interface list: Null
Table 19-6 describes the fields shown in the display.
| Field | Description |
|---|---|
| Tracing route to group CBONE-AUDIO (172.24.255.1) | Name and address of group for which routes are being traced. |
| Response from PIM4 (192.168.37.33) | Address of the access server from which the response to the trace request packets came. |
| 7msec | How long it took to receive the response. |
| Interface list: 192.168.37.0/24 10.20.0.0/16 | Interface out which a multicast packet from the access server listed on the right side of the previous line will be forwarded. |
Use this form of the neighbor router configuration command to define a neighboring access server with which to exchange routing information. Use the no form of this command to remove an entry.
neighbor ip-address| ip-address | IP address of a peer access server with which routing information will be exchanged |
No neighboring access servers are defined.
Router configuration
For exterior routing protocol EGP, this command specifies routing peers. For normally broadcast protocols such as IGRP or RIP, this command permits the point-to-point (nonbroadcast) exchange of routing information. When used in combination with the passive-interface router configuration command, routing information can be exchanged between a subset of access servers on a LAN.
Multiple neighbor commands can be used to specify additional neighbors or peers.
OSPF has its own version of the neighbor command. See the neighbor (OSPF) command page in this chapter.
The following example establishes an EGP neighbor:
autonomous-system 109 router egp 110 neighbor 172.16.1.1
In the following example, IGRP updates are sent to all interfaces on network 172.16.0.0 except Ethernet interface 1. However, in this case a neighbor router configuration command is included. This command permits the sending of routing updates to specific neighbors. One copy of the routing update is generated per neighbor.
router igrp 109 network 172.16.0.0 passive-interface ethernet 1 neighbor 172.16.20.4
Use this form of the neighbor router configuration command to configure OSPF access servers interconnecting to nonbroadcast networks. Use the no form of this command with the appropriate IP address and arguments to remove the configuration.
neighbor ip-address [priority number] [poll-interval seconds]| ip-address | Interface IP address of the neighbor. |
| priority number | (Optional) 8-bit number indicating the access server priority value of the nonbroadcast neighbor associated with the IP address specified. The default is 0. |
| poll-interval seconds | (Optional) Unsigned integer value reflecting the poll interval. RFC 1247 recommends that this value should be much larger than the Hello interval. The default is 2 minutes (120 seconds). |
No configuration is specified.
Router configuration
X.25 and Frame Relay provide an optional broadcast capability that can be configured in the map to allow OSPF to run as a broadcast network. At the OSPF level you can configure the access server as a broadcast network. See the x25 map and frame-relay map interface configuration command descriptions in "X.25 Commands" and "Frame Relay Commands" chapters, respectively, of this manual for more detail.
One neighbor entry must be included in the access server's configuration for each known nonbroadcast network neighbor. The neighbor address has to be on the primary address of the interface.
If a neighboring access server has become inactive (Hello packets have not been seen for the Router DeadInterval period), it may still be necessary to send Hello packets to the dead neighbor. These Hello packets will be sent at a reduced rate called Poll Interval.
When the access server first starts up, it sends only Hello packets to those access servers with non-zero priority, that is, access servers that are eligible to become designated routers and backup designated routers. After designated routers and backup designated routers are selected, they will then start sending Hello packets to all neighbors in order to form adjacencies.
The following example declares an access server at address 172.16.3.4 on a nonbroadcast network, with a priority of 1 and a poll-interval of 180:
router ospf neighbor 172.16.3.4 priority 1 poll-interval 180
Use the neighbor advertisement-interval router configuration command to set the minimum interval between sending BGP routing updates. Use the no form of this command to remove an entry.
neighbor {ip-address | peer-group-name} advertisement-interval seconds| ip-address | Neighbor's IP address. |
| peer-group-name | Name of a BGP peer group. |
| seconds | Time in seconds. Integer from 0 through 600. |
30 seconds for external peers and 5 seconds for internal peers.
Router configuration
In the following example, the minimum time between sending BGP routing updates is set to
10 seconds:
router bgp 5 neighbor 10.4.4.4 advertisement-interval 10
Use the neighbor any router configuration command to control how neighbor entries are added to the routing table for both EGP and BGP. Use the no form of this command to remove the configuration.
neighbor any [access-list-number]| access-list-number | (Optional) Access list number the neighbor must be accepted by to be allowed to peer with the EGP or BGP process. If no list is specified, any neighbor will be allowed to peer with the access server. |
No configuration is specified.
Router configuration
In the following example, only neighbors permitted by access list 1 are allowed to peer with the local router:
access-list 1 permit 10.0.0.0 0.255.255.255 ! global access list assignment router egp 0 neighbor any 1
A dagger (+) indicates that the command is documented in another chapter.
access-list +
neighbor any third-party
router egp 0
Use the neighbor any third-party router configuration command to configure an EGP process that determine which neighbors will be treated as the next hop in EGP advertisements. Use the no form of this command to remove the configuration.
neighbor any third-party ip-address [internal | external]| ip-address | IP address of the third-party access server that is to be the next hop in EGP advertisements. |
| internal | (Optional) Indicates that the third-party access server should be listed in the internal section of the EGP update. |
| external | (Optional) Indicates that the third-party access server should be listed in the external section of the EGP update. |
No EGP process is configured.
Router configuration
The following example specifies the particular neighbors that an EGP process will view as peers:
access-list 2 permit 10.0.0.0 0.255.255.255 ! global access list assignment router egp 0 neighbor any 2 neighbor any third-party 10.1.1.1
Use the neighbor configure-neighbors router configuration command to instruct the access server to treat temporary neighbors that have been accepted by a template as if they had been configured by hand. The no form of this command causes any new neighbor accepted by the template to be treated as temporary.
neighbor template-name configure-neighbors| template-name | A user selectable designation that identifies a particular template (an arbitrary word). |
New neighbors are treated as temporary.
Router configuration
Under normal circumstances, neighbors that are allowed to connect to the access server because you had configured a template are treated as temporary. When a temporary neighbor disconnects, the local access server will not try to actively reestablish a connection with it. In addition, information about temporary neighbors will not show up in the access server configuration (show running-config).
When configure-neighbors is enabled on a particular template, any neighbor accepted by that template will be treated as if it had been manually configured. These neighbors will show up in show running-config displays and will be written to the nonvolatile configuration if a copy running-config startup-config command is issued.
In the following example, any BGP speaker matching access-list 7 can connect to the access server and exchange information. Any neighbor that connects will be treated as if it had been manually configured.
access-list 7 permit 172.29.3.0 0.0.0.255 neighbor internal-ethernet neighbor-list 7 neighbor internal-ethernet configure-neighbors
To allow a BGP speaker (the local router) to send the default route 0.0.0.0 to a neighbor for use as a default route, use the neighbor default-originate router configuration command. To remove the default route, use the no form of this command.
neighbor {ip-address | peer-group-name} default-originate [route-map map-name]| ip-address | Neighbor's IP address. |
| peer-group-name | Name of a BGP peer group. |
| map-name | (Optional) Name of the route map. The route map allows route 0.0.0.0 to be injected conditionally. |
No default route is sent to the neighbor.
Router configuration
This command does not require the presence of 0.0.0.0 in the local router. When used with a route map, the default route 0.0.0.0 is injected if the route map contains a match ip address clause and there is a route that matches the IP access list exactly. The route map can contain other match clauses also.
In the following example, the local router injects route 0.0.0.0 to the neighbor 160.89.2.3 unconditionally:
router bgp 109 network 160.89.0.0 neighbor 160.89.2.3 remote-as 200 neighbor 160.89.2.3 default-originate
In the following example, the local router injects route 0.0.0.0 to the neighbor 160.89.2.3 only if there is a route to 198.92.68.0:
router bgp 109 network 160.89.0.0 neighbor 160.89.2.3 remote-as 200 neighbor 160.89.2.3 default-originate route-map default-map ! route-map default-map 10 permit match ip address 1 ! access-list 1 permit 198.92.68.0
Use the neighbor distribute-list router configuration command to distribute BGP neighbor information as specified in an access list. Use the no form of this command to remove an entry.
neighbor {ip-address | peer-group-name} distribute-list access-list-number {in | out}| ip-address | Neighbor's IP address. |
| peer-group-name | Name of a BGP peer group. |
| access-list-number | Predefined access list number. Only standard access lists can be used with this command. |
| in | Access list is applied to incoming advertisements to that neighbor. |
| out | Access list is applied to outgoing advertisements from that neighbor. |
No BGP neighbor is specified.
Router configuration
Using distribute lists is one of two ways to filter BGP advertisements. The other way is to use autonomous system-path filters, as with the ip as-path access-list global configuration command and the neighbor
filter-list command.
If you specify a BGP peer group by using the peer-group-name argument, all of the members of the peer group will inherit the characteristic configured with this command. Specifying the command with an IP address will override the value inherited from the peer group.
The following example applies list 39 to incoming advertisements to neighbor 172.23.4.1:
router bgp 109 network 172.16.0.0 neighbor 172.23.4.1 distribute-list 39 in
ip as-path access-list
neighbor filter-list
Use the neighbor ebgp-multihop router configuration command to accept and attempt BGP connections to external peers residing on networks that are not directly connected. Use the no form of this command to return to the default of allowing only directly connected neighbors.
neighbor {ip-address | peer-group-name} ebgp-multihop| ip-address | IP address of the BGP-speaking neighbor. |
| peer-group-name | Name of a BGP peer group. |
Only directly connected neighbors are allowed.
Router configuration
This feature should only be used under the guidance of technical support staff.
If you specify a BGP peer group by using the peer-group-name argument, all of the members of the peer group will inherit the characteristic configured with this command.
The following example allows connections to or from neighbor 172.16.1.1, which resides on a network that is not directly connected:
router bgp 109 neighbor 172.16.1.1 ebgp-multihop
Use the neighbor filter-list router configuration command to set up BGP filters, using access lists defined with the ip as-path access-list command. Use the no form of this command to disable this function.
neighbor {ip-address | peer-group-name} filter-list access-list-number {in | out || ip-address | IP address of the neighbor. |
| peer-group-name | Name of a BGP peer group. |
| access-list-number | Number of an access for the autonomous system path. You define this access list with the ip as-path access-list command. |
| in | Access list to incoming routes. |
| out | Access list to outgoing routes. |
| weight weight | Assigns a relative importance to incoming routes matching autonomous system paths. Acceptable values are 0 to 65535. |
Disabled
Router configuration
This command establishes filters on both inbound and outbound BGP routes. Any number of weight filters are allowed on a per-neighbor basis, but only one in or out filter is allowed. The weight of a route affects BGP's route-selection rules.
The implemented weight is based on the first matched autonomous system path. Weights indicated when an autonomous system path is matched override the weights assigned by global neighbor commands. In other words, the weights assigned with the match as-path and set weight route-map commands override the weights assigned using the neighbor weight and neighbor filter-list commands.
See the "Regular Expressions" appendix for information on forming regular expressions.
If you specify a BGP peer group by using the peer-group-name argument, all of the members of the peer group will inherit the characteristic configured with this command. Specifying the command with an IP address will override the value inherited from the peer group.
In the following example, the BGP neighbor with IP address 172.28.1.1 is not sent advertisements about any path through or from the adjacent autonomous system 123:
ip as-path access-list 1 deny _123_ ip as-path access-list 1 deny ^123 .* ! The space in the above expression (^123 .*)is required. router bgp 109 network 172.16.0.0 neighbor 172.29.6.6 remote-as 123 neighbor 172.28.1.1 remote-as 47 neighbor 172.28.1.1 filter-list 1 out
ip as-path access-list
neighbor distribute-list
neighbor weight
Use the neighbor neighbor-list router configuration command to configure BGP to support anonymous neighbor peers by configuring a neighbor template. Use the no form of this command to delete the template, and also cause any temporary neighbors accepted by the template to be shut down and removed.
neighbor template-name neighbor-list access-list-number| template-name | A user selectable designation that identifies a particular template (an arbitrary word). |
| access-list-number | An IP access list number in the range 1 through 99. |
No configuration is defined.
Router configuration
To specify a group of anonymous neighbors, configure a neighbor template rather than specifically configure each neighbor. The template allows you to specify an IP access list which defines remote systems that can establish a BGP connection to the access server. External BGP peers must be on a directly connected Ethernet unless they are overridden by the neighbor ebgp-multihop command.
Once you specify a template, you configure the template as if it were a regular neighbor entry, such as setting the protocol version or filter lists, so that anonymous neighbors accepted by the template will receive the settings of the template.
These neighbors accepted by the template appear in the show ip bgp summary and show ip bgp neighbor displays, although they do not appear in the access server configuration. When the session is disconnected, all knowledge about the neighbor is discarded and the access server will not attempt to actively re-establish a connection.
You can use the neighbor configure-neighbors command to request that the access server treat peers learned through a template as if they were manually configured neighbors. These peers will then show up in show running-config displays and can be stored as part of the nonvolatile configuration.
In the following example, any BGP speaker from 172.29.3.0 can connect to the access server and exchange information:
access-list 7 permit 172.29.3.0 0.0.0.255 neighbor internal-ethernet neighbor-list 7 neighbor internal-ethernet configure-neighbors
In the following example, any BGP speaker in the connected internet can establish a BGP connection to the local access server, and the local access server will send them routing information. However, the distribute-list clause instructs the local access server to ignore all information these remote BGP speakers send to it.
access-list 9 permit 0.0.0.0 255.255.255.255 access-list 10 deny 0.0.0.0 255.255.255.255 neighbor route-server-peers neighbor-list 9 neighbor route-server-peers distribute-list 10 in
A dagger (+) indicates that the command is documented in another chapter.
access-list (standard) +
neighbor configure-neighbors
neighbor ebgp-multihop
Use the neighbor next-hop-self router configuration command to configure the access server to disable next-hop processing on BGP updates. Use the no form of this command to disable this feature.
neighbor ip-address next-hop-self| ip-address | IP address of the BGP-speaking neighbor |
Disabled
Router configuration
This command is useful in nonmeshed networks such as Frame Relay or X.25 where BGP neighbors may not have direct access to all other neighbors on the same IP subnet.
If you specify a BGP peer group by using the peer-group-name argument, all of the members of the peer group will inherit the characteristic configured with this command. Specifying the command with an IP address will override the value inherited from the peer group.
The following example forces all updates destined for 172.16.1.1 to advertise this access server as the next hop:
router bgp 109 neighbor 172.16.1.1 next-hop-self
To enable MD5 authentication on a TCP connection between two BGP peers, use the neighbor password router configuration command. To disable this feature, use the no form of this command.
neighbor {ip-address | peer-group-name} password string| ip-address | IP address of the BGP-speaking neighbor. |
| peer-group-name | Name of a BGP peer group. |
| string | Case-sensitive password of up to 80 characters. The first character cannot be a number. The string can contain any alphanumeric characters, including spaces. You cannot specify a password in the format number-space-anything. The space after the number causes problems. |
Disabled
Router configuration
You can invoke authentication between two BGP peers, causing each segment sent on the TCP connection between them to be verified. This feature must be configured with the same password on both BGP peers; otherwise, the connection between them will not be made. The authentication feature uses the MD5 algorithm. Specifying this command causes the generation and checking of the MD5 digest on every segment sent on the TCP connection.
Configuring a password for a neighbor causes existing sessions to be torn down and a new one made.
If you specify a BGP peer group by using the peer-group-name argument, all of the members of the peer group will inherit the characteristic configured with this command.
If a router has a password configured for a neighbor, but the neighbor router does not, a message like the following will appear on the console while the routers attempt to establish a BGP session between them:
%TCP-6-BADAUTH: No MD5 digest from [peer's IP address]:11003 to [local router's IP address]:179
Similarly, if the two routers have different passwords configured, a message like the following will appear on the console:
%TCP-6-BADAUTH: Invalid MD5 digest from [peer's IP address]:11004 to [local router's IP address]:179
The following example enables the authentication feature between this router and the BGP neighbor at 172.16.1.1. The password that must also be configured for the neighbor is bla4u00=2nkq.
router bgp 109 neighbor 172.16.1.1 password bla4u00=2nkq
neighbor peer-group (creating)
To create a BGP peer group, use the neighbor peer-group router configuration command. To remove the peer group and all of its members, use the no form of this command.
neighbor peer-group-name peer-group| peer-group-name | Name of the BGP peer group. |
There is no BGP peer group.
Router configuration
Often in a BGP speaker, there are many neighbors configured with the same update policies (that is, same outbound route maps, distribute lists, filter lists, update source, and so on). Neighbors with the same update policies can be grouped into peer groups to simplify configuration and make update calculation more efficient.
Once a peer group is created with the neighbor peer-group command, it can be configured with the neighbor commands. By default, members of the peer group inherit all of the configuration options of the peer group. Members can also be configured to override the options that do not affect outbound updates.
Peer group members will always inherit the following: remote-as (if configured), version, update-source, out-route-map, out-filter-list, out-dist-list, minimum-advertisement-interval, and next-hop-self. All of the peer group members will inherit changes made to the peer group.
If a peer group is not configured with a remote-as, the members can be configured with the neighbor {ip-address | peer-group-name} remote-as command. This allows you to create peer groups containing EBGP neighbors.
In the following example, the peer group named internal configures the members of the peer group to be IBGP neighbors. By definition, this is an IBGP peer group because the router bgp command and the neighbor remote-as command indicate the same autonomous system (in this case, AS 100). All the peer group members use loopback 0 as the update source and use set-med as the outbound route-map. The inbound filter-list command shows that except 171.69.232.55 all the neighbor has filter-list 2 as the inbound filter list.
router bgp 100 neighbor internal peer-group neighbor internal remote-as 100 neighbor internal update-source loopback 0 neighbor internal route-map set-med out neighbor internal filter-list 1 out neighbor internal filter-list 2 in neighbor 172.19.232.53 peer-group internal neighbor 172.19.232.54 peer-group internal neighbor 172.19.232.55 peer-group internal neighbor 172.19.232.55 filter-list 3 in
In the following example, the peer group external-peers is defined without the neighbor remote-as command. This is what makes it an EBGP peer group. Each individaul member of the peer group is configured with its respective AS-number separately. Thus the peer group consists of members from autonomous systems 200, 300 and 400. All the peer group members have set-metric route map as an outbound route map and filter-list 99 as an outbound filter list. Except for neighbor 172.19.232.110, all of them have 101 as the inbound filter list.
router bgp 100 neighbor external-peers peer-group neighbor external-peers route-map set-metric out neigbhor external-peers filter-list 99 out neighbor external-peers filter-list 101 in neighbor 172.19.232.90 remote-as 200 neighbor 172.19.232.90 peer-group external-peers neighbor 172.19.232.100 remote-as 300 neighbor 172.19.232.100 peer-group external-peers neighbor 172.19.232.110 remote-as 400 neighbor 172.19.232.110 peer-group external-peers neighbor 172.19.232.110 filter-list 400 in
clear ip bgp peer-group
neighbor peer-group (creating)
neighbor peer-group (assigning members)
show ip bgp peer-group
To configure a BGP neighbor to be a member of a peer group, use the neighbor peer-group router configuration command. To remove the neighbor from the peer group, use the no form of this command.
neighbor ip-address peer-group peer-group-name| ip-address | IP address of the BGP neighbor who belongs to the peer group specified by the tag. |
| peer-group-name | Name of the BGP peer group to which this neighbor belongs. |
There are no BGP neighbors in a peer group.
Router configuration
The neighbor at the IP address indicated inherits all the configured options of the peer group.
In the following example,
router bgp 100 neighbor internal peer-group neighbor internal remote-as 100 neighbor internal update-source loopback 0 neighbor internal route-map set-med out neighbor internal filter-list 1 out neighbor internal filter-list 2 in neighbor 172.19.232.53 peer-group internal neighbor 172.19.232.54 peer-group internal neighbor 172.19.232.55 peer-group internal neighbor 172.19.232.55 filter-list 3 in
neighbor peer-group (creating)
neighbor remote-as
Use the neighbor remote-as router configuration command to add an entry to the BGP neighbor table. Use the no form of this command to remove a neighbor.
neighbor {ip-address | peer-group-name} remote-as number| ip-address | Neighbor's IP address. |
| peer-group-name | Name of a BGP peer group. |
| number | Autonomous system to which the neighbor belongs. |
There are no BGP neighbor peers.
Router configuration
Specifying a neighbor with an autonomous system number that matches the autonomous system number specified in the router bgp global configuration command identifies the neighbor as internal to the local autonomous system. Otherwise, the neighbor is considered external.
If you specify a BGP peer group by using the peer-group-name argument, all of the members of the peer group will inherit the characteristic configured with this command.
The following example specifies that the access server at the address 172.16.1.2 is a neighbor in autonomous system number 109:
router bgp 110 network 172.16.0.0 neighbor 172.16.1.2 remote-as 109
In the following example, a BGP access server is assigned to autonomous system 109, and two networks are listed as originating in the autonomous system. Then the addresses of three remote access servers (and their autonomous systems) are listed. The access server being configured will share information about networks 172.16.0.0 and 192.168.7.0 with the neighbor access servers. The first access server listed is in the same Class B network address space, but in a different autonomous system; the second neighbor command illustrates specification of an internal neighbor (with the same autonomous system number) at address 172.16.234.2; and the last neighbor command specifies a neighbor on a different network.
router bgp 109 network 172.16.0.0 network 192.168.7.0 neighbor 172.16.200.1 remote-as 167 neighbor 172.16.234.2 remote-as 109 neighbor 172.50.64.19 remote-as 99
Use the neighbor route-map router configuration command to apply a route map to incoming or outgoing routes. Use the no form of this command to remove the entry.
neighbor {ip-address | peer-group-name} route-map route-map-name {in | out}| ip-address | Neighbor's IP address. |
| peer-group-name | Name of a BGP peer group. |
| route-map-name | Name of route map. |
| in | Apply to incoming routes. |
| out | Apply to outgoing routes. |
No route maps are applied to a peer.
Router configuration
If an outbound route map is specified, it is proper behavior to only advertise routes that match at least one section of the route map.
If you specify a BGP peer group by using the peer-group-name argument, all of the members of the peer group will inherit the characteristic configured with this command. Specifying the command with an IP address will override the value inherited from the peer group.
In the following example, route map "internal-map" is applied to incoming route from 192.168.70.24:
router bgp 5 neighbor 192.168.70.24 route-map internal-map in ! route-map internal-map match as-path 1 set local-preference 100
To specify that a COMMUNITIES attribute should be sent to a BGP neighbor, use the neighbor send-community router configuration command. To remove the entry, use the no form of this command.
neighbor {ip-address | peer-group-name} send-community| ip-address | Neighbor's IP address. |
| peer-group-name | Name of a BGP peer group. |
No COMMUNITIES attribute is sent to any neighbor.
Router configuration
If you specify a BGP peer group by using the peer-group-name argument, all of the members of the peer group will inherit the characteristic configured with this command.
In the following example, the router belongs to autonomous system 109 and is configured to send the communities attribute to its neighbor at IP address 192.168.70.23:
router bgp 109 neighbor 192.168.70.23 send-community
ip community-list
match community-list
set community
Use the neighbor third-party router configuration command to send updates regarding EGP third-party access servers. Use the no form of this command to disable these updates.
neighbor ip-address third-party third-party-ip-address [internal | external]| ip-address | IP address of the EGP peer. |
| third-party-ip-address | Address of the third-party access server on the network shared by the Cisco access server and the EGP peer specified by address. |
| internal | (Optional) Indicates that the third-party access server should be listed in the internal section of the EGP update. This is the default. |
| external | (Optional) Indicates that the third-party access server should be listed in the external section of the EGP update. |
Disabled
Router configuration
Using this third-party mechanism, EGP tells its peer that another access server (the third party) on the shared network is the appropriate access server for some set of destinations. If updates mentioning third-party access servers are desired, use this command.
All networks reachable through the third-party access server will be listed in the EGP updates as reachable by the access server. The optional internal and external keywords indicate whether the third-party access server should be listed in the internal or external section of the EGP update. Normally, all networks are mentioned in the internal section.
This command can be used multiple times to specify additional third-party access servers.
In the following example, routes learned from access server 172.16.6.99 will be advertised to 172.16.6.5 as third-party internal routes:
neighbor 172.16.6.5 third-party 172.16.6.99 internal
In the following example, routes learned from 172.16.6.100 will be advertised to 172.16.6.5 as third-party external routes:
neighbor 172.16.6.5 third-party 172.16.6.100 external
Use the neighbor update-source router configuration command to configure the access server to allow internal BGP sessions to use any operational interface for TCP connections. Use the no form of this command to restore the interface assignment to the closest interface, also called the
best-local-address.
| ip-address | IP address of the BGP-speaking neighbor. |
| peer-group-name | Name of a BGP peer group. |
| interface | Loopback interface. |
Best-local-address
Router configuration
This feature works in conjunction with the Loopback interface feature described in the "Configuring Interfaces" chapter of the Access and Communication Servers Configuration Guide.
If you specify a BGP peer group by using the peer-group-name argument, all of the members of the peer group will inherit the characteristic configured with this command.
In the following example, BGP TCP connections for the specified neighbor will be sourced with Loopback interface's IP address rather than the best-local-address:
router bgp 110 network 192.168.0.0 neighbor 192.168.2.3 remote-as 110 neighbor 192.168.2.3 update-source Loopback0
Use the neighbor version router configuration command to configure the access server to accept only a particular version. Use the no form of this command to return the version to the default level of that neighbor.
neighbor {ip-address | peer-group-name} version value| ip-address | IP address of the BGP-speaking neighbor. |
| peer-group-name | Name of a BGP peer group. |
| value | BGP version number. The version can be set to 2 to force the router to only use Version 2 with the specified neighbor. The default is to use Version 4 and dynamically negotiate down to Version 2 if requested. |
Version 4
Router configuration
Entering this command disables dynamic version negotiation.
Our implementation of BGP supports Versions 2, 3, and 4 of BGP. If the neighbor does not accept default version 4, dynamic version negotiation is implemented to negotiate down to version 2.
Our implementation of BGP supports BGP Versions 2, 3, and 4. If the neighbor does not accept default Version 4, dynamic version negotiation is implemented to negotiate down to Version 2.
If you specify a BGP peer group by using the peer-group-name argument, all of the members of the peer group will inherit the characteristic configured with this command.
The following example locks down to Version 4 of the BGP protocol:
router bgp 109 neighbor 172.18.27.2 version 4
Use the neighbor weight router configuration command to specify a weight to assign to a specific neighbor connection. Use the no form of this command to remove the assignment.
neighbor {ip-address | peer-group-name} weight weight| ip-address | Neighbor's IP address. |
| peer-group-name | Name of a BGP peer group. |
| weight | Weight to assign. Acceptable values are 0 to 65535. |
Routes learned through another BGP peer have a default weight of 0 and routes sourced by the local access server have a default weight of 32768.
Router configuration
All routes learned from this neighbor will have the assigned weight initially. The route with the highest weight will be chosen as the preferred route when multiple routes are available to a particular network.
The weights assigned with the match as-path and set weight route-map commands override the weights assigned using the neighbor weight and neighbor filter-list commands.
If you specify a BGP peer group by using the peer-group-name argument, all of the members of the peer group will inherit the characteristic configured with this command.
The following example sets the weight of all routes learned via 172.23.12.1 to 50:
router bgp 109 neighbor 172.23.12.1 weight 50
neighbor distribute-list
neighbor filter-list
Use this form of the network router configuration command to specify the list of networks for the BGP routing process. Use the no form of this command to remove the entry.
network network-number mask network-mask| network-number | IP address of a peer access server with which routing information will be exchanged. |
| mask | Network or subnetwork mask. |
| network-mask | Network mask address. |
No networks are specified.
Router configuration
These types of networks can be learned from connected routes, dynamic routing, and from static route sources.
A maximum of 200 network commands may be specified for a single BGP process.
The following example sets up network 172.16.1.27 to be included in the access server's BGP updates:
router bgp 120 network 172.16.1.27 mask 255.255.255.0
network backdoor
network mask
network weight
router bgp
Use this form of the network router configuration command to specify the list of networks for the EGP routing process. Use the no form of this command to remove a network from the list.
network network-number| network-number | IP address of a peer access server with which routing information will be exchanged. |
No networks are specified.
Router configuration
The networks to be advertised to the EGP peers of an EGP routing process are advertised with a distance of zero. The restrictions on the network you specify are that it must appear in the routing table, and the network number must not contain any subnet information. The network can be connected, statically configured, or redistributed into EGP from other routing protocols. Multiple commands can be used to specify additional networks.
The following example illustrates a typical configuration for an EGP access server process. The access server is in autonomous system 109 and is peering with access servers in autonomous system 164. It will advertise the networks 172.16.0.0 and 192.168.7.0 to the access server in autonomous system 164, 10.2.0.2. The information sent and received from peer access servers can be filtered in various ways, including blocking information from certain access servers and suppressing the advertisement of specific routes.
autonomous-system 109 router egp 164 network 172.16.0.0 network 192.168.7.0 neighbor 10.2.0.2
To specify a list of networks for the IP Enhanced IGRP routing process, use the network router configuration command. To remove a network from the list, use the no form of this command.
network network-number| network-number | IP address of the directly connected network. |
Disabled
Router configuration
The network number must not contain any subnet information. You can specify multiple network commands.
IP Enhanced IGRP sends updates to the interfaces in the specified network(s). Also, if you do not specify an interface's network, it will not be advertised in any IP Enhanced IGRP updates.
The following example configures an access server for IP Enhanced IGRP and assigns autonomous system number 109. The network commands indicate the networks directly connected to the access server.
router eigrp 109 network 172.16.0.0 network 192.168.7.0
Use this form of the network router configuration command to specify a list of networks for the IGRP routing process. Use the no form of this command to remove a network from the list.
network network-number| network-number | IP address of the directly connected networks. |
No networks are specified.
Router configuration
The network number specified must not contain any subnet information. You can specify multiple network commands.
IGRP sends updates to the interfaces in the specified network(s). Also, if an interface's network is not specified, it will not be advertised in any IGRP update.
The following example configures an access server for IGRP and assigns autonomous system 109. The network commands indicate the networks directly connected to the access server.
router igrp 109 network 172.16.0.0 network 192.168.7.0
Use this form of the network router configuration command to specify a list of networks for the RIP routing process. Use the no form of this command to remove a network from the list.
network network-number| network-number | IP address of the network of directly connected networks. |
No networks are specified.
Router configuration
The network number specified must not contain any subnet information. You can specify multiple network commands. RIP routing updates will be sent and received only through interfaces on this network.
RIP sends updates to the interfaces in the specified networks. Also, if an interface's network is not specified, it will not be advertised in any RIP update.
The following example defines RIP as the routing protocol to be used on all interfaces connected to networks 172.19.0.0 and 192.168.7.0:
router rip network 172.19.0.0 network 192.168.7.0
Use the network area router configuration command to define the interfaces on which OSPF runs and to define the area ID for those interfaces. Use the no form of this command to disable OSPF routing for interfaces defined with the address wildcard-mask pair; you must specify the complete address range and area ID.
network address wildcard-mask area area-id| address | IP address. |
| wildcard-mask | IP-address-type mask that includes "don't care" bits. |
| area-id | Area that is to be associated with the OSPF address range. It can be specified as either a decimal value or as an IP address. If you intend to associate areas with IP subnets, you can specify a subnet address as the area-id. |
Disabled
Router configuration
The address and wildcard-mask arguments together allow you to define one or multiple interfaces to be associated with a specific OSPF area using a single command. Using the wildcard-mask allows you to define one or multiple interfaces to be associated with a specific OSPF area using a single command. If you intend to associate areas with IP subnets, you can specify a subnet address as the area-id.
The access server sequentially evaluates the address/wildcard-mask pair for each interface as follows:
In the following partial example, OSPF routing process 109 is initialized, and four OSPF areas are defined: 10.9.50.0, 2, 3, and 0. Areas 10.9.50.0, 2, and 3 mask specific address ranges, while Area 0 enables OSPF for all other networks.
router ospf 109 network 172.16.20.0 0.0.0.255 area 10.9.50.0 network 172.16.0.0 0.0.255.255 area 2 network 172.19.10.0 0.0.0.255 area 3 network 0.0.0.0 255.255.255.255 area 0
Use the network backdoor router configuration command to specify a backdoor route to a BGP border access server that will provide better information about the network. Use the no form of this command to remove an address from the list.
network address backdoor| address | IP address of the network to which you want a backdoor route |
No network is advertised.
Router configuration
A backdoor network is treated as a local network, except that it is not advertised.
The following example configures network 172.16.0.0 as a local network and network 192.168.7.0 as a backdoor network:
router bgp 109 network 172.16.0.0 network 192.168.7.0 backdoor
Use the network weight router configuration command to assign an absolute weight, or importance, to a BGP network. Use the no form of this command to delete the entry.
network address weight weight| address | IP address of the network. |
| weight weight | Absolute weight. Integer from 0 to 65535. |
Weight is unmodified. Weight is zero if the original default weight has not been modified by other router configuration commands.
Router configuration
The weight specified by this command overrides a weight assigned by the redistribute command.
The following example assigns network 192.168.0.0 an absolute weight of 100:
router bgp 5 network 192.168.0.0 weight 100
To add an offset to incoming and outgoing metrics to routes learned via RIP and IGRP, use the offset-list access server configuration command. To remove an offset list, use the no form of this command.
offset-list {in | out} offset [access-list-number | [interface type interface number]]| in | Applies the access list to incoming metrics. |
| out | Applies the access list to outgoing metrics. |
| offset | Positive offset to be applied to metrics for networks matching the access list. If the offset is zero, no action is taken. |
| access-list-number | (Optional) Access list to be applied. If unspecified, the argument supplied to offset is applied to all metrics. If offset is zero, no action is taken. For IGRP, the offset is added to the delay component only. Must be a standard access list. |
| interface-type | (Optional) Interface type to which the offset-list is applied. |
| interface-number | (Optional) Interface number to which the offset-list is applied. |
Disabled
Router configuration
The offset value is added to the routing metric. An offset-list with an interface type and interface number is considered extended and takes precedence over an offset-list that is not extended. Therefore, if an entry passes the extended offset-list and the normal offset-list, the extended offset-list's offset is added to the metric.
The following example applies an offset of 10 to the access server's delay component for all outgoing metrics:
offset-list out 10
In the following example, the access server applies the same offset in the previous example only to access list 121:
offset-list out 10 121
In the following example of an extended offset-list, the access server applies the offset of 10 to routes learned from Ethernet interface 0:
offset-list in 10 ethernet 0
To control how OSPF calculates default metrics for the interface, use the ospf auto-cost determination router configuration command. To disable this feature, use the no form of this command.
ospf auto-cost determinationThis command has no arguments or keywords.
Enabled
Router configuration
In Cisco IOS Release 10.2 and earlier, OSPF assigns default OSPF metrics to interfaces regardless of the interface bandwidth. It gives both 64K and T1 links the same metric (1562), and thus requires an explicit ip ospf cost command in order to take advantage of the faster link.
In Cisco IOS Release 10.3, by default OSPF will calculate the OSPF metric for an interface according to the bandwidth of the interface. For example, a 64K link will get a metric of 1562, while a T1 link will have a metric of 64.
The OSPF metric is calculated as metric-scale / bandwidth, with metric-scale equal to 108 by default, which gives FDDI, for example, a metric of 1.
The following example causes a fixed default metric assignment, regardless of interface bandwidth:
router ospf 1 no ospf auto-cost-determination
Use the passive-interface router configuration command to disable sending routing updates on an interface. Use the no form of this command to reenable sending routing updates on the specified interface.
passive-interface type number| type | Interface type |
| number | Interface number |
Routing updates are sent on the interface.
Router configuration
If you disable the sending of routing updates on an interface, the particular subnet will continue to be advertised to other interfaces, and updates from other access servers on that interface continue to be received and processed.
IP Enhanced IGRP is disabled on an interface that is configured as passive although it advertises the route.
For OSPF, OSPF routing information is neither sent nor received through the specified access server interface. The specified interface address appears as a stub network in the OSPF domain.
The following example sends IGRP updates to all interfaces on network 172.16.0.0 except Ethernet interface 1:
router igrp 109 network 172.16.0.0 passive-interface ethernet 1
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 a16-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 access server. 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 router configuration 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 access server 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 between 0 and 65535. |
| subnets | (Optional) For redistributing routes into OSPF, the scope of redistribution for the specified protocol. |
Route redistribution is disabled.
protocol--No source protocol is defined.
process-id--No process ID is defined.
metric metric-value--0
metric-type type-value--Type 2 external route
match internal | external--internal
external type-value--internal
tag tag-value--If no value is specified, the remote autonomous system number is used for routes
from BGP and EGP; for other protocols, the default is 0.
route-map map-tag--If the route-map argument is not entered, all routes are redistributed; if no
map-tag value is entered, no routes are imported.
weight weight--No network weight is defined.
subnets--No subnets are defined.
Router configuration
Changing or disabling any keyword will not affect the state of other keywords.
A access server receiving a link-state protocol (LSP) with an internal metric will consider the cost of the route from itself to the redistributing access server plus the advertised cost to reach the destination. An external metric only considers the advertised metric to reach the destination.
Routes learned from IP routing protocols can be redistributed at level-1 into an attached area or at level-2. The keyword level-1-2 allows both in a single command.
Redistributed routing information should always be filtered by the distribute-list out router configuration command. This ensures that only those routes intended by the administrator are passed along to the receiving routing protocol.
Whenever you use the redistribute or the default-information router configuration commands to redistribute routes into an OSPF routing domain, an access server acting as an access server automatically becomes an Autonomous System Boundary Router (ASBR). However, an ASBR does not, by default, generate a default route into the OSPF routing domain.
When routes are redistributed between OSPF processes, no OSPF metrics are preserved.
When routes are redistributed into OSPF and no metric is specified in the metric keyword, the default metric that OSPF uses is 20 for routes from all protocols except BGP route, which gets a metric of 1.
When redistributing routes into OSPF, only routes that are not subnetted are redistributed if the subnets keyword is not specified.
The only connected routes affected by this redistribute command are the routes not specified by the network command.
You cannot use the default-metric command to affect the metric used to advertise connected routes.
Default redistribution of IGPs or EGP into BGP is not allowed unless default-information originate is specified.
When routes are redistributed into OSPF and no metric is specified in the metric keyword, the default metric that OSPF uses is 20 for routes from all protocols except BGP route, which gets a metric of 1.
The following are examples of the various configurations you would use to redistribute one routing protocol into another routing protocol.
The following example configuration causes OSPF routes to be redistributed into a BGP domain:
router bgp 109 redistribute ospf...
The following example configuration causes IGRP routes to be redistributed into an OSPF domain:
router ospf 110 redistribute igrp...
The following example causes the specified IGRP process routes to be redistributed into an OSPF domain. The IGRP-derived metric will be remapped to 100 and RIP routes to 200.
router ospf 109 redistribute igrp 108 metric 100 subnets redistribute rip metric 200 subnets
In the following example, BGP routes are configured to be redistributed into IS-IS. The link-state cost is specified as 5, and the metric type will be set to external, indicating that it has lower priority than internal metrics.
router isis redistribute bgp 120 metric 5 metric-type external
default-information allowed
distribute-list out
route-map
show route-map
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 route-map 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. 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. |
| deny | (Optional) If the match criteria are met for the route map, and deny is specified, the route is not redistributed, and no further route maps sharing the same map tag name will be examined. |
| 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. |
No default available.
Global configuration
Use route maps to redistribute routes or to subject packets to policy routing. Both purposes are described in this section.
The following example redistributes all OSPF routes into IGRP:
router igrp 109 redistribute ospf 110 default metric 1000 100 255 1 1500
The following example redistributes RIP routes with a hop count equal to 1 into OSPF. These routes will be redistributed into OSPF as external link state advertisements with a metric of 5, metric type of Type 1 and a tag equal to 1.
router ospf 109 redistribute rip route-map rip-to-ospf route-map rip-to-ospf permit match metric 1 set metric 5 set metric-type type1 set tag 1
match as-path
match community-list
match interface
match ip address
match ip next-hop
match ip route-source
match metric
match route-type
match tag
set as-path
set automatic-tag
set community
set level
set local-preference
set metric
set metric-type
set next-hop
set origin
set tag
set tag
show route-map
ip policy route-map
match ip address
match length
set default interface
set interface
set ip default next-hop
set ip next-hop
Use the router bgp global configuration command to configure the Border Gateway Protocol (BGP) routing process. Use the no form of this command to remove the routing process.
router bgp autonomous-system| autonomous-system | Identifies the access server to other BGP access servers and tags the routing information passed along. |
No BGP routing process is enabled by default.
Global configuration
This command allows you to set up a distributed routing core that automatically guarantees the loop-free exchange of routing information between autonomous systems.
The following example configures a BGP process for autonomous system 120:
router bgp 120
neighbor
network (BGP)
timers bgp
Use the router egp global configuration command to configure the Exterior Gateway Protocol (EGP) routing process. Use the no form of this command to turn off the EGP routing process.
router egp remote-as| remote-as | Identifies the autonomous system number the access server expects its peers to be advertising in their EGP messages. |
No EGP routing process is defined.
Global configuration
You must specify the autonomous system number before starting EGP. The local autonomous system number will be included in EGP messages sent by the access server. The software does not insist that the actual remote autonomous system number match the configured autonomous system numbers. The output from the debug ip-egp EXEC command will advise of any discrepancies.
The following example assigns an access server to autonomous system 109 and is peering with access servers in autonomous system 164:
autonomous-system 109 router egp 164
autonomous-system (EGP)
neighbor (EGP, IGRP, RIP)
network (EGP)
timers egp
Use the router egp 0 global configuration command to specify that an access server should be considered a core gateway. Use the no form of this command to disable this function.
router egp 0This command has no arguments or keywords.
Disabled
Global configuration
Core gateways are central clearinghouses of routing information. Only one core gateway process can be configured in an access server.
The router egp 0 global configuration command allows a specific access server to have an EGP process that will enable it to act as a peer with any reachable autonomous system and information is exchanged freely between autonomous systems.
Normally, an EGP process expects to communicate with neighbors from a single autonomous system. Because all neighbors are in the same autonomous system, the EGP process assumes that these neighbors all have consistent internal information. Therefore, if the EGP process is informed about a route from one of its neighbors, it will not send it out to other neighbors.
With core EGP, the assumption is that all neighbors are from different autonomous systems, and all have inconsistent information. In this case, the EGP process distributes routes from one neighbor to all others (but not back to the originator). This allows the EGP process to be a central clearinghouse for information.
To control how an EGP process determines which neighbors will be treated as peers, use the neighbor any router configuration command with the router egp 0 global configuration command.
The following example illustrates how an EGP core gateway can be configured:
access-list 1 permit 10.0.0.0 0.255.255.255 ! global access list assignment router egp 0 neighbor any 1 network 172.16.0.0
neighbor any
neighbor any third-party
To configure the IP Enhanced IGRP routing process, use the router eigrp global configuration command. To shut down the routing process on the specified autonomous system, use the no form of this command.
router eigrp process-number| process-number | Number of a process that identifies the routes to other IP Enhanced IGRP access servers. It is also used to tag the routing information. If you have an autonomous system number, you can use it for the process number. |
Disabled
Global configuration
The following example shows how to configure an IP Enhanced IGRP routing process and assign autonomous system number 109:
router eigrp 109
Use the router igrp global configuration command to configure the Interior Gateway Routing Protocol (IGRP) routing process. Use the no form of this command to shut down the routing process on the specified autonomous system.
router igrp process-number| process-number | Number of a process that identifies the routes to other IP Enhanced IGRP access servers. It is also used to tag the routing information. If you have an autonomous system number, you can use it for the process number. |
No IGRP routing process is defined.
Global configuration
You are not required to have a registered autonomous system number to use IGRP. If you do not have a registered number, you can create your own. However, if you do have a registered number, we recommends that you use it to identify the IGRP process.
The following example shows how to configure an IGRP routing process and assign autonomous system 109:
router igrp 109
Use the router ospf global configuration command to configure an OSPF routing process on an access server. Use the no form of this command to terminate an individual OSPF routing process.
router ospf process-id| process-id | Internally used identification parameter for an OSPF routing process. It is locally assigned and can be any positive integer. A unique value is assigned for each OSPF routing process. |
No OSPF routing process is defined.
Global configuration
You can specify multiple OSPF routing processes in each access server.
The following example shows how to configure an OSPF routing process and assign a process ID of 109:
router ospf 109
network (OSPF)
Use the router rip global configuration command to configure the Routing Information Protocol (RIP) routing process. Use the no form of this command to turn off the RIP routing process.
router ripThis command has no arguments or keywords.
No RIP routing process is defined.
Global configuration
The following example shows how to begin the RIP routing process:
router rip
To modify an autonomous system path for BGP routes, use the set as-path route map configuration command. To not modify the autonomous system path, use the no form of this command.
set as-path {tag | prepend as-path-string}| tag | Converts the tag of a route into an autonomous system path. Applies only when redistributing routes into BGP. |
| prepend as-path-string | Appends the string following the keyword prepend to the as-path of the route that is matched by the route map. Applies to inbound and outbound BGP route maps. |
Autonomous system path is not modified.
Route map configuration
The only global BGP metric available to influence the best path selection is the AS-PATH length. By varying the length of the AS-PATH, a BGP speaker can influence the best path selection by a peer further away.
By allowing you to convert the tag into an autonomous system path, the set as-path tag variation of this command modifies the autonomous system length. The set as-path prepend variation allows you to prepend an arbitrary autonomous system path string to BGP routes. Usually the local autonomous system number is prepended multiple times. This increases the autonomous system path length.
The following example converts the tag of a redistributed route into an autonomous system path:
route-map set-as-path-from-tag match as-path 2 set as-path prepend 100 100 100 ! router bgp 100 redistribute ospf 109 route-map se t-as-path-from-tag
The following example prepends 100 100 100 to all the routes advertised to 131.108.1.1:
route-map set-as-path match as-path 1 set as-path prepend 100 100 100 ! router bgp 100 neighbor 131.108.1.1 route-map set-as-path out
match as-path
match community-list
match interface
match ip address
match ip next-hop
match ip route-source
match metric
match route-type
match tag
route-map
set automatic-tag
set community
set level
set local-preference
set metric
set metric-type
set next-hop
set origin
set tag
set weight
Use the set automatic-tag route-map configuration command to automatically compute the tag value. Use the no form of this command to disable this function.
set automatic-tagThis command has no arguments or keywords.
Disabled
Route-map configuration
You must have a match clause (even if it points to a "permit everything" list) if you want to set tags.
Use the route-map global configuration command, and the route-map configuration commands match and set, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which redistribution is allowed for the current route-map. The set commands specify the set actions--the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set route-map configuration commands specify the redistribution set actions to be performed when all of a route map's match criteria are met. When all match criteria are met, all set actions are performed.
In the following example, the access server is configured to automatically compute the tag value for the BGP learned routes:
route-map tag match as path 10 set automatic-tag ! router bgp 100 table-map tag
To set the BGP COMMUNITIES attribute, use the set community route-map configuration command. To delete the entry, use the no form of this command.
set community community-number [additive]| community-number | Valid values are 1 through 4294967200, internet, no-export, or no-advertise. The value internet is predefined to indicate the Internet community and all routes are members of it. |
| additive | (Optional) Add the community to the already existing communities. |
No BGP COMMUNITIES attributes exist.
Route-map configuration
You must have a match clause (even if it points to a "permit everything" list) if you want to set tags.
Use the route-map global configuration command and the route-map configuration commands match and set, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which redistribution is allowed for the current route-map. The set commands specify the set actions--the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set route-map configuration commands specify the redistribution set actions to be performed when all of a route map's match criteria are met. When all match criteria are met, all set actions are performed.
In the following example, routes that pass the autonomous system path access list 1 have the community set to 109. Routes that pass the autonomous system path access list 2 have the community set to no-export (these routes will not be advertised to any EBGP peers).
route-map set_community 10 permit match as-path 1 set community 109 route-map set_community 20 permit match as-path 2 set community no-export
ip community-list
match community-list
route-map
To indicate where to output packets that pass a match clause of a route map for policy routing, 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. |
Disabled
Use this command to provide certain users a different default route. If the router has no explicit route for the destination, then it routes the packet to this interface.
Use the ip policy route-map interface configuration command, the route-map global configuration command, and the match and set route-map configuration commands, to define the conditions for policy routing packets. The ip policy route-map command identifies a route map by name. Each route-map has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which policy routing occurs. The set commands specify the set actions--the particular routing actions to perform if the criteria enforced by the match commands are met.
If there is no explicit route for this destination, then route to this interface. The first interface specified with the set default interface command that is up is used. The optionally specified interfaces are tried in turn.
The set clauses can be used with one another. They are evaluated in the following order:
set ip next-hop
set interface
set ip default next-hop
set default interface
In the following example, packets with a Level 3 length of 3 to 50 bytes are output to Ethernet interface 0:
interface serial 0 ip policy route-map brighton route-map brighton match length 3 50 set default interface ethernet 0
match ip address
route-map
set interface
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. |
Disabled
Route-map configuration
Use the ip policy route-map interface configuration command, the route-map global configuration command, and the match and set route-map configuration commands, to define the conditions for policy routing packets. The ip policy route-map command identifies a route map by name. Each route-map has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which policy routing occurs. The set commands specify the set actions--the particular routing actions to perform if the criteria enforced by the match commands are met.
If the first interface specified with the set interface command is down, the optionally specified interfaces are tried in turn.
The set clauses can be used in conjunction with one another. They are evaluated in the following order:
set ip next-hop
set interface
set ip default next-hop
set default interface
A useful next hop implies an interface. As soon as a next hop and an interface are found, the packet is routed.
Specifying set interface null 0 is a way to write a policy that the packet be dropped and an "unreachable" message be generated.
In the following example, packets with a Level 3 length of 3 through 50 bytes are output to Ethernet interface 0:
interface serial 0 ip policy route-map testing ! route-map testing match length 3 50 set interface ethernet 0
ip policy route-map
match ip address
match length
route-map
set default interface
set ip default next-hop
set ip next-hop
To indicate where to output packets that pass a match clause of a route map for policy routing, 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 sent. It need not be an adjacent router. |
Disabled
Router configuration
Use this command to provide certain users a different default route. If the router has no explicit route for the destination, then it routes the packet to this next hop.
Use the ip policy route-map interface configuration command, the route-map global configuration command, and the match and set route-map configuration commands, to define the conditions for policy routing packets. The ip policy route-map command identifies a route map by name. Each route-map has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which policy routing occurs. The set commands specify the set actions--the routing actions to perform if the criteria set by the match commands are met.
If there is no explicit route for this destination, then route to this next hop. The first next hop specified with the set ip default next-hop command that appears to be adjacent to the router is used. The optional specified IP addresses are tried in turn.
The set clauses can be used with one another. They are evaluated in the following order:
set ip next-hop
set interface
set ip default next-hop
set default interface
In the following example, packets with a Level 3 length of 3 to 50 bytes are output to the router at IP address 161.14.2.2:
interface serial 0 ip policy route-map hartford ! route-map hartford match length 3 50 set ip default next-hop 161.14.2.2
ip policy route-map
match ip address
match length
route-map
set default interface
set interface
set ip next-hop
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. |
Disabled
Router configuration
Use the ip policy route-map interface configuration command, the route-map global configuration command, and the match and set route-map configuration commands, to define the conditions for policy routing packets. The ip policy route-map command identifies a route map by name. Each route-map has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which policy routing occurs. The set commands specify the set actions--the particular routing actions to perform if the criteria enforced by the match commands are met.
If the first next hop specified with the set ip next-hop command is down, the optionally specified IP addresses are tried in turn.
The set clauses can be used in conjunction with one another. They are evaluated in the following order:
set ip next-hop
set interface
set ip default next-hop
set default interface
In the following example, packets with a Level 3 length of 3 to 50 bytes are output to the router at IP address 161.14.2.2:
interface serial 0 ip policy route-map thataway route-map thataway match length 3 50 set ip next-hop 161.14.2.2
ip policy route-map
match ip address
match length
route-map
set default interface
set interface
set ip default next-hop
Use the set level route-map configuration command to indicate where to import routes. Use the no form of this command to delete the entry.
set level {level-1 | level-2 | level-1-2 | stub-area | backbone}| level-1 | Import into a Level-1 area |
| level-2 | Import into Level-2 sub-domain |
| level-1-2 | Import into Level-1 and Level-2 |
| stub-area | Import into OSPF NSSA area |
| backbone | Import into OSPF backbone area |
Disabled
For IS-IS destinations, the default value is level-2. For OSPF destinations, the default value is backbone.
Route-map configuration
Use the route-map global configuration command, and the route-map configuration commands match and set, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which redistribution is allowed for the current route-map. The set commands specify the set actions--the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set route-map configuration commands specify the redistribution set actions to be performed when all of a route map's match criteria are met. When all match criteria are met, all set actions are performed.
In the following example, routes will be imported into the Level 1 area:
route-map name set level level-l
Use the set local-preference route-map configuration command to specify a preference value for autonomous system path. Use the no form of this command to delete the entry.
set local-preference value| value | Preference value. An integer from 0 through 4294967295. |
Preference value of 100.
Route-map configuration
The preference is sent only to all access servers in the local autonomous system.
You must have a match clause (even if it points to a "permit everything" list) if you want to set tags.
Use the route-map global configuration command, and the route-map configuration commands match and set, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which redistribution is allowed for the current route-map. The set commands specify the set actions--the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set route-map configuration commands specify the redistribution set actions to be performed when all of a route map's match criteria are met. When all match criteria are met, all set actions are performed.
You can change the default preference value with the bgp default local-preference command.
In the following example, the local preference of is set to 100 for all routes that are included in access list 1:
route-map map-preference match as-path 1 set local-preference 100
match
route-map
Use the set metric route-map configuration command to set the metric value for the destination routing protocol. Use the no form of this command to return to the default metric value.
set metric metric-value| metric-value | Metric value or IGRP bandwidth in kilobits per second. An integer from 0 through 294967295. |
Default metric value.
Route-map configuration
Use the route-map global configuration command, and the route-map configuration commands match and set, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which redistribution is allowed for the current route-map. The set commands specify the set actions--the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set route-map configuration commands specify the redistribution set actions to be performed when all of a route map's match criteria are met. When all match criteria are met, all set actions are performed.
In the following example, the metric value for the destination routing protocol is set to 100:
route-map set-metric set metric 100
Use the set metric-type route-map command to set the metric type for the destination routing protocol. Use the no form of this command to disable the metric type for the destination routing protocol.
set metric-type {type-1 | type-2}| type-1 | OSPF external type 1 metric. |
| type-2 | OSPF external type 2 metric. |
Disabled
Route-map configuration
Use the route-map global configuration command, and the route-map configuration commands match and set, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which redistribution is allowed for the current route-map. The set commands specify the set actions--the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set route-map configuration commands specify the redistribution set actions to be performed when all of a route map's match criteria are met. When all match criteria are met, all set actions are performed.
In the following example, the metric type of the destination protocol is set to OSPF external type 1:
route-map map-type set metric-type type-1
Use the set next-hop route-map configuration command to specify the address of the next hop. Use the no form of this command to delete the entry.
set next-hop next-hop| next-hop | IP address of the next hop router (access server). |
Default next-hop address.
Route-map configuration
You must have a match clause (even if it points to a "permit everything" list) if you want to set tags.
Use the route-map global configuration command, and the route-map configuration commands match and set, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which redistribution is allowed for the current route-map. The set commands specify the set actions--the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set route-map configuration commands specify the redistribution set actions to be performed when all of a route map's match criteria are met. When all match criteria are met, all set actions are performed.
In the following example, routes that pass the access list have the next hop set to 192.168.70.24:
route-map map_hop match address 5 set next-hop 192.168.70.24
Use the set origin route-map configuration command to set the BGP origin code. Use the no form of this command to delete the entry.
set origin {igp | egp remote-as | incomplete}| igp | Remote EGP. |
| egp | Local IGP. |
| remote-as | Remote autonomous system. An integer from 0 through 65535. |
| incomplete | Unknown heritage. |
Default origin, based on route in main IP routing table.
Route-map configuration
You must have a match clause (even if it points to a "permit everything" list) if you want to set tags.
Use the route-map global configuration command, and the route-map configuration commands match and set, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which redistribution is allowed for the current route-map. The set commands specify the set actions--the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set route-map configuration commands specify the redistribution set actions to be performed when all of a route map's match criteria are met. When all match criteria are met, all set actions are performed.
In the following example, routes that pass the route map have the origin set to IGP:
route-map set_origin match as-path 10 set origin igp
Use the set tag route-map configuration command to set a tag value of the destination routing protocol. Use the no form of this command to delete the entry.
set tag tag-value| tag-value | Name for the tag. Integer from 0 through 4294967295. |
If not specified, the default action is to forward the tag in the source routing protocol onto the new destination protocol.
Route-map configuration
Use the route-map global configuration command, and the route-map configuration commands match and set, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria--the conditions under which redistribution is allowed for the current route-map. The set commands specify the set actions--the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set route-map configuration commands specify the redistribution set actions to be performed when all of a route map's match criteria are met. When all match criteria are met, all set actions are performed.
In the following example, the tag value of the destination routing protocol is set to 5:
route-map tag set tag 5
Use the set weight route-map configuration command to specify the BGP weight for the routing table. Use the no form of this command to delete the entry.
set weight weight| weight | Weight value. From 0 through 65535. |
The weight will not be changed by the specified route map.
Route-map configuration
You must have a match clause (even if it points to a "permit everything" list) if you want to set tags.
The implemented weight is based on the first matched autonomous system path. Weights indicated when an autonomous system path is matched override the weights assigned by global neighbor commands. In other words, the weights assigned with the match as-path and set weight route-map commands override the weights assigned using the neighbor weight and neighbor filter-list commands.
In the following example, the BGP weight for the routes matching the autonomous system path access list is set to 200:
route-map set-weight match as-path 10 set weight 200
Use the show ip bgp EXEC command to display a particular network in the BGP routing table.
show ip bgp [network] [network-mask] [subnets]| network | (Optional) Network number, entered to display a particular network in the BGP routing table. |
| network-mask | (Optional) Displays all BGP routes matching the address/mask pair. |
| subnets | (Optional) Displays route and more specific routes. |
EXEC
The following is sample output from the show ip bgp command:
Router# show ip bgp
BGP table version is 716977, local access server ID is 192.168.32.1
Status codes: s suppressed, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
* i3.0.0.0 192.168.22.1 0 100 0 1800 1239 ?
*>i 192.168.16.1 0 100 0 1800 1239 ?
* i6.0.0.0 192.168.22.1 0 100 0 1800 690 568 ?
*>i 192.168.16.1 0 100 0 1800 690 568 ?
* i7.0.0.0 192.168.22.1 0 100 0 1800 701 35 ?
*>i 192.168.16.1 0 100 0 1800 701 35 ?
* 192.168.72.24 0 1878 704 701 35 ?
* i8.0.0.0 192.168.22.1 0 100 0 1800 690 560 ?
*>i 192.168.16.1 0 100 0 1800 690 560 ?
* 192.168.72.24 0 1878 704 701 560 ?
* i10.13.0.0 192.168.22.1 0 100 0 1800 690 200 ?
*>i 192.168.16.1 0 100 0 1800 690 200 ?
* 192.168.72.24 0 1878 704 701 200 ?
* i10.15.0.0 192.168.22.1 0 100 0 1800 174 ?
*>i 192.168.16.1 0 100 0 1800 174 ?
* i10.16.0.0 192.168.22.1 0 100 0 1800 701 i
*>i 192.168.16.1 0 100 0 1800 701 i
* 192.168.72.24 0 1878 704 701 i
Table 19-7 describes significant fields shown in the display.
| Field | Description |
|---|---|
| BGP table version is 716977 | Internal version number for the table. This is incremented any time the table changes. |
| local access server ID | An Internet address of the access server. |
| Status codes | Asterisk (*) indicates that the table entry is valid. A > character indicates that the table entry is the best entry to use for that network. A lowercase "i" indicates that the table entry was learned via an internal BGP session. A lowercase "s" indicates that the table entry is suppressed. |
| Network | Internet address of the network the entry describes. |
| Next Hop | IP address of the next system to use when forwarding a packet to the destination network. An entry of 0.0.0.0 indicates that the access server has some non-BGP route to this network. |
| Metric | If shown, this is the value of the interautonomous system metric. This is frequently not used. |
| Weight | Set through the use of autonomous system filters. |
| Path | Autonomous system paths to the destination network. There can be one entry in this field for each autonomous system in the path. At the end of the path is the origin code for the path. A lowercase "i" indicates that the entry was originated with the IGP and advertised with a network router configuration command. A lowercase "e" indicates that the route originated with EGP. A question mark (?) indicates that the origin of the path is not clear. Usually this is a path that is redistributed into BGP from an IGP. |
| LocPrf | Local preference value. Default is 100. |
The following is sample output from the show ip bgp subnets command:
Router# show ip bgp 192.168.0.0 255.255.0.0 subnets
BGP table version is 1738, local access server ID is 192.168.72.24
Status codes: s suppressed, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 192.168.0.0 192.168.72.30 8896 32768 ?
* 192.168.72.30 0 109 108 ?
*> 192.168.1.0 192.168.72.30 8796 32768 ?
* 192.168.72.30 0 109 108 ?
*> 192.168.11.0 192.168.72.30 42482 32768 ?
* 192.168.72.30 0 109 108 ?
*> 192.168.14.0 192.168.72.30 8796 32768 ?
* 192.168.72.30 0 109 108 ?
*> 192.168.15.0 192.168.72.30 8696 32768 ?
* 192.168.72.30 0 109 108 ?
*> 192.168.16.0 192.168.72.30 1400 32768 ?
* 192.168.72.30 0 109 108 ?
*> 192.168.17.0 192.168.72.30 1400 32768 ?
* 192.168.72.30 0 109 108 ?
*> 192.168.18.0 192.168.72.30 8876 32768 ?
* 192.168.72.30 0 109 108 ?
*> 192.168.19.0 192.168.72.30 8876 32768 ?
* 192.168.72.30 0 109 108 ?
Use the show ip bgp cidr-only privileged EXEC command to display only routes with non-natural network masks.
show ip bgp cidr-onlyThis command has no arguments or keywords.
Privileged EXEC
The following is sample output for the show ip bgp cidr-only command:
Router# show ip bgp cidr-only
BGP table version is 220, local access server ID is 192.168.73.131
Status codes: s suppressed, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 192.0.0.0/8 192.168.72.24 0 1878 ?
*> 192.168.0.0/16 192.168.72.30 0 108 ?
Table 19-8 describes significant fields shown in the display.
| Field | Description |
|---|---|
| BGP table version is 220 | Internal version number for the table. This is incremented any time the table changes. |
| local access server ID | An Internet address of the access server. |
| Status codes | s--The table entry is suppressed.
*--The table entry is valid. >--The table entry is the best entry to use for that network. i--The table entry was learned via an internal BGP session. |
| Network | Internet address of the network the entry describes. |
| Next Hop | IP address of the next system to use when forwarding a packet to the destination network. An entry of 0.0.0.0 indicates that the access server has some non-BGP route to this network. |
| LocPrf | Local preference value. Default is 100. |
| Metric | If shown, this is the value of the interautonomous system metric. This is frequently not used. |
| Weight | Set through the use of autonomous system filters. |
| Path | Autonomous system paths to the destination network. There can be one entry in this field for each autonomous system in the path. At the end of the path is the origin code for the path.
i--The entry was originated with the IGP and advertised with a e--The route originated with EGP. ?--The origin of the path is not clear. Usually this is a path that is |
To display routes that belong to specified BGP communities, use the show ip bgp community EXEC command.
show ip bgp community community-number [exact]| community-number | Valid value is community number in the range from 1 through 4294967200, no-export, or no-advertise. |
| exact | (Optional) Displays only routes that have exactly the same specified communities. |
EXEC
The following is sample output from the show ip bgp community command:
Router# show ip bgp community 10
BGP table version is 716977, local access server ID is 192.168.32.1
Status codes: s suppressed, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
* i3.0.0.0 192.168.22.1 0 100 0 1800 1239 ?
*>i 192.168.16.1 0 100 0 1800 1239 ?
* i6.0.0.0 192.168.22.1 0 100 0 1800 690 568 ?
*>i 192.168.16.1 0 100 0 1800 690 568 ?
* i7.0.0.0 192.168.22.1 0 100 0 1800 701 35 ?
*>i 192.168.16.1 0 100 0 1800 701 35 ?
* 192.168.72.24 0 1878 704 701 35 ?
* i8.0.0.0 192.168.22.1 0 100 0 1800 690 560 ?
*>i 192.168.16.1 0 100 0 1800 690 560 ?
* 192.168.72.24 0 1878 704 701 560 ?
* i10.13.0.0 192.168.22.1 0 100 0 1800 690 200 ?
*>i 192.168.16.1 0 100 0 1800 690 200 ?
* 192.168.72.24 0 1878 704 701 200 ?
* i10.15.0.0 192.168.22.1 0 100 0 1800 174 ?
*>i 192.168.16.1 0 100 0 1800 174 ?
* i10.16.0.0 192.168.22.1 0 100 0 1800 701 i
*>i 192.168.16.1 0 100 0 1800 701 i
* 192.168.72.24 0 1878 704 701 i
Table 19-9 describes significant fields shown in the display.
| Field | Description |
|---|---|
| BGP table version | Internal version number of the table. This number is incremented whenever the table changes. |
| local access server ID | IP address of the access server. |
| Status codes | Status of the table entry. The status is displayed at the beginning of each line in the table. It can be one of the following values: |
| s suppressed | Entry is suppressed. |
| * valid | Entry is valid. |
| > best | Entry is the best to use for that network. |
| i -internal | Entry learned via an internal BGP session. |
| Origin codes | Indicates the origin of the entry. The origin code is placed at the end of each line in the table. It can be one of the following values: |
| i - IGP | Entry originated from IGP and was advertised with a network router configuration command. |
| e - EGP | Entry originated from EGP. |
| ? - incomplete | Origin of the path is not clear. Usually, this is an access server that is redistributed into BGP from an IGP. |
| Network | IP address of a network entity. |
| Next Hop | IP address of the next system that is used when forwarding a packet to the destination network. An entry of 0.0.0.0 indicates that the access server has some non-BGP routes to this network. |
| Metric | If shown, this is the value of the interautonomous system metric. This is frequently not used. |
| LocPrf | Local preference value as set with the set local-preference route-map configuration command. The default value is 100. |
| Weight | Weight of the route as set via autonomous system filters. |
| Path | Autonomous system paths to the destination network. There can be one entry in this field for each autonomous system in the path. |
To display routes that are permitted by the BGP community list, use the show ip bgp community-list EXEC command.
show ip bgp community-list community-list-number [exact]| community-list-number | Community list number in the range from 1 through 99. |
| exact | (Optional) Displays only routes that have an exact match. |
EXEC
The following is sample output of the show ip bgp community-list command:
Router# show ip bgp community-list 20
BGP table version is 716977, local access server ID is 192.168.32.1
Status codes: s suppressed, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
* i3.0.0.0 192.168.22.1 0 100 0 1800 1239 ?
*>i 192.168.16.1 0 100 0 1800 1239 ?
* i6.0.0.0 192.168.22.1 0 100 0 1800 690 568 ?
*>i 192.168.16.1 0 100 0 1800 690 568 ?
* i7.0.0.0 192.168.22.1 0 100 0 1800 701 35 ?
*>i 192.168.16.1 0 100 0 1800 701 35 ?
* 192.168.72.24 0 1878 704 701 35 ?
* i8.0.0.0 192.168.22.1 0 100 0 1800 690 560 ?
*>i 192.168.16.1 0 100 0 1800 690 560 ?
* 192.168.72.24 0 1878 704 701 560 ?
* i10.13.0.0 192.168.22.1 0 100 0 1800 690 200 ?
*>i 192.168.16.1 0 100 0 1800 690 200 ?
* 192.168.72.24 0 1878 704 701 200 ?
* i10.15.0.0 192.168.22.1 0 100 0 1800 174 ?
*>i 192.168.16.1 0 100 0 1800 174 ?
* i10.16.0.0 192.168.22.1 0 100 0 1800 701 i
*>i 192.168.16.1 0 100 0 1800 701 i
* 192.168.72.24 0 1878 704 701 i
Table 19-10 describes significant fields shown in the display.
| Field | Description |
|---|---|
| BGP table version | Internal version number of the table. This number is incremented whenever the table changes. |
| local access server ID | IP address of the access server. |
| Status codes | Status of the table entry. The status is displayed at the beginning of each line in the table. It can be one of the following values: |
| s suppressed | Entry is suppressed. |
| * valid | Entry is valid. |
| > best | Entry is the best to use for that network. |
| i -internal | Entry learned via an internal BGP session. |
| Origin codes | Indicates the origin of the entry. The origin code is placed at the end of each line in the table. It can be one of the following values: |
| i - IGP | Entry originated from IGP and was advertised with a network router configuration command. |
| e - EGP | Entry originated from EGP. |
| ? - incomplete | Origin of the path is not clear. Usually, this is a router that is redistributed into BGP from an IGP. |
| Network | IP address of a network entity. |
| Next Hop | IP address of the next system that is used when forwarding a packet to the destination network. An entry of 0.0.0.0 indicates that the access server has some non-BGP routes to this network. |
| Metric | If shown, this is the value of the interautonomous system metric. This is frequently not used. |
| LocPrf | Local preference value as set with the set local-preference route-map configuration command. The default value is 100. |
| Weight | Weight of the route as set via autonomous system filters. |
| Path | Autonomous system paths to the destination network. There can be one entry in this field for each autonomous system in the path. |
Use the show ip bgp filter-list privileged EXEC command to display routes that conform to a specified filter list.
show ip bgp filter-list access-list-number| access-list-number | Regular expression access list number from 1 through 199 |
Privileged EXEC
The following is sample output from the show ip bgp filter-list command:
Router# show ip bgp filter-list 2
BGP table version is 1738, local access server ID is 192.168.72.24
Status codes: s suppressed, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
* 192.168.0.0 192.168.72.30 0 109 108 ?
* 192.168.1.0 192.168.72.30 0 109 108 ?
* 192.168.11.0 192.168.72.30 0 109 108 ?
* 192.168.14.0 192.168.72.30 0 109 108 ?
* 192.168.15.0 192.168.72.30 0 109 108 ?
* 192.168.16.0 192.168.72.30 0 109 108 ?
* 192.168.17.0 192.168.72.30 0 109 108 ?
* 192.168.18.0 192.168.72.30 0 109 108 ?
* 192.168.19.0 192.168.72.30 0 109 108 ?
* 192.168.24.0 192.168.72.30 0 109 108 ?
* 192.168.29.0 192.168.72.30 0 109 108 ?
* 192.168.30.0 192.168.72.30 0 109 108 ?
* 192.168.33.0 192.168.72.30 0 109 108 ?
* 192.168.35.0 192.168.72.30 0 109 108 ?
* 192.168.36.0 192.168.72.30 0 109 108 ?
* 192.168.37.0 192.168.72.30 0 109 108 ?
* 192.168.38.0 192.168.72.30 0 109 108 ?
* 192.168.39.0 192.168.72.30 0 109 108 ?
Table 19-11 describes significant fields shown in the display.
| Field | Description |
|---|---|
| BGP table version is 1738 | Internal version number for the table. This is incremented any time the table changes. |
| local access server ID | An Internet address of the access server. |
| Status codes | s--The table entry is suppressed.
*--The table entry is valid. >--The table entry is the best entry to use for that network. i--The table entry was learned via an internal BGP session. |
| Network | Internet address of the network the entry describes. |
| Next Hop | IP address of the next system to use when forwarding a packet to the destination network. An entry of 0.0.0.0 indicates that the access server has some non-BGP route to this network. |
| LocPrf | Local preference value. Default is 100. |
| Metric | If shown, this is the value of the interautonomous system metric. This is frequently not used. |
| Weight | Set through the use of autonomous system filters. |
| Path | Autonomous system paths to the destination network. There can be one entry in this field for each autonomous system in the path. At the end of the path is the origin code for the path.
i--The entry was originated with the IGP and advertised with a e--The route originated with EGP. ?--The origin of the path is not clear. Usually this is a path that is |
To display routes with inconsistent originating autonomous systems, use the show ip bgp inconsistent-as privileged EXEC command.
show ip bgp inconsistent-asThis command has no arguments or keywords.
Privileged EXEC
The following is sample output from the show ip bgp inconsistent-as command:
Router# show ip bgp inconsistent-as
BGP table version is 87, local router ID is 172.19.82.53
Status codes: s suppressed, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
* 11.0.0.0 171.69.232.55 0 0 300 88 90 99 ?
*> 171.69.232.52 2222 0 400 ?
* 171.69.0.0 171.69.232.55 0 0 300 90 99 88 200 ?
*> 171.69.232.52 2222 0 400 ?
* 200.200.199.0 171.69.232.55 0 0 300 88 90 99 ?
*> 171.69.232.52 2222 0 400 ?
Use the show ip bgp neighbors EXEC command to display detailed information on the TCP and BGP connections to individual neighbors.
show ip bgp neighbors [address] [routes | paths]| address | (Optional) Address of the neighbor whose routes you have learned from. |
| routes | (Optional) Routes of specified neighbors. |
| paths | (Optional) Autonomous system path of specified neighbor. |
EXEC
The following is sample output from the show ip bgp neighbors command:
Router# show ip bgp neighbors
BGP neighbor is 172.16.6.68, remote AS 10, external link
BGP version 3, remote access server ID 172.16.6.68
BGP state = Established, table version = 22, up for 0:00:13
Last read 0:00:12, hold time is 180, keepalive interval is 60 seconds
Received 24 messages, 0 notifications
Sent 28 messages, 4 notifications
Connections established 1; dropped 0
Connection state is ESTAB, I/O status: 1, unread input bytes: 0
Local host: 172.16.6.69, 12288 Foreign host: 172.16.6.68, 179
Enqueued packets for retransmit: 0, input: 0, saved: 0
Event Timers (current time is 835828):
Timer: Retrans TimeWait AckHold SendWnd KeepAlive
Starts: 20 0 18 0 0
Wakeups: 1 0 2 0 0
Next: 0 0 0 0 0
iss: 60876 snduna: 62649 sndnxt: 62649 sndwnd: 1872
irs: 95187024 rcvnxt: 95188733 rcvwnd: 1969 delrcvwnd: 271
SRTT: 364 ms, RTTO: 1691 ms, RTV: 481 ms, KRTT: 0 ms
minRTT: 4 ms, maxRTT: 340 ms, ACK hold: 300 ms
Flags: higher precedence
Datagrams (max data segment is 1450 bytes):
Rcvd: 36 (out of order: 0), with data: 18, total data bytes: 1708
Sent: 40 (retransmit: 1), with data: 36, total data bytes: 1817
Table 19-12 describes significant fields shown in the display.
| Field | Description |
|---|---|
| BGP neighbor | Lists the IP address of the BGP neighbor and its autonomous system number. If the neighbor is in the same autonomous system as the access server, then the link between them is internal. Otherwise, it is considered external. |
| BGP version | Specifies that the BGP version being used to communicate with the remote access server is BGP version 3; the neighbor's access server ID (an IP address) is also specified. |
| BGP state | Indicates the internal state of this BGP connection. |
| table version | Indicates that the neighbor has been updated with this version of the primary BGP routing table. |
| up time | Indicates the amount of time that the underlying TCP connection has been in existence. |
| Last read | Time that BGP last read a message from this neighbor. |
| hold time | Maximum amount of time that can elapse between messages from the peer. |
| keepalive interval | Time period between sending keepalive packets, which help ensure that the TCP connection is up. |
| Received | Number of received messages indicates the number of total BGP messages received from this peer, including keepalives. The number of notifications is the number of error messages received from the peer. |
| Sent | The number of sent messages indicates the total number of BGP messages that have been sent to this peer, including keepalives. The number of notifications is the number of error messages that we have sent to this peer. |
| Connections established | The number of connections established is a count of the number of times that we have established a TCP connection and the two peers have agreed speak BGP with each other. The number of dropped connections is the number of times that a good connection has failed or been taken down. |
The remainder of the display describes the status of the underlying TCP connection.
The following is sample output from the show ip bgp neighbors paths command:
Router# show ip bgp neighbors 192.168.72.24 paths
Address Refcount Metric Path
0x3BAE7C 41 0 1878 ?
0x3BA714 3 0 1878 1755 i
0x3BA58C 1 0 1878 i
Table 19-13 describes significant fields shown in the display.
| Field | Description |
|---|---|
| Address | Internal address where the path is stored. |
| Refcount | Number of routes using that path. |
| Metric | The MULTI_EXIT_DISC metric for the path. (The name of this metric for BGP versions 2 and 3 is INTER_AS.) |
| Path | The AS_PATH for that route, followed by the origin code for that route:
|
Use the show ip bgp paths EXEC command to display all the BGP paths in the database.
show ip bgp pathsThis command has no arguments or keywords.
EXEC
The following is sample output from the show ip bgp paths command:
Router# show ip bgp paths
Address Hash Refcount Metric Path
0x297A9C 0 2 0 i
0x30BF84 1 0 0 702 701 ?
0x2F7BC8 2 235 0 ?
0x2FA1D8 3 0 0 702 701 i
Table 19-14 describes significant fields shown in the display.
| Field | Description |
|---|---|
| Address | Internal address where the path is stored. |
| Hash | Hash bucket where path is stored. |
| Refcount | Number of routes using that path. |
| Metric | The MULTI_EXIT_DISC metric for the path. (The name of this metric for BGP versions 2 and 3 is INTER_AS.) |
| Path | The AS_PATH for that route, followed by the origin code for that route. |
To display information about BGP peer groups, use the show ip bgp peer-group EXEC command.
show ip bgp peer-group [tag] [summary]| tag | (Optional) Displays information about that specific peer group. |
| summary | (Optional) Displays a summary of the status of all the members of a peer group. |
EXEC
The following is sample output from the show ip bgp peer-group command:
Router# show ip bgp peer-group0 internal
BGP neighbor is internal, peer-group leader
BGP version 4
Minimum time between advertisement runs is 5 seconds
Incoming update AS path filter list is 2
Outgoing update AS path filter list is 1
Route map for outgoing advertisements is set-med
Use the show ip bgp regexp privileged EXEC command to display routes matching the regular expression.
show ip bgp regexp regular-expression| regular-expression | Regular expression to match the BGP autonomous system paths |
Privileged EXEC
Router# show ip bgp regexp 108$
BGP table version is 1738, local access server ID is 192.168.72.24
Status codes: s suppressed, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
* 192.168.0.0 192.168.72.30 0 109 108 ?
* 192.168.1.0 192.168.72.30 0 109 108 ?
* 192.168.11.0 192.168.72.30 0 109 108 ?
* 192.168.14.0 192.168.72.30 0 109 108 ?
* 192.168.15.0 192.168.72.30 0 109 108 ?
* 192.168.16.0 192.168.72.30 0 109 108 ?
* 192.168.17.0 192.168.72.30 0 109 108 ?
* 192.168.18.0 192.168.72.30 0 109 108 ?
* 192.168.19.0 192.168.72.30 0 109 108 ?
* 192.168.24.0 192.168.72.30 0 109 108 ?
* 192.168.29.0 192.168.72.30 0 109 108 ?
* 192.168.30.0 192.168.72.30 0 109 108 ?
* 192.168.33.0 192.168.72.30 0 109 108 ?
* 192.168.35.0 192.168.72.30 0 109 108 ?
* 192.168.36.0 192.168.72.30 0 109 108 ?
* 192.168.37.0 192.168.72.30 0 109 108 ?
* 192.168.38.0 192.168.72.30 0 109 108 ?
* 192.168.39.0 192.168.72.30 0 109 108 ?
Use the show ip bgp summary EXEC command to display the status of all BGP connections.
show ip bgp summaryThis command has no arguments or keywords.
EXEC
The following is sample output from the show ip bgp summary command:
Router# show ip bgp summary
BGP table version is 717029, main routing table version 717029
19073 network entries (37544 paths) using 3542756 bytes of memory
691 BGP path attribute entries using 57200 bytes of memory
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State
192.168.16.1 4 1755 32642 2973 717029 0 0 1:27:11
192.168.17.1 4 1755 4790 2973 717029 0 0 1:27:51
192.168.18.1 4 1755 7722 3024 717029 0 0 1:28:13
192.168.19.1 4 1755 0 0 0 0 0 2d02 Active
192.168.20.1 4 1755 3673 3049 717029 0 0 2:50:10
192.168.21.1 4 1755 3741 3048 717029 0 0 12:24:43
192.168.22.1 4 1755 33129 3051 717029 0 0 12:24:48
192.168.23.1 4 1755 0 0 0 0 0 2d02 Active
192.168.24.1 4 1755 0 0 0 0 0 2d02 Active
192.168.25.1 4 1755 0 0 0 0 0 2d02 Active
192.168.26.1 4 1755 0 0 0 0 0 2d02 Active
192.168.27.1 4 1755 4269 3049 717029 0 0 12:39:33
192.168.28.1 4 1755 3037 3050 717029 0 0 2:08:15
192.168.72.24 4 1878 11635 13300 717028 0 0 0:50:39
Table 19-15 describes significant fields shown in the display.
| Field | Description |
|---|---|
| BGP table version | Internal version number of BGP database. |
| main routing table version | Indicates last version of BGP database injected into main routing table. |
| Neighbor | IP address of a neighbor. |
| V | Indicates BGP version number spoken to that neighbor. |
| MsgRcvd | BGP messages received from that neighbor. |
| MsgSent | BGP messages sent to that neighbor. |
| TblVer | Last version of the BGP database that was sent to that neighbor. |
| InQ | Number of messages from that neighbor waiting to be processed. |
| OutQ | Number of messages waiting to be sent to that neighbor. |
| Update/State | The length of time that the BGP session has been in state Established, or the current state if it is not Established. |
To display the contents of the DVMRP routing table, use the show ip dvmrp route EXEC command.
show ip dvmrp route [ip-address]| ip-address | (Optional) IP address of an entry in the DVMRP routing table. |
EXEC
The following is sample output of the show ip dvmrp route command:
DVMRP Routing Table - 3 entries 10.13.32.0/22 [0/11] via 192.168.195.10, Tunnel1, uptime 3:50:24, expires 0:02:24 10.13.52.0/22 [0/9] via 192.168.195.10, Tunnel1, uptime 0:59:14, expires 0:02:24 10.23.68.0/22 [0/8] via 192.168.195.10, Tunnel1, uptime 3:50:24, expires 0:02:24
Table 19-16 describes the fields shown in the display
| Field | Description |
|---|---|
| 3 entries | Number of entries in the DMVRP routing table. |
| 10.13.32.0/22 | Source network. |
| [0/11] | Administrative distance/reliability. |
| via 192.168.195.10 | Next-hop access server to the source network. |
| Tunnel1 | Interface to the source network. |
| uptime | How long in hours, minutes, and seconds that the route has been in the DVMRP routing table. |
| expires | How long in hours, minutes, and seconds until the entry is removed from the DVMRP routing table. |
Use the show ip egp EXEC command to display statistics on EGP connections and neighbors.
show ip egpThis command has no arguments or keywords.
EXEC
The following is sample output from the show ip egp command:
Router# show ip egp
Local autonomous system is 109
EGP Neighbor FAS/LAS State SndSeq RcvSeq Hello Poll j/k Flags
10.3.0.27 1/109 IDLE 625 61323 60 180 0 Perm, Act
* 10.2.0.37 1/109 UP 12:29 250 14992 60 180 3 Perm, Act
* 10.7.0.63 1/109 UP 1d19 876 10188 60 180 4 Perm, Pass
Table 19-17 describes the fields shown in the display.
| Field | Description |
|---|---|
| EGP Neighbor | Address of the EGP neighbor. |
| FAS | Foreign autonomous system number. |
| LAS | Local autonomous system number. |
| State | State of the connection between peers. |
| SndSeq | Send sequence number. |
| RcvSeq | Receive sequence number. |
| Hello | Interval between Hello/I-Heard-You packets. |
| Poll | Interval between Poll/Update packets. |
| j/k | Measure of reachability; 4 is perfect. |
| Flags | Perm--Permanent.
Temp--Temporary (neighbor will be removed). Act--Active, controlling the connection. Pass--Passive, neighbor controls the connection. |
To display the neighbors discovered by IP Enhanced IGRP, use the show ip eigrp neighbors EXEC command.
show ip eigrp neighbors [type number]| type | (Optional) Interface type |
| number | (Optional) Interface number |
EXEC
Use the show ip eigrp neighbors command to determine when neighbors become active and inactive. It is also useful for debugging certain types of transport problems.
The following is sample output from the show ip eigrp neighbors command:
Router# show ip eigrp neighbors
IP-EIGRP Neighbors for process 77
Address Interface Holdtime Uptime Q Seq SRTT RTO
(secs) (h:m:s) Count Num (ms) (ms)
192.168.81.28 Ethernet1 13 0:00:41 0 11 4 20
192.168.80.28 Ethernet0 14 0:02:01 0 10 12 24
192.168.80.31 Ethernet0 12 0:02:02 0 4 5 20
Table 19-18 explains the fields in the output.
| Field | Description |
|---|---|
| process 77 | Autonomous system number specified in the ipx router configuration command. |
| Address | IP address of the Enhanced IGRP peer. |
| Interface | Interface on which the access server is receiving hello packets from the peer. |
| Holdtime | Length of time, in seconds, that the access server will wait to hear from the peer before declaring it down. If the peer is using the default hold time, this number will be less than 15. If the peer configures a nondefault hold time, it will be reflected here. |
| Uptime | Elapsed time, in hours, minutes, and seconds, since the local access server first heard from this neighbor. |
| Q Count | Number of IP Enhanced IGRP packets (Update, Query, and Reply) that the access server is waiting to send. |
| Seq Num | Sequence number of the last update, query, or reply packet that was received from this neighbor. |
| SRTT | Smooth round-trip time. This is the number of milliseconds it takes for an IP Enhanced IGRP packet to be sent to this neighbor and for the local access server to receive an acknowledgment of that packet. |
| RTO | Retransmission timeout, in milliseconds. This is the amount of time the access server waits before retransmitting a packet from the retransmission queue to a neighbor. |
To display the IP Enhanced IGRP topology table, use the show ip eigrp topology EXEC command.
show ip eigrp topology [autonomous-system-number | [[ip-address] mask]]| autonomous-system-number | (Optional) A decimal number between 1 and 65535. |
| ip-address | (Optional) When specified with a mask, a detailed description of the entry is provided. |
| mask | (Optional) Subnet mask. |
EXEC
Use the show ip eigrp topology command to determine DUAL states and to debug possible DUAL problems.
The following is sample output from the show ip eigrp topology command:
Router# show ip eigrp topology
IP-EIGRP Topology Table for process 77
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - Reply status
P 192.168.90.0 255.255.255.0, 2 successors, FD is 0
via 192.168.80.28 (46251776/46226176), Ethernet0
via 192.168.81.28 (46251776/46226176), Ethernet1
via 192.168.80.31 (46277376/46251776), Ethernet0
P 192.168.81.0 255.255.255.0, 1 successors, FD is 307200
via Connected, Ethernet1
via 192.168.81.28 (307200/281600), Ethernet1
via 192.168.80.28 (307200/281600), Ethernet0
via 192.168.80.31 (332800/307200), Ethernet0
Table 19-19 explains the fields in the output.
| Field | Description |
|---|---|
| Codes | State of this topology table entry. Passive and Active refer to the Enhanced IGRP state with respect to this destination; Update, Query, and Reply refer to the type of packet that is being sent. |
| P - Passive | No Enhanced IGRP computations are being performed for this destination. |
| A - Active | Enhanced IGRP computations are being performed for this destination. |
| U - Update | Indicates that an update packet was sent to this destination. |
| Q - Query | Indicates that a query packet was sent to this destination. |
| R - Reply | Indicates that a reply packet was sent to this destination. |
| r - Reply status | Flag that is set when after the access server has sent a query and is waiting for a reply. |
| 192.168.90.0 and so on | Destination IP network number. |
| 255.255.255.0 | Destination subnet mask. |
| successors | Number of successors. This number corresponds to the number of next hops in the IP routing table. |
| FD | Feasible distance. This value is used in the feasibility condition check. If the neighbor's reported distance (the metric after the slash) is less than the feasible distance, the feasibility condition is met and that path is a feasible successor. Once the access server determines it has a feasible successor, it does not have to send a query for that destination. |
| replies | Number of replies that are still outstanding (have not been received) with respect to this destination. This information appears only when the destination is in Active state. |
| state | Exact Enhanced IGRP state that this destination is in. It can be the number 0, 1, 2, or 3. This information appears only when the destination is Active. |
| via | IP address of the peer who told the access server about this destination. The first N of these entries, where N is the number of successors, are the current successors. The remaining entries on the list are feasible successors. |
| (46251776/46226176) | The first number is the Enhanced IGRP metric that represents the cost to the destination. The second number is the Enhanced IGRP metric that this peer advertised. |
| Ethernet0 | Interface from which this information was learned. |
To display the number of IP Enhanced IGRP packets sent and received, use the show ip eigrp traffic EXEC command.
show ip eigrp traffic [autonomous-system-number]| autonomous-system-number | (Optional) A decimal number between 1 and 65535. |
EXEC
The following is sample output from the show ip eigrp traffic command:
Router# show ip eigrp traffic
IP-EIGRP Traffic Statistics for process 77
Hellos sent/received: 218/205
Updates sent/received: 7/23
Queries sent/received: 2/0
Replies sent/received: 0/2
Acks sent/received: 21/14
Table 19-20 describes the fields that might be shown in the display.
| Field | Description |
|---|---|
| process 77 | Autonomous system number specified in the ip router command. |
| Hellos sent/received | Number of hello packets that were sent and received. |
| Updates sent/received | Number of update packets that were sent and received. |
| Queries sent/received | Number of query packets that were sent and received. |
| Replies sent/received | Number of reply packets that were sent and received. |
| Acks sent/received | Number of acknowledgment packets that were sent and received. |
To display the multicast groups that are directly connected to the access server and that were learned via IGMP, use the show ip igmp groups EXEC command.
show ip igmp groups [group-name | group-address | type number]| group-name | (Optional) Name of the multicast group, as defined in the DNS hosts table. |
| group-address | (Optional) Address of the multicast group. This is a multicast IP address in four-part dotted notation. |
| type | (Optional) Interface type. |
| number | (Optional) Interface number. |
EXEC
If you omit all optional arguments, the show ip igmp groups command displays by group address and interface type and number all directly connected multicast groups.
The following is sample output of the show ip igmp groups command:
Router> show ip igmp groups
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter
172.24.255.1 Ethernet0 18:51:41 0:02:15 192.168.37.192
172.22.226.60 Ethernet0 1:51:31 0:02:17 192.168.37.192
172.22.127.255 Ethernet0 18:51:45 0:02:17 192.168.37.192
172.26.2.2 Ethernet1 18:51:47 never 0.0.0.0
172.22.0.1 Ethernet0 18:51:43 0:02:14 192.168.37.192
172.25.2.2 Ethernet0 18:51:43 0:02:21 192.168.37.33
172.25.2.2 Ethernet1 18:51:47 never 0.0.0.0
172.25.2.4 Ethernet0 18:18:02 0:02:20 192.168.37.192
172.25.2.4 Ethernet1 18:23:32 0:02:55 192.168.36.128
Table 19-21 describes the fields shown in the display.
| Field | Description |
|---|---|
| Group address | Address of the multicast group. |
| Interface | Interface through which the group is reachable. |
| Uptime | How long in hours, minutes, and seconds this multicast group has been known. |
| Expires | How long in hours, minutes, and seconds until the entry is removed from the IGMP groups table. |
| Last Reporter | Last host to report being a member of the multicast group. |
To display multicast-related information about an interface, use the show ip igmp interface EXEC command.
show ip igmp interface [type number]| type | (Optional) Interface type. |
| number | (Optional) Interface number. |
EXEC
If you omit the optional arguments, the show ip igmp interface command displays information about all interfaces.
This command also displays information about dynamically learned DVMRP access servers on the interface.
The following is sample output from the show ip igmp interface command:
Router> show ip igmp interface
Ethernet0 is up, line protocol is up
Internet address is 192.168.37.6, subnet mask is 255.255.255.0
IGMP is enabled on interface
IGMP query interval is 60 seconds
Inbound IGMP access group is not set
Multicast routing is enabled on interface
Multicast TTL threshold is 0
Multicast designated router (DR) is 192.168.37.33
No multicast groups joined
Ethernet1 is up, line protocol is up
Internet address is 192.168.36.129, subnet mask is 255.255.255.0
IGMP is enabled on interface
IGMP query interval is 60 seconds
Inbound IGMP access group is not set
Multicast routing is enabled on interface
Multicast TTL threshold is 0
Multicast designated router (DR) is 192.168.36.131
Multicast groups joined: 172.25.2.2 172.26.2.2
Tunnel0 is up, line protocol is up
Internet address is 10.1.37.2, subnet mask is 255.255.0.0
IGMP is enabled on interface
IGMP query interval is 60 seconds
Inbound IGMP access group is not set
Multicast routing is enabled on interface
Multicast TTL threshold is 0
No multicast groups joined
Table 19-22 describes the fields shown in the display.
| Field | Description |
|---|---|
| Ethernet0 is up, line protocol is up | Interface type, number, and status. |
| Internet address is... subnet mask is... | Internet address of the interface and subnet mask being applied to the interface, as specified with the ip address interface configuration command. |
| IGMP is enabled on interface | Indicates whether IGMP has been enabled on the interface with the ip pim interface configuration command. |
| IGMP query interval is 60 seconds | Interval at which the access server sends PIM router-query messages, as specified with the ip igmp query-interval interface configuration command. |
| Inbound IGMP access group is not set | Indicates whether an IGMP access group has been configured with the ip igmp access-group interface configuration command. |
| Multicast routing is enabled on interface | Indicates whether multicast routing has been enabled on the interface with the ip pim interface configuration command. |
| Multicast TTL threshold is 0 | Packet time-to-threshold, as specified with the ip multicast-threshold interface configuration command. |
| Multicast designated router (DR) is ... | IP address of the designated router in the autonomous system. |
| Multicast groups joined: No multicast groups joined | Indicates whether this interface is a member of any multicast groups and, if so, lists the IP addresses of the groups. |
ip address
ip igmp access-group
ip igmp query-interval
ip multicast ttl-threshold
ip pim
Use the show ip irdp EXEC command to display IRDP values.
show ip irdpThis command has no arguments or keywords.
EXEC
The following is sample output from the show ip irdp command:
Router# show ip irdp
Ethernet 0 has access server discovery enabled
Advertisements will occur between every 450 and 600 seconds.
Advertisements are valid for 1800 seconds.
Default preference will be 100.
--More--
Serial 0 has access server discovery disabled
--More--
Ethernet 1 has access server discovery disabled
As the display shows, show ip irdp output indicates whether or not access server discovery has been configured for each access server interface, and lists the values of access server discovery configurables for those interfaces on which access server discovery has been enabled. Explanations for the less self-evident lines of output in the display follow.
Advertisements will occur between every 450 and 600 seconds.
Indicates the configured minimum and maximum advertising interval for the interface.
Advertisements are valid for 1800 seconds.
Indicates the configured holdtime values for the interface.
Default preference will be 100.
Indicates the configured (or in this case default) preference value for the interface.
To display the route map used for local policy routing, if any, use the show ip local policy EXEC command.
show ip local policyThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.1.
The following is sample output from the show ip local policy command:
Router# show ip local policy
Local policy routing is enabled, using route map equal
route-map equal, permit, sequence 10
Match clauses:
length 150 200
Set clauses:
ip next-hop 10.10.11.254
Policy routing matches: 0 packets, 0 bytes
route-map equal, permit, sequence 20
Match clauses:
ip address (access-lists): 101
Set clauses:
ip next-hop 10.10.11.14
Policy routing matches: 2 packets, 172 bytes
ip local policy route-map
match ip address
match length
route-map
set default interface
set interface
set ip default next-hop
set ip next-hop
To display the contents of the IP fast switching cache, use the show ip mcache EXEC command.
show ip mcache [group [source]]| group | (Optional) Displays the fast switching cache for the single group. The group argument can be either a Class D IP address or a DNS name. |
| source | (Optional) If source is also specified, displays a single multicast cache entry. The source argument can be either a unicast IP address or a DNS name. |
EXEC
The following is sample output from the show ip mcache command. This entry shows a specific source (wrn-source 204.62.246.73) sending to the World Radio Network group (224.2.143.24).
Router> show ip mcache wrn wrn-source
IP Multicast Fast-Switching Cache
(204.62.246.73/32, 224.2.143.24), Fddi0, Last used: 00:00:00
Ethernet0 MAC Header: 01005E028F1800000C1883D30800
Ethernet1 MAC Header: 01005E028F1800000C1883D60800
Ethernet2 MAC Header: 01005E028F1800000C1883D40800
Ethernet3 MAC Header: 01005E028F1800000C1883D70800
Table 19-23 describes the significant fields in the display.
| Field | Description |
|---|---|
| 204.62.246.73 | Source address. |
| 224.2.143.24 | Destination address. |
| Fddi0 | Incoming or expected interface the packet should be received on. |
| Last used: | Latest time the entry was accessed for a packet that was successfully fast switched. The word "Semi-fast" indicates that the first part of the outgoing interface list is fast switched and the rest of the list is process level switched. |
| Ethernet0
MAC Header: | Outgoing interface list and respective MAC header that is used when rewriting the packet for output. If the interface is a tunnel, the MAC header will show the real next hop MAC header and then in parentheses the real interface name. |
To display the contents of the IP multicast routing table, use the show ip mroute EXEC command.
show ip mroute [group] [source] [summary] [count]| group | (Optional) IP address or name of the multicast group as defined in the DNS hosts table. |
| source | (Optional) IP address or name of a multicast source. |
| summary | (Optional) Displays a one-line, abbreviated summary of each entry in the IP multicast routing table. |
| count | (Optional) Displays statistics about the group and source, including number of packets, packets per second, average packet size, and bits per second. |
EXEC
If you omit all optional arguments and keywords, the show ip mroute command displays all entries in the IP multicast routing table.
The access server populates the multicast routing table by creating source, group (S,G) entries from star, group (*,G) entries. The star refers to all source addresses, the "S" refers to a single source address, and the "G" is the destination multicast group address. In creating (S,G) entries, the access server uses the best path to that destination group found in the unicast routing table (that is, via Reverse Path Forwarding {RPF]).
The following is sample output from the show ip mroute command for a system operating is dense mode. This command displays the contents of the IP multicast routing table for the multicast group named cbone-audio.
Router> show ip mroute cbone-audio
IP Multicast Routing Table
Flags: P - Prune, D - Dense, S - Sparse, C - Connected, L - Local
R - RP-bit set, F - Register flag, T - SPT-bit set
Timers: Uptime/Expires
Interface state: Interface, Next-Hop, State/Mode
(*, 172.24.255.1), uptime 0:57:31, expires 0:02:59, RP is 0.0.0.0, flags: DC
Incoming interface: Null, RPF neighbor 0.0.0.0
Outgoing interface list:
Ethernet0, Forward state, Dense mode, uptime 0:57:31, expires 0:02:52
Tunnel0, Forward state, Dense mode, uptime 0:56:55, expires 0:01:28
(192.168.37.100/32, 172.24.255.1), uptime 20:20:00, expires 0:02:55, flags: C
Incoming interface: Tunnel0, RPF neighbor 10.20.37.33
Outgoing interface list:
Ethernet0, Forward state, Dense mode, uptime 20:20:00, expires 0:02:52
The following is sample output from the show ip mroute command for a system operating in sparse mode:
Router# show ip mroute
IP Multicast Routing Table
Flags: P - Prune, D - Dense, S - Sparse, C - Connected, L - Local
R - RP-bit set, F - Register flag, T - SPT-bit set
Timers: Uptime/Expires
Interface state: Interface, Next-Hop, State/Mode
(*, 172.24.255.3), uptime 5:29:15, RP is 192.168.37.2, flags: SC
Incoming interface: Tunnel0, RPF neighbor 10.3.35.1
Outgoing interface list:
Ethernet0, Forward state, Sparse mode, uptime 5:29:15, expires 0:02:57
(192.168.46.0/24, 172.24.255.3), uptime 5:29:15, expires 0:02:59, flags: C
Incoming interface: Tunnel0, RPF neighbor 10.3.35.1
Outgoing interface list:
Ethernet0, Forward state, Sparse mode, uptime 5:29:15, expires 0:02:57
Table 19-24 explains the fields shown in the displays.
| Field | Description |
|---|---|
| Flags: | Provides information about the entry. |
| D - Dense | Entry is operating in dense mode. |
| S - Sparse | Entry is operating in sparse mode. |
| C - Connected | A member of the multicast group is present on the directly connected interface. |
| L - Local | The router itself is a member of the multicast group. |
| P - Pruned | Route has been pruned. The router keeps this information in case a downstream member wants to join the source. |
| R - Rp-bit set | Indicates that the (S,G) entry is pointing towards the RP. This is typically prune state along the shared tree for a particular source. |
| F - Register flag | Indicates that the router is Registering for a multicast source. |
| T - SPT-bit set | Indicates that packets have been received on the shortest path source tree. |
| (*, 172.24.255.1) (192.168.37.100/32, 172.24.255.1) | Entry in the IP multicast routing table. The entry consists of the IP address of the source access server followed by IP address of the multicast group. An asterisk (*) in place of the source access server indicates all sources.
Entries in the first format are referred to as (*,G,) or "star comma G," entries. Entries in the second format are referred to as (S,G) or ("S comma G") entries. (*,G) entries are used to build (S,G) entries. |
| uptime | How long in hours, minutes, and seconds the entry has been in the IP multicast routing table. |
| expires | How long in hours, minutes, and seconds until the entry will be removed from the IP multicast routing table on the outgoing interface. |
| RP | Address of the rendezvous point (RP) access server. For access servers operating in sparse mode, this address is always 0.0.0.0. |
| flags: | Information about the entry. |
| Incoming interface: | Expected interface for a multicast packet from the source. If the packet is not received on this interface, it is discarded. |
| RPF neighbor | IP address of the upstream access server to the source. |
| Outgoing interface list: | Interfaces through which packets will be forwarded. |
| Ethernet0 | Name and number of the outgoing interface. |
| Forward state | Indicates that packets will be forwarded on the interface if there are no restrictions due to access lists or TTL threshold. |
| Dense mode Sparse mode | Mode in which the interface is operating. |
| Uptime | How long in hours, minutes, and seconds the entry has been in the IP multicast routing table. |
| Expires | How long in hours, minutes, and seconds until the entry will be removed from the IP multicast routing table. |
Use the show ip ospf EXEC command to display general information about OSPF routing processes in a particular access server.
show ip ospf [process-id]| process-id | (Optional) Specifies a process ID. If this argument is included, only information for the specified routing process is included. |
EXEC
The following is sample output from the show ip ospf command when entered without a specific OSPF process ID:
Router# show ip ospf
Routing Process "ospf 201" with ID 192.168.110.200
Supports only single TOS(TOS0) route
It is an area border and autonomous system boundary router
Summary Link update interval is 0:30:00 and the update due in 0:16:26
External Link update interval is 0:30:00 and the update due in 0:16:27
Redistributing External Routes from,
igrp 200 with metric mapped to 2, includes subnets in redistribution
rip with metric mapped to 2
igrp 2 with metric mapped to 100
igrp 32 with metric mapped to 1
Number of areas in this access server is 3
Area 192.168.110.0
Number of interfaces in this area is 1
Area has simple password authentication
SPF algorithm executed 6 times
Area ranges are
Link State Update Interval is 0:30:00 and due in 0:16:55
Link State Age Interval is 0:20:00 and due in 0:06:55
Table 19-25 describes significant fields shown in the display.
| Field | Description |
|---|---|
| Routing process "ospf 201" with ID 192.168.110.200 | Process ID and OSPF access server ID. |
| Type of Service | Number of Types of Service supported (Type 0 only). |
| Type of OSPF Router | Possible types are internal, area border, or autonomous system boundary. |
| Summary Link update interval | Specify summary update interval in hours:minutes:seconds, and time to next update. |
| External Link update interval | Specify external update interval in hours:minutes:seconds, and time to next update. |
| Redistributing External Routes from | Lists of redistributed routes, by protocol. |
| Number of areas | Number of areas in the access server, area addresses, and so on. |
| Link State Update Interval | Specify access server and network link state update interval in hours:minutes:seconds, and time to next update. |
| Link State Age Interval | Specify max-aged update deletion interval and time until next database cleanup in hours:minutes:seconds. |
Use the show ip ospf border-routers privileged EXEC command to display the internal OSPF routing table entries to an access server acting as an Area Border Router (ABR) or Autonomous System Boundary Router (ASBR).
show ip ospf borders-routersThis command has no arguments or keywords.
Privileged EXEC
The following is sample output from the show ip ospf border-routers command:
Router# show ip ospf border-routers
OSPF Process 109 internal Routing Table
Destination Next Hop Cost Type Rte Type Area SPF No
192.168.97.53 172.24.1.53 10 ABR INTRA 0.0.0.3 3
192.168.103.51 192.168.96.51 10 ABR INTRA 0.0.0.3 3
192.168.103.52 192.168.96.51 20 ASBR INTER 0.0.0.3 3
192.168.103.52 172.24.1.53 22 ASBR INTER 0.0.0.3 3
Table 19-26 describes the fields shown in the display.
| Field | Description |
|---|---|
| Destination | Destination access server ID. |
| Next Hop | Next hop toward the destination. |
| Cost | Cost of using this route. |
| Type | The access server type of the destination; it is either an Area Border Router (ABR) or Autonomous System Boundary Router (ASBR) or both. |
| Rte Type | The type of this route, it is either an intra-area or interarea route. |
| Area | The area ID of the area that this route is learned from. |
| SPF No | The internal number of SPF calculation that installs this route. |
Use the show ip ospf database EXEC command to display lists of information related to the OSPF database for a specific access server. The various forms of this command deliver information about different OSPF link state advertisements.
show ip ospf [process-id area-id] databaseEXEC
| process-id | (Optional) Internally used identification parameter. It is locally assigned and can be any positive integer number. The number used here is the number assigned administratively when enabling the OSPF routing process. |
| area-id | (Optional) Area number associated with the OSPF address range defined in the network router configuration command used to define the particular area. |
| link-state-id | (Optional) Identifies the portion of the Internet environment that is being described by the advertisement. The value entered depends on the advertisement's LS type. It must be entered in the form of an IP address.
When the link state advertisement is describing a network, the link-state-id can take one of two forms: --The network's IP address (as in type 3 summary link advertisements and in autonomous system external link advertisements). --A derived address obtained from the link state ID. (Note that masking a network links advertisement's link state ID with the network's subnet mask yields the network's IP address.) When the link state advertisement is describing a router, the link state ID is always the described router's OSPF router ID. When an autonomous system external advertisement (LS Type = 5) is describing a default route, its link state ID is set to Default Destination (0.0.0.0). |
When entered with the optional keywords router, network, summary, asb-summary, and external, different displays result. Examples and brief descriptions of each form follow.
The following is sample output from the show ip ospf database command when no optional arguments or keywords are used:
Router# show ip ospf database
OSPF Router with id(192.168.239.66) (Autonomous system 300)
Displaying Router Link States(Area 0.0.0.0)
Link ID ADV Router Age Seq# Checksum Link count
172.18.21.6 172.18.21.6 1731 0x80002CFB 0x69BC 8
172.18.21.5 172.18.21.5 1112 0x800009D2 0xA2B8 5
172.18.1.2 172.18.1.2 1662 0x80000A98 0x4CB6 9
172.18.1.1 172.18.1.1 1115 0x800009B6 0x5F2C 1
172.18.1.5 172.18.1.5 1691 0x80002BC 0x2A1A 5
172.18.65.6 172.18.65.6 1395 0x80001947 0xEEE1 4
172.18.241.5 172.18.241.5 1161 0x8000007C 0x7C70 1
172.18.27.6 172.18.27.6 1723 0x80000548 0x8641 4
172.18.70.6 172.18.70.6 1485 0x80000B97 0xEB84 6
Displaying Net Link States(Area 0.0.0.0)
Link ID ADV Router Age Seq# Checksum
172.18.1.3 192.20.239.66 1245 0x800000EC 0x82E
Displaying Summary Net Link States(Area 0.0.0.0)
Link ID ADV Router Age Seq# Checksum
172.18.240.0 172.18.241.5 1152 0x80000077 0x7A05
172.18.241.0 172.18.241.5 1152 0x80000070 0xAEB7
172.18.244.0 172.18.241.5 1152 0x80000071 0x95CB
Table 19-27 describes significant fields shown in the display.
| Field | Description |
|---|---|
| Link ID | Access server ID number. |
| ADV Router | Advertising access server's ID. |
| Age | Link state age. |
| Seq# | Link state sequence number (detects old or duplicate link state advertisements). |
| Checksum | Fletcher checksum of the complete contents of the link state advertisement. |
| Link count | Number of interfaces detected for access server. |
The following is sample output from the show ip ospf database EXEC command when no optional arguments are specified:
Router# show ip ospf database asb-summary
OSPF Router with id(192.168.239.66) (Autonomous system 300)
Displaying Summary ASB Link States(Area 0.0.0.0)
LS age: 1463
Options: (No TOS-capability)
LS Type: Summary Links(AS Boundary Router)
Link State ID: 172.18.245.1 (AS Boundary Router address)
Advertising Router: 172.18.241.5
LS Seq Number: 80000072
Checksum: 0x3548
Length: 28
Network Mask: 0.0.0.0 TOS: 0 Metric: 1
Table 19-28 describes significant fields shown in the display.
| Field | Description |
|---|---|
| Router ID | Router ID number. |
| Autonomous system | OSPF autonomous system number (OSPF process ID). |
| LS age | Link state age. |
| Options | Type of Service options (Type 0 only). |
| LS Type | Link state type. |
| Link State ID | Link state ID (autonomous system boundary router). |
| Advertising Router | Advertising router's router ID. |
| LS Seq Number | Link state sequence (detects old or duplicate link state advertisements). |
| Checksum | LS checksum (Fletcher checksum of the complete contents of the link state advertisement). |
| Length | Length in bytes of the link state advertisement. |
| Network Mask | Network mask implemented. |
| TOS | Type of Service. |
| Metric | Link state metric. |
The following is sample output from the show ip ospf database external command when no optional arguments are specified:
Router# show ip ospf database external
OSPF Router with id(192.168.239.66) (Autonomous system 300)
Displaying AS External Link States
LS age: 280
Options: (No TOS-capability)
LS Type: AS External Link
Link State ID: 192.168.0.0 (External Network Number)
Advertising Router: 172.18.70.6
LS Seq Number: 80000AFD
Checksum: 0xC3A
Length: 36
Network Mask: 255.255.0.0
Metric Type: 2 (Larger than any link state path)
TOS: 0
Metric: 1
Forward Address: 0.0.0.0
External Route Tag: 0
Table 19-29 describes significant fields shown in the display.
| Field | Description |
|---|---|
| Router ID | ID number of the router or access server. |
| Autonomous system | OSPF autonomous system number (OSPF process ID). |
| LS age | Link state age. |
| Options | Type of Service options (Type 0 only). |
| LS Type | Link state type. |
| Link State ID | Link state ID (External Network Number). |
| Advertising Router | Advertising device's router ID. |
| LS Seq Number | Link state sequence number (detects old or duplicate link state advertisements). |
| Checksum | LS checksum (Fletcher checksum of the complete contents of the link state advertisement). |
| Length | Length in bytes of the link state advertisement. |
| Network Mask | Network mask implemented. |
| Metric Type | External Type. |
| TOS | Type of Service. |
| Metric | Link state metric. |
| Forward Address | Forwarding address. Data traffic for the advertised destination will be forwarded to this address. If the forwarding address is set to 0.0.0.0, data traffic will be forwarded instead to the advertisement's originator. |
| External Route Tag | External route tag, a 32-bit field attached to each external route. This is not used by the OSPF protocol itself. |
The following is sample output from the show ip ospf database network command when no optional arguments are specified:
Router# show ip ospf database network
OSPF Router with id(192.168.239.66) (Autonomous system 300)
Displaying Net Link States(Area 0.0.0.0)
LS age: 1367
Options: (No TOS-capability)
LS Type: Network Links
Link State ID: 172.18.1.3 (address of Designated Router)
Advertising Router: 192.168.239.66
LS Seq Number: 800000E7
Checksum: 0x1229
Length: 52
Network Mask: 255.255.255.0
Attached Router: 192.168.239.66
Attached Router: 172.18.241.5
Attached Router: 172.18.1.1
Attached Router: 172.18.54.5
Attached Router: 172.18.1.5
Table 19-30 describes significant fields shown in the display.
| Field | Description |
|---|---|
| OSPF Router with ID(192.168.239.66) | ID number of the router or access server. |
| Autonomous system 300 | OSPF autonomous system number (OSPF process ID). |
| LS age: 1367 | Link state age. |
| Options: (No TOS-capability) | Type of Service options (Type 0 only). |
| LS Type: Network Links | Link state type. |
| Link State ID | Link state ID of designated router. |
| Advertising Router | Advertising device's router ID. |
| LS Seq Number | Link state sequence (detects old or duplicate link state advertisements). |
| Checksum | LS checksum (Fletcher checksum of the complete contents of the link state advertisement). |
| Network Mask | Network mask implemented. |
| AS Boundary Router | Definition of device type. |
| Other fields | List of routers or access servers attached to the network, by IP address. |
The following is sample output from the show ip ospf database router command when no optional arguments are specified:
Router# show ip ospf database router
OSPF Router with id(192.168.239.66) (Autonomous system 300)
Displaying Router Link States(Area 0.0.0.0)
LS age: 1176
Options: (No TOS-capability)
LS Type: Router Links
Link State ID: 172.18.21.6
Advertising Router: 172.18.21.6
LS Seq Number: 80002CF6
Checksum: 0x73B7
Length: 120
AS Boundary Router
155 Number of Links: 8
Link connected to: another Router (point-to-point)
(link ID) Neighboring Router ID: 172.18.21.5
(Link Data) Router Interface address: 172.18.21.6
Number of TOS metrics: 0
TOS 0 Metrics: 2
Table 19-31 describes significant fields shown in the display.
| Field | Description |
|---|---|
| Router ID | ID number of the router or access server. |
| Autonomous system | OSPF autonomous system number (OSPF process ID). |
| LS age | Link state age. |
| Options | Type of Service options (Type 0 only). |
| LS Type | Link state type. |
| Link State ID | Link state ID. |
| Advertising Router | Advertising router's router ID. |
| LS Seq Number | Link state sequence (detects old or duplicate link state advertisements). |
| Checksum | LS checksum (Fletcher checksum of the complete contents of the link state advertisement). |
| Length | Length in bytes of the link state advertisement. |
| AS Boundary Router | Definition of device type. |
| Number of Links | Number of active links. |
| link ID | Link type. |
| Link Data | Device interface address. |
| TOS | Type of Service metric (Type 0 only). |
The following is sample output from show ip ospf database summary command when no optional arguments are specified:
Router# show ip ospf database summary
OSPF Router with id(192.168.239.66) (Autonomous system 300)
Displaying Summary Net Link States(Area 0.0.0.0)
LS age: 1401
Options: (No TOS-capability)
LS Type: Summary Links(Network)
Link State ID: 172.18.240.0 (summary Network Number)
Advertising Router: 172.18.241.5
LS Seq Number: 80000072
Checksum: 0x84FF
Length: 28
Network Mask: 255.255.255.0 TOS: 0 Metric: 1
Table 19-32 describes significant fields shown in the display.
| Field | Description |
|---|---|
| Router ID | Access server ID number. |
| Autonomous system | OSPF autonomous system number (OSPF process ID). |
| LS age | Link state age. |
| Options | Type of Service options (Type 0 only). |
| LS Type | Link state type. |
| Link State ID | Link state ID (summary network number). |
| Advertising Router | Advertising access server's ID. |
| LS Seq Number | Link state sequence (detects old or duplicate link state advertisements). |
| Checksum | LS checksum (Fletcher checksum of the complete contents of the link state advertisement). |
| Length | Length in bytes of the link state advertisement. |
| Network Mask | Network mask implemented. |
| TOS | Type of Service. |
| Metric | Link state metric. |
The following is sample output from the show ip ospf database asb-summary command when no optional arguments are specified:
Router# show ip ospf database database-summary
OSPF Router with ID (172.19.65.21) (Process ID 1)
Area ID Router Network Sum-Net Sum-ASBR Subtotal Delete Maxage
202 1 0 0 0 1 0 0
AS External 0 0 0
Total 1 0 0 0 1
Table 19-33 describes significant fields shown in the display.
| Field | Description |
|---|---|
| Area ID | Area number. |
| Router | Number of router link state advertisements in that area. |
| Network | Number of network link state advertisements in that area. |
| Sum-Net | Number of summary link state advertisements in that area. |
| Sum-ASBR | Number of summary autonomous system boundary router (ASBR) link state advertisements in that area. |
| Subtotal | Sum of Router, Network, Sum-Net, and Sum-ASBR for that area. |
| Delete | Number of link state advertisements that are marked "Deleted" in that area. |
| Maxage | Number of link state advertisements that are marked "Maxaged" in that area. |
| AS External | Number of external link state advertisements. |
Use the show ip ospf interface EXEC command to display OSPF-related interface information.
show ip ospf interface [type number]| type | (Optional) Interface type |
| number | (Optional) Interface number |
EXEC
The following is sample output from the show ip ospf interface command when Ethernet 0 is specified:
Router# show ip ospf interface ethernet 0
Ethernet 0 is up, line protocol is up
Internet Address 172.19.254.202, Mask 255.255.255.0, Area 0.0.0.0
AS 201, Router ID 192.168.99.1, Network Type BROADCAST, Cost: 10
Transmit Delay is 1 sec, State OTHER, Priority 1
Designated Router id 172.19.254.10, Interface address 172.19.254.10
Backup Designated access server id 172.19.254.28, Interface addr 172.19.254.28
Timer intervals configured, Hello 10, Dead 60, Wait 40, Retransmit 5
Hello due in 0:00:05
Neighbor Count is 8, Adjacent neighbor count is 2
Adjacent with neighbor 172.19.254.28 (Backup Designated Router)
Adjacent with neighbor 172.19.254.10 (Designated Router)
Table 19-34 describes significant fields shown in the display.
| Field | Description |
|---|---|
| Ethernet | Status of physical link and operational status of protocol. |
| Internet Address | Interface IP address, subnet mask, and area address. |
| AS | Autonomous system number (OSPF process ID), access server ID, network type, link state cost. |
| Transmit Delay | Transmit delay, interface state, and access server priority. |
| Designated Router | Designated access server ID and respective interface IP address. |
| Backup Designated router | Backup designated access server ID and respective interface IP address. |
| Timer intervals configured | Configuration of timer intervals. |
| Hello | Number of seconds until next Hello packet is sent out this interface. |
| Neighbor Count | Count of network neighbors and list of adjacent neighbors. |
Use the show ip ospf neighbor EXEC command to display OSPF-neighbor information on a per-interface basis.
show ip ospf neighbor [type number] [neighbor-id] detail| type | (Optional) Interface type |
| number | (Optional) Interface number |
| neighbor-id | (Optional) Neighbor ID |
| detail | Displays all neighbors given in detail (list all neighbors) |
EXEC
The following is sample output from the show ip ospf neighbor command showing a single line of summary information for each neighbor:
Router# show ip ospf neighbor
ID Pri State Dead Time Address Interface
192.168.199.137 1 FULL/DR 0:00:31 192.168.80.37 Ethernet0
192.168.48.1 1 FULL/DROTHER 0:00:33 192.168.48.1 Fddi0
192.168.48.200 1 FULL/DROTHER 0:00:33 192.168.48.200 Fddi0
192.168.199.137 5 FULL/DR 0:00:33 192.168.48.189 Fddi0
The following is sample output showing summary information about the neighbor that matches the Neighbor ID:
Router# show ip ospf neighbor 192.168.199.137
Neighbor 192.168.199.137, interface address 192.168.80.37
In the area 0.0.0.0 via interface Ethernet0
Neighbor priority is 1, State is FULL
Options 2
Dead timer due in 0:00:32
Link State retransmission due in 0:00:04
Neighbor 192.168.199.137, interface address 192.168.48.189
In the area 0.0.0.0 via interface Fddi0
Neighbor priority is 5, State is FULL
Options 2
Dead timer due in 0:00:32
Link State retransmission due in 0:00:03
If you specify the interface along with the Neighbor ID, the access server displays the neighbors that match the Neighbor ID on the interface, as in the following sample display:
Router# show ip ospf neighbor ethernet 0 192.168.199.137
Neighbor 192.168.199.137, interface address 192.168.80.37
In the area 0.0.0.0 via interface Ethernet0
Neighbor priority is 1, State is FULL
Options 2
Dead timer due in 0:00:37
Link State retransmission due in 0:00:04
You can also specify the interface without the Neighbor ID to show all neighbors on the specified interface, as in the following sample display:
Router# show ip ospf neighbor fddi 0
ID Pri State Dead Time Address Interface
192.168.48.1 1 FULL/DROTHER 0:00:33 192.168.48.1 Fddi0
192.168.48.200 1 FULL/DROTHER 0:00:32 192.168.48.200 Fddi0
192.168.199.137 5 FULL/DR 0:00:32 192.168.48.189 Fddi0
The following is sample output from the show ip ospf neighbor detail command:
Router# show ip ospf neighbor detail
Neighbor 192.168.96.54, interface address 192.168.96.54
In the area 0.0.0.3 via interface Ethernet0
Neighbor priority is 1, State is FULL
Options 2
Dead timer due in 0:00:38
Neighbor 192.168.103.52, interface address 192.168.103.52
In the area 0.0.0.0 via interface Serial0
Neighbor priority is 1, State is FULL
Options 2
Dead timer due in 0:00:31
Table 19-35 describes significant fields shown in the previous displays.
| Field | Description |
|---|---|
| Neighbor x.x.x.x | Neighbor access server ID. |
| interface address x.x.x.x | IP address of the interface. |
| In the area | Area and interface through which OSPF neighbor is known. |
| Neighbor priority | Access server priority of neighbor, neighbor state. |
| State | OSPF state. |
| Options | Hello packet options field contents (E-bit only; possible values are 0 and 2; 2 indicates area is not a stub; 0 indicates area is a stub. |
| Dead timer | Expected time before access server will declare neighbor dead. |
Use the show ip ospf virtual-links EXEC command to display the parameters and current state of OSPF virtual links.
show ip ospf virtual-linksThis command has no arguments or keywords.
EXEC
The information displayed by show ip ospf virtual-links is useful in debugging OSPF routing operations.
The following is sample output from the show ip ospf virtual-links command:
Router# show ip ospf virtual-links
Virtual Link to access server 192.168.101.2 is up
Transit area 0.0.0.1, via interface Ethernet0, Cost of using 10
Transmit Delay is 1 sec, State POINT_TO_POINT
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Hello due in 0:00:08
Adjacency State FULL
Table 19-36 describes significant fields shown in the display.
| Field | Description |
|---|---|
| Virtual Link to access server 192.168.101.2 is Up | Specifies the OSPF neighbor, and if the link to that neighbor is Up or Down. |
| Transit area 0.0.0.1 | The transit area through which the virtual link is formed. |
| via interface Ethernet0 | The interface through which the virtual link is formed. |
| Cost of using 10 | The cost of reaching the OSPF neighbor through the virtual link. |
| Transmit Delay is 1 sec | The transmit delay on the virtual link. |
| State POINT_TO_POINT | The state of the OSPF neighbor. |
| Timer intervals... | The various timer intervals configured for the link. |
| Hello due in 0:00:08 | When the next Hello is expected from the neighbor. |
| Adjacency State FULL | The adjacency state between the neighbors. |
To display information about interfaces configured for PIM, use the show ip pim interface EXEC command.
show ip pim interface [type number]| type | (Optional) Interface type. |
| number | (Optional) Interface number. |
EXEC
This command works only on interfaces that are configured for PIM.
The following is sample output from the show ip pim interface command:
Router> show ip pim interface
Address Interface Mode Neighbor Query DR
Count Interval
192.168.37.6 Ethernet0 Dense 2 30 192.168.37.33
192.168.36.129 Ethernet1 Dense 2 30 192.168.36.131
10.1.37.2 Tunnel0 Dense 1 30 0.0.0.0
Table 19-37 describes the fields shown in the display.
| Field | Description |
|---|---|
| Address | IP address of the next-hop access server. |
| Interface | Interface type and number that is configured to run PIM. |
| Mode | Multicast mode in which the access server is operating. This can be dense mode or sparse mode. |
| Neighbor Count | Number of PIM neighbors that have been discovered through this interface. |
| Query Interval | Frequency, in seconds, of PIM router-query messages, as set by the ip pim query-interval interface configuration command. The default is 30 seconds. |
| DR | IP address of the designated router on the LAN. Note that serial lines do not have designated routers, so the IP address is shown as 0.0.0.0. |
To list the PIM neighbors discovered by the access server, use the show ip pim neighbor EXEC command.
show ip pim neighbor [type number]| type | (Optional) Interface type. |
| number | (Optional) Interface number. |
EXEC
Use this command to determine which access servers on the LAN are configured for PIM.
The following is sample output from the show ip pim neighbor command:
Router> show ip pim neighbor
PIM Neighbor Table
Neighbor Address Interface Uptime Expires
192.168.37.2 Ethernet0 17:38:16 0:01:25
192.168.37.33 Ethernet0 17:33:20 0:01:05 (DR)
192.168.36.131 Ethernet1 17:33:20 0:01:08 (DR)
192.168.36.130 Ethernet1 18:56:06 0:01:04
10.1.22.9 Tunnel0 19:14:59 0:01:09
Table 19-38 describes the fields shown in the display.
| Field | Description |
|---|---|
| Neighbor Address | IP address of the PIM neighbor. |
| Interface | Interface type and number on which the neighbor is reachable. |
| Uptime | How long in hours, minutes, and seconds the entry has been in the PIM neighbor table. |
| Expires | How long in hours, minutes, and seconds until the entry will be removed from the IP multicast routing table. |
| (DR) | Indicates that this neighbor is a designated router on the LAN. |
To display the rendezvous point (RP) access servers associated with a sparse-mode multicast group, use the show ip pim rp EXEC command.
show ip pim rp [group-name | group-address]| group-name | (Optional) Name of the multicast group, as defined in the DNS hosts table. |
| group-address | (Optional) Address of the multicast group. This is a multicast IP address in four-part dotted notation. |
EXEC
The following is sample output from the show ip pim rp command from an access server that is not an RP:
Router> show ip pim rp
Group: 172.22.127.255, number of RPs: 1
RP address: 192.168.37.2, state: Tunnel, uptime 0:01:25, expires in 0:03:04
The following is sample output from the show ip pim rp command from an access server that is an RP:
Router# show ip pim rp
Group: 172.22.127.255, number of RPs: 1
RP address: 192.168.37.2, state: Up, next RP-reachable in 0:01:01
Table 19-39 explains the fields shown in the displays.
| Field | Description |
|---|---|
| Group: | Address of the multicast group. |
| number of RPs: | Number of RPs in the multicast group. |
| RP address: | Address of the RP. |
| state: | |
| uptime | |
| expires | |
| next RP-reachable in |
Use the show ip protocols EXEC command to display the parameters and current state of the active routing protocol process.
show ip protocolsThis command has no arguments or keywords.
EXEC
The information displayed by show ip protocols is useful in debugging routing operations. Information in the Routing Information Sources field of the show ip protocols output can help you identify an access server suspected of delivering bad routing information.
The following is sample output from the show ip protocols command, showing IGRP processes:
Router# show ip protocols
Routing Protocol is "igrp 109"
Sending updates every 90 seconds, next due in 44 seconds
Invalid after 270 seconds, hold down 280, flushed after 630
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Default networks flagged in outgoing updates
Default networks accepted from incoming updates
IGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
IGRP maximum hopcount 100
IGRP maximum metric variance 1
Redistributing: igrp 109
Routing for Networks:
192.168.72.0
Routing Information Sources:
Gateway Distance Last Update
192.168.72.18 100 0:56:41
192.168.72.19 100 6d19
192.168.72.22 100 0:55:41
192.168.72.20 100 0:01:04
192.168.72.30 100 0:01:29
Distance: (default is 100)
Routing Protocol is "bgp 1878"
Sending updates every 60 seconds, next due in 0 seconds
Outgoing update filter list for all interfaces is 1
Incoming update filter list for all interfaces is not set
Redistributing: igrp 109
IGP synchronization is disabled
Automatic route summarization is enabled
Neighbor(s):
Address FiltIn FiltOut DistIn DistOut Weight RouteMap
172.18.211.17 1
172.18.213.89 1
198.6.255.13 1
192.168.72.18 1
192.168.72.19
192.168.84.17 1
Routing for Networks:
172.18.209.0
172.18.211.0
172.26.254.0
Routing Information Sources:
Gateway Distance Last Update
192.168.72.19 20 0:05:28
Distance: external 20 internal 200 local 200
Table 19-40 describes significant fields shown in the display.
| Field | Description |
|---|---|
| Routing Protocol is "igrp 109" | Specifies the routing protocol used. |
| Sending updates every 90 seconds | Specifies the time between sending updates. |
| next due in 88 seconds | Precisely when the next update is due to be sent. |
| Invalid after 270 seconds | Specifies the value of the invalid parameter. |
| hold down for 280 | Specifies the current value of the hold-down parameter. |
| flushed after 630 | Specifies the time in seconds after which the individual routing information will be thrown (flushed) out. |
| Outgoing update... | Specifies whether the outgoing filtering list has been set. |
| Incoming update ... | Specifies whether the incoming filtering list has been set. |
| Default networks | Specifies how these networks will be handled in both incoming and outgoing updates. |
| IGRP metric | Specifies the value of the K0-K5 metrics as well as the maximum hopcount. |
| Redistributing | Lists the protocol that is being redistributed. |
| Routing | Specifies the networks that the routing process is currently injecting routes for. |
| Routing Information Sources | Lists all the routing sources the access server is using to build its routing table. For each source, you will see displayed:
|
Use the show ip route EXEC command to display the current state of the routing table.
show ip route [ip-address [mask] | protocol [process-id]]| ip-address | (Optional) Address for which to display routing information. |
| mask | (Optional) Subnet mask of the subnet for which to display routing information. |
| 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) Identifier for the particular routing protocol process. |
EXEC
The following is sample output from the show ip route command when entered without an address:
Router# show ip route
Codes: I - IGRP derived, R - RIP derived, O - OSPF derived
C - connected, S - static, E - EGP derived, B - BGP derived
* - candidate default route, IA - OSPF inter area route
E1 - OSPF external type 1 route, E2 - OSPF external type 2 route
Gateway of last resort is 172.19.254.240 to network 172.29.0.0
O E2 150.150.0.0 [160/5] via 172.19.254.6, 0:01:00, Ethernet2
E 192.67.131.0 [200/128] via 172.19.254.244, 0:02:22, Ethernet2
O E2 192.68.132.0 [160/5] via 172.19.254.6, 0:00:59, Ethernet2
O E2 130.130.0.0 [160/5] via 172.19.254.6, 0:00:59, Ethernet2
E 128.128.0.0 [200/128] via 172.19.254.244, 0:02:22, Ethernet2
E 129.129.0.0 [200/129] via 172.19.254.240, 0:02:22, Ethernet2
E 192.65.129.0 [200/128] via 172.19.254.244, 0:02:22, Ethernet2
E 131.131.0.0 [200/128] via 172.19.254.244, 0:02:22, Ethernet2
E 192.75.139.0 [200/129] via 172.19.254.240, 0:02:23, Ethernet2
E 192.16.208.0 [200/128] via 172.19.254.244, 0:02:22, Ethernet2
E 192.84.148.0 [200/129] via 172.19.254.240, 0:02:23, Ethernet2
E 192.168.223.0 [200/128] via 172.19.254.244, 0:02:22, Ethernet2
E 192.44.236.0 [200/129] via 172.19.254.240, 0:02:23, Ethernet2
E 140.141.0.0 [200/129] via 172.19.254.240, 0:02:22, Ethernet2
E 141.140.0.0 [200/129] via 172.19.254.240, 0:02:23, Ethernet2
Table 19-37 describes significant fields shown in this display.
| Field | Description |
|---|---|
| O | Indicates protocol that derived the route. Possible values include the following:
|
|
E2 | Type of route. Possible values include the following:
|
|
150.150.0.0 | Indicates the address of the remote network. |
| [160/5] | The first number in the brackets is the administrative distance of the information source; the second number is the metric for the route. |
| via 172.19.254.6 | Specifies the address of the next access server to the remote network. |
| 0:01:00 | Specifies the last time the route was updated in hours:minutes:seconds. |
| Ethernet 2 | Specifies the interface through which the specified network can be reached. |
| * | Indicates the last path used when a packet was forwarded. It pertains only to the nonfast-switched packets. However, it does not indicate what path will be used next when forwarding a nonfast-switched packet except when the paths are equal cost. |
When you specify that you want information about a specific network displayed, more detailed statistics are shown. The following is sample output from the show ip route command when entered with the address 172.19.0.0.
Router# show ip route 172.19.0.0
Routing entry for 172.19.0.0 (mask 255.255.0.0)
Known via "igrp 109", distance 100, metric 10989
Tag 0
Redistributing via igrp 109
Last update from 172.16.35.13 on TokenRing0, 0:00:58 ago
Routing Descriptor Blocks:
* 172.16.35.13, from 172.16.35.13, 0:00:58 ago, via TokenRing0
Route metric is 10989, traffic share count is 1
Total delay is 45130 microseconds, minimum bandwidth is 1544 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 2/255, Hops 4
Table 19-38 describes significant fields shown in this display.
| Field | Description |
|---|---|
| Routing entry for 172.19.0.0 (mask 255.255.0.0) | Network number and mask. |
| Known via "igrp 109" | Indicates how the route was derived. |
| distance 100 | Administrative distance of the information source. |
| Tag 0 | Integer that is used to implement the route. |
| Redistributing via igrp 109 | Indicates redistribution protocol. |
| Last update from 172.16.35.13 on TokenRing0 | Indicates the IP address of an access server that is the next hop to the remote network and the access server interface on which the last update arrived. |
| 0:00:58 ago | Specifies the last time the route was updated in hours:minutes:seconds. |
| 172.16.35.13, from 172.16.35.13, 0:00:58 ago | Indicates the next hop address, the address of the gateway that sent the update, and the time that has elapsed since this update was received in hours:minutes:seconds. |
| via TokenRing0 | Interface for this route. |
| Route metric is 10989 | This value is the best metric for this routing descriptor block. |
| traffic share count is 1 | Number of uses for this routing descriptor block. |
| Total delay is 45130 microseconds | Total propagation delay in microseconds. |
| minimum bandwidth is 1544 Kbit | Minimum bandwidth encountered when transmitting data along this route. |
| Reliability 255/255 | Likelihood of successful packet transmission expressed as a number between 0 and 255 (255 is 100% reliability). |
| minimum MTU 1500 bytes | Smallest MTU along the path. |
| Loading 2/255 | Effective bandwidth of the route in kilobits per second/255 is saturation. |
| Hops 4 | Hops to the destination or to the access server where the route first enters IGRP. |
A dagger (+) indicates that this command is documented in another chapter.
show interfaces tunnel +
show ip route summary
Use the show ip route summary EXEC command to display the current state of the routing table.
show ip route summaryThis command has no arguments or keywords.
EXEC
The following is sample output from the show ip route summary command:
Router# show ip route summary
Route Source Networks Subnets Overhead Memory (bytes)
connected 0 3 126 360
static 1 2 126 360
igrp 109 747 12 31878 91080
internal 3 360
Total 751 17 32130 92160
Router#
Table 19-39 describes the fields shown in the display:
| Field | Description |
|---|---|
| Route Source | Routing protocol name, or connected, static, or internal. Internal--those routes that are in the primary routing table merely as markers to hold subnet routes. These routes are not owned by any routing protocol. There should be one of these internal routes for each subnetted network in the routing table. |
| Networks | The number of Class A, B, or C networks that are present in the routing table for each route source. |
| Subnets | The number of subnets that are present in the routing table for each route source, including host routes. |
| Overhead | Any additional memory involved in allocating the routes for the particular route source other than the memory specified under "Memory." |
| Memory | The number of bytes allocated to maintain all the routes for the particular route source. |
Use the show ip route supernets-only privileged EXEC command to display information about supernets.
show ip route supernets-onlyPrivileged EXEC
The following is sample output from the show ip route supernets-only command:
Router# show ip route supernets-only
Codes: I - IGRP derived, R - RIP derived, O - OSPF derived
C - connected, S - static, E - EGP derived, B - BGP derived
i - IS-IS derived, D - EIGRP derived
* - candidate default route, IA - OSPF inter area route
E1 - OSPF external type 1 route, E2 - OSPF external type 2 route
L1 - IS-IS level-1 route, L2 - IS-IS level-2 route
EX - EIGRP external route
Gateway of last resort is not set
B 192.168.0.0 (mask is 255.255.0.0) [20/0] via 192.168.72.30, 0:00:50
B 192.0.0.0 (mask is 255.0.0.0) [20/0] via 192.168.72.24, 0:02:50
This display shows supernets only; it does not show subnets.
To display the contents of the session directory cache, use the show ip sd EXEC command.
show ip sd [group | "session-name" | detail]| group | (Optional) Displays the session(s) defining the multicast group in detail format. |
| "session-name" | (Optional) Displays the single session in detail format. Can be in uppercase or lowercase and still match. The session name is enclosed in quotation marks. |
| detail | (Optional) Displays all sessions in detail format. |
EXEC
If the router is configured to be a member of 224.2.127.255 (the default session directory group), it will cache session directory announcements. If no arguments are used, a sorted list of session names is displayed.
The following is sample output from the show ip sd command, showing each session that the router has learned:
Router> show ip sd
SD Cache - 22 entries
*cisco: CABONE Audio
*cisco: CABONE Video
*cisco: CABONE Whiteboard
*cisco: CBONE audio
*cisco: CBONE video
*cisco: CBONE Whiteboard
*cisco: CCIE Audio
*cisco:Eng Services Ops Review
*cisco:Scamp's Managers Meeting
A3TEST
aki
APLtest
arch-nus
Bharat Dave-ETH
cbone
CERN - LHCC
cisco: Beta Folks
DB
DECUS '95: Marc Andreessen (audio)
DECUS '95: Marc Andreessen (vic/h261)
Digital Unix Multicast
DSTC Fun with whiteboard
The following is sample output from the show ip sd detail command:
Router# show ip sd detail
SD Cache - 3 entries
Session Name: *cisco: CABONE Audio
Description: cisco Customer Advocacy Audio Channel
Group: 224.0.255.128, ttl: 16
Lifetime: from 00:00:24 PDT May 9 1995 until 00:00:24 PDT May 23 1995
Created by: bpinsky@on-tap.cisco.com (171.68.225.179)
Media: audio 55557 2688
--More--
Session Name: *cisco: CABONE Video
Description: cisco Customer Advocacy Video Channel
Group: 224.0.255.130, ttl: 16
Lifetime: from 00:00:56 PDT May 9 1995 until 00:00:56 PDT May 23 1995
Created by: bpinsky@on-tap.cisco.com (171.68.225.179)
Media: video 62676 63933
--More--
Session Name: *cisco: CABONE Whiteboard
Description: cisco Customer Advocacy Whiteboard
Group: 224.0.255.129, ttl: 16
Lifetime: from 00:00:30 PDT May 9 1995 until 00:00:30 PDT May 23 1995
Created by: bpinsky@on-tap.cisco.com (171.68.225.179)
Media: whiteboard 43411 14736
Table 19-40 describes the significant fields in the display.
| Field | Description |
|---|---|
| Session Name | Name of the session. |
| Description | Description of the session. |
| Group | Group address. |
| ttl | Time-to-live for the session. |
| Lifetime | Lifetime of the session advertisement. |
| Created by | Creator of the session. |
| Media | Type of media, port number and conference ID. |
Use the show route-map EXEC command to display all route-maps configured or only the one specified.
show route-map [map-name]| map-name | (Optional) Name of a specific route-map. |
EXEC
The following is sample output from the show route-map command:
Router# show route-map
route-map foo, permit, sequence 10
Match clauses:
tag 1 2
Set clauses:
metric 5
route-map foo, permit, sequence 20
Match clauses:
tag 3 4
Set clauses:
metric 6
Table 19-41 describes the fields shown in the display:
| Field | Description |
|---|---|
| route-map | Name of the route-map. |
| permit | Indicates that the route is redistributed as controlled by the set actions. |
| sequence | Number that indicates the position a new route map is to have in the list of route maps already configured with the same name. |
| Match clauses tag | Match criteria--conditions under which redistribution is allowed for the current route-map. |
| Set clauses metric | Set actions--the particular redistribution actions to perform if the criteria enforced by the match commands are met. |
Use the summary-address router configuration command to create aggregate addresses for OSPF. The no summary-address command restores the default.
summary-address address mask| address | Summary address designated for a range of addresses. |
| mask | IP subnet mask used for the summary route. |
Disabled
Router configuration
Routes learned from other routing protocols can be summarized. The metric used to advertise the summary is the smallest metric of all the more specific routes. This command helps reduce the size of the routing table.
Using this command for OSPF causes an OSPF autonomous system boundary router (ASBR) to advertise one external route as an aggregate for all redistributed routes that are covered by the address. For OSPF, this command summarizes only routes from other routing protocols that are being redistributed into OSPF. Use the area range command for route summarization between OSPF areas.
In the following configuration, summary address 10.1.0.0 includes address 10.1.1.0, 10.1.2.0, 10.1.3.0, and so forth. Only the address 10.1.0.0 is advertised in an external link state advertisement.
summary-address 10.1.0.0 255.255.0.0
Use the synchronization router configuration command to disable the synchronization between BGP and your IGP. Use the no form of this command to enable an access server to advertise a network route without waiting for the IGP.
synchronizationThis command has no arguments or keywords.
Enabled
Router configuration
Usually, a BGP speaker does not advertise a route to an external neighbor unless that route is local or exists in the IGP. The no synchronization command allows an access server to advertise a network route without waiting for the IGP. This feature allows access servers within an autonomous system to have the route before BGP makes it available to other autonomous systems.
Use synchronization if there are access servers in the autonomous system that do not speak BGP.
The following example enables the access server to advertise a network route without waiting for the IGP:
router bgp 120 no synchronization
Use the table-map router configuration command to modify metric and tag values when the IP routing table is updated with BGP learned routes. Use the no form of this command to disable this function.
table-map route-map-name| route-map-name | Route map name, from the route-map command. |
Disabled
Router configuration
This command adds the route map name defined by the route-map command to the IP routing table. This command is used to set the tag name and the route metric to implement redistribution.
You can use match clauses of route maps in the table-map command. IP access list, autonomous system paths, and next-hop match clauses are supported.
In the following example, the access server is configured to automatically compute the tag value for the BGP learned routes and to update the IP routing table.
route-map tag match as path 10 set automatic-tag ! router bgp 100 table-map tag
match as-path
match ip address
match ip next-hop
route-map
Use the timers basic router configuration command to adjust EGP, RIP, or IGRP network timers. Use the no form of this command to restore the defaults.
timers basic update invalid holddown flush [sleeptime]| update | Rate (in seconds) at which updates are sent. This is the fundamental timing parameter of the routing protocol. |
| invalid | Interval of time (in seconds) after which a route is declared invalid; it should be three times the value of update. A route becomes invalid when there is an absence of updates that refresh the route. The route then enters holddown. The route is marked inaccessible and advertised as unreachable. However, the route is still used for forwarding packets. |
| holddown | Interval (in seconds) during which routing information regarding better paths is suppressed. It should be at least three times the value of update. A route enters into a holddown state when an update packet is received that indicates the route is unreachable. The route is marked inaccessible and advertised as unreachable. However, the route is still used for forwarding packets. When holddown expires, routes advertised by other sources are accepted and the route is no longer inaccessible. |
| flush | Amount of time (in seconds) that must pass before the route is removed from the routing table; the interval specified must be at least the sum of invalid and holddown. If it is less than this sum, the proper holddown interval cannot elapse, which results in a new route being accepted before the holddown interval expires. |
| sleeptime | (Optional) For IGRP only, interval (in milliseconds) for postponing routing updates in the event of a flash update. The sleeptime value should be less than the update time. If the sleeptime is greater than the update time, routing tables will become unsynchronized. |
| Protocol | update | invalid | holddown | flush | sleeptime |
|---|---|---|---|---|---|
| EGP | N/A | 1080 | N/A | 1200 | N/A |
| RIP | 30 | 180 | 180 | 240 | N/A |
| IGRP | 90 | 270 | 280 | 630 | 0 |
Router configuration
The basic timing parameters for IGRP, EGP, and RIP are adjustable. Since these routing protocols are executing a distributed, asynchronous routing algorithm, it is important that these timers be the same for all access servers in the network.
In the following example, updates are broadcast every 5 seconds. If an access server is not heard from in 15 seconds, the route is declared unusable. Further information is suppressed for an additional 15 seconds. At the end of the suppression period, the route is flushed from the routing table.
router igrp 109 timers basic 5 15 15 30
Note that by setting a short update period, you run the risk of congesting slow-speed serial lines; however, this is not a big concern on faster-speed Ethernets and T1-rate serial lines. Also, if you have many routes in your updates, you can cause the access servers to spend an excessive amount of time processing updates.
When the timers basic command is used with EGP, the update time and holddown time are ignored. For example, the commands that follow will set the invalid time for EGP to 100 seconds and the flush time to 200 seconds.
router egp 47 timers basic 0 100 0 200
Use the timers bgp router configuration command to adjust BGP network timers. Use the no form of this command to reset the BGP timing defaults.
timers bgp keepalive holdtime| keepalive | Frequency, in seconds, with which the access server sends keepalive messages to its peer. The default is 60 seconds. |
| holdtime | Interval, in seconds, after not receiving a keepalive message that the access server declares a peer dead. The default is 180 seconds. |
keepalive timer = 60 seconds
holdtime timer = 180 seconds
Router configuration
The following example changes the keepalive timer to 70 seconds and the holdtime timer to 210 seconds:
timers bgp 70 210
clear ip bgp
router bgp
show ip bgp
Use the timers egp router configuration command to adjust EGP Hello and polltime network timers. Use the no form of this command to reset the EGP timing defaults.
timers egp hello polltime| hello | Frequency, in seconds, with which the access server sends Hello messages to its peer. The default is 60 seconds. |
| polltime | Interval, in seconds, for how frequently to exchange updates. The default is 180 seconds. |
Hello timer = 60 seconds
polltime timer = 180 seconds
Router configuration
To change the invalid time or flush time for EGP routes, use the timers basic router configuration command.
The following example changes the EGP timers to 2 minutes and 5 minutes, respectively:
timers egp 120 300
router egp
show ip bgp
timers basic (EGP, RIP, IGRP)
Use the traffic-share router configuration command to control how traffic is distributed among routes when there are multiple routes for the same destination network that have different costs. Use the no form of this command to disable this function.
traffic-share {balanced | min}| balanced | Distributes traffic proportionately to the ratios of the metrics. |
| min | Uses routes that have minimum costs. |
Traffic is distributed proportionately to the ratios of the metrics.
Router configuration
This command applies to IGRP and Enhanced IGRP routing protocols only. With the default setting, routes that have higher metrics represent less-preferable routes and get less traffic. Configuring traffic-share min causes the access server to divide traffic among the routes with the best metric. Other routes will remain in the routing table, but will receive no traffic.
In the following example, only routes of minimum cost will be used:
router igrp 5 traffic-share min
Use the validate-update-source router configuration command to cause the access server to validate the source IP address of incoming routing updates for RIP and IGRP routing protocols. Use the no form of this command to disable this validate function for RIP or IGRP.
validate-update-sourceThis command has no arguments or keywords.
Enabled
Router configuration
This command is only applicable to RIP and IGRP. The access server ensures that the source IP address of incoming routing updates is on the same IP network as one of the addresses defined for the receiving interface.
Disabling split horizon on the incoming interface will also cause the system to perform this validation check.
For unnumbered IP interfaces (interfaces configured as ip unnumbered), no checking is performed.
In the following example, the access server is configured to perform no validation checks on the source IP address of incoming RIP updates:
router rip network 172.25.0.0 no validate-update-source
Use the variance router configuration command to control load balancing in an IGRP-based internet. Use the no form of this command to reset variance to the default value.
variance multiplier| multiplier | Metric value used for load balancing. It can be a value from 1 to 128. The default is 1, which means equal-cost load balancing. |
1 (equal-cost load balancing)
Router configuration
Setting this value lets the access server determine the feasibility of a potential route. A route is feasible if the next access server in the path is closer to the destination than the current access server and if the metric for the entire path is within the variance. Only paths that are feasible can be used for load balancing and included in the routing table.
If the following two conditions are met, the route is deemed feasible and can be added to the routing table:
The following example sets a variance value of 4:
router igrp 109 variance 4
|
|