[cisco-voip] Device pack installation methodology question

[Tim Frazee]

Ryan,

I perform the task you describe often and depending on the customer, in
different ways.....

I would not suggest only installing a device pack on some servers.. Device
packs are meant to be installed on all nodes of the cluster. Its not a best
practice, its a great practice. All nodes get all need cop files...

The largest client I work with now we started the implementation using
lessons learned from past needs like this. The phone load is hard set at
each phone vs. leaning on the device defaults. This method works great. It
gives me ultimate granularity when it comes to who gets what load and when.

If the client wasn't deployed this way, its easy to get there. Bulk update
before you need to.

If this method doesn't flip your switch, another method I've used in the
past is to keep the device defaults page /ccmadmin page open during the
device pack install on the publisher. I usually run the cop file installs
from ssh. (faster and thinner) Once the device pack has run its course, the
device defaults page has not timed out yet. Then you comitt your
pre-device-pack parameters back to the db by hitting the save button. (can
also export the device defaults before the device pack install, then import
back in post device pack install)

The last 2 methods will work only if a phone doesnt reset/reboot after the
device pack has been installed but before you've set the device defaults
back. the first method.... it wont matter...

If all else fails... force your phones into fallback or keep them from
registering to the server by an ACL.

On Sat, Jan 3, 2015 at 2:31 PM, Ryan Huff <ryanhuff at outlook.com> wrote:

> 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.
>
> Thanks,
>
> Ryan
>
> ------------------------------
> Date: Sat, 3 Jan 2015 14:20:43 -0600
> From: brez at brezworks.com
> To: cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] Device pack installation methodology question
>
>
> On 1/3/2015 2:11 PM, Ryan Huff wrote:
>
> 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.
>
> The approach I am going to use is:
>
> 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.
>
> Does that sound reasonable or is there an easier way?
>
>
> 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.
>
> Jeremy "TheBrez" Bresley
> brez at brezworks.com
>
> _______________________________________________ cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150103/89672bc1/attachment.html>