show ldp statistics

Total number of each message type sent and received.

Number of each message type sent and received in the last 5 seconds.

LDP message types:

• Hello—Messages that enable LDP nodes to discover one another and to detect the failure of a neighbor or of the link to the neighbor.

• Initialization—Messages that indicate an LDP session has started.

• Keepalive—Messages that ensure that the keepalive timeout is not exceeded.

• Notification—Advisory information and signal error information.

• Address—Messages with address information.

• Address withdrawal—Messages regarding address withdrawal.

• Label mapping—Messages with label mapping information.

• Label request—Request for a label mapping from a neighboring router.

• Label withdrawal—Withdrawal message sent by the downstream LSR to recall a label that it previously mapped. If an LSR that has received a label mapping subsequently determines that it no longer needs that label, it can send a label release message that frees the label for use.

• Label release—Message sent by the downstream LSR to recall a label that it previously mapped. If an LSR that has received a label mapping subsequently determines that it no longer needs that label, it can send a label release message that frees the label for use.

• Label abort—Messages about label interruptions.

• All UDP—All hello messages sent by LSRs to the well-known UDP port, 646.

• All TCP—All LDP session messages.

LDP events and errors:

• Sessions opened—Number of LDP sessions that have been opened.

• Sessions closed—Number of LDP sessions that have been closed.

• Topology changes—Number of changes to the known LDP topology.

• No interface—Number of missing interface address messages. When a new LDP session is initialized and before sending label lapping or label request messages, the LSR advertises its interface addresses with one or more address messages.

• No session—Number of missing session messages. Session messages are used to establish, maintain, and terminate sessions between LDP peers.

• No adjacency—The exchange of hello adjacency messages results in the creation of an adjacency. The LDP identifier, together with the sender's LDP identifier in the PDU header, enables the receiver to match the initialization message with one of its hello adjacencies. If there is no matching hello adjacency, the LSR sends a session the initialization message is rejected.

• Unknown version—The LDP protocol version is not supported by the receiver, or it is supported but is not the version negotiated for the session during session establishment.

• Malformed PDU—An LDP PDU received on a TCP connection for an LDP session is malformed if the LDP identifier in the PDU header is unknown to the receiver, or if it is known but is not the LDP identifier associated by the receiver with the LDP peer for this LDP session.

  An LDP PDU is considered to be malformed if the LDP protocol version is not supported by the receiver, or it is supported but is not the version negotiated for the session during session establishment.

  An LDP PDU is considered malformed if the PDU length field is too small (less than 14) or too large (greater than maximum PDU length).

• Malformed message—Malformed LDP messages that are part of the LDP discovery mechanism are handled by silently discarding them.

  An LDP message is malformed if the message type is unknown. If the message type is less than 0x8000 (high order bit = 0), it is an error signaled by the unknown message type status code.

  An LDP message is considered to be malformed If the message length is too large, meaning that the message extends beyond the end of the containing LDP PDU.

  The LDP message is considered to be malformed if the message length is too small, meaning that it is smaller than the smallest possible value component.

  The LDP message is considered to be malformed if the message is missing one or more mandatory parameters.

• Unknown message type—If the message type is less than 0x8000 (high order bit = 0) or greater than or equal to 0x8000 (high order bit = 1) it is considered to be an unknown message.

• Inappropriate message—The message is not of the type that the receiver expects to receive.

• Malformed TLV—The TLV lLength is too large or the receiver cannot decode the TLV value. This can indicate an issue in either the sending or receiving LSR.

• Bad TLV value—The TLV Length is too large.

• Missing TLV—The TLV is missing one or more mandatory parameters.

• PDU too large—The PDF is greater than the maximum PDU length. Section "Initialization Message" in RFC 5036 describes how the maximum PDU length for a session is determined.

Total number of each event or error.

Number of each event or error in the last 5 seconds.