Operator Messages Manual
Chapter 93 SMP (NonStop SNMP Agent) Messages
The messages in this chapter are generated by the NonStop Simple
Network Management Protocol (SNMP) agent, referred to in this chapter
as the NonStop agent. The subsystem ID displayed by NonStop agent
messages includes SMP as the subsystem name. The following example shows the format for SMP operator messages
as they are sent to printers, log files, or terminals:
96-03-17 10:07:00 \NOVA.$ZSNMP TANDEM.SMP.D23 000003 process $Z876
state changed to starting, caused by
Operator
|
| | | |  | 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 Process must run under a SUPER group creator
accessor id | Cause The NonStop agent process was started by a user who was not
a super-group user (255,n), and the NonStop
agent is receiving request messages on a port numbered less than 1023. Effect The agent process does not start. Recovery Use one of these approaches to enable a user who is not a super-group
user to start the NonStop agent: Reset the program file as follows: Log on as a super-group user (255,n) and then start the NonStop agent. Use the File Utility Program (FUP) to give ownership of
the NonStop agent program file (SNMPAGT) to a super-group user. Then
secure the program file so that a user who is not a super-group user
can execute it, and set the PROGID so that the owner ID of SNMPAGT
is used as the creator accessor ID when the program is run.
Alternatively, a user who is not a super-group user
can restart the NonStop agent if the PORT startup parameter is assigned
a value greater than 1023 when the subagent is started.
|
| 2 Internal error in method method-name at location location‑number. Detail:
explanatory-text | | method-name | is the name of a function used internally by the NonStop
agent. | | location-number | is a numeric identifier for a specific location within
the function. | | explanatory-text | is information describing the problem. |
Cause The NonStop agent encountered an unrecoverable internal error,
such as unsuccessful completion of initialization procedures or corruption
of memory. Effect Depending on the severity of the situation, the NonStop agent
responds as follows: If a nonfatal error occurs (such as when an unknown
value is encountered in a request), the NonStop agent stops processing
the request. When the NonStop agent cannot run at all and a takeover
by the backup would only cause a recurrence of the error (such as
when the NonStop agent cannot complete its initialization procedures),
the agent process stops. When a takeover by the backup would clear the error
(such as when corruption of memory occurs), the NonStop agent primary
process abends and the backup process takes over.
Recovery Contact your HP service provider 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 and the saveabend file of the affected process
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 obj-type obj-name state changed to state, caused by { Object | Operator | Service } | | obj-type | is one of the following configurable objects: PROCESS,
ENDPOINT, PROFILE, or TRAPDEST. | | obj-name | is the name of the configurable object, in the form $agent‑process.#object‑name. | | state | is one of the following: DEFINED, STARTED, STARTING,
STOPPING, or STOPPED. |
Cause A NonStop agent object changed state for one of the following
reasons: Effect Object and Operator messages are generally informational only. Service messages reflect the NonStop agent’s ability to
use a service. An unavailable service reduces the NonStop agent’s
ability to function as configured. An unwanted service that becomes
available can cause the NonStop agent to function in an undesirable
way. Recovery Object and Operator messages are informational only; no corrective
action is needed. Service state changes can require investigation
of the circumstances regarding the availability of the underlying
resource. |
| 4 OSS error in method method-name at location location-number. OSS Function:
OSS-function-name Error: OSS-err-num | | method-name | is the name of a function used internally by the NonStop
agent. | | location-number | is a numeric identifier for a specific location within
the function. | | OSS-function-name | is the name of an Open Systems Solutions, Inc., (OSS)
ASN.1 function used to encode and decode SNMP messages. This function,
called by method-name, generated the error. | | OSS-err-num | is an encoding or decoding error returned by the specified
function. See Table 93-1 for
values. |
Cause One of the errors listed in Table 93-1 was returned to the NonStop agent by an Open
Systems Solutions, Inc., (OSS) ASN.1 function. Effect If the error is fatal, the agent stops running. Messages associated
with nonfatal errors are discarded. Recovery Contact your local Simple Network Management Protocol (SNMP)
expert and provide all relevant information as follows: Descriptions of the problems and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs and the saveabend file of the affected process
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. Table 93-1 Encoding and Decoding Errors Returned by an Open Systems Solutions,
Inc., ASN.1 Function | OSS‑err‑num | Fatal
Error? | Description |
|---|
| 4 | No | The end of the input
buffer was reached before the data was fully encoded. | | 0 | No | The protocol data unit
(PDU) was encoded or decoded successfully. This value should never
be seen in an event message for encoding. | | -1 | No | The user-provided output
buffer is too small. This error can be an encoding or decoding error. | | -2 | Yes | An invalid encoding
value was passed. This error can be an encoding or decoding error. | | -3 | Yes | A PDU number passed
to the encoder has no corresponding PDU number generated by the ASN.1
compiler. This error can be an encoding or decoding error. | | -4 | No | The input data contains
an encoded value that exceeds the implementation limits of the decoder.
This is a decoding error. | | -5 | No | The data being decoded
is erroneous. This is a decoding error. | | -6 | Yes | An unexpected NULL
pointer was passed as an argument to the encoder. This error can
be an encoding or decoding error. | | -7 | Yes | An incompatible version
of the ASN.1 compiler was used to produce the control table. This
error can be an encoding or decoding error. | | -8 | No | A memory allocation
error occurred. This error can be an encoding or decoding error. | | -9 | No | There are two possible
causes for this error:Encoding a varbind, the syntax selector (CHOICE) was
out of range. The tag associated with the protocol data unit (PDU)
number specified with pdunum does not match the first PDU in the input
buffer.
| | -10 | No | A bad OBJECT IDENTIFIER
was encountered. The first element must be 0 (ccit), 1 (iso), or
2 (joint-iso-ccit). The second element must be 0 (standard), 1 (registration
authority), 2 (member body), or 3 (identified organization). | | -11 | Yes | An unexpected NULL
pointer was passed to the encoder. | | -12 | Yes | A value having more
than the allowed precision was found in a time type. | | -13 | Yes | A type with a length
or count field before it had a negative length. | | -15 | Yes | The control table
was corrupt. | | -16 | Yes | An attempt was made
to violate the constraint imposed by SizeConstraint. For example,
the number of values in an array of integers is greater than the number
specified in the SizeConstraint of the corresponding SET OF INTEGER. | | -18 | Yes | An error occurred
during error recovery. |
|
| 5 Socket error in method method-name at location location‑number. Socket
Function: socket-function-name, Error:
socket-err-num, File Name: socket-file-name | | method-name | is the name of a function used internally by the NonStop
agent. | | location-number | is a numeric identifier for a specific location within
the function. | | socket-function-name | is the name of socket function. This function, called
by method-name, generated the error. | | socket-err-num | is the socket error number. | | socket-file-name | is the name of the protocol stack with which the socket
is communicating. |
Cause A socket library call returned an error when the NonStop agent
was communicating with HP Transmission Control Protocol/Internet Protocol
(TCP/IP) software. Effect Depends on the error condition. Recovery Network management personnel should consult the file $SYSTEM.SYSTEM.ERRNOH
to translate the socket-err-num value to
a socket error mnemonic. Then consult the Tandem NonStop
TCP/IP and IPX/SPX Programming Manual(for systems running
a D40 or later release of the NonStop Kernel) or the Tandem
TCP/IP Programming Manual (for systems running a pre-D40
release of the NonStop Kernel) to interpret the socket error. If necessary, contact your HP service provider and provide all
relevant information as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated The socket error mnemonic to which socket-err-num translated Supporting documentation such as Event Management
Service (EMS) logs and the saveabend file of the affected process
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
| 6 Configuration error in method method-name at location location‑number. Detail: explanatory-text | | method-name | is the name of a function used internally by the NonStop
agent. | | location-number | is a numeric identifier for a specific location within
the function. | | explanatory-text | is information describing the problem. |
Cause The SNMPCTL file specified at agent startup is already in use
by another agent process. Effect The agent does not start. Recovery Network management personnel should perform one of these two
recovery procedures: Stop the agent that already has the SNMPCTL file open,
then restart the agent. Start the agent from a subvolume that contains an
SNMPCTL file not in use or in which a new SNMPCTL file can be created.
|
| 9 Bad PDU received from process-name. Method method-name at location location-number. Detail: explanatory-text | | process-name | identifies a NonStop SNMP subagent process. | | method-name | is the name of a function used internally by the NonStop
agent. | | location-number | is a numeric identifier for a specific location within
the function. | | explanatory-text | is information describing the problem. |
Cause A subagent constructed and sent the NonStop agent an interprocess
communication (IPC) protocol data unit (PDU) that the agent cannot
decode. This problem should occur only during the debugging of a
subagent. Effect The NonStop agent discards and does not process the message.
If you are using the Event Management Service (EMS) Trap Subagent,
no events are translated into traps. Recovery The subagent developer must check the construction of the IPC
PDU. |
| 10 Bad NMS PDU received from IP-address. Method function-name at location location-number. Detail: explanatory-text | | IP-address | is the internet protocol (IP) address of the SNMP
manager that sent the erroneous message. | | function-name | is the name of a function used internally by the NonStop
agent. | | location-number | is a numeric identifier for a specific location within
the function. | | explanatory-text | is information describing the problem. |
Cause An SNMP manager sent the NonStop agent a message that contained
decodable but erroneous data. Effect The NonStop agent discards the message. Recovery The developer must check the construction of the protocol data
unit. |
| 11 sysUpTime reset explanatory-text | | explanatory-text | identifies the reason for the reset. |
Cause The value of the system group object sysUpTime has been reset. Effect The object sysUpTime indicates the value that has been reset.
This is an informational message only. Recovery This is an informational message only. No corrective action
is necessary. |
| 12 Cannot send trap to non-existent trapDest, trapdest-name, for process-name | | trapdest-name | is the name of the trap destination. | | process-name | is the name of the subagent process. |
Cause A subagent process tried to send a trap to a trap destination
that was not configured within the NonStop agent. Effect The NonStop agent discards the message. Recovery Network management personnel should configure the trap destination
for the agent process. |
| 13 Invalid PDU, pdu-name, received on service point, protocol‑name, from process-name | | pdu-name | is the name of the protocol data unit (PDU). | | protocol-name | is the name of the protocol. | | process-name | is the name of the subagent process. |
Cause A subagent process has incorrectly opened the agent for the
service requested. Effect The NonStop agent sends a close request to the subagent and
waits for the close response from the subagent. Recovery The subagent developer needs to correct the problem, then restart
the agent. |
| 14 Guardian error in method method-name at location location-number. Detail:
explanatory-text | | method-name | is the name of a function used internally by the NonStop
agent. | | location-number | is a numeric identifier for a specific location within
the function. | | explanatory-text | is information including the Guardian procedure, the
returned error, and in some cases, a brief descriptive text. |
Cause A Guardian procedure called by the NonStop agent returned an
error. Effect The NonStop agent continues execution, but will not be able
to return valid information for some of its private Management Information
Base (MIB) objects. Recovery Collect any relevant information, including the details from
the error message. See the Guardian Procedure Calls Reference
Manual for information about the specific procedure and
returned error number. If necessary, contact your HP service provider 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 and the saveabend file of the affected process
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. |
|