Monthly Archives: June 2016

VMware Update Manager HP Vibsdepot Change

I posted last year about how to get HP specific updates related to VMware through VMware Update Manager.  A co-worker of mine recently pointed that URL is incorrect now.  HP recently rebranded their enterprise products as HP Enterprise (HPE).  Consequently, the VIBS download locations changed.

New HP VUM URLs

Drivers: http://vibsdepot.hpe.com/index-drv.xml

All other components: http://vibsdepot.hpe.com/index.xml

To get all HP updates, you need to add both as download locations.

Make sure you update your environment accordingly!

Ecobee Thermostat After One Year – Part 1

I also wanted to use this blog to discuss some gadgets and things that aren’t work related.  Finding in depth reviews of these kinds of things are hard to come by, especially ones where there isn’t any real incentives to be for or against the product.  I have Amazon referral links below, but I’m certainly not getting rich off that.  🙂

I purchased an Ecobee3 thermostat by Ecobee about a year ago.  I find it’s better to live with it before making any judgments about it.  I think now is a good time to write a review after living with it for a year.

Basic Background Info

I just wanted to share some basic information that may help others compare their results or their current situation that may help them to determine what to expect from their purchase of an Ecobee3 should they decide to purchase one.

Ecobee3 can be purchased in two packages:

You can also add packs of two remote sensors.

Protip: If you have sections of your house with consistently offset temperatures from each other, such as an upstairs and downstairs, place sensors equally between the two.  This avoids skewing of one house section's temperature over another.

I purchased my Ecobee3 for my primary residence, which is a 1650 sq ft house, no garage.  It’s a two story house built in 2001 in the Richmond, Virginia area. Other than the Ecobee3 purchase, I haven’t done any significant energy efficient upgrades to the house.  It’s still running the original HVAC system, which is an American Standard electric heat pump system with one stage aux heat (emergency heat).  I don’t have any additional specific information about it beyond that.  It had a standard manual thermostat, which we set and forgot about.  We conscientiously change our air filters in the house every two months, and service the unit each year to ensure efficiency.

The house, typical of most multi-story houses, has a temperature disparity between the floors of about 5F on average.  On top of that, my wife and I share an office, which is another 3-4F warmer than the rest of the upstairs due to all the computer equipment running up here (router, NAS device for lab, Windows based file server, my workstation, her workstation, 7 LCD monitors between us).   I also have my desk treadmill I got last year around the same time. It uses significant electricity and generates more heat in the room when I’m using it.  We do have dampers which we change depending on the season to force AC more upstairs in the summer, and force more heated air downstairs in the winter, but the temperature disparity can’t be overcome by this alone unfortunately, no matter what we do.

I frequently work from home, and my wife is home most of the time as well, aside from a few days a week during the day.  I wouldn’t expect a ton of energy savings from detecting when we’re home or not.

Installation

I purchased the Ecobee3 version before HomeKit integration was offered.  Ecobee3 comes with a motion/temp sensor within the thermostat itself, and one additional remote sensor.  I purchased one more motion/temp sensor two pack.

My thermostat is located downstairs in our family/entertainment room.  I placed the remaining sensors in the downstairs kitchen, our upstairs bedroom, and our sauna office.  We elected not to place sensors in any bathrooms, an extra bedroom upstairs that’s a glorified storage room, or any hallways.

Protip: I would balance sensors evenly between floors that have natural temperature disparities like we do. Otherwise, the weighted whole house temperature might get skewed more often towards one floor or another when all are evenly occupied.

Installation was relatively simple, even for me.  While I’m an IT engineer, I’m not much of a DIY’er for house work.  I’ve never replaced nor installed a thermostat ever before the Ecobee3.  I checked their website, and provided the wires that were in my current thermostat.  It provided me the wiring directions for the Ecobee3.

Protip: Use their website to determine wiring.  Also, know what kind of system you have prior to install.  I would also elect to install the thermostat when the system will engage, and you will be around to know if there are any misconfigurations.

