Preparing OpenManage Network Manager

Procedure

Before you modify OpenManage Network Manager:

1. Validate that OpenManage Network Manager is receiving SNMPv3 traps and SYSLOG messages from all network switches. If the SNMP traps are not displaying, verify that the switch configurations are correct.

2. Ensure that the current running configuration is committed and backed up to OpenManage Network Manager and then to a remote location outside the SU.

Note: If you are reluctant to make configuration changes to the network switches on your own, create a support request with Dell Technologies Support for assistance.

The following SNMP configuration lines are extracted from functional BMC and ToR switches configured with the Azure Stack Hub baseline 1910 Partner Toolkit - sample trap categories and user and group names are included:

Note: Not all snmp-server enable traps lines are required. Only include the trap categories that are required for your monitoring environment.

snmp-server enable traps bgp

snmp-server enable traps snmp authentication coldstart linkdown linkup syslog-reachable syslog-unreachable

snmp-server enable traps vrrp

snmp-server enable traps lacp

snmp-server enable traps entity

snmp-server enable traps stack

snmp-server enable traps stp

snmp-server enable traps ecfm

snmp-server enable traps vlt

snmp-server enable traps xstp

snmp-server enable traps isis

snmp-server enable traps config

snmp-server enable traps envmon cam-utilization fan supply temperature

snmp-server enable traps ecmp

snmp-server enable traps mac

snmp-server group AzureStack_RO 3 auth notify rview read rview

snmp-server host <DellEMC-MGMTVM IP address> traps version 3 auth azure_ro udp-port 162

snmp-server user azure_ro AzureStack_RO 3 encrypted auth sha deec6a166eb07f5b972caf6842a267ece0ec5122

snmp-server view rview 1 included

snmp-server trap-source Vlan 5

The following lines are extracted from a functional ToR switch:

snmp-server enable traps bgp

snmp-server enable traps snmp authentication coldstart linkdown linkup syslog-reachable syslog-unreachable

snmp-server enable traps vrrp

snmp-server enable traps lacp

snmp-server enable traps entity

snmp-server enable traps stp

snmp-server enable traps ecfm

snmp-server enable traps vlt

snmp-server enable traps fips

snmp-server enable traps ets

snmp-server enable traps xstp

snmp-server enable traps isis

snmp-server enable traps config

snmp-server enable traps pfc

snmp-server enable traps envmon cam-utilization fan supply temperature

snmp-server enable traps ecmp

snmp-server enable traps mac

snmp-server group AzureStack_RO 3 auth notify rview read rview

snmp-server host <DellEMC-MGMTVM IP address> vrf management traps version 3 auth azure_ro udp-port 162

snmp-server user azure_ro AzureStack_RO 3 encrypted auth sha d608944700a2e79311339887688d54cc42a0207a

snmp-server view rview 1 included

snmp-server vrf management

3. Validate that SYSLOG has been set up correctly.

The following lines are extracted from the SYSLOG configuration on the BMC switch:

logging <DellEMC-MGMTVM IP address>

logging source-interface Vlan 5

The following lines are extracted from the SYSLOG configuration on the ToR switches:

logging <DellEMC-MGMTVM IP address>

logging <DellEMC-MGMTVM IP address> vrf management

4. Test to ensure that traps are received in the OpenManage Network Manager console by performing a shut/no-shut on an interface on each switch.

Configuring OpenManage Network Manager alerts

Procedure

To configure OpenManage Network Manager to forward alerts northbound to SCOM:

1. In the OpenManage Network Manager management console, go to Automation/Actions.
2. To create an automation event processing rule, right-click anywhere in the Automation and Event Processing Rules table. From the menu, select New > Automation. In the Specify Rule Properties dialogue box, enter the rule name and description. Select Enabled, and then click Next.

Figure 21.          Specifying the OpenManage Network Manager event processing rule name

3. To add one or more Event Definition entities, under Filtering > Specify Event(s), click Add.
4. Select the event that you want to forward to SCOM. In the example in the following screenshot, all events of critical severity are forwarded:
   1. From the Max items returned list box, select 1500.
   2. Use the list boxes to select Severity and is and 6 – Critical, and then click Go.
   3. To forward critical alerts of any OID, click Add All, and then click Done.

Note: The events can include SNMP traps and SYSLOG messages from the switches.

Figure 22.          Creating event definition

5. To go to the Action tab, click Next. Click Add Action, and then select Forward Northbound.
   1. For Forwarded Message Type, select SNMPv2 Trap.

Note: The options in Forwarded Message Type include: SNMPv2 Trap, HTTP REST Call, and Syslog. SNMPv3 traps are sent from the network switches to OpenManage Network Manager, but those traps are forwarded to SCOM as SNMPv2.

2. For Destination Address, enter the SCOM management server IP address.
3. For Destination Port and Community String, enter the appropriate SNMP details that SCOM uses.
4. To get traps to display in SCOM, select Only forward variable bindings received in original trap payload (do not forward mined variable bindings) and Send Generic Message, and then click Apply.

Figure 23.          Creating northbound forwarding action

6. To complete the wizard, click Save.

Figure 24.          Completing the creation of the northbound forwarding action

The settings make a significant difference to the amount of data that is in the trap payloads that display in programs such as Wireshark. Even though the traps that are received from the switches are SNMPv3, there is no problem forwarding these alerts to SCOM as SNMPv2 traps. If you want to forward SYSLOG messages to SCOM, the same configuration can be used, that is, forward the SYSLOG messages as SNMPv2 traps.