new1234.jpg

Archive

Posts Tagged ‘SSH’

VMware: Updating vCenter Server Appliance 6.0 to Update 1

December 18th, 2015 3 comments

Current build VMware vCenter Server 6.0.0 2776510, vSphere client 6.0.0 2741530

 

Note: Supported upgrade paths to VCSA 6.0 U1 include from 5.1 U3 & 5.5.

While on the topic of upgrades, going from VCSA 6.0 to 6.0 U1 is quite simple. First, you’ll need a patch ISO, which can be found on here. You ‘ll notice there are two patch ISOs, FP and TP.

Download VCSA patch from here.

image


FP
is a full product patch for VC & PSC appliances only.

TP is third party patch spanning multiple products, such as VCSA, vCenter Windows, VUM, PSC appliance and windows.

 

To update/patch your vCenter 6.0 Appliance, please follow the below steps:

  1. Connect directly to vSphere host which running vCenter Appliance
  2. Take a snapshot of VCSA
  3. Connect downloaded ISO file to the VCSA VM
  4. Log in to the VCSA via SSH
  5. Run the following command
    To mount ISO and accept EULA:

software-packages stage –iso –acceptEulas

image

 

To stage ISO:

software-packages install –iso

image

 

To see  the staged content:

software-packages list –staged

image

 

To  install the staged rpms:

software-packages install –staged

image

 

shutdown reboot –r patching

image

 

Result

image

New buildnumber: VMware vCenter Server 6.0.0 3018523

 

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Toggling the vCenter Server Appliance 6.x default shell

December 18th, 2015 No comments

This article provides vSphere Administrators steps to toggle between default shells available on the vCentrer Server Appliance (vCSA). 

Currently, the vCSA is bundled with these supported shells:

  • Appliance Shell
  • BASH Shell
    Today I tried to upgrade vCenter Appliance 6.0.0 to Update 1, after runnning command “software-packages stage –iso –acceptEulas” I receiver message:

    -bash: software-packages: command not found

image

 

Switching the vCenter Server Appliance 6.x to Appliance Shell

 

  1. Log in to the vCenter Server Appliance via SSH.
  2. Run this command to change from using the BASH Shell to the Appliance Shell:

    chsh -s /bin/appliancesh root

  3. Log out from the BASH Shell and re-log in for this to take affect.

image

 

Result

After restart the SSH sessoin I was able to run commands in bash shell

image

 

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Error when uploading files to vCenter Server Appliance using WinSCP

September 15th, 2015 No comments

Last week I tried to download some logfiles with WinSCP from the customer vCenter 6.0 appliance but I couldn’t, I received this error message:
  

Host is not communicating for more than 15 seconds. If the problem repeats, try turning off 'Optimize connection buffer size'. 

 

Solution

When you copy files using WinSCP, part of the operation happens on the target Linux system. The default Appliance Shell cannot be the remote partner of WinSCP. You must enable the Bash shell on the appliance, as follows:

  1. Initiate an SSH connection to the vCenter Server Appliance.
  2. Provide the root user user name and password when prompted.
  3. Run this command to enable the Bash shell:
     
    shell.set --enable True
     
  4. Run this command to access the Bash shell:
     
    shell
  5. In the Bash shell, run this command to change the default shell to Bash:

    chsh -s /bin/bash root
     
  6. Use WinSCP to upload the certificate files to the vCenter Server Appliance.
  7. To return to the Appliance Shell, run this command:

    chsh -s /bin/appliancesh root

image[3]

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Unable to remove an inaccessible NFS datastore

August 27th, 2014 3 comments

The backend storage volume corresponding to the datastore has been removed and the datastore appears as Inactive, when I want to remove (via vSphere Client connected to vCenter server) the NFS datastore I receive this error message:

Unmounting the datastore in vCenter Server fails with the error:
‘Call “HostDatastoreSystem.RemoveDatastore” form object “datastoreSystem-28” on vCenter Server “xxxx” failed. CannotRemove datastore ‘datastore_name’ because Storage I/O control is enabled on it. Correct it and re-try the operation

image

 

Solution:

To resolve this issue, log in directly to each ESXi host that has access to the inactive datastore and manually remove it.

– Connect to the vSphere ESXi host using SSH

– Run this command to list the mounted datastores:

esxcli storage nfs list

image

– Run this command to unmount the NFS datastore:

esxcli storage nfs remove –v datastorename

image

The inactive NFS datastore has been removed

Note: if your datastore display name have some spaces, please use quotes

 

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Install Broadcom 5720 network adapter

March 20th, 2013 2 comments

Today I installed a new Dell PowerEdgde R620 host with vSphere 5.0 update 1. The Intel Ethernet I350 adapter was recognized and installed correct but the Broadcom 5720 wasn’t. I downloaded the latest Broadcom driver CD from VMware and uploaded the extracted content to my local datastore.
To install the drivers I used the following command:

esxcli software vib install -v /vmfs/volumes/pathtodatastore/NIC/net-tg3-3.120h.v50.2-1OEM.500.0.0.472560.x86_64.vib

^ full path to the file must be specified

image
After reboot the Broadcom adapter was installed successfully:

image

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Call "HostDatastoreSystem.QueryVmfsDatastoreCreateOptions" for object "ha-datastoresystem" on ESXi "SERVERNAME" failed.

February 27th, 2012 20 comments

After I placed two new 146 GB SAS hard disks to an ESXi 4.1 host, configured a new array, try to add a new datastore with my vSphere Client I received this warning:

Call “HostDatastoreSystem.QueryVmfsDatastoreCreateOptions” for object “ha-datastoresystem” on ESXi “SERVERNAME” failed.

image

After reading VMwareKB 1008886 and following the instructions I solved the issue..


Solution:

image

Commandline:

dd if=/dev/zero of="/vmfs/devices/disks/vml.0000000000766d686261313a313a30" bs=512 count=34 conv=notrunc

Output:

34+0 records in
34+0 records out

 

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: No SSH access after upgrade to vSphere 4.1

August 13th, 2010 No comments

After upgrading the datacenter from vSphere 4.0 to 4.1 I was unable to connect with my service account “esxuser” by putty or console or Veeam to make some backups, warning message: Access denied

I changed my password a few times.. maybe it was changed, I restarted the SSH service.. no luck.. I created a new account with shell access but still the same deny!

image

Solution:

Connect direct your ESX console by VI client, go to Permissions tab and add your service account with Administrator rights:

 

image

Yeah, I was able to connect again with my service account.. 🙂

image

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn