[cisco-voip] Are there any gotchas to watch out for switching to FQDN server names from IP address server names?

[Nick Barnett]

I just thought I would share what happened with this, even though it is
super old. Changing the node names to FQDN was mostly painless. The one
thing that bit me was bug CSCuy13916. After changing the names of the
nodes, the TFTP service needs to be DEACTIVATED and then re-activated in
order to fully update the certificates.  Before taking those steps, I kept
getting certificate errors from CuciLync, but afterwards, everything worked
as designed.

Other than that, any CTI route points (and any other device as well) that
exist will fall to another node in the CMG. Not a big deal, just something
to be aware of.

Thanks,
Nick

On Wed, Aug 31, 2016 at 3:13 PM, Nick Barnett <nicksbarnett at gmail.com>
wrote:

> We are on 10.0 and this cluster has been upgraded over the years from 8.0
> to 8.6 to 10.0.  I know it used to be common practice to rip the host name
> out of a new node and put in the IP address. That's how we are set up...
> but now that I need to do some work with certs so that jabber and cucilync
> work properly, it's time to fix this.
>
> Is there anything I should watch out for? Anything that may bite me in
> rare cases? We have CER, CVP, CUC, UCCE and a rarely used IMP.
>
> I checked that each node has DNS enabled by looking at "show network eth0"
> on each sub. I also then looked up each FQDN from each node and they all
> resolve properly. As far as I know, that's about it.
>
> Thanks in advance!
>
> nick
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20161128/3b0e7619/attachment.html>