OpenVMS ALPLAN03_071 Alpha V7.1 LAN ECO Summary
TITLE: OpenVMS ALPLAN03_071 Alpha V7.1 LAN ECO Summary
NOTE: An OpenVMS saveset or PCSI installation file is stored
on the Internet in a self-expanding compressed file.
The name of the compressed file will be kit_name-dcx_vaxexe
for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.
Once the file is copied to your system, it can be expanded
by typing RUN compressed_file. The resultant file will
be the OpenVMS saveset or PCSI installation file which
can be used to install the ECO.
Copyright (c) Compaq Computer Corporation 1998. All rights reserved.
Modification Date: 21-OCT-1998
Modification Type: New ECO Kit
OP/SYS: OpenVMS Alpha
COMPONENT: LAN - Local Area Network
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: ALPLAN03_071
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 5256 Blocks
Kit Applies To: OpenVMS Alpha V7.1 through V7.1-1H2
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Yes
Installation Rating: 1 - INSTALL_1
To be installed on all systems running
the listed version(s) of OpenVMS.
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
ALPBASE01_071 or its supersedant
In order to receive all the corrections listed in this
kit, the following remedial kits should also be installed:
None
ECO KIT SUMMARY:
An ECO kit exists for LAN Drivers on OpenVMS Alpha V7.1 through V7.1-1H2.
This kit addresses the following problems:
NEW FUNCTIONALITY INCLUDED IN THE ALPLAN03_071 KIT
o ATMworks 351 Adapter (Alpha Only)
The ATMworks 351 adapter is a high-performance, 155Mbits/s,
full-duplex ATM adapter that enables systems with peripheral
component interconnect (PCI) slots to communicate on an ATM
network. The ATMworks 351 driver is supported by the
SYS$ATMWORKS351 port driver which has a device name HWcu,
where c is the controller and u is the unit number, as for
example, HWA0. The following two sections describe
configuration restrictions and performance considerations for
the ATMworks 351 adapter.
o Restrictions
The following restrictions apply to the ATMworks 351 adapter:
o The ATMworks 350 (DGLPB-AB) is not supported in the same
system as the ATMworks 351 (DGLPA-FA/UA).
o The PBX Token Ring NIC (SN-PBXNP-AC) option from Digital
is not supported in the same system as the ATMworks 351.
o FlowMaster over the ATMworks 351 is automatically disabled
by the driver.
o OpenVMS only supports two ATMworks 351 adapters in the
AS4X00 and AS8X00 class systems.
o The ATMworks 351 is not supported on the DWLPA-xx, a PCI
bus adapter.
o The ATMworks 351 is not to be used on a Cluster
Interconnect, nor will it be used in its current form as a
future Cluster Interconnect.
o The OpenVMS driver for the ATMworks 351 supports a minimum
revision of D01. If an older revision of the card is
detected the following message is displayed and the device
is left off line:
HWn0-W-UNSUPPORT, Unsupported adapter revision found
5.1.3 Performance
When any I/O intensive adapter is configured within the same
PCI segment equipped with an ATMworks 351 adapter, performance
will be less than anticipated. It is strongly recommended
that you install an ATMworks 351 adapter on the primary PCI
bus. If this is not possible, then you should install the NIC
on a lightly loaded PCI bus.
When configuring an AS8400 with ATM, it is strongly
recommended that you install one ATMworks 351 per PCI segment.
With AS4X00, you can install two ATMworks 351s in the same
segment. A PCI segment consists of four associated PCI slots.
In a 12-slot PCI plug-in-unit (DWLPB) for the AlphaServer
8400, there are three PCI segments. You can install
additional adapters in the PCI segment provided they generate
only light I/O loading. If a message similiar to the
following appears on the operator's console, then the I/O load
is not light enough, and the configuration should be adjusted.
%ELDRIVER, LAN Emulation Event at dd-mmm-yyy hh:mm:ss.ss
%ELDRIVER, LAN Emulation unavailable: Elan_name on device ELA0:
For additional ATMworks 351 information and restrictions, you
should refer to your hardware documentation, and please refer
to the latest AlphaServer support information at the following
URL:
http://www.digital.com/alphaserver/products.html
o Add support for the DE500-BA adapter.
o Add RACORE (Token Ring) adapter support
The RACORE (Token Ring) adapter was never supported in V6.2.
The supported adapter, Thomas Conrad (Token Ring adapter) is
being phased out so this new adapter must be supported.
PROBLEMS ADDRESSED IN ALPLAN03_071:
o If a customer has a FDDI DAS (Dual Attached Station) and has
the FDDI cable plugged into the primary port B, the State value
in a status report is incorrect. It says "Waiting" when it
should say "In Use". For example:
NCL>sho fddi station fddi-1 phy port * all status
Node 0 FDDI Station FDDI-1 PHY Port FDDI-1
at 1998-06-02-10:47:56.549-04:00Iinf
Status
State = Waiting
UID = EB380655-F9FF-11D1-8004-AA00040018FD
Neighbor PHY Type = A
Estimated Link Error Rate = 15
Broken Reason = None
Reject Reason = Remote Reject
Also, it was discovered that the Estimated Link Error rate
field was passing a longword and should be an unsigned byte.
INSTALLATION NOTES:
The images in this kit will not take effect until the system is
rebooted. If there are other nodes in the VMScluster, they must
also be rebooted in order to make use of the new images.
If it is not possible or convenient to reboot the entire cluster at
this time, a rolling re-boot may be performed.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
alplan03_071.README
alplan03_071.CHKSUM
alplan03_071.CVRLET_TXT
alplan03_071.a-dcx_axpexe
|
