CMCC System Error Messages

CMCC ADAPTER Messages

CMCC System Error Messages

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 chapter "About this Manual" 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]

Table 5: Error Message Severity Levels

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

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

Table 6: CMCC Facility Codes

Code Facility

ADAPTER

Adapter task

BSQ

Buffer status queue processing

CBUS_ATTN

ciscoBus controller statistics

CBUS_WRITE

ciscoBus controller write support

CCA

Channel card adapter processing

CIOS

Channel adapter Cisco IOS wrapper

CLAW

Common Link Access for Workstations (CLAW)

CMPCTG

Logical Link Control (LLC) Transmission Group

CONFIG

Configuration processing

CTA

Channel transport architecture device task/mapper

DEBUGGER

Messages issued when nonrecoverable errors occur

DIAG

Diagnostic testing

DMA

Direct memory access (DMA)

GET_DATA

Internal routine for allocating transfer elements

GT64011

Channel port adapter GT64011

INT

Interrupt handler interface

IPC

Interprocess communication (IPC) subfacility

IPC_DRVR

Interprocess communication (IPC) driver

IPP

Encryption feature

LOADER

Relocating loader

LOVE

Channel Interface Processor (CIP)-to-router statistics

MBUF

Memory buffer

MEMD

Memory device

MPC

Multipath Channel (MPC) protocol

MSG802

IEEE 802.2cx Logical Link Control (LLC) protocol stack

NEVADA

Interrupt controller

OFFL

Offload protocol

PACK

Packed extension to the Common Link Access Workstation (CLAW)

PKTS

Packet switching Application Programming Interface (API)

SCB

Storage control block

SCHED

Multitasking scheduler

SLC

Serial link controller

SLCI

Signaling Link Code Interface (SLCI)

SSI802

Common Service System Service Interface (SSI)

SUBSYS

Software subsystem

SYS

Channel Interface Processor (CIP) operating system

SYSMGT_EVENT

Network management processing for system management event generation

SYSMGT_RPC

Network management processing for system management remote-procedure call (RPC) operation

TN3270

TN3270 server terminal emulation

UTIL

Channel adapter utilities

XCPA

Channel port adapter

Code	Facility
ADAPTER	Adapter task
BSQ	Buffer status queue processing
CBUS_ATTN	ciscoBus controller statistics
CBUS_WRITE	ciscoBus controller write support
CCA	Channel card adapter processing
CIOS	Channel adapter Cisco IOS wrapper
CLAW	Common Link Access for Workstations (CLAW)
CMPCTG	Logical Link Control (LLC) Transmission Group
CONFIG	Configuration processing
CTA	Channel transport architecture device task/mapper
DEBUGGER	Messages issued when nonrecoverable errors occur
DIAG	Diagnostic testing
DMA	Direct memory access (DMA)
GET_DATA	Internal routine for allocating transfer elements
GT64011	Channel port adapter GT64011
INT	Interrupt handler interface
IPC	Interprocess communication (IPC) subfacility
IPC_DRVR	Interprocess communication (IPC) driver
IPP	Encryption feature
LOADER	Relocating loader
LOVE	Channel Interface Processor (CIP)-to-router statistics
MBUF	Memory buffer
MEMD	Memory device
MPC	Multipath Channel (MPC) protocol
MSG802	IEEE 802.2cx Logical Link Control (LLC) protocol stack
NEVADA	Interrupt controller
OFFL	Offload protocol
PACK	Packed extension to the Common Link Access Workstation (CLAW)
PKTS	Packet switching Application Programming Interface (API)
SCB	Storage control block
SCHED	Multitasking scheduler
SLC	Serial link controller
SLCI	Signaling Link Code Interface (SLCI)
SSI802	Common Service System Service Interface (SSI)
SUBSYS	Software subsystem
SYS	Channel Interface Processor (CIP) operating system
SYSMGT_EVENT	Network management processing for system management event generation
SYSMGT_RPC	Network management processing for system management remote-procedure call (RPC) operation
TN3270	TN3270 server terminal emulation
UTIL	Channel adapter utilities
XCPA	Channel port adapter

Table 7: Representation of Variable Fields in Error Messages

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)

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.

Note The prepended portion of the error message (%CARD-SEVERITY-MSG:SLOT) is not shown in the error message listings in this manual.

CMCC ADAPTER Messages

The following are Channel Interface Processor (CIP) error messages for the adapter task.

Error Message

%ADAPTER-6-BADREQUEST: Bad request code [dec] generated on port [dec]

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 Channel Interface Processor (CIP) has recovered by ignoring the request. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%ADAPTER-6-BADSTATE: Bad state: port [dec], request code [dec], state [dec], flags [hex]

Explanation The specified port was in an invalid state while it was attempting to process the specified general request.

