ldp Messages

ldp Messages

This chapter describes messages generated by the ldp subsystem.

Critical
Message: <function>():line <line> Processing failed, memory likely exhausted
Meaning: The system has run out of memory.

Action: Report this to Avici Customer Support. This is a critical memory/software error.

Major
Message: <function>() LPE bad params
Meaning: An internal software component failed due to incorrect parameters.

Action: Save your system log to a file and contact Avici Customer Support.
Message: <function>: retries <number>
Meaning: LDP failed to initialize properly

Action: Save your system log to a file and contact Avici Customer Support.
Message: AVMALLOC failed
Meaning: Memory Allocation failed in LDP

Action: Report this to Avici Customer Support. This is a critical error.
Message: Creation of platform-wide label manager failed
Meaning: LDP failed to initialize properly

Action: Save your system log to a file and contact Avici Customer Support.
Message: Deletion of fec(<address>) node from the tree failed
Meaning: LDP tried to delete an already deleted fec.

Action: No action required.
Message: Deletion of router id <address> from addr list failed
Meaning: Router id update failed for LDP

Action: Save your system log to a file and contact Avici Customer Support.
Message: Error registering avMalloc tags for LDP
Meaning: An error occurred while trying to initialize LDP

Action: Save your system log to a file and contact Avici Customer Support.
Message: Fatal, no fec while adding req
Meaning: An internal error occurred while adding a FEC to the LDP database

Action: Save your system log to a file and contact Avici Customer Support.
Message: Get label request failed, error <number>
Meaning: Internal communication failed during label request

Action: Save your system log to a file and contact Avici Customer Support.
Message: IPC ptr is NULL
Meaning: An internal error ocurred while adding a timer item.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Incorrect message size: <number> at <function>
Meaning: The Route Server to LDP communication failed due to incorrect parameters

Action: Save your system log to a file and contact Avici Customer Support.
Message: Incorrect message type: <type> at <function>
Meaning: The Route Server to LDP communication failed due to incorrect parameters

Action: Save your system log to a file and contact Avici Customer Support.
Message: Incorrect number of args: <number> at <function>
Meaning: The Route Server to LDP communication failed due to incorrect parameters

Action: Save your system log to a file and contact Avici Customer Support.
Message: LDP delete fail, wait time for deletion <number> secs.
Meaning: Router id update failed for LDP entities

Action: Save your system log to a file and contact Avici Customer Support.
Message: LDPID: <address>/<number> Index: <number> LMAN Add Label Failure, IF Index: <number>
Meaning: LDP failed to add label to the platform-wide label database

Action: Save your system log to a file and contact Avici Customer Support.
Message: LDPID: <address>/<number> Index: <number> LMAN Create Failure, IF Index: <number>
Meaning: LDP failed to initialize properly

Action: Save your system log to a file and contact Avici Customer Support.
Message: LMAN lbl ctx is null
Meaning: An internal software component failed due to incorrect parameters.

Action: Save your system log to a file and contact Avici Customer Support.
Message: LPE create_lsp request refused by switch mapping
Meaning: An LDP LSP could not be created due to bad parameters

Action: Save your system log to a file and contact Avici Customer Support.
Message: LPE delete_lsp request refused by switch mapping for FEC 0x<hexadecimal>/<number>, fec_index <number> and in_label <number>
Meaning: An LDP LSP could not be deprogrammed

Action: Save your system log to a file and contact Avici Customer Support.
Message: Line <number>; Error, cannot allocate memory, cannot store label <number>, FEC <address>/<number> to rca-tree.
Meaning: An internal software component failed to allocate memory.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Line <number>; Error, label <number> out-of-range, cannot store FEC <address>/<number> to rca-tree.
Meaning: LDP label out of range (of that supported by Avici)

