[c-nsp] DST change on catos 6500

[Jared Mauch]

	Is there a reason why you don't just swap your device to UTC
to avoid all these issues?  Seems to be an easy "fix" and if you ever have
a network 'event' during this timeframe will be easier to debug.

	Avoids all the flash filesystem bugs related to DST that i've had
them fix over the years as well.  (where the timestamp on the file will
"change" every spring/fall).

	- Jared

On Wed, Mar 07, 2007 at 01:01:55PM -0500, dalton wrote:
> 
> Hi,
> Just want to clarify this change for catos side of things.
> For the new DST change (EST zone)
> 
> 6500 currently has:
> 
> set timezone EST5EDT -5 0
> set summertime enable EST5EDT
> 
> What I am going to implement per cisco docs is:
> 
> set summertime recurring second Sunday March 02:00 first Sunday November 02:00
> -----
> Question is, do I need to specify an offset at the end of this of 60?
> 
> In the ios example, it does not specify offset, but catos does.
> 
> "In order to comply with the 2007 DST time change, use this command on any device that runs Cisco CatOS release 5.4 and later:
> 
>     set summertime enable EDT 
>     set summertime recurring second Sunday March 02:00 first Sunday November 02:00 60 
> "
> 
> -thanks
> 
> 
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

-- 
Jared Mauch  | pgp key available via finger from jared at puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.