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
[...] Mit freundlichen Grüßen / Kind regards Olaf Weiser EMEA Storage Competence Center Mainz, German / IBM Systems, Storage Platform,---IBM DeutschlandIBM Allee 171139 EhningenPhone: +49-170-579-44-66E-Mail: olaf.wei...@de.ibm.com---IBM Deutschland GmbH / Vorsitzender des Aufsichtsrats: Martin JetterGeschäftsführung: Martina Koederitz (Vorsitzende), Susanne Peter, Norbert
Janzen, Dr. Christian Keller, Ivo Koerner, Markus KoernerSitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart,
HRB 14562 / WEEE-Reg.-Nr. DE 99369940 From:
"Oesterlin, Robert"
<robert.oester...@nuance.com>To:
gpfsug main discussion
list <gpfsug-discuss@spectrumscale.org>Date:
10/17/2016 11:43 AMSubject:
[gpfsug-discuss]
CES: IP address won't assign: "handleNetworkProblem
with lock held"Sent by:
gpfsug-discuss-boun...@spectrumscale.orgYes - so interesting - it looks like
the nodes have the addresses assigned but CES doesn’t know that. [root@tct-gw01 ~]# mmlscluster --ces GPFS cluster information GPFS cluster name:
nrg1-tct.nrg1.us.grid.nuance.com GPFS cluster id:
17869514639699411874 Cluster Export Services global parameters- Shared root directory:
/gpfs/fs1/ces Enabled Services:
NFS Log level:
0 Address distribution policy:
even-coverage Node Daemon node name
IP address CES IP
address list--- 4 tct-gw01.infra.us.grid.nuance.com
10.30.22.160 None 5 tct-gw02.infra.us.grid.nuance.com
10.30.22.161 None 6 tct-gw03.infra.us.grid.nuance.com
10.30.22.162 None 7 tct-gw04.infra.us.grid.nuance.com
10.30.22.163 None [root@tct-gw01 ~]# mmdsh -N cesnodes
"ip a | grep 10.30.22." | sort -k 1tct-gw01.infra.us.grid.nuance.com:
inet 10.30.22.160/24 brd 10.30.22.255 scope global
bond0tct-gw01.infra.us.grid.nuance.com:
inet 10.30.22.176/24 brd 10.30.22.255 scope global
secondary bond0:0 tct-gw02.infra.us.grid.nuance.com:
inet 10.30.22.161/24 brd 10.30.22.255 scope global
bond0tct-gw02.infra.us.grid.nuance.com:
inet 10.30.22.177/24 brd 10.30.22.255 scope global
secondary bond0:0tct-gw02.infra.us.grid.nuance.com:
inet 10.30.22.178/24 brd 10.30.22.255 scope global
secondary bond0:1 tct-gw03.infra.us.grid.nuance.com:
inet 10.30.22.162/24 brd 10.30.22.255 scope global
bond0tct-gw03.infra.us.grid.nuance.com:
inet 10.30.22.178/24 brd 10.30.22.255 scope global
secondary bond0:0 tct-gw04.infra.us.grid.nuance.com:
inet 10.30.22.163/24 brd 10.30.22.255 scope global
bond0tct-gw04.infra.us.grid.nuance.com:
inet 10.30.22.179/24 brd 10.30.22.255 scope global
secondary bond0:0 Bob OesterlinSr Storage Engineer, Nuance HPC Grid From: <gpfsug-discuss-boun...@spectrumscale.org>
on behalf of Olaf Weiser <olaf.wei...@de.ibm.com>Reply-To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org>Date: Monday, October 17, 2016 at 1:27 PMTo: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org>Subject: [EXTERNAL] Re: [gpfsug-discuss] CES: IP address won't assign:
"handleNetworkProblem with lock held" ip a | grep 10.30.22.___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