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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Manual Failover of IP Phones to Secondary controller

Status
Not open for further replies.

Broaders

Technical User
Jun 4, 2010
6
GB
Hello,

I would like to manually failover any IP sets on the primary controller to the secondary controller. These are two 3300 devices Running 7.1 PR2 / 13.1.0.38

I require moving the IP trunk to a different switch on the primary controller.

Can a failover be done gracefully aswell?

Thanks in advanced

Ian
 
hmm think I found it, HST COURTESY HANDOFF

I assume this is all I need?
 
Why would reconfiguring the trunking require you to fail over the IP sets? Just change your route lists to go around the trunks you're messing with.
 
I'm going to physically unplug the link to the network, the local phones to that controller will loose IP connectivity to the controller no?

Meaning they fail over to the other controller? I'd rather do it gracefully though.

The controllers themselves have two 10/100/1000 LAN ports, are they resilient in the sense that I can plug both of them in to different switches but the same vlan meaning the controller doesn't loose IP connectivity to the network?
 
The commands can be found in the system help just be aware they are case sensitive and are done via the shell. (You can use putty to access the shell)


hsHelp

hsShowIcps

hsShowSets

hsHandoff

hsHandback

hsPushback

hsDebug

hsTrace
 
Oh, yeah, I guess unplugging the network link to the controller would disrupt the IP sets as well as the trunking, I mis-read what you're trying to do.

Yes, the HST Courtesy Handoff command is what you want, but you have to give it a couple of minutes to gracefully push all the phones over to the resilient controller. Use the "HST Status Handoff" to see how many are failed over or still pending, then once they're all over, unplug your Ethernet cable.

Failback from the secondary back to the primary should take about 5 minutes assuming you're using the default settings ("Resiliency - Allow Return to Primary"; "Resiliency - Secondary ICP Health Check"; and "Resiliency - Successful Health Checks Prior to Hand Off") in Controller Registry form.

The whole failover/failback process works pretty well if you just give it time to do it's thing.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top