It appears number 3 on your list is the case. My nodes are all SAN connected and until I get separate CES nodes no NSD is necessary (currently run CES on the NSD servers – just for a test cluster). Mark From: gpfsug-discuss-bounces at spectrumscale.org [mailto:gpfsug-discuss-bounces at spectrumscale.org] On Behalf Of Markus Rohwedder Sent: Tuesday, December 19, 2017 9:24 AM To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org> Subject: Re: [gpfsug-discuss] pmcollector and NSD perf Hello Mark, the NSD sensor is GPFSNSDDisk. Some things to check: 1. Is the sensor activated? In a GPFS managed sensor config you should be able to see something like this when you call mmperfmon config show: { name = "GPFSNSDDisk" period = 10 restrict = "nsdNodes" }, 2. Perfmon designation The NSD server nodes should have the perfmon designation. [root at cache-41 ~]# mmlscluster GPFS cluster information ======================== GPFS cluster name: gpfsgui-cluster-4.localnet.com GPFS cluster id: 10583479681538672379 GPFS UID domain: localnet.com Remote shell command: /usr/bin/ssh Remote file copy command: /usr/bin/scp Repository type: CCR Node Daemon node name IP address Admin node name Designation ------------------------------------------------------------------------------ 1 cache-41.localnet.com 10.0.100.41 cache-41.localnet.com quorum-perfmon 2 cache-42.localnet.com 10.0.100.42 cache-42.localnet.com quorum-gateway-perfmon 3 cache-43.localnet.com 10.0.100.43 cache-43.localnet.com gateway-perfmon 3. Direct Disk writes? One reason why there may be no data on your system is if you are not using the NSD protocol, meaning the clients can directly write to disk as in a SAN environment. In this case the sensor does not catch the transactions. 4. Cross cluster mount Or maybe you are using a cross cluster mount. Mit freundlichen Grüßen / Kind regards Dr. Markus Rohwedder Spectrum Scale GUI Development ________________________________ Phone: +49 7034 6430190 IBM Deutschland [cid:image002.gif at 01D378AE.BAB5B6F0] E-Mail: rohwedder at de.ibm.com<mailto:rohwedder at de.ibm.com> Am Weiher 24 65451 Kelsterbach Germany ________________________________ IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Martina Köderitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 [Inactive hide details for Mark Bush ---12/19/2017 03:30:14 PM---I've noticed this in my test cluster both in 4.2.3.4 and 5.0.0.]Mark Bush ---12/19/2017 03:30:14 PM---I've noticed this in my test cluster both in 4.2.3.4 and 5.0.0.0 that in the GUI on the monitoring s From: Mark Bush <Mark.Bush at siriuscom.com<mailto:Mark.Bush at siriuscom.com>> To: "gpfsug-discuss at spectrumscale.org<mailto:gpfsug-discuss at spectrumscale.org>" <gpfsug-discuss at spectrumscale.org<mailto:gpfsug-discuss at spectrumscale.org>> Date: 12/19/2017 03:30 PM Subject: [gpfsug-discuss] pmcollector and NSD perf Sent by: gpfsug-discuss-bounces at spectrumscale.org<mailto:gpfsug-discuss-bounces at spectrumscale.org> ________________________________ I’ve noticed this in my test cluster both in 4.2.3.4 and 5.0.0.0 that in the GUI on the monitoring screen with the default view the NSD Server Throughput graph shows “Performance Collector did not return any data”. I’ve seen that in other items (SMB before for example) but never for NSD. Is there something that must be enabled in the zimon sensor or collector config file to grab this or is this a bug? Mark_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=IbxtjdkPAM2Sbon4Lbbi4w&m=a6GCq72qeADy6hsfA-24PmWHU06W5z2xqx9tKIJ8qJ4&s=OQccy8ikWB-ByYgLsJFgI8szDs1ZrwnsaFrLCwTfTwI&e= -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20171219/194aceb4/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 166 bytes Desc: image001.png URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20171219/194aceb4/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 1851 bytes Desc: image002.gif URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20171219/194aceb4/attachment.gif> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 105 bytes Desc: image003.gif URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20171219/194aceb4/attachment-0001.gif>