It worked straight off the bat except for one issue.   It asks you if energizing your heat pump cools or warms your house.  I accepted the default, which is the most common.  Mine was of course the lesser common.  This became very obvious as soon as cooling was needed.   Ecobee notified me my house was going in the wrong direction from what the thermostat expected.  I simply went in and changed this option, and everything worked at a basic level there on out.

Ecobee updated the firmware a few times since.  One notable update came a few months after the initial release, which claims to have improved the algorithms responsible for deciding when to use the heat pump versus aux heat and full on AC.  This should improve efficiency significantly.

Issues Encountered?  Just a few…

After the initial install snafu I discussed above, the only issue I’ve encountered is the sensor in the kitchen downstairs, despite it being the closest to the thermostat unit itself, would alert of getting disconnected and reconnected frequently.  New versions of firmware that would automatically install on the themostat would make this better, then back to bad, then better again.  I tried replacing the CR2032 watch battery in it, but that didn’t do any good.  Eventually, Ecobee apparently nailed it somewhere in the firmware update chain, and it has rarely happened again.  Even though this happened, it never significantly impacted operation that I’m aware of.

Once, I updated my Asus RT-AC68W to the latest firmware revision, and my Ecobee3 absolutely could not connect to wifi.  I downgraded, and it reconnected.  I did it again a few months later with an even newer firmware revision, and it did it again.  The only way I could resolve it is downgrade back again.  However, I recently upgraded my router to a fork in the Asus router’s code that Asus uses as a base for their firmware.   I had no issues at all  after that. I’m guessing there was indeed something wrong with the Asus firmware.  Why it caused issues specifically with the Ecobee3, I have no idea.

Protip: If your router or WAP has the ability to provide segregated connectivity only to the internet and to nothing else on your LAN, you might as well use that for the Ecobee.  Any Ecobee actions you perform against the thermostat goes out to the internet to Ecobee's servers and back down to your thermostat.  Local connectivity doesn't do you any good.  This reduces risk to your network.

What I’ve liked about the Ecobee3

Here’s what I’ve liked about the Ecobee3 so far:

  • Easy initial installation for the most part.  No special wifi network configurations necessary, no port port forwarding, nothing like that.  “It just works” is pretty much the case, at least as much as you could possibly hope for IMO.
  • Easy to maintain.  Firmware updates automatically, no issues I’ve encountered other than the kitchen sensor issue, which eventually went away.
  • IOS apps have worked fairly reliably.  Sometimes I need to force close the app and restart it, but that’s really minor.
  • Remote ability to manipulate settings, such as desired temperature, turning the HVAC system off when it’s not needed, flipping the mode from heat to cooling as the seasons change, and scheduling vacations to save energy.  My wife LOVES the ability to do this without having to go to the thermostat.
  • Automatic detection for when we are home and not, or which rooms are occupied (see negatives below, it’s definitely not all roses)
  • AWESOME analytics when you want it.  This helps you determine how efficient the system is running, diagnosing and detecting problems, etc.  This helped me detect a problem recently where a small leak in the heat pump system caused the outside fan unit to freeze up.  The unit was becoming noisy.  I fired up the iPad IOS app, looked at trends, and noticed a sharp increase in how much the heat pump was running just to maintain heat.  I promptly called for service.  It also helped me to determine that using the single room small portable AC unit I have for the office does help avoid running the whole house unit. At my fingertips, I can find out what temperature it is in any room with a sensor, when my AC, heat pump, and auxilury heat has run on an easy to read graph along side the outside and inside actual temperatures, along with my desired temperature.  The data you gain access to alone in my opinion may make the thermostat worth it.  I didn’t know exactly what the temperature differences between rooms actually was before.  I didn’t know how much my system was running.  I didn’t know any trends concerning how much the auxiliary heat was used vs the heat pump, or how much the AC was actually running to cool the house down.  I could actually see the impact of my desk treadmill had on the office temperature.  All this data is  eye-opening.  You can use it to make informed decisions that can save you money.
  • Alerts when things aren’t running right.  Ecobee notifies me if it sees the temperature moving in the wrong direction compared to what it expects, which helped me diagnose the initial misconfiguration.  I get alerts when it’s time for routine maintenance.  Ecobee sends alerts if the aux heat runs for longer than an amount of time I configure.  That helped me discover a window in the house was left opened accidentally, and when a damper somehow got closed shut.  This happened once before I got the Ecobee, and it ran like this for a few weeks before we noticed.  I get alerts if the weighted temperature goes above or below configured thresholds, so I know if there’s a major problem.
  • Plenty of tweaking options!  If the automated logic of the Ecobee doesn’t quite work for you (or even not at all), you’re given enough options to change to make it work for you.
  • You gain access to settings and abilities you just don’t have with a dump thermostat.  For example, I can choose to run the HVAC system’s fan a minimum of a defined number of minutes to circulate air throughout the house, which has helped the temperature imbalance in the house between rooms/floors.
  • It’s a really nice looking thermostat quite honestly.  Very well made, nice looking display, the touchscreen works really well on it.

