Filter
Top Products
Chapter 3
Detailed Description
The Detailed Picture of Hardware Monitoring
57
Startup Process (in Detail)
The following steps describe the process used to start the hardware monitoring. The startup process is
illustrated in Figure 3-2 on page 57.
The startup process is managed by the startup client (startcfg_client). The startup client is run when the
system is restarted, following an IOSCAN, when the enable monitoring command is executed from the
Hardware Monitoring Request Manager, or when monconfig changes the monitor requests.
1. When the system is restarted, following an IOSCAN, or when the enable monitoring command is executed,
the Hardware Monitoring Request Manager (monconfig) calls the start up client (startcfg_client).
2. The startup client reads the contents of a monitor startup configuration file and registers the monitoring
requests contained in the file with the EMS registrar. This causes the associated monitor to start running.
If monitoring is already enabled, the startup client unregisters all current monitoring requests, then reads
the content of the startup configuration files and registers the requests again.
3. The monitor examines the IOSCAN results table to determine if there are any hardware resources on the
system that it is responsible for monitoring. If it finds such resources, the monitor continues to run. If it
does not find any resources, the monitor stops.
4. If the monitor supports asynchronous event detection, it registers with diaglogd, indicating what types of
errors the monitor wants to receive. The monitor may specify a product description, product number, or
driver name.
5. The startup client then repeats the process for all monitor startup configuration files.
Figure 3-2 Monitoring Startup Process