How to configure SNMP Notifications

Ops Center Protector User Guide

Version

7.9.x

Audience

anonymous

Part Number

MK-99PRT002-10

ft:lastEdition

2024-12-11

Protector supports SNMPv2c & SNMPv3 and sends Notification ‘TRAPS’ based on the following events:

Notification	Description
Logs	Generated by: Message, Category, Log Id, Actioned by ‘node’, level
Pool Monitoring	Generated by: Ser No., Pool Id, Pool Name, Pool Type, Pool Capacity
Journal Monitoring	Generated by: Ser No., Journal Id, Policy, Journal Capacity
HUR Monitoring	Generated by: Ser No., Policy, Source, Dest, HUR Network Latency
Custom	Generated by: Postgres SQL query

Figure. SNMP Viewer - Generating Notification

Notifications are generated on the Protector Master node (The Agent) and captured by an SNMP viewer (The Manager).

Protector is shipped with its own MIB file which will be required by the SNMP Manager to interpret the OIDs (Object Identifiers).

To configure Protector to send SNMP traps, the following steps need to be carried out:

Configure the Protector UI

Specify Name:

From the LHS pane select ‘Notifications’ and then a name:

Figure. Notification - Create Notification

Specify Notification criteria:

Now, in the Notification Criteria, select where it will come from and then fill in the required field(s).

Figure. Notification - Specify Notification Criteria

Select Notification Options:

Finally, select the SNMP version, which can be either SNMPv2c/SNMPv3 or both. Once done, click Finish.

Figure. Notification - Select Notification Options

Edit the Protector configuration files

On the Master host, there are two files that need to be edited to complete the SNMP configuration, dependent on the version of SNMP required.

SNMPv2

In an editor open db/config/ notification/snmpv2c.cfg
Edit the appropriate HandlerExecutable section by inserting the desired values for the flags

Flag	Options
-c	community string default = public
-trap_host	The DNS/IP of the SNMP Manager (Trap host)
-trap_port	The port that the SNMP Manager will listen on

SNMPv3

In an editor open db/config/ notification/snmpv3.cfg
Edit the appropriate HandlerExecutable section by inserting the desired values for the flags

Flag	Options
-a	authentication protocol (MD5\|SHA\|SHA-224\|SHA-256\|SHA-384\|SHA-512), default:SHA
-A	authentication protocol pass phrase, default:mypassword
-x	privacy protocol (DES\|AES), default:AES
-X	privacy protocol pass phrase, default:mypassword
-l	security level (noAuthNoPriv\|authNoPriv\|authPriv), default: authPriv
-u	security name, default:traptest
-trap_host	The DNS/IP of the SNMP Manager (Trap host)
-trap_port	The port that the SNMP Manager will listen on default:162

For more information see: http://www.net-snmp.org/

Firewall configuration

The firewall on the Protector Master must to be opened to allow data on port 162 through

Restart the Protector services

The services on the Protector Master need to be restarted each time the files snmpv2c.cfg and/or snmpv3.cfg are modified.

Copy the MIB file

Locate the Protector MIB which will be here: db/mibs/ HITACHI-Protector-MIB.txt and copy it to the SNMP Manager.

Protector agent files

Protector is an SNMP agent, and these are the files associated with the notification traps: