I've got a issues/question with the 2nd part of the section 2.7 BGP Summarization.
Here is the part:
- Create an additional Loopback interface on SW1 using the
148.X.177.0/24
subnet and advertise it into BGP.- This prefix should not be advertised outside of AS 65057.
- Ensure that R5 still has reachability to this network.
- The filtering configuration should be done on SW1.
While my solution matches the book the route 148.X.177.0/24 goes into R5 as EIGRP from SW1 via the redistribute action of RIP to EIGRP on SW1. Rip is thinking the route belongs to it from the network statement under RIP so it is redistributing it into EIGRP.
Rack1R5#show ip bgp 148.1.177.0
BGP routing table entry for 148.1.177.0/24, version 11
Paths: (1 available, best #1, table Default-IP-Routing-Table, not advertised to EBGP peer, RIB-failure(17))
Flag: 0x820
Not advertised to any peer
Local
148.1.57.7 from 148.1.57.7 (150.1.7.7)
Origin IGP, metric 0, localpref 100, valid, internal, best
Community: no-export
Rack1R5#show ip route 148.1.177.0
Routing entry for 148.1.177.0/24
Known via "eigrp 100", distance 170, metric 28416, type external
Redistributing via eigrp 100
Last update from 148.1.57.7 on GigabitEthernet0/0, 00:37:58 ago
Routing Descriptor Blocks:
* 148.1.57.7, from 148.1.57.7, 00:37:58 ago, via GigabitEthernet0/0
Route metric is 28416, traffic share count is 1
Total delay is 110 microseconds, minimum bandwidth is 100000 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 1
I'm trying to figure is this is as expected or was I expected to block it. If so I think it should be in the solution.
Maybe I missed something earlier in the lab but I'm not sure. If anyone else has come across this let me know.
Thanks,
Andy