ATM Configuration and Troubleshooting Guide

Configuring EMS High Availability over ATM
Configuring EMS HA-ATM for Local Recovery
Chapter 6 121
Special Considerations for HP-UX 11.X
If you are running EMS HA-ATM on HP-UX 11.X, you must keep in
mind the following things:
• On HP-UX 11.X, EMS HA-ATM requires that the primary ELAN
interface being monitored must have been operational at least once
since the last reboot of the system. Additionally, all secondary ELAN
interfaces should be operational when EMS HA-ATM is started for
the first time after a reboot.
Before starting the EMS HA-ATM monitor, you can verify the status
of these ELAN interfaces by issuing this command:
elstat -n ELAN_interface_name -v
Also, for the primary ELAN interface, you can verify that it has been
operational at least once, by issuing this command:
netstat -in
If the primary ELAN interface appears in the output, it is configured
at the IP level and can be used by EMS HA-ATM to transfer its IP
address to other ELAN interfaces. If it does not appear when doing
netstat -in, then it has not been operational since the last reboot.
In this case, EMS HA-ATM will not be able to transfer its IP
addresses to secondary ELAN interfaces. It is necessary to make the
primary ELAN interface operational before any local recovery can
occur.
After the EMS HA-ATM monitor is started, all ELAN interfaces
(primary and secondary) should appear when doing netstat -in.If
any secondary ELAN interfaces do not appear, then follow these
steps in the order shown:
a. Ensure that the primary ELAN interface is operational.
b. Fix secondary ELAN interfaces so that they become operational.
After the EMS HA-ATM monitor is started, if any ELAN interfaces
(primary or secondary) do not appear at the IP level (not shown with
netstat -in), then error messages will be logged for those ELAN
interfaces in the following file:
/var/opt/hatmmon/log/ primary_ELAN_interface_name _hatmmon.log