[cisco-voip] Disaster Recovery Procedure CUCM 5.1(2)

Discussion:

Patrick Diener

2007-10-19 12:27:36 UTC

I'm trying to put together a rough step by step procedure to do a
disaster recovery for a cucm 5.1(2) cluster and there are some stuff I
can't figure out how it should/will work...

I based the steps on the DRS Admin Guide for Version 5.0 (5.1 not out yet?!?)

Important: I try to do a restore on a new server hw => new first node MAC

Step 1:
perform fresh install of cucm sw
!! set same hostname as before !!

Step 2:
perform restore using DRS and restart server (worked like a charm in the lab...)

form now on I'm stuck...

Step 3:
Licensing?!?
all activated services will not start cause the .lic files are not
valid for the new server hw (at least thats what happened in the
lab..)
=> will TAC send me a new .lic equal to the old one?
=> do I need to contact licensing at cisco.com?
=> any experience how long it will take to get the new .lic files?

Step 4:
move some phones to the restored publisher (assuming callmanager
service is running) and test all features needed
=> will the phones register if security has been configured? I assume
the new callmanager, tftp and capf certificates will not match the
certificates stored in the phones ctl file (right?) how do I get out
of this mess without touching each and every phone to delete the ctl
file or perform a factory reset?

Step 5:
restore sub (or subs)

all comments, experiences and remarks are appreciated!

cheers
Patrick

Scott Voll

2007-10-19 14:52:49 UTC

Permalink

for licensing you are correct. you will need cisco licensing to change the
mac address to the new hardware.

I'm guessing you have a couple hours involved in this. you might be able to
push it a little faster having a TAC engineer help, but that would have to
be confirmed by wes or ryan or mike.

Scott

PS. No clue on the scurity stuff.

Post by Patrick Diener
I'm trying to put together a rough step by step procedure to do a
disaster recovery for a cucm 5.1(2) cluster and there are some stuff I
can't figure out how it should/will work...
I based the steps on the DRS Admin Guide for Version 5.0 (5.1 not out yet?!?)
Important: I try to do a restore on a new server hw => new first node MAC
perform fresh install of cucm sw
!! set same hostname as before !!
perform restore using DRS and restart server (worked like a charm in the lab...)
form now on I'm stuck...
Licensing?!?
all activated services will not start cause the .lic files are not
valid for the new server hw (at least thats what happened in the
lab..)
=> will TAC send me a new .lic equal to the old one?
=> do I need to contact licensing at cisco.com?
=> any experience how long it will take to get the new .lic files?
move some phones to the restored publisher (assuming callmanager
service is running) and test all features needed
=> will the phones register if security has been configured? I assume
the new callmanager, tftp and capf certificates will not match the
certificates stored in the phones ctl file (right?) how do I get out
of this mess without touching each and every phone to delete the ctl
file or perform a factory reset?
restore sub (or subs)
all comments, experiences and remarks are appreciated!
cheers
Patrick
_______________________________________________
cisco-voip mailing list
https://puck.nether.net/mailman/listinfo/cisco-voip

Wes Sisk

2007-10-19 17:04:11 UTC

Permalink

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
TAC has no access to generate licenses.  Have to go to
<a class="moz-txt-link-abbreviated" href="mailto:***@cisco.com">***@cisco.com</a>.  /Wes<br>
<br>
Scott Voll wrote:
<blockquote
cite="mid:***@mail.gmail.com"
type="cite">
<div>for licensing you are correct.  you will need cisco licensing to
change the mac address to the new hardware.</div>
<div> </div>
<div>I'm guessing you have a couple hours involved in this.  you
might be able to push it a little faster having a TAC engineer help,
but that would have to be confirmed by wes or ryan or mike.</div>
<div> </div>
<div>Scott</div>
<div> </div>
<div>PS.  No clue on the scurity stuff.<br>
<br>
 </div>
