The First step to configure LDAP user or group authentication is to ad an LDAP identity source to the management cluster In my case i will be using a Windows 2016 AD Server that i use for my lab Hostname : lab-ad01.lab.local To configure the LDAP connection: Click on system
Continue readinglogin into the MSX manager UI https://nsxmanagerip Click System -> Overview -> Add Nodes: 2Select the Compute Manager from the drop-down menu, enable SSH (if required), enter the cli and root password, DNS, NTP and select the form factor: Note: Select the same form factor as of the first NSX-T manager
Continue readingPrerequisites IP Information Create four “Host A” records in your DNS server for the three NSX-T Manager/Controller nodes that will be deployed and one for the virtual IP. Her is an example that i have used in my environment FQDN IPnsxmgr01.lab.local 192.168.50.51nsxmgr02.lab.local 192.168.50.52nsxmgr03.lab.local 192.168.50.53nsxmgr.lab.local 192.168.1.50 DNS Server NSX-T Data Center
Continue readingProcess Open an SSH session to the first deployed NSX Manager node. (In my case 192.168.50.1 nsxmgr01.lab.local)Log in with the administrator credentials On the NSX Manager node, run the get certificate api thumbprint command. The command output is a string of numbers that is unique to this NSX Manager. Run
Continue readingWhat is a compute manager? A compute manager, for example, vCenter Server, is an application that manages resources such as hosts and VMs. In the current release only vCenter is supported NSX-T Data Center polls compute managers to collect cluster information from vCenter Server. This helps with the auto deployment of new nodes
Continue readingStep one: taking a Network Interface Card inventory on an ESXi host Step Two: Collect NIC Vendor and device ID numbers: Step Three: Decode the NIC Vendor and device ID numbers into the format VID:DID SVID:SSID Example: VID = Vendor Id = 14e4 DID = Device Id = 165f SVID = Sub-Vendor
Continue reading