Login
- Released At: 16-12-2024
- Page Views:
- Downloads:
- Table of Contents
- Related Documents
-
|
|
|
AD-WAN 6.5 Branch Solution |
|
SeerAnalyzer Service Configuration Guide |
|
|
|
|
Document version: 5W103-20240909
Copyright © 2024 New H3C Technologies Co., Ltd. All rights reserved.
No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd.
Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are the property of their respective owners.
This document provides generic technical information, some of which might not be applicable to your products.
The information in this document is subject to change without notice.
Contents
Add network assets and generate topology
View the southbound collection IP address
Configure global NetStream settings
View NetStream flow analysis results
Configure analysis task settings
Configure analysis task settings
Set alarm thresholds and enable AI prediction
Configure analysis task settings
Configure analysis task settings
Configure analysis task settings
Configure the report template list
Configure the periodic report list
View the configuration results
Configure analysis task settings
Configure application group settings
Configure UserLog analysis tasks
Configure analysis task settings
Audio and video quality analysis
Parent-child QoS policy queue statistics
Configuring collection settings
Overview
Product overview
H3C SeerAnalyzer (the analyzer for short) focuses on digging the values in machine data. Based on the big data technology, SeerAnalyzer analyzes valuable information in massive data and provides reference for enterprise network&service operations and business decision making in enterprises through various methods such as machine learning and deep learning. SeerAnalyzer collects real-time data about and provides insights into the device performance, user online status, and service traffic, and visualizes the network operating status and proactively perceives risks and automatically alarms through the big data analytics technique and AI algorithms.
The analyzer in WAN scenario acts as the core engine for the WAN AIOps. Through collecting multi-dimensional network information such as the state data, log data, and traffic data and cooperating with the big data and AI technologies, the analyzer provides capabilities including network-wide health assessment, application flow analysis, capacity prediction, and intelligent troubleshooting. The WAN analyzer mainly provides four functions: health analytics, diagnostic analytics, prediction analytics, and reports.
|
|
NOTE: In cloud scenario, only NetStream flow analysis is supported. |
Terms
Table 1 Terms
|
Description |
|
|
SNMP |
Simple Network Management Protocol |
|
NETCONF |
Network Configuration Protocol |
|
NetStream |
A flow-based statistics method |
|
UserLog |
Log of users accessing external network flows |
|
URL |
Uniform Resource Locator |
|
RIR |
Resilient Intelligent Routing |
|
gRPC |
Google Remote Procedure Call |
|
TWAMP |
Two-Way Active Measurement Protocol |
|
QoS |
Quality of Service |
Networking
|
|
CAUTION: · The networking solution in this document uses the southbound single stack, and the collection network uses the IPv4 protocol. · In southbound single stack and dual stack deployment scenarios for the collection component, you must deploy a collection gateway and make sure the gateway network can communicate with the collection pod southbound networks (both IPv4 and IPv6 networks in dual stack scenario) to ensure successful data collection. |
· Northbound network: Northbound service virtual IP set in the Unified Platform. The IP address is used by the cluster to provide external services.
· Southbound network: Network used by the collection component or an independent collector to collect data from devices. Make sure the southbound network and the devices to be collected can reach each other. Currently, the southbound network supports the following networking solutions. Select one as needed.
¡ Unified southbound and northbound network—The analyzer and the data collection share the network of Unified Platform, and no additional network is created.
¡ Southbound single stack—In this networking solution, the data collection uses a separate network, which can use the IPv4 or IPv6 network.
¡ Southbound dual stack—In this networking solution, the data collection uses a separate network, which must be configured with both IPv4 and IPv6 addresses.
Network diagram
In the WAN branch solution, the network is typically vertical, as described follows:
· A vertical industry network contains multiple layers, two layers or three layers typically. The three layers include the core provincial network, city network, and county network, as shown in the figure above.
· In a vertical industry network, a typical traffic model is communication between vertical networks.
· You can use a square-shaped network or dual IRF links to implement load sharing and backup.
Table 2 shows the addresses planned for interfaces on devices.
Table 2 Device node address planning
|
Device |
Interface |
Interface address |
Peer device |
Peer interface |
Peer address |
Remarks |
|
Server |
\ |
192.168.40.155 |
\ |
\ |
\ |
Northbound service VIP |
|
Server |
\ |
3.2.139.233 |
\ |
\ |
\ |
Southbound passive collection IP |
|
Server |
\ |
3.2.139.237 |
\ |
\ |
\ |
Southbound active collection IP |
|
\ |
3.2.139.238 |
\ |
\ |
\ |
||
|
\ |
3.2.139.239 |
\ |
\ |
\ |
||
|
\ |
3.2.139.240 |
\ |
\ |
\ |
||
|
Switch |
Vlan1 |
3.2.139.1 |
\ |
\ |
\ |
Southbound gateway network |
|
Hub1 |
GE2/0 |
20.3.1.1 |
Agg1 |
GE2/0 |
20.3.1.2 |
|
|
GE3/0 |
20.1.2.1 |
Internet |
GE3/0 |
20.1.2.2 |
|
|
|
Hub2 |
GE2/0 |
120.1.3.1 |
Internet |
GE5/0 |
120.1.3.2 |
|
|
GE3/0 |
20.2.2.1 |
Agg1 |
GE5/0 |
20.2.2.2 |
|
|
|
Agg1 |
GE2/0 |
20.3.1.2 |
Hub1 |
GE2/0 |
20.3.1.1 |
|
|
GE3/0 |
20.3.2.1 |
Spoke1 |
GE3/0 |
20.3.2.2 |
|
|
|
GE4/0 |
120.1.4.2 |
Internet |
GE4/0 |
120.1.4.1 |
|
|
|
GE5/0 |
20.2.2.2 |
Hub2 |
GE3/0 |
20.2.2.1 |
|
|
|
Spoke1 |
GE2/0 |
PPPoE dialup |
Internet |
GE2/0 |
PPPoE dialup |
|
|
GE3/0 |
20.3.2.2 |
Agg1 |
GE3/0 |
20.3.2.1 |
|
Add network assets and generate topology
Perform this task to add network assets to SeerAnalyzer and generate topology accordingly. You must complete these configurations before you can use SeerAnalyzer.
Configuration workflow
Figure 1 Configuration workflow
|
|
NOTE: · Before you perform this task, make sure the device management IP (typically a loopback address) can communicate with the analyzer’s southbound active collection IP and southbound passive collection IP. · LLDP information can be collected through gRPC or NETCONF. Node and interface information of devices on the topology can be collected through SNMP, NETCONF, or gRPC. You must select one collection method. · In an analyzer collection template, you can configure different collection methods. For example, use SNMP to collect device interface information and use NETCONF or gRPC to collect LLDP information; use NETCONF or gRPC to collect all information. · As a best practice, use gRPC for data collection when there are a large number of devices. |
Network planning
See “Network diagram.”
Restrictions and guidelines
· The configuration deployed by the controller includes configuration of basic functions (for example, EVPN) and it is the prerequisites for testing the analyzer function later. For more information, see the controller deployment guide.
· For the analyzer to read information about a device successfully, make sure the configuration in the SNMP protocol template is the same as that on the device.
· For the analyzer to correctly establish a NETCONF connection to a device and ensure collection tasks, make sure the configured username and password are the same as those on the device.
Procedure
View the southbound collection IP address
|
|
WARNING! · In southbound single stack or southbound dual stack deployment mode, the southbound passive collection cluster IP and the container IP for each node of southbound active collection must be able to communicate with the devices. If such IP addresses are filtered, some collected data will fail to be sent to the analyzer, and the functionality will be affected. · In unified southbound & northbound deployment mode, the northbound service VIP and the node IP for the collection component must be able to communicate with the devices. If such IP addresses are filtered, some collected data will fail to be sent to the analyzer, and the functionality will be affected. · In southbound single stack deployment mode, the southbound passive collection cluster IP, the southbound active collection cluster IP, and the container IP for each node of southbound active collection must be able to communicate with the network gateway of the network to which the IP addresses belong. If you cannot do that, data collection will be affected. · In southbound dual stack deployment mode, the southbound passive collection cluster IP, the southbound active collection cluster IP, and the container IP (IPv4 or IPv6) for each node of southbound active collection must be able to communicate with the network gateway of the network to which the IP addresses belong. If you cannot do that, data collection will be affected. · In the branch scenario of the EVPN solution, only the unified southbound & northbound network is supported in the cloud scenario. |
This document uses the southbound single stack mode as an example. In the actual environment, the southbound collection IP of the analyzer (IP address that the analyzer uses to communicate with the network devices) depends on the actual device deployment.
Southbound single stack (the southbound collection IP of the analyzer is the cluster IP allocated by the southbound single-stack network system)
1. Navigate to the System > Deployment page. Expand the Public Service entry.
2. In the Actions column for COLLECTOR, click Details as shown in Figure 2.
3. On the component details page that opens, you can see two cluster IPs.
¡ The cluster IP address corresponding to the component names without the init suffix is the southbound passive collection IP address of the analyzer. In this document, the southbound passive collection IP address is 3.2.139.233 (system-allocated). Collection methods mainly include NetStream, gRPC, SYSLOG, and SNMPTrap. The devices actively send data to this IP address.
¡ The cluster IP address corresponding to the component names with the init suffix is the southbound active collection IP address of the analyzer. In this document, the southbound active collection IP addresses are 3.2.139.237, 3.2.139.238, 3.2.139.239, and 3.2.239.240 (system-allocated IP+NIC IP addresses in the node containers). Collection methods include SNMP and NETCONF.
The component details page is as shown in Figure 3.
Figure 3 Viewing the southbound collection IP address
Southbound dual stack (the southbound collection IP of the analyzer is the cluster IP allocated by the southbound network system)
1. Navigate to the System > Deployment page. Expand the Public Service entry.
2. In the Actions column for COLLECTOR, click Details.
The Component Details page opens.
3. On this page, you can view two cluster IPs (cluster IPs of the southbound IPv4 network) and two cluster secondary IPs (cluster IPs of the southbound IPv6 network).
¡ The cluster IP address corresponding to the component names without the init suffix is the southbound passive collection IP address of the analyzer. In this document, the southbound passive collection IP address is 3.2.139.233 (system-allocated). Collection methods mainly include NetStream, gRPC, SYSLOG, and SNMPTrap. The devices actively send data to this IP address.
¡ The cluster IP address corresponding to the component names with the init suffix is the southbound active collection IP address of the analyzer. In this document, the southbound active collection IP addresses are 3.2.139.237, 3.2.139.238, 3.2.139.239, and 3.2.239.240 (system-allocated IP+NIC IP addresses in the node containers). Collection methods include SNMP and NETCONF.
The component details page is as shown in Figure 4.
Figure 4 Viewing the southbound collection IPv4 and IPv6 addresses
Unified southbound & northbound network (the southbound collection IP of the analyzer is the northbound service VIP)
The passive collection IP of the analyzer is the northbound service VIP. The active collection IP is the node IP of the collection component node.
You can identify the IP address information as follows:
1. Log in to https://northbound service VIP:8443/matrix/ui page.
2. Navigate to the Deploy > Clusters > Deploy Cluster page. Click the set icon for a node, as shown in Figure 5.
3. Select the Details option from the drop-down list to open the node details page, as shown in Figure 6. You can view the IP address of the node in the cluster.
4. To view the node IP addresses of other nodes in the cluster, repeat the previous steps.
Configure devices
Configure devices as needed. As a best practice, configure all devices. This section takes device Hub1 as an example. The configuration is as follows.
Prerequisites
|
|
WARNING! · This section mainly describes the zero-touch deployment configuration for devices. In the WAN branch solution, zero-touch deployment is used. You only need to make sure the devices and the controller can reach each other at Layer 3 and the controller can correctly incorporate devices. · The configuration deployed by the controller includes configuration of basic functions (for example, EVPN) and it is the prerequisites for testing the analyzer function later. For more information, see the latest controller deployment guides. |
1. Configure WebSocket.
The device actively sends WebSocket requests to the northbound service VIP of the controller, and establishes a TCP connection (with the default port number 19443). For example:
<Hub1>system-view
[Hub1]dns proxy
[Hub1]dns proxy enable
[Hub1]cloud-management server domain 192.168.40.155
2. Configure routing.
To advertise the routes of devices on the underlay network, you must configure the corresponding routing protocol. For example, you must configure routing protocol OSPF for an MSTP network, and configure static or default routes for an Internet network.
[Hub1]ospf 1
[Hub1-ospf-1]area 0.0.0.0
[Hub1-ospf-1-ospf-1-area-0.0.0.0] network 20.3.1.0 0.0.0.255
[Hub1]ip route-static 0.0.0.0 0 20.1.2.2
Configure SNMP
The analyzer collects device data through SNMP. You must configure SNMP settings on devices to ensure that the analyzer can correctly connect to devices. This section takes device Hub1 as an example.
[Hub1] snmp-agent
[Hub1] snmp-agent community read public
[Hub1] snmp-agent sys-info version all
[Hub1] snmp-agent target-host trap address udp-domain 3.2.139.233 params securityname public v2c //Southbound passive collection IP; on the unified southbound & northbound network, the command is "snmp-agent target-host trap address udp-domain 3.2.139.233 udp-port 50002 params securityname public v2c"
[Hub1] snmp-agent trap source loopback0 //The source interface is a loopback interface corresponding to the IP address incorporated by the analyzer.
Configure NETCONF
The analyzer collects device data through NETCONF. You must configure NETCONF settings on devices to ensure that the analyzer can correctly connect to devices. This section takes device Hub1 as an example.
1. Create a management user, and set the service type and user role for the user:
[Hub1] local-user admin class manage
[Hub1-luser-manage-admin] password simple admin
[Hub1-luser-manage-admin] service-type ssh telnet http https
[Hub1-luser-manage-admin] authorization-attribute user-role network-admin
2. Enable the NETCONF over SSH service:
[Hub1] netconf ssh server enable
3. Set the login authentication mode to scheme:
[Hub1] line vty 0 63
[Hub1-line-vty0-63] authentication-mode scheme
[Hub1-line-vty0-63] user-role network-admin
[Hub1-line-vty0-63] user-role network-operator
[Hub1-line-vty0-63] idle-timeout 0 0
Configure gRPC
Configure the sensor paths. This section takes device Hub1 as an example.
|
|
CAUTION: When the analyzer uses an IPv6 address to incorporate the device, the source address in the gRPC configuration must be the IPv6 address of the incorporated device. When the analyzer uses an IPv4 address to incorporate the device, enter the interface name. |
[HUB1] grpc enable
[HUB1] telemetry
[HUB1-telemetry] sensor-group device //Collect card and transceiver module information of the device
[HUB1-telemetry-sensor-group-device] sensor path device/boards
[HUB1-telemetry-sensor-group-device] sensor path device/extphysicalentities
[HUB1-telemetry-sensor-group-device] sensor path device/physicalentities
[HUB1-telemetry-sensor-group-device] sensor path device/transceivers //Collect transceiver module information
[HUB1-telemetry-sensor-group-device] sensor path car/carpolicies //Collect interface CAR information (configure this command as needed)
[HUB1-telemetry] sensor-group lldp
[HUB1-telemetry-sensor-group-lldp] sensor path lldp/lldpneighbors //Collect LLDP information
[HUB1-telemetry] sensor-group ifmgr //Collect basic interface information and statistics
[HUB1-telemetry-sensor-group-ifmgr] sensor path ifmgr/interfaces
[HUB1-telemetry-sensor-group-ifmgr] sensor path ifmgr/statistics
[HUB1-telemetry-sensor-group-ifmgr] sensor path ifmgr/ethportstatistics
[HUB1-telemetry] destination-group sa
[HUB1-telemetry-destination-group-sa] ipv4-address 3.2.139.233 port 50051
//The IP address is the southbound passive collection IP, and the port number is fixed at 50051
[HUB1-telemetry] subscription sa
[HUB1-telemetry-subscription-sa] sensor-group device sample-interval 60
//The minimum sampling interval allowed is 5 seconds. A smaller sampling interval consumes more CPU resources. Set the sampling interval according to the actual device conditions. Typically, set the sampling interval to 60 seconds
[HUB1-telemetry-subscription-sa] sensor-group interface sample-interval 60
//The minimum sampling interval allowed is 5 seconds. A smaller sampling interval consumes more CPU resources. Set the sampling interval according to the actual device conditions. Typically, set the sampling interval to 60 seconds
[HUB1-telemetry-subscription-sa] sensor-group lldp sample-interval 60
//The minimum sampling interval allowed is 5 seconds. A smaller sampling interval consumes more CPU resources. Set the sampling interval according to the actual device conditions. Typically, set the sampling interval to 60 seconds
[HUB1-telemetry-subscription-sa] source-address interface loopback0
[HUB1-telemetry-subscription-sa] destination-group sa
Enabling LLDP
[Hub1] lldp global enable
Add geographic areas
You can add geographic areas in multiple methods, for example, synchronize them from the controller or manually add them.
Synchronize geographic areas from the controller
1. To add a controller connection, navigate to the Analytics > Analysis Options > Resources > Assets > Data Sources page, click Add, and enter basic information on the page that open. Click OK to add the controller connection, as shown in Figure 7.
Parameters
¡ Name: Enter the name of a controller, a string of up to 36 characters.
¡ Type: Controller.
¡ Scene: SDWAN.
¡ Username: Specify a username for logging in to the system.
¡ Password: Specify the password for logging in to the system. The default is Pwd@12345.
¡ IP: Northbound service VIP.
¡ Port: Port number in the URL for logging in to the system. When the protocol is HTTP, the default port number is 30000. When the protocol is HTTPS, the default is 30443.
¡ HTTPS: To log in through HTTP, turn off this option. To log in through HTTPS, turn on this option.
2. To import areas, navigate to the Analytics > Analysis Options > Resources > Areas > Geographic Area page, and click Import Areas. Select Import from Controller, and wait until the areas are successfully imported, as shown in Figure 8.
Figure 8 Importing areas
Manually add areas
1. Navigate to the Analytics > Analysis Options > Resources > Areas > Geographic Area page, and click Add Area.
The page as shown in Figure 9 opens.
2. Configure the following required parameters on the page that opens:
¡ Area Name: Name of the area. It supports only Chinese characters, letters, digits, hyphens, and underscores, and cannot exceed 255 characters.
¡ Area Tag: Select a label for the area. Options include site, building, and custom. Select Site for the SDWAN scenario.
¡ Longitude: Enter the longitude of the site.
¡ Latitude: Enter the latitude of the site.
Add network assets
You can add network assets in multiple methods, for example, import them from an Excel template file or manually add them. You can add network assets in one or multiple methods. No matter which method is used to add network assets, make sure the incorporated IP addresses can reach the southbound addresses of the analyzer.
The analyzer does not support using different IP addresses to manage the same physical device.
If it is determined that the IP address of a device managed on the analyzer is different from that of the device managed on the controller, then in data source management in a branch scenario, you do not need to synchronize the device information from the controller.
The permission control of the analyzer is performed from both the device and the area dimensions. A device must be bound to an area. Areas can be synchronized from the controller or manually added.
Import assets from the template
1. Navigate to the Analytics > Analysis Options > Resources > Assets > Asset List page, and then click Download Template to download the template for importing assets, as shown in Figure 10.
2. Fill in the information of the assets to be imported in the template:
¡ Asset Name: Required. Enter a string of up to 64 characters. Only letters, Chinese characters, digits, hyphens (-), underscores (_), tildes (~), pound signs (#), and dots (.) are allowed.
¡ Asset Type: Options include Router, Switch, Firewall, LB, Cloud, AC, and Cloud AP. In this example, enter Router.
¡ IP Address: Enter the IPv4 or IPv6 address of an asset. The IP address is optional when the asset type is virtual asset and device category is cloud.
¡ MAC Address: Required. Enter the MAC address of an asset.
¡ Asset Version Number: Optional. Version number of an asset.
¡ Asset Model: Optional. Model of an asset.
¡ Asset Serial Number: Serial number of an asset. It is optional in on-premises deployment and required in cloud deployment.
|
|
NOTE: If the NETCONF template associated with the asset uses the cloud-management template, then the asset serial number is required and must be consistent with the serial number of the same physical device managed by the controller. |
¡ Security Type: Options include firewall, ips, waf, acg, and splat. This field is required for a firewall.
¡ Geographic Area: Required for non-admin accounts and optional for the admin account. Name of the geographic area to be bound to an asset. The name must have existed on the Analytics > Analysis Options > Resources > Areas > Geographic Area page.
¡ Logical Area: Optional. Name of the logical area to be bound to an asset. The name must have existed on the Analytics > Analysis Options > Resources > Areas > Logical Area page.
¡ Scenario: Required. In this example, select SDWAN.
¡ SNMP protocol template: Optional. Name of the SNMP template to be bound to an asset. The name must have existed on the Analytics > Analysis Options > Collector > Common Collector > SNMP page. For more information, see "Configure SNMP collection."
¡ NETCONF protocol template: Optional. Name of the NETCONF template to be bound to an asset. The name must have existed on the Analytics > Analysis Options > Collector > Common Collector > NETCONF page. For more information, see "Configure NETCONF collection."
3. Import assets from the template:
a. Navigate to the Analytics > Analysis Options > Resources > Assets > Asset List page.
b. Click Import Assets and select Import from Excel File. Wait until the assets are successfully imported, as shown in Figure 11.
Manually add assets
1. Navigate to the Analytics > Analysis Options > Resources > Assets page, and click Add Asset.
The page as shown in Figure 12 opens.
2. Configure the following parameters on the page that opens:
¡ Asset Type: Options include Network Device, Security, and Virtual Asset. The default is Network Device. In this example, select Network Device.
¡ Device Category: Options include Router, Switch, AC, and Cloud AP. The default is Router. In this example, select Router.
¡ Asset Name: Required. Enter a string of up to 64 characters. Only letters, Chinese characters, digits, hyphens (-), underscores (_), tildes (~), pound signs (#), and dots (.) are allowed.
¡ Asset No.: Optional. Enter asset serial numbers, separated with commas.
|
|
NOTE: If the NETCONF template associated with the asset uses the cloud-management template, then the asset serial number is required and must be consistent with the serial number of the same physical device managed by the controller. |
¡ IP Address: Required. Enter an IPv4 or IPv6 address.
¡ Scenario: Required. In this example, select SDWAN.
¡ Geographic Area: For the admin account, this field is optional and is Global by default. For non-admin accounts, this field is required, and you must select a geographic area as needed. This example uses Global.
¡ Logical Area: Optional. Select a logical area as needed. The default value is Global.
¡ Device Role: Not available in the WAN scenario.
¡ Other Properties: Not available in the WAN scenario.
¡ Description: Optional. Enter a description for the asset.
|
|
NOTE: The Asset Type, Device Category, Asset Name, IP Address, and Scenario fields are required, and the other fields are optional. After an asset is added, the other information about the device is automatically obtained by the system. |
Add virtual assets
|
|
CAUTION: This step applies only when the cloud view (service provider network, Internet, or MPLS) is involved in the WAN branch scenario. In this case, you must add virtual assets. |
1. Navigate to the Analytics > Analysis Options > Resources > Assets page, and click Add Asset.
The page as shown in Figure 13 opens.
2. Configure the following parameters on the page that opens:
¡ Asset Type: Options include Network Device, Security, and Virtual Asset. The default is Network Device. In this example, select Virtual Asset.
¡ Device Category: When the asset type is Virtual Asset, the default device category is Cloud. In this example, select Cloud.
¡ Asset Name: Required. Enter a string of up to 64 characters. Only letters, Chinese characters, digits, hyphens (-), underscores (_), tildes (~), pound signs (#), and dots (.) are allowed.
¡ Scenario: Optional. In this example, select SDWAN.
Figure 13 Adding virtual assets
Configure collection settings
Configure SNMP collection
Configure SNMP templates
|
|
NOTE: SNMP collection cannot be deployed in the cloud. |
1. Navigate to the Analytics > Analysis Options > Collector > Common Collector > SNMP page. Manually add a protocol template on this page.
|
|
NOTE: If the SNMP configuration of the device matches the configuration of the SNMP access protocol template that is default-bound to the analyzer, you do not need to manually add a protocol template. If they are not consistent, you must add an SNMP access protocol template according to the configuration on the device and bind it. |
2. Navigate to the Analytics > Analysis Options > Resources > Assets > Asset List page. Select devices, and click Set Access Parameters.
3. From the dropdown menu, select SNMP Template Settings, select the corresponding template, and click OK, as shown in Figure 14.
Figure 14 SNMP template settings
Refer to the steps below to view the default SNMP template and manually add an SNMP template.
· To view the default SNMP template: Locate the template named default in the SNMP template list, and then click Details in the Actions column for this template. In the window that opens, view the default SNMP template configuration, as shown in Figure 16.
Figure 15 Protocol template list
Figure 16 Default SNMP access protocol template
· To add an SNMP template: Add the corresponding template based on the device configuration.
¡ Create an SNMPv1 template:
If a device is configured with SNMPv1, you must create an SNMPv1 template accordingly on the analyzer.
Navigate to the Analytics > Analysis Options > Collector > Common Collector > SNMP page. Click Add and then configure the parameters as follows:
- Template Name: Required. Enter a template name, a string of up to 32 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
- Version: Required. Select v1.
- Read-Only Community Name: Required. Enter the corresponding name configured on the device. The default name is public.
- Read-Write Community Name: Optional. Enter the corresponding name configured on the device. The default name is private.
- Port Info: Required. Enter the corresponding value configured on the device. The default port is 161.
- Timeout: Required. Configure the timeout based on the actual network latency. The default value is 4 seconds. Modify this value only if absolutely necessary.
- Retries: Required. Configure this value according to the actual network latency. The default value is 4 seconds. Modify this value only if absolutely necessary.
Figure 17 Creating an SNMPv1 template
¡ Create an SNMPv2c template:
If a device is configured with SNMPv2c, you must create an SNMPv2c template accordingly on the analyzer.
Navigate to the Analytics > Analysis Options > Collector > Common Collector > SNMP page. Click Add and then configure the parameters as follows:
- Template Name: Required. Enter a template name, a string of up to 32 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
- Version: Required. Select v2c.
- Read-Only Community Name: Required. Enter the corresponding name configured on the device. The default name is public.
- Read-Write Community Name: Optional. Enter the corresponding name configured on the device. The default name is private.
- Port Info: Required. Enter the corresponding value configured on the device. The default port is 161.
- Timeout: Required. Configure the timeout based on the actual network delay. The default value is 4 seconds. Modify this value only if absolutely necessary.
- Retries: Required. Configure this value according to the actual network latency. The default value is 4 seconds. Modify this value only if absolutely necessary.
Figure 18 Create an SNMPv2c template:
¡ Create an SNMPv3 template:
If a device is configured with SNMPv3, you must create an SNMPv3 template accordingly on the analyzer.
Navigate to the Analytics > Analysis Options > Collector > Common Collector > SNMP page. Click Add and then configure the parameters as follows:
- Template Name: Required. Enter a template name, a string of up to 32 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
- Version: Required. Select v3.
- Username: Required. Enter the corresponding name configured on the device.
- Authentication Algorithm: Required. Select the algorithm configured on the device. The default value is Auth-Sha.
- Authentication Key: Required. Enter the corresponding value configured on the device. This field is not available when the authentication algorithm is No-Auth.
- Encryption Algorithm: Required. Select the corresponding protocol configured on the device.
- Encryption Key: Enter the corresponding value configured on the device. This field is not available when the Encryption Algorithm is No-Priv.
- ContextName: Optional. Enter the corresponding name configured on the device.
- Port Info: Required. Enter the corresponding value configured on the device. The default port is 161.
- Timeout: Required. Configure the timeout based on the actual network latency. The default value is 4 seconds. Modify this value only if absolutely necessary.
- Retries: Required. Configure this value according to the actual network latency. The default value is 4 seconds. Modify this value only if absolutely necessary.
Figure 19 Creating an SNMPv3 template
Configure SNMP collection tasks
SNMP collection tasks are started by default.
Configure NETCONF collection
Configure NETCONF templates
|
|
NOTE: Select a custom NETCONF templates or NETCONF template Cloud-Management. · A custom NETCONF template uses SSH connections to subscribe to data. · NETCONF template Cloud-Management uses WebSocket connections to subscribe to data. For deployment in the cloud, you must select NETCONF template Cloud-Management. |
1. Edit a custom NETCONF template:
b. In the dialog box that opens, configure related parameters, and click OK to add a NETCONF template, as shown in Figure 20.
- Enter a template name. This field is required.
- Enter a username and password.
- Use the default settings for the other parameters
|
|
CAUTION: For the analyzer to correctly establish a NETCONF connection to a device and ensure collection for related tasks, make sure the configured username and password are the same as those on the device. |
Figure 20 Creating a NETCONF protocol template
2. Edit NETCONF template Cloud-Management:
To use NETCONF template Cloud-Management, you must execute related commands on the device. For more information, see “Configure WebSocket.”
Template Cloud-Management is generated by default, and you do not need to manually configure it.
3. Reference the NETCONF templates:
a. Navigate to the Analytics > Analysis Options > Resources > Assets > Asset List page. Select devices and then click Set Access Parameters.
b. From the dropdown menu, select NETCONF Template Settings. Select a custom protocol template or template Cloud-Management and the general template for the WAN scenario (WAN_basic_template), as shown in the following figures:
Figure 21 Custom NETCONF template settings
Figure 22 NETCONF template Cloud-Management settings
Figure 23 NETCONF collection template settings
Configure NETCONF collection tasks
The NETCONF collection tasks are started by default.
Configure gRPC collection
gRPC collection tasks are started by default.
Configure the analysis tasks
Configure the DeviceResource analysis task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Start analysis task DeviceResource, as shown in Figure 24.
Figure 24 Starting analysis task DeviceResource
Configure the IfKpiAnalysis analysis task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Start the IfKpiAnalysis analysis task, as shown in Figure 25.
Figure 25 IfKpiAnalysis analysis task
Configure the NodeKpiAnalysis analysis task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Start analysis task NodeKpiAnalysis, as shown in Figure 26.
Figure 26 NodeKpiAnalysis analysis task
Generate the topology
1. About 10 minutes after the configuration is finished, navigate to the Analytics > Health Analysis > Health Overview > Topology page.
The topology can be automatically generated, as shown in Figure 27.
2. In this case, you can manually adjust the
device layout or use the auto layout (horizontal alignment, auto layered
layout, and layering by role) to adjust the topology, as shown in Figure 28. To save the adjustment, click the save icon 
.
Figure 28 Adjusting the topology
|
|
NOTE: The topology of links across Internet cannot be automatically obtained, and must be manually added. |
Network health
The network health page contains multiple tabs, including overview, device, board, interface, transceiver module, link, and power consumption. This page displays the health trend of devices, device status, and the list of devices in the network. By default, the health trend during the most recent 24 hours is displayed. You can specify a time span to display at the upper-left corner and can view the data during the most recent 15 days.
Configuration workflow
Figure 29 Configuration workflow
|
|
NOTE: · You can configure the SNMP, NETCONF, and gRPC collection methods to collect device information and interface information. · Do not use both NETCONF and SNMP to collect transceiver module data. · Health analysis tasks must be enabled, regardless of the collection methods you use. · As a best practice, use gRPC for data collection when there are a large number of devices. |
Network planning
See "Network diagram."
Restrictions and guidelines
MSR routers do not support reporting data of the network health chip-related collection metrics.
Procedure
Configure devices
Configure SNMP
See "Configure SNMP."
Configuring NETCONF
See "Configure NETCONF."
Configuring gRPC
See "Configure gRPC."
Configure syslog settings
Configure syslog settings to collect various logs during the operation of the device, including running logs, login logs, and fault logs of modules. This section takes device Hub1 as an example. The configuration is as follows:
[HUB1] info-center enable
[HUB1] info-center loghost source loopback0 //The source interface is a loopback interface corresponding to the IP address incorporated by the analyzer
[HUB1] info-center loghost 3.2.139.233 //Southbound passive collection IP address
Configure collection settings
Configure an SNMP template
See "Configure SNMP collection."
Configure a NETCONF template
See "Configure NETCONF collection."
Configure syslog collection settings
Navigate to the Analytics > Analysis Options > Resources > Assets > Asset List page, select target devices, click SYSLOG, and then select Enable.
Configure gRPC collection settings
The gRPC data collection task is enabled by default.
Configure SNMP trap collection settings
The SNMP trap data collection task is enabled by default.
Configure analysis tasks
Configure the DeviceResource analysis task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Start the DeviceResource analysis task, as shown in Figure 30.
Figure 30 Starting analysis task DeviceResource
Configure the IfKpiAnalysis analysis task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Start the IfKpiAnalysis analysis task, as shown in Figure 31.
Figure 31 IfKpiAnalysis analysis task
Configure the NodeKpiAnalysis analysis task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Start the NodeKpiAnalysis analysis task, as shown in Figure 32.
Figure 32 NodeKpiAnalysis analysis task
Configure the HealthAnalysis analysis task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Start the HealthAnalysis analysis task, as shown in Figure 33.
Figure 33 HealthAnalysis analysis task
Configure the SnmpTrapParase analysis task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Start the SnmpTrapParase analysis task, as shown in Figure 34.
Figure 34 SnmpTrapParase analysis task
Configure the bgpAnalysis analysis task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Start the bgpAnalysis task, as shown in Figure 35.
Figure 35 bgpAnalysis analysis task
Configure the QACLAnalysis task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Start the QACLAnalysis task, as shown in Figure 36.
Figure 36 QACLAnalysis analysis task
Configure the AbnormalDetection task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Start the AbnormalDetection task, as shown in Figure 36.
Figure 37 QACLAnalysis analysis task
Display the result
Navigate to the Analytics > Health Analysis > Network Analysis > Network Health page to display the device health. You can view detailed information by switching between the Device, Boards, Interface, Interface, Transceiver Modules, and Links tabs.
Figure 38 Network Health–Overview
Figure 39 Network Health–Device list
Figure 40 Network Health–Device
Figure 41 Network Health–Device (continued)
Figure 42 Network Health–Boards
Figure 43 Network Health–Boards (continued)
Figure 44 Network Health–Interface
Figure 45 Network Health–Interface (continued)
Figure 46 Network Health–Transceiver Modules
Figure 47 Network Health–Transceiver Modules Failure Prediction
Figure 48 Network Health–Links
Figure 49 Network Health-Links Metric Statistics
Change analysis
The change analysis page display history snapshot data comparison statistics and comparison details. By default, the history snapshot data comparison statistics during the most recent 24 hours are displayed. You can specify a time span to display at the upper-left corner.
Configuration workflow
Figure 50 Configuration workflow
|
|
NOTE: The LLDP, ARP, IPv4Route, and IPv6Route indexes can be collected through both NETCONF and gRPC. You must select only one of the two collection methods. For other indexes, you can use only NETCONF. |
Network planning
See "Network diagram."
Procedure
As a best practice, perform the configuration on each device. This section uses Hub1 as an example.
Configure devices
Configure SNMP
See "Configure SNMP."
Configuring NETCONF
See "Configure NETCONF."
Configuring gRPC
|
|
CAUTION: When the analyzer uses an IPv6 address to incorporate the device, the source address in the gRPC configuration must be the IPv6 address of the incorporated device. When the analyzer uses an IPv4 address to incorporate the device, enter the interface name. |
[Hub1]grpc enable
[Hub1]telemetry
[Hub1-telemetry]sensor-group test
[Hub1-telemetry-sensor-group-test]sensor path lldp/lldpneighbors //Collect LLDP information.
[Hub1-telemetry-sensor-group-test]sensor path route/ipv4routes //Collect IPv4 routing table.
[Hub1-telemetry-sensor-group-test]sensor path route/ipv6routes //Collect IPv6 routing table.
[Hub1-telemetry-sensor-group-test]sensor path mac/macunicasttable //Collect MAC address table.
[Hub1-telemetry-sensor-group-test]sensor path arp/arptable //Collect ARP table
[Hub1-telemetry-sensor-group-test]quit
[Hub1-telemetry]destination-group test
[Hub1-telemetry-destination-group-test]ipv4-address 3.2.139.233 port 50051
// The IP address is the southbound passive collection IP, and the port number is fixed at 50051.
[Hub1-telemetry-destination-group-test]quit
[Hub1-telemetry]subscription test
[Hub1-telemetry-subscription-test]sensor-group test sample-interval 300
[Hub1-telemetry-subscription-test]source-address interface loopback0
[Hub1-telemetry-subscription-test]destination-group test
Configure collection settings
Configure an SNMP template
See "Configure SNMP collection."
Configure a NETCONF template
1. See "Configure NETCONF collection" To add a NETCONF template.
2. Select the WAN general template, and click Add(Clone). Select ARP_ArpTable, ND_NDTable, Route_Ipv4Routes, and Route_Ipv6Routes, and then click OK, as shown in Figure 51.
Figure 51 Adding (cloning) an SNMP collection template
3. Navigate to the Analytics > Analysis Options > Resources > Assets > Asset List page, select target devices, and then click Set Asset Parameters. Click SNMP Template Settings, select the associated template, and then click OK, as shown in Figure 52.
Figure 52 Configuring SNMP template settings
Configure analysis tasks
Configure the DeviceResource analysis task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Start the DeviceResource analysis task, as shown in Figure 53.
Figure 53 Starting analysis task DeviceResource
Configure the IfKpiAnalysis analysis task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Start the IfKpiAnalysis analysis task, as shown in Figure 54.
Figure 54 IfKpiAnalysis analysis task
Configure the NodeKpiAnalysis analysis task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Start the NodeKpiAnalysis analysis task, as shown in Figure 55.
Figure 55 NodeKpiAnalysis analysis task
Display the result
Navigate to the Analytics > Health Analysis > Network Analysis > Change Analysis page to display the devices with changes.
Figure 56 Change analysis
NetStream flow analysis
NetStream collects and analyzes business traffic on a per-flow basis. It displays the devices, interfaces, and links in the path of a flow identified by the five-tuple (source IP address, destination IP address, source port, destination port, and protocol) and the VPN that the flow belongs. Flow analysis is performed based on interfaces, applications, IP groups, hosts, BGP, VPNs, and TTEs to provide traffic statistics such as incoming traffic size, outgoing traffic size, traffic trends, traffic list, and traffic details.
Configuration workflow
Figure 57 Configuration workflow
You must configure NETCONF or gRPC collection to collect interface descriptions. To use NETCONF, collection, you must bind a NETCONF collection template.
NetStream can analyze only the traffic data reported in the version 9 format.
Network planning
Restrictions and guidelines
· Interface-based NetStream flow analysis supports displaying the latency, jitter, and packet loss quality information and providing related tunnel quality information.
· The application names in NetStream configuration can be selected from the flow classifier templates of the QoS component.
· Tunnel quality information is not provided for traffic on underlay interfaces.
· For NetStream to provide BGP statistics, configure related BGP commands in advance. Support for those commands depends on the device model.
· The applications are displayed in the order of customized applications, applications synchronized from the QoS component, and applications identified and reported by device DPI.
· Cloud NetStream is supported by E6307 and later.
· The device sampling granularity and mode must be consistent across the devices with NetStream enabled.
Procedure
Configure device settings
Configure the sampling granularity
Configure the sampling granularity by using one of the following commands on all devices that perform NetStream flow analysis. Hub 1 is used as an example.
[Hub1] sampler ns mode random packet-interval 1024
[Hub1] sampler ns mode random packet-interval n-power 1 //Configure the sampling mode and sampling rate as an integer or 2 to the nth power.
Configure NetStream
|
|
IMPORTANT: The IP version in the following configuration is the IP version of business traffic, not underlay traffic. |
· Configure NetStream for IPv4 business traffic.
[Hub1]ip netstream //Enable NetStream if this command is supported.
[Hub1]ip netstream timeout active 1 //Set the aging timer for active flows to 1 minute as a best practice.
[Hub1]ip netstream export version 9 origin-as //Set the NetStream version for data export. To use cloud NetStream, execute the following command: ip netstream export version 9 origin-as serial-number
[Hub1]ip netstream export host 3.2.139.233 9996
//Configure the IP address for north-south passive data collection. The port number 9996 is the default port of the analyzer. If a VPN instance is configured for the route between the analyzer and the device network, you must specify the VPN instance name in this command. For example: [Hub1]ip netstream export host 3.2.139.233 9996 vpn-instance vpnname
[Hub1]ip netstream export source interface LoopBack0 //Specify the source interface for data packets sent to NetStream servers.
· Configure IPv4 NetStream inbound and outbound traffic collection on interfaces.
[Hub1]interface GigabitEthernet2/0 //Enter the view of an interface. Typically, configure NetStream on all WAN interfaces.
[Hub1-GigabitEthernet2/0]ip netstream outbound //Configure NetStream outbound traffic collection.
[Hub1-GigabitEthernet2/0]ip netstream inbound //Configure NetStream inbound traffic collection. Configuring both inbound and outbound collection might affect device performance. Make sure you are fully aware of the impact.
[Hub1-GigabitEthernet2/0]ip netstream outbound sampler ns //Configure NetStream outbound sampling.
[Hub1-GigabitEthernet2/0]ip netstream inbound sampler ns //Configure NetStream inbound sampling.
[Hub1-GigabitEthernet2/0]ip netstream ipsec raw-packet //Configure IPsec decapsulation if IPsec encryption is performed on traffic.
|
|
NOTE: When traffic is transmitted through a subinterface, configure the netstream command on the subinterface for devices using the B64 platform. For device devices using the B75 platform, configure the netstream command on the physical interface. |
· Configure IPv4 NetStream inbound and outbound traffic collection on tunnel interfaces.
[Hub1]interface Tunnel 1 //Enter the view of a tunnel interface.
[Hub1-Tunnel1]ip netstream outbound //Configure NetStream outbound traffic collection.
[Hub1- Tunnel1]ip netstream inbound //Configure NetStream inbound traffic collection. Configuring both inbound and outbound collection might affect device performance. Make sure you are fully aware of the impact.
[Hub1- Tunnel1]ip netstream outbound sampler ns //Configure NetStream outbound sampling.
[Hub1- Tunnel1]ip netstream inbound sampler ns //Configure NetStream inbound sampling.
[Hub1- Tunnel1]ip netstream ipsec raw-packet //Configure IPsec decapsulation if IPsec encryption is performed on traffic.
· Configure NetStream for IPv6 business traffic.
[Hub1]ipv6 netstream //Enable NetStream if this command is supported.
[Hub1]ipv6 netstream timeout active 1 //Set the aging timer for active flows to 1 minute as a best practice.
[Hub1]ipv6 netstream export version 9 origin-as //Set the NetStream version for data export. To use cloud NetStream, execute the following command: ipv6 netstream export version 9 origin-as serial-number
[Hub1]ipv6 netstream export host 3.2.139.233 9996 //Configure the IP address for north-south passive data collection. The port number 9996 is the default port of the analyzer component. If a VPN instance is configured for the route between the analyzer and the device network, you must specify the VPN instance name in this command. For example: [Hub1]ipv6 netstream export host 3.2.139.233 9996 vpn-instance vpnname
[Hub1]ipv6 netstream export source interface LoopBack0 //Specify the source interface for data packets sent to NetStream servers.
|
|
NOTE: When traffic is transmitted through a subinterface, configure the netstream command on the subinterface for devices using the B64 platform. For device devices using the B75 platform, configure the netstream command on the physical interface. |
· Configure IPv6 NetStream inbound and outbound traffic collection on interfaces.
[Hub1]interface GigabitEthernet2/0 //Enter the view of an interface. Typically, configure NetStream on all WAN interfaces.
[Hub1-GigabitEthernet2/0]ipv6 netstream outbound //Configure IPv6 NetStream outbound traffic collection. This configuration might affect device performance. Make sure you are fully aware of the impact.
[Hub1-GigabitEthernet2/0]ipv6 netstream outbound sampler ns //Configure IPv6 NetStream outbound sampling.
[Hub1-GigabitEthernet2/0]ipv6 netstream inbound //Configure IPv6 NetStream inbound traffic collection. Configuring both inbound and outbound collection might affect device performance. Make sure you are fully aware of the impact.
[Hub1-GigabitEthernet2/0]ipv6 netstream inbound sampler ns //Configure IPv6 NetStream inbound sampling.
[Hub1-GigabitEthernet2/0]ipv6 netstream ipsec raw-packet //Configure IPv6 IPsec decapsulation if IPsec encryption is performed on traffic.
· Configure IPv6 NetStream inbound and outbound traffic collection on tunnel interfaces.
[Hub1]interface Tunnel 1 //Enter the view of a tunnel interface.
[Hub1-Tunnel1]ipv6 netstream outbound //Configure NetStream outbound traffic collection.
[Hub1- Tunnel1]ipv6 netstream inbound //Configure NetStream inbound traffic collection. This configuration might affect device performance. Make sure you are fully aware of the impact.
[Hub1- Tunnel1]ipv6 netstream outbound sampler ns //Configure NetStream outbound sampling.
[Hub1- Tunnel1]ipv6 netstream inbound sampler ns //Configure NetStream inbound sampling.
[Hub1- Tunnel1]ipv6 netstream ipsec raw-packet //Configure IPsec decapsulation if IPsec encryption is performed on traffic.
· Configure community attributes as needed. The following configuration uses BGP VPNv4 configuration as an example.
¡ Configure community attributes.
[Hub1]route-policy r1 permit node 1
[Hub 1-route-policy-r1-1] apply community 100:1 //Configure one or multiple community attributes.
¡ Configure a RIB.
[Hub1]rib
[Hub1-rib]address-family ipv4
[Hub1-rib]flush route-attribute bgp //Carry attribute messages in routes when RIB deploys the routes to FIB
¡ Add labels to outgoing traffic, and apply a routing policy to a BGP peer.
[Hub1]bgp 100
[Hub1-bgp-default]address-family vpnv4
[Hub1-bgp-default-bgp-default-vpnv4] peer 72.26.1.2 route-policy r1 export //Specify the IP address of a BGP peer.
[Hub1-bgp-default-bgp-default-vpnv4] peer 72.26.1.2 advertise-community
· Configure SDWAN tunnel quality collection.
[Hub1] grpc enable
[Hub1] telemetry
[Hub1-telemetry] sensor-group TunnelQuality
[Hub1-telemetry-sensor-group-TunnelQuality] sensor path rir/sdwanlinkqualities/sdwanlinkquality/peerttes/peertte/results/result
[Hub1-telemetry] destination-group sa
[Hub1-telemetry-destination-group-sa] ipv4-address 3.2.139.233 port 50051 //Specify the IP address for north-south passive data collection.
[Hub1-telemetry] subscription sa
[Hub1-telemetry-subscription-test] sensor-group TunnelQuality sample-interval 60
//Set the sampling interval to 60 seconds as a best practice.
[Hub1-telemetry-subscription-sa] source-address interface loopback0
[Hub1-telemetry-subscription-sa] destination-group sa
· Verify that the APR process is running.
|
|
IMPORTANT: NetStream relies on the APR process to automatically identify device DPI applications. The methods for pulling the APR process and the load on device performance vary by device model. For more information, see the technical support team for the routers. |
[Hub1]display application
Total:416
Pre-defined count:416
User-defined count:0
Application name Type App ID Tunnel Encrypted DetectLen
116114 Pre-defined 0x000050d8 No No 0
11Platform Pre-defined 0x00005179 No No 0
12530WAPMenHu Pre-defined 0x00005208 No No 0
12580 Pre-defined 0x00004eed No No 0
126WebEmail Pre-defined 0x000051b8 No No 0
139Email Pre-defined 0x00005240 No No 0
163Email Pre-defined 0x000051be No No 0
17173 Pre-defined 0x00004f15 No No 0
178Game Pre-defined 0x00004e8e No No 0
19Lou Pre-defined 0x000051a8 No No 0
1HaoYaoDian Pre-defined 0x00005289 No No 0
2345DaoHang Pre-defined 0x0000528a No No 0
360News Pre-defined 0x000050fd No No 0
360Weather Pre-defined 0x0000504e No No 0
365DiChanJiaJu Pre-defined 0x0000520a No No 0
36Kr Pre-defined 0x00004ff9 No No 0
4399 Pre-defined 0x00004f31 No No 0
51Com Pre-defined 0x0000519b No No
Collect interface descriptions
Perform one of the following tasks:
2. Configure gRPC. Only Ifmgr subscription is required.
Configure data collection
Configure NetStream collection
NetStream collection tasks are enabled by default.
Collect interface and SDWAN tunnel information
Perform one of the following tasks:
· Configure NETCONF collection.
NETCONF collection tasks are enabled by default. In the NETCONF collection template, select the Ifmgr_Interfaces, SDWAN_SdwanTteConnections, and SDWAN_SdwanSiteTte indexes.
· Configure gRPC collection.
gRPC collection tasks are enabled by default.
Configure analysis tasks
Configure the NetStream analysis task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Enable the NetStream analysis task.
Figure 58 Enabling the NetStream analysis task
3. If the sampling rate is set by the power of 2, select yes for the sampling by the power of 2 parameter.
Figure 59 Modifying the sampling parameters
Configure the SDWAN tunnel analysis task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Enable the SDWAN tunnel analysis task.
Figure 60 Enabling the SDWAN tunnel analysis task
Configure the IfKpiAnalysis analysis task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Enable the IfKpiAnalysis task.
Figure 61 Enabling the IfKpiAnalysis task
Configure global NetStream settings
Perform the following tasks as needed.
Configure applications and application types
1. Navigate to the Analytics > Analysis Options > Global Configure > Application Configuration page.
2. Hover the curser over User-defined Applications, and then click the plus sign.
3. Add an application type.
Figure 62 Adding an application type
Figure 63 Configuring an application type
4. Click Create, and configure the following parameters:
¡ Name: Enter an application name. The name is a case-sensitive string of Chinese characters, letters, digits, and special characters. The name cannot exceed 36 characters.
¡ Used Names: Leave this parameter empty.
¡ Abbreviation: Leave this parameter empty. This parameter is used in non-WAN scenarios.
¡ Full flow link: Leave this parameter empty. This parameter is used in non-WAN scenarios.
¡ Protocol: Select an option from TCP, UDP, or ANY. ANY indicates that the protocol is not distinguished.
¡ Company: Configure as needed.
¡ Type: Select the application type you have added.
¡ Level: Select a level. This parameter is used in non-WAN scenarios.
¡ Description: Configure as needed.
¡ Client IP Addresses: Enter the source IPv4 or IPv6 addresses of the traffic to match.
¡ Client Ports: Enter the source port number of the traffic to match.
¡ Server IP Addresses: Enter the destination IPv4 or IPv6 addresses of the traffic to match.
¡ Server Ports: Enter the destination port number of the traffic to match.
¡ URL/IP: Leave this parameter empty.
¡ Application Protocol: Leave this parameter empty. This parameter is used in non-WAN scenarios.
¡ Response Level: Use the default setting. This parameter is used in non-WAN scenarios.
5. Click Save.
Configure interface groups
1. Navigate to the Analytics > Analysis Options > Global Configure > Interface Group Settings page.
2. Click Add Configuration.
Figure 64 Adding an interface group
3. Configure the following parameters, and then click Add to Configuration.
¡ Name: Enter an interface group name.
¡ Description: Configure as needed.
¡ Device Name: Select a device.
¡ Device IP: Select the IP address of the device.
¡ Interface Name: Select interfaces.
Figure 65 Configuring an interface group
4. Click OK.
Figure 66 Interface group list
Add IP groups to a network segment
1. Navigate to the Analytics > Analysis Options > Global Configure > Network Segment Configuration page.
2. Select a network segment, and then click Add.
3. Configure the following parameters:
¡ Enabled or Not: Use the default setting.
¡ Network Segment Name: Enter a network segment name.
¡ Link Name: Leave this parameter empty. This parameter is used in non-WAN scenarios.
¡ IP Address Ranges: Enter source and destination IP addresses or IP address ranges to match.
4. Click OK.
View NetStream flow analysis results
1. Navigate to the Analytics > Health Analysis > Flow Analysis > NetStream Flow Analysis page.
2. Click each tab to view the traffic analysis results for interfaces, interface groups, application groups, applications, IP addresses, hosts, sessions, BGP, VPNs, and TTEs
Figure 67 NetStream flow analysis results for underlay traffic on interfaces
Figure 68 NetStream flow analysis results for overlay traffic on interfaces
Figure 69 NetStream flow analysis results for interface groups
Figure 70 NetStream flow analysis results for applications
Figure 71 NetStream flow analysis results for application groups
Figure 72 NetStream flow analysis results for IP groups
Figure 73 NetStream flow analysis results for hosts
Figure 74 NetStream flow analysis results for sessions
Figure 75 NetStream flow analysis results for BGP
Figure 76 BGP traffic list
Figure 77 NetStream flow analysis results for VPNs
Figure 78 NetStream flow analysis results for TTEs
Network path detection
Network path detection uses NQA Two-Way Active Measurement Protocol (TWAMP) Light to detect the path latency, jitter, and packet loss on the specified source and destination IP addresses. The analyzer collects and analyzes the statistics of test sessions and test results for the TWAMP module of all devices. Then, it performs calculation based on the time granularity, providing network quality measurement and analysis for all forwarding paths on the network.
Configuration workflow
Figure 79 Configuration workflow
|
|
NOTE: · Configure either NETCONF or gRPC collection for TWAMP Light. TWAMP Light is commonly configured. · As a best practice, use gRPC for data collection when the network has a large number of devices. · You can configure quality thresholds. Threshold violation events are pushed to the anomalies analysis page. |
Network planning
See "Network diagram."
Procedure
Configure devices settings
Configure NETCONF settings
See "Configure NETCONF."
Configure gRPC settings
|
|
CAUTION: When the analyzer uses an IPv6 address to incorporate the device, the source address in the gRPC configuration must be the IPv6 address of the incorporated device. When the analyzer uses an IPv4 address to incorporate the device, enter the interface name. |
The example uses Hub1 as an example to describe how to configure sensor paths.
[Hub1] grpc enable
[Hub1] telemetry
[Hub1-telemetry] sensor-group twamp_client
[Hub1-telemetry-sensor-group-twamp_client] sensor path nqa/twamplightclients
[Hub1-telemetry] sensor-group twamp_two_way //collect two-way latency quality
[Hub1-telemetry-sensor-group-twamp_two_way] sensor path nqa/twamplightdelaystats/twamplightdelaystat
[Hub1-telemetry-sensor-group-twamp_two_way] sensor path nqa/twamplightlossstats/twamplightlossstat
[Hub1-telemetry] destination-group sa
[Hub1-telemetry-destination-group-sa] ipv4-address 3.2.139.233 port 50051
//The IP address is the southbound passive collection IP, and the port number is fixed at 50051
[Hub1-telemetry] subscription sa
[Hub1-telemetry-subscription-sa] sensor-group twamp_client sample-interval 60
//The minimum sampling interval allowed is 5 seconds. A smaller sampling interval consumes more CPU resources. Set the sampling interval according to the actual device conditions. Typically, set the sampling interval to 60 seconds and the sampling interval is not changed once set
[Hub1-telemetry-subscription-sa] sensor-group twamp_two_way sample-interval 10
//The minimum sampling interval allowed is 5 seconds. A smaller sampling interval consumes more CPU resources. Set the sampling interval according to the actual device conditions. Available sampling intervals are 5 seconds, 10 seconds, and 60 seconds. Typically, set the sampling interval to 10 seconds
[Hub1-telemetry-subscription-sa] source-address interface loopback0
[Hub1-telemetry-subscription-sa] destination-group sa
Configure TWAMP Lite
The source and destination IP addresses are the two end IP addresses of the path to be detected, which are configured on the devices on both ends of the path, respectively. The following uses the path between Hub1 and Agg1 as an example. You can configure TWAMP Lite for all links on the network.
· Configure Agg1:
//Configure the TWAMP Light client
[Agg1] nqa twamp-light client
[Agg1-nqa-twamp-light-client] test-session 1
[Agg1-nqa-twamp-light-client-session1] source ip 20.3.1.1
[Agg1-nqa-twamp-light-client-session1] destination ip 20.3.1.2
[Agg1-nqa-twamp-light-client-session1] source port 1000 //No requirements for the port number
[Agg1-nqa-twamp-light-client-session1] destination port 2000 //No requirements for the port number
//Start a TWAMP Light test
[Agg1] nqa twamp-light sender
[Agg1-nqa-twamp-light-sender] start test-session 1 permanent statistics-interval 1000 monitor 2000
· Configure Hub1:
//Configure the NQA server
[Hub1] nqa server enable
[Hub1] nqa twamp-light responder
[Hub1-nqa-twamp-light-responder] test-session 1 ip destination 20.3.1.2 source 20.3.1.1 destination-port 2000 source-port 1000
Configure collection settings
Configure NETCONF collection
1. Configure NETCONF templates. For more information, see "Configure NETCONF collection."
When you configure a NETCONF collection template, select the NQA_TwamplightClients, NQA_TwamplightDelayStats_TwamplightDelayStat, and NQA_TwamplightLossStats_TwamplightLossStat collected metrics.
2. Navigate to the Analytics > Analysis Options > Resources > Assets > Asset List page. Select the device, and then select Set Access Parameters > NETCONF Template Settings. Select the templates, and then click OK.
Figure 80 Protocol template settings
Figure 81 Collection template settings
Figure 82 Selecting collected metrics
Configure gRPC collection
gRPC collection tasks are started by default.
Configure analysis task settings
Start the TwampStreamAnalysis task
1. Navigate to the Analytics > Analysis Options > Task Management page, and then start the TwampStreamAnalysis task.
Figure 83 TwampStreamAnalysis task
2. If you use gRPC for data collection, make sure the gRPC sampling interval for the task is the same as that configured on the device. The gRPC sampling interval configured on the device is the value for the twamp_two_way sample-interval field in the configuration example. In the configuration example, the sampling interval is 10 seconds. Select 10 from the gRPC Sampling Interval(second) list.
Figure 84 Editing the gRPC sampling interval
Set alarm thresholds
|
|
IMPORTANT: If you edit the threshold settings for a single path, the new settings take effect only on the path. |
|
|
NOTE: You can use the following default global thresholds or configure the thresholds as required: · Latency threshold—200000 us. · Jitter threshold—50000 us. · Packet loss threshold—30%. · Packet error threshold—30%. |
To set alarm thresholds:
1. To set the global thresholds, navigate to the Analytics > Health Analysis > Network Analysis > Network Business Analysis > Network Path Detection page, and then click Global Threshold Settings. On the dialog box that opens, edit the thresholds. Global threshold settings take effect on all paths.
Figure 85 Configuring global threshold settings
2. To set the thresholds for a single path, navigate to the Analytics > Health Analysis > Network Analysis > Network Business Analysis > Network Path Detection page. Click the Thresholds icon in the Actions column for a path. On the dialog box that opens, click the Configure thresholds for this path link, and then configure the threshold settings as required.
Figure 86 Clicking the Thresholds icon in the Actions column for a path
Figure 87 Thresholds
Figure 88 Settings thresholds
Start the AnomaliesAnalysis task
Navigate to the Analytics > Analysis Options > Task Management page, and then start the AnomaliesAnalysis task.
Figure 89 AnomaliesAnalysis task
Display the result
1. Navigate to the Analytics > Health Analysis > Network Analysis > Network Business Analysis > Network Path Detection page. The Network Path Detection page displays the quality information for all forwarding paths. To view detailed quality information for a path, click the Details icon in the Actions column for the path. The page that opens displays the trend graphs of latency, jitter, packet loss rate, and packet error rate for the network path.
Figure 90 Network path detection – TopN data
Figure 91 Network path detection – service quality list
Figure 92 Quality trend graphs
2. Navigate to the Analytics > Diagnosis Analysis > Anomalies page. The anomalies analysis page opens, displaying the alarm messages.
Figure 93 Alarm messages pushed to the anomalies analysis page
Link traffic
Link traffic displays the usage of network links within a specific time range. After usage alarm thresholds are set, a link will generate alarms when its usage exceeds the thresholds. The AI prediction feature can display the future traffic usage and rate for a link based on its history traffic usage and rate. If the AI predicted usage is higher than the high usage threshold or lower than the low usage alarm threshold, the system will provide corresponding link expansion and contraction suggestions, and generate link capacity optimization prediction reports.
Configuration workflow
Figure 94 Configuration workflow
|
|
NOTE: · For basic interface traffic information about physical links, you can use SNMP, gRPC, or NETCONF to collect data. You must select one of the collection methods. · IPv4 and IPv6 link information is only supported by gRPC and requires device support. · As a best practice, use gRPC for data collection when the network has a large number of devices. |
Network planning
See "Network diagram."
Procedure
Configure device settings
Configure devices as required. As a best practice, configure all devices. The following uses Hub1 as an example.
Configure SNMP settings
See "Configure SNMP."
Configure NETCONF settings
See "Configure NETCONF."
Configure gRPC settings
|
|
CAUTION: When the analyzer uses an IPv6 address to incorporate the device, the source address in the gRPC configuration must be the IPv6 address of the incorporated device. When the analyzer uses an IPv4 address to incorporate the device, enter the interface name. |
The example uses Hub1 as an example to describe how to configure sensor paths.
[Hub1]grpc enable
[Hub1]telemetry
[Hub1-telemetry]sensor-group interface
[Hub1-telemetry-sensor-group-interface]sensor path ifmgr/interfaces
[Hub1-telemetry-sensor-group-interface]sensor path ifmgr/statistics
[Hub1-telemetry-sensor-group-interface]quit
[Hub1-telemetry]destination-group sa
[Hub1-telemetry-destination-group-sa]ipv4-address 3.2.139.233 port 50051 //The IP address is the southbound passive collection IP, and the port number is fixed at 50051
[Hub1-telemetry-destination-group-sa] quit
[Hub1-telemetry]subscription sa
[Hub1-telemetry-subscription-sa] sensor-group interface sample-interval 60
//A smaller sampling interval consumes more CPU resources. Set the sampling interval according to the actual device conditions. Typically, set the sampling interval to 60 seconds
[Hub1-telemetry-subscription-sa]source-address interface loopback0 //The source interface is a loopback interface corresponding to the IP address incorporated by the analyzer
[Hub1-telemetry-subscription-sa] destination-group sa
Configure collection settings
Configure SNMP collection
See "Configure SNMP collection."
Configure gRPC collection
gRPC collection tasks are started by default.
Configure NETCONF collection
See "Configure NETCONF collection."
Configure analysis task settings
Start the IfKpiAnalysis task
Navigate to the Analytics > Analysis Options > Task Management page, and then start the IfKpiAnalysis task.
Start the NodeKpiAnalysis task
Navigate to the Analytics > Analysis Options > Task Management page, and then start the NodeKpiAnalysis task.
Figure 96 NodeKpiAnalysis task
Set alarm thresholds and enable AI prediction
1. Navigate to the Analytics > Health Analysis > Network Analysis > Network Health > Links page, and then click the configuration icon in the Links-Metric Statistics area. On the dialog box that opens, configure the low usage alarm threshold, high usage alarm threshold, and AI prediction validity period as required.
Figure 97 Link traffic settings
2. Navigate to the Analytics > Health Analysis > Network Analysis > Network Health > Links page, and then select AI Prediction Link for links. AI prediction predicts the future traffic usage and rate for the links based on their history traffic usage and rate. To view the prediction trend graphs for a link, click the icon to the left of the link.
Figure 98 Enabling AI prediction
3. If the predicted usage is higher than the specified high usage alarm threshold or lower than the specified low usage alarm threshold, corresponding alarms are generated and link bandwidth expansion or contraction suggestions are provided on the Analytics > Diagnosis Analysis > Issue Analysis page. You can view the suggestions for all links in the Link capacity optimization prediction Report.
Display the result
Navigate to the Analytics > Health Analysis > Network Analysis > Network Health > Links page to display the usage of physical links in a specific time range. Click the right arrow next to the link name to display the link usage and rate. If you enable AI prediction, the AI predicted traffic usage and rate for the link are also displayed.
Figure 99 Physical links
Figure 100 Physical link details
Navigate to the Analytics > Report > Report template > List of report templates page, and then select the link capacity optimization prediction report to view the report.
Figure 101 Link capacity optimization prediction Report
Route monitoring
Route monitoring displays the most recent route neighbor information for the routing protocols configured on the devices.
Configuration workflow
Figure 102 Configuration workflow
|
|
NOTE: For BGP, OSPF, and IS-IS, configure either SNMP collection or NETCONF collection (required setting). NETCONF collection is supported by only specific device versions. For OSPFv3, only NETCONF collection is supported. |
Network planning
See "Network diagram."
Restrictions and guidelines
· In the collection template settings, you can see the collection time for collection indexes. You need to wait for 20 minutes before the data can be displayed.
· Route monitoring supports the SNMP and NETCONF collection methods (NETCONF collection is supported by only specific device versions). For OSPFv3, only NETCONF collection is supported.
Procedure
Configure device settings
Configure SNMP
See "Configure SNMP."
Configuring NETCONF
See "Configure NETCONF."
Configure collection settings
Configure SNMP collection settings
Configure an SNMP template
1. Navigate to the Analytics > Analysis Options > Collector > Common Collector > SNMP page, select the default template, and click Add(Clone). Select isis_neighbor, bgp_neighbor, and ospf_neighbor, and then click OK, as shown in Figure 103.
Figure 103 Adding (cloning) an SNMP collection template
2. Navigate to the Analytics > Analysis Options > Resources > Assets > Asset List page, select target devices, and then click Set Asset Parameters. Click SNMP Template Settings, select the associated template, and then click OK, as shown in Figure 104.
Figure 104 Configuring SNMP template settings
Configure SNMP collection tasks
SNMP collection tasks are started by default.
Configure NETCONF collection settings
Configure a NETCONF template
1. Navigate to the Analytics > Analysis Options > Collector > Common Collector > NETCONF page, select the netconf_default collection template, and then click Add(Clone). Select BGP_Sessions, IETF_ospfv3_instance, IETF_ospfv3_instance_private, ISIS_Peers, OSPF_Neighbours, and then click OK, as shown in Figure 105.
Figure 105 Adding (cloning) a NETCONF collection template
2. Navigate to the Analytics > Analysis Options > Resources > Assets > Asset List page, select target devices, click Set Asset Parameters, and then click NETCONF Template Settings. Then select a custom template and WAN template, as shown in Figure 106.
Figure 106 Configuring NETCONF template settings
Configure NETCONF collection tasks
NETCONF data collection tasks are enabled by default.
Configure analysis task settings
The system automatically analyzes route neighbor information at the back end.
Display the result
Navigate to the Analytics > Health Analysis > Network Analysis > Network Business Analysis > Route Monitoring page to display the most recent route neighbor information on the physical topology and devices, as shown in Figure 107 to Figure 110.
Figure 107 Route monitoring-BGP
Figure 108 Route monitoring-OSPF
Figure 109 Route monitoring-IS-IS
Figure 110 Route monitoring-OSPFv3
Anomalies analysis
The anomalies analysis feature displays statistics about failures across the network within the specified time range. You can view failure information based on device, network, protocol, and overlay.
Configuration workflow
Figure 111 Configuration workflow
Network planning
See "Network diagram."
Procedure
Configure device settings
Configure syslog settings
See "Configure syslog settings."
Configure SNMP
See "Configure SNMP."
Configuring NETCONF
See "Configure NETCONF."
Configure collection settings
Configure syslog collection settings
Navigate to the Analytics > Analysis Options > Resources > Assets > Asset List page, select target devices, click SYSLOG, and then select Enable.
Configure an SNMP template
See "Configure SNMP collection."
Configure a NETCONF template
See "Configure NETCONF collection."
Collection task
Syslog, SNMP, and NETCONF data collection tasks are enabled by default.
Configure analysis task settings
Start the AnomaliesAnalysis task
Navigate to the Analytics > Analysis Options > Task Management page to start the AnomaliesAnalysis task, as shown in Figure 112.
Figure 112 Starting the AnomaliesAnalysis task
Start the AnomaliesAnalysis Java task
Navigate to the Analytics > Analysis Options > Task Management page to start the AnomaliesAnalysis Java task, as shown in Figure 113.
Figure 113 Starting the AnomaliesAnalysisJava task
Start network health analysis tasks
See "Configure analysis tasks."
Display the result
Navigate to the Analytics > Diagnosis Analysis > Anomalies page to display fault statistics in the network. You can view fault information by switching between the Device, Network, Protocol, and Overlay tabs.
Figure 114 Anomalies
Issue analysis
Issue analysis displays data for network issues.
Network issues: Issue statistics based on device category within the specified time range.
Configuration workflow
Figure 115 Configuration workflow
Network planning
See "Network diagram."
Procedure
Configure device settings
Configure SNMP
See "Configure SNMP."
Configure collection settings
Configure SNMP trap tasks
SNMP trap collection tasks are enabled by default.
Configure analysis task settings
Configure an SNMP trap analysis task
Navigate to the Analytics > Analysis Options > Task Management page to start the SNMP trap analysis task, as shown in Figure 116.
Figure 116 Configuring an SNMP trap analysis task
Display the result
Navigate to the Analysis > Diagnosis Analysis > Issue Analysis page displays issues in the system in details, as shown in Figure 117.
Intelligent prediction
With statistical learning and machine learning, intelligent prediction analyzes the regular patterns of time series data (KPI), fits and predicts the future trends of the data, and generates baselines and data predictions.
Configuration workflow
Figure 118 shows the configuration flowchart.
Figure 118 Configuration workflow
|
|
NOTE: · SNMP, NETCONF, and gRPC can collect device information and interface information. You must use one of them for data collection. · When the Analyzer needs to collect information from a large number of devices, use gRPC for data collection as a best practice. |
Network plan
See “Network diagram.”
Restrictions and guidelines
Before using the intelligent prediction service, start AI tasks as needed on the Analytics > Predict Analysis > AI Task Management page. The system performs AI tasks at 1:00 a.m. every day.
Configuration procedure
Configure device settings
Configure SNMP
For more information about this task, see "Configure SNMP."
Configure NETCONF
For more information about this task, see "Configure NETCONF."
Configure gRPC
For more information about this task, see "Configure gRPC."
Configure collection settings
Configure SNMP-based collection
For more information about this task, see "Configure SNMP collection."
Configure NETCONF-based collection
For more information about this task, see "Configure NETCONF collection."
Configure gRPC-based collection
By default, gRPC-based collection is enabled.
Configure analysis tasks
Enable the IfKpiAnalysis task
Navigate to the Analytics > Analysis Options > Task Management page, and then enable the IfKpiAnalysis task.
Figure 119 IfKpiAnalysis
Enable the NodeKpiAnalysis task
Navigate to the Analytics > Analysis Options > Task Management page, and then enable the NodeKpiAnalysis task.
Figure 120 NodeKpiAnalysis
Start AI tasks
Navigate to the Analytics > Predict Analysis > AI Task Management page, and then start AI tasks as needed.
Figure 121 Starting AI tasks
Intelligent prediction is not available for devices that do not generate time series data (KPI). Time series data is collected and delivered by other modules. For more information about CPU, memory, packet loss, and packet error data collection, see "Network health."
View the prediction results
1. Navigate to the Analytics > Predict Analysis > AI Tasks page. This page displays the list of incorporated devices.
2. Click the Details icon in the Actions column for a device. The system will display details of the device from multiple aspects including actual value, predicted value, upper value, and lower value. The displayed device details depend on the selected KPIs.
Figure 122 List of incorporated devices
Figure 123 Results of intelligent prediction
Report
The report template list displays all report templates that the current operator can manage. You can search for a service report as needed and export a report in multiple file formats. In addition, you can configure a report template to achieve regular statistics collection and automatic report file generation.
Configuration workflow
Figure 124 shows the configuration flowchart.
Figure 124 Configuration workflow
Network planning
See “Network diagram.”
Restrictions and guidelines
· If HTTP is enabled, only unidirectional authentication is supported.
· If HTTPS is enabled, the domain name in the server certificate cannot be an IP address.
· If you export a report template from the report template in CSV format, it will exported as a table rather than a picture.
· When the U-Center-IAR license expires, you cannot add report templates, add user-defined report templates, or manage scheduled reports.
Configuration procedure
The reported data is collected from service modules. For more information about service module configuration, see the configuration guides of desired service modules.
Supported report template categories include NE report, link & tunnel report, and application report. For more information about NetStream reports, see "NetStream flow analysis". For more information about link tunnel reports, see "Link traffic". For more information about application reports, see "Report".
Configure the report template list
Configure the display settings of NE report templates
1. Navigate to the Analytics > Report > Report Template > List of Report Templates page.
2. Click the name of an NE report template, and then configure parameters as needed. In this example, an NE report template is configured.
Figure 125 Display settings of the NE report template
Configure the display settings of link & tunnel traffic reports
1. Navigate to the Analytics > Report > Report Template > List of Report Templates page.
2. Click the name of a link tunnel template, and then configure parameters as needed. In this example, an IGP link traffic report template is configured.
Figure 126 Display settings of the IGP link traffic report template
Configure the display settings of application reports
1. Navigate to the Analytics > Report > Report Template > List of Report Templates page.
2. Click the name of an application template, and then configure parameters as needed. In this example, a NetStream report template is configured.
Figure 127 Display settings of the NetStream report template
Configure the periodic report list
Configure mail server settings
1. Navigate to the System > System Settings > Mail Server Configuration page.
2. Configure the following parameters as needed:
¡ Server Address: Domain name or IP address of the mail server. The value must be a string of 1 to 255 characters. This parameter is required.
¡ Server Port: Domain name or IP address of the mail server. The value must be a string of 1 to 255 characters. This parameter is required.
¡ Server Connection (SSL/TLS): Options include TLSv1, TLSv1.1, TLSv1.2, SSL, and None. By default, None is selected.
¡ Username: Username used for connection to the mail server. The username must be a string of 1 to 128 characters.
¡ Password: Password used for connection to the mail server. The password must be a string of 1 to 64 characters.
¡ Sender's Mail Address: Mail address of the sender. The address must be a string of 1 to 255 characters.
Figure 128 Mail server settings
Add scheduled reports
1. Navigate to the Analytics > Report > Report Task > Periodic Report List page.
2. Configure the following parameters as needed:
¡ Template Name: Click the Select Report Template button on the right of this parameter, and then select a predefined report template. This parameter is required.
¡ Report Name: Name of the scheduled report. The name must be a string of 1 to 64 characters that contain Chinese characters, English letters, digits, parentheses, hyphens, or underscores. This parameter is required.
¡ Schedule Type: This parameter is required. Options include Daily, Weekly, Monthly, Quarterly, Half-Yearly, and Yearly. You can select only one of them. The schedule type is Daily.
¡ Schedule Start Date: Date when the scheduled report starts. This parameter is required.
¡ Expire At: Date when the scheduled report expires.
¡ Report Format: Format of the report. Options include XLSX, PDF, XLS, and DOCX. You can select only one of them.
¡ Mail Address: Destination mail addresses. A mail address must be a string of 1 to 255 characters and you can add up to 10 mail addresses. This parameter is optional.
¡ Select Resource Groups: The Analytics component does require this parameter.
Figure 129 Adding a scheduled report 1
Figure 130 Adding a scheduled report 2
View the configuration results
Navigate to the Analytics > Report > Report Template > Report Template List page, and then select a report template to view report data.
Figure 131 NE report
Figure 132 IGP link traffic report
Figure 133 NetStream report
RIR log analysis
The analyzer performs analysis for scheduling information reported through the flow log mechanism, and locates the link scheduling reasons. You can display event type distribution, top 10 scheduling event types, and top 10 inter-site scheduling events within the specified time range. Supported event types include link failure, quality change, bandwidth change, configuration change, and optimization. You can select an event type to view the scheduling details.
Configuration workflow
Figure 134 Configuration workflow
Network planning
Procedure
Configure network devices as required. As a best practice, configure all devices. The following uses Hub1 as an example.
Configure device settings
[Hub1]rir sdwan
[Hub1-rir sdwan]log enable
[Hub1-rir sdwan]quit
[Hub1]userlog flow export source-ip 30.1.1.1 //IP address for device incorporation that is typically a loopback interface address.
[Hub1]userlog flow export host 3.2.139.233 port 9998 //Southbound passive collection IP address.
[Hub1] grpc enable
[Hub1] telemetry
[Hub1-telemetry] sensor-group TunnelQuality
[Hub1-telemetry-sensor-group-TunnelQuality] sensor path rir/sdwanlinkqualities/sdwanlinkquality/peerttes/peertte/results/result //Collect SDWAN quality information.
[Hub1-telemetry] destination-group sa
[Hub1-telemetry-destination-group-sa] ipv4-address 3.2.139.233 //Southbound passive collection IP address.
[Hub1-telemetry] subscription sa
[Hub1-telemetry-subscription-sa] sensor-group TunnelQuality sample-interval 60
// As a best practice, set the interval to 60s.
[Hub1-telemetry-subscription-sa] source-address interface loopback0
[Hub1-telemetry-subscription-sa] destination-group sa
Configure collection settings
NAT collection
The NTA collection and analysis component is enabled by default.
NETCONF collection
NETCONF collection tasks are enabled by default. In the NETCONF collection template, select the Ifmgr_Interfaces, SDWAN_SdwanTteConnections, and SDWAN_SdwanSiteTte indexes.
Configure analysis task settings
Configure the RIR log bulk analysis task
Navigate to the Analytics > Analysis Options > Task Management page to start the RIR log bulk analysis task, as shown in Figure 135.
Figure 135 RIR scheduling log bulk analysis task
Configure the SDWAN tunnel analysis task
Navigate to the Analytics > Analysis Options > Task Management page to start the SDWAN tunnel analysis task, as shown in Figure 136.
Figure 136 SDWAN tunnel analysis task
Configure application group settings
|
|
NOTE: The analyzer can obtain application group and link information through the controller, and automatically match the application groups defined in the controller. |
For more information, see the application group configuration section in the most recent configuration guide of the controller.
Display the result
Navigate to the Analytics > Health Analysis > Application Analysis > RIR page to display event type distribution, top 10 scheduling event types, top 10 inter-site scheduling events, and details before and after link selection, as shown in Figure 137 and Figure 138.
UserLog flow analysis
This function collects the session logs of all devices, displays the application and traffic information, and monitors and analyzes UserLog flows.
Configuration workflow
Figure 139 Configuration workflow
Network planning
See "Network diagram."
Restrictions and guidelines
Configure NAT rules as needed. The analyzer only collects NAT logs.
Procedure
Configure devices as needed. As a best practice, configure all devices. This section takes device Hub1 as an example. The configuration is as follows.
Configure devices
[Hub1]nat log enable
[Hub1]nat log flow-active 10
[Hub1]nat log flow-begin
[Hub1]nat log flow-end
[Hub1]userlog flow export version 3
[Hub1]userlog flow export source-ip 30.1.1.1 //IP address of the loopback interface
[Hub1]userlog flow export host 3.2.139.233 port 9998 //Southbound passive collection IP address
[Hub1]acl advanced 3333 //As a best practice, deny the IP addresses that do not require NAT such as the IP address of the tunnel interface, IP address of the VSI interface, and IP address of the WAN interface.
[Hub1-acl-ipv4-adv-3333]rule 0 deny ip source 40.1.1.0 0.0.0.255
[Hub1-acl-ipv4-adv-3333]rule 5 permit ip
[Hub1-acl-ipv4-adv-3333]exit
[Hub1]interface GigabitEthernet3/0
[Hub1-GigabitEthernet3/0]nat outbound 3333
Configure collection settings
The NAT data collection task is enabled by default.
Configure UserLog analysis tasks
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Start the UserLog analysis task, as shown in Figure 140.
Figure 140 Starting the UserLog analysis task
Display the result
Navigate to the Analytics > Health Analysis > Application Analysis > UserLog Flow Analysis page to display the session log list. Click a log entry to display the 5-tuple list, and click a 5-tuple entry to access the UserLog details page.
Figure 141 Session log list
URL audit
URL audit monitors user access URLs by collecting and analyzing log information from network devices to regulate network behaviors. The network devices refer to the routers that are configured with URL filtering policies. This feature can monitor only HTTP URLs.
Configuration workflow
Figure 142 Configuration workflow
Network planning
See "Network diagram."
Restrictions and guidelines
The analyzer does not define URL filtering rules. You need to configure URL filtering rules as required. For the analyzer to perform URL audit, you must specify logging as the default action of the URL filtering policies for the device to generate URL filtering logs. In addition, URL audit requires a license. URL audit is optional if a network behavior manager exists.
Procedure
Configure network devices as required. As a best practice, configure all devices. The following uses Hub1 as an example.
Configure EIA settings
For information about how to configure EIA settings, see Generic 802.1X Authentication with EIA Configuration Examples.
Configure device settings
[Hub1] object-policy ip Any-Any
[Hub1-object-policy-ip-Any-Any]rule 0 inspect policy
[Hub1-object-policy-ip-Any-Any]rule 65533 inspect 8048_url_profile_global disable
[Hub1-object-policy-ip-Any-Any]rule 65534 pass
[Hub1]quit
[Hub1]security-zone intra-zone default permit
[Hub1]security-zone name Trust
[Hub1-security-zone-Trust]import interface GigabitEthernet0/3 //LAN interface.
[Hub1-security-zone-Trust]import interface Vsi-interface10 //Tunnel interface.
[Hub1]quit
[Hub1]security-zone name Untrust
[Hub1-security-zone-Untrust]import interface GigabitEthernet0/0 //WAN interface, configured based on network planning.
[Hub1-security-zone-Untrust]quit
[Hub1]zone-pair security source Any destination Any
[Hub1-zone-pair-security-Any-Any]object-policy apply ip Any-Any
[Hub1-zone-pair-security-Any-Any]quit
[Hub1]url-filter policy policy
[Hub1-url-filter-policy-policy]default-action permit logging
[Hub1-url-filter-policy-policy]exit
[Hub1]app-profile policy
[Hub1-app-profile-policy]url-filter apply policy policy
[Hub1-app-profile-policy]quit
[Hub1]info-center enable
[Hub1]info-center loghost source loopback0
[Hub1]info-center loghost 3.2.139.233 //Southbound passive collection IP address.
Configure collection settings
Navigate to Analytics > Analysis Options > Resources > Assets, select devices, click SYSLOG, and then select Enable.
The SYSLOG collection and analysis component is enabled by default.
Configure analysis task settings
Navigate to Analytics > Analysis Options > Task Management to start the URL audit analysis task, as shown in Figure 143.
Figure 143 URL audit log analysis task
Display the result
Navigate to Analytics > Health Analysis > Application Analysis > URL Audit to display the URL access list. On this page, you can perform the following operations:
· Click a device IP to display domain names and number of accesses.
· Click an entry in the Domain Name column to display source IP addresses and number of accesses
· Click an entry in the Username column to display URL access details.
Figure 144 URL access list
Audio and video quality analysis
This function monitors the quality of audio & video traffic on network devices such as clients, servers, and media gateways, and proactively detects problems such as frequent packet drops and increased jitters on devices based on indexes such as device health. This function enables administrators to take effective measures to ensure the quality of audio & video traffic, such as by expanding the network or contacting the audio and video solution providers for help.
|
|
NOTE: This function does not support analyzing encrypted SIP or H.323 packets. |
Configuration workflow
Figure 145 Configuration workflow
Network planning
See "Network diagram."
Restrictions and guidelines
To perform audio and video analysis, make sure the device supports audio and video configuration. Determine whether to configure gRPC according to the CPU usage. Configuring gRPC will cause the CPU usage by 5%.
Only certain router models and versions support the audio and video quality analysis function in a WAN scenario. Before using this function, contact the solution and product personnel to identify whether your devices support it.
Procedure
Configure devices
# Configure SQA and eMDI.
[Hub1 Sqa // Enter SQA view.
[Hub1-sqa] sqa-sip enable // Enable SIP-based SQA.
[Hub1-sqa] sqa-h323 enable // Enable H.323-based SQA.
[Hub1-sqa] exit
[Hub1 emdi
[Hub1-emdi] exit
# Configure gRPC.
|
|
IMPORTANT: Determine whether to configure gRPC according to the CPU usage. Configuring gRPC will cause the CPU usage by 5%. |
[Hub1] grpc enable
[Hub1] telemetry
[Hub1-telemetry] sensor-group sqa
[Hub1-telemetry-sensor-group-sqa] sensor path sqa/bidirectionalcallevent
[Hub1-telemetry-sensor-group-sqa] sensor path sqa/callevent
[Hub1-telemetry-sensor-group-sqa] sensor path sqa/calltrafficevent
[Hub1-telemetry-sensor-group-sqa] exit
[Hub1-telemetry] destination-group sqa
[Hub1-telemetry-destination-group-sqa] ipv4-address 3.2.139.233 // Southbound passive collection IP address
[Hub1-telemetry] subscription sqa
[Hub1-telemetry-subscription-sqa] sensor-group sqa sample-interval 60
Configure analysis tasks
Configure the audio and video quality analysis task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Start the VideoQualityAnalysis analysis task, as shown in Figure 146.
Figure 146 Starting the VideoQualityAnalysis analysis task
Configure the IfKpiAnalysis analysis task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Start the IfKpiAnalysis analysis task, as shown in Figure 147.
Figure 147 IfKpiAnalysis analysis task
Configure the NodeKpiAnalysis analysis task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Start the NodeKpiAnalysis analysis task, as shown in Figure 148.
Figure 148 NodeKpiAnalysis analysis task
Display the result
Navigate to the Analytics > Health Analysis > Application Analysis > Audio and Video Analysis page to display the MOS distribution, session statistics, traffic trend, and session list.
Figure 149 Audio and video analysis
Parent-child QoS policy queue statistics
Parent-child policy queue is an implementation of QoS that divides network traffic into multiple priority queues, allowing different policies and priorities to be applied to each queue. For a parent policy queue, you can set the overall bandwidth allocation policy and assign bandwidth ratios to the child policy queues. Child policy queues are used for fine-grained priority and bandwidth control based on specific applications, service types, or traffic.
Configuration workflow
Figure 150 Configuration workflow
Network planning
See “Network diagram.”
Procedure
Configure devices
Configure NETCONF
See “Configure NETCONF.”
Configure gRPC
|
|
CAUTION: · When the analyzer uses an IPv6 address to incorporate the device, the source address in the gRPC configuration must be the IPv6 address of the incorporated device. When the analyzer uses an IPv4 address to incorporate the device, enter the interface name. · You can use either NETCONF collection or gRPC collection, but not both. If you configure NETCONF collection for parent-child QoS policy queues on the analyzer, do not configure gRPC collection on the device, and vice versa. |
# Configure a sensor path. The configuration is performed on PE1.
[PE1] grpc enable
[PE1] telemetry
[PE1-telemetry] sensor-group qos_policy
[PE1-telemetry-sensor-group-qos_policy] sensor path lr/interfaces
[PE1-telemetry-sensor-group-qos_policy] sensor path mqc/gts
[PE1-telemetry-sensor-group-qos_policy] sensor path mqc/ifcategorypolicyrun/application/nestpolicyl1/application/nestpolicyl2/application
[PE1-telemetry] destination-group sa
[PE1-telemetry-destination-group-sa] ipv4-address 3.2.139.233 port 50051
//The IP address is the southbound passive collection IP, and the port number is fixed at 50051.
[PE1-telemetry] subscription sa
[PE1-telemetry-subscription-sa] sensor-group ifmgr sample-interval 300
//The minimum sampling interval allowed is 5 seconds. A smaller sampling interval consumes more CPU resources. Set the sampling interval according to the actual device conditions. Typically, set the sampling interval to 300 seconds as a best practice.
[PE1-telemetry-subscription-sa] source-address interface loopback0 //The source interface is a loopback interface corresponding to the IP address incorporated by the analyzer
[PE1-telemetry-subscription-sa] destination-group sa
Configuring collection settings
NETCONF collection
See “Configure NETCONF collection." Make sure to select the LR_Interfaces, MQC_GTS, and MQC_IfCategoryPolicyRun collection metrics.
gRPC collection
The gRPC collection tasks are enabled by default.
Configure analysis tasks
Configure the IfKpiAnalysis analysis task
1. Navigate to the Analysis > Analysis Options > Task Management page.
2. Start the IfKpiAnalysis parsing task.
Figure 151 Configuring an IfKpiAnalysis analysis task
Configure the NodeKpiAnalysis analysis task
1. Navigate to the Analytics > Analysis Options > Task Management page.
2. Start the NodeKpiAnalysis analysis task.
Figure 152 NodeKpiAnalysis analysis task
Configure the HealthAnalysis analysis task
1. Navigate to the Analysis > Analysis Options > Task Management page.
2. Start the HealthAnalysis analysis task.
Figure 153 HealthAnalysis analysis task
Configure BufferMonitorAnalysis task
1. Navigate to the Analysis > Analysis Options > Task Management page.
2. Start the BufferMonitorAnalysis task.
Figure 154 Configure the BufferMonitorAnalysis task
Configure DeviceResource analysis task
1. Navigate to the Analysis > Analysis Options > Task Management page.
2. Start the DeviceResource analysis task.
Figure 155 DeviceResource analysis task
Display the result
Navigate to the Analytics > Health Analysis > Network Health > Queue page. This page displays the parent-child QoS policy queue statistics in a specific time span.
Figure 156 QoS queue statistics
Figure 157 QoS queue statistics data trend graphs