<div><span class="gmail_quote">On 10/19/07, <b
class="gmail_sendername">Patrick Diener</b> <<a
moz-do-not-send="true" href="mailto:***@gmail.com">***@gmail.com</a>>
wrote:</span>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">I'm
trying to put together a rough step by step procedure to do a<br>
disaster recovery for a cucm 5.1(2) cluster and there are some stuff I
<br>
can't figure out how it should/will work...<br>
<br>
I based the steps on the DRS Admin Guide for Version 5.0 (5.1 not out
yet?!?)<br>
<br>
Important: I try to do a restore on a new server hw => new first
node MAC<br>
<br>
Step 1:<br>
perform fresh install of cucm sw<br>
!! set same hostname as before !!<br>
<br>
Step 2:<br>
perform restore using DRS and restart server (worked like a charm in
the lab...)<br>
<br>
form now on I'm stuck...<br>
<br>
Step 3:<br>
Licensing?!?<br>
all activated services will not start cause the .lic files are not<br>
valid for the new server hw (at least thats what happened in the<br>
lab..)<br>
=> will TAC send me a new .lic equal to the old one?
<br>
=> do I need to contact licensing at <a moz-do-not-send="true"
href="http://cisco.com">cisco.com</a>?<br>
=> any experience how long it will take to get the new .lic files?<br>
<br>
Step 4:<br>
move some phones to the restored publisher (assuming callmanager
<br>
service is running) and test all features needed<br>
=> will the phones register if security has been configured? I assume<br>
the new callmanager, tftp and capf certificates will not match the<br>
certificates stored in the phones ctl file (right?) how do I get out
<br>
of this mess without touching each and every phone to delete the ctl<br>
file or perform a factory reset?<br>
<br>
Step 5:<br>
restore sub (or subs)<br>
<br>
<br>
all comments, experiences and remarks are appreciated!<br>
<br>
cheers<br>
Patrick<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a moz-do-not-send="true" href="mailto:cisco-***@puck.nether.net">cisco-***@puck.nether.net</a><br>
<a moz-do-not-send="true"
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote>
</div>
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-***@puck.nether.net">cisco-***@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></pre>
</blockquote>
</body>
</html>

Wes Sisk

2007-10-19 17:03:14 UTC

Permalink

Hi Patrick,

Good stuff. Most of this is finally covered in CM513 docs:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_installation_guide09186a00808be1dc.html

ws: same hostname, ip, and passwords

Post by Patrick Diener
perform restore using DRS and restart server (worked like a charm in the lab...)
form now on I'm stuck...

ws: you restored the pub only, correct? and rebooted? after you
reinstall sub will need to DRS restore it as well.

Post by Patrick Diener
Licensing?!?
all activated services will not start cause the .lic files are not
valid for the new server hw (at least thats what happened in the
lab..)
=> will TAC send me a new .lic equal to the old one?
=> do I need to contact licensing at cisco.com?
=> any experience how long it will take to get the new .lic files?

ws: yep, new license files if replacing the pub. covered in the doc,

Post by Patrick Diener
move some phones to the restored publisher (assuming callmanager
service is running) and test all features needed
=> will the phones register if security has been configured? I assume
the new callmanager, tftp and capf certificates will not match the
certificates stored in the phones ctl file (right?) how do I get out
of this mess without touching each and every phone to delete the ctl
file or perform a factory reset?

ws: this comes later actually. check the doc, you will create new CTL
files using same USB token.

Post by Patrick Diener
restore sub (or subs)

step5: reinstall subs, then restore subs, then perform post-replace
checklist.

Post by Patrick Diener
all comments, experiences and remarks are appreciated!
cheers
Patrick
_______________________________________________
cisco-voip mailing list
https://puck.nether.net/mailman/listinfo/cisco-voip

Ruben Montes (Europe)

2007-10-19 17:27:56 UTC

Permalink

Hello,

I had to do a Publisher replacement from a MCS7825 to a MCS7835 last
week. We had two additional subscribers. I followed step by step the
guide Wes has mentioned and all went fine (the whole change took us 9
hours).

The main problem is that you MUST reinstall also all the subscribers
from the cluster: this was confirmed by TAC and by the customer's SE
cisco engineer.

If you have any additional question about this just drop me an email...

Regards,

Ruben

-----Mensaje original-----
De: cisco-voip-***@puck.nether.net
[mailto:cisco-voip-***@puck.nether.net] En nombre de Wes Sisk
Enviado el: viernes, 19 de octubre de 2007 19:03
Para: Patrick Diener
CC: cisco-***@puck.nether.net
Asunto: Re: [cisco-voip] Disaster Recovery Procedure CUCM 5.1(2)

Hi Patrick,

Good stuff. Most of this is finally covered in CM513 docs:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_installation_g
uide09186a00808be1dc.html

ws: same hostname, ip, and passwords

Post by Patrick Diener
perform restore using DRS and restart server (worked like a charm in the lab...)
form now on I'm stuck...

