ATM Release Notes

ATM Version I.10.20.80
Known Problems and Workarounds
Chapter 452
• While an ATM adapter is operational, if you disconnect the ATM cable from the switch
and reconnect it to another switch, the ELAN interfaces configured over the ATM adapter
might not start automatically.
Workaround: Run the atminit command to restart the adapter and all of its LANE
interfaces.
• When using a FORE switch, you might experience a delay (approximately two to three
minutes) in your ELAN interfaces coming up after you reboot the system.
Workaround: Ensure that you have either of these installed: (1) the FORE patch
asx-i960_6.0.1_1.48662E or (2) a release of FT later than FT 5.4.
• You might have to specify the LAN type during ELAN interface configuration, if you are
in either of these situations:
— You have an ELAN connectivity problem, and your ATM switch’s manufacturer
diagnoses the problem as being caused by the absence of the LAN type during
configuration.
— Your ATM switch provides the capability of specifying the LAN type during
configuration, and you have configured the LAN Emulation services to require the
LAN type during configuration.
Workaround: The only way you can do this is to manually specify the LAN type in the
ELAN interface’s configuration file; you cannot do this within SAM. Set the parameter
HP_ATM_ELAN_TYPE as follows:
HP_ATM_ELAN_TYPE = 802.3 for Ethernet
HP_ATM_ELAN_TYPE = 802.5 for Token Ring
However, keep in mind that each time you use SAM to modify the interface’s
configuration, SAM overwrites the ELAN interface configuration file. So, for example,
you’ve manually specified the LAN type in an ELAN interface’s configuration file. Then,
you later use SAM to modify some other part of the interface’s configuration. When you
save the configuration in SAM, the previous configuration file (with the LAN type you
manually specified) is overwritten. This means you then must manually re-edit the
configuration file to re-specify the LAN type.
• At this time, HP’s implementation of Multiprotocol Over ATM (MPOA) supports putting
the MPS on only a FORE router.
• In MPOA, if a shortcut route consists of MPCs that are on HP systems and an MPS that is
on a Cisco router, when you try to send traffic over that shortcut, no data will be
transferred over the shortcut. This might cause the applications to hang. If you issue the