I have notice something interesting when doing a rip scenario on a
frame-relay hub-spoke setup. I had just turned off split-horizon on the hub.
When I did a 'ip route clear *' on one of the spokes to force the removal of
the rip routes, I noticed the following debug trace on this spoke. Ie. the
hub 172.16.0.1 replied to a rip route query, even though this broke the
split-horizon rule.
RIP: sending general request on Serial0.1 to 255.255.255.255
RIP: sending general request on Serial0.1 to 224.0.0.9
RIP: received v1 update from 172.16.0.1 on Serial0.1
172.16.0.0 in 1 hops
1.0.0.0 in 2 hops
Lateron, rip entries are getting old and go through proper hold-down and
flush. See below
R 1.0.0.0/8 [120/2] via 172.16.0.1, 00:01:47, Serial0.1
172.16.0.0/24 is subnetted, 1 subnets
C 172.16.0.0 is directly connected, Serial0.1
Is this proper behaviour? Wouldn't this allow for an infinity-race for a
short time?
(all routers are 2500 series, running 11.2 desktop)
Thanks,
Johan
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=3070&t=3070
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
