It's a refresh upgrade so you don't get any options. On Mon, Jan 3, 2022 at 11:21 AM Lelio Fulgenzi <le...@uoguelph.ca> 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 > > On Jan 3, 2022, at 2:07 PM, Mathew Miller <miller.mat...@gmail.com> wrote: > > > > CAUTION: This email originated from outside of the University of Guelph. > Do not click links or open attachments unless you recognize the sender and > know the content is safe. If in doubt, forward suspicious emails to > ith...@uoguelph.ca > > 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 connect to server specified (5) > > Is that normal when in a cluster that the post upgrade COP file fails with > this message or a symptom of the bug? You don't happen to have a bug ID do > you? > > > > > > > > On Mon, Jan 3, 2022 at 10:55 AM James Buchanan <james.buchan...@gmail.com> > wrote: > >> Oh, the publisher moved to the new version, didn’t it? I remember Unity >> Connection doing that. It’s on version 14 already right? I think that’s a >> bug. >> >> Probably the most straightforward way to resolve is to rebuild the >> subscriber from scratch. >> >> On 3 Jan 2022, at 18:52, Mathew Miller <miller.mat...@gmail.com> wrote: >> >> >> 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 10:22 AM James Buchanan <james.buchan...@gmail.com> >> wrote: >> >>> 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 <miller.mat...@gmail.com> wrote: >>> >>> >>> 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 >>> >>> Enterprise Replication not active (62) >>> command failed -- unable to connect to server specified (5) >>> >>> >>> >>> utils dbreplication runtimestate it says >>> >>> >>> Cluster Detailed View from CUC-01 (2 Servers): >>> >>> PING DB/RPC/ REPL. >>> Replication REPLICATION SETUP >>> SERVER-NAME IP ADDRESS (msec) DbMon? QUEUE Group >>> ID (RTMT) & Details >>> ----------- ---------- ------ ------- ----- >>> ----------- ------------------ >>> CUC-01 X.X.X.X 0.018 Y/Y/Y -- (-) >>> (-) Replication Not Setup >>> CUC-02 X.X.X.X 0.125 Y/Y/Y -- (-) >>> (-) DB-diff >>> >>> >>> I've attempted to reset replication this way. >>> >>> >>> https://www.cisco.com/c/en/us/support/docs/unified-communications/unity-connection/116942-technote-uc-00.html >>> >>> >>> It doesn't seem to be working for me. Replication status always just >>> says not setup >>> >>> Any ideas? >>> >>> >>> _______________________________________________ >>> cisco-voip mailing list >>> cisco-voip@puck.nether.net >>> https://puck.nether.net/mailman/listinfo/cisco-voip >>> >>> _______________________________________________ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-voip > >
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip