From: Chuck Larrieu (chuck@xxxxxxxxxxxxx)
Date: Mon Feb 26 2001 - 04:04:06 GMT-3
Last report of the evening.
Maybe a bit basic for this august group. But I have completed my studies of
various routing protocols over a frame relay hub and spoke. Found some
interesting behaviours.
OSPF - well documented issues, as found both in Caslow and Bootcamp Lab 1.
No need to repeat.
EIGRP, IGRP, and RIP - all behave more or less the same way. Split horizon
must be disabled on the hub interface. Using only native inverse arp, all
routes show up properly in all router tables. The next hop address is the
frame port address of the hub router. pinging can occur using extended ping
with any connected interface as the source except for the frame interface.
Otherwise layer two debugs show that frame relay has no map for the
destination address. I personally found this interesting. I suspect it may
have something to do with the classful nature of EIGRP, IGRP, and RIP. I
also presume that the solution to the problem lies with static frame maps.
RIP version 2 seems to behave a lot like OSPF. The next hop address in the
routing tables is that of the source router frame port ip address. I am
assuming that the solution to the problem involves local policy routing, as
it did in the bootcamp lab.
Chuck
----------------------
I am Locutus, a CCIE Lab Proctor. Xx_Brain_dumps_xX are futile. Your life as
it has been is over ( if you hope to pass ) From this time forward, you will
study US!
( apologies to the folks at Star Trek TNG )
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:29:01 GMT-3