Run health check APIs to verify compatibility between VLAN ID ranges you specified and the MTU settings on a transport node with the corresponding settings on a physical switch.
- Health check results are only indicators of possible network configuration errors. For example, health check run on hosts from different L2 domains results in untrunked VLAN IDs. This result cannot be considered as a configuration error as hosts must be in the same L2 domain for the health check tool to give correct results.
- Only 50 health check operations can be in progress at any given time.
- After a health check finishes, NSX preserves that result on the system only for 24 hours.
In a health check operation, the NSX opsAgent sends probe packets from a transport node to another node to verify compatibility between VLAN ID range you specified and the MTU value on the transport node with corresponding settings on the physical switch.
Number of VLANs | Waiting Time (secs) |
[3073,4095] | 150 |
[1025, 3072] | 120 |
[513, 1024] | 80 |
[128, 512] | 60 |
[64, 127] | 30 |
[1, 63] | 20 |
Prerequisites
- At least two uplinks configured on N-VDS for VLAN and MTU check to work.
- Transport nodes on the same L2 domain.
- Health check supported on ESX hosts running v6.7U2 or later.
Procedure
Results
The API response section contains the health check results. The NSX Ops agent waits for an acknowledgement packet from the destination transport node to retrieve VLAN ID ranges supported on the physical switch.
- Untrunked: Lists the VLAN ID ranges that are not compatible with a physical switch. The VLAN ID ranges that are compatible with the physical switch are also listed.
- Trunked: Lists the VLAN ID ranges that are compatible with a physical switch.
- Unknown: There is no valid result for some or all uplinks because of infrastructure issues or unsupported platform types such as Edge.
- vlan_and_mtu_allowed: Lists the VLAN ID ranges that are compatible.
- mtu_disallowed: Lists the VLAN ID ranges for which the MTU value is not compatible with a physical switch.
- vlan_disallowed: Lists the VLAN ID ranges that are not compatible with a physical switch.
What to do next
-
In an overlay-based transport zone, update both VLAN ID and MTU config in the uplink profile on N-VDS. Likewise, update VLAN or MTU on the physical switch.
-
In a vlan-based transport zone, update MTU config in the uplink profile. And, update VLAN config on logical switches of that transport zone. Likewise update VLAN or MTU on the physical switch.