<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Yes, you should be all set with respect to your certificates getting backed up.<div><br></div><div>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. </div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">-Ryan</span>
</div>
<br><div><div>On Feb 28, 2013, at 4:50 AM, Michael Hamann <<a href="mailto:mail@mhamann.net">mail@mhamann.net</a>> wrote:</div><br class="Apple-interchange-newline">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<div style="">
<div>
Hello Ryan,
</div>
<div>
</div>
<div>
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 ?
</div>
<div>
</div>
<div>
> 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.
</div>
<div>
</div>
<div>
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 ?
</div>
<div>
</div>
<div>
Michael
</div>
<div>
</div>
<blockquote style="position: relative; margin-left: 0px; padding-left: 10px; border-left: solid 1px blue;" type="cite">
Ryan Ratliff <<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>> hat am 27. Februar 2013 um 17:54 geschrieben:
<br>
<br>There are two things that immediately jump out at me that are going to give you ITL headaches.
<div>
1. You need to get the fix for CSCtn50405 before you move to vm.
</div>
<div>
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.
</div>
<div>
</div>
<div>
<br>
<div>
<span style="border-collapse: separate; font-family: Helvetica; border-spacing: 0px;" class="Apple-style-span">-Ryan</span>
</div>
<br>
<div>
<div>
On Feb 26, 2013, at 4:15 PM, Michael Hamann <
<a href="mailto:mail@mhamann.net">mail@mhamann.net</a>> wrote:
</div>
<br class="Apple-interchange-newline">
<div>
<div>
Hello,
</div>
<div>
</div>
<div>
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.
</div>
<div>
</div>
<div>
We plan the migration for the next weekend. Our plan is so far:
</div>
<div>
</div>
<div>
- Backup all maschines
</div>
<div>
- Taking down pub + 1 sub
</div>
<div>
- Build a new publisher in a vm prepared with the right ova template. Same IP etc...
</div>
<div>
- restore settings and files with drs
</div>
<div>
- rehost the license file from old license mac to the new one.
</div>
<div>
- after some checks - boot up the sub
</div>
<div>
- check db synchronisation
</div>
<div>
- done
</div>
<div>
</div>
<div>
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 ?
</div>
<div>
</div>
<div>
Any hints appreciated...
</div>
<div>
</div>
<div>
Thank you
</div>
<div>
Michael
</div>
</div> _______________________________________________
<br>cisco-voip mailing list
<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</div>
</div>
</blockquote>
<div>
<br>
</div>
</div></div><br></div></body></html>