5.7 Mapper

The mapper is an SNMP subagent acting as a DMI management application. It sends management requests to the DMI SP using the management interface. It also processes events from the component through the SP and passes them on to the Master Agent. Thus, the DMI-enabled component looks like any other SNMP-managed component. Figure 5-3illustrates the mapper and component communication.

Figure 5-3 DMI Mapper and DMI Components

The following sections describe the subagent tasks during the life cycle.

5.7.1 Subagent Initialization/Reinstallation

• Registers itself with SP, so the SP may provide services, such as access to the MIF database and indications from components.

• Builds a translation table for mapping. This is done by reading the map files created for each component. The translation table is built when the mapper initially comes up. Later, when a new component is installed and registered with the SP, the DMI SP sends an event to the mapper. The mapper then adds the new map file entry into its mapping table.

• Establishes a connection between the Master Agent and subagent; it also registers itself with the Master Agent.

• Builds up the translation table used for SNMP/DMI mapping and translating SNMP OIDs to DMI objects dynamically.

5.7.2 Invoking the Mapper

The mapper is invoked using the following options:

snmpXdmid -s hostname [-h] [-c config_dir] [-d debug_level]

Table 5-3 Invoking DMI SP Arguments

Argument	Definition
-h	Displays the command line usage
-s hostname	The name of the host where the SP is running; by default it is the local host
-c config_dir	The full path of the directory containing the snmpXdmid.conf configuration file
-d debug_level	In debug mode, the process does not run as a daemon and it displays trace messages on the display screen; depending on the debug_level (1-5), it prints a specific amount of information