Home > Articles > Routing Information Protocol (RIPv2)

Routing Information Protocol (RIPv2)

Contents

  1. Lab 1: Configuring RIPv2
  2. Lab 2: Helper Map
  3. Lab 3: RIPv2 Challenge Lab

Chapter Description

The Routing Information Protocol (RIP) is a perfect example of a simple distance vector routing protocol that follows all the standard distance vector designs. In this sample chapter from CCIE Enterprise Infrastructure Foundation, 2nd Edition, you will explore the simplicity of RIP configuration, advanced RIP filtering scenarios, and RIP configuration challenges.

From the Book

CCIE Enterprise Infrastructure Foundation

CCIE Enterprise Infrastructure Foundation, 2nd Edition

$159.99 (Save 20%)

Lab 1: Configuring RIPv2

Lab 1

Click to view larger image

This lab should be conducted on the Enterprise POD.

Lab Setup:

If you are using EVE-NG, and you have imported the EVE-NG topology from the EVE-NG-Topology folder, ignore the following tasks and use Lab 1-Configuring RIPv2 in the RIPv2 folder in EVE-NG.

To copy and paste the initial configurations, go to the Initial-config folder → RIPv2 folder → Lab-1.

Task 1

Configure RIPv2 on all routers and switches. Advertise their directly connected interfaces in this routing domain. These devices should not have a classful nature. If this configuration is successful, the routers and switches should successfully exchange routes.

Use the following policy when configuring this task:

  1. R7 and R1 must use two static routes for reachability.

  2. R1 and R4 must not use a static route(s). R1 cannot use any solution that’s used in the previous policy or the next ones to provide reachability. You are allowed to disable the sanity check.

  3. You cannot use PBR to resolve any of the policies in this task.

  4. The IP addresses configured on all the devices in the topology are correct.

Task 2

  1. Configure R4 such that it sends RIPv2 updates out of its G0/3 interface to a broadcast destination.

    1. Do not change RIP’s version.

  2. Ensure that R1 is configured to send unicast updates to its neighboring router R7.

Task 3

Configure the following loopback interfaces on R3. Starting with network 30.3.0.0/24, this router should only advertise every other third octet network (for example, x.x.0.x, x.x.2.x, x.x.4.x). These are networks 30.3.0.0, 30.3.2.0, 30.3.4.0, 30.3.6.0, 30.3.8.0, and 30.3.10.0/24.

int lo0 = 30.3.0.1 /24

int lo6 = 30.3.6.1 /24

int lo1 = 30.3.1.1 /24

int lo7 = 30.3.7.1 /24

int lo2 = 30.3.2.1 /24

int lo8 = 30.3.8.1 /24

int lo3 = 30.3.3.1 /24

int lo9 = 30.3.9.1 /24

int lo4 = 30.3.4.1 /24

int lo10 = 30.3.10.1 /24

int lo5 = 30.3.5.1 /24

Lab Setup:

If you are using EVE-NG, and you have imported the EVE-NG topology from the EVE-NG-Topology folder, ignore the following tasks.

To copy and paste the initial configurations, go to the Initial-config folder → RIPv2 folder → Lab-1-Task3.

Task 4

Configure the following loopback interfaces on R6. Starting with network 60.6.0.0/24, this router should only advertise every eighth third octet subnet (for example, x.x.0.x, x.x.8.x, x.x.16.x).

int lo0 = 60.6.0.1 /24

int lo6 = 60.6.6.1 /24

int lo1 = 60.6.1.1 /24

int lo7 = 60.6.7.1 /24

int lo2 = 60.6.2.1 /24

int lo8 = 60.6.8.1 /24

int lo3 = 60.6.3.1 /24

int lo9 = 60.6.9.1 /24

int lo4 = 60.6.4.1 /24

int lo10 = 60.6.10.1 /24

int lo5 = 60.6.5.1 /24

Lab Setup:

If you are using EVE-NG, and you have imported the EVE-NG topology from the EVE-NG-Topology folder, ignore the following tasks.

To copy and paste the initial configurations, go to the Initial-config folder → RIPv2 folder → Lab-1-Task4.

Task 5

Configure the following loopback interfaces on R4. This router should be configured such that it only advertises the even-numbered hosts of the odd third octet networks of these loopback interfaces plus all other networks (for example, x.x.1.x, x.x.3.x, x.x.5.x).

Lab Setup:

If you are using EVE-NG, and you have imported the EVE-NG topology from the EVE-NG-Topology folder, ignore the following tasks.

To copy and paste the initial configurations, go to the Initial-config folder → RIPv2 folder → Lab-1-Task5.

int lo1

ip addr 40.4.1.1 255.255.255.0

ip addr 40.4.1.2 255.255.255.255 sec

ip addr 40.4.1.3 255.255.255.255 sec

ip addr 40.4.1.4 255.255.255.255 sec

ip addr 40.4.1.5 255.255.255.255 sec

ip addr 40.4.1.6 255.255.255.255 sec

ip addr 40.4.1.7 255.255.255.255 sec

ip addr 40.4.1.8 255.255.255.255 sec

ip addr 40.4.1.9 255.255.255.255 sec

ip addr 40.4.1.10 255.255.255.255 sec

int lo6

ip addr 40.4.6.1 255.255.255.0

ip addr 40.4.6.2 255.255.255.255 sec

ip addr 40.4.6.3 255.255.255.255 sec

ip addr 40.4.6.4 255.255.255.255 sec

ip addr 40.4.6.5 255.255.255.255 sec

ip addr 40.4.6.6 255.255.255.255 sec

ip addr 40.4.6.7 255.255.255.255 sec

ip addr 40.4.6.8 255.255.255.255 sec

ip addr 40.4.6.9 255.255.255.255 sec

ip addr 40.4.6.10 255.255.255.255 sec

int lo2

ip addr 40.4.2.1 255.255.255.0

ip addr 40.4.2.2 255.255.255.255 sec

ip addr 40.4.2.3 255.255.255.255 sec

ip addr 40.4.2.4 255.255.255.255 sec

ip addr 40.4.2.5 255.255.255.255 sec

ip addr 40.4.2.6 255.255.255.255 sec

ip addr 40.4.2.7 255.255.255.255 sec

ip addr 40.4.2.8 255.255.255.255 sec

ip addr 40.4.2.9 255.255.255.255 sec

ip addr 40.4.2.10 255.255.255.255 sec

int lo7

ip addr 40.4.7.1 255.255.255.0

ip addr 40.4.7.2 255.255.255.255 sec

ip addr 40.4.7.3 255.255.255.255 sec

ip addr 40.4.7.4 255.255.255.255 sec

ip addr 40.4.7.5 255.255.255.255 sec

ip addr 40.4.7.6 255.255.255.255 sec

ip addr 40.4.7.7 255.255.255.255 sec

ip addr 40.4.7.8 255.255.255.255 sec

ip addr 40.4.7.9 255.255.255.255 sec

ip addr 40.4.7.10 255.255.255.255 sec

int lo3

ip addr 40.4.3.1 255.255.255.0

ip addr 40.4.3.2 255.255.255.255 sec

ip addr 40.4.3.3 255.255.255.255 sec

ip addr 40.4.3.4 255.255.255.255 sec

ip addr 40.4.3.5 255.255.255.255 sec

ip addr 40.4.3.6 255.255.255.255 sec

ip addr 40.4.3.7 255.255.255.255 sec

ip addr 40.4.3.8 255.255.255.255 sec

ip addr 40.4.3.9 255.255.255.255 sec

ip addr 40.4.3.10 255.255.255.255 sec

int lo8

ip addr 40.4.8.1 255.255.255.0

ip addr 40.4.8.2 255.255.255.255 sec

ip addr 40.4.8.3 255.255.255.255 sec

ip addr 40.4.8.4 255.255.255.255 sec

ip addr 40.4.8.5 255.255.255.255 sec

ip addr 40.4.8.6 255.255.255.255 sec

ip addr 40.4.8.7 255.255.255.255 sec

ip addr 40.4.8.8 255.255.255.255 sec

ip addr 40.4.8.9 255.255.255.255 sec

ip addr 40.4.8.10 255.255.255.255 sec

int lo4

ip addr 40.4.4.1 255.255.255.0

ip addr 40.4.4.2 255.255.255.255 sec

ip addr 40.4.4.3 255.255.255.255 sec

ip addr 40.4.4.4 255.255.255.255 sec

ip addr 40.4.4.5 255.255.255.255 sec

ip addr 40.4.4.6 255.255.255.255 sec

ip addr 40.4.4.7 255.255.255.255 sec

ip addr 40.4.4.8 255.255.255.255 sec

ip addr 40.4.4.9 255.255.255.255 sec

ip addr 40.4.4.10 255.255.255.255 sec

int lo9

ip addr 40.4.9.1 255.255.255.0

ip addr 40.4.9.2 255.255.255.255 sec

