VMware converter does not find or recognize LVM CentOS 6 |-wi-ao|

As discussed in this VMware thread:  http://communities.vmware.com/thread/413602 VMware converter 5 fails to recognize LVM slices on CentOS 6 or Red Hat 6. Log files shows: WARN storage.lvm ]: Failed to match lvs output line ‘  lv_root|vg00|587034787840B|-wi-ao–|1 This issue is:  -wi-ao–    converter is expecting:  -wi-ao  (no –) Two fixes: 1.  downgrade to:   lvm2-2.02.72 -or- 2. Wrap ...

VMware “Unable to connect to the MKS:”

Unable to connect to the MKS: Login (username / password) incorrect Open /etc/vmware/config with a text editor. Add this:  vmauthd.server.alwaysProxy = “TRUE” Check your firewall config/network setup.    This error is caused by your vSphere client not able to communicate with the ESX/ESXi host directly. All “Unable to connect to the MKS:” errors are network issues.   ...

VMware vCenter SSL Certificate Locations

ESX/ESXi 4.0 /etc/vmware/ssl/ vCenter Server 4.0 C:UsersAll UsersVMwareVMware VirtualCenterSSL For Windows Server 2008, C:ProgramDataVMwareVMware VirtualCenterSSL    

Connect vCenter To ESX/ESXi Through MIP NATd IP

To make both connectivity to vCenter and clone operations function with NATd ESX service consoles: 1. In Vmware vCenter client, disable Vmware HA and DRS. 2. In Vmware vCenter client, disconnect the host. The VMs will continue to run. 3. Log in to the ESX service console via SSH and change to root. $ ssh ...

SSH Client in ESXi

By default, the ssh command does not exist in VMware ESXi 4.1. To create it, login as root and execute the following command: ln -s /sbin/dropbearmulti /bin/ssh

VMware ESX 4.0 to 4.1 Upgrade Error

When updated VMware ESX 4.0 to 4.1: Host was not updated, no changes required. Skipping bulletin ESX410-GA-esxupdate; it is installed or obsoleted. Encountered error RunCommandError: This is an unexpected error. Please report it as a bug. Error Message – Command ‘[‘/usr/bin/vim-cmd’, ‘hostsvc/runtimeinfo’]’ terminated due to signal 6 Simply type: ldconfig [ad#Google Adsense]

vCenter 4.1 “No 64Bit DSN Found” DSN Error on Windows 2008 R2 Server

This error will appear when attempting to install VMware vCenter 4.1. A work around for this issue is to create a system DSN. Then open regedt32 on the server and go to HKLM > Software > ODBC.INI > Update its driver to: C:WINDOWSsystem32sqlncli10.dll. Restart the vCenter install.

Shrink Postgres Tables / Databases

psql With psql cli: vacuum full; also do: reindex ;

Set-ExecutionPolicy : Access to the registry key ‘HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell’ is denied.

When running VMware PowerShell CLI you receive this error: Set-ExecutionPolicy : Access to the registry key ‘HKEY_LOCAL_MACHINESOFTWAREMicrosoftPowerShell1ShellIdsMicrosoft.PowerShell’ is denied. Right click powercli and click: “Run As Administrator” Once powershell starts type this command: Set-ExecutionPolicy RemoteSigned


List off all the rules in order. This helps to see if an allow is overriding one of your denies: iptables -nvL –line-numbers Reject or Drop? Drop means to drop everything at the interface and give no response. Best for port probes and the like. Reject responds to the source. Best practices for TCP/IP