RIPv1 Summarisation
nezzy456
Users Awaiting Email Confirmation Posts: 53 ■■□□□□□□□□
in CCNA & CCENT
Hi,
I was just wondering about summarisation.
If RIPv1 is summarising what happens to variable metrics?
If the router which is sending the summary knows of 2 networks which all are different hops away 1, 2.
172.30.1.0 172.30.2.0 192.168.1.0
Router
Router
Router2
Router 1
Boundary
What will he send to Router 1?
I guess he will summarise to 172.30.0.0 but what metric? 1 or 2?
Cheers
I was just wondering about summarisation.
If RIPv1 is summarising what happens to variable metrics?
If the router which is sending the summary knows of 2 networks which all are different hops away 1, 2.
172.30.1.0 172.30.2.0 192.168.1.0
Router
Router
Router2
Router 1
Boundary
What will he send to Router 1?
I guess he will summarise to 172.30.0.0 but what metric? 1 or 2?
Cheers
Comments
-
phoeneous Member Posts: 2,333 ■■■■■■■□□□Hi,
I was just wondering about summarisation.
If RIPv1 is summarising what happens to variable metrics?
If the router which is sending the summary knows of 2 networks which all are different hops away 1, 2.
172.30.1.0 172.30.2.0 192.168.1.0
Router
Router
Router2
Router 1
Boundary
What will he send to Router 1?
I guess he will summarise to 172.30.0.0 but what metric? 1 or 2?
Cheers
See attached screenshot from PT
From left to right, r1 - r2 - r3 - r4
r1 sh ip route
172.30.0.0/24 is subnetted, 2 subnets
C 172.30.1.0 is directly connected, Serial0/0/0
R 172.30.2.0 [120/1] via 172.30.1.2, 00:00:00, Serial0/0/0
R 192.168.1.0/24 [120/2] via 172.30.1.2, 00:00:00, Serial0/0/0
r2 sh ip route
C 172.30.1.0 is directly connected, Serial0/0/0
C 172.30.2.0 is directly connected, Serial0/1/0
R 192.168.1.0/24 [120/1] via 172.30.2.2, 00:00:25, Serial0/1/0
r3 sh ip route
172.30.0.0/24 is subnetted, 2 subnets
R 172.30.1.0 [120/1] via 172.30.2.1, 00:00:17, Serial0/0/0
C 172.30.2.0 is directly connected, Serial0/0/0
C 192.168.1.0/24 is directly connected, Serial0/1/0
r4 sh ip route
R 172.30.0.0/16 [120/1] via 192.168.1.1, 00:00:02, Serial0/0/0
C 192.168.1.0/24 is directly connected, Serial0/0/0
r1#sh ip pro
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 21 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: rip
Default version control: send version 1, receive any version
Interface Send Recv Triggered RIP Key-chain
Serial0/0/0 1 2 1
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
172.30.0.0
Passive Interface(s):
Routing Information Sources:
Gateway Distance Last Update
172.30.1.2 120 00:00:05
Distance: (default is 120)
r2#sh ip pro
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 2 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: rip
Default version control: send version 1, receive any version
Interface Send Recv Triggered RIP Key-chain
Serial0/0/0 1 2 1
Serial0/1/0 1 2 1
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
172.30.0.0
Passive Interface(s):
Routing Information Sources:
Gateway Distance Last Update
172.30.2.2 120 00:00:04
Distance: (default is 120)
r3#sh ip pro
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 5 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: rip
Default version control: send version 1, receive any version
Interface Send Recv Triggered RIP Key-chain
Serial0/0/0 1 2 1
Serial0/1/0 1 2 1
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
172.30.0.0
192.168.1.0
Passive Interface(s):
Routing Information Sources:
Gateway Distance Last Update
172.30.2.1 120 00:00:15
Distance: (default is 120)
r4#sh ip pro
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 28 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: rip
Default version control: send version 1, receive any version
Interface Send Recv Triggered RIP Key-chain
Serial0/0/0 1 2 1
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
192.168.1.0
Passive Interface(s):
Routing Information Sources:
Gateway Distance Last Update
192.168.1.1 120 00:00:07
Distance: (default is 120) -
Neeko Member Posts: 170I struggled to understand what you were even asking, man thats one badly articulated question