www.howtonetwork.org

CCNA & CCNP Certifcation Training

  • About
  • Contact
  • FAQ
  • Join
  • Home
  • CCNA
    • ICND1
    • ICND2
    • 101 CCNA LABS
  • CCNP
    • ROUTE
    • SWITCH
    • TSHOOT
    • 101 CCNP LABS
  • CompTIA
    • Security+
    • Network+
  • Design
    • CCDA
    • CCDP
You are here: Home / 101 CCNA LABS / IP Routing / Lab 038: Passive Interfaces for RIPv2 Updates

Lab 038: Passive Interfaces for RIPv2 Updates

Lab 38:

Passive Interfaces for RIPv2 Updates

Lab Objective:

The objective of this lab exercise is for you to learn and understand how to prevent RIPv2 from sending unnecessary updates by using passive interfaces.

Lab Purpose:

Preventing unnecessary RIPv2 updates using passive interfaces is a fundamental skill. By default, RIPv2 sends updates via Multicast on all interfaces for which RIPv2 has been enabled. For example, it is not possible to ever have another device connected to a Loopback interface, so it is a waste of router processing power to have RIPv2 continuously send updates to a Loopback interface. As a Cisco engineer, as well as in the Cisco CCNA exam, you will be expected to know how to prevent RIPv2 sending unnecessary updates.

Certification Level:

This lab is suitable for CCNA certification exam preparation

Lab Difficulty:

This lab has a difficulty rating of 7/10

Readiness Assessment:

When you are ready for your certification exam, you should complete this lab in no more than 10 minutes

Lab Topology:

Please use the following topology to complete this lab exercise:

101labs_fig35

Task 1:

This lab will only use 2 routers. Configure the hostnames on routers R1 and R2 as illustrated in the topology.

Task 2:

Configure a back-to-back Serial connection between R1 and R2. Configure the DCE interface Serial0/0 in R2 to provide clocking to R1 at a clock speed of 2Mbps.

Task 3:

Configure IP addresses 192.168.0.1/30 and 192.168.0.2/30 on R1 and R2 Serial0/0 interfaces respectively. Configure the Loopback interfaces on R1 with the IP addresses illustrated in the topology. Enable RIPv2 for the Serial0/0 interface on R1 and the Loopback subnets.

Task 4:

First, use the show ip protocols command to see the interfaces on which RIPv2 is sending updates. Next, enable debugging on R1 and verify that RIPv2 updates are being sent on all RIPv2-enabled interfaces. When you have verified this, disable debugging.

Task 5:

Prevent RIPv2 from sending updates on the Loopback interfaces. Verify your configuration by enabling debugging. Disable debugging when done.

Prev

Next

About Us

This is a free bonus site for members of www.howtonetwork.com

Copyright

The content on this copyright Reality Press Ltd.
Copyright Reality Press Ltd.