1 What Does Each Error Value in the Output of the display ospf error Command Mean?

Latest reply: Aug 25, 2017 15:21:46 1837 1 0 0

1      What Does Each Error Value in the Output of the display ospf error Command Mean?

·         General packet errors: indicates the statistics about general packet errors.

o    IP: received my own packet: indicates that a device receives a packet with the source address being the IP address of the device.

Cause: A Layer 2 loop occurs.

o    Bad packet: indicates that an error packet is received.

The causes are listed as follows:

      • The router ID contained in the received packet is 0.
      • The sum of the IP header length and packet length is different from the length of the packet received by socket.
      • The packet length is incorrect in the following situations:
        • The IP header length is smaller than the length of the OSPF packet.
        • The length of the OSPF packet is smaller than the length of a Hello packet header.
        • The length of the OSPF packet is smaller than the length of a DD packet header.
        • The length of the OSPF packet is smaller than the length of a Request packet header.
        • The length of the OSPF packet is smaller than the length of an Update packet header.
        • The number of LSAs in an Update packet is inconsistent with the number of calculated LSAs.
        • The length of the OSPF packet is smaller than the length of an ACK packet.
      • The type value of the OSPF packet is greater than 5.
      • An error is returned during packet processing.
      • An error occurs during packet parse.

o    Bad version: indicates that the version number is incorrect.

Cause: The OSPF version number contained in the received packet is not 2.

    • Bad checksum: indicates that the checksum is incorrect. The value is not counted.

o    Bad area id: indicates that a packet is received from an area that the interface does not belong to.

Cause: The area whose ID is changed is restarted and a retransmitted packet is received.

o    Drop on unnumbered interface: indicates the number of packets discarded by an unnumbered P2P interface.

Cause: The OSPF network type configured on the unnumbered P2P interface is not P2P.

o    Bad virtual link: indicates the number of error packets received on the Vlink.

The causes are listed as follows:

      • The Vlink is a null link and the packet is received from an area that the interface does not belong to.
      • The current status of the interface that receives the packet is not P2P.
      • The router ID contained in the packet is not the router ID of the neighbor on the Vlink.

o    Bad authentication type: indicates that the authentication type is incorrect.

The causes are listed as follows:

      • The calculated checksum is inconsistent with the one filled in the packet header by the sender.
      • Null authentication fails.
      • Simple authentication fails.
      • MD5 authentication fails.

o    Bad authentication key: indicates that the authentication key is incorrect.

The causes are listed as follows:

      • The null authentication is incorrect and the returned type value of the authentication error is 0.
      • The simple authentication is incorrect and the returned type value of the authentication error is 2.
      • The MD5 authentication is incorrect and the authentication error type is returned.
      • Other errors occur and the returned type value of the authentication error is 1.

o    Packet too small: indicates that a packet of an improper length is received.

Cause: The sum of the IP header length and packet length is different from the length of the packet received by socket.

    • Packet size > ip length: indicates that the packet length is greater than the specified value. This value is not counted.

o    Transmit error: indicates that the packet is incorrectly transmitted.

Cause: The packet fails to be transmitted.

o    Interface down: indicates the number of OSPF interfaces in the Down state.

Cause: The count is increased by 1 each time an OSPF interface becomes Down.

o    Unknown neighbor: indicates that there is no corresponding neighbor.

The causes are listed as follows:

      • A non-Hello packet is received but there is no corresponding neighbor.
      • The packet is received on the Vlink but there is no corresponding neighbor.
      • The packet is received in an NBMA network but there is no corresponding neighbor.

o    Netmask mismatch: indicates that the network mask is unmatched.

Cause: The mask contained in the header of the Hello packet received in a non-P2P network is inconsistent with the mask of the interface that receives the packet.

·         HELLO packet errors: indicates the statistics about Hello packet errors.

o    Hello timer mismatch: The values of the Hello timers on the two ends of a link are inconsistent.

Cause: The set values of the Hello timers on the two ends of a link are different.

o    Dead timer mismatch: indicates the values of the dead timers on the two ends of a link are inconsistent.

Cause: The values of the dead timers on the two ends of a link are different.

o    Extern option mismatch: indicates that the Option bits in Hello packets mismatch.

The causes are listed as follows:

      • The received Hello packet carries the E bit and NP bit.
      • The Hello packet with the E bit is received in the stub area.
      • The Hello packet with the E bit is not received in a common area.
      • The Hello packet without the NP bit is received in the NSSA.
      • The Hello packet with the NP bit is received in a common area.

o    Router id confusion: indicates that router IDs conflict.

Cause: The router IDs of two neighboring devices conflict (note: this count is applicable to only the case that the router IDs of two neighboring devices conflict, and is inapplicable to router ID conflict on the entire network).

o    Virtual neighbor unknown: indicates an unknown neighbor on a Vlink.

Cause: The router ID in the received Hello packet is different from that of the neighbor on the Vlink.

o    NBMA neighbor unknown: indicates an unknown NBMA neighbor.

Cause: The network type of the neighbor contained in the received Hello packet is NBMA, but the NBMA neighbor does not exist.

