<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>Hi guys,</div>
<div><br>
</div>
<div>Just to add to this, this is one of the reasons we generally have pub as backup call processor, and sub as primary (in a small cluster)</div>
<div>Then you can do your changes on pub with less impact.</div>
<div><br>
</div>
<div>Cheers,</div>
<div><br>
</div>
<div>Tim.</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Jeremy Bresley <<a href="mailto:brez@brezworks.com">brez@brezworks.com</a>><br>
<span style="font-weight:bold">Date: </span>Sunday, 4 January 2015 07:20<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>" <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [cisco-voip] Device pack installation methodology question<br>
</div>
<div><br>
</div>
<div>
<div bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 1/3/2015 2:11 PM, Ryan Huff wrote:<br>
</div>
<blockquote cite="mid:COL130-W48A39D289EC54932FB996DC55A0@phx.gbl" type="cite"><style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">I need to install a device pack on a 2 node 9.1(2) CCM cluster to get support for some 88xx phones but I do not want to update the loads for anything else.<br>
<br>
The approach I am going to use is:<br>
<br>
Drop the publisher out of the CM Group, forcing all phones to the subscriber. Install the device pack on the publisher and reboot the publisher. Once the publisher is backup, set all the device defaults back to what I want them to be then add the publisher
back to the CM Group. Then drop the subscriber from the CM Group forcing all the phones on the publisher and start the install process over for the subscriber. Once everything is back up add the subscriber back to the CM Group.<br>
<br>
Does that sound reasonable or is there an easier way?<br>
</div>
</blockquote>
<br>
Any time I've needed device support I just install it on all the nodes then reboot them one at a time during a maintenance window. As long as both nodes are running call processing, they'll fail over when the node reboots. Not sure about on 9.X, but on 10.X
this just shows as a blip on the phones of them reregistering, not a full reboot. Obviously if you install new software for those phones, they'll upgrade software when they reboot.<br>
<br>
Jeremy "TheBrez" Bresley<br>
<a class="moz-txt-link-abbreviated" href="mailto:brez@brezworks.com">brez@brezworks.com</a><br>
</div>
</div>
</span>
</body>
</html>