ATM Configuration and Troubleshooting Guide

Troubleshooting
Troubleshooting EMS HA over ATM
Chapter 9 277
Example for HP-UX 11.X:
------------------------ EVENT #4 -----------------------
20:09:1998:22:49:19:986 320 : The current ELAN interface or ATM adapter
has recovered from a failure.
ELAN interface: el100 is UP.
ATM adapter: atm0 is UP.
Usually, when the current ATM adapter and its ELAN interface become
operational, these two messages are logged: ATM adapter has changed
to UP and ELAN interface has changed to UP. But, when it happens
during the delay period, the message The Current ELAN interface or
ATM adapter has recovered from a failure is logged. The message
Current ATM adapter status has changed to UP might also be
logged, depending on the timing of internal events. No separate message
for the ELAN interface is logged, though.
If only the ELAN interface becomes operational during the delay
period—that is, the ATM adapter status was not DOWN—only the
message The Current ELAN interface or ATM adapter has
recovered from a failure is logged.
D Checking that remote recovery is successful if local recovery is
not possible. If the message Local recovery not possible appears,
this means that the primary ATM adapter and/or ELAN interface have
failed, and it is not possible to recover to the local ELAN interface.
Recovery is not possible because of one or more of the following reasons:
• The secondary ATM adapter is DOWN.
• The secondary ATM adapter link to the secondary ATM switch is
DOWN.
• The secondary ATM switch is DOWN.
• The secondary LAN Emulation Services for the secondary ELANs
have failed.
If local recovery cannot be done, the hatmmon daemon notifies EMS that
the ELAN interface resource is down (and MC/ServiceGuard starts
remote recovery). To confirm that remote recovery is successful, look at
the MC/ServiceGuard syslog.log and pkg x .sh_control.log files.
These files are described in more detail in your MC/ServiceGuard
documentation. If problems occur, you can also look in the EMS log file
(/var/opt/resmon/log/api.log).