-
Cisco IOS System Messages, Volume 2 of 2
-
System Messages Overview
-
MBUF through MODEM
-
MODEM_HIST through NSP
-
NSP_APS through POSDW
-
POSLC through PQUICC_ETHER
-
PQUICC_ETHERNET through RESOURCE_MON
-
RESYNCH through SDLC
-
SDLLC through SNAPSHOT
-
SNASW
-
SNMP through SWITCH_IF
-
SYS through TCPIP
-
TDM through TXCONN
-
UBR7200 through VPD
-
VPDN through XTAGATM
-
Volume 2 Glossary
-
Table Of Contents
SNASW Messages
The following are Systems Network Architecture (SNA) Switching Services 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_7 : PROBLEM - [int] - BIND received with the next hop in the RSCV set to the local node again [chars]
Explanation The SNA switch received a BIND request with a badly formatted RSCV. The local node name shows as the CP name for the next hop in the RSCV again. The session cannot be activated.
Recommended Action 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-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.
–
–
–
–
–
–
–
–
–
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:
–
–
–
–
–
–
–
–
–
–
–
–
–
–
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:
–
–
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:
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
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:
–
–
–
–
–
–
–
–
–
–
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:
–
–
–
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:
–
–
–
–
Error Message%SNASW-3-CS2_LOG_31 : PROBLEM - [int] - Unable to activate port as the IP DLC does not support IP hostnames [chars]
Explanation Unable to activate port because the IP DLC does not support IP hostnames. The START_PORT verb will fail and the port will not restart successfully.
Recommended Action Either choose a different IP DLC that does support IP hostnames or, if IPv4 is being used, specify the local port by IP address instead of IP hostname.
Error Message%SNASW-3-CS2_LOG_32 : PROBLEM - [int] - Unable to start link station as the IP DLC does not support IP hostnames [chars]
Explanation Unable to activate link station because the IP DLC does not support IP hostnames. The START_LS verb will fail and the link station will not restart successfully.
Recommended Action Either choose a different IP DLC that does support IP hostnames or, if IPv4 is being used, specify the link station by IP address instead of IP hostname.
Error Message%SNASW-3-CS2_LOG_33 : PROBLEM - [int] - Unable to start dynamic link as the IP DLC does not support IP hostnames [chars]
Explanation Unable to activate dynamic link station as the IP DLC does not support IP hostnames. Link activation will fail and the link station will not start successfully.
Recommended Action Either choose a different IP DLC that does support IP hostnames or, if IPv4 is being used, specify the link station by IP address instead of IP hostname.
Error MessageExplanation This message provides debugging information for a special image provided by Cisco technical support. The x in the message text represents any number between 0 and 9.
Recommended Action Follow the instructions provided by Cisco technical support for these messages.
Error Message%SNASW-3-DEBUG_LOG_0 : PROBLEM - [int] - SNA Switch DEBUG log [chars]
Explanation This message provides SNA Switch Debug log information
Recommended Action Report this problem to SNA Switch technical support. 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-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-DLCInvalidFsmState : Invalid Input=[chars] to SNASW [chars] [hex] with OldState=[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-DLCPortFailure : Port [chars] activation failed: [chars]
Explanation An error has been received from CLS. This condition typically indicates a configuration error.
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-DLUR_LOG_1 : EXCEPTION - [int] - UNBIND could not be correlated to DLUR-served LU [chars]
Explanation The system is unable to correlate a received UNBIND request with a DLUR-supported session. This is a normal race condition caused by the crossing of UNBIND requests.
Recommended Action No action is required. A positive response will be sent to UNBIND.
Error Message%SNASW-3-DLUR_LOG_2 : PROBLEM - [int] - REQACTPU rejected [chars]
Explanation A DLUS has rejected a REQACTPU with the given sense code. An SSCP-PU session with the given DLUS will not be activated. If a backup DLUS is configured for the PU, a DLUR will attempt to activate the PU via the backup DLUS.
Recommended Action Examine the sense code and retry activation if appropriate.
Error Message%SNASW-4-DLUR_LOG_5 : EXCEPTION - [int] - CPSVRMGR pipe session failure [chars]
Explanation A CPSVRMGR pipe has failed to the specified DLUS. Any PUs using the specified DLUS are deactivated, and a DACTPU(cold) is sent. The DLUR may attempt to contact one or more backup DLUSs, if configured.
Recommended Action If a pipe with backup DLUS is not initiated automatically, manually restart any required PUs.
Error Message%SNASW-4-DLUR_LOG_8 : EXCEPTION - [int] - Inconsistent DLUS Names [chars]
Explanation The DLUS names are inconsistent. The host has requested the activation of a downstream link to a PU by sending an ACTPU. The link is configured to request a different DLUS. The DLUS initiating the activation is used.
Recommended Action No action is required. If the host DLUS is the regular DLUS and not a backup, adjust the downstream link configuration at a convenient time.
Error Message%SNASW-4-DLUR_LOG_9 : EXCEPTION - [int] - Protocol Error from DLUS Host: RU Size too large for SSCP Session [chars]
Explanation A protocol error from a DLUS has occurred. The system has received an RU that is too large for SSCP session. This situation typically occurs when the SSCP sends a LOGON screen that is too large. The data is discarded.
Recommended Action If you are expecting an SSCP LOGON screen, enter your LOGON command as usual.
Error Message%SNASW-4-DLUR_LOG_10 : EXCEPTION - [int] - Failed to contact a DLUS for PU. Retry count exceeded. [chars]
Explanation The DLUR has failed to contact either the DLUS or the backup or default DLUSs after the system has attempted the configured number of retries. No contact is made with the DLUS.
Recommended Action Check the earlier logs for causes of individual failures to contact the host. Resolve any problems or increase the timeout or retry count and try again.
Error Message%SNASW-3-DLUR_LOG_11 : PROBLEM - [int] - Received PLU-SLU BIND request with duplicate FQPCID [chars]
Explanation The system has received a PLU-SLU BIND request with duplicate FQPCID. The session activation will fail with the sense code 083B0002.
Recommended Action 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. Run a trace on the specified link if more diagnostics are required.
Error Message%SNASW-6-DLUR_LOG_12 : INFO - [int] - A pipe to a DLUS has activated [chars]
Explanation A pipe to a DLUS has been activated.
Recommended Action No action is required.
Error Message%SNASW-6-DLUR_LOG_13 : INFO - [int] - A pipe to a DLUS has deactivated [chars]
Explanation A pipe to a DLUS has been deactivated.
Recommended Action No action is required.
Error Message%SNASW-4-DLUR_LOG_14 : EXCEPTION - [int] - An attempt to activate a persistent pipe to a DLUS has failed [chars]
Explanation A DLUR has requested a persistent pipe to a DLUS, but the DLUS does not support persistent pipes. The sense codes are as follows:
–
–
The attempt to activate a persistent pipe to the DLUS will fail.
Recommended Action If the DLUR is unable to contact a different DLUS that does support persistent pipes, then the following should be considered. If the sense code is 088E0009, DLUR requirements for persistent pipes could be removed. Otherwise, the DLUS must be upgraded to support persistent pipes.
Error Message%SNASW-4-DLUR_LOG_15 : EXCEPTION - [int] - A DLUS has sent an ACTPU without a PU name [chars]
Explanation A DLUS has sent an ACTPU without a PU name. The ACTPU will be rejected with the specified sense code. PU activation will not continue.
Recommended Action Check the status of the named DLUS. Check that the named DLUS is correctly configured. Optionally, reconfigure the SNA switch to use a different DLUS.
Error Message%SNASW-4-DLUR_LOG_16 : EXCEPTION - [int] - A DLUS has sent an ACTPU with a PU name that is already in use [chars]
Explanation A DLUS has sent an ACTPU with a PU name that is already in use. The ACTPU will be rejected with the specified sense code. PU activation will not continue.
Recommended Action Reconfigure the DLUS or the DLUR to use different PU names. If the DLUS and the DLUR use the same PU name, then they must apply the name to the same PU.
Error Message%SNASW-4-DLUR_LOG_17 : EXCEPTION - [int] - A DLUS has sent an ACTPU with a PU name different from the name in the last ACTPU received for the same DSPU. [chars]
Explanation A DLUS has sent an ACTPU with a PU name that is different from the PU name in the last ACTPU received for the same DSPU. The PU name of this implicit or DLUS-defined DSPU will change its name to the name from this new ACTPU.
Recommended Action Reconfigure the DLUS or DLUSs in the network to use the same PU name when referring to the same PU.
Error Message%SNASW-4-DLUR_LOG_18 : EXCEPTION - [int] - Failed to contact one or both of the default DLUS when attempting to activate a persistent pipe required by a DLUS-dependent port. The retry count is exceeded. [chars]
Explanation The DLUR has failed to contact either the default primary DLUS, the default backup DLUS, or both after the configured number of retries when attempting to activate a persistent pipe required to enable a DLUS-dependent port. The DLUS-dependent port is not enabled.
Recommended Action Check earlier logs for causes of individual failures to contact the host. Resolve any problems or increase the timeout or retry count and try again.
Error Message%SNASW-6-DLUR_LOG_19 : INFO - [int] - Deactivating a persistent pipe because it is not required [chars]
Explanation The DLUR is deactivating a persistent pipe because it is not required to keep it active.
Recommended Action No action is required.
Error Message%SNASW-4-DLUR_LOG_20 : EXCEPTION - [int] - Invalid MU type received by DLUR [chars]
Explanation An invalid MU type has been received by a DLUR from an internal or downstream PU. The invalid MU will be discarded.
Recommended Action If the PU is internal, contact your Cisco technical support representative with details of this log. If the PU is downstream, contact the supplier of the downstream node.
Error Message%SNASW-4-DLUR_LOG_21 : EXCEPTION - [int] - Different PUs have LUs whose names clash [chars]
Explanation Two LUs having the same name exist under different PUs. One is already activated, and DLUS has attempted to activate the other. The second LU will not be activated.
Recommended Action Rename one of the LUs with a unique network name.
Error Message%SNASW-4-DLUR_LOG_22 : EXCEPTION - [int] - PU not found for REQACTPU RSP or REQDACTPU [chars]
Explanation A REQACTPU RSP or REQDACTPU has been received and the node has not been able to correlate it to a physical unit control block. The REQACTPU RSP or REQDACTPU will be discarded.
Recommended Action Copy the error message exactly as it appears on the console or the system log, contact the supplier of the DLUS, and provide the supplier with the gathered information along with other details of this log.
Error Message%SNASW-4-DLUR_LOG_23 : EXCEPTION - [int] - A REQACTPU RSP has not been received. Possible hung PU problem [chars]
Explanation An REQACTPU RSP has not been received for this PU for two| consecutive iterations of the Hung PU awareness time interval indicated on the show snasw node command. If the condition corrects itself you will see message %SNASW-6-DLUR_LOG_24 indicating the PU is no lunger hung.
Recommended Action Enter the show snasw pu detail command for the PU in question. Contact your Cisco technical support representative to assist in determining the cause of the hung PU. If it is determined that there is just a normal delay in the PU activation sequence (in other words, %SNASW-4-DLUR_LOG_23 is followed each time by %SNASW-6-DLUR_LOG_24), then you can use the hung-pu-awareness keyword on the snasw cpname configuration command to increase the timer value.
Error Message%SNASW-6-DLUR_LOG_24 : INFO - [int] - A PU previously logged as possibly hung is no longer possibly hung [chars]
Explanation A PU that had previously been logged as hung (via message %SNASW-4-DLUR_LOG_23) is now not believed to be hung. This could be because| a REQACTPU RSP or ACTPU REQ was finally received, or could be due to the| cancellation of the REQACTPU REQ (due to a downstream PU outage, a REQDACTPU| RSP, or the loss of the DLUR-DLUS pipe).
Recommended Action No action is required.
Error Message%SNASW-3-DLUR_LOG_25 : PROBLEM - [int] - A new DSPU has activated with the same node ID and CP name as an existing DSPU [chars]
Explanation A DSPU connecting into the node has the same node ID and CP name as an existing active DSPU. The new link will be deactivated.
Recommended Action Change the node ID or CP name on one of the DSPUs.
Error Message%SNASW-4-DS2_LOG_0 : EXCEPTION - [int] - Insufficient resources to (un)register adjacent LEN [chars]
Explanation The 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 or vice versa. Therefore, session activation to the LEN may fail when a link to it is active, or neighboring nodes may believe the LEN to be contactable when the link to is down.
Recommended Action Ensure that sufficient resources are available to the SNA switch and recycle the link to the required state.
Error Message%SNASW-3-DS_LOG_1 : PROBLEM - [int] - Network search not started because it would exceed the maximum number of concurrent locates supported by this node [chars]
Explanation A network search has not started because it would exceed the maximum number of concurrent locates that are supported by this node. The session activation will fail with the specified sense code.
Recommended Action Collect the trace information and report the problem to your Cisco technical support representative.
Error Message%SNASW-4-DS_LOG_2 : EXCEPTION - [int] - Locate search failed: search error [chars]
Explanation A network search for which this node was the originator or the network node server has failed. The most common sense codes are as follows (the sense code is an amalgam of sense codes received from the various nodes that took part in the search):
–
–
–
–
These sense codes usually indicate a transient problem in the network (either a resource shortage or link failure). The session activation will fail with the specified sense code.
Recommended Action Retry the session activation. If the problem persists, 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-DS_LOG_3 : PROBLEM - [int] - Received badly formed Locate from an adjacent node [chars]
Explanation The system has received a badly formed Locate request from an adjacent node. This condition may indicate an interoperability problem. Sense codes are as follows:
–
–
–
CP-CP sessions with the adjacent node 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-3-DS_LOG_4 : PROBLEM - [int] - Insufficient storage to process Locate received from adjacent node [chars]
Explanation Available storage was insufficient for processing a locate request that was received from the adjacent node. CP-CP sessions with the adjacent node will be deactivated to avoid possible deadlocks.
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-DS_LOG_5 : EXCEPTION - [int] - Received Locate with no Find GDS variable [chars]
Explanation A locate request has been received with no Find GDS variable. The locate request is discarded.
Recommended Action No action is required.
Error Message%SNASW-3-DS_LOG_9 : PROBLEM - [int] - Insufficient storage for CP-CP sessions [chars]
Explanation Available storage is insufficient for CP-CP sessions. CP-CP sessions 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-DS_LOG_10 : EXCEPTION - [int] - CP-CP sessions deactivated while broadcast Locate outstanding [chars]
Explanation CP-CP sessions have been deactivated while a broadcast locate was in process. Session activation may fail.
Recommended Action This log flags that a session failure impacted a pending broadcast locate. Other more specific logs give reasons for the session failure and appropriate actions.
Error Message%SNASW-3-DS_LOG_11 : PROBLEM - [int] - Received registration or deletion request from an unknown end node [chars]
Explanation The system has received a registration or deletion request from an unknown end node. This condition may indicate an interoperability problem, but is not considered fatal. The registration request is discarded.
Recommended Action No action is required.
Error Message%SNASW-3-DS_LOG_12 : PROBLEM - [int] - Insufficient storage to register resources owned by a served end node [chars]
Explanation Available storage was insufficient for registering resources owned by a served end node. The specified resource will not be registered, and the registration request has been rejected. Network searches for the resource may fail if the end node is unable to register it.
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-DS_LOG_13 : PROBLEM - [int] - Resource registration failure: resource already registered [chars]
Explanation The system has failed to register a resource for a served end node because the resource is already registered, but with a different parent resource. This situation typically occurs when the same LU is defined on two or more end nodes. The registration request is rejected, and as a result other resources may not be registered and subsequent network searches may fail.
Recommended Action Remove or rename the LU on one of the end nodes.
Error Message%SNASW-3-DS_LOG_14 : PROBLEM - [int] - Registration failure notification received from network node server is badly formed [chars]
Explanation The registration failure GDS variable received from the network node server is badly formed. This condition may indicate an interoperability problem. CP-CP sessions to the node 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-DS_LOG_15 : PROBLEM - [int] - Link/session failure while registering resources with network node server [chars]
Explanation A link or session failure occurred while resources were being registered with the network node server. CP-CP sessions to the node will be deactivated.
Recommended Action This log flags that a registration request was disrupted by the link or session failure. Other more specific logs give details on the reasons for the failure and suggest appropriate actions.
Error Message%SNASW-3-DS_LOG_17 : PROBLEM - [int] - Protocol error while registering resources with network node server [chars]
Explanation A protocol error occurred while resources were being registered with the network node server. CP-CP sessions to the node 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-4-DS_LOG_18 : EXCEPTION - [int] - Locate search timed out [chars]
Explanation The local node has not received a Locate response from the adjacent node for the Locate timeout interval indicated in the show snasw node command. This condition typically indicates a problem in another node in the network that is not responding to Locates. The local node will fail the Locate with one of the following sense codes:
–
–
Recommended Action Try to determine which node along the Locate path is not responding. If the end result of the diagnosis is that delays longer than the Locate timeout interval are normal in your environment, then you can use the locate-timeout keyword on the snasw cpname configuration command to increase (or disable) the locate-timeout timer.
Error Message%SNASW-3-DS_LOG_21 : PROBLEM - [int] - Served end node attempted to delete a home directory entry [chars]
Explanation A served end node has attempted to delete a directory entry that is defined as a home entry at this node. This situation normally occurs when the snasw location command has been used to define LUs owned by served end or LEN nodes. The delete request is rejected with the specified sense code.
Recommended Action Enter the no snasw location command to remove the home entry from the directory.
Error Message%SNASW-4-DS_LOG_22 : EXCEPTION - [int] - Served end node attempted to delete a non-existant directory entry [chars]
Explanation A served end node has attempted to delete a directory entry that does not exist. This condition is normally caused by a network race condition that causes the delete request to arrive when the resource has not been registered. The delete request is rejected with the specified sense code.
Recommended Action No action is required.
Error Message%SNASW-3-DS_LOG_23 : PROBLEM - [int] - Served end node attempted to delete a resource it doesn't own [chars]
Explanation A served end node has attempted to delete a resource when it was not registered as the owner of the resource. This condition may indicate an interoperability problem. The Delete request is rejected with the specified sense code. This result may cause the end node to deactivate CP-CP sessions.
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-DS_LOG_24 : PROBLEM - [int] - Received Register/Delete GDS variable containing format errors [chars]
Explanation They system has received from a served end node a Register or Delete GDS variable that contained format errors. Sense codes are as follows:
–
–
The resources specified will not be registered.
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-DS_LOG_26 : PROBLEM - [int] - Unable to register resources because this node is not authorised at the network node server [chars]
Explanation The network node server has rejected a Register request with a sense code indicating that this node is not authorized to register resources at the network node. This condition usually indicates a mismatch between the configuration of the network node server (to consider this end node unauthorized) and the configuration of this node (to register resources). No further resource registration will occur until CP-CP sessions have been deactivated and reestablished.
Recommended Action Modify the network node server configuration to consider this node authorized.
Error Message%SNASW-3-DS_LOG_27 : PROBLEM - [int] - Unable to register resources because the network node server's directory is full [chars]
Explanation A resource registration failed because the directory of the network node server is full. This condition may indicate a shortage of storage at the network node or a configured upper bound on the size of its directory. No further resource registration will occur until CP-CP sessions have been deactivated and reestablished.
Recommended Action Increase the size of the directory at the network server. This action may be a simple configuration change, or it may require freeing up storage by reducing the load at the server.
Error Message%SNASW-3-DS_LOG_28 : PROBLEM - [int] - Resource registration failed because the resource conflicted with an existing entry in the network node's directory [chars]
Explanation A resource registration has failed because the resource conflicted with existing resources in the directory of the network node server. This condition most commonly occurs when two LUs having the same name are defined on two different end nodes that are being served by the same network node. This condition may also occur if the network node has a home directory entry defined for the same resource. Registration of the resource in question will fail, but other resources should still be registered correctly.
Recommended Action Check the directory of the network node for the duplicate entry. If the duplicate entry is a home entry, remove the home entry from the directory. If the duplicate entry is a registered entry that is owned by a different end node, redefine the LU to use a different name.
Error Message%SNASW-3-DS_LOG_29 : PROBLEM - [int] - Resource registration failed because network node server detected a protocol error in the Register request [chars]
Explanation A resource registration has failed because the network node server detected a protocol error in the Register request. This condition may indicate an interoperability problem. Registration of the resource in question will fail, but other resources should still be registered correctly.
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-DS_LOG_30 : PROBLEM - [int] - Resource registration failed with an unknown sense code [chars]
Explanation A resource registration has failed with an unknown sense code. This condition may indicate an interoperability problem. No further resource registration will occur until CP-CP sessions have been deactivated and reestablished.
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-DS_LOG_31 : PROBLEM - [int] - Delete failure reply received with sense code that is unrecoverable [chars]
Explanation A Delete reply has been received with an unrecoverable sense code. CP-CP sessions to the node 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-DS_LOG_32 : PROBLEM - [int] - Unable to correlate received Register or Delete reply to a directory entry [chars]
Explanation A directory error correlator was returned on a register, or a delete reply cannot be correlated to a directory entry. This condition is considered a protocol error and may indicate an interoperability problem. CP-CP sessions to the node 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-DS_LOG_33 : PROBLEM - [int] - Unable to delete resources because this node is not authorised at the network node server [chars]
Explanation The network node server has rejected a delete request with a sense code indicating that this node is not authorized to register resources at the network node. This situation usually indicates a mismatch between the configuration of the network node server (to consider this end node unauthorized) and the configuration of this node (to register resources). No further resource registration or deletion will occur until CP-CP sessions have been deactivated and reestablished.
Recommended Action Modify the network node server configuration to consider this node authorized.
Error Message%SNASW-4-DS_LOG_34 : EXCEPTION - [int] - Delete request failed because the resource was not found or not removable [chars]
Explanation A delete request has failed, either because the entry was defined as a home entry at the network node server or because the resource was not found. Neither error is severe, and neither will affect future registration, deletion, or other aspects of network operation. Further deletion and registration will continue unaffected.
Recommended Action No action is required.
Error Message%SNASW-4-DS_LOG_35 : EXCEPTION - [int] - Register GDS variable received with an invalid resource name [chars]
Explanation A resource name in the received register request is invalid. The register request 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-4-DS_LOG_36 : EXCEPTION - [int] - Central Resource Registration failure [chars]
Explanation A central resource registration failure has occurred. Network performance may degrade because of additional broadcast Locate searches.
Recommended Action No action is required.
Error Message%SNASW-4-DS_LOG_37 : EXCEPTION - [int] - Central Resource Registration failure: invalid correlator received [chars]
Explanation A central resource registration failure has occurred. An invalid correlator has been received. Network performance may degrade because of additional broadcast locate searches.
Recommended Action No action is required.
Error Message%SNASW-6-DS_LOG_38 : INFO - [int] - Central Directory Server located [chars]
Explanation The central directory server has been located.
Recommended Action No action is required.
Error Message%SNASW-3-DS_LOG_40 : PROBLEM - [int] - Locate received from adjacent node exceeded the maximum number of concurrent locates supported by this node [chars]
Explanation A locate has been received from an adjacent node that exceeded the maximum number of concurrent locates that are supported by this node. CP-CP sessions with the adjacent node will be deactivated to avoid possible deadlocks.
Recommended Action The network will recover from this problem and CP-CP sessions will be reactivated. If the problem persists, collect trace information and report it to a Cisco technical support representative.
Error Message%SNASW-3-DS_LOG_41 : PROBLEM - [int] - Insufficient storage to start a network search [chars]
Explanation Available storage was insufficient for starting a network search. The session activation will fail with the specified sense code.
Recommended Action Make more resources available to the SNA switch.
Error Message%SNASW-3-DS_LOG_42 : PROBLEM - [int] - CP-CP sessions deactivated while directed Locate outstanding [chars]
Explanation CP-CP sessions are deactivated while the directed locate is in process. Session activation may fail.
Recommended Action This log flags that a session failure impacted a pending directed locate. Other, more specific logs give reasons for the session failure and appropriate actions.
Error Message%SNASW-6-DS_LOG_43 : INFO - [int] - Locate search failed: LU not found [chars]
Explanation A network search for which this node was the originator or the network node server has failed to locate the target LU. This condition may be caused by an incorrect target LU name, an inoperative target system, or link errors in the backbone of the network. The session activation will fail with the specified sense code.
Recommended Action If the target LU name is correct, check that the system on which the LU is defined is active. If the system is active, check the topology of the network to ensure that the target system or its network node server is reachable from this node.
Error Message%SNASW-4-DS_LOG_44 : EXCEPTION - [int] - CP-CP sessions established with end node: invalid directory entry removed [chars]
Explanation CP-CP sessions have been established with an adjacent end node that was previously defined using the snasw location command. The invalid directory definitions for the end node and any of its LUs will be removed.
Recommended Action Do not configure the invalid entries in the future.
Error Message%SNASW-3-DS2_LOG_1 : PROBLEM - [int] - Inaccurate directory entry held for this LU [chars]
Explanation A directed locate for this LU has been tried, but the LU was not recognized at the end node stored in the directory. The directory entry is removed, and a broadcast locate is sent instead.
Recommended Action No action is required.
Error Message%SNASW-4-DS2_LOG_2 : EXCEPTION - [int] - Failed to register resource with NNS/CDS [chars]
Explanation The system has failed to allocate memory for storage of a resource in the register list. Registration will not take place immediately.
Recommended Action No action is required.
Error Message%SNASW-4-DS2_LOG_3 : EXCEPTION - [int] - Received a Locate reply with an invalid RSCV [chars]
Explanation A locate reply has been received that contained an invalid RSCV. The locate request that solicited the reply may have failed.
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-DS2_LOG_4 : EXCEPTION - [int] - Insufficient resources to register adjacent LEN LU [chars]
Explanation A branch network node has insufficient resources to register the LU of an adjacent LEN node. The directory of this node and/or that of its NNS may become inconsistent because the LEN LU will not be registered when it should be. Therefore, session activation to the LEN LU may fail when a link to it is active.
Recommended Action Ensure that sufficient resources are available to the SNA switch, and then recycle the link to the required state.
Error Message%SNASW-3-DS2_LOG_5 : PROBLEM - [int] - LEN LU registration failed because the LU name is already registered as the child of a different CP [chars]
Explanation The node has been configured to register LEN LU names when BINDs from LEN nodes are passed through. In this case, registration failed because of a resource name conflict. The LU name is already registered as the child of a different CP. Registration of the resource in question will fail, so sessions to the LEN LU cannot be started except by the LEN itself. Other resources should still be registered correctly.
Recommended Action Check the directory of the network node directory for the duplicate entry. If it is a home entry, remove the home entry from the directory. If it is a registered entry owned by a different end node, redefine the LU to use a different name.
Error Message%SNASW-4-DS2_LOG_6 : EXCEPTION - [int] - Duplicate FQPCID prevents start of network search [chars]
Explanation A LOCATE message with a duplicate PCID has been received. This condition could occur if two LEN nodes send BINDs to SNA the switch at the same time and with the same PCID. Session activation will fail with the specified sense code.
Recommended Action No action is required. The downstream system should retry the session activation using a different PCID.
Error Message%SNASW-4-DS2_LOG_7 : EXCEPTION - [int] - Adjacent node registered an Associated Resource which was not an ENCP [chars]
Explanation The local node is a Branch Network Node or Network Node, and a downstream node registered an Associated Resource that was not an ENCP resource.
Recommended Action No action is required. The node will force the resource type to be ENCP.
Error Message%SNASW-3-EVENT : [chars]
Explanation This message indicates that an informational event has occurred.
Recommended Action No action is required.
Error Message%SNASW-4-HPR_LOG_0 : EXCEPTION - [int] - HPR Route Setup RU received with format errors [chars]
Explanation An HPR Route Setup RU has been received with format errors. The message cannot be processed and will be discarded.
Recommended Action Report the error to the remote end.
Error Message%SNASW-4-HPR_LOG_1 : EXCEPTION - [int] - Unable to correlate HPR Route Setup RU [chars]
Explanation The system is unable to correlate an HPR route setup reply. The message cannot be processed and will be discarded.
Recommended Action Report the error to the remote end.
Error Message%SNASW-3-HPR_LOG_2 : PROBLEM - [int] - Unable to activate RTP connection [chars]
Explanation The system is unable to activate the RTP connection. In certain situations, the origin may retry activation.
Recommended Action Examine the sense code and retry activation, if appropriate.
Error Message%SNASW-4-HPR_LOG_3 : EXCEPTION - [int] - Link failure caused HPR route setup request to be dropped [chars]
Explanation A link failure has occurred between this node and the source of the route setup request. The route setup request is dropped by this node. The partner node on that link should generate a negative reply.
Recommended Action Investigate the link failure.
Error Message%SNASW-4-HPR_LOG_4 : EXCEPTION - [int] - HPR manager failed to obtain memory to send indication [chars]
Explanation The HPR manager failed to get memory to send an RTP indication. The data_lost flag will be set in the next successfully sent indication.
Recommended Action Investigate the memory shortage.
Error Message%SNASW-4-HPR_LOG_5 : EXCEPTION - [int] - NLP received with format errors [chars]
Explanation An NLP has been received with format errors. The message cannot be processed and will be discarded.
Recommended Action Report the error to the remote end.
Error Message%SNASW-4-HPR_LOG_6 : EXCEPTION - [int] - NLP received for RTP connection which no longer exists [chars]
Explanation An NLP has been received for an RTP connection that no longer exists. The message cannot be processed and will be discarded.
Recommended Action Report the error to the remote end.
Error Message%SNASW-4-HPR_LOG_8 : EXCEPTION - [int] - Connection Setup NLP received for previous NCE instance [chars]
Explanation A connection setup NLP has been received that specified a previous instance of this NCE. The NCE must have been shut down and restarted since processing the route setup request. No RTP connection can be started; therefore, the NLP will be discarded.
Recommended Action Report the error to the remote end.
Error Message%SNASW-4-HPR_LOG_9 : EXCEPTION - [int] - Local node has received a HPR Route Setup RU that it cannot forward because the next hop is not HPR-capable so is replying with the backout sense code [chars]
Explanation The local node has received an HPR Route Setup RU that it cannot forward because the next hop in the route is not HPR-capable. The local node does not support RTP, so the local node cannot act as the destination node and replies with the backout sense code. The route setup between the origin node and the destination will fail. RTP connections cannot be activated between these two nodes. This is a normal condition when the local node has a link that is able to be automatically activated to a node that does not support HPR. An intermediate node in the route that supports RTP might be able to take over the role of the destination node for the route setup. If this situation occurs, sessions that originate at or beyond the origin node will use HPR from the origin to the new destination and use ISR from the new destination to the local node and beyond it. If no intermediate node is able to act as the destination, HPR will not be used at all by such sessions.
Recommended Action No action is required.
Error Message%SNASW-4-HPR_LOG_10 : EXCEPTION - [int] - Local node has received a HPR Route Setup RU that it cannot forward because the next hop is not HPR-capable so is acting as the new destination [chars]
Explanation The local node has received an HPR Route Setup RU that it cannot forward because the next hop in the route is not HPR-capable. The local node supports RTP, so the local node can act as the destination. The Route Setup will be between the origin node and the local node, which is the new destination. RTP connections will be activated between these two nodes. This is a normal event when the local node has a link that is able to be automatically activated to a node that does not support RTP. Sessions that originate at or beyond the origin node will use HPR from the origin to the new destination and use ISR from and the new destination and beyond it.
Recommended Action No action is required.
Error Message%SNASW-4-HPR_LOG_11 : EXCEPTION - [int] - The local node is acting as the new destination for a backed-out Route Setup [chars]
Explanation The local node has received an HPR Route Setup Reply that contains the backout sense code and is able to act as the new destination for the Route Setup. The Route Setup has been successfully backed out. The Route Setup is between the origin node and the local node (the new destination). RTP connections will be activated between these two nodes. This is a normal event when a node in the route has a link that is able to be automatically activated to a node that does not support RTP or HPR. Sessions that originate at or beyond the origin node will use HPR from the origin node to the new destination and use ISR from the new destination and beyond it.
Recommended Action No action is required.
Error Message%SNASW-4-HPR_LOG_12 : EXCEPTION - [int] - A Route Setup has been backed out from the orignal destination to the new destination [chars]
Explanation The local node has received an HPR Route Setup Reply in which the destination node is not the same as the destination node that was in the corresponding route setup request. The route setup has successfully backed out. The route setup is between the origin node and the new destination. RTP connections will be activated between these two nodes. This is a normal event when a node in the route has a link that is able to be automatically activated to a node that does not support RTP or HPR. Sessions that originate at or beyond the local node will use HPR from the local node to the new destination and use ISR from new destination and beyond it.
Recommended Action No action is required.
Error Message%SNASW-4-HPR_LOG_13 : EXCEPTION - [int] - A Route Setup Reply has been received with the backout sense code HPR will not be used for this session [chars]
Explanation The local node has received an HPR route setup reply with the backout sense code. The route setup has failed because the destination node does not support RTP. No intermediate node supports RTP and was able to become the new destination. The route setup has failed and HPR will not be used for the session that is being activated. This is a normal event when a node in the route has a link that is able to be automatically activated to a node that does not support RTP or HPR.
Recommended Action No action is required.
Error Message%SNASW-4-HPR_LOG_14 : EXCEPTION - [int] - Local node is the destination of a HPR Route Setup RU but does not support RTP so is replying with the backout sense code [chars]
Explanation The local node has received an HPR route setup RU as the destination node but cannot accept the RU because the local node does not support RTP. The local node replies with the backout sense code. The Route Setup between the origin node and this node will fail. RTP connections cannot be activated between these two nodes. This is a normal event when another HPR-capable node has a link that is able to be automatically activated to this node. It may be possible for an intermediate node in the route that supports RTP to take over the role of the destination node for the route setup. If this condition occurs, sessions that originate at (or beyond) the origin node will use HPR from the origin to the new destination and use ISR from the new destination to the local node and beyond it. If no intermediate node is able to act as the destination, HPR will not be used at all by such sessions.
Recommended Action No action is required.
Error Message%SNASW-4-HPR_LOG_15 : EXCEPTION - [int] - Remote NCE has restarted, so disconnect this RTP connection with previous instance of that NCE [chars]
Explanation A connection setup NLP has been received from a remote NCE that has shut down and restarted. An RTP connection still exists from that NCE before it shut down. The old RTP connection will be disconnected.
Recommended Action No action is required.
Error Message%SNASW-4-HPR_LOG_16 : EXCEPTION - [int] - Unable to activate Route Setup RTP connection [chars]
Explanation The system was unable to activate a Route Setup RTP connection during the processing of a Route Setup Request. The Route Setup Request will fail with the specified sense code. The next route setup request will trigger another attempt to activate the route setup RTP connection.
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-HPR_LOG_17 : EXCEPTION - [int] - Connection Setup NLP rejected because it specified unsupported Topic ID [chars]
Explanation A connection setup NLP was rejected because it specified the CP-CP session or route setup topic ID, but was received on a TG that does not support the Control Flows over an RTP Tower. The CP-CP session or Route Setup RTP connection will fail with the sense code HA0010017.
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-HPR_LOG_18 : EXCEPTION - [int] - HPR Route Setup RU received with existing FQPCID [chars]
Explanation An HPR Route Setup RU has been received with an FQPCID that matches an existing route. The message will be rejected and the route not established.
Recommended Action Report the error to the remote end.
Error Message%SNASW-4-HS_LOG_0 : EXCEPTION - [int] - CRV exchange failed [chars]
Explanation The CRV exchange has failed. This condition indicates that the cryptography keys 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 on the session deactivated problem log (log 271) to identify the local LU and partner LU, and correct the mismatch in the cryptography keys.
Error Message%SNASW-4-HS_LOG_1 : EXCEPTION - [int] - LU6.2 session state error [chars]
Explanation An LU 6.2 session state error has occurred. This may indicate an interoperability problem. Sense codes are as follows:
–
–
–
–
–
–
–
–
–
–
–
–
The session will be deactivated with the specified sense code.
Recommended Action Use the information in the session-deactivated problem log (271) to identify the local LU and partner LU. If conditions warrant, run a trace on the specified link station, contact your Cisco technical support representative with the log and trace information, and provide the representative with the gathered information.
Error Message%SNASW-4-HS_LOG_3 : EXCEPTION - [int] - MU format errors [chars]
Explanation An LU 6.2 session format error has occurred. This may indicate an interoperability problem. Sense codes are as follows:
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
The session will be deactivated with the specified sense code.
Recommended Action Use the information in the session-deactivated problem log (271) to identify the local LU and partner LU. If conditions warrant, run a trace on the specified link station, contact your Cisco technical support representative with the log and trace information, and provide the representative with the gathered information.
Error Message%SNASW-4-HS_LOG_4 : EXCEPTION - [int] - LU6.2 response correlation error [chars]
Explanation An LU 6.2 response correlation error has occurred. This may indicate an interoperability problem. The session will be deactivated with the sense code 200E0000 (uncorrelated positive response, or uncorrelated RTR response).
Recommended Action Use the information from the session-deactivated problem log (271) to identify the local LU and partner LU. If conditions warrant, run a trace on the specified link station, contact your Cisco technical support representative with the log and trace information, and provide the representative with the gathered information.
Error Message%SNASW-4-HS_LOG_5 : EXCEPTION - [int] - LU6.2 session ended abnormally - insufficient storage [chars]
Explanation An LU 6.2 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-HS_LOG_6 : EXCEPTION - [int] - Protocol error during CRV exchange [chars]
Explanation A protocol error has occurred during a CRV exchange. This indicates a possible interoperability problem. Sense codes are as follows:
–
–
–
–
–
–
–
–
–
–
–
–
–
–
The session will be deactivated with the specified sense code.
Recommended Action Use the information in the session-deactivated problem log (271) to identify the local LU and partner LU. Run a trace on the specified link station, contact your Cisco technical support representative with the log and trace information, and provide the representative with the gathered information.
Error Message%SNASW-4-HS_LOG_7 : EXCEPTION - [int] - SIGNAL RU received on full-duplex conversation [chars]
Explanation An incoming SIGNAL RU has been received on a full-duplex conversation. The session will be deactivated with the sense code 10030004.
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-HS_LOG_8 : PROBLEM - [int] - EXPD RU received while previous expedited data remains to be processed [chars]
Explanation An EXPD RU has been received while previously expedited data remains to be processed. The session will be deactivated with the sense code 200F0000.
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-HS_LOG_9 : EXCEPTION - [int] - Insufficient storage to initialise half session [chars]
Explanation Available storage was insufficient for initializing the half session. The half session will fail to activate 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-LDLC_CTRL_LOG_0 : EXCEPTION - [int] - Unable to create a new LDLC_CTRL instance [chars]
Explanation The system was unable to create a new LDLC_CTRL instance. Link activation cannot continue. This condition will result in the failure of an outbound link activation attempt or the rejection of an inbound link activation.
Recommended Action Check the surrounding logs for evidence of buffer congestion. If buffer congestion is causing this failure, either decrease the system load or make more resources available to LDLC.
Error Message%SNASW-4-LDLC_CTRL_LOG_1 : EXCEPTION - [int] - LDLC command frame retry limit exceeded [chars]
Explanation The LDLC command frame retry limit has been exceeded. Link activation will fail, or an active link will be brought down.
Recommended Action Check the connectivity to the remote address
Error Message%SNASW-4-LDLC_CTRL_LOG_2 : EXCEPTION - [int] - LDLC link reported inoperative by underlying media [chars]
Explanation An LDLC link has been reported as inoperative by the underlying media. Link activation will fail, or an active link will be brought down.
Recommended Action Check for faults at the supplied destination address. Check for faults and error conditions in the underlying drivers and media. Check for connectivity in the underlying media. Check for outages on the connection path. Ensure that all the wires are still plugged in.
Error Message%SNASW-4-LDLC_DATA_LOG_0 : EXCEPTION - [int] - Unrecognised NHDR routing instruction [chars]
Explanation The system has received an unrecognized NHDR routing instruction. The specified packet cannot be routed by LDLC and will be discarded. Data may be lost. This condition may indicate an interoperability problem.
Recommended Action Check the surrounding logs for other evidence of interoperability problems. If failures or problems occur, gather a trace of the protocol flows, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNASW-4-LDLC_DATA_LOG_1 : EXCEPTION - [int] - Unrecognised LDLC RU identifier [chars]
Explanation The system has received an unrecognized LDLC RU identifier. This packet cannot be processed by LDLC and will be discarded. Link activation and link deactivation may fail. Data may be lost. This condition may indicate an interoperability problem.
Recommended Action Check the surrounding logs for other evidence of interoperability problems. If failures or problems occur, gather a trace of the protocol flows, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNASW-4-LDLC_DATA_LOG_2 : EXCEPTION - [int] - Unable to grant credit [chars]
Explanation The LDLC is unable to grant further send credit.
Recommended Action Check the surrounding logs for evidence of buffer congestion. If buffer congestion is causing this failure, either decrease the system load or make more resources available to the LDLC.
Error Message%SNASW-6-LDLC_DEBUG_LOG_0 : INFO - [int] - Link activation race has occurred [chars]
Explanation A link activation race has occurred. Link activation will be completed, but the routes may be different in each direction. No other effect will be noticeable.
Recommended Action No action is required.
Error Message%SNASW-4-LDLC_IP_LOG_0 : EXCEPTION - [int] - IPDLC failed to allocate necessary storage [chars]
Explanation The IPDLC could not allocate the necessary storage. Some operations may fail. See other logs.
Recommended Action Either decrease the system load (for example, by reducing the number of active links), or make more storage available to the IPDLC.
Error Message%SNASW-4-LDLC_IP_LOG_1 : EXCEPTION - [int] - IPDLC failed to request a posting [chars]
Explanation The IPDLC failed to request a posting. Link activation may fail or data transmission may be delayed.
Recommended Action Either decrease the system load (for example, by reducing the number of active links), or make more storage available to the IPDLC.
Error Message%SNASW-4-LDLC_IP_LOG_2 : EXCEPTION - [int] - IPDLC failed to grow a link hash table [chars]
Explanation The IPDLC failed to grow a link hash table. Data transmission rates may be marginally degraded.
Recommended Action If there are few instances of this log, the IPDLC has recovered, and no action is required. If this log occurs repeatedly, then either decrease the system load (for example, by reducing the number of active links), or make more storage available to the SNAP-IPDLC.
Error Message%SNASW-4-LDLC_IP_LOG_3 : EXCEPTION - [int] - IPDLC failed to create a UDP stub [chars]
Explanation The IPDLC failed to create a UDP stub. Port activation will fail.
Recommended Action Either decrease the system load (for example, by reducing the number of active links), or make more storage available to the IPDLC.
Error Message%SNASW-4-LDLC_IP_LOG_4 : EXCEPTION - [int] - IPDLC's UDP stub has failed to initialise [chars]
Explanation IPDLC has created a UDP stub, but the UDP stub failed to initialize successfully. Port activation will fail.
Recommended Action Check the surrounding logs and other diagnostics for reports of a failure from a UDP stub process.
Error Message%SNASW-6-LDLC_IP_LOG_9 : INFO - [int] - Invalid IP address specified for a IPDLC link [chars]
Explanation An invalid IP address has been specified for an IPDLC link. The link will fail to start.
Recommended Action Correct the configuration. These settings are supplied in the address information passed to the SNA switch on the SNASw link.
Error Message%SNASW-4-LDLC_IP_LOG_10 : EXCEPTION - [int] - Unable to activate IPDLC port [chars]
Explanation The system was unable to activate an IPDLC port. This condition will result in the failure of a port activation attempt. No further IPDLC operation will be possible until a port is activated successfully.
Recommended Action Check the surrounding logs for evidence of buffer congestion. If buffer congestion is causing this failure, either decrease system load or make more resources available to the IPDLC. Ensure that the necessary facilities are available for the UDP interface to operate correctly. Check that valid DLC-specific configuration data was provided to IPDLC at define time.
Error Message%SNASW-4-LDLC_IP_LOG_11 : EXCEPTION - [int] - Unable to activate IPDLC link [chars]
Explanation The system is unable to activate an IPDLC link. Link activation cannot continue. This condition will result in the failure of an outbound link activation attempt or the rejection of an inbound link activation.
Recommended Action Check the surrounding logs for evidence of buffer congestion. If buffer congestion is causing this failure, either decrease the system load or make more resources available to the IPDLC. Ensure that the necessary facilities are available for the UDP interface to operate correctly. Check that valid DLC specific configuration data was provided to SNAP-IPDLC at define time.
Error Message%SNASW-3-LDLC_IP_LOG_12 : PROBLEM - [int] - The IPDLC UDP stub process has abended - SNAP IPDLC will abend [chars]
Explanation The UDP stub process has ended abnormally. IPDLC will end itself abnormally. All links using SNAP-IPDLC will fail. SNAP-IPDLC will fail.
Recommended Action Check for the UDP/IP problem that caused the UDP stub to end abnormally. If the reason cannot be determined, gather a full trace and contact your Cisco technical support representative.
Error Message%SNASW-4-LDLC_IP_LOG_13 : EXCEPTION - [int] - The UDP stub failed to resolve a host name into an IP address. [chars]
Explanation The UDP stub failed to resolve a host name into an IP address. Port activation will fail.
Recommended Action Check that the host name is configured in the DNS server or in your local hosts file. If this machine uses a DNS server, check that it has the correct IP address for the server, and that the server is reachable. Also check surrounding logs for problems that may be related.
Error Message%SNASW-4-LDLC_IP_LOG_14 : EXCEPTION - [int] - A link activation was attempted for an address that matches an existing link. [chars]
Explanation A link activation was attempted for an address that matches an existing link. The link will fail to start. The existing link is unaffected.
Recommended Action Correct the configuration. These settings are supplied in the address information passed to SNAP APPN on the verb DEFINE_LS.
Error Message%SNASW-4-LDLC_IP_LOG_15 : EXCEPTION - [int] - The UDP stub has detected an error. [chars]
Explanation The UDP Stub has detected an error.
Recommended Action Investigate the logs to help identify the error.
Error Message%SNASW-3-LDLC_IP_LOG_20 : PROBLEM - [int] - Failed to activate LDLC link using IPv4 numerical address from remote host. [chars]
Explanation Failed to resolve remote hostname. Attempt to activate HPR/IP link using IPv4 numerical address supplied by remote host has also failed. The link will fail to start.
Recommended Action Check the DNS configuration.
Error Message%SNASW-6-LM_LOG_0 : INFO - [int] - An LU-SSCP session has been activated for LU type 0,1,2 or 3 [chars]
Explanation An LU-SSCP session has been activated.
Recommended Action No action is required.
Error Message%SNASW-6-LM_LOG_1 : INFO - [int] - A PLU-SLU session has been activated for LU type 0,1,2 or 3 [chars]
Explanation A PLU-SLU session has been activated.
Recommended Action No action is required.
Error Message%SNASW-6-LM_LOG_2 : INFO - [int] - An LU-SSCP session has been deactivated for LU type 0,1,2 or 3 [chars]
Explanation An LU-SSCP session has been deactivated.
Recommended Action No action is required.
Error Message%SNASW-6-LM_LOG_3 : INFO - [int] - A PLU-SLU session has been deactivated for LU type 0,1,2 or 3 [chars]
Explanation A PLU-SLU session has been deactivated.
Recommended Action No action is required.
Error Message%SNASW-3-LM_LOG_4 : PROBLEM - [int] - Insuffcient storage to dyamically define dependent LU with host [chars]
Explanation Available storage was insufficient for dynamically defining a dependent LU with a host. The LU-SSCP session will not 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-3-LM_LOG_5 : PROBLEM - [int] - Insufficient storage to BIND LU type 0,1,2 or 3 PLU-SLU session (as PLU) [chars]
Explanation Available storage was insufficient for a BIND LU type 0, 1, 2, or 3 PLU-SLU session. The BIND request 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-4-LM_LOG_6 : EXCEPTION - [int] - Insufficient storage to send RTM statistics to host [chars]
Explanation Available storage was insufficient for sending 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-LM_LOG_7 : 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-LM_LOG_12 : PROBLEM - [int] - Insufficient storage to activate LU-SSCP session for LU type 0,1,2 or 3 (as SSCP) [chars]
Explanation Available storage was insufficient for activating an LU-SSCP session for LU type 0, 1, 2, or 3. The ACTLU request 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-LM_LOG_13 : PROBLEM - [int] - Insufficient storage to activate LU type 0,1,2 or 3 PLU-SLU session (as SLU) [chars]
Explanation Available storage was insufficient for activating an LU type 0, 1, 2, or 3 PLU-SLU session. 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-LM_LOG_14 : PROBLEM - [int] - Insufficient storage to activate LU-SSCP session for LU type 0,1,2 or 3 (as LU) [chars]
Explanation Available storage was insufficient for activating an LU-SSCP session for LU type 0, 1, 2, or 3. The ACTLU request will not 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-LM_LOG_15 : PROBLEM - [int] - A BIND request received by an LU type 0,1,2 or 3 was rejected by SNA Switch because it failed parameter checks [chars]
Explanation A BIND request was received by an LU type 0,1,2, or 3 that failed parameter checks. The sense codes that apply to this condition are as follows:
–
–
–
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
The BIND request will be rejected with the specified sense code. The PLU-SLU session is not activated.
Recommended Action If possible, investigate the configuration of the system that sent the BIND request. If a configuration error is found, correct it. If the configuration error cannot be found, 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-LM_LOG_16 : PROBLEM - [int] - A BIND request received by an LU type 0,1,2 or 3 was rejected by an application connected to SNA Switch [chars]
Explanation A BIND request that was received by an LU type 0, 1, 2, or 3 was rejected by an application connected to the SNA switch. The BIND request will be rejected with the specified sense code. The PLU-SLU session is not activated.
Recommended Action Investigate why the application rejected the BIND request; the sense code should help with this. It may be necessary to investigate the configuration of the system that sent the BIND request, if this is possible. If a configuration error is found, correct it. If the configuration error cannot be found, 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-LM_LOG_17 : PROBLEM - [int] - A BIND request received by an LU type 0,1,2 or 3 was rejected by SNA Switch because the application connection was not open [chars]
Explanation A BIND request that was received by an LU type 0, 1, 2, or 3 was rejected because the application connection was not open. This condition may be caused by a normal window condition, or it may indicate that the system that sent the BIND request is incorrectly configured or is defective. The BIND request will be rejected with the specified sense code. The PLU-SLU session is not activated.
Recommended Action Investigate the cause of the problem. If the information indicates that the system that sent the BIND request is incorrectly configured, correct the configuration error. If it appears that the system is defective, 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-LM_LOG_18 : EXCEPTION - [int] - An LU-SSCP session activation attempt failed because the SSCP was not suitable [chars]
Explanation An ACTLU was received for an LU from the wrong SSCP. The ACTLU is rejected with the sense code 084B0000. The LU activation attempt fails.
Recommended Action If it is required that the LU accept the ACTLU so that the activation attempt will succeed, change the LU definition so that either the LU requires the SSCP identifier that is received from the SSCP, or the LU accepts any SSCP identifier.
Error Message%SNASW-3-LM_LOG_19 : PROBLEM - [int] - An UNBIND RSP was received at a secondary LU [chars]
Explanation An UNBIND RSP was received at a secondary LU. This is an illegal condition SNA as no UNBIND RQ was sent. The UNBIND RSP is dropped.
Recommended Action The session may not be coming down properly. Check that the dependent LU applications are correctly replying to all signals. If the dependent LU applications are correctly replying to all signals, 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-LM2_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 configured at this LU and the partner LU are inconsistent. The session will be deactivated with the sense code 08350001.
Recommended Action Correct the mismatch in cryptography keys.
Error Message%SNASW-4-LM2_LOG_1 : EXCEPTION - [int] - A conventional half-session has aborted. [chars]
Explanation A critical buffer shortage, protocol error, or CRV exchange protocol error has occurred. This indicates a possible interoperability problem. Sense codes for CRV exchange errors are as follows:
–
–
–
–
–
–
–
–
–
–
–
–
–
–
The session will be deactivated with the specified sense code.
Recommended Action If the surrounding logs indicate a critical congestion, decrease the system load or make more resources available to the SNA switch. If the surrounding logs do not indicate a critical congestion, 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-MIBQueryFailure : Query [chars] failed. NOF primary rc=[hex] secondary rc=[hex].
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-MIBRegisterFailure : [chars] Indication [hex] failed. NOF primary rc=[hex] secondary rc=[hex].
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-MIBTrapFailure : Trap failed. [chars] MIB OID=[chars] index OID=[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-MS_LOG_3 : EXCEPTION - [int] - Insufficient storage to deliver MDS_MU to a registered application [chars]
Explanation Available storage was insufficient for delivering MDS_MU to a registered application. The MU will be returned to the sender indicating that a resource shortage error has occurred.
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-MS_LOG_5 : EXCEPTION - [int] - Memory shortage in processing signal [chars]
Explanation The system was unable to allocate memory to process an incoming TRANSFER_MS_DATA, SEND_MDS_MU, or register signal. The signal will be returned to the sender and note that a resource shortage error has occurred.
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-MS_LOG_6 : EXCEPTION - [int] - MS unable to add time stamp and/or product set id [chars]
Explanation The system was unable to add the product set ID or the date time stamp requested. This condition occurred because of memory shortage or because the addition caused an NMVT to exceed maximum size. Additions will not be made to the signal.
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-MS_LOG_7 : INFO - [int] - Alert data logged [chars]
Explanation TRANSFER_MS_DATA/SEND_MDS_MU data has arrived.
Recommended Action No action is required.
Error Message%SNASW-4-MS_LOG_8 : EXCEPTION - [int] - Memory shortage preventing data log [chars]
Explanation The system was unable to allocate memory and therefore was unable to log data supplied by the user. The data will not be logged.
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-MS_LOG_9 : EXCEPTION - [int] - Unrecognized signal received from application [chars]
Explanation A signal was received that was unrecognized and could not be returned to the sender. The signal memory will be freed.
Recommended Action Check that issued signals are acceptable according to the API specification.
Error Message%SNASW-4-MS_LOG_10 : EXCEPTION - [int] - Alert/Resolution received and cannot be sent [chars]
Explanation A memory failure occurred while the system was trying to allocate space to route a back- level alert or resolution to the parent MS process. The alert or resolution will not be sent. The information will be logged here.
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-MS_LOG_12 : EXCEPTION - [int] - Memory shortage in verb processing [chars]
Explanation The system was unable to allocate control block space to process an incoming verb. The verb will not be processed and will be returned to the sending application with a primary return code of NAP_UNEXPECTED_SYSTEM_ERROR.
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-MS_LOG_13 : EXCEPTION - [int] - Memory shortage in trying to send an alert [chars]
Explanation The system was unable to allocate memory needed to send an alert. The alert will not be sent; however, the sense code of the alert will be logged.
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-MS_LOG_14 : EXCEPTION - [int] - Memory shortage in MDS_MU processing [chars]
Explanation The system was unable to allocate the memory necessary to process an MDS_MU. The MDS_MU will not be processed. If the MDS_MU originated at the local node, the SEND_MDS_MU verb containing the MDS_MU will be returned to the sending application, noting the error. If the MDS_MU did not originate from the local node, an error message will be returned to the originating application.
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-MS_LOG_15 : EXCEPTION - [int] - Correlator clash detected in MDS_MU processing [chars]
Explanation A correlation error was detected while the system was processing an MDS_MU. The MDS_MU will not be processed. If the MDS_MU originated at the local node, the SEND_MDS_MU verb containing the MDS_MU will be returned to the sending application, noting the error. If the MDS_MU did not originate from the local node, an error message will be returned to the originating application. An error message may also be sent to other applications if they are affected by the correlation clash.
Recommended Action Correct the correlator value and reissue the SEND_MDS_MU.
Error Message%SNASW-4-MS_LOG_16 : EXCEPTION - [int] - Insufficient storage to pass Alert data to registered Alert handler [chars]
Explanation Available storage was insufficient for passing an alert to the registered Alert Handler. The alert will not be sent but will be logged.
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-MS_LOG_17 : EXCEPTION - [int] - Following alert failed to be sent to focal point [chars]
Explanation The system received a send failure for an alert that is stored on the send alert queue. No held alert function is available to store the alert until another focal point is established. The alert will not be sent; however, it will be logged.
Recommended Action No action is required.
Error Message%SNASW-4-MS_LOG_18 : EXCEPTION - [int] - Error on alert send not correlated with entries on send alert queue [chars]
Explanation The system was unable to correlate an error received on an alert send with the alerts stored in the send alert queue. Either the send alert queue is too small and the original alert has been deleted, or a previous error prevented the alert from being held on the queue. The alert will not be sent to the focal point.
Recommended Action Determine if a prior memory shortage caused the alert not to be held on the queue.
Error Message%SNASW-3-MS_LOG_22 : PROBLEM - [int] - Error message received reporting invalid format of our MDS_MUs [chars]
Explanation MS capabilities has received an error message that reports a format error has occurred on an MDS_MU that the local node has sent. The error message will be logged; however, no further action can be taken. Ignoring the message may lead to further unexpected occurrences.
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-MS_LOG_23 : EXCEPTION - [int] - MS Capabilities unable to send request due to memory shortage [chars]
Explanation MS capabilities failed to get space to send a message and the message will not be sent. If the intended message was a request for focal point services, MS will pursue focal point services alternatively. If the intended message was to revoke a previous focal point, the message will not be sent. The node will still appear in the focal point sphere of control list.
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-MS_LOG_24 : EXCEPTION - [int] - Error message received at MS Capabilities (delivery failure) [chars]
Explanation MS Capabilities has received an error message. This message is assumed to be the result of a send failure. The error message received will be logged so that send failure types can be examined. MS capabilities will take appropriate recovery action if the failed send affects the focal point table.
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-MS_LOG_27 : EXCEPTION - [int] - Memory Failure in MDS creation sequence [chars]
Explanation MDS failed to get needed memory during the creation sequence. The MDS creation 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-MS_LOG_28 : EXCEPTION - [int] - Insufficient storage to process received MS Capabilities information [chars]
Explanation Available storage was insufficient for processing the received MS Capabilities information. The category for which this failure occurred will be reset.
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-MS_LOG_29 : EXCEPTION - [int] - Parsing error found in MDS_MU header [chars]
Explanation The MDS has received an MDS_MU that it could not parse correctly. An alert will be raised. If the MDS_MU originated from a local application, the SEND_MDS_MU will be returned with the return codes NAP_PARAMETER_CHECK and NAP_INVALID_MDS_MU_FORMAT.
Recommended Action Investigate the syntax of the MDS_MU that was sent, correct the syntax, and reissue the SEND_MDS_MU.
Error Message%SNASW-4-MS_LOG_31 : EXCEPTION - [int] - Insufficient storage to queue Alert/Resolution for error correlation, [chars]
Explanation Available storage was insufficient for queueing an alert or resolution for error correlation. The alert or resolution will not be queued. If an error message regarding the failure to send this alert or resolution is received, MDS will be unable to correlate it. If the alert or resolution is sent successfully, no further problems will result.
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-MS_LOG_32 : EXCEPTION - [int] - MDS unable to get memory to send TP_ENDED [chars]
Explanation The MDS was unable to get a buffer to send TP_ENDED for SEND_TP. TP_ENDED 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-4-MS_LOG_33 : EXCEPTION - [int] - MDS unable to get memory for SNASVCMG session list entry [chars]
Explanation The MDS was unable to get memory for a SNASVCMG session control block. The control block will not be obtained.
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-MS_LOG_34 : EXCEPTION - [int] - Unexpected what_received in MDS Transaction Program [chars]
Explanation An MDS Transaction Program has received an unexpected what_received. The transaction program will reinitialize. The MDS_MU that was being sent will be returned to the originator if the error was detected at the originating node, or the originator will be notified of the send failure via an error message.
Recommended Action Investigate the cause of the unexpected what_received.
Error Message%SNASW-4-MS_LOG_36 : EXCEPTION - [int] - Following locally originated MSCAPS message failed to be sent [chars]
Explanation The system has received a send failure for a local MS capabilities originated message. MS capabilities will treat the send failure as a loss of connectivity to the partner node. If focal point relationships are affected, MS capabilities will take appropriate recovery action.
Recommended Action Investigate the cause of the failed send.
Error Message%SNASW-4-MS_LOG_37 : EXCEPTION - [int] - MS unable to allocate space for link control block [chars]
Explanation The system was unable to allocate a resource to set up a link control block for a received PU_STATUS message. The active link will be treated as unknown by MS. Any messages received over the link will be returned as undeliverable. Any TRANSFER_MS_DATA or SEND_MDS_MUs received from applications that specify the link in the PU_STATUS will be returned with link_name unknown.
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-NOF_LOG_10 : PROBLEM - [int] - Insufficient storage to process ACTLU [chars]
Explanation Available storage was insufficient for processing the received ACTLU. The LU-SSCP session will not be started. An ACTLU negative response with the specified sense code is 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-NOF_LOG_11 : PROBLEM - [int] - ACTLU received for LU which is not defined locally, and implicit LU definition is not supported [chars]
Explanation An ACTLU was received for an LU that is not defined locally, and implicit LU definition is not supported. This condition typically indicates a mismatch between this node and the host configuration. The LU-SSCP session is not activated. The ACTLU is rejected with the specified sense code.
Recommended Action Remove the LU from the host configuration.
Error Message%SNASW-4-NOF_LOG_15 : EXCEPTION - [int] - An LU-SSCP session activation attempt failed because the SSCP was not suitable [chars]
Explanation An ACTLU was received for an LU from the wrong SSCP. The ACTLU is rejected with the sense code 084B0000. The LU activation attempt has failed.
Recommended Action If it is required that the LU accept the ACTLU so that the activation attempt will succeed, change the LU definition so that either the LU requires the SSCP identifier that is received from the SSCP, or the LU accepts any SSCP identifier.
Error Message%SNASW-6-NOF_LOG_2 : INFO - [int] - Node started [chars]
Explanation The node has been successfully started.
Recommended Action No action is required.
Error Message%SNASW-3-NOF_LOG_3 : PROBLEM - [int] - Insufficient storage to start SNA Switch [chars]
Explanation Available storage was insufficient for starting the SNA switch. The SNA switch was not started.
Recommended Action Make more storage available to the SNA switch.
Error Message%SNASW-6-NOF_LOG_4 : INFO - [int] - Node stopped [chars]
Explanation The node has been successfully stopped.
Recommended Action No action is required.
Error Message%SNASW-3-NOF_LOG_7 : PROBLEM - [int] - Failed to dynamically load TP [chars]
Explanation The system failed to dynamically load an APPC transaction program or CPI-C application. The received Attach will fail with the specified sense code.
Recommended Action Collect the trace information, 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-PC_LOG_0 : EXCEPTION - [int] - Unable to route intra-node session data [chars]
Explanation The system was unable to route intranode session data. This error usually indicates a race condition when an intranode session is deactivating.
Recommended Action No action is required.
Error Message%SNASW-3-PS_LOG_1 : PROBLEM - [int] - Attach rejected because requested conversation type not supported by requested transaction program [chars]
Explanation Attach rejected because the specified conversation type is not supported by the specified transaction program. This condition may be a result of be a mismatch in the capabilities of the originating transaction program and the destination transaction program, or it may simply be a configuration error. The Attach will be rejected.
Recommended Action Check the conversation type or types supported by the specified transaction program, and check that this matches the conversation type supported defined for the transaction program. If they match, or the transaction program is not defined, there is a mismatch between the originating and destination transaction programs.
Error Message%SNASW-4-PC_LOG_4 : EXCEPTION - [int] - Insufficient storage to generate Alert [chars]
Explanation Available storage was insufficient for generating an alert to report invalid received data. An alert will not be generated.
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-PC_LOG_5 : EXCEPTION - [int] - Unable to route inter-node session data [chars]
Explanation The system was unable to route internode session data. This error usually indicates a race condition when an internode session is deactivating.
Recommended Action No action is required.
Error Message%SNASW-4-PC_LOG_9 : EXCEPTION - [int] - Unable to forward an HPR NLP - unknown ANR label [chars]
Explanation The system failed to forward an HPR network layer packet because the ANR label could not be matched to an outgoing link. This is usually a normal race condition that occurs when an HPR-capable link is deactivated. This condition may also be caused by an earlier resource shortage (look for log 192). An RTP connection may attempt to switch paths or may fail altogether.
Recommended Action Enter the show snasw link command to look for an active HPR-capable link that has the specified ANR label. If there is an active HPR-capable link that has the specified ANR label, the problem has been caused by a shortage of storage. 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-PC_LOG_10 : PROBLEM - [int] - Insufficient storage to start link inactivity timer [chars]
Explanation Available storage was insufficient for starting the link-inactivity timer. The limited resource link will not be automatically deactivated.
Recommended Action If the link is idle (not being used by any sessions), deactivate the link by entering the snasw stop link command.
Error Message%SNASW-3-PC_LOG_11 : PROBLEM - [int] - Unable to forward an HPR NLP - insufficient storage [chars]
Explanation Available storage was insufficient for forwarding an HPR network layer packet. The network layer packet will be discarded. If this error occurs frequently, it may cause RTP connections to switch paths 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-PC_LOG_12 : PROBLEM - [int] - Insufficient storage to register ANR label [chars]
Explanation Available storage was insufficient for registering an ANR label. HPR traffic that is using this ANR label will not be routed correctly, and as a result RTP connections may switch paths 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-4-PC_LOG_14 : EXCEPTION - [int] - Received a frame with a badly formed transmission header or a frame that is too small to be a valid SNA frame [chars]
Explanation The system has received a frame that has a badly formed transmission header or a frame that is too small to be a valid SNA frame. The invalid frame will be discarded. An alert is generated.
Recommended Action No action is required.
Error Message%SNASW-4-PC_LOG_15 : EXCEPTION - [int] - Unable to correlate DLC credit for MLTG link [chars]
Explanation The system was unable to correlate DLC credit for an MLTG link. This exception will occur during a window condition in normal link deactivation.
Recommended Action If several instances of this log appear and poor RTP connection performance occurs, investigate this condition further by querying link stations that are members of the MLTGs. Unexpectedly low quantities of data sent over a link may indicate problems with DLC credit. Run a trace of the signals sent to and from the DLCs that are underlying the affected links, contact your Cisco technical support representative, and provide the representative with the details of the problem.
Error Message%SNASW-4-PC_LOG_16 : EXCEPTION - [int] - Link failure because too many outgoing packets are queued for transmission [chars]
Explanation A remote node is not processing information fast enough, and this situation is causing large queues to form on this node. This condition results in a link failure.
Recommended Action Check the error logs on the remote node to which this link is connected.
Error Message%SNASW-4-PC_LOG_17 : EXCEPTION - [int] - Link failure because too many outgoing packets are queued for transmission [chars]
Explanation A remote node is not processing information fast enough, and this situation is causing large queues to form on this node. This condition results in a link failure.
Recommended Action Check the error logs on the remote nodes to which this MLTG is connected.
Error Message%SNASW-3-PS_LOG_3 : PROBLEM - [int] - Conversation ended by protocol error [chars]
Explanation A session that is being used by a conversation has been deactivated because of a protocol error. This error caused the conversation to fail. The conversation will be terminated, either by an APPC primary_rc of NAP_CONV_FAILURE_NO_RETRY or by a CPI-C return_code of CM_RESOURCE_FAILURE_NO_RETRY.
Recommended Action This log provides information about the TPs and conversation that have been affected by a protocol error on a session. Other more specific problem or exception logs give more information on the protocol error. Use the session identifier to correlate this log with other related logs.
Error Message%SNASW-3-PS_LOG_4 : PROBLEM - [int] - Conversation ended by session outage [chars]
Explanation The session that is being used by a conversation has been deactivated because of a session outage. This outage caused the conversation to fail. The conversation will be terminated, either by an APPC primary_rc of NAP_CONV_FAILURE_RETRY, or a CPI-C return_code of CM_RESOURCE_FAILURE_RETRY.
Recommended Action This log gives information about the TPs and conversation that have been affected by a session outage. Other, more specific problem or exception logs give more information on the reason for the session outage. Use the session identifier to correlate this log with other related logs.
Error Message%SNASW-4-PS_LOG_5 : EXCEPTION - [int] - Protocol error detected on conversation [chars]
Explanation The SNA switch has detected a protocol error on an APPC conversation. The sense codes are as follows:
–
–
–
–
–
–
The conversation will be terminated, either by an APPC primary_rc of NAP_CONV_FAILURE_NO_RETRY, or a CPI-C return_code of CM_RESOURCE_FAILURE_NO_RETRY, and the session will be deactivated.
Recommended Action Report the protocol error to the partner LU support. If additional diagnostic information is required, run a link trace. The session identifier can be used to correlate this log to other logs that contain the appropriate link station name.
Error Message%SNASW-4-PS_LOG_7 : EXCEPTION - [int] - Error data received from partner LU. [chars]
Explanation The partner TP has issued a SEND_ERROR or DEALLOCATE verb specifying an error in the data. An error state was generated by the partner TP. The specified TP will experience a problem. Subsequent recovery or termination of the conversation will be determined by the applications.
Recommended Action Check that both the local TP and the partner TP exist, are correctly named, and are working properly.
Error Message%SNASW-4-PS_LOG_8 : EXCEPTION - [int] - Error data sent to partner LU. [chars]
Explanation The local TP has issued a SEND_ERROR or DEALLOCATE verb specifying error data. The specified TP will experience a problem. Subsequent recovery or termination of the conversation will be determined by the applications.
Recommended Action Check that both the local TP and the partner TP exist, are correctly named, and are working properly.
Error Message%SNASW-6-PS_LOG_9 : INFO - [int] - Processed APING from partner LU. [chars]
Explanation An APING from the partner LU has been processed successfully.
Recommended Action No action is required.
Error Message%SNASW-3-PS_LOG_10 : PROBLEM - [int] - Attach rejected because requested conversation duplex type not supported by requested transaction program [chars]
Explanation The Attach was rejected because the specified conversation duplex type is not supported by the specified transaction program. This condition may indicate a mismatch in the capabilities of the originating transaction program and the destination transaction program. This condition may also be a configuration error. Possible sense codes are as follows:
–
–
The Attach will be rejected.
Recommended Action Check that the conversation duplex type or types are supported by the specified transaction program. Check that the conversation duplex type or types match the conversation type that is supported and defined for the transaction program. If the types match, or the transaction program is not defined, there is a mismatch between the originating and destination transaction programs.
Error Message%SNASW-4-PS_LOG_11 : EXCEPTION - [int] - Entry could not be added to signed-on-to list sending PV sign-on Attach. [chars]
Explanation The local LU has failed to add an entry into the signed-on-to list when sending a PV sign-on Attach (FMH-5). This condition occurred because of a resource shortage. The Attach will be sent but will not contain the sign-on request.
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-PS_LOG_12 : EXCEPTION - [int] - Unable to process Sign-Off verb due to resource shortage. [chars]
Explanation The local LU was unable to process a sign-off verb issued by a local TP because of a resource shortage. The sign-off request will fail, and any entries in the signed-on-to and sign-on-from lists will remain valid.
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-PS_LOG_13 : EXCEPTION - [int] - SNA Switch detected a mapped conversation protocol error on an APPC mapped conversation [chars]
Explanation The SNA switch has detected a mapped conversation protocol error on an APPC mapped conversation. The conversation will be terminated, either by an APPC primary_rc of NAP_CONV_FAILURE_NO_RETRY or by a CPI-C return_code of CM_RESOURCE_FAILURE_NO_RETRY. The partner TP will fail the conversation with an APPC primary_rc of NAP_DEALLOCATE_ABEND or a CPI-C return_code of CM_DEALLOCATE_ABEND. The session will not be deactivated.
Recommended Action Report the protocol error to the partner LU support. If additional diagnostic information is required, run a link trace. The session identifier can be used to correlate this log to other logs that contain the appropriate link station name.
Error Message%SNASW-4-PS_LOG_14 : EXCEPTION - [int] - SNA Switch detected a mapped conversation protocol error on an APPC mapped conversation [chars]
Explanation The SNA switch has received an error data GDS variable on an APPC mapped conversation. The conversation will be terminated, either by an APPC primary_rc of NAP_CONV_FAILURE_NO_RETRY or by a CPI-C return_code of CM_RESOURCE_FAILURE_NO_RETRY. The partner TP will fail the conversation with an APPC primary_rc of NAP_DEALLOCATE_ABEND or a CPI-C return_code of CM_DEALLOCATE_ABEND. The session will not be deactivated.
Recommended Action Report the protocol error to the partner LU support. If additional diagnostic information is required, run a link trace. The session identifier can be used to correlate this log to other logs which contain the appropriate link station name.
Error Message%SNASW-4-PS_LOG_15 : EXCEPTION - [int] - An LU received an aping with data size greater than the maximum allowed [chars]
Explanation An LU received an APING that has a data length greater than the maximum allowed length. The conversation will be terminated with a primary_rc of DEALLOC_ABEND.
Recommended Action Do not APING the SNA switch LUs with a data size greater than the defined maximum. 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-6-PU_LOG_0 : INFO - [int] - A PU-SSCP session has been activated [chars]
Explanation A PU-SSCP session has been activated.
Recommended Action No action is required.
Error Message%SNASW-6-PU_LOG_1 : INFO - [int] - A PU-SSCP session has been deactivated [chars]
Explanation A PU-SSCP session has been deactivated.
Recommended Action No action is required.
Error Message%SNASW-4-PU_LOG_2 : EXCEPTION - [int] - Insufficient storage to send RTM statistics to host [chars]
Explanation Available storage was insufficient for sending RTM statistics to the host. The RTM statistics that are displayed by 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-3-RM_LOG_0 : PROBLEM - [int] - Insufficient storage to start TP instance and conversation requested by received Attach [chars]
Explanation Available storage was insufficient for starting the transaction program instance and conversation requested by a received attach (FMH5). If other instances of the same transaction program are active, the SNA switch will queue the attach and wait for one of them to become free. Otherwise, the session will be deactivated with a sense code of 08640000).
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-RM_LOG_3 : PROBLEM - [int] - Insufficient storage to start conversation requested by [MC_]ALLOCATE or CMALLC [chars]
Explanation Available storage was insufficient for starting a new conversation requested by ALLOCATE, MC_ALLOCATE or CMALLC. [MC_]ALLOCATE will fail with a primary_rc of NAP_UNEXPECTED_SYSTEM_ERROR, or CMALLC with fail with a return_code of CM_PRODUCT_SPECIFIC_ERROR.
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-RM_LOG_13 : EXCEPTION - [int] - APPC Transaction Program or CPI-C application has ended abnormally with active conversations [chars]
Explanation An APPC transaction program or CPI-C application has ended abnormally with active conversations. This condition usually indicates an error in the application. The SNA switch will deactivate all sessions currently being used by the application.
Recommended Action Run a trace on the APPC API or the CPI-C API to see the sequence of verbs that is causing the problem.
Error Message%SNASW-3-RM_LOG_14 : PROBLEM - [int] - Deactivating session because of insufficient storage [chars]
Explanation The SNA switch has deactivated the session because of insufficient storage.
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-RM_LOG_15 : PROBLEM - [int] - Insufficient storage to initiate session activation requested by [MC_]ALLOCATE or CMALLC [chars]
Explanation Available storage was insufficient for initiating the session activation requested by ALLOCATE, MC_ALLOCATE or CMALLC. [MC_]ALLOCATE will fail with a primary_rc of NAP_ALLOCATION_ERROR and a econdary_rc of NAP_ALLOCATION_FAILURE_NO_RETRY. CMALLC will fail with a return_code of CM_ALLOCATION_FAILURE_NO_RETRY.
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-RM_LOG_22 : PROBLEM - [int] - LU-LU verification failed. [chars]
Explanation LU-LU verification has failed. The partner LU has sent an incorrect response to a challenge that was sent by a local LU. This condition has been caused by either a security attack or a defect in the software at the partner LU location. The session will be deactivated.
Recommended Action Check the identity of the partner LU. If the condition was caused by a defect in the software at the partner LU location, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNASW-4-RM_LOG_23 : EXCEPTION - [int] - Insufficient storage to deactivate limited resource session [chars]
Explanation Available storage was insufficient for deactivating a limited resource session. The limited resource session will not be deactivated (although it may be deactivated later). This condition could cause limited resource links to be kept active while they are not required.
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-RM_LOG_27 : INFO - [int] - Session limits changed [chars]
Explanation The session limits for a local LU, partner LU, have changed. The mode has also changed. The termination count indicates the number of sessions that the SNA switch will deactivate as a result of the change in session limits.
Recommended Action No action is required.
Error Message%SNASW-3-RM_LOG_37 : PROBLEM - [int] - LU-LU verification protocol error [chars]
Explanation An LU-LU verification protocol error has occurred. This condition may indicate an interoperability problem. 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-3-RM_LOG_42 : PROBLEM - [int] - Failed to activate a new session, since this would exceed LU or mode session limit [chars]
Explanation The SNA switch was unable to activate a new session because the maximum session limit specified for the mode or the local LU would be exceeded. ALLOCATE, MC_ALLOCATE, or CMALLC verbs will either fail or hang waiting for a session to become free.
Recommended Action Wait for a session to become free and retry, or use a different mode.
Error Message%SNASW-3-RM_LOG_43 : PROBLEM - [int] - Insufficient storage to start TP instance requested by TP_STARTED [chars]
Explanation Available storage was insufficient for starting the transaction program instance requested by TP_STARTED. If other instances of the same transaction program are active, the SNA switch will queue the TP_STARTED waiting for one of them to become free.Otherwise, the TP_STARTED verb will fail with primary_rc of NAP_UNEXPECTED_SYSTEM_ERROR.
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-RM_LOG_44 : PROBLEM - [int] - Insufficient storage to initiate automatic session activation [chars]
Explanation Available storage was insufficient for initiating an automatic session activation. Fewer active sessions will be available on the specified mode, and application delays or failures may result.
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-RM_LOG_45 : PROBLEM - [int] - Insufficient storage to initiate session activation requested by ACTIVATE_SESSION [chars]
Explanation Available storage was insufficient for initiating session activation requested by ACTIVATE_SESSION verb. ACTIVATE_SESSION will fail with NAP_ACTIVATION_FAIL_NO_RETRY
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-RM_LOG_46 : PROBLEM - [int] - Bracket protocol error [chars]
Explanation A bracket protocol error has occurred. This condition may indicate a problem in the partner LU. The sense codes are as follows:
–
–
–
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-3-RM_LOG_47 : PROBLEM - [int] - Attach protocol error [chars]
Explanation Attach protocol error. This may indicate a problem in the partner LU. The sense codes are as follows:
–
–
–
–
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-3-RM_LOG_48 : PROBLEM - [int] - Attach rejected because security information invalid [chars]
Explanation An Attach has been rejected because the security information is invalid. This condition indicates an attempt to access a secure TP by an unknown user or by a known user who has specified an incorrect password. The Attach will be rejected.
Recommended Action Use the information in the log to locate the attempted security violation.
Error Message%SNASW-3-RM_LOG_49 : PROBLEM - [int] - Attach rejected because requested sync level not supported by requested transaction program [chars]
Explanation An Attach has been rejected because the specified synchronization level is not supported by the specified transaction program. This condition may indicate a mismatch in the capabilities of the originating transaction program and the destination transaction program. This condition might also indicate a configuration error. The Attach will be rejected.
Recommended Action Check the synchronization level supported by the specified transaction program, and check that it matches the synchronization level defined for the transaction program. If the synchronization levels match, or the transaction program is not defined, there is a mismatch between the originating and destination transaction programs.
Error Message%SNASW-3-RM_LOG_50 : PROBLEM - [int] - Attach rejected because requested TP is temporarily disabled [chars]
Explanation An Attach has been rejected because the specified TP is temporarily disabled. The Attach will be rejected.
Recommended Action This condition is not currently supported by the SNA switch. This log message should not occur.
Error Message%SNASW-3-RM_LOG_51 : PROBLEM - [int] - Attach rejected because requested TP is permanently disabled [chars]
Explanation An Attach has been rejected because the specified TP is permanently disabled. This condition should occur only if an application has explicitly disabled the transaction program. The Attach will be rejected.
Recommended Action Collect a trace. Copy the message and trace information 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-RM_LOG_52 : PROBLEM - [int] - Failed to activate a new session, because mode name was not recognized [chars]
Explanation The SNA switch was unable to activate a new session because the mode name specified was not recognized. ALLOCATE, MC_ALLOCATE, or CMALLC verbs will fail.
Recommended Action Check the mode name.
Error Message%SNASW-3-RM_LOG_53 : PROBLEM - [int] - Attach rejected because security information not specified [chars]
Explanation An Attach has been rejected because security information is not specified. This condition indicates an attempt to access a secure TP without specifying a user ID or password. The Attach will be rejected.
Recommended Action Use the information in the log to locate the security mismatch.
Error Message%SNASW-3-RM_LOG_54 : PROBLEM - [int] - Bracket protocol error [chars]
Explanation A BIS protocol error has occurred. This condition may indicate a problem in the partner LU. The session will be deactivated with the sense code 20100000.
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-RM2_LOG_0 : PROBLEM - [int] - CP-CP session deactivated because of excessive delay [chars]
Explanation An adjacent node has not responded within a reasonable period of time to a request on a CP-CP session. The SNA switch will deactivate CP-CP sessions with this adjacent node. CP-CP sessions are deactivated with the sense code 08640002.
Recommended Action Contact the supplier of the adjacent node.
Error Message%SNASW-6-RTP_LOG_0 : INFO - [int] - RTP Connection has connected [chars]
Explanation The RTP connection has connected.
Recommended Action No action is required.
Error Message%SNASW-6-RTP_LOG_1 : INFO - [int] - RTP Connection has disconnected [chars]
Explanation The RTP connection has disconnected normally.
Recommended Action No action is required.
Error Message%SNASW-4-RTP_LOG_2 : EXCEPTION - [int] - RTP Connection has disconnected [chars]
Explanation The RTP connection has disconnected because of an error. Sessions that were using the connection will fail.
Recommended Action Investigate the cause of the error.
Error Message%SNASW-4-RTP_LOG_3 : EXCEPTION - [int] - Remote end of RTP Connection has disconnected [chars]
Explanation The RTP connection has disconnected due to an error. Sessions using the connection will fail.
Recommended Action Investigate the cause of the error.
Error Message%SNASW-4-RTP_LOG_4 : EXCEPTION - [int] - RTP connection has timed-out [chars]
Explanation The RTP connection has timed out. The node will attempt to switch paths.
Recommended Action Investigate the cause of the error.
Error Message%SNASW-4-RTP_LOG_5 : EXCEPTION - [int] - RTP connection dropped, possibly due to local link failure [chars]
Explanation An RTP connection has been dropped, most likely because of a local link failure (possibly due to operator intervention). The node will attempt to switch paths.
Recommended Action Investigate the cause of the link failure or other outage.
Error Message%SNASW-6-RTP_LOG_6 : INFO - [int] - Successful path-switch [chars]
Explanation The RTP connection has successfully switched paths.
Recommended Action No action is required.
Error Message%SNASW-4-RTP_LOG_7 : EXCEPTION - [int] - Path-switch failure [chars]
Explanation The RTP connection has failed to switch paths. The RTP connection will be disconnected.
Recommended Action Investigate the cause of the error.
Error Message%SNASW-4-RTP_LOG_8 : EXCEPTION - [int] - Segmented NLP received on Route Setup RTP connection [chars]
Explanation A Route Setup RTP connection RTP process received a segmented NLP. All NLPs that are received should contain Route Setup GDS data, which should never be segmented. The NLP will be dropped.
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-RTP_LOG_9 : EXCEPTION - [int] - RTP connection has timed-out [chars]
Explanation A route setup RTP connection has timed out waiting for the status from the adjacent node. The RTP connection will fail.
Recommended Action Investigate the cause of the error at the adjacent node.
Error Message%SNASW-4-RTP2_LOG_0 : EXCEPTION - [int] - RTP Connection is path-switching to a much longer path [chars]
Explanation An RTP connection is switching to a much longer path than it started with. Each packet requires much more room for routing information than was originally planned. Performance across this RTP connection may degrade, since some packets may have to be segmented.
Recommended Action If performance degradation is noticed, reactivate failed links, and then issue the PATH_SWITCH verb.
Error Message%SNASW-4-RTP2_LOG_1 : EXCEPTION - [int] - Invalid ARB support received from remote node [chars]
Explanation A value for ARB support that the local node does not support has been received in an ARB setup segment. The remote node has not completed the ARB negotiation correctly. This is a protocol error. The connection will be deactivated.
Recommended Action Investigate the cause of the error at the adjacent node.
Error Message%SNASW-4-SC_LOG_1 : EXCEPTION - [int] - Protocol error detected in PIU on intermediate session [chars]
Explanation The SNA switch has detected a protocol error in a PIU received on an intermediate session. This typically indicates a problem on an adjacent node. The sense codes are as follows:
–
–
–
–
–
–
–
–
The intermediate session will be deactivated.
Recommended Action If more diagnostics are required, run a trace on the specified link. Report the problem in the adjacent node to your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNASW-4-SC_LOG_2 : EXCEPTION - [int] - Deactivating intermediate session because of insufficient storage [chars]
Explanation The system has deactivated an intermediate session because of insufficient storage.
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-SCM_LOG_0 : PROBLEM - [int] - ISR session activation failed - ISR session limit reached [chars]
Explanation Intermediate session activation has failed because the SNA switch is not configured to support any more intermediate sessions. This condition is usually caused by a normal network race condition because the SNA switch will inform other network nodes that it has reached its limit on intermediate sessions via topology. ISR session activation will fail with the sense code 0805000D.
Recommended Action Collect a trace. Copy the message and trace information 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-SCM_LOG_1 : PROBLEM - [int] - Protocol error in received ISR BIND request [chars]
Explanation A protocol error has occurred in a received ISR BIND request. This condition may indicate an interoperability problem. Sense codes are as follows:
–
–
–
–
The session activation will fail with the specified sense code.
Recommended Action If more diagnostics are required, run a trace on the specified link. Report the problem to your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNASW-3-SCM_LOG_3 : PROBLEM - [int] - Unable to identify or activate the next hop of an ISR session [chars]
Explanation The system is unable to identify or activate the next hop of an ISR session. ISR session activation will fail with the specified sense code.
Recommended Action This log is preceded by other logs giving more specific reasons for the failure. Follow the actions given in those logs.
Error Message%SNASW-3-SCM_LOG_4 : PROBLEM - [int] - Fatal error detected in ISR session [chars]
Explanation ISR has detected a fatal error in an intermediate session. The ISR session will be deactivated with the specified sense code.
Recommended Action This log should be preceded by a log 536 or 537. Follow the actions given in those logs.
Error Message%SNASW-3-SCM_LOG_5 : PROBLEM - [int] - ISR session failure because of link outage or error [chars]
Explanation The ISR session has failed because of a link outage or link error. The ISR session will be deactivated with the specified sense code.
Recommended Action The information in this log can be used to give information to determine which ISR sessions are affected by a link outage or link error. The preceding logs will provide more specific information about the reason for the link outage or link error.
Error Message%SNASW-3-SCM_LOG_6 : PROBLEM - [int] - Unable to assign LFSID to secondary stage of ISR session [chars]
Explanation The system is unable to assign an LFSID to the secondary stage of an ISR session. This condition is probably caused by insufficient storage to extend the appropriate LFSID routing table. This condition could also indicate that the table is full. Each link can route a maximum of 64770 ISR sessions. ISR session activation will fail with the specified sense code.
Recommended Action This information in this log can be used to determine which ISR session is affected by a failure in the LFSID table management. Preceding logs give more detail on the reason for the failure.
Error Message%SNASW-4-SCM_LOG_7 : EXCEPTION - [int] - Unable to correlate BIND response received during ISR session activation [chars]
Explanation The system is unable to correlate a BIND response received during ISR session activation. This is a normal race condition caused by a BIND request that is immediately followed by an UNBIND request for the same session.
Recommended Action No action is required.
Error Message%SNASW-4-SCM_LOG_8 : EXCEPTION - [int] - Unable to correlate UNBIND request received for an ISR session [chars]
Explanation The system has failed to correlate an UNBIND request received for an ISR session. This is a normal race condition that is typically caused by the crossing of UNBIND requests for the same session.
Recommended Action An +RSP(UNBIND) is sent in reply. No action is required.
Error Message%SNASW-6-SCM_LOG_9 : INFO - [int] - ISR Session Activated [chars]
Explanation An ISR session has been activated.
Recommended Action No action is required.
Error Message%SNASW-6-SCM_LOG_10 : INFO - [int] - ISR Session Deactivated [chars]
Explanation An ISR session has been deactivated.
Recommended Action No action is required.
Error Message%SNASW-3-SCM_LOG_11 : PROBLEM - [int] - Received ISR BIND request with duplicate FQPCID [chars]
Explanation The system has received an ISR BIND request with a duplicate FQPCID. ISR session activation will fail with the sense code 083B0002.
Recommended Action If more diagnostics are required, run a trace on the specified link. Report the problem to your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNASW-3-SCM_LOG_12 : PROBLEM - [int] - Protocol error in received ISR BIND request [chars]
Explanation The system has detected a protocol error in a received ISR BIND response. This may indicate an interoperability problem. Sense codes are as follows:
–
–
–
–
–
–
ISR session activation will fail with the specified sense code.
Recommended Action If more diagnostics are required, run a trace on the specified link. Report the problem to your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNASW-3-SCM_LOG_13 : PROBLEM - [int] - ISR is unable to support requested RU size [chars]
Explanation ISR is unable to support RU size requested on nonnegotiable BIND request or response. Sense codes are as follows:
–
–
ISR session activation will fail with the specified sense code.
Recommended Action Collect a trace. Copy the message and trace information 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-SCM_LOG_14 : PROBLEM - [int] - ISR is unable to support requested pacing window size [chars]
Explanation ISR is unable to support a fixed receive pacing window that was requested on nonnegotiable BIND request or response. Sense codes are as follows:
–
–
ISR session activation will fail with the specified sense code.
Recommended Action Collect a trace. Copy the message and trace information 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-SCM_LOG_15 : PROBLEM - [int] - Insufficient storage to activate ISR session [chars]
Explanation Available storage was insufficient for activating the ISR session. The ISR session activation will fail with the sense code 08120014.
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-SCM_LOG_16 : PROBLEM - [int] - Slow session activation detected [chars]
Explanation An intermediate session activation attempt did not complete during the Hung session awareness time interval shown on the show snasw node command.
Recommended Action Examine the session in all the nodes along the session path to determine at which point the session is hung. If you determine that the delay in session setup is normal in your environment, then you should consider using the hung-session-awareness keyword on the snasw cpname configuration command to specify a higher value for the timer.
Error Message%SNASW-3-SM_LOG_0 : PROBLEM - [int] - Insufficient storage to define LU type 6.2 [chars]
Explanation Available storage was insufficient for defining a new LU type 6.2.
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-SM_LOG_1 : PROBLEM - [int] - Fatal error detected on LU6.2 session [chars]
Explanation The system has detected a fatal error on a LU 6.2 session. The session will be deactivated with the specified sense code.
Recommended Action This log gives additional information on the failed session. It is preceded by an exception log (150, 151, 153, 154, 155, 156, or 157) giving more specific information about the fatal error.
Error Message%SNASW-3-SM_LOG_2 : PROBLEM - [int] - BIND or +RSP(BIND) specifies duplex support which is different from that for existing sessions [chars]
Explanation An incoming BIND or +RSP(BIND) has specified a duplex support for the remote LU that is inconsistent with the duplex support for existing sessions between the partner LUs. The BIND or +RSP(BIND) is rejected.
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-SM_LOG_5 : PROBLEM - [int] - Insufficient storage to activate LU6.2 session [chars]
Explanation Available storage was insufficient for activating an LU 6.2 session. 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-SM_LOG_6 : EXCEPTION - [int] - Abnormal UNBIND request received [chars]
Explanation The system has received an abnormal UNBIND request. This condition may indicate a configuration error or a protocol error. The session will fail with the specified sense code.
Recommended Action If the sense code indicates a configuration error, check for inconsistencies between the configuration at the local LU and the configuration at the partner LU. If the configuration is consistent and the problem persists, contact your Cisco technical support representative, and provide the representative with the details of the problem.
Error Message%SNASW-3-SM_LOG_10 : PROBLEM - [int] - Format error in received LU6.2 BIND request [chars]
Explanation The system has detected a format error for a received LU 6.2 BIND request. Sense codes are as follows:
–
–
–
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-SM_LOG_11 : PROBLEM - [int] - Format error in received LU6.2 BIND response [chars]
Explanation The system has detected a format error for a received LU 6.2 BIND response. The session activation will fail with the sense code 0835xxxx (parameter error at offset xxxx in BIND RU).
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-SM_LOG_12 : PROBLEM - [int] - LU-mode session limit exceeded [chars]
Explanation An LU-mode session limit has been exceeded. This problem should not occur, because session limits are negotiated with a CNOS exchange prior to sessions being activated. However, this log can also be caused by a normal race condition when the session limits are reset, or when this node has been restarted after having previously had sessions with this partner LU. The session activation will fail with the specified sense code.
Recommended Action If this problem persists, check the session limits and active session counts on the specified local LU and partner LU.
Error Message%SNASW-4-SM_LOG_13 : EXCEPTION - [int] - BIND race with single-session partner LU - partner LU has lost race [chars]
Explanation A BIND race with a single-session partner LU has occurred. This is a normal network race condition. The race is resolved in favor of the LU with the higher name. In this case, the partner LU lost the race. The session activation will fail with the specified sense code.
Recommended Action No action is required.
Error Message%SNASW-3-SM_LOG_14 : PROBLEM - [int] - Detected consistency errors in received BIND request [chars]
Explanation The system has detected consistency errors in a received BIND request. This condition may indicate an interoperability problem. Sense codes are as follows:
–
–
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-SM_LOG_15 : PROBLEM - [int] - Detected consistency errors in received BIND response [chars]
Explanation The system has detected consistency errors in a received BIND response. This may indicate an interoperability problem. Sense codes are as follows:
–
–
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-3-SM_LOG_16 : PROBLEM - [int] - Format error in received UNBIND request [chars]
Explanation The system has detected a format error in a received UNBIND request. This condition may indicate an interoperability problem. Sense codes are as follows:
–
–
–
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-SM_LOG_18 : EXCEPTION - [int] - Unable to correlate received BIND response [chars]
Explanation The system is unable to correlate a received BIND response. This condition is probably a normal race condition. If a BIND request is followed immediately by an UNBIND request, and then by another BIND request that uses the same LFSID, the response to the first BIND request will not be correlated. The BIND response will be discarded.
Recommended Action No action is required.
Error Message%SNASW-4-SM_LOG_20 : EXCEPTION - [int] - Unable to correlate received INIT-SELF response or NOTIFY request [chars]
Explanation The system is unable to correlate a received INIT-SELF response or NOTIFY request. This is a normal race condition that is caused by deactivation of a session being deactivated before the INIT-SELF response has arrived. The request or response is discarded.
Recommended Action No action is required.
Error Message%SNASW-4-SM_LOG_21 : EXCEPTION - [int] - Unable to correlate received UNBIND request [chars]
Explanation The system is unable to correlate a received UNBIND request. This is a normal race condition that is caused by the crossing of UNBIND requests. The system will send a positive response to the UNBIND request.
Recommended Action No action is required.
Error Message%SNASW-4-SM_LOG_30 : EXCEPTION - [int] - Received ACTLU when LU already active [chars]
Explanation An ACTLU has been received when the LU was already active. The ACTLU will be rejected with the specified sense code.
Recommended Action Run a trace on the link station corresponding to the specified PU name and contact your Cisco technical support representative with details of the problem.
Error Message%SNASW-3-SM_LOG_31 : PROBLEM - [int] - Insufficient storage to activate LU-SSCP session [chars]
Explanation Available storage was insufficient for activating an LU-SSCP session. The ACTLU 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-4-SM_LOG_32 : EXCEPTION - [int] - Unable to activate a new session since it would exceed the LU-mode session limit [chars]
Explanation The system was unable to activate a new session because the new session would exceed the LU-mode session limits. This is a normal race condition and should occur infrequently. The session activation will fail with the specified sense code which may cause ALLOCATE, MC_ALLOCATE or CMALLC requests to fail.
Recommended Action No action is required.
Error Message%SNASW-3-SM_LOG_33 : PROBLEM - [int] - Insufficient storage to reassemble received BIND response [chars]
Explanation Available storage was insufficient for reassembling a received BIND response. 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-3-SM_LOG_34 : PROBLEM - [int] - Badly formed partner LU name in received BIND request [chars]
Explanation A partner LU name on a received BIND request is badly formed. 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-SM_LOG_35 : PROBLEM - [int] - Unrecognized mode name in received BIND request [chars]
Explanation The mode name on a received BIND request is unrecognized. The session activation will fail with the specified sense code.
Recommended Action Modify the partner LU configuration so it does not attempt to use the unrecognized mode.
Error Message%SNASW-3-SM_LOG_36 : PROBLEM - [int] - Unable to activate session to single session partner LU, because there is an active session on another mode [chars]
Explanation The system was unable to activate the session to a single session partner LU because there is already an active session on another mode. This condition usually indicates a contention between two or more APPC transaction programs or CPI-C applications for the same dependent LU 6.2. The session activation will fail with the specified sense code, which may cause ALLOCATE, MC_ALLOCATE or CMALLC requests to fail.
Recommended Action Collect a trace. Copy the message and trace information 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-6-SM_LOG_37 : INFO - [int] - LU6.2 session activated [chars]
Explanation An LU 6.2 session has been activated.
Recommended Action No action is required.
Error Message%SNASW-6-SM_LOG_38 : INFO - [int] - LU6.2 session deactivated [chars]
Explanation An LU 6.2 session has been deactivated.
Recommended Action No action is required.
Error Message%SNASW-4-SM_LOG_39 : EXCEPTION - [int] - An LU-SSCP session activation attempt failed because the SSCP was not suitable [chars]
Explanation An ACTLU was received for an LU from the wrong SSCP. The ACTLU is rejected with the sense code 084B0000. The LU activation attempt has failed.
Recommended Action If it is required that the LU accept the ACTLU so that the activation attempt will succeed, change the LU definition so that either the LU requires the SSCP identifier that is received from the SSCP, or the LU accepts any SSCP identifier.
Error Message%SNASW-4-SM_LOG_40 : EXCEPTION - [int] - LU-mode session limit exceeded - BIND race [chars]
Explanation The LU-mode session limit has been exceeded because of a BIND race. This is normal race condition caused by an attempt of both the local LU and the partner LU to activate the last session on the mode simultaneously. The race will be resolved in favor of the node with the higher name. In this case the partner LU has lost the race. The session activation will fail with the specified sense code.
Recommended Action No action is required.
Error Message%SNASW-3-SM_LOG_41 : PROBLEM - [int] - FQPCID collision on received BIND request [chars]
Explanation An FQPCID collision has occurred. The FQPCID specified on a received BIND request matches the FQCPID being used for an existing active session. This condition can be caused by a collision in the hashing algorithm used to generate an FQPCID. Alternatively, this condition may indicate a problem in the node generating the FQPCID. The session activation will fail with the specified sense code.
Recommended Action If problem is persistent or occurs often, copy the message and trace information 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-SM_LOG_42 : PROBLEM - [int] - Session identifier collision on received BIND request [chars]
Explanation A session identifier collision has occurred. The session identifier specified on a received BIND request matches the session identifier for an existing active session. The session activation will fail with the specified sense code.
Recommended Action If problem is persistent or occurs often, copy the message and trace information 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-6-SM_LOG_43 : INFO - [int] - An LU-SSCP session has been activated for LU type 6.2 [chars]
Explanation An LU-SSCP session has been activated.
Recommended Action No action is required.
Error Message%SNASW-6-SM_LOG_44 : INFO - [int] - An LU-SSCP session has been deactivated for LU type 6.2 [chars]
Explanation An LU-SSCP session has been deactivated.
Recommended Action No action is required.
Error Message%SNASW-3-SM_LOG_45 : PROBLEM - [int] - LU-LU verification protocol mismatch. [chars]
Explanation The system has detected an LU-LU verification protocol mismatch. The partner LU has requested that the basic protocol be used when the local LU runs only the enhanced protocol with the partner LU. The local LU may be configured to run only the enhanced protocol with the partner LU or it may be configured to run either protocol with the partner LU. The local LU has determined that the partner LU can run the enhanced protocol. This problem is a result of either a configuration mismatch, a migration problem, or a security attack. The session activation will fail.
Recommended Action Check the identity of the partner LU. If the problem is a configuration mismatch, reconfigure the verification protocol that the partner LU uses at the partner LU location. If the problem is a migration problem, upgrade the software at the partner LU location. If the problem is a security attack, investigate the security attack.
Error Message%SNASW-3-SM_LOG_46 : PROBLEM - [int] - LU-LU verification failed. [chars]
Explanation An LU-LU verification has failed. The partner LU has sent an incorrect response to a challenge sent by a local LU. This condition is either a configuration mismatch or a security attack. The session activation will fail.
Recommended Action Check the identity of the partner LU. If the condition is a result of a configuration mismatch, reconfigure the password either at the local LU or at the partner LU (or at both LUs) so that both LUs have the same password.
Error Message%SNASW-3-SM_LOG_47 : PROBLEM - [int] - LU-LU verification protocol failed. [chars]
Explanation Duplicate random data has been received. A list is kept of all random data sent as challenges by the local LU. The receipt of duplicate random data from a partner LU should be a rare event and is evidence of a security attack. The session activation will fail.
Recommended Action Check the identity of the partner LU. Check that the random number generators available to the local and partner LUs are of good quality and therefore unlikely to generate matching data. Investigate recurrences of this problem as security attacks.
Error Message%SNASW-3-SM_LOG_48 : PROBLEM - [int] - BIND(-RSP) request received in response to a BIND request [chars]
Explanation A BIND(-RSP) has been received in response to a BIND request. This condition may indicate a configuration error or a protocol error. Sense codes that typically indicate a configuration error or a normal race condition include the following:
–
–
–
–
–
–
Less common sense codes include the following:
–
–
–
–
–
–
The session activation will fail with the specified sense code.
Recommended Action If the sense code indicates a configuration error, check for inconsistencies between the configuration at the local LU and the configuration at the partner LU. If the configuration is consistent and the problem persists, contact your Cisco technical support representative with details of the problem.
Error Message%SNASW-4-SM_LOG_49 : EXCEPTION - [int] - UNBIND request received in response to a BIND request [chars]
Explanation An UNBIND request has been received in response to a BIND request. This condition may indicate a configuration error or a protocol error. Sense codes that typically indicate a configuration error or a normal race condition include the following:
–
–
–
–
–
–
Less common sense codes include the following:
–
–
–
–
–
–
–
The session activation will fail with the specified sense code.
Recommended Action If the sense code indicates a configuration error, check for inconsistencies between the configuration of the local LU the partner LU. If the configuration is consistent and the problem persists, contact your Cisco technical support representative with details of the problem.
Error Message%SNASW-4-SM2_LOG_0 : EXCEPTION - [int] - Standard compression levels used [chars]
Explanation A BIND response was received that accepted session compression, but the BIND response did not specify the compression levels required. This condition occurred either because the response is from a back-level node or because the BIND request was shortened. If the compression level negotiation fails and the standard compression levels are used, compression will be used in both directions even though it may have been configured for one direction only.
Recommended Action No action is required.
Error Message%SNASW-4-SM2_LOG_1 : EXCEPTION - [int] - Failed to adjust a buffer pool [chars]
Explanation The desired number of buffers could not be reserved for a buffer pool. The receive pacing window size for the session will not increase as fast as configured.
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-SS_LOG_4 : EXCEPTION - [int] - Network Node server not required [chars]
Explanation The network node server is not required. This condition is logged when an APPN network node that does not support function set 1015 (back-level) attempts to activate CP-CP sessions with the SNA switch when the SNA Switch already has a network node server. The CP-CP session will be deactivated with the specified sense code. The SNA switch cannot subsequently use this network node as its server unless all links to it are deactivated and at least one link is restarted.
Recommended Action No action is required.
Error Message%SNASW-3-SS_LOG_5 : PROBLEM - [int] - CP capabilities exchange failed because of contention loser CP-CP session failure [chars]
Explanation A CP capabilities exchange has failed because of a contention loser CP-CP session failure. The contention winner CP-CP session will be deactivated. The SNA switch will attempt to reactivate CP-CP sessions with this adjacent CP.
Recommended Action The information in this log indicates that a CP-CP session has failed. Other logs give more details on the reason for the session failure such as insufficient resources or link failure.
Error Message%SNASW-3-SS_LOG_7 : PROBLEM - [int] - Insufficient storage to generate Alert CPSS003 [chars]
Explanation Available storage was insufficient for generating an Alert CPSS003 (protocol error in received BIND or LOCATE). 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-SS_LOG_8 : PROBLEM - [int] - CP capabilities exchange failed because of protocol error [chars]
Explanation The CP capabilities exchange has failed because of a protocol error. This condition may indicate an interoperability problem. Sense codes are as follows:
–
–
–
–
–
CP-CP sessions with the specified adjacent node will be deactivated. The SNA switch will not attempt to reactivate CP-CP sessions with this adjacent CP.
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-SS_LOG_9 : PROBLEM - [int] - Protocol error in CP capabilities exchange [chars]
Explanation The CP capabilities exchange has failed because of a badly formatted CP CAPS GDS variable. Sense codes are as follows:
–
–
CP-CP sessions with the specified adjacent node will be deactivated. The SNA switch will not attempt to reactivate CP-CP sessions with this adjacent CP.
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-6-SS_LOG_11 : INFO - [int] - Adjacent CP contacted [chars]
Explanation An adjacent CP has been contacted.
Recommended Action No action is required.
Error Message%SNASW-6-SS_LOG_12 : INFO - [int] - CP-CP sessions established [chars]
Explanation CP-CP sessions have been successfully established with the adjacent node.
Recommended Action No action is required.
Error Message%SNASW-4-SS_LOG_13 : EXCEPTION - [int] - Retrying CP-CP session activation after failure [chars]
Explanation The system is retrying CP-CP session establishment after an error has occurred.
Recommended Action No action is required.
Error Message%SNASW-3-SS_LOG_16 : PROBLEM - [int] - CP capabilities exchange failed because of contention winner CP-CP session failure [chars]
Explanation A CP capabilities exchange failed because of a contention winner CP-CP session failure. The contention loser CP-CP session will be deactivated. The SNA switch will attempt to reactivate CP-CP sessions with the adjacent CP.
Recommended Action The information in this log indicates that a CP-CP session has failed. Other logs give more details on the reason for the session failure such as insufficient resources or link failure.
Error Message%SNASW-4-SS_LOG_17 : EXCEPTION - [int] - CP-CP sessions established between network nodes in different networks [chars]
Explanation CP-CP sessions have been established between two network nodes in different networks. The CP-CP sessions will be deactivated with the specified sense code.
Recommended Action No action is required.
Error Message%SNASW-6-SS_LOG_18 : INFO - [int] - CP-CP sessions deactivated [chars]
Explanation CP-CP sessions to the adjacent node have been deactivated.
Recommended Action No action is required.
Error Message%SNASW-4-SS_LOG_19 : EXCEPTION - [int] - Insufficient resources to register LU on adjacent LEN [chars]
Explanation The branch network node has insufficient resources to register an LU on an adjacent LEN node. The LU resource may not be put into the directory and may not be accessible to other resources.
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-SS_LOG_20 : EXCEPTION - [int] - Automatic retry of CP-CP sessions on a timer has failed [chars]
Explanation The node has failed to start a timer to retry CP-CP sessions to a Network Node Server. The node will not automatically attempt to activate CP-CP sessions. Therefore, the system can either be left without CP-CP sessions at all or with CP-CP sessions using a node that is not the best available. CP-CP sessions will, however, be retried using the normal method when a local application needs them or when a new link activates.
Recommended Action If CP-CP sessions are not required or if the administrator is satisfied with the existing Network Node Server, no action is required. If the administrator wants to start CP-CP sessions, they can be started manually.
Error Message%SNASW-4-TC_LOG_0 : EXCEPTION - [int] - Session pacing error [chars]
Explanation A session pacing error has occurred. This condition may indicate an interoperability problem. Sense codes are as follows:
–
–
–
–
–
The session will be deactivated with the specified sense code.
Recommended Action Use the information in the session deactivated problem log (271) to identify the local LU and partner LU. If more diagnostic information is required, 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-TC_LOG_1 : EXCEPTION - [int] - Session segmentation error [chars]
Explanation A session segmentation error has occurred. This condition may indicate an interoperability problem. Sense codes are as follows:
–
–
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. If more diagnostic information is required, 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-TC_LOG_2 : EXCEPTION - [int] - RU length error [chars]
Explanation An RU length error has occurred. This condition may indicate an interoperability problem. The session will be deactivated with the sense code 10020000 (RU length error).
Recommended Action For an LU 6.2 session, use the information on the session deactivated problem log (271) to identify the local LU and partner LU. If more diagnostic information is required, 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-TNBM_LOG_0 : EXCEPTION - [int] - The Buffer Manager Monitor could not allocate necessary resource [chars]
Explanation The Buffer Manager Monitor could not allocate the necessary resources The Buffer Manager will fail to operate. The Buffer Manager will fail to detect congestion conditions or relief from congestion, which could cause the node to lock up.
Recommended Action Shut down and restart the node.
Error Message%SNASW-4-TNBM_LOG_1 : EXCEPTION - [int] - Insufficient storage to create new buffer pool [chars]
Explanation Available storage was insufficient for creating a new buffer pool. Activation of some resources such as session or LS will fail. See other logs.
Recommended Action Investigate the memory shortage and the system load.
Error Message%SNASW-4-TNBM_LOG_2 : EXCEPTION - [int] - Insufficient buffers to create new buffer pool [chars]
Explanation Insufficient buffers were available to create a new buffer pool. Activation of some resources such as session or LS will fail. See other logs.
Recommended Action Investigate the buffer shortage and system load.
Error Message%SNASW-4-TNBM_LOG_3 : EXCEPTION - [int] - Critical buffer congestion [chars]
Explanation The Buffer Manager Monitor has detected critical buffer congestion. The SNA switch will throttle back session traffic by withholding pacing responses or resetting pacing windows on adaptive-paced sessions until the congestion has decreased. This condition can occur if the node receives a large, sudden burst of data traffic on several sessions.
Recommended Action The condition should clear itself automatically, but if the condition occurs frequently, it may indicate that the node is routing more sessions than it can handle efficiently with the available buffer storage. Reduce the number of sessions through the router.
Error Message%SNASW-4-TNBM_LOG_4 : EXCEPTION - [int] - Buffer congestion relieved [chars]
Explanation The buffer congestion has been relieved. The SNA switch will stop throttling back session traffic. If the congestion eases further, the SNA switch will start to increase pacing windows on adaptively paced sessions.
Recommended Action No action is required.
Error Message%SNASW-4-TNBM_LOG_5 : EXCEPTION - [int] - Critical buffer congestion detected while attempting to relieve congestion [chars]
Explanation The Buffer Manager detected critical buffer congestion while attempting to relieve a previous congestion condition. The SNA switch will throttle back session traffic by withholding pacing responses or resetting pacing windows on adaptive-paced sessions until the congestion has reduced. This condition can occur if the node receives a large, sudden burst of data traffic on several sessions.
Recommended Action The condition should clear itself automatically, but if it occurs frequently, it may indicate that the node is routing more sessions than it can handle efficiently with the available buffer storage. Reduce the number of sessions through the router.
Error Message%SNASW-4-TNBM_LOG_6 : EXCEPTION - [int] - Insufficient storage to request posting [chars]
Explanation Available storage was insufficient for requesting posting. The component using the Buffer Manager may fail to operate or may lock up. See other logs to determine the effects of this condition.
Recommended Action Investigate the memory shortage and the system load.
Error Message%SNASW-4-TNTL_LOG_0 : EXCEPTION - [int] - Implicit alias space wrapped [chars]
Explanation The space for implicit aliases has wrapped. There is a very slight possibility of duplicate aliases.
Recommended Action Shut down and restart to avoid any conflict.
Error Message%SNASW-3-TNTL_LOG_1 : PROBLEM - [int] - Invalid internal state detected [chars]
Explanation A software error has caused a bad internal state to be detected. This condition could result in a loss of system function. Refer to other problem logs for the actual effect.
Recommended Action Shut down and restart.
Error Message%SNASW-3-TRACE : Diagnostic trace record too large for configured buffer. Buffer ID [hex]
Explanation A trace record could not be written to one of the cyclic trace buffers, because it was bigger than the available buffer space. The buffer will be cleared.
Recommended Action Increase the size of the relevant cyclic trace buffer or, if diagnostics are not currently necessary, disable the tracing.
Error Message%SNASW-3-TRACE_2 : Resizing of [chars] buffer failed due to insufficient memory; using buffer-size of [dec] KB.
Explanation A cyclic trace buffer could not be resized because of insufficient memory. The previously allocated buffer, if any, will continue to be used.
Recommended Action Reconfigure a smaller buffer size for the specified buffer type.
Error Message%SNASW-4-TS_LOG_0 : EXCEPTION - [int] - Unable to generate session route : unknown COS name [chars]
Explanation A CoS name that was specified for a session activation could not be associated with a valid CoS. The session activation will fail with the specified sense code.
Recommended Action Ensure that the origin node or its network node server does not use the unrecognized CoS in its mode-to-CoS mapping tables.
Error Message%SNASW-4-TS_LOG_1 : EXCEPTION - [int] - Unable to generate session route - no suitable TGs from origin node [chars]
Explanation No suitable TG could be found from the origin end node to the backbone network for the CoS that is specified for a session activation. This condition may be caused by a temporary link failure between the origin node and a network node. A session activation will fail with the specified sense code.
Recommended Action Check for a link failure at the origin node that explains the route failure. If no link failure is found, either change the mode-to-CoS mapping on the origin node or its network node server to use a different class of service, or reconfigure the network to ensure that a usable route exists from the origin node to the backbone network (for example, by defining or activating another link from the origin node to a network node).
Error Message%SNASW-4-TS_LOG_2 : EXCEPTION - [int] - Unable to generate session route - no suitable TGs to destination node [chars]
Explanation No suitable TG could be found from the backbone network to the destination end node for the CoS specified for a session activation. This condition may be caused by a temporary link failure between the destination node and a network node. The session activation will fail with the specified sense code.
Recommended Action Check for a link failure at the destination node that explains the route failure. If no link failure is found, either change the mode-to-CoS mapping on the origin node or its network node server to use a different class of service, or reconfigure the network to ensure that a usable route exists from the destination node to the backbone network (for example, by defining and/or activating another link from the destination node to a network node).
Error Message%SNASW-4-TS_LOG_6 : EXCEPTION - [int] - Unable to generate session route to adjacent node [chars]
Explanation No suitable TG could be found for a session activation to an adjacent node for the given CoS. This condition may be caused by a link failure. The session activation will fail with the specified sense code.
Recommended Action Check for a link failure that explains the failure. If no link failure is found, reconfigure the network to ensure that a usable link exists between this node and the specified adjacent node.
Error Message%SNASW-4-TS_LOG_7 : EXCEPTION - [int] - Unable to generate session route - RSCV truncated [chars]
Explanation The route selection control vector generated for the specified route was too long. The route selection control vector must be less than 256 bytes. The session activation will fail with the specified sense code.
Recommended Action Reconfigure the network to ensure that a short enough route exists between the origin and destination nodes.
Error Message%SNASW-3-TS_LOG_13 : PROBLEM - [int] - Failed to send alert due to insufficient memory [chars]
Explanation Insufficient memory was available to send an alert. The host will not see an alert. The following alert numbers identify the alert:
–
–
–
–
–
The alerts are detailed in the Management Services Reference (C30-3346). No other symptoms will be seen.
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.