Click to Rate and Give Feedback
TechNet
TechNet Library
TechNet Archive
SMS 2.0
 Translating SNMP Traps

  Switch on low bandwidth view
Translating SNMP Traps
Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

You can use Systems Management Server (SMS) to translate Windows NT events into Simple Network Management Protocol (SNMP) traps. SNMP is the network management protocol of TCP/IP, which you can use to monitor the activity of various Windows NT resources on your network. Control information about each resource is maintained in a structure known as an SNMP trap, which is reported to the SMS Administrator console using the Event to Trap Translator.

The Event to Trap Translator converts selected Windows NT events from the Windows NT event logs to SNMP traps and sends them to the designated trap receiver. The traps must be sent to network management consoles other than the SMS Administrator console.

Related Topics 

Start the Event to Trap Translator 

Configure Clients to Translate Events to SNMP Traps 

About SNMP Traps 

Remote Configuration Tool 

Event to Trap Translator Overview 

Event to Trap Translator Overview

Use the Event to Trap Translator for configuring events on Windows NT clients to translate to SNMP trap. You can browse for all the possible events that can be translated to SNMP traps on a client, and you can easily add or remove events from a client configuration. Also, you can use this tool to configure clients individually. The Event to Trap Translator gives you the option to configure one client and then export that configuration to a text file. You can then use this text file with the Remote Configuration Tool, in a package, to automatically configure many clients with the same configuration.

Specified events are translated only while the SNMP service is running (the Event to Trap Translator runs as part of this service). However, if the computer running the Event to Trap Translator is restarted, the Event to Trap Translator also restarts. After restart, the Event to Trap Translator looks at the event log to see if any new specified events have occurred between the time the computer restarted and the Event to Trap Translator restarted. If so, the Event to Trap Translator translates these events.

Added events persist between invocations of the Event to Trap Translator; once added, they remain in the configuration registry until you remove them.

Note The SNMP service must be stopped and restarted on a client after the Event to Trap Translator is installed, or the Event to Trap Translator will not function. The first time the Event to Trap Translator is started, no events are listed because none have been specified.

Related Topics 

Configure Clients to Translate Events to SNMP Traps 

Remotely Modify the Client Configuration for SNMP 

Start the Event to Trap Translator 

Specify Client Events to Translate to SNMP Traps 

Remove an Event Being Translated into SNMP Traps 

Modify Event Properties 

Specify Trap Settings for Events 

Export an Event Configuration 

Search for Events to Translate to SNMP Traps 

About the Event to Trap Translator Window 

About Custom Events 

Translating SNMP Traps Overview 

Start the Event to Trap Translator

Note The Event to Trap Translator requires read/write access to the Windows NT Registry, so you must have administrative privileges on the client before you can configure events on that computer.

  1. In the SMS Administrator console, navigate to Collections.

  2. Right-click any Windows NT resource, point to All Tasks, and then click Start Event to Trap Translator.

Related Topics 

Search for Events to Translate to SNMP Traps 

Remove an Event Being Translated into SNMP Traps 

Event to Trap Translator Overview 

Specify Client Events to Translate to SNMP Traps

After an event is added, it remains in the event configuration until you remove it.

Note The Event to Trap Translator requires read/write access to the Windows NT Registry, so you must have administrative privileges on the client before you can configure events on that computer.

  1. In the Event to Trap Translator window, click Edit.

    The window expands to display event source selection folders and additional buttons. 

  2. In the Event Sources column in the lower left of the window, double-click a category folder to display folders of event sources.

    A source is the software that logged the event, which can be an application, a component of an application, or a component of the operating system. 

  3. Double-click a folder of event sources to display all the events for that source in the Events column.

  4. In the Event ID field, select the event.

  5. Click Add to add the event to the configuration registry.

  6. In the Properties dialog box for the selected event, click OK.

    The event is added to the list of events to be translated to Simple Network Management Protocol (SNMP) traps. This list is located at the top of the Event to Trap Translator window. 

Related Topics 

Search for Events to Translate to SNMP Traps 

Remove an Event Being Translated into SNMP Traps 

Event to Trap Translator Overview 

Search for Events to Translate to SNMP Traps

In the Event to Trap Translator window, you can search for specific events that you want to configure for translation to Simple Network Management Protocol (SNMP) traps.

  1. In the Event to Trap Translator window, click Edit.

    The Event to Trap Translator window expands to display event source selection folders and additional buttons. 

  2. Click Find to open the Find dialog box, in which you can specify the search text and other settings.

  3. Click Find Next.

    Any found text is selected in the columns in the lower half of the Event to Trap Translator window. 

  4. Click Find Next again to find the next occurrence of the text, or click Cancel to close the Find Event dialog box.

Related Topics 

Specify Client Events to Translate to SNMP Traps 

