Hopefully a qucik query for the VI3 guru's.
We're finally getting ready to roll the product to replace our ailing 2.5 set up and having installed a play box with ESX 3.0.2 I dropped into putty to play with the command line stuff.
But apparently esxcfg does not exist on my set up and cannot be found via searching - is this something I need to install manually or do I have a faulty version of the product (it was dl'd from vmware and is fully and genuinely licensed)
I need you to SU a little different. Try this way "su -" the "-" add
the paths to the account
Sounds like you have not elevated your rights to root or equal. You need to do this before the esxcfg- command are available
Steve Beaver
VMware Communities User Moderator
*Virtualization is a journey, not a project.*
Esxcfg is actually a series of commands - e.g. esxcfg-mpath (manages multipathing) esxcfg-vswif for your IP interface, esxcfg-vswitch for your virtual switches.
The path to these commands is set up during install. Look in /usr/sbin for the whole list. There are several references that explain what each command does. Take a look at http://download3.vmware.com/vmworld/2006/tac9685.pdf for more information.
Something like that I think - I have logged in and 'su''d to be root and after some more trials have found the command set under /usr/sbin but even as root I cnnot run the dratted things.
Do I need to further up my rights?
I need you to SU a little different. Try this way "su -" the "-" add
the paths to the account
If you su - to root, you can type 'esxcfg-' and hit the tab key twice, will list the commands associated. This will make things easier to locate which command you want to use. Also notice the dash after esxcfg its part of the command.
Thanks guys the "-" did it - one for my little book of things to remember.
In linux when you do the switch user command 'su' by itself it just changes to that user and you pick up the user rights such as read/write/execute privileges on files. But when you su - ( it is short for -l (login) and it means that you are creating a login shell and as part of that it runs .bash_profile). This in effect switches the environment to that user which sets up things like the correct path, etc of the new user.
It is usually good practice to run su - when switching users.