CMCC-DIAG through CMCC-NEVADA

CMCC DIAG Messages
CCMC DMA Messages
CMCC GET_DATA Messages
CMCC GT64011 Messages
CMCC INT Messages
CMCC IPC Messages
CMCC IPC_DRVR Messages
CMCC IPP Messages
CMCC LOADER Messages
CMCC LOVE Messages
CMCC MBUF Messages
CMCC MEMD Messages
CMCC MPC Messages
CMCC MSG802 Messages
CMCC NEVADA Messages

CMCC DIAG Messages

The following are Channel Interface Processor (CIP) error messages for diagnostic testing.

Error Message

%DIAG-6-BADCODE: Invalid request code ([dec]) to run_diag

Explanation A request was made to run an ESCON Channel Adapter (ECA) diagnostic, but the number of the diagnostic to run was not valid. This is an internal logic error. The request to run the diagnostic is ignored.

Error Message

%DIAG-6-BADLOAD: Firmware load error. Unable to run_diag

Explanation A request was made to run an ESCON Channel Adapter (ECA) diagnostic, but the firmware for the port adapter did not load properly. This is an internal logic error. The request to run the diagnostic is ignored.

CCMC DMA Messages

The following are error messages for the direct memory access (DMA), function on the Channel Interface Processor (CIP) that is responsible for transferring data between the dynamic RAM (DRAM) on the CIP and the memory device facility.

Error Message

%DMA-0-BADFIFO: FIFO failure detected during transfer ([dec] [hex])

Explanation An error has occurred in one of the first-in, first-out (FIFO) hardware components used in the direct memory access (DMA) transfer operation. This failure was detected and has resulted in the dropping of a packet. This problem is an indication of either a very serious software bug or a Channel Interface Processor (CIP) hardware problem. This error could happen if you are running a version of CIP microcode that is incompatible with the hardware revision of this CIP board.

Recommended Action If you are sure that you are running a supported version of CIP microcode, copy the error message exactly as it appears, issue the show tech-support command, and provide the information to your Cisco technical support representative.

Error Message

%DMA-3-BADXFER: Invalid DMA request type ([hex] [dec])

Explanation An unsupported direct memory access (DMA) request type has been detected.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%DMA-3-CBUSERR: CBUS error (no ACK neither NACK) 0x[hex]

Explanation The direct memory access (DMA) controller started a read or write operation and did not receive a response from the ciscoBus (CBUS) indicating the completion status. This error could be caused by an improperly seated board in the router or by an intermittent hardware problem on the Channel Interface Processor (CIP), the Switch Processor (SP), the Route Switch Processor (RSP), or the chassis.

Recommended Action If this error message occurs repeatedly, first try reseating all the boards in the router. If this does not fix the problem, copy the error message exactly as it appears, issue the show tech-support command, and provide the information to your Cisco technical support representative.

Error Message

%DMA-3-CBUSPARITY: CBUS parity error 0x[hex]

Explanation A parity error was detected on the ciscoBus (CBUS) during a data transfer. This error could be caused by an improperly seated board in the router or by an intermittent hardware problem on the Channel Interface Processor (CIP), the Switch Processor (SP), the Route Switch Processor (RSP), or the chassis.

Error Message

%DMA-4-DATAPARITY: DMA Data FPGA parity error 0x[hex]

Explanation A parity error was detected during a direct memory access (DMA) data transfer. This error could be caused by an improperly seated board in the router or by an intermittent hardware problem on the Channel Interface Processor (CIP), the Switch Processor (SP), the Route Switch Processor (RSP), or the chassis.

Error Message

%DMA-3-DMAFAIL: DMA request failed ([hex])

Explanation During an attempted packet transfer, a failure has occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%DMA-0-INCOMPL: DMA transfer incomplete on interrupt

Explanation The direct memory access (DMA) controller indicated to the Channel Interface Processor (CIP) that the current DMA transfer had completed, but the DMA status register showed that the transfer was still in progress. This is a CIP hardware problem, from which the software cannot recover. The CIP has restarted after a fatal error dump. This error could happen if you are running a version of CIP microcode that is incompatible with the hardware revision of this CIP board.

Error Message

%DMA-3-LOGICERR: CBUS timeout (10 us) 0x[hex]

