Inter-VR Routing for IPv4 Unicast Static Routes:
- In EXOS 15.6 there is a new feature that allows static routing between two virtual routers.
- Allows for routing of IPv4 unicast packets between Virtual Routers via static routes. This is referred to as Inter-VR Routing. The next hop gateway of a static route may reside in a Virtual LAN belonging to a different Virtual Router from the Virtual Router of the static route.When inter-vr routing is configured the gateway address should be different from VLAN IP of the switch and it should be reachable (ARP resolved) from the switch.
- Inter-VR routing is supported for hardware forwarding and software forwarding of IPv4 unicast packets, including Equal-Cost Multi-Path (ECMP).
Example Command: "configure iproute add <network> <next hop> vlan <egress_vlan> vr <ingress_vr_name>"
Note that the “vlan <egress_vlan>”, specifying the outgoing VLAN of the next hop gateway, refers to a VLAN belonging to a different VR because Inter-VR routing is desired. The “vr <ingress_vr_name>” of the static route command refers to which VR’s route table the route is added.
Consider the following Network Topology:
In the topology above VLAN v1 belongs to VR vr1, and VLAN v2 belongs to VR vr2. The final two commands add Inter-VR routes between VR vr1 and VR vr2. The resulting behavior is that IPv4 unicast packets with a source IP address in subnet 22.214.171.124/8 in VR vr1, and a destination IP address in subnet 126.96.36.199/8, are forwarded to gateway 188.8.131.52 belonging to VLAN v2 in VR vr2. Reverse packets are forwarded to gateway 10.1.1.2 belonging to VLAN v1 in VR vr1.
create vr "vr1"
create vr "vr2"
create vlan "v1" vr vr1
create vlan "v2" vr vr2
configure vlan v1 tag 10
configure vlan v2 tag 20
configure vlan v1 add ports 1 tagged
configure vlan v2 add ports 2 tagged
configure vlan v1 ipaddress 10.1.1.1/8
configure vlan v2 ipaddress 184.108.40.206/8
enable ipforwarding vlan v1
enable ipforwarding vlan v2
configure iproute add 220.127.116.11/8 18.104.22.168 vlan v2 vr vr1
configure iproute add 22.214.171.124/8 10.1.1.2 vlan v1 vr vr2
The example above is for packets routed through a gateway to a remote subnet. But Inter-VR routing can also be accomplished to/from a host adjacent to the switch, i.e. hosts connected to locally attached networks, by adding a /32 host route. In the example network above, to have packets from VR1 route to a host/server in VR2 directly on the 126.96.36.199/8 subnet, such as 188.8.131.52, the following CLI command can be used by specifying 184.108.40.206/32:
configure iproute add 220.127.116.11/32 18.104.22.168 vlan v2 vr vr1