Friday, August 31, 2012

VCAP5-DCD Tips

Before taking my VCAP-DCD test at VMworld I got a few tips from Jason Boche who was thankfully in the VMware testing lounge area. It might help you: 
  • Go through the test and mark / flag all design questions for review without spending any time on them. Finish the multiple choice and many to many boxes-of-doom questions and save the design questions for last. 
  • For the long scenario multiple choice questions, see if you can answer the question from just the last line or last short paragraph without reading the whole thing. 
I'll add to those: 
  • Go through the quick demo of how the design questions work. It's not the same as the test but close enough to help you out. 
  • For the design questions, check to see what all your available components are before trying to start the project. 
  • Hammer out the main components and then move things around to start the design. I actually do this with visio as well..get all the main stencils on the page first. 

I met three people who had failed the test. It's a long test. Time management is crucial. Good luck.
I'll be taking the VCAP5-DCA next, thanks to the VMworld discount code from PearsonVue. 


Tuesday, August 28, 2012

Die vRAM Die!

vRAM entitlements gone. Now shops that have intentionally purchased smaller memory servers this past year are grumbling. As are the shops that upgraded to Ent+ just to get the higher vRAM entitlement. 

Hopefully it's not too little too late. vRAM made shops wake up and look around at the rest of the competitors...and they can sing a sweet tune.

The Ent+ vCloud Suite upgrade path is like giving your partner flowers after you screwed up: A good idea, but maybe you shouldn't have had a reason to buy the flowers in the first place. 

How about some more trickle down features to Enterprise? I'm still waiting for my vDS. 

Saturday, July 28, 2012

vCSA upgrade tips & recommendations

