
PKT-INT (Packet Interface)
Issue 4 May 2002
10-1295
555-233-123
Maintenance Object Interactions
■
Packet Bus Maintenance
Packet Interfaces 1A2 and 1B2 physically interact with the PKT-BUS
(Packet Bus). For certain types of Packet Interface errors, it may be difficult
to isolate the fault to one of these two components. In these cases, Packet
Interface maintenance will forward the error report to the Packet Bus
maintenance, thus causing Packet Bus maintenance to record a Packet
Bus fault in the hardware error log and to run appropriate Packet Bus tests.
■
Packet Circuit Pack Maintenance
The operation of Packet Interfaces 1A2 and 1B2 affect the operation and
maintenance of other circuit packs connected to the Packet bus. This
includes:
1. Expansion Interface circuit pack maintenance (EXP-INTF)
2. BRI applications (BRI-PT)
3. Universal DS1 applications (UDS1) for ISDN/PRI applications
4. C-LAN applications
5. ASAI applications
Some errors of Packet Circuit Packs may require examination of the
Packet Interface operating status. To obtain this information, examine the
Error and Alarm Logs for PKT-INT entries. Also issue the status
packet-interface command to determine the service state of the Packet
Interfaces (for example, in-service/out-of-service) and information about
the total number of Packet Interface links assigned to a Packet Interface
instance. For a Packet Interface in the standby SPE in a system equipped
with duplicated SPEs, a Packet Interface is in “standby” mode if it is not out
of service due to a failure condition. The number of links for a standby
Packet Interface is always zero.
In general, if all links for a Packet Interface circuit pack on an Active SPE
are shown in the “Failed Links” category, there may be a fault on the
Packet Interface or on the Packet Bus that caused all links to go down. If
only a small percentage of the links are shown as “Failed Links,” then the
Packet Interface is probably not the source of the problem. Examples of the
source of individual link failures include the failure of a BRI telephone set, a
disconnect of the cord to a BRI set, and a failure or removal of an
Expansion Interface circuit pack in an Expansion Port Network, The
disconnect of a BRI set causes three link failures and the removal of an EI
board in an EPN causes one link failure. Refer to Chapter 8, “Maintenance
Commands” for more information on the status packet-interface
command.
Содержание 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...