What I haven’t liked about the Ecobee

There are a few things that I haven’t liked:

  • If you lose internet connectivity, you lose the ability to remotely manage the Ecobee3.  I know if they changed this, it would likely complicate installation and day to day management of it.  I’m fine with this honestly.
  • The wifi connection issue when I’ve updated my router.  I do think that was very likely a problem with my router’s firmware though.
  • Ecobee isn’t being intentionally misleading.  You may think this thermostat can simply be installed, initially configured and setup your schedule, keep that updated as your daily life patterns change, and then let it automate your house beyond that, and you’re good to go.  No significant tweaking required!  That wasn’t my experience.  I fully recognize this may be because of the weird temperature disparity within my house coupled with the varying tolerance of temperature ranges between my wife and I.  I found I had to resort to some pretty unorthodox tweaking that most people would never need to do. Here’s an example of one of the issues I had to tweak my way out of to stop constant complaints from my wife.  We would often times both be in my office for long periods of time.  Since the office is so hot, this works to our favor in the winter.  All other rooms get de-weighted, so the heat pump doesn’t run nearly as much.  The problem is when my wife goes downstairs, and is confronted with a 10F colder temperature.  I tried various tweaks until finally deactivating the office as even being counted when determining the house temperature because nothing else would make it be acceptably warm enough when she left the office, negating significant savings.  I’ve also had to tweak other settings as well to get optimum performance for winter and summer that would be more specific to each HVAC system.  Didn’t have to in order to get a basically functioning system, but still.  Expect to need to tweak.
Protip: Check in on your analytics when you begin using AC or heat for the first time you have the thermostat, or perhaps even if you just changed your HVAC system.  You may need to tweak some settings.
  • Firmware updates are out of the blue and are managed by Ecobee.  Furthermore, Ecobee doesn’t do a very good job of notifying you when new firmware drops, when it’s installed on your system, and changelogs to the firmware, so you might know what to expect.
  • The iPad version of the app has significantly more in it than the iPhone app.  This is most noticeably in the amount of trending data available.  Surely some limited trending data could be made available on the iPhone.
  • Not every tweaking function is available on even the iPad app.
  • Remote sensors are around $65-70 for a two pack, which is price gouging, quite honestly.  That’s why we don’t have sensors in the rooms we’re not in much, even though that would be nice.
  • You and anyone else who manipulates any setting really needs to basically understand how the Ecobee works before they start fiddling with it.  For example, my wife would be upstairs in the winter, and would come downstairs and be a bit too cold, so she’d change the desired temperature to a set and hold for something warmer.  She didn’t understand the displayed temperature was a weighted average on the thermostat for all rooms with a greater weight to rooms that detected motion.  She’d set it a few degrees warmer than whatever that said,  and that was that.  That would leave the set/hold on indefinitely, throwing the schedule I had configured out the window.  Next thing I know, a non-optimal set and hold was running for a week.  It took some explaining that moving from room to room alone may have automatically made it comfortable.

Would I have bought it knowing what I know now?

