I'd recommend option 2. That way when the subscriber comes back up after the IP change everything should be all set in the cluster.<br><br>You could probably walk through option 1 without any problems as well. Just that when the sub comes up after the IP change it won't have connectivity to anything, but that should resolve itself once you move it to the other location.<br>
<br>You might have to run "utils dbreplication status" or check the Unified Reporting GUI to confirm replication is still good after doing all of this, just to be on the safe side.<br><br><div class="gmail_quote">
On Mon, Nov 17, 2008 at 10:25 AM, Nick <span dir="ltr"><<a href="mailto:csvoip@googlemail.com">csvoip@googlemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Has anyone done this procedure and can advise on this please?<br><br><br><div class="gmail_quote">2008/11/14 Nick <span dir="ltr"><<a href="mailto:csvoip@googlemail.com" target="_blank">csvoip@googlemail.com</a>></span><div>
<div></div><div class="Wj3C7c"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>I need to build a subscriber in one location and then ship it to different location and change the IP address. </div>
<div> </div>
<div>I have just read the following document but I'm not clear on whether I should?</div>
<div> </div>
<div><a href="http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/install/6_1_1/ipchange/ipchg611.html" target="_blank">http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/install/6_1_1/ipchange/ipchg611.html</a> </div>
<div> </div>
<div>1) Build the subscriber then change the IP address at location 1 while it is still on line, reboot the cluster then power down the subscriber and ship it to location 2. </div>
<div> </div>
<div>or</div>
<div> </div>
<div>2) Build the subscriber, power it down, ship it to location 2, then proceed with the IP address change, then reboot the cluster.</div>
<div> </div>
<div> </div>
</blockquote></div></div></div><br>
<br>_______________________________________________<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" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>