Installing and Configuring SNMP for the Symantec Management Platform (SMP)
search cancel

Installing and Configuring SNMP for the Symantec Management Platform (SMP)

book

Article ID: 157452

calendar_today

Updated On:

Products

Monitor Solution

Issue/Introduction

This document provides instructions for installing and configuring the SNMP (Simple Network Management Protocol) service in a Windows environment for use with the SMP (Symantec Management Platform) Server to ensure that the service is running and sending/ receiving alerts within an environment.  The SNMP service is not installed or configured by default on Microsoft Windows operating systems. Before trying to install the SNMP service please verify if it is already installed.

SNMP alerts not showing up in console

Environment

ITMS 7.x, 8.x
Monitor Solution

Resolution

How to tell if SNMP is installed

  1. Click Start > Run > and  type “services.msc” and hit enter.
  2. Look for SNMP Services in the list.
  3. Note that SNMP Trap service may be installed. The "SNMP Trap" service is different than "SNMP Services" so be sure to select "SNMP Services".
Installation
 
NOTE: SNMP Service must be installed on both Clients and Servers for it to function correctly.
 
Review Microsoft documentation for the Operating System to install and configure the SNMP service
 
Configuration
There are many settings that affect the way SNMP is configured in an environment. Some settings are changed from the Windows operating system and  some of them are changed from the SMP Console. These settings are covered in detail below.
 
Windows Settings:
  1. Click Start > Run and type “services.msc” and hit enter.
  2. Look for SNMP Services in the list.
  3. Note that SNMP Trap service may be installed. The "SNMP Trap" service is different than "SNMP Services" so be sure to select "SNMP Services".
  4. Ensure that the SNMP Service status is started. If it is not started right click it and select "start".
  5. Ensure that the SNMP Trap status is stopped. If the status is started right click it and select "stop". The SNMP Trap service is a trap service for where Windows will collect all the SNMP traps. If the SNMP Trap service is enabled the SMP will not be able to properly collect the traps being sent. The SNMP Trap service on Windows interferes with the one that is automatically installed with SMP so please make sure it is turned off or the SNMP Alerts will not be sent correctly. Note steps 4 and 5 should be true for both client and server machines.
  6. Now make sure the SNMP service is pointing at the correct trap destination. This can be done by double clicking the SNMP Service in the Services window. Select Traps and Look at the IP address of the trap destination. Does this IP match that of the NS (Notification Server) or is it the IP of the machine to be receiving the SNMP alerts? This can be verified by logging on to the SNMP trap destination, starting a command prompt and entering ipconfig then recording the information that follows.
  7. If the correct IP address is not listed click Add enter the correct IP address and click Add. Then remove the old one by selecting it and clicking Remove.
SMP Settings:
  1. Once SNMP is configured to run properly in a Windows environment settings within the SMP (Symantec Management platform) Server should also be checked. The main basis of comparison for determining whether or not the SNMP alerts are coming in as desired will be in the Event Console within SMP. To access the Event Console go to Manage > Events and Alerts. Here all SNMP Alerts should be displayed. If a particular alert is not being recieved, double check the SNMP Service on the machine that is expected to alert.
  2. If the expected alert is still not present, check the following items: click Settings > All Settings > Monitoring and Alerting > Monitor > Remote Monitoring Server Settings. Under the General tab under SNMP, ensure that the community string is public ( or at least it is the same as the community string listed in the SNMP services under the Traps tab).
  3. Next Check the following: click Settings > All Settings > Monitoring and Alerting> Alert Rule Settings. Under the Discarding Rules tab, make sure there is no discarding rules affecting the particular machine or particular alert in question so that it is being deleted from the event console. Under the Forwarding Rules tab make sure that if alerts are being forwarded that they are configured properly according to the local environment.
  4. Next Check the following: click Settings > All Settings > Monitoring and Alerting > Event Console Purging Maintenance. Make sure that the purging policy here is appropriate and that it isn’t deleting the alerts from the event console before they may be viewed.
Powered by Wolken Software