Direct Route Leaking Between Virtual Routers

Version 32.4 adds support for leaking direct routes of specified VLAN(s) to a different Virtual Router (VR). Adjacent (directly connected) hosts are also reachable in the specified VR.

Note

This feature is an additional method for achieving Inter-VR routing without an external router. You can also allow a static route's gateway to be in a different VR by entering the configure iproute add command and specifying vlan egress_vlan, or redistribute routes from one OSPF instance to another OSPF instance in a different VR by entering the enable ospf export {vr} command.

Leaked direct routes are created with origin direct-inter-vr in the leak-to-VR. These routes have a lower route priority than direct routes and a higher route priority than any other route type.

The route priority of direct-inter-vr can be modified using the iproute priority command. These routes can be redistributed to the OSPF protocol in the leak-to-VR like any other routes in the VR. OSPF‘s route redistribution command is also extended as part of this feature and includes the direct-inter-vr route type.

Note

To ping a directly attached host from the switch command line successfully, the ping command must specify the correct VR name (or use the correct command line VR context) containing the VLAN with that subnet. If another VR name or VR context is used, the ping will not be successful.