From: Joe Chang (changjoe@earthlink.net)
Date: Mon Dec 16 2002 - 14:20:44 GMT-3
From job experience I know that serially attached controllers at frame-relay
connected remote sites should have no problems connecting to their hosts
over TCP transported DLSW. We never had to use FST as the encapsulation.
That job was also my first networking job, so I can't quite remember
anything that could help you any more ( I didn't really know what was going
on at the time anyways). Usually when the circuit is stuck right before
getting connected there's something at the head-end that needs to be
double-checked.
----- Original Message -----
From: "Vinay Arora" <cybervinay@yahoo.com>
To: <ccielab@groupstudy.com>
Sent: Monday, December 16, 2002 9:47 AM
Subject: DLSW across a frame-relay WAN
> I tried to setup a DLSW connection for connecting a IBM controller (5394)
> PU2.1 at remote location to connect to IBM AS400 at the central site.
>
> I could verify the DLSW peers connectivity (show dlsw peers) and MAC
> reachability (show dlsw reach). The Circuit (show dlsw circuit) was in
> ckt_established state and was not getting to connect state. I could see
the
> XID exchange process being exchanged but the connection not getting thru.
>
> I have the exact same config working for another remote site that was on
> normal T1 circuit WAN with ppp encapsulation.
>
> I am using TCP as transport for the DLSW, but later I searched on CCO and
> found a sample config that uses frame-relay as DLSW transport
>
(http://www.cisco.com/en/US/tech/tk331/tk336/technologies_configuration_exam
> ple09186a0080093d9f.shtml)
>
> DO I need to use the frame-relay transport or the TCP should work across a
> Fram-relay WAN
>
>
> Below is the config I used.
>
>
> Central Site Router
>
> dlsw local-peer peer-id 192.168.5.11
> dlsw remote-peer 0 tcp 192.168.46.1
> dlsw remote-peer 0 tcp 192.168.23.1
> dlsw bridge-group 4
>
> interface FastEthernet0/0
> ip address 192.168.5.11 255.255.255.0
> no ip mroute-cache
> duplex auto
> speed auto
> no cdp enable
> bridge-group 4
>
> interface Serial0/3
> no ip address
> encapsulation frame-relay
>
> interface Serial0/3.51 point-to-point
> ip address 192.168.200.9 255.255.255.252
> frame-relay interface-dlci 51
>
> bridge 4 protocol ieee
>
>
>
> Remote router with IBM controller
>
> source-bridge ring-group 4
> dlsw local-peer peer-id 192.168.23.1
> dlsw remote-peer 0 tcp 192.168.5.11
>
> interface FastEthernet0/0
> ip address 192.168.23.2 255.255.255.0
> no ip mroute-cache
> duplex auto
> speed auto
> no cdp enable
>
> interface Serial0/0
> ip address 192.168.200.10 255.255.255.252
> encapsulation frame-relay
> frame-relay interface-dlci 50
>
> interface Serial0/1
> description IBM 5494 Controller PU 2.1
> no ip address
> encapsulation sdlc
> no keepalive
> nrzi-encoding
> clockrate 56000
> sdlc role prim-xid-poll
> sdlc vmac 4000.2300.0000
> sdlc address 01
> sdlc partner 4000.0000.0000 01
> sdlc dlsw 1
>
> I have omitted the routing and other config portion for clarity.
> I know some one from the group must have used DLSW across Frame-relay and
> would be able to assist me.
>
> TIA
>
> Vinay
> .
.
This archive was generated by hypermail 2.1.4 : Fri Jan 17 2003 - 17:21:46 GMT-3