During the BETA of vSphere 4.1, there were some inconsistencies in some of the build numbers which was eventually resolved. It looks like something was still missed in the final RTM release of vSphere 4.1 ....
Here is a screenshot of the python libraries on classic ESX 4.1 used for esxupdate. At some point, it looks like this release was going to be named vSphere 4.5 as most people had anticipated, but then was revised to 4.1.
I'm sure there will be few more easter eggs, happy hunting 🙂
Following part1 and part2 of new vSphere 4.1 CLI Utilities, here are some new vimsh commands:
For ESX use /usr/bin/vmware-vim-cmd
For ESXi use /bin/vim-cmd
1. vmsvc/power.suspendResume is used for vMotion and sVMotion tasks before switching over to the new VM.
[root@esx4-1 ~]# vmware-vim-cmd vmsvc/power.suspendResume
Insufficient arguments.
Usage: power.suspendResume vmid
Suspend & resume the specified virtual machine.
2. vmsvc/queryftcompat allows you to query a given Virtual Machine to check for Fault Tolerance compatibility.
[root@esx4-1 ~]# vmware-vim-cmd vmsvc/queryftcompat
Insufficient arguments.
Usage: queryftcompat vmid
Query FT compatibility for a VM.
3. vimsvc/auth/lockdown_is_enabled allows you to query if the host has the lockdown feature enabled, this is only applicable to ESXi.
~ # vim-cmd vimsvc/auth/lockdown_is_enabled
false
4. vimsvc/auth/lockdown_is_possible allows you to check if you can put the host into lockdown mode.
~ # vim-cmd vimsvc/auth/lockdown_is_possible
true
5. vimsvc/auth/lockdown_mode_enter allows you to enter lockdown mode on an ESXi host.
~ # vim-cmd vimsvc/auth/lockdown_mode_enter
6. vimsvc/auth/lockdown_mode_exit allows you to exit lockdown mode on an ESXi host.
~ # vim-cmd vimsvc/auth/lockdown_mode_exit
The next two commands refer to the following services which can also be configured using the vSphere Client:
7. hostsvc/start_local_tsm allows you to enable Local Tech Support Mode on an ESXi host.
~ # vim-cmd hostsvc/start_local_tsm
8. hostsvc/start_remote_tsm allows you to enable Remote Tech Support Mode (SSH access) on an ESXi host.
~ # vim-cmd hostsvc/start_remote_tsm
9. hostsvc/stop_local_tsm allows you to disable Local Tech Support Mode on an ESXi host.
~ # vim-cmd hostsvc/stop_local_tsm
10. hostsvc/stop_remote_tsm allows you to disable Remote Tech Support Mode (SSH access) on an ESXi host.
~ # vim-cmd hostsvc/stop_remote_tsm
With the new release of vSphere 4.1, there are new additions to the CLI utilities that administrators can leverage for configurations and troubleshooting. Although, not all were treated equally from an announcement and documentation standpoint.
Here is an example of the new version of vmkfstools and -D option:
2. storageRM is a debugging utility for Storage I/O Control at the host level.
Default Values:
SleepTime: 4000
Threshold: 35
Gamma: 0.25
Beta-per-host: 4.00
LowerBound: 4
UpperBound: 64
Storage I/O Control-- This tool does flow control at the host
in order to maintain disk I/O latency close to a
threshold and queue sizes converge at values
proportional to the beta parameter.
The following histogram related options are available:
-a, --print the list of all luns, their latency threshold,
queue depths and if Storage I/O Controlis set/unset
-b, --Beta per host value
-d
-f, --force the run without checking version or checksum
-g, --defGamma value for use in control equation
-h, --help will print the usage
-l, --lower bound on the length of lun queue, (default 4)
-n, --no anomaly detection is done
-r, --reset issue queue for all luns to default
-s, --sleep time in ms for periodic execution
-t, --threshold on the latency (in ms), for rate control
-u, --upper bound on the length of lun queue (default 64)
-v, --debug log level value
storageRM Usage:
storageRM [options]
Usage: [-d] [-t time] [-v] [-s threshold]
-d run in daemon mode
-t daemon sleep period in seconds, minimum 10 seconds
-v run with verbose logging
-s saturate threshold [10, 100], i.e. 60 for 60% of line rate
Warning: This is an unsupported command. Use at your own risk.
net-dvs -a [ -P maxPorts] switch_name
net-dvs -d switch_name
net-dvs [ -A | -D ] -p port switch_name
net-dvs [ -s name=value | -u name ] -p port switch_name
net-dvs -l [ switch_name ]
net-dvs -i (init database)
net-dvs [-S | -R | -G ]
net-dvs -T
net-dvs -v "vlanID[;t|p[0-7][;min-max,min-max...]]
net-dvs -V "primaryVID,secondaryVID,i|c|p;primaryVID,secondaryVID,i|c|p..."
net-dvs -m "sid;dname;snaplen;
[oiveld];encapvlan;wildcardsIn,wildcardsOut;dstPort1,dstPort2,...;srcInPort1,srcInport2,...;srcOutPort1,srcOutPort2,...;:sid2;dname2..."
net-dvs dvswitch -k "respool1_id;respool2_id;..."
net-dvs dvswitch -p dvport -K "respool1_id:shares:limit;respool2_id:shares:limit;..."
net-dvs dvswitch -p dvport -z "respool_id"
net-dvs dvswitch -j [activate|deactivate]
net-dvs -L uplink_name1[,uplink_name2,...] -t team_policy_type -p port switch_name
net-dvs dvswitch -H "red|yellow|green:some message" switch_name
net-dvs -o "depth,param|classname;depth,param|classname;... -p port|globalPropList switch_name
net-dvs --mtu mtu_value [-p dvport] switch_name
net-dvs --x 0|1 -p dvport switch_name
net-dvs --vlan vlanID -p dvport switch_name
net-dvs --reset -p dvport switch_name
net-dvs --cap cap_value -p dvport switch_name
net-dvs --states -p dvport switch_name
VMware remote Device Connect
Usage: /usr/lib/vmware/bin/remoteDeviceConnect OPTIONS filename
Options:
-h
-p
-t
-d
-n
-f
-A : use Authd to connect
-U
-V
-P
Examples:
remoteDeviceConnect -t floppy -d floppy0 -f device /dev/fd0
remoteDeviceConnect -t floppy -d floppy0 -f file image.flp
remoteDeviceConnect -t usb "path:2/1 vid:0x0547 pid:0x2131"
sensord: failed to open ipmi device: No such file or dir
sensord: unsupported hardware
statedumper [-f filename] [-s off] [-e off] [-b] [-o] [-r] [-x]
The following options are supported:
-e
-f
-o - output entry offsets
-r
-s
-b - filter on branch count, use -s and -e for start/end
-x - dump extra debug data
/usr/lib/vmware/bin/vmkeventd: invalid option -- h
Usage: /usr/lib/vmware/bin/vmkeventd [-d]
9. analyze-esx-init-boot.py looks like a debugging utility to analyze the COS boot up logs
[root@esx4-1 ~]# /usr/sbin/analyze-esx-init-boot.py -s -S /vmfs/volumes/datastore1/esxconsole-4c27dd75-a38d-5044-5670-005056927558/logs/sysboot.log -V /var/log/messages
ERROR: Could not find 'cpu 0: early measured tsc speed' in the log
This is one of the very first log messages after boot
POST boot times will not be relevant
Unable to find vsish. Please ensure that you have debugging tools installed and your PATH is correctly setup.
VMKernel: 0.0000 secs
POST Tests: 0.0000 secs
Init Scripts: 0.0000 secs
ESX Boot Time: 0.0000 secs
Hardware/BIOS: 0.0000 secs
Total Boot Time: 0.0000 secs
Serial port output was on