mainesysadmin.com

esxRanger Pro 3.1 tvzc Manual Restore Details
esxRanger Pro product is unavailable to restore

Solution
This is a how-to restore a esxRanger Pro 3.1 tvzc backup by hand

Download this file from vizoncore.com
http://www.vizioncore.com/Downloads/ProductSupport/vcbrestore.zip
Extract and Copy vcbrestore to /tmp on the Vi3 host (note you can not run this binary from a VMFS)
Note: if you’re going to use WinScp make sure to “disable transfer resume” in preferences. This will remove any errors when sending large files to the VMFS3.
Run chmod 777 /tmp/vcbrestore
Create a directory on the VMFS3 where the VM will be contained.
Copy *.tvzc to the folder you just created on the VMFS.

List the files in the tvzc
/tmp/vcbrestore -D -I ./test_4.tvzc -O /dev/stdout | tar tvf - -O

Extract each file needed in the directory
/tmp/vcbrestore -D -I ./test_4.tvzc -O /dev/stdout | tar xvf - “each fie needed”
(If the vzc files are not on the VMFS where the VM will be created just use a path in the output file name)

Repeat for each file needed and remove .vzsnap off each file name
Register the VMX file the esx host
vmware-cmd -s register <full- path to the VMX>
You might still have to edit the VM in the Vi3 client to fix any issues.
Once the VM is up and running rm tvzc to remove the files from the VMFS.

http://hostname:8222

secedit /refreshpolicy machine_policy

This information was stolen from vmtn.net
http://www.vmware.com/community/message.jspa?messageID=423354

Re: SNMP Information from ESX3
Posted: Sep 29, 2006 8:48 AM in response to: cklemmer
Click to reply to this topic Reply

first edit snmpd.conf

1. vi /etc/snmp/snmpd.conf

configure it to point to the management server IP address
use a community name (here it’s public)

trapsink *.*.*.*
trapcommunity public

then start snmpd service

1. service snmpd start

configure it to autostart

1. chkconfig snmpd on

test it on local machine

1. snmpwalk -v 1 -c public localhost system

test it on another system (x.x.x.x is the esx server’s IP)

1. snmpwalk -v 1 -c public x.x.x.x system

configure your management server to receive SNMP and act upon.

This article applies to VMware ESX 3.0.1 in addition to older versions 2.5.3 - 3.0

VMware ESX server has snmpd daemon that can be used to monitor performance and send snmp traps
Virtual Center monitor many performance metrics, like CPU, Memory, network and disk I/O, but it is expensive and it is limited to those metrics.
What if you need to monitor disk space on /var/log partition? and want to receive an alert when it reaches 90%; What if you want to monitor httpd on ESX and receive a message when it fails.
If you are working in an environment with many servers and a team of systems administrators, you are most likely using a system monitoring tool or at least evaluating one.

* Edit snmpd.confWhatsup pro
# vi /etc/snmp/snmpd.conf
* Configure it to point to the management server IP address and use a community name (here it’s public)
trapsink *.*.*.* trapcommunity public
* Then start snmpd service
# service snmpd start
* Configure it to autostart
# chkconfig snmpd on
* Test it on local machine
#snmpwalk -v 1 -c public localhost system
* Test it on another system (x.x.x.x is the esx server’s IP)
#snmpwalk -v 1 -c public x.x.x.x system
* Open the firewall esxcfg-firewall -o 162,tcp,in,snmp
* Go to Whatsup machine (or any management station your have like Dell Open Manage IT Assistant or Nagios)
* Compile ESX MIBs from ESX server
/usr/lib/vmware/snmp/mibs/
VMWARE-ESX-MIB.mib
VMWARE-RESOURCES-MIB.mib
VMWARE-ROOT-MIB.mib
VMWARE-SYSTEM-MIB.mib
VMWARE-TRAPS-MIB.mib
VMWARE-VMINFO-MIB.mib
* If you haven’t added the server to be monitored yet, run discovery or add device to add the server to the database
* Create monitors for SNMP and configure credentials and communities (public, private etc…)
* Open the firewall on the management station ( here it is Whatsup pro)
* Write click the machine you want to monitor and select the monitored items (ping, http, cpu, disk space… etc.)
* Configure the actions to be triggered (email, page, event log…)

from command prompt execue: esxtop

http://kb.vmware.com/selfservice/viewContent.do?externalId=1560391

Using 2GB Fibre Channel Drivers on ESX Server 3.0.1
Products

VMware ESX Server
VMware VirtualCenter
Details

ESX Server 3.0.1 is installed with 4GB Fibre Channel drivers by default. However, the following conditions require you to roll back to 2GB Fibre Channel drivers, which are available on the VMware Infrastructure CD.

*
MSCS clustering on an ESX Server system requires 2GB Fibre Channel drivers.

*
Some arrays are qualified only with 2GB HBA and Fibre Channel drivers in ESX Server 3.0. These arrays are footnoted in the ESX Server 3.x Storage/SAN Compatibility Guide (http://www.vmware.com/pdf/vi3_san_guide.pdf).

Solution

To determine which Fibre Channel drivers are installed

1.
Use the command vmkload_mod -l to determine which drivers are installed.

2.
Review the command output. 4GB drivers are indicated by lpfcdd_732, qla2200_707, or qla2300_707. If one of these is present, modify your drivers.

To modify installed Fibre Channel drivers

1.
Uninstall any 4GB drivers using the command rpm -e <4GB_driver_name>.

Example:

rpm -e VMware-esx-drivers-scsi-qla2200-v7.07-7.7.4.1vmw-29822

The actual driver name varies, depending on the Fibre Channel manufacturer and ESX Server build number.

2.
Install the 2GB drivers using the command rpm -Uvh <2GB_driver_name>.

Example:

rpm -Uvh VMware-esx-drivers-scsi-qla2300-v7xx-7.4.0.1vmw-29822.i386.rpm

The actual driver name varies, depending on the Fibre Channel manufacturer and ESX Server build number.

3.

In the file /etc/vmware/esx.conf, change:
*
lpfcdd_732 to lpfcdd_7xx

*
qla2200_707 to qla2200_7xx

*
qla2300_707 to qla2300_7xx

4.
Issue the command:

esxcfg-boot -b

Also known as update-boot, this option implies -g (regenerate-grub) plus a new initrd creation. The command looks in esx.conf to see what is there and builds an appropriate initial RAM disk (initrd) and puts the appropriate data on the grub.conf kernel command line.

5.
Reboot the system.

6.
(Optional) Follow the instructions again in To determine which Fibre Channel drivers are installed (above). Ensure that all instances of 4GB Fibre Channel drivers were replaced with 2GB Fiber Channel drivers.

Product Versions

VMware ESX Server 3.0.x
VMware VirtualCenter 2.0.x

TAC9858: Patching and Updating VMware ESX Server 3
Evan Chan, VMware and Govindarajan Soundararajan, VMware

http://download3.vmware.com/vmworld/2006/tac9858.pdf