-
Cisco IOS Release 12.0 System Message Guide
-
About the Cisco IOS Software Documentation
-
System Error Messages Overview
-
AAAA through APPN
-
ARAP through C1600
-
C2600 through CT3
-
DBCONN through FILESYS
-
FPGA through IPC_RSP_CBUS
-
IPFAST through LPD
-
M32X through NHRP
-
NIC100 through RTT
-
S4T68360 through SWITCH
-
SYS through TI1570
-
TIB through XCPA
-
CMCC-ADAPTER through CMCC-IPC_DRVR
-
CMCC-LOADER through CMCC-XCPA
-
System Failure Error Messages
-
Table Of Contents
System Error Messages
AAAA Messages
TACACS+ authentication, authorization, and accounting security accounting error messages
Error Message%AAAA-3-BADARG : [atalk_address]talk_address]AA: bad argument ([hex])
Explanation NVGEN was attempted on a non-existent AAA command.
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%AAAA-3-BADLIST : [atalk_address]talk_address]AA: bad [chars] list [chars]
Explanation One of the AAA methods does not seem to have a list associated with it.
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%AAAA-4-BADMETHNAME : Bad [chars] method-list name [chars] (this is only a warning)
Explanation A method-list name should not be the same as a method-name. Choose a different name for the method list.
Recommended Action Choose a different method-list name (that is not a method-name).
Error Message%AAAA-3-BADSTATE :
[atalk_address]talk_address]AA: Bad state for [chars] list name ([dec])Explanation An AAA method list is neither default nor named.
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%AAAA-3-BADSTR : Bad accounting data: [chars]
Explanation During AAA accounting operations, the internal database of accounting information for a user was found to be corrupt. In all cases, this indicates an internal software error, and that accounting information for a particular user session has been lost.
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%AAAA-3-DROPACCT : accounting record dropped: [chars]-[chars] [chars] [chars]
Explanation An attempt to send an accounting record to a server failed.
Recommended Action Check that the server (TACACS+ or RADIUS) is operational. Next, check the NAS is configured properly. Finally, check that the NAS can communicate with the server.
Error Message%AAAA-3-ILLEGALNAME : Illegal [chars] method-list name [chars] rejected
Explanation A method-list name should not be the same as a method-name. Choose a different name for the method list.
Recommended Action Choose a different method-list name (that is not a method-name).
Error Message%AAAA-3-INVALIDLIST : [atalk_address]talk_address]AA: invalid [chars] list [dec]
Explanation One of the AAA method lists has inconsistent settings.
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%AAAA-3-INVSTATE : [chars] AUTHOR/[chars]: Internal state is invalid: astruct 0x[hex] ustruct 0x[hex]
Explanation One of the two mentioned data-structures is not set, but is needed. 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%AAAA-3-LOSTTIMER : Lost periodic accounting timer for user [chars]. Restarting timer...
Explanation The periodic timer associated with this ustruct has been lost.
Recommended Action Re-allocate and restart a timer.
Error Message%AAAA-3-MKTIMERFAIL : Failed to create periodic accounting timer for user [chars]. This user may not generate periodic accounting records
Explanation Failed to malloc a timer struct for periodic accounting.
Recommended Action Free up some memory and have the user re-authenticate.
Error Message%AAAA-3-NOFREELISTS : [atalk_address]talk_address]AA: No free [chars] lists for [chars]
Explanation You have reached the maximum number of possible authentication lists for this method.
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%AAAA-3-NOLIST : [chars]: no method list-name
Explanation An internal software error 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%AAAA-3-NULUSR : accounting for null user
Explanation This message indicates an internal software error. During shutdown of a line or interface, the system tried to send accounting information via AAA, but could not find the user to which the accounting information belonged. The most likely reason for this error is trying to do accounting twice for the same event. This error message can occur without any loss of accounting information.
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%AAAA-3-OVERWRITE : Overwrote internal buffer space [chars]
Explanation An internal software error 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%AAAA-3-PERIODICFORKFAIL : Failed to start periodic accounting process. Periodic accounting records may not be sent
Explanation Failed to create the periodic accounting process.
Recommended Action Free up some memory.
Error Message%AAAA-3-PERNOTIMER : AAA/ACCT/TIMER: Periodic update but no timer
Explanation An attempt was made to free a timer, and the method is PERIODIC, but no timer seems to exist.
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%AAAA-3-RELOGIN : sanity check in re-login [chars] to [chars]
Explanation A software or hardware error 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%AAAA-3-STRCREATE : str_create overwrote its internal buffer
Explanation An internal buffer used to assemble a string was exceeded, possibly corrupting other memory.
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%AAAA-3-SUBTYPE : Bad Subtype [dec] for [chars] ([dec])
Explanation An internal software error 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%AAAA-3-TIMERNOPER : AAA/ACCT/TIMER: No periodic update but timer set
Explanation An attempt was made to free a timer, but the update method is not PERIODIC, so no timer should exist.
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.
ADJ Error Messages
Adjacency subsystem error messages
Error Message%ADJ-3-ADJDELMSG : Invalid delete message length [dec]
Explanation An internal software error 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%ADJ-3-ADJFIBIDB : Adjacency update with invalid fibidb([dec])
Explanation An internal software error 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%ADJ-3-NULLFIBHWIDB : Add [chars] with null cef hwidb([chars])
Explanation An internal software error 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%ADJ-3-NULLFIBIDB : Add [chars] with null cef idb
Explanation An internal software error 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.
AIP Error Messages
ATM Interface Processor error messages
Error Message%AIP-3-AIPFAILSETUPVC : [chars] Failed to setup vc [dec] (Cause: [chars])
Explanation The AIP driver failed to set up a virtual circuit.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AIP-3-AIPFAILSETUPVCAVG : Interface [chars], Failed to setup vc [dec] (Cause: [chars]) Expected range [[dec] .. [dec]]Kbps for AIP Average Rate Metering. Average Rate=Peak Rate= [dec] Kbps turns Average Rate Metering OFF
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
ALC Error Messages
ATM Line Card error messages
Error Message%ALC-3-CMDERR : Interface ([chars]): [chars] IPC command fails (cause: 0x[hex])
Explanation The ATM RP driver experienced an IPC command 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%ALC-3-EVENT : Interface ([chars]): unknown IPC event ([int]) from linecard
Explanation The ATM RP driver received an unknown event from the linecard.
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%ALC-3-INIT : ATM driver ([int]/[int]) initialization [chars]
Explanation The ATM RP driver experienced a software initialization 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%ALC-4-NULLCEFIDB : Interface ([chars])
Explanation This interface does not have CEF IDB by mistake.
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%ALC-4-UNSUP : Interface ([chars]): unsupported feature: [chars]
Explanation This feature is not supported by GSR ATM RP.
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%ALC-3-VCADJ : Per-VC adjacency error: VC:[int] [chars]
Explanation The ATM RP driver experienced a per-VC adjacency software 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%ALC-3-VCENCTYPE : VC:[int] unknown VC encapsulation type ([int])
Explanation The ATM RP driver experienced an unknown VC encapsulation software 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.
ALIGN Error Messages
The ALIGN facility controls a feature in reduced instruction-set computer (RISC)-processor-based Cisco products that identifies software in need of memory use optimization.
Error Message%ALIGN-3-CORRECT : Alignment correction made at 0x[hex] reading/writing 0x[hex]
Explanation A software component within the router needs memory optimization.
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%ALIGN-1-FATAL : [chars]
Explanation An alignment error has occurred. Alignment errors are caused by misaligned reads and writes. For example, a two-byte read of a memory address that is not a multiple of two bytes is an alignment error. Alignment errors are caused by internal software failures. The system will be reloaded, often with a bus error.
Recommended Action This message is caused by a software failure. To take advantage of recent fixes, upgrade your system to the latest Cisco IOS software release in your release train. If this message recurs, copy the error message text exactly as it appears on the console or in the system log, enter the show log, show alignment and show tech-support commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALIGN-3-FULL : Alignment log is full - no new entries will be recorded
Explanation The router identified more software components in need of memory optimization than it can record.
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%ALIGN-3-READEXCEPTION : Warning : read access failed at [chars], still continuing
Explanation A Cisco LS1010 read access failure did not cause a reload. This is a result of either a bad resister value in ASP version 3.3 or less, or a problem in the hardware.
Recommended Action If the ASP version is 3.3 or higher, report it to your technical support representative.
Error Message%ALIGN-3-SPURIOUS : Spurious memory access made at 0x[hex] reading 0x[hex]
Explanation An error was identified (and temporarily corrected) within a software component in the router.
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%ALIGN-3-TRACE : -Traceback= [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation This message indicates where the previous ALIGN error 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.
ALPS Error Messages
Airline Protocol Support error messages
Error Message%ALPS-3-ALPSFAIL : ALPS: Assertion failed: [chars]
Explanation An internal software error 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%ALPS-5-ASCU_DOWN : ASCU [hex] on interface [chars] is down
Explanation An ALPS ASCU has changed from up to down.
Recommended Action No action is required.
Error Message%ALPS-6-ASCU_IF_STUCK : Polling for ASCU [hex] on interface [chars] is stalled
Explanation The polling mechanism for an ALPS interface has become stuck.
Recommended Action No action is required.
Error Message%ALPS-5-ASCU_UP : ASCU [hex] on interface [chars] is up
Explanation An ALPS ASCU has changed from down to up.
Recommended Action No action is required.
Error Message%ALPS-6-CIRCUIT_BUSY_END : Circuit [chars] has exited a congested state
Explanation An ALPS circuit is no longer experiencing congestion.
Recommended Action No action is required.
Error Message%ALPS-6-CIRCUIT_BUSY_START : Circuit [chars] has entered a congested state
Explanation An ALPS circuit is experiencing congestion.
Recommended Action No action is required.
Error Message%ALPS-5-CIRCUIT_CLOSED : Circuit [chars] changed state to closed
Explanation An ALPS circuit has changed from open to closed.
Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_DROPS_CKT_DISABLED : Threshold exceeded for circuit disabled drops for circuit [chars]
Explanation The number of ALPS circuit drops that are caused by a circuit being disabled exceeds the ALPS circuit threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_DROPS_INVALID_ASCU : Threshold exceeded for invalid ASCU drops for circuit [chars]
Explanation The number of ALPS circuit drops that are caused by an invalid ASCU identifier exceeds the ALPS circuit threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_DROPS_LIFETIME_EXPIRED : Threshold exceeded for lifetime timer expiration drops for circuit [chars]
Explanation The number of ALPS circuit drops that are caused by lifetime timer expiration exceeds the ALPS circuit threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_DROPS_QUEUE_OVERFLOW : Threshold exceeded for queue overflow drops for circuit [chars]
Explanation The number of ALPS circuit drops that are caused by queue overflow exceeds the ALPS circuit threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_DROPS_VC_RESET : Threshold exceeded for X.25 VC Reset drops for circuit [chars]
Explanation The number of ALPS circuit drops that are caused by an X.25 VC reset exceeds the ALPS circuit threshold value.
Recommended Action No action is required.
Error Message%ALPS-5-CIRCUIT_OPEN : Circuit [chars] changed state to open
Explanation An ALPS circuit has changed from closed to open.
Recommended Action No action is required.
Error Message%ALPS-6-CIRCUIT_OPEN_FAILED : Circuit [chars] received a Circuit Open Failed message
Explanation An ALPS circuit sent a Circuit Open Request message and received a Circuit Open Failed message as a reply.
Recommended Action No action is required.
Error Message%ALPS-6-PEER_BUSY_END : Peer connection to [int] has exited a congested state
Explanation An ALPS peer connection is no longer experiencing congestion.
Recommended Action No action is required.
Error Message%ALPS-6-PEER_BUSY_START : Peer connection to [int] has entered a congested state
Explanation An ALPS peer connection is experiencing congestion.
Recommended Action No action is required.
Error Message%ALPS-5-PEER_CLOSED : Peer connection to [int] changed state to closed
Explanation An ALPS peer connection is now closed.
Recommended Action No action is required.
Error Message%ALPS-5-PEER_CLOSED_DYNAMIC_INACTIVITY : Peer connection to [int] is closed due to inactivity
Explanation An ALPS peer connection is now closed because of inactivity.
Recommended Action No action is required.
Error Message%ALPS-7-PEER_DROPS_MAX_SIZE_EXCEEDED : Threshold exceeded for maximum size exceeded drops for peer [int]
Explanation The number of ALPS peer drops that are caused by the maximum size being exceeded exceeds the ALPS peer threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-PEER_DROPS_PEER_UNREACHABLE : Threshold exceeded for peer unreachable peer drops for peer [int]
Explanation The number of ALPS peer drops that are caused by a peer unreachable condition exceeds the ALPS peer threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-PEER_DROPS_QUEUE_OVERFLOW : Threshold exceeded for TCP Queue overflow peer drops for peer [int]
Explanation The number of ALPS peer drops that are caused by queue overflow exceeds the ALPS peer threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-PEER_DROPS_VERSION_MISMATCH : Threshold exceeded for version mismatch peer drops for peer [int]
Explanation The number of ALPS peer drops that are caused by a version mismatch exceeds the ALPS peer threshold value.
Recommended Action No action is required.
Error Message%ALPS-5-PEER_OPEN : Peer connection to [int] changed state to open
Explanation An ALPS peer connection is now open.
Recommended Action No action is required.
AMDP2_FE Error Messages
AMDP2 Ethernet and Fast Ethernet error messages
Error Message%AMDP2_FE-4-BABBLE : [chars] transmit problem, CSR0=[hex]
Explanation The transmitter has been on the channel longer than the time taken to transmit the largest frame.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-1-DISCOVER : Only found [dec] interfaces on bay [dec], shutting down bay
Explanation The software could not identify the interface card.
Recommended Action Power down, reseat the interface card, and reboot. If the message recurs, call your technical support representative for assistance.
Error Message%AMDP2_FE-5-EXCESSCOLL : [chars] TDR=[dec], TRC=[dec]
Explanation The Ethernet/Fast Ethernet interface is experiencing multiple collisions. This may occur under heavy loads.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-1-INITFAIL : [chars] CSR[dec]=0x[hex]
Explanation The software failed to initialize/restart an Ethernet/Fast Ethernet interface.
Recommended Action Clear the interface. If the message recurs, call your technical support representative for assistance.
Error Message%AMDP2_FE-5-LATECOLL : [chars] transmit error
Explanation Late collisions occurred on the Ethernet/Fast Ethernet interface.
Recommended Action If the interface is Fast Ethernet, verify that both peers are in the same duplex mode. For regular Ethernet, the system should recover. No action is required.
Error Message%AMDP2_FE-5-LOSTCARR : [chars] cable/transceiver problem?
Explanation The cable and/or transceiver is not connected.
Recommended Action Connect the cable and/or transceiver.
Error Message%AMDP2_FE-1-MEMERR : [chars] CSR[dec]=0x[hex]
Explanation The interface could not access system resources for a long time. This problem may occur under very heavy loads.
Recommended Action The system should recover. No action is required. If the message recurs, call your technical support representative for assistance.
Error Message%AMDP2_FE-2-NOISL : [chars] hardware does not support ISL
Explanation The interface cannot be configured as an ISL trunk.
Recommended Action Check the configuration.
Error Message%AMDP2_FE-1-NOMII : [chars] MII transceiver not connected
Explanation The MII transceiver was disconnected while the MII port was selected.
Recommended Action Connect the transceiver and enter the shutdown and no shutdown commands for the interface in the configuration menu.
Error Message%AMDP2_FE-3-NOTAMDP2 : Slot [dec] device ID seen as [hex], expected [hex]
Explanation The software could not recognize the interface chips.
Recommended Action Power down, reseat the interface card, and reboot. If the message recurs, call your technical support representative for assistance.
Error Message%AMDP2_FE-1-NOTSUPPORTED : 2FE PA not supported on NPE100, shutting down bay
Explanation The 2FE port adapter is not supported on a Cisco 7200 router with NPE100.
Recommended Action NPE150 or better is needed for a 2FE PA.
Error Message%AMDP2_FE-3-OWNERR : [chars] packet buffer, pak=0x[hex]
Explanation The software detected an error in descriptor ownership.
Recommended Action Try a later version of the software. If the message recurs, call your technical support representative for assistance.
Error Message%AMDP2_FE-3-SPURIDON : [chars] spurious chip init, CSR[dec]=0x[hex]
Explanation An illegal condition indicating initialization done has occurred.
Recommended Action Clear the interface. If this message recurs, call your technical support representative for assistance.
Error Message%AMDP2_FE-3-UNDERFLO : [chars] transmit error
Explanation While transmitting a frame, the controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
APPN Error Messages
Advanced Peer-to-Peer Networking error messages
Error Message%APPN-3-APPN_ASSERT : APPN_ASSERT
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-Assert : Assertion failed in [chars] at line [dec]
Explanation A hardware or software error 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%APPN-3-BadIPSreceived : RTP received unrecognized IPS
Explanation A system component received an internal interprocess signal that it does not recognize or cannot process.
Recommended Action There is an internal code 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%APPN-3-BADJ02 : BADJ02: Pool [hex] is neither Limited nor Permanent
Explanation A hardware or software error 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%APPN-3-BadMemory : Mfreeing bad storage: addr = [hex], header = [hex], size = [dec]
Explanation A hardware or software error 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%APPN-3-BadQCase : RTP is getting messages for the queues can't be processed
Explanation A hardware or software error 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%APPN-3-BDLAY01 : BDLAY01: Delay ipm while previous delay ipm still pending; pool_p=[hex]
Explanation A request to send an IPM (SNA pacing message) after an appropriate delay has detected a serious problem.
Recommended Action The request is used to schedule the sending of an IPM when the overall status of the buffers in the node reaches a certain value. The request is invalid because the specified buffer pool has already been scheduled. There is an internal code problem with the system. 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%APPN-3-BDST01 : BDST01: bfr_cnt for pool [hex] is [dec] after all buffers freed
Explanation A system software problem occurred.
Recommended Action A request to free (destroy) a buffer pool has detected a serious problem. The number of buffers in the pool, as indicated by the buffer pool control block, does not match the actual number of buffers in the pool. Either a logic problem exists, or the buffer pool control block has been overwritten with bad data. 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%APPN-3-BFRE01 : BFRE01:Buffer [hex] is invalid
Explanation A request to free a data buffer detected a serious problem.
Recommended Action The data buffer's header has been corrupted, or more likely, a data buffer that has already been freed is being freed again. There is an internal code problem with the system. 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%APPN-3-BFRE02 : BFRE02:Buffer [hex] points to an invalid pool [hex]
Explanation A request to free a data buffer detected a serious problem.
Recommended Action The data buffer's header contains invalid information, or the target buffer pool is invalid. Either a logic problem exists, or more likely, the buffer header or the buffer pool control block have been overwritten with bad data. There is an internal code problem with the system. 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%APPN-3-BFRE03 : BFRE03:Buffer [hex] points to pool [hex] with in_use_p of NULL
Explanation A request to free a data buffer detected a serious problem.
Recommended Action The buffer pool identified in the buffer header indicates that no buffers are currently allocated. Either the data buffer's header contains invalid information, the target buffer pool is invalid or has been corrupted, or the data buffer has already been freed. Either a logic problem exists, or more likely, the buffer header or the buffer pool control block have been overwritten with bad data. There is an internal code problem with the system. 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%APPN-3-BFRE04 : BFRE04:Buffer [hex] is of an unknown type
Explanation A request to free a data buffer detected a serious problem.
Recommended Action The data buffer's header contains invalid information. The buffer type (the type of buffer pool from which the buffer was allocated) is invalid. Either a logic problem exists, or more likely, the buffer header or the buffer pool control block have been overwritten with bad data. There is an internal code problem with the system. 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%APPN-3-BFRE50 : BFRE50:Pool [hex] header was freed but wait list was not empty
Explanation A hardware or software error 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%APPN-3-BGET01 : BGET01:Pool [hex] is invalid
Explanation A request to allocate a data buffer detected a serious problem.
Recommended Action The specified buffer pool contains invalid information, or the buffer pool is invalid. Either a logic problem exists, the buffer pool control block have been overwritten with bad data, or the specified buffer pool has been freed. There is an internal code problem with the system. 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%APPN-3-BGET02 : BGET02:Pool [hex] type is unknown
Explanation A request to allocate a data buffer detected a serious problem.
Recommended Action The specified buffer pool control block contains invalid information. The type of buffer pool indicated in the control block is invalid. Either a logic problem exists, or more likely, the buffer pool control block have been overwritten with bad data. There is an internal code problem with the system. 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%APPN-3-BGET03 : BGET03:Demand buffer size must be 0
Explanation A request to allocate a data buffer detected a serious problem.
Recommended Action The parameters specified on the request are inconsistent. A demand buffer was requested, but the specified buffer size is invalid. Demand buffers are allocated on request, not from a buffer pool, and the size of the requested buffer must be specified on the request. There is an internal code problem with the system. 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%APPN-3-BGET99 : BGET99:Pool [hex] has no free buffers
Explanation A request to allocate a data buffer detected a serious problem.
Recommended Action An internal routine was invoked with an invalid parameter. The invoked routine is used to take one of the available buffers in the buffer pool and mark it as allocated, but the specified buffer pool does not have any available buffers. There is an internal code 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%APPN-3-BGETAS01 : BGETAS01:Pool [hex] is invalid
Explanation A request to allocate a data buffer detected a serious problem.
Recommended Action The specified buffer pool contains invalid information, or the buffer pool is invalid. Either a logic problem exists, the buffer pool control block have been overwritten with bad data, or the specified buffer pool has been freed. There is an internal code problem with the system. 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%APPN-3-BGETAS02 : BGETAS02:Pool [hex] type is unknown
Explanation A hardware or software error 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%APPN-3-BGETAS03 : BGETAS03:Demand buffer size must be 0
Explanation A hardware or software error 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%APPN-3-BGETAS04 : BGETAS04:Invalid pool type
Explanation A request to allocate a data buffer detected a serious problem.
Recommended Action The specified buffer pool control block contains invalid information or cannot be used. The type of buffer pool indicated in the control block is invalid or specifies a type of buffer pool that cannot be used by the requested function to asynchronously allocate a buffer. Either a logic problem exists, or more likely, the buffer pool control block has been overwritten with bad data. There is an internal code problem with the system. 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%APPN-3-BGETAS99 : BGETAS99:Pool [hex] has no free buffers
Explanation A hardware or software error 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%APPN-3-BQXFR01 : BQXFR01:Source data will not fit in target- source bfr=[hex], length is [dec], target length is [dec], byte_count is [dec]
Explanation A system software problem occurred.
Recommended Action A request to transfer data from one data buffer to a data buffer in a different buffer pool failed because one or more parameters specified on the request are invalid. The amount of data to be transferred exceeds the size of the target data buffer. 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%APPN-3-BQXFR02 : BQXFR02:Byte_count of [dec] exceeds source bfr ([hex]) length of [dec]
Explanation A system software problem occurred.
Recommended Action A request to transfer data from one data buffer to a data buffer in a different buffer pool failed because one or more parameters specified on the request are invalid. The amount of data to be transferred exceeds the size of the target data buffer. 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%APPN-3-BQXFR03 : BQXFR03: Byte_count of [dec] exceeds buf_size of [dec] - source bfr is [hex]
Explanation A system software problem occurred.
Recommended Action A request to transfer data from one data buffer to a data buffer in a different buffer pool failed because one or more parameters specified on the request are invalid. The amount of data to be transferred exceeds the size of the target data buffer. 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%APPN-3-BQXFR04 : BQXFR04: Pool type is unknown- target_pool_p is [hex]
Explanation A system software problem occurred.
Recommended Action A request to transfer data from one data buffer to a data buffer in a different buffer pool failed because the specified target buffer pool control block is invalid. The type of buffer pool indicated in the control block is invalid. Either a logic problem exists, or more likely, the buffer pool control block has been overwritten with bad data. 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%APPN-3-BQXFR05 : BQXFR05: Source buffer [hex] type unknown
Explanation A system software problem occurred.
Recommended Action A request to transfer data from one data buffer to a data buffer in a different buffer pool was successful, but the source data buffer could not be freed. The buffer type indicator (which specifies type of buffer pool from which the buffer was allocated) in the source data buffer is invalid. Either a logic problem exists, or more likely, the buffer header has been overwritten with bad data. 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%APPN-3-BQXFR06 : BQXFR06: Target pool [hex] is invalid
Explanation A system software problem occurred.
Recommended Action A request to transfer data from one data buffer to a data buffer in a different buffer pool failed because the specified target buffer pool control block is invalid. A logic problem exists, the buffer pool control block has been overwritten with bad data, or the buffer pool has been freed. 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%APPN-3-BQXFR07 : BQXFR07: Target pool [hex] has no buffers available
Explanation A hardware or software error 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%APPN-3-BRDLRECYC01 : BRDLRECYC01:Rate_Delay B_delay recycled
Explanation A hardware or software error 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%APPN-3-BRST01 : BRST01:Pool [hex] is not valid
Explanation A request to reset the number of buffers in a buffer pool to its initial, current, or assigned value has detected a serious problem.
Recommended Action The specified buffer pool is invalid. Either a logic problem exists, or the buffer pool control block has been overwritten with bad data. 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%APPN-3-BRST02 : BRST02:new_size for pool [hex] is not valid
Explanation A request to reset the number of buffers in a buffer pool to its initial, current, or assigned value has detected a serious problem.
Recommended Action One of the parameters specified on the request is invalid. There is an internal code problem with the system. 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%APPN-3-BRST03 : BRST03:Pool [hex] is not Fixed or Varying
Explanation A request to reset the number of buffers in a buffer pool to its current value has detected a serious problem.
Recommended Action The operation is not allowed for the specified buffer pool. Only fixed or varying buffer pools can have the number of buffers contained by the pool reset to the current size of the pool. There is an internal code problem with the system. 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%APPN-3-BRST04 : BRST04:Pool [hex] is not a Varying pool
Explanation A request to reset the number of buffers in a buffer pool to its current value has detected a serious problem.
Recommended Action The operation is not allowed for the specified buffer pool. Only varying buffer pools can have the number of buffers contained by the pool reset to the assigned size of the pool. There is an internal code problem with the system. 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%APPN-3-BRSV01 : BRSV01: buf_size is [dec], Buffer size must be zero
Explanation A system software problem occurred.
Recommended Action A request to create a buffer pool has detected a serious problem. The parameters specified in the request are inconsistent. The specified buffer size is invalid for the requested type of buffer pool. For fixed and varying buffer pools, you must specify a nonzero buffer size. 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%APPN-3-BRSV02 : BRSV02:pool_size is [dec], Pool size must be 0
Explanation A system software problem occurred.
Recommended Action A request to create a buffer pool has detected a serious problem. The parameters specified in the request are inconsistent. The specified size of the buffer pool (the number of buffers in the pool) is invalid for the requested type of buffer pool. For all types of buffer pools except varying buffer pools, you must specify a nonzero buffer pool size. For limited and rate-limited buffer pools, a value of -1 is also allowed. 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%APPN-3-BRSV03 : BRSV03:pool_size is [dec], Pool size must be 0
Explanation A system software problem occurred.
Recommended Action A request to create a buffer pool has detected a serious problem. The parameters specified in the request are inconsistent. The specified size of the buffer pool (the number of buffers in the pool) is invalid for the requested type of buffer pool. For all types of buffer pools except varying buffer pools, you must specify a nonzero buffer pool size. For limited and rate-limited buffer pools, a value of -1 is also allowed. 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%APPN-3-BRSV04 : BRSV04: pool_size is [hex]
Explanation A system software problem occurred.
Recommended Action A request to create a buffer pool has detected a serious problem. The parameters specified in the request are inconsistent. The specified size of the buffer pool (the number of buffers in the pool) is invalid for the requested type of buffer pool. For all types of buffer pools except varying buffer pools, you must specify a nonzero buffer pool size. For limited and rate-limited buffer pools, a value of -1 is also allowed. 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%APPN-3-BRSV05 : BRSV05: Cannot reserve a pool of Demand buffers..
Explanation A system software problem occurred.
Recommended Action A request to create a buffer pool has detected a serious problem. The specified type of buffer pool is not allowed. The request attempted to create a buffer pool containing demand buffers. Demand buffers are allocated on request and are not part of a buffer pool. 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%APPN-3-BRSV06 : BRSV06: Pool type is unknown..
Explanation A system software problem occurred.
Recommended Action The specified type of buffer pool was invalid. The specified type is not an allowed buffer pool type. 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%APPN-3-BRSV07 : BRSV07: Unknown Mstatus value..
Explanation A hardware or software error 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%APPN-3-BRSV08 : BRSV08: Rate_Limited pool size must = -1 and buffer size = 0..
Explanation A system software problem occurred.
Recommended Action A request to create a buffer pool has detected a serious problem. The parameters specified in the request are inconsistent. The request is trying to create a rate-limited buffer pool. The only allowed value for the size of the buffer pool is -1, and the only allowed value for the size of the buffers in the pool is zero. 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%APPN-3-BSEG01 : BSEG01: Source buffer [hex] or Pool [hex] is not valid
Explanation A request to segment the data contained in a data buffer (either split the data into segments or combine the data into existing data segments) failed because either the specified data buffer or buffer pool control block is invalid.
Recommended Action Probable causes of this error are a logic problem, the buffer header has been overwritten with bad data, the buffer pool control block has been overwritten with bad data, the data buffer has been freed, or the buffer pool has been freed. 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%APPN-3-BSEG02 : BSEG02: Bad input parameter to segment buffer [hex] in Pool [hex]
Explanation A request to segment the data contained in a data buffer (either split the data into segments or combine the data into existing data segments) failed because one or more of the parameters specified in the request are invalid.
Recommended Action There is an internal code problem with the system. 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%APPN-3-BSEG03 : BSEG03: Bqxfr failed while segmenting buffer [hex] in Pool [hex]
Explanation A request to segment the data contained in a data buffer (either split the data into segments or combine the data into existing data segments) failed because the segmented data could not be transferred into the specified target buffer pool.
One or more of the following log entries should also be created when this error occurs:
•
F7100000-00000036
•
•
•
•
•
There is an internal code problem with the system.
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%APPN-3-BSEG04 : BSEG04: Request to move [dec] bytes; actual moved [dec] bytes
Explanation A request to segment the data contained in a data buffer (either split the data into segments or combine the data into existing data segments) encountered an error while copying the data from the source data buffer into a target buffer.
Recommended Action The actual number of bytes copied did not match the requested number of bytes to be copied. There is an internal code problem with the system. It is possible that this condition may not cause any external processing problems. The node may be able to recover from the condition and continue normal processing. 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%APPN-3-BSEG05 : BSEG05: Request to join [hex] to [hex] failed with return of [dec]
Explanation A request to segment the data contained in a data buffer (either split the data into segments or combine the data into existing data segments) encountered an error while moving the data from the source data buffer into a target buffer.
Recommended Action There is an internal code problem with the system. It is possible that this condition may not cause any external processing problems. The node may be able to recover from the condition and continue normal processing. 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%APPN-3-BUNR01 : BUNR01: Pool [hex] is not valid
Explanation A system software problem occurred.
Recommended Action A request to decrease the number of buffers in a buffer pool has detected a serious problem. The specified buffer pool is invalid. Either there is a logic problem, or the buffer pool control block has been overwritten with bad data. 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%APPN-3-BUNR02 : BUNR02: chg_amt for pool [hex] is negative
Explanation A system software problem occurred.
Recommended Action A request to decrease the number of buffers in a buffer pool has detected a serious problem. The parameter used to indicate how many buffers should be removed from the buffer pool is invalid. 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%APPN-3-BUNR03 : BUNR03: Pool [hex] is not a Fixed or Varying pool
Explanation A system software problem occurred.
Recommended Action A request to decrease the number of buffers in a buffer pool has detected a serious problem. The operation is not allowed on the specified buffer pool. Only fixed and varying buffer pools can have their sizes (the number of buffers in the pool) decreased. 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%APPN-3-BXFER01 : BXFER01: Source data will not fit in target-
Explanation A request to transfer data from one data buffer to a data buffer in a different buffer pool failed because one or more parameters specified on the request are invalid.
Recommended Action The amount of data to be transferred exceeds the size of the target data buffer. There is an internal code problem with the system. 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%APPN-3-BXFER02 : BXFER02: Source buffer type unknown- buffer=[hex]
Explanation A request to transfer data from one data buffer to a data buffer in a different buffer pool was successful, but the source data buffer could not be freed.
Recommended Action The buffer type indicator in the source data buffer (which specifies type of buffer pool from which the buffer was allocated) is invalid. Either there is a logic problem, or more likely, the buffer header has been overwritten with bad data. There is an internal code problem with the system. 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%APPN-3-BXFER03 : BXFER03: Source buffer is invalid - buffer=[hex]
Explanation A request to transfer data from one data buffer to a data buffer in a different buffer pool failed because the specified source buffer is invalid.
Recommended Action Either the data buffer has been overwritten with bad data, or a data buffer that has already been freed is being used. There is an internal code problem with the system. 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%APPN-3-BXFER04 : BXFER04: Target buffer is invalid - buffer=[hex]
Explanation A request to transfer data from one data buffer to a data buffer in a different buffer pool failed because the specified target buffer is invalid.
Recommended Action Either the data buffer has been overwritten with bad data, or a data buffer that has already been freed is being used. 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%APPN-3-BXFER05 : BXFER05: Cannot Bxfr into a Rate_limited pool, target buffer=[hex]
Explanation A request to transfer data from one data buffer to a data buffer in a different buffer pool failed because the specified target buffer pool control block is invalid.
Recommended Action The specified buffer pool cannot be used for the requested type of transfer (data cannot be transferred into a rate-limited buffer pool). 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%APPN-3-DlurRetryFail : DLUS Operator activation required for DLUS-DLUR pipe
Explanation A hardware or software error 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%APPN-3-Error : [chars]
Explanation A hardware or software error 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%APPN-3-Generic : [chars]
Explanation A hardware or software error 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%APPN-3-logamATTACH_REJECTED : Incoming Attach Rejected, subtype = 0x[hex]
Explanation The attach manager (AM) rejected a request to start a conversation (SNA ATTACH). The AM rejected an incoming ATTACH from a partner node. Following are some of the reasons that the ATTACH is rejected, along with the associated subtype:
•
•
•
•
•
•
•
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logamRCV_ALLOC_NEVER_ISSUED : Program never issued RECEIVE ALLOCATE
Explanation A program was started by the attach manager (AM) but ended before issuing a RECEIVE_ALLOCATE for the ATTACH that initiated the program.
Recommended Action The AM started a program because of it received an ATTACH for a transaction program that references the program. The started program ended before issuing a RECEIVE_ALLOCATE for the incoming ATTACH. Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logamUNEXPECTED_DOS_ERROR_RC : Unexpected system error, start_timer_rc = 0x[hex]
Explanation An operating system function failed while processing an incoming ATTACH or a RECEIVE_ALLOCATE from a transaction program.
Recommended Action The attach manager (AM) could not process an incoming request to create a conversation because a system function failed. The conversation failure occurred while processing an incoming ATTACH message or a RECEIVE_ALLOCATE from a local transaction program. The failure could have occurred for one of the following reasons. The function PEstart_timer failed while queueing the RECEIVE_ALLOCATE verb (to wait for an incoming ATTACH). The program file referenced in an incoming ATTACH could not be found. The program filename was determined from the transaction program in the ATTACH (default TP processing). The function PEstart_timer failed while queueing the incoming ATTACH (to wait for a transaction program to issue the appropriate RECEIVE_ALLOCATE verb). The program file referenced in an incoming ATTACH could not be found. The program filename was obtained from a DEFINE_TP verb for the transaction program in the ATTACH. There is an internal code problem. Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logamUNEXPECTED_EGPE_ERROR_RC : AM unable to create process
Explanation A hardware or software error occurred.
Recommended Action There is an internal code problem. Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logamUNKNOWN_IPS_RCVD : Unknown IPS received
Explanation The attach manager (AM) received an internal interprocess signal that it does not recognize or cannot process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logamUNKNOWN_VERB_RCVD : Unknown verb received from API, ips name = [hex]
Explanation The attach manager (AM) received an application programming interface verb from an API interface that it does not recognize or cannot process.
Recommended Action There is an internal code problem. Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logapiGPE_ERROR : Error Encountered, = [hex]
Explanation A system function failed while trying to process an API verb received from an application program.
Recommended Action Probable causes of the error are a serious memory shortage, a system error that occurred while processing the API verb, or a programming error in the local node. One of the functions that can fail is Pattach. Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logapiOS_ERROR : OS Error Encountered, rc = [hex]
Explanation An operating system function failed while trying to process an API verb received from an application program.
Recommended Action Probable causes of this error are a serious memory shortage, a system error that occurred while processing the API verb, or a programming error in the local node. Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logcsCS_ACT_AS_DLCX_FAIL_RSP : CS - CS - activate_as for local path control failed
Explanation A hardware or software error 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%APPN-3-logcsCS_ACT_AS_RSP : CS - CS - activate_as for local path control failed, sense_code = [hex]
Explanation Configuration services (CS) failed to initialize. The address space for local path control could not be created. The cause of the failure is indicated by the sense code. This condition should occur only if there is a serious memory shortage.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. 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%APPN-3-logcsCS_ACT_AS_RSP_NEG : CS - Rcvd activate_as_rsp(neg): sense_code = [hex], ls_name = [chars], real_adj_cp_name = [chars]
Explanation Configuration services (CS) failed to successfully activate a route. The address space for the transmission group could not be created. The cause of the failure is indicated by the sense code. The likely cause for this problem is that memory could not be allocated for the new address space.
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%APPN-3-logcsCS_ACT_AS_RSP_UNKWN_LPID : CS - ACT_AS_RSP UNKNOWN LPID: lpid = [hex]
Explanation The link station identified in the received response does not exist.
Recommended Action Configuration services (CS) received an ACTIVATE_AS_RSP interprocess signal (IPS) specifying a link-station control block that is invalid or no longer exists. 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%APPN-3-logcsCS_ACT_ROUTE : CS - ACTIVATE ROUTE FAILED, sense_code = [hex], tg_number = [hex], native_name = [chars]
Explanation An attempt to activate a route to the indicated node failed. The route is a connection network transmission group (TG), link TG, or local TG.
Recommended Action The sense code specifies the error encountered. Probable causes of this error are that a communications error occurred trying to establish a connection, a hardware error occurred, or internal resources (such as memory) are not available. If the condition is one that generates an alert (such as a hardware error), the detecting component that generated an alert will indicate the specific cause of 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%APPN-3-logcsCS_ALERT_MSU : CS - ALERT_MSU received either:
Explanation A connection was unexpectedly terminated by the local DLC support because an alert situation was detected.
Recommended Action An established connection or a connection in the process of being established was unexpectedly terminated. Probable causes of this error are a communications error terminating the connection, or a hardware error terminating the connection. The local DLC support generates an alert indicating the specific cause of 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%APPN-3-logcsCS_AS_DEACTVD_UNKN_LPID : CS - AS_DEACTIVATED UNKNOWN LPID: lpid = [hex]
Explanation The link station identified in the received interprocess signal (IPS) does not exist.
Recommended Action Configuration services (CS) received an AS_DEACTIVATED IPS from ASM specifying a link-station control block that is invalid or no longer exists. 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%APPN-3-logcsCS_CREATE_TG_RSP : CS - create_tg for local path control failed, return_code = [hex]
Explanation Configuration services (CS) failed to initialize. The transmission group (TG) for local path control could not be created.
Recommended Action Initialization of the CS component failed. The request to create the local path control TG failed with the indicated return code. The probable cause of this error is a serious memory shortage. 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%APPN-3-logcsCS_DISC_IND : CS - DISC.IND for: port_name = [chars], link_status = [hex]
Explanation A connection was unexpectedly terminated by the remote node or because a communications error occurred.
Recommended Action Probable causes of this error are the remote node terminating the connection, a communications error terminating the connection, or a hardware error terminating the connection. If the condition is one that generates an alert (such as a hardware error), the detecting DLC will generate an alert indicating the specific cause of 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%APPN-3-logcsCS_FLUSH_IPS : CS - Flushing ips queue, ips_name = [hex]
Explanation A hardware or software error 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%APPN-3-logcsCS_FSM_CN_TG : CS - FSM_CN_TG Abending - INVALID ACTION!, pratner_cp_name = [chars]
Explanation The connection network transmission group (TG) finite state machine (FSM) encountered an unrecoverable error and configuration services (CS) abended.
Recommended Action Probable causes of this error are invalid input or input out of sequence. Configuration services abends, effectively terminating the node. 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%APPN-3-logcsCS_FSM_DLC_INV_INPUT : CS - FSM_DLC INVALID INPUT:, dlc_name = [chars], current state = [hex], input value = [hex]
Explanation The DLC finite state machine (FSM) received an unexpected or unrecognized input value.
Recommended Action Probable causes of this error are invalid input or input out of sequence. 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%APPN-3-logcsCS_FSM_LS_INVALID_ACTION : CS - FSM_LS INVALID ACTION: ls_name = [chars]
Explanation The link station finite state machine (FSM) encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. 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%APPN-3-logcsCS_FSM_LS_INV_INPUT : CS - FSM_LS INVALID INPUT: ls_name = [chars], current_state = [hex]
Explanation The finite state machine (FSM) governing link activation XID3 exchanges encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. 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%APPN-3-logcsCS_FSM_LS_INV_STATE : CS - FSM_LS INVALID STATE: ls_name = [chars], current_state = [hex], input_value = [hex]
Explanation The link station finite state machine (FSM) encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. 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%APPN-3-logcsCS_FSM_PORT_INV_ACTION : CS - FSM_PORT INVALID ACTION: port_name = [chars], action = [hex]
Explanation The port finite state machine (FSM) encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. 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%APPN-3-logcsCS_FSM_PORT_INV_INPUT : CS - FSM_PORT INVALID INPUT: port_name = [chars], current_state = [hex], ips_name(input) = [hex]
Explanation The port finite state machine (FSM) received an unexpected or unrecognized input value.
Recommended Action Probable causes of this error are invalid input or input out of sequence. 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%APPN-3-logcsCS_FSM_PORT_INV_STATE : CS - FSM_PORT INVALID STATE: port_name = [chars], current_state = [hex], input_value = [hex]
Explanation The port finite state machine (FSM) encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. 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%APPN-3-logcsCS_FSM_TG_INVALID_ACTN : CS - FSM_TG_NEGOTIATION INVALID ACTION: ls_name = [chars], action = [hex]
Explanation The transmission group (TG) number negotiation FSM encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. The remote node can also cause this problem by sending an XID out of sequence or with invalid parameters. 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%APPN-3-logcsCS_FSM_TG_INVALID_STATE : CS - FSM_TG_NEGOTIATION INVALID STATE: ls_name = [chars], current_state = [hex], input_value = [hex]
Explanation The transmission group (TG) number negotiation FSM for secondary link stations encountered an unexpected condition.
Recommended Action Probable causes of this error are invalid input or input out of sequence. The remote node can also cause this problem by sending an XID out of sequence or with invalid parameters. 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%APPN-3-logcsCS_FSM_XID3_INVAL_INPUT : CS - FSM_XID3 INVALID INPUT: ls_name = [chars], current_state = [hex], input_value = [hex]
Explanation The finite state machine (FSM) governing link activation XID3 exchanges encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. The remote node can also cause this problem by sending an XID with invalid settings. 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%APPN-3-logcsCS_FSM_XID3_NONACT_PRI : CS - FSM_XID3_NONACT_PRI INVALID ACTION: ls_name = [chars], action = [hex]
Explanation The finite state machine (FSM) governing nonactivation XID3 exchanges for primary link stations encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. The remote node can also cause this problem by sending an XID out of sequence or with invalid parameters. The FSM should be robust enough to handle any condition, except blatant protocol violations. 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%APPN-3-logcsCS_NONACT_SEC_INV_ACTION : CS - FSM_XID3_NONACT_SEC INVALID ACTION: LS=[chars]; ACTION=[hex];
Explanation The finite state machine (FSM) governing nonactivation XID3 exchanges for secondary link stations encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. 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%APPN-3-logcsCS_NONACT_SEC_INV_STATE : CS - FSM_XID3_NONACT_SEC INVALID STATE: ls_name = [chars], current state = [hex], input = [hex]
Explanation The finite state machine (FSM) governing nonactivation XID3 exchanges for secondary link stations encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. 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%APPN-3-logcsCS_NULL_LS_CB : CS - Null LS CB: Dlc:%1; Port:%2
Explanation A hardware or software error 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%APPN-3-logcsCS_NULL_PORT_CB : CS - Null Port CB: Dlc:%1
Explanation A hardware or software error 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%APPN-3-logcsCS_PDOPEN_TO_DLCX_FAILED : CS - PDopen to DLCX failed
Explanation A hardware or software error 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%APPN-3-logcsCS_PEGET_PID_PC_FAILED : CS - PEget_pid for PC failed
Explanation A hardware or software error 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%APPN-3-logcsCS_PEGET_SS_EID_FAILED : CS - PEget_ss_eid for port failed, ss_name = [chars]
Explanation A hardware or software error 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%APPN-3-logcsCS_START_LS : CS - Sending START_LS(-RSP) to Console: ls_name = [chars], sense_code = [hex]
Explanation The link station finite state machine (FSM) encountered a normal race condition.
Recommended Action An inbound activation request was received for a link station at the same time that the node was attempting to activate the link station with an outbound request. The local node was in the process of attempting to establish a connection with a remote node (link station outbound activation request) when an inbound activation request was received from the same remote node for the same link station. This is a normal race condition that can be avoided, but is recoverable. The outbound connection request is rejected with a X`C3E2F4F8' sense code, but the node continues by processing the inbound connection attempt. If successfully processed, communication is established via the inbound connection attempt. The only undesired side effect is that the link station is changed to one used for inbound requests, not outbound requests. If the connection is established, ensure that the established connection's characteristics are valid and usable (such as CP-CP session support and BTU sizes). If not satisfactory, terminate the connection and retry initiating it from the local node. To prevent these collisions, change the network definitions in the nodes so that only one node will attempt to establish the connection.
Error Message%APPN-3-logcsCS_START_LS_SENT_TO_NOF : CS - START_LS sent to NOF:
Explanation Configuration services (CS) completed processing a NOF request to activate a link station or completed processing a NOF request while starting up all activate-at-startup link stations.
Recommended Action This log entry indicates the results of that attempt. If the response is positive (the sense code is zero), the link station was successfully started and is now available for use. If the sense code is not zero, the activation attempt failed and the sense code specifies the error encountered. Probable causes of this error are that a communications error occurred trying to establish a connection, a hardware error occurred, or internal resources (such as memory) are not available. If the condition is one that generates an alert (such as a hardware error), the detecting component generates an alert that indicates the specific cause of the problem. If the attempt failed, the indicating link station is not activated. The operator request that triggered the request from NOF fails. If this failure occurs while a node is starting up, one or more of the activate-at-startup links did not activate. Determine why the link could not be activated and remedy the situation. When fixed, reissue the request to start the link station. If the error occurred during node startup, reactivate all links that were not activated.
Error Message%APPN-3-logcsCS_XID_ON_INACTV_PORT : CS - XID received on inactive port: port_name = [chars]
Explanation Configuration services (CS) received an XID from a DLC for an undefined or inactive port.
Recommended Action CS received an incoming XID from a DLC for a port that is not defined to CS or is inactive (according to CS). This condition should occur only during a race condition where the DLC is forwarding the XID just as CS is deactivating the port. 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%APPN-3-logcsCS_XXXCSP51_LOGMSG_00 : CS - Invalid LSA_IPS lsah.u_cep_id (ls_cb_p)
Explanation Configuration services (CS) encountered an unrecoverable error.
Recommended Action CS received an invalid data-link control (DLC) command from a DLC component. The link station identifier contained in the command is invalid (it does not reference a valid 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%APPN-3-logcsCS_XXXCSP51_LOGMSG_01 : CS - Invalid LSA_IPS lsah.primitive_code (port_cb_p)
Explanation Configuration services (CS) encountered an unrecoverable error.
Recommended Action CS received an invalid data-link control (DLC) command from a DLC component. The port identifier contained in the command is invalid (it does not reference a valid port). 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%APPN-3-logcsCS_XXXXIP11_LOGMSG_00 : CS - Unable to locate link station control block
Explanation The configuration services component detected an external error and attempted to generate an alert to be sent to the Systems Network Architecture/Management Services (SNA/MS) alert focal point.
Recommended Action The alert could not be sent because the data-link control (DLC) control block associated with the alert cannot be determined. 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%APPN-3-logcsCS_XXXXIP11_LOGMSG_01 : CS - Sending Alert to MS, sense_code = [hex], proc_name = [chars], port_name = [chars], ls_name = [chars]
Explanation The configuration services (CS) component detected an external error and generated an alert to be sent to the Systems Network Architecture/Management Services (SNA/MS) alert focal point.
Recommended Action The sense code indicates the type of error encountered. The SNA/MS reference lists the alerts that are generated by the CS component of APPN. MS tries to forward the alert to the alert focal point, and also logs the contents of the alert in the local system log. Any XID data associated with the alert is logged separately in log records 2F101000-0000001E, 2F101000-0000001F, 2F101000-00000020, or 2F101000-00000021. 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%APPN-3-logcsCS_XXXXIP11_LOGMSG_02 : CS - Associated outbound XID data in alert (length < 29):
Explanation This log record is used to log any associated outbound XID data associated with the alert.
Recommended Action In particular, this log record is used to log any additional information when an outbound XID is not available. See the description of log record 2F101000-0000001D for more information. 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%APPN-3-logcsCS_XXXXIP11_LOGMSG_03 : CS - Associated outbound XID data in alert (length = 29):
Explanation This log record is used to log any associated outbound XID data associated with the alert.
Recommended Action In particular, this log record is used when outbound XID data is available. See the description of log record 2F101000-0000001D for more information. 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%APPN-3-logcsCS_XXXXIP11_LOGMSG_04 : CS - Associated inbound XID data in alert (length < 29):
Explanation This log record is used to log any associated outbound XID data associated with the alert.
Recommended Action In particular, this log record is used when outbound XID data is available. See the description of log record 2F101000-0000001D for more information. 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%APPN-3-logcsCS_XXXXIP11_LOGMSG_05 : CS - Associated inbound XID data in alert (length = 29):
Explanation This log record is used to log any associated outbound XID data associated with the alert.
Recommended Action In particular, this log record is used when inbound XID data is available. See the description of log record 2F101000-0000001D for more information. 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%APPN-3-logdsDS_NEWDSa00_LOGMSG_01 : DS - APmain: Unknown APPL message received = %#0.4x
Explanation Directory services (DS) internal search routine received an internal interprocess signal that it does not recognize or cannot process.
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%APPN-3-logdsDS_NEWDSa01_LOGMSG_01 : DS - LSprocess_locate_msg: Unknown search procedure
Explanation Directory services (DS) received an invalid LOCATE_MESSAGE interprocess signal.
Recommended Action The appropriate search finite state machine (FSM) could not be determined from the data in the signal. 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%APPN-3-logdsDS_NEWDSa01_LOGMSG_02 : DS - LSprocess_locate_msg: Invalid searchFSM type
Explanation Directory services (DS) received an invalid LOCATE_MESSAGE interprocess signal.
Recommended Action The appropriate search finite state machine (FSM) could not be determined from the data in the signal. The DS routine used to determine the search FSM returned an invalid value. 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%APPN-3-logdsDS_NEWDSc02_LOGMSG_01 : DS - Invalid wildcard indicator in resource descriptor
Explanation Directory services (DS) received an invalid UPDATE_DIRECTORY (of type DELETE) interprocess signal.
Recommended Action The resource type could not be determined from the resource descriptor in the signal. 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%APPN-3-logdsDS_NEWDSc02_LOGMSG_02 : DS - CPupdate directory: Invalid resource hierarchy found in UPDATE_DIRECTORY message
Explanation Directory services (DS) received an invalid UPDATE_DIRECTORY (of type UPDATE or ADD) interprocess signal.
Recommended Action The resource hierarchy contained in the signal's resource descriptor is invalid. 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%APPN-3-logdsDS_NEWDScf0_LOGMSG_01 : DS - CP_STATUS FSM: Unanticipated CP_STATUS message received, node name = [chars], new state = [dec], old state = [dec], session status = [dec]
Explanation The control point (CP) status FSM encountered an unexpected CP_STATUS interprocess signal (IPS).
Recommended Action Probable causes of this error are invalid input or input out of sequence. 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%APPN-3-logdsDS_NEWDScf0_LOGMSG_02 : DS - CP_STATUS FSM: Invalid action encountered
Explanation The control point (CP) status FSM encountered an unrecoverable error.
Recommended Action Probable causes of this error are invalid input or input out of sequence. 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%APPN-3-logdsDS_NEWDSd03_LOGMSG_01 : DS - DBcheck_rsc_hierarchy_error: rsc_hierarchy structure does not contain an NN or EN
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action A resource hierarchy control block in the directory is invalid. It does not contain a network node name or end node name. 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%APPN-3-logdsDS_NEWDSd03_LOGMSG_02 : DS - DBcheck_rsc_hierarchy_error: rsc_hierarchy structure does not contain an LU
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action A resource hierarchy control block in the directory is invalid. It does not contain an LU name. 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%APPN-3-logdsDS_NEWDSd10_LOGMSG_01 : DS - DBcreate_adj_node: Duplicate adjacent node record created
Explanation Directory services (DS) detected two adjacent nodes with the same control point name.
Recommended Action DS received a CP_STATUS message to add an adjacent node to the directory. The adjacent node identified in the signal is already defined in the directory. Probable causes of this error are a network definition error where two nodes are defined with the same control point name, a remote node sending an invalid message, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSd15_LOGMSG_01 : DS - Invalid adjacent node record encountered
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action An adjacent node record in the directory is invalid. It does not contain a valid eyecatcher. 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%APPN-3-logdsDS_NEWDSd20_LOGMSG_01 : DS - DBcopy_sdi_to_sdo: sdi not allocated
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action There is an internal code problem in the DS component. The routine that is used to copy search data descriptor control blocks determined the source control block is either not a search data descriptor or is no longer in use. 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%APPN-3-logdsDS_NEWDSd20_LOGMSG_02 : DS - DBcopy_sdi_to_sdo: sdo not allocated
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action There is an internal code problem in the DS component. The routine that is used to copy search data descriptor control blocks determined the source control block is either not a search data descriptor or is no longer in use. 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%APPN-3-logdsDS_NEWDSd20_LOGMSG_03 : DS - DB_insert_search_data: duplicate DB entry
Explanation Directory services (DS) encountered an unexpected condition. An internal logic problem exists within DS.
Recommended Action Duplicate search requests for the same resource have been requested (duplicate search data descriptors). 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%APPN-3-logdsDS_NEWDSd20_LOGMSG_04 : DS - DBdump_search_data: invalid search_status enum
Explanation Directory services (DS) encountered an unexpected condition. An internal control block is invalid.
Recommended Action The search status indicator in the descriptor is invalid. 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%APPN-3-logdsDS_NEWDSd30_LOGMSG_01 : DS - DBcreate_locate_record: Creating duplicate locate record
Explanation Directory services (DS) encountered an unexpected condition. There is an internal logic problem with DS.
Recommended Action Duplicate locate requests have been created (duplicate locate records). 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%APPN-3-logdsDS_NEWDSd30_LOGMSG_02 : DS - DBinit_search: Invalid SEARCH_EVENT.TYPE
Explanation Directory services (DS) encountered an unexpected condition. An internal control block is invalid.
Recommended Action The type of search in the request is invalid. 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%APPN-3-logdsDS_NEWDSd40_LOGMSG_01 : DS - DBcreate_locate_cb: Creating duplicate locate cb
Explanation Directory services (DS) encountered an unexpected condition. There is an internal logic problem with DS.
Recommended Action Duplicate locate records have been created (duplicate descriptors for the same locate request). 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%APPN-3-logdsDS_NEWDSd42_LOGMSG_01 : DS - Invalid search_state
Explanation Directory services (DS) encountered an unexpected condition. An internal control block is invalid.
Recommended Action The search status in the locate record is invalid. 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%APPN-3-logdsDS_NEWDSd42_LOGMSG_02 : DS - Invalid node_role enum encountered
Explanation Directory services (DS) encountered an unexpected condition. An internal control block is invalid.
Recommended Action The search finite state machine (FSM) ID, which indicates the local node's role in the search, is invalid. 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%APPN-3-logdsDS_NEWDSd50_LOGMSG_01 : DS - Invalid wildcard indicator in resource descriptor, value = [dec]
Explanation Directory services (DS) encountered an unexpected condition. An internal control block is invalid.
Recommended Action A resource descriptor is invalid. The wildcard indicator in the descriptor is invalid. 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%APPN-3-logdsDS_NEWDSd50_LOGMSG_02 : DS - LU name duplicates the name of a non-cached directory entry
Explanation Directory services (DS) detected two resources with the same name.
Recommended Action DS received a request to add an LU to the directory, but an LU or control point is already defined in the directory with the same name. The existing entry is a home or registered entry, meaning it was explicitly placed in the directory by local or remote configuration information. Probable causes of this error are a network definition error with two resources defined with the same name, the remote node sending an invalid message, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSd50_LOGMSG_03 : DS - Partial wildcard LU name conflicts with another partial wildcard directory entry
Explanation Directory services (DS) received a request to add duplicate partial wildcard entries in the directory.
Recommended Action DS received a request to add a partial wildcard resource description to the directory, but the wildcard LU name is already defined in the directory. Probable causes of this error are a network definition error with the same partial wildcard entry defined twice, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSd50_LOGMSG_04 : DS - Duplicate full wildcard directory entries
Explanation Directory services (DS) received a request to add duplicate partial wildcard entries in the directory.
Recommended Action Configuration services (CS) received a request to add a full wildcard resource description to the directory, but the directory already contains a full wildcard directory entry. Only one full wildcard entry is allowed in the directory. Probable causes of the error are a network definition error with the multiple full wildcard entries defined, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSd51_LOGMSG_01 : DS - Adjacent node has an unexpected node type of NN
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action An internal control block is invalid or there is a logic error in the DS component. A search of the directory returned an incorrect or invalid directory entry. The search was a domain search, which should search only for resources owned by end nodes or migration end nodes within the domain of the network node. The returned directory entry is invalid, because its associated adjacent node record indicates that the adjacent node, which the resource is in the domain of, is a network node. 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%APPN-3-logdsDS_NEWDSd51_LOGMSG_02 : DS - Invalid adjacent node type in adjacent node record, value = [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action An internal control block is invalid. An adjacent node record in the directory is invalid. It does not contain a valid node type value. 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%APPN-3-logdsDS_NEWDSd54_LOGMSG_01 : DS - Could not open DSrd.log file, unable to dump DS database
Explanation The request to open the specified dump file failed.
Recommended Action Directory services (DS) could not dump the resource directory. The dump file could not be opened. Probable causes of the error are that a system function failure has occurred (preventing the file from being opened by directory services), or the file is already opened by another program within the system. The file can be read by other programs, but should not be opened for write access. 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%APPN-3-logdsDS_NEWDSd54_LOGMSG_02 : DS - Invalid resource location in a directory entry
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action A resource directory entry is invalid. The resource location in the entry is invalid. 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%APPN-3-logdsDS_NEWDSd54_LOGMSG_03 : DS - Invalid entry type in a directory entry, type = [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action A resource directory entry is invalid. The entry type (permanent, registered, or cached) in the entry is invalid. 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%APPN-3-logdsDS_NEWDSd54_LOGMSG_04 : DS - Invalid wildcard indicator in a directory entry, type = [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action A resource directory entry is invalid. The wildcard type (explicit, partial, or full) in the entry is invalid. 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%APPN-3-logdsDS_NEWDSf01_LOGMSG_01 : DS - DBsd_gds_12C4_search_status invalid, value = [dec]
Explanation Directory services (DS) received or detected an invalid LOCATE message (GDS x`12C4').
Recommended Action DS encountered an invalid LOCATE GDS variable. The search-status indicators in the message are invalid. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSf03_LOGMSG_01 : DS - FMT: Inbound search: Unrecognized control vector in CV2B = %#0.2x
Explanation Directory services (DS) does not recognize a control vector contained in a received x`2B' control vector.
Recommended Action DS encountered an invalid x`2B' control vector. It contains one or more control vectors not recognized by directory services. Probable causes of this error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSf04_LOGMSG_01 : DS - FMTmap_cv0E: invalid cv0E
Explanation Directory services (DS) encountered an unexpected situation.
Recommended Action There is an internal code problem in the DS component. The routine used to map and unmap the control vector x`0E' determined that the unmapped x`0E' control vector structure is either not a x`0E' control vector structure, or is no longer in use. 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%APPN-3-logdsDS_NEWDSf04_LOGMSG_02 : DS - FMTmap_cv0E: invalid NET_NAME_TYPE
Explanation Directory services (DS) encountered an unexpected situation.
Recommended Action There is an internal code problem in the DS component. The routine used to map and unmap the control vector x`0E' determined that the unmapped x`0E' control vector structure is invalid. 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%APPN-3-logdsDS_NEWDSf04_LOGMSG_03 : DS - FMTunmap_cv0E: invalid NET_NAME_TYPE
Explanation Directory services (DS) cannot parse a received x`0E' control vector.
Recommended Action DS encountered an invalid x`0E' control vector. The network name (resource) type is not recognized by DS. Probable causes of this error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSf05_LOGMSG_01 : DS - FMTmap_find_cv80: Invalid MIN_RSP_ENTRY
Explanation Directory services (DS) encountered an unexpected situation.
Recommended Action There is an internal code problem in the DS component. The routine used to map and unmap the control vector x`80' determined that the unmapped x`0E' control vector structure is invalid. It contains an invalid minimum response entry type indicator. 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%APPN-3-logdsDS_NEWDSf06_LOGMSG_01 : DS - FMTunmap_rsc_entry: Invalid resource type
Explanation Directory services (DS) could not parse received an x`3C', x`3D', x`81', or x`82' control vector.
Recommended Action The resource type is not recognized by DS. Probable causes of this error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSf06_LOGMSG_02 : DS - FMTunmap_rsc_entry: Invalid cvkey
Explanation Directory services (DS) could not parse a received resource entry control vector.
Recommended Action DS encountered an invalid resource entry control vector. The resource entry control vectors understood by directory services are x`3C', x`3D', x`81', and x`82'. Probable causes of this error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSi00_LOGMSG_01 : DS - INFOmain: Unknown IPS received, IPS = %#0.4x
Explanation Directory services (DS) received an internal interprocess signal that it does not recognize or cannot process.
Recommended Action There is an internal code 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%APPN-3-logdsDS_NEWDSl00_LOGMSG_01 : DS - LSmain: invalid search_event received, %#0.4x
Explanation Directory services (DS) received an invalid request from another node (search).
Recommended Action DS received an invalid search request that contains an invalid search event type. Probable causes of this error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSl01_LOGMSG_01 : DS - Inbound search received, but adjacent node does not exist, adj cp name = [chars]
Explanation Directory services (DS) received an invalid request from another node (search).
Recommended Action DS received an invalid search request. The adjacent node name in the search request does not match any adjacent node records in the directory. Probable causes of this error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSl01_LOGMSG_02 : DS - Received inbound search from node which is being disabled; ignoring search
Explanation Directory services (DS) received a search request from a node with which it is currently deactivating its CP-CP sessions.
Recommended Action The search request is ignored. The node could not send back the reply, because the CP-CP sessions are no longer active to the node. The search request is ignored, and DS continues to process other signals. It is possible that the node will continue to work correctly if this problem occurs. If it appears to be behaving satisfactorily, no immediate action is required.
Error Message%APPN-3-logdsDS_NEWDSl01_LOGMSG_03 : DS - Adjacent node state is invalid. We have a bug
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action An adjacent node record in the directory is invalid. The node state (status) in the adjacent node record is invalid. 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%APPN-3-logdsDS_NEWDSl01_LOGMSG_04 : DS - Inbound search contained invalid or unrecognized control vectors, sense_code = [hex]
Explanation Directory services (DS) received an invalid network search request from another node.
Recommended Action DS received an invalid network search request. DS could not parse the control vectors contained in the request. The sense code specifies the type of error encountered by DS. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSl01_LOGMSG_05 : DS - Inbound search contained incorrect or unexpected control vectors, sense_code = [hex]
Explanation Directory services (DS) received an invalid network search request from another node.
Recommended Action DS received an invalid network search request. The network search either does not contain one or more required control vectors, or contains one or more control vectors that are not valid for the requested type of search. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSl01_LOGMSG_06 : DS - LSprocess_rcvd_search: SearchFSM_Error
Explanation Directory services (DS) received an invalid network search request from another node.
Recommended Action The appropriate search finite state machine (FSM) could not be determined from the data in the request. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSl01_LOGMSG_07 : DS - LSprocess_rcvd_search: Invalid SearchFSM type
Explanation Directory services (DS) received an invalid network search request from another node.
Recommended Action The appropriate search finite state machine (FSM) could not be determined from the data in the request. The DS routine used to determine the search FSM returned an invalid value. 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%APPN-3-logdsDS_NEWDSl02_LOGMSG_01 : DS - FMT:Inbound search: Unexpected control vector in CV2B, mapped_cv[[dec]] = [hex]
Explanation Directory services (DS) does not recognize a control vector contained in a received x`2B' control vector.
Recommended Action DS encountered an invalid network search request. The x`2B' control vector in the request contains one or more control vectors not recognized or processed by directory services. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSl04_LOGMSG_01 : DS - LSprocess_cp_outage: Unknown search procedure
Explanation Directory services (DS) received an invalid CP outage notification from another node.
Recommended Action DS received an invalid notification from another node that a control point has been deactivated (the CP-CP sessions to the node have been deactivated). The appropriate search finite state machine (FSM) could not be determined from the data in the notification. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSl04_LOGMSG_02 : DS - LSprocess_cp_outage: Invalid searchFSM type
Explanation Directory services (DS) received an invalid CP outage notification from another node, which caused an unexpected condition.
Recommended Action DS received an invalid notification from another node that a control point has been deactivated (the CP-CP sessions to the node have been deactivated). The appropriate search finite state machine (FSM) could not be determined from the data in the notification. The directory services routine used to determine the search FSM returned an invalid value. 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%APPN-3-logdsDS_NEWDSl10_LOGMSG_01 : DS - DBsd_gds12C4_search_status invalid, value = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x`12C4'.
Recommended Action DS encountered a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error on the local node. 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%APPN-3-logdsDS_NEWDSl10_LOGMSG_02 : DS - Search event type invalid, type = [dec]
Explanation Directory services (DS) received an invalid request from another node (search).
Recommended Action The search event type in the request is invalid. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSl20_LOGMSG_01 : DS - LSeval_input_InpRole: Invalid LR.SEARCH.ROLE
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action A locate record is invalid. The local node search role indicator in the locate record is invalid. 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%APPN-3-logdsDS_NEWDSlf1_LOGMSG_01 : DS - FSM(dir_INN): Invalid search status in GDS variable x'12C4', value = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x`12C4'.
Recommended Action The DS finite state machine (FSM) dir_INN received a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. This FSM controls the processing of directed searches for resources by an intermediate network node. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf1_LOGMSG_02 : DS - FSM(dir_INN): Invalid input. CP name in CP outage not found, cp name = [chars]
Explanation Directory services (DS) received an invalid control point (CP) outage notification.
Recommended Action The DS finite state machine (FSM) dir_INN received an invalid or unexpected CP outage notification. DS does not have any locate records (pending locate requests) for the control point name contained in the notification. This FSM controls the processing of directed searches for resources by an intermediate network node. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf1_LOGMSG_03 : DS - FSM(dir_INN): Invalid input. Search event type is invalid, type = [dec]
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The directory services finite state machine (FSM) dir_INN received an invalid input search event. The search event type is invalid. This FSM controls the processing of directed searches for resources by an intermediate network node. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. 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%APPN-3-logdsDS_NEWDSlf1_LOGMSG_04 : DS - FSM(dir_INN): invalid input value = %#0.8x
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) dir_INN received an unexpected or unrecognized input value. This FSM controls the processing of directed searches for resources by an intermediate network node. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Another log record may be created in conjunction with this log record (2F102000-00000038 or 2F102000-0000003A) that contains more detailed information on the invalid input condition. 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%APPN-3-logdsDS_NEWDSlf1_LOGMSG_05 : DS - FSM(dir_INN): state error, lcb: %#0.8x pcid: %#0.8x%0.8x row: [dec] col: [dec] inp: %#0.8x
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) dir_INN encountered a state error. This FSM controls the processing of directed searches for resources by an intermediate network node. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-0000003B) may be created in conjunction with this log record when an invalid input value is received. 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%APPN-3-logdsDS_NEWDSlf1_LOGMSG_06 : DS - FSM(dir_INN): invalid action value, lcb: %#0.8x se_p: %#0.8x inp: %#0.8x action: [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) dir_INN sent an unknown or invalid action value. This FSM controls the processing of directed searches for resources by an intermediate network node. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-0000003B) may be created in conjunction with this log record when an invalid input value is received. 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%APPN-3-logdsDS_NEWDSlf2_LOGMSG_01 : DS - FSM(brd_INN): Invalid search status in GDS variable x'12C4', status = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x`12C4'.
Recommended Action The DS finite state machine (FSM) brd_INN received a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. This FSM controls the processing of broadcast searches for resources by an intermediate network node. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf2_LOGMSG_02 : DS - FSM(brd_INN): Invalid input. CP name in CP outage not found. cp name = [chars]
Explanation Directory services (DS) received an invalid control point (CP) outage notification. The associated locate record could not be determined.
Recommended Action The DS finite state machine (FSM) brd_INN received an invalid or unexpected CP outage notification. DS does not have any locate records (pending locate requests) for the control point name contained in the notification. This FSM controls the processing of broadcast searches for resources by an intermediate network node. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf2_LOGMSG_03 : DS - FSM(brd_INN): Invalid input. Search event type is invalid, type = [dec]
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) brd_INN received an invalid input search event. The search event type is invalid. This FSM controls the processing of broadcast searches for resources by an intermediate network node. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf2_LOGMSG_04 : DS - FSM(brd_INN): invalid input value = %#0.8x
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) brd_INN received an unexpected or unrecognized input value. This FSM controls the processing of broadcast searches for resources by an intermediate network node. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record may be created in conjunction with this log record (2F102000-0000003E or 2F102000-00000040) that contains more detailed information on the invalid input condition. 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%APPN-3-logdsDS_NEWDSlf2_LOGMSG_05 : DS - FSM(brd_INN): state error, lcb: %#0.8x pcid: %#0.8x%0.8x row: [dec] col: [dec]
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) brd_INN encountered a state error. This FSM controls the processing of broadcast searches for resources by an intermediate network node. Probable causes of the error are an invalid input value was received because of a programming error in the local node, or the remote node sent an invalid message. Another log record (2F102000-00000041) may be created in conjunction with this log record when an invalid input value is received. 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%APPN-3-logdsDS_NEWDSlf2_LOGMSG_06 : DS - FSM(brd_INN): Invalid resource returned from a domain search, rsc_location = [dec]
Explanation Directory services (DS) encounter an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) brd_INN retrieved an incorrect or invalid directory entry from the directory. The directory entry was retrieved using a domain search, which should only search for resources owned by end nodes or migration end nodes within the domain of the network node. The returned directory entry is invalid, because its associated adjacent node record indicates that the adjacent node (of which the resource is in the domain) is a network node. This FSM controls the processing of broadcast searches for resources by an intermediate network node. There is a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf2_LOGMSG_07 : DS - FSM(brd_INN): invalid action value, lcb: %#0.8x se_p: %#0.8x inp: %#0.8x action: [dec]
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) brd_INN send an unknown or invalid action value. This FSM controls the processing of broadcast searches for resources by an intermediate network node. Probable causes of the error are an invalid input value was received because of a programming error in the local node, or the remote node sent an invalid message. Another log record (2F102000-00000041) may be created in conjunction with this log record when an invalid input value is received. 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%APPN-3-logdsDS_NEWDSlf3_LOGMSG_01 : DS - FSM(parent): Invalid search status in GDS variable x'12C4', value = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x`12C4'.
Recommended Action The DS finite state machine (FSM) parent received a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. This FSM controls the processing of searches for resources relative to the parent node in the request. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf3_LOGMSG_02 : DS - FSM(parent): Invalid input. Search event type is invalid = [dec]
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) parent received an invalid input search event. The search event type is invalid. This FSM controls the processing of searches for resources relative to the parent node in the request. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. 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%APPN-3-logdsDS_NEWDSlf3_LOGMSG_03 : DS - FSM(parent): invalid input value = %#0.8x
Explanation A hardware or software error 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%APPN-3-logdsDS_NEWDSlf3_LOGMSG_04 : DS - FSM(parent): state error, lr: %#0.8x row: [dec] col: [dec] inp: %#0.8x
Explanation A hardware or software error 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%APPN-3-logdsDS_NEWDSlf3_LOGMSG_05 : DS - FSM(parent): invalid action, lr: %#0.8x se_p: %#0.8x inp: %#0.8x action: [dec]
Explanation A hardware or software error 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%APPN-3-logdsDS_NEWDSlf4_LOGMSG_01 : DS - FSM(child): Invalid search status in GDS variable x'12C4', value = [dec]
Explanation A hardware or software error 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%APPN-3-logdsDS_NEWDSlf4_LOGMSG_02 : DS - FSM(child): Invalid input. Locate message is a request
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) child received an invalid input locate message. The locate message is a locate request, and only locate replies should be processed by this FSM. This FSM controls the processing of searches for resources relative to the child node in the request. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. 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%APPN-3-logdsDS_NEWDSlf4_LOGMSG_03 : DS - FSM(child): Invalid input. Search event type is invalid, se type = [dec]
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) child received an invalid input search event. The search event type is invalid. This FSM controls the processing of searches for resources relative to the child node in the request. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. 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%APPN-3-logdsDS_NEWDSlf4_LOGMSG_04 : DS - FSM(child): invalid input value = %#0.8x
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) child received an unexpected or unrecognized input value. This FSM controls the processing of searches for resources relative to the child node in the request. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record may be created in conjunction with this log record (2F102000-0000004A, 2F102000-0000004B, or 2F102000-0000004C) that contains more detailed information about the invalid input condition. 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%APPN-3-logdsDS_NEWDSlf4_LOGMSG_05 : DS - FSM(child): state error, lr: %#0.8x row: [dec] col: [dec] inp: %#0.8x
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) child encountered a state error. This FSM controls the processing of searches for resources relative to the child node in the request. Probable causes of the error are an invalid input value was received because of a programming error in the local node, or the remote node sent an invalid message. Another log record (2F102000-0000004D) may be created in conjunction with this log record when an invalid input value is received. 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%APPN-3-logdsDS_NEWDSlf4_LOGMSG_06 : DS - FSM(child): invalid action value, lr: %#0.8x se_p: %#0.8x inp: %#0.8x action: [dec]
Explanation Directory services (DS) encountered an unexpected condition while searching for a resource.
Recommended Action The DS finite state machine (FSM) child sent an unknown or invalid action value. This FSM controls the processing of searches for resources relative to the child node in the request. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-0000004D) may be created in conjunction with this log record when an invalid input value is received. 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%APPN-3-logdsDS_NEWDSlf5_LOGMSG_01 : DS - FSM(dir_NNSdlu): Received locate reply is incompatible with inputted search type
Explanation Directory services (DS) received an invalid locate reply.
Recommended Action The DS finite state machine (FSM) dir_NNSdlu received an invalid locate reply. The node received a locate reply from a child node, but the child node is not in the domain of the network node server. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf5_LOGMSG_02 : DS - FSM(dir_NNSdlu): Invalid search status in GDS variable x'12C4', value = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x`12C4'.
Recommended Action The DS finite state machine (FSM) dir_NNSdlu received a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf5_LOGMSG_03 : DS - FSM(dir_NNSdlu): Received CP outage is incompatible with inputted search type
Explanation Directory services (DS) received an invalid control point (CP) outage notification.
Recommended Action The DS finite state machine (FSM) dir_NNSdlu received an invalid CP outage notification. The node received the notification from a child node, but the child node is not in the domain of the network node server. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf5_LOGMSG_04 : DS - FSM(dir_NNSdlu): Invalid input. Locate message is a request
Explanation Directory services (DS) encountered an unexpected software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) dir_NNSdlu received an invalid input locate message. The locate message is a locate request, and only locate replies should be processed by this FSM. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. 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%APPN-3-logdsDS_NEWDSlf5_LOGMSG_05 : DS - FSM(dir_NNSdlu): Invalid input. Search event type is invalid, se type = [dec]
Explanation Directory services (DS) encountered an unexpected software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) dir_NNSdlu received an invalid input search event. The search event type is invalid. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. 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%APPN-3-logdsDS_NEWDSlf5_LOGMSG_06 : DS - FSM(dir_NNSdlu): invalid input value = %#0.8x
Explanation Directory services (DS) encountered an unexpected software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) dir_NNSdlu received an unexpected or unrecognized input value. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record may be created in conjunction with this log record (2F102000-00000051, 2F102000-00000053, or 2F102000-00000054) that contains more detailed information on the invalid input condition. 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%APPN-3-logdsDS_NEWDSlf5_LOGMSG_07 : DS - FSM(dir_NNSdlu): state error, lcb: %#0.8x pcid: %#0.8x%0.8x row: [dec] col: [dec] inp: %#0.8x
Explanation Directory services (DS) encountered an unexpected software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) dir_NNSdlu encountered a state error. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-00000055) may be created in conjunction with this log record when an invalid input value is received. 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%APPN-3-logdsDS_NEWDSlf5_LOGMSG_08 : DS - FSM(dir_NNSdlu): Invalid resource location in a directory entry, value = [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (FSM) dir_NNSdlu detected an error in the directory database. A resource directory entry is invalid. The resource location indicator in the entry is invalid. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. There is a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf5_LOGMSG_09 : DS - FSM(dir_NNSdlu): invalid action, lcb: %#0.8x se_p: %#0.8x inp: %#0.8x action: [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) dir_NNSdlu sent an unknown or invalid action value. This FSM controls the processing of directed searches for resources by the network node server of the destination LU. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-00000055) may be created in conjunction with this log record when an invalid input value is received. 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%APPN-3-logdsDS_NEWDSlf6_LOGMSG_01 : DS - FSM(ENdlu): Invalid search status in GDS variable x'12C4', value = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x`12C4'.
Recommended Action The DS finite state machine (FSM) ENdlu received a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. This FSM controls the processing of searches for resources by the end node owning the destination LU. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf6_LOGMSG_02 : DS - FSM(ENdlu): Invalid chain status in GDS variable x'12C4', value = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x`12C4'.
Recommended Action The DS finite state machine (FSM) ENdlu received a search request containing an invalid LOCATE GDS variable. The chain status indicators in the variable are invalid. This FSM controls the processing of searches for resources by the end node owning the destination LU. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf6_LOGMSG_03 : DS - FSM(ENdlu): Invalid input. Search event type is invalid, se type = [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) ENdlu received an invalid input search event. The search event type is invalid. This FSM controls the processing of searches for resources by the end node owning the destination LU. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf6_LOGMSG_04 : DS - FSM(ENdlu): invalid input value = %#0.8x
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) ENdlu received an unrecognized or unexpected input value. This FSM controls the processing of searches for resources by the end node owning the destination LU. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf6_LOGMSG_05 : DS - FSM(ENdlu): state error, lcb: %#0.8x pcid: %#0.8x row: [dec] col: [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) ENdlu encountered a state error. This FSM controls the processing of searches for resources by the end node owning the destination LU. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-0000005C) may be created in conjunction with this log record when an invalid input value is received. 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%APPN-3-logdsDS_NEWDSlf6_LOGMSG_06 : DS - FSM(ENdlu): invalid action value, lcb: %#0.8x se_p: %#0.8x inp: %#0.8x action: [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) ENdlu sent an unknown or invalid action value. This FSM controls the processing of searches for resources by the end node owning the destination LU. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-0000005C) may be created in conjunction with this log record when an invalid input value is received. 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%APPN-3-logdsDS_NEWDSlf7_LOGMSG_01 : DS - FSM(NNolu): Invalid search status in GDS variable x'12C4', value = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x`12C4'.
Recommended Action The DS finite state machine (FSM) NNolu received a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. This FSM controls the processing of searches for resources by the network node owning the origin LU. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf7_LOGMSG_02 : DS - FSM(NNolu): Invalid input. Locate message is not a request
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The directory services FSM NNolu received an invalid input locate message. The locate message is not a locate request, and only locate requests should be processed by this FSM. This FSM controls the processing of searches for resources by the network node owning the origin LU. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf7_LOGMSG_03 : DS - FSM(NNolu): Invalid input. Search event type is invalid, se type = [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The directory services FSM NNolu received an invalid input search event. The search event type is invalid. This FSM controls the processing of searches for resources by the network node owning the origin LU. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf7_LOGMSG_04 : DS - FSM(NNolu): invalid input value, input = [hex]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The directory services FSM NNolu received an unexpected or unrecognized input value. This FSM controls the processing of searches for resources by the network node owning the origin LU. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. Another log record may be created in conjunction with this log record (2F102000-0000005F, 2F102000-00000060, or 2F102000-00000061) that contains more detailed information about the invalid input condition. 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%APPN-3-logdsDS_NEWDSlf7_LOGMSG_05 : DS - FSM(NNolu): state error, lcb: %#0.8x pcid: %#0.8x%0.8x row: [dec] col: [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) ENdlu encountered a state error. This FSM controls the processing of searches for resources by the end node owning the destination LU. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-00000062) may be created in conjunction with this log record when an invalid input value is received. 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%APPN-3-logdsDS_NEWDSlf7_LOGMSG_06 : DS - FSM(NNolu): Invalid resource location in a directory entry, value = [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The directory services FSM NNolu detected an error in the directory database. A resource directory entry is invalid. The resource location indicator in the entry is invalid. There is a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf7_LOGMSG_07 : DS - FSM(NNolu): State error. Expected non-explicit (wildcard) locate reply not found
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (FSM) NNolu encountered a state error. The current state indicates that a nonexplicit (wildcard) locate reply was received for the resource and saved by DS. The saved reply cannot be located using the current search correlator. This FSM controls the processing of searches for resources by the network node owning the origin LU. There is a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf7_LOGMSG_08 : DS - FSM(NNolu): Duplicate LU found on search
Explanation Directory services (DS) detected two resources with the same name.
Recommended Action The DS finite state machine (FSM) NNolu received more than one positive locate reply for the same LU name. This FSM controls the processing of searches for resources by the network node owning the origin LU. Probable causes of the error are a network definition error (two resources defined with the same name), the remote node sending an invalid message, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf7_LOGMSG_09 : DS - FSM(NNolu): invalid action value, input = [hex], action = [hex]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The directory services FSM NNolu sent an unknown or invalid action value. This FSM controls the processing of searches for resources by the network node owning the origin LU. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-00000062) may be created in conjunction with this log record when an invalid input value is received. 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%APPN-3-logdsDS_NEWDSlf8_LOGMSG_01 : DS - FSM(CPolu_child): Invalid search status in GDS variable x'12C4', value = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x`12C4'.
Recommended Action The DS finite state machine (FSM) CPolu_child received a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. This FSM controls the processing of searches for resources relative to the child node in the request by the node owning the origin LU. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf8_LOGMSG_02 : DS - FSM(CPolu_child): Invalid input. Search event type is invalid, se type = [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (FSM) CPolu_child received an invalid input search event. The search event type is invalid. This FSM controls the processing of searches for resources relative to the child node in the request by the node owning the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. 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%APPN-3-logdsDS_NEWDSlf8_LOGMSG_03 : DS - FSM(CPolu_child): invalid input value = [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (FSM) CPolu_child received an unexpected or unrecognized input value. This FSM controls the processing of searches for resources relative to the child node in the request by the node owning the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record may be created in conjunction with this log record (2F102000-00000068 or 2F102000-00000069). The additional log record contains more detailed information on the invalid input condition. 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%APPN-3-logdsDS_NEWDSlf8_LOGMSG_04 : DS - FSM(CPolu_child): state error, lr: %#0.8x row: [dec] col: [dec] inp: %#0.8x
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (FSM) CPolu_child encountered a state error. This FSM controls the processing of searches for resources relative to the child node in the request by the node owning the origin LU. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-0000006A) may be created in conjunction with this log record when an invalid input value is received. 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%APPN-3-logdsDS_NEWDSlf8_LOGMSG_05 : DS - FSM(CPolu_child): invalid action, lr: %#0.8x se_p: %#0.8x inp: %#0.8x action: [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (FSM) CPolu_child sent an unknown or invalid action value. This FSM controls the processing of searches for resources relative to the child node in the request by the node owning the origin LU. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-0000006A) may be created in conjunction with this log record when an invalid input value is received. 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%APPN-3-logdsDS_NEWDSlf9_LOGMSG_01 : DS - FSM(CPolu_parent): Negative LOCATE_MESSAGE(RQ) invalid
Explanation Directory services (DS) received a locate request containing sense data.
Recommended Action The DS finite state machine (FSM) CPolu_parent received a locate request containing a nonzero sense code. This FSM controls the processing of searches for resources relative to the parent node in the request by the node owning the origin LU. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlf9_LOGMSG_02 : DS - FSM(CPolu_parent): Invalid input. Search event type is invalid, type = [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (FSM) CPolu_parent received an invalid input search event. The search event type is invalid. This FSM controls the processing of searches for resources relative to the parent node in the request by the node owning the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. 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%APPN-3-logdsDS_NEWDSlf9_LOGMSG_03 : DS - FSM(CPolu_parent): invalid input value = [hex]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (FSM) CPolu_parent received an unexpected or unrecognized input value. This FSM controls the processing of searches for resources relative to the parent node in the request by the node owning the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record may be created in conjunction with this log record (2F102000-0000006E). The additional log record contains more detailed information on the invalid input condition. 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%APPN-3-logdsDS_NEWDSlf9_LOGMSG_04 : DS - FSM(CPolu_parent): state error, lr: %#0.8x row: [dec] col: [dec] inp: %#0.8x
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (FSM) CPolu_parent encountered a state error. This FSM controls the processing of searches for resources relative to the parent node in the request by the node owning the origin LU. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-0000006F) may be created in conjunction with this log record when an invalid input value is received. 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%APPN-3-logdsDS_NEWDSlf9_LOGMSG_05 : DS - FSM(CPolu_parent): invalid action, lr: %#0.8x se_p: %#0.8x inp: %#0.8x action: [dec]
Explanation The DS finite state machine (FSM) CPolu_parent sent an unknown or invalid action value. This FSM controls the processing of searches for resources relative to the parent node in the request by the node owning the origin LU. Probable causes of the error are an invalid input value received because of a programming error in the local node, or the remote node sending an invalid message. Another log record (2F102000-0000006F) may be created in conjunction with this log record when an invalid input value is received. 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.
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%APPN-3-logdsDS_NEWDSlfa_LOGMSG_01 : DS - FSM(NNSolu): Invalid search status in GDS variable x'12C4', value = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x`12C4'.
Recommended Action The DS finite state machine (FSM) NNSolu received a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. This FSM controls the processing of searches for resources by the network node server of the origin LU. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. This error is also logged by the directory services resource registration routines. 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%APPN-3-logdsDS_NEWDSlfa_LOGMSG_02 : DS - FSM(NNSolu): Invalid input. Locate message status is invalid, status = [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) NNSolu received an invalid input locate message. The locate status value is invalid. This FSM controls the processing of searches for resources by the network node server of the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. 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%APPN-3-logdsDS_NEWDSlfa_LOGMSG_03 : DS - FSM(NNSolu): Invalid input. Search event type is invalid, type = [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) NNSolu received an invalid input search event. The search event type is invalid. This FSM controls the processing of searches for resources by the network node server of the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. This error is also logged by the directory services resource registration routines. 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%APPN-3-logdsDS_NEWDSlfa_LOGMSG_04 : DS - FSM(NNSolu): invalid input value = %#0.8x
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) NNSolu received an unexpected or unrecognized input value. This FSM controls the processing of searches for resources by the network node server of the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record may be created in conjunction with this log record (2F102000-00000072 or 2F102000-00000074) that contains more detailed information on the invalid input condition. 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%APPN-3-logdsDS_NEWDSlfa_LOGMSG_05 : DS - FSM(NNSolu): state error, lcb: %#0.8x pcid: %#0.8x%0.8x row: [dec] col: [dec] inp: %#0.8x
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) NNSolu encountered a state error. This FSM controls the processing of searches for resources by the network node server of the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record (2F102000-00000075) may be created in conjunction with this log record when an invalid input value is received. 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%APPN-3-logdsDS_NEWDSlfa_LOGMSG_06 : DS - FSM(NNSolu): Invalid resource location in a directory entry, value = [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (FSM) NNSolu detected an error in the directory database. A resource directory entry is invalid. The resource location indicator in the entry is invalid. This FSM controls the processing of searches for resources by the network node server of the origin LU. There is a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlfa_LOGMSG_07 : DS - FSM(NNSolu): State error. Expected non-explicit (wildcard) locate reply not found
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (FSM) NNSolu encountered a state error. The current state indicates that a nonexplicit (wildcard) locate reply was received for the resource and saved by DS. The saved reply cannot be located using the current search correlator. This FSM controls the processing of searches for resources by the network node server of the origin LU. There is a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlfa_LOGMSG_08 : DS - FSM(NNSolu): Duplicate LU found on search
Explanation Directory services (DS) detected two resources with the same name.
Recommended Action The DS finite state machine (FSM) NNSolu received more than one positive locate reply for the same LU name. This FSM controls the processing of searches for resources by the network node server of the origin LU. Probable causes of the error are a network definition error (two resources are defined with the same name), the remote node sending an invalid message, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlfa_LOGMSG_09 : DS - FSM(NNSolu): invalid action, lcb: %#0.8x se_p: %#0.8x inp: %#0.8x action: [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) NNSolu sent an unknown or invalid action value. This FSM controls the processing of searches for resources by the network node server of the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record (2F102000-00000075) may be created in conjunction with this log record when an invalid input value is received. 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%APPN-3-logdsDS_NEWDSlfb_LOGMSG_01 : DS - FSM(ENolu): Invalid search status in GDS variable x'12C4', value = [dec]
Explanation Directory services (DS) tried to process a search request containing an invalid locate GDS x`12C4'.
Recommended Action The DS finite state machine (FSM) ENolu received a search request containing an invalid LOCATE GDS variable. The search status indicators in the variable are invalid. This FSM controls the processing of searches for resources by the end node owning the origin LU. Probable causes of the error are the remote node sending an invalid message, corrupted data in the directory, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlfb_LOGMSG_02 : DS - FSM(ENolu): Invalid input. Locate message is not a request
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) ENolu child received an invalid input locate message. The locate message is not a locate request, and only locate requests should be processed by this FSM. This FSM controls the processing of searches for resources by the end node owning the origin LU. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlfb_LOGMSG_03 : DS - FSM(ENolu): Invalid input. Search event type is invalid, type = [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) ENolu received an invalid input search event. The search event type is invalid. This FSM controls the processing of searches for resources by the end node owning the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. 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%APPN-3-logdsDS_NEWDSlfb_LOGMSG_04 : DS - FSM(ENolu): invalid input value = %#0.8x
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) ENolu received an unexpected or unrecognized input value. This FSM controls the processing of searches for resources by the end node owning the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record may be created in conjunction with this log record (2F102000-0000007B, 2F102000-0000007C, or 2F102000-0000007D) that contains more detailed information on the invalid input condition. 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%APPN-3-logdsDS_NEWDSlfb_LOGMSG_05 : DS - FSM(ENolu): state error, lcb: %#0.8x pcid: %#0.8x row: [dec] col: [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) ENolu encountered a state error. This FSM controls the processing of searches for resources by the end node owning the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record (2F102000-0000007E) may be created in conjunction with this log record when an invalid input value is received. 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%APPN-3-logdsDS_NEWDSlfb_LOGMSG_06 : DS - FSM(ENolu): Invalid resource location in a directory entry, value = [dec]
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action The DS finite state machine (FSM) ENolu detected an error in the directory database. A resource directory entry is invalid. The resource location indicator in the entry is invalid. This FSM controls the processing of searches for resources by the end node owning the origin LU. There is a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlfb_LOGMSG_07 : DS - FSM(ENolu): Duplicate LU found on search
Explanation Directory services (DS) detected two resources with the same name.
Recommended Action The DS finite state machine (FSM) ENolu received more than one positive locate reply for the same LU name. This FSM controls the processing of searches for resources by the end node owning the origin LU. Probable causes of the error are a network definition error (two resources defined with the same name), the remote node sending an invalid message, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSlfb_LOGMSG_08 : DS - FSM(ENolu): invalid action, lcb: %#0.8x se_p: %#0.8x inp: %#0.8x action: [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action The DS finite state machine (FSM) ENolu sent an unknown or invalid action value. This FSM controls the processing of searches for resources by the end node owning the origin LU. Probable causes of the error are a programming error in the local node or the remote node sending an invalid message. Another log record (2F102000-0000007E) may be created in conjunction with this log record when an invalid input value is received. 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%APPN-3-logdsDS_NEWDSlse_LOGMSG_01 : DS - Search event type is invalid, type = [dec]
Explanation Directory services (DS) encountered a software problem while searching for a resource.
Recommended Action DS detected an invalid search event. The search event type is invalid. Probable causes of the error are a programming error in the local node, or the remote node sending an invalid message. 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%APPN-3-logdsDS_NEWDSr00_LOGMSG_01 : DS - RRmain: Unknown IPS received, IPS = %#0.4x
Explanation Directory services (DS) received an internal interprocess signal (IPS) that it does not recognize or cannot process.
Recommended Action The DS internal data reporting routine received an IPS that it does not recognize or process. 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%APPN-3-logdsDS_NEWDSr10_LOGMSG_01 : DS - Resource Registration Request length error, lu name = [chars]
Explanation Directory services (DS) received an invalid resource registration request from another node.
Recommended Action The received request is either not large enough to contain the required control vectors (X`80' and X`3D') or exceeds the maximum allowed length for a GDS variable. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSr10_LOGMSG_02 : DS - Resource Registration Request received from an invalid session (not CP-CP) adj cp name = [chars], cgid = = [dec], conw_cgid = [dec], conl_gid = [dec]
Explanation Directory services (DS) received an unexpected resource registration request from another node.
Recommended Action DS received a resource registration request from an invalid session. The session from which the received request was received is not one of the CP-CP sessions with the adjacent node. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSr10_LOGMSG_03 : DS - Resource Registration Request is not a REGISTER or a DELETE
Explanation Directory services (DS) received an invalid resource registration request from another node.
Recommended Action DS received an invalid resource registration request. The received request is not a resource registration or registration deletion request. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSr10_LOGMSG_04 : DS - LU name in Resource Registration duplicates non-cached directory entry
Explanation Directory services (DS) detected two resources with the same name.
Recommended Action DS received a resource registration request for an LU that is already defined in the directory. The resource hierarchy (the owning node or network server) of the resource in the directory does not match the resource hierarchy in the received request. Probable causes of the error are a network definition error (two resources are defined with the same name), the remote node sending an invalid message, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSr10_LOGMSG_05 : DS - Resource Type field in cv3c in Resource Registration Request is not ENCP
Explanation Directory services (DS) received an invalid resource registration request from another node.
Recommended Action The type of resource contained in the control vector X`3C' is not an end node (X`00F4' - end node control point name). Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSr10_LOGMSG_06 : DS - Resource Type field in cv3d in Resource Registration Request is not ENCP or LU
Explanation Directory services (DS) received an invalid resource registration request from another node.
Recommended Action The type of resource contained in the control vector X`3D' is not an end node (X`00F4' - end node control point name) or LU (X`00F3' - LU). Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSr20_LOGMSG_01 : DS - Resource Registration Reply received, but adjacent node cb does not exist or is not authorized, lu name = [chars], sense code = [hex]
Explanation Directory services (DS) received an unexpected resource registration reply from another node.
Recommended Action The adjacent node name in the registration reply does not match any adjacent node records in the directory. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSr20_LOGMSG_02 : DS - Resource Registration Reply has an invalid length
Explanation Directory services (DS) received an invalid resource registration reply from another node.
Recommended Action The received reply is either not large enough to contain the required control vectors (X`80' and X`3D') or exceeds the maximum allowed length for a GDS variable. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSr20_LOGMSG_03 : DS - Resource Registration Reply received from an invalid session (not CP-CP), adjacent cp name = [chars], cgid = [dec], conn winner gid = [dec], conn lose gid = [dec]
Explanation Directory services (DS) received an unexpected resource registration reply from another node.
Recommended Action DS received a resource registration reply from an invalid session. The session the received reply was received from is not one of the CP-CP sessions with the adjacent node. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSr20_LOGMSG_04 : DS - Resource Registration Reply is not a REGISTER or DELETE
Explanation Directory services (DS) received an invalid resource registration reply from another node.
Recommended Action DS received an invalid resource registration reply. The received reply is not a resource registration (GDS X`12C3') or registration deletion (GDS X`12C9') reply. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSr20_LOGMSG_05 : DS - First CV in Resource Registration Reply is not cv80
Explanation Directory services (DS) received an invalid resource registration reply from another node.
Recommended Action The first control vector in the received reply is not X`80' (register), or the length of the X`80' control vector is invalid. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSr20_LOGMSG_06 : DS - CV80 is not a REGISTER_REPLY
Explanation Directory services (DS) received an invalid resource registration reply from another node.
Recommended Action The request/reply indicator in the X`80' control vector (register) is invalid. It does not indicate that the received message is a reply. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSr20_LOGMSG_07 : DS - CV80 is not a DELETE_REPLY
Explanation Directory services (DS) received an invalid resource registration reply from another node.
Recommended Action DS received an invalid resource registration reply (type=delete). The request/reply indicator in the X`80' control vector (register) is invalid. It does not indicate that the received message is a reply. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSr20_LOGMSG_08 : DS - CV in Resource Registration Reply is too short
Explanation Directory services (DS) received an invalid resource registration reply from another node.
Recommended Action The length of one or more of the control vectors in the received reply is invalid, or the length of the containing GDS variable is invalid. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSr20_LOGMSG_09 : DS - Resource Registration Reply error: TP failure
Explanation The directory services (DS) resource registration receive transaction program failed.
Recommended Action The transaction program used by DS to receive resource registration replies encountered an error while trying to receive a registration reply. Probable causes of the error are a serious memory shortage, the remote node sending an invalid message, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSr20_LOGMSG_10 : DS - Resource Registration failed for a resource, lu name = [chars], sense code = [hex]
Explanation Registration of a resource with its network node server failed.
Recommended Action The local node's network node server or central directory server rejected a resource registration request from the local node. The sense code indicates why the node rejected the request. Probable causes of the error are a network definition error (the resource being registered is already defined in the network), the remote node encountering an unrecoverable error while processing the request, or the local node sending an invalid registration request. 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%APPN-3-logdsDS_NEWDSr20_LOGMSG_11 : DS - Resource Registration Delete Reply received, not supported
Explanation Directory services (DS) received an invalid resource registration reply from another node.
Recommended Action The reply is to a resource deletion request. The local DS does not send resource deletion requests, so it should never receive a resource deletion reply. Probable causes of the error are the remote node sending an invalid message or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSr20_LOGMSG_12 : DS - Unable to find directory entry for correlator in resource registration negative reply
Explanation Registration of a resource with its network node server failed.
Recommended Action The local node's network node server or central directory server rejected a resource registration request from the local node. DS cannot correlate the resource identified in the reply to any resource defined in the local directory. Probable causes of the error are corrupted data in the directory, a programming error in the local node, or the remote node sending an invalid message. 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%APPN-3-logdsDS_NEWDSs02_LOGMSG_01 : DS - start send_search transaction program failed
Explanation An operating system function failed while trying to start the directory services send_search transaction program.
Recommended Action Directory services could not start the transaction program used to send search requests (locates and CP outage notifications) to adjacent nodes. Probable causes are an operating system error occurring while attempting to start the transaction program (TP) process, one or more missing required files (preventing the creation of the TP process), a serious memory shortage problem, or a programming error in the local node. 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%APPN-3-logdsDS_NEWDSs02_LOGMSG_02 : DS - start en_rsc_registration transaction program failed
Explanation An operating system function failed while trying to start the directory services en_rsc_registration transaction program.
Recommended Action Directory services could not start the transaction program used to send resource registration requests to the node's network node server and central directory server. Probable causes are an operating system error occurring while attempting to start the transaction program (TP) process, one or more missing required files (preventing the creation of the TP process), a serious memory shortage problem, or a programming error in the local node. 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%APPN-3-logdsInvalid_LR : DS - Invalid locate record detected
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action There is an internal code problem in the DS component. A invalid locate record was encountered. One or more of the fields in the record are invalid. Probable causes of the error are corrupted data in the directory or a programming error in the local node. 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%APPN-3-logdsLR_CP_NAME : DS - DBset_lr_cp_name invoked
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action There is an internal code problem in the DS component. An invalid internal function was invoked. The internal routine DBset_lr_cp_name() is no longer valid and should not be invoked by directory services. There is a programming error in the local node. 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%APPN-3-logdsLR_FQPCID : DS - DBset_lr_fqpcid invoked
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action There is an internal code problem in the DS component. An invalid internal function was invoked. The internal routine DBset_lr_fqpcid() is no longer valid and should not be invoked by directory services. There is a programming error in the local node. 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%APPN-3-logdsLR_PCID_modifier : DS - DBset_lr_PCID_modifier invoked
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action There is an internal code problem in the DS component. The internal routine DBset_lr_PCID_modifier() is no longer valid and should not be invoked by directory services. There is a programming error in the local node. 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%APPN-3-logdsLR_SEARCH_NUM : DS - DBset_lr_search_num invoked
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action There is an internal code problem in the DS component. The internal routine DBset_lr_search_num() is no longer valid and should not be invoked by directory services. There is a programming error in the local node. 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%APPN-3-logdsLR_SEARCH_ROLE : DS - DBset_lr_search_role invoked
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action There is an internal code problem in the DS component. An invalid internal function was invoked. The internal routine DBset_lr_search_role() is no longer valid and should not be invoked by directory services. There is a programming error in the local node. 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%APPN-3-logdsNULLPOINTER : DS - NULL POINTER
Explanation Directory services (DS) encountered an unexpected condition.
Recommended Action There is an internal code problem in the DS component. The pointer to a required control block or data structure is NULL. The NULL pointer could be a value returned from a directory services function or a pointer contained in an internal DS control block. Probable causes of this error are corrupted data in the directory or a programming error in the local node. 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%APPN-3-loghpcFRR : HPC Process entered FRR
Explanation A hardware or software error 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%APPN-3-loghpcHASM_DEQD_UNKWN_MU : HPC Process dequeued an unknown MU
Explanation The high-performance routing address space manager (HPR ASM) received an SNA message (MU) that it does not recognize or cannot process.
Recommended Action HPR ASM processes only session messages (such as BIND and UNBIND). There is an internal code 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%APPN-3-loghpcHASM_DEQD_UNKWN_Q : HPC Process dequeued from an unknown Q
Explanation A high-performance routing address space manager (HPR ASM) received an interprocess signal (IPS) via an unrecognized process queue.
Recommended Action There is an internal code 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%APPN-3-loghpcHPC_ALERT : HPC Process sending an Alert to MS
Explanation High-performance routing (HPR) path control generated an alert.
Recommended Action The HPR path control, address space manager, or session connector detected an alert condition and sent the formatted SNA alert to MS for transmission to its alert focal point. 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%APPN-3-loghpcHPC_BAD_FSM_RR_COMBO : HPC Bad FSM receive router combination
Explanation An instance of high-performance routing path control (HPR PC) received an SNA message that it does not recognize or cannot process.
Recommended Action The HPR path control receive router FSM sent an unknown or invalid action code. Probable causes of this error are an invalid message was received or a message was received out of sequence. There is an internal code 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%APPN-3-loghpcHPC_DEQD_UNKWN_IPS : HPC dequeued an unknown IPS
Explanation The high-performance routing address space manager (HPR ASM) or an instance of HPR path control received an internal interprocess signal that it does not recognize or cannot process.
Recommended Action There is an internal code 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%APPN-3-loghpcHPC_DEQD_UNKWN_MU : HPC dequeue unknown MU
Explanation The high-performance routing path control (HPR PC) received an SNA message (MU) that it does not recognize or cannot process.
Recommended Action There is an internal code 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%APPN-3-loghpcHPC_DEQD_UNKWN_RQ : HPC Process dequeued an unknown RU request code
Explanation A hardware or software error 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%APPN-3-loghpcHPC_DEQD_UNKWN_RQ_1STSG : HPC dequeued an unknown RU request code in the first segment
Explanation The high-performance routing path control (HPR PC) received an SNA message (MU) that it does not recognize or cannot process.
Recommended Action The received message is the first segment in a multisegmented message. There is an internal code 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%APPN-3-loghpcHPC_DEQD_UNKWN_RQ_LSTSG : HPC dequeued an unknown RU request code in the last segment
Explanation The high-performance routing path control (HRP PC) received an SNA message (MU) that it does not recognize or cannot process.
Recommended Action The received message is the last segment in a multisegmented message. The request code was obtained from the first segment. 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%APPN-3-loghpcHPC_DEQD_UNKWN_RQ_MIDSG : HPC dequeued an unknown RU request code in the middle segment
Explanation The high-performance routing path control (HPR PC) received an SNA message (MU) that it does not recognize or cannot process.
Recommended Action The received message is a middle segment in a multisegmented message. The request code was obtained from the first segment. 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%APPN-3-loghpcHPC_DEQD_UNKWN_RQ_ONYSG : HPC dequeued an unknown RU request code in the only segment
Explanation The high-performance routing path control (HPR PC) received an SNA message (MU) that it does not recognize or cannot process.
Recommended Action The received message is a single-segment message. There is an internal code 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%APPN-3-loghpcHPC_DQD_UNK_RTP_IPS : HPC dequeued unknown RTP IPS
Explanation An instance of high-performance routing path control (HPR PC) received an invalid IPS message from a DLC or rapid transport protocol (RTP).
Recommended Action The received IPS was a DLC message not recognized or supported by HPR path control. There is an internal code 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%APPN-3-loghpcHPC_MU_ERR_CHK_FAILED : HPC MU error checker failed
Explanation An instance of high-performance routing path control (HPR PC) received an SNA message (MU) that contains SNA headers whose TH or RH settings are invalid.
Recommended Action HPR path control received an invalid SNA message from another node. The received message did not pass the basic SNA message verification checks (validating TH and RH settings). Probable causes of this error are the remote node sending an invalid message, a programming error in the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-loghpcHPC_SC_CANT_GET_SC_CB : HPC SC can't get SC CB
Explanation A high-performance routing session connector (HPR SC) received an internal interprocess signal, but cannot find the control blocks associated with the session connector.
Recommended Action The HPR path control/session connector main process received an interprocess signal that it cannot route. The logical process identified in the signal is a session connector using HPR, but the process-specific control blocks cannot be located. There is an internal code 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%APPN-3-loghpcHPC_SC_DQD_UNK_IPS : HPC SC dequeued unknown IPS
Explanation The high-performance routing path control (HPR PC) received an internal interprocess signal that it does not recognize or cannot process.
Recommended Action There is an internal code 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%APPN-3-loghsINVALID_MASK_GEN : Invalid Jump Table Mask Generated, hs lpid = [hex], mask = [hex]
Explanation A half-session (HS) cannot parse the SNA request header in an SNA message.
Recommended Action A half-session for an LU could not compute an internal hash value from the SNA request header contained in an SNA message. The SNA message can either be an outbound message being sent by the local node or an inbound message received from a remote node. Probable causes of this error are a programming error in the local node or the remote node sending an invalid message. 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%APPN-3-loghsPROTOCOL_ERROR_IN_DFC : Session level protocol error detected, hs lpid = [hex], sense code = [hex]
Explanation An SNA protocol error was detected while half-session (HS) (data flow control) was processing a message.
Recommended Action Half-session detected an SNA protocol error while processing a message. The message did not pass one or more of the SNA protocol checks (send or receive checks). The sense code identifies the actual SNA protocol error. Probable causes of this error are the remote node sending an invalid message, the local transaction program or SNA component sending an invalid message, a programming error in the local node, a software problem in the node that sent the message, or incompatible APPC/APPN support in the remote node (with the local APPC/APPN support). 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%APPN-3-loghsUNKNOWN_IPS_RCVD : Unknown IPS Received, hs lpid = [hex], ips name = [hex]
Explanation A half-session (HS) for an LU received an internal interprocess signal it does not recognize or cannot process.
Recommended Action There is an internal code 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%APPN-3-logmsASSIGN_PCID_FAILED : MS: Assign PCID failed, rc = [hex]
Explanation Management services (MS) encountered an unrecoverable error.
Recommended Action Management services encountered an error trying to obtain the local node's procedure correlator identifier (PCID) value from session services. Probable causes of this error are a system function failure (preventing the transmission of the internal message), a serious memory shortage, or an internal code 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%APPN-3-logmsCSWMSAPI_LOGMSG_01 : MSAPI: PQENQ FP information to APPL PID failed, application pid = [hex]
Explanation Management services (MS) encountered a problem trying to send a message to a management services application.
Recommended Action MS had new information regarding the focal point of a specific MS category. MS tried to inform all applications in this category of the change. The request to send the MS message (PQenq) failed. Probable causes of this error are an operating system error occurring while attempting to send the message, a serious memory shortage, or a programming error in the local node. 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%APPN-3-logmsCSWMSAPL_LOGMSG_01 : MSAPL: Same APPL name with different PIDS encountered, appl name = [chars], pid = [hex], application entry pid = [hex]
Explanation Management services (MS) received duplicate application registration requests.
Recommended Action The application name in the registration request has already been registered before with a different process ID. Probable causes of this error are the MS application starting multiple times, two different applications using the same application name, or the application ending, restarting, and trying to reregister with a new PID. 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%APPN-3-logmsCSWMSAPL_LOGMSG_02 : MSAPL: APPL name not found, appl name = [chars].
Explanation Management services (MS) encountered a problem while updating the MS application list.
Recommended Action MS could not find the MS application name in the application list while trying to delete the application from the list or to increase the counters associated with the application. 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%APPN-3-logmsCSWMSAPS_BAD_DEST_APPL : MSAPS: Invalid destination APPL name, dest_fq_cp_name = [chars], origin_appl = [chars], dest_appl = [chars], seq_no = [hex], pid = [hex]
Explanation Management services (MS) encountered a problem trying to send a message.
Recommended Action The request did not specify a valid destination MS application name. The application name was either not specified or the specified name was longer than eight characters. Probable causes of this error are the originator of the MDS message specifying an incorrect destination or a programming error in the local node. 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%APPN-3-logmsCSWMSAPS_BAD_DEST_CP : MSAPS: Invalid fully qualified destination CP name, dest_fq_cp_name = [chars], origin_appl = [chars], dest_appl = [chars], seq_no = [hex]
Explanation Management services (MS) encountered a problem trying to send a message.
Recommended Action The request did not specify a valid network-qualified destination control point name. Probable causes of this error are the originator of the MDS message specifying an incorrect destination or a programming error in the local node. 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%APPN-3-logmsCSWMSAPS_BAD_ORIG_APPL : MSAPS: Invalid original APPL name, dest_fq_cp_name = [chars], origin_appl = [chars], dest_appl = [chars], seq_no = [hex]
Explanation Management services (MS) encountered a problem trying to send a message.
Recommended Action The request did not specify a valid origin MS application name. The application name was either not specified or the specified name was longer than eight characters. Probable causes of this error are the originator of the MDS message specifying an incorrect destination or a programming error in the local node. 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%APPN-3-logmsCSWMSAPS_TP_APPL_FAILED : MSAPS: Sending error message TP failed, origin_appl = [chars], pid = [hex], seq_no = [hex]
Explanation Management services (MS) encountered a problem trying to send a message.
Recommended Action The request did not specify a valid origin MS application name. The application name was either not specified or the specified name was longer than eight characters. Probable causes of this error are the originator of the MDS message specifying an incorrect destination, an operating system error occurring while attempting to send the error message, a serious memory shortage, or a programming error in the local node. 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%APPN-3-logmsCSWMSCAP_LOGMSG_01 : MSCAP: cannot process received MS capability
Explanation Management services (MS) does not recognize a subvector contained in a received MS capabilities message (x`80F0' major vector).
Recommended Action The received MS capabilities message contains one or more control vectors not recognized by management services. Probable causes of this error are the message containing subvectors used only by MS focal points, the remote node sending an invalid message, or a programming error in the local node. Unless a network configuration error exists, there is probably a software problem in the node that sent the message or the APPC/APPN support in the remote node is incompatible with the local APPC/APPN support. 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%APPN-3-logmsCSWMSCAP_LOGMSG_02 : MSCAP: Trying to build unknown MS CAP
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS detected an error while processing a request to build and send an MS capabilities message. The request specified an invalid MS capabilities message type. 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%APPN-3-logmsCSWMSCAT_LOGMSG_01 : MSCAT: CACHED_MSG not found from UOW
Explanation Management services (MS) encountered a problem trying to correlate a received MS error message (SNA condition report, or SNACR) with an outstanding MS request.
Recommended Action The error message indicates that the focal point was lost. MS is trying to locate the originating message so it can be forwarded to a backup focal point. The unit-of-work correlator in the received error message does not match that of any outstanding MS request. Probable causes of this error are the message is a reply to a request that has been discarded by MS (only so many outstanding requests are held by MS), the remote node sent an invalid message, there is a programming error in the local node, there is a software problem in the node that sent the message, or the APPC/APPN support in the remote node is not compatible with the local APPC/APPN support. Note that this log event can also be created during normal node initialization. During local node initialization, MS may try to send an entry point authorization request (x`63') to reacquire its focal points before the connections to the focal point are active. The send request fails, and there are no cached messages, so this error is logged. If this log event is logged during node initialization, no specific action is required. MS will retry acquiring its focal point later. Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logmsCSWMSCAT_LOGMSG_02 : MSCAT: MS_TRANSPORT not marked by UOW
Explanation Management services (MS) encountered a problem trying to correlate a received MS error message (SNA condition report, or SNACR) with an outstanding MS capabilities request.
Recommended Action The error message indicates that the focal point was lost. MS is trying to locate the originating message so it can be forwarded to a backup focal point. The unit-of-work correlator in the received error message does not match that of any outstanding MS request. There is programming error in the local node. The unit-of-work is logged in a related log record (2F103000-00000035). 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%APPN-3-logmsCSWMSRAP_LOGMSG_01 : MSRAP: Error trying to register as FP, pid = [hex]
Explanation Management services (MS) MS_CAPS received an application request to be registered as a focal point.
Recommended Action An MS application has requested to register itself as a focal point application. This function is not supported, so the request is ignored. Probable causes of this error are a user trying to start a focal point application on this node, or a non-FP application falsely identifying itself as a focal point application. 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%APPN-3-logmsCSWMSRAP_LOGMSG_02 : MSRAP: Error trying to register with duplicate PID, pid = [hex]
Explanation Management services (MS) received duplicate application registration requests.
Recommended Action The application name in the registration request has already been registered with a different process Probable causes of this error are the MS application starting multiple times, two different applications using the same application name, or the application ending, starting and trying to reregister with a new PID. 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%APPN-3-logmsCSWMSRAP_LOGMSG_03 : MSRAP: Send registration response to APPL failed, application name = [chars]
Explanation Management services (MS) could not send the results of a registration request back to the MS application.
Recommended Action Probable causes of this error are a system function failure (preventing the transmission of the internal message), or a serious memory shortage. 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%APPN-3-logmsCSWMSRAP_LOGMSG_04 : MSRAP: APPL name not found for de-registration, application name = [chars]
Explanation Management services (MS) encountered a problem while processing a deregistration request from an application.
Recommended Action MS could not find the MS application name in the list of active MS applications. Probable causes of this error are the application not registering itself, the application specifying an incorrect name on the deregistration request, or a software 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%APPN-3-logmsCSWMSRAP_LOGMSG_05 : MSRAP: APPL name not found for deletion, application name = [chars]
Explanation Management services (MS) encountered a problem while updating the MS application list.
Recommended Action MS could not find the MS application name in the application list while attempting to remove the application from the list. 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%APPN-3-logmsCSWMSRBM_LOGMSG_01 : MSRBM: GDS_CP_MSU not found by set_held_alert_flag_on
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS could not find the CP-MSU GDS variable when trying to send out a queued alert message to the focal point. Management Services has established a new focal-point/entry-point relationship and was trying to resend the queued messages, but the message did not contain a valid CP-MSU. 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%APPN-3-logmsCSWMSRBM_LOGMSG_02 : MSRBM: GDS_CP_MSU not found by set_buffered_flag_on
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS could not find the CP-MSU GDS variable when trying to send out a queued alert message to the focal point. Management Services has established a new focal-point/entry-point relationship and was trying to resend the queued messages, but the message did not contain a valid CP-MSU. 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%APPN-3-logmsCSWMSUTL_LOGMSG_01 : MSUTL: Time not found from UOW
Explanation Management services received an invalid MS message.
Recommended Action MS could not locate the time stamp subvector (x`02') in the received unit-of-work correlator. Probable causes of this error are the message containing an invalid unit-of-work correlator, the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logmsCSWMSUTL_LOGMSG_02 : MSUTL: Cannot find CP_MSU from GDS DATA
Explanation Management services (MS) detected an error while trying to parse a received MS error message.
Recommended Action MS detected a serious error in an MS error message being sent to a local MS application. The message is an SNA condition report (SNACR), but the message does not contain a valid CP-MSU GDS variable (x`1212'). The sense code identifying the error that generated the message cannot be located. Probable causes of this error are the originator of the MDS message not formatting the message correctly or an internal code 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%APPN-3-logmsCSWMSUTL_LOGMSG_03 : MSUTL: Cannot parse CP_MSU from GDS DATA
Explanation Management services (MS) detected an error while trying to parse a received MS error message.
Recommended Action MS detected a serious error in an MS error message being sent to a local MS application. The message is an SNA condition report (SNACR), but the message does not contain a valid CP-MSU GDS variable (x`1212'). The sense code identifying the error that generated the message cannot be located. Probable causes of this error are the originator of the MDS message not formatting the message correctly or an internal code 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%APPN-3-logmsCSWMSUTL_LOGMSG_04 : MSUTL: Cannot find SNA_REPORT_CODE SV from SNACR GDS DATA
Explanation Management services (MS) detected an error while trying to parse a received MS error message.
Recommended Action MS detected a serious error in an MS error message being sent to a local MS application. The message is an SNA condition report (SNACR), but the CP-MSU GDS variable in the received message does not contain a SNA report code subvector (x`7D'). The sense code identifying the error that generated the message cannot be located. Probable causes of this error are the originator of the MDS message not formatting the message correctly or an internal code 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%APPN-3-logmsDISPLAY_CONSOLE_BUFFER : MS: Displaying console buffer
Explanation Management services (MS) detected an error while trying to parse a received error message.
Recommended Action This log record is created along with other log records to identify the type of error that was detected by MS. Refer to the related log entries and messages for more information and other recommended actions.
Error Message%APPN-6-LogMsg : [chars]
Explanation A hardware or software error 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%APPN-3-logmsMDS_MU_ERROR : MS: MDS_MU received with error, sense_data = [hex]
Explanation Management services (MS) encountered an error processing a received MS message.
Recommended Action This log record is created along with other log records to identify the type of error that was detected by MS. Refer to the related log entries and messages for more information and other recommended actions.
Error Message%APPN-3-logmsPQENQ_FAILED : MS: PQenq failed, pid = [hex]
Explanation Management services (MS) encountered a problem while trying to send a message to a management services application program.
Recommended Action The request to send the MS message (PQenq) failed. Probable causes of this error are an operating system error occurring while attempting to send the message, a serious memory shortage, or a programming error in the local node. 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%APPN-3-logmsPQENQ_FAILED_ABEND : MS: PQenq FAILED, MS ABENDING
Explanation Management services (MS) could not send a request to another node component.
Recommended Action MS sends requests to directory services to search for destination nodes (that is LOCATE messages) and the control point's resource manager to start one of the MS service transaction programs. Probable causes of this error are a system function failure occurring (preventing the transmission of the internal message), a serious memory shortage, or an internal code 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%APPN-3-logmsSVKEY_NOT_FOUND : MSSVL: Subvector key not found, key = [hex]
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS detected an error while parsing an MDS message. This error could occur while processing a message received from another node or while building a message to send to another node. The message does not contain an expected or required subvector. For inbound messages, probable causes of this error are the remote node sending an invalid message, a programming error in the local node, a software problem (probably in the node that sent the message), or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. For outbound messages, the probable cause is an internal code 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%APPN-3-logmsSVLIST_EMPTY : MSSVL: SV LIST empty
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS detected an error while parsing an MDS message. This error could occur while processing a message received from another node or while building a message to send to another node. The message does not contain an expected or required subvector. For inbound messages, the probable causes of this error are the remote node sending an invalid message, a programming error on the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. For outbound messages, the probable cause is an internal code 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%APPN-3-logmsUNKNOWN_ALERT : Processing an unknown ALERT, storage in signal queue is lost, id = [hex], sender_name = [chars], failing_module = [chars], detecting_module = [chars]
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS detected an error while processing a request to build and send an alert. The request specified an unrecognized alert ID. 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%APPN-3-logmsUNKNOWN_CAP : Processing an unknown CAP
Explanation Management services (MS) does not recognize a subvector contained in a received MS capabilities message (x`80F0' major vector).
Recommended Action The received MS capabilities message contains one or more control vectors not recognized by management services. Probable causes of this error are the message containing subvectors used only by MS focal points, the remote node sending an invalid message, or a programming error in the local node. Unless a network configuration error exists, there is probably a software problem in the node that sent the message or the APPC/APPN support in the remote node is incompatible with the local APPC/APPN support. 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%APPN-3-logmsUNKNOWN_GDS : Processing an unknown GDS, gds key = [hex]
Explanation Management services (MS) does not recognize a message received from another node.
Recommended Action The local node does not recognize the GDS variable contained in a message. The only MS capabilities messages processed by the local node are CP-MSU (control point management services units), MS capabilities messages, and SNACRs (SNA condition reports). Probable causes of this error are the remote node sending an invalid message, a programming error in the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logmsUNKNOWN_ID_FOR_ALERT : MS: Unknown ID for alert, id = [hex]
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS detected an error while processing a request to build and send an alert. The request specified an unrecognized alert ID. 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%APPN-3-logmsXID_NO_DATA : MS: xid_psid_sv_p passed by CS has no data
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS detected an error while processing a request to build and send an alert from configuration services. The alert request received from configuration services (CS) does not contain any product set ID information. MS expects CS to insert the product set ID from the XID being processed when the error occurred in the generated alert. 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%APPN-3-logmsXID_NULL : MSP79: xid_psid_sv_p passed by CS = NULL
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS detected an error while processing a request to build and send an alert from configuration services. The alert request received from configuration services (CS) does not contain any product set ID information. MS expects CS to insert the product set ID from the XID being processed when the error occurred in the generated alert. 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%APPN-3-logmsXXXMSP03_LOGMSG_01 : MSP03: Unknown local node type encountered, node_type = [hex]
Explanation Management services (MS) encountered an error while processing an interprocess signal.
Recommended Action MS received a CP_STATUS signal from session services (SS) for a network node, but the local node type indicator is invalid. 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%APPN-3-logmsXXXMSP03_LOGMSG_02 : MSP03: CP status for EN-EN session
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS received an unexpected CP_STATUS signal from session services (SS). The local node is an end node, and the CP_STATUS update is for an adjacent end node. 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%APPN-3-logmsXXXMSP03_LOGMSG_03 : MSP03: Misdefined as network node
Explanation Management services (MS) encountered an error while processing an interprocess signal.
Recommended Action MS received an unexpected CP_STATUS signal from session services (SS). The local node is an end node, and the CP_STATUS update is for an adjacent end node. 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%APPN-3-logmsXXXMSP03_LOGMSG_04 : MSP03: Misdefined as virtual node
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS received an unexpected CP_STATUS signal from session services (SS). The CP_STATUS update is for a virtual node (connection network). 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%APPN-3-logmsXXXMSP03_LOGMSG_05 : MSP03: CP status received from unknown node type, node_type = [hex]
Explanation Management services (MS) encountered an error while processing an interprocess signal.
Recommended Action MS received an unexpected CP_STATUS signal from session services (SS). The local node is an end node, and the CP_STATUS update is for an adjacent end node. 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%APPN-3-logmsXXXMSP04_LOGMSG_01 : MSP04: EN received data from another node
Explanation Management services (MS) received an unexpected MS message.
Recommended Action MS received an MS message in which the local node is not the final destination. This should not occur because the local node is an end node. The message must have been routed incorrectly. The only time end nodes should receive MS messages is when they are the final destination. Probable causes of this error are the remote node believing the local node is a network node, the remote node sending an invalid message, a programming error in the local node, a network configuration error, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logmsXXXMSP04_LOGMSG_02 : MSP04: Tried to use specified LU name for ISR, partner_lu_name = [chars]
Explanation Management services (MS) received an unexpected MS message.
Recommended Action MS received an MS message from an adjacent node via the CP-CP sessions set up with that node. The adjacent node is not an end node served by the local node, which is a network node. This should not occur, because the only time network nodes should receive MS messages via CP-CP sessions is from their served end nodes. The message must have been routed incorrectly. Probable causes of this error are the remote node believing the local node is its serving network node, the remote node sending the message over an invalid session, a programming error in the local node, a network configuration error, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logmsXXXMSP04_LOGMSG_03 : MSP04: Tried to send to this node, partner_lu_name = [chars], destination_name = [chars]
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS received an MS message from an adjacent node via a SNASVCMG session set up with that node. The destination of the message is not the local node or one of the end nodes served by the local node. This should not occur, because the only time network nodes should receive MS messages via CP-CP sessions is from their served end nodes. The message must have been routed incorrectly. Probable causes of this error are the remote node believing the local node is its serving network node, the remote node sending the message over an invalid session, a programming error in the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logmsXXXMSP04_LOGMSG_04 : MSP04: Destination application not recognized, rc = [hex]
Explanation Management services (MS) received an MS message for an unrecognized MS application.
Recommended Action MS received an MS message it could not route locally. The destination MS application name is not recognized by management services. That is, it is not EP_ALERT, MS_CAPS, or any of the other registered MS applications. Probable causes of this error are the originator of the MDS message specifying the wrong MS application name, the destination application not registering with MS or deregistering before the message was received, the remote node sending an invalid message, a programming error in the local node, a software problem probably in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logmsXXXMSP09_LOGMSG_01 : MSP09: NN information routed to EN, node_type = [hex]
Explanation Management services (MS) received an unexpected MS message.
Recommended Action MS received an MS error message rejecting a message sent by the local node. The remote network node that received the MS message does not serve the intended destination end node, and it is not the intended destination either. Normally, if the local node is a network node, it recomputes the route and resends the message, assuming that the network information it used to send the original message is out of date. However, because the local node is an end node, the message is ignored and an alert is generated. The original message or the error message must have been routed incorrectly. Probable causes of this error are the local node sending the original message over an invalid session, the remote node sending the message over an invalid session, a programming error in the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logmsXXXMSP12_LOGMSG_01 : MSP12: Should not have received MS Caps 62, dest_appl = [chars]
Explanation Management services (MS) received an unexpected MS message.
Recommended Action MS received an invalid MS capabilities message from an MS migration node. The MS capabilities message was a focal point authorization reply (x`62'). Probable causes of this error are the remote node sending an invalid message, a programming error in the local node, a software problem probably in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logmsXXXMSP12_LOGMSG_02 : MSP12: ATL not found for 0x64. This should not happen
Explanation Management services (MS) received an unexpected MS message.
Recommended Action MS received an unexpected MS capabilities message from a MS migration node. The MS capabilities message was an entry point authorization reply (x`64'), but the reply could not be correlated with an outstanding entry point authorization request (x`63) for that node. The reply could not be correlated with any outstanding request. Probable causes of this error are the remote node sending an invalid message, a programming error in the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logmsXXXMSP12_LOGMSG_03 : MSP12: Unknown MS Caps SV received, sv_key = [hex]
Explanation Management services (MS) received an invalid MS message.
Recommended Action MS received an unexpected MS capabilities message from a MS migration node. The type of message was not recognized by the local node. The local node only processes focal point authorization requests (x`61') or entry point authorization replies (x`64) from MS migration nodes. Probable causes of this error are the remote node sending an invalid message, a programming error in the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logmsXXXMSP12_LOGMSG_04 : MSP12: Missing MS Caps SV. This should not happen, key = %lx
Explanation Management services (MS) received an invalid MS message from an MS migration node.
Recommended Action MS received an invalid MS message from a MS migration node. The message was not an alert (major vector x`0000') MS capabilities (major vector x`80F0') message. Probable causes of this error are the remote node sending an invalid message, a programming error in the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logmsXXXMSP12_LOGMSG_05 : MSP12: Non CP_MSU received. This should not happen, cp_msu = %lx
Explanation Management services (MS) received an invalid MS message from an MS migration node.
Recommended Action MS received an invalid MS message from an MS migration node. The message was not a CP-MSU (GDS variable x`1212'). Probable causes of this error are the remote node sending an invalid message, a programming error in the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logmsXXXMSP16_LOGMSG_02 : MSP16: Bad response code from start_tp, response_code = [hex]
Explanation Management services (MS) encountered a problem trying to start a management services service transaction program.
Recommended Action The control point resource manager replied to the request to start the transaction program (TP) with an error code. The service transaction program is not started. Probable causes of this error are an operating system error occurring while attempting to start the TP process, one or more missing required files (preventing the creation of the TP process), a serious memory shortage, or a programming error in the local node. 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%APPN-3-logmsXXXMSP16_LOGMSG_03 : MSP16: Pcreate failed, returned pid = [hex]
Explanation Management services (MS) encountered a problem trying to start a management services service transaction program.
Recommended Action The request to start the service transaction program (Pcreate) failed. Probable causes of this error are an operating system error occurring while attempting to start the transaction program (TP) process, one or more missing required files (preventing the creation of the TP process), a serious memory shortage, or a programming error in the local node. 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%APPN-3-logmsXXXMSP17_LOGMSG_01 : MSP17: PQENQ failed to SS. MS abending
Explanation Management services (MS) could not send an internal request (IPS) to session services.
Recommended Action The function PQenq failed. Probable causes of this error are a system function failure occurring (preventing the transmission of the internal message), a serious memory shortage, or an internal code 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%APPN-3-logmsXXXMSP18_LOGMSG_01 : MSP18: No MDS_CTL, verification bit not set
Explanation Management services (MS) encountered an unexpected condition.
Recommended Action MS could not set the verification flag in the MDS routing information portion of a MS message. The MS message being processed is missing either the MDS routing GDS variable (x`1311') or the MDS control subvector (x`90') within the MDS routing variable. The MS message is invalid. For inbound messages, probable causes of this error are the remote node sending an invalid message, a programming error in the local node, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. For outbound messages, the probable cause is an internal code 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%APPN-3-logmsXXXMSP19_LOGMSG_01 : MSP19: Message to migration node, but dest APPL is not ALERT NETOP nor MS CAPS
Explanation Management services (MS) MDS router received an incorrectly routed message.
Recommended Action MS tried to send an MDS message to a MS migration node, but the destination MS application name is not the alert focal point (ALERT_NETOP) or the MS capabilities application (MS_CAPS). Those two MS applications are the only two applications supported in an MS migration node. Probable causes of this error are the originator of the MDS message specifying the wrong MS application name, the remote node sending an invalid message, or a programming error in the local node. Unless an application in the local node specified an invalid destination application, there is probably a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logmsXXXMSP19_LOGMSG_02 : MSP19: PQenq to tp failed, ms_transport tossed
Explanation Management services (MS) encountered a problem trying to send a message to a management services service transaction program.
Recommended Action The request to send the MS message (PQenq) failed. Probable causes of this error are an operating system error occurring while attempting to send the message, a serious memory shortage, or a programming error in the local node. 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%APPN-3-logmsXXXMSP23_LOGMSG_01 : MSP23: Destination nau name not located, destination nau name = [chars]
Explanation Management services (MS) detected an error while trying to send an MS message.
Recommended Action The local node cannot find the destination (LU or control point) specified in the MS message. The search of the APPN network for the destination failed. Probable causes of this error are the originator of the MDS message specifying the wrong destination LU, the remote node owning the destination LU not currently being available, or a programming error in the local node. 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%APPN-3-logmsXXXMSP29_LOGMSG_01 : MSP29: Message to unknown APPL name
Explanation Management services (MS) detected an error while trying to send an MS message to a local MS application.
Recommended Action The destination application name specified in the MS message is not registered with the local node. The destination LU is owned by the local node, but the specified MS application is not active. Probable causes of this error are the destination application not being started, the destination application not registering itself, the originator of the MDS message specifying the wrong destination LU, or an internal code 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%APPN-3-logmsXXXMSP29_LOGMSG_02 : MDP29: No sense code in the error message to APPL, message discarded
Explanation Management services (MS) detected an error while trying to send an MS message to a local MS application.
Recommended Action MS detected a serious error in an MS error message being sent to a local MS application. The message is an SNA condition report (SNACR), but the message does not specify a sense code. All SNACRs must contain a sense code identifying the error being reported. Probable causes of this error are the originator of the MDS message not formatting the message correctly or an internal code 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%APPN-3-logmsXXXMSP70_LOGMSG_01 : MSP70: Received invalid major vector, vector = [int]
Explanation Management services (MS) encountered a problem trying to send an alert.
Recommended Action The size of the alert (the alert major vector) in the message is too small or too large. There is a programming error in the local node. 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%APPN-3-lognofASM_ID_NOT_FOUND : NOF unable to find ASM process ID in recovered subsystem ssid, ssid = [chars]
Explanation Node operator facility (NOF) could not find the address space manager (ASM) process in a recovered subsystem.
Recommended Action NOF is in the process of restarting a recovered subsystem (coprocessor). NOF could not locate the ASM process in the recovered subsystem, so it cannot load the subsystem with the list of NAUs (control point and LUs) defined locally to the APPN node. Probable causes of this error are the ASM in the recovered subsystem not starting or an internal code 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%APPN-3-lognofBAD_SUBSYSTEM_STATE : NOF received SS_AVAILABLE - subsytem is in an incompatible state, ssid_number = [hex], status_1 = [hex], state = [hex]
Explanation Node operator facility (NOF) received a notification IPS (SS_AVAILABLE) that contains unexpected data.
Recommended Action The notification was sent to inform NOF that an environment manager process (probably in an attached coprocessor) that ended has been restarted. The status indicators in the notification indicate that the subsystem is not loaded, or that the subsystem is loaded and the node is operational and available. There is an internal code 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%APPN-3-lognofCANT_CREATE_PROCESS : NOF could not create a node process in a subsystem, process_name = [chars], ss_id = [chars]
Explanation A surrogate NOF process in an attached coprocessor could not create a local process in the attached subsystem (coprocessor).
Recommended Action The function Pcreate failed. Probable causes of this error are a system function failure occurring (preventing the creation of the node process), a serious memory shortage, or an internal code 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%APPN-3-lognofCANT_MAKE_PROC_ON_SSID : NOF could not create environment in a subsystem, ss_id name = [chars]
Explanation The node operator facility (NOF) process in the control point could not create the environment manager process in an attached subsystem (coprocessor).
Recommended Action Probable causes of this error are a system function failure (preventing the creation of environment manager), one or more missing required files (preventing the creation of environment manager), a serious memory shortage, or an internal code 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%APPN-3-lognofCANT_SEND_RQST_CREATE : Could not send REQUEST_CREATE message
Explanation The main node operator facility (NOF) process in the APPN node control point cannot send a process create message to the surrogate NOF in an attached coprocessor.
Recommended Action The command to send the creation request (REQUEST_CREATE IPS message) to the surrogate NOF process (PIM) in the coprocessor failed. The function PQenq failed. Probable causes of this error are a system function failure occurring (preventing the activation of the surrogate NOF process in the attached coprocessor), an error sending the IPS message to the surrogate NOF process, a serious memory shortage, or an internal code 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%APPN-3-lognofCOULD_NOT_CREATE_PROC : NOF could not create a node process, process name = [chars]
Explanation The main node operator facility (NOF) process in the APPN control point could not create a local process in the control point processor.
Recommended Action The function Pcreate failed. Probable causes of this error are a system function failure (preventing the creation of the node process), a serious memory shortage, or an internal code 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%APPN-3-lognofDATA_DUMP : NOF - Additional data for previous event
Explanation A hardware or software error 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%APPN-3-lognofDLC_NAME_ACTV_VCB : Required dlc_name not found in ACTIVATE_DLC VCB
Explanation Node operator facility (NOF) rejected an ACTIVATE_DLC verb because the DLC name in the verb (dlc_name) was not specified.
Recommended Action The ACTIVATE_DLC verb is rejected, so the specified data-link control is not started. Reissue the verb with correct values. If the error occurred while loading the initial network configuration or while processing the network definition file, correct the error in the file and reload the configuration.
Error Message%APPN-3-lognofDLC_NAME_DEACTV_VCB : Required dlc_name not found in DEACTIVATE_DLC VCB
Explanation Node operator facility (NOF) rejected a DEACTIVATE_DLC verb because the DLC name in the verb (dlc_name) was not specified.
Recommended Action The DEACTIVATE_DLC verb is rejected, so the specified data-link control is not stopped. Reissue the verb with correct values. If the error occurred while loading the initial network configuration or while processing the network definition file, correct the error in the file and reload the configuration.
Error Message%APPN-3-lognofDLC_NAME_WAS_NOT_FOUND : DEFINE_DLC dlc name is not specified
Explanation A DEFINE_DLC verb was rejected because the DLC name in the verb (dlc_name) was not specified.
Recommended Action The DEFINE_DLC verb is rejected, so the specified data-link control is not created or started. Reissue the verb with correct values. If the error occurred while loading the initial network configuration or while processing the network definition file, correct the error in the file and reload the configuration.
Error Message%APPN-3-lognofENV_RSP_INV_CORREL : NOF received PE_CREATE_ENVIRONMENT_RSP with invalid correlator
Explanation Node operator facility (NOF) received a response interprocess signal (IPS) (PE_CREATE_ENVIRONMENT_RSP) that it could not correlate.
Recommended Action The response is from a request to create an environment, probably in an attached coprocessor. NOF could not correlate the response to any of its outstanding creation requests. There is an internal code problem in the local NOF or environment manager. 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%APPN-3-lognofEXCEPTION_RSP_RCVD : NOF received exception response, sense_code = [hex], ips_name = [hex]
Explanation A node component encountered an error while processing a node operator facility (NOF) request.
Recommended Action The other component sent an EXCEPTION_RSP IPS message indicating the failure. The EXCEPTION_RSP message contains a sense code that identifies the cause of the failure. Probable causes of this error are an unrecoverable system error, detection of a configuration error by the node, not all required software components being installed or available for use by the node, a serious memory shortage, or an internal code 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%APPN-3-lognofFQ_ADJ_CPNAME_NOT_FOUND : DEFINE_LINK adjacent CP name is invalid or not specified when required, adj_cp_name = [chars]
Explanation Node operator facility (NOF) rejected a DEFINE_LINK verb because the value of the adjacent CP name in the verb (fq_adj_cpname) is invalid or is missing.
Recommended Action The error occurred because of a specified adjacent CP name that was not a network-qualified, SNA type-a character name or because the node specified is a LEN node and the adjacent CP name was not specified. The DEFINE_LINK verb is rejected, so the link to the adjacent node is not defined. Reissue the verb with correct values. If the error occurred while loading the initial network configuration or while processing the network definition file, correct the error in the file and reload the configuration.
Error Message%APPN-3-lognofIBM_COS_NOT_DELETED : IBM defined COS names (CPSVCMG or SNASVCMG) cannot be deleted
Explanation Node operator facility (NOF) rejected a DELETE_COS verb because the specified class-of-service name was CPSVCMG or SNASVCMG.
Recommended Action A DELETE_COS verb was rejected because it attempted to delete a class-of-service definition (CPSVCMG or SNASVCMG) that is required by the APPN node. The DELETE_COS verb is rejected, so the class-of-service definition is still defined. The specified class-of-service cannot be deleted. No action is required unless you meant to delete a different class-of-service definition and specified the name incorrectly. If so, reissue the verb with the correct name.
Error Message%APPN-3-lognofINVALID_EID : NOF received PE_LOST_ENVIRONMENT with invalid EID, eid = [hex]
Explanation Node operator facility (NOF) received a notification interprocess signal (IPS) (PE_LOST_ENVIRONMENT) that it could not correlate.
Recommended Action The notification was sent by environment manager to inform operator facility (OF) that an environment manager process (probably in an attached coprocessor) ended. NOF could not correlate the notification to any of the subsystems (coprocessors) that it is using. There is an internal code problem in the local NOF. 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%APPN-3-lognofNO_MS_CNTL_MSG_TO_SCM : NOF could not send MS cntl message to SCM, send_pid = [hex]
Explanation Node operator facility (NOF) could not send an interprocess signal (IPS) to the session connector manager to request accounting data.
Recommended Action The failed IPS was a request to retrieve accounting data from the session connector manager, including intermediate sessions, their RSCVs, performance statistics, and threshold values. The function PQenq failed. Probable causes of this error are a system function failure (preventing the transmission of the IPS to the session connector manager), a serious memory shortage problem, or an internal code 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%APPN-3-lognofPAP01_ERROR_RECOV : WARNING PAP01 error recovery was called, event == not Rcld([hex]), qualifier = [hex]
Explanation A node process encountered an unrecoverable error and abended.
Recommended Action The node continues to execute. Node operator facility (NOF) detected that one or more local processes abended with an unrecoverable error. Probable causes of this error are an internal code problem in the local system, an unrecoverable system error, or a serious memory shortage. 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%APPN-3-lognofPDQENQ_ERROR : NOF - Error in PDqenq, rc = [hex], cfg_did = [hex]
Explanation The main node operator facility (NOF) process in the node control point cannot forward an IPS message to the configuration control component in the system.
Recommended Action The function PDQenq failed. Probable causes of this problem are a system function failure (preventing the sending of the IPS), a serious memory shortage, or an internal code 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%APPN-3-lognofPECREATE_ENV_FAILED : NOF - PEcreate_environment_failed, define_rc = [hex]
Explanation Node operator facility (NOF) could not create the processing environment required by the local system in the attached subsystem (coprocessor).
Recommended Action None of the ports or links supplied by the attached subsystem can be used by the node. The function PEdefine_subsystem failed. Probable causes of this error are a system function failure (preventing the creation of environment manager), not all required software components being installed or available for use by the node, a serious memory shortage, or an internal code 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%APPN-3-lognofPEDEFINE_SUBSYS_FAILED : NOF - PEdefine_subsystem failed, define_rc = [hex]
Explanation Node operator facility (NOF) could not create the processing environment required by the local system in the attached subsystem (coprocessor).
Recommended Action None of the ports or links supplied by the attached subsystem can be used by the node. The function PEdefine_subsystem failed. Probable causes of this error are a system function failure (preventing the creation of environment manager), not all required software components being installed or available for use by the node, a serious memory shortage, or an internal code 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%APPN-3-lognofRECVD_ABEND_NOTIF : NOF received abend notification from a process, abending_process = [chars], abending_process_id = [hex], lpid = [hex]
Explanation A node process notified node operator facility (NOF) sent a ABEND_NOTIFICATION to NOF, thereby notifying NOF that it is abending.
Recommended Action NOF detected that one or more local processes abended. The local process sent an ABEND_NOTIFICATION to NOF before ending. The detected error is probably not a critical error (such as a processor exception), but it is unrecoverable. Probable causes of this error are an internal code problem, an unrecoverable system error, or a serious memory shortage. 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%APPN-3-lognofRECVD_VAL_STRING_EXPCTD : NOF received an unexpected response IPS, ips_name = [hex], message_name = [chars]
Explanation Node operator facility (NOF) received an unexpected internal interprocess signal (IPS).
Recommended Action NOF was expecting a response from another node component, but received a different signal. There is an internal code 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%APPN-3-lognofRQD_COS_NAME_NOT_FOUND : DEFINE_COS class-of-service name is invalid or not specified, cos_name = [chars]
Explanation Node operator facility (NOF) rejected a DEFINE_COS verb (cos_name) because the class-of-service name is invalid or was not specified.
Recommended Action This error occurred because you specified a COS name, but the specified value is not an SNA type-a character name, or because you did not specify a COS name. The DEFINE_COS verb is rejected, so the class-of-service definition is not created. Reissue the verb with correct values. If the error occurred while loading the initial network configuration or while processing the network definition file, correct the error in the file and reload the configuration.
Error Message%APPN-3-lognofUNABLE_TO_MONITOR_EGPE : NOF unable to monitor environment manager, RC is %1
Explanation Node operator facility (NOF) could not add a notification to inform it when an environment manager process ends.
Recommended Action NOF is notified whenever the environment manager in the control point or a subsystem (coprocessor) ends. If environment manager ends, that subsystem is no longer available for use by the APPN node. The environment manager function PEstart_EGPE_down_monitor failed. Probable causes of this error are an internal code problem, an error occurring while trying to set up the monitor path between NOF and the environment manager environments, or a serious memory shortage. 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%APPN-3-lognofUNEXPCTD_DOS_ERROR_RC : Unexpected system error while stopping the node
Explanation While the node operator facility (NOF) was stopping an APPN node, an operating system function failed.
Recommended Action NOF encountered a system error while NOF was processing an immediate stop request (STOP_APPN type=HARD). Probable causes of the error are the failure of the function PEstart_timer or an internal code 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%APPN-3-lognofUNEXPCTD_SGNL : NOF received an unexpected signal from CS
Explanation Node operator facility (NOF) received an internal interprocess signal (IPS) from configuration services (CS) that it does not recognize or cannot process.
Recommended Action There is an internal code 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%APPN-3-lognofUNEXPCTD_SGNL_SM_AM_RM : NOF received an unexpected signal from SM, AM or RM, ips_name = [hex]
Explanation Node operator facility (NOF) received an internal interprocess signal (IPS) from an APPC component (session manager, attach manager, or resource manager) that it does not recognize or cannot process.
Recommended Action There is an internal code 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%APPN-3-lognofUNKNOWN_IPS_RECEIVED : NOF received unknown IPS from API, ips_name = [hex]
Explanation Node operator facility (NOF) received an internal interprocess signal containing an API verb that it does not recognize or cannot process.
Recommended Action There is an internal code 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%APPN-3-lognofUNKNOWN_SSID : NOF received SS_AVAILABLE with unknown ss_id, ss_id = [hex]
Explanation Node operator facility (NOF) received a notification IPS (SS_AVAILABLE) that it cannot correlate.
Recommended Action NOF could not correlate the notification to any of the subsystems (coprocessors) that it is using. There is an internal code 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%APPN-3-lognofUNKNOWN_VERB_RECEIVED : NOF received unknown verb from API, pri.rc = [hex], sec.rc = [hex]
Explanation Node operator facility (NOF) received an internal interprocess signal containing an API verb that it does not recognize or cannot process.
Recommended Action There is an internal code 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%APPN-3-lognofUNRECOV_ERR_EVENT_RCLD : WARNING Unrecoverable Error: event == Rcld, qualifier = [dec], rc= [hex]
Explanation A node process encountered an unrecoverable error and abended.
Recommended Action Node operator facility (NOF) detected that one or more local processes abended with an unrecoverable error. Probable causes of this error are an internal code problem, an unrecoverable system error, or a serious memory shortage. 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%APPN-3-logpcASM_ACTIVATE_AS_FAILED : ASM - Address Space cannot be activated, sense code = [hex]
Explanation The address space manager encountered an error while trying to create a new address space.
Recommended Action The address space manager could not create an address space for a new path control instance because the required buffers could not be allocated. The local node does not have enough memory available to accept the new address space and its possible sessions. 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%APPN-3-logpcASM_AS_NOT_FOUND : ASM - Address Space was not found in the AS Table
Explanation The address space manager could not determine the address space responsible for handling the messages processed by a particular path control instance.
Recommended Action The address space for the path control instance does not exist. Probable causes of this error are a programming error within the local node or the remote node sending an invalid message. 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%APPN-3-logpcASM_BIUI_RCV_CHECK : ASM - neither BIUI nor EBIUI was set when MU segmentation is not allowed
Explanation The address space manager received an invalid message.
Recommended Action The address space manager received a segmented message, but the received message should not be segmented. That is, the received message is not allowed to be segmented, but the segmentation indicators in the transmission header (TH) indicate the message is not a one-segment message. For example, UNBIND messages and messages received from a session services control point (SSCP) should not be segmented. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logpcASM_CV_LENGTH_ERR : ASM - CV length error, remaining length = [hex]
Explanation The address space manager received a message containing invalid control vector information.
Recommended Action The lengths of a set of control vectors or subvectors do not correspond to the expected length indicated by the containing SNA vector. The address space manager received a message containing invalid control vectors. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logpcASM_DEQD_UNKWN_IPS : ASM dequeued an unknown IPS, ips name = [hex]
Explanation The address space manager (ASM) received an internal signal (IPS) that it does not recognize or cannot process.
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%APPN-3-logpcASM_DEQD_UNKWN_MU : ASM dequeued an unknown MU, header type = [hex]
Explanation The address space manager (ASM) received an SNA message (MU) that it does not recognize or cannot process.
Recommended Action ASM processes only session messages (such as BIND, UNBIND, or ACTPU/ACTLU). 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%APPN-3-logpcASM_IPM_4_NONADAPT_PAC : ASM - IPM received while Adaptive Pacing is not supported by the node, sense code = [hex]
Explanation The address space manager received an unexpected BIND pacing message.
Recommended Action The address space manager received an SNA isolated pacing message (IPM) from a transmission group (TG) that is not allowed to perform adaptive pacing (use IPMs) for BIND messages. The local node and the node that sent the IPM negotiated that adaptive BIND pacing would not be used on the TG from which the IPM was received. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logpcASM_LFSID_IN_USE_REJ1 : ASM - the LFSID is in use, reject the BIND, sense code = [hex]
Explanation The address space manager rejected a request to create a new session with a remote node because the LFSID in the BIND request is already assigned to another session.
Recommended Action Probable causes of this error are the remote node sent an invalid message or lost the existing session, the APPC/APPN support in the remote node is not compatible with the local APPC/APPN support, or a network race condition may have occurred in which the remote node detected the loss of an existing session before the local node and sent a request using the same LFSID. 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%APPN-3-logpcASM_LFSID_IN_USE_REJ2 : ASM - a NAU is being deleted and ASM is waiting for a LFSID_IN_USE_RSP, sense code = [hex]
Explanation The address space manager is rejecting any outstanding session creation requests because the LU or control point (CP) is being stopped.
Recommended Action The address space manager was processing a session initiation request (BIND) from another node when the related LU or CP was deactivated by operator request. This is not an error condition. The event is logged so that problem-determination personnel can determine why a session was rejected. 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%APPN-3-logpcASM_LFSID_IN_USE_REJ3 : ASM - the LFSID is not in use, but has not been freed in ASM, sense_code = [hex]
Explanation The address space manager encountered an error while trying to accept a new session.
Recommended Action The address space manager rejected a request to create a new session with a remote node because the LFSID in the BIND request is already assigned to another session according to the address space manager. One probable cause of this error is that a race condition occurred where the local node detected the loss of an existing session and is in the process of cleaning up the session when it receives a request from a remote node for a session with the same LFSID. Other probable causes are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logpcASM_LRG_LFSID_RCV_CHECK : ASM - LFSID is out of bounds, large table is used, sidh = [hex], sense code = [hex]
Explanation The address space manager received a message containing an invalid or unrecognized LFSID.
Recommended Action Possible problems include the following. The SIDH value was 00, which is reserved for messages exchanged with a session services control point (SSCP), but the received message was not an SSCP message. The SIDH value was not 00, but the received message was an SSCP message. The SIDH value was 01, which should be reserved for BIND pacing, but the received message is not a BIND pacing message. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logpcASM_MSG_DEQ_UNKN_Q : ASM - ASM message dequeued from unknown Queue, returned queue no. = [hex]
Explanation An address space manager received an interprocess signal (IPS) via an unrecognized process queue in the address space manager (ASM).
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%APPN-3-logpcASM_NO_BUFF_4_IPM_ACK : ASM - Cannot get a buffer to build and send an IPM ack
Explanation The address space manager encountered an error while trying to respond to a BIND pacing message.
Recommended Action The address space manager could not send an acknowledgment to a BIND pacing message because it could not obtain the buffer needed to build the acknowledgment. Probable causes of this error are the local node not having enough memory available to accept any new BIND requests for the related address space (TG), a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logpcASM_PREM_END : ASM ending prematurely
Explanation The address space manager (ASM) process unexpectedly exited its internal signal processing loop.
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%APPN-3-logpcASM_RCV_BIND_BAD_SIDH : ASM - The BIND received contains an invalid sidh value
Explanation The address space manager received an invalid BIND message.
Recommended Action The address space manager could not process a received session initiation request (BIND). The LFSID contained in the BIND was invalid (bad SIDH value). Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logpcASM_RCV_BIND_RU_ERROR : ASM - BIND RU error(s), reject the BIND, sense code = [hex]
Explanation The address space manager received an invalid BIND message.
Recommended Action The address space manager could not process a received session initiation request (BIND) because it contained invalid SNA control information. Invalid information can include the following:
•
•
•
•
•
•
•
Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%APPN-3-logpcASM_RCV_IPM_0_SEND_NWS : ASM - Received a solicited IPM but the next window size is zero, sense code = [hex]
Explanation The address space manager received an invalid pacing message.
Recommended Action The address space manager could not process a received pacing message (IPM) because the contents of the received message are invalid. The received message is a solicited IPM message, but the allowed next window size (as specified in the received message) is zero. APPN nodes should not send solicited IPM messages with a next window size of zero, since the receiving node is already waiting for a pacing message before it will send any additional data. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logpcASM_RCV_IPM_PACING_ERR1 : ASM - Received a reset ack and this node does not support adaptive bind pacing, sense code = [hex]
Explanation The address space manager received an unexpected BIND pacing message.
Recommended Action The address space manager received an SNA isolated pacing acknowledgment message (IPM) that acknowledges a request from the local node to reset the pacing window size (the number of messages allowed to be sent). The local node did not send a request to reset the pacing window size. More specifically, the local node received a reset acknowledgment IPM from the remote node. The local node either does not support adaptive pacing or has not sent an unsolicited pacing message yet, so the acknowledgment is for a message that was never sent. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logpcASM_RCV_IPM_PACING_ERR2 : ASM - Received an UNKNOWN ipm, sense code = [hex]
Explanation The address space manager received an invalid pacing message.
Recommended Action The address space manager could not process a received pacing message (IPM) because the message type in the received message is invalid. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logpcASM_RCV_IPM_RH_RU_ERR : ASM - IPM RH or RU error, sense code = [hex]
Explanation The address space manager received an invalid pacing message.
Recommended Action The address space manager could not process a received pacing message (IPM) because it contained invalid SNA control information. Some or all of the following information is invalid: the request/response indicator in the RH is set (the message is a response), the pacing indicator in the RH is not set, the response type indicators in the RH (DR1, DR2) are set, the format indicator in the IPM RU is invalid, or the size of the received message is incorrect. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logpcASM_RCV_IPM_TH_ERR : ASM - IPM TH bits are not set correctly, sense code = [hex]
Explanation The address space manager received an invalid pacing message.
Recommended Action The address space manager could not process a received pacing message (IPM) because it contained invalid SNA control information. The received IPM violated SNA segmentation rules. The received message is multisegmented, but IPM messages are not allowed to be segmented. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logpcASM_RCV_IPM_UNEXPECTED : ASM - Received a solicited IPM which was never requested, sense code = [hex]
Explanation The address space manager received an unexpected BIND pacing message.
Recommended Action The address space manager received an SNA isolated pacing message (IPM) that indicates it was solicited by the local node, but the local node did not solicit the IPM. APPN nodes solicit IPMs when they want to send more messages, but have already sent all the messages allowed by the last pacing message received from the remote node. The local node received a solicited IPM message from the remote node, but it still is allowed to send more messages (the new window size is nonzero). Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logpcASM_RCV_IPM_WRONG_STATE : ASM - IPM received while ASM is in the middle of reassembling, sense code = [hex]
Explanation The address space manager received an unexpected BIND pacing message.
Recommended Action The address space manager received an SNA isolated pacing message (IPM) while in the process of receiving a multisegmented message from the node that sent the IPM. IPM messages can be sent only until all the segments of the previously transmitted message are sent. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logpcASM_RECVD_BAD_SIDH : ASM received bad SIDH in SMALL mode, sense code = [hex]
Explanation The address space manager (ASM) received a message containing an invalid LFSID.
Recommended Action The address space manager received a message containing an SIDH (high session index) that is invalid or unrecognized. If the SIDH value was 01, which is reserved for BIND pacing, the received message was not a BIND pacing message. If the SIDH value was 00, which is reserved for session services control point (SSCP) data, the received message was not an SSCP message. Probable causes of this error are the remote node sending an invalid message, a software problem in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logpcASM_SEGMENTATION_ERROR1 : ASM - MU segment reassembly error, sense code = [hex]
Explanation The address space manager received an invalid message.
Recommended Action The address space manager could not process a received message, because it contained invalid SNA control information. This error could occur in the following situations. The received message violated SNA segmentation rules. The local node was in the process of assembling a multisegmented message, and the begin segment indicator was set in the TH (it was attempting to begin a new message before completing the previous message). The local node was expecting a new message, but the begin segment indicator was not set in the TH (it was attempting to continue a message that was already completely assembled). The received message was part of a multisegmented message, but the LFSID or the sequence number in the message did not match the values in the other segments of the message. The received message is multisegmented, but the node that sent the message had indicated that it would not send multisegmented messages. The received message violated SNA pacing protocols. The size of the received message exceeded the maximum size agreed upon by the local node and the node that sent the message. Probable causes of this error are a programming error in the local node or in the node that sent the message, or incompatibility between the APPC/APPN support in the remote node and the local APPC/APPN support. 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%APPN-3-logpcASM_SEGMENTATION_ERROR2 : ASM - MU segment reassembly failed, free up MU, sense code = [hex]