RJIL - iPASOLINK Ix - Alarms & Troubleshooting PDF [PDF]

Citation preview

NEC iPASOLINK iX Alarms & Troubleshooting Document RJIL NEC MW Rev 1.0 5/5/2015



1



INDEX Content 1 Corrective Maintenance…………………………………………………………………………………4 1.1 Reporting Method……………………………………………………………………………………………………………....…….4 1.2 View Current Status…………………………………………………………………………………………………….……………..4



2 Main Card Alarms & Troubleshooting Process……………………………………..………….6 2.1 Bus Error……………………………………………………………………………………………………………………..……………..6 2.2 Clock Drift Alarm……………………………………………………………………………………………………..………………….6 2.3 Clock Fail Alarm………………………………………………………………………………………………………..…………………7 2.4 LTI………………………………………………………………………………………………………………………………………..….....7 2.5 MDU CPU Alarm………………………………………………………………………………………………….……….……………..7 2.6 Memory fail……………………………………………………………………………………………………….……….……………….8 2.7 Module……………………………………………………………………………………………………………….……….………………8 2.8 SSM Fail……………………………………………………………………………………………………………….…….………………..8 2.9 Temperature……………………………………………………………………………………………………….…….…………………9



3 ODU Alarms & Troubleshooting Process……………………………………..………………….10 3. 1 ODU Alarm………………………………………………………………………………………………..………………………………10 3.2 ODU CPU/Cable open………………………………………………………………………………..……………………………….10 3.3 RX Level……………………………………………………………………………………………………..……………………………….10 3.4 TX Input……………………………………………………………………………………………………………………………………….11 3.5 TX Power……………………………………………………………………………………………………………………………………..11 3.6 Type Mismatch…………………………………………………………………………………………………………………………….11



4 Modem Alarms & Troubleshooting Process………………………..………………………….. 12 4.1 Low BER…………………………………………………………………………………………………………………………………………12 4.2 MOD………………………………………………………………………………………………………………………………………………12 4.3 ODU Power Supply…………………………………………………………………………………………………………………………12 4.4 Radio Traffic Aggregation Mismatch…………………………………………..…………………………………………………13 4.5 RDI……………………………………………………………………………………………………………………….…………..……………13 4.6 RX Bus Error……………………………………………………………………………………………………………………..……………14 4.7 TX Bus Error…………………………………………………………………….…………………………………………….………………14 4.8 UAE…………………………………………………………………………………………….………………………………….………………14 4.9 Unlocked……………………………………………………………………………..…………………………………………………………15 4.10 AMR Mismatch…………………………………………………….………………………………………………………………………15 4.11 CLK Fail…………………………………………………………………………………………………………………………………..……15 4.12 Communication Fail………………………………………………………………………………………….…………………………16 4.13 Compression Setting Mismatch……………………………………………………………………………………………………16 4.14 Early Warning………………………………………………………………………………………………………………………………16



2



4.15 Frame ID……………………………………………………………………………………………………………………….…………17 4.16 High BER…………………………………………………………………………………………………………………….……………17 4.17 IF Cable Short……………………………………………………………………………………………………..……………………17 4.18 L2SYNC Loss…………………………………………………………………………………………………………..…………………18 4.19 LOF…………………………………………………………………………………………………………………………..………………18



5 GbE Alarms & Troubleshooting Process 5.1 Eth LOS……………………………………………………………………………………………………………………………….………19 5.2 Eth TF……………………………………………………………………………………………………………………………….…………19 5.3 LAN Link………………………………………………………………………………………………………………………………………19 5.4 Link OAM Down……………………………………………………………………………………………………………………………20 5.5 Remote Critical Event……………………………………………………………………………..……………………………………20 5.6 Remote Dying Gasp………………………………………………………………………………………………………………………21 5.7 Remote Link Fault…………………………………………………………………………………………………………………………21 5.8 SFP Removed………………………………………………………………………………………..………………………………………21 5.9 SFP Mismatch………………………………………………………………………………….……………………………………………22 5.10 LAG Link……………………………………………………………………………………………..………………………………………22 5.11 License Mismatch…………………………………………………………………….…………………………………………………23



