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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

DLSW Problems - Duplicate DLSW SDLC VMAC

Hi,

I have some problems with a DLSW Estabilishement Circuit CONNECTED State.

My topologie is to connect IBM Mainframes into a Single Gateway Scenario. All the configurations in the machines are correct, and during a feel period of elapsed time we had the mainframe XCA/line/PU Station (Side DLSW) and the PU from CCU 3745 line (Single Gateway Side) both into ACTIVE state. The problem occured when we tried to INACT and ACT the mainframe VTAM lines; The lines, after this restart operation stayed in PCTD1 all the time. Searching the problem into DLSW's Border Router definitions, we observe that there are two Routers Serial Interfaces defineds with the same SDLC VMAC address (4000.3745.0000). Executing the DEBUG DLSW command was verified that there are the following messages:

00:39:07: CSM: delete group cache for 4000:3745:1, group 0

00:39:07: CSM: delete group cache for 4000:3745:1, group 0

00:39:07: DLSw: START-FSM (2147483685): event:DLC-CloseStn.Cnf state:CLOSE_PEND

00:39:07: DLSw: 2147483685 to dead queue

My question is, the ocurrence of these two delete group cache for the same Mac Address 4000.3745.1, group 0, means the mistake into maintain defined two Serials Interfaces with the same SDLC VMAC Address ?

The messages dispalynd  the CONNECTED state never appears and iI think mus be something like that sample:

%DLSWC-3-RECVSSP: SSP OP = 8( CONQ ) from peer 10.17.2.198(2065)

DLSw: START-FSM (488636): event:WAN-CONQ state:CKT_ESTABLISHED

DLSw: core: dlsw_action_i()

DISP Sent : CLSI Msg : CONNECT.Req dlen: 16

DLSw: END-FSM (488636): state:CKT_ESTABLISHED->CONTACT_PENDING

DLSW Received-ctlQ : CLSI Msg : CONNECT.Cfm CLS_OK dlen: 8

DLSw: START-FSM (488636): event:DLC-Connect.Cnf state:CONTACT_PENDING

DLSw: core: dlsw_action_j()

%DLSWC-3-SENDSSP: SSP OP = 9( CONR ) to peer 10.17.2.198(2065) success

DISP Sent : CLSI Msg : FLOW.Req dlen: 0

DLSw: END-FSM (488636): state:CONTACT_PENDING->CONNECTED

Part of others message that appears at the answer of the command DEBUG DLSW was:

00:39:07: %DLSWC-3-RECVSSP: SSP OP = 3( CUR ) -explorer from peer 10.245.105.1(2065)

00:39:07: %DLSWC-3-RECVSSP: SSP OP = 25( HLTN ) from peer 10.245.105.1(2065)

00:39:07: DLSw: START-FSM (2147483685): event:WAN-HLTN state:CKT_ESTABLISHED

00:39:07: DLSw: core: dlsw_action_6()

00:39:07: CSM: delete group cache for 4000:3745:1, group 0

00:39:07: CSM: delete group cache for 4000:3745:1, group 0

00:39:07: DISP Sent : CLSI Msg : CLOSE_STN.Req dlen: 4

00:39:07: DLSw: END-FSM (2147483685): state:CKT_ESTABLISHED->CLOSE_PEND

00:39:07: DLSW Received-ctlQ : CLSI Msg : CLOSE_STN.Cfm CLS_OK dlen: 8

00:39:07: DLSw: START-FSM (2147483685): event:DLC-CloseStn.Cnf state:CLOSE_PEND

00:39:07: DLSw: core: dlsw_action_y()

00:39:07: DLSw: 2147483685 to dead queue

Thanks in advance for any help.

Francisco Kuhner.

1 REPLY
Bronze

DLSW Problems - Duplicate DLSW SDLC VMAC

Francesco,

a duplicate sdlc vmac is only an issue if the sdlc addresses for the attached devices are the same. However, it is not good practice as it can obviously lead to issues. The delete of the duplicate mac-addresses with message core: dlsw_action_6 relates to a failure to resolve the remote mac-address. Is the issue now resolved ?

Matthew

494
Views
0
Helpful
1
Replies