3. NSX Manager Deployment

Lets start with deploying NSX manager first to form the management plane. NSX manager is deployed via ova file which can be downloaded from VMware website.

The current version of NSX-T is 2.2.0 . Please refer NSX-T 2.2 Installation Guide before going ahead with deployment.

NSX-T 2.2.0 supports following hypervisor versions:

vSphere 6.5/6.5 U1/6.5 U2
RHEL KVM 7.3
Ubuntu KVM 16.04

NSX manager deployment is pretty straight forward like any standard virtual appliance deployment. Steps are shown in screenshot below.

For more information on NSX Manager installation, please see this article

Once the NSX Manager boots up, verify that the IP address set during deployment was applied as expected.

Also you can try to ping NSX-T from vCenter server and Esxi host to verify its connectivity.

Once connectivity is verified, connect to the NSX Manager GUI by typing https://NSX Manager-FQDN/ and login via admin user and password set during deployment

To apply license to your NSX-T appliance, click on System > Configuration > License and click on Add button to specify your license bit.

Comments

AWS on a Nutshell

Accessing the Platform To access AWS Cloud services, you can use the AWS Management Console, the AWS Command Line Interface (CLI), or the AWS Software Development Kits (SDKs). The AWS Management Console is a web application for managing AWS Cloud services. The console provides an intuitive user interface for performing many tasks. Each service has its own console, which can be accessed from the AWS Management Console. The console also provides information about the account and billing. The AWS Command Line Interface (CLI) is a unified tool used to manage AWS Cloud services. With just one tool to download and configure, you can control multiple services from the command line and automate them through scripts. The AWS Software Development Kits (SDKs) provide an application programming interface (AP...

vCenter Server Options on VxRail Appliance

In this post we will discuss the pros and cons of vCenter Server deployment on VxRail. During VxRail initialization we can choose two options for vCenter Server deployment, both options are “Deploy new vCenter Server Appliance (VCSA)” and “Join existing vCenter Server”. We should know its limitation before we choose the each option. You can find the details as below. If we choose the bundle vCenter Server deployment The vCenter Service Server Appliance (VCSA), vCenter Server Platform Services Controller (PSC) and vRealize Log Insight VM are already pre-loaded on each VxRail node. When VxRail initialization it can deploy these VMs automatically based on our business requirement. Pros The vCenter Server (VCSA) deployment is done automatically. When installing software package upgrade for the VxRail Manager, both VCSA and PSC includes the processing of package upgrade. VMware Log Insight is deployed automatically The vCenter license is bundled on VxRail Appliance. C...

Console Mouse Not Working in Windows 2012 VMs

I recently ran into some problems while deploying a Windows Server 2012 R2 VM in my vSphere 6.5 U2 lab. I’ve come to expect that the console mouse response is going to be terrible until VMware Tools is installed, but for some odd reason I had no mouse control whatsoever. Thinking it may be a quirk of the Web Console, I tried both the Remote Console and the HTML5 client to no avail. The VM appeared to be healthy and would register keyboard input, but the motion of the mouse cursor was erratic or the cursor would not move at all. Thinking that I just needed to battle on and get Tools installed, I attempted to use the keyboard for this purpose – what a chore. You think it would have been easy, but the installer kept losing focus and falling behind other open windows. Many of the windows keyboard shortcuts I’d normally use were not functioning because they register on my laptop – not in the console. I couldn’t RDP to the VM either because the NIC needed to be configured with a vali...

Vsphere total

Search This Blog