ah .. I see. sorry, should have checked that ,
so to stay with this example, the  IP address 10.30.22.176is set by CES.. as a floating service IP ..

something is insane.. are the smb/NFS services running (systemctl ...)    and can you access the exports from outside ?





From:        "Oesterlin, Robert" <[email protected]>
To:        gpfsug main discussion list <[email protected]>
Date:        10/17/2016 12:02 PM
Subject:        Re: [gpfsug-discuss] [EXTERNAL] Re: CES: IP address won't assign: "handleNetworkProblem with lock held"
Sent by:        [email protected]




No - the :0 and :1 address are floating addresses *assigned by CES* - it created those interfaces. The issue seems to be that these are assigned and CES doesn't know it.
 
 
Bob Oesterlin
Sr Storage Engineer, Nuance HPC Grid

 
 
From: <[email protected]> on behalf of Olaf Weiser <[email protected]>
Reply-To:
gpfsug main discussion list <[email protected]>
Date:
Monday, October 17, 2016 at 1:53 PM
To:
gpfsug main discussion list <[email protected]>
Subject:
[EXTERNAL] Re: [gpfsug-discuss] CES: IP address won't assign: "handleNetworkProblem with lock held"

 
ah .. I see.. seems, that you already has IP aliases around .. GPFS don't like it...
eg. your node
tct-gw01.infra.us.grid.nuance.com:      inet 10.30.22.160/24   
has already an alias -  
10.30.22.176 ... if I understand you answers correctly...

from the doc'... [...] you need to provide a static IP adress, that is not already[...] as an alias [...]  

_______________________________________________
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
http://gpfsug.org/mailman/listinfo/gpfsug-discuss

Reply via email to