$('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


Use of subnodes

How an agent can use subnodes.

For a general introduction to subnodes, and how they are used, see (Subnodes).

There are two ways that a single agent can use subnodes:


Monitor the same data from different sources

When one agent represents multiple instances of a monitored entity type, each subnode includes the same attribute groups and the correct values for the specific monitored entity instance. The number of subnodes varies based on agent configuration. The example in Figure 1 shows the monitoring of different systems.

Figure 1. Subnodes monitoring different systems


Monitor multiple types of information

When one agent monitors multiple types of monitored entities, each entity type is displayed in a separate subnode in the Tivoli Enterprise Portal physical Navigation tree. Each subnode includes the information that is defined in that subnode type. The following example shows two subnode types. Each type is monitoring a different type of entity, with different types of data available for each entity:

The agent in (Figure 2) runs one copy of each subnode type. A particular agent might create any subset of the defined agents. Subnodes can be used to mimic Tivoli Monitoring V5 profiles.

Figure 2. Subnode types in Navigator tree

There are two ways of using subnodes, different subnodes of the same type, and subnodes of different types. Both ways of using subnodes can be used in the same agent, where each type can have more than one subnode instance.

(Figure 2) shows two types of subnodes that monitor two types of entities: Common Areas and Kennel Runs. In addition, there are several subnodes that are defined for each type. There are three subnodes of type Common Area; these subnodes have the following IDs: Meadow, Hill, and Tree. There are also four subnodes of type Kennel (each collecting data from a different system that is dedicated to a Kennel Run); these subnodes have the following IDs: system1, system2, system4, and system5.

The first 24 characters of subnode IDs must be unique for all instances of the subnode type in the IBM Tivoli Monitoring installation. See Subnode name unique in (Table 2).


Data Providers in subnodes

A subnode can contain any mixture of data from the different data provider types. Most current Agent Builder data providers can be used in a subnode, including the following data providers:

A subnode can also contain a joined attribute group that combines data from two other attribute groups from the same subnode or from agent-level attribute groups.


Status of subnodes

There are two ways to determine status for a subnode agent. The first way is to look at the data that is displayed in the Performance Object Status attribute group. This attribute group displays the status for each of the other attribute groups at the same level in the agent. The Performance Object Status attribute group at the agent level displays the collection status for the other attribute groups at the agent level. The Performance Object Status attribute group in each subnode displays the collection status for the attribute groups in that subnode.

The Agent Builder also creates one attribute group for each subnode type, which displays one row for each configured subnode of that type. In the example in (Figure 3), four subnodes are running to collect data.

Figure 3. Monitoring multiple subnode instances of the same subnode type

The Performance Object Status subnode contains data visible in the Navigator tree and can have situations that monitor the status of the other data collections.

The example in Figure 4 shows a case where the data collection failed (The script was renamed causing it to fail). Typically, any value other than NO_ERROR indicates that there is a problem. For each of the data collectors that are defined in the subnode, there is one row in the table.

Figure 4. Example: data collection in a subnode



+

Search Tips   |   Advanced Search