Upgrading the vCenter Server Appliance looks simple enough. If you run into problems, maybe these tips can help:

  • Create the 20G (yes 20G) disk in the kb article. 
  • Take a snapshot first (shut down services)
  • Really. TAKE A SNAPSHOT FIRST
  • If the upgrade does not go smoothly the first time, do not try again with a half-broken install. Revert to snap.
  • If your upgrade breaks during the export, check your free inodes (df -i)
  • Increase the number of inodes on the /storage/db/export partition (mkfs -t ext2 -i 8192 /dev/sdc1 )
  • Problems mounting /dev/sdc1 (doesn't like ext2)? tune2fs -O has_journal /dev/sdc1
  • tail -f /opt/vmware/var/log/vami/updatecli.log during the upgrade. This file is created a minute or two after you kick off the upgrade. 
  • There will be a long (potentially hours long) pause in the log while the database export is happening. Top will show db2bp kjourneld and db2sync in use. Do not kill any of these processes. 
  • You didn't take my advice and create a snapshot? You needed to use a restored backup? You might need to remove the /etc/udev/rules.d/70-persistent-net.rules mac addresses if the appliance says it can't bring up eth0. 

Monday, July 2, 2012

Real competition now






What was that pooled vRAM licensing? Never mind? Good idea.
Now update the goddamn vCenter Appliance and stop making software that requires MS Windows.

Tuesday, April 3, 2012

vConverter 5 P2V Windows XP "server"

Let's see if I remember all the steps for this P2V.

Source machine was a physical Windows XP "server" on one subnet; destination was a new vSphere 5 environment on a second subnet. No routing between the two subnets, just another physical Windows XP workstation with nics on both subnets that I could install vConverter on.

After fighting with SSL certs with vConverter (an issue with the source machine's external firewall), I opted to turn off ssl in vConverter:
  • Path for XP [and probably Windows 2003] C:\Documents and Settings\All Users\Application Data\VMware\VMware vCenter Converter Standalone\converter-worker.xml (the path for 2008 Server / Windows 7 is hidden folder C:\ProgramData\VMware\VMware vCenter Converter Standalone\converter-worker.xml)
  • Edit the <nfc> <useSsl> statement from true to false
  • Restart the vConverter Worker service 
I've done plenty of cross-network P2Vs before. Your vConverter server is your go between. P2V the source physical machine to a VMware Workstation image on a shared directory on the vConverter host and then V2V the workstation image to your vSphere environment.

For this case, I didn't have a ton of extra space on the vConverter machine, so I needed to shrink the physical 80G IDE partition down to 20G (12G in use). No problems here and the "optimize partition alignment" option gives me plenty of warm fuzzies.

I booted up the final vSphere version, finished vmware tools intstall and got set to extend the C partition back out for future growth.

No dice.

IDE vmdk's can not be extended.

No problem, says Google. Swap the disk adapter in vConverter. So I go back to the workstation image of the source and V2V again with lsilogic parallel.

BSOD.

V2V with Buslogic?

BSOD.

Plan D: Change the IDE disk to SCSI.
  • Clone the IDE version of the XP "server" for backup.
  • Grab the lsilogic drivers from www.lsi.com/support 
    • Your Windows XP 32bit version will be something like LSI20320-R_xp_50700_01034132IT_1201800_1005239.zip 
    • 64bit XP: LSIMPT_SCSI_WinXP_1.28.03.zip
    • VMware's KB article mentions the different versions but doesn't specify the 1.28.03 is for 64bit XP only. We'll see if they update the doc with my comment. 
  • I created a virtual floppy on one guest in the environment and copied over these files onto the floppy for future use (I'm sure they'll be needed again).
  • Create a new vHDD with lsilogic parallel on scsi0:1; size doesn't matter, thin. 
  • Attach the vFloppy to the XP VM (note: vFloppies can only be connected to a single VM at a time) and install the correct drivers. Shutdown the XP VM.
  • This process assumes there are no snapshots.
  • Double dream hands time:
    • Open ssh on one of the esxi servers, login, su to root and change directory to the XP VM that we've been screwing with.
    • ls -l to get the byte count of the ide vmdk
    • vmkfstools -c <size in bytes> -d thin -a lsilogic <name of new temp vmdk>
    • Copy a backup of the ide .vmdk disk descriptor file (*not* the large -flat.vmdk)
    • Copy a backup of the vmx file
    • cat <name of new temp vmdk> ; note the following parameters: 
      • ddb.geometry.cylinders = "#"
      • ddb.geometry.heads = "#"
      • ddb.geometry.sectors = "#"
      • ddb.adapterType = "lsilogic"
    • vi <ide vmdk> and change the settings listed above to the values from the <temp vmdk> that you just copied down; save & close. 
    • vi <vmx file> and you'll need to look around and change a few areas: 
      • For ide0:0 that is your virtual hard disk, change all values to start with scsi0:0
      • For ide0:1 that is probably listed as your cdrom; update these values to ide0:0 
      • Look for a value scsi0:0.present = "false" and update this to "true"
      • ide0:1.present should be updated to "false"  (you might be able to delete this line)
      • save & close
    • Try turning on the XP VM. If all has gone according to plan, you should boot without issue. Do a little dance (see link above for inspiration).
    • Delete the temp vmdk and the backup files from within your ssh session
  •  Shut the VM back down and extend the C: partition (while you're at it, delete the scsi0:1 disk)
    • Extend the vHDD from the vSphere Client GUI
    • Boot from your favorite partition changer iso. I'm partial (ha!) to gparted...it's not let me down yet.
    • Start the XP VM up again and probably go through a disk check. This is normal. 
Even Marquese gets DDH at 1:06

Thursday, March 29, 2012

DB2 to Postgre vCSA change

The vCenter Server Appliance in the not-released-yet 5.0.1 (5u1) version will be switching from embedded DB2 to Postgre. ARG. Drink up
Is this because the transaction log settings and otherwise working with DB2 to truncate existing tables has been an issue? I sure can't find any detailed information online with the inner workings of the DB2 db. Hopefully smoother sailings than I've had so far.


Tuesday, March 27, 2012

vDR email spam

Crazy crazy amounts of email spewing from a vDR 2.0 appliance. VMware says this is a known bug and you could turn off email alerts and/or reboot your appliance on a regular basis. Drink Up.

Come on  guys, really? That's not acceptable. How about I limit the number of outgoing packets per day on port 25? It worked this morning... but long term I hope that VMware is fixing this bug.

iptables -A OUTPUT -p tcp --dport 25 -m limit --limit 10/day -j ACCEPT

Also I was trying to find a config file that would have the settings for the email reports, but perhaps this isn't kept in a config or xml file. find / -mtime -1 after I made changes in the UI didn't seem to point to any text files.