Refer to the exhibit. An engineer is comparing these RPL and route map configurations. Which two conclusions will the engineer reach? (Choose two.)
Answer(s): C,D
RPL is applying local preference 50 and community (2:666) for prefix 172.22.0.0/16, but the route map is applying only local preference 50 for the same prefix.The RPL configuration applies both local preference 50 and community (2:666, no-advertise) for the prefix 172.22.0.0/16. The route map, however, matches the same prefix using the prefix list LOW_LP_PREFIXES but only applies local preference 50. There is no community set in the route map.RPL is applying local preference 100 and community (2:100) for multiple prefixes, but the route map is applying default local preference for multiple prefixes.In the RPL configuration, prefixes other than 172.22.0.0/16 (i.e., in the else block) are assigned local preference 100 and community (2:100). The route map does not explicitly configure a local preference for unmatched prefixes, so the default BGP local preference (100) is applied. The key difference is that the RPL also sets a community (2:100) for the other prefixes, which is not applied by the route map.
What is the purpose of the confederation identifier in a BGP confederation?
Answer(s): D
In BGP confederations, the confederation identifier represents the external AS number for the entire confederation. The BGP confederation splits a single large autonomous system (AS) into smaller, manageable sub-ASes. These sub-ASes use private AS numbers internally but appear as a single unified AS to external BGP peers. The confederation identifier ensures that external BGP peers see the confederation as one cohesive AS rather than multiple smaller ASes.
SIMULATIONGuidelinesThis is a lab item in which tasks will be performed on virtual devices. Refer to the Tasks tab to view the tasks for this lab item. Refer to the Topology tab to access the device console(s) and perform the tasks. Console access is available for all required devices by clicking the device icon or using the tab(s) above the console window. All necessary preconfigurations have been applied. Do not change the enable password or hostname for any device. Save your configurations to NVRAM before moving to the next item. Click Next at the bottom of the screen to submit this lab and move to the next question. When Next is clicked, the lab doses and cannot be reopened.Topology: Tasks:Troubleshoot and configure BGP according to the topology to achieve these goals:1. R1 and R3 establishes IBGP connectivity using Loopback addresses. The updates should come from Loopback0.2. R3 should be able to ping loopback0 interface of R2. These changes must be accomplished through BGP.3. R1 advertises only the summary route of 172.16.100.0/22 to R2 and R3.
Answer(s): A
Step 1: R1 and R3 IBGP Connectivity Using Loopback0To establish IBGP between R1 and R3 using their Loopback0 interfaces and ensure updates originate from Loopback0, configure the following:On R1:router bgp 100 neighbor 10.3.3.3 remote-as 100 neighbor 10.3.3.3 update-source Loopback0On R3:router bgp 100 neighbor 10.1.1.1 remote-as 100 neighbor 10.1.1.1 update-source Loopback0neighbor update-source Loopback0 ensures that the BGP updates are sourced from Loopback0.Verify the BGP peering: show ip bgp summaryStep 2: R3 Can Ping R2 Loopback0 (10.2.2.2/32)To allow R3 to reach R2’s Loopback0, configure R1 to redistribute the route from EBGP to IBGP. Ensure next-hop resolution works correctly:On R1:router bgp 100 neighbor 10.3.3.3 next-hop-selfnext-hop-self: This changes the next-hop IP to R1's IP when advertising routes to R3. This ensures R3 can resolve the next-hop for R2's loopback.Step 3: R1 Advertises Only Summary Route (172.16.100.0/22)To advertise only the summary route 172.16.100.0/22 to both R2 and R3:On R1:router bgp 100 network 172.16.100.0 mask 255.255.252.0 aggregate-address 172.16.100.0 255.255.252.0 summary-onlyaggregate-address 172.16.100.0 255.255.252.0 summary-only advertises the summary route and suppresses more specific routes.Verification Commands:-Verify IBGP Peering: show ip bgp summary-Verify BGP Advertisements: show ip bgp-Verify R3 Reachability to R2’s Loopback: ping 10.2.2.2 source Loopback0-Verify the Summary Route Advertisement on R2 and R3: show ip bgp-IBGP Peering: Use Loopback0 and configure update-source.-Next-Hop Resolution: next-hop-self ensures reachability for EBGP routes.-Summary Route: Use aggregate-address with summary-only to advertise a summary route.
Which requirement must be met while using parameter with conditional matching in routing policy definition?
Answer(s): B
In routing policy definitions, parameters are used for conditional matching and must start with the $ symbol. The $ symbol designates a parameter variable that can be used in the policy logic to dynamically match conditions such as prefixes, communities, or attributes.
How does conditional matching operate with RPL?
RPL (Routing Policy Language) operates by using conditional matching to evaluate routes based on specific criteria. The criteria can include attributes like prefixes, communities, route tags, local preferences, or AS paths. Once the match condition is evaluated, an action is taken depending on whether the criteria match or differ. Actions can include setting attributes, accepting, rejecting, or modifying routes.
Post your Comments and Discuss Cisco 300-510 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the 300-510 content, but please register or login to continue.