A3 Online Help

Menu path: Configuration > Network Configuration > Client Parking.

An A3 installation can be responsible for a registration network with clients that stay attached for extended periods of time(for example, students that aren't able to register). These clients consume resources and generate useless load on the captive portal and registration DHCP server.

Using the client parking feature, devices can be given a longer DHCP lease and use an extremely lightweight captive portal so as to minimize resources. That captive portal displays a message explaining that they haven’t registered their clients for a certain amount of time, and will let them leave the parked state by pressing a link.

The parked vs. unparked state is controlled through one of the Security Events (1300003), which is triggered according to a threshold setting. The Grace setting in the security event controls how long the client has to register before the client is placed back in a parked state.

Note

Parking requires that A3 be your DHCP server for the registration network.

Topic	Usage	Example
Parking Lease Length	The length of time, in seconds, during which a device is left in parking.	3600
Parking Threshold	The threshold (in seconds) after which a device will be placed in parking. A value of 0 deactivates the parking detection. Detection works by measuring the time in seconds a device has been in the registration role and comparing it with this threshold.	21600
Place in DHCP Parking Group	If enabled, the device is placed in the DHCP parking group when it is parked.
Show Parking Portal	If enabled, the parking portal is shown to the device instead of the usual portal.