Configuring OVSDB with Netvisor ONE

There are a number of steps required to configure OVSDB using Netvisor One.


1. Configure the vNET with the number of private VLANs, VXLANs, and managed ports:

CLI (network-admin@Leaf1) > vnet-create name name-string vlans vlan-range num-private-vlans integer vxlans vxlan-id managed-ports port-list 

2. Configure the underlay network:

CLI (network-admin@Leaf1) > vrouter-create name-string vnet name-string router type hardware

CLI (network-admin@Leaf1) > vrouter-interface-add vrouter-name name-string vlan vlan-id ip ip-address netmask netmask 

3. Configure the tunnel:

CLI (network-admin@Leaf1) > vnet-tunnel-network-add name name-string network ip-address netmask netmask 

CLI (network-admin@Leaf1) > trunk-modify name name-string trunk-id trunk-id port port-list 

4. Create the SSL/TLS certificate:

CLI (network-admin@Leaf1) > cert-create name name-string country country-string state state-string city city-string organization organization-string organizational-unit organizational-unit-string common-name common-name-string container zone name-string

5. Configure OVSDB:

CLI (network-admin@Leaf1) > openvswitch-create name name-string vnet name-string global-vtep tunnel-ip ip-address dedicated-service cert-name name-string

CLI (network-admin@Leaf1) > openvswitch-interface-add ovs-name name-string ip ip-address netmask netmask if data|mgmt vlan vlan-id

Configuring the interface as data or management depends on the location of the controller, on the data network or the management network.


If the controller is on a Layer 3 network several hops away, use openvswitch-modify to configure a gateway IP address. This is required in order for the configuration to work properly.


6. Add the hardware VTEP manager:

CLI (network-admin@Leaf1) > opensvswitch-hwvtep-manager-add name name-string manager-type odl|nsx connection-method ssl ip ip-address username username-string password password-string port port-number

Netvisor automatically establishes the VXLAN tunnel between the local and remote hardware and software VTEPs.

If you connect to VMware NSX controllers, you must use SSL or TLS to securely connect with the hardware VTEP.