Полезная информация

cc/td/doc/product/software/ios120/12supdoc
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

CMCC-LOADER Error Messages
CMCC-LOVE Error Messages
CMCC-MBUF Error Messages
CMCC-MEMD Error Messages
CMCC-MPC Error Messages
CMCC-MSG802 Error Messages
CMCC-NEVADA Error Messages
CMCC-OFFL Error Messages
CMCC-PACK Error Messages
CMCC-PKTS Error Messages
CMCC-SCB Error Messages
CMCC-SCHED Error Messages
CMCC-SLC Error Messages
CMCC-SLCI Error Messages
CMCC-SSI802 Error Messages
CMCC-SUBSYS Error Messages
CMCC-SYS Error Messages
CMCC-SYSMGT_EVENT Error Message
CMCC-SYSMGT_RPC Error Messages
CMCC-TCPIP Error Message
CMCC-TN3270 Error Messages
CMCC-UTIL Error Message
CMCC-XCPA Error Messages

CMCC-LOADER Error Messages

CIP error messages related to the relocating loader facility


Error Message   
%LOADER-3-ABSERR: Error: not handled - Symbol [chars] is absolute

Explanation   The loader does not handle variables of this type.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-ALOCER1: Error: Allocating storage - load fails

Explanation   There is not enough storage to load this file.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative. More storage will probably be needed. You might use the current storage more efficiently by running a different combination of features.


Error Message   
%LOADER-3-ALOCER2: Error: Did not allocate storage - loading of data failed

Explanation   There is not enough storage to load this file.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative. More storage will probably be needed. You might use the current storage more efficiently by running a different combination of features.


Error Message   
%LOADER-3-ATFERR: Error: atf array overflow

Explanation   The area to free (ATF) array is too small. The ATF array is an array of areas to be freed when an attempted load fails.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-BADSHT: Error: Section header type [hex]([dec]) not understood

Explanation   The input file is not in the proper format.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-BADVERS: [chars]: Invalid segment version: [chars]

Explanation   The segment version does not match the remainder of the currently loaded software.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-BAKEXP: Error: Deleting external symbol [chars] from the exported table

Explanation   The symbols should have been deleted from the table, but were not. This will probably cause problems during future file loads.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-BIGEND: Error: Input is not big endian

Explanation   The input file is not the correct type for loading.

Recommended Action   Check the input file type. If the file type is correct, copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LOADER-3-BINDERR: Error: Bind value in symbol table entry not understood

Explanation   The loader cannot handle variables of this type.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-COMERR: Error: type not handled, must be .scommon

Explanation   The loader cannot handle this type.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-COMMIX: Error: common variable [chars] matches name of non-common loaded variable

Explanation   An error occurred in the input files.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-COMPER: Error: Compiled for incorrect target machine

Explanation   The input file is not the correct type for loading.

Recommended Action   Check the input file type. If the file type is correct, copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LOADER-3-DREADE: Error: Reading in program data

Explanation   An error prevented the loader from reading a section of the file.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-DUPEXP: Error: Duplicate exported external symbol [chars] not allowed

Explanation   The file being loaded attempted to export a symbol that had already been exported by a previously loaded file.

Recommended Action   There is a conflict between loadable files and/or the kernel. Report this error to your technical support representative.


Error Message   
%LOADER-3-EIDENT: Error: File header has unknown data in e_ident area

Explanation   The input file is not in the correct format needed for loading.

Recommended Action   Check the input file format. If the format is correct, copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LOADER-3-ELF32: Error: Input is not an ELF32 file

Explanation   The input file is not in the correct format needed for loading.

Recommended Action   Check the input file format. If the format is correct, copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LOADER-3-ELFH: Error: Cannot read ELF header from input file

Explanation   The loader could not read the module header information.

Recommended Action   Check the file. If it is correct, report this error message to your technical support representative.


Error Message   
%LOADER-3-ERR16H: Error: processing HI16 LO16 pair. Low without High

Explanation   The loader cannot handle relocation entries of this type.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-ERR16M: Error: processing HI16 LO16. Low [hex] does not match High [hex]

Explanation   The loader cannot handle relocation entries of this type.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-ERRCNR: Error: Cannot relocate - required symbol [chars] is not resolved

Explanation   A required symbol is missing.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-FCLOSE: Warning: File close failed, code = [dec]

Explanation   Loading is complete, but the close failed.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-FILESIZE: Unable to access image file

Explanation   The CIP has failed to access necessary image files.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-FOPEN: Error: Cannot open the input file [chars]

Explanation   An error occurred when attempting to open a file to be loaded.

Recommended Action   Confirm that the file exists. Create it if possible. If the problem persists, copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LOADER-3-FOPENBZ: Cannot open [chars] - busy (code [dec]), have tried every 5 secs for a minute

Explanation   A required file is currently in use. An open was retried every 5 seconds for 1 minute, before failing the open.

Recommended Action   Report this error to your technical support representative, if open fails.


Error Message   
%LOADER-3-FOPENER: Error: file ([chars]) open failure code [dec]

Explanation   A required file cannot be opened.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-FREADE: Error: reading, offset: [hex] size: [hex]([dec])

Explanation   The loader could not read the input file. The load failed.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-GPPROB: Error: Allocation of GP relative space problem: [hex]([dec]) left, [hex]([dec]) needed

Explanation   The space needed for the allocation of a larger area has been exhausted.

Recommended Action   Sufficient space should be allocated in advance. Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LOADER-3-GREADE: Error: reading in GP relative section data

Explanation   An error prevented the loader from reading a section of the file.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-HDRSIZ: Error: this size header entry cannot be handled

Explanation   The file is not in the proper format. The loader cannot handle it.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-HDRVER: Error: Input is not current version

Explanation   The input file is not the correct version of object file format.

Recommended Action   Check the file format version. If the file version is correct, copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LOADER-0-HEADER: Loading file [chars]:

Explanation   This message precedes other messages relating to loading a file. It is a header to identify the name of the file being loaded.

Recommended Action   Copy this message and the following messages. Report this information to your technical support representative.


Error Message   
%LOADER-3-HILO16MX: Error: HI/LO16 relocation table exceeded max of [dec]

Explanation   The maximum number of pending HI16 entries exceeded the table capacity.

Recommended Action   MAX_HILO16 must be increased, and the loadrel.c file must be recompiled. Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LOADER-3-HREADE: Error: Cannot read headers from the file

Explanation   An error occurred while reading the file headers.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-INSUFF: Error: insufficient space for suballocation: [hex]([dec]) left, [hex]([dec]) needed

Explanation   There is not enough space for the new allocation.

Recommended Action   Sufficient space should be allocated in advance. Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LOADER-0-INVALIDIOS: IOS version incompatible with CIP - must be at least [dec].[dec]

Explanation   This Cisco IOS software release is incompatible with this CIP microcode image.

Recommended Action   The Cisco IOS software must be updated to match the CIP version. Report this error to your technical support representative.


Error Message   
%LOADER-6-LOADING: [chars] -- [dec] bytes

Explanation   The CIP successfully loaded a segment image.

Recommended Action   This is an informational message only. No action is required.


Error Message   
%LOADER-0-LOADMAP_DATA1: Ver: [chars] Rev: [dec] Segment: [chars]

Explanation   This message identifies the segment whose section information follows.

Recommended Action   Report this information to your technical support representative.


Error Message   
%LOADER-0-LOADMAP_DATA2: [hex] [hex] [dec] [chars]

Explanation   This message provides data for addresses, sizes, and so on, of modules loaded into the CIP storage.

Recommended Action   Report this information to your technical support representative.


Error Message   
%LOADER-0-LOADMAP_DATA3: [chars]

Explanation   This message displays the compile information for the segment listed in the previous line.

Recommended Action   Report this information to your technical support representative.


Error Message   
%LOADER-0-LOADMAP_EMPTY1: Loader initialization is not complete, no segments loaded

Explanation   The loader has not been initialized. Therefore, no modules are loaded in CIP storage.

Recommended Action   Report this information to your technical support representative.


Error Message   
%LOADER-0-LOADMAP_EMPTY2: No segments have been loaded

Explanation   The loader has not loaded any modules into CIP storage.

Recommended Action   Report this information to your technical support representative.


Error Message   
%LOADER-0-LOADMAP_HEAD0: Segment Load Map

Explanation   This message precedes and introduces data listing the map of modules loaded into CIP storage. It also acts as a header for the displayed data.

Recommended Action   Copy the error message and the lines of data. Report this information to your technical support representative.


Error Message   
%LOADER-0-LOADMAP_HEAD1: Start End Size Name

Explanation   This message precedes and introduces data listing the map of modules loaded into CIP storage. It also acts as a header for the displayed data.

Recommended Action   Copy the error message and the lines of data. Report this information to your technical support representative.


Error Message   
%LOADER-3-LOADRC: Error: Return code is [hex]([dec])

Explanation   This message displays the error level on the load failure.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-MAXRSE: Error: too many Resident Symbol Tables

Explanation   MAX_RSE_TABS is not sufficient to handle this file.

Recommended Action   MAX_RSE_TABS must be increased, and the loadrel.c file must be recompiled. Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LOADER-3-MAXSEC: Error: Total number of sections has exceeded pre-allocated space for [dec] entries

Explanation   MAX_SECTION_COUNT is not sufficient to handle this file.

Recommended Action   MAX_SECTION_COUNT must be increased, and the loadrel.c file must be recompiled. Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LOADER-3-MAXSTRT: Error: Too many string tables

Explanation   MAX_STR_TABS is not sufficient to handle this file.

Recommended Action   MAX_STR_TABS must be increased, and the loadrel.c file must be recompiled. Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LOADER-3-MAXSYMT: Error: Too many symbol tables

Explanation   MAX_SYM_TABS is not sufficient to handle this file.

Recommended Action   MAX_SYM_TABS must be increased, and the loadrel.c file must be recompiled. Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LOADER-3-NOBITS0: Error: NOBITS but size [dec] is not 0, not understood

Explanation   Either the loader cannot process the input file, or the file is not in the proper format.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-NODSO: Error: section contains dynamic shared objects

Explanation   The input file cannot have dynamic shared objects.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-NOELF: Error: Input is not an ELF file

Explanation   The input file is not in the correct format.

Recommended Action   Check the input file format. If the format is correct, copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LOADER-3-NOERES: Error: Could not resolve external symbol [chars]

Explanation   A reference from the file being loaded to an external symbol cannot be resolved.

Recommended Action   Define all prerequisite external symbols before loading the file. If the message recurs, copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LOADER-3-NOPREFIX: Unable to determine microcode image name

Explanation   The CIP is unable to compose the microcode image name.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-NOPRG: Error: No code to handle program headers

Explanation   The input file is not in the correct format.

Recommended Action   Check the input file format. If the format is correct, copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LOADER-3-NOSECH: Error: No section headers to process

Explanation   The input file is not in the proper format.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-NOSO: Error: section contains symbols conflicting with shared objects

Explanation   The input file cannot have shared objects.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-NOTRE: Error: File is neither relocatable nor executable

Explanation   The input file is not in the correct format.

Recommended Action   Check the input file format. If the format is correct, copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LOADER-3-NOVERS: [chars]: No entry for loader_segment_version

Explanation   The loader requires a file to be loaded to have an entry, loader_segment_version, containing a specific structure.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-READERR: Error: file read failure code [dec]

Explanation   An error occurred while the file was being read.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-RELFLG: Error: Cannot handle the flags in the relocation entry

Explanation   The loader cannot handle relocation entries of this type.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-RELREAD: Error: Cannot read relocation entries

