EMS HA Monitors Version A.01.00 Release Notes

Chapter 1 7

Known Problems and Workarounds

• The network monitor may report invalid status for LAN interfaces.

The EMS monitor gets LAN interface status from the MIB-II subagent. Certain

Ethernet LAN drivers have problems reporting correct values to the MIB-II

subagent causing the monitor to report an Ethernet LAN card as DOWN when it

is functioning properly. The affected LAN card is Hewlett-Packard LAN

Interface Hw Rev 0 (P/N 25567B).

The erroneous reporting occurs most often when the an active LAN interface

has been disabled, then activated again. The lanscan command will report

an UP value while the lanadmin command and the EMS monitor display a

DOWN value. The lanscan command is correct.

There is no workaround. A patch will be included in a future Core LAN patch.

• The cmviewcl command does not show the full path of a packages resource

dependency. As a workaround, use the EMS conﬁguration interface under

SAM to view the full resource path.

• There is no differentiation between monitor starts due to system reboot and

those due to monitor failure.

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 ﬁle.

As a workaround, edit the /etc/inittab ﬁle to make sure it contains the

following lines pertaining to EMS:

ems1::bootwait:touch /etc/opt/resmon/persistence/reboot_flag

ems2::bootwait:/usr/bin/rm -f /etc/opt/resmon/persistence/runlevel4_flag

ems3::once:touch /etc/opt/resmon/persistence/runlevel4_flag

ems4:23456:respawn:/etc/opt/resmon/persistence/runlevel4_flag