Aruba JL852AAE Configuration Guide

Brand: Aruba

Model: JL852AAE

Type: Configuration Guide

This manual is also suitable for

HPE IMC Orchestrator 6.3

IMC Analyzer Configuration Guide

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

i 
Contents 
Overview ························································································1 
Terms ········································································································································ 1 
Networking ································································································································· 2 
Network configuration ··················································································································· 2 
Configure basic network settings ·························································7 
Configuration workflow ·················································································································· 7 
Network configuration ··················································································································· 7 
Procedure ··································································································································· 7 
Configure network devices ······································································································ 7 
Add network assets ············································································································· 14 
Configure protocol templates ································································································· 18 
Set the protocols ················································································································· 22 
Configure network health ································································· 26 
Configuration workflow ················································································································ 26 
Network configuration ················································································································· 26 
Procedure ································································································································· 26 
Configure basic network settings ···························································································· 26 
Start parsing tasks on the analyzer ························································································· 26 
Verify the configuration ········································································································· 28 
Restrictions and guidelines ·········································································································· 30 
Configure health summary ······························································· 31 
Configuration workflow ················································································································ 31 
Network configuration ················································································································· 31 
Procedure ································································································································· 31 
Configure basic network settings ···························································································· 31 
Starting parsing tasks on the analyzer ····················································································· 31 
Obtain topology ··················································································································· 31 
Configure traffic heatmap ······································································································ 32 
Verify the configuration ········································································································· 33 
Restrictions and guidelines ·········································································································· 33 
Configure packet loss analysis ·························································· 34 
Configuration workflow ················································································································ 34 
Network diagram ························································································································ 34 
Procedure ································································································································· 34 
Configure basic network settings ···························································································· 34 
Configure device settings ······································································································ 35 
Configure applications ·········································································································· 36 
Start parsing tasks on the analyzer ························································································· 36 
Verify the configuration ········································································································· 36 
Restrictions and guidelines ·········································································································· 37 
Configure change analysis ······························································· 38 
Configuration workflow ················································································································ 38 
Network configuration ················································································································· 38 
Procedure ································································································································· 38 
Configure basic network settings ···························································································· 38 
Start parsing tasks on the analyzer ························································································· 38 
Verify the configuration ········································································································· 39 
Restrictions and guidelines ·········································································································· 39 
Configure issue center (problem center) ·············································· 40 
Configuration workflow ················································································································ 40 
Network configuration ················································································································· 40 

ii 
Procedure ································································································································· 40 
Configure network devices ···································································································· 40 
Manage assets ··················································································································· 40 
Start parsing tasks on the analyzer ························································································· 41 
Verify the configuration ········································································································· 41 
Restrictions and guidelines ·········································································································· 42 
Configure switch logins ···································································· 43 
Configuration workflow ················································································································ 43 
Network configuration ················································································································· 43 
Procedure ································································································································· 43 
Configure network devices ···································································································· 43 
Manage assets ··················································································································· 43 
Add a widget ······················································································································ 44 
Verify the configuration ········································································································· 44 
Restrictions and guidelines ·········································································································· 45 
Configure intent verification ······························································ 46 
Configuration workflow ················································································································ 46 
Network configuration ················································································································· 46 
Procedure ································································································································· 46 
Configure network devices ···································································································· 46 
Manage assets ··················································································································· 46 
Configure intent verification settings ························································································ 47 
Verify the configuration ········································································································· 48 
Restrictions and guidelines ·········································································································· 49 
Configure TCP flow analysis ····························································· 50 
Configuration workflow ················································································································ 50 
Network configuration ················································································································· 50 
Procedure ································································································································· 50 
Configure device settings ······································································································ 50 
Configure collector settings ··································································································· 54 
Configure flow analysis ········································································································· 55 
Start the parsing task ··········································································································· 56 
Verify the configuration ········································································································· 56 
Restrictions and guidelines ·········································································································· 58 
Configure illegal analysis ································································· 59 
Configuration workflow ················································································································ 59 
Network configuration ················································································································· 59 
Procedure ································································································································· 59 
Configure device settings ······································································································ 59 
Configure collector settings ··································································································· 59 
Configure flow analysis ········································································································· 59 
Configure parsing tasks ········································································································ 61 
Verify the configuration ········································································································· 62 
Restrictions and guidelines ·········································································································· 64 
Configure application health ····························································· 65 
Configuration workflow ················································································································ 65 
Network configuration ················································································································· 65 
Procedure ································································································································· 65 
Configure device settings ······································································································ 65 
Configure collector settings ··································································································· 65 
Configure settings on the application health page ······································································ 65 
Start parsing tasks ··············································································································· 65 
Verify the configuration ········································································································· 65 
Configure issue analysis ·································································· 67 
Configuration workflow ················································································································ 67 
Network issue workflow ········································································································ 67 

