Chapter 44 IPB (Interprocessor Bus) Messages

Cause  cpu1 has detected a problem on bus z while sending a message to cpu2.

Effect  If more than 10 timeouts and resends occur in 11 minutes, the operating system disables the bus path and generates IPB operator message 101.

Recovery  Informational message only; no corrective action is needed.

Cause  Either the operating system has disabled the bus path due to bus errors, or the operator has issued a command-interpreter (X/Y) BUSDOWN command.

If IPB operator message 100 or 102 was generated before this message, there was a hardware failure on the bus.

Effect  The operating system brings down the bus.

Recovery  If an operator has brought down the bus, the bus remains down until an operator manually restores it with the Tandem Command Language (TACL) (X/Y) BUSUP command.

If the operating system has brought down the bus, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

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.

Cause  cpu1 has detected checksum errors on bus z by cpu2.

Effect  If more than 10 of these errors occur in 11 minutes, the operating system disables the faulty bus path and generates IPB operator message 101.

Recovery  Informational message only; no corrective action is needed.

Cause  An operator has used the Tandem Command Language (TACL) (X/Y) BUSUP command to bring up bus z to the specified processor.

Effect  The operating system brings up the bus.

Recovery  Informational message only; no corrective action is needed.

Cause  Either there is a bus hardware problem or cpu1 is trying to recover from other errors from processor cpu2.

Effect  The system reports the problem and continues processing.

Recovery  Informational message only; no corrective action is needed.

Cause  The processor has detected an error on bus z, such as a timeout error, while receiving data.

Effect  The system reports the error and continues processing.

Recovery  Normally, no corrective action is needed. However, if the error recurs, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

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.

Cause  A hardware problem has occurred on bus z. The bus is experiencing parity errors.

Effect  The error counter is set to zero.

Recovery  Normally, no corrective action is needed. However, if the error recurs, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

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.

Cause  A hardware problem has occurred on the out queue for bus z.

Effect  The specified bus is marked as bad and is no longer used for sending messages.

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

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.

Cause  The routing code on the received packet from bus z did not match the cpu2 code.

Effect  None.

Recovery  Normally, no corrective action is needed. However, if the error recurs, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

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.

Cause  The IPB interface on the specified NonStop Cyclone processor has encountered either a parity error or a reset on the control lines from the bus controller. IPB operator messages 110, 111, and 112 indicate hardware errors reported by the NonStop Cyclone IPB chip and are recorded in a common error counter.

Effect  If more than 1000 of these errors occur in a 19.2-second interval, the operating system shuts down the bus to all processors and generates IPB operator message 101 (bus down).

Recovery  Normally, no corrective action is needed. However, if the error recurs, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

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.

Cause  The IPB interface on the specified processor has encountered an error in one of its send state machines. IPB operator messages 110, 111, and 112 indicate hardware errors reported by the NonStop Cyclone IPB chip and are recorded in a common error counter.

Effect  If more than 1000 of these errors occur in a 19.2-second interval, the operating system shuts down the bus to all processors and generates IPB operator message 101 (bus down).

Recovery  Normally, no corrective action is needed. However, if the error recurs, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

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.

Cause  The IPB interface on the specified processor has encountered an error in one of its send state machines. IPB operator messages 110, 111, and 112 indicate hardware errors reported by the NonStop Cyclone IPB chip and are recorded in a common error counter.

Effect  If more than 1000 of these errors occur in a 19.2-second interval, the operating system shuts down the bus to all processors and generates IPB operator message 101 (bus down).

Recovery  Normally, no corrective action is needed. However, if the error recurs, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

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.

Cause  There were either too many BUSXSUM events or too many INQTIMEOUT events.

Effect  The operating system turns off reception on the specified bus.

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

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.

Cause  There were errors in the transmission of a message over the IPB.

Effect  If there are more than 10 of these errors, the operating system disables the bus path and issues IPB operator message 113 (bus reception turned off).

Recovery  Informational message only; no corrective action is needed.