6. Flowchart for Troubleshooting ODU TX Section……………………………………………….24 7. Flowchart for Troubleshooting ODU RX Section………………..……………………………..25 8. Flowchart for Troubleshooting MDU Section………………….…………………………………26



3



1. Corrective Maintenance 1.1 Reporting Methods Equipment condition can be obtained by the Web LCT. The condition is also visibly reported using indication lamps on the equipment. iPASOLINK defines the following alarm status: Alarm Status



CL indicates that one or more previously reported alarms has/have been cleared. This state applies to all alarms detected for this managed object with the same alarm type, probable cause and specific problems (if given). Multiple associated notifications may be cleared by using the Correlated notifications parameter (defined below).



ID indicates that the detected condition cannot be determined to classify the severity level. CR indicates for the Critical Alarm that causes a service affecting failure, which requires an immediate corrective action. If this level of condition is reported, the managed object could totally go out of service, restoring its capability.



]: MJ indicates for the Major Alarm that causes a service affecting failure which requires an urgent corrective action. If this level of condition is reported, the capability of the managed object could be severely degraded, restoring its full capability. MN indicates for the Minor Alarm that detects the existence of a non-service affecting condition, which requires the corrective action in order to prevent a more serious (such as a service affecting) failure. This condition does not degrade the capacity of the managed object.



WR indicates for the detection of a potential or impending service affecting fault, before any significant effects have been felt. Action should be taken to further diagnose (if necessary) and correct the problem in order to prevent a more serious failure, such as a service affecting fault.



1.2 VIEW CURRENT STATUS Overview Current Status window of the Web LCT displays the equipment status, event logs and alarms detected by the equipment. The window displays the view-only information; not editable.



Display Current Status Window Procedure 1. Launch and log in to Web LCT. The initial (main) window of the Web LCT displays the Current Status window; or if Web LCT is already logged in, click the Current Status on top of the MENU frame in the left. The main window in the right displays Current Status window. 2. Click the Refresh tool button. the detected information is displayed.



Figure Current Status (Initial Window) The Current Status window provides the information on the following objects



4



separated by tabs on which their items are indicated:  Active Alarm  Event Log  MODEM/ODU  MDU  GbE



Active Alarm Tab The Active Alarm tabbed window displays all the current alarms that have been detected by the equipment. The displayed information can be saved onto the storage area of WebLCT PC. To save the information, click the Save button located within the Active Alarm list. See Save the Displayed Information for an example.



5



2 Main Card Alarms & Troubleshooting Process 2.1 Bus Error Indication



Category



Description



Severity



Bus Error



Alarm



Data communication Bus failure has been detected.



MJ



Troubleshooting: Bus Error If Alarm is indicated for the Status, a failure occurs to the Bus on the indicated Main Board. Please contact NEC for the further maintenance support.



2.2 Clock Drift Alarm Indication



Category



Description



Severity



CLK Drift



Alarm



Drift condition has been detected from Reference Clock Source Frequency.



MN



Troubleshooting: CLK Drift If its Status indicates Alarm, the reference clock frequency of the incoming signal of the indicated facility is out of synchronized range. The problem of this condition pertains to the opposing site equipment. Procedure 1. Check if any alarms occur to the equipment in the other site, and clear them. 2. Retrieve the Current Status, and check if the CLK Drift alarm is cleared. 3. Is the CLK Drift alarm cleared? YES: This step ends the procedure. NO: Go to Step 4. 4. Check if any alarm(s) issued to the indicated port/line is/are cleared. 5. Is any alarm reported to the indicated port/line? YES: Clear it/them then go to the next step. NO: Contact NEC for the further maintenance support. 6. Retrieve the Current Status, and check if the CLK Drift alarm is cleared. If the Alarm is not cleared; contact NEC for the further maintenance support. This step ends the procedure.



6



2.3 Clock Fail Alarm Indication



Category



Description



Severity



CLK FAIL



Alarm



Reference Clock failed.



MN



