It will be difficult, but not impossible to get more women in tech. I’m very hopeful about the prospects.
File this one under “Good to know!”
This is pretty sweet!
Nice that Google developed the app for iOS too! I can’t wait to try it out. If you have used it on either platform, please let me know your thoughts.
One more tool in the 24×7 admin arsenal.
I loathe updating Java because you never know what it will break. This morning, it was the Dell EqualLogic VSM plug-in for vCenter.
Upon launching the plug-in, I got these errors:
I thought to disable the current version and enable the previous version, but there is a way to add this URL as an exception.
Launch the Java control panel (I’m running 2008 R2) and click on the security tab.
Click the edit Site List button:
Add the URL in the above mentioned error, by clicking Add, then typing in the URL.I also added the IP to vcenter as well. Click OK.
One more warning about the HTTP location you’ve entered. Just click continue. Apply the changes and close the java applet. Be sure to close the vCenter client as well.
Launch the client and log into VSM as usual.
Update- info on Windows 7
In Windows 7, there is no exception list under the security tab. To add your site to an exception list, you can create an exception.sites file and add the URL.
Browse to this location: C:\Users\username\AppData\LocalLow\Sun\Java\Deployment\security
If there is a file named exception.sites, add the URL to that file. One URL per line.
If not, you can create it and add your URL.
I’m running vSphere 5.1 and I can’t launch the vSphere Client. I am able to launch the web client just fine. Upon launching the fat client, I get an error:
We updated our domain from 2003 to 2008 R2 and replaced all old domain controllers (DCs). I’d changed the primary and secondary server URL (there was no port number previously) during the cut over and all has been working well for the past 26 days and today, nothing.
I logged into the web client as admin@system-domain to confirm I was pointing to the new domain controllers and I was. So now I’m really stumped. KB article 203918 solved the riddle.
To view the identity sources: Administration > Sign-On and Discovery > Configuration. Here you can view the identity sources. Click the pencil to edit and see more detail.
Here are my current settings:
I added the port number to both the primary and secondary server URLs and tested the connection. Click OK to close the dialog box.
I was then able to launch the fat client without error.
Don’t forget to log out of the web client as admin@system-domain.
It’s safe to assume when I installed 5.1, I didn’t enter the port number as suggested in the Configuring vCenter Single Sign on doc and it worked just fine. Upon upgrading, the port became a required setting.
I am officially a VMware Certified Associate in Data Center Virtualization (VCA-DCV)!
Last week I attended the VMware vSphere: Optimize and Scale (5.1) class at New Horizons and after hearing from a few of the attendees that the exam was a cinch if you worked with VMware and you sat through the online VMware Data Center Virtualization Fundamentals e-learning course, you could pass the VMware Certified Associate (VCA) exam with no problem. After watching the video, reading the exam blueprint, VMware vSphere Basics guide, and taking the practice exam twice, I was ready to schedule.
There is no class prerequisite to take the VCA like the VCP5 and such!
The test is administered by Pearsons Vue and you must request authorization from VMware first to schedule your exam. There is a PDF that outlines the exam registration procedure in great detail. Once you’re registered, signed up with Pearsons and pay for your exam ($120) you’re ready to go. There are tons of discount codes out there that will either give you a 50% discount or maybe even a freebie. Check the VCA forums and see which one works.
The test was 50 questions, 75 minutes long and for but a few questions, they come straight from the e-learning course. My advice, read the question, re-read it and focus on the sentence in the middle that gives you the most clues about what the answer may be. Did I say READ the question? To pass, you need to score a 300. The scale is 100-500 and I got a 420.
My next stop is to study for the VMware Certified Professional 5 – Data Center Virtualization (VCP5-DCV) exam. To obtain this one, you must have taken qualifying coursework prior to obtaining your certification. In the meantime, I’ll take the VMware Certified Associate – Cloud (VCA-Cloud) & VMware Certified Associate – Workforce Mobility (VCA-WM) as well.
I’ll post my training plan and will let you know of my progress. Good luck to you if you’re on the path to becoming VMware certified.
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.
Next, create a baseline. Enter a name and description for your new baseline, select ‘Host Extension’ then click next.
Add the extension to the baseline. Click next.
Review your setting and click finish.
Your newly created baseline is now listed under the Baselines and Groups tab.
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.
Check the box next to the MEM install and click attach.
Highlight the attached baseline and click scan.
Confirm that you’re scanning for patches and extensions. Remove the check next to upgrades. Click scan.
The host will now be labeled as non-compliant. Click remediate in the lower right corner.
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.
Edit any host remediation options and click next. Edit any cluster remediation options and click next. Review your remediation settings and click finish.
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.
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.
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.
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.
This is what it looked like before the install:
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
The new commands are now available. To list them:
# esxcli equallogic
Log out of the host and disable SSH.
For more information on Dell’s MEM, read this great blog post from Cormac Hogan of vMWare.
We’ve all run up against a scenario where a newly installed application will not work properly unless you reboot the server. The problem with that is you are probably working on the app during business hours and a reboot is out of the question right now. There are 2 easy ways to schedule a reboot of your Windows server to happen during off hours with no late night RDP sessions required.
Please test these procedures on a test box before using them on your production server. Also, there are several ways to do this, just Google them and you’ll see what I mean. This was performed on Windows 2008 R2 SP1.
Option #1 Using Task Scheduler and a batch file
To prepare your server for a late night/early morning reboot, do the following:
Open notepad and enter the following:
echo rebooting the server
shutdown /r /f /d p:4:1 /c "Planned restart by Techmom"
I inserted the ping to slow down the command just a bit so I can test it abort the shutdown with a shutdown /a at a command line.
/r = restart
/f= force running apps closed without warning users
/d = Provide reason for restart
p:4:1= Planned:Major:Minor = Application: Maintenance (Planned)
/c = Comment on the reason of the restart or shutdown
This is what you’ll see in the event log regarding the reboot. The comment is a good place to make a note of why the reboot must occur.
Once you know it works, time to create a task.
Open Task Scheduler. In the Actions Panel, click create task. Click each tab and choose the options that will allow you to perform your reboot. My settings are as follows:
Trigger Tab, click New.
Action Tab, click new and browse to the batch script.
Conditions & Settings Tabs are with the default options selected.
Test the schedule to confirm the system will reboot.
If you are logged in during the test, you will see the warning popup informing you of the impending reboot.
Your server will reboot on the schedule you set. Review the event logs and the task scheduler library to confirm the reboot was successful.
Option #2 Use PSShutdown
PSShutdown is a Systernals utility that you can download from Microsoft to reboot local and remote machines. Follow the installation instructions before use.
This tool allows you to issue a psshutdown command from the command line, specify the reboot time as well as add parameters. To get a full list of the switches issue a PsShutdown /? at the prompt.
Open the command prompt and enter the command. In this example, I’ve chosen the following:
-r = reboot
-f = Force apps close
-t = Time to start shutdown
-m = Message
Upon reboot, review the event log for more information on your reboot.
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.
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.
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.
- Name the appliance as it should appear in vCenter. Select an inventory location, click next.
- 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.
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
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.
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.
Enable the VSM plug-in:
Click on Plug-ins + Manage Plug-ins. Right click on the VSM plug-in and click enable.
Close plug-in manager & confirm that Dell EqualLogic VSM is listed under solutions & applications.
When the appliance is deployed successfully, click close and launch the VSM console.
The default credentials are root/eql
Change the default password:
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
Press enter to continue and restart your vSphere client.
Click on Home and launch VSM & log in with your vSphere admin credentials.
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.
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.
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.
In the add PS series group box, enter the group name or IP and credentials (I suggest using grpadmin). Click add and OK.
Monitor recent tasks to see when it’s complete.
Looks like my new vSphere 5.1 cluster upgrade is coming along swimmingly. Time to get these VMs backed up and the old restore points accessible. Enters VDP
VDP is VMware’s newest VM backup and recovery solution that is supported for vSphere 5.1. As before, it’s integrated with vCenter and can be managed via the vSphere web client. It comes in 2 flavors and depending on the flavor, you get your choice of duplication store sizes, 1/2 Tb, 1TB and 2TB in the Basic version and many more choices in the Advanced version. Data is deduplicated across all backup jobs and utilizes change block tracking and VADP to lighten the load on your ESXi hosts and keeps that backup window much shorter, but only capturing the blocks that have changed. Works with both the Windows and Linux appliance vCenter.
Here are the steps I took to deploy my VDP appliance as well as migrate the restore points from VDR.
I had 1 VDR appliance that backed up both Windows and Linux VMs in 4.1, just with separate dedupe stores. To back up all windows VMs I configured a 900GB disks target and a 500GB disk for Linux. Since one appliance can only contain 1 disk, I will deploy 2 appliances, (1) .5TB and (1) 1TB. Take a look at the VDP Admin guide for more details on how to size, configure, etc.
- A disk presented to your esxi hosts that are of a large enough capacity to hold the dedupe store, OS, logs, checkpoints, etc. It must be formatted for VMFS-5.
- Download the appliance from vmware’s website.
Deploy VDP appliance:
- Launch vSphere web client. From Home, click on vCenter > Datacenter > Objects Tab > Actions Icon > Deploy OVF Template
- Browse to the downloaded OVA appliance file and click next.
- Review the details and click next.
- Accept the EULA and click next.
- Enter the name of the appliance and select a folder or datacenter in which to deploy it to.
- Select a resource where to run the template and click next.
- Select a datastore that has sufficient space then select a virtual disk format. Thin Provisioned is best to begin with. You can convert to thick once the VM is deployed, otherwise the deploy may fail. Click next.
- Select the network the appliance will run on and click next.
- Enter the IP and DNS information and click next.
- Review the details, click the check box next to power on and click finish.
- To check the status of the deploy, review recent tasks. When the template is powered up, point your supported browser to https://IP_OR_Hostname:8543/vdp-configure
- Log in with username: root password:changeme
- On the welcome screen, click next.
- Confirm the network settings are correct and click next.
- Select your timezone, click next.
- Enter your new root password. It must follow all of the listed criteria and cannot be more than 9 characters, 9 exactly! (so weird) Click next.
- Enter your vCenter information:
- vCenter service account username
- FQDN or IP
- If you’re running vCenter on a non-default port, change it here.
- Check the box next to use vCenter for SSO authentication.
- Click test connection, if successful, click ok then finish.
- Click Restart Now to reboot the appliance. The restart may take ~30 minutes. Monitor it’s progress from the console and when the blue “Welcome” screen is up you can proceed. Be warned, you may be back in ‘install mode’ instead of ‘maintenance mode’ after the appliance come back online. I thought it was me, but there are people out there that had to go through process more than once. If you’re back at the configuration wizard, just humor it and answer all the questions again.
View the Maintenance Interface
- Launch the appliance. Once configured, it’s now on it’s maintenance interface. Point your browser to https://VDPIP_or_Hostname:8543/vdp-configure/
- When the system health check completes, view the status of the appliance. From page 24 of the VDP admin guide explains what the maintenance interface is used for.
- “Viewing Status”—Allows you to see the services currently running (or currently stopped) on the VDP Appliance.
- “Starting and Stopping Services” —Allows you to start and stop selected services onthe VDP Appliance.
- “Collecting Logs”—Allows you to download current logs from the VDP Appliance.
- “Changing vSphere Data Protection Configuration ”—Allows you to view or change network settings, configure vCenter Registration, or to view or edit system settings (timezone information and vSphere Data Protection credentials).
- Rolling Back an Appliance” —Allows you to restore the VDP Appliance to an earlier known and valid state.
- “Upgrading the vSphere Data Protection Appliance” —Allows you to upgrade ISO images on your vSphere Data Protection Appliance.
- *Note* Maintenance services will be stopped for the first 24-48 hours after deployment. This is so your 1st backup window is uninterrupted by maintenance activities.
Migrate Restore Points
- Point browser to https://VDPIP_or_HOSTNAME:8543/vdp-migration and log in with your VDP root password.
- Click Attach VDR. This takes some time and will depend on the size of your backup set size.
You can select the jobs you like to keep and edit the retention. This takes a very long time so be patient.
VMware KB on migrating restore points
Keeping VDR around for restores
Officially, VDR is not supported in 5.1, however, if you have the plug-in for VDR in vCenter, you can do restores. It’s best to do a restore rehearsal and never overwrite the existing VM. It’s recommended to keep VDR and VDP on separate hosts and to keep VDR powered off until you need to do a restore. If you’re using DRS, just create a rule that will separate virtual machines. This way, they won’t wind up on the same host by mistake.