Re: [gpfsug-discuss] Specifying nodes in commands

2017-11-10 Thread Chase, Peter
__ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss=DwIFAw=jf_iaSHvJObTbx-siA1ZOg=p_1XEUyoJ7-VJxF_w8h9gJh8_Wj0Pey73LCLLoxodpw=spXDnba2A_tVauiszV7sXhSkn6GeEljABN4lUEB4f8s=1Hd1SNkXtfLRcirm

Re: [gpfsug-discuss] Specifying nodes in commands

2017-11-10 Thread Marc A Kaplan
mmapplypolicy ... -N nodeClass ... will use the nodes in nodeClass as helper nodes to get its work done. mmdsh -N nodeClass command ... will run the SAME command on each of the nodes -- probably not what you want to do with mmapplypolicy. To see more about what mmapplypolicy is doing use

Re: [gpfsug-discuss] Specifying nodes in commands

2017-11-10 Thread Frederick Stock
How do you determine if mmapplypolicy is running on a node? Normally mmapplypolicy as a process runs on a single node but its helper processes, policy-help or something similar, run on all the nodes which are referenced by the -N option. Fred __

[gpfsug-discuss] Specifying nodes in commands

2017-11-10 Thread Chase, Peter
Hello all, I'm running a script triggered from an ILM external list rule. The script has the following command in, and it isn't work as I'd expect: /usr/lpp/mmfs/bin/mmapplypolicy /gpfs1/aws -N cloudNode -P /gpfs1/s3upload/policies/migration.policy --scope fileset I'd expect the mmapplypolicy

Re: [gpfsug-discuss] Spectrum Scale with NVMe

2017-11-10 Thread John Hearns
Chad, Thankyou for the reply. Indded I had that issue - I only noticed because I looked at the utisation of the NSDs and a set of them were not being filled with data... A set which were coincidentally all connected to the same server (me whistles innocently) -Original Message-

[gpfsug-discuss] Antwort: [Newsletter] Re: Problem with the gpfsgui - separate networks for daemon and admin

2017-11-10 Thread Matthias . Knigge
Hi Andreas, hi Neil, the GUI-Node returned a hostname with a FQDN. The clients have no FQDN. Thanks for this tip. I will change the hostname in the first step. If this does not help then I will change the configuration files. I will give you feedback in the next week! Thanks, Matthias

Re: [gpfsug-discuss] Problem with the gpfsgui - separate networks for daemon and admin

2017-11-10 Thread Andreas Koeninger
Hi Matthias,   what's "hostname" returning on your nodes?   1.) If it is not the one that the GUI has in it's database you can force a refresh by executing the below command on the GUI node:   /usr/lpp/mmfs/gui/cli/runtask OS_DETECT --debug   2.) If it is not the one that's shown in the returned

Re: [gpfsug-discuss] Problem with the gpfsgui - separate networks for daemon and admin

2017-11-10 Thread Wilson, Neil
Hi Matthias, Not sure if this will help but we had a very similar issue with the GUI not showing performance data, like you we have separate networks for the gpfs data traffic and management/admin traffic. For some reason when we put the full FQDN of the node into the "hostname" field (it's

[gpfsug-discuss] Antwort: [Newsletter] Re: Problem with the gpfsgui - separate networks for daemon and admin

2017-11-10 Thread Matthias . Knigge
Some more information: Only the GUI-Node is running on CentOS 7. The Clients are running on CentOS 6.x and RHEL 6.x. Von:"Andreas Koeninger" An: gpfsug-discuss@spectrumscale.org Kopie: gpfsug-discuss@spectrumscale.org Datum: 10.11.2017 11:06 Betreff:

[gpfsug-discuss] Antwort: [Newsletter] Re: Problem with the gpfsgui - separate networks for daemon and admin

2017-11-10 Thread Matthias . Knigge
Hi Andreas, the version of the GUI and the other packages are the following: gpfs.gui-4.2.3-0.noarch Yes, the collector is running locally on the GUI-Node and it is only one collector configured. The oupt of your command: [root@tower-daemon ~]# echo "get metrics cpu_user last 10 bucket_size

Re: [gpfsug-discuss] Problem with the gpfsgui - separate networks for daemon and admin

2017-11-10 Thread Andreas Koeninger
Hi Matthias,   1.) Which GUI version are you running? 2.) Is the Collector running locally on the GUI? 3.) Is there more than one collector configured? 4.) Run the following command on the collector node to verify that there's data in the collector:   > echo "get metrics cpu_user last 10