Cisco IOS System Error Messages, Volume 2 of 2 - SNASW [Cisco IOS Software Releases 12.2 Mainline]

Table Of Contents

SNASW Messages

SNASW Messages

The following are Systems Network Architecture Switching Services (SNASw) error messages.
Error Message  
%SNASW-4-APPN_LOG_0 : EXCEPTION - [int] - SNA Switch could not allocate necessary storage [chars]
Explanation The SNA switch could not allocate the necessary storage. Some operations might fail. Other logs will provide more information.
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch.
Error Message  
%SNASW-3-APPN_LOG_1 : PROBLEM - [int] - SNA Switch could not allocate necessary storage [chars]
Explanation The SNA switch could not allocate the necessary storage. Some operations will fail. See other logs or verbs.
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch.
Error Message  
%SNASW-4-APPN_LOG_2 : EXCEPTION - [int] - SNA Switch cryptography call failed, possibly due to missing password [chars]
Explanation A call from the SNA switch to perform a cryptographic operation has failed. The session activation will fail, an active session will end abnormally with the given sense code, or some other action will fail. More information may appear in subsequent logs.
Recommended Action Check the logs that follow for evidence of failed session activation: if evidence is present, check the MODE, LS, or INTERNAL PU definitions for cryptographic support. Check that any passwords that are necessary have been defined. If this problem occurs intermittently or with sessions already active with the same PLU, SLU, and mode, make more storage available to the SNA switch.
Error Message  
%SNASW-3-ASM_LOG_0 : PROBLEM - [int] - Received BIND request directed at this node with unrecognized secondary LU name [chars]
Explanation The system has received a BIND request directed at this node (either without an RSCV or at the last hop on the RSCV) with an unrecognized secondary LU name. This condition usually indicates a configuration error at the primary LU. The session activation will fail with the specified sense code.
Recommended Action Correct the primary LU configuration.
Error Message 
%SNASW-3-ASM_LOG_2 : PROBLEM - [int] - Insufficient storage to generate an Alert [chars]
Explanation There is insufficient storage to generate an alert to report a BIND segmentation or pacing error. The alert will not be sent.
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch.
Error Message 
%SNASW-3-ASM_LOG_3 : PROBLEM - [int] - Insufficient storage to process received BIND request [chars]
Explanation There is insufficient storage to process a received BIND request. The BIND request will be rejected with the specified sense code.
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch.
Error Message  
%SNASW-3-ASM_LOG_4 : PROBLEM - [int] - ACTPU, ACTLU, DACTPU or DACTLU received on link on which dependent LUs are not supported [chars]
Explanation An ACTPU, ACTLU, DACTPU or DACTLU was received over a link on which dependent LUs are not supported. This condition may indicate an interoperability problem. The request will be rejected with the specified sense code.
Recommended Action Copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message  
%SNASW-3-ASM_LOG_5 : PROBLEM - [int] - Branch Network Node received BIND request with badly formed RSCV [chars]
Explanation A branch network node has received a BIND request with a badly formed RSCV. This condition may indicate an interoperability problem. The session activation will fail.
Recommended Action Copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message  
%SNASW-3-ASM_LOG_6 : PROBLEM - [int] - Badly-formed BIND request rejected by SNA Switch [chars]
Explanation The SNA switch has received and rejected a badly formed BIND request. This condition may indicate an interoperability problem. The session activation will fail.
Recommended Action Copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message  
%SNASW-3-ASM_LOG_11 : PROBLEM - [int] - Received BIND request with badly formed secondary LU name [chars]
Explanation The system has received a BIND request with a badly formed secondary LU name. This may indicate an interoperability problem. The session activation will fail with the specified sense code.
Recommended Action Copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message  
%SNASW-3-ASM_LOG_12 : PROBLEM - [int] - Received BIND request where network ID of secondary LU does not match local network ID [chars]
Explanation The system has received a BIND request in which the network identifier of the secondary LU does not match local network identifier. The session activation will fail with the specified sense code.
Recommended Action Copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message  
%SNASW-4-ASM_LOG_15 : EXCEPTION - [int] - Insufficient storage to deactivate link [chars]
Explanation Insufficient storage is available to deactivate a link. The link will not be deactivated.
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch.
Error Message  
%SNASW-4-ASM_LOG_18 : EXCEPTION - [int] - Unable to correlate received BIND response [chars]
Explanation The system is unable to correlate the received BIND response. This condition is a normal race condition and occurs when a BIND is followed immediately by an UNBIND for the same session. The BIND response is discarded.
Recommended Action No action is required.
Error Message  
%SNASW-3-ASM_LOG_19 : PROBLEM - [int] - Received BIND using LFSID that is already in use [chars]
Explanation The system has received a BIND using an LFSID that is the system is already using. This condition is usually caused by a race condition (a BIND, UNBIND, BIND sequence all using the same LFSID, where the second BIND overtakes the UNBIND). Nodes at the current level of APPN contain "LFSID aging" processes to minimize the changes of this race condition, but some older implementations may not support this processing. The BIND will be rejected with the specified sense code.
Recommended Action If this message is persistent, or occurs frequently, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message 
%SNASW-3-ASM_LOG_22 : PROBLEM - [int] - Session control request received with invalid LFSID [chars]
Explanation A session control request with an invalid LFSID (that is, an LFSID that is not in a range appropriate for the request) has been received. This condition may indicate an interoperability problem. The request will be rejected with the specified sense code.
Recommended Action Copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message  
%SNASW-3-ASM_LOG_24 : PROBLEM - [int] - Failed to initialize address space instance [chars]
Explanation There is insufficient storage to create an LFSID routing table for a link station. Link activation will fail.
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch.
Error Message  
%SNASW-4-ASM_LOG_25 : EXCEPTION - [int] - Unable to extend local form session identifier routing table [chars]
Explanation The system is unable to extend the LFSID routing table. The session activation will fail with the specified sense code.
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch.
Error Message  
%SNASW-4-ASM_LOG_26 : EXCEPTION - [int] - Independent LU session deactivated because LU deleted [chars]
Explanation An independent LU-LU session has been deactivated because the local LU has been deleted.
Recommended Action No action is required.
Error Message  
%SNASW-3-ASM_LOG_27 : PROBLEM - [int] - Detected fatal BIND or UNBIND protocol error [chars]
Explanation The system has detected a fatal BIND or UNBIND protocol error. This condition may indicate an interoperability problem. Sense codes are as follows:
•20110000—BIND pacing window overrun, or PI not set when expected.