Action: Save your system log to a file and contact Avici Customer Support.
Message: Line <number>; Error,cannot allocate memory, cannot store FEC <address>/<number> to recompute-tree.
Meaning: An internal software component failed to allocate memory.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Memory allocation failure while adding timer item
Meaning: An internal software component failed to allocate memory.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Platform-wide add label failure
Meaning: LDP failed to add label to the platform-wide label database

Action: Save your system log to a file and contact Avici Customer Support.
Message: Swmap is unable to free label <label>
Meaning: An internal software component failed to free an LDP label

Action: Save your system log to a file and contact Avici Customer Support.
Message: Unable to allocate memory for tunnel egress 0x<number>
Meaning: An internal software component failed to allocate memory.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Unable to initialize LDP task
Meaning: LDP failed to initialize properly

Action: Save your system log to a file and contact Avici Customer Support.
Message: Unable to initialize patricia tree for fec
Meaning: LDP failed to initialize properly

Action: Save your system log to a file and contact Avici Customer Support.
Message: Unknown FEC lookup flag <hexadecimal> at <function>
Meaning: The Route Server to LDP communication failed due to incorrect parameters

Action: Save your system log to a file and contact Avici Customer Support.
Message: app->rdb is NULL, <number>
Meaning: An internal software component failed due to incorrect parameters.

Action: Save your system log to a file and contact Avici Customer Support.
Message: attempting to delete fec <address> when pointer to fec_lbl_ctx of type <type> is not NULL
Meaning: Memory deallocation failed due to internal error

Action: Save your system log to a file and contact Avici Customer Support.
Message: attempting to delete fec <address> when rdb state is <value>
Meaning: Memory deallocation failed due to internal error

Action: Save your system log to a file and contact Avici Customer Support.
Message: attempting to free when states are not idle, lbl state <label state>, lpe state <value>
Meaning: Memory deallocation failed due to internal error

Action: Save your system log to a file and contact Avici Customer Support.
Message: fec index <id> not found when trying to delete
Meaning: Internal data structures are corrupted.

Action: Save your system log to a file and contact Avici Customer Support.
Message: fec_index <id> already present when trying to insert
Meaning: Internal data structures are corrupted.

Action: Save your system log to a file and contact Avici Customer Support.
Message: in label <number> not found when trying to delete
Meaning: Internal data structures are corrupted.

Action: Save your system log to a file and contact Avici Customer Support.
Message: ldp_gated_route_query failed: <number>
Meaning: IPriori had an internal communication error when querying for a route

Action: Save your system log to a file and contact Avici Customer Support.
Message: lman_info pointer is NULL
Meaning: An internal software component failed due to incorrect parameters.

Action: Save your system log to a file and contact Avici Customer Support.
Message: memory allocation failed for arg
Meaning: An internal software component failed to allocate memory.

Action: Save your system log to a file and contact Avici Customer Support.
Message: memory allocation failed for ctx
Meaning: An internal software component failed to allocate memory.

Action: Save your system log to a file and contact Avici Customer Support.
Message: memory allocation failed for fec
Meaning: An internal software component failed to allocate memory.

Action: Save your system log to a file and contact Avici Customer Support.
Message: memory allocation failed for lbl_ctx
Meaning: An internal software component failed to allocate memory.

Action: Save your system log to a file and contact Avici Customer Support.
Message: memory allocation failed for new
Meaning: An internal software component failed to allocate memory.

Action: Save your system log to a file and contact Avici Customer Support.
Message: memory allocation failed for reply
Meaning: An internal software component failed to allocate memory.

Action: Save your system log to a file and contact Avici Customer Support.
Message: next_hop_reply failed to get fec <address>
Meaning: IPriori had an internal communication error

Action: Save your system log to a file and contact Avici Customer Support.
Message: parse_newroute_notify_request failed
Meaning: IPriori had an internal communication error

Action: Save your system log to a file and contact Avici Customer Support.
Message: parse_release_route_reply failed: <string>, <number>, <number>
Meaning: IPriori had an internal communication error

Action: Save your system log to a file and contact Avici Customer Support.
Message: parse_swmap_free_label_reply, size error
Meaning: Internal communication failed due to incorrect parameters

