[cisco-voip] Device pack installation methodology question

[Leslie Meade]

I'd also recommend this way as well. A whole lot easier

Leslie


From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Matthew Collins
Sent: Monday, January 05, 2015 1:38 AM
To: Ryan Huff; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Device pack installation methodology question

Hi Ryan,

I have just installed the device pack on the publisher first. Then changed the device defaults back to their originals, Then reboot the publisher, TFTP and subs in turn. No need to mess around with the CM groups.

One tip I got from the forum a couple of years ago when installing device pack was to open the device defaults page in IE, Then install the device pack using another browser Firefox or chrome, once the device pack is installed go back to the IE page without refreshing and select save, This will then revert all the firmware version back to the pre device pack state, Saves having to manually change each one back.


Regards

Matthew


From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Huff
Sent: 03 January 2015 20:12
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] Device pack installation methodology question

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?

Thanks,

Ryan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150106/4fc25b35/attachment.html>