Troubleshooting guide

Troubleshooting Guide
216
command. For example, if you issue this command on a resilient device’s primary ICP and it
is out of service there, you must then issue the command on the device’s secondary ICP to
determine the state of that device on that ICP.
If a resilient device is out of service on both of its ICPs
• The device may, itself, be out of service.
• The device may be in the process of registering on an ICP.
State XNET ICP
You issue the State XNET ICP command to find resilient calls (calls in survival state) across IP
trunks. If a device loses its ICP during a call, it retains PSTN access through a healthy controller.
A healthy controller with calls on it that are in survival state is indicated in the command output
by a link handle of zero.
Obtaining the Status of Resilient Trunks
Use the following commands to obtain the status of resilient T1/E1 trunks:
• EDT Show Resiliency
• Dtstats Read and Dtstats Clear
• Netsync State
•State
• Show Faults
Refer to the System Administration Tool online help for instructions on how to use these
commands.
Controlling the Failover and Failback of Resilient Trunks
Use the following commands to control the failover and failback of resilient T1/E1 trunks:
• EDT Force Failover
• EDT Force Failback
• Programmed Failover
Refer to the System Administration Tool online help for instructions on how to use these
commands.
Table 75: State XNET ICP Command Output for ICPs with Resilient Calls
Input
Output for Link
Handle Value
Meaning
state xnet icp 44 0 (zero) ICP 44 is healthy and is currently streaming calls in survival state.