ATM Configuration and Troubleshooting Guide

Conﬁguring EMS High Availability over ATM

Stopping the Daemon

Chapter 6138

Stopping the Daemon

You can stop the hatmmon monitoring daemon in two ways:

• Unconﬁgure EMS HA-ATM, which stops the daemon immediately

(see “Unconﬁguring EMS HA-ATM” on page 139).

Note: this is the preferred way.

• Stop resource monitoring by doing one or both of these things, as

applicable:

— If a monitor was started in SAM, remove the monitoring request

for the ELAN interface resource, which stops the daemon after

60 minutes have elapsed (see “Stopping the Monitor for the

ELAN Interface Resource” on page 129).

— If a monitor was started by MC/ServiceGuard, reconﬁgure the

HA cluster so that it no longer needs to monitor the resource (see

your MC/ServiceGuard documentation). Note that the hatmmon

daemon continues to run until 60 minutes have elapsed.

If you want to stop the hatmmon daemon immediately, ensure that

the daemon is still running, by using this command:

ps -ef | grep hatmmon

and then stop the daemon with this command:

kill -15 hatmmon_pid

If you kill the daemon, keep these things in mind:

— For local recovery, if a monitoring request is speciﬁed for the

ELAN resource, the monitor for that request will be restarted

(because the request has not been removed; see “Stopping the

Monitor for the ELAN Interface Resource” on page 129).

— For remote recovery, if the HA cluster is still running, and a

package has a resource dependency for the ELAN interface, the

monitor for that resource will be restarted (because the package’s

dependency on the resource has not been removed; see your

MC/ServiceGuard documentation).