Chapter 33 ETHSA Messages

The messages in this chapter are generated by the SNMP Ethernet/Token Ring Subagent. The subsystem ID displayed by these messages includes ETHSA 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.

3001

Object available Ethernet-SNMP-subagent - subagent-process-name:seq-no, event number: subagent-process-available, reason: reason, previous state: disconnected, current state: connected, user content: undefined

subagent-process-name:seq-no

is the name and the sequence number of the Ethernet/Token Ring Subagent process.

reason

indicates the reason the Ethernet/Token Ring Subagent process has become available, as follows:

`reason`	Definition
underlying-serv-up	Indicates that the Ethernet/Token Ring Subagent process has come up because an underlying resource upon which it depends has become available.
operator-initiated	Indicates that an operator has brought the Ethernet/Token Ring Subagent process up.

Cause The Ethernet/Token Ring Subagent process completed process initialization after initial startup or after a takeover by the backup process.

Effect The startup configuration (or last saved configuration in the case of a takeover by the backup) is used to establish connections with NonStop agent specified for the subagent’s private zesaAgentName object and to build MIB values derived from the TCP/IP process specified by the zesaTcpIpProcess object.

Recovery Informational message only; no corrective action is needed.

3002

Object unavailable Ethernet-SNMP-subagent - subagent-process-name:seq-no, event number: subagent-process-unavailable, reason: reason, previous state: state, current state: disconnected, [ underlying object: underlying-process-name,] symptom string: code-location/internal-context-text, user content: undefined

subagent-process-name:seq-no

is the name and the sequence number of the Ethernet/Token Ring Subagent process.

reason

indicates the reason the Ethernet/Token Ring Subagent process is unavailable, as follows:

`reason`	Definition
underlying-serv-failed	Indicates that an underlying service the Ethernet/Token Ring Subagent depends on has failed, or an extended memory segment of the subagent process is full and cannot be extended.
internal-failed	Indicates that an internal subagent error in program logic or data was encountered.

state

indicates the previous state of the Ethernet/Token Ring Subagent process, as follows:

`state`	Definition
connected	Indicates a running state, after initialization is complete.
disconnected	Indicates startup initialization state.

underlying-process-name

is the name of the underlying process whose failure caused the Ethernet/Token Ring Subagent process to go out of service. The name of the Ethernet/Token Ring Subagent process specified for the subagent’s private zesaProcessName MIB object appears here.

This information is displayed only if reason is underlying-serv-failed.

code-location/internal-context-text

indicates where in the subsystem or application code the fault occurred.

Cause The Ethernet/Token Ring Subagent process terminated either:

For reasons other than an internal fault or invalid startup configuration.
Because the extended memory segment of the subagent process is full and could not be extended to satisfy a memory allocation request.

Effect The Ethernet/Token Ring Subagent process is unavailable.

Recovery In case of a memory allocation failure, free swap space on the subagent process swap volume and restart the subagent.

