Method to implement the OD system


The OD is a function implemented through the collaboration of products and the NMS. OD principles are provided in the product documentation. To support the OD, the NE version must be later than V100R007C00 and the NMS version must be later than V100R006C02.

Other related questions:
Detection of the OSNR of a 40G or 100G system using the traditional OSNR detection method
The optical spectrum of 40G or 100G signals is wider than that of 10G signals. Therefore, the signal spectra of adjacent channels overlap each other. The channel noise includes not only the ASE noise but also the power crosstalk of some signals. Therefore, the OSNR tested using the traditional OSA method is less than the actual OSNR. The traditional OSA method is implemented based on the interpolation of inter-channel noise that is equivalent to in-band noise. The traditional OSNR detection methods, including the scanning method and the integral method, have the following disadvantages: Scanning method: applicable only to a system with a 100G channel spacing and without traversing an OEQ node. The detection results have a low precision. Integral method: When there are a few wavelengths, turning on or off the lasers will cause noise power fluctuation and therefore affect the detection accuracy. In addition, the noise power cannot be measured by turning on or off the laser when there is only one wavelength.

NE versions required by the OD system
To support the OD, the OptiX OSN 6800/8800 version must be later than V100R007C00 and the NMS version must be later than V100R006C02.

Common issues about the OD system
Question: For the first version of OD on NG WDM V100R007C00 (matching U2000 V100R006C02): 1. What are the differences in OPM/MCA performance reporting? 2. Why must the fiber connections be correct before the OD works? 3. How long does it take before the OSNR can be queried after the OD feature is configured for the first time or the NE is reset? 4. The OD function is forcibly enabled for a network that does not support the OD function, causing the MCA/OPM8 function to be abnormal and the original function unavailable. How to solve this problem? 5. Where can the length and type of optical fibers be configured? From the interface for creating logical fiber connections on the U2000 or other navigation paths? Analysis: Answer: 1. When the OSNR detection fails, the OSNR in the OPM is an invalid value. The MCA OSNR performance value is compatible with the existing MCA board and is reported as ?600. 2. When the OD feature is started for the first time, or the network changes (such as dimension adjustment or dimension expansion), the OD connection relationship needs to be synchronized to the equipment through the NMS interface (OTU-MUX/DMUX does not need to be changed.) 3. 10 minutes. 4. You can run a Navigator command to resolve the problem. :emca-check-section-id:0, 0&0 5. The navigation path is on the Board Port-Advanced Attributes tab page. Notes: 1. The line-side fiber type and length configured on the FIU, DAS1, or RAU board at the receive end must be consistent with those of actual fibers. 2. If there is no RAU board at the receive end, configure the fiber type and length information on the FIU or DAS1 board. If there is RAU board at the receive end, configure the information on this RAU board.

Preparations for the OD V2 test on the live network
Question: How do I prepare the OD V2 tests on an NG WDM network? What are the key points? Answer: You can obtain presentation slides about OD V2 from However, some issues are prone to be ignored during live-network tests. As a result, the preparations are insufficient and the test cannot be performed. Based on the actual test experience, pay attention to the following points: 1. Check whether the live-network equipment configurations meet OD V2 enabling requirements, including the following aspects: a. Hardware requirements For example, hardware version requirements of the OA, MCA, and OPM8 boards. b. Networking requirements Exercise caution because OD V2 has many restrictions on networking. The OD V2 may fail to be enabled on the live network if networking configurations do not meet requirements. The following describes some of the restrictions: (1) OA boards must be configured between the FIU boards at the receive-end site of an OMS and the ROADM or multiplexer/demultiplexer boards. (2) Optical-layer boards in all degrees must be configured on the same NE. c. NMS configuration requirements ASE calibration is required for the RAU board in one of the steps. However, during ASE calibration, the Raman laser needs to be enabled and disabled. You are advised to contact Huawei R&D engineers to evaluate whether it is necessary to perform ASE calibration on the live network. d. Collect network-wide scripts and send them to Huawei HQ for evaluating whether networking conditions and hardware configurations on the live network meet OD V2 enabling requirements. 2. Software version requirements, including a. Equipment software: NG DWDM V100R008C00 or later. A live-network version upgrade may be required. b. U2000: V100R009C00 or later. A U2000 version upgrade may be required. c. MDS 6630: V100R007C20. The tool needs to be integrated into the U2000. Therefore, you must apply for a valid license. 3. After all preparations are ready, start OD V2 configurations with reference to OD V2 feature slides.

Methods used to implement virtual load balancing
Currently, virtual and physical SVN load balancing can be implemented. vLB is used to balance the load of multiple WIs. Physical LB balances the load of WIs to prevent a large number of users from accessing the same WI.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top