Cause for the failure to create ODU1 cross-connections on TN52TOM boards on OSN 6800 (without cross-connect boards)

7

The TN52TOM board does not support distributed ODU1 cross-connections.

Other related questions:
ODU1 cross-connections failing to be created on the TN52TOM board of OSN 6800 where no cross-connection is configured
The TN52TOM board does not support distributed ODU1 cross-connections.

Precautions for using commands to delete board-level cross-connections and then create NE-level cross-connections on OSN 6800 devices
Question: After an engineer changes board-level optical cross-connections of a pass-through wavelength on an OSN 6800 NE (version: 5.51.04.13) to NE-level optical cross-connections using a command (direct change on the T2000 will cause a transient service interruption), services on the wavelength are interrupted. In addition, when the engineer attempts to delete the NE-level optical cross-connections on the T2000 (version: V200R007C01), the T2000 displays a message indicating that the NE-side optical cross-connections do not exist. Why? Analysis: 1. An error occurs during service creation using the command. 2. The system control board or dynamic optical-layer grooming board ROAM is faulty. Answer: 1. NE-level or board-level optical cross-connections can be created for other wavelengths on the T2000. This means that the failure of the system control board or ROAM board can be excluded. 2. In the output of the :cfg-get-e2eoxc:0,0; command for querying NE-level optical cross-connections, the ROAM optical cross-connection status of the wavelength is 0000 rather than active, adding, or deleting. 3. NE-level optical cross-connections can be created for the wavelength using a command, and the NE-level optical cross-connections on the wavelength can also be deleted from the T2000. 4. The sequence of the operations performed by the engineer is as follows: Delete the board-level optical cross-connections on the wavelength. --> Create NE-level optical cross-connections for the wavelength. --> Query the NE- and board-level optical cross-connections on the wavelength. (All optical cross-connections on the wavelength can be queried). --> Delete the board-level optical cross-connections on the wavelength and check optical cross-connection status. 5. After board-level optical cross-connections are deleted using commands, the optical cross-connection status is always deleting if it is not verified, but services are not interrupted. After the engineer creates board-level optical cross-connections, the status of board-level optical cross-connections changes to active. In this case, after the verification command is issued, the wavelength cannot be displayed if the engineer queries board-level optical cross-connections, but can be displayed if the engineer queries NE-level optical cross-connections. 6. When the engineer queries the board- and NE-level optical cross-connections, the wavelength can be displayed. As a result, the engineer mistakenly determines that the optical cross-connections are not deleted and therefore deletes the optical cross-connections again. Consequently, the optical cross-connections are incomplete on the NE side. Suggestion and conclusion: If board-level optical cross-connections are deleted using commands, the board-level optical cross-connections cannot be displayed during the optical cross-connection query upon creation command issuing.

Whether the TN52TDX board supports ODU1 cross-connections
The TN52TDX board supports only ODU2 cross-connections.

Precautions for OSN 6800 to use command lines to delete board optical cross-connections or create single-site optical cross-connections
(1) The single-site or board optical cross-connections of other wavelengths are successfully created on the NMS. Therefore, the system control board fault or ROAM fault of the optical-layer scheduling board is ruled out. (2) When the cfg-get-e2eoxc:0,0 command is used to query the single-site optical cross-connections, the optical cross-connection of the wavelength on the ROAM is 0000, which is abnormal. The state should be one of active, adding, and deleting. (3) When a command line is used to create the single-site optical cross-connection of the wavelength, the optical cross-connection is successfully created. In addition, the single-site optical cross-connection of the wavelength can also be successfully deleted from the NMS. (4) Check the operation records of the onsite engineer and find that the procedure is as follows: Check the board optical cross-connection of the wavelength à Create the single-site optical cross-connection of the wavelength à Query the board and single-site optical cross-connections of the wavelength. The wavelength is present on both the board optical cross-connection and single-site optical cross-connection. Then, you can delete the board optical cross-connection and verify it. (5) If the board optical cross-connection is deleted using a command line but no verification is performed, services will not be interrupted when the board optical cross-connection is in the deleting state. If a single-site optical cross-connection is created at that time, the board optical cross-connection will become the active state. After the verification command is successfully delivered, the wavelength cannot be found in the board optical cross-connection and it can be queried only in the single-site optical cross-connection. (6) Because the onsite engineer found the wavelength both in the board optical cross-connection and single-site optical cross-connection, the engineer falsely determined that the optical cross-connection was not successfully deleted and then deleted it again. As a result, optical cross-connections on the NE software side are incomplete.

Whether ODU0 services can be configured on the TN52TOG boards on OSN 6800 devices
OSN 6800 devices do not support ODU0 cross-connections.

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