Filter
Top Products
Communication Manager Maintenance-Object Repair Procedures
986 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Attempt to clear the alarm with busyout board location, test ds1-loop
location ds1/csu-loopback-tests, and release board location. If the RLB
test continues to fail, then the CSU module/T1 sync splitter needs to be replaced.
p. Error Type 1313: CPE loop-back jack deactivation error. This error occurs when the
TN767E circuit pack could not deactivate a CPE loop-back jack loop-back.
Attempt to clear the alarm with busyout board location, test ds1-loop location
end-loopback/span-test, and release board location. If the attempt to
deactivate the CPE loop-back jack loop back continues to fail, other steps must be taken to
deactivate the loop back.
q. Error Type 1314: Far CSU Loopback deactivation error. This error occurs when the
TN767E circuit pack could not deactivate a far-end CSU loop back on power-up/reset or
upon software request.
Attempt to clear the alarm with busyout board location, test ds1-loop
location end-loop back/span-test, release board location. If the attempt to
deactivate the Far CSU loop back continues to fail, then escalate the problem.
r. Error Type 1538: The hyperactive circuit pack is out-of-service and may exhibit one or
more of the following symptoms:
● The common circuit pack-level tests, such as Test #51 and Test #220, are aborting with
error code 2000.
● The tests run on the ports of this circuit pack are returning NO BOARD.
● A busyout/release of the circuit pack has no affect on test results.
● List configuration shows that the circuit pack and ports are properly installed.
The circuit pack is isolated from the system and all trunks of this circuit pack are placed into
the out-of-service state. The system will try to restore the circuit pack within 15 minutes.
When no faults are detected for 15 minutes, the DS1 Interface circuit pack is restored to
normal operation. All trunks of the DS1 Interface circuit pack are then returned to the
in-service state. If the error recurs after 15 minutes, then escalate this problem.
s. Error Type 3160: For later releases of G3V4 and beyond, only error 3073 shows that this
board is receiving Slips, and the AUX data shows the last Slip count that was reported.
t. Error Type 3329 - 3345: For later releases of G3V4 and beyond, only error 3329 shows
that this board is receiving misframes and the AUX data shows the last misframe count that
was reported.
u. Error Type 3840: ignore, is not service-affecting.
v. Error Type 3900: used to give status information about a CPE Loopback Jack test. The
value in the Aux Data field indicates the status of the loop-back test:
Aux Data 1: Test is currently running.
Aux Data 2: Test failed because loop back could not be activated.
Aux Data 3: Test failed because test pattern could not be detected.
Aux Data 4: Test has been deactivated.