Operator Messages Manual
Chapter 89 SLSA (ServerNet LAN Systems Access) Messages
The messages in this chapter are generated by the ServerNet
LAN Systems Access (SLSA) subsystem. The subsystem ID displayed by
these messages includes SLSA 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 -00001 LAN Manager switching from cpu n to cpu n | Cause LANMAN switched to another processor. Effect The backup LANMAN process takes over. Recovery None. This is an informational event. |
| 1 000001 LAN Manager internal Error | Cause LANMAN encountered an internal error. Effect The LANMAN primary process might change to the backup process. Recovery This is a serious error. Contact your HP representative. |
| 2 000002 LAN Manager internal trap | Cause LANMAN encountered an internal error. Effect The LANMAN primary process might change to the backup process. Recovery This is a serious error. Contact your HP representative. |
| 3 000003 LAN Manager backup is up | Cause The LANMAN backup process started. Effect LANMAN is running as a NonStop process pair. Recovery None. This is an informational event. |
| 4 000004 LAN Manager backup is down | Cause The LANMAN primary process could not start the backup process.
The processor in which LANMAN is attempting to start the backup process
might not be started. Effect LANMAN is not running as a NonStop process pair. Recovery Start the processor in which LANMAN is attempting to start the
backup process. |
| 5 000005 LAN Manager create failure | Cause LANMAN could not create a backup process although the processor
in which it is attempting to start the process is up. Effect LANMAN does not run as a NonStop process pair. Recovery Switch the backup process to a different processor. For more
information on switching a manager process to another processor, see
the SCF Reference Manual for the Kernel Subsystem. |
| 6 000006 LAN Manager checkpoint failure | Cause The LANMAN primary process was unable to create a checkpoint
with the backup process. Effect The LANMAN backup process does not have current information. Recovery If this error persists, abort and restart the LANMAN process.
For more information on aborting and starting a manager process, see
the SCF Reference Manual for the Kernel Subsystem. |
| 7 000007 LAN Manager process create failure | Cause LANMAN could not create a LAN Monitor (LANMON) process. Effect A LANMON process in one of the processors is not running. Recovery Abort and restart LANMAN. For more information on aborting and
starting a manager process, see the SCF Reference Manual
for the Kernel Subsystem. |
| 4001 004001 Transient Fault: Servernet-addressable-controller
-$ZZLAN.sac-name Origin: source, Severity: level, Type: fault-code [fault-text], ErrorDetail1 [error-detail1], ErrorDetail2 [error-detail2], ErrorDetail3 [error-detail3],[ Text: custom-text ] | | sac-name | specifies the ServerNet addressable controller (SAC)
where the transient fault occurred. | | source | specifies where the transient fault originated from.
This field displays one of the following: | Unrecognized origin | | LANMON | | DIH | | QIO Subsystem | | LMLIB | | NonStop Kernel | | XIO subsystem | | Filter | | SvNet process | | SvNet interrupt | | DSM subsystem | | NSK Configuration Routine | | LAN Manager | | Service Processor |
| | level | specifies this event as informational, warning, fatal,
or unrecognized. | | fault-code | is a number associated with this particular transient
fault. If transient fault originated within the SLSA subsystem,
the event message also displays text. fault-code and associated text are described later under “Fault Numbers for Transient Fault Events”, along with associated
cause, effect, and recovery information. If the transient
fault originated outside the SLSA subsystem, the event message displays
the error code received from the other subsystem or process. | | error-detail1 | is informational and for HP analysis only. Contact
your HP representative for more information. | | error-detail2 | is informational and for HP analysis only. Contact
your HP representative for more information. | | error-detail3 | is informational and for HP analysis only. Contact
your HP representative for more information. | | fault-text | is a brief description of the cause of the transient
fault. This field only appears if fault-code is associated with the SLSA subsystem. | | custom-text | is additional text describing the reason for the
transient fault. |
Cause A SAC encountered a fault. Effect The effect depends on the fault specified by fault-code. For more information, see “Fault Numbers for Transient Fault Events”. Recovery The recovery depends on the fault specified by fault-code. For more information, see “Fault Numbers for Transient Fault Events”. |
| 4002 004002 Object available Servernet-addressable-controller
- $ZZLAN.sac-name, event number: SAC
available, reason: reason, previous
state: state, current state: state, user content: text | | sac-name | specifies the SAC that became available. | | reason | gives the reason that the SAC became available. | | state | in the previous state field, state specifies the state the SAC was in before becoming available. In
the current state field, state specifies
the state of the SAC after it became available. | | text | provides additional information about the event. |
Cause A SAC is available and the SLSA subsystem can access it. Effect The system can access the SAC. Recovery None. This is an informational event. |
| 4003 004003 Object unavailable Servernet-addressable-controller
- $ZZLAN.sac-name, event number: SAC
unavailable, cause: reason, previous
state: state, current state: state, use content: text | | sac-name | specifies the SAC that became unavailable. | | reason | gives the reason that the SAC is unavailable. | | state | in the previous state field, state specifies the state the SAC was in before becoming unavailable.
In the current state field, state specifies
the state of the SAC after it become unavailable. | | text | provides additional information about the event. |
Cause The SLSA subsystem cannot access the SAC or the physical interfaces
(PIFs) subordinate to it because the SAC was aborted, stopped, or
a failure occurred. Effect The SLSA subsystem cannot communicate with the LAN. Recovery Start the SAC or replace the adapter. |
| 4004 004004 (Other) State Change Servernet-addressable-controller
- $ZZLAN.sac-name, event number: SAC
state change, reason: reason, previous
state: state, current state: state, user content: text | | sac-name | specifies the ServerNet addressable controller (SAC)
where a state change occurred. | | reason | specifies the cause of the state change. | | state | in the previous state field, state specifies the state the SAC was in when the state change occurred.
In the current state field, state specifies
the state of the SAC after the state change occurred. | | text | provides additional text information about the state-change
event. |
Cause A SAC changed from one state to another. Effect If the SAC is in the STARTED state, the system can access the
adapter through the specified SAC; otherwise, the SAC is unavailable. Recovery If the SAC is in the STOPPED state, start the SAC. |
| 4007 004007 SAC ownership change from cpu n to cpu n | Cause The ownership of a ServerNet addressable controller (SAC) changed
from one processor to another. Effect The data path to the SAC on an Ethernet 4 ServerNet adapter
(E4SA) or the Ethernet port on the multifunction I/O board (MFIOB)
changes. Recovery Use the ALTER SAC command to reassign the ownership of the SAC
back to its original owner. |
| 4008 004008 operation: Servernet-addressable-controller - $ZZLAN.sac-name | | operation | specifies the type of operation that occurred. | | sac-name | specifies the name of the SAC on which the operation
was performed. |
Cause A user issued an SCF ALTER SAC command to change the attributes
of a SAC. Effect The configuration database is updated with the new attribute
information. Recovery None. This is an informational event. |
| 4009 004009 Owner state report: Servernet-addressable-controller
- $ZZLAN.sac-name, current state: state | | sac-name | specifies the name of the SAC that had a change of
ownership. | | state | indicates the state of the SAC after the change of
ownership. |
Cause A SAC has a new owner. Effect None. Recovery None. This is an informational event. |
| 4010 004010 Self test failure: Servernet-addressable-controller
- $ZZLAN.sac-name Test result: result-code | | sac-name | specifies the name of the SAC that failed a power-on
self-test (POST). | | result-code | is a series of eight hexadecimal numbers that indicate
the reason for the failure. |
Cause A power-on self-test (POST) failed on a SAC. Effect The system cannot start the SAC. Recovery Replace the board or firmware, and contact your HP representative. |
| 4011 004011 Servernet-addressable-controller -
$ZZLAN.sac-name dump to file-name Reason reason | | sac-name | specifies the name of the SAC that had its memory
dumped to a file. | | file-name | specifies the name of the file where the dump information
is stored. | | reason | specifies whether this dump was manual or automatic.
A manual dump indicates that the dump command was issued from the
system console. An auto dump indicates that the dump occurred as
part of a SAC failure‑recovery procedure. |
Cause A SAC dumped information to the file specified by file-name. Effect A dump file was created. Recovery None. This is an informational message. However, you might need
to submit the dump file to your HP representative if this is part
of a troubleshooting process. |
| 4012 004012 Firmware Update Servernet-addressable-controller
- $ZZLAN.sac-name Status: status [Current Revision: adapter‑revision][Firmware File Name: file-name] [and
Revision: file-revision][Reason: reason] | | sac-name | specifies the name of the SAC that had a firmware
update. | | status | specifies the status of the firmware update process.
The status can be | Initiated | | Successful Completion | | Failed | | Completion with unknown result |
Initiated indicates that the update process has started. The
other statuses indicate the result. | | adapter‑revision | specifies the revision of the firmware on the adapter
before the firmware update occurred. | | file-name | specifies the name of the file the new firmware is
stored in. | | file-revision | specifies the revision of the firmware in the file
to be downloaded onto the controller. | | reason | specifies whether this was manual or automatic update.
A manual update indicates the command was issued from the system
console. An automatic update indicates that the firmware update
occurred because the system detected a newer version of the firmware
file prior to a download of operation code to the controller. |
Cause The system updated SAC firmware from the file specified by file-name. Effect New firmware is installed on the SAC if the firmware update
was successful; otherwise, the update has no effect. Recovery None. This is an informational message. If you want to use a
different version of the firmware on the SAC, specify the appropriate
firmware file name, and perform a manual firmware update. |
| 4013 004013 Adapter Event - Servernet-addressable-controller
- $ZZLAN.sac-name Event: event-code event-text occurred count
times [ First occurrence at date time ] Last occurrence at date time { First
lost event number: event-code event-text | Severity: level, Reason: detail-code Reporting module id and Occurring module id [ Text: custom-text ] } | | sac-name | specifies the name of the SAC that had a firmware
update. | | event-code | specifies the type of adapter event that occurred.
The event codes are: | | event-text | describes the event specified by event-code. | | count | indicates the number of times the event specified
by event-code occurred. The value of count might be approximate for some event-codes. | | date | indicates the date when this event occurred. The date
is written in the form daymonthyear, for example, 17JUN97 | | time | indicates the time when this event occurred. The time
is shown in the form hours:minutes.seconds; for example, 15:13:39 | | level | indicates the severity of this event as either informative
or warning. | | detail-code | For HP use only. | | id | For HP use only. | | custom-text | specifies whether the link pulse is present or missing. |
Cause An adapter-reported event. The event code describes the cause. Effect None. These events are generally informational. Recovery None for informational events, but you may need to check the
adapter or its connections. |
| 4014 004014 Servernet-addressable-controller -
$ZZLAN.CC1.0 Type Detection: message | | message | is the message describing the event. Possible values
are: CCSA SAC Detected This message means that the SAC
was discovered. Empty CCSA SAC This message means that the requested
SAC (representing the plug-in card [PIC]) is not installed.
|
Cause For CCSA, the PIC that is the hardware correspondent of the
subordinated SAC of an ADAPTER object can be present or not present.
This is originally unknown. When the SLSA subsystem discovers the
actual availability of the PIC, it generates this event to inform
the user about the presence or absence of the PIC/SAC. Effect This is an informational event. However, if the event indicates
Empty CCSA SAC, the SAC object stays in the STARTING state unless
the SAC is aborted or the adapter is replaced. Recovery If the SAC is detected, no recovery is required. Otherwise,
check that the correct PICs are installed in the CCSA adapter. |
| 4015 004015 SAC NAME sac-name, Reason: text | | sac-name | specifies the name of the SAC which has now become
accessible. | | text | message indicating that a service request made to
a subsystem was successful. |
Cause A service request made to a subsystem was successful. Effect SAC access is established. Recovery None. |
| 4016 004016 NAME: sac-name, Reason: text1, Origin: Subsystem, Severity: level, Type Code: code, Type String: text2 | | sac-name | specifies the name of the SAC which is no longer
accessible by a CPU. | | text1 | underlying-serv-failed | | Subsystem | specifies where the transient fault originated from.
This field displays one of the following: | Unrecognized origin | | QIO subsystem | | XIO subsystem | | TNet services | | level | | specifies this event as fatal | | code | | internal error code |
| | text2 | additional error information that is returned by
subsystem. |
Cause A service request made to a subsystem failed. Effect SAC access is lost. Recovery Restart the SAC. If the problem persists inform your HP representative. |
| 4101 004101 Transient Fault: physical-interface
-$ZZLAN.pif-name Origin: source, Severity: level, Type: fault-code [fault-text],[ Text: custom-text ] | | pif-name | specifies the physical interface (PIF) where the
transient fault occurred. | | source | specifies where the transient fault originated from.
This field displays one of the following: | Unrecognized origin | | LANMON | | DIH | | QIO Subsystem | | LMLIB | | NonStop Kernel | | XIO subsystem | | Filter | | SvNet process | | SvNet interrupt | | DSM subsystem | | NSK Configuration Routine | | LAN Manager | | Service Processor |
| | level | specifies this event as informational, warning, fatal,
or unrecognized. | | fault-code | is a number associated with this particular transient
fault. If transient fault originated within the SLSA subsystem,
the event message also displays text. fault-code and associated text are described later under “Fault Numbers for Transient Fault Events”, along with associated
cause, effect, and recovery information. If the transient
fault originated outside the SLSA subsystem, the event message displays
the error code received from the other subsystem or process. | | fault-text | is a brief description of the cause of the transient
fault. This field only appears if fault-code is associated with the SLSA subsystem. | | custom-text | is additional text describing the reason for the
transient fault. |
Cause A PIF encountered a fault. Effect The effect depends on the fault specified by fault-code. For more information, see “Fault Numbers for Transient Fault Events”. Recovery The recovery depends on the fault specified by fault-code. For more information, see “Fault Numbers for Transient Fault Events”. |
| 4102 004102 Object available Physical-interface
- $ZZLAN.pif-name, event number: PIF
available, reason: reason, previous
state: state, current state: state, user content: text | | pif-name | specifies the physical interface (PIF) that became
available. | | reason | cause of the PIF-available event. | | state | in the previous state field, state specifies the state the PIF was in before the state change occurred.
In the current state field, state specifies
the state of the PIF after the state change occurred. | | text | provide additional information about the event. |
Cause A PIF became available, and the SLSA subsystem can access it. Effect The system can access the LAN through the PIF. Recovery None. This is an informational event. |
| 4103 004103 Object unavailable Physical-interface
- $ZZLAN.pif-name, event number: PIF
unavailable, cause: reason, previous
state: state, current state: state, use content: text | | pif-name | specifies the physical interface (PIF) that became
unavailable. | | reason | give the reason the PIF became unavailable. | | state | in the previous state field, state specifies the state the PIF was in before becoming unavailable.
In the current state field, state specifies
the state of the PIF when it become unavailable. | | text | provides additional information about the event. |
Cause The SLSA subsystem cannot access a PIF because the PIF was aborted
or stopped or because a failure occurred. Effect The SLSA subsystem cannot communicate with the LAN through the
PIF. Recovery Start the PIF or the SAC and the adapter it is subordinate to.
Replace the adapter if the problem was a hardware failure. |
| 4104 004104 (Other) State Change Physical-interface
- $ZZLAN.pif-name, event number: PIF
state change, reason: reason, previous
state: state, current state: state, user content: text | | pif-name | specifies the physical interface (PIF) that had a
state change. | | reason | specifies the cause of the state change. | | state | in the previous state field, state specifies the state the PIF was in before becoming unavailable.
In the current state field, state specifies
the state of the PIF when it become unavailable. | | text | provides additional text information about the state-change
event. |
Cause A physical interface (PIF) changed from one state to another. Effect If the PIF is in the STARTED state, the system can access the
LAN through the specified PIF; otherwise, the PIF is unavailable,
and the system cannot access the LAN. Recovery If the PIF is in the STOPPED state, start the PIF. |
| 4105 004105 operation: physical-interface - $ZZLAN.adapter-name.sac-unit#.pif-unit-letter | | operation | specifies the operation that occurred. | | pif-name | specifies the name of the physical interface (PIF)
on which the operation was performed. |
Cause A PIF object was altered by an SCF ALTER PIF command. Effect The attributes of the PIF have been altered. Recovery None. This is an informational event. |
| 4107 004008 operation: physical-interface - $ZZLAN. adapter- name.sac-unit#.pif-unit-letter | | operation | specifies the type of operation that occurred. | | pif-name | specifies the name of the PIF on which the operation
was performed. |
Cause A user issued an SCF ALTER PIF command to change the attributes
of a PIF. Effect The configuration database is updated with the new attribute
information. Recovery None. This is an informational event. |
| 4108 004108 PIF NAME pif-name, Reason: text | | pif-name | specifies the physical interface (PIF), which is now
accessible by a CPU. | | text | message indicating a service request made to a subsystem
was successful. |
Cause A service request made to a subsystem was successful. Effect PIF access is established. Recovery None. |
| 4109 004109 NAME:pif-name, Reason: text1, Origin: Subsystem, Severity: level, Type Code: code, Type String: text2 | | pif-name | specifies the physical interface (PIF) which is no
longer accessible by a CPU. | | text1 | underlying-serv-failed | | Subsystem | specifies where the transient fault originated from.
This field displays one of the following: | Unrecognized origin | | QIO subsystem | | XIO subsystem | | TNet services |
| | level | specifies this event as fatal. | | code | internal error code. | | text2 | additional error information that is returned by
subsystem. |
Cause A service request made to a subsystem failed. Effect PIF access is lost. Recovery Restart the PIF. If the problem persists inform your HP representative. |
| 4201 004201 Transient Fault: logical-interface
- $ZZLAN.lif-name Origin: source, Severity: level, Type: fault-code [fault‑text], [ Text: custom-text ] | | lif-name | specifies the logical interface (LIF) where the transient
fault occurred. | | source | specifies where the transient fault originated from.
This field displays one of the following: | Unrecognized origin | | LANMON | | DIH | | QIO Subsystem | | LMLIB | | NonStop Kernel | | XIO subsystem | | Filter | | SvNet process | | SvNet interrupt | | DSM subsystem | | NSK Configuration Routine | | LAN Manager | | Service Processor |
| | level | specifies this event as informational, warning, fatal,
or unrecognized. | | fault-code | is a number associated with this particular transient
fault. If transient fault originated within the SLSA subsystem,
the event message also displays text. fault-code and associated text are described later under “Fault Numbers for Transient Fault Events”, along with associated
cause, effect, and recovery information. If the transient
fault originated outside the SLSA subsystem, the event message displays
the error code received from the other subsystem or process. | | fault-text | is a brief description of the cause of the transient
fault. This field only appears if fault-code is associated with the SLSA subsystem. |
Cause A LIF encountered a fault. Effect The effect depends on the fault specified by fault-code. For more information, see “Fault Numbers for Transient Fault Events”. Recovery The recovery depends on the fault specified by fault-code. For more information, see “Fault Numbers for Transient Fault Events”. |
| 4202 004202 Object available logical-interface
- $ZZLAN.lif-name, event number: LIF
available, reason: reason, previous state: state, current state: state, user content: text | | lif-name | specifies the logical interface (LIF) that became
available. | | reason | gives the reason that the LIF became unavailable. | | state | in the previous state field, state specifies the state the LIF was in before becoming available. In
the current state field, state specifies
the state of the LIF when it become available. | | text | provides additional information about the event. |
Cause A LIF became available, and the SLSA subsystem can access it. Effect The system can access the LIF. Recovery None. This is an informational event. |
| 4203 004203 Object unavailable Logical-interface
- $ZZLAN.lif-name, event number: LIF
unavailable, cause: reason, previous
state: state, current state: state, use content: text | | lif-name | specifies the logical interface (LIF) that became
unavailable. | | reason | gives the reason that the LIF became unavailable. | | state | in the previous state field, state specifies the state the LIF was in before becoming unavailable.
In the current state field, state specifies
the state of the LIF when it become unavailable. | | text | provides additional information about the event. |
Cause The SLSA subsystem cannot access a LIF because it has been aborted
or stopped, or because a failure occurred. Effect The system cannot use the LIF. Recovery Start the LIF. |
| 4204 004204 (Other) State Change logical-interface
- $ZZLAN.lif-name, event number: LIF
state change, reason: reason, previous
state: state, current state: state, user content: text | | lif-name | specifies the logical interface (LIF) that had a state
change. | | reason | in the previous state field, state specifies the state the LIF was in before the state change. In
the current state field, state specifies
the state of the LIF when after the state change. | | state | is either the previous state of the LIF or the current
state of the LIF. | | text | provides additional text information about the state-change
event. |
Cause A logical interface (LIF) changed from one state to another. Effect If the LIF is in the STARTED state, the system can access the
LAN through the PIFs subordinate to the LIF; otherwise, the LIF is
unavailable. Recovery If the LIF is in the STOPPED state, start the LIF. |
| 4207 004207 operation: Logical-interface - $ZZLAN.lif-name | | operation | specifies the operation that occurred. | | lif-name | specifies the name of the logical interface (LIF)
on which the operation was performed. |
Cause A LIF object has been added or deleted from the SLSA system
and configuration database by an SCF ADD LIF or DELETE LIF command. Effect A new LIF object now exists for clients to use, or a LIF object
has been removed. Recovery None. This is an informational event. |
| 4208 004208 count Queue
full events during the last duration seconds
for Logical-interface - $ZZLAN.lif-name in CPU processor | | count | specifies the number of times the queue was full. | | duration | specifies the time during which the count was made. | | lif-name | specifies the name of the LIF that had a full input
queue. | | processor | specifies the processor the LIF is running in. |
Cause The client input queue is full and packets were rejected count times for duration seconds. Effect Packets are dropped for the LIF. Recovery Make sure that the client is processing the incoming packets. conditional-4303 |
| 4401 004401 Transient Fault: adapter - $ZZLAN.adapter-name Origin: source, Severity: level, Type: fault-code [fault-text], [ Text: custom-text ] | | adapter-name | specifies the ServerNet adapter where the transient
fault occurred. | | source | specifies where the transient fault originated. This
field displays one of the following: | Unrecognized origin | | LANMON | | DIH | | QIO Subsystem | | LMLIB | | NonStop Kernel | | XIO subsystem | | Filter | | SvNet process | | SvNet interrupt | | DSM subsystem | | NSK Configuration Routine | | LAN Manager | | Service Processor |
| | level | specifies this event as informational, warning, fatal,
or unrecognized. | | fault-code | is a number associated with this particular transient
fault. If the transient fault originated within the SLSA subsystem,
the event message also displays text. fault-code and associated text are described later under “Fault Numbers for Transient Fault Events”, along with associated
cause, effect, and recovery information. If the transient
fault originated outside the SLSA subsystem, the event message displays
the error code received from the other subsystem or process. | | fault-text | is a brief description of the cause of the transient
fault. This field only appears if fault-code is associated with the SLSA subsystem. | | custom-text | is additional text describing the reason for the
transient fault. |
Cause An adapter encountered a fault. Effect The effect depends on the fault specified by fault-code. For more information, see “Fault Numbers for Transient Fault Events”. Recovery The recovery depends on the fault specified by fault-code. For more information, see “Fault Numbers for Transient Fault Events”. |
| 4402 004402 Object available Adapter - $ZZLAN.adapter-name, event number: Adapter available, reason: reason, previous state: state, current state: state, user content:
text | | adapter-name | specifies the adapter that became available. | | reason | gives the reason that the adapter became available. | | state | in the previous state field, state specifies the state the adapter was in before becoming available.
In the current state field, state specifies
the state of the adapter when it become available. | | text | provide additional information about the event. |
Cause An adapter became available, and the SLSA subsystem can use
it. Effect The system can access the adapter. Recovery None. This is an informational event. |
| 4403 004403 Object unavailable Adapter - $ZZLAN.adapter-name, event number: Adapter unavailable,
cause: reason, previous state: state, current state: state, use content: text | | adapter-name | specifies the adapter that became unavailable. | | reason | gives the reason that the adapter became unavailable. | | state | in the previous state field, state specifies the state the adapter was in before becoming unavailable.
In the current state field, state specifies
the state of the adapter when it become unavailable. | | text | is a string providing additional text information
about the filter-unavailable event. |
Cause The adapter was been aborted or stopped, or a fault occurred. Effect The system cannot access the LAN through the adapter. Recovery Start the adapter, replace it, or reload the firmware. |
| 4404 004404 (Other) State Change Adapter - $ZZLAN.adapter-name, event number: Adapter state change,
reason: reason, previous state: state, current state: state, user content: text | | adapter-name | specifies the adapter that had a state change. | | reason | specifies the cause of the state change. | | state | in the previous state field, state specifies the state the adapter was in before becoming available.
In the current state field, state specifies
the state of the adapter after the state change. | | text | provides additional information about the event. |
Cause An adapter changed from one state to another. Effect If the adapter is in the STARTED state, the system can access
the adapter; otherwise, the adapter is unavailable. Recovery If the adapter is in the STOPPED state, start the adapter. |
| 4407 004407 operation: Adapter - $ZZLAN.adapter-name | | operation | specifies the type of operation that occurred. | | adapter-name | specifies the name of the adapter on which the operation
was performed. |
Cause An ADAPTER object and its subordinated objects have been added
or deleted from the SLSA system and configuration database by an SCF
ADD ADAPTER or DELETE ADAPTER command. Effect An adapter and its subordinate objects are available to the
SLSA subsystem, or the object is no longer in the SLSA system and
configuration database. Recovery None. This is an informational event. |
| 4501 004501 Transient Fault: process - $ZZLAN Origin: source, Severity: level, Type: fault-code [fault-text], [ Text: custom-text ] | | source | specifies where the transient fault originated from.
This field displays one of the following: | Unrecognized origin | | LANMON | | DIH | | QIO Subsystem | | LMLIB | | NonStop Kernel | | XIO subsystem | | Filter | | SvNet process | | SvNet interrupt | | DSM subsystem | | NSK Configuration Routine | | LAN Manager | | Service Processor |
| | level | specifies this event as informational, warning, fatal,
or unrecognized. | | fault-code | is a number associated with this particular transient
fault. If the transient fault originated within the SLSA subsystem,
the event message also displays text. fault-code and associated text are described later under “Fault Numbers for Transient Fault Events”, along with associated
cause, effect, and recovery information. If the transient
fault originated outside the SLSA subsystem, the event message displays
the error code received from the other subsystem or process. | | fault-text | is a brief description of the cause of the transient
fault. This field only appears if fault-code is associated with the SLSA subsystem. | | custom-text | is additional text describing the reason for the
transient fault. |
Cause The LANMAN encountered a fault. Effect The effect depends on the fault specified by fault-code. For more information, see “Fault Numbers for Transient Fault Events”. Recovery The recovery depends on the fault specified by fault-code. For more information, see “Fault Numbers for Transient Fault Events”. |
| 4502 004502 Object available Process - $ZZLAN,
event number: Process available, reason: reason, previous state: state, current state:
state, user content: text | | reason | cause of the process-available event. | | state | in the previous state field, state specifies the state the process was in before becoming available.
In the current state field, state specifies
the state of the process when it become available. | | text | provides additional information about the event. |
Cause The LANMAN process is running. Effect Other subsystems can use the SLSA subsystem to access the LAN. Recovery None. This is an informational event. |
| 4503 004503 Object unavailable Process - $ZZLAN,
event number: Process unavailable, cause: reason, previous state: state, current state:
state, use content: text | | reason | specifies the reason that the process became unavailable. | | state | in the previous state field, state specifies the state the process was in before becoming unavailable.
In the current state field, state specifies
the state of the process when it become unavailable. | | text | provides additional information about the event. |
Cause This event is likely to happen if LANMAN and QIOMON are incompatible. Effect LANMAN fails to either attach to the QIO segment or create the
QIO module ID and LANMAN stops itself. Recovery Install compatible versions of LANMAN and QIO and cold load
the system. |
| 4504 004504 (Other) State Change Process - $ZZLAN,
event number: Process state change, reason: reason, previous state: state, current state:
state, user content: text | | reason | specifies the cause of the state change. | | state | in the previous state field, state specifies the state the process was in before becoming unavailable.
In the current state field, state specifies
the state of the process when it become unavailable. | | text | provides additional information about the event. |
Cause A LANMAN process changed from one state to another. Effect None. Recovery None. This is an informational event. |
| 4507 004507 LAN Manager terminated due to bad
process name | Cause The LANMAN process started with a process name other than $ZZLAN,
which is the required name. Effect LANMAN stops. Recovery Reconfigure the system to start LANMAN with the process name
$ZZLAN. |
| 4508 004508 LAN Manager terminated because processor does not have system disk running | |
| 4601 004601 Transient Fault: process - $ZZLAN.monitor-name Origin: source, Severity: level, Type: fault-code [fault-text], [ Text: custom-text ][ , Manager:
manager-name] | | monitor-name | specifies the SLSA monitor process that had a transient
fault. | | source | specifies where the transient fault originated. This
field displays one of the following: | Unrecognized origin | | LANMON | | DIH | | QIO Subsystem | | LMLIB | | NonStop Kernel | | XIO subsystem | | Filter | | SvNet process | | SvNet interrupt | | DSM subsystem | | NSK Configuration Routine | | LAN Manager | | Service Processor |
| | level | specifies this event as informational, warning, fatal,
or unrecognized. | | fault-code | is a number associated with this particular transient
fault. If the transient fault originated within the SLSA subsystem,
the event message also displays text. fault-code and associated text are described later under “Fault Numbers for Transient Fault Events”, along with associated
cause, effect, and recovery information. If the transient
fault originated outside the SLSA subsystem, the event message displays
the error code received from the other subsystem or process. | | fault-text | is a brief description of the cause of the transient
fault. This field only appears if fault-code is associated with the SLSA subsystem. | | custom-text | is additional text describing the reason for the
transient fault. | | manager-name | specifies the name of the parent LANMAN for the LANMON. |
Cause A LANMON encountered a fault. Effect The effect depends on the fault specified by fault-code. For more information, see “Fault Numbers for Transient Fault Events”. Recovery The recovery depends on the fault specified by fault-code. For more information, see “Fault Numbers for Transient Fault Events”. |
| 4602 004602 Object available Monitor - $ZZLAN.monitor-name, event number: process available, reason: reason, previous state: state, current state: state, user content:
text | | monitor-name | specifies the LANMON that became available. | | reason | specifies the reason the LANMON process became available. | | state | in the previous state field, state specifies the state the monitor was in before becoming available.
In the current state field, state specifies
the state of the monitor when it become available. | | text | provides additional information about the event. |
Cause A monitor became available and the SLSA subsystem can use it. Effect The LANMAN process can use the monitor. Recovery None. This is an informational event. |
| 4603 004603 Object unavailable Monitor - $ZZLAN.monitor-name, event number: Monitor unavailable,
cause: reason, previous state: state, current state: state, use content: text | | monitor-name | specifies the LANMON process that became unavailable. | | reason | specifies the reason the LANMON process became unavailable. | | state | in the previous state field, state specifies the state the LANMON was in before becoming unavailable.
In the current state field, state specifies
the state of the LANMON when it become unavailable. | | text | provides additional information about the event. |
Cause The LANMON process has been aborted or stopped, or a fault has
occurred. Effect There is a loss of service to SLSA from the processor that the
LANMON process was running in. Recovery Reload the processor. |
| 4604 004604 (Other) State Change Monitor - $ZZLAN.monitor-name, event number: Monitor state change,
reason: reason, previous state: state, current state: state, user content: text | | monitor-name | specifies the LANMON process that had a state change. | | reason | specifies the reason LANMON had a state change. | | state | is either the previous state of the LANMON or the
current state of the LANMON. | | text | provides additional information about the state-change
event. |
Cause A LANMON process changed from one state to another. Effect None. Recovery None. This is an informational event. |
| 4607 004607 Resource Unavailable Monitor - monitor-name count resource shortage reports for resource of type resource [text] | | monitor-name | specifies the name of the LANMON process that has
a resource shortage. | | count | the number of resource allocation failures since the
last report. | | resource | indicates the type of resource that cannot be allocated;
for example, Memory Heap, QIO Pool, or QIO Space. | | text | provides additional information about the failure
of resource allocations. |
Cause Failures encountered during resource allocation. Effect The LANMON cannot obtain resources, which can lead to termination
of the specified LANMON. Recovery Find out why resources are not available, and fix the problem
if possible. |
| 4701 004701 LANMON-info: Monitor - monitor-name, Text: text | | monitor-name | specifies the LANMON process that generated this
event. | | text | provides additional information about this event. |
Cause A LANMON process started up and is reporting start-up, VPROC,
and status information. Effect None. Recovery None. This is an informational event. |
| 4702 004702 LAN Manager-info: Process - process-name, Text: text | | process-name | specifies that the LANMAN process that generated this
event. | | text | provides additional information about this event. |
Cause LANMAN started up and is using this event to report its VPROC. Effect None. Recovery None. This is an informational event. |
| 4703 004703 SLSA Internal Report object-type - object-name Unrecoverable fault -
process terminated, Origin:source,
Severity level, Type: fault-code [fault-text], Detected at line line-number in file source-filename [, Text: custom-text] | | object-type | specifies type of object that encountered the problem.
Currently, Monitor is the only type. | | object-name | specifies the name of the object that encountered
the problem. | | source | specifies where the transient fault originated from.
This field displays one of the following: | Unrecognized origin | | LANMON | | DIH | | QIO Subsystem | | LMLIB | | NonStop Kernel | | XIO subsystem | | Filter | | SvNet process | | SvNet interrupt | | DSM subsystem | | NSK Configuration Routine | | LAN Manager | | Service Processor |
| | level | specifies this event as fatal. | | fault-code | is a number associated with this particular transient
fault. If transient fault originated within the SLSA subsystem,
the event message also displays text. fault-code and associated text are described later under “Fault Numbers for Transient Fault Events”, along with associated
cause, effect, and recovery information. If the transient
fault originated outside the SLSA subsystem, the event message displays
the error code received from the other subsystem or process. | | fault-text | is a brief description of the cause of the transient
fault. This field only appears if fault-code is associated with the SLSA subsystem. | | line-number | specifies the line of code in which this fatal fault
is encountered. | | source-filename | specifies the name of the source file in which this
fatal fault is encountered. | | custom-text | is additional information describing the reason for
the transient fault. |
Cause A component of the SLSA subsystem encountered an unrecoverable
fault. Effect The object (usually a process) is terminated. Recovery The recovery depends on the fault specified by fault-code. For more information, see “Fault Numbers for Transient Fault Events”. Contact your
HP representative. |
| 4715 004715 ATM Adapter Event $ZZLAN.pif-name TYPE event-code event-text Severity: level First occurrence:
date time Last occurrence: date time Reporting module id Occurring module id Info1: info-code1 Info2: info-code2 Info3: info-code3 Text: custom-text | | pif-name | specifies the physical interface (PIF) of the ATM3SA
adapter which reported an event. | | event-code | specifies a numeric code associated with a specific
event which was encountered by the ATM3SA adapter. For more information
about the event-code, see “Event Code Numbers for ATM3SA Adapter Events”. | | event-text | specifies a text description of the event associated
with the event-code. For more information about the event-text, See “Event Code Numbers for ATM3SA Adapter Events”. | | level | specifies this event as informational, warning, or
fatal. | | date | indicates the date when this event occurred. The date
is written in the form daymonthyear, for example, 31AUG01. | | time | indicates the time when this event occurred. The time
is shown in the form hours:minutes:seconds, for example, 15:27:23. | | id | specifies the module identifier. For internal HP use
only. | | info-code1, info-code2,
nfo-code3 | are numbers associated with the event-code to provide
further detail about the event. The values for info-codes only appears
in event messages if the values are non-zero. For more information
on the info-code, see “Event Code Numbers for ATM3SA Adapter Events”. | | custom-text | provides additional text information about the event-code. For more information, see “Event Code Numbers for ATM3SA Adapter Events”. |
Cause The cause of this event depends directly on the event-code. For more information, see “Event Code Numbers for ATM3SA Adapter Events”. Effect The effect of this event depends directly on the event-code. For more information, see “Event Code Numbers for ATM3SA Adapter Events”. Recovery The recovery of this event depends directly on the event-code. For more information, see “Event Code Numbers for ATM3SA Adapter Events”. |
| 4871 004871 ATMSAP Transient Fault ATMSAP Name:
$ZZLAN.atmsap-name, Origin: source, Severity: level, Type Code: fault-code [ Type String:
fault-text ] [ ErrorDetail: error-code1 [ ErrorDetail2: error-code2 [ ErrorDetail3: error-code3 ]]], [
Text: custom-text ] | | atmsap-name | specifies the ATM service-access-point (SAP) where
the transient fault occurred. | | source | specifies where the transient fault originated from.
The field displays one of the following: | Unrecognized origin | | LANMON | | DIH | | QIO Subsystem | | LMLIB | | NonStop Kernel | | XIO subsystem | | Filter | | SvNet process | | SvNet interrupt | | DSM subsystem | | NSK Configuration Routine | | LAN Manager | | Service Processor |
| | level | specifies this event as informational, warning, fatal,
or unrecognized. | | fault-code | is a number associated with this particular transient
fault. If the transient fault originated within the SLSA subsystem,
the event message also displays fault-text. fault-code and fault-text are described
under along with associated cause, effect, and recovery information.
If the transient fault originated outside the SLSA subsystem, the
event message displays the error code received from the other subsystem
or process. | | fault-text | is a brief description of the cause of the transient
fault. This field only appears if fault-code is associated with the SLSA subsystem. | | error-code1, error-code2,
error-code3 | are numbers associated with the fault-code to provide details for support personnel analyzing this particular
transient fault. | | custom-text | is additional text describing the reason for the
transient fault. |
Cause An ATMSAP encountered a fault. Effect The effect depends on the fault specified by fault-code. For more information, see “Fault Numbers for Transient Fault Events”. Recovery The recovery depends on the fault specified by fault-code. For more information, see “Fault Numbers for Transient Fault Events” |
| 4872 004872 ATMSAP Available ATMSAP Name: $ZZLAN.atmsap-name, Event Number: ATMSAP Available, Reason: reason, Previous State: state, Current State: state [ User Content:
text ] | | atmsap-name | specifies the ATM service-access-point (SAP) that
became available. | | reason | cause of the ATMSAP-available event. | | state | in the previous state field, state specifies the state that the ATMSAP was in before becoming available.
In the current state field, state specifies
the state of the ATMSAP when it became available. | | text | provides additional information about the event. |
Cause An ATMSAP became available, and the SLSA subsystem can access
it. Effect The system can access the ATM network through the ATMSAP. Recovery None. This is an informational event. |
| 4873 004873 ATMSAP Unavailable ATMSAP Name: $ZZLAN.atmsap-name, Event Number: ATMSAP unavailable, Reason: reason, Previous State: state, Current State: state [ User Content:
text ] | | atmsap-name | specifies the ATM service-access-point (SAP) that
became unavailable. | | reason | gives the reason the ATMSAP became unavailable. | | state | in the previous state field, state specifies the state the ATMSAP was in before becoming unavailable.
In the current state field, state specifies
the state of the ATMSAP when it became unavailable. | | text | provides additional information about the event. |
Cause The SLSA subsystem cannot access an ATMSAP because the ATMSAP
because the ATMSAP was aborted or stopped or because a failure occurred. Effect The SLSA subsystem is unable to communicate with the ATM network
through the ATMSAP. Recovery Start the ATMSAP or the PIF and SAC and the adapter it is subordinate
to. |
| 4874 004874 ATMSAP State Change ATMSAP Name: $ZZLAN.atmsap-name, Event Number: ATMSAP state change, Reason: reason, Previous State: state, Current State: state, [ User Content:
text ] | | atmsap-name | specifies the ATM service-access-point (SAP) that
had a state change. | | reason | specifies the cause of the state change. | | state | in the previous state field, state specifies the state the ATMSAP was in before the state change occurred.
In the current state field, state specifies
the state of the ATMSAP after the state change occurred. | | text | provides additional information about the state-change
event. |
Cause An ATMSAP changed from one state to another. Effect If the ATMSAP is in the STARTED state, the system can access
the ATM network through the specified ATMSAP; otherwise, the ATMSAP
is unavailable, and the system cannot access the ATM network Recovery If the ATMSAP is in the STOPPED state, start the ATMSAP. |
| 4877 004877 ATMSAP Config Change Type: config-type, ATMSAP Name: $ZZLAN.atmsap-name | | config-type | specifies the type of object configuration. This field
displays one of the following: | Add object | | Delete object | | Alter object |
| | atmsap-name | specifies the ATM service-access-point (SAP) that
was configured. |
Cause An ATMSAP was configured as Add object, Delete object, or Alter
object. Effect The effect depends on the configuration specified by config-type. If config-type is Add object, the ATMSAP can be started to access the ATM network.
If config-type is Delete object, the ATMSAP
is undefined, The ATMSAP configuration cab be changed in the stopped
state. Recovery None. This is an informational event. |
| 4878 004878 ATMSAP Access Gained ATMSAP, Name:
$ZZLAN.atmsap-name, Reason: reason [ Text: custom-text ] | | atmsap-name | specifies the ATM service-access-point (SAP) that
became accessible (that is, link up). | | reason | gives the reason the ATMSAP became accessible. | | custom-text | is additional text describing the reason for the access
gained. |
Cause An ATMSAP was accessible (that is, link up). Effect Data can be sent to and received from the ATM network through
the ATMSAP. Recovery None. This is an informational event. |
| 4879 004879 ATMSAP Access Lost ATMSAP Name: $ZZLAN.atmsap-name, Reason: reason, Origin: source, Severity: level, Type Code: fault-code [ Type String: fault-text ] [ Text:
custom-text ] | | atmsap-name | specifies the ATM service-access-point (SAP) that
became inaccessible (that is, link down). | | reason | gives the reason the ATMSAP became inaccessible. | | source | specifies where the loss of access originated from.
This field displays one of the following: | Unrecognized origin | | LANMON | | DIH | | QIO Subsystem | | LMLIB | | NonStop Kernel | | XIO subsystem | | Filter | | SvNet process | | SvNet interrupt | | DSM subsystem | | NSK Configuration Routine | | LAN Manager | | Service Processor |
| | level | specifies this event as informational, warning, fatal,
or unrecognized. | | fault-code | is a number associated with this particular loss of
access. If access loss originated within the SLSA subsystem, the
event message also displays fault-text. fault-code and associated fault-text are described under along with associated
cause, effect, and recovery information. If the fault originated
outside the SLSA subsystem, the event message displays the error
code received from the other subsystem or process. | | fault-text | is a brief description of the cause of the loss of
access. This field only appears if fault-code is associated with the SLSA subsystem. | | custom-text | is additional text describing the reason for the access
loss. |
Cause An ATMSAP was inaccessible (that is, link down). Effect The effect depends on the fault specified by the fault-code. For more information, see “Fault Numbers for Transient Fault Events”. Recovery The recovery depends on the fault specified by fault-code. For more information, see “Fault Numbers for Transient Fault Events”. |
The event-codes specified in the
type field of the ATM3SA adapter event messages are unique to a specific
event. The following text describes each event-code and gives an explanation of its info-codes, cause, effect, and recovery. | 2501 Request rejected due to PIF not started | | info-code1 | Refers to the ID of the object that was requested
to be operated on. | | info-code2 | Refers to the function that was requested to be
operated on the object (info-code1). | 4096 ADD | | 4102 DELETE | | 4099 START | | 4100 STOP | | 4097 STATS | | 4098 STATS RESET | | 4101 STATUS | | 4104 CPU DOWN (SAC) | | 4105 ASSERT (SAC) | | 16384 PING | | 24576 ADD FILTER | | 24577 DELETE FILTER | | 24578 DELETE ALL FILTERS |
| | info-code3 | Refers to the type of object that was requested to
be operated on (info-code1). | 0 NULL | | 1 PIF | | 2 SAC | | 10 ATMSAP |
| | custom-text | PIF is not STARTED yet |
Cause Request rejected due to PIF not started. A command for a PIF
subordinate object has been issued but the PIF has not yet been
started. Effect The command is rejected. Recovery Ensure that the PIF is in the STARTED state and reissue the
command. If this problem persists contact your HP representative. |
| 2502 Request rejected due to bad object type | | info-code1 | Refers to the ID of the object that was requested
to be operated on. | | info-code2 | Refers to the function that was requested to be
operated on the object (info-code1). | 4096 ADD | | 4102 DELETE | | 4099 START | | 4100 STOP | | 4097 STATS | | 4098 STATS RESET | | 4101 STATUS | | 4104 CPU DOWN (SAC) | | 4105 ASSERT (SAC) | | 16384 PING | | 24576 ADD FILTER | | 24577 DELETE FILTER | | 24578 DELETE ALL FILTERS |
| | info-code3 | Refers to the type of object that was requested to
be operated on (info-code1). | 0 NULL | | 1 PIF | | 2 SAC | | 10 ATMSAP |
| | custom-text | Invalid Object Type |
Cause Request rejected due to bad object type. The object associated
with this command is not a SAC, PIF, or ATMSAP. Effect The command is rejected. Recovery Reissue the command. If this problem persists contact your
HP representative. |
| 5000 PIF request rejected due to PIF state | | info-code1 | Refers to the function that was requested to be
operated on the PIF object. | 4096 ADD | | 4102 DELETE | | 4099 START | | 4100 STOP | | 4097 STATS | | 4098 STATS RESET | | 4101 STATUS | | 16384 PING |
| | custom-text | PIF is not STARTED yet |
Cause The PIF request was rejected due to the PIF state. The PIF
must be in a STARTED state for this command to be processed. An
attempt was made to process a PIF management command when the PIF
was not in the STARTED state. The only PIF management command that
can override this rule is a DELETE PIF. Effect The command is rejected. Recovery Reissue the command. If this problem persists contact your
HP representative. |
| 5001 Attempting to add bad object under PIF | | info-code1 | Refers to the type of object that was requested to
be added under the PIF object: | | custom-text | Invalid SCF object type |
Cause An attempt was made to add a subordinate object under the
PIF, but the object was not an ATMSAP. Effect The command is rejected. Recovery Verify that the object to be added under the PIF is an ATMSAP,
and reissue the command. If this problem persists contact your HP
representative. |
| 5002 PIF is busy with pending DIH request | | info-code1 | Refers to the PIF function that is currently being
processed. | 4096 ADD | | 4102 DELETE | | 4099 START | | 4100 STOP | | 4097 STATS | | 4098 STATS RESET | | 4101 STATUS | | 16384 PING |
| | info-code2 | Refers to the PIF function that was rejected due to
the fact that the PIF was already processing a function which
has not been completed yet. | 4096 ADD | | 4102 DELETE | | 4099 START | | 4100 STOP | | 4097 STATS | | 4098 STATS RESET | | 4101 STATUS | | 16384 PING |
| | custom-text | Previous CMD not completed. |
Cause An attempt was made to process a DIH PIF request while the
PIF still had a pending DIH PIF request. No DIH PIF requests will
be processed until the PIF finishes its pending request. The only
exception is for a DELETE. Effect The command is rejected. Recovery Reissue the command. If this problem persists contact your
HP representative. |
| 5003 Attempting an invalid PIF function | | info-code1 | Refers to the invalid PIF function that is still being
processed. | | custom-text | Invalid PIF func type. |
Cause Attempting an invalid PIF function. An attempt was made to
process a PIF management command other than an ADD, DELETE, PING,
START, STATS, STATS RESET, STATUS, or STOP. Effect The command is rejected Recovery Verify that the command intended for the PIF is a ADD, DELETE,
START, STATS, STATS RESET, STATUS, or STOP. If this problem persists
contact your HP representative. |
| 5004 Add PIF request message size is invalid | | info-code1 | Refers to the invalid ADD PIF message length received. | | info-code2 | Refers to the expected ADD PIF message length. | | custom-text | Invalid ADD PIF MSG size. |
Cause The ADD PIF request message size is invalid. The length of
the message does not match the length of a PIF configuration structure.
The message that was received might have corrupted. Effect The command is rejected. Recovery Reissue the command. If this problem persists contact your
HP representative. |
| 8500 DIH request requires PIF to be aborted | | info-code1 | Refers to the function that was requested to be
operated on the SAC object. | | info-code2 | Refers to the subordinate object type that will be
added under the SAC object. | | info-code3 | Refers to the subordinate object ID that will be added
under the SAC object. | | custom-text | PIF is already started |
Cause A DIH request requires PIF to be aborted. An attempt was made
to ADD a PIF under the SAC object. However, the request failed because
the PIF already exists and is currently in the STARTED state. Effect The PIF object will be terminated and restarted. Recovery None. |
| 8501 Add PIF rejected due to invalid object | | info-code1 | Refers to the function that was requested to be
operated on the SAC object. | | info-code2 | Refers to the subordinate object type that will be
added under the SAC object. | | info-code3 | Refers to the subordinate object ID that will be added
under the SAC object. | | custom-text | Invalid object to ADD |
Cause An attempt was made to add a subordinate object under the
SAC other than a PIF. The current architecture only allows the PIF
object to be the subordinate object under the SAC. The values specified
in info-code2 and info-code3 represent which object type and object ID were attempted to be
added under the SAC. Effect The command is rejected. Recovery Reissue the command. If this problem persists contact your
HP representative. |
| 8502 SAC command failed due to invalid function | | info-code1 | Refers to the function that was requested to be
operated on the SAC object. | 4096 ADD | | 4099 START | | 4098 STATS RESET | | 4104 CPU DOWN (SAC) | | 4105 ASSERT (SAC) | | 16384 PING |
| | info-code2 | Refers to the subordinate object type that will be
added under the SAC object. This will only apply if the function
request on the SAC is an ADD (info-code1 = 4096). | | info-code3 | Refers to the subordinate object ID that will be added
under the SAC object. info-code will
only apply if the function request on the SAC is an ADD (info-code1 = 4096). | | custom-text | Invalid DIH SAC command |
Cause SAC command failed due to invalid function. A DIH message
for the SAC was received which requested an invalid function be
performed on the SAC object. Effect The command is rejected. Recovery Reissue the command. If this problem persists contact your
HP representative. |
The faults specified in the type field of the transient-fault
event message can occur for the LANMON, the DIH, and an internal library
accessed by the LANMAN process. Each fault has a number. The number
ranges are assigned as follows 2000 through 2999 indicates a LANMON fault 3000 through 3999 indicates a DIH fault 4000 through 4999 indicates an internal library fault
The following text describes the cause,
effect, and recovery for each fault specified in the type-field of
the event message. The faults are listed in numerical order. | 2001 LANMON General failure return | Cause When two or more IO files are active at a time or memory pointer
is pointing to NULL or when two or more processes are created at
a time or when Startup parameter indicates abnormal use of LANMON. Effect LANMON halts. Recovery Reload the processor. |
| 2002 Anchor initialization failure | Cause The LANMON could not initialize with QIO. The failure could
be due to a software-version mismatch between LANMON and QIO. Effect LANMON halts. Recovery Reload the processor. |
| 2003 QIO initialization error | Cause The LANMON could not initialize with QIO. The failure could
be due to a software-version mismatch between LANMON and QIO. Effect LANMON halts. Recovery Reload the processor. |
| 2004 Resource failure | Cause The LANMON was unable to obtain memory resources. Effect The operation that LANMON was attempting to execute failed. Recovery Check the memory usage in the processor and check the configuration
of QIO. |
| 2005 Invalid object target | Cause The LANMON received a corrupted message from the LANMAN, which
could be due to a software-version mismatch between LANMON and LANMAN,
corrupted memory, an incorrect configuration, or a corrupted configuration
database. Effect The current operation fails. Recovery Verify the software versions of LANMON, LANMAN, QIO, and the
SLSA DIH. Also, check the configuration of LANMON and LANMAN. |
| 2006 Message not implemented | Cause There is a software version mismatch between a LANMON and
the LANMAN. Effect A LANMAN request is ignored, and the operation fails. Recovery Verify the software versions of LANMON and LANMAN. |
| 2007 Invalid message | Cause There is a software version mismatch between a LANMON and
the LANMAN. Effect A LANMAN request is ignored, and the operation fails. Recovery Verify that the software versions of LANMON and LANMAN. |
| 2008 Invalid status request | Cause A status request was made using an invalid state. The problem
is due to a software-version mismatch between a LANMON and the LANMAN
or memory corruption in LANMON or LANMAN. Effect The request is ignored. Recovery Verify the software versions of LANMON and LANMAN. |
| 2009 Invalid add | Cause A LANMON cannot get resources, or the object already exists.
If this error occurs at startup, the problem might be in the configuration. Effect The object is not added. Recovery Correct the configuration database or add the required subordinate
objects, and retry the command. |
| 2011 Start failure sac init 1 | Cause The driver issued a command to initialize a SAC and received
a response that had a bad checksum. Effect The state of the SAC is unknown. The LANMON resets and retries
the operation on the SAC. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 2012 Start failure sac init 2 | Cause The driver issued a command to initialize a SAC and received
a response that had a bad checksum. Effect The state of the SAC is unknown. The LANMON resets and retries
the operation on the SAC. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it |
| 2013 Start failure pif init 1 | Cause The driver issued a command to initialize a PIF and received
a response that had a bad checksum. Effect The state of the PIF is unknown. The LANMON resets and retries
the operation on the PIF. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 2014 Start failure pif init 2 | Cause The driver issued a command to initialize a PIF, and received
a response that had a bad checksum. Effect The state of the PIF is unknown. The LANMON resets and retries
the operation on the PIF. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 2015 Timer expired | Cause An adapter is not responding to the LANMON because the adapter
is not in its slot, not inserted correctly, or malfunctioning, or
the processor cannot communicate with the adapter. Effect The processor cannot transfer data through the adapter. Recovery Follow the procedures for removing the ServerNet adapter,
and reinstall it. If the error persists, replace the adapter. |
| 2016 Invalid state machine | Cause An internal LANMON error occurred. If this error occurs in
one processor, the error might be due to memory corruption. If
the error occurs in all processors, the code may be corrupted. Effect LANMON halts. Recovery Perform a trace on the LANMON, and contact your HP representative. |
| 2017 Error from filter tree create | Cause QIO could not allocate memory resources. This error might
be due to the current configuration. Effect The PIF is not accessible from the processor, and clients
attempting to use the PIF receive a filter-registration error. Recovery Check your configuration of QIO and the SLSA subsystem, and
correct them if necessary. |
| 2018 SAC control block initialization error | Cause A resource failure occurred during initialization of the SAC. Effect The state of the SAC is unknown. The LANMON resets and retries
the operation on the SAC. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 2020 Parent object is not in valid state | Cause A user tried to start a subordinate object when its parent
object was not started. For example, trying to start a PIF without
starting its parent SAC first. Effect The command is ignored, and no state change occurs. Recovery Issue the command to put the parent object in a valid state. |
| 2021 Child object is not in valid state | Cause A user tried to stop a parent object while the subordinate
object was still in the STARTED state. For example, trying to issue
a STOP command to a SAC that has subordinate PIFs that are still
in the STARTED state. Effect The command is ignored, and no state change occurs. Recovery Stop the subordinate objects, or abort the parent object by
using sub option. |
| 2022 Invalid object type | Cause While performing operation on invalid objects (LIF, PIF, SAC). Effect LANMON halts. Recovery Reload the processor. |
| 2023 Invalid PIF in ADD LIF request | Cause When adding an LIF, if PIF is already associated with other
LIF or if PIF does not exist. Effect ADD LIF command fails and LIF is not added to SLSA subsystem. Recovery Specify existing PIF name and ensure that no existing LIF
is already associated with the specified PIF. |
| 2024 Undesired action in state machine | Cause While trying to delete or abort adapter, it is not in stopped
state. Effect The command is ignored. Recovery Issue a STOP command and then delete or abort the adapter. |
| 2025 Object not found | Cause A LANMON received a corrupted message from the LANMAN. This
error might be due to a software-version mismatch between LANMON
and LANMAN, corrupted memory, an incorrect configuration, or a corrupted
configuration database. Effect The current operation fails. Recovery Verify the software versions of LANMON, LANMAN, QIO, and the
SLSA DIH. Also check the configuration of LANMON and LANMAN. |
| 2026 Message ignored, Not owner | Cause When changing the attributes for objects (LIF, PIF), only
the owner CPU replies to LANMAN and other CPUs ignore the message,
or when particular message is not for the particular LANMON. Effect None. Recovery None. For information only. |
| 2027 Object not owned by this LANMON | Cause When accessing SAC not owned by particular LANMON, rare but
acceptable condition. Effect The processor cannot perform action on SAC. Returns error
message. Recovery Alter the access list. SAC is made available to LANMON. |
| 2028 DIH PING error Host side device error | Cause The SLSA driver cannot ping the device. The problem is in
the DIHs or ServerNet fabric. Effect The LANMON resets and retries the operation on the SAC or
PIF. Recovery Check the ServerNet fabric, and bring it up if it is down.
If the problem persists, reload the processor. |
| 2030 Failed because there are registered users | Cause A STOP command was issued while there were active clients. Effect The command is ignored. Recovery Issue an ABORT command, or stop the clients and issue the
STOP command. |
| 2032 Bad file code or corrupted file for download | Cause The file corresponds to a file name for downloadable operational
or firmware code that cannot be used due to a bad file code or inappropriate
information content. Effect The SAC cannot start or firmware cannot be updated. Recovery Make sure the right file and file name are used. |
| 2033 SLSA module is not in the download file | Cause Firmware or operational code file does not contain a downloadable
module that is appropriate for the particular SAC object. Effect The SAC cannot start or firmware cannot be updated. Recovery Make sure the right file and file name are used. |
| 2034 PIF is already associated with an existing
LIF | Cause An ADD LIF command was issued to add a PIF that is already
being used by a LIF. A PIF can be used by only one LIF. Effect The ADD LIF command fails. Recovery Choose a different unused PIF, or remove the LIF that is using
the specified PIF. |
| 2035 Error from filter tree deletion | Cause An error occurred in the filter-tree removal operation during
a DELETE LIF command. Effect LIF is not removed. Recovery This is a serious error, contact your HP representative. |
| 2036 Failed due to failure(s) in subordinated PIF(s) | Cause A SAC went into the STARTING state because a subordinate PIF
failed and none of the other PIFs subordinate to the SAC are in
the STARTED state. Recovery requires the SAC to restart. Effect The SAC goes into STARTING state and must restart. The SAC
may perform a dump if the AUTODUMP flag is ON. Recovery None. Check for a PIF transient-fault event message. |
| 2037 Delete failed to remove object | Cause The system cannot remove an object during a DELETE command. Effect The object is not removed. Recovery This is a serious error, contact your HP representative. |
| 2038 Device type do not support given command | Cause A command was issued to an object whose parent is of an adapter
type that does not support the specified command Effect The command fails. Recovery Reissue the command to an object whose parent is of an adapter
type that supports the specified command. |
| 2039 SAC is busy with load or dump | Cause When finding the diagnose state of SAC, it is busy with load
or dump operation. Effect Reset operation on the SAC fails. Recovery Allow time to complete the operation and then reset the SAC. |
| 2040 Powerfail message received | Cause A powerfail occurred and the LANMON has received a power-on
message. All SACs must be restarted. Effect All STARTED SACs are restarted Recovery None. This is an informational event. |
| 2041 Invalid dump location information | Cause A DUMP operation occurred for a SAC object that is using invalid
dump‑address information. Dump-address information is obtained from
the application‑download file during the process of starting the
SAC object. Possible causes of bad dump address information are: The SAC never downloads a valid application download
file because no such file exists or because the SAC was never started. The application‑download file contains invalid dump-address
information.
Effect The dump operation fails. Recovery Make sure that a valid application‑download file with valid
dump-address information exists. Use the START SAC command to make
sure that the application‑download file is downloaded into the adapter. |
| 2042 Invalid DIH message received | Cause A message from a DIH contains invalid content. Effect The dump or download operation fails. Recovery Retry the dump or download operation. |
| 2043 Cannot remove PIF with associated LIF | Cause A DELETE ADAPTER command was issued for an ADAPTER object
that has one or more subordinated PIFs linked to existing LIF objects.
An ADAPTER object cannot be removed until there are no LIFs dependent
on it and its subordinated objects. Effect The DELETE ADAPTER command fails. Recovery To delete the ADAPTER object, you must delete all LIFs that
are linked to PIFs subordinate to the specified ADAPTER. Use the
INFO LIF command to determine the names of the LIFs and their associated
PIFs.. |
| 2044 SAC reset fail | Cause An attempt to perform a hardware reset of the SAC failed. Effect The system cannot put the SAC in a definite state. Recovery Make sure the adapter is in the proper slot. If the problem
persists, check the adapter hardware. |
| 2045 Adapter configured but not present | Cause SLSA subsystem does not detect the adapter corresponding to
the specified object because the adapter is not plugged in, or the
adapter is in the process of being reset. Effect The command fails. Recovery Retry the command. If this message persists, make sure the
adapter is installed correctly, and retry the command. |
| 2046 Adapter not same as configured | Cause An operation failed because the adapter in the specified object
location is not the same as the configured adapter type for the
location. Effect The command fails. Recovery Check that the right adapter is in the right location. Reconfigure
the adapter type, accordingly. If the adapter type was correct,
follow the procedures for removing a ServerNet adapter, and reinstall
it. |
| 2047 PIF failed due to failure in associated LIF | Cause A PIF went into the STARTING state because the LIF associated
with the PIF has an error. Recovery requires the PIF to restart. Effect The PIF goes into the STARTING state and must restart. Recovery None. Check for a LIF transient-fault event message. |
| 2048 Downloading filter(s) to adapter fail | Cause Filter error during SAP filter operation. Add filter operation
fails. Effect LIF is not added. Recovery Contact your HP representative. |
| 2049 Removing filter(s) from adapter fail | Cause Delete filter operation fails. Effect LIF is not deleted. Recovery Contact your HP representative. |
| 2050 LIF type does not match specified PIF type | Cause An attempt was made to add a LIF whose type is not compatible
with the type of the PIF specified in the ADD LIF command. Effect The ADD LIF command fails. Recovery Reissue ADD LIF command using different PIF whose type is
compatible with LIF type, or choose different LIF type which is
compatible with the specified PIF type. |
| 2051 Invalid access list | Cause An attempt was made to specify an access list that has more
than two processors for a SAC whose adapter type (MIOE) only supports
two processors in its access list. Effect The ALTER SAC command fails. Recovery Reissue the ALTER SAC command, specifying no more than two
processors in the access list. |
| 2052 Alter not support for specified attribute | Cause An attempt was made to alter PIF attributes which are not
alterable for the adapter type of the target PIF. Effect The ALTER PIF command fails. Recovery Reissue the ALTER PIF command to a PIF that supports the attribute
you are altering, or reissue the command without the unalterable
attributes. |
| 2053 Cannot remove PIF with subord objects | Cause Occurs while deleting an adapter, if associated SAP for PIF
still exists. Effect The delete operation for the adapter fails. Recovery Issue abort adapter and suball command. Delete all LIFs associated
with the PIF and then issue the delete command for the adapter. |
| 2054 Cannot remove objects with subordinates | Cause SAP cannot be deleted because of existence of subordinates. Effect The delete adapter command fails. Recovery Contact your HP representative. |
| 2055 No status of subord with parent not started | Cause Centry data is not available for the ATM adapter. Effect None. Recovery Contact your HP representative. |
| 2056 Object asynchronously aborted by adapter | Cause Token Ring adapter sends an asynchronous delete message. Effect PIF is forcefully deleted. Recovery None. |
| 2069 BAD pointer | Cause A LANMON encountered an internal error. Effect LANMON halts. Recovery Get a processor dump file, then reset and reload the processor. |
| 2099 Onboard POST fail | Cause The SAC encountered a failure during the power-on self-test
(POST) process. Effect The system cannot download the operational code and cannot
put the SAC in the STARTED state. Recovery Check the firmware and hardware by forcing a POST. Use an
SCF ABORT SAC command with the SUB ALL option for the affected SAC
and issue the SCF START SAC command. If this problem persists, contact
your HP representative. |
| 3001 Object state is not valid for this operation | Cause A request for an invalid state changed was made, such as a
START command being issued when the object was already in the STARTED
state. Effect The object rejects the command and does not change its state. Recovery Check the state of the object and issue the appropriate command. |
| 3002 Object has active subordinate object | Cause An attempt was made to stop a SAC while a data transfer was
in progress. Effect The SAC rejects the command and does not change its state. Recovery Check the state of the SAC and issue the appropriate command. |
| 3003 Object does not support the operation requested | Cause The configuration database has a bad adapter configuration. Effect Initialization of the adapter fails, and the system cannot
access the adapter. Recovery Check the configuration database. |
| 3009 TPMP response length is invalid | Cause The driver issued a command to initialize a SAC and received
a response that had an invalid length. Effect The state of the SAC is unknown. The LANMON resets and retries
the operation on the SAC. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 3010 TPMP response checksum bad | Cause The driver issued a command to initialize a SAC and received
a response with a bad checksum. Effect The state of the SAC is unknown. The LANMON resets and retries
the operation on the SAC. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 3011 TPMP response sequence number bad | Cause The driver issued a command to initialize a SAC and received
a response that had an invalid sequence number. Effect The state of the SAC is unknown. The LANMON resets and retries
the operation on the SAC. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 3012 TPMP response command is bad | Cause The driver issued a command to initialize a SAC and received
an invalid response. Effect The state of the SAC is unknown. The LANMON resets and retries
the operation on the SAC. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 3013 TPMP response checksum address bad | Cause The driver issued a command to initialize a SAC and received
a response with an invalid address for the checksum. Effect The state of the SAC is unknown. The LANMON resets and retries
the operation on the SAC. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 3014 TPMP response checksum length bad | Cause The driver issued a command to initialize a SAC and received
a response with invalid length for the checksum field. Effect The state of the SAC is unknown. The LANMON resets and retries
the operation on the SAC. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 3015 Anchor Table invalid | Cause The configuration information in the SAC is invalid. Effect The SLSA subsystem cannot establish communication with the
SAC. Recovery Follow the procedures for removing the ServerNet adapter,
and reinstall it. If the error persists, replace the adapter. |
| 3016 TPMP reinit response length bad | Cause The driver issued a command to reinitialize a SAC and received
a response with an invalid length. Effect The SAC is in an unknown state. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 3017 TPMP controller command failed | Cause The driver issued a command to initialize a SAC and the initialization
failed. Effect The SAC is in an unknown state. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 3018 NIOC reinit response bad | Cause The driver issued a native I/O controller protocol (NIOC)
command to reinitialize a SAC and received an invalid response. Effect The SAC is in an unknown state. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 3019 Failed to get NIOC resource list for adapter | Cause The driver requested a native I/O controller protocol (NIOC)
resource list from the adapter, but did not receive it. Effect The SAC is in an unknown state. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 3020 BTE NACK occurred | Cause Outbound data transfer from a SAC to a processor failed. Effect The SLSA subsystem begins recovery actions to reestablish
a connection with the adapter. Recovery If this error persists, abort and restart the SAC. If the
abort-and-restart sequence does not correct the problem, follow
the procedures for removing and reinstalling the adapter. If the
error persists, perform a trace on the adapter, and contact your
HP representative. |
| 3024 Invalid state machine event | Cause The driver encountered an invalid internal state. Effect The SLSA subsystem initiates recovery. Recovery If this error persists, perform a trace on the object generating
the event, and contact your HP representative. |
| 3025 Failed to create NIOC queue | Cause The driver issued a command to create a queue for a SAC and
the command failed. Effect The SAC is in an unknown state. Recovery If this error persists, follow the procedures for removing
and installing the ServerNet adapter. |
| 3026 Failed to delete NIOC queue | Cause The driver issued a command to delete a queue for a SAC and
the command failed. Effect The SAC is in an unknown state. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 3027 Invalid NIOC response | Cause The format of the response to a message from the driver to
a SAC was bad. Effect LANMON resets the SAC. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 3028 Failed to open PIF | Cause The driver issued a command to initialize a PIF and the initialization
failed. Effect The PIF is in an unknown state. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 3029 Failed to close the PIF | Cause The driver issued a command to close a PIF and the closure
failed. Effect The PIF is in an unknown state. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 3030 Ethernet command response received an error | Cause A violation of the Ethernet protocol occurred. Effect The configuration of the PIF fails. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 3031 Ethernet response header bad | Cause A violation of the Ethernet protocol occurred Effect The configuration of the PIF fails. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 3032 Bad MAC address info in Node Specinfo | Cause The service processor (SP) did not configure the NonStop Kernel
tables correctly. Effect The adapter fails to initialize, and the system cannot access
the adapter. Recovery If the problem persists, power-cycle the adapter. If problem
still persists, contact your HP representative. |
| 3033 Failed to set MAC address | Cause An attempt to set the MAC address failed. Effect The LANMON resets and retries the operation. Recovery If this error persists, follow the procedures for removing
the ServerNet adapter, and reinstall it. |
| 3034 Failed to take PIF ownership | Cause An Ethernet command to establish ownership of the PIF failed. Effect The LANMON resets and retries the operation. Recovery Perform a trace on the LANMON, and contact your HP representative. |
| 3035 Failed to enable the line or PIF | Cause An Ethernet command to enable data transfer failed. Effect The LANMON resets and retries the operation. Recovery Perform a trace on the LANMON, and contact your HP representative. |
| 3036 Host failed to do SAC Set Config | Cause The application (download) code cannot configure the SAC. Effect LANMON retries the operation. Recovery If the problem persists, power-cycle the adapter. If the problem
still persists, contact your HP representative. |
| 3038 SAC name is too long | Cause An internal data error was encountered which could be caused
by a software‑version mismatch between a LANMON and the SLSA DIH
or by a bad configuration file. Effect The SAC is not initialized but is in the STARTING state. Recovery Issue an ABORT command to the SAC, and restart it. |
| 3040 No matching PIF found | Cause The PIF contains invalid configuration information. Effect The SLSA subsystem cannot establish communication with the
PIF. Recovery Follow the procedures for removing the ServerNet adapter,
and reinstall it. If the error persists, replace the adapter. |
| 3041 BTE timeout occurred | Cause The processor sent a command to a ServerNet adapter but received
no response. Either the adapter is not there or the processor has
no access through the ServerNet fabric. Effect The SLSA subsystem begins trying to reestablish a connection
to the adapter. Recovery If this problem persists, abort and restart the SAC. If the
problem still persists, follow the procedures for removing and reinstalling
the adapter. If the error persists, perform a trace on the adapter,
and contact your HP representative. |
| 3042 Powerfail interrupt received | Cause A power failure occurred. Effect The SLSA subsystem initiates power-fail recovery. Recovery If the SLSA recovery operation is not successful, abort and
restart the affected SACs. |
| 3043 SAC or PIF ping was unsuccessful | Cause A LANMON pinged the SAC or PIF but did not receive a reply. Effect No data path is established to the SAC. Recovery If the problem persists, power-cycle the adapter. If the problem
still persists, contact your HP representative. |
| 3044 Path switched to X fabric | Cause The path to the adapter changed fabrics. Effect None. Recovery None. This is an informational event. |
| 3045 Path switched to Y fabric | Cause The path to the adapter changed fabrics. Effect None. Recovery None. This is an informational event. |
| 3046 All paths to this SAC are down | Cause The system cannot access the SAC. Effect LANMON retries the operation. Recovery If the problem persists, check the connections to the SAC
or power-cycle the adapter. If the problem still persists, contact
your HP representative. |
| 3047 Cannot force application to invoke boot | Cause The application (download) code attempted to force the boot
code to start, but the boot of the SAC failed. Effect The system cannot start the SAC. Recovery If the problem persists, power-cycle the adapter. If the problem
still persists, contact your HP representative. |
| 3049 Controller cannot establish connection | Cause The adapter cannot establish a connection to the LAN (for
example, the token‑ring adapter cannot join the ring) either because
of mismatched parameters or a missing cable. Effect The PIF cannot go into the STARTED state (that is, it remains
in the STARTING state). Recovery Make sure that the cable is connected and that the parameters
of the PIF match the LAN it wants to join. |
| 3050 Failed path message received | Cause A SAC requested a path switch. Effect Path switching is in progress. Recovery None. This is an informational event. However, if no other
SACs have reported this message, replace the SAC at the earliest
opportunity; otherwise, this error could indicate that the entire
fabric has failed. If this error persists, contact your HP representative. |
| 3051 Invalid TNet address | Cause Internal error. Effect None. Recovery Contact your HP representative. |
| 3052 Invalid CSP queue size. Queue size must be
power of 2. | Cause Internal error. Effect A fatal error for the SAC. Recovery Contact your HP representative. |
| 3053 Invalid number of resources specified by SAC | Cause Internal error. Effect A fatal error for the SAC. Recovery Contact your HP representative. |
| 3054 Invalid CSP command | Cause Internal error. Effect A fatal error for the SAC. Recovery Contact your HP representative. |
| 3055 Invalid CSP inbound message | Cause Internal error. Effect A fatal error for the PIF. Recovery Contact your HP representative. |
| 4002 Object not found | Cause The LANMAN could not find an object in the internal library
because of an internal inconsistency within the library. Effect LANMAN cannot find information about an object, such as the
status of a SAC. Recovery Abort LANMAN, and restart it. For more information on aborting
and starting processes, see the SCF Reference Manual
for the Kernel Subsystem. |
| 4003 Object list is empty | Cause The LANMONs in the system did not initialize. Effect No SAC objects are displayed when you issue the NAMES command. Recovery Abort LANMAN, and restart it. For more information on aborting
and starting processes, see the SCF Reference Manual
for the Kernel Subsystem. |
| 4004 Invalid context parameter | Cause A data structure in the QIO shared memory has been corrupted. Effect Communication with the LANMON is not possible. Recovery Restart the system. This is a serious error. Contact your
HP representative. |
| 4005 Object is not owned by any LANMON | Cause A command that requires an owner was issued to an unowned
object. Effect No data is returned to the command. Recovery Alter the access list so a LANMON owns the object. |
|