[gpfsug-discuss] Ganesha all IPv6 sockets - ist this to be expected?
Christopher Black
cblack at nygenome.org
Mon Sep 16 15:55:34 BST 2019
On our recent ESS systems we do not see /etc/tuned/scale/tuned.conf (or script.sh) owned by any package (rpm -qif …).
I’ve attached what we have on our ESS 5.3.3 systems.
Best,
Chris
From: <gpfsug-discuss-bounces at spectrumscale.org> on behalf of "Wahl, Edward" <ewahl at osc.edu>
Reply-To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date: Monday, September 16, 2019 at 10:50 AM
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Subject: Re: [gpfsug-discuss] Ganesha all IPv6 sockets - ist this to be expected?
What package provides this /usr/lib/tuned/ file?
Ed
________________________________
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: Monday, September 16, 2019 3:12 AM
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
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 at nsd01 ~]# tuned-adm active
Current active profile: scale
in there
[root at 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 at 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)" <heinrich.billich at id.ethz.ch>
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date: 09/13/2019 05:02 PM
Subject: [EXTERNAL] [gpfsug-discuss] Ganesha all IPv6 sockets - ist this to be expected?
Sent by: gpfsug-discuss-bounces at spectrumscale.org
________________________________
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
heinrich.billich at id.ethz.ch
========================
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 at 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 at 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss&d=DwMFAw&c=C9X8xNkG_lwP_-eFHTGejw&r=DopWM-bvfskhBn2zeglfyyw5U2pumni6m_QzQFYFepU&m=vVQfi9vKAMyJJJkblLG-6lFn75kWWfpc6yGZpiIkJMo&s=l9Yuaa-imE1XkV2RV-lyYdcH0aRV2klb5vXbPDHg6F4&e=>
________________________________
This message is for the recipient’s use only, and may contain confidential, privileged or protected information. Any unauthorized use or dissemination of this communication is prohibited. If you received this message in error, please immediately notify the sender and destroy all copies of this message. The recipient should check this email and any attachments for the presence of viruses, as we accept no liability for any damage caused by any virus transmitted by this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20190916/8f60d415/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tuned.conf
Type: application/octet-stream
Size: 2859 bytes
Desc: tuned.conf
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20190916/8f60d415/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: script.sh
Type: application/octet-stream
Size: 270 bytes
Desc: script.sh
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20190916/8f60d415/attachment-0005.obj>
More information about the gpfsug-discuss
mailing list