The dreaded 0x2 errors on the Qlogic driver! When will this be fixed! I cry this because I find very little information online about it. We've all experienced storage issues. Maybe some severe others not so much. But, how many of us have experienced a storage issue only to find that an ESXi host goes unresponsive after the issue is fixed or during the issue. Now your VMs may or may not keep running.
Is it possible? How does it work? Does it work well? The last question is the one you should ask before you embark on this vROPS on physical adventure. It does work. Now, as of this writing it ONLY works with the soon to be deprecated EPOPS agent. It is NOT currently supported with the newer telegraph agent yet (hopefully in the future). The agent mostly works without a hitch. Some of the in box alerts don't work for physicals because they are looking for VM specific metrics, so you have to create custom symptoms and alerts just for physical (like disk usage for instance).
Upgrade your vRLI and find issues connecting to AD or to your vSphere? When you try to connect do you find some sort of key error when trying to accept the SSL certificate? Fear not! This fairly easy to fix but there isn't a lot of info online about this. I got these steps from VMware and pasted them here exactly. In the future supposedly there will be an article published about this, but until then here we go.
If you've ever wondered about that MTU health check on a dV switch, fear not! One piece I've noticed is that if the full path (between hosts in the case of VSAN) is NOT the same MTU, this alert will fire. The “fix” is to ensure all network switches in the path have the MTU of that size or “jumbo frames” enabled. Generally you don't want mismatched MTUs anyway as it can cause other issues, but as a general troubleshooting step a good switch check doesn't hurt.
To upgrade to the newest version of vRSLCM (super long acronym!) it's really a migration. There is a tool you use to migrate from the older 2.x version to the 8.x version. They just skipped a bunch of versions in between… the wizard itself is pretty easy. The one piece that may trip you up is it asks to setup a VMware Identity Manager instance. It will not let you proceed without doing so.