Maintenance-Object Repair Procedures
555-233-143
8-1598
Issue 1 May 2002
Restarting Non-Functioning Port Circuit Packs
A defective TDM-bus control channel or system-timing reference on one of the
EPNs can cause port circuit packs residing outside the EPN’s control carrier to
enter the reset state. When this situation occurs, the circuit pack will stop
functioning, and its red LED will light. The system does not detect the presence of
a circuit pack when it is in the reset state. Hence, executing the list config board
command indicates that the circuit pack is absent.
If a circuit pack enters the reset state, it remains out of service until it receives a
restart message from the control channel on the same TDM bus (A or B) that was
active when it reset, or until it is powered up again.
To force the system to send a restart message to every circuit pack on a network,
try one of the following methods, depending on the circumstances. Any normally
functioning circuit pack (i.e., not in reset state) will ignore the restart message.
Procedure 1 (Nondestructive)
If the control channel is on the same TDM bus as it was when the circuit pack
entered the reset state, issue the test tdm P command to execute the Idle Time
Slot test (#294).
Procedure 2 (Nondestructive)
If you are on-site, reseat the circuit pack. This action causes the circuit pack in
the reset state to begin functioning on the control channel of the current bus.
Procedure 3 (Destructive)
Issue the reset port-network P level 2 command to reset the EPN containing the
circuit pack in the reset state. During an EPN reset, two restart messages (one on
the control channel of each TDM bus) are sent to each circuit pack in the EPN.
Resetting the EPN will disrupt every call going to and originating from the EPN.
Procedure 4 (Destructive)
Execute the recycle carrier PC command. This command removes and restores
power to the designated port carrier. Thus, any other circuit packs in this carrier
will also be temporarily taken out-of-service.
Summary of Contents for S8700 Series
Page 50: ...Maintenance Architecture 555 233 143 1 26 Issue 1 May 2002 ...
Page 74: ...Initialization and Recovery 555 233 143 3 12 Issue 1 May 2002 ...
Page 186: ...Alarms Errors and Troubleshooting 555 233 143 4 112 Issue 1 May 2002 ...
Page 232: ...Additional Maintenance Procedures 555 233 143 5 46 Issue 1 May 2002 ...
Page 635: ...status psa Issue 1 May 2002 7 379 555 233 143 status psa See status tti on page 7 406 ...
Page 722: ...Maintenance Commands 555 233 143 7 466 Issue 1 May 2002 ...