5.4.1.1 Management Interface

The MI functionality for the SEA includes the following:

• A management application communicates with the DMI through the MI. A management application requests information about components in the system by issuing the DMI Get, Set, and List commands. It also registers with the SP for event notifications and proper filtering capabilities.

• When an event is generated, the DMI SP looks into its subscription and filtering table. DMI SP forwards the event in case it passes through the filtering process. The event is then forwarded to all management applications that have subscribed with the SP to receive such events.

5.4.1.2 Component Interface

The components communicate with the DMI through the CI. The components' subagents are created by end users to manage the respective components (devices/applications, etc.). The following functions are provided by the CI:

• Registration - Components register with the DMI SP.

• Sending Events - Component instrumentation sends an indication block to the SP for processing. The DMI mapper translates the DMI indication an SNMP trap.

• Components respond to the DMI SP requests to Get and Set various attributes instrumented by the component subagent.

5.4.1.3 MIF Database

The MIF database functionality for the SEA includes the following:

• There is one MIF database associated with the SP. Each component has a MIF file to describe its manageable characteristics. When the component is initially installed into the system, the MIF is added to the MIF database. SP controls all access to the MIF database.

• No MIF modification mechanism the to MIF database is provided. If the MIF needs to change, it must be uninstalled and modified using regular text editor tools, and then installed again.

• Upon installation and removal of a MIF from the MIF database, the SP must issue an indication to all registered management applications.

5.4.2 Invoking DMI Service Provider

After installing, a script file invokes the DMI SP at boot time if the /etc/dmi/conf/dmispd.conf configuration file contains neither blank lines nor comment lines. The DMI SP is invoked using the following options:

dmispd [-h] [-c config_dir] [-d debug_level]

Table 5-1 Invoking DMI SP Arguments

5.5 DMI API Libraries

The DMI API library provided with the SEA package is a C library containing procedures for developing management applications using DMI. The library also provides a component interface for users to create subagents, including component instrumentation for the management of components. Additionally, DMI APIs simplify the processes of installing components in the MIF database and invoking the SP's component interface.

5.6 MIF-to-MIB Compiler

This utility translates DMI MIF files to SNMP format and generates a map configuration file. The Network Management application (Sun Net Manager, Enterprise Manager, etc.) may use the MIB to manage the DMI-based component MIF. The mapper process uses the map file. The map file helps in mapping SNMP-based MIB variables to the DMI-based MIF attributes.

miftomib "[mifname=] [value value ...]" mifpathname [mibpathname]

Table 5-2 MIF-to-MIB Compiler Arguments

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-3 illustrates 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