Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Hypervisor MTU Mismatch Probe (Virtual Infra NSX-T Only)

Release: Juniper Apstra 4.1
{}
Change Release
date_range 19-Jan-24
Purpose

NSX-T Only - Detect maximum transmission unit (MTU) value deviations across hypervisor physical network adapters (pnics).

Source Processor
Interface MTU (generic graph collector)

output stage: Interface MTU (number set) (generated from graph)

Additional Processor(s)
Check MTU mismatch between hypervisors (standard deviation)

input stage: Interface MTU

output stage: Hypervisor MTU Deviation (number set)

MTU Mismatch (range)

input stage: Hypervisor MTU Deviation (number set)

output stage: MTU Mismatch (discrete state set)

Example Usage

NSX Integration - If validation fails between NSX-T nodes and the controller in terms of mismatch of minimum configured MTU to support Geneve encapsulation or if the VLANs defined on NSX-T nodes are not configured on ToR leaf interfaces connecting an NSX node to the fabric, then anomalies are 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.

footer-navigation