Explanation   The loader could not read part of the file.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-RELTYP: Error: relocation type [hex]([dec]) not recognized

Explanation   The loader cannot handle this type of relocation.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-RELTYP2: Error: relocation type R_MIPS_[chars] not handled

Explanation   The loader cannot handle this type of relocation.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-RESERR: [chars] [dec] external symbols cannot be resolved

Explanation   Either the prerequisite files are not loaded, or there are incorrect references.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-SECERR: Error: Cannot handle section [chars]

Explanation   The loader cannot process this type of section of the code.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-SEEKER: Error: file seek failure code [dec]

Explanation   An error occurred positioning within the file.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-SHFLAGE: Error: no storage allocated - sh_flags did not indicate how

Explanation   The loader cannot handle this file.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-SHNHIPE: Error: not handled -End appl specific range of indices

Explanation   The loader cannot handle variables of this type.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-SHNHIR: Error: not handled - End reserved range of indices

Explanation   The loader cannot handle variables of this type.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-SIZERR1: Error: common variable [chars] has a size incompatible with loaded variable

Explanation   The loader cannot allocate a larger variable to an already loaded smaller variable.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-SORBER: Error: type not handled, must be .sdata or .sbss

Explanation   The loader cannot handle this type.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-SREADE: Error: Cannot read in symbol string

Explanation   The loader could not read a needed section of the file.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-SREADS: Error: Cannot read in symbol table

Explanation   An error prevented reading a necessary part of the file for loading.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-STOTHER: Error: Problem: a symbol table entry is using field ST_OTHER

Explanation   The loader cannot handle this file.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-STREXE: Error: Strings exceed string table area allocated [dec] [dec]

Explanation   The preallocated area is not large enough.

Recommended Action   The loader must be recompiled with more area. Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LOADER-3-SUNDERR: Error: not handled - Small undefined symbol

Explanation   The loader cannot handle variables of this type.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-SYMEXE: Error: Symbols exceed symbol table area allocated [dec] [dec]

Explanation   The preallocated area is not large enough for loading.

Recommended Action   The loader must be recompiled with more area. Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LOADER-3-SYRERR: Error: Relocation entry symbol, [hex]([dec]), is not in symbol table

Explanation   This is an error in the input file.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-TSHSIZ: Error: total sections headers [hex]([dec]) too large for pre-allocated area [hex]([dec])

Explanation   The preallocated area is not large enough for loading.

Recommended Action   The loader must be recompiled with more area. Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LOADER-3-TYPERR: Error: Type value in symbol table entry not understood

Explanation   The loader cannot handle variables of this type.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-USRERR: Error: not handled - Undefined section reference

Explanation   The loader cannot handle variables of this type.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-VARHIP: Error: Symbol is HIPROC variable - not handled

Explanation   The loader cannot handle variables of this type.

Recommended Action   Report this error to your technical support representative.


Error Message   
%LOADER-3-VARLOP: Error: Symbol is LOPROC variable - not handled

Explanation   The loader cannot handle variables of this type.

Recommended Action   Report this error to your technical support representative.

CMCC-LOVE Error Messages

CIP error messages related to the mechanism that sends statistics from the CIP to the router


Error Message   
%LOVE-3-LOVELETTER: Error in love letter processing for port [dec] ([dec])

Explanation   An attempt to transfer statistics to the router from the CMCC card failed.

Recommended Action   The CMCC card tried to recover by dropping the buffer with the statistics. However, it's possible that one or more buffers were lost in the process. Copy the error message exactly as it appears, issue the show tech-support command and call your technical service representative with all the information.


Error Message   
%LOVE-3-NOMEM: No memory available for Love Letter processing

Explanation   The CMCC card does not have enough memory to start the love letter process. Love letters are used to transmit channel statistics to Cisco IOS software. No love letters will be transmitted by this CMCC card.

Recommended Action   Verify the amount of memory installed on the channel adapter and upgrade if necessary.

CMCC-MBUF Error Messages

Memory buffer error messages


Error Message   
%MBUF-0-MFREEx2: mfree: mbuf [hex] already free'ed from pc=[hex] ra=[hex] @(pc=[hex]ra=[hex])

Explanation   A request was made to free an mbuf that was already free.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MBUF-0-PANIC: panic[[chars]@[dec]] in [chars]: [chars]

Explanation   An unexpected internal error has occurred in the TCP/IP stack.

Recommended Action   Report this error to your technical support representative.

CMCC-MEMD Error Messages

CIP error message related to the memory device facility


Error Message   
%MEMD-3-BADIPC: IPC message received with no IPC handler

Explanation   An IPC message was queued to the CIP and there was no handler defined to process it.

Recommended Action   The CIP dropped the IPC message. Report this error to your technical support representative.


Error Message   
%MEMD-3-BADPTR: Bad pointer in MEMD. Code: [hex]. ICB: [hex] Header: [hex], Data: [hex]

Explanation   While processing a buffer queue in MEMD, a pointer was found to have an invalid value.

Recommended Action   The CIP dropped the packet. Report this error to your technical support representative.


Error Message   
%MEMD-3-BADVCN: Bad vcn [dec]([hex]), port adapter [dec], MSGDEF_LIMIT_MEDIUM

Explanation   A packet was queued to the CIP and the virtual circuit associated with the packet is not valid.

Recommended Action   The CIP dropped the packet. Report this error to your technical support representative.


Error Message   
%MEMD-3-FRAME_DATA1: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex], MSGDEF_LIMIT_MEDIUM

Explanation   This message contains a hex dump of data associated with the immediately preceding error message.

Recommended Action   Forward a copy of the entire hex dump to your Cisco technical support representative.


Error Message   
%MEMD-3-FRAME_DATA2: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex], MSGDEF_LIMIT_MEDIUM

Explanation   This message contains a hex dump of data associated with the immediately preceding error message.

Recommended Action   Forward a copy of the entire hex dump to your Cisco technical support representative.


Error Message   
%MEMD-3-FRAME_START: Start address of bad frame: 0x[hex] dumping from 0x[hex], MSGDEF_LIMIT_MEDIUM

Explanation   This message contains the start address of a data frame with a bad virtual circuit number.

Recommended Action   Forward a copy of this message to your Cisco technical support representative.


Error Message   
%MEMD-3-VCNDEREGISTER: Invalid VCN ([dec]) specified

Explanation   When attempting to deregister a routine to handle data for a given virtual circuit, the virtual circuit number was out of range. The deregistration request is ignored.

Recommended Action   Restart the CIP. Report this error to your technical support representative.


Error Message   
%MEMD-3-VCNREGISTER: Invalid VCN ([dec]) specified

Explanation   When attempting to register a routine to handle data for a given virtual circuit, the virtual circuit number was out of range. No messages for the given virtual circuit will be accepted, and additional error messages will be generated for each message.

Recommended Action   Restart the CIP. Report this error to your technical support representative.


Error Message   
%MEMD-3-WRONGINT: VCN [dec]([hex]) not for port adapter [dec], MSGDEF_LIMIT_MEDIUM

Explanation   A packet has been queued for the CIP with a valid virtual circuit number, but the virtual circuit number is associated with the other port adapter.

Recommended Action   The CIP dropped the packet. Report this error to your technical support representative.

CMCC-MPC Error Messages

MultiPath Channel error messages


Error Message   
%MPC-6-BAD_DIRECTION: PA[dec] MPC [hex]-[hex] configured for [chars]

Explanation   This informational message is given when an XID2 message specifies a subchannel read/write transfer direction differently from the direction configured.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MPC-3-BAD_DLC_CMD: Received MPC DLC command [hex] unrecognized

Explanation   This error message is given when an MPC DLC frame is received and the DLC command is not recognized.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MPC-3-BAD_FLAGS: Received MPC frame with invalid flags [hex]

Explanation   This error message is given when an MPC block is received and the header configuration is not recognized.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MPC-3-BAD_HDR: Unrecognized MPC header received [hex] [hex]

Explanation   This error message is given when an MPC block is received and the header configuration is not recognized.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MPC-3-BLOCK_SEQ_ERROR: Block rcvd with seq num [hex], expected [hex]

Explanation   This error message is given when an MPC block is received with a sequence number error.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MPC-6-INIT: PA[dec] MPC [hex]-[hex] Device initialized

Explanation   This informative message is given when an MPC device is initialized. The device string is in the form PA x MPC yyyy-zz, where x is the port adapter number, yyyy is the path and zz is the device number.

Recommended Action   No action is required.


Error Message   
%MPC-3-LENGTH_ERR: Inconsistent length in received MPC frame

Explanation   This error message is given when an MPC frame is received with a length value that is inconsistent with the channel block length.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MPC-6-LINK_CONFIGURED: Link [chars] already configured

Explanation   This informative message is given when an attempt is made to configure an MPC link that has already been configured.

Recommended Action   No action is required.


Error Message   
%MPC-6-NODE_NOT_ACTIVE: PA[dec] MPC [hex]-[hex] Rcvd TG data but TG not active

Explanation   This informative message is given when a message if received for an MPC link where the transmission group has not been configured.

Recommended Action   No action is required.


Error Message   
%MPC-0-NOMEM: [chars] Attempt to acquire memory failed, pc: [hex]

Explanation   This error message is given when a call to create a pool or get a buffer fails.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MPC-3-PARTNER_FSM_ERR: TG Name: [chars], Event [chars], State [chars]

Explanation   This error message is given when an internal state machine attempts to execute an event inconsistent with the state.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MPC-6-SEQ_NUM_WRAP: Sequence number from host wrapped. TG name [chars]

Explanation   This informative message is given when the sequence number in a block from the host has wrapped.

Recommended Action   No action is required.


Error Message   
%MPC-6-SHUTDOWN: PA[dec] MPC [hex]-[hex] Device shutdown

Explanation   This informative message is given when an MPC device is shut down. The device string is in the form PA x MPC yyyy-zz, where x is the port adapter number, yyyy is the path and zz is the device number.

Recommended Action   No action is required.


Error Message   
%MPC-3-SUBCH_FSM_ERR: PA[dec] MPC [hex]-[hex] Event [chars], State [chars]

Explanation   This error message is given when an internal state machine attempts to execute an event inconsistent with the state.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MPC-3-SWEEP_FSM_ERR: TG Name: [chars], Event [chars], State [chars]

Explanation   This error message is given when an internal state machine attempts to execute an event inconsistent with the state.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MPC-3-SWEEP_SEQ_ERROR: Sweep rcvd with seq num [hex], expected [hex]

Explanation   This error message is given when an MPC sweep command is received with a sequence number error.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MPC-0-SYSMGT_ERROR1: MPC Subch detected error in sysmgt call: invalid CMPC DEVICE length

Explanation   An invalid parameter was received in a SYSMGT call.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MPC-0-SYSMGT_ERROR2: MPC Subch detected error in sysmgt call: invalid operation [dec]

Explanation   An invalid parameter was received in a SYSMGT call.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MPC-0-SYSMGT_ERROR3: MPC Llcc-Tg detected error in sysmgt call: invalid operation [dec]

Explanation   An invalid parameter was received in a SYSMGT call.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MPC-0-SYSMGT_ERROR4: MPC Llcc-Tg detected error in sysmgt call: invalid CMPC DEVICE length

Explanation   An invalid parameter was received in a SYSMGT call.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MPC-6-TOO_MANY_TGS: Cannot configure more than [dec] MPC TGs

Explanation   This informative message is given when an attempt is made to configure more than the maximum number of MPC TGs.

Recommended Action   No action is required.


Error Message   
%MPC-3-XID2_BAD_DATA: Invalid Xid2 Message: bad length or format

