-
Cisco IOS Release 12.0 System Message Guide
-
About the Cisco IOS Software Documentation
-
System Error Messages Overview
-
AAAA through APPN
-
ARAP through C1600
-
C2600 through CT3
-
DBCONN through FILESYS
-
FPGA through IPC_RSP_CBUS
-
IPFAST through LPD
-
M32X through NHRP
-
NIC100 through RTT
-
S4T68360 through SWITCH
-
SYS through TI1570
-
TIB through XCPA
-
CMCC-ADAPTER through CMCC-IPC_DRVR
-
CMCC-LOADER through CMCC-XCPA
-
System Failure Error Messages
-
Table Of Contents
CMCC-SYSMGT_EVENT Error Message
CMCC-SYSMGT_RPC 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 err