In an enterprise network, different network access policies can be deployed for users on access devices to meet different network access requirements. The application of mobile office and BYOD technologies brings frequent changes of users' physical locations and IP addresses. Therefore, the original network control solution based on physical ports and IP addresses cannot ensure consistency of network access experience. For example, the network access policy of a user does not change when the user's physical location changes.
The free mobility solution allows a user to obtain the same network access policy regardless of the user's location and IP address changes.
The switches must be associated with the Agile Controller-Campus in the free mobility solution. An administrator only needs to uniformly deploy network access policies on the Agile Controller-Campus for users, and deliver the policies to all associated switches. Then, a user can obtain the same access policy no matter how the user's physical location and IP address change.
Employees in an enterprise connect to the network in wired and wireless modes and are authenticated using 802.1X or Portal authentication.
The employees do not work in fixed locations and want to obtain the same rights after being authenticated regardless of their access locations.
As shown in Figure 1, the agile core switch coreswitch functions as the authentication point and the access switch is a common switch.
You can configure 802.1X authentication and Portal authentication on the core switch so that wired and wireless users can connect to the network after being authenticated by the core switch.
The employees do not work in fixed locations and want to obtain the same rights after being authenticated regardless of their access locations.
When the controller delivers a UCL group name that is not supported by the switch, for example, this group name contains Chinese characters or special characters, the switch cannot parse the group name. A UCL group name that can be supported by the switch must be consistent with the value of group-name in the ucl-group group-index [ name group-name ] command, cannot be -, --, a, an, or any, and cannot contain any of the following characters: / \ : * ? " < > | @ ' %. Therefore, when configuring a UCL group name on the controller, do not use Chinese characters or special characters.
If the switch has been associated with an Agile Controller-Campus and has free mobility configured, perform the following steps to delete historical data and reconfigure the core switch.
Item |
Data |
Description |
|
---|---|---|---|
VLAN plan |
ID: 11 VLANIF11 IP address: 192.168.11.254/24 |
The core switch uses this VLAN to communicate with the Agile Controller-Campus. |
|
ID: 12 VLANIF12 IP address: 192.168.12.254/24 |
The core switch uses this VLAN to manage APs. |
||
ID: 13 VLANIF13 IP address: 192.168.13.254/24 |
The core switch uses this VLAN to provide wireless access services. |
||
ID: 14 VLANIF14 IP address: 192.168.14.254/24 |
The core switch uses this VLAN to provide wired access services. |
||
Core switch (coreswitch) |
Interface number: GE1/0/11 IDs of allowed VLANs: 11 |
IDs of allowed VLANs: 11, 12, 13, and 14 |
|
Interface number: GE1/0/12 IDs of allowed VLANs: 12, 14 |
This interface allows packets from the wired access service VLAN and APs' management VLAN to pass through. |
||
Access switch |
Interface number: GE0/0/1 IDs of allowed VLANs: 12, 14 |
This interface connects to GE1/0/12 on the core switch (coreswitch). |
|
Interface number: GE0/0/3 IDs of allowed VLANs: 14 |
This interface provides wired access and allows packets from the wired access service VLAN to pass through. |
||
Interface number: GE0/0/5 IDs of allowed VLANs: 12 |
This interface provides wireless access and allows packets from the APs' management VLAN to pass through. |
||
Server |
Agile Controller-Campus: 192.168.11.1 |
The Service Manager (SM) and Service Controller (SC) are installed on the same server. The SC functions as both the RADIUS server and Portal server. |
|
Email server: 192.168.11.100 |
- |
||
Video server: 192.168.11.110 |
- |
||
DNS server: 192.168.11.200 |
– |
Item |
Data |
Description |
---|---|---|
Core switch (coreswitch) |
RADIUS authentication server:
|
|
RADIUS accounting server:
|
||
Portal server:
|
||
XMPP password: Admin@123 |
The configuration is the same as that on the Agile Controller-Campus. |
|
Agile Controller-Campus |
Core switch's IP address: 192.168.11.254 |
This IP address is the IP address of VLANIF 11. |
RADIUS parameters:
|
The configuration is the same as that on the core switch. |
|
Portal parameters:
|
||
XMPP password: Admin@123 |
The configuration is the same as that on the core switch. |
|
Account: Employees:
Guests:
|
Use fast authorization to authorize the security group Employee_Group to the staff. Use fast authorization to authorize the security group Guest_Group to the guest. |
|
Security group: Employee_Group Guest_Group Email server: 192.168.11.100 Video server: 192.168.11.110 |
– |
|
Pre-authentication domain |
DNS server |
Employees can send domain names to the DNS server for resolution before being authenticated. |
Post-authentication domain |
Email servers, video server |
After passing authentication, employees can access the mail server and video server. You can improve bandwidth for employees to access the video server. After passing authentication, guests cannot access the mail server and can only access the video server. You can reduce bandwidth for guests to access the video server. |
In this example, an access switch exists between users and the core switch functioning as the authentication point, and transparently transmits packets. To ensure that users can pass 802.1X authentication, configure the access switch to transparently transmit 802.1X packets (EAP packets in this example because EAP mode is used).
<HUAWEI> system-view [HUAWEI] sysname l2switch [l2switch] l2protocol-tunnel user-defined-protocol 802.1x protocol-mac 0180-c200-0003 group-mac 0100-0000-0002 [l2switch] vlan batch 12 14 [l2switch] interface gigabitEthernet 0/0/1 [l2switch-GigabitEthernet0/0/1] port link-type trunk [l2switch-GigabitEthernet0/0/1] port trunk allow-pass vlan 12 14 [l2switch-GigabitEthernet0/0/1] l2protocol-tunnel user-defined-protocol 802.1x enable [l2switch-GigabitEthernet0/0/1] bpdu enable [l2switch-GigabitEthernet0/0/1] quit [l2switch] interface gigabitEthernet 0/0/3 //Wired access interface [l2switch-GigabitEthernet0/0/3] port link-type access [l2switch-GigabitEthernet0/0/3] port default vlan 14 [l2switch-GigabitEthernet0/0/3] l2protocol-tunnel user-defined-protocol 802.1x enable [l2switch-GigabitEthernet0/0/3] bpdu enable [l2switch-GigabitEthernet0/0/3] quit [l2switch] interface gigabitEthernet 0/0/5 //Wireless access interface [l2switch-GigabitEthernet0/0/5] port link-type access [l2switch-GigabitEthernet0/0/5] port default vlan 12 [l2switch-GigabitEthernet0/0/5] l2protocol-tunnel user-defined-protocol 802.1x enable [l2switch-GigabitEthernet0/0/5] bpdu enable [l2switch-GigabitEthernet0/0/5] quit
Choose corresponding to Core_SW to save the configuration.
Saving the configuration is similar to running the save command on the device, which saves all the device configurations (including security groups, access right control policies, and QoS policies deployed on the controller) to the configuration file.
If security groups, access right control policies, and QoS policies are saved to the device's configuration file, these configurations can be directly restored from the configuration file after the device restarts, and do not need to be requested from the controller. Otherwise, user authentication fails after the device restarts because security groups, access right control policies, and QoS policies are not deployed on the device.
After passing 802.1X or Portal authentication anywhere, the employees can access the mail and video servers, and the videos can be smoothly played.
After passing 802.1X or Portal authentication anywhere, the guests cannot access the mail server but can only access the video server, and the videos may freeze.
Core switch configuration file
# sysname coreswitch # vlan batch 11 to 14 # authentication-profile name p1 dot1x-access-profile d1 portal-access-profile web1 access-domain default force authentication-profile name p_dot1x dot1x-access-profile d1 free-rule-template default_free_rule access-domain default force authentication-profile name p_portal portal-access-profile web1 free-rule-template default_free_rule access-domain default force # group-policy controller 192.168.11.1 password %^%#(K2]5P#C6'97.pR(gFv$K$KbGYN}R1Y76~K^;AP&%^%# src-ip 192.168.11.254 # dhcp enable # radius-server template policy radius-server shared-key cipher %^%#teXm2B&.1O0:cj$OWPq7@!Y\!%}dC3Br>p,}l\L.%^%# radius-server authentication 192.168.11.1 1812 weight 80 radius-server accounting 192.168.11.1 1813 weight 80 # radius-server authorization 192.168.11.1 shared-key cipher %^%#FKIlCKv=f(AgM-G~W"}G.C\%;b'3A/zz-EJV;vi*%^%# # free-rule-template name default_free_rule free-rule 1 destination ip 192.168.11.200 mask 255.255.255.0 source ip any free-rule 2 source vlan 12 # url-template name huawei url http://192.168.11.1:8080/portal # web-auth-server policy server-ip 192.168.11.1 port 50200 shared-key cipher %^%#SQn,Cr"c;M&{#(R^:;P3F_H$3f3sr$C9%*G7R|u3%^%# url-template huawei # portal-access-profile name web1 web-auth-server policy direct # aaa authentication-scheme auth authentication-mode radius accounting-scheme acco accounting-mode radius accounting realtime 15 domain default authentication-scheme auth accounting-scheme acco radius-server policy # interface Vlanif11 ip address 192.168.11.254 255.255.255.0 # interface Vlanif12 ip address 192.168.12.254 255.255.255.0 dhcp select interface # interface Vlanif13 ip address 192.168.13.254 255.255.255.0 dhcp select interface dhcp server dns-list 192.168.11.200 # interface Vlanif14 ip address 192.168.14.254 255.255.255.0 dhcp select interface dhcp server dns-list 192.168.11.200 # interface GigabitEthernet1/0/11 port link-type trunk port trunk allow-pass vlan 11 # interface GigabitEthernet1/0/12 port link-type trunk port trunk allow-pass vlan 12 14 authentication-profile p1 # capwap source interface vlanif12 # wlan security-profile name wlan-security1 security-profile name wlan-security2 security wpa2 dot1x aes ssid-profile name dot1x_test ssid dot1x_test ssid-profile name portal_test ssid portal_test vap-profile name dot1x_test forward-mode tunnel service-vlan vlan-id 13 ssid-profile dot1x_test security-profile wlan-security2 authentication-profile p_dot1x vap-profile name portal_test forward-mode tunnel service-vlan vlan-id 13 ssid-profile portal_test security-profile wlan-security1 authentication-profile p_portal regulatory-domain-profile name domain1 ap-group name ap-group1 regulatory-domain-profile domain1 radio 0 vap-profile dot1x_test wlan 1 vap-profile portal_test wlan 2 radio 1 vap-profile dot1x_test wlan 1 vap-profile portal_test wlan 2 radio 2 vap-profile dot1x_test wlan 1 vap-profile portal_test wlan 2 ap-id 0 ap-mac 60de-4476-e360 ap-name area_1 ap-group ap-group1 wlan work-group default # dot1x-access-profile name d1 # return
Configuration file of the access switch
# sysname l2switch # vlan batch 12 14 # l2protocol-tunnel user-defined-protocol 802.1x protocol-mac 0180-c200-0003 group-mac 0100-0000-0002 # interface GigabitEthernet0/0/1 port link-type trunk port trunk allow-pass vlan 12 14 l2protocol-tunnel user-defined-protocol 802.1x enable # interface GigabitEthernet0/0/3 port link-type access port default vlan 14 l2protocol-tunnel user-defined-protocol 802.1x enable # interface GigabitEthernet0/0/5 port link-type access port default vlan 12 l2protocol-tunnel user-defined-protocol 802.1x enable # return
Switch Version |
Card or Switch Where the Authentication Control Point Can Be Deployed |
---|---|
V200R009C00 |
Only the S5720-HI supports V200R011C00. |
V200R010C00 |
|
V200R011C00, V200R011C10 |
|
V200R012C00 and later versions |
|