Explanation   This error message is given when an MPC subchannel is in the XID2 exchange state and the message received has a length that is not valid for an XID2 message segment.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MPC-3-XID2_BAD_HDR: Unrecognized Xid2 header received

Explanation   This error message is given when an XID2 frame is received and the header configuration is not recognized.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MPC-3-XID2_FSM_ERR: PA[dec] MPC [hex]-[hex] Event [chars], State [chars]

Explanation   This error message is given when an internal state machine attempts to execute an event inconsistent with the state.

Recommended Action   Report this error to your technical support representative.

CMCC-MSG802 Error Messages

CIP 802 error messages related to the IEEE 802.2cx Logical Link Control (LLC) protocol stack


Error Message   
%MSG802-3-ADAPTER_LIMIT_EXCEEDED: Configuration for adapter [dec] [sci_notation] rejected ([chars])

Explanation   An attempt was made to configure more than 18 CSNA adapters. A maximum of 18  CSNA adapters are allowed per CIP.

Recommended Action   Reduce the number of CSNA adapters configured to comply with the 18  CSNA adapter limit.


Error Message   
%MSG802-6-ADAPTER_OPEN: Adapter [chars]/[int] now open

Explanation   This is an informative message given for bringing up each adapter specified.

Recommended Action   No action is required.


Error Message   
%MSG802-6-ADAPTER_REM: Adapter [chars]/[int] now removed

Explanation   This is an informative message given for removing each adapter specified.

Recommended Action   No action is required.


Error Message   
%MSG802-6-ADAPTER_UPD: Adapter [chars]/[int] LLC parm now altered

Explanation   This is an informative message given for changing the LLC parameters for each adapter specified.

Recommended Action   No action is required.


Error Message   
%MSG802-6-BADNS_WARN: INVALID NS detected [dec] times; tuning of LLC parameter may be needed !!!

Explanation   The LLC protocol stack has received a bad frame that contains an invalid Ns from its peer. The problem is often caused by mis-configuration of LLC parameters. Fine tuning of the LLC parameters of the CIP adapter and its peer might be required to correct this problem. This warning message is only displayed for every 500 occurrences of BAD Ns detected for the given connection.

Recommended Action   Fine tuning of the LLC parameters of CIP adapter and its peer might be required to correct this problem.


Error Message   
%MSG802-6-CTASET_FAIL: set cta max_conn [dec] failed ([dec] bytes free) - max conn remain at [dec]

Explanation   This message means that the CTA mapper is not able to honor the maximum connection as configured, most likely because of running out of resources (such as a shortage of memory). Any attempt to decrease the maximum connection will be rejected. It might be rejected by the mapper because of lack of memory.

Recommended Action   Verify if overconfigured by checking the maximum numbers of connections configured. If not, report this error to your technical support representative.


Error Message   
%MSG802-6-FLOW_OFF_TERM: Terminating connection, RMAC=[hex].[hex].[hex] LMAC=[hex].[hex].[hex] RSAP=[hex] LSAP=[hex]

Explanation   This is an informative message given when the connection is terminated.

Recommended Action   No action is required.


Error Message   
%MSG802-6-FRAMESZ_EXCEEDED: frame exceeded max size ([dec] bytes)

Explanation   The MEMD buffer currently supported a maximum frame size of 4472 bytes. CSNA detected that the frame sent is larger than what it should be and the frame was discarded. This error most likely occurred because the maximum frame length is misconfigured.

Recommended Action   Check the maximum frame length configured.


Error Message   
%MSG802-3-HARD_ERROR: [chars]

Explanation   The protocol stack encountered error conditions that prevent it from continuing its normal operations.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MSG802-3-INVALID_CFGCMD: invalid config cmd detected cmd=[dec]

Explanation   The LLC task detected an invalid configuration command. The command is rejected.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MSG802-6-INVALID_ID: [chars]: invalid id type = [hex]

Explanation   The LLC has received an invalid ID type. Currently, such an ID type is not supported. The request is discarded.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MSG802-3-INVALID_MSICMD: invalid msi cmd detected cmd=[dec]

Explanation   The LLC task detected an invalid MSI command. The request is discarded.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MSG802-6-INVALID_PRIMITIVE: [chars]: invalid primitive code = [hex]

Explanation   The LLC has received an invalid service primitive. The module and routine that received such a primitive and the Service Primitive code are displayed.

Recommended Action   This is not a fatal error and the CSNA should be able to continue to operate. If somehow, the error becomes disruptive, report this error to your technical support representative.


Error Message   
%MSG802-3-INVALID_VCN1: LAN not configured for vcn=[dec], adapter=[dec], lan=[dec], ran=[dec] - cfg cmd rejected ([chars])

Explanation   Unable to process the configuration command because an invalid VCN was detected. The configuration command is rejected.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MSG802-3-INVALID_VCN2: LAN has configured for vcn=[dec], adapter=[dec], lan=[dec], ran=[dec] - cfg cmd rejected ([chars])

Explanation   Unable to process the configuration command because an invalid VCN was detected. The configuration command is rejected.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MSG802-6-LLC_DUP_CCB: LLC Station : RMAC=[hex].[hex].[hex] LMAC=[hex].[hex].[hex] LSAP=[hex] RSAP=[hex]

Explanation   An open station was received but the station address is already open.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MSG802-6-LLC_DUP_SAP: LLC Duplicate SAP on interface [int] : SAP=[hex], new user([hex]) old user([hex])

Explanation   Two SAP users have tried to open the same SAP number on the same adapter. A SAP user may be an XCA Major Node, a TN3270 Server PU, or TN3270 Server DLUR.

Recommended Action   Check XCA Node definitions.


Error Message   
%MSG802-6-LLC_SHUT: LLC shutdown completed

Explanation   This is an informative message given for shutdown of the LLC. Both the LLC DMA READ/WRITE task and the TIMER task were taken down.

Recommended Action   No action is required.


Error Message   
%MSG802-6-LLC_START: Starting LLC-2 with a session capacity of [int]

Explanation   This is an informative message given for bringing up an LLC subsystem.

Recommended Action   No action is required.


Error Message   
%MSG802-6-MAX_FAILED: change max conn [dec] failed ([dec] bytes free) - max conn remain at [dec]

Explanation   This message means that CIP is not able to honor the maximum connection as configured, most likely because of running out of resources (such as shortage of memory). Any attempt to decrease the maximum connection will be rejected. It might be rejected by the mapper because of lack of memory.

Recommended Action   Verify if overconfigured by checking the maximum numbers of connections configured. If not, report this error to your technical support representative.


Error Message   
%MSG802-6-MAX_FAILED2: cipmsg pool empty - max conn remain at [dec]

Explanation   This message means that CIP is not able to honor the maximum connection as configured, because it was unable to allocate a MSG buffer from the CIPMSG pool.

Recommended Action   Enter the max_llc command again. If the error persists, report this error to your technical support representative.


Error Message   
%MSG802-6-MAX_LLC_EXCEEDED: MAX_LLC_SESSIONS([int]) exceeded - [int] sessions rejected

Explanation   The maximum number of concurrent LLC connections has been exceeded.

Recommended Action   Increase the MAX_LLC_SESSIONS parameter on the CIP virtual interface.


Error Message   
%MSG802-6-NOMEM: Insufficient memory to initialize LLC - [chars]

Explanation   The channel adapter does not have enough available memory to initialize the LLC stack. The LLC stack will not be started.

Recommended Action   Verify the amount of memory installed on the channel adapter and upgrade if necessary.


Error Message   
%MSG802-3-QUEUE_OPEN: [chars] ([chars])

Explanation   The LLC task detected a queue open failure. Most likely the resource is not available for such a request.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MSG802-3-RESOURCE_DEPLETED: [chars] ([chars])

Explanation   The protocol stack encountered error conditions that prevent it from continuing its normal operations. Possible error such as resource depletion.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MSG802-6-SHRINK_CONN: reducing max_conn doesn't take effect until the virtual interface is restarted - max conn remain at [dec]

Explanation   This is an informative message given for reduce max_conn. Reducing the max_conn is not allowed for this release.

Recommended Action   No action is required.


Error Message   
%MSG802-6-SHUT_IN_PROG: shutdown in progress ... [chars] command rejected

Explanation   This message means that LLC is in shutdown cleanup state. All configuration commands are subsequently rejected.

Recommended Action   Retry the command when the LLC is in operational state.


Error Message   
%MSG802-6-START802_FAILED: unable to start 802 for [dec] connections - Memory Avail = [dec] bytes ([chars])

Explanation   This message means that CIP is not able to bring up the CTA 802 task, most likely because it is running out of resources (such as shortage of memory).

Recommended Action   Verify if overconfigured. Check the maximum number of connections configured. Report this error to your technical support representative.


Error Message   
%MSG802-6-THRESHOLD: Connection threshold is set to accept maximum [dec] connections

Explanation   CSNA is currently configured to accept the maximum number of connections per user command.

Recommended Action   No action is required.


Error Message   
%MSG802-3-UNKNOWN_EVENT: detect unknown event; event=[dec]

Explanation   The LLC task detected an unknown event.

Recommended Action   Report this error to your technical support representative.


Error Message   
%MSG802-3-UNSUPPORTED: [chars] ([chars])

Explanation   The LLC task detected an unsupported function being requested. The request is voided.

Recommended Action   Report this error to your technical support representative.

CMCC-NEVADA Error Messages

Error messages related to the CIP interrupt controller


Error Message   
%NEVADA-0-BADADD: Add: Invalid nevada interrupt code [dec]

Explanation   An attempt was made to specify an interrupt handler for an invalid interrupt type on the Nevada interrupt control chip. This is a fatal internal logic error.

Recommended Action   Report this error to your technical support representative.


Error Message   
%NEVADA-0-BADDISABLE: Disable: Invalid nevada interrupt code [dec]

Explanation   An attempt was made to disable an invalid interrupt type on the Nevada interrupt control chip. This is a fatal internal logic error.

Recommended Action   Report this error to your technical support representative.


Error Message   
%NEVADA-0-BADENABLE: Enable: Invalid nevada interrupt code [dec]

Explanation   An attempt was made to enable an invalid interrupt type on the Nevada interrupt control chip. This is a fatal internal logic error.

Recommended Action   Report this error to your technical support representative.


Error Message   
%NEVADA-0-BADENABLE2: Enable: No interrupt routine for code [dec]

Explanation   An attempt was made to enable an interrupt routine on the Nevada interrupt control chip, but there was no interrupt routine specified. This is a fatal internal logic error.

Recommended Action   Report this error to your technical support representative.


Error Message   
%NEVADA-0-BADINT: Interrupt received with no interrupt routine defined

Explanation   An interrupt was received for a code with no interrupt handler defined. This is a fatal internal logic error.

Recommended Action   Report this error to your technical support representative.


Error Message   
%NEVADA-0-BADREMOVE: Remove: Invalid nevada interrupt code [dec]

Explanation   An attempt was made to remove an interrupt handler for an invalid interrupt type on the Nevada interrupt control chip. This is a fatal internal logic error.

Recommended Action   Report this error to your technical support representative.

CMCC-OFFL Error Messages

CIP error messages related to the offload protocol


Error Message   
%OFFL-4-BADDESC: Socket descriptor [dec] in request is bad: state [chars] compare [dec]

Explanation   The host sent a socket request with an invalid socket descriptor. The CIP sent an error response to this socket request. This could be a host error or a CIP internal logic error.

Recommended Action   This message is followed by a dump of the request. Copy the error messages exactly as they appear, and report them to your technical support representative.


Error Message   
%OFFL-3-BADSEQ: Socket request [chars] should be last in sequence