Troubleshooting: CLK FAIL If its Status indicates Alarm, the reference clock source failure is detected from the incoming signal of the indicated facility. The problem of this condition pertains to the optical or electrical Ethernet cable of the opposing site Procedure 1. Check if any other alarm(s) is/are detected from/for the indicated facility or from the other site. 2. Clear the alarm(s). 3. Retrieve the Current Status, and check if the CLK Fail alarm is cleared. If the alarm is not cleared contact NEC for the further maintenance support. This step ends the procedure.



2.4 LTI Indication LTI



Category Alarm



Description Loss of Incoming Timing Inputs have been detected.



Severity MJ



Troubleshooting: LTI If its Status indicates Alarm, the system detects LTI (Loss of Timing Inputs) where the equipment does not synchronize with any reference sources The problem of this condition pertains to the optical fiber cables, electrical cables, or to the far-end NE Procedure 1. Check if any alarm regarding the reference clock occurs. If any exist(s), clear it/ 2. Retrieve the Current Status, and check if the LTI alarm is cleared. If the alarm is not cleared, contact NEC for the further maintenance support. This step ends the procedure.



2.5 MDU CPU Alarm Indication MDU CPU Alarm



Category Alarm



Description Failure of Main Board CPU has been detected.



Severity MJ



Troubleshooting: MDU CPU Alarm If Alarm is indicated for the Status, the CPU on the MODEM has a failure. Procedure 5-24 1. Launch WebLCT. 2. Click the Maintenance tool button on the WebLCT.



7



3. Execute the CPU Reset to the target MODEM. ◆ WebLCT Menu Path: Maintenance Control ➜ H/W F/W Reset Control For details, refer to 4.7 Reset Equipment for the resetting procedure. 4. Retrieve the Current Status, and check if the MDU CPU Alarm is cleared. 5. Is MDU CPU Alarm cleared? w YES: This step ends the procedure. w NO: Go to Step 6. 6. Execute the H/W Reset to the standby MODEM. 7. Retrieve the Current Status, and check if the MDU CPU Alarm is cleared. 8. Is MDU CPU Alarm cleared? w YES: This step ends the procedure. w NO: Contact NEC for the further maintenance support. This step ends the procedure.



2.6 Memory Fail Indication Memory FAIL



Category Alarm



Description Failure of Main Board Memory has been detected.



Severity MJ



Troubleshooting: Memory FAIL If Alarm is indicated for the Status, the system detects an error in the Main Board memory. Please contact NEC for the further maintenance support.



2.7 Module Indication Module



Category Alarm



Description Equipment failure.



Severity MJ



Troubleshooting: Module If its Status indicates Alarm, the system detects the hardware error of the indicated block. Procedure 1. Replace the iPASOLINK iX. 2. Retrieve the Current Status, and check if the Module alarm is cleared. If the alarm is not cleared, contact NEC for the further maintenance support. This step ends the procedure.



2.8 SSM Fail Indication SSM Fail



Category Alarm



Description Received Sync Status Message value is in unstable condition.



Severity MN



8



Troubleshooting: SSM Fail If its Status indicates Alarm, the received Sync Status Message is in the unstable condition. The problem of this condition pertains to the input cable.



2.9 Temperature Indication Temperature



Category Alarm



Description The temperature exceeds the threshold.



Severity MN



Troubleshooting: Temperature If its Status indicates Alarm, the temperature within the equipment rises over the operational range. Possible cause may be the hardware failure Procedure 1. Replace the iPASOLINK iX. 2. Retrieve the Current Status, and check if the Temperature alarm is cleared. If the alarm is not cleared, contact NEC for the further maintenance support. This step ends the procedure.



9



3 ODU Alarms & Troubleshooting Process 3. 1 ODU Alarm Indication ODU Alarm



Category Alarm



Description Indicates that the fatal error occurs to ODU.



Severity MJ



Troubleshooting: ODU Alarm If Alarm is indicated for the Status, the hardware error is detected from ODU. Procedure 1. Replace ODU 2. Retrieve the Current Status, and check if the ODU Alarm is cleared. If the alarm is not cleared, contact NEC for the further maintenance support This step ends the procedure.



