GUIDANCE FOR HANDLING CRITICAL ALARM IN MULTIPLEXER EQUIPMENT

(U-NODE Series, UN5000, V-NODE)

PT. NEC Indonesia

4th Floor, Summitmas I, Jalan Jendral Sudirman Kav. 61-62
Jakarta Selatan, 12190
Ph. +021-5201215

CONTENTS

AIS ..
AIS_RX .
AIS_TX .
AU_AIS_RX ..
AU_AIS_TX
BVPERR ..
DEG_RX ..
LINKDOWN ..
LOF .
LOS .
MS_AIS ..
MS_DEG .
MS_RDI ..
PPS_FAIL .
RDI .
TU_AIS .
UNEQ

Troubleshoot Guidance

3
3
3
4
4
5
6
6
7
7
8
8
9
10
10
10
11

1. AIS
Description
This message indicates that the AIS (alarm indication signal) is detected from the incoming signal on the
indicated facility. If this condition occurs, the problem is on the indicated line in the far-end NE.
Clear AIS Condition
1. Check if an alarm occurs to a facility or path in the far-end NE that is associated with the
indicated facility, and clear them by following instruction for the far-end NE.
2. Retrieve the Current Alarms & Events, and verify the condition.
This step is the end of the procedure
2. AIS_RX
Description
This message indicates that the AIS (alarm indication signal) is detected from the incoming signal (RX) on
E32 facility. If this condition occurs, the problem is on the indicated line in the far-end NE.
Clear AIS_RX Condition
1. Check if an alarm occurs in the far-end NE that is associated with the indicated E32 facility, and
clear it by following instruction for the far-end NE.
2. Retrieve the Current Alarms & Events, and verify the condition
This step is the end of the procedure.
3. AIS_TX
Description
This message indicates that the AIS (alarm indication signal) is detected from the outgoing signal (TX) on
E32 facility. The AIS is inserted if an LOS, LOF, AIS, or LPBKFACILITY is detected from E32 facility at farend NE. If this condition occurs, the problem is on the indicated line in the far-end NE. The condition
should be cleared when these alarms causing the node to send the AIS to downstream are cleared.
Clear AIS_TX Condition
1. Check the alarm at the far-end NE for the indicated E32 facility and the NE that is connected to
this far-end NE via the E32 line.
If a LOS, LOF, AIS, or LPBKFACILITY alarm occurs to the E32 facility of the far-end NE, clear it
by following the corresponding instructions (refer to 1 AIS, 10.7.40 LOF, 10.7.44 LOS, or
10.7.45 LPBKFACILITY).
If any alarms occur in the NE that is connected to the far-end NE, clear them by following
instructions for that NE.
2. Retrieve the Current Alarms & Events, and verify the condition.
This step is the end of the procedure.

Troubleshoot Guidance

4. AU-AIS_RX
Description
This message indicates that the AIS (Alarm Indication Signal) is detected from the incoming signal on the
line facility. The problem exists not in the local NE but does between the local NE and the point
generating AU3/AU4 indicated by the AID

Clear AU-AIS_RX Condition

1. Retrieve the Current Alarms & Events, and locate a path signal failure that has caused the
condition.
2. Clear the failure of path signal.
3. Retrieve the Current Alarms & Events, and verify the condition.
4. Is the alarm cleared?
YES: This step is the end of the procedure.
NO: Replace the interface package whose facility is in AU-AIS_RX condition.
5. Retrieve the Current Alarms & Events, and verify the condition.
This step is the end of the procedure.
5. AU-AIS_TX
Description
This message indicates that the AIS (Alarm Indication Signal) is detected from the outgoing signal on the
line facility.

Clear AU-AIS_TX
1. Verify the following:
Verify that the crossconnection is specified correctly.
Locate the AU3/AU4 to which the alarmed facility is crossconnecting, and if an AU-AIS_RX
alarm exists there, clear it.
Troubleshoot Guidance