Explanation   The host sent a socket request that should be the last in a sequence but is not. This error is caused either by an internal logic error, or by an incompatibility between the offload code on the mainframe and the offload code on the CIP.

Recommended Action   This message is followed by a hex dump of the offending sequence of offload messages. Copy the error messages exactly as they appear, and report them to your technical support representative.


Error Message   
%OFFL-6-COMMAND: Unrecognized offload command code [dec]. xfer_element = 0x[hex]

Explanation   The host sent an offload command with an invalid offload command code.

Recommended Action   The CIP has ignored the request. Report this error to your technical support representative.


Error Message   
%OFFL-7-HEX16B: [hex]: [hex][hex][hex][hex] [hex][hex][hex][hex] [hex][hex][hex][hex] [hex][hex][hex][hex] [chars]

Explanation   This message contains a hex dump of data associated with the immediately preceding error message.

Recommended Action   Forward a copy of the entire hex dump to your Cisco technical support representative.


Error Message   
%OFFL-7-HEX4W: [hex]: [hex] [hex] [hex] [hex] [chars]

Explanation   This message contains a hex dump of data associated with the immediately preceding error message.

Recommended Action   Forward a copy of the entire hex dump to your Cisco technical support representative.


Error Message   
%OFFL-3-ILLALD: Illegal data alignment: 0x[hex] + [dec] bytes >= 0x[hex]. xfer_element = 0x[hex]

Explanation   An internal logic error occurred. The data following an offload message header crossed a buffer boundary. The CIP ignored the message. This error message is usually an indication that the CIP received bad data. Examples of this are CLAW frames that are duplicated or arrive out of order. The offload messages contained in these corrupted CLAW frames are ignored, which can lead to hanging sessions or session loss.

Recommended Action   Check if there were any special events that coincided with this error message, such as an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears, issue the show tech-support command and call your technical service representative with the information.


Error Message   
%OFFL-3-ILLALH: Illegal hdr alignment at 0x[hex], [dec] bytes available

Explanation   An internal logic error occurred. An offload message header crossed a buffer boundary.

Recommended Action   The CIP ignored the request. Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%OFFL-3-ILLEN: Illegal byte count in offload data. [dec] specified, [dec] available. xfer_element = 0x[hex]

Explanation   An internal logic error occurred. The buffer length field in the offload message header does not equal the size of the data buffer.

Recommended Action   The CIP assumes the offload message header contains no data. Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%OFFL-0-ILLFREE1: SCB chain does not end with a read hdr

Explanation   An internal logic error occurred. A sequence of buffers was attempted to be freed, but was incomplete.

Recommended Action   Report this error to your technical support representative.


Error Message   
%OFFL-0-ILLFREE2: SCB ends with a read hdr with the MTC bit set

Explanation   An internal logic error occurred. A sequence of buffers was attempted to be freed, but was incomplete.

Recommended Action   Report this error to your technical support representative.


Error Message   
%OFFL-3-ILLNUM: Illegal number of socket requests. Rejected at [dec]

Explanation   The CIP received a CLAW frame with too many offload messages. This typically means that the mainframe has sent bad data to the offload device. Examples of this are CLAW frames that are duplicated or arrive out of order. The offload messages contained in these corrupted CLAW frames are ignored, which can lead to hanging sessions or session loss.

Recommended Action   Check if there were any special events that coincided with this error message, such as an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears, issue the show tech-support command and call your technical service representative with the information.


Error Message   
%OFFL-3-ILLRST: Received restart with [dec] intf, [dec] is max. xfer_element = 0x[hex]

Explanation   The host sent an offload restart request with too many defined interfaces.

Recommended Action   The CIP has ignored the request. Check your host configuration for this offload device. Report this error to your technical support representative.


Error Message   
%OFFL-6-LONGREC: Attempt to transmit too large a record

Explanation   The amount of data being read by the channel exceeded the size of the read CCW.

Recommended Action   Report this error to your technical support representative.


Error Message   
%OFFL-3-MISRST: Received restart [chars] with unknown IP [dec].[dec].[dec].[dec]

Explanation   The host sent an offload restart request with an unknown IP address for the API link.

Recommended Action   The CIP has ignored the mismatch. Correct your host configuration for this offload device.


Error Message   
%OFFL-0-NOMBUF: Out of mbuf's for handling socket operations

Explanation   An internal logic error occurred. Not enough memory buffers were allocated to handle the current offload socket operation.

Recommended Action   Report this error to your technical support representative.


Error Message   
%OFFL-3-NOMEM: Not enough memory to start offload tasks

Explanation   Not enough free memory is available to start the TCP/IP offload tasks. The configuration request was ignored.

Recommended Action   Install more memory for the CIP, or configure fewer devices.


Error Message   
%OFFL-3-NOMEM2: Not enough memory to process socket requests, [dec] open, [dec] in holddown

Explanation   Not enough free memory is available to process a socket request. The socket request failed.

Recommended Action   Install more memory for the CIP, configure fewer devices, or limit the number of sessions through this offload device.


Error Message   
%OFFL-3-NOMEMT: Insufficient memory ([chars]) for offload packet trace

Explanation   Not enough free memory is available for TCP/IP offload PKTTRACE. Tracing of a packet is skipped.

Recommended Action   Refine (limit) the PKTTRACE option on the mainframe to reduce the number of packets being traced.


Error Message   
%OFFL-0-NOPEND: Trying to free buffer when no send is pending. Operation: [dec]

Explanation   A request to free a send buffer was made even though there is no send pending. This is an internal logic error.

Recommended Action   Report this error to your technical support representative.


Error Message   
%OFFL-3-PENDREQ: Pending request [hex] deleted due to new request [hex]

Explanation   The offload application had to save a socket request for later execution while another request of the same type was pending. This is an internal logic error. The first request was dropped.

Recommended Action   Report this error to your technical support representative.


Error Message   
%OFFL-3-REGERR: Register of offload PKTTRACE failed. Packet tracing skipped

Explanation   An internal error occurred. The callback registry refused to add the offload tracing function to its list. Tracing of packets is skipped.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%OFFL-3-REJSOCK: Not enough memory to handle new socket. [dec] sockets open. [dec] in holddown

Explanation   Not enough free memory is available to open another socket. The socket request failed.

Recommended Action   Install more memory for the CIP, configure fewer devices, or limit the number of sessions through this offload device.


Error Message   
%OFFL-3-REQFORM: Socket request [dec] uses invalid parameters. Offset [dec]: [hex]

Explanation   The host sent a socket request with an invalid parameter. The CIP sent an error message in response to this request.

Recommended Action   Report this error to your technical support representative.


Error Message   
%OFFL-3-REQLEN: Socket request [dec] has illegal length [dec]

Explanation   The host sent a socket request with an incorrect length. The CIP sent an error message in response to this request.

Recommended Action   This message is followed by a hex dump of the offending offload message. Copy the error messages exactly as they appear, and report them to your technical support representative.


Error Message   
%OFFL-3-REQTYPE: Unknown [chars] socket request code [dec]

Explanation   The host sent a socket request with an unknown type.

Recommended Action   The CIP has ignored the request. Report this error to your technical support representative.


Error Message   
%OFFL-4-SENDERR: Bad serial number [hex] in send request - expected [hex]

Explanation   The host sent a send socket request that had an unexpected serial number in the header. This is most likely a bug on the host.

Recommended Action   The CIP sent an error response to the send socket request. The host TCP/IP stack will probably print the error message, "Unexpected result from Offload device...." Copy the error messages exactly as they appear, and report them to your technical support representative.


Error Message   
%OFFL-4-SOCLEFT: [dec] Sockets found after shutdown

Explanation   When the offload application quit, it detected sockets that were still waiting for cleanup. This is an internal logic error.

Recommended Action   This message should be preceded by other error messages that provide further information. Copy the error messages exactly as they appear, and report them to your technical support representative.


Error Message   
%OFFL-6-SOCREQ: Unrecognized socket request code [dec]

Explanation   The host sent a socket request with an invalid code.

Recommended Action   The CIP has ignored the request. Report this error to your technical support representative.


Error Message   
%OFFL-6-TRDISA: Offload PKTTRACE disabled

Explanation   The mainframe TCP/IP disabled PKTTRACE tracing. This can be caused by GTF being terminated or from a NOTRACE command.

Recommended Action   No action is required.


Error Message   
%OFFL-6-TRENAB: Offload PKTTRACE enabled

Explanation   The mainframe TCP/IP enabled tracing using PKTTRACE.

Recommended Action   No action is required.


Error Message   
%OFFL-4-TRRESU: Pending trace packets now [dec], tracing resumed ([dec])

Explanation   The number of outstanding trace packets pending to go to the mainframe has reached an acceptable level. Tracing of packets is resumed but some packets received or sent by this offload device were not traced during the suspension. The number in parenthesis is the number of times suspend occurred. It serves as a correlator to the suspend message.

Recommended Action   No action is required.


Error Message   
%OFFL-4-TRSUSP: Pending trace packet limit [dec] reached, tracing suspended ([dec])

Explanation   The limit of outstanding trace packets pending to go to the mainframe has been reached. Tracing of packets is suspended temporarily rather than continuing to flood the channel with trace data. This means that some of the packets received and/or sent by this offload device will not be traced. The number in parenthesis is the number of times suspend occurred. It serves as a correlator to the resume message.

Recommended Action   A message that indicates the resumption of tracing will be seen when the congestion abates. No action is required. However, reducing the amount of tracing might minimize such suspensions.


Error Message   
%OFFL-6-UNEXP: Unexpected offload command code [dec]

Explanation   An internal logic error occurred. The request type in the offload message was valid, but unexpected.

Recommended Action   The CIP has ignored the request. Report this error to your technical support representative.


Error Message   
%OFFL-6-VIRTOFFL: offload device may not be created on a virtual port adapter

Explanation   An attempt was made to configure an offload device on the virtual port adapter. Offload devices are permitted on physical port adapters only.

Recommended Action   The configuration request was ignored. No action is required.


Error Message   
%OFFL-6-WRCHAIN: Received too long message, xfer_element 0x[hex] chains to 0x[hex]

Explanation   The offload application received a message consisting of more than one xfer_element. This is currently not supported.

Recommended Action   Report this error to your technical support representative.


Error Message   
%OFFL-6-WRITEREAD: Host Wrote data on read subchannel

Explanation   The mainframe wrote data to the read subchannel. This is most likely the result of a misconfiguration under a VM guest where the write device is attached to the read subchannel.

Recommended Action   Check the device definitions on the host and if running under VM, verify that the write device is attached to the write subchannel and the read device is attached to the read subchannel.


Error Message   
%OFFL-4-WRONGDESC: Wrong descriptor type in purge request, descriptor [hex] [chars]found (position [dec])

Explanation   The host sent a purge socket request that contained the host descriptor instead of the offload box descriptor. This is most likely a bug or an obscure feature on the host. If the CIP found the specified host descriptor, it processed the purge request. Otherwise, it ignored it.

Recommended Action   If this error message occurs occasionally and does not coincide with any other problems, it can be ignored. If it occurs several times per day, it should be reported to your technical service representative because it could be an indication of an application problem or a network problem between the mainframe and a client workstation. You must supply the following information when reporting this problem:


Error Message   
%OFFL-0-WRONGFREE: Trying to free mbuf out of sequence

Explanation   An internal logic error occurred. An unexpected address was specified in a request to free a buffer

Recommended Action   Report this error to your technical support representative.

CMCC-PACK Error Messages

CMCC error messages related to the Packed extension to the Common Link Access to Workstation (CLAW) facility


Error Message   
%PACK-3-BADLEN: Invalid length in CLAW packed control message - act [dec], exp [dec]

