Table of Contents

SNASW Messages

The following are Systems Network Architecture (SNA) Switching Services error messages.

Error Message   

Explanation   The Systems Network Architecture (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   

Explanation   The Systems Network Architecture (SNA) switch could not allocate necessary storage. Some operations will fail. See other logs/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   

Explanation   A call from the Systems Network Architecture (SNA) switch to perform a cryptographic operation has failed. The session activation will fail, or an active session will end abnormally with the given sense code. More information might appear in subsequent logs.

Recommended Action   Check the following logs for evidence of failed session activation. If there is evidence of a failed session activation, check MODE, LS, or INTERNAL Physical Unit (PU) definitions for cryptographic support. Check that any passwords necessary have been defined. If this problem occurs intermittently or to active sessions with the same Primary Logical Unit (PLU) or Secondary Logical Unit (SLU) and mode, it will be necessary to make more storage available for the SNA switch.

Error Message   

Explanation   The system has received a Berkeley Internet Name Domain (BIND) request directed at this node (either without an Route Selection Control Vector (RSCV) or at the last hop on the RSCV) with an unrecognized secondary logical unit (LU) name. This condition usually indicates a configuration error at the primary LU. Session activation will fail with the specified sense code.

Recommended Action   Correct the primary LU configuration.

Error Message   

Explanation   There is insufficient storage to generate an alert to report a Berkeley Internet Name Domain (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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   There is insufficient storage to process a received Berkeley Internet Name Domain (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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   ACTPUs, ACTLUs, DACTPUs or DACTLUs were received over a link on which dependent logical units (LU) are not supported. This condition might indicate an interoperability problem. The request will be rejected with the specified sense code.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A branch network node has received a Berkeley Internet Name Domain (BIND) request with a badly formed Route Selection Control Vector (RSCV). This condition might indicate an interoperability problem. Session activation will fail.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The Systems Network Architecture (SNA) switch received and rejected a malformed Berkeley Internet Name Domain (BIND) request. This condition might indicate an interoperability problem. Session activation will fail.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The system has received a Berkeley Internet Name Domain (BIND) request with a badly formed secondary Logical Unit (LU) name. This condition might indicate an interoperability problem. The session activation will fail with the specified sense code.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The system has received a Berkeley Internet Name Domain (BIND) request where the network identifier of the secondary Logical Unit (LU) does not match the local network identifier. The session activation will fail with the specified sense code.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   There is insufficient storage 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The system is unable to correlate the received Berkeley Internet Name Domain (BIND) response. This condition is a normal race condition and is caused by a BIND response being followed immediately by an UNBIND response for the same session. The BIND response is discarded.

Recommended Action   No action is required.

Error Message   

Explanation   The system has received a Berkeley Internet Name Domain (BIND) using a local form session identifier (LFSID) that the system is 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 Advanced Peer-to-Peer Networking (APPN) contain "LFSID aging" processes to minimize the changes of this race condition, but some older implementations might not support this processing. The BIND will be rejected with specified sense code.

Recommended Action   If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A session control request with an invalid local form session identifier (LFSID) has been received. The LFSID is not in a range appropriate for the request. This error might indicate an interoperability problem. The request will be rejected with the specified sense code.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   There is insufficient storage to create a local form session identifier (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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The system is unable to extend the local form session identifier (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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   An independent Logical Unit (LU) to LU session was deactivated because the local LU was deleted.

Recommended Action   No action is required.

Error Message   

Explanation   The system detected a fatal Berkeley Internet Name Domain (BIND) or UNBIND protocol error. This condition might indicate an interoperability problem. The following are sense codes:

• 20110000 - BIND pacing window overrun, or PI not set when expected.

• 20110001 - Unexpected solicited BIND IPM.

• 20110002 - PI set when not expected.

• 20110003 - Pacing response not IPM.

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

• 10010003 - BIND IPM format error.

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

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

• 800F0000 - Local-form session identifier (LFSID) incorrect for SC request.

• 800F0001 - ODAI incorrect Link will be deactivated.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The system has received a Berkeley Internet Name Domain (BIND) IPM on a link where adaptive BIND pacing is not supported. This condition might indicate an interoperability problem. The BIND IPM will be discarded.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A dependent Logical Unit (LU) to LU session was deactivated because the LU has been deleted.

Recommended Action   No action is required.

Error Message   

Explanation   An invalid message name has been supplied on a snasw msg-trap command.

Recommended Action   Enter the command again with a valid message name.

Error Message   

Explanation   A Logical Unit (LU) type 0, 1, 2, or 3 format error has occurred. This condition might indicate an interoperability problem. The frame that contains the error is discarded.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A Logical Unit (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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   A Logical Unit (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 error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A Logical Unit (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 error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A Logical Unit (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   

Explanation   A Logical Unit (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   

Explanation   A Logical Unit (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   

Explanation   There is insufficient storage to report Real Time Monitor (RTM) statistics to a host. The RTM statistics that are 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   There is insufficient storage to report Real Time Monitor (RTM) status to an application. The RTM statistics that are reported and displayed by the application might 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   A call reference value (CRV) exchange has failed. This condition indicates that the cryptography keys configured at this Logical Unit (LU) and the partner LU are not consistent. The session will be deactivated with the specified sense code (08350001).

Recommended Action   Identify the local LU and partner LU and correct the mismatch in the cryptography keys. Use the information on the session to deactivate the problem log (log 271).

Error Message   

Explanation   A protocol error has occurred during a call reference value (CRV) exchange. This condition indicates a possible interoperability problem.

The following are sense codes:

• 20090000 - CRV request received from secondary LU, or CRV response received from primary LU, or CRV not received when expected.

• 10020000 - CRV RU too short.

• 400F0000 - CRV with FI not set.

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

• 40140000 - CRV not RQD1.

• 40110000 - CRV not expedited.

• 40150000 - CRV with QRI not set.

• 40080000 - CRV with PI set.

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

• 400D0000 - CRV request with CDI set.

• 40100000 - CRV request with CSI set to CODE1.

• 40160000 - CRV request with EDI set.

• 40170000 - CRV request with PDI set.

• 40130000 - CRV response RTI and SDI inconsistent session will be deactivated with specified sense code.

Recommended Action   Use the information in the session deactivated problem log (271) to identify the local Logical Unit (LU) and partner LU. Run a trace on the specified link station. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   There is insufficient storage space to initialize 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   An internal software error has occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   An internal software error has occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   An internal software error has occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   An active link station has failed. The link and any sessions using the link will be deactivated

Recommended Action   Restart the link. If the problem persists, inspect the log for problems or exceptions logged by the data-link control (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   

Explanation   The number of exchange identifications (XIDs) that were received during link activation exceeded the limit that is defined for the port. This condition could indicate an XID protocol error or an excessively unreliable physical media. The sense data gives more information about the error.

• 083E0001 - The limit was exceeded while exchanging prenegotiation or negotiation exchange identifications (XIDs).

• 0809003A - The limit was exceeded while exchanging NULL XIDs. Link activation will fail.

Recommended Action   Retry the activation. If the Systems Network Architecture (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   

Explanation   The number of negotiation exchange identifications (XIDs) received during a non-activation exchange has exceeded the limit that was defined for the port. This condition might indicate an XID protocol error or an excessively unreliable physical media. Non-activation 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. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   There is insufficient storage to activate 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   An exchange identification (XID) 3 from an adjacent back-level low-entry networking (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 control point (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   

Explanation   The link to host is incorrectly configured as a link to a Type 2.1 node. The link activation will fail.

Recommended Action   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   

Explanation   There was an exchange identification (XID) protocol error during the activation exchange. This condition might indicate an interoperability problem between this node and the adjacent node, or this condition might be caused by the adjacent node resetting and restarting the exchange without sending a DISC or DM frame.

The following are sense codes:

• 0806002C - The adjacent node has changed its network name during an XID exchange.

• 0809003A - Received a null XID when an XID format 3 was expected.

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

• 0809003D - Nonactivation XID received when a null XID or activation XID was expected.

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

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

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

• 08090047 - Received XID after receiving mode-setting command (for example, SNRM or SABME).

• 08090048 - Received unsolicited XID from normal response mode (NRM) secondary link station.

• 08090049 - The adjacent node sent an XID error control vector (x'22').

• 08090055 - Invalid VRN in TG descriptor CV of XID3.

• 086F0000 - XID3 control vector length error.

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

• 088C0EF1 - The adjacent node is type 4 or 5 but did not include a Physical Unit (PU) name control vector.

• 088C0EF4 - The adjacent node was inconsistent in including a network name control vector.

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

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

• 08910005 - The network name control vector does not contain a valid CP name 0895xxyy - XID3 control vector error (xx indicates key of first control vector in error, yy indicates offset of error within control vector).

• 08960000 - Control vector is too long.

• 08960001 - Network name control vector is too long.

• 10150001 - Received XID3 is too short (less than 29 bytes).

• 10150002 - Length of received XID3 does not match length indicated in XID3.

• 10160000 - The adjacent node indicated an invalid Berkeley Internet Name Domain (BIND) pacing setting.

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

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

• 10160004 - Unexpected XID format.

• 10160005 - The adjacent end node supports receipt of Berkeley Internet Name Domain (BIND) segments, but does not support BIND segment generation.

• 10160006 - The adjacent end node does not support receipt of Berkeley Internet Name Domain (BIND) segments and has a maximum MTU size less than 265 bytes.

• 10160007 - The adjacent network node does not support receipt of Berkeley Internet Name Domain (BIND) segments and has a maximum MTU size less than 521 bytes.

• 10160008 - The adjacent node was inconsistent in its setting of networking capabilities.

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

• 1016000B - The adjacent node has selected zero as the TG number, which is invalid.

• 1016000C - The adjacent network node does not support Berkeley Internet Name Domain (BIND) segment generation and has a maximum MTU size less than 521 bytes.

• 1016000D - The adjacent node does not support the Synchronous Data Link Control (SDLC) command or response profiles, which are the only profiles supported by Advanced Peer-to-Peer Networking (APPN) and low-entry networking (LEN) nodes.

• 1016000E - Product set identifier on XID3 has changed.

• 10160010 - The Asynchronous Balanced Mode (ABM) support indicated in sent and received XID3s is inconsistent.

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

• 10160014 - The adjacent node changed role from non-negotiable to negotiable.

• 10160015 - The adjacent node supports Berkeley Internet Name Domain (BIND) pacing as sender only.

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

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

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

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

• 1016001E - The adjacent node did not send its control point (CP) name in XID3, but requested CP-CP sessions on this link.

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

• 10160022 - The adjacent node included High-Performance Routing (HPR) capabilities [X'61'] control vector in its XID3 but specified a maximum MTU size less than 768.

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

• 10160026 - NCE field lengths in the HPR control flows [X'81'] subfield are inconsistent with the length of the the HPR capabilities [X'61'] control vector.

• 10160027 - The adjacent node indicated support for control flows over Rapid Transport Protocol (RTP), but did not include a HPR control flows [X'81'] subfield.

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

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

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

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   No free Transmission Group (TG) numbers are available between this node and the specified adjacent node. This condition should only occur 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   

Explanation   The system has received an exchange identification (XID) protocol error during a non-activation exchange. This condition might indicate an interoperability problem between this node and the adjacent node.

The following are sense codes:

• 0809003A - Received a null XID when an activation XID format 3 was expected.

• 0809003B - Received a null XID when a nonactivation XID format 3 was expected.

• 0809003E - Activation XID received when non-activation XID expected.

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

• 08090042 - Nonactivation exchange initiation indicator not set when expected.

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

• 10160002 - The adjacent node was inconsistent in its setting of ACTPU suppression indicator.

• 10160008 - The adjacent node was inconsistent in its setting of networking capabilities.

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

• 10160019 - The adjacent node has attempted to change its control point (CP) name when control point to control point sessions supported on link station, or link station not quiesced. The link will be deactivated.

Recommended Action   Run a trace on the link station or port to obtain more diagnostic information on the problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The link to the host has been configured incorrectly as a link to a downstream physical unit (DSPU). The 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   

Explanation   An unexpected SET_MODE has been received from an adjacent host before the exchange identification (XID) exchange had completed, and there was not a link configured to that host. An implicit link cannot be activated because there is not a local Physical Unit (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   

Explanation   The system attempted to activate more than one Transmission Group (TG) to an adjacent node that does not support parallel TGs. Link activation will fail.

Recommended Action   Modify the configuration so that there is only one link station defined to the specified adjacent node. Several links to the adjacent node can be defined, but only one can be active concurrently.

Error Message   

Explanation   There is insufficient storage to perform an 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   There were conflicting requirements for error recovery between the local node and a partner node when attempting to activate a link that is High-Performance Routing (HPR) capable. The link will activate, but the link will not be HPR capable. To allow HPR protocols to be used on the local link and partner nodes, each one must be able to accommodate the error recovery requirements of the other.

Recommended Action   This condition will require reconfiguration, but that reconfiguration might not be possible.

Error Message   

Explanation   There is insufficient storage to update the Automatic Network Routing (ANR) routing tables following the deactivation of a High-Performance Routing (HPR)-capable link. This node might be unable to free resources that are no longer required. The system 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 Systems Network Architecture (SNA) switch

Error Message   

Explanation   There is insufficient storage to update the Automatic Network Routing (ANR) routing tables following the activation of a High-Performance Routing (HPR)-capable link. HPR traffic using this ANR label will not be routed correctly and might cause Rapid Transport Protocol (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 Systems Network Architecture (SNA) switch

Error Message   

Explanation   Data-link control (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 is persistent, look for DLC specific logs that give more information on the reason for the failure.

Error Message   

Explanation   There is insufficient storage to forward an alert generated by the data-link control (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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The system has been unable to deactivate this port. The snasw stop port command will fail, and the port might not restart successfully.

Recommended Action   If required, attempt to restart the port. If the restart fails, look for data-link control (DLC) specific logs that give more information on the reason for the failure. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The system experienced an unrecoverable data-link control (DLC) failure. 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. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A session or application required the Systems Network Architecture (SNA) switch to automatically activate a link station. The link station was not configured to be automatically activated, or the link station was not stopped automatically the last time that it was stopped. The session or application will fail with the specified sense code.

Recommended Action   Enter the snasw start link command to manually activate the link, or redefine the link to support automatic activation using the snasw link command.

Error Message   

Explanation   A session or application required the Systems Network Architecture (SNA) switch to automatically activate a link station. The request failed because the owning port was not active. This condition usually indicates an inconsistent network topology that might 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 conditions warrant, increase the port link-activation limits or check the consistency of the network topology.

Error Message   

Explanation   A session required the Systems Network Architecture (SNA) switch to automatically activate a link station. The SNA switch has been unable to identify the requested link. This condition usually indicates an inconsistent network topology that might 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   

Explanation   A session required the Systems Network Architecture (SNA) switch to automatically activate a dynamic link station. The request failed because the owning port was not active. This condition usually indicates an inconsistent network topology that might 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   If conditions warrant, increase the port activation limits or, check the consistency of the network topology.

Error Message   

Explanation   A session required the Systems Network Architecture (SNA) switch to automatically activate a dynamic link station. The SNA switch has been unable to identify the requested connection network. This condition usually indicates an inconsistent network topology that might 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   

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   

Explanation   The control point (CP) name on an exchange identification (XID) 3 that has been received from an adjacent node is different than expected. 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   

Explanation   The node ID on an exchange identification (XID) 3 that was received from a back level node is different than expected. 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   

Explanation   The node type indicated on an exchange identification (XID) 3 that was received from an adjacent node is different than expected. 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   

Explanation   Both sent and received exchange identifications (XID) indicate the same, non-negotiable 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   

Explanation   A session or application required the Systems Network Architecture (SNA) switch to automatically activate a link station. The request failed because it would have exceeded the port total link-activation limit. This condition usually indicates an inconsistent network topology that might 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   

Explanation   A session or application required the Systems Network Architecture (SNA) switch to automatically activate a link station. 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 inconsistent network topology that might 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   

Explanation   A session required the Systems Network Architecture (SNA) switch to automatically activate a dynamic link station. The request failed because it would have exceeded the port total link-activation limit. This problem usually indicates an inconsistent network topology that might 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   

Explanation   A session required the Systems Network Architecture (SNA) switch to automatically activate a dynamic link station. 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 condition usually indicates an inconsistent network topology that might 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   

Explanation   A non-Advanced Peer-to-Peer Networking (APPN) link station to an upstream host has been successfully started.

Recommended Action   No action is required.

Error Message   

Explanation   A non-Advanced Peer-to-Peer Networking (APPN) link station to a downstream Physical Unit (PU) has been successfully started.

Recommended Action   No action is required.

Error Message   

Explanation   A non-Advanced Peer-to-Peer Networking (APPN) link station to an upstream host has been successfully stopped.

Recommended Action   No action is required.

Error Message   

Explanation   A non-Advanced Peer-to-Peer Networking (APPN) link station to a downstream Physical Unit (PU) has been successfully stopped.

Recommended Action   No action is required.

Error Message   

Explanation   A locally initiated dependent session activation request required the Systems Network Architecture (SNA) switch to automatically activate a link to a specified Physical Unit (PU) name, but the SNA switch was unable to identify a link to the PU. This condition indicates an inconsistent local configuration. The configuration 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. The link definitions can be viewed by entering the show snasw link command.

Error Message   

Explanation   The Systems Network Architecture (SNA) switch link has been successfully started.

Recommended Action   No action is required.

Error Message   

Explanation   Intra-node session support ended abnormally. This situation should only occur because of a shortage of available storage. Any active intra-node sessions will fail, and no more intra-node sessions will 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   A session required the Systems Network Architecture (SNA) switch to automatically activate a dynamic link station. The SNA switch was unable to identify the requested connection network Transmission Group (TG). This condition usually indicates an inconsistent network topology that might 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   

Explanation   There was insufficient storage to generate 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The Systems Network Architecture (SNA) switch link has been successfully started on a node that supports High-Performance Routing (HPR).

Recommended Action   No action is required.

Error Message   

Explanation   The Systems Network Architecture (SNA) switch link has been successfully stopped.

Recommended Action   No action is required.

Error Message   

Explanation   A data-link control (DLC) has been successfully started.

Recommended Action   No action is required.

Error Message   

Explanation   A data-link control (DLC) has been successfully stopped.

Recommended Action   No action is required.

Error Message   

Explanation   A port has been successfully started.

Recommended Action   No action is required.

Error Message   

Explanation   A port has been successfully stopped.

Recommended Action   No action is required.

Error Message   

Explanation   The specified link is configured to support control point (CP) to CP sessions. The CP to CP sessions could not be started. This condition could have occurred because the remote node is not configured to support CP to CP sessions on this link or because both the local and remote nodes are End Nodes (CP to CP sessions are not allowed to be started at End Nodes). The CP to CP sessions will not be established.

Recommended Action   Correct the configuration mismatch by removing CP to CP session support from the local connection definition, or by adding CP to CP session support to the connection definition of the adjacent node.

Error Message   

Explanation   A data-link control (DLC) could not be started 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The specified link station is configured with a pre-defined Transmission Group (TG) number, but the adjacent node has sent a different non-zero 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   

Explanation   An adjacent node has attempted to use a Transmission Group (TG) number for a link that is already pre-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   

Explanation   An adjacent node has attempted to use a Transmission Group (TG) number for this link that is already in use by another link station. This condition might 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. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   An adjacent node has changed its control point (CP) name.

Recommended Action   No action is required.

Error Message   

Explanation   There is insufficient storage to update the topology database with link station information. The topology will be inconsistent, and this condition might result in unexpected session activation failures (typically with sense codes 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 Systems Network Architecture (SNA) switch. Cycling the specified link station by either activating then deactivating or by deactivating then activating might clear the condition.

Error Message   

Explanation   There is insufficient storage to update the topology database with connection network information. The topology will be inconsistent, and this condition might result in unexpected session activation failures (typically with sense codes 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 Systems Network Architecture (SNA) switch. Cycling the specified link station by either activating then deactivating or by deactivating then activating might clear the condition.

Error Message   

Explanation   There is insufficient storage to enable intra-node sessions. Intra-node sessions 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 Systems Network Architecture (SNA) switch.

Error Message   

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 that is being activated is:

• 1 - dynamic

• 3 - implicit

• 4 - discovery

Recommended Action   No action is required

Error Message   

Explanation   A link activation race has been detected on an ATM port. The local node is responsible for resolving this race, and the local node will disconnect its link. The remote node link activation request will succeed.

Recommended Action   This is a normal race condition. No action is required.

Error Message   

Explanation   A link activation race has been 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 local node link activation request will succeed.

Recommended Action   This is a normal race condition. No action is required.

Error Message   

Explanation   A PORT_BANDWIDTH_UPDATE signal (status = QUIESCING) has been received. Any Connection Network Transmission Group (TGs) on this port will be advertised as quiescent. Any auto-activated TGs will be advertised as non-operational.

Recommended Action   If conditions warrant, increase the bandwidth available to the local port.

Error Message   

Explanation   A PORT_BANDWIDTH_UPDATE signal with status set to OK has been received. Any Connection Network Transmission Group (TGs) on this port that have been advertised as quiescent will be advertised as active. Any auto-activated TGs that have been advertised as non-operational will be advertised as operational.

Recommended Action   To avoid future problems with bandwidth shortage, increase the bandwidth available to the local port.

Error Message   

Explanation   The data-link control (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. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   An automatic retry link station is inactive after the system has tried to reactivate the station the maximum number of allowed retries. The link station will remain inactive awaiting operator intervention. The activation of any sessions relying on this link station will fail if this condition is not corrected.

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   

Explanation   The Systems Network Architecture (SNA) switch cannot start a link to an adjacent node over a connection network Transmission Group (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   

Explanation   The Systems Network Architecture (SNA) switch cannot start a link to an adjacent node over a connection network Transmission Group (TG) because the data-link control (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   

Explanation   A Branch Network node has insufficient resources to (un)register an adjacent low entry networking (LEN) node. The directory of the LEN node and the node of the NNS might become inconsistent. This condition might cause the LEN control point (CP) to still be seen as active when it is inactive, or the LEN CP might be seen as inactive when it is active. A session activation to the LEN might fail when a link to it is active, or the neighboring nodes might believe the LEN to be contactable when the link to that LEN is down.

Recommended Action   Ensure sufficient resources are available to the Systems Network Architecture (SNA) switch and then re-cycle the link to the required state.

Error Message   

Explanation   An invalid Transmission Group (TG) descriptor has been received from a Dependent Logical Unit Server (DLUS). The Physical Unit (PU) will not be activated.

Recommended Action   Check the configuration of the DLUS that is named by this log. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A Dependent Logical Unit Server (DLUS)-defined downstream Dependent Logical Unit Requester (DLUR)-served link could not be defined. This condition occurred because the specified port does not exist, or there is an existing link station to the same destination address. The Physical Unit (PU) will not be activated.

Recommended Action   Correct the configuration.

Error Message   

Explanation   A Dependent Logical Unit Server (DLUS)-defined downstream link failed to activate. The Physical Unit (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 that the named LS has not activated. Check the configuration of the DLUS.

Error Message   

Explanation   A Dependent Logical Unit Server (DLUS)-defined downstream physical unit (DSPU) name clashes with the locally defined DSPU name of a different Physical Unit (PU). An implicit link will fail. The ACTPU for the DSPU that is connected over this link will be rejected.

Recommended Action   Reconfigure this node or the DLUS to remove the clash in the use of this PU name. If the DLUS and the Dependent Logical Unit Requester (DLUR) use the same PU name, then they must apply this name to the same PU.

Error Message   

Explanation   There is insufficient information to create a Dependent Logical Unit Server (DLUS)-defined link. A Physical Unit (PU) will not be activated. The ACTPU for the named PU will be rejected with the given sense code.

Recommended Action   Correct the Physical Unit (PU) definition at the DLUS. The DLUS-defined link could not be created using the information from the DLUS in the Transmission Group (TG) descriptor (CV x'46') shown below.

For example, for a Token-Ring link to be created, the Systems Network Architecture (SNA) switch requires the x'46' to contain the following subfields:

• x'91' Signalling information CV specifying EBCDIC 'TR.'

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

• x'93' LSAP info containing a 1-byte destination SAP address.

• x'94' MAC info containing a 6-byte destination MAC address.

Error Message   

Explanation   An internal software error has occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   An internal software error has occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   An internal software error has occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   An error has been received from CLS, which typically indicates a configuration error.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The system is unable to correlate a received UNBIND request to a Dependent Logical Unit Requester (DLUR)-supported session. This is a normal race condition caused by the UNBIND requests crossing.

Recommended Action   No action is required.

Error Message   

Explanation   A Dependent Logical Unit Server (DLUS) has rejected a REQACTPU with given sense code. A system services control points (SSCP) Physical Unit (PU) session with the given DLUS will not be activated. If a backup DLUS is configured for the Physical Unit (PU), a Dependent Logical Unit Requester (DLUR) will attempt to activate the PU via the backup DLUS.

Recommended Action   Examine the sense code and retry activation if appropriate.

Error Message   

Explanation   A CPSVRMGR pipe has failed to the specified Dependent Logical Unit Server (DLUS). Any Physical Units (PU) using the specified DLUS are deactivated, and the DACTPU (cold) is sent. The Dependent Logical Unit Requester (DLUR) might attempt to contact one or more backup DLUSs.

Recommended Action   Manually restart any required PUs if a pipe with a backup DLUS is not initiated automatically.

Error Message   

Explanation   The Dependent Logical Unit Server (DLUS) names are inconsistent. The host has requested the activation of a downstream link to a Physical Unit (PU) by sending an ACTPU. The link is configured to request a different DLUS. The DLUS initiating the activation is used.

Recommended Action   Adjust the downstream link configuration if the host DLUS is the regular DLUS (not a backup). No immediate action is required.

Error Message   

Explanation   A protocol error from a Dependent Logical Unit Server (DLUS) has occurred. The host received a request/response unit (RU) too large for the system services control point (SSCP) session. This condition is typically caused by the SSCP sending a LOGON screen that is too large. The data is lost.

Recommended Action   If you are expecting an SSCP LOGON screen, enter your LOGON command as usual.

Error Message   

Explanation   The Dependent Logical Unit Requester (DLUR) has failed to contact either the Dependent LU Server (DLUS) or the backup/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 information about the causes of individual failures to contact the host. Correct any problems, increase the timeout or retry count, and make another attempt.

Error Message   

Explanation   The system has received a Primary Logical Unit (PLU)/Secondary Logical Unit (SLU) Berkeley Internet Name Domain (BIND) request with a duplicate fully qualified procedure correlation identifier (FQPCID). Session activation will fail with the specified sense code (083B0002).

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information., and run a trace on the specified link if more diagnostics are required.

Error Message   

Explanation   A pipe to a Dependent Logical Unit Server (DLUS) has been activated.

Recommended Action   No action is required.

Error Message   

Explanation   A pipe to a Dependent Logical Unit Server (DLUS) has been deactivated.

Recommended Action   No action is required.

Error Message   

Explanation   A Dependent Logical Unit Requester (DLUR) has requested a persistent pipe to a Dependent Logical Unit Server (DLUS), but the DLUS does not support persistent pipes.

The following are sense codes:

• 088E0009 - The DLUR has failed the pipe activation because it requires all pipes to be persistent.

• 08A0000C - The DLUS has failed the pipe activation because there is no Physical Unit (PU) requiring service. 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   

Explanation   A Dependent Logical Unit Server (DLUS) has sent an ACTPU without a Physical Unit (PU) name. The ACTPU will be rejected with the specified sense code. Physical Unit (PU) activation will not continue.

Recommended Action   Check the status of the named DLUS and ensure that the named DLUS is correctly configured. An alternate solution is to reconfigure the Systems Network Architecture (SNA) switch to use a different DLUS.

Error Message   

Explanation   A Dependent Logical Unit Server (DLUS) has sent an ACTPU with a Physical Unit (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 Dependent Logical Unit Requester (DLUR) to use different Physical Unit (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   

Explanation   A Dependent Logical Unit Server (DLUS) has sent an ACTPU with a Physical Unit (PU) name that is different than the PU name in the last ACTPU that was received for the same downstream physical unit (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 in the network to use the same PU name when referring to the same PU.

Error Message   

Explanation   The Dependent Logical Unit Requester (DLUR) failed to contact either the default primary Dependent Logical Unit Server (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, increase the timeout or retry count, and make an another attempt.

Error Message   

Explanation   The Dependent Logical Unit Requestor (DLUR) is deactivating a persistent pipe because it is not required to keep it active.

Recommended Action   No action is required.

Error Message   

Explanation   An invalid MU type has been received by Dependent Logical Unit Requester (DLUR) from an internal or downstream Physical Unit (PU). The invalid MU will be discarded.

Recommended Action   If this is an internal PU, contact your Cisco technical support representative with details of this log. If this is a downstream PU, contact the supplier of the downstream node.

Error Message   

Explanation   A network search has not started because it would exceed the maximum number of concurrent locates that are supported by this node. Session activation will fail with the specified sense code.

Recommended Action   Collect a system trace, and Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A failure has occurred in this node or the network server node during a network search. The displayed sense code is an amalgam of sense codes that were received from the various nodes that took part in the search. The most common sense codes are as follows :

• 08900060 - Insufficient storage to process a locate search.

• 08900010 - Routing error on a directed locate search.

• 08900070 - Session outage in the search tree.

• 0812000A - Insufficient resources at the CDS.

These sense codes usually indicate a transient problem in the network (either a resource shortage or link failure). Session activation will fail with the specified sense code.

Recommended Action   Retry the session activation. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The system has received a badly formed locate request from an adjacent node. This condition might indicate an interoperability problem. The following are sense codes:

• 1010B080 - Missing command parameters control vector in a Found GDS variable.

• 10140080 - GDS variable or control vector length error.

• 1014A082 - Missing search argument directory entry in a Find GDS variable control point (CP)-to-control point sessions with adjacent node will be deactivated with the specified sense code.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   There is insufficient storage to process a locate request that has been received from an adjacent node. Control point (CP) to control point 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   A locate request has been received with the no find general data stream (GDS) variable.

Recommended Action   No action is required.

Error Message   

Explanation   There is insufficient storage for control point to control point (CP) sessions. CP to 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   All control point (CP) to CP sessions have been deactivated while the broadcast locate request is in process. The session activation might fail.

Recommended Action   This log simply flags the fact that a session failure impacted a pending broadcast. Look at other more specific logs to give the reasons for the session failure and the appropriate actions.

Error Message   

Explanation   The system has received a registration or deletion request from an unknown end node. This condition might indicate an interoperability problem, but the condition is not considered fatal. The registration request is discarded.

Recommended Action   No action is required.

Error Message   

Explanation   There is insufficient storage to register resources that are 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 might fail if the end node is unable to register the resource.

Recommended Action   Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to the Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The system has failed to register a resource for a served end node because the resource is already registered with a different parent resource. This condition typically occurs when the same logical unit (LU) is defined on two or more end nodes. The registration request is rejected, which might result in other resources not being registered and subsequent network search failures.

Recommended Action   Remove or rename the LU on one of the end nodes.

Error Message   

Explanation   The registration failure general data stream (GDS) variable that was received from the network node server is badly formed. This condition might indicate an interoperability problem. Control point (CP) to control point sessions to the node will be deactivated.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   There has been a link or session failure while registering resources with the network node server. Control point (CP) to control point sessions to node will be deactivated.

Recommended Action   A registration request has been disrupted by the link or session failure. Other more specific logs give details on the reasons for the failure and the appropriate actions.

Error Message   

Explanation   There has been a protocol error while registering resources with the network node server. Control point (CP) to control point sessions to the node will be deactivated.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A local node has timed out after waiting for a locate response from the specified adjacent node. This condition typically indicates a problem in another node in the network. The other node is not responding to the locates (possibly because only one control point (CP) to control point session is active with an adjacent node). The locate will fail with the specified sense code. The following are the Sense codes:

• 08120010 - The adjacent CP is short of resources; CP to CP sessions will be deactivated.

• 08900060 - Search failure; the adjacent CP does not have sufficient resources, but CP to CP sessions will not be deactivated.

Recommended Action   Verify that there are no nodes in the network with a single CP to CP session active to an adjacent node.

Error Message   

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 a snasw location command has been used to define logical units (LUs) that are owned by served end or low entry networking (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   

Explanation   A served end node attempted to delete a directory entry that does not exist. This condition is normally caused by a network race condition and 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   

Explanation   A served end node attempted to delete a resource when that node was not registered as the owner of the resource. This condition might indicate an interoperability problem. The delete request is rejected with the specified sense code. This condition might cause the end node to deactivate control point (CP) to control point sessions.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The system has received a register or delete general data stream (GDS) variable from a served end node that contained format errors. The following are sense codes:

• 08950000 - GDS variable or control vector length error.

• 10140080 - Invalid control vector register or delete attempt is rejected. The resources specified will not be registered.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The network node server has rejected a register request with a sense code that indicates this node is not authorized to register resources at the network node. This condition usually indicates a mismatch between the network node server configuration (to consider this end node unauthorized) and this node configuration (to register resources). No further resource registration will occur until control point (CP) to control point sessions are deactivated and reestablished.

Recommended Action   Modify the network node server configuration to consider this node authorized.

Error Message   

Explanation   A resource registration has failed because the network node server directory is full. This condition might indicate a shortage of storage at the network node or a configured upper bound on the size of the directory. No further resource registration will occur until control point (CP) to control point sessions are deactivated and reestablished.

Recommended Action   Increase the size of the directory at the network server. This action might be a simple configuration change or might require freeing up storage by reducing the load at the server.

Error Message   

Explanation   A resource registration has failed because the resource conflicted with existing resources in the network node server directory. This situation commonly occurs when two LUs with the same name are defined on two different end nodes that are being served by the same network node. This situation might 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 network node directory 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   

Explanation   A resource registration has failed because the network node server detected a protocol error in the register request. This condition might indicate an interoperability problem. Registration of the resource in question will fail, but other resources should still be registered correctly.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A resource registration has failed with an unknown sense code. This condition might indicate an interoperability problem. No further resource registration will occur until control point (CP) to control point sessions are deactivated and reestablished.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A delete reply has been received with an unrecoverable sense code. Control point (CP) to control point sessions to the node will be deactivated.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A directory error correlator has been returned on a register, or a delete reply cannot be correlated to a directory entry. This situation is considered a protocol error and might indicate an interoperability problem. Control point (CP) to control point sessions to node will be deactivated.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The network node server has rejected a delete request with a sense code that indicates this node is not authorized to register resources at the network node. This situation usually indicates a mismatch between the network node server configuration (to consider this end node unauthorized) and this node configuration (to register resources). No further resource registration or deletion will occur until control point (CP) to control point sessions are deactivated and reestablished.

Recommended Action   Modify the network node server configuration to consider this node authorized.

Error Message   

Explanation   A delete request failed because the entry has been defined as a home entry at the network node server or because the resource was not found. These errors are not severe. These errors will not affect future registration, deletion, or other aspects of network operation. The delete attempt has failed, and future deletion and registration will continue unaffected.

Recommended Action   No action is required.

Error Message   

Explanation   There is an invalid resource name in the received register request. The register request will fail.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   There is a central resource registration failure. The network performance might degrade because of the additional broadcast locate searches.

Recommended Action   No action is required.

Error Message   

Explanation   A central resource registration failure and invalid correlator has been received. Network performance might degrade because of additional broadcast locate searches.

Recommended Action   No action is required.

Error Message   

Explanation   The Central Directory Server has been located.

Recommended Action   No action is required.

Error Message   

Explanation   A locate has been received from an adjacent node that exceeded the maximum number of concurrent locates that are supported by this node. Control point (CP) to control point sessions with the adjacent node will be deactivated to avoid possible deadlocks.

Recommended Action   The network will recover from this problem, and the CP to CP sessions will be reactivated. If the problem persists, collect trace information, and report it to a Cisco technical support representative.

Error Message   

Explanation   There is insufficient storage to start a network search. Session activation will fail with the specified sense code.

Recommended Action   Make more resources available to the Systems Network Architecture (SNA) switch.

Error Message   

Explanation   Control point (CP) to control point sessions are deactivated while the directed locate request is in process. Session activation might fail.

Recommended Action   A session failure impacted a pending directed locate request. Other, more specific logs give reasons for the session failure and appropriate actions.

Error Message   

Explanation   Either the network node server or a network search for which this node was the originator failed to locate the target Logical Unit (LU). This condition might be caused by the target LU name being incorrect, the target system being inoperative, or by link errors in the backbone of the network. The session activation will fail with the specified sense code.

Recommended Action   If the target Logical Unit (LU) name is correct, check that the system the LU is defined on is active. If the system is active, check the topology of the network to ensure that the target system or the network node server of the target system is reachable from this node.

Error Message   

Explanation   Control point (CP) to (CP) sessions have been established with an adjacent end node that was previously defined using the Systems Network Architecture (SNA) switch location. The invalid directory definitions for the end node and any of its Logical Units (LU) will be removed.

Recommended Action   Do not configure the invalid entries in future.

Error Message   

Explanation   A Branch Network node has insufficient resources to (un)register an adjacent low entry networking (LEN) node. The directory of the LEN node and the node of the NNS might become inconsistent. This condition might cause the LEN control point (CP) to still be seen as active when it is inactive, or the LEN CP might be seen as inactive when it is active. A session activation to the LEN might fail when a link to it is active, or the neighboring nodes might believe the LEN to be contactable when the link to the LEN is down.

Recommended Action   Ensure sufficient resources are available to the Systems Network Architecture (SNA) switch and then re-cycle the link to the required state.

Error Message   

Explanation   A directed locate for this logical unit (LU) has been tried, but the LU is 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   

Explanation   The system failed to allocate memory for the storage of a resource in the register list, and registration will not take place immediately.

Recommended Action   No action is required.

Error Message   

Explanation   A locate reply has been received that contained an invalid Route Selection Control Vector (RSCV). The locate request that solicited the reply might have failed.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A Branch Network node has insufficient resources to (un)register an adjacent low entry networking (LEN) node. The directory of the LEN node and the node of the NNS might become inconsistent. This condition might cause the LEN control point (CP) to still be seen as active when it is inactive, or the LEN CP might be seen as inactive when it is active. A session activation to the LEN might fail when a link to it is active, or the neighboring nodes might believe the LEN to be contactable when the link to the LEN is down.

Recommended Action   Ensure sufficient resources are available to the Systems Network Architecture (SNA) switch and then re-cycle the link to the required state.

Error Message   

Explanation   The node has been configured to register low-entry networking (LEN) logical unit (LU) names when Berkeley Internet Name Domains (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 control point (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 network node directory for the duplicate entry. If it is a home entry, then 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   

Explanation   This message is for informational purposes only.

Recommended Action   No action is required.

Error Message   

Explanation   A High-Performance Routing (HPR) route setup request/response unit (RU) has been received with format errors. The message cannot be processed, and the message will be discarded.

Recommended Action   Report error to the remote end.

Error Message   

Explanation   The system is unable to correlate a High-Performance Routing (HPR) route setup reply. The message cannot be processed, and the message will be discarded.

Recommended Action   Report the error to the remote end.

Error Message   

Explanation   The system is unable to activate the Rapid Transport Protocol (RTP) connection. In certain situations, the origin might retry activation.

Recommended Action   Examine the sense code, and retry activation, if appropriate.

Error Message   

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 -ve reply.

Recommended Action   Investigate the link failure.

Error Message   

Explanation   The High-Performance Routing (HPR) manager failed to allocate memory to send a Rapid Transport Protocol (RTP) indication. The data_lost flag will be set in the next successfully sent indication.

Recommended Action   Investigate the memory shortage.

Error Message   

Explanation   A Network Layer Packet (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   

Explanation   A Network Layer Packet (NLP) has been received for a Rapid Transport Protocol (RTP) connection that no longer exists. The message cannot be processed, and the message will be discarded.

Recommended Action   Report the error to the remote end.

Error Message   

Explanation   A connection setup Network Layer Packet (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 Rapid Transport Protocol (RTP) connection can be started, and the NLP will be discarded.

Recommended Action   Report the error to the remote end.

Error Message   

Explanation   The local node has received a High-Performance Routing (HPR) route setup request/response unit (RU) that the local node cannot forward because the next hop in the route is not HPR-capable. The local node does not support Rapid Transport Protocol (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 fail. RTP connections cannot be activated between these two nodes. This is a normal condition when the local node has an auto-activated link to a node that does not support HPR. An intermediate node in the route that supports RTP might possibly take over the role of the destination node for the route setup. If this condition happens to sessions that originate at or beyond the origin node, the origin node will use HPR from the origin to the new destination and use Intermediate Session Routing (ISR) from the new destination to the local node and beyond. If no intermediate node is able to act as the destination, HPR will not be used at all by the sessions.

Recommended Action   No action is required.

Error Message   

Explanation   The local node has received a High-Performance Routing (HPR) route setup RU that it cannot forward because the next hop in the route is not HPR-capable. The local node supports Rapid Transport Protocol (RTP), so the local node can act as the destination. The route setup will be between the origin node and the local node (the new destination). RTP connections will be activated between these two nodes. This is a normal condition when the local node has an auto-activated link 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 Intermediate Session Routing (ISR) from the new destination and beyond it.

Recommended Action   No action is required.

Error Message   

Explanation   The local node has received a High-Performance Routing (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 was successfully backed out. The route setup is between the origin node and the local node (the new destination). Rapid Transport Protocol (RTP) connections will be activated between these two nodes. This is a normal condition when a node in the route has an auto-activated link 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 Intermediate Session Routing (ISR) from the new destination and beyond it.

Recommended Action   No action is required.

Error Message   

Explanation   The local node has received an High-Performance Routing (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. Rapid Transport Protocol (RTP) connections will be activated between these two nodes. This is a normal condition when a node in the route has an auto-activated link 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 Intermediate Session Routing (ISR) from the new destination and beyond it.

Recommended Action   No action is required.

Error Message   

Explanation   The local node has received a High-Performance Routing (HPR) route setup reply with the backout sense code. The route setup has failed because the destination node does not support Rapid Transport Protocol (RTP). No intermediate node supports RTP and became the new destination. The route setup has failed, and HPR will not be used for the activated session. This is a normal condition when a node in the route has an auto-activated link to a node that does not support RTP or HPR.

Recommended Action   No action is required.

Error Message   

Explanation   The local node has received a High-Performance Routing (HPR) route setup RU as the destination node but cannot accept the RU because the local node does not support Rapid Transport Protocol (RTP). The local node replies with the backout sense code. The route setup between the origin node and the local node will fail. RTP connections cannot be activated between these two nodes. This is a normal condition when another HPR-capable node has an auto-activated link to this node. It might 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 happens, sessions that originate at or beyond the origin node will use HPR from the origin to the new destination and use Intermediate Session Routing (ISR) from the new destination to the local node and beyond. 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   

Explanation   A connection setup Network Layer Packet (NLP) has been received from a remote NCE that has shut down and restarted. A Rapid Transport Protocol (RTP) connection still exists from that NCE before the connection shut down. The old RTP connection will be disconnected

Recommended Action   No action is required.

Error Message   

Explanation   The system is unable to activate a route setup Rapid Transport Protocol (RTP) connection, during the processing of a route setup request. The route setup request will fail with the sense code shown. 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   A connection setup Network Layer Packet (NLP) has been rejected because it specified the control point (CP) to CP session or route setup topic ID but was received on a Transmission Group (TG) that does not support the Control Flows over a Rapid Transport Protocol (RTP) tower. The CP to CP session or the route setup Rapid Transport Protocol (RTP) connection will fail with sense code HA0010017.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A High-Performance Routing (HPR) route setup request/response unit (RU) has been received with a fully qualified procedure correlation identifier (FQPCID) that matches an existing route. The message will be rejected, and the route will not be established.

Recommended Action   Report the error to the remote end.

Error Message   

Explanation   The call reference value (CRV) exchange has failed. This condition indicates that the cryptography keys that are configured at this Logical Unit (LU) and the partner LU are inconsistent. This session will be deactivated with the specified sense code (08350001).

Recommended Action   Use the information from the session deactivated problem log (log 271) to identify the local LU and partner LU and to correct the mismatch in cryptography keys.

Error Message   

Explanation   A Logical Unit type 6.2 (LU6.2) session state error has occurred. This condition might indicate an interoperability problem.

The following are sense codes:

• 20020000 - Chaining sequence error.

• 20030000 - Bracket state error.

• 20040000 - Received normal flow request when half-duplex flip-flop state not receive.

• 200A0000 - Immediate request mode violated by partner LU.

• 200B0000 - Queued response indicator invalid.

• 200E0000 - Unexpected SIGNAL response.

• 200F0000 - Received unexpected response or received EXPD RU before previous EXPD RU was acknowledged.

• 20120000 - Unexpected sense code on negative response.

• 40040000 - Received RQE, BB, CEB chain from contention loser.

• 40110000 - RU category of response does not match request.

• 40120000 - Request code of response does not match request.

• 40210000 - QRI setting on response does not match request. The session will be deactivated with the specified sense code.

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. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A Logical Unit type 6.2 (LU6.2) session format error occurred. This condition might indicate an interoperability problem.

The following are sense codes:

• 080F6051 - Security error (FMH12 error)

• 10030000 - Function not supported (unrecognized request code).

• 10050000 - SIGNAL or LUSTAT request too short.

• 10084001 - Invalid FM header type (not 5, 7 or 12).

• 40030000 - BB not allowed.

• 40040000 - CEB or EB not allowed.

• 40070000 - Definite response not allowed.

• 40090000 - CD not allowed.

• 400B0000 - Chaining error or EC,RQE1/2,CD RU received on full-duplex conversation.

• 400C0000 - Bracket error.

• 400F0000 - Incorrect use of format indicator (FI).

• 40100000 - Alternate code not supported.

• 40110000 - Incorrect specification of RU category.

• 40120000 -Incorrect specification of request code.

• 40130000 - Incorrect specification of SDI and RTI.

• 40140000 - Incorrect use of DR1I, DR2I and ERI.

• 40150000 - Incorrect use of QRI.

• 40160000 - Incorrect use of EDI.

• 40170000 - Incorrect use of PDI.

• 40180000 - Incorrect setting of QRI with bidder's BB.

• 40190000 - Incorrect indicators with last-in-chain request 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 conditions warrant, run a trace on the specified link station. Contact your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   There is has been a Logical Unit type 6.2 (LU6.2) response correlation error. This condition might indicate an interoperability problem. The sense code is 200E0000 - Uncorrelated positive response, or uncorrelated RTR response. The session will be deactivated with the specified sense code.

Recommended Action   Use information on the session deactivated problem log (271) to identify the local LU and partner LU. If required, run a trace on the specified link station and contact your Cisco technical support representative with the log and trace.

Error Message   

Explanation   The Logical Unit type 6.2 (LU6.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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   A protocol error has occurred during a call reference value (CRV) exchange. This condition indicates a possible interoperability problem.

The following are sense codes:

• 20090000 - CRV request received from secondary LU, or CRV response received from primary LU, or CRV not received when expected.

• 10020000 - CRV RU too short.

• 400F0000 - CRV with FI not set.

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

• 40140000 - CRV not RQD1.

• 40110000 - CRV not expedited.

• 40150000 - CRV with QRI not set.

• 40080000 - CRV with PI set.

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

• 400D0000 - CRV request with CDI set.

• 40100000 - CRV request with CSI set to CODE1.

• 40160000 - CRV request with EDI set.

• 40170000 - CRV request with PDI set.

• 40130000 - CRV response RTI and SDI are inconsistent. Session will be deactivated with specified sense code.

Recommended Action   Use the information from the session deactivated problem log (271) to identify the local Logical Unit (LU) and the partner LU. Run a trace on the specified link station, and contact your Cisco technical support representative with the log and trace.

Error Message   

Explanation   An incoming SIGNAL RU has been received on a full-duplex conversation. The session will be deactivated with the specified sense code (10030004).

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   An EXPD request/response unit (RU) has been received while previously expedited data remains to be processed. The session will be deactivated with the specified sense code (200F0000).

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   There is insufficient storage to initialize 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The system is unable to create a new LDLC_CTRL instance, and 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 attempt.

Recommended Action   Check the surrounding logs for evidence of buffer congestion. If buffer congestion is causing this failure, decrease the system load or make more resources available to the LDLC.

Error Message   

Explanation   A LDLC command frame retry limit has been exceeded. The link activation will fail, or an active link will be brought down.

Recommended Action   Check the connectivity to the remote address.

Error Message   

Explanation   A LDLC link has been reported as inoperative by the underlying media. The link activation will fail, or an active link will be brought down.

Recommended Action   Check for faults at the supplied destination address and for faults and error conditions in the underlying drivers and media. Check for connectivity in the underlying media and for outages on the connection path. Ensure that all of your wires are still plugged in.

Error Message   

Explanation   An unrecognized Network Layer Header (NHDR) routing instruction has occurred. The packet cannot be routed by LDLC, and the packet will be discarded. Data might be lost. This condition might indicate an interoperability problem.

Recommended Action   Check the surrounding logs for other evidence of interoperability problems. If other 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   

Explanation   A LDLC request/response unit (RU) identifier is not recognized. This packet cannot be processed by LDLC and will be discarded. Link activation and deactivation might fail, and data might be lost. This condition might indicate an interoperability problem.

Recommended Action   Check the surrounding logs for other evidence of interoperability problems. If other 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   

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, decrease the system load or make more resources available to the LDLC.

Error Message   

Explanation   Link activation race has occurred. Link activation will complete, but the routes might be different in each direction. No other effect will be noticeable.

Recommended Action   No action is required.

Error Message   

Explanation   The IPDLC could not allocate the necessary storage, and some operation might fail. See other logs for more information.

Recommended Action   Decrease the system load by reducing the number of active links, or make more storage available to the IPDLC.

Error Message   

Explanation   The IPDLC failed to request a posting. The link activation might fail, or data transmission might be delayed.

Recommended Action   Decrease the system load by reducing the number of active links, or make more storage available to the IPDLC.

Error Message   

Explanation   The IPDLC failed to grow a link hash table. Data transmission rates might 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, decrease the system load by reducing the number of active links, or make more storage available to SNAP-IPDLC.

Error Message   

Explanation   The IPDLC failed to create a User Datagram Protocol (UDP) stub, and the port activation will fail.

Recommended Action   Decrease the system load by reducing the number of active links or make more storage available to the IPDLC.

Error Message   

Explanation   The IPDLC has created a User Datagram Protocol (UDP) stub, but the UDP stub failed to initialize successfully. The 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   

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 that is passed to the Systems Network Architecture (SNA) switch on SNASw link.

Error Message   

Explanation   The system is unable to activate an IPDLC port. This condition will result in the failure of a port activation attempt. No further IPDLC operations will be possible until a port is successfully activated.

Recommended Action   Check the surrounding logs for evidence of buffer congestion. If buffer congestion is causing this failure, decrease the system load or make more resources available to IPDLC. Ensure that the necessary facilities are available for the User Datagram Protocol (UDP) interface to operate correctly. Check that valid data-link control (DLC) specific configuration data has been provided to the IPDLC at definition time.

Error Message   

Explanation   The system is unable to activate an IPDLC link, and the 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 attempt.

Recommended Action   Check the surrounding logs for evidence of buffer congestion. If buffer congestion is causing this failure, decrease the system load or make more resources available to the IPDLC. Ensure that the necessary facilities are available for the User Datagram Protocol (UDP) interface to operate correctly. Check that valid data-link control (DLC) specific configuration data has been provided to SNAP-IPDLC at define time.

Error Message   

Explanation   The User Datagram Protocol (UDP) stub process has abended. IPDLC will abend itself. All links using SNAP-IPDLC will fail, and SNAP-IPDLC will fail.

Recommended Action   Check for the UDP/IP problem that caused the UDP stub to abend. If the reason cannot be determined, gather a full trace and contact your Cisco technical support representative.

Error Message   

Explanation   A Logical Unit (LU) system services control points (SSCP) session has been activated.

Recommended Action   No action is required.

Error Message   

Explanation   A Primary Logical Unit (PLU) /Secondary Logical Unit (SLU) session has been activated.

Recommended Action   No action is required.

Error Message   

Explanation   A Logical Unit (LU) system services control points (SSCP) session has been deactivated.

Recommended Action   No action is required.

Error Message   

Explanation   A Primary Logical Unit (PLU) /Secondary Logical Unit (SLU) session has been deactivated.

Recommended Action   No action is required.

Error Message   

Explanation   There is insufficient storage to dynamically define a dependent logical unit (LU) with a host. Logical unit (LU) system services control points (SSCP) sessions 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   There is insufficient storage for a Berkeley Internet Name Domain (BIND) logical unit (LU) type 0, 1, 2, or 3 Primary Logical Unit (PLU) /Secondary Logical Unit session. The BIND requests 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   There is insufficient storage to send Real Time Monitor (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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   There is insufficient storage to report Real Time Monitor (RTM) status to the application. The RTM statistics are reported and displayed by the application. This information might 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   There is insufficient storage to activate a logical unit (LU) system services control points (SSCP) session for LU type 0, 1, 2, or 3. ACTLU requests 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   There is insufficient storage to activate a LU type 0, 1, 2, or 3 Primary Logical Unit (PLU)/Secondary Logical Unit (SLU) session. Berkeley Internet Name Domain (BIND) requests 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   There is insufficient storage to activate a Logical Unit (LU) system services control points (SSCP) session for LU type 0, 1, 2, or 3. ACTLU requests 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   A Berkeley Internet Name Domain (BIND) request has been received by a Logical Unit (LU) type 0, 1, 2, or 3 that failed parameter checks. The sense codes that apply to this condition follow:

• 08210004 - Cryptography required by the Secondary Logical Unit (SLU) is not supported by the Primary Logical Unit (PLU).

• 08210005 - Session key missing 0835xxxx, with parameter error at offset xxxx in Berkeley Internet Name Domain (BIND) request/response unit (RU). The offsets that apply to this sense code follow:

  • 0002 - Invalid FM profile.

  • 0003 - Invalid TS profile.

  • 0004 - Invalid primary FM usage.

  • 0005 - Invalid secondary FM usage.

  • 0006 - Invalid common FM usage.

  • 0007 - Invalid common FM usage.

  • 0008 - Invalid secondary send pacing.

  • 0009 - Invalid secondary receive pacing.

  • 000A - Invalid secondary send RU size.

  • 000B - Invalid secondary receive RU size.

  • 000E - Invalid PS profile (invalid session type).

  • 000F - Invalid PS usage (applies to remote job entry Berkeley Internet Name Domain, or RJE BIND, only).

  • 0010 - Invalid primary half-session PS usage (applies to RJE BIND only).

  • 0014 - Invalid default screen size: rows (applies to 3270 display BIND only); invalid default buffer size: rows (applies to 3270 printer BIND only).

  • 0015 - Invalid default screen size: columns (applies to 3270 display BIND only); invalid default buffer size: columns (applies to 3270 printer BIND only).

  • 0016 - Invalid alternate screen size: rows (applies to 3270 display BIND only); invalid alternate buffer size: rows (applies to 3270 printer BIND only).

  • 0017 - Invalid alternate screen size: columns (applies to 3270 display BIND only); invalid alternate buffer size: columns (applies to 3270 printer BIND only).

  • 001A - Invalid cryptography.

  • 001B - Invalid cryptography method BIND request will be rejected with the specified sense code. The A Primary Logical Unit (PLU) /Secondary Logical Unit (SLU) session has been activated. session is not activated.

Recommended Action   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, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A Berkeley Internet Name Domain (BIND) request that was received by a Logical Unit (LU) type 0, 1, 2, or 3 was rejected by an application connected to the Systems Network Architecture (SNA) switch. The BIND request will be rejected with the specified sense code. Primary Logical Unit (PLU) /Secondary Logical Unit (SLU) sessions have not been activated.

Recommended Action   Investigate why the application rejected the BIND request; the sense code should help with this. It might be necessary to investigate the configuration of the system that sent the BIND request, if possible. If a configuration error is found, correct the error. If the error message cannot be found, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A Berkeley Internet Name Domain (BIND) request was received by a logical unit (LU) type 0, 1, 2, or 3 and has been rejected because the application connection was not open. This condition might be caused by a normal window condition, or this condition might indicate that the system that sent the BIND request is incorrectly configured or is defective. BIND requests will be rejected with the specified sense code. Primary Logical Unit (PLU)/Secondary Logical Unit (SLU) sessions are 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, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   An ACTLU has been received for a Logical Unit (LU) from the wrong system services control points (SSCP). The ACTLU was rejected with the sense code 084B0000. The LU activation attempt fails.

Recommended Action   If it is necessary for the activation attempt to succeed, the definition must be changed. The LU configuration must be changed to require the correct SSCP identifier or to accept any SSCP identifier.

Error Message   

Explanation   An UNBIND RSP has been received at a secondary logical unit (LU). This is an illegal condition for Systems Network Architecture (SNA) because no UNBIND RQ was sent. The UNBIND RSP is dropped.

Recommended Action   The session might not be coming down properly. Check that the dependent logical unit (LU) applications are correctly replying to all signals. If 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, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The call reference value (CRV) exchange has failed. This condition indicates that the cryptography keys configured at this logical unit (LU) and the partner LU are inconsistent. The session will be deactivated with the specified sense code (08350001).

Recommended Action   Correct the mismatch in cryptography keys.

Error Message   

Explanation   There is either a critical buffer shortage, a protocol error, or a call reference value (CRV) exchange protocol error. This condition indicates a possible interoperability problem.

Sense codes for CRV exchange errors are as follows:

• 20090000 - CRV request received from secondary LU, or CRV response received from primary LU, or CRV not received when expected.

• 10020000 - CRV RU too short.

• 400F0000 - CRV with FI not set.

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

• 40140000 - CRV not RQD1.

• 40110000 - CRV not expedited.

• 40150000 - CRV with QRI not set.

• 40080000 - CRV with PI set.

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

• 400D0000 - CRV request with CDI set.

• 40100000 - CRV request with CSI set to CODE1.

• 40160000 - CRV request with EDI set.

• 40170000 - CRV request with PDI set.

• 40130000 - CRV response RTI and SDI inconsistent. Session will be deactivated with specified sense code.

Recommended Action   If the surrounding logs indicate that congestion is critical, decrease the system load or make more resources available to the Systems Network Architecture (SNA) switch. If this information does not adequately solve the problem, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   An internal software error has occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   An internal software error has occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   An internal software error has occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   There is insufficient storage to deliver the MDS_MU to a registered application. The MU will be returned to the sender, indicating that there is a resource shortage error.

Recommended Action   Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to the Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The system has been 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 the resource shortage error.

Recommended Action   Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to the Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The system has been unable to add the product set ID or the date time stamp requested. This condition occurred because of a 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   TRANSFER_MS_DATA/SEND_MDS_MU data has arrived.

Recommended Action   No action is required.

Error Message   

Explanation   The system is unable to allocate memory and unable to log the data that has been 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   A signal has been received that could not be recognized and could not be returned to the sender. The signal memory will be made available to the system.

Recommended Action   Check that the issued signals are acceptable for the Application Programming Interface (API) specification.

Error Message   

Explanation   A memory failure has 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The system is unable to allocate control block space to process an incoming verb. The verb will not be processed, and the verb 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The system has been unable to allocate the memory required to send an alert, and the alert will not be sent. 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The system has not been able to allocate the memory necessary to process a MDS_MU. The MDS_MU will not be processed. If the MDS_MU originated at the local node, the SEND_MDS_MU verb that contains 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   A correlation error has occurred while processing a MDS_MU. The MDS_MU will not be processed. If the MDS_MU originated at the local node, the SEND_MDS_MU verb that contains 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 might 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   

Explanation   There is insufficient storage to pass an alert to the registered Alert Handler. The alert will logged but not sent.

Recommended Action   Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to the Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The system has received a send failure for an alert that is stored in the send alert queue. No function is available to store the alert until another focal point is established. The alert will be sent but not logged.

Recommended Action   No action is required.

Error Message   

Explanation   The system has been unable to correlate an error that has been received on an "alert send" with the alerts that are stored in the send alert queue. The send alert queue is either too small and the original alert was deleted, or a previous error prevented the alert from being held in 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 in the queue.

Error Message   

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 might lead to further unexpected occurrences.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   MS capabilities has been unable 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   MS capabilities has received an error message. This message might 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 effects the focal point table.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The MDS failed to get the required memory during a 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   There is insufficient storage to process 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 Systems Network Architecture (SNA) switch.

Error Message   

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   

Explanation   There is insufficient storage to queue 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The MDS is 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The MDS has been 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   An MDS Transaction Program has received an unexpected what_received. The transaction program will re-initialize. The MDS_MU that was being sent will be returned to the originator if the error has been 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   

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 the focal point relationships are affected, MS capabilities will take the appropriate recovery action.

Recommended Action   Investigate the cause of the failed send.

Error Message   

Explanation   The system has been unable to allocate resources 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The node has been successfully started.

Recommended Action   No action is required.

Error Message   

Explanation   There is insufficient storage to start the Systems Network Architecture (SNA) switch. The SNA switch was not started.

Recommended Action   Make more storage available to the SNA switch.

Error Message   

Explanation   The node was successfully stopped.

Recommended Action   No action is required.

Error Message   

Explanation   A failure occurred when the system attempted to dynamically load an Advanced Program to Program Communication (APPC) transaction program or a common programming interface for communications (CPI-C) application. The displayed message will indicate a failure and will include the specified sense code.

Recommended Action   Run a trace, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   There is insufficient storage to process a received ACTLU Logical Unit (LU) system services control points (SSCP), and the session will not be started. An ACTLU -ve 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   An ACTLU has been received for a logical unit (LU) that is not defined locally, and the implicit LU definition is not supported. This condition typically indicates a mismatch between the node and the host configuration. The LU system services control points (SSCP) session is not activated, and the ACTLU is rejected with the specified sense code.

Recommended Action   Remove the LU from the host configuration.

Error Message   

Explanation   An ACTLU Logical Unit (LU) has been received from the incorrect system services control points (SSCP). The ACTLU is rejected with sense code 084B0000, The LU activation attempt has failed.\

Recommended Action   If it is necessary for the activation attempt to succeed, the definition must be changed. The LU configuration must be changed to require the correct SSCP identifier or to accept any SSCP identifier.

Error Message   

Explanation   The system is unable to route an intra-node session data. This error usually indicates a race condition when an intra-node session is deactivating.

Recommended Action   No action is required.

Error Message   

Explanation   There is insufficient storage to generate an alert to report the receipt of invalid data. An alert is not generated for this condition.

Recommended Action   Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to the Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The system is unable to route inter-node session data. This error usually indicates a race condition when an inter-node session is deactivating.

Recommended Action   No action is required.

Error Message   

Explanation   The system failed to forward a High Performance Routing (HPR) Network Layer Packet because the Automatic Network Routing (ANR) label could not be matched to an outgoing link. This is usually a normal race condition when an HPR capable link is deactivated. This condition might be caused by an earlier resource shortage (look for log 192). The Rapid Transport Protocol (RTP) connection will attempt to path switch, or might fail.

Recommended Action   Enter the show snasw link command to look for an active HPR-capable link with the specified ANR label. If an active HPR-capable link exists, the problem has been caused by a storage shortage. Decrease the system load (for example, by reducing the number of active sessions), or make more storage available to the Systems Network Architecture (SNA) switch.

Error Message   

Explanation   There is insufficient storage to start 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   

Explanation   There is insufficient storage to forward a High-Performance Routing (HPR) Network Layer Packet (NLP), and the NLP will be discarded. If this error occurs frequently, this condition might cause Rapid Transport Protocol (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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   There is insufficient storage to register a Automatic Network Routing (ANR) label. High-Performance Routing (HPR) traffic using this ANR label will not be routed correctly, and this condition might cause Rapid Transport Protocol (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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The system has received a frame with a badly formed transmission header or an invalid frame (for example, the frame is too small to be a valid Systems Network Architecture (SNA) frame). The invalid frame will be discarded, and an alert is generated.

Recommended Action   No action is required.

Error Message   

Explanation   The system is unable to correlate data-link control (DLC) credit for a multilink trunk group (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 Rapid Transport Protocol (RTP) connection performance occurs, investigate this condition further by querying link stations that are members of MLTGs. If unexpectedly low quantities of data sent over a link, this condition might indicate problems with DLC credit. Run a trace of the signals sent, and run a trace of the DLCs that identifies the affected links. Contact your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

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, and check the link that is connected to the remote node.

Error Message   

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 that this multilink trunk group (MLTG) is connected to.

Error Message   

Explanation   The attach is rejected because the specified conversation type is not supported or defined by the specified transaction program. This condition might indicate a mismatch between the capabilities of the originating transaction program and the destination transaction program. This condition could also indicate a configuration error. The attach will be rejected.

Recommended Action   Ensure that that the conversation type(s) for the specified program and the transaction program are supported and that they match. If the conversation type(s) for the specified program and the transaction program match, or if the conversation types are not specified for the transaction program, then there is a mismatch between the originating and the destination transaction programs.

Error Message   

Explanation   The Systems Network Architecture (SNA) switch detected a protocol error on an Advanced Program to Program Communication (APPC) conversation.The sense codes will include more information.

The following are sense codes:

• 10010000 - Invalid GDS logical length.

• 1008201D - FMH7 or log data mismatch (for example, FMH7 not received when expected, or log data truncated, or CEB not set on FMH7 when expected).

• 10086000 - Received FMH but not FMH7.

• 1008200E - FMH7 format error (log data concatenation not valid).

• 1008200A - FMH7 received with no sense data (sense data is zero).

• 20040000 - An incoming RU was received on a full-duplex conversation that is in send-only state. 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 deactivated.

Recommended Action   Report the protocol error to partner Logical Unit (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   

Explanation   A session is being used by a conversation that has been deactivated because of a protocol error. This condition caused the conversation to fail. The conversation will be terminated by an Advanced Program to Program Communication (APPC) primary_rc of NAP_CONV_FAILURE_NO_RETRY, or by a common programming interface for communications (CPI-C) return_code of CM_RESOURCE_FAILURE_NO_RETRY.

Recommended Action   This log provides information about which TPs and conversations have been affected by a protocol error on a session. Problem specific information about the protocol error is provided by specific exception logs. Use the session identifier to correlate other related logs.

Error Message   

Explanation   A session is being used by a conversation that has been deactivated because of a session outage. This condition caused the conversation to fail. The conversation will be terminated by an Advanced Program to Program Communication (APPC) primary_rc of NAP_CONV_FAILURE_RETRY or by a common programming interface for communications (CPI-C) return_code of CM_RESOURCE_FAILURE_RETRY.

Recommended Action   This log provides information about which TPs and conversations have been affected by a session outage. Other more problem-specific exception logs can provide more information on the reason for the session outage. Use the session identifier to correlate this log with other related logs.

Error Message   

Explanation   The partner TP issued a SEND_ERROR or DEALLOCATE verb specifying a data error. The error state has been generated by the partner TP, and 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   

Explanation   The local TP 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   

Explanation   An APING from the partner Logical Unit (LU) has been processed successfully.

Recommended Action   No action is required.

Error Message   

Explanation   The attach is rejected because the specified conversation duplex type is not supported or defined by the specified transaction program. This condition might indicate a mismatch between 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.

The following are sense codes:

• 10086034 - Half-duplex attach, not supported by TP.

• 08640003 - Full-duplex attach, not supported by TP.

Recommended Action   Check that the conversation duplex type(s) are supported by the specified transaction program, and ensure that the conversation duplex type(s) match the conversation duplex supported and defined by the transaction program. If the conversation duplex type(s) match or if the types are not defined for the transaction program, there is a mismatch between the originating and destination transaction programs.

Error Message   

Explanation   The local Logical Unit (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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The local Logical Unit (LU) has been 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The Systems Network Architecture (SNA) switch detected a mapped conversation protocol error on an Advanced Program to Program Communication (APPC) mapped conversation. The conversation will be terminated, either by an APPC primary_rc of NAP_CONV_FAILURE_NO_RETRY, or a common programming interface for communications (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 Logical Unit (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   

Explanation   The Systems Network Architecture (SNA) switch has received an error data general data stream (GDS) variable on an Advanced Program to Program Communication (APPC) mapped conversation. The conversation will be terminated, either by an APPC primary_rc of NAP_CONV_FAILURE_NO_RETRY or a common programming interface for communications (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 Logical Unit (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   

Explanation   A Logical Unit (LU) received an aping with a data length greater than the maximum allowed. The conversation will be terminated with primary_rc of DEALLOC_ABEND. The Systems Network Architecture (SNA) switch LUs should not receive an aping with a data size greater than the defined maximum.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A Physical Unit (PU) system services control points (SSCP) session has been activated.

Recommended Action   No action is required.

Error Message   

Explanation   A Physical Unit (PU) system services control points (SSCP) session has been deactivated.

Recommended Action   No action is required.

Error Message   

Explanation   There is insufficient storage to send Real Time Monitor (RTM) statistics to the host. The RTM statistics that are 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   There is insufficient storage to start the transaction program and conversation requested by a received attach (FMH5). If other instances of the same transaction program are active, the Systems Network Architecture (SNA) switch will queue the attach and wait for one of the sessions to become available. If the system is unable to allocate an available session, 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   

Explanation   There is insufficient storage to start a new conversation requested by ALLOCATE, MC_ALLOCATE or CMALLC. [MC_]ALLOCATE will fail with primary_rc of NAP_UNEXPECTED_SYSTEM_ERROR, or CMALLC with fail with 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   An Advanced Program to Program Communication (APPC) transaction program or common programming interface for communications (CPI-C) application has ended abnormally with active conversations. This condition might indicate an error in the application. The Systems Network Architecture (SNA) switch will deactivate all sessions that are currently being used by the application.

Recommended Action   Run a trace on the APPC Application Programming Interface (API) or the CPI-C API to see the sequence of verbs causing the problem.

Error Message   

Explanation   The Systems Network Architecture (SNA) switch 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   

Explanation   There is insufficient storage to initiate the session activation requested by ALLOCATE, MC_ALLOCATE or CMALLC. [MC_]ALLOCATE will fail with primary_rc of NAP_ALLOCATION_ERROR and secondary_rc of NAP_ALLOCATION_FAILURE_NO_RETRY. CMALLC will fail with 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   Logical unit (LU) to LU verification failed. The partner LU has sent an incorrect response to the challenge that was sent by a local LU. This condition has been caused by 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 this is 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   

Explanation   There is insufficient storage to deactivate a limited resource session. The limited resource session will not be deactivated (although the session might 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The session limits for a local Logical Unit (LU) and the partner LU have changed. The mode has also changed. The termination count indicates the number of sessions the Systems Network Architecture (SNA) switch will deactivate as a result of the change in session limits.

Recommended Action   No action is required.

Error Message   

Explanation   A Logical Unit (LU) to LU verification protocol error has occurred. This might indicate an interoperability problem. The session will be deactivated with the specified sense code.

Recommended Action   Contact your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The Systems Network Architecture (SNA) switch is unable to activate a new session. This condition occurs if the maximum session limit for the mode or the local Logical Unit (LU) will be exceeded. ALLOCATE, MC_ALLOCATE or CMALLC verbs will fail or hang while waiting for a session to become available.

Recommended Action   Wait for a session to become available or use a different mode.

Error Message   

Explanation   There is insufficient storage to start the transaction program instance requested by TP_STARTED. If other instances of the same transaction program are active, the Systems Network Architecture (SNA) switch will place the TP_STARTED request in a queue and wait for a session to become available. If a session does become available, 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   

Explanation   There is insufficient storage to initiate an automatic session activation. Fewer active sessions will be available on the specified mode, and this situation might cause application delays or failures.

Recommended Action   Decrease the system load (for example, by reducing the number of active sessions), or make more storage available to the Systems Network Architecture (SNA) switch.

Error Message   

Explanation   There is insufficient storage to initiate the 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   A bracket protocol error has occurred. This condition might indicate a problem in the partner Logical Unit (LU).

The following are sense codes:

• 20080000 - Partner LU attempted to start bracket after sending BIS.

• 20030000 - Partner LU attempted to start bracket after local LU had BID for session successfully, or unexpected RTR request received

• 20100000 - Received negative response to BID with sense code 088B0000 from a partner LU who supports parallel sessions, or BIS protocol error. The session will be deactivated with the specified sense code.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   This condition indicates that there is an attach protocol error, and there might be a problem with the partner Logical Unit (LU). The following are sense codes:

• 080F6051 - Attach security protocol violation.

• 10086011 - LUW identifier format error, or LUW identifier not specified, when the synchronize level is syncpt.

• 10086040 - Synchronize level not supported by session, or an already verified state is not accepted from the partner LU.

• 10086031 - PIP not allowed by TP. The session will be deactivated with the specified sense code.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

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. This error indicates a security violation.

Recommended Action   The log will provide information that you can use to locate the attempted security violation.

Error Message   

Explanation   An attach has been rejected because the specified synchrononize level is not supported by the specified transaction program. This condition might indicate a mismatch between the capabilities of the originating transaction program and the destination transaction program. This condition also might indicate a configuration error. The attach will be rejected.

Recommended Action   Check the synchronize level supported by the specified transaction program, and ensure that the level matches the synchronize 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   

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 Systems Network Architecture (SNA) switch. This message should not occur.

Error Message   

Explanation   An attach has been rejected because the specified TP is permanently disabled. This condition only occurs when an application has disabled the transaction program. The attach will be rejected.

Recommended Action   Run a trace. Contact your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The Systems Network Architecture (SNA) switch has been 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   

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   The log will provide information that you can use to locate the security mismatch.

Error Message   

Explanation   A BIS protocol error has occurred. This condition might indicate a problem with the partner Logical Unit (LU). The session will be deactivated with the specified sense code (20100000).

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   An adjacent node has not responded within a reasonable period of time to a request on a control point (CP) to CP session. The Systems Network Architecture (SNA) switch will deactivate the CP to CP sessions with this adjacent node. The CP to CP sessions are deactivated with the sense code 08640002.

Recommended Action   Contact the supplier of the adjacent node.

Error Message   

Explanation   The Rapid Transport Protocol (RTP) connection has connected.

Recommended Action   No action is required.

Error Message   

Explanation   The Rapid Transport Protocol (RTP) connection has disconnected normally

Recommended Action   No action is required.

Error Message   

Explanation   The Rapid Transport Protocol (RTP) connection has disconnected because error sessions that were using the connection have failed.

Recommended Action   Investigate the cause of the error.

Error Message   

Explanation   The Rapid Transport Protocol (RTP) connection has disconnected because error sessions that were using the connection have failed.

Recommended Action   Investigate the cause of the error.

Error Message   

Explanation   The Rapid Transport Protocol (RTP) connection has timed out. The node will attempt to path-switch.

Recommended Action   Investigate the cause of the error.

Error Message   

Explanation   A Rapid Transport Protocol (RTP) connection was dropped by a local link failure. This condition might be caused by operator intervention. The node will attempt to path-switch.

Recommended Action   Investigate the cause of the link failure.

Error Message   

Explanation   The Rapid Transport Protocol (RTP) connection has successfully switched paths.

Recommended Action   No action is required.

Error Message   

Explanation   The Rapid Transport Protocol (RTP) connection has failed to path-switch. The RTP connection will be disconnected.

Recommended Action   Investigate the cause of the error.

Error Message   

Explanation   A route setup Rapid Transport Protocol (RTP) connection RTP process has received a segmented Network Layer Packet (NLP). All NLPs received should contain route setup general data stream (GDS) data that should never be segmented. The NLP will be dropped.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A route setup Rapid Transport Protocol (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   

Explanation   A Rapid Transport Protocol (RTP) connection is path-switching to a much longer path than was started with. Each packet is requiring more room for routing information than was originally planned. Because some packets might have to be segmented, performance across this RTP might degrade.

Recommended Action   If performance degradation occurs, reactivate the failed links and issue the 'PATH_SWITCH' verb.

Error Message   

Explanation   A value for Adaptive Rate Based (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   

Explanation   The Systems Network Architecture (SNA) switch has detected a protocol error in a frame received on an intermediate session. This condition typically indicates a problem on an adjacent node.

The following are sense codes:

• 10010003 - Invalid IPM format.

• 10020000 - RU length error.

• 10030000 - CLEAR request on secondary stage, or CLEAR response on primary stage.

• 20110000 - Sender has overrun pacing window, or PI not set on first RU of window.

• 20110001 - Unexpected IPM 20110002 - PI set on other than first RU in window.

• 20110003 - Invalid pacing response.

• 80070000 - Segment error The intermediate session will be deactivated.

Recommended Action   If more diagnostics are required, run a trace on the specified link. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The system 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   Intermediate Session Routing (ISR) activation has failed. The Systems Network Architecture (SNA) switch is not configured to support any more intermediate sessions. This condition is typically caused by a normal network race condition (since 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 specified sense code (0805000D).

Recommended Action   Run a trace. Contact your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A protocol error has been received in an Intermediate Session Routing (ISR) Berkeley Internet Name Domain (BIND) request. This condition might indicate an interoperability problem. The following are sense codes:

• 08350008 - Secondary-to-primary staging indicator incorrect.

• 0835000C - Primary-to-secondary staging indicator incorrect.

• 10010024 - Unextended non-LU6.2 BIND.

• 10020000 - BIND request/response unit (RU) length error ISR session activation will fail with the specified sense code.

Recommended Action   Report the problem your Cisco technical support representative, and run a trace on the specified link if more diagnostics are required.

Error Message   

Explanation   The system is unable to identify or activate the next hop of an Intermediate Session Routing (ISR) session. The 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 instructions in those logs.

Error Message   

Explanation   Intermediate Session Routing (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 instructions in those logs.

Error Message   

Explanation   A Intermediate Session Routing (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 determine which ISR sessions are affected by a link outage or link error. The preceding logs will give more specific information about the link outage or link error.

Error Message   

Explanation   The system is unable to assign a local form session identifier (LFSID) to the secondary stage of a Intermediate Session Routing (ISR) session. This condition indicates that there is insufficient storage to extend the appropriate LFSID routing table. This condition could also indicate that the LFSID routing 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   The information in this log can be used to determine which ISR sessions are affected by the failure in the LFSID table. Preceding logs give more detail on the reason for the failure.

Error Message   

Explanation   The system is unable to correlate a Berkeley Internet Name Domain (BIND) response that has been received during an Intermediate Session Routing (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   

Explanation   The system failed to correlate an UNBIND request that has been received for an Intermediate Session Routing (ISR) session. +RSP UNBIND is not sent in reply. This error is a normal race condition that is typically caused by UNBIND requests for the same session crossing.

Recommended Action   No action is required.

Error Message   

Explanation   An Intermediate Session Routing (ISR) session has been activated.

Recommended Action   No action is required.

Error Message   

Explanation   An Intermediate Session Routing (ISR) has been deactivated.

Recommended Action   No action is required.

Error Message   

Explanation   The system has received a Intermediate Session Routing (ISR) Berkeley Internet Name Domain (BIND) request with a duplicate fully qualified procedure correlation identifier (FQPCID). The ISR session activation will fail with the specified sense code (083B0002).

Recommended Action   Report the problem your Cisco technical support representative, and run a trace on the specified link if more diagnostics are required.

Error Message   

Explanation   A protocol error has been received in a Intermediate Session Routing (ISR) Berkeley Internet Name Domain (BIND) response. This condition might indicate an interoperability problem. The following are sense codes:

• 08350007 - Control vectors included indicator incorrect.

• 08350008 - Secondary-to-primary staging indicator incorrect.

• 0835000C - Primary-to-secondary staging indicator incorrect.

• 086F0000 - BIND response length inconsistent

• 10010024 - Unextended non-LU6.2 BIND response.

• 10020000 - BIND request/response unit (RU) length error ISR session activation will fail with the specified sense code.

Recommended Action   Report the problem your Cisco technical support representative, and run a trace on the specified link if more diagnostics are required.

Error Message   

Explanation   Intermediate Session Routing (ISR) is unable to support the request/response unit (RU) size that has been requested by a non-negotiable Berkeley Internet Name Domain (BIND) request or response.

The following are sense codes:

• 0835000A - Maximum secondary send RU size is larger than the sizes that are supported by ISR.

• 0835000B - Maximum primary send RU size is larger than the sizes that are supported by ISR. The ISR session activation will fail with the specified sense code.

Recommended Action   Run a trace. Contact your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   Intermediate Session Routing (ISR) is unable to support a fixed receive pacing window requested on a non-negotiable Berkeley Internet Name Domain (BIND) request or response.

The following are sense codes:

• 08350009 - Maximum primary send window size is larger than the sizes that are supported by ISR.

• 0835000D - Maximum secondary send window size is larger than the sizes that are supported by ISR. The ISR session activation will fail with the specified sense code.

Recommended Action   Run a trace. Contact your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   There is insufficient storage to activate an Intermediate Session Routing (ISR) session. The ISR session activation will fail with the specified 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   There is insufficient storage to define a new Logical Unit type 6.2 (LU 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   A fatal error has been detected on a Logical Unit type 6.2 (LU 6.2) session. The session will be deactivated with specified sense code.

Recommended Action   This log provides information about the failed session. More specific information about the fatal error can be found in the preceding exception logs (150, 151, 153, 0154, 155, 156, or 157).

Message   

Explanation   An incoming BIND or +RSP(BIND) has specified duplex support for the remote Logical Unit (LU). This condition is inconsistent with the existing sessions between the partner LUs. The BIND or +RSP(BIND) is rejected.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   There is insufficient storage to activate a Logical Unit type 6.2 (LU6.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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   An abnormal UNBIND request has been received. This condition might indicate a configuration error or a protocol error. The session will fail with the specified sense code.

Recommended Action   If the sense codes indicate a configuration error, check for inconsistencies in the configuration between the local Logical Unit (LU) the partner LU. If the configuration is consistent between the local and partner LUs and the problem persists, contact your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A format error has been received for a Logical Unit type 6.2 (LU 6.2) Berkeley Internet Name Domain (BIND) request. The following are sense codes:

• 0835xxxx - Parameter error at offset xxxx in BIND RU.

• 088C6000 - FQPCID not included in extended BIND.

• 083B0000 - Invalid FQPCID format Session activation will fail with specified sense code.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The system has received a format error in a Logical Unit type 6.2 (LU6.2) Berkeley Internet Name Domain (BIND) response.The following are sense codes:

• 0835xxxx - Parameter error at offset xxxx in Berkeley Internet Name Domain (BIND) request/response unit (RU) session activation will fail with specified sense code.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A Logical Unit (LU) mode session limit has been exceeded. This error should not occur because the session limits are negotiated with a CNOS exchange. The CNOS exchange occurs before the sessions are activated. However, this log can also be caused by a normal race condition when the session limits are reset, or when this node was restarted after having previously had sessions with this partner LU. The session activation will fail with the specified sense code.

Recommended Action   If this condition recurs, check the session limits and active session counts on the specified local LU and partner LU.

Error Message   

Explanation   A Berkeley Internet Name Domain (BIND) race with single session partner Logical Unit (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 specified sense code.

Recommended Action   No action is required.

Error Message   

Explanation   The system has detected consistency errors in a received Berkeley Internet Name Domain (BIND) request. This condition might indicate an interoperability problem.

The following are sense codes:

• 0835xxxx - Parameter error at offset xxxx in BIND RU.

• 080F6051 - Security error Session activation will fail with specified sense code.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The system has detected consistency errors in a received Berkeley Internet Name Domain (BIND) response. This condition might indicate an interoperability problem. The following are sense codes:

• 0835xxxx - Parameter error at offset xxxx in BIND RU.

• 080F6051 - Security error session will be deactivated with specified sense code.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A format error has been received in a UNBIND request. This condition might indicate an interoperability problem. The following are sense codes:

• 0835xxxx - Parameter error at offset xxxx in UNBIND RU.

• 0895xxyy - Format error in control vector, where xx is key of control vector, and yy is offset into control vector of byte in error.

• 10020000 - RU length error None (session will still be deactivated).

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   There is insufficient storage to activate a Logical Unit (LU) system services control points (SSCP) session. The ACTLU will be rejected with 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   There is insufficient storage to reassemble a Berkeley Internet Name Domain (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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   A partner Logical Unit (LU) name on a received Berkeley Internet Name Domain (BIND) request is badly formed. The session activation will fail with the specified sense code.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The mode name on a Berkeley Internet Name Domain (BIND) request is unrecognized. The session activation will fail with the specified sense code.

Recommended Action   Modify the partner Logical Unit (LU) configuration so that the LU does not attempt to use the unrecognized mode.

Error Message   

Explanation   The system is unable to activate the session to a single session partner Logical Unit (LU). This condition occurs when there is already an active session on another mode, and might indicate a conflict between two or more Advanced Program to Program Communication (APPC) transaction programs or common programming interface for communications (CPI-C) applications for the same dependent Logical Unit type 6.2 (LU6.2). The session activation will fail with specified sense code, and might cause ALLOCATE, MC_ALLOCATE, or CMALLC requests to fail.

Recommended Action   Run a trace. Contact your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A Logical Unit 6.2 (LU6.2) session has been activated.

Recommended Action   No action is required.

Error Message   

Explanation   A Logical Unit 6.2 (LU6.2) session has been deactivated.

Recommended Action   No action is required.

Error Message   

Explanation   A fully qualified procedure correlation identifier (FQPCID) collision has occurred. The FQPCID that has been specified on a received Berkeley Internet Name Domain (BIND) request matches the FQCPID that is being used for an existing active session. A collision might have occurred in the hashing algorithm used to generate the FQPCID. This condition might also occur if there is a problem in the node generating the FQPCID. The session activation will fail with the specified sense code.

Recommended Action   If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A session identifier collision has occurred. The session identifier that has been specified on a received Berkeley Internet Name Domain (BIND) request matches the session identifier for an existing active session. The session activation will fail with specified sense code.

Recommended Action   If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   A Logical Unit (LU) system services control points (SSCP) session has been activated.

Recommended Action   No action is required.

Error Message   

Explanation   A Logical Unit (LU) system services control points (SSCP) session has been deactivated.

Recommended Action   No action is required.

Error Message   

Explanation   A Logical Unit (LU) to LU verification protocol mismatch has occurred. The partner LU has requested that the basic protocol is used when the local LU runs only the enhanced protocol with the partner LU. The local LU can be configured to run only the enhanced protocol with the partner LU, or the local LU might be configured to run either protocol with the partner LU. (The local LU must determine that the partner LU can run the enhanced protocol.) This condition is caused by a mismatch in configuration, 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 mismatch, reconfigure the verification protocol so that the partner LU uses the same protocol at the partner LU location. For a migration problem, upgrade the software at the partner LU location. For a security attack, investigate the security hole.

Error Message   

Explanation   A Logical Unit (LU) to LU verification has failed. The partner LU has sent an incorrect response to a challenge sent by a local LU. This is either a mismatch in configuration or a security attack. The session activation will fail.

Recommended Action   Check the identity of the partner LU. If there is a mismatch in configuration, reconfigure the password either at the local LU, at the partner LU, or at both LUs so that both LUs have the same password.

Error Message   

Explanation   There has been duplicate random data received. A list is kept of all the random data sent as challenges by the local Logical Unit (LU). Receiving duplicate random data from a partner LU should be a rare event. This condition might indicate 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. Ensure that the random number generators are operating correctly and that they are not generating matching data. If this condition recurs, investigate the recurrences as security attacks.

Error Message   

Explanation   A BIND(-RSP) has been received in response to a Berkeley Internet Name Domain (BIND) request. This condition might indicate a configuration error, or a protocol error.

Common sense codes that typically indicate a configuration error or a normal race condition include the following:

• 0805xxxx - The session could not be activated as session activation limits have been reached.

• 08060014 - The partner LU is not known.

• 0806xxxx - The BIND specified a resource that is not known.

• 080Fxxxx - Security authorization failed.

• 0821xxxx - The BIND supplied an invalid session parameter.

• 0835xxxx - Parameter error in BIND RU at offset xxxx.

Other sense codes include:

• 0812xxxx - Session activation failed because of a resource shortage at the remote node.

• 083Bxxxx - Invalid PCID in BIND RU.

• 0852xxxx - Duplicate session activation request.

• 0861xxxx - Invalid COS name in BIND RU 088Cxxxx: control vector or subfield missing from BIND RU.

• 0895xxxx - BIND RU contained a control vector that was in error.

• 0896xxxx - BIND RU contained a control vector that was too long. Session activation will fail with the specified sense code.

Recommended Action   If the sense code indicates a configuration error, look for inconsistencies in the configurations of the local LU and the partner LU. If the configuration is consistent and the problem recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered

Explanation   The system is unable to correlate the received Berkeley Internet Name Domain (BIND) response. This error is probably caused by a normal race condition. If a BIND request is received that is followed immediately by an UNBIND request and then by another BIND request using the same local form session identifier (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   

Explanation   The system is unable to correlate the received INIT-SELF response or NOTIFY request. This is a normal race condition caused by the session being deactivated before the INIT-SELF response has arrived. The request or response is discarded.

Recommended Action   No action is required.

Error Message   

Explanation   The system is unable to correlate a received UNBIND request. This is a normal race condition caused by UNBIND requests crossing. None (will send a +ve response to UNBIND).

Recommended Action   No action is required.

Error Message   

Explanation   An ACTLU has been received when a Logical Unit (LU) is already "active." The ACTLU will be rejected with specified sense code.

Recommended Action   Run a trace on the link station corresponding to the specified Physical Unit (PU) name. Contact the host support with the details of the problem.

Error Message   

Explanation   The system is unable to activate a new session because it would exceed the Logical Unit (LU) mode session limits. This problem is a normal race condition and should occur infrequently. The session activation will fail with specified sense code and might cause ALLOCATE, MC_ALLOCATE, or CMALLC requests to fail.

Recommended Action   No action is required.

Error Message   

Explanation   A Logical Unit 6.2 (LU6.2) session has been activated.

Recommended Action   No action is required.

Error Message   

Explanation   A Logical Unit 6.2 (LU6.2) session has been deactivated.

Recommended Action   No action is required.

Error Message   

Explanation   An ACTLU has been received for a logical unit (LU) from the wrong system services control points (SSCP). The ACTLU is rejected with sense code 084B0000. The LU activation attempt fails.

Recommended Action   If it is necessary for the activation attempt to succeed, the definition must be changed. The LU configuration must be changed to require the correct SSCP identifier or to accept any SSCP identifier.

Error Message   

Explanation   The Logical Unit (LU)-mode session limit has been exceeded because of a Berkeley Internet Name Domain (BIND) race. This is normal race condition caused by both the local Logical Unit (LU) and partner LU attempting 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 specified sense code.

Recommended Action   No action is required.

Error Message   

Explanation   A Logical Unit (LU) system services control points (SSCP) session has been activated.

Recommended Action   No action is required.

Error Message   

Explanation   A Logical Unit (LU) system services control points (SSCP) session was deactivated.

Recommended Action   No action is required.

Error Message   

Explanation   An UNBIND request has been received in response to a Berkeley Internet Name Domain (BIND) request. This condition might indicate a configuration error or a protocol error. The following are common sense codes that typically indicate a configuration error or a normal race condition include the following:

• 0805xxxx - The session could not be activated as session activation limits have been reached.

• 08060014 - The partner LU is not known.

• 0806xxxx - The BIND specified a resource that is not known.

• 080Fxxxx - Security authorization failed.

• 0821xxxx - The BIND supplied an invalid session parameter.

• 0835xxxx - Parameter error in BIND RU at offset xxxx Other sense codes include.

• 0812xxxx - Session activation failed because of a resource shortage at the remote node.

• 083Bxxxx -Invalid PCID in BIND RU.

• 0852xxxx - Duplicate session activation request.

• 0861xxxx - Invalid COS name in BIND RU.

• 088Cxxxx - Control vector or subfield missing from BIND RU.

• 0895xxxx - BIND RU contained a control vector that was in error.

• 0896xxxx - BIND RU contained a control vector that was too long. Session activation will fail with the specified sense code.

Recommended Action   If the sense codes indicate a configuration error, check for inconsistencies in the configuration between the local Logical Unit (LU) the partner LU. If the configuration is consistent between the local and partner LUs and the problem persists, contact your Cisco technical support representative, and provide the representative with the gathered information.

Recommended Action   information.

Error Message   

Explanation   A Berkeley Internet Name Domain (BIND) response has been received that accepted session compression, but the BIND response did not specify the compression levels required. This condition occurred 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, the compression will be used in both directions even though it might have been configured for one direction only.

Recommended Action   No action is required.

Error Message   

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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The network node server is not required. This condition is logged when a back-level APPN network node (one that does not support function set 1015) attempts to activate a control point (CP) to CP sessions with the Systems Network Architecture (SNA) switch when it already has a network node server. The CP to 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 the sever are deactivated and at least one link is restarted.

Recommended Action   No action is required.

Error Message   

Explanation   A control point (CP) capabilities exchange failed because of a contention loser CP to CP session failure. The contention winner CP to CP session will be deactivated. The Systems Network Architecture (SNA) switch will attempt to reactivate CP to CP sessions with the adjacent CP.

Recommended Action   The information in this log indicates that a CP to CP session failed. Other logs will give more specific information about the session failure (for example, insufficient resources or link failure).

Error Message   

Explanation   There is insufficient storage to generate 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   The control point (CP) capabilities exchange has failed because of a protocol error. This condition might indicate an interoperability problem.

The following are sense codes:

• 08060030 - CP capabilities requested by unknown CP.

• 08210002 - CP capabilities requested on other than CPSVCMG mode.

• 08150007 - CP capabilities requested when CP-CP session already established.

• 08B60000 - CP-CP sessions not supported by adjacent node.

• 08090039 - CP transaction error 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 error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The control point (CP) capabilities exchange has failed because of a badly formatted CP CAPS general data stream (GDS) variable.

The following are sense codes:

• 10101000 - CP capabilities length error.

• 10101002 - Unexpected GDS identifier (not CP capabilities) 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 error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   An adjacent control point (CP) has been contacted.

Recommended Action   No action is required.

Error Message   

Explanation   Control point (CP) to CP sessions have been successfully established with the adjacent node.

Recommended Action   No action is required.

Error Message   

Explanation   The system is retrying a control point (CP) to control point session after an error has occurred.

Recommended Action   No action is required.

Error Message   

Explanation   A control point (CP) capabilities exchange failed because of a contention winner CP to CP session failure. The contention loser CP to CP session will be deactivated. The Systems Network Architecture (SNA) switch will attempt to reactivate the CP to CP sessions with the adjacent CP.

Recommended Action   The information in this log indicates that a CP to CP session failed. Other logs will give more specific information about the session failure (for example, insufficient resources or link failure).

Error Message   

Explanation   Control point (CP) to CP sessions have been established between two network nodes in different networks. The CP to CP sessions will be deactivated with the specified sense code.

Recommended Action   No action is required.

Error Message   

Explanation   Control point to CP sessions to the adjacent node have been deactivated.

Recommended Action   No action is required.

Error Message   

Explanation   The Branch Network node has insufficient resources to register an Logical Unit (LU) on an adjacent low-entry networking (LEN) node. The LU resource might not be put into the directory and might 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 Systems Network Architecture (SNA) switch.

Error Message   

Explanation   A session pacing error has occurred. This condition might indicate an interoperability problem. The session will be deactivated with the specified sense code. The following are sense codes:

• 20110000 - sender has overrun pacing window, or PI not set on the first request/response unit (RU) of window

• 20110001 - unexpected IPM

• 20110002 - PI set on other than first RU in window

• 20110003 - invalid pacing response

• 10010003 - invalid IPM format

Recommended Action   Use the information on the session deactivated problem log (271) to identify the local LU and partner LU. If more diagnostics are required, run a trace on the specified link. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The system has received a session segmentation error. This condition might indicate an interoperability problem. The following are sense codes:

• 80070000 - Segmenting error.

• 80070001 - Segmentation not supported on this link. The session will be deactivated with the specified sense code.

Recommended Action   Use information on the session deactivated problem log (271) to identify the local LU and partner LU. If more diagnostics are required, run a trace on the specified link. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The problem indicates a request/response unit (RU) length error. This condition might indicate an interoperability problem. The sense code is as follows: 10020000 - RU length error. The session will be deactivated with the specified sense code.

Recommended Action   For a Logical Unit 6.2 (LU6.2) session, use information on the session deactivated problem log (271) to identify the local Logical Unit (LU) and partner LU. If more diagnostics are required, run a trace on the specified link. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message   

Explanation   The Buffer Manager Monitor could not allocate the necessary resources. The Buffer Manager will fail to operate and detect congestion or relief from congestion, possibly leading to the node locking up.

Recommended Action   Shutdown and restart the node.

Error Message   

Explanation   There is insufficient storage to create a new buffer pool. Activation of some resource (for example, session or LS) will fail. See other logs.

Recommended Action   Investigate the memory shortage and the system load.

Error Message   

Explanation   This condition indicates insufficient buffers to create a new buffer pool. Activation of some resource (for example, session or LS) will fail. See other logs.

Recommended Action   Investigate the buffer shortage and the system load.

Error Message   

Explanation   The Buffer Manager Monitor has detected critical buffer congestion. The Systems Network Architecture (SNA) switch will throttle back session traffic by withholding pacing responses or by 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. The condition should clear itself automatically.

Recommended Action   If this condition occurs frequently, the node might be routing more sessions than it can efficiently handle with the available buffer storage. Reduce the number of sessions through the router.

Error Message   

Explanation   The buffer congestion was relieved. The Systems Network Architecture (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   

Explanation   The Buffer Manager detected critical buffer congestion while attempting to relieve a previous congestion condition. The Systems Network Architecture (SNA) switch will throttle back session traffic by withholding pacing responses or by 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. The condition should clear itself automatically.

Recommended Action   If this condition occurs frequently, it might indicate that the node is routing more sessions than the node can handle efficiently with the available buffer storage. Reduce the number of sessions through the router.

Error Message   

Explanation   There is insufficient storage to request posting. The component that is using the Buffer Manager might fail to operate or lock up. See other logs for effects.

Recommended Action   Investigate the memory shortage and the system load.

Error Message   

Explanation   The space for implicit aliases has wrapped. There is a very slight possibility of duplicate aliases.

Recommended Action   Shut down and restart the system to avoid any conflict.

Error Message   

Explanation   A software error has caused the system to detect a bad internal state. The system could potentially lose functionality. Refer to other problem logs for the actual effect.

Recommended Action   Shutdown and restart the system.

Error Message   

Explanation   A trace record could not be written to one of the cyclic trace buffers. The error was larger than the available space in the buffer, and the buffer will be cleared.

Recommended Action   Increase the size of the relevant cyclic trace buffer or disable the tracing (if diagnostics are not currently necessary).

Error Message   

Explanation   A cyclic trace buffer could not be resized because of insufficient memory. The previously allocated buffer will continue to be used.

Recommended Action   Reconfigure a smaller buffer size for the specified buffer type.

Error Message   

Explanation   A Class of Service (CoS) name 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 no mode-to-CoS mapping tables exist at the origin node or its network node server, do not use the unrecognised CoS.

Error Message   

Explanation   No suitable Transmission Group (TG) could be found from the origin end node to the backbone network for the Class of Service (CoS) that is specified for a session activation. This condition might 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   First 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 CoS, or reconfigure the network to ensure there is a usable route 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   

Explanation   No suitable Transmission Group (TG) could be found from the backbone network to the destination end node for the Class of Service (CoS) specified for a session activation. This condition might be caused by a temporary link failure between the destination node and a network node. A session activation will fail with the specified sense code.

Recommended Action   First 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 CoS, or reconfigure the network to ensure there is a usable route from the destination node to the backbone network (for example, by defining or activating another link from the destination node to a network node).

Error Message   

Explanation   No suitable Transmission Group (TG) could be found for a session activation to an adjacent node for the given Class of Service (CoS). This might be caused by a link failure. A 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 there is a usable link between this node and the specified adjacent node.

Error Message   

Explanation   The Route Selection Control Vector (RSCV) generated for this route was more than 256 bytes long, and it must be less than 256 bytes long. The session activation will fail with the specified sense code.

Recommended Action   Reconfigure the network to ensure that there is a short enough route between the origin and destination nodes.

Error Message   

Explanation   There is insufficient memory available to send an alert, and the host will not see an alert. The number below identifies the alert:

• 1 - CPDB001

• 2 - CPDB002

• 3 - CPDB003

• 4,6 - CPDB004

• 5,7 - CPDB005 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 Systems Network Architecture (SNA) switch.

Posted: Fri Jun 16 11:53:55 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.