ATM Configuration and Troubleshooting Guide

Conﬁguring EMS High Availability over ATM

Conﬁguring EMS HA-ATM for Local Recovery

Chapter 6 123

Conﬁguring the Local Recovery Delay Period

NOTE Once you have conﬁgured the delay period, it is not in effect when the

hatmmon monitor ﬁrst starts (regardless of whether you start it manually

or MC/ServiceGuard starts it [see “Starting the Monitor for the ELAN

Interface Resource” below]). For example, if hatmmon starts when the

primary ELAN interface is inactive and a secondary interface is active,

an immediate recovery to the secondary interface occurs. If no secondary

interface is conﬁgured, hatmmon notiﬁes MC/ServiceGuard that the

resource is down (which causes a package remote recovery). Once

hatmmon starts, and has taken the actions needed at startup time, any

failures—and hatmmon’s reporting of any resource failure to

MC/ServiceGuard—will be affected by the delay period.

If you want to specify a delay period for local recovery (see “Local

Recovery” on page 93), follow these steps:

Step 1. Using an editor of your choice (for example, vi), create a ﬁle with this

name:/etc/atm/hatmmon/config/

ELAN_interface_name

where

ELAN_interface_name

is the name of the primary ELAN

interface you want to conﬁgure a delay for (for example,

/etc/atm/hatmmon/config/ela0).

Step 2. In the ﬁle you just created, add this line:

INTERFACE_FAILURE_DELAY=num_of_delay_seconds

where

num_of_delay_seconds

is the number of seconds you want

hatmmon to wait until it starts a local recovery of the ELAN interface (for

example, INTERFACE_FAILURE_DELAY=20).

Step 3. If you are monitoring another primary ELAN interface, repeat steps 1

and 2 for that interface.

Otherwise, go to the next section, “Starting the Monitor for the ELAN

Interface Resource”.