Operator Messages Manual
Chapter 32 ENVOY Messages
The messages in this chapter are sent by the ENVOY subsystem.
The subsystem ID displayed by these messages includes ENVOY 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,%cntlr,%unit) CPU changed from cpu1 to cpu2 because cause | Cause The primary I/O process has received an operator request, such
as a Peripheral Utility Program (PUP) PRIMARY, and it has successfully
executed the request, or it has detected an execute I/O (EIO) error.
Controller ownership has been given to the backup process. This message
also displays when an I/O process starts up. Effect The I/O process has switched to its backup processor. Recovery If the cause of the processor switch was not the result of an
operator request, contact your HP 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,%cntlr,%unit) STATE changed
from obj state to obj state because cause | Cause The I/O process has received an operator request that has resulted
in a state change. The following operator requests may result in a
state change: Tandem Maintenance and Diagnostic System (TMDS) ABORT/DIAG/START/STOP Peripheral Utility Program (PUP) UP/DOWN
Effect The I/O process has changed to the indicated state. Recovery Informational message only; no corrective action is needed. |
| -10003 Controller Powered On. Device: \system.line name | Cause An I/O power-on interrupt was detected. Effect The I/O process executes its I/O power-on interrupt processing
logic. Recovery Informational message only; no corrective action is needed. |
| 3 Line-name LDEV ldev STATE changed from STARTED to STOPPED because OPERATOR REQUESTED
LDEV ldev DOWN | Cause An operator request or a hardware problem. ldev is the logical device name. Effect The IOP went into a down state. Recovery Start the device again. |
| 4 Line-name LDEV ldevSTATE changed from STOPPED to STARTED because OPERATOR REQUESTED
LDEV ldevUP | Cause The IOP went into an UP state because of an operator request. ldev is the logical device name. Effect None. Recovery Not applicable. |
| 5 LDEV ldev I/O ADDR
(cpu,concname,clipnum,linenum) I/O Process Abend Cause cause Program
counter %program counter error-dependent
text string | Cause The I/O process has abended because of an error condition detected,
as defined by the cause code. ldev is the
logical device name. concname is the SWAN
concentrator name the I/O process is using. clipnum is the number of the CLIP that the I/O process is using. program counter indicates the location where the internal
error occurred. linenum is the WAN line
being used by the I/O process. Effect The I/O process abends. Recovery Check the ServerNet Communications Configuration
and Management Manual and recreate the line. |
| 6 LDEV ldev I/O ADDR
(cpu,chan,%cntlr,%unit) Process Internal
Error #file error Cause cause Program Counter %program counter error-dependent text
string | Cause The I/O process detected an error on one of the following operations
or conditions: Required dedicated buffer not available
Effect The current request is aborted with an error. Recovery Collect the EMS messages from the EMS log. Contact your HP 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. |
| 7 Line-name LDEV ldevStatistics Cause: Cause Threshold thresholdTime Sent time date Last Reset time date Msgs
Sent n Msgs Rcvd n Blks High Cnt nNaks Rcvd n Bcc Errors n Format
Errors nText Errors n Retries n No Blks n | Cause Communications line errors have exceeded the designated threshold
value or the line was closed and the non-zero device statistics were
recorded. ldev is the logical device name. cause is the message text for the cause. threshold is the line-variable modifier that specifies
the value at which error statistics are generated. Effect None. Recovery Not applicable. |
| 8 Line-name LDEV ldevStatistics Cause: CauseThreshold thresholdTime Sent time date Last Reset time date Msgs
Sent n Msgs Rcvd n Blks High Cnt nNaks Rcvd n Bcc Errors n Format
Errors nText Errors n Retries n No Blks n | Cause Communications line errors have exceeded the designated threshold
value or the line was closed and the non-zero device statistics were
recorded. ldev is the logical device name. cause is the message text for the cause. threshold is the line-variable modifier that specifies
the value at which error statistics are generated. Effect None. Recovery Not applicable. |
| 9 Line-name LDEV ldevSTATE changed from STARTED to STOPPED because of HARDWARE OR LOW
LEVEL SOFTWARE PROBLEM LDEV ldev DOWN | Cause The primary I/O process has received an operator-initiated request
whose successful execution resulted in a state change. ldev is the logical device name. Effect State of the device changed. Recovery Not applicable. |
| 10 Line-name LDEV ldevCPU changed from m to nbecause TAKEN OVER BY PRIMARY | Cause The primary I/O PROCESS has received an operator-initiated request
to switch CPUs and has successfully executed the request or has detected
an EIO error and ownership has been given to the backup process. ldev is the logical device name. The following operator-initiated
request may result in a CPU switch: Effect The I/O PROCESS has switched to its backup CPU. Recovery If the cause of the CPU switch was not the result of an operator
request, report it to your HP representative. |
| 11 IOPON interrupt | Cause An I/O power-on interrupt was detected. Effect The I/O process executes its I/O power-on processing logic. Recovery Not applicable. |
| 13 LDEV ldev, LINE line name | | ldev | specifies the logical device name. |
Cause The line status has changed to the SUSPENDED state because the
path is down. Effect Disruption in the data transfer occurs. Recovery Bring up the path. |
| 1000 LDEV ldev Unknown
Event unknown event Program Counter %program counter Param(s) = %param1 %param2 %param3 | Cause The system requested the generation of an event unknown to the
process. Effect None. Recovery Contact your HP 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. |
| 1001 LDEV ldev I/O ADDR
(cpu,concname,clipnum,linenum) Bad EIO Status # file system error Driver Request request EIO Command %Lac Parameter %Lprm Device
Status Device status Channel Status CLIP status Residue residue | Cause An EIO error was detected. File-system error numbers must be
in the range 200 through 231: 200: TLAM Ownership in other CPU 210: IOP ownership aborted 222: Read/Write already pends 223: Socket error reported in EMS 230: CPU power on occurred 231: Socket lost because of concentrator power on.
ldev is the logical device name. concname is the SWAN concentrator name the I/O process
is using. clipnum is the number of the
CLIP that the I/O process is using. program counter indicates the location where the internal error occurred. linenum is WAN line being used by the I/O process. Effect After the error occurs, a CPU switch may occur. (The primary
I/O PROCESS gives ownership to the backup process.) Recovery 1. Collect the EMS messages from the EMS log.
2. Look for any particular errors, such as BADEIOSTATUS.
3. Call your HP representative. |
| 1002 LDEV ldev I/O ADDR
(cpu,concname,clipnum,linenum) Bad Interrupt Status # file system error Driver Request request Interrupt Cause
(%Ric) Interrupt Status (%Rist) Residue residue | Cause An EIO error was detected in the range 200 through 231: 200: TLAM Ownership in other CPU 210: IOP ownership aborted 222: Read/Write already pending 223: Socket error reported in EMS 230: CPU power on occurred 231: Socket lost because of concentrator power on.
ldev is the logical device name. concname is the SWAN concentrator name the I/O process
is using. clipnum is the number of the
CLIP that the I/O process is using. program counter indicates the location where the internal error occurred. linenum is WAN line being used by the I/O process. Effect A CPU switch may occur. (The primary I/O PROCESS gives
ownership to the backup process.) Recovery 1. Collect the EMS messages from the EMS log.
2. Call your HP representative. |
| 1003 LDEV ldev I/O ADDR
(cpu,concname,clipnum,linenum) Bad Interrupt Cause # file-system-error Driver Request request Received RIC Interrupt cause Expected RIC Interrupt
cause Residue residue (Byte-Synchronous
Controllers) or I/O ADDR (cpu,chan,%cntlr,%unit) Bad Interrupt Cause # file-system-error Controller Type Controller Type Driver
Request request Received RIC Interrupt cause Expected Data RIC Interrupt
cause Modem RIC Interrupt cause Residue residue (Asynchronous Controllers) | Cause A communications line error (such as loss of modem signals)
was detected. ldev is the logical device
name. concname is the SWAN concentrator
name the I/O process is using. clipnum is
the number of the CLIP that the I/O process is using. program counter indicates the location where the internal
error occurred. linenum is the WAN line
being used by the I/O process. Effect Disruption in data transfer. Recovery Not applicable. |
| 1004 LDEV ldev I/O ADDR
(cpu,concname,clipnum,linenum) Statistics Cause cause Threshold Threshold Time Sent time date Last Reset time date Msgs Sent n Msgs Rcvd n Blks High
Cnt n Naks Rcvd n Bcc Errors n Format Errors n Text Errors n Retries n No Blks n | Cause Communications line errors have exceeded the designated threshold
value (or were closed, and non-zero device statistics were recorded). | ldev | is the logical device name. | | concname | is the SWAN concentrator name the I/O process is using. | | clipnum | is the number of the CLIP that the I/O process is
using. | | program counter | indicates the location where the internal error occurred. | | linenum | is WAN line being used by the I/O process. |
Effect None. Recovery Not applicable. |
| 1005 Line-name LDEV ldevTrace Start ENVOY Trace Types: typeIOPRM
Trace Types: typeDLC Trace Types: typeStatus: status Line-name
LDEV ldevTrace Start Status status | Cause The START, MODIFY, and STOP values are returned when you enter
the Trace command. If an error occurred during the trace, the ERROR
value is returned. ldev is the logical
device name. Effect None. Recovery Not applicable. |
| 1006 LDEV ldev Configuration
Parameter Modified Parameter parameter Old Value n New Value n | Cause You used incorrect values to configure the line, then modified
the values, or you neither defined the value nor assigned a default. ldev is the logical device name. Effect None. Recovery Not applicable. |
| 1009 Line-name LDEV ldev I/O Process Warning: warning-code warning-message | Cause The I/O process detected a non-fatal error. ldev is the logical device name. Effect None. Recovery Not applicable. |
| 1010 Line-name LDEV ldev Process launch Error # file-system-error error-detail | | file-system-error | indicates the error returned in creating the backup
process. | | error-detail | is a description of the error number. |
Cause The primary IOP was unable to create a backup. The primary
IOP automatically retries the backup creation following a time-out. Effect The IOP will not have a backup process. Recovery None. |
| 1011 ACTIVATE PATH REQUEST status ON PATH path FROM CPU n | | status | indicates whether the IOP has successfully issued
an activate path request. | | path | indicates the path requested by IOP while the request
has been issued. | | n | indicates the primary CPU of the IOP. |
Cause The IOP tried to issue an activate path request. Effect None. Recovery Not applicable. |
|