The times for daylight savings in many states in Australia has been altered due to the Commonwealth Games coming to Melbourne in 2006.
In Australia, the end of the daylight savings time has been moved from the last week of March to the first week of April. The implication of this change is that instead of ending on Sunday, the 26th of March, 2006 at 3:00AM, the daylight savings time will end on Sunday, the 2nd of April, 2006 at 3:00AM. This change applies only for the year 2006.
The daylight saving times affect these Australian states:
This document discusses how the Cisco Security Monitoring, Analysis and Response System (MARS) is affected by the daylight savings time change and how to work around the issue.
There are no specific requirements for this document.
The information in this document is based on all versions of Cisco Security MARS.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Refer to Cisco Technical Tips Conventions for more information on document conventions.
Most of the major OS vendors have already released patches to avoid any problems that this daylight savings time change might cause. Customers are advised to upgrade their OS versions with these patches:
All network management applications that use the system time resources will be affected by this daylight savings change. It is highly recommended that you install these OS patches on all of your application servers in order to minimize any impact of this event.
Adjust the system times of the Cisco Security MARS to account for changes in the local time. If the system time is not adjusted, the system will run one hour ahead of the correct time in the time period between March 26th, 2006 and April 2nd, 2006. The problems include wrong time stamps in log files, reports, and display functions.
The Cisco Security MARS 4.1.5 patch resolves this issue but this patch will be posted to Cisco.com on April 10th, 2006 and a fix for this issue is required by March 26th, 2006. Contact the Cisco Technical Assistance Center (TAC) to get your appliance manually updated.
Cisco TAC can provide this service as a workaround to customers until April 10th, 2006, when the Cisco Security MARS 4.1.5 code will be released.