Explanation   A control message was received under the packed CLAW link and the length did not match that of a known packed control message.

Recommended Action   Get a GTF and/or a channel trace to verify that the host is sending the bad packed message.


Error Message   
%PACK-3-BADSCBQ: Found data queued with channel queue partially empty

Explanation   After a packet was received, the packed driver detected that packed data was waiting to be queued even though the channel queue was partially empty

Recommended Action   This is an internal logic error. Report this error to your technical support representative.


Error Message   
%PACK-0-BADSIZE: Invalid size in connection request- [dec] R, [dec] W; defined - [dec] R [dec] W

Explanation   In a packed connection request, either a requested read size was smaller than the defined packed type or a requested write size was larger than the defined packed type.

Recommended Action   Report this error to your technical support representative.


Error Message   
%PACK-0-BADSIZE2: Packed type names:[chars] - [chars]

Explanation   This message lists the packed type names that experienced the BADSIZE-PACK error.

Recommended Action   Report this error to your technical support representative.


Error Message   
%PACK-3-BADSTATE: Claw packed sublink [dec] is in an unknown state [dec]. Path=[hex][hex][hex] device=[hex] link=[hex]

Explanation   A packet was received from the host on a packed sublink for which the state was unknown. This is a logic error.

Recommended Action   The packet was dropped. Report this error to your technical support representative.


Error Message   
%PACK-0-BADTYPE: Host Packed names [chars] - [chars] do not match any configured names

Explanation   An attempt was made to establish a packed connection but the packed type names specified on the host do not match any of the packed names specified in the CMCC.

Recommended Action   Correct the host configuration or upgrade the CMCC microcode to a version that supports the packed type specified by the host.


Error Message   
%PACK-0-BADTYPE2: Supported packed type names: [chars] - [chars]

Explanation   An attempt was made to establish a packed connection but the packed type names specified on the host do not match any of the packed names specified in the CMCC.

Recommended Action   Correct the host and/or router configuration.


Error Message   
%PACK-0-BADVERSION: Host CLAW Packing version [dec] does not equal CMCC version [dec]

Explanation   The version specified in a packed CLAW message from the host is not the same as the version specified in the CMCC.

Recommended Action   Report this error to your technical support representative.


Error Message   
%PACK-6-COMMAND: Unrecognized CLAW packing control command code [dec]

Explanation   The host sent a CLAW packing control command with an invalid command code.

Recommended Action   The CMCC ignored the request. Get a GTF and/or a channel trace to verify that the host is sending the bad packed message.


Error Message   
%PACK-6-CTLERROR: Packed control error message received with return code of [dec]

Explanation   The host rejected a prior CLAW packed control message sent by the CMCC.

Recommended Action   Check the return code and correct as appropriate.


Error Message   
%PACK-3-ILLEN: Not enough data left in buffer for packed message - remaining [dec], length [dec]

Explanation   The host wrote a block of packed messages and the length of the lock was inconsistent with the size of the packed messages.

Recommended Action   Get a GTF and/or a channel trace to verify that the host is sending the bad packed message.


Error Message   
%PACK-3-ILLEN2: Received zero length packed message

Explanation   The host wrote a block of packed messages and the length of a packed message was zero. This is an invalid size.

Recommended Action   Get a GTF and/or a channel trace to verify that the host is sending the bad packed message.


Error Message   
%PACK-6-NOCONN: Channel wrote data on sublink [dec] without a valid connection. Path=[hex][hex][hex] device=[hex] link=[hex]

Explanation   A packet was received from the host but the packed sublink specified with the data does not represent a valid connection.

Recommended Action   The packet was dropped. Report this error to your technical support representative.


Error Message   
%PACK-0-NOLINKID: Unable to allocate sublink id for CLAW packing sublink

Explanation   An attempt was made to allocate a sublink ID to assign to a connection request, but all sublink IDs were in use. This error should not occur.

Recommended Action   The CMCC recovered by generating a bad return code to the requestor. Report this error to your technical support representative.


Error Message   
%PACK-3-NOMBUF: Couldn't allocate a new MBUF from the CLAW Packing pool

Explanation   This message indicates a design error. There should always be enough MBUFs for packed CLAW data.

Recommended Action   Contact your technical support representative.


Error Message   
%PACK-3-NOMORE: Packed sublink [dec] doesn't support the more bit

Explanation   The host sent a packet message on a sublink with the more bit on, even though that sublink does not support the more bit.

Recommended Action   Get a GTF and/or a channel trace to verify that the host is sending the bad packed message.


Error Message   
%PACK-6-NOTPRESENT: CLAW Packing sublink [dec] being freed was not present

Explanation   The host software attempted to disconnect a CLAW packing sublink that was not established.

Recommended Action   The CMCC ignored the request. Report this error to your technical support representative.


Error Message   
%PACK-6-RANGE: CLAW packing sublink [dec] being freed is out of range

Explanation   The CLAW packing sublink ID in a disconnect is not in the valid range for all CLAW packed sublinks.

Recommended Action   The CMCC recovered by ignoring this request. Report this error to your technical support representative.


Error Message   
%PACK-6-RANGE2: Out of range sublink ([dec]) received in packed claw message

Explanation   The CLAW packing sublink ID in a packed message is not in the valid range for all CLAW packed sublinks.

Recommended Action   The CMCC has recovered by ignoring this request. Report this error to your technical support representative.


Error Message   
%PACK-0-SYSMGT_ERROR1: CLAW detected error in sysmgt call: invalid CLAWPACK CONTROL length

Explanation   An invalid parameter was received in a sysmgt call.

Recommended Action   Report this error to your technical support representative.


Error Message   
%PACK-0-SYSMGT_ERROR2: CLAW detected error in sysmgt call: invalid CLAWPACK SUBLINK length

Explanation   An invalid parameter was received in a sysmgt call.

Recommended Action   Report this error to your technical support representative.


Error Message   
%PACK-3-TOOLARGE: Received [dec] byte message on packed sublink [dec] - max is [dec]

Explanation   The host sent a packed message on a sublink that was larger than the write size negotiated during the Packed Connection Request sequence.

Recommended Action   Get a GTF and/or a channel trace to verify that the host is sending the bad packed message.

CMCC-PKTS Error Messages

Channel adapter error messages related to the packet switching API


Error Message   
%PKTS-3-BUFLEN: Zero length buffer detected in [chars] for [chars]([hex])

Explanation   An application buffer error was detected in the channel adapter packet switching API.

Recommended Action   Report this message to your technical support representative.


Error Message   
%PKTS-3-CONSISTENCY: [chars] : [chars] [hex] [dec]

Explanation   A consistency error was detected in the channel adapter packet switching API.

Recommended Action   Report this message to your technical support representative.


Error Message   
%PKTS-3-INIT: [chars] ([dec])

Explanation   The CMCC packet switching initialization failed because of a lack of memory on the card. Packets will not be switched between the CMCC card and the route processor.

Recommended Action   Verify that the MCC card is capable of supporting the configured CMCC microcode. Also verify the amount of memory installed.


Error Message   
%PKTS-3-NOSUPP: [chars] ([dec])

Explanation   An attempt was made to call a function in a packet switching API control block that was not implemented or supported.

Recommended Action   Report this message to your technical support representative.


Error Message   
%PKTS-3-NOTREADY: packet switching API not initialized - [chars]

Explanation   An attempt was made to call a function in a packet switching API before the initialization was complete.

Recommended Action   Report this message to your technical support representative.


Error Message   
%PKTS-3-SEGMENT: [chars] : [chars] [hex] [dec]

Explanation   A data buffer was detected that contains too many segments or particles to transmit to the platform route processor. The packet was dropped.

Recommended Action   Report this message to your technical support representative.

CMCC-SCB Error Messages

CIP error messages related to the storage control block


Error Message   
%SCB-6-BADSCB: Request to free SCB 0 ignored

Explanation   An attempt was made to free SCB 0. This is an internal logic error. The request was ignored.

Recommended Action   Report this message to your technical support representative.


Error Message   
%SCB-6-RESUME: SCB on port [dec] available, correlator: [dec] task: [chars] [hex], MSGDEF_LIMIT_GLACIAL

Explanation   A task waiting for a channel storage control block woke up. This message is typically preceded by the message, "SCB limit on port reached." The correlator value in this message and the following message indicate that the two messages form a pair. In most cases, the pair of messages indicates a burst of activity that resulted in an unusually long queue for the channel.

Recommended Action   This is an informational message. No action is required.


Error Message   
%SCB-6-WAIT: SCB limit on port [dec] reached, correlator: [dec] task: [chars] [hex], MSGDEF_LIMIT_GLACIAL

Explanation   A task tried to allocate a channel storage control block when all blocks were in use. The task is now waiting for a block to become available. This message is typically followed by the message, "SCB on port available." The correlator value in this message and the following message indicate that the two messages form a pair. In most cases, the pair of messages indicates a burst of activity that resulted in an unusually long queue for the channel.

Recommended Action   If this message is followed by any kind of indication that the CIP stopped working properly, report it to your technical support representative, along with the output of the following commands:

In addition, check the multiple virtual storage (MVS) syslog and the TCPIP joblog (or equivalent for other mainframe operating systems) for unusual channel-related messages. Pay particular attention to anything related to TCP/IP offload.

CMCC-SCHED Error Messages

Error messages related to the scheduler, the facility responsible for determining which process to run at a given time on the CIP


Error Message   
%SCHED-0-BADPRIORITY: Task priority of [dec] is not allowed.

Explanation   A request was made to create a process, but the priority for the process was not valid. The process was not created.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SCHED-0-INVLOCK1: Invalid lock word of [dec] used in lock request

Explanation   An attempt was made to request a lock, but the lock word contained invalid data. This is a fatal internal logic error.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SCHED-0-INVLOCK2: Invalid lock word of [dec] used in unlock request

Explanation   An attempt was made to unlock a lock, but the data in the lock word was not valid. This is a fatal internal logic error.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SCHED-0-NMLDATA: tcb_addr = 0x[hex] current_tcb = 0x[hex] lock_value = [dec]

Explanation   This message contains data that relates to the "SCHED-0-NOTMYLOCK" message.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SCHED-0-NOLOCK: Attempt was made to unlock resource that wasn't locked

Explanation   An attempt was made to unlock a lock that was not held. This is a fatal internal logic error.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SCHED-0-NOPROCID: No process id available for task creation

Explanation   An attempt was made to create more tasks than the CIP is designed to allow. The process was not created.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SCHED-0-NOSTACK: Could not allocate [dec] bytes for stack from SRAM

Explanation   An attempt was made to create a process and not sufficient storage was available to contain the stack for the process. The process was not created.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SCHED-0-NOTCB: Could not allocate [dec] bytes for tcb from SRAM

Explanation   An attempt was made to create a process and sufficient storage was not available to contain the control block for the process. The process was not created.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SCHED-0-NOTMYLOCK: Attempt was made to unlock another task's resource

Explanation   An attempt was made to unlock a lock that was set by another task. This is a fatal internal logic error.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SCHED-0-NOTPROCES: Attempt was made to lock while not at process level

Explanation   An attempt was made to lock while not at the process level. This is a fatal internal logic error.

Recommended Action   Report this error to your technical support representative.

CMCC-SLC Error Messages

CIP error messages related to the serial link controller


Error Message   
%SLC-3-PCANMIRESET: Reset of Port [dec] NMI failed

Explanation   After servicing a Non-Maskable Interrupt from a PCA interface, the attempt to reset the interrupt failed.

Recommended Action   Report this message to your technical support representative.


Error Message   
%SLC-3-SCANEP1: Scan of EP ring 1 failed

