Incorrect Client-Side Service Type Causes Failure of Interconnection With a Router

Incorrect client-side service type causes a failure of interconnection with a router.

Product

OptiX BWS 1600G, OSN 6800, OSN 8800

Fault Type

Equipment Interconnection

Client Equipment

Symptom

On a network, an ETMX board on the OptiX BWS 1600G is used to receive a 2.5 Gbit/s service from a router on the client side. Client-side channels run properly after an expansion is performed on the network.

When the ETMX board on the OptiX BWS 1600G receives the 2.5 Gbit/s service, interconnections with ports on the router are successful but exchanges of protocols fail. After an outloop is configured on the ETMX board at the local end by using the NMS to loopback the service to the router, port interconnections and protocol exchanges are successful. After an inloop is configured on the WDM-side optical port on the ETMX board at the remote end by using a fiber patch cord to loopback the service to the router, port interconnections are successful but protocol exchanges fail. This indicates that the fault lies on the WDM-side link or interconnected ports.

Cause Analysis

The analysis of the problem is as follows:

1. An SDH analyzer is used to test the WDM-side channel after the expansion is performed. No exception is found.
2. After the outloop on the ETMX board at the local end is performed, port interconnections and protocol exchanges are successful. This indicates that the router is running properly.
3. After the inloop on the ETMX board at the remote end through a fiber patch cord is performed, protocol exchanges fail. This indicates that protocol configuration is incorrect after signals are transmitted from the router to the ETMX board.

The preceding information shows that the problem is due to incorrect configurations of the ETMX board.

Procedure

1. Check the WDM-side configurations of the board. Service Type for services received from the client side of the ETMX board can beSDH, SONET, or ODU1.. By default, Service Type is set to SDH and J0 byte in the SDH interface overhead is set to Null.
2. Check the interconnected ports and no alarm is generated. This indicates that the no error is generated in the J0 byte.
3. Confirm that on the client side of the OptiX BWS 1600G, the service type interconnected with the router is OC48, which is different from the service type of the ETMX board. This is why the problem occurs.
4. Change Service Type of the ETMX board to SONET. Then, protocol exchanges are successful and services are normal.

Result

The problem is resolved.

Reference Information

None.

MORE BLOG:

How to do when Abnormal Optical Power Reporting Caused by the Coupling Exception

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

Incorrect Configuration of the ZL80018 Chip on OptiX OSN 1800