wlan-switch enable

Usage Scenario

By default, when a WLAN user roams between different APs, the user needs to be re-authenticated for login after being logged out, which causes services to be interrupted. To prevent a service interruption, run the wlan-switch enable command to enable WLAN user roaming switchover on a BAS interface. The NetEngine 8000 F then updates user access information and keeps users online upon receiving packets sent by the WLAN users to trigger roaming procedures.

After WLAN user roaming switchover is enabled on a BAS interface, you need to configure the interface to use received user packets to trigger roaming procedures for WLAN users. Perform the following configurations based on the actual roaming scenarios:

• If users do not pass through Wi-Fi blind spots when roaming between different APs, run either the ip-trigger or arp-trigger command or both to configure the interface to trigger roaming procedures for the WLAN users based on the received IP or ARP packets, or run the ipv6?trigger command to configure the interface to trigger roaming procedures for Layer 2 IPv6 users based on the received IPv6 packets.
• If users pass through Wi-Fi blind spots when roaming between different APs, run the dhcp session-mismatch action roam { ipv4 | ipv6 | nd } * command to configure the interface to allow users to send DHCPv4 Discover or Request messages or DHCPv6 Solicit messages or ND RS messagesto re-log in.
  NOTE:
• The dhcp session-mismatch action roam { ipv4 | ipv6 | nd } * and dhcp session-mismatch action offline commands override one another. If the two commands are run on the same interface, the command run later takes effect.
• The dhcp session-mismatch action roam { ipv4 | ipv6 } * command can be configured together with the ip-trigger, the arp-trigger and the ipv6-trigger commands.
  To control the range of interfaces for roaming switchover, you can specify a switching group after enabling WLAN user switchover on a BAS interface, so that WLAN user roaming switchover is performed between interfaces of the specified roaming switchover group.

Precautions

This command is supported only on the admin VS.

The wlan-switch enable command cannot be run together with the access session-group-template or remote-backup-profile command on the same interface.

WLAN user roaming switchover and one-to-many mappings between one MAC address and multiple sessions are mutually exclusive and therefore cannot be configured on the same interface.

The same MAC address must be configured for the BAS main interface (including GE main interface and Eth-Trunk main interface) before and after the switchover. If different MAC addresses are configured, the IP/ARP packet to trigger WLAN roaming cannot be received on the BAS interface after the switchover is performed, which means that roaming cannot be triggered.

Users roaming between different interfaces can be IPoE users (excluding static users with proactive detection, static users with the same MAC address but different IP addresses, and all leased line users).

The wlan-switch enable and dhcp lease-proxy commands are mutually exclusive.

If the parameter switch-group-name is specified, the parameter settings on different BRAS interfaces must be the same for handovers during WLAN user roaming. If they are consistent, handovers during WLAN user roaming are not allowed.

Roaming between different types of interfaces is not allowed.

The roaming function applies only to GE and Trunk interfaces, but not VE interfaces or PW-VE interfaces.

UP hot backup and wlan user roaming are mutually exclusive. When the backup-group { <master-interface-type> <master-interface-num> | <master-interface-name> } { <slave-interface-type> <slave-interface-num> | <slave-interface-name> } configuration is performed for hot backup, respectively, check whether the wlan-switch enable [ switch-group <switch-group-name> ] configuration exists on the master and slave interfaces or their sub-interfaces. If such configuration exists, the configuration cannot be performed. In the BAS view of a roaming interface, when the wlan-switch enable [ switch-group <switch-group-name> ] configuration is performed, check whether the main interface or its sub-interface is configured as the master or slave interface for hot backup. If such configuration exists, the configuration cannot be performed.

UP warm backup or load balancing and wlan user roaming are mutually exclusive. When the master interface { <interface-type> <interface-num> | <interface-name> } and slave interface { <interface-type> <interface-num> | <interface-name> } configurations are performed for warm backup or load balancing, respectively, check whether the wlan-switch enable [ switch-group <switch-group-name> ] configuration exists on the master or slave interfaces or their sub-interfaces. If such configuration exists, the configuration cannot be performed. In the BAS view of a roaming interface, when the wlan-switch enable [ switch-group <switch-group-name> ] configuration is performed, check whether the main interface is configured as the master or slave interface for warm backup or load balancing. If such configuration exists, the configuration cannot be performed.