I just did this recently too, to add support for an 8831 on an 8x cluster. Trying to recall from memory, here's what I recall doing:
1. Deactivate TFTP on both nodes 2. BAT Export the Device Defaults 3. Install the Dev Pack on Pub 4. Restart Pub 5. Install Dev Pack on Sub 6. Restart Sub 7. BAT Import the Device Defaults 8. Activate TFTP on both nodes 9. Add new 8831's For step 7, I also did a BAT export of device defaults post dev pack, and ran a diff on the two. I saw the changes to the existing phone firmware as well as the addition of the new phone models. When you import the old device defaults back in at this stage, note that the absence of the new phone models simply tells CUCM BAT process to ignore them and leave them alone, while reverting the firmware changes on all of the existing phones. On Sat Jan 03 2015 at 2:15:25 PM Ryan Huff <ryanh...@outlook.com> 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? > > Thanks, > > Ryan > _______________________________________________ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-voip >
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
