Just upgraded to SanHQ 3.1.0 and I have a 2 issues:
1) Is it normal it reports reports 3.0.9.something and says it’s a beta?
2) After the update, I have a bunch of active alerts about space usage on my luns which weren’t there before (arrays are a mix of 7.0.9, 7.0.10 and 7.1.2 and 8.0.3).
My luns are NOT thin provisioned on the EQL side and there is no snapshot reserve.
When I connect to the group, I see the volume space is showing 100% (which is expected)
In VMware, I see there is free space. I expected the array to report 100% all the time after I filled up enough of the datastore and I was ok with that as I could see the real data in VMware. The problem is SANHQ now shows all my arrays with a red icon because it’s reporting false alerts about space usage.
Is this a known issue? (I didn’t notice anything in the release notes for SanHQ)
Do I have to install VSM to give the array visibility into VMware to report usage correctly and make SanHQ happy?
Is there any way to make SanHQ 3.1 go back to reporting the way 3.0.2 did?
My pool (alert id 2.2) shows 15% free (which is expected) but I also see an alert id 3.32 saying my member has 0.2% free space remaining. What does that mean? I only have 1 array in my group so pool free space (it's using the default pool) should be member free space, no? Or is it because my pool is using 100% of my array so that error is a false alarm in my situation and should be disabled? (or is everything misconfigured on my EQL?)
I also noticed on the member, in the summary when you click on it, i see the capacity summary showing compression as 1 incompatible and the 3 things below it as N/A. I've never noticed that before but I assume it's nothing to worry about?
I'm sorry but I'm still not understanding what's going on with the free space. There are no snapshots on the EQL side and only 1 volume is thin provisioned (750GB of which only half is used). From the EQL side, it's incorrectly reporting the free space left on the luns but that's ok because VMware sees the correct value and i'm not thin provisioned on the EQL side so no danger there (except that one small lun)
Below are three screen shots from group manager and one from sanhq. What am I missing or not understanding? The only thing I can think of is sanhq is complaining the default pool is using all the space on the array even though there is free space in the pool.
I understand the SCSI unmap and as I said, I'm not thin provisioned on the EQL so I don't care what the array thinks is free or not (and I adjusted the alerts per your recommendation to stop those alerts in the new sanhq)
My problem is the following two alerts I still see. One of them makes sense (the 15% one) but I don't understand where this 0.2% free is coming from. This is a single member group with just the default pool defined
I'm also seeing strange reporting from SanHQ 3.1.0. For example, free space as reported by the group on one particular volume (thin provisioned, no snapshot space used or reserved) is 60%, but SanHQ is reporting 96% used and throwing an alarm. I've got several other volumes showing discrepancies between the group and SanHQ as well, and I've had to disable email alerting because it's become essentially useless, alerting on conditions that don't even exist.
I opened a case and during testing, it looks like there may be a couple bugs. Per my screen shots, i have 15.2% free and it triggers a caution alert. As a test we changed the caution threshold to 16 and the alert was still there. We changed the threshold to 15 and the alert was cleared.
We also noticed that the thresholds seem to keep reverting to defaults. I make the change, go back to the servers and groups and wait for the next polling cycle and the alert clears. If I go back to check the thresholds, they have reverted to their defaults but as long as I don't change anything, I'm ok. The minute I change one, it seems like everything goes back to defaults because that's what is showing in the interface.
There's no confirmation of any bug just yet, but the ticket has been submitted (and for good measure, what may be a vvol bug with incorrect reporting as well)
Just adding that I've been experiencing this same issue after upgrading to the EPA release. The false alerts continued for days even after I disabled the particular alert ID across all severity levels. Restarts of services and the SAN HQ server itself did not help. I was prepared to call in to support the other morning when i noticed the false alerts suddenly stopped even though I hadn't touched anything in days. Still not sure what caused the bug to correct itself, but, hoping it sticks.
So it looks like everything I ran into is a known issue. Quick recap...
Sanhq issues
1) member space alert: the alert is correct but the text that accompanies the alert is wrong. Instead of saying, for example, I've crossed the less than 20% free, it says I have less than 0.2% free. The decimal is in the wrong place.
2) changing the value of a threshold doesn't always show the correct value when coming back to that screen (it shows default values).
Trying to change one value ends up resetting all values because they are displaying defaults instead of current value. Seems like you have one chance to change everything and you may not be able to see currently set value in the future. With the new version being more vocal about alerts, changing values becomes a lot more important to avoid false alerts (at least in my environment)
I was told both of these are known issues. The recommendation is to revert to 3.0.2. That's no fun because I lose out on seeing the VVol stuff. Knowing the slow pace of releases, maybe Donald can find out what kind of time frame we're looking at for a real fix? :) Maybe is more people complain, they will push out a fix sooner? :)
VVol issue (also known issue):
I hinted at this in my last comment and this probably isn't the thread for it but I'll put it out there in case it helps someone else.
I storage vmotioned a VM from a VVol to a normal datastore and group manager still shows the vm as being in the storage container with a zero size. Sanhq also shows the vm as still being there (I can partially understand this for historical data perhaps but putting the timeline to a period where the VM isn't there still shows it as being selectable in the list of volumes. )
The workaround for the group manager issue is remove VM from inventory (in vcenter) and re-add it. Not sure if that fixes sanhq issue as well but I don't like the workaround anyway. A fix will come eventually in the form on an updated firmware.
And finally a quick question for Don: can I uninstall sanhq 3.1 and reinstall 3.0.2 or did 3.1 change some of the data/config files that might cause a problem for 3.0.2?
Origin3k
6 Operator
•
2424 Posts
•
12408 Points
2120
1
Posted July 15th, 2015 15:00
Ah ok.
How to deal with different kind of volume types or the need for different thresholds?
Regards,
Joerg