Hi Guys!
I recently upgraded from TrueNAS 13 to TrueNAS Scale on my testing environment.
Whilst the upgrade went well and my pools are still alive, I have some issues on my 10G network.
From my VMWare ESXI hosts I cannot ping any more with a packet size of 8972 to my TrueNAS server (192.168.10.55):
Using a lower packet size works, up to max. 8954, 8955 and higher fails.
Vice vesa, from my TrueNAS box to my ESXI host, it's the same issue: Pings with jumbo packets up to 8954 work fine, 8955 and higher doesn't:
Of course, MTU is set properly to 9000 everywhere.
I then tried to increase the sysctl variable "kern.ipc.maxsockbuf", however, this one seems not to work on TrueNAS scale, whilst it did on TrueNAS 12 and 13.
Any help on the one or the other issue would be appreciated!
Thanks a lot and best wishes,
I recently upgraded from TrueNAS 13 to TrueNAS Scale on my testing environment.
Whilst the upgrade went well and my pools are still alive, I have some issues on my 10G network.
From my VMWare ESXI hosts I cannot ping any more with a packet size of 8972 to my TrueNAS server (192.168.10.55):
Code:
[root@fra-esxi2:~] vmkping -d -s 8972 -I vmk1 192.168.10.55 PING 192.168.10.55 (192.168.10.55): 8972 data bytes --- 192.168.10.55 ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss [root@fra-esxi2:~] vmkping -d -s 8954 -I vmk1 192.168.10.55 PING 192.168.10.55 (192.168.10.55): 8954 data bytes 8962 bytes from 192.168.10.55: icmp_seq=0 ttl=64 time=0.486 ms 8962 bytes from 192.168.10.55: icmp_seq=1 ttl=64 time=0.411 ms 8962 bytes from 192.168.10.55: icmp_seq=2 ttl=64 time=0.403 ms --- 192.168.10.55 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.403/0.433/0.486 ms [root@fra-esxi2:~] ^C [root@fra-esxi2:~] vmkping -d -s 8955 -I vmk1 192.168.10.55 PING 192.168.10.55 (192.168.10.55): 8955 data bytes --- 192.168.10.55 ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss [root@fra-esxi2:~]
Using a lower packet size works, up to max. 8954, 8955 and higher fails.
Vice vesa, from my TrueNAS box to my ESXI host, it's the same issue: Pings with jumbo packets up to 8954 work fine, 8955 and higher doesn't:
Code:
root@argos[~]# ping 192.168.10.57 -s 8954 PING 192.168.10.57 (192.168.10.57) 8954(8982) bytes of data. 8962 bytes from 192.168.10.57: icmp_seq=1 ttl=64 time=0.343 ms 8962 bytes from 192.168.10.57: icmp_seq=2 ttl=64 time=0.337 ms ^C --- 192.168.10.57 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1003ms rtt min/avg/max/mdev = 0.337/0.340/0.343/0.003 ms root@argos[~]# ping 192.168.10.57 -s 8955 PING 192.168.10.57 (192.168.10.57) 8955(8983) bytes of data. ^C --- 192.168.10.57 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2049ms root@argos[~]#
Of course, MTU is set properly to 9000 everywhere.
I then tried to increase the sysctl variable "kern.ipc.maxsockbuf", however, this one seems not to work on TrueNAS scale, whilst it did on TrueNAS 12 and 13.
Code:
root@argos[~]# sysctl kern.ipc.maxsockbuf sysctl: cannot stat /proc/sys/kern/ipc/maxsockbuf: No such file or directory root@argos[~]#
Any help on the one or the other issue would be appreciated!
Thanks a lot and best wishes,