Verify the interface package of the AU3/AU4 to which the alarmed facility is
crossconnecting, and clear any alarms if occurred.
If a SQLCH_n exists on the facility, clear it.
Retrieve the Current Alarms & Events, and verify the condition.
Is the AU-AIS_TX condition cleared?
YES: This step is the end of the procedure.
NO: By referring to the 5. Hardware Replacement section, replace the interface package to
which the alarmed facility is crossconnecting. If the package is already replaced in Step 1, go
to Step 5.
Retrieve the Current Alarms & Events, and verify the condition.
Is the alarm cleared?
YES: This step is the end of the procedure.
NO: Replace the PSW40B package.
Retrieve the Current Alarms & Events, and verify the condition.
Is the alarm cleared?
YES: This step is the end of the procedure.
NO: Replace the interface package whose facility is in the AU-AIS_TX condition.
Retrieve the Current Alarms & Events, and verify the condition
This step is the end of the procedure.

2.
3.

4.
5.

6.
7.

8.

6. BPVERR (Bipolar Verification Error)

Description
This message indicates that an error for bipolar coding rule is detected from incoming signal on the
indicated facility.
Clear BPVERR Condition
1. The problem may exist in the far-end NE. Verify the interface package in the far-end
NE that is associated with the alarmed facility and clear any alarms if exist.
2. Retrieve the Current Alarms & Events, and verify the condition.
3. Is the alarm cleared?
YES: This step is the end of the procedure.
NO: Execute the switch operation to the target package.
4. Retrieve the Current Alarms & Events, and verify the condition.
5. Is the alarm cleared?
YES: Replace the alarmed package that is switched to the protection side.
NO: Contact NEC for the appropriate maintenance support.
6. Retrieve the Current Alarms & Events, and verify the condition.
This step is the end of the procedure.

Troubleshoot Guidance

7. DEG_RX (Degraded Receive Level)

Description
This message indicates that the B3 error (MIN) is detected on the higher or lower order path or monitor
facility, or that the V5 bit-2 error (MIN) is detected on the lower order path monitor facility.
Clear DEG_RX Condition
1. Verify if any alarms exist between the local NE and far-end NE, and clear the condition.
2. Verify the optical connector:
Clean the optical connectors (plug and receptacle) NOTE: Clean Optical Connectors.
Check if the optical level is appropriate. Inspect Optical Connectors. Optical fiber cables
must be routed in the appropriate way.
3. Retrieve the Current Alarms & Events, and verify the condition.
4. Is the alarm cleared?
YES: This step is the end of the procedure.
NO: Replace the interface package of the local NE.
5. Retrieve the Current Alarms & Events, and verify the condition.
6. Is the DEG_RX alarm cleared?
YES: This step is the end of the procedure.
NO: Replace the interface package of the far-end NE.
7. Retrieve the Current Alarms & Events, and verify the condition.
This step is the end of the procedure.
8. LINKDOWN
Description
This message indicates that a link between the facility indicated by AID and the far-end NE could not be
established. LINKDOWN detection is available when the Auto-Negotiation is disabled.
Clear LINKDOWN Condition
1. Verify the following:
Verify the auto-negotiation setting at the far-end NE (a router, etc.) that is associated with
the reported facility. Clear any setting errors if they exist.
Check the cables related to the alarmed facility if they are correctly connected.
When the alarmed facility is GBEMF, verify the optical input level for it. If it is inappropriate
(too low or high), adjust the input level by using an attenuator or clean plugs of optical fiber
cables by referring to the 4.1 Inspect and Clean Optical Connectors subsection.
2. Retrieve the Current Alarms & Events, and verify the condition.
3. Is the alarm cleared?
YES: This step is the end of the procedure.
NO: Replace the package reporting the LINKDOWN alarm.
4. Retrieve the Current Alarms & Events, and verify the condition.
This step is the end of the procedure.
Troubleshoot Guidance

9. LOF
Description
This message indicates that a loss of frame (LOF) is detected on the facility indicated by the AID. If this
condition occurs, the problem is on the indicated line in the far-end NE, or in the optical/electrical path
between the local NE and far-end NE. This condition indicates for SINF16F, SINF64F, SINFMF, and
STM1EF facilities.
Clear LOF Condition
1. Verify that the cable of the indicated facility is properly connected.
For the optical cables, also check the optical plugs and receptacles of the alarmed facility and
those in the far-end NE.
Using a video fiber scope, inspect plugs and receptacles (refer to 4.1.1 Inspect Optical
Connectors). If they are contaminated with dirt and dust particles, clean them by referring
to 4.1.2 Clean Optical Connectors.
Using an optical power meter, measure the optical output/input power to see if the level is
within the appropriate range. Refer to the Package Description/Installationmanual for each
specification.
2. Check the interface package of the far-end NE that is associated with the alarmed facility, and
clear the problem.
3. Retrieve the Current Alarms & Events, and verify the condition.
4. Is the alarm cleared?
YES: This step is the end of the procedure.
NO: Replace the interface package reporting the LOF alarm at the local NE.
5. Retrieve the Current Alarms & Events, and verify the condition
This step is the end of the procedure.
10. LOS
Description
This message indicates that a loss of signal (LOS) is detected on the facility indicated by the AID. If this
condition occurs, the problem is on the indicated line in the far-end NE, or in the electrical/optical path
between the local NE and far-end NE.
Clear LOS Condition
1. Verify the following:
Verify if the appropriate fiber cables are properly and securely connected. For the optical
cables, also check the optical plugs and receptacles of the alarmed facility and those in the
far-end NE.
Using a video fiber scope, inspect plugs and receptacles (refer to 4.1.1 Inspect Optical
Connectors). If they are contaminated with dirt and dust particles, clean them by
referring to 4.1.2 Clean Optical Connectors.

Troubleshoot Guidance

 Using an optical power meter, measure the optical output/input power to see if the
level is within the appropriate range. Refer to the Package Description/ Installation
manual for each specification.
Verify if the connected cables and connectors are not defective.
If any alarms have occurred to the interface package of the far-end NE whose facility is
associated with the alarmed facility, clear them.
2. Retrieve the Current Alarms & Events, and verify the condition.
3. Is the alarm cleared?
YES: This step is the end of the procedure.
NO: By referring to the 5. Hardware Replacementsection, replace the package whose facility
is in the LOS condition.
4. Retrieve the Current Alarms & Events, and verify the condition. If the alarm is
not cleared, contact NEC for the appropriate maintenance support.
This step is the end of the procedure.
11. MS-AIS
Description
This message indicates that the alarm indication signal (AIS) is detected from the incoming
signal on the indicated facility of the multiplex section line (MS).
Clear MS-AIS Condition
1. Retrieve the Current Alarms & Events, and locate any alarms that have caused inserting AIS.
Also, verify the following:
Check PSW40B package(s) of the far-end NE associated with the indicated facility, and
confirm (both) PSW40B package(s) is/are properly installed.
If the opposing NE is U-Node REG, check if LOS is detected between REGs.
2. Clear the alarm(s).
3. Retrieve the Current Alarms & Events, and verify the condition.
4. Is the alarm cleared?
YES: This step is the end of the procedure.
NO: Replace the package whose facility is in the MS-AIS condition.
5. Retrieve the Current Alarms & Events, and verify the condition. If the alarm is not cleared,
contact NEC for the appropriate maintenance support.
This step is the end of the procedure.
12. MS-DEG
Description
This message indicates that the B2 error (MIN) is detected from the incoming signal on the indicated
facility of the multiplex section line (MS). If this condition occurs, the problem is on the indicated line in
the far-end NE, or in the optical path between the local and the far-end NE.

Troubleshoot Guidance

Clear MS-DEG Condition

1. Verify the following:
If an alarm has occurred to the package of the far-end NE that is associated with the
indicated facility, clear the alarm.
Dust and dirt may be considered to cause the error. Clean the optical connectors of the
reported facility, such as the optical plugs of the fiber cables and the receptacles on the
packages, by referring to the 4.1 Inspect and Clean Optical Connectors subsection.
NOTE:Confirm that connection must be securely made again after cleaning.
2. Retrieve the Current Alarms & Events, and verify the condition.
3. Is the alarm cleared?
YES: This step is the end of the procedure.
NO: Replace the package of the indicated facility.
4. Retrieve the Current Alarms & Events, and verify the condition. If the alarm is not cleared,
contact NEC for the appropriate maintenance support.
This step is the end of the procedure.
13. MS-RDI
Description
This message indicates that the Remote Defect Indication (RDI) is detected from the incoming signal on
the indicated facility of the multiplex section line (MS). The MS-RDI is issued when a LOS, LOF
(consecutive B2 error), MS-AIS, or RS-TIM NOTE: alarm is detected at the far-end NE. If this condition
occurs, the problem is in the indicated line at the local NE, or in the optical path between the local NE
and far-end NE.

