Monthly Archives: May 2015

XFP not supporting FC800 services OSN8800 TN55TQX

TN55TQX card in general supports various service types including STM-64, OC192, 10GE, FC800, FC1200 or OTU2. However there are dedicated XFP modules (BOMs) for different services. Unfortunately U2000 does not alert or notify when user creates service with wrong XFP type. Moreover many XFPs will actually work although wrong service type is created. For example customer ordered several TQX cards equipped with: 10GE/STM64 dedicated XFPs (BOM 34060313), and FC800 dedicated XFPs (BOM 34060658). However XFPs arrived distributed randomly and customer didn’t pay attention to verify XFP type while creating services. Unexpectedly most services ware working although wrong XFP BOMs were used. Eventually one of the FC800 services failed and after investigation XFPs mismatch across the network has been discovered on OSN 8800.

Software version OSN 8800 V100R007C02SPC200

iManager U2000 V100R008C00SPC300

The following XFP types have been delivered to the customer:

BOM 34060313 (dedicated for STM64/10GE):

-          FTLX1412M3BCL(also working when FC800 configured)

-          FTLX1413M3BCL-HW (also working when FC800 configured)

-          SXP3104NV-H1

-          TRF5013FN-GA420

-          TRF5015FN-GA420

BOM 34060658 (dedicated for FC800 services):

-          PT745F-81-1D (also working when 10GE or STM64 configured)

The problem with XFP mismatch has been discovered when FC800 service was created with XFP SXP3104NV-H1 type.  U2000 didn’t rapport any problems although the far end equipment reported link down. The issue has been resolved by relocating XFPs across the network to get dedicated XFPs for all relevant services.Wrong XFP types were used when crating FC800 serviceXFP modules relocation

Although some XFP types can work even when incorrect service type is created, this configuration is not recommended or supported by Huawei transport network. There is no guarantee this configuration is stable, and under certain conditions errors might occur.

TwitterLinkedInGoogle+FacebookPinterestTumblrStumbleUponRedditShare

10GE LAN link flapping on customer router due to SNCP switch

【Problem Summary】Huawei DWDM 10GE LAN link from Hyderabad to Banaglore flapping on customer router. 
【Problem Details】Below is the diagram shown end to end connectivity details :-

Huawei DWDM topology

The end points which is connected to the router is on the LSX cards. You can refer to the PDF for end to end connectvity details.When there is fiber cut in any ring, there is ODUk SNCP ring switch. Below alarm flow to the router which causes router to flap :-

SNCP

Although the ring is within 50ms, this will still cause the router to flap. So customer asked us how to avoid this flapping.
Below two causes has been obeserved in this router flapping :-

1. Whenever there is ODUk SNCP ring switch in any ring, it will cause the SNCP switch in the other rings due to SNCP cascade effects so to avoid that we should set hold off time in the ODUk SNCP protection group in each SNCP protection group. but in this case we can`t ensure the switching within 50ms. Total switching time will be :-

                          Hold-off Time in ODUk SNCP Protection Group +<= 50ms(Means whatever will be th exact switching time). 

This will also cause the router flapping. This point only help to avoid the SNCP cascade effects i.e before switching will happen in the other rings it will wait for 100ms.


2. Principles of Router 

(1)Router includes physical layer and protocol layer

(2)Condition which can trigger physical layer down: R_LOS/R_LOF/AIS/RDI;

(3)Condition which can trigger protocol layer down:

Whenever physical layer is down, protocol layer will be down;

When physical layer is up but the hello protocol packets between Routers are lost continuously;

(4)Hold off time: the waiting time when physical layer detects the condition which can trigger itself down ,  suggest setting hold off time as 200ms;

(5)Hold up time: the waiting time when physical layer cannot detect the condition which triggered itself down ,



【Resolution Summary】 Set the hold off time in Router and Hold off time in each ODUk SNCP protection group.
【Resolution Details】

We have to set the hold off time in each SNCP protection group of 100ms, so this will make the actual switching time more than 100ms.Actually switching time will be:-

                                Hold-off Time in ODUk SNCP Protection Group +<= 50ms(Means whatever will be th exact switching time). 

And need to set the hold off time in router should be greater than the above time. To avoid this flapping.

Required to set the hold off time in ODUk SNCP protection group and in router as well to avoid flapping on OSN 1800.