SEARCH CONTACT US SUPPORT SERVICES PRODUCTS STORE
United States    
COMPAQ STORE | PRODUCTS | SERVICES | SUPPORT | CONTACT US | SEARCH
gears
compaq support options
support home
software & drivers
ask Compaq
reference library
support forum
frequently asked questions
support tools
warranty information
service centers
contact support
product resources
parts for your system
give us feedback
associated links
.
} what's new
.
} contract access
.
} browse patch tree
.
} search patches
.
} join mailing list
.
} feedback
.
patches by topic
.
} DOS
.
} OpenVMS
.
} Security
.
} Tru64 Unix
.
} Ultrix 32
.
} Windows
.
} Windows NT
.
connection tools
.
} nameserver lookup
.
} traceroute
.
} ping
OpenVMS ALPLAN05_061 Alpha V6.1 Boot Drivers/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) Digital Equipment Corporation 1996. All rights reserved. OP/SYS: OpenVMS Alpha COMPONENT: LAN - Local Area Network Boot Drivers SOURCE: Digital Equipment Corporation ECO INFORMATION: ECO Kit Name: ALPLAN05_061 ECO Kits Superseded by This ECO Kit: ALPLAN02_062 (OpenVMS Alpha V6.1) AXPLAN04_061 ALPBOOT01_062 AXPLAN03_061 AXPLAN02_061 AXPLAN01_061 ECO Kit Approximate Size: 3618 Blocks Kit Applies To: OpenVMS Alpha V6.1, V6.1-1H1, V6.1-1H2 System/Cluster Reboot Necessary: Yes Installation Rating: 3 - To be installed on all systems running the listed versions of OpenVMS which are experiencing the problems described. NOTE: In order to receive the full fixes listed in this kit, the following remedial kits also need to be installed: None ECO KIT SUMMARY: An ECO kit exists for LANs and Boot Drivers on OpenVMS Alpha V6.1. This kit addresses the following problems: Problems addressed in ALPLAN05_061 kit o "ACCVIO" crashes in the LAN driver code (varying offsets on different Ethernet only drivers) with R5 equal to zero. This problem is corrected in OpenVMS Alpha V6.2 o BUGCHECK NETDLLERR crash in SYS$FADRIVER+0031F8. The SHOW LAN/DEV=FA displays the "Last error CSR" field equal to 606. The system will also have more than 2 gigabytes of memory for this problem to appear. o INVEXCEPTN crash in OTS$MOVE_C+00344. A large number of multicast addresses being enabled, writes over the adapter type field. This problem is corrected in OpenVMS Alpha V6.2. o Machinecheck, bugcheck (ICONIODB) crashes when DEFPA in use. Crashed in EXCEPTION+0015D1C offset. Console version 4.1 is installed for DEFPA support. This problem is corrected in OpenVMS Alpha V6.2 o System crash during startup or shutdown at NET$FDDI+50DD when trying to access an FDDI network management data structure that does not exist. It is possible for a DECnet-OSI user to create an FDDI station with CSMACD Network Management data structures. o When stopping LAN protocols, some will not be removed from the multicast table. o Allocating a local data structure and overwriting existing pointers causes 106 bytes of memory to be "lost" when deleting the last user of the port. Problems addressed in AXPLAN04_061 kit o Varying kinds of pool corruption crashes. The pool corruption always is below the 1GB address range. The TGEC supports 1GB of memory. The driver uses a constant to determine at what point it should copy to low memory buffers. The constant was set at 2GB instead of 1GB. Problems addressed in ALPLAN02_062 kit o Separate the ALPBOOT01_062 remedial kit into separate kits for LAN and BOOTDRIVER fixes. Problems addressed in ALPBOOT01_062 kit o Digital has determined that a condition exists in some PCI-Ethernet interfaces in which there is an extremely remote possibility for data corruption during network transmission. Digital has received no customer complaints to date, but rather first encountered the problem during internal product testing and analysis. This specific condition exists when the PCI interface is set to a DMA burst length of 0 or 32 longwords. Using a DMA burst length of 1, 2, 4, 8 or 16 longwords will eliminate this condition. To address this concern, Digital is making available a driver patch and considers its installation mandatory for all affected systems and options to optimize data integrity. No hardware modification or replacement is necessary. This condition only exists under the Digital UNIX operating system V3.2C and OpenVMS Alpha V6.1 (and variants, i.e. V6.1-1H1, V6.1-1H2) and V6.2. Higher-level protocols and layered applications may, in fact, detect the corruption and retry the data transmission with some negligible affect on data throughput. Windows NT has a default setting of 16 longwords for the DMA burst length. This does not pose a risk unless a customer were to change this setting. The system and option products from Digital that are impacted by this condition include: DE434 PCI-Ethernet option AlphaServer 400 system DE435 PCI-Ethernet option AlphaServer 1000 system DE450 PCI-Ethernet option AlphaServer 2000 system AlphaStation 200 system AlphaServer 2100 system AlphaStation 250 system AlphaServer 8200 system AlphaStation 400 system AlphaServer 8400 system AlphaStation 600 system For OpenVMS Alpha users, this condition exists in V6.1 (and variants) and V6.2. Digital plans on providing the corrected driver in all OpenVMS Alpha factory installed software as of early December and in the V6.2-1H1 hardware release and the V7.0 release scheduled for distribution in January 1996, as well. Because the OpenVMS operating system drivers have this parameter hard coded, it is not possible to change it without loading a new driver. Problems addressed in AXPLAN03_061 kit o The images supplied with the AXPLAN02_061 kit were not installable on OpenVMS AXP V6.1-1H2. This kit provides corrected images that will install on V6.1, V6.1-1H1, V6.1-1H2. Problems addressed in AXPLAN02_061 kit o The DEFTA for TurboChannel systems, has a data corruption problem. This fix provides a driver software fix for that problem. Also, DEFPA support is added. This is not a problem in V6.1-1H2. o The SMC Tulip adapter requires software selection of thin wire/thick wire. This fix adds this software selection to the runtime driver and the boot driver. ******************* NOTE ******************* In order to receive this complete fix, the ALPBOOT06_061 kit *MUST* also be installed. ********************************************** Problems addressed in AXPLAN01_061 kit o If multiple PCI LAN adapters are present in a system, typically multiple Tulip PCI Ethernet adapters, the adapters may not be configured properly resulting in the adapters being marked offline. ******************* NOTE ******************* In order to receive the complete Third Party Tulip Ethernet Adaptor fix listed under "Problems addressed in AXPLAN02_061 kit", the AXPBOOT03_061 kit *MUST* also be installed. ********************************************** INSTALLATION NOTES: In order for the corrections in this kit to take effect, the system must be rebooted. If the system is a member of a VMScluster, the entire cluster should be rebooted.





Files on this server are as follows:

alplan05_061.README
alplan05_061.CHKSUM
alplan05_061.CVRLET_TXT
alplan05_061.a-dcx_axpexe

privacy and legal statement