VMware NSX-T Integration

Overview

You can integrate NSX-T with Apstra software (as of version 3.1) to help deploy fabric VLANs that are needed for deploying NSX-T in the data center or for providing connectivity between NSX-T overlay networks and fabric underlay networks. You can accelerate NSX-T deployments by making sure the fabric is ready in terms of LAG, MTU and VLAN configuration as per NSX-T transport node requirements. This feature also helps network operators with fabric visibility in terms of seeing all the NSX-T VMs, VM ports, and physical gateway ports. NSX-T integration helps identify issues on the fabric and on the virtual infrastructure. It eliminates manual config validation tasks between the NSX-T Nodes side and the ToR switches.

Supported Versions

As of version 3.3.0 VMware NSX-T integration is currently available for the VMware NSX-T Data Center 2.5 version.

Limitations

  • NSX-T Edge integration is currently supported on bare metal deployments only. NSX-T Edge is not supported on VMs.
  • Having more than one NSX-T virtual infra in a blueprint is not supported. We recommend only one virtual infra per blueprint.
  • NSX-T integration does not support DVS port group with VLAN-type trunking.

Enabling NSX-T Integration

We recommend that you create a user profile dedicated to managing NSX-T integration activities.

  1. From the web interface, navigate to External Systems > Virtual Infra Managers and click Create Virtual Infra Manager.

  2. In the dialog that appears enter the NSX-T manager IP address (or DNS name), select the virtual infra type VMware NSX-T Manager and enter a username and password.

  3. Click Create to create the virtual infra manager and return to the list view. When the connection is successful, the connection state changes from DISCONNECTED to CONNECTED.

  4. From the blueprint, navigate to Staged > Virtual > Virtual Infra and click Add Virtual Infra.

  5. Select the virtual infra manager from the drop-down list, then click VLAN Remediation Policy to expose additional fields. The information entered here is used in Intent-based analytics (IBA) probes that can remediate anomalies.

    _images/Remediation_Policy.png
  6. Select the VN type and routing zone.

    • If VLAN (rack-local) is selected you can’t change the default routing zone.
    • If VXLAN (inter-rack - when VN extends to different ToRs in the fabric) is selected you can select a different routing zone.
    _images/VN_Type.png
  7. Click Create to create the virtual infra manager and return to the list view. The new virtual infra manager appears in the list.

    _images/Virtual_Infra.png
  8. Click Uncommitted (top) to see changes, then click Commit (top-right) to add the NSX-T manager to the active blueprint.

Virtual Infrastructure Visibility

When you’ve successfully integrated NSX-T, you have visibility of NSX-T VMs and transport nodes in the virtual infrastructure. You can query the status of the VMware fabric health.

To see a list of the VMs connected to the hypervisor, navigate to the dashboard and scroll to fabric health for VMware option.

_images/Fabric_Health.png

You can also query VMs that are hosted on hypervisors connected to TOR leafs. From the blueprint, navigate to Active > Query and click VMs.

_images/VMs_Query.png

VMs include the following details:

VM Name
The Virtual Machine name which is hosted on NSX managed hypervisor.
Hosted On
The ESXi host on which Virtual Machine is hosted.
Hypervisor Hostname
The hypervisor hostname on which Virtual Machine is hosted and is connected to the leaf TORs in a fabric.
Hypervisor Version
The software version of OS running on the hypervisor.
VM IP
The IP address as reported by NSX-T after the installation of VM tools. If the IP address is not available this field is empty. AOS displays VM IP if the IP address is available on installation VM tools on the VM.
Leaf:Interface
System ID for the interface on the leaf to which ESXi host is connected and on which VM resides.
Port Group Name:VLAN ID
The VLAN ID which NSX-T port groups are using. Overlay VM to VM traffic in a NSX-T enabled Data Center tunnels between transport nodes over this Virtual network.
MAC Addresses
MAC address of the VM connected to the AOS Fabric.
Virtual Infra address
IP address of the NSX-T infra added to a Blueprint

To search for nodes in the physical topology that have VMs, navigate to Active > Physical and select Has VMs? from the Nodes drop-down list.

_images/Has_VMs.png

Validating Virtual Infra Integration

You can validate virtual infra with intent-based analytics. Two predefined analytics dashboards (as listed below) are available that instantiate predefined virtual infra probes.

Virtual Infra Fabric Health Check Dashboard

Hypervisor MTU Mismatch Probe

Hypervisor MTU Threshold Check Probe

Hypervisor and Fabric LAG Config Mismatch Probe

Hypervisor and Fabric VLAN Config Mismatch Probe

Hypervisor Missing LLDP Config Probe

VMs without Fabric Configured VLANs Probe

Virtual Infra Redundancy Check Dashboard
Hypervisor Redundancy Checks Probe

For more information, see Analytics Dashboard and Instantiating Predefined Probe.

Disabling Virtual Infra Integration

Virtual infra integrations are disabled by deleting them from the blueprint and external systems.

  1. From the blueprint, navigate to Staged > Virtual > Virtual Infra and click the Delete button for the virtual infra to disable.
  2. Navigate to the Uncommitted tab and commit the deletion.
  3. From the External Systems menu (left-side), navigate to Virtual Infra Managers and click the Delete button for the virtual infra to disable.