Knorrhane

Start webaccess Vsphere 4

nikkar — Mon, 31 Aug 2009 07:36:30 GMT

service vmware-webAccess start

To make the service start automatically at each ESX reboot, type

chkconfig -level 3 vmware-webAccess on

VMware Port Requirements

nikkar — Tue, 21 Apr 2009 18:46:52 GMT

http://myitforum.com/cs2/blogs/phoward/archive/2009/03/29/vmware-port-requirements.aspx

Remove snapshot task times out in VirtualCenter but still runs on ESX

nikkar — Tue, 21 Apr 2009 08:16:09 GMT

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1008504

IPMI_SI during boot up

nikkar — Fri, 19 Dec 2008 08:25:55 GMT

http://communities.vmware.com/thread/132882

change the download location for update manager

nikkar — Mon, 08 Sep 2008 20:25:00 GMT

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004152

Choose the right block size when you create vmfs datastore

nikkar — Sun, 07 Sep 2008 18:33:00 GMT

From http://itknowledgeexchange.techtarget.com/virtualization-pro/choosing-a-block-size-when-creating-vmfs-datastores/

When you create a VMFS datastore on your VMware ESX servers many administrators select the default 1MB block size without knowing when or why to change it. The block size determines the minimum amount of disk space that any file will take up on VMFS datastores. So an 18KB log file will actually take up 1MB of disk space (1 block) and a 1.3MB file will take up 2MB of disk space (2 blocks). But the block size also determines the maximum size that any file can be, if you select a 1MB block size on your data store the maximum file size is limited to 256GB. So when you create a VM you cannot assign it a single virtual disk greater then 256GB. There is also no way to change the block size after you set it without deleting the datastore and re-creating it, which will wipe out any data on the datastore.

Because of this you should choose your block size carefully when creating VMFS datastores. The VMFS datastores mainly contain larger virtual disk files so increasing the block size will not use all that much more disk space over the default 1MB size. You have the following choices when creating a datastore:

1MB block size - 256GB maximum file size
2MB block size - 512GB maximum file size
4MB block size - 1024GB maximum file size

• 8MB block size - 2048GB maximum file size

Besides having smaller files use slightly more disk space on your datastore there are no other downsides to using larger block sizes. There is no noticeable I/O performance difference by using a larger block size. When you create your datastore, make sure you choose your block size carefully. 1MB should be fine if you have a smaller datastore (less than 500GB) and never plan on using virtual disks greater then 256GB. If you have a medium (500GB - 1TB) datastore and there is a chance that you may need a VM with a larger disk then go with a 2MB or 4MB block size. For larger datastores (1TB - 2TB) go with a 4MB or 8MB block size. In most cases you will not be creating virtual disks equal to the maximum size of your datastore (2TB) so you will usually not need a 8MB block size.

So remember, choose carefully, once you create your datastore there is no changing it later.

How to identify your pci devices such as nics

nikkar — Tue, 02 Sep 2008 19:10:00 GMT

Find a got post on vm/etc

http://vmetc.com/2008/05/26/trouble-pinging-multiple-nic-esx-host-after-install/

ESXi ssh non root user

nikkar — Mon, 18 Aug 2008 19:43:00 GMT

http://www.yellow-bricks.com/2008/08/14/esxi-ssh-and-non-root-users/#comment-860

Enable SSh on esxi 3 3.5

nikkar — Sun, 17 Aug 2008 18:58:00 GMT

ESXi 3.5 does ship with the ability to run SSH, but this is disabled by default (and is not supported).

1) At the console of the ESXi host, press ALT-F1 to access the console window.
2) Enter unsupported in the console and then press Enter. You will not see the text you type in.
3) If you typed in unsupported correctly, you will see the Tech Support Mode warning and a password prompt. Enter the password for the root login.
4) You should then see the prompt of ~ #. Edit the file inetd.conf (enter the command *vi /etc/inetd.conf*).
5) Find the line that begins with #ssh and remove the #. Then save the file. If you're new to using vi, then move the cursor down to #ssh line and then press the Insert key. Move the cursor over one space and then hit backspace to delete the #. Then press ESC and type in :wq to save the file and exit vi. If you make a mistake, you can press the ESC key and then type it :q! to quit vi without saving the file.
6) Restart host or try kill -HUP `ps | grep inetd`

Link to Remote Command-Line Interface

nikkar — Wed, 13 Aug 2008 18:14:00 GMT

http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_rcli.pdf

Install esxi 3.5 in vmware workstation 6.5 beta build 99530

nikkar — Mon, 11 Aug 2008 20:54:00 GMT

Create a new virtual machine choose custom advanced.

Choose operatingsystem Other Linux 64bit

Then choose the lsilogic scsi kontroller.

Then choose the appropriet memory and disk settings.

remove the virtual machine from favorite list.

Edit the vmx file and add line: monitor_control.restrict_backdoor = "true"

Start the virtual machine and boot from the .iso file.

Install esxi.

Link to VI Team Blog and the best practise deploying VI part one and two

nikkar — Mon, 11 Aug 2008 11:18:00 GMT

http://blogs.vmware.com/vi/2008/07/top-tips-for-de.html

http://blogs.vmware.com/vi/2008/08/top-tips-for-de.html

Tech support mode ESXi

nikkar — Fri, 08 Aug 2008 10:34:00 GMT

If you want to see the hardware the ESXi has recognized.

From the main screen, press ALT+F1
Type "unsupported" (no quotes)
Enter the root password
Type "lspci" and it will show you the devices it sees.

How to add the sql agent jobs manually

nikkar — Thu, 12 Jun 2008 07:23:00 GMT

Adding the SQL Server Agent Jobs To add a SQL Server Agent Job:

Open SQL Management Studio using the database login used by VirtualCenter to connect to the database (typically not SA or Administrator). See Administrative Credentials are required for Oracle and SQL Server databases when installing or upgrading Virtual Center (1003052) to ensure you have the correct permissions.
Click New Query.
Copy the contents of job_schedule1_mssql.sql into your query window. The script is located in the install directory. The default location is C:\Program Files\VMware\Infrastructure\VirtualCenter Server.
Select your VirtualCenter database from the Database dropdown.
Execute the script.
Repeat steps 2-5 for job_schedule2_mssql.sql and job_schedule3_mssql.sql.

Note: This article does not apply to installations using Oracle or Microsoft SQL Server 2005 Express. Note: The SQL Server Agent is not available in Microsoft SQL Server 2005 Express. Historic data is managed by the VirtualCenter Server service.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004382

Script shutdown all vm from service console

nikkar — Tue, 10 Jun 2008 13:14:00 GMT

Here is a bash script to power off all active VMs on a host.

#!/bin/bash
* IFS='*
* '*
* for vm in `vmware-cmd -l`*
* do*
* name=`vmware-cmd "$vm" getconfig displayname -q`*
* state=`vmware-cmd "$vm" getstate -q`*
* if *
* then*
* echo "Trying to power off $name...."*
* output=`vmware-cmd "$vm" stop trysoft`*
* if $? -eq 0 ; then*
* echo "$name was powered off successfully."*
* fi*
* fi*
* done*
This script was posted some time ago on the VMTN forumsby Alex, but he has now been updated it to report if each VM has successfully powered off