0

VMware vSphere NSX 6.3.3 Step-By-Step Installation : Howto

 

NSX Manager Deployment

1. NSX Manager

It will automatically install all the required component as per request Like NSX controller.

2. NSX Controllers: Need to be deploy in odd number like 3 or 5.

3. Edge

4. Distributed Router Controllers

 

Now First you need to Create NSX Cluster this is not compulsion but suggested or i have created one Resource pool with Expandable check.

image

Download the OVA file from VMware website.

image

 

NSX Components Layer where they Installed.

Data Plane: On ESXi host

          a) Kernel Modules: VXLAN (16 Million VXLAN Segment)

b) Distributed Logical Router (DLR)

c) Distributed Firewall (DFW)

d) VDS switch and Edge Service Appliance.

Control Plane:

             a) NSX Controllers

b) User World Agent

c) Logical Router Control VM

Management Plane:

             a) vCenter Server

b) NSX Manager

             c) Message Bus

 

Deployment of NSX Manager:

1. Only One NSX manager per vCenter Server.

2. Deploy as a VM.

3. What if my NSX manager is Shutdown: No worries, everything continues to work but you will not able to change anything. No Service impact.

Solution: Protect with vSphere HA.

NSX manager Virtual Machine Requirement: reference vmware doc.

1. 4 vCPUs

2. 16 GB of RAM

3. 60 GB of Storage

Steps for Installation:

1. Right-Click on the cluster in which you would like to deploy the NSX Manager OVA and choose “Deploy OVF Template”

2017-09-12 14_46_23-vSphere Web Client

image

2. Browse the file and Click next.

image

3. Select the Resources

2017-09-12 14_50_12-vSphere Web Client

4. Review the details and click Next.

image

5. Accept the License agreements and click next.

image

6. Select Storage and click next.

image

7. Now Provide Network from VDS.

image

8. Provide IP details, CLI password and DNS sever click next and finish.

image

After installation you will see new icon with Networking & Security.

image

when you click on Dashboard option on the left hand side then you can see that status of NSX Manager and Host Preparation Status.

image

When you click on Installation Option then it will show you NSX manager and it’s controller nodes name and status.

2017-09-12 16_07_09-vSphere Web Client

Now under Installation you have multiple tabs like Management, Host Preparation, Logical Network Preparation and Service deployments

Click on the Host Preparation and you can see whether NSX manager module vCenter, NSX Manager, EAM(ESX Agent Manager) is installed or not.

These are the VIB which will be install.

esx-vsip
esx-vxlan

 

image

Open Putty session for ESXi host.

 

[root@esx002291:~] esxcli software vib list
Name                                                           Version                                Vendor  Acceptance Level  Install Date
—————————–  ——————————————————————-  ——  —————-  ————

esx-vsip                                            6.5.0-0.0.5534171                      VMware  VMwareCertified   2017-07-19
esx-vxlan                                         6.5.0-0.0.5534171                      VMware  VMwareCertified   2017-07-19

0

“Agent VIB module not installed” when installing EAM/VXLAN Agent using VUM

After upgrading NSX Manager 6.3.2 facing issue with NSX manager and EAM, VIB is continuously failing.

“Problem with ESXi host preparation and specifically the error ‘Dependencies of the VIB which is updating the ESX image cannot be satisfied by the host”.

Now at this point all the Hosts are in ready state.

After rebooting NSX Manager and Deleting VUM database still not working

what is inside in ESXi logs showing error > /var/log/esxupdate.log

