Chapter 135 YMP (YMIOP) Messages

The messages in this chapter are generated by the YMIOP subsystem. $YMIOP, the maintenance I/O process, provides an interface for other NonStop Kernel processes to the master service processor (MSP). Additionally, $YMIOP starts the first TACL process after a system load, as well as the terminal session to which operator messages will be logged during a system load. For more information about the service processor, see the HP NonStop S-Series Operations Guide.

The subsystem ID displayed by these messages includes YMP as the subsystem name. The following example shows the format for YMP operator messages as they are sent to printers, log files, or terminals:

12:53 19MAR96 254,00,004 TANDEM.YMP.F40 1003 YMIOP process on cpu 01 is giving up ownership.




	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.

1000

YMIOP process detected an internal software error.

Cause A logic error occurred in the driver or service layers of the $YMIOP process.

Effect The $YMIOP process enters into an abort state rejecting all requests with file-system error 66 (device down).

Recovery Dump processors 0 and 1, then load the system. Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

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

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.

1001

MSP msp-num is not responding and YMIOP-MSP connection is being reset.

msp-num

is the number of the Master Service Processor (MSP), either 0 or 1.

Cause A software or hardware fault cut off communication with the specified MSP.

Effect The $YMIOP process attempts to reestablish the connection with the MSP. This may cause the active windows for the startup TACL and operator console to switch from X to Y or Y to X.

Recovery No corrective action is needed if one or more of the following is true:

A manual MSP reset was done just prior to the observation of this event
A firmware update on this MSP was done just prior to the observation of this event
An “MSP connection resumed” (event 1009) for the corresponding MSP is observed immediately following this event

If this error persists, your system is not disabled, but you should contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

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

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.

1002

Resource r is absent on the MSP msp-num.

r

is the number of the absent resource, either 0, 1, 2, or 3.

0	CLCI	enables the $YMIOP process to interface with a terminal emulator to provide the initial TACL at system load.
1	CNSL	enables the $YMIOP process to interface with a terminal emulator to provide the console on which operator messages are displayed at system load.
2	EVNT	provides the $YMIOP process with SP-detected events, such as the insertion of a CRU. YMIOP then forwards these events to other NonStop Kernel processes.
3	SPRPC	implements a remote procedure call interface between the $YMIOP process and the SP.

msp-num

is the number of the Master Service Processor (MSP), either 0 or 1.

Cause The specified resource has not been configured or has been removed from the MSP.

Effect YMIOP aborts all outstanding requests directed to the absent resource on the specified MSP with file-system error 140 (communications problem). YMIOP directs future requests for this resource to the alternate MSP, if it exists.

Recovery If this error persists and reports the absence of either the EVNT or the SPRPC resource on both MSPs, power cycle the system and then perform a system load to reinitialize the MSPs and thus gain access to the missing resource. (The system can continue to function without the CNSL resource, or without the CLCI resource if other terminals are available.)

If the error still persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

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

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.

1003

YMIOP process on cpu nn is giving up ownership.

nn

is the number of the processor.

Cause The primary $YMIOP process could not communicate with either MSP and all its attempts to reinitialize the MSPs failed.

Effect The YMIOP primary process aborts all outstanding requests with file-system error 210 (ownership changed during operation). The $YMIOP backup process then takes over from this primary process and becomes the new primary $YMIOP process. All future requests for $YMIOP process are directed to this new primary process.

Recovery If the error persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

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

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.

1004

YMIOP process on cpu nn is the new primary.

nn

is the number of the processor.

Cause The former primary process gave up ownership or the processor running the former primary process failed.

Effect All new requests for the $YMIOP process are directed to the new primary process.

Recovery If the processor running the primary process has failed, take a processor dump, then reload this processor to start a backup $YMIOP process and thus restore fault tolerance. Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

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

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

1005

YMIOP process on cpu nn is going DOWN.

nn

is the number of the processor in which the YMIOP primary process was running.

Cause The primary and backup $YMIOP processes could no longer communicate with either MSP. Repeated attempts to reinitialize the MSPs failed.

Effect All current requests and future requests are terminated with file-system error 66 (device down).

Recovery Dump processors 0 and 1, then perform a system load, which will restart the $YMIOP process. Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

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

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

1006

YMIOP process on cpu nn had a TSER_BUF_MANAGE error with MSP mm.

`nn`	is the number of the processor in which the YMIOP primary process was running.
`mm`	is the number of the master service processor (MSP) in which YMIOP was trying to communicate.

Cause A TNET services error was encountered when tryi8ng to communicate with the MSP.

Effect All current requests are terminated with file-system error 140 (communications problem). The $YMIOP process will attempt to reinitialize communications with the MSP.

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

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

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

1007

YMIOP process on cpu nn is unable to install MSP mm XIO_MODULE_INSTALL error xx.

`nn`	is the number of the processor in which the YMIOP primary process was running.
`mm`	is the number of the master service processor (MSP) in which YMIOP was trying to communicate.
`xx`	is the error number returned by XIO.

Cause YMIOP failed to install a module driver to communicate with a service processor.

Effect The $YMIOP process may be running with a single point of failure, since it cannot establish communications with one of the MSPs.

Recovery Ensure that both IOMF/PMF CRUs are present. Please contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

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

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

1008

YMIOP process detected loss of communication with MSP msp-num on resource r.

msp-num

is the number of the Master Service Processor (MSP), either 0 or 1.

r

is the number of the resource, either 0, 1, 2, or 3:

0	CLCI enables the $YMIOP process to interface with a terminal emulator to provide the initial TACL at system load.
1	CNSL enables the $YMIOP process to interface with a terminal emulator to provide the console on which operator messages are displayed at system load.
2	EVNT provides the $YMIOP process with SP-detected events, such as the insertion of a CRU. YMIOP then forwards these events to other NonStop Kernel processes.
3	SPRPC implements a remote procedure call interface between the $YMIOP process and the SP.

Cause The $YMIOP process detected loss of communication with the MSP.

Effect The $YMIOP process attempts to reestablish the connection with the MSP. This may cause the active windows for the startup TACL and operator console to switch from X to Y or Y to X.

Recovery No corrective action is needed if an “MSP connection resumed” (event 1009) for the corresponding MSP is observed immediately following this event. However, you are requested to notify the Global NonStop Solution Center (GNSC) and Global NonStop Solution Center (GNSC) that this event has occurred and provide the relevant Event Management Service (EMS) logs.

If this error persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

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

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

1009

MSP msp-num is now responding and YMIOP-MSP connection is resumed.

msp-num

is the number of the Master Service Processor (MSP), either 0 or 1.

Cause The $YMIOP process was successful in reestablishing connection with the specified MSP.

Effect The $YMIOP process has restored the connection with the MSP and now can service all requests directed to this MSP.

Recovery No corrective action is needed.