Aruba JL849AAE Configuration Guide

IMC Orchestrator 6.2

IMC Analyzer Configuration Guide

The information in this document is subject to change without notice.

i 
Contents 
Overview ························································································1 
Terms ········································································································································ 1 
Networking ································································································································· 2 
Network topology ························································································································· 3 
Data collection-to-parsing task mappings ·························································································· 7 
Configure basic network settings ·························································9 
Deployment workflow ···················································································································· 9 
Network topology ························································································································· 9 
Procedure ··································································································································· 9 
Configure network devices ······································································································ 9 
Add network assets ············································································································· 16 
Configure protocol templates ································································································· 20 
Set the protocols ················································································································· 24 
Configure network health ································································· 28 
Deployment workflow ·················································································································· 28 
Network topology ······················································································································· 28 
Procedure ································································································································· 28 
Configure basic network settings ···························································································· 28 
Start parsing tasks on the controller ························································································ 28 
Display analysis results ········································································································ 31 
Restrictions and guidelines ·········································································································· 31 
Configure health summary ······························································· 32 
Deployment workflow ·················································································································· 32 
Network topology ······················································································································· 32 
Procedure ································································································································· 32 
Configure basic network settings ···························································································· 32 
Start parsing tasks on the controller ························································································ 32 
Obtain topology ··················································································································· 32 
Configure traffic heatmap ······································································································ 33 
Display analysis results ········································································································ 34 
Restrictions and guidelines ·········································································································· 34 
Configure packet loss analysis ·························································· 35 
Deployment workflow ·················································································································· 35 
Network topology ······················································································································· 35 
Procedure ································································································································· 35 
Configure basic network settings ···························································································· 35 
Configure device settings ······································································································ 35 
Configure applications ·········································································································· 37 
Start parsing tasks on the controller ························································································ 37 
Display analysis results ········································································································ 37 
Restrictions and guidelines ·········································································································· 38 
Configure change analysis ······························································· 39 
Deployment workflow ·················································································································· 39 
Network topology ······················································································································· 39 
Procedure ································································································································· 39 
Configure basic network settings ···························································································· 39 
Start parsing tasks on the controller ························································································ 39 
Display analysis results ········································································································ 40 
Restrictions and guidelines ·········································································································· 40 
Configure issue center (problem center) ·············································· 41 
Deployment workflow ·················································································································· 41 

ii 
Network topology ······················································································································· 41 
Procedure ································································································································· 41 
Configure network devices ···································································································· 41 
Manage assets ··················································································································· 41 
Start parsing tasks on the controller ························································································ 42 
Display analysis results ········································································································ 42 
Restrictions and guidelines ·········································································································· 43 
Configure switch logins ···································································· 44 
Deployment workflow ·················································································································· 44 
Network topology ······················································································································· 44 
Procedure ································································································································· 44 
Configure network devices ···································································································· 44 
Manage assets ··················································································································· 44 
Add a widget ······················································································································ 45 
Display analysis results ········································································································ 45 
Restrictions and guidelines ·········································································································· 46 
Configure intent verification ······························································ 47 
Deployment workflow ·················································································································· 47 
Network topology ······················································································································· 47 
Procedure ································································································································· 47 
Configure network devices ···································································································· 47 
Manage assets ··················································································································· 47 
Configure intent verification settings ························································································ 48 
Display intent verification result ······························································································ 49 
Restrictions and guidelines ·········································································································· 50 
Configure TCP flow analysis ····························································· 51 
Deployment workflow ·················································································································· 51 
Network topology ······················································································································· 51 
Procedure ································································································································· 51 
Configure device settings ······································································································ 51 
Configure collector settings ··································································································· 55 
Configure flow analysis ········································································································· 56 
Start the parsing task ··········································································································· 57 
Display the result ················································································································· 57 
Restrictions and guidelines ·········································································································· 58 
Configure illegal analysis ································································· 59 
Deployment workflow ·················································································································· 59 
Network topology ······················································································································· 59 
Procedure ································································································································· 59 
Configure device settings ······································································································ 59 
Configure collector settings ··································································································· 59 
Configure flow analysis ········································································································· 59 
Configure parsing tasks ········································································································ 61 
Display the result ················································································································· 62 
Restrictions and guidelines ·········································································································· 62 
Configure issue analysis ·································································· 63 
Deployment workflow ·················································································································· 63 
Network issue workflow ········································································································ 63 
Applications issue workflow ··································································································· 63 
Network topology ······················································································································· 63 
Procedure ································································································································· 63 
Configure network issues ······································································································ 63 
Configure application issues ·································································································· 63 
Display the result ················································································································· 63 
Restrictions and guidelines ·········································································································· 64 