•20110001—Unexpected solicited BIND IPM.

•20110002—PI set when not expected.

•20110003—Pacing response not IPM.

•10020000—RU (BIND, UNBIND or BIND IPM) length error.

•10010003—BIND IPM format error.

•80070000—BIND or RSP(BIND) segment out of sequence, or segmented UNBIND or RSP(UNBIND).

•80070002—BIND or RSP(BIND) segments interleaved.

•800F0000—LFSID incorrect for SC request.

•800F0001—ODAI incorrect.

The link will be deactivated.

Recommended Action Copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message  
%SNASW-3-ASM_LOG_28 : PROBLEM - [int] - Received BIND IPM on link where adaptive BIND pacing not supported [chars]
Explanation The system has received a BIND IPM on a link where adaptive BIND pacing is not supported. This may indicate an interoperability problem. The BIND IPM will be discarded.
Recommended Action Copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message  
%SNASW-4-ASM_LOG_29 : EXCEPTION - [int] - Dependent LU session deactivated because LU deleted [chars]
Explanation A dependent LU-LU session has been deactivated because the LU has been deleted.
Recommended Action No action is required.
Error Message 
%SNASW-3-BAD_MSG_NAME : Invalid message name specified for snasw msg-trap
Explanation An invalid message name was supplied on a snasw msg-trap command.
Recommended Action Enter the command again with a valid message name.
Error Message  
%SNASW-4-CH2_LOG_0 : EXCEPTION - [int] - CRV exchange failed on a PLU-SLU session. The session will fail [chars]
Explanation A CRV exchange has failed. This condition indicates that the cryptography keys that are configured at this LU and the partner LU are inconsistent. The session will be deactivated with the sense code 08350001.
Recommended Action Use the information in the session-deactivated problem log (log 271) to identify the local LU and partner LU and correct the cryptography key mismatch.
Error Message  
%SNASW-4-CH2_LOG_1 : EXCEPTION - [int] - Protocol error during CRV exchange [chars]
Explanation Protocol error during CRV exchange. This indicates a possible interoperability problem. Sense codes are as follows:
•20090000—CRV request received from the secondary LU, or CRV response received from the primary LU, or CRV not received when expected.

•10020000—CRV RU too short.

•400F0000—CRV with FI not set.

•400B0000—CRV chain indicators not set to BC, EC.

•40140000—The CRV not RQD1.

•40110000—The CRV not expedited.

•40150000—The CRV with QRI not set.

•40080000—The CRV with PI set.

•400C0000—The CRV request with BBI, EBI or CEBI set.

•400D0000—The CRV request with CDI set.

•40100000—The CRV request with CSI set to CODE1.

•40160000—The CRV request with EDI set.

•40170000—The CRV request with PDI set.

•40130000—The CRV response RTI and SDI inconsistent.

The session will be deactivated with the specified sense code.

Recommended Action Use the information on the session deactivated problem log (271) to identify the local LU and partner LU. Run a trace on the specified link station and contact your Cisco technical support representative with the log and trace information.
Error Message  
%SNASW-4-CH2_LOG_2 : EXCEPTION - [int] - Insufficient storage to initialise half session [chars]
Explanation Available storage was insufficient for initializing the half session. The half session activation will fail with the specified sense code.
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch.
Error Message  
%SNASW-4-CH_LOG_0 : EXCEPTION - [int] - LU type 0,1,2 or 3 format error [chars]
Explanation An LU type 0, 1, 2, or 3 format error has occurred. This condition may indicate an interoperability problem. The PIU containing the error is discarded.
Recommended Action Copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message  
%SNASW-4-CH_LOG_1 : EXCEPTION - [int] - LU type 0,1,2 or 3 session ended abnormally because of insufficient storage [chars]
Explanation An LU type 0, 1, 2, or 3 session has ended abnormally because of insufficient storage. The session will be deactivated with the specified sense code.
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch.
Error Message  
%SNASW-4-CH_LOG_2 : EXCEPTION - [int] - LU type 0,1,2 or 3 session ended abnormally while receiving data [chars]
Explanation An LU type 0, 1, 2, or 3 session has ended abnormally while receiving data. The session will be deactivated with the specified sense code.
Recommended Action Copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message  
%SNASW-4-CH_LOG_3 : EXCEPTION - [int] - LU type 0,1,2 or 3 session ended abnormally because of invalid application data [chars]
Explanation An LU type 0, 1, 2, or 3 session has ended abnormally because of invalid data received from the application. The session will be deactivated with the specified sense code.
Recommended Action Copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message  
%SNASW-4-CH_LOG_4 : EXCEPTION - [int] - Application sent invalid Data message [chars]
Explanation An LU type 0, 1, 2, or 3 application has sent an invalid Data message. A status acknowledge (NACK-2) was sent to the application.
Recommended Action Investigate the error in the application.
Error Message  
%SNASW-4-CH_LOG_5 : EXCEPTION - [int] - Application sent invalid Status Control message [chars]
Explanation An LU type 0, 1, 2, or 3 application has sent an invalid Status Control message. A Status Control (NACK-2) was sent to the application.
Recommended Action Investigate the error in the application.
Error Message  
%SNASW-4-CH_LOG_6 : EXCEPTION - [int] - Application sent invalid Acknowledgment or Status message [chars]
Explanation An LU type 0, 1, 2, or 3 application has sent an invalid Acknowledgment or Status message. A Status error was sent to the application.
Recommended Action Investigate the error in the application.
Error Message  
%SNASW-4-CH_LOG_8 : EXCEPTION - [int] - Insufficient storage to report RTM statistics to Host [chars]
Explanation Available storage was insufficient for reporting the RTM statistics to the host. The RTM statistics displayed by the host will be inconsistent.
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch.
Error Message  
%SNASW-4-CH_LOG_9 : EXCEPTION - [int] - Insufficient storage to report RTM status to application [chars]
Explanation Available storage was insufficient for reporting the RTM status to the application. The RTM statistics reported and displayed by the application may be inconsistent.
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch.
Error Message  
%SNASW-3-CLSIBadPrimitive : CLSI bad primitive type, header= [chars]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message  
%SNASW-3-CLSIBadReturnCode : CLSI bad return code: [dec], header= [chars]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message  
%SNASW-3-CLSIFailure : SNASW failed to process CLSI message, header= [chars]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message  
%SNASW-4-CPUUsage : SNASw process, type [hex] ran for [int] ms processing IPS of type [hex], address [hex]
Explanation A process within the SNA switch ran for an unexpectedly long time.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message 
%SNASW-3-CS_LOG_0 : PROBLEM - [int] - An active link station has failed [chars]
Explanation An active link station has failed. The link and any sessions using it will be deactivated.
Recommended Action Attempt to restart the link. If the problem persists, inspect the log for problems or exceptions that were logged by the DLC that give more specific reasons for the failure, and follow the actions specified by those logs. Otherwise, run a trace on the specified port or link station to find the reason for the failure.
Error Message  
%SNASW-3-CS_LOG_1 : PROBLEM - [int] - XID exchange count exceeds activation limit [chars]
Explanation The number of XIDs that were received during link activation exceeded the limit defined for the port. This condition could indicate an XID protocol error or an excessively unreliable physical medium. The sense data gives more information about the error:
•083E0001—The limit was exceeded while prenegotiation or negotiation XIDs were being exchanged.

