I recall reading in the pre-upgrade steps for CUCM to check for expired certs.
The cucm steps seem more thought out than connection.
For example, cucm upgrade talks about vmTools refresh but connection doesn’t.
Apparently.
Sent from my iPhone
On Jan 3, 2022, at 3:59 PM, James Buchanan wrote:
That’s a needle in the haystack! Thanks for sharing the fix!
> On 3 Jan 2022, at 20:47, Mathew Miller wrote:
>
>
> It was failing the upgrade, so I went to try the tool again. It seems I had
> an expired ip-sec cert which was causing the problem. I regenerated that and
> a couple of magic
It was failing the upgrade, so I went to try the tool again. It seems I had an
expired ip-sec cert which was causing the problem. I regenerated that and a
couple of magic reboots and it seems to be working now.
> On Jan 3, 2022, at 11:46 AM, Matthew Loraditch
> wrote:
>
>
> It won’t
Seems like Unity clustering isn’t as trouble free as they’d have us believe. :(
Sent from my iPhone
On Jan 3, 2022, at 2:40 PM, Buchanan, James wrote:
CAUTION: This email originated from outside of the University of Guelph. Do not
click links or open attachments unless you recognize the
That’s a really good point—the last time I did a refresh upgrade, I didn’t run the tool after upgrading each server—just after the cluster was upgraded. From: Matthew LoraditchSent: 03 January 2022 19:46To: Mathew Miller; James BuchananCc: Cisco VOIPSubject: RE: [cisco-voip] CUC 10.5 to 14 ER Not
It won’t upgrade or you are running the check and it’s failing? It’s been a
while since I’ve done one of these myself, but if it’s just the check tool,
try to just run the actual upgrade.
I believe the tool is intended to be run on all servers before you start
anything.
From: cisco-voip On
The refresh upgrade with CUCM gives you the option to decide when to move to the new version but Unity Connection doesn’t. I didn’t find any bug ID around this, but I imagine you’ll have to either 1) switch the publisher back to 10.5 (utils sytem switch-version) and then upgrade the subscriber, or
It's a refresh upgrade so you don't get any options.
On Mon, Jan 3, 2022 at 11:21 AM Lelio Fulgenzi wrote:
> I wonder if it’s like cucm where you upgrade pub first without switch
> version then upgrade sub without switch version, then switch version on pub
> then on sub.
>
> Sent from my iPhone
I wonder if it’s like cucm where you upgrade pub first without switch version
then upgrade sub without switch version, then switch version on pub then on sub.
Sent from my iPhone
On Jan 3, 2022, at 2:07 PM, Mathew Miller wrote:
CAUTION: This email originated from outside of the University
Yes, Publisher upgraded and is on 14.X.
The post upgrade COP file when run on the pub says.
1.1 FAIL Cluster Database Status (Node authentication and replication
status)
When I do a utils dbreplication status it shows
Enterprise Replication not active (62)
command failed -- unable to
The subscriber will not upgrade.
I'm getting a failure on the pre-upgrade check for the subscriber.
1.1 FAIL Network status (NTP, DNS, Cluster Connectivity)
validate_network: Error, intra-cluster communication is broken,
unable
to connect to X.X.X.X
On Mon, Jan 3, 2022 at
Hello,
Have you upgraded the subscriber? That needs to be done before database
replication will work.
Thanks?
James
> On 3 Jan 2022, at 18:15, Mathew Miller wrote:
>
>
> Hello,
>
> Working on an upgrade from CUC 10.5 to 14.
>
> Publisher finished and didn't seem to have any issues.
>
Hello,
Working on an upgrade from CUC 10.5 to 14.
Publisher finished and didn't seem to have any issues.
After running the post upgrade check COP file it fails
1.1 FAIL Cluster Database Status (Node authentication and replication
status)
When I do a utils dbreplication status it shows
13 matches
Mail list logo
