Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

DLSW Debugging

Hi Folks,

Really i need your help to undestand the output of a debug dlsw command.

My customer has a sporadic problem, suddenly the circuit goes down, but the dlsw peer keeps stable. There are not CRC errors, input/output errors at the serial interface.

I took the debug some seconds after the circuit was down.

Any help will be appreciate

Best Regards,

Johnny Ramos

johnny.ramos@telefonica-data.com.pe

----------------------------------

Jun 27 19:49:00: DLSw: Processing delayed event - prev state:CKT_START

.Jun 27 19:49:00: DLSw: START-FSM (1476395245): event:ADMIN-WAN_FAIL state:CKT_START

.Jun 27 19:49:00: DLSw: core: dlsw_action_z()

.Jun 27 19:49:00: DISP Sent : CLSI Msg : CLOSE_STN.Req dlen: 4

.Jun 27 19:49:00: DLSw: END-FSM (1476395245): state:CKT_START->CLOSE_PEND

.Jun 27 19:49:00: DLSW Received-ctlQ : CLSI Msg : ID.Cfm CLS_OK dlen: 128

.Jun 27 19:49:00: DLSw: START-FSM (704643306): event:DLC-Id state:CKT_ESTABLISHED

.Jun 27 19:49:00: DLSw: core: dlsw_action_f()

.Jun 27 14:49:00.306 GMT: %DLSWC-3-SENDSSP: SSP OP = 7( XID ) to peer 130.2.1.1(2065) success

.Jun 27 19:49:00: DLSw: END-FSM (704643306): state:CKT_ESTABLISHED->CKT_ESTABLISHED

.Jun 27 14:49:00.346 GMT: %DLSWC-3-RECVSSP: SSP OP = 8( CONQ ) from peer 130.2.1.1(2065)

.Jun 27 19:49:00: DLSw: START-FSM (704643306): event:WAN-CONQ state:CKT_ESTABLISHED

.Jun 27 19:49:00: DLSw: core: dlsw_action_i()

.Jun 27 19:49:00: DISP Sent : CLSI Msg : CONNECT.Req dlen: 16

.Jun 27 19:49:00: DLSw: END-FSM (704643306): state:CKT_ESTABLISHED->CONTACT_PENDING

.Jun 27 19:49:00: DLSW Received-ctlQ : CLSI Msg : CLOSE_STN.Cfm CLS_OK dlen: 8

.Jun 27 19:49:00: DLSw: START-FSM (1476395245): event:DLC-CloseStn.Cnf state:CLOSE_PEND

.Jun 27 19:49:00: DLSw: core: dlsw_action_y()

.Jun 27 19:49:00: DLSw: 1476395245 to dead queue

.Jun 27 19:49:00: DLSw: START-TPFSM (peer 130.2.1.1(2065)): event:CORE-DELETE CIRCUIT state:CONNECT

.Jun 27 19:49:00: DLSw: dtp_action_v(), peer delete circuit for peer 130.2.1.1(2065)

.Jun 27 19:49:00: DLSw: END-TPFSM (peer 130.2.1.1(2065)): state:CONNECT->CONNECT

.Jun 27 19:49:00: DLSw: END-FSM (1476395245): state:CLOSE_PEND->DISCONNECTED

.Jun 27 19:49:00: DLSW Received-ctlQ : CLSI Msg : CONNECT.Cfm CLS_OK dlen: 28

.Jun 27 19:49:00: DLSw: START-FSM (704643306): event:DLC-Connect.Cnf state:CONTACT_Pw cirG

.Jun 27 19:49:00: DLSw: core: dlsw_action_j()

.Jun 27 14:49:00.434 GMT: %DLSWC-3-SENDSSP: SSP OP = 9( CONR ) to peer 130.2.1.1(2065) success

.Jun 27 19:49:00: DISP Sent : CLSI Msg : FLOW.Req dlen: 0

.Jun 27 19:49:00: DLSw: END-FSM (704643306): state:CONTACT_PENDING->CONNECTED

.Jun 27 14:49:00.502 GMT: %DLSWC-3-RECVSSP: SSP OP = 10( INFO ) from peer 130.2.1.1(2065)

.Jun 27 19:49:00: DLSw: 704643306 decr r - s:20 so:0 r:19 ro:0

.Jun 27 19:49:00: DLSw: START-FSM (704643306): event:WAN-INFO state:CONNECTED

.Jun 27 19:49:00: DLSw: core: dlsw_action_m()

.Jun 27 19:49:00: DISP Sent : CLSI Msg : DATA.Req dlen: 41

.Jun 27 19:49:00: DLSw: END-FSM (704643306): state:CONNECTED->CONNECTED

1 REPLY
Bronze

Re: DLSW Debugging

The debugs taken after the circuit came down are not really helpful since they will only show it reestablishing.

A DLSW peer will only be torn down if it misses 3 consecutive keepalives and, with the default values, this will only be after 90 seconds so SNA circuits can time out if there is a probalem on the WAN connection without the peer necessarily coming down.

Check that other traffic is not preventing the DLSW traffic from being serviced. If so, configuring prioritisation may help.

Check also that there are no buffer misses since the additional overhead of expanding the buffer pool can cause SNA sessions to time out.

You might also find the following URL helpfull http://www.cisco.com/warp/customer/697/dlswts4.html

235
Views
0
Helpful
1
Replies
CreatePlease to create content