[cisco-voip] P2V CUCM 8.5.1

[Michael Hamann]

Hello Ryan,

now I am a bit confused but I may not have described our plan clearly.

The only maschine we want to virtualize is the publisher. Within the maintenance
window we want to shut down the physical pub (A) plus one physical sub (B) - but
just to have them safe if something crashes completely. Only the sub (B) will be
used again if everything went fine.

So while installing the new publisher in a vm all phones will be registered and
running on the only sub (C) left. After installing the Base software + upgrade,
locales, cop files etc. we plan a restore with DRS to the new pub (A-new),
rehost the license. After all this we start sub (B) again and hope to have all 3
maschine running well.

Is this the right plan ?
Michael


> Ryan Ratliff <rratliff at cisco.com> hat am 28. Februar 2013 um 15:40
> geschrieben:
> 
>  Yes, you should be all set with respect to your certificates getting backed
> up.
> 
>  With respect to the sub right now your phones have ITL files that include
> certificates to trust the TFTP server they got the ITL file from, one CAPF
> cert, and TVS on every node in the cluster.   Any time you do a fresh install
> of a server it gets new certificates, which immediately makes that server
> untrusted by phones until they get a new ITL/CTL file that includes info for
> that new node.
> 
>  If your publisher is used for TFTP then as long as the phones continue to
> trust it then they will take any updated ITL file and trust the sub(s) just
> fine.  It is far easier to just put the sub into the cluster before you do the
> restore so you don't change certs, lose MOH files, etc.
> 
>  Regarding that existing sub, you're going to want to isolate the VMs from the
> production network until they are restored anyway (you don't want phones
> talking to the new pub before it's restore) so it should be able to stay
> active with  no issues.  In fact if you go that route you can take your time
> building the vm cluster, make sure to get all the right locales and phone
> loads reinstalled, then do the backup/restore/switch in one maintenance
> window.
> 
>  -Ryan
> 
>  On Feb 28, 2013, at 4:50 AM, Michael Hamann < mail at mhamann.net
> <mailto:mail at mhamann.net> > wrote:
> 
>  Hello Ryan,
> 
>  thank you for your hint! To correct myself we use CUCM Version 8.5.1.14900-5
> at the moment. Am I right that the bug you mentioned is fixed in this version
> and that our DRS backup should include the certificates ?
> 
>  > 2. You need to install the sub in VM before you do the DRS restore or its
>  > certificates will not be restored and phones won't trust it.
> 
>  Our plan is to shut down one of the subs and have the last sub still running
> (to stay in production).  If we have the right certificates restored on the
> publisher is this still a problem ?
> 
>  Michael
> 
> 
>   > > Ryan Ratliff < rratliff at cisco.com <mailto:rratliff at cisco.com> > hat am
>   > > 27. Februar 2013 um 17:54 geschrieben:
> > 
> >   There are two things that immediately jump out at me that are going to
> > give you ITL headaches.
> >   1. You need to get the fix for CSCtn50405 before you move to vm.
> >   2. You need to install the sub in VM before you do the DRS restore or its
> > certificates will not be restored and phones won't trust it.
> > 
> > 
> >   -Ryan
> > 
> >   On Feb 26, 2013, at 4:15 PM, Michael Hamann < mail at mhamann.net
> > <mailto:mail at mhamann.net> > wrote:
> > 
> >   Hello,
> > 
> >   we plan to migrate our productive CUCM 8.5.1 publisher running on a cisco
> > labeled IBM server to VMware 5.0 environment running on a spec cisco UCS
> > system. We have two subs (7825I) plus the publisher in the cluster. We
> > heavily use extension mobility with active directory integration.
> > 
> >   We plan the migration for the next weekend. Our plan is so far:
> > 
> >   - Backup all maschines
> >   - Taking down pub + 1 sub
> >   - Build a new publisher in a vm prepared with the right ova template. Same
> > IP etc...
> >   - restore settings and files with drs
> >   - rehost the license file from old license mac to the new one.
> >   - after some checks - boot up the sub
> >   - check db synchronisation
> >   - done
> > 
> >   Do we miss something ? Do we have to take care of the logged in extension
> > mobility user ? Will they still be logged in after a restore ?
> > 
> >   Any hints appreciated...
> > 
> >   Thank you
> >   Michael
> >   _______________________________________________
> >   cisco-voip mailing list
> >   cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> >   <https://puck.nether.net/mailman/listinfo/cisco-voip>
> > 
> >  > 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130228/e7a4ec99/attachment.html>