169
Verification
After the above configurations, perform the following command to view information about the portal
server.
<Router> display portal server newpt
Portal server:
1)newpt:
IP : 192.168.0.111
Key : portal
Port : 50100
URL : http://192.168.0.111:8080/portal
Status : Up
Cross-subnet portal authentication across VPNs
Network requirements
As shown in
, Router A, as the PE device connecting the user side, needs to provide cross-
subnet portal authentication for hosts in VPN 1 through communication with the RADIUS server and
portal server in VPN 3.
Figure 74
Network diagram for cross-subnet portal authentication across VPNs
Before enabling portal authentication, be sure to configure the MPLS L3VPN capabilities properly and
specify VPN targets for VPN 1 and VPN 3 so that VPN 1 and VPN 3 can communicate with each other.
This example gives only the access authentication configuration on the user-side PE. For information
about MPLS L3VPN, see
MPLS Configuration Guide
.
Configure the RADIUS server properly to provide normal authentication/accounting functions for users.
Configuration procedure
Configure Router A:
1.
Configure a RADIUS scheme.
# Create a RADIUS scheme named
rs1
and enter its view.
<RouterA> system-view
[RouterA] radius scheme rs1
# Configure the VPN instance to which the RADIUS scheme belongs as
vpn3
.
[RouterA-radius-rs1] vpn-instance vpn3
# Set the server type for the RADIUS scheme. When using the iMC server, you must set the server type to
extended
.
[RouterA-radius-rs1] server-type extended