CCIE R&S Advanced Technologies Class v4.5 - RIP Overview, RIP Versions, RIP Auto-Summary

Transcript

1	Introduction	0h 43m
2	Using the Cisco Documentation	0h 52m
3	Ethernet Overview, Layer 2 Switchports, Trunking, ISL, 802.1q, DTP	0h 47m
4	VTP, VTP Authentication, VTP Pruning	1h 02m
5	VTP Prune Eligible List, VTP Transparent, VTP Troubleshooting, Trunk Allowed List, Extended VLANs	0h 48m
6	VLAN and VTP Review	0h 19m
7	SVIs, Native Routed Interfaces, Router-on-a-Stick	0h 46m
8	Layer 2 EtherChannel, EtherChannel Load Balancing, Layer 3 EtherChannel	0h 57m
9	802.1q Tunneling, Layer 2 Protocol Tunneling, EtherChannel over 802.1q Tunneling	1h 03m
10	STP Root Bridge Election, STP Root Port Election, STP Designated Port Election, STP Priority, STP Cost, STP Port-Priority	1h 06m
11	STP Review	0h 12m
12	STP Timers, STP PortFast	0h 34m
13	STP UplinkFast	0h 11m
14	STP BackboneFast	0h 12m
15	STP BPDU Filter	0h 13m
16	STP BPDU Guard	0h 11m
17	STP Root Guard	0h 11m
18	STP Loop Guard, Unidirectional Link Detection (UDLD)	0h 11m
19	Multiple Spanning-Tree Protocol (MST)	0h 40m
20	Rapid Spanning-Tree Protocol (RSTP), Rapid-PVST	0h 18m
21	MST with Multiple Regions	0h 33m
22	Flex Links	0h 16m
23	Frame Relay	0h 39m
24	Frame Relay Configuration Part 1	0h 34m
25	Frame Relay Configuration Part 2	0h 41m
26	Frame Relay Switching	0h 27m
27	Back-to-Back Frame Relay	0h 08m
28	Frame-Relay End-to-End Keepalives	0h 18m
29	PPP, PPP PAP Authentication, PPP CHAP Authentication	0h 59m
30	PPPoFR, PPPoE	0h 40m
31	Transparent Bridging, IRB	0h 32m
32	Fallback Bridging	0h 14m
33	IP Routing Overview, Switching Paths, Static Routing	0h 42m
34	Static Routing Examples	0h 25m
35	IP Default-Gateway, IP Default-Network	0h 14m
36	On-Demand Routing (ODR)	0h 07m
37	Floating Static Routes	0h 10m
38	Backup Interface	0h 29m
39	Enhanced Object Tracking, IP SLA, Reliable Static Routing	0h 21m
40	Policy Routing	0h 43m
41	GRE Tunneling, GRE Recursive Routing Errors	0h 27m
42	Reliable Backup Interface with GRE	0h 25m
43	RIP Overview, RIP Versions, RIP Auto-Summary	0h 48m
44	RIP Split-Horizon, RIP Timers	0h 22m
45	RIP Broadcast Updates, IP Directed Broadcast, IP Broadcast-Address, Smurf Attacks, Fraggle Attacks	0h 16m
46	RIP Unicast Updates	0h 03m
47	RIP Offset-List	0h 18m
48	RIP Authentication	0h 11m
49	RIP Summarization	0h 10m
50	Prefix-Lists, RIP Distribute-List Filtering, RIP Administrative Distance Filtering	0h 48m
51	RIP Default Routing, RIP Conditional Default Routing	0h 18m
52	RIP Triggered, RIP Validate Update Source,	0h 12m
53	EIGRP Overview	0h 29m
54	EIGRP Auto-Summary	0h 07m
55	EIGRP Split-Horizon	0h 11m
56	EIGRP Update Types, EIGRP Neighbor, EIGRP Passive-Interface	0h 24m
57	EIGRP Hello-Interval, EIGRP Hold-Time	0h 05m
58	EIGRP Authentication	0h 11m
59	EIGRP Time Based Authentication	0h 25m
60	EIGRP Path Selection, EIGRP Metric Weights, EIGRP Traffic Engineering	0h 47m
61	EIGRP Unequal Cost Load Balancing, EIGRP Variance	0h 19m
62	EIGRP QUERY, EIGRP Summarization, EIGRP Leak-Map	0h 28m
63	EIGRP Stub Router Advertisement	0h 22m
64	EIGRP Default Routing	0h 13m
65	EIGRP Route Filtering	0h 11m
66	EIGRP Router-ID	0h 07m
67	Miscellaneous EIGRP Features	0h 02m
68	OSPF Overview	0h 27m
69	Establishing OSPF Adjacencies, Understanding the OSPF Database	0h 43m
70	OSPF Network Type Broadcast, OSPF DR/BDR Election, OSPF over NBMA, OSPF Network Type Non-Broadcast and Point-to-Multipoint	0h 56m
71	OSPF Network Type Point-to-Point, OSPF Network Type Mismatch	0h 13m
72	OSPF Network Type Point-to-Multipoint Non-Broadcast, OSPF Per Neighbor Cost	0h 17m
73	OSPF Network Type Loopback	0h 02m
74	OSPF Path Selection	0h 27m
75	OSPF Convergence Timers	0h 09m
76	OSPF Authentication	0h 12m
77	OSPF Summarization	0h 32m
78	OSPF Stub Areas, OSPF Totally Stubby Areas, OSPF NSSAs, OSPF Totally NSSAs	0h 40m
79	Controlling OSPF NSSA Redistribution	0h 02m
80	OSPF Type 7 to 5 Translator Election, OSPF LSA Type 3 Filter, OSPF Forwarding Address Suppression	0h 24m
81	Route Redistribution Overview	0h 36m
82	Route Redistribution Configuration & Verification, Connected Redistribution	0h 22m
83	OSPF External Path Selection, TCL PING Scripting	0h 33m
84	Routing Loops Overview, EIGRP Route Loop Prevention	0h 55m
85	Metric Based Routing Loops, Route Tagging	0h 46m
86	Administrative Distance Based Routing Loops, Debug IP Routing, IP Route Profile	0h 58m
87	BGP Overview, BGP Peering Types	0h 51m
88	Establishing BGP Peerings, EBGP Multihop, BGP Neighbor Disable Connected Check, BGP TTL Security	0h 49m
89	BGP 4-Byte ASNs	0h 20m
90	BGP Local AS, BGP Peer Groups	0h 30m
91	BGP Next-Hop Self, BGP Next-Hop Processing	0h 30m
92	BGP Route Reflectors	0h 37m
93	Large Scale BGP Route Reflectors with Clusters	0h 34m
94	BGP Confederation	0h 37m
95	BGP NLRI Advertisements, BGP Network Statement, BGP Redistribution	0h 43m
96	BGP Aggregation, BGP Aggregation & Summary-Only, BGP Aggregation & Unsuppress-Map	0h 46m
97	BGP Origin, BGP Aggregation & AS-Set, BGP Aggregation & Advertise-Map	0h 22m
98	BGP Conditional Route Injection	0h 21m
99	BGP Bestpath Selection, BGP Multipath, BGP Weight	0h 53m
100	BGP Local Preference, BGP Local Preference and Communities, BGP AS-Path Prepending,	0h 30m
101	BGP MED, BGP MED Missing As Worst, BGP Deterministic MED	0h 17m
102	BGP Communites, BGP Regular Expressions	0h 43m
103	BGP Filtering, BGP Convergence Timers, BGP Default Routing, Miscellaneous BGP Features	0h 24m
104	MPLS Overview, MPLS Label Distribution Protocol (LDP)	1h 05m
105	MPLS Tunnels, MPLS Penultimate Hop Popping (PHP)	0h 40m
106	MPLS Layer 3 VPNs Overview, VRF Lite	0h 36m
107	MPLS Layer 3 VPNs and VPNv4 BGP	1h 08m
108	MPLS Layer 3 VPN Verification & Troubleshooting	0h 49m
109	MPLS Layer 3 VPN OSPF PE-CE Routing Overview	0h 06m
110	MPLS Layer 3 VPN OSPF PE-CE Routing Path Selection & Sham-Links	2h 01m
111	MPLS Layer 3 VPN OSPF PE-CE Routing Loop Prevention & Down-Bit, OSPF Capability VRF-Lite	0h 40m
112	IPv6 Overview, IPv6 ICMPv6 ND, IPv6 over NBMA	0h 44m
113	IPv6 Routing Overview, IPv6 Static Routing	0h 28m
114	IPv6 RIPng	0h 20m
115	IPv6 EIGRPv6	0h 09m
116	IPv6 OSPFv3	0h 31m
117	MP-BGP for IPv6	0h 26m
118	IPv6 Tunneling	1h 13m
119	Multicast Overview, IGMP	0h 34m
120	PIM Overview	0h 18m
121	PIM Dense Mode	1h 03m
122	PIM Sparse Mode	0h 30m
123	PIM Sparse Mode Configuration	0h 36m
124	PIM Sparse Mode RPF & RP Troubleshooting	0h 27m
125	Auto-RP, Multicast over GRE Tunnels	0h 53m
126	Bootstrap Router (BSR), Bidirectional PIM, Source Specific Multicast (SSM)	0h 40m
127	MSDP, Anycast RP	0h 27m
128	IPv6 Multicast Routing	0h 24m
129	QoS Overview, IntServ QoS, DiffServ QoS, IP Precedence, DSCP, MQC, HQF	0h 41m
130	MQC Classification	0h 44m
131	FIFO, FQ, WFQ, CBWFQ, HQF	0h 50m
132	LLQ	0h 23m
133	WRED	0h 31m
134	Traffic Shaping, Traffic Policing	0h 40m
135	Frame Relay Traffic Shaping (FRTS)	0h 33m
136	RSVP	0h 07m
137	Catalyst 3560 QoS	1h 00m
138	IOS Security Overview, Access Lists (ACLs)	0h 58m
139	Time Based ACLs, Dynamic ACLs	0h 33m
140	Reflexive ACLs	0h 21m
141	TCP Intercept, Content Based Access Control (CBAC)	0h 34m
142	Zone Based Policy Firewall (ZBPF)	1h 09m
143	AAA, Local Authentication, Local Authorization, Role Based CLI Access	0h 43m
144	Port Security, Static CAM Entries, Storm Control, 802.1X Authentication, PACLs, RACLs, VLAN Access Maps (VACLs)	0h 48m
145	DHCP Snooping, Dynamic ARP Inspection (DAI), IP Source Guard	0h 12m
146	Protected Ports, Private VLANs	0h 25m
147	IP Services Overview, HSRP	1h 10m
148	VRRP, GLBP	0h 28m
149	NAT	0h 42m
150	DHCP, DNS	0h 30m
151	NetFlow	0h 09m
152	WCCP, Miscellaneous IP Services	0h 06m
153	System Management Overview, NTP, NTP Authentication	0h 24m
154	SNMP, RMON	0h 38m
155	Syslog, Telnet, SSH, Banners	0h 21m
156	EEM Scripting, Miscellaneous System Management	0h 26m
Total Duration		81h 02m