3.2 ODU CPU/Cable Open Indication ODU CPU / Cable Open



Category Alarm



Description CPU of ODU fails, or IF Cable between MDU and ODU is disabled or is not connected.



Severity MJ



Troubleshooting: ODU CPU / Cable Open If Alarm is indicated for the Status, the CPU on ODU has a failure, or IF Cable between MDU and ODU is not properly connected.



3.3 RX Level Indication RX Level



Category Alarm



Description Receiving level is lower than the threshold that is between –72 to –94 dBm according to the modulation system and bit rates.



Severity MJ



Troubleshooting: RX Level If its Status indicates Alarm, the receiving level is lower than the threshold level. Check the level using the flowchart: 5.4 Replacing Procedures for Radio Portion.



10



3.4 TX Input Indication TX Input



Category Alarm



Description TX IF Signal is out of range that is –29 dBm ±5 dB.



Severity MJ



Troubleshooting: TX Input If Alarm is indicated for the Status, TX IF signal level is out of the range (–29 dBm ±5 dB). Refer to Replacing Procedures for Radio Portion for the procedure(s).



3.5 TX Power Indication TX Power



Category Alarm



Description Transmitting power is lower than 3 dB.



Severity MJ



Troubleshooting: TX Power If Alarm is indicated for the Status, the transmitting power level of ODU is lower than 3dB. Refer to Replacing Procedures for Radio Portion for the procedure(s).



3.6Type Mismatch Indication Type Mismatch



Category Alarm



Description Connected ODU type is not supported by iPASOLINK system, or is not operational by the provisioned modulation settings.



Severity MJ



Troubleshooting: Type Mismatch If Alarm is indicated for the Status, the indicated object is not supported by iPASOLINK system, or is not operational by the provisioned modulation settings. Procedure 1. Launch the WebLCT, and display the Inventory window to check the configuration. If any setting is found inappropriate, correct it/them. 2. Retrieve the Current Status, and check if the Type Mismatch alarm is cleared. 3. Is the alarm cleared? YES: This step ends the procedure. NO: Replace the indicated object, then go to Step 4. 4. Retrieve the Current Status, and check if the Type Mismatch alarm is cleared. If the alarm is not cleared, contact NEC for the further maintenance support. This step ends the procedure.



11



4 Modem Alarms & Troubleshooting Process 4.1 Low BER Indication Low BER



Category Alarm



Description Radio signal is degraded (Low BER threshold, where the threshold is 1E– 6/1E–7/1E–8/1E–9).



Severity MN



Troubleshooting: Low BER If its Status indicates Alarm, radio signals are degraded (too low). Procedure 1. Launch the WebLCT. MODEM 2. Display the Current Metering to check RX Level. from maintenance manual for Replacing Procedures for Radio Portion. This step ends the procedure.



4.2 MOD Indication MOD



Category Alarm



Description Indicates the operating status of Modulator. The Status indicates Alarm if a failure occurs in the Modulator section.



Severity MJ



Troubleshooting: MOD If Alarm is indicated for the Status, the MODEM fails to output power. Please contact NEC for the further maintenance support.



4.3 ODU Power Supply Indication ODU Power Supply



Category Alarm



Description Power is not supplied to ODU.



Severity MJ



Troubleshooting: ODU Power Supply If Alarm is indicated for the Status, the power supply to ODU fails. Procedure 1. Launch WebLCT to display the ODU Power Control window. ◆ WebLCT Menu Path:



12



Maintenance Control ➜ ODU Power Control 2. Check if the ODU Power is set to on. If it is set to on, replace the ODU. This step ends the procedure.



4.4 Radio Traffic Aggregation Setting Mismatch Indication Radio Traffic Aggregation Setting Mismatch



Category Alarm



Description RTA settings at local and that of remote do not match; or the firmware version, license, and/or FPGA version of MODEM is/ are not compliant with RTA function.



Severity MJ



Troubleshooting: Radio Traffic Aggregation Setting Mismatch If Alarm is indicated for the Status, RTA (Radio Traffic Aggregation) settings at the local and that at the remote do not match or the firmware version, license, and/or the FPGA version of MODEM is/are not compliant with the RTA function. Procedure 1. At both the local and remote side, check the firmware version, license, and MODEM’s FPGA version of the Radio Group that is issuing the alarm, and correct it/them if any is/are wrong. 2. Retrieve the Current Status, and check if the Radio Traffic Aggregation Setting Mismatch is cleared. YES: This step ends the procedure. NO: Check and correct the RTA Settings at both local and remote side. 3. If the alarm is not cleared, contact NEC for the further maintenance support. This step ends the procedure.



4.5 RDI Indication RDI



Category Alarm



Description Remote Defect Indication has been detected at MODEM port.



Severity MJ



Troubleshooting: RDI If its Status indicates Alarm, RDI (Remote Defect Indication) signal is detected. Procedure 1. Check if any alarm(s) occur(s) in the opposing site equipment. If any exist(s), correct it/them.



2. Retrieve the Current Status, and check if the RDI alarm is cleared. If the alarm is not cleared, contact NEC for the further maintenance suppo This step ends the procedure.



13



4.6 RX Bus Error Indication RX Bus Error



Category Alarm



Description Detects data communication Bus failure in the incoming direction at MODEM.



Severity MJ



Troubleshooting: RX Bus Error If Alarm is indicated for the Status, Bus Error (equipment internal failure) is detected at the receiving port. A hardware failure is likely to cause this condition. Please contact NEC for the further maintenance support.



4.7 TX Bus Error Indication TX Bus Error



Category Alarm



Description Data communication Bus failure in the outgoing direction at MODEM Card.



Severity MJ



Troubleshooting: TX Bus Error If Alarm is indicated for the Status, the data communication Bus failure is detected from a signal at the outgoing direction. This condition is caused by the hardware failure on the Card. Please contact NEC for the further maintenance support.



4.8 UAE Indication UAE



Category Alarm



Description Unavailable Seconds Event has been detected.



Severity MN



Troubleshooting: UAE If its Status indicates Alarm, the Unavailable Second Event is detected. Procedure 1. Check if any other alarm(s) occur(s), and clear it/them. 2. Retrieve the Current Status, and check if the UAE alarm is cleared. If the alarm is not cleared, contact NEC for the further maintenance support. This step ends the procedure.



14



4.9 Unlocked Indication Unlocked



Category Alarm



Description Wireless synchronization status at the local side is set to unlocked.



Severity MJ



Troubleshooting: Unlocked If its Status indicates Alarm, the status of Wireless Synchronization at the local side is unstable (clock is not locked). Procedure 1. Check the equipment clock setting at both local and its opposing site, and adjust it/them 2. Retrieve the Current Status, and check if the Unlocked alarm is cleared. If the alarm is not cleared, contact NEC for the further maintenance support.



4.10 AMR Range Mismatch Indication AMR Range Mismatch



Category Alarm



Description Indicates a mismatched condition by detecting that mapped numbers of E1 channels at TX MODEM ports and those at RX MODEM ports do not match; or the range of RX AMR modula- tion and that of TX AMR modulation do not match.



Severity MJ



Troubleshooting: AMR Range Mismatch If its Status indicates Alarm, the selected RX AMR modulation and TX AMR modulation do not match. Procedure 5-4 Specify the same AMR Configuration to both the local and its opposing NE. Refer to the Operation manual for the details.



4.11 CLK FAIL Indication CLK FAIL



Category Alarm



Description Reference Clock failed.



Severity MN



Troubleshooting: CLK FAIL If its Status indicates Alarm, the reference clock source failure is detected from the



incoming signal of the indicated facility. The problem of this condition pertains to the optical or electrical Ethernet cable of the opposing site. Procedure 1. Check if any other alarm(s) is/are detected from/for the indicated facility or from the other site. 2. Clear the alarm(s). 3. Retrieve the Current Status, and check if the CLK Fail alarm is cleared. If the alarm is not cleared, contact NEC for the further maintenance support.



15



This step ends the procedure.



4.12 Communication FAIL Indication Communication FAIL



Category Alarm



Description Controls of equipment internal communication failed.



Severity MJ



