I have tested the latest release (4.7.2.J) and it appears that it does NOT implement the new dates for daylight savings time. So upgrade OS does not seem to be an answer. You should evaluate the impact of not having quite correct time for several weeks, and if it will have an impact then you may need to plan for manual change at the time when daylight savings moves ahead.
I had thought of that and agree that simply advancing the time an hour manually will not work with NTP configured. My theory is that if we change the selected time zone by an hour then the time used on the concentrator should be right.
A piece of good news that I heard today is that Cisco is working on new code for the VPN3000 series that will address Daylight Savings Time. They hope to have the code available by the end of February (cuttint it close).
I am not aware of any major problems of the VPN3000 changing time. It has been making the adjustment for Daylight Savings Time for quite a while with no problem that I am aware of. Now the issue is not that it would impact sessions but that it would not make the change on the correct date.
I guess that there might be some issues if the VPN3000 did not make the change on the correct date and other devices in the network did make the change, so that the concentrator was out of sync with other devices. Whether that creates a real problem would depend on the particular situation in your own network.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...