Cabletron Systems CSX1000 manual Cause cause code received for Dlci dlci index, Cause Code Event

USER’S GUIDE

Cause <cause code> received for DLCI <dlci index>

A CLLM message was received indicating that the PVC associated with the indicated DLCI is subject to the event denoted by the indicated cause code. These events are listed below with their corresponding cause code:

Cause Code Event

2Mild congestion

3Severe congestion

7Fixed fault notification: facility/equipment failure

10Discard all frames: maintenance action in progress

CB disconnect:(1) Password Incorrect

CB disconnect:(2) Call-back number not found

CB disconnect:(3) Ethernet address inconsistent

CB disconnect:(4) Disconnecting for Call-back

CB disconnect:(5) Invalid Packet Received

CB disconnect:(6) Unable to resolve protocols

CB disconnect:(7) Inband Timeout

CB disconnect:(8) Line Integrity Violation

CB disconnect:(?) Unspecified

For all of the above Combinet generated messages, the Combinet has disconnected for the indicated reason. Check your Combinet configuration, and adjust if necessary. If problem persists, contact your Combinet distributor.

[CCP] Internal Decompression Failure

The system was unable to decompress a packet though the frame was delivered properly from a protocol perspective. This is an unexpected condition with a properly functioning device implementation and is thus considered a unrecoverable error. The system will close the CCP protocol, meaning that the connection continues to operate, but in an uncompressed mode.

[CCP] Option Negotiation Failure, Non-Convergence detected

During PPP negotiation, the system attempted to negotiate CCP, but it was not possible to arrive at a mutually acceptable set of protocol parameters with the connected device. The connection continues to operate, but without compression.

The cause of this problem may result from:

•the system has too little memory to support compression, or

•the two devices involved don’t agree on which bridging/routing protocol to use (due to a mis- configuration)

Check configuration for correct protocol. If this is not the problem, check memory availability.

CDR was unable to obtain a buffer to report a CDR event

A buffer was unavailable to send a call detail recording event log message, and the message was discarded. This message is logged once when the condition first occurs. It will not be logged again until the condition has been cleared and CDR has successfully obtained a buffer. If the condition occurs again later, another message will be logged.

438 CyberSWITCH