IEWB Vol2 Task4.1 - RIP domain on R1, R3 and SW1

From: Nitro Drops (nitrodrops@hotmail.com)
Date: Sat Aug 30 2008 - 23:25:30 ART


When configuring RIP process on R1, R3 and SW1. "Passive-interface
default" have been used on both R3 and R1. "No passive interfaces" have
been used on R1 F0/0 and R3 E0/0.
Rack1R3#sh run | begin router rip
router rip
 version 2
 passive-interface default
 no passive-interface Ethernet0/0
 network 163.1.0.0
 no auto-summary
Rack1R1#sh run | begin router rip
router rip
 version 2
 passive-interface default
 no passive-interface FastEthernet0/0
 network 163.1.0.0
 no auto-summary

Qns : How come SW2 still can learn the routes for 163.1.13.0/24 via
both R1 and R3? Even though this subnet 163.1.13.0/24 is not
advertised by both R1 and R3 into RIP domain, as 'passive-interface
default' command is used on both R1 and R3? Understand that this subnet
falls into the major network 163.1.0.0/16. Does it means major network
takes precedence over 'passive-interface default' command?

Rack1SW2#
Rack1SW2#sh ip route rip
     163.1.0.0/16 is variably subnetted, 6 subnets, 2 masks
R 163.1.35.0/24 [120/1] via 163.1.38.3, 00:00:21, FastEthernet1/14
R 163.1.13.3/32 [120/1] via 163.1.18.1, 00:00:08, FastEthernet1/15
R 163.1.12.0/24 [120/1] via 163.1.18.1, 00:00:08, FastEthernet1/15
R 163.1.13.0/24 [120/1] via 163.1.38.3, 00:00:21, FastEthernet1/14
                      [120/1] via 163.1.18.1, 00:00:08, FastEthernet1/15

Rack1SW2#sh ip route 163.1.13.0
Routing entry for 163.1.13.0/24
  Known via "rip", distance 120, metric 1
  Redistributing via rip
  Last update from 163.1.18.1 on FastEthernet1/15, 00:00:00 ago
  Routing Descriptor Blocks:
  * 163.1.38.3, from 163.1.38.3, 00:00:13 ago, via FastEthernet1/14
      Route metric is 1, traffic share count is 1
    163.1.18.1, from 163.1.18.1, 00:00:00 ago, via FastEthernet1/15
      Route metric is 1, traffic share count is 1

Rack1SW2#

CheersNit



This archive was generated by hypermail 2.1.4 : Mon Sep 01 2008 - 08:15:33 ART