iii 
Configure UDP flow analysis····························································· 65 
Deployment workflow ·················································································································· 65 
Network topology ······················································································································· 65 
Procedure ································································································································· 65 
Configure device settings ······································································································ 65 
Configure collector settings ··································································································· 65 
Configure flow analysis ········································································································· 65 
Configure parsing tasks ········································································································ 65 
Display the result ················································································································· 65 
Restrictions and guidelines ·········································································································· 66 
Configure INT flow analysis ······························································ 67 
Deployment workflow ·················································································································· 67 
Network topology ······················································································································· 67 
Procedure ································································································································· 67 
Configure INT settings on the device ······················································································· 67 
Configure collector settings ··································································································· 72 
Configure applications ·········································································································· 72 
Configure parsing tasks ········································································································ 72 
Display the result ················································································································· 72 
Restrictions and guidelines ·········································································································· 73 
Configure intelligent prediction ·························································· 74 
Deployment workflow ·················································································································· 74 
Network topology ······················································································································· 74 
Procedure ································································································································· 74 
Configure basic network settings ···························································································· 74 
Start parsing tasks on the controller ························································································ 74 
Enable AI prediction ············································································································· 74 
Display the result ················································································································· 75 
Restrictions and guidelines ·········································································································· 75 
Configure health report ···································································· 76 
Deployment workflow ·················································································································· 76 
Network topology ······················································································································· 76 
Procedure ································································································································· 76 
Configure mail server settings ································································································ 76 
Create a network-wide health report task ················································································· 77 
Immediately generate a health report ······················································································ 78 
Display the result ················································································································· 79 
Restrictions and guidelines ·········································································································· 80 
Configure RoCE network analysis ······················································ 81 
Deployment workflow ·················································································································· 81 
Network topology ······················································································································· 81 
Procedure ································································································································· 81 
Configure switch settings ······································································································ 81 
Configure RoCE server settings ····························································································· 84 
Configure RoCE-associated parsing tasks ··············································································· 88 
Configure server and cluster settings for RoCE network analysis ·················································· 88 
Display the result ················································································································· 89 
Restrictions and guidelines ·········································································································· 90 
FAQ ···························································································· 91 
 

1

Overview

HPE IMC Orchestrator Analyzer focuses on digging the values in machine data. Based on the big

data technology, IMC Orchestrator Analyzer 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. IMC Orchestrator

Analyzer 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.

IMC Orchestrator Analyzer supports data analysis for DC scenario. IMC Orchestrator Analyzer

analyzes network device running data, network service application traffic data, and user access and

network usage data.

IMC Orchestrator Analyzer in the DC scenario is designed to ensure high availability and low latency

for the DC network. Through all-time full data collection for network device running information, IMC

Orchestrator Analyzer establishes a network-wide health assessment system, and supports

TCP/UDP session analysis, application visibility and analysis, chip-level buffer monitoring, and

packet loss analysis. IMC Orchestrator Analyzer provides full support and assurance for DC network

O&M.

Terms

Table 1 Terms

Term

Definition

SNMP

Simple Network Management Protocol (SNMP), which is used to remotely manage

and operate network devices.

NETCONF

Network Configuration Protocol (NETCONF), which is used to configure and

manage network devices and supports programming.

