You are viewing the legacy RunMyJobs documentation site.
For RunMyJobs 2023.3 and later, go here and use the dropdown menu at upper right to switch to the desired version.

Sending SNMP Traps →

Integrating Redwood Server into your SNMP Landscape

Historically, SNMP was used to monitor network devices; this has evolved as monitoring applications and processes becomes more and more important. Using the existing infrastructure and internal knowledge allows many companies to save costs related to the implementation of an application-specific monitoring infrastructure. Redwood Server allows you to send SNMP traps to your network management stations. If your management software supports loading MIB files we suggest that you install these in the SNMP receiving software. How this is done is dependent on the management software.

SNMP integration requires the SNMP module, please check your license key to make sure you have the Module.SNMP license key.

Network monitoring solutions retrieve the settings from MIB files to be able to communicate with devices and applications. The MIB file is a text file which contains information on the device or application and how to communicate with it. Redwood Server offers a MIB file which contains the definition of a trap. The standard MIB file complies with the standards and should easily be imported into network management system. You can edit this file, however, Redwood strongly recommends you pay great attention when editing this file, as the MIB file must comply with syntax requirements.

The process definition System_SNMP_SendTrap can be submitted within any RedwoodScript process or chain to send a trap to the SNMP monitor. Also, by using events or chains, you can send such logical events within Redwood Server to the management software (for example, if an important process fails). It has two parameters, TRAPID and TRAPDATA, they can contain virtually any number or string that suit your corporate guidelines for your network management solution. Usually, customers use a fixed trap ID and a variable message, containing information about which process failed. Note that you can use Redwood Expression Language to generate dynamic parameter values.

There are many different network management solutions, in the following example, we use HP OpenView; see the manual for your management software.

Example

Configuring HP OpenView

  1. In Redwood Server, navigate to "Configuration > Software".
  2. Download the redwood-mib.mib file.
  3. In HP OpenView, navigate to [Options] > [Load/Unload MIB: SNMP] > [Load] and choose the redwood-mib.mib file. When you are asked to load the definitions in the event system, choose OK. Now the Management Information Base is known to HP OpenView NNM, and traps from the process server can be received.
  4. Navigate to [Options] > [Event configuration]. There you will see "RedwoodTraps" in the Enterprises view. When you choose that line, you will see more specific information in the events view. Only one event is specified: userTrap. This event is raised when you use the System_SNMP_SendTrap in Redwood Server. Choose the line to view the details of the UserTrap event.
  5. In [Event Message] choose what you want to do with the trap. For example, choose the monitor where you want to log all the process server traps (for example Application Alert Events ). Also, as an event log message you can give the following 2 specific messages:
  6. $1 gives the TRAPID parameter of System_SNMP_SendTrap (for example the ID).
  7. $2 gives the TRAPDATA parameter, the message that you specified.
  8. On the [Actions] tab you can specify the message ($2) to be displayed in a pop-up window that is shown as soon as the trap is received. An example is: net send <host> $2.

See Also

Sending SNMP Traps →