NOTE:RS-TIM may not be a cause of reporting MS-RDI if the AIS (detection) is not
selected for the Section Trace setup.
Clear MS-RDI Condition
1. Check if an alarm such as LOS, LOF, MS-AIS, or RS-TIM has occurred to the local
NE, and clear the alarm.
2. Retrieve the Current Alarms & Events, and verify the condition.
3. Is the alarm cleared?
YES: This step is the end of the procedure.
NO: Some errors above may be disclosed by eliminating RS-TIM. Check if any of them still
exists, and clear it/them.
4. Retrieve the Current Alarms & Events, and verify the condition.
Troubleshoot Guidance

5. Is the alarm cleared?

YES: This step is the end of the procedure.
NO: Replace the alarmed package.
6. Retrieve the Current Alarms & Events, and verify the condition. If the alarm is not cleared,
contact NEC for the appropriate maintenance support.
This step is the end of the procedure.
14. PPS_FAIL
Description
This message indicates that a path protection switching (PPS) has failed in the 1-Way PPS or
2-Way PPS configuration. If this condition occurs, the problem is in both incoming paths
from which the path selector could not select an outgoing path.
Clear PPS_FAIL Condition
1. Verify if any alarms causing PPS_FAIL have occurred to the local NE and far-end NE that are
associated with the indicated path, and clear them.
2. Retrieve the Current Alarms & Events, and verify the condition.
This step is the end of the procedure.
15. RDI
Description
This message indicates that a path remote defect indication (RDI) is detected from the path
terminated at the GBEM (HPTM3) or from the higher order/lower order path (HPT/LPT).
Clear RDI Condition
1. Verify the following:
Verify the indicated path (HPT, HPT3 or LPT) at the far-end NE for alarms, such as UNEQ,
TIM causing RDI*, and clear them. *: When AIS detection is not selected for LPT/HPT
path trace (CDI path: Provisioning Trace Path Trace), TIM is not a cause reporting
RDI.
When RDI is reported for HPT or LPT facility, also verify the interface package if it works
properly. If not, replace the package.
2. Retrieve the Current Alarms & Events, and verify the condition.
This step is the end of the procedure.
16. TU-AIS
Description
This message indicates that the AIS (Alarm Indication Signal) is detected from the incoming
signal on the line facility. The problem exists not in the local NE but does between the local
NE and the point generating TU-3/TU-12 indicated by the AID.
Clear TU-AIS Condition
1. Check the following and correct any problems:
Crossconnect configuration is correctly set.
Interface packages are installed securely on the far-end NE that terminates the TU path.
There is no failure on the line connecting the TU path signal.
Troubleshoot Guidance

10

2. Retrieve the Current Alarms & Events, and verify the condition.
3. Is the alarm cleared?
YES: This step is the end of the procedure.
NO: Replace the interface package whose facility is in TU-AIS condition.
3. Retrieve the Current Alarms & Events, and verify the condition. If the alarm is not cleared,
contact NEC for the appropriate maintenance support.
This step is the end of the procedure.
17. UNEQ
Description
This message indicates that the unequipped code (UNEQ) is detected on the HPTM3, HPT or
LPT.
Clear UNEQ Condition
1. Retrieve the Current Alarms & Events, and determine the facility reporting the
condition.
2. Verify the following, and correct them:
Confirm that the crossconnect setups are correct.
Confirm that the far-end NE is not sending UNEQ on the path.
3. Retrieve the Current Alarms & Events, and verify the condition. If the alarm is not cleared,
contact NEC for the appropriate maintenance support.
This step is the end of the procedure.

Troubleshoot Guidance

11