Remove an Event Being Translated into SNMP Traps 

Event to Trap Translator Overview 

Remove an Event Being Translated into SNMP Traps

Added events persist between invocations of the Event to Trap Translator. Once they are added, these events remain in the event configuration until you remove them.

Note The Event to Trap Translator requires read/write access to the Windows NT Registry, so you must have administrative privileges on the client before you can configure events on that computer.

  1. In the Event to Trap Translator window, click Edit to expand the window.

  2. Select the event to be removed and click Remove.

Related Topics 

Specify Client Events to Translate to SNMP Traps 

Search for Events to Translate to SNMP Traps 

Event to Trap Translator Overview 

Modify Event Properties

You can limit when a particular Windows NT event is translated into a Simple Network Management Protocol (SNMP) trap by generating traps only when the frequency of a Windows NT event causes concern. For example, you can generate an SNMP trap for logon failures if three failures occur within 60 seconds. (In this case, only one trap is generated, not three.)

  1. In the Event to Trap Translator window, select the event.

  2. Click Properties.

  3. In the Properties dialog box for the selected event, complete the following settings to specify the event properties:

    Generate Trap If Event Count Reaches count  

    Specify how many times this event must occur before the SNMP trap is generated.

    Generate Trap Within Time Interval time  

    Select to specify that the number of events in Generate Trap If Event Count Reaches count must occur within a finite period of time. In the number box, type the number of seconds.

  4. Click OK.

Note The Properties dialog box also displays the specific ID for the trap. You use the specific ID to configure a trap filter for traps generated from this event.

Related Topics 

About the Event to Trap Translator Window 

Event to Trap Translator Overview 

Export an Event Configuration

You can use the Event to Trap Translator to export an event configuration to a file. You can save an event configuration as a text file (.txt) for import to consoles or as a configuration file (.cnf) for use in SMS advertisements.

  1. In the Event to Trap Translator window, select the events.

  2. Click Export.

  3. In the Export Events dialog box, specify the file name and file type.

  4. Click OK.

Related Topics 

Event to Trap Translator Overview 

Configure Clients to Translate Events to SNMP Traps

For the Event to Trap Translator to operate successfully, you must make sure that these operations have been performed:

  • Install the TCP/IP Protocol stack on every computer from which or to which you want to receive or send traps. (The TCP/IP Protocol stack is installed from Network in Control Panel.) When installing the TCP/IP Protocol stack, make sure the SNMP Service is enabled so that the Windows NT-based client can send and receive traps.

  • Configure the SNMP Service to use the appropriate Simple Network Management Protocol (SNMP) community, and ensure that the address (or addresses) to which SNMP traps will be forwarded is also specified. The community name is part of the SNMP packet when the trap is sent, and it is used for authentication.

    Note Once the SNMP Service is installed and running, you must reapply any service pack that is being used. However, do not use Service Pack 2 for Windows NT 4.0. The SNMP Service will not work with this service pack. 

  • Verify that the client software is installed and then configure the Event to Trap Translator Client Agent.

Events can be translated to SNMP traps on computers running Windows NT versions 3.51 and later.

Once clients are configured to translate events to SNMP traps, you can use the Event to Trap Translator to configure which events are translated to SNMP traps. You can configure each client individually, or you can configure one client and then export the configuration to a text file that you can use with the Remote Configuration Tool (Eventcmt.exe), in a package, to automatically configure many clients.

Related Topics 

Install the SNMP Service on Windows NT Version 3.51 

Install the SNMP Service on Windows NT Version 4 

Install the SNMP Service on Windows NT Version 5 

Configure the SNMP Service on Windows NT Version 3.51 

Configure the SNMP Service on Windows NT Version 4 

Configure the SNMP Service on Windows NT Version 5 

Event to Trap Translator Overview 

Remotely Modify the Client Configuration for SNMP

SMS provides the Remote Configuration Tool (Eventcmt.exe), to automatically configure which events are translated to SNMP traps. You can use this tool together with a package to distribute the desired configuration to selected clients. To use this tool you must first create a text file which includes the desired client configuration. This procedure walks you through this process using the Event to Trap Translator.

  1. Select a client to configure and start the Event to Trap Translator.

  2. Use the settings in the Event to Trap Translator window to add or remove events to be translated to SNMP traps.

  3. When the configuration for this client is complete, click Export.

  4. In the Export Events dialog box, specify the file name, file type, and location.

  5. Click OK.

  6. Distribute this configuration file together with the Remote Configuration Tool to clients remotely using the SMS software distribution process.

Related Topics 

Search for Events to Translate to SNMP Traps 

Remove an Event Being Translated into SNMP Traps 

Event to Trap Translator Overview 

Cc723625.spacer(en-us,TechNet.10).gif

© 2009 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Page view tracker