Sending All System Events As Snmp V2C Informs; Sending All System Events As Snmp V3 Informs - GE MDS ORBIT MCR Technical Manual

Sending all system events as SNMP v2c informs

An SNMP inform is an acknowledged trap. Following example shows how to configure the unit to send
v2c informs for all the events in the system to a specified SNMP target:
1. Ensure version v2c is enabled.
% set services snmp agent version v2c
2. Configure SNMP manager as a target that listens on port 5000, has IP address of 192.168.1.2, can
receive v2c informs (tag "std_v2_inform") with security name of "public", with retry timeout of 15
seconds (timeout parameter is in units of 0.01 seconds) and max number of retries of 3.
% 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_inform
% set services snmp target TARGET-1-v2c v2c sec-name public
% set services snmp target TARGET-1-v2c timeout 1500
% set services snmp target TARGET-1-v2c retries 3
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
4. Commit configuration.
% 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
2014-04-22 16:02:17 192.168.1.1 [UDP: [192.168.1.1]:161->[192.168.1.2]]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (271741) 0:45:17.41
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-
15T04:25:53.677885+00:00\",\"action\":\"login\",\"service\":\"ssh\",\"domain\":\"os\",\"o
bject\":\"session\",\"status\":\"success\",\"src_ipv4\":\"192.168.1.2\",\"src_port\":42694,\
"user_name\":\"admin\",\"event\":\"ssh_login\",\"profile\":\"http://gemds.com/cee_profil
e/1.0beta1.xsd\"}"

Sending all system events as SNMP v3 informs

Following example shows how to configure the unit to send v3 informs for all the events in the system to
a specified SNMP target via the CLI command line:
1. Ensure version v3 is enabled.
% set services snmp agent version v3
Create a remote user named "RemUser1" with engine-id of SNMP inform receiver
2.
(80:00:1f:88:04:74:65:73:74:69:6e:67) and SHA1 authentication with password "sha1Password"
and AES encryption with password "aesPassword".
318 MDS Orbit MCR/ECR Technical Manual MDS 05-6632A01, Rev. F