NetStream

NetStream is a stream-based statistics method, and is used to collect and analyze

statistics of service traffic in the network.

ERSPAN

Layer 3 remote port mirroring. ERSPAN encapsulates traffic in GRE packets with

protocol number 0x88BE and routes the traffic to a remote monitoring device for

data monitoring.

Syslog

Syslog protocol, which is used to record system log messages.

Telemetry

Telemetry stream is a network monitoring technology that collects data from

devices, and is used to report data to collectors.

gRPC

Google Remote Procedure Call (gRPC), which is used to configure and manage

devices and supports programming through multiple languages.

INT

In-Band Telemetry, a network monitoring technology that collects data from

devices and reports collected data to collectors. The collectors analyze the

received collected data, and monitor the network device performance and network

running conditions.

TCB

Transient Capture Buffer (TCB), a technology that monitors lost packets of queues

through memory management units (MMUs).

MOD

Mirror On Drop (MOD), which detects the packets dropped during the forwarding

process in the device.

DRNI

Distributed Resilient Network Interconnect (DRNI) is a cross-device link

aggregation technology. It aggregates two physical devices on the aggregation

layer into one device to provide device-level redundancy protection and load

2

Term

Definition

sharing.

PFC

Priority-based flow control (PFC) is a granular traffic control mechanism. It can

meet the requirements for no packet loss in Ethernet traffic transmission and

provide the lossless service through Ethernet.

ECN

RFC 2481 defines an end-to-end congestion notification mechanism. The ECN

feature uses the DS fields in IP headers to mark the congestion state for packets

along the transmission path. An endpoint that supports this function can identify

whether congestion occurs on the transmission path through packet contents and

adjust the packet sending method accordingly to avoid deteriorating congestion.

RoCE

RDMA over Converged Ethernet (RoCE), a network protocol that allows Ethernet

to use Remote Direct Memory Access (RDMA).

Networking

WARNING!

The networking solution in this document uses the southbound single stack, and the collection

network uses the IPv4 protocol.

• Northbound network—Northbound service virtual IP set in the IMC PLAT. The IP address is

used by the cluster to provide external services.

• Southbound network—Network used by the analyzer's collection component or an

independent collector to receive collected 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

system share the network of the IMC PLAT, and no additional network is created.

 Southbound single stack—In this networking solution, the data collection system uses a

separate network, which can use the IPv4 or IPv6 network.

 Southbound dual stack—In this networking solution, the data collection system uses a

separate network, which must be configured with both IPv4 and IPv6 addresses.

3

Network topology

Figure 1 Network diagram

• The southbound network and northbound network of IMC Orchestrator Analyzer are

separated. The southbound network can be on the same subnet as the device management

interfaces or on a different subnet from the device management interfaces.

• Traffic of ERSPAN, INT, and telemetry stream is sent to the collector NICs through in-band

service interfaces.

• Leaf nodes and border nodes use DRNI to avoid single point of failure. On this network, the

keepalive links of the DR systems reuse the device management network addresses. For

actual networks, allocate addressees as needed.

• The collectors are used to collect traffic of ERSPAN, INT, and telemetry stream. As a best

practice, use the HPELinux operating system and make sure collector NICs support DPDK.

For common NICs that support DPDK, see HPE IMC Orchestrator Analyzer Installation and

Deployment Guide.

Table 2 Device and server interface IP address details

Device

Interface

IP address

Remarks

Northbound

VIP of the IMC

PLAT

\

192.168.10.100

Northbound VIP of the

cluster

Southbound

passive

collection IP

address of IMC

Orchestrator

Analyzer

\

192.168.11.100

Southbound passive

collection VIP

4

Device

Interface

IP address

Remarks

Southbound

active

collection IP

address of IMC

Orchestrator

Analyzer

\

192.168.11.104

Southbound active

collection VIP

SA001

ethipv4 (connecting to MGT)

192.168.10.3

Northbound network

address of node 1

enp61s0f0 (connecting to MGT)

