Table Of Contents
show ip ospf
show ip ospf border-routers
show ip ospf database
show ip ospf flood-list
show ip ospf interface
show ip ospf neighbor
show ip ospf request-list
show ip ospf retransmission-list
show ip ospf sham-links
show ip ospf statistics
show ip ospf summary-address
show ip ospf timers rate-limit
show ip ospf traffic
show ip ospf virtual-links
show ip policy
show ip policy-list
show ip prefix-list
show ip protocols
show ip rip database
show ip route
show ip route profile
show ip route summary
show ip route supernets-only
show ip route track-table
show isis database verbose
show isis database
show isis hostname
show isis rib
show isis rib redistribution
show isis spf-log
show isis topology
show key chain
show route-map
snmp-server enable traps ospf cisco-specific errors config-error
snmp-server enable traps ospf cisco-specific errors shamlink
snmp-server enable traps ospf cisco-specific retransmit
snmp-server enable traps ospf cisco-specific state-change
spf-interval
summary-address (IS-IS)
summary-address (OSPF)
synchronization
show ip ospf
To display general information about Open Shortest Path First (OSPF) routing processes, use the show ip ospf command in EXEC mode.
show ip ospf [process-id]
Syntax Description
process-id
|
(Optional) Process ID. If this argument is included, only information for the specified routing process is included.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2(4)T
|
This command was modified to show packet pacing timers in the displayed output.
|
12.2(15)T
|
This command was modified to show additional information if the OSPF Forwarding Address Suppression in Type-5 LSAs feature is configured.
|
12.0(25)S
12.3(2)T
|
The output of this command was expanded to display link-state advertisement (LSA) throttling timers.
The output of this command was expanded to display LSA throttling timers and the limit on redistributed routes.
|
Examples
The following is sample output from the show ip ospf command when entered without a specific OSPF process ID:
Routing Process "ospf 201" with ID 10.0.0.1 and Domain ID 10.20.0.1
Supports only single TOS(TOS0) routes
SPF schedule delay 5 secs, Hold time between two SPFs 10 secs
Minimum LSA interval 5 secs. Minimum LSA arrival 1 secs
LSA group pacing timer 100 secs
Interface flood pacing timer 55 msecs
Retransmission pacing timer 100 msecs
Number of external LSA 0. Checksum Sum 0x0
Number of opaque AS LSA 0. Checksum Sum 0x0
Number of DCbitless external and opaque AS LSA 0
Number of DoNotAge external and opaque AS LSA 0
Number of areas in this router is 2. 2 normal 0 stub 0 nssa
External flood list length 0
Number of interfaces in this area is 2
Area has message digest authentication
SPF algorithm executed 4 times
Number of LSA 4. Checksum Sum 0x29BEB
Number of opaque link LSA 0. Checksum Sum 0x0
Number of DCbitless LSA 3
Number of indication LSA 0
Number of interfaces in this area is 0
Area has no authentication
SPF algorithm executed 1 times
192.168.0.0/16 Passive Advertise
Number of LSA 1. Checksum Sum 0x44FD
Number of opaque link LSA 0. Checksum Sum 0x0
Number of DCbitless LSA 1
Number of indication LSA 1
Table 57 describes the significant fields shown in the display.
Table 61 show ip ospf Field Descriptions
Field
|
Description
|
Routing process "ospf 201" with ID 10.0.0.1
|
Process ID and OSPF router ID.
|
Supports...
|
Number of types of service supported (Type 0 only).
|
SPF schedule delay
|
Delay time of SPF calculations.
|
Minimum LSA interval
|
Minimum interval between link-state advertisements.
|
LSA group pacing timer
|
Configured LSA group pacing timer (in seconds).
|
Interface flood pacing timer
|
Configured LSA flood pacing timer (in milliseconds).
|
Retransmission pacing timer
|
Configured LSA retransmission pacing timer (in milliseconds).
|
Number of...
|
Number and type of link-state advertisements that have been received.
|
Number of external LSA
|
Number of external link-state advertisements.
|
Number of opaque AS LSA
|
Number of opaque link-state advertisements.
|
Number of DCbitless external and opaque AS LSA
|
Number of demand circuit external and opaque link-state advertisements.
|
Number of DoNotAge external and opaque AS LSA
|
Number of do not age external and opaque link-state advertisements.
|
Number of areas in this router is
|
Number of areas configured for the router.
|
External flood list length
|
External flood list length.
|
The following is an excerpt of output from the show ip ospf command when the OSPF Forwarding Address Suppression in Type-5 LSAs feature is configured:
Number of interfaces in this area is 4
Perform type-7/type-5 LSA translation, suppress forwarding address
Routing Process "ospf 1" with ID 192.168.0.1
Supports only single TOS(TOS0) routes
Supports Link-local Signaling (LLS)
Initial SPF schedule delay 5000 msecs
Minimum hold time between two consecutive SPFs 10000 msecs
Maximum wait time between two consecutive SPFs 10000 msecs
Minimum LSA interval 5 secs
Minimum LSA arrival 1000 msecs
LSA group pacing timer 240 secs
Interface flood pacing timer 33 msecs
Retransmission pacing timer 66 msecs
Number of external LSA 0. Checksum Sum 0x0
Number of opaque AS LSA 0. Checksum Sum 0x0
Number of DCbitless external and opaque AS LSA 0
Number of DoNotAge external and opaque AS LSA 0
Number of areas in this router is 0. 0 normal 0 stub 0 nssa
External flood list length 0
Table 58 describes the significant fields shown in the display.
Table 62 show ip ospf Field Descriptions
Field
|
Description
|
Area
|
OSPF area and tag.
|
Number of interfaces...
|
Number of interfaces configured in the area.
|
It is...
|
Possible types are internal, area border, or autonomous system boundary.
|
Routing process "ospf 1" with ID 192.168.0.1
|
Process ID and OSPF router ID.
|
Supports...
|
Number of types of service supported (Type 0 only).
|
Initial SPF schedule delay
|
Delay time of SPF calculations at startup.
|
Minimum hold time
|
Minimum hold time between consecutive SPF calculations.
|
Maximum wait time
|
Maximum wait time between consecutive SPF calculations.
|
Incremental-SPF
|
Status of incremental SPF calculations.
|
Minimum LSA...
|
Minimum time interval (in seconds) between link-state advertisements, and maximum arrival time (in milliseconds) of link-state advertisements,
|
LSA group pacing timer
|
Configured LSA group pacing timer (in seconds).
|
Interface flood pacing timer
|
Configured LSA flood pacing timer (in milliseconds).
|
Retransmission pacing timer
|
Configured LSA retransmission pacing timer (in milliseconds).
|
Number of...
|
Number and type of link-state advertisements that have been received.
|
Number of external LSA
|
Number of external link-state advertisements.
|
Number of opaque AS LSA
|
Number of opaque link-state advertisements.
|
Number of DCbitless external and opaque AS LSA
|
Number of demand circuit external and opaque link-state advertisements.
|
Number of DoNotAge external and opaque AS LSA
|
Number of do not age external and opaque link-state advertisements.
|
Number of areas in this router is
|
Number of areas configured for the router listed by type.
|
External flood list length
|
External flood list length.
|
The following is sample output from the show ip ospf command. In this example, the user had configured the redistribution maximum-prefix command to set a limit of 2000 redistributed routes. Shortest Path First (SPF) throttling was configured with the timers throttle spf command.
Routing Process "ospf 1" with ID 10.0.0.1
Supports only single TOS(TOS0) routes
Supports Link-local Signaling (LLS)
It is an autonomous system boundary router
Redistributing External Routes from,
static, includes subnets in redistribution
Maximum limit of redistributed prefixes 2000
Threshold for warning message 75%
Initial SPF schedule delay 5000 msecs
Minimum hold time between two consecutive SPFs 10000 msecs
Maximum wait time between two consecutive SPFs 10000 msecs
Table 59 describes the significant fields shown in the display.
Table 63 show ip ospf Field Descriptions
Field
|
Description
|
Routing process "ospf 1" with ID 10.0.0.1
|
Process ID and OSPF router ID.
|
Supports ...
|
Number of Types of Service (TOS) supported.
|
It is ...
|
Possible types are internal, area border, or autonomous system boundary.
|
Redistributing External Routes from
|
Lists of redistributed routes, by protocol.
|
Maximum limit of redistributed prefixes
|
Value set in the redistribution maximum-prefix command to set a limit on the number of redistributed routes.
|
Threshold for warning message
|
Percentage set in the redistribution maximum-prefix command for the threshold number of redistributed routes needed to cause a warning message. The default is 75 percent of the maximum limit.
|
Initial SPF schedule delay
|
Delay (in milliseconds) before initial SPF schedule for SPF throttling. Configured with the timers throttle spf command.
|
Minimum hold time between two consecutive SPFs
|
Minimum hold time (in milliseconds) between two consecutive SPF calculations for SPF throttling. Configured with the timers throttle spf command.
|
Maximum wait time between two consecutive SPFs
|
Maximum wait time (in milliseconds) between two consecutive SPF calculations for SPF throttling. Configured with the timers throttle spf command.
|
Number of areas
|
Number of areas in router, area addresses, and so on.
|
The following is sample output from the show ip ospf command. In this example, the user had configured LSA throttling, and those lines of output are displayed in bold.
Routing Process "ospf 4" with ID 10.10.24.4
Supports only single TOS(TOS0) routes
Supports Link-local Signaling (LLS)
Initial SPF schedule delay 5000 msecs
Minimum hold time between two consecutive SPFs 10000 msecs
Maximum wait time between two consecutive SPFs 10000 msecs
Initial LSA throttle delay 100 msecs
Minimum hold time for LSA throttle 10000 msecs
Maximum wait time for LSA throttle 45000 msecs
Minimum LSA arrival 1000 msecs
LSA group pacing timer 240 secs
Interface flood pacing timer 33 msecs
Retransmission pacing timer 66 msecs
Number of external LSA 0. Checksum Sum 0x0
Number of opaque AS LSA 0. Checksum Sum 0x0
Number of DCbitless external and opaque AS LSA 0
Number of DoNotAge external and opaque AS LSA 0
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
External flood list length 0
Number of interfaces in this area is 2
Area has no authentication
SPF algorithm last executed 04:28:18.396 ago
SPF algorithm executed 8 times
Number of LSA 4. Checksum Sum 0x23EB9
Number of opaque link LSA 0. Checksum Sum 0x0
Number of DCbitless LSA 0
Number of indication LSA 0
The following is sample output from the show ip ospf command. In this example, the user had configured the redistribution maximum-prefix command to set a limit of 2000 redistributed routes. Shortest Path First (SPF) throttling was configured with the timers throttle spf command.
Routing Process "ospf 1" with ID 100.0.0.1
Supports only single TOS(TOS0) routes
Supports Link-local Signaling (LLS)
It is an autonomous system boundary router
Redistributing External Routes from,
static, includes subnets in redistribution
Maximum limit of redistributed prefixes 2000
Threshold for warning message 75%
Initial SPF schedule delay 5000 msecs
Minimum hold time between two consecutive SPFs 10000 msecs
Maximum wait time between two consecutive SPFs 10000 msecs
Table 60 describes significant fields shown in the display.
Table 64 show ip ospf Field Descriptions
Field
|
Description
|
Routing process "ospf 201" with ID 192.42.110.200
|
Process ID and OSPF router ID.
|
Supports ...
|
Number of Types of service supported.
|
It is ...
|
Possible types are internal, area border, or autonomous system boundary.
|
Redistributing External Routes from
|
Lists of redistributed routes, by protocol.
|
Maximum limit of redistributed prefixes
|
Value set in the redistribution maximum-prefix command to set a limit on the number of redistributed routes.
|
Threshold for warning message
|
Percentage set in the redistribution maximum-prefix command for the threshold number of redistributed routes needed to cause a warning message. The default is 75 percent of the maximum limit.
|
Initial SPF schedule delay
|
Delay (in milliseconds) before the initial SPF schedule for SPF throttling. Configured with the timers throttle spf command.
|
Minimum hold time between two consecutive SPFs
|
Minimum hold time (in milliseconds) between two consecutive SPF calculations for SPF throttling. Configured with the timers throttle spf command.
|
Maximum wait time between two consecutive SPFs
|
Maximum wait time (in milliseconds) between two consecutive SPF calculations for SPF throttling. Configured with the timers throttle spf command.
|
Number of areas
|
Number of areas in router, area addresses, and so on.
|
The following is sample output from the show ip ospf command. In this example, the user had configured LSA throttling, and those lines of output are displayed in bold.
Routing Process "ospf 4" with ID 10.10.24.4
Supports only single TOS(TOS0) routes
Supports Link-local Signaling (LLS)
Initial SPF schedule delay 5000 msecs
Minimum hold time between two consecutive SPFs 10000 msecs
Maximum wait time between two consecutive SPFs 10000 msecs
Initial LSA throttle delay 100 msecs
Minimum hold time for LSA throttle 10000 msecs
Maximum wait time for LSA throttle 45000 msecs
Minimum LSA arrival 1000 msecs
LSA group pacing timer 240 secs
Interface flood pacing timer 33 msecs
Retransmission pacing timer 66 msecs
Number of external LSA 0. Checksum Sum 0x0
Number of opaque AS LSA 0. Checksum Sum 0x0
Number of DCbitless external and opaque AS LSA 0
Number of DoNotAge external and opaque AS LSA 0
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
External flood list length 0
Number of interfaces in this area is 2
Area has no authentication
SPF algorithm last executed 04:28:18.396 ago
SPF algorithm executed 8 times
Number of LSA 4. Checksum Sum 0x23EB9
Number of opaque link LSA 0. Checksum Sum 0x0
Number of DCbitless LSA 0
Number of indication LSA 0
show ip ospf border-routers
To display the internal OSPF routing table entries to an Area Border Router (ABR) and Autonomous System Boundary Router (ASBR), use the show ip ospf border-routers command in privileged EXEC mode.
show ip ospf border-routers
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
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
Codes: i - Intra-area route, I - Inter-area route
i 192.168.97.53 [10] via 172.16.1.53, Serial0, ABR, Area 0.0.0.3, SPF 3
i 192.168.103.51 [10] via 192.168.96.51, Serial0, ABR, Area 0.0.0.3, SPF 3
I 192.168.103.52 [22] via 192.168.96.51, Serial0, ASBR, Area 0.0.0.3, SPF 3
I 192.168.103.52 [22] via 172.16.1.53, Serial0, ASBR, Area 0.0.0.3, SPF 3
Table 61 describes the significant fields shown in the display.
Table 65 show ip ospf border-routers Field Descriptions
Field
|
Description
|
192.168.97.53
|
Router ID of the destination.
|
[10]
|
Cost of using this route.
|
via 172.16.1.53
|
Next hop toward the destination.
|
Serial0
|
Interface type for the outgoing interface.
|
ABR
|
The router type of the destination; it is either an ABR or ASBR or both.
|
Area
|
The area ID of the area from which this route is learned.
|
SPF 3
|
The internal number of the shortest path first (SPF) calculation that installs this route.
|
show ip ospf database
Use the show ip ospf database command in EXEC mode to display lists of information related to the OSPF database for a specific router. The various forms of this command deliver information about different OSPF link state advertisements.
show ip ospf [process-id area-id] database
show ip ospf [process-id area-id] database [adv-router [ip-address]]
show ip ospf [process-id area-id] database [asbr-summary] [link-state-id]
show ip ospf [process-id area-id] database [asbr-summary] [link-state-id] [adv-router
[ip-address]]
show ip ospf [process-id area-id] database [asbr-summary] [link-state-id] [self-originate]
[link-state-id]
show ip ospf [process-id area-id] database [database-summary]
show ip ospf [process-id] database [external] [link-state-id]
show ip ospf [process-id] database [external] [link-state-id] [adv-router [ip-address]]
show ip ospf [process-id area-id] database [external] [link-state-id] [self-originate]
[link-state-id]
show ip ospf [process-id area-id] database [network] [link-state-id]
show ip ospf [process-id area-id] database [network] [link-state-id] [adv-router [ip-address]]
show ip ospf [process-id area-id] database [network] [link-state-id] [self-originate]
[link-state-id]
show ip ospf [process-id area-id] database [nssa-external] [link-state-id]
show ip ospf [process-id area-id] database [nssa-external] [link-state-id] [adv-router
[ip-address]]
show ip ospf [process-id area-id] database [nssa-external] [link-state-id] [self-originate]
[link-state-id]
show ip ospf [process-id area-id] database [router] [link-state-id]
show ip ospf [process-id area-id] database [router] [adv-router [ip-address]]
show ip ospf [process-id area-id] database [router] [self-originate] [link-state-id]
show ip ospf [process-id area-id] database [self-originate] [link-state-id]
show ip ospf [process-id area-id] database [summary] [link-state-id]
show ip ospf [process-id area-id] database [summary] [link-state-id] [adv-router [ip-address]]
show ip ospf [process-id area-id] database [summary] [link-state-id] [self-originate]
[link-state-id]
Syntax Description
process-id
|
(Optional) Internal identification. It is locally assigned and can be any positive integer. 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) 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).
|
adv-router [ip-address]
|
(Optional) Displays all the LSAs of the specified router. If no IP address is included, the information is about the local router itself (in this case, the same as self-originate).
|
asbr-summary
|
(Optional) Displays information only about the autonomous system boundary router summary LSAs.
|
database-summary
|
(Optional) Displays how many of each type of LSA for each area there are in the database, and the total.
|
external
|
(Optional) Displays information only about the external LSAs.
|
network
|
(Optional) Displays information only about the network LSAs.
|
nssa-external
|
(Optional) Displays information only about the NSSA external LSAs.
|
router
|
(Optional) Displays information only about the router LSAs.
|
self-originate
|
(Optional) Displays only self-originated LSAs (from the local router).
|
summary
|
(Optional) Displays information only about the summary LSAs.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
11.0
|
The database-summary keyword was added.
|
12.0
|
The following keywords were added:
• self-originate
• adv-router
|
12.0(25)S
|
The output of the show ip ospf database database-summary command was increased to include Self-originated Type-7 and Self-originated Type-5 output.
|
Examples
The following is sample output from the show ip ospf database command when no arguments or keywords are used:
Router# show ip ospf database
OSPF Router with id(192.168.239.66) (Process ID 300)
Displaying Router Link States(Area 0.0.0.0)
Link ID ADV Router Age Seq# Checksum Link count
172.16.21.6 172.16.21.6 1731 0x80002CFB 0x69BC 8
172.16.21.5 172.16.21.5 1112 0x800009D2 0xA2B8 5
172.16.1.2 172.16.1.2 1662 0x80000A98 0x4CB6 9
172.16.1.1 172.16.1.1 1115 0x800009B6 0x5F2C 1
172.16.1.5 172.16.1.5 1691 0x80002BC 0x2A1A 5
172.16.65.6 172.16.65.6 1395 0x80001947 0xEEE1 4
172.16.241.5 172.16.241.5 1161 0x8000007C 0x7C70 1
172.16.27.6 172.16.27.6 1723 0x80000548 0x8641 4
172.16.70.6 172.16.70.6 1485 0x80000B97 0xEB84 6
Displaying Net Link States(Area 0.0.0.0)
Link ID ADV Router Age Seq# Checksum
172.16.1.3 192.168.239.66 1245 0x800000EC 0x82E
Displaying Summary Net Link States(Area 0.0.0.0)
Link ID ADV Router Age Seq# Checksum
172.16.240.0 172.16.241.5 1152 0x80000077 0x7A05
172.16.241.0 172.16.241.5 1152 0x80000070 0xAEB7
172.16.244.0 172.16.241.5 1152 0x80000071 0x95CB
Table 62 describes significant fields shown in the display.
Table 66 show ip ospf Database Field Descriptions
Field
|
Description
|
Link ID
|
Router ID number.
|
ADV Router
|
Advertising router'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 router.
|
The following is sample output from the show ip ospf database command with the asbr-summary keyword:
Router# show ip ospf database asbr-summary
OSPF Router with id(192.168.239.66) (Process ID 300)
Displaying Summary ASB Link States(Area 0.0.0.0)
Options: (No TOS-capability)
LS Type: Summary Links(AS Boundary Router)
Link State ID: 172.16.245.1 (AS Boundary Router address)
Advertising Router: 172.16.241.5
Network Mask: 0.0.0.0 TOS: 0 Metric: 1
Table 63 describes significant fields shown in the display.
Table 67 show ip ospf database asbr-summary Field Descriptions
Field
|
Description
|
OSPF Router with id
|
Router ID number.
|
Process ID
|
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 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 command with the external keyword:
Router# show ip ospf database external
OSPF Router with id(192.168.239.66) (Autonomous system 300)
Displaying AS External Link States
Options: (No TOS-capability)
LS Type: AS External Link
Link State ID: 10.105.0.0 (External Network Number)
Advertising Router: 172.16.70.6
Network Mask: 255.255.0.0
Metric Type: 2 (Larger than any link state path)
Table 64 describes significant fields shown in the display.
Table 68 show ip ospf database external Field Descriptions
Field
|
Description
|
OSPF Router with 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 (external network number).
|
Advertising Router
|
Advertising router's 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 LSA).
|
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 command with the network keyword:
Router# show ip ospf database network
OSPF Router with id(192.168.239.66) (Process ID 300)
Displaying Net Link States(Area 0.0.0.0)
Options: (No TOS-capability)
Link State ID: 172.16.1.3 (address of Designated Router)
Advertising Router: 192.168.239.66
Network Mask: 255.255.255.0
Attached Router: 192.168.239.66
Attached Router: 172.16.241.5
Attached Router: 172.16.1.1
Attached Router: 172.16.54.5
Attached Router: 172.16.1.5
Table 65 describes significant fields shown in the display.
Table 69 show ip ospf database network Field Descriptions
Field
|
Description
|
OSPF Router with id
|
Router ID number.
|
Process ID 300
|
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 of designated router.
|
Advertising Router
|
Advertising router'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.
|
AS Boundary Router
|
Definition of router type.
|
Attached Router
|
List of routers attached to the network, by IP address.
|
The following is sample output from the show ip ospf database command with the router keyword:
Router# show ip ospf database router
OSPF Router with id(192.168.239.66) (Process ID 300)
Displaying Router Link States(Area 0.0.0.0)
Options: (No TOS-capability)
Link State ID: 172.16.21.6
Advertising Router: 172.16.21.6
Link connected to: another Router (point-to-point)
(link ID) Neighboring Router ID: 172.16.21.5
(Link Data) Router Interface address: 172.16.21.6
Table 66 describes significant fields shown in the display.
Table 70 show ip ospf database router Field Descriptions
Field
|
Description
|
OSPF Router with id
|
Router ID number.
|
Process ID
|
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 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 router type.
|
Number of Links
|
Number of active links.
|
link ID
|
Link type.
|
Link Data
|
Router interface address.
|
TOS
|
Type of service metric (Type 0 only).
|
The following is sample output from show ip ospf database command with the summary keyword:
Router# show ip ospf database summary
OSPF Router with id(192.168.239.66) (Process ID 300)
Displaying Summary Net Link States(Area 0.0.0.0)
Options: (No TOS-capability)
LS Type: Summary Links(Network)
Link State ID: 172.16.240.0 (summary Network Number)
Advertising Router: 172.16.241.5
Network Mask: 255.255.255.0 TOS: 0 Metric: 1
Table 67 describes significant fields shown in the display.
Table 71 show ip ospf database summary Field Descriptions
Field
|
Description
|
OSPF Router with id
|
Router ID number.
|
Process ID
|
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 router'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 show ip ospf database command with the database-summary keyword:
Router# show ip ospf database database-summary
OSPF Router with ID (100.0.0.1) (Process ID 1)
LSA Type Count Delete Maxage
Process 1 database summary
LSA Type Count Delete Maxage
Self-originated Type-5 200
Table 68 describes significant fields shown in the display.
Table 72 show ip ospf database database-summary Field Descriptions
Field
|
Description
|
Area 0 database summary
|
Area number.
|
Count
|
Count of LSAs of the type identified in the first column.
|
Router
|
Number of router link state advertisements in that area.
|
Network
|
Number of network link state advertisements in that area.
|
Summary Net
|
Number of summary link state advertisements in that area.
|
Summary ASBR
|
Number of summary autonomous system boundary router (ASBR) link state advertisements in that area.
|
Type-7 Ext
|
Type-7 LSA count.
|
Self-originated Type-7
|
Self-originated Type-7 LSA.
|
Opaque Link
|
Type-9 LSA count.
|
Opaque Area
|
Type-10 LSA count
|
Subtotal
|
Sum of LSAs 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.
|
Process 1 database summary
|
Database summary for the process.
|
Count
|
Count of LSAs of the type identified in the first column.
|
Router
|
Number of router link state advertisements in that process.
|
Network
|
Number of network link state advertisements in that process.
|
Summary Net
|
Number of summary link state advertisements in that process.
|
Summary ASBR
|
Number of summary autonomous system boundary router (ASBR) link state advertisements in that process.
|
Type-7 Ext
|
Type-7 LSA count.
|
Opaque Link
|
Type-9 LSA count.
|
Opaque Area
|
Type-10 LSA count.
|
Type-5 Ext
|
Type-5 LSA count.
|
Self-Originated Type-5
|
Self-originated Type-5 LSA count.
|
Opaque AS
|
Type-11 LSA count.
|
Total
|
Sum of LSAs for that process.
|
Delete
|
Number of link state advertisements that are marked "Deleted" in that process.
|
Maxage
|
Number of link state advertisements that are marked "Maxaged" in that process.
|
show ip ospf flood-list
To display a list of OSPF link-state advertisements (LSAs) waiting to be flooded over an interface, use the show ip ospf flood-list command in EXEC mode.
show ip ospf flood-list interface-type interface-number
Syntax Description
interface-type
|
Interface type over which the LSAs will be flooded.
|
interface-number
|
Interface number over which the LSAs will be flooded.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(1)T
|
This command was introduced.
|
Usage Guidelines
Use this command to observe OSPF packet pacing.
Examples
The following is sample output of the show ip ospf flood-list command:
Router# show ip ospf flood-list ethernet 1
Interface Ethernet1, Queue length 20
Link state flooding due in 12 msec
Type LS ID ADV RTR Seq NO Age Checksum
5 10.2.195.0 192.168.0.163 0x80000009 0 0xFB61
5 10.1.192.0 192.168.0.163 0x80000009 0 0x2938
5 10.2.194.0 192.168.0.163 0x80000009 0 0x757
5 10.1.193.0 192.168.0.163 0x80000009 0 0x1E42
5 10.2.193.0 192.168.0.163 0x80000009 0 0x124D
5 10.1.194.0 192.168.0.163 0x80000009 0 0x134C
Table 69 describes the significant fields shown in the display.
Table 73 show ip ospf flood-list Field Descriptions
Field
|
Description
|
Interface Ethernet1
|
Interface for which information is displayed.
|
Queue length
|
Number of LSAs waiting to be flooded.
|
Link state flooding due in
|
Length of time before next link-state transmission.
|
Type
|
Type of LSA.
|
LS ID
|
Link-state ID of the LSA.
|
ADV RTR
|
IP address of advertising router.
|
Seq NO
|
Sequence number of LSA.
|
Age
|
Age of LSA (in seconds).
|
Checksum
|
Checksum of LSA.
|
show ip ospf interface
To display OSPF-related interface information, use the show ip ospf interface command in EXEC mode.
show ip ospf interface [interface-type interface-number] [brief]
Syntax Description
interface-type
|
(Optional) Interface type. If the interface-type argument is included, only information for the specified interface type is included.
|
interface-number
|
(Optional) Interface number. If the interface-number argument is included, only information for the specified interface number is included.
|
brief
|
(Optional) Displays brief overview information for OSPF interfaces, states, addresses and masks, and areas on the router.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.0(25)S
|
The brief keyword was added.
|
12.2(15)S
|
The brief keyword was added.
|
12.2(15)T
|
The brief keyword was added.
|
Examples
The following is sample output of the show ip ospf interface command when Ethernet interface 0 is specified:
Router# show ip ospf interface ethernet 0
Ethernet 0 is up, line protocol is up
Internet Address 192.168.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 192.168.254.10, Interface address 192.168.254.10
Backup Designated router id 192.168.254.28, Interface addr 192.168.254.28
Timer intervals configured, Hello 10, Dead 60, Wait 40, Retransmit 5
Neighbor Count is 8, Adjacent neighbor count is 2
Adjacent with neighbor 192.168.254.28 (Backup Designated Router)
Adjacent with neighbor 192.168.254.10 (Designated Router)
Table 70 describes the significant fields shown in the display.
Table 74 show ip ospf interface Field Descriptions
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), router ID, network type, link-state cost.
|
Transmit Delay
|
Transmit delay, interface state, and router priority.
|
Designated Router
|
Designated router ID and respective interface IP address.
|
Backup Designated router
|
Backup designated router 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.
|
show ip ospf neighbor
To display OSPF-neighbor information on a per-interface basis, use the show ip ospf neighbor command in EXEC mode.
show ip ospf neighbor [interface-type interface-number] [neighbor-id] [detail]
Syntax Description
interface-type
|
(Optional) Interface type.
|
interface-number
|
(Optional) Interface number.
|
neighbor-id
|
(Optional) Neighbor ID.
|
detail
|
(Optional) Displays all neighbors given in detail (lists all neighbors).
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
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
10.199.199.137 1 FULL/DR 0:00:31 192.168.80.37 Ethernet0
172.16.48.1 1 FULL/DROTHER 0:00:33 172.16.48.1 Fddi0
172.16.48.200 1 FULL/DROTHER 0:00:33 172.16.48.200 Fddi0
10.199.199.137 5 FULL/DR 0:00:33 172.16.48.189 Fddi0
The following is sample output showing summary information about the neighbor that matches the neighbor ID:
Router# show ip ospf neighbor 10.199.199.137
Neighbor 10.199.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
Dead timer due in 0:00:32
Link State retransmission due in 0:00:04
Neighbor 10.199.199.137, interface address 172.16.48.189
In the area 0.0.0.0 via interface Fddi0
Neighbor priority is 5, State is FULL
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 system displays the neighbors that match the neighbor ID on the interface, as in the following sample display:
Router# show ip ospf neighbor ethernet 0 10.199.199.137
Neighbor 10.199.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
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
172.16.48.1 1 FULL/DROTHER 0:00:33 172.16.48.1 Fddi0
172.16.48.200 1 FULL/DROTHER 0:00:32 172.16.48.200 Fddi0
10.199.199.137 5 FULL/DR 0:00:32 172.16.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.5.2, interface address 10.225.200.28
In the area 0 via interface GigabitEthernet1/0/0
Neighbor priority is 1, State is FULL, 6 state changes
DR is 10.225.200.28 BDR is 10.225.200.30
LLS Options is 0x1 (LR), last OOB-Resync 00:03:08 ago
Dead timer due in 00:00:36
Neighbor is up for 00:09:46
Index 1/1, retransmission queue length 0, number of retransmission 1
First 0x0(0)/0x0(0) Next 0x0(0)/0x0(0)
Last retransmission scan length is 1, maximum is 1
Last retransmission scan time is 0 msec, maximum is 0 msec
Table 71 describes the significant fields shown in the displays.
Table 75 show ip ospf neighbor detail Field Descriptions
Field
|
Description
|
Neighbor
|
Neighbor router ID.
|
interface address
|
IP address of the interface.
|
In the area
|
Area and interface through which the OSPF neighbor is known.
|
Neighbor priority
|
Router priority of the neighbor, neighbor state.
|
State
|
OSPF state.
|
state changes
|
Number of state changes since the neighbor was created.This value can be reset using the clear ip ospf counters neighbor command.
|
DR is
|
Router ID of the designated router for the interface.
|
BDR is
|
Router ID of the backup designated router for the interface.
|
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.)
|
LLS Options..., last OOB-Resync
|
Link-Local Signalling and out-of-band (OOB) link-state database resynchronization performed hours:minutes:seconds ago (NSF information). The field indicates the last successful out-of-band resynchronization with the NSF-capable router.
|
Dead timer due in
|
Expected time before Cisco IOS software will declare the neighbor dead.
|
Neighbor is up for
|
Number of hours:minutes:seconds since the neighbor went into two-way state.
|
Index
|
Neighbor location in the area-wide and autonomous system-wide retransmission queue.
|
retransmission queue length
|
Number of elements in the retransmission queue.
|
number of retransmission
|
Number of times update packets have been re-sent during flooding.
|
First
|
Memory location of the flooding details.
|
Next
|
Memory location of the flooding details.
|
Last retransmission scan length
|
Number of link state advertisements (LSAs) in the last retransmission packet.
|
maximum
|
Maximum number of LSAs sent in any retransmission packet.
|
Last retransmission scan time
|
Time taken to build last retransmission packet.
|
maximum
|
Maximum time taken to build any retransmission packet.
|
show ip ospf request-list
To display a list of all link-state advertisements (LSAs) requested by a router, use the show ip ospf request-list command in EXEC mode.
show ip ospf request-list [neighbor] [interface] [interface-neighbor]
Syntax Description
neighbor
|
(Optional) Displays the list of all LSAs requested by the router from this neighbor.
|
interface
|
(Optional) Displays the list of all LSAs requested by the router from this interface.
|
interface-neighbor
|
(Optional) Displays the list of all LSAs requested by the router on this interface from this neighbor.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.2
|
This command was introduced.
|
Usage Guidelines
The information displayed by the show ip ospf request-list command is useful in debugging OSPF routing operations.
Examples
The following is sample output from the show ip ospf request-list command:
Router# show ip ospf request-list serial 0
OSPF Router with ID (192.168.1.11) (Process ID 1)
Neighbor 192.168.1.12, interface Serial0 address 172.16.1.12
Type LS ID ADV RTR Seq NO Age Checksum
1 192.168.1.12 192.168.1.12 0x8000020D 8 0x6572
show ip ospf retransmission-list
To display a list of all link-state advertisements (LSAs) waiting to be re-sent, use the show ip ospf retransmission-list command in EXEC mode.
show ip ospf retransmission-list [neighbor] [interface] [interface-neighbor]
Syntax Description
neighbor
|
(Optional) Displays the list of all LSAs waiting to be re-sent for this neighbor.
|
interface
|
(Optional) Displays the list of all LSAs waiting to be re-sent on this interface.
|
interface-neighbor
|
(Optional) Displays the list of all LSAs waiting to be re-sent on this interface, from this neighbor.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.2
|
This command was introduced.
|
Usage Guidelines
The information displayed by the show ip ospf retransmission-list command is useful in debugging OSPF routing operations.
Examples
The following is sample output from the show ip ospf retransmission-list command:
Router# show ip ospf retransmission-list serial 0
OSPF Router with ID (192.168.1.12) (Process ID 1)
Neighbor 192.168.1.11, interface Serial0 address 172.16.1.11
Link state retransmission due in 3764 msec, Queue length 2
Type LS ID ADV RTR Seq NO Age Checksum
1 192.168.1.12 192.168.1.12 0x80000210 0 0xB196
show ip ospf sham-links
To display information about all sham-links configured for a provider edge (PE) router in the Virtual Private Network (VPN) backbone, use the show ip ospf sham-links command in EXEC mode.
show ip ospf sham-links
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.2(8)T
|
This command was introduced.
|
Usage Guidelines
Use this command to display Open Shortest Path First (OSPF) information about the sham-links configured on a PE router.
Examples
The following example shows sample output from the show ip ospf sham-links command for a PE router in the VPN backbone:
Router1# show ip ospf sham-links
Sham Link OSPF_SL0 to address 10.44.0.1 is up
Area 120 source address 10.0.0.1
DoNotAge LSA allowed., Cost of using 1
Transmit Delay is 1 sec, State POINT_TO_POINT,
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Adjacency State FULL (Hello suppressed)
Index 2/2, retransmission queue length 0, number of retransmission 27
First 0x0(0)/0x0(0) Next 0x0(0)/0x0(0)
Last retransmission scan length is 0, maximum is 2
Last retransmission scan time is 0 msec, maximum is 0 msec
show ip ospf statistics
To display Open Shortest Path First (OSPF) shortest path first (SPF) calculation statistics, use the show ip ospf statistics command in user EXEC or privileged EXEC mode.
show ip ospf statistics [detail]
Syntax Description
detail
|
(Optional) Displays statistics separately for each OSPF area and includes additional, more detailed statistics.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0(24)S
|
This command was introduced.
|
12.2(18)S
|
The command was integrated into Cisco IOS Release 12.2(18)S.
|
12.3(2)T
|
The command was integrated into Cisco IOS Release 12.3(2)T.
|
Usage Guidelines
The show ip ospf statistics command provides important information about SPF calculations and the events that trigger them. This information can be meaningful for both OSPF network maintenance and troubleshooting. For example, entering the show ip ospf statistics command is recommended as the first troubleshooting step for link-state advertisement (LSA) flapping.
Examples
The following is sample output from the show ip ospf statistics command that shows a single line of information for each SPF calculation:
Router# show ip ospf statistics
------------------------------------------
Area 0: SPF algorithm executed 10 times
Area 200: SPF algorithm executed 8 times
Summary OSPF SPF statistic
Delta T Intra D-Intra Summ D-Summ Ext D-Ext Total Reason
08:17:16 0 0 0 0 0 0 0 R,
08:16:47 0 0 0 0 0 0 0 R, N,
08:16:37 0 0 0 0 0 0 0 R, X
00:04:40 208 40 208 44 220 0 720 R, N, SN, X
00:03:15 0 112 4 108 8 96 328 R, N, SN, X
00:02:55 164 40 176 44 188 0 612 R, N, SN, X
00:01:49 0 4 4 0 4 4 16 R, N, SN, X
00:01:48 0 0 4 0 4 0 12 R, N, SN, SA, X
00:01:43 0 0 4 0 4 0 8 R,
00:00:53 164 40 176 44 188 0 612 R, N, SN, X
Table 70 describes the significant fields shown in the display.
Table 76 show ip ospf statistics Field Descriptions
Field
|
Description
|
OSPF process ID
|
A unique value assigned to the OSPF process in the configuration.
|
Area
|
OSPF area ID.
|
SPF algorithm executed
|
Number of times SPF algorithm has been executed for the particular area.
|
Delta T
|
Amount of time in milliseconds that has passed from when SPF started its calculation to the current time.
|
Intra
|
Time in milliseconds for the SPF algorithm to process intra-area LSAs and install intra-area routes in the routing table.
|
D-Intra
|
Time in milliseconds for the SPF algorithm to delete invalid intra-area routes from the routing table.
|
Summ
|
Time in milliseconds for the SPF algorithm to process interarea LSAs and install interarea routes in the routing table.
|
D-Summ
|
Time in milliseconds for the SPF algorithm to delete invalid interarea routes from the routing table.
|
Ext
|
Time in milliseconds for the SPF algorithm to process external and not so stubby area (NSSA) LSAs and install external and NSSA routes in the routing table.
|
D-Ext
|
Time in milliseconds for the SPF algorithm to delete invalid external and NSSA routes from the routing table.
|
Total
|
Total duration time, in milliseconds, for the SPF algorithm process.
|
Reason
|
Record of reasons causing SPF to be executed:
• N—A change in a network LSA (type 2) has occurred.
• R—A change in a router LSA (type 1) has occurred.
• SA—A change in a Summary autonomous system boundary router (ASBR) (SA) LSA has occurred.
• SN—A change in a Summary Network (SN) LSA has occurred.
• X—A change in an External Type-7 (X7) LSA has occurred.
|
The following is sample output from the show ip ospf statistics command with the detail keyword entered to show the statistics separately for a specific area:
Router# show ip ospf statistics detail
SPF 7 executed 2d17h ago, SPF type Full
SPF calculation time (in msec):
SPT Intra D-Intr Summ D-Summ Ext7 D-Ext7 Total
LSIDs processed R:4 N:1 Stub:5 SN:17 SA:1 X7:0
Table 70 describes the significant fields shown in the display.
Table 77 show ip ospf statistics detail Field Descriptions
Field
|
Description
|
SPF
|
Number of SPF algorithms executed in the OSPF area. The number increases by one for each SPF algorithm that is executed in the area.
|
Executed ago
|
Time in milliseconds that has passed between the start of the SPF algorithm execution and the current time.
|
SPF type
|
SPF type can be Full or Incremental.
|
SPT
|
Time in milliseconds requires to compute the first stage of the SPF algorithm (to build a short path tree). The SPT time plus the time required to process links to stub networks equals the Intra time.
|
Ext
|
Time in milliseconds for the SPF algorithm to process external and not so stubby area (NSSA) link-state advertisements (LSAs) and install external and NSSA routes in the routing table.
|
Total
|
Total duration time, in milliseconds, for the SPF algorithm process.
Note Total time is the sum of previous times excluding the SPT time, which is already included in the Intra time.
|
LSIDs processed
|
Number of LSAs processed during the SPF calculation:
• N—Network LSA.
• R—Router LSA.
• SA—Summary autonomous system boundary router (ASBR) (SA) LSA.
• SN—Summary Network (SN) LSA.
• Stub—Stub links.
• X7—External Type-7 (X7) LSA.
|
LSIDs changed
|
Number of LSAs changed between this SPF calculation and the previous one. LSA changes force SPF to be scheduled.
|
Last 10 LSIDs
|
List of last ten Intra area LSAs that have changed between this SPF calculation and the previous one. LSID types:
• R—Router LSA (type 1)
• N—Network LSA (type 2)
|
show ip ospf summary-address
To display a list of all summary address redistribution information configured under an OSPF process, use the show ip ospf summary-address command in EXEC mode.
show ip ospf [process-id] summary-address
Syntax Description
process-id
|
(Optional) OSPF area ID.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
The process-id argument can be entered as a decimal number or as an IP address format.
Examples
The following is sample output from the show ip ospf summary-address command:
Router# show ip ospf summary-address
OSPF Process 2, Summary-address
10.2.0.0/255.255.0.0 Metric -1, Type 0, Tag 0
10.2.0.0/255.255.0.0 Metric -1, Type 0, Tag 10
show ip ospf timers rate-limit
To display all of the link-state advertisements (LSAs) in the rate limit queue, use the show ip ospf timers rate-limit command in privileged EXEC mode.
show ip ospf timers rate-limit
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(25)S
|
This command was introduced.
|
Usage Guidelines
Use this command if you need to see when LSAs in the queue will be sent.
Examples
The following is sample output from the show ip ospf timers rate-limit command:
Router# show ip ospf timers rate-limit
LSAID: 10.1.1.1 Type: 1 Adv Rtr: 172.16.2.2 Due in: 00:00:00.028
LSAID: 172.16.4.1 Type: 3 Adv Rtr: 172.16.2.2 Due in: 00:00:00.028
Table 72 describes the significant fields shown in the display.
Table 78 show ip ospf timers rate-limit Field Descriptions
Field
|
Description
|
LSAID
|
ID of the LSA.
|
Type
|
Type of LSA.
|
Adv Rtr
|
ID of advertising router.
|
Due in
|
When the LSA is scheduled to be sent (in hours:minutes:seconds).
|
show ip ospf traffic
To display Open Shortest Path First (OSPF) traffic statistics, use the show ip ospf traffic command in user EXEC or privileged EXEC mode.
show ip ospf [process-id] traffic [interface-type interface-number]
Syntax Description
process-id
|
(Optional) Process ID. If the process-id argument is included, only information for the specified routing process is included.
|
interface-type
|
(Optional) Interface type.
|
interface-number
|
(Optional) interface number.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(11)T
|
This command was introduced.
|
12.0(28)S
|
This command was integrated in Cisco IOS Release 12.0(28)S.
|
Examples
The following is sample output from the show ip ospf traffic command:
Router# show ip ospf traffic
Rcvd: 5300 total, 730 checksum errors
333 hello, 10 database desc, 3 link state req
24 link state updates, 13 link state acks
222 hello, 12 database desc, 3 link state req
17 link state updates, 12 link state acks
OSPF Router with ID (2.0.0.202) (Process ID 100)
OSPF queues statistic for process ID 100:
OSPF Hello queue size 0, no limit, max size 3
OSPF Router queue size 0, limit 200, drops 0, max size 3
OSPF packets received/sent
Invalid Hellos DB-des LS-req LS-upd LS-ack Total
Length 0, Checksum 0, Version 0, Bad Source 0,
No Virtual Link 0, Area Mismatch 0, No Sham Link 0,
Self Originated 0, Duplicate ID 0, LLS 0,
Type 0, Length 0, Data 0, Checksum 0,
OSPF packets received/sent
Invalid Hellos DB-des LS-req LS-upd LS-ack Total
Length 0, Checksum 0, Version 0, Bad Source 0,
No Virtual Link 0, Area Mismatch 0, No Sham Link 0,
Self Originated 0, Duplicate ID 0, LLS 0,
Type 0, Length 0, Data 0, Checksum 0,
OSPF packets received/sent
Invalid Hellos DB-des LS-req LS-upd LS-ack Total
Length 0, Checksum 0, Version 0, Bad Source 0,
No Virtual Link 0, Area Mismatch 0, No Sham Link 0,
Self Originated 0, Duplicate ID 0, LLS 0,
Type 0, Length 0, Data 0, Checksum 0,
OSPF packets received/sent
Invalid Hellos DB-des LS-req LS-upd LS-ack Total
Length 0, Checksum 730, Version 800, Bad Source 0,
No Virtual Link 0, Area Mismatch 0, No Sham Link 0,
Self Originated 3387, Duplicate ID 0, LLS 0,
Type 0, Length 0, Data 0, Checksum 0,
Summary traffic statistics for process ID 100:
Rcvd: 5300 total, 4917 errors
333 hello, 10 database desc, 3 link state req
24 link state upds, 13 link state acks, 0 invalid
222 hello, 12 database desc, 3 link state req
17 link state upds, 12 link state acks, 0 invalid
Table 79 describes the significant fields shown in the display.
Table 79 show ospf traffic Field Descriptions
Field
|
Description
|
OSPF statistics
|
Traffic statistics accumulated for all OSPF processes running on the router. To ensure compatibility with the show ip traffic command, only checksum errors are displayed. Name of the route map.
|
OSPF queues statistic for process ID
|
Cisco IOS-specific queue statistics.
|
OSPF Hello queue
|
Queue statistics for the internal Cisco IOS queue between the packet switching code (process IP Input) and the OSPF hello process for all received OSPF packets.
|
OSPF Router queue
|
Queue statistics for the internal Cisco IOS queue between the OSPF hello process and the OSPF router for all received OSPF packets except OSPF hellos.
|
queue size
|
Actual size of the queue.
|
queue limit
|
Maximum allowed size of queue.
|
queue max size
|
Maximum recorded size of the queue.
|
Interface statistics
|
Per-interface traffic statistics for all interfaces that belong to the specific OSPF process ID.
|
OSPF packets received or set
|
Number of OSPF packets received and sent on the interface, sorted by packet types.
|
OSPF header errors
|
Packet appears in this section if it was discarded because of an error in the header of an OSPF packet. The discarded packet is counted under the appropriate discard reason.
|
OSPF LSA errors
|
Packet appears in this section if it was discarded because of an error in the header of an OSPF link-state advertisement (LSA). The discarded packet is counted under the appropriate discard reason.
|
Summary traffic statistics for process ID
|
Summary traffic statistics accumulated for an OSPF process.
Note The OSPF process ID is a unique value assigned to the OSPF process in the configuration.
The value for the Received errors is the sum of the OSPF header errors that are detected by the OSPF process, unlike the sum of the checksum errors that are listed in the global OSPF statistics.
|
Related Commands
Command
|
Description
|
clear ip ospf traffic
|
Clears OSPF traffic statistics.
|
show ip ospf virtual-links
To display parameters and the current state of OSPF virtual links, use the show ip ospf virtual-links command in EXEC mode.
show ip ospf virtual-links
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
The information displayed by the show ip ospf virtual-links command is useful in debugging OSPF routing operations.
Examples
The following is sample output from the show ip ospf virtual-links command:
Router# show ip ospf virtual-links
Virtual Link to router 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
Table 73 describes the significant fields shown in the display.
Table 80 show ip ospf virtual-links Field Descriptions
Field
|
Description
|
Virtual Link to router 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 (in seconds) 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.
|
show ip policy
To display the route map used for policy routing, use the show ip policy command in user EXEC or privileged EXEC mode.
show ip policy
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
12.3(7)T
|
The display output was modified to include a label for dynamic route maps.
|
Examples
The following is sample output from the show ip policy command:
Ethernet0/3 AAA-02/06/04-14:01:26.619-1-AppSpec (Dynamic)
The following is sample output from the show route-map command, which relates to the preceding sample display:
route-map equal, permit, sequence 10
Policy routing matches: 0 packets, 0 bytes
route-map equal, permit, sequence 20
ip address (access-lists): 101
Policy routing matches: 144 packets, 15190 bytes
Table 81 describes the significant fields shown in the display.
Table 81 show ip policy Field Descriptions
Field
|
Description
|
route-map equal
|
The name of the route map is equal.
|
permit
|
The route map contains permit statements.
|
sequence
|
Sequence number of the route map, which determines in what order it is processed among other route maps.
|
Match clauses
|
Clauses in the route map that must be matched to satisfy the permit or deny action.
|
Set clauses
|
Set clauses that will be put into place if the match clauses are met.
|
Policy routing matches packets
|
Number of packets that meet the match clauses.
|
bytes
|
Number of bytes in the packets that meet the match clauses.
|
Related Commands
Command
|
Description
|
match ip address
|
Distributes any routes that have a destination network number address that is permitted by a standard or extended access list, and performs policy routing on packets.
|
match length
|
Bases policy routing on the Level 3 length of a packet.
|
route-map (IP)
|
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing.
|
set default interface
|
Indicates where to output packets that pass a match clause of a route map for policy routing and have no explicit route to the destination.
|
set interface
|
Indicates where to output packets that pass a match clause of route map for policy routing.
|
set ip default next-hop verify-availability
|
Indicates where to output packets that pass a match clause of a route map for policy routing and for which the Cisco IOS software has no explicit route to a destination.
|
set ip next-hop
|
Indicates where to output packets that pass a match clause of a route map for policy routing.
|
show ip policy-list
To display information about a configured policy list and policy list entries, use the show ip policy-list command in user EXEC mode.
show ip policy-list policy-list-name
Syntax Description
policy-list-name
|
Displays information about the specified policy list with this argument.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(22)S
|
This command was introduced.
|
12.2(15)T
|
This command was integrated into 12.2(15)T.
|
Examples
The following is sample output from the show ip policy-list command. The output of this command will display the policy-list name and configured match clauses. The following sample output is similar to the output that will be displayed:
Router> show ip policy-list
policy-list POLICY-LIST-NAME-1 permit
policy-list POLICY-LIST-NAME-2 permit
as-path (as-path filter): 1
Related Commands
Command
|
Description
|
show route-map
|
Displays configured route maps and information about referenced policy maps.
|
show ip prefix-list
To display information about a prefix list or prefix list entries, use the show ip prefix-list command user and privileged EXEC mode.
show ip prefix-list [detail | summary] prefix-list-name [network/length] [seq sequence-number]
[longer] [first-match]
Syntax Description
detail | summary
|
(Optional) Displays detailed or summarized information about all prefix lists.
|
prefix-list-name
|
(Optional) The name of a specific prefix list.
|
network/length
|
(Optional) The network number and length (in bits) of the network mask.
|
seq
|
(Optional) Applies the sequence number to the prefix list entry.
|
sequence-number
|
(Optional) The sequence number of the prefix list entry.
|
longer
|
(Optional) Displays all entries of a prefix list that are more specific than the given network/length.
|
first-match
|
(Optional)Displays the entry of a prefix list that matches the given network/length.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0
|
This command was introduced.
|
Examples
The following example shows the output of the show ip prefix-list command with details about the prefix list named test in privileged EXEC mode:
Router# show ip prefix-list detail test
Description: test-list
count: 1, range entries: 0, sequences: 10 - 10, refcount: 3
seq 10 permit 35.0.0.0/8 (hit count: 0, refcount: 1)
Related Commands
Command
|
Description
|
clear ip prefix-list
|
Resets the hit count of the prefix list entries.
|
distribute-list in (BGP)
|
Filters networks received in updates.
|
distribute-list out (BGP)
|
Suppresses networks from being advertised in updates.
|
ip prefix-list
|
Creates an entry in a prefix list.
|
ip prefix-list description
|
Adds a text description of a prefix list.
|
Command
|
Description
|
match ip address
|
Distributes any routes that have a destination network number address that is permitted by a standard or extended access list, and performs policy routing on packets.
|
neighbor prefix-list
|
Distributes BGP neighbor information as specified in a prefix list.
|
show ip protocols
To display the parameters and current state of the active routing protocol process, use the show ip protocols command in EXEC mode.
show ip protocols
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2(15)T
|
Support for the route-hold timer was integrated into the output.
|
Usage Guidelines
The information displayed by the show ip protocols command is useful in debugging routing operations. Information in the Routing Information Sources field of the show ip protocols output can help you identify a router suspected of delivering bad routing information.
Examples
EIGRP Example
The following is sample output from the show ip protocols command that shows Enhanced Interior Gateway Routing Protocol (EIGRP) process 77:
Router# show ip protocols
Routing Protocol is "eigrp 77"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Automatic network summarization is in effect
Routing Information Sources:
Gateway Distance Last Update
Distance: internal 90 external 170
Table 75 describes the significant fields shown in the display.
Table 82 show ip protocols Field Descriptions for EIGRP Process 77
Field
|
Description
|
Routing Protocol is "eigrp 77"
|
Name and autonomous system number of the currently running routing protocol.
|
Outgoing update filter list for all interfaces...
|
Indicates whether a filter for outgoing routing updates has been specified with the distribute-list out command.
|
Incoming update filter list for all interfaces...
|
Indicates whether a filter for incoming routing updates has been specified with the distribute-list in command.
|
Redistributing: eigrp 77
|
Indicates whether route redistribution has been enabled with the redistribute command.
|
Automatic network summarization...
|
Indicates whether route summarization has been enabled with the auto-summary command.
|
Routing for Networks:
|
Networks for which the routing process is currently injecting routes.
|
Routing Information Sources:
|
Lists all the routing sources that the Cisco IOS software is using to build its routing table. The following is displayed for each source:
• IP address
• Administrative distance
• Time the last update was received from this source
|
Distance: internal 90 external 170
|
Internal and external distances of the router. Internal distance is the degree of preference given to EIGRP internal routes. External distance is the degree of preference given to EIGRP external routes.
|
IS-IS Example
The following is sample output from the show ip protocols command that shows Intermediate System-to-Intermediate System (IS-IS) processes:
Router# show ip protocols
Routing Protocol is "isis"
Sending updates every 0 seconds
Invalid after 0 seconds, hold down 0, flushed after 0
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Routing Information Sources:
Distance: (default is 115)
Table 76 describes the significant fields shown in the display.
Table 83 show ip protocols Field Descriptions for an IS-IS Process
Field
|
Description
|
Routing Protocol is "isis"
|
Specifies the routing protocol used.
|
Sending updates every 0 seconds
|
Specifies the time between sending updates.
|
Invalid after 0 seconds
|
Specifies the value of the invalid parameter.
|
hold down 0
|
Specifies the current value of the hold-down parameter.
|
flushed after 0
|
Specifies the time (in seconds) after which the individual routing information will be thrown out (flushed).
|
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.
|
Redistributing
|
Lists the protocol that is being redistributed.
|
Routing
|
Specifies the networks for which the routing process is currently injecting routes.
|
Routing Information Sources
|
Lists all the routing sources the Cisco IOS software is using to build its routing table. For each source, you will see the following displayed:
• IP address
• Administrative distance
• Time the last update was received from this source
|
RIP Example
The following is sample output from the show ip protocols command that shows Routing Information Protocol (RIP) processes:
Router# show ip protocols
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 2 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Default version control: send version 2, receive version 2
Interface Send Recv Key-chain
Routing Information Sources:
Gateway Distance Last Update
Distance: (default is 120)
Table 77 describes the significant fields shown in the display.
Table 84 show ip protocols Field Descriptions for a RIP Process
Field
|
Description
|
Routing Protocol is "rip"
|
Specifies the routing protocol used.
|
Sending updates every 30 seconds
|
Specifies the time between sending updates.
|
next due in 2 seconds
|
Precisely when the next update is due to be sent.
|
Invalid after 180 seconds
|
Specifies the value of the invalid parameter.
|
hold down for 180
|
Specifies the current value of the hold-down parameter.
|
flushed after 240
|
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 version control:
|
Specifies the version of RIP packets that are sent and received.
|
Redistributing
|
Lists the protocol that is being redistributed.
|
Routing
|
Specifies the networks for which the routing process is currently injecting routes.
|
Routing Information Sources
|
Lists all the routing sources the Cisco IOS software is using to build its routing table. For each source, you will see the following displayed:
• IP address
• Administrative distance
• Time the last update was received from this source
|
EIGRP NSF Awareness Verification Example
The following is sample output from the show ip protocols command. The output shows that the router is running EIGRP, is NSF-aware, and that the route-hold timer is set 240 seconds, which is the default value for the route-hold timer.
Router# show ip protocols
Routing Protocol is "eigrp 101"
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
EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
EIGRP maximum hopcount 100
EIGRP maximum metric variance 1
Redistributing: eigrp 101
EIGRP NSF-aware route hold timer is 240s
Automatic network summarization is in effect
Routing Information Sources:
Gateway Distance Last Update
Distance: internal 90 external 170
Table 78 describes the significant fields shown in the display.
Table 85 show ip protocols Field Descriptions for IGRP Processes
Field
|
Description
|
Routing Protocol is "eigrp 101"
|
Specifies the routing protocol used.
|
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.
|
EIGRP...
|
Specifies the value of the K0-K5 metrics, and the maximum hop count.
|
Redistributing
|
Lists the protocol that is being redistributed.
|
EIGRP NSF-Aware...
|
Displays the route-hold timer value.
|
Automatic network summarization...
|
Specifies that automatic summarization is enabled.
|
Routing
|
Specifies the networks for which the routing process is currently injecting routes.
|
Routing Information Sources
|
Lists all the routing sources the Cisco IOS software is using to build its routing table. For each source, you will see the following displayed:
• IP address
• Administrative distance
• Time the last update was received from this source
|
show ip rip database
To display summary address entries in the Routing Information Protocol (RIP) routing database entries if relevant are routes being summarized based upon a summary address, use the show ip rip database command in EXEC mode.
show ip rip database [ip-address {mask}]
Syntax Description
ip-address
|
(Optional) Address about which routing information should be displayed.
|
mask
|
Argument for the subnet mask. The subnet mask must also be specified if the IP address argument is entered.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(6)T
|
This command was introduced.
|
Usage Guidelines
Summary address entries will appear in the database only if relevant child routes are being summarized. When the last child route for a summary address becomes invalid, the summary address is also removed from the routing table.
The RIP private database is populated only if triggered extensions to RIP are enabled with the ip rip triggered command.
Examples
The following output shows a summary address entry for route 10.11.0.0/16, with three child routes active:
Router# show ip rip database
10.11.11.0/24 directly connected, Ethernet2
^^^^^^^^^^^^^^^^^^^^^^^^^^^
10.11.10.0/24 directly connected, Ethernet3
10.11.11.0/24 directly connected, Ethernet4
10.11.12.0/24 directly connected, Ethernet5
The following is sample output from the show ip rip database command with a prefix and mask:
Router# show ip rip database 172.19.86.0 255.255.255.0
[1] via 172.19.67.38, 00:00:25, Serial0
[2] via 172.19.70.36, 00:00:14, Serial1
Table 79 describes the fields in the displays.
Table 86 show ip rip database Field Descriptions
Field
|
Description
|
10.0.0.0/16 auto-summary
|
Summary address entry.
|
10.11.11.0/24 directly connected, Ethernet0
|
Directly connected entry for Ethernet 0.
|
172.19.65.0/24
[1] via 172.19.70.36, 00:00:17, Serial0
[2] via 172.19.67.38, 00:00:25, Serial1
|
The destination 172.19.65.0/24 is learned via RIP. There are two sources advertising it. One is 172.19.70.36 via Serial interface0, and it was updated 17 seconds ago. The other source is 172.19.67.38 via Serial interface 1, and it was updated 25 seconds ago.
|
Related Commands
|
Description
|
ip rip triggered
|
Enables triggered extensions of RIP.
|
ip summary-address rip
|
Configures a Cisco router running RIP Version 2 to advertise a summarized local IP address pool on a network access server so that the address pool can be provided to dialup clients, and specifies the IP address and network mask that identify the routes to be summarized.
|
show ip protocols
|
Displays the parameters and current state of the active routing protocol process.
|
show ip route
To display the current state of the routing table, use the show ip route command in user EXEC or privileged EXEC mode.
show ip route [[ip-address [mask] [longer-prefixes]] | [protocol [process-id]] | [list
access-list-number | access-list-name] | [static download]]
Syntax Description
ip-address
|
(Optional) Address about which routing information should be displayed.
|
mask
|
(Optional) Argument for a subnet mask.
|
longer-prefixes
|
(Optional) Specifies that only routes matching the ip-address and mask pair should be displayed.
|
protocol
|
(Optional) The 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, hello, igrp, isis, ospf, and rip.
|
process-id
|
(Optional) The number used to identify a process of the specified protocol.
|
list
|
(Optional) The list keyword is required to filter output by an access list name or number.
|
access-list-number
|
(Optional) Filters the displayed output from the routing table based on the specified access list name.
|
access-list-name
|
(Optional) Filters the displayed output from the routing table based on the specified access list number.
|
static
|
(Optional) All static routes.
|
download
|
(Optional) The route installed using the AAA route download function.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
9.2
|
This command was introduced.
|
10.0
|
The "D—EIGRP, EX—EIGRP, N1—OSPF NSSA external type 1 route" and "N2—OSPF NSSA external type 2 route" codes were added to the command output.
|
10.3
|
The process-id argument was added.
|
11.0
|
The longer-prefixes keyword was added.
|
11.1
|
The "U—per-user static route" code was added to the command output.
|
11.2
|
The "o—on-demand routing" code was added to the command output.
|
11.3
|
The output from the show ip route ip-address command was enhanced to display the origination of an IP route in Intermediate System-to-Intermediate System (IS-IS) networks.
|
12.0(1)T
|
The "M—mobile" code was added to the command output.
|
12.0(3)T
|
The "P—periodic downloaded static route" code was added to the command output.
|
12.0(4)T
|
The "ia—IS-IS" code was added to the command output.
|
12.2(2)T
|
The output from the show ip route ip-address command was enhanced to display information on the multipaths to the specified network.
|
12.2(13)T
|
The egp and igrp arguments were removed because the exterior gateway protocol (EGP) and the Interior Gateway Routing Protocol (IGRP) are no longer available in Cisco IOS software.
|
12.3(2)T
|
The output from the show ip route command was enhanced to display route tag information.
|
12.3(8)T
|
The output from the show ip route command was enhanced to display static routes using DHCP.
|
Usage Guidelines
The show ip route static download command provides a way to display all dynamic static routes with name and distance information, including active and inactive ones. You can display all active dynamic static routes with both the show ip route and show ip route static commands after these active routes are added in the main routing table.
Examples
Routing Table Examples
The following examples show the standard routing tables displayed by the show ip route command. Use the codes displayed at the beginning of each report and the information in Table 87 to understand the type of route.
The following is sample output from the show ip route command when entered without an address:
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,
i - IS-IS derived, ia - IS-IS, U - per-user static route,
o - on-demand routing, M - mobile, P - periodic downloaded static route,
D - EIGRP, EX - EIGRP external, E1 - OSPF external type 1 route,
E2 - OSPF external type 2 route, N1 - OSPF NSSA external type 1 route,
N2 - OSPF NSSA external type 2 route
Gateway of last resort is 10.119.254.240 to network 10.140.0.0
O E2 10.110.0.0 [160/5] via 10.119.254.6, 0:01:00, Ethernet2
E 10.67.10.0 [200/128] via 10.119.254.244, 0:02:22, Ethernet2
O E2 10.68.132.0 [160/5] via 10.119.254.6, 0:00:59, Ethernet2
O E2 10.130.0.0 [160/5] via 10.119.254.6, 0:00:59, Ethernet2
E 10.128.0.0 [200/128] via 10.119.254.244, 0:02:22, Ethernet2
E 10.129.0.0 [200/129] via 10.119.254.240, 0:02:22, Ethernet2
E 10.65.129.0 [200/128] via 10.119.254.244, 0:02:22, Ethernet2
E 10.10.0.0 [200/128] via 10.119.254.244, 0:02:22, Ethernet2
E 10.75.139.0 [200/129] via 10.119.254.240, 0:02:23, Ethernet2
E 10.16.208.0 [200/128] via 10.119.254.244, 0:02:22, Ethernet2
E 10.84.148.0 [200/129] via 10.119.254.240, 0:02:23, Ethernet2
E 10.31.223.0 [200/128] via 10.119.254.244, 0:02:22, Ethernet2
E 10.44.236.0 [200/129] via 10.119.254.240, 0:02:23, Ethernet2
E 10.141.0.0 [200/129] via 10.119.254.240, 0:02:22, Ethernet2
E 10.140.0.0 [200/129] via 10.119.254.240, 0:02:23, Ethernet2
The following is sample output that includes IS-IS Level 2 routes learned:
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,
i - IS-IS derived, ia - IS-IS, U - per-user static route,
o - on-demand routing, M - mobile, P - periodic downloaded static route,
D - EIGRP, EX - EIGRP external, E1 - OSPF external type 1 route,
E2 - OSPF external type 2 route, N1 - OSPF NSSA external type 1 route,
N2 - OSPF NSSA external type 2 route
Gateway of last resort is not set
10.89.0.0 is subnetted (mask is 255.255.255.0), 3 subnets
C 10.89.64.0 255.255.255.0 is possibly down,
routing via 0.0.0.0, Ethernet0
i L2 10.89.67.0 [115/20] via 10.89.64.240, 0:00:12, Ethernet0
i L2 10.89.66.0 [115/20] via 10.89.64.240, 0:00:12, Ethernet0
The following is sample output using the longer-prefixes keyword. When the longer-prefixes keyword is included, the address and mask pair becomes the prefix, and any address that matches that prefix is displayed. Therefore, multiple addresses are displayed.
In the following example, the logical AND operation is performed on the source address 10.0.0.0 and the mask 10.0.0.0, resulting in 10.0.0.0. Each destination in the routing table is also logically ANDed with the mask and compared to that result of 10.0.0.0. Any destinations that fall into that range are displayed in the output.
Router# show ip route 10.0.0.0 10.0.0.0 longer-prefixes
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,
i - IS-IS derived, ia - IS-IS, U - per-user static route,
o - on-demand routing, M - mobile, P - periodic downloaded static route,
D - EIGRP, EX - EIGRP external, E1 - OSPF external type 1 route,
E2 - OSPF external type 2 route, N1 - OSPF NSSA external type 1 route,
N2 - OSPF NSSA external type 2 route
Gateway of last resort is not set
S 10.134.0.0 is directly connected, Ethernet0
S 10.10.0.0 is directly connected, Ethernet0
S 10.129.0.0 is directly connected, Ethernet0
S 10.128.0.0 is directly connected, Ethernet0
S 10.49.246.0 is directly connected, Ethernet0
S 10.160.97.0 is directly connected, Ethernet0
S 10.153.88.0 is directly connected, Ethernet0
S 10.76.141.0 is directly connected, Ethernet0
S 10.75.138.0 is directly connected, Ethernet0
S 10.44.237.0 is directly connected, Ethernet0
S 10.31.222.0 is directly connected, Ethernet0
S 10.16.209.0 is directly connected, Ethernet0
S 10.145.0.0 is directly connected, Ethernet0
S 10.141.0.0 is directly connected, Ethernet0
S 10.138.0.0 is directly connected, Ethernet0
S 10.128.0.0 is directly connected, Ethernet0
10.19.0.0 255.255.255.0 is subnetted, 1 subnets
C 10.19.64.0 is directly connected, Ethernet0
10.69.0.0 is variably subnetted, 2 subnets, 2 masks
C 10.69.232.32 255.255.255.240 is directly connected, Ethernet0
S 10.69.0.0 255.255.0.0 is directly connected, Ethernet0
The following examples display all downloaded static routes. A P designates which route was installed using AAA route download.
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
U - per-user static route, o - ODR, P - periodic downloaded static route
T - traffic engineered route
Gateway of last resort is 172.21.17.1 to network 0.0.0.0
172.31.0.0/32 is subnetted, 1 subnets
P 172.31.229.41 is directly connected, Dialer1 20.0.0.0/24 is subnetted, 3 subnets
P 10.1.1.0 [200/0] via 172.31.229.41, Dialer1
P 10.1.3.0 [200/0] via 172.31.229.41, Dialer1
P 10.1.2.0 [200/0] via 172.31.229.41, Dialer1
Router# show ip route static
172.27.4.0/8 is variably subnetted, 2 subnets, 2 masks
P 172.1.1.1/32 is directly connected, BRI0
P 172.27.4.0/8 [1/0] via 103.1.1.1, BRI0
S 172.31.0.0/16 [1/0] via 172.21.114.65, Ethernet0
S 10.0.0.0/8 is directly connected, BRI0
P 10.0.0.0/8 is directly connected, BRI0
172.21.0.0/16 is variably subnetted, 5 subnets, 2 masks
S 172.21.114.201/32 is directly connected, BRI0
S 172.21.114.205/32 is directly connected, BRI0
S 172.21.114.174/32 is directly connected, BRI0
S 172.21.114.12/32 is directly connected, BRI0
P 10.0.0.0/8 is directly connected, BRI0
P 10.1.0.0/8 is directly connected, BRI0
P 10.2.2.0/8 is directly connected, BRI0
S* 0.0.0.0/0 [1/0] via 172.21.114.65, Ethernet0
S 172.29.0.0/16 [1/0] via 172.21.114.65, Ethernet0
The following example shows how to use the show ip route static download command to display all active and inactive routes installed using AAA route download:
Router# show ip route static download
Connectivity: A - Active, I - Inactive
A 10.10.0.0 255.0.0.0 BRI0
A 10.11.0.0 255.0.0.0 BRI0
A 10.12.0.0 255.0.0.0 BRI0
A 10.13.0.0 255.0.0.0 BRI0
I 10.20.0.0 255.0.0.0 172.21.1.1
I 10.22.0.0 255.0.0.0 Serial0
I 10.30.0.0 255.0.0.0 Serial0
I 10.31.0.0 255.0.0.0 Serial1
I 10.32.0.0 255.0.0.0 Serial1
A 10.34.0.0 255.0.0.0 103.1.1.1
A 10.36.1.1 255.255.255.255 BRI0 200 name remote1
I 10.38.1.9 255.255.255.0 104.21.69.1
Table 87 show ip route Field Descriptions
Field
|
Description
|
O
|
Indicates the protocol that derived the route. It can be one of the following values:
I—Interior Gateway Routing Protocol (IGRP) derived
R—Routing Information Protocol (RIP) derived
O—Open Shortest Path First (OSPF) derived
C—connected
S—static
E—Exterior Gateway Protocol (EGP) derived
B—Border Gateway Protocol (BGP) derived
D—Enhanced Interior Gateway Routing Protocol (EIGRP)
EX—EIGRP external
i—IS-IS derived
ia—IS-IS
M—mobile
P—periodic downloaded static route
U—per-user static route
o—on-demand routing
|
E2
|
Type of route. It can be one of the following values:
*—Indicates the last path used when a packet was forwarded. It pertains only to the nonfast-switched packets. However, it does not indicate which path will be used next when forwarding a nonfast-switched packet, except when the paths are equal cost.
IA—OSPF interarea 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
N1—OSPF not-so-stubby area (NSSA) external type 1 route
N2—OSPF NSSA external type 2 route
|
10.110.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 10.119.254.6
|
Specifies the address of the next router to the remote network.
|
0:01:00
|
Specifies the last time the route was updated (in hours:minutes:seconds).
|
Ethernet2
|
Specifies the interface through which the specified network can be reached.
|
Specific Route Information
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 10.0.0.1:
Router# show ip route 10.0.0.1
Routing entry for 10.0.0.1/32
Known via "isis", distance 115, metric 20, type level-1
Last update from 10.191.255.251 on Fddi1/0, 00:00:13 ago
Routing Descriptor Blocks:
* 10.22.22.2, from 10.191.255.247, via Serial2/3
Route metric is 20, traffic share count is 1
10.191.255.251, from 10.191.255.247, via Fddi1/0
Route metric is 20, traffic share count is 1
When an IS-IS router advertises its link-state information, it includes one of its own IP addresses to be used as the originator IP address. When other routers calculate IP routes, they can store the originator IP address with each route in the routing table.
The example above shows the output from the show ip route command when looking at an IP route generated by IS-IS. Each path that is shown under the Routing Descriptor Blocks report displays two IP addresses. The first address (10.22.22.2) is the next hop address. The second is the originator IP address from the advertising IS-IS router. This address helps you determine where a particular IP route has originated in your network. In the example the route to 10.0.0.1/32 was originated by a router with IP address 10.191.255.247.
Table 81 describes the significant fields shown when using the show ip route command with an IP address (previous displays).
Table 88 show ip route with Address Field Descriptions
Field
|
Description
|
Routing entry for 10.0.0.1/32
|
Network number and mask.
|
Known via...
|
Indicates how the route was derived.
|
Tag
|
Integer that is used to implement the route.
|
type
|
Indicates the IS-IS route type (Level 1 or Level 2).
|
Redistributing via...
|
Indicates the redistribution protocol.
|
Last update from 10.191.255.251
|
Indicates the IP address of a router that is the next hop to the remote network and the router interface on which the last update arrived.
|
Routing Descriptor Blocks:
|
Displays the next hop IP address followed by the information source.
|
Route metric
|
This value is the best metric for this routing descriptor block.
|
traffic share count
|
Number of uses for this routing descriptor block.
|
The following is sample output using the longer-prefixes keyword. When the longer-prefixes keyword is included, the address and mask pair becomes the prefix, and any address that matches that prefix is displayed. Therefore, multiple addresses are displayed.
In the following example, the logical AND operation is performed on the source address 10.0.0.0 and the mask 10.0.0.0, resulting in 10.0.0.0. Each destination in the routing table is also logically ANDed with the mask and compared to that result of 10.0.0.0. Any destinations that fall into that range are displayed in the output.
Router# show ip route 10.0.0.0 10.0.0.0 longer-prefixes
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,
i - IS-IS derived, ia - IS-IS, U - per-user static route,
o - on-demand routing, M - mobile, P - periodic downloaded static route,
D - EIGRP, EX - EIGRP external, E1 - OSPF external type 1 route,
E2 - OSPF external type 2 route, N1 - OSPF NSSA external type 1 route,
N2 - OSPF NSSA external type 2 route
Gateway of last resort is not set
S 10.134.0.0 is directly connected, Ethernet0
S 10.10.0.0 is directly connected, Ethernet0
S 10.129.0.0 is directly connected, Ethernet0
S 10.128.0.0 is directly connected, Ethernet0
S 10.49.246.0 is directly connected, Ethernet0
S 10.160.97.0 is directly connected, Ethernet0
S 10.153.88.0 is directly connected, Ethernet0
S 10.76.141.0 is directly connected, Ethernet0
S 10.75.138.0 is directly connected, Ethernet0
S 10.44.237.0 is directly connected, Ethernet0
S 10.31.222.0 is directly connected, Ethernet0
S 10.16.209.0 is directly connected, Ethernet0
S 10.145.0.0 is directly connected, Ethernet0
S 10.141.0.0 is directly connected, Ethernet0
S 10.138.0.0 is directly connected, Ethernet0
S 10.128.0.0 is directly connected, Ethernet0
10.19.0.0 255.255.255.0 is subnetted, 1 subnets
C 10.19.64.0 is directly connected, Ethernet0
10.69.0.0 is variably subnetted, 2 subnets, 2 masks
C 10.69.232.32 255.255.255.240 is directly connected, Ethernet0
S 10.69.0.0 255.255.0.0 is directly connected, Ethernet0
The following output includes the tag 120 applied to the route 10.22.0.0/16. You must specify an IP prefix in order to see the tag value.
Router# show ip route 10.22.0.0
Routing entry for 10.22.0.0/16
Known via "isis", distance 115, metric 12
Last update from 172.19.170.12 on Ethernet2, 01:29:13 ago
Routing Descriptor Blocks:
* 172.19.170.12, from 3.3.3.3, via Ethernet2
Route metric is 12, traffic share count is 1
Static Routes Using a DHCP Gateway Examples
The following example shows that IP route 68.8.8.0 is directly connected to the Internet and is the next-hop (option 3) default gateway. Routes 1.1.1.1 [1/0], 4.3.2.1 [24/0], and 67.2.2.2 [1/0] are static, and route 0.0.0.0/0 is a default route candidate.:
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is 10.0.19.14 to network 0.0.0.0
68.0.0.0/24 is subnetted, 1 subnets
C 68.8.8.0 is directly connected, Ethernet1
1.0.0.0/32 is subnetted, 1 subnets
S 1.1.1.1 [1/0] via 68.8.8.1
4.0.0.0/32 is subnetted, 1 subnets
S 4.3.2.1 [24/0] via 68.8.8.1
67.0.0.0/32 is subnetted, 1 subnets
S 67.2.2.2 [1/0] via 68.8.8.1
10.0.0.0/28 is subnetted, 1 subnets
C 10.0.19.0 is directly connected, Ethernet0
15.0.0.0/24 is subnetted, 1 subnets
C 15.15.15.0 is directly connected, Loopback0
S* 0.0.0.0/0 [1/0] via 10.0.19.14
Related Commands
Command
|
Description
|
show dialer
|
Displays general diagnostic information for interfaces configured for DDR.
|
show interfaces tunnel
|
Displays a list of tunnel interface information.
|
show ip route summary
|
Displays the current state of the routing table in summary format.
|
show ip route profile
To display routing table change statistics, use the show ip route profile command in EXEC mode.
show ip route profile
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0
|
This command was introduced.
|
Usage Guidelines
Use this command in combination with the ip route profile global configuration command to validate the routing table change statistics.
Examples
The following example shows the frequency of routing table changes in a 5-second sampling interval. In this example, the Prefix add change occurred 22 times in one interval and 24 times in another interval. The output represents this with a Fwd-path change value of 2 and a Prefix add value of 2:
Router# show ip route profile
--------------------------------------------------------------------
Change/ Fwd-path Prefix Nexthop Pathcount Prefix
interval change add Change Change refresh
--------------------------------------------------------------------
Table 89 describes the significant fields shown in the display.
Table 89 show ip route profile Field Descriptions
Field
|
Description
|
Change/interval
|
Represents the frequency buckets. A Change/interval of 20 represents the bucket that is incremented when a particular event occurs 20 times in a sampling interval. It is very common to see high counters for the Change/interval bucket for 0. This counter represents the number of sampling intervals in which there were no changes to the routing table. Route removals are not counted in the statistics, only route additions.
|
Fwd-path change
|
Number of changes in the forwarding path. This value represents the accumulation of Prefix add, Nexthop change, and Pathcount change.
|
Prefix add
|
A new prefix was added to the routing table.
|
Nexthop change
|
A prefix is not added or removed, but the next hop changes. This statistic is only seen with recursive routes that are installed in the routing table.
|
Pathcount change
|
The number of paths in the routing table has changed. This change is the result of an increase in the number of paths for an Interior Gateway Protocol (IGP).
|
Prefix refresh
|
Indicates standard routing table maintenance. The forwarding behavior was not changed.
|
Related Commands
Command
|
Description
|
ip route profile
|
Enables IP routing table statistics collection
|
show ip route summary
To display the current state of the routing table, use the show ip route summary command in EXEC mode.
show ip route summary
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
The following is sample output from the show ip route summary command:
Router# show ip route summary
IP routing table name is Default-IP-Routing-Table(0)
IP routing table maximum-paths is 16
Route Source Networks Subnets Overhead Memory (bytes)
eigrp 109 747 12 31878 91080
Table 90 describes the significant fields shown in the display.
Table 90 show ip route summary Field Descriptions
Field
|
Description
|
IP routing table name is...
|
Type of routing table.
|
IP routing table maximum-paths is...
|
Number of parallel routes supported by this routing table.
|
Route Source
|
Routing protocol name, or the connected, static, or internal keyword. "Internal" indicates those routes that are in the routing table that are not owned by any routing protocol.
|
Networks
|
Number of prefixes that are present in the routing table for each route source.
|
Subnets
|
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 in the Memory field.
|
Memory
|
Number of bytes allocated to maintain all the routes for the particular route source.
|
Related Commands
Command
|
Description
|
show ip route
|
Displays the current state of the routing table.
|
show ip route supernets-only
To display information about supernets, use the show ip route supernets-only privileged command in EXEC mode.
show ip route supernets-only
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
The following is sample output from the show ip route supernets-only command. This display shows supernets only; it does not show subnets.
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 172.160.0.0 (mask is 255.255.0.0) [20/0] via 172.160.72.30, 0:00:50
B 192.0.0.0 (mask is 255.0.0.0) [20/0] via 172.160.72.24, 0:02:50
Table 91 describes the significant fields shown in the display.
Table 91 show ip route supernets-only Field Descriptions
Field
|
Description
|
B
|
Border Gateway Protocol (BGP) derived, as shown in list of codes.
|
172.160.0.0 (mask is 255.255.0.0)
|
Supernet IP address.
|
[20/0]
|
Administrative distance (external/internal).
|
via 172.160.72.30
|
Next hop IP address.
|
0:00:50
|
Age of the route (how long ago the update was received).
|
show ip route track-table
To display information about the IP route track table, use the show ip route track-table command in privileged EXEC mode.
show ip route track-table
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.3(2)XE
|
This command was introduced.
|
12.3(8)T
|
This command was integrated into Cisco IOS Release 12.3(8)T.
|
Examples
The following example displays information about the IP route track table:
Router# show ip route track-table
ip route 0.0.0.0 0.0.0.0 10.1.1.242 track-object 123 state is [up]
Table 92 describes the significant fields shown in the display.
Table 92 show ip route track-table Field Descriptions
Field
|
Description
|
ip route
|
The configured IP route.
|
track-object
|
The track object number.
|
state is
|
The state of the track object. The object may be up or down.
|
show isis database verbose
To display additional information about the IS-IS database, use the show isis database verbose command in user EXEC or privileged EXEC mode.
show isis database verbose
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0(5)S
|
This command was introduced.
|
Examples
The following is sample output from the show isis database verbose command:
Router# show isis database verbose
IS-IS Level-1 Link State Database
LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL
dtp-5.00-00 * 0x000000E6 0xC9BB 1042 0/0/0
Metric:10 IP 172.21.39.0/24
dtp-5.00-01 * 0x000000E7 0xAB36 1065 0/0/0
Metric:10 IS-Extended dtp-5.01
Interface IP Address:172.21.39.5
Physical BW:10000000 bits/sec
Reservable BW:1166000 bits/sec
BW Unreserved[0]: 1166000 bits/sec, BW Unreserved[1]: 1166000 bits/sec
BW Unreserved[2]: 1166000 bits/sec, BW Unreserved[3]: 1166000 bits/sec
BW Unreserved[4]: 1166000 bits/sec, BW Unreserved[5]: 1166000 bits/sec
BW Unreserved[6]: 1166000 bits/sec, BW Unreserved[7]: 1153000 bits/sec
Table 93 describes the significant fields shown in the display.
Table 93 show isis database verbose Field Descriptions
Field
|
Description
|
LSPID
|
LSP identifier. The first six octets form the System ID of the router that originated the LSP.
The next octet is the pseudonode ID. When this byte is zero, the LSP describes links from the system. When it is nonzero, the LSP is a pseudonode LSP. This is similar to a router LSA in OSPF; the LSP describes the state of the originating router. For each LAN, the designated router for that LAN creates and floods a pseudonode LSP that describes all systems attached to that LAN.
The last octet is the LSP number. If all the data cannot fit into a single LSP, the LSP is divided into multiple LSP fragments. Each fragment has a different LSP number. An asterisk (*) indicates that the system issuing this command originated the LSP.
|
LSP Seq Num
|
LSP sequence number that allows other systems to determine if they received the latest information from the source.
|
LSP Checksum
|
Checksum of the entire LSP packet.
|
LSP Holdtime
|
Amount of time that the LSP remains valid (in seconds). An LSP hold time of zero indicates that this LSP was purged and is being removed from all routers' link-state databases (LSDBs). The value indicates how long the purged LSP will stay in the LSDB before it is completely removed.
|
ATT
|
Attach bit. This bit indicates that the router is also a Level 2 router, and it can reach other areas. Level 1 routers use the Attach bit to find the closest Level 2 router. They install a default route to the closest Level 2 router.
|
P
|
P bit. This bit detects if the IS can repair area partitions. Cisco and other vendors do not support area partition repair.
|
OL
|
Overload bit. This bit determines if the IS is congested. If the overload bit is set, other routers do not use this system as a transit router when they calculate routes. Only packets for destinations directly connected to the overloaded router are sent to this router.
|
Area Address
|
Reachable area addresses from the router. For Level 1 LSPs, these are the area addresses configured manually on the originating router. For Level 2 LSPs, these are all the area addresses for the area to which this router belongs.
|
NLPID
|
Network Layer Protocol identifier.
|
Hostname
|
Host name of the node.
|
Router ID
|
Traffic engineering router identifier for the node.
|
IP Address
|
IPv4 address for the interface.
|
Metric
|
IS-IS metric for the cost of the adjacency between the originating router and the advertised neighbor, or the metric of the cost to get from the advertising router to the advertised destination (which can be an IP address, an end system (ES), or a connectionless network service [CLNS] prefix).
|
Affinity
|
Link attribute flags that are being flooded.
|
Physical BW
|
Link bandwidth capacity (in bits per second).
|
Reservable BW
|
Amount of reservable bandwidth on this link.
|
BW Unreserved
|
Amount of bandwidth that is available for reservation.
|
The following example includes a route tag:
Router# show isis database verbose
IS-IS Level-1 Link State Database:
LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL
dasher.00-00 0x000000F8 0xE57B 518 1/0/0
Metric: 10 IP 172.19.170.0/24
Metric: 10 IP 10.3.0.0/30
Metric: 10 IS-Extended dasher.02172.19.170.0/24
Metric: 20 IP-Interarea 1.1.1.1/32
Metric: 20 IP-Interarea 205.171.0.6/32
Related Commands
Command
|
Description
|
show isis mpls traffic-eng adjacency-log
|
Displays a log of 20 entries of MPLS traffic engineering IS-IS adjacency changes.
|
show isis mpls traffic-eng advertisements
|
Displays the last flooded record from MPLS traffic engineering.
|
show isis mpls traffic-eng tunnel
|
Displays information about tunnels considered in the IS-IS next hop calculation.
|
show isis database
To display the Intermediate System-to-Intermediate System (IS-IS) link-state database, use the show isis database command in user EXEC or privileged EXEC mode.
show isis [process-tag] database [level-1] [level-2] [l1] [l2] [detail] [lspid]
Syntax Description
process-tag
|
(Optional) A unique name among all International Organization for Standardization (ISO) router processes including IP and Connectionless Network Service (CLNS) router processes for a given router. If a process tag is specified, output is limited to the specified routing process. When "null" is specified for the process tag, output is displayed only for the router process that has no tag specified. If a process tag is not specified, output is displayed for all processes.
|
level-1
|
(Optional) Displays the IS-IS link-state database for Level 1.
|
level-2
|
(Optional) Displays the IS-IS link-state database for Level 2.
|
l1
|
(Optional) Abbreviation for the level-1 option.
|
l2
|
(Optional) Abbreviation for the level-2 option.
|
detail
|
(Optional) Displays the contents of each link-state packet (LSP). Otherwise, a summary display is provided.
|
lspid
|
(Optional) Displays the link-state protocol data unit (PDU) identifier. Displays the contents of a single LSP by its ID number.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2(15)T
|
Support was added for IPv6.
|
12.2(18)S
|
This command was integrated into Cisco IOS Release 12.2(18)S.
|
12.0(26)S
|
This command was integrated into Cisco IOS Release 12.0(26)S.
|
12.0(29)S
|
The process-tag argument was added.
|
Usage Guidelines
The order of the optional argument and keywords is not important when this command is entered. For example, the following are both valid command specifications and provide the same output: show isis database detail l2 and show isis database l2 detail.
Examples
The following is sample output from the show isis database command:
Router# show isis database
IS-IS Level-1 Link State Database
LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL
0000.0C00.0C35.00-00 0x0000000C 0x5696 792 0/0/0
0000.0C00.40AF.00-00* 0x00000009 0x8452 1077 1/0/0
0000.0C00.62E6.00-00 0x0000000A 0x38E7 383 0/0/0
0000.0C00.62E6.03-00 0x00000006 0x82BC 384 0/0/0
0800.2B16.24EA.00-00 0x00001D9F 0x8864 1188 1/0/0
0800.2B16.24EA.01-00 0x00001E36 0x0935 1198 1/0/0
IS-IS Level-2 Link State Database
LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL
0000.0C00.0C35.03-00 0x00000005 0x04C8 792 0/0/0
0000.0C00.3E51.00-00 0x00000007 0xAF96 758 0/0/0
0000.0C00.40AF.00-00* 0x0000000A 0x3AA9 1077 0/0/0
The following is sample output from the show isis database command using the process-tag argument to display information about a VPN routing/forwarding instance (VRF)-aware IS-IS instance tagFirst:
Router# show isis tagFirst database level-2
IS-IS Level-2 Link State Database:
LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL
igp-01.00-00 0x0000000A 0x5E73 914 0/0/0
igp-01.03-00 0x00000001 0x8E41 894 0/0/0
igp-01.04-00 0x00000001 0x8747 894 0/0/0
igp-03.00-00 * 0x00000005 0x55AD 727 0/0/0
igp-03.02-00 * 0x00000001 0x3B97 727 0/0/0
igp-02.00-0 0x00000004 0xC1FB 993 0/0/0
igp-02.01-00 0x00000001 0x448D 814 0/0/0
igp-04.00-00 0x00000004 0x76D0 892 0/0/0
Table 94 describes the significant fields shown in the display.
.
Table 94 show isis database Field Descriptions
Field
|
Description
|
Tag tagFirst
|
Tag name that identifies an IS-IS instance.
|
LSPID
|
The LSP identifier. The first six octets form the system ID of the router that originated the LSP.
The next octet is the pseudonode ID. When this byte is zero, the LSP describes links from the system. When it is nonzero, the LSP is a so-called nonpseudonode LSP. This is similar to a router link-state advertisement (LSA) in the Open Shortest Path First (OSPF) protocol. The LSP will describe the state of the originating router.
For each LAN, the designated router for that LAN will create and flood a pseudonode LSP, describing all systems attached to that LAN.
The last octet is the LSP number. If there is more data than can fit in a single LSP, the LSP will be divided into multiple LSP fragments. Each fragment will have a different LSP number. An asterisk (*) indicates that the LSP was originated by the system on which this command is issued.
|
LSP Seq Num
|
Sequence number for the LSP that allows other systems to determine if they have received the latest information from the source.
|
LSP Checksum
|
Checksum of the entire LSP packet.
|
LSP Holdtime
|
Amount of time the LSP remains valid (in seconds). An LSP hold time of zero indicates that this LSP was purged and is being removed from the link-state database (LSDB) of all routers. The value indicates how long the purged LSP will stay in the LSDB before being completely removed.
|
ATT
|
The Attach bit. This bit indicates that the router is also a Level 2 router, and it can reach other areas. Level 1-only routers and Level 1-2 routers that have lost connection to other Level 2 routers will use the Attach bit to find the closest Level 2 router. They will point a default route to the closest Level 2 router.
|
P
|
The P bit. Detects if the intermediate systems is area partition repair-capable. Cisco and other vendors do not support area partition repair.
|
OL
|
The Overload bit. Determines if the IS is congested. If the Overload bit is set, other routers will not use this system as a transit router when calculating routers. Only packets for destinations directly connected to the overloaded router will be sent to this router.
|
The following is sample output from the show isis database detail command:
Router# show isis database detail
IS-IS Level-1 Link State Database
LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL
0000.0C00.0C35.00-00 0x0000000C 0x5696 325 0/0/0
Area Address: 47.0004.004D.0001
Metric: 10 IS 0000.0C00.62E6.03
Metric: 0 ES 0000.0C00.0C35
0000.0C00.40AF.00-00* 0x00000009 0x8452 608 1/0/0
Area Address: 47.0004.004D.0001
Topology: IPv4 (0x0) IPv6 (0x2)
Metric: 10 IS 0800.2B16.24EA.01
Metric: 10 IS 0000.0C00.62E6.03
Metric: 0 ES 0000.0C00.40AF
IPv6 Address: 2001:0DB8::/32
Metric: 10 IPv6 (MT-IPv6) 2001:0DB8::/64
Metric: 5 IS-Extended cisco.03
Metric: 10 IS-Extended cisco1.03
Metric: 10 IS (MT-IPv6) cisco.03
As the output shows, in addition to the information displayed with the show isis database command, the show isis database detail command displays the contents of each LSP.
Table 95 describes the significant fields shown in the display.
.
Table 95 show isis database detail Field Descriptions
Field
|
Description
|
Area Address:
|
Reachable area addresses from the router. For Level 1 LSPs, these are the area addresses configured manually on the originating router. For Level 2 LSPs, these are all the area addresses for the area to which this route belongs.
|
Metric:
|
IS-IS metric for the cost of the adjacency between the originating router and the advertised neighbor, or the metric of the cost to get from the advertising router to the advertised destination (which can be an IP address, an end system [ES], or a CLNS prefix).
|
Topology
|
States the topology supported (for example, IPv4, IPv6).
|
IPv6 Address
|
The IPv6 address.
|
MT-IPv6
|
Advertised using multitopology TLV.
|
The following is additional sample output from the show isis database detail command. This LSP is a Level 2 LSP. The area address 39.0001 is the address of the area in which the router resides.
Router# show isis database detail l2
IS-IS Level-2 Link State Database
LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL
0000.0C00.1111.00-00* 0x00000006 0x4DB3 1194 0/0/0
Metric: 10 IS 0000.0C00.1111.09
Metric: 10 IS 0000.0C00.1111.08
Metric: 10 IP 172.16.65.0 255.255.255.0
show isis hostname
To display the router-name-to-system-ID mapping table entries for an Intermediate System-to-Intermediate System (IS-IS) router, use the show isis hostname command in privileged EXEC mode.
show isis hostname
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0
|
This command was introduced.
|
12.0S
|
This command was integrated into Cisco IOS Release 12.0(S).
|
Usage Guidelines
In the IS-IS routing domain, the system ID is used to represent each router. The system ID is part of the network entity title (NET) that is configured for each IS-IS router. For example, a router with a configured NET of 49.0001.0023.0003.000a.00 has a system ID of 0023.0003.000a. Router-name-to-system-ID mapping is difficult for network administrators to remember during maintenance and troubleshooting on the routers. Entering the show isis hostname command displays the entries in the router-name-to-system-ID mapping table.
If the dynamic hostname feature has not been disabled by entering the no dynamic hostname command, the mapping will consist of a dynamic host mapping table. However, if the clns host command has been entered to create a mapping between the router name and the system ID, this locally defined mapping will take precedence over the dynamicly learned one from the dynamic hostname feature.
Examples
The following example changes the hostname to RouterA and assigns the NET 49.0001.0000.0000.000b.00 to RouterA.
Router# configure terminal
Router(config)# hostname RouterA
RouterA(config)# router isis CompanyA
RouterA(config-router)# net 49.0001.0000.0000.000b.00
RouterA(config-router)# hostname dynamic
RouterA(config-router)# end
Entering the show isis hostname command displays the dynamic host mapping table. The dynamic host mapping table displays the router-name-to-system-ID mapping table entries for Router-b, Router-c and for the local router named Router-a. The command output shows that the local router is running the IS-IS process named CompanyA. The table also shows that the neighbor router Router-b is a Level-1 router, and its hostname is advertised by the Level-1 (L1) link-state protocol (LSP). Router-b is a Level-2 router and its hostname is advertised by the L2 LSP. The * symbol that appears under Level for the local router Router-a signifies that this is the router-name-to-system-ID mapping information for the local router.
Router-a# show isis hostname
Level System ID Dynamic Hostname (CompanyA)
1 3333.3333.333b Router-b
2 3131.3131.313b Router-c
* 3232.3232.323b Router-a
Related Commands
Command
|
Description
|
clns host
|
Defines a name-to-NSAP mapping that can then be used with commands that require NSAPs.
|
hostname
|
Specifies or modifies the hostname for the network server.
|
hostname dynamic
|
Enables dynamic hostname capability.
|
net
|
Configures an IS-IS NET for a CLNS or IS-IS routing process.
|
show isis rib
To display paths for a specific route or for all routes under a major network that are stored in the IP local Routing Information Base (RIB), use the show isis rib command in privileged EXEC mode.
show isis rib [ip-address | ip-address-mask]
Syntax Description
ip-address
|
(Optional) Displays paths for a specific route.
|
ip-address-mask
|
(Optional) Displays paths for all routes under a major network.
|
Defaults
If no ip-address or ip-address-mask arguments is specified, all routes in the Integrated Intermediate System-to-Intermediate System (IS-IS) local RIB will be displayed.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(26)S
|
This command was introduced.
|
12.3(4)T
|
This command was integrated into Cisco IOS Release 12.3(4)T.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S
|
Usage Guidelines
To verify that an IP prefix update that exists in the IP global RIB also has been updated in the IS-IS local RIB, enter the show isis rib command.
Examples
The following is sample output from the show isis rib command to show all routes under the major network with the IP address mask 10.2.2.0 255.255.255.0 that are stored within the IS-IS local RIB:
Router# show isis rib 10.2.2.0 255.255.255.0
IPv4 local RIB for IS-IS process
[115/L2/20} via 10.2.2.2(Ethernet2), from 10.22.22.22, tag 0, LSP[10/10]
Table 96 describes the significant fields shown in the display.
Table 96 show isis rib Field Descriptions
Field
|
Description
|
2.2.2.0/24
|
IP prefix that is stored within the IS-IS local RIB.
|
[115/L2/20]
|
Administrative instance/type/metric for the routing path to reach the next hop of the router.
|
via 2.2.2.2(Ethernet2)
|
IP address of the next hop—in this instance, Ethernet2.
|
tag 0
|
Priority of the IP prefix. All prefixes have a tag 0 priority unless otherwise configured.
|
Related Commands
Command
|
Description
|
ip route priority high
|
Assigns a high priority to an IS-IS IP prefix.
|
debug isis rib
|
Displays debug information for IP Version 4 routes within the global or IS-IS local RIB.
|
show isis rib redistribution
To display the prefixes in the local redistribution cache, use the show isis rib redistribution command in user EXEC or privileged EXEC mode.
show isis rib redistribution [level-1 | level-2] [network-prefix]
Syntax Description
level-1
|
(Optional) Displays level 1 local redistribution cache information.
|
level-2
|
(Optional) Displays level 2 local redistribution cache information.
|
network-prefix
|
(Optional) The network ID in the A.B.C.D format for a specific network.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0(27)S
|
This command was introduced.
|
12.3(7)T
|
This command was integrated into Cisco IOS Release 12.3(7)T.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S.
|
Usage Guidelines
You can use the show isis rib redistribution command to verify that desired routes have been redistributed into Intermediate System-to-Intermediate System (IS-IS). The command output will show the network prefixes in the local redistribution cache.
Examples
In the following example, the output from the show isis rib redistribution command verifies that Internet Protocol version 4 (IPv4) routes have been redistributed into IS-IS. The output is self-explanatory.
Router# show isis rib redistribution
IPv4 redistribution RIB for IS-IS process
The following lines indicate that the prefix 10.3.3.0 with a mask 24 was redistributed from the connected routing protocol into IS-IS as a level 1 route, cost 0, with a metric type external:
The following lines show that the connected routing protocol owns the prefix 10.0.18.48 and that the metric for the route is 28:
Related Commands
Command
|
Description
|
clear isis rib redistribution
|
Clears some or all prefixes in the local redistribution cache.
|
debug isis rib redistribution
|
Debugs the local redistribution cache event.
|
show isis spf-log
To display how often and why the router has run a full shortest path first (SPF) calculation, use the show isis spf-log user command in user EXEC or privileged EXEC mode.
show isis [area-tag] [ipv6 | *] spf-log
Syntax Description
area-tag
|
(Optional) Required for multiarea IS-IS configuration. Optional for conventional IS-IS configuration.
Meaningful name for a routing process. This name must be unique among all IP or Connectionless Network Service (CLNS) router processes for a given router. If an area tag is not specified, a null tag is assumed and the process is referenced with a null tag. If an area tag is specified, output is limited to the specified area.
|
ipv6
|
(Optional) Displays IS-IS multitopology for IPv6 SPF log.
|
*
|
(Optional) Displays the SPF logs of all address families.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2(15)T
|
Support was added for IPv6.
|
12.2(18)S
|
This command was integrated into Cisco IOS Release 12.2(18)S.
|
12.0(26)S
|
This command was integrated into Cisco IOS Release 12.0(26)S.
|
Examples
The following is sample output from the show isis spf-log command with the optional ipv6 keyword:
Router# show isis ipv6 spf-log
When Duration Nodes Count Last trigger LSP Triggers
00:15:46 3124 40 1 milles.00-00 TLVCODE
00:15:24 3216 41 5 milles.00-00 TLVCODE NEWLSP
00:15:19 3096 41 1 deurze.00-00 TLVCODE
00:14:54 3004 41 2 milles.00-00 ATTACHFLAG LSPHEADER
00:14:49 3384 41 1 milles.00-01 TLVCODE
00:14:23 2932 41 3 milles.00-00 TLVCODE
00:05:18 3140 41 1 PERIODIC
00:03:54 3144 41 1 milles.01-00 TLVCODE
00:03:49 2908 41 1 milles.01-00 TLVCODE
00:03:28 3148 41 3 bakel.00-00 TLVCODE TLVCONTENT
00:03:15 3054 41 1 milles.00-00 TLVCODE
00:02:53 2958 41 1 mortel.00-00 TLVCODE
00:02:48 3632 41 2 milles.00-00 NEWADJ TLVCODE
00:02:23 2988 41 1 milles.00-01 TLVCODE
00:02:18 3016 41 1 gemert.00-00 TLVCODE
00:02:14 2932 41 1 bakel.00-00 TLVCONTENT
00:02:09 2988 41 2 bakel.00-00 TLVCONTENT
00:01:54 3228 41 1 milles.00-00 TLVCODE
00:01:38 3120 41 3 rips.03-00 TLVCONTENT
Table 97 describes the significant fields shown in the display.
Table 97 show isis spf-log Field Descriptions
Field
|
Description
|
When
|
How long ago (in hours: minutes: seconds) a full SPF calculation occurred. The last 20 occurrences are logged.
|
Duration
|
Number of milliseconds required to complete this SPF run. Elapsed time is wall clock time, not CPU time.
|
Nodes
|
Number of routers and pseudonodes (LANs) that make up the topology calculated in this SPF run.
|
Count
|
Number of events that triggered this SPF run. When there is a topology change, often multiple link-state packets (LSPs) are received in a short time. A router waits 5 seconds before running a full SPF run, so it can include all new information. This count denotes the number of events (such as receiving new LSPs) that occurred while the router was waiting its 5 seconds before running full SPF.
|
Last trigger LSP
|
Whenever a full SPF calculation is triggered by the arrival of a new LSP, the router stores the LSP ID. The LSP ID can provide a clue as to the source of routing instability in an area. If multiple LSPs are causing an SPF run, only the LSP ID of the last received LSP is remembered.
|
Triggers
|
A list of all reasons that triggered a full SPF calculation. For a list of possible triggers, see Table 29.
|
Table 98 lists possible triggers of a full SPF calculation.
Table 98 Possible Triggers of Full SPF Calculation
Trigger
|
Description
|
ATTACHFLAG
|
This router is now attached to the Level 2 backbone or it has just lost contact to the Level 2 backbone.
|
ADMINDIST
|
Another administrative distance was configured for the IS-IS process on this router.
|
AREASET
|
Set of learned area addresses in this area changed.
|
BACKUPOVFL
|
An IP prefix disappeared. The router knows there is another way to reach that prefix but has not stored that backup route. The only way to find the alternative route is through a full SPF run.
|
DBCHANGED
|
A clear isis * command was issued on this router.
|
IPBACKUP
|
An IP route disappeared, which was not learned via IS-IS, but via another protocol with better administrative distance. IS-IS will run a full SPF to install an IS-IS route for the disappeared IP prefix.
|
IPQUERY
|
A clear ip route command was issued on this router.
|
LSPEXPIRED
|
Some LSP in the link-state database (LSDB) has expired.
|
LSPHEADER
|
ATT/P/OL bits or is-type in an LSP header changed.
|
NEWADJ
|
This router has created a new adjacency to another router.
|
NEWAREA
|
A new area (via network entity title [NET]) was configured on this router.
|
NEWLEVEL
|
A new level (via is-type) was configured on this router.
|
NEWLSP
|
A new router or pseudonode appeared in the topology.
|
NEWMETRIC
|
A new metric was configured on an interface of this router.
|
NEWSYSID
|
A new system ID (via NET) was configured on this router.
|
PERIODIC
|
Typically, every 15 minutes a router runs a periodic full SPF calculation.
|
RTCLEARED
|
A clear clns route command was issued on this router.
|
TLVCODE
|
TLV code mismatch, indicating that different TLVs are included in the newest version of an LSP.
|
TLVCONTENT
|
TLV contents changed. This normally indicates that an adjacency somewhere in the area has come up or gone down. The "Last trigger LSP" column indicates where the instability may have occurred.
|
show isis topology
To display a list of all connected routers in all areas, use the show isis topology command in user EXEC or privileged EXEC mode.
show isis [process-tag] [ipv6 | *] topology
Syntax Description
process-tag
|
(Optional) A unique name among all International Organization for Standardization (ISO) router processes including IP and Connectionless Network Service (CLNS) router processes for a given router. If a process tag is specified, output is limited to the specified routing process. When "null" is specified for the process tag, output is displayed only for the router process that has no tag specified. If a process tag is not specified, output is displayed for all processes.
|
ipv6
|
(Optional) Displays Intermediate System-to-Intermediate System (IS-IS) IPv6 topology.
|
*
|
(Optional) Displays the topology of all address families.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
12.2(15)T
|
Support was added for IPv6.
|
12.2(18)S
|
This command was integrated into Cisco IOS Release 12.2(18)S.
|
12.0(26)S
|
This command was integrated into Cisco IOS Release 12.0(26)S.
|
12.0(29)S
|
The process-tag argument was added.
|
Usage Guidelines
Use the show isis topology EXEC command to verify the presence and connectivity between all routers in all areas.
Examples
The following example shows output from the show isis topology command using the optional ipv6 keyword. The command shown is used in a dual CLNS-IP network:
Router# show isis ipv6 topology
IS-IS IPv6 paths to level-1 routers
System Id Metric Next-Hop Interface SNPA
0000.0000.0009 10 0000.0000.0009 Tu529 *Tunnel*
0000.0000.0017 20 0000.0000.0009 Tu529 *Tunnel*
0000.0000.0053 30 0000.0000.0009 Tu529 *Tunnel*
0000.0000.0068 20 0000.0000.0009 Tu529 *Tunnel*
IS-IS paths to level-2 routers
System Id Metric Next-Hop Interface SNPA
0000.0000.0009 10 0000.0000.0009 Tu529 *Tunnel*
0000.0000.0017 20 0000.0000.0009 Tu529 *Tunnel*
0000.0000.0053 30 0000.0000.0009 Tu529 *Tunnel*
0000.0000.0068 20 0000.0000.0009 Tu529 *Tunnel*
IS-IS paths to level-1 routers
System Id Metric Next-Hop Interface SNPA
0000.0000.0003 10 0000.0000.0003 Et1 0000.0c03.6944
0000.0000.0053 10 0000.0000.0053 Et1 0060.3e58.ccdb
IS-IS paths to level-1 routers
System Id Metric Next-Hop Interface SNPA
0000.0000.0002 10 0000.0000.0002 Et2 0000.0c03.6bc5
0000.0000.0053 10 0000.0000.0053 Et2 0060.3e58.ccde
Table 99 describes the significant fields shown in the display.
Table 99 show isis topology Field Descriptions
Field
|
Description
|
Tag
|
Identifies the routing process.
|
System Id
|
Six-byte value that identifies a system in an area.
|
Metric
|
IS-IS metric for the cost of the adjacency between the originating router and the advertised neighbor, or the metric of the cost to get from the advertising router to the advertised destination (which can be an IP address, an end system [ES], or a CLNS prefix).
|
Next-Hop
|
The address of the next hop router.
|
Interface
|
Interface from which the system was learned.
|
SNPA
|
Subnetwork point of attachment. This is the data-link address.
|
show key chain
To display authentication key information, use the show key chain command in EXEC mode.
show key chain [name-of-chain]
Syntax Description
name-of-chain
|
(Optional) Name of the key chain to display, as named in the key chain command.
|
Defaults
Information about all key chains is displayed.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
Examples
The following is sample output from the show key chain command:
accept lifetime (always valid) - (always valid) [valid now]
send lifetime (always valid) - (always valid) [valid now]
accept lifetime (00:00:00 Dec 5 1995) - (23:59:59 Dec 5 1995)
send lifetime (06:00:00 Dec 5 1995) - (18:00:00 Dec 5 1995)
Related Commands
Command
|
Description
|
accept-lifetime
|
Sets the time period during which the authentication key on a key chain is received as valid.
|
key
|
Identifies an authentication key on a key chain.
|
key chain
|
Enables authentication for routing protocols.
|
key-string (authentication)
|
Specifies the authentication string for a key.
|
send-lifetime
|
Sets the time period during which an authentication key on a key chain is valid to be sent.
|
show route-map
To display static and dynamic route maps, use the show route-map command in privileged EXEC mode.
show route-map [map-name | dynamic [dynamic-map-name | application [application-name]] |
all] [detailed]
Syntax Description
map-name
|
(Optional) Name of a specific route map.
|
dynamic
|
(Optional) Displays dynamic route map information.
|
dynamic-map-name
|
(Optional) Name of a specific dynamic route map.
|
application
|
(Optional) Displays dynamic route maps based on applications.
|
application-name
|
(Optional) Name of a specific application.
|
all
|
(Optional) Displays all static and dynamic route maps.
|
detailed
|
(Optional) Displays the details of the access control lists (ACLs) that have been used in the match clauses for dynamic route maps.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.0(22)S
|
An additional counter collect policy routing statistic was integrated in Cisco IOS Release 12.0(22)S.
|
12.2(15)T
|
An additional counter collect policy routing statistic was integrated in Cisco IOS Release 12.2(15)T.
|
12.3(7)T
|
The dynamic, application, and all keywords were added.
|
12.0(28)S
|
The support for recursive next-hop clause was added.
|
12.3(14)T
|
The support for recursive next-hop clause was integrated into Cisco IOS Release 12.3(14)T. Support for the map display extension functionality was added: The detailed keyword was added.
|
Usage Guidelines
For Cisco IO Releases 12.3(14)T and later releases, you can display the ACL-specific information that pertains to the route map in the same display without having to execute a show route-map command to display each ACL that is associated with the route map.
Examples
show route-map Command with No Keywords Specified Example
The following is sample output from the show route-map command:
route-map sid, permit, sequence 10
route-map sid, permit, sequence 20
Policy routing matches: 0 packets; 0 bytes
The following example shows Multiprotocol Label Switching (MPLS)-related route map information:
route-map OUT, permit, sequence 10
ip address (access-lists): 1
Policy routing matches: 0 packets, 0 bytes
route-map IN, permit, sequence 10
ip address (access-lists): 2
Policy routing matches: 0 packets, 0 bytes
Table 79 describes the significant fields shown in the display.
Table 100 show route-map Field Descriptions
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.
|
Policy routing matches
|
Number of packets and bytes that have been filtered by policy routing.
|
show route-map Command with Dynamic Route Map Specified Example
The following is sample output from the show route-map command when entered with the dynamic keyword:
Router# show route-map dynamic
route-map AAA-02/06/04-14:01:26.619-1-AppSpec, permit, sequence 0, identifier 1137954548
ip address (access-lists): PBR#1 PBR#2
Policy routing matches: 0 packets, 0 bytes
route-map AAA-02/06/04-14:01:26.619-1-AppSpec, permit, sequence 1, identifier 1137956424
ip address (access-lists): PBR#3 PBR#4
Policy routing matches: 0 packets, 0 bytes
route-map AAA-02/06/04-14:01:26.619-1-AppSpec, permit, sequence 2, identifier 1124436704
ip address (access-lists): PBR#5 PBR#6
Policy routing matches: 0 packets, 0 bytes
Current active dynamic routemaps = 1
The following is sample output from the show route-map command when entered with the dynamic and application keywords:
Router# show route-map dynamic application
Number of active routemaps = 1
When you specify an application name, only dynamic routes for that application are shown. The following is sample output from the show route-map command when entered with the dynamic and application keywords and the AAA application name:
Router# show route-map dynamic application AAA
Number of active rmaps = 2
AAA-02/06/04-14:01:26.619-1-AppSpec
AAA-02/06/04-14:34:09.735-2-AppSpec
Router# show route-map dynamic AAA-02/06/04-14:34:09.735-2-AppSpec
route-map AAA-02/06/04-14:34:09.735-2-AppSpec, permit, sequence 0, identifier 1128046100
ip address (access-lists): PBR#7 PBR#8
Policy routing matches: 0 packets, 0 bytes
route-map AAA-02/06/04-14:34:09.735-2-AppSpec, permit, sequence 1, identifier 1141277624
ip address (access-lists): PBR#9 PBR#10
Policy routing matches: 0 packets, 0 bytes
route-map AAA-02/06/04-14:34:09.735-2-AppSpec, permit, sequence 2, identifier 1141279420
ip address (access-lists): PBR#11 PBR#12
Policy routing matches: 0 packets, 0 bytes
Current active dynamic routemaps = 2
show route-map Command with Detailed ACL Information for Route Maps Specified Example
The following is sample output from the show route-map command with the dynamic and detailed keywords entered:
Router# show route-map dynamic detailed
route-map AAA-01/20/04-22:03:10.799-1-AppSpec, permit, sequence 1, identifier 29675368
ip address (access-lists):
Extended IP access list PBR#3
1 permit icmp 0.0.16.12 1.204.167.240 8.1.1.0 0.0.0.255 syn dscp af12 log-input fragments
Extended IP access list PBR#4
1 permit icmp 0.0.16.12 1.204.167.240 8.1.1.0 0.0.0.255 syn dscp af12 log-input fragments
Policy routing matches: 0 packets, 0 bytes
Related Commands
Command
|
Description
|
redistribute (IP)
|
Redistributes routes from one routing domain into another routing domain.
|
route-map (IP)
|
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing.
|
snmp-server enable traps ospf cisco-specific errors config-error
To enable Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF) nonvirtual interface mismatch errors, use the snmp-server enable traps ospf cisco-specific errors config-error command in global configuration mode. To disable OSPF nonvirtual interface mismatch error SNMP notifications, use the no form of this command.
snmp-server enable traps ospf cisco-specific errors config-error
no snmp-server enable traps ospf cisco-specific errors config-error
Syntax Description
This command has no keywords or arguments.
Defaults
This command is disabled by default.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.3(5)
|
This command was introduced.
|
12.3(4)T
|
This command was integrated into Cisco IOS Release 12.3(4)T.
|
12.0(26)S
|
This command was integrated into Cisco IOS Release 12.0(26)S.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S.
|
Usage Guidelines
To enable the cospfShamLinkConfigError trap, you must first enter the snmp-server enable traps ospf cisco-specific errors config-error command in global configuration mode. The snmp-server enable traps ospf cisco-specific errors config-error command enables the cospfConfigError trap, so that both traps can be generated at the same place and maintain consistency with a similar case for configuration errors across virtual links.
If you try to enable the cospfShamLinkConfigError trap before configuring the cospfospfConfigError trap you will receive an error message stating you must first configure the cospfConfigError trap.
Examples
The following example enables the router to send nonvirtual interface mismatch error notifications to the host at the address myhost.cisco.com using the community string defined as public:
Router(config)# snmp-server enable traps ospf cisco-specific errors config-error
Router(config)# snmp-server host myhost.cisco.com informs version 2c public
Related Commands
Command
|
Description
|
snmp-server enable traps ospf cisco-specific retransmit
|
Enables SNMP notifications for OSPF retransmission errors.
|
snmp-server enable traps ospf cisco-specific errors shamlink
|
Enables SNMP notifications for OSPF sham-link errors.
|
snmp-server enable traps ospf cisco-specific state-change
|
Enables SNMP notifications for OSPF transition state changes.
|
snmp-server enable traps ospf cisco-specific errors shamlink
To enable Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF) sham-link errors, use the snmp-server enable traps ospf cisco-specific errors shamlink command in global configuration mode. To disable OSPF sham-link error SNMP notifications, use the no form of this command.
snmp-server enable traps ospf cisco-specific errors shamlink [authentication [bad-packet
[config] | config [bad-packet]]
no snmp-server enable traps ospf cisco-specific errors shamlink [authentication [bad-packet
[config] | config [bad-packet]]
Syntax Description
authentication
|
(Optional) Enables SNMP notifications only for authentication failures on OSPF sham-link interfaces.
|
bad-packet
|
(Optional) Enables SNMP notifications only for packet parsing failures on OSPF sham-link interfaces.
|
config
|
(Optional) Enables SNMP notifications only for configuration mismatch errors on OSPF sham-link interfaces.
|
Defaults
This command is disabled by default.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.0(30)S
|
This command was introduced.
|
12.3(14)T
|
This command was integrated into Cisco IOS Release 12.3(14)T.
|
Usage Guidelines
To enable the cospfShamLinkConfigError trap, you must first enter the snmp-server enable traps ospf cisco-specific errors config-error command in global configuration mode. The snmp-server enable traps ospf cisco-specific errors config-error command enables the cospfConfigError trap, so that both traps can be generated at the same place and maintain consistency with a similar case for configuration errors across virtual links.
If you try to enable the cospfShamLinkConfigError trap before configuring the cospfospfConfigError trap you will receive an error message stating you must first configure the cospfConfigError trap.
Examples
The following example enables the router to send OSPF sham-link error notifications to the host at the address myhost.cisco.com using the community string defined as public:
Router(config)# snmp-server enable traps ospf cisco-specific errors config-error
Router(config)# snmp-server enable traps ospf cisco-specific errors shamlink
Router(config)# nmp-server host myhost.cisco.com informs version 2c public
Related Commands
Command
|
Description
|
snmp-server enable traps ospf cisco-specific errors config-error
|
Enables SNMP notifications for OSPF nonvirtual interface mismatch errors.
|
snmp-server enable traps ospf cisco-specific retransmit
|
Enables SNMP notifications for OSPF retransmission errors.
|
snmp-server enable traps ospf cisco-specific state-change
|
Enables SNMP notifications for OSPF transition state changes.
|
snmp-server enable traps ospf cisco-specific retransmit
To enable Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF) retransmission errors, use the snmp-server enable traps ospf cisco-specific retransmit command in global configuration mode. To disable OSPF sham-link error SNMP notifications, use the no form of this command.
snmp-server enable traps ospf cisco-specific retransmit [packets [shamlink | virt-packets] |
shamlink [packets | virt-packets] | virt-packets [shamlink]]
no snmp-server enable traps ospf cisco-specific retransmit [packets [shamlink | virt-packets] |
shamlink [packets | virt-packets] | virt-packets [shamlink]]
Syntax Description
packets
|
(Optional) Enables SNMP notifications only for packet retransmissions on nonvirtual interfaces.
|
shamlink
|
(Optional) Enables SNMP notifications only for sham-link retransmission notifications.
|
virt-packets
|
(Optional) Enables SNMP notifications only for packet retransmissions on virtual interfaces.
|
Defaults
This command is disabled by default.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.3(5)
|
This command was introduced.
|
12.3(4)T
|
This command was integrated into Cisco IOS Release 12.3(4)T.
|
12.0(26)S
|
This command was integrated into Cisco IOS Release 12.0(26)S.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S.
|
12.0(30)S
|
The shamlink keyword and related options were added.
|
12.3(14)T
|
Support was added for the shamlink keyword and related options.
|
Examples
The following example enables the router to send OSPF sham-link retransmission notifications:
Router(config)# snmp-server enable traps ospf cisco-specific retransmit shamlink
Related Commands
Command
|
Description
|
snmp-server enable traps ospf cisco-specific errors config-error
|
Enables SNMP notifications for OSPF nonvirtual interface mismatch errors.
|
snmp-server enable traps ospf cisco-specific errors shamlink
|
Enables SNMP notifications for OSPF sham-link errors.
|
snmp-server enable traps ospf cisco-specific state-change
|
Enables SNMP notifications for OSPF transition state changes.
|
snmp-server enable traps ospf cisco-specific state-change
To enable Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF) transition state changes, use the snmp-server enable traps ospf cisco-specific state-change command in global configuration mode. To disable OSPF transition state change SNMP notifications, use the no form of this command.
snmp-server enable traps ospf cisco-specific state-change [nssa-trans-change | shamlink
[interface | interface-old | neighbor]]
no snmp-server enable traps ospf cisco-specific state-change [nssa-trans-change | shamlink
[interface | interface-old | neighbor