Higher Education Network Solution V100R024C00 Deployment and Maintenance Guide
Higher Education Network Solution V100R024C00 Deployment and Maintenance Guide
Solution
V100R024C00
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: https://www.huawei.com
Email: [email protected]
Preface
Purpose
This document describes Huawei Smart Higher Education Network Solution in
terms of version mapping, networking, tool usage, data planning, and solution
deployment.
Intended Audience
This document is intended for Network planning engineers, network deployment
engineers, and network O&M engineers. Operators must have the following
experience and skills:
Security Statements
● Personal Data
Some personal data (such as MAC and IP addresses of terminals) may be
obtained or saved during business operations, fault locating, or log audit of
your purchased products, services, or features. Therefore, user privacy policies
must be defined in compliance with local laws and adequate measures taken
to fully protect personal data. Logs and fault diagnosis data can be
transferred out of your network only with your authorization. If the data
needs to be transferred out of the European Economic Area (EEA), personal
data must be anonymized and cannot be restored by any means.
When discarding, recycling, or reusing a device, back up or clear data on the
device as required to prevent data leakage. If you need support, contact after-
sales technical support personnel.
● Product Lifecycle
Huawei's regulations on product lifecycle are subject to the Product End of
Life Policy. For details about this policy, visit the following web page:
https://support.huawei.com/ecolumnsweb/en/warranty-policy
● Vulnerability
Declaration
● This manual is only a reference for you to configure your devices. The
contents in the manual, such as command line syntax, and command outputs,
are based on the device conditions in the lab. The manual provides
instructions for general scenarios, but do not cover all usage scenarios of all
product models. The contents in the manual may be different from your
actual device situations due to the differences in software versions, models,
and configuration files. The manual will not list every possible difference. You
should configure your devices according to actual situations.
● The purchased products, services and features are stipulated by the
commercial contract made between Huawei and the customer. All or partial
products, services and features described in this document may not be within
the purchased scope or the usage scope. Unless otherwise specified in the
contract, all statements, information, and recommendations in this document
are provided "AS IS" without warranties, guarantees or representations of any
kind, either express or implied.
● The specifications provided in this manual are tested in lab environment (for
example, the tested device has been configured with a certain type of cards or
only one protocol is run on the device). Results may differ from the listed
specifications when you attempt to obtain the maximum values with multiple
functions enabled on the device.
● Interface numbers used in this manual are examples. In device configuration,
use the existing interface numbers on devices.
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Symbol Description
GUI Conventions
Format Description
Change History
Issue Date Description
Contents
Preface.......................................................................................................................................... iii
1 Version Requirements.............................................................................................................1
2 Overview....................................................................................................................................8
2.1 Logical Architecture................................................................................................................................................................ 8
2.2 Physical Architecture.............................................................................................................................................................. 9
7 Deployment Configuration................................................................................................. 30
7.1 Creating a Site........................................................................................................................................................................30
7.2 Importing the Network Plan............................................................................................................................................. 31
7.3 Configuring Core Switches to Go Online...................................................................................................................... 34
7.3.1 Configuring a Stack or CSS for Switches................................................................................................................... 34
7.3.2 Configuring the Controller to Manage the Core Switch Running V200 Through NETCONF.................. 34
7.3.3 Configuring the Controller to Manage the Core Switch Running V600 Through NETCONF.................. 35
7.3.4 Configuring Stacked Core Switches to Be Managed by the Controller.......................................................... 37
7.4 Configuring Aggregation and Access Switches to Go Online................................................................................38
7.5 Configuring WACs and APs to Go Online.....................................................................................................................45
7.5.1 Configuring WAC HSB..................................................................................................................................................... 45
7.5.2 Configuring WACs to Be Managed by the Controller........................................................................................... 57
7.5.3 Configuring Fit APs to Join a WAC.............................................................................................................................. 58
7.6 (Optional) Configuring the Service Awareness Function........................................................................................60
7.6.1 (Optional) Configuring the Service Awareness Function for the Switches Running V200...................... 60
7.6.2 (Optional) Configuring the WAC Resource Mode................................................................................................. 62
7.7 Configuring BRAS.................................................................................................................................................................. 63
7.7.1 Configuring VRRP HSB.....................................................................................................................................................63
8 Service Deployment.............................................................................................................. 78
8.1 Service Deployment for MAC Address-Prioritized Portal Authentication Users..............................................78
8.1.1 Configuring a Wired Network....................................................................................................................................... 78
8.1.2 Configuring the Wireless Network.............................................................................................................................. 79
8.1.3 Configuring Authentication for BRAS Users............................................................................................................. 79
8.2 Service Deployment for 802.1X Proxy Authentication............................................................................................. 87
8.2.1 Configuring 802.1X Authentication on the WAC.................................................................................................... 87
8.2.2 Configuring BRAS Proxy Authentication....................................................................................................................88
8.3 Service Deployment for Wired Dumb Terminals........................................................................................................96
8.3.1 Configuring a Wired Network....................................................................................................................................... 96
8.3.2 Configuring MAC Address Authentication on Switches....................................................................................... 96
11 O&M..................................................................................................................................... 197
11.1 Instructions for Maintenance Engineers.................................................................................................................. 197
11.1.1 Troubleshooting Principles.........................................................................................................................................197
11.1.2 Troubleshooting Precautions.................................................................................................................................... 197
1 Version Requirements
Table 1-1 lists the products and software versions used in Huawei Smart Higher
Education Network Solution.
Table 1-1 Products and versions required by Huawei Smart Higher Education
Network Solution
Scenari Device Product Series Mappin Description Related
o Type g Docume
Version nt
2 Overview
for network devices. The security big data platform implements network-wide
security situational awareness.
● Core layer
The core layer is responsible for high-speed connections on a campus
network, but does not have specific services deployed. This layer refers to the
zone where servers and application systems are deployed in the data center,
and provides data and application services for internal and external users on
the campus network.
● Aggregation layer
Traffic of access devices and users converges at the aggregation layer and is
then forwarded to the core layer. In this way, the aggregation layer increases
the quantity of users who can access the core layer.
● Access layer
It connects various terminals to the campus network. Typically, Ethernet
switches are used at this layer. Some terminals may need other types of
access devices, such as APs and IoT access gateways.
● Campus user terminal layer
It contains various campus terminals, including computers, laptops, printers,
fax machines, mobile phones, and cameras.
gateways, and provides access for wired, wireless, and IoT terminals of
campus users.
Multiple campuses are interconnected through DWDM devices.
● Security design
Firewalls are deployed at the egress for isolation, anti-DDoS devices are used
to defend against DDoS attacks from the Internet, and the sandbox is used to
prevent unknown threats.
● Authentication design
All users are authenticated by the BRAS device in a unified manner, and the
third-party accounting system is used to implement accounting. Multi-path
load balancing is implemented to improve the utilization of multi-link
resources at the Internet egress of the campus network.
● IoT design
IoT applications can be flexibly expanded through edge computing gateways
and wireless private networks to manage logistics assets.
4 Network Plan
● The entire campus network uses a three-layer architecture, including the core
layer, aggregation layer, and access layer. Two core switches form a stack and
are deployed at the core layer to connect to all access switches. Terminals are
directly connected to access switches.
● Two BRASs as authentication access points work in HSB mode and connect to
the core switches in off-path mode.
● Two firewalls work in HSB mode. If the BRASs connect to the core switches in
off-path mode, the firewalls connect to the core switches. If the BRASs
connect to the core switches in in-path mode, the firewalls connect to the two
BRASs and the ISP.
● iMaster NCE-Campus functions as a network controller, and iMaster NCE-
CampusInsight functions as a network analyzer.
● iMaster NCE-Campus and iMaster NCE-CampusInsight connect to the core
switches through a switch.
● Set parameters based on network conditions, such as the network scale and
topology. The recommended values and precautions provided in the following
tables are for reference only.
● In this solution, you can select a physical interface or an Eth-Trunk interface as the
public network interface. If you select an Eth-Trunk interface as the public network
interface, run the mode lacp-static command.
XGigab XGigab
itEther itEther
net6/0/ net4/0/
6 6
This section does not include the network planning configuration for VRRP
HSB. For details, see the corresponding section.
5 Deployment Process
Figure 5-1 and Figure 5-2 show the solution deployment process.
You can view the basic network configuration, network egress configuration,
security service configuration, access control configuration, and O&M
management configuration of the solution by referring to CloudCampus
Documentation.
This document focuses on the unauthorized access prevention solution and the
digital map for intelligent O&M.
6 Installation
NOTE
When installing iMaster NCE-Campus, you need to install the terminal identification value-
added feature so that the terminal view of the digital map can be accessed.
BRAS router Apply for and install licenses based on the purchased
license items in the bill of quantity (BOQ) of this project
by referring to Huawei Router License Operation Guide.
iMaster NCE- For details about how to apply for and install a license for
CampusInsight the analyzer that is integrated with the controller, see
iMaster NCE-CampusInsight License Usage Guide
(Integrated with iMaster NCE-Campus).
For details about how to apply for and install a license for
the analyzer that is independently deployed, see iMaster
NCE-CampusInsight License Usage Guide (Independent
Deployment).
Use BNG This license is for the BNG By NE40E series, ME60
r function function and supports 32K devi series, NetEngine 8000E
acc license users by default. It can be ce M8, NetEngine 8000
ess purchased to increase the M14, NetEngine 8000
number of users to 128K. M8K, NetEngine 8000
PPPoE, IPoE, L2TP, DAA, M14K, and NetEngine
and EDSG functions are 8000 X
included in this license.
7 Deployment Configuration
Procedure
Step 1 Choose Resource Center > Site Management and click Create to create a site.
Set Device Type to LSW, WAC, and FW, and click OK.
Step 2 Set parameters in the Site Info area, such as Site name, Site location, and
Device type. In IPv4 single-stack or IPv4/IPv6 dual-stack deployment scenarios,
you can set Southbound IP service name as needed.
NOTE
Step 4 Click OK. The site is created and configurations are delivered.
----End
Procedure
Step 1 Choose Resource Center > Site Management > Import Network Plan from the
main menu. On the displayed page, click the template download link to download
the template.
Step 2 Enter the information about devices and physical links to be added based on the
template requirements.
Table 7-1 shows an example of the information entered on the Device sheet;
Table 7-2 shows an example of the information entered on the Board sheet; and
Table 7-3 shows an example of the information entered on the Link sheet.
NOTE
When you add a stack to a site on iMaster NCE-Campus by importing the stack information
through a template, the stack restarts if the actual stack information is different from the
information in the template imported to iMaster NCE-Campus. Before the restart, iMaster
NCE-Campus delivers new stack information (except the slot IDs of modular switch
members in the stack) to the stack. Therefore:
● For a stack of modular switches that needs to go online on iMaster NCE-Campus using
commands, you can run the display esn and display css status commands during local
command configuration and record the mappings between the ESNs, stack IDs, and
stack priorities of the member switches in the stack. To prevent a stack restart, ensure
that the stack information filled in the template is the same as that when the stack is
set up.
● For a stack of fixed switches that achieves plug-and-play in DHCP mode, the stack
needs to have empty configuration. In addition, you are advised to fill in the stack
information in the template as planned due to the presence of many fixed switches on
the stadium network. If the stack information in the template is different from the
original information, the stack can restart and go online again according to the planned
information.
● ESN: If the ESN is not specified, the device name and device model must be
specified. If the ESN is specified, you are advised to specify the device model
as well. Otherwise, the device may fail to be added.
The ESNs of switches, APs, and WACs must be imported to the site to which
these devices belong. You are advised to enter device ESNs using the network
plan template.
● Device Name: Mandatory.
● Device Model: Optional for devices with 20-character ESNs, and mandatory
for devices with 12-character ESNs.
● Description: Optional.
● Role: Optional. Configure roles for devices based on the site requirements. If
you do not set the device role when adding a device, the system sets the
device role to Access by default.
● Stack Name: Mandatory for stacked devices.
● Slot ID: Mandatory for stacked devices.
● Stack Priority: Optional. If this parameter is not set for a stack device, the
default value 100 is used.
Step 3 On iMaster NCE-Campus, select the template file for Select file, and click Upload.
After the upload is complete, click Import All to import the data in the template
file to the site.
NOTE
If you need to add new devices and links to the network, you can import a new template
that contains information about the new devices, devices connected to the new devices,
and new links.
----End
Configuration Roadmap
1. Configure the VLAN and IP address for the core switch to connect to iMaster
NCE-Campus.
2. Configure a static route from the core switch to iMaster NCE-Campus.
3. Configure the core switch to communicate with iMaster NCE-Campus in
NETCONF over SSH Call Home mode.
NOTE
To manage a core switch on iMaster NCE-Campus using commands, you need to connect
the core switch to iMaster NCE-Campus first and then enable the NETCONF function.
Procedure
Basic configurations on the core switch have been completed. Therefore, in this
section, you only need to configure parameters for communication between the
core switch and iMaster NCE-Campus.
Step 2 Check whether the core switch is managed by iMaster NCE-Campus on the
controller's web UI or by running the following command:
[Core] display netconf connect-status
------------------------------------------------------------------------------
Netconf status : enable
Upload alarm status : enable
Connected to controller before : yes
------------------------------------------------------------------------------
Controller address source : --
Controller URL : --
Controller IP address : --
Controller port : --
Management VLAN : --
Management IP address : --
Register phase : --
Register status : --
------------------------------------------------------------------------------
Netconf src-ip : 172.31.31.4
Netconf src-ipv6 : --
Netconf src-port : 830
Controller information :
No Mode name IP Port Connected
-------------------------------------------------------------------------------
1 callhome imaster-campus 172.31.31.30 10020
Y
2 ssh - - - N
3 ssh - - - N
4 ssh - - - N
5 ssh - - - N
6 ssh - - - N
-------------------------------------------------------------------------------
----End
NCE-Campus mainly manages devices from the access layer to the core layer. To
manage a core switch, you need to run commands on the core switch to connect
it to iMaster NCE-Campus.
Configuration Roadmap
1. Configure the VLAN and IP address for the core switch to connect to iMaster
NCE-Campus.
2. Configure a static route from the core switch to iMaster NCE-Campus.
3. Configure the core switch to communicate with iMaster NCE-Campus in
NETCONF over SSH Call Home mode.
NOTE
To manage a core switch on iMaster NCE-Campus using commands, you need to connect
the core switch to iMaster NCE-Campus first and then enable the NETCONF function.
Procedure
Step 1 Configure an SSH server user.
<Core> system-view
[Core] ssh user huawei
[Core] ssh user huawei authentication-type x509v3-rsa
[Core] ssh user huawei assign pki default
[Core] ssh user huawei service-type snetconf
NOTE
The username must be huawei. Otherwise, the device cannot go online, causing a
deployment failure.
Step 2 Specify the source interface of the SSH server. When Warning is displayed, enter y
and press Enter.
[Core] ssh server-source all-interface
Step 4 Configure the SSH authentication mode. Set the authorization type and the public
key algorithm of the SSH server. Add the x509v3-ssh-rsa algorithm without
changing the current public key algorithms configured on the SSH server. In this
example, the default public key algorithms RSA_SHA2_256 and RSA_SHA2_512 are
used.
[Core] ssh server assign pki default
[Core] ssh authorization-type default root
[Core] ssh server publickey x509v3-ssh-rsa rsa_sha2_256 rsa_sha2_512
Step 6 Set parameters for interconnection with iMaster NCE-Campus on the device based
on the ZTP configuration that has been performed on iMaster NCE-Campus. The
callhome template name must be set to default-callhome, and the endpoint
name can be set as needed. You are advised to set the endpoint name in the
format interface-name_ac-south-ip-address.
[Core] netconf
[Core-netconf] callhome default-callhome
Step 7 Load the preset CA certificate from the NVRAM to the realm default.
[Core] pki import-certificate default_ca realm default
----End
Context
The core switches have set up a stack or a CSS, and the stack/CSS needs to be
managed by iMaster NCE-Campus.
Prerequisites
The controller is configured by referring to 7.3.2 Configuring the Controller to
Manage the Core Switch Running V200 Through NETCONF to manage two
member devices.
Procedure
Step 1 Choose Resource Center > Site Management.
Step 2 Choose Device Management > Device Group and click Create Stack.
Step 3 Set parameters such as Stack name and Site, and select Synchronize from
detected stacks or Manual creation for Creation mode.
1. Synchronize from detected stacks: The system automatically detects the
stacks that have been set up on switches. You need to manually add the stack
of detected member switches. If the stack member information fails to be
obtained, click Synchronize from detected stacks again to refresh the stack
member information.
2. Manual creation: Switches need to be manually added to a stack.
Step 4 Choose Resource Center > Device Management from the main menu. Then,
choose Device Management > Device Group and check the status of the added
device. If the device status is Normal or Alarm, the device is successfully
managed.
----End
Configuration Roadmap
1. Configure the core switch as the management subnet gateway of the
aggregation and access switches.
2. Configure the management VLAN auto-negotiation function with the core
switch acting as the root device.
NOTE
In this example, aggregation/access switches and APs respectively use different auto-
negotiated management VLANs. When configuring the management VLANs, enable the
management VLAN auto-negotiation function for wireless devices.
Data Plan
Procedure
Step 1 On the core switch, configure a management subnet for aggregation and access
switches, enable the DHCP server function on the gateway interface of the subnet,
and enable the function of automatically negotiating the iMaster NCE-Campus
address.
Step 2 Choose Network Configuration > Site Configuration > Site Configuration from
the main menu. Click the Site Configuration tab, and choose Switch > Subnet
from the navigation pane. On the page that is displayed, click Create. Configure
the wired management subnet based on the following information, and then click
OK.
● Set Device to Core, Subnet name to Manage_Net, VLAN ID to 4080, IP
assignment to Manual, and IP address/Mask to 172.31.32.1/24.
● Toggle on DHCP and set DHCP mode to Server.
● Enable Management network. Then set AP mode to Fit AP, and enable
Controller address auto-negotiation.
● Enable Static management IP address for switches and set Static
management IP address range to 172.31.32.2-172.31.32.100.
NOTE
– If IP assignment is set to Auto, you can click in the Operation column of the
subnet list to modify a created subnet and configure the static management IP
address function for switches.
– A core switch must have the IP addresses that can be dynamically assigned.
Aggregation and access switches obtain IP addresses when they go online for the
first time in PnP mode. It is recommended that half of the IP address segment of a
management subnet be used to allocate static IP addresses and the other half be
used to allocate dynamic IP addresses.
DHCP mode The options include Server and Relay. In this example, the
server mode is used. As such, the core switch acts as a DHCP
server to dynamically assign IP addresses to aggregation and
access switches for device management.
Step 3 Configure the management VLAN auto-negotiation function on the core switch. In
this way, the core switch can act as the root device to configure a management
VLAN for aggregation and access switches through PnP packet negotiation.
Step 4 Choose Network Configuration > Site Configuration > Site Configuration from
the main menu, and click the Site Configuration tab. Choose Site >
Management VLAN from the navigation pane. Select the core switch in the
device list, and then click . In the Modify Management VLAN window that is
displayed, set Management VLAN auto-negotiation for wired devices to 4080
and Management VLAN auto-negotiation for wireless devices to 3100, and
disable Allow traffic on uplink interfaces. After the configuration is completed,
click OK. Then enable Management VLAN Auto-Negotiation and click Apply.
Management With the current device acting as the root device, the
VLAN auto- management VLAN of the connected downlinks can be enabled
negotiation level by level through the negotiation mechanism. When wired
for wired and wireless devices share the same management VLAN and the
devices auto-negotiated management VLAN for wireless devices is not
configured, if the root device or its connected device identifies
that a downlink port is connected to an AP, the device changes
the PVID of the port to the auto-negotiated management VLAN
ID for wired devices.
Management With the current device acting as the root device, the wireless
VLAN auto- management VLAN of the connected downlinks can be enabled
negotiation level by level through the negotiation mechanism. When
for wireless management VLANs are planned separately for wired and
devices wireless devices, and both management VLAN auto-negotiation
for wired devices and management VLAN auto-negotiation for
wireless devices are configured, if the root device or its
connected device identifies that a downlink port is connected to
an AP, the device changes the PVID of the port to the configured
auto-negotiated management VLAN ID for wireless devices,
instead of the auto-negotiated management VLAN ID for wired
devices.
Set as the After this function is enabled, the PVID of the current device's
PVID for uplink interface will be changed to the management VLAN ID.
uplink
interfaces
Step 5 Verify the configuration for managing aggregation and access switches.
● Check the device onboarding information on iMaster NCE-Campus.
Choose Resource Center > Device Management from the main menu and
view the device list of the site. If Status is displayed as Normal, the devices
go online successfully.
● Check the configuration delivery results on iMaster NCE-Campus.
Choose Task Center > Configuration Result to view the configuration result.
You can select a device and view the configuration details in the feature list,
including whether the configuration is successfully delivered to the device.
● Log in to the device CLI to view the device onboarding information.
Run the display netconf connect-status command to check the NETCONF
configuration on the switch, including the connection status between the
switch and iMaster NCE-Campus.
[Agg] display netconf connect-status
------------------------------------------------------------------------------
Partner:
--------------------------------------------------------------------------------
ActorPortName SysPri SystemID PortPri PortNo PortKey PortState
GigabitEhternet5/0/5 32768 00e0-fc6e-bb11 32768 262 2609 10111100
GigabitEhternet5/0/6 32768 00e0-fc6e-bb11 32768 263 2609 10111100
GigabitEhternet6/0/5 32768 00e0-fc6e-bb11 32768 262 2609 10111100
GigabitEhternet6/0/6 32768 00e0-fc6e-bb11 32768 263 2609 10111100
----End
Network Requirements
● WAC networking mode: Layer 2 bypass mode
● DHCP deployment mode: The WAC and core switch function as DHCP servers
to assign IP addresses to APs and STAs, respectively.
● Service data forwarding mode: direct forwarding
● CSS: Two switches at the core layer are deployed in a CSS.
Data Plan
Item Data
Configuration Roadmap
1. Configure network connectivity between WACs, APs, and other network
devices.
2. Configure a VRRP group on WAC1 and WAC2. Configure a higher priority for
WAC1 so that it becomes the master device to forward traffic. Configure a
lower priority for WAC2 so that it becomes the backup device.
3. Configure basic WLAN services to ensure that users can connect to the
Internet through the WLAN.
4. Configure the HSB function on WAC1 and WAC2 so that service information
on WAC1 is backed up to WAC2 in real time or in batches, ensuring seamless
service switchover from the master device to the backup device in case of a
master device failure.
5. Configure wireless configuration synchronization in VRRP HSB scenarios.
Configuration Precautions
● In direct forwarding mode, you are advised to configure multicast packet
suppression on the interfaces of a switch connected to APs. In tunnel
forwarding mode, you are advised to configure multicast packet suppression
in traffic profiles of the WAC.
● The port isolation configuration is recommended on the ports of the device
directly connected to APs. If port isolation is not configured and direct
forwarding is used, a large number of unnecessary broadcast packets may be
generated in the VLAN, blocking the network and degrading user experience.
● In tunnel forwarding mode, the management VLAN and service VLAN cannot
be the same. Only packets from the management VLAN can be transmitted
between the WAC and APs, and packets from the service VLAN cannot.
● In the VRRP HSB networking, the configurations of the DHCP address pools
on the master and backup ACs must be consistent. For example, the ranges of
IP addresses that cannot be automatically assigned must be consistent on the
master and backup WACs.
● In wireless configuration synchronization scenarios, the device does not
support profile-based configuration for source-ip and nas-ip.
Procedure
Step 1 Configure switches, WAC1, and WAC2 to ensure that APs and WACs can exchange
CAPWAP packets with each other.
NOTE
If direct forwarding is used, you are advised to configure port isolation on GE1/0/1 of
switches connected to APs. If port isolation is not configured, a large number of
unnecessary broadcast packets may be transmitted in the VLANs, or STAs connected to
different APs can directly communicate at Layer 2.
# On ACC0102, set the PVIDs of GE1/0/1 and GE2/0/1 connected to APs to VLAN
3100 (management VLAN) and add the interfaces to VLAN 3100 and VLAN 3102
(service VLAN). Add the interfaces connecting ACC0102 to AGG0102 to Eth-Trunk
1, and allow packets from VLAN 3100 and VLAN 3102 to pass through Eth-Trunk
1.
<ACC0102> system-view
[ACC0102] vlan batch 3100 3102
[ACC0102] interface gigabitethernet 1/0/1
//The configuration for gigabitethernet 2/0/1 is the same as that for gigabitethernet 1/0/1, and is not
mentioned here.
[ACC0102-GigabitEthernet0/0/1] port link-type trunk
[ACC0102-GigabitEthernet0/0/1] port trunk pvid vlan 3100
[ACC0102-GigabitEthernet0/0/1] undo port trunk allow-pass vlan 1
[ACC0102-GigabitEthernet0/0/1] port trunk allow-pass vlan 3100 3102
[ACC0102-GigabitEthernet0/0/1] port-isolate enable
[ACC0102-GigabitEthernet0/0/1] quit
[ACC0102] interface eth-trunk 1
[ACC0102-Eth-Trunk1] port link-type trunk
[ACC0102-Eth-Trunk1] undo port trunk allow-pass vlan 1
[ACC0102-Eth-Trunk1] port trunk allow-pass vlan 3100 3102
[ACC0102-Eth-Trunk1] quit
[ACC0102] interface Xgigabitethernet 1/0/4
[ACC0102-Xgigabitethernet 1/0/4] undo port link-type
[ACC0102-Xgigabitethernet 1/0/4] eth-trunk 1
[ACC0102-Xgigabitethernet 1/0/4] quit
[ACC0102] interface Xgigabitethernet 2/0/4
[ACC0102-Xgigabitethernet 2/0/4] undo port link-type
[ACC0102-Xgigabitethernet 2/0/4] eth-trunk 1
[ACC0102-Xgigabitethernet 2/0/4] quit
# Add the interfaces connecting Core to AGG0102 to the planned Eth-Trunk. Set
the Eth-Trunk type to trunk, and allow packets from VLAN 3100 and VLAN 3102
to pass through the Eth-Trunk. Add the interfaces connecting Core to WAC1 and
WAC2 to the planned Eth-Trunk. Set the Eth-Trunk type to trunk, and allow
packets from VLAN 3100 to pass through the Eth-Trunk.
[Core] vlan batch 3100 3102
[Core] interface eth-trunk 2
[Core-Eth-Trunk2] port link-type trunk
[Core-Eth-Trunk2] undo port trunk allow-pass vlan 1
[Core-Eth-Trunk2] port trunk allow-pass vlan 3100 3102
[Core-Eth-Trunk2] quit
# Add the interfaces connecting WAC1 to Core to the planned Eth-Trunk, and
allow packets from VLAN 3100 to pass through the Eth-Trunk.
[WAC1] vlan batch 3100 3102
[WAC1] interface eth-trunk 3
[WAC1-eth-trunk 3] port link-type trunk
[WAC1-eth-trunk 3] undo port trunk allow-pass vlan 1
[WAC1-eth-trunk 3] port trunk allow-pass vlan 3100
[WAC1-eth-trunk 3] quit
[WAC1] interface 10GE 0/0/10
[WAC1-10GE 0/0/10] undo port link-type
[WAC1-10GE 0/0/10] eth-trunk 3
[WAC1-10GE 0/0/10] quit
[WAC1] interface 10GE 0/0/11
[WAC1-10GE 0/0/11] undo port link-type
[WAC1-10GE 0/0/11] eth-trunk 3
[WAC1-10GE 0/0/11] quit
[WAC1] interface vlanif 3100
[WAC1-Vlanif3100] ip address 10.10.100.1 24
[WAC1-Vlanif3100] quit
# Add the interfaces connecting WAC2 to Core to the planned Eth-Trunk, and
allow packets from VLAN 3100 to pass through the Eth-Trunk.
[WAC2] vlan batch 3100 3102
[WAC2] interface eth-trunk 4
Configure the DNS server address as required. The common methods are as follows:
● In the interface address pool scenario, run the dhcp server dns-list ip-address &<1-8>
command in the VLANIF interface view.
● In the global address pool scenario, run the dns-list ip-address &<1-8> command in the
IP address pool view.
# Create a management VRRP group on WAC1. Set the VRRP priority of WAC1 to
120 and the preemption delay to 1800 seconds.
[WAC1] interface vlanif 3100
[WAC1-Vlanif3100] vrrp vrid 1 virtual-ip 10.10.100.3
[WAC1-Vlanif3100] vrrp vrid 1 priority 120
[WAC1-Vlanif3100] vrrp vrid 1 preempt-mode timer delay 1800
[WAC1-Vlanif3100] admin-vrrp vrid 1
[WAC1-Vlanif3100] quit
# Create HSB service 0 on WAC1, and configure the IP addresses and port
numbers for the active and standby channels. Set the number of retransmission
times and the interval of HSB service 0.
[WAC1] hsb-service 0
[WAC1-hsb-service-0] service-ip-port local-ip 10.10.29.1 peer-ip 10.10.29.2 local-data-port 10241 peer-data-
port 10241
[WAC1-hsb-service-0] service-keep-alive detect retransmit 3 interval 6
[WAC1-hsb-service-0] quit
# Create HSB group 0 on WAC1, and bind HSB service 0 and mVRRP group 1 to
HSB group 0.
[WAC1] hsb-group 0
[WAC1-hsb-group-0] bind-service 0
[WAC1-hsb-group-0] track vrrp vrid 1 interface vlanif 3100
[WAC1-hsb-group-0] quit
# Create HSB service 0 on WAC2, and configure the IP addresses and port
numbers for the active and standby channels. Set the number of retransmission
times and the interval of HSB service 0.
[WAC2] hsb-service 0
[WAC2-hsb-service-0] service-ip-port local-ip 10.10.29.2 peer-ip 10.10.29.1 local-data-port 10241 peer-data-
port 10241
[WAC2-hsb-service-0] service-keep-alive detect retransmit 3 interval 6
[WAC2-hsb-service-0] quit
# Create HSB group 0 on WAC2, and bind HSB service 0 and mVRRP group 1 to
HSB group 0.
[WAC2] hsb-group 0
[WAC2-hsb-group-0] bind-service 0
[WAC2-hsb-group-0] track vrrp vrid 1 interface vlanif 3100
[WAC2-hsb-group-0] quit
2. Import an AP on WAC1.
[WAC1] wlan
[WAC1-wlan-view] ap auth-mode mac-auth
[WAC1-wlan-view] ap-id 0 ap-mac 00e0-fc76-e360
[WAC1-wlan-ap-0] ap-name area_1
[WAC1-wlan-ap-0] ap-group ap-group1
Warning: This operation may cause AP reset. If the country code changes, it will clear channel, power
and antenna gain configuration s of the radio, Whether to continue? [Y/N]:y [AC1-wlan-ap-0] quit
[AC1-wlan-view] display ap all
Total AP information:
nor : normal [1]
Extra information: P : insufficient power supply
--------------------------------------------------------------------------------------------------
ID MAC Name Group IP Type State STA Uptime ExtraInfo
--------------------------------------------------------------------------------------------------
0 00e0-fc76-e360 area_1 ap-group1 10.23.100.254 AP5030DN nor 0 10S -
--------------------------------------------------------------------------------------------------
Total: 1
In this example, the security policy is set to WPA-WPA2+PSK+AES and the password to
YsH_2022. In actual situations, configure the security policy according to service
requirements.
[WAC1-wlan-view] security-profile name wlan-net
[WAC1-wlan-sec-prof-wlan-net] security wpa-wpa2 psk pass-phrase YsH_2022 aes
[WAC1-wlan-sec-prof-wlan-net] quit
# Create the SSID profile wlan-net and set the SSID name to wlan-net.
[WAC1-wlan-view] ssid-profile name wlan-net
[WAC1-wlan-ssid-prof-wlan-net] ssid wlan-net
[WAC1-wlan-ssid-prof-wlan-net] quit
# Create the VAP profile wlan-net, set the data forwarding mode and service
VLAN, and bind the security profile and SSID profile to the VAP profile.
[WAC1-wlan-view] vap-profile name wlan-net
[WAC1-wlan-vap-prof-wlan-net] forward-mode direct-forward
[WAC1-wlan-vap-prof-wlan-net] service-vlan vlan-id 3102
[WAC1-wlan-vap-prof-wlan-net] security-profile wlan-net
[WAC1-wlan-vap-prof-wlan-net] ssid-profile wlan-net
[WAC1-wlan-vap-prof-wlan-net] quit
# Bind the VAP profile wlan-net to radios 0 and 1 of APs in the AP group.
[WAC1-wlan-view] ap-group name ap-group1
[WAC1-wlan-ap-group-ap-group1] vap-profile wlan-net wlan 1 radio 0
[WAC1-wlan-ap-group-ap-group1] vap-profile wlan-net wlan 1 radio 1
[WAC1-wlan-ap-group-ap-group1] quit
[WAC1-wlan-view] quit
Step 8 Configure DTLS encryption for inter-WAC control and data tunnels.
# Configure DTLS encryption for inter-WAC control and data tunnels on WAC1.
[WAC1] capwap dtls inter-controller psk YsH_2022
[WAC1] capwap dtls inter-controller control-link encrypt on
Warning: This operation may cause devices using CAPWAP connections to reset or go offline. Continue? [Y/
N]:y
[WAC1] capwap dtls inter-controller data-link encrypt
Warning: This operation may cause devices using CAPWAP connections to reset or go offline. Continue? [Y/
N]:y
[WAC1] wlan
# Configure DTLS encryption for inter-WAC control and data tunnels on WAC2.
[WAC2] capwap dtls inter-controller psk YsH_2022
[WAC2] capwap dtls inter-controller control-link encrypt on
Warning: This operation may cause devices using CAPWAP connections to reset or go offline. Continue? [Y/
N]:y
[WAC2] capwap dtls inter-controller data-link encrypt
Warning: This operation may cause devices using CAPWAP connections to reset or go offline. Continue? [Y/
N]:y
[WAC2] wlan
# Run the display hsb-service 0 command on WAC1 and WAC2 to check the
HSB service status. In the command output of both devices, the value
Connected of Service State indicates that the HSB channel has been
established.
[WAC1] display hsb-service 0
Hot Standby Service Information:
----------------------------------------------------------
Local IP Address : 10.10.29.1
Peer IP Address : 10.10.29.2
Source Port : 10241
Destination Port : 10241
Keep Alive Times :3
Keep Alive Interval : 6
Service State : Connected
Service Batch Modules :
Shared-key :-
----------------------------------------------------------
[WAC2] display hsb-service 0
Hot Standby Service Information:
----------------------------------------------------------
Local IP Address : 10.10.29.2
Peer IP Address : 10.10.29.1
Source Port : 10241
Destination Port : 10241
Keep Alive Times :3
Keep Alive Interval : 6
Service State : Connected
Service Batch Modules :
Shared-key :-
----------------------------------------------------------
Run the display hsb-group 0 command on WAC1 and WAC2 to check the
running status of the HSB group.
[WAC1] display hsb-group 0
Hot Standby Group Information:
----------------------------------------------------------
HSB-group ID :0
Vrrp Group ID :1
Vrrp Interface : Vlanif3100
Service Index :0
Group Vrrp Status : Master
Group Status : Active
Group Backup Process : Realtime
Backup State : Ended
Backup Start Time : JAN, 14 Sep 2024 14:30:46
3. The WLAN with SSID wlan-net is available for STAs connected to the AP, and
these STAs can connect to the WLAN and go online normally.
# Simulate a fault of the master WAC by restarting the master WAC to verify
the backup configuration. Restart WAC1. When the link between the AP and
WAC1 is disconnected, WAC2 becomes the master WAC to ensure service
stability.
NOTE
Before restarting the WAC, run the save command to save the configuration file on the
WAC to prevent configuration loss after the restart.
# During the restart of WAC1, services on the STAs are not interrupted. After the
AP goes online on WAC2, run the display ap all command on WAC2. The
command output shows that the AP state changes from standby to normal.
# After WAC1 recovers from the restart, an active/standby switchback is triggered.
The AP automatically goes online on WAC1.
----End
Context
In this solution, two WACs work in HSB mode and need to be managed by iMaster
NCE-Campus.
Procedure
Step 1 Manually add the WAC information to the site.
Choose Resource Center > Device Management > Device, click Add Device, and
manually add device ESNs and roles to the site. Then click OK.
NOTE
● The ESNs of switches, APs, and WACs must be entered into the site. You are advised to
enter device ESNs when adding them to the site.
● If the ESN of a device has 12 characters, you must set Mode to Device model and
specify the device model in the Device information area.
Step 2 Configure the core switch as the management subnet gateway (VLAN 3100) of
the WACs. For details, see 7.5.3 Configuring Fit APs to Join a WAC.
Step 3 Configure management VLAN auto-negotiation for wireless devices on the core
switch that acts as the root device. For details, see Configuring Aggregation and
Access Switches to Be Managed by the Controller (Batch Import of Device and
Eth-Trunk Information).
Step 4 Create Eth-Trunks for connecting to the downstream WACs on the core switch.
Create Eth-Trunk interfaces for connecting to the downstream WACs on the core
switches.
Choose Network Configuration > Site Configuration > Site Configuration from
the main menu. On the Site Configuration tab page, choose Switch > Interface
from the navigation pane. The physical interface configuration page is displayed.
Click a stack at the access layer, select the member interfaces to be aggregated on
the interface panels of the two member switches, and click Aggregate. In the
Interface Configuration area, set the IDs of the Eth-Trunk interfaces to 3 and 4,
respectively, set the link type to hybrid, and add the interfaces to VLAN 3100.
NOTE
Wireless AP management packets are sent from the core switch to the WACs, while wireless
service packets do not need to be forwarded by the WACs. Therefore, when configuring
wireless management VLAN, select Eth-Trunks 3 and 4 of the core switch as the access
interfaces for wireless AP management VLANs. Since the default type of links delivered by
iMaster NCE-Campus is hybrid, you need to set the link type of Eth-Trunks 3 and 4
connected to the WACs to hybrid.
----End
Procedure
Step 1 Configure a DHCP interface address pool for the core switch, and enable Option
43 to carry the WAC's IP address. In this example, the management channel
between the WAC and AP is automatically established using the auto-negotiated
management VLAN for wireless devices, which has been enabled in 7.4
Configuring Aggregation and Access Switches to Go Online. The procedure for
configuring a wireless management subnet is as follows:
Choose Network Configuration > Site Configuration > Site Configuration from
the main menu. Click the Site Configuration tab, and choose Switch > Subnet
from the navigation pane. On the page that is displayed, click Create. Configure
the subnet based on the following information, and then click OK.
● Set Device to Core, Subnet name to AP_Manage_Net, VLAN ID to 3100, IP
assignment to Manual, and IP address/Mask to 10.10.100.254/24.
● Toggle on DHCP and set DHCP mode to Server.
● Enable Management network. Then set AP mode to Fit AP, enable WAC
address auto-negotiation, and set WAC address to 10.10.100.1.
● If Fit APs are added in advance by importing a network plan, perform steps 1
and 2 to manage them. If Fit APs are not added in advance, perform steps 2
and 3 to manage them after they are connected to the network.
Step 2 Associate APs with the WAC. Choose Network Configuration > Site
Configuration > Site Configuration from the main menu, click the Site
Configuration tab, and choose Switch > Fit AP Management from the
navigation pane. In the WAC list, select the row where the core switch resides, and
click Add in the lower right corner to add the Fit APs added offline for
management by the core switch.
NOTE
After you configure an existing WAC to manage working Fit APs, the original configurations
on the Fit APs will be lost. Exercise caution when performing this operation.
Step 3 Manually add APs that are not added through network plan import in advance.
Choose Resource Center > Device Management. In the device list, click the
standalone WAC. The Basic Information page is displayed. In the AP List area,
select the APs to be managed, click Repair, and select the corresponding site.
Then click OK.
----End
NOTICE
● SAC affects the forwarding performance of devices. Therefore, use SAC properly
when necessary.
● Only the following models support SAC: S5731-H, S5731-H-K, S5731S-H,
S5731-S, S5731S-S, S5732-H, S5732-H-K, S6730-H, S6730-H-K, S6730S-H,
S6730-S, and S6730S-S.
● Functions such as application assurance and in-band flow measurement are
supported on switches after their resource mode is configured as planned.
● To use application assurance, both access and core switches must support
service awareness.
● To use in-band flow measurement, access switches or access APs must support
service awareness.
Configuration Roadmap
The configuration roadmap is as follows:
1. Set the resource allocation mode.
2. Enable the IAE.
3. Update the signature database for application identification.
4. Enable service awareness on an interface.
Procedure
Configure the service awareness function.
# Change the resource allocation mode of a switch to sac.
<HUAWEI> system-view
[HUAWEI] assign resource-mode sac
[HUAWEI] quit
NOTE
After the resource allocation mode is set to sac, you need to save the configuration and
restart the switch for the configuration to take effect.
You can change the resource allocation mode of mid-points (such as aggregation switches)
for in-band flow measurement to Enhanced_sipfm. After the resource allocation mode is
changed, you need to save the configuration and restart the devices.
# Log in to SwitchA on the PC connected to GE0/0/1 using STelnet, and run the
display traffic policy statistics interface gigabitethernet 0/0/1 inbound
command to check STelnet packet statistics. The command output shows statistics
about the packets matching the traffic classifier, and the forwarded packets
matching the traffic classifier.
[HUAWEI] display traffic policy statistics interface gigabitethernet 0/0/1 inbound
Interface: GigabitEthernet0/0/1
Traffic policy inbound: p1
Rule number: 1
Current status: success
Statistics interval: 300
---------------------------------------------------------------------
Board : 0
---------------------------------------------------------------------
Matched | Packets: 21
| Bytes: 1,986
| Rate(pps): 0
| Rate(bps): 0
---------------------------------------------------------------------
Passed | Packets: 21
| Bytes: 1,986
| Rate(pps): 0
| Rate(bps): 0
---------------------------------------------------------------------
Dropped | Packets: 0
| Bytes: 0
| Rate(pps): 0
| Rate(bps): 0
---------------------------------------------------------------------
Filter | Packets: 0
| Bytes: 0
---------------------------------------------------------------------
Car | Packets: 0
| Bytes: 0
---------------------------------------------------------------------
● In this example, the direct data forwarding mode is used. Therefore, you need to enable
the security engine for both the WAC and AP. If tunnel forwarding is used, you need to
enable the security engine only on the WAC.
● Application assurance and in-band flow measurement are available on the WAC and the
AP after their resource modes are configured as planned.
1. Choose Configuration > QoS > App Identification & Optimization > SAC >
SAC Configuration.
2. Enable Loading the SAC signature database on the AC.
3. Disable Loading the SAC signature database on the AP. In Loading the
SAC Signature Database for APs by AP Group, enable SAC for a specified AP
group.
4. Click Apply.
----End
Table 7-10 Data plan for VLANs between the core switches and the BRASs
S Interface VLAN IP Des Interface VLAN IP Int
o on the ID of Address tin on the ID of Addre erf
ur Source the of the ati Destinati the ss of ace
ce Device Interfac Interfac on on Interfa the Des
D e on the e on the Dev Device ce on Interf crip
e Source Source ice the ace tio
vi Device Device Destin on n
ce ation the
Device Desti
natio
n
Devic
e
Table 7-11 lists the parameters for planning VRRP between the core switch and
the BRAS nodes.
Table 7-11 Data plan for VRRP between the core switch and the BRAS nodes
Item ME60-a ME60-b
Table 7-12 lists the RBS planning parameters for the BRASs.
Procedure
Step 1 Configure VRRP on the access side of the master and backup BRASs. ME60-a is the
master device, and ME60-b is the backup device.
Step 4 Add the interfaces connecting the core switches to the BRAS nodes to VLAN 3940.
#
interface eth-trunk 5.3940
port link-type trunk
port trunk allow-pass vlan 3940
trust dscp
#
interface eth-trunk 6.3940
port link-type trunk
port trunk allow-pass vlan 3940
trust dscp
#
----End
Table 7-13 Data plan for VLANs between the core switch and BRASs
S Et Source VL IP De Et Destina VLA IP Interfa
o h- Device A Addre sti h- tion N ID Addr ce
u Tru Interfa N ss of na Tr Device of ess of Descrip
rc nk ce ID the tio un Interfa the the tion
e Int of Sourc n k ce Inter Desti
D erf th e De Int face natio
e ac e Devic vic erf on n
vi e Int e e ac the Devic
c on erf Interf e Desti e
e th ac ace on natio Interf
e e th n ace
So on e Devi
urc th De ce
e e sti
De So na
vic ur tio
e ce n
De De
vic vic
e e
Step 1 Configure a default static route to the core switch on the BRAS.
ip route-static vpn-instance vpn_xxx 0.0.0.0 0.0.0.0 vpn-instance vpn_xxx 10.10.211.4 //Configure a default
route to the core switch on the BRAS.
Step 4 Configure a VLANIF interface and a default route on the core switch.
#
ip vpn-instance out_vrf
ipv4-family
route-distinguisher 3940:1
#
vlan 3211
#
interface Vlanif3211 //Configure a VLANIF interface.
ip binding vpn-instance out_vrf
ipv6 enable
ip address 10.10.211.4 255.255.255.0
#
interface eth-trunk 5.3211 //Add the interface to the VLAN.
port link-type trunk
undo port trunk allow-pass vlan 1
port trunk allow-pass vlan 3211
port negotiation disable
trust dscp
#
interface eth-trunk 6.3211 //Add the interface to the VLAN.
port link-type trunk
undo port trunk allow-pass vlan 1
port trunk allow-pass vlan 3211
trust dscp
#
ospf 101 router-id 10.10.0.36 vpn-instance out_vrf //Configure OSPF.
area 0.0.0.0
#
ip route-static vpn-instance out_vrf 0.0.0.0 0.0.0.0 10.10.211.5 //Configure a default IPv4 route to the
firewall.
#
----End
Prerequisites
A site has been created. For details, see 7.1 Creating a Site.
Procedure
To enable LLDP globally, perform the following steps:
Step 2 Select a site from the Site drop-down list box in the upper left corner.
Step 4 Choose Site > Device System Configuration, and enable LLDP in the Others area.
NOTE
iMaster NCE-Campus supports only global LLDP configuration on switches. To enable LLDP
on WACs, you need to run commands. The following uses a WAC as an example:
<AC01>system-view
[AC01]lldp enable
----End
Step 1 Configure the core switch as a clock source on the analyzer and controller. The
following uses the configuration on the analyzer as an example. The procedure on
the controller is the same as that on the analyzer.
Step 3 Choose Maintenance > Time Management > Configure Time Zone and Time,
click Forcibly Synchronize, and wait until the synchronization is complete.
----End
Step 2 Select a site from the Site drop-down list box in the upper left corner.
Step 3 Choose Site > Device System Configuration on the Site Configuration tab page.
Step 4 In the Basic Configuration area, set Time zone, DST, and NTP server IP address,
and click OK.
----End
Prerequisites
The WAC that functions as the NTP client can communicate with the NTP server.
NTP time synchronization needs to be configured on both the master and backup
WACs.
Procedure
Step 1 Specify the source interface for sending NTP packets.
[WAC1]ntp-service enable
[WAC1]ntp server server-source -i all
Warning: Setting the protocol listening source address to all interfaces will bring security risks and lead to
connection interruptions. Continue? [Y/N]y
----End
Precautions
A planning project must meet the following requirements; otherwise, the import
will fail.
● The size of the planning file does not exceed 200 MB.
● When you upload planning projects exported from Huawei WLAN Planner,
you can upload a maximum of three planning projects at a time, with the size
of each planning project package within 30 MB.
● The number of regions in each planning project does not exceed 250. In a
single region, the number of APs does not exceed 200, and the number of
obstacles also does not exceed 200.
Prerequisites
A planning project has been exported from WLAN Planner. In addition, the MAC
addresses and SNs of APs at different positions have been filled in the planning
project.
Procedure
Step 1 Choose Network Monitoring > LAN Monitoring > WLAN Monitoring from the
main menu and select a site.
Step 2 Click Planning Import and click the Planner Project tab.
Step 3 Set Planner Type, click , and select the desired planning project package.
NOTE
● You need to upload planning projects exported from WLAN Planner. During the upload,
do not plan regions on multiple clients; otherwise, the upload may fail.
● You can import information only about the regions that you have permissions to
configure.
● If you want to upload planning projects exported from Huawei WLAN Planner, you can
upload a maximum of three planning projects at a time.
Step 4 Click Upload. After the upload is successful, the planned regions are displayed in
the region topology.
NOTE
After the upload is successful, you can view uploaded planning projects in the
Import Records area. After you click View Details, the file
PlannerProjectImportResult is automatically downloaded.
Right-click in the imported network planning diagram and choose Edit mode from
the shortcut menu. Then, right-click an AP and choose Associate with Pre-
deployed AP from the shortcut menu. Set the MAC address of the AP and click
OK.
You can associate APs in batches when the following conditions are met:
----End
Procedure
Step 1 Choose Network Monitoring > LAN Monitoring > WLAN Monitoring from the
main menu and select a site.
Step 2 Choose Planning Import, and click the Region List tab.
Step 3 Click to download the planning template, and fill in region and
AP information in this template.
NOTE
1. During the import, do not add, delete, or modify regions, WACs, or APs on multiple
clients. Otherwise, the import may fail.
2. You can import information only about the regions that you have permissions to
configure.
Step 4 In the resource tree, select the node for which you want to create a region, right-
click in the blank area in the region topology, and choose Add Region from the
shortcut menu.
Step 6 Click Confirm. The region is successfully created and displayed in the resource
tree.
Step 7 Right-click in the blank area in the region topology and choose Add AP from the
shortcut menu. In the displayed dialog box, plan and add APs and click OK.
----End
Prerequisites
The system administrator has configured interconnection with iMaster NCE-
CampusInsight. For details, see Configuring Interconnection Between iMaster
NCE-CampusInsight and iMaster NCE-Campus.
Procedure
Step 1 Log in to iMaster NCE-Campus as a tenant administrator and choose System >
System Management > Analysis Component Integration from the main menu.
Step 2 Click Synchronize Immediately and click OK in the dialog box that is displayed.
iMaster NCE-Campus then synchronizes data of all devices and sites under the
current tenant to iMaster NCE-CampusInsight.
----End
Follow-up Procedure
● After iMaster NCE-Campus and iMaster NCE-CampusInsight are
interconnected, you can be redirected to the iMaster NCE-CampusInsight web
UI through the iMaster NCE-Campus web UI. In this way, you can perform
O&M operations on iMaster NCE-CampusInsight.
● To view metric data of devices on iMaster NCE-CampusInsight, enable data
reporting by referring to Configuring Devices to Report Data to iMaster
NCE-CampusInsight.
8 Service Deployment
Procedure
Step 1 Choose Network Configuration > Site Configuration > Site Configuration from
the main menu, select a target site, and click the Site Configuration tab. On the
page that is displayed, choose Switch > Interface from the navigation pane and
click the Physical Interface tab.
Step 2 Select a switch to be configured, click interfaces, and set Link type. You can select
multiple physical interfaces or Eth-Trunk interfaces.
1. Set Link type to Trunk for device interconnection interfaces and allow
packets from all service VLANs to pass through.
2. Set Link type to Access for the interfaces connected to wired terminals and
set the VLAN IDs of the interfaces to the service VLAN IDs of wired users.
3. Set Link type to Trunk for the switch interfaces connected to APs, set the
default VLAN as the management VLAN of APs, and allow packets from the
service VLANs for wireless uses to pass through.
Step 3 Choose Remote Module > Module Configuration from the navigation pane,
select the device for which an RU is to be configured, select the interface
connected to the RU, and set RU interface VLAN mode.
1. If all terminals connected to the RU are in the same VLAN, set RU interface
VLAN mode to Transparent. That is, the RU interfaces do not change the
VLAN IDs of received packets.
2. If both wired terminals and APs are connected to the RU or different VLANs
are used, set RU interface VLAN mode to Manual.
a. For the interface connected to wired terminals, configure the default
VLAN and untagged VLANs as the user service VLANs.
b. For the interface connected to APs, configure the AP management VLAN
as the default VLAN and an untagged VLAN, and configure the wireless
user service VLAN as a tagged VLAN.
c. For the uplink interface of the RU, configure all service VLANs and AP
management VLANs as tagged VLANs.
----End
Procedure
Step 1 Log in to the web system of the WAC, choose Config Wizard > Wireless Service,
and click Create. On the Basic Information page that is displayed, set the SSID
name, forwarding mode, and service VLAN ID, and click Next.
Step 2 On the Security Authentication page, set Security settings to Open and click
Next.
Step 3 On the Access Control page, configure the bound AP group, effective radios, and
single-user rate limit or no rate limit based on service requirements, and click
Finish.
----End
Data Plan
Procedure
Step 1 Configure a RADIUS server group.
[~BRAS1] radius-server group shenlan
[*BRAS1-radius-shenlan] radius-server authentication 172.31.4.216 1812
[*BRAS1-radius-shenlan] radius-server accounting 172.31.4.216 1813
[*BRAS1-radius-shenlan] radius-server shared-key-cipher ******
[*BRAS1-radius-shenlan] radius-server source interface Loopback1
[*BRAS1-radius-shenlan] undo radius-server user-name domain-included
[*BRAS1-aaa-authen-radius] commit
[~BRAS1-aaa-authen-radius] quit
# Configure a local IPv6 prefix pool. WLAN users use IPv6 ND addresses, and the
prefix allocation mode is set to unshared.
[~BRAS1] ipv6 prefix jiaoxuelou_v6 local
[*BRAS1-ipv6-prefix-jiaoxuelou_v6] prefix 2001:DA2:207:E030::/60
[*BRAS1-ipv6-prefix-jiaoxuelou_v6] slaac-unshare-only
[*BRAS1-ipv6-prefix-jiaoxuelou_v6] commit
[~BRAS1-ipv6-prefix-jiaoxuelou_v6] quit
# Configure a local IPv6 address pool, and bind the prefix pool to this address
pool.
[~BRAS1] ipv6 pool jiaoxuelou_v6 bas delegation
[*BRAS1-ipv6-pool-jiaoxuelou_v6] prefix jiaoxuelou_v6
[*BRAS1-ipv6-pool-jiaoxuelou_v6] commit
[~BRAS1-ipv6-pool-jiaoxuelou_v6] quit
Step 5 Enable MAC address authentication in the MAC address authentication domain
named mac-domain, and bind the RADIUS server group and the authentication
template named mac-auth to this domain.
[~BRAS1] user-group mac-group
[~BRAS1] aaa
[~BRAS1-aaa] domain mac-auth
[*BRAS1-aaa-domain-mac-auth] radius-server group shenlan
[*BRAS1-aaa-domain-mac-auth] authentication-scheme mac-auth
[*BRAS1-aaa-domain-mac-auth] accounting-scheme radius
[*BRAS1-aaa-domain-mac-auth] commit
[~BRAS1-aaa-domain-mac-auth] ip-pool jiaoxuelou1
[~BRAS1-aaa-domain-mac-auth] ipv6-pool jiaoxuelou_v6
[~BRAS1-aaa-domain-mac-auth] mac-authentication enable
Step 6 Configure a web authentication domain named web-auth in which users can
access only limited resources. Bind none authentication scheme and none
accounting scheme to this domain.
[~BRAS1] user-group web-before
[~BRAS1] aaa
[~BRAS1-aaa] domain web-auth
[*BRAS1-aaa-domain-web-auth] authentication-scheme none
[*BRAS1-aaa-domain-web-auth] accounting-scheme none
[*BRAS1-aaa-domain-web-auth] commit
[~BRAS1-aaa-domain-web-auth] ip-pool jiaoxuelou_1
[~BRAS1-aaa-domain-web-auth] prefix-assign-mode unshared
[~BRAS1-aaa-domain-web-auth] ipv6-pool jiaoxuelou_v6
[~BRAS1-aaa-domain-web-auth] user-group web-before
[~BRAS1-aaa-domain-web-auth] web-server 172.31.4.216
[~BRAS1-aaa-domain-web-auth] web-server url https://172.31.4.216/index_20.html
[~BRAS1-aaa-domain-web-auth] quit
[~BRAS1-aaa] quit
# Configure the web authentication server. By default, the BRAS supports only
Portal 3.0. You can configure Portal 2.0 based on the web server protocol. You are
advised to set the IP address for communicating with the web server to the
loopback address of the active and standby BRASs.
[~BRAS1] web-auth-server enable
[~BRAS1] web-auth-server version v2
[~BRAS1] web-auth-server 172.31.4.216 key cipher ******
[~BRAS1] web-auth-server source-ip 10.10.0.1
[~BRAS1] web-auth-server source interface LoopBack1
Step 7 Configure ACLs and a traffic policy for the web authentication domain named
web-auth.
# Configure an ACL numbered 6004 to permit the traffic between the user group
(web-before) and the web authentication server and between the user group
(web-before) and the DNS server.
[~BRAS1] acl number 6004
[*BRAS1-acl-ucl-6004] rule 5 permit ip source user-group web-before destination ip-address 172.31.4.216 0
[*BRAS1-acl-ucl-6004] rule 10 permit ip source user-group web-before destination ip-address x.x.x.x 0
[*BRAS1-acl-ucl-6004] rule 15 permit ip source ip-address 172.31.4.216 0 destination user-group web-before
[*BRAS1-acl-ucl-6004] rule 20 permit ip source ip-address DNS_ip destination user-group web-before
[*BRAS1-acl-ucl-6004] commit
[~BRAS1-acl-ucl-6004] quit
# Configure an ACL numbered 6005 to allow HTTP redirection for the TCP packets
originating from the user group (web-before) and carrying the destination port
(www or 8080).
[~BRAS1] acl number 6005
[*BRAS1-acl-ucl-6005] rule 5 permit tcp source user-group web-before destination-port eq www
[*BRAS1-acl-ucl-6005] rule 10 permit tcp source user-group web-before destination-port eq 8080
[*BRAS1-acl-ucl-6005] commit
[~BRAS1-acl-ucl-6005] quit
# Configure an ACL numbered 6006 to allow HTTPS redirection for the TCP
packets originating from the user group (web-before) and carrying the
destination port (443).
[~BRAS1] acl number 6006
[*BRAS1-acl-ucl-6006] rule 5 permit tcp source user-group web-before destination-port eq 443
[*BRAS1-acl-ucl-6006] commit
[~BRAS1-acl-ucl-6006] quit
# Configure an ACL numbered 6008 to deny all traffic originating from the user
group (web-before).
[~BRAS1] acl number 6008
[*BRAS1-acl-ucl-6008] rule 5 permit ip source ip-address any destination user-group web-before
[*BRAS1-acl-ucl-6008] rule 10 permit ip source user-group web-before destination ip-address any
[*BRAS1-acl-ucl-6008] commit
[~BRAS1-acl-ucl-6008] quit
# Configure an IPv6 ACL numbered 6004 to permit the traffic between the user
group (web-before) and the web authentication server and between the user
group (web-before) and the DNS server.
[~BRAS1] acl ipv6 number 6004
[*BRAS1-acl-ucl-6004] rule 5 permit ipv6 source user-group web-before destination ipv6-address
2001:db8:1::1/128
[*BRAS1-acl-ucl-6004] rule 10 permit ipv6 source user-group web-before destination ipv6-address
2001:db8:1::2/128
[*BRAS1-acl-ucl-6004] rule 15 permit ipv6 source ipv6-address 2001:db8:1::1/128 destination user-group
web-before
[*BRAS1-acl-ucl-6004] rule 20 permit ipv6 source ipv6-address 2001:db8:1::2/128 destination user-group
web-before
[*BRAS1-acl-ucl-6004] commit
[~BRAS1-acl-ucl-6004] quit
# Configure an IPv6 ACL numbered 6005 to allow HTTP redirection for the TCP
packets originating from the user group (web-before) and carrying the
destination port (www or 8080).
[~BRAS1] acl ipv6 number 6005
[*BRAS1-acl-ucl-6005] rule 5 permit tcp source user-group web-before destination-port eq www
[*BRAS1-acl-ucl-6005] rule 10 permit tcp source user-group web-before destination-port eq 8080
[*BRAS1-acl-ucl-6005] commit
[~BRAS1-acl-ucl-6005] quit
# Configure an IPv6 ACL numbered 6006 to allow HTTPS redirection for the TCP
packets originating from the user group (web-before) and carrying the
destination port (443).
[~BRAS1] acl ipv6 number 6006
[*BRAS1-acl-ucl-6006] rule 5 permit tcp source user-group web-before destination-port eq 443
[*BRAS1-acl-ucl-6006] commit
[~BRAS1-acl-ucl-6006] quit
# Configure an IPv6 ACL numbered 6008 to deny all traffic originating from the
user group (web-before).
[~BRAS1] acl number 6008
[*BRAS1-acl-ucl-6008] rule 5 permit ipv6 source ipv6-address any destination user-group web-before
[*BRAS1-acl-ucl-6008] rule 10 permit ipv6 source user-group web-before destination ipv6-address any
[*BRAS1-acl-ucl-6008] commit
[~BRAS1-acl-ucl-6008] quit
Step 9 Configure the HTTPS noise reduction function and insert the JavaScript script
during HTTPS redirection.
[~BRAS1-access-https-redirect] js enable
Warning: To enable the function of inserting a JavaScript script during web redirection, run the web-server
mode post command in the domain view.
[*BRAS1-access-https-redirect] blacklist packet-rate 40
[*BRAS1-access-https-redirect] blacklist retry-time 10 interval 3
[*BRAS1-access-https-redirect] commit
[~BRAS1-access-https-redirect] quit
Step 11 Configure the MAC address carried in the Access-Request packet of a user as the
user name.
[~BRAS1-aaa] default-user-name template mac-name include mac-address -
[*BRAS1-aaa] default-password template pwd1 cipher ****
[*BRAS1-aaa] commit
[~BRAS1-aaa] quit
# If multiple remote backup profiles exist on the network, configure the dhcp
session-mismatch action offline command so that a DHCP request is sent to
trigger user logout when the BAS interface or VLAN changes. If only one remote
backup profile exists on the network, configure the dhcp session-mismatch
action roam ipv4 ipv6 nd command so that a DHCP request is sent to trigger
user roaming when the BAS interface or VLAN changes.
[~BRAS1-Eth-Trunk8.3111-bas] dhcp session-mismatch action offline
[*BRAS1-Eth-Trunk8.3111-bas] commit
Or
[~BRAS1-Eth-Trunk8.3111-bas] dhcp session-mismatch action roam ipv4 ipv6 nd
[*BRAS1-Eth-Trunk8.3111-bas] commit
----End
3. Run the display station all command on the WAC to check information
about online STAs.
[WAC1]display station all
Rf/WLAN: Radio ID/WLAN ID
Rx/Tx: link receive rate/link transmit rate(Mbps)
-----------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------
STA MAC AP ID Ap name Rf/WLAN Band Type Rx/Tx RSSI VLAN IPv4 address
SSID IPv6 address Online time
-----------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------
9eec-a9a2-544a 2 AirEngine5773-21_1 1/1 5G 11be 6/195 -64 3113 10.10.111.245
EDU_BRAS 2001:DA1:207:E039:CFF5:EEAD:1067:2260 000:00:01:45
-----------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------
Total: 1 2.4G: 0 5G: 1 6G: 0
5. If a user goes offline, run the display aaa offline-record command on the
BRAS to check the user's offline records or check the user's authentication
records on the AAA server.
[~BRAS1] display aaa normal-offline-record mac-address 00e0-fc12-3456
--------------------------------------------
User name : HUAWEI-02017000000000@dom1
Domain name : dom1
User MAC : 00e0-fc12-3456
Stack type flag : IPv4
User access type : IPoE
User access interface: GigabitEthernet1/0/1.1
User access PeVlan/CeVlan : -/-
User IP address : 10.10.0.254
User IPv6 address : 2001:db8::2/128
User ID :0
User authen state : Authened
User acct state : AcctReady
User author state : AuthorIdle
User login time : 2012-01-09 13:38:41
User offline time : 2012-01-09 14:15:44
User offline reason: User request to offline
--------------------------------------------
Are you sure to display some information?[Y/N]:
# Create the SSID profile named EDU_dot1x, set the SSID name to EDU_dot1x,
and enable PMK fast roaming.
[WAC1-wlan-view] ssid-profile name EDU_dot1x
[WAC1AC-wlan-ssid-prof-EDU_dot1x] ssid EDU_dot1x
[WAC1-wlan-ssid-prof-EDU_dot1x] pmk-cache-roam enhancement enable
[WAC1-wlan-ssid-prof-EDU_dot1x] quit
# Create the VAP profile named EDU_dot1x, configure the data forwarding mode
and service VLANs, and bind the security profile, SSID profile, and authentication
profile to the VAP profile.
[WAC1-wlan-view] vap-profile name EDU_dot1x
[WAC1-wlan-vap-prof-EDU_dot1x] forward-mode tunnel
[WAC1-wlan-vap-prof-EDU_dot1x] service-vlan vlan-id 3116
[WAC1-wlan-vap-prof-EDU_dot1x] security-profile EDU_dot1x
[WAC1-wlan-vap-prof-EDU_dot1x] ssid-profile EDU_dot1x
[WAC1-wlan-vap-prof-EDU_dot1x] authentication-profile p1
[WAC1-wlan-vap-prof-EDU_dot1x] quit
# Bind the VAP profile named EDU_dot1x to the AP group, and apply the profile
to radios 0 and 1 of APs in the AP group.
[WAC1-wlan-view] ap-group name ap-group1
[WAC1-wlan-ap-group-ap-group1] vap-profile EDU_dot1x wlan 1 radio 0
[WAC1-wlan-ap-group-ap-group1] vap-profile EDU_dot1x wlan 1 radio 1
[WAC1-wlan-ap-group-ap-group1] quit
----End
Data Plan
Procedure
This section uses BRAS1 as an example. The configuration on BRAS2 is similar to
that on BRAS1.
# Configure a local IPv6 prefix pool. WLAN users use IPv6 ND addresses, and the
prefix allocation mode is set to unshared.
[~BRAS1] ipv6 prefix office_v6 local
[*BRAS1-ipv6-prefix-office_v6] prefix 2001:DA2:207:E030::/60
[*BRAS1-ipv6-prefix-office_v6] slaac-unshare-only
[*BRAS1-ipv6-prefix-office_v6] commit
[~BRAS1-ipv6-prefix-office_v6] quit
# Configure a local IPv6 address pool, and bind the prefix pool to this address
pool.
[~BRAS1] ipv6 pool office_v6 bas delegation
[*BRAS1-ipv6-pool-office_v6] prefix office_v6
[*BRAS1-ipv6-pool-office_v6] commit
[~BRAS1-ipv6-pool-office_v6] quit
Step 2 Set the RADIUS server group to a third-party AAA server. The source address for
communicating with the RADIUS server and the NAS address are the loopback
address of the active and standby BRASs.
[~BRAS1] radius-server group shenlan
[*BRAS1-radius-shenlan] radius-server shared-key-cipher EDU@1234
[*BRAS1-radius-shenlan] radius-server authentication 172.31.4.216 1812
[*BRAS1-radius-shenlan] radius-server accounting 172.31.4.216 1813
[*BRAS1-radius-shenlan] radius-server source interface LoopBack1
[*BRAS1-radius-shenlan] radius-server nas-ip-address 10.10.0.1
[*BRAS1-radius-shenlan] undo radius-server user-name domain-included
[*BRAS1-radius-shenlan] commit
[~BRAS1-radius-shenlan] quit
[~BRAS1] radius-server authorization 172.31.4.216 shared-key-cipher EDU@1234
# Configure the local IP address used by the RADIUS server to create UDP sockets
with local ports 1645, 1646, and 3799.
[~BRAS1] radius local-ip 10.10.0.1
[*BRAS1] commit
# (Optional) Configure a DSCP value for RADIUS packets sent from the BRAS to
the WAC.
To prevent RADIUS packets from being discarded due to network congestion, run
the following commands to increase the DSCP value of RADIUS packets sent from
the BRAS to a RADIUS proxy.
[~BRAS1] radius-client packet dscp 48
[*BRAS1] commit
Step 6 (Optional) Configure avalanche prevention for the RADIUS proxy to adjust the
access rate of RADIUS proxy users.
NOTE
1. In RADIUS proxy scenarios, the default access rate of a high-performance MPU is 200
users per second, and that of a low-performance MPU is 150 users per second. For details
about how to improve the access performance, see the board specifications.
2. To view RADIUS proxy statistics, run the display radius-client statistics global
command. When the RADIUS proxy server continuously discards a large number of packets,
perform the following operations based on the processing capability of the BRAS: decrease
the first-packet processing rate of the RADIUS proxy server; increase the suppression and
recovery thresholds for the number of active sessions on the RADIUS proxy, the bandwidth
of whitelist CPCAR for RADIUS, and the sending rate limit for total CAR.
3. Before increasing the access performance of the RADIUS proxy access, check whether the
processing performance of the RADIUS server can meet the requirements, especially in the
scenario where one server connects to multiple BAS devices. This can prevent the server
from being suspended due to the increase of concurrent access requests.
To change the access rate of RADIUS proxy users to 500 users per second, perform
the following operations:
# Configure the suppression and recovery thresholds for the number of active
sessions on the RADIUS proxy.
[~BRAS1] aaa
[*BRAS1-aaa] access-speed adjustment system-state radius-proxy active-session threshold restrain 600
resume 550
[*BRAS1-aaa] commit
[~BRAS1-aaa] quit
[~BRAS1-Eth-Trunk8.3116-bas] quit
[~BRAS1-Eth-Trunk8.3116] quit
----End
AAA:
Server-template of second acct: -
Current authen method : RADIUS-PROXY authentication
Authen result : Success
Current author method : Idle
Author result : Success
Action flag : Idle
Authen state : Authed
Author state : Idle
Configured accounting method : RADIUS accounting
Quota-out : Offline
Current accounting method : RADIUS accounting
Realtime-accounting-switch : Open
Realtime-accounting-interval(sec) : 900
Realtime-accounting-send-update : No
Realtime-accounting-traffic-update : No
Accounting start time : 2024-10-17 20:28:56
Online time (h:min:sec) : 00:03:46
Accounting state : Accounting
Accounting session ID : BRAS052083117000005c6c4dAAAB1m
MTU : 1500
IPv6 MTU : 1500
Idle-cut direction : Both
Idle-cut-data (time,rate,idle): 0 sec, 60 kbyte/min, 0 min 0 sec
Ipv4 Realtime speed : 0 kbyte/min
Ipv4 Realtime speed inbound : 0 kbyte/min
Ipv4 Realtime speed outbound : 0 kbyte/min
Ipv6 Realtime speed : 0 kbyte/min
Ipv6 Realtime speed inbound : 0 kbyte/min
Ipv6 Realtime speed outbound : 0 kbyte/min
Dot1X:
User MSIDSN name :-
EAP user : No
MD5 end : No
VPN&Policy-route:
Vpn-Instance :-
IPv6 Vpn-Instance :-
Multicast Service:
Multicast-profile :-
Multicast-profile-ipv6 :-
Max Multicast List Number :4
IGMP enable : Yes
PIM-SM enable : No
PIM-SM-V6 enable : No
ACL&QoS:
Link bandwidth auto adapt : Disable
UpPriority : Unchangeable
DownPriority : Unchangeable
Flow Statistic:
If flow info contain l2-head : Yes
Flow-Statistic-Up : Yes
Flow-Statistic-Down : Yes
Up packets number(high,low) : (0,78)
Up bytes number(high,low) : (0,12988)
Down packets number(high,low) : (0,86)
Down bytes number(high,low) : (0,29291)
IPV6 Up packets number(high,low) : (0,0)
IPV6 Up bytes number(high,low) : (0,0)
IPV6 Down packets number(high,low) : (0,0)
IPV6 Down bytes number(high,low) : (0,0)
Dslam information :
Circuit ID :-
Remote ID :-
Actual datarate upstream :0(Kbps)
Actual datarate downstream :0(Kbps)
Min datarate upstream :0(Kbps)
Min datarate downstream :0(Kbps)
Attainable datarate upstream :0(Kbps)
Attainable datarate downstream :0(Kbps)
Max datarate upstream :0(Kbps)
Max datarate downstream :0(Kbps)
Min lowpower datarate upstream :0(Kbps)
Min lowpower datarate downstream :0(Kbps)
Max delay upstream :0(s)
Max delay downstream :0(s)
Actual delay upstream :0(s)
Actual delay downstream :0(s)
Access loop encapsulation :0x000000
-------------
------------------------------------------------
STA MAC AP ID Ap name Rf/WLAN Band Type Rx/Tx RSSI VLAN IPv4 address
SSID IPv6 address
Online time
-----------------------------------------------------------------------------------------------------------------------
-------------
------------------------------------------------
5225-7639-f88d 2 AirEngine5773-21_1 1/2 5G 11be 6/172 -65 3117 10.10.111.246
EDU_dot1x 2001:DA1:207:
E038:1501:CFFF:8431:8DE6
000:00:06:27
-----------------------------------------------------------------------------------------------------------------------
-------------
------------------------------------------------
Total: 1 2.4G: 0 5G: 1 6G: 0
5. If a user goes offline, run the display aaa offline-record command on the
BRAS to check the user's offline records or check the user's authentication
records on the AAA server.
[~BRAS1] display aaa normal-offline-record mac-address 00e0-fc12-3456
--------------------------------------------
User name : HUAWEI-02017000000000@dom1
Domain name : dom1
User MAC : 00e0-fc12-3456
Stack type flag : IPv4
User access type : IPoE
User access interface: GigabitEthernet1/0/1.1
User access PeVlan/CeVlan : -/-
User IP address : 10.10.0.254
User IPv6 address : 2001:db8::2/128
User ID :0
User authen state : Authened
User acct state : AcctReady
User author state : AuthorIdle
User login time : 2012-01-09 13:38:41
User offline time : 2012-01-09 14:15:44
User offline reason: User request to offline
--------------------------------------------
Are you sure to display some information?[Y/N]:
Procedure
Step 1 Configure a user subnet gateway on the core switch.
1. Choose Network Configuration > Site Configuration > Site Configuration
from the main menu, click the Site Configuration tab, and choose Switch >
Subnet from the navigation pane, and create a subnet.
2. Click Create to create a service gateway for users and set parameters based
on the site requirements. Select a core switch from the Device drop-down list,
set Subnet name, and set VLAN ID and IP/Mask. Enable DHCP, set DNS
service, and disable Management network. Then click OK.
Step 2 Configure the interconnection interfaces between the core, aggregation, and
access switches to allow packets from corresponding service VLANs to pass
through.
1. Choose Network Configuration > Site Configuration > Site Configuration,
click the Site Configuration tab, choose Switch > Interface from the
navigation pane, select a switch, and select a device interconnection interface.
2. Click the Eth-Trunk icon on the interface, set Link type to Trunk, add allowed
VLANs, and click Apply.
Step 3 Configure the type of user access interfaces and service VLANs on the access
switches.
Choose Network Configuration > Site Configuration > Site Configuration from
the main menu, click the Site Configuration tab, choose Switch > Interface from
the navigation pane, select an access switch, select an interface, set Link type to
Access, add the interface to a service VLAN, and click Apply.
----End
Procedure
Step 1 Create a RADIUS server template.
1. Choose Network Configuration > Global Settings > Template
Management, click the Policy Template tab, and select RADIUS Server.
2. Click Create and configure a RADIUS server template. If Type is set to Built-
in, iMaster NCE-Campus is used as the authentication server. If Type is set to
Third-party, a third-party authentication server is used.
Step 2 Configure MAC address authentication on the authentication control point, and
bind the configured RADIUS server template to it.
1. Choose Network Configuration > Site Configuration > Site Configuration
from the main menu, and click the Site Configuration tab. Choose Switch >
Authentication from the navigation pane, click the Wired Authentication
tab, and click Create.
2. Set Authentication mode to MAC address authentication, select the
RADIUS server template configured in step 1 for RADIUS server, select a
bypass policy to grant specified network access rights to users when the
device is disconnected from the authentication server, and click OK.
Step 3 Configure a default permit rule for the access device to allow access to the
domain names or IP addresses of the authentication, DHCP, and DNS servers.
1. Choose Network Configuration > Site Configuration > Site Configuration
from the main menu, and click the Site Configuration tab. Choose Switch >
Authentication from the navigation pane, click the Default Permit Rule tab,
and click Create.
2. Set Name and click ... on the right of ACL to create an ACL. In the displayed
dialog box, create ACL rules to allow access to the authentication server, DNS
server, and DHCP server by specifying the corresponding IP address segments.
Then select the authentication device where the default permit rule is to be
applied. After the configuration is completed, click OK.
Step 4 Configure the authentication server. (If iMaster NCE-Campus is used as the
authentication server, perform the following steps. If a third-party authentication
server is used, contact technical support from vendors.)
1. Choose Admission Management > Admission Resource > Admission User
Management from the main menu, click the User tab, click , and create a
user group named Printer_MAC. It is recommended that MAC accounts with
the same permissions be added to the same user group. This facilitates
subsequent authorization based on user groups.
4. Create an authorization result. Assume that the printer can access only
network segment 10.1.2.0/24 after being authenticated. The configuration is
as follows.
Choose Admission Management > Admission Policy > Authentication and
Authorization from the main menu and click the Authorization Result tab.
Click Create. On the displayed page, set Name to Printer_MAC_Result and
ACL to Printer_MAC_Author_ACL. You can configure an ACL on this page to
allow packets destined for 10.1.2.0/24 to pass through. For user authorization,
you have to configure a numbered ACL. After the configuration is completed,
click OK.
----End
9.1 Overview
Users exploit defects of the broadband accounting technology to cut down their
broadband costs. Specifically, they purchase their personal broadband services and
share the services with their roommates through unauthorized routers or
unauthorized software, and in return their roommates pay a certain fee for the
services.
The switch is embedded with intelligent identification of unauthorized access. The
lightweight deployment solution is used to identify unauthorized access during
forwarding. The network administrator enables the unauthorized access
prevention function in one-click mode. The access switch passively listens to uplink
packets in the forwarding process, constructs a flow sequence feature profile,
determines whether there is a flow sequence exception based on the terminal flow
sequence detection algorithm and whether an unauthorized access behavior
exists, and identifies the type of the unauthorized access behavior. When detecting
flow sequence hopping, the switch collects hopping information, sends the
information to iMaster NCE-Campus, and collects evidence based on the terminal
fingerprint database. iMaster NCE-Campus displays the unauthorized access
detection result and provides handling functions, such as MAC address-based
blocking.
Process description:
----End
----End
Procedure
NOTE
● Only the switches running V600 support the unauthorized access prevention function.
● The unauthorized access prevention function can be enabled on the aggregation switch.
Applicable scenarios: VXLAN deployed across core and aggregation layers and VLAN
deployed across core and aggregation layers
Applicable models: S5755-H, S5732-H-V2, S6730-H-V2, and S6750-H
● The unauthorized access prevention function can be enabled on the access switch.
Applicable scenarios: VXLAN deployed across core and access layers and VLAN deployed
across core and access layers
Applicable models: S5755-H, S5732-H-V2, S6730-H-V2, S6750-H, S5735-L-V2, S5735-S-
V2, S5735I-L-V2, S5735I-S-V2, S5535-L-V2, and S5535-S-V2
● False positives occur when the unauthorized hub access prevention function is enabled
on the switch that is not directly connected to terminals.
● After the unauthorized access prevention function is enabled, the CPU usage of the
device increases. Therefore, exercise caution when enabling this function.
Step 1 Choose Provision > Device > Device Configuration from the main menu of
iMaster NCE-Campus, select the devices to be configured in the Device List, and
click OK.
Step 2 In the Feature List on the left, choose Unauthorized access prevention >
Unauthorized access prevention and click Unauthorized access prevention
type.
Step 3 Click Create, select an unauthorized access prevention type, and click OK to create
multiple unauthorized access prevention tasks.
----End
Procedure
Step 1 Choose Provision > Device > Device Configuration from the main menu of
iMaster NCE-Campus, select the devices to be configured in the Device List, and
click OK.
Step 2 In the Feature List on the left, choose Unauthorized access prevention >
Unauthorized access prevention and click Disabled detection interface.
Step 4 Click Create, enter interface information, and click OK. You can add multiple
interfaces on which unauthorized access detection is to be disabled.
----End
NOTE
Procedure
Step 1 Query the detection result of unauthorized access prevention on the switch port. If
the query result contains data, unauthorized access exists on the port, and Ua-
type indicates the unauthorized access type.
[ACC1] display uap detection-results
------------------------------------------------------------------------------------
Interface MAC Ip-address Ua-type Detection-time
------------------------------------------------------------------------------------
100GE1/0/1 0010-9400-0005 192.168.99.138 wi-fi-sharing 2024-05-06T16:40:53+08:00
Step 2 Choose Admission > Admission Resources > Terminal Management from the
main menu of iMaster NCE-Campus and click Private Terminal. On the
Unauthorized Terminal List tab page, you can view the unauthorized access
result, including the MAC address, unauthorized access type, access device name
and port, reported device name and port, and blocking status.
----End
Procedure
Step 1 Choose Monitoring > Alarm > Current Alarms from the main menu of iMaster
NCE-Campus. The alarm named The terminal is unauthorized terminal then is
displayed.
Step 2 Click the alarm name to view alarm details, including the unauthorized access
type, terminal IP address and MAC address, and reported device name and port.
----End
NOTE
If a port is shut down, the device may be out of management, which poses high risks.
Therefore, this blocking mode is not recommended.
Procedure
Step 1 Choose Admission > Admission Resources > Terminal Management from the
main menu of iMaster NCE-Campus and click Private Terminal. On the
Unauthorized Terminal List tab page, select the unauthorized terminal and click
MAC Block Reporting Device.
Step 2 Select I understand the risks and want to continue and click OK.
----End
Procedure
Step 1 Choose Admission > Admission Resources > Terminal Management from the
main menu of iMaster NCE-Campus and click Private Terminal. On the
Unauthorized Terminal List tab page, select the unauthorized terminal and click
No blocking.
Step 2 Select I understand the risks and want to continue and click OK.
Step 3 Check the delivery of MAC address blocking canceling on the switch.
[ACC1] display current-configuration
...
#
acl number 4999
#
----End
NOTE
● To use the online GIS map, you need to pay for it and ensure that iMaster NCE-Campus
can access the Internet. If you choose to use a logical map instead of the online GIS
map, you can only view organizations, sites, and direct links between sites. Currently,
offline GIS maps are not supported.
● Only IPsec VPN tunnel interconnection links can be displayed on the online GIS map.
● Non-managed third-party devices can be added to the device topology, but monitoring
information such as the status of the third-party devices cannot be displayed.
● When installing iMaster NCE-Campus, you need to install the terminal identification
value-added feature and enable it so that terminals can be viewed on the digital map.
To view all information about terminals, you need to disable the terminal data masking
function.
● There is a delay of 10 to 20 minutes for terminals that go online without being
authenticated to be displayed in the terminal statistics and device topology on the
digital map.
● SNMP-managed devices can be displayed on the topology only and do not support
advanced functions such as application experience assurance and VIP user assurance on
the digital map.
● Only site-based domain management is supported. Sites and their devices are displayed
by site. Site-based domain management does not apply to applications, users, or
terminals.
● A single site can manage a maximum of 5000 devices. If the number of devices on a
campus exceeds 5000, they need to be managed at different sites.
Prerequisites
A GIS map has been configured. For details, see 10.1.1.1 Configuring an Online
GIS Map.
Procedure
Step 1 Create a site and configure its GIS coordinates.
● Create sites in batches and configure their GIS coordinates.
a. Log in to iMaster NCE-Campus as a tenant administrator and choose
Resource Center > Site Management from the main menu.
b. Click Batch Create, download the site configuration template, enter site
information in the template, and save the template.
The longitude and latitude are required for configuring GIS coordinates of
a site.
c. Click and select the template created in the previous step, click
Upload, and click OK.
● Create a site and configure its GIS coordinates.
Log in to iMaster NCE-Campus as a tenant administrator and choose
Resource Center > Site Management from the main menu. Then, create a
single site by referring to 7.1 Creating a Site.
To configure the GIS coordinates of the site, you need to set Site location to
the longitude and latitude of the site or click to select a location.
Step 2 Modify the GIS coordinates of an existing site. If you do not configure the GIS
coordinates of a site when creating it or wants to modify the GIS coordinates of
an existing site, perform the following steps:
2. Click next to the site name, set Site location to the longitude and latitude
of the site or click to select a location.
3. Click OK.
----End
Procedure
Step 1 In logical map mode, click in the lower right corner to set the background
image for the digital map.
Step 2 In the Set Background window that is displayed, click Select Background. In the
Select Background window, upload the image to be set.
----End
Related Operation
After setting the background image of the logical map, you can plan site locations
based on the background image.
1. (Optional) If the current map layout is locked, click in the lower right
corner to unlock the map layout.
2. Drag the site icon to the planned position on the background image and then
save the change.
Setting the
background 1. Click next to the target site or building/floor. The
image of a topology management page is displayed.
site or region 2. Click to enter the editing mode.
3. Right-click the blank area, choose Set Background
Image from the shortcut menu, and set the background
image as prompted.
4. Click on the left of the page to set the font size and
color of the node label on the topology page.
5. After the setting is complete, click to enter the
monitoring mode.
NOTE
By default, wired devices are not configured with licenses and cannot use the analysis
capability of iMaster NCE-CampusInsight. You need to set the licenses for the devices based
on your site requirements. After the licenses are successfully set, the system enables the
corresponding analysis capability for these devices and starts deducting the corresponding
resource items.
1. Choose Inventory > Device > Device from the main menu, and then click the
Wired Device tab.
2. Select one or more devices, click Set Protocol, and select Set SNMP from the
drop-down list box. In the dialog box that is displayed, modify the device
protocol parameters.
NOTE
Setting licenses for all ● Click Set License and choose All Devices.
wired devices ● In the dialog box that is displayed, set
License category and click Confirm.
Setting licenses for ● Select one or more wired devices, click Set
selected wired devices License and choose Selected Devices.
● In the dialog box that is displayed, set
License category and click Confirm.
NOTE
● On the Wired Device tab page, click Export Device and choose Export All Devices
to export all devices. To export selected devices, select one or more devices, click
Export Device and choose Export Selected Devices.
NOTE
By default, wireless devices are not configured with licenses and cannot use the analysis
capability of iMaster NCE-CampusInsight. You need to set the licenses for the devices based
on your site requirements. After the licenses are successfully set, the system enables the
corresponding analysis capability for these devices and starts deducting the corresponding
resource items.
1. Choose Inventory > Device > Device from the main menu, and then click the
Wireless Device tab.
2. Set the licenses for wireless devices based on your site requirements.
Task Operation
Setting licenses for all ● Click Set License and choose All Devices.
wireless devices ● In the dialog box that is displayed, set
License category and click Confirm.
Setting licenses for ● Select one or more wireless devices, click Set
selected wireless devices License and choose Selected Devices.
● In the dialog box that is displayed, set
License category and click Confirm.
NOTE
On the Wireless Device tab page, click Export Region Plan and choose Export All to
export positions of wireless devices mounted to all sites and buildings/floors. Select
one or more sites or buildings/floors from the list, click Export Region Plan and
choose Export Selected to export positions of wireless devices mounted to the
selected sites or buildings/floors.
Context
Switches, firewalls, AR routers, cloud APs, WACs, and Fit APs can report data to
iMaster NCE-Campus and iMaster NCE-CampusInsight. In this manner, iMaster
NCE-Campus or iMaster NCE-CampusInsight can monitor device and terminal
information in real time, learn the device states based on the reported alarms and
logs, and display the health status of devices and networks on the GUI.
You can enable the data reporting function for switches, firewalls, AR routers, and
cloud APs on iMaster NCE-Campus.
You can configure WACs and Fit APs to report data using the web system. For
WACs running V600R023C00 or later versions, this function can also be enabled
on iMaster NCE-Campus.
Procedure
Step 1 Choose Network Monitoring > Monitoring Settings > Data Collection Settings
from the main menu and click the Monitoring Settings tab.
Step 2 Enable switches to report data to iMaster NCE-Campus. Specifically, click Devices
report performance data to the iMaster NCE-Campus using HTTP, enable the
function as required, and click OK.
If Report device log data is enabled, select the types of logs to be reported to
iMaster NCE-Campus.
NOTE
● Enable Report terminal identification information. This function helps improve the
identification accuracy. If the controller identifies terminals using DHCP options or
mDNS, you need to configure DHCP snooping and mDNS snooping on devices.
● Device models that can report terminal identification information lists the device
models that can report terminal identification information.
Step 4 Enable WACs and Fit APs to report data to iMaster NCE-Campus and iMaster NCE-
CampusInsight on iMaster NCE-Campus,.
Step 5 Enable WACs and Fit APs to report data to iMaster NCE-Campus and iMaster NCE-
CampusInsight through the WAC's web system.
Item Data
AP group ap-group1
AP system default
profile
Item Data
b. Set parameters for interconnection between the WAC and iMaster NCE-
CampusInsight.
On the WAC's web system, choose Maintenance > AC Maintenance >
WMI from the main menu. On the Channel 2 tab page, set parameters
for interconnection between the WAC and iMaster NCE-CampusInsight,
and click Apply.
Generally, the port number of iMaster NCE-CampusInsight is 27371.
NOTE
Step 6 To enable firewalls to report data to iMaster NCE-Campus, click Devices report
performance data to the iMaster NCE-Campus using HTTP, enable related
functions as required, and click OK.
NOTE
Firewalls that assume the TG or Firewall role support only Report performance data,
Report terminal monitoring information, and Report application data functions.
Firewalls that assume the Gateway role support only Report performance data, Report
WAN-side application traffic data, and Report WAN-side link traffic data functions.
----End
Context
A large number of users are using various applications every moment on the
campus network. Huawei's iMaster NCE-Campus and iMaster NCE-CampusInsight
provide application experience assurance capabilities, helping network O&M
personnel monitor application analysis details in real time and detect network
problems in a timely manner.
● Key application assurance: You can configure assurance for key applications to
monitor application analysis details on a per-site basis. For example, you can
configure application assurance for a WeLink conference to ensure the
conference quality.
● Key service assurance: You can create service assurance events for
applications, that is, create assurance objects (including assured terminals and
assurance period) to monitor application analysis details by assurance object.
For example, you can create a service assurance event for the Huawei WeLink
conference application (by specifying the assured terminal and assurance
period of a WeLink conference) to monitor the quality for a terminal to access
the WeLink conference application in a conference in real time.
Prerequisites
● Interconnection has been configured between iMaster NCE-
CampusInsight and iMaster NCE-Campus and data has been synchronized
between iMaster NCE-CampusInsight and iMaster NCE-Campus.
● Application data reporting has been enabled for the site. For details, see
10.1.3 Configuring Devices to Report Data.
Procedure
Step 1 Click Application on the map navigation bar. In the Application Statistics
window, view application statistics of the current tenant.
NOTE
● Only the applications with traffic and enabled with the application analysis license on
iMaster NCE-CampusInsight are displayed.
● Application assurance depends on application identification, and application
identification requires the latest service awareness signature database. Therefore, you
need to update the service awareness signature database (independent of device
software upgrades). Otherwise, a device may fail to identify a new application, and
becomes invisible on the traffic path of the application during the analysis and
demarcation.
By default, the application statistics of the current day is displayed. You can click
Today to select a time frame as needed.
NOTE
▪ Click View Policy. You can select the topology view or list view to
view the automatically orchestrated policy information.
Click Next and add the SSID for which application assurance needs to be
enabled. Then, click Finish.
– This configuration applies to the scenario where STA service traffic is directly
forwarded and the IP address pool is not on the WAC. That is, STA service traffic
does not pass through the WAC. If STA service traffic passes through the WAC, you
need to configure iPCA 2.0 on the WAC. For details, see Application Scenarios for
iPCA 2.0.
– The SSID to be selected must be referenced by the AP group. Otherwise, the SSID
may fail to be selected.
3. Monitor the application analysis details of each site.
a. Click Application on the map navigation bar. In the Application
Statistics window, click an application name.
b. On the Involved Site tab page, view the list of sites that access the
application.
e. In the topology view on the left, click High packet loss rate to view fault
analysis details, including basic information, troubleshooting, and packet
loss rate trend.
d. In the topology view on the left, click High packet loss rate to view fault
analysis details, including basic information, troubleshooting, and packet
loss rate trend.
----End
Context
Before configuring VIP user assurance, you need to enable preferential access for
VIP users and configure bandwidth reservation, independent authorization, and AP
location.
● Preferential access must be enabled for VIP users. Otherwise, they cannot
access the SSID after the number of SSID access users exceeds the threshold.
● Bandwidth reservation must be enabled for VIP users. The reserved bandwidth
is 20% by default. When the bandwidth reserved for VIP users is insufficient,
user experience cannot be guaranteed.
● An independent authorization result must be configured for VIP users to
distinguish them from common users. Otherwise, APs cannot identify VIP
users and experience of VIP users cannot be guaranteed.
● The AP location must be configured for VIP users. Otherwise, the user journey
cannot be displayed.
NOTE
● VIP user experience assurance depends on identification of VIP users. This function is
applicable only to users authorized based on user groups (such as MAC address, 802.1X,
and PPSK authentication users), but is not applicable to users who are not authorized
based on user groups (such as open-system and PSK authentication users) because
these users cannot be identified as VIP users.
● To configure wireless VIP users, you need to configure the WAC as the authentication
point and iMaster NCE-Campus as the authentication server or authentication relay
agent, and authorize a VIP user group for wireless VIP users.
Procedure
The following configures VIP user assurance in the WAC + Fit AP scenario.
Step 1 Configure preferential access and bandwidth reservation for VIP users.
1. Configure the priority for a VIP user group. When the priority of a user group
is set to 1, this user group is a VIP user group. When the priority of a user
group is set to 0, this user group is a common user group.
NOTE
If the default radio profile is not used, bind the configured radio profile to the
corresponding AP or AP group, so that parameter settings in the profile can take
effect.
If wireless configuration synchronization in VRRP HSB scenarios has been configured
on the master and backup WACs, the above configurations of the master WAC can be
automatically synchronized to the backup WAC.
3. In the standalone WAC + Fit AP scenario, create a user group on the WAC and
enter the name of the user group in Authorized user group on the controller.
4. Click OK.
----End
Context
● Before viewing terminal statistics, you need to enable terminal identification
and disable terminal data masking. After terminal identification is enabled,
authenticated terminals are identified and displayed on the digital map. After
terminal data masking is disabled, you can view the details and user journey
of terminals.
Procedure
Step 1 Enable terminal identification.
1. Choose Admission Management > Admission Resource > Terminal
Management > Terminal Configuration from the main menu, toggle on
Terminal identification, and click OK.
1. Choose Advanced Feature > CampusInsight from the main menu. The
iMaster NCE-CampusInsight GUI is displayed.
2. Choose System > Security Management > Client Privacy Masking from the
main menu.
3. Ensure that In-depth Masking of Client Privacy is disabled.
----End
Table 10-4 Differences between the GIS map and logical map
Connecting Yes No
the client to
the Internet
Button for setting the initial view of the GIS map. The
initial view can be auto view and custom view.
If you select the auto view, the view is automatically
adjusted based on the object positions on the map. After
you select this view, the settings are automatically saved
and the map is refreshed. If you select the custom view,
you can drag and zoom on the map to adjust the view and
then click Save to save the settings and refresh the map.
Move button. You can click this button to drag the view.
– Search box
You can search for information about specific sites. You can click a site
name to locate the site on the map and view the site details.
NOTE
LLDP has been configured. For details, see 7.8 Enabling LLDP.
1. View device statistics of the current tenant.
Click Device on the map navigation bar to view statistics on all devices of the
current tenant, including the total number of devices, device status, and
number of devices in each state (normal, alarm, offline, and not registered).
The device name, model, and status are displayed in the device topology.
Mover the cursor to a device in the topology to view the device
information. You can right-click the device to perform O&M operations on
the device. Mover the cursor to a link to view the link information. For an
aggregated link, you can double-click the link to view information about
its member links. For a topology branch, you can click to expand it
and view link information.
NOTE
▪ Click in the lower right corner of the page to unlock the view.
You can drag device icons in the current topology view to modify the
c. Right-click a device and choose Create Link from the shortcut menu. You
can configure the peer device to be connected to the current device. After
the configuration is complete, the current device is added to a link. The
link created using this method must be consistent with the actual
physical link connection. Otherwise, a conflict occurs.
d. In the lower left corner of the page, click Device topology and select
Streamlight switch. The dynamic effect of the current device topology
connection is displayed.
e. In the lower left corner of the page, click Device topology and select
Spatial view to view the physical locations of devices at each layer of the
current site.
When you switch from the device topology to the spatial view, the space
view of the selected level in the resource tree is displayed. When you
switch from the spatial view to the device topology, the device topology
is displayed. For a non-device node, you can double-click the current icon
to display the next level. For a device node, you can double-click the
device to display the device details window.
f. In the upper right corner of the page, click Edit Topo. In the Edit Topo
pane that is displayed on the right, add unmanaged third-party devices
and configure links.
g. In the upper right corner of the page, click Region Management and
view and manage region information of the current site. For details, see
7.10 Configuring Region Information.
h. In the upper right corner of the page, click Network Monitoring to view
information such as the device health status and terminal packet loss
rate at the current site.
i. In the upper right corner of the page, click Configure Site to configure a
single site, or configure sites in batches by using templates to provision
services.
Currently, only the WAC can be used as the authentication point for wireless VIP user
authentication. When a third-party authentication server is used, you can view VIP users
and their flags in the user experience view of the analyzer.
Click Workbench to access the digital map homepage and view user statistics. VIP
users set in 10.1.5 Configuring User Experience Assurance are marked with VIP
flags. VIP users whose experience scores are lower than 60 are identified as
experience exceptions. User experience scoring applies only to wireless
authentication users.
Click the name of a user to go to the User Details page. You can view the basic
user information and access records of the user, including the online access
terminals authenticated using the name of this user and historical access records
of the terminals.
Click the name of a terminal to go to the Terminal Details page. You can also
access the Terminal Details page by clicking a terminal on the Terminal
Statistics page.
On the Terminal Details page, view details such as the device type, access
location, key indicators, and authentication records of the terminal. Then, click
User Journey. On the floor plan that is displayed, you can view the locations and
tracks of the APs accessed by the terminal.
On the User Journey Details page, view user access details, experience exception
analysis, and logout information.
● Click each dimension in Experience Analysis Model. The trend and issue
analysis of the selected dimension are displayed on the right.
● Click the time axis of Experience Journey in the lower part of the page to
view the user journey details at a specific time point.
User locations in the device topology view are displayed. You can move the cursor
to a device to view basic information.
The User Details page displays the basic information and network quality
information about the user.
the core switch be used as the NTP server and that network-wide devices
(including the analyzer node server) use the core switch as the NTP clock source.
For details about time synchronization of the analyzer, see 7.9.1 Configuring
Time Synchronization Between the Controller and Analyzer. For details about
time synchronization of the switch and WAC, see 7.9.3 Configuring Time
Synchronization for WACs and Fit APs.
10.2.1.2.1 Adding the Switches Running V200 and Later Versions and Enabling
Neighbor Discovery Through LLDP
Configure SNMP to add devices to CampusInsight for management. SNMP
parameter settings on CampusInsight must be consistent with those on the
devices.
<HUAWEI> system-view
[HUAWEI] snmp-agent sys-info version v3
[HUAWEI] snmp-agent mib-view included iso-view iso
//iso-view specifies the configured MIB view name. To ensure that CampusInsight can properly manage
devices, the MIB view must contain the iso node.
[HUAWEI] snmp-agent group v3 snmpv3group privacy write-view iso-view notify-view iso-view
//snmpv3group specifies the configured user group. The write view name and notification view name are
specified as iso-view. By default, the write view has the read permission. Therefore, you do not need to set
the read view. The notification view is used to specify the MIB objects for which alarms can be sent to
CampusInsight.
[HUAWEI] snmp-agent usm-user v3 snmpv3user group snmpv3group
//snmpv3user specifies the configured user name, which is consistent with the security name of
CampusInsight. The security level of a user cannot be lower than that of the user group to which the user
belongs. Otherwise, a communications failure occurs. For example, if the security level of the user group
that snmpv3group specifies is privacy, the security level of the user that snmpv3user specifies must be
authentication and encryption.
[HUAWEI] snmp-agent usm-user v3 snmpv3user authentication-mode sha
Please configure the authentication password (8-255)
Enter Password:
Confirm Password:
//Set the authentication protocol and password of the user, which are the same as that of CampusInsight.
The authentication protocol is SHA. Enter the authentication password as prompted.
[HUAWEI] snmp-agent usm-user v3 snmpv3user privacy-mode aes256
Please configure the privacy password (8-255)
Enter Password:
Confirm Password:
//Set the encryption protocol and password of the user, which are the same as the proprietary protocol and
encryption password of CampusInsight. The encryption protocol is AES256. Enter the encryption password
as prompted.
[HUAWEI] snmp-agent protocol source-interface vlanif4000
//You are advised to set the loopback interface as the SNMP source interface. vlanif4000 specifies the
device interface corresponding to the IP address used by CampusInsight for managing the device. Set the
device interface based on the site requirements.
NOTE
If a switch fails to go online due to limitations on the SNMP source interface, you can run
the snmp-agent protocol source-status all-interface command to allow all interfaces to
be used by the SNMP proxy to receive and respond to IPv4 packets from the CCU. In this
way, data can be managed in a unified manner. A risk message will be displayed when you
run this command.
10.2.1.2.2 Adding the Switches Running V600 and Later Versions and Enabling
Neighbor Discovery
<HUAWEI> system-view
[HUAWEI] snmp-agent sys-info version v3
[HUAWEI] snmp-agent mib-view included iso-view iso
//iso-view specifies the configured MIB view name. To ensure that CampusInsight can properly manage
devices, the MIB view must contain the iso node.
[HUAWEI] snmp-agent group v3 snmpv3group privacy write-view iso-view notify-view iso-view
//snmpv3group specifies the configured user group. The write view name and notification view name are
specified as iso-view. By default, the write view has the read permission. Therefore, you do not need to set
the read view. The notification view is used to specify the MIB objects for which alarms can be sent to
CampusInsight.
[HUAWEI] snmp-agent usm-user v3 snmpv3user group snmpv3group
//snmpv3user specifies the configured user name, which is consistent with the security name of
CampusInsight. The security level of a user cannot be lower than that of the user group to which the user
belongs. Otherwise, a communications failure occurs. For example, if the security level of the user group
that snmpv3group specifies is privacy, the security level of the user that snmpv3user specifies must be
authentication and encryption.
[HUAWEI] snmp-agent usm-user v3 snmpv3user authentication-mode sha
Please configure the authentication password (8-255)
Enter Password:
Confirm Password:
//Set the authentication protocol and password of the user, which are the same as that of CampusInsight.
The authentication protocol is SHA. Enter the authentication password as prompted.
[HUAWEI] snmp-agent usm-user v3 snmpv3user privacy-mode aes256
Please configure the privacy password (8-255)
Enter Password:
Confirm Password:
//Set the encryption protocol and password of the user, which are the same as the proprietary protocol and
encryption password of CampusInsight. The encryption protocol is AES256. Enter the encryption password
as prompted.
[HUAWEI] snmp-agent protocol source-status all-interface (This command needs to be configured on the
S8700 and does not need to be configured on the S6700 running V200R020C00 and later versions.)
//Allow all interfaces to receive and respond to CampusInsight request packets. By default, no interface can
receive or respond to CampusInsight request packets.
NOTE
If the device does not support the secure key exchange algorithms and you still need to use
the SFTP synchronization mode, evaluate the security risks, enable the SFTP function in
non-secure mode on CampusInsight, and perform operations according to 3 in What Do I
Do If AP Information Fails to Be Synchronized Using SFTP .
<AC> system-view
[AC] mgmt isolate disable
//The management plane isolation function is enabled by default for the AC6605, AC6805, and ACU2
running V200R010C00. When the WAC is managed through a non-management interface, run this
command to disable the management plane isolation function.
[AC] snmp-agent sys-info version v3
[AC] snmp-agent mib-view iso-view include iso
//iso-view specifies the configured MIB view name. To ensure that CampusInsight can properly manage
devices, the MIB view must contain the iso node.
[AC] snmp-agent group v3 snmpv3group privacy write-view iso-view notify-view iso-view
//snmpv3group specifies the configured user group. The write view name and notification view name are
specified as iso-view. By default, the write view has the read permission. Therefore, you do not need to set
the read view. The notification view is used to specify the MIB objects for which alarms can be sent to
CampusInsight.
[AC] snmp-agent usm-user version v3 snmpv3user group snmpv3group
//snmpv3user specifies the configured user name, which is consistent with the security name of
CampusInsight. The security level of a user cannot be lower than that of the user group to which the user
belongs. Otherwise, a communications failure occurs. For example, if the security level of the user group
that snmpv3group specifies is privacy, the security level of the user that snmpv3user specifies must be
authentication and encryption.
[AC] snmp-agent usm-user version v3 snmpv3user authentication-mode sha
Please configure the authentication password (8-255)
Enter Password:
Confirm Password:
//Set the authentication protocol and password of the user, which are the same as that of CampusInsight.
The authentication protocol is SHA. Enter the authentication password as prompted.
[AC] snmp-agent usm-user version v3 snmpv3user privacy-mode aes128
Please configure the privacy password (8-255)
Enter Password:
Confirm Password:
//Set the encryption protocol and password of the user, which are the same as the proprietary protocol and
encryption password of CampusInsight. The encryption protocol is AES128. Enter the encryption password
as prompted.
[AC] snmp-agent protocol source-interface vlanif4000
//You are advised to set the loopback interface as the SNMP source interface. vlanif4000 specifies the
device interface corresponding to the IP address used by CampusInsight for managing the device. Set the
device interface based on the site requirements.
For details, see Adding Resources under "Operation Guide > Inventory > Device"
in the iMaster NCE-CampusInsight Product Documentation (Independent
Deployment).
NOTICE
● To ensure system security and proper running of the data reporting function,
the Telemetry function uses the TLS authentication mode by default. You are
advised not to use non-TLS authentication, because it may cause system
security risks.
● The onsite network must be implemented based on the plan to ensure that all
switches on the campus network and iMaster NCE-CampusInsight can
communicate with each other. Otherwise, Telemetry packets will fail to be
reported. The Telemetry configuration on devices must be planned based on
the network requirements. The configuration here is for reference only.
● Before configuring the Telemetry function, load a license. In some versions, the
Telemetry function can be configured after the license is loaded. In some other
versions, the Telemetry function can be configured after the license is loaded
and the device is restarted. For details, see the corresponding product
documentation of the device.
Procedure
Step 1 Configure the southbound floating IP address of iMaster NCE-CampusInsight.
<HUAWEI> system-view
[HUAWEI] telemetry
[HUAWEI-telemetry] destination-group destgroup
[HUAWEI-telemetry-destination-group-destgroup] ipv4-address 172.31.31.32 port 30003 [ vpn-instance vpn-
instance-name ] protocol grpc
//Configure the southbound floating IP address of iMaster NCE-CampusInsight. 172.31.31.32 is used as an
example. Set this parameter based on site requirements. The port number is fixed at 30003. If the route to
the destination IP address destip-address is a private network route, specify vpn-instance vpn-instance-
name, where vpn-instance-name specifies the name of the VPN instance corresponding to the private
network.
[HUAWEI-telemetry-destination-group-destgroup] quit
If multiple sampling intervals are configured for the same sampling object, the network
load will increase. To prevent this, ensure that the same sensor path sensor-path
corresponding to the sampled data sent to iMaster NCE-CampusInsight is added to only
one sensor group sensor-group.
[HUAWEI-telemetry] sensor-group clientlg
//Create a sampling sensor group named devicesyslog to collect Syslog information.
[HUAWEI-telemetry-sensor-group-devicesyslog] sensor-path huawei-syslog:syslog/loginfos/loginfo
[HUAWEI-telemetry-sensor-group-devicesyslog-path] quit
[HUAWEI-telemetry-sensor-group-devicesyslog] quit
----End
The following configuration is used only as an example. The logs that can be reported vary
depending on the device.
<HUAWEI> system-view
[HUAWEI] collect dynamic mac disable
//Disable the function of reporting data of wired users who are not authenticated. If data of wired users
who are authenticated needs to be reported, you do not need to disable data reporting. Perform this
operation based on the site requirements.
[HUAWEI] pki realm default
[HUAWEI-pki-realm-default] certificate-check none
[HUAWEI-pki-realm-default] quit
//Disable certificate revocation check.
[HUAWEI] arp snooping enable
//Enable the ARP snooping function globally.
[HUAWEI] dhcp snooping enable ipv4
[HUAWEI] dhcp snooping packet-flow log enable
//Enable the DHCP snooping function globally, configure the device to process only DHCPv4 packets, and
enable the DHCP snooping print function.
[HUAWEI] interface GigabitEthernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] arp snooping enable
[HUAWEI-GigabitEthernet1/0/1] dhcp snooping enable
[HUAWEI-GigabitEthernet1/0/1] quit
//Enable the ARP snooping and DHCP snooping functions on the user-side interface.
//After ARP snooping and DHCP snooping are enabled, the switch reports ARP and DHCP packets to
iMaster NCE-CampusInsight. ARP packets are used to display the switch interface to which a user is
connected during user journey. DHCP packets are used to display the protocol interaction process in the
DHCP phase of a user during protocol tracing and display the time required for DHCP during user journey.
GigabitEthernet 0/0/1 is used only as an example. Set this parameter based on the site requirements.
[HUAWEI] interface 25GigabitEthernet 0/0/3
[HUAWEI-25GigabitEthernet0/0/3] dhcp snooping trusted
[HUAWEI-25GigabitEthernet0/0/3] quit
//After DHCP snooping is enabled, all interfaces on the switch are untrusted interfaces by default. In this
case, you need to run the dhcp snooping trusted command to configure the interface connected to the
DHCP server as a trusted interface. Otherwise, DHCP Reply packets sent from the DHCP server are
discarded and users connected to the switch cannot obtain IP addresses from the DHCP server.
25GigabitEthernet 0/0/3 is used only an example. Set this parameter based on the site requirements.
[HUAWEI] smi-server
[HUAWEI-smi-server] collect-item device-data enable
[HUAWEI-smi-server] collect-item device-data interval 1
//Configure the switch to report device, board, interface, and AP data to iMaster NCE-CampusInsight at an
interval of one minute (5 minutes by default).
[HUAWEI-smi-server] collect-item poe enable
NOTE
NOTE
● The Packet Event configuration on devices must be planned based on the network
requirements. The configuration here is for reference only.
● Only the S5700, S6700, S8700, and S16700 running V600R22C10 and later versions
support the Packet Event function. Before the configuration, ensure that the current
device model and version support the Packet Event function. For details, see the product
documentation of the corresponding device.
<HUAWEI> system-view
[HUAWEI] collector collect collect-id
//Create a flow table collector.
[HUAWEI-collect-1] source {ip | ipv6} source-ip-address export host {ip | ipv6} destip-address udp-port
30002 [ vpn-instance vpn-instance-name ]
//Set the destination address destip-address for receiving flow entries to the data collection IP address of
iMaster NCE-CampusInsight and source address source-ip-address to the IP address of the device interface.
The destination UDP port number is fixed at 30002. If the interface corresponding to source-ip-address is
bound to a VPN instance, vpn-instance vpn-instance-name must be specified, where vpn-instance-name
indicates the name of the VPN instance.
[HUAWEI-collect-1] quit
[HUAWEI] packet event monitor
[HUAWEI-packet-event-monitor] collector collect collect-id
//Associate the flow table collector with the Packet Event packet monitoring view.
[HUAWEI-packet-event-monitor] capture drop-event
[HUAWEI-packet-event-monitor-drop-event] capture drop-packet forward-exception enable
//Enable the packet loss visualization function for packets discarded due to a forwarding exception.
[HUAWEI-packet-event-monitor-drop-event] capture drop-packet forward-normal enable
//Enable the packet loss visualization function for packets discarded due to specified packet discarding rules.
[HUAWEI-packet-event-monitor-drop-event] capture drop-packet buffer-overflow enable
//Enable the packet loss visualization function for packets discarded due to buffer congestion.
[HUAWEI-packet-event-monitor-drop-event] capture drop-packet acl-deny enable
//Enable the packet loss visualization function for packets discarded due to the deny action in an ACL rule.
[HUAWEI-packet-event-monitor-drop-event] quit
[HUAWEI-packet-event-monitor] export interval 10
//Set the interval at which flow entries are reported to iMaster NCE-CampusInsight to 10s. In the actual
configuration, you need to perform the configuration based on the network maintenance experience. The
configuration here is for reference only.
[HUAWEI-packet-event-monitor] capture drop-event
[HUAWEI-packet-event-monitor-drop-event] aging-time 15
//Set the aging time of packet loss visualization flow entries to 15s. In the actual configuration, you need to
perform the configuration based on the network maintenance experience. The configuration here is for
reference only.
[HUAWEI-packet-event-monitor-drop-event] quit
[HUAWEI-packet-event-monitor] quit
[HUAWEI] quit
● The function of reporting wireless location data is available only when the license of the
value-added package for wireless location has been purchased and the basic wireless
location feature has been installed. To check whether the license of the value-added
package for wireless location has been purchased, choose System > System Settings >
License Management from the main menu and click the Resource Control Item
Consumption tab.
● To use the terminal location function to locate rogue terminals and APs, you need to
enable the WIDS function on APs.
● Wireless location data can be reported through HTTP/2 and UDP. HTTP/2 is
recommended. UDP is an insecure protocol and therefore is not recommended.
By default, HTTP/2 is enabled and UDP is disabled. To use UDP for reporting wireless
location data, log in to the management plane of iMaster NCE-CampusInsight, and
choose Product > Software Management > Deploy Product Software from the main
menu. Select Modify Configurations from the More drop-down list box. On the page
that is displayed, set RTLS_UDP_Enable to true.
● Only APs and WACs running V200R020C10 or later can report terminal location data
through HTTP/2.
<WAC> system-view
[WAC] wlan
[WAC-wlan-view] air-scan-profile name default
//Create the air scan profile default. By default, the profile already exists in the system.
[WAC-wlan-air-scan-prof-default] scan-period 100
//Set the air scan period. The recommended value is 100 ms.
[WAC-wlan-air-scan-prof-default] scan-interval 2000
//Set the air scan interval. The recommended value is 2000 ms.
[WAC-wlan-air-scan-prof-default] quit
[WAC-wlan-view] radio-2g-profile name wlan-radio-2g
[WAC-wlan-radio-2g-prof-wlan-radio-2g] air-scan-profile default
[WAC-wlan-radio-2g-prof-wlan-radio-2g] quit
[WAC-wlan-view] radio-5g-profile name wlan-radio-5g
[WAC-wlan-radio-5g-prof-wlan-radio-5g] air-scan-profile default
[WAC-wlan-radio-5g-prof-wlan-radio-5g] quit
//Create a radio profile and bind the air scan profile to the radio profile.
[WAC-wlan-view] ap-group name default
[WAC-wlan-ap-group-default] radio-2g-profile wlan-radio-2g radio 0
Warning: This action may cause service interruption. Continue?[Y/N]y
[WAC-wlan-ap-group-default] radio-5g-profile wlan-radio-5g radio 1
Warning: This action may cause service interruption. Continue?[Y/N]y
[WAC-wlan-ap-group-default] quit
//Bind the radio profile to an AP group.
[WAC-wlan-view] location-profile name default
//Create the location profile default.
[WAC-wlan-location-prof-default] collect-location-data enable
//Enable the terminal location data reporting function on the APs.
[WAC-wlan-location-prof-default] quit
[WAC-wlan-view] ap-group name default
[WAC-wlan-ap-group-default] location-profile default radio all
//Bind the location profile default to the AP group.
[WAC-wlan-ap-group-default] quit
[WAC-wlan-view] wmi-server name test
//Create the WMI profile test.
[WAC-wlan-wmi-server-prof-test] server ip-address 172.31.31.32 port 27371
//In the profile test, configure the destination address and port number for the APs to report terminal
location data. 172.31.31.32 is the southbound floating IP address of iMaster NCE-CampusInsight. The port
number is fixed at 27371.
[WAC-wlan-wmi-server-prof-test] server backup ip-address 172.31.31.34 port 27371
//(Perform this step only in DR scenarios.) 172.31.31.34 is the southbound floating IP address of the
secondary iMaster NCE-CampusInsight node. The port number is fixed at 27371.
[WAC-wlan-wmi-server-prof-test] collect-item location-data interval 3
//Set the interval at which the APs report terminal location data to 3s.
[WAC-wlan-view] ap-system-profile name default
NOTE
Only APs and WACs running V200R020C10 or later can report DNS data through HTTP/2.
[WAC] interface vlanif 100
[WAC-Vlanif100] dhcp server dns-list 10.6.4.66
//Set the IP address of the DNS server to 10.6.4.66 for the interface address pool on VLANIF 100. 10.6.4.66
is used only as an example. Change it to the actual IP address of the DNS server.
[WAC-Vlanif100] wlan
[WAC-wlan-view] wmi-server name test
//Create the WMI profile test.
[WAC-wlan-wmi-server-prof-test] collect-item dns-data enable
[WAC-wlan-wmi-server-prof-test] collect-item dns-data interval 60
//In the profile test, set the interval for collecting DNS performance metrics to 60 seconds.
[WAC-wlan-wmi-server-prof-test] wlan
[WAC-wlan-view] vap-profile name wlan-vap
[WAC-wlan-vap-prof-wlan-vap] dns-snooping enable
//Enable DNS snooping in the VAP profile. By default, DNS snooping is disabled.
[WAC-wlan-vap-prof-wlan-vap] quit
[WAC-wlan-view] ap-system-profile name default
//Configure the AP system profile default. By default, the profile is bound to the AP group.
[WAC-wlan-ap-system-prof-default] wmi-server test index 2
//Bind the WMI profile test to the AP system profile default. In this case, the index must be set to index 2.
Configuring AI Roaming
NOTE
The AirEngine 6760-X1, AirEngine 6760-X1E, and AirEngine 5760-51 can switch to the dual-
radio + independent scanning mode only after an RTU license is loaded.
<WAC> system-view
[WAC] wlan
[WAC-wlan-view] ap-system-profile name default
//Create an AP system profile and enter its view.
[WAC-wlan-ap-system-prof-default] radio-mode 2radio-independent-scan
[WAC-wlan-ap-system-prof-default] quit
//Enable the dual-radio + independent radio scanning mode. Switching the radio mode will cause an AP to
restart.
[WAC-wlan-view] sta-profiling enable
//Enable the terminal profiling function.
[WAC-wlan-view] rrm-profile name wlan-rrm01
//Create an RRM profile and enter its view.
[WAC-wlan-rrm-prof-wlan-rrm01] smart-roam ai-mode
[WAC-wlan-rrm-prof-wlan-rrm01] quit
//Enable AI-powered proactive roaming.
[WAC-wlan-view] radio-5g-profile name radi01
//Create a 5G radio profile and enter its view.
[WAC-wlan-radio-5g-prof-radio01] rrm-profile wlan-rrm01
[WAC-wlan-radio-5g-prof-radio01] quit
[WAC-wlan-view] quit
//Bind the RRM profile to the 5G radio profile.
APs running V200R023C00SPC100 and later versions can report spectrum analysis data.
<WAC> system-view
[WAC] wlan
[WAC-wlan-view] ap-id 1
[WAC-wlan-ap-1] radio 0
[WAC-wlan-radio-1/0] spectrum-analysis enable
[WAC-wlan-radio-1/0] quit
[WAC-wlan-ap-1] radio 1
[WAC-wlan-radio-1/1] spectrum-analysis enable
//Enable spectrum analysis on radios 0 and 1 of AP 1.
<WAC> system-view
[WAC] wlan
//Configure parameters for APs to communicate with iMaster NCE-CampusInsight. 172.31.31.32 is the
southbound floating IP address of iMaster NCE-CampusInsight. The port number is fixed at 27371.
[WAC-wlan-view] wmi-server name test
[WAC-wlan-wmi-server-prof-test] server ip-address 172.31.31.32 port 27371
//Enable the function of reporting spectrum analysis data.
[WAC-wlan-wmi-server-prof-test] collect-item spectrum-data enable
[WAC-wlan-wmi-server-prof-test] quit
//Bind the WMI profile to the AP group default through an AP system profile.
[WAC-wlan-view] ap-system-profile name default
[WAC-wlan-ap-system-prof-default] wmi-server test index 2
[WAC-wlan-ap-system-prof-default] quit
[WAC-wlan-view] ap-group name default
[WAC-wlan-ap-group-dafault] ap-system-profile default
NOTE
On wired networks, only the S8700-6 equipped with SRUEX1 series and the S8700-10
equipped with SURFX1 series support application-based IFIT measurement.
Before configuring application-based packet loss and delay measurement result reporting,
ensure that application-based traffic statistics reporting has been configured.
For details, see 10.2.10 Configuring Packet Loss and Delay Measurement Result
Reporting.
NOTE
● You can configure a WAC to collect traffic statistics on a specified application and report
the statistics to iMaster NCE-CampusInsight for visualized display (only in tunnel
forwarding scenarios).
● After application-based traffic statistics reporting is enabled on a WAC, the forwarding
performance of the WAC will deteriorate by about 20%. Therefore, you are advised to
enable application-based traffic statistics reporting on APs.
● The number of applications that can be identified using the application signature
database for APs is fewer than that for WACs. For details, see Service Awareness.
<WAC> system-view
[WAC] defence engine enable
//Enable the security engine on the WAC.
[WAC] defence engine enable ap-group name name
//Enable the security engine for APs in the AP group name.
[WAC] wlan
[WAC-wlan-view] sac-profile name wlan-sac
[WAC-wlan-sac-prof-wlan-sac] vap-protocol-statistic enable
[WAC-wlan-sac-prof-wlan-sac] user-protocol-statistic enable
[WAC-wlan-sac-prof-wlan-sac] quit
//Create the SAC profile wlan-sac and enable the SAC statistics collection function (collecting VAP protocol
statistics and user protocol statistics).
[WAC-wlan-view] vap-profile name wlan-vap
[WAC-wlan-vap-prof-wlan-vap] sac-profile wlan-sac
[WAC-wlan-vap-prof-wlan-vap] quit
//Bind the SAC profile wlan-sac to the VAP profile wlan-vap to make the configured policy take effect.
[WAC-wlan-view] wmi-server name test
[WAC-wlan-wmi-server-prof-test] undo collect-item application-statistics-data
[WAC-wlan-wmi-server-prof-test] collect-item application-statistics-data interval 300
[WAC-wlan-wmi-server-prof-test] quit
NOTE
Before configuring the function of reporting poor-QoE monitoring results, ensure that SAC
has been configured.
The SAC configuration roadmap is as follows:
1. Enable the security engine.
2. Create an SAC profile and bind it to a VAP profile.
For details, see Configuring Application-based Traffic Statistics Reporting.
<WAC> system-view
[WAC] defence engine enable ap-group name name
//Enable the security engine for APs in the AP group name.
[WAC] wlan
[WAC-wlan-view] vap-profile name wlan-vap
[WAC-wlan-vap-prof-wlan-vap] service-experience-analysis monitor application espace_voip
......
[WAC-wlan-vap-prof-wlan-vap] quit
//Configure an application to be monitored based on service experience analysis (SEA), for example,
espace_voip (eSpace).
//Enable APs to report application-based poor-QoE monitoring results at an interval of 60 seconds.
[WAC-wlan-view] ap-system-profile name default
//Configure the AP system profile default. By default, the profile is bound to the AP group.
[WAC-wlan-ap-system-prof-default] wmi-server test index 2
//Bind the WMI profile test to the AP system profile default.
Before configuring application-based packet loss and delay measurement result reporting,
ensure that application-based traffic statistics reporting has been configured.
Measurement points are classified into in-point, mid-point, and out-point based
on the packet forwarding direction. Different interfaces on a device can function
as different measurement points.
● In-point: indicates the ingress measurement point of a measurement flow. An
in-point (marked as ) colors a measurement flow.
NOTICE
[WAC] wmi-server
[WAC-wmi-server] undo collect-item s-ipfpm-data
[WAC-wmi-server] quit
//Enable the WAC to periodically report measurement results to iMaster NCE-CampusInsight.
[WAC] wlan
[WAC-wlan-view] wmi-server name test
[WAC-wlan-wmi-server-prof-test] undo collect-item s-ipfpm-data disable
[WAC-wlan-wmi-server-prof-test] quit
//Enable the AP to periodically report measurement results to iMaster NCE-CampusInsight.
[WAC-wlan-view] ap-system-profile name default
//Configure the AP system profile default. By default, the profile is bound to the AP group.
[WAC-wlan-ap-system-prof-default] wmi-server test index 2
//Bind the WMI profile test to the AP system profile default.
NOTE
This configuration applies to the scenario where STA service traffic is directly forwarded and
the IP address pool is not on the WAC. That is, STA service traffic does not pass through the
WAC. If STA service traffic passes through the WAC, you need to configure iPCA 2.0 on the
WAC. For details, see Application Scenarios for iPCA 2.0 and Configuring Application-
based iPCA 2.0 to Implement Network Packet Loss and Delay Measurement.
on which packet loss and delay measurement results are reported, for example, welink_meeting.
[HUAWEI] interface 25GE0/0/3
[HUAWEI-25GE0/0/3] s-ipfpm measure flow 1000 in-point egress bidirectional
[HUAWEI-25GE0/0/3] quit
//Bind the measurement flow to the interface specified as an in-point and enable the measurement
function on the interface.
[HUAWEI] smi-server
[HUAWEI-smi-server] collect-item sipfpm-data enable
[HUAWEI-smi-server] quit
//Enable the access switch to periodically report measurement results to iMaster NCE-CampusInsight.
NOTE
Access switches running V600 do not support application identification. Therefore, wired
access switches running V200 and later versions as described in Licensing Requirements
and Limitations for SAC must be used. On wired networks, only the S8700-6 equipped
with SRUEX1 series and the S8700-10 equipped with SRUFX1 series support application-
based IFIT measurement. Application identification can be enabled on the S8700-6
functioning as the core or aggregation switch through reverse flow creation and the
S8700-6 is configured as an in-point. Bidirectional flow measurement can be enabled on
the access switch running V600 functioning as the out-point. For details, see Configuring
Application-based Packet Loss and Delay Measurement Result Reporting.
4. Configure aggregation switches AGG01 and AGG02 running V200 and later
versions.
<HUAWEI> system-view
[HUAWEI] assign resource-mode enhanced-sipfpm
[HUAWEI] quit
[HUAWEI] save
[HUAWEI] reboot
//Change the resource allocation mode of the switch to enhanced-sipfpm. After the resource
allocation mode is changed, you need to save the configuration and restart the switch for the
configuration to take effect.
<HUAWEI> system-view
[HUAWEI] s-ipfpm measure interval 60
//On aggregation switches, set the packet loss and delay measurement interval to 60 seconds.
[HUAWEI] s-ipfpm report-loss-reason enable
//Enable the function of reporting the packet loss cause.
//Only the S5731-H, S5731-H-K, S5731-S, S5731S-H, S5731S-S, S5732-H, S5732-H-K, S6730-H, S6730-
H-K, S6730S-H, S6730-S, and S6730S-S support this command.
[HUAWEI] interface Xgigabitethernet 3/0/4
[HUAWEI-Xgigabitethernet 3/0/4] s-ipfpm measure auto-detect mid-point ingress bidirectional
[HUAWEI-Xgigabitethernet 3/0/4] quit
//Configure this command on all interfaces connected to access switches, such as XGE3/0/4,
XGE4/0/4, and XGE4/0/7. XGE3/0/4 is used as an example.
[HUAWEI] interface Xgigabitethernet 3/0/5
[HUAWEI-XGigabitEthernet3/0/5] s-ipfpm measure auto-detect mid-point egress bidirectional
//Enable the measurement function on interfaces. After this function is enabled, the interfaces can
automatically detect the measurement flow bound to the in-point without the need of binding the
measurement flow to the interfaces. You need to configure this function on all interfaces connected
to core switches, such as XGE3/0/5, XGE3/0/6, XGE4/0/5, and XGE4/0/6. XGE3/0/5 is used as an
example.
[HUAWEI-XGigabitEthernet3/0/5] quit
[HUAWEI] smi-server
[HUAWEI-smi-server] collect-item sipfpm-data enable
[HUAWEI-smi-server] quit
//Enable aggregation switches to periodically report measurement results to iMaster NCE-
CampusInsight.
5. Configure aggregation switches AGG01 and AGG02 running V600 and later
versions.
<HUAWEI> system-view
[HUAWEI] system resource large-flow
[HUAWEI] quit
[HUAWEI] save
[HUAWEI] reboot
//Change the resource allocation mode of the switch to large-flow. After the resource allocation
mode is changed, you need to save the configuration and restart the switch for the configuration to
take effect.
<HUAWEI> system-view
[HUAWEI] ifit
[HUAWEI-ifit] flow-learning native-ip
[HUAWEI-ifit-native-ip] report-loss-reason enable
//Enable the function of reporting the packet loss cause on aggregation switches.
[HUAWEI-ifit-native-ip] flow-learning interface Xgigabitethernet 3/0/4 transit-input bidirectional
//Configure this command on all interfaces connected to access switches, such as XGE3/0/4,
XGE4/0/4, and XGE4/0/7. XGE3/0/4 is used as an example.
[HUAWEI-ifit-native-ip] flow-learning interface Xgigabitethernet 3/0/5 transit-output bidirectional
//Bind native IP flow learning to a specified interface on an aggregation switch. Enable the
measurement function on interfaces. After this function is enabled, the interfaces can automatically
detect the measurement flow bound to the in-point without the need of binding the measurement
flow to the interfaces. You need to configure this function on all interfaces connected to core
switches, such as XGE3/0/5, XGE3/0/6, XGE4/0/5, and XGE4/0/6. XGE3/0/5 is used as an example.
[HUAWEI-ifit-native-ip] quit
[HUAWEI-ifit] quit
[HUAWEI] telemetry
[HUAWEI-telemetry] sensor-group test
[HUAWEI-telemetry-sensor-test] sensor-path huawei-ifit:ifit/huawei-ifit-statistics:flow-native-ip-
statistics/flow-native-ip-statistic
//Configure aggregation switches to report statistics to iMaster NCE-CampusInsight through Telemetry.
[HUAWEI-telemetry-sensor-group-test] quit
[HUAWEI-telemetry] destination-group test
[HUAWEI-telemetry-destination-group-test] ipv4-address 172.31.31.32 port 10001 protocol grpc
[HUAWEI-telemetry-destination-group-test] quit
[HUAWEI-telemetry] subscription test
[HUAWEI-telemetry-subscription-test] sensor-group test
[HUAWEI-telemetry-subscription-test] destination-group test
//Change the resource allocation mode of the switch to large-flow. After the resource allocation
mode is changed, you need to save the configuration and restart the switch for the configuration to
take effect.
<HUAWEI> system-view
[HUAWEI] ifit
[HUAWEI-ifit] flow-learning native-ip
[HUAWEI-ifit-native-ip] report-loss-reason enable
//Enable the function of reporting the packet loss cause on core switches.
[HUAWEI-ifit-native-ip] flow-learning interface Xgigabitethernet 5/0/5 transit-input bidirectional
//Bind native IP flow learning to a specified interface on a core switch. Configure this function on all
interfaces connected to aggregation switches, such as XGE5/0/5, XGE5/0/6, XGE6/0/5, and XGE6/0/6.
XGE5/0/5 is used as an example.
[HUAWEI-ifit-native-ip] flow-learning interface Xgigabitethernet 5/0/8 egress bidirectional
//Enable the measurement function on interfaces. After this function is enabled, the interfaces can
automatically detect the measurement flow bound to the in-point without the need of binding the
measurement flow to the interfaces. You need to configure this function on all uplink interfaces, such
as XGE5/0/8, XGE5/0/9, XGE6/0/8, and XGE6/0/9. XGE5/0/8 is used as an example.
[HUAWEI-ifit-native-ip] quit
[HUAWEI-ifit] quit
[HUAWEI] telemetry
[HUAWEI-telemetry] sensor-group test
[HUAWEI-telemetry-sensor-group-test] sensor-path huawei-ifit:ifit/huawei-ifit-statistics:flow-native-ip-
statistics/flow-native-ip-statistic
//Configure core switches to report statistics to iMaster NCE-CampusInsight through Telemetry.
[HUAWEI-telemetry-sensor-group-test] quit
[HUAWEI-telemetry] destination-group test
[HUAWEI-telemetry-destination-group-test] ipv4-address 172.31.31.32 port 10001 protocol grpc
[HUAWEI-telemetry-destination-group-test] quit
[HUAWEI-telemetry] subscription test
[HUAWEI-telemetry-subscription-test] sensor-group test
[HUAWEI-telemetry-subscription-test] destination-group test
click in the upper right corner of the page to enable the smart
assistant.
– Metric display area: Displays the global data of selected metrics within
the specified time range.
– Topology view switching: You can select site and link metrics to be
displayed and switch to the user experience view or application
experience view as required.
– Timeline: You can select Real Time or History from the drop-down list
box.
▪ History: You can click to select a time range and drag the
pointer on the timeline to adjust the time range to view the
corresponding metric data.
3. In the To Be Handled area on the right, click the desired network
optimization item to view network events. Click an event to view the root
cause analysis and service impact analysis.
Click a network event to view its details, including statistics, cause analysis,
and troubleshooting suggestions. Click an affected device to view the AP
details of the device. Click of a site to view the detailed location of the
faulty device or link in the topology.
4. Click the Network Health View icon to check site metrics, link metrics, and
view types in the pop-up window. The selected metrics are displayed in the
topology display area. A maximum of three site metrics and three link metrics
can be selected at the same time.
– Site Metrics: After site metrics are selected, the metric values of all sites
within the selected time range are displayed. You can click the metric
value to view details.
– Link Metrics: After link metrics are selected, you can move the pointer to
a link to view basic link information and information about selected link
metrics within the selected time range.
– View Type: You can switch to the user experience view or application
experience view as required.
5. After the required metrics are selected, pop-ups are displayed for sites that
have data. Click a pop-up to view the metric details of the corresponding site.
6. On the Metric Details page, select the time range in the upper part for
metric statistics. Click different tabs to view details about different metrics,
including statistics and trend charts.
7. In the topology display area, double-click a site to enter the device topology
view.
– Click Device Topo, select metrics to be displayed, and view network
health details in the metric display area based on the current dimension.
You can click the pop-up above a device to view the metric details.
– Click Device Topo and select Space View under View Type to view
network health details based on the space dimension. You can click the
pop-up above a region to view the metric details. In addition, you can
double-click a region to drill down to view network health details by the
minimum granularity of floors.
Parameter Description
Refreshes the topology. After you click this icon, the topology layout
will be restored to the layout saved last time.
– User topology: Displays the number of abnormal VIP users and total
number of users at each site. You can view the distribution of users at
each site and adjust the layout.
– Smart assistant: Provides an overview of the user experience view,
including information about common users and VIP users, to-dos, and
event broadcast. You can click in the upper right corner of the page
to enable the smart assistant.
3. Click Users in the upper part on the homepage to view statistics about all end
users in a list. The latest experience score is displayed for users with Access
Type set to Wireless.
4. Click VIP Setting. The VIP user list is displayed. You can add or delete VIP
users as required.
– Adding a VIP user: Click Add. In the dialog box that is displayed, enter the
desired user name, click , select the user, and click OK. Then the user
is set as a VIP user.
– Deleting a VIP user: Search for a VIP user by user name or MAC address,
select the user, and click Delete. Then the user is set as a common user.
5. Click a user name to go to the details page and view the user experience
details.
– Timeline
The Experience Journey area in the lower part of the page displays the
access time ranges in the current time window. You can click the timeline
to view details about APs to which end users connect in a specified time
range.
– The User Details page displays detailed information about the user,
experience exception analysis, access applications, and network quality.
– Wired user
User locations in the device topology view are displayed. You can move
the cursor to a device to view basic information.
The User Details page displays the basic information and network
quality information about the user.
6. Double-click the user icon on the homepage of the user experience view and
drill down to check user data by selected site, region, building, and floor
based on the completed network plan.
You can click in the upper right corner of the page to enable the
smart assistant.
3. Click Applications in the upper part of the map on the homepage to view
statistics about all applications. The application list displays the application
name, traffic, and total number of abnormal/service flows.
4. Click an application to view its details. The Application Details page displays
detailed information about the application and the list of sites that access the
application.
5. Click a site name to view the application details of the site, including basic
application information, fault demarcation information, and flow list.
The fault demarcation information includes the packet loss rate and delay of
traffic.
The flow list displays information about users who use the application. You
can click a user name to go to the user details page. In addition, you can click
the start or end time of a user to view the traffic data of the user at each
time point in the topology on the left. You can also click the source or
destination to view the location of the user in the device view of the topology.
If the application status is abnormal, the abnormal flow is marked in red in
the topology. You can click an abnormal metric in red to view the fault
analysis result on iMaster NCE-CampusInsight. The page on the right displays
basic information and troubleshooting information about the abnormal flow.
NOTE
This function can be applied to the following issues: optical module exception, queue
congestion, port congestion, abnormal increase of forwarding CPU usage, abnormal
increase of AC CPU usage, abnormal increase of AC memory usage, and block memory
threshold exceeded on the forwarding plane.
11 O&M
● Record all the operations you have performed, especially the key operations
such as restarting devices and clearing databases. Before performing the key
operations, confirm the operation feasibility, back up data, and prepare the
emergency and security measures. Only qualified personnel can perform key
operations.
● Take ESD protection measures, for example, wear an ESD wrist strap when
replacing or maintaining device components.
● After the system recovers, observe system running to ensure that the fault is
rectified. Then, complete the associated troubleshooting report in a timely
manner.
A fault can be detected on the user side (for example, a user cannot access the
Internet) or on the network side (for example, an alarm is generated on a device).
After a fault is detected, you need to collect the fault information about each
device immediately, analyze the fault information, and then locate and rectify the
fault. For solution-level troubleshooting on the entire network, the key is to
quickly narrow down the fault scope to a specific component based on the fault
symptom and then rectify the fault.