Controller-less WLANs

Time Range Profile on IAP from 4.2.1 firmware

Aruba Employee
Requirement:

How can we enable/disable a network during specific hours of day?



Solution:

Beginning with Instant 6.4.3.4-4.2.1.0 , IAP's allow  us to enable or disable an SSID for users at a particular time of the day.

This is achieved by use of time range profile on IAP.



Configuration:

In the Instant UI:-


1. Navigate to System > Show advanced options > Time Based Services.
2. Click New under Time Range Profiles. The New Profile window for creating time range profiles is displayed

We can configure both periodic and Absolute time ranges.

 

 

Periodic Time Range:

 

 

Absolute Time Range:

 

 

 

Mapping the time-range to a SSID Profile:

To apply a time range profile to a WLAN SSID in the Instant UI:


1. Navigate to the WLAN SSID profile configuration wizard (click Network>New or Network> or select the
WLAN SSID> click edit).
2. Click Show advanced options.
3. Click Edit, select a time range profile from the list and select a value from the Status drop-down list, and
then click OK

 

 

 

 

CLI:

 

Creating the time-range profile:-

18:64:72:c9:c4:9c (config) # time-range ?
<name>     profile name

18:64:72:c9:c4:9c (config) # time-range <profile name>
absolute     Absolute configuration.Start time and end time should be configured in hh:mm format
periodic     Periodic configuration.start time and end time should be configured    in hh:mm format
 

 

Eg:  Below is the snippet from running-config:

 

time-range "Disable SSID" absolute start 12/14/2015 17:00 end 12/14/2015 23:00
time-range "Enable SSID" periodic daily 08:00 to 16:59
 

Mapping the time-range profile to an SSID:

18:64:72:c9:c4:9c (config) # wlan ssid-profile <name of SSID profile>
18:64:72:c9:c4:9c (SSID Profile "Time-Range") # time-range ?
<name>     Time Range Profile Name

18:64:72:c9:c4:9c (SSID Profile "Time-Range") # time-range <name of time-range>
disable
enable

 

The keyword enable will ensure that SSID is advertised as per the time specified in time-range.

Similarly, the keyword disable will ensure that SSID is not advertised as per the time specified in time-range.

 

Note:

 

Time-based services require an active NTP server connection. IAPs use the default NTP server for time
synchronization. However, the administrators can also configure an NTP server on the IAP. To verify the
time synchronization between the NTP server and the IAP, execute the show time-range command and
check if the time on the NTP server is in synchronization with the local time.

 

 



Verification

I have configured a SSID with the name Time-Range.

 


 

 

 

Configured Time-Ranges on IAP:

 

 

Time-Range is not mapped to an SSID :-

 

 

Mapped the Time-Range with the name "Disable SSID" in order to disable the SSID:

 

 

BSS-Table post application of time-range:

 

Bss-Uptime changed post removal of Time-range:

 

Version history
Revision #:
2 of 2
Last update:
‎03-08-2016 01:14 PM
Updated by:
 
Labels (1)
Contributors
Comments
SteveW

   There seems to be a bug in the GUI in 6.4.3.4-4.2.1.0_52602 for defining Time Range Profiles only when you are defining a profile type of 'Day':

 

   The 'End Time:' minutes must be equal to or greater than the 'Start Time:' minutes.  That is, you cannot set a start time of    8:30   and an end time of   10:05   because the gui insists the end time must be after the start time?!?

 

 

    Also, I wonder about Time Profiles in relation to daylight saving time.  If I issue an 'AP Current Time' request (in the GUI), I receive similar to this:

*********************************************

  4/14/2016 11:19:16 AM   Target: IAP-205-1   Command: show clock

*********************************************

 

Current Time    :2016-04-14  10:19:16

 

---> Note the 1 hour variance in the two times displayed.  So which time is used by the time profiles applied to an SSID?

Hi Steve,

This seems to be an anamoly and engineering team is working on it. We will keep you posted once the anamoly is fixed.

It seems to be affected only on the minute hand configuration.

If the minute hand configuration for end-time is more than the minute hand under start time it is working fine.

working:

---------
Time-Based-Service.PNG

Non-working:
-----------------

Time-Based-Service1.PNG

Regards,

Sajin

 

Search Airheads
cancel
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.