Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Hypervisor and Fabric LAG Config Mismatch Probe (Virtual Infra)

Purpose

Detect inconsistent LAG configs between fabric and virtual infra and calculate LAGs missing on hypervisors and managed leaf devices connected to hypervisors.
Source Processor
Hypervisor NICs with LAG (generic graph collector)

output stage: Hypervisor NICs LAG Intent Status (discrete state set) (generated from graph)
Additional Processor(s)
Hypervisor NIC LAG anomalies (state)

input stage: Hypervisor NICs LAG Intent Status

output stage: Hypervisor NIC LAG Mismatch Anomaly (discrete state set)
Example Usage

vSphere Integration - This probe detects inconsistent LAG configs between fabric LAG dual-leaf devices and ESXi hosts. LACP mode information is collected from the fabric LAG dual-leaf devices and also connects to vCenter API and collects LAG groups and members per hypervisor.

Note:

Current validation is done on vCenter virtual Distributed Switches only, not on virtual Standard Switches. LLDP must be enabled on vCenter vDS switches.

Anomalies are raised if any of the following occurs:

  • LAG member ports on ToR are connected to non-LAG physical ports on ESXi.
  • Non-LAG member ports on ToR are connected to LAG physical ports on ESXi.

NSX Integration - Enabling this probe activates a continuous LAG validation between NSX-T transport nodes and data center fabric. It validate that LAGs are properly configured between fabric LAG dual-leaf devices and NSX-T transport nodes. The NSX-T uplink profile defines the network interface configuration facing the fabric in terms of LAG and LACP config. Network interface misconfiguration between the transport node and the ToR switch is validated and detected.

Anomalies are raised in the following circumstances:

  • NSX-T transport nodes are not configured for LAG but ToR has LAG member ports in the fabric.
  • ESXi hosts are dual-attached to ToR leaf devices but corresponding NSX-T transport nodes are “single-attached” or they are using “NIC-teaming” using active-standby or load-balanced config.
  1. Add NSX-T API user as a Virtual Infra.
  2. Add NSX-T Manager in the blueprint (External Systems > Virtual Infra Managers).
  3. Enable this probe (Hypervisor and Fabric LAG config mismatch).

Let’s say in the NSX-T uplink profile, LAG is deleted but the fabric has LAG in terms of ToR leaf devices having LAG member ports. As a result in a blueprint after enabling this probe LAG mismatch anomalies are raised.

Since the LAG on the NSX-T transport nodes has been deleted, there is a mismatch between physical network adapter (pnic) on ESXi host LAG configuration and LAG configuration on ToR leaf devices.

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.