Summerization in Ripv2 is made using interface level configuration.
There are 2 notes that i want to point out down there , first while doing this lab i actually made a loop
second i want to point out to one limitation in RIPv2 concerning summerization
Task 1 : Summerize 2.0.0.0/8 out of R2 to R1 instead of 2.2.2.2/32
There are 2 notes that i want to point out down there , first while doing this lab i actually made a loop
second i want to point out to one limitation in RIPv2 concerning summerization
Task 1 : Summerize 2.0.0.0/8 out of R2 to R1 instead of 2.2.2.2/32
R2(config-if)#ip summary-address rip 2.0.0.0 255.0.0.0
Looks beautiful but now take another look at our topology ? don't you notice a problem , the problem is that the summary route kept appearing and disappearing from R1 so i made a debug ip rip database and noticed the below
*Mar 1 00:42:49.187: RIP-DB: Remove 2.0.0.0/8, (metric 4294967295) via 192.168.12.2, Serial0/0
What happened is the following R2 advertise to R1 2.0.0.0/8 so R1 advertise it to R3 then R4 and R4 then advertise it back to R2 from R2 momentery
R 2.0.0.0/8 [120/4] via 192.168.24.4, 00:00:00, Serial0/1
Note* that R2 don't install summary entry once summerization is configured and seems that this is what cause the problem
Solution Make R2 summarize out of all interfaces not only S0/0 but also through S0/1 to avoid loop
Task 2 : Summarize network 192.168.0.0/16 out of S0/0
R 2.0.0.0/8 [120/4] via 192.168.24.4, 00:00:00, Serial0/1
Note* that R2 don't install summary entry once summerization is configured and seems that this is what cause the problem
Solution Make R2 summarize out of all interfaces not only S0/0 but also through S0/1 to avoid loop
Task 2 : Summarize network 192.168.0.0/16 out of S0/0
R2(config-if)#ip summary-address r 192.168.0.0 255.255.0.0
Summary mask must be greater or equal to major net
It turned out that RIP doesn't support superneting so i can't advertise a summary address of a super net like 192.168.0.0 since it's by default a class C of /24
The only solution to fix issue would be create a null 0 route and resdistribute it into RIP
The only solution to fix issue would be create a null 0 route and resdistribute it into RIP
R2(config)# ip route 192.168.0.0 255.255.0.0 null 0
R2(config)# router rip
R2(config-router)# redistribute static
R1#sh ip route | i /16
R 192.168.0.0/16 [120/1] via 192.168.12.2, 00:00:04, Serial0/0