
PKT-INT (Packet Interface)
Issue 4 May 2002
10-1317
555-233-123
Active-Standby Peer Link Test (#888)
The Active-Standby Peer Link Test is only run in a system equipped with the High
Reliability or Critical Reliability Configuration. It verifies that the Peer Link can be
set up between the active and standby SPEs. The Peer Link is a link set up across
the Packet Bus between the Packet Interfaces on the active and standby SPEs. It
is used for forwarding data and control messages between the active and standby
SPE in preparation for a planned SPE interchange. This test not only checks the
operation of setting up a Peer Link but it also verifies that the active and standby
Packet Interfaces can communicate over the Packet Bus.
This test is run against the standby Packet Interface although it checks
functionality on both the active and standby Packet Interfaces.
Table 10-488.
TEST #888 Active-Standby Peer Link Test
Error
Code
Test
Result
Description/Recommendation
1006
1137
ABORT
Packet Interface is in the out-of-service state so normal
maintenance tests will not run on it.
1. Reset the Packet Interface using the reset
packet-interface CS command. Refer to the Packet
Interface Reset Test (#889) repair procedures for further
action.
1139
ABORT
The Packet Bus is alarmed.
1. Try to retire the alarm associated with the Packet Bus.
Refer to the Alarm Log through the display alarms
command. Refer to the PKT-BUS Packet Bus maintenance
documentation for further action.
2. Retry the command when the alarm associated with the
Packet Bus is retired.
1336
ABORT
Internal system error.
1. If you wish to run this test on the standby Packet Interface,
you must first make it active with reset system
interchange.
1338
ABORT
The test is not allowed to run since a planned SPE interchange
is in progress. A planned interchange may be caused by 24
hour scheduled testing. During this time the terminal will be
held out of service but it should recover automatically after 3
minutes.
1. Wait 3 minutes and retry the command.
Continued on next page
Содержание Definity SI
Страница 1: ...0DLQWHQDQFH IRU YD D 1 7 6HUYHU 6 Volumes 1 2 and 3 555 233 123 Issue 4 May 2002...
Страница 62: ...Maintenance Architecture 555 233 123 1 26 Issue 4 May 2002...
Страница 92: ...Management Terminals 555 233 123 3 26 Issue 4 May 2002...
Страница 204: ...Routine Maintenance Procedures 555 233 123 5 100 Issue 4 May 2002...
Страница 250: ...LED Interpretation 555 233 123 7 10 Issue 4 May 2002...
Страница 2763: ...VC DSPPT Issue 4 May 2002 10 1977 555 233 123 Figure 10 107 VC Circuit Pack DSP Port Local TDM Loopback Test...
Страница 2776: ...Maintenance Object Repair Procedures 555 233 123 10 1990 Issue 4 May 2002 Figure 10 109 VC Circuit Pack Summer Port Loopback Test...
Страница 2804: ...Maintenance Object Repair Procedures 555 233 123 10 2018 Issue 4 May 2002...
Страница 2968: ...Index 555 233 123 IN 10 Issue 4 May 2002...