Demand test descriptions and error codes - Avaya Support

Expansion Interface 2-Way Transmission Test (#241)
Expansion Interface 2-Way Transmission Test (#241)
Note:
Note: The term EI applies to both the Expansion Interface (EI) and ATM Expansion
Interface (ATM-EI) boards.
This test is nondestructive and applies to each EI, both active and standby.
The EI 2-way transmission test is a basic connectivity test between two PNs. The test first
sends dial tone from the cabinet of the EI circuit pack under test through the switch, through the
DS1 converter circuit packs, and through another EI circuit pack to a tone detector in the other
cabinet. The connections are then reversed and the tone is passed in the opposite direction.
If the test either fails or aborts with the above connection, a second PN is chosen (if one is
available and the EI circuit pack is In-Service) and the same test is run on this new connection.
This helps in the isolation of the fault. Since two EI circuit packs are involved in the connection,
either one of them could be at fault. This test can help determine which one is actually at fault.
The test results indicate if the test failed in one or both directions. The test aborts if the EIs do
not exist on both ends (for example, the EIs are not administered correctly). If the test passes,
the TDM and ATM framer interfaces of both EIs are functioning properly.
This test runs on ATM-EI (Expansion Interface Circuit Pack) and EXP-INTF (Expansion
Interface Circuit Pack).
Table 376: Expansion Interface 2-Way Transmission Test (#241) 1 of 7
Error
Code
Test
Result
Description / Recommendation
1002 ABORT The system could not allocate time slots for the test. The system may be
under heavy traffic conditions, or it may have time slots out-of-service
due to TDM-BUS errors. A system is considered under heavy traffic
when the Call Processing Occupancy is greater than 50% or when the
System Management and the Call Processing Occupancies together
exceed 65%.
1. Enter status health to view the occupancy measurements.
2. Enter display errors and resolve any TDM-BUS (TDM Bus)
errors.
3. If the system has no TDM-BUS errors and is not handling heavy
traffic, retry the command at 1-minute intervals up to 5 times.
1 of 7
Issue 5 May 2009 1315