Creating Tunnels
You create tunnels to encapsulate protocols on the network. You can create tunnels for IP-in-IP, VXLAN, and NVGRE network traffic. However, Netvisor ONE supports tunnels for the local scope only and does not use any discovery mechanism.
IP-in-IP protocol encapsulates an IP header with an outer IP header for tunneling. The outer IP header source and destination identifies the endpoints of a tunnel. The inner IP header source and destination identify the original sender and recipient of the datagram.
In addition to the IP header and the VXLAN header, the VTEP also inserts a UDP header. During ECMP, the switch includes this UDP header to perform the hash function. The VTEP calculates the source port by performing the hash of the inner Ethernet frame's header. Netvisor ONE supports the Destination UDP port on the VXLAN port .
The outer IP header contains the Source IP address of the VTEP performing the encapsulation. The remote VTEP IP address or the IP Multicast group address provides the destination IP address.
Network Virtualization with Generic Routing Encapsulation (NVGRE) uses GRE to tunnel Layer 2 packets over Layer 3 networks. NVGRE seems similar to VXLAN but it doesn’t rely on IP multicast for address learning.
To create a tunnel for IP-in-IP traffic, local IP address, remote IP address, and the vrouter, leaf, use the following syntax:
CLI network-admin@switch > tunnel-create name test scope local local-ip remote-ip vrouter-name leaf1
To remove a tunnel, use the tunnel-delete command.
To modify a tunnel, use the tunnel-modify command.
To display the output for the configured tunnel, use the tunnel-show command. For example,
CLI network-admin@switch > tunnel-show name test layout vertical
scope: cluster
name: test
type: vxlan
vrouter-name: leaf1
peer-vrouter-name: leaf-test-06
router-if: eth1.10
next-hop-mac: 66:0e:94:b7:95:c3
nexthop-vlan: 4092
active: yes
state: ok
bfd: disabled
bfd-state: not-replicator-vtep
ports: 49
auto-tunnel: static
Logging Changes to Tunnel States
This feature enables you to log tunnel state changes so you view tunnel state historical data for debugging purposes. The following state changes are logged in tunnel history:
Creating tunnels
Deleting tunnels
Tunnel hardware state changes including:
l Virtual Router ID (VRID) associated with the tunnel vrouter
l the router interface associated with the tunnel local-ip
l the tunnel next hop add or remove
l tunnel next hop egress ports
l Equal-Cost Multi-Path routing (ECMP) group updates