Recommended Action The Channel Interface Processor (CIP) recovered by forcing the port into a valid state. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%ADAPTER-6-DIAGBEGIN: [chars] diagnostic starting

Explanation The user has used the test cbus command to request a particular adapter diagnostic to be run. This message informs the user that the diagnostic routine has started.

Recommended Action Wait for the next message.

Error Message

%ADAPTER-0-DIAGDATA: Module Call: [hex][hex] Error ID: [hex][hex], MSGDEF_LIMIT_FAST

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

Error Message

%ADAPTER-6-DIAGDATA2: Module Call: [hex][hex] Error ID: [hex][hex]

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.

Error Message

%ADAPTER-0-DIAGFAIL: Port [dec] failed the [chars] diagnostic, MSGDEF_LIMIT_FAST

Explanation A diagnostic routine has failed. The specified port will not be used.

Error Message

%ADAPTER-6-DIAGFAIL2:[chars] diagnostic failed

Explanation A diagnostic requested by the test cbus command failed.

Error Message

%ADAPTER-6-DIAGGOOD2:[chars] diagnostic ran successfully

Explanation A diagnostic requested by the test cbus command has completed successfully.

Recommended Action No action is required.

Error Message

%ADAPTER-6-DIAGRANGE:Diagnostic number ([dec]) out of range 0-[dec]

Explanation The diagnostic number requested by the test cbus command is invalid.

Recommended Action Reenter the command with a valid diagnostic number.

Error Message

%ADAPTER-6-DIAGSTOP:Interface must be shutdown to run diagnostic

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.

Error Message

%ADAPTER-0-DIAGTERM: Port [dec]: The [chars] diagnostic failed to terminate, MSGDEF_LIMIT_FAST

Explanation A diagnostic routine did not end when expected. The specified port will not be used.

Error Message

%ADAPTER-6-DIAGTERM2: [chars] diagnostic failed to terminate

Explanation A diagnostic requested from the test cbus command did not end when expected.

Error Message

%ADAPTER-0-LOADFAIL: Port [dec] microcode load failed.

Explanation Each adapter has an onboard microprocessor. This message indicates that the operation to load the code for that microprocessor has failed.

Error Message

%ADAPTER-6-LOGDATA: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]

Explanation An error occurred in the adapter. The information displayed will help software developers determine the nature of the error.

Error Message

%ADAPTER-6-LOGOUT: Port [dec] logout data. Adapter microcode [hex]

Explanation This message indicates 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 indicate 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 Cisco technical support representative.

Error Message

%ADAPTER-6-LOGSAME: [hex] to [hex] same as above

Explanation This message is used when logout information is displayed to avoid printing duplicate data.

Error Message

%ADAPTER-6-NO_CHAN_EV_BUF: No channel event buffer: Daughter board [dec], 60*ONESEC

Explanation Channel link incident events are being dropped by the channel adapter because of an overflow of incidents.

Recommended Action Use Simple Network Management Protocol (SNMP) to poll the Channel Interface Processor (CIP) for the current link incident report (LIR) counts.

Error Message

%ADAPTER-6-NO_CHAN_EV_POOL: Could not allocate channel event pool

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 (Simple Network Management Protocol [SNMP) traps] will be generated.

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

Error Message

%ADAPTER-6-SCAN: Port [dec] scan data. Adapter microcode [hex]

Explanation This message precedes the "SCANDATA" error message 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, including the preceding "SCANDATA" error message, to your Cisco technical support representative.

Error Message

%ADAPTER-6-SCANDATA: [hex] [hex] [hex] [hex] [hex]

Explanation The data in this message is related to the hardware failure of an adapter.

Recommended Action Report the entire error message and scan data to your Cisco technical support representative.

Error Message

%ADAPTER-0-START_FAIL: Diagnostics failed for port [dec], start request ignored.

Explanation Prior to receipt by the adapter of a start command from the route processor, a set of diagnostics is run. If one of them fails, then the adapter will not be started when the start command is issued.

Error Message

%ADAPTER-6-WRAP: Wrap plug detected in port [dec]. Wrap loop started, MSGDEF_LIMIT_FAST

Explanation A wrap plug is installed in the specified port. Wrap diagnostics 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.

Error Message

%ADAPTER-6-WRAPSTOP1: Wrap plug removed from port [dec]. Wrap loop ended, MSGDEF_LIMIT_FAST

Explanation The wrap plug has been removed causing the wrap diagnostics to end.

Recommended Action No action is required.

Error Message

%ADAPTER-6-WRAPSTOP2: Port [dec] active. Port [dec] wrap loop ended, MSGDEF_LIMIT_FAST

Explanation The wrap diagnostics have ended because the other adapter is active.

Recommended Action Remove the wrap plug and connect the interface to a channel if you wish to use this adapter. Otherwise, no action is required.

Table of Contents