Table Of Contents
OSPF Debug Commands on Cisco IOS XR Software
debug ospf adj
debug ospf config
debug ospf database-timer
debug ospf events
debug ospf flood
debug ospf gs
debug ospf hello
debug ospf lsa-generation
debug ospf mda
debug ospf monitor
debug ospf mpls traffic-eng advertisements
debug ospf nsf
debug ospf packet
debug ospf rib
debug ospf rtrid
debug ospf spf
debug ospf tree
debug ospf uv
OSPF Debug Commands on Cisco IOS XR Software
This chapter describes the commands used to debug the Open Shortest Path First (OSPF) routing protocol on Cisco IOS XR software.
debug ospf adj
To display debugging information for adjacency events, use the debug ospf adj command in EXEC mode. To disable debugging output, use the no form of this command.
debug ospf instance-name adj [interface-type interface-instance]
no debug ospf instance-name adj [interface-type interface-instance]
Syntax Description
instance-name
|
Name that uniquely identifies an OSPF routing process. The instance name is any alphanumeric string no longer than 40 characters. The instance-name argument is defined by the router ospf command.
|
interface-type
|
(Optional) Interface type. For more information, use the question mark (?) online help function.
|
interface-instance
|
(Optional) Either a physical interface instance or a virtual interface instance as follows:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the modular services card or line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
Defaults
Debugging is disabled.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Use the debug ospf adj command to display debugging messages containing information related to adjacency events, such as the following:
•
Interface down event.
•
Two-way communication with a neighbor event. This is the most advanced state before beginning adjacency establishment. Communication between the two routers is bidirectional.
•
Neighbor (NBR) negotiation complete.
Caution 
The
debug ospf adj command generates a substantial amount of output. Use the command only when traffic on the IP network is low so that other activity on the system is not adversely affected.
Task ID
Task ID
|
Operations
|
ospf
|
read, write
|
Examples
The following is sample output from the debug ospf adj command:
RP/0/RP0/CPU0:router# debug ospf 1 adj GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:13:39: ospf[239]: Neighbor change Event on intf GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:13:39: ospf[239]: DR/BDR election on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:13:39: ospf[239]: Elect BDR Router ID 192.168.20.207(IP Addr
192.168.20.207)
RP/0/RP0/CPU0:13:39: ospf[239]: Elect DR Router ID 1.1.1.1(IP Addr 192.168.20.206)
RP/0/RP0/CPU0:13:39: ospf[239]: DR: 1.1.1.1(Id) 192.168.20.206(IP Addr)
RP/0/RP0/CPU0:13:39: ospf[239]: BDR: 192.168.20.207(Id) 192.168.20.207(IP Addr)
RP/0/RP0/CPU0:14:9: ospf[239]: Rcv DBD from 192.168.20.207(192.168.20.207) on
GigabitEthernet0/2/0/0 seq 0x19b8 opt 0x52 flag 0x7 len 32 mtu 1500 state FULL
RP/0/RP0/CPU0:14:9: ospf[239]: Bad seq received from 192.168.20.207 on
GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:14:9: ospf[239]: Send DBD to 192.168.20.207(192.168.20.207) on
GigabitEthernet0/2/0/0 seq 0x5251 opt 0x52 flag 0x7 len 32
RP/0/RP0/CPU0:14:9: ospf[239]: Neighbor change Event on intf GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:14:9: ospf[239]: DR/BDR election on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:14:9: ospf[239]: Elect BDR Router ID 192.168.20.207(IP Addr 192.168.20.207)
RP/0/RP0/CPU0:14:9: ospf[239]: Elect DR Router ID 1.1.1.1(IP Addr 192.168.20.206)
RP/0/RP0/CPU0:14:9: ospf[239]: DR: 1.1.1.1(Id) 192.168.20.206(IP Addr)
RP/0/RP0/CPU0:14:9: ospf[239]: BDR: 192.168.20.207(Id) 192.168.20.207(IP Addr)
RP/0/RP0/CPU0:14:14: ospf[239]: Rcv DBD from 192.168.20.207(192.168.20.207) on
GigabitEthernet0/2/0/0 seq 0x19b8 opt 0x52 flag 0x7 len 32 mtu 1500 state EXSTART
RP/0/RP0/CPU0:14:14: ospf[239]: NBR Negotiation Done. We are the SLAVE
RP/0/RP0/CPU0:14:14: ospf[239]: build dbd: took 0 ms for nbr 192.168.20.207, count=1
RP/0/RP0/CPU0:14:14: ospf[239]: Send DBD to 192.168.20.207(192.168.20.207) on
GigabitEthernet0/2/0/0 seq 0x19b8 opt 0x52 flag 0x2 len 52
RP/0/RP0/CPU0:14:14: ospf[239]: Rcv DBD from 192.168.20.207(192.168.20.207) on
GigabitEthernet0/2/0/0 seq 0x19b9 opt 0x52 flag 0x1 len 52 mtu 1500 state EXCHANGE
RP/0/RP0/CPU0:14:14: ospf[239]: Exchange Done with 192.168.20.207 on
GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:14:14: ospf[239]: sent LS REQ packet to 192.168.20.207, length 12
RP/0/RP0/CPU0:14:14: ospf[239]: Send DBD to 192.168.20.207(192.168.20.207) on
GigabitEthernet0/2/0/0 seq 0x19b9 opt 0x52 flag 0 len 32
RP/0/RP0/CPU0:14:14: ospf[239]: Synchronized with 192.168.20.207 on
GigabitEthernet0/2/0/0, state FULL
RP/0/RP0/CPU0:14:14: ospf[239]: %ROUTING-OSPF-5-ADJCHG : Process 1, Nbr 192.168.20.207 on
GigabitEthernet0/2/0/0 from LOADING to FULL, Loading Done
RP/0/RP0/CPU0:14:14: ospf[239]: Flooding Stats for nbr 192.168.20.207, LSA-Req Sent: 2
packets, 2 LSAs; LSA Upd rec'ed: 5 packets, 5 LSAs, DBD-rec'ed: 4 packets, 2 LSAs
Related Commands
Command
|
Description
|
undebug
|
Enters debug mode to disable or reset multiple active debug command sessions.
|
debug ospf config
To display debugging information for the Open Shortest Path First (OSPF) configuration, use the debug ospf config command in EXEC mode. To turn off debugging output, use the no form of this command.
debug ospf instance-name config
no debug ospf instance-name config
Syntax Description
instance-name
|
Name that uniquely identifies an OSPF routing process. The instance name is any alphanumeric string no longer than 40 characters. The instance name is defined by the router ospf command.
|
Defaults
Debugging is disabled.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Caution 
The
debug ospf config command generates a substantial amount of output. Use the command only when traffic on the IP network is low so that other activity on the system is not adversely affected.
Task ID
Task ID
|
Operations
|
ospf
|
read, write
|
Examples
The following example shows how to enable debugging information for the OSPF configuration:
RP/0/RP0/CPU0:router# debug ospf config
Related Commands
Command
|
Description
|
undebug
|
Enters debug mode to disable or reset multiple active debug command sessions.
|
debug ospf database-timer
To display debugging information for database timer events, use the debug ospf database-timer command in EXEC mode. To disable debugging output, use the no form of this command.
debug ospf instance-name database-timer
no debug ospf instance-name database-timer
Syntax Description
instance-name
|
Name that uniquely identifies an OSPF routing process. The instance name is any alphanumeric string no longer than 40 characters. The instance name is defined by the router ospf command.
|
Defaults
Debugging is disabled.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Use the debug ospf database-timer command to display messages containing information related to database events.
Caution 
The
debug ospf database-timer command generates a substantial amount of output. Use the command only when traffic on the IP network is low so that other activity on the system is not adversely affected.
Task ID
Task ID
|
Operations
|
ospf
|
read, write
|
Examples
The following is sample output from the debug ospf database-timer command:
RP/0/RP0/CPU0:router# debug ospf 1 database-timer
RP/0/RP0/CPU0:26:18: ospf[239]: Stop timer for 1.1.1.1 1.1.1.1 1 3
RP/0/RP0/CPU0:26:18: ospf[239]: Stop timer for 192.168.20.207 192.168.20.207 1 3
RP/0/RP0/CPU0:26:18: ospf[239]: Stop timer for 192.168.20.207 192.168.20.207 2 3
RP/0/RP0/CPU0:26:18: ospf[239]: Add 1.1.1.1 1.1.1.1 1 to min 27
RP/0/RP0/CPU0:26:18: ospf[239]: Delay 600/765270/765788 translated to 27/0 for 15/21 0
(3)
RP/0/RP0/CPU0:26:58: ospf[239]: Add 192.168.20.207 192.168.20.207 1 to min 27
RP/0/RP0/CPU0:26:58: ospf[239]: Delay 600/725715/725852 translated to 27/0 for 15/60 0
(3)
RP/0/RP0/CPU0:26:58: ospf[239]: Add 192.168.20.207 192.168.20.207 2 to min 27
RP/0/RP0/CPU0:26:58: ospf[239]: Delay 600/725709/725852 translated to 27/0 for 15/60 0
(3)
Related Commands
Command
|
Description
|
undebug
|
Enters debug mode to disable or reset multiple active debug command sessions.
|
debug ospf events
To display information on OSPF-related events such as adjacencies, flooding information, designated router selection, and shortest path first (SPF) calculation, use the debug ospf events command in EXEC mode. To disable debugging output, use the no form of this command.
debug ospf instance-name events [interface-type interface-instance]
no debug ospf instance-name events [interface-type interface-instance]
Syntax Description
instance-name
|
Name that uniquely identifies an OSPF routing process. The instance name is any alphanumeric string no longer than 40 characters. The instance name is defined by the router ospf command.
|
interface-type
|
(Optional) Interface type. For more information, use the question mark (?) online help function.
|
interface-instance
|
(Optional) Either a physical interface instance or a virtual interface instance as follows:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the modular services card or line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
Defaults
Debugging is disabled.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Use the debug ospf events command to display messages containing information related to neighbor state, interface, database, and so on.
The debug ospf events command output shown may appear if any of the following situations occurs:
•
The IP subnet masks for routers on the same network do not match.
•
The OSPF hello interval for the router does not match that configured for a neighbor.
•
The OSPF dead interval for the router does not match that configured for a neighbor.
If a router configured for OSPF routing is not seeing an OSPF neighbor on an attached network, perform the following tasks:
•
Make sure that both routers have been configured with the same IP mask, OSPF hello interval, and OSPF dead interval.
•
Make sure that both neighbors are part of the same area type.
In the following example line, the neighbor and this router are not part of a stub area (that is, one is a part of a transit area and the other is a part of a stub area, as explained in RFC 1247):
OSPF: hello packet with mismatched E bit
Caution 
The
debug ospf events command generates a substantial amount of output. Use the command only when traffic on the IP network is low so that other activity on the system is not adversely affected.
Task ID
Task ID
|
Operations
|
ospf
|
read, write
|
Examples
The following is sample output from the debug ospf events command:
RP/0/RP0/CPU0:router# debug ospf 1 events
RP/0/RP0/CPU0:28:55: ospf[239]: Send hello to 224.0.0.5 area 0 on GigabitEthernet0/2/0/0
from 192.168.20.206 (nbr/if state 3/2)
RP/0/RP0/CPU0:28:55: ospf[239]: Send hello pkt pri 1 options 0x12 DR 0.0.0.0 BDR 0.0.0.0
hello 10 dead 40 netmask 255.255.255.0
RP/0/RP0/CPU0:28:59: ospf[239]: Rcv hello from 192.168.20.207 area 0 from
GigabitEthernet0/2/0/0 192.168.20.207 (nbr/if state 3/2)
RP/0/RP0/CPU0:28:59: ospf[239]: Rcv hello pkt pri 1 options 0x12 DR 192.168.20.207 BDR
192.168.20.206 hello 10 dead 40 netmask 255.255.255.0 (nbr_dr 192.168.20.207 nbr_bdr
192.168.20.206)
RP/0/RP0/CPU0:28:59: ospf[239]: End of hello processing
RP/0/RP0/CPU0:29:5: ospf[239]: Send hello to 224.0.0.5 area 0 on GigabitEthernet0/2/0/0
from 192.168.20.206 (nbr/if state 3/2)
RP/0/RP0/CPU0:29:5: ospf[239]: Send hello pkt pri 1 options 0x12 DR 0.0.0.0 BDR 0.0.0.0
hello 10 dead 40 netmask 255.255.255.0
RP/0/RP0/CPU0:29:9: ospf[239]: Rcv hello from 192.168.20.207 area 0 from
GigabitEthernet0/2/0/0 192.168.20.207 (nbr/if state 3/2)
RP/0/RP0/CPU0:29:9: ospf[239]: Rcv hello pkt pri 1 options 0x12 DR 192.168.20.207 BDR
192.168.20.206 hello 10 dead 40 netmask 255.255.255.0 (nbr_dr 192.168.20.207 nbr_bdr
192.168.20.206)
RP/0/RP0/CPU0:29:9: ospf[239]: End of hello processing
RP/0/RP0/CPU0:29:15: ospf[239]: Send hello to 224.0.0.5 area 0 on GigabitEthernet0/2/0/0
from 192.168.20.206 (nbr/if state 3/2)
RP/0/RP0/CPU0:29:15: ospf[239]: Send hello pkt pri 1 options 0x12 DR 0.0.0.0 BDR 0.0.0.0
hello 10 dead 40 netmask 255.255.255.0
RP/0/RP0/CPU0:29:19: ospf[239]: Rcv hello from 192.168.20.207 area 0 from
GigabitEthernet0/2/0/0 192.168.20.207 (nbr/if state 3/2)
RP/0/RP0/CPU0:29:19: ospf[239]: Rcv hello pkt pri 1 options 0x12 DR 192.168.20.207 BDR
192.168.20.206 hello 10 dead 40 netmask 255.255.255.0 (nbr_dr 192.168.20.207 nbr_bdr
192.168.20.206)
RP/0/RP0/CPU0:29:19: ospf[239]: End of hello processing
RP/0/RP0/CPU0:29:25: ospf[239]: end of Wait on intf GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:29:25: ospf[239]: DR/BDR election on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:29:25: ospf[239]: Elect BDR Router ID 1.1.1.1(IP Addr 192.168.20.206)
RP/0/RP0/CPU0:29:25: ospf[239]: Elect DR Router ID 192.168.20.207(IP Addr 192.168.20.207)
RP/0/RP0/CPU0:29:25: ospf[239]: Elect BDR Router ID 1.1.1.1(IP Addr 192.168.20.206)
Related Commands
Command
|
Description
|
debug ospf packet
|
Displays information about each OSPF packet received.
|
undebug
|
Enters debug mode to disable or reset multiple active debug command sessions.
|
debug ospf flood
To display information about flood events such as acknowledgments and updates received, use the debug ospf flood command in EXEC mode. To disable debugging output, use the no form of this command.
debug ospf instance-name flood [access-list-name]
no debug ospf instance-name flood [access-list-name]
Syntax Description
instance-name
|
Name that uniquely identifies an OSPF routing process. The instance name is any alphanumeric string no longer than 40 characters. The instance name is defined by the router ospf command.
|
access-list-name
|
(Optional) Name of a particular access control list. The name cannot contain a space or quotation mark; it may contain numbers.
|
Defaults
Debugging is disabled.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Use the debug ospf flood command to display messages containing information related to flood events.
Caution 
The
debug ospf flood command generates a substantial amount of output. Use the command only when traffic on the IP network is low so that other activity on the system is not adversely affected.
Task ID
Task ID
|
Operations
|
ospf
|
read, write
|
Examples
The following is sample output from the debug ospf flood command:
RP/0/RP0/CPU0:router# debug ospf 1 flood
RP/0/RP0/CPU0:33:19: ospf[239]: Rcv Update Type 2, LSID 192.168.20.207, Adv rtr
192.168.20.207, age 764, seq 0x80000001
RP/0/RP0/CPU0:33:19: ospf[239]: Mask 255.255.255.0
RP/0/RP0/CPU0:33:19: ospf[239]: %ROUTING-OSPF-5-ADJCHG : Process 1, Nbr 192.168.20.207 on
GigabitEthernet0/2/0/0 from LOADING to FULL, Loading Done
RP/0/RP0/CPU0:33:19: ospf[239]: Sending update on GigabitEthernet0/2/0/0 to 192.168.20.207
Area 0
RP/0/RP0/CPU0:33:19: ospf[239]: Send Type 1, LSID 1.1.1.1, Adv rtr 1.1.1.1, age 40, seq
0x80000001 (0)
RP/0/RP0/CPU0:33:19: ospf[239]: Inc retrans unit nbr count index 1 (0/1) to 1/1
RP/0/RP0/CPU0:33:19: ospf[239]: Set Nbr 192.168.20.207 1 first flood info from 0 (0) to
0x81e1994 (18)
RP/0/RP0/CPU0:33:19: ospf[239]: Init Nbr 192.168.20.207 1 next flood info to 0x81e1994
RP/0/RP0/CPU0:33:19: ospf[239]: Add Type 1 LSA ID 1.1.1.1 Adv rtr 1.1.1.1 Seq 80000002 to
GigabitEthernet0/2/0/0 192.168.20.207 retransmission list
RP/0/RP0/CPU0:33:19: ospf[239]: Start GigabitEthernet0/2/0/0 192.168.20.207 retrans timer
RP/0/RP0/CPU0:33:19: ospf[239]: Set idb next flood info from 0 (0) to 0x81e1994 (18)
RP/0/RP0/CPU0:33:19: ospf[239]: Add Type 1 LSA ID 1.1.1.1 Adv rtr 1.1.1.1 Seq 80000002 to
GigabitEthernet0/2/0/0 flood list
RP/0/RP0/CPU0:33:19: ospf[239]: Start GigabitEthernet0/2/0/0 pacing timer for 0.000001
msec
RP/0/RP0/CPU0:33:19: ospf[239]: Flooding update on GigabitEthernet0/2/0/0 to 224.0.0.5
Area 0
RP/0/RP0/CPU0:33:19: ospf[239]: Send Type 1, LSID 1.1.1.1, Adv rtr 1.1.1.1, age 1, seq
0x80000002 (0)
RP/0/RP0/CPU0:33:19: ospf[239]: Create retrans unit 0x81e0178/0x81df818 1 (0/1) 1
RP/0/RP0/CPU0:33:19: ospf[239]: Set nbr 1 (0/1) retrans to 4976 count to 1
RP/0/RP0/CPU0:33:19: ospf[239]: Set idb next flood info from 0x81e1994 (18) to 0 (0)
RP/0/RP0/CPU0:33:19: ospf[239]: Remove Type 1 LSA ID 1.1.1.1 Adv rtr 1.1.1.1 Seq 80000002
from GigabitEthernet0/2/0/0 flood list
RP/0/RP0/CPU0:33:19: ospf[239]: Stop GigabitEthernet0/2/0/0 flood timer
RP/0/RP0/CPU0:33:21: ospf[239]: Sending delayed ACK on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:33:21: ospf[239]: Ack Type 1, LSID 192.168.20.207, Adv rtr 192.168.20.207,
age 764, seq 0x80000003
RP/0/RP0/CPU0:33:21: ospf[239]: Ack Type 2, LSID 192.168.20.207, Adv rtr 192.168.20.207,
age 764, seq 0x80000001
RP/0/RP0/CPU0:33:21: ospf[239]: Received ACK from 192.168.20.207 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:33:21: ospf[239]: Rcv Ack Type 1, LSID 1.1.1.1, Adv rtr 1.1.1.1, age 40, seq
0x80000001
RP/0/RP0/CPU0:33:24: ospf[239]: Retransmitting update on GigabitEthernet0/2/0/0 to
192.168.20.207 Area 0
Related Commands
Command
|
Description
|
undebug
|
Enters debug mode to disable or reset multiple active debug command sessions.
|
debug ospf gs
To display information on OSPF graceful shutdown events, use the debug ospf gs command in EXEC mode. To disable debugging output, use the no form of this command.
debug ospf instance-name gs
no debug ospf instance-name gs
Syntax Description
instance-name
|
Name that uniquely identifies an OSPF routing process. The instance name is any alphanumeric string no longer than 40 characters. The instance name is defined by the router ospf command.
|
Defaults
Debugging is disabled.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Use the debug ospf gs command to display information about OSPF graceful shutdown events.
Caution 
The
debug ospf gs command generates a substantial amount of output. Use the command only when traffic on the IP network is low so that other activity on the system is not adversely affected.
Task ID
Task ID
|
Operations
|
ospf
|
read, write
|
Examples
The following is sample output from the debug ospf gs command:
RP/0/RP0/CPU0:router# debug ospf 1 gs
RP/0/RP0/CPU0:1h:39:57: ospf[239]: GS: Leave init. state/event
Initial/Shutdown_Not_Configured
RP/0/RP0/CPU0:1h:39:57: ospf[239]: GS: Moving to normal OSPF operation. state Initial ->
Normal
RP/0/RP0/CPU0:1h:39:57: ospf[239]: GS: NORMAL memory notification seen
Related Commands
Command
|
Description
|
undebug
|
Enters debug mode to disable or reset multiple active debug command sessions.
|
debug ospf hello
To display information about hello events for an interface or all interfaces, use the debug ospf hello command in EXEC mode. To disable debugging output, use the no form of this command.
debug ospf instance-name hello [interface-type interface-instance]
no debug ospf instance-name hello [interface-type interface-instance]
Syntax Description
instance-name
|
Name that uniquely identifies an OSPF routing process. The instance name is any alphanumeric string no longer than 40 characters. The instance name is defined by the router ospf command.
|
interface-type
|
(Optional) Interface type. For more information, use the question mark (?) online help function.
|
interface-instance
|
(Optional) Either a physical interface instance or a virtual interface instance as follows:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the modular services card or line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
Defaults
Debugging is disabled.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Use the debug ospf hello command to obtain information about the hello protocol messages related to the hello protocol events such as receiving, sending, and processing hello packets.
Caution 
The
debug ospf hello command generates a substantial amount of output. Use the command only when traffic on the IP network is low so that other activity on the system is not adversely affected.
Task ID
Task ID
|
Operations
|
ospf
|
read, write
|
Examples
The following is sample output from the debug ospf hello command:
RP/0/RP0/CPU0:router# debug ospf 1 hello
RP/0/RP0/CPU0:34:50: ospf[239]: Rcv hello from 192.168.20.207 area 0 from
GigabitEthernet0/2/0/0 192.168.20.207 (nbr/if state 3/2)
RP/0/RP0/CPU0:34:50: ospf[239]: ospf_router Rcv hello from new nbr 192.168.20.207 area 0
from GigabitEthernet0/2/0/0 192.168.20.207
RP/0/RP0/CPU0:34:50: ospf[239]: Rcv hello pkt pri 1 options 0x12 DR 192.168.20.207 BDR
192.168.20.206 hello 10 dead 40 netmask 255.255.255.0 (nbr_dr 0.0.0.0 nbr_bdr 0.0.0.0)
RP/0/RP0/CPU0:34:50: ospf[239]: End of router thread hello processing
RP/0/RP0/CPU0:34:56: ospf[239]: Send hello to 224.0.0.5 area 0 on GigabitEthernet0/2/0/0
from 192.168.20.206 (nbr/if state 3/2)
RP/0/RP0/CPU0:34:56: ospf[239]: Send hello pkt pri 1 options 0x12 DR 0.0.0.0 BDR 0.0.0.0
hello 10 dead 40 netmask 255.255.255.0
RP/0/RP0/CPU0:35:0: ospf[239]: Rcv hello from 192.168.20.207 area 0 from
GigabitEthernet0/2/0/0 192.168.20.207 (nbr/if state 3/2)
RP/0/RP0/CPU0:35:0: ospf[239]: Rcv hello pkt pri 1 options 0x12 DR 192.168.20.207 BDR
192.168.20.206 hello 10 dead 40 netmask 255.255.255.0 (nbr_dr 192.168.20.207 nbr_bdr
192.168.20.206)
RP/0/RP0/CPU0:35:0: ospf[239]: End of hello processing
RP/0/RP0/CPU0:35:6: ospf[239]: Send hello to 224.0.0.5 area 0 on GigabitEthernet0/2/0/0
from 192.168.20.206 (nbr/if state 3/2)
RP/0/RP0/CPU0:35:6: ospf[239]: Send hello pkt pri 1 options 0x12 DR 0.0.0.0 BDR 0.0.0.0
hello 10 dead 40 netmask 255.255.255.0
RP/0/RP0/CPU0:35:10: ospf[239]: Rcv hello from 192.168.20.207 area 0 from
GigabitEthernet0/2/0/0 192.168.20.207 (nbr/if state 3/2)
RP/0/RP0/CPU0:35:10: ospf[239]: Rcv hello pkt pri 1 options 0x12 DR 192.168.20.207 BDR
192.168.20.206 hello 10 dead 40 netmask 255.255.255.0 (nbr_dr 192.168.20.207 nbr_bdr
192.168.20.206)
RP/0/RP0/CPU0:35:10: ospf[239]: End of hello processing
RP/0/RP0/CPU0:35:16: ospf[239]: Send hello to 224.0.0.5 area 0 on GigabitEthernet0/2/0/0
from 192.168.20.206 (nbr/if state 3/2)
RP/0/RP0/CPU0:35:16: ospf[239]: Send hello pkt pri 1 options 0x12 DR 0.0.0.0 BDR 0.0.0.0
hello 10 dead 40 netmask 255.255.255.0
RP/0/RP0/CPU0:35:20: ospf[239]: Rcv hello from 192.168.20.207 area 0 from
GigabitEthernet0/2/0/0 192.168.20.207 (nbr/if state 3/2)
RP/0/RP0/CPU0:35:20: ospf[239]: Rcv hello pkt pri 1 options 0x12 DR 192.168.20.207 BDR
192.168.20.206 hello 10 dead 40 netmask 255.255.255.0 (nbr_dr 192.168.20.207 nbr_bdr
192.168.20.206)
RP/0/RP0/CPU0:35:20: ospf[239]: End of hello processing
RP/0/RP0/CPU0:35:26: ospf[239]: Send hello to 224.0.0.5 area 0 on GigabitEthernet0/2/0/0
from 192.168.20.206 (nbr/if state 3/6)
RP/0/RP0/CPU0:35:26: ospf[239]: Send hello pkt pri 1 options 0x12 DR 192.168.20.207 BDR
192.168.20.206 hello 10 dead 40 netmask 255.255.255.0
RP/0/RP0/CPU0:35:26: ospf[239]: %ROUTING-OSPF-5-ADJCHG : Process 1, Nbr 192.168.20.207 on
GigabitEthernet0/2/0/0 from LOADING to FULL, Loading Done
RP/0/RP0/CPU0:35:30: ospf[239]: Rcv hello from 192.168.20.207 area 0 from
GigabitEthernet0/2/0/0 192.168.20.207 (nbr/if state 3/6)
RP/0/RP0/CPU0:35:30: ospf[239]: Rcv hello pkt pri 1 options 0x12 DR 192.168.20.207 BDR
192.168.20.206 hello 10 dead 40 netmask 255.255.255.0 (nbr_dr 192.168.20.207 nbr_bdr
192.168.20.206)
RP/0/RP0/CPU0:35:30: ospf[239]: End of hello processing
Related Commands
Command
|
Description
|
undebug
|
Enters debug mode to disable or reset multiple active debug command sessions.
|
debug ospf lsa-generation
To display information about link-state advertisement (LSA) events, use the debug ospf lsa-generation command in EXEC mode. To disable debugging output, use the no form of this command.
debug ospf instance-name lsa-generation [access-list-name]
no debug ospf instance-name lsa-generation [access-list-name]
Syntax Description
instance-name
|
Name that uniquely identifies an OSPF routing process. The instance name is any alphanumeric string no longer than 40 characters. The instance name is defined by the router ospf command.
|
access-list-name
|
(Optional) Name of a particular access control list. The name cannot contain a space or quotation mark; it may contain numbers.
|
Defaults
Debugging is disabled.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Use the debug ospf lsa-generation command to display messages containing information related to LSA generation events.
Caution 
The
debug ospf lsa-generation command generates a substantial amount of output. Use the command only when traffic on the IP network is low so that other activity on the system is not adversely affected.
Task ID
Task ID
|
Operations
|
ospf
|
read, write
|
Examples
The following is sample output from the debug ospf lsa-generation command:
RP/0/RP0/CPU0:router# debug ospf 1 lsa-generation
RP/0/RP0/CPU0:36:32: ospf[239]: Build router LSA for area 0, router ID 1.1.1.1, seq
0x80000001
RP/0/RP0/CPU0:36:32: ospf[239]: Start redist-scanning
RP/0/RP0/CPU0:36:32: ospf[239]: Scan for redistribution
RP/0/RP0/CPU0:36:32: ospf[239]: End scanning, Elapsed time 000000000.000000000
RP/0/RP0/CPU0:37:11: ospf[239]: %ROUTING-OSPF-5-ADJCHG : Process 1, Nbr 192.168.20.207 on
GigabitEthernet0/2/0/0 from LOADING to FULL, Loading Done
RP/0/RP0/CPU0:37:12: ospf[239]: Build router LSA for area 0, router ID 1.1.1.1, seq
0x80000002
Related Commands
Command
|
Description
|
undebug
|
Enters debug mode to disable or reset multiple active debug command sessions.
|
debug ospf mda
To display debugging information for the Open Shortest Path First (OSPF) management data API (MDA), use the debug ospf mda command in EXEC mode. To turn off debugging output, use the no form of this command.
debug ospf instance-name mda
no debug ospf instance-name mda
Syntax Description
instance-name
|
Name that uniquely identifies an OSPF routing process. The instance name is any alphanumeric string no longer than 40 characters. The instance name is defined by the router ospf command.
|
Defaults
Debugging is disabled.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Caution 
The
debug ospf mda command generates a substantial amount of output. Use the command only when traffic on the IP network is low so that other activity on the system is not adversely affected.
Task ID
Task ID
|
Operations
|
ospf
|
read, write
|
Examples
The following example shows how to enable debugging information for the OSPF MDA:
RP/0/RP0/CPU0:router# debug ospf mda
Related Commands
Command
|
Description
|
undebug
|
Enters debug mode to disable or reset multiple active debug command sessions.
|
debug ospf monitor
To display debugging information for the Open Shortest Path First (OSPF) SPF (Dijkstra), use the debug ospf monitor command in EXEC mode. To turn off debugging output, use the no form of this command.
debug ospf instance-name monitor
no debug ospf instance name monitor
Syntax Description
instance-name
|
Name that uniquely identifies an OSPF routing process. The instance name is any alphanumeric string no longer than 40 characters. The instance name is defined by the router ospf command.
|
Defaults
Debugging is disabled.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Caution 
The
debug ospf monitor command generates a substantial amount of output. Use the command only when traffic on the IP network is low so that other activity on the system is not adversely affected.
Task ID
Task ID
|
Operations
|
ospf
|
read, write
|
Examples
The following is sample output from the debug ospf monitor command:
RP/0/RP0/CPU0:router# debug ospf monitor
RP/0/RP0/CPU0:40:40: ospf[239]: sched dijkstra: Schedule SPF in area 0 Change in LS ID
1.1.1.1, LSA type R,
RP/0/RP0/CPU0:40:40: ospf[239]: Begin Dijkstra for area 0 at 000002440.267000000
RP/0/RP0/CPU0:40:40: ospf[239]: initialize throttling to 500 ms
RP/0/RP0/CPU0:40:40: ospf[239]: End Dijkstra at 000002440.269000000, Total elapsed time
000000000.002000000
RP/0/RP0/CPU0:41:19: ospf[239]: initialize throttling to 500 ms
RP/0/RP0/CPU0:41:19: ospf[239]: sched dijkstra: Schedule SPF in area 0 Change in LS ID
192.168.20.207, LSA type R,
RP/0/RP0/CPU0:41:19: ospf[239]: initialize throttling to 500 ms
RP/0/RP0/CPU0:41:19: ospf[239]: %ROUTING-OSPF-5-ADJCHG : Process 1, Nbr 192.168.20.207 on
GigabitEthernet0/2/0/0 from LOADING to FULL, Loading Done
RP/0/RP0/CPU0:41:19: ospf[239]: sched dijkstra: Schedule SPF in area 0 Change in LS ID
192.168.20.207, LSA type N,
RP/0/RP0/CPU0:41:19: ospf[239]: reset throttling to 5000 ms
RP/0/RP0/CPU0:41:19: ospf[239]: Schedule SPF: spf_time 000002440.272000000 wait_interval
000000005.000000000
RP/0/RP0/CPU0:41:19: ospf[239]: Force running SPF
RP/0/RP0/CPU0:41:19: ospf[239]: sched dijkstra: Schedule SPF in area 0 Change in LS ID
0.0.0.0, LSA type R, N,
RP/0/RP0/CPU0:41:20: ospf[239]: reset throttling to 500 ms
RP/0/RP0/CPU0:41:20: ospf[239]: wait_interval 500 ms next wait_interval 5000 ms
RP/0/RP0/CPU0:41:20: ospf[239]: sched dijkstra: Schedule SPF in area 0 Change in LS ID
1.1.1.1, LSA type R,
RP/0/RP0/CPU0:41:20: ospf[239]: Begin Dijkstra for area 0 at 000002480.302000000
RP/0/RP0/CPU0:41:20: ospf[239]: End Dijkstra at 000002480.302000000, Total elapsed time
000000000.000000000
Related Commands
Command
|
Description
|
undebug
|
Enters debug mode to disable or reset multiple active debug command sessions.
|
debug ospf mpls traffic-eng advertisements
To print information about traffic engineering advertisements in OSPF link-state advertisement (LSA) messages, use the debug ospf mpls traffic-eng advertisements command in EXEC mode. To disable debugging output, use the no form of this command.
debug ospf instance-name mpls traffic-eng advertisements [access-list-name]
no debug ospf instance-name mpls traffic-eng advertisements [access-list-name]
Syntax Description
instance-name
|
Name that uniquely identifies an OSPF routing process. The instance name is any alphanumeric string no longer than 40 characters. The instance name is defined by the router ospf command.
|
access-list-name
|
(Optional) Name of a particular access control list. The name cannot contain a space or quotation mark; it may contain numbers.
|
Defaults
Debugging is disabled.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Use the debug ospf mpls traffic-eng advertisements command to observe traffic engineering advertisements passed between the OSPF protocol and Multiprotocol Label Switching traffic engineering (MPLS-TE).
Caution 
The
debug ospf mpls traffic-eng advertisements command generates a substantial amount of output. Use the command only when traffic on the IP network is low so that other activity on the system is not adversely affected.
Task ID
Task ID
|
Operations
|
ospf
|
read, write
|
Examples
The following example shows how to enable debugging information about traffic engineering advertisements in OSPF LSA messages:
RP/0/RP0/CPU0:router# debug ospf 1 mpls traffic-eng advertisements
Related Commands
Command
|
Description
|
undebug
|
Enters debug mode to disable or reset multiple active debug command sessions.
|
debug ospf nsf
To display information about OSPF nonstop forwarding (NSF) events that occur during a restart, use the debug ospf nsf command in EXEC mode. To disable debugging output, use the no form of this command.
debug ospf instance-name nsf
no debug ospf instance-name nsf
Syntax Description
instance-name
|
OSPF instance name that uniquely identifies an OSPF routing process. The instance name is any alphanumeric string no longer than 40 characters. The instance name is defined by the router ospf command.
|
Defaults
Debugging is disabled.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Use the debug ospf nsf command to track OSPF processes during NSF restart.
Caution 
The
debug ospf nsf command generates a substantial amount of output. Use the command only when traffic on the IP network is low so that other activity on the system is not adversely affected.
Task ID
Task ID
|
Operations
|
ospf
|
read, write
|
Examples
The following is sample output from the debug ospf nsf command:
RP/0/RP0/CPU0:router:router# debug ospf 1 nsf
RP/0/RP0/CPU0:52:24: ospf[239]: Extended options bit out 0x3, GigabitEthernet0/2/0/0
(lls_len 12 bytes)
RP/0/RP0/CPU0:52:24: ospf[239]: ......: if_state 0x2
RP/0/RP0/CPU0:52:24: ospf[239]: OSPF: NSF 2 Way Communication to 192.168.20.207 on
GigabitEthernet0/2/0/0, state FULL
RP/0/RP0/CPU0:52:26: ospf[239]: Extended options bit out 0x3, GigabitEthernet0/2/0/0
(lls_len 12 bytes)
RP/0/RP0/CPU0:52:28: ospf[239]: Extended options bit out 0x3, GigabitEthernet0/2/0/0
(lls_len 12 bytes)
RP/0/RP0/CPU0:52:30: ospf[239]: Extended options bit out 0x3, GigabitEthernet0/2/0/0
(lls_len 12 bytes)
RP/0/RP0/CPU0:52:32: ospf[239]: Extended options bit out 0x3, GigabitEthernet0/2/0/0
(lls_len 12 bytes)
RP/0/RP0/CPU0:52:34: ospf[239]: Extended options bit out 0x3, GigabitEthernet0/2/0/0
(lls_len 12 bytes)
RP/0/RP0/CPU0:52:36: ospf[239]: Extended options bit out 0x3, GigabitEthernet0/2/0/0
(lls_len 12 bytes)
RP/0/RP0/CPU0:52:38: ospf[239]: Extended options bit out 0x3, GigabitEthernet0/2/0/0
(lls_len 12 bytes)
RP/0/RP0/CPU0:52:40: ospf[239]: Extended options bit out 0x3, GigabitEthernet0/2/0/0
(lls_len 12 bytes)
RP/0/RP0/CPU0:52:42: ospf[239]: Extended options bit out 0x3, GigabitEthernet0/2/0/0
(lls_len 12 bytes)
RP/0/RP0/CPU0:52:44: ospf[239]: OSPF process 1: NSF RESTART TIMER period 1 expired
RP/0/RP0/CPU0:52:44: ospf[239]: OSPF: OOB Resync scheduled for 192.168.20.207 on
GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:52:45: ospf[239]: OSPF: Starting OOB-Resync with 192.168.20.207 address
192.168.20.207 on GigabitEthernet0/2/0/0 (requester)
RP/0/RP0/CPU0:52:45: ospf[239]: %ROUTING-OSPF-5-ADJCHG : Process 1, Nbr 192.168.20.207 on
GigabitEthernet0/2/0/0 from LOADING to FULL, Loading Done
RP/0/RP0/CPU0:52:45: ospf[239]: OSPF: NSF interface count-: 0 (area 0),
GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:52:45: ospf[239]: OSPF process 1: oob-resync completed for all neighbors
RP/0/RP0/CPU0:52:45: ospf[239]: OSPF: scheduling rtr lsa for area 0
RP/0/RP0/CPU0:52:45: ospf[239]: OSPF: OOB-Resync completed with 192.168.20.207 address
192.168.20.207 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:52:45: ospf[239]: OSPF: no change in router LSA, area 0 (reset
db_nsf_active)
Related Commands
Command
|
Description
|
undebug
|
Enters debug mode to disable or reset multiple active debug command sessions.
|
debug ospf packet
To display information about each OSPF packet transmitted and received, use the debug ospf packet command in EXEC mode. To disable debugging output, use the no form of this command.
debug ospf instance-name packet [interface-type interface-instance]
no debug ospf instance-name packet [interface-type interface-instance]
Syntax Description
instance-name
|
OSPF instance name that uniquely identifies an OSPF routing process. The instance name is any alphanumeric string no longer than 40 characters. The instance name is defined by the router ospf command.
|
interface-type
|
(Optional) Interface type. For more information, use the question mark (?) online help function.
|
interface-instance
|
(Optional) Either a physical interface instance or a virtual interface instance as follows:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the modular services card or line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range varies depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
Defaults
Debugging is disabled.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Use the debug ospf packet command to display the receipt of OSPF packets producing one set of information for each packet received. The output varies slightly depending on which authentication is used.
Caution 
The
debug ospf packet command generates a substantial amount of output. Use the command only when traffic on the IP network is low so that other activity on the system is not adversely affected.
Task ID
Task ID
|
Operations
|
ospf
|
read, write
|
Examples
The following is sample output from the debug ospf packet command:
RP/0/RP0/CPU0:router# debug ospf 1 packet
RP/0/RP0/CPU0:55:10: ospf[239]: Recv: ACK l:44 rid:192.168.20.207 aut:0 auk: from
192.168.20.207 to 224.0.0.5 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:18: ospf[239]: Send: HLO l:48 rid:1.1.1.1 aut:0 auk: from 192.168.20.206
to 224.0.0.5 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:20: ospf[239]: Recv: HLO l:48 rid:192.168.20.207 aut:0 auk: from
192.168.20.207 to 224.0.0.5 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:28: ospf[239]: Send: HLO l:48 rid:1.1.1.1 aut:0 auk: from 192.168.20.206
to 224.0.0.5 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:30: ospf[239]: Recv: HLO l:48 rid:192.168.20.207 aut:0 auk: from
192.168.20.207 to 224.0.0.5 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:38: ospf[239]: Send: HLO l:48 rid:1.1.1.1 aut:0 auk: from 192.168.20.206
to 224.0.0.5 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:40: ospf[239]: Recv: HLO l:48 rid:192.168.20.207 aut:0 auk: from
192.168.20.207 to 224.0.0.5 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:48: ospf[239]: Send: DBD l:32 rid:1.1.1.1 aut:0 auk: from 192.168.20.206
to 192.168.20.207 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:48: ospf[239]: Send: HLO l:48 rid:1.1.1.1 aut:0 auk: from 192.168.20.206
to 224.0.0.5 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:48: ospf[239]: Recv: DBD l:32 rid:192.168.20.207 aut:0 auk: from
192.168.20.207 to 192.168.20.206 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:48: ospf[239]: Send: DBD l:52 rid:1.1.1.1 aut:0 auk: from 192.168.20.206
to 192.168.20.207 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:48: ospf[239]: Recv: DBD l:72 rid:192.168.20.207 aut:0 auk: from
192.168.20.207 to 192.168.20.206 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU00:55:48: ospf[239]: Send: REQ l:48 rid:1.1.1.1 aut:0 auk: from
192.168.20.206 to 192.168.20.207 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:48: ospf[239]: Send: DBD l:32 rid:1.1.1.1 aut:0 auk: from 192.168.20.206
to 192.168.20.207 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:48: ospf[239]: Recv: UPD l:96 rid:192.168.20.207 aut:0 auk: from
192.168.20.207 to 192.168.20.206 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:48: ospf[239]: Recv: REQ l:36 rid:192.168.20.207 aut:0 auk: from
192.168.20.207 to 192.168.20.206 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:48: ospf[239]: %ROUTING-OSPF-5-ADJCHG : Process 1, Nbr 192.168.20.207 on
GigabitEthernet0/2/0/0 from LOADING to FULL, Loading Done
RP/0/RP0/CPU0:55:48: ospf[239]: Send: UPD l:64 rid:1.1.1.1 aut:0 auk: from 192.168.20.206
to 192.168.20.207 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:49: ospf[239]: Send: UPD l:64 rid:1.1.1.1 aut:0 auk: from 192.168.20.206
to 224.0.0.5 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:50: ospf[239]: Recv: HLO l:48 rid:192.168.20.207 aut:0 auk: from
192.168.20.207 to 224.0.0.5 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:50: ospf[239]: Send: ACK l:64 rid:1.1.1.1 aut:0 auk: from 192.168.20.206
to 224.0.0.5 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:50: ospf[239]: Recv: ACK l:44 rid:192.168.20.207 aut:0 auk: from
192.168.20.207 to 224.0.0.5 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:54: ospf[239]: Send: UPD l:64 rid:1.1.1.1 aut:0 auk: from 192.168.20.206
to 192.168.20.207 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:56: ospf[239]: Recv: ACK l:44 rid:192.168.20.207 aut:0 auk: from
192.168.20.207 to 224.0.0.5 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:55:58: ospf[239]: Send: HLO l:48 rid:1.1.1.1 aut:0 auk: from 192.168.20.206
to 224.0.0.5 on GigabitEthernet0/2/0/0
RP/0/RP0/CPU0:56:0: ospf[239]: Recv: HLO l:48 rid:192.168.20.207 aut:0 auk: from
192.168.20.207 to 224.0.0.5 on GigabitEthernet0/2/0/0
Related Commands
Command
|
Description
|
debug ospf events
|
Displays information on OSPF-related events, such as adjacencies, flooding information, designated router selection, and SPF calculation.
|
undebug
|
Enters debug mode to disable or reset multiple active debug command sessions.
|
debug ospf rib
To display information about the interaction between the OSPF process and the Routing Information Base (RIB), use the debug ospf rib command in EXEC mode. To disable debugging output, use the no form of this command.
debug ospf instance-name rib [access-list-name]
no debug ospf instance-name rib [access-list-name]
Syntax Description
instance-name
|
OSPF instance name that uniquely identifies an OSPF routing process. The instance name is any alphanumeric string no longer than 40 characters. The instance name is defined by the router ospf command.
|
access-list-name
|
(Optional) Name of a particular access list. The name cannot contain a space or quotation mark; it may contain numbers.
|
Defaults
Debugging is disabled.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Use the debug ospf rib command to trace RIB being redistributed into the OSPF process, which results in the origination of Type 5 or Type 7 LSAs.
Caution 
The
debug ospf rib command generates a substantial amount of output. Use the command only when traffic on the IP network is low so that other activity on the system is not adversely affected.
Task ID
Task ID
|
Operations
|
ospf
|
read, write
|
Examples
The following example shows how to enable debugging information about the interaction between the OSPF process and the RIB:
RP/0/RP0/CPU0:router# debug ospf 1 rib
Related Commands
Command
|
Description
|
undebug
|
Enters debug mode to disable or reset multiple active debug command sessions.
|
debug ospf rtrid
To display debugging information for the Open Shortest Path First (OSPF) router ID assignment, use the debug rtrid command in EXEC mode. To turn off debugging output, use the no form of this command.
debug ospf instance-name rtrid
no debug ospf instance-name rtrid
Syntax Description
instance-name
|
OSPF instance name that uniquely identifies an OSPF routing process. The instance name is any alphanumeric string no longer than 40 characters. The instance name is defined by the router ospf command.
|
Defaults
Debugging is disabled.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Caution 
The
debug ospf rtrid command generates a substantial amount of output. Use the command only when traffic on the IP network is low so that other activity on the system is not adversely affected.
Task ID
Task ID
|
Operations
|
ospf
|
read, write
|
Examples
The following is sample output from the debug ospf rtrid command:
RP/0/RP0/CPU0:router# debug ospf rtrid
RP/0/RP0/CPU0:1h:4:9: ospf[239]: RID: Deleting router-id SysDB tuple
RP/0/RP0/CPU0:1h:4:9: ospf[239]: RID: Checking for old router id
RP/0/RP0/CPU0:1h:4:9: ospf[239]: RID: Checking for configured router id
RP/0/RP0/CPU0:1h:4:9: ospf[239]: RID: Router-id set by numeric configuration: 1.1.1.1
Related Commands
Command
|
Description
|
undebug
|
Enters debug mode to disable or reset multiple active debug command sessions.
|
debug ospf spf
To display information about OSPF packet events, use the debug ospf spf command in EXEC mode. To disable debugging output, use the no form of this command.
debug ospf instance-name spf {external access-list-name | inter access-list-name | intra
access-list-name | topology access-list-name}
no debug ospf instance-name spf {external access-list-name | inter access-list-name | intra
access-list-name | topology access-list-name}
Syntax Description
instance-name
|
OSPF instance name that uniquely identifies an OSPF routing process. The instance name is any alphanumeric string no longer than 40 characters. The instance name is defined by the router ospf command.
|
external
|
Displays information on shortest path first (SPF) for external nodes.
|
access-list-name
|
Name of an IP access control list.
|
inter
|
Displays information on inter-area SPF calculations
|
intra
|
Displays information on intra-area SPF (Dijkstra) calculations.
|
topology
|
Displays information on topology (route) calculations.
|
Defaults
Debugging is disabled.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
For insights into the intraarea SPF calculation (link-state advertisement (LSA) Types 1 and 2), use the intra option.
For interarea summary processing (LSA Types 3 and 4), use the inter option.
For external (LSA Types 5 and 7), use the external option.
For tracking the creation and deletion of routes, use the topology option.
Caution 
The
debug ospf spf command generates a substantial amount of output. Use the command only when traffic on the IP network is low so that other activity on the system is not adversely affected.
Task ID
Task ID
|
Operations
|
ospf
|
read, write
|
Examples
The following is sample output from the debug ospf spf command:
RP/0/RP1/CPU0:router# debug ospf 1 spf intra accessintra
RP/0/RP1/CPU0:1h:26:1: ospf[239]: Add better path to LSA ID 192.168.20.255, gateway
192.168.20.0, dist 1
RP/0/RP1/CPU0:1h:26:1: ospf[239]: Add path: next-hop 192.168.20.206, interface
GigabitEthernet0/2/0/0
RP/0/RP1/CPU0:1h:26:1: ospf[239]: Adding Stub nets
RP/0/RP1/CPU0:1h:26:1: ospf[239]: Add Network Route to 192.168.20.0 Mask 255.255.255.0.
Metric: 1, Next Hop: 192.168.20.206
RP/0/RP1/CPU0:1h:26:1: ospf[239]: delete old routes: area 0
RP/0/RP1/CPU0:1h:26:1: ospf[239]: OSPF: ospf_gen_asbr_sum_all_areas
RP/0/RP1/CPU0:1h:26:41: ospf[239]: %ROUTING-OSPF-5-ADJCHG : Process 1, Nbr 192.168.20.207
on GigabitEthernet0/2/0/0 from LOADING to FULL, Loading Done
RP/0/RP1/CPU0:1h:26:41: ospf[239]: process dijkstra: area 0
RP/0/RP1/CPU0:1h:26:41: ospf[239]: Initializing to run spf
RP/0/RP1/CPU0:1h:26:41: ospf[239]: It is a router LSA 1.1.1.1. Link Count 1
RP/0/RP1/CPU0:1h:26:41: ospf[239]: Processing link 0, id 192.168.20.207, link data
192.168.20.206, type 2
RP/0/RP1/CPU0:1h:26:41: ospf[239]: Add better path to LSA ID 192.168.20.207, gateway
192.168.20.206, dist 1
RP/0/RP1/CPU0:1h:26:41: ospf[239]: Add path: next-hop 192.168.20.206, interface
GigabitEthernet0/2/0/0
RP/0/RP1/CPU0:1h:26:41: ospf[239]: Add Network Route to 192.168.20.0 Mask 255.255.255.0.
Metric: 1, Next Hop: 192.168.20.206
RP/0/RP1/CPU0:1h:26:41: ospf[239]: It is a network LSA 192.168.20.207. Router Count 2
RP/0/RP1/CPU0:1h:26:41: ospf[239]: Processing router id 1.1.1.1
RP/0/RP1/CPU0:1h:26:41: ospf[239]: New newdist 1 olddist 0
RP/0/RP1/CPU0:1h:26:41: ospf[239]: Processing router id 192.168.20.207
RP/0/RP1/CPU0:1h:26:41: ospf[239]: Add better path to LSA ID 192.168.20.207, gateway
192.168.20.207, dist 1
RP/0/RP1/CPU0:1h:26:41: ospf[239]: Add path: next-hop 192.168.20.207, interface
GigabitEthernet0/2/0/0
RP/0/RP1/CPU0:1h:26:41: ospf[239]: It is a router LSA 192.168.20.207. Link Count 1
RP/0/RP1/CPU0:1h:26:41: ospf[239]: Processing link 0, id 192.168.20.207, link data
192.168.20.207, type 2
RP/0/RP1/CPU0:1h:26:41: ospf[239]: Ignore newdist 2 olddist 1
RP/0/RP1/CPU0:1h:26:41: ospf[239]: Adding Stub nets
RP/0/RP1/CPU0:1h:26:41: ospf[239]: delete old routes: area 0
RP/0/RP1/CPU0:1h:26:41: ospf[239]: OSPF: ospf_gen_asbr_sum_all_areas
Related Commands
Command
|
Description
|
undebug
|
Enters debug mode to disable or reset multiple active debug command sessions.
|
debug ospf tree
To display debugging information for the Open Shortest Path First (OSPF) database tree, use the debug ospf tree command in EXEC mode. To turn off debugging output, use the no form of this command.
debug ospf instance-name tree
no debug ospf instance-name tree
Syntax Description
instance-name
|
OSPF instance name that uniquely identifies an OSPF routing process. The instance name is any alphanumeric string no longer than 40 characters. The instance name is defined by the router ospf command.
|
Defaults
Debugging is disabled.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced on the Cisco CRS-1.
|
Release 3.0
|
No modification.
|
Release 3.2
|
This command was supported on the Cisco XR 12000 Series Router.
|
Release 3.3.0
|
No modification.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Caution 
The
debug ospf tree command generates a substantial amount of output. Use the command only when traffic on the IP network is low so that other activity on the system is not adversely affected.
Task ID
Task ID
|
Operations
|
ospf
|
read, write
|
Examples
The following example shows how to enable debugging information for the OSPF database tree:
RP/0/RP0/CPU0:router# debug ospf 1 tree
Related Commands
Command
|
Description
|
undebug
|
Enters debug mode to disable or reset multiple active debug command sessions.
|
debug ospf uv
To display debugging information about Open Shortest Path First (OSPF) global verifier events, use the debug ospf uv command in EXEC mode. To turn off debugging output, use the no form of this command.
debug ospf instance-name uv
no debug ospf instance-name uv
Syntax Description
instance-name
|
OSPF instance name that uniquely identifies an OSPF routing process. The instance name is any alphanumeric string no longer than 40 characters. The instance name is defined by the router ospf command.
|
Defaults
Debugging is disabled.
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 3.3.0
|
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.
Caution 
The
debug ospf uv command generates a substantial amount of output. Use the command only when traffic on the IP network is low so that other activity on the system is not adversely affected.
Task ID
Task ID
|
Operations
|
ospf
|
read, write
|
Examples
The following example shows how to enable debugging information for OSPF global verifier events:
RP/0/RP0/CPU0:router# debug ospf 1 uv
Related Commands
Command
|
Description
|
undebug
|
Enters debug mode to disable or reset multiple active debug command sessions.
|