Action: Save your system log to a file and contact Avici Customer Support.
Message: parse_swmap_free_label_reply, too many args
Meaning: Internal communication failed due to incorrect parameters

Action: Save your system log to a file and contact Avici Customer Support.
Message: parse_swmap_get_label_reply, size error
Meaning: Internal communication failed due to incorrect parameters

Action: Save your system log to a file and contact Avici Customer Support.
Message: parse_swmap_get_label_reply, too many args
Meaning: Internal communication failed due to incorrect parameters

Action: Save your system log to a file and contact Avici Customer Support.
Message: parse_swmap_get_label_reply, type <reply type>, size <label size>
Meaning: Internal communication failed due to incorrect parameters

Action: Save your system log to a file and contact Avici Customer Support.
Message: rdb->fec_index_tree data structure corruption
Meaning: Internal data structures are corrupted.

Action: Save your system log to a file and contact Avici Customer Support.
Message: rdb->in_label_tree data structure corruption
Meaning: Internal data structures are corrupted.

Action: Save your system log to a file and contact Avici Customer Support.
Message: register request for label availability failed status <number>, rxState <number>
Meaning: Internal communication failed during initialization

Action: Save your system log to a file and contact Avici Customer Support.
Message: release_route api failed: <number>
Meaning: IPriori had an internal communication error when releasing a route

Action: Save your system log to a file and contact Avici Customer Support.
Message: swmap_free_label API failed in <name>
Meaning: Internal communication failed during label deletion

Action: Save your system log to a file and contact Avici Customer Support.
Message: swmap_free_label, error <number>
Meaning: Internal communication failed while freeing label

Action: Save your system log to a file and contact Avici Customer Support.
Message: swmap_get_label API failed <message>
Meaning: Internal communication communication failed during label allocation

Action: Save your system log to a file and contact Avici Customer Support.
Message: trans in label value <number> is already present in tree
Meaning: Internal data structures are corrupted.

Action: Save your system log to a file and contact Avici Customer Support.
Message: unknown fec type: <type>
Meaning: FEC type not recognized by LDP

Action: Save your system log to a file and contact Avici Customer Support

Minor
Message: LPE: FEC <FEC IP address> encountered an unexpected state <LPE state> while trying to release the Lsp-state associated with a session
Meaning: The label programming engine encountered an unexpected state while a session released its lsp-state.

Action: Gather the logs, verify all LSPs and call Avici Customer Support if the error persists.

Warning
Message: <<Time> ldp_sess_tcp_close_and_retry>
Meaning: TCP connection closed. The TCP connection will be retried. Ignore Time value.

Action: Wait for a period of time and the session will come up after the retry of the TCP connection.
Message: <<Time> hjldp_lpe_async_reply(): ldp handle missing>
Meaning: The LDP Entity handle did not exist at the time of processing the asynchronous reply from the Label Processing Engine. One of the reason could be interface went down while waiting for reply from hardware programming. Ignore Time value.

Action: No action required.
Message: <GENERIC_LMS_LOG : hj_bsd_sock_Error:>: <number>
Meaning: A Socket Error occurred

Action: The socket error number specified points to the reason for the socket error. Please refer the error nuber doc.
Message: <hjsock_event_tcp_send:Write failed:>: <number>, <address>:<local port>=> <remote address>:<remote port> Socket state : <state>
Meaning: LDP is trying to send LDP messages over TCP where that TCP connection has already been closed by the remote peer.

Action: Please refer the error # documentation for the logged error number. TCP connection will try again to establish LDP Session. Call Avici customer support if the problem persists.
Message: <hjsock_event_gen_send: send failed:>: <number>, <address>:<local port>=> <remote address>:<remote port> Socket state : <state>
Meaning: LDP is trying to send UDP Hello messages.

