316 MDS Orbit MCR/ECR Technical Manual MDS 05-6632A01, Rev. F
MDS-EVENT-MIB::mdsEventInfoInCee.0 = STRING:
"@cee:{\"host\":\"(none)\",\"pname\":\"loggingmgr\",\"time\":\"2014-04-
15T02:02:38.091753+00:00\",\"action\":\"login\",\"service\":\"ssh\",\"domain\":\"os\",\"o
bject\":\"session\",\"status\":\"success\",\"src_ipv4\":\"192.168.1.2\",\"src_port\":42135,\
"user_name\":\"admin\",\"event\":\"ssh_login\",\"profile\":\"http://gemds.com/cee_profil
e/1.0beta1.xsd\"}"
As can be seen above, the SNMP agent sent a v1 trap for “ssh_login” event
NOTE The following configuration are very similar to the WebUI Screens already presented. To save
space only the CLI version is presented.
Sending all system events as SNMP v2c traps
Following example shows how to configure the unit to send v2c traps for all the events in the system to a
specified SNMP target via the CLI command line:
Ensure version v2c is enabled. 1.
% set services snmp agent version v2c
Configure SNMP manager as a target that listens on port 5000, has IP address of 192.168.1.2, can 2.
receive v2c traps (tag “std_v2_trap”) with security name of “public”.
% set services snmp target TARGET-1-v2c ip 192.168.1.2
% set services snmp target TARGET-1-v2c port 5000
% set services snmp target TARGET-1-v2c tag std_v2_trap
% set services snmp target TARGET-1-v2c v2c sec-name public
Give the VACM group named “all-rights” (as configured in previous examples) notify access to 3.
“internet” view.
% set services snmp vacm group all-rights access any no-auth-no-priv notify-view internet
Commit configuration. 4.
% commit
To test above configuration, start an SNMP trap receiver (like “snmptrapd” with configuration file as
shown below) and generate “ssh_login” event by logging into the Orbit via SSH.
snmptrapd.conf:
engineID testing
snmpTrapdAddr 0.0.0.0:5000
authCommunity log,execute,net public
doNotFork yes
$ snmptrapd -M +./ -Lo -c snmptrapd.conf
NET-SNMP version 5.4.3
192.168.1.1 [UDP: [192.168.1.1]:161->[192.168.1.2]]: Trap ,
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (592863) 1:38:48.63,
SNMPv2-MIB::snmpTrapOID.0 = OID: MDS-EVENT-MIB::mdsEvent,
MDS-EVENT-MIB::mdsEventName.0 = STRING: "ssh_login",
MDS-EVENT-MIB::mdsEventInfoInCee.0 = STRING:
"@cee:{\"host\":\"(none)\",\"pname\":\"loggingmgr\",\"time\":\"2014-04-
15T01:34:26.373312+00:00\",\"action\":\"login\",\"service\":\"ssh\",\"domain\":\"os\",\"o
bject\":\"session\",\"status\":\"success\",\"src_ipv4\":\"192.168.1.2\",\"src_port\":42031,\
"user_name\":\"admin\",\"event\":\"ssh_login\",\"profile\":\"http://gemds.com/cee_profil
e/1.0beta1.xsd\"}"
As can be seen above, the SNMP agent sent a v2 trap for “ssh_login” event.