GE MDS ORBIT ECR - Configuring the SNMP Agent to Send Notifications (Traps;Informs); Sending All System Events as SNMP V1 Traps

MDS 05-6632A01, Rev. F MDS Orbit MCR/ECR Technical Manual 313
Click “Save” on the Web UI.
Via the CLI using the following commands:
% commit
The snmpwalk tool can be used test above configuration:
$ snmpwalk -M +./ -v3 -u User1 -a sha -A sha1Password -x aes -X aesPaasword -l authpriv
192.168.1.1 internet
SNMPv2-MIB::sysDescr.0 = STRING: GE MDS Orbit SNMP Agent
SNMPv2-MIB::sysObjectID.0 = OID: MDS-ORBIT-SMI-MIB::mdsOrbit
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (6128338) 17:01:23.38
SNMPv2-MIB::sysContact.0 = STRING:
SNMPv2-MIB::sysName.0 = STRING:
SNMPv2-MIB::sysLocation.0 = STRING:
SNMPv2-MIB::sysServices.0 = INTEGER: 72
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
Configuring the SNMP agent to send notifications (traps/informs)
The SNMP notification table is preloaded with following entries:
Each entry above specifies a SNMP notify name (e.g. std_v1_trap), the tag (e.g. std_v1_trap) and the type
of notification (trap or inform). The notify and tag names are kept the same for ease of configuration of
SNMP targets. The SNMP notify name is used to lookup up the tag (in notify table) that in turns is used
to look up all the SNMP targets (in target table) to which the SNMP notification needs to be sent.
Each event in the Orbit system can be configured to send an SNMP notification (trap/inform). By default,
all events are configured to send SNMP notification with SNMP notify name of “” (empty string). This
selects all tags in the notify table and attempts to lookup the targets that have been configured for these
tags. The user can also configure the SNMP notify name to be used for each event.
Sending all system events as SNMP v1 traps
Following example shows how to configure the unit to send v1 traps for all the events in the system to a
specified SNMP target:
Ensure version v1 is enabled. 1.