Guest

Cisco SCE 1000 Series Service Control Engine

Field Notice: FN - 62641 - SCE - U.S. Daylight Savings Time Policy Changes Effective March 2007 for SCE


March 2, 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

SCE 1010 SCOS - 2.5.10

SCE 1010 SCOS - 2.5.5

SCE 1010 SCOS - 2.5.6

SCE 1010 SCOS - 2.5.7

SCE 1010 SCOS - 2.5.8

SCE 1010 SCOS - 2.5.9

SCE 1010 SCOS - 3.0.0

SCE 1010 SCOS - 3.0.1

SCE 1010 SCOS - 3.0.3

SCE 1010 SCOS - 3.0.4

SCE 1010 SCOS - 3.0.5

SCE 2020 SCOS - 2.5.10

SCE 2020 SCOS - 2.5.5

SCE 2020 SCOS - 2.5.6

SCE 2020 SCOS - 2.5.7

SCE 2020 SCOS - 2.5.8

SCE 2020 SCOS - 2.5.9

SCE 2020 SCOS - 3.0.0

SCE 2020 SCOS - 3.0.1

SCE 2020 SCOS - 3.0.3

SCE 2020 SCOS - 3.0.4

SCE 2020 SCOS - 3.0.5

SCE SCAS BB - 2.5.10

SCE SCAS BB - 2.5.5

SCE SCAS BB - 2.5.6

SCE SCAS BB - 2.5.7

SCE SCAS BB - 2.5.8

SCE SCAS BB - 2.5.9

SCE SCAS BB - 3.0.0

SCE SCAS BB - 3.0.1

SCE SCAS BB - 3.0.3

SCE SCAS BB - 3.0.4

SCE SCAS BB - 3.0.5

SCE SCAS BB - 3.0.5A

SCE SCMS CM - 2.5.5 (BUNDLED LINUX)

SCE SCMS CM - 2.5.5(BUNDLED SOLAR)

SCE SCMS CM - 2.5.5(NOT BND LINUX)

SCE SCMS CM - 2.5.5(NOT BND SOLAR)

SCE SCMS CM - 2.5.8(BUNDLED LINUX)

SCE SCMS CM - 2.5.8(BUNDLED SOLAR)

SCE SCMS CM - 2.5.8(NOT BND LINUX)

SCE SCMS CM - 2.5.8(NOT BND SOLAR)

SCE SCMS CM - 3.0.0 (BUNDLED)

SCE SCMS CM - 3.0.0 (NOT BUNDLED)

SCE SCMS CM - 3.0.3 (BUNDLED)

SCE SCMS CM - 3.0.3 (NOT BUNDLED)

SCE SCMS CM - 3.0.4 (BUNDLED)

SCE SCMS CM - 3.0.4 (NOT BUNDLED)

SCE SCMS CM - 3.0.5

SCE SCMS SM - 2.5.10

SCE SCMS SM - 2.5.5

SCE SCMS SM - 2.5.6

SCE SCMS SM - 2.5.7

SCE SCMS SM - 2.5.8

SCE SCMS SM - 2.5.9

SCE SCMS SM - 3.0.0

SCE SCMS SM - 3.0.1

SCE SCMS SM - 3.0.3

SCE SCMS SM - 3.0.4

SCE SCMS SM - 3.0.5

Problem Description

Several countries around the world have changed their Daylight Saving Time (DST) dates and their time zone definitions lately, or are about to change it. Specifically, as of spring 2007, DST start and end dates for the United States will transition to comply with the U.S. Energy Policy Act of 2005. DST dates in the United States will start three weeks earlier (2:00 A.M. on the second Sunday of March) and will end one week later (2:00 A.M. on the first Sunday of November).

Cisco Service Control solution components - the SCE OS, the SCA BB Console, the SM and the CM - which were not updated with the new DST dates, would be one hour off, possibly causing incorrect enforcement of time-based policies, reporting and logging.

For systems that are not located in affected countries, no action should be taken, and this field notice may be disregarded for these systems.

Background

Cisco Service Control solution components depend on correct time management for correct enforcement of time-based policies, reporting and logging.

The SCE OS (SCOS)

