H3C Technologies H3C Intelligent Management Center - Manual (Page 334)

316
{
IP Address—IPv4 or IPv6 address of the portal device.
{
Listening Port—Port number to which UAM listens for portal packets sent from the portal server.
The value defaults to 2000.
{
Local Challenge—Value Yes indicates that the portal device can create local challenge in CHAP
authentication. The value No indicates that the portal server sends challenge requests to the
portal server in CHAP authentication. UAM does not support local challenge values on portal
devices, and the value must be No.
{
Authentication Retries—Number of authentication requests that the portal server re-sends to the
portal device when a request timed out. The portal server considers a request timeout occurs if
it cannot receive a reply from the portal device within a specified period of time after the request
was sent.
{
Logout Retries—Number of logout requests that the portal server re-sends to the portal device
when a request timed out. The portal server considers a request timeout occurs if it cannot
receive a reply from the portal device within a specified period of time after the request was sent.
{
Support Server Heartbeat—Whether or not UAM enables server heartbeat for the portal device.
For more information, see "
Configuring UAM as the portal server ."
− The portal server sends a server heartbeat packet to the portal device at certain intervals
(specified by the Server Heartbeat Interval parameter). If receiving no server heartbeat
packet within an interval, the portal device considers the portal server failed and changes
the authentication mode to the fail-open mode. In the fail-open mode, the portal device
allows all users to access the Internet without authentication.
− If the portal device receives a server heartbeat packet in the fail-open mode, the device
considers that the portal server recovers and restores to the authentication mode.
This function is effective only when it is enabled on both the portal server and the portal device.
To enable server heartbeat on the portal server, select Yes for Support Server Heartbeat on the
page for adding or modifying a portal device in UAM and configure server heartbeat at the
CLI on the portal device. The commands for enabling server heartbeat on a portal device vary
with the portal device model.
{
Support User Heartbeat—Whether or not UAM enables user heartbeat for the portal device. For
more information, see "
Configuring UAM as the portal server ."
− User heartbeat packets are used for maintaining user status on the portal server and portal
device. The portal server sends a user heartbeat packet to the portal device at certain
intervals (specified by the User Heartbeat Interval parameter). Users that exist on both the
server and the access device can keep online, whereas other users are logged out. This
function is effective only when it is enabled on both the portal server and the portal device.
− To enable user heartbeat on the portal server, select Yes for Support User Heartbeat on the
page for adding or modifying a portal device in UAM and configure user heartbeat at CLI
on the portal device. The commands for enabling user heartbeat on a portal device vary
with the portal device model.
{
Key—Key used for the portal device and UAM to authenticate each other.
{
Access Method—Can be Directly Connected, Layer 3, or Reallocate IP. Directly Connected
indicates that no Layer 3 devices exist between the portal device and endpoint users. Layer 3
indicates that Layer 3 devices exist between the portal device and endpoint users. Reallocate IP
indicates that IP address reallocation is enabled on the portal device.
{
DHCP Request Retransmit Delay—Appears only when the Access Method parameter is
Reallocate IP. When a user passes portal authentication and obtains a public IP address, it
notifies the portal server of the successful IP address acquisition. The value of this parameter is