Users Guide
Table Of Contents
- Table of Contents
- 1 Regulatory and Safety Approvals
- 2 Functional Description
- 3 Network Link and Activity Indication
- 4 Features
- 4.1 Software and Hardware Features
- 4.2 Virtualization Features
- 4.3 VXLAN
- 4.4 NVGRE/GRE/IP-in-IP/Geneve
- 4.5 Stateless Offloads
- 4.6 Priority Flow Control
- 4.7 Virtualization Offload
- 4.8 SR-IOV
- 4.9 Network Partitioning (NPAR)
- 4.10 Security
- 4.11 RDMA over Converged Ethernet – RoCE
- 4.12 VMWare Enhanced Networking Stack (ENS)
- 4.13 Supported Combinations
- 4.14 Unsupported Combinations
- 5 Installing the Hardware
- 6 Software Packages and Installation
- 7 Updating the Firmware
- 8 Link Aggregation
- 9 System-Level Configuration
- 10 PXE Boot
- 11 SR-IOV – Configuration and Use Case Examples
- 12 NPAR – Configuration and Use Case Example
- 13 Tunneling Configuration Examples
- 14 RoCE – Configuration and Use Case Examples
- 15 DCBX – Data Center Bridging
- 16 DPDK – Configuration and Use Case Examples
- Revision History
Broadcom NetXtreme-E-UG304-2CS
34
NetXtreme-E User Guide User Guide for Dell Platforms
NVGRE is a method for network virtualization, similar to VXLAN in purpose. NVGRE uses a GRE header. The key field
defined in RFC 2890 is used to carry a virtual subnet identifier. NVGRE is identified using EtherType = 0x6558, the EtherType
for Transparent Ethernet Bridging (carrying a full Ethernet frame as the payload).
4.7.4.3 Geneve
The NetXtreme-E family of Ethernet controllers supports Generic Network Virtualization Encapsulation (Geneve, also known
as Next Generation Encapsulation). It leverages the same concepts as VXLAN, using UDP destination port to identify the
presence of the Geneve tunnel header. A primary goal for Geneve is to enable transport of metadata (system state) between
source and destination.
4.7.4.4 IP-in-IP
IP-in-IP is a Layer 3 overlay or tunneling scheme over a Layer 3 network. It is a method by which an IP datagram may be
encapsulated (carried as payload) within another IP datagram for the purpose of altering the routing of the inner IP packets
and allowing them to be delivered to an intermediate destination that would otherwise not be selected by the destination
Address field in the inner IP header. IP Encapsulation with IP is defined in RFC 2003.
This document focuses on a UDP datagram or TCP segment carried inside the IP-in-IP packet.
4.7.4.5 Checksum Offload
The following checksums are computed on transmit path and then computed and verified on the receive path.
Outer IPv4 checksum if the outer IP datagram is an IPv4 datagram.
Outer UDP checksum (if non-zero): The current VXLAN IETF draft suggests that the outer UDP checksum should be
transmitted as zero. If the outer UDP checksum field in the VXLAN frame received is zero, then the frame is accepted
without computing outer UDP checksum. If the outer UDP checksum field in the VXLAN frame received is non-zero,
then the outer UDP checksum should be computed. (Note: The current IETF draft allows the receiver to ignore outer
UDP checksum when it is set to non-zero.) This item is not available in L2GRE/NVGRE/IP-in-IP -aware offload.
Inner IPv4 checksum if the inner IP datagram is an IPv4 datagram.
Inner UDP or TCP checksum.
4.7.4.6 VLAN Tagging
A VXLAN-frame supports the following tagging options:
No IEEE 802.1Q tag in inner and outer datagrams.
IEEE 802.1Q tag in the outer IP datagram only.
IEEE 802.1Q tag in the inner IP datagram only.
IEEE 802.1Q tags in both the inner and outer IP datagrams.
NOTE: The device supports insertion and removal of outer IEEE 801.Q Tag for VXLAN/GRE/IP-in-IP frames. It also
supports insertion and removal of inner 8IEEE 01.Q Tag for VXLAN.frames. The device retains inner IEEE 801.Q
Tag for NVGRE frames in the inner packet.
4.7.4.7 VMQ
For VXLAN frames, the NetQueue uses the following fields for the queue selection:
Inner destination MAC address.
Outer destination MAC address.
VXLAN Network Identifier (VNI).