DLSW Direct over FR

[thisisshanky]

I am configuring DLSw configuration like this.

R1, R2 R3.

R2 and R1 has peering which needs reliability. So I decided to go for TCP encapsulation.

R2 and R3 has a peering which needs to be done over frame relay (Direct).

There is no peering between R1 and R3.

R1, R2 R3 have PCs in lan segments, which need to communicate via netbios. So Since there is no peering between R1 and R3, I configured R2 as a border peer.

R2

dlsw local-peer peer-id x.x.x.x group 1 border promiscous

dlsw bridge-group 1

int s0/1

frame-relay map dlsw 403

R1

dlsw local-peer peer-id y.y.y.y group 1

dlsw bridge-group 1

dlsw remote-peer 0 tcp x.x.x.x

R2

dlsw local-peer peer-id z.z.z.z group 1

dlsw bridge-group 1

dlsw remote-peer 0 frame-relay interface serial 0/1 304

int s0/1

frame-relay map dlsw 304

403 and 304 are the dlci numbers of the frame-relay connection between R2 and R3. I can see that the R1 and R2 are in connect state.

R2 and R3 are not. Can somebody explain why?

[ciscomoderator]

Since there has been no response to your post, it appears to be either too complex or too rare an issue for other forum members to assist you. If you don't get a suitable response to your post, you may wish to review our resources at the online Technical Assistance Center (http://www.cisco.com/tac) or speak with a TAC engineer. You can open a TAC case online at http://www.cisco.com/tac/caseopen

If anyone else in the forum has some advice, please reply to this thread.

Thank you for posting.

[#3]

Hi,

In order to connect Ethernet segments using Direct FR DLSW you need to use the frame relay map llc2 instead of frame relay map dlsw command , the latter works only for connecting TR LAN's

Yasser Mahmud

AT&T, UK