No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

BSC(PCU)-SGSN Can't Communicate When Redundant Link Between Two Sites Is Active

Publication Date:  2012-07-27 Views:  37 Downloads:  0
Issue Description
BSC is at Hubli location and SGSN is Banglore location. There is direct lease line between these two locations. For redundancy purposes, a third location Manglore is connect to Hubli and Banglore. So the primary path for BSC traffic was Hubli to Banglore and the redundant path was Hubli-Manglore-Banglore. The issue was that whenever primary path goes down the Gb link between BSC and SGSN goes down. For details please check attached diagram.
The router used was NE40E.
Alarm Information
Gb link shows down at BSC side.
Handling Process
1. Issue detected during redundancy checking.
2. Traceroute shows request droping at PE2 router.
3. Routing was checked at PE2.
4. Routing changed at PE2 router.
Root Cause
The root cause was that whenever seconday link (Hubli-Manglore-Banglore) is active the requests was coming to PE2 routers. The routing on PE2 router for logical IP of BSC was routed towards non active IP(IP of slot15 board) of BSC.  so the requests from SGSN were droped at non active card. 
Suggestions
Suggestions: The logical IP of BSC should always be routed to active IP of PCU card in both PE routers.

END