•0809003A—The limit was exceeded while NULL XIDs were being exchanged.

Link activation will fail.

Recommended Action Retry the activation. If the SNA switch is still unable to activate the link station, run a trace on the link station or port to diagnose the problem.
Error Message 
%SNASW-3-CS_LOG_2 : PROBLEM - [int] - XID exchange count exceeds nonactivation limit [chars]
Explanation The number of XIDs received during nonactivation exchange exceeded the limit that was defined for the port. This condition could indicate an XID protocol error or an excessively unreliable physical medium. Nonactivation XID exchange will fail, and the link will be deactivated.
Recommended Action Run a trace on the link station or port to diagnose the problem, and contact your Cisco technical support representative with the trace information.
Error Message 
%SNASW-3-CS_LOG_3 : PROBLEM - [int] - Insufficient storage to activate link [chars]
Explanation Available storage was insufficient for activating the link, and the link activation will fail.
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch.
Error Message 
%SNASW-3-CS_LOG_4 : PROBLEM - [int] - Link to back-level LEN node not configured [chars]
Explanation An XID3 from an adjacent back-level LEN node (not carrying a network name control vector) has been received, and there was not a link configured to that back-level LEN node. An implicit link cannot be activated because the CP name of the adjacent node is not known. Inbound link activation will fail.
Recommended Action Define a link station by entering the snasw link command with adj_cp_type set to NAP_BACK_LEVEL_LEN_NODE.
Error Message 
%SNASW-3-CS_LOG_5 : PROBLEM - [int] - Link to host not configured correctly (host is not a Type 2.1 node) [chars]
Explanation The link to host is incorrectly configured as a link to a Type 2.1 node. Link activation will fail.
Recommended Action Define or redefine the link station by entering the snasw link command with adj_cp_type set to NAP_HOST_XID3 or NAP_HOST_XID0.
Error Message 
%SNASW-3-CS_LOG_6 : PROBLEM - [int] - XID protocol error during activation exchange [chars]
Explanation An XID protocol error occurred during the activation exchange. This condition may indicate an interoperability problem between this node and the adjacent node, or this condition may be caused by the adjacent node resetting and restarting the exchange without sending a DISC or DM frame. The sense codes are as follows:
•0806002C—The adjacent node has changed its network name during the course of an XID exchange.

•0809003A—A null XID was received when an XID format 3 was expected.

•0809003C—Prenegotiation XID received when not expected (had already received a negotiation proceeding XID3).

•0809003D —Nnonactivation XID received when a null XID or activation XID was expected.

•08090040—Received an unexpected or invalid mode-setting command (for example, SNRM or SABME).

•08090045—The adjacent node has stopped supporting exchange state indicators in the middle of an XID exchange.

•08090046—The adjacent node had previously indicated it did not support exchange state indicators, but has sent a XID with exchange state indicators set.

•08090047—An XID was received after receipt of a mode-setting command (such as SNRM or SABME).

•08090048—An unsolicited XID was received from an NRM secondary link station.

•08090049—The adjacent node has sent an XID error control vector (x'22'). 08090055—Invalid VRN in TG descriptor CV of XID3.

•086F0000—XID3 control vector length error.

•088C1000—The adjacent node is a network node, but did not include a product set identifier control vector in the XID3.

•088C0EF1—The adjacent node is type 4 or 5, but did not include a PU name control vector.

•088C0EF4—The adjacent node has no been inconsistent in including a network name control vector.

•088C4680—An XID was received on an ATM port, but it did not include a TG identifier TG descriptor subfield.

•08910004—The network name control vector does not contain a valid network identifier.

•08910005—The network name control vector does not contain a valid CP name.

•0895xxyy—XID3 control vector error (xx indicates key of first control vector in error, yy indicates offset of error within control vector).

•08960000—The control vector is too long.

•08960001—The network name control vector is too long.

•10150001—A received XID3 is too short (less than 29 bytes).

