We ended up reinstalling the subscriber... faster than trying to figure out
why it wouldn't work...
On Mon, Mar 21, 2016 at 8:23 AM, Jonathan Charles wrote:
> We weren't changing the domain...
>
> On Fri, Mar 18, 2016 at 10:43 PM, Dave Wolgast wrote:
>
>> Just to be sure, is the new domain the
We weren't changing the domain...
On Fri, Mar 18, 2016 at 10:43 PM, Dave Wolgast wrote:
> Just to be sure, is the new domain the same as the old domain? When we
> wanted to change the domain, we actually had to redo the DNS with the old
> domain to make PCD work. We then changed the domain in DN
I'm sure you verified that the reverse arpa lookup is also working for that
forward FQDN?
Sent from my iPhone
On Mar 18, 2016, at 11:57 PM, Jonathan Charles
mailto:jonv...@gmail.com>> wrote:
No change to domain... this was a PCD migration cluster... we are now changing
the cucm 11 migration c
No change to domain... this was a PCD migration cluster... we are now
changing the cucm 11 migration cluster's hostnames and IPs to be the ones
of the old 8.5 cluster.
Jonathan
On Fri, Mar 18, 2016 at 10:43 PM, Dave Wolgast wrote:
> Just to be sure, is the new domain the same as the old domain
We are running PCD 11 against a CUCM 11 cluster.
On the readdress, we are getting a failure:
ERROR node.domain is invalid.
We also tried running it from the CLI:
Domain is invalid.
We have verified DNS is correct for the new name, the IP is not in use...
and Google is blank on this...
Any ide
