[gpfsug-discuss] CES: IP address won't assign: "handleNetworkProblem with lock held"

[Simon Thompson (Research Computing - IT Services)]

Does it strictly follow this?

We were doing some testing with tap interfaces into vxlan networks and found that if we simulated taking down the vxlan interface (which appears in ifconfig as a physical int really), then it moved the ces ip onto the box's primary Nic which was a different subnet.

Simon
________________________________________
From: gpfsug-discuss-bounces at spectrumscale.org [gpfsug-discuss-bounces at spectrumscale.org] on behalf of Olaf Weiser [olaf.weiser at de.ibm.com]
Sent: 17 October 2016 19:27
To: gpfsug main discussion list
Subject: Re: [gpfsug-discuss] CES: IP address won't assign:     "handleNetworkProblem with lock held"

simple question  -sorry for that - your Nodes.. do they have an IP address in the same subnet as your IP address listed here ?
and if, is this network up n running so that GPFS can find/detect it ?

what tells mmlscluster --ces ?


from each node - assuming class C /24 network , do a
ip a | grep 10.30.22.





cheers




From:        "Oesterlin, Robert" <Robert.Oesterlin at nuance.com>
To:        gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date:        10/17/2016 08:00 AM
Subject:        [gpfsug-discuss] CES: IP address won't assign:        "handleNetworkProblem with lock held"
Sent by:        gpfsug-discuss-bounces at spectrumscale.org
________________________________



Can anyone help me pinpoint the issue here? These message repeat and the IP addresses never get assigned.

[root at tct-gw01 ~]# tail /var/mmfs/gen/mmfslog
Mon Oct 17 10:57:55 EDT 2016: mmcesnetworkmonitor: Found unassigned address 10.30.22.178
Mon Oct 17 10:57:55 EDT 2016: mmcesnetworkmonitor: Found unassigned address 10.30.22.179
Mon Oct 17 10:57:55 EDT 2016: mmcesnetworkmonitor: Found unassigned address 10.30.22.177
Mon Oct 17 10:57:55 EDT 2016: mmcesnetworkmonitor: Found unassigned address 10.30.22.176
Mon Oct 17 10:57:55 EDT 2016: mmcesnetworkmonitor: handleNetworkProblem with lock held: assignIP 10.30.22.178_0-_+,10.30.22.179_0-_+,10.30.22.177_0-_+,10.30.22.176_0-_+ 1
Mon Oct 17 10:57:55 EDT 2016: mmcesnetworkmonitor: Assigning addresses: 10.30.22.178_0-_+,10.30.22.179_0-_+,10.30.22.177_0-_+,10.30.22.176_0-_+
Mon Oct 17 10:57:55 EDT 2016: mmcesnetworkmonitor: moveCesIPs: 10.30.22.178_0-_+,10.30.22.179_0-_+,10.30.22.177_0-_+,10.30.22.176_0-_+


[root at tct-gw01 ~]# mmces state show -a
NODE                                     AUTH          AUTH_OBJ      NETWORK       NFS           OBJ           SMB           CES
tct-gw01.infra.us.grid.nuance.com        DISABLED      DISABLED      HEALTHY       HEALTHY       DISABLED      DISABLED      HEALTHY
tct-gw02.infra.us.grid.nuance.com        DISABLED      DISABLED      HEALTHY       HEALTHY       DISABLED      DISABLED      HEALTHY
tct-gw03.infra.us.grid.nuance.com        DISABLED      DISABLED      HEALTHY       HEALTHY       DISABLED      DISABLED      HEALTHY
tct-gw04.infra.us.grid.nuance.com        DISABLED      DISABLED      HEALTHY       HEALTHY       DISABLED      DISABLED      HEALTHY
[root at tct-gw01 ~]# mmces address list

Address         Node                                Group      Attribute
-------------------------------------------------------------------------
10.30.22.178    unassigned                          none       none
10.30.22.179    unassigned                          none       none
10.30.22.177    unassigned                          none       none
10.30.22.176    unassigned                          none       none


Bob Oesterlin
Sr Storage Engineer, Nuance HPC Grid
507-269-0413
 _______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss