<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 1/3/2015 2:31 PM, Ryan Huff wrote:<br>
</div>
<blockquote cite="mid:COL130-W162FC2BE9C4F50EDF37931C55A0@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">Correct, ordinarily that would be what I would do
as well. In this case though, I am trying to avoid upgrading the
firmware on anything, other than the devices I am trying to get
support for.<br>
<br>
Thanks,<br>
<br>
Ryan<br>
<br>
<div>
<hr id="stopSpelling">Date: Sat, 3 Jan 2015 14:20:43 -0600<br>
From: <a class="moz-txt-link-abbreviated" href="mailto:brez@brezworks.com">brez@brezworks.com</a><br>
To: <a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
Subject: Re: [cisco-voip] Device pack installation methodology
question<br>
<br>
<div class="ecxmoz-cite-prefix">On 1/3/2015 2:11 PM, Ryan Huff
wrote:<br>
</div>
<blockquote
cite="mid:COL130-W48A39D289EC54932FB996DC55A0@phx.gbl">
<style><!--
.ExternalClass .ecxhmmessage P {
padding:0px;
}
.ExternalClass body.ecxhmmessage {
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>
</div>
</div>
</blockquote>
You shouldn't need to install the whole device pack update, just <font
face="Helvetica, Arial, sans-serif"><small>the</small> </font><span
style="color: rgb(51, 51, 51); font-family: Arial; font-size:
11px; font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: 14px; orphans: auto;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px; display: inline !important; float:
none; background-color: rgb(255, 255, 255);"><big><font
face="Helvetica, Arial, sans-serif">cmterm-88xx-sip.10-2-2-16.cop.sgn
file. That's all we did when we needed support for the 8831
conf phones. You don't need to install the whole
cmterm-devicepack file to get support for one phone, that just
makes it more convenient to get all of them upgraded at once.<br>
<br>
Jeremy "TheBrez" Bresley<br>
<a class="moz-txt-link-abbreviated" href="mailto:brez@brezworks.com">brez@brezworks.com</a><br>
</font></big></span>
</body>
</html>