ip addr 40.4.9.3 255.255.255.255 sec

ip addr 40.4.9.4 255.255.255.255 sec

ip addr 40.4.9.5 255.255.255.255 sec

ip addr 40.4.9.6 255.255.255.255 sec

ip addr 40.4.9.7 255.255.255.255 sec

ip addr 40.4.9.8 255.255.255.255 sec

ip addr 40.4.9.9 255.255.255.255 sec

ip addr 40.4.9.10 255.255.255.255 sec

int lo5

ip addr 40.4.5.1 255.255.255.0

ip addr 40.4.5.2 255.255.255.255 sec

ip addr 40.4.5.3 255.255.255.255 sec

ip addr 40.4.5.4 255.255.255.255 sec

ip addr 40.4.5.5 255.255.255.255 sec

ip addr 40.4.5.6 255.255.255.255 sec

ip addr 40.4.5.7 255.255.255.255 sec

ip addr 40.4.5.8 255.255.255.255 sec

ip addr 40.4.5.9 255.255.255.255 sec

ip addr 40.4.5.10 255.255.255.255 sec

int lo10

ip addr 40.4.10.1 255.255.255.0

ip addr 40.4.10.2 255.255.255.255 sec

ip addr 40.4.10.3 255.255.255.255 sec

ip addr 40.4.10.4 255.255.255.255 sec

ip addr 40.4.10.5 255.255.255.255 sec

ip addr 40.4.10.6 255.255.255.255 sec

ip addr 40.4.10.7 255.255.255.255 sec

ip addr 40.4.10.8 255.255.255.255 sec

ip addr 40.4.10.9 255.255.255.255 sec

ip addr 40.4.10.10 255.255.255.255 sec

Task 6

Configure the routers and switches in this routing domain based on the following timers:

  • Periodic updates are sent every 30 seconds.

  • Routers and switches should declare a route invalid after 1.5 minutes.

  • Routers and switches should suppress routing information regarding a better path for 1.5 minutes.

  • Routers and switches should flush routes 30 seconds after they are invalid.

  • Routers and switches should postpone their periodic updates by 100 milliseconds.

Task 7

Since R1 is a very fast router, configure it such that it adds an inter-packet delay of 50 milliseconds between the updates.

Task 8

Configure R2 to set the number of received but not yet processed RIP update packets in the RIP input queue to 100.

Task 9

Configure all routers to suppress a flash update when a topology change occurs 10 seconds before a regular update.

Task 10

Configure R1 and R2 to authenticate their routing updates through their direct connection. Configure these two routers to use the unencrypted key ccie for this purpose.

Task 11

Configure R5, R6, and SW4 to use authentication with the strongest authentication method available to RIPv2. These routers should use Micronic? as their password.

Task 12

Configure R1 to accept existing and future routes that have a prefix length of 10 to 14. These routes should be received from R7 only. Do not use an access list(s) or a neighbor command to accomplish this task.

Task 13

Configure R7 to inject a default route.

Task 14

Configure R4 to filter the default route injected by R7.

Task 15

Configure SW4 such that it always prefers to reach network 10.1.4.0/24 through R6.

  1. SW4 should use R5 when R6 is down.

  2. Restrictions: Do not use an offset list to accomplish this task.

Task 16

Configure SW4 to filter network 50.5.5.0/24. Do not use an access list to accomplish this task.

Task 17

Configure R4 such that it injects a default route into the RIPv2 routing domain.

  1. Restrictions:

    1. This default route should not be given to R6.

    2. Do not configure R6 to accomplish this task. R5 should only have a default route from R4.

Task 18

Configure R3 to summarize its Loopback Lo0–Lo3, Lo30–Lo33 and advertise two summary routes into the RIP routing domain.

Task 19

Configure Lo200 with the IP address 120.2.2.2/24 on SW2. This switch should advertise this network in the RIPv2 routing domain. Configure SW1 such that this network is never advertised to any router downstream/beyond SW4, as those are future devices connected to SW4.

Task 20

Erase the startup configuration of the routers, the startup configuration, and the VLAN.dat file for each switch and reload the devices before proceeding to the next lab.

2. Lab 2: Helper Map | Next Section

Cisco Press Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Cisco Press and its family of brands. I can unsubscribe at any time.

Overview

Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Cisco Press products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@ciscopress.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security

Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children

This site is not directed to children under the age of 13.

Marketing

Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out

Users can always make an informed choice as to whether they should proceed with certain services offered by Cisco Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.ciscopress.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links

This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020