1 HV Installation and Operations Guide

Chapter 7 HP-UX Configuration 177

Chapter 7

3. Restore the dm_stape.psmcfg file and the dm_stape.sapcfg files as follows:

mv /var/stm/config/tools/monitor/dm_stape.psmcfg.orig

/var/stm/config/tools/monitor/dm_stape.psmcfg

mv /var/stm/config/tools/monitor/dm_stape.sapcfg.orig

/var/stm/config/tools/monitor/dm_stape.sapcfg

4. Check for monitoring requests in monconfig. In monconfig, enter [C]

command and verify that “SCSI_tape” is accepting monitoring requests.

Preventing dm_stape from polling

If the POLL_INTERVAL value in the /var/stm/config/tools/monitor/

dm_stape.cfg

file is set to zero, the monitor still runs, but does not log any

events or poll the devices (that is, it will not send any SCSI commands).

Preventing dm_stape from polling is much easier than stopping the dm_stape

process. However, in IPR releases before IPR0109 this will not work properly.

This bug has been partially fixed in the IPR0106 release.

For the IPR0103 release, there are patches that partially fix the problem:

■ For HP-UX 11.00 with IPR0103 installed the patch number is:

PHSS_24044.

■ For HP-UX 11.11 with IPR0103 installed the patch number is:

PHSS_24045.

Note For the IPR0106 release and for the IPR0103 release with either

patch, the dialogued process must be running when you set the

POLL_INTERVAL value to zero. If it is not, the monitor will fill the

api.log file with error messages until the hard disk space is used

up, and consume most of the CPU time. Under no circumstances

should dialogued or the STM diagnostics be shut down.

After installing the appropriate patch, manually set the POLL_INTERVAL

value in the

/var/stm/config/tools/monitor/dm_stape.cfg file to zero

to stop the monitor from polling.