Explanation   An attempt to scan the first set of internal latches on the Enterprise Systems Connection (ESCON) processor failed.

Recommended Action   Report this message to your technical support representative.


Error Message   
%SLC-3-SCANEP2: Scan of EP ring 2 failed

Explanation   An attempt to scan the second set of internal latches on the Enterprise Systems Connection (ESCON) processor failed.

Recommended Action   Report this message to your technical support representative.


Error Message   
%SLC-3-SCANSLC: Scan of SLC ring failed

Explanation   An attempt to scan the internal latches of the serial link controller failed.

Recommended Action   Report this message to your technical support representative.


Error Message   
%SLC-3-STOPBIDITO: Stop BIDI clock timed out

Explanation   An attempt was made to stop the clock on the interface between the Enterprise Systems Connection (ESCON) processor and the serial link controller. The serial link controller did not indicate that the clock was stopped.

Recommended Action   Report this message to your technical support representative.


Error Message   
%SLC-3-STOPEPTO: Stop EP clock timed out

Explanation   An attempt was made to stop the clock on the Enterprise Systems Connection (ESCON) processor. The serial link controller did not indicate that the clock was stopped. The CIP attempted to stop the BIDI clock.

Recommended Action   Report this message to your technical support representative.

CMCC-SLCI Error Messages

CIP error messages related to the SLC Interface


Error Message   
%SLCI-3-BAD_TYPE_CODE: PA[dec] MPC [hex]-[hex] got unrecognized xfer_list type code

Explanation   This error message is given when an MPC process receives a xfer_list with an unrecognized type code.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SLCI-3-INBOUND_FSM_ERR: PA[dec] MPC [hex]-[hex] Event [chars], State [chars]

Explanation   This error message is given when an internal state machine attempts to execute an event inconsistent with the state.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SLCI-3-INFLOW_FSM_ERR: PA[dec] MPC [hex]-[hex] Event [chars], State [chars]

Explanation   This error message is given when an internal state machine attempts to execute an event inconsistent with the state.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SLCI-0-NOMEM: Attempt to acquire memory failed, pc: [hex]

Explanation   This error message is given when a call to create a pool or get a buffer fails.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SLCI-0-STASH_ADR_ERR: PA[dec] MPC [hex]-[hex] Stash check failed, mbuf addr [hex] and SCB addr [hex]

Explanation   The error message is given when the internal stash validation fails on mismatch between an mbuf data address and a storage control block (SCB) data address.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SLCI-0-STASH_EMPTY: Stash empty on read complete

Explanation   The error message is given when a read operation completes, but there was no stashed data.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SLCI-0-STASH_MORE_MBUFS: PA[dec] MPC [hex]-[hex] Stash check failed, more mbufs than SCBs

Explanation   The error message is given when the internal stash validation fails because the mbuf chain is longer than the storage control block (SCB) chain.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SLCI-0-STASH_MORE_SCBS: PA[dec] MPC [hex]-[hex] Stash check failed, more SCBs than mbufs

Explanation   The error message is given when the internal stash validation fails because the storage control block (SCB) chain is longer than the mbuf chain.

Recommended Action   Report this error to your technical support representative.

CMCC-SSI802 Error Messages

CIP SSI802 error messages related to the common service System Service Interface (SSI) facility


Error Message   
%SSI802-6-DUMP: [chars]

Explanation   This message is used by the dump utility to display the hex dump of storage.

Recommended Action   No action is required.


Error Message   
%SSI802-3-FATAL_ERROR: SSI_ASSERT failure in [chars] @ [int] - [chars]

Explanation   The CSNA encountered unrecoverable error conditions that prevent it from continuing its normal operations.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SSI802-3-RTN_ADR: Return Address: 0x[hex]

Explanation   This is a debug feature to show the return address when an ASSERT is used in an inline function.

Recommended Action   Action according to subsequent error.

CMCC-SUBSYS Error Messages

Software subsystem error messages


Error Message   
%SUBSYS-2-BADCLASS: Bad subsystem class ([dec]) - ignoring subsystem

Explanation   A software consistency check failed.

Recommended Action   Call your technical support representative for assistance.


Error Message   
%SUBSYS-2-BADSEQUENCE: Subsystem ([chars]) has cross-class sequence for ([chars])

Explanation   A software consistency check failed.

Recommended Action   Call your technical support representative for assistance.


Error Message   
%SUBSYS-2-BADVERSION: Bad subsystem version number ([dec]) - ignoring subsystem

Explanation   A software consistency check failed.

Recommended Action   Call your technical support representative for assistance.


Error Message   
%SUBSYS-2-MAXRECUR: Too many levels of recursion

Explanation   A software consistency check failed.

Recommended Action   Call your technical support representative for assistance.


Error Message   
%SUBSYS-2-MISMATCH: Kernel and subsystem version differ ([dec].[dec]) - ignoring subsystem

Explanation   A software consistency check failed.

Recommended Action   Call your technical support representative for assistance.


Error Message   
%SUBSYS-2-NOTFOUND: Subsystem ([chars]) needs subsystem ([chars]) to start

Explanation   A software consistency check failed.

Recommended Action   Call your technical support representative for assistance.

CMCC-SYS Error Messages

CIP operating system error messages


Error Message   
%SYS-3-BADBLOCK: Bad block pointer [hex]

Explanation   A block of memory is corrupt at the indicated location.

Recommended Action   If this message recurs, call your technical support representative for assistance.


Error Message   
%SYS-3-BADFREEMAGIC: Corrupt free block at [hex] (magic [hex])

Explanation   A block of memory is corrupt at the indicated location.

Recommended Action   If this message recurs, call your technical support representative for assistance.


Error Message   
%SYS-3-BADFREEPTRS: Bad [chars] pointer [hex] at [hex] ([chars] = [hex])

Explanation   A pointer in the block header at the indicated location is corrupt.

Recommended Action   If this message recurs, call your technical support representative for assistance.


Error Message   
%SYS-3-BADMAGIC: Corrupt block at [hex] (magic [hex])

Explanation   The free memory pool is corrupted.

Recommended Action   Call your technical support representative for assistance.


Error Message   
%SYS-2-BADSHARE: Bad refcount in [chars], ptr=[hex], count=[hex]

Explanation   An internal software error has occurred.

Recommended Action   If this message recurs, call your technical support representative for assistance.


Error Message   
%SYS-6-BLKINFO: [chars]blk [hex], words [int], alloc [hex], [chars], dealloc [hex], rfcnt [hex]

Explanation   An internal software error has occurred.

Recommended Action   If this message recurs, call your technical support representative for assistance.


Error Message   
%SYS-3-CACHE_DIRTY_ADR: cache line 0x[hex] dirty, task: [chars]

Explanation   This error message reports the address at which a scancache operation detected that cache was not flushed as expected.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SYS-6-CACHE_DIRTY_MSG: [chars][chars]

Explanation   This message provides additional information about a CACHE_DIRTY_ADR message.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SYS-3-CACHED_PAGE_ADR: Uncached page pointer 0x[hex] in call to return_page_inline

Explanation   The pointer to a page being returned to the page pool was a cached address.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SYS-2-FREEBAD: Attempted to free memory at [hex], not part of buffer pool

Explanation   An internal software error has occurred.

Recommended Action   If this message recurs, call your technical support representative for assistance.


Error Message   
%SYS-2-FREEFREE: Attempted to free unassigned memory at [hex], alloc [hex], dealloc [hex]

Explanation   An internal software error has occurred.

Recommended Action   If this message recurs, call your technical support representative for assistance.


Error Message   
%SYS-3-INUSEFREE: Block [hex] on free list [dec] in use

Explanation   An internal software error has occurred.

Recommended Action   If this message recurs, call your technical support representative for assistance.


Error Message   
%SYS-3-INVMEMINT: Invalid memory action ([chars]) at interrupt level

Explanation   This message indicates that a memory allocation or deallocation was attempted from an interrupt handler.

Recommended Action   If this message recurs, call your technical support representative for assistance.


Error Message   
%SYS-2-LOWMEM: Low memory debug exception (limit=[int] free=[int])

Explanation   The CIP is running short on memory.

Recommended Action   It may be necessary to free some memory by exiting a program. If this message recurs, call your technical support representative for assistance.


Error Message   
%SYS-2-MEMTOOSMALL: CIP software requires a minimum of 8MB of DRAM

Explanation   The CIP software has become large enough that it will not run with only 2 MB of DRAM.

Recommended Action   Contact your support representative for a free 8 MB upgrade.


Error Message   
%SYS-6-MTRACE: [chars]: addr, pc ADDRPC ADDRPC ADDRPC ADDRPC ADDRPC ADDRPC ADDRPC ADDRPC

Explanation   The free memory pool is corrupted.

Recommended Action   If this message recurs, contact your technical support representative for assistance.


Error Message   
%SYS-2-NOMEMFRG: Memory fragmentation check debug exception (fragment size [int])

Explanation   The system detected an error while checking memory fragmentation.

Recommended Action   If this message recurs, call your technical support representative for assistance.


Error Message   
%SYS-2-NOMEMORY: No memory available for [chars] [dec]

Explanation   An operation could not be accomplished because of a low-memory condition.

Recommended Action   Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


Error Message   
%SYS-3-NZREFCNT: Block [hex] on free list [dec] with ref count [dec]

Explanation   A block of memory in the free pool is actually in use. The number of processes using the memory block is indicated.

Recommended Action   If this message recurs, call your technical support representative for assistance.


Error Message   
%SYS-3-OVERRUN: Block overrun at [hex] (redzone [hex])

Explanation   An internal software error has occurred.

Recommended Action   If this message recurs, contact your technical support representative for assistance.


Error Message   
%SYS-5-RELOAD: Reload requested

Explanation   A reload or restart has been requested.

Recommended Action   This is a notification message only. No action is required.


Error Message   
%SYS-5-RESTART: System restarted --[chars]

Explanation   A reload or restart has been requested.

Recommended Action   This is a notification message only. No action is required.


Error Message   
%SYS-3-WRONGFREELIST: Block [hex], size [dec], on wrong free list ([dec], [dec])

Explanation   A freed buffer has been placed on the wrong list of free buffers.

Recommended Action   If this message recurs, call your technical support representative for assistance.

CMCC-SYSMGT_EVENT Error Message

CIP error message related to network management processing for system management event generation


Error Message   
%SYSMGT_EVENT-4-ERROR: [chars] - [chars]([chars])

Explanation   This message indicates a System Management event sending operation failure. Traps, alerts, and console messages for a channel event will not be generated.

Recommended Action   If this error recurs, report it to your technical support representative.

CMCC-SYSMGT_RPC Error Messages

CIP error messages related to network management processing for system management remote procedure calls


Error Message   
%SYSMGT_RPC-3-ERROR: Error detected ([chars])

Explanation   A system error has been detected in the Systems Management Remote Procedure Call processing.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SYSMGT_RPC-3-IPC_ERROR: [chars] [chars] failed ([chars]), MSGDEF_LIMIT_GLACIAL

Explanation   This message indicates a System Management Remote Procedure Call operation failure. Request for information from the channel adapter card will not be processed.

Recommended Action   Report this error to your technical support representative.


Error Message   
%SYSMGT_RPC-3-NOMEM: [chars]

Explanation   Channel adapter system management could not initialize because of a lack of memory available on the channel adapter. Since the channel adapter SYSMGT component was unable to initialize, most show extended channel command information and all channel adapter event notifications will not be available to the user.

Recommended Action   Upgrade the channel adapter with more memory.


Error Message   
%SYSMGT_RPC-6-STATE_CHANGE: System Management [chars]

