217
Targets.
b. Exchange the VPN related route information per VR with PE device using Extended communities
2.
The internal Routers in the Enterprise networks to provide isolation of different departments/offices at layer-
3 or routing domain.
This scenario does not mandate that the BGP protocol be running on the device. It can still be run in this
scenario to achieve dynamic route leaking only. The IGP protocol (OSPF or RIP) running in the VR instance
communicates route information with corresponding peers in the same VR on other CE devices or internal
Routers.
Figure 7-10: VRF Scenarios
The default global routing table is also referred to as VR 0.
In the following example, subnetworks 10.10.10.0/24 and 11.11.11.0/24 belong to the virtual routing domain
“HR Dept” and subnetworks 20.20.20.0/24 and 22.22.22.0/24 belong to virtual routing domain “Finance
Dept”. Hence, the hosts in networks 10.10.10.0/24 can communicate only with other network 11.11.11.0/24
via the router and the hosts in networks 20.20.20.0/24 can communicate only with other network
22.22.22.0/24 via the router.
If there is a shared service printer @30.30.30.30 in the default global routing domain “Shared Services”, we
would want the HR and Finance domains to have access to it. Therefore, we statically leak a 30.30.30.0/24
route from global routing table to VR 10 and VR 20. At the same time, we statically leak the routes
10.10.10.0/24 and 11.11.11.0/24 from VR 10 to global table (the same applies to VR 20).
Figure 7-11: VRF routing with shared services
The route tables in both the VRs and the global domain look like the following:
Summary of Contents for QuantaMesh QNOS5
Page 1: ...QuantaMesh Ethernet Switch Configuration Guide QNOS5 NOS Platform ...
Page 209: ...209 Table 7 8 IPv6 Neighbor Discovery Settings ...
Page 226: ...226 Table 8 2 L3 Multicast Defaults ...
Page 254: ...254 Appendix A Term and Acronyms Table 9 5 Terms and Acronyms ...
