Cross-connection level of the services on the TOM board

6

ODUk cross-connections are configured on the TOM board. For details about the service grooming mode in each scenario, see the multimedia in "Logical Ports" in the product documentation.

Other related questions:
Method used to query the service cross-connection configurations of the TOM board
1. Select the NE in the NE Explorer, and choose Configuration > WDM Service Management from the navigation tree. 2. On the WDM Cross-Connection Configuration tab, click Query to view the cross-connection configuration of the corresponding board.

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.

Whether two GE services on two TOM boards can be cross-connected to the same ODU1 timeslot on an ND2 board
The cross-connections between the TOM and ND2 boards are ODU1 cross-connections, which occupy the entire ODU1 timeslot. Therefore, two GE services on two TOM boards cannot be cross-connected to the same ODU1 timeslot of an ND2 board.

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.

Service rate limit for GE services on the TOM board
The TOM board does not support port bandwidth limit. All OTN boards do not support this function. The function is supported only by the service boards that support the L2 processing capability, such as TEM28 and LEM24.

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