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

ESXi Firewall rule for IPFIX(port 2055) gets disabled on ESXi 6.7 post reboot / netcpa process restart (67570)

Last Updated: 3/26/2019Categories: TroubleshootingTotal Views: 6118Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

1. When IPFIX is enabled from (NSX/vRNI), IPFIX packets are not received by the collector.
2. If an ESXi host reboots, the IPFIX packets are not received by the collector.
3. if netcpa process on ESXi host is restarted, IPFIX packets are not received by the collector.

How to Identify the problem:
Initiate a packet capture on the uplink vmnic interface (vmnic x) of source ESXi host from where the IPFIX packets are generated using the example below.

Example:
pktcap-uw --switchport 50331650 --dir 1 --stage 1 -o -| tcpdump-uw -ner - -n -t port 2055

Will see 0(zero) packets for IPFIX traffic for the above packet capture.

To find the switch port number
[root@localhost:~] net-stats -l
PortNum          Type SubType SwitchName       MACAddress         ClientName
33554434            4       0 vSwitch0         00:50:56:01:18:b3  vmnic0
33554436            3       0 vSwitch0         00:50:56:01:18:b3  vmk0
50331650            4       0 vSwitch1         00:50:56:01:18:b4  vmnic1    <------------- Considering this uplink is used for vRNI traffic
50331652            3       0 vSwitch1         00:50:56:68:a9:32  vmk1

Cause

After the ESXi host reboot / netcpa process restart the IPFIX firewall rule in the ESXi host gets automatically disabled. This blocks IPFIX pakcets at source ESXi host level.

Resolution

This is a known issue currently affecting ESXi 6.7 release and currently there is no resolution.

Workaround

Enable IPFIX firewall rule on ESXi host from Web Client UI

1. Login to UI of ESXi
2. Navigate to networking tab on the left pane
3. Navigate to Firewall rules tab on the right pane
4. Identify the ipfix firewall rule from the displayed rules and go to action and enable the same.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
将旧元数据解决方案迁移到新的 Edge 群集解决方案 (67554)

KB
•
执行安全/审核扫描后标记的 NSX Controller 证书标记为错误证书 (67817)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware NSX-T Data Center 2.x

VMware NSX-T Data Center

Take Our Survey

Support Assistant