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 3.x, NSX for vSphere, VDS Netflow and IPFIX configuration (54472)

Last Updated: 7/19/2018Categories: How toTotal Views: 5615Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When enabling IPFIX in VRNI User Interface (UI), while adding the data sources, you experience these symptoms:

The Netflow settings in the vCenter Server for VDS/NSX for vSphere is not enabled.

Sending the packets to the desired collector VM (Proxy VM) fails.

Appearance of incomplete or missing flow data within vRNI.

Purpose

This article provides steps for the validation of a VDS data source and or a NSX data source for vRNI data flows.

Cause

This issue occurs due to the configuration settings for VDS data source or NSX IPFIX data source are incorrect, missing, or disabled.

Resolution

This articles provides steps on adding the collector address (proxy VM IP address) for the collection of Netflow/IPFIX flow data from a VDS/NSX data sources. The VDS and NSX data source settings can be disabled and enabled from the vRNI GUI and is the recommended method of configuration.

For further information on enabling these data source in vRNI please see documentation:

Enabling IPFIX Configuration on VDS and DVPG

Enabling VMware NSX IPFIX

For flow information to be present for a given communication there needs be a method in which to see and gather the data. vRealize Network Insight uses IPFIX and Netflow to gather flow information from a VMware VDS switch and or from VMware NSX for vSphere environment.

To validate settings please review:

To enable Netflow on VDS:

Log in to the vCenter Server.

Navigate to Networking.

Select the Distributed Virtual Switch.

Navigate to the DVPG.

Select the Configure Tab.

Select Edit.

Select Advanced.

For the Override Port Policies section toggle the radio button to ALLOWED NETFLOW.

In the same open Configure dialogue box select the Monitoring section.

For the NETFLOW change this from DISABLED to ENABLED.

To enable IPFIX for NSX:

From the vSphere Web Client, navigate to Home > Networking and Security.

Under the NSX Tools section, select Flow Monitoring > IPFIX for the given NSX Manager you are trying to add the IPFIX setting.

Under configuration tab for IPFIX we will need to Enable IPFIX. This will allow IPFIX data to be sent to vRNI.

Click the Add button and add the vRNI Collector VM IP Address (Proxy VM) and the field Collector Port: 2055.

All other values can be left at the default values.

Note: Ensure that the vCenter Server and NSX for vSphere are pointing to the same Proxy VM. In a multi proxy VM environment for FIREWALL RULE ID, ALLOWED, and DENIED FLOWS to appear in vRNI flow data.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
Spectre および Meltdown の脆弱性 (CVE-2017-5753、CVE-2017-5715、CVE-2017-5754) に対する vCloud Director および ESXi パッチ (52988)

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

Take Our Survey

Support Assistant