From: brian.m.edwards@xxxxxxxxx
Date: Fri Jan 14 2000 - 15:35:56 GMT-3
Did adding eigrp on the R2 interface fix your problem? There is no problem with
using cable ranges over Frame Relay as the one guy suggested.
What if R4 used a point-to-point subinterface? Would that mess up the EIGRP tim
ers and cause the same problem? I have seen this same interface state before an
d I could have sworn that I turned on EIGRP on all the interfaces, but maybe I
missed one.
-----------------------------------------------------
>From CCD AT config guide:
By default, hello packets are sent every 5 seconds. The exception is on low-spe
ed, nonbroadcast, multiaccess (NBMA) media, where the default hello interval is
60 seconds. Low speed is considered to be a rate of T1 or slower, as specified
with the bandwidth interface configuration command. The default hello interval
remains 5 seconds for high-speed NBMA networks. Note that for the purposes of
Enhanced IGRP, Frame Relay and Switched Multimegabit Data Services (SMDS) netwo
rks may or may not be considered to be NBMA. These networks are considered NBMA
if the interface has not been configured to use physical multicasting; otherwi
se they are considered not to be NBMA.
------------------------------------------------------
What does it mean by physical multicasting? How do you turn it on/off? Is the d
efault different for p-t-p subint's vs. phys int's?
-----------------------------------------------------
>From CCD Frame config guide:
Additionally, certain protocols such as AppleTalk and transparent bridging cann
ot be supported on partially meshed networks because they require "split horizo
n," in which a packet received on an interface cannot be transmitted out the sa
me interface even if the packet is received and transmitted on different virtua
l circuits.
------------------------------------------------------
Why does AT "require" split horizon. I think it means RTMP. You can disable spl
it-horizon on AT-EIGRP.
> -----Original Message-----
> From: Ben Rife [SMTP:brife@bignet.net]
> Sent: Thursday, January 13, 2000 11:10 AM
> To: ccielab@groupstudy.com
> Subject: Appletalk and Frame-Relay
>
> I am trying to estab an appletalk (eigrp) connection over frame using IETF e
ncapsulation. I can not get the two routers to verify, and estab. a connection
. Can someone help.
>
> R2#
> appletalk routing eigrp 2
>
> interface Serial0
> ip address 172.17.59.98 255.255.255.240
> encapsulation frame-relay IETF
> ip ospf network broadcast
> ip ospf priority 0
> no ip mroute-cache
> appletalk cable-range 2-2 2.2
> appletalk zone two
> ipx network BBB
> no fair-queue
> frame-relay map appletalk 2.1 101 broadcast IETF
> frame-relay map appletalk 2.4 101 broadcast IETF
> frame-relay map ipx BBB.0000.0000.0001 101 broadcast IETF
> frame-relay map ipx BBB.0000.0000.0004 101 broadcast IETF
> frame-relay map ip 172.17.59.97 101 broadcast IETF
> frame-relay map ip 172.17.59.99 101 broadcast IETF
>
> R4#
> appletalk routing eigrp 4
> interface Serial0.2 multipoint
> ip address 172.17.59.97 255.255.255.240
> no ip directed-broadcast
> ip ospf network broadcast
> ip ospf priority 255
> appletalk cable-range 2-2 2.4
> appletalk zone two
> appletalk protocol eigrp
> no appletalk protocol rtmp
> ipx input-sap-filter 1000
> ipx network BBB
> frame-relay map appletalk 2.2 100 broadcast IETF
> frame-relay map ipx BBB.0000.0000.0001 200 broadcast IETF
> frame-relay map ipx BBB.0000.0000.0002 100 broadcast IETF
> frame-relay map ip 172.17.59.98 100 broadcast IETF
> frame-relay map ip 172.17.59.99 200 broadcast IETF
>
> R4#sh app int s0.2
> Serial0.2 is up, line protocol is up
> AppleTalk port disabled, Acquiring port net information
> AppleTalk cable range is 2-2
> AppleTalk address is 2.4, Valid
> AppleTalk zone is "two"
> Routing protocols enabled: EIGRP
> AppleTalk discarded 14 packets due to output errors
> AppleTalk address gleaning is not supported by hardware>
> AppleTalk route cache is enabled
>
> Thanks, Ben
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:22:44 GMT-3