Tag: VMware vSphere

VMworld 2015 in the books

I’m coming off another vmworld and this one was pretty good. This year, we were back in San Fransisco at the Moscone Center. There were plenty great sessions, engaging speakers, opportunities to meet up with folks from past vmworld’s, networking, vendor parties and the party in AT&T park was the icing on the cake. The VWoman session was really enlightening as usual, but it was the same time as the hall crawl and it was not easy to blow that off. I really don’t like that they put both up against each other. It’s like they wanted the men to have the hall crawl all to themselves. #fail

One key highlight was seeing a woman I met at VMworld 2 years ago present a session this year. Sonya Ryherd from Cox Automotive did a session with her colleague, Chris Nakagaki, called, Introduction to Monitoring the Public Cloud with vRealize Operations Manager. They did a great job. It was one of those sessions where you walked away knowing something you didn’t know before. I was very intrigued and learned even more about what vRealize Operations could do. I’m installing it ASAP!

It’s very invigorating to walk away from the conferences with a renewed sense of direction and passion in what I do. Along with finding out about the new technologies and direction they’re headed, you discover features, flings, tips and tools that you’ve never knew existed. That’s like finding the prize in the cracker jack box. You knew it was there, but you didn’t know what that little gem would be.

The 1st things I’ll do when I get back to the office.

  • Plan for the upgrade to vSphere 6.0.
  • Upgrade tools to v10 before the sphere upgrade.
  • Deploy my ESXi lab in the cloud using Ravello & get ready for the VCP6 exam in 2016.
  • Install our newly purchased vRealize Operations

All in all,  a really good time this year, dare I say the best VMworld yet for me.  I ate at a number of wonderful restaurants:

  • The Cavalier
  • Flour + Water
  • Shalimar
  • Brenda’s Soul Food
  • Green Papaya (not wonderful, but I got my sushi fix)
  • Chipotle (like, who doesn’t eat here when at VMworld?)
  • Scoma’s
  • Ghirardelli’s

I won some cool swag:

  • Signed Tour de France jersey
  • $40 VMworld store gift card
  • 2 Starbuck’s gift cards
  • FitBit HR

And got plenty of t-shirts and swag to drag back to the east coast.

I have a ton of photos, but I’ll post just one.

A great way to end a day at VMworld

One sad note about the conference….I’m sad that It’ll be in Las Vegas next year, but I’ll try to be there. I’m not a woman that likes Hades very much.

See you next year (maybe)!

Be soical and share.

Configure and Install the Multipath Extension Module for vSphere and EqualLogic

The MEM (Multipath Extension Module)  by EqualLogic (EQL) handles path selection and load balancing to the storage array. Upon install, it will add another path selection policy called ‘dell_psp_eql_routed’ in addition to the 3 default policies. Using this PSP is ideal when you’re datastores reside on EQL since the module is written by EQL, it has been designed to perform more efficiently in regards to path selection and load balancing to the array.

Here is how I installed and configured MEM on my esxi hosts. I’m running ESXi 5.1 Update 1 with vSphere CLI installed on vCenter.

Prerequisite: Be sure to configure an iSCSI vSwitch for multipathing before installing MEM. Please read  TR1075 for more information on how to configure the vSwitch.

Download MEM from EQL support site. Login is required. Review the release notes, TR1074 as well as the installation & user guide before proceeding.

On the vCenter server,  launch vCenter client. From the home screen, open Update Manager and click on the patch repository tab. Click import patches and browse to the MEM offline bundle zip  and click next to upload.

import-mem-offline-bundle

browse-mem

upload-mem

Next, create a baseline. Enter a name and description for your new baseline, select ‘Host Extension’ then click next.

newbaseline1

Add the extension to the baseline. Click next.

newbaseline2

Review your  setting and click finish.

newbaseline3

Your newly created baseline is now listed under the Baselines and Groups tab.

baseline-and-groups

Now it’s time to install. Begin by putting your host into maintenance mode.Click the update manager tab of the host and click attach.

