Automatic starting deterrence of armmon

[井上雅也]

Hi all.
armmon is an unnecessary process.
Please teach me how to carry out automatic starting deterrence of the armmon.
And please let me also know the influence by the stop of armmon.
thanks!

[Thierry Poels_1]

hi,

if you have no AutoRaid installed you can disable its monitoring:
/etc/opt/resmon/lbin/monconfig
and delete the monitor.

regards,
Thierry.

[井上雅也]

Thank you for your reply.

By the way,what is "AutoRaid"?
Is it the general term of the disk array product made from Hewlett-Packard Company?
Is not armmon required when the disk array of the other company is being used?

Would you teach the detailed procedure of Automatic starting deterrence of armmon, if it can do?

[Andrew Merritt_2]

äº ä¸ é ä¹ ,

Armmon should not run if there is no hardware for it to monitor, so either you've got an AutoRaid, or there is a problem.

If you don't have an AutoRaid, then:

1) What version of OnlineDiags do you have installed? (Shown when you start STM)

2) Is it one armmon process running continuously, or several, either running at once or one after the other? Or are you just seeing armmon running briefly at system startup time, which is normal?

3) How much CPU is the armmon process us

[Andrew Merritt_2]

Sorry, last reply got slightly truncated. Here's the rest of it:

AutoRaid shows up in ioscan as one of:
HP C3586A
HP C5447A


Andrew

[井上雅也]

Thank you for your reply.

In the server of the system which I am taking charge of, the disk array product applicable to below is not used.

##########
HP C3586A
HP C5447A
##########

I append the execution result of the ioscan command to below.

#################################################################################
root 0 root CLAIMED BUS_NEXUS
ioa 0 0 sba CLAIMED BUS_NEXUS System Bus Adapter (803)
ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
lan 0 0/0/0/0 btlan3 CLAIMED INTERFACE PCI Ethernet (10110019)
/dev/ether0
ext_bus 0 0/0/1/0 c720 CLAIMED INTERFACE SCSI C895 Ultra Wide Single-Ended
target 0 0/0/1/0.3 tgt CLAIMED DEVICE
disk 0 0/0/1/0.3.0 sdisk CLAIMED DEVICE HP DVD-ROM 304
/dev/dsk/c0t3d0 /dev/rdsk/c0t3d0
target 1 0/0/1/0.4 tgt CLAIMED DEVICE
tape 0 0/0/1/0.4.0 stape CLAIMED DEVICE HP C1537A
/dev/rmt/0m /dev/rmt/c0t4d0BEST /dev/rmt/c0t4d0DDS
/dev/rmt/0mb /dev/rmt/c0t4d0BESTb /dev/rmt/c0t4d0DDSb
/dev/rmt/0mn /dev/rmt/c0t4d0BESTn /dev/rmt/c0t4d0DDSn
/dev/rmt/0mnb /dev/rmt/c0t4d0BESTnb /dev/rmt/c0t4d0DDSnb
target 2 0/0/1/0.7 tgt CLAIMED DEVICE
ctl 0 0/0/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t7d0
ext_bus 1 0/0/2/0 c720 CLAIMED INTERFACE SCSI C875 Ultra Wide Single-Ended
target 3 0/0/2/0.7 tgt CLAIMED DEVICE
ctl 1 0/0/2/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c1t7d0
ext_bus 2 0/0/2/1 c720 CLAIMED INTERFACE SCSI C875 Ultra Wide Single-Ended
target 4 0/0/2/1.7 tgt CLAIMED DEVICE
ctl 2 0/0/2/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c2t7d0
tty 0 0/0/4/0 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/GSPdiag1 /dev/mux0 /dev/tty0p1
/dev/diag/mux0 /dev/tty0p0 /dev/tty0p2
tty 1 0/0/5/0 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/GSPdiag2 /dev/diag/mux1 /dev/mux1 /dev/tty1p1
ba 1 0/1 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 2 0/2 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
xnf_cad 0 0/2/0/0 xnfs0400 CLAIMED INTERFACE PCI Network (140c8100)
ba 3 0/4 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ext_bus 3 0/4/0/0 c720 CLAIMED INTERFACE SCSI C875 Fast Wide Differential
target 5 0/4/0/0.3 tgt CLAIMED DEVICE
disk 1 0/4/0/0.3.0 sdisk CLAIMED DEVICE SEAGATE ST318436LC
/dev/dsk/c3t3d0 /dev/rdsk/c3t3d0
target 6 0/4/0/0.4 tgt CLAIMED DEVICE
disk 2 0/4/0/0.4.0 sdisk CLAIMED DEVICE SEAGATE ST39236LC
/dev/dsk/c3t4d0 /dev/rdsk/c3t4d0
target 7 0/4/0/0.5 tgt CLAIMED DEVICE
disk 3 0/4/0/0.5.0 sdisk CLAIMED DEVICE SEAGATE ST39236LC
/dev/dsk/c3t5d0 /dev/rdsk/c3t5d0
target 8 0/4/0/0.6 tgt CLAIMED DEVICE
disk 4 0/4/0/0.6.0 sdisk CLAIMED DEVICE SEAGATE ST39236LC
/dev/dsk/c3t6d0 /dev/rdsk/c3t6d0
target 9 0/4/0/0.7 tgt CLAIMED DEVICE
ctl 3 0/4/0/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c3t7d0
ba 4 0/5 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ext_bus 4 0/5/0/0 c720 CLAIMED INTERFACE SCSI C875 Fast Wide Differential
target 10 0/5/0/0.3 tgt CLAIMED DEVICE
disk 5 0/5/0/0.3.0 sdisk CLAIMED DEVICE SEAGATE ST318436LC
/dev/dsk/c4t3d0 /dev/rdsk/c4t3d0
target 11 0/5/0/0.4 tgt CLAIMED DEVICE
disk 6 0/5/0/0.4.0 sdisk CLAIMED DEVICE SEAGATE ST39236LC
/dev/dsk/c4t4d0 /dev/rdsk/c4t4d0
target 12 0/5/0/0.5 tgt CLAIMED DEVICE
disk 7 0/5/0/0.5.0 sdisk CLAIMED DEVICE SEAGATE ST39236LC
/dev/dsk/c4t5d0 /dev/rdsk/c4t5d0
target 13 0/5/0/0.6 tgt CLAIMED DEVICE
disk 8 0/5/0/0.6.0 sdisk CLAIMED DEVICE SEAGATE ST39236LC
/dev/dsk/c4t6d0 /dev/rdsk/c4t6d0
target 14 0/5/0/0.7 tgt CLAIMED DEVICE
ctl 4 0/5/0/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c4t7d0
ba 5 0/8 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
lan 1 0/8/0/0 btlan5 CLAIMED INTERFACE PCI Ethernet (10110019)
ba 6 0/10 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
xnf_cad 2 0/10/0/0 xnfs0400 CLAIMED INTERFACE PCI Network (140c8100)
ba 7 0/12 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
lan 2 0/12/0/0 btlan5 CLAIMED INTERFACE PCI Ethernet (10110019)
ioa 1 1 sba CLAIMED BUS_NEXUS System Bus Adapter (803)
ba 8 1/0 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
xnf_cad 1 1/0/0/0 xnfs0400 CLAIMED INTERFACE PCI Network (140c8100)
ba 9 1/2 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
lan 3 1/2/0/0 btlan5 CLAIMED INTERFACE PCI Ethernet (10110019)
ba 10 1/4 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
lan 5 1/4/0/0 btlan5 CLAIMED INTERFACE PCI Ethernet (10110019)
ba 11 1/8 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
xnf_cad 3 1/8/0/0 xnfs0400 CLAIMED INTERFACE PCI Network (140c8100)
ba 12 1/10 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ext_bus 5 1/10/0/0 c720 CLAIMED INTERFACE SCSI C875 Fast Wide Differential
target 15 1/10/0/0.3 tgt CLAIMED DEVICE
disk 9 1/10/0/0.3.0 sdisk CLAIMED DEVICE SEAGATE ST318436LC
/dev/dsk/c5t3d0 /dev/rdsk/c5t3d0
target 16 1/10/0/0.4 tgt CLAIMED DEVICE
disk 10 1/10/0/0.4.0 sdisk CLAIMED DEVICE SEAGATE ST39236LC
/dev/dsk/c5t4d0 /dev/rdsk/c5t4d0
target 17 1/10/0/0.5 tgt CLAIMED DEVICE
disk 11 1/10/0/0.5.0 sdisk CLAIMED DEVICE SEAGATE ST39236LC
/dev/dsk/c5t5d0 /dev/rdsk/c5t5d0
target 18 1/10/0/0.6 tgt CLAIMED DEVICE
disk 12 1/10/0/0.6.0 sdisk CLAIMED DEVICE SEAGATE ST39236LC
/dev/dsk/c5t6d0 /dev/rdsk/c5t6d0
target 19 1/10/0/0.7 tgt CLAIMED DEVICE
ctl 5 1/10/0/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c5t7d0
ba 13 1/12 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ext_bus 6 1/12/0/0 c720 CLAIMED INTERFACE SCSI C875 Fast Wide Differential
target 20 1/12/0/0.3 tgt CLAIMED DEVICE
disk 13 1/12/0/0.3.0 sdisk CLAIMED DEVICE SEAGATE ST318436LC
/dev/dsk/c6t3d0 /dev/rdsk/c6t3d0
target 21 1/12/0/0.4 tgt CLAIMED DEVICE
disk 14 1/12/0/0.4.0 sdisk CLAIMED DEVICE SEAGATE ST39236LC
/dev/dsk/c6t4d0 /dev/rdsk/c6t4d0
target 22 1/12/0/0.5 tgt CLAIMED DEVICE
disk 15 1/12/0/0.5.0 sdisk CLAIMED DEVICE SEAGATE ST39236LC
/dev/dsk/c6t5d0 /dev/rdsk/c6t5d0
target 23 1/12/0/0.6 tgt CLAIMED DEVICE
disk 16 1/12/0/0.6.0 sdisk CLAIMED DEVICE SEAGATE ST39236LC
/dev/dsk/c6t6d0 /dev/rdsk/c6t6d0
target 24 1/12/0/0.7 tgt CLAIMED DEVICE
ctl 6 1/12/0/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c6t7d0
pbc 0 32 pbc CLAIMED BUS_NEXUS Bus Converter
processor 0 33 processor CLAIMED PROCESSOR Processor
pbc 1 36 pbc CLAIMED BUS_NEXUS Bus Converter
processor 1 37 processor CLAIMED PROCESSOR Processor
pbc 2 40 pbc CLAIMED BUS_NEXUS Bus Converter
processor 2 41 processor CLAIMED PROCESSOR Processor
pbc 3 44 pbc CLAIMED BUS_NEXUS Bus Converter
processor 3 45 processor CLAIMED PROCESSOR Processor
pbc 4 96 pbc CLAIMED BUS_NEXUS Bus Converter
processor 4 97 processor CLAIMED PROCESSOR Processor
pbc 5 100 pbc CLAIMED BUS_NEXUS Bus Converter
processor 5 101 processor CLAIMED PROCESSOR Processor
pbc 6 104 pbc CLAIMED BUS_NEXUS Bus Converter
processor 6 105 processor CLAIMED PROCESSOR Processor
pbc 7 108 pbc CLAIMED BUS_NEXUS Bus Converter
processor 7 109 processor CLAIMED PROCESSOR Processor
memory 0 192 memory CLAIMED MEMORY Memory
#################################################################################

The disk array which armmon is supporting is not used so that the result of ioscan may also show.
However, armmon has started automatically at the time of starting of OS.
I append the execution result of the ps command to below.
(OS is rebooted on August 15.)

#################################################################################
UID PID PPID C STIME TTY TIME COMMAND
root 1858 1 0 8æ 15 ? 0:14 /usr/sbin/stm/uut/bin/tools/monitor/armmon
#################################################################################


Is this the bug of EMS and OnlineDiags?
If it is a bug, please teach me the solution of a bug, and the deterrence method of automatic starting.
If it is not a bug, please teach me the deterrence method of automatic starti

[Andrew Merritt_2]

(Looks like there's a bug in the interface to the forum, and both your response and mine have been truncated, and I just posted another response which hasn't appeared).

What version of OnlineDiags do you have installed? If it is not recent, you should upgrade to a recent version with the latest patch for that version. (http://www.docs.hp.com/hpux/onlinedocs/diag/stm/stm_upd.htm#table shows the versions)


Andrew

[井上雅也]

Thank you for your reply.


The installed version is [B.11.00.10.12].
################################################################################
OnlineDiag B.11.00.10.12 HPUX 11.0 Support Tools Bundle
################################################################################


However, even if this version is old, it is difficult on employment of a system to upgrade.
Therefore, I want to correspond by deterring automatic starting of armmon.

Can't automatic starting be deterred?
Does a way only have upgrading

[Andrew Merritt_2]

The version installed is the September 1999 version of OnlineDiags, which is 5 years out of date. I really would strongly recommend that this is upgraded to a more recent version. If you ask HP for support on this, they will tell you the same. There have been a lot of bug fixes as well as support for new hardware added in the 16 releases since that version. Upgrading will take care of this problem.

Returning to the original question, what problems is the running of 'armmon' causing? What is a reason that you want to stop it? It isn't using a lot of CPU, or interfering with the running of the system.

It is possible to stop the process running, by renaming the binary file, the .hwa file and the .dict file for the monitor. I don't have the detailed instructions to hand, and I can't say if it will work on a version of OnlineDiags so old. I think the first priority would be to install a supported versino of the software.

[井上雅也]

Although it is a reason to stop,

1)armmon carries out double starting (bug of a product).
2)There is request of not wanting to install a measure patch as much as possible.
3)There is request of not wanting to also carry out upgrade as much as possible.

By these, I thought that the armmon itself would be stopped.



Which following files should be renamed about a stop procedure?

####################################################################################
/var/stm/data/tools/monitor/disk_em.hwa
/var/stm/data/tools/monitor/dm_core_hw.hwa
/var/stm/data/tools/monitor/dm_memory.hwa
/var/stm/data/tools/monitor/dm_stape.hwa
/var/stm/data/tools/monitor/sysstat_em.hwa

./etc/opt/resmon/dictionary/DEFAULT
./etc/opt/resmon/dictionary/mibmond.dict
./etc/opt/resmon/dictionary/RemoteMonitor.dict
./etc/opt/resmon/dictionary/armmon.dict
./etc/opt/resmon/dictionary/disk_em.dict
./etc/opt/resmon/dictionary/dm_FCMS_adapter.dict
./etc/opt/resmon/dictionary/dm_TL_adapter.dict
./etc/opt/resmon/dictionary/dm_core_hw.dict
./etc/opt/resmon/dictionary/dm_fc_hub.dict
./etc/opt/resmon/dictionary/dm_fc_scsi_mux.dict
./etc/opt/resmon/dictionary/dm_fc_sw.dict
./etc/opt/resmon/dictionary/dm_memory.dict
./etc/opt/resmon/dictionary/dm_ses_enclosure.dict
./etc/opt/resmon/dictionary/dm_stape.dict
./etc/opt/resmon/dictionary/dm_ups.dict
./etc/opt/resmon/dictionary/fc60mon.dict
./etc/opt/resmon/dictionary/fw_disk_array.dict
./etc/opt/resmon/dictionary/ha_disk_array.dict
./etc/opt/resmon/dictionary/lpmc_em.dict
./etc/opt/resmon/dictionary/scsi123_em.dict
./etc/opt/resmon/dictionary/sysstat_em.dict
./usr/newconfig/etc/opt/resmon/dictionary/mibmond.dict
####################################################################################


Should it reboot after renaming of an object file?

[Andrew Merritt_2]

> 1)armmon carries out double starting (bug of a product).
Yes, it is a bug, but a very old one that has been fixed for years, and doesn't have any adverse consequences.

> 2)There is request of not wanting to install a measure patch as much as possible.
> 3)There is request of not wanting to also carry out upgrade as much as possible.

I think the policy needs to be reviewed; the system needs to be reasonably up-to-date, and it would be best to plan to do this. You will probably also need to update the general HP-UX patches to a reasonable level.

The files to renamed would be:
/etc/opt/resmon/dictionary/armmon.dict
/usr/sbin/stm/uut/bin/tools/monitor/armmon

and, if present,
/var/stm/data/tools/monitor/armmon.hwa

You don't need to reboot, only kill the existing armmon process. I believe this should work, but I can't be absolutely sure since the revision of OnlineDiags is so old.

As I suggested, the preferred options would be:

1) Update OnlineDiags
2) Do nothing, since armmon is doing nothing harmful
3) disable armmon.