Call Manager Upgrade Sequencing

[Ben Duff]

Hi,

In the past when upgrading our small cluster we've upgraded the Publisher and then upgraded the Subscribers and then rebooted/switch version the Publisher and then the Subscribers. This has worked fine.

We're looking to go from 12.5 SU3 to 12.5 SU4 but there's bug CSCvx76922 titled During Upgrade Without Switch Version Subscriber Upgrade Hangs which we'd prefer to avoid running into. It says "If switch version is done first on the Publisher, this issue will not be seen."

To me this is saying upgrade the Publisher and switch version/reboot before upgrading the Subscribers, is this supported as the Upgrade Sequencing document doesn't mention it, it's always upgrade Publisher then upgrade Subscribers and then switch versions.

Thanks

Ben

[Nithin Eluvathingal]

The bug id says the publisher should be switched before upgrading the sub and this behaviour is not seen to every subscriber its intermittent issue.

Workaround is contact TAC. 

Open a case with TAC for the workaround to get applied.