Bleeder's Posts

This sounds like the same problem as in previous releases.  I guess it still hasn't been fixed Reference: vROPS 6.1.0 not displaying vSAN dashboards using Management Pack for Storage Devic... See more...
This sounds like the same problem as in previous releases.  I guess it still hasn't been fixed Reference: vROPS 6.1.0 not displaying vSAN dashboards using Management Pack for Storage Devices
Also still getting the error even with ESXi600-201605001 on all hosts.  The sad thing is, prior to this I had opened a case with VMware to be sure everything was in order before upgrading.  They ... See more...
Also still getting the error even with ESXi600-201605001 on all hosts.  The sad thing is, prior to this I had opened a case with VMware to be sure everything was in order before upgrading.  They said everything looked fine, but to wait for that patch because we use App Volumes.  I guess there is yet another bug that hasn't been made public.. No CBT/backups in use here either.
Same problem here.  Did you also have to manually create the stats object (vsan.perf.stats_object_create)?
I've tried 32GB and 64GB and it still happens.  It just masks the issue for a while longer, rather than actually fixing it.
Kudos to Michael Webster for re-interating the queue depth issue with certain virtual disk controller configurations (which VMware continues to ignore for their own appliances): Performance Issu... See more...
Kudos to Michael Webster for re-interating the queue depth issue with certain virtual disk controller configurations (which VMware continues to ignore for their own appliances): Performance Issues Due To Virtual SCSI Device Queue Depths | Long White Virtual Clouds
Can you please clarify "legacy setup"?  A screenshot would be helpful.
It appears they also have it configured with a queue depth of only 128.  I suppose that might be fine for small environments that aren't very busy, but I don't know why they wouldn't set it highe... See more...
It appears they also have it configured with a queue depth of only 128.  I suppose that might be fine for small environments that aren't very busy, but I don't know why they wouldn't set it higher to avoid that being a bottleneck in large environments. cat /proc/scsi/mptspi/0 ioc0: LSI53C1030 B0, FwRev=01032920h, Ports=1, MaxQ=128
Been there, done that.  All my dashboards are shared to the default Everyone group.  "VC Shared" is also checked for them. We are strictly using vCenter logins, no LDAP import/etc.  I'm beginning... See more...
Been there, done that.  All my dashboards are shared to the default Everyone group.  "VC Shared" is also checked for them. We are strictly using vCenter logins, no LDAP import/etc.  I'm beginning to wonder if there was an assumption that users would be imported vs vCenter login.
They finally made a public KB article for the problem, but still no fix: https://kb.vmware.com/kb/2144799
Yes, unfortunately they redesigned that page a while ago and buried the "Build Your Own"  link way down there.  It's especially easy to miss when browsing from some mobile/low-resolution devices.... See more...
Yes, unfortunately they redesigned that page a while ago and buried the "Build Your Own"  link way down there.  It's especially easy to miss when browsing from some mobile/low-resolution devices.  I've had to field several questions just like yours.
Really?  I opened an SR on a related issue and they did not mention anything about a patch (and of course closed the SR). VMware support
Anyone know if this has been fixed yet?  Maybe in Update 2?
Take a look at slide 35 here: https://horizonworkspace.vmware.com/data/shf/i+xTgUEKR1SPUfKy72BX6AAFMTUyODIA
I don't know about that.  It seems like most people didn't want a web client, at all. Finally they've listened to most people complaints with the vSphere client with HTML5 vSphere HTML5 We... See more...
I don't know about that.  It seems like most people didn't want a web client, at all. Finally they've listened to most people complaints with the vSphere client with HTML5 vSphere HTML5 Web Client – VMware Labs
Hoping this will be fixed with Update 2 this month..
Did you ever find a fix for this?  Perhaps a script or something that can change the ID's to match? I see that VMware finally acknowledged the mismatched ID's in https://kb.vmware.com/kb/21441... See more...
Did you ever find a fix for this?  Perhaps a script or something that can change the ID's to match? I see that VMware finally acknowledged the mismatched ID's in https://kb.vmware.com/kb/2144159
@adamjg - Hosted UI became "Ghosted UI" Monday, January 25.  VMRC was included in the products that they were responsible for. Here's the tribute: http://blog.chipx86.com/2016/01/26/a-tribute... See more...
@adamjg - Hosted UI became "Ghosted UI" Monday, January 25.  VMRC was included in the products that they were responsible for. Here's the tribute: http://blog.chipx86.com/2016/01/26/a-tribute-to-vmware-workstation-fusion-and-hosted-ui/
How can VMRC be the solution when the team responsible for it (and Workstation and Fusion) was laid off?
Does it make any difference if you login as the local admin user?  I have this same problem when logging in as a user that has limited vCenter permissions.  I couldn't find anything stating that ... See more...
Does it make any difference if you login as the local admin user?  I have this same problem when logging in as a user that has limited vCenter permissions.  I couldn't find anything stating that additional permissions were needed for viewing MPSD dashboards.