EMS HA Monitors Version A.02.00 Release Notes

6 Chapter 1
Known Problems and Workarounds
• If you are using the disk monitor, the SCSI pass-through driver must
be configured into the kernel. If it is not, add spt0 to the
/stand/system file and rebuild the kernel.
• There is no differentiation between monitor restart notifications due
to system reboot and those due to a monitor being restarted.
Currently the persistence client (p_client) logs all monitor restarts as
RM_RESTART. If you would like to be able to distinguish between restarts due
to monitor failure (which are logged as RM_RESTART) and restarts during
system reboot (which should be logged as RM_REBOOT), you need to modify
the inittab file.
As a workaround, edit the /etc/inittab file to make sure it looks like this:
init:3:initdefault:
ems1::bootwait:touch /etc/opt/resmon/persistence/reboot_flag
ems2::bootwait:/usr/bin/rm -f /etc/opt/resmon/persistence/runlevel4_flag
ems5::boot:/etc/opt/resmon/lbin/p_client -r
ems3:3:once:touch /etc/opt/resmon/persistence/runlevel4_flag
ems4:3456:respawn:/etc/opt/resmon/lbin/p_client
Note that the contents of the ems3 and ems4 lines depends on the init
level declared in the first line. For example, an inittab file with an
init level of 2 would look like this:
init:2:initdefault:
ems1::bootwait:touch /etc/opt/resmon/persistence/reboot_flag
ems2::bootwait:/usr/bin/rm -f /etc/opt/resmon/persistence/runlevel4_flag
ems5::boot:/etc/opt/resmon/lbin/p_client -r
ems3:2:once:touch /etc/opt/resmon/persistence/runlevel4_flag
ems4:23456:respawn:/etc/opt/resmon/lbin/p_client