debug IP ospf adj Versus debug IP ospf events in packet tracer

MrXpert

I've been getting used to seeing the output from using the debug ip ospf adj and debug ip ospf events commands in packet tracer and the out put normally may look a bit like this:

HQ-R1#show debug
IP routing:
OSPF events debugging is on
00:09:24: OSPF: Rcv hello from 1.1.1.1 area 0 from Serial0/3/0 192.168.0.1

00:09:24: OSPF: Mismatched hello parameters from 192.168.0.1

00:09:24: OSPF: Dead R 60 C 60 Hello R 16 C 15 Mask R 255.255.255.252 C 255.255


ROUTER-A#show debug
IP routing:
OSPF adjacency events debugging is on
ROUTER-A(config-if)#
00:10:14: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Serial0/3/0 from FULL to DOWN, Neighbor Down: Dead timer expired

00:10:14: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Serial0/3/0 from FULL to Down: Interface down or detached

00:10:14: OSPF: Build router LSA for area 0, router ID 1.1.1.1, seq 0x80000004

00:10:19: OSPF: Build summary LSA for area 0, router ID 1.1.1.1, seq 0x80000007

I intentionally altered the Hello intervals to get a mismatched parameter and this is clearly shown using the "debug ip ospf events" command in PT
However what has got me a bit miffed is cbt nuggets, train signal state,Odom say that the command "debug ip ospf adj" is the one to use when it comes to seeing the mismatched parameters.
Obviously in my actual output above using debug ip ospf events in PT is actually the more useful command.

Is this a bug in packet tracer? have they got it arse about face? can anyone confirm please? i dont have any real equipment to test it on

dtlokee

No it's not a bug in packet tracer they look the same as the debugs on the real equipment. Maybe they were referring to mismatched area id and not the hello and dead timers?