Re: [gpfsug-discuss] tscCmdPortRange question

[Felipe Knop]

Olaf,

Correct.

mmchconfig -i   is accepted for tscCmdPortRange   . The change should take
place immediately, upon invocation of the next command.

  Felipe


Felipe Knop k...@us.ibm.com
GPFS Development and Security
IBM Systems
IBM Building 008
2455 South Rd, Poughkeepsie, NY 12601
(845) 433-9314  T/L 293-9314





From:   "Olaf Weiser" 
To: gpfsug main discussion list 
Date:   03/06/2018 02:47 PM
Subject:    Re: [gpfsug-discuss] tscCmdPortRange question
Sent by:gpfsug-discuss-boun...@spectrumscale.org



this parameter is just for administrative commands.. "where" to send the
output of a command...
and for those admin ports .. so called ephemeral ports... it depends , how
much admin commands ( = sessions  = sockets)  you want to run in parallel

in my experience.. 10 ports is more than enough
we use those in a range from 5-50010



to be clear ..
demon - to - demon .. communication always uses 1191


cheers





From:"Simon Thompson (IT Research Support)"

To:"gpfsug-discuss@spectrumscale.org"

Date:03/06/2018 06:55 PM
Subject:[gpfsug-discuss] tscCmdPortRange question
Sent by:gpfsug-discuss-boun...@spectrumscale.org



We are looking at setting a value for tscCmdPortRange so that we can apply
firewalls to a small number of GPFS nodes in one of our clusters.

The docs don’t give an indication on the number of ports that are required
to be in the range. Could anyone make a suggestion on this?

It doesn’t appear as a parameter for “mmchconfig -i”, so I assume that it
requires the nodes to be restarted, however I’m not clear if we could do a
rolling restart on this?

Thanks

Simon___
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss


___
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=oNT2koCZX0xmWlSlLblR9Q&m=pezsJOeWDWSnEkh5d3dp175Vx4opvikABgoTzUt-9pQ&s=S_Qe62jYseR2Y2yjiovXwvVz3d2SFW-jCf0Pw5VB_f4&e=



___
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss

Re: [gpfsug-discuss] tscCmdPortRange question

[Olaf Weiser]

this parameter is just for administrative
commands.. "where" to send the output of a command...and for those admin ports .. so called
ephemeral ports... it depends , how much admin commands ( = sessions  =
sockets)  you want to run in parallel in my experience.. 10 ports is more
than enough we use those in a range from 5-50010
to be clear .. demon - to - demon .. communication
always uses 1191cheersFrom:      
 "Simon Thompson
(IT Research Support)" To:      
 "gpfsug-discuss@spectrumscale.org"
Date:      
 03/06/2018 06:55 PMSubject:    
   [gpfsug-discuss]
tscCmdPortRange questionSent by:    
   gpfsug-discuss-boun...@spectrumscale.orgWe are looking at setting a value for tscCmdPortRange
so that we can apply firewalls to a small number of GPFS nodes in one of
our clusters. The docs don’t give an indication on the
number of ports that are required to be in the range. Could anyone make
a suggestion on this? It doesn’t appear as a parameter for “mmchconfig
-i”, so I assume that it requires the nodes to be restarted, however I’m
not clear if we could do a rolling restart on this? Thanks Simon___gpfsug-discuss mailing listgpfsug-discuss at spectrumscale.orghttp://gpfsug.org/mailman/listinfo/gpfsug-discuss

___
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss