Configuring portal server detection and portal user information synchronization
Network requirements
As shown in Figure 53, a host is directly connected to a switch (the access device) and must pass portal authentication before it can access the Internet. A RADIUS server serves as the authentication/accounting server.
Detailed requirements are as follows:
The host is assigned with a public network IP address either manually or through DHCP. Before passing portal authentication, the host can access only the portal server. After passing portal authentication, the host can access the Internet.
The access device (Switch) can detect whether the portal server is reachable and send trap messages upon state changes. When the portal server is unreachable due to a connection failure, network device failure, or portal server failure, for example, the access device can disable portal authentication, allowing users to access the Internet without authentication.
The access device can synchronize portal user information with the portal server periodically.
Figure 53: Network diagram
Configuration considerations
Configure the portal server and enable portal server heartbeat function and the portal user heartbeat function.
Configure the RADIUS server to implement authentication and accounting.
Configure direct portal authentication on interface VLAN-interface 100, which is connected with the user host.
Configure the portal server detection function on the access device, so that the access device can detect the status of the portal server by cooperating with the portal server heartbeat function.
Configure the portal user information synchronization function, so that the access device can synchronize portal user information with the portal server by cooperating with the portal user heartbeat function.
Configure IP addresses for the host, switch, and servers as shown in Figure 53 and make sure that they can reach each other.
Configure the RADIUS server properly to provide authentication and accounting functions for users.
Configuring the portal server (IMC PLAT 5.0)
This example assumes that the portal server runs IMC PLAT 5.0(E0101) and IMC UAM 5.0(E0101).
# Configure the portal server.
Log in to IMC and select the Service tab. Then, select User Access Manager > Portal Service Management > Server from the navigation tree to enter the portal server configuration page, as shown in Figure 54.
Configure the portal server heartbeat interval and user heartbeat interval.
Use the default value for other parameters.
Figure 54: Portal server configuration
# Configure the IP address group.
Select User Access Manager > Portal Service Management > IP Group from the navigation tree to enter the portal IP address group configuration page. Then, click Add to enter the page shown in Figure 44.
Enter the IP group name.
Enter the start IP address and end IP address of the IP group. Make sure that the host IP address is in the IP group.
Select a service group. By default, the group Ungrouped is used.
Select the IP group type Normal.
Figure 55: Adding an IP address group
# Add a portal device.
Select User Access Manager > Portal Service Management > Device from the navigation tree to enter the portal device configuration page. Then, click Add to enter the page shown in Figure 45.
Enter the device name NAS.
Enter the IP address of the switch's interface connected to the user.
Enter the key, which must be the same as that configured on the switch.
Set whether to enable IP address reallocation. This example uses direct portal authentication, and therefore select No from the Reallocate IP list.
Set whether to support the portal server heartbeat and user heartbeat functions. In this example, select Yes for both Support Server Heartbeat and Support User Heartbeat.
Figure 56: Adding a portal device
# Associate the portal device with the IP address group.
As shown in Figure 46, click the icon in the Port Group Information Management column of device NAS to enter the port group configuration page.
Figure 57: Device list
On the port group configuration page, click Add to enter the page shown in Figure 47. Perform the following configurations:
Enter the port group name.
Select the configured IP address group. The IP address used by the user to access the network must be within this IP address group.
Use the default settings for other parameters.
Figure 58: Adding a port group
# Select User Access Manager > Service Parameters > Validate System Configuration from the navigation tree to validate the configurations.
Configure the switch
Configure a RADIUS scheme:
# Create RADIUS scheme rs1 and enter its view.
<Switch> system-view [Switch] radius scheme rs1
# Configure the server type for the RADIUS scheme. When using the IMC server, configure the RADIUS server type as extended.
[Switch-radius-rs1] server-type extended
# Specify the primary authentication server and primary accounting server, and configure the keys for communication with the servers.
[Switch-radius-rs1] primary authentication 192.168.0.112 [Switch-radius-rs1] primary accounting 192.168.0.112 [Switch-radius-rs1] key authentication simple radius [Switch-radius-rs1] key accounting simple radius
# Configure the access device to not carry the ISP domain name in the username sent to the RADIUS server.
[Switch-radius-rs1] user-name-format without-domain [Switch-radius-rs1] quit
Configure an authentication domain:
# Create ISP domain dm1 and enter its view.
[Switch] domain dm1
# Configure AAA methods for the ISP domain.
[Switch-isp-dm1] authentication portal radius-scheme rs1 [Switch-isp-dm1] authorization portal radius-scheme rs1 [Switch-isp-dm1] accounting portal radius-scheme rs1 [Switch-isp-dm1] quit
# Configure domain dm1 as the default ISP domain for all users. Then, if a user enters a username without the ISP domain at logon, the authentication and accounting methods of the default domain are used for the user.
[Switch] domain default enable dm1
Configure portal authentication:
# Configure a portal server on the switch, making sure that the IP address, port number and URL match those of the actual portal server.
[Switch] portal server newpt ip 192.168.0.111 key simple portal port 50100 url http://192.168.0.111:8080/portal
# Enable portal authentication on the interface connecting the host.
[Switch] interface vlan-interface 100 [Switch–Vlan-interface100] portal server newpt method direct [Switch–Vlan-interface100] quit
Configure the portal server detection function:
# Configure the access device to detect portal server newpt, specifying the detection method as portal heartbeat probe, setting the server probe interval to 40 seconds, and specifying the access device to send a server unreachable trap message and disable portal authentication to permit unauthenticated portal users if two consecutive probes fail.
[Switch] portal server newpt server-detect method portal-heartbeat action trap permit-all interval 40 retry 2
The product of interval and retry must be greater than or equal to the portal server heartbeat interval, and Hewlett Packard Enterprise recommends configuring the interval as a value greater than the portal server heartbeat interval configured on the portal server.
Configure portal user synchronization:
# Configure the access device to synchronize portal user information with portal server newpt, setting the synchronization probe interval to 600 seconds, and specifying the access device to log off users if the users do not appear in the user synchronization packets sent from the server in two consecutive probe intervals.
[Switch] portal server newpt user-sync interval 600 retry 2
The product of interval and retry must be greater than or equal to the portal user heartbeat interval, and Hewlett Packard Enterprise recommends configuring the interval as a value greater than the portal user heartbeat interval configured on the portal server.
Verifying the configuration
Use the following command to view information about the portal server:
<Switch> display portal server newpt
Portal server:
1)newpt:
IP : 192.168.0.111
Key : ******
Port : 50100
URL : http://192.168.0.111:8080/portal
Status : Up