VSAN-Troubleshooting-Reference-Manual

Diagnostics and Troubleshooting Reference Manual – Virtual SAN
provided (which is the same IP address as the vCenter Server Appliance where RVC
is running).
Note that you do not need to supply a username, password or hostname in the rvc
command line. If you do not, RVC will simply prompt you to each of these in turn.
ie-vcva-01:~ # rvc
Host to connect to (user@host): administrator:vmware@192.168.1.100
password:
0 /
1 localhost/
>
In the above example, “administrator” was the privileged user that logged into
RVC. This may need some further clarification as vSphere can support a number of
different sources for users. For example, the user might be a local user on the
vCenter Server Appliance (e.g. root), or it could be a Single Sign On (SSO) user such
as administrator@vsphere.local or indeed an Active Directory (AD) user. The
“default domain” setting in vCenter’s Single Sign-On configuration determines
default domain for the administrator user.
The default domain in SSO is important as it determines which password should you
be supplying to login to not just RVC, but also the vSphere web client. As mentioned,
there are multiple administrator users in vSphere environments. It could be the AD
administrator, the SSO administrator or in the case of Windows vCenter Servers, the
local administrator. This has caused a little confusion in the past, which is why we
are taking the time to explain it here.
To check the current default domain settings, login to the vSphere web client as
administrator@vsphere.local, navigate to Administration > Single Sign-On >
Configuration > Identity Sources. There are entries for the vsphere.local domain, the
Local OS and Active Directory if it is configured. One of these will be the default, and
this has a direct bearing on which administrator is the default one when
administrator is used as the username when attempting to launch RVC.
In the above example, localos is the default. Therefore RVC will attempt to find a
local user to authenticate for RVC. If this is the vCenter Server Appliance, which runs
Linux, it is unlikely that there will be a local privileged user called administrator.
Therefore an attempt to launch RVC with this user will typically not work. Note that
this is not a consideration specific to RVC. This will not allow a log via the vSphere
V M W A R E S T O R A G E B U D O C U M E N T A T I O N / 75