Re: [cisco-voip] Device pack installation methodology question

2015-01-07 Thread Matthew Loraditch 
So to not look like a complete nut, this may have been sitting in my outbox on 
my laptop for several days...
Doh!


Matthew G. Loraditch - CCNP-Voice, CCNA, CCDA

1965 Greenspring Drive
Timonium, MD 21093

voice. 410.252.8830
fax.  410.252.9284

Twitter<http://twitter.com/heliontech>  |  
Facebook<http://www.facebook.com/#!/pages/Helion/252157915296>  | 
Website<http://www.heliontechnologies.com/>  |  Email 
Support<mailto:supp...@heliontechnologies.com?subject=Technical%20Support%20Request>


From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of 
Matthew Loraditch
Sent: Wednesday, January 07, 2015 6:04 AM
To: Ryan Huff; Jeremy Bresley; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Device pack installation methodology question

I believe it works like this:
The firmware updates immediately upon device package install, but isn't 
available until TFTP is restarted. The device defaults are updated as well. 
Just go into device defaults before you restart (since you do have to do a full 
restart for new device models to work) and change the settings back to your 
older versions.

Now the thing I am wondering is if any of the newer http enhancements to 
downloads change things with respect to firmware availability, but even then 
you'd still only have a few minute window between the install completing and 
you changing the fields back to what they were. I guess it really matters what 
your root concern with the other firmware is as to whether there is an 
acceptable risk where a few phones might upgrade and have to revert.


Matthew G. Loraditch - CCNP-Voice, CCNA, CCDA

1965 Greenspring Drive
Timonium, MD 21093

voice. 410.252.8830
fax.  410.252.9284

Twitter<http://twitter.com/heliontech>  |  
Facebook<http://www.facebook.com/#!/pages/Helion/252157915296>  | 
Website<http://www.heliontechnologies.com/>  |  Email 
Support<mailto:supp...@heliontechnologies.com?subject=Technical%20Support%20Request>


From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ryan 
Huff
Sent: Saturday, January 03, 2015 3:31 PM
To: Jeremy Bresley; 
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] Device pack installation methodology question

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: b...@brezworks.com<mailto:b...@brezworks.com>
To: cisco-voip@puck.nether.net<mailto:cisco-voip@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
b...@brezworks.com<mailto:b...@brezworks.com>

___ cisco-voip mailing list 
cisco-voip@puck.nether.net<mailto: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

Re: [cisco-voip] Device pack installation methodology question

2015-01-07 Thread Matthew Loraditch 
I believe it works like this:
The firmware updates immediately upon device package install, but isn't 
available until TFTP is restarted. The device defaults are updated as well. 
Just go into device defaults before you restart (since you do have to do a full 
restart for new device models to work) and change the settings back to your 
older versions.

Now the thing I am wondering is if any of the newer http enhancements to 
downloads change things with respect to firmware availability, but even then 
you'd still only have a few minute window between the install completing and 
you changing the fields back to what they were. I guess it really matters what 
your root concern with the other firmware is as to whether there is an 
acceptable risk where a few phones might upgrade and have to revert.


Matthew G. Loraditch - CCNP-Voice, CCNA, CCDA

1965 Greenspring Drive
Timonium, MD 21093

voice. 410.252.8830
fax.  410.252.9284

Twitter<http://twitter.com/heliontech>  |  
Facebook<http://www.facebook.com/#!/pages/Helion/252157915296>  | 
Website<http://www.heliontechnologies.com/>  |  Email 
Support<mailto:supp...@heliontechnologies.com?subject=Technical%20Support%20Request>


From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ryan 
Huff
Sent: Saturday, January 03, 2015 3:31 PM
To: Jeremy Bresley; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Device pack installation methodology question

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: b...@brezworks.com<mailto:b...@brezworks.com>
To: cisco-voip@puck.nether.net<mailto:cisco-voip@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
b...@brezworks.com<mailto:b...@brezworks.com>

___ cisco-voip mailing list 
cisco-voip@puck.nether.net<mailto: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

Re: [cisco-voip] Device pack installation methodology question

2015-01-06 Thread Josh Warcop 
Gotcha! I'm a big fan of assigning the phone firmware on the device and not 
relying on device defaults. Reboot the servers in the middle of the day! It is 
redundant right? :-)

From: Anthony Holloway<mailto:avholloway+cisco-v...@gmail.com>
Sent: ‎1/‎6/‎2015 12:48 PM
To: Josh Warcop<mailto:j...@warcop.com>; Dave 
Goodwin<mailto:dave.good...@december.net>
Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] Device pack installation methodology question

Josh,

You have to reboot the server to add the new phone types to the UI.  If
you're simply adding firmware updates via Device Pack, then only restart
TFTP.

On Tue Jan 06 2015 at 10:57:29 AM Josh Warcop  wrote:

>  #1 Use BAT to apply specific firmware loads to the phone configuration
> and not rely on device defaults.
> #2 Install COP and restart TFTP
> #3 Why reboot the server?
>
> Sent from my Windows Phone
>  --
> From: Anthony Holloway 
> Sent: ‎1/‎6/‎2015 11:51 AM
> To: Dave Goodwin 
> Cc: cisco-voip@puck.nether.net
> Subject: Re: [cisco-voip] Device pack installation methodology question
>
>  Dave,
>
>  You're definitely going to want to use BAT Export/Import instead of
> screenshots or copy paste.  Look at this small example:
>
>  On the top, this is the default layout of the web page and we cannot see
> the full firmware filename.  On the bottom, I have manipulated the HTML DOM
> to increase the size of the text input fields to show you the hidden
> portion.
>
>   In short, BAT Export/Import eliminates typing and thus typos, and it's
> faster.
>
> On Tue Jan 06 2015 at 9:17:45 AM Dave Goodwin 
> wrote:
>
> What I have done in some past upgrades is to copy/paste everything on
> Device Defaults page (or screen shot it). Deactivate TFTP service on all
> nodes - so it can't even start following any necessary reboots. Install the
> upgrade. Go back to Device Defaults page and set everything back how you
> like it. Activate TFTP service on all nodes where you had previously
> deactivated it.
>
>  HTH,
> Dave
>
>
>
> On Saturday, January 3, 2015, Ryan Huff  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: b...@brezworks.com
> To: cisco-voip@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
> b...@brezworks.com
>
> ___ 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
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Device pack installation methodology question

2015-01-06 Thread Anthony Holloway 
Josh,

You have to reboot the server to add the new phone types to the UI.  If
you're simply adding firmware updates via Device Pack, then only restart
TFTP.

On Tue Jan 06 2015 at 10:57:29 AM Josh Warcop  wrote:

>  #1 Use BAT to apply specific firmware loads to the phone configuration
> and not rely on device defaults.
> #2 Install COP and restart TFTP
> #3 Why reboot the server?
>
> Sent from my Windows Phone
>  --
> From: Anthony Holloway 
> Sent: ‎1/‎6/‎2015 11:51 AM
> To: Dave Goodwin 
> Cc: cisco-voip@puck.nether.net
> Subject: Re: [cisco-voip] Device pack installation methodology question
>
>  Dave,
>
>  You're definitely going to want to use BAT Export/Import instead of
> screenshots or copy paste.  Look at this small example:
>
>  On the top, this is the default layout of the web page and we cannot see
> the full firmware filename.  On the bottom, I have manipulated the HTML DOM
> to increase the size of the text input fields to show you the hidden
> portion.
>
>   In short, BAT Export/Import eliminates typing and thus typos, and it's
> faster.
>
> On Tue Jan 06 2015 at 9:17:45 AM Dave Goodwin 
> wrote:
>
> What I have done in some past upgrades is to copy/paste everything on
> Device Defaults page (or screen shot it). Deactivate TFTP service on all
> nodes - so it can't even start following any necessary reboots. Install the
> upgrade. Go back to Device Defaults page and set everything back how you
> like it. Activate TFTP service on all nodes where you had previously
> deactivated it.
>
>  HTH,
> Dave
>
>
>
> On Saturday, January 3, 2015, Ryan Huff  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: b...@brezworks.com
> To: cisco-voip@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
> b...@brezworks.com
>
> ___ 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
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Device pack installation methodology question

2015-01-06 Thread Ryan Ratliff (rratliff) 
TFTP won't serve up any new files until the service is restarted so just take a 
screenshot (or open a browser window to the device defaults page and keep it 
handy) so you can change the loads back after the devpack install is done but 
before you reboot.

-Ryan

On Jan 3, 2015, at 3:31 PM, Ryan Huff 
mailto:ryanh...@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: b...@brezworks.com<mailto:b...@brezworks.com>
To: cisco-voip@puck.nether.net<mailto:cisco-voip@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
b...@brezworks.com<mailto:b...@brezworks.com>

___ cisco-voip mailing list 
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> 
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto: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

Re: [cisco-voip] Device pack installation methodology question

2015-01-06 Thread Andy 
You could BAT update your existing handsets with the firmware you want them to 
run (in the Device\Phone\Phone Load Name).
Then assuming the firmware is currently on the TFTP servers it wouldn’t matter 
what device packs you install your handsets will always run the code you want 
them to.
It makes migrations easier to manage and gives you better control day to day, 
without having to remember that you might need to change the Pub config back to 
a previous version if you don’t want it globally role out.

Andy
andy.ca...@gmail.com



> On 3 Jan 2015, at 20:31, Ryan Huff  wrote:
> Device
> 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: b...@brezworks.com
> To: cisco-voip@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
> b...@brezworks.com <mailto:b...@brezworks.com>
> 
> ___ 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 <mailto:cisco-voip@puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip 
> <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

Re: [cisco-voip] Device pack installation methodology question

2015-01-06 Thread Josh Warcop 
#1 Use BAT to apply specific firmware loads to the phone configuration and not 
rely on device defaults.
#2 Install COP and restart TFTP
#3 Why reboot the server?

Sent from my Windows Phone

From: Anthony Holloway<mailto:avholloway+cisco-v...@gmail.com>
Sent: ‎1/‎6/‎2015 11:51 AM
To: Dave Goodwin<mailto:dave.good...@december.net>
Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] Device pack installation methodology question

Dave,

You're definitely going to want to use BAT Export/Import instead of
screenshots or copy paste.  Look at this small example:

On the top, this is the default layout of the web page and we cannot see
the full firmware filename.  On the bottom, I have manipulated the HTML DOM
to increase the size of the text input fields to show you the hidden
portion.

In short, BAT Export/Import eliminates typing and thus typos, and it's
faster.

On Tue Jan 06 2015 at 9:17:45 AM Dave Goodwin 
wrote:

> What I have done in some past upgrades is to copy/paste everything on
> Device Defaults page (or screen shot it). Deactivate TFTP service on all
> nodes - so it can't even start following any necessary reboots. Install the
> upgrade. Go back to Device Defaults page and set everything back how you
> like it. Activate TFTP service on all nodes where you had previously
> deactivated it.
>
> HTH,
> Dave
>
>
> On Saturday, January 3, 2015, Ryan Huff  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: b...@brezworks.com
>> To: cisco-voip@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
>> b...@brezworks.com
>>
>> ___ 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
>
___
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

Re: [cisco-voip] Device pack installation methodology question

2015-01-06 Thread Leslie Meade 
I'd also recommend this way as well. A whole lot easier

Leslie


From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of 
Matthew Collins
Sent: Monday, January 05, 2015 1:38 AM
To: Ryan Huff; cisco-voip@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-boun...@puck.nether.net] On Behalf Of Ryan 
Huff
Sent: 03 January 2015 20:12
To: cisco-voip@puck.nether.net<mailto:cisco-voip@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
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Device pack installation methodology question

2015-01-06 Thread 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  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: b...@brezworks.com
> To: cisco-voip@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
> b...@brezworks.com
>
> ___ 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
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Device pack installation methodology question

2015-01-06 Thread Anthony Holloway 
Dave,

You're definitely going to want to use BAT Export/Import instead of
screenshots or copy paste.  Look at this small example:

On the top, this is the default layout of the web page and we cannot see
the full firmware filename.  On the bottom, I have manipulated the HTML DOM
to increase the size of the text input fields to show you the hidden
portion.

In short, BAT Export/Import eliminates typing and thus typos, and it's
faster.

On Tue Jan 06 2015 at 9:17:45 AM Dave Goodwin 
wrote:

> What I have done in some past upgrades is to copy/paste everything on
> Device Defaults page (or screen shot it). Deactivate TFTP service on all
> nodes - so it can't even start following any necessary reboots. Install the
> upgrade. Go back to Device Defaults page and set everything back how you
> like it. Activate TFTP service on all nodes where you had previously
> deactivated it.
>
> HTH,
> Dave
>
>
> On Saturday, January 3, 2015, Ryan Huff  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: b...@brezworks.com
>> To: cisco-voip@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
>> b...@brezworks.com
>>
>> ___ 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
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Device pack installation methodology question

2015-01-06 Thread Brian Meade 
What I do is save the Device Defaults page as HTML then install the device
packs on all nodes.  I then go back to the Device Defaults page and set
everything back to what I saved in the HTML file.  I then do the cluster
reboot.

That keeps any other phone models from upgrading and allows me to get
support for the new device.

Brian

On Sat, Jan 3, 2015 at 3:31 PM, Ryan Huff  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: b...@brezworks.com
> To: cisco-voip@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
> b...@brezworks.com
>
> ___ 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
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Device pack installation methodology question

2015-01-06 Thread Mehtab Shinwari 
What we do is pretty simple actually and we have done this numerous times:


1)  Take a screenshot of the device defaults

2)  Install the device pack on the PUB

3)  This will change other defaults, go ahead and change them back

4)  Install the device pack on the sub(s)

5)  Verify the defaults are the same and have not changed

6)  Reboot the cluster

Simple just follow these steps and you will be fine.

Best of Luck Ryan.

Regards


Mehtab Shinwari | CCNP-V/RS, VCP-DCV
Senior Support Engineer - Team Lead
7am-7pm | Fri-Sun

+1-212-616-7859 office
+1-212-616-7850 fax

www.fidelus.com

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ryan 
Huff
Sent: Saturday, January 03, 2015 3:12 PM
To: cisco-voip@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