Unequivocally, yes.  I need to crunch the numbers to see if the thermostat itself has saved me money on its own by making my HVAC system more efficient, which I intend to do soon as a follow up to the best of my ability.  It’s hard to calculate this.  I’ve gotten concrete practical examples of where the Ecobee has helped me solve issues that would have cost me more money in electricity or a service call.

It’s also far more convenient to remotely change settings without having to go to the thermostat or even be home.  I’ve even made some tweaks to make my wife more comfortable from my iPad while I was out of town.  How cool is that? (No pun intended!)

My wife loves being able to change basic stuff right from her phone if she wants. She’s not a tech gadget person, and even she has seen the value of it.  That says a lot.

I’ve also got an Amazon Echo Dot.  Voice commands are limited to mainly setting a temperate, but that works.  With that said, I have never had a use for that in practice.

vCloud Air OnDemand and DR Overview

Recently, I worked on a project to deploy for a customer vCloud Air Disaster Recovery.  Along the way, as mentioned in a previous post, I went ahead and picked up the applicable VMware certification for it.  I wanted to discuss how vCloud Air works.  To begin with, I wanted to discuss the two offerings, and how they interact.

vCloud Air OnDemand

vCloud Air OnDemand is a public cloud Infrastructure As a Service (IAaS) solution.  You can run pretty much whatever workloads you like.  These are VMs or appliances you deploy either manually by yourself, using their catalog, or perhaps even upload templates from your VMware on premise  environment.

vCloud Air Disaster Recovery

vCloud Air Disaster Recovery is a public cloud Infrastructure As a Service solution.  It’s identical to vCloud Air OnDemand except it’s geared specifically for failing over replicated virtual machines.  VMs you run in this cloud can only be replicated virtual machines from your vSphere environment.  These VMs are replicated with vSphere Replication.  In addition, you can designate isolated networks within vCloud Air DR for isolated testing.

Two Separate Clouds

One design concept to understand is vCloud Air OnDemand and vCloud Air Disaster Recovery are two completely separate clouds.  While they have very similar features and management interfaces, they are completely independent and separate.  This is so much so that in order for VMs in either to be able to communicate with each other, you must setup site to site VPN connections between them.  Keep this in mind.

When Should I Use vCloud Air OnDemand vs Disaster Recovery?

This seems obvious, right?  If you want to replicate VMs using a whole VM replication technology and fail VMs over, use DR.  Use OnDemand when application or service data will replicate natively instead of whole VM replication.

But it’s not so simple as that.  What if a VM has the ability to replicate within its service or application?  Do some services and replication prohibit you from using whole VM replication?

The giant elephant in the room for DR solutions when asking these questions is Active Directory.  If you want your DR solution to be wholly independent, you likely need domain controllers in the cloud and on premise.  And it’s not supported to use whole VM replication with Active Directory Domain Controllers.  So, DCs are out for use with vCloud Air DR for production use cases.

Generally speaking, it maybe a bad idea for infrastructure bread and butter type VMs generally speaking.  For example, DHCP servers could be replicated, but the problem is vSphere Replication can only configure VMs with as low a RPO as 15 minutes, and going over a WAN link might make that 15 minute RPO at best impossible with all your other VMs you’re replicating.  Perhaps it would be better to build a VM within OnDemand and run a script to export the DHCP database regularly to the DR site.

Bottom line though is this:  You only need OnDemand if you won’t replicate VMs using vSphere Replication to vCloud Air.  If you want to run replicated VMs within vCloud Air as a DR solution, AND you want to ensure that the vCloud DR site is not dependent at all on your on premise infrastructure, you probably need both if only to facilitate running Domain Controllers.  Perhaps other services and applications you’ll replicate data to through other means, too.

It would look something like this:

vcloudairdrcommondesign

 

VMware ESXi 6.0 Express Patch 6 causing CBT issues

The always useful Veeam support digest is reporting that at the very least Veeam is seeing issues with Change Block Tracking (CBT) caused by vSphere 6.0 Express Patch 6.  This build was released on May 12th of this year.  It is the current build according to VMware’s build number KB article.