The SCOS can be configured to automatically switch to DST on a specified date, and also to switch back to standard time. The transition times into and out of DST may be configured as recurring, if DST always begins and ends on the same day every year, as in the United States, using the clock summer-time recurring command. For this command, the default values are the United States transition rules. The impact of the DST change in the United States is that these default values are no longer correct.

The SCA BB, SM and CM:

The SCA BB, SM and CM depend on the time management that is performed by their underlying Java Runtime Environment (JRE). The impact of the DST change in the United States is that the JRE, if not updated, would be one hour off, thereby causing the solution components to be one hour off as well. This JRE needs to be updated for each of the components in order to accommodate the new DST dates.

Problem Symptoms

The SCOS, the SCA BB Console, the SM and the CM, which were not updated with the new DST dates, would be one hour off, possibly causing incorrect enforcement of time-based policies, reporting and logging, as detailed in the following sections.

The SCE OS (SCOS)

-Incorrect time-based policy enforcement

-Incorrect timestamps in raw data records (RDRs)

-Incorrect time display

-Incorrect timestamps in logs

The SCA BB Console and Reporter

-Incorrect times in reports in the Reporter

-Incorrect time display

-Incorrect timestamps in system logs

The Subscriber Manager (SM)

-Incorrect quota aggregation period enforcement by the Quota Manager