Troubleshooting: Communication FAIL If Alarm is indicated for the Status, a failure occurs in the equipment internal communication among the modules. Contact NEC for the further maintenance support. .



4.13 Compression Setting Mismatch Indication Compression Setting Mismatch



Category Alarm



Description Header Compression Modes of MODEM Cards at two opposed sites do not match.



Severity MJ



Troubleshooting: If its Status indicates Alarm, Header Compression settings at two opposed sites do not match, or FPGA version is improper. Procedure 1. Launch WebLCT. 2. Check and match the Value Mode settings and Header Compression Mode settings of alarmed MODEM and its opposed MODEM: ◆ WebLCT Menu Path: Provisioning ➜ MODEM Function Setting ➜ MODEM Port Setting 3. Retrieve the Current Status, and check if the Compression Setting Mismatch alarm is cleared. If the alarm is not cleared, contact NEC for the further maintenance support. This step ends the procedure.



4.14 Early Warning Indication Early Warning



Category Alarm



Description Radio signal is degraded (Early Warning threshold, where the threshold is 1E–9).



Severity MN



Troubleshooting: Early Warning If its Status indicates Alarm, the system detects degradation of radio signals. (Early Warning threshold detection.) Procedure 1. Launch the WebLCT. 2. Display the Current Metering to check RX Level.



16



from maintenance manual for Replacing Procedures for Radio Portion. This step ends th procedure.



4.15 Frame ID Indication Frame ID



Category Alarm



Description Frame ID (route differentiation ID) and its expected value do not match.



Severity MJ



Troubleshooting: Frame ID If its Status indicates Alarm, it shows that the Frame ID (route differentiation ID) and its expected value do not match. Procedure 1. Check the Frame ID values at both the local and its opposing NEs. 2. If the Frame ID values are correct, replace the iPASOLINK iX. This step ends the procedure.



4.16 High BER Indication High BER



Category Alarm



Description Radio signal is degraded (High BER threshold, where the threshold is 1E–3/1E–4/1E–5).



Severity MJ



Troubleshooting: High BER If its Status indicates Alarm, it shows that the radio signals are degraded (too high). Procedure 1. Launch the WebLCT. 2. Display the Current Metering to check RX Level. from maintenance manual for Replacing Procedures for Radio Portion. This step ends the procedure.



4.17 IF Cable Short Indication IF Cable Short



Category Alarm



Description IF Cable between MDU and ODU is short-circuited.



Severity MJ



Troubleshooting: If Alarm is indicated for the Status, it shows that the IF Cable between MDU and ODU is short-circuited. Procedure



17



1. Replace the IF Cable. 2. Retrieve the Current Status, and check if the IF Cable Short alarm is cleared. 3. Is the alarm cleared? YES: This step ends the procedure. NO: Replace the MDU, and go to 4.. 4. Retrieve the Current Status, and check if the IF Cable Short alarm is cleared. If the alarm is not cleared, contact NEC for the further maintenance support. This step ends the procedure.



4.18 L2SYNC Loss Indication L2SYNC Loss



Category Alarm



Description Frame Synchronization Loss has been detected from GFP Frames on MODEM port.



Severity MJ



Troubleshooting: L2SYNC Loss If its Status indicates Alarm, the frame synchronization loss is detected from the GFP Frame on MODEM port. Procedure 1. Launch the WebLCT. 2. Display the Current Metering to check RX Level.



This step ends the procedure.



4.19 LOF Indication LOF



Category Alarm



Description Loss of Frame at the Radio side.



Severity MJ



Troubleshooting: LOF This message indicates that the Loss of Frame is detected at the Radio side. Procedure 1. Launch the WebLCT, and display the Current Metering to check RX Level: If the value is appropriate, go to Step 4. from maintenance manual for Replacing Procedures for Radio Portion. 2. Retrieve the Current Status, and check if the LOF alarm is cleared. 3. Is the alarm cleared? YES: This step ends the procedure. NO: Go to Step 4. 4. Replace the iPASOLINK iX. 5. Retrieve the Current Status, and check if the LOF alarm is cleared. If the alarm is not cleared, contact NEC for the further maintenance support.



