EMS Manual

EMS Programs
EMS Manual—426909-005
13-51
Translating an EMS Event Into an SNMP Trap
Effect. The distributor fails to start up.
Recovery. Specify no more than 10 source collectors.
Cause. More than the maximum allowable (10) TEXTOUT destinations have been
specified.
Effect. The distributor fails to start up.
Recovery. Specify no more than 10 TEXTOUT destinations.
Cause. An incorrect distributor type is specified.
Effect. The distributor fails to start up.
Recovery. Specify a valid distributor type.
Translating an EMS Event Into an SNMP Trap
When a NonStop SNMP (Simple Network Management Protocol) agent is provided as
a routing destination, EMSDIST can translate each event into an SNMP trap and send
the trap to the NonStop SNMP agent for routing to manager stations configured to
receive them. An example of this general procedure is:
1. Install and configure the NonStop agent and the EMS trap subagent.
2. Create a compiled filter that sets up the routing ID and identifies the events to
translate into SNMP traps.
3. From TACL, load any DDL definition used by the filter, and compile the filter with
EMF.
4. With the NonStop agent running, start the EMSDIST program.
EMSDIST automatically translates the EMS event into an SNMP trap when the
destination is an SNMP agent process.
If no trap appears on the management console and the error “SNMP BAD-IPC-PDU-
RCVD events” (SMP event number 9) appears in the NonStop Kernel event log, the
problem is probably due to incorrect installation of the ZSMPTMPL template file that
comes with the agent.
For detailed instructions about translating an EMS event into an SNMP trap, see the
SNMP Configuration and Management Manual.
Too many textout devices
Use C[ONSUMER], F[ORWARDING], or P[RINTING]