Action: Look for other LDP socket error message for this issue and refer the error # documentation. Call Avici Customer support if the problem persists.
Message: <socket_event_tcp_open_establish: connect failed:>: <number>, <address>:<local port>=> <remote address>:<remote port> Socket state : <state>
Meaning: LDP tried to establish a TCP connection and the connect failed.

Action: Check the local and peer LDP configuration. Refer to the error# documentation for the reason. Based on the error # information either call Avici Customer support, or no action required.
Message: <hjsock_event_tcp_active_ind: recv returned Error:>: <number>, <address>:<local port>=> <remote address>:<remote port> Socket state : <state>
Meaning: LDP tried to read a TCP connection that was already closed by a remote peer.

Action: Check the local and peer LDP configuration. Refer to the error # documentation for error information, based on the error # description, either call Avici Customer Support, or no action is required.
Message: Bad PDU length seen for the entity <entity index>,session <peer router id>:<peer label space id>, TCP bytes to drop <TCP bytes to drop>
Meaning: LDP will close the session after sending a session shutdown notification to the peer node. Ignore time value.

Action: Check the LDP configuration of the interface. Look for other LDP messages, and call Avici Customer support if the problem persists.
Message: Close the TCP connection and retry connection again for the entity <entity index> session <peer router id>:<peer label space id>, tcp bytes to drop <TCP bytes to drop>
Meaning: <filled by documentation>The TCP connection has been closed. The TCP connection will be retried.

Action: Wait for the TCP connection to come up after the retry.
Message: Dead Neighbor event for interface <interface>f (entity/adjacency hello transmit state <state>/<state>)
Meaning: Hello hold timer on the module has expired. The module has sent a dead neighbor event to the server to kill the adjacency with the peer.

Action: Check the hello hold timer values on both local and remote routers.
Message: Drop bytes (<number>) failed on session <peer id>:<peer label space id>, entity index <interface index>, label space id <number>. (dbg: <debug info>, <debug info>)
Meaning: LDP tried to consume received bytes on Fault Tolerant TCP protocol. The error # points to the exact reason why it was failed.

Action: No action required. Refer the Error # doc for the logged error number.
Message: Error occured while reading TCP data on TCP connection <local address>:<local port>=> <remote address>:<remote port> Socket state : <state>
Meaning: An error was received while reading TCP data.

Action: Please refer to the error # documentation for the specified error.
Message: Hello expired for local address <address> and peer address <remote address>, TCP bytes to drop <tcp bytes>
Meaning: LDP is processing the Hello Expired Event. This message is a follow up action to the dead neighbor event from the module. Ignore Time value.

Action: Check the Hello hold timer values on both local and remote peers. Change to a higher value.
Message: Hello-Processing: IP header length(<IP header length>) does not match the length reported by data plane(<Data plane packet length>) for received buffer, Source logical interface <source logical interface number>
Meaning: The IP header length of incoming packet does not match the length reported by hardware.

Action: Contact Avici Customer Support.
Message: KeepAlive hold timer expired for the entity <entity index>,session <peer router id>:<peer label space id>, TCP bytes to drop <TCP bytes to drop>
Meaning: The LDP KeepAlive Hold Timer expired while the session was Operational. LDP will close the session after sending a session shutdown notification to the peer node. Ignore time value.

Action: Check the LDP configuration of the interface. Look for other LDP messages, and call Avici Customer support if the problem persists.
Message: LDP HA State-machine Info: Received event <event> in state <state>
Meaning: Indicates the reception of an event corresponding to the received event in the specified state.

Action: No action required.
Message: LDP transition: No interface notification available while trying to validate all repository-stored interfaces against the router-configured interfaces
Meaning: During the transition from backup to primary server, the LDP interface validation failed, due to non-availability of interface information from caller routine.

Action: Gather the logs, verify LSPs after failover and call Avici Customer Support.
Message: LDP-Swmap Transition message not sent for fec <address>/<bits> fec index <number> in label <number>
Meaning: An internal LSP info processing error occurred for the specified FEC during transition.

