Solved: DST OS Upgrade

pharden · ‎03-07-2007

Has anyone ran the DST OS Upgrade patch from Cisco site? I am scheduled tonight and was wondering if there are any issue and Do we need to do a reboot?

Rob Huffman · ‎03-08-2007

Hi Phillip,

Good stuff! One thing I forgot to mention was that if you are running any Java based phones (7906G,7911G,7941G,7961G,7970 or 7971) you need to do a firmware upgrade to 8.2.1.

My appologies for overlooking this (Step 2).

To obtain the complete Daylight Savings Time (DST) Update for the Operating System, Unified CallManager Cluster, and the 7906, 7911, 7921, 7941, 7961, 7970, 7971 IP phone models, you must perform the following steps in order:

1. Apply the Operating System (OS) 2000.4.2sr14, 2000.4.3aSR7, 2000.4.4sr2 or HIGHER, found here:

http://www.cisco.com/cgi-bin/tablebuild.pl/cmva-3des

2. Apply either the 8.2.1 stand-alone phone load or the device pack for this release:

8.2.1 Stand-alone phone load found here:

http://www.cisco.com/cgi-bin/tablebuild.pl/ip-7900ser

Device Pack for Unified CallManager 4.1(3), found here:

http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr-41

3. Apply the Unified CallManager Update, found here:

http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr-41

From this doc;

http://ftp-sj.cisco.com/cisco/crypto/3DES/voice/callmgr/4.1/ciscocm.4-1-3-2007-DST-Update.1-0-1-readme.htm

Hope this helps!

Rob

Please remember to rate helpful posts.....

View solution in original post

Rob Huffman · ‎03-07-2007

Hi Phillip,

We did the OS upgrade 2 weekends ago (3-4 reboots per server). The DST patch itself required 1 reboot per server. Have a look at the CCM 4.1(3) Readme;

When applying this Package be advised that a clusterwide reboot is required.

This package will install on the following Cisco CallManager versions:

4.1(3)

Step 1: Download ciscocm.4-1-3-2007-DST-Update.1-0-1.exe to the Publisher's hard drive. Make note of the location where you save the downloaded file.

Step 2: Double-click on the downloaded file to begin the installation. The install will ask if you wish to install, select yes.

Step 3: Verify that the installation completed successfully by taking the following actions:

When the system prompts you to view the log file, if the number of errors listed in the dialog is "0", you can select No.

If the number of errors detected was greater than 0, select Yes to view the log file and scroll down to the end of the log file. The errors section at the bottom of the log file will be updated with a corresponding severity.

Step 4: The Publisher will be rebooted at the completion of install. After the Publisher is back up, each server in the cluster must be rebooted in a sequential fashion, starting with the TFTP server and backup CCM Servers.

From this doc;

http://ftp-sj.cisco.com/cisco/crypto/3DES/voice/callmgr/4.1/ciscocm.4-1-3-2007-DST-Update.1-0-1-readme.htm#_Toc158448915

Everything went very well for us :) Best of luck with your changes.

Hope this helps!

Rob

pharden · ‎03-08-2007

Hey Rob

Thank you so much for your response. You have helpped me numerous times. I did as your post laid out. I only downloaded the patch to the Pub and rebooted each server in sequence.

Thnaks Again

Phillip

Rob Huffman · ‎03-08-2007

Hi Phillip,

Good stuff! One thing I forgot to mention was that if you are running any Java based phones (7906G,7911G,7941G,7961G,7970 or 7971) you need to do a firmware upgrade to 8.2.1.

My appologies for overlooking this (Step 2).

To obtain the complete Daylight Savings Time (DST) Update for the Operating System, Unified CallManager Cluster, and the 7906, 7911, 7921, 7941, 7961, 7970, 7971 IP phone models, you must perform the following steps in order:

1. Apply the Operating System (OS) 2000.4.2sr14, 2000.4.3aSR7, 2000.4.4sr2 or HIGHER, found here:

http://www.cisco.com/cgi-bin/tablebuild.pl/cmva-3des

2. Apply either the 8.2.1 stand-alone phone load or the device pack for this release:

8.2.1 Stand-alone phone load found here:

http://www.cisco.com/cgi-bin/tablebuild.pl/ip-7900ser

Device Pack for Unified CallManager 4.1(3), found here:

http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr-41

3. Apply the Unified CallManager Update, found here:

http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr-41

From this doc;

http://ftp-sj.cisco.com/cisco/crypto/3DES/voice/callmgr/4.1/ciscocm.4-1-3-2007-DST-Update.1-0-1-readme.htm

Hope this helps!

Rob

Please remember to rate helpful posts.....

tahequivoice · ‎03-08-2007

I have a question, What will happen if the only thing done is to set the DST change on the server using either tzedit, or disabling DST and manually setting the clock ahead? What will break?

Rob Huffman · ‎03-08-2007

Hi Todd,

Cisco does have a manual workaround for Callmanager (but I wouldn't use the tzedit) Have a look;

Here is what Cisco recommends;

CCM OS Manual Workaround 3.x and 4.x

On the new US DST date, Logon with sufficient privileges to CCM Windows Server (starting with Publisher)

Click Start, Settings, Control Panel, Date and Time

Adjust the time accordingly

Click on TimeZone tab

Uncheck the Automatically adjust clock for daylight savings changes

Click Apply or Ok

Repeat steps for all servers in the cluster.

When DST ends in the Fall, the clock would have to be manually adjusted again using the same method described in steps 1-3 and 6-7 above. Please note, however, that manually adjusting the clock on CCM servers could result in a conflict in time which may produce time synchronization issues.

From this doc;

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_field_notice09186a00807e02b1.shtml

Hope this helps!

Rob

tahequivoice · ‎03-08-2007

OK, so changing the time on the server manually, which is what we have planned, shouldnt affect Java on the phones, the CCM web interface, or the IPCC and Monitoring servers, as long as they are all at the same time? Reason I ask is I see a lot of different posts, both here and on other forums regarding DST changes, that Java will be affected as it doesnt use OS time, but time based on files. So basically at this point it is a wait and see if everything goes well after the time change occurs. How will this affect devices that are in other times zones? The server is CST, but there are phones and gateways in PST and EST, basically every time zone in the country.

kdamisch · ‎03-08-2007

At this link:

http://ftp-sj.cisco.com/cisco/crypto/3DES/voice/callmgr/4.2/ciscocm.4-2-3-2007-DST-Update.1-0-1-readme.htm

I noticed this in the readme file for the CCM 4.2(3) DST fix:

"This package needs to be uninstalled prior to any major upgrade."

What do they consider a major upgrade? Is it regarding the OS upgrades and/or CCM service releases?

Thanks,

Kevin

rshoker99 · ‎03-11-2007

TAC told us to do the following

1. win-OS-Upgrade-K9.2000-4-4a-sr4.exe

Operating System Upgrade Service Release

2. Upgrade firmware for your IP Phones with Device Pack 39 on your Call Manager servers.

3. Re-run the Call Manager DST 2007 1-0-1.exe update.

4. Restart your cluster.

5. Reset all your phones.

We also had to reset the Windows DST

Cisco Ip communicators require 1.4.2 version Java (we need to down grade)

Which solved problem

We did not have to edit any DB's

Rob Huffman · ‎03-12-2007

Hi Raj,

Thanks for posting back this info. Very helpful. 5 points from this end.

Thanks again,

Rob