===========================================================================
2017-09-04T12:21:51Z esxupdate: 75636: vmware.runcommand: INFO: runcommand called with: args = ‘localcli system visorfs ramdisk list | grep /vibtransaction && localcli system visorfs ramdisk remove -t /tmp/vibtransaction’, outfile = ‘None’, returnoutput = ‘True’, timeout = ‘0.0’.
2017-09-04T12:21:51Z esxupdate: 75636: Transaction: DEBUG: Populating VIB list from all VIBs in metadata https://vc01.domain.local:443/eam/vib?id=54fbc544-436e-4e06-800d-3e2a95448d92; depots:
2017-09-04T12:21:51Z esxupdate: 75636: downloader: DEBUG: Downloading https://vc01.domain.local:443/eam/vib?id=54fbc544-436e-4e06-800d-3e2a95448d92 to /tmp/tmpgxbeofzh…
2017-09-04T12:21:51Z esxupdate: 75636: Metadata.pyc: INFO: Unrecognized file vendor-index.xml in Metadata file
2017-09-04T12:21:51Z esxupdate: 75636: imageprofile: INFO: Adding VIB VMware_locker_tools-light_6.2.6-0 -4463934 to ImageProfile (Updated) ESXi-6.5.0-20170702001-standard
2017-09-04T12:21:51Z esxupdate: 75636: imageprofile: INFO: Adding VIB VMware_bootbank_esx-vsip_6.2.6-0 -4977495 to ImageProfile (Updated) ESXi-6.5.0-20170702001-standard
2017-09-04T12:21:51Z esxupdate: 75636: imageprofile: INFO: Adding VIB VMware_bootbank_esx-vxlan_6.5.0-0.0.4463934 to ImageProfile (Updated) ESXi-6.5.0-20170702001-standard
2017-09-04T12:21:51Z esxupdate: 75636: vmware.runcommand: INFO: runcommand called with: args = ‘[‘/bin/localcli’, ‘system’, ‘maintenanceMode’, ‘get’]’, outfile = ‘None’, returnoutput = ‘True’, timeout = ‘0.0’.
2017-09-04T12:21:52Z esxupdate: 75636: HostInfo: INFO: localcli system returned status (0) Output: Enabled Error:
2017-09-04T12:21:52Z esxupdate: 75636: BootBankInstaller.pyc: INFO: Unrecognized value “title=Loading VMware ESXi” in boot.cfg

===========================================================================

I found nothing,it’s just blocking the VIB to be install on Host. After this i started troubleshooting further and start checking logs and error in vCenter and NSX Manager logs.

Thanks to Conor Scolard he found that NSX manager is trying to install old VIB as you can see in logs.
After upgrading NSX manager 6.3.2 it should be “6.5.0-0.0.4463934″

===========================================================================

2017-09-04T12:21:51Z esxupdate: 75636: Transaction: DEBUG: Populating VIB list from all VIBs in metadata https://vc01.domain.local:443/eam/vib?id=54fbc544-436e-4e06-800d-3e2a95448d92; depots:
2017-09-04T12:21:51Z esxupdate: 75636: downloader: DEBUG: Downloading https://vc01.domain.local:443/eam/vib?id=54fbc544-436e-4e06-800d-3e2a95448d92 to /tmp/tmpgxbeofzh…
2017-09-04T12:21:51Z esxupdate: 75636: Metadata.pyc: INFO: Unrecognized file vendor-index.xml in Metadata file
2017-09-04T12:21:51Z esxupdate: 75636: imageprofile: INFO: Adding VIB VMware_locker_tools-light_6.5.0-0.23.5969300 to ImageProfile (Updated) ESXi-6.5.0-20170702001-standard
2017-09-04T12:21:51Z esxupdate: 75636: imageprofile: INFO: Adding VIB VMware_bootbank_esx-vsip_6.5.0-0.0.4463934 to ImageProfile (Updated) ESXi-6.5.0-20170702001-standard
2017-09-04T12:21:51Z esxupdate: 75636: imageprofile: INFO: Adding VIB VMware_bootbank_esx-vxlan_6.5.0-0.0.4463934 to ImageProfile (Updated) ESXi-6.5.0-20170702001-standard

===========================================================================

Tried to open EAM Mob >> https://vcenterIP/eam/mob, it’s not working then “rebooted vCenter” and after that this start working.

As you can see here we have older version of VIB.(NSX Manager is on 6.3.2 version)

 

Under NSX Component Installation on Hosts > Clusters & Hosts is known as “Agency” and this mean Agency is corrupted.

===========================================================================

Now only option is to Delete Agency and it will automatically create new Agency and pick the Latest VIB drivers.

This is Easy when you are not using

1. VXLAN
2. NSX Firewall

But before that how to identify that Agency is corrupted.

Open SSH for NSX manager.

1. type enable and provide password.

===========================================================================
admin@nsx.domain..local’s password:
nsx.domain..local> en
Password:
===========================================================================

2. After this if you are working with VMware then tech support guy will type their secret password to enable “Engineering Mode”