192.168.11.101

Southbound passive

collection pod address of

node 1

enp61s0f0 (connecting to MGT)

192.168.11.105

Southbound active

collection pod address of

node 1

SA002

ethipv4 (connecting to MGT)

192.168.10.4

Northbound network

address of node 2

enp61s0f0 (connecting to MGT)

192.168.11.102

Southbound passive

collection pod address of

node 2

enp61s0f0 (connecting to MGT)

192.168.11.106

Southbound active

collection pod address of

node 2

SA003

ethipv4 (connecting to MGT)

192.168.10.5

Northbound network

address of node 3

enp61s0f0 (connecting to MGT)

192.168.11.103

Southbound passive

collection pod address of

node 3

enp61s0f0 (connecting to MGT)

192.168.11.107

Southbound active

collection pod address of

node 3

Collector

enp61s0f0 (connecting to MGT)

192.168.10.101

Collector management IP

enp61s0f3 (connecting to leaf1-

WGE1/0/11)

11.1.1.3

Collection NIC address of

the collector

\

11.1.1.2

Floating IP address of the

collector

Management

switch

MGT

vlan-int10

192.168.10.1

Gateway of the analyzer's

northbound network

vlan-int11

192.168.11.1

Gateway of the analyzer's

southbound network

vlan-int21

192.168.21.1

Gateway of the controller

container network

leaf1

MGE0/0/0

192.168.21.3

Device management

address

WGE1/0/1 (connecting to spine1:

WGE1/0/1)

192.168.120.2

Underlay interface address

WGE1/0/11 (connecting to spine2:

WGE1/0/11)

192.168.122.2

Underlay interface address

WGE1/0/21 (connecting to leaf2:

WGE1/0/21)

Int-Vlan4094

69.1.1.11

IPL interface

5

Device

Interface

IP address

Remarks

WGE1/0/31 (connecting to the

collector)

11.1.1.1

Collection NIC

interconnection address of

the collector

Loop0

2.1.1.11

Loopback interface

address

Loop1

3.1.1.11

Loopback interface

address, DRNI group

address

Leaf2

MGE0/0/0

192.168.21.4

Device management

address

WGE1/0/1 (connecting to spine1:

WGE1/0/2)

192.168.220.2

Underlay interface address

WGE1/0/11 (connecting to spine2:

WGE1/0/12)

192.168.222.2

Underlay interface address

WGE1/0/21 (connecting to leaf1:

WGE1/0/21)

Int-Vlan4094

69.1.1.111

IPL interface

Loop0

2.1.1.111

Loopback interface

address

Loop1

3.1.1.11

Loopback interface

address, DRNI group

address

Leaf3

MGE0/0/0

192.168.21.5

Device management

address

WGE1/0/1 (connecting to spine1:

WGE1/0/3)

192.168.121.2

Underlay interface address

WGE1/0/11 (connecting to spine2:

WGE1/0/13)

192.168.123.2

Underlay interface address

WGE1/0/21 (connecting to leaf4:

WGE1/0/21)

Int-Vlan4094

68.1.1.3

IPL interface

Loop0

2.1.1.22

Loopback interface

address

Loop1

3.1.1.111

Loopback interface

address, DRNI group

address

Leaf4

MGE0/0/0

192.168.21.6

Device management

address

WGE1/0/1 (connecting to spine1:

WGE1/0/4)

192.168.221.2

Underlay interface address

WGE1/0/11 (connecting to spine2:

WGE1/0/14)

192.168.223.2

Underlay interface address

WGE1/0/21 (connecting to leaf4:

WGE1/0/21)

Int-Vlan4094

68.1.1.4

IPL interface

Loop0

2.1.1.222

Loopback interface

address

Loop1

3.1.1.111

Loopback interface

address, DRNI group

address

6

Device

Interface

IP address

Remarks

Border1

MGE0/0/0

192.168.21.7

Device management

address

WGE1/0/1 (connecting to spine1:

WGE1/0/5)

192.168.124.2

Underlay interface address

WGE1/0/11 (connecting to spine2:

WGE1/0/15)

192.168.125.2

Underlay interface address

WGE1/0/21 (connecting to boarder2:

WGE1/0/21)

Int-Vlan4094

70.1.1.1

IPL interface

Loop0

2.1.1.21

Loopback interface

address

Loop1

3.1.1.211

Loopback interface

address, DRNI group

address

Border2

MGE0/0/0

192.168.21.8

Device management

address

WGE1/0/1 (connecting to spine1:

WGE1/0/6)

192.168.224.2

Underlay interface address

WGE1/0/11 (connecting to spine2:

WGE1/0/16)

192.168.225.2

Underlay interface address

WGE1/0/21 (connecting to boarder1:

WGE1/0/21)

Int-Vlan4094

70.1.1.2

IPL interface

Loop0

2.1.1.21

Loopback interface

address

Loop1

3.1.1.211

Loopback interface

address, DRNI group

address

Spine1

MGE0/0/0

192.168.21.9

Device management

address

WGE1/0/1 (connecting to leaf1:

WGE1/0/1)

192.168.120.1

Underlay interface address

WGE1/0/2 (connecting to leaf2:

WGE1/0/1)

192.168.220.1

Underlay interface address

WGE1/0/3 (connecting to leaf3:

WGE1/0/1)

192.168.121.1

Underlay interface address

WGE1/0/4 (connecting to leaf4:

WGE1/0/1)

192.168.221.1

Underlay interface address

WGE1/0/5 (connecting to boarder1:

WGE1/0/1)

192.168.124.1

Underlay interface address

WGE1/0/6 (connecting to boarder2:

WGE1/0/1)

192.168.224.1

Underlay interface address

Loop0

2.1.1.10

Loopback interface

address

Spine2

MGE0/0/0

192.168.21.10

Device management

address

WGE1/0/11 (connecting to leaf1:

WGE1/0/11)

192.168.122.1

Underlay interface address

7

Device

Interface

IP address

Remarks

WGE1/0/12 (connecting to leaf2:

WGE1/0/11)

192.168.222.1

Underlay interface address

WGE1/0/13 (connecting to leaf3:

WGE1/0/11)

192.168.123.1

Underlay interface address

WGE1/0/14 (connecting to leaf4:

WGE1/0/11)

192.168.223.1

Underlay interface address

WGE1/0/15 (connecting to boarder1:

WGE1/0/11)

192.168.125.1

Underlay interface address

WGE1/0/16 (connecting to boarder2:

WGE1/0/11)

192.168.225.1

Underlay interface address

Loop0

2.1.1.10

Loopback interface

address

IMPORTANT:

Use the same NIC for the southbound passive collection pod and southbound active collection

pod.

Data collection-to-parsing task mappings

WARNING!

A data collection task might correspond to multiple data parsing tasks. For how to configure each

type of data collection tasks and parsing tasks, see the configuration guide in each chapter.

Table 3 Data collection-to-parsing task mappings

Service

Data collection

Parsing task

Network health

SNMP collection

SNMP parsing

NETCONF collection

FlinkNetConf parsing

gRPC collection

grpcAnalysis parsing

Change analysis

NETCONF collection

FlinkNetConf parsing

Snmp-trap collection

SNMPTrap parsing

SNMP collection

SNMP parsing

gRPC collection

grpcAnalysis parsing

Packet loss analysis

gRPC collection

grpcAnalysis parsing

IfKpiAnalysis parsing

RoCE network analysis

NETCONF collection

FlinkNetConf parsing

gRPC collection

grpcAnalysis parsing

8

Service

Data collection

Parsing task

IfKpiAnalysis parsing

NodeKpiAnalysis parsing

Network events

Snmp-trap collection

SNMPTrap parsing

Intent verification

SNMP collection

SNMP parsing

gRPC collection

grpcAnalysis parsing

NETCONF collection

FlinkNetConf parsing

NETCONF parsing

Snmp-trap collection

SNMPTrap parsing

Issue center

SNMP collection

Issue center-related parsing tasks

SYSLOG collection

NETCONF collection

gRPC collection

Intelligent prediction

SNMP collection

SNMP parsing

INT analysis

INT collection

INT parsing

TCP flow analysis

ERSPAN or telemetry stream

TCP parsing

Noncompliance analysis

ERSPAN or telemetry stream

TCP parsing

Sysflood parsing

Illegal noncompliant traffic analysis

Application analysis

ERSPAN or telemetry stream

TCP parsing

Sysflood parsing

Illegal noncompliant traffic analysis

UDP flow analysis

ERSPAN or telemetry stream

TCP parsing

9

Configure basic network settings

Deployment workflow

Figure 2 Deployment workflow

Network topology

See "Network topology."

Procedure

Configure network devices

Configure routing

# Configure the static route from the network device to the southbound collection network of IMC

Orchestrator Analyzer. If the controller has deployed this route, skip this step.

#

ip route-static 192.168.11.0 24 192.168.21.1

#

Configure the log host

#

info-center loghost source MGE 0/0/0

info-center loghost 192.168.11.100 facility local5

#

Add network assetsConfigure network devices Set the protocols

Configure

routes,SNMP,NETCONF,SSH,

and local users

Add a NETCONF protocol

template

Configure protocol templates

Set Syslog

Set the SNMP template

Set the NETCONF template

End

Required sub-process

Required main process

Optional sub-process

Start

Configure the log host

Configure gRPC

Synchronize assets from the

controller

Manually and assets

Import assets from Excel

Import assets from the IMC

Platform

Add an SNMP protocol template

Add an SNMP collection template

Add a NETCONF collection

template

10

NOTE:

The IP address 192.168.11.100 here is the southbound passive collection VIP, which is the same

in the following configurations. You must first plan this IP address before deploying the

environment. In the actual network, use the allocated IP address for configuration.

Configure SNMP

#

snmp-agent

snmp-agent community write private

snmp-agent community read public

snmp-agent sys-info version v2c v3

snmp-agent target-host trap address udp-domain 192.168.11.100 params securitynam

e public v2c

snmp-agent trap enable arp

snmp-agent trap enable l2vpn

snmp-agent trap enable radius

snmp-agent trap enable stp

snmp-agent trap source M-GigabitEthernet0/0/0

#

Configure NETCONF

#

netconf soap http enable

netconf soap https enable

netconf ssh server enable

restful https enable

#

Configure SSH

#

ssh server enable

#

Configure a local user

# Configure the username and password as admin and Qwert@1234, respectively.

local-user hpe class manage

password simple Qwert@1234

service-type ftp

service-type telnet http https ssh

authorization-attribute user-role network-admin

authorization-attribute

user-role network-operator

line vty 0 63

authentication-mode scheme

user-role network-admin

user-role network-operator

#

11

NOTE:

When the underlay is not automatically deployed, the configurations in sections above in

"Configure network devices" must be manually deployed.

Configure gRPC

The controller supports deploying gRPC configuration. In the current software version, 46 sensor

paths can be deployed.

To configure gRPC:

1. Add collectors.

Navigate to the Analytics > Data Collection > Telemetry page. Add the following collectors:

 Add collector 1: Set the IP address to 192.168.11.100 (collector management IP) and port

number to 50051, which is used for gRPC collection.

 Add collector 2: Set the IP address to 11.1.1.3 (collection NIC address of the collector

rather than the management address of the collector) and port number to 5555. The

collector is used for ERSPAN, INT, or telemetry stream collection.

Figure 3 Adding the gRPC collector on the controller

2. Add a collection template.

Navigate to the Analytics > Data Collection > Telemetry > gRPC page. Click the

Collection Template tab, and click Edit. Select collection paths, and set the default push

interval to 30 seconds. You can edit the collection template as needed. As a best practice,

include at least collection paths for collecting the following information: device information,

