![]() |
Cisco IOS IP Routing: OSPF Command Reference
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
OSPF Commands show ip ospf through T
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Contents
OSPF Commands: show ip ospf through T show ip ospfTo display general information about Open Shortest Path First (OSPF) routing processes, use the showipospf command in user EXEC or privileged EXEC mode. Command History
ExamplesThe following is sample output from the showipospf command when entered without a specific OSPF process ID:
Router# show ip ospf
Routing Process "ospf 201" with ID 10.0.0.1 and Domain ID 10.20.0.1
Supports only single TOS(TOS0) routes
Supports opaque LSA
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
Area BACKBONE(0)
Number of interfaces in this area is 2
Area has message digest authentication
SPF algorithm executed 4 times
Area ranges are
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 DoNotAge LSA 0
Flood list length 0
Area 172.16.26.0
Number of interfaces in this area is 0
Area has no authentication
SPF algorithm executed 1 times
Area ranges are
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
Number of DoNotAge LSA 0
Flood list length 0
Cisco IOS Release 12.2(18)SXE, 12.0(31)S, and 12.4(4)TThe following is sample output from the showipospfcommand to verify that the BFD feature has been enabled for OSPF process 123. The relevant command output is shown in bold in the output. Router# show ip ospf Routing Process "ospf 123" with ID 172.16.10.1 Supports only single TOS(TOS0) routes Supports opaque LSA 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 Incremental-SPF disabled 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 0x000000 Number of opaque AS LSA 0. Checksum Sum 0x000000 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 BFD is enabled Area BACKBONE(0) Number of interfaces in this area is 2 Area has no authentication SPF algorithm last executed 00:00:03.708 ago SPF algorithm executed 27 times Area ranges are Number of LSA 3. Checksum Sum 0x00AEF1 Number of opaque link LSA 0. Checksum Sum 0x000000 Number of DCbitless LSA 0 Number of indication LSA 0 Number of DoNotAge LSA 0 Flood list length 0 The table below describes the significant fields shown in the display.
The following is an excerpt of output from the showipospf command when the OSPF Forwarding Address Suppression in Type-5 LSAs feature is configured:
Router# show ip ospf
.
.
.
Area 2
Number of interfaces in this area is 4
It is a NSSA area
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 opaque LSA
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
Incremental-SPF disabled
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
The table below describes the significant fields shown in the display.
The following is sample output from the showipospf command. In this example, the user had configured the redistributionmaximum-prefix command to set a limit of 2000 redistributed routes. SPF throttling was configured with the timersthrottlespf command.
Router# show ip ospf 1
Routing Process "ospf 1" with ID 10.0.0.1
Supports only single TOS(TOS0) routes
Supports opaque LSA
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
The table below describes the significant fields shown in the display.
The following is sample output from the showipospf command. In this example, the user had configured LSA throttling, and those lines of output are displayed in bold. Router# show ip ospf 1 Routing Process "ospf 4" with ID 10.10.24.4 Supports only single TOS(TOS0) routes Supports opaque LSA 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 Incremental-SPF disabled 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 Area 24 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 Area ranges are 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 Number of DoNotAge LSA 0 Flood list length 0 The following is sample showipospfcommand. In this example, the user had configured the redistributionmaximum-prefix command to set a limit of 2000 redistributed routes. SPF throttling was configured with the timersthrottlespf command.
Router# show ip ospf 1
Routing Process "ospf 1" with ID 192.168.0.0
Supports only single TOS(TOS0) routes
Supports opaque LSA
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
The table below describes the significant fields shown in the display.
The following is sample output from the showipospf command. In this example, the user had configured LSA throttling, and those lines of output are displayed in bold. Router# show ip ospf 1 Routing Process "ospf 4" with ID 10.10.24.4 Supports only single TOS(TOS0) routes Supports opaque LSA 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 Incremental-SPF disabled 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 Area 24 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 Area ranges are 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 Number of DoNotAge LSA 0 Flood list length 0 show ip ospf border-routersTo display the internal Open Shortest Path First (OSPF) routing table entries to an Area Border Router (ABR) and Autonomous System Boundary Router (ASBR), use the showipospfborder-routers command in privileged EXEC mode. Command History
ExamplesThe following is sample output from the showipospfborder-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
The table below describes the significant fields shown in the display.
show ip ospf databaseTo display lists of information related to the Open Shortest Path First (OSPF) database for a specific router, use the showipospfdatabase command in EXEC mode.
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
Command HistoryUsage GuidelinesThe various forms of this command deliver information about different OSPF link state advertisements. ExamplesThe following is sample output from the showipospfdatabase 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
The table below describes the significant fields shown in the display.
The following is sample output from the showipospfdatabasecommand with the asbr-summarykeyword:
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)
LS age: 1463
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
LS Seq Number: 80000072
Checksum: 0x3548
Length: 28
Network Mask: 0.0.0.0 TOS: 0 Metric: 1
The table below describes the significant fields shown in the display.
The following is sample output from the showipospfdatabasecommand with the externalkeyword:
Router# show ip ospf database external
OSPF Router with id(192.168.239.66) (Autonomous system 300)
Displaying AS External Link States
LS age: 280
Options: (No TOS-capability)
LS Type: AS External Link
Link State ID: 10.105.0.0 (External Network Number)
Advertising Router: 172.16.70.6
LS Seq Number: 80000AFD
Checksum: 0xC3A
Length: 36
Network Mask: 255.255.0.0
Metric Type: 2 (Larger than any link state path)
TOS: 0
Metric: 1
Forward Address: 0.0.0.0
External Route Tag: 0
The table below describes the significant fields shown in the display.
The following is sample output from the showipospfdatabasecommand with the networkkeyword:
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)
LS age: 1367
Options: (No TOS-capability)
LS Type: Network Links
Link State ID: 172.16.1.3 (address of Designated Router)
Advertising Router: 192.168.239.66
LS Seq Number: 800000E7
Checksum: 0x1229
Length: 52
Network Mask: 255.255.255.0
Attached Router: 192.168.239.66
Attached Router: 172.16.241.5
Attached Router: 172.16.1.1
Attached Router: 172.16.54.5
Attached Router: 172.16.1.5
The table below describes the significant fields shown in the display.
The following is sample output from the showipospfdatabasecommand with the routerkeyword:
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)
LS age: 1176
Options: (No TOS-capability)
LS Type: Router Links
Link State ID: 172.16.21.6
Advertising Router: 172.16.21.6
LS Seq Number: 80002CF6
Checksum: 0x73B7
Length: 120
AS Boundary Router
155 Number of Links: 8
Link connected to: another Router (point-to-point)
(link ID) Neighboring Router ID: 172.16.21.5
(Link Data) Router Interface address: 172.16.21.6
Number of TOS metrics: 0
TOS 0 Metrics: 2
The table below describes the significant fields shown in the display.
The following is sample output from showipospfdatabasecommand with the summarykeyword:
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)
LS age: 1401
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
LS Seq Number: 80000072
Checksum: 0x84FF
Length: 28
Network Mask: 255.255.255.0 TOS: 0 Metric: 1
The table below describes the significant fields shown in the display.
The following is sample output from showipospfdatabasecommand with the database-summarykeyword:
Router# show ip ospf database database-summary
OSPF Router with ID (10.0.0.1) (Process ID 1)
Area 0 database summary
LSA Type Count Delete Maxage
Router 3 0 0
Network 0 0 0
Summary Net 0 0 0
Summary ASBR 0 0 0
Type-7 Ext 0 0 0
Self-originated Type-7 0
Opaque Link 0 0 0
Opaque Area 0 0 0
Subtotal 3 0 0
Process 1 database summary
LSA Type Count Delete Maxage
Router 3 0 0
Network 0 0 0
Summary Net 0 0 0
Summary ASBR 0 0 0
Type-7 Ext 0 0 0
Opaque Link 0 0 0
Opaque Area 0 0 0
Type-5 Ext 0 0 0
Self-originated Type-5 200
Opaque AS 0 0 0
Total 203 0 0
The table below describes the significant fields shown in the display.
show ip ospf eventsTo display the IP Open Shortest Path First (OSPF) events information, use the show ip ospf events command in user EXEC or privileged EXEC mode. Syntax Description
ExamplesThe following is sample output from the show ip ospf eventscommand. The fields are self-explanatory. Router# show ip ospf events OSPF Router with ID (4.4.4.4) (Process ID 1) 1 Jan 22 01:51:03.090: DB free: 1.1.1.10x6CF250 103 2 Jan 22 01:51:03.090: delete MAXAGE lsa: 0x666CF2500x666CF250 3 Jan 22 01:50:56.086: DB free: 1.1.1.10x6025D4 103 4 Jan 22 01:50:56.086: DB free: 1.1.1.10x6D59A0 103 5 Jan 22 01:50:56.082: Insert MAXAGE lsa: 0x666D59A01.1.1.1 6 Jan 22 01:50:55.590: Timer Exp: if_ack_delayed0x64782774 7 Jan 22 01:50:55.590: Timer Exp: if_ack_delayed0x64786CB4 8 Jan 22 01:50:55.586: Timer Exp: if_ack_delayed0x647CD1A8 9 Jan 22 01:50:55.586: Timer Exp: if_ack_delayed0x647C8134 10 Jan 22 01:50:53.586: Insert MAXAGE lsa: 0x666025D41.1.1.1 11 Jan 22 01:50:53.586: Rcv Changed Type-3 LSA, LSID 1.1.1.1, Adv-Rtr 3.3.3.3, Seq# 80000002, Age 3600, Area 1 12 Jan 22 01:50:53.586: Insert MAXAGE lsa: 0x666D59A01.1.1.1 13 Jan 22 01:50:53.586: Generate Changed Type-3 LSA, LSID 1.1.1.1, Seq# 80000002, Age 3600, Area 0 14 Jan 22 01:50:53.290: End of SPF, Topo Base, SPF time 4ms, next wait-interval 200ms 15 Jan 22 01:50:53.290: Generic: ospf_external_route_sync0x1 16 Jan 22 01:50:53.290: Generic: ospf_external_route_sync0x0 17 Jan 22 01:50:53.290: Generic: ospf_external_route_sync0x0 18 Jan 22 01:50:53.290: Starting External processing, Topo Base in area 1 19 Jan 22 01:50:53.290: Starting External processing, Topo Base in area 0 20 Jan 22 01:50:53.286: Starting External processing, Topo Base 21 Jan 22 01:50:53.286: Generic: ospf_inter_route_sync0x0 22 Jan 22 01:50:53.286: Starting summary processing, Topo Base, Area 0 23 Jan 22 01:50:53.286: Generic: ospf_inter_route_sync0x1 24 Jan 22 01:50:53.286: Generic: post_spf_intra0x0 25 Jan 22 01:50:53.286: Generic: ospf_intra_route_sync0x1 26 Jan 22 01:50:53.286: Generic: update_rtr_route0x1 27 Jan 22 01:50:53.286: Generic: update_rtr_route0x1 28 Jan 22 01:50:53.286: Generic: update_rtr_route0x1 29 Jan 22 01:50:53.286: Starting Intra-Area SPF, Topo Base, Area 1, spf_type Full 30 Jan 22 01:50:53.286: Starting SPF, Topo Base, wait-interval 200ms 31 Jan 22 01:50:53.118: Rcv New Type-3 LSA, LSID 1.1.1.1, Adv-Rtr 3.3.3.3, Seq# 80000001, Age 1, Area 1 32 Jan 22 01:50:53.118: DB add: 1.1.1.10x6025D4 103 33 Jan 22 01:50:53.090: Insert MAXAGE lsa: 0x666CF2501.1.1.1 34 Jan 22 01:50:53.090: Rcv Changed Type-3 LSA, LSID 1.1.1.1, Adv-Rtr 3.3.3.3, Seq# 80000002, Age 3600, Area 0 35 Jan 22 01:50:53.086: Rcv Changed Type-1 LSA, LSID 1.1.1.1, Adv-Rtr 1.1.1.1, Seq# 80000008, Age 2, Area 1 36 Jan 22 01:50:53.086: Schedule SPF, Topo Base, Area 1, spf-type Full, Change in LSA Type R, LSID 1.1.1.1, Adv-Rtr 1.1.1.1 37 Jan 22 01:50:46.310: Timer Exp: exfaddr0x0 38 Jan 22 01:50:16.310: Timer Exp: exfaddr0x0 show ip ospf fast-rerouteTo display information for an Open Shortest Path First (OSPF) per-prefix loop-free alternate (LFA) fast reroute (FRR) configuration, use the show ip ospf fast-reroute command in privileged EXEC mode. Syntax Description
Usage GuidelinesUse the show ip ospf fast-reroute command to display information on the current tiebreaker policy. Use the prefix-summary keyword to display the number of prefixes per area, per priority, and how many that, in absolute numbers and in percentages, have repair paths. Use the remote-lfa tunnels keyword to display information about tunnel interfaces created by remote LFA FRR using the fast-reroute per-prefix remote-lfa tunnel command. ExamplesThe following example displays summary information about LFA FRR status, including the current tiebreaker policy:
Router# show ip ospf fast-reroute
OSPF Router with ID (192.1.1.1) (Process ID 1)
Loop-free Fast Reroute protected prefixes:
Area Topology name Priority
1 Base Low
172.69.69.66 Base High
AS external Base Low
Repair path selection policy tiebreaks:
23 srlg
34 lowest-metric
67 primary-path (required)
256 load-sharing
Last SPF calculation started 00:00:11 ago and was running for 20 ms.
The table below describes the significant fields shown in the display.
The following example displays information about prefixes that are protected by the OSPFv2 loop-free alternate FRR feature. It displays information on the number of prefixes by area and by priority (high or low) and how many are protected, that is, have repair paths configured.
Router# show ip ospf fast-reroute prefix-summary
OSPF Router with ID (192.1.1.1) (Process ID 1)
Base Topology (MTID 0)
Area 0:
Interface Protected Primary paths Protected paths Percent protected
All High Low All High Low All High Low
Loopback0 Yes 0 0 0 0 0 0 0% 0% 0%
Ethernet0/3 Yes 1 1 0 0 0 0 0% 0% 0%
Ethernet0/2 Yes 3 2 1 2 1 1 66% 50% 100%
Ethernet0/1 Yes 2 1 1 2 1 1 100% 100% 100%
Ethernet0/0 Yes 4 2 2 4 2 2 100% 100% 100%
Area total: 10 6 4 8 4 4 80% 66% 100%
Process total: 10 6 4 8 4 4 80% 66% 100%
The following example displays information about tunnel interfaces created by remote LFA FRR:
Router# show ip ospf fast-reroute remote-lfa tunnels
OSPF Router with ID (192.168.1.1) (Process ID 1)
Area with ID (0)
Base Topology (MTID 0)
Interface MPLS-Remote-Lfa3
Tunnel type: MPLS-LDP
Tailend router ID: 192.168.3.3
Termination IP address: 192.168.3.3
Outgoing interface: Ethernet0/0
First hop gateway: 192.168.14.4
Tunnel metric: 20
Protects:
192.168.12.2 Ethernet0/1, total metric 30
Related Commands
show ip ospf flood-listTo display a list of Open Shortest Path First (OSPF) link-state advertisements (LSAs) waiting to be flooded over an interface, use the showipospfflood-listcommand in EXEC mode. Command History
ExamplesThe following is sample output of the showipospfflood-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
The table below describes the significant fields shown in the display.
show ip ospf interfaceTo display interface information related to Open Shortest Path First (OSPF), use the show ip ospf interface command in user EXEC or privileged EXEC mode.
show
ip
ospf
interface
commandshow
ip
[ospf]
[process-id]
interface
[type number]
[brief]
[multicast]
[topology {topology-name | base}]
Syntax Description
Command History
ExamplesThe following is sample output from the show ip ospf interface command when Ethernet interface 0/0 is specified. It shows that LFA and FRR is enabled on the interface and that it can be both a protected and a protecting interface.
Router# show ip ospf interface ethernet 0/0
Ethernet0/0 is up, line protocol is up
Internet Address 192.168.254.202/24, Area 0
Process ID 1, Router ID 192.168.99.1, Network Type BROADCAST, Cost: 10
Topology-MTID Cost Disabled Shutdown Topology Name
0 10 no no Base
Transmit Delay is 1 sec, State DR, Priority 1
Designated Router (ID) 192.168.99.1, Interface address 192.168.254.202
Backup Designated router (ID) 192.168.254.10, Interface address 192.168.254.10
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
oob-resync timeout 40
Hello due in 00:00:05
Supports Link-local Signaling (LLS)
Cisco NSF helper support enabled
IETF NSF helper support enabled
Can be protected by per-prefix Loop-free FastReroute
Can be used for per-prefix Loop-free FastReroute repair paths
Index 1/1, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 1, maximum is 1
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 192.168.254.10 (Backup Designated Router)
Suppress hello for 0 neighbor(s)
Cisco IOS Release 12.2(33)SRBThe following sample output from the show ip ospf interface brief topology VOICE command shows a summary of information, including a confirmation that the Multitopology Routing (MTR) VOICE topology is configured in the interface configuration:
Router# show ip ospf interface brief topology VOICE
VOICE Topology (MTID 10)
Interface PID Area IP Address/Mask Cost State Nbrs F/C
Lo0 1 0 10.0.0.2/32 1 LOOP 0/0
Se2/0 1 0 10.1.0.2/30 10 P2P 1/1
The following sample output from the show ip ospf interface brief topology VOICE command displays details of the MTR VOICE topology for the interface. When the command is entered without the brief keyword, more information is displayed.
Router# show ip ospf interface topology VOICE
VOICE Topology (MTID 10)
Loopback0 is up, line protocol is up
Internet Address 10.0.0.2/32, Area 0
Process ID 1, Router ID 10.0.0.2, Network Type LOOPBACK
Topology-MTID Cost Disabled Shutdown Topology Name
10 1 no no VOICE
Loopback interface is treated as a stub Host Serial2/0 is up, line protocol is up
Internet Address 10.1.0.2/30, Area 0
Process ID 1, Router ID 10.0.0.2, Network Type POINT_TO_POINT
Topology-MTID Cost Disabled Shutdown Topology Name
10 10 no no VOICE
Transmit Delay is 1 sec, State POINT_TO_POINT
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
oob-resync timeout 40
Hello due in 00:00:03
Supports Link-local Signaling (LLS)
Cisco NSF helper support enabled
IETF NSF helper support enabled
Index 1/1, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 1, maximum is 1
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 10.0.0.1
Suppress hello for 0 neighbor(s)
Cisco IOS Release 12.2(33)SRCThe following sample output from the show ip ospf interface command displays details about the configured Time-to-Live (TTL) limits:
Router# show ip ospf interface ethernet 0
.
.
.
Strict TTL checking enabled
! or a message similar to the following is displayed
Strict TTL checking enabled, up to 4 hops allowed
.
.
.
The table below describes the significant fields shown in the displays.
show ip ospf max-metricTo display IP Open Shortest Path First (OSPF) max-metric origination information, use the show ip ospf max-metric command in user EXEC or privileged EXEC mode. Command History
ExamplesThe following is sample output from the show ip ospf max-metriccommand. The fields are self-explanatory. Router# show ip ospf max-metric OSPF Router with ID (190.0.30.1) (Process ID 2) Base Topology (MTID 0)Start time: 3d12h, Time elapsed: 00:01:07.964 Originating router-LSAs with maximum metric Condition: always, State: active Advertise external-LSAs with metric 16711680 show ip ospf neighborTo display Open Shortest Path First (OSPF) neighbor information on a per-interface basis, use the showipospfneighbor command in privileged EXEC mode. Syntax Description
Command History
ExamplesThe following sample output from theshowipospfneighbor command shows a single line of summary information for each neighbor:
Router# show ip ospf neighbor
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
Options 2
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
Options 2
Dead timer due in 0:00:32
Link State retransmission due in 0:00:03
If you specify the interface along with the neighbor ID, the 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
Options 2
Dead timer due in 0:00:37
Link State retransmission due in 0:00:04
You can also specify the interface without the neighbor ID to show all neighbors on the specified interface, as in the following sample display:
Router# show ip ospf neighbor fddi 0
ID Pri State Dead Time Address Interface
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 theshowipospfneighbordetail 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
Options is 0x42
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
The table below describes the significant fields shown in the displays.
Cisco IOS Release 12.2(33)SRCThe following is sample output from theshowipospfneighbor command showing a single line of summary information for each neighbor. If one OSPF neighbor has enabled TTL security, the other side of the connection will show the neighbor in the INIT state.
Router# show ip ospf neighbor
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
172.16.1.201 1 INIT/DROTHER 00.00.35 10.1.1.201 Ethernet0/0
The following sample output from the show ip ospf neighbor command shows the network from the neighbor's point of view:
Router# show ip ospf neighbor 192.0.2.1 fast-reroute
OSPF Router with ID (192.1.1.1) (Process ID 1)
Area with ID (0)
Neighbor with Router ID 192.0.2.1:
Reachable over:
Ethernet0/0, IP address 192.0.2.1, cost 10
SPF was executed 1 times, distance to computing router 10
Router distance table:
192.1.1.1 i [10]
192.0.2.1 i [0]
192.3.3.3 i [10]
192.4.4.4 i [20]
192.5.5.5 i [20]
Network LSA distance table:
192.2.12.2 i [10]
192.2.13.3 i [20]
192.2.14.4 i [20]
192.2.15.5 i [20]
show ip ospf nsfTo display IP Open Shortest Path First (OSPF) nonstop forwarding (NSF) state information, use the show ip ospf nsf command in user EXEC or privileged EXEC mode. Command History
ExamplesThe following is sample output from the show ip ospf nsfcommand. The fields are self-explanatory. Router# show ip ospf nsf Routing Process "ospf 2" Non-Stop Forwarding enabled IETF NSF helper support enabled Cisco NSF helper support enabled OSPF restart state is NO_RESTART Handle 1786466308, Router ID 192.0.2.1, checkpoint Router ID 0.0.0.0 Config wait timer interval 10, timer not running Dbase wait timer interval 120, timer not running show ip ospf nsrTo display IP Open Shortest Path First (OSPF) nonstop routing (NSR) status information, use the show ip ospf nsr command in privileged EXEC mode. Syntax Description
ExamplesThe following sample output from the show ip ospf nsrcommand shows that OSPF on the standby RP is fully synchronized and ready to continue operation if the active RP fails or if a manual switchover is performed. NSR is configured and enabled for the "ospf 1" OSPF routing process. The fields are self-explanatory. Router# show ip ospf 1 nsr Active RP Operating in duplex mode Redundancy state: ACTIVE Peer redundancy state: STANDBY HOT Checkpoint peer ready Checkpoint messages enabled ISSU negotiation complete ISSU versions compatible Routing Process "ospf 1" with ID 10.1.1.100 NSR configured Checkpoint message sequence number: 6360 Standby synchronization state: synchronized Bulk sync operations: 1 Next sync check time: 18:48:27.097 PST Fri Dec 10 2010 LSA Count: 3301, Checksum Sum 0x06750217 show ip ospf request-listTo display a list of all link-state advertisements (LSAs) requested by a router, use the showipospfrequest-listcommand in EXEC mode. Syntax Description
Command History
Usage GuidelinesThe information displayed by the showipospfrequest-listcommand is useful in debugging Open Shortest Path First (OSPF) routing operations. ExamplesThe following is sample output from the showipospfrequest-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
The table below describes the significant fields shown in the displays. show ip ospf retransmission-listTo display a list of all link-state advertisements (LSAs) waiting to be re-sent, use the showipospfretransmission-listcommand in EXEC mode. Syntax Description
Command History
Usage GuidelinesThe information displayed by the showipospfretransmission-listcommand is useful in debugging Open Shortest Path First (OSPF) routing operations. ExamplesThe following is sample output from the showipospfretransmission-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
The table below describes the significant fields shown in the displays. show ip ospf ribTo display information for the Open Shortest Path First (OSPF) local Routing Information Base (RIB) or locally redistributed routes, use the showipospfribcommand in privileged EXEC mode. Syntax Description
Command History
Usage GuidelinesIf the network-prefix and network-mask arguments are both entered, only the route that matches the network prefix and IP address mask is displayed. If only the network-prefix argument is entered, a longest prefix lookup is performed and the matching route is displayed. ExamplesThe following example displays information about locally redistributed routes:
Router# show ip ospf 1 rib redistribution 192.168.240.0
OSPF Redistribution for Process 1
192.168.240/20, metric 0, tag 0, from OSPF Router 130
Attributes 0x1000220, event 1
via Ethernet0/0
OSPF Redistribution Process 130
The table below describes the significant fields shown in the display.
The following example displays information about primary paths and the LFA and FRR repair paths protecting them:
Router# show ip ospf 1 rib
OSPF Router with ID (192.1.1.1) (Process ID 1)
Base Topology (MTID 0)
OSPF local RIB
Codes: * - Best, > - Installed in global RIB
* 192.168.15.0/24, Intra, cost 10, area 0, Connected
via 192.168.15.1, Ethernet0/3
*> 192.168.23.0/24, Intra, cost 20, area 0
via 192.168.12.2, Ethernet0/0
repair path via 192.168.13.3, Ethernet0/1, cost 20
via 192.168.13.3, Ethernet0/1
repair path via 192.168.12.2, Ethernet0/0, cost 20
*> 192.168.26.0/24, Intra, cost 20, area 0
via 192.168.12.2, Ethernet0/0
repair path via 192.168.13.3, Ethernet0/1, cost 30
*> 192.168.46.0/24, Intra, cost 30, area 0
via 192.168.12.2, Ethernet0/0
repair path via 192.168.13.3, Ethernet0/1, cost 40
Related Commands
show ip ospf sham-linksTo 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. Command History
Usage GuidelinesUse this command to display Open Shortest Path First (OSPF) information about the sham-links configured on a PE router. ExamplesThe 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
Run as demand circuit
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
Hello due in 00:00:09
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 statisticsTo display Open Shortest Path First (OSPF) shortest path first (SPF) calculation statistics, use the showipospfstatisticscommand in user EXEC or privileged EXEC mode. Usage GuidelinesThe showipospfstatistics 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 showipospfstatistics command is recommended as the first troubleshooting step for link-state advertisement (LSA) flapping. ExamplesThe following is sample output from the showipospfstatisticscommand that shows a single line of information for each SPF calculation: Router# show ip ospf statistics OSPF process ID 200 ------------------------------------------ Area 0: SPF algorithm executed 10 times Area 200: SPF algorithm executed 8 times Summary OSPF SPF statistic SPF calculation time 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 The table below describes the significant fields shown in the display.
The following is sample output from the showipospfstatisticscommand 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 0 0 0 0 0 0 0 0 LSIDs processed R:4 N:1 Stub:5 SN:17 SA:1 X7:0 Change record R, LSIDs changed 1 Last 10 LSIDs: 2.0.0.202(R) The table below describes the significant fields shown in the display.
show ip ospf summary-addressTo display a list of all summary address redistribution information configured under an Open Shortest Path First (OSPF) process, use the showipospfsummary-addresscommand in EXEC mode. Command History
Usage GuidelinesThe process-id argument can be entered as a decimal number or as an IP address format. ExamplesThe following is sample output from the showipospfsummary-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
The table below describes the significant fields shown in the displays. show ip ospf timers rate-limitTo display all of the link-state advertisements (LSAs) in the rate limit queue, use the showipospftimersrate-limitcommand in privileged EXEC mode. Command History
ExamplesThe following is sample output from the showipospftimersrate-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
The table below describes the significant fields shown in the display. show ip ospf trafficTo display Open Shortest Path First (OSPF) traffic statistics, use the showipospftraffic command in user EXEC or privileged EXEC mode. Command DefaultWhen the showipospftraffic command is entered without any arguments, global OSPF traffic statistics are displayed, including queue statistics for each OSPF process, statistics for each interface, and per-OSPF process statistics. Command History
Usage GuidelinesYou can limit the displayed traffic statistics to those for a specific OSPF process by entering a value for the process-id argument, or you can limit output to traffic statistics for a specific interface associated with an OSPF process by entering values for the interface-type and interface-number arguments. To reset counters and clear statistics, use the clearipospftraffic command. Cisco IOS Release 12.0(28)SThe following is sample output from the show ip ospf traffic command.
Router# show ip ospf traffic
OSPF statistics:
Rcvd: 5300 total, 730 checksum errors
333 hello, 10 database desc, 3 link state req
24 link state updates, 13 link state acks
Sent: 264 total
222 hello, 12 database desc, 3 link state req
17 link state updates, 12 link state acks
OSPF Router with ID (10.0.1.2) (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
Interface statistics:
Interface Loopback0
OSPF packets received/sent
Invalid Hellos DB-des LS-req LS-upd LS-ack Total
Rx: 0 0 0 0 0 0 0
Tx: 0 0 0 0 0 0 0
OSPF header errors
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,
Authentication 0,
OSPF LSA errors
Type 0, Length 0, Data 0, Checksum 0,
Interface Serial3/0
OSPF packets received/sent
Invalid Hellos DB-des LS-req LS-upd LS-ack Total
Rx: 0 111 3 1 7 6 128
Tx: 0 111 4 1 12 5 133
OSPF header errors
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,
Authentication 0,
OSPF LSA errors
Type 0, Length 0, Data 0, Checksum 0,
Interface Serial2/0
OSPF packets received/sent
Invalid Hellos DB-des LS-req LS-upd LS-ack Total
Rx: 0 0 0 0 0 0 0
Tx: 0 0 0 0 0 0 0
OSPF header errors
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,
Authentication 0,
OSPF LSA errors
Type 0, Length 0, Data 0, Checksum 0,
Interface Ethernet0/0
OSPF packets received/sent
Invalid Hellos DB-des LS-req LS-upd LS-ack Total
Rx: 0 222 7 2 17 7 255
Tx: 0 111 8 2 5 7 133
OSPF header errors
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,
Authentication 0,
OSPF LSA errors
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
Sent: 266 total
222 hello, 12 database desc, 3 link state req
17 link state upds, 12 link state acks, 0 invalid
The table below describes the significant fields shown in the display.
Cisco IOS Release 12.2(33)SRCThe following is sample output from the show ip ospf traffic command. The output has been modified to include the number of packets dropped due a TTL security check. Router# show ip ospf traffic . . . OSPF header errors 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, Authentication 0, TTL Check Fail 2, . Cisco IOS Release 12.4(6)TThe following is sample output from the showipospftraffic command that displays the detailed traffic information for OSPF packets received and sent on each OSPF interface and OSPF process.
Router# show ip ospf traffic
OSPF statistics:
.
.
.
Interface Ethernet0/0.1
OSPF packets received/sent
Type Packets Bytes
RX Invalid 0 0
RX Hello 0 0
RX DB des 0 0
RX LS req 0 0
RX LS upd 0 0
RX LS ack 0 0
RX Total 0 0
TX Failed 0 0
TX Hello 16 1216
TX DB des 0 0
TX LS req 0 0
TX LS upd 0 0
TX LS ack 0 0
TX Total 16 1216
.
.
.
Interface Serial2/0
OSPF packets received/sent
Type Packets Bytes
RX Invalid 0 0
RX Hello 11 528
RX DB des 4 148
RX LS req 1 60
RX LS upd 3 216
RX LS ack 2 128
RX Total 21 1080
TX Failed 0 0
TX Hello 14 1104
TX DB des 3 252
TX LS req 1 56
TX LS upd 3 392
TX LS ack 2 128
TX Total 23 1932
.
.
.
Interface Ethernet0/0
OSPF packets received/sent
Type Packets Bytes
RX Invalid 0 0
RX Hello 13 620
RX DB des 3 116
RX LS req 1 36
RX LS upd 3 228
RX LS ack 4 216
RX Total 24 1216
TX Failed 0 0
TX Hello 17 1344
TX DB des 4 276
TX LS req 1 56
TX LS upd 7 656
TX LS ack 2 128
TX Total 31 2460
.
.
.
Summary traffic statistics for process ID 1:
OSPF packets received/sent
Type Packets Bytes
RX Invalid 0 0
RX Hello 24 1148
RX DB des 7 264
RX LS req 2 96
RX LS upd 6 444
RX LS ack 6 344
RX Total 45 2296
TX Failed 0 0
TX Hello 31 2448
TX DB des 7 528
TX LS req 2 112
TX LS upd 10 1048
TX LS ack 4 256
TX Total 54 4392
OSPF header errors
Length 0, Checksum 0, Version 0, Bad Source 13,
No Virtual Link 0, Area Mismatch 0, No Sham Link 0,
Self Originated 0, Duplicate ID 0, Hello 0,
MTU Mismatch 0, Nbr Ignored 0, LLS 0,
Authentication 0,
OSPF LSA errors
Type 0, Length 0, Data 0, Checksum 0,
To start collecting new statistics, reset the counters and clear the traffic statistics by entering the clearipospftraffic command as follows: Router# clear ip ospf traffic show ip ospf virtual-linksTo display parameters and the current state of Open Shortest Path First (OSPF) virtual links, use the showipospfvirtual-links command in EXEC mode. Command History
Usage GuidelinesThe information displayed by the showipospfvirtual-links command is useful in debugging OSPF routing operations. ExamplesThe following is sample output from the showipospfvirtual-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
Hello due in 0:00:08
Adjacency State FULL
The table below describes the significant fields shown in the display.
show ipv6 ospfTo display general information about Open Shortest Path First ( OSPF) routing processes, use the show ipv6 ospf command in user EXEC or privileged EXEC mode. Syntax Description
Command History
show ipv6 ospf Output ExampleThe following is sample output from the show ipv6 ospf command:
Router# show ipv6 ospf
Routing Process "ospfv3 1" with ID 10.10.10.1
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 240 secs
Interface flood pacing timer 33 msecs
Retransmission pacing timer 66 msecs
Number of external LSA 0. Checksum Sum 0x000000
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
Area BACKBONE(0)
Number of interfaces in this area is 1
MD5 Authentication, SPI 1000
SPF algorithm executed 2 times
Number of LSA 5. Checksum Sum 0x02A005
Number of DCbitless LSA 0
Number of indication LSA 0
Number of DoNotAge LSA 0
Flood list length 0
The table below describes the significant fields shown in the display.
show ipv6 ospf With Area Encryption ExampleThe following sample output shows the show ipv6 ospf command with area encryption information:
Router# show ipv6 ospf
Routing Process "ospfv3 1" with ID 10.0.0.1
It is an area border router
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 240 secs
Interface flood pacing timer 33 msecs
Retransmission pacing timer 66 msecs
Number of external LSA 0. Checksum Sum 0x000000
Number of areas in this router is 2. 2 normal 0 stub 0 nssa
Reference bandwidth unit is 100 mbps
Area BACKBONE(0)
Number of interfaces in this area is 2
SPF algorithm executed 3 times
Number of LSA 31. Checksum Sum 0x107493
Number of DCbitless LSA 0
Number of indication LSA 0
Number of DoNotAge LSA 20
Flood list length 0
Area 1
Number of interfaces in this area is 2
NULL Encryption SHA-1 Auth, SPI 1001
SPF algorithm executed 7 times
Number of LSA 20. Checksum Sum 0x095E6A
Number of DCbitless LSA 0
Number of indication LSA 0
Number of DoNotAge LSA 0
Flood list length 0
The table below describes the significant fields shown in the display.
The following example displays the configuration values for SPF and LSA throttling timers:
Router# show ipv6 ospf
Routing Process "ospfv3 1" with ID 10.9.4.1
Event-log enabled, Maximum number of events: 1000, Mode: cyclic
It is an autonomous system boundary router
Redistributing External Routes from,
ospf 2
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
The table below describes the significant fields shown in the display.
The following example shows information about LSAs that are currently being rate limited:
Router# show ipv6 ospf rate-limit
List of LSAs that are in rate limit Queue
LSAID: 0.0.0.0 Type: 0x2001 Adv Rtr: 10.55.55.55 Due in: 00:00:00.500
LSAID: 0.0.0.0 Type: 0x2009 Adv Rtr: 10.55.55.55 Due in: 00:00:00.500
The table below describes the significant fields shown in the display.
show ipv6 ospf trafficTo display IPv6 Open Shortest Path First Version 3 (OSPFv3) traffic statistics, use the showipv6ospftrafficcommand in privileged EXEC mode. Command DefaultWhen the showipv6ospftraffic command is entered without any arguments, global OSPF traffic statistics are displayed, including queue statistics for each OSPF process, statistics for each interface, and per OSPF process statistics. Usage GuidelinesYou can limit the displayed traffic statistics to those for a specific OSPF process by entering a value for the process-id argument, or you can limit output to traffic statistics for a specific interface associated with an OSPF process by entering values for the interface-type and interface-number arguments. To reset counters and clear statistics, use the clearipv6ospftraffic command. ExamplesThe following example shows the display output for the showipv6ospftraffic command for OSPFv3:
Router# show ipv6 ospf traffic
OSPFv3 statistics:
Rcvd: 32 total, 0 checksum errors
10 hello, 7 database desc, 2 link state req
9 link state updates, 4 link state acks
0 LSA ignored
Sent: 45 total, 0 failed
17 hello, 12 database desc, 2 link state req
8 link state updates, 6 link state acks
OSPFv3 Router with ID (10.1.1.4) (Process ID 6)
OSPFv3 queues statistic for process ID 6
Hello queue size 0, no limit, max size 2
Router queue size 0, limit 200, drops 0, max size 2
Interface statistics:
Interface Serial2/0
OSPFv3 packets received/sent
Type Packets Bytes
RX Invalid 0 0
RX Hello 5 196
RX DB des 4 172
RX LS req 1 52
RX LS upd 4 320
RX LS ack 2 112
RX Total 16 852
TX Failed 0 0
TX Hello 8 304
TX DB des 3 144
TX LS req 1 52
TX LS upd 3 252
TX LS ack 3 148
TX Total 18 900
OSPFv3 header errors
Length 0, Checksum 0, Version 0, No Virtual Link 0,
Area Mismatch 0, Self Originated 0, Duplicate ID 0,
Instance ID 0, Hello 0, MTU Mismatch 0,
Nbr Ignored 0, Authentication 0,
OSPFv3 LSA errors
Type 0, Length 0, Data 0, Checksum 0,
Interface Ethernet0/0
OSPFv3 packets received/sent
Type Packets Bytes
RX Invalid 0 0
RX Hello 6 240
RX DB des 3 144
RX LS req 1 52
RX LS upd 5 372
RX LS ack 2 152
RX Total 17 960
TX Failed 0 0
TX Hello 11 420
TX DB des 9 312
TX LS req 1 52
TX LS upd 5 376
TX LS ack 3 148
TX Total 29 1308
OSPFv3 header errors
Length 0, Checksum 0, Version 0, No Virtual Link 0,
Area Mismatch 0, Self Originated 0, Duplicate ID 0,
Instance ID 0, Hello 0, MTU Mismatch 0,
Nbr Ignored 0, Authentication 0,
OSPFv3 LSA errors
Type 0, Length 0, Data 0, Checksum 0,
Summary traffic statistics for process ID 6:
OSPFv3 packets received/sent
Type Packets Bytes
RX Invalid 0 0
RX Hello 11 436
RX DB des 7 316
RX LS req 2 104
RX LS upd 9 692
RX LS ack 4 264
RX Total 33 1812
TX Failed 0 0
TX Hello 19 724
TX DB des 12 456
TX LS req 2 104
TX LS upd 8 628
TX LS ack 6 296
TX Total 47 2208
OSPFv3 header errors
Length 0, Checksum 0, Version 0, No Virtual Link 0,
Area Mismatch 0, Self Originated 0, Duplicate ID 0,
Instance ID 0, Hello 0, MTU Mismatch 0,
Nbr Ignored 0, Authentication 0,
OSPFv3 LSA errors
Type 0, Length 0, Data 0, Checksum 0,
The network administrator wants to start collecting new statistics, resetting the counters and clearing the traffic statistics by entering the clearipv6ospftraffic command as follows: Router# clear ipv6 ospf traffic The table below describes the significant fields shown in the display.
show ospfv3 sham-linksTo display parameters and the current state of Open Shortest Path First version 3 (OSPFv3) sham links, use the show ospfv3 sham-links command in user EXEC or privileged EXEC mode. Syntax Description
ExamplesThe following example displays OSPFv3 sham-link information for all VRFs:
Router# show ospfv3 vrf * sham-links
OSPFv3 1 address-family ipv6 vrf v1 (router-id 8.0.0.22)
Sham Link OSPFv3_SL1 to address 2001:111::824 is up
Interface ID 39
Area 0 source address 2001:111::822
Run as demand circuit
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 1/2/2, retransmission queue length 0, number of retransmission 0
First 0x0(0)/0x0(0)/0x0(0) Next 0x0(0)/0x0(0)/0x0(0)
Last retransmission scan length is 0, maximum is 0
Last retransmission scan time is 0 msec, maximum is 0 msec
Table 1
show ospfv3 virtual-links Field Descriptions Field Description
Sham Link OSPFv3_SL1 to address 2001:111::824 is up Specifies the
OSPFv3 neighbor, and if the link to that neighbor is up or down.
Interface ID Interface ID and IPv6 address of the router.
Area 0 source address 2001:111::822 The area the sham link is in and the IPv6 source address of the local
endpoint.
Cost of using 1 The cost of reaching the OSPFv3 neighbor through the sham link.
Transmit Delay is 1 sec The transmit delay (in seconds) on the sham link.
State POINT_TO_POINT The state of the OSPFv3 neighbor.
Timer intervals... The various timer intervals configured for the link.
Adjacency State FULL (Hello suppressed) The neighbor adjacency state.
shutdown (router OSPF)To initiate a graceful shutdown of the Open Shortest Path First (OSPF) protocol under the current instance, use the shutdown command in router configuration mode. To restart the OSPF protocol, use the noform of this command. Usage GuidelinesUse the shutdown command in router configuration mode to temporarily shut down a protocol in the least disruptive manner and to notify its neighbors that it is going away. All traffic that has another path through the network will be directed to that alternate path. snmp-server enable traps ospfT o enable all Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF), use the snmp-server enable traps ospfcommand in global configuration mode. To disable all SNMP notifications for OSPF, use the noform of this command. Command History
Usage GuidelinesIf you wish to enable or disable specific OSPF SNMP notifications, enter one or more of the following commands of the following commands: [no] snmp-server enable traps ospf cisco-specific errors [no] snmp-server enable traps ospf cisco-specific lsa [no] snmp-server enable traps ospf cisco-specific retransmit [no] snmp-server enable traps ospf cisco-specific state-change [no] snmp-server enable traps ospf errors [no] snmp-server enable traps ospf lsa [no] snmp-server enable traps ospf retransmit [no] snmp-server enable traps ospf state-change ExamplesThe following exampleglobally enables SNMP notifications for OSPF:
Router(config)# snmp-server enable traps ospf
Related Commands
snmp-server enable traps ospf cisco-specific errorsT o enable Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF) configuration mismatch errors, use the snmp-server enable traps ospf cisco-specific errorscommand in global configuration mode. To disable SNMP notifications for OSPF configuration mismatch errors, use the noform of this command.
snmp-server
enable
traps
ospf
cisco-specific
errors
[config-error]
[virt-config-error]
no
snmp-server
enable
traps
ospf
cisco-specific
errors
[config-error]
[virt-config-error]
Command History
Usage GuidelinesTo enable the SNMP notifications for OSPF configuration errors for both virtual and nonvirtual interfaces, enter the snmp-server enable traps ospf cisco-specific errorscommand in global configuration mode without the optional keywords. ExamplesThe following example enables the router to send OSPF configuration mismatch errors only for nonvirtual interfaces:
Router(config)# snmp-server enable traps ospf cisco-specific errors config-error
Related Commands
snmp-server enable traps ospf cisco-specific errors config-errorTo e nable 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-errorcommand 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
Command DefaultThis command is disabled by default; therefore, SNMP notifications for OSPF nonvirtual interface mismatch errors are not created. Command History
Usage GuidelinesTo 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. ExamplesThe 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
snmp-server enable traps ospf cisco-specific errors shamlinkT o 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 shamlinkcommand in global configuration mode. To disable OSPF sham-link error SNMP notifications, use the noform 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
Command DefaultThis command is disabled by default; therefore, SNMP notifications for OSPF sham-link errors are not created. Command History
Usage GuidelinesTo 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. ExamplesThe 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)# snmp-server host myhost.cisco.com informs version 2c public Related Commands
snmp-server enable traps ospf cisco-specific lsaT o enable Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF) opaque link-state advertisements (LSAs), use the snmp-server enable traps ospf cisco-specific lsacommand in global configuration mode. To disable SNMP notifications for OSPF opaque LSAs, use the noform of this command.
snmp-server
enable
traps
ospf
cisco-specific
lsa
[lsa-maxage]
[lsa-originate]
no
snmp-server
enable
traps
ospf
cisco-specific
lsa
[lsa-maxage]
[lsa-originate]
Command History
Usage GuidelinesThe snmp-server enable traps ospf cisco-specific lsa command enables the traps that are defined by the CISCO-OSPF-TRAP-MIB for opaque LSAs. An opaque link-state advertisement (LSA) is used in MPLS traffic engineering to distribute attributes such as capacity and topology of links in a network. The scope of this LSA can be confined to the local network (Type 9, Link-Local), OSPF area (Type 20, Area-Local), or Autonomous System (Type 11, AS scope). The information in an opaque LSA can be used by an external application across the OSPF network. To enable the cospfMaxAgeLsa trap, enter the snmp-server enable traps ospf cisco-specific lsacommand with the lsa-maxage keyword. To enable the cospfOriginateLsa trap, enter the snmp-server enable traps ospf cisco-specific lsacommand with the lsa-originate keyword. When you enter the snmp-server enable traps ospf cisco-specific lsa command without either keyword, both traps will be enabled. ExamplesThe following example enables the router to send OSPF opaque LSA notifications to the host at the address myhost.cisco.com using the community string defined as public whenever new opaque LSAs are created: Router(config)# snmp-server enable traps ospf cisco-specific lsa lsa-originate Router(config)# snmp-server host myhost.cisco.com informs version 2c public Related Commands
snmp-server enable traps ospf cisco-specific retransmitT o enable Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF) retransmission errors, use the snmp-server enable traps ospf cisco-specific retransmitcommand in global configuration mode. To disable OSPF sham-link error SNMP notifications, use the noform 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
Command DefaultThis command is disabled by default; therefore, SNMP notifications for OSPF retransmission errors are not created. Command History
ExamplesThe 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
snmp-server enable traps ospf cisco-specific state-changeT o 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-changecommand in global configuration mode. To disable OSPF transition state change SNMP notifications, use the noform 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]]
Syntax Description
Command DefaultThis command is disabled by default; therefore, SNMP notifications for OSPF transition state changes are not created. Command History
Usage GuidelinesYou cannot enter both the interface and interface-old keywords because you cannot enable both the new and replaced sham-link interface transition state change traps. You can configure only one of the two traps, but not both. ExamplesThe following example enables the router to send OSPF sham-link transition state change 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 state-change shamlink Router(config)# snmp-server host myhost.cisco.com informs version 2c public Related Commands
snmp-server enable traps ospf errorsT o enable Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF) errors, use the snmp-server enable traps ospf errorscommand in global configuration mode. To disable SNMP notifications for OSPF errors, use the noform of this command.
snmp-server
enable
traps
ospf
errors
[authentication-failure]
[bad-packet]
[config-error]
[virt-authentication-failure]
[virt-bad-packet]
[virt-config-error]
no
snmp-server
enable
traps
ospf
errors
[authentication-failure]
[bad-packet]
[config-error]
[virt-authentication-failure]
[virt-bad-packet]
[virt-config-error]
Syntax Description
Command History
Usage GuidelinesWhen you enter the snmp-server enable traps ospf errors command without any optional keywords, all OSPF error traps will be enabled. To enable only one or more OSPF error traps, enter one or more of the optional keywords. ExamplesThe following example enables the router to send all OSPF error notifications:
Router(config)# snmp-server enable traps ospf errors
Related Commands
snmp-server enable traps ospf lsaT o enable Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF) link-state advertisements (LSAs), use the snmp-server enable traps ospf lsacommand in global configuration mode. To disable SNMP notifications for OSPF LSAs, use the noform of this command.
snmp-server
enable
traps
ospf
lsa
[lsa-maxage]
[lsa-originate]
no
snmp-server
enable
traps
ospf
lsa
[lsa-maxage]
[lsa-originate]
Syntax Description
Command History
Usage GuidelinesThe snmp-server enable traps ospf lsacommand enables the traps for standard LSAs that are defined by the OSPF-MIB. To enable the ospfMaxAgeLsa trap, enter the snmp-server enable traps ospf lsacommand with the lsa-maxage keyword. To enable the ospfOriginateLsa trap, enter the snmp-server enable traps ospf lsacommand with the lsa-originate keyword. When the ospfOriginateLsa trap is enabled, it will not be invoked for simple LSA refreshes that take place every 30 minutes or when an LSA has reached its maximum age and is being flushed. When you enter the snmp-server enable traps ospf lsa command without either keyword, both traps will be enabled. To enable the traps that are defined by the CISCO-OSPF-TRAP-MIB for opaque LSAs, enter the snmp-server enable traps ospf cisco-specific lsacommand in global configuration mode. ExamplesThe following example enables the router to send SNMP notifications when new LSAs are originated by the router as a result of a topology change:
Router(config)# snmp-server enable traps ospf lsa lsa-originate
Related Commands
snmp-server enable traps ospf rate-limitT o limit the number of Open Shortest Path First (OSPF) traps that are sent during a specified number of seconds, use the snmp-server enable traps ospf rate-limitcommand in global configuration mode. To disable the limit placed on the number of OSPF traps sent during a specified number of seconds, use the noform of this command.
snmp-server
enable
traps
ospf
rate-limit
seconds
trap-number
no
snmp-server
enable
traps
ospf
rate-limit
seconds
trap-number
Command History
Usage GuidelinesThere is a possibility that a router sends trap bursts, which can drain network resources in a small interval of time. It is recommended that you enter the snmp-server enable traps ospf rate-limit command to configure a sliding window mechanism that will limit the number of traps that are sent within a specified number of seconds. ExamplesThe following example sets the trap rate limit window so that during a 40-second window of time, no more that 50 traps are sent.
Router(config)# snmp-server enable traps ospf rate-limit 40 50
Related Commands
snmp-server enable traps ospf retransmitT o enable Simple Network Management Protocol (SNMP) notifications when packets are re-sent in an Open Shortest Path First (OSPF) network, use the snmp-server enable traps ospf retransmitcommand in global configuration mode. To disable SNMP notifications, use the noform of this command.
snmp-server
enable
traps
ospf
retransmit
[packets]
[virt-packets]
no
snmp-server
enable
traps
ospf
retransmit
[packets]
[virt-packets]
Syntax Description
Command History
Usage GuidelinesTo enable the ospfTXRetransmit trap so that SNMP notifications are sent only when packets from nonvirtual interfaces are re-sent, enter the snmp-server enable traps ospf retransmitcommand with the packets keyword. To enable the ospfTxRetransmit trap so that SNMP notifications are sent only when packets from virtual interfaces are re-sent, enter the snmp-server enable traps ospf retransmitcommand with the virt-packets keyword. When you enter the snmp-server enable traps ospf retransmit command without either keyword, both traps will be enabled. ExamplesThe following example enables the router to send SNMP notifications when packets are re-sent by virtual interfaces:
Router(config)# snmp-server enable traps ospf retransmit virt-packets
Related Commands
snmp-server enable traps ospf state-changeT o enable Simple Network Management Protocol (SNMP) notifications for Open Shortest Path First (OSPF) transition state changes, use the snmp-server enable traps ospf state-changecommand in global configuration mode. To disable SNMP notifications for OSPF transition state changes, use the noform of this command.
snmp-server
enable
traps
ospf
state-change
[if-state-change]
[neighbor-state-change]
[virtif-state-change]
[virtneighbor-state-change]
no
snmp-server
enable
traps
ospf
state-change
[if-state-change]
[neighbor-state-change]
[virtif-state-change]
[virtneighbor-state-change]
Syntax Description
Usage GuidelinesTo enable all traps for transition state changes, enter the snmp-server enable traps ospf state-change command without of the optional keywords. ExamplesThe following example enables the router to send SNMP notifications for transition state changes for virtual interfaces and virtual neighbors:
Router(config)# snmp-server enable traps ospf state-change virtif-state-change virtneighbor-state-change
Related Commands
summary-address (OSPF)To create aggregate addresses for Open Shortest Path First (OSPF), use the summary-address command in router configuration mode. To restore the default, use the no form of this command.
summary-address
commandsummary-address
{ip-address mask | prefix mask}
[not-advertise]
[tag tag]
[nssa-only]
no
summary-address
{ip-address mask | prefix mask}
[not-advertise]
[tag tag]
[nssa-only]
Syntax Description
Command History
Usage GuidelinesR outes learned from other routing protocols can be summarized. The metric used to advertise the summary is the lowest metric of all the more specific routes. This command helps reduce the size of the routing table. Using this command for OSPF causes an OSPF Autonomous System Boundary Router (ASBR) to advertise one external route as an aggregate for all redistributed routes that are covered by the address. For OSPF, this command summarizes only routes from other routing protocols that are being redistributed into OSPF. Use the area range command for route summarization between OSPF areas. OSPF does not support the summary-address 0.0.0.0 0.0.0.0command. ExamplesIn the following example, the summary address 10.1.0.0 includes address 10.1.1.0, 10.1.2.0, 10.1.3.0, and so on. Only the address 10.1.0.0 is advertised in an external link-state advertisement. summary-address 10.1.0.0 255.255.0.0 timers lsa arrivalTo set the minimum interval at which the software accepts the same link-state advertisement (LSA) from Open Shortest Path First (OSPF) neighbors, use the timers lsa arrivalcommand in router configuration mode. To restore the default value, use the no form of this command. Command History
Usage GuidelinesThe timers lsa arrival command controls the minimum interval for accepting the same LSA. The "same LSA" is defined as an LSA instance that contains the same LSA ID number, LSA type, and advertising router ID. If an instance of the same LSA arrives sooner than the interval that is set, the LSA is dropped. We suggest you keep the millisecondsvalue of the timers lsa arrival command less than or equal to the neighbors' hold-interval value of the timers throttle lsa all command. ExamplesThe following example sets the minimum interval for accepting the same LSA at 2000 milliseconds: router ospf 1 log-adjacency-changes timers throttle lsa all 200 10000 45000 timers lsa arrival 2000 network 10.10.4.0 0.0.0.255 area 24 network 10.10.24.0 0.0.0.255 area 24 Related Commands
timers pacing floodTo configure link-state advertis ement (LSA) flood packet pacing, use the timers pacing flood command in router configuration mode. To restore the default flood packet pacing value, use the no form of this command. Command History
Usage GuidelinesConfiguring Open Shortest Path First (OSPF) flood pacing timers allows you to control interpacket spacing between consecutive link-state update packets in the OSPF transmission queue. This command allows you to control the rate at which LSA updates occur so that high CPU or buffer utilization that can occur when an area is flooded with a very large number of LSAs can be reduced. The default settings for OSPF packet pacing timers are suitable for the majority of OSPF deployments. Do not change the packet pacing timers unless all other options to meet OSPF packet flooding requirements have been exhausted. Specifically, network operators should prefer summarization, stub area usage, queue tuning, and buffer tuning before changing the default flood timers. Furthermore, there are no guidelines for changing timer values; each OSPF deployment is unique and should be considered on a case-by-case basis. The network operator assumes risks associated with changing the default flood timer values. ExamplesThe following example configures LSA flood packet-pacing updates to occur in 55-millisecond intervals for Open Shortest Path First (OSPF) routing process 1: Router(config)# router ospf 1 Router(config-router)# timers pacing flood 55 timers pacing lsa-groupTo change th e interval at which Open Shortest Path First ( OSPF) link-state advertisements (LSAs) are collected into a group and refreshed, checksummed, or aged, use the timers pacing lsa-groupcommandin router configuration mode. To restore the default value, use the no form of this command. Command DefaultThe default interval for this command is 240 seconds. OSPF LSA group pacing is enabled by default. Command History
Usage GuidelinesThis command allows you to control the rate at which LSA updates occur so that high CPU or buffer utilization that can occur when an area is flooded with a very large number of LSAs can be reduced. The default settings for OSPF packet pacing timers are suitable for the majority of OSPF deployments. Do not change the packet pacing timers unless all other options to meet OSPF packet flooding requirements have been exhausted. Specifically, network operators should prefer summarization, stub area usage, queue tuning, and buffer tuning before changing the default flooding timers. Furthermore, there are no guidelines for changing timer values; each OSPF deployment is unique and should be considered on a case-by-case basis. The network operator assumes the risks associated with changing the default timer values. Cisco IOS software groups the periodic refresh of LSAs to improve the LSA packing density for the refreshes in large topologies. The group timer controls the interval used for group refreshment of LSAs; however, this timer does not change the frequency that individual LSAs are refreshed (the default refresh rate is every 30 minutes). The duration of the LSA group pacing is inversely proportional to the number of LSAs the router is handling. For example, if you have about 10,000 LSAs, decreasing the pacing interval would benefit you. If you have a very small database (40 to 100 LSAs), increasing the pacing interval to 10 to 20 minutes might benefit you slightly. timers pacing retransmissionTo configure link-state adv ertisement (LSA) retransmission packet pacing, use the timers pacing retransmission command in router configuration mode. To restore the default retransmission packet pacing value, use the no form of this command. Command History
Usage GuidelinesConfiguring Open Shortest Path First (OSPF) retransmission pacing timers allow you to control interpacket spacing between consecutive link-state update packets in the OSPF retransmission queue. This command allows you to control the rate at which LSA updates occur so that high CPU or buffer utilization that can occur when an area is flooded with a very large number of LSAs can be reduced. The default settings for OSPF packet retransmission pacing timers are suitable for the majority of OSPF deployments. Do not change the packet retransmission pacing timers unless all other options to meet OSPF packet flooding requirements have been exhausted. Specifically, network operators should prefer summarization, stub area usage, queue tuning, and buffer tuning before changing the default flooding timers. Furthermore, there are no guidelines for changing timer values; each OSPF deployment is unique and should be considered on a case-by-case basis. The network operator assumes risks associated with changing the default packet retransmission pacing timer values. timers throttle lsa allTo set rate-limiting values for all types of Open Shortest Path First (OSPF) link-state advertisement (LSA) generation, use the timers throttle lsa allcommand in router configuration mode. To restore the default values, use the no form of this command. Syntax Description
Command Defaultstart-interval : 0 millisecondshold-interval:5000 millisecondsmax-interval: 5000 milliseconds Command History
Usage GuidelinesThe "same LSA" is defined as an LSA instance that contains the same LSA ID number, LSA type, and advertising router ID. We suggest you keep the millisecondsvalue of the timers lsa arrivalcommand less than or equal to the hold-interval value of the timers throttle lsa all command. ExamplesThis example customizes OSPF LSA throttling so that the start interval is 200 milliseconds, the hold interval is 10,000 milliseconds, and the maximum interval is 45,000 milliseconds. The minimum interval between instances of receiving the same LSA is 2000 milliseconds. router ospf 1 log-adjacency-changes timers throttle lsa all 200 10000 45000 timers lsa arrival 2000 network 10.10.4.0 0.0.0.255 area 24 network 10.10.24.0 0.0.0.255 area 24 timers throttle spfTo turn on Open Shortest Path First ( OSPF) shortest path first (SPF) throttling, use the timers throttle spf command in the appropriate configuration mode. To turn off OSPF SPF throttling, use the no form of this command.
timers
throttle
spf
spf-start
spf-hold
spf-max-wait
no
timers
throttle
spf
spf-start
spf-hold
spf-max-wait
Syntax Description
Command ModesAddress family configuration (config-router-af) Router address family topology configuration (config-router-af-topology) Router configuration (config-router) OSPF for IPv6 router configuration (config-rtr) Command History
Usage GuidelinesThe first wait interval between SPF calculations is the amount of time in milliseconds specified by the spf-startargument. Each consecutive wait interval is two times the current hold level in milliseconds until the wait time reaches the maximum time in milliseconds as specified by the spf-max-wait argument. Subsequent wait times remain at the maximum until the values are reset or a link-state advertisement (LSA) is received between SPF calculations. Release 12.2(33)SRB If you plan to configure the Multi-Topology Routing (MTR) feature, you need to enter the timers throttle spf command in router address family topology configuration mode in order to make this OSPF router configuration command become topology-aware. Release 15.2(1)T When you configure the ospfv3 network manet command on any interface attached to the OSPFv3 process, the default values for the spf-start, spf-hold, and the spf-max-wait arguments are reduced to 1000 milliseconds, 1000 milliseconds, and 2000 milliseconds respectively. ExamplesThe following example shows how to configure a router with the delay, hold, and maximum interval values for the timers throttle spf command set at 5, 1000, and 90,000 milliseconds, respectively. router ospf 1 router-id 10.10.10.2 log-adjacency-changes timers throttle spf 5 1000 90000 redistribute static subnets network 10.21.21.0 0.0.0.255 area 0 network 10.22.22.0 0.0.0.255 area 00 The following example shows how to configure a router using IPv6 with the delay, hold, and maximum interval values for the timers throttle spf command set at 500, 1000, and 10,000 milliseconds, respectively. ipv6 router ospf 1 event-log size 10000 one-shot log-adjacency-changes timers throttle spf 500 1000 10000 ttl-security all-interfacesTo enable Time-to-Live (TTL) security check on all OSPF interfaces, use the ttl-security all-interfacescommand in interface configuration mode. To disable TTL security check, use the noform of this command. Usage GuidelinesUse the ttl-security all-interfaces command to enable TTL security check on all OSPF interfaces. This command applies only to normal OSPF interfaces. It does not apply to virtual or sham links that require TTL security protection. Virtual and sham links must be configured independently. As a convenience, this command can be used to globally enable TTL security check on all OSPF interfaces. Then the ip ospf ttl-security disable command ininterface configuration mode can be used to disable TTL security on an interface-by-interface basis. © 2012 Cisco Systems, Inc. All rights reserved.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|