o    Invalid Source Address: indicates that the source address of the packet is invalid.

Cause: The Hello packet is received but there is no corresponding neighbor.

·         DD packet errors: indicates the statistics about DD packet errors.

o    Neighbor state low: indicates that status of the neighbor that receives the DD packet is low.

The causes are listed as follows:

      • The neighbor in the Down or Attempt state receives the DD packet.
      • The neighbor in the state lower than Exchange receives an LSRequest packet.
      • The neighbor in the state lower than Exchange receives an Update packet.
      • The neighbor in the state lower than Exchange receives an ACK packet.
    • Router id confusion: is not used.
    • Extern option mismatch: is the same as that in a Hello packet.
    • Unknown LSA type: is not used.

o    MTU option mismatch: indicates that the MTU in the received DD packet is greater than that configured on the interface.

Cause: The MTU in the received DD packet is greater than the OSPF MTU configured on the interface.

·         LS ACK packet errors: indicates the statistics about LSAck packet errors.

o    Neighbor state low: is the same as that in a DD packet.

o    Bad ack: indicates that an ACK packet in which the LSA is unmatched with that in the retransmission list in terms of the contents and age is received.

Cause: The LSA contained in the ACK packet sent by the neighbor is unmatched with that in the retransmission list in terms of the contents and age.

o    Duplicate ack: indicates duplicate ACK packets.

Cause: An Ack packet is replied several times for an LSA. This count is not considered as an error on a broadcast network.

    • Unknown LSA type: is not used.

·         LS REQ packet errors: indicates the statistics about LSRequest packet errors.

    • Neighbor state low: is not used.
    • Empty request: is not used.

o    Bad request: indicates that an incorrect request packet is received.

The causes are listed as follows:

      • Duplicate LSAs are received from the neighbor but the LSA still exists in the request list.
      • An old LSA is received from the neighbor but the LSA still exists in the request list.
      • A request packet is received from the neighbor but the requested LSA is null on the local node.

·         LS UPD packet errors: indicates the statistics about Update packet errors.

    • Neighbor state low: is not used.
    • Newer self-generate LSA: is not used.
    • LSA checksum bad: is not used.

o    Received less recent LSA: indicates that an LSA that is older than that in the LSDB is received.

Cause: An older LSA is received, that is, the device has a new LSA.

    • Unknown LSA type: is not used.

·         Opaque errors: indicates statistics about Opaque LSA errors.

o    9-out of flooding scope: indicates that the flooding of Type 9 LSAs is out of the flooding range.

Cause: Type 9 Opaque LSAs are received but the Opaque capability is not enabled.

o    10-out of flooding scope: indicates that the flooding of Type 10 LSAs is out of the flooding range.

Cause: Type 10 Opaque LSAs are received but the Opaque capability is not enabled.

o    11-out of flooding scope: indicates that the flooding of Type 11 LSAs is out of the flooding range.

Cause: Opaque LSAs are received when the Opaque capability is not enabled, or Type 11 LSAs are received when the current area does not support the As-external-lsa capability.

·         Retransmission for packet over Limitation errors: indicates that the number of packet retransmission times exceeds the set limit.

o    Number for DD Packet: indicates that the number of DD packet retransmission times exceeds the set limit.

Cause: After the limit on the number of packet retransmission times is set, the neighbor becomes Down and the count is increased by 1, each time the number of DD packet retransmission times exceeds the set limit.

o    Number for Update Packet: indicates that the number of Update packet retransmission times exceeds the set limit.

Cause: After the limit on the number of packet retransmission times is set, the neighbor becomes Down and the count is increased by 1, each time the number of Update packet retransmission times exceeds the set limit.

o    Number for Request Packet: indicates that the number of request packet retransmission times exceeds the set limit.

Cause: After the limit on the number of packet retransmission times is set, the neighbor becomes Down and the count is increased by 1, each time the number of LS Request packet retransmission times exceeds the set limit.

·         Receive Grace LSA errors: indicates the statistics about received Grace LSA errors.

o    Number of invalid LSAs: indicates the number of invalid Grace LSAs.

Cause: The received Grace LSA is incorrectly parsed.

o    Number of policy failed LSAs: indicates the number of policy failures.

Cause: The GR helper policy fails and the device fails to enter the helper state.

o    Number of wrong period LSAs: indicates that the value of the GR timer contained in the received Grace LSA is incorrect.

The causes are listed as follows:

      • The aging time of the Opaque-LSAs is not 3600s and greater than the GR period.
      • The value of the age field in the received Opaque-LSA is greater than 1800.

·         Configuration errors: indicates the statistics about configuration errors.

o    Tunnel cost mistake: indicates that the cost of the tunnel is incorrect.

Cause: The cost of the tunnel is not greater than 0.

o    The network type of the neighboring interface is not consistent: indicates that the network type of the local interface is inconsistent with that of the neighboring interface.

Cause: The network types configured on the neighboring interfaces may be inconsistent.

 

  • x
  • convention:

gululu Admin Created Aug 25, 2017 15:21:46 Helpful(0) Helpful(0)

good
  • x
  • convention:

Come on!

Reply

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

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
Fast reply Scroll to top