From: Narvaez, Pablo (Pablo.Narvaez@xxxxxxxxxxxxx)
Date: Sat Apr 06 2002 - 01:48:50 GMT-3
Thanks a lot Mamoor, you just saved me from doing more research ... I have just
a little time before the lab!
-----Original Message-----
From: Ahmed Mamoor Amimi [mailto:mamoor@ieee.org]
Sent: Viernes, 05 de Abril de 2002 10:13 p.m.
To: Lupi, Guy; ccielab@groupstudy.com
Subject: Re: DLSW in frame-relay
Thankyou very much Lupi. I was doing promiscuous at one side and it was not
connecting. i then statically also put a remote statement on ther side and
it worked. .... here are config similar to urs :
r1-------r2
r1:
dlsw local-peer peer-id 10.13.1.1 group 2 promiscuous
dlsw remote-peer 0 frame-relay interface Serial0.2 103
r2:
dlsw local-peer peer-id 10.13.1.1 group 2 promiscuous
dlsw remote-peer 0 frame-relay interface Serial0.2 103
r1#sh dlsw peers
Peers: state pkts_rx pkts_tx type drops ckts TCP
uptime
LLC2 Se0.2 103 CONNECT 9 9 conf 0 0 -
00:03:01
Total number of connected peers: 1
Total number of connections: 1
r1#
Thanks for pushing me to do that again and it works......
People usually left thinks and feel failed when they are at the end of
it..... and i was doing the same. thanks again.
Pablo u should also try this ....
-Mamoor
----- Original Message -----
From: Lupi, Guy <Guy.Lupi@eurekaggn.com>
To: 'Ahmed Mamoor Amimi ' <mamoor@ieee.org>; <ccielab@groupstudy.com>
Sent: Saturday, April 06, 2002 8:51 AM
Subject: RE: DLSW in frame-relay
> I believe that the theory is that a point-to-point subinterface cannot
have
> more than one dlci, therefore by default everything is mapped to it. I
have
> this working, here are my configs. Maybe you mistyped something?
>
> R2
>
> dlsw local-peer peer-id 172.16.32.3
> dlsw remote-peer 0 frame-relay interface Serial0.1 233
> !
> interface Ethernet0
> no ip address
> shutdown
> !
> interface Serial0
> no ip address
> encapsulation frame-relay
> no fair-queue
> !
> interface Serial0.1 point-to-point
> ip address 172.16.32.2 255.255.255.0
> frame-relay interface-dlci 233
>
> r2#sh dlsw peer
> Peers: state pkts_rx pkts_tx type drops ckts TCP
> uptime
> LLC2 Se0.1 233 CONNECT 20 20 conf 0 0 -
> 00:09:33
> Total number of connected peers: 1
> Total number of connections: 1
>
> r2#
>
>
>
> R3
>
> dlsw local-peer peer-id 172.16.32.3
> dlsw remote-peer 0 frame-relay interface Serial0.1 332
> !
> interface Serial0
> no ip address
> encapsulation frame-relay
> !
> interface Serial0.1 point-to-point
> ip address 172.16.32.3 255.255.255.0
> frame-relay interface-dlci 332
>
> r3#sh dlsw peer
> Peers: state pkts_rx pkts_tx type drops ckts TCP
> uptime
> LLC2 Se0.1 332 CONNECT 22 22 conf 0 0 -
> 00:10:32
> Total number of connected peers: 1
> Total number of connections: 1
>
> r3#
>
>
> -----Original Message-----
> From: Ahmed Mamoor Amimi
> To: ccielab@groupstudy.com
> Sent: 4/5/2002 10:15 PM
> Subject: DLSW in frame-relay
>
> When doing as under :
> dlsw remote-peer 0 frame-relay interface Serial1.1 301
>
>
> But for this we also have to map dlsw over frame-relay map :
>
> But what happened when the link is p-t-p sub-interface and that dont
> allow to
> map anything except
>
> frame-relay interface dlci 301
>
> How can we map llc2 or dlsw over it. my dlsw peers are not getting
> connected.
>
> the last line of debug says :
> 10:11:57: DLSw: LLC2 peer aborting connection for peer on interface
> Serial1
>
>
> My config is as like : r1 ------- r2
>
> Both r1 and r2 are using sub-interface and p-t-p. How we are going to
> add the
> dlsw map statement as the dlsw is not connecting across the frame-relay.
>
>
> -Mamoor
>
>
>
> the
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:57 GMT-3