Chapter 124 TRAPMUX (Trap Multiplexer) Messages

Cause  The Trap Multiplexer received a coldStart trap. The coldStart trap is a standard SNMP trap signifying that the sending entity has reinitialized—most likely because of a restart due to an error condition—and its configuration may change.

Effect  The effect is specific to the product that generated the trap.

Recovery  This message is intended for applications programs. No operator response is necessary.

Cause  The Trap Multiplexer received a warmStart trap. A warmStart trap is a standard SNMP trap signifying that the sending entity has reinitialized—most likely because of a routine restart—but its configuration will not change.

Effect  The effect is specific to the product that generated the trap.

Recovery  This message is intended for applications programs. No operator response is necessary.

Cause  The Trap Multiplexer received a linkDown trap. A linkDown trap is a standard SNMP trap signifying that the sending entity has experienced a failure in one of its communication links.

Effect  The effect is specific to the product that generated the trap.

Recovery  This message is intended for applications programs. The recovery actions required are specific to the product that generated the trap. Contact your local Simple Network Management Protocol (SNMP) site expert for assistance or advice on what tools might be used to identify the source and nature of the problem that caused the linkDown trap.

Cause  The Trap Multiplexer received a linkUp trap. A linkUp trap is a standard SNMP trap signifying that one of the sending entity’s communication links has become activated.

Effect  The effect is specific to the product that generated the trap.

Recovery  This message is intended for monitoring programs. No operator response is necessary.

Cause  The Trap Multiplexer received an authenticationFailure trap. An authenticationFailure trap is a standard SNMP trap signifying that the sending entity has received a request that failed authentication.

Effect  The effect is specific to the product that generated the trap.

Recovery  This message is intended for applications programs. The recovery actions required are specific to the product that generated the trap. Contact your local Simple Network Management Protocol (SNMP) site expert for assistance or advice on what tools might be used to identify the source and nature of the problem that caused the authenticationFailure trap.

Cause  The Trap Multiplexer received an egpNeighborLoss trap. An egpNeighborLoss trap is a standard SNMP trap signifying that the sending entity no longer has a peer relationship with an Exterior Gateway Protocol (EGP) neighbor.

Effect  The effect is specific to the product that generated the trap.

Recovery  This message is intended for applications programs. The recovery actions required are specific to the product that generated the trap. Contact your local Simple Network Management Protocol (SNMP) site expert for assistance or advice on what tools might be used to identify the source and nature of the problem that caused the egpNeighborLoss trap.

Cause  The Trap Multiplexer received an enterpriseSpecific trap. An enterpriseSpecific trap indicates that the sending entity has experienced some enterprise-defined event.

Effect  The effect is specific to the product that generated the trap.

Recovery  This message is intended for applications programs. The recovery actions required are specific to the product that generated the trap. Contact your local Simple Network Management Protocol (SNMP) site expert for assistance or advice on what tools might be used to identify the source and nature of the problem that caused the enterpiseSpecific trap.

Cause  The Trap Multiplexer process terminated normally. (Abnormal termination is reported by the operating system.)

Effect  The backup process of the NonStop process pair should take over. If recovery is successful, an event announcing the takeover is generated.

Recovery  Examine the event logs for related events. Often, Trap Multiplexer event message 103 is generated prior to this event; see the message contents for a description of the associated problem. Contact your local Simple Network Management (SNMP) site expert for assistance in determining the cause of the termination and, if necessary, restarting the Trap Multiplexer process. If the termination resulted from incorrect specification of the agent process name, rerun the Trap Multiplexer using the ‑a startup parameter to specify the proper name.

Cause  The Trap Multiplexer process has started.

Effect  The process is ready for service.

Recovery  Informational message only; no corrective action is needed.

Cause  The Trap Multiplexer encountered an I/O error. The cause is most likely the assignment of an incorrect agent process name at Trap Multiplexer startup or a stopped NonStop agent process.

Effect  The Trap Multiplexer cannot function. If the Trap Multiplexer was running as a process pair when the I/O error occurred, the backup process takes over. This new primary process tries to establish communication with the NonStop agent. If the process cannot establish communication, it retries every 10 minutes for a period of 1 hour, then stops.

Recovery  Investigate the reported error code and subcode, then correct the condition they describe.

For a description of the file‑system error, see Appendix B. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

Cause  The Trap Multiplexer process ran out of memory. The most likely cause is a problem of internal resource management.

Effect  This error may prevent a part of the Trap Multiplexer from functioning. The Trap Multiplexer might be able to correct the situation or might subsequently fail. In the latter case, additional events would be emitted.

Recovery  Try using another disk as a swap space. If the problem persists, 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 Trap Multiplexer process experienced an internal or logic error.

Effect  The Trap Multiplexer process might or might not be able to recover from the error. If the primary process cannot recover, its backup process should take over; if recovery is successful, an event announcing the takeover is generated. If the error is not recoverable and the Trap Multiplexer process terminates, additional events are generated.

Recovery  If the Trap Multiplexer primary and backup process cannot recover from the error, you can try restarting the subagent. Regardless of whether the Trap Multiplexer is able to recover, 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.