[cisco-voip] MRA failover doesn't work, Cisco TAC agrees, says it's a documentation defect

[Matthew Huff]

We have a fairly common and standard deployment for our MRA solution. All are running CUCM 14+, latest Expressway, etc...

Vmware server 1 (jn DMZ)
  ExpressWay-E-1

Vmware server 2 (in DMZ)
   ExpressWay-E-2

Vmware Server 3 (In Core)
  CUCM Publisher
   Expressway-C-1

VMWare Server 4( In Core)
   CUCM Subscriber
   Expressway-C-2



  1.  If ether Expreway-E VMs fail, redundancy works fine
  2.  If either CUCM fails, redundancy works fine
  3.  If either Expressway-C VMs fail, redundancy works fine
  4.  If VMWare Server 4 fails (say during patching, hardware maintenance or hardware failure), redundancy fails. Remote phones un-register and never register no matter what is done. If either CUCM Subscriber or Expressway-C-2 is brought back online, phones register.

Cisco TAC claims that this is a limitation of our Cisco 88xx SIP MRA phones and is not solvable unless we purchase two new vmware servers and split the CUCM and Expressway-C into separate servers so they both won't go down at once. Sinc VMWare Server 3 & 4 are at different locations, vMotion isn't an option since there is no shared storage.

Anyone run into this or have any suggestions? We have engaged our VAR and cisco rep and may have to replace our phone system since we are all working from home and MRA support including redundancy is critical to us.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20220621/81f1ec0c/attachment.htm>