Chapter 46 IPXSA (IPX/SPX Subagent) Messages

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

1001

Object available IPX/SPX-SNMP-subagent-process - subagent-process-name, event number: subagent-process-available, reason: reason previous state: disconnected, current state: connected, user content: undefined

`subagent-process-name`	is the name of the IPX/SPX Subagent process.
`reason`	indicates why an operator has brought the IPX/SPX Subagent process up.

Cause An IPX/SPX Subagent process has started successfully.

Effect The IPX/SPX Subagent is available for processing requests.

Recovery Informational message only; no corrective action is needed.

1002

Object unavailable IPX/SPX-SNMP-subagent-process - subagent-process-name, event number: subagent-process-unavailable, cause: operatorrequest, previous state: connected, current state: disconnected, user content: undefined

subagent-process-name

is the name of the IPX/SPX Subagent process.

Cause An IPX/SPX Subagent primary process was intentionally stopped.

Effect The backup process takes over if it exists.

Recovery Informational message only; no corrective action is needed.

1003

Object available agent-resource-object - agent-process-name, event number: agent-available, reason: reason, previous state: disconnected, current state: connected, user content: undefined

agent-process-name

is the name of the NonStop agent process.

reason

is the change reason, as follows:

reason	Definition
operatorrequest	Indicates that an operator has intentionally started the agent connection.
subagent-keepalive	Indicates that the subagent has reestablished lost connections, either through use of the -k startup parameter or its corresponding MIB object, tdmNwSaKeepAliveTimer.

Cause The IPX/SPX Subagent has successfully connected with a NonStop agent process.

Effect The IPX/SPX Subagent can receive requests from the NonStop agent process.

Recovery Informational message only; no corrective action is needed.

1004

Object available agent-resource-object - agent-process-name, event number: agent-unavailable, reason: reason, previous state: connected, current state: disconnected, user content: undefined

agent-process-name

is the name of a NonStop agent process.

reason

is the change reason, as follows:

reason	Definition
operatorrequest	The value of tdmNwSaAgentState object for the NonStop agent process was deliberately set to disconnected.
invalid-processname	A Set operation on tdmNwSaAgentName specified a syntactically incorrect value.
incorrect-processname	A Set operation on tdmNwSaAgentName specified a syntactically incorrect value.
resource-problem	A NonStop agent process failed.

Cause The IPX/SPX Subagent lost its connection to the configured NonStop agent process.

Effect The IPX/SPX Subagent cannot receive requests or transmit responses using the NonStop agent process.

Recovery Correcting the situation depends on the reason for the disconnection:

Change Reason	Recovery
operator request	No corrective action is required because the stoppage was deliberate.
invalid processname	Resubmit the Set request using the correct syntax for a NonStop Kernel process name.
incorrect processname	Start a NonStop agent process using a unique process name.
resource problem	Try to set the value of tdmNwSaAgentState to connected. If the operation fails, see the NonStop IPX/SPX Configuration and Management Manual for ideas about how to troubleshoot the NonStop agent.

1005

Object available backup-process-resource-object - subagent-process-name, event number: backup-available, reason: reason previous state: disconnected, current state: connected, user content: undefined

subagent-process-name

is the name of the IPX/SPX Subagent process.

reason

indicates the reason the IPX/SPX Subagent backup process has become available, as follows:

reason	Definition
operatorrequest	Indicates that an operator has started the backup process.
subagent-keepalive	Indicates that the subagent has reestablished lost connections, either through use of the -k startup parameter or its corresponding MIB object, tdmNwSaKeepAliveTimer.

Cause The IPX/SPX Subagent’s backup process has successfully started.

Effect If the primary IPX/SPX Subagent process fails, the backup process takes over as the primary subagent process and a new backup process is created.

Recovery Informational message only; no corrective action is needed.

1006

Object available backup-process-resource-object - subagent-process-name, event number: backup-unavailable, reason: reason previous state: connected, current state: disconnected, user content: undefined

subagent-process-name

is the name of the IPX/SPX Subagent process.

reason

indicates the reason the IPX/SPX Subagent backup process has become unavailable, as follows:

reason	Definition
operator request	The value of tdmNwSaBackupState object was deliberately set to disconnected.
resource problem	The processor in which the backup process was running failed, or a critical resource was not available.

Cause The backup IPX/SPX Subagent process stopped or failed to start.

Effect The IPX/SPX Subagent is no longer running in fault-tolerant mode.

Recovery Correcting the situation depends on the reason for the stoppage:

Change Reason	Recovery
operator request	No corrective action is required, because the stoppage was deliberate.
resource problem	If a processor failure caused the problem, use a Set operation to change the value of tdmNwSaBackupCPU to an available processor, then Set the value of tdmNwSaBackupState to connected. You can also reload the processor that failed, and the subagent backup process automatically restarts.

1007

Object available emscollector-resource-object - collector-process event number: emscollector-available, reason: reason, previous state: disconnected, current state: connected, user content: undefined

collector-process

is the name of the EMS collector process name to which the IPX/SPX Subagent sends events it generates.

reason

indicates the reason the interface with the EMS collector process has become available, as follows:

reason	Definition
operatorrequest	Indicates that an operator has brought the EMS collector process up.
subagent-keepalive	Indicates that the subagent has reestablished lost connections, either through use of the -k startup parameter or its corresponding MIB object, tdmNwSaKeepAliveTimer.

