OpenManage on vSphere 4

 

1. From support.dell.com download OMI-SrvAdmin-Dell-Web-LX-620-677.esx40.tar.gz or the latestest caompatible version of openmanage.

2. Transfer OMI-SrvAdmin-Dell-Web-LX-620-677.esx40.tar.gz to the ESX server…preferably into the /tmp directory using FastSCP or winscp.

3. Using putty, run this command from that directory: tar –zxvf OMI-SrvAdmin-Dell-Web-LX-620-677.esx40.tar.gz

4. Cd into the linux/supportscripts directory

5. Run ./srvadmin-install.sh and follow the guided install.

 

#in the line com2sec notConfigUser default public

#change public to the string

# make sure #”smuxpeer .1.3.6.1.4.1.674.10892.1” #is at the end of the file

nano /etc/snmp/snmpd.conf

Run the following:

/sbin/service snmpd restart

srvadmin-services.sh restart

/usr/sbin/esxcfg-firewall -e snmpd

 

Home to atthedatacenter.com

Hope it helps

dw

Advertisements

error “Failed to Open File” when trying to perform a P2V with the VMware Converter tool

I was receiving an error “Failed to Open File” when trying to perform a  P2V with the VMware Converter tool.  It turned out not to actually be a file or permissions problem but a DNS resolution issue.  When Virtual Center passes the information to the Converter Agent on the host being migrated it sends the host name, not the IP address of the ESX server.  If the machine can’t resolve that name it will fail with the “Failed to Open File” error.

One way to fix this is with a host file. Add the vcenter server and esx host to the host file of the machine to be converted if a DNS server resolution is not an option for the client. You should always have a DNS server for your ESX environment so adding a record there if needed would work.

 

Home to atthedatacenter.com

Hope it helps

dw

Error adding ESX 3.5 to vCenter 4.0 – No License server

 

So the customer didn’t ever have a license server. It was a fresh install of vSphere 4 and vCenter 4. We wanted to add an existing ESX 3.5 server to vCenter to move the VM’s to the new vSphere cluster. I received this error:

“vi3 host cannot be added if vcenter is licensed but license server is not configured. configure license server and try again.”

clip_image001

Research will show –

According to http://www.vmware.com/pdf/vsp_4_legacy_host_lic.pdf,  "vCenter Server 4.0 does not require a license server to manage ESX 4.0/ESXi 4.0 hosts. vCenter Server 4.0 requires a license server to manage ESX 3.x/ESXi 3.5 hosts. If you do not have a license server installed and you need one, download the VMware License Server from the VMware Web site."

I haven’t found a separate download for the license server, but I did discover its on the vCenter CD.

Look in the vpx folder for VMware-licenseserver.exe on the vCenter 4.0 cd.

Hope it saves some search and download time.

Home to atthedatacenter.com

Hope it helps

dw

ESX 4 Service Console partitioning

VMware has changed the recommended ESX 4 Service Console partitioning from previous versions. The following Custom Partitioning Design are from the vSphere Essentials PoC delivery guide(s) found in the vSphere 4 Services Kit:

 

Mount Point

Type

Size

Purpose

/

ext3

5.0GB

The / (or “root”) partition stores the ESX system and all files not stored in another custom partition. If this partition is filled to capacity, the ESX host could crash. It is imperative to prevent this.

 

swap

1.6GB

The swap partition is used to supplement RAM if the service console runs out of physical memory.

/home

ext3

512MB

The /home partition is created as a failsafe to help prevent / from filling up. Service console accounts (not vCenter) each have an associated /home folder. As a best practice, administrators should not use these folders for storage. If service console accounts are to be used and there are multiple users requiring access, the size of this partition may need to be increased. By default, /home is part of the / partition. By creating a custom partition for it the / partition will be protected if /home fills to capacity.

/tmp

ext3

2.0GB

The /tmp partition is also created as a failsafe to help prevent filling the / partition. /tmp is often used to untar support files, temporarily store copied logs and stage patches. By default, /tmp is part of the / partition. By creating a custom partition for it the / partition will be protected if /tmp fills to capacity.

/vmimages

ext3

512MB

Traditionally, /vmimages was used to store CD-ROM images (.ISOs) and Floppy Disk images (.flp, .img). However, most organizations following best-practices have moved this from each individual host to a single shared-storage location. However, by default ESX creates a /vmimages folder within / . This makes it dangerously easy for an Administrator to mistake it for the shared-storage repository and copy images into it that will fill / . As a failsafe to help prevent this, a small custom /vmimages partition can be created. If the local /vmimages folder is actually used, this size may need to be increased.

/var

ext3

2.0GB

The /var partition stores most system logs. Creating a custom /var partition provides substantial, dedicated log storage space (/var/log) while protecting the / partition from being filled by log files. Normally /var is part of the / partition.

· The installer also automatically creates the following partitions without displaying them:

/boot

ext3

260MB

/boot stores the files necessary to boot the service console.

 

vmkcore

100MB

The vmkcore partition temporarily stores log and error information should the VMkernel crash.

Home to atthedatacenter.com

Hope it helps

dw

VMware Resources

Disable CTRL-ALT-DEL on vSphere

If you hit CTRL-ALT-DEL on a vSphere console, the server will reboot even if there are running VMs and it has not been put in Maintenance Mode. This has been disabled by editing /etc/inittab,so these two lines are remarked out.

# Trap CTRL-ALT-DELETE

# ca::ctrlaltdel:/sbin/shutdown -t3 -r no

http://www.delltechcenter.com/page/vSphere+4+Default+and+CTRL-ALT-DEL

 

Home to atthedatacenter.com

Hope it helps

dw