L3VRF¶

It is possible to move an interface to an existing L3VRF domain. This operation enables to isolate incoming traffic coming from that interface in a separate routing domain.

To bind a physical interface eth0 to an L3VRF domain in vrf main, do the following:

[~#]
vsr running config# / vrf main l3vrf l3vrf1 table-id 101
vsr running config# / vrf main l3vrf l3vrf1 interface physical eth1 port pci-b0s4

To move an interface to an other L3VRF within the same VRF, do:

[~#]
vsr running config# del / vrf main l3vrf l3vrf1 interface physical eth1
vsr running config# / vrf main l3vrf l3vrf2 table-id 102
vsr running config# / vrf main l3vrf l3vrf2 interface physical eth1 port pci-b0s4

It is also possible to unbind an interface from an L3VRF by issuing the command below. In that way, eth0 is moved to the default L3VRF domain.

[~#]
vsr running config# del / vrf main l3vrf l3vrf2 interface physical eth1
vsr running config# / vrf main interface physical eth1 port pci-b0s4

All configurable interfaces are eligible to be bound to an L3VRF, provided they actually route packets. For instance, interfaces attached to a bridge or a a LAG interface cannot be bound to an L3VRF.