Tuesday, June 7, 2016

The LBE, LDG and LQG Boards Report the LINK_ERR or LINK_STATUS Alarm

The LBE, LDG and LQG boards report the LINK_ERR or LINK_STATUS alarm.

Product

OptiX Metro 6040

Fault Type

Optical Transponder Board
LINK_ERR
LINK_STATUS
ALM_DATA_RLOS
ALM_DATA_TLOS

Symptom

The LBE, LDG or LQG board reports the LINK_ERR or LINK_STATUS alarm.

Cause Analysis

The causes for the alarms must be ascertained before the correct solutions can be found.

Procedure

  1. The trigger conditions for the LBE or LBES board to generate the LINK_ERR alarm are as follows:
    1. The receive sequence (at the physical coding sublayer (PCS)) at the peer or local end is incorrect.
    2. The bit error ratio is extremely high.
    3. The synchronization frame is lost.
    4. Bit synchronization is lost.
    5. Signals are lost.
  2. The trigger conditions for the LOG board to generate the LINK_ERR alarm are as follows:
    1. Bit synchronization is lost.
    2. When auto-negotiation is enabled, the LINK_ERR alarm is reported if the auto-negotiation fails.
    3. When LPT is enabled, the board reports the LINK_ERR alarm if the service network is faulty or the peer board reports LINK_ERR.
  3. The trigger conditions for the LDG board to generate the LINK_STATUS alarm are as follows:
    1. Bit synchronization is lost.
    2. When auto-negotiation is enabled, the LINK_STATUS alarm is reported if the auto-negotiation fails.
    3. When LPT is enabled, the board reports the LINK_STATUS alarm if the service network is faulty or the peer board reports LINK_STATUS. When the optical interface on the client side is inlooped, neither LINK_ERR nor LINK_STATUS is reported.
  4. When no light is received on the client side, LINK_ERR or LINK_STATUS is suppressed because the R_LOS alarm is reported. If the client-side link is normal but no packet is sent or received, only ALM_DATA_RLOS or ALM_DATA_TLOS is reported.

Monday, June 6, 2016

The Protection Switching Times Out Severely

The protection switching time is out severely in the event of wavelength protection between the SCS boards of the OptiX Metro 6100 because of the wrong test method.

Fault Type

Protection

Symptom

In the test of inter-board wavelength protection of the SCS board, the test result is severely beyond the standard. The minimum switching time is over 1000 ms and the maximum switching time even reaches up to 3000 ms. The standard switching time should be less than 50 ms. As a result, the test result is far from the required switching time.
The test meter used on site is the ANT-20SE.
The test procedure is as follows:
  1. Perform a hard loopback between the IN and OUT optical interfaces of the LQS board by using a fiber, and connect the TI1 and RO1 optical interfaces of the SCS board to the test instrument.
  2. Configure inter-board wavelength protection by using the T2000.
  3. After completing the configuration, test the inter-board wavelength protection by using the tester. No alarm is found and the optical path is normal.
  4. Disconnect the fibers on the client-side optical receiving interfaces of the active and standby LQS boards. The protection switching can be completed but times out severely.

Cause Analysis

The trigger condition of the wavelength protection switching is an anomaly of service receiving on the WDM side. Hence, the correct test moth is to remove the fiber on the WDM side of the LQS board. During the test, however, the client-side receive fiber of the LQS board is removed. Hence, the switching process is as follows:
  • Remove the client-side receiving fiber of the LQS board.
  • The LQS board shuts down the WDM-side laser according to the ALS function in about 2 seconds.
  • The system detects that there is no optical input on the WDM-side optical interface of the LQS board. Hence, the board reports the SF event.
  • The protection group switches over to the protection path.
Hence, the actual test time includes the switching time and the time taken for the ALS to close the laser. As a result, the switching times out severely.

Procedure

  1. The test method is changed to perform by disconnecting the WDM-side fiber, the switching time is normal.
  2. The test is past after the test method is changed to perform by disconnecting the WDM-side fiber.

The Optical Amplifier Reports the IN_PWR_HIGH Alarm Because of Optical Power Reflection

The optical amplifier reports the IN_PWR_HIGH alarm because of optical power reflection.

Fault Type

Optical Amplifier Unit
IN_PWR_HIGH

Symptom

A metropolitan area ring network composed of the OptiX Metro 6040 bears single wavelengths. After the local commissioning of all sites, if you shut down all the optical amplifiers such as the OPU and OBU, the IN_PWR_HIGH alarm is reported. In this case, if you power on some of the amplifiers, the optical power of the network is restored.