interface information, error packet statistics, entry resources, and change analysis. Configure

other collection paths depending on your requirements and device support.

Figure 4 gRPC collection module

Manual device configuration example:

# Global configuration:

grpc enable //Enable gRPC

# Collection configuration:

telemetry //Enter telemetry view

12

sensor-group grp_RM3EK5C3ROSYRTT3M7V5SS2MCA // Create a sensor group

sensor path device/base //Add a sensor path

sensor path device/boards //Add a sensor path

destination-group grp_XRI7PLERR2WMZCXMVCTJFU2BCE//Create a destination group

ipv4-address 192.168.11.100 port 50051 //Add a collector using the specified

IP address and port number to the destination group

When you create subscriptions, data collection types include periodical and event-trigged:

Periodical data collection:

subscription grp_XRI7PLERR2WMZCXMVCTJFU2BCE//Create a subscription, and specify a

sensor group and destination group for the subscription

sensor-group grp_RM3EK5C3ROSYRTT3M7V5SS2MCA sample-interval 30 //Specify a

sensor group

source-address 192.168.21.3 //Specify a source IP address, which is the device

management IP

destination-group grp_XRI7PLERR2WMZCXMVCTJFU2BCE //Specify a destination group

Event-trigged data collection:

subscription grp_XRI7PLERR2WMZCXMVCTJFU2BCE//Create a subscription, and specify a

sensor group and destination group for the subscription

sensor-group grp_RM3EK5C3ROSYRTT3M7V5SS2MCA //Specify a sensor group. You do

not need to configure the data push interval for an event-triggered sensor group

source-address 192.168.21.3 //Specify a source IP address, which is the device

management IP

destination-group grp_XRI7PLERR2WMZCXMVCTJFU2BCE //Specify a destination group

When you use the controller to deploy configuration, follow these steps:

a. Click Edit.

b. Select the corresponding sensor paths, and click Save. For example:

13

c. Select sensor paths as needed.

Device information collection:

sensor path device/base //Used for collecting device

information

sensor path device/boards //Used for collecting device

information

sensor path device/extphysicalentities //Used for collecting device

information

sensor path device/physicalentities //Used for collecting device

information

sensor path device/transceivers //Used for collecting device

transceiver module information

Interface information collection:

sensor path ifmgr/ethportstatistics //Used for collecting device

interface statistics

sensor path ifmgr/interfaces //Used for collecting device

interface information

sensor path ifmgr/statistics //Used for collecting

device interface statistics

(Optional.) Device buffer monitoring information:

sensor path buffermonitor/bufferusages //Used for collecting

buffermonitor data

sensor path buffermonitor/commbufferusages //Used for collecting

buffermonitor data

sensor path buffermonitor/commheadroomusages //Used for collecting

buffermonitor data

sensor path buffermonitor/ecnandwredstatistics //Used for collecting

buffermonitor data

sensor path buffermonitor/egressdrops //Used for collecting buffermonitor

data

sensor path buffermonitor/ingressdrops //Used for collecting buffermonitor

data

sensor path buffermonitor/pfcspeeds //Used for collecting buffermonitor data

sensor path buffermonitor/pfcstatistics //Used for collecting buffermonitor

data

Error packet statistics collection:

14

sensor path ifmgr/ethportstatistics //Used for collecting CRC error packet

statistics

Entry resource collection:

sensor path resourcemonitor/monitors //Used for collecting entry

resources, which replaces NETCONF collection

sensor path resourcemonitor/resources //Used for collecting entry resources,

which replaces NETCONF collection

Change analysis collection:

sensor path route/ipv4routes //Used for collecting configuration change entries

sensor path route/ipv6routes //Used for collecting configuration change entries

sensor path lldp/lldpneighbors //Used for collecting configuration change

entries

sensor path mac/macunicasttable //Used for collecting configuration change

entries

sensor path arp/arptable //Used for collecting configuration change entries

sensor path nd/ndtable //Used for collecting configuration change entries

