FQDN mappings from CSV uploaded under "Physical IP and DNS Mapping" are not appearing for source entities in VCF Operations for Networks

Products

• VCF Operations for Networks

Issue/Introduction

VCF Operations for Networks appliances continue to display as IP addresses instead of the expected FQDNs despite a successful CSV upload.

 

NOTE:  VCF Operations for Networks was formerly named Aria Operations for Networks (AON), and prior to that was named vRealize Network Insight (vRNI).

Environment

• Aria Operations for Networks 6.x

Cause

 

• Non-Retroactive Mapping: The FQDN mapping mechanism is not retroactive. Mapping metadata is attached to flow records during the ingestion/discovery phase. Flows that were already processed and stored in the database prior to the CSV upload will retain their original IP-based identity.

• New Flow Requirement: Only new flows initiated after the CSV processing will reflect the mapping.

 

Resolution

 

• Verify New Flows: Focus validation efforts on newly initiated network traffic. If an entry exists in the CSV for a specific IP, any new flow generated from that source should now resolve to the mapped FQDN.

• Engage Support: If entirely new flows from sources defined in the CSV still do not resolve to FQDNs during this monitoring period, engage support for further troubleshooting. (Creating and managing Broadcom cases)