All of these KB articles were newly created in the month of April and cover a range of issues related to problems with NSX Intelligence, NSX-T UI alarms, ARP_PROXY, NSX Application Platform deployment, NSX-T upgrade, HCX SSL/TLS services, ESXi Host Stale Records, ESXi 7.0 U3L upgrade, and Uplink Profile issues:
This KB article explains that in some cases, the NSX Intelligence Plan and Troubleshoot view may not display any traffic even though there is traffic on the network. This can occur when the NSX Intelligence agent is not able to establish a connection to the NSX Manager or when the NSX Intelligence cluster is not functioning properly.
This KB article explains how to troubleshoot NSX-T UI alarms that are generated when an application on the NSX node has crashed. This is a known issue impacting NSX-T data center!
This KB article provides information on how to troubleshoot the issue where ARP_PROXY shows NULL on LB service interfaces.
This KB article provides troubleshooting steps for when NSX Application Platform deployment fails at 70% registering the platform. This behavior is fixed on NSX 4.0.0.1.
This KB article addresses an issue where an NSX-T upgrade fails with the error message “NSX Manager upgrade dry run failed, Do not proceed with the upgrade.” The article explains that this can occur when there are insufficient resources or when the upgrade package is corrupted.
This KB article provides information on an issue with HCX SSL/TLS services running on TCP port 9443 being flagged for DH 1024 key-size. The article explains that this can occur due to outdated cipher suite configurations.
This KB article discusses an issue where stale records of ESXi hosts are present on the NSX UI from the Corfu database. The article explains that this can occur due to a failure in the cleanup process of the Corfu database.
This KB article addresses an issue where ESXi 7.0 U3L upgrade from Dell OEM ISO loads driver 4.1.9 driver but the host is disconnected after a reboot. The article explains that this can occur when the driver version is not compatible with the ESXi version.
This KB article provides information on an issue where removinguplinks from an Uplink Profile causes incorrect TEP order and some VMs lose connectivity. The article explains that this can occur when the Uplink Profile is not properly configured, resulting in incorrect Transport Node Profile (TNP) settings. The article provides guidance on steps to identify and resolve the issue, including correcting the TNP settings and restarting the NSX Manager service.
Our curated solutions are available 24/7 through VMware KB Articles. Make sure to also check our other resources:
- Knowledge Base : So many articles. So many topics. Find what you need.
- Product Documentation : Explore a full range of technical documentation including manuals, release notes, and more.
- Tech Zone : Go from zero to hero with the latest VMware technical resources.
- Technical Papers : Access content written by VMware technical experts.
- VMware Blogs : Benefit from the experience of industry professionals from around the VMware community.
- Compatibility Guides : Get information regarding supported and compatible hardware, software, and guest and host operating systems.
- Product Support Centers : All available support information grouped by product.
- Community Forums : Connect with users across the globe.
- Support Best Practices : Learn about best practices to help you get the most out of your support experience.
- SnS Extension Estimator : Determine whether you will receive a support contract extension when upgrading your license.
Comments