From: Fabrice Bobes (study@6colabs.com)
Date: Fri Mar 21 2003 - 18:27:30 GMT-3
Hello,
My understanding of this problem is that Classical IP with SVC over ATM
(RFC 1577) doesn't support multicast.
Here is an excerpt taken from RFC 1577:
"8. IP Multicast Address
ATM does not support multicast address services, therefore there are
no mappings available from IP multicast addresses to ATM multicast
services.
"
If you configure EIGRP, the neighbor relationship is established and
maintained via Hello packets (224.0.0.10).
Obviously, this is a problem when configuring EIGRP over CLIP and the
hello packets won't keep the link active.
The solution found by Tasuka is to tear down the SVC before the default
idle timeout of 300 seconds. I don't believe it's a satisfactory
solution: when you tear down the SVC, you temporary lose connection.
Another way of fixing the problem is to unicast the hello packets
between the EIGRP neighbors:
Router eigrp 100
neighbor 150.4.100.14 ATM2/0
I hope this helps,
Fabrice Bobes, CCIE #8609
http://www.6CoLabs.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Joe Chang
Sent: Friday, March 21, 2003 10:38 AM
To: Tasuka Amano Hsu; ccielab Groupstudy
Subject: Re: ATM SVC routing exchange!
The default idle-timeout on an SVC is 5 minutes, however the EIGRP
hellos
and BGP keepalives should keep the link active.
----- Original Message -----
From: "Tasuka Amano Hsu" <tasuka@mac.com>
To: "ccielab Groupstudy" <ccielab@groupstudy.com>
Sent: Tuesday, March 18, 2003 10:38 PM
Subject: ATM SVC routing exchange!
> Hi,
> after I configure a ATM connection with SVC with Classical IP,
> and use EIGRP and BGP for routing exchange,
> I found if no traffic pass the ATM SVC path, the path will
disconnected,
> and that make the routing did not keep renew, any method ?
> or that is normal for SVC ?
>
> Best Regards
> Tasuka
This archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:43 GMT-3