Operator Messages Manual
Chapter 123 TR3271 Messages
The messages in this chapter are sent by the TR3271 subsystem.
The subsystem ID displayed by these messages includes TR3271 as the
subsystem name. | | | |  | NOTE: Negative-numbered messages are common to most subsystems. If
you receive a negative-numbered message that is not described in this
chapter, see Chapter 15. | | | | |
| -1 LDEV ldev I/O ADDR
(cpu,chan,%ctlr,%unit) line-name CPU SWITCHED FROM cpu1 TO cpu2 { OPERATOR REQUESTED | HARDWARE
OR LOW LEVEL SOFTWARE PROBLEM | TAKEN OVER BY PRIMARY } | | ldev | identifies the logical device (LDEV). | | (cpu, chan, %ctlr, %unit) | indicates the input/output (I/O) path associated with
this message. | | line-name | identifies the line on which the error has occurred. |
Cause The I/O process has received a SWITCH CPU request from Distributed
Systems Management (DSM), or it has detected a problem causing the
switch. Effect The I/O process switches to its backup processor. Recovery No action is necessary if the switch is due to a request. Otherwise,
contact your HP support representative and provide all relevant information
as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a processor dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
| -2 LDEV ldev I/O ADDR
(cpu,chan,%ctlr,%unit) line-name PATH SWITCHED FROM { A | B | UNDEFINED }
TO { A | B | UNDEFINED } { OPERATOR REQUESTED | HARDWARE OR LOW LEVEL
SOFTWARE PROBLEM | TAKEN OVER BY PRIMARY } | | ldev | identifies the logical device (LDEV). | | (cpu, chan, %ctlr, %unit) | indicates the input/output (I/O) path associated with
this message. | | line-name | identifies the line on which the error has occurred. |
Cause The I/O process has received a SWITCH PATH request from Distributed
Systems Management (DSM) or has detected a problem causing it to switch. Effect The I/O process switches to the other communications interface
unit (CIU) path. Recovery No action is necessary if the switch is due to a request. Otherwise,
contact your HP support representative and provide all relevant information
as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a processor dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
| -3 LDEV ldev I/O ADDR
(cpu,chan,%ctlr,%unit) line-name STATE SWITCHED FROM { STARTED | STOPPED }
TO { STARTED | STOPPED } { OPERATOR REQUESTED | HARDWARE OR LOW LEVEL
SOFTWARE PROBLEM | UNKNOWN REASON } | | ldev | identifies the logical device (LDEV). | | (cpu, chan, %ctlr, %unit) | indicates the input/output (I/O) path associated with
this message. | | line-name | identifies the line on which the error has occurred. |
Cause The I/O process has received a state change request from Distributed
Systems Management (DSM) (for example START or STOP), or it has detected
a problem causing the state to change. Effect The I/O process changes state. Recovery No action is necessary if the change is due to a request. Otherwise,
contact your HP support representative and provide all relevant information
as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a processor dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
| 3 LDEV ldev I/O ADDR
(cpu,chan,%ctlr,%unit) line-name I/O BUS ERROR #errnum | | ldev | identifies the logical device (LDEV). | | (cpu, chan, %ctlr, %unit) | indicates the input/output (I/O) path associated with
this message. | | line-name | identifies the line on which the error has occurred. | | #errnum | identifies a file-system error. The value of #errnum must be in the range 214 through 229. For more
information, see Table 123-1 for #errnum values. Table 123-1 errnum Values for TR3271 Message
3 | errnum | Meaning |
|---|
| 214 | Channel timeout | | 215 | I/O attempted to absent memory page | | 216 | Memory breakpoint encountered | | 217 | Memory parity error | | 218 | Interrupt timeout | | 219 | Illegal device reconnect | | 220 | Protect violation | | 221 | Controller handshake violation | | 222 | Bad channel status from EIO instruction | | 223 | Bad channel status from IIO instruction | | 224 | Controller error | | 225 | No unit, or multiple units assigned |
|
Cause An I/O-bus error has occurred during a data transfer with the
indicated line. Effect The TR3271 subsystem switches to the backup process and abnormally
terminates all requests. Note that the backup process does not retry
the operation once the switch has occurred. Recovery Contact your HP support representative and provide all relevant
information as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a processor dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. See Appendix B,
for a definition of the specified error. For more detailed information
including recovery actions, see the Guardian Procedure
Errors and Messages Manual. |
| 4 LDEV ldev I/O ADDR
(cpu,chan,%ctlr,%unit) line-name ERROR %ciu-status | | ldev | identifies the logical device (LDEV). | | (cpu, chan, %ctlr, %unit) | indicates the input/output (I/O) path associated with
this message. | | line-name | identifies the line on which the error has occurred. | | %ciu-status | indicates status information for the communications
interface unit (CIU). For a TR3271 communications line, this information
is the status word returned by the controller, in the format described
in Table 123-2. For the CIU, the
bits of the status word that are equal to 1 are interpreted in Table 123-2. Table 123-2 ciu-status Values for TR3271 Message
4 | Bit | Meaning |
|---|
| <0> | Power on (unit 0) | | | <1> | Channel underrun (write unit) | | | | Channel overrun (read unit) | | | <2> | Channel abort | | | <3> | CIU detected channel parity error | | | <4:7> | Unused, should never be used | | | <8> | CIU internal hardware error detected | | | <9> | CIU internal microprogram error detected | | | <10> | Unused, should never be used | | | <11:15> | % 0 | No data complete
(no error) | | | % 1 | Data transfer complete
(no error) | | | % 2 | Write ended and data
not sent (retry) | | | % 3 | CLB underrun (retry) | | | % 4 | Invalid CLB frame A field
(ABORT) | | | % 5 | CLB frame less than two
bytes long (ABORT) | | | % 6 | Invalid CLB frame C field
(ABORT) | | | % 7 | FCS error on incoming
CLB frame (param retry) | | | %10 | CLB received and aborted
frame (param retry) | | | %11 | CLB receiver underrun
(param retry) | | | %12 | Incoming CLB bits not
modulo 256 (param retry) | | | %13 | CLB output wait-for-acknowledgment
(WACK) timeout (param retry) | | | %14 | CLB input enable WACK
timeout (OUTPUT) | | | %15 | FLAK timeout (clear retry) | | | %16 | CLIP/BOB protocol violation
(clear retry) | | | %17 | Reserved—should
not happen (clear retry) | | | %20 | LOCS address out of range
(ABORT) | | | %21 | LOCS block exceeds end
of RAM (ABORT) | | | %22 | LOCS block sizes do not
match (ABORT) | | | %23 | LOCS block invalid format
(ABORT) | | | %24 | LOCS block bad checksum
(ABORT) | | | %25 | Execution address invalid
(ABORT) | | | %26 | Start execution issued
and CIU not loaded (ABORT) | | | %27 | Invalid EIO command (ABORT) | | | %30 | Invalid EIO parameter
word (ABORT) | | | %31 | Invalid EIO command for
unit used (ABORT) | | | %32 | Invalid NVRAM program
(ABORT) | | | %33-%37 | Reserved—should
not happen (ABORT) |
|
Cause An error occurred on the indicated TR3271 line and the I/O retry
did not succeed. Effect Another path or processor is tried. If a path or processor is
not available, the line goes down. Recovery The information given by the value %ciu-status usually indicates a hardware problem. Contact your HP support representative
and provide all relevant information as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a processor dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
| 6 LDEV ldev line-name UP | | ldev | identifies the logical device (LDEV). | | line-name | identifies the line on which the error has occurred. |
Cause The TR3271 line has been brought up successfully. The line can
be brought up programmatically using the START command or interactively
using the Subsystem Control Facility (SCF) or the Communications Management
Interface (CMI) START LINE command. Effect The operation is finished. Recovery Informational message only; no corrective action is needed. |
| 7 LDEV ldev (cpu,chan,%ctlr,%unit) line-name DOWN | | ldev | identifies the logical device (LDEV). | | (cpu, chan, %ctlr, %unit) | indicates the input/output (I/O) path associated with
this message. | | line-name | identifies the line on which the error has occurred. |
Cause The TR3271 line has been brought down programmatically, using
the STOP or ABORT command, or interactively, using the Subsystem Control
Facility (SCF) or the Communications Management Interface (CMI) STOP
or ABORT command. The TR3271 subsystem may also have brought down
the line because of errors. Effect All activity on the line stops. Recovery If this error was not caused by a command, contact your HP support
representative and provide all relevant information as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a processor dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
| 67 LDEV ldev line-name SUBDEV #dev Error
#errnum | | ldev | identifies the logical device (LDEV). | | line-name | identifies the line on which the error has occurred. | | #dev | identifies the subdevice. | | #errnum | identifies a file-system error. |
Cause An operation or a request to the indicated TR3271 subdevice
is incorrect. Effect The effect depends on the file-system error that has occurred. Recovery Appropriate recovery action depends on the file-system error
that has occurred. See Appendix B, for a definition of the specified error.
For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. If you
cannot recover from the error, bring down the subdevice. |
| 74 LDEV ldev I/O ADDR
(cpu,chan,%ctlr,%unit) line-name PROCESS INTERNAL ERROR P = %nnnnnn, E = %nnnnnn X1-X4
%param1 %param2 %param3 %param4 | | ldev | identifies the logical device (LDEV). | | (cpu, chan, %ctlr, %unit) | indicates the input/output (I/O) path associated with
this message. | | line-name | identifies the line on which the error has occurred. | | P = %nnnnnn | is the program counter register. | | E = %nnnnnn | is the environment register. | | %param1 %param2 %param3 %param4 | the values of parameters %param1 through %param4, are defined in Table 123-3. |
Cause An error has occurred at code location %param1...param4. Effect The application requests are aborted and TR3271 recovers, if
possible. Recovery If the TR3271 subsystem can recover from the internal error,
you can continue to run. Otherwise, report this and other related
error messages to your HP support representative and provide all relevant
information as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a processor dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. Table 123-3 param Values for TR3271 Message
74 | param1 | Meaning |
|---|
| %1001 | CLIP error: Buffer in use (Error originated
in level 2) | | | %1002 | CLIP error: Undefined function (Error
originated in level 3) | | | | param2: | CLIP function modifier | | %1003 | CLB error: Timeout (Error originated
in level 2) | | | | param2: | State | | | param3: | Event | | %1004 | Level 3 Error: Subdevice send or close
queue (Error originated in helper procedures) | | | | param2: | ID that indicates where this message originated | | | | %004001-%4003 in PROC QUEUE^SDCB | | | | %004401-%4405 in PROC DEQUEUE^SDCB | | | | %4701 in PROC PROC^QUEUE^SDCB^TOP | | | | %005001-%5003 in PROC QUEUE^CLOSE^SDCB | | | | %005401-%5405 in PROC DEQUEUE^CLOSE^SDCB | | | param3: | SDN to be queued/dequeued | | %1004 | param4 | Problem SDN in queue | | %1005 | Level 3 Error: Checkpoint (Error originated
in level 3) | | | | param2: | Subdevice number | | %1006 | DSM Error | | | | (Error originated in level 4 DSM) | | | | param2: | CLIP function modifier | | | param3: | Level 4 subdevice number | | %1007 | CLIP statistics threshold | | | | (Error originated in level 4 DSM) | | | %1010 | DSM error: unexpected asynchronous
CLIP response. (Error originated in level 4 DSM) | | | | param2: | CLIP function modifier | | %1011 | Memory error: Required memory exceeds
limit (Error originated in level 3) | | | %1012 | Memory error: Buffer not available
for release (Error originated in level 3) | | | %1013 | Memory error: Level 3 not waiting
for buffer received (Error originated in level 2 or level 3) | | | %1014 | CLB error: Timeout when no testing
sysgened (Error originated in level 2) | | | %1015 | CLB error: Overrun (Error originated
in level 2) | | | | param2: | Count of bytes received | | | param3: | CLB blocksize in bytes | | %1016 | CLIP error: Overrun, CLIP data exceeds
read buffer size (Error originated in level 2) | | | | param2: | Count of bytes received for this message | | | param3: | Read buffer size | | %1022 | CLIP error: Format, CLIP data length
is less than minimum required (Error originated in level 3) | | | | param2: | CLIP function modifier | | %1024 | Level 4 LCB error, no data to return
for read or writeread (Error originated in FINISH^ helper procedure) | | | | param2: | Caller address of procedure that called FINISH^ | | | param3: | LCB.P1 of original request | | %1025 | Level 3 error: Driver error flag not
set while a hardware error has been reported (Error originated in
level 3) | | | %1027 | Out of case range | | | | param2: | 1 (Error originated in CAP or HELPER procedures) | | | | 2 (Error originated in driver) | | | | 3 (Error originated in level
3) | | | | 5 (Error originated in level
4 CRT) | | | | 7 (Error originated in level
4 PTP) | | | | 8 (Error originated in level
4 DSM) | | | param3: | 1 through 4, identifies the case statement within a particular
level | | %1030 | Subdevice number in the CLIP response
is out of range (Error originated in level 3) | | | | param2: | Subdevice number as found in the CLIP response |
|
| 90 LDEV ldev line-name I/O Process abend. CODE: #errcode IOPRM RETURNED ERROR CODE: #ioprm-error P =
p-reg, E = e-reg | | ldev | identifies the logical device (LDEV). | | line-name | identifies the line on which the error has occurred. | | #errcode | indicates the reason for the abend. See Table 123-4 for a list of common cause
error codes. See Table 123-5 for
a list of TR3271-specific internal error codes. | | #ioprm-error | indicates an IOPRM error value returned from the last
IOPRM call. | | #p-reg | The content of the P register in octal, in the location
of the code where event message was generated. This field will be
printed only if the abend is due to IOPRM returning an error value. | | #e-reg | The content of the Env register in octal, in the location
of the code where event message was generated. This field will be
printed only if the abend is due to IOPRM returning an error value. |
Cause Either the necessary system resources could not be allocated
to the AM3270 input/output (I/O) process, or a WAN parameter is incorrect
or inconsistent, or an IOPRM error has been encountered. Effect The I/O process stops and cannot be used. The WAN subsystem
STOP DEVICE command should be used to kill the AM3270 process. Recovery Recovery depends on the error code displayed. If #errcode is 1 through 99, see Table 123-4 for the list of common cause
codes and the appropriate recovery actions. If #errcode is above 99, see Table 123-5 for
a list of internal error codes and the appropriate recovery actions. Table 123-4 Common Cause Codes for TR3271 Messages 74 and 90 | Message 74 Code in Octal | Message 90 Code
in Decimal | Cause | Effect | Recovery |
|---|
| %1 | 1 | A failure occurred in
an attempt to allocate segment space. | TR3271 terminates. | Stop the I/O process (IOP) with the COUP and try starting it
again. If the error persists, try to redistribute the workload with
SYSGEN. If the error persists, contact your HP support representative. | | %2 | 2 | A failure occurred in
an attempt to use segment space. | TR3271 terminates. | Stop the IOP with the COUP and try starting it again. If the
error persists, try to redistribute the workload with SYSGEN. If the
error persists, contact your HP support representative. | | %3 | 3 | A failure occurred in
an attempt to deallocate segment space. | TR3271 terminates. | Stop the IOP with the COUP and try starting it again. If the
error persists, try to redistribute the workload with SYSGEN. If the
error persists, contact your HP support representative. | | %4 | 4 | A failure occurred in
an attempt to lock memory space. | TR3271 terminates. | Stop the IOP with the COUP and try starting it again. If the
error persists, try to redistribute the workload with SYSGEN. If the
error persists, contact your HP support representative. | | %5 | 5 | A failure occurred in
an attempt to allocate pool space. | TR3271 terminates. | Stop the IOP with the COUP and try starting it again. If the
error persists, try to redistribute the workload with SYSGEN. If the
error persists, contact your HP support representative. | | %6 | 6 | A failure occurred in
an attempt to obtain pool space. | TR3271 terminates. | Stop the IOP with the COUP and try starting it again. If the
error persists, try to redistribute the workload with SYSGEN. If the
error persists, contact your HP support representative. | | %7 | 7 | The number of I/O units
supplied to the I/O process (IOP) was invalid. | TR3271
terminates. | Correct the configuration with the valid
number of I/O units. If the error persists, contact your HP support
representative. | | %10 | 8 | The subsystem could
not find the logical device (LDEV) number for the Communications Subsystem
Manager (CSM). | If only message 74 displays, this is
just a warning. If both message 74 and 90 display, the subsystem terminates. | If only message 74 displays, this is just a warning, and no
corrective action is needed. If both message 74 and 90 display, CSM
has probably terminated and all lines on this path must be stopped
with the COUP STOP command. If CSM is running for this path, contact
your HP representative. | | %11 | 9 | An incorrect subdevice
type was specified. | TR3271 terminates. | If you were running either SYSGEN or the COUP, check the configuration
file, supply the correct subdevice type, and then run SYSGEN or the
COUP again. | | %12 | 10 | An incorrect device
type was specified. | TR3271 terminates. | If you were running either SYSGEN or the COUP, check the configuration
file, supply the correct subdevice type, and then run SYSGEN or the
COUP again. | | %16 | 14 | The IOP could not find
the CSM process. | The line either stays running or stops.
If the line is still running, this is just a warning. | If the line is running, message is Informational only; no corrective
action is needed. If the line is down, bring up the line using the
SCF START command. | | %17 | 15 | An IOGET procedure
call returned an error. | TR3271 freezes. | Contact your HP support representative. | | %21 | 17 | The process terminates
due to the failure of the brother process. | Both the
primary and brother processes terminate. | Determine why
the brother process terminated. Check EMS message 90 and cause code
for the brother process. Take appropriate action. | | %22 | 18 | The controller type
specified is not supported. | TR3271 terminates. | If you were running either SYSGEN or the COUP, check the configuration
file, supply the correct controller type; run SYSGEN or the COUP again. | | %23 | 19 | An attempt to copy
a named device descriptor (NDD) has failed. | TR3271 freezes. | Contact your HP support representative. | | %31 | 25 | The primary processor
failed while the backup was waiting for the initial checkpoint. | N/A | Check what happened to the primary processor.
Stop the IOP with the COUP or try starting it again with the SCF START
command. | | %32 | 26 | The primary IOP was
aborted while the backup was waiting for the initial checkpoint. | Check what happened to the primary processor. | Check what happened to the primary processor. Stop the IOP with the
COUP or try starting it again with the SCF START command. | | %34 | 28 | Error during initialization
of WAM shared driver using TCP/IP | AM3270 will be in
ABENDED state. | Use WAN subsystem STOP DEVICE command | | %35 | 29 | Error while getting
SWAN concentrator information using WAN shared driver. | AM3270 will be in ABENDED state | Use WAN subsystem STOP
DEVICE command |
Table 123-5 Internal Error Codes for TR3271 Messages 74 and 90 | Code in Octal | Code in Decimal | Meaning | Recovery |
|---|
| %1301 | 705 | The wrong interrupt
handler was specified. TR3271 uses the default interrupt handler. | Use the CMI ALTER command to change the values. | | %1303 | 707 | A physical-subchannel-address
error has occurred. (The controller address is invalid.) | Contact your HP support representative. | | %1304 | 708 | The logical device
(LDEV) address in the primary WRITE path is different from that of
the backup WRITE path. | Contact your HP support representative. | | %1305 | 709 | The memory available
is insufficient for the request. | Check the configuration
file and specify the correct value of LOCALPOOLPAGES. Then run SYSGEN/the
COUP again. | | %1306 | 710 | A failure has occurred
during an attempt to obtain local pool space for the translate table. | Contact your HP support representative. | | %1307 | 711 | A failure has occurred
during an attempt to obtain local pool space for a Distributed Systems
Management (DSM) subdevice. | Contact your HP support
representative. | | %1310 | 712 | A failure has occurred
during an attempt to allocate an extended memory segment for a DSM
subdevice. | Contact your HP support representative. | | %1311 | 713 | A failure has occurred
during an attempt to allocate pool space for a DSM subdevice. | Contact your HP support representative. |
|
| 106 LDEV ldev line-name INSUFFICIENT BUFFER SPACE ALLOCATED IN SYSGEN | | ldev | identifies the logical device (LDEV). | | line-name | identifies the line on which the error has occurred. |
Cause The dedicated buffer size for the TR3271 line handler was too
small. The line handler cannot operate properly. Effect The line handler does not accept any operations. Recovery Reconfigure the system specifying a larger buffer size with
the MAXLOCALAREA modifier. The MAXLOCALAREA modifier specifies the
largest buffer obtainable from the local pool. The default size is
2048 words. |
| 112 LDEV ldev line-name DAX: SUBDEV #dev SELECTED AND NOT OPEN/JOIN, DATA DISCARD | | ldev | identifies the logical device (LDEV). | | line-name | identifies the line on which the error has occurred. | | #dev | identifies the subdevice. |
Cause The INITSTATUS modifier was defined with a value of %177777
for the TR3271 subsystem. An INITSTATUS of %177777 causes the TR3271
subsystem to respond to SELECTs, sent from a host to subdevices that
are neither opened nor connected, with an ACK0. An ACK0 indicates
that the data from the host, which is unsolicited, is acknowledged.
However, the data is discarded because the target subunit is not ready
to receive it. Effect Data is discarded. Recovery Verify that the subdevice #dev has
not been opened or connected. If the subdevice should not be discarding
data, contact your HP support representative and provide all relevant
information as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a processor dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
| 141 LDEV ldev I/O ADDR
(cpu,chan,%ctlr,%unit) line-name CLIP DOWNLOADED | | ldev | identifies the logical device (LDEV). | | (cpu, chan, %ctlr, %unit) | indicates the input/output (I/O) path associated with
this message. | | line-name | identifies the line on which the error has occurred. |
Cause The communications line interface processor (CLIP) in the SWAN
concentrator was successfully downloaded with DLC task. Effect The operation is finished. Recovery Informational message only; no corrective action is needed. |
| 147 LDEV ldev I/O ADDR
(cpu,chan,%ctlr,%unit) line-name CIU path CSS STATUS
PROBE ERROR %probe-err | | ldev | identifies the logical device (LDEV). | | (cpu, chan, %ctlr, %unit) | indicates the input/output (I/O) path associated with
this message. | | line-name | identifies the line on which the error has occurred. | | path | identifies the primary TCP/IP path used by the AM3270
IOP. | | %probe-err | identifies a status probe error. For a list of the
possible values of %probe-err (which contains
the communications line interface processor (CLIP) status byte in
the message text), see Table 123-6. Table 123-6 probe-err Values for TR3271 Message
147 | probe-err | Meaning |
|---|
| -1 | No response—timed out | | -2 | Unexpected probe status | | 1 | CLB type—normal frame | | 2 | CLB type—first frame | | 3 | CLB type—continue | | 4 | CLB type—last frame | | 5 | CLB type—abort | | 6 | CLB type—error |
|
Cause The TR3271 received a status-probe response from the CLIP. The
probe indicates that the CLIP is in the boot state rather than the
run state. Effect The TR3271 subsystem attempts to download the CLIP again. If
it cannot download the primary path, the communications access process
(CAP) attempts to download on another path. Recovery Decode the CLIP status byte given by the value %probe-err to determine which error has occurred. If
the CLIP does not restart automatically, try to restart it manually.
Note the error, contact your HP support representative and provide
all relevant information as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a processor dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
| 157 LDEV ldev I/O ADDR
(cpu,chan,%ctlr,%unit) line-name CSS FRAME ERR CIU path ERROR = #frame-err A,C=%param1 T,S = %param2 | | ldev | identifies the logical device (LDEV). | | (cpu, chan, %ctlr, %unit) | indicates the input/output (I/O) path associated with
this message. | | line-name | identifies the line on which the error has occurred. | | path | identifies the communications interface unit (CIU)
path. | | %frame-err | indicates the reason for the error. For a list of
possible values, see Table 123-7. | | %param1 | contains the A (address) and C (control) fields in
the CAPCLIP frame received with an error. | | %param2 | contains the T (type) and S (sequence) fields of the
CLB frame in the CAPCLIP frame received with an error. Table 123-7 frame-err Values for TR3271 Message
157 | frame-err | Meaning |
|---|
| 0 | Unexpected frame | | 1 | Invalid A field (address) | | 2 | Invalid C field (control) | | 3 | Invalid T field (type) | | 4 | Invalid S field (sequence number) | | 5 | Invalid function | | 6 | Not the expected response to the command | | 7 | Type-6 error message received from CLIP | | %10 | Not the expected multiframe type received |
|
Cause An invalid frame was received. It is normal for this error to
occur when the communications line interface processor (CLIP) resets
itself. Effect Generally, the system recovers automatically. Recovery If this error did not occur during a path switch, note the values
of #frame‑err, %param1, and %param2; contact your HP support
representative; and provide all relevant information as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a processor dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
| 158 LDEV ldev I/O ADDR
(cpu,chan,%ctlr,%unit) line-name CSS
UNEXPECTED BREAKPOINT, CIU path FRAME F,M
= %param3 | | ldev | identifies the logical device (LDEV). | | (cpu, chan, %ctlr, %unit) | indicates the input/output (I/O) path associated with
this message. | | line-name | identifies the line on which the error has occurred. | | path | identifies the communications interface unit (CIU)
path. | | %param3 | contains the communications line interface processor
(CLIP) function (F) and modifier (M). |
Cause The IOP has received a CAPCLIP message from the DEBUG task.
This indicates a problem with the DLC. Effect The CLIP stops. Recovery Note the value of %param1, then contact
your HP support representative and provide all relevant information
as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a processor dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
| 160 LDEV ldev I/O ADDR
(cpu,chan,%ctlr,%unit) line-name CSS LIU CONFIGURATION ERROR, CIU path ERROR = config-err %param1 | | ldev | identifies the logical device (LDEV). | | (cpu, chan, %ctlr, %unit) | indicates the input/output (I/O) path associated with
this message. | | line-name | identifies the line on which the error has occurred. | | path | identifies the communications interface unit (CIU)
path. | | config-err | identifies a configuration error. If the value of config-err is 0, a bad configuration was sent to the
communications line interface processor (CLIP). If the value of config-err is 1, there was an unexpected CLIP response. | | %param1 | indicates the CLIP function (F) and modifier (M). |
Cause The CLIP of the 3650/6100 Communications Subsystem (CSS) has
received a line configuration different from that in the I/O process. Effect The line does not come up. Recovery Note the values of config-err and param1, then contact your HP support representative
and provide all relevant information as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a processor dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
| 164 LDEV ldev I/O ADDR
(cpu,chan,%ctlr,%unit) line-name CSS LINE ERROR CIU path F,M = %param3 Error = %param4 #param5 | | ldev | identifies the logical device (LDEV). | | (cpu, chan, %ctlr, %unit) | indicates the input/output (I/O) path associated with
this message. | | line-name | identifies the line on which the error has occurred. | | path | identifies the communications interface unit (CIU)
path. | | %param3 | indicates the communications line interface processor
(CLIP) function (F) and modifier (M). | | %param4 | indicates the CLIP status, as described in Table 123-8. | | %param5 | indicates the CLIP subdevice number. |
Cause The CLIP of the 3650/6100 Communications Subsystem (CSS) responded
to the I/O process with an invalid function modifier. Effect The line is in the stopped state. Recovery Note the values of all the parameters, then contact your HP
support representative and provide all relevant information as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a processor dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
| 165 LDEV ldev I/O ADDR
(cpu,chan,%ctlr,%unit) line-name CSS SUBDEVICE ERROR CIU path SUBDEV #param3 F,M = %param4 STATUS %param5 | | ldev | identifies the logical device (LDEV). | | (cpu, chan, %ctlr, %unit) | indicates the input/output (I/O) path associated with
this message. | | line-name | identifies the line on which the error has occurred. | | path | identifies the communications interface unit (CIU)
path. | | %param3 | indicates the subdevice number. | | %param4 | indicates the communications line interface processor
(CLIP) function (F) and modifier (M). | | %param5 | indicates the CLIP status as described in Table 123-8. |
Cause The CLIP of the 3650/6100 Communications Subsystem (CSS) has
responded to the I/O process with an invalid subdevice state. Effect The subdevice is in the stopped state. Recovery Note the values of all parameters, then contact your HP support
representative and provide all relevant information as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a processor dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. Table 123-8 CLIP Status for TR3271 Message 165 | param5 | Meaning |
|---|
| 1 | Station in use | | 2 | Subunit already defined | | 3 | Invalid station | | 4 | Subunit not defined | | 5 | Invalid subdevice | | 6 | Invalid function modifier | | 7 | Invalid request sequence | | 8 | Protocol failure | | 9 | Invalid request type (function) | | 10 | Buffer allocation failed | | 11 | Maximum NAKs received | | 12 | Wait-for-acknowledgment (WACK) received | | 13 | No response | | 14 | Modem error or loss | | 15 | BCC error | | 16 | Not used | | 17 | Not used | | 18 | Invalid response for protocol | | 19 | No buffer space in device | | 20 | Improper buffer format | | 21 | Read buffer too small | | 22 | Reset request received | | 23 | EOT received | | 24 | Unknown device status | | 25 | Line overran CLIP | | 26 | Not used | | 27 | Operation timeout | | 28 | Line not configured | | 29 | Invalid parameter | | 30 | Subunit not ready | | 31 | RVI received with status |
|
| 166 ACTIVATE PATH REQUEST status ON PATH path from CPU cpuno | | status | indicates whether the activate path request succeeded
or failed. | | path | indicates the path (A or B or NONE or UNKNOWN) on
which the activate path request is requested. | | cpuno | the IOP’s primary processor number. |
Cause If the status is failed, then IOP failed to issue activate path
request to the NonStop operating system. Effect The line will be in the stopped state. Recovery Stop and start the device/IOP. |
|