CCNP TSHOOT 6.0 - Cisco Learning Home

CCNPv6 TSHOOT
*Nov 5 03:03:13.845: OSPF: Rcv hello from 10.1.211.1 area 0 from Vlan200 10.1.2
00.252
*Nov 5 03:03:13.845: OSPF: End of hello processing
DLS2#
*Nov 5 03:03:16.051: OSPF: Send hello to 224.0.0.5 area 0 on FastEthernet0/5 fr
om 10.1.2.13
*Nov 5 03:03:16.286: OSPF: Rcv hello from 10.1.203.1 area 0 from FastEthernet0/
5 10.1.2.14
*Nov 5 03:03:16.286: OSPF: Mismatched hello parameters from 10.1.2.14
*Nov 5 03:03:16.286: OSPF: dead R 40 C 15, hello R 10 C 5 Mask R 255.255.255.2
52 C 255.255.255.252
DLS2#
DLS2#undebug all
All possible debugging has been turned off
DLS2#
*Nov 5 03:03:28: %OSPF-5-ADJCHG: Process 1, Nbr 10.1.203.1 on FastEthernet0/5 f
rom FULL to DOWN, Neighbor Down: dead timer expired
A third debug command that can be useful in troubleshooting the establishment of OSPF neighbor relationships
is debug ip ospf events. This command displays the same information that is displayed by the debug ip
ospf adj command, but it also displays the transmission and reception of hello packets and reports mismatches
in the hello parameters.
Confirming the transmission of hello packets by using this command can be useful because the debug ip ospf
packet or debug ip ospf adj commands do not display the transmission of hello packets.
You can also use this command to display the reception of invalid hello packets. If there is a mismatch between
the neighbors in the hello parameters that prevents the neighbor relationship from forming, this command displays
the type of parameter mismatch and the value of the mismatched parameters. It displays mismatches for the
following parameters:
• Hello and dead timers
• Area ID
• Subnet and subnet mask
• Authentication type and authentication data
• Flags that signify the area type, such as stub or not-so-stubby area (NSSA)
Because this command displays more events, it is often better to first enable the debug ip ospf adj
command and only use the debug ip ospf event command if you did not get the information you need.
All contents are Copyright © 1992–2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 25 of 39