___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Device pack installation methodology question

2015-01-06 Thread Tim Smith 
Hi guys,

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)
Then you can do your changes on pub with less impact.

Cheers,

Tim.

From: Jeremy Bresley mailto:b...@brezworks.com>>
Date: Sunday, 4 January 2015 07:20
To: "cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>" 
mailto:cisco-voip@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
b...@brezworks.com<mailto:b...@brezworks.com>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Device pack installation methodology question

2015-01-06 Thread Dave Goodwin 
What I have done in some past upgrades is to copy/paste everything on
Device Defaults page (or screen shot it). Deactivate TFTP service on all
nodes - so it can't even start following any necessary reboots. Install the
upgrade. Go back to Device Defaults page and set everything back how you
like it. Activate TFTP service on all nodes where you had previously
deactivated it.

HTH,
Dave

On Saturday, January 3, 2015, Ryan Huff  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: b...@brezworks.com
> 
> To: cisco-voip@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
> b...@brezworks.com 
>
> ___ 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

Re: [cisco-voip] Device pack installation methodology question

2015-01-06 Thread Erick Bergquist 
Install the device pack on all the nodes, starting with the publisher.

Set the device defaults back to what you want.

Reboot the nodes one at a time, starting with the publisher.

As long as the network and phones are stable and not rebooting/etc
frequently they won't take a new load until you reboot.
You could always stop the TFTP service I suppose for a bit to.


On Sat, Jan 3, 2015 at 2:31 PM, Ryan Huff  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: b...@brezworks.com
> To: cisco-voip@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
> b...@brezworks.com
>
> ___ 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
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Device pack installation methodology question

2015-01-06 Thread Techguy 
Approach makes sense, though I see requirement of phones resets as the cm
group is modified to one node instead of two, otherwise phones will stay or
keep registering to pub as it's available. (and sub in the second round).

TG
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Device pack installation methodology question

2015-01-06 Thread Matthew Collins 
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-boun...@puck.nether.net] On Behalf Of Ryan 
Huff
Sent: 03 January 2015 20:12
To: cisco-voip@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
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Device pack installation methodology question

2015-01-06 Thread James Andrewartha 
On 04/01/15 04:31, Ryan Huff 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.

I came across
http://amyengineer.com/2014/03/04/voice-basics-upgrading-firmware-for-specific-phone-models/
a while ago. It only covers installing a single phone cop, not a whole
device pack though.

-- 
James Andrewartha
Network & Projects Engineer
Christ Church Grammar School
Claremont, Western Australia
Ph. (08) 9442 1757
Mob. 0424 160 877
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Device pack installation methodology question

2015-01-06 Thread Ryan Huff 
I like that approach - seems simpler, does mean running the phones without 
valid tftp for a few (ringtones, phone desktops, corp. directory ...) but 
that's what maintenance windows are for.

Thanks for your time!

Thanks,

Ryan

From: avholloway+cisco-v...@gmail.com
Date: Sat, 3 Jan 2015 20:58:09 +
Subject: Re: [cisco-voip] Device pack installation methodology question
To: ryanh...@outlook.com; cisco-voip@puck.nether.net

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 nodes2. BAT Export the Device Defaults3. Install the 
Dev Pack on Pub4. Restart Pub5. Install Dev Pack on Sub6. Restart Sub7. BAT 
Import the Device Defaults8. Activate TFTP on both nodes9. 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  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

Re: [cisco-voip] Device pack installation methodology question

2015-01-06 Thread Terry Cheema 
The easiest way I have found is using imort/export function to keep the 
firmware same. The below steps should do:
1) Export the device defaults
2) Install the cop file on the pub and the subsequent nodes (after the 
installation is complete loads will be updated)
3) Import the device defaults to revert back to previous firmware.
4) Once confirmed the loads are same as per the original - Reload the servers 
one at a time.

-Terry


Sent from my iPhone

> On 4 Jan 2015, at 7:31 am, Ryan Huff  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: b...@brezworks.com
> To: cisco-voip@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
> b...@brezworks.com
> 
> ___ 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
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Device pack installation methodology question

2015-01-06 Thread Anthony Holloway 
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  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

Re: [cisco-voip] Device pack installation methodology question

2015-01-06 Thread Jeremy Bresley 

On 1/3/2015 2:31 PM, Ryan Huff 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: b...@brezworks.com
To: cisco-voip@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.


You shouldn't need to install the whole device pack update, just the 
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.


Jeremy "TheBrez" Bresley
b...@brezworks.com
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Device pack installation methodology question

2015-01-03 Thread Ryan Huff 
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: b...@brezworks.com
To: cisco-voip@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

b...@brezworks.com

  


___
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

Re: [cisco-voip] Device pack installation methodology question

2015-01-03 Thread Jeremy Bresley 

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
b...@brezworks.com
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip