Windows SNMP Service has missing tabs

So by now, you have gone though the process of installing the Windows SNMP Service  but when trying to configure, you realize that there are missing tabs!

2019-04-19 08_34_56-Window

This is a relatively simple but obnoxious change that seems to have changed from previous Windows versions and 2016.

To fix this, simply run the following command from a Windows Command prompt:

> Dism /online /enable-feature /featurename:Server-RSAT-SNMP /ALL

2019-04-23 16_06_55-Screen clipping taken_ 4_19_2019 9_10 AM - OneNote

This will install the complete features for the SNMP service and in the end will give you the familiar looking screen with all the tabs.

2019-04-19 14_15_34-Window

Install and configure SNMP in Windows

In order to configure a Windows Server for Monitoring (Discovery / Inventory and Alert Processing), first we have to install the SNMP service.

By default, it is turned off or not installed on most operating systems.

Installation Instructions for the Windows SNMP Service

  1. Open Server Manager
  2. Click on Add Roles and Features
    2019-04-19 13_47_02-Window
  3. Click Next (this will be a summary page)
  4. Click Next (by default, Role-based or feature-based installation
  5. Click Next (by default, it will select the server you are running the wizard on)
    2019-04-19 13_50_16-Window
  6. Click next on the Roles wizard (we are not installing a role)
  7.  Under Features, expand “Remote Server Administration tools  > Feature Administration Tools ” and select “SNMP Tools” then click Next
    2019-04-19 13_53_33-Window
  8. Click Install on the “Confirm installation selections “
  9. Click Close on the “Installation Progress”

The installation will take a couple of minutes to complete. After this, the SNMP service will be visible on the Services console.

2019-04-19 14_00_27-Window

Alternatively, you can also install the SNMP Service using Windows PowerShell:

Get-WindowsFeature SNMP-Service

 

Configuration instructions for the Windows SNMP Service

To configure the Windows SNMP service for SNMPv1/v2, there are two main tabs we will focus on. These are “Security” and “Traps”.

Security is to configure the SNMP agent, while, as the name states, Traps is to configure the SNMP destination for SNMP generated traps.

  1. Start by configuring the agent. First, click on Security and enter the community string under “Accepted Community Names”. In most instances, a “Read-Only” rights configuration will suffice.
  2. If this will be your host using for monitoring, select  “Accept SNMP packets from any  host”. Otherwise, specify which hosts to accept SNMP packets from.
    2019-04-19 14_15_34-Window
  3. Next, is configuring the trap destination. This configuration is done under Traps.  You will need to enter the community string and a destination IP (or DNS name) to where any generated alerts will be sent to.
    2019-04-19 14_18_10-Window

Once the above steps are completed, click OK. Then, right click on the SNMP service and click restart for settings to take effect.

At this point, you should be able to go to your Management Station (Monitoring Utility or Software) and inventory and monitor this Windows Server by providing the SNMP agent community String.

SNMP in terms of System Management

The Simple Network Management Protocol (SNMP for short) has two aspects.

One, is as an agent, which allows the device that is running SNMP to be discovered and inventoried by a Monitoring Agent. (Port 161)

The second, allows to send traps to a Monitoring Agent via port 162.

For our purposes, we won’t go into all the specifics of SNMP, just that it can be used by a Monitoring Software for discovery/ inventory and alert processing. More specifics can be found here:

https://en.wikipedia.org/wiki/Simple_Network_Management_Protocol 

That being said, here are some pieces of how SNMP can be leveraged in multi-operating system environments:

How to Configure SNMP on ESX 5.x and 6.x

Looking at a ESX SSH CLI prompt can be a bit daunting for us folk who grew up with “Windows GUI’s”. One problem that I’ve often ran into in ESX monitoring from Third party utilities, is that the documentation and even terminology can be a bit confusing.

This is a simple straightforward way of configuring SNMP and trap forwarding to a Third Party monitoring utility.

Enable SSH in the ESX Host

  • In Vcenter, select your host. 
  • Once the host is selected, click on the Configure tab
  • Click Security Profile on the left menu
  • Scroll down to Services and click Edit

2019-04-12 00_36_23-vSphere Web Client

SNMP Configuration:

  1. First check if SNMP is already configured:
    #esxcli system snmp get

    2019-04-12 00_50_31-How To_ Configure SNMP on ESX - OneNote
  2. If SNMP is not configured most settings will show blank. We will start  by setting the community name (in this example we use public).
    Note: SNMP community strings are case sensitive 
    #  esxcli system snmp set -c public
  3. Configure the SNMP Agent to Send SNMP v1 or v2c Traps to your monitoring agent’s host IP using the following command:  esxcli system snmp set –targets target_address@port/community.
    Note: SNMP traps by default are sent on port 162
  4. # esxcli system snmp set -t 10.0.157.180@162/public
  5. Enable the SNMP service on the ESX host
    # esxcli system snmp set --enable true
  6. Verify SNMP is configured correctly via the GET command
    # esxcli system snmp get
    2019-04-12 00_54_13-How To_ Configure SNMP on ESX - OneNote
  7. Finally, end a test trap from your ESX host to the monitoring agent host
    #  esxcli system snmp test

    2019-04-12 00_56_01-How To_ Configure SNMP on ESX - OneNote

At this point, you should be able to go to your monitoring agent software and check that the test trap is received. 

Our next article will show how to configure and test a SNMPv3 trap. Stay tuned!

Reference: https://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.monitoring.doc/GUID-EA64297A-35FD-4226-A1B2-367C57D38CBD.html