An administrator has deployed an NC2 cluster in AWS.
The following configuration decisions were made:
Created a new VPC from the NC2 console as part of the deployment
Selected the Public option for prism access policy
Host type selected was i13en,metal
The administrator now has a goal of provision public internet access to a user VM (UVM),web-1, on the Nutanix cluster. The admin can access Prism Element via the public DNS of the Auto-created load balancer.
The administrator tries to create another network load balancer for the web server access. After creating the load balancer and registering web-1’s IP address as a target, the administrator finds that the health check for the VM target is failing and the DNS returns as NOT Found message in the browser.
Why is the issue happening?
Submit