Thursday, June 16, 2016

Determine the Factors That Affect the OSNR By Using the ANT30 Tester

This case describes how to determine the factors that affect the OSNR by using the ANT30 tester.

Product

OptiX BWS 1600G
OptiX Metro 6100
OptiX Metro 6040
OptiX OSN 3800

Fault Type

Bit Error
Dispersion Abnormity
OSNR Abnormity
Tester

Symptom

During a test of one OptiX BWS 1600G project, the ANT30 tester is used to test the optical power and OSNR of each channel. It is found that the frequency spacing based on which the OSNR is tested for different sites is different, and it keeps changing (it may be 112.5 GHz, 50 GHz, 75 GHz or other values at different time). As a result, the OSNR value is affected. But in fact the standard frequency spacing is 50 GHz in this network. Therefore, in this case, the settings of the ANT30 tester are adjusted so that the frequency spacing is always 50 GHz. After the settings are adjusted, however, the OSNR performance is still unstable, and the frequency spacing still fails to meet the specification requirement.

Cause Analysis

The reason why the OSNR performance is not improved after the settings of the ANT30 tester are adjusted is that the ANT30 tester uses the default values of a single station and the default values keep unchanged even if an attempt to change them is made.
The procedure for handling the problem is as follows:

Procedure

  1. Adjust the settings of the ANT30 tester to ensure that the frequency spacing is 50 GHz. Then, select Configuration from the menu in the screen of the ANT30 tester, and then double-click Average Value and increase the value by four points, so that the optical power and OSNR of each channel are optimal.
  2. Select Table to query the results.
  3. Click  and wait until ANT30 test finishes scanning the wavelengths to obtain the correct OSNR value. Do not click  because this button is used to query the default values of a station and you will lost all existing settings of the ANT30 tester.
  4. The number of the scanned wavelengths is displayed on the left of the ANT30 tester screen. The number depends on the Average Value set through the Configuration menu. For example, if the Average Value is 5, the scanning stops after five wavelengths are scanned.

Result

You can check the results after the operation is finished as the requests.

Reference Information

None.

Wednesday, June 15, 2016

Interconnection Between Optical Interface Boards of Devices Fails

The optical interface board (namely, N1SF64) of the OptiX OSN 7500 and the optical interface board (namely, A1SF64) of the OptiX 10G (Metro 5000) support different protocols. In this case, when the two boards are interconnected with each other, the service fails. After two optical interface boards that support the same protocol are interconnected, the service runs normally.

Product

Fault Type

  • Device interconnection failure
  • BEFFEC_EXC
  • PLL_FAIL

Symptom

The optical interface board (namely, N1SF64) of the OptiX OSN 7500 and the optical interface board (namely, A1SF64) of the OptiX 10G (Metro 5000) support different protocols, which causes the service failure after the two boards are interconnected.

Cause Analysis

The N1SF64 board supports the ITU-T G.709 protocol, which cannot be interconnected with the A1SF64 board that supports the ITU-T G.975 protocol.

Procedure

  1. Use an optical fiber to connect two N1SF64 boards.
  2. Verify the boards on the NMS. It is found that the service is normal and no alarm is generated.
  3. Use an optical fiber to connect the N1SF64 board to the A1SF64 board.
  4. Verify the boards on the NMS. It is found that the boards cannot work in the normal state. Query the NE alarms. The results are as follows:
    • BEFFEC_EXC
    • PLL_FAIL
  5. Replace the board to ensure that the two optical interface boards provide the same rate and support the same protocol. Then, the service is normal, and no alarm is generated.

Reference Information

Before the network commissioning, you must determine whether the protocol adopted by the board supports the interconnection. If the protocols of the two boards to be interconnected do not support the interconnection, the service fails when the interconnection is performed forcibly.


How to do when Failing to Connect the 155 Mbit/s Optical Port on the Router of Company C

Tuesday, June 14, 2016

The LWX Board of the OptiX Metro 6100 Reports a TP_LOC Alarm

The LWX board of the OptiX Metro 6100 reports a TP_LOC alarm because no service is input to the board.

Product

OptiX Metro 6040

Fault Type

Optical Transponder Unit
TP_LOC

Symptom

During the deployment, the LWX board of the OptiX Metro 6100 reports a TP_LOC alarm.

