DescriptionOption
primary AAA server does not respond to RADIUS messages sent after
Response Window expires, the controller will forward the retransmitted RADIUS
messages to the secondary AAA server. Note that the zombie period is not
started immediately after the Response Window expires, but after the
configured Response Window plus ¼ of the configured Zombie Period. The
default Response Window is 20 seconds.
Set the time (in seconds) after which, if the AAA server does not respond to
ANY packets during the zombie period, it will be considered to inactive or
Zombie
Period
unreachable. An AAA server that is marked "zombie" (inactive or unreachable)
will be used for proxying with a low priority. If there are other live AAA servers,
the controller will attempt to use these servers first instead of the zombie AAA
server. The controller will only proxy requests to a zombie server only when
there are no other live servers. Any request that is proxied to an AAA server
will continue to be sent to that AAA server until the home server is marked
inactive or unreachable. At that point, the request will fail over to another server,
if a live AAA server is available. The default Zombie Period is 40 seconds.
Set the time (in seconds) after which, if no RADIUS messages are proxied to
the AAA server after it has been marked as inactive or unreachable, the
Revive
Interval
controller will mark the AAA server as active again (and assume that it has
become reachable again). The default Revive Interval is 120 seconds.
Click Yes to respond with a reject message to the NAS if no response is
received from the RADIUS server. Click No to skip sending a response.
No
Response
Fail
CAUTION: To ensure that the RADIUS failover mechanism functions correctly,
either accept the default values for the Response Window, Zombie Period,
and Revive Interval, or make sure that the value for Response Window is
always higher than the value for RADIUS NAS request timeout multiplied by
the value for RADIUS NAS max number of retries. For information on
configuring the RADIUS NAS request timeout and max number of retries,
see Administrator Guide. For 3rd party APs, you must ensure that the
configured Response Window on the controller is higher than the RADIUS
NAS request timeout multiplied by the RADIUS value. The maximum number
of retries is configured at 3rd party controller/ AP.
10. Configure the Rate Limiting options.
• Maximum Outstanding Requests (MOR): Set the maximum outstanding requests per
server. Type 0 to disable it, or set a value between 10 and 4096. When the MOR value is
reached, RADIUS messages are dropped and a corresponding event is triggered.
• Threshold (% of MOR): Set a percentage value of the MOR at which (when reached) the
controller will generate an event. For example, if the MOR is set to 1000 and the threshold
is set to 50%, the controller will generate an event when the number of outstanding requests
reaches 500.
SmartCell Gateway 200/Virtual SmartZone High-Scale for Release 3.4.1 Administrator Guide
393
Overview of the Captive Portal
Configuring the Captive Portal
To Next Page
Loading...
