RIPv2 done!
So finally I was able to finish RIPv2. I went through the UniverCD and read RIPv2 and then took some notes. I will post my notes about RIPv2 first followed by EIGRP in the next post.
Doesn’t matter which routing protocol you are working with, “show ip protocols” is your friend. It will display tons of information more than you will ever need.
“Flash-update-threshold” command suppresses flash updates when the arrival of a regularly scheduled periodic update matches, or is less than the number of seconds (0-30) that is configured.
RIPv2 supports two modes of authentication on an interface, plain text and md5. Default authentication in every RIPv2 packet is plain text. Read more
Narbik’s Soup-to-Nuts Workbook RIPv2 Lab 6
“Lab 6 - Advanced RIPv2 configuration” was a very interesting lab. I actually got stuck on Task 1 that required that I configure RIPv2 on the ethernet segment. I thought it was funny that it stated if I see R1’s loopback on R2 then the configuration is successful. I thought to myself, that shouldnt take more than a minute. Well I was wrong. I didn’t pay attention the the ip addressing and it WAS NOT THE SAME! After clearing ip routing tables 5 times I said to myself: “Man this must be something tricky”. Well looked up in the answers and guess what? There is a whole paragraph on it in the docCD.
Narbik’s Soup-to-Nuts Workbook RIPv2 Lab 5
“Lab 5 - Filtering routes” requires that we use router filtering to filter routes out. Task 1 requires use to filter the odd numbered subnets so R1 only receives even numbered subnets. I had to look this up since this was totally new to me. Let me list the example out of Narbik’s book with my own solution so you can understand it.
Narbik’s Soup-to-Nuts Workbook RIPv2 Lab 4
“Lab 4 - Configuring Default routes” asks us to not configure any routing protocols on R1 and use a default route pointing towards R2. Then configure a static route on R2 for R1’s loopback. Then we were asked to inject a default route into the RIP domain so that other routers can get to R1’s loopback.
Narbik’s Soup-to-Nuts Workbook RIPv2 Lab 3
“Lab 3 - Configuring RIPv2 Updates” builds on Lab 1 where we configured a basic network and advertised all the directly connected subnets including loopbacks. As we know that by default, RIPv2 neighbors use multicast address of 224.0.0.9 to exchange updates. This can be changed to either unicast or broadcast behavior. Task 2 requires that R2 and R3 should exchange their updates using unicast. We use the “neighbor” command under the RIPv2 process to send updates via unicast to the neighbor’s IP address. We also need to make sure that we use “passive-interface” command for fastethernet0/0 otherwise RIPv2 will send two updates, one unicast and one multicast.
Narbik’s Soup-to-Nuts Workbook RIPv2 Lab 2
“Lab 2: RIPv2 Authentication” asks to configure both clear text and MD5 authentication between R1 R2 R3 and R4. I was able to look this up from the docCD.
Enabling RIP Authentication
RIP Version 1 does not support authentication. If you are sending and receiving RIP Version 2 packets, you can enable RIP authentication on an interface.
The key chain determines the set of keys that can be used on the interface. If a key chain is not configured, no authentication is performed on that interface, not even the default authentication.
We support two modes of authentication on an interface for which RIP authentication is enabled: plain text authentication and MD5 authentication. The default authentication in every RIP Version 2 packet is plain text authentication. Read more
Narbik’s Soup-to-Nuts Workbook RIPv2 Lab 1
“Lab 1 - Configuring RIPv2″ starts off as a basic RIPv2 lab that involves 4 routers R1, R2, R3 and R4. R1 & R2 and R3 & R4 have a frame-relay point-to-point connections between them. R2 & R3 are connected via a switch.
Loading ...