DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Object Repair Procedures
9-793EXP-INTF (Expansion Interface Circuit Pack)
9
An Expansion Interface circuit pack yellow LED blinks slowly when a No
Neighbor condition exists (0.5 seconds on, 0.5 seconds off) and Test #237
fails on this Expansion Interface circuit pack, but Test #238 passes.
An SNI circuit pack with a no neighbor condition blinks its yellow LED
slowly (0.5 seconds on, 0.5 seconds off) and Test #759 fails on this SNI
circuit pack, but Test #989 passes.
■ If a Tone-Clock in an EPN that does not provide the current on-line
synchronization reference (see
status synchronization
) is providing an
invalid system clock:
In a direct connect configuration
, the PPN Expansion Interface circuit
pack yellow LED will blink quickly (Fiber Out-of-Frame condition - 0.1
seconds on, 0.1 seconds off).
Test #238 fails on this Expansion Interface circuit pack.
In a CSS configuration
, the SNI connected to the EPN Expansion Interface
circuit pack blinks its yellow LED quickly (Fiber Out-of-Frame condition -
0.1 seconds on, 0.1 seconds off).
The EPN Expansion Interface circuit pack yellow LED blinks slowly
(In-frame, No Neighbor condition - 0.5 seconds on, 0.5 seconds off).
If the EPN is in-service, Test #237 fails on this Expansion Interface circuit
pack, but Test #238 passes.
These symptoms can also be the result of other problems (for example, one half
of the fiber being unable to transmit data). If the system exhibits these symptoms,
execute the following procedure:
1. Verify that the EPN stays down for at least 1 minute.
If the EAL comes back in service after a short time, without switching the
Active Tone-Clock, the problem was probably that the on-line
synchronization source became invalid (See SYNC Maintenance
documentation for more information).
However, if the EAL (s) have not come back into service after a minute, the
synchronization source is not the cause of the problem. Proceed to Step 2.
2. Check for errors via the
display errors
command with the
Category
field
set to
tone
and the Active alarms field set to
n
. Some of the alarms on EPN
objects might have been resolved if the EPN went down. Refer to the
appropriate MO Maintenance documentation for descriptions of any of the
errors occurring at about the same time as the EXP-PN errors, SYS-LINK
errors against EAL s, RNLs, or LNLs, or FIBER-LK (769, 1025, or 1281)
errors. Resolve any active alarms. Also, if Error Type 18 was logged
against the SYNC MO when the EPN went down, the problem was
probably that the synchronization on-line reference became invalid. Since
reference switching was disabled, the Tone-Clock did not switch from the
invalid reference. Therefore, the Tone-Clock circuit pack put out a system
