Example: Configuring portal server detection and portal user synchronization

Network configuration

As shown in Figure 71, the host is directly connected to the switch (the access device). The host is assigned a public IP address either manually or through DHCP. A portal server acts as both a portal authentication server and a portal Web server. A RADIUS server acts as the authentication/accounting server.

Configure direct portal authentication on the switch, so the host can access only the portal server before passing the authentication and access other network resources after passing the authentication.
Configure the switch to detect the reachability state of the portal authentication server, send log messages upon state changes, and disable portal authentication when the authentication server is unreachable.
Configure the switch to synchronize portal user information with the portal server periodically.

Figure 71: Network diagram

Prerequisites

Configure IP addresses for the switch and servers as shown in Figure 71 and make sure the host, switch, and servers can reach each other.
Configure the RADIUS server correctly to provide authentication and accounting functions.

Configuring the portal authentication server on IMC PLAT 3.20

In this example, the portal server runs on IMC PLAT 3.20-R2602P13 and IMC UAM 3.60-E6301.

Configure the portal authentication server:
1. Log in to IMC and click the Service tab.
2. Select Access Service > Portal Service Management > Server from the navigation tree to open the portal server configuration page, as shown in Figure 72.
3. Configure the portal server heartbeat interval and user heartbeat interval.
4. Use the default settings for other parameters.
5. Click OK.
Figure 72: Portal authentication server configuration
Configure the IP address group:
1. Select Access Service > Portal Service Management > IP Group from the navigation tree to open the portal IP address group configuration page.
2. Click Add to open the page as shown in Figure 73.
3. Enter the IP group name.
4. Enter the start IP address and end IP address of the IP group.
  Make sure the host IP address (2.2.2.2) is in the IP group.
5. Select a service group.
  This example uses the default group Ungrouped.
6. Select the action Normal.
7. Click OK.
Figure 73: Adding an IP address group
Add a portal device:
1. Select Access Service > Portal Service Management > Device from the navigation tree to open the portal device configuration page.
2. Click Add to open the page as shown in Figure 74.
3. Enter the device name NAS.
4. Enter the IP address of the switch's interface connected to the host.
5. Enter the key, which must be the same as that configured on the switch.
6. Set whether to enable IP address reallocation.
  This example uses direct portal authentication, and therefore select No from the Reallocate IP list.
7. 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.
8. Click OK.
Figure 74: Adding a portal device
Associate the portal device with the IP address group:
1. As shown in Figure 75, click the icon in the Port Group Information Management column of device NAS to open the port group configuration page.
  Figure 75: Device list
2. Click Add to open the page as shown in Figure 76.
  Figure 76: Port group configuration
3. Enter the port group name.
4. Select the configured IP address group.
  The IP address used by the user to access the network must be within this IP address group.
5. User default values for other parameters.
6. Click OK.
Select Access Service > Service Parameters > Validate System Configuration from the navigation tree to validate the configurations.

Configuring the portal authentication server on IMC PLAT 5.0

In this example, the portal server runs on IMC PLAT 5.0(E0101) and IMC UAM 5.0(E0101).

Configure the portal authentication server:
1. Log in to IMC and click the Service tab.
2. Select User Access Manager > Portal Service Management > Server from the navigation tree to open the portal server configuration page, as shown in Figure 77.
3. Configure the portal server heartbeat interval and user heartbeat interval.
4. Use the default settings for other parameters.
5. Click OK.
Figure 77: Portal authentication server configuration
Configure the IP address group:
1. Select User Access Manager > Portal Service Management > IP Group from the navigation tree to open the portal IP address group configuration page.
2. Click Add to open the page as shown in Figure 78.
3. Enter the IP group name.
4. Enter the start IP address and end IP address of the IP group.
  Make sure the host IP address is in the IP group.
5. Select a service group.
  This example uses the default group Ungrouped.
