Top KB Articles for VMware NSX !!

-
                                         KB Articles for VMware NSX
  1. Supportability of 32-bit app SSL VPN-Plus Mac Client in NSX-v 6.4.6 and older versions
  2. How to Reset a VeloCloud SD-WAN Edge?
  3. Guest Introspection status reports “Warning: Guest Introspection service not ready”
  4. “No NSX Managers available” error in the vSphere Web Client
  5. TCP and UDP Ports required to access VMware vCenter Server, VMware ESXi and ESX hosts, and other network components
  6. Tech Support Access in NSX for vSphere 6.x
  7. Licensing NSX for vSphere 6.x
  8. “Agent VIB module not installed” when installing EAM/VXLAN Agent using VUM
  9. Guest Introspection VM disconnect on VDI infrastructure
  10. vCenter Server or Platform Services Controller certificate validation error for external VMware Solutions in vSphere 6.0
  11. “The pending transaction requires xxx MB free space” error when installing VIBs
  12. Update sequence for vSphere 6.0 and its compatible VMware products
  13. vCenter Server certificate validation error for external solutions in environments with Embedded Platform Services Controller
  14. vCenter Server or Platform Services Controller certificate validation error messages for external solutions in environments with a External Platform Services Controller
  15. NSX-T admin password expired
  16. Collecting diagnostic information for VMware NSX for vSphere 6.x
  17. After upgrading to NSX-v 6.4.0, you see the error: “Possible DHCP DOS attack seen on the host. Please refer to NSX Manager and VM Kernel logs for details.”
  18. Product offerings for VMware NSX for vSphere 6.2.x, 6.3.x and 6.4.x
  19. Build numbers and versions of VMware NSX for vSphere
  20. Correlating build numbers and versions of VMware products

Comments

Post a Comment

Popular posts from this blog

How to migrate the N-VDS as the host switch to VDS 7.0 in NSX-T 3.x

-
Image
  Hello There, In this article, i am covering how to migrate the ESXi host switch from N-VDS to VDS 7.0 switch in NSX-T 3.2.x version. When using N-VDS as the host switch,  NSX-T  is represented as an opaque network in  vCenter Server . N-VDS owns one or more of the physical interfaces (pNICs) on the transport node, and port configuration is performed from  NSX-T Data Center . You can migrate your host switch to  vSphere  Distributed Switch (VDS) 7.0 for optimal pNIC usage and manage the networking for  NSX-T  hosts from  vCenter Server . When running  NSX-T  on a VDS switch, a segment is represented as an  NSX-T  Distributed Virtual Port Groups. Any changes to the segments on the  NSX-T  network are synchronized in  vCenter Server. We have an NSX-T environment running with NSX-T 3.2.2.1 version. this environment was designed and implemented with NSX-T 2.x version and that time we used the N-VDS as host switch configuration on the transport nodes bcuz VDS was not supported that time. 
Read more

vROPS appliances password remediation tasks failed from SDDC manager

-
Image
Issue details:-   Password remediation tasks on SDDC manager getting failed with below error. However, we are able to connect SSH with root password on the vROPS appliances, no issues with credentials. I checked Operations logs on SDDC manager and found below logs, indicating the SSH connectivity issues from SDDC to vROPS appliances. Tried to do SSH vROPS appliance from SDDC manager, getting below error... Seems some issue with ECDSA key.. Resolution:- SSH to vROPS appliance and retrieve the ECDSA ssh keys as below. Now, we have 2 options to update the correct SSH keys for vROPS appliance on SDDC manager known_Hosts files located at below location.   /root/.ssh/known_hosts   /etc/vmware/vcf/commonsvcs/known_hosts   /home/vcf/.ssh/known_hosts   /opt/vmware/vcf/commonsvcs/defaults/hosts/known_hosts First option is manually copy and paste the SSH key on all the known_hosts files and restart the SDDC manager services and then try to remediate the password again. it will be successful this
Read more

How to Import/Register a VM into vRA portal

-
Image
You can import an unmanaged virtual machine to a vRealize Automation environment. An unmanaged virtual machine exists in a vCenter but is not managed in a vRealize Automation environment and cannot be viewed in the vRA portal . Once you import an unmanaged virtual machine, the virtual machine is managed by using the vRealize Automation management interface. you can see the virtual machine on the Managed Machines tab or the Items tab. Please follow below steps to Import/Register VM into a vRA portal. Log in to vRealize Automation as a fabric administrator and as a business group manager. If you are importing virtual machines that use static IP addresses, prepare a properly configured address pool.  If you use bulk import to import a virtual machine with a static IP address that is allocated to another virtual machine, the import fails. Create a Blueprint and should not have even network attached as well. See below snapin. Create Network profile that shoul
Read more