vnet-tunnel-network-add
vNET managers can add, modify, and delete VXLAN tunnels from a vNET. A software VTEP server is connected to a port 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-add
|
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.0
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 add a vNET tunnel, t1, with IP address, 10.100.100.224, and netmask 155.255.255.248
CLI network-admin@switch > vnet-tunnel-network-add vnet-name t1 network 10.100.100.224 netmask 255.255.255.248