Cause Analysis

The TP_LOC alarm indicates a loss of the transmitter PLL clock.
No service is input to the client side of the LWX board at the local station and the Automatic Laser Shutdown of the board is Disabled. This indicates that the laser of the LWX board is forced to emit light and thus there is no signal code stream in the WDM-side wavelengths. The LWX board at the opposite station cannot lock the clock and thus reports the TP_LOC alarm.

Procedure

  1. Provide services to the client sides of the LWX boards at both the local and opposite stations. In this manner, the TP_LOC alarm is cleared.

Communication Between Equipment and NMS Fails After Standby CXL Board Is Switched to Main Mode

After the standby CXL board is switched to the main mode, the communication between the equipment and the NMS fails. Check the relevant information. It is found that the MAC address of the port is changed after the switching, and as a result the network is blocked. In this case, ensure that the router supports different MAC addresses of the same port.

Product

Fault Type

  • Protection Switching Failure
  • DCN fault

Symptom

The OptiX OSN 2500 forms an STM-4 ring, where there is one gateway NE. During the acceptance test, the standby CXL4 board is switched to the main mode, and then the communication between the NEs and the NMS fails but the corresponding alarms are not reported.

Cause Analysis

The software of the standby CXL board may be different from the software of the main CXL board or the DCN may be faulty.

Procedure

  1. Access the NE at the local end and the switching of the CXL4 boards is successful. It indicates that the software of the main CXL4 board and the software of the standby CXL4 board are the same.
  2. Contact the DCN service personnel. It is learnt that the router port in the DCN is already blocked. Although the OptiX OSN 2500 has only one ETH port, the MAC address of this port is still changed when the CXL boards are switched. As a result, the router port is blocked.
  3. The DCN service personnel enable the two MAC addresses of the same router port. Then, the communication is restored to normal.

Monday, June 13, 2016

An R_OOF Alarm Occurs When the LWC Interconnects with Third-Party Equipment

When the LWC board receives the Ethernet POS service, an R_OOF alarm is generated intermittently on the LWC board is interconnected with the third-party equipment because the clock setting of the client data equipment is improper.

Product

OptiX BWS 1600G

Fault Type

Equipment Interconnection
Service Interruption
Bit Error
Client Equipment
R_OOF

Symptom

On a WDM network(such as OSN6800, OSN8800), the SSEM4LWC01 boards are used at the ends and the TRC board is used as the regeneration board to establish the 2.5G IP circuit. In addition, the data equipment is used at both of the client sides. After services are added and run for a period, an R_OOF alarm is generated intermittently on both the client side and WDM side of the LWC, and the data equipment also reports bit errors. As a result, services are interrupted.

Cause Analysis

The clock of the data equipment is set to trace a line clock by default. The data equipment at both ends adopts the default settings, so the clocks are traced mutually. In this case, change the clock of the data equipment at one end to trace an internal clock to solve the problem.

Procedure

  1. Apply a self-loop at the WDM-side port on the data equipment, and it is found that the system is normal. Release the self-loop and restore the original fiber connection, the R_OOF alarm persists.
  2. On the WDM side of the LWC board, apply a self-loop between the IN and OUT ports by using a fiber jumper (an optical attenuator must be installed between the two ports). The data equipment runs normally and the LWC no longer reports the R_OOF alarm intermittently. Release the self-loop and restore the original fiber connection, the R_OOF alarm is reported intermittently again. This indicates that the board is normal.
  3. Check the data configuration of the data equipment. It is found that the clocks of the data equipment at both ends trace each other.

Result

After the clock setting is changed, the services are restored.

Reference Information

In the case of the traditional WDM equipment, the client equipment is generally required to provide clock data and the wavelength conversion board is required only to transmit the clock data transparently.


How to do when the Occasional Failure to Go Online for TN11HSC1 Boards

Analysis and Handling of the ALM_DATA_RLOS and ALM_DATA_TLOS Alarms Reported by the LBE

The LBE board reported the ALM_DATA_RLOS and ALM_DATA_TLOS alarms due to a fault of the module on the client side.

Product

Fault Type
Equipment Interconnection
Service Interruption
Ethernet Service
ALM_DATA_RLOS
ALM_DATA_TLOS

Symptom

