Documentation for Intellect 4.11.0-4.11.3. Documentation for other versions of Intellect is available too.

Previous page Next page


You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

SNMP-service implements message conversion into SNMP format. SNMP-message is a sequence of parameters, describing the event. Parameter’s name is changed by the value of this parameter in the pattern of SNMP-message with the event registration. Changing the SNMP-message is done in the following way:

  1. Go to the settings panel of SNMP trap object.
  2. Enter in the field Message’s format string (%parameter’s name1%text% parameter’s name2%... parameters’names in the required sequence. Description of event’s main parameters is given in the table.

    Parameter’s name

    Description of parameter

    Availability in the message

    %event_action%

    Event, registered in the system

    Is determined by object’s type, for which the event may be registered

    %event_source_id%

    Object’s identification number, for which the event has been registered

    %event_source_type%

    Object’s type, for which the event has been registered

    %owner%

    Computer name, from which the message has been received

    Obligatory message’s parameters

    % time %

    Time of event’s creation

    %user_id%

    Computer’s user identification number,   from which the message has been received

    Optional message’s parameters

    %module%

    Module’s name, for which the event has been registered

    Note.

     In case when message’s format string is not set, SNMP message is formed in accordance with the pattern  %event_action%,%event_source_id%,%event_source_type%, %owner%,%user_id%,%module%.
  3. To save the changes click Apply button.

Changing the pattern of SNMP-message is completed.

Example of SNMP-message, formed in accordance with the pattern 1)%owner% 2)%module% 3)%time% 4)% event_source_id % 5)% event_source_type % 6)% user_id % 7)% event_action % is exemplified in the figure below.

  • No labels