DSLW Direct / Lite Encapsulation Question

victor_cappuccio · ‎09-04-2005

Hello please I have this confusion with DSLW.

Ok suppose this topology:

Let say:

===========PVC 300 =============

DLCI DLCI

Rtr-A -s0/0 - F-RELAY NETWORK - s0/0 Rtr B

-AAA-- -BBB--

===========PVC 300 =============

(Sorry I’m not good with ASCII drawing, try to think about 2 routers connected to a Frame relay network using a mayor interface and frame-relay map statements)

Now I think that the difference between DSLW Direct and Lite is in the mapping of my DSLW Header that is above the L2 Stuff and my DLCI to the remote PVC, that is

For example

I could have the same dslw remote-peer 0 interface serial 0/0/0 AAA in router A

And in router B I could have dslw remote-peer 0 interface serial 0/0/0 BBB

Now my question is about LLC2 type and the relation between DLSW Direct Encapsulation and Lite Encapsulation (I know that this 2 are Specific L2 Encapsulation)

So in order to bridge non-routable traffic to that kind of tunnel I create with the remote-peer global configuration command , I must do a frame-relay map statement because this is a layer 2 Desktop Encapsulation Protocol Right?

Now If this is correct, it’s on the documentation that says For DSLW Direct Encapsulation:

RtrA

Frame-relay map dslw AAA

RtrB

Frame-relay map dslw BBB

And in for DSLW Lite Encapsulation

RtrA

Frame-relay map llc2 AAA

RtrB

Frame-relay map llc2 BBB

Now my question is which is the difference, I’m confused between the passtru option that suppresses or prevents local Ack of keepalives in the remote-peer DSLW Global command, and the LLC2 encapsulation used in the DSLW Lite?

Georg Pauwen · ‎09-04-2005

Hello,

as you already mentioned, LLC2 is a reliable protocol, so DLSW+ Lite provides local acknowledgement for traffic sent over the WAN.

When you add the 'pass-thru' keyword to your dlsw remote-peer statements for frame relay, the LLC2 header is not added. If you use 'pass-thru', you need to map the DLCI's with the 'frame-relay map dlsw' statement (on multipoint interfaces, which means physical and multipoint subinterfaces).

Is that what you are asking ?

Regards,

GP