<html><body><p><font size="2">Hi Kristy,</font><br><font size="2">At first glance your config looks ok. Here are a few things to check.</font><br><br><font size="2">Is 4.2.3 the first time you have installed and configured performance monitoring? Or have you configured it at some version < 4.2.3 and then upgraded to 4.2.3?</font><br><a href="https://www.ibm.com/support/knowledgecenter/STXKQY_4.2.3/com.ibm.spectrum.scale.v4r23.doc/bl1adv_guienableperfmon.htm"></a><br><a href="https://www.ibm.com/support/knowledgecenter/STXKQY_4.2.3/com.ibm.spectrum.scale.v4r23.doc/bl1adv_guienableperfmon.htm"><font size="2">Did you restart pmcollector after changing the configuration?</font></a><br><a href="https://www.ibm.com/support/knowledgecenter/STXKQY_4.2.3/com.ibm.spectrum.scale.v4r23.doc/bl1adv_guienableperfmon.htm"><font size="2">https://www.ibm.com/support/knowledgecenter/STXKQY_4.2.3/com.ibm.spectrum.scale.v4r23.doc/bl1adv_guienableperfmon.htm</font></a><br><font size="2">"Configure peer configuration for the collectors. The collector configuration is stored in the /opt/IBM/zimon/ZIMonCollector.cfg file. This file defines collector peer configuration and the aggregation rules. If you are using only a single collector, you can skip this step. Restart the pmcollector service after making changes to the configuration file. The GUI must have access to all data from each GUI node. "</font><br><br><font size="2">Firewall ports are open for performance monitoring and MGMT GUI?</font><br><a href="https://www.ibm.com/support/knowledgecenter/STXKQY_4.2.3/com.ibm.spectrum.scale.v4r23.doc/bl1adv_firewallforgui.htm?cp=STXKQY"><font size="2">https://www.ibm.com/support/knowledgecenter/STXKQY_4.2.3/com.ibm.spectrum.scale.v4r23.doc/bl1adv_firewallforgui.htm?cp=STXKQY</font></a><br><a href="https://www.ibm.com/support/knowledgecenter/STXKQY_4.2.3/com.ibm.spectrum.scale.v4r23.doc/bl1adv_firewallforPMT.htm"><font size="2">https://www.ibm.com/support/knowledgecenter/STXKQY_4.2.3/com.ibm.spectrum.scale.v4r23.doc/bl1adv_firewallforPMT.htm</font></a><br><br><font size="2">Did you setup the collectors with :</font><br><font size="2">prompt# mmperfmon config generate --collectors collector1.domain.com,collector2.domain.com,\u2026 </font><br><br><font size="2">Once the configuration file has been stored within IBM Spectrum Scale, it can be activated as follows.</font><br><font size="2">prompt# mmchnode --perfmon \u2013N nodeclass1,nodeclass2,\u2026 <br></font><br><font size="2">Perhaps once you make sure the federated mode is set between hostA and hostB as you like then 'systemctl restart pmcollector' and then 'systemctl restart gpfsgui' on both nodes?<br><br><br></font><br><img width="16" height="16" src="cid:1__=8FBB0BB9DFE1B57D8f9e8a93df938690918c8FB@" border="0" alt="Inactive hide details for gpfsug-discuss-request---05/24/2017 12:58:21 PM---Send gpfsug-discuss mailing list submissions to gp"><font size="2" color="#424282">gpfsug-discuss-request---05/24/2017 12:58:21 PM---Send gpfsug-discuss mailing list submissions to gpfsug-discuss@spectrumscale.org</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">gpfsug-discuss-request@spectrumscale.org</font><br><font size="2" color="#5F5F5F">To: </font><font size="2">gpfsug-discuss@spectrumscale.org</font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">05/24/2017 12:58 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">gpfsug-discuss Digest, Vol 64, Issue 61</font><br><font size="2" color="#5F5F5F">Sent by: </font><font size="2">gpfsug-discuss-bounces@spectrumscale.org</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><tt><font size="2">Send gpfsug-discuss mailing list submissions to<br> gpfsug-discuss@spectrumscale.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> </font></tt><tt><font size="2"><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></font></tt><tt><font size="2"><br>or, via email, send a message with subject or body 'help' to<br> gpfsug-discuss-request@spectrumscale.org<br><br>You can reach the person managing the list at<br> gpfsug-discuss-owner@spectrumscale.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of gpfsug-discuss digest..."<br><br><br>Today's Topics:<br><br> 1. SS Metrics (Zimon) and SS GUI, Federation not working<br> (Kristy Kallback-Rose)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Wed, 24 May 2017 12:57:49 -0700<br>From: Kristy Kallback-Rose <kkr@lbl.gov><br>To: gpfsug-discuss@spectrumscale.org<br>Subject: [gpfsug-discuss] SS Metrics (Zimon) and SS GUI, Federation<br> not working<br>Message-ID:<br> <CAA9oNus2BRyJcQEHXa7j1Vmz_Z6swTwRDatMw93P0_sD8X76vg@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>Hello,<br><br> We have been experimenting with Zimon and the SS GUI on our dev cluster<br>under 4.2.3. Things work well with one collector, but I'm running into<br>issues when trying to use symmetric collector peers, i.e. federation.<br><br> hostA and hostB are setup as both collectors and sensors with each a<br>collector peer for the other. When this is done I can use mmperfmon to<br>query hostA from hostA or hostB and vice versa. However, with this<br>federation setup, the GUI fails to show data. The GUI is running on hostB.<br>>From the collector candidate pool, hostA has been selected (automatically,<br>not manually) as can be seen in the sensor configuration file. The GUI is<br>unable to load data (just shows "Loading" on the graph), *unless* I change<br>the setting of the ZIMonAddress variable in<br>/usr/lpp/mmfs/gui/conf/gpfsgui.properties<br>from localhost to hostA explicitly, it does not work if I change it to<br>hostB explicitly. The GUI also works fine if I remove the peer entries<br>altogether and just have one collector.<br><br> I thought that federation meant that no matter which collector was<br>queried the data would be returned. This appears to work for mmperfmon, but<br>not the GUI. Can anyone advise? I also don't like the idea of having a pool<br>of collector candidates and hard-coding one into the GUI configuration. I<br>am including some output below to show the configs and query results.<br><br>Thanks,<br><br>Kristy<br><br><br> The peers are added into the ZIMonCollector.cfg using the default port<br>9085:<br><br> peers = {<br><br> host = "hostA"<br><br> port = "9085"<br><br> },<br><br> {<br><br> host = "hostB"<br><br> port = "9085"<br><br> }<br><br><br>And the nodes are added as collector candidates, on hostA and hostB you<br>see, looking at the config file directly, in /opt/IBM/zimon/ZIMonSensors.<br>cfg:<br><br>colCandidates = "hostA.nersc.gov <</font></tt><tt><font size="2"><a href="http://hosta.nersc.gov/">http://hosta.nersc.gov/</a></font></tt><tt><font size="2">>", "<br>hostB.nersc.gov <</font></tt><tt><font size="2"><a href="http://hostb.nersc.gov/">http://hostb.nersc.gov/</a></font></tt><tt><font size="2">>"<br><br>colRedundancy = 1<br><br>collectors = {<br><br>host = "hostA.nersc.gov <</font></tt><tt><font size="2"><a href="http://hosta.nersc.gov/">http://hosta.nersc.gov/</a></font></tt><tt><font size="2">>"<br><br>port = "4739"<br><br>}<br><br><br>Showing the config with mmperfmon config show:<br><br>colCandidates = "hostA.nersc.gov <</font></tt><tt><font size="2"><a href="http://hosta.nersc.gov/">http://hosta.nersc.gov/</a></font></tt><tt><font size="2">>", "<br>hostB.nersc.gov <</font></tt><tt><font size="2"><a href="http://hostb.nersc.gov/">http://hostb.nersc.gov/</a></font></tt><tt><font size="2">>"<br><br>colRedundancy = 1<br><br>collectors = {<br><br>host = ""<br><br><br>Using mmperfmon I can query either host.<br><br><br>[root@hostA ~]# mmperfmon query cpu -N hostB<br><br><br>Legend:<br><br> 1: hostB.nersc.gov <</font></tt><tt><font size="2"><a href="http://hostb.nersc.gov/">http://hostb.nersc.gov/</a></font></tt><tt><font size="2">>|CPU|cpu_system<br><br> 2: hostB.nersc.gov <</font></tt><tt><font size="2"><a href="http://hostb.nersc.gov/">http://hostb.nersc.gov/</a></font></tt><tt><font size="2">>|CPU|cpu_user<br><br> 3: hostB.nersc.gov <</font></tt><tt><font size="2"><a href="http://hostb.nersc.gov/">http://hostb.nersc.gov/</a></font></tt><tt><font size="2">>|CPU|cpu_contexts<br><br><br><br>Row Timestamp cpu_system cpu_user cpu_contexts<br><br> 1 2017-05-23-17:03:54 0.54 3.67 4961<br><br> 2 2017-05-23-17:03:55 0.63 3.55 6199<br><br> 3 2017-05-23-17:03:56 1.59 3.76 7914<br><br> 4 2017-05-23-17:03:57 1.38 5.34 5393<br><br> 5 2017-05-23-17:03:58 0.54 2.21 2435<br><br> 6 2017-05-23-17:03:59 0.13 0.29 2519<br><br> 7 2017-05-23-17:04:00 0.13 0.25 2197<br><br> 8 2017-05-23-17:04:01 0.13 0.29 2473<br><br> 9 2017-05-23-17:04:02 0.08 0.21 2336<br><br> 10 2017-05-23-17:04:03 0.13 0.21 2312<br><br><br>[root@ hostB ~]# mmperfmon query cpu -N hostB<br><br><br>Legend:<br><br> 1: hostB.nersc.gov <</font></tt><tt><font size="2"><a href="http://hostb.nersc.gov/">http://hostb.nersc.gov/</a></font></tt><tt><font size="2">>|CPU|cpu_system<br><br> 2: hostB.nersc.gov <</font></tt><tt><font size="2"><a href="http://hostb.nersc.gov/">http://hostb.nersc.gov/</a></font></tt><tt><font size="2">>|CPU|cpu_user<br><br> 3: hostB.nersc.gov <</font></tt><tt><font size="2"><a href="http://hostb.nersc.gov/">http://hostb.nersc.gov/</a></font></tt><tt><font size="2">>|CPU|cpu_contexts<br><br><br><br>Row Timestamp cpu_system cpu_user cpu_contexts<br><br> 1 2017-05-23-17:04:07 0.13 0.21 2010<br><br> 2 2017-05-23-17:04:08 0.04 0.21 2571<br><br> 3 2017-05-23-17:04:09 0.08 0.25 2766<br><br> 4 2017-05-23-17:04:10 0.13 0.29 3147<br><br> 5 2017-05-23-17:04:11 0.83 0.83 2596<br><br> 6 2017-05-23-17:04:12 0.33 0.54 2530<br><br> 7 2017-05-23-17:04:13 0.08 0.33 2428<br><br> 8 2017-05-23-17:04:14 0.13 0.25 2326<br><br> 9 2017-05-23-17:04:15 0.13 0.29 4190<br><br> 10 2017-05-23-17:04:16 0.58 1.92 5882<br><br><br>[root@ hostB ~]# mmperfmon query cpu -N hostA<br><br><br>Legend:<br><br> 1: hostA.nersc.gov <</font></tt><tt><font size="2"><a href="http://hosta.nersc.gov/">http://hosta.nersc.gov/</a></font></tt><tt><font size="2">>|CPU|cpu_system<br><br> 2: hostA.nersc.gov <</font></tt><tt><font size="2"><a href="http://hosta.nersc.gov/">http://hosta.nersc.gov/</a></font></tt><tt><font size="2">>|CPU|cpu_user<br><br> 3: hostA.nersc.gov <</font></tt><tt><font size="2"><a href="http://hosta.nersc.gov/">http://hosta.nersc.gov/</a></font></tt><tt><font size="2">>|CPU|cpu_contexts<br><br><br><br>Row Timestamp cpu_system cpu_user cpu_contexts<br><br> 1 2017-05-23-17:05:45 0.33 0.46 7460<br><br> 2 2017-05-23-17:05:46 0.33 0.42 8993<br><br> 3 2017-05-23-17:05:47 0.42 0.54 8709<br><br> 4 2017-05-23-17:05:48 0.38 0.5 5923<br><br> 5 2017-05-23-17:05:49 0.54 1.46 7381<br><br> 6 2017-05-23-17:05:50 0.58 3.51 10381<br><br> 7 2017-05-23-17:05:51 1.05 1.13 10995<br><br> 8 2017-05-23-17:05:52 0.88 0.92 10855<br><br> 9 2017-05-23-17:05:53 0.5 0.63 10958<br><br> 10 2017-05-23-17:05:54 0.5 0.59 10285<br><br><br>[root@ hostA ~]# mmperfmon query cpu -N hostA<br><br><br>Legend:<br><br> 1: hostA.nersc.gov <</font></tt><tt><font size="2"><a href="http://hosta.nersc.gov/">http://hosta.nersc.gov/</a></font></tt><tt><font size="2">>|CPU|cpu_system<br><br> 2: hostA.nersc.gov <</font></tt><tt><font size="2"><a href="http://hosta.nersc.gov/">http://hosta.nersc.gov/</a></font></tt><tt><font size="2">>|CPU|cpu_user<br><br> 3: hostA.nersc.gov <</font></tt><tt><font size="2"><a href="http://hosta.nersc.gov/">http://hosta.nersc.gov/</a></font></tt><tt><font size="2">>|CPU|cpu_contexts<br><br><br><br>Row Timestamp cpu_system cpu_user cpu_contexts<br><br> 1 2017-05-23-17:05:50 0.58 3.51 10381<br><br> 2 2017-05-23-17:05:51 1.05 1.13 10995<br><br> 3 2017-05-23-17:05:52 0.88 0.92 10855<br><br> 4 2017-05-23-17:05:53 0.5 0.63 10958<br><br> 5 2017-05-23-17:05:54 0.5 0.59 10285<br><br> 6 2017-05-23-17:05:55 0.46 0.63 11621<br><br> 7 2017-05-23-17:05:56 0.84 0.92 11477<br><br> 8 2017-05-23-17:05:57 1.47 1.88 11084<br><br> 9 2017-05-23-17:05:58 0.46 1.76 9125<br><br> 10 2017-05-23-17:05:59 0.42 0.63 11745<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <</font></tt><tt><font size="2"><a href="http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20170524/e64509b9/attachment.html">http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20170524/e64509b9/attachment.html</a></font></tt><tt><font size="2">><br><br>------------------------------<br><br>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></font></tt><tt><font size="2"><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></font></tt><tt><font size="2"><br><br><br>End of gpfsug-discuss Digest, Vol 64, Issue 61<br>**********************************************<br><br></font></tt><br><BR>
</body></html>