This post is more than 5 years old
2 Posts
0
137440
August 14th, 2013 15:00
Performance Metrics not available on a new Installation of vFoglight 6.8 (5.6.7)
Hi all!
I have just installed vFoglight 6.8 (Foglight 5.6.7) on RHEL 6.4 that uses an external database on MS SQL.
It has been running for 24 hours.
I am not able to view acces or report on any performance metrics on any of the VC's, DataCentres, ESX Hosts, Data Stores or VM's.
All the vCentres and it's objects like the names of the hosts, vms and datatores are visible and show if powered on or off and there summary pages.
and all the alerts from the Metrics show too?
Just no Performance Metrics (CPU, Disk, Mem and Network).
I did install a patch for the VMWare-Performance 5.6.7.1 cartride and update the agents as well as updated the FGLAM to 5.6.7.2.
Still the same issue after these checks:
Database access is correct
No firewall.
vCenter access Administrator
Restarted the service and server after each change
No errors found on the Agent log and no agent alerts / errors on the the FMS for the agent or FMS itself.
Installation Virtual Server details:
RHEL 6.4
16gb memory
4 vcpu
1gb NIC
Java Mem: (at first default) - now Xms8192m and Xmx8192m
MS SQL DB space available 8gb out of 10gb (will grow when needed)
Your help would be appreciated!
Thanks,
Otto




jschen
17 Posts
1
August 14th, 2013 16:00
Hi Otto,
You may need to tune the FGLAM for the Vmware Performance agent. Please take a look at this KB article from support
https://support.quest.com/SolutionDetail.aspx?id=SOL86012&pr=Foglight%20for%20Virtualization%20Enterprise%20Edition
Thanks,
Jeffrey Chen
tottom
2 Posts
0
September 12th, 2013 18:00
Hello,
Apologies for only getting back to you now.
With your assistance i was able to get the performance stats working correctly.
The support article on it's own did not work but it was the last thing i had to do to get it to work on a fresh install
(although my database grew to 160gb in 11 days...)
This is what i had done to fix it:
I have updated the VMWPerformance patch 5.6.7.1 and after that I have updated the FGLAM version to 5.6.7.2.
Once the updates were done, I then used your solution and restarted the FMS.
Thank you very much for your assistance!