Configure vNV - L3 Scenario


Virtual Netvisor (vNV) can be used in conjunction with UNUM to create a seed switch.


Install vNV on the same ESXi server as UNUM, and it reduces the impact of UNUM polling on physical switches.


This section details how to configure vNV in a fabric over an L3 scenario.


Topology


Topology Layer 3


Use the above topology for this demonstration. Here, switches use VLAN 4000 for fabric communication (by default, we use VLAN 1 for fabric communication).


VLAN 11 connected via eth2 (Network Adapter 3) is used to communicate with the rest of the fabric.


VM Properties


A vNV has three interfaces, Eth0, Eth1, and Eth2. In the VM, these interfaces are Network Adapter 1, Network Adapter 2, and Network Adapter 3, respectively.


Eth0 (Network Adapter 1) is not connected anywhere in the VM configuration. Eth1 (Network Adapter 2) and Eth2 (Network Adapter 3) are for management and in-band communication, as illustrated in the image below.



VMware NIC Settings


Port Group Configuration


Following Port Groups (PG) properties are selected on PGs that are associated to VM interfaces Network Adapter 2 and Network Adapter 3.


VLAN ID - 4095


Security   Promiscuous mode – Accept

Security MAC address Changes – Accept

Security Forged Transmits - Accept


The figure below demonstrates the same.



VMware Port Group Security Settings


vNV Configuration


You need to configure vNV to communicate with other switches in the fabric and to ensure vNV’s in-band network is reachable from the rest of the fabric.

Management/in-band Shell Configuration


The following is the vmgmt0 (mgmt) and vdata0 (in-band) interface configuration of vNV.


From below snippet, 10.20.11.11/24 is associated with vdata0 (in-band) and 10.13.25.241/23 is associated with vmgmt0 (mgmt).


vdata0

Link encap: Ethernet 

HWaddr 66:0e:94:f9:53:ba

inet addr: 10.20.11.11

Bcast: 10.20.11.255

Mask: 255.255.255.0


vmgmt0 

Link encap: Ethernet

HWaddr 66:0e:94:f9:ac:0a

inet addr: 10.13.25.241

Bcast: 10.13.25.255

Mask: 255.255.254.0


vNV CLI Configuration


VLAN Configuration:

CLI (network-admin@DISC-vNV*) > running-config-show | grep vlan-create

CLI (network-admin@DISC-vNV*) > vlan-create id 11 replicators none scope local description vlan-11 ports 1-63,65-271

CLI (network-admin@DISC-vNV*) > vlan-create id 4000 replicators none scope local description vlan-4000 ports 1-271


Here VLAN 11 is used to connect to the rest of the fabric through eth2 (Network Adapter 3) and VLAN 4000 is used to patch in-band interface to vRouter zone.


vRouter Configuration


CLI (network-admin@DISC-vNV*) > running-config-show | grep vlan-create

CLI (network-admin@DISC-vNV*) > vlan-create id 11 replicators none scope local description vlan-11 ports 1-63,65-271

CLI (network-admin@DISC-vNV*) > vlan-create id 4000 replicators none scope local description vlan-4000 ports 1-271


Here vRouter type is “fabric-comm” and is needed in case of fabric over L3 configuration.



vRouter Interface Configuration


CLI (network-admin@DISC-vNV*) > running-config-show | grep vrouter-interface-add

CLI (network-admin@DISC-vNV*) > vrouter-interface-add vrouter-name DISC-vNV nic eth1.11 ip 10.0.1.11/24 assignment2 none vlan 11

CLI (network-admin@DISC-vNV*) > vlan-type public if data if-nat-realm internal

CLI (network-admin@DISC-vNV*) > vrouter-interface-add vrouter-name DISC-vNV nic eth0.4000 ip 10.20.11.100/24 assignment2 none vlan 4000 vlan-type public if data fabric-nic if-nat-realm internal


The VLAN-11 interface communicates with the fabric, and the VLAN-4000 interface to reach the switch in-band IP. 


The VLAN-4000 interface IP is in the same subnet as switch in-band IP and that interface is “fabric-nic.”


Switch Route Configuration


Switch routes are configured to reach in-band IPs of other switches from the global zone.


CLI (network-admin@DISC-vNV*) > running-config-show | grep switch-route-create

CLI (network-admin@DISC-vNV*) > switch-route-create network 10.0.1.0/24 gateway-ip 10.20.11.100

CLI (network-admin@DISC-vNV*) > switch-route-create network 10.20.1.0/30 gateway-ip 10.20.11.100

CLI (network-admin@DISC-vNV*) > switch-route-create network 10.20.2.0/24 gateway-ip 10.20.11.100

CLI (network-admin@DISC-vNV*) > switch-route-create network 10.20.3.0/24 gateway-ip 10.20.11.100

CLI (network-admin@DISC-vNV*) > switch-route-create network 10.20.4.0/24 gateway-ip 10.20.11.100

CLI (network-admin@DISC-vNV*) > switch-route-create network 10.20.5.0/24 gateway-ip 10.20.11.100

CLI (network-admin@DISC-vNV*) > switch-route-create network 10.20.6.0/24 gateway-ip 10.20.11.100

CLI (network-admin@DISC-vNV*) > switch-route-create network 10.20.7.0/24 gateway-ip 10.20.11.100


Networks defined here are the in-band networks of other switches in the fabric and 10.20.11.100 is the VLAN-4000 IP configured on the vNV vRouter.



vRouter Static Route Configuration


CLI (network-admin@DISC-vNV*) > running-config-show | grep vrouter-static

CLI (network-admin@DISC-vNV*) > vrouter-static-route-add vrouter-name DISC-vNV network 0.0.0.0/0 gateway-ip 10.0.1.1


The default route is now 10.0.1.1, which is on the other end of the VLAN-11 vrouter interface reachable through eth2 (Network Adapter 3).


With this, you are able to reach in-band IPs of switches in the fabric and vNV is able to join the fabric.

north
    keyboard_arrow_up
    keyboard_arrow_down
    description
    print
    feedback
    support
    business
    rss_feed
    south