vSphere 6.0 -Deprecated VMFS volumes

After adding some SAN storage to my UCS Blades, they displayed an error in vSPhere that said “Deprecated VMFS volume(s) found on the host.  Please consider upgrading volume(s) to the latest version.

My volumes were already the latest and greatest at VMFS5 so I turned to trusty google.  Apparently this is a known issue affecting vCenter Server 6.0.  It said to restart the management agents on each host to clear up the issue, sweet.  I logged onto each host using the DCUI and proceeded to restart the management agents…the error never disappeared.  Grr.  Digging a little deeper I found that some people who fixed it were doing it through the command line.  Both methods should do the same thing but I gave it a shot.  Sure enough, connecting to each host via putty (ssh) and running the “services.sh restart” command did the trick.  It may throw some alerts but you shouldn’t lose connectivity to anything and the alert will promptly disappear.

For more information on this error see vmWare’s support:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2109735

 

Advertisements

Cisco UCS – Unable to boot to SAN

During the configuration of my UCS B-Series I ran into some issues with booting to SAN that required me to open a TAC case after exhausting the Internet.  The answer was so counter-intuitive that I wanted to post it here in case anyone else can use it.  Here are the steps I took and where I hit a roadblock.

First I created host profiles in the UCS for each blade and applied WWNs from the SAN pool.  Each blade has a side A and side B WWN which I zoned to different node pairs on our 3par to distribute the load.  Next I cabled the UCS to our fabric switches and set up the boot policy on each blade to boot to one of the WWNs from each side of the fabric, one for the primary and one secondary.  I created boot volumes on the 3par for each blade and powered up the blades.  I set them to boot to a locally mapped ISO and when the prompt came to scan for storage to use for the install, they all found their proper disks immediately.  After rebooting the blades could not find their boot disks.

ucs-boot

The catch is that there are 4 storage WWNs mapped on each side, so you can’t just pick any WWN.  To find out what one you need to use, you will have to get onto the command line of the controller on each side of the UCS and run these commands.

You’ll need to ssh using putty (or any ssh client) to each controller of the UCS and log in as an admin.

Type: Connect Adapter 1/1/1
This command is used to identify each blade, just change the middle number to correspond to each blade you need to pull up.  Blade 2 would be 1/2/1 and so on.

Type: Connect

Type: attach-fls

Type: vnic
Here you will see two listings, and you choose the one you want to view in the next command.  Choose the top if you’re on side A, choose the bottom if you’re on side B.

ucs-cmd

Type: lunlist xx
Where xx is the number of the vnic you want to list, choose the top one if you’re on side A, the bottom if you’re on side B.

What you’ll see listed here is a list of all of the WWN paths currently zoned.  The top number is the one you need to enter on the first graphic above for the boot order SAN targets.  These are the only ones that will work!

Hope this helps!  If you have any questions please feel free to drop me a comment.