diff options
Diffstat (limited to 'docs/_locale/de_DE/LC_MESSAGES/configexamples/inter-vrf-routing-vrf-lite.po')
| -rw-r--r-- | docs/_locale/de_DE/LC_MESSAGES/configexamples/inter-vrf-routing-vrf-lite.po | 575 |
1 files changed, 0 insertions, 575 deletions
diff --git a/docs/_locale/de_DE/LC_MESSAGES/configexamples/inter-vrf-routing-vrf-lite.po b/docs/_locale/de_DE/LC_MESSAGES/configexamples/inter-vrf-routing-vrf-lite.po deleted file mode 100644 index dc6efef0..00000000 --- a/docs/_locale/de_DE/LC_MESSAGES/configexamples/inter-vrf-routing-vrf-lite.po +++ /dev/null @@ -1,575 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, VyOS maintainers and contributors -# This file is distributed under the same license as the VyOS package. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: VyOS 1.4\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-10-21 12:01+0200\n" -"PO-Revision-Date: 2022-10-21 10:05+0000\n" -"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:3 -#: eb41ae1b116f44aca5187f22bd6e3c38 -msgid "Inter-VRF Routing over VRF Lite" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:5 -#: f0616081b9784167ab9c07a7350cb12c -msgid "" -"**Virtual Routing and Forwarding** is a technology that allow multiple " -"instance of a routing table to exist within a single device. One of the key " -"aspect of **VRFs** is that do not share the same routes or interfaces, " -"therefore packets are forwarded between interfaces that belong to the same " -"VRF only." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:10 -#: ea59f5e8a5e6486d80e4e4d65d0de34c -msgid "" -"Any information related to a VRF is not exchanged between devices -or in the" -" same device- by default, this is a technique called **VRF-Lite**." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:13 -#: ac294973fcec422ea2769beb2f586a5d -msgid "" -"Keep networks isolated is -in general- a good principle, but there are cases" -" where you might need that some network can access other in a different VRF." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:16 -#: 8b47e55fd64d400b96bd14a41ba2f2cd -msgid "" -"The scope of this document is to cover such cases in a dynamic way without " -"the use of MPLS-LDP." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:19 -#: 0a4d0fe3ed8948c685128f24ac43b5e2 -msgid "" -"General information about L3VPNs can be found in the " -":ref:`configuration/vrf/index:L3VPN VRFs` chapter." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:23 -#: 4c8919e0683e407e853338762e005b73 -msgid "Overview" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:25 -#: 4649bebe3b9c452a983b440677eef8ef -msgid "Let’s say we have a requirement to have multiple networks." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:27 -#: 4adf12c76e3042d1aa0615aa93f6c028 -msgid "LAN 1" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:28 -#: 2bb42d1b9104415db47557052928d2e8 -msgid "LAN 2" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:29 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:91 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:106 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:727 -#: 9e0ca4a0df5f4fb88e8aeb21241714a2 7eecdf4e5fe844e39ce8c9bd6e275a30 -#: e12f1fbf318148dda9a8468e462ec0f0 9da4873cd37c45d2a1e9e6c8cce272f7 -msgid "Management" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:30 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:108 -#: c81a9b48a8c045e2aed48642d26b13ab 091224a1afed4eac89b75bb783b866c4 -msgid "Internet" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:32 -#: 99888ffd849e412cbad21c08b326160e -msgid "" -"Both LANs have to be able to route between each other, both will have " -"managed devices through a dedicated management network and both will need " -"Internet access yet the LAN2 will need access to some set of outside " -"networks, not all. The management network will need access to both LANs but " -"cannot have access to/from the outside." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:38 -#: 0f23fd96749846889ded22c066ef1961 -msgid "" -"This scenario could be a nightmare applying regular routing and might need " -"filtering in multiple interfaces." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:41 -#: 6ab38930088d40d7828f23898bd381d1 -msgid "" -"A simple solution could be using different routing tables, or VRFs for all " -"the networks so we can keep the routing restrictions. But for us to route " -"between the different VRFs we would need a cable or a logical connection " -"between each other:" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:46 -#: 5a813032fce9458eb29d0498989614da -msgid "One cable/logical connection between LAN1 and LAN2" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:47 -#: ef9bfefcf4104ea0b95f1a3b7a9ee796 -msgid "One cable/logical connection between LAN1 and Internet" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:48 -#: 6462901ab71c4c9ba3bdd5ed60994278 -msgid "One cable/logical connection between LAN2 and Internet" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:49 -#: d3f6c4a564e741508c3095bd738b4e0b -msgid "One cable/logical connection between LAN1 and Management" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:50 -#: 50efd8066bcb420fbf4f3e43a4b2ac4a -msgid "One cable/logical connection between LAN2 and Management" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:52 -#: 12a6f2d5993647ca884f54b7ea65424d -msgid "As we can see this is unpractical." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:54 -#: 86964e2fdcfe42b1acef7ebe5f6be8e7 -msgid "" -"To address this scenario we will use to our advantage an extension of the " -"BGP routing protocol that will help us in the “Export” between VRFs without " -"the need for MPLS." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:58 -#: 67c99502bfe344c18b2772fead0bfdef -msgid "" -"MP-BGP or MultiProtocol BGP introduces two main concepts to solve this " -"limitation: - Route Distinguisher (RD): Is used to distinguish between " -"different VRFs –called VPNs- inside the BGP Process. The RD is appended to " -"each IPv4 Network that is advertised into BGP for that VPN making it a " -"unique VPNv4 route. - Route Target (RT): This is an extended BGP community " -"append to the VPNv4 route in the Import/Export process. When a route passes " -"from the VRF routing table into the BGP process it will add the configured " -"export extended community(ies) for that VPN. When that route needs to go " -"from BGP into the VRF routing table will only pass if that given VPN import " -"policy matches any of the appended community(ies) into that prefix." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:72 -#: de34231c61084297b36ddb578477b67d -msgid "Topology" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rstNone -#: cdc1520b038842a68babb2a9a2525fc4 -msgid "Network Topology Diagram" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:82 -#: 16f28c31e1f143c5986ab85cc840b32b -msgid "IP Schema" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:85 -#: 40ae6d91025b43babf6a28156ac7500b -msgid "Device-A" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:85 -#: c35074ba59f949b8a2a46f3811869080 -msgid "Device-B" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:85 -#: bc3f51095ca3484f863d2762794aa0f8 -msgid "IPv4 Network" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:85 -#: 72b11e54e57a4b439f2b75faa92ce102 -msgid "IPv6 Network" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:87 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:89 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:91 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:93 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:616 -#: 3f41e5bfa21947be87ec7081d7ee8ba2 b54901e4a8b249f89f67b364fa24663d -#: 19cc658588fd4ebf9502ea26ea498d7a 02ad5c6d77bf461396340263ef2d3420 -#: 900ff739e58e4f79bf99a1f561c405b4 -msgid "Core" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:87 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:102 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:701 -#: 56574650a4194ff79d5645140cf03d6b f25b32ec296c44b7aa3458a0f9b44760 -#: 9b5243427ba34f7cbf9939103226d9b1 -msgid "LAN1" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:87 -#: 2d1e1dc89c1f40318ed9748de6273f9f -msgid "10.1.1.0/30" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:87 -#: cbe4082191094f4bab8916aef6f9a5c0 -msgid "2001:db8::/127" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:89 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:104 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:713 -#: 65ddfdbbfa3b4c349173b73a2fa3356f b7f31fe8dd854681bb11900e87d1f179 -#: 5734149a4be547639059a2cdd24050e8 -msgid "LAN2" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:89 -#: b7c3c79b8c4842cca5336eb1b94dff85 -msgid "172.16.2.0/30" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:89 -#: f4007f87de1f4bada7ce0e55633d427b -msgid "2001:db8::2/127" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:91 -#: 1daaf01c8340423d93f96757bf6041ed -msgid "192.168.3.0/30" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:91 -#: 1b4913f318a04b02a17c852a5f28e312 -msgid "2001:db8::4/127" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:93 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:739 -#: f9c8ebe5ce5f46d5ae5f6a311ec9ce1c 1a78a58c2a3d41d8aa2f998dc8bfa291 -msgid "ISP" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:93 -#: e5138de5b6844fb4bc208ad2d66aec94 -msgid "10.2.2.0/30" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:93 -#: c048ed3059334c8c964fc7c9595d8062 -msgid "2001:db8::6/127" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:97 -#: a4c3a66971e240858d9343a409da32e9 -msgid "RD & RT Schema" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:100 -#: 129b297c60754ac498ec18058a07dcee -msgid "VRF" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:100 -#: 935cb9b1a2e0495fb580d674e4a9e3d0 -msgid "RD" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:100 -#: edb2eabdd1284a7dbe82d4544b8616b6 -msgid "RT" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:102 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:102 -#: 79ca3a7d0fa14923bfca6af65dff61e9 b49d97869905413e8df40c8e1abb1b3b -msgid "64496:1" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:104 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:104 -#: 81afc720df0d48a0b9df047a6543aeea 0e1ffef8c627472daa211f00b436b220 -msgid "64496:2" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:106 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:106 -#: 471376839df44e6a98853fbe83f8c302 3b9f6979c3374fb7a754201c21604f75 -msgid "64496:50" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:108 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:108 -#: 901fb99798914a7ba27ae0b4e7e2af72 c22fb6bacd9f4f178ebc8d64e28967fe -msgid "64496:100" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:113 -#: 37b3b1695a5142b8b4eb0f4eda8e9392 -msgid "Configurations" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:115 -#: 8fcddacdabb347938fdddd5df33ef082 -msgid "" -"We use a static route configuration in between the Core and each LAN and " -"Management router, and BGP between the Core router and the ISP router but " -"any dynamic routing protocol can be used." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:120 -#: d0ba532920c146b58e8609eeb52a9351 -msgid "Remote Networks" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:122 -#: 2370f525c998496dae1e93ecb14ef1d2 -msgid "" -"The following template configuration can be used in each remote router based" -" in our topology." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:134 -#: a3a69aba21694a54945c258e54511f4c -msgid "Core Router" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:137 -#: 1d698f00b16644879ae215618bc43467 -msgid "Step 1: VRF and Configurations to remote networks" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:139 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:231 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:290 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:774 -#: e37f8f84308849c193ca0456b07b9e12 7a85dc42dbe8467c93d1259f5c8a2831 -#: 00c29f4758af4aa6bdb6ae7100df73c1 2b99ef8b24734d5ca80591ca6fdd5b75 -msgid "Configuration" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:143 -#: 9d83ffd71ed3407584a88fe68993f486 -msgid "" -"Set the VRF name and Table ID, set interface address and bind it to the VRF." -" Last add the static route to the remote network." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:160 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:248 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:320 -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:829 -#: 3aba84af46df47cc9fd2ae84f9b503da da748005d3874b4480b7bbd9d591e27a -#: 1ecb9ec20cdc4c2893ee6fca2ee51358 a280fb687cdc40178d509af90951189b -msgid "Verification" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:164 -#: 37ce0e67288f45fe9ef9c08369138fb2 -msgid "" -"Checking the routing table of the VRF should reveal both static and " -"connected entries active. A PING test between the Core and remote router is " -"a way to validate connectivity within the VRF." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:228 -#: c75588c0d4934b26bc2191593d95078c -msgid "Step 2: BGP Configuration for VRF-Lite" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:235 -#: 1b8331d7180b4c1fa784335dc8a73fb7 -msgid "" -"Setting BGP global local-as as well inside the VRF. Redistribute static " -"routes to inject configured networks into the BGP process but still inside " -"the VRF." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:252 -#: 23fba5b0b23849658c56bfe042cba29a -msgid "" -"Check the BGP VRF table and verify if the static routes are injected showing" -" the correct next-hop information." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:287 -#: 43ff822c83a548f1bfc03261deb495b8 -msgid "Step 3: VPN Configuration" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:293 -#: c4ae33aea35c4a3f9deaff43b955090e -msgid "" -"Within the VRF we set the Route-Distinguisher (RD) and Route-Targets (RT), " -"then we enable the export/import VPN." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:312 -#: 4186090c0eb4432aa7763a11232d7c73 -msgid "" -"A key point to understand is that if we need two VRFs to communicate between" -" each other EXPORT rt from VRF1 has to be in the IMPORT rt list from VRF2. " -"But this is only in ONE direction, to complete the communication the EXPORT " -"rt from VRF2 has to be in the IMPORT rt list from VRF1." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:317 -#: dbff84d09cf543e78ef3bedf22f4cce0 -msgid "" -"There are some cases where this is not needed -for example, in some DDoS " -"appliance- but most inter-vrf routing designs use the above configurations." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:324 -#: 20333d5d9494441a974b2c7b031c3620 -msgid "" -"After configured all the VRFs involved in this topology we take a deeper " -"look at both BGP and Routing table for the VRF LAN1" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:417 -#: 50932524836549ed803143fff7ca704a -msgid "" -"As we can see in the BGP table any imported route has been injected with a " -"\"@\" followed by the VPN id; In the routing table of the VRF, if the route " -"was installed, we can see -between round brackets- the exported VRF table." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:422 -#: 040c2e2ba85b4694b54fc037d8e22e62 -msgid "Step 4: End to End verification" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:425 -#: 56ca70dcbe824d18ad0daeed1283e2cb -msgid "Now we perform some end-to-end testing" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:427 -#: 5f0852ffedff48d0b4b2996888183b7a -msgid "From Management to LAN1/LAN2" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:469 -#: 6ce8210eb4d24cceb40d4b8940231d99 -msgid "From Management to Outside (fails as intended)" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:520 -#: c1d07bc3b8de4706bd224c06ee17dbbe -msgid "LAN1 to Outside" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:571 -#: 3db16afd744a4f0bb44dfcf01987a098 -msgid "" -"we are using \"source-address\" option cause we are not redistributing " -"connected interfaces into BGP on the Core router hence there is no comeback " -"route and ping will fail." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:575 -#: cfb5c05281f242db8863602ddb0693f9 -msgid "LAN1 to LAN2" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:601 -#: bf275914b4ec4567b5fecc55c805c298 -msgid "Conclusions" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:603 -#: 066850a20fcf43a8a9f17c58e2038810 -msgid "" -"Inter-VRF routing is a well-known solution to address complex routing " -"scenarios that enable -in a dynamic way- to leak routes between VRFs. Is " -"recommended to take special consideration while designing route-targets and " -"its application as it can minimize future interventions while creating a new" -" VRF will automatically take the desired effect in its propagation." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:611 -#: 8683a9d3f2104a9db49b0a0907555f32 -msgid "Appendix-A" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:614 -#: 5abc7d4aebac4e02af6886aac14cf1ce -msgid "Full configuration from all devices" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:764 -#: 41e37392648b4e2da99de7267631749e -msgid "Appendix-B" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:767 -#: 8f882d02b8fa437f87c5f3e7520c95c5 -msgid "Route-Filtering" -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:770 -#: bf9c4776ac3e43c180cf5abb70bfa7aa -msgid "" -"When importing routes using MP-BGP it is possible to filter a subset of them" -" before are injected in the BGP table. One of the most common case is to use" -" a route-map with an prefix-list." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:778 -#: 68fcdc98c6d246099510635b49afe34e -msgid "We create a prefix-list first and add all the routes we need to." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:803 -#: e7a748ac55dc4c02b90fea5c37b64b9b -msgid "" -"Then add a route-map and reference to above prefix. Consider that the " -"actions taken inside the prefix will MATCH the routes that will be affected " -"by the actions inside the rules of the route-map." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:815 -#: 1bb8831212be41398444370636f0f441 -msgid "" -"We are using a \"white list\" approach by allowing only what is necessary. " -"In case that need to implement a \"black list\" approach then you will need " -"to change the action in the route-map for a deny BUT you need to add a rule " -"that permits the rest due to the implicit deny in the route-map." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:820 -#: 384686127eda49c39439e379043fd224 -msgid "" -"Then we need to attach the policy to the BGP process. This needs to be under" -" the import statement in the vrf we need to filter." -msgstr "" - -#: ../../configexamples/inter-vrf-routing-vrf-lite.rst:853 -#: e9beeb420b0e42cf8fe71412b1255dc0 -msgid "" -"As we can see even if both VRF LAN1 and LAN2 has the same import RTs we are " -"able to select which routes are effectively imported and installed." -msgstr "" |