Chapter 117 TCPIPSA (TCP/IP Subagent) Messages

The messages in this chapter are generated by the Transmission Control Protocol/Internet Protocol (TCP/IP) Subagent subsystem. The subsystem ID displayed by these messages includes TCPIPSA 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 TCP/IP-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 TCP/IP Subagent process.

reason

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

`reason`	Definition
underlying-serv-up	Indicates that the TCP/IP 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 TCP/IP Subagent process up.

Cause The TCP/IP 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 in the subagent’s private ztsaAgentName object and to build MIB-II values derived from the TCP/IP process specified in the subagent’s private ztsaTcpIpProcess object.

Recovery Informational message only; no corrective action is needed.

1002

Object unavailable TCP/IP-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 TCP/IP Subagent process.

reason

indicates the reason the TCP/IP Subagent process is unavailable, as follows:

`reason`	Definition
underlying-serv-failed	Indicates that an underlying service the TCP/IP Subagent depends on has failed.
internal-failed	Indicates that an internal subagent error in program logic or data was encountered.

state

indicates the previous state of the TCP/IP 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 TCP/IP Subagent process to go out of service. The name of the TCP/IP Subagent process specified for the TCP/IP Subagent’s private ztsaProcessName 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 TCP/IP Subagent process terminated for reasons other than an internal fault or invalid startup configuration.

Effect The TCP/IP Subagent process is unavailable.

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.

1003

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 TCP/IP Subagent’s private ztsaAgentName 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 TCP/IP Subagent reacquired its connection to the configured NonStop agent process.

Effect Requests can now be made against the MIB-II and private MIB objects supported by the TCP/IP Subagent.

Recovery Informational message only; no corrective action is needed.

1004

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 TCP/IP Subagent’s private ztsaAgentName 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 TCP/IP Subagent and the NonStop agent to go out of service. The name of the NonStop agent process specified for the TCP/IP Subagent’s private ztsaAgentName MIB object appears here.

code-location/internal-context-text

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

Cause The TCP/IP Subagent lost its connection to the configured NonStop agent process.

Effect SNMP requests cannot be made against the MIB-II or private MIB objects supported by the TCP/IP Subagent.

Recovery Check the operating state of the NonStop agent process. If necessary, restart the NonStop agent. The TCP/IP Subagent will attempt to reconnect to the NonStop agent at the rate indicated by its ztsaKeepAliveTimer object.

1005

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 TCP/IP Subagent process.

reason

indicates the reason the backup TCP/IP Subagent process has become available, as follows:

`reason`	Definition
underlying-serv-up	Indicates that the backup TCP/IP 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 TCP/IP Subagent process up by setting the ztsaBackupState MIB object to “enabled.”

state

indicates the previous state of the backup TCP/IP 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 ztsaBackupState MIB object to “disabled.”

Cause The TCP/IP Subagent successfully started a backup process identified by ztsaBackupCPU:ztsaBackupPIN.

Effect TCP/IP 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.

1006

Object unavailable backup-process - subagent-process-name:seq-no, event number: backup-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 and the sequence number of the TCP/IP Subagent process.

reason

indicates the reason the backup TCP/IP Subagent process has become unavailable, as follows:

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

state

indicates the previous state of the backup TCP/IP Subagent process, as follows:

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

underlying-process-name

is the name of the underlying process whose failure caused the backup TCP/IP Subagent process to go out of service. The name of the TCP/IP Subagent process specified for the TCP/IP Subagent’s private ztsaProcessName 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 TCP/IP Subagent process stopped or failed to start.

