Setting these variables will enable the execution script listed in Step 4 (
csiprep.py
) to create a user
account on the ESX/vSphere Server (if it does not already exist), add that user to the
sudoer
file, and
then add the key for that user to the authorized key file. If the user account does not currently exist,
then the
csiprep.py
script creates it with the following settings:
n
username = CSI_USER
n
group name = User name
n
uid = Next user ID available in /etc/passwd (Example: If the last one used is 506, then the next
user would be 507.)
n
password = None set (An Administrator must set the password. This account can also be used
for Web Services communication.)
n
home directory = /home/<new_user>/.ssh/authorized_keys
n
shell = :/bin/bash
4. You must be
root
to run the prep script. Additionally, you must also have the
root
password or
existing sudo access, as an account may be created and the sudo config file is modified. The
/etc/sudoers
configuration file is modified to grant root access for the CSI_USER account, which
enables VCM to collect information that requires root access from the ESX Service Console Operating
System. If you have a root access password, execute the following in the command prompt:
su —
cd <directory location of files copied>
python csiprep.py
If you have sudo access with your current account, execute the following in the command prompt:
sudo python csiprep.py
The ESX/vSphere Server should now have a new/modified account for CSI_USER, full sudo settings,
and the public key stored in the /home/$CSI_USER/.ssh/authorized_keys. The CSI_USER variable can
be an existing account (in which case the account will have any missing elements set up, such as sudo
or .ssh).
5. Once you complete this step, a log file is generated (
csiprep.log
). At this point you may remove the
files. It is recommended that you keep the .log file for troubleshooting purposes.
Adding ESX/vSphere Servers to VCM
Use the following procedure to manually add your ESX/vSphere Server into VCM’s list of Available
Machines if they were not included in a discovery.
In VCM:
1. Click
Administration | Machines Manager | Available Machines | Available UNIX Machines
.
2. Click
Add Machines
. The
Add Machines
page of the
Discovery Manual Machine Entry
wizard
appears.
Getting Started with VCM for Virtualization
VMware, Inc.
125
Summary of Contents for VCENTER CONFIGURATION MANAGER 5.3
Page 8: ...vCenter Configuration Manager Installation and Getting Started Guide 8 VMware Inc...
Page 46: ...vCenter Configuration Manager Installation and Getting Started Guide 46 VMware Inc...
Page 158: ...vCenter Configuration Manager Installation and Getting Started Guide 158 VMware Inc...
Page 178: ...vCenter Configuration Manager Installation and Getting Started Guide 178 VMware Inc...
Page 194: ...vCenter Configuration Manager Installation and Getting Started Guide 194 VMware Inc...
Page 204: ...vCenter Configuration Manager Installation and Getting Started Guide 204 VMware Inc...
Page 208: ...vCenter Configuration Manager Installation and Getting Started Guide 208 VMware Inc...
Page 234: ...vCenter Configuration Manager Installation and Getting Started Guide 234 VMware Inc...
Page 264: ...vCenter Configuration Manager Installation and Getting Started Guide 264 VMware Inc...
Page 274: ...274 VMware Inc vCenter Configuration Manager Installation and Getting Started Guide...