We have 4 LSP's and 1 ESS that register back to seconday ESS (8500) not Primary (8730 CM5.2) after a failover test. We have confirmed in the MGC list for all 5 servers (4-8300's and 1-8510) the Primary IP address in line 1 with Secondary ESS in line 2, but they still register back to secondary ESS everytime. In ideas where we should look to force them back to the Primary?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
LSP/ESS won't register to Primary 1
- Thread starter fondog
- Start date
jimbojimbo
Vendor
LSP's should not be registering to an ESS server pair. The gateways should register to the CLAN's or Processor Ethenet associated with the ESS server provided the timers and transition points are properly set. I believe the default primary timer is still 1 minute which does not provide sufficient time for the ESS to take control of the cabinets and for the CLAN boards to come back on-line.
- Thread starter
- #4
Hi jimbo,
What I should have stated was that our 8300 LSP's in (Denver, San Fran, Ill, and LA) and 8500 ESS (PA) are registering back to the gateway for our 8500 ESS in FL not our primary 8730 gateways in NJ when we do a failover test. The timers all seem to be correct, however, when we restore power and/or the network connections to bring the Primary online and do a 'list media', we see that they are registered to FL ESS IP not NJ primary IP even though the IP address for primary gateway is the 1st IP address in the MGC list. We have to telnet into each gateway and 'clear mgc list', then add each IP address back in individually. We have these set on manual not auto, could that possibly be the issue. On amother note, we have one other LSP that always registers back to the primary and they are all set up the same way.
What I should have stated was that our 8300 LSP's in (Denver, San Fran, Ill, and LA) and 8500 ESS (PA) are registering back to the gateway for our 8500 ESS in FL not our primary 8730 gateways in NJ when we do a failover test. The timers all seem to be correct, however, when we restore power and/or the network connections to bring the Primary online and do a 'list media', we see that they are registered to FL ESS IP not NJ primary IP even though the IP address for primary gateway is the 1st IP address in the MGC list. We have to telnet into each gateway and 'clear mgc list', then add each IP address back in individually. We have these set on manual not auto, could that possibly be the issue. On amother note, we have one other LSP that always registers back to the primary and they are all set up the same way.
-
1
- #5
fondog, that is normal. LSP's will NOT fail back to a main site, from an ESS, without issuing the "get forced-takeover ipserver-interface X", where X="all" or "port-network x"
ESS Servers are designed this way, until you join them back manually to the main switch, the LSP's will stay registered to the ESS.
This is assuming you have G650's/IPSI's/CLANs, and are not just using Media Gateways with Processor Ethernet.
Mitch
Mitch
AVAYA Certified Expert
ESS Servers are designed this way, until you join them back manually to the main switch, the LSP's will stay registered to the ESS.
This is assuming you have G650's/IPSI's/CLANs, and are not just using Media Gateways with Processor Ethernet.
Mitch
Mitch
AVAYA Certified Expert
- Thread starter
- #6
- Status
Similar threads
- Locked
- Question
- Locked
- Question