Otherwise, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
The saveabend file (if generated)
Details from the message or messages generated
Supporting documentation such as Event Management Service (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.

3003

Object available agent-interface - agent-process-name, event number: agent-interface available, reason: underlying-serv-up, previous state: state, current state: connected, user content: undefined

agent-process-name

is the NonStop agent process name specified for the Ethernet/Token Ring Subagent’s private zesaAgentName MIB object.

underlying-serv-up

indicates that the interface with the NonStop agent process is available because an underlying resource upon which it depends has become available.

state

indicates the previous state of the NonStop agent process, as follows:

`state`	Definition
connected	Indicates a normal operational state.
disconnected	Indicates a nonoperational state where subagent functions dependent on the interface are not available.

Cause The Ethernet/Token Ring Subagent reacquired its connection to the configured NonStop agent process.

Effect Requests can now be made against the MIB objects supported by the Ethernet/Token Ring Subagent.

Recovery Informational message only; no corrective action is needed.

3004

Object unavailable agent-interface - agent-process-name, event number: agent-interface-unavailable, cause: underlying-serv-failed, previous state: state, current state: disconnected, underlying object: underlying-process-name, symptom string: code-location/internal-context-text, user content: undefined

agent-process-name

is the NonStop agent process name specified for the Ethernet/Token Ring Subagent’s private zesaAgentName MIB object.

underlying-serv-failed

indicates that an underlying service the NonStop agent depends on has failed.

state

indicates the previous state of the NonStop agent process, as follows:

`state`	Definition
connected	Indicates a normal operational state.
disconnected	Indicates a nonoperational state where subagent functions dependent on the interface are not available.

underlying-process-name

is the name of the underlying process whose failure caused the interface between the Ethernet/Token Ring Subagent and the NonStop agent to go out of service. The name of the NonStop agent process specified for the subagent’s private zesaAgentName MIB object appears here.

code-location/internal-context-text

indicates where in the subsystem or application code the fault occurred.

Cause The Ethernet/Token Ring Subagent lost its connection to the configured NonStop agent process.

Effect SNMP requests cannot be made against the MIB objects supported by the Ethernet/Token Ring Subagent.

Recovery Check the operating state of the NonStop agent process. If necessary, restart the NonStop agent. The Ethernet/Token Ring Subagent will attempt to reconnect to the NonStop agent at the rate indicated by its zesaKeepAliveTimer object.

3005

Object available backup-process - subagent-process-name: seq-no, event number: backup-process-available, reason: reason, previous state: state, current state: connected, user content: undefined

subagent-process-name:seq-no

is the name and the sequence number of the Ethernet/Token Ring Subagent process.

reason

indicates the reason the backup Ethernet/Token Ring Subagent process has become available, as follows:

`reason`	Definition
underlying-serv-up	Indicates that the backup Ethernet/Token Ring Subagent process is available because an underlying resource upon which it depends has become available.
operator-initiated	Indicates that an operator has brought the backup Ethernet/Token Ring Subagent process up by setting the zesaBackupState MIB object to “enabled.”

state

indicates the previous state of the backup Ethernet/Token Ring Subagent process, as follows:

`state`	Definition
connected	Indicates a normal operational state.
disconnected	Indicates a nonoperational state where subagent function dependent on the interface was not available.
enabled	Indicates that the process was set by an operator such that the subagent would immediately attempt to restore it to a connected state.
disabled	Indicates that the process had been taken out of service explicitly by an operator setting the zesaBackupState MIB object to “disabled.”

Cause The Ethernet/Token Ring Subagent successfully started a backup process identified by zesaBackupCPU:zesaBackupPIN.

Effect Ethernet/Token Ring Subagent configuration changes are now saved to the backup. In case of a primary failure, the backup will resume subagent processing using the last successfully checkpointed configuration.

Recovery Informational message only; no corrective action is needed.

3006

Object unavailable backup-process - subagent-process-name:seq-no, event number: backup-process-unavailable, cause: reason, previous state: state, current state: state, [ underlying object: underlying-process-name,] symptom string: code-location/internal-context-text, user content: undefined

subagent-process-name:seq-no

is the name and the sequence number of the Ethernet/Token Ring Subagent process.

reason

indicates the reason the backup Ethernet/Token Ring Subagent process has become unavailable, as follows:

`reason`	Definition
underlying-serv-failed	Indicates that an underlying service the backup Ethernet/Token Ring Subagent process depends on has failed.
operator-initiated	Indicates that an operator has taken the backup Ethernet/Token Ring Subagent process out of service.

state

indicates the previous and current states of the backup Ethernet/Token Ring Subagent process, as follows:

`previous state: state`	Associated Text (DDL AS Clause)
connected	Indicates a normal operational state.

`current state: state`	Associated Text (DDL AS Clause)
disconnected	Indicates a nonoperational state where subagent function is not available.
disabled	Indicates that the process has been taken out of service explicitly by an operator setting the zesaBackupState MIB object to “disabled.”

underlying-process-name

is the name of the underlying process whose failure caused the backup Ethernet/Token Ring Subagent process to go out of service. The name of the Ethernet/Token Ring Subagent process specified for the subagent’s private zesaProcessName MIB object appears here.

This information is displayed only if reason is underlying-serv-failed.

code-location/internal-context-text

indicates where in the subsystem or application code the fault occurred.

Cause The backup Ethernet/Token Ring Subagent process stopped or failed to start.

Effect The Ethernet/Token Ring Subagent process continues to run without a backup. Configuration changes are not saved if a primary process failure occurs.

Recovery Check the status of the configured backup processor (zesaBackupCPU). If it is not available or there are insufficient resources to run a backup process, disable the backup (set zesaBackupState “Disabled (3)”), set the zesaBackupCPU to an available processor, and reenable the backup (set zesaBackupState “Enabled(4)”.

3007

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

collector-process

is the EMS collector process name specified for the subagent’s private zesaEmsCollectorName MIB object.

reason

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

`reason`	Definition
underlying-serv-up	Indicates that the interface with the EMS collector process is available because an underlying resource upon which it depends has become available.
operator-initiated	Indicates that an operator has brought the EMS collector process up.

state

indicates the previous state of the interface to the EMS collector process, as follows:

`state`	Definition
connected	Indicates a normal operational interface between the subagent and the EMS collector.
disconnected	Indicates a nonoperational state where subagent function dependent on the interface was not available.
enabled	Indicates that the interface had been set by an operator such that the subagent would immediately attempt to restore it to a connected state.
disabled	Indicates that the interface had been taken out of service explicitly by an operator setting the zesaEmsCollectorState MIB object to “disabled.”

Cause The subagent acquired or reacquired its connection to the configured EMS collector process (zesaEmsCollectorName).

Effect Subsequent EMS events generated by the subagent will be sent to the configured EMS collector process.

Recovery Informational message only; no corrective action is needed.

3008

Object unavailable emscollector-interface - collector-process, event number: emscollector-process-unavailable, cause: reason, previous state: state, current state: disconnected, [ underlying object: underlying-process-name,] symptom string: code-location/internal-context-text, user content: undefined

subagent-process-name:seq-no

is the name of the EMS collector process to which the Ethernet/Token Ring Subagent is sending events (as specified for the subagent’s private zesaEmsCollectorName MIB object).

reason

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

`reason`	Definition
underlying-serv-failed	Indicates that an underlying service the interface with the EMS collector process depends on has failed.
operator-initiated	Indicates that an operator has taken the EMS collector process out of service.

state

indicates the previous state of the interface with the EMS collector process, as follows:

`state`	Definition
connected	Indicates a normal operational state.
disconnected	Indicates a nonoperational state where subagent function dependent on the interface is not available.
enabled	Indicates that the interface has been set by an operator such that the subagent immediately attempts to restore it to a connected state.
disabled	Indicates that the interface has been taken out of service explicitly by an operator setting the zesaEmsCollectorState MIB object to “disabled.”

underlying-process-name

is the name of the underlying process whose failure caused the interface between the Ethernet/Token Ring Subagent and the EMS collector to go out of service. The name of the EMS collector process specified for the subagent’s private zesaEmsCollectorName MIB object appears here.

This information is displayed only if reason is underlying-serv-failed.

code-location/internal-context-text

indicates where in the subsystem or application code the fault occurred.

Cause The subagent lost its connection to the configured EMS collector process (zesaEmsCollectorName).

Effect Events generated by the subagent are discarded until the EMS collector interface is returned to a connected state. The subagent attempts to reacquire the EMS collector connection whenever the subagent attempts to generate an event message and based at the rate indicated by its zesaKeepAliveTimer object.

Recovery Check the operating state of the EMS collector process (zesaEmsCollectorName).

3009

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

tcpip-process

is the TCP/IP process name being managed by the Ethernet/Token Ring Subagent (as specified for the subagent’s private zesaTcpIpProcess MIB object).

reason

indicates the reason the interface with the TCP/IP process has become available, as follows:

`reason`	Definition
underlying-serv-up	Indicates that the interface with the TCP/IP process is available because an underlying resource upon which it depends has become available.
operator-initiated	Indicates that an operator has brought the TCP/IP process up.

state

indicates the previous state of the interface with the TCP/IP process, as follows:

`state`	Definition
connected	Indicates a normal operational interface between the Ethernet/Token Ring Subagent and the TCP/IP process it is managing.
disconnected	Indicates a nonoperational state such that subagent function dependent on the interface is not available.
enabled	Indicates that the interface to the TCP/IP resource has been set by an operator such that the subagent immediately attempts to restore it to a connected state.
disabled	Indicates that the interface to TCP/IP resource has been taken out of service explicitly by an operator setting the zesaTcpIpState MIB object to “disabled.”

Cause The subagent acquired or reacquired its connection to the configured TCP/IP process (zesaTcpIpProcess).

Effect The MIB object values supported by the Ethernet/Token Ring Subagent are rebuilt using SPI responses from the TCP/IP process (zesaTcpIpProcess). When the update sequence is complete (as indicated by zesaRefreshNow value = "autoDynamicRefresh (0)"), SNMP requests made against the MIB objects will return current values.

Recovery Informational message only; no corrective action is needed.

3010

Object unavailable tcpip-resource - tcpip-process, event number: tcpip-resource-unavailable, cause: reason, previous state: state, current state: state, [ underlying object: underlying-process-name,] symptom string: code-location/internal-context-text, user content: undefined

tcpip-process

is the name of the TCP/IP process being managed by the Ethernet/Token Ring Subagent (as specified for the subagent’s private zesaTcpIpProcess MIB object).

reason

indicates the reason the interface with the TCP/IP process has become unavailable, as follows:

`reason`	Definition
underlying-serv-failed	Indicates that an underlying service the interface with the TCP/IP process depends on has failed.
operator-initiated	Indicates that an operator has taken the TCP/IP process out of service.

state

indicates the previous and current states of the TCP/IP process being monitored, as follows:

`previous state: state`	Associated Text (DDL AS Clause)
connected	Indicates a normal operational state.

`current state: state`	Associated Text (DDL AS Clause)
disconnected	Indicates a nonoperational state where subagent function is not available.
disabled	Indicates that the process has been taken out of service explicitly by an operator setting the zesaTcpIpState MIB object to “disabled.”

underlying-process-name

is the name of the underlying process whose failure caused the interface between the Ethernet/Token Ring Subagent and the TCP/IP process to go out of service. The name of one of the following processes is inserted in the message text following “underlying object:”

The name of the TCP/IP process specified for the subagent’s private zesaTcpIpProcess MIB object
The name of the SCP process specified for the subagent’s private zesaScpProcess MIB object
The name of the NonStop agent process specified for the subagent’s private zesaAgentName MIB object

This information is displayed only if reason is underlying-serv-failed.

code-location/internal-context-text

indicates where in the subsystem or application code the fault occurred.

Cause The Ethernet/Token Ring Subagent process lost its connection to the configured TCP/IP process (zesaTcpIpProcess), the SCP SPI interface process (zesaScpProcess), or the NonStop agent process (zesaAgentName).

If the underlying object is the NonStop agent process (zesaAgentName), the subagent has lost its connection to the agent process and has temporarily disconnected the TCP/IP interface to conserve resources.

Effect Values for the MIB objects supported by the Ethernet/Token Ring Subagent are not computed. SNMP requests for these MIB objects receive an SNMP-ERR-GEN-ERROR response. Private MIB objects supported by the Ethernet/Token Ring Subagent can still be accessed.

Recovery If the underlying object is the TCP/IP process or the SCP process, use SCF or the STATUS command to check the operating state of the TCP/IP or SCP process. The subagent attempts to reacquire the TCP/IP connection according to the value of its zesaKeepAliveTimer object.

If no error conditions are found in the TCP/IP and SCP processes, or if the subagent fails to reacquire the SCP interface, stop and restart the subagent with a different SCP process.

If the underlying object is the NonStop agent process, check the operating state of the NonStop agent process. If necessary, restart the NonStop agent. The Ethernet/Token Ring Subagent attempts to reconnect to the NonStop agent at the rate indicated by its zesaKeepAliveTimer object.

3011

Transient Fault Ethernet-SNMP-subagent - subagent-process-name:seq-no, event number srl-call-failed, fault type: srl-call-failure user content: undefined

subagent-process-name:seq-no

is the name and the sequence number of the Ethernet/Token Ring Subagent process.

Cause A shared resource library (SRL) call failed.

Effect Old values in the MIB are retained and the MIB does not get refreshed.

Recovery Informational message only; no corrective action is needed.

3012

Object unavailable Ethernet-SNMP-subagent - subagent-process-name:seq-no, event number: internal-fault, cause: internal-failed, previous state: state, current state: disconnected, symptom string: configuration-fault-detail, user content: undefined

subagent-process-name:seq-no

is the name and the sequence number of the Ethernet/Token Ring Subagent process.

internal-failed

indicates that an internal error was encountered.

state

indicates the previous state of the Ethernet/Token Ring Subagent process, as follows:

`state`	Definition
connected	Indicates a subagent in a running state, having completed its startup initialization.
disconnected	Indicates a subagent performing startup initialization.

code-location/internal-context-text

indicates where in the subsystem or application code the fault occurred.

Cause The Ethernet/Token Ring Subagent internal consistency checking logic has detected a program logic error.

Effect The Ethernet/Token Ring Subagent terminates.

Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
The saveabend file (if generated)
Details from the message or messages generated
Supporting documentation such as Event Management Service (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.

3013

Object unavailable Ethernet-SNMP-subagent - subagent-process-name:seq-no, event number: startup-configuration-invalid, cause: internal-failed, previous state: enabled, current state: disconnected, symptom string: invalid startup params user content: undefined

`subagent-process-name`:`seq-no`	is the name and the sequence number of the Ethernet/Token Ring Subagent process.
internal-failed	indicates that an internal error was encountered.
invalid startup params	indicates that invalid startup parameters were passed to the subagent.

Cause The startup parameters passed to the subagent process contain invalid definitions or the specified agent process was not found.

Effect The Ethernet/Token Ring Subagent terminates.

Recovery Check the startup parameter string passed to the Ethernet/Token Ring Subagent. Check the operating state of the specified NonStop agent process to ensure that it is running and ready to accept subagent connections.

3014

Takeover by backup process, Primary-stopped

Cause The subagent primary process terminated. The recognized causes are either process termination or primary processor failure.

Effect The backup process takes over the subagent primary role using the last known configuration parameters. Any transactions that were in progress at the time of the primary failure are lost.

The new primary attempts to restart a backup process in the former primary processor according to the zesaKeepAliveTimer interval.

Recovery If the cause was a processor failure, the backup processor (zesaBackupCPU) should be changed to a currently active processor.

If the cause was a primary process failure, the event log should be examined to determine the underlying cause for the process abend.