Events & Alarms
Sending Event and Alarm traps to an SNMP Trap Daemon is an optional feature of the applications running
n2svcd framework. This feature is disabled by default, but can be enabled by adding
<snmp> element to the
n2svcd.xml configuration file directly within the
<?xml version="1.0" encoding="utf-8"?> <n2svcd> <snmp enabled="1" host="localhost"/>
Some parameters may be modified. Refer to the n2svcd Configuration section for details.
When enabled by configuration, the
n2svcd applications will each send SNMPv2c
traps to the configured address/port using UDP.
The N-Squared Trap MIB definitions are available here:
They are defined underneath the N-Squared Enterprise number 56540.
The recommended deployment for SNMP with
n2svcd is the following:
snmptrapdLinux component is run local to listen on the localhost
n2svcdapplications are configured to deliver via UDP to the local
snmptrapdwill aggregate all individual traps into a single stream.
- The “forward” feature of
snmptrapdis used to securely relay these traps to an external sink.
The specific configuration of
snmptrapd will depend on the nature of the security
required for the off-platform relay. Refer to the
MIUB Object IDs
The N-Squared enterprise-specific OIDs are:
Event & Alarm
MANDATORY: This will always use the 8-byte GMT encoding.
Seconds are rounded down to the earlier decisecond.
MANDATORY: The name of the n2svcd application which was “in control” at generation time.
This is the name as configured in the
When an application is repeated, this will include the repeat number, e.g. “Logic:2”.
MANDATORY: The module class of the software file which generated the trap.
OPTIONAL: A label identifying the affected object/connection/resource.
The affected object may be the source object, but not always.
When present, this is also used to correlate ALARM and CLEAR pairs.
The message string.
The Event/Alarm ID is in format
YY are two-character
alphanumerics which together indicate the originating module, and
NNNNN is a unique
five-digit number (with possible leading zeros) that uniquely identifies the nature of
the event or alarm.
XX-YY-NNNNN event/alarm ID can be used in the on-line searchable Alarm Guide to
find the associated event/alarm description, parameter description, and recommended
- [-2] WARNING
-  NOTICE
- [-3] ALARM
- [-1] CLEAR
Debugging traces are never written to SNMP.