Re: [gpfsug-discuss] Ganesha all IPv6 sockets - ist this to be expected?

Malahal R Naineni Thu, 03 Oct 2019 22:50:34 -0700

Ganesha uses /etc/netconfig for using IPv6 or IPv4. It will use IPv6 only, unless you remove/comment IPv6 entries from /etc/netconfig, then it will use IPv4.

If IPv6 is configured in /etc/netconfig, it will try creating socket() with IPv6. If that fails with EAFNOSUPPORT, then it will fall back to IPv4. Any other error code, it bails out with an error message. So with your original initramfs, it is possible that socket() call for IPv6 might be failing with a different error.

Regards, Malahal.

----- Original message -----
From: "Billich Heinrich Rainer (ID SD)" <[email protected]>
Sent by: [email protected]
To: gpfsug main discussion list <[email protected]>
Cc:
Subject: [EXTERNAL] Re: [gpfsug-discuss] Ganesha all IPv6 sockets - ist this to be expected?
Date: Tue, Oct 1, 2019 6:04 PM

Hello,

I wanted to completely disable IPv6 to get ganesha to use IPv4 sockets only. Once we did set the sysctl configs to disable IPv6 *and* did rebuild the initramfs.*.img file to include the new settings IPv6 was completely gone and ganesha did open an IPv4 socket only. We missed to rebuild the initramfs.*.img file in the first trial. Rpcbind/ganesha failed to start without the initramfs rebuild.

Cheers, Heiner

Some related documents from netapp

https://access.redhat.com/solutions/8709#‌rhel7disable

https://access.redhat.com/solutions/2798411

https://access.redhat.com/solutions/2963091

From: <[email protected]> on behalf of "Billich Heinrich Rainer (ID SD)" <[email protected]>
Reply to: gpfsug main discussion list <[email protected]>
Date: Monday, 16 September 2019 at 17:51
To: gpfsug main discussion list <[email protected]>
Subject: Re: [gpfsug-discuss] Ganesha all IPv6 sockets - ist this to be expected?

Hello Olaf,

Thank you, so we’ll try to get rid of IPv6. Actually we do have this settings active but I may have to add them to the initrd file, too. (See https://access.redhat.com/solutions/8709#‌rhel7disable) to prevent ganesha from opening an IPv6 socket. It’s probably no big issue if ganesha uses IPv4overIPv6 for all connections, but to keep things simple I would like to avoid it.

@Edward

We got /etc/tuned/scale/tuned.conf with GSS/xCAT. I’m not sure whether it’s part of any rpm.

Cheers,

Heiner

From: <[email protected]> on behalf of Olaf Weiser <[email protected]>
Reply to: gpfsug main discussion list <[email protected]>
Date: Monday, 16 September 2019 at 09:12
To: gpfsug main discussion list <[email protected]>
Subject: Re: [gpfsug-discuss] Ganesha all IPv6 sockets - ist this to be expected?

Hallo Heiner,
usually, Spectrum Scale comes with a tuned profile (named scale) ..

[root@nsd01 ~]# tuned-adm active
Current active profile: scale

in there
[root@nsd01 ~]# cat /etc/tuned/scale/tuned.conf | tail -3
# Disable IPv6
net.ipv6.conf.all.disable_ipv6=1
net.ipv6.conf.default.disable_ipv6=1
[root@nsd01 ~]#

depending on .... what you need to achieve .. one might be forced to changed that.. e.g. for RoCE .. you need IPv6 to be active ...
but for all other scenarios with SpectrumScale (at least what I'm aware of right now) ... IPv6 can be disabled...

From: "Billich Heinrich Rainer (ID SD)" <[email protected]>
To: gpfsug main discussion list <[email protected]>
Date: 09/13/2019 05:02 PM
Subject: [EXTERNAL] [gpfsug-discuss] Ganesha all IPv6 sockets - ist this to be expected?
Sent by: [email protected]

Hello,

I just noted that our ganesha daemons offer IPv6 sockets only, IPv4 traffic gets encapsulated. But all traffic to samba is IPv4, smbd offers both IPv4 and IPv6 sockets.
I just wonder whether this is to be expected? Protocols support IPv4 only, so why running on IPv6 sockets only for ganesha? Did we configure something wrong and should completely disable IPv6 on the kernel level

Any comment is welcome

Cheers,
Heiner
--
=======================
Heinrich Billich
ETH Zürich
Informatikdienste
Tel.: +41 44 632 72 56
[email protected]
========================

I did check with

ss -l -t -4
ss -l -t -6

add -p to get the process name, too.

do you get the same results on your ces nodes?

[root@nas22ces04-i config_samples]# ss -l -t -4
State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 8192 *:gpfs *:*
LISTEN 0 50 *:netbios-ssn *:*
LISTEN 0 128 *:5355 *:*
LISTEN 0 128 *:sunrpc *:*
LISTEN 0 128 *:ssh *:*
LISTEN 0 100 127.0.0.1:smtp *:*
LISTEN 0 10 10.250.135.24:4379 *:*
LISTEN 0 128 *:32765 *:*
LISTEN 0 50 *:microsoft-ds *:*
[root@nas22ces04-i config_samples]# ss -l -t -6
State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 128 :::32767 :::*
LISTEN 0 128 :::32768 :::*
LISTEN 0 128 :::32769 :::*
LISTEN 0 128 :::2049 :::*
LISTEN 0 128 :::5355 :::*
LISTEN 0 50 :::netbios-ssn :::*
LISTEN 0 128 :::sunrpc :::*
LISTEN 0 128 :::ssh :::*
LISTEN 0 128 :::32765 :::*
LISTEN 0 50 :::microsoft-ds :::*

_______________________________________________
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

_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss

Re: [gpfsug-discuss] Ganesha all IPv6 sockets - ist this to be expected?

Reply via email to