HP Surestore Bridge FC 2/1 LV and FC 4/1 HV Installation and Operations Guide

176 HP-UX Configuration Chapter 7
Re-enter the Criteria Threshold, Criteria Operator, Notification
Method, User comment, and Client Configuration File.
—Type
[Y] to keep the changes.
Repeat these steps for all monitor requests that contain “SCSI_tape.
f. Type
[C] for the changes to take effect.
3. Rename the dm_stape.psmcfg file as follows:
mv /var/stm/config/tools/monitor/dm_stape.psmcfg
/var/stm/config/tools/monitor/dm_stape.psmcfg.orig
4. Verify that EMS is not taking further monitoring requests for dm_stape. In
moncofig, enter [C] command until no monitoring requests exist for
“SCSI_tape.
5. Rename the dm_stape.sapcfg file as follows:
mv /var/stm/config/tools/monitor/dm_stape.sapcfg
/var/stm/config/tools/monitor/dm_stape.sapcfg.orig
6. Kill dm_stape and remove the dm_stape.hwa file as follows:
ps -ef | grep dm_stape (to get pid of dm_stape)
kill -2 <dm_stape pid>; rm /var/stm/data/tools/monitor/
dm_stape.hwa
7. Rename the dm_stape binary (optional; dm_stape will not run at all) as
follows:
mv /usr/sbin/stm/uut/bin/tools/monitor/dm_stape
/usr/sbin/stm/uut/bin/tools/monitor/dm_stape.orig
Note This step may cause the EMS framework to generate errors.
To restart dm_stape after it has been stopped:
1. Rename dm_stape binary back (if step 7 was performed when stopping
dm_stape):
mv /usr/sbin/stm/uut/bin/tools/monitor/dm_stape.orig
/usr/sbin/stm/uut/bin/tools/monitor/dm_stape
2. Add monitoring requests for dm_stape:
a. Log in as
[root].
b. Run
/etc/opt/resmon/lbin/monconfig.
c. Add monitoring requests for “SCSI_tape” with the [A] command.