From: giuks (giuliano.barros@gmail.com)
Date: Sun Dec 28 2008 - 15:17:01 ARST
Folks,
I was doing "IE R&S Wok Vol1 4.1 - RIP V1 Contiguous Netwoks".
Everything worked, but this strange behaviour.
1.0.0.1 (FA0/0) R1 (SE1/0) 12.0.0.1 -----12.0.0.2 (SE1/0) R2 (FA0/0) 2.0.0.2
As the workbook shows and I knew... R1 should advertise 2.0.0.0 with metric
2 and R2 should advertise 1.0.0.0 with metric 2, but they re advert to each
other the same routes with metric 1, without add 1 hop. There were other
behaviours too.
I looked for a explanation and did find anything. So I did some tests.
With RIP V2 auto-sum, the problem is worse because each router adv the
fast0/0 net with 2 hops to the fa0/0 itself.
With RIP V2 no auto-sum, the problem is solved.
With RIP V1 and all nets with the same primary network, it does not happen
and works fine.
It seems like a bug. Did somebody see this before? Follow the logs.
Thks,
giuks
Both routers with dynamips = IOS (tm) 3600 Software (C3640-JK9O3S-M),
Version 12.3(26), RELEASE SOFTWARE (fc2)
###################################### Rack1R1#
Rack1R1#
interface FastEthernet0/0
ip address 1.0.0.1 255.255.0.0
duplex auto
speed auto
end
interface Serial1/0
ip address 12.0.0.1 255.255.0.0
encapsulation frame-relay
serial restart-delay 0
frame-relay map ip 12.0.0.2 102 broadcast
end
router rip
version 1
network 1.0.0.0
network 12.0.0.0
Rack1R1#sh ip route
Gateway of last resort is not set
1.0.0.0/16 is subnetted, 1 subnets
C 1.0.0.0 is directly connected, FastEthernet0/0
R 2.0.0.0/8 [120/1] via 12.0.0.2, 00:00:07, Serial1/0
12.0.0.0/16 is subnetted, 1 subnets
C 12.0.0.0 is directly connected, Serial1/0
Rack1R1#sh ip rip data
1.0.0.0/8 auto-summary
1.0.0.0/16 directly connected, FastEthernet0/0
2.0.0.0/8 auto-summary
2.0.0.0/8
[1] via 12.0.0.2, 00:00:08, Serial1/0
12.0.0.0/8 auto-summary
12.0.0.0/16 directly connected, Serial1/0
Rack1R1#debu ip rip
RIP protocol debugging is on
*Mar 1 02:25:55.495: RIP: sending v1 update to 255.255.255.255 via
Serial1/0 (12.0.0.1)
*Mar 1 02:25:55.495: RIP: build update entries
*Mar 1 02:25:55.499: network 1.0.0.0 metric 1
*Mar 1 02:25:55.499: network 2.0.0.0 metric 1
<--------------------------
*Mar 1 02:25:55.503: subnet 12.0.0.0 metric 1
*Mar 1 02:25:55.643: RIP: sending v1 update to 255.255.255.255 via
FastEthernet0/0 (1.0.0.1)
*Mar 1 02:25:55.643: RIP: build update entries
*Mar 1 02:25:55.647: network 2.0.0.0 metric 1
<--------------------------
*Mar 1 02:25:55.647: network 12.0.0.0 metric 1
*Mar 1 02:25:58.131: RIP: received v1 update from 12.0.0.2 on Serial1/0
*Mar 1 02:25:58.135: 1.0.0.0 in 1 hops <--------------------------
*Mar 1 02:25:58.135: 2.0.0.0 in 1 hops
*Mar 1 02:25:58.139: 12.0.0.0 in 1 hops
Rack1R1#un all
###################################### Rack1R2#
Rack1R2#
interface FastEthernet0/0
ip address 2.0.0.2 255.255.0.0
duplex auto
speed auto
end
interface Serial1/0
ip address 12.0.0.2 255.255.0.0
encapsulation frame-relay
serial restart-delay 0
frame-relay map ip 12.0.0.1 201 broadcast
end
router rip
version 1
network 2.0.0.0
network 12.0.0.0
Rack1R2#sh ip route
Gateway of last resort is not set
R 1.0.0.0/8 [120/1] via 12.0.0.1, 00:00:14, Serial1/0
2.0.0.0/16 is subnetted, 1 subnets
C 2.0.0.0 is directly connected, FastEthernet0/0
12.0.0.0/16 is subnetted, 1 subnets
C 12.0.0.0 is directly connected, Serial1/0
Rack1R2#sh ip rip data
1.0.0.0/8 auto-summary
1.0.0.0/8
[1] via 12.0.0.1, 00:00:12, Serial1/0
2.0.0.0/8 auto-summary
2.0.0.0/16 directly connected, FastEthernet0/0
12.0.0.0/8 auto-summary
12.0.0.0/16 directly connected, Serial1/0
Rack1R2#
*Mar 1 02:30:18.951: RIP: sending v1 update to 255.255.255.255 via
FastEthernet0/0 (2.0.0.2)
*Mar 1 02:30:18.951: RIP: build update entries
*Mar 1 02:30:18.955: network 1.0.0.0 metric 1
<--------------------------
*Mar 1 02:30:18.955: network 12.0.0.0 metric 1
Rack1R2#
*Mar 1 02:30:34.247: RIP: sending v1 update to 255.255.255.255 via
Serial1/0 (12.0.0.2)
*Mar 1 02:30:34.247: RIP: build update entries
*Mar 1 02:30:34.251: network 1.0.0.0 metric 1
<--------------------------
*Mar 1 02:30:34.251: network 2.0.0.0 metric 1
*Mar 1 02:30:34.255: subnet 12.0.0.0 metric 1
*Mar 1 02:30:35.087: RIP: received v1 update from 12.0.0.1 on Serial1/0
*Mar 1 02:30:35.091: 1.0.0.0 in 1 hops
*Mar 1 02:30:35.091: 2.0.0.0 in 1 hops <--------------------------
*Mar 1 02:30:35.091: 12.0.0.0 in 1 hops
Rack1R2#un all
#########################################################
RIP V2 auto-summary default
RIP V2
Rack1R2(config-if)#
*Mar 1 03:13:04.203: RIP: received v2 update from 12.0.0.1 on Serial1/0
*Mar 1 03:13:04.207: 1.0.0.0/8 via 0.0.0.0 in 1 hops
*Mar 1 03:13:04.207: 2.0.0.0/8 via 0.0.0.0 in 1 hops
<--------------------------
*Mar 1 03:13:04.211: 12.0.0.0/16 via 0.0.0.0 in 1 hops
*Mar 1 03:13:17.159: RIP: sending v2 update to 224.0.0.9 via Serial1/0
(12.0.0.2)
*Mar 1 03:13:17.159: RIP: build update entries
*Mar 1 03:13:17.163: 1.0.0.0/8 via 0.0.0.0, metric 1, tag 0
<--------------------------
*Mar 1 03:13:17.163: 2.0.0.0/8 via 0.0.0.0, metric 1, tag 0
*Mar 1 03:13:17.163: 12.0.0.0/16 via 0.0.0.0, metric 1, tag 0
Rack1R2(config-if)#do un
*Mar 1 03:13:24.239: RIP: sending v2 update to 224.0.0.9 via
FastEthernet0/0 (2.0.0.2) <-------------- "FastEthernet0/0 (2.0.0.2) "
*Mar 1 03:13:24.239: RIP: build update entries
*Mar 1 03:13:24.243: 1.0.0.0/8 via 0.0.0.0, metric 1, tag 0
<--------------------------
*Mar 1 03:13:24.243: 2.0.0.0/8 via 0.0.0.0, metric 2, tag 0
<-------------------------- 2 ??? It happens with 1.0.0.0 at R1 fa0/0
*Mar 1 03:13:24.247: 12.0.0.0/8 via 0.0.0.0, metric 1, tag 0
Rack1R2(config-if)#do un all
###################################################################
RIP V2 no auto-summary
Rack1R2(config-router)#
*Mar 1 03:19:07.643: RIP: sending v2 update to 224.0.0.9 via
FastEthernet0/0 (2.0.0.2)
*Mar 1 03:19:07.643: RIP: build update entries
*Mar 1 03:19:07.643: 1.0.0.0/16 via 0.0.0.0, metric 2, tag 0
<------------------- Now it is correct
*Mar 1 03:19:07.643: 12.0.0.0/16 via 0.0.0.0, metric 1, tag 0
Rack1R2(config-router)#
*Mar 1 03:19:12.375: RIP: sending v2 update to 224.0.0.9 via Serial1/0
(12.0.0.2)
*Mar 1 03:19:12.375: RIP: build update entries
*Mar 1 03:19:12.379: 1.0.0.0/16 via 12.0.0.1, metric 2, tag 0
<------------------- Now it is correct. The 2.0.0.0 also is advertised by R1
with metric 2.
*Mar 1 03:19:12.379: 2.0.0.0/16 via 0.0.0.0, metric 1, tag 0
*Mar 1 03:19:12.383: 12.0.0.0/16 via 0.0.0.0, metric 1, tag 0
Rack1R2(config-router)#
*Mar 1 03:19:15.631: RIP: received v2 update from 12.0.0.1 on Serial1/0
*Mar 1 03:19:15.635: 1.0.0.0/16 via 0.0.0.0 in 1 hops <---------
2.0.0.0 also is advertised by R1 with metric 2, but does not appear as
received.
*Mar 1 03:19:15.635: 12.0.0.0/16 via 0.0.0.0 in 1 hops
###################################################################
Rack1R1#debu ip rip
RIP protocol debugging is on
Rack1R1#un all
*Mar 1 03:56:41.807: RIP: received v1 update from 10.12.0.2 on Serial1/0
*Mar 1 03:56:41.811: 10.1.0.0 in 2 hops <-------------------
*Mar 1 03:56:41.811: 10.2.0.0 in 1 hops
*Mar 1 03:56:41.815: 10.12.0.0 in 1 hops
Rack1R1#un all
*Mar 1 03:56:45.359: RIP: sending v1 update to 255.255.255.255 via
FastEthernet0/0 (10.1.0.1)
*Mar 1 03:56:45.359: RIP: build update entries
*Mar 1 03:56:45.359: subnet 10.2.0.0 metric 2 <-------------------
*Mar 1 03:56:45.359: subnet 10.12.0.0 metric 1
*Mar 1 03:56:45.575: RIP: sending v1 update to 255.255.255.255 via
Serial1/0 (10.12.0.1)
*Mar 1 03:56:45.575: RIP: build update entries
*Mar 1 03:56:45.579: subnet 10.1.0.0 metric 1
*Mar 1 03:56:45.579: subnet 10.2.0.0 metric 2 <-------------------
*Mar 1 03:56:45.579: subnet 10.12.0.0 metric 1
Rack1R1#un all
Rack1R2#debu ip rip
RIP protocol debugging is on
Rack1R2#un all
*Mar 1 03:55:47.271: RIP: sending v1 update to 255.255.255.255 via
Serial1/0 (10.12.0.2)
*Mar 1 03:55:47.271: RIP: build update entries
*Mar 1 03:55:47.275: subnet 10.1.0.0 metric 2 <-------------------
*Mar 1 03:55:47.275: subnet 10.2.0.0 metric 1
*Mar 1 03:55:47.275: subnet 10.12.0.0 metric 1
*Mar 1 03:55:47.323: RIP: sending v1 update to 255.255.255.255 via
FastEthernet0/0 (10.2.0.2)
*Mar 1 03:55:47.323: RIP: build update entries
*Mar 1 03:55:47.327: subnet 10.1.0.0 metric 2 <-------------------
*Mar 1 03:55:47.327: subnet 10.12.0.0 metric 1
Rack1R2#un all
*Mar 1 03:55:50.671: RIP: received v1 update from 10.12.0.1 on Serial1/0
*Mar 1 03:55:50.675: 10.1.0.0 in 1 hops
*Mar 1 03:55:50.675: 10.2.0.0 in 2 hops <-------------------
*Mar 1 03:55:50.679: 10.12.0.0 in 1 hops
Rack1R2#un all
giuks
-----------------------------------------------------
Giuliano C. G. Barros
giuliano.barros@gmail.com
Cisco Certified Network Professional
-----------------------------------------------------
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Thu Jan 01 2009 - 12:53:10 ARST