Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vRNI does not support NSX-T Switch IPFIX data (67494)

Last Updated: 5/21/2019Categories: TroubleshootingTotal Views: 3701Language:
Chinese (Simplified)English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

Flows being reported in vRealize Network Insight  (vRNI) might be corrupted (For example: Incorrect IP addresses, huge amount of traffic etc. being reported in the flows).

Duplicate flow being reported for each flow, one of which will not be enriched with a VM, Security Group and other information.

Cause

NSX-T users can enable export of flow information in two ways:

Through the DFW IPFIX

Through the Switch IPFIX

Currently, vRNI does not allow a user to enable switch IPFIX. But NSX-T does allow a user to configure the switch IPFIX and point it to the vRNI Collector. This can potentially cause the flow data corruption in vRNI and the flows shown along with their metrics would be incorrect and unusable. Also, if a user specifies the same observation domain ID in both DFW and Switch IPFIX profiles, it can cause corruption in the flow data being received by vRNI. That corruption will persist as there is no way to clean that up hence the issue occurs.

In worst case, corrupted data would be cleaned after flow retention period. New flow, such as flows for which Four Tuple is not created when the wrong switch IPFIX was configured, will be shown correctly immediately.

In case of manually configuring the Switch IPFIX to point to vRNI Collector, if a user decommissions the vRNI collector, then the vRNI Collector IP address will be unreachable and issues related to unreachable IP address will occur in the network.

Resolution

This is a known issue affecting VMware vRealize Network Insight 3.9 and later versions.

Currently, there is no resolution.

Workaround

To work around this issue, remove the VRNI collector IP address from the NSX-T Switch IPFIX profiles.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Network Insight

Related Versions:

VMware vRealize Network Insight 4.x

VMware vRealize Network Insight 3.x

Take Our Survey

Support Assistant