Communication Manager: ATM-DCH: Asynchronous Transfer Mode D-Chel Port

Doc ID    SOLN251540
Version:    1.0
Status:    Published
Published date:    11 Jun 2014
Author:   
ls29
 

Details

ATM-DCH uses the existing ISDN-PLK or D-chel maintenance strategy with modifications. The ATM circuit pack can be administered for up to 8 Circuit Emulation Service (CES) or signaling groups, each with its own D-Chel, as opposed to one D-Chel for an entire DS1 circuit pack.

 
The D-chel ISDN-PRI interface is emulated for ATM-CES and uses out-of-band signaling to transmit control messages between two endpoints. User information or bearer chels (B-Chels) carry digitized voice and digital data and are assigned to DS1 ISDN trunks or PRI endpoints. Call-control signaling for the B-Chels is combined and carried over the separate ISDN-PRI Signaling Link port D-Chel. Problems with ATM-DCH affects every associated B-Chel, since call-control signaling cot reach the far-end switch or terminal adapter. Stable calls can remain operational, but no new calls can be made. In turn, ATM-DCH depends on the:
● TN230X ATM Trunk circuit pack where it resides
● Packet bus that provides the link to the processor
When working ATM-DCH alarms or errors, also investigate
● ATM-TRK (Circuit Emulation Service Circuit Pack)

● PKT-BUS (Packet Bus)

Problem Clarification

Alarm on MO ATM-DCH

Cause

Various-see Solution section

Solution

Enter command "display errors" and find the corresponding error code below.

Error Type 0: test port location Run the short test sequence first. If every test passes, run the long test sequence. Refer to each appropriate test’s description, and follow its recommended procedures.
 
Error Type 18: release port location D-Chel busied out. No calls possible over this D-Chel.
 
Error Type 130: test port location Circuit pack removed or has been insane for more than 11 minutes. To clear the error, reinsert or replace the circuit pack.
 
Error Type 1793: test board location l ATM Trunk circuit pack failed the Signaling Link Board check (#643). Resolve any ATM-TRK (Circuit Emulation Service Circuit Pack) errors in the Error Log.
 
Signaling Link Board Check (#643)
This test checks the health of the critical ATM TN230X circuit pack, DS1 Interface circuit pack, or DS1Interface media module hardware components required by the signaling link.
 
Error   Test                Description / Recommendation
Code   Result
            ABORT           Internal system error
1. Retry the command at 1-minute intervals up to 5 times.
 
1700    ABORT           Rollabout video abort. The PRI terminal adapter associated with this D-chel port is detached from the circuit pack. This is normal when the rollabout video feature is enabled. To complete a test on this port:
1. Re-attach the disconnected PRI terminal adapter.
2. Enter change ds1 location to disable rollabout video on the board, and set the “Alarm when PRI Endpoint Detached” field to y.
 
8          FAIL                The circuit pack is not in service.
1. Check the Hardware Error Log for entries logged against UDS1-BD or ATM-TRK. Consult UDS1-BD (UDS1 Interface Circuit Pack) or ATM-TRK (Circuit Emulation Service Circuit Pack) for repair procedures.
 
            PASS              The circuit pack or media module transporting the ISDN-PRI Signaling
Link Port is in service.
 
Any      NO BOARD    See NO BOARD for the repair procedures.
 
NO BOARD
No board was detected by the test. The test could not relate the internal ID to the port. This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.
1. Enter display errors and check the Error Log for Error Type 125 (wrong board) or Error Type 131 (no board). Resolve either of these issues, if applicable.
2. Verify that the board is properly translated and inserted by using list configuration.
Resolve any problems.
3. For DS1/UDS1 boards, use add ds1 location to administer the DS1 interface if it is not already administered.
4. If the board was already administered correctly, check the Error Log to determine whether the board is hyperactive (Error Type 1538). If so, the board was shut down. Reseating the board will re-initialize it.
5. If the circuit pack is correctly inserted, enter the following commands:
● busyout board location
● reset board location
● release board location
● test board location long
This should re-establish the linkage between the internal ID and the port. If not, verify that a valid board is inserted.
Note: : Hyperactivity causes some special problems with the sequence suggestedabove. If the ports are translated after entering list config but the Vintage field reports that there is no board when there really is a board, then the busyoutboard and release board commands will not work even though resetboard location will work. The switch will put the hyperactive board back inservice after the hyperactivity clears
 

Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy