Archive for June, 2010


To Rename vSwitch name in a ESX box , Do the following :

logon to your SC(Esx Concole via ssh)  and Edit the file:
/etc/vmware/esx.conf

change the following line

/net/vswitch/child0001/name = “vSwitch1”

to:
/net/vswitch/child0001/name = “NEWSwitch_name”

save and reboot your ESX Server.


Ref : http://www.redhat.com

To begin a kickstart installation, you must boot the system from a Red Hat Linux boot diskette, Red Hat Linux boot CD-ROM, or the Red Hat Linux CD-ROM #1 and enter a special boot command at the boot prompt. The installation program looks for a kickstart file if the ks command line argument is passed to the kernel.

Boot Diskette
If the kickstart file is located on a boot diskette as described in Section 7.8.1 Creating a Kickstart Boot Diskette, boot the system with the diskette in the drive, and enter the following command at the boot: prompt:

linux ks=floppy
CD-ROM #1 and Diskette
The linux ks=floppy command also works if the ks.cfg file is located on a vfat or ext2 file system on a diskette and you boot from the Red Hat Linux CD-ROM #1.

An alternate boot command is to boot off the Red Hat Linux CD-ROM #1 and have the kickstart file on a vfat or ext2 file system on a diskette. To do so, enter the following command at the boot: prompt:

linux ks=hd:fd0:/ks.cfg
With Driver Disk
If you need to use a driver disk with kickstart, specify the dd option as well. For example, to boot off a boot diskette and use a driver disk, enter the following command at the boot: prompt:

linux ks=floppy dd
Boot CD-ROM
If the kickstart file is on a boot CD-ROM as described in Section 7.8.2 Creating a Kickstart Boot CD-ROM, insert the CD-ROM into the system, boot the system, and enter the following command at the boot: prompt (where ks.cfg is the name of the kickstart file):

linux ks=cdrom:/ks.cfg

Other options to start a kickstart installation are as follows:

ks=nfs:<server>:/<path>
The installation program will look for the kickstart file on the NFS server <server>, as file <path>. The installation program will use DHCP to configure the Ethernet card. For example, if your NFS server is server.example.com and the kickstart file is in the NFS share /mydir/ks.cfg, the correct boot command would be ks=nfs:server.example.com:/mydir/ks.cfg.

ks=http://<server>/<path>
The installation program will look for the kickstart file on the HTTP server <server>, as file <path>. The installation program will use DHCP to configure the Ethernet card. For example, if your HTTP server is server.example.com and the kickstart file is in the HTTP directory /mydir/ks.cfg, the correct boot command would be ks=http://server.example.com/mydir/ks.cfg.

ks=floppy
The installation program looks for the file ks.cfg on a vfat or ext2 file system on the diskette in /dev/fd0.

ks=floppy:/<path>
The installation program will look for the kickstart file on the diskette in /dev/fd0, as file <path>.

ks=hd:<device>:/<file>
The installation program will mount the file system on <device> (which must be vfat or ext2), and look for the kickstart configuration file as <file> in that file system (for example, ks=hd:sda3:/mydir/ks.cfg).

Note Note
The second colon is a syntax chane for Red Hat Linux 9.
ks=file:/<file>
The installation program will try to read the file <file> from the file system; no mounts will be done. This is normally used if the kickstart file is already on the initrd image.

ks=cdrom:/<path>
The installation program will look for the kickstart file on CD-ROM, as file <path>.


Create Privileges

  1. Click “View | Administration | Roles”
  2. Right client and cick “Add”
  3. Select a name and select the required privileges

Create User

  1. Click on the “Users and Groups” tab
  2. Click on the “Users” button
  3. Right click and select “Add”
  4. Specify the desired User Name, Password, etc and Click “OK”

Create a Local Group

  1. Click on the “Groups” button
  2. Right click and select “Add”
  3. Enter the group name you want and enter the User Name you created above in the User Name field and click Add
  4. Click “OK” to create the group

Assign Permissions

  1. Click on the “Permissions” Tab
  2. Right click and Select “Add Permission”
  3. Click on the “Add” button and select the Group you created above and click on the Add button.
  4. Click on the OK button.
  5. Choose the Assigned Role (Priviages) and click “OK”.

Note : You can use the permissions tab in either the main inventory (main page) or per Virtual Machine. This is useful to know if you need to allow one user to access just one Virtual Machine.


Error : Got the following error while configuring HA on 2 ESX Cluster.

  • HA agent configuration errors on ESX hosts:
    • Failed to connect to host
    • Failed to install the VirtualCenter agent
    • cmd addnode failed for primary node: Internal AAM Error – agent could not start
    • cmd addnode failed for primary node:/opt/vmware/aam/bin/ft_startup failed
  • Solution :

    It could be for several Reason Like below.

  • Check the release notes for current releases to see if the problem has been resolved in a bug fix. See the Documentation page for vSphere 4 or VMware Infrastructure 3.

  • Verify that there are enough licenses to configure VMware HA. For more information, see Verifying that the feature is licensed (1003692).
  • Verify that name resolution is correctly configured on the ESX Server. For more information, see Identifying issues with and setting up name resolution on ESX Server (1003735).

  • Verify that name resolution is correctly configured on the vCenter Server. For more information, see Configuring name resolution for VMware VirtualCenter (1003713).

  • Verify that the time is correct on all ESX Servers with the date command. For more information on setting up time synchronization with ESX Server, see Installing and Configuring NTP on VMware ESX Server (1339).

  • Verify that network connectivity exists from the VirtualCenter Server to the ESX Server. For more information, see Testing network connectivity with the Ping command (1003486).

  • Verify that network connectivity exists from the ESX Server to the isolation response address. For more information, see Testing network connectivity with the Ping command (1003486).

  • Verify that all of the required network ports are open. For more information, see Testing port connectivity with the Telnet command (1003487).

  • Determine if there is a cluster resource issue. For more information, see Advanced Configuration options for VMware High Availability (1006421).

  • Verify that the correct version of the VirtualCenter agent service is installed. For more information on determining agent versions and how to manually uninstall and reinstall the HA agents on an ESX host, see Verifying and reinstalling the correct version of VMware VirtualCenter Server agent (1003714).

  • Verify the VirtualCenter Server Service has been restarted. To restart the VirtualCenter Server Service, see Stopping, starting, or restarting the vCenter Server service (1003895).
  • Verify that VMware HA is only attempting to configure on one Service Console. For more information, see VMware High Availability configuration issues when an iSCSI Service Console is on the same network (1003789).

  • Verify that the VMware HA cluster is not corrupted. To do this you need to create another cluster as a test. For more information, see Recreating VMware High Availability Cluster (1003715).
  • Verify that that UDP 8043 packets used for the HA backbone communications are not dropped between the ESX hosts. For more information see HA fails to configure after task passes 90% “Internal AAM Error – agent could not start” (1018217).
  • Ensure that the ESXi host userworld swap option is enabled. For more information see ESXi hosts without swap enabled cannot be added to a VMware High Availability Cluster (1004177).
  • My one was with Time configuration Mismatch beetween two esx.

    Follow my following Blog to set time and zone correctly.

    https://ashraf9719.wordpress.com/2010/05/31/redhat-changing-timezone/

    Redhat – Quota Implementation

    Posted: June 2, 2010 in Redhat

    The link is the best ever for Implementing QUOTA on Redhat/CentOS

    http://souptonuts.sourceforge.net/quota_tutorial.html