Veeam is reporting they’re seeing the issue if you’re not using application aware processing and using VMware Tools quiescence on your Veeam jobs.

Other blog articles are mentioning other backup products also impacted, including VMware Data Protection and IBM TSM.  It’s safe to assume this will broadly impact all VMware centered backup products.

If you’re using Express Patch 6, you currently have two options:

  1. Roll back to ESXi 6.0 Update 2.
  2. Don’t use quiesced snapshots.

Heads up!

Qlogic QConvergeConsole vCenter Plugin

I recently had a customer running into storage performance issues, and we determined that Qlogic CNA I/O card firmware and driver upgrades were in order.

Updating the drivers on multiple hosts if you have VMware Update Manager is easy. Just simply import the VIB into the patch repository, setup or change out the drivers in an existing baseline, and remediate your hosts. You can see similar instructions on my other blog post about updating Cisco UCS drivers within vSphere environments.

But what about firmware updates?

Qlogic QConvergeConsole

Qlogic has a pre-boot package you can use to update the firmware, but that’s not automated.  Plus, it can get pretty tedious having to boot off a USB stick or image remotely through an out of band management card.

Thankfully, Qlogic has a set of utilities to help you get more information about your Qlogic cards, and deploy new adapter firmware packages right from vCenter!

How do you take advantage of this?

You need to deploy the vCenter Qlogic plug-in. There are two packages available – one for the thick client, and one for the Web Client. I would recommend the Web Client one. First off, VMware has ceased development of the thick client, so generally using web plug-ins when given a choice is better. Secondly, I quite honestly had issues even getting the vSphere client plug-in to work properly, but the web client plugin worked great. Both had installation issues. I neglected to write down the exact wording, but the installer (and this was on a Windows installable vCenter 5.5 server) said something to the effect of an invalid console mode. After some googling, I found for other software from other manufacturers this can be overcome by setting the compability mode to Windows 7/2008R2. After doing that, both installed easily.

You also need to deploy the CIM provider VIB to the ESXi hosts. This is again another simple VIB deployment to the hosts, but does require a reboot. Updated drivers and CIM provider can be done to save time.

How to update Qlogic firmware

To update the firmware on Qlogic HBAs, navigate to the host you wish to update, and go to Manage > QConvergeConsole. Be patient, as the plug-in gathers and displays the information. The plug-in isn’t exactly a speed demon. Once it displays information for the HBAs, you click on the card on the left pain of the plug-in, and then click the card you wish to update. You’ll get current information about the card, including firmware information, and various features. You can even toggle some modes on the card like Personality Type and SR-IOV.

qlogicfwupdate1

Click “Update Adapter Flash Image”. In the next window, browse to the downloaded card firmware, select the bin image, and click OK. You’ll then be provided with a confirmation dialogue box that shows you the firmware you’re currently running, and the new firmware you’re about to install. Click OK to proceed.

qlogicfwupdate2

Be patient as it deploys the firmware. This can take several minutes. Once completed, you’ll receive a dialogue box that says the firmware will not take effect until after you reboot.

Note also if you have multiple Qlogic cards in your server, you must update each card individually, even if they’re the same model card.

At this point, reboot your ESXi server normally, and verify firmware updated successfully after the server boots back up.

FYI, for this customer, updating the drivers and firmware increased synthetic benchmarks by about 250%.  It’s definitely worthwhile to check for these updates, especially if your environment isn’t performing up to snuff.

No, seriously, I’m gonna blog again now

You know the saying when it rains, it pours?

After my last blog entry where I promised to blog more again, we had two deaths in the family (one on my side, one on my wife’s side).  Plus, our dog of 10 months old became ill, and come to find out after tests and what not, she had an undeveloped kidney that eventually had to be removed, so we’ve had to keep a constant eye on her and what not.  She’s still recovering, but she’s slowly getting back to her lovable self.

Free time has been pretty sparse, so blogging took a back seat.

Well, it’s time to get back into the habit, so here we go!  No, like, seriously this time!  I mean it!

(Anybody want a peanut?)