ws: you restored the pub only, correct? and rebooted? after you
reinstall sub will need to DRS restore it as well.

ws: yep, new license files if replacing the pub. covered in the doc,

ws: this comes later actually. check the doc, you will create new CTL
files using same USB token.

Post by Patrick Diener
restore sub (or subs)

step5: reinstall subs, then restore subs, then perform post-replace
checklist.

Patrick Diener

2007-10-22 12:57:05 UTC

Permalink

thanks a lot for all the good responses, you really helped a lot!!!

considering the new information I changed my step by step process to
the following:

Step 1: Gather necessary stuff
- contact cisco licensing to get new .lic files for the replacement publisher hw
- make sure the USB tokens needed to change the CTL File are accessible

Step 2: Install CUCM on replacement hw
- make sure to use same hostname, ip address and passwords as the
server you like to replace
- add .lic files acquired in Step 1
- check weather sufficient DLUs and node licenses are now available

Step 3: DRS
- recover the latest backup using the disaster recovery system

Step 4: Reinstall Subscribers
- a fresh install is necessary for all subscribers in the cluster
- after the reinstall use DRS to recovery lost data on the Sub. (I
assume activated services, enterprise parameters, etc.)

Step 5: Update CTL file and LSCs
- use CTL Client and USB tokens to update the CTL File with the new
Certificates of all CallManager nodes, the TFTP Servers and CAPF
- if used, update the LSCs (cause CAPF cert. has been changed(??))

=> as I see it telephony service will be interrupted during sub.
rebuild. if security is configured tel. service will not be back up
until step 5 is finished...

all this is also covered in the doc wes posted!

Regards
Patrick

Post by Ruben Montes (Europe)
Hello,
I had to do a Publisher replacement from a MCS7825 to a MCS7835 last
week. We had two additional subscribers. I followed step by step the
guide Wes has mentioned and all went fine (the whole change took us 9
hours).
The main problem is that you MUST reinstall also all the subscribers
from the cluster: this was confirmed by TAC and by the customer's SE
cisco engineer.
If you have any additional question about this just drop me an email...
Regards,
Ruben
-----Mensaje original-----
Enviado el: viernes, 19 de octubre de 2007 19:03
Para: Patrick Diener
Asunto: Re: [cisco-voip] Disaster Recovery Procedure CUCM 5.1(2)
Hi Patrick,
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_installation_g
uide09186a00808be1dc.html

yet?!?)

Post by Patrick Diener
Important: I try to do a restore on a new server hw => new first node

MAC

Post by Patrick Diener
perform fresh install of cucm sw
!! set same hostname as before !!

ws: same hostname, ip, and passwords

Post by Patrick Diener
perform restore using DRS and restart server (worked like a charm in

the lab...)

Post by Patrick Diener
form now on I'm stuck...

ws: you restored the pub only, correct? and rebooted? after you
reinstall sub will need to DRS restore it as well.

ws: yep, new license files if replacing the pub. covered in the doc,

ws: this comes later actually. check the doc, you will create new CTL
files using same USB token.

Post by Patrick Diener
restore sub (or subs)

step5: reinstall subs, then restore subs, then perform post-replace
checklist.

_______________________________________________
cisco-voip mailing list
https://puck.nether.net/mailman/listinfo/cisco-voip

Wesley Sisk

2007-10-22 13:58:01 UTC

Permalink

Patrick,

Nice compilation. You users will have dialtone after subscriber install.
Technically you could wait until next maint window to redo
security/capf/tls. existing phones will register to the cluster.
However, you will not be able to add new phones.

Ruben Montes (Europe)

2007-10-22 16:42:26 UTC

Permalink

Hello,

Just my 5 cents... In my case, it was necessary to update the CTL in
order to have all the phones registered again in the cluster...

Regards,

Ruben

-----Mensaje original-----
De: cisco-voip-***@puck.nether.net
[mailto:cisco-voip-***@puck.nether.net] En nombre de Wesley Sisk
Enviado el: lunes, 22 de octubre de 2007 15:58
Para: Patrick Diener
CC: cisco-***@puck.nether.net
Asunto: Re: [cisco-voip] Disaster Recovery Procedure CUCM 5.1(2)

Patrick,

Nice compilation. You users will have dialtone after subscriber
install.
Technically you could wait until next maint window to redo
security/capf/tls. existing phones will register to the cluster.
However, you will not be able to add new phones.