Flows not visible in VCF Operations For Networks (vRNI) for specific VM and physical server IPs when ENS is enabled

Products

• VCF Operations for Networks

Issue/Introduction

• Flows are not displayed in vRNI for some of the VMs and physical servers.
• 
• The source ip is a physical server and destination is a vm (connected to DVS portgroup).
• The VMs for which the flows are not visible are part of DVS portgroup.
• ENS is enabled on the DVS uplinks used by the affected VMs.

Environment

VCF Operations for Networks 6.14.0

Cause

vRNI will not read the flows as DVS flows will be dropped if ENS is enabled on the uplinks.

DVS flows will not be captured at vRNI side where ENS is enabled because of the current vRNI version limitation.

 

Resolution

The VMs can be moved to NSX backed segments to see the flows in vRNI as NSX flows can be captured in vRNI even if ENS is enabled.

The DVS flows will be captured in vRNI with ENS setting enabled from VCF 9.1.

Also ENS can be disabled as a workaround to see the flows in vRNI for VMs connected to DVS portgroup.

Additional Information

Refer below document to enable ENS setting on uplinks:

https://techdocs.broadcom.com/us/en/storage-and-ethernet-connectivity/ethernet-nic-controllers/bcm957xxx/adapters/introduction/features/enhanced-network-stack--ens-.html