attachbaseline

Check the box next to the MEM install and click attach.

attachbaseline2

Highlight the attached baseline and click scan.
scanhost

Confirm that you’re scanning for patches and extensions. Remove the check next to upgrades. Click scan.

confirmscan

The host will now be labeled as non-compliant. Click remediate in the lower right corner.

remediate

Click next twice in the remediate wizard if you’re accepting the defaults. On the schedule window, type in a new task name and description (optional) and select a remediation time. I did mine immediately, but this task can be scheduled for a later time. Click next.

remediate-sched

Edit any host remediation options and click next. Edit any cluster remediation options and click next. Review your remediation settings and click finish.

review-remediate

Monitor the recent tasks pane to see the status of the installation. Upon completion, the host will be listed as compliant in the update manager tab.

compliant

 

Reboot.

From a system with vMware vSphere CLI installed on it, run the following command to verify the MEM installation. You will need the setup.pl script in order to run it. It’s included in the MEM download.

Enter the following command using your esxi hostname or IP:
# setup.pl --server=esxhostname_or_IP --query

Enter the credentials for the host. After a few moments, the command will display the version of the MEM installed, the default PSP that is now set as well as the vmkernal ports used by MEM.
verifymem

To list the new Dell EQL PSP as well as the defaults, use the following command:

# esxcli --server esxhostname_or_IP storage nmp psp list

Enter the credentials for the host.
listpsps

Multipathing is available immediately after installation. You can see the paths to the disk as well as the new PSP. On the host, go to the configuration tab+ hardware+storage+right-click the datastore + properties+ managed paths.

after-paths

This is what it looked like before the install:

before-paths

Here you can see that there were 2 active connections to each controller, however, only 1 was being used for I/O. Once MEM is installed, there are redundant active connections to each controller and the load is more evenly balanced.

As I mentioned before, the MEM is totally functioning, however, in order to use the new esxcli commands that are available to manage and report on, you’ll have to restart the hostd agent on the esxi host.

Enable SSH on your host and log into it.

Restart the hostd service:

# /etc/init.d/hostd restart

restart-hostd

The new commands are now available. To list them:
# esxcli equallogic

eql-cmds

Log out of the host and disable SSH.

Done!
For more information on Dell’s MEM, read this great blog post from Cormac Hogan of vMWare.

Be soical and share.

Deploy Equallogic’s Virtual Storage Manager (VSM)

Equallogic has a great appliance that you can deploy to vSphere and use to provision datastores to your cluster, create smart copies, replicas and clones as well as configure replication. Equallogic Virtual Storage Manager (VSM) is a must have if you have storage running on either a PS or FS array.  The latest version of VSM, v3.5.3 supports vSphere 5.5.

To deploy a new VSM appliance:

Download the latest OVA (v.3.5.3), release notes, installation and user guides, from equallogic’s website.

Download VSM
Download VSM appliance

Using the vSphere client (not the web client), confirm the vCenter managed IP is set. This will ensure that VSM can identify and communicate the vCenter.

Administration + vSphere server settings + Runtime Settings. Confirm that vCenter’s IP and FQDN is listed, if not, add them.

vCenter Runtime Settings
vCenter Runtime Settings

Time to deploy:

Click on File + Deploy OVF template. The deploy OVF template launches. Browse to the OVA file you downloaded. The appliance will need 15GB of space if thick provisioned (2.2GB if thin).

Click Next twice. Accept the EULA twice. Click next.

Deploy OVF
Browse to the OVA
  • Name the appliance as it should appear in vCenter. Select an inventory location, click next.

Name the VSM appliance

  • Select the host/cluster on which the appliance should run. Click next.
  • Select a resource pool, click next. Select the datastore, click next.
  • Choose a disk format. Thick provisioned is a good choice. Click next.
  • If prompted to select a network where the NIC should be attached, choose it from the drop down and click next.

VSM Properties:

vsm properties

