SNMP Traps Overview
The NetWorker Simple Network Management Protocol (SNMP) Module (included with the NetWorker server package) allows NetWorker servers to send notification messages to SNMP management agents.
You must configure SNMP-enabled network management software to accept traps from the NetWorker server. For detailed information about SNMP management operations, see your network management documentation.
The NetWorker SNMP Module uses traps to communicate NetWorker event notifications to SNMP management stations. A trap is an unsolicited notification sent from the SNMP agent (the NetWorker server) to the SNMP event manager. When you configure the SNMP notification in NetWorker, you can define the types of traps that the NetWorker server sends to the SNMP event manager.
See the NetWorker Administration Guide for your NetWorker version for any changes to limitations and enhancements. The NetWorker Administration Guide is available through:
https://www.dell.com/support/home/product-support/product/networker/docs
Receive SNMP v2c traps on Linux.
To receive SNMP v2c traps on Linux, perform the following: Install the following packages:
- net-snmp-agent-libs
- net-snmp-libs
- net-snmp
1. Copy the MIB file for NetWorker located at the following location to the Linux trap receiver folder (/usr/share/snmp/mibs):
- Linux NetWorker server: /opt/nsr/snmp
- Symbolic Link can be used instead of copy: ln -s /opt/nsr/snmp/NETWORKER-MIB.txt /usr/share/snmp/mibs/NETWORKER-MIB.txt
- Windows NetWorker server: ..\Program Files\EMC NetWorker\nsr\snmp
2. Add the following to the snmptrapd.conf file:
authCommunity log,execute,net public
3. On the NetWorker server, specify the SNMP notification command (nsrtrap) in the NetWorker notifications or policy notification command field.
- For Linux: /usr/sbin/nsrtrap -c community_string traps_receiver_address
- For Windows: "C:\Program Files\EMC NetWorker\nsr\bin\nsrtrap.exe -c community_string traps_receiver_address"
- If -i version is not specified with the nsrtrap command, the default SNMP version is 2c.
- NetWorker: Notifications Overview: NetWorker: Notifications Overview.
- NetWorker: How to configure policy notifications: NetWorker: How To Configure Policy Email Notifications
4. On the Linux trap receiver, run the following commands to save the SNMP traps:
nohup snmptrapd -f -C -c ./snmptrapd.conf -Lf /var/log/snmptrap.log -M /usr/share/snmp/mibs -m NETWORKER-MIB &
NOTE: The nohup option ensures that the command runs even after the session is terminated. Use & to run the command in the background. The /var/log/snmptrap.log file is updated when traps are received. Another location of your choosing can be specified when running the above command.
Receive SNMP v2c traps on Windows.
To receive SNMP v2c traps on Windows, perform the following:
For SNMP Trap receiver:
- Install the iReasoning MIB browser.
- In the Address field, specify the IP of the NetWorker server.
- Select Tools > Trap Receiver > Trap Receiver Settings.
- Select UDP and port 162.
1. On the NetWorker server, specify the SNMP notification command (nsrtrap) in the NetWorker notifications or policy notification command field.
- For Linux: /usr/sbin/nsrtrap -c community_string traps_receiver_address
- For Windows: "C:\Program Files\EMC NetWorker\nsr\bin\nsrtrap.exe -c community_string traps_receiver_address"
- If -i version is not specified with the nsrtrap command, the default SNMP version is 2c.
- NetWorker: Notifications Overview: NetWorker: Notifications Overview.
- NetWorker: How to configure policy notifications: NetWorker: How To Configure Policy Email Notifications
2. Load the NetWorker MIB file located at the following location to the iReasoning MIB Browser using the Load MIBs option on the iReasoning MIB Browser.
- Linux NetWorker server: /opt/nsr/snmp
- Windows NetWorker server: C:\Program Files\EMC NetWorker\nsr\snmp
3. Go to iReasoning MIB Browser > Trap Receiver to review traps received.
Receive SNMP v3 traps on Linux.
To receive SNMP traps on Linux, perform the following: Install the following packages:
- net-snmp-agent-libs
- net-snmp-libs
- net-snmp
1. Copy the MIB file for NetWorker from the following paths to the Linux trap receiver directory (/usr/share/snmp/mibs).
- Linux NetWorker server: /opt/nsr/snmp
- Symbolic Link can be used instead of copy: ln -s /opt/nsr/snmp/NETWORKER-MIB.txt /usr/share/snmp/mibs/NETWORKER-MIB.txt
- Windows NetWorker server: C:\Program Files\EMC NetWorker\nsr\snmp
2. Provide the following information about the NMC > NetWorker admin console > NetWorker server properties > Security tab:
- Username
- Engine ID
- Authentication Protocol
- Authentication Key
- Privacy Protocol
- Privacy Key
NOTE: The above information should be the same as provided under the snmptrapd.conf file on the Linux Trap Receiver (mentioned in step 3).
3. Follow these steps on the Linux trap receiver:
a. Stop snmptrapd:
systemctl stop snmptrapd
b. Add the the following to the snmptrapd.conf file.
createUser -e <Engineid> <SNMPv3 username> <MD5/SHA> <password for authentication protocol> <AES/DES> <password for private protocol> authuser log <SNMPv3 username>
Example:
createUser -e 8000000001020304 myuser MD5 mypassword123 DES mypassword123 authuser log myuser
- EngineID should be a hexadecimal number from 10 to 64 characters.
- Username can have a maximum of up to 32 characters.
- The length of the passwords for both authentication protocol and private protocol should be in between 8-32 characters.
c. Start snmptrapd:
systemctl start snmptrapd
4. On the NetWorker server, specify the SNMP notification command (nsrtrap) in the NetWorker notifications or policy notification command field.
NOTE: SNMPv3 traps can only be configured at the NetWorker Policy level.
5. On the Linux trap receiver, run the following commands to save the SNMP traps:
nohup snmptrapd -f -C -c ./snmptrapd.conf -Lf /var/log/snmptrap.log -M /usr/share/snmp/mibs -m NETWORKER-MIB &
NOTE: The nohup option ensures that the command runs even after the session is terminated. Use & to run the command in the background. The /var/log/snmptrap.log file is updated when traps are received. Another location of your choosing can be specified when running the above command.
Receive SNMP v3 traps on Windows.
To receive SNMP traps on Windows, perform the following:
1. Install a licensed version of MG-Soft MIB browser.
2. Click View and select SNMP Protocol Preferences.
3. Select the SNMP protocol version as SNMP v3 USM.
4. Go to the Edit User option and add the following SNMP v3 security parameters:
- Security username: The name of the SNMP v3 user should be of the same value as provided in the NetWorker server properties under the Security tab.
- Context name: This is not mandatory and can be provided as any set of alphabetical characters.
- Context Engine ID: Specify the same Engine ID that is provided in NetWorker server properties under the Security tab.
- Authentication Protocol: Specify the authentication protocol as HMAC MD5 or HMAC-SHA.
- Private Protocol: Specify the private protocol as CBC-DES or CFB-AES.
5. Load the user profile after making the necessary entries for the attributes in Step 2.
6. Copy the MIB file for NetWorker from the following paths to the directory "C:\ProgramData\MG-SOFT\SMI Modules\MIB Modules\SMI"
- Linux NetWorker server: /opt/nsr/snmp
- Windows NetWorker server: C:\Program Files\EMC NetWorker\nsr\snmp
7. Load the MIB file to the MG-Soft MIB browser using the option Import MIB from the MIB tab. Keep the NetWorker MIB file at the location.
8. Go to the Remote SNMP Agent box on the upper left of the MG-Soft MIB browser. Provide the IP address of the NetWorker server from which the SNMP v3 traps are to be received.
9. On the MG-Soft MIB browser, go to Tools > Trap Ringer Console section.
10. On the NetWorker server, specify the SNMP notification command (nsrtrap) in the NetWorker notifications or policy notification command field.
NOTE: SNMPv3 traps can only be configured at the NetWorker Policy level.
NOTE: Configurations to system settings such as SNMP traps receiver cannot be performed by NetWorker support, system configurations and changes must be performed by the System Administrator.