Effect The TCP/IP 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 (ztsaBackupCPU). If it is not available or there are insufficient resources to run a backup process, disable the backup (set ztsaBackupState “Disabled (3)”), set the ztsaBackupCPU to an available processor, and reenable the backup (set ztsaBackupState “Enabled(4)”.

1007

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 TCP/IP Subagent’s private ztsaEmsCollectorName 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 ztsaEmsCollectorState MIB object to “disabled.”

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

Effect Subsequent EMS events generated by the subagent will be sent to ztsaEmsCollectorName.

Recovery Informational message only; no corrective action is needed.

1008

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 TCP/IP Subagent is sending events (as specified for the subagent’s private ztsaEmsCollectorName 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 ztsaEmsCollectorState MIB object to “disabled.”

underlying-process-name

is the name of the underlying process whose failure caused the interface between the TCP/IP Subagent and the EMS collector to go out of service. The name of the EMS collector process specified for the subagent’s private ztsaEmsCollectorName 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 (ztsaEmsCollectorName).

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 and event message.

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

1009

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 TCP/IP Subagent (as specified for the subagent’s private ztsaTcpIpProcess 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 TCP/IP 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 ztsaTcpIpState MIB object to “disabled.”

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

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

Recovery Informational message only; no corrective action is needed.

1010

Object unavailable tcpip-resource - tcpip-process, event number: tcpip-resource-unavailable, cause: reason, previous state: state, current state: disconnected, [ 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 TCP/IP Subagent (as specified for the subagent’s private ztsaTcpIpProcess 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 state of the interface with the TCP/IP 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 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 the TCP/IP resource has been taken out of service explicitly by an operator setting the ztsaTcpIpState MIB object to “disabled.”

underlying-process-name

is the name of the underlying process whose failure caused the interface between the TCP/IP 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 ztsaTcpIpProcess MIB object
The name of the SCP process specified for the subagent’s private ztsaScpProcess MIB object
The name of the NonStop agent process specified for the subagent’s private ztsaAgentName 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 TCP/IP Subagent process lost its connection to the configured TCP/IP process (ztsaTcpIpProcess), the SCP SPI interface process (ztsaScpProcess), or the NonStop agent process (ztsaAgentName).

If the underlying object is the NonStop agent process (ztsaAgentName), 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-II objects supported by the TCP/IP Subagent are not computed. SNMP requests for these MIB-II objects receive an SNMP-ERR-GEN-ERROR response. Private MIB objects supported by the TCP/IP Subagent can still be accessed.

Recovery If the underlying object is the TCP/IP process or the SCP process, use SCF 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 ztsaKeepAliveTimer 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.

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 TCP/IP Subagent attempts to reconnect to the NonStop agent at the rate indicated by its ztsaKeepAliveTimer object.

1011

Transient Fault TCP/IP-SNMP-subagent - subagent-process-name:seq-no, event number out-of-memory, fault type: Memory-allocation user content: undefined

subagent-process-name:seq-no

is the name and the sequence number of the TCP/IP Subagent process.

Cause The extended memory segment of the TCP/IP Subagent process is full and could not be extended to satisfy a memory allocation request.

Effect The operation that was in progress is aborted. This may result in objects transitioning into the “disconnected” state to be later reconnected. The subagent functionality will be impaired as long as the memory shortage continues.

Recovery Free swap space on the subagent process swap volume or stop and restart the subagent with a different swap volume specified on the run line. 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 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.

1012

Object unavailable TCP/IP-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 TCP/IP Subagent process.

internal-failed

indicates that an internal error was encountered.

state

indicates the previous state of the TCP/IP 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 TCP/IP Subagent internal consistency checking logic has detected a program logic error.

Effect The TCP/IP 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.

1013

Object unavailable TCP/IP-SNMP-subagent - subagent-process-name:seq-no, event number: startup-configuration-invalid, cause: internal-failed, previous state: enabled, 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 TCP/IP Subagent process.

internal-failed

indicates that an internal error was encountered.

configuration-fault-detail

provides additional information about the configuration in the following format:

Agent process name parameter bad-value invalid
TCP/IP process name parameter bad-value invalid
Non-local TCP/IP process name parameter bad-value
Collector process name parameter bad-value invalid
Info cache value bad-value, out of range
Stats cache value bad-value, out of range
Status cache value bad-value, out of range
Keep alive timer value bad-value, out of range
Backup CPU value bad-value, out of range
SCP process name parameter bad-value invalid
Non-local SCP process name parameter bad-value
Unrecognized parameter type bad-value
Incomplete parameter specification bad-value, missing value
Parameter bad-value, specified multiple times

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

Effect The TCP/IP Subagent terminates.

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




	NOTE: Event 1013 is sent to the EMS collector that is in effect when the parsing error is detected. If the -c startup parameter is specified later in the startup string, after the error is detected, the event is sent to the default collector $0. If $0 is not available, no event is generated.

1014

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 ztsaKeepAliveTimer interval.

Recovery If the cause was a processor failure, the backup processor (ztsaBackupCPU) 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.

1015

Transient Fault TCP/IP-SNMP-subagent - subagent-process-name:seq-no, event number: lanmon-resource-unavailable, fault type: lanmon-not-responding, user content: undefined

subagent-process-name:seq-no

is the name and the sequence number of the TCP/IP Subagent process.

Cause The LANMON process did not respond to the LM_Get_Version_ function within the necessary timeframe.

Effect The ifDescr object values will not contain the LANMON version string.

Recovery Generally, this condition is transient and no corrective action is necessary. 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 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 as well.

1022

Transient Fault TCP/IP-SNMP-subagent - subagent-process-name:seq-no, event number: lmPIFgetstatus-error, fault type: PIF-status-cmd-not-completed, user content: undefined

subagent-process-name:seq-no

is the name and the sequence number of the TCP/IP Subagent process.

Cause The LM_Get_Status_ function returned an error for the PIF.

Effect The ifTable values obtained through the STATUS command are not current until the timer expires, the same ZLANMSRL call is retried, and a response obtained.

Descriptions of the problem and accompanying symptoms
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 as well.

1023

Transient Fault TCP/IP-SNMP-subagent - subagent-process-name:seq-no, event number: lmPIFgetattr-error, fault type: PIF-attr-cmd-not-completed, user content: undefined

subagent-process-name:seq-no

is the name and the sequence number of the TCP/IP Subagent process.

Cause The LM_Get_Attributes_ function returned an error on the PIF.

Effect The ifTable values obtained through the INFO command are not current until the timer expires, the same ZLANMSRL call is retried, and a response obtained.

Descriptions of the problem and accompanying symptoms
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 as well.

1039

Transient Fault TCP/IP-SNMP-subagent - subagent-process-name:seq-no, event number: lmLIFgetattr-error, fault type: LIF-attr-cmd-not-completed, user content: undefined

subagent-process-name:seq-no

is the name and the sequence number of the TCP/IP Subagent process.

Cause The LM_Get_Attributes_ function returned an error for the LIF.

Effect The ifTable values are not current until the timer expires, the same ZLANMSRL call is retried, and a response obtained.

Descriptions of the problem and accompanying symptoms
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 as well.

1041

Transient Fault TCP/IP-SNMP-subagent - subagent-process-name:seq-no, event number: lmPIFgetstats-error, fault type: PIF-status-cmd-not-completed, user content: undefined

subagent-process-name:seq-no

is the name and the sequence number of the TCP/IP Subagent process.

Cause The LM_Get_Statistics_ function returned an error.

Effect The ifTable values obtained through the STATS command are not current until the timer expires, the same ZLANMSRL call is retried, and a response obtained.

Descriptions of the problem and accompanying symptoms
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 as well.