Configuring Packet Load Balancing over One to Many Links
When VirtualWire is deployed as legacy packet broker, moving packets from production to an analyzer tool, it requires load balancing feature because you can monitor 10Gb links with 1Gb tools.
Netvisor One load balances the traffic by distributing the traffic load to different tool ports or appliances in order to scale the monitoring. This also provides redundancy in the monitoring technology.
When a member port goes down, traffic on the port is switched to remaining member ports and evenly distributed.
To configure load balancing, use the following steps:
1) First configure a trunk on the desired ports. In this case, ports 15 and 16 are configured as a trunk:
CLI (network-admin@Leaf1) > trunk-create name lb_trunk ports 15,16
Created trunk lb_trunk, id 128
2) Create the port association on the switch:
CLI (network-admin@Leaf1) > port-association-create name pa1 master-ports 1 slave-ports 128 virtual-wire bidir
3) Display the configuration:
CLI (network-admin@Leaf1) > port-association-show
switch name master-ports slave-ports policy virtual-wire bidir
------- ---- ------------ ----------- ----------- ------------ -----
leaf1 pa1 1 128 all-masters true true
CLI (network-admin@Leaf1) > port-show port 1,16
switch port vnet hostname status config trunk
------- ---- ---- -------- ------ --------- --------
leaf1 1 40g,jumbo
leaf1 16 trunk 10g,jumbo lb_trunk
CLI (network-admin@Leaf1) > vflow-show layout vertical
name: Internal-Keepalive
scope: local
in-port:
ether-type: ipv4
dst-ip: 239.4.9.7
proto: udp
flow-class: control
precedence: 14
action: to-cpu
action-to-ports-value:
enable: enable
table-name: L1-Virtual-Wire-1-0
name: VIRT_WIRE_MAS_SLV
scope: local
in-port: 1
ether-type:
dst-ip:
proto:
flow-class:
precedence: 14
action: to-port
action-to-ports-value: 128
enable: enable
table-name: L1-Virtual-Wire-1-0