Example Configuration

In this example, you have the following configurations on two switches (SW1 and SW2) on the network:

1. On SW1, configure a vRouter:

vrouter-create name vrrp-rtr1 vnet vrrp-router router-type hardware enable

Add the first vRouter interface:

vrouter-interface-add vrouter-name vrrp-rtr1 ip 192.168.11.3 netmask 24 vlan 100 if data

3. Use the vrouter-interface-show command to see the name of the interface:

CLI network-admin@switch > vrouter-interface-show format all layout vertical

vrouter-name: vrrp-rtr1

nic: eth0.100

ip: 192.168.11.3/24

assignment: static

mac: 66:0e:94:dd:18:c4

vlan: 100

vxlan: 0

if: data

alias-on:

exclusive: no

nic-config: enable

nic-state: up

 

4. Create the VRRP interface:

CLI (server-switch)>vrouter-interface-add vrouter-name vrrp-rtr1 ip 192.168.11.2 netmask 24 vlan 100 if data vrrp-id 10 vrrp-primary eth0.100 vrrp-priority 100

5. Create the vRouter and interfaces on SW2:

CLI network-admin@switch > vrouter-create name vrrp-rtr2 vnet vrrp-router router-type hardware dedicated-vnet-service

6. Add the vRouter interface:

CLI network-admin@switch > vrouter-interface-add vrouter-name vrrp-rtr2 ip 192.168.11.4 netmask 24 vlan 100 if data

7. Use the vrouter-interface-show command to see the name of the interface:

CLI network-admin@switch > vrouter-interface-show format all layout vertical

vrouter-name: vrrp-router2

nic: eth2.100

ip: 192.168.11.3/24

assignment: static

mac: 66:0e:94:21:a9:6c

vlan: 100

vxlan: 0

if: data

alias-on:

exclusive: no

nic-config: enable

nic-state: up

 

8. Create the VRRP interface:

CLI network-admin@switch > vrouter-interface-add vrouter-name vrrp-rtr2 ip 192.168.11.2 netmask 24 vlan 100 if data vrrp-id 10 vrrp-primary eth0.100 vrrp-priority 50

9. Display the information about the VRRP setup:

CLI network-admin@switch > vrouter-interface-show format all layout vertical

vrouter-name: vrrp-router1

nic: eth0.100

ip: 192.168.11.3/24

assignment: static

mac: 66:0e:94:dd:18:c4

vlan: 100

vxlan: 0

if: data

alias-on:

exclusive: no

nic-config: enable

nic-state: up

vrouter-name: vrrp-router1

nic: eth1.100

ip: 192.168.11.2/24

assignment: static

mac: 00:00:5e:00:01:0a

vlan: 100

vxlan: 0

if: data

alias-on:

exclusive: no

nic-config: enable

nic-state: up

vrrp-id: 10

vrrp-primary: eth1.100

vrrp-priority: 100

vrrp-state: master

vrouter-name: vrrp-router2

nic: eth3.100

ip: 192.168.11.4/24

assignment: static

mac: 66:0e:94:21:54:07

vlan: 100

vxlan: 0

if: data

alias-on:

exclusive: no

nic-config: enable

nic-state: up

vrouter-name: vrrp-router2

nic: eth3.100

ip: 192.168.11.2/24

assignment: static

mac: 00:00:5e:00:01:0a

vlan: 100

vxlan: 0

if: data

alias-on:

exclusive: no

nic-config: enable

nic-state: down

Pluribus Networks Configuration Guide

pluribusnetworks.com 87

vrrp-id: 10

vrrp-primary: eth3.100

vrrp-priority: 50

vrrp-state: slave

 

When you intentionally disable the VRRP interface, the slave interface becomes the master interface:

vrouter-name: vrrp-router2

nic: eth3.100

ip: 192.168.11.1/24

assignment: static

mac: 00:00:5e:00:01:0a

vlan: 100

vxlan: 0

if: data

alias-on:

exclusive: no

nic-config: enable

nic-state: up

vrrp-id: 10

vrrp-primary: eth3.100

vrrp-priority: 50

vrrp-state: master

 

When you re-enable the VRRP interface, it becomes the master again, and the second interface returns to the slave:

vrouter-name: vrrp-router2

nic: eth3.100

ip: 192.168.11.2/24

assignment: static

mac: 00:00:5e:00:01:0a

vlan: 100

vxlan: 0

if: data

alias-on:

exclusive: no

nic-config: enable

nic-state: down

vrrp-id: 10

vrrp-primary: eth3.100

vrrp-priority: 50

vrrp-state: slave

 

Layer 3 Table Validation

Layer 3 entries can become unsynchronized between the software table and the hardware table. This is useful when routes are modified while the routes are updating on the network. This feature adds parameters to the l3-setting-modify command to automatically check Layer 3 entries:

l3-setting-modify

one or more of the following options:

 

aging-time seconds

Specify the aging-time for Layer 3 entries, use 0 to disable aging.

convergence-time seconds

Specify the unicast convergence time on bootup (seconds)

l3-checker|no-l3-checker

Specify if you want to check Layer 3 consistency

l3-checker-interval duration: #d#h#m#

Specify the interval for Layer 3 consistency checker

l3-checker-fix|
no-l3-checker-fix

Enable fixing of inconsistent entries

 

Two commands are available to manually check and fix Layer 3 inconsistencies:

l3-check-fix

l3-check-show

 

Active-Active VLAG with Link-State Layer 3 Unicast Protocols

 

There are VLAG egress filtering rules for packets ingressing cluster links that prevent packets from egressing VLAGs. In addition to the properties of control packets in unicast routing protocols, such as OSPF, that set TTL=1, make it difficult to support routing protocols from creatingLayer3 adjacencies over VLAGs. This feature allows unicast routing protocols such as OSPF to form Layer3 adjacencies over VLAGs, by implementing a dual-forwarder logic, while at the same time allowing routing control packets to be directed to the right cluster switch. This feature is enabled by default, but you enable or disable it on a per vRouter basis. When the feature is ON, the cluster vRouter implements special logic to synchronize vRouter gateway MAC addresses as well as vrouter interface IP addresses with the cluster peer.

When you configure the ports for active-active VLAG, you should use the port-config-modify command and add the parameter jumbo to support jumbo frames on the network.

CLI (network-admin@spine1)>vrouter-modify vrouter-name name-string cluster-active-active-routing|no-cluster-active-active-routing

To display the configuration, use the vrouter-show command:

CLI (network-admin@spine1)>vrouter-show

switch...cluster-active-active-routing...

------   ---------------------   

spine1   enable

Using an L3 Network to Establish the Netvisor OS Fabric

The Netvisor OS fabric can be established over the management network or an in-band network over Layer 2. Fabric over a Layer 3 network uses an existing or new Layer 3 network in order to establish the Netvisor OS fabric. Currently this feature is only supported over a BGP network. Before you can configure this feature on your network, make sure that BGP routing is configured on your switches.