[cisco-voip] Cluster setup with 2 Subs - Sub 2 did not pick up the load.

Ryan Ratliff (rratliff) rratliff at cisco.com
Tue Jan 31 09:58:14 EST 2017


What phones are you using?

In general if your CM groups are configured correctly then yes, phones should fail over to the third server but as others have indicated it requires that:
1) The phone have the 3rd sub in its CM group (or CCM will reject the registration attempt)
2) The phone knows about the 3rd server so it will even try to use it

If 1 was a problem your phones would have shown registration rejected on the display. CCM traces would confirm this and probably exist today since this is a backup sub.
If 2 was a problem then only logs from the phones at the time would have helped, nothing that’s going to exist after the fact.

My recommendation would be to test a single phone now to make sure it can register to the 3rd sub. Make a copy of the CM group and Device Pool, assign it to a single phone and start changing up the CM group to test.
You should see on the phone’s web page (make sure to turn it on) all 3 servers listed under network setup. The phone will maintain an active connection to the active and first backup servers (shows as Standby), see the attached screenshot.
[cid:7624463E-CA1B-4760-B0DB-61C40FDDDA9B at cisco.com]

If you don’t see all three servers listed then check Status Messages for an error like “Trust List Update Failed” which means you’ve got an issue with the ITL, a very real possibility if your client is really on UCM 8.5 still.

-Ryan

On Jan 30, 2017, at 7:22 PM, Gary_Bates_Command_Solutions <gbates at commandsolutions.com.au<mailto:gbates at commandsolutions.com.au>> wrote:

HI Ryan

possible, I wasn’t around wen it was setup.


From: Ryan Huff [mailto:ryanhuff at outlook.com]
Sent: Tuesday, 31 January 2017 11:08 AM
To: Gary_Bates_Command_Solutions <gbates at commandsolutions.com.au<mailto:gbates at commandsolutions.com.au>>
Cc: Nathan Reeves <nathan.a.reeves at gmail.com<mailto:nathan.a.reeves at gmail.com>>; Cisco VoIP List <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Cluster setup with 2 Subs - Sub 2 did not pick up the load.

Was the third node (the second subscriber) added after the cluster (pub and sub1) was established and phones already registered?

Sent from my iPhone

On Jan 30, 2017, at 7:02 PM, Gary_Bates_Command_Solutions <gbates at commandsolutions.com.au<mailto:gbates at commandsolutions.com.au>> wrote:
Hi Ryan

Not using DNS to resolve Hostnames, all server names are IP addresses.
On Sub 2 , the CM services and TFTP services were checked and no issues.

One question, how do you check “all registerable nodes are listed in the trust list” ??

On the phones I am seeing TFTP server 1 --> Sub 1 and TFTP server 2 --> Sub 2

When I manually change TFTP server 1 to point to Sub 2 it asks me to erase the ITL, does that sound right ?

Thx Gary

From: Ryan Huff [mailto:ryanhuff at outlook.com]
Sent: Monday, 30 January 2017 11:42 PM
To: Nathan Reeves <nathan.a.reeves at gmail.com<mailto:nathan.a.reeves at gmail.com>>
Cc: Gary_Bates_Command_Solutions <gbates at commandsolutions.com.au<mailto:gbates at commandsolutions.com.au>>; Cisco VoIP List <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Cluster setup with 2 Subs - Sub 2 did not pick up the load.

I realize you mentioned the IP addresses of the communications manager servers were listed in the phone's trust list however; keep in mind that if DNS/FQDNs are being used, the phones will also have to be able to resolve those FQDNs (otherwise, you'd likely experience something very similar to this).

If you have verified from the individual phone, that all registerable nodes are listed in the trust list, verify those nodes are also in the CM Server Group.

You might also check on this server node that did not except phone registrations, that CM services and TFTP services are enabled.

-Ryan

On Jan 30, 2017, at 2:15 AM, Nathan Reeves <nathan.a.reeves at gmail.com<mailto:nathan.a.reeves at gmail.com>> wrote:
Which Servers are included in the Server Group which is selected in the Device Pool assigned to the Phones?  When you mention 'TFTP Server lists', I'm assuming you mean the IP Addresses included in DHCP Option 150?  This is seperate to the CUCM Servers that are pushed to the phones.

But assuming all servers are included in the CUCM Server Group assigned to the Device Pool, the phones should have failed over upon loss of communication with their primary (and possibly) secondary CUCM Server.

Take a look at the web page of a phone and under the 'Network Setup' page, see what are set for 'Unified CM 1', 'Unified CM 2' and 'Unified CM 3' are.

On Mon, Jan 30, 2017 at 2:52 PM, Gary_Bates_Command_Solutions <gbates at commandsolutions.com.au<mailto:gbates at commandsolutions.com.au>> wrote:
My client had an issue where the 2nd sub did not register any phones when the Pub and primary Sub failed.

This is a 1500 seat call centre so it caused a massive problem.

All phones have the IP addresses of both subs in their TFTP server lists. Network routing confirmed ok. Call Manager / TFTP service running on both Subs. DB replication status good.

Could someone confirm that if Pub / Sub 1 go down, Sub 2 should allow phone/ device registration and calls to still work ?

Regards

 Gary Bates
 Voice and Network Specialist
 CCIE #53842

<image001.jpg>

 Mobile 0424 229 995 ( + 61 424 229995<tel:+61%20424%20229%20995> )
 Email: gbates at commandsolutions.com.au<mailto:garycomsolutions at iprimus.com.au>


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170131/c05aaa14/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2017-01-31 at 9.55.34 AM.png
Type: image/png
Size: 45778 bytes
Desc: Screen Shot 2017-01-31 at 9.55.34 AM.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170131/c05aaa14/attachment.png>


More information about the cisco-voip mailing list