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

SNASW QLLC with remote Stratus; sense 1016

Attaching a remote Stratus controller we got the following error during XID negotiation: %SNASW-3-CS_LOG_6: PROBLEM - 1766 - XID protocol error during activation exchange

The XID sent by the IOS contains following the CV22:

22 07 00 09 00 10 16 00 00

The attached trace in ANALYSER format contains the XIDs exchanged. I interpret the error as the bit 0 of the byte 9 of the received XID3 is on and means:

1 ACTPU for an SSCP-PU session not requested

Is this the right cause of the sense 1016? Is there a way to tell the IOS to ignore this bit that is also sent on to an IBM 3745 and causes no error.

Note: the Stratus controller is a remote material that connects ATM for a bank on which we have no control.

1 REPLY
New Member

Re: SNASW QLLC with remote Stratus; sense 1016

Your analysis on the sense code and the ACTPU not requested bit is correct.

Can we get the pdlog and configuration? If you don't want to attach those entire files, "show snasw pdlog id 1766 detail" and "show run | incl snasw" should be enough.

What I'm looking for is what kind of link this is, and how you have the port configured.

There are certain types of links that we determine must be dependant LU only, so we don't let the link come up if it won't be usable. It sounds like the Stratus controller is LU 6.2 only? Ray noticed that the incoming XID does not have a CPname, and we suspect this is the problem SNASw has with it. Since you have migrated from subarea (IBM 3745) to APPN, a CP name is required for APPN routing

We think you may be able to work around this by adding a conntype to the snasw port. Unless this is a "dial out" link initiated from the host, probably adding "conntype dyncplen" to your snasw port that the downstream connects in on will fix the problem, as SNASw will create a dynamic CP name (starting with @) for the downstream device. That should make it look like a different link and adjacent CP type, one which can support LU 6.2 and does not require the ACTPU requested support.

If that doesn't work, or you have any question about this, please collect the pdlog and configuration requested above.

218
Views
0
Helpful
1
Replies
CreatePlease to create content