Archive for April, 2018

What can go wrong: Upgrading vCenter 5.5 to vCenter 6.0

April 2, 2018

These are the things that can go wrong; very wrong!

The digital signature on the installer has failed a verification check. The install can not continue.

This may indicate that the installer has been modified or corrupted and a new copy needs to obtained.

certificate error

  • This is not an issue actually. You just have to add the publisher certificate to your trusted root authorities certificates repository.
  • Visit https://www.symantec.com/theme/roots
  • Download the Root package for VeriSign Certificates.
  • Unzip the package and open > VeriSign Root Certificates > Generation 5 (G5) PVA > VeriSign Class 3 Public Primary Certification Authority – G5.
  • Double click the certificate and click Install Certificate.
  • When prompted for location make sure you add them in the following repositories.
    • Root Authority
    • Trusted Root Authorities
    • Third Party Root Authorities.
  • This will resolve the issue.

error-db

error-db2

Error: Incompatible source vCenter Server database version.

Error: Internal error occurs during VMware vCenter Server Database pre-upgrade checks.

  • This is MS SQL compatibility error.¬† VMware has provided an Inter-operability matrix as well which you can consult before any up-gradation. Minimum requirement is to upgrade your database server to Microsoft SQL Server 2008 R2 SP3.

 

Advertisements

Horton Works – Assign Static IP to HDP Sandbox V2.X in vSphere 6.X

April 2, 2018

HWX-RGB-full-w-tagline

I downloaded the HDP Sandbox 2.6 and tried to install it in vSphere. After making and breaking the file .ova file and finally deploying it;the machine got up but with network issues. To give your appliance a static IP address you will have to edit the networking scripts and reboot the machine. First of all verify your NIC instance with the following command (ens32 in my case).

ip addr show

01

The scripts can be found in the following location.

cd /etc/sysconfig/network-scripts

02

Evidently a script in my NIC instance name was missing.  I copied the contents of the already provided script (ifcfg-ens33) into a new file in my NIC instance name and modified the parameters to give a static IP to my sandbox instance.

vi ifcfg-ens32

03

BOOTPROTO=static

IPADDR=172.X.X.X.

NETMASK=255.255.255.0

GATEWAY=172.X.X.X

04

Save the file and reboot your appliance.

# reboot

After the reboot; the script assigned the static IP to the NIC instance and the Ambari server was up and running.


%d bloggers like this: