$('a[name]').remove(); $('#ic-homepage__footer').before('

'); $("#tabs").tabs({ selected: 1 }); $("#ic-homepage__ic-tips").append( quickTipHTML() ); unhideOneProductTip(); $("#ic-homepage__product-tips").wrapInner('

'); $("#ic-homepage__feed-tips").wrapInner('

'); });

IBM Tivoli Monitoring > Version 6.3 > User's Guides > Agent Builder User's Guide IBM Tivoli Monitoring, Version 6.3

Monitor events from a Simple Network Management Protocol event sender

Define a data source to collect SNMP event data.


Simple Network Management Protocol (SNMP) V1, V2C (note that this version name is V2C and not just V2), and V3 are supported by IBM Tivoli Monitoring agents. SNMP Traps and Informs can be received and processed by the agent. Data that is received by this provider is passed to Tivoli Monitoring as events.

For more information about the attribute groups for SNMP events, see (SNMP Event attribute groups).


Procedure

  1. On the Agent Initial Data Source page or the Data Source Location page (Figure 1), click Data from a server in the Monitoring Data Categories area.

    Figure 1. Adding SNMP events

  2. In the Data Sources area, click SNMP Events.

  3. Click Next.

  4. In the Simple Network Management Protocol Event Information window (Figure 2), do one of the following steps:

    Figure 2. Simple Network Management Protocol Event Information window

    • Click All Events to create an attribute group that sends an event for any received SNMP event.

    • Click Generic Events to create an attribute group that sends an event for any received generic SNMP event that matches any of the selected generic event types.

    • Click Custom Events to create one or more attribute groups that send events for enterprise-specific SNMP events. Click Browse to choose the events to be monitored.

      In the Simple Network Management Protocol (SNMP) Management Information Base (MIB) Browser window, the events in the selection pane are organized by the MIB module in which they were defined. Expand an SNMP object to show the events in that MIB module. In the list, click the object that you want to specify and click OK.

      Select the Include attributes that show information defined in the trap configuration file check box if you have a trap configuration file that contains static data for your traps. For more information about the SNMP trap configuration file, see (SNMP trap configuration).

      Select the Include variable binding (VarBind) data attribute check box if you want to include an attribute with all of the variable binding (VarBind) data that is received in the trap protocol data unit (PDU). For more information about this attribute, see the attribute definition (SNMP Event attribute groups).

      Figure 3. SNMP MIB Browser window

      1. The browser does not browse the live system; it reads definitions and, Management Information Bases (MIBs). The list of MIBs included with Agent Builder is defined in ( Monitor data from a Simple Network Management Protocol (SNMP)). MIBs loaded by either SNMP data provider are available in both.

      2. If you select a MIB module or individual events, all the events in that module are converted to separate data sources. One attribute is added for each of the variables that are defined in the event. If you want all the events for the selected modules or traps to arrive in a single event source, select the Collect events in a single attribute group check box. If you select individual traps and the Collect events in a single attribute group flag is selected, one attribute is added for each of the variables that are defined in each of the events (duplicate variables are ignored). If you select a module, variable attributes are not added.

      3. To type your own filter, use the following syntax:

        The value of the OID (object identifier) element is used to determine which traps to process for this attribute group.

        • Trap matching: The OID attribute of the global_snmp_event_settings_for_group element can be a comma-delimited list of tokens. A single token has the following syntax: 

            [enterpriseOID][-specificType]

        • Example: "1.2.3.5.1.4,1.2.3.4.5.6.7.8.9-0" The first token matches any trap with an enterprise OID of 1.2.3.5.1.4. The second token matches any trap with an enterprise of 1.2.3.4.5.6.7.8.9 and specific of 0. Because the tokens are listed together in one attribute group, an event received that matches either is processed by that attribute group.

      4. Every event that is received is processed only by the first attribute group that matches the received event. Subnode attribute groups are processed first, and then the base attribute groups are processed. The agent developer must ensure that the groups are defined in a way so that events are received in the expected attribute group.

  5. In the SNMP Event Information window (Figure 2), select the Subnode Host matching check box to match events to subnodes. If the SNMP event attribute group is part of a subnode, you can select the Subnode Host Matching check box to control whether the event must come from the SNMP agent that is monitored.

    For example: You have an agent to monitor routers, where each subnode instance represents a specific router. You develop an agent to collect data from a router with the SNMP data collector. You also define an attribute group to receive SNMP events sent by that router. Each router instance includes the same data that is defined for the event filter. Therefore, you need another way to make sure that events from your router are shown in the attribute group for that router.

    When subnode host-matching is selected, an event that is sent by the router is compared to the host defined for the SNMP data collector. If the host in use by the SNMP data collector is the same host that sent the received event, the subnode instance processes the SNMP event. Otherwise, the event is passed to the next subnode instance. Address-matching applies only to subnodes. No address-matching is done by the SNMP event attribute groups in the base agent. For the address-matching to work, the subnode definition must contain at least one SNMP attribute group. The SNMP host that is used by SNMP for that subnode instance is the host that is used for matching.

    If the Subnode Host Matching check box is clear, your subnode instances do not do this extra comparison. You must allow the user to configure a different OID filter for each subnode in this case. Otherwise, you do not need to include SNMP event attribute groups in the subnode definition.

  6. In the SNMP Event Information window (Figure 2), select the operating systems.

  7. Optional: You can click Test in the SNMP Event Information window Figure 2 to start and test your agent. See Test SNMP event attribute groups

  8. Optional:
    In the SNMP Event Information window, click Advanced to select Event Filtering and Summarization Options. See (Event filtering and summarization).

    1. When you finish selecting Event Filtering and Summarization Options, return to the SNMP Event Information window (Figure 2). If you previously selected Custom Events in the SNMP Event Information window, click Next, to select key attributes, otherwise skip the next step.

    2. On the Select key attributes page (Figure 4), click one or more key attributes for the attribute group, or click Produces a single data row.

      Figure 4. Select key attributes page

  9. Click Next, or click Finish if you are using the new agent wizard to save the agent and open the Agent Editor.



What to do next

For information about adding further attributes, see (Create attributes).


+

Search Tips   |   Advanced Search