Re: [gpfsug-discuss] help with multi-cluster setup: Network is unreachable

Sorry, I made a mistake on the original description: all our clients are already on 4.1.1-7. Jaime Quoting "J. Eric Wonderley" : Hi Jamie: I think typically you want to keep the clients ahead of the server in version. I would advance the version of you client nodes.

Re: [gpfsug-discuss] help with multi-cluster setup: Network is unreachable

I only ask that we look beyond the trivial. The existing multi-cluster setup with mixed versions of servers already work fine with 4000+ clients on 4.1. We still have 3 legacy servers on 3.5, we already have a server on 4.1 also serving fine. The brand new 4.1 server we added last week

[gpfsug-discuss] socketMaxListenConnections and net.core.somaxconn

Hello all, what happens if we set socketMaxListenConnections to a larger number than we have clients? more memory used? Thanks Matt The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive

Re: [gpfsug-discuss] help with multi-cluster setup: Network is unreachable

Hi Jamie: I think typically you want to keep the clients ahead of the server in version. I would advance the version of you client nodes. New clients can communicate with older versions of server nsds. Vice versa...no so much. ___ gpfsug-discuss

Re: [gpfsug-discuss] help with multi-cluster setup: Network is unreachable

Quoting valdis.kletni...@vt.edu: On Mon, 08 May 2017 12:06:22 -0400, "Jaime Pinto" said: Another piece og information is that as far as GPFS goes all clusters are configured to communicate exclusively over Infiniband, each on a different 10.20.x.x network, but broadcast 10.20.255.255. As far

Re: [gpfsug-discuss] help with multi-cluster setup: Network is unreachable

On Mon, 08 May 2017 12:06:22 -0400, "Jaime Pinto" said: > Another piece og information is that as far as GPFS goes all clusters > are configured to communicate exclusively over Infiniband, each on a > different 10.20.x.x network, but broadcast 10.20.255.255. As far as Have you verified that