Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Hypervisor MTU Threshold Check Probe (Virtual Infra)

Purpose

Detect virtual infra interfaces with maximum transmission units (MTU) below a specified threshold (default: 1600).
Source Processor
Interface MTU (generic graph collector)

output stage: Interface MTU (number set) (generated from graph)
Additional Processor(s)
MTU below threshold (range)

input stage: Interface MTU

output stage: MTU below threshold (discrete state set)
Example Usage

NSX Integration - To carry VXLAN-encapsulated overlay traffic, an MTU greater than 1600 is recommended. NSX-T transport nodes connected to ToR leaf devices that are below the specified threshold are detected.

To support Geneve encapsulation, the MTU configuration on NSX-T nodes involved in an overlay transport zone must have a valid MTU setting on the ESXi host. The image (from a previous Apstra version) below shows hypervisors with the MTU above the threshold.

If any of the hypervisors were below the threshold, the expected value would change to true and an anomaly would be raised.

For more information about this probe, from the blueprint, navigate to Analytics > Probes, click Create Probe, then select Instantiate Predefined Probe from the drop-down list. Select the probe from the Predefined Probe drop-down list to see details specific to the probe.