Service interruption on NodeB caused by incorrect configuration of tunnel route constraint

wissal · Created Dec 24, 2019 16:42:31

Hello,

Please find below the solution for your issue

Check the status of the 10GE link, and no anomaly occurs. In addition, no ETH_RX_FLOW_OVER alarm exists on the network, and thus this problem is not caused by a broadcast storm.
Check the route information of the service. It is detected that the service once routed on to the STM-1 POS link with a 155M bandwidth.
When the fault recurs, check the actual route of the MPLS tunnel between NE01 and NE06. It is detected that a large number of voice services are transmitted on the STM-1 POS link between NE01 and NE03. The abrupt increase of services results in packet congestion, which affects existing services.
Check the configuration of the 10GE tunnel between NE01 and NE06. It is detected that the configuration sequence of Route Constraint Port IP Address for positive tunnel is the same as the configuration sequence of Route Constraint Port IP Address for reverse tunnel, and the parameters of Rerouting Mode of both the positive tunnel and the reverse tunnel are all set to Include Loose.

As a result, the services after re-optimization are transmitted along an incorrect route that involving the POS port, and thus the re-optimization fails.
Change the configuration sequence of Route Constraint Port IP Address for the reverse tunnel to a sequence which is in reverse of the configuration sequence of Route Constraint Port IP Address for the positive tunnel, and make sure that no service is transmitted on the STM-1 POS link.

In this case, all services are restored.

Notice

When a dynamic MPLS tunnel is created, make sure that the route constraint condition is correctly set, and select a proper Rerouting Mode.

I Hope the solution is helpful, thanks

wissal · Created Dec 24, 2019 16:42:31

Hello,

Please find below the solution for your issue

Check the status of the 10GE link, and no anomaly occurs. In addition, no ETH_RX_FLOW_OVER alarm exists on the network, and thus this problem is not caused by a broadcast storm.
Check the route information of the service. It is detected that the service once routed on to the STM-1 POS link with a 155M bandwidth.
When the fault recurs, check the actual route of the MPLS tunnel between NE01 and NE06. It is detected that a large number of voice services are transmitted on the STM-1 POS link between NE01 and NE03. The abrupt increase of services results in packet congestion, which affects existing services.
Check the configuration of the 10GE tunnel between NE01 and NE06. It is detected that the configuration sequence of Route Constraint Port IP Address for positive tunnel is the same as the configuration sequence of Route Constraint Port IP Address for reverse tunnel, and the parameters of Rerouting Mode of both the positive tunnel and the reverse tunnel are all set to Include Loose.

As a result, the services after re-optimization are transmitted along an incorrect route that involving the POS port, and thus the re-optimization fails.
Change the configuration sequence of Route Constraint Port IP Address for the reverse tunnel to a sequence which is in reverse of the configuration sequence of Route Constraint Port IP Address for the positive tunnel, and make sure that no service is transmitted on the STM-1 POS link.

In this case, all services are restored.

Notice

When a dynamic MPLS tunnel is created, make sure that the route constraint condition is correctly set, and select a proper Rerouting Mode.

I Hope the solution is helpful, thanks