Re: ATM PVC : Why does this not work in multipoint subintf?

From: Joe Chang (changjoe@earthlink.net)
Date: Mon Feb 10 2003 - 12:44:25 GMT-3


By coincidence I was reading up on just this topic over the weekend. Check
out:

http://www.cisco.com/univercd/cc/td/doc/product/atm/c8540/12_1/pereg_1/atm_t
ech/basics.htm#1020002

and to configure it:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fwan
_c/wcfatm.htm

As I understand it, aal5snap encapsulation is not natively compatible with
broadcast or multipoint networks. The SAR layer cannot tell if cells
received on the same PVC come from different sources. For point to
multipoint to work, SVCs must be established to each spoke and the hub
interface explicitly configured for multipoint simulation.

----- Original Message -----
From: "sam" <sam@avtechusa.com>
To: <ccielab@groupstudy.com>
Sent: Saturday, February 08, 2003 9:52 PM
Subject: ATM PVC : Why does this not work in multipoint subintf?

> Hi all.
>
> I set up a really simple config. 2 routers with an LS1010 in the middle
>
> I can get this to work with point-2-point subinterface, but when I
> create a multipoint subinterface, my links are down - down. Any help
> would be greatly appreciated.
>
> R1
>
> !
> interface ATM0
> no ip address
> pvc 0/5 qsaal
> !
> pvc 0/16 ilmi
> !
> atm ilmi-keepalive
> !
> interface ATM0.1 multipoint
> ip address 131.1.69.9 255.255.255.0
> pvc 0/34
> protocol ip 131.1.69.6 broadcast
> encapsulation aal5mux ip
>
> R2
>
> !
> interface ATM0
> no ip address
> pvc 0/5 qsaal
> !
> pvc 0/16 ilmi
> !
> no atm ilmi-keepalive
> end
> !
> interface ATM0.1 multipoint
> ip address 131.1.69.6 255.255.255.0
> pvc 0/33
> protocol ip 131.1.69.9 broadcast
> encapsulation aal5mux ip
> !
>
> Thanks in advance!
> Sam Sena
> Avtech Technologies
>
> 4500 New Brunswick Ave
> Piscataway NJ
> (732) 424-8008 (o)
> (732) 424-7388 (f)
> .
.



This archive was generated by hypermail 2.1.4 : Sat Mar 01 2003 - 11:06:17 GMT-3