Enter the values as required and click next.

  • FQDN hostname
  • Time zone
  • NTP servers
  • vCenter http and https ports
  • vCenter username
  • vCenter password
  • Default gateway
  • DNS servers
  • IP address
  • Netmask

Review the settings. Click the check box next to power off after deployment and click finish. Close the ‘completed successfully’ dialog box.

View the task & events tab on the vsm appliance to check the status. Look for the “VSM server starting up” entry. This confirms the appliance is ready.

vsm server starting

Review the summary tab of the VM. Do not update VMware tools on the appliance. This just means that the VMware updated tools after the appliance was released. You can safely ignore the out of date tools status.

vsm summary tab

Enable the VSM plug-in:

Click on Plug-ins + Manage Plug-ins. Right click on the VSM plug-in and click enable.

plugins

Enable Plug-in

Close plug-in manager & confirm that Dell EqualLogic VSM is listed under solutions & applications.

under home

When the appliance is deployed successfully, click close and launch the VSM console.

The default credentials are root/eql

Change the default password:

VSM cli

Select 1 + Select 4

Enter a new root password. Press enter to return to main menu.

Configuring VMware vSphere Storage APIs for Storage Awareness (VASA)

For more info on VASA, read Cormac Hogan’s blog post.

Select 3 to configure VASA

configure vasa

Press enter to continue and restart your vSphere client.

Launch VSM:

Click on Home and launch VSM & log in with your vSphere admin credentials.

Launch VSM

login

These are the vCenter credentials you use to log into the client.

Configure Storage Network (optional):

Click the configure VSM properties icon in the toolbar.

configure vsm in gui

Enable the 2nd nic in the VSM server and configure it with an IP on your iSCSI subnet. You’ll have to already have a port group configured to see that subnet or else, the enabled check will be grayed out. *Note*The storage network can only be configured from the gui. This is a setting that cannot be set from the CLI.

cfg-storagenw

Click OK to close. You’ll be prompted to restart. Restart the vSphere client as well. When the VSM server is back up (see console), enable the plug-in.

Add a PS series group:

Click Groups in the navigation pane. Under the getting started tab, click Add PS series group.

Add PS group

In the add PS series group box, enter the group name or IP and credentials (I suggest using grpadmin). Click add and OK.

add-ps-creds

Monitor recent tasks to see when it’s complete.

add-ps-tasks

You’re done.

Be soical and share.

When powering on a VMA template- Cannot initialize property ‘vami.netmask0.vSphere_Management_Assistant…has no associated network protocol profile.

I’m new to 5.1 and I’m chugging along, getting my new cluster up and running. Deploying a template was a walk in the park in 4.1. This is where you find out you don’t know what you don’t know.

Problem

When I power on the VMA template I get this error:

 

VM Power-On Error

This is caused by not having created an IP Pool for your vAPPS. What is an IP Pool you say?  Here is an explanation from the vSphere 5.1 online documentation:

IP pools provide a network identity to vApps. An IP pool is a network configuration that is assigned to a network used by a vApp. The vApp can then leverage vCenter Server to automatically provide an IP configuration to its virtual machines.

Solution

You’ll have to configure an IP Pool in order to get your template powered on. Click on the Datacenter in vSphere client. There is a new tab called IP Pools, click on it to configure a pool.

IP Pool Tab

Click Add. The New IP Pools Properties box appears.  Give the pool a name. Depending on which version of IP you’re using, click on the corresponding tab.

New IP Pool Properties

Enter the subnet and gateway information as it pertains to your environment. I did not check Enable IP pool and you may or may not have to depending on your environment. Click on the DNS tab and configure DNS as needed. Go through the other tabs and configure them as they apply. Since I’m only using IPv4 without DHCP, it requires limited config. Click OK when you’re finish.

ippool-finish

You should now be able to power on your VMA template.

Similar information can be found here:

 

 

 

 

 

Be soical and share.
Social media & sharing icons powered by UltimatelySocial