|
|
The system can report error conditions in numerous facility codes related to the Cisco Mainframe Channel Connection (CMCC) product family. The CMCC product family includes the Channel Interface Processor (CIP) and the Channel Port Adapter (CPA). The format of CMCC error messages differs from the format of other system error messages.
The format for CMCC error messages parallels the format for other system error messages; however, CMCC error messages also indicate the card and slot reporting the error. CMCC error messages begin with a percent sign (%) and are structured as follows:
%CARD-SEVERITY-MSG:SLOT %FACILITY-SEVERITY-MNEMONIC: Message-text
CARD is a code that describes the type of card reporting the error. CIP, CIP2, ECPA, and PCPA are possible card types.
SEVERITY is a single-digit code from 0 to 7 that reflects the severity of the condition. The lower the number, the more serious the situation. Table 5 lists the severity levels.
MSG is a mnemonic that indicates this is an error message. It is always shown as MSG.
SLOT indicates the slot number of the card reporting the error. It is shown as SLOT followed by a number. (For example, SLOT5.)
FACILITY is a code consisting of two or more uppercase letters that indicate the facility to which the message refers. A facility can be a hardware device, a protocol, or a module of the system software. Table 6 lists the CMCC facility codes.
MNEMONIC is a code that uniquely identifies the error message.
Message-text is a text string describing the condition. This portion of the message sometimes contains detailed information about the event, including terminal port numbers, network addresses, or addresses that correspond to locations in the system memory address space. Because the information in these variable fields changes from message to message, it is represented here by short strings enclosed in square brackets ([ ]). A decimal number, for example, is represented as [dec]. Table 7 lists the representations of variable fields and the type of information in them.
The format of non-CMCC error messages is discussed in the "About this Manual" chapter at the beginning of this book.
The following is a sample CMCC error message:
%ECPA-6-MSG:slot5 %SYSMGT_RPC-6-STATE_CHANGE: System Management [chars]
| Level | Description |
|---|---|
0 - emergency | System unusable |
1 - alert | Immediate action needed |
2 - critical | Critical condition |
3 - error | Error condition |
4 - warning | Warning condition |
5 - notification | Normal, but significant, condition |
6 - informational | Informational message only |
7 - debugging | Appears during debugging only |
| Code | Facility |
|---|---|
ADAPTER | Adapter processing |
BSQ | Buffer status queue processing |
CBUS_ATTN | ciscoBus controller statistics |
CBUS_WRITE | ciscoBus controller write support |
CCA | Channel card adapter |
CIOS | Channel adapter Cisco IOS wrappers |
CLAW | Common Link Access for Workstations |
CMPCTG | LLC Transmission Group |
CONFIG | Configuration processing |
CTA | Channel transport architecture |
DEBUGGER | Messages issued when nonrecoverable errors occur |
DIAG | Diagnostic processing |
DMA | Direct memory access |
GET_DATA | Internal routine for allocating transfer elements |
GT64011 | Channel port adapter GT64011 |
INT | Interrupt handler |
IPC | Interprocess communication |
IPC_DRVR | Driver Interprocess communication |
LOADER | Relocating loader |
LOVE | CMCC-to-router statistics |
MBUF | Message buffer |
MEMD | Memory device |
MPC | MultiPath Channel protocol |
MSG802 | IEEE 802.2cx Logical Link Control (LLC) protocol stack |
NEVADA | Internal controller |
OFFL | Offload protocol |
PACK | Packed extension to CLAW |
PKTS | Packet switching API |
SCB | Storage control block |
SCHED | Multitasking scheduler |
SLC | Serial link controller |
SLCI | SLC interface |
SSI802 | Common Service System Service Interface (SSI) |
SUBSYS | Software subsystem |
SYS | CMCC operating system |
SYSMGT_EVENT | Network management processing for system management event generation |
SYSMGT_RPC | Network management processing for system management remote procedure calls |
TCPIP | TCP/IP |
TN3270 | TN3270 server terminal emulation |
UTIL | Channel adapter utilities |
XCPA | Channel port adapter |
| Representation | Type of Information |
|---|---|
[atalk_address] | AppleTalk address |
[atalk_net] | AppleTalk network, either 600 or 600-601 |
[char] | Single character |
[chars] | Character string |
[dec] | Decimal number |
[enet] | Ethernet address (for example, 0000.FEED.00C0) |
[hex] | Hexadecimal number |
[inet] | Internet address (for example, 12.128.2.16) |
[int] | Integer number |
[node] | Address or node name |
[sci_notation] | Scientific notation |
[t-line] | Terminal line number in octal (or decimal if the decimal-TTY service is enabled) |
[v-name] | VINES name; or number (hex or decimal) |
The CMCC error messages are organized alphabetically into sections by facility, and within each facility section, messages are listed alphabetically by mnemonic. Each error message is followed by an explanation and a recommended action.
%CARD-SEVERITY-MSG:SLOT) is not shown in the error message listings in this manual.
CIP error messages for the adapter task
Explanation A request was sent to the function that handles general requests for the specified port. The request code was not in a range recognized by that function.
Recommended Action The CIP recovered by ignoring the request. Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The specified port was in an invalid state while it attempted to process the specified general request.
Recommended Action The CIP recovered by forcing the port into a well-known state. Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The user has used the test cbus command to request a particular adapter diagnostic to be run. This message is to inform the user that the diagnostic routine has started.
Recommended Action Wait for the next message.
Explanation A diagnostic routine has detected a failure in the ESCON channel adapter (ECA) hardware. These codes are used to locate the specific component that failed.
Recommended Action Report this message to your technical support representative.
Explanation A diagnostic routine has detected a failure in the ESCON channel adapter (ECA) hardware. These codes are used to locate the specific component that failed.
Recommended Action Report this message to your technical support representative.
Explanation A diagnostic routine has failed. The specified port will not be used.
Recommended Action Report this message to your technical support representative.
Explanation A diagnostic requested by the test cbus command failed.
Recommended Action Report this message to your technical support representative.
Explanation A diagnostic requested by the test cbus command completed successfully.
Recommended Action No action is required.
Explanation The diagnostic number requested by the test cbus command is not a valid diagnostic number.
Recommended Action Enter the command again with a valid diagnostic number.
Explanation The test cbus command was used to run a diagnostic on an active interface.
Recommended Action Use the shutdown command to stop the interface and then reissue the diagnostic request.
Explanation A diagnostic routine did not complete execution. The specified port will not be used.
Recommended Action Report this message to your technical support representative.
Explanation A diagnostic requested via the test cbus command did not terminate.
Recommended Action Report this message to your technical support representative.
Explanation Each adapter has an onboard microprocessor. This message indicates that the operation to load the code for that microprocessor failed.
Recommended Action Report this message to your technical support representative.
Explanation An error occurred in the adapter. The information displayed will help personnel in software development to determine the nature of the error.
Recommended Action Report this message to your technical support representative.
Explanation This message is displayed at the start of the logout data. Logout data occurs whenever a problem is detected on the port adapter or, with an ESCON channel adapter (ECA), on the fiber.
Recommended Action If this message is being continually generated on a new installation, it may be an indication that the fiber is not connected properly. Verify that the connector is firmly seated. If a loose fiber was not the cause of these messages, report this message to your technical support representative.
Explanation This message is used when logout information is displayed in order to avoid printing duplicate data.
Recommended Action Report this message to your technical support representative.
Explanation Channel link incident events are being dropped by the channel adapter because of an overflow of incidents.
Recommended Action Use SNMP get to poll the CIP for the current link incident report (LIR) counts.
Explanation There is insufficient memory on the channel adapter to allocate buffers used for generating channel adapter events. Unless the memory is increased, no channel link incident events (SNMP trap) will be generated.
Recommended Action Report this error to your technical support representative.
Explanation This message precedes SCANDATA for the adapter in the specified port. This scan is usually produced as a result of a hardware error.
Recommended Action Report the entire error message and SCANDATA to your technical support representative.
Explanation The data in this message is related to a hardware failure of an adapter.
Recommended Action Report the entire error message and scan data to your technical support representative.
Explanation Prior to the adapter receiving a start command from the route processor, a set of diagnostics is run. If one of them fails, the adapter will not be started when the start command is issued.
Recommended Action Report this message to your technical support representative.
Explanation A wrap plug is installed in the specified port. Wrap diagnostics will run until the plug is removed if this is the only adapter, or if both adapters have wrap plugs installed.
Recommended Action Remove the wrap plug and connect the interface to a channel.
Explanation The wrap plug has been removed, causing the wrap diagnostics to terminate.
Recommended Action No action is required.
Explanation The wrap diagnostics have been terminated because the other adapter is active.
Recommended Action Remove the wrap plug and connect the interface to a channel if you want to use this adapter. Otherwise, no action is required.
CIP error messages for buffer status queue processing
Explanation An Incomplete Data Transfer Notice was received for a channel command word (CCW) that did not perform a read, or read backward. This is a fatal internal logic error.
Recommended Action Report this message to your technical support representative.
Explanation Could not find the end of a more-to-come chain. This is a fatal internal logic error.
Recommended Action Report this message to your technical support representative.
Explanation The sequence of buffer status queue entries received for read commands does not match the sequence of the storage control blocks used for the reads. This is a fatal internal logic error.
Recommended Action Report this message to your technical support representative.
CIP error message relating to the CBUS_ATTN routine, the facility that receives configuration requests and gathers statistics
Explanation The route processor (RP) requested that the CIP store a configuration command at an invalid memory address. The CIP recovered by ignoring the request.
Recommended Action Report this error to your technical support representative.
CIP error messages for the CBUS_WRITE facility, which is used by the enhanced online insertion and removal (EOIR) support on the CIP to track write operations to the memory device and reissue them if a ciscoBus problem occurs
Explanation The type parameter in the write tracking table is invalid. This is an internal CIP logic error. The CIP recovered by ignoring the entry.
Recommended Action Report this error to your technical support representative.
Explanation A write error interrupt occurred, but the hardware that keeps track of the address of the error does not have a valid address.
Recommended Action Report this error to your technical support representative.
Explanation A write error was detected, but there was no corresponding entry in the table that keeps track of these entries. This is an internal CIP logic error. The CIP recovered by ignoring the write error.
Recommended Action Report this error to your technical support representative.
Explanation This is a debugging print of the CBUS write stack. It is associated with the CBUS_WRITE-3-MISSING error message.
Recommended Action Report this error to your technical support representative.
Explanation A write operation to an address other than the memory device (MEMD) timed out. This is probably a hardware problem. The CIP failed and attempted to restart.
Recommended Action Record the address indicated in the error message. The address will enable a support representative to determine which component to replace. Report this error to your technical support representative.
CIP error messages for channel card adapter processing
Explanation The adapter notified the CIP that an accept command response was issued. The CIP does not request notification of accept command response messages. Therefore, this message means the adapter has generated an unexpected message.
Recommended Action Normal processing will resume, but it would be useful for software development personnel to know that this message has occurred. Report this message to your technical support representative.
Explanation The adapter presented the CIP with a message using an undefined code point. This is a fatal internal logic error.
Recommended Action Report this message to your technical support representative.
Explanation The adapter notified the CIP that the buffer status queue was full. The CIP never provides enough buffers to the adapter to cause the buffer status queue to become full. This is a fatal internal logic error.
Recommended Action Report this message to your technical support representative.
Explanation A user attempted to start the parallel channel adapter (PCA) with the select bypass switch in the BYPASS position. The PCA cannot go online with the switch in the BYPASS position.
Recommended Action Move the select bypass switch on the PCA-Y cable from the BYPASS position to the SELECT position.
Explanation The adapter notified the CIP that a halt subchannel command was issued by the host, but provided the CIP with an undefined type of cancel.
Recommended Action The CIP software recovered, but software development personnel should be informed. Report this message to your technical support representative.
Explanation The adapter notified the CIP that a halt subchannel command was issued by the host for an undefined path. This is an internal logic error.
Recommended Action The CIP software recovered, but software development personnel should know about this problem. Report this message to your technical support representative.
Explanation The adapter notified the CIP that a start subchannel command was issued by the host for an undefined path. This is an internal logic error.
Recommended Action The CIP software recovered, but software development personnel should know about this problem. Report this message to your technical support representative.
Explanation The adapter notified the CIP that a connection was established for a device other than the one that the CIP had just requested. This is an internal logic error.
Recommended Action The CIP software recovered, but software development personnel should know about the problem. Report this message to your technical support representative.
Explanation When a device error occurs, the adapter specifies the type of error so that the correct recovery action can be performed. The type specified is not defined. This is a fatal internal logic error.
Recommended Action Report this message to your technical support representative.
Explanation A device error was generated and either it occurred while status was being presented but no device was active, or it occurred for an undefined device. This is a fatal internal logic error.
Recommended Action Report this message to your technical support representative.
Explanation A device error occurred, but the path specified in the device error message is not defined. This is a fatal internal logic error.
Recommended Action Report this message to your technical support representative.
Explanation During a device-level error, the control unit busy statistic was not updated because the timer was never started.
Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Explanation The adapter reported an ending status interrupt for a channel command word that should not have caused the CIP to be notified. This is an internal logic error.
Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Explanation The adapter sent a request to the CIP to perform a logout, but the command modifier in the message was not a valid value. This is an internal logic error.
Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Explanation The adapter requested that the CIP present the status of an undefined path. This is an internal logic error.
Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Explanation The adapter has requested the CIP to perform reset processing for an undefined path. This is an internal logic error.
Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Explanation The adapter requested that the CIP reset a logical path, but the flags on the reset request were not valid. This is an internal logic error.
Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Explanation The CIP was notified that an I/O operation was attempted with a storage control block that was marked as not ready. The specified I/O operation should never have a not ready storage control block. This is a fatal internal logic error.
Recommended Action Report this message to your technical support representative.
Explanation The adapter requested that the CIP perform a selective reset, but the request code in the message was not a valid value. This is an internal logic error.
Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Explanation The adapter has requested that the CIP perform a selective reset on an undefined logical path. This is an internal logic error.
Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Explanation The adapter has presented the CIP with notification that status was accepted by the channel, but the request code in the status message was not a valid code. This is an internal logic error.
Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Explanation During status presentation, the control unit busy statistic was not updated because the timer was never started.
Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Explanation The adapter requested that the CIP perform a system reset, but the request code in the message was not a valid value. This is an internal logic error.
Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Explanation The mainframe wrote data to the CIP and the number of buffers required to hold all the data being written was more than the total number of buffers allocated on the CIP for that purpose. This is a fatal error.
Recommended Action Report this message to your technical support representative.
Explanation The wrap plug is installed on the parallel channel adapter (PCA) in the specified port. The PCA cannot be used unless connected to a channel.
Recommended Action Remove the wrap plug and connect the channel cables.
Explanation The adapter requested that the CIP perform a request. When the CIP tried to present the response to the request, it was not able to write the common communication area. This is a fatal internal logic error.
Recommended Action Report this message to your technical support representative.
Channel adapter Cisco IOS wrappers error messages
Explanation An internal software error occurred while generating this message from the channel adapter. It indicates that a buffer has been corrupted.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An internal software error occurred while generating this message from the channel adapter. It indicates that a buffer has been freed twice.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An internal software error occurred while generating debug messages from the channel adapter.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. Turn off IPC debugging on the channel adapter until this can be fixed.
Explanation An internal software error occurred while generating this message from the channel adapter.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An internal software error occurred while generating debug messages from the channel adapter.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. Turn off IPC debugging on the Channel Adpater until this can be fixed.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The Channel Adpater is not equipped with enough memory to accommodate all the configured channel adapter features. The Channel Adpater may be rendered inoperable, or certain features may not work properly.
Recommended Action Upgrade the channel adapter with more memory.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
CIP error messages related to the Common Link Access for Workstations (CLAW) facility
Explanation An attempt was made to establish a connection, but the application names specified on the host do not match any of the application names specified in the router configuration.
Recommended Action Correct the host and/or router configuration.
Explanation An attempt was made to establish a connection, but the application names specified on the host do not match any of the application names specified in the router configuration.
Recommended Action Correct the host and/or router configuration.
Explanation All the data sent in an IP datagram should fit in one transfer list element. This message required more than one.
Recommended Action Report this error to your technical support representative.
Explanation During the system-validate processing, the host name configured in the router did not match the host name configured on the host.
Recommended Action Correct the host and/or router configuration.
Explanation The host is configured to receive frames that are smaller than the CMCC is designed to send.
Recommended Action The CMCC has notified the host of the problem. Reconfigure the frame size on the host to be 4096 or larger.
Explanation The host has generated a bad return code in the response to the system-validate request sent by the CMCC.
Recommended Action Check the return code and correct the configuration as appropriate.
Explanation The version specified in a message from the host is not the same as the version specified in the CMCC.
Recommended Action Report this error to your technical support representative.
Explanation During the system-validate processing, the workstation name configured in the router did not match the workstation name configured on the host.
Recommended Action Correct the host and/or router configuration.
Explanation The host is configured to write more data in a single frame to the CMCC than the CMCC is designed to receive.
Recommended Action The CMCC will notify the host of the problem. Reconfigure the frame size on the host to be 4096 or smaller.
Explanation The host sent a CLAW command with an invalid CLAW command code.
Recommended Action The CMCC will ignore the request. Report this error to your technical support representative.
Explanation When running with IP Host Backup enabled, the application that owns the IP address is stored in a tree. When the application that owns the IP address is done with the IP address, the owner removes itself from the tree. Before removing itself, a check is made to see if it exists. It did exist, but the delete request failed.
Recommended Action This is a fatal internal logic error. The CIP microcode has been reinitialized. If this error persists, stop using the IP Host Backup feature until the problem can be corrected.
Explanation When running with IP Host Backup enabled, the application that owns the IP address is stored in a tree. When the application that owns the IP address is done with the IP address, the owner removes itself from the tree. Before removing itself, a check is made to verify that the entry exists. The entry did not exist.
Recommended Action This is an internal logic error. It may prevent IP Host Backup from working properly. If this error persists, stop using the IP Host Backup feature until the problem can be corrected.
Explanation When running with IP Host Backup enabled, the application that owns the IP address is stored in a tree. When the application that owns the IP address is done with the IP address, the owner removes itself from the tree. Before removing itself, a check is made to see if it is really the owner of the IP address. It was not the owner.
Recommended Action This is an internal logic error. It may prevent IP Host Backup from working properly. If this error persists, stop using the IP Host Backup feature until the problem can be corrected.
Explanation When running with IP Host Backup enabled, the application that owns the IP address is stored in a tree. When an attempt is made to claim the IP address, the application is inserted into the tree. If the insert fails, then the tree is searched to find the owner of the application so that an appropriate error message may be issued. If this search fails, then this message is issued to indicate that the tree is corrupted.
Recommended Action This is a fatal internal logic error. The CIP microcode has been reinitialized. If this error persists, stop using the IP Host Backup feature until the problem can be corrected.
Explanation The host sent a CLAW option request command for an invalid link.
Recommended Action The CMCC will ignore the request. Report this error to your technical support representative.
Explanation When running in IP Host Backup mode, the first device listed attempted to establish a CLAW connection to use the specified IP address. The IP address is already in use by the second device.
Recommended Action If the second CLAW device is the desired owner of the IP address, then stop the first CLAW device and restart the second CLAW device. If not, stop the second CLAW device.
Explanation The host sent a CLAW option request to define an application that already exists.
Recommended Action The CMCC will ignore the request. Report this error to your technical support representative.
Explanation The amount of data being read by the channel exceeded the size of the read channel command word (CCW).
Recommended Action Report this error to your technical support representative.
Explanation A packet was received from the host, but the logical link specified with the data does not represent a valid connection.
Recommended Action The packet was dropped. Report this error to your technical support representative.
Explanation An attempt was made to allocate a link ID to assign to a connection request, but all link IDs were in use. This should not occur.
Recommended Action The CMCC software has recovered by generating a bad return code to the requester. Report this error to your technical support representative.
Explanation Not enough free memory is available in order for the CLAW task to replenish the channel buffers after getting a write buffer.
Recommended Action Install more memory for the CMCC, or configure fewer devices.
Explanation The CLAW connection request sequence was attempted before a system validate sequence completed successfully. This is a CLAW protocol error.
Recommended Action Restart the host application and the CMCC application. If this problem persists, contact your technical support representative.
Explanation The host software attempted to disconnect a link that was not established.
Recommended Action The CMCC software has ignored the request. Report this error to your technical support representative.
Explanation No available transmit buffers exist, but the CLAW connection has not reached its transmit buffer limit.
Recommended Action The packet has been dropped. Report this error to your technical support representative.
Explanation The host sent an unknown CLAW option request command.
Recommended Action The CMCC software has ignored the request. Report this error to your technical support representative.
Explanation The link ID in a disconnect is not in the valid range for all CLAW links.
Recommended Action The CMCC software has recovered by ignoring this request. Report this error to your technical support representative.
Explanation Each SCB pointing to data for the host is classified as a particular type before being queued to the host. After sending a block of data, the CLAW application detected an invalid type defining the data. This is an internal logic error.
Recommended Action The CMCC has recovered by ignoring the transfer. Report this error to your technical support representative.
Explanation An invalid parameter was received in a sysmgt call.
Recommended Action Report this error to your technical support representative.
Explanation The router has sent an IP datagram to the CMCC that is larger than the maximum transmission unit (MTU) for the CMCC. The MTU for the CLAW connection is set on the DEVICE statement for the CLAW device in the host TCPIP configuration file (PROFILE.TCPIP). The IP datagram has been dropped.
Recommended Action Check the configured IP MTU on the CMCC, and the host configuration file. If correct, report this problem to your technical support representative.
Explanation The request type in a transfer element is not a valid value. This is an internal logic error.
Recommended Action The CMCC software has recovered by ignoring the transfer element. Report this error to your technical support representative.
Explanation The request type in a transfer element is valid but is not expected to occur at this time. This is an internal logic error.
Recommended Action The CMCC software has recovered by ignoring the transfer element. Report this error to your technical support representative.
Explanation An attempt was made to configure a CLAW device on the virtual port adapter. CLAW devices are only permitted on real port adapters.
Recommended Action The configuration request was ignored. Report this error to your technical support representative.
Explanation The mainframe wrote data to the read subchannel. This is most likely the result of a misconfiguration under a VM guest where the write device is attached to the read subchannel.
Recommended Action Check the device definitions on the host. If running under VM, verify that the write device is attached to the write subchannel and the read device is attached to the read subchannel.
LLC Transmission group error messages
Explanation This is an informative message given when a CMPC TG is in the active state.
Recommended Action No action is required.
Explanation This error message is given when the length values in Xid3 control vectors exceed the length field in the Xid3 message. The contents of the Xid3 immediately follow.
Recommended Action No action is required.
Explanation This error message is given when a loop back TG is configured by using the same local and remote SAP values.
Recommended Action For loopback configurations, the local and remote SAPs should be different. Change one of the SAP values.
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.
Explanation This is an informative message given when a CMPC TG notices a CV22 with sense data.
Recommended Action Indicates that an endpoint of the APPN session has detected a protocol problem. No action on this router is required. Check the log for each of the two endpoints and take appropriate action.
Explanation This is an informative message given when a CMPC TG is initialized. The message indicates which TG has been configured.
Recommended Action No action is required.
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.
Explanation This message is given when an attempt by CMPC TG to open the Logical Link Control (LLC) adapter failed.
Recommended Action Ensure that the LLC adapter referenced by this TG is configured.
Explanation A call to create a pool or get a buffer failed.
Recommended Action Report this error to your technical support representative.
Explanation This is an informative message given when a CMPC TG is no longer in the active state.
Recommended Action No action is required.
Explanation This is an informative message given when a CMPC TG notices a CV22 with sense data.
Recommended Action Indicates that an endpoint of the APPN session has detected a protocol problem. No action on this router is required. Check the log for each of the two endpoints and take appropriate action.
Explanation This is an informative message given when a CMPC TG is removed.
Recommended Action No action is required.
Explanation This message is given when an invalid parameter was received in a SYSMGT call.
Recommended Action Report this error to your technical support representative.
Explanation This message is given when an invalid parameter was received in a SYSMGT call.
Recommended Action Report this error to your technical support representative.
CIP error messages related to the configuration facility
Explanation The port type function returned an invalid port type. This is an internal logic error.
Recommended Action Report this message to your technical support representative.
Explanation During the shutdown processing, buffers were found queued to the channel. One of the device tasks did not properly flush the data prior to shutting down.
Recommended Action Report this message to your technical support representative.
Explanation The router has attempted to configure a parallel channel adapter (PCA) with an invalid channel speed.
Recommended Action The CIP has recovered by ignoring the request. Report this error to your technical support representative.
Explanation The virtual circuit number specified by the route processor on a configuration request is too large. This is an internal logic error. The configuration request was ignored.
Recommended Action Report this message to your technical support representative.
Explanation The route processor attempted to configure an odd address for a CLAW device. CLAW configuration requests must specify an even address. This is an internal logic error. The configuration request was ignored.
Recommended Action Report this message to your technical support representative.
Explanation During initialization, each application that will receive configuration commands from the system registers routines to process its configuration commands. An incorrect registration identifier was used.
Recommended Action This is a fatal error. The CIP has been restarted. Report this message to your technical support representative.
Explanation The route processor attempted to reconfigure an existing device without first removing the device. This is an internal logic error. The original configuration remains.
Recommended Action Report this message to your technical support representative.
Explanation A feature was configured that is not supported on this CIP hardware revision. The feature was activated, but is not guaranteed to work properly.
Recommended Action Upgrade your CIP to either a CIP with hardware revision 4.4 or to a CIP2.
Explanation The route processor attempted to configure an existing device. This is an internal logic error. The configuration request was ignored.
Recommended Action Report this message to your technical support representative.
Explanation The route processor attempted to configure a device using a virtual circuit number that was already in use by another device. This is an internal logic error. The configuration request was ignored.
Recommended Action Report this message to your technical support representative.
Explanation The route processor attempted to configure a device using a virtual circuit number that was already in use. There was no device found associated with this virtual circuit number. This is an internal logic error. The configuration request was ignored.
Recommended Action Report this message to your technical support representative.
Explanation The CIP does not have sufficient storage to allocate an application block. The configuration request was ignored.
Recommended Action Purchase the next-larger storage size for the CIP, or configure fewer devices.
Explanation Configuration command processing is dynamically set up when features are added to an image. The required feature to process a configuration command is not a part of the current image.
Recommended Action Either run a CIP microcode load that supports the configuration command being issued, or do not issue that configuration command.
Explanation The route processor attempted to unconfigure a device, but the control unit image for the device could not be located. This is an internal logic error. The unconfigure request was ignored.
Recommended Action Report this message to your technical support representative.
Explanation The route processor attempted to unconfigure a device, but the device was not defined. This is an internal logic error. The unconfigure request was ignored.
Recommended Action Report this message to your technical support representative.
Explanation No storage was available for the device block. The configuration request is ignored.
Recommended Action Purchase the next-larger storage size for the CIP, or configure fewer devices.
Explanation An attempt was made to configure more than 64 different paths. Only 64 paths are supported. The configuration request was ignored.
Recommended Action Configure fewer paths.
Explanation There is not enough memory to process configuration commands in the channel adapter.
Recommended Action Verify the amount of memory installed on the channel adapter and upgrade if necessary.
Explanation No storage was available for the logical path table. The configuration request was ignored.
Recommended Action Purchase the next-larger storage size for the CIP, or configure fewer devices.
Explanation Whenever the system sends a configuration command to the CIP, it responds with a confirmation message. There was not sufficient available memory on the CIP to allocate a block to hold a confirmation message.
Recommended Action If you are not at the maximum CIP memory configuration, additional memory may be installed on the CIP. Otherwise, configure fewer channel connections.
Explanation The route processor attempted to unconfigure a device, but the virtual circuit number for the device is not defined. This is an internal logic error. The unconfigure request was ignored.
Recommended Action Report this message to your technical support representative.
Explanation The route processor attempted to configure an odd address for an offload device. Offload configuration requests must specify an even address. This is an internal logic error. The configuration request was ignored.
Recommended Action Report this message to your technical support representative.
Explanation During initialization, each application that uses the virtual port adapter registers to receive notification when the shutdown or no shutdown commands are issued on that adapter. The table to hold these registration requests is too small.
Recommended Action This is a fatal error. The CIP has been restarted. Report this message to your technical support representative.
Explanation A feature was configured in which the configuration command is larger than the channel adapter can process. The configuration command will be ignored by the channel adapter.
Recommended Action Report this message to your technical support representative.
Explanation An attempt was made to define more than 256 devices. Only 256 devices are supported on an adapter. The configuration request was ignored.
Recommended Action Configure fewer devices.
Explanation Configuration command processing is dynamically set up when features are added to an image. The required feature to process a configuration command is not a part of the current image.
Recommended Action Either run a CIP microcode load that supports the configuration command being issued, or do not issue that configuration command.
Explanation Work was pending when the router finished processing an unconfigure request. This is an internal logic error.
Recommended Action Report this message to your technical support representative.
CIP error messages for the channel transport architecture device task/mapper
Explanation All the data sent in a CSNA write should fit in one transfer list element. This message required more than one.
Recommended Action Report this error to your technical support representative.
Explanation An error has been detected in the processing of host-bound messages.
Recommended Action Report this error to your technical support representative.
Explanation A host write was received while the setup state equalled "pending open."
Recommended Action Report this error to your technical support representative.
Explanation A host read was received while the setup state equalled "setup open."
Recommended Action Report this error to your technical support representative.
Explanation A host read was received while the setup state equalled "pending complete."
Recommended Action Report this error to your technical support representative.
Explanation A host write was received while the setup state equalled "setup complete."
Recommended Action Report this error to your technical support representative.
Explanation Because of an error on the channel, some data intended to be sent to the channel was not sent to the channel. Virtual Telecommunications Access Method (VTAM) will receive an error indication and should retry the operation.
Recommended Action Report this error to your technical support representative.
Explanation This subchannel has been inactive for more than the subchannel timeout interval. Most likely, the host has been halted or Virtual Telecommunications Access Method (VTAM) has been terminated by a Z NET,CANCEL command.
Recommended Action Restart the VTAM/HOST and activate the XCA major node.
Explanation This is an informative message given when a CSNA device is initialized. The device string is in the form CSNAx/yyyy/zz, where x is the daughter board number, yyyy is the path, and zz is the device number.
Recommended Action No action is required.
Explanation The amount of data being read by the channel exceeded the size of the read channel command word (CCW).
Recommended Action Report this error to your technical support representative.
Explanation An error occurred in the message from the host, as indicated by the description.
Recommended Action Report this error to your technical support representative.
Explanation An error occurred in the message from the host, as indicated by the description.
Recommended Action Report this error to your technical support representative.
Explanation A received CTA command code is not in the valid range.
Recommended Action Report this error to your technical support representative.
Explanation A call to create a pool or get a buffer failed.
Recommended Action Report this error to your technical support representative.
Explanation A queue init/alloc failed.
Recommended Action Report this error to your technical support representative.
Explanation This is an informative message given when a CSNA device is shutdown. The device string is in the form CTA n/mmmm/yy, where n is the daughterboard number, mmmm is the path, and yy is the device number.
Recommended Action No action is required.
Explanation An invalid parameter was received in a SYSMGT call.
Recommended Action Report this error to your technical support representative.
Explanation An invalid parameter was received in a SYSMGT call.
Recommended Action Report this error to your technical support representative.
Explanation An invalid parameter was received in a SYSMGT call.
Recommended Action Report this error to your technical support representative.
Explanation An unrecognized event was received by the CTA attn fsm. This is an unrecoverable event. This instance of CTA is initialized and the XCA node must be cycled to resume operation.
Recommended Action Report this error to your technical support representative.
Explanation An XFER element type code not in the valid range was received.
Recommended Action Report this error to your technical support representative.
Explanation An LSI command code not in the valid range was received.
Recommended Action Report this error to your technical support representative.
Explanation An LSI status code not valid for the command was received.
Recommended Action Report this error to your technical support representative.
CIP error messages issued when nonrecoverable errors occur on the CIP
Explanation A line from the call chain. This is part of a fatal error dump. The CIP has hit an unrecoverable problem and is printing out context information about where the problem occurred.
Recommended Action Report this to your technical support representative.
Explanation A fatal internal CIP error occurred. The message includes hardware version information.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A fatal internal CIP error occurred. The message includes software version information.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation During initialization, each application that uses an IP address registers a routine to be used by the console dbcb command to fetch the IP address. The identifier associated with the routine was not within a valid range.
Recommended Action This is a fatal error. The CIP has been restarted.
Explanation During initialization, each application that uses global transmit buffers registers a routine to be used by the console dbcb command to fetch the buffer counts. The identifier associated with the routine was not within a valid range.
Recommended Action This is a fatal error. The CIP has been restarted.
Explanation A fatal internal CIP error occurred. The CIP failed.
Recommended Action Report this to your technical support representative.
Explanation The message detects invalid addresses while trying to perform a stack dump.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The message displays data from the low core area of the CIP.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The CIP has failed. The low core area of the CIP will begin to dump.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation This indicates the CIP has finished dumping all debugging information and is attempting a restart.
Recommended Action Report this to your technical support representative.
Explanation This is a line of internal interrupt stack information.
Recommended Action Report this to your technical support representative.
Explanation This is a line of internal interrupt stack information.
Recommended Action Report this to your technical support representative.
Explanation This is a line of internal interrupt stack information.
Recommended Action Report this to your technical support representative.
Explanation This is a line of internal interrupt stack information.
Recommended Action Report this to your technical support representative.
Explanation This is a line of internal interrupt stack information.
Recommended Action Report this to your technical support representative.
Explanation This is a line of internal interrupt stack information.
Recommended Action Report this to your technical support representative.
Explanation This is a line of internal interrupt stack information.
Recommended Action Report this to your technical support representative.
Explanation This is a line of internal interrupt stack information.
Recommended Action Report this to your technical support representative.
Explanation This is a line of internal interrupt stack information.
Recommended Action Report this to your technical support representative.
Explanation This is a line of internal interrupt stack information.
Recommended Action Report this to your technical support representative.
Explanation This is a line of internal interrupt stack information.
Recommended Action Report this to your technical support representative.
Explanation This is a line of internal interrupt stack information.
Recommended Action Report this to your technical support representative.
Explanation This message begins a dump of the current task's stack. This is part of a fatal error dump. The CIP has hit an unrecoverable problem and is printing out context information about where the problem occurred.
Recommended Action Report this to your technical support representative.
Explanation This message is the second line from the current task's stack dump. This is part of a fatal error dump. The CIP has hit an unrecoverable problem and is printing out context information about where the problem occurred.
Recommended Action Report this to your technical support representative.
Explanation The message displays stack information of the stack overflow task.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation This message begins a dump of the internal interrupt stack. If this has occurred, the CIP has failed.
Recommended Action Report this to your technical support representative.
Explanation This is a display of the internal trace table header.
Recommended Action Report this to your technical support representative.
Explanation This is a single entry from the internal trace table.
Recommended Action Report this to your technical support representative.
Explanation This message begins a dump of the internal trace table. If this has occurred, the CIP has failed.
Recommended Action Report this to your technical support representative.
CIP error messages for diagnostic processing
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.
Recommended Action Report this message to your technical support representative.
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.
Recommended Action Report this message to your technical support representative.
Error messages for the function on the CIP that is responsible for transferring data between the dynamic RAM (DRAM) on the CIP and memory device facility
Explanation An error occurred in one of the hardware FIFOs used in the DMA transfer operation. This failure was detected and resulted in a packet being dropped.
Recommended Action Report this error to your technical support representative.
Explanation An unsupported DMA request type was detected.
Recommended Action Copy the error message exactly as it appears, issue the show tech-support command and call your technical service representative with the information.
Explanation The CBUS controller started a read or write operation and did not receive a response from the CBUS indicating the completion status. The packet was dropped.
Recommended Action Report this error to your technical support representative. This could be an indication that the CIP is not properly seated in its slot.
Explanation A parity error was detected on the CBUS during a data transfer.
Recommended Action The packet has been dropped. Report this error to your technical support representative.
Explanation A parity error was detected during data transfer.
Recommended Action The packet has been dropped. Report this error to your technical support representative.
Explanation A failure occurred while trying to transfer a packet.
Recommended Action Copy the error message exactly as it appears, issue the show tech-support command and call your technical service representative with the information.
Explanation The CIP was notified that the current DMA transfer had completed, but the DMA status register indicated the transfer was still in progress.
Recommended Action The CIP has restarted. Report this error to your technical support representative.
Explanation The CBUS did not respond to the DMA controller within 10 microseconds.
Recommended Action The packet has been dropped. Report this error to your technical support representative.
Explanation A DMA interrupt occurred, but no transfer was pending. This is either an internal logic error, or a hardware failure.
Recommended Action The CIP has restarted. Report this error to your technical support representative.
Explanation An error occurred during a DMA transfer. These are the DMA hardware controller registers at the end of the transfer.
Recommended Action Report this error to your technical support representative.
CIP error message related to the internal routine for allocating transfer elements
Explanation An attempt was made to allocate a transfer element and no storage was available. This is a fatal error.
Recommended Action The CIP has restarted. Report this error to your technical support representative.
Channel Port Adapter GT64011 error message
Explanation An unexpected GT64011 error interrupt occurred.
Recommended Action Ensure that all port adapters are properly seated. If this error recurs, contact your technical support representative.
Explanation An unexpected GT64011 error interrupt occurred.
Recommended Action Make sure all port adapters are properly seated. If this error recurs, contact your technical support representative.
Explanation The GT64011 was found to have an incompatible device or vendor ID.
Recommended Action If this error recurs, contact your technical support representative.
CIP error messages for the interrupt handler interface
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 technical support representative.
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 technical support representative.
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 technical support representative.
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 technical support representative.
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 technical support representative.
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 technical support representative.
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 technical support representative.
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 technical support representative.
CIP error messages related to the interprocess communication (IPC) subfacility
Explanation An error occurred in the 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, and report it to your technical support representative.
Explanation An internal inconsistency was found in some IPC data structures.
Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative.
Explanation An internal inconsistency was found in some IPC data structures.
Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative, along with the output of the show ipc status and show ipc queue commands.
Explanation Someone requested a message that was too large for the IPC system.
Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative, along with the output of the show ipc status command.
Explanation An internal inconsistency was found in some IPC data structures.
Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative.
Explanation The given IPC message header cache has emptied.
Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative, along with the output of the show ipc status command.
Explanation The 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, and report it to your technical support representative.
Explanation The IPC user failed to provide any means of handling the received message.
Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative, along with the output of the show ipc ports command.
Explanation The IPC protocol 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 technical support representative.
Explanation The IPC user attempted a prohibited call into IPC while IPC was running on the interrupt stack.
Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative, along with the output of the show ipc status command.
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, and report it to your technical support representative.
Explanation An internal inconsistency was found in some IPC data structures.
Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative.
CMCC driver interprocess communication error messages
Explanation The IPC DRVR packet switch notification detected a DMA transfer error.
Recommended Action The IPC subsystem is used by the channel adapter loader and channel adapter network management. A single 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 need to reload the channel adapter microcode. In any case, report this message to your technical support representative.
Explanation The IPC DRVR transport subsystem could not obtain the necessary memory.
Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative.
|
|