Explanation   The channel adapter System Management subsystem has changed state.

Recommended Action   This is an informational message only. No action is required.


Error Message   
%SYSMGT_RPC-4-UNKNOWN: [chars] request for class [dec] contains unknown [chars] [dec]

Explanation   The channel microcode received a sysmgt request on the this port (either clear or query) with an unknown code.

Recommended Action   Check your microcode version to ensure that it agrees with the Cisco IOS release.

CMCC-TCPIP Error Message

TCP/IP error message


Error Message   
%TCPIP-0-PANIC: panic[[chars]@[dec]] in [chars]: [chars]

Explanation   An unexpected internal error occurred in the TCP/IP stack.

Recommended Action   Check if there were any special events that coincided with this error message, such as an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears, issue the show tech-support command and call your technical service representative with the information.

CMCC-TN3270 Error Messages

Error messages related to the TN3270 server feature of the CIP card


Error Message   
%TN3270S-4-BAD_MAX_LUS_CFG: Could not change maximum LUs to [dec]

Explanation   The TN3270 server could not change the maximum number of LUs to the requested value. The previous number is still in use.

Recommended Action   Review the previous error messages to discover what caused the failure, and take action based on those messages.


Error Message   
%TN3270S-6-BADTIMER: Bad timer operation([dec]),ra=%lx,funcPtr=%lx

Explanation   A bad timer operation was detected, and the timer operation was aborted. The rest of the information is useful for developers to debug the problem. Such bad-timer occurrences are usually harmless, but are reported because they may be indicative of a more serious problem.

Recommended Action   Report this problem to your technical support representative. Since the error message reflects an internal program logic error, this problem should always be reported.


Error Message   
%TN3270S-1-CREATE_MUXWAIT_FAILED: A TN3270 server related semaphore could not be created.

Explanation   An important semaphore could not be created.This is either because of memory shortage or some internal code error.

Recommended Action   This is most probably because of insufficient memory on the board. Upgrade your board with additional memory. If you believe sufficient memory is on the board, it is possible that there is a memory leak. Report details of your configuration, output from the show controllers cxbus command, and any action you must do to reproduce this problem to your technical support representative.


Error Message   
%TN3270S-1-CREATE_POOL_FAILED: A TN3270 server related buffer pool could not be created.

Explanation   An important buffer pool could not be created. This is either because of memory shortage or some internal code error.

Recommended Action   This is most probably because of insufficient memory on the board. Upgrade your board with additional memory. If you believe sufficient memory is on the board, it is possible that there is a memory leak. Report details of your configuration, output from the show controllers cxbus command, and any action you must do to reproduce this problem to your technical support representative.


Error Message   
%TN3270S-1-CREATE_THREAD_FAILED: A TN3270 server related thread could not be started

Explanation   An important thread could not be created. This is either because of memory shortage or some internal code error.

Recommended Action   This is most probably because of insufficient memory on the board. Upgrade your board with additional memory. If you believe sufficient memory is on the board, it is possible that there is a memory leak. Report details of your configuration, output from the show controllers cxbus command, and any action you must do to reproduce this problem to your technical support representative.


Error Message   
%TN3270S-4-DDDLU_NOT_SUPPORTED: Host does not support dddlu at IP addr [chars], port [dec], 600*ONESEC

Explanation   TheTN3270 server cannot complete one or more connection requests from a TN3270/E client because the host does not support dynamic definition of dependent LUs (DDDLU).

Recommended Action   Check that all PUs configured for use with DDDLU have the LUGROUP operand defined. Also, check that the specified VTAM LUGROUP major node is active.


Error Message   
%TN3270S-4-FUNC_NEGOT_LOOP: Client [chars]:[dec] in loop on TN3270E function negotiation [dec]., 600*ONESEC

Explanation   The client software is not behaving as per RFC.

Recommended Action   Try to locate the TN3270 client that caused the problem. There could be a bug in the client.


Error Message   
%TN3270S-0-ILLEGAL_CCMUTEX_RELEASE: Releasing unacquired semaphore, lock_held [hex] lock_value [hex] ccMutex tcb [hex] thread tcb [hex]

Explanation   An exclusive lock is being released illegally by the executing thread. The lock is either held by no one or by some other thread.

Recommended Action   To recover, you must microcode reload the CIP. Since this problem is very serious, you might get this error again. In any case, send output of this message and tasks on CIP console to your technical support representative. Also, send your configuration and any action you must do to get this problem.


Error Message   
%TN3270S-4-ILLEGAL_SUBOPTION: Client [chars]:[dec] sent Telnet suboption [dec] illegally

Explanation   The client software is not behaving as per RFC.

Recommended Action   Try to locate the TN3270 client that caused the problem. There could be a bug in the client.


Error Message   
%TN3270S-1-LISTENFAIL: Listening on [hex] [dec] Failed; err [dec]

Explanation   There was an attempt to bring up a PU, but listening on the corresponding TCP/IP port could not be started.

Recommended Action   Check that sufficient memory is present on the CIP card. Report this error to your technical support representative.


Error Message   
%TN3270S-2-LOW_MEM: Insufficient memory for TN3270 server, [dec] KBytes available, [dec] required

Explanation   Insufficient memory prevents proper operation of TN3270 server.

Recommended Action   Ensure that enough memory is available on the board. Upgrade the memory on the board or cancel other services running on the CIP. If you believe sufficient memory is on the board, it is possible that there is a memory leak. Report details of your configuration, output from the show controllers cxbus command, and any action you must do to reproduce this problem to your technical support representative.


Error Message   
%TN3270S-1-LU_ERROR: lu error [chars]: [chars]:[dec] pu:[hex], tnet:[hex]

Explanation   An unexpected event was presented to the LU named by the LOCADDR and PU. The error may cause the TN3270 session to not work properly. More detail on this error is contained in the "LU_ERROR_INFO" messages immediately following this message.

Recommended Action   Report this problem to your technical support representative.


Error Message   
%TN3270S-1-LU_ERROR_INFO: LU info: Event [chars], state = [hex], snaState = [hex], flag = [hex]

Explanation   This message shows information about the LU state, history, and flags before the error happened.

Recommended Action   Report this problem to your technical support representative.


Error Message   
%TN3270S-1-LU_NO_BUFFER: No buffer for lu: [chars]

Explanation   Some preallocated LU buffers for transmission have run out. The transmission of the message is aborted. The LU session is left incomplete. In addition, the LU session could hang.

Recommended Action   Use the show command to find out as much as possible about the LU state and report the information to your technical support representative.


Error Message   
%TN3270S-6-LU_THRESHOLD: Warning: TN3270 sessions are at [dec]%% of maximum-lus

Explanation   This message indicates that the number of LU sessions is approaching the configured maximum-lus setting.

Recommended Action   No action is required.


Error Message   
%TN3270S-1-MEMORY_SHORTAGE: Insufficient memory on board; failed to allocate [dec] bytes

Explanation   Memory could not be allocated for an important operation.

Recommended Action   Upgrade your board for additional memory. If you believe sufficient memory is on the board, it is possible that there is a memory leak. Report details of your configuration, output from the show controllers cxbus command, and any action you must do to reproduce this problem to your technical support representative.


Error Message   
%TN3270S-1-NAIL_NOT_FOUND: Deletion of the Client IP ([chars]) LU Nailing first ([dec]) to last ([dec]) from PU ([dec]) failed because the configuration was not found

Explanation   Deletion of the Client IP LU Nailing command failed because it could not be found.

Recommended Action   No action is required.


Error Message   
%TN3270S-1-NegRsp_NO_CORRELATOR: TN3270E negative response correlation: [chars].[dec], client IP addr [chars], nextSqn=[dec], rspSqn=[dec], 600*ONESEC

Explanation   A TN3270E client sent a negative response to a TN3270 request sent previously by the server. The negative response does not have a sequence number that can be correlated by the server.

Recommended Action   Determine the DLOGMOD used for the session. Review the outbound pacing bits used for this session and ensure that the pacing value is no bigger than 4. If the message recurs, contact the client software vendor and lodge a problem report.


Error Message   
%TN3270S-1-NO_BIND_REQ_RCVD: No BIND REQ received on LU [chars].[dec], 120*ONESEC

Explanation   Either a BIND REQUEST or SSCP-LU data was expected (but not received) from the host within 30 seconds from the start of SSCP-LU session for this TN3270 session. If the condition persists for another 2 minutes, the LU is declared bad. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening point are in use.

Recommended Action   Examine the system services control point (SSCP) host VTAM console for status of the specified PU and LU. Review the VTAM console log output for relevant events (such as deactivation of the PU or LU). If, after VTAM console review, the cause is still unknown, report this error to your technical support representative. A temporary workaround is simply to recycle the affected LU at the VTAM console. This will put the LU back into normal circulation.


Error Message   
%TN3270S-1-NO_DYN_ACTLU_REQ_RCVD: No ACTLU REQ received on LU [chars].[dec], 120*ONESEC

Explanation   The host has not sent an ACTLU REQ within 30 seconds of sending a Reply-PSID RSP. If this condition persists for another 2 minutes, the current TN3270 session connected to the LU is disconnected. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening point are in use.

Recommended Action   Examine the system services control point (SSCP) host VTAM console for status of the specified PU and LU. Review the VTAM console log output for relevant events (such as deactivation of the PU or LU). If, after VTAM console review, the cause is still unknown, report this error to your technical support representative. A temporary workaround is simply to recycle the affected LU at the VTAM console. This will put the LU back into normal circulation.


Error Message   
%TN3270S-1-NO_EVENT_BUFS: No IPC sysmgt event buffers for at least one minute , 600*ONESEC

Explanation   The TN3270 server has events that will result in SNMP traps and/or SNA Alerts, but has not been able to allocate IPC buffer resources to report the events to router system code. The TN3270 server will continue to try to report these events, but lack of buffers may continue until a CIP microcode reload is performed.

Recommended Action   Report this problem to your technical representative. Include output from the following commands:

As a workaround, reload the CIP microcode.


Error Message   
%TN3270S-1-NO_LU_MEMORY: No memory on the CIP was available for completing a requested TN3270 LU session

Explanation   Insufficient memory is available to the TN3270 server to complete one or more requests by TN3270/E clients for LU sessions. The sessions have been disconnected.

Recommended Action   Review the memory required to run the TN3270 server application in light of current client load. Install additional memory, if necessary.


Error Message   
%TN3270S-4-NO_LU_SESSIONS: No LU sessions left for PUs at IP addr [chars], port [dec], 600*ONESEC

Explanation   The TN3270 server cannot complete one or more connection requests from a TN3270/E client because no more available LUs are left in the generic pool associated with the specified IP listening-point address.

Recommended Action   Review the LU requirements for the application endpoints. Configure additional PUs listening at the specified IP address and port number.


Error Message   
%TN3270S-1-NO_NAIL_MEMORY: Insufficient memory available on the cip for Client IP LU Nailing

Explanation   There is insufficient memory available to complete the Client IP LU Nailing configuration on the CIP.

Recommended Action   No action is required.


Error Message   
%TN3270S-1-NO_NTFY_AV_RSP_RCVD: No NOTIFY(available) RSP received on LU [chars].[dec], 120*ONESEC

Explanation   No response to a power-on (AVAILABLE) NOTIFY request was received by the TN3270 server within 30 seconds of sending it to the host. If this condition persists for another 2  minutes, the current TN3270 session connected to the LU is disconnected. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening point are in use.

Recommended Action   Examine the system services control point (SSCP) host VTAM console for status of the specified PU and LU. Review the VTAM console log output for relevant events (such as deactivation of the PU or LU). If, after VTAM console review, the cause is still unknown, report this error to your technical support representative. A temporary workaround is simply to recycle the affected LU at the VTAM console. This will put the LU back into normal circulation.