iii 
Applications issue workflow ··································································································· 67 
Network configuration ················································································································· 67 
Procedure ································································································································· 67 
Configure network issues ······································································································ 67 
Configure application issues ·································································································· 67 
Verify the configuration ········································································································· 67 
Restrictions and guidelines ·········································································································· 68 
Configure UDP flow analysis····························································· 69 
Configuration workflow ················································································································ 69 
Network configuration ················································································································· 69 
Procedure ································································································································· 69 
Configure device settings ······································································································ 69 
Configure collector settings ··································································································· 69 
Configure flow analysis ········································································································· 69 
Configure parsing tasks ········································································································ 69 
Verify the configuration ········································································································· 69 
Restrictions and guidelines ·········································································································· 70 
Configure INT flow analysis ······························································ 72 
Configuration workflow ················································································································ 72 
Network configuration ················································································································· 72 
Procedure ································································································································· 72 
Configure INT settings on the device ······················································································· 72 
Configure collector settings ··································································································· 77 
Configure applications ·········································································································· 77 
Configure parsing tasks ········································································································ 77 
Verify the configuration ········································································································· 77 
Restrictions and guidelines ·········································································································· 78 
Configure intelligent prediction ·························································· 80 
Configuration workflow ················································································································ 80 
Network configuration ················································································································· 80 
Procedure ································································································································· 80 
Configure basic network settings ···························································································· 80 
Starting parsing tasks on the analyzer ····················································································· 80 
Enabling AI prediction ·········································································································· 80 
Verify the configuration ········································································································· 81 
Restrictions and guidelines ·········································································································· 81 
Configure health report ···································································· 83 
Configuration workflow ················································································································ 83 
Network configuration ················································································································· 83 
Procedure ································································································································· 83 
Configure mail server settings ································································································ 83 
Create a network-wide health report task ················································································· 84 
Immediately generate a health report ······················································································ 85 
Verify the configuration ········································································································· 86 
Restrictions and guidelines ·········································································································· 87 
Configure link analysis ······································································0 
Configuration workflow ·················································································································· 0 
Network configuration ··················································································································· 0 
Procedure ··································································································································· 0 
Configure basic network settings ······························································································ 0 
Configure device settings ········································································································ 0 
Configure link settings ············································································································ 1 
Start parsing tasks for the analyzer ··························································································· 2 
Verify the configuration ··········································································································· 2 
Restrictions and guidelines ············································································································ 3 

iv 
Configure vSwitch health monitoring (OVS) ···········································4 
Configuration workflow ·················································································································· 4 
Network configuration ··················································································································· 4 
Procedure ··································································································································· 4 
Configure a data source for the controller ··················································································· 4 
Add vSwitch assets················································································································ 4 
Verify the configuration ··········································································································· 4 
Restrictions and guidelines ············································································································ 8 
FAQ ······························································································9 
 

Overview

Analyzer focuses on digging the values in machine data. Based on the big data technology,

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

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

access and network usage data.

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

sharing.

Term

Definition

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.

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.

Network configuration

• The southbound network and northbound network of 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 DRNI 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 operating system provided with IMC PLAT (of version earlier than E0707) and

make sure collector NICs support DPDK. For common NICs that support DPDK, see the

analyzer installation and deployment guide.

Figure 1 Network diagram

Table 2 Device and server interface IP address details

Device

Interface

IP address

Remarks

Northbound VIP of

the IMC PLAT

192.168.12.145

Northbound VIP of the

cluster

Southbound passive

collection IP address

of Analyzer

192.168.16.100

Southbound passive

collection VIP

Southbound active

collection IP address

of Analyzer

192.168.16.104

Southbound active

collection VIP

SA001

ethipv4 (connecting to MGT)

192.168.12.141

Northbound network

address of node 1

enp61s0f0 (connecting to MGT)

192.168.16.101

Southbound passive

collection pod address of

node 1

enp61s0f0 (connecting to MGT)

192.168.16.105

Southbound active

collection pod address of

node 1

SA002

ethipv4 (connecting to MGT)

192.168.12.142

Northbound network

address of node 2

enp61s0f0 (connecting to MGT)

192.168.16.102

Southbound passive

collection pod address of

node 2

enp61s0f0 (connecting to MGT)

192.168.16.106

Southbound active

collection pod address of

IMC PLAT

SA001 SA002 SA003

Controller Analyzer

Peer-Link

Peer-LinkPeer-Link

192.168.12.1 192.168.16.1

192.168.11.1

Management

switch Border1 Border2

Leaf1

Spine2

192.168.12.146

11.1.1.3 11.1.1.1 Leaf2 Leaf3 Leaf4

ServerServerServerServer

Collector

Device

Interface

IP address

Remarks

node 2

SA003

ethipv4 (connecting to MGT)

192.168.12.143

Northbound network

address of node 3

enp61s0f0 (connecting to MGT)

192.168.16.103

Southbound passive

collection pod address of

node 3

enp61s0f0 (connecting to MGT)

192.168.16.107

Southbound active

collection pod address of

node 3

Collector

enp61s0f0 (connecting to MGT)

192.168.12.146

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

Gateway of the analyzer's

northbound network

vlan-int11

192.168.16.1

Gateway of the analyzer's

southbound network

vlan-int21

192.168.11.1

Gateway of the device

management network

leaf1

MGE0/0/0

192.168.12.23

Device management

address

WGE1/0/1 (connecting to spine1:

WGE1/0/1)

10.1.1.2

Underlay interface

address

WGE1/0/11 (connecting to spine2:

WGE1/0/11)

10.2.1.2

Underlay interface

address

WGE1/0/21 (connecting to leaf2:

WGE1/0/21)

Int-Vlan4094

69.1.1.11

IPL interface

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

Device management

address

WGE1/0/1 (connecting to spine1:

WGE1/0/2)

10.1.2.2

Underlay interface

address

WGE1/0/11 (connecting to spine2:

WGE1/0/12)

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

Device

Interface

IP address

Remarks

Loop1

3.1.1.11

Loopback interface

address, DRNI group

address

Leaf3

MGE0/0/0

192.168.12.25

Device management

address

WGE1/0/1 (connecting to spine1:

WGE1/0/3)

10.1.3.2

Underlay interface

address

WGE1/0/11 (connecting to spine2:

WGE1/0/13)

10.2.3.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.12.26

Device management

address

WGE1/0/1 (connecting to spine1:

WGE1/0/4)

10.1.4.2

Underlay interface

address

WGE1/0/11 (connecting to spine2:

WGE1/0/14)

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

Border1

MGE0/0/0

192.168.12.27

Device management

address

WGE1/0/1 (connecting to spine1:

WGE1/0/5)

10.1.5.2

Underlay interface

address

WGE1/0/11 (connecting to spine2:

WGE1/0/15)

10.2.5.2

Underlay interface

address

WGE1/0/21 (connecting to board2:

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

Device management

address

WGE1/0/1 (connecting to spine1:

WGE1/0/6)

10.1.6.2

Underlay interface

address

Device

Interface

IP address

Remarks

WGE1/0/11 (connecting to spine2:

WGE1/0/16)

10.2.6.2

Underlay interface

address

WGE1/0/21 (connecting to board1:

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

Device management

address

WGE1/0/1 (connecting to leaf1:

WGE1/0/1)

10.1.1.1

Underlay interface

address

WGE1/0/2 (connecting to leaf2:

WGE1/0/1)

10.1.2.1

Underlay interface

address

WGE1/0/3 (connecting to leaf3:

WGE1/0/1)

10.1.3.1

Underlay interface

address

WGE1/0/4 (connecting to leaf4:

WGE1/0/1)

10.1.4.1

Underlay interface

address

WGE1/0/5 (connecting to board1:

WGE1/0/1)

10.1.5.1

Underlay interface

address

WGE1/0/6 (connecting to board2:

WGE1/0/1)

10.1.6.1

Underlay interface

address

Loop0

2.1.1.10

Loopback interface

address

Spine2

MGE0/0/0

192.168.12.30

Device management

address

WGE1/0/11 (connecting to leaf1:

WGE1/0/11)

10.2.1.1

Underlay interface

address

WGE1/0/12 (connecting to leaf2:

WGE1/0/11)

10.2.2.1

Underlay interface

address

WGE1/0/13 (connecting to leaf3:

WGE1/0/11)

10.2.3.1

Underlay interface

address

WGE1/0/14 (connecting to leaf4:

WGE1/0/11)

10.2.4.1

Underlay interface

address

WGE1/0/15 (connecting to board1:

WGE1/0/11)

10.2.5.1

Underlay interface

address

WGE1/0/16 (connecting to board2:

WGE1/0/11)

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

Configure basic network settings

Configuration workflow

Figure 2 Configuration workflow

Network configuration

See “Network configuration.”

Procedure

Configure network devices

Configure routing

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

analyzer. If the controller has deployed this route, skip this step.

[Device] ip route-static 192.168.16.0 24 192.168.11.1

Configure the log host

[Device] info-center loghost source MGE 0/0/0

[Device] info-center loghost 192.168.16.100 facility local5

NOTE:

The IP address 192.168.16.0 here is the southbound network address. The IP address

192.168.11.1 is the device management network gateway used for southbound communication

between the device management network and the controller. Configure the settings as needed.

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 PLAT

Add an SNMP protocol template

Add an SNMP collection template

Add a NETCONF collection

template

Configure SNMP

[Device] snmp-agent

[Device] snmp-agent community write private

[Device] snmp-agent community read public

[Device] snmp-agent sys-info version v2c v3

[Device] snmp-agent target-host trap address udp-domain 192.168.16.100 params securityname

[Device] public v2c

[Device] snmp-agent trap enable arp

[Device] snmp-agent trap enable l2vpn

[Device] snmp-agent trap enable radius

[Device] snmp-agent trap enable stp

[Device] snmp-agent trap source M-GigabitEthernet0/0/0

Configure NETCONF

netconf ssh server enable

Configure SSH

ssh server enable

Configure a local user

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

[Device]local-user admin class manage

[Device-luser-manage-admin] password simple Qwert@1234

[Device-luser-manage-admin] service-type ftp

[Device-luser-manage-admin] service-type telnet http https ssh

[Device-luser-manage-admin] authorization-attribute user-role network-admin

[Device-luser-manage-admin] authorization-attribute user-role network-operator

[Device-luser-manage-admin] line vty 0 63

[Device-line-vty0-63] authentication-mode scheme

[Device-line-vty0-63]user-role network-admin

[Device-line-vty0-63]user-role network-operator

[Device-line-vty0-63] quit

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 used for device data collection.

To configure gRPC:

1. Add a collector.

Navigate to the Analytics > Data Collection > Telemetry page to add a collector:

 Set the IP address to 192.168.16.100 (collector management IP) and port number to

50051 for collecting CPU, memory, interface, and cache queue data from devices through

gRPC.

Figure 3 Adding a 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 60

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

3. Deploy the configuration through the controller.

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

Click Edit.

Figure 5 Clicking Edit

Select the corresponding sensor paths, and click Save.

Figure 6 Saving the configuration

Select sensor paths as needed.

For periodic collection, specify sensor paths of the same collection interval in one collection

group.

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

sensor path device/transceiverschannels //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

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/tcbpacketinfoevent //TCB sensor path

sensor path telemetryftrace/genevent //MOD data sensor path

4. Perform manual configuration.

For the controller-issued paths, see the previous step and select the settings as needed. This

step illustrates the detailed configuration procedure. The sensor group, destination group, and

subscription name are customizable.

 Enable GRPC globally:

[Device] grpc enable //Enable the GRPC service.

 Configure periodic data collection:

[Device] telemetry //Enter Telemetry view.

[Device-telemetry] sensor-group group_grpc //Create a sensor group.

[Device-telemetry-sensor-group-group_grpc] sensor path device/base //Add a

sencor path.

[Device-telemetry-sensor-group-group_grpc] sensor path device/boards //Add a

sencor path.

[Device-telemetry-sensor-group-group_grpc]

destination-group destination_grpc //Create a destination group.

[Device-telemetry-destination-group-destination_grpc]

ipv4-address 192.168.16.100 port 50051 vpn-instance mgmt //Specify the IPv4

address and listening port number of a collector for the destination group. Specify

the VPN instance setting as needed.

[Device-telemetry-destination-group-destination_grpc]

subscription subscription_grpc //Create a subscription associated with the

sensor group and destination group.

[Device-telemetry-subscription_grpc]

sensor-group group_grpc sample-interval 60 //Associate the sensor group with the

subscription and configure the data collection interval as needed.

[Device-telemetry-subscription_grpc]

source-address 192.168.12.23 //Specify the source IP address for packets sent

to collectors. As a best practice, specify the device management IP address.

[Device-telemetry-subscription_grpc]

destination-group destination_grpc //Associate the destination group.

[Device-telemetry-subscription_grpc] quit

 Configure event-triggered data collection:

[Device] telemetry //Enter telemetry view.

[Device-telemetry] sensor-group group_grpc //Create a sensor group.

[Device-telemetry-sensor-group-group_grpc]

sensor path tcb/tcbpacketinfoevent //Add a sencor path.

[Device-telemetry-sensor-group-group_grpc]

sensor path telemetryftrace/genevent //Add a sencor path.

[Device-telemetry-sensor-group-group_grpc]

destination-group destination_grpc //Create a destination group.

[Device-telemetry-destination-group-destination_grpc]

ipv4-address 192.168.16.100 port 50051 vpn-instance mgmt //Specify the IPv4

address and listening port number of a collector for the destination group. Specify

the VPN instance setting as needed.

[Device-telemetry-destination-group-destination_grpc]

subscription subscription_grpc //Create a subscription associated with the

sensor group and destination group.

[Device-telemetry-subscription-subscription_grpc]

sensor-group group_grpc //Associate the sensor group. You do not need to configure

the interval for event-triggered data collection.

[Device-telemetry-subscription-subscription_grpc]

source-address 192.168.12.23 //Specify the source IP address for packets sent to

collectors. As a best practice, specify the device management IP address.

[Device-telemetry-subscription-subscription_grpc]

destination-group destination_grpc //Associate the destination group.

[Device-telemetry-subscription-subscription_grpc]

quit

5. 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 7 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 the 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. View the analyzer time.

# Use the date command to view the analyzer time..

[root@sa ~]# date

Sat Aug 13 14:27:51 CST 2022

2. Set the time zone.

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

the network device.

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

3. Set the system time.

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

[Device]clock protocol none

[Device] quit

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

4. Verify the time zone and system time settings.

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

<Device> system-view

[Device] dis clock

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.

Figure 8 Configuring data sources on the controller

2. To import logical areas, navigate to the Analysis > Analysis Options > Resources > Areas >

Logical Areas page, and click Import Areas. Select Import from Controller, and wait until

the areas are successfully imported. The logical areas imported from the controller correspond

to the fabrics of the controller.

Figure 9 Importing logical areas

Page is loading ...

Aruba JL852AAE Configuration Guide

Brand: Aruba

Model: JL852AAE

Type: Configuration Guide

This manual is also suitable for

Download PDF

report

Aruba JL852AAE Configuration Guide

This manual is also suitable for

Aruba JL852AAE Configuration Guide

Related papers

Other documents