cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5642
Views
0
Helpful
6
Replies

NTP and Timezones (GMT not correct)

Hello,

i have a question about the Timezone settings in the WLCs.

We have serveral systems: 2100, 2500, 4400, 5500 series.

Problem occurs at firmware 7.0.98.0, 7.0.220.0, 7.0.240.0, 7.4.100.0

So i think this issue is not firmware or modelbased.

I have configured connection to NTP-server (windows).

The WLCs are getting the actual time from the server (when i change the time manually it's getting corrected, so it's working)

When the WLC is at default config and got the time from the NTP-Server at the location in the commands --> set time menu is set to -Select Location- the time is correct at UTC/GMT.

Delta is 0 0

When i change to location GMT+1 (Berlin, Amsterdam) the time is shown also correct (GMT+2 since we at daylight savings at the moment).

But we want to change all systems to have UTC/GMT timezone.

When i change the timezone back to GMT, it just gets back 1 hour (to GMT+1 instead of GMT).

What do i have to do to get the controller back to 'real GMT'.

For Example:

Time: UTC 9:15 AM

Timezone:

Time shown on WLC: 9:15 AM

--> correct

Time: UTC 9:15 AM

Timezone: GMT +1 (Berlin, Amsterdam)

Time shown on WLC: 11:15 AM

--> correct (since we are at daylight savings)

Time: UTC 9:15 AM

Timezone: GMT

Time shown on WLC: 10:15 AM

--> incorrect (looks like he tinks we have daylight savings at GMT Timezone).

Even after reboot no change

(Controller) >show time           

Time............................................. Wed Sep 18 13:05:40 2013

Timezone delta................................... 0:0

Timezone location................................ (GMT +1:00) Amsterdam, Berlin, Rome, Vienna

NTP Servers

    NTP Polling Interval.........................     3600

     Index     NTP Key Index     NTP Server      NTP Msg Auth Status

    -------  ---------------------------------------------------------------

       1              0         10.96.75.77       AUTH DISABLED

(Controller) >show time

Time............................................. Wed Sep 18 12:05:53 2013

Timezone delta................................... 0:0

Timezone location................................ (GMT) London, Lisbon, Dublin, Edinburgh

NTP Servers

    NTP Polling Interval.........................     3600

     Index     NTP Key Index     NTP Server      NTP Msg Auth Status

    -------  ---------------------------------------------------------------

       1              0         10.96.75.77       AUTH DISABLED

(Controller) >

Maybe anyone can help me with this.

Thanks and Regards,

Gregor

6 Replies 6

Scott Fella
Hall of Fame
Hall of Fame

What I usually do is set the time and delta manually to the correct time, then I set NTP. If the time is off there, then I just trick the WLC and set it +1 or -1 to get it to the correct time.

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***

Hello Scott,

well, this would be the workaround if there is no 'real' solution for this, but some configuration for 32 controllers (even with prime i can't do this with templates).

I can't belive that the controllers for some reason don't know how to handle the NTP and timezone settings correctly ...

I just hope it doesn't change the time when the daylight savings ends and you have to make this settings twice a year.

Regards,

Gregor

Well this has always been an issue and maybe I should of said that in my original post. Will time differ again with DST, probably. I just notice that time has to be close as possible before you use NTP as if the time is too far off, the WLC will not adjust.

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***

I have configured connection to NTP-server (windows).

This is your issue.

Windows and NTP/SNTP ... They don't mix or don't work well.  You need to find an alternative source to synchronize NTP but don't use Windows.

Windows use Windows-based NTP and they are totally different to the NTP/SNTP standards.

Sadly Windows isn't the source of the issue.

I tried two unix timeservers as well and same result.

All other systems, Junipers, Cisco Switches, Checkpoint Firewalls, OpNet Appliances are working correctly with this servers.

Ok, I didn't read your thread properly. 

I'll do what Scott has posted, I use the "Delta" option to +1 or -1 hour.

Review Cisco Networking for a $25 gift card