Explanation The direct memory access (DMA) controller tried to start a read or write operation but did not receive a response from the ciscoBus (CBUS) within 10 microseconds. This error could be caused by an improperly seated board in the router or by an intermittent hardware problem on the Channel Interface Processor (CIP), the Switch Processor (SP), the Route Switch Processor (RSP), or the chassis.

Error Message

%DMA-0-NOXFER: No transfer pending on DMA interrupt

Explanation The direct memory access (DMA) controller indicated to the Channel Interface Processor (CIP) that the current DMA transfer had completed, but there was no record of a transfer in progress. This is an indication of either a very serious software bug or a CIP hardware problem. In either case, this error condition is not recoverable. The CIP has restarted after a fatal error dump. This error could happen if you are running a version of CIP microcode that is incompatible with the hardware revision of this CIP board.

Error Message

%DMA-0-REGISTERS: [hex] [hex] [hex] [hex]

Explanation This error message follows some of the other direct memory access (DMA) related error messages. It provides some context for those error messages.

Recommended Action When reporting DMA error messages to your Cisco technical service representative, make sure you include the output of this error message exactly as it appears.

CMCC GET_DATA Messages

The following Channel Interface Processor (CIP) error messages are related to the internal routine for allocating transfer elements.

Error Message

%GET_DATA-0-NOMEMORY: Can not allocate storage for xfer elements

Explanation An attempt was made to allocate a transfer element, and no storage was available. This is a fatal error.

Recommended Action The Channel Interface Processor (CIP) has restarted. Report this error to your Cisco technical support representative.

CMCC GT64011 Messages

The following are channel port adapter GT64011 error messages.

Error Message

%GT64011-2-ERROR_INT: GT64011 Error (cause=0x[hex])

Explanation An unexpected GT64011 error interrupt has occurred.

Recommended Action Make sure all port adapters are properly seated. If this error persists, contact your Cisco technical support representative.

Error Message

%GT64011-2-ERROR_REGS: GT64011: Bus Error = 0x[hex], Address Decode Error = 0x[hex]

Explanation An unexpected GT64011 error interrupt has occurred.

Recommended Action Make sure all port adapters are properly seated. If this error persists, contact your Cisco technical support representative.

Error Message

%GT64011-2-UNKNOWN_ID: GT64011 Unknown Device or Vendor ID ([hex])

Explanation The GT64011 was found to have an incompatible device or vendor ID.

Recommended Action If this error persists, contact your Cisco technical support representative.

CMCC INT Messages

The following are Channel Interface Processor (CIP) error messages for the interrupt handler interface.

Error Message

%INT-0-ADDFAST: Add: Invalid fast io code [dec]

Explanation A request was made to add an interrupt handler to the fast I/O path with an invalid interrupt type. This is a fatal internal logic error.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%INT-0-ADDFLIH: Add: Invalid interrupt code [dec]

Explanation A request was made to add an interrupt handler with an invalid interrupt number. This is a fatal internal logic error.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%INT-0-ADDFULL: Add: Invalid full io code [dec]

Explanation A request was made to add an I/O interrupt handler with an invalid interrupt code. This is a fatal internal logic error.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%INT-0-ADDTRAP: Add: Invalid trap code [dec]

Explanation A request was made to add a system call handler with an invalid system call number. This is a fatal internal logic error.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%INT-0-REMOVEFAST: Remove: Invalid fast io code [dec]

Explanation A request was made to remove an interrupt handler from the fast I/O path with an invalid interrupt type. This is a fatal internal logic error.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%INT-0-REMOVEFLIH: Remove: Invalid interrupt code [dec]

Explanation A request was made to remove an interrupt handler with an invalid interrupt number. This is a fatal internal logic error.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%INT-0-REMOVEFULL: Remove: Invalid full io code [dec]

Explanation A request was made to remove an I/O interrupt handler with an invalid interrupt code. This is a fatal internal logic error.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%INT-0-REMOVETRAP: Remove: Invalid trap code [dec]

Explanation A request was made to add a system call handler with an invalid system call number. This is a fatal internal logic error.

Recommended Action Report this error to your Cisco technical support representative.

CMCC IPC Messages

The following are Channel Interface Processor (CIP) error messages related to the interprocess communication (IPC) subfacility.

Error Message

%IPC-2-CANT_SEND: Cannot send IPC message: [chars]

Explanation An error has occurred in the interprocess communication (IPC) slave discovery mechanism. It might result in a malfunction in the operation of the IPC.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%IPC-4-CONSISTENCY: Message failed consistency check: [chars]

