
Refer to the exhibit. An engineer has configured R1 as EIGRP stub router. After the configuration, router R3 failed to reach to R2 loopback address.
Which action advertises R2 loopback back into the R3 routing table?
Refer to the exhibit. An engineer has configured R1 as EIGRP stub router. After the configuration, router R3 failed to reach to R2 loopback address.
Which action advertises R2 loopback back into the R3 routing table?
The correct action to advertise R2's loopback back into the R3 routing table involves adding a static route for R2's loopback address in R1 and redistributing it to advertise to R3. This process ensures that R1, configured as an EIGRP stub, contains the necessary route information, which it can then pass on to R3. The commands required for this configuration include 'redistribute static' and 'eigrp stub static' to facilitate proper route advertisement in a stub scenario.
Answer is B - as I lab it. I was thinking it was another answer but the lab pointed me to the right direction. ip access-list standard R2LO permit 2.2.2.2 ! route-map R2LO_LEAK permit 10 match ip address R2LO ! router eigrp 1 network 1.1.1.1 0.0.0.0 network 192.168.12.0 network 192.168.13.0 eigrp stub connected summary leak-map R2LO_LEAK
For me "A" is correct. I labbed it in CML. "B" is incorrect, because there is no such distribute-list (as others pointed out). Pls, see some good explanations here: https://community.cisco.com/t5/routing/eigrp-eigrp-stub-connected-static-summary/td-p/2575321 https://learningnetwork.cisco.com/s/question/0D53i00000Kso40CAB/clarification-needed-on-eigrp-stub-static-option https://notes.networklessons.com/redistribute-static-route-into-eigrp-stub-router
As previously mentioned (for example by HungarianDish) there is no such possibilty eigrp leak-map with distribute list. I also labbed the configuration, and I agree with HungarianDish, that answer is "A". Even the wording is met.
Option B is correct: https://networklessons.com/cisco/ccie-routing-switching-written/eigrp-stub-leak-map
The example you supplied matches the question. So i agree it should be B. Also strange that we get this question on CCNP as it seems out of scope of the exam. By the way, love the example, so simple!
In the example you have supplied shows if we want to use leak-map we have the option: eigrp stub leak-map <leak map name> There is no such option as distribute-list regarding leak-map, but redistribute command works as HungarianDish labbed: Correct answer is A
That's not true, you do NOT use a distribute list for create a leak-map, in fact if you look the configuration there is configured a route-map that is matching the 3.3.3.3/32 prefix and then is going to apply the leak map in the eigrp stub command using also the leak map the distribute list in NOT used
In the example you have supplied shows if we want to use leak-map we have the option: eigrp stub leak-map <leak map name> There is no such option as distribute-list regarding leak-map, but redistribute command works as HungarianDish labbed: Correct answer is A
That's not true, you do NOT use a distribute list for create a leak-map, in fact if you look the configuration there is configured a route-map that is matching the 3.3.3.3/32 prefix and then is going to apply the leak map in the eigrp stub command using also the leak map the distribute list in NOT used
never heard about leak-map, thanks!
I agree the correct answer is B. C would work if the config was on R1 and not R3.
A https://community.cisco.com/t5/routing/eigrp-eigrp-stub-connected-static-summary/td-p/2575321
B says applied with a distribute-list and that is incorrect, isn't it?
The correct answer is: B
hi, R1 is stub, it advertises only summury and connected routes. Even if we do the purpose in answer A, R1 cant advetises it because it is an redistributed route. it has to be stub redistribute
We have to assume it is stub redistribute.
We have to assume it is stub redistribute.
redistribution of staic routes not work with stub . The only possible is B
B IS CORRECT
by default eigrp stub doesn't distribute static for that reason exists eigrp stub static to allow it
A https://learningnetwork.cisco.com/s/article/eigrp-stub-routing
Its B Redistributing static routes into eigrp isnt enough. If you don't have the "eigrp stub static" configured, it will not advertise the redistributed route. Ref: https://learningnetwork.cisco.com/s/article/eigrp-stub-routing
Answer is C. eigrp stub leak-map MY-ROUTE-MAP make exeption for stub feature. router eigrp 1 eigrp stub leak-map MY-ROUTE-MAP route-map MY-ROUTE-MAP permit 10 match ip address MY-ACL ip access-list standard MY-ACL permit x.x.x.x wildcard (loopback network)
Use a leak map on R1 that matches the required prefix and apply it with the EIGRP stub feature.
I lab it answer B is correct. distribute-list works foradvise 2.2.2.2. It look like distribute-list is over eigrp stub feature. If C is configure in R1, Also correct.
Yea we know that but there is no answer like that so we have to choose something from cisco fuc*ed up answers. So answer is B
My config on R1: router eigrp 1 network 1.1.1.1 0.0.0.0 network 192.168.12.0 network 192.168.13.0 redistribute static eigrp stub connected static summary ip route 2.2.2.2 255.255.255.255 192.168.12.2 You need the static route on R1 to get the prefix 2.0.0.0/32 back into the eigrp table. Plus, you need to push out the static route with these two commands on R1: redistribute static eigrp stub static
*typo: prefix 2.2.2.2/32
After applying the config, that is what you see on R3: r3#sh ip route eigrp | b Gateway Gateway of last resort is not set 1.0.0.0/32 is subnetted, 1 subnets D 1.1.1.1 [90/130816] via 192.168.13.1, 00:13:36, GigabitEthernet0/0 2.0.0.0/32 is subnetted, 1 subnets D EX 2.2.2.2 [170/3072] via 192.168.13.1, 00:12:49, GigabitEthernet0/0 D 192.168.12.0/24 [90/3072] via 192.168.13.1, 00:13:36, GigabitEthernet0/0 r3#
Using the "redistributed" parameter had the very same effect: Config on R1: ! router eigrp 1 network 1.1.1.1 0.0.0.0 network 192.168.12.0 network 192.168.13.0 redistribute static eigrp stub connected summary redistributed ip route 2.2.2.2 255.255.255.255 192.168.12.2 !
For me, definitely answer "A".
A and B are correct, but both of them have terrible wording. A. If you configure a static route to 2.2.2.2, then that will remove that route from the EIGRP topology due to AD. So even if R1 was not a stub router, it would not advertise the route. On top of that, we not only have to redistribute static routes into EIGRP, we also need to configure the eigrp stub to advertise static, as follows: eigrp <AS#> redistribute static <---This alone does not redistribute the static route eigrp stub static <---This completes the static redistribute for a stub router B There is not distribute-list into eigrp stub command. But what I think cisco meant was to create a prefix-list for R2 Loopback, reference it into a route-map, and tie that to a leak-map in eigrp, as follows: ip prefix-list R2LOOP permit 2.2.2.2/32 ! route-map R2LOOP permit match ip address prefix-list R2LOOP ! router eigrp <AS#> eigrp stub leak-map R2LOOP So I think B is the best answer, as A is far too vague.
the answer correct is "A"
because, need redisitribute static in R1, because R1 is router stub
I don't know why but this questions seems like it's asking about leak-map feature of EIGRP stub configuration... I can't explain but I have this feeling maybe it's because there is no other question talking about leak-map. Therefor it's B to me.
Think the question has being edited - answer is now C (verified in CML)
Please ignore - its obviously B
There is no such option as distribute-list regarding leak-map, but redistribute command works as HungarianDish labbed: Correct answer is A
HQ(config-router-af)#do sh run | sec acc access-list 10 permit 192.168.4.0 0.0.0.255 (R2) access-list 20 permit 172.16.0.0 0.0.255.255 (R3) HQ(config-router-af)# HQ(config-router-af)#do sh run | sec route-m route-map LEAK-BR2 permit 10 match ip address 10 20 HQ(config-router-af)#do sh run | sec eig router eigrp cisco ! address-family ipv4 unicast autonomous-system 10 ! topology base network 0.0.0.0 eigrp router-id 5.5.5.5 eigrp stub connected summary leak-map LEAK-BR2 exit-address-family
Answer seems to be A. I will lab to verify on my own but the rest are not correct. B. there is no distribute-list leak-map command C. This is applying the change to R3. Since R1 is a stub as well, it is not propagating R2 to R3 routes. D. If we add a static null route for R2 loopback, we lose reachability to R2 loopback.
R1 router eigrp 1 network 1.1.1.0 0.0.0.255 network 192.168.12.0 network 192.168.13.0 eigrp router-id 1.1.1.1 eigrp stub connected summary ! ip forward-protocol nd ! ! no ip http server no ip http secure-server ip route 2.2.2.2 255.255.255.255 192.168.12.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)
R1(config)#router eigrp 1 R1(config-router)#redistribute static metric 1 1 1 1 1 R3#ping 2.2.2.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds: .....
R1(config-router)#router eigrp 1 R1(config-router)#stub static connected we need the connected keyword to advertise the links between the routers R3#ping 2.2.2.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 4/5/6 ms R3# B doesn't exist as a command
R1(config-router)#distribute-list ? <1-199> IP access list number <1300-2699> IP expanded access list number WORD Access-list name gateway Filtering incoming address updates based on gateway prefix Filter prefixes in address updates route-map Filter prefixes based on the route-map
R1(config-router)#distribute-list ? <1-199> IP access list number <1300-2699> IP expanded access list number WORD Access-list name gateway Filtering incoming address updates based on gateway prefix Filter prefixes in address updates route-map Filter prefixes based on the route-map
R1(config-router)#router eigrp 1 R1(config-router)#stub static connected we need the connected keyword to advertise the links between the routers R3#ping 2.2.2.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 4/5/6 ms R3# B doesn't exist as a command
R1(config-router)#distribute-list ? <1-199> IP access list number <1300-2699> IP expanded access list number WORD Access-list name gateway Filtering incoming address updates based on gateway prefix Filter prefixes in address updates route-map Filter prefixes based on the route-map
R1(config-router)#distribute-list ? <1-199> IP access list number <1300-2699> IP expanded access list number WORD Access-list name gateway Filtering incoming address updates based on gateway prefix Filter prefixes in address updates route-map Filter prefixes based on the route-map
R1(config)#router eigrp 1 R1(config-router)#redistribute static metric 1 1 1 1 1 R3#ping 2.2.2.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds: .....
R1(config-router)#router eigrp 1 R1(config-router)#stub static connected we need the connected keyword to advertise the links between the routers R3#ping 2.2.2.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 4/5/6 ms R3# B doesn't exist as a command
R1(config-router)#distribute-list ? <1-199> IP access list number <1300-2699> IP expanded access list number WORD Access-list name gateway Filtering incoming address updates based on gateway prefix Filter prefixes in address updates route-map Filter prefixes based on the route-map
R1(config-router)#distribute-list ? <1-199> IP access list number <1300-2699> IP expanded access list number WORD Access-list name gateway Filtering incoming address updates based on gateway prefix Filter prefixes in address updates route-map Filter prefixes based on the route-map
R1(config-router)#router eigrp 1 R1(config-router)#stub static connected we need the connected keyword to advertise the links between the routers R3#ping 2.2.2.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 4/5/6 ms R3# B doesn't exist as a command
R1(config-router)#distribute-list ? <1-199> IP access list number <1300-2699> IP expanded access list number WORD Access-list name gateway Filtering incoming address updates based on gateway prefix Filter prefixes in address updates route-map Filter prefixes based on the route-map
R1(config-router)#distribute-list ? <1-199> IP access list number <1300-2699> IP expanded access list number WORD Access-list name gateway Filtering incoming address updates based on gateway prefix Filter prefixes in address updates route-map Filter prefixes based on the route-map
B as everyone is said is not even possible , there is no such a command with distribution list . I go with A , for A to work we need to know the configuration of R1 . In order for this to work , we need 1) to create static route for R2 lo0 2) under eigrp process , when we are configuring the stub function , we won't just let the default stub, advertising connected and summary. We need to configure " eigrp stub connected static" , then in R3 , we will see as D EX 2.2.2.2 . So I only counted that they configure that. A is the answer
In my opinion the answer is C Here is the config I assume is configured on the routers based on the problem *R1* router eigrp 10 network 0.0.0.0 eigrp stub connected summary leak-map LEAK ip prefix-list TEST seq 5 permit 2.2.2.2/32 route-map LEAK permit 10 match ip address prefix-list TEST *R2* router eigrp 10 network 0.0.0.0 *R3* router eigrp 10 network 0.0.0.0 A) This is the configuration that this answer is suggesting. ip route 2.2.2.2 255.255.255.255 192.168.12.2 redistribute static metric 1000000 10 255 1 1500 However, the answer is missing the command "eigrp stub connected static" B) The command does not exist R1(config-router)#distribute-list ? <1-199> IP access list number <1300-2699> IP expanded access list number WORD Access-list name gateway Filtering incoming address updates based on gateway prefix Filter prefixes in address updates route-map Filter prefixes based on the route-map C) Correct D) Does not make any sense
anyone can post a configuration of this? The answer should be a leak-map
correct answer is B The EIGRP stub feature is useful to prevent unnecessary EIGRP queries and to filter some routes that you advertise. What if you want to configure your router as a stub router but still make an exception to some routes that it advertises? That is possible with the leak-map feature.
Leak-map can't be applied to distribute-lists it can only be applied to the stub so B is incorrect. A could be correct because R1 stub could be configured to advertise redistributed routes. In that case the route with null0 would be advertised to both routers. The route wouldn't become a successor on R2 because it already has a connected route with an AD of 1 which is lower than 90 so the R2 wouldn't add this route into his routing table. R3 on the other hand would add it to his routing table.
who said you would apply distribution list TO leap-map? it says WITH it.
I believe B is correct https://networklessons.com/cisco/ccie-routing-switching-written/eigrp-summary-leak-map
The answer "A" would work, but "B" makes so much more sense for me. https://networklessons.com/cisco/ccie-routing-switching-written/eigrp-stub-leak-map
Hi! There seems to be a problem with answer "B". As already pointed out in other comments, the "eigrp stub leak-map" is using a route-map, and not a distribute-list.
Answer C. A & D both require "redistribute static" under EIGRP. B is wrong because the leak-map is applied to the stub command and not via a distribute list.
the only one that can be right is A, the answer B is using a distribute list instead of a route-map that's the bad thing about this. The point is that we need also to remember that when eigrp stub is enabled by default you can only advertise connected network and summary networks, if we want to redistribute static routes we need to add the command eigrp stub connected summary static
this is the output afer the command mentioned: Metric weight K1=1, K2=0, K3=1, K4=0, K5=0 Soft SIA disabled NSF-aware route hold timer is 240 Router-ID: 192.168.34.2 Stub, connected, static, summary Topology : 0 (base) Active Timer: 3 min
output command show ip protocols: EIGRP-IPv4 Protocol for AS(100) Metric weight K1=1, K2=0, K3=1, K4=0, K5=0 Soft SIA disabled NSF-aware route hold timer is 240 Router-ID: 192.168.34.2 Stub, connected, summary router eigrp 100 network 192.168.24.0 0.0.0.3 network 192.168.34.0 0.0.0.3 redistribute connected redistribute static eigrp stub connected static summary
this is the output afer the command mentioned: Metric weight K1=1, K2=0, K3=1, K4=0, K5=0 Soft SIA disabled NSF-aware route hold timer is 240 Router-ID: 192.168.34.2 Stub, connected, static, summary Topology : 0 (base) Active Timer: 3 min
Im going with A on this just because answer B mention distribute list, thats not correct. We should use a prefix list with a route map or something like that.
Answer is A. You need these 2 commands: redistribute static and eigrp stub static
B is correct
it's a tricky one but the correct answer is A B: wrong because leak map only works with route-map
access-list 10 permit 2.2.2.2 route-map LEAK_MAP permit 10 match ip address 10 router eigrp 1 distribute-list route-map LEAK_MAP out
B is Wrong !!! . If you do this your access list has deny any on the end of the ACE , so the network between R1-R2 ( 192.168.12.0 ) and R1-R3 , are filtered also . Putting permit any in the end , also doesn't help . Leak map doesn't exist in distribution command .
R1(config)#ip access-list standard R2_L0 R1(config-std-nacl)#permit host 2.2.2.2 R1(config)#route-map R2_L0_LEAK R2(config-route-map)#match ip address R2_L0 R1(config)#router eigrp 1 R1(config-router)#eigrp stub leak-map R2_L0_LEAK