-Incorrect time display (for example in subscriber's lease expiry time, and in SCE connection establishment time)

-Incorrect timestamps in logs

The Collection Manager (CM)

-Incorrect timestamps in records

-Incorrect timing of daily topper/aggregator operations

-Incorrect timestamps in logs

Workaround/Solution

Future releases of the SCOS, SCA BB, SM and CM will include the required adjustments for the DST changes. For existing releases, DST adjustments should be performed manually, as described in the following sections:

In addition to the procedure described below, the operating systems (Windows, Solaris or Linux), where the SCA BB Console, the SM and the CM are running, must also be updated to accommodate the DST changes. For more information about patches to these operating systems, see the References section below.

-Adjusting the DST on the SCOS:

The clock summer-time CLI command is used to adjust the DST on the SCE. Use the following command to adjust the SCE to the new DST dates:

SCE(config)#clock summer-time DST recurring 2 Sunday March 02:00 1 Sunday November 02:00

Verify the change by displaying the current summer-time settings. Note that in this example, the SCE is in the PST time zone:

SCE#show timezone
Time zone: PST. Minutes offset from UTC: -480
summer-time zone name is DST, offset from local time is 60 minutes.
Summer time starts 02:00:00 PST SUN March 11 2007
Summer time ends 02:00:00 DST SUN November 4 2007

For further information about managing DST on the SCE, please refer to the Cisco SCE Software Configuration Guide.

-Adjusting the DST for the SCA BB Console:

DST is adjusted on the SCA BB Console by updating the underlying JRE. This process requires stopping and restarting the SCA BB Console GUI.

The 'tzupdater' is a tool provided by Sun, to allow the updating of installed JRE images with more recent timezone data in order to accommodate the U.S. 2007 DST changes. This tool provides a way to update timezone data while leaving other system configuration and dependencies unchanged.

For more complete background information, see the References section below.

-Installation:

Download the tool bundle archive tzupdater-tzdata2006n-b01.zip from the Sun Java SE Download site.

Note that Sun's Download site requires registration.

Unzip the content of the archive to a directory on the machine where the SCA BB Console is running.

-Usage:

The tool's command-line interface is as follows.

<"java.exe"> -jar tzupdater.jar <"options">

The Java.exe part should point to the same "java.exe" file that is used by the SCA BB Console, which is located at the Console's installation tree, under the 'jre/bin' directory. For example, in version 3.0.5, with the default installation location, this maps to:

"C:Program FilesCisco SCASSCAS BB Console 3.0.5jrebinjava.exe"

The tool's command-line options are:

-u, --update Update the time zone data.

-t, --test Runs verification tests only and exit.

-v, --verbose Display detailed messages.

Additional options are described in the tool's README file.

The following example shows how to use the tool, after it was extracted to the "C:\temp\tzupdater2006p" directory, in order to adjust the JRE of the SCA BB Console 3.0.5 to the new DST dates. The SCA BB Console GUI should be closed before running this command:

C:\temp\tzupdater2006p>"C:Program FilesCisco SCASSCAS BB Console 3.0.5jrebinjava.exe" -jar tzupdater.jar --update --verbose" 
java.home: C:\Program Files\Cisco SCAS\SCAS BB Console 3.0.5\jre 
java.vendor: Sun Microsystems Inc. 
java.version: 1.5.0_02 
JRE time zone data version: tzdata2003d 
Embedded time zone data version: tzdata2006p 
Extracting files... done. 
Renaming directories... done. 
Validating the new time zone data... done. 
Time zone data update is complete. 

Verifying the change:

C:\temp\tzupdater2006p>"C:Program FilesCisco SCASSCAS BB Console 3.0.5jrebinjava.exe" -jar tzupdater.jar --test --verbose" 
java.home: C:\Program Files\Cisco SCAS\SCAS BB Console 3.0.5\jre 
java.vendor: Sun Microsystems Inc. 
java.version: 1.5.0_02 
JRE time zone data version: tzdata2006p 
Embedded time zone data version: tzdata2006p 
Validating the time zone data 
Validation complete 

The JRE for the SCA BB Console is now updated with the new DST settings.

-Adjusting the DST for the SM and the CM:

As with the SCA BB Console, DST is adjusted on the SM and the CM by updating the underlying JRE, using Sun's 'tzupdater' tool. This process should be done separately for every SM and CM in the system, and requires stopping and restarting the SM and the CM.

-Installation:

As with the SCA BB Console, download the tool bundle archive from the Sun Java SE download site, and unzip the content of the archive to a directory on the machines where the SM and the CM are running.

-Usage:

The tool's command-line interface is as follows.

<"java"> -jar tzupdater.jar <"options">

The "Java" part should point to the same "java" file that is used by the SM or the CM.

On the SM, this file is located under the "~/j2re1.4.2_05/" directory of the 'pcube' account.

On the CM, this file is located under the "~/cm/lib/j2re1.4.2_03" directory on Solaris, and the "~/cm/lib/j2re1.4.2_04" directory on Linux, of the 'pcube' or 'scmscm' accounts.

The following example shows how to use the tool, after it was extracted to the "/tmp/tzupdater2006p" directory, in order to adjust the JRE of the SM and CM to the new DST dates.

-bash-2.05b$ ~/j2re1.4.2_05/bin/java -jar /tmp/tzupdater.jar --update --verbose 
java.home: ~/j2re1.4.2_05/ 
java.vendor: Sun Microsystems Inc. 
java.version: 1.4.2_05 
JRE time zone data version: tzdata2003d 
Embedded time zone data version: tzdata2006p 
Extracting files... done. 
Renaming directories... done. 
Validating the new time zone data... done. 
Time zone data update is complete. 

Verifying the change:

C:\temp\tzupdater2006p~/j2re1.4.2_05/bin/java -jar /tmp/tzupdater.jar --test --verbose 
java.home: ~/j2re1.4.2_05/ 
java.vendor: Sun Microsystems Inc. 
java.version: 1.4.2_05 
JRE time zone data version: tzdata2006p 
Embedded time zone data version: tzdata2006p 
Validating the time zone data 
Validation complete 

The JRE for the SM and CM is now updated with the new DST settings. The SM and CM should be restarted after running this update procedure.

References:

-Sun Java

(1) Sun Java - U.S. Daylight Savings Time Changes in 2007

(2) JDK - US DST timezone 1.0.1 - Sun Java SE TZupdater Tool

-Sun Solaris

(3)Sun Solaris Alert Notification: Daylight Savings Time (DST) Changes for Australia (2006), United States (2007) and Others

-Microsoft Windows

(4) Microsoft Windows - Daylight Saving Time Help and Support Center

(5) 2007 time zone update for Microsoft Windows operating systems

-Red Hat Linux

(6) Red Hat Linux: The glibc enhancement update adjusts timezone files for USA and other countries

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.

DDTS

Description

CSCsh24223 (registered customers only)

Accomodate with US Daylight policy change.

CSCsh20257 (registered customers only)

Accomodate with US Daylight policy change.

CSCsh20253 (registered customers only)

Accomodate with US Daylight policy change.

CSCsh20239 (registered customers only)

Accomodate with US Daylight policy change.

Revision History

Revision

Date

Comment

1.0

 

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.