Aaron,
 
Not sure if this matches your symptoms precisely, but this appears to be the same problem as the one fixed in
 
https://www.ibm.com/support/pages/apar/IV93896
 
(fixed in 5.0.2.0 / 4.2.3.13)
 
This particular problem/fix above did not cause nodes to be expelled. It "just" affected how the nodes are reported. After the cluster is configured, DNS does not play a significant role in nodes joining or being expelled from the cluster.
 
  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
 
 
 
----- Original message -----
From: TURNER Aaron <aaron.tur...@ed.ac.uk>
Sent by: gpfsug-discuss-boun...@spectrumscale.org
To: "gpfsug-discuss@spectrumscale.org" <gpfsug-discuss@spectrumscale.org>
Cc:
Subject: [EXTERNAL] [gpfsug-discuss] Odd networking/name resolution issue
Date: Sat, May 9, 2020 6:25 AM
 
Dear All,
 
We are getting, on an intermittent basis with currently no obvious pattern, an issue with GPFS nodes reporting rejecting nodes of the form:
 
nodename.domain.domain.domain....
 
DNS resolution using the standard command-line tools of the IP address present in the logs does not repeat the domain, and so far it seems isolated to GPFS.
 
Ultimately the nodes are rejected as not responding on the network.
 
Has anyone seen this sort of behaviour before?
 
Regards
 
Aaron Turner
The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
_______________________________________________
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