•10150002—The length of a received XID3 does not match the length indicated in XID3.

•10160000—The adjacent node indicated an invalid BIND pacing setting.

•10160001—The maximum number of I-frames that the adjacent node can receive before sending an acknowledgment is set to zero.

•10160003—The maximum BTU size the adjacent node can receive is set to less than 99 bytes.

•10160004—Unexpected XID format.

•10160005—The adjacent end node supports receipt of BIND segments but does not support BIND segment generation.

•10160006—The adjacent end node does not support receipt of BIND segments and has a maximum BTU size of less than 265 bytes.

•10160007—The adjacent network node does not support receipt of BIND segments and has a maximum BTU size of less than 521 bytes.

•10160008—The adjacent node has been inconsistent in its setting of networking capabilities.

•10160009—The adjacent network node supports CP-CP sessions but does not provide CP services.

•1016000B—The adjacent node has selected zero as the TG number; this value is invalid.

•1016000C—The adjacent network node does not support BIND segment generation and has a maximum BTU size of less than 521 bytes.

•1016000D—The adjacent node does not support the SDLC command/response profile (which is the only profile supported by APPN and LEN nodes).

•1016000E—The product set identifier on XID3 has changed.

•10160010—The ABM support indicated in sent and received XID3s is inconsistent.

•10160013—The DLC type in sent and received XIDs are not in agreement.

•10160014—The adjacent node has changed its role from nonnegotiable to negotiable.

•10160015—The adjacent node supports BIND pacing as sender only.

•10160017—After two exchanges, randomized node IDs sent by this node and the adjacent node are still identical.

•1016001A—The adjacent node is inconsistent in its support for parallel TGs.

•1016001B—The adjacent node provides or requests CP services but does not support CP-CP sessions.

•1016001C—The adjacent node indicated an LS role that was not primary, secondary, or negotiable.

•1016001E—The adjacent node did not send its CP name in XID3 but requested CP-CP sessions on this link.

•10160020—The adjacent node is not type 2, 4, or 5.

•10160022—The adjacent node included an HPR Capabilities [x'61'] control vector in its XID3 but specified a maximum BTU size less than 768.

•10160023—The adjacent node included an HPR Capabilities [x'61'] control vector in its XID3 but specified an invalid ANR label length (less than 1 or greater than 8).

•10160026—The NCE field lengths in the HPR Control Flows [x'81'] subfield are inconsistent with the length of the HPR Capabilities [x'61'] control vector.

•10160027—The adjacent node indicated support for control flows over RTP, but it did not include an HPR Control Flows [x'81'] subfield.

•10160028—The adjacent node has specified an invalid error mode in its HPR Capabilities CV.

•10160034—The adjacent node indicated no support for LDLC, but the local node supports only LDLC.

•10160044—The adjacent node indicated support for LDLC, but did not include an LLC SAP subfield in the HPR Capabilities CV. Link activation will fail.

Recommended Action Copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message 
%SNASW-3-CS_LOG_7 : PROBLEM - [int] - No free TG numbers [chars]
Explanation No free TG numbers are available between this node and the specified adjacent node. This condition should occur only if there are already 236 parallel TGs between this node and the adjacent node. Link activation will fail.
Recommended Action Reconfigure the network to reduce the number of parallel TGs between this node and the specified adjacent node.
Error Message 
%SNASW-3-CS_LOG_8 : PROBLEM - [int] - XID protocol error during non-activation exchange [chars]
Explanation An XID protocol error has occurred during a non-activation exchange. This condition may indicate an interoperability problem between this node and the adjacent node. The sense codes are as follows:
•0809003A—A null XID was received when an activation XID format 3 was expected.

•0809003B—A null XID was received when a nonactivation XID format 3 was expected.

•0809003E—An activation XID was received when a nonactivation XID was expected.

•0809003F—The adjacent node initiated a secondary-initiated nonactivation XID exchange on a link that does not support secondary-initiated nonactivation XID exchanges.

•08090042—The nonactivation exchange initiation indicator was not set when expected.

•0809004E—A non-null XID was received from a secondary NRM link station when a null XID was expected.

•10160002—The adjacent node has been inconsistent in its setting of the ACTPU suppression indicator.

•10160008—The adjacent node has been inconsistent in its setting of networking capabilities.

•1016000B—The adjacent node attempted to change TG number during nonactivation exchange to a TG number that was already in use.

•10160019—The adjacent node has attempted to change its CP name when CP-CP sessions supported on link station, or the link station is not quiesced.

The link will be deactivated.