Error Message   
%TN3270S-1-NO_NTFY_UA_RSP_RCVD: No NOTIFY(UA) RSP received on LU [chars].[dec], 120*ONESEC

Explanation   No response to a power-off (UNAVAILABLE) NOTIFY request was received by the TN3270 server within 30 seconds of sending it to the host. If this condition persists for another 2  minutes, the current TN3270 session connected to the LU is disconnected. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening point are in use.

Recommended Action   Examine the system services control point (SSCP) host VTAM console for status of the specified PU and LU. Review the VTAM console log output for relevant events (such as deactivation of the PU or LU). If, after VTAM console review, the cause is still unknown, report this error to your technical support representative. A temporary workaround is simply to recycle the affected LU at the VTAM console. This will put the LU back into normal circulation.


Error Message   
%TN3270S-1-NO_PSID_RSP_RCVD: No NMVT Reply PSID received on LU [chars].[dec], 120*ONESEC

Explanation   No response to a Reply PSID was received by the TN3270 server within 30 seconds of sending it to the host. This fault can only occur on dynamic LUs that have been misconfigured or de-activated at the host. If this condition persists for another 2 minutes, the current TN3270 session connected to the LU is disconnected. Bad dynamic LUs are placed in a special area where no attempt to reuse them is made until all other generic-pool LUs of the IP listening point have been exhausted.

Recommended Action   Check the status of the LU via VTAM, and vary the LU active if appropriate. This action must happen within 2 minutes of the time that this message appears; otherwise, the LU is placed in "bad" LU area and will not be reused unless all good LUs are in use. Examine the host VTAM log for trouble. In particular, look for messages indicating a badly configured LUGROUP resource definition or file. Fix the configuration and recycle the affected major nodes.


Error Message   
%TN3270S-1-NO_SDT_REQ_RCVD: No SDT REQ received on LU [chars].[dec], 120*ONESEC

Explanation   No SDT (Start Data Transfer) REQ was received by the TN3270 server from the PLU host for the specified LU. If the condition persists for another 2 minutes, the LU is declared bad. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening point are in use.

Recommended Action   Examine the system services control point (SSCP) host VTAM console for status of the specified PU and LU. Review the VTAM console log output for relevant events (such as deactivation of the PU or LU). If, after VTAM console review, the cause is still unknown, report this error to your technical support representative. A temporary workaround is simply to recycle the affected LU at the VTAM console. This will put the LU back into normal circulation.


Error Message   
%TN3270S-1-NO_SDT_TMARK_RCVD: No SDT TIMING-MARK received on LU [chars].[dec], 120*ONESEC

Explanation   No SDT (Start Data Transfer) TIMING-MARK response was received by TN3270 server from the TN3270 client software for the specified TN3270 session. If the condition persists for another 2 minutes, the LU is declared bad. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening point are in use.

Recommended Action   Some TN3270 clients may not fully handle the TN3270 RFCs. Enable the client-side trace to figure out on what the client is failing. Replace the failing client software with software from the list of TN3270 software types that are known to work with the TN3270 server (see your technical representative for this). If the problem persists, report this error to your technical support representative.


Error Message   
%TN3270S-1-NO_UNBIND_RSP_RCVD: No UNBIND RSP received on LU [chars].[dec], 120*ONESEC

Explanation   No response to an UNBIND request was received by the TN3270 server within 30  seconds of sending the request to the host. If this condition persists for another 2 minutes, the current TN3270 session connected to the LU is disconnected. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening-point are in use.

Recommended Action   Examine the system services control point (SSCP) host VTAM console for status of the specified PU and LU. Review the VTAM console log output for relevant events (such as deactivation of the PU or LU). If, after VTAM console review, the cause is still unknown, report this error to your technical support representative. A temporary workaround is simply to recycle the affected LU at the VTAM console. This will put the LU back into normal circulation.


Error Message   
%TN3270S-1-NO_UNBIND_TMARK_RCVD: No UNBIND-time TIMING-MARK received from client for LU [chars].[dec], 120*ONESEC

Explanation   No UNBIND TIMING-MARK response was received by TN3270 server from the TN3270 client software for the specified TN3270 session. If the condition persists for another 2  minutes, the LU is declared bad. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening point are in use.

Recommended Action   Some TN3270 clients may not fully handle the TN3270 RFCs. Enable the client-side trace to figure out on what the client is failing. Replace the failing client software with software from the list of TN3270 software types that are known to work with the TN3270 server (see your technical representative for this). If the problem persists, report this error to your technical support representative.


Error Message   
%TN3270S-1-RP_PU_CONFLICT: RP & CIP hold conflicting PU name([chars]) or index(%ld)

Explanation   The Route Processor (RP) requested an update or delete action on a physical unit (PU) resource reported as stale or incorrect by the CIP TN3270 server.

Recommended Action   Reload the CIP microcode. If the problem recurs, copy the error message exactly as it appears. Run and record the output from the following commands on each CIP in the router before reloading the CIP microcode:

Report this message to your technical support representative.


Error Message   
%TN3270S-4-SESSION_NEGOT_TIME_EXPIRED: A client session from [chars]:[dec] failed to negotiate TN3270/TN3270E., 600*ONESEC

Explanation   A Telnet session that failed to negotiate TN3270/TN3270E within a time period was disconnected.

Recommended Action   Try to locate the TN3270 client that caused the problem. There could be a bug in the client or it could be a transient network problem.


Error Message   
%TN3270S-1-SNA_BAD_SEQUENCE: LU-LU session bad sequence number, lu [chars].[dec] expected snf = [dec], current snf = [dec]

Explanation   An unexpected LU-LU session sequence was received. The LU was presented to the LU named by the LOCADDR and PU. The error will cause a negative response of sense code X2001 to send to the host.

Recommended Action   Examine the system services control point (SSCP) host VTAM console for status of the specified LU. Get a trace output for the specified LU and report this problem to your technical support representative.


Error Message   
%TN3270S-1-SNA_BAD_WSF: LU-LU session [chars].[dec] WSF data is illegal

Explanation   A WSF 3270DS Write with wrong data length was received.

Recommended Action   Examine what application in the host sends this WSF, and report this problem to your technical support representative.


Error Message   
%TN3270S-1-SNA_NO_PU_RESPONSE: PU [chars] locaddr [dec] does not get a response in 30 seconds

Explanation   A PU sent a request to the host but did not get a response in 30 seconds.

Recommended Action   Check to see if the PU is still in ACT/BUSY state. Examine to see if the VTAM can talk to the PU. Check the LLC2 connection.


Error Message   
%TN3270S-4-SO_SNDBUF_FAILED: TNSetBindParam:SO_SNDBUF setsockopt for session failed sendSize [dec] err [dec]

Explanation   An internal error occurred while setting the transmit window size on TCP session, so the session is using a default window size.

Recommended Action   Report this message to your technical support representative. Also send your configuration, output from the show controllers cxbus command, and any action you must do to reproduce this problem.


Error Message   
%TN3270S-1-START_FAIL: Failed to start TN3270-server

Explanation   The TN3270 server failed to start correctly, and is now not running. The immediately preceding error messages point to the cause of the failure.

Recommended Action   Review the previous error messages to discover what caused the start failure, and take action based on those messages.


Error Message   
%TN3270S-6-START_OK: Starting TN3270-server

Explanation   This is an informational message announcing the bringing up of the TN3270 server subsystem.

Recommended Action   No action is required.


Error Message   
%TN3270S-1-STARTUP_RACE: InitTimerService Failed;Previous timer service still up

Explanation   The shutdown of TN3270 server was not finished when a new reincarnation was attempted.

Recommended Action   If this problem is caused by a quick restart of the TN3270 server, try to restart the TN3270 server. Report this message to your technical support representative. Also send your configuration, output from the show controllers cxbus command, and any action you must do to reproduce this problem.


Error Message   
%TN3270S-6-STOPPING: Stopping Tn3270-server

Explanation   This is an informational message announcing the shutdown of the TN3270 server subsystem.

Recommended Action   No action is required.


Error Message   
%TN3270S-2-TELNETINITFAIL: Initialization of Tn3270 server Failed

Explanation   Initialization of Telnet component of TN3270 server failed.

Recommended Action   This is most probably because of inadequate memory on the CIP card. Check the memory, and report this message to your technical support representative.


Error Message   
%TN3270S-4-TN3270_CONFIG_INCOMPATIBLE: IOS sub-codepoint [dec] with length [dec] not understood, 600*ONESEC

Explanation   The TN3270 server received a configuration command from the Cisco IOS newer than CIP expects. Some functionality may not be implemented.

Recommended Action   Check that the Cisco IOS release is compatible with the CIP version.


Error Message   
%TN3270S-6-TOOBIG: [dec] byte IP datagram exceeds TN3270 Server receive buffer limit

Explanation   The router sent an IP datagram to the TN3270 server IP address that is larger than the maximum size of 4096. The IP datagram was dropped.

Recommended Action   No action is required.


Error Message   
%TN3270S-4-TOO_MANY_HOST_WRITES: Client on PU [dec]:locaddr [dec] ip [chars]:[dec] is being disconnected;Check outbound LU pacing

Explanation   This could either be a transient network problem or an internal error in server.

Recommended Action   Ensure that LU outbound pacing is configured. If that is correct, try to locate the TN3270 client that caused the problem. There could be a bug in the client. Also, try to get a Telnet trace of the session by reproducing the problem. Report this error to your technical support representative.


Error Message   
%TN3270S-7-UNKNOWN_SNA_MSG: Unknown message for PU [chars], data: [chars]

Explanation   A SNA message from the host is invalid.

Recommended Action   If it only happens once, this could be a glitch in the line. Record the message for later reference. If this error recurs, check if the host is configured correctly.

CMCC-UTIL Error Message

CIP error message related to channel adapter utilities


Error Message   
%UTIL-3-LINKLIST: [chars]([hex])

Explanation   An internal software error occurred.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.

CMCC-XCPA Error Messages

Channel port adapter error messages


Error Message   
%XCPA-3-CKSUM_OFFSET: Invalid checksum offset: offset = [dec], length = [dec]

Explanation   The microcode was unable to update the packet checksum. The packet will be dropped.

Recommended Action   Copy the error message exactly as it appears, issue the show tech-support command and call your technical service representative with the information.


Error Message   
%XCPA-2-MBX: [chars] - [dec]

Explanation   A software program error occurred on the Channel Port Adapter Mailbox. This error could affect console support on the port adapter, logger messages, and configuration commands.

Recommended Action   Copy the error message exactly as it appears, issue the show tech-support command and call your technical service representative with the information.


Error Message   
%XCPA-3-NOMEMORY: Out of memory trying to [chars]

Explanation   The necessary resources could not be allocated.

Recommended Action   Copy the error message exactly as it appears, issue the show tech-support command and call your technical service representative with the information.


Error Message   
%XCPA-2-PMC_TIMEOUT: PMC Timeout: poll_interval = 0x[hex]

Explanation   A timeout occurred while trying to access either memory or the channel interface.

Recommended Action   Copy the error message exactly as it appears, issue the show tech-support command and call your technical service representative with the information.


Error Message   
%XCPA-3-SWVER_MISMATCH: Incompatible switching version, unable to find version [dec]

Explanation   The Cisco IOS release and CMCC microcode version are incompatible.

Recommended Action   Copy the error message exactly as it appears, issue the show tech-support command and call your technical service representative with the information.


hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1998 © Cisco Systems Inc.