Chapter 47 IPX‑SPX Messages

The messages in this chapter are sent by the NonStop IPX/SPX subsystem. The subsystem ID displayed by these messages includes IPX‑SPX 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.

process name Object Available Reason: change reason Previous state: prev state Current state: curr state

`process name`	is the name of the IPXPROTO process for which this message is generated.
`change reason`	is why the object changed states.
`prev state`	is the state that the IPXPROTO process was in before this message occurred.
`curr state`	is the state of the IPXPROTO process after this message occurred.

Cause NonStop IPX/SPX issues this message whenever a process becomes available.

Effect The process has been created and initialized and is ready for use.

Recovery Informational message only, no corrective action is needed.

process name Object Unavailable Cause: failure cause Underlying object: underlying obj name Symptom: symptom string

`process name`	is the name of the IPXPROTO process for which this message is generated.
`failure cause`	is the reason for the failure.
`underlying obj name`	specifies the names of the underlying object that failed.
`symptom string`	is the location of the internal failure.

Cause NonStop IPX/SPX issues this message whenever a process becomes unavailable or a restart operation has failed. This error occurs after the process has been either stopped or aborted using the Subsystem Control Facility (SCF), when executing cleanup procedures because of a fatal error, or when the process cannot initialize.

Effect The desired process is not available for use.

Recovery If the process was stopped or aborted using SCF, restart the process by using the SCF START command.

On D-series RVUs, if the failure was caused by an underlying object, investigate the status of the underlying object by doing a STATUS LINE or STATUS PORT on the TLAM line or port.

If the failure was caused by an internal failure, save the information returned in this message, contact your Global Mission Critical Solution Center (GMCSC), and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

process name State Change Reason: change reason Previous state: prev state Current state: curr state

`process name`	is the name of the IPXPROTO process for which this message is generated.
`change reason`	is why the object changed states.
`prev state`	is the state that the IPXPROTO process was in before this message occurred.
`curr state`	is the state of the IPXPROTO process after this message occurred.

Cause NonStop IPX/SPX issues this message whenever one of the following occurs:

A process enters a state other than available or unavailable that requires operator intervention before its state can change.
A process persists in the same state long enough for the operator to notice.

Effect The process state is something other than available or unavailable.

Recovery If the state change was caused by an underlying object, investigate the status of the underlying object. Enter a Subsystem Control Facility (SCF) START command to bring the state to STARTED.

process name NonStop processing error. The backup process is corrupted. Cause: cause string [ Action: recovery string ]

`process name`	is the name of the IPXPROTO process for which this error is generated.
`cause string`	is a text description of the cause for the error.
`recovery string`	is a text description of the recovery action to take to correct the error.

Cause NonStop IPX/SPX issues this message when an error occurs that causes the backup process to become corrupted. The backup process is considered corrupted when the primary process cannot checkpoint data to the backup process.

Effect The backup process is running, but it is corrupted. The primary process continues to run. The IPXPROTO process recovers automatically, if possible.

Recovery Check the recovery string for the appropriate action.

process name NonStop processing error. The backup process was unable to take over processing. The process is aborted. Cause: cause string [ Action: recovery string ]

`process name`	is the name of the IPXPROTO process for which this error is generated.
`cause string`	is a text description of the cause for the error.
`recovery string`	is a text description of the recovery action to take to correct the error.

Cause NonStop IPX/SPX issues this message when the backup process cannot take over processing.

Effect The IPXPROTO process is aborted.

Recovery Restart the IPXPROTO process.

process name NonStop processing error. Unable to start the Backup process. Cause: cause string Error detail: err num [ Action: recovery string ]

`process name`	is the name of the IPXPROTO process for which this error is generated.
`cause string`	is a text description of the cause for the error.
`err num`	is the file-system error that was received when trying to create the backup process.
`recovery string`	is a text description of the recovery action to take to correct the error.

Cause The IPXPROTO process cannot start the backup process.

Effect The primary process continues to run without a backup process.

Recovery Start and restart the IPXPROTO process to bring up the backup process.

process name Socket error Local: local ipxaddr Remote: remote ipxaddr Opener: opener process name

`process name`	indicates the name of the IPXPROTO process for which this error is generated.
`local ipxaddr`	indicates the local IPX address to which the local socket is bound.
`remote ipxaddr`	indicates the remote IPX address to which the remote socket is bound.
`opener process name`	indicates the process name of the opener of the local socket.

Cause The IPXPROTO process encountered an internal error on a socket.

Effect The socket connection is lost. The IPXPROTO process will reply to applications with the socket error EIO (4005) and release buffers associated with the socket.

Recovery Applications should close the socket and reopen. If applications cannot automatically recover from this error, stop and restart the applications.

See the TCP/IP and IPX/SPX Programming Manual for a list of socket errors that describe the error conditions for the socket routines and explain how a program can recover from these errors.