Monitoring, Management & Location Tracking

Wrong time pushed to Cisco devices via Airwave

 

Question: I am managing my Cisco devices from Airwave. The devices use NTP to update the time. However i see a wrong time zone pushed to my device via Airwave.


Environment Information: This can happen on any version of Airwave and any supported version of Cisco device.

 

Symptoms: This happens because of a misconfiguration on the Airwave.

 

Please see the snips from Cisco device.

The current time on the Cisco device.

(arubalab-device) >show time
Time............................................. Wed Jul 16 12:32:40 2014
Timezone delta................................... -6:0   <<---- this shows that the timezone offset is -6 hours

 
Timezone location................................
NTP Servers
    NTP Polling Interval.........................     3600
     Index     NTP Key Index                  NTP Server                  NTP Msg Auth Status
    -------  ----------------------------------------------------------------------------------
       1              0                                130.160.4.10       AUTH DISABLED
 
(arubalab-device) >config time ?
 
manual         Configures the system time.
ntp            Configures the Network Time Protocol.
timezone       Configures the system's timezone.
 
(arubalab-device) >config time timezone ?
 
delta          Configures the system's timezone delta.
location       Configures the system's timezone location.
 
(arubalab-device) >config time timezone location ?
 
<location_index> Enter the timezone location index.
1. (GMT-12:00) International Date Line West
2. (GMT-11:00) Samoa
3. (GMT-10:00) Hawaii
4. (GMT -9:00) Alaska
5. (GMT -8:00) Pacific Time (US and Canada)
6. (GMT -7:00) Mountain Time (US and Canada)
7. (GMT -6:00) Central Time (US and Canada)
8. (GMT -5:00) Eastern Time (US and Canada)
9. (GMT -4:00) Altantic Time (Canada)
10. (GMT -3:00) Buenos Aires (Agentina)
11. (GMT -2:00) Mid-Atlantic
12. (GMT -1:00) Azores
13. (GMT) London, Lisbon, Dublin, Edinburgh
14. (GMT +1:00) Amsterdam, Berlin, Rome, Vienna
15. (GMT +2:00) Jerusalem
16. (GMT +3:00) Baghdad
17. (GMT +4:00) Muscat, Abu Dhabi
18. (GMT +4:30) Kabul
19. (GMT +5:00) Karachi, Islamabad, Tashkent
20. (GMT +5:30) Colombo, Kolkata, Mumbai, New Delhi
21. (GMT +5:45) Katmandu
22. (GMT +6:00) Almaty, Novosibirsk
23. (GMT +6:30) Rangoon
24. (GMT +7:00) Saigon, Hanoi, Bangkok, Jakatar
25. (GMT +8:00) HongKong, Bejing, Chongquing
26. (GMT +9:00) Tokyo, Osaka, Sapporo
27. (GMT +9:30) Darwin
28. (GMT+10:00) Sydney, Melbourne, Canberra
29. (GMT+11:00) Magadan, Solomon Is., New Caledonia
30. (GMT+12:00) Kamchatka, Marshall Is., Fiji
31. (GMT+12:00) Auckland (New Zealand)


We manually configure it on the controller.

(arubalab-device) >config time timezone location 7
 
(arubalab-device) >show time
Time............................................. Wed Jul 16 13:33:10 2014
Timezone delta................................... 0:0
Timezone location................................ (GMT -6:00) Central Time (US and Canada)
NTP Servers
    NTP Polling Interval.........................     3600
     Index     NTP Key Index                  NTP Server                  NTP Msg Auth Status
    -------  ----------------------------------------------------------------------------------
       1              0                                130.160.4.10       AUTH DISABLED
 
(arubalab-device) >show time
Time............................................. Wed Jul 16 13:34:12 2014
Timezone delta................................... 0:0
Timezone location................................ (GMT -6:00) Central Time (US and Canada)
NTP Servers
    NTP Polling Interval.........................     3600
     Index     NTP Key Index                  NTP Server                  NTP Msg Auth Status
    -------  ----------------------------------------------------------------------------------
       1              0                                130.160.4.10       AUTH DISABLED
 
(arubalab-device) >debug ntp detail enable
(arubalab-device) >debug ntp packet enable
(arubalab-device) >debug ntp low enable
 
(arubalab-device) >show debug
MAC debugging .............................. disabled
Debug Flags Enabled:
  ntp low enabled.
  ntp detail enabled.
  ntp packet enabled.
 
(arubalab-device) >show time
Time............................................. Wed Jul 16 13:35:01 2014
Timezone delta................................... 0:0
Timezone location................................ (GMT -6:00) Central Time (US and Canada)
NTP Servers
    NTP Polling Interval.........................     3600
     Index     NTP Key Index                  NTP Server                  NTP Msg Auth Status
    -------  ----------------------------------------------------------------------------------
       1              0                                130.160.4.10       AUTH DISABLED
 