Cause The IPX/SPX Subagent has successfully connected with an EMS collector process.

Effect The IPX/SPX Subagent can send EMS event messages to the EMS collector process.

Recovery Informational message only; no corrective action is needed.

1008

Object available emscollector-resource-object - collector-process event number: emscollector-unavailable, reason: reason, previous state: connected, current state: disconnected, user content: undefined

collector-process

is the name of the EMS collector process name to which the IPX/SPX Subagent sends events it generates.

reason

indicates the reason the interface with the EMS collector process has become unavailable, as follows:

reason	Definition
operatorrequest	The value of tdmNwSaEmsCollectorState object for the EMS collector process was deliberately set to disconnected.
invalid-processname	A Set operation on tdmNwSaEmsCollectorName specified a syntactically incorrect value.
incorrect-processname	An EMS collector process was stopped, and a non-collector process by the same name was started. When the subagent attempted to reconnect with the stopped collector process, the name of the process running did not identify an EMS collector process.
resource-problem	Resources needed to support communications between the subagent and the EMS collector process are not available.

Cause The IPX/SPX Subagent lost its connection to the configured EMS collector process.

Effect The IPX/SPX Subagent cannot send additional EMS events to the EMS collector until a connection is reestablished.

Recovery Correcting the situation depends on the reason for the disconnection:

Change Reason	Recovery
operator request	No action is required because the stoppage was deliberate.
invalid processname	Resubmit the Set request using the correct syntax for a NonStop Kernel process name.
incorrect processname	Start an EMS collector process using a unique process name.
resource problem	Try to set the value of tdmNwSaEmsCollectorState to connected. If the operation fails, see the EMS Manual for other ideas on making the EMS collector process available.

1009

Object available ipxproto-resource-object - ipxproto-process event number: ipxproto-available, reason: reason, previous state: disconnected, current state: connected, user content: undefined

ipxproto-process

is the name of the IPXPROTO process.

reason

is the reason the IPXPROTO process is available, as follows:

reason	Definition
operator request	Indicates that an operator has set the subagent to reestablish lost connections.
subagent keepalive	Indicates that the subagent has reestablished lost connections, either through use of the -k startup parameter or its corresponding MIB object, tdmNwSaKeepAliveTimer.

Cause The IPX/SPX Subagent has successfully connected with an IPXPROTO process.

Effect The IPX/SPX Subagent can retrieve information from the IPXPROTO process to populate MIB tables that describe IPXPROTO processes.

Recovery Informational message only; no corrective action is needed.

1010

Object available ipxproto-resource-object - ipxproto-process event number: ipxproto-unavailable, reason: reason, previous state: connected, current state: disconnected, user content: undefined

ipxproto-process

is the name of the IPXPROTO process.

reason

indicates the reason the IPXPROTO process has become unavailable, as follows:

reason	Definition
operator request	The value of tdmNwSaIpxProtoState object for the IPXPROTO process was deliberately set to disconnected.
invalid processname	A Set operation on tdmNwSaIpxProtoName specified a syntactically incorrect value.
incorrect processname	A Set operation on tdmNwSaIpxProtoName specified a name for a process that is not an IPXPROTO process.
resource problem	Resources needed to support communications between the subagent and the IPXPROTO process are not available.

Cause The IPX/SPX Subagent lost its connection to IPXPROTO process.

Effect The IPX/SPX Subagent cannot retrieve information from the IPXPROTO process.

Recovery Correcting the situation depends on the reason for the disconnection:

Change Reason	Recovery
operator request	No action is required because the stoppage was deliberate.
invalid processname	Resubmit the Set request using the correct syntax for a NonStop Kernel process name.
incorrect processname	Resubmit the Set request using the name of an existing IPXPROTO process.
resource problem	Try to set the value of tdmNwSaIpxProtoState to connected. If the operation fails, see the NonStop IPX/SPX Configuration and Management Manual for ideas about how to handle unavailable IPXPROTO processes.

1011

Transient Fault IPX/SPX-SNMP-subagent-process - subagent-process-name, event number: memory-allocation-failure, fault type: Memory-allocation user content: undefined

subagent-process-name

is the name of the IPX/SPX Subagent process.

Cause The IPX/SPX Subagent could not allocate the memory needed to perform an operation. The IPX/SPX Subagent allocates memory for various operations, including responding to SNMP requests and adding a new entry to the tdmNwSaIPXPROTONamesTable, the tdmNwSaAgentNamesTable, and the tdmNwServerTable.

Effect The operation could not be completed.

Recovery Stop the IPX/SPX Subagent if necessary; try using another disk as a swap device. If the problem persists, contact the Global NonStop Solution Center (GNSC) 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 EMS logs

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.

1012

Transient Fault IPX/SPX-SNMP-subagent-process - subagent-process-name, event number: process-trapped, fault type: Internal-error user content: undefined

subagent-process-name

is the name of the IPX/SPX Subagent process.

Cause The subagent process trapped.

Effect The subagent process stops.

Recovery If the trap occurred in the primary IPX/SPX Subagent process, any existing backup process takes over, so no corrective action is needed. If a backup process was not running, try restarting the IPX/SPX Subagent. Regardless of whether the subagent is able to recover, contact the Global NonStop Solution Center (GNSC) 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 EMS logs

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.