The mapper normally starts at the system boot time through startup scripts. The mapper startup must be performed in the later stages of system startup. This enables the SNMP Master Agent and DMI (SP) to be initialized. Dynamic registration then takes place between snmpXdmid and both the Master Agent and the DMI SP.
This enables the SP to provide services (such as access to the MIF database). The mapper also adds an entry in the subscription table/filter table on the SP to receive indications.
The mapper builds the translation table.
The translation table retains a Master Agent registration point for each unique pair of SNMP OID prefix and component names it finds in the .MAP files. When constructing these translation tables, the mapper searches all .MAP files in the /var/dmi/map directory.
Identifiers for these components, along with group identifiers associated with each component, are retained for translation. Attributes of installed components not found in a .MAP file by the program are inaccessible by the SNMP agent. Whenever a component is installed or uninstalled, the translation tables are appropriately adjusted.
The mapper connects to the Master Agent.
Registration is achieved by using the following definitions:
At this point, the agent registers the object ID for the MIB for which it is responsible.
The MIB OID prefixes that have been retrieved from the .MAP files are used for registration. OID prefixes associated with component names for which there are no installed components may also be registered.
On initialization, if the DMI and its interfaces are functional, and the translation table is correct, a cold-start trap is sent to the agent. Refer to "6.6.1 Exception Reporting"for more information on trapping.
Reinitialization occurs upon detection of a severe or potentially severe error. This may be an error in communicating with either DMI or the Master Agent. On reinitializing DMI, Master Agent, and table initialization, a warm-start trap is sent to the Master Agent.