Recommended Action Run a trace on the link station or port to obtain more diagnostic information on the problem. Contact your Cisco technical support representative with the log and trace information.
Error Message 
%SNASW-3-CS_LOG_9 : PROBLEM - [int] - Link to host not configured correctly (host is not a DSPU) [chars]
Explanation The link to the host has been incorrectly configured as a link to a DSPU. Link activation will fail.
Recommended Action Define or redefine the link station by entering the snasw link command with adj_cp_type set to NAP_HOST_XID3 or NAP_HOST_XID0.
Error Message  
%SNASW-3-CS_LOG_10 : PROBLEM - [int] - Link to host not configured [chars]
Explanation An unexpected SET_MODE has been received from an adjacent host before the XID exchange had completed, and there was not a link configured to that host. An implicit link cannot be activated because there is no local PU defined to use the link. Inbound link activation will fail.
Recommended Action Define a link station by entering the snasw link command with adj_cp_type set to NAP_HOST_XID3 or NAP_HOST_XID0.
Error Message  
%SNASW-3-CS_LOG_11 : PROBLEM - [int] - Parallel TGs not supported to this adjacent node [chars]
Explanation The system attempted to activate more than one TG to an adjacent node that does not support parallel TGs. Link activation will fail.
Recommended Action Modify the configuration so that only one link station is defined to the specified adjacent node. Alternatively, several links to the adjacent node can be defined, but only one can be active at a time.
Error Message  
%SNASW-4-CS_LOG_12 : EXCEPTION - [int] - Insufficient storage to perform orderly link deactivation (link deactivated immediate instead) [chars]
Explanation Available storage was insufficient for performing orderly link deactivation. The system performed an immediate deactivation instead.
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch.
Error Message  
%SNASW-3-CS_LOG_13 : PROBLEM - [int] - Conflicting requirements for error recovery, link is not HPR-capable [chars]
Explanation During an attempt to activate a link that is HR-capable, error-recovery requirements for a local node and a partner node were in conflict. The link will activate, but it will not be HPR-capable.
Recommended Action To allow HPR protocols to be used on the link, each of the local and partner nodes must be able to accommodate the error recovery requirements of the other. At the minimum, this will require reconfiguration, but reconfiguration may not always be possible.
Error Message  
%SNASW-4-CS_LOG_14 : EXCEPTION - [int] - Insufficient storage to update ANR routing tables following deactivation of an HPR-capable link [chars]
Explanation Available storage was insufficient for updating the ANR routing tables following deactivation of an HPR-capable link. The node may not be able to free resources that are no longer required but will otherwise operate normally.
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch.
Error Message  
%SNASW-4-CS_LOG_15 : EXCEPTION - [int] - Insufficient storage to update ANR routing tables following activation of an HPR-capable link [chars]
Explanation Available storage was insufficient for updating the ANR routing tables following the activation of an HPR-capable link. HPR traffic using this ANR label will not be routed correctly, possibly causing RTP connections to path-switch or fail altogether.
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch.
Error Message  
%SNASW-3-CS_LOG_17 : PROBLEM - [int] - DLC failed [chars]
Explanation A DLC has ended abnormally. All ports and link stations defined on the DLC will be inoperative.
Recommended Action Restart the DLC by entering the snasw start port command. If the problem persists, look for DLC-specific logs giving more information about the reason for the failure.
Error Message  
%SNASW-4-CS_LOG_19 : EXCEPTION - [int] - Insufficient storage to forward Alert generated by DLC [chars]
Explanation Available storage was insufficient for forwarding an alert generated by the DLC. The alert will be discarded.
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch.
Error Message 
%SNASW-3-CS_LOG_22 : PROBLEM - [int] - Unable to deactivate port [chars]
Explanation The system is unable to deactivate the specified port. The snasw stop port command will fail, and the port may not restart successfully.
Recommended Action Attempt to restart the port, if required. If restart fails, look for DLC specific logs giving more information about the reason for the failure.
Error Message  
%SNASW-3-CS_LOG_24 : PROBLEM - [int] - Unrecoverable DLC failure [chars]
Explanation An unrecoverable DLC failure has occurred. The DLC will be destroyed, and all ports and link stations defined on the DLC will be inoperative.
Recommended Action Restart the DLC and ports by entering the snasw start port command. If these operations fail, or this problem is persistent, run a trace on the DLC and contact your Cisco technical support representative with the log and trace information.
Error Message  
%SNASW-4-CS_LOG_25 : EXCEPTION - [int] - Link not configured for automatic activation or last stopped non-automatically [chars]
Explanation A session or application required the SNA switch to activate a link station automatically, but the link station was not configured to be automatically activated or was not stopped automatically the last time it was stopped. The session or application will fail with the specified sense code.
Recommended Action Either manually activate the link by entering the snasw start link command or redefine the link to support automatic activation by entering the snasw link command.
Error Message  
%SNASW-4-CS_LOG_26 : EXCEPTION - [int] - Unable to activate link station because owning port is not active [chars]
Explanation A session or application required the SNA switch to activate a link station automatically, but the request failed because the owning port was not active. This problem usually indicates an inconsistency in the network topology that may be transient (caused by a normal race condition) or permanent (indicated by logs 127 or 128). The session or application will fail with the specified sense code.
Recommended Action If possible, increase the port link-activation limits. Otherwise, check the consistency of the network topology.
Error Message  
%SNASW-4-CS_LOG_27 : EXCEPTION - [int] - Unable to find requested link [chars]
Explanation A session required the SNA switch to activate a link station automatically, but the SNA switch was unable to identify the requested link. This problem usually indicates an inconsistency in the network topology that may be transient (caused by a normal race condition) or permanent (indicated by logs 127 or 128). The session will fail with the specified sense code.
Recommended Action Check the consistency of the network topology.
Error Message  
%SNASW-4-CS_LOG_28 : EXCEPTION - [int] - Unable to activate dynamic link station because owning port is not active [chars]
Explanation A session required the SNA switch to activate a dynamic link station automatically, but the request failed because the owning port was not active. This problem usually indicates an inconsistency in the network topology that may be transient (that is, caused by a normal race condition) or permanent (indicated by logs 127 or 128). The session will fail with the specified sense code.
Recommended Action If possible, increase the port activation limits. Otherwise, check the consistency of the network topology.
Error Message  
%SNASW-4-CS_LOG_29 : EXCEPTION - [int] - Unable to find requested connection network [chars]
Explanation A session required the SNA switch to activate a dynamic link station automatically, but the SNA switch was unable to identify the requested connection network. This problem usually indicates an inconsistency in the network topology that may be transient (caused by a normal race condition) or permanent (indicated by logs 127 or 128). The session will fail with the specified sense code.
Recommended Action Check the consistency of the network topology.
Error Message 
%SNASW-3-CS_LOG_30 : PROBLEM - [int] - Incoming call rejected because port link-activation limits exceeded [chars]
Explanation An incoming call was rejected because the port link-activation limits would be exceeded by this call. The link activation will fail.
Recommended Action If possible, increase the port link-activation limits.
Error Message  
%SNASW-3-CS_LOG_31 : PROBLEM - [int] - The CP name on an XID3 received from adjacent node is different to that expected [chars]
Explanation The CP name on an XID3 that has been received from an adjacent node is different from the expected CP name. The link activation will fail.
Recommended Action If the received adjacent CP name is correct, correct the link station configuration by entering the snasw link command. Depending on other aspects of the link station definition, the CP name check can be disabled by entering the snasw link command with the adj_cp_name field set to all zeros.
Error Message  
%SNASW-3-CS_LOG_32 : PROBLEM - [int] - The node ID on an XID3 received from a back-level node is different to that expected [chars]
Explanation The node ID on an XID3 received from a back level node is different from the expected node ID. The link activation will fail.
Recommended Action If the received node ID is correct, correct the link station configuration by entering the snasw link command. Depending on other aspects of the link station definition, the node ID check can be disabled by entering the snasw link command with the adj_node_id field set to all zeros.
Error Message  
%SNASW-3-CS_LOG_33 : PROBLEM - [int] - The node type indicated on an XID3 received from an adjacent node is different to that expected [chars]
Explanation The node type indicated on an XID3 received from an adjacent node is different from the expected node type. The link activation will fail.
Recommended Action If the received node type is correct, correct the link station configuration by entering the snasw link command. Depending on other aspects of the link station definition, the node type check can be disabled by entering the snasw link command with the adj_node_type field set to NAP_LEARN_NODE.
Error Message  
%SNASW-3-CS_LOG_34 : PROBLEM - [int] - Both sent and received XIDs indicate the same, non-negotiable, link station role [chars]
Explanation Both sent and received XIDs indicate the same nonnegotiable link station role. The link activation will fail.
Recommended Action Either correct the local port definition or the remote definition so that the link station roles are complementary or at least one link station is negotiable.
Error Message  
%SNASW-4-CS_LOG_35 : EXCEPTION - [int] - Unable to activate link station because port total link-activation limit reached [chars]
Explanation A session or application required the SNA switch to activate a link station automatically, but the request failed because it would have exceeded the port total link-activation limit. This problem usually indicates an inconsistency in the network topology that may be transient (caused by a normal race condition) or permanent (indicated by logs 127 or 128). The session or application will fail with the specified sense code.
Recommended Action Check the consistency of the network topology.
Error Message  
%SNASW-4-CS_LOG_36 : EXCEPTION - [int] - Unable to activate link station because port outbound link-activation limit reached [chars]
Explanation A session or application required the SNA switch to activate a link station automatically, but the request failed because it would have exceeded the maximum number of concurrently active outbound links allowed for the owning port. This number is the total link-activation limit minus the inbound link-activation limit (that part of the total limit reserved for active inbound links). This problem usually indicates an inconsistency in the network topology that may be transient (caused by a normal race condition) or permanent (indicated by logs 127 or 128). The session or application will fail with the specified sense code.
Recommended Action Check the consistency of the network topology.
Error Message  
%SNASW-4-CS_LOG_37 : EXCEPTION - [int] - Unable to activate dynamic link station because port total link-activation limit reached [chars]
Explanation A session required the SNA switch to activate a dynamic link station automatically, but the request failed because it would have exceeded the port total link-activation limit. This problem usually indicates an inconsistency in the network topology that may be transient (caused by a normal race condition) or permanent (indicated by logs 127 or 128). The session will fail with the specified sense code.
Recommended Action Check the consistency of the network topology.
Error Message  
%SNASW-4-CS_LOG_38 : EXCEPTION - [int] - Unable to activate dynamic link station because port outbound link-activation limit reached [chars]
Explanation A session required the SNA switch to activate a dynamic link station automatically, but the request failed because it would have exceeded the maximum number of concurrently active outbound links allowed for the owning port. This number is the total link-activation limit minus the inbound link-activation limit (that part of the total limit reserved for active inbound links). This problem usually indicates an inconsistency in the network topology that may be transient (caused by a normal race condition) or permanent (indicated by logs 127 or 128). The session will fail with the specified sense code.
Recommended Action Check the consistency of the network topology.
Error Message  
%SNASW-6-CS_LOG_39 : INFO - [int] - Link station to host started [chars]
Explanation A non-APPN link station to an upstream host has been successfully started.
Recommended Action No action is required.
Error Message 
%SNASW-6-CS_LOG_40 : INFO - [int] - Link station to DSPU started [chars]
Explanation A non-APPN link station to a downstream PU has been successfully started.
Recommended Action No action is required.
Error Message  
%SNASW-6-CS_LOG_41 : INFO - [int] - Link station to host stopped [chars]
Explanation A non-APPN link station to an upstream host has been successfully stopped.
Recommended Action No action is required.
Error Message  
%SNASW-6-CS_LOG_42 : INFO - [int] - Link station to DSPU stopped [chars]
Explanation A non-APPN link station to a downstream PU has been successfully stopped.
Recommended Action No action is required.
Error Message  
%SNASW-4-CS_LOG_43 : EXCEPTION - [int] - Unable to find requested link [chars]
Explanation A locally initiated dependent session activation request required the SNA switch to automatically activate a link to a specified PU name, but the SNA switch was unable to identify the a link to the PU. This problem indicates an inconsistent local configuration that is transient and is caused by a recent modification. The session activation request will fail with the specified sense code.
Recommended Action Check the consistency of the local configuration. Link definitions can be viewed by entering the show snasw link command.
Error Message  
%SNASW-6-CS_LOG_44 : INFO - [int] - SNA Switch link started [chars]
Explanation An SNA switch link has been successfully started.
Recommended Action No action is required.
Error Message 
%SNASW-3-CS_LOG_51 : PROBLEM - [int] - Intra-node session support ended abnormally [chars]
Explanation Intranode session support has ended abnormally. This condition should occur only because of a shortage of available storage. Any active intranode sessions will fail, and no more intranode sessions can be activated.
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch.
Error Message  
%SNASW-4-CS_LOG_52 : EXCEPTION - [int] - Unable to find requested connection network [chars]
Explanation A session required the SNA switch to activate a dynamic link station automatically, but the SNA switch was unable to identify the requested connection network TG. This problem usually indicates an inconsistency in the network topology that may be transient (caused by a normal race condition) or permanent (indicated by logs 127 or 128). The session will fail with the specified sense code.
Recommended Action Check the consistency of the network topology.
Error Message  
%SNASW-3-CS_LOG_54 : PROBLEM - [int] - Insufficient storage to generate link Alert [chars]
Explanation Available storage was insufficient for generating a link alert. The alert will not be sent.
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch.
Error Message  
%SNASW-6-CS_LOG_55 : INFO - [int] - HPR-capable SNA Switch link started [chars]
Explanation An SNA switch link has been successfully started on a node that supports HPR.
Recommended Action No action is required.
Error Message  
%SNASW-6-CS_LOG_56 : INFO - [int] - SNA Switch link stopped [chars]
Explanation An SNA switch link has been successfully stopped.
Recommended Action No action is required.
Error Message  
%SNASW-6-CS_LOG_57 : INFO - [int] - DLC started [chars]
Explanation A DLC has been successfully started.
Recommended Action No action is required.
Error Message  
%SNASW-6-CS_LOG_58 : INFO - [int] - DLC stopped [chars]
Explanation A DLC has been successfully stopped.
Recommended Action No action is required.
Error Message  
%SNASW-6-CS_LOG_59 : INFO - [int] - Port started [chars]
Explanation A port has been successfully started.
Recommended Action No action is required.
Error Message 
%SNASW-6-CS_LOG_60 : INFO - [int] - Port stopped [chars]
Explanation A port has been successfully stopped.
Recommended Action No action is required.
Error Message  
%SNASW-4-CS_LOG_61 : EXCEPTION - [int] - Unable to start requested CP-CP sessions with adjacent node [chars]
Explanation The specified link is configured to support CP-CP sessions, but these sessions could not be started. This condition could have occurred either because the remote node is not configured to support CP-CP sessions on this link or because both the local and remote nodes are end nodes. CP-CP sessions are not allowed to be started on end nodes. CP-CP sessions will not be established.
Recommended Action Correct the configuration mismatch, either by removing CP-CP sessions support from the local connection definition or by adding it to the connection definition of the adjacent node.
Error Message  
%SNASW-3-CS_LOG_62 : PROBLEM - [int] - Failed to create DLC [chars]
Explanation A DLC could not be started either because of insufficient resources or because the specified DLC type is not supported. The DLC is inoperative.
Recommended Action If the DLC type is supported, either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch.
Error Message  
%SNASW-3-CS_LOG_63 : PROBLEM - [int] - Pre-defined TG number does not match that sent by adjacent node [chars]
Explanation The specified link station is configured with a predefined TG number, but the adjacent node has sent a different nonzero TG number. Link activation will fail.
Recommended Action Correct the mismatched TG number configuration at this node or at an adjacent node by entering the snasw link command.
Error Message  
%SNASW-3-CS_LOG_64 : PROBLEM - [int] - Adjacent node sent a TG number that was pre-assigned to another LS [chars]
Explanation An adjacent node has attempted to use for this link a TG number that is already defined on another link station. Link activation will fail.
Recommended Action Correct the mismatched TG number configuration at this node or at an adjacent node by entering the snasw link command.
Error Message  
%SNASW-3-CS_LOG_65 : PROBLEM - [int] - Adjacent node sent a TG number that was already in use by another LS [chars]
Explanation An adjacent node has attempted to use a TG number for this link that is already in use by another link station. This may indicate an interoperability problem. Link activation will fail.
Recommended Action Run a trace on the link station or port to get more diagnostic information on the problem and contact your Cisco technical support representative with the log and trace information.
Error Message  
%SNASW-6-CS_LOG_66 : INFO - [int] - Adjacent node has changed its CP name [chars]
Explanation An adjacent node has changed its CP name.
Recommended Action No action is required.
Error Message  
%SNASW-3-CS_LOG_67 : PROBLEM - [int] - Insufficient storage to update topology database with link station [chars]
Explanation Available storage was insufficient for updating the topology database with link station information. The topology will be inconsistent, and this condition may result in unexpected session activation failures (typically with the sense code 8014xxxx, 0806002B, or 08500001).
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch. Cycling the specified link station either by activating and then deactivating, or by deactivating then activating may clear the condition.
Error Message  
%SNASW-3-CS_LOG_68 : PROBLEM - [int] - Insufficient storage to update topology database with connection network [chars]
Explanation Available storage was insufficient for updating the topology database with connection network information. The topology will be inconsistent, and this condition may result in unexpected session activation failures (typically with the sense code 8014xxxx, 0806002B, or 08500001).
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch. Cycling the specified port either by activating and then deactivating, or by deactivating then activating may clear the condition.
Error Message  
%SNASW-3-CS_LOG_69 : PROBLEM - [int] - Insufficient storage to enable intra-node sessions [chars]
Explanation Available storage was insufficient for enabling intranode sessions. Intranode session cannot be activated.
Recommended Action Either decrease the system load (for example, by reducing the number of active sessions) or make more storage available to the SNA switch.
Error Message 
%SNASW-6-CS2_LOG_0 : INFO - [int] - Implicit link limit on port reached [chars]
Explanation An implicit, dynamic, or discovery link could not be activated because the implicit link limit defined on the port has been reached or exceeded. The link type being activated is as follows:
•1—dynamic

