What Are the Meanings of Common OSPF Logs Highlighted

Latest reply: Oct 30, 2018 09:46:34 1091 8 10 0
What are the meanings of the following OSPF logs?
  • IF_CHG_E

The meanings are described as follows:

  • Feb 13 2009 17:10:52 LL-NE40E-1 %OSPF/3/NBR_CHG_DOWN(l): Neighbor event:neighbor state changed to Down. (ProcessId=1, NeighborAddress=, NeighborEvent=InactivityTimer, NeighborPreviousState=Full, NeighborCurrentState=Down)

    Log description: The neighbor relationship on the interface with the IP address changed from the Full state to the Down state. The status change reason is InactivityTimer, meaning that no Keepalive message is received from the neighbor in the DeadInterval configured on the OSPF interface.

    The other possible causes are listed below:
    • KillNbr: An interface or a BFD session went Down, or an OSPF process was reset.
    • LLDown: A VLANIF, trunk, or serial interface went Down.
    • SeqNumberMismatch: A fault occurred in route transmission between OSPF neighbors, or due to a transmission delay on links, the remote device received a Keepalive message from the local device after the OSPF neighbor relationship went Down and then sent a DD packet to the local device that is in the Full state.
  • May 10 2009 14:13:00 R13 %OSPF/6/NBR_CHANGE_E(l): Neighbor changes event: neighbor status changed. (ProcessId=1, NeighborAddress=, NeighborEvent=1-Way, NeighborPreviousState=Full, NeighborCurrentState=Init)

    Log description: The neighbor relationship on the interface with the IP address changed from the Full state to the Init state. The status change reason is 1-way, meaning that the local device received a Hello packet requesting for initializing the neighbor relationship.

    Reason for generating this log: The OSPF neighbor relationship on the remote device went Down, and the remote device sent an initialization packet to the local device. After having received the packet, the OSPF neighbor relationship on the local device also went Down.

  • May 12 2009 14:23:58 R13 %OSPF/6/IF_CHG_E(l): Interface received event InterfaceDown, interface state changed from DR to Down. (Process ID=1)

    Log description: The interface (where DR is configured) with the IP address went Down. The status change reason is that the interface received a neighbor interface Down event. Usually a physical interface went Down.

    The other possible causes are listed below:

    NeighborChange: After the DR on a broadcast network went Down, the BDR became a DR.

  • x
  • convention:

Created Sep 8, 2018 07:02:01 Helpful(1) Helpful(1)

Very helpful!!
  • x
  • convention:

MVE Created Sep 28, 2018 13:37:35 Helpful(1) Helpful(1)

that's verygoold to read
such articles are hard to find
  • x
  • convention:

Created Sep 29, 2018 05:51:15 Helpful(1) Helpful(1)

I am very interested for this post, which is very helpful to our daily troubleshooting. I always have similar problems in my daily work, but I do not know how to deal with them. Now I have a clear idea. Thank you very much for your sharing. Hope you can update continue like this
  • x
  • convention:

Created Sep 29, 2018 05:59:36 Helpful(1) Helpful(1)

I am very interested for this post, which is very helpful to our daily troubleshooting. When these print records appear in the log, is there a single possibility?
  • x
  • convention:

Created Sep 29, 2018 06:35:02 Helpful(1) Helpful(1)

Thanks for you share about this which is very useful for my daily troubleshooting.
And now i can easy to check the ospf logs if i face any issue about this.before this i aways do not know how to deal with them,and wasted a lot of time to serch this.Thanks agin for you selfless Sharing, Hope you can aways work like this. :):):):)
  • x
  • convention:

Created Sep 29, 2018 06:58:13 Helpful(1) Helpful(1)

This is exactly what I was looking for. I have been stuck for a long time on this problem. you gave me a very good idea ,I very much appreciate it.

Please keep on post and share more cases for all of us:)
  • x
  • convention:

Good Good Study Day Day Up
Created Sep 30, 2018 08:55:21 Helpful(0) Helpful(0)

I have encountered this question about you. I have checked a lot of information, but I still have not answered this question clearly. Thank you for sharing this knowledge and solving my doubts. I hope that you can continue to update such knowledge points. Thank you. !
  • x
  • convention:

Created Oct 30, 2018 09:46:34 Helpful(0) Helpful(0)

Thanks for your sharing, normally, the OSPF is a very important protocol and very common, so the logs are also very important for checking the issue of OSPF, this post is very good for us to understand the logs, thanks again
  • x
  • convention:


You need to log in to reply to the post Login | Register

Notice Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " Privacy."
If the attachment button is not available, update the Adobe Flash Player to the latest version!
Login and enjoy all the member benefits

Login and enjoy all the member benefits