Guest

Cisco Mobile Wireless Transport Manager

Field Notice: FN - 62909 - New Zealand Daylight Saving Time Policy Changes Effective September 2007 - For Mobile Wireless Transport Manager (MWTM)


September 5, 2007

NOTICE:

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.


Products Affected

Products Affected

MWTM - 5.0

 

Problem Description

The operating systems of most Cisco products that support Daylight Saving Time (DST) have built in mechanisms to automatically change the times, based on current user-selected rules. Once the new DST is implemented, the time on devices that maintain time zone information will continue to change according to the old method, unless changes are made.

Background

On April 30, 2007, the Minister of Internal Affairs issued a statement regarding a change in Daylight Saving Time policy for New Zealand. The change in policy has modified the start and end dates for Daylight Saving Time (DST). Beginning in 2007 and beyond, Daylight Saving Time in New Zealand will start on the last Sunday of September at 2:00 A.M. local time and end on the first Sunday of April at 3:00 A.M. local time.

Specifically for 2007-2008, Daylight Saving Time will begin at 2:00 A.M. local time on September 30, 2007, and end at 3:00 A.M. local time on April 6, 2008.

For more information, see the statement issued by the Minister of Internal Affairs: Daylight saving to be extended.

The old Daylight Saving Time policy dictated that DST started on the first Sunday in October and ended on the third Sunday in March.

On April 30, 2007, Hon Rick Barker, Minister of Internal Affairs, announced a three week extension to the period of daylight saving. Daylight saving now runs from the last Sunday in September until the first Sunday in April.

Table 1 Summary of changes to Daylight Savings Time, represents New Zealand local time

Event

Prior to 2007

Year 2007 and After

Start

First Sunday in October

2:00 A.M. on September 30, 2007

(Last Sunday in September)

End

Third Sunday in March

3:00 A.M.on April 6, 2008

(First Sunday in April)

 

Problem Symptoms

As a result, the system clock, any applications or log timestamps that MWTM writes to will be off by one hour after September 30, 2007.

Workaround/Solution

MWTM 6.0 does not require a fix

For MWTM 5.0 - The following steps describe how to update the Java Virtual Machine used with MWTM by applying the tzupdater utility from Sun Microsystems. If you are running a version of SGM prior to 4.1.0, then you should upgrade to 4.1 before attempting this procedure.

0) Download the updater tool from Sun: http://java.sun.com/javase/downloads/index.jsp and unzip it onto your local system.

View the readme: http://java.sun.com/javase/tzupdater_README.html.

Windows Client

1) Exit all running MWTM/SGM clients. Open an SGM/MWTM DOS prompt and change to the appropriate directory:

C:\Program Files\Cisco Systems\SGM Client\bin>cd ..\j2re\bin

Note: For MWTM, the base directory is C:\Program Files\SGM Client\bin

2) Verify that the update has not yet been applied by using the -t option:

C:\Program Files\Cisco Systems\SGM Client\j2re\bin>.\java -jar c:\tzupdater2006p\tzupdater.jar -t

/data/tzdata2006p.test:900: test failed: America/Guatemala 
/data/tzdata2006p.test:901: test failed: America/Guatemala 
... 
Validation tests failed.

Note: c:\tzupdater2006p is where you downloaded and unzipped the tzupdate.jar in step 1.

3) Apply the update with the -u option:

C:\Program Files\Cisco Systems\SGM Client\j2re\bin>.\java -jar c:\tzupdater2006p\tzupdater.jar -u

4) Verify that the update was applied correctly (you should receive no test failed messages):

C:\Program Files\Cisco Systems\SGM Client\j2re\bin>.\java -jar c:\tzupdater2006p\tzupdater.jar -t

Solaris Client

Note: After applying the tzupdater tool, commands such as Solaris pkgchk will report errors about the files altered by tzupdater. These files are under the jre/lib/zi directory. This is expected and does not indicate an error.

1) Exit all running SGM/MWTM clients. Change directories:

cd /opt/CSCOsgmClient/j2re/jre/bin

2) Verify that the update has not yet been applied by using the -t option:

./java.sgm -jar /opt/tzupdater2006p/tzupdater.jar -t

/data/tzdata2006p.test:900: test failed: America/Guatemala 
/data/tzdata2006p.test:901: test failed: America/Guatemala 
... 
Validation tests failed.

Note: /opt/tzupdater2006 is where you unzipped tzupdate.zip in step 0, and /opt/CSCOsgmClient is the location of your installed SGM/ MWTM client.

3) You must be logged in as root to apply the change. As root, apply the update with the -u option:

./java.sgm -jar /opt/tzupdater2006p/tzupdater.jar -u

4) Verify that the update was applied correctly:

./java.sgm -jar /opt/tzupdater2006p/tzupdater.jar -t

You should receive no test failed messages.

Solaris or Linux Server

Note: After applying the tzupdater tool, commands such as Solaris pkgchk will report errors about the files altered by tzupdater. These files are under the jre/lib/zi directory. This is expected and does not indicate an error.

1) Stop SGM/MWTM server processes:

/opt/CSCOsgm/bin/sgm stop cd /opt/CSCOsgm/j2re/jre/bin

2) Verify that the update has not yet been applied by using the -t option:

./java.sgm -jar /opt/tzupdater2006p/tzupdater.jar -t

/data/tzdata2006p.test:900: test failed: America/Guatemala 
/data/tzdata2006p.test:901: test failed: America/Guatemala 
... 
Validation tests failed.

Note: /opt/tzupdater2006 is where you unzipped tzupdate.zip in step 0, and /opt/CSCOsgm is the location of your installed, SGM/ MWTM server.

3) You must be logged in as root to apply the change. As root, apply the update with the -u option:

./java.sgm -jar /opt/tzupdater2006p/tzupdater.jar -u

4) Verify that the update was applied correctly:

./java.sgm -jar /opt/tzupdater2006p/tzupdater.jar -t

You should receive no test failed messages.

Revision History

Revision

Date

Comment

1.0

05-SEP-2007

Initial Public Release

 

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.