Adding initial NSX configuration to HOL-1403
It looks like VMware modified the NSX beginner lab 1403 so that the tasks now are completely independent of each other and can be done in pretty much any order. Unfortunately this process lost all of the initial configuration steps that were included in the actual lab.
So if you actually do want to follow one of the many initial configuration tutorials out there for NSX (after the point of the NSX manager deployment at least, as that VM is not deployable in that lab since you only have access to the web interface for it) you will need to basically reset the NSX configuration settings that have been made for you. This requires a certain order and if you are not familiar with the order on how to set up the components can be very frustrating as the error messages that pop up when you try to delete something that is in use are not very clear on where the issue is most of the time.
Just for reference here are the IP address pool settings the lab used:
The controller IP pool also uses a DNS server of “192.168.110.10”.
To start you will use the “vSphere Web Client” shortcut on the desktop and log in with the default credentials of “root” and “VMware1!”. Click on the “Networking & Security” link. First we need to start with the NSX Edges, click the appropriate menu option and use the small red x to delete both routers.
After all VMs are disconnected you can delete the switch itself by pressing the red x button when marking the switch.
After all switches are deleted we can continue getting the actual NSX bits and pieces off the hosts and the controller VMs deleted. To do so switch to the “Installation” menu. We will remove the transport zone first by navigating to the “Logical network preparation”, the option to delete will be available through a right-click.
For the “Segment ID” simply click the “Reset” button. In the “VXLAN Transport” click the “Unconfigure” link for all 3 clusters.
Click the “Management” tab and one after another mark each NSX Controller and press the red x button to delete them. If you get an error that a controller can not be deleted wait for about a minute and try again. If the error persists simply switch to the hosts and clusters view and shut down the 2 controller VMs in the management cluster. They should be deletable afterwards.
Click the NSX Manager IP and then on the “Manage” tab and navigate to the “Grouping Objects”. In there you should now be able to also delete the IP pools. You can see this menu in the very first screenshot of this post.
The last step is to move to the hosts and clusters view for vCenter and reboot every single host. The hosts do not have HA enabled and will automatically restart the VMs once they are back up.
With that the environment is reset and you can start configuring NSX from scratch after the NSX manager was deployed and initially configured to connect to vCenter Server.