Error Type 1: one or more network-region connections have failed.
1. Enter display failed-ip-network-region to verify that connections between pairs of network regions are failing.
2. If so, enter test failed-ip-network-region to retest these paths.
3. For each affected network region, check the error log for failures to related MOs, such as:
- IPMEDPRO (IP Media Processor Circuit Pack)
- MEDPRO (Media Processor MAPD Circuit Pack)
- CLAN-BD (Control LAN Circuit Pack)
- DIG-IP-S (Digital IP Station)
- RDIG-STA (Remote Digital Station) and resolve any problems.
4. Enter test failed-ip-network-region to retest these paths.
5. If errors persist, escalate.
Network Region Interconnectivity Test (#1417)
This test does not specify and list Error Codes in the usual mer. If this test detects a failure, the test is retried using different IP endpoints, if available, from the same two network regions. If the test still fails between these network regions:
1. Maintenance software marks the connectivity between them as “failed.”
2. Communication Manager denies every attempted call between them.
For this test, devices that can serve as IP endpoints include:
● IPMEDPRO
● MEDPRO
● CLAN-BD
● IP phones or Softphones, with the ability to initiate a ping
For a network region without an IPMEDPRO, MEDPRO, or a CLAN-BD, Test #1417 looks for another ping-capable endpoint. If found, the region’s testing continues. If not, the test assumes that the region’s connectivity is operating normally.
Error Test Description / Recommendation
Code Result
1 ABORT Internal error
2 1. Retry the command at 1-minute intervals up to 3 times.
11 2. If the problem persists, escalate the problem.
1005 ABORT Incorrect test configuration.
1. Verify the Ethernet link is in-service on all C-LAN boards in the source and destination regions with status port location or status link n).
1125 ABORT Ethernet link not in service.
1. Verify the Ethernet link is in-service for all C-LAN boards in the source and destination regions under test using status port location or status link n. If interface is enabled, the Ethernet link is expected to be in-service for this test to run.
2000 ABORT Response to the test was not received within the allowed time.
1. Retry the command at 1-minute intervals up to 3 times.
2. If the problem persists, reset the circuit pack.
3. Rerun the test. If the problem persists, replace the circuit pack.
2012 ABORT Internal system error.
1. Retry the command at 1-minute intervals, up to 3 times.
2100 ABORT Could not locate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals, up to 5 times.
2500 ABORT Internal system error.
1. Retry the command at 1-minute intervals, up to 3 times.
2801 ABORT No IP address defined.
1. Verify IP interfaces translations and retest.
2802 ABORT Different IP address pinged than was allocated for the test.
1. Retry the command at 1-minute intervals up to 3 times.
2807 ABORT The board is administered but not enabled on the change ipserver-interfaces screen.
1003 FAIL Ping to the destination failed due to on-board problems of the source of the ping. The source of the ping can be a C-LAN board or a IPMEDPRO board for this error to occur.
1. Retry the command at 1-minute intervals, up to 3 times.
2. Look for problems associated with IPMEDPRO or C-LAN boards in this region.
7 FAIL Ping to the destination failed due to the destination being down.
89 1. Verify that at least one destination reachable through the network 1007 regions being tested is up. Ping this destination (ping ip-address 1007 xxx.xxx.xxx.xxx).
2805 FAIL The number of pings received did not match the number sent (normally one ping is sent). This means that no ping responses were received from the destination region endpoint being tested back to the source endpoint sending the ping.
PASS TCP/IP Ping test between network regions is successful.