Slides - Diagrams

Slides - Introduction

Slides - Ethernet Switching

Slides - Advanced Ethernet Switching

Slides - Frame Relay

Slides - PPP

Slides - Transport Bridging

Slides - Redistribution

Slides - IOS Security

Slides - Layer 2 Security

Slides - IP Services

Slides - System Management

0:00:13	So, in our next section here, we're gonna discuss
0:00:18	mainly within the scope of RIP version 2...
0:00:21	as RIP version 1 doesn't really
0:00:25	in today's networks since it's considered a
0:00:32	Now, we'll see as we compare RIP to the more
0:00:39	there's really not that many features that
0:00:43	There's not too many caveats about how RIP works
0:00:50	but within the scope of the
0:00:53	there's no excuse for not understanding
0:00:59	So, every feature that is documented
0:01:03	every feature that's documented
0:01:06	you do need to understand how
0:01:09	Because it's pretty much the most basic
0:01:14	So, there should not be any case that could
0:01:20	when we are tested on this.
0:01:22	Now, RIP is considered a distance
0:01:28	which means that it uses loop prevention
0:01:32	Poison Reverse, Count to Infinity, which is gonna
0:01:38	Because devices in the RIP domain,
0:01:40	they're not gonna understand what's
0:01:44	They only know what their directly connected
0:01:49	and RIP does not support any topology...
0:01:52	advertisement information to tell the routers where the prefixes
0:02:00	So, sometimes, this distance vector
0:02:05	because when we receive the updates in, we really have
0:02:11	or what are the different devices
0:02:14	in order to get to those
0:02:18	So, we'll see that there are some potential
0:02:23	Especially when we're doing redistribution
0:02:27	because RIP has no idea what's
0:02:34	Now, RIP does not use its
0:02:38	It rides on top of UDP using port number 520,
0:02:43	which implies that if we're gonna exchange
0:02:46	then, we need to have
0:02:51	So, if there's any type of filtering or
0:02:54	we would need to make sure that
0:02:59	and that port being 520 is
0:03:06	As I mentioned, the two different versions:
0:03:09	we're mainly gonna be
0:03:13	because this is a classless protocol which means
0:03:19	or super nets, or aggregates that are of
0:03:26	So, essentially, any protocol that
0:03:31	or Variably Length Subnet Masks,
0:03:33	we would consider those as classless.
0:03:37	Now, RIP version 1, when we look at the
0:03:41	it did not include a field that was the subnet mask or
0:03:49	So, RIP version 1 did not support...
0:03:51	different lengths of masks in the network,
0:03:55	which means that if we were
0:04:00	and we wanted to subnet this. Every subnet
0:04:05	So, we could use all /24s or /26s, or all /22.
0:04:12	As long as the masks are the same,
0:04:16	because the issue is that the subnet mask
0:04:23	Now, another difference between them is that
0:04:29	which means that other devices on the segment
0:04:34	they would have to process the updates.
0:04:38	So, any other hosts or any other routers that are on
0:04:44	there would be an interrupt in the CPU
0:04:48	because it's destined for the all
0:04:56	So, the devices would have to process the
0:05:00	Now, RIP version 2 is a little bit more
0:05:04	because there is a reserved
0:05:10	that is specifically for that routing
0:05:16	This means that if we were running RIP version 2
0:05:22	by default, they would not be
0:05:26	So, unless they were actually
0:05:29	and listening for the multicast
0:05:33	they're not gonna have to process those updates.
0:05:37	So, the two main difference is there,
0:05:40	which means that with classless,
0:05:45	because in the RIPv2 update packet format,
0:05:53	which is the network, and the prefix
0:06:00	Now, configuration wise, the RIP
0:06:04	We simply go to global configuration
0:06:08	there's no process number, there's
0:06:11	which means that on the router, we can only
0:06:18	Now, we will see later when
0:06:22	and to the Virtual Routing and
0:06:29	we can have multiple instance
0:06:33	if they are dedicated to different routing tables.
0:06:36	So, we can have one process that's
0:06:40	then, other sub-processes that
0:06:44	But for the global routing table,
0:06:50	As opposed to protocols like EIGRP or OSPF,
0:06:53	we can define based on the EIGRP autonomous
0:06:59	that we can have multiple instances running
0:07:05	So, once we initialize the process
0:07:08	then, we're going to tell the router what
0:07:13	and what interfaces do we
0:07:16	This is what the network
0:07:20	Since RIP has its origins
0:07:24	with RIP version 1, the network statement
0:07:31	Now, this does not control
0:07:35	It simply controls what interface the
0:07:41	But the potential issue that
0:07:44	is that since the network statement
0:07:48	which is the classful network, it means that if we want
0:07:55	but, all of the interfaces are
0:07:58	we're gonna have to go some steps beyond
0:08:03	or to filter updates as they're coming in access list,
0:08:07	because RIP is only gonna support network statements
0:08:15	Once we enable the protocol,
0:08:18	a couple quick verifications that we can do,
0:08:22	is gonna show us some of the
0:08:26	like what are the timers, what are the different
0:08:31	what interfaces the protocol has enabled,
0:08:33	and whether we are receiving
0:08:39	Once we receive the updates in,
0:08:42	they go into the RIP database for processing
0:08:47	So, just like OSPF or EIGRP, or BGP,
0:08:51	there's two different data structures
0:08:54	One that lists all the routes that we are advertising
0:09:00	and then, the active instance of which of
0:09:04	That would be the routing table,
0:09:07	or the forwarding table when we look at the routes used by the
0:09:17	If we do run into some problems with
0:09:21	we can look at the Debug IP RIP Output.
0:09:24	This is gonna show us any updates that we are
0:09:31	So, if for some reason, networks are missing from the
0:09:37	we can see, is that updates actually
0:09:41	Are there any problems with
0:09:44	Those type of issues would show
0:09:51	Now, configuration wise,
0:09:56	definition between the RIP version 1
0:10:01	They're both gonna be running under
0:10:06	This means that we have the control
0:10:11	are we running on a per-link basis.
0:10:15	Now, by default, we'll see that IOS sends
0:10:21	but it listens for both version 1 and
0:10:28	We can change this either global on the
0:10:31	or the individual link levels with the IP RIP
0:10:37	depending if we wanna run some combination
0:10:45	So, in any case, regardless of what version we're
0:10:51	we can verify this with
0:10:54	that again, will tell us what are all
0:10:57	What version are we sending?
0:11:01	And that who are the actual neighbors that we
0:11:08	The next important default
0:11:12	is that since it has its origins as a
0:11:18	RIP version 2 follows along with the
0:11:25	So, even though RIP version 2
0:11:29	it does do automatic classful
0:11:33	Which is controlled by the Auto-Summary
0:11:37	Now, we'll see that the RIP version process
0:11:42	when we're using the Auto-Summary
0:11:46	because regardless whether
0:11:49	RIP version 2 will automatically support VLSM,
0:11:54	but only for subnets that are
0:12:01	Now, what I mean by the major network...
0:12:04	is any subnet that is sharing
0:12:14	So, for example, if we have
0:12:21	and 10.1.2.0/24,
0:12:25	and 10.1.3.0/31,
0:12:32	all of these networks fall under
0:12:39	Because the classful network
0:12:47	So, the major network or the classful network
0:12:51	If we were looking at other
0:13:01	192.168.2.0/24, these would be
0:13:10	because anything that starts with the 192,
0:13:16	Now, if you haven't seen a lot of the details behind
0:13:23	there's an easy way to tell what is
0:13:28	and what is the major network
0:13:34	in the... The first four most
0:13:40	So, when we look at an address,
0:13:47	so, in dotted decimal format, we would
0:13:52	And in this first octet A,
0:14:01	So, 8 bits there, that's gonna make
0:14:05	Now, the first four of these control
0:14:11	Anything that starts with 0.0.0.0,
0:14:16	this is a class A network.
0:14:19	Anything that starts with 1.0.0.0,
0:14:22	this is a class B, or actually, it's less specific
0:14:32	it's anything that just starts with zero.
0:14:35	This would be A.
0:14:36	For class B, this starts with 1.0.
0:14:41	Class C would be 1.1.0.
0:14:45	Class D is 1.1.1.0,
0:14:50	and then finally, class E is 1.1.1.1.
0:14:55	Where our class D addressing,
0:15:00	and the class A, B, and C, this would
0:15:06	So, just by looking at the first octet, we can figure out what
0:15:12	And that's gonna tell us what
0:15:18	Now, the reason that this is significant...
0:15:21	is that with the default behavior RIP
0:15:25	there are some problems we'll
0:15:28	when the networks cross the
0:15:32	they will be automatically summarized
0:15:38	The result of this in certain circumstances is that
0:15:44	if the routers do not understand where the individual
0:15:51	We'll see later when we get to EIGRP,
0:15:54	the EIGRP process fixes this automatically
0:15:57	by essentially no routing any major
0:16:03	that we are receiving, but also
0:16:09	Now, in our particular case,
0:16:13	the devices in the network are using
0:16:25	for all of the transit links between the neighbors.
0:16:29	So, for example, between routers 1, 4, and 6,
0:16:41	So, this means that that /24, that is the subnet
0:16:51	Additionally, these routers have loopback addresses
0:16:57	Where the major network of the
0:17:05	And the 10 in this case is because I'm using
0:17:10	So, from router 6's perspective, its subnet
0:17:17	Where routers 5's would be 150.10.5.0/24.
0:17:27	Now, once we enable RIP on
0:17:31	we will see that with the default behavior,
0:17:34	since the transit links are in a different
0:17:40	when router 5 does an advertisement
0:17:44	it will be summarized to the /16
0:17:55	Now, if we look at any of the
0:17:59	and we were to variably subnet these.
0:18:02	Let's say that on router 5,
0:18:06	with the default configuration,
0:18:15	We can variably subnet this if
0:18:23	We'll see that even with auto-summary on,
0:18:27	RIP version 2 will support the
0:18:32	as long as the major network matches the interface
0:18:41	So, since all of the transit links
0:18:46	it means that any subnet mask inside
0:18:51	But anytime we cross the major network
0:18:58	then, the prefixes will be
0:19:03	So, let's take a look at
0:19:06	What I'm gonna do is just simply enable
0:19:11	We'll run version 2,
0:19:15	and we will advertise 155.10 and 155.10,
0:19:20	but we're gonna leave
0:19:27	So again, configuration wise,
0:19:30	We just go to global config.
0:19:32	Make sure that the routing process is on.
0:19:36	Start the global RIP process, and then specify
0:19:43	So I'll say 155...
0:19:46	And 155.10 and 150.10.
0:19:50	I could be more specific
0:19:54	I could say in the case of...
0:19:56	switch 4, if I do Show
0:20:02	we see that our loopback is actually
0:20:08	because it's a subnet of the major network.
0:20:11	But if we were to look at the
0:20:18	we'll see that any subnet advertisement
0:20:26	is gonna be automatically
0:20:30	So, this could be one shortcut to figure out
0:20:36	the address is part of.
0:20:38	So, I entered... Actually it was
0:20:45	but the RIP process is changing this to
0:20:53	So, let's take the same configuration,
0:20:58	So, I'll do this on the access server,
0:21:02	It's gonna quickly allow me to send a bunch
0:21:08	to go to all of the router's consoles.
0:21:10	So first, I'll make sure that everyone
0:21:15	They need to go to global config.
0:21:17	Start the RIP process, and then
0:21:23	Network 150.10.0.0 and
0:21:30	Then, we'll go back to accept.
0:21:32	Control Z, then this should send
0:21:38	So, assuming that all of the routers were
0:21:43	that they were not in user mode,
0:21:45	then, we should see the result
0:21:50	that it did go to global config, it did run the
0:21:56	So next, let's look at router 5.
0:21:59	And we'll do a basic verification to see, is the
0:22:05	what are the defaults of the process?
0:22:08	And who are the neighbors that
0:22:11	So, if we look at router 5,
0:22:19	It says, "Right now,
0:22:23	And we don't have any filter sets.
0:22:26	We don't have any type of distribute list or
0:22:32	It says that the default timers are
0:22:37	Invalid and hold down after 180,
0:22:44	So, this essentially means
0:22:47	but then for 240 seconds later,
0:22:52	then, it's gonna be removed from the RIP
0:22:58	But after receiving the update once the
0:23:03	the network will go into hold down,
0:23:06	which means that I will not
0:23:10	if it has a worst hop count than the
0:23:17	So, this is the way that RIP tries to
0:23:23	So, we'll see this in more detail a little bit
0:23:29	Next, we see that the default send version is 1,
0:23:37	These are the actual interfaces
0:23:41	So, we're resetting version 1 for
0:23:46	Auto-summary is in effect.
0:23:48	The default maximum paths is 4,
0:23:50	which means that if we had equal
0:23:55	so both the same longest match
0:23:59	we would install up to 4
0:24:03	and then tell this either to the fast
0:24:07	Then, it's up to the switching path to actually
0:24:13	So again, as we saw previously
0:24:16	it's not the actual routing protocols or the routing
0:24:22	The routing table just presents the
0:24:27	Then, the switching path actually determines
0:24:35	Next, we see the networks...
0:24:37	that we are routing for. This essentially means what
0:24:45	if their addresses fall
0:24:48	So, if I have any interface that has the
0:24:54	then, we're running RIP on that.
0:24:55	Likewise if they start with 155.10,
0:24:58	we're running RIP on that.
0:25:01	So, it does not control what
0:25:05	because what is advertised is controlled by
0:25:10	So, what is the address?
0:25:12	This simply means that we have the
0:25:17	And we can see that again from this output.
0:25:22	both of our serials, and the loopback.
0:25:28	Next, we see the routing information sources.
0:25:32	These are the neighbors...
0:25:35	that we are learning RIP updates from.
0:25:38	For each of these neighbors, we're using the
0:25:45	which implies that we can change the
0:25:50	So, we'll see that if we're trying to do
0:25:53	or any type of filtering for RIP,
0:25:56	not only can we change the
0:26:01	we can change it on a per-neighbor basis,
0:26:04	and we can change it on a per-prefix
0:26:10	There's a question here, "What does it
0:26:14	So, if we scroll up a little bit,
0:26:16	this output here, Redistributing RIP,
0:26:18	it simply means that it's only advertising
0:26:27	or connected interfaces that
0:26:31	So, if we were to redistribute EIGRP into RIP,
0:26:35	then it would say Redistributing RIP EIRP.
0:26:39	So, it essentially means that
0:26:41	It's just the default output to tell us what different
0:26:48	are we picking the prefixes from
0:26:59	So next, let's look at what is the
0:27:04	If we Show IP RIP Database,
0:27:09	it says that we have two
0:27:14	One is for the major network
0:27:19	The other one s for the major network that is
0:27:27	Fast Ethernet 0/0,
0:27:28	and serial 0/0.
0:27:32	We see that we are
0:27:37	from the different neighbors.
0:27:38	And also that inside the 155.10 network,
0:27:43	I have some Variably Length
0:27:47	So on my local interface, Fast Ethernet 0/1,
0:27:51	I have this configured as a /25.
0:27:56	Now, if we look at the result of this,
0:27:59	in the routing table, let's say on switch 2,
0:28:05	"I wanna know what
0:28:09	that switch 2 is receiving from router 5."
0:28:12	So, 5 is running RIP on all of its links.
0:28:18	But with the default options,
0:28:23	So, this means then if I were to look
0:28:28	I would only be receiving...
0:28:33	either classful summaries,
0:28:36	or subnets that match exactly to the
0:28:45	So, if we look at the
0:28:49	Show Run Interface VLAN 58,
0:28:52	we can see that VLAN 58 has the
0:29:01	Now, from RIP version 1's perspective,
0:29:04	if we were to look at the Debug IP RIP,
0:29:08	when the update comes in from router 5,
0:29:13	the prefixes are included,
0:29:19	Now, if the prefixes include subnets,
0:29:24	we will assume that the mask of the subnets matches
0:29:33	So here, we see that now, we received...
0:29:37	we received an update from router 5.
0:29:42	This update includes 150.10.0.0. So, we are
0:29:51	Then, we are receiving subnets.
0:29:54	It doesn't tell us the mask of these though.
0:29:57	Since my interface is /24,
0:30:00	I'm gonna assume that all of these are /24.
0:30:04	So, this means that none of
0:30:09	We see that router 5 is not
0:30:16	because when we look back at router 5,
0:30:19	this prefix doesn't have the same
0:30:27	So, this is the default classful
0:30:31	That when we send updates out,
0:30:37	or the subnets that match the
0:30:43	On the other end of the advertisement,
0:30:45	since normally, my connected neighbor
0:30:49	they will assume that the mask of those
0:30:59	So, typically, we would not do this configuration,
0:31:05	Because pretty much every possible implementation of
0:31:10	Whether this is on the routers or
0:31:15	there's really no reason to run version 1.
0:31:18	So, next step, I'm gonna go
0:31:23	and set it to be version 2 globally.
0:31:27	So, simply, the version 2
0:31:30	If we now, look at the result of this
0:31:43	we see that now the default version 4 RIP is 2, both
0:31:51	So, we're sending version 2,
0:31:55	This means now that the router would be ignoring
0:32:02	Which really shouldn't be a problem unless there's some
0:32:10	So, pretty much everything else
0:32:12	The timers are the same
0:32:15	There's no difference in the maximum paths.
0:32:17	Automatic summarization is still on.
0:32:19	Only difference is that we're now sending only
0:32:26	We could then control this on the
0:32:31	like let's say on Fast Ethernet 0/1,
0:32:36	maybe I have some legacy host
0:32:39	So, I'll say, IP RIP Send Version 1 and 2.
0:32:45	And I will receive version 1 and 2.
0:32:51	If we look at the result to this
0:32:55	we could see now for this particular link,
0:33:04	So, this then would mean that everytime
0:33:08	it has to send it separately in
0:33:12	and separately in the
0:33:16	So, we essentially have doubled the updates.
0:33:18	Because when we look at this from
0:33:21	the version 1 and the version 2
0:33:28	It's simply that the router supports running both
0:33:34	So now, let's lok at the result to this,
0:33:38	was that we set all routers to be
0:33:42	We still did not disable automatic
0:33:46	If we now look at the
0:33:51	let's say, Show IP Route RIP.
0:33:54	We see now that we are
0:34:02	but also the /25 subnet.
0:34:06	So, since we're running version 2,
0:34:08	the update does include the
0:34:12	Which means that we can support
0:34:16	Also, we are receiving the summary for
0:34:25	Since auto summary is on, we cannot advertise the
0:34:34	Again, if every single link in the network
0:34:40	then it would not be a problem.
0:34:42	It's only that we have 2
0:34:46	that we have this disconnect
0:34:51	Now, we'll also see that whether
0:34:57	or whether we're running
0:35:00	both of them support the
0:35:04	So, if I were to go to switch 2, let's say,
0:35:12	And I said the address was 1.2.3.4/32
0:35:19	Then, under the RIP process,
0:35:24	I'll enable the process on the link.
0:35:27	Eventhough automatic summarization is on,
0:35:31	if we were to look at switch 4, one of
0:35:35	and Show IP Route RIP.
0:35:45	We see, let's see, 1.0.0.0/8,
0:35:53	this version of code may not support this.
0:36:00	Show IP Route RIP.
0:36:05	It sees just the /8. So...
0:36:09	Router 5 and switch 4, they're receiving
0:36:16	Let's try this real quick. Let's go to everyone.
0:36:19	And I'm gonna revert them back to version 1.
0:36:23	So, under router RIP, we'll say, Version 1 Only.
0:36:33	And now, if we look at...
0:36:37	Switch 4, let's say Show IP Route RIP,
0:36:45	I wanna see when the new update
0:36:54	now we're still receiving it as 1.0.0.0/8.
0:36:59	The previous versions used to support this
0:37:04	that RIP would...
0:37:07	automatically advertise this /32 regardless,
0:37:11	I'm wondering if it has to be in the same...
0:37:14	major network. Let's try that here.
0:37:20	that we have another loopback.
0:37:23	Let's say loopback 155...
0:37:27	10.88,
0:37:31	I'll say, "The address is 155.10.88.88/32."
0:37:42	This is already part of our major network
0:37:47	And if we look at the other neighbors now,
0:37:52	now, the host route is learned. So, really,
0:37:59	that is supports the advertisement of the host routes.
0:38:04	But as we could see, it still has to be
0:38:09	So, if you have two different pools of addresses
0:38:15	and you try to run this
0:38:18	or RIP version 2 with auto-summary off,
0:38:21	or excuse me, with auto-summary on,
0:38:23	then, potentially, you could have
0:38:30	Now, where we will see this...
0:38:33	in this particular case...
0:38:35	is with version 2 configured,
0:38:41	the routers will be receiving
0:38:47	from different neighbors about
0:38:51	So now, I've changed it back to version 2.
0:38:53	If we look at router 5 and say,
0:39:00	we know about...
0:39:02	the subnets that make up
0:39:07	So, we know about the /32.
0:39:09	The other neighbor should
0:39:14	but look at the loopback advertisements.
0:39:19	It says, "We're receiving...
0:39:22	4 updates...
0:39:24	about the same prefix, which is...
0:39:28	150.10.0.0/16,
0:39:30	it's coming from routers 1, 2, 3, and 4.
0:39:37	Now, as we know from the initial
0:39:42	this is not really the case.
0:39:43	Now, router 4 for example here,
0:39:46	it has the prefix 150.10.4.4/24,
0:39:55	where router 1 has 150.10.1.1/24.
0:40:02	The /16, that's not what we actually
0:40:08	But when these updates are sent out,
0:40:10	since we're crossing the
0:40:14	these are then automatically
0:40:22	What is gonna be the end result
0:40:27	if we were to try to send traffic
0:40:32	So, let's say now on router 5,
0:40:36	or to the destination address 150.10.1.1.
0:40:44	The routing process says that
0:40:49	Now, there's actually more than that, but the
0:40:52	If I set next one path's higher, we would see
0:41:01	So, whether reachability is
0:41:04	it really does not depend on
0:41:08	It's gonna depend on the switching process
0:41:14	So, let's say now we try
0:41:20	It just so happens that however
0:41:27	we are pointing this particular
0:41:33	If I were to say, Show IP CEF Exact Route,
0:41:38	what happens when I'm sending
0:41:44	and I'm going to 150.10.1.1?
0:41:49	CEF says...
0:41:51	that this is coming from me
0:41:58	The interface is serial 0/0/0.
0:42:01	The address that we're
0:42:06	Now, we may see this change depending
0:42:12	So, if I were to go to the...
0:42:17	Just the global config here.
0:42:22	So, this is reverting us to either
0:42:30	Now, let's send this packet on 5.
0:42:38	Now, we see that not all of the
0:42:43	Because it just so happens that
0:42:48	is making a different decision than CEF,
0:42:52	which means that some of the times, the packets
0:42:59	Now, what I could also do
0:43:02	all of these interfaces I'm running IP
0:43:07	This is gonna turn process
0:43:13	So, those are all my links that are running IP.
0:43:16	Additionally...
0:43:18	And I'm not sure if this is the interface
0:43:22	And if we say, IP Load Sharing Per
0:43:29	And I'm gonna say this on all of these links.
0:43:31	So, on the frame-relay, IP Load
0:43:38	point-to-point serial to router 4.
0:43:40	And then, on my two LAN interfaces.
0:43:49	So now, this means when
0:43:53	and then the outgoing interface is
0:43:58	the switching process should
0:44:03	and load balance between
0:44:08	Now, in this case, since I
0:44:11	it should mean that one of
0:44:14	and three of them are gonna be wrong.
0:44:18	Because the only one that's correct to send traffic
0:44:23	The other ones, depending on
0:44:28	They may or may not
0:44:30	But if we ping the destination
0:44:34	and let's say we send a bunch of packets,
0:44:40	we'll see that some of the times,
0:44:43	the packet is gonna get through,
0:44:48	some of the times, it won't.
0:44:52	And we may have to send this as...
0:44:56	transit traffic. Let's do this. Let's say...
0:45:00	Clear IP Cache.
0:45:04	And then try this again. Let's say,
0:45:25	And also, this is gonna depend on
0:45:29	So, if we look at this over
0:45:34	we'd see that some of the times, the traffic is
0:45:37	It really depends on how
0:45:40	which of these neighbors we're
0:45:44	Because again, this is not
0:45:47	The routing process just installs
0:45:51	then hands it over either to process switching,
0:45:56	Then, that determines where the interface
0:46:04	So, if I were to vary the input and the
0:46:08	this traffic is gonna work, sometimes, it's not.
0:46:11	But there's really no way to predict
0:46:14	So, let's say we send traffic to router 2.
0:46:19	Okay, as we see, some of the
0:46:22	Some of them are not.
0:46:27	So, anytime that you see this
0:46:32	where some of the traffic gets
0:46:37	usually, that would be related to an error
0:46:41	in the relationship between the
0:46:46	where possibly, some of the
0:46:51	and the switching path is
0:46:56	where one of those routes may
0:47:00	but at least one of them is wrong.
0:47:07	So, we know what the particular
0:47:11	is that when we look at the routing table,
0:47:14	we don't want to learn the /16
0:47:20	Because if we have these four equal path routes,
0:47:26	we know that they're not
0:47:29	They're not all under the /16.
0:47:34	So, what we simply need to do...
0:47:36	is just disable auto-summary.
0:47:39	So then, it doesn't matter
0:47:43	We'll say, No Auto-Summary.
0:47:51	Then, when we look at the result of this
0:47:56	RIP.
0:48:01	we see now for the 150.10 network,
0:48:06	now, we see the /24 subnets.
0:48:12	So, under normal cases here,
0:48:17	it's pretty much the first thing that you would do when
0:48:23	but within the scope of the lab exam, it really
0:48:27	So, you could theoretically run into a design
0:48:33	Then, you would have to understand
0:48:38	But in the real world design,
0:48:41	If you're running a classless protocol,
0:48:43	you would want it to behave as fully classless.
0:48:47	Now, we'll see if we want to do
0:48:50	define this on the interface
0:48:54	but I it to do it just on its own.
0:48:58	If I want aggregation,
0:49:00	on what interfaces the
0:49:03	and what the actual masks of

Now Viewing

CCIE R&S Advanced Technologies Class v4.5
Title:	CCIE R&S Advanced Technologies Class v4.5
Duration:	81h 02m
The CCIE Routing & Switching Advanced Technologies Class is the first step in understanding CCIE level technologies and is a companion to the Advanced Technologies Lab Workbook. Each technology you need to know for the CCIE Routing & Switching lab will be described in detail using an instructor led hands on demonstration. The class consists of over 80 hours of in depth explanations and examples.
Get instant access to our entire library!
	Sign Up
Download this Course
$299.00	Add to Cart

RIP Overview, RIP Versions, RIP Auto-Summary

Create Bookmark