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

Farewell, vCenter Server for Windows

Farewell, vCenter Server for Windows

Farewell, vCenter Server for Windows

VMware plans to deprecate vCenter Server for Windows with the next numbered release (not update release) of vSphere. The next version of vSphere will be the terminal release for which vCenter Server for Windows will be available. Why Is VMware deprecating vCenter Server for Windows? VMware is consistently striving to simplify data center administration and The post Farewell, vCenter Server for Windows appeared first on VMware vSphere Blog .


VMware Social Media Advocacy

0

Goodbye, vSphere Web Client!

Goodbye, vSphere Web Client!

Goodbye, vSphere Web Client!

VMware plans to deprecate the Flash-based vSphere Web Client with the next numbered release (not update release) of vSphere. The next version of vSphere will be the terminal release for which vSphere Web Client will be available. The vSphere GUIs, including the vSphere Web Client and HTML5-based vSphere Client, are tools that are used every day The post Goodbye, vSphere Web Client! appeared first on VMware vSphere Blog .


VMware Social Media Advocacy

0

Tips for Passing your VCDX

Tips for Passing your VCDX

Tips for Passing your VCDX

The VMware Certified Design Expert (VCDX) is the most elite certification that VMware offers. Those that earn it have proven they can operate at the highest levels of expertise, showing not only their advanced technical knowledge but also their ability to think on their feet, to identify and recognize customer requirements, and begin creating a conceptual design within minutes.


VMware Social Media Advocacy

0

VMware Fun Facts 2017

VMware Fun Facts 2017

VMware Fun Facts 2017

VMware started with 5 people in 1998 and now has over 20,000 people. Take a quick tour of VMware’s history with this fun facts animation. Learn more about life at VMware: https://careers.vmware.com/ http://facebook.com/vmwarecareers http://twitter.com/vmwarecareers http://instagram.com/vmwarecareers https://www.linkedin.com/company-beta/2988/life/


VMware Social Media Advocacy

0

How to configure Dell PERC H730 mini RAID Cards for VMware VSAN

I was facing some issue with VSAN cluster and after troubleshooting with the help of VMWare we found that our Dell PERC H730 mini RAID card is not in HBA pass-through mode. It was in RAID Mode and Disks are in pass-through mode.

Pre-requisites for VSAN.

2017-08-18 12_33_20-Bookshelf Online_ VMware Virtual SAN_ Deploy and Manage [V6] Instructor Lecture

Pic Credit: VMWare

So As we know that VSAN pre requisites regarding Hardware RAID controller should be in HBA or pass-through mode.  Yes, HBA is pass-through mode in Dell PERC H730.

Note: Before starting this activity need to follow below steps.

1. Using Web client Put that ESXi host into maintenance mode and use this option Evacuate all data to other hosts.

2. After that Remove all the disks from that disk group and it will automatically delete that disk group.

3. Now Open iDRAC for that Dell Server and follow the below steps. (Press F2)

4. It will open below console and from here you can choose RAID settings.

2017-07-21 14_23_59-

Here you can select your controller.

2017-07-21 14_29_34-

2017-07-21 14_29_51-

DO NOT CLICK ON CLEAR CONFIGURATION.

2017-07-21 14_30_12-

Select Convert to RAID Capable

2017-07-21 14_30_12-

As you can see in below screen shot this Controller is in RAID mode.

2017-07-21 14_30_44-

Go further down and click on Advanced Controller Properties.

2017-07-21 14_31_00-

Select Switch to “HBA mode” option and your controller will be now in pass-through mode.

Note: If you select HBA mode then you can see below option to flip back to RAID.

2017-07-21 14_33_52-

After this reboot the Server.

0

vSAN ReadyNode™ Sizer: Size and Deploy vSAN for…

vSAN ReadyNode™ Sizer: Size and Deploy vSAN for the workload of your choice

vSAN ReadyNode™ Sizer: Size and Deploy vSAN for…

The new All Flash vSAN ReadyNode™ Sizer is now available and is accessible here: https://vsansizer.vmware.com/ What are the key features of the vSAN ReadyNode™ Sizer? The key features of vSAN ReadyNode™ Sizer are: Evaluation Sizer: A basic evaluation version of the vSAN ReadyNode™ Sizer which requires minimal input such as the count of The post vSAN ReadyNode™ Sizer: Size and Deploy vSAN for the workload of your choice appeared first on Virtual Blocks .


VMware Social Media Advocacy