I changed the node names tonight and so far so good... one awful thing
happened. I have a pretty complex profile setup in RTMT that shows graphs,
charts, had specialized alerts in it. It took a good while to get it put
together in a decent format. When I changed the name of the publisher, it's
not complaining that the name of the nodes is not found in the database.
GACK! Any chance of fixing this one? I'd hate to have to rebuild that
Exact error message is "Unable to restore configuration! Host name in the
configuration is not defined in the DB!"
On Wed, Aug 31, 2016 at 4:20 PM, Nick Barnett <nicksbarn...@gmail.com>
> awesome info, thank you! I'm pretty sure our gateways have DNS, but I'll
> be making sure... and I've dealt with enough dbreplication issues lately
> that I'll be vigilant on that as well. It may take me 8 hours to do it that
> way though.... blech. I just had to do a cluster reboot earlier this week
> and it took just under an hour with 9 nodes.
> On Wed, Aug 31, 2016 at 4:15 PM, <dan...@ohnesorge.me> wrote:
>> One of the most important points that people tend to forget when changing
>> the processnode (System>Server) entries is that MGCP and SCCP gateways will
>> download a config file (like a phone) and will need to resolve these
>> entries. For what ever reason I've seen so many customers not add any ip
>> name server to their routers so this one can bite you in the ass.
>> Now with regards to actually changing the entries, I have done this way
>> too many times. What you REALLY need to do is change the entry one by one,
>> then restart all the nodes in the cluster one by one. Then change the next
>> entry and repeat! I know this sounds totally unnecessary but the
>> processnode has the ability to stuff up your dbreplication to the point
>> where TAC will suggest a rebuild.
>> Sent from my iPhone
>> On 1 Sep 2016, at 06:39, Ryan Huff <ryanh...@outlook.com> wrote:
>> If the UC servers already have DNS entries (means they already have a
>> domain name too); then the servers are already using FQDNs, at least for
>> internal referencing. If you're saying the you want to change the
>> processNode names (the CM Server references) then as long as the FQDNs are
>> resolvable in the forward and reverse direction, it should be fine.
>> If you need to change the hostname or domain names of the servers to
>> something more palatable (a crossroads often encountered when dealing with
>> Jabber and end users and UC servers that were IP addresses first); that is
>> a horse of a much different color; please *carefully *consult
>> 100_chapter_0100.html (especially in the case of IM & Presence HA)
>> If you are also talking about changing the IP Phone URL references under
>> Enterprise Parameters (from IP address to FQDN); your phone networks will
>> need DNS capabilities to resolve those FQDNs as well. As a matter of
>> practice, I always ensure IP phone networks have DNS capabilities, but it
>> can be uncommonly found out in the wild.
>> Beyond that, if you are simply just changing the processNode references
>> for IP addresses to FQDNs (presumably, so CUCM requests come from an FQDN
>> and not an IP address) and everything is already resolving correctly, you
>> should be g2g.
>> = Ryan =
>> *From:* cisco-voip <cisco-voip-boun...@puck.nether.net> on behalf of
>> Nick Barnett <nicksbarn...@gmail.com>
>> *Sent:* Wednesday, August 31, 2016 4:13 PM
>> *To:* Cisco VoIP Group
>> *Subject:* [cisco-voip] Are there any gotchas to watch out for switching
>> to FQDN server names from IP address server names?
>> 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!
>> cisco-voip mailing list
cisco-voip mailing list