308
succeeds and the portal server is reachable. Otherwise, it considers that the probe fails and
the portal server is unreachable.
2. Probe parameters
{ Probe interval—Interval at which probe attempts are made.
{ Maximum number of probe attempts—Maximum number of consecutive probe attempts
allowed. If the number of consecutive probes reaches this value, the access device
considers that the portal server is unreachable.
3. Actions to be taken when the server reachability status changes (you can choose one or more)
{ Sending a trap message—When the status of a portal server changes, the access device
sends a trap message to the NMS. The trap message contains the portal server name and
the current state of the portal server.
{ Sending a log—When the status of a portal server changes, the access device sends a log
message. The log message indicates the portal server name and the current state and
original state of the portal server.
{ Disabling portal authentication (enabling portal authentication bypass)—When the
device detects that a portal server is unreachable, it disables portal authentication on the
interfaces that use the portal server (allows all portal users on the interfaces to access
network resources). When the device receives from the portal server portal heartbeat
packets or authentication packets (such as logon requests and logout requests), it
re-enables the portal authentication function.
You can configure any combination of the configuration items described as needed, with respect to
the following:
• If both detection methods are specified, a portal server is regarded as unreachable as long as
one detection method fails, and an unreachable portal server is regarded as recovered only
when both detection methods succeed.
• If multiple actions are specified, the access device executes all the specified actions when the
status of a portal server changes.
• The detection function configured for a portal server takes effect on an interface only after you
enable portal authentication and reference the portal server on the interface.
To configure the portal server detection function:
Step Command Remarks
1. Enter system view.
system-view
N/A
2. Configure the portal
server detection
function.
portal server
server-name
server-detect method
{
http
|
portal-heartbeat
} *
action
{
log
|
permit-all
|
trap
} *
[
interval
interval ]
[
retry
retries ]
Not configured by default.
The portal server specified in the
command must exist.
The portal heartbeat detection method works only when the portal server supports the portal server
heartbeat function. Only the IMC portal server supports the portal server heartbeat function. To
implement detection with this method, you also need to configure the portal server heartbeat function
on the IMC portal server and make sure that the product of interval and retry is greater than or equal
to the portal server heartbeat interval. Hewlett Packard Enterprise recommends configuring the
interval to be greater than the portal server heartbeat interval configured on the portal server.
Configuring portal user information synchronization
Only Layer 3 portal authentication supports this feature.
Once the device loses communication with a portal server, the portal user information on the device
and that on the portal server might be inconsistent after the communication resumes. To solve this
To Next Page
Loading...
Need help?
General