18



5 GbE interface Alarms & Troubleshooting Process 5.1 Eth LOS Indication ETH LOS



Category Alarm



Description Loss of Signal at the indicated Ethernet optical port.



Severity MJ



Troubleshooting: ETH LOS If its Status indicates Alarm, the LOS (Loss of Signal) is detected from the incoming signal on the indicated Ethernet facility. The problem of this condition pertains to the optical fiber or to the far-end NE. Procedure 1. Verify that the cable connections are all appropriate. 2. Check if any alarm(s) is/are issued to the far-end NE. If any exist(s), clear it/them. 3. Retrieve the Current Status, and check if the ETH LOS alarm is cleared. If the alarm is not cleared, contact NEC for the further maintenance support. This step ends the procedure.



5.2 Eth TF Indication ETH TF



Category Alarm



Description Transmission failure at the indicated Ethernet optical port.



Severity MJ



Troubleshooting: ETH TF If its Status indicates Alarm, a failure is detected in an installed SFP module. The problem of this condition is likely to be caused by a defective SFP module. Procedure 1. Replace the target SFP module. 2. Retrieve the Current Status, and check if the ETH TF alarm is cleared. If the alarm is not cleared, contact NEC for the further maintenance support. This step ends the procedure.



5.3 LAN Link Indication LAN Link



Category Alarm



Description Link of the LAN Port has been disconnected.



Severity MJ



Troubleshooting: LAN Link If its Status indicates Alarm, the Link-Down is detected from the indicated Ethernet port.



19



The problem of this condition pertains to the optical fiber cables or to the opposing site equipment. Procedure 1. Check the connections of optical fiber cables. place optical fiber cables if required. 2. Retrieve the Current Status, and check if the LAN LINK alarm is cleared. 3. Is the alarm cleared? YES: This step ends the procedure. NO: Go to Step 4. 4. Check if any alarm(s) occur(s) to the far-end NE, and clear it/them if any exist(s). 5. Retrieve the Current Status, and check if the LAN LINK alarm is cleared. If the alarm is not cleared, contact NEC for the further maintenance support. This step ends the procedure.



5.4 Link OAM Down Indication Link OAM Down



Category Alarm



Description Detects Link OAM Keepalive Protocol timeout.



Severity MJ



Troubleshooting: Link OAM Down If its Status indicates Alarm, Link OAM Keepalive Protocol Timeout is detected. The problem of this condition pertains to the opposing site equipment, for Ethernet Link, configuration of Link OAM, hardware error, etc . This is an alarm regarding IEEE802.3ah, Link OAM. Procedure 1. Check if any errors occur regarding to Link OAM Configuration, or to equipment at opposing site, and clear them. 2. Retrieve the Current Status, and check if the Link OAM Down alarm is cleared. 3. Is the alarm cleared? w YES: This step ends the procedure. w NO: Contact NEC. This step ends the procedure.



5.5 Remote Critical Event Indication Remote Critical Event



Category Alarm



Description Equipment failure at the opposing site is detected via Ethernet link.



Severity CR



Troubleshooting Remote Critical Event If its Status indicates Alarm, the hardware error is detected at the opposing site equipment, which is reported via Ethernet link. This is an alarm regarding IEEE802.3ah, Link OAM. Procedure 1. Replace the opposing site equipment. 2. Retrieve the Current Status, and check if the Remote Critical Event alarm is cleared. If the alarm is not cleared , contact NEC for the further maintenance support.



20



This step ends the procedure.



5.6 Remote Dying Gasp Indication Remote Dying Gasp



Category Alarm



Description Opposing site equipment is in reboot process.



Severity CR



Troubleshooting Remote Dying Gasp If its Status indicates Alarm, the opposing site equipment is in reboot process. This is an alarm regarding IEEE802.3ah, Link OAM. Procedure 1. Check if any failures occur to the opposing site equipment, and if any exist, clear them. 2. Retrieve the Current Status, and check if the Remote Dying Gasp alarm is cleared. If the alarm is not cleared, contact NEC for the further maintenance support. This step ends the procedure.



5.7 Remote Link Fault Indication Remote Link Fault



Category Alarm



Description Link failure has been detected at the opposing site.



Severity MJ



Troubleshooting Remote Link Fault If its Status indicates Alarm, Ethernet link failure at the opposing site is detected via incoming port. This is an alarm regarding IEEE802.3ah, Link OAM. Procedure 1. Check if any alarms occur to the equipment or cable connections at opposing site, and clear them. 2. Retrieve the Current Status, and check if the Remote Link Fault alarm is cleared. If the alarm is not cleared, contact NEC for the further maintenance support. This step ends the procedure.



5.8 SFP Removed Indication SFP Removed



Category Alarm



Description Indicated port is vacant (no SFP is mounted).



Severity MJ



Troubleshooting SFP Removed If its Status indicates Alarm, the system cannot detect the SFP Module on the indicated port. This condition is caused if the SFP is not properly plugged in, is not mounted, or is defective. Procedure 1. Check if the SFP on the indicated port is properly and securely plugged in.



21



w If the indicated port is vacant, mount an SFP Module onto the port. w If an SPF module is mounted on the indicated port, dismount and remount it to ensure the mounted condition. 2. Retrieve the Current Status, and check if the SFP Removed alarm is cleared. 3. Is the alarm cleared? w YES: This step ends the procedure. w NO: Replace the SFP module. 4. Retrieve the Current Status, and check if the SFP Removed alarm is cleared. If the alarm is not cleared, contact NEC for the further maintenance support. This step ends the procedure.



5.9 SFP Type Mismatch Indication SFP Type Mismatch



Category Alarm



Description An installed SFP and its registered information do not match.



Severity MJ



Troubleshooting SFP Type Mismatch If its Status indicates Alarm, the provided SFP Port type and the mounted SFP Module do not match. Procedure 1. Launch WebLCT, and display the Inventory window to check the port configuration. Correct the setting(s) if any inappropriate setting is found. 2. Retrieve the Current Status, and check if the SFP Type Mismatch alarm is cleared. 3. Is the SFP Type Mismatch alarm cleared? w YES: This step ends the procedure. w NO: Go to Step 4. 4. Check if the mounted SFP Module is the correct type for the port. 5. Is the type of SFP Module appropriate? w YES: Contact NEC. w NO: Replace SFP Module, and go to Step 6. 6. Retrieve the Current Status, and check if the SFP Type Mismatch alarm is cleared. If the alarm is not cleared, contact NEC for the further maintenance support. This step ends the procedure.



5.10 LAG Link Indication LAG LINK



Category Alarm



Description All the member ports of ETH Link Aggregation Group are failed.



Severity MJ



Troubleshooting LAG LINK If its Status indicates Alarm, it shows that all the member ports of Ethernet LAG (Link Aggregation Group) have failed. The problem of this condition pertains to the optical fiber cables or to the far-end NE. Procedure



22



1. Check if any alarm(s) occur(s) in the opposing site, and clear it/them if exist(s). 2. Retrieve the Current Status, and check if the LAG LINK alarm is cleared. If the alarm is not cleared, contact NEC for the further maintenance support. This step ends the procedure.



5.11 License Mismatch Indication License Mismatch



Category Alarm



Description Unlicensed setting(s) is/are registered.



Severity MJ



Troubleshooting License Mismatch If its Status indicates Alarm, registration(s) of unlicensed setting(s) is/are detected. This alarm may be issued if the system is downgraded by an inappropriate use of license, etc., leaving the settings registered under the previous (higher graded) license. To recover from this status, all the provisioning data should be removed. Procedure 1. Launch WebLCT to display the Shipment window. ◆ WebLCT Menu Path: Equipment Utility ➜ Shipment 2. Remove the provisioning data. Refer to 4.10.6 Restore Default Settings. 3. Is the alarm cleared? w YES: This step ends the procedure. w NO: Contact NEC. This step ends the procedure.



23



6.Flowchart for Troubleshooting ODU TX Section



24



7.Flowchart for Troubleshooting ODU RX Section



25



8.Flowchart for Troubleshooting MDU Section



26