[cisco-voip] Firmware Update

Tue May 26 15:20:17 EDT 2009

Sure.

Updating 5.1.2 1000-11 to 5.1.2 3114-1. Its and Engineering Special Cisco says we need to fix bugs and add the 7975 device to the usable phone list that we currently don't have.

The file I have downloaded is a tar.gz

________________________________
From: Wes Sisk [mailto:wsisk at cisco.com]
Sent: Tuesday, May 26, 2009 2:12 PM
To: Darren Ducote
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Firmware Update

Hi Darren,

You will need to be bit more explicit here.

Most "OS Updates" on the appliance (cm5.x and later) come in the form of ".cop.sgn" files. These files patch the current active partition and do not involve the inactive partition.

If you upgrade to a Mainline version (6.1 to 7.0), upgrade to a maintenance release (7.0.1 to 7.0.2), upgrade to a service update (7.0.1 to 7.0.1.11002-4 or "SU1a") or upgrade to an engineering special (7.0.2.20000-5 or "7.0(2a)" to 7.0.2.21010-2) then then upgrade will install to the inactive partition, migrate your data, and require reboot to switch partitions.  If this is completed in proper order (publisher, tftp, backup subscribers, active subscribers) then phones *should* attempt to upgrade automatically.  This may fail if:
1. cm6.x or later and replication to TFTP server is still in progress when phones reboot
2. tftp server is still rebuilding configuration files when phones reboot
3. some phones will fail if tftp processing allocation is exceeed.  this is likely to happen with large numbers of phones (2000+ attempting concurrent upgrade) or if phones are across a WAN from CUCM.  WAN causes the TFTP process to take much longer. This in turn keeps TFTP threads tied up for extended periods of time.  The phone peer to peer firmware sharing feature is intended to counter this process.  Using "load server" on the phone configuration page can also counter this.

There are perfmon counters in RTMT for Cisco TFTP to identify these conditions.

If a failure does occur most admins have the best success with reseting phones one device pool at a time to allow phones to upgrade.  This is assuming your phones are divided into device pools of less than ~1000 phones each.

Regards,
Wes

On Tuesday, May 26, 2009 2:23:45 PM, Darren Ducote <ducotedt at stfran.com><mailto:ducotedt at stfran.com> wrote:

When I install an OS/Engineering update and reboot to the inactive partition, do the phones try and download the new firmware after the swing back over to the subscriber or do I have to manually update that for each device?

In other words I am worried that all the phones will try to do a TFTP firmware update after installing the updated OS. Thanks!

________________________________
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

***St. Francis Medical Center and affiliates encrypt email containing Patient Health Information. You will receive a notice with instructions on how to open any encrypted email you receive. To learn more about this click Here<http://userawareness.zixcorp.com/sites/index.php?b=141&type=1>

________________________________

_______________________________________________

cisco-voip mailing list

cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>

https://puck.nether.net/mailman/listinfo/cisco-voip

________________________________
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

***St. Francis Medical Center and affiliates encrypt email containing Patient Health Information.  You will receive a notice with instructions on how to open any encrypted email you receive.  To learn more, go to this web site: http://userawareness.zixcorp.com/sites/index.php?b=141&type=1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090526/993ccf5b/attachment.html>