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

Ethernet payload

Ethernet payload

  • The Ethernet payload varies based on the type of data it is carrying. It is a combination of either TCP, UDP, or RTP header combined with an IPv4 or IPv6 header, and most importantly the actual payload which contains the data that is being sent. The fields within the payload are displayed in the following figure:

    TableDescription automatically generated

    Figure 22.    Ethernet payload options

    As shown in the figure, the amount of actual data sent within an Ethernet Frame is dependent upon the number of bytes consumed by the other fields. Other options are available which are not listed here. For example, Linux hosts automatically add a timestamp to the TCP stack, adding 12 bytes.