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

Gary_Bates_Command_Solutions gbates at commandsolutions.com.au
Mon Jan 30 19:01:31 EST 2017


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>
Cc: Gary_Bates_Command_Solutions <gbates at commandsolutions.com.au>; Cisco
VoIP List <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

 



 

 Mobile 0424 229 995 ( + 61 424 229995 <tel:+61%20424%20229%20995>  )

 Email:  <mailto:garycomsolutions at iprimus.com.au>
gbates at commandsolutions.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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170131/3055bb36/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2737 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170131/3055bb36/attachment.jpg>


More information about the cisco-voip mailing list