Configuration A: North-South Traffic Monitoring
North-south traffic crosses the AHV host’s physical uplink. For example, traffic between VMs and the corporate network or the internet.
The source of the mirror session is the host’s uplink bond port, such as br0-up. The destination is the capture vNIC you created in Prepare the Network Sensor VM.
Keep the sensor VM on the mirrored host
Nutanix recommends that the sensor VM runs on the same AHV host as the uplink you are mirroring, and that it is configured as an agent VM so it is not migrated away, which would otherwise break the session.
Identify the Source Port Name
Determine the name of the uplink bond port on the AHV host, which is typically br0-up. To confirm, SSH into the AHV host and run:
ovs-vsctl showLook for the bond port associated with the physical uplink NICs. Note the port name, which is referenced as <uplink-port> below.
Mirror the bond port, not a bond member
AHV does not support mirroring from an individual member of a bond, such as eth0. The bond port itself, such as br0-up, must be used.
Create the Traffic Mirroring Session
From a CVM, run:
acli net.create_traffic_mirror r7_north_south \
description="Rapid7 north-south monitoring" \
source_list={uuid=<ahv-host-uuid>,type=kHostNic,identifier=<uplink-port>,direction=kBiDir} \
dest_list={uuid=<sensor-vm-uuid>,type=kVmNic,identifier=<capture-nic-mac>}Set direction to kIngress for inbound-only, kEgress for outbound-only, or kBiDir for both directions.
Verify
acli net.list_traffic_mirrorConfirm that r7_north_south is listed with State kActive. For full session details, including traffic counters:
acli net.get_traffic_mirror r7_north_southLegacy Alternative: OVS Mirror
If aCLI Traffic Mirroring is unavailable because AOS is older than 6.0, you can achieve the same result by manipulating OVS directly. If the cluster is registered to Prism Central, do not use this method. Configure Traffic Mirroring through the Prism Central UI or v4 API instead.
Unsupported method
This method is not officially supported by Nutanix, and mirror rules do not persist across host reboots. Use the aCLI Traffic Mirroring method above wherever possible.
ovs-vsctl \
-- --id=@s get port <uplink-port> \
-- --id=@d get port <capture-tap> \
-- --id=@m create mirror name=r7_ns_mirror \
select-src-port=@s select-dst-port=@s output-port=@d \
-- add bridge <bridge> mirrors @m<capture-tap> is the tap interface corresponding to the sensor VM’s capture NIC. Match its MAC address with virsh domiflist <sensor-vm-uuid> on the AHV host.
The mirror selects only the uplink port, so VM-to-VM traffic on the same bridge is not captured. Avoid select-all=true, which mirrors every port on the bridge, including VM tap ports.
Preserve existing mirrors
Do not run ovs-vsctl clear bridge <bridge> mirrors. It removes every mirror on the bridge, including mirrors that other tools rely on. To remove only the mirror created by this guide, run ovs-vsctl -- --id=@m get mirror r7_ns_mirror -- remove bridge <bridge> mirrors @m.
Next steps
Once the mirror session is active, confirm that the capture interface is visible inside the sensor VM by running sudo ip addr list. Then return to Step 4: Download and Install the Network Sensor Software to assign the capture NIC in the Insight platform and complete your sensor setup.