O 33.3.3.3/32 via 133.3.3.3 110/0
00:00:11
C 133.3.3.0/24 Direct, Te 1/13 0/0 22:39:61
Dell# show ip route vrf VRF-Shared
O 11.1.1.1/32 via VRF-Red:111.1.1.1 110/0 00:00:10
C 111.1.1.0/24 Direct, VRF-Red:Te 1/11 0/0 22:39:59
O 22.2.2.2/32 via VRF-Blue:122.2.2.2 110/0 00:00:11
C 122.2.2.0/24 Direct, VRF-Blue:Te 1/22 0/0 22:39:61
O 44.4.4.4/32 via 144.4.4.4 110/0
00:00:11
C 144.4.4.0/24 Direct, Te 1/4 0/0 00:32:36
Important Points to Remember
• If the target VRF conatins the same prefix as either the sourced or Leaked route from some other VRF,
then route Leaking for that particular prefix fails and the following error-log is thrown.
SYSLOG (“Duplicate prefix found %s in the target VRF %d”, address,
import_vrf_id) with
The type/level is EVT_LOGWARNING.
• The source routes always take precedence over leaked routes. The leaked routes are deleted as soon
as routes are locally learnt by the VRF using other means.
• For recovery, you must take appropriate action either by deleting the unwanted prefixes or issuing
clear command or both.
• In the target VRF, you cannot leak routes that are imported through the route leaking feature.
• The leaked route points to the next-hop of the source routes. You cannot do any modifications to the
next-hop of the leaked route in the destination VRF.
• IPv6 link local routes will never be leaked from one VRF to another.
Configuring Route Leaking with Filtering
When you initalize route leaking from one VRF to another, all the routes are exposed to the target VRF. If
the size of the source VRF's RTM is considerablly large, an import operation results in the duplication of
the target VRF's RTM with the source RTM entries. To mitigate this issue, you can use route-maps to filter
the routes that are exported and imported into the route targets based on certain matching criteria.
These match criteria include, prefix matches and portocol matches.
You can use the
match source-protocol
or
match ip-address
commands to specify matching
criteria for importing or exporting routes between VRFs.
NOTE: You must use the match source-protocol or match ip-address commands in conjunction
with the route-map command to be able to define the match criteria for route leaking.
Consider a scenario where you have created two VRF tables VRF-red and VRF-blue. VRF-red exports
routes with the export_ospfbgp_protocol route-map to VRF-blue. VRF-blue imports these routes into its
RTM.
For leaking these routes from VRF-red to VRF-blue, you can use the ip route-export route-map
command on VRF-red (source VRF, that is exporting the routes); you must also specify a match criteria
for these routes using the match source-protocol command. When you leak these routes into VRF-blue,
Virtual Routing and Forwarding (VRF)
1113
Содержание S4820T
Страница 1: ...Dell Configuration Guide for the S4820T System 9 8 0 0 ...
Страница 282: ...Dell 282 Control Plane Policing CoPP ...
Страница 569: ...Figure 62 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 569 ...
Страница 572: ...Figure 64 Inspecting a LAG Port on BRAVO Using the show interface Command 572 Link Aggregation Control Protocol LACP ...
Страница 573: ...Figure 65 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 573 ...
Страница 617: ...mac address table static multicast mac address vlan vlan id output range interface Microsoft Network Load Balancing 617 ...
Страница 622: ...Figure 81 Configuring Interfaces for MSDP 622 Multicast Source Discovery Protocol MSDP ...
Страница 623: ...Figure 82 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 623 ...
Страница 624: ...Figure 83 Configuring PIM in Multiple Routing Domains 624 Multicast Source Discovery Protocol MSDP ...
Страница 629: ...Figure 86 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 629 ...
Страница 630: ...Figure 87 MSDP Default Peer Scenario 3 630 Multicast Source Discovery Protocol MSDP ...
Страница 751: ...10 11 5 2 00 00 05 00 02 04 Member Ports Te 1 2 1 PIM Source Specific Mode PIM SSM 751 ...
Страница 905: ...Figure 112 Single and Double Tag First byte TPID Match Service Provider Bridging 905 ...
Страница 979: ...6 Member not present 7 Member not present Stacking 979 ...
Страница 981: ...storm control Storm Control 981 ...
Страница 999: ... Te 1 1 0 INCON Root Rootguard Te 1 2 0 LIS Loopguard Te 1 3 0 EDS Shut Bpduguard Spanning Tree Protocol STP 999 ...
Страница 1103: ...Figure 134 Setup OSPF and Static Routes Virtual Routing and Forwarding VRF 1103 ...