Controller Based WLANs

Can we configure different time offset on Local controllers if NTP config is pushed from the Master?
Q:

1. Can we configure NTP servers on a local controller?

2. Can we configure different timezones for different local controllers?

 



A:

1. NTP servers configuration is pushed from the master controller. Thus we cannot configure NTP servers on the local controller.

2. We can still set different timezones for different local controller as this configuration is not pushed from the master.

For example, we have three controllers:

(7010-Master) #show switches

All Switches
------------
IP Address   Name               Location          Type     Model      Version             Status  Configuration State  Config Sync Time (sec)  Config ID
----------   ----               --------          ----     -----      -------             ------  -------------------  ----------------------  ---------
10.17.171.3  7010-Master        Building1.floor1  master   Aruba7010  6.5.0.0-beta_54788  up      UPDATE SUCCESSFUL    0                       3
10.17.171.4  Aruba7005          Building1.floor1  standby  Aruba7005  6.5.0.0-beta_54788  up      UPDATE SUCCESSFUL    8                       3
10.17.171.5  local-10.17.171.5  Building1.floor1  local    Aruba7005  6.5.0.0-beta_54788  up      UPDATE SUCCESSFUL    4                       3
Total Switches:3

 

On the master, we configure a NTP server and verify the config:

(7010-Master) (config) #ntp server 125.62.193.121 iburst
(7010-Master) (config) #write memory

(7010-Master) (config) #show ntp servers

NTP Server Table Entries
------------------------

Flags:     * Selected for synchronization
           + Included in the final selection set
           # Selected for synchronization but distance exceeds maximum
           - Discarded by the clustering algorithmn
           = mode is client

  remote                                  local                                    st   poll   reach    delay     offset      disp

=========================================================================================================================================

*125.62.193.121                           10.17.171.3                               2   64       1    0.07285     0.004868    2.81735

(7010-Master) (config) #show ntp status

Authentication:         disabled
time since restart:     10
time since reset:       10
packets received:       7
packets processed:      5
current version:        5
previous version:       0
declined:               0
access denied:          0
bad length or format:   0
bad authentication:     0
rate exceeded:          0
system peer:          125.62.193.121
system peer mode:     client
leap indicator:       00
stratum:              3
precision:            -19
root distance:        0.37376 s
root dispersion:      8.08533 s
reference ID:         [125.62.193.121]
reference time:       daf5bee4.a768d6e0  Sun, May 29 2016 11:17:56.653
system flags:         auth monitor ntp kernel stats
jitter:               0.000000 s
stability:            0.000 ppm
broadcastdelay:       0.000000 s
authdelay:            0.000000 s

(7010-Master) (config) #show ntp peer 125.62.193.121

remote ::, local ::
hmode client, pmode bclient, stratum 2, precision -20
leap 00, refid [129.6.15.29], rootdistance 0.30092, rootdispersion 0.14299
ppoll 6, hpoll 6, keyid 0, version 4, association 52333
reach 001, unreach 0, flash 0x0000, boffset 0.07236, ttl/mode 0
timer 0s, flags system_peer, config, burst, shortlist
reference time:      daf5bb1f.4170c42b  Sun, May 29 2016 11:01:51.255
originate timestamp: 00000000.00000000  Wed, Feb  6 2036 22:28:16.000
receive timestamp:   daf5beee.9f3ee8d0  Sun, May 29 2016 11:18:06.622
transmit timestamp:  daf5beee.9f3ee8d0  Sun, May 29 2016 11:18:06.622
filter delay:  0.07236  0.07288  0.07239  0.07211
               0.07257  0.07285  0.00000  0.00000
filter offset: 0.004796 0.004887 0.004941 0.004925
               0.005191 0.004868 0.000000 0.000000
filter order:  0        1        2        3
               4        5        6        7
offset 0.004796, delay 0.07236, error bound 0.43304, filter error 0.01425
remote host:          125.62.193.121
local interface:      10.17.171.3
time last received:   13s
time until next send: 44s
reachability change:  23s
packets sent:         7
packets received:     7
bad authentication:   0
bogus origin:         0
duplicate:            0
bad dispersion:       0
bad reference time:   0
candidate order:      6
flags:   system_peer, config, iburst, burst, shortlist

From the above  commands, we can see that the controller has peered with the configured ntp server and actively getting time information from it. NTP servers will only send time in UTC. It has to be converted into local time by applying appropriate offset. This can be done independently on different controllers.

Below we will configure master controller in PST and local in IST timezone and verify the configuration:

(7010-Master) #show role
switchrole:master
masterip:10.150.2.100

(7010-Master) #configure terminal
(7010-Master) (config) #clock timezone PST -8
(7010-Master) (config) #exit

(7010-Master) #show clock timezone

clock timezone PST -8

(7010-Master) #show clock

Sun May 29 11:25:35 PST 2016

 

Below, we will configure standby in IST timezone and verify the time:

(local-10.17.171.5) #show role
Switchrole:local
masterip:10.150.2.100
IKE PSK: b5479b021b31784514cbfcf30bc47fe4be26295317c8e2ca

(local-10.17.171.5) #configure t
Enter Configuration commands, one per line. End with CNTL/Z

(local-10.17.171.5) (config) #clock timezone IST -5 30
(local-10.17.171.5) (config) #exit
(local-10.17.171.5) #show clock time

clock timezone IST -5 30

(local-10.17.171.5) #show clock

Sun May 29 14:06:01 IST 2016

Version History
Revision #:
2 of 2
Last update:
‎03-24-2017 05:00 PM
Updated by:
 
Labels (1)
Contributors
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.