9-2 log adjacency-changes detail

9-2 log adjacency -changes detail

Syntax Description:

This command has no arguments.

Purpose: To enable the logging of changes in an OSPF neighbor's status. If the UNIX syslog facility is enabled, messages can be sent to a UNIX host running the syslog daemon. If you are not using the UNIX syslog facility, then the status change messages are stored in the router's internal buffer. This command is an excellent tool for troubleshooting OSPF.

Initial Cisco IOS Software Release: 11.2. The detail keyword was added in 12.1.

Configuration Example 1: Enabling OSPF Neighbor Status-Change Logging to the Console

To enable the display of OSPF neighbor status-change events on the console, use the following configuration.

  router ospf 1    log-adjacency-changes   

Verification

When the state of an OSPF neighbor changes, the events are displayed on the console. For example, if you execute the command clear ip ospf process on an OSPF neighbor, the following output should be displayed.

 rtrA#  clear ip ospf process  Reset ALL OSPF processes? [no]: y rtrA# 00:52:14: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Ethernet0/0 from FULL to DOW N, Neighbor Down: Interface down or detached 00:52:23: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Ethernet0/0 from LOADING to FULL, Loading Done 

If the keyword detail is used, then complete information regarding the neighbor status will be logged.

  router ospf 1    log-adjacency-changes detail   rtrA#  clear ip ospf process  Reset ALL OSPF processes? [no]:  yes  rtrA# 00:50:12: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Ethernet0/0 from FULL to DOW N, Neighbor Down: Interface down or detached 00:50:13: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Ethernet0/0 from DOWN to INI T, Received Hello 00:50:13: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Ethernet0/0 from INIT to 2WA Y, 2-Way Received 00:50:13: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Ethernet0/0 from 2WAY to EXS TART, AdjOK? 00:50:13: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Ethernet0/0 from EXSTART to EXCHANGE, Negotiation Done 00:50:13: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Ethernet0/0 from EXCHANGE to  LOADING, Exchange Done 00:50:13: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Ethernet0/0 from LOADING to FULL, Loading Done 

Configuration Example 2: Enabling OSPF Neighbor Status-Change Logging to Memory

Use the following configuration to enable the logging of OSPF neighbor status-change events to memory.

   logging buffered 4096 debugging    !   router ospf 1    log-adjacency-changes detail   

The parameters 4096 and debugging are default values and are supplied by the router when you use the command logging buffered. The default values vary by platform.

Verification

The show logging command displays the status of buffered logging. If logging is enabled, then the contents of the buffer will be displayed.

 rtrA#  show logging  Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes,  0 overruns)     Console logging: level debugging, 67 messages logged     Monitor logging: level debugging, 0 messages logged     Buffer logging: level debugging, 8 messages logged     Logging Exception size (4096 bytes)     Trap logging: level informational, 71 message lines logged Log Buffer (4096 bytes): 00:56:38: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Ethernet0/0 from FULL to DOW N, Neighbor Down: Interface down or detached 00:56:43: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Ethernet0/0 from DOWN to INI T, Received Hello 00:56:43: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Ethernet0/0 from INIT to 2WA Y, 2-Way Received 00:56:43: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Ethernet0/0 from 2WAY to EXS TART, AdjOK? 00:56:43: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Ethernet0/0 from EXSTART to EXCHANGE, Negotiation Done 00:56:43: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Ethernet0/0 from EXCHANGE to  LOADING, Exchange Done 00:56:43: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Ethernet0/0 from LOADING to FULL, Loading Done 

Troubleshooting

Step 1. Verify that the OSPF neighbors have established a relationship.

Step 2. Verify that buffered logging is enabled using the show logging command.