Cisco ospf syslog messages

[Carlton Patterson]

Hello Community,

Can someone please tell me if the following messages are flagged should a ospf %OSPF-5-ADJCHG occur?

badVersion 1

areaMismatch 2

unknownNbmaNbr 3

unknownVirtualNbr 4

authTypeMismatch 5

authFailure 6

netMaskMismatch 7

helloIntervalMismatch 8

deadIntervalMismatch 9

optionMismatch 10

mtuMismatch 11

duplicateRouterId 12

noError 13

Cheers

Carlton

[mahmoodmkl]

Hi,

The adjacency will not occur due to below reasons.

1.area ID mismatch.

2.subnet mismatch.

3.autentication mismatch.

4.hello/dead intervals mismatch.

5.mtu mismatch.

Thanks

[Carlton Patterson]

mahmood,

Thanks for responding. I understand that an adjacency won't occur for the reasons you mentioned. My question is will any of those reason appear in a syslog message if for example an existing adjacency disappeared for any of those reasons?

Cheers

[cadet alain]

Hi,

no it will only tell you that it went from FULL to Down but  in certain cases you'll receive other OSPF syslog messages

indicating the problem

for example let's change the area on one side:

%OSPF-5-ADJCHG: Process 1, Nbr 10.0.0.2 on FastEthernet0/0 from FULL to DOWN, Neighbor Down: Interface down or detached

%OSPF-6-AREACHG: 10.0.0.1/32 changed from area 0 to area 1

%OSPF-4-ERRRCV: Received invalid packet: mismatch area ID, from backbone area must be virtual-link but not found from 10.0.0.2, FastEthernet0/0

Regards.

Alain

Don't forget to rate helpful posts.

[mahmoodmkl]

Hi

afaik they appear on the console


Sent from Cisco Technical Support iPhone App

[cadet alain · Accepted solution]

Hi,

if we change hello-interval on one side then the adjency will go down but we won't receive any message indicating this is a mistmatched hello parameter which is the cause.

Regards.

Alain

Don't forget to rate helpful posts.

[Carlton Patterson]

Cadet,

This is exactly what I thought.

Cheers mate.