Action: Contact Avici customer support.
Message: Label <old Label> from <peer address> implicitly withdrawn for FEC <FEC IP address>, new label = <new label>
Meaning: A new label mapping was received before the withdrawal of the old one, hence the old one is implicitly withdrawn.

Action: If the problem persists, contact Avici Customer Support.
Message: Prot error <0>: <0> <Hello Send: Unable to send.>
Meaning: Unable to send LDP Hello Message. Ignore 0 values.

Action: Check the LDP configuration on the interface
Message: Received TCP disconnect event for the entity <entity index>, session <peer router id>:<peer label space id>, TCP bytes to drop <TCP bytes to drop>
Meaning: A TCP Disconnect event occurred while the session was Operational. Ignore Time value.

Action: Look for the message reason in the session down trap log message. Check the LDP configuration on the local and peer interface. Call Avici Customer support if the problem persists.
Message: Replication spool size (<<arg1>>) reached <<arg2>> emergency threshold
Meaning:

Action: Gather the logs and call Avici Customer Support.
Message: Request to disassociate LDP routing database has been denied
Meaning: An RDB Unbind was refused because the trees are still in use.

Action: Collect logs and contact Avici Customer Support.
Message: Socket Error occured action <socket_event_tcp_open_establish: connect failed:> (req <number>) for the socket <address>:<local port>=> <remote address>:<remote port> Socket state : <state>
Meaning: The TCP Connection failed.

Action: TCP connection will be retired after some period of time. The error number points to the reason for the failure. Please refer the error number doc.
Message: Unexpected code-path while doing initial replication for LDP entities
Meaning: A Global LDP instance was not initialized.

Action: Check the configuration.
Message: backup down event received in <LDP high availability fsm> state
Meaning: A backup server down event was received from the server finite state machine

Action: Check the redudancy configuration on the primary server, if hot, wait for a period of time for the server to come back up.
Message: decode error fatal case, mismatch between octets decoded <number> and pdu len: <pdu length> for entity <entity index> session: <peer router id>:<peer label space id>, TCP bytes to drop <bytes to drop>
Meaning: A fatal decode error occurred due to a mismatch between the decoded octets and the expected pdu length.

Action: Save the system logs and contact Avici customer support.
Message: fatal notification with status code <number> received on entity <entity>, session <peer router id>:<peer label space id>, TCP bytes to drop <TCP bytes to drop>
Meaning: A Fatal Notification was received from the peer. The session will be shutdown. An attempt to reestablish the connection will take place. Ignore Time value.

Action: Look for the reason in the session down trap log message. Check the LDP configuration on the local and peer interface. Contact Avici customer support if the problem persists.
Message: fec not found for reroute event from RouteTask for address <address>
Meaning: This message is logged when LDP receives a recompute notification from the routing task for the fec, which deoesn't exist in the LDP database.

Action: No action required
Message: non-fatal case mismatch in octets decoded <number>, pdu len: <pdu length> for entity <entity index> session: <peer router id>:<peer label space id>, TCP bytes to drop <bytes to drop>
Meaning: A non-fatal decode error occurred due to a mismatch between the octets decoded and the expected pdu length.

Action: Save the system logs and contact Avici customer support.
Message: sending basic hello failed on interface <interface>f
Meaning: The sending hello failed.

Action: Look for other messages prior to this one which will specify the error.
Message: sending lsp info to switchmap failed for fec <hexadecimal>/<number>, fec index <number> and in label <number>
Meaning: An internal software component failed due to incorrect parameters.

Action: Save your system log to a file and contact Avici Customer Support.
Message: sending targeted hello to peer <ip address> failed
Meaning: Sending the targeted hello failed.

Action: Look for other messages prior to this one which will specify the error.
Message: session <peer router id>:<peer label space id> shutdown on interface <interface>f (cause <cause>, session state <state>)
Meaning: The session is going down for the specified cause.

