Chapter 69 ONS (Open Notification Service) Messages

The messages in this chapter are sent by the Open Notification Service (ONS), which gathers Event Management Service (EMS) events from the system log, $0, translates these events into Simple Network Management Protocol (SNMP) traps, and sends them to a network manager through the Tandem SNMP Agent. The subsystem ID displayed by these messages includes ONS 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.

5103

$ZONS RECEIVED A BAD SPI BUFFER DURING DELIVERY! WARNING.

Cause The format of the incoming event buffer was incorrect or unreadable.

Effect The event buffer in question has been discarded by $ZONS. This event will not be processed. $ZONS continues processing.

Recovery Informational message only; no corrective action is needed.

5104

SNMP AGENT HAS STOPPED RESPONDING TO $ZONS! FATAL.

Cause While processing data, the SNMP Agent has become disconnected.

Effect $ZONS stops.

Recovery Confirm that the SNMP Agent is still running. If it is, restart the ONS. If the SNMP Agent is not running, restart the SNMP Agent and $ZONS.

5105

NMP WAS UNAVAILABLE TO $ZONS DURING STARTUP! FATAL.

Cause $ZONS has stopped itself because the network management platform (NMP) did not connect within the allowed two-hour time period.

Effect $ZONS stops.

Recovery If you expect NMP usage to resume within the next two hours, restart ONS.

5106

$ZONS TIMEOUT ON EVENT DELIVERY TO NMP! WARNING.

Cause The network management platform (NMP) did not respond to the ONS trap by setting the completion bit (an object within the ONS management information base (MIB)) within the two-minute time period. The NMP may be offline. This message is displayed for Syshealth events only.

Effect This error has no effect on $ZONS operation, but it may indicate that the NMP has failed to receive important data.

Recovery The recovery action depends on which NMP you are using, as follows:

If you are using a Tandem-proprietary NMP, confirm that the NMP is still executing. If the NMP is not executing, restart it.
If you are using your own NMP product, this is an informational message only, and no corrective action is needed.

5107

$ZONS CAN’T REGISTER MIB WITH SNMP AGENT! FATAL.

Cause $ZONS was unable to connect with the SNMP Agent process.

Effect $ZONS stops.

Recovery Ensure that the SNMP Agent is running. Then restart $ZONS.

5108

$ZONS CAN’T START DISTRIBUTORS DURING STARTUP! FATAL.

Cause $ZONS was unable to start its distributors.

Effect $ZONS stops.

Recovery Confirm that the standard EMS distributor object, EMSDIST, resides on either SYSnn or on $SYSTEM.SYSTEM. Confirm that process identification numbers (PINs) are still available. Restart $ZONS.

5109

$ZPER WAS UNABLE TO START $ZONS! FATAL.

Cause One of the following situations has occurred:

The Syshealth Persistence Monitor ($ZPER) is not running; therefore, access for registering $ZONS as a persistent process has been denied.
ONS is incorrectly installed or is secured in such a way that $ZPER is unable to access the $ZONS object.
You might not have sufficient security access to run ONS.

Effect $ZONS does not start.

Recovery The recovery action depends on the cause, as follows:

Confirm that $ZPER is running. If not, restart $ZPER, using the Syshealth Management screen. Then restart ONS.
Confirm that all ONS components are installed in their correct locations and are secured for super-group user (255,nn) access.
Reenter the STARTON program with valid system and agent names.
Confirm that you have super-group user (255,nn) access.

5110

$ZONS CAN’T CREATE THE ONS DATABASE (ONSDB) DURING STARTUP! FATAL.

Cause $ZONS attempted to create its statistics database in $SYSTEM.ZSERVICE and was denied access or creation capability.

Effect $ZONS stops.

Recovery Confirm that $SYSTEM has no form of write protection in effect and that sufficient disk space exists on $SYSTEM. Restart $ZONS.

5111

$ZONS CAN’T CREATE FORMATTER PROCESS ($ZNFMT) DURING STARTUP! FATAL.

Cause $ZONS attempted to start $ZNFMT and was unable to do so.

Effect $ZONS stops.

Recovery Confirm that the ALRMFMT object file is in $SYSTEM.ZSERVICE and is secured for super-group user (255,nn) access. Restart $ZONS.