VNET managers can add, modify, and delete VXLAN tunnels from a VNET. A software VTEP server is connected to a port that is not part of the VNET. The port for the software VTEP server is configured (tagged or untagged) for a VLAN configured by the fabric administrator that routes into the Layer 3 network used by the hardware VTEPs. The VNET administrator accesses the VTEP server using either an out of band management port or a dedicated in-band vlan.

Syntax   vnet-tunnel-network-show name name-string network ip-address netmask netmask description description-string 

name name-string

Specify the name for the VNET tunnel.

network ip-address

Specify the IP address for the tunnel.

netmask netmask

Specify the netmask of the IP address.

description description-string

Specify a description for the VNET tunnel.

Defaults   None

Access   VNET Administrator

History   Command introduced in Version 2.5.

Usage   The fabric administrator enables the vnet administrator to create tunnels from software VTEPs to hardware VTEPs by provisioning a route on each switch from a VLAN or subnet associated with the VNET to the Layer 3 network where hardware VTEP tunnels are configured. In addition, ACLs are configured to constrain software VTEPs to only exchange packets with software VTEPs in the same VNET and hardware VTEPs.

Examples  To display a VNET tunnel, t1, with IP address,, and netmask, use the following syntax:

CLI network-admin@switch > vnet-tunnel-network-add vnet-name t1 network netmask