 |
» |
|
|
 |
|  |  |
The known problems and corresponding workarounds for version
I.11.00.80 of the ATM link software on HP-UX 11.0 are as follows: On HP VISUALIZE
UNIX B1000, C3000, J5000, and J7000 Workstations, if you are running
a firmware version earlier than 3.2, the A5513A and A5515A HP-PCI
ATM/155 adapters do not work if they are installed in the 66 MHz
slots of those workstations (slot 2 of the B1000 and C3000, and
slots 4 and 7 of the J5000 and J7000). The adapters do work if they are installed in
the 33 MHz slots of those workstations. Workaround: Install
B1000/C3000/J5000/J7000 firmware version 3.2 or later. The firmware
version 3.2 is available as firmware patch PF_CBCJ0032 (contact
your Hewlett-Packard representative for patch installation information).
After the firmware is installed, the adapters will work in any of
the PCI slots in the B1000, C3000, J5000, and J7000 workstations.
Instructions for checking the firmware revision number are provided in
the workstation owner's guide (interrupt the boot process
and enter the command IN -FV at the main menu of the boot console). If you are running an HP
ATM version later than I.11.00.10 and are using a Nortel Centillion
ATM switch that has a software version earlier than 4.0, you will
most likely experience interoperability problems (see Nortel support
reference number CR 80877). Workaround: Upgrade
your Nortel Centillion switch to software version 4.0 or later. Installation error when installing EMS on a system
where the Japanese version of EMS is already installed. The error messages that are generated are as follows: ERROR: The EMS (B5736BA) and EMS Japanese (B5736BJ) products cannot be selected together. Exit swinstall, and run it again - this time only marking and installing one or the other. ERROR: The "checkinstall" script for "EMS-Config" failed (exit code "1"). The script location was "/var/tmp/AAAa02046/catalog/EMS-Config/pfiles/checkinstall". * This script had errors and the execution of this product cannot proceed until the problem is fixed. Check the above output from the script for further details.
|
Although these error messages occur, you do
not have to do anything: ATM and EMS will operate correctly. If you have installed the
HP-UX Extension Pack 9905 and are running swinstall to install a new version of ATM on top of a previous
version of ATM, swinstall might seem to be "hung," with "Rebooting" in
the Status field of the "Install Analysis" window. Select the Logfile... button. You should see this error in the "Log
File" window: Internal error. "system_name": You do not have the required permissions to perform this SD operation. Please check to see that you have the required permissions using the "swacl" command or see your system administrator for assistance. This error occurred in function "SMC_DisplayLogInfo", source file "smc_details.c", line 2110. Please give this information to your Hewlett-Packard support contact.. You should exit the user interface immediately. Proceed at your own risk!
|
Workaround: At this point,
select the OK button to exit the "Log File" window.
This takes you back to the "Install Analysis" window,
where the Status field should contain "Ready." From
the "File" menu, select Exit to exit swinstall. The system will reboot, and when it has finished
rebooting, the ATM software installation is complete (and correct). 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. During system startup, an
ELAN interface's initialization might not complete before
the IP initialization stars. This can lead to errors if the IP configuration
uses that ELAN interface. An example of this is when static routes
use the ELAN interface. Workaround: To avoid
this, a tunable delay parameter (ATM_ELAN_TIMEOUT) has been added to the ATM subsystem file (/etc/rc.config.d/atmconf). This parameter specifies how long the ATM startup
script waits for the ELAN interface initializations to complete. Note
that the default value for the ATM_ELAN_TIMEOUT parameter is 0 (zero), which means "no delay." 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 (the parameter is called 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 command atmmgr card_instance_number show on the MPCs, you will see that a shortcut VCC is established
between the MPCs. However, the traffic will not be able to travel
over the shortcut VCC. In an HA configuration with
local recovery, if you have floating IP addresses configured, you
may not be able to traffic after both the primary and backup elan
interfaces go down, and the primary elan interface comes up before
the secondary interface. If both elan interfaces come up, you may
recover normal traffic on the secondary interface, by forcing the
primary interface to go down temporarily, for instance, by disconnecting
and reconnecting the cable (do not reset either the ATM card or
the elan interface). If you want the traffic back on the primary
interface, for instance, after traffic has resumed on the secondary
interface and the primary is up, force the secondary interface to
go down temporally by disconnecting and reconnecting the cable (do
not reset either the ATM card or the elan interface). If you are planning on upgrading
your operating system to HP-UX version 11i on an L-class or N-class
server, you may need to update your system firmware. For additional details,
please refer to the Readme Before Installing or Updating
to HP-UX 11i document provided with your HP product.
|