Skip to main content

Toggling the vCenter Server Appliance default shell

  Purpose

This article provides vSphere Administrators steps to toggle between default shells available on the vCentrer Server Appliance (vCSA).
Resolution
Currently, the vCSA is bundled with these supported shells:
  • BASH Shell
  • Appliance Shell

Switching the vCenter Server Appliance 6.x to BASH Shell

  1. Log in to the vCenter Server Appliance through SSH.
  2. Run this command to enable access the Bash shell:

    shell.set --enabled true
     
  3. Type shell and press Enter.
  4. In the temporary BASH shell, run this command to permanently configure the default Shell to BASH for Root:

    chsh -s /bin/bash root
     
  5. Log out from the BASH Shell.
  6. Log in again for the changes to take effect.
Note: For 6.7 please do the below.
  1. Log in to the vCenter Server Appliance through SSH.
  2. Type shell and press Enter.
  3. In the temporary BASH shell, run this command to permanently configure the default Shell to BASH for Root:

    chsh -s /bin/bash root
     
  4. Log out from the BASH Shell.
  5. Log in again for the changes to take effect.

Switching the vCenter Server Appliance 6.x to Appliance Shell

  1. Log in to the vCenter Server Appliance through 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 Appliance Shell.
  4. Log in again for the changes to take effect.
Related Information

Note: This KB explains how to enable SSH on VCSA and also login issues with VCSA.
If you see the error message Access Denied when logging into an SSH session, see 2146205.

切换 vCenter Server Appliance 6.x 默认 shell
"Access Denied" error when using SSH to login to the appliance

Comments

  1. Toggling The Vcenter Server Appliance Default Shell >>>>> Download Now

    >>>>> Download Full

    Toggling The Vcenter Server Appliance Default Shell >>>>> Download LINK

    >>>>> Download Now

    Toggling The Vcenter Server Appliance Default Shell >>>>> Download Full

    >>>>> Download LINK fe

    ReplyDelete

Post a Comment

Popular posts from this blog

Error [403] The maximum number of sessions has been exceeded in the H5 client during login or logout

  Symptoms In virgo log, you see messages similar to: [2020-05-19T07:25:45.285Z] [ERROR] http-nio-5090-exec-130 72026859 142953 501051 com.vmware.vise.security.spring.DefaultAuthenticationProvider logout failed for sessionId 142953, clientId 501051 java.lang.IllegalStateException: The specified cardinality of 1..1 for osgi:reference implementing com.vmware.vcenter.apigw.api.ApiGatewaySessionManager in bundle com.vmware.h5ngc requires that exactly one OSGI service satisfies the filtering criteria but no such service was found.         at com.vmware.o6jia.context.ExternalServiceTargetSource.getTarget(ExternalServiceTargetSource.java:99)         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:192)         at com.sun.proxy.$Proxy159.logout(Unknown Source)   ...

Investigating virtual machine file locks on ESXi

      Details Adding an existing virtual machine disk (VMDK) to a virtual machine that is already powered on fails.                 Failed to add disk scsi0:1. Failed to power on scsi0:1   Powering on the virtual machine results in the power on task remaining at 95% indefinitely. Cannot power on the virtual machine after deploying it from a template. Powering on a virtual machine fails with an error: Unable to open Swap File Unable to access a file since it is locked Unable to access a file <filename> since it is locked Unable to access Virtual machine configuration In the /var/log/vmkernel log file, you see entries similar to: WARNING: World: VM xxxx: xxx: Failed to open swap file <path>: Lock was not free WARNING: World: VM xxxx: xxx: Failed to initialize swap file <path>   When opening a console to the virtual machine, you may receive ...

"Performance data is currently not available for this entity" viewing the performance tab

  Symptoms While accessing the performance tab and navigating to Overview, you see: No data available   The data for Real time, but fails to retrieve it for past 1 day, week, month or year.  While selecting the advance parameter in performance tab, you see: Performance data is currently not available for this entity Cause This issue is caused by the vCenter Server database (Postgress) containing a stale/future time stamp reference for the ESXi host when the data was collected. For vCenter Servers using SQL, see  "Performance data is currently not available for this entity" error after updating rollup in vSphere Resolution Backup the vCenter...