Table of Contents
ATM Forum call clearing codes and LAN emulation failure codes
Not all these are errors. Some occur in normal operation, for example you may see clear code 47 if someone switches off their pc. These are the clear codes that are generated by IBM switches. Keep in mind that some equipment reports these in Hex (eg. 8265) and some in Decimal (eg. MSS)
ATM Forum call clearing codes
| Code (Decimal) | Cause | Reasons |
|---|---|---|
| 1 | address unknown, call routes properly to destination ATM switch, where it fails to match anything in the reachable address table. | 1. destination device offline, 2. destination device has messed up it's ILMI, 3. typing mistake in bytes 14-19 of destination address |
| 2 | ||
| 3 | no route to destination, no working path through network to destination switch. | Usually 1. problem within PNNI peer group: a. PNNI link down, b. PNNI setup problem, c. destination switch offline, d. typing error in bytes 1-13 of ATM address. 2. problem with IISP to alien ATM network: a. IISP link down, b. manual entries in reachable address table do not cover intended destination. |
| 10 | vpi or vci unacceptable. | Usually: 1. outside range for port or device. |
| 16 | normal clearing. (UNI 3.1) | |
| 17 | user is busy | Usually: 1. Adapter already handling max number of concurrent calls. |
| 18 | no response from user | |
| 27 | destination is out of order | |
| 31 | normal clearing. (UNI 3.0) | |
| 35 | vpi or vci is already in use | |
| 38 | network down | |
| 41 | temporary problem | |
| 45 | no vpi or vci is available | |
| 47 | resource is unavailable, no further information | |
| 49 | quality of service is unavailable | |
| 51 | user cell rate is unavailable (uni 3.0 ) | |
| 63 | service or option is unavailable, no further information | |
| 73 | unsupported combination of traffice parameters | |
| 81 | invalid call reference value | |
| 89 | invalid end point reference | |
| 92 | switch is busy with pending add party requests | |
| 93 | AAL paramaters cannot be supported | |
| 96 | mandatory information element is missing | |
| 97 | message type does not exist or is not implemented | |
| 99 | information element does not exist or is not implemented | |
| 100 | invalid information element contents | |
| 101 | message is not compatible with call state | |
| 102 | expiry of recovery timer | |
| 104 | incorrect message length | |
| 111 | protocol error, unspecified |
Failure codes from LAN emulation
LE clients issue configure, join and register requests to the LAN emulation server. If these are invalid they may be refused with a LAN emulation status code. You may see the following. Again, beware hex and decimal.
| code (Decimal) | cause |
|---|---|
| 0 | success |
| 1 | client is using a later version of LANE than server |
| 2 | details of request incompatible with eLAN |
| 4 | LAN address (emulated MAC address) already in use |
| 5 | ATM address already in use |
| 6 | resource shortage - table full, no capacity for VCCs etc. |
| 7 | access denied for security reasons |
| 8 | LE client id is not correct |
| 9 | attempt to register multicast address |
| 10 | ATM address is in a bad format |
| 20 | LE client is not recognised, usually has asked to join an elan that doesn't exist (Typing mistake in elan name?) elan names are 'CaSe SeNsItIvE' |
| 21 | configuration parameters supplied yield ambiguous answer |
| 22 | configuration parameters supplied are insufficient |
