Installation guide

The MPH process is automatic, requiring no human intervention and no

training. The installation time is approximately 10 minutes.

This software will not impact or degrade your system’s performance. MPH

runs as a background task, using very negligible CPU resources and is

invisible to the user. The disk space required for the collected data and the

application is approximately 300 blocks per system. This could be slightly

higher in the case of a high number of errors.

Before running MPH, review the following information:

• The Software Development Environment subset (OSFPGMR) must be

installed.

• The MPH software kit is contained in the mandatory base software

subset OSFHWBASE400. This subset is installed automatically during

the operating system installation. Full documentation is located in

/usr/field/mph/user_guide*.

• Disk space requirements for MPH is approximately 100 blocks.

• If the operating system needs to be shut down for any reason, an

orderly shutdown process must be followed. Otherwise, you will have to

restart the MPH script.

To run MPH on your system, complete the following steps:

1. Enter the following command to run the MPH script:

# MPH_OSF_020.CSH

2. Enter the information requested by the script.

Running the MPH_OSF_020.CSH script does the following:

• Creates an MPH directory. The default directory location is /var/mph.

• Updates the system crontab ﬁles to execute the MPH ﬁles at the

appropriate times. The binary error log extractor runs daily at 2:00

a.m. The data is mailed to Compaq at 3:00 a.m. every Wednesday and

Sunday.

4.6.2 Performance Monitor

The Performance Monitor is a real-time performance monitor that allows

you to detect and correct performance problems. You can display graphs

and counters to monitor dozens of different system values, including CPU

performance, memory usage, disk transfers, ﬁle-system capacity, network

efﬁciency, and buffer cache hit rates. In addition, thresholds can be set to

alert you to, or correct, a problem when it occurs, and archives of data can

4–24 Customizing the System Environment