6. Select the action Normal.
7. Click OK.
Figure 78: Adding an IP address group
Add a portal device:
1. Select User Access Manager > Portal Service Management > Device from the navigation tree to open the portal device configuration page.
2. Click Add to open the page as shown in Figure 79.
3. Enter the device name NAS.
4. Enter the IP address of the switch's interface connected to the host.
5. Enter the key, which must be the same as that configured on the switch.
6. Set whether to enable IP address reallocation.
  This example uses direct portal authentication, and therefore select No from the Reallocate IP list.
7. Select whether to support server heartbeat and user heartbeat functions.
  In this example, select Yes for both Support Server Heartbeat and Support User Heartbeat.
8. Click OK.
Figure 79: Adding a portal device
Associate the portal device with the IP address group:
1. As shown in Figure 80, click the icon in the Port Group Information Management column of device NAS to open the port group configuration page.
2. Click Add to open the page as shown in Figure 81.
3. Enter the port group name.
4. Select the configured IP address group.
  The IP address used by the user to access the network must be within this IP address group.
5. Use the default settings for other parameters.
6. Click OK.
Figure 80: Device list
Figure 81: Adding a port group
Select User Access Manager > Service Parameters > Validate System Configuration from the navigation tree to validate the configurations.

Configuring the switch

Configure a RADIUS scheme:

# Create a RADIUS scheme named rs1 and enter its view.

<Switch> system-view
[Switch] radius scheme rs1

# 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

# Exclude the ISP domain name from the username sent to the RADIUS server.

[Switch-radius-rs1] user-name-format without-domain
[Switch-radius-rs1] quit

# Enable RADIUS session control.

[Switch] radius session-control enable

Configure an authentication domain:
# Create an ISP domain named 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. If a user enters the username without the ISP domain name at login, 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 authentication server.
```
[Switch] portal server newpt
[Switch-portal-server-newpt] ip 192.168.0.111 key simple portal
[Switch-portal-server-newpt] port 50100
```
# Configure reachability detection of the portal authentication server: set the server detection interval to 40 seconds, and send log messages upon reachability status changes.
```
[Switch-portal-server-newpt] server-detect timeout 40 log
```
NOTE:
The value of timeout must be greater than or equal to the portal server heartbeat interval.
# Configure portal user synchronization with the portal authentication server, and set the synchronization detection interval to 600 seconds.
```
[Switch-portal-server-newpt] user-sync timeout 600
[Switch-portal-server-newpt] quit
```
NOTE:
The value of timeout must be greater than or equal to the portal user heartbeat interval.
# Configure a portal Web server.
```
[Switch] portal web-server newpt
[Switch-portal-websvr-newpt] url http://192.168.0.111:8080/portal
[Switch-portal-websvr-newpt] quit
```
# Enable direct portal authentication on VLAN-interface 100.
```
[Switch] interface vlan-interface 100
[Switch–Vlan-interface100] portal enable method direct
```
# Enable portal fail-permit for the portal authentication server newpt.
```
[Switch–Vlan-interface100] portal fail-permit server newpt
```
# Specify portal Web server newpt on VLAN-interface 100.
```
[Switch–Vlan-interface100] portal apply web-server newpt
```
# Configure the BAS-IP as 2.2.2.1 for portal packets sent from VLAN-interface 100 to the portal authentication server.
```
[Switch–Vlan-interface100] portal bas-ip 2.2.2.1
[Switch–Vlan-interface100] quit
```

Verifying the configuration

# Use the following command to display information about the portal authentication server.

[Switch] display portal server newpt
Portal server: newpt
  Type                  : IMC
  IP                    : 192.168.0.111
  VPN instance          : Not configured
  Port                  : 50100
  Server Detection      : Timeout 40s  Action: log
  User synchronization  : Timeout 600s
  Status                : Up

The Up status of the portal authentication server indicates that the portal authentication server is reachable. If the access device detects that the portal authentication server is unreachable, the Status field in the command output displays Down. The access device generates a server unreachable log "Portal server newpt turns down from up." and disables portal authentication on the access interface, so the host can access the external network without authentication.

prev	up	next
Example: Configuring extended cross-subnet portal authentication	home	Example: Configuring cross-subnet portal authentication for MPLS L3VPNs