Action: Note the cause andcall Avici Customer Support if the problem persists.
Message: socket error occured due to <error description>(<error number>)
Meaning: This is a generic message. The error will be specified in the error description. See the error number appendix in the back of this document for an error description.

Action: Please refer to the error # documentation for the specified error.

Information
Message: invalid rdb state for fec <ip address>, state <fec rdb state>
Meaning: The specified FEC is in an invalid state.

Action: Contact Avici customer support.
Message: LPE received error status <return code> for fec <address>/<bits> while LPE asynchronous reply
Meaning: When LDP is waiting for a response from hardware programming, and at that time an upstream session is lost, then this message is logged after receiving a response from hardware. This is harmless.

Action: No action required.
Message: Mismatch in octets decoded expected (<expected number of bytes>) vs actual (<actual bytes>) on session <peer router id>:<peer label space id>
Meaning: A mismatch in expected decoded octets vs the actual decoded octets has been detected. Session Shutdown Notification is sent to Peer due to the mismatch in decoding the LDP PDU. Ignore time value.

Action: Look for other LDP log messages, Contact Avici customer support if the problem persists.
Message: Parse error occured while decoding PDU, octets decoded expected (<expected number of bytes>) vs actual (<actual bytes>) on session <peer router id>:<peer label space id>
Meaning: A parse error mismatch between the PDU length and number of bytes decoded has been detected. LDP sent a session shutdown Notification with status flag as fatal to the Peer node.

Action: Look for other LDP log messages for this issue. Contact Avici customer support if the problem persists.
Message: Primary nexthop address <ip address> seen in secondary nexthops for the fec <Fec IP address>/<fec bits>
Meaning: An ECMP FEC mapping from the primary has been withdrawn and has not been made secondary in a timely fashion. This is a transient condition only.

Action: No action required.
Message: create LSP failed for fec <ip address>/<fec bits> label: <number>
Meaning: Transient convergence activities are taking place among various asynchronous sub-components of the LDP engine. The condition is harmless and very brief in existence. Once the effects of the trigger event stabilize the condition identified by these messages cease to exist

Action: No action required.
Message: decode error non-fatal case, mismatch between octets decoded <expected number of bytes> and pdu len: <actual bytes> for entity <entity index> session: <peer router id>:<peer label space id>, TCP bytes to drop <TCP bytes to drop>
Meaning: A mismatch in the number of expected decoded octets has been detected verses the number of actual decoded octets.

Action: A session shutdown notification has been sent to the peer due to the mismatch in decoding the LDP PDU.
Message: found existing secondary nexthop address <nexthop ip address> for fec <fec ip address>/<fec bits>
Meaning: This is a follow-up message to message 'ecmp_sec_next_hop_change: Secondary next hop with same params, Discard the request, Lpe Idle.'

Action: No action required.
Message: function <name>, line <line>, fec <FEC>, state <state>
Meaning: LDP received a Label Mapping for the specified fec while waiting for route Lookup.

Action: No action required
Message: number of outsegment is zero for fec <fec ip address>/<fec bits>
Meaning: This message is logged in combination with another message ( reroute create-lsp request failed).

Action: No action required.
Message: primary next hop address <ip address> seen during syncing for fec <Fec IP address>/<fec bits>
Meaning: A follow-up message to the 'Primary seen in is_sec_nh_params_new' message indicating that the component mentioned in that message has finally received the notification of the promotion of the secondary and has detected that an old primary exists

Action: No action required.
Message: same secondary params found for the fec <fec ip address>/<fec bits> for nexhop <nexthop address>, fec state <fec state>
Meaning: A second route for a FEC has been learned while a Primary route is being propagated through the LDP engine. The LDP engine will verify if the LDP label for this second path has already been received.

Action: No action required.

   Source File Name: ldp.fm
    HTML File Name: ldp.html
    Last Updated: 09/26/06 at 14:21:19

ldp Messages

Critical

Major

Minor

Warning

Information

Please email suggestions and comments to: doc@avici.com