Unsuccessful FE service caused by wrong physical connection Publication Date: 2012-07-25 Views: 0 Downloads: 0 References: 0 Issue Description For Z customer, we are implementing a metropolitan MSTP network with OSN 3500 and Metro 1000V3 equipment. The...
More
Unsuccessful FE service caused by wrong physical connection Publication Date: 2012-07-25 Views: 0 Downloads: 0 References: 0 Issue Description For Z customer, we are implementing a metropolitan MSTP network with OSN 3500 and Metro 1000V3 equipment. The currently used U2000 version is V100R003C00SPC100, the OSN 3500 version is V200R011C00SPC200, and Metro 1000V3 version is V300R007C02SPC200. Alarm Information During deployment, when we configure new 2 FE service between sites A and site B in Network STU_AIS_VC12 alarms were generated on near end and far end for the service path. Below is the block diagram for the connection and service path. Handling Process Step1: we fix the connection and create the service again between Metro and OSN in site A, it was successful. Step2: Create the service on the whole path from metro in site A to OSN in site B. and try to ping, the service was successful, also the alarm TU_AIS_VC12 disappear. Root Cause Step1: After configuration 2 FE ports in Site A
Less