(arubalab-device) >*emWeb: Jul 16 13:35:01.679: ntp Auth key Info = -1
*sntpReceiveTask: Jul 16 14:01:07.602: Initiating time sequence
*sntpReceiveTask: Jul 16 14:01:07.602: Fetching time from:130.160.4.10
*sntpReceiveTask: Jul 16 14:01:07.602: Started=3614526067.602803 2014 Jul 16 14:01:07.602
*sntpReceiveTask: Jul 16 14:01:07.602: hostname=130.160.4.10 hostIdx=1 hostNum=0
*sntpReceiveTask: Jul 16 14:01:07.602: Looking for the socket addresses
*sntpReceiveTask: Jul 16 14:01:07.602: NTP Polling cycle: accepts=0, count=5, attempts=1, retriesPerHost=6. Outgoing packet on NTP Server on socket 0:
*sntpReceiveTask: Jul 16 14:01:07.602: sta=0 ver=3 mod=3 str=15 pol=8 dis=0.000000 ref=0.000000
*sntpReceiveTask: Jul 16 14:01:07.603: ori=0.000000 rec=0.000000
*sntpReceiveTask: Jul 16 14:01:07.603: tra=3614526067.602960 cur=3614526067.602960
*sntpReceiveTask: Jul 16 14:01:07.603: 00000000: 1b 0f 08 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
*sntpReceiveTask: Jul 16 14:01:07.603: 00000010: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
*sntpReceiveTask: Jul 16 14:01:07.603: 00000020: 00 00 00 00 00 00 00 00  d7 71 4a 73 9a 5b 98 00  .........qJs.[..
*sntpReceiveTask: Jul 16 14:01:07.603: Flushing outstanding packets
*sntpReceiveTask: Jul 16 14:01:07.603: Flushed 0 packets totalling 0 bytes
*sntpReceiveTask: Jul 16 14:01:07.603: Packet of length 48 sent to ::ffff:130.160.4.10 UDPport=123
*sntpReceiveTask: Jul 16 14:01:07.604: Packet of length 48 received from ::ffff:130.160.4.10 UDPport=123
*sntpReceiveTask: Jul 16 14:01:07.604: Incoming packet on socket 0:
*sntpReceiveTask: Jul 16 14:01:07.604: 00000000: 1c 03 08 ec 00 00 01 c7  00 00 0e 28 82 cf a5 1c  ...........(....
*sntpReceiveTask: Jul 16 14:01:07.604: 00000010: d7 71 4a 4d e6 a1 25 67  d7 71 4a 73 9a 5b 98 00  .qJM..%g.qJs.[..
*sntpReceiveTask: Jul 16 14:01:07.604: 00000020: d7 71 4a 73 cf 9c 24 bb  d7 71 4a 73 cf a0 d2 57  .qJs..$..qJs...W
*sntpReceiveTask: Jul 16 14:01:07.604: sta=0 ver=3 mod=4 str=3 pol=8 dis=0.055298 ref=3614526029.900897
*sntpReceiveTask: Jul 16 14:01:07.604: ori=3614526067.602960 rec=3614526067.810976
*sntpReceiveTask: Jul 16 14:01:07.604: tra=3614526067.811048 cur=3614526067.604421
*sntpReceiveTask: Jul 16 14:01:07.604: Offset=0.207321+/-0.001390 disp=3.757034
*sntpReceiveTask: Jul 16 14:01:07.604: best=0.207321+/-0.001390
*sntpReceiveTask: Jul 16 14:01:07.604: accepts=1 rejects=0 flushes=0
*sntpReceiveTask: Jul 16 14:01:07.604: Correction: 0.207321 +/- 0.001390 disp=3.757034
*sntpReceiveTask: Jul 16 14:01:07.604: Setting clock to 2014 Jul 16 14:01:07.811 - 0.207 +/- 3.758 secs
*sntpReceiveTask: Jul 16 14:01:07.604: Times: old=(1405537267,604720) new=(1405537267,812041) adjust=(0,207321)
*sntpReceiveTask: Jul 16 14:01:07.813: time changed by 0.207 secs to 2014 Jul 16 14:01:07.813 +/- 3.757+0.001
*sntpReceiveTask: Jul 16 14:01:07.813: Stopped normally
*sntpReceiveTask: Jul 16 15:01:19.254: Initiating time sequence
*sntpReceiveTask: Jul 16 15:01:19.254: Fetching time from:130.160.4.10
*sntpReceiveTask: Jul 16 15:01:19.254: Started=3614529679.254102 2014 Jul 16 15:01:19.254
*sntpReceiveTask: Jul 16 15:01:19.254: hostname=130.160.4.10 hostIdx=1 hostNum=0
*sntpReceiveTask: Jul 16 15:01:19.254: Looking for the socket addresses
*sntpReceiveTask: Jul 16 15:01:19.254: NTP Polling cycle: accepts=0, count=5, attempts=1, retriesPerHost=6. Outgoing packet on NTP Server on socket 0:
*sntpReceiveTask: Jul 16 15:01:19.254: sta=0 ver=3 mod=3 str=15 pol=8 dis=0.000000 ref=0.000000
*sntpReceiveTask: Jul 16 15:01:19.254: ori=0.000000 rec=0.000000
*sntpReceiveTask: Jul 16 15:01:19.254: tra=3614529679.254237 cur=3614529679.254237
*sntpReceiveTask: Jul 16 15:01:19.254: 00000000: 1b 0f 08 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
*sntpReceiveTask: Jul 16 15:01:19.254: 00000010: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
*sntpReceiveTask: Jul 16 15:01:19.254: 00000020: 00 00 00 00 00 00 00 00  d7 71 58 8f 41 15 b0 00  .........qX.A...
*sntpReceiveTask: Jul 16 15:01:19.254: Flushing outstanding packets
*sntpReceiveTask: Jul 16 15:01:19.254: Flushed 0 packets totalling 0 bytes
*sntpReceiveTask: Jul 16 15:01:19.254: Packet of length 48 sent to ::ffff:130.160.4.10 UDPport=123
*sntpReceiveTask: Jul 16 15:01:19.255: Packet of length 48 received from ::ffff:130.160.4.10 UDPport=123
*sntpReceiveTask: Jul 16 15:01:19.255: Incoming packet on socket 0:
*sntpReceiveTask: Jul 16 15:01:19.256: 00000000: 1c 03 08 ec 00 00 01 b3  00 00 09 37 82 cf a5 1c  ...........7....
*sntpReceiveTask: Jul 16 15:01:19.256: 00000010: d7 71 56 aa ef 67 d1 62  d7 71 58 8f 41 15 b0 00  .qV..g.b.qX.A...
*sntpReceiveTask: Jul 16 15:01:19.256: 00000020: d7 71 58 8f 76 9b b3 46  d7 71 58 8f 76 a0 8a 48  .qX.v..F.qX.v..H
*sntpReceiveTask: Jul 16 15:01:19.256: sta=0 ver=3 mod=4 str=3 pol=8 dis=0.035995 ref=3614529194.935178
*sntpReceiveTask: Jul 16 15:01:19.256: ori=3614529679.254237 rec=3614529679.463313
*sntpReceiveTask: Jul 16 15:01:19.256: tra=3614529679.463387 cur=3614529679.256060
*sntpReceiveTask: Jul 16 15:01:19.256: Offset=0.208201+/-0.001749 disp=3.757034
*sntpReceiveTask: Jul 16 15:01:19.256: best=0.208201+/-0.001749
*sntpReceiveTask: Jul 16 15:01:19.256: accepts=1 rejects=0 flushes=0
*sntpReceiveTask: Jul 16 15:01:19.256: Correction: 0.208201 +/- 0.001749 disp=3.757034
*sntpReceiveTask: Jul 16 15:01:19.256: Setting clock to 2014 Jul 16 15:01:19.464 - 0.208 +/- 3.759 secs
*sntpReceiveTask: Jul 16 15:01:19.256: Times: old=(1405540879,256357) new=(1405540879,464558) adjust=(0,208201)
*sntpReceiveTask: Jul 16 15:01:19.465: time changed by 0.208 secs to 2014 Jul 16 15:01:19.465 +/- 3.757+0.002
 
show time
Time............................................. Wed Jul 16 15:56:35 2014
Timezone delta................................... 0:0
Timezone location................................ (GMT -6:00) Central Time (US and Canada)
NTP Servers
    NTP Polling Interval.........................     3600
 
     Index     NTP Key Index                  NTP Server                  NTP Msg Auth Status
    -------  ----------------------------------------------------------------------------------
       1              0                                130.160.4.10       AUTH DISABLED
 
(arubalab-device) >*sntpReceiveTask: Jul 16 15:01:19.465: Stopped normally
*emWeb: Jul 16 15:56:35.209: ntp Auth key Info = -1


After some time we would see the device with incorrect time zone.
 
Below is the config which we have under the Group -Basic tab of Airwave
 
One.jpg
 
 
 
We would have the below configuration under the Cisco WLC config page.
 
two.png
 
 
 
This means that we are using NTP server ( internal or external depends on the IP configured).

Under the Symptoms section we saw that Airwave is pushing delta time zone difference of 6 hours.
This value is configured as shown below.
 
three.jpg
 
So Airwave pushes a delta time zone of -6 hours.
 
Resolution: To resolve this we can change the value from -6 to 0four.jpg
 
NTP server will only sync the time which was synced properly on the controllers. However to adjust the time zone, we need to configure the UTC time zone properly.

If we have an offset value here, this same will be pushed to the devices.
Version history
Revision #:
1 of 1
Last update:
‎10-29-2014 02:03 PM
Updated by:
 
Labels (1)
Contributors
Tags (1)
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.