•3—implicit

•4—discovery

Recommended Action No action is required.
Error Message 
%SNASW-4-CS2_LOG_2 : EXCEPTION - [int] - Link activation race detected - local node responsible for disconnect [chars]
Explanation A link activation race was detected on an ATM port. The local node is responsible for resolving this race. The local node will disconnect its link. The link activation request made by the remote node will succeed.
Recommended Action This is a normal race condition. No action is required.
Error Message 
%SNASW-4-CS2_LOG_3 : EXCEPTION - [int] - Link activation race detected - adjacent node responsible for disconnect [chars]
Explanation A link activation race was detected on an ATM port. The remote node is responsible for resolving this race. The local node will send a negotiation error CV indicating that the remote link activation request should fail. The link activation request made by the local node will succeed.
Recommended Action This is a normal race condition. No action is required.
Error Message 
%SNASW-4-CS2_LOG_4 : EXCEPTION - [int] - PORT_BANDWIDTH_UPDATE (status = QUIESCING) received [chars]
Explanation A PORT_BANDWIDTH_UPDATE signal with status set to QUIESCING has been received. Any Connection Network TGs on this port will be advertised as quiescing. Any TGs that can normally be activated automatically will be advertised as nonoperational.
Recommended Action If possible, increase the bandwidth available to the local port.
Error Message  
%SNASW-4-CS2_LOG_5 : EXCEPTION - [int] - PORT_BANDWIDTH_UPDATE (status = OK) received [chars]
Explanation A PORT_BANDWIDTH_UPDATE signal with status set to OK has been received. Any Connection Network TGs on this port that had been advertised as quiescing will be advertised as active. Any TGs that can normally be activated automatically that had been advertised as nonoperational will be advertised as operational.
Recommended Action To avoid future problems with bandwidth shortage, increase the bandwidth available to the local port.
Error Message  
%SNASW-3-CS2_LOG_9 : PROBLEM - [int] - DLC failure during creation [chars]
Explanation The DLC has returned inconsistent data during creation. The DLC will be destroyed, and all ports and link stations defined on the DLC will be inoperative.
Recommended Action Run a trace on the DLC and contact your Cisco technical support representative with the log and trace information.
Error Message 
%SNASW-4-CS2_LOG_10 : EXCEPTION - [int] - Link activation retry limit reached [chars]
Explanation An automatic retry link station is still inactive after the maximum allowed number of retries. The link station will remain inactive awaiting operator intervention. In the meantime, the activation of any sessions relying on this link station will fail.
Recommended Action Check the surrounding logs for link activation failures. Check the configuration of the link station. Check the state of the adjacent node. Enter the snasw start link command to retry activation.
Error Message 
%SNASW-4-CS2_LOG_11 : EXCEPTION - [int] - A request to activate a connection network TG was rejected because the local and destination link addresses were incompatible [chars]
Explanation The SNA switch cannot start a link to an adjacent node over a connection network TG because the link address on the local node is not compatible with the link address on the adjacent node. The session will fail with the specified sense code.
Recommended Action Check the local and destination link addresses.
Error Message  
%SNASW-4-CS2_LOG_12 : EXCEPTION - [int] - A request to activate a connection network TG was rejected because a defined link was already active between the local and destination address and multiple links are not supported [chars]
Explanation The SNA switch cannot start a link to an adjacent node over a connection network TG because the DLC does not support multiple links between the local and destination addresses. The session will fail with the specified sense code.
Recommended Action Check the local and destination link addresses.
Error Message 
%SNASW-4-CS2_LOG_25 : EXCEPTION - [int] - Insufficient resources to (un)register adjacent LEN [chars]
Explanation A branch network node has insufficient resources to register or unregister an adjacent LEN node. The directory of this node and that of its NNS may become inconsistent because the LEN CP will still be present when it should not be present, or vice versa. Therefore, session activation to the LEN may fail when a link to it is active, or neighboring nodes may show the LEN as able to be contacted when the link to it is down.
Recommended Action Ensure that sufficient resources are available to the SNA switch and then recycle the link to the required state.
Error Message  
%SNASW-4-CS2_LOG_26 : EXCEPTION - [int] - Invalid TG descriptor received from DLUS [chars]
Explanation An invalid TG descriptor was received from a DLUS. The PU will not be activated.
Recommended Action Check the configuration of the DLUS named by this log. Copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message  
%SNASW-4-CS2_LOG_27 : EXCEPTION - [int] - A DLUS-defined downstream DLUR-served link could not be defined [chars]
Explanation A DLUS-defined downstream DLUR-served link could not be defined because either the specified port does not exist or there is an existing link station to the same destination address. The PU will not be activated.
Recommended Action Correct the configuration.
Error Message  
%SNASW-4-CS2_LOG_28 : EXCEPTION - [int] - A DLUS-defined downstream DLUR-served link failed to activate [chars]
Explanation A DLUS-defined downstream link failed to activate. The PU will not be activated.
Recommended Action Check that the named port is active. Check that the downstream node at the given address is powered on. Check surrounding logs for reasons why the named LS has not activated. Check the configuration of the DLUS.
Error Message  
%SNASW-4-CS2_LOG_29 : EXCEPTION - [int] - DLUS-defined DSPU name clashes with locally-defined DSPU name [chars]
Explanation A DLUS-defined DSPU name clashes with the locally-defined DSPU name of a different PU. An implicit link will fail. The ACTPU for the DSPU connected over this link will be rejected.
Recommended Action Reconfigure this node or the DLUS to remove the duplicate PU name. If the DLUS and the DLUR use the same PU name, then it must refer to the same PU.
Error Message 
%SNASW-4-CS2_LOG_30 : EXCEPTION - [int] - Insufficient information to create a DLUS-defined link to a DLUR DSPU [chars]
Explanation Insufficient information was available to create a DLUS-defined link. A PU will not be activated. The ACTPU for the named PU will be rejected with the given sense code.
Recommended Action Correct the PU definition at the DLUS. The DLUS-defined link could not be created using the information from the DLUS in the TG descriptor (CV x'46') shown below.
For example, for a Token Ring link to be created, the SNA switch requires the x'46' to contain the following subfields:

•x'91'—Signaling information CV specifying EBCDIC 'TR'

•x'92'—Port identifier containing an 8-byte EBCDIC port name

•x'93'—LSAP information containing a 1-byte destination SAP address

•x'94'—MAC information containing a 6-byte destination MAC address
Error Message 
%SNASW-3-DLCBadMessage : DLC unrecognized message, header= [chars]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message  
%SNASW-3-DLCFailure : SNASW failed to process DLC message, header= [chars]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message  
%SNASW-3