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
101
NetXtreme-E User Guide User Guide for Dell Platforms
13.4 GRE Tunnelling
An IP GRE is an IP inside an IP tunnel which can carry private network traffic between two heterogeneous networks. On the
VM, use the following commands:
modprobe ip_gre;
ip tunnel add gre45 mode gre local <public IP> remove <Private IP>
ip link set dev gre45 up;
ip addr add <private IP>/mask broadcast <broadcast ip> dev gre45
In this example, gre45 is the interface name.
13.5 IP-in-IP Tunnelling
Similar to GRE, IP-in-IP is another encapsulation that carries a private IP onto a public IP. Use the following commands:
modprobe ipip
ip tunnel add ipip45 mode ipip remote <Peer IP> local <private ip> ttl 255 dev <VM Interface Name>
ip link set dev ipip45 up
ip addr add dev ipip45 <IP addr> peer <Peer IP>/mask
ip link set dev ipip45 up
13.6 VXLAN – Configuration and Use Case Examples
VXLAN encapsulation permits multiple virtual machines or containers residing on one server to be isolated from each other
in virtual tunnels by encapsulating traffic with VXLAN headers. Broadcom NetXtreme controllers accelerate this
encapsulation and de-encapsulation in hardware.
This example discusses basic VXLAN connectivity between two Linux servers. Each server has one physical NIC enabled
with outer IP address set to 1.1.1.4 and 1.1.1.2, respectively.
A VXLAN interface with ID 10 is created with multicast group 239.0.0.10 and is associated with physical network port eth1
on each server.
An IP address for the host is created on each server and associated to that VXLAN interface. Once the VXLAN interface is
brought up, the VM present in system 1 can communicate with the VM present in system 2 using the VXLAN interfaces. The
VLXAN format is shown in Table 31.
Table 32 provides VXLAN command and configuration examples.
Table 31: VXLAN Frame Format
MAC header Outer IP header with proto =
UDP
UDP header with Destination
port= VXLAN
VXLAN header (Flags, VNI) Original L2
Frame
FCS
Table 32: VXLAN Command and Configuration Examples
System 1 System 2
ifconfig eth1 1.1.1.4/24 ifconfig eth1 1.1.1.2/24
ip link add vxlan10 type vxlan id 10 group 239.0.0.10 dev
eth1 dstport 4789
ip link add vxlan10 type vxlan id 10 group 239.0.0.10 dev eth1 dstport 4789
ifconfig vxlan10 192.168.1.5 mtu 1450 ifconfig vxlan10 192.168.1.10 mtu 1450
ip --d link show vxlan10 –