Portal
Language
 
Home>Knowledge Base>Enabling SNMP on Windows Server 2008 R2
Information
Article ID70
Created On10/9/2010
Modified10/9/2010
Share With Others
Enabling SNMP on Windows Server 2008 R2
Enabling SNMP on Windows Server 2008 R2

Installing the Fusion-io Software

  1. Download and install the Windows Fusion-io ioDrive software from http://support.fusionio.com.
    • During installation, make sure Full Install is selected, or Custom with SNMP is selected.
    • After installation, the Fusion-io SNMP MIB fioIoDimm.mib is available in C:\Program Files\Fusion-io ioMemory VSL\SNMP.



  2. Before proceeding, make sure the ioDrive devices are attached. They should be visible in either ioManager or with fio-status from the command line.
    • Run ioManager from the desktop or through the Fusion-io program files group. There is one ioDrive visible in the following example.



  3. Go to Start > Run > Administrative Tools > Server Manager > Features (on left side) > Add Features. Enable SNMP Services by selecting it in the Add Features Wizard.



  4. Restart the computer so Windows will enable the extra tabs for the SNMP Service Properties dialog box.

Configuring SNMP Security

  1. Start up the Services management console by going to Start > Administrative Tools > Services. Find the SNMP Service in the list of services.
  2. Right-click on the SNMP Service and select Properties from the pop-up menu.
  3. Set up the SNMP service properties.
    • Add a community name such as public, and set the option to Accept SNMP packets from any host. Alternatively, add a specific IP address.
    • The community name must match the name used on the monitoring system.
    • Apply these settings.


Enabling SNMP Traps

Enter a community name and click Add to list.Then, add the host name or IP address of your monitoring system.


Note: The name trap_community is just an example. Use the community name required by your monitoring system.

Start Monitoring

Run your SNMP monitoring server to start collecting statistics and to listen for traps. See below for troubleshooting tips.

Troubleshooting

Problem:

The SNMP monitoring system does not detect any data.

Recommendations:

  1. Verify that the SNMP service is installed or configured properly. Check the instructions in this document for any missed steps.
  2. Verify TCP/IP access between the monitoring system and the system to be monitored. Communications can be interrupted by firewalls, switches, or other networking nodes in the path. The following steps demonstrate how to verify that the Fusion-io SNMP agent is installed and operating properly on the computer with the ioDrives installed.

    Go to http://net-snmp.sourceforge.net/download.html

    Download the Windows binaries. There is no need to do the full installation of the Net-SNMP service. Unselect it during installation. The rest of the Net-SNMP tools will be installed, including snmpwalk.

    Use snmpwalk to verify that the Fusion-io SNMP agent is operating properly.
    $ snmpwalk -c public -v 1 localhost .1.3.6.1.4.1.30018

    SNMPv2-SMI::enterprises.30018.1.1.1.0 = INTEGER: 1
    SNMPv2-SMI::enterprises.30018.1.1.2.0 = INTEGER: 12
    SNMPv2-SMI::enterprises.30018.1.1.3.0 = INTEGER: 2
    SNMPv2-SMI::enterprises.30018.1.2.1.1.1.1.4 = INTEGER: 4
    SNMPv2-SMI::enterprises.30018.1.2.1.1.1.1.5 = INTEGER: 5
    SNMPv2-SMI::enterprises.30018.1.2.1.1.1.2.4 = INTEGER: 2
    SNMPv2-SMI::enterprises.30018.1.2.1.1.1.2.5 = INTEGER: 2
    SNMPv2-SMI::enterprises.30018.1.2.1.1.1.3.4 = STRING: "Fusion-io ioDIMM3 160GB"
    SNMPv2-SMI::enterprises.30018.1.2.1.1.1.3.5 = STRING: "Fusion-io ioDIMM3 160GB"

    [. . .]

    This lists the OIDs that are part of the Fusion-io MIB and verifies that the Fusion-io SNMP agent is working locally on the server. The Fusion-io MIB contains a description of the OIDs and their meaning. It is located in C:\Program Files\Fusion-io ioMemory VSL\SNMP.

    snmpwalk can be run on other hosts, and even on the monitoring system itself. (When checking from other systems, the word localhost in the snmpwalk command must be changed to the correct host name or IP address.) By doing this, it is possible to isolate the problem to the network communication or not.

  3. Verify that the monitoring system is configured correctly. Try collecting data from other services and systems. Verify the community names and other parameters.

Problem:

Partial or truncated output from the SNMP service.

Recommendation:

Restart the Windows SNMP service. Also, check for networking problems.

Problem:

SNMP Service Properties window only has 4 tabs.

Solution:

Restart the computer.