The LBE boards at two adjacent OTM sites on an OptiX BWS 1600G network are interconnected to provide the accounting service.
After an optical cable cutover is performed, no alarm is reported on the T2000, but the accounting service is interrupted.

Cause Analysis

If alarm filtering is set on the T2000, no alarm may be reported to the T2000.
During the analysis, it is found that the LBE has reported the ALM_DATA_RLOS and ALM_DATA_TLOS alarms.
The ALM_DATA_RLOS alarm indicates that no data is received by the Ethernet port. That is, the GE port does not receive any data from the data equipment. The ALM_DATA_TLOS alarm indicates that no data is transmitted from the Ethernet port. That is, the WDM side of the local board does not receive any data.
The main causes are as follows:
  • The transmitter on the client-side data equipment is abnormal.
  • The board is faulty.
  • Interconnection between the data equipment and the WDM equipment is abnormal. For example, the types of the client-side optical modules are inconsistent or the client-side optical modules are faulty.

Procedure

  1. Query the performance data of the LBF board. It is found that the receiver power on the client side and the performance values of the board are normal. In addition, the received power of Layer-3 switch on the client side of the local station is normal.
  2. Configure an outloop on client side of the local LBE board. As a result, the LBE reports both the ALM_DATA_RLOS and ALM_DATA_TLOS alarms. The fault persists.
  3. Configure an inloop on client side of the remote LBE board. As a result, the local LBE reports both the ALM_DATA_RLOS and ALM_DATA_TLOS alarms.
  4. Configure an inloop on client side of the local LBE board. As a result, the ALM_DATA_TLOS alarm on the remote LBE board clears. This indicates that the switch on the client side of the local station is faulty.
  5. After the switch equipment is restarted by the customer, the fault persists.
  6. Replace the optical modules on the Layer-3 switch on the client side of the local LBE board. The alarms on the LBE board clear.

Result

The fault is eliminated, and the services are restored.

Saturday, June 11, 2016

How to Select Test Meters on Site When Testing OTU Boards of the Data Type



Fault Type

Optical Transponder Board
Tester

Symptom

The OTU boards of the data type used in a project are the SSC6LOG01M01, SSC6LDGD01M12, SSC8LBE01M01, and SSC6FCETD04. The meters available on site are as follows:
  • SmartBits Main Chassis model SMB600B
  • SmartBits Main Chassis model SMB600 (with option SWF1201A, SWF1212A)
  • SmartBits Main Chassis model SMB600 (with option SWF1201A)
  • SmartMetrics 10 Gbps Ethernet XFP, 1 Port MSA Module model XFP3730A
  • 10/100/1000 Mbps and Gigabit Ethernet Fiber, 2-port, SmartMetrics XD Module model LAN3320A
  • 10/100/1000 Mbps and Gigabit Ethernet Fiber, 2-port, TeraMetrics XD Module model LAN3321A
  • 10/100/1000 Mbps and Gigabit Ethernet Fiber, 4-port, SmartMetrics XD Module model LAN3324A
  • SmartMetrics Gigabit Ethernet Module model LAN3201B
  • SMART Optical Level Attenuator, 1260 nm to 1650 nm model OLA-55 (2280/01)
On site, which one or two test meters should be selected to test all the OTU boards of the data type?

Cause Analysis

According to the types of OTU boards used on site, services that need to be configured and activated in the project include GE, 10GE, and FC100/200. The meter SmartBits Main Chassis model SMB600B can be used to test these three types of services. The test card varies with the service type.
All the services in the project can be tested with the meter SmartBits Main Chassis model SMB600B.
  • In the case of the GE service, use the test card LAN3320A.
    • 1x SmartBits Main Chassis model SMB600B
    • 1x 10/100/1000Mbps and Gigabit Ethernet Fiber, 2-port, SmartMetrics XD Module model LAN3320A
  • In the case of the 10GE service, use the test card XFP-3730A.
    • 1x SmartBits Main Chassis model SMB600B
    • 1x SmartMetrics 10 Gbps Ethernet XFP, 1 Port MSA Module model XFP3730A
  • In the case of the FC100/200 service, use the test card FBC3602.
    • 1x SmartBits Main Chassis model SMB600B
    • 1x FBC3602

Procedure

  1. None.