I have a RIP process running on my three routers.
here is the connection
------r1-----r3-----r2-----
r1 and r3 are running version 2
r2 is running version 1
I have a default-metric of 5 configured under r3's RIP process.
Here is the problem;
Two of the networks (20.0.0.0 and 12.0.0.0) in r1's table have
a metric of 5, one network (210.1.1.0) has a metric of one.
I thought that you use default-metric with the redistribute command to set a
metric and use an offset-list when passing routes that are part of the same
domain.
The question is, why does network 12.0.0.0 and 20.0.0.0 have a metric of
five on r1 and why doesn't the network (210.1.1.0)
also have a metric of 5 like the other two networks?
Anybody know this one?
Below is a config, route table
and a debug of the rip process
for r3 and r1.
r3#s
Building configuration...
Current configuration:
!
version 11.1
service udp-small-servers
service tcp-small-servers
!
hostname r3
!
enable secret 5 $1$5w1e$zSVDgD18hiUshKj.eS5jM.
enable password root
!
ip subnet-zero
no ip domain-lookup
!
key chain time
key 1
key-string up
!
controller T1 1/0/0
!
controller T1 1/0/1
!
interface Loopback1
ip address 20.1.1.1 255.255.255.0
!
interface FastEthernet0/0/0
ip address 100.1.1.1 255.255.255.0
no ip route-cache distributed
no ip mroute-cache
!
interface Serial0/1/0
ip address 33.1.1.1 255.255.255.0
ip rip authentication mode md5
ip rip authentication key-chain time
no ip route-cache distributed
no ip mroute-cache
bandwidth 56
!
interface Serial0/1/1
ip address 133.1.1.1 255.255.255.0
no ip route-cache distributed
no ip mroute-cache
bandwidth 1544
!
interface Serial0/1/2
ip address 210.1.1.1 255.255.255.0
no ip route-cache distributed
no ip mroute-cache
bandwidth 56
clockrate 56000
!
interface Serial0/1/3
ip address 11.1.1.1 255.255.255.0
no ip route-cache distributed
no ip mroute-cache
bandwidth 56
clockrate 56000
!
interface TokenRing1/1/0
no ip address
no ip route-cache distributed
no ip mroute-cache
shutdown
!
interface TokenRing1/1/1
no ip address
no ip route-cache distributed
no ip mroute-cache
shutdown
!
interface TokenRing1/1/2
no ip address
no ip route-cache distributed
no ip mroute-cache
shutdown
!
interface TokenRing1/1/3
no ip address
no ip route-cache distributed
no ip mroute-cache
shutdown
!
interface ATM2/0/0
ip address 13.1.1.1 255.255.255.0
no ip route-cache distributed
no ip mroute-cache
map-group 2
atm pvc 1 1 32 aal5snap
!
interface FastEthernet2/1/0
ip address 12.1.2.1 255.255.255.0
no ip route-cache distributed
no ip mroute-cache
!
interface ATM3/0/0
ip address 12.1.1.1 255.255.255.0
no ip route-cache distributed
no ip mroute-cache
map-group 1
atm clock INTERNAL
atm pvc 1 1 33 aal5snap
!
router rip
version 2
timers basic 5 15 15 30
network 12.0.0.0
network 20.0.0.0
network 33.0.0.0
network 210.1.1.0
default-metric 5
!
ip classless
!
!
map-list 1
ip 12.1.1.2 atm-vc 1 broadcast
!
map-list 2
ip 13.1.1.2 atm-vc 1 broadcast
logging buffered
access-list 1 permit 210.1.1.0 0.0.0.255
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
password root
login
!
end
r3#sir
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate
default
U - per-user static route
Gateway of last resort is not set
100.0.0.0/24 is subnetted, 1 subnets
C 100.1.1.0 is directly connected, FastEthernet0/0/0
33.0.0.0/24 is subnetted, 1 subnets
C 33.1.1.0 is directly connected, Serial0/1/0
R 201.1.1.0/24 [120/1] via 33.1.1.2, 00:00:04, Serial0/1/0
20.0.0.0/24 is subnetted, 1 subnets
C 20.1.1.0 is directly connected, Loopback1
11.0.0.0/24 is subnetted, 1 subnets
C 11.1.1.0 is directly connected, Serial0/1/3
12.0.0.0/24 is subnetted, 1 subnets
C 12.1.1.0 is directly connected, ATM3/0/0
133.1.0.0/24 is subnetted, 1 subnets
C 133.1.1.0 is directly connected, Serial0/1/1
C 210.1.1.0/24 is directly connected, Serial0/1/2
r3#
r3#drp
RIP protocol debugging is on
r3#
RIP: ignored v1 packet from 210.1.1.2 (illegal version)
RIP: received packet with MD5 authentication
RIP: received v2 update from 33.1.1.2 on Serial0/1/0
201.1.1.0/24 -> 0.0.0.0 in 1 hops
RIP: sending v2 update to 224.0.0.9 via Serial0/1/0 (33.1.1.1)
20.0.0.0/8 -> 0.0.0.0, metric 5, tag 0
12.0.0.0/8 -> 0.0.0.0, metric 5, tag 0
210.1.1.0/24 -> 0.0.0.0, metric 1, tag 0
RIP: sending v2 update to 224.0.0.9 via Serial0/1/2 (210.1.1.1)
33.0.0.0/8 -> 0.0.0.0, metric 5, tag 0
201.1.1.0/24 -> 0.0.0.0, metric 2, tag 0
20.0.0.0/8 -> 0.0.0.0, metric 5, tag 0
12.0.0.0/8 -> 0.0.0.0, metric 5, tag 0
RIP: sending v2 update to 224.0.0.9 via ATM3/0/0 (12.1.1.1)
12.1.1.0/24 -> 0.0.0.0, metric 1, tag 0
33.0.0.0/8 -> 0.0.0.0, metric 5, tag 0
201.1.1.0/24 -> 0.0.0.0, metric 2, tag 0
20.0.0.0/8 -> 0.0.0.0, metric 5, tag 0
210.1.1.0/24 -> 0.0.0.0, metric 1, tag 0
RIP: sending v2 update to 224.0.0.9 via Loopback1 (20.1.1.1)
33.0.0.0/8 -> 0.0.0.0, metric 5, tag 0
201.1.1.0/24 -> 0.0.0.0, metric 2, tag 0
12.0.0.0/8 -> 0.0.0.0, metric 5, tag 0
210.1.1.0/24 -> 0.0.0.0, metric 1, tag 0
RIP: ignored v2 packet from 20.1.1.1 (sourced from one of our addresses)
RIP: ignored v1 packet from 210.1.1.2 (illegal version)
RIP: sending v2 update to 224.0.0.9 via Serial0/1/0 (33.1.1.1)
20.0.0.0/8 -> 0.0.0.0, metric 5, tag 0
12.0.0.0/8 -> 0.0.0.0, metric 5, tag 0
210.1.1.0/24 -> 0.0.0.0, metric 1, tag 0
RIP: sending v2 update to 224.0.0.9 via Serial0/1/2 (210.1.1.1)
33.0.0.0/8 -> 0.0.0.0, metric 5, tag 0
201.1.1.0/24 -> 0.0.0.0, metric 2, tag 0
20.0.0.0/8 -> 0.0.0.0, metric 5, tag 0
12.0.0.0/8 -> 0.0.0.0, metric 5, tag 0
RIP: sending v2 update to 224.0.0.9 via ATM3/0/0 (12.1.1.1)
12.1.1.0/24 -> 0.0.0.0, metric 1, tag 0
33.0.0.0/8 -> 0.0.0.0, metric 5, tag 0
201.1.1.0/24 -> 0.0.0.0, metric 2, tag 0
20.0.0.0/8 -> 0.0.0.0, metric 5, tag 0
210.1.1.0/24 -> 0.0.0.0, metric 1, tag 0
RIP: sending v2 update to 224.0.0.9 via Loopback1 (20.1.1.1)
33.0.0.0/8 -> 0.0.0.0, metric 5, tag 0
201.1.1.0/24 -> 0.0.0.0, metric 2, tag 0
12.0.0.0/8 -> 0.0.0.0, metric 5, tag 0
210.1.1.0/24 -> 0.0.0.0, metric 1, tag 0
RIP: ignored v2 packet from 20.1.1.1 (sourced from one of our addresses)
RIP: received packet with MD5 authentication
RIP: received v2 update from 33.1.1.2 on Serial0/1/0
201.1.1.0/24 -> 0.0.0.0 in 1 hopsu
All possible debugging has been turned off
r3#
r1#s
Building configuration...
Current configuration:
!
version 12.0
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname r1
!
!
ip subnet-zero
no ip domain-lookup
!
key chain time
key 1
key-string up
!
!
!
!
!
interface Loopback1
ip address 201.1.1.1 255.255.255.0
no ip directed-broadcast
!
interface Ethernet0/0
ip address 100.1.1.3 255.255.255.0
no ip directed-broadcast
!
interface Serial0/0
bandwidth 56
ip address 33.1.1.2 255.255.255.0
no ip directed-broadcast
ip rip authentication mode md5
ip rip authentication key-chain time
no ip mroute-cache
no fair-queue
clockrate 56000
!
interface Ethernet0/1
no ip address
no ip directed-broadcast
shutdown
!
interface Serial0/1
bandwidth 1544
ip address 133.1.1.2 255.255.255.0
no ip directed-broadcast
clockrate 56000
!
router rip
version 2
timers basic 5 15 15 30
network 33.0.0.0
network 201.1.1.0
!
ip classless
!
!
!
line con 0
exec-timeout 0 0
transport input none
line aux 0
line vty 0 4
login
!
no scheduler allocate
end
r1#
r1#sir
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate
default
U - per-user static route, o - ODR
Gateway of last resort is not set
100.0.0.0/24 is subnetted, 1 subnets
C 100.1.1.0 is directly connected, Ethernet0/0
33.0.0.0/24 is subnetted, 1 subnets
C 33.1.1.0 is directly connected, Serial0/0
C 201.1.1.0/24 is directly connected, Loopback1
R 20.0.0.0/8 [120/5] via 33.1.1.1, 00:00:03, Serial0/0
R 12.0.0.0/8 [120/5] via 33.1.1.1, 00:00:03, Serial0/0
133.1.0.0/24 is subnetted, 1 subnets
C 133.1.1.0 is directly connected, Serial0/1
R 210.1.1.0/24 [120/1] via 33.1.1.1, 00:00:03, Serial0/0
r1#
r1#drp
RIP protocol debugging is on
r1#u
03:23:07: RIP: received packet with MD5 authentication
03:23:07: RIP: received v2 update from 33.1.1.1 on Serial0/0
03:23:07: 20.0.0.0/8 -> 0.0.0.0 in 5 hops
03:23:07: 12.0.0.0/8 -> 0.0.0.0 in 5 hops
03:23:07: 210.1.1.0/24 -> 0.0.0.0 in 1 hops
03:23:07: RIP: sending v2 update to 224.0.0.9 via Serial0/0 (33.1.1.2)
03:23:07: 201.1.1.0/24 -> 0.0.0.0, metric 1, tag 0
03:23:07: RIP: sending v2 update to 224.0.0.9 via Loopback1 (201.1.1.1)
03:23:07: 33.0.0.0/8 -> 0.0.0.0, metric 1, tag 0
03:23:07: 20.0.0.0/8 -> 0.0.0.0, metric 6, tag 0
03:23:07: 12.0.0.0/8 -> 0.0.0.0, metric 6, tag 0
03:23:07: 210.1.1.0/24 -> 0.0.0.0, metric 2, tag 0
03:23:07: RIP: ignored v2 packet from 201.1.1.1 (sourced from one of our
addresses)
03:23:12: RIP: received packet with MD5 authentication
03:23:12: RIP: received v2 update from 33.1.1.1 on Serial0/0
03:23:12: 20.0.0.0/8 -> 0.0.0.0 in 5 hops
03:23:12: 12.0.0.0/8 -> 0.0.0.0 in 5 hops
03:23:12: 210.1.1.0/24 -> 0.0.0.0 in 1 hops
03:23:12: RIP: sending v2 update to 224.0.0.9 via Serial0/0 (33.1.1.2)
03:23:12: 201.1.1.0/24 -> 0.0.0.0, metric 1, tag 0
03:23:12: RIP: sending v2 update to 224.0.0.9 via Loopback1 (201.1.1.1)
03:23:12: 33.0.0.0/8 -> 0.0.0.0, metric 1, tag 0
03:23:12: 20.0.0.0/8 -> 0.0.0.0, metric 6, tag 0
03:23:12: 12.0.0.0/8 -> 0.0.0.0, metric 6, tag 0
03:23:12: 210.1.1.0/24 -> 0.0.0.0, metric 2, tag 0
03:23:12: RIP: ignored v2 packet from 201.1.1.1 (sourced from one of our
addresses)
03:23:16: RIP: received packet with MD5 authentication
03:23:16: RIP: received v2 update from 33.1.1.1 on Serial0/0
03:23:16: 20.0.0.0/8 -> 0.0.0.0 in 5 hops
03:23:16: 12.0.0.0/8 -> 0.0.0.0 in 5 hops
03:23:16: 210.1.1.0/24 -> 0.0.0.0 in 1 hops
03:23:16: RIP: sending v2 update to 224.0.0.9 via Serial0/0 (33.1.1.2)
03:23:16: 201.1.1.0/24 -> 0.0.0.0, metric 1, tag 0
03:23:16: RIP: sending v2 update to 224.0.0.9 via Loopback1 (201.1.1.1)
03:23:16: 33.0.0.0/8 -> 0.0.0.0, metric 1, tag 0
03:23:16: 20.0.0.0/8 -> 0.0.0.0, metric 6, tag 0
03:23:16: 12.0.0.0/8 -> 0.0.0.0, metric 6, tag 0
03:23:16: 210.1.1.0/24 -> 0.0.0.0, metric 2, tag 0
03:23:16: RIP: ignored v2 packet from 201.1.1.1 (sourced from one of our
addresses)
All possible debugging has been turned off
r1#
routers --------r1--------r3---------r2---------
Networks 201 33 210
version 2 2 2 1
the version between r3 and r2 is v2 on the r3 side
and v1 on the r2 side
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=25933&t=25933
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
