Disable VR (vSphere Replication) on VM

You have long removed SRM/vSphere replication.

You discovered a VM still had vSphere Replication enabled.

system has paused replication disk added to vm

Manually remove vSphere replication from vCenter

1. In a webbrowser go to: http://YOUR-vCenter Server/mob
2. Remove this extensions: “com.vmware.vcHms”

More information about MOB, and removing plugins from vCenter, here: http://www.viktorious.nl/2012/05/06/vcenter-howto-remove-a-plugin-from-the-plugin-manager/

Remove vSphere replication from the affected VM
1. vim-cmd vmsvc/getallvms |grep “NAME OF THE VM” <- You are merely looking for the VM’s ID # 2. vim-cmd hbrsvc/vmreplica.disable [VM #] More hbrsvc commands can be found here: http://www.virtuallyghetto.com/2011/07/hbr-host-based-replication-cli-for-srm.html

Are you looking for VMware Hosting that offers cross-site vSphere Replication?  Contact VMDK Hosting

VMware Tools For FreeBSD

cd /usr/ports/emulators/open-vm-tools-nox11/

make all install

vi /etc/rc.conf
vmware_guest_vmblock_enable=”YES”
vmware_guest_vmhgfs_enable=”YES”
vmware_guest_vmmemctl_enable=”YES”
vmware_guest_vmxnet_enable=”YES”
vmware_guestd_enable=”YES”

vi /etc/ntp.conf
First line: tinker panic 0

vi /boot/loader.conf
kern.hz=100
vi /etc/sysctl.conf
kern.cam.da.retry_count=100

vmware-toolbox-cmd timesync disable

Configure HP ILO via ESXi CLI – Reset ILO Password via ESXi CLI

The HP server must have been installed with the HP ESXi ISO -or- Updated via VMware Update Manager (VUM) with the latest vibs from vibsdepot.hp.com.

The process to configure the ILO is as follows:

1.  SSH to the ESXi host

2. cd /opt/hp/tools

3. Export the current config:   ./hponcfg -w /tmp/ilo_config.txt

4. Edit the above export config file (/tmp/ilo_config.txt) and change the following variables:

<IP_ADDRESS VALUE = “10.10.10.20”/>
<SUBNET_MASK VALUE = “255.255.255.0”/>
<GATEWAY_IP_ADDRESS VALUE = “10.10.10.1”/>
<DHCP_ENABLE VALUE = “N”/>

5. Flash the updated config to the ILO:   ./hponcfg -f /tmp/ilo_config.txt

[Let the ILO restart]

6. You must now reset the Administrator password.    Create the file:   reset_admin_pw.xml with the below info and add the new password in the password section:

<ribcl VERSION="2.0">
<login USER_LOGIN="Administrator" PASSWORD="YOUR-NEW-PASSWORD">
<user_INFO MODE="write">
<mod_USER USER_LOGIN="Administrator">
<password value="newpass"/>
</mod_USER>
</user_INFO>
</login>
</ribcl>

7. Flash “reset_admin_pw.xml” to the ILO:   ./hponcfg -f reset_admin_pw.xml

8.  Done.    You should be able to reach the ILO web management interface and login as Administrator.

 

Reset TopSpin Infiniband Switch Password

To reset the password on a TopSpin Inifiband switch you’ll need to boot the system in the single user mode.

To do this:

Connect a console to the serial port and stop the booting at ppcboot.   Do the following:

1) at the “Hit any key to stop autoboot:” prompt, press a key quickly ( <5sec )

2) type in (without quotes, press enter): “setenv bootargs $(bootargs) -s”

3) type in (without quotes, press enter): “bootd”

4) you are now running linux in single user mode – on the recovery area readonly filesystem; load the Disk On Chip driver, type in (without quotes, press enter): “/sbin/insmod /sbin/doc.o”

5) mount the /topspin Disk On Chip filesystem, found on /dev/msys/fla2, on an available directory (such as /tmp), type in (without quotes, press enter):   “mount -t ext3 /dev/msys/fla2 /tmp”

6) the actual config file, config:startup-config, will now be accessible at the path /tmp/config/runtime/startup-config – either remove this file (if there is no other config data to worry about), or vi the file to remove the password spec for user “super” – remove the line with syntax similar to “username super password {integer} {encrypted password}”, sync and reboot; the super user password will revert to the default value “super”.

 

See below for an example:

 

 

PPCBoot 1.1.6 (TopspinOS 2.5.0-BETA releng #273 08/26/2004 16:56:57) (Aug 26 2004 – 20:05:19)

Board: Topspin 270 Fabric Switch Card

 

• VCO: 800 MHz CPU: 400 MHz PLB: 133 MHz OPB: 66 MHz EPB: 33 MHz Drive Anafa2 #1 and #2 reset low… POST: FPGA Rev:0xad : PASSED HW Slot 0. I’m a core. The other core is NOT master. Request mastership. I am master. Hit any key to stop autoboot: 0 => setenv bootargs $(bootargs) -s => bootd Releasing Anafa 1 from reset… Releasing Anafa 2 from reset…

ENET Speed is 100 Mbps – FULL duplex connection

 

Boot Regular Image from Disk Partition 0: boot sig=0x0 Loading:

++++++++++++++++++++++++++++++++++++++++[ 1272K]

 

• ++++++++++++++++++++++++++++++++++++++++[ 2552K]

++++++++++++++++++++++++++++++++++++++++[ 3832K] [ 5112K] [ 6392K] [

++++++++++++++++++++++++++++++++++++++++7672K] ++++++++++++++++++ [ Done

]

 

• Verifying Checksum … OK Uncompressing Multi-File Image … OK Linux version 2.4.19-rc3 (releng@borg(TopspinOS 2.5.0-BETA releng #273

08/26/2004 16:56:57)) (gcc version 2.95.3 20010315 (release)) #23 Thu Aug

26 20:05:59 PDT 2004 Topspin 270 Fabric Switch Card Installing knfsd (copyright (C) 1996 okir@monad.swb.de). iic_ibmocp_init: IBM on-chip iic adapter module 802.1Q VLAN Support v1.7 Ben Greear <greearb@candelatech.com> All bugs added by David S. Miller <davem@redhat.com> RAMDISK: Compressed image found at block 0 VFS: Mounted root (ext2 filesystem) readonly.

 

BusyBox v0.60.5 (2004.08.08-19:40+0000) Built-in shell (ash) Enter ‘help’

for a list of built-in commands.

 

# /sbin/insmod /sbin/doc.o Partition check: fla: fla1 fla2 flb: flb1 # mount -t ext3 /dev/msys/fla2 /tmp EXT3-fs warning: maximal mount count reached, running e2fsck is recommended EXT3-fs: recovery complete. # rm /tmp/config/runtime/startup-config

 

• –OR–

# vi /tmp/config/runtime/startup-config

 

[remove the line with syntax similar to “username super password {integer} {encrypted password}”, sync and reboot; password will revert to the default value “super”.]

 

CentOS / RHEL horrible disk performance with SSD

noop, is essentially a first-in first-out (FIFO) queue with no extra logic.

Each virtual machine can stop worrying about the disk, instead passing I/O requests along to the hypervisor to make a better decision about overall performance.

Add “elevator=noop” to the kernel parameters in your boot loader’s configuration in /etc/grub.conf

`echo noop > /sys/block/${DEVICE}/queue/scheduler`.

Set the default in your kernel config for all VM kernels you roll, with `CONFIG_DEFAULT_IOSCHED=”anticipatory”`.

 

 

 

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 lvm with:

/sbin/lvm.wrapper $@ | sed -e ‘s/-wi-ao–/-wi-ao/’

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.   Do not be fooled by the mention of certificate issues…

 

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
$ sudo su –

1. Change the IP address in /etc/hosts to the public IP.
$ vi /etc/hosts
$ cat /etc/hosts
127.0.0.1 localhost
::1 localhost
33.33.22.22 esxhost.example.com esxhost

1. Verify the hostIP address is the public IP, and add preserveServerIp in /etc/opt/vmware/vpxa/vpxa.cfg .
$ vi /etc/opt/vmware/vpxa/vpxa.cfg


33.33.22.22

true

1. Restart the VPXA service.
$ service vmware-vpxa restart

1. Log out of the ESX service console.
2. In Vmware vCenter client, reconnect the host. You may need to re-enter the root user�s credentials.
3. In Vmware vCenter client, enable Vmware HA and DRS.