When you configure SCOM to receive SNMP traps from OpenManage Enterprise and OpenManage Network Manager, there are several options. Some customers may already have set up SCOM as an SNMP receiver to accommodate downstream monitoring tools and devices. The method that is described in this section is based on the Kevin Holman blog post . Dell Technologies labs followed the steps in this blog post, and we have documented the steps for reference and comparison with your SCOM environment.
Note: Before you do the steps that are described in this section, complete a full backup of the SCOM environment. User either traditional backup and recovery tools or snapshot technology on a virtualized platform. You may also prefer to contact Microsoft Support for help with setting up SCOM as an SNMP trap receiver.
Verify that all necessary firewall rules have been enabled on the SCOM management server to receive SNMP traps. Test SNMP communications with target servers, if necessary. The following screenshots show the inbound and outbound rules that are required for this purpose:
If the rules are incorrectly configured, you see SNMP traps reaching the SCOM management server from OpenManage Enterprise and OpenManage Network Manager through a utility, such as Wireshark. You do not see those traps displayed in the SCOM console monitoring view.
Note: To adhere to your corporate monitoring standards, you must modify the sample Management Pack. We used the default Management Pack in the Dell Technologies lab for testing purposes only. The figures in the following sections reflect the use of the default Management Pack:
To prepare the CSV file, after you download the networklist.csv file from TechNet:
Note: To determine the community string of the SCOM environment stated in Base64, follow the instructions in the blog post. In the Dell Technologies lab, we used the cs3commst1ng community string when translating to Base64.
In the Dell Technologies lab, we created a share that is named CSV, on a central file server, and granted everyone read permission to the share.
To import Management Pack into SCOM:
The following screenshot shows that Management Pack is already imported:
Note: It can take a while for the Management Pack to appear in the SCOM management server. Ensure that the Management Pack is visible under Administration > Management Packs > Installed Management Packs, as shown in the following figure, before proceeding with the next step:
Management Pack creates an object discovery in SCOM that you must customize.
To create an object discovery override:
In the test environment, we used the default object Demo SNMP Device Class Discovery.
To configure the resource pool:
In the test environment, we created Demo SNMP Device Resource Pool.
In our example, the SCOM management server should be the only visible pool member.
Management Pack has created a monitoring view. In the test environment, we named the monitoring view Demo SNMP Devices. Under Demo SNMP Devices, we named the state view SNMP Devices, which contains the contents of the CSV file that we prepared previously.
Note: You might need to refresh the SNMP Devices view to see the list of servers.
SCOM is ready to receive SNMP traps from OpenManage Enterprise and OpenManage Network Manager.