VNA Devices are not consolidated correctly in the Data Aggregator

Products

• DX NetOps
• CA Performance Management - Usage and Administration
• CA Virtual Network Assurance

Issue/Introduction

DX NetOps Virtual Network Assurance (VNA) is integrated with DX NetOps Performance Management.

The Versa plugin is being used to gather SDN related inventory and metrics.

The Versa devices are all successfully enabled for SNMP communication with NetOps Data Collectors and that communication does function properly.

We see some devices from Versa that aren't being consolidated in the Data Aggregator causing Inventory discrepancies in the NetOps Portal web UI.

For example in the Administration->Monitored Items Management->Monitored Devices Inventory we might search using a device short name. The results would show two entries.

• Both have names that contain part of a matched value (usually short host/device name)
• Each shows a different Primary IP address set for use

Environment

All supported DX NetOps Performance Management and Virtual Network Assurance releases

Cause

The Data Aggregator is not consolidating the devices properly due to an unexpected configuration on the devices. The following example shows the problem faced.

Device named instanceABC-01 with DA Item_ID 123456789 has these IPs. Note Primary is 1111:2222:3333::18b (IPv6 address).
		<IPInformation>
			<IPAddresses>1111:2222:3333::18b</IPAddresses>
		</IPInformation>
		<IPInformation>
			<IPAddresses>1.2.3.4</IPAddresses>
		</IPInformation>
		<IPInformation>
			<IPAddresses>5.6.7.8</IPAddresses>
		</IPInformation>

Device named lo0.instanceABC-01.broadcom.com with DA Item_ID 545455 has these IPs with primary 1.2.3.4 (IPv4 address).
		<IPInformation>
			<IPAddresses>1.2.3.4</IPAddresses>
		</IPInformation>

Even though the device with Item_ID 545455 has it's primary IP known to device with Item_ID 123456789, the reverse is not true. As a result we don't consolidate/reconcile them together in the Data Aggregator.

It should be consolidating these together. It's considered a product limitation that should be provided as a feature.

Resolution

A feature exists with engineering, known by ID F122770, that would correct this behavior. Its a change that requires new code added to a future new release.

This has been completed and added to the product in release 22.2.2. Upgrade to that or newer releases to obtain this new feature.