Re: DLSW+ circuit state problem

From: Jarry Way (ccie@xxxxxxxxxxx)
Date: Mon Sep 04 2000 - 12:16:08 GMT-3


   
John,

Routers configured as blowed.

Central Router:
..
dlsw local-peer peer-id 16.106.110.21 promiscuous
..
interface Serial3/1
 no ip address
 no ip directed-broadcast
 encapsulation sdlc
 no keepalive
 clockrate 9600
 sdlc role secondary
 sdlc vmac 4012.1019.3100
 sdlc address C3 xid-passthru
 sdlc partner 4012.2019.02c3 C3
 sdlc address C4 xid-passthru
 sdlc partner 4012.2019.02c4 C4
 sdlc address C5 xid-passthru
 sdlc partner 4012.2019.02c5 C5
 sdlc dlsw C3 C4 C5

Branch Router:
dlsw local-peer peer-id 16.106.109.77
dlsw remote-peer 0 tcp 16.106.110.21
.....
interface Serial0/2
 no ip address
 no ip directed-broadcast
 encapsulation sdlc
 no ip mroute-cache
 no keepalive
 clockrate 9600
 sdlc role prim-xid-poll
 sdlc vmac 4012.2019.0200
 sdlc poll-pause-timer 150
 sdlc T1 6000
 sdlc address C3
 sdlc partner 4012.1019.31c3 C3
 sdlc address C4
 sdlc partner 4012.1019.31c4 C4
 sdlc address C5
 sdlc partner 4012.1019.31c5 C5
 sdlc dlsw C3 C4 C5
!
.....

The branch router's serial0/2 connect to one 4700 emulation server(C3) and two
ATMs(C4 & C5) by PSD. From output of 'show dlsw circuit' command, the states of
 C3 and C5 are CONNECT, but C4 is CONTACT_PENDING.

I have done two experiments. When the C4 ATM directly connected to the router's
 serial interface, its circuit status changed to CONNECT and worked fine. When
it directly connect to IBM 3745 (no router, no DLSW) by SDLC line via PSD, it a
lso worked well.

Any more suggestion? Thanks.

Jarry Way

> Jarry, can you send configs? Do you have the remote router set as
>"primary" and the router connected to the FEP as "secondary"?
> Check your VTAM definitions also.
>
>----- Original Message -----
>From: "Jarry Way" <ccie@cool.com.cn>
>To: <ccielab@groupstudy.com>
>Sent: Sunday, September 03, 2000 10:00 PM
>Subject: DLSW+ circuit state problem
>
>
>> Hi, all
>>
>> There are two DLSW peer routers, one is in the central office connect to
>IBM 3745 by SDLC, the other is in the branch office connect to some PU 2.0
>devices by SDLC.
>>
>> Now, I have a problem on it. On the peer routers, DLSW peer state is
>CONNECT, but the circuit state on central office is CONNECT_PENDING and SDLC
>state is SNRMSEEM, the branch one is CONTACT_PENDING and SNRMSEND.
>>
>> I don't know what is reason of the problem. Can anybody help me, thanks.
>>
>>
>> Jarry Way, CCIE #6095
>> Brilliance Computer Industry Co., Ltd.
>>
>>
>>



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:52 GMT-3