nsx.domain..local# st e
Engineering Mode: The authorized NSX Manager system administrator is requesting a shell which is able to perform lower level unix commands/diagnostics and make changes to the appliance. VMware asks that you do so only in conjunction with a support call to prevent breaking your virtual infrastructure. Please enter the shell diagnostics string before proceeding.Type Exit to return to the NSX shell. Type y to continue: y
Password: this is VMware password
su: Authentication failure
nsx.domain..local# st e
Engineering Mode: The authorized NSX Manager system administrator is requesting a shell which is able to perform lower level unix commands/diagnostics and make changes to the appliance. VMware asks that you do so only in conjunction with a support call to prevent breaking your virtual infrastructure. Please enter the shell diagnostics string before proceeding.Type Exit to return to the NSX shell. Type y to continue: y
Password:
[root@nsx ~]# cd /home/secureall/secureall/logs/
[root@nsx /home/secureall/secureall/logs]# less vsm.log
[root@nsx /home/secureall/secureall/logs]# psql -U secureall
psql.bin (9.3.15 (VMware Postgres 9.3.15.0-4760484 release))
Type “help” for help.
Cannot read termcap database;
using dumb terminal settings.

===========================================================================

3. After this run below command
secureall=# select * from deployment_unit;

by using these commands you can check if there is any issue with NSX Manager database or not.

===========================================================================

Now Solution time:

1. First open https://vcenter/eam/mob

 

2. Highlighted in Yellow is Agency

3. Click on this and after that click on “DestroyAgency”.

4. Click on Invoke Method

5. Just follow the same path and check the VIB version and you will see this time it’s updated with newer version.

6. Now go to NSX Manager View and this time you will see there is no status it’s blank, that mean we can install latest version.

7. Click on Action Gear icon and install the agent.

0

New vSphere Availability Option’s and Quarantine Mode

In 6.5 VMware has changed the name of vSphere High Availability (vSphere HA) to vSphere Availability.

In vSphere 6.0 Version

2017-09-05 10_18_03-vSphere Web Client

And in 6.5 Version

2017-09-05 10_19_12-vSphere Web Client

 

New Setting in 6.5 vSphere is Proactive HA which works with DRS and it has two options.

 

First thing, this is DRS feature, not an HA and basically, it will get data from physical hardware like RAM, CPU like DRS algorithms doing normally and then use DRS to decide whether it needs to move VMs or not.

Proactive HA look at different alerts to see if maybe something is going on with the host in order to make a decision to move workload or not.

Now in order to do this, Different hardware vendor is creating or in process of creating OEM.

If you are using Proactive HA with OEM and there is DIMM or NIC card failure then, in this case, Proactive HA coordinate with DRS and take action on that host. (vMotion)

Now we have two option in this setting:

1. Automation Level is like DRS.

2. Remediation

Quarantine Mode Means: DRS will move all the VMs but no impact on VM performance and affinity rules should not be violated.

when you decided to put the host into quarantine mode, then it will start evacuating the VMs but it will consider the basic facts of and this is DRS affinity and anti affinity rules should not be violated, and also if there is no performance degradation.

After this DRS will not place any VM on that host.

As I said second consideration is if there is no performance degradation on VMs if DRS see any impact on VMs performance then DRS place VM on this Quarantine host.

A) Quarantine mode for all failures

B) Quarantine mode for moderate and Maintenance mode for Severe failure(Mixed).

C) Maintenance mode for all failures

 

Admission Control: New Change is Autocalculation

Now it can automatically calculate the Percentage of resources which are required for Cluster failover.

 

Performance degration VMs tolerate:

Here 100% means this setting is disabled and you are fine if there is any degradation in terms of performance and if i put 0% percent then i am not okay or i dont want any performance degradation with VMs.

In the event of failure and VMs restarted and they are not getting sufficient resource and facing performance degradation then it will alert me.

 

0

How to upgrade NSX Manager from 6.2.6 to 6.3.2

Today i was updating NSX manager from 6.2.6 to 6.3.2 version.

Environment running with vCloud director 8.20 and ESXi 6.5 U1.

1. Check VMware Product Interoperability Matrices for more information “Link”.
2. Check Update sequence for vSphere “KB“.

Before upgrade to NSX 6.3.2.

1. NSX Manager VM Snapshot.
2. NSX Manager Appliance Backup.(FTP server required)

3. Check “Lookup service” and “vCenter” server status in NSX management service.

4. Download the NSX 6.3.2 version from VMware website.

5. After this upload the bundle file into NSX manager console from Upgrade option.

 

 

 

 

it will start uploading this image to NSX manager and will start installing.

After uploading bundle it will give you Warning! Please create an NSX Manager backup before proceeding with upgrade also it will ask you whether you want to enable SSH and Finally hit Upgrade button.

After this it will pop up with new version with 6.3.2 version.

After this Need to upgrade NSX Controller if you have.

Also install the agent in Agency.

Final Status after upgrade.