ATM Configuration and Troubleshooting Guide

Configuring EMS High Availability over ATM
Configuring EMS HA-ATM for Local Recovery
Chapter 6 125
When you add a monitoring request for an ELAN interface resource, the
monitoring daemon (hatmmon) is automatically started for that interface.
The daemon continues to run as long as that monitoring request exists in
SAM. If you remove the monitoring request for an ELAN interface
resource, the hatmmon daemon for that ELAN interface stops running 60
minutes later (unless you use the kill -15 command to stop the
daemon before the 60 minutes elapse). See “Stopping the Monitor for the
ELAN Interface Resource” on page 129 for more information.
Step 10. Exit SAM.
Step 11. For each primary and secondary ELAN, use this command:
elstat -n net_interfac e -v
The status of each ELAN interface should be “Operational.” (If a
secondary LECS is configured, the status of both the primary LEC and
secondary LEC for each ELAN interface should be “Operational.”) If the
status is not “Operational,” check the switch configuration. If the
problem persists, see “Troubleshooting LAN Emulation” on page 226.
Step 12. Type this command:
netstat -in
Each primary ELAN interface should have an IP address assigned, and
the secondary ELAN interfaces should have their addresses shown as
“none”.
Example: The following example (using HP-UX 10.20 naming
conventions) shows four ATM adapters (atm0, atm1, atm2, and atm3)
installed. Two sets of primary ELAN interfaces are defined: the first set
is ela0, ela1, and ela2, and the second set is elb0, elb1, and elb2. Two
sets of secondary ELAN interfaces are defined: the first set is elc0,
elc1, and elc2, and the second set is eld0, eld1, and eld2.
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
...
atm0 9360 none none 0 0 0 0 0
ipa0 9180 24.128.168.0 24.128.169.5 3784 0 3819 0 0