The following paths support incremental data reporting. (As a best practice, use incremental

data reporting.) For change analysis, you do not need to configure both full data reporting and

incremental data reporting for a sensor path. If you have configured incremental data

reporting for a sensor path, you do not need to configure full data reporting. Support for

sensor paths depends on the device model. As a best practice, configure the collection

interval as 3600 seconds.

sensor path arp event/arptableevent //Used for collecting configuration change

entries, incremental data reporting

sensor path mac/overlaymacevent //Used for collecting configuration change

entries, incremental data reporting

sensor path mac/underlaymacevent //Used for collecting configuration change

entries, incremental data reporting

sensor path nd/ndtableevent //Used for collecting configuration change entries,

incremental data reporting

sensor path route_stream/ipv4routeevent //Used for collecting configuration

change entries, incremental data reporting

sensor path route_stream/ipv6routeevent //Used for collecting configuration

change entries, incremental data reporting

(Optional.) Event-trigged data collection:

sensor path buffermonitor/portquedropevent //Queue packet drop alarm

sensor path buffermonitor/portqueoverrunevent //Queue threshold crossing alarm

sensor path tcb/tcbrawpacketinfoevent //TCB sensor path

sensor path telemetryftrace/genevent //MOD data sensor path

3. Configure VNI data collection.

VNI data collection settings cannot be deployed from the controller. Configure the settings

manually as needed.

#

telemetry

sensor-group vni

sensor path l2vpn/acs //AC statistics

sensor path l2vpn/vsis //VSI configuration

sensor path l2vpn/vsistatistics //VSI statistics

destination-group vni

ipv4-address 191.168.11.112 port 50051 vpn-instance mgmt

15

subscription vni

sensor-group vni sample-interval 600

destination-group vni

#

4. Add collected devices and associate them with collectors.

Navigate to the Analytics > Data Collection > Telemetry > gRPC page. Select the collected

devices, and click Add. On the page that opens, select collectors for the selected devices,

and click Apply to deploy the configuration to devices.

Figure 5 Adding collected devices and associate them with collectors

CAUTION:

• When you configure a destination group, the IP address is the southbound passive collection

VIP and the port number is 50051. If the interface connecting the device to IMC Orchestrator

Analyzer is bound to a VPN instance, you must specify the vpn-instance parameter after

the collector address of the destination group. Otherwise, you do not need to specify the

parameter.

• For non-event-triggered data collection, as a best practice, set the collection interval to one

minute. You can adjust the collection interval as needed according to the display accuracy

requirements.

Set the time zone and system time on the network device

1. Set the time zone.

# Set the name of the time zone to bj. Use the time zone of the controller as the time zone of

the network device.

[leaf1]clock timezone bj add 08:00:00

2. Set the system time.

# Set the system time to 14:53:00 2021/12/08.

[leaf1]clock protocol none

<leaf1> clock datetime 14:53:00 2021/12/08

3. Verify the time zone and system time settings.

# Display the system time and date when the time zone and system time are specified.

[leaf1]dis clock

16

14:53:13.271 bj Wed 12/08/2021

Time Zone : bj add 08:00:00

Add network assets

NOTE:

You can import assets in multiple methods, including synchronization from controller, manual

addition, import from Excel, and import from IMC PLAT. You can add network assets in one or

more of these methods.

Synchronize assets from the controller

1. To add a controller connection, navigate to the Analysis > Analysis Options > Resources >

Assets > Data Sources page, click Add, enter basic information on the page that opens, and

click OK.

 Name: Enter the name of a controller, a string of up to 36 characters.

 Type: Controller.

 Scene: DC.

 Username: Enter the administrator account admin. For more information, see the

controller deployment guide.

 Password: Enter the password Pwd@12345 for the administrator account admin.

 IP: Northbound service VIP.

 Port: Port number in the URL for logging into 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.

Page is loading ...

Aruba JL849AAE Configuration Guide

This manual is also suitable for

Aruba JL849AAE Configuration Guide