LAN-Side Site Configuration
Before installing cloud-managed devices are installed, you need to configure device functions on iMaster NCE-Campus in offline mode. After cloud-managed devices are installed and connect to iMaster NCE-Campus, iMaster NCE-Campus will automatically deliver service parameters to the devices. This implements device plug-and-play.
- Configuring an Interface Template
- Configuring General Functions at a Site
- Configuring AP Services
- Configuring AR Services
- Configuring Switch Services
- Configuring a Subnet
- Configuring Physical Interfaces
- Configuring a Loopback Interface
- Configuring a Static Route
- Configuring OSPF
- Configuring OSPF on an Interface
- Configuring a Fit AP
- Configuring Static MAC Limit
- Configuring Authentication
- Configuring STP
- Configuring Attack Defenses
- Configuring Voice STA OUI
- Configuring Device VLANs
- Configuring a DNS Server
- Configuring Free Mobility
- Configuring a Traffic Policy (QoS)
- Checking CIS Interworking Information
- Configuring Firewall Services
- Configuring WAC Services
- Saving Configurations and Verifying Configuration Delivery Results
Configuring an Interface Template
Context
iMaster NCE-Campus can deliver an interface template to switch interfaces at different sites for configuration. This improves the configuration efficiency.
Procedure (Interface Security)
- Choose from the main menu.
- On the Feature Deployment tab page, select Security.
- Click Create to create an interface security template.
A port security template defines general configurations of switch interface security.
Procedure (Ring Network)
- Choose from the main menu.
- On the Feature Deployment tab page, select Ring Network.
- Click Create to create an interface ring network template.
A port ring network template is used to configure loop detection on a switch interface.
Procedure (VLAN)
- Choose .
- On the Feature Deployment tab page, select VLAN.
- Click Create to create an interface VLAN template.
A VLAN template defines the VLANs allowed on a switch interface.
Procedure (Physical Attribute)
- Choose .
- On the Feature Deployment tab page, select Interface Physical Attributes.
- Click Create to create an interface physical attribute template.
A port physical attribute template defines the interface rate and duplex mode of a switch interface.
Procedure (Interface Traffic Policy)
- Choose .
- On the Feature Deployment tab page, select Interface Traffic Policy.
- Click Create to create an interface traffic policy.
An interface traffic policy template configures a traffic policy for a single switch interface or multiple switch interfaces in batches.
Port traffic policies take precedence over the policies for outgoing and incoming traffic that are globally enabled.
Procedure (Device Traffic Policy)
- Choose .
- On the Feature Deployment tab page, select Device Traffic Policy.
- Click Create to create a device traffic policy.
A maximum of 1000 device traffic policies and 256 traffic policies can be configured. A maximum of 256 rules can be configured in a traffic policy.
Procedure (Object Group)
- Choose .
- On the Object Group tab page, create interface and device object groups.
- On the Interface tab page, click Create, set the object group name, select mode, and click Add to add an interface to the object group.
Switch interfaces at different sites with the same configuration can be grouped together in an object group. This facilitates iMaster NCE-Campus to deliver unified configuration to the ports in each object group.
- On the Device tab page, click Create, set the object group name, and click Add to add a device to the object group.
Devices at different sites with the same configuration can be grouped together in an object group. This facilitates iMaster NCE-Campus to deliver unified configuration to the devices in each object group.
- Interfaces and devices can be filtered by site.
- A maximum of 100 object groups can be created.
- An object group can contain at most 2000 devices or interfaces.
- When the Device Model mode is selected, the interface object group cannot be added to a stack switch, modular switch, or card on a switch.
- On the Interface tab page, click Create, set the object group name, select mode, and click Add to add an interface to the object group.
Procedure (Configuration Delivery)
- Choose from the main menu.
- On the Feature Deployment tab page, click
next to a configured template under an interface category to deliver configuration to specific interfaces.
During configuration delivery, you can create an object group or select a created object group. Then, iMaster NCE-Campus delivers the same configuration to the objects in the selected object group.
- Click OK
Parameter Description
Parameter |
Description |
---|---|
Template name |
Name of an interface security template. |
DHCP snooping |
Whether to enable DHCP snooping on the network interface. Ensure that downlink DHCP clients connected to the LSW can obtain IP addresses from an authorized DHCP server to prevent DHCP attacks.
Set the current interface as a DHCP snooping trusted interface. This parameter is valid for switches running V200R011C10SPC550 or a later version. |
ND Snooping |
Whether to enable ND snooping on the current interface. After ND snooping is enabled, iMaster NCE-Campus can check the validity of NA, NS, and RS packets to prevent address spoofing attacks caused by forged NA, NS, and RS packets. This parameter is valid for switches running V200R011C10SPC550 or a later version.
|
IPSG |
IP source guard (IPSG) implements source IP address filtering based on Layer 2 interfaces. IPSG is used to prevent network access from malicious hosts using stolen IP addresses. In addition, IPSG prevents unauthorized hosts from accessing or attacking networks with forged IP addresses. |
DAI |
Dynamic ARP inspection (DAI) is used to prevent Man in The Middle (MITM) attacks. If DAI is not configured, ARP entries of authorized users on the device may be updated by the pseudo ARP packets sent by attackers. |
Port isolation |
Whether to isolate the current interface from other interfaces. If this function is enabled, this network interface is isolated from other network interfaces interface port isolation is enabled in the same VLAN at Layer 2 but can still communicate with them at Layer 3. |
Storm control |
Whether to enable the storm suppression function. After this function is enabled, storm suppression is performed for broadcast, unknown multicast, and unknown unicast packets on the current interface. This parameter is valid for switches running V200R011C10SPC550 or a later version. Within the specified interval, devices automatically sample packets to calculate the average rate of receiving packets.
|
Parameter |
Description |
---|---|
Template name |
Name of the template to configure. |
STP |
Whether to enable STP. |
STP edge port |
Whether to set the current interface as an STP edge port. This parameter is valid for switches running V200R011C10SPC550 or a later version.
|
Loop detection |
When a loop occurs on a network, broadcast, multicast, and unknown unicast packets are repeatedly transmitted on the network. This wastes network resources and may even cause a network breakdown. To minimize the impact of loops on a Layer 2 network, a detection technology that quickly notifies users of loops is required. When a loop occurs, users are requested to check network connections and configurations, and control the problematic interface. |
Loop detection VLAN |
VLAN where loop detection is configured. |
Loop action |
Action taken by the device after LBDT detects a loop:
|
Parameter |
Description |
---|---|
Template name |
Name of an interface VLAN template. |
Link type |
This parameter is selected based on the actual connection of the network interface.
NOTE:
|
VLAN ID |
VLAN ID. This parameter is required when the Link type is Access. |
Default VLAN |
These parameters are required when the Link type is Trunk. Packets received by the trunk interface are processed uniformly. For untagged packets, the cloud switch automatically adds the VLAN ID to the packets. If the VLAN ID is defined in Allowed VLAN, the cloud switch permits the packets to pass through. Otherwise, the cloud switch discards the packets.
NOTE:
You can set Allowed VLAN to all only on switches running V200R011C10SPC550 or a later version. |
Allowed VLAN |
|
Tagged VLAN |
This parameter is required when the Link type is Hybrid. Add the hybrid interface to the specified VLANs. Frames of the VLANs then pass through the hybrid interface in tagged mode. The VLAN ID is in the range of 1 to 4094. The values of Tagged VLAN and Untagged VLAN cannot overlap. The value cannot be all. |
Untagged VLAN |
This parameter is required when the Link type is Hybrid. Add the hybrid interface to the specified VLANs. Frames of the VLANs then pass through the hybrid interface in untagged mode. The VLAN ID is in the range of 1 to 4094. The values of Tagged VLAN and Untagged VLAN cannot overlap. The value cannot be all. |
Voice VLAN |
Whether to enable the voice VLAN function. This function can be used to improve the priority of data packets of IP phones and guarantee the quality of voice calls. This function is applicable only to switches of V200R012C00 and later versions.
|
Voice VLAN ID |
Voice VLAN ID. (This parameter is valid only when Voice VLAN is set to ON.) Traffic from this VLAN must be permitted on the current interface. Otherwise, the voice VLAN function cannot take effect. For an interface, if the link type is set to Hybrid and the Voice packet priority increasing mode is set to MAC, the value of Voice VLAN ID must be the same as that of Untagged VLAN of the current interface. |
Voice packet priority increasing mode |
Voice VLAN application scenario. (This parameter is valid only when Voice VLAN is set to ON.)
NOTE:
To change the tag in a packet with the VLAN tag being 0 to the tag matching the voice VLAN ID, deliver the voice-vlan command with the keyword include-tag0 specified. |
Parameter |
Description |
---|---|
Template name |
Name of an interface physical attribute template. |
Auto-negotiation |
The interface and its directly connected network interface of the remote device support auto-negotiation of the duplex mode and interface rate so that the data transmission capability reaches the maximum value supported by both devices. If the remote device does not support auto-negotiation or the auto-negotiation mechanism is inconsistent with that of the local device, you can configure network interfaces at both ends to work in non-auto-negotiation mode and set the same interface rate and duplex mode at both ends. |
Interface rate |
When auto-negotiation is disabled, maximum transmission rate used by the interface to transmit data. If the interface works in non-auto-negotiation mode, you can adjust it manually. NOTE:
The data transmission rate is also affected by network cables. If the rates of interfaces at both ends are the same but the network cable does not support the maximum transmission rate, interfaces at both ends of a link cannot work properly. To address this issue, you are advised to use Category 5 enhanced cables. If the network cable fault persists, it is recommended that interfaces at both ends of the network cable should work in non-auto-negotiation mode and the rate should be set manually based on the actual transmission capability. |
Duplex mode |
When auto-negotiation is disabled:
Network interfaces at both ends of a link must be configured with the full-duplex mode to avoid packet loss. |
POE |
Enable or disable PoE power supply on a network interface. Only PoE switches support this function. For details about PoE-supporting models, see the switch product documentation. |
Power-on time |
Select a time policy from the drop-down list box to automatically disable PoE power supply on the network interface during the time beyond the specified range. Only PoE switches support this function. For details about PoE-supporting models, see the switch product documentation. If predefined time policies do not meet requirements, click + and create a customized time template in the displayed dialog box. |
Parameter |
Description |
---|---|
Name |
Name of an interface traffic policy. |
Trust select |
|
Outbound traffic policy |
Traffic policy applied to switches in the outbound direction. You need to select a traffic policy configured on the Site Configuration > Switch > Traffic Policy page. |
Inbound traffic policy |
Traffic policy applied to switches in the inbound direction. You need to select a traffic policy configured on the Site Configuration > Switch > Traffic Policy page. |
Parameter |
Description |
|
---|---|---|
Name |
Device where the traffic policy takes effect. |
|
Traffic policy |
Name |
Name of a traffic policy. |
Enable globally |
Whether to enable the traffic policy globally. If the traffic policy is enabled globally, the traffic policy can take effect on all interfaces on the switches. |
|
Flow Direction |
Traffic direction in which the traffic policy takes effect. This parameter is valid only when the traffic policy is enabled globally. The options are as follows: inbound: indicates that the traffic policy is applied to the inbound interfaces of the switch. outbound: indicates that the traffic policy is applied to the outbound interfaces of the switch. both: indicates that the traffic policy is applied to the inbound and outbound interfaces of the switch. |
|
Rule list |
Traffic classifiers and traffic behaviors bound to the traffic policy. |
Configuring General Functions at a Site
Configuring Service Parameters
Context
You can configure the following functions:
- Configuring APs to report terminal locations to a third-party server: APs can report MAC addresses and IP addresses of terminals as well as the MAC addresses and signal strength of associated or non-associated APs to a third-party server. The third-party server locates the terminals based on the received information.
- Setting keys for AP identification: A pre-shared key (PSK) can be configured for each AP for identification.
- Determining AP installation locations: You can decide where to install APs.
- Enabling or disabling HTTP for access to cloud-managed devices: By default, tenant administrators can use HTTP or HTTPS to log in to the web page of cloud-managed devices and perform related operations. Since the HTTP protocol has security risks, you are advised to disable tenant administrators from accessing cloud-managed devices using HTTP. If the HTTP service is disabled, tenant administrators can access the HTTPS address for logging in to the web system of cloud-managed devices. If the HTTP service is enabled, when tenant administrators access the HTTP address of the web system of cloud-managed devices, they will be redirected to the HTTPS address for login.
- Enabling or disabling LLDP globally: Link Layer Discovery Protocol (LLDP) is a standard Layer 2 discovery protocol. It collects local device information including the management IP address, device ID, and port ID and advertises the information to neighbors. Neighbors save the received information in their management information bases (MIBs). The NMS can use data in MIBs to check the link status. On iMaster NCE-Campus, you can enable or disable LLDP globally for devices in batches. By default, LLDP is enabled globally after devices go online.
Enabling or disabling HTTP service and LLDP takes effect only on the following devices:
- APs running V200R008C10 or a later version
- Switches running V200R011C10SPC550 or a later version
- Enabling or disabling public key-free authentication upon first authentication of SSH clients
On iMaster NCE-Campus, you can use SSH to access a third-party device on the same subnet as a cloud-managed device through the command-line interface (CLI) of the cloud managed device. In this manner, you can perform remote O&M for the third-party device. To ensure the successful first access from a cloud-managed device as an SSH client to a third-party device, you need to enable public key-free authentication upon first authentication of SSH clients. This function is supported only on APs running V200R008C10 or a later version and switches running V200R012C00 or a later version.
- Setting SNMP parameters for devices: On iMaster NCE-Campus, you can set SNMP parameters for devices so that devices can establish SNMP connections with third-party NMSs, implementing device monitoring and configuring alarm-related services through the third-party NMSs.
- After iMaster NCE-Campus delivers SNMP configurations to a device, the device automatically creates a user group named cloud_campus_group_name. Both the names of the read and notify views associated with the user group are cloud_campus_view, and users in the user group can access nodes under the sub-tree whose root node is the International Organization for Standardization (ISO). The trap host port of the alarm server to which devices report alarms is 162.
- If SNMPv3 is used, the encryption algorithm of SNMPv3 users is AES128 and the authorization mode is SHA.
Procedure
- Choose from the main menu.
- Select a site from the Site drop-down list in the upper left corner.
- Choose Site Configuration tab. on the
- Set Domain name on Site Configuration tab.
The following devices do not support domain name configuration:
- S1720, S5330-HI, S5331-H, S5332-H, S5720-EI, S5720-HI, S5730-HI, S5731-H, S5731-S, S5731S-H, S5731S-S, S5732-H, S600-E, S6320-HI, S6330-H, S6720-EI, S6720-HI, S6730-H, S6730-S, S6730S-S, S12700, S127E, S7700 series switches
- AR routers of any model
- Firewalls of any model
- Set Time zone, DST and NTP server IP address on Basic Info tab.
The DST can be configured for switches only after the iMaster NCE-Campus V300R019C10SPC207 patch is installed.
- Click
next to Device Administrator and set parameters.
- When you create a site, an admin user and accampus user are automatically created on devices at the site. The passwords for the accampus user are randomly generated by the system. You can click
in the Operation column of a user to change the password.
- If you want to delete the admin user, ensure that another administrator account has been created on the devices.
- When a tenant administrator logs in to iMaster NCE-Campus for the first time, a dialog box is displayed for setting the default password of the device administrator. After the default password of the device administrator is set, when another site is created under the tenant, the device administrator at the site uses this password by default. You can change the password on this page.
- Different users are responsible for device O&M based on the site type.
- Newly created sites: By default, the accampus and admin users are available, whereas the accampus user is preferred for device O&M.
- At upgraded sites: If the accampus user is unavailable, the admin user performs device O&M.
- Device O&M is unavailable if both the admin user and the accampus user are deleted.
- A maximum of 32 local users can be created.
- When iMaster NCE-Campus functions as an HWTACACS or RADIUS authentication server, if there are online users authenticated in HWTACACS or RADIUS mode, you need to delete these online users before changing the authentication mode to the default mode.
- When you create a site, an admin user and accampus user are automatically created on devices at the site. The passwords for the accampus user are randomly generated by the system. You can click
- Click
next to SNMP, enable SNMP Access, and set SNMP parameters.
- Click
next to AP VAS and set parameters.
- Before enabling the information upload function, ensure that the specified server has the capability of receiving and parsing packets sent by APs. For details about the AP packet format, contact Huawei technical support.
- The port number range varies depending on the AP version:
- For V200R008C10 or earlier, the value range is from 5000 to 65535.
- For V200R009C00 or later, the value range is from 1 to 65535.
- In the Other area, enable LLDP and HTTP.
LLDP can be enabled only on ARs, firewalls, LSWs, and APs. If LLDP needs to be enabled on WACs, you need to log in to the WACs to enable LLDP using the CLI.
- Click Apply to save the configuration.
Parameter Description
Parameter |
Description |
---|---|
Domain name |
Default domain name suffix for all switches and APs at the current site, for example, huawei.com. The value specified for Device name during device addition and the value specified here constitute the fully qualified domain name (FQDN) of the device. The FQDN helps users identify devices in a network management system. This parameter applies only to:
|
Parameter |
Description |
---|---|
Time zone |
Default time zone for all devices at the current site. This setting is applicable to firewalls, switches, and APs only. |
DST |
Daylight saving time for devices at the current site. This setting is applicable to switches, APs, and ARs only. |
NTP server IP address |
NTP server IP address for the current site. This setting is applicable to firewalls, switches, and APs only. |
Parameters |
Description |
|
---|---|---|
Local user |
User name |
User name for logging in to a device. The user name is in the username or username@domainname format. The value is case-insensitive and cannot contain spaces or the following special characters: *, ?, ". If HWTACACS authentication bypass is enabled, an authentication account same as the local user account must be configured. |
Password |
Password of the user account. The password must meet the following requirements:
|
|
Role |
Priority of a local user. After uses of different levels log in to a device, they can use only the commands of the same or a lower level than their own levels.
|
|
Service type |
Access mode of a local user.
|
|
BootROM password |
BootROM password of a switch or an AP. If you do not set this password, the administrator password and BootROM password that take effect are those set by tenant administrators when they log in to iMaster NCE-Campus for the first time, or those set in the Device Password Configuration area on the Device Management tab page under . |
|
Login timeout interval (min) |
Period after which a user is disconnected from the user interface. The value is 10 by default. The value 0 indicates that this function is disabled. |
|
Screen length |
Number of rows printed on a split screen. The value is 24 by default. The value 0 indicates that this function is disabled. |
|
Login restriction |
Whether to restrict login to devices via SSH. You can bind SSH virtual type terminal (VTY) accounts of devices to specified advanced ACLs to restrict the accounts that are allowed to log in to devices via SSH. Only APs and switches support this function. The available ACL numbers are in the range from 3032 to 3999. |
|
HWTACACS Authentication |
- |
Whether to enable the HWTACACS authentication mode for the devices at the current site. NOTE:
HWTACACS authentication cannot be disabled if a switch supports login through a console port. |
HWTACACS Server |
Select a HWTACACS server from the drop-down list box. The server has been defined on the Policy Template page. |
|
Command line authorization |
You can set this parameter as needed. This function is optional when the controller functions as a HWTACACS authentication server. If the controller functions as a HWTACACS authorization server to authorize command lines to device users, you need to configure a command set and enable this function. |
|
HWTACACS authentication bypass |
Bypass policy after a HWTACACS server authentication or authorization failure.
|
|
RADIUS Authentication NOTE:
Devices running V200R0C19C10 or later support RADIUS authentication. |
RADIUS server |
RADIUS server configured in the desired RADIUS server template. The RADIUS server template is defined on the policy template page. |
Authentication protocol |
RADIUS authentication protocol. PAP and CHAP are supported. |
|
RADIUS authentication bypass |
|
Parameter |
Description |
|
---|---|---|
Protocol version |
SNMP version. SNMPv3 is recommended, because it is more secure than SNMPv1 and SNMPv2c. |
|
Configuration in the scenario where Version is set to V1 or V2C |
Read community name |
Group of NMSs and SNMP agents. A community name functions as the password for authentication when devices in the community communicate with each other. An NMS can access an SNMP agent only if the community name carried in the SNMP request sent by the NMS is the same as that configured on the SNMP agent. A community name consists of a read community name and a write community name. Currently, iMaster NCE-Campus can only interconnect with SNMP through the read community name. The parameter value consists of 1 to 32 characters including digits, letters, or special characters. |
Allowed IP addresses |
IP address whitelist of NMS servers. The whitelist defines NMS servers' IP addresses, improving the system security. If the whitelist is left empty, an NMS server with any IP address can access devices. |
|
Alarm Server |
WIndicates whether to configure alarm servers for devices. Through this function, alarms generated on a device can be sent to the NMS server in a timely manner, implementing effective management on devices. The IP addresses must be of Class A, B, or C. Multiple IP addresses need to be separated with line breaks, and up to 20 IP addresses can be entered.
|
|
Alarm server list |
Alarm server IP address. The IP addresses must be of Class A, B, or C. Multiple IP addresses need to be separated with line breaks, and up to 20 IP addresses can be entered. |
|
Configuration in the scenario where Version is set to V3 |
User List |
Click Add and add the account information. To implement the bidirectional communication in the following scenarios, ensure that User name, Encryption Password, and Authentication Password are the same as those on the NMS server:
|
Allowed IP addresses |
IP address whitelist of NMS servers. The whitelist defines NMS servers' IP addresses, improving the system security. If the whitelist is left empty, an NMS server with any IP address can access devices. The IP addresses must be of Class A, B, or C. Multiple IP addresses need to be separated with line breaks, and up to 20 IP addresses can be entered. |
|
Alarm Server |
Whether to configure alarm servers for devices. Through this function, alarms generated on a device can be sent to the NMS server in a timely manner, implementing effective management on devices. |
|
Alarm server list |
Click Add, add an alarm server, and select corresponding accounts from the drop-down list box. The alarm server IP addresses must be of Class A, B, or C, and up to 20 IP addresses can be added. |
Parameter |
Description |
---|---|
Information upload |
Enable Information upload function. |
Server IP or domain |
IP address or domain name of the third-party server that receives packets. Only APs of V200R009C00 and later versions support the domain name. |
Port number |
Number of the port on which packets are received. This parameter is configurable only when Information upload is enabled. The default value is 10031. |
Interval (ms) |
Interval at which an AP reports the received information. The default value is 20,000 ms. |
Threshold (dBm) |
Scanned signal strength. If the signal strength is lower than the threshold, no action is performed. The default value is -75 dBm. |
AP PSK |
Whether to enable the function of configuring the PSK. Enabling this parameter indicates that a PSK is added, while disabling this parameter indicates that no PSK exists. |
Update PSK Key |
Whether to update the PSK value. If the PSK is not configured, the update button is unavailable. |
Set AP installation location |
WSpecify whether to enable the function of configuring AP installation location information. After this field is enabled, you can configure the AP installation location. Only APs of V200R009C00 and later versions support this parameter. |
AP installation location |
Set the AP installation location. |
Parameter |
Description |
---|---|
LLDP |
An LLDP-enabled device sends LLDP packets containing its own status information to neighbors that have LLDP enabled, and collects the status information about these neighbors. Enable this function when you need to know the Layer 2 connection status between devices and analyze the network topology through the NMS. This function is enabled by default. Frequently enabling or disabling LLDP globally may cause service data delivery failures. The interval between two consecutive LLDP operations must be longer than 10s. |
HTTP service |
Whether to enable the HTTP service on cloud-managed devices. By default, this function is enabled. If the HTTP service is disabled, tenant administrators can log in to the web system of cloud-managed devices using HTTPS. If the HTTP service is enabled, when tenant administrators access the web system of cloud-managed devices using HTTP, they will be redirected to an HTTPS address for login. |
Public key-free upon first authentication of SSH client |
Whether to enable the first authentication function on an SSH client. |
IPv6 |
Whether to enable IPv6 globally. The configuration takes effect only after the function is enabled in the AP's SSID configuration as well. After IPv6 is globally enabled, it takes effect only after it is enabled in the AP's SSID configuration as well. |
Configuring a Management VLAN
Context
For security purposes, you are advised to configure a dedicated management VLAN for the Layer 2 network of a tenant. This management VLAN can be used for configuration and O&M of cloud-managed devices. Using iMaster NCE-Campus, you can configure a management VLAN to manage firewalls, switches, and APs at a site.
- You must change the management VLANs of all cloud-managed devices on a network from bottom to top. Otherwise, the devices cannot be managed by iMaster NCE-Campus.
- On the page, you can also create and manage VLANs for specific switches.
- Currently, iMaster NCE-Campus can create and manage a maximum of 512 VLANs.
You can configure the management VLAN auto-negotiation function for firewalls and switches. Downstream cloud-managed devices newly added to the network use the auto-negotiated management VLAN configured on the firewalls or switches as the management VLAN by default to obtain IP addresses from the DHCP server and register with iMaster NCE-Campus.
- Firewall: V500R005C00
- Switch: V200R012C00
If an uplink interface on a switch is pre-configured as an Eth-Trunk interface, perform either of the following operations:
- (Recommended) Disable Auto permit on uplink interface in the switch's management VLAN configuration.
- Configure the uplink interface as an Eth-Trunk interface on the switch and iMaster NCE-Campus are the same.
Prerequisites
- Before configuring the management VLAN auto-negotiation function, ensure that LLDP has been enabled globally. For details about how to enable or disable LLDP, see Configuring Service Parameters.
- If uplink interfaces have been configured on a device, configure the interfaces in the same way on iMaster NCE-Campus. For details, see Configuring Physical Interfaces. Alternatively, disable Auto permit on uplink interface in the management VLAN configuration.
- In cloud management scenarios, uplink interfaces on a device cannot be configured as an Eth-Trunk 0 interface. The Eth-Trunk 0 interface is reserved for Eth-Trunk auto-negotiation between devices.
- After a central AP gets on-boarded, configure the uplink interfaces of the central AP to allow packets from the management VLAN to pass through. For details, see Configuring Physical Interfaces.
Procedure
- Choose from the main menu.
- Select a site from the Site drop-down list in the upper left corner.
- Choose Network Configuration tab. on the
- To enable the management VLAN auto-negotiation function, set Auto-negotiation to ON and click Apply.After you enable the management VLAN auto-negotiation function:
- The management VLAN auto-negotiation function is automatically enabled on all the interfaces of all firewalls and switches at the selected site. In this case, the downlink devices connected to these interfaces can automatically switch their management VLAN through auto-negotiation. To disable this function on some interfaces of a specific device, select the desired interfaces on the Interface page, and set Management VLAN auto-negotiation in the Advanced area to OFF.
- If an Eth-Trunk interface on a switch at the selected site has Eth-Trunk auto-negotiation enabled (disabled by default), the physical interfaces on the downlink switches directly connected to the member interfaces in the Eth-Trunk interface are automatically added to Eth-Trunk0, and are connected to the uplink network via the auto-negotiated management VLAN.
- Find the target device in VLAN list and click
to configure a management VLAN for the device.
- In the On-Premise scenario, APs switch between modes and dynamically obtain the IP address of the controller for registration using a DHCP server. If necessary, you can configure a static IP address for each AP to connect to the controller. In this case, you need to set the IP address assignment mode to Static and set the IP address, mask, gateway address, and primary and secondary DNS address.
- Click
to restore the management VLAN of the device to the default value.
Parameter Description
Parameter |
Description |
---|---|
Auto-negotiated Management VLAN |
(For firewalls and switches only) When a downstream NE is connected to the current device, this VLAN is automatically used as the management VLAN of the NE through negotiation. The NE then can obtain an IP address from the DHCP server and register with iMaster NCE-Campus. |
Management VLAN |
(For switches and APs only) Management VLAN of the current device. The switch or AP creates a VLANIF interface based on the management VLAN. The IP address of the VLANIF interface is used as the management IP address of the device to initiate a registration request to iMaster NCE-Campus. |
Auto permit on uplink interface |
(For switches only) After this function is enabled:
|
Configuring a CLI Whitelist
Context
The command-line interface (CLI) is an interface where executable instructions are entered as prompted. Some CLI commands that users need to run are supported by devices, but not supported on iMaster NCE-Campus. To prevent command input on devices, iMaster NCE-Campus supports the CLI configuration and can deliver the saved commands to devices.
The commands that can be delivered to devices by iMaster NCE-Campus must be defined in a command whitelist configured on iMaster NCE-Campus.
- Some configuration items can be configured through a command whitelist and on the iMaster NCE-Campus web UI. You are advised to use only one of them. Performing configurations on the web UI is recommended.
- To change the configuration mode from the CLI whitelist to the web UI, you must delete the configured commands in the CLI whitelist, and then reconfigure them on the web UI.
- If Local CLI-based switch configuration is disabled, after you log in to a switch using the CLI, you can only run specified commands. For details about the commands that can be run, see Enabling or Disabling Local CLI-based Device Configuration.
Prerequisites
A device has been added to iMaster NCE-Campus and a site.
Procedure
- Choose from the main menu.
- In the displayed window, select a site from the Site drop-down list.
- Choose Network Configuration tab. on the
- Set Device Type on the displayed page, click Create, and enter name and CLI. Press Enter to separate multiple commands.
- When Configure device is set to Global, the configured commands take effect for devices of all types. When Configure device is set to Personalized, the configured commands take effect only for the selected devices.
- When you deliver configurations to devices by specifying commands in the command whitelist, if the parameters specified in the commands delivered through the web UI are involved in the commands in the command whitelist, the parameter values cannot be found on the web UI. Therefore, you need to view the parameters on target devices and then add the parameters to the command lines in the CLI whitelist.
- Click Confirm and save the CLI configuration.
- The template name, user name, and password entered in the CLI can contain both uppercase and lowercase letters. Other information in the CLI can only contain lowercase letters.
- To modify a command delivered to a device, deliver the undo command for the command to be deleted and then deliver the modified command to the device.
Operation
Description
Create
After a new command is saved, the configuration will be sent to the target device immediately.
Delete
- Selecting a command and clicking Delete will only delete the command stored on iMaster NCE-Campus and will not delete the command stored on the target device.
- If you need to delete a command from a device, create and save the undo command for the command to be deleted, and deliver the undo command to the target device. Then manually delete the undo command and command to be deleted from the target device.
CLI Whitelist of APs
Table 6-280 lists the commands that can be delivered from iMaster NCE-Campus to an AP. For the detailed command format and parameter description, see the command reference of the AP.
Function |
View |
Command |
---|---|---|
Display the WLAN view. |
system-view |
wlan |
Displays or delete a interface view. |
system-view |
interface interface-type interface-number undo interface interface-type interface-number |
Create or delete a VLANIF interface. |
system-view |
interface vlanif vlan-id undo interface vlanif vlan-id NOTE:
Deleting a VLANIF interface that functions as a management interface will cause the switch to be disconnected from iMaster NCE-Campus. Exercise caution when performing this operation. |
Add an RU in offline mode or enter the AP view. |
wlan |
ap-id ap-id [ [ type-id type-id | ap-type ap-type ] { ap-mac ap-mac | ap-sn ap-sn | ap-mac ap-mac ap-sn ap-sn } ] undo ap ap-id |
Add an RU in offline mode or enter the AP view. |
wlan |
ap-mac ap-mac [ type-idtype-id | ap-typeap-type ] [ ap-idap-id ] [ ap-snap-sn ] |
Configure or restore an RU name |
AP-view |
ap-name ap-name undo ap-name |
Configure or restore the memory usage alarm threshold. |
system-view |
set memory-usage threshold threshold-value undo set memory-usage threshold |
Configure or restore physical interfaces on the SSH server to which clients can connect |
system-view |
ssh server permit interface { interface-type interface-number } &<1-5> undo ssh server permit interface |
Configure or restore the port number of the SSH server. |
system-view |
ssh server port port-number undo ssh server port |
Configure or restore an interval for updating the SSH server key pair. |
system-view |
ssh server rekey-interval hours undo ssh server rekey-interval |
Configure or restore a timeout interval for an SSH server connection. |
system-view |
ssh server timeout seconds undo ssh server timeout |
Enable or disable the SSH server function. |
system-view |
stelnet server enable undo stelnet server enable |
Enable or disable the SFTP function of the SSH server. |
system-view |
sftp server enable undo sftp server enable |
Creates or delete an attack defense. |
system-view |
cpu-defend policy policy-name undo cpu-defend policy policy-name |
Set or restore the rate limit for packets sent to the CPU. |
attack defense policy view |
packet-type packet-type rate-limit rate-value { wired | wireless } undo packet-type packet-type rate-limit { wired | wireless } |
Configure or restore the rate limit for upstream and downstream packets of all STAs or each STA on a VAP. |
traffic profile view |
rate-limit { client | vap } { up | down } rate-value undo rate-limit { client | vap } { up | down } |
Set or restore the rate limit for Secure Shell (SSH), Telecommunication Network Protocol (Telnet), or File Transfer Protocol (FTP) packets. |
attack defense policy view |
application-apperceive packet-type { ssh | telnet | ftp } rate-limit rate-value undo application-apperceive packet-type { ssh | telnet | ftp } |
Create or delete a QoS CAR profile. |
system-view interface |
qos car car-name cir cir-value [ cbs cbs-value [ pbs pbs-value ] | pir pir-value [ cbs cbs-value pbs pbs-value ] ] undo qos carcar-name |
Create or delete a VAP profile. |
wlan |
vap-profile name profile-name undo vap-profile { name profile-name | all } |
Create or delete a SSID profile. |
wlan |
ssid-profile name profile-name undo ssid-profile { name profile-name | all } |
Create or delete a traffic profile. |
wlan |
traffic-profile name profile-name undo traffic-profile { all | name profile-name } |
Create or delete a Hotspot2.0 profile. |
wlan |
hotspot2-profile name profile-name undo hotspot2-profile { name profile-name | all } |
Create or delete a security profile. |
wlan |
security-profile profile-name undo security-profile |
Create or delete a 2G radio profile. |
wlan |
radio-2g-profile name profile-name undo radio-2g-profile { name profile-name | all } |
Create or delete a 5G radio profile. |
wlan |
radio-5g-profile name profile-name undo radio-5g-profile { name profile-name | all } |
Create or deletes an RRM profile |
wlan |
rrm-profile name profile-name undo rrm-profile { name profile-name | all } |
Create or delete an air scan profile. |
wlan |
air-scan-profile name profile-name undo air-scan-profile { name profile-name | all } |
Create or delete a location profile. |
wlan |
location-profile name profile-name undo location-profile { name profile-name | all } |
Create or delete an AP group |
wlan |
ap-group name group-name undo ap-group { name group-name | all } |
Configure broadcast flood attack detection. |
vap-profile |
anti-attack broadcast-flood undo anti-attack broadcast-flood |
Enable or disable the MU-MIMO optimization function. |
ssid-profile |
mu-mimo undo mu-mimo |
Enable or disable IGMP snooping. |
system-view traffic-profile |
igmp-snooping enable undo igmp-snooping enable |
Set or restore the maximum transmission unit (MTU) of the AP's CAPWAP tunnel. |
system-view interface vlanif |
mtu mtu undo mtu |
Specify or restore the noise floor threshold for triggering radio calibration. |
rrm-profile |
calibrate noise-floor-threshold threshold undo calibrate noise-floor-threshold |
Create or delete a radio calibration policy. |
wlan |
calibrate policy { rogue-ap | load | non-wifi | noise-floor } undo calibrate policy { rogue-ap | load | non-wifi | noise-floor } |
Enable or disable the DHCP function. |
system-view |
dhcp enable undo dhcp enable |
Set or restore the maximum number of ping packets to be sent. |
system-view |
dhcp server ping packet number undo dhcp server ping packet |
Set or restore the maximum response time of a ping packet. |
system-view |
dhcp server ping timeout milliseconds undo dhcp server ping timeout |
Enable or disable DHCP snooping. |
system-view interface |
dhcp snooping enable [ vlan { vlan-id1 [ to vlan-id2 ] } &<1-10> ] undo dhcp snooping enable [ vlan { vlan-id1 [ to vlan-id2 ] } &<1-10> ] |
Set or restore the GI mode to short GI. |
radio-2g-profile radio-5g-profile |
guard-interval-mode { short | normal } undo guard-interval-mode short |
Set or restore the start threshold for the number of STAs that preferentially access the 5 GHz radio during band steering. |
rrm-profile |
band-steer balance start-threshold start-threshold undo band-steer balance start-threshold |
Set or restore the RTS-CTS threshold in a radio profile. |
radio-2g-profile radio-5g-profile |
rts-cts-threshold rts-cts-threshold undo rts-cts-threshold |
Enable user CAC based on terminal SNR. |
rrm-profile |
uac client-snr enable undo uac client-snr enable |
Configure or restore the user CAC threshold based on terminal SNR. |
rrm-profile |
uac client-snr threshold threshold undo uac client-snr threshold |
Enable the user CAC threshold based on channel usage. |
rrm-profile |
uac channel-utilization enable undo uac channel-utilization enable |
Configure or restore the user CAC threshold based on channel usage. |
rrm-profile |
uac channel-utilization threshold access access-threshold [ roam roam-threshold ] undo uac channel-utilization threshold |
Set or restore the maximum MSS value for a TCP connection. |
system-view |
tcp max-mss mss-value undo tcp max-mss |
Configure or disable the device to output information to a log host |
system-view |
info-center loghost domain domain-name [ channel { channel-number | channel-name } | facility local-number | language language-name | portport| transport { udp | tcpssl-policy policy-name } ] * undo info-center loghost domain domain-name |
Set or default the timestamp format of logs messages |
system-view |
info-center timestamp log { { date | short-date | format-date } [ precision-time { tenth-second | millisecond } ] | boot | none } undo info-center timestamp log |
Configure security profile. |
wlan vap-profile |
security-profile |
Disable/Enable smart roaming. |
radio-2g-profile radio-5g-profile |
smart-roam disable undo smart-roam disable |
Enable or disable the HTTPS server function on the device. |
system-view |
http secure-server enable undo http secure-server enable |
Enable or disable the HTTP server. |
system-view |
http server enable undo http server enable |
Restore the default user CAC threshold based on the number of users. |
rrm-profile |
undo uac client-number threshold |
Disable user CAC based on the number of users. |
rrm-profile |
undo uac client-number enable |
Create or delete an IoT profile. |
wlan |
iot-profile nameprofile-name undo iot-profile { name profile-name | all } |
Configure a host computer or delete the host computer configuration. |
iot-profile |
management-server server-ip server-ip server-port server-port-num undo management-server server-ip server-ip server-port server-port-num |
Display the IoT card interface view. |
wlan ap-group |
card card-number |
Bind an IoT profile. |
card |
iot-profile profile-name config-agent udp port udp-port |
Set the radio type in a radio profile. |
radio-2g-profile radio-5g-profile |
radio-type { dot11b | dot11g | dot11n | dot11ax } undo radio-type radio-type { dot11a | dot11n | dot11ac | dot11ax } undo radio-type |
Enable an AP to sendARP/ND proxy packets for a STAbefore the STA is successfully associated. |
wlan |
sta arp-nd-proxy before-assoc undo sta arp-nd-proxy before-assoc |
Enable the DHCP-based terminal type awareness function. |
system-view |
device-sensor dhcp option undo device-sensor dhcp option |
Enable the User Agent function. |
system-view |
http parse user-agent enable undo http parse user-agent enabled |
Set the memory usage threshold. |
system-view |
set memory-usage threshold threshold-value undo set memory-usage threshold |
Set or restore the CPU usage alarm threshold and CPU usage alarm recovery threshold. |
system-view |
set cpu-usage threshold threshold-value [ restore restore-threshold-value ] undo set cpu-usage threshold |
Set or restore the lower temperature alarm threshold for APs. |
wlan |
low-temperature threshold threshold undo low-temperature threshold |
Set or restore the upper temperature alarm threshold for APs. |
wlan |
high-temperature threshold threshold undo high-temperature threshold |
Set the lower temperature alarm threshold for RUs. |
AP system profile view |
low-temperature threshold threshold undo low-temperature threshold |
Set the upper temperature alarm threshold for RUs. |
AP system profile view |
high-temperature threshold threshold undo high-temperature threshold |
Configure the source IP address for the device to communicate with a Portal server. |
system-view |
web-auth-server server-name source-ip ip-address undo web-auth-server server-name undo source-ip |
Configure the offline self-healing function. |
system-view |
offline self-healing-reset disable undo offline self-healing-reset disable |
Add or delete MAC addresses of neighboring APs that are allowed to connect to an AP to a Mesh whitelist profile. |
mesh-whitelist-profile |
peer-ap mac mac-address undo peer-ap mac mac-address |
Configure AP indicators to turn off or turn off during the specified time range/ restores the default settings. |
system-view |
led off [ time-range time-range-name ] undo led off |
Set or restore a time range. |
system-view |
time-range time-name { start-time to end-time { days } &<1-7> | from time1 date1 [ to time2 date2 ] } undo time-range time-name [ start-time to end-time { days } &<1-7> | from time1 date1 [ to time2 date2 ] ] |
Create or delete an AP system profile |
wlan |
ap-system-profile name profile-name undo ap-system-profile |
Set or restore a Mesh ID for a Mesh profile |
mesh-profile |
mesh-id name undo mesh-id |
Create or delete a Mesh profile |
wlan |
mesh-profile name profile-name undo mesh-profile { all | name profile-name } |
Create or delete a Mesh whitelist profile or display the Mesh whitelist profile view. |
wlan |
mesh-whitelist-profile name whitelist-name undo mesh-whitelist-profile { all | name whitelist-name } |
Delete entries from all session tables. |
system-view |
reset session all NOTE:
Running this command on a device will cause the device to go offline and then online. Exercise caution when running this command. |
Create a VLAN and displays the VLAN view. If the VLAN exists, the VLAN view is displayed. |
system-view |
vlan vlan-id vlan batch { vlan-id1 [ to vlan-id2 ] } &<1-10> undo vlan vlan-id undo vlan batch { vlan-id1 [ to vlan-id2 ] } &<1-10> |
Configure a VLAN as the default VLAN of an interface and add the interface to the VLAN. |
vlan |
port interface-type { interface-number1 [ to interface-number2 ] }&<1-10> undo port interface-type { interface-number1 [ to interface-number2 ] }&<1-10> |
Enable the port bridge function on an interface. The interface then can forward packets whose source and destination MAC addresses are both learned by this interface. |
GE interface Eth-Trunk interface XGE interface MultiGE interface |
port bridge enable undo port bridge enable |
Configure the default VLAN of an interface and adds the interface to the VLAN. |
GE interface Eth-Trunk interface XGE interface MultiGE interface |
port default vlanvlan-id undo port default vla |
Specify the default VLAN ID of a hybrid interface. |
GE interface Eth-Trunk interface XGE interface MultiGE interface |
port hybrid pvid vlanvlan-id undo port hybrid pvid vlan |
Add a hybrid interface to the specified VLANs. Frames of the VLANs then pass through the hybrid interface in tagged mode. |
GE interface Eth-Trunk interface XGE interface MultiGE interface |
port hybrid tagged vlan { { vlan-id1 [ to vlan-id2 ] }&<1-10> | all } undo port hybrid vlan { { vlan-id1 [ to vlan-id2 ] }&<1-10> | all } |
Add a hybrid interface to the specified VLANs. Frames of the VLANs then pass through the hybrid interface in untagged mode. |
GE interface Eth-Trunk interface XGE interface MultiGE interface |
port hybrid untagged vlan { { vlan-id1 [ to vlan-id2 ] }&<1-10> | all } undo port hybrid vlan { { vlan-id1 [ to vlan-id2 ] }&<1-10> | all } |
Set the link type of an interface. |
GE interface Eth-Trunk interface XGE interface MultiGE interface |
port link-type { access | hybrid | trunk } undo port link-type |
Add a trunk interface to the specified VLANs. |
GE interface Eth-Trunk interface XGE interface MultiGE interface |
port trunk allow-pass vlan { { vlan-id1 [ to vlan-id2 ] }&<1-10> | all } undo port trunk allow-pass vlan { { vlan-id1 [ to vlan-id2 ] }&<1-10> | all } |
Specify the default VLAN for a trunk interface. |
GE interface Eth-Trunk interface XGE interface MultiGE interface |
port trunk pvid vlanvlan-id undo port trunk pvid vlan |
Set the AP channel mode to indoor mode or restore the AP channel mode to outdoor mode. |
wlan |
channel-load-mode indoor undo channel-load-mode indoor NOTE:
After this command is delivered successfully to an AP, the AP is automatically restart for the configuration to take effect. |
Configure or delete an IP address for an interface. |
VLANIF interface view loopback interface view |
ip address ip-address { mask | mask-length } undo ip address ip-address { mask | mask-length } |
Enable or disable an interface to use the interface address pool. |
VLANIF interface view |
dhcp select interface undo dhcp select interface |
Configure or delete a unicast static route. |
system-view |
ip route-static ip-address { mask | mask-length } { nexthop-address | interface-type interface-number [ nexthop-address ] } [ preference preference | tag tag ] * [ permanent | inherit-cost ] [ description text ] undo ip route-static ip-address { mask | mask-length } [ nexthop-address | interface-type interface-number [ nexthop-address ] ] [ preference preference | tag tag ] * [ permanent ] undo ip route-static all |
Disable or enable intelligent flow control for unknown unicast packets. |
system-view |
unicast-suppression auto-detect disable undo unicast-suppression auto-detect disable |
Configure or delete an IP address pool for a sub-VLAN. |
vlan |
ip pool start-address [ to end-address ] undo ip pool |
Create or delete a RADIUS server template. |
system-view |
radius-server template template-name undo radius-server template template-name |
Modify or restore a RADIUS attribute. |
RADIUS server template view |
radius-attribute set service-type attribute-value [ auth-type mac | user-type ipsession ] undo radius-attribute set service-type |
Configure or delete the DNS server address for the DHCP client. |
IP address pool view DHCP Option template view |
dns-list { ip-address &<1-8> | unnumbered interface interface-type interface-number } undo dns-list { ip-address | unnumbered interface | all } |
Enable or disable DNS proxy. |
system-view |
dns proxy enable undo dns proxy enable |
Enable or disable dynamic DNS resolution |
system-view |
dns resolve undo dns resolve |
Enabling/Disabling the USB ethernet port mode |
system-view |
usb enable [ 5w ] undo usb enable card connect-type { ethernet | serial } undo card connect-type iot-card reboot ap ap-id ap-id card { card-id | usb } |
LSW CLI Whitelist
Table 6-281 lists supported CLI commands for switches. For the detailed command format and parameter description, see the command reference of the switch.
Function |
View |
Command |
---|---|---|
Displays or delete a interface view. |
system-view |
interface interface-type interface-number undo interface interface-type interface-number |
Create or delete a VLAN view |
system-view |
vlan vlan-id undo vlan vlan-id |
Enable the device to obtain packets matching specified rules. |
system-view |
capture-packet { interface interface-type interface-number | acl acl-number } * [ vlan vlan-id | cvlan cvlan-id ] * destination terminal [ car cir car-value | time-out time-out-value | packet-num number | packet-len length ] * capture-packet cpu [ vlan vlan-id | acl acl-number ] * destination terminal [ time-out time-out-value | packet-num number | packet-len length ] * |
Configure traditional local management parameters (SSH, HTTP, and HTTPS). |
system-view |
ssh [ ipv4 | ipv6 ] server port port-number undo ssh [ ipv4 | ipv6 ]server port ssh server rekey-interval hours undo ssh server rekey-interval ssh server timeout seconds undo ssh server timeout stelnet [ ipv4 | ipv6 ] server enable undo stelnet [ ipv4 | ipv6 ] server enable sftp server enable undo sftp server enable ssh server-source -i loopback interface-number undo ssh server-source http ipv6 server enable undo http ipv6 server enable http [ ipv6 ] server port port-number undo http [ ipv6 ] server port http timeout undo http timeout http [ ipv6 ] secure-server port port-number undo http [ ipv6 ] secure-server port http [ ipv6 ] secure-server enable undo http [ ipv6 ] secure-server enable http server-source -i loopback interface-number undo http server-source |
Specify the IP addresses of administrators allowed to log in to the switches. |
system-view |
ssh [ ipv6 ] server acl acl-number undo ssh [ ipv6 ] server acl telnet [ ipv6 ] server acl acl-number undo telnet [ ipv6 ] server acl http[ ipv6 ] acl undo http[ ipv6 ] acl |
Enable broadcast storm suppression. |
vlan |
broadcast-suppression threshold-value undo broadcast-suppression |
interface |
broadcast-suppression { percent-value | cir cir-value [ cbs cbs-value ] | packets packets-per-second } undo broadcast-suppression multicast-suppression { percent-value | cir cir-value [ cbs cbs-value ] | packets packets-per-second } undo multicast-suppression unicast-suppression { percent-value | cir cir-value [ cbs cbs-value ] | packets packets-per-second } undo unicast-suppression |
|
Enable link aggregation. |
interface |
lacp preempt enable undo lacp preempt enable lacp timeout undo lacp timeout lacp force-forward undo lacp force-forward |
system-view |
lacp priority undo lacp priority |
|
Enable DLDP. |
system-view |
dldp enable undo dldp enable dldp interval interval undo dldp interval dldp authentication-mode { md5 md5-password | simple simple-password | sha sha-password | none } undo dldp authentication-mode [ md5 md5-password | simple simple-password | sha sha-password | none ] dldp delaydown-timer time undo dldp delaydown-timer [ time ] |
Enable port mirroring. |
interface |
port-mirroring to observe-port observe-port-index { both | inbound | outbound } undo port-mirroring [ to observe-port observe-port-index ] { both | inbound | outbound } |
system-view |
observe-port [ observe-port-index ] interface interface-type interface-number [ untag-packet ] undo observe-port observe-port-index |
|
Enable IGMP snooping. |
system-view |
igmp-snooping enable |
VLAN |
l2-multicast forwarding-mode undo l2-multicast forwarding-mode l2-multicast router-port-discard undo l2-multicast router-port-discard igmp-snooping enable undo igmp-snooping enable igmp-snooping version version undo igmp-snooping version |
|
Enable DHCP snooping. |
system-view VLAN interface |
dhcp snooping check dhcp-request enable undo dhcp snooping check dhcp-request enable dhcp snooping check dhcp-rate enable [ rate ] undo dhcp snooping check dhcp-rate enable |
Enable ND snooping. |
VLAN interface |
nd snooping enable dhcpv6 only undo nd snooping enable nd snooping trusted interface interface-type interface-number undo nd snooping trusted interface interface-type interface-number nd snooping trusted dhcpv6 only |
Enable MLD snooping. |
system-view VLAN |
mld-snooping enable [ vlan { vlan-id1 [ to vlan-id2 ] } &<1-10> ] undo mld-snooping enable [ vlan { all | { vlan-id1 [ to vlan-id2 ] } &<1-10> } ] mld-snooping enable undo mld-snooping enable |
Enable IPv6 management. (IPv6 addresses are configured on the VLANIF interfaces, but iMaster NCE-Campus can still manage devices using IPv4 addresses.) |
interface |
ipv6 address { ipv6-address prefix-length | ipv6-address/prefix-length } undo ipv6 address [ ipv6-address prefix-length | ipv6-address/prefix-length ] ipv6 address { ipv6-address prefix-length | ipv6-address/prefix-length } anycast ipv6 address auto global [ default ] ipv6 address auto link-local ipv6 address { ipv6-address prefix-length | ipv6-address/prefix-length } eui-64 ipv6 address ipv6-address link-local undo ipv6 address dhcpv6-prefix ipv6 enable undo ipv6 enable |
Port security |
interface |
port-security enable undo port-security enable port-security mac-address sticky [ mac-address vlan vlan-id ] undo port-security mac-address sticky [ mac-address vlan vlan-id ] port-security max-mac-num max-number undo port-security max-mac-num port-security aging-time undo port-security aging-time port-security protect-action undo port-security protect-action |
Enable QoS functions. |
system-view |
traffic classifier classifier-name [ operator { and | or } ] undo traffic classifier classifier-name traffic policy policy-name [ match-order { auto | config } ] [ atomic ] undo traffic policy policy-name drop-profile drop-profile-name qos queue queue-index wred drop-profile-name qos-profile name profile-name undo qos-profile { all | name profile-name } traffic behavior behavior-name undo traffic behavior behavior-name |
interface |
traffic-policy policy-name { inbound | outbound } undo traffic-policy [ policy-name ] { inbound | outbound } trust { 8021p | dscp } trust { 8021p { inner | outer } | dscp } qos queue queue-index wred drop-profile-name qos { pq | wrr | drr } undo qos { pq | wrr | drr } qos queue queue-index drr weight weight undo qos queue queue-index drr qos queue queue-index wrr weight weight undo qos queue queue-index wrr qos lr inbound cir cir-value [ cbs cbs-value ] qos lr outbound cir cir-value [ cbs cbs-value ] qos queue queue-index shaping cir cir-value pir pir-value [ cbs cbs-value pbs pbs-value ] |
|
traffic classifier |
if-match [ ipv6 ] acl { acl-number | acl-name } undo if-match [ ipv6 ] acl { acl-number | acl-name } if-match vlan-id start-vlan-id [ to end-vlan-id ] [ cvlan-id cvlan-id ] undo if-match vlan-id start-vlan-id [ to end-vlan-id ] [ cvlan-id cvlan-id ] |
|
traffic behavior |
car cir cir-value [ pir pir-value ] [ cbs cbs-value pbs pbs-value ] [ share ] [ green { discard | pass [ remark-dscp dscp-value | remark-8021p 8021p-value ] } ] [ yellow { discard | pass [ remark-dscp dscp-value | remark-8021p 8021p-value ] } ] [ red { discard | pass [ remark-dscp dscp-value | remark-8021p 8021p-value ] } ] undo car statistic enable undo statistic enable remark dscp { dscp-name | dscp-value } undo remark dscp |
|
traffic policy |
classifier classifier-name behavior behavior-name undo classifier classifier-name |
|
drop profile |
color { green | non-tcp | red | yellow } low-limit low-limit-percentage high-limit high-limit-percentage discard-percentage discard-percentage undo color { green | non-tcp | red | yellow } |
|
Enable ACL functions. |
system-view |
acl [ number ] acl-number [ match-order { auto | config } ] undo acl { [ number ] acl-number | all } |
advanced ACL basic ACL user ACL user-defined ACL layer 2 ACL |
rule [ rule-id ] { deny | permit } { protocol-number | icmp } [ destination { destination-address destination-wildcard | any } | { { precedence precedence | tos tos } * | dscp dscp } | { fragment | first-fragment } | logging | icmp-type { icmp-name | icmp-type [ icmp-code ] } | source { source-address source-wildcard | any } | time-range time-name | ttl-expired | vpn-instance vpn-instance-name ] * undo rule { deny | permit } { protocol-number | icmp } [ destination { destination-address destination-wildcard | any } | { { precedence precedence | tos tos } * | dscp dscp } | { fragment | first-fragment } | logging | icmp-type { icmp-name | icmp-type [ icmp-code ] } | source { source-address source-wildcard | any } | time-range time-name | ttl-expired | vpn-instance vpn-instance-name ] * rule [ rule-id ] { deny | permit } { protocol-number | tcp } [ destination { destination-address destination-wildcard | any } | destination-port { eq port | gt port | lt port | range port-start port-end } | { { precedence precedence | tos tos } * | dscp dscp } | { fragment | first-fragment } | logging | source { source-address source-wildcard | any } | source-port { eq port | gt port | lt port | range port-start port-end } | tcp-flag { ack | established | fin | psh | rst | syn | urg } * | time-range time-name | ttl-expired | vpn-instance vpn-instance-name ] * undo rule { deny | permit } { protocol-number | tcp } [ destination { destination-address destination-wildcard | any } | destination-port { eq port | gt port | lt port | range port-start port-end } | { { precedence precedence | tos tos } * | dscp dscp } | { fragment | first-fragment } | logging | source { source-address source-wildcard | any } | source-port { eq port | gt port | lt port | range port-start port-end } | tcp-flag { ack | established | fin | psh | rst | syn | urg } * | time-range time-name | ttl-expired | vpn-instance vpn-instance-name ] * rule [ rule-id ] { deny | permit } { protocol-num ber | udp } [ destination { destination-address destination-wildcard | any } | destination-port { eq port | gt port | lt port | range port-start port-end } | { { precedence precedence | tos tos } * | dscp dscp } | { fragment | first-fragment } | logging | source { source-address source-wildcard | any } | source-port { eq port | gt port | lt port | range port-start port-end } | time-range time-name | ttl-expired | vpn-instance vpn-instance-name ] * undo rule { deny | permit } { protocol-number | udp } [ destination { destination-address destination-wildcard | any } | destination-port { eq port | gt port | lt port | range port-start port-end } | { { precedence precedence | tos tos } * | dscp dscp } | { fragment | first-fragment } | logging | source { source-address source-wildcard | any } | source-port { eq port | gt port | lt port | range port-start port-end } | time-range time-name | ttl-expired | vpn-instance vpn-instance-name ] * rule [ rule-id ] { deny | permit } { protocol-number | gre | igmp | ip | ipinip | ospf } [ destination { destination-address destination-wildcard | any } | { { precedence precedence | tos tos } * | dscp dscp } | { fragment | first-fragment } | logging | source { source-address source-wildcard | any } | time-range time-name | ttl-expired | vpn-instance vpn-instance-name ] * undo rule { deny | permit } { protocol-number | gre | igmp | ip | ipinip | ospf } [ destination { destination-address destination-wildcard | any } | { { precedence precedence | tos tos } * | dscp dscp } | { fragment | first-fragment } | logging | source { source-address source-wildcard | any } | time-range time-name | ttl-expired | vpn-instance vpn-instance-name ] * undo rule rule-id [ destination | destination-port | { { precedence | tos } * | dscp } | { fragment | first-fragment } | logging | icmp-type | source | source-port | tcp-flag | time-range | ttl-expired | vpn-instance ] * |
|
Set the source IP address and source MAC address of offline detection packets in a VLAN. |
system-view |
access-user arp-detect vlan vlan-id ip-address ip-address mac-address mac-address undo access-user arp-detect vlan vlan-id ip-address ip-address mac-address mac-address |
Set the default source IP address of offline detection packets. |
system-view |
access-user arp-detect default ip-address ip-address undo access-user arp-detect default ip-address ip-address |
Configure a traffic suppression mode. |
system-view |
suppression mode { by-packets | by-bits } undo suppression mode |
Set the working mode of DLDP. |
system-view |
dldp work-mode { enhance | normal } undo dldp work-mode [ enhance | normal ] |
Enable MUX VLAN. |
VLAN |
mux-vlan undo mux-vlan subordinate group { vlan-id1 [ to vlan-id2 ] } &<1-10> undo subordinate group { vlan-id1 [ to vlan-id2 ] } &<1-10> subordinate separate vlan-id undo subordinate separate |
interface |
port mux-vlan enable vlan { vlan-id1 [ to vlan-id2 ] } &<1-10> undo port mux-vlan enable vlan { vlan-id1 [ to vlan-id2 ] } &<1-10> undo port mux-vlan enable |
|
Set the maximum MSS value for a TCP connection. |
system-view |
tcp max-mss mss-value undo tcp max-mss |
Priority Mapping Commands |
interface |
trust { 8021p { inner | outer } | dscp } undo trust |
Congestion Avoidance and Congestion Management Commands |
system-view |
drop-profile drop-profile-name undo drop-profile drop-profile-name |
Create a user group or displays the user group view. |
system-view |
user-group group-name undo user-group group-name |
Basic IPv6 Configuration Commands |
interface |
ipv6 ipv6 address undo ipv6 address ipv6 enable undo ipv6 enable |
DHCP Snooping Configuration Commands |
system-view |
undo dhcp enable undo dhcp snooping enable undo dhcp snooping trusted |
Configure DHCP. |
system-view |
ip pool ip-pool-name undo ip pool ip-pool-name snmp-agent trap enable feature-name dhcp undo snmp-agent trap source |
ip pool |
gateway-list ip-address &<1-8> undo gateway-list { ip-address | all } network ip-address [ mask { mask | mask-length } ] undo network ip-address [ mask { mask | mask-length } ] excluded-ip-address start-ip-address [ end-ip-address ] undo excluded-ip-address start-ip-address [ end-ip-address ] domain-name domain-name undo domain-name |
|
interface |
dhcp select global undo dhcp select global |
|
Configure or delete the DNS server address for the DHCP client. |
ip pool |
dns-list { ip-address &<1-8> | unnumbered interface interface-type interface-number } undo dns-list { ip-address | unnumbered interface | all } |
Enable or disable dynamic DNS resolution |
system-view |
dns resolve undo dns resolve |
Enable or disable DNS proxy |
system-view |
dns proxy enable undo dns proxy enable |
Configure DNS. |
system-view |
dns domain domain-name [ vpn-instance vpn-instance-name ] undo dns domain domain-name [ vpn-instance vpn-instance-name ] dns server ip-address [ vpn-instance vpn-instance-name ] undo dns server ip-address [ vpn-instance vpn-instance-name ] |
Configure switch bridge. |
system-view |
stp vlan { vlan-id1 [ to vlan-id2 ] } &<1-10> root primary undo stp vlan { vlan-id1 [ to vlan-id2 ] } &<1-10> root stp [ instance instance-id ] root primary undo stp [ instance instance-id ] root |
Configure Cluster. |
system-view |
cluster enable undo cluster enable |
Configure Stack |
system-view |
stack timer mac-address switch-delay delay-time undo stack timer mac-address switch-delay stack reserved-vlan mad restore mad exclude interface undo mad exclude interface |
Change the working mode of Ethernet interfaces from Layer 2 mode to Layer 3 mode |
interface |
undo portswitch |
Configure multi-active detection (MAD) on an interface. |
system-view |
mad detect [mode direct | mode relay] undo mad detect [mode direct | mode relay] |
Change the power supply standards of interfaces from 802.3at to 802.3af. |
interface |
poe af-inrush enable undo poe af-inrush enable |
Set the memory usage threshold. |
system-view |
set memory-usage threshold threshold-value [ slot slot-id ] undo set memory-usage threshold [ threshold-value ] [ slot slot-id ] |
Set the alarm threshold and alarm recovery threshold of CPU usage. |
system-view |
For fixed switches: cpu-usage threshold threshold-value [ restore restore-threshold-value ] [ slot slot-id ] undo cpu-usage threshold [ threshold-value [ restore [ restore-threshold-value ] ] ] [ slot slot-id ] |
Sets the CPU usage alarm threshold and CPU usage alarm recovery threshold. |
system-view |
For modular switches: set cpu-usage threshold threshold-value [ restore restore-threshold-value ] [ slot slot-id ] undo set cpu-usage threshold [ threshold-value [ restore [ restore-threshold-value ] ] ] [ slot slot-id ] |
Set the temperature alarm thresholds. |
system-view |
For fixed switches: temperature threshold slot { slot-id | all } lower-limit min-temperature upper-limit max-temperature undo temperature threshold slot { slot-id | all } |
Set the temperature alarm thresholds. |
system-view |
For modular switches: temperature threshold slot STRING<1-10> sensor INTEGER<0-127> upper-limit INTEGER<0-93> |
Configure ACL-based packet filtering globally or in a VLAN. |
system-view |
traffic-filter [ vlan vlan-id ] inbound acl { [ ipv6 ] { bas-acl | adv-acl | name acl-name } | l2-acl | user-acl } [ rule rule-id ] undo traffic-filter [ vlan vlan-id ] inboundacl { [ ipv6 ] { bas-acl | adv-acl | nameacl-name } | l2-acl | user-acl } [ rule rule-id ] |
Set the MAC address of BPDUs. |
system-view |
bpdu mac-address undo bpdu mac-address |
Configure access control for service packets based on traffic classifiers. |
traffic behavior |
permit undo permit |
Set to advertise the MED TLVs or set the MED TLVs disabled on an interface. |
interface |
lldp tlv-enable med-tlv { all | capability | inventory | location-id { civic-address device-type country-code { ca-type ca-value } &<1-10> | elin-address Tel-Number } | network-policy [ voice-vlan { vlan vlan-id [ cos cvalue | dscp dvalue ]* | 8021p [ cos cvalue | dscp dvalue ]* | untagged } ] | power-over-ethernet } undo lldp tlv-enable med-tlv { all | capability | inventory | location-id [ civic-address | elin-address ] | network-policy [ voice-vlan { vlan | cos | dscp | 8021p | untagged } ] | power-over-ethernet } |
Disables an interface from automatically recovering from the Error-Down state to the Up state. |
system-view |
undo error-down auto-recovery cause { auto-defend | bpdu-protection | efm-remote-failure | efm-threshold-event | error-statistics | link-flap | mac-address-flapping | port-security | transceiver-power-low | storm-control | data-integrity-error } |
OSPF Configuration Commands |
system-view |
ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * undo ospf process-id [ flush-waiting-timer time ] preference [ ase ] { preference | route-policy route-policy-name } * undo preference [ ase ] silent-interface { all | interface-type interface-number } undo silent-interface { all | interface-type [ interface-number ] } bandwidth-reference value undo bandwidth-reference area area-id undo area area-id abr-summary ip-address mask [ cost { cost | inherit-minimum } | [ advertise [ generate-null0-route ] | not-advertise | generate-null0-route [ advertise ] ] ] * undo abr-summary ip-address mask network network-address wildcard-mask [ description text ] undo network network-address wildcard-mask stub [ no-summary | default-route-advertise backbone-peer-ignore ] * undo stub |
Enabling or Disabling NAC re-authentication |
system-view |
mac-authen reauthenticate mac-address mac-address mac-access-profile name access-profile-name undo mac-access-profile name access-profile-name mac-authen reauthenticate undo mac-authen reauthenticate mac-authen timer reauthenticate-period reauthenticate-period-value undo mac-authen timer reauthenticate-period authentication-profilename authentication-profile-name mac-access-profile access-profile-name undo mac-access-profile |
FW CLI Whitelist
Table 6-282 lists supported CLI commands for firewalls. For the detailed command format and parameter description, see the command reference of the firewall.
Function |
View |
Command |
---|---|---|
Create or delete an interface. |
system-view |
interface interface-type interface-number undo interface interface-type interface-number |
Create or delete a common interface group. |
system-view |
interface-group [ interface-group-id ] name interface-group-name undo interface-group { interface-group-id | name interface-group-name } |
Configure traditional local management parameters (SSH and Telnet). |
system-view |
ssh user user-name undo ssh user user-name ssh user user-name authentication-type password undo ssh user user-name authentication-type ssh user user-name service-type stelnet undo ssh user user-name service-type telnet server enable undo telnet server enable |
Configure policy-based routing. |
policy-based-route |
rule copy rule-name new-rule-name rule move rule-name1 { { after | before } rule-name2 | up | down | top | bottom } rule name rule-name rule rename old-name new-name |
Configure an ACL. |
system-view |
acl [ number ] acl-number [ vpn-instance vpn-instance-name ] undo acl { all | [ number ] acl-number } |
Configure traditional local management parameters (HTTP and HTTPS). |
system-view |
web-manager enable [ port port-number ] web-manager security enable [ port port-number ] undo web-manager enable [ port port-number ] undo web-manager security enable [ port port-number ] |
Configure PPPoE. |
interface |
dialer enable-circular undo dialer enable-circular dialer number dial-number [ autodial ] undo dialer number dial-number |
system-view |
dialer-rule undo dialer-rule |
|
interface |
dialer-group group-number undo dialer-group dialer timer idle seconds undo dialer timer idle restart |
|
Enable a 3G/4G card. |
system-view |
apn profile profile-name undo apn profile profile-name |
interface cellular interface-number |
ip address negotiate undo ip address negotiate |
|
interface cellular |
apn-profile undo apn-profile |
|
Enable intelligent outbound selection to load balance traffic among multiple links. |
system-view |
multi-interface |
multi-interface |
add interface { interface-name | interface-type interface-num } [ { { weight weight-value } | { priority priority-value } }* ] add interface-group { group-name | isp isp-name} [ { { weight weight-value } | { priority priority-value } }* ] mode { proportion-of-bandwidth | proportion-of-weight | priority-of-userdefine } undo mode priority-of-link-quality protocol { icmp | tcp-simple } undo priority-of-link-quality protocol priority-of-link-quality parameter { delay | jitter | loss }* undo priority-of-link-quality parameter priority-of-link-quality {interval INTEGER<1-10> | times INTEGER<2-10>}* undo priority-of-link-quality {interval | times}* priority-of-link-quality mask INTEGER<1-32> undo priority-of-link-quality mask load-balance flow hash { destination-ip | destination-port | source-ip | source-port }* multi-interface priority-of-link-quality parameter { delay accuracy delay-accuracy | jitter accuracy jitter-accuracy } undo multi-interface priority-of-link-quality parameter { delay accuracy | jitter accuracy } standby-interface status down undo standby-interface status session persistence enable undo session persistence enable session persistence source-ip mask <src-mask-value> session persistence destination-ip mask <dst-mask-value> undo session persistence { source-ip | destination-ip }* mask session persistence table aging-time <aging-time-value> undo session persistence table aging-time session persistence mode { source-ip | destination-ip }* undo session persistence mode |
|
diagnose |
reset session persistence table |
|
rule |
action pbr egress-interface multi-interface undo action pbr egress-interface multi-interface |
|
Configure that server certificate validation is not required during the upload of log files to the FTPS server. |
system-view |
gawa-log non-certificate undo gawa-log non-certificate |
Set the maximum MSS value for a TCP connection. |
system-view |
tcp max-mss mss-value undo tcp max-mss |
Display the diagnose view. |
system-view |
diagnose |
ISP Link Selection Configuration Commands |
interface-group |
add interface undo add interface |
multi-interface |
add interface-group undo add interface-group |
|
Configure the country or region where the FW is deployed. |
system-view |
country country-code undo country |
Display the IPSec intelligent link selection profile view. |
system-view |
ipsec smart-link profile profile-name undo ipsec smart-link profile profile-name |
Add links for IPSec intelligent link selection. |
system-view |
link link-id interface interface-type interface-number [ local local-address ] [ nexthop nexthop-address ] remote remote-address undo link link-id |
Switch links for IPSec intelligent link selection. |
system-view |
auto-switch preempt enable undo auto-switch preempt enable |
Disable an interface in Error-Down state to go Up. |
system-view |
undo error-down auto-recovery cause { auto-defend | bpdu-protection | efm-remote-failure | efm-threshold-event | error-statistics | link-flap | mac-address-flapping | port-security | transceiver-power-low | storm-control | data-integrity-error } |
Configuring AP Services
An AD9431DN-24X in cloud management mode is subject to the following limitations:
- It only coordinates radio resources of managed RUs but is not involved in the roaming, radio calibration, or load balancing service with other cloud APs (including cloud central APs).
- It does not support NAT, IPSec VPN, SAC application identification, IoT, or Bluetooth, and cannot serve as a PPPoE client.
Configuring an SSID
Context
When an end user searches for available wireless local area networks (WLANs), the network names displayed are SSIDs. An authentication mode can be specified for each SSID to perform access control for end users.
Only one authentication mode can be specified for each SSID, and the WLAN selected by an end user determines the authentication mode. Multiple SSIDs can be deployed on one AP. For example, employees and guests access the Internet using different SSIDs and different authentication modes.
Procedure
- Select a site.
- Choose from the main menu.
- In the displayed window, select a site from the Site drop-down list in the upper left corner.
- Choose the Site Configuration tab.
- Choose Create, and configure basic information of an SSID. from the navigation pane, click
- If you change the values of SSID hiding, Limit access of traditional terminals, Maximum number of users, U-APSD, and WMM Scene, connected STAs are disconnected and then reconnected.
- The AP4051TN, AP6750-10T, AP8050TN-HD, AP350, AirEngine 8760R-X1E, AirEngine 8760-X1-PRO, AirEngine 6760-X1, AirEngine 6760-X1E, and AirEngine 5760-51 support three radios, that is, 2.4G (wlan-radio 0/0/0), 5G (wlan-radio 0/0/1), and 5G (wlan-radio 0/0/2). APs of other models support the radios other than 5G (wlan-radio 0/0/2). When three radios are required on the AirEngine 6760-X1, AirEngine 6760-X1E, and AirEngine 5760-51, set RF mode to Triple-radio.
- The NAT mode is not supported on the AirEngine9700D-M and AD9431DN-24X.
- Click Next and configure an authentication mode for end users connecting to the SSID.
The following table lists the authentication modes in different authentication scenarios.
Table 6-283 Mapping between authentication modes and configurationsAuthentication Scenario
Authentication Mode
Configuration Procedure
iMaster NCE-Campus functions as the authentication server.
Portal authentication
802.1X authentication
MAC authentication
iMaster NCE-Campus functions as a relay server.
API-based portal authentication
Portal authentication in RADIUS relay mode
RADIUS authentication
Third-party server connected to iMaster NCE-Campus.
Interconnection with a portal server
Interconnection with a RADIUS server
- Click Next and configure SSID-based policy control, such as SSID-based rate limiting, terminal rate limiting, IPv6, and ACLs.
Parameter Description
Parameter |
Description |
|
---|---|---|
Basic Settings |
SSID Name |
SSID when a STA connects to a wireless network. NOTE:
If the SSID name contains Chinese characters, it may be displayed as garbled characters on terminals running Windows. |
Working status |
The default value is ON. If the value is set to OFF, the SSID is unavailable. |
|
Scheduled switch-on |
Time range during which the SSID is enabled. The SSID is disabled beyond the time range. This improves the network security and saves energy. If the preconfigured time policy cannot meet flexibility requirements, click NOTE:
|
|
Effective radio |
Triple-frequency bands are used by default. The default value is recommended. NOTE:
Only the AP4051TN and AP8050TN-HD support 5G (wlan-radio 0/0/2). |
|
AP tags |
The label specifies the AP where the SSID is configured. If the value is empty, the SSID is configured on all APs in the site. Otherwise, you need to add a label for the AP as prompted. |
|
Network connection mode |
|
|
VLAN |
This parameter is available only when the value of Network connection mode is Layer 2 forwarding. The VLAN ID of an AP is assigned to a STA that is associated with an SSID based on the label. NOTE:
If the same AP has multiple labels that correspond to different VLAN IDs, the VLAN ID with the smallest priority takes effect. |
|
Advanced Configuration |
SSID hiding |
By default, this function is disabled. After this function is enabled, SSIDs are invisible. |
MDNS Snooping |
By default, this function is disabled. After this function is enabled, the access device can parse service information in mDNS packets sent by wireless terminals and identify the terminals. |
|
Disable AP after AP disconnection |
By default, this function is disabled. After this function is enabled, the SSID will be automatically disabled if the AP uplink is disconnected. This ensures that the device can automatically connect to other APs. |
|
Band steering (5G-prioritized) |
By default, this function is enabled. The band steering function enables an AP to steer STAs to the 5 GHz frequency band first, which reduces load and interference on the 2.4 GHz frequency band. User experience is therefore improved. |
|
Transmit rate of 2.4G Beacon frames (Mbit/s) |
Transmit rate of 2.4 GHz Beacon frames and 5 GHz Beacon frames, in Mbit/s. Only APs running V200R009C00 or a later version support these parameters. |
|
Transmit rate of 5G Beacon frames (Mbit/s) |
||
Limit access of traditional terminals |
By default, this function is disabled. After this function is enabled, 802.11a, 802.11b, and 802.11g traditional terminals cannot be connected. |
|
Maximum number of users |
Maximum number of STAs connected to the SSID. |
|
Access threshold policy |
|
|
User isolation |
By default, this function is enabled. After this function is enabled, STAs connected to the SSID of a certain AP are isolated from each other. |
|
Isolation mode |
|
|
IGMP-Snooping |
By default, this function is disabled. After IGMP snooping is enabled, multicast data can be forwarded and controlled at the data link layer. |
|
Disable broadcast or multicast |
By default, this function is disabled. After this function is enabled, WLAN sharing and broadcast or multicast discovery is disabled, and the Bonjour transparent transmission parameter becomes configurable. |
|
Multicast-to-unicast conversion |
By default, this function is disabled. After this function is enabled on an AP, the AP listens on Report and Leave messages to maintain multicast-to-unicast entries. When sending multicast packets to the client, the AP converts the multicast data packets to unicast data packets based on the multicast-to-unicast entries to improve multicast traffic transmission efficiency. After adaptive multicast-to-unicast conversion is enabled, when the air interface performance encounters a bottleneck during multicast-to-unicast conversion, an AP automatically switches the multicast group containing the minimum number of STAs to the multicast mode. After the air interface performance is improved and keeps being improved for a period of time, the AP automatically switches the multicast group containing the maximum number of STAs to the unicast mode. In this way, the air interface performance is automatically adjusted without manual intervention, improving wireless user experience. |
|
Bonjour transparent transmission |
By default, this function is disabled. Bonjour is a Zeroconf solution proposed by Apple and applies to Layer 2 broadcast domains. It allows network devices in a Layer 2 broadcast domain to obtain IP addresses and discover services. |
|
U-APSD |
By default, this function is disabled. U-APSD is a new energy saving mode defined for WMM, which can improve the energy-saving capability of STAs. Some STAs may not well support U-APSD. In this case, you need to disable U-APSD. |
|
WMM scenario |
Set the WMM parameter based on the network requirements to enable high-priority data packets to occupy wireless channels, namely, adjusting the forwarding priority of video and voice service traffic. To make the WMM function take effect, you need to enable the WMM function switch among the radio parameters. The options of this parameter are as follows:
NOTE:
Only APs running V200R008C10 or a later version support WMM function. |
|
Terminal MAC address filtering |
By default, this function is disabled. After this function is enabled, the system filters the MAC addresses of the devices connected to the network according to the blacklist or whitelist.
|
|
Audio quality analysis |
By default, this function is disabled. If this function is enabled and the SIP port is configured, the system will enable the SIP protocol. In this case, devices can capture SIP packets and analyze the service type of the packets, such as the voice service. If iMaster NCE-Campus allows devices to report performance data to the analyzer, the analyzer can obtain the performance data of the voice service and analyze the voice call quality. |
|
802.11r Fast Roaming Enable |
Whether to enable 802.11r fast roaming function. The options are as follows:
|
|
802.11r over the DS |
802.11r fast roaming mode.
|
|
Reassociation timeout interval(s) |
Timeout period for reassociation. The default value is 1 second. |
|
Device-pipe synergy roaming |
Whether to enable device-pipe collaborative roaming. This function is disabled by default. |
|
Service assurance mode |
|
|
Mobile game acceleration |
Whether to enable the mobile game acceleration function. The default value is enable. This function is supported on the following mobile game applications: PlayerUnknown's Battlegrounds (PUBG), PUBG Mobile, Crossfire, Knives Out, Honor of Kings, DNF, Fantasy Westward Journey, League of Legends, Fortnite, and Identity V. After this function is enabled, the uplink and downlink rates will be accelerated for the mobile game applications that support this function. |
|
Suppressing UE power saving |
Whether to enable the function of preventing terminals from entering energy-saving mode. After the function is enabled, the terminals consume more power and extra bandwidth. If no terminal unexpectedly enters energy-saving state, you are advised to disable the function. This function is disabled by default. |
|
MU-MIMO |
Whether to enable MU-MIMO optimization. In an environment with less interference, the MU-MIMO optimization function meets user requirements for high downlink throughput of APs. This function is enabled by default. |
|
Terminal aging time (minutes) |
Time when weak-signal terminals are forced offline. To prevent user experience deterioration when a large number of weak-signal STAs access the network, you can reduce the aging time of these STAs. |
Parameter |
Description |
|
---|---|---|
SSID-based rate limiting |
Limit the uplink or downlink bandwidth of a single SSID. |
|
Static terminal rate limiting |
Whether to configure static rate limiting for a single terminal to limit its uplink and downlink bandwidths separately. If both static and dynamic terminal rate limiting functions are enabled, static terminal rate limiting takes effect. |
|
Dynamic terminal rate limiting |
Whether to enable dynamic rate limiting for a single terminal. If this function is enabled, the uplink and downlink bandwidths of each terminal are limited separately. If both static and dynamic terminal rate limiting functions are enabled, static terminal rate limiting takes effect. |
|
Advanced Configuration |
IPV6 |
Whether to enable IPv6 for the SSID. |
ACL |
Configure ACL-based packet filtering to permit or reject the packets matching ACL rules. You can select an ACL from the drop-down list box. NOTE:
Choose from the main menu. You can manage ACL templates in a centralized manner. |
|
Application traffic statistics collection |
After this function is enabled, APs parse packets from users to collect the network usage statistics about each user application. NOTE:
AP2050DN, AP2050DN-E, AP2050DN-S, AP4050DN-E, AP4050DN-HD, AP6050DN(256M), AP6150DN(256M), AP7050DE(256M), AP8030DN, AP8130DN, R230D, R240D, R250D, R250D-E, R251D, R251D-E, R450D and the AirEngine series(excluding AP7060DN and AirEngine5760-10) do not support application traffic statistics collection. |
|
APP filtering list |
Configure blocking, CAR, and DSCP marking policies for network packets of certain applications. If you want to learn supported applications in the AP signature database, visit https://support.huawei.com/enterprise/en/doc/EDOC1000183795. NOTE:
AP2050DN, AP2050DN-E, AP2050DN-S, AP4050DN-E, AP4050DN-HD, AP6050DN(256M), AP6150DN(256M), AP7050DE(256M), AP8030DN, AP8130DN, R230D, R240D, R250D, R250D-E, R251D, R251D-E, R450D and the AirEngine series(excluding AP7060DN and AirEngine5760-10) do not support APP filtering. |
|
URL filtering |
By default, this function is disabled. After enabling this function, configure a URL filtering policy to limit network resources accessed by STAs.
NOTE:
|
|
IPSEC ACL |
Use ACLs to configure IPsec policies to implement priority-based processing of data packets meeting related conditions. |
Configuring Radio Parameters
Context
WLAN technology uses radio signals (such as 2.4 GHz or 5 GHz radio waves) as transmission medium. To prevent signal interference, neighboring APs must transmit wireless signals over non-overlapping channels. You can adjust channels and power of APs to ensure that the APs work at the optimal performance.
APs need to be configured with parameters including the handshake protocol, air interface scanning parameters, and antenna gain to control the wireless coverage area of the APs and reduce the radio interference and data transmission collisions. The radio function can be enabled or disabled periodically to reduce unnecessary power consumption.
In different countries and areas, laws and regulations define different working channels and power for wireless communication. When APs are deployed, radio parameters must comply with local laws and regulations.
For details about constraints, visit the following website to download Country codes & Channels compliance status.
Procedure
- Select a site.
- Choose from the main menu.
- In the displayed window, select a site from the Site drop-down list in the upper left corner.
- Choose the Site Configuration tab.
- Choose Basic Settings area. from the navigation pane, and configure basic radio parameters in the
d
- (Optional) Expand Advanced Settings and set radio calibration parameters as needed.
- (Optional) In the Channel Planning area, click
next to the target AP, click Edit for 2.4 GHz/5 GHz radio, and set radio parameters.
- The default values of the channel and transmit power depend on the AP model and country code. Set these two parameters for all APs based on the RF planning.
- If Calibration mode is set to Automatic or Timing, the radio parameters on the page are not updated in real time since iMaster NCE-Campus cannot actively detect the AP calibration result. To manually trigger radio calibration, click Immediate Calibration, and the parameters on the page will be updated based on the actual calibration result. You can view the real-time progress when performing manual radio calibration by clicking Refresh.
- If you change the values of WMM parameters, connected STAs will be disconnected and then reconnected.
- Currently, only the AP4051TN and AP8050TN-HD support triple frequency bands. For devices that support 5G dual frequency bands, set the channel of wlan-radio 0/0/1 to the high frequency channel and that of wlan-radio 0/0/2 to the low frequency channel.
To view supported channels on an AP, you can run the display ap configurable channel ra 1 command on the AP to check the channel of wlan-radio 0/0/1 and the display ap configurable channel ra 2 command to check the channel of wlan-radio 0/0/2.
Parameter Description
Parameter |
Description |
---|---|
Country/Region |
Region where the tenant network belongs. After Region is selected based on the region where the AP is deployed, the AP resets the working channel and power of the radio based on local laws and regulations and adjusts the configurable channel range and power. |
Schedule for enabling radio |
Time range during which the radio is enabled. The radio is disabled beyond the time range. This improves the network security and saves energy. If the preconfigured time policy cannot meet flexibility requirements, click |
Calibration mode |
Radio calibration mode. You are advised to use Timing mode and set the optimization time to off-peak hours (for example, 00:00-06:00 at the local time).
|
Calibration policy |
The calibration policy takes effect only in automatic radio calibration mode. You are advised to use scheduled optimization and set the optimization time to off-peak hours (for example, 00:00-06:00).
|
AI-powered calibration |
This function is enabled by default and takes effect when the system connects to the CampusInsight. If the CampusInsight is not connected, the device automatically uses the original mode for optimization. After the AI optimization function takes effect, the device automatically optimizes the AI algorithm based on the historical data of the device within seven days. If the interference source around the device changes during the day and night, this function has good optimization effect. |
RF mode |
Radio mode of the AP. |
Parameter |
Description |
|
---|---|---|
2.4GHz |
DCA channel set (20MHz) |
Channel set used by an AP to transmit wireless signals at the 2.4 GHz frequency band. To reduce AP co-channel or adjacent-channel interference, the system selects a channel from the channel set based on the neighbor relationship between APs and allocates a channel to each AP based on Dynamic Channel Allocation (DCA).
|
GI mode |
Set the guard interval (GI) mode. This parameter is valid for APs running V200R009C00 or a later version.
|
|
TPC cap threshold calibration (dBm) |
Transmit power range after radio calibration is completed, in dBm. The default value is 9 dBm to 127 dBm. If the lower threshold is too low, the power may be low and cannot meet radio coverage requirements after radio calibration is performed. If the upper threshold is too high, the power may be high and interferences occur between APs after radio calibration is performed. |
|
TPC floor threshold calibration (dBm) |
||
Access user count limit |
Set the maximum number of STAs that can access the AP on the 2.4 GHz frequency band. The default value is 64. Access threshold policy:
|
|
Upper threshold of access users |
||
Access threshold policy |
||
Radio coverage threshold |
Transmit Power Control (TPC) threshold, in dBm. The default value is -60 dBm. The threshold is adjusted based on the AP deployment height and distance to achieve optimal coverage after radio calibration is performed. A higher threshold indicates higher power adjusted by TPC. |
|
Multicast transmit rate |
The configured multicast transmit rate must be in the basic rate set or supported rate set, and supported by the STA. Otherwise, the STA cannot receive multicast data. |
|
Base rate (Mbit/s) |
2.4 GHz. |
|
Support rate (Mbit/s) |
2.4 GHz. |
|
Kick off weak-signal terminals |
Whether to kick off weak-signal terminals. After this function is enabled, APs kick off detected weak-signal terminals. |
|
Scene |
After Kick off weak-signal terminals is enabled, APs check connected terminals based on Signal-to-noise Ratio Threshold and Detection Cycle.
|
|
Signal-to-noise Ratio Threshold (dB) |
||
Detection Cycle (ms) |
||
Dual-band dynamic adjustment |
Whether to enable dual-band dynamic adjustment. This function is disabled by default. |
|
Interference rate environment deterioration threshold |
The environment deteriorates if the interference rate exceeds the threshold. |
|
Number of times that the threshold is exceeded |
Number of times that the interference rate exceeds the threshold. |
|
Redundant 2.4G radio adjustment mode |
Processing mode of the redundant radio. This parameter is valid only when Dynamic switch frequency is set to On.
|
|
Ultimate power |
If obstacles exist or signals are not covered, the signals with higher power are used to implement signal coverage.
|
|
Bandwidth reservation ratio for VIPs |
Ratio of the bandwidth reserved for VIP users. This parameter is configured to guarantee the bandwidth for VIP users. The air interface bandwidth reservation algorithm for VIP users is implemented based on RU allocation in downlink and uplink OFDMA transmission mode. This algorithm evaluates the spectrum resources required by users in real time and reserves or allocates spectrum resources for VIP users to meet their service requirements.
|
|
5GHz |
Calibration bandwidth |
DCA channel bandwidth used by an AP to transmit wireless signals at the 5 GHz frequency band. A higher-bandwidth channel indicates a higher transmission rate. |
Channel set |
Channel set used by an AP to transmit wireless signals at the 5 GHz frequency band. To achieve optimal calibration, use three or more than three optional channels. NOTE:
|
|
Basic rate (Mbit/s) |
5 GHz base rates. |
|
Supported rate (Mbit/s) |
5 GHz supported rates. |
|
GI mode |
Set the guard interval (GI) mode. This parameter is valid for APs running V200R009C00 or a later version.
|
|
TPC cap threshold calibration (dBm) |
Transmit power range after radio calibration is completed, in dBm. The default value is 12 dBm to 127 dBm. If the lower threshold is too low, the power may be low and cannot meet radio coverage requirements after radio calibration is performed. If the upper threshold is too high, the power may be high and interferences occur between APs after radio calibration is performed. |
|
TPC floor threshold calibration (dBm) |
||
Access user count limit |
Set the maximum number of STAs that can access the AP on the 5 GHz frequency band. The default value is 64. Access threshold policy:
|
|
Upper threshold of access users |
||
Access threshold policy |
||
Radio coverage threshold |
Transmit Power Control (TPC) threshold, in dBm. The default value is -60 dBm. The threshold is adjusted based on the AP deployment height and distance to achieve optimal coverage after radio calibration is performed. A higher threshold indicates higher power adjusted by TPC. |
|
A-MSDU |
Enable the MAC Protocol Data Unit (MPDU) aggregation function. |
|
Maximum number of subframes |
Maximum number of subframes that can be aggregated into an A-MSDU at one time. |
|
Multicast transmit rate |
Configure the maximum length of an A-MPDU. |
|
Kick off weak-signal terminals |
Whether to kick off weak-signal terminals. After this function is enabled, APs kick off detected weak-signal terminals. |
|
Scene |
After Kick off weak-signal terminals is enabled, APs check connected terminals based on Signal-to-noise Ratio Threshold and Detection Cycle.
|
|
Signal-to-noise Ratio Threshold (dB) |
||
Detection Cycle (ms) |
||
Interference rate environment deterioration threshold |
The environment deteriorates if the interference rate exceeds the threshold. |
|
Number of times that the threshold is exceeded |
Number of times that the interference rate exceeds the threshold. |
|
Ultimate power |
If obstacles exist or signals are not covered, the signals with higher power are used to implement signal coverage.
|
|
Bandwidth reservation ratio for VIPs |
Ratio of the bandwidth reserved for VIP users. This parameter is configured to guarantee the bandwidth for VIP users. The air interface bandwidth reservation algorithm for VIP users is implemented based on RU allocation in downlink and uplink OFDMA transmission mode. This algorithm evaluates the spectrum resources required by users in real time and reserves or allocates spectrum resources for VIP users to meet their service requirements.
|
|
General parameters |
Beacon interval (TUs) |
Interval at which an AP sends Beacon frames. The default value of 100 ms is recommended. An AP sends Beacon frames at intervals to notify STAs of an existing 802.11 network. After an STA receives a Beacon frame, it can modify parameters used to connect to the 802.11 network. A long interval for sending Beacon frames lengthens the dormancy time of STAs, while a short interval for sending Beacon frames increases air interface costs. |
RTS-CTS mode |
Working mode of Request To Send/Clear To Send (RTS-CTS). RTS-CTS prevents data transmission failures caused by channel conflicts. The default value cts-to-self is recommended.
|
|
Airtime fair scheduling |
Airtime fair scheduling preferentially schedules users who occupy the channel for a short time. In this way, each user is assigned equal time to occupy the channel, ensuring fairness in channel usage. By default, this function is enabled. |
|
Packet-based power control |
Packet-based power control technology detects the signal strength of STAs in real time to conserve energy. If an AP detects that the signal strength of a STA is strong (for example, the STA is close to the AP), the AP reduces its transmit power when sending packets. If an AP detects that the signal strength of a STA is weak (for example, the STA is far away from the AP), the AP uses the normal transmit power to send radio signals. By default, this function is enabled. |
|
Beamforming |
Beamforming can enhance signals at an angle (for target users), attenuate signals at another angle (for non-target users or obstacles), and control the signal transmission direction and coverage area. By default, this function is disabled. NOTE:
For details about beamforming requirements, see "beamforming enable" page in related AP product documentation. |
|
Load balance |
In scenarios where APs are close to each other and there is a high degree of overlap between APs' coverage ranges, you can configure load balancing to evenly distribute user traffic to different APs and ensure wireless network experience of each STA. When a STA attempts to connect to a WLAN, the AP that receives the access request of the AP evaluates the current load based on the number of online STAs and its maximum capability. If the load is much higher than the average load of a neighboring AP in the same AP group, the AP rejects the access request. |
|
Smart roaming |
Enables smart roaming. When STAs connected to an AP have weak signals, their network access rates are low. In this situation, if many low-rate STAs connect to the AP, air interface occupation time of other STAs is reduced. As a result, the AP throughput decreases, degrading user experience. To prevent this situation, configure forced logout of weak-signal STAs. When detecting that the SNR or access rate of a STA is lower than the specified threshold, the AP sends a Disassociation packet to the STA to force the STA offline so that the STA can reconnect to the WLAN. After enabling smart roaming and configuring the smart roaming threshold, APs forcibly disconnect STAs with SNR or access rate lower than the threshold. |
|
Scan duration (ms) |
Duration during which an AP continuously scans the air interface. The AP continuously scans surrounding radio signals during the duration. After the scanning is complete, the AP sends collected information to iMaster NCE-Campus for radio calibration and spectrum analysis. A longer scanning time indicates more collected data and more accurate data analysis result. However, scanning for a long time consumes too many system resources, which may affect normal services. Therefore, you are advised to use the default value of 60 ms. |
|
Scan interval (ms) |
Interval at which an AP scans the air interface. The default value of 10000 ms is recommended. |
|
Channel to scan |
Channel set where an AP scans the air interface. The default value is Channel in region.
|
|
WMM |
Whether to enable the Wi-Fi Multimedia (WMM) function. NOTE:
Only APs running V200R008C10 or a later version support WMM function. |
|
Channel contention parameters |
WMM classifies packets into four access categories (ACs): AC_VO (voice), AC_VI (video), AC_BE (best effort), and AC_BK (background). Each AC queue defines a set of EDCA parameters, which determine the capability of occupying channels. These parameters ensure that a higher-priority AC queue has a higher probability to preempt channels than a lower-priority AC queue. EDCA parameters are as follows:
ACK policy:
|
|
Dynamic BE optimization |
Dynamic optimization of the Best Effort (BE) service. After this function is enabled, the AP dynamically reduces the air interface resources consumed by terminals based on the number of access users by using algorithm. This saves more resources for the BE service, improving user experience. In the BE service, packets arriving first are forwarded first. However, the BE service does not ensure the delay, jitter, packet loss rate, or reliability of transmission. |
|
BE optimization threshold (packets/second) |
Threshold for BE optimization algorithm. You are advised to retain the default value. |
|
Multimedia dynamic optimization |
After this function is enabled, the AP dynamically reduces the air interface resources consumed by terminals based on the number of access users by using algorithm. This saves more resources for audio and video applications, improving user experience. |
|
Audio optimization threshold (packets/second) |
Optimization thresholds for audio and video applications. You are advised to retain the default value. |
|
Video optimization threshold (packets/second) |
||
Scene |
This parameter is displayed when both Dynamic BE optimization and Multimedia dynamic optimization are disabled. Set the WMM parameter based on the network requirements to enable high-priority data packets to occupy wireless channels, namely, adjusting the forwarding priority of video and voice service traffic. To make the WMM function take effect, you need to enable the WMM function switch among the radio parameters. The options of this parameter are as follows:
|
Parameter |
Description |
---|---|
Radio status |
Whether the radio status is enabled. By default, the radio is enabled. |
Frequency bandwidth |
Working bandwidth. The default value is 20mhz.
|
Automatic channel selection |
When Frequency bandwidth is set to Calibration Bandwidth, the channel is automatically selected. |
Channel |
Frequency band over which radio signals are transmitted. To prevent signal interference, ensure that adjacent APs work in non-overlapping channels. To avoid radio interference, it is recommended that non-overlapping channels (such as channels 1, 6, and 11) be planned for neighboring APs at 2.4 GHz frequency band. |
Automatic bandwidth selection |
(For 5G radio only) When Frequency bandwidth is set to Calibration Bandwidth, the radio bandwidth can be dynamically adjusted without being restricted by the existing calibration bandwidth. |
Automatic power selection |
Whether to enable automatic power selection. When this function is disabled, the transmit power can be manually adjusted. |
Transmit power level |
Transmit power of a radio. The transmit power must ensure that radio signals meet network requirements and the quality of radio signals is improved. |
Antenna gain |
The antenna gain is used to measure the antenna's capability to transmit and receive signals at a specified direction. A higher antenna gain indicates a longer signal transmission distance. The value is the actual gain of an antenna used by an AP. |
Redundant radio adjustment |
(For 2.4G radio only) Whether to enable the redundant radio adjustment function for the 2.4G radio of the current device. After setting this parameter to On, ensure that Dual-band dynamic adjustment in Advanced Settings is set to On. Otherwise, this function does not take effect on the target device. |
Configuring AP Security Services
Context
With the popularization of Internet technologies and diversity of network applications, network attacks occur more and more frequently. You can configure security policies for APs to improve network security. In addition, iMaster NCE-Campus allows you to modify AP security policies in a blacklist or whitelist.
- Configure static MAC addresses for uplink devices connected to APs or trusted users to ensure security communication.
- Configure WLAN security policies to detect and take countermeasures against unauthorized APs, protecting the network and users of an enterprise from being accessed by unauthorized device.
- Enable attack defense. After this function is enabled, APs analyze and report the contents and behavior of packets processed by CPUs to determine whether packets have attacking features. The APs take defense measures to the packets with attacking features.
- Control the access from STAs to APs by using:
- Blacklist of MAC addresses
- Whitelist of MAC addresses or OUIs
- Configure packet rate limiting. The rates of APs' broadcast packets and IGMP multicast packets are limited to proper values to prevent these packets from occupying too many network resources. Only APs of V200R009C00 or a later version support this function.
Security Configuration |
Description |
---|---|
Detection of brute force key cracking attacks |
An AP checks whether the number of key negotiation failures occurring during WPA/WPA2-PSK, WAPI-PSK, or WEP-Share-Key authentication of a user exceeds the threshold (20). If so, the AP considers that the user is using the brute force method to crack the password. |
Spoofing attack detection |
An AP checks whether the source MAC address of a packet is its MAC address when receiving broadcast Disassociation packets or Deauthentication packets. If so, the AP considers that the WLAN is under the spoofing attack of Disassociation or Deauthentication packets. |
Rogue device detection |
An AP can detect information about wireless devices in its coverage range, and determines accordingly whether rogue devices exist on the WLAN. |
Flood attack detection |
An AP monitors the traffic volume of each STA to prevent flooding attacks. If the traffic volume of an STA exceeds the threshold (for example, the AP receives more than 100 packets from an STA within 1 second), the AP considers this STA to be flooding packets. |
Weak IV detection |
An AP checks whether a packet carries a weak IV (whose first byte value is in the range from 3 to 15 and second byte value is 255). |
Defense using dynamic blacklist |
If detecting a user flooding packets or using the brute force method to crack passwords, an AP adds the user to the dynamic blacklist and discards all packets of the user until the dynamic blacklist entry expires (after 10 minutes). |
Manual containment |
An AP takes countermeasures against rogue devices based on the device types (AP or STA). |
Fake AP containment |
An AP uses the MAC address of a fake AP to broadcast Deauthentication packets to take countermeasures against the fake AP, preventing STAs from connecting to the fake AP again. |
Ad-hoc device containment |
An AP uses the MAC address of an ad-hoc device to continuously send unicast Deauthentication packets, disconnecting rogue devices. |
Open device containment |
An AP uses the MAC address of a rogue AP using open authentication to broadcast Deauthentication packets to counter the rogue AP, preventing STAs from connecting to the rogue AP again. |
STA protection |
An AP uses the MAC address of a rogue AP connected to protected STAs to continuously send unicast Deauthentication packets, disconnecting the rogue AP. |
Procedure
- Configure static MAC addresses for uplink devices connected to APs or trusted users.
- Select a site.
- Choose from the main menu.
- In the displayed window, select a site from the Site drop-down list in the upper left corner.
- Choose the Site Configuration tab.
- Choose Static MAC Limit tab page. from the navigation pane, and enter the
- Select a device and click Create.
- Set MAC Address, VLAN ID, and Interface Name, and click Submit.
- Click Apply. The "Operation succeeded." message is displayed.
- Select a site.
- Configure a WLAN security policy.
- Select a site.
- Choose from the main menu.
- In the displayed window, select a site from the Site drop-down list in the upper left corner.
- Choose the Site Configuration tab.
- Choose WLAN Security tab page. from the navigation pane and enter the
- Set Security level based on the detection and defense items, and set parameters as needed.
- Select a site.
- Configure an attack defense policy.
- Select a site.
- Choose from the main menu.
- In the displayed window, select a site from the Site drop-down list in the upper left corner.
- Choose the Site Configuration tab.
- Choose Attack Defense tab page. from the navigation pane and enter the
- Enable the desired attack defense functions and set a transmission rate for the defended packets.
- Select a site.
- Configure a STA MAC address blacklist.
- Select a site.
- Choose from the main menu.
- In the displayed window, select a site from the Site drop-down list in the upper left corner.
- Choose the Site Configuration tab.
- Choose Blacklist/Whitelist tab page. from the navigation pane, and enter the
- Configure a STA MAC address blacklist.
- Select a site.
- Configure rate limiting for broadcast and multicast packets.
- Select a site.
- Choose from the main menu.
- In the displayed window, select a site from the Site drop-down list in the upper left corner.
- Choose the Site Configuration tab.
- Choose Storm Suppression tab page. from the navigation pane, and enter the
- Set parameters for limiting the rates of broadcast and multicast packets.
- Select a site.
Parameter Description
Parameter |
Description |
---|---|
MAC whitelist |
If a rogue AP is detected but matches the authorized AP list, the AP is considered authorized and will not be contained. This parameter is valid when Rogue device detection is enabled. |
OUI whitelist |
|
SSID whitelist |
|
MAC address list for manual device containment |
MAC addresses of rogue devices that are specified manually for containment. This parameter is valid when Manual device containment is enabled. Alternatively, you can choose AP > Security under Monitor > Health > Devices 360 menu, access the Risky Device Detection tab page, and click Add Manual Contain to add target devices to this list. |
Spoofing SSID rule list |
Specifies the regular expression for an SSID. If an SSID matches the regular expression, the SSID is considered a spoofing one. This parameter is valid when Rogue device detection is enabled. |
MAC address list for terminal protection |
MAC addresses of authorized STAs that need to be protected from getting connected to rogue APs. This parameter is valid when Terminal protection is enabled. |
Attack Defense Type |
Description |
---|---|
Abnormalities |
An attacker sends malformed IP packets to the target system. Then the system may crash when processing such packets. |
Packet fragments |
An attacker sends a large number of fragmented packets to the target system to consume memory resources of the target system. As a result, the target system cannot respond to normal IP packets. |
ICMP flood |
An attacker sends a large number of ICMP packets to the attack target within a short period of time, exhausting sessions of network devices and leading to network breakdown. Attacks of oversized ICMP packets will also result in congestion of network links. |
TCP SYN |
An attacker sends a large number of packets with forged IP addresses to the target system, so the target system cannot reply packets to the correct destination addresses, exhausting host resources. |
UDP flood |
An attacker sends a large number of UDP packets to the target system in a short period of time and requests for responses. The target system then is overloaded and cannot process valid tasks. |
Parameter |
Description |
---|---|
MAC Address |
Unique code of a terminal address. |
VLAN ID |
Code of a virtual local area network (VLAN). |
Interface Name |
AP interface. A combination of the same MAC address and Vlan ID can be bound to only one interface. |
Parameter |
Description |
---|---|
Binding type |
(Optional) Use either of the following policies to control STA access to APs. Broadcast, multicast, or all-0 MAC addresses or OUIs are not supported. You can configure up to 2048 records.
|
Parameter |
Description |
---|---|
ALL |
Whether to enable rate limit for all broadcast packets and IGMP multicast packets on an AP. |
ARP |
Whether to enable rate limit for ARP broadcast packets on an AP. |
ND |
Whether to enable rate limit for ND broadcast packets on an AP. |
IGMP |
Whether to enable rate limit for IGMP multicast packets on an AP. |
DHCP |
Whether to enable rate limit for DHCP broadcast packets on an AP. |
DHCPv6 |
Whether to enable rate limit for DHCPv6 broadcast packets on an AP. |
mDNS |
Whether to enable rate limit for mDNS multicast packets on an AP. |
Other-broadcast |
Whether to enable rate limit for broadcast packets other than ARP, ND, DHCP and DHCPv6 packets on an AP. |
Other-multicast |
Whether to enable rate limit for multicast packets other than IGMP and mDNS packets on an AP. |
Configuring an IoT Module
Context
The Internet of Things (IoT) is the interconnection of various information sensing equipment, such as the radio frequency identification (RFID), infrared sensor, Global Positioning System (GPS), and laser scanner, within the Internet infrastructure. The IoT aims to interconnect all objects for easier identification and management.
Installed with IoT modules, Huawei IoT APs not only provide wireless coverage but also support IoT applications, and administrators only need to manage one network as the WLAN and IoT are integrated.
Currently, only the AP2051DN-E, AP4050DN-E, AP7152DN, AP7052DN, AD9430DN-12, AD9430DN-24, R250D-E, and R251D-E support the IoT function.
Tenant administrators can set IoT parameters for the preceding IoT APs running V200R009C00 or a later version on iMaster NCE-Campus. Figure 6-51 shows a basic IoT networking diagram.
According to physical interface, IoT APs and IoT cards can be connected in either of the following modes:
- Serial interface
An IoT card is an external device connecting to an AP, and communicates with an IoT server (which needs to be deployed separately) through the AP. The IoT server can obtain data from the IoT card and also can deliver configuration data to the IoT card.
- Ethernet interface
An IoT card can be regarded as a special PC connecting to an AP through an Ethernet interface. In this mode, the IoT card complies with the IP protocol used by common PCs for communication.
Procedure
- Select a site.
- Choose from the main menu.
- In the displayed window, select a site from the Site drop-down list in the upper left corner.
- Choose the Site Configuration tab.
- Choose IoT Cards page. from the navigation pane, and select a configuration type on the
- To configure same parameters for all IoT APs of the same model at the selected site, select Global configuration and select a device model from the Device type drop-down list.
- To configure parameters for a specified IoT AP, select Personalized Config and select the target AP.
- In the Select Interface area, select the desired communication interface between APs and IoT cards, set parameters, and click OK.
Parameter Description
Parameter |
Description |
|
---|---|---|
Port type |
- |
Type of the interface on an IoT card connecting to an IoT AP. For cards, the Serial Port and Ethernet Port options are supported; for USBs, only the Serial Port option is supported. |
Serial Port |
Communication protocol |
Protocol and port for communication between an IoT card and the IoT server. |
Communication port |
||
Trusted host address |
When an AP functions as a server to receive data, the AP communicates only with trusted clients. If this parameter is left empty, connection establishment and configuration delivery are allowed between the AP and any reachable client on the network. The value is the combination of a unicast IP address and a mask, for example, 192.168.0.1/24. |
|
Shared key |
(Only involved in TCP) Key used for encrypting packets between an AP and the IoT server, which improves the data communication security. To ensure the security, you are advised to use a key containing at least two types of lower-case letters, upper-case letters, digits, and special characters. |
|
IoT server |
Address and port of the IoT server. If multiple IoT servers are configured, at least one of the address and port must be different between two servers. |
|
Port |
||
Ethernet Port |
Administrative status |
Whether to enable the IoT card function. |
Default VLAN |
Default VLAN on the network interface of an AP for communication between the AP and an IoT card. The IoT card automatically obtains an IP address from the DHCP address pool of the default VLAN for external communication. |
Configuring a Bluetooth Module
Context
iMaster NCE-Campus allows administrators to set Bluetooth parameters and deliver the settings to desired APs. The available functions include Bluetooth terminal location, Bluetooth tag location, and Bluetooth data transparent transmission.
- Bluetooth terminal location
The administrator of a large shopping mall wants to use the Bluetooth location technology to provide shopping navigation and shopping guide for customers.
Figure 6-52 Networking for Bluetooth-based STA location- iMaster NCE-Campus delivers related configurations to APs.
- The built-in Bluetooth module of each AP scans surrounding BLE devices and Bluetooth STAs (such as mobile phones and tablets) and collect BLE broadcast frames sent by the BLE devices and Bluetooth STAs.
- The APs report the obtained information about the BLE devices and packets sent by Bluetooth STAs to the location server.
- The APP server obtains map information and BLE device locations from the location server.
The APP server pushes map information and BLE device locations to the Bluetooth STAs.
- Bluetooth tag-based location
With the Bluetooth tag location function, administrators can easily locate assets and personnel in places such as schools, warehouses, hospitals, and enterprises.
Figure 6-53 Networking for Bluetooth tag location- iMaster NCE-Campus delivers related configurations to APs.
The built-in Bluetooth module of each AP scans surrounding Bluetooth tags and collects BLE broadcast frames sent by the Bluetooth tags.
The APs report the obtained information about Bluetooth tags to the location server.
- Bluetooth data transparent transmission
In places such as hospitals and schools, with Bluetooth data transparent transmission function, administrators can collect and analyze heath data of people who wear Bluetooth clients (such as Bluetooth thermometers, Bluetooth blood pressure meters, and Bluetooth heart rate meters).
Figure 6-54 Networking for Bluetooth data transparent transmission- iMaster NCE-Campus delivers related configurations to APs.
- The Bluetooth clients obtain users' health data. The built-in Bluetooth module of each AP scans Bluetooth clients in surrounding environments and collects BLE broadcast frames sent by the Bluetooth clients.
The APs report the obtained users' health data to the location server.
Tenant administrators can set Bluetooth parameters on iMaster NCE-Campus to facilitate network management and control over key assets.
- Only the AP2050DN-E, AP2051DN-E, AP4050DN-E, AP4051TN, AP6052DN, AP7050DE, AP7052DE, AP7052DN, AP4050DE-M, and AP4050DE-M-S, AP4050DE-B-S, AP7060DN, AP7152DN, AP8050DN, AP8050DN-S, AP8050TN-HD, AP8082DN, AP8150DN, AP8182DN, R250D-E, and the R251D-E supports the preceding Bluetooth functions.
- Among the preceding models, administrators can configure Bluetooth parameters only for the APs running V200R009C00 or later versions on iMaster NCE-Campus.
Procedure
- Select a site.
- Choose from the main menu.
- In the displayed window, select a site from the Site drop-down list in the upper left corner.
- Choose the Site Configuration tab.
- Choose Bluetooth page, set parameters based on the desired scenario. from the navigation pane. On the
- Bluetooth-based STA location:
- (Optional) If no independent BLE device is deployed on the network, you need to enable the broadcast function of the built-in Bluetooth module of APs.
- Enable Monitoring and set Monitoring mode to iBeacon.
- (Optional) Enable and configure the data reporting function if data needs to be reported.
- Bluetooth tag-based location
- Enable Monitoring and set Monitoring mode to Tag.
- Enable and configure the data reporting function.
- Bluetooth data transparent transmission
- Enable Monitoring and set Monitoring mode to Transparent.
- Enable and configure the data reporting function.
- Bluetooth-based STA location:
- Click Apply.
Follow-up Procedure
- Bluetooth terminal locationAfter configuring Bluetooth terminal location, you need to perform the following operations to view terminal locations on the location server:
Set Bluetooth terminal location parameters on the location server.
Configure the location server to communicate with the APP server.
Install a Bluetooth location app (provided by the location server vendor) on Bluetooth terminals (such as mobile phones), enable the Bluetooth function on the terminals, and enable the Wi-Fi or cellular network to ensure that the Bluetooth terminals can access the Internet and send scanned BLE device information to the location server.
- Bluetooth tag-based location
After configuring Bluetooth tag location, you need to configure related parameters on the location server so that you can view Bluetooth tag locations on the location server.
- Bluetooth data transparent transmission
After configuring Bluetooth data transparent transmission, you need to configure servers to collect data from Bluetooth clients for analysis.
Parameter Description
Parameter |
Description |
|
---|---|---|
Broadcast |
Broadcast |
Whether to enable the broadcast function of a Bluetooth module. If no independent BLE device is deployed on the network, you need to enable the broadcast function of the built-in Bluetooth module of an AP. |
Transmit power (dBm) |
Transmit power of the built-in Bluetooth module of an AP. Set the parameter according to the planning, and then fine-tune the parameter on site. The options are -21, -18, -15, -12, -9, -6, -3, 0, 1, 2, 3, 4, and 5, in dBm. The default value is 0. |
|
RSSI calibration value (dBm) |
RSSI value of a Bluetooth Low Energy (BLE) device measured at a distance of 1 m. It is used to estimate the distance between the BLE device and Bluetooth-capable STAs. Set the parameter according to the planning, and then fine-tune the parameter on site. The value is an integer that ranges from -97 to -50, in dBm. The default value is -65. |
|
Broadcast interval (ms) |
Interval for an AP's built-in Bluetooth module to send BLE advertising packets. Set the parameter according to the planning, and then fine-tune the parameter on site. The value is an integer that ranges from 100 to 10240, in milliseconds. The default value is 400. |
|
UUID in broadcast packets |
Value of the UUID parameter (hexadecimal type) in a BLE broadcast frame, which is the unique identifier of a BLE device. Set this parameter based on UUIDs provided by third-party vendors. The vendors can identity their devices using the UUID. For example, a Bluetooth tracker vendor provides a UUID value, and an AP identifies Bluetooth STAs based on the UUID. |
|
Major value in broadcast packets |
Value of the Major parameter in a BLE broadcast frame, in hexadecimal notation. This field specifies a major group and is combined with the Minor field to define information about a BLE device, for example, location of a BLE device. Set this parameter based on values provided by third-party vendors. For example, a Bluetooth tracker vendor that provides a large business volume will provide different UUIDs in different areas. If a separate UUID is set for Jiangsu in China, you need to set this parameter to China. |
|
Minor value in broadcast packets |
Value of the Minor parameter in a BLE broadcast frame, in hexadecimal notation. This field specifies a minor group and is combined with the Major field to define information about a BLE device, for example, location of a BLE device. Set this parameter based on values provided by third-party vendors. For example, a Bluetooth tracker vendor that provides a large business volume will provide different UUIDs in different areas. If a separate UUID is set for Jiangsu in China, you need to set this parameter to Jiangsu. |
|
Monitoring |
Monitoring |
Whether to enable the Bluetooth monitoring function of an AP's built-in Bluetooth module. |
Monitoring mode |
|
|
Data report |
Whether to enable APs to report Bluetooth location packets.
|
|
Data report mode |
Mode for an AP to report Bluetooth location packets. If Bluetooth location packets are reported by APs upon receipt, the location accuracy is higher, but the AP performance is affected. |
|
Data report interval (s) |
Interval for an AP to report Bluetooth location packets when Data report mode is set to Periodic. The unit is second, and the default value is 10. |
|
Server address |
Destination and port number for an AP to send Bluetooth location packets. |
|
Server port |
Configuring IPSec VPN
Context
To improve data transmission security, an IPSec tunnel can be established between an AP and its peer device to transmit data flows to be protected. A security protocol is used to encrypt and verify network packets in the IPSec tunnel to ensure secure transmission of key service data over the Internet, reducing the risks of information leakage.
Procedure
This section describes how to configure IPSec for APs on iMaster NCE-Campus. Matching IPSec parameters must have been configured on the peer device. For detailed IPsec configuration method is determined by the peer device.
- Select a site.
- Choose from the main menu.
- In the displayed window, select a site from the Site drop-down list in the upper left corner.
- Choose the Site Configuration tab.
- Choose IPSEC VPN page. from the navigation pane, and enter the
- Click Create and configure IPSec policies for all the APs in the current site, and click OK.
Parameter Description
Parameter |
Description |
||
---|---|---|---|
Policy name |
Name that uniquely identifies an IPsec policy. You are advised to set this parameter to the IP address or domain name of the peer device. |
||
Peer IP or domains |
IP address of the peer device. Only one IPsec policy can be created for an IP address. Otherwise, the IPsec tunnel fails to be established. |
||
Local ID |
Type and value of the local ID, used for identity authentication during IKE negotiation.
NOTE:
The type and value of the local ID on an AP must be the same as those on the peer device. |
||
Encryption ACL |
Click Add to create a local ACL rule, and click Submit to save the ACL rule.
NOTE:
|
||
Filtering ACL |
|||
IPSec template |
- |
Click +, set IKE Parameters and IPSec Parameters, and click Save to save the current template. |
|
IKE Parameters |
IKE version |
IKE protocol version number used by an IKE peer. The value on the local device must be the same as that on the peer device. IKEv2 with higher security, better extensibility, and higher negotiation efficiency is recommended. If IKEv1 is used, Negotiation mode must be set to the same value on the local and peer devices. |
|
Encryption algorithm |
Algorithm used to encrypt and decrypt IP packets. A longer key indicates higher security but slower encryption speed. The algorithms are listed as follows from the highest security level to the lowest security level: AES-256, AES-192, AES-128, 3DES, and DES. You are not advised to use the insecure algorithms DES and 3DES. |
||
Negotiation mode |
Negotiation mode in the IKEv1 phase (for IKEv1 only).
|
||
Authentication algorithm |
Authentication algorithm used in IKEv1 negotiation (for IKEv1 only). The algorithms are listed as follows from the highest security level to the lowest security level: SHA2-512, SHA2-384, SHA2-256, SHA1, and MD5. You are not advised to use the insecure algorithms MD5 and SHA1. NOTE:
Among APs running WLAN V200R019C00, the authentication algorithm is configurable only on the AP2051DN, AP4050DE-M, AP4050DN-E, and AP6050DN. |
||
Integrity algorithm |
Integrity algorithm used in IKEv2 negotiation (for IKEv2 only). The algorithms are listed as follows from the highest security level to the lowest security level: SHA2-512, SHA2-384, SHA2-256, AES-XCBC-96, SHA1, and MD5. You are not advised to use the insecure algorithms MD5 and SHA1. |
||
PRF |
Pseudo-random function (PRF) algorithm used in IKEv2 negotiation (for IKEv2 only). The algorithms are listed as follows from the highest security level to the lowest security level: SHA2-512, SHA2-384, SHA2-256, AES-XCBC-96, SHA1, and MD5. You are not advised to use the insecure algorithms MD5 and SHA1. |
||
DH group |
Diffie-Hellman (DH) group used in IKE phase-1 key negotiation. The DH group is used to calculate the shared key, preventing packets from being cracked. The DH groups are listed as follows from the highest security level to the lowest security level: group16, group15, group14, group5, group2, and group1. You are not advised to use the insecure group1, group2, and group5. NOTE:
The DH group on two ends of an IPsec tunnel must be the same; otherwise, IKE negotiation fails. |
||
SA timeout interval (s) |
IKE SA lifetime, for periodic IKE SA update to reduce risks of SA cracking and improve security. If an IKE SA times out, a new IKE SA needs to be negotiated. It is recommended that you set this parameter to a value greater than 600s. |
||
IPSec Parameters |
Encapsulation mode |
Encapsulation mode in which fields related to AH or ESP are inserted into the original IP packets based on certain rules to authenticate and encrypt packets. Compared with the transport mode, the tunnel mode has higher security but occupies more bandwidth. NOTE:
If a NAT device exists on an IPsec tunnel, NAT traversal must be enabled and Encapsulation mode and Security protocol must be set to Tunnel mode and ESP, respectively. |
|
Security protocol |
Protocol used to encapsulate and transmit data packets. AH and ESP have their own advantages and disadvantages. AH-ESP is recommended in scenarios with high security requirements.
|
||
PFS |
Perfect forward secrecy (PFS) used when the local end initiates negotiation. An addition DH exchange is performed during negotiation of a child SA in IKEv1 phase 2 or IKEv2 to ensure security of the IPsec SAs and improve communication security. You are not advised to use the insecure group1, group2, and group5. NOTE:
If PFS is enabled for tunnel negotiation, the DH group specified for the local end and peer end must be the same; otherwise, IKE negotiation fails. |
||
IPSec SA Aging |
SA lifetime, for periodic SA update to reduce risks of SA cracking and improve security. The current SA becomes invalid if either of the following times out. IKE will negotiate a new SA for to the peer to protect IPsec communication.
NOTE:
This parameter is only valid for the SAs established through IKE. When IKEv1 is used for IPsec negotiation, flow-based SA timeout must be disabled on both ends if the value is set to 0 on either end. When IKEv2 is used for IPsec negotiation, flow-based SA timeout must be disabled on the local end if the value is set to 0 on this end. |
||
DPD |
- |
Whether dead peer detection (DPD) is enabled. After this function is enabled, an IKE peer detects whether the peer is alive through DPD messages. |
|
Detection mode |
|
||
Load sequence |
|
||
Detection interval (s) |
Interval for sending DPD packets. When there are a large number of IPsec tunnels, you need to set this parameter to a larger value to prevent performance deterioration caused by frequent exchange of DPD packets. |
||
Retransmission interval (s) |
Interval at which DPD packets are retransmitted. |
||
Key |
The authentication key on two ends of an IPsec tunnel must be the same. For example, if the key on one end is a character string but the key on the other end is a hexadecimal number, the SA cannot be set up. |
Configuring Physical Interfaces
Context
- Cloud AP
A cloud AP integrates wired and wireless access capabilities depending on the model and supports access control of mobile end users. It can control 2.4 GHz or 5 GHz wireless network coverage.
To configure MAC address limiting on a WAN interface or access parameters on a wired LAN Interface, you need to specify WAN and LAN interfaces on a cloud AP. The interfaces must be the same as those used for connection during device installation.
Figure 6-55 shows a basic networking of a cloud AP.
- Central AP + Distributed APs
In an agile distributed Wi-Fi networking, a central AP is connected to multiple distributed APs (RUs). This solution best suits scenarios with densely-located rooms, such as hotels.
The administrator can configure network access parameters on WAN and LAN interfaces of the central AP and WAN interfaces of distributed APs. The interfaces must be the same as those used for connections during device installation.
Figure 6-56 shows basic networking of the central AP and distributed APs in the agile distributed Wi-Fi solution.
Figure 6-56 Basic networking of the central AP and distributed APs in the agile distributed Wi-Fi solution- The central AP is responsible for service forwarding and access control. It provides wired access capabilities, and provides wireless access capabilities through downstream distributed APs.
- A distributed AP is also a remote unit (RU). It can process radio signals independently to implement wireless access of STAs. A distributed AP is directly connected to the central AP through a network cable to prevent attenuation of RF signals on feeders. The planning and deployment of distributed APs are flexible, effectively reducing construction costs and improving wireless network access experience.
Procedure (Cloud AP)
- Select a site.
- Choose from the main menu.
- In the displayed window, select a site from the Site drop-down list in the upper left corner.
- Choose the Site Configuration tab.
- Choose from the navigation pane, and set Configuration type on the page.
- To configure the same parameters for all devices at the selected site, select Global configuration.
- To configure parameters for a specified device at the selected site, select Personalized configuration and select the target AP.
- Click + and select a panel by device model. This step is required when Configuration type is set to Global configuration.
Port settings for a panel take effect on all APs with the same panel at the site.
- Specify interface 0 or 1 in the panel as a WAN interface, set parameters, and click Apply.
- Specify another interface in the panel as a LAN interface, set parameters, and click Apply. The LAN interface must be different from the WAN interface.
Only some models of cloud APs provide LAN interfaces. The parameters set on a nonexistent network interface do not take effect.
- If the LAN interface is directly connected to a network device, such as a switch, set Scenario to Directly connect to switch.
- If the LAN interface is directly connected to a wired STA, such as a PC, set Scenario to Directly connect to PC.
Procedure (Central AP + Distributed AP)
- Select a site.
- Choose from the main menu.
- In the displayed window, select a site from the Site drop-down list in the upper left corner.
- Choose the Site Configuration tab.
- Choose from the navigation pane, and set Device type and Configuration type on the page.
- To configure the same parameters for all devices at the selected site, select Global configuration.
- To configure parameters for a specified device at the selected site, select Personalized configuration and select the target central AP.
- Specify an interface as the WAN interface of the central AP, set parameters, and click Apply.
- On the AD9430DN-24, network interfaces 24 to 27 can be specified as WAN interfaces.
- On the AD9430DN-12, network interfaces 12 and 13 can be specified as WAN interfaces.
- Specify an interface as the LAN interface of the central AP, set parameters, and click Apply.
- If the LAN interface is directly connected to a distributed AP, set Scenario to Directly connect to distributed AP.
- If the LAN interface is directly connected to a wired STA, such as a PC, set Scenario to Directly connect to PC.
- If the LAN interface is directly connected to a network device such as a switch, set Scenario to Directly connect to switch.
- If the LAN interface is directly connected to another central AP, set Scenario to Directly connect to central AP.
- Select Device type and Configuration type in the Distributed AP Interface page.
- To configure the same parameters for all devices at the selected site, select Global configuration.
- To configure personalized parameters for a specified device at the selected site, select Personalized configuration and select the target distributed AP.
- Specify an interface as the WAN interface of the distributed AP, set Scenario to WAN, and click Apply.
If this parameter does not exist, the network interface cannot be used as a WAN interface.
- Specify an interface as the LAN interface of the distributed AP, set parameters, and click Apply.
Only some models of distributed APs provide LAN interfaces. The parameters set on a nonexistent network interface do not take effect.
- If the LAN interface is directly connected to a network device, such as a switch, set Scenario to Directly connect to switch.
- If the LAN interface is directly connected to a wired STA, such as a PC, set Scenario to Directly connect to PC.
Parameter Description
Parameter |
Description |
---|---|
Administrative status |
Whether to enable the network interface. If the value of this parameter is set to OFF, the network interface will be unavailable. Exercise caution when performing this operation. |
LLDP |
An LLDP-enabled device sends LLDP packets containing its own status information to neighbors that have LLDP enabled, and collects the status information about these neighbors. Enable this function when you need to know the Layer 2 connection status between devices and analyze the network topology through the NMS. The default value is ON. Frequently enabling or disabling LLDP globally may cause service data delivery failures. The interval between two consecutive LLDP operations must be longer than 10s. The configuration takes effect only when LLDP is also enabled in the Other area on the page. |
Default VLAN |
VLAN that the network interface joins by default. |
Allowed VLAN |
VLAN allowed by the network interface. When you click Add to add VLAN IDs, you can specify different VLANs packets that can pass through the AP based on labels. If VLAN ID is empty, the APs specified by the corresponding AP label allow packets from all VLANs to pass. You need to configure the AP label as follows:
|
MAC limit |
MAC address limiting on an AP limits the number of STAs connected to the AP. MAC address limiting can prevent network attacks. After the maximum number of MAC addresses is reached, the AP will reject access requests of subsequent STAs. In this case, services may be affected. |
Parameter |
Description |
---|---|
Administrative status |
Whether to enable the network interface. If the value of this parameter is set to OFF, the network interface will be unavailable. Exercise caution when performing this operation. |
LLDP |
An LLDP-enabled device sends LLDP packets containing its own status information to neighbors that have LLDP enabled, and collects the status information about these neighbors. Enable this function when you need to know the Layer 2 connection status between devices and analyze the network topology through the NMS. The default value is ON. Frequently enabling or disabling LLDP globally may cause service data delivery failures. The interval between two consecutive LLDP operations must be longer than 10s. The configuration takes effect only when LLDP is also enabled in the Other area on the page. |
Binding check |
Whether to enable Dynamic ARP Inspection (DAI), IP Source Guard (IPSG), and DHCP snooping on the network interface. By default, these functions are not enabled.
|
Network connection mode |
|
VLAN ID |
This parameter is available only when the AP serves as a Layer 2 forwarding device. The value must be the same as the VLAN ID of a switch interface connected to the uplink network interface. |
Terminal's rate limit (Mbps) |
Rate limit for uplink STAs. |
ACL |
The ACL permits STAs to access or prevents STAs from accessing specified resources based on the destination IP address, protocol type, and interface number. |
Parameter |
Description |
---|---|
Administrative status |
Whether to enable the network interface. If the value of this parameter is set to OFF, the network interface will be unavailable. Exercise caution when performing this operation. |
LLDP |
An LLDP-enabled device sends LLDP packets containing its own status information to neighbors that have LLDP enabled, and collects the status information about these neighbors. Enable this function when you need to know the Layer 2 connection status between devices and analyze the network topology through the NMS. The default value is ON. Frequently enabling or disabling LLDP globally may cause service data delivery failures. The interval between two consecutive LLDP operations must be longer than 10s. The configuration takes effect only when LLDP is also enabled in the Other area on the page. |
POE |
Whether to enable PoE power supply on the downlink network interface to perform power-on or power-off operations over the distributed AP that is directly connected to the network interface. |
Parameter |
Description |
---|---|
Administrative status |
Whether to enable the network interface. If the value of this parameter is set to OFF, the network interface will be unavailable. Exercise caution when performing this operation. |
LLDP |
An LLDP-enabled device sends LLDP packets containing its own status information to neighbors that have LLDP enabled, and collects the status information about these neighbors. Enable this function when you need to know the Layer 2 connection status between devices and analyze the network topology through the NMS. The default value is ON. Frequently enabling or disabling LLDP globally may cause service data delivery failures. The interval between two consecutive LLDP operations must be longer than 10s. The configuration takes effect only when LLDP is also enabled in the Other area on the page. |
Binding check |
Whether to enable Dynamic ARP Inspection (DAI), IP Source Guard (IPSG), and DHCP snooping on the network interface. By default, these functions are not enabled.
|
Network connection mode |
|
VLAN ID |
This parameter is available only when the AP serves as a Layer 2 forwarding device. The value must be the same as the VLAN ID of a switch interface connected to the uplink network interface. |
Terminal's rate limit (Mbit/s) |
Rate limit for uplink STAs. |
ACL |
The ACL permits STAs to access or prevents STAs from accessing specified resources based on the destination IP address, protocol type, and interface number. |
Parameter |
Description |
---|---|
Administrative status |
Whether to enable the network interface. If the value of this parameter is set to OFF, the network interface will be unavailable. Exercise caution when performing this operation. |
LLDP |
An LLDP-enabled device sends LLDP packets containing its own status information to neighbors that have LLDP enabled, and collects the status information about these neighbors. Enable this function when you need to know the Layer 2 connection status between devices and analyze the network topology through the NMS. The default value is ON. Frequently enabling or disabling LLDP globally may cause service data delivery failures. The interval between two consecutive LLDP operations must be longer than 10s. The configuration takes effect only when LLDP is also enabled in the Other area on the page. |
VLAN ID |
VLAN that the network interface joins by default. |
Allowed VLAN |
VLAN allowed by the network interface. |
MAC limit |
MAC address limiting on an AP limits the number of STAs connected to the AP. MAC address limiting can prevent network attacks. After the maximum number of MAC addresses is reached, the AP will reject access requests of subsequent STAs. In this case, services may be affected. |
Parameter |
Description |
---|---|
Administrative status |
Whether to enable the network interface. If the value of this parameter is set to OFF, the network interface will be unavailable. Exercise caution when performing this operation. |
LLDP |
An LLDP-enabled device sends LLDP packets containing its own status information to neighbors that have LLDP enabled, and collects the status information about these neighbors. Enable this function when you need to know the Layer 2 connection status between devices and analyze the network topology through the NMS. The default value is ON. Frequently enabling or disabling LLDP globally may cause service data delivery failures. The interval between two consecutive LLDP operations must be longer than 10s. The configuration takes effect only when LLDP is also enabled in the Other area on the page. |
VLAN ID |
VLAN that the network interface joins by default. |
Allowed VLAN |
VLAN allowed by the network interface. |
Parameter |
Description |
---|---|
Administrative status |
Whether to enable the network interface. If the value of this parameter is set to OFF, the network interface will be unavailable. Exercise caution when performing this operation. |
LLDP |
An LLDP-enabled device sends LLDP packets containing its own status information to neighbors that have LLDP enabled, and collects the status information about these neighbors. Enable this function when you need to know the Layer 2 connection status between devices and analyze the network topology through the NMS. The default value is ON. Frequently enabling or disabling LLDP globally may cause service data delivery failures. The interval between two consecutive LLDP operations must be longer than 10s. The configuration takes effect only when LLDP is also enabled in the Other area on the page. |
Default VLAN |
VLAN that the network interface joins by default. |
Allowed VLAN |
VLAN allowed by the network interface. When you click Add to add VLAN IDs, you can specify different VLANs packets from which are allowed to pass based on the AP labels. If VLAN ID is empty, the APs specified by the corresponding AP label allow packets from all VLANs to pass. You need to configure the AP label as follows:
|
Parameter |
Description |
---|---|
Administrative status |
Whether to enable the network interface. If the value of this parameter is set to OFF, the network interface will be unavailable. Exercise caution when performing this operation. |
LLDP |
An LLDP-enabled device sends LLDP packets containing its own status information to neighbors that have LLDP enabled, and collects the status information about these neighbors. Enable this function when you need to know the Layer 2 connection status between devices and analyze the network topology through the NMS. The default value is ON. Frequently enabling or disabling LLDP globally may cause service data delivery failures. The interval between two consecutive LLDP operations must be longer than 10s. The configuration takes effect only when LLDP is also enabled in the Other area on the page. |
Binding check |
Whether to enable Dynamic ARP Inspection (DAI), IP Source Guard (IPSG), and DHCP snooping on the network interface. By default, these functions are not enabled.
|
Network connection mode |
|
VLAN ID |
This parameter is available only when the AP serves as a Layer 2 forwarding device. The value must be the same as the VLAN ID of a switch interface connected to the uplink network interface. |
Configuring DHCP
Context
If a STA connects to an AP in NAT mode, the AP is used as the default gateway and the STA dynamically obtains an IP address from the AP. Figure 1 shows basic DHCP networking.
By default, the STAs connected to an AP in NAT mode obtain IP addresses in the range from 10.1.1.2 to 10.1.1.254 and belong to VLAN 3911. You can either use default settings or set the IP addresses and VLAN ID as needed.
Procedure
- Select a site.
- Choose from the main menu.
- In the displayed window, select a site from the Site drop-down list in the upper left corner.
- Choose the Site Configuration tab.
- Choose enable DHCP enable by def, then set DHCP server parameters on the DHCP page. from the navigation pane, and
- (Optional) In the LAN VLAN area, specify the VLAN ID for the STAs connected to an AP in NAT mode.
You are advised to use the default VLAN 3911. The VLAN ID must be different from the configured service VLAN IDs. Changing this VLAN ID may cause NAT and IPsec users to go offline.
Parameter Description
Parameter |
Description |
---|---|
DHCP enable |
Enable DHCP and set DHCP parameters. This parameter is enabled by default. |
IP |
Default gateway and subnet mask of the DHCP client. The gateway IP address and subnet mask determine the IP address range (DHCP address pool) that DHCP clients may obtain. |
Mask |
|
Log records |
This switch is turned off by default. When this switch is turned on, it takes effect when the system connects to the CampusInsight. This function is used to record DHCP Server configuration success or failure logs and report the logs to the CampusInsight for data analysis and display. |
Third-party URL Filtering |
URL filtering by third-party software. After this function is enabled, third-party software can be used to implement URL filtering. |
Lease |
Lease of an IP address that a DHCP client automatically obtains. After the IP address lease expires, an IP address is assigned again. |
Master WINS |
Primary and secondary WINS server addresses assigned to a DHCP client. |
Slave WINS |
|
Static address binding |
Binding between IP addresses and MAC addresses. A fixed IP address is assigned to a DHCP client with a specified MAC address. |
VLAN ID |
Configuring a VLAN ID. A LAN-side VLAN cannot be a service VLAN in use, and NAT and IPsec users will go offline if this VLAN is modified. The LAN VLAN cannot be the same as the management VLAN. Otherwise, the configuration delivery may fail. |
Configuring NAT Logs
Context
NAT logs are generated when devices perform address translation. The logs record the original source IP addresses, source ports, destination IP addresses, destination ports, and translated source IP addresses and source ports, as well as user actions and time stamps. You can view NAT logs to learn about information about users who have accessed a network using NAT.
Procedure
- Select a site.
- Choose from the main menu.
- In the displayed window, select a site from the Site drop-down list in the upper left corner.
- Choose the Site Configuration tab.
- Choose NAT Logs page. from the navigation pane, and set parameters on the
- Click Save.
Parameter Description
Parameter |
Description |
---|---|
NAT Logs |
Whether devices report NAT logs to the Syslog server. |
Text log output interval |
Interval for sending text logs to the Syslog server, in seconds. |
Binary log output |
Whether to send binary logs to the Syslog server. After the function is enabled, binary logs are sent to the Syslog server. |
Log server address and port |
IP address and port of the Syslog server. |
Source address for sending logs and source port |
IP address of the AP and the port for sending logs. The IP address can be automatically obtained. Therefore, only the port needs to be manually configured. |
Configuring Terminal Connectivity Check
Context
This function enables access devices to simulate a STA to send ping packets to the gateway to detect whether the gateway can be pinged and response delay of the gateway. In addition, the access devices can generate detection logs for CampusInsight to perform protocol playback and fault display.
Procedure
- Select a site.
- Choose from the main menu.
- In the displayed window, select a site from the Site drop-down list in the upper left corner.
- Choose the Site Configuration tab.
- Choose Terminal Connectivity Check. from the navigation pane, and enable
This function is disabled by default.
- Click Apply.
Configuring the Mesh Function
Context
The mesh function enables APs to set up Mesh networks for data backhaul or enhanced Wi-Fi. It can be used in indoor areas to expand Wi-Fi coverage or in outdoor areas to expand long-distance Wi-Fi coverage.
Extended indoor Wi-Fi coverage |
Outdoor long-distance Wi-Fi coverage |
---|---|
If devices running V200R019C00SPC700 are deployed on a Mesh network, you need to run commands on the devices to delete a Mesh network or remove members from Mesh groups.
system-view interface Wlan-Radio0/0/1 undo mesh-profile MESH_SPC700 wlan mesh-profile name MESH_SPC700 undo security-profile undo mesh-id quit undo mesh-profile name MESH_SPC700 undo security-profile name MESH_SPC700
The following APs support the Mesh function:
- Mesh-supporting device models: AP8050DN, AP8150DN, AP7060DN, AP2051DN, AP4050DN and models of the AirEngine series. Only the models of the AirEngine series support whitelist configuration and can be deployed on a mesh network with multiple MPPs.
- Mesh-supporting device versions: V200R019C00SPC700, V200R019C00SPC800, V200R019C00SPC803 and later versions (excluding V200R019C10).
- The following models of the AirEngine series support mesh configuration: AirEngine8760R-X1, AirEngine8760R-X1E, AirEngine6760R-51, AirEngine6760 51E, AirEngine6760-X1, and AirEngine6760-X1E, airEngine5760-51, AirEngine8760-X1-PRO, AirEngine5760-22W.
- The AirEngine series supports configuration only in NCE-Campus V3000R19C10SPC208 and later versions.
Procedure
- Select a site.
- Choose from the main menu.
- In the displayed window, select a site from the Site drop-down list in the upper left corner.
- Choose the Site Configuration tab.
- Choose Create to create a mesh network. from the navigation pane, and click
- Radio parameters of APs that have been added to mesh networks cannot be modified.
- On a cloud mesh network, when configuring an SSID with the network connection mode of Layer 2 forwarding, ensure that the SSID is configured on all devices in the mesh network. Otherwise, services may be abnormal.
- Click OK. After the mesh network is created, you can view the mesh network information in the mesh network list.
Parameter Description
Parameter |
Description |
|
---|---|---|
Name |
Name of a Mesh network. |
|
Effective Radio |
Radio parameters for Mesh links.
NOTE:
Currently, 5 GHz radio (wlan-radio 0/0/2) is not supported on APs. |
|
Use whitelist |
A Mesh whitelist contains MAC addresses of neighboring APs allowed to set up Mesh links with an AP. After this function is enabled, only neighboring APs with MAC addresses in the whitelist can connect to the AP. A maximum of 512 MAC addresses can be configured in the whitelist, and the whitelisted MAC addresses must be unique. This function is disabled by default. If no Mesh whitelist is configured, APs may establish Mesh links with neighboring APs randomly, wasting limited Mesh link resources. In addition, because there may be rogue neighboring APs, potential security risks exist if no Mesh whitelist is configured. NOTE:
|
|
Scene |
Two application scenarios Single MPP and Multiple MPPs can be configured based on the number of MPPs on the Mesh network.
NOTE:
When Scene is set to Single MPP, APs on the same Mesh network must be configured with the same radio channel and bandwidth. For details about how to configure radio parameters, see 4. |
|
Members |
Device Report Role |
AP's role reported to iMaster NCE-Campus after the AP goes online. |
Name |
Name and ESN of the AP to be added to the Mesh network. |
|
ESN |
||
Configured Role |
Role of the AP to be added to the Mesh network. The options are MPP and MP. The default role is MP. A maximum of 512 APs can be added to a Mesh network, and the ratio of MPs to MPPs cannot be greater than 6:1.
NOTE:
This parameter is configurable only for AirEngine series devices. |
Related Operations
- Modifying a Mesh network
On the mesh network tab page, click
to modify the desired Mesh network.
- Deleting a Mesh network
On the mesh network tab page, click
to delete the desired Mesh network.
Configuring AR Services
Configuring a Network
If an AR runs V300R003C00 or an earlier version and is deployed in PPPoE mode, you have to configure NAT on the AR before performing the following operations.
Context
- NQA for WAN uplinks
Network Quality Analysis (NQA) is a technology to measure network performance in real time and collect statistics on network information, such as the delay, jitter, and packet loss rate. NQA monitors network quality of service (QoS) indicators in real time, and effectively diagnoses and locate network faults.
NQA association means that NQA notifies other modules of detection results and other modules process services based on the detection results.
The following uses NQA association with static routes as an example:
A static route with the next hop being 192.168.0.88 is configured. If 192.168.0.88 is reachable, the static route is valid. Otherwise, the static route is invalid. By establishing association between NQA and application modules, you can determine the validity of static routes in real time.
- WAN-side DNS and NAT
- DNS
The device connected to the network through the AR can identify some domain names through a DNS server and resolves the domain names into IP addresses.
DNS technology implements mapping between domain names and IP addresses, so that users can easily access the Internet without remembering specific IP addresses.
After a DNS client is connected to a network, it sends a DNS request to the DNS relay agent. The DNS relay agent directly forwards the request to the DNS server. Then the DNS server performs domain name resolution and forwards a response to the DNS client.
- NAT
Enabling NAT on an AR router allows downstream devices connected to the AR router to use the IP address of the WAN interface on the AR router for Internet access.
NAT translates the address in the IPv4 packet header into another address. AR routers support NAT based on the outbound interface address (also called Easy IP). Devices on a tenant network can directly use the IP address of the public interface on an AR router to access the Internet.
- DNS
- LAN-side subnet
After an AR router is configured with DHCP, downstream devices can automatically obtain IP addresses from the AR router to communicate with the uplink network of the AR router.
Figure 1 shows the typical DHCP networking.
- DHCP server
A DHCP server dynamically assigns network parameters, including IP addresses, to DHCP clients.
- (Optional) DHCP relay agent
If DHCP clients and the DHCP server are on different subnets, you can configure a DHCP relay agent to communicate with the DHCP server so that the DHCP clients can obtain valid IP addresses. Devices on multiple subnets can share one DHCP server through the DHCP relay agent, reducing costs and facilitating centralized management.
- DHCP client
A DHCP client is a terminal such as a PC, mobile phone, IP phone, or diskless workstation that broadcasts DHCP Request packets to obtain network parameters such as an IP address.
- DHCP server
Procedure (Configuring NQA for WAN Uplinks)
- Select a site.
- Choose from the main menu.
- In the displayed window, select a site from the Site drop-down list in the upper left corner.
- Choose the Site Configuration tab.
- Choose WAN tab page, set parameters related to WAN uplinks. from the navigation pane. On the Click the desired AR router to configure link quality association analysis policies.
- If Mode selection is set to Active/standby mode, you need to configure a link quality association analysis policy only for ports on the active link.
- If Mode selection is set to Load mode, you need to configure a link quality association analysis policy for ports on link 1 and link 2, respectively.
Click
next to Associate with NQA to select a link quality association analysis policy for ports on required links. If no appropriate policy is available, click Create to create a link quality association analysis policy.
- Click Apply.
Procedure (Configuring WAN-side DNS and NAT)
- Select a site.
- Choose from the main menu.
- In the displayed window, select a site from the Site drop-down list in the upper left corner.
- Choose the Site Configuration tab.
- Choose from the navigation pane.
- Set parameters on the WAN tab page and click Apply.
NAT policies can be created on multiple interfaces on a device.
Procedure (Configuring LAN-side Subnets)
- Select a site.
- Choose from the main menu.
- In the displayed window, select a site from the Site drop-down list in the upper left corner.
- Choose the Site Configuration tab.
- Choose from the navigation pane.
- On the LAN tab page, set the network configuration mode to Local Internet access or Multi-branch interconnection.
- To set the same DHCP parameters for ARs at the selected site, select Local Internet access.
- To set different DHCP parameters for ARs at the selected site, select Multi-branch interconnection.
Changing the network configuration mode will clear the configuration of interfaces. Exercise caution when performing this operation.
- Click Create, and set LAN-side subnet parameters.
For example, you can configure the DHCP mode (server or relay). If the server mode is selected, you can customize the value carried in DHCP option 148. You can also configure the IP address lease period, reserved IP address, and static mappings between IP addresses and MAC addresses in the Advanced area.
Parameter Description
Parameter |
Description |
---|---|
Test Case Name |
Name of the NQA test instance. |
Destination IP address |
Destination IP address of a link to be detected. |
Source interface |
Source interface of a link to be detected. |
Number of sent packets |
Number of packets sent for each detection. |
Packet sending interval |
Interval for sending probe packets. |
Timeout interval |
Maximum timeout interval of failed attempts. |
Packet sending frequency |
Frequency of sending probe packets. |
Parameter |
Description |
---|---|
Interface name |
Select the WAN interface that is used as the outbound interface to access the public network. |
ACL |
Select the created ACL and bind the address mapping rule to an interface. |
NAT pre-classification |
Enable or disable NAT pre-classification. NAT pre-classification enables the NAT-enabled device to carry the private network IP address used before NAT translation to the outbound interface. The NAT-enabled device can classify network packets based on private IP addresses, providing differentiated services. NOTE:
If Security Compliance needs to be used, you need to enable QoS Pre NAT. |
Application traffic statistics collection |
After this function is enabled, routers parse packets from users to obtain the network usage information about each user application and report the statistics to iMaster NCE-Campus. |
DNS proxy |
Enable or disable the DNS relay on the AR. The value ON indicates that the DNS relay is enabled. |
DNS server configurations |
Click Create to configure the DNS server for the AR and click OK to save the configuration. You can add a maximum of six DNS servers in descending order of priority. |
DNS Local Domain Configuration |
When a terminal user sends a domain name resolution request, the AR first queries the local domain name mapping table. If the domain name cannot be resolved, the AR forwards the request to the DNS server. |
Parameter |
Description |
---|---|
Mode of IPv4 pool |
This parameter value can be set to Manual or Auto.
|
IPv4 pool |
This parameter value can be set to an available IP address from the resource pool. Alternatively, you can click |
VLAN ID |
The value is the same as the VLAN ID of the AR that is directly connected to intranet devices. Intranet devices use the AR as the default gateway. |
Network name |
Name of the network. |
IP |
IP address of the VLANIF interface, which is used as the default gateway address of DHCP clients. |
Mask |
Subnet mask of an IP address that a DHCP client automatically obtains. The gateway IP address and subnet mask determine the IP address range (DHCP address pool) that DHCP clients may obtain. |
Outbound traffic policy |
Traffic policy applied to outgoing traffic. |
Inbound traffic policy |
Traffic policy applied to incoming traffic. |
DHCP |
DHCP working mode of the AR when the value is ON:
|
DNS Service |
DNS server address specified for DHCP clients:
|
Primary DNS / Secondary DNS |
IP address of the DNS server. This parameter needs to be set when DNS Service is set to Customized. |
Domain name suffix |
When configuring the DHCP server, you can configure the DNS domain name suffix allocated to the DHCP client, that is, implement the function of the dhcp server domain-name command. |
AP mode |
Mode of an AP in the subnet. The options are Cloud AP and Fit AP. NOTE:
When configuring Branch connection, you need to set parameters such as AP mode and Automatically negotiates the controller address only when you select Multi-branch interconnection. The AP mode of the current subnet can be specified only when the AP is managed by iMaster NCE-Campus for the first time. If the AP device is not configured with the initial configuration or has been executed, the AP mode cannot be changed. |
Automatically negotiates the controller address |
When the function is enabled, the DHCP server of the current subnet automatically generates Option 148. Devices (switches or cloud-based APs) in the subnet can obtain the iMaster NCE-Campus address through Option 148 to register with iMaster NCE-Campus. |
Controller address type |
Type of the iMaster NCE-Campus address. The value can be an IP address or a domain name. If the iMaster NCE-Campus address is set to a domain name, ensure that the DNS function is configured on the live network to resolve the iMaster NCE-Campus domain name. Otherwise, devices fail to register with iMaster NCE-Campus. |
DHCP option |
DHCP option that is delivered to a DHCP client with an IP address. When cloud platform address(148) is selected, the value of the text type should be set to agilemode=xxx;agilemanage-mode=xxx;agilemanage-domain=xxxx.xxx;agilemanage-port=xxx. For example, agilemode=agile-cloud;agilemanage-mode=domain;agilemanage-domain=device-naas.huawei.com;agilemanage-port=10020. When requesting IP addresses through DHCP, Intranet cloud devices can obtain the address and port of the iMaster NCE-Campus server through this option.
|
Lease period |
Lease of an IP address that a DHCP server dynamically allocates to a DHCP client. This parameter is available only when the value of DHCP mode is Server. After the lease is reached, the DHCP server reclaims the IP address. The reclaimed IP address can still be assigned to another DHCP client. |
Reserved IP address |
Reserved IP address range. The AR does not allocate IP addresses in the IP address range to intranet devices. This parameter is available only when the value of DHCP mode is Server. |
Static address binding |
Fixed IP address allocated to a specified terminal. This parameter is available only when the value of DHCP mode is Server. |
DHCP server IP address |
This parameter is available only when the value of DHCP mode is Relay. When the AR function |