Explanation An internal inconsistency has been found in some interprocess communication (IPC) data structures.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%IPC-3-DELETED: Attempt to delete an IPC message (0x[hex]) a second time, MSGDEF_LIMIT_SLOW

Explanation An internal inconsistency has been found in some interprocess communication (IPC) data structures.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ipc status command, as well as the show ipc queue command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the command output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%IPC-3-GIANT: Request for giant IPC packet denied. Request size = [dec], MSGDEF_LIMIT_SLOW

Explanation A message has been requested that was too large for the interprocess communication (IPC) system.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ipc status command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show ipc status command output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%IPC-2-LOCK: Lock done a deleted element

Explanation An internal inconsistency has been found in some interprocess communication (IPC) data structures.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%IPC-3-NOBUFF: The [chars] IPC message header cache has emptied

Explanation The specified interprocess communication (IPC) message header cache has been emptied.

Error Message

%IPC-5-NODELFUNC: Delayed init function not available

Explanation The interprocess communication (IPC) application cannot be initialized because its initialization function does not appear in the IPC initialization function list.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%IPC-2-NODISPATCH: Message for [dec].[dec] has no receive queue or dispatch routine, MSGDEF_LIMIT_SLOW

Explanation The interprocess communication (IPC) user has failed to provide any means of handling the received message.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ipc ports command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show ipc ports output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%IPC-2-NOMEM: No memory available for [chars]

Explanation The interprocess communication (IPC) subsystem could not obtain the memory it needed.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%IPC-2-ONINT: Called from interrupt level: [chars]

Explanation The interprocess communication (IPC) user attempted a prohibited call into IPC while IPC was running on the interrupt stack.

Error Message

%IPC-5-SLAVELOG: VIP-[chars]

Explanation The Cisco IOS software, running on a Versatile Interface Processor (VIP) card, generated this message. The error message has been passed up to the Route Processor (RP) or Route Switch Processor (RSP) for display. This message appears only if the user has configured the service slavelog command.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%IPC-2-UNLOCK: Unlock done on already unlocked element

Explanation An internal inconsistency was found in some interprocess communication (IPC) data structures.

CMCC IPC_DRVR Messages

The following are interprocess communication (IPC) driver error messages.

Error Message

%IPC_DRVR-2-DMAERR: DMA Error detected - [chars]([dec])

Explanation The interprocess communication (IPC) DRVR packet switch notification has detected a direct memory access (DMA) transfer error.

Recommended Action The IPC subsystem is used by the channel adapter loader and channel adapter network management. A single direct memory access (DMA) error will not impact these channel adapter functions. However, if you are experiencing problems loading the channel adapter or retrieving information from the channel adapter, you will have to reload the channel adapter microcode. In any case, report this message to your Cisco technical support representative.

Error Message

%IPC_DRVR-4-NOMEM: Unable to obtain [chars], MSGDEF_LIMIT_GLACIAL

Explanation The interprocess communication (IPC) DRVR transport subsystem could not obtain the memory it needed.

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

CMCC IPP Messages

The following are error messages for the encryption feature.

Error Message

%IPP-3-PKT_EXCEEDS_MTU: [chars]: Outbound Packet exceeds max MTU size for CMCC

Explanation An outbound Cisco Multipath Channel (CMPC) packet is larger than the Maximum Transmission Unit (MTU) size for the Cisco Mainframe Channel Connection (CMCC).

Recommended Action Investigate why the host is sending packets that are larger than the configured MTU size on the CMCC.

CMCC LOADER Messages

The following are Channel Interface Processor (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 Cisco technical support representative.

Error Message

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

Explanation There is not enough memory to load this file.

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

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

Error Message

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

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

Recommended Action Report this error to your Cisco 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 Cisco 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, then copy the error message exactly as it appears and report it to your Cisco technical support representative.

Error Message

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

Explanation The loader cannot handle variables of the type given.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation The loader cannot handle input files of the type given.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation An error has occurred in the input files.

Recommended Action Report this error to your Cisco 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, then copy the error message exactly as it appears and report it to your Cisco technical support representative.

Error Message

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

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

Recommended Action Report this error to your Cisco 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 the kernel. Report this error to your Cisco 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, then copy the error message exactly as it appears and report it to your Cisco 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, then copy the error message exactly as it appears and report it to your Cisco 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, then report this error message to your Cisco technical support representative.

Error Message

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

Explanation The loader cannot handle relocation entries of the type given.

Recommended Action Report this error to your Cisco 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 the type given.

Recommended Action Report this error to your Cisco 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 Cisco technical support representative.

Error Message

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

Explanation Loading is complete, but the close process failed.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation The Channel Interface Processor (CIP) has failed to access necessary image files.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation An error occurred during an attempt to open a file to be loaded.

Recommended Action Confirm that the file exists. If the file does not exist, create it if possible. If the problem persists, copy the error message exactly as it appears and report it to your Cisco 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. The open process was retried every 5 seconds for a minute before failing.

Recommended Action If subsequent open processes fail, report this error to your Cisco technical support representative.

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

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 Cisco 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 Cisco technical support representative.

Error Message

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

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

Recommended Action Check the file format version. If the file version is correct, then copy the error message exactly as it appears and report it to your Cisco 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 Cisco technical support representative.

Error Message

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

Explanation The number of pending HI16 entries has exceeded table capacity.

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 Cisco 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.

Error Message

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

Explanation The version of Cisco IOS software is incompatible with this Channel Interface Processor (CIP) microcode image.

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

Error Message

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

Explanation The Channel Interface Processor (CIP) has successfully loaded a segment image.

Recommended Action 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 Cisco technical support representative.

Error Message

%LOADER-0-LOADMAP_DATA2: [hex] [hex] %08d [chars]

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

Recommended Action Report this information to your Cisco technical support representative.

Error Message

%LOADER-0-LOADMAP_DATA3: [chars]

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

Recommended Action Report this information to your Cisco 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 have been loaded in Channel Interface Processor (CIP) storage.

Recommended Action Report this information to your Cisco technical support representative.

Error Message

%LOADER-0-LOADMAP_EMPTY2: No segments have been loaded.

Explanation The loader has not loaded any modules into Channel Interface Processor (CIP) storage.

Recommended Action Report this information to your Cisco 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 Channel Interface Processor (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 Cisco 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 Channel Interface Processor (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 Cisco 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 Cisco technical support representative.

Error Message

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

Explanation An internal software error has occurred.

Error Message

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

Explanation An internal software error has occurred.

Error Message

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

Explanation An internal software error has occurred.

Error Message

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

Explanation An internal software error has occurred.

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 Cisco technical support representative.

Error Message

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

Explanation A section of the input file contains dynamic shared objects. The input file cannot have dynamic shared objects.

Recommended Action Report this error to your Cisco 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, then copy the error message exactly as it appears and report it to your Cisco technical support representative.

Error Message

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

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

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

Error Message

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

Explanation The Channel Interface Processor (CIP) is unable to compose the microcode image name.

Recommended Action Report this error to your Cisco 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, then copy the error message exactly as it appears and report it to your Cisco 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 Cisco technical support representative.

Error Message

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

Explanation A section of the input files contains symbols that conflict with shared objects. The input file cannot have shared objects.

Recommended Action Report this error to your Cisco 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, then copy the error message exactly as it appears and report it to your Cisco technical support representative.

Error Message

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

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

Recommended Action Report this error to your Cisco 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 Cisco 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 Cisco 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 Cisco 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 Cisco 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 Cisco technical support representative.

Error Message

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

Explanation Either the prerequisite files are not loaded, or the loader cannot recognize some external symbols that are referenced.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

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

Recommended Action Report this error to your Cisco 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 Cisco 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 Cisco 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 Cisco 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 Cisco 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 Cisco technical support representative.

Error Message

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

Explanation The loader cannot handle this type of file.

Recommended Action Report this error to your Cisco 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 Cisco technical support representative.

Error Message

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

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

Recommended Action Report this error to your Cisco 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 Cisco 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 for the loader.

Recommended Action The loader must be recompiled with a larger area allocated. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

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

Explanation The preallocated area is not large enough for the loader.

Recommended Action Report this error to your Cisco 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 the loader.

Error Message

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

Explanation There is an error in the input file.

Recommended Action Report this error to your Cisco 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 the loader.

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 Cisco 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 Cisco 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 Cisco 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 Cisco technical support representative.

CMCC LOVE Messages

The following are Channel Interface Processor (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 Cisco Mainframe Channel Connection (CMCC) card has failed.

Recommended Action The CMCC card tried to recover by dropping the buffer that contained the statistics. However, it is 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 provide the information to your Cisco technical support representative.

Error Message

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

Explanation The Cisco Mainframe Channel Connection (CMCC) card does not have enough memory to start the love letter processing. Love letters are used to transmit channel statistics to IOS. 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 Messages

The following are 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 a memory buffer that was already free.

Recommended Action Report this error to your Cisco 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 Cisco technical support representative.

CMCC MEMD Messages

The following are Channel Interface Processor (CIP) error messages related to the memory device facility.

Error Message

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

Explanation An interprocess communication (IPC) message was queued to the Channel Interface Processor (CIP) but there was no handler defined to process it. This error occurs if the IPC subsystem was not initialized at the time an IPC message was received. The CIP has dropped the IPC message.

Recommended Action If these error messages appear repeatedly, copy all the error messages exactly as they appear, issue the show tech-support command, and provide the information to your Cisco technical support representative.

Error Message

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

Explanation While a buffer queue was being processed in MEMD, a pointer was found to have an invalid value. The Channel Interface Processor (CIP) wrote an error code to MEMD indicating that it is corrupted. The Switch Processor (SP) or Silicon Switch Processor (SSP) will now report this error condition back to the Route Processor (RP), which in turn will restart the ciscoBus (CBUS) complex that resets all the interfaces.

Recommended Action First find out which board wrote the invalid pointer value to MEMD. You will need help from your Cisco technical service representative to set up the router for a MEMD snapshot in case of an error condition. Depending on what that snapshot shows, the investigation can be narrowed down to either a particular board in the router or a software problem. Copy all the error messages exactly as they appear, issue the show tech-support and show extended channel subchannel or show extended vc commands, and provide the information to your Cisco 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 Channel Interface Processor (CIP), but the virtual circuit associated with the packet is not valid. This could mean that the virtual circuit number is out of range or that there is no application registered to receive packets on this virtual circuit. The CIP has dropped the packet.

Recommended Action This error message is followed by a dump of the beginning of the bad frame. If these error messages appear repeatedly, copy all the error messages exactly as they appear, issue the show tech-support and show extended channel subchannel or show extended vc commands, and provide the information to your Cisco 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 This message should always be preceded by either a MEMD-WRONGINT or a MEMD-BADVCN error message. Follow the recommended action as explained under that error message.

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 This message should always be preceded by either a MEMD-WRONGINT or a MEMD-BADVCN error message. Follow the recommended action as explained under that error message.

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 an incorrect virtual circuit number.

Recommended Action This message should always be preceded by either a MEMD-WRONGINT or a MEMD-BADVCN error message. Follow the recommended action as explained under that error message.

Error Message

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

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

Recommended Action This error message should happen only when a configuration statement is removed from a Channel Interface Processor (CIP). Copy the error message exactly as it appears, issue the show tech-support and the show extended channel subchannel or show extended vc commands, and provide the information to your Cisco 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 This error message should only happen when a new configuration statement is added to a Channel Interface Processor (CIP). Issue the show extended channel subchannel or show extended vc command, remove the configuration statement, copy the error message exactly as it appears, issue the show tech-support command, and provide the information to your Cisco technical support representative.

Error Message

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

Explanation A packet was queued for the Channel Interface Processor (CIP) with a valid virtual circuit number, but the virtual circuit number is associated with a different port adapter. The CIP has dropped the packet.

CMCC MPC Messages

The following are Multipath Channel (MPC) error messages.

Error Message

%MPC-3-BAD_CONFIG_CODE: [chars]: Unrecognized config action code [dec]

Explanation A Transmission Group (TG) configuration command has been received containing an unrecognized action code.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%MPC-3-BAD_CONFIG_DIR: PA[dec] MPC [hex]-[hex] bad direction code 0x[hex]

Explanation The configuration message for a Cisco Multipath Channel (CMPC) statement contains an invalid direction code.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation An XID2 message from the host has specified a subchannel read/write transfer direction different from the direction configured.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation A Multipath Channel (MPC) data-link connection (DLC) frame has been received with an unrecognized DLC command.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation A Multipath Channel (MPC) block has been received with an unrecognized header configuration.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation A Multipath Channel (MPC) block has been received with an unrecognized header configuration.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%MPC-3-BAD_INB_BFR: Inbound bfr to CMPC has no room for header

Explanation Cisco Multipath Channel (CMPC) is attempting to build a data-link connection (DLC) header, but there is insufficient space in the inbound buffer.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation A Multipath Channel (MPC) block has been received with a sequence number error.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%MPC-3-CFG_TYPE_ERR: [chars]: CMPC TG partner type code invalid

Explanation The Cisco Multipath Channel (CMPC) Transmission Group (TG) configuration block contains an invalid partner type code.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%MPC-3-CMPCP_ACT_ERR: Activate, but CvInfo block already active with handle [dec]

Explanation An attempt has been made to activate a Multipath Channel (MPC)+ control block that is already active.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%MPC-3-CMPCP_BLK_FMT_ERR: [chars]: [chars]

Explanation A Multipath Channel (MPC)+ channel block has been received that contains a format error.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%MPC-6-CMPCP_CONN_ACT: [chars]: [chars] Connection Activated

Explanation An IP type connection has been activated.

Recommended Action No action is required.

Error Message

%MPC-6-CMPCP_CONN_INACT: [chars]: [chars] Connection Deactivated

Explanation An IP type connection has been deactivated.

Recommended Action No action is required.

Error Message

%MPC-3-CMPCP_CV_ERR1: Unrecognized/Unexpected CV: [hex]

Explanation An unrecognized or unexpected Multipath Channel (MPC)+ subvector has been received from the host.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%MPC-3-CMPCP_CV_ERR2: Possible Config error: Rcvd [chars] [chars], [chars] [chars]

Explanation Cisco Multipath Channel (CMPC)+ has detected a mismatch between a value received from the host and a configured or generated value.

Recommended Action This is probably a configuration error. Otherwise, report this error to your Cisco technical support representative.

Error Message

%MPC-3-CMPCP_CV_ERR3: Corrupt CV Frame: [chars]

Explanation A received CV frame is corrupted.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%MPC-3-CMPCP_CV_LEN_ERR: Received subvector [hex] too long

Explanation A Multipath Channel (MPC)+ subvector that is longer than the area reserved on the basis of protocol analysis has been received from the host .

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%MPC-6-CMPCP_CV_LOG: [chars]: Event/State [chars]/[chars]

Explanation This informational message is given before CMPCP_CV_ERR type messages to provide a more complete description of the problem.

Recommended Action See the CMPCP_CV_ERR message that follows.

Error Message

%MPC-3-CMPCP_DUPL_TOKEN: Duplicate group token, '[chars]' PA[dec] MPC [hex]-[hex]

Explanation An XID2 message from the host specifies a group token that has already been specified for another Transmission Group (TG).

Recommended Action This is probably a configuration error in which multiple read or write subchannels are specified in a TRLE. If this is not the case, report this error to your Cisco technical support representative.

Error Message

%MPC-3-CMPCP_FRAME_ERR1: [chars]: Frame rcvd on [chars] token [chars]

Explanation A problem has been detected with a Multipath Channel (MPC)+ frame token.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%MPC-3-CMPCP_FRAME_ERR2: [chars]: Frame rcvd on [chars] token, [chars]: [hex]

Explanation A specific field in a Multipath Channel (MPC)+ subvector received from the host is not recognized.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%MPC-3-CMPCP_HANDLE_ERR: All CMPC+ handles in use

Explanation A Multipath Channel (MPC)+ handle cannot be allocated because the handle pool is empty.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%MPC-3-CMPCP_INACT_ERR: Inact, but CvInfo block already inactive

Explanation An attempt is made to inactivate a Multipath Channel (MPC)+ control block that is already inactive.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%MPC-3-CMPCP_PROT_ERR: [chars]: Unrecognized Protocol Type: 0x[hex]

Explanation The host has attempted to set the protocol type for a connection to a value not recognized by Cisco Multipath Channel (CMPC)+.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%MPC-6-CMPCP_STALE_TOKEN: Rcvd MPC+ local token is stale

Explanation A local token has been received that is no longer in use.

Recommended Action This probably occurred during a Transmission Group (TG) shutdown sequence, with no associated operational problems. Otherwise, report this error to your Cisco technical support representative.

Error Message

%MPC-3-CMPCP_TOKEN_ERR: Error in rcvd MPC+ local token: [chars]

Explanation An invalid condition has been detected in a received local token.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%MPC-3-CMPCP_TOKEN_LEN_ERR: Token detectd with invalid size: [dec]

Explanation A token with an invalid length has been detected.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%MPC-3-CONFIG_ERR: TG configured IP but channel protocol not MpcPlus

Explanation The host has attempted a channel connection to a Transmission Group (TG) but did not use the correct channel protocol (Multipath Channel [MPC]+) .

Recommended Action This is probably a configuration error. Otherwise, report this error to your Cisco technical support representative.

Error Message

%MPC-3-CV_CMGR_FSM_ERR: [chars]: Event [chars], State [chars]

Explanation An internal state machine has attempted to execute an event inconsistent with the state.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%MPC-3-CV_PROT_FSM_ERR: [chars]: Event [chars], State [chars]

Explanation An internal state machine has attempted to execute an event inconsistent with the state.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation A Multipath Channel (MPC) device has been initialized. The device string is in the form PAx 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 A Multipath Channel (MPC) frame has been received with a length value that is inconsistent with the channel block length.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation An attempt has been made to configure a Multipath Channel (MPC) link that has already been configured.

Recommended Action No action is required.

Error Message

%MPC-6-NODE_NOT_ACTIVE: Host attempted activation of [chars] but TG not configured

Explanation A message has been received for a Multipath Channel (MPC) link for which the transmission group has not been configured.

Recommended Action Configure the required Transmission Group (TG). This process may require the host node or profile to be cycled down and up.

Error Message

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

Explanation A call to create a pool or get a buffer has failed.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%MPC-3-PARTNER_CFG_ERR: [chars]: [chars]

Explanation A configuration command has failed because the Multipath Channel (MPC) partner linkage is not established.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation An internal state machine has attempted to execute an event inconsistent with the state.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation 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 A Multipath Channel (MPC) device has been shut down. The device string is in the form PAx 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 An internal state machine has attempted to execute an event inconsistent with the state.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation An internal state machine has attempted to execute an event inconsistent with the state.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation A Multipath Channel (MPC) sweep command has been received with a sequence number error.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation An invalid parameter has been received in a system management call.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation An invalid parameter has been received in a system management call.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation An invalid parameter has been received in a system management call.

Recommended Action Report this error to your Cisco 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 has been received in a system management call.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation This informative message has been given when an attempt is made to configure more than the maximum number of Multipath Channel (MPC) Transmission Groups (TGs).

Recommended Action No action is required.

Error Message

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

Explanation A Multipath Channel (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 Cisco technical support representative.

Error Message

%MPC-3-XID2_BAD_HDR: Unrecognized Xid2 header received

Explanation An XID2 frame has been received with an unrecognized header.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation An internal state machine has attempted to execute an event inconsistent with the state.

Recommended Action Report this error to your Cisco technical support representative.

CMCC MSG802 Messages

The following are Channel Interface Processor (CIP) 802 error messages that are 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 Cisco SNA (CSNA) adapters. A maximum of 18 CSNA adapters is allowed per Channel Interface Processor (CIP).

Recommended Action To comply with the 18 CSNA adapter limit, reduce the number of CSNA adapters configured.

Error Message

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

Explanation This message confirms operability for the specified adapters that have been brought up.

Recommended Action No action is required.

Error Message

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

Explanation This message confirms the removal for each of the specified adapters that have been removed.

Recommended Action No action is required.

Error Message

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

Explanation This message confirms the changed Logical Link Control (LLC) parameters for each of the specified adapters.

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 Logical Link Control (LLC) protocol stack has received a bad frame that contains an "Invalid NS" message from its peer. This problem is often caused by incorrectly configured LLC parameters.

Recommended Action Reconfigure the LLC parameters of the Channel Interface Processor (CIP) adapter and the peer.

Error Message

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

Explanation The CTA mapper cannot provide the maximum number of connections as configured because of insufficient memory. Any attempt to decrease the maximum number of connections will be rejected.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

%MSG802-6-DMA_ABORT: DMA message consists of [dec] fragments with length of [dec]

Explanation The specified Dependent LU (DLU) send request has been aborted because it contained too many fragments or the fragments were too long.

Recommended Action If the error persists, notify your Cisco technical support representative.

Error Message

%MSG802-6-FLOW_OFF_COUNT: On [int], Off30 [int], total [int], max off time [int] ms

Explanation This message provides statistics about flowed-off connections. This message usually is preceded by a CTA-0-INACTIVE message.

Recommended Action No action is required.

Error Message

%MSG802-6-FLOW_OFF_INFO: Ran [hex], Ucep 0x[hex], Pcep 0x[hex], [int] ms, ccb 0x[hex]

Explanation This message provides statistics about flowed-off connections. This message usually is preceded by a CTA-0-INACTIVE message.

Recommended Action No action is required.

Error Message

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

Explanation A connection has been terminated.

Recommended Action No action is required.

Error Message

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

Explanation The MEMD buffer currently supports a maximum frame size of 4472 bytes. Cisco SNA (CSNA) detected that the specified frame exceeded the maximum size. The frame has been discarded.

Recommended Action Check the maximum frame length configured for the MEMD buffer.

Error Message

%MSG802-3-HARD_ERROR: [chars]

Explanation The protocol stack has encountered error conditions that prevent it from continuing its normal operations. This error is probably an error checking condition.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation The Logical Link Control (LLC) task has detected an invalid configuration command. The command is rejected.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation The Logical Link Control (LLC) has received an invalid ID type that is not supported. The request is discarded.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation The Logical Link Control (LLC) task has detected an invalid MSI command. The request is discarded.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation The Logical Link Control (LLC) has received an invalid service primitive code. The error message will provide the service primitive code and identify the module and routine that had received it. This is not a fatal error and the Cisco SNA (CSNA) will continue to operate.

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

Error Message

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

Explanation An attempt to process the specified configuration command has failed because an invalid virtual circuit number (VCN) was detected. The configuration command is rejected.

Recommended Action Report this error to your Cisco 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 An attempt to process the specified configuration command has failed because an invalid virtual circuit number (VCN) was detected. The configuration command is rejected.

Recommended Action Report this error to your Cisco 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 A request to open station has been received for station address that already is open.

Recommended Action Report this error to your Cisco 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 The remote service access point (SAP) has been opened by more than one external communication adapter (XCA) major node. The pair of values that follow old and new user are the USAP that identified the external communication adapter (XCA) major node that attempted to activate the Maximum Transmission Unit (MTU) that was already in use.

Recommended Action Check the external communication adapter (XCA) node definitions.

Error Message

%MSG802-6-LLC_SHUT: LLC shutdown completed

Explanation The Logical Link Control (LLC) has been shut down. The LLC direct memory access (DMA) READ/WRITE task and the TIMER task have been shut down.

Recommended Action No action is required.

Error Message

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

Explanation The Logical Link Control (LLC) subsystem has been brought up.

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 The Channel Interface Processor (CIP) was not able to provide the maximum number of connections as configured because of insufficient memory. Any attempt to decrease the maximum number of connections will be rejected.

Recommended Action Check the maximum number of connections configured to see if CIP is over-configured. If the Multipath is not over-configured, notify your Cisco technical support representative.

Error Message

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

Explanation The Channel Interface Processor (CIP) was not able to provide the maximum number of connections there were configured because it is unable to allocate a message buffer from the Multipath message pool.

Recommended Action Retry the max_llc command. If the error persists, notify your Cisco technical support representative.

Error Message

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

Explanation The maximum number of concurrent Logical Link Control (LLC) connections has been exceeded.

Recommended Action Increase MAX_LLC_SESSIONS parameter on the Channel Interface Processor (CIP) virtual interface.

Error Message

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

Explanation The channel adapter does not have sufficient memory to initialize the Logical Link Control (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 Logical Link Control (LLC) task has detected a queue-open failure.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation The protocol stack has encountered error conditions that prevent it from continuing its normal operations. Possible errors include resource depletion.

Recommended Action Report this error to your Cisco 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 An attempt has been made to reduce the maximum connection limit. This release of Cisco IOS software does not allow you to reduce the maximum connection limit.

Recommended Action No action is required.

Error Message

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

Explanation The Logical Link Control (LLC) has entered a shutdown cleanup state. All configuration commands will be rejected.

Recommended Action Retry the command when the LLC has returned to an operational state.

Error Message

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

Explanation The Channel Interface Processor (CIP) cannot bring up the CTA 802 task because of insufficient memory.

Error Message

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

Explanation The Cisco SNA (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 Logical Link Control (LLC) task has detected an unknown event.

Recommended Action Report this error to your Cisco technical support representative.

Error Message

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

Explanation The Logical Link Control (LLC) task has detected a request for an unsupported function. The request will be ignored.

Recommended Action Report this error to your Cisco technical support representative.

CMCC NEVADA Messages

The following error messages are related to the Channel Interface Processor (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 Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.

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 Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.

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 Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.

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 no interrupt routine was specified. This is a fatal internal logic error.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.

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 Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.

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 Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.

Table of Contents