HP 4800G Series Configuration Manual page 1290

For re-DHCP authentication, you need to configure a public address pool (20.20.20.0/24, in this
example) and a private address pool (10.0.0.0/24, in this example) on the DHCP server. The
configuration steps are omitted. For DHCP configuration information, refer to DHCP Configuration
in the IP Services Volume.
For re-DHCP authentication, the switch must be configured as a DHCP relay agent (instead of a
DHCP server) and the portal-enabled interface must be configured with a primary IP address (a
public IP address) and a secondary IP address (a private IP address).
You need to configure IP addresses for the devices as shown in
are available between devices.
Perform configurations on the RADIUS server to ensure that the user authentication and
accounting functions can work normally.
Configure the switch:
1) Configure a RADIUS scheme
# Create a RADIUS scheme named rs1 and enter its view.
<Switch> system-view
[Switch] radius scheme rs1
# Set the server type for the RADIUS scheme. When using the iMC server, you need set the server type
to 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.113
[Switch-radius-rs1] primary accounting 192.168.0.113
[Switch-radius-rs1] key authentication radius
[Switch-radius-rs1] key accounting radius
# Specify that the ISP domain name should not be included in the username sent to the RADIUS server.
[Switch-radius-rs1] user-name-format without-domain
[Switch-radius-rs1] quit
2) Configure an authentication domain
# Create an ISP domain named dm1 and enter its view.
[Switch] domain dm1
# Configure the ISP domain to use RADIUS scheme rs1.
[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 dm1 as the default ISP domain for all users. Then, if a user enters the username without the
ISP domain at login, the authentication and accounting methods of the default domain will be used for
the user.
Figure 1-10
1-16
and ensure that routes