Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
PowerScale: Network Design Considerations
Executive summary Network architecture design Latency, bandwidth, and throughput Ethernet flow control SyncIQ considerations Quality of Service (QoS) Software-Defined Networking PowerScale OneFS ports SmartConnect considerations Ethernet, MTU, and IP overhead
Introduction
Ethernet packet
Ethernet payload
Jumbo frames
IP packet overhead
Data payload to Ethernet frame efficiency
ICMP and MTU with OneFS
OneFS MTU commands
VLAN and interface MTU
Confirming transmitted MTU
Access Zones best practices Source-Based Routing considerations Isilon 6th generation 1 GbE interfaces Intelligent Platform Management Interface IPv6 OneFS host-based firewall Network troubleshooting Appendix A: Supported network optics and transceivers Appendix B: Technical support and resources

Confirming transmitted MTU

Confirming transmitted MTU

  • Manually checking a permitted MTU ensures a configured MTU is transmitted. The ping command is used to confirm if an MTU can be transmitted. Start with the largest MTU and work down to find the limit.

    For example, to check if an MTU of 8900 bytes is transmitted to an endpoint, from the OneFS CLI, use the following command: ping –s 8900 –D <IP Address>. The -s specifies the packet size, and the -D specifies not to fragment the packet.

    If the ping is successful, the MTU is transmitted across. If the ping is unsuccessful, gradually lower the MTU until it is successfully transmitted. Verify that the MTU can be transmitted from both endpoints.

    OneFS is based on FreeBSD. FreeBSD also has options for gradually increasing the MTU by performing a “sweeping ping” using the –g option. For more information about ping options in FreeBSD, access the FreeBSD manual at the following link: https://www.freebsd.org/cgi/man.cgi?ping(8)