<div><font size=2 face="sans-serif">Hallo Heiner, </font><br><font size=2 face="sans-serif">usually, Spectrum Scale comes with a
tuned profile (named scale) .. </font><br><br><tt><font size=3>[root@nsd01 ~]# tuned-adm active <br>Current active profile: scale<br></font></tt><div><br><font size=2 face="sans-serif">in there </font><br><tt><font size=3>[root@nsd01 ~]# cat /etc/tuned/scale/tuned.conf |
tail -3 <br># Disable IPv6 <br>net.ipv6.conf.all.disable_ipv6=1 <br>net.ipv6.conf.default.disable_ipv6=1 <br>[root@nsd01 ~]# <br></font></tt><br><font size=2 face="sans-serif">depending on .... what you need to achieve
.. one might be forced to changed that.. e.g. for RoCE .. you need IPv6
to be active ... </font><br><font size=2 face="sans-serif">but for all other scenarios with SpectrumScale
(at least what I'm aware of right now) ... IPv6 can be disabled... </font><br><br><br><br><br><br><br><br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Billich Heinrich
Rainer (ID SD)" <heinrich.billich@id.ethz.ch></font><br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">gpfsug main discussion
list <gpfsug-discuss@spectrumscale.org></font><br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">09/13/2019 05:02 PM</font><br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[EXTERNAL] [gpfsug-discuss]
Ganesha all IPv6 sockets - ist this to be expected?</font><br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">gpfsug-discuss-bounces@spectrumscale.org</font><br><hr noshade><br><br><br><tt><font size=2><br>Hello,<br><br>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. <br>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<br><br>Any comment is welcome<br><br>Cheers,<br>Heiner<br>-- <br>=======================<br>Heinrich Billich<br>ETH Zürich<br>Informatikdienste<br>Tel.: +41 44 632 72 56<br>heinrich.billich@id.ethz.ch<br>========================<br> <br><br>I did check with<br><br> ss -l -t -4<br> ss -l -t -6<br><br>add -p to get the process name, too.<br><br>do you get the same results on your ces nodes?<br><br><br>[root@nas22ces04-i config_samples]# ss -l -t -4<br>State Recv-Q Send-Q
Local Address:Port
Peer Address:Port<br>LISTEN 0 8192
*:gpfs
*:*<br>LISTEN 0 50
*:netbios-ssn
*:*<br>LISTEN 0 128
*:5355
*:*<br>LISTEN 0 128
*:sunrpc
*:*<br>LISTEN 0 128
*:ssh
*:*<br>LISTEN 0 100
127.0.0.1:smtp
*:*<br>LISTEN 0 10
10.250.135.24:4379
*:*<br>LISTEN 0 128
*:32765
*:*<br>LISTEN 0 50
*:microsoft-ds
*:*<br>[root@nas22ces04-i config_samples]# ss -l -t -6<br>State Recv-Q Send-Q
Local Address:Port
Peer Address:Port<br>LISTEN 0 128
:::32767
:::*<br>LISTEN 0 128
:::32768
:::*<br>LISTEN 0 128
:::32769
:::*<br>LISTEN 0 128
:::2049
:::*<br>LISTEN 0 128
:::5355
:::*<br>LISTEN 0 50
:::netbios-ssn
:::*<br>LISTEN 0 128
:::sunrpc
:::*<br>LISTEN 0 128
:::ssh
:::*<br>LISTEN 0 128
:::32765
:::*<br>LISTEN 0 50
:::microsoft-ds
:::*<br><br>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><tt><font size=2>http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></tt></a><tt><font size=2><br><br></font></tt><br><br></div></div><BR>