
Maintenance Object Repair Procedures
555-233-123
10-776
Issue 4 May 2002
t. In response to Error Type 10002, the system denied all calling services for
up to 10 seconds.
If EI Error Type 257 is logged at the same time against an Expansion
Interface circuit pack on this link, first try to resolve this error. The error
associated with Error Type 257 could be the cause of this error.
If Error Type 257 is not logged at the same time as this error, then Error
Type 10002 indicates that heavy call traffic was encountered involving EPN
endpoints.
No system technician action is required; however, should this error recur
frequently, the system should be examined for traffic engineering. The PPN
and EPNs may not be equipped with sufficient trunks and Tone Detectors
for the number of stations in each cabinet.
u. Error Type 10003 indicates that heavy call traffic involving EPN endpoints
has returned to normal levels. This Error Type should always appear after
Error Type 10002 or 10004. No system technician action is required.
v. Error type 10004 indicates that an extreme backup of traffic was present on
the EI circuit pack. The EPN served by this link was most probably not
providing service when this error was logged. If this is a high or critical
reliability system, the system should have switched to the Standby
Expansion Link in order to restore service. Error type 11000 with an Aux
value of 5 should have been logged against EXP-INTF to indicate this
condition.
In a standard system, the system should have reset the EPN in order to
restore service. EXP-LINK Error Type 122 with an Aux value of 6 should
have been logged to indicate this condition.
w. Error Type 11000 with an Aux value of 0 appears when an EI Link switch
takes place. Data calls between the PPN and EPN may have experienced
some data loss or, in severe cases, the data calls may have dropped. The
link that became active is the link with the circuit pack address given in the
Error Log entry. The link switch may have occurred for several reasons:
1. System Technician demanded the Expansion Interface Link switch.
This can be verified by using the list history command.
2. The Expansion Interface Link switch may have been scheduled.
Check the Maintenance-Related System Parameters form.
3. An Expansion Interface circuit pack error may have been detected.
Examine the Error Log for other EI circuit pack errors with the same
approximate time as this error.
Содержание 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...