Cause Analysis

This problem is caused by optical refection of the amplifiers.
The sites of the network are OADM sites. That is, services pass through between the MI and MO optical interfaces on the MR2 boards of all the sites. If the pass-through wavelengths of the network are not blocked, optical power reflection of the amplifiers occur.

Procedure

  1. To solve this problem, the pass-through wavelengths between the MI and MO optical interfaces on the MR2 boards of the network must be blocked. If a wavelength bearing no services passes through the MR2 boards of all the sites, this wavelength must also be blocked. You can also add a electrically variable optical attenuator to the link between the MI and MO optical interfaces of each site, and set the attenuation of each electrically variable optical attenuator to the maximum value until more pass-through wavelengths are loaded.
  2. This method is used to avoid repeated amplification of noise.

Packet Loss Occurs in Ethernet Service Testing of the L4G Board

The packet loss occurs in Ethernet service testing of the L4G board due to the different equipment and meters.

Fault Type

Ethernet service

Symptom

In a test of EPL and VLAN networking by using the L4G board, the Smartbits meter is used to transmit complete bandwidth signals that are looped back on the client side at the remote end. During the test, a packet loss ratio of 0.001% is found. If the EPL networking is set up without the VLAN networking, no packets are lost on site.

Cause Analysis

In the EPL networking, exact synchronization of Ethernet networking can hardly be realized and a frequency deviation tolerance of +/-100 ppm is permitted. Hence, different equipment and meters trace different clock sources. If the inner oscillation frequency of the transmit unit is quicker than that of the receive unit, packet loss occurs.

Procedure

  1. None.

Friday, June 3, 2016

Packet Loss Occurs in Ethernet Service Testing of the L4G Board

The packet loss occurs in Ethernet service testing of the L4G board due to the different equipment and meters.

Fault Type

Ethernet service

Symptom

In a test of EPL and VLAN networking by using the L4G board, the Smartbits meter is used to transmit complete bandwidth signals that are looped back on the client side at the remote end. During the test, a packet loss ratio of 0.001% is found. If the EPL networking is set up without the VLAN networking, no packets are lost on site.

Cause Analysis

In the EPL networking, exact synchronization of Ethernet networking can hardly be realized and a frequency deviation tolerance of +/-100 ppm is permitted. Hence, different equipment and meters trace different clock sources. If the inner oscillation frequency of the transmit unit is quicker than that of the receive unit, packet loss occurs.

Procedure

  1. None.

The SC2 Board Reports the CRC4_CROSSTR Alarm

The SC2 board reports the CRC4_CROSSTR alarm due to the board faulty.

Fault Category

Optical Supervisory Channel Unit
CRC4_CROSSTR

Symptom

The SC2 board in the OptiX Metro 6100 reports the CRC4_CROSSTR alarm.

Cause Analysis

The main causes may be the abnormal received optical power and the fault in the fiber or optical connectors.

Procedure

  1. The received optical power of the SC2 board is normal (The receiver sensitivity of the SC2 board is -48V.), whereas the SC2 board reports the alarm.
  2. The fault persists even when the fibers and connectors at the RM1 interface of the SC2 board are cleaned.
  3. Replace the SC2 board, and the fault is cleared. This indicates that the RM1 interface of the SC2 board is faulty.

Thursday, June 2, 2016

The WXCP Protection Configured for the LOG Board Is Invalid

The WXCP protection configured for the LOG board is invalid due to the configured attributes of the board.

Product

OptiX Metro 6040

Fault Category

Protection

Symptom

The LOG board is configured with the correct WXCP protection.
During a protection switching test, services are interrupted because there is no protection channel to which the services can be switched; however, no alarms are reported to the T2000.
Check whether the protection configuration is correct.
If you delete the protection group and then configure a new one, the fault persists.

Cause Analysis

The WXCP protection configured for the LOG board is invalid due to the configured attributes of the board.

Procedure

  1. Check the LOG board of the protection group.
    1. In the NE Explorer, select the LOG board to be checked.
    2. Select Configuration > WDM Interface from the Function Tree.
    3. Click the Advanced Attributes tab.
    4. Check whether the Max Packet Length is 9800.
  2. In this case, set the value of this parameter to 1511.
  3. Because the value of the parameter cannot be changed, set the LOG board.
  4. After the LOG board is reset, the value of the parameter is displayed as 9800.
  5. Test whether the fault is cleared. If the fault is cleared, the WXCP protection becomes valid.