Re: SNA Connection fail

jrmoraes77 · ‎11-17-2003

I just install a network based on layers of access (to WAN), DLSw and CSNA. When we start the tests some remote devices start a DLSw circtuits and SNA traffic with no problems, but other devices (SDLC) on remote sites start a DLSw traffic but can't start applicatins on Mainframe (CICS). The command show dlsw circuits history detail showed bellow show many WAN INFOFRAMES without response. Anyone can help us to fix this problem or indicate where is the problem (WAN, DLSw, CSNA, Mainframe, etc.) ?

Best Regards

3221225577 4000.3500.00fe(04) 4026.3401.12c1(04) 10.232.177.26

Created at : 13:43:09.865 UTC Mon Nov 17 2003

Connected at : 13:43:10.181 UTC Mon Nov 17 2003

Destroyed at : 14:11:06.677 UTC Mon Nov 17 2003

Local Corr : 3221225577 Remote Corr: 3120562367

Bytes: 5534/3320 Info-frames: 34/61

XID-frames: 1/2 UInfo-frames: 0/0

Flags: Remote created, Local connected

Last events:

Current State Event Add. Info Next State

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

CONNECTED WAN infoframe 0x0 CONNECTED

CONNECTED DLC DataInd 0x0 CONNECTED

CONNECTED WAN infoframe 0x0 CONNECTED

CONNECTED DLC DataInd 0x0 CONNECTED

CONNECTED WAN infoframe 0x0 CONNECTED

CONNECTED WAN halt-dl 0x0 HALT_PENDING

HALT_PENDING DLC DiscCnf 0x0 CLOSE_PEND

CLOSE_PEND DLC CloseStnCnf 0x0 DISCONNECTED

dixho · ‎11-17-2003

Where do you the show dlsw circuit history detail?

The WAN Infoframe may not be the problem because I do not think that RR (LLC2 ack) frames show up in the show dlsw circuit history detail. The root cause is the WAN HALT-DL. This causes the DLSw circuit to disconnect. We need to find out why the remote DLSw peer sends out HALT_DL.

I suggest you to do a show dlsw circuit history detail on the other side of DLSw and find out why it issues a HALT_DL. You may also need debug llc2 packet, CIP console trace, show interface serial, or debug sdlc packet.

jrmoraes77 · ‎11-23-2003

Thank you for assistance. The customer indentify a problem in VTAM, IBM are working now to fix this problem.

Thank you.