Jump to page titleUNITED STATES
hp.com home products and services support and drivers solutions how to buy
» contact hp

more options
hp.com home
End of Jump to page title
HP Services Software Patches
Jump to content

» software & drivers
» ask Compaq
» reference library
» forums & communities
» support tools
» warranty information
» contact support
» parts
» give us feedback

patches by topic
» OpenVMS
» Security
» Tru64 Unix
» Ultrix 32
» Windows
» Windows NT

associated links
» what's new
» contract access
» browse patch tree
» search patch tree
» join mailing list

connection tools
» nameserver lookup
» traceroute
» ping

Find Support Information and Customer Communities for Presario.
Content starts here
OpenVMS VMS73_LAN-V0300 Alpha V7.3 LAN ECO Summary
TITLE: OpenVMS VMS73_LAN-V0300 Alpha V7.3 LAN ECO Summary
NOTE:  An OpenVMS saveset or PCSI installation file is stored
       on the Internet in a self-expanding compressed file.
       For OpenVMS savesets, the name of the compressed saveset
       file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or
       kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS
       saveset is copied to your system, expand the compressed
       saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe.
       For PCSI files, once the PCSI file is copied to your system,
       rename the PCSI file to kitname.pcsi-dcx_axpexe or
       kitname.pcsi-dcx_vaxexe, then it can be expanded by typing
       RUN kitname.pcsi-dcx_axpexe or kitname.pcsi-dcx_vaxexe.  The
       resultant file will be the PCSI installation file which can be
       used to install the ECO.

New Kit Date:       27-SEP-2002
Modification Date:  Not Applicable
Modification Type:  NEW KIT

Copyright (c) Compaq Computer Corporation 2001,2002.  All rights reserved.

OP/SYS:     OpenVMS Alpha


SOURCE:     Compaq Computer Corporation


     ECO Kit Name:  VMS73_LAN-V0300
     ECO Kits Superseded by This ECO Kit:  None
     ECO Kit Approximate Size:  5168 Blocks
     Kit Applies To: OpenVMS Alpha V7.3
     System/Cluster Reboot Necessary:  Yes
     Rolling Re-boot Supported:  Yes
     Installation Rating:  INSTALL_1
                            1 - To be installed by all customers.
     Kit Dependencies:

       The following remedial kit(s) must be installed BEFORE
       installation of this kit:


       In order to receive all the corrections listed in this
       kit, the following remedial kits should also be installed:



An ECO kit exists for LAN components on OpenVMS Alpha V7.3.  
This kit addresses the following problems:


     o  The receiving side of a transmit request to  the  EBA  (Galaxy
        Shared  Memory  LAN) device may crash because the PFN count is
        incorrect.  The transmit side now updates the PFN count before
        updating  the  pointers  given  to  the  other instance in the
        Galaxy  (that  is  the  target  of  the   transmit   request),
        eliminating a race condition in the driver.

          Images Affected:[SYS$LDR]SYS$EBDRIVER.EXE

     o  If the cluster code (PEDRIVER) is using the EBA (Galaxy Shared
        Memory  LAN)  device,  it may choose another slower LAN device
        rather than the shared memory LAN device.   This  change  sets
        the  device  line speed to 30000 so that PEDRIVER chooses this
        interconnect over other slower interconnects.

          Images Affected:[SYS$LDR]SYS$EBDRIVER.EXE

     o  Occasionally, a transmit request to  the  EIA  (82558,  82559,
        82559ER,  DE600, DE602 PCI Ethernet) device is not seen by the
        device.  This causes the transmit to be delayed until the next
        transmit  request  is  given  to the device.  Under heavy load
        conditions, this is not noticeable.  Under light load, this is
        seen  as  a transmit that may take seconds to complete.  Where
        the device is used as a cluster interconnect,  the  result  is
        transmit retries and virtual circuit closures.

          Images Affected:[SYS$LDR]SYS$EIDRIVER.EXE

     o  With  the  EIA  (82558,  82559,  82559ER,  DE600,  DE602   PCI
        Ethernet)  device, if the link partner redoes auto-negotiation
        (switch powered off, for example), the driver does not force a
        link  transition  when  appropriate,  resulting  in  the  link
        partner selecting  half-duplex  mode  when  it  should  select
        full-duplex  mode.   Also,  the  requested  settings  are  not
        advertised correctly resulting in difficulty  auto-negotiating
        to the intended speed and duplex mode.

          Images Affected:[SYS$LDR]SYS$EIDRIVER.EXE

     o  The EIA (82558, 82559, 82559ER,  DE600,  DE602  PCI  Ethernet)
        device  driver  is  treating  the console environment variable
        EIx0_MODE   setting   of   "twisted-pair"   as   "Full-Duplex,
        Twisted-pair",  so  it should select half-duplex 10 mbit mode,
        but selects full-duplex instead.

          Images Affected:[SYS$LDR]SYS$EIDRIVER.EXE

     o  The EIA (82558, 82559, 82559ER,  DE600,  DE602  PCI  Ethernet)
        device is not being set up correctly, generally resulting in a
        duplex mode  mismatch  problem,  if  the  console  environment
        variable, EIx0_MODE is set to FastFD.

          Images Affected:[SYS$LDR]SYS$EIDRIVER.EXE

     o  The EIA (82558, 82559, 82559ER,  DE600,  DE602  PCI  Ethernet)
        device  occasionally  reads  an invalid buffer descriptor from
        the receive ring.  When this happens a  machine  check  occurs
        with   resulting   system   crash,   often  with  an  "invalid
        scatter-gather map" error.

          Images Affected:[SYS$LDR]SYS$EIDRIVER.EXE

     o   Add support for the Intel 82559ER chip and the DE602-BB NIC.

          Images Affected:[SYS$LDR]SYS$EIDRIVER.EXE

     o  Resolve a system crash with the EIA  (82558,  82559,  82559ER,
        DE600,  DE602  PCI Ethernet) device driver and with IP traffic
        (generally involving a lot of telnet connections).   When  the
        number  of  segments  comprising  a  transmit  packet  request
        exceeds 15, the driver copies the remaining segments into  one
        additional   segment.   If  this  segment  is  not  physically
        contiguous,  therefore  requiring  two   additional   segments
        instead  of  one,  the driver corrupts the stack and causes an
        INVEXCPTN system crash.  The problem is  that  the  check  for
        maximum number of segments is off by one.

          Images Affected:[SYS$LDR]SYS$EIDRIVER.EXE

     o  Fix a few  problems  with  auto-negotiation  by  DE500-BA  PCI
        Ethernet devices to improve the ability of the DE500-BA driver
        to auto-negotiate  to  the  correct  setting.   This  includes
        adjusting  the  timing of various auto-negotiation events, and
        restarting auto-negotiation when appropriate.

          Images Affected:[SYS$LDR]SYS$EWDRIVER_DE500BA.EXE

     o  On rare occasions, it is possible  for  the  Tulip  driver  to
        reset  the  Tulip  chip,  but not wait long enough after reset
        before touching the device resulting in a machine check system
        crash.  The solution is to increase the amount of time after a
        reset to guarantee that the  device  has  sufficient  time  to
        reset itself after a reset.  The Tulip driver includes support
        for the Tulip chip, DE425 EISA NIC, and the PCI Ethernet  NICs
        DE434, DE435, DE500-XA, DE500-AA, DE500-BA, DE504-BA.

          Images Affected:[SYS$LDR]SYS$ERDRIVER.EXE

     o  The DEGPA firmware included in the device driver for the DEGPA
        PCI  Gigabit  Ethernet  NIC cannot deal with a transmit buffer
        that is within 12 bytes of a 4 gigabyte boundary.  This  could
        lead  to  data  corruption.   This  problem  only  affects the
        AlphaServer  4100,   AlphaServer   DS20,   AlphaServer   ES40,
        AlphaServer  GS80  and  GS160, and system upgrades such as the
        DS25, ES45, and only those systems with at least  4  gigabytes
        of  memory.   The  fix  is to avoid the problem by copying the
        buffer to a special buffer that is not near such  a  boundary.
        The  number  of  times the workaround is invoked is tallied in
        the    internal    driver    counters    (MC    LANCP     SHOW
        DEVICE/INTERNAL_COUNTERS) called "4GB workarounds", so you can
        see if the condition ever does occur.

          Images Affected:[SYS$LDR]SYS$EW1000A.EXE

     o  Increase the amount of time given for reset by the  DEGPA  PCI
        Gigabit Ethernet device driver of the Tigon II chip.  The time
        is increased from 80 to 640 milliseconds.   On  some  systems,
        insufficient  reset  time  occasionally  results  in a machine
        check system crash when the driver touches the device after  a

          Images Affected:[SYS$LDR]SYS$EW1000A.EXE
     o  When a user (protocol) is stopped, the  user  context  is  not
        reset  correctly  by  the  DEGPA  PCI  Gigabit Ethernet device
        driver.  This results in the inability  to  restart  the  user
        without  rebooting  the  system.   For  example,  if DECnet is
        stopped and restarted it may fail to restart.

          Images Affected:[SYS$LDR]SYS$EW1000A.EXE

     o  The multicast addresses list is not given  to  the  DEGPA  PCI
        Gigabit  Ethernet  device  again  after  the driver resets the
        device to clear a transmit timeout condition.  This can happen
        if  the  cable  is unplugged with transmits outstanding to the
        device.  The consequence is that multicast traffic  stops  for
        all  users  (protocols)  until  another  user is started or an
        existing user is stopped and restarted.

          Images Affected:[SYS$LDR]SYS$EW1000A.EXE

     o  On DEC 7000 systems, with the DEFPA PCI FDDI device, which use
        mailbox  hardware to read and write registers, the error bits,
        which the driver should clear, are not being cleared properly.
        This  may  result  in  a machine check system crash because of
        stale error bits.

          Images Affected:[SYS$LDR]SYS$FWDRIVER.EXE

     o  For all LAN devices, modify the VCI  transmit  path  (used  by
        PEDRIVER, DECnet-Plus, TCP/IP, LAST, LAT and others) to verify
        the  transmit  request  is  not  too  long,  incrementing  the
        "Transmit  too  long" error counter and returning error status
        to the offending application.  This improves  the  ability  to
        diagnose  application  problems  by identifying the failure to
        transmit in the device counters and making it more visible.

          Images Affected:[SYS$LDR]SYS$LAN.EXE

     o  For all LAN devices, modify the VCI interface to allow  a  VCI
        user to enable promiscuous mode.

          Images Affected:[SYS$LDR]SYS$LAN.EXE

     o  For all LAN devices, remove the limitation  of  255  multicast
        addresses  enabled  for a device.  This may improve efficiency
        somewhat by decreasing the multicast filtering  work  done  by
        the  LAN  driver.   Only  the  Gigabit  Ethernet  devices take
        advantage of this capability.

          Images Affected:[SYS$LDR]SYS$LAN.EXE

     o  When a DECnet-Plus NCL command,  "SHOW  FDDI  STATION  *  ALL"
        request  is  processed  by  the  LAN driver network management
        code,  if  the  requested   device   returns   counters   data
        asynchronously, it is possible that R3 is destroyed during the
        LAN driver processing.  This results in an INVEXCPTN crash  in
        NCL.EXE.   The  problem  is that R3 is not preserved cross the
        call to obtain counters, when it should be.  This affects  any
        DECnet-Plus  network managed device that returns counters data
        asynchronously to a counters request, which is all XMI and all
        FDDI adapters.

          Images Affected:[SYS$LDR]NET$CSMACD.EXE

     o  Improve the boot messages for the EIA (82558, 82559,  82559ER,
        DE600,  DE602  PCI  Ethernet),  ERA  (Tulip, DE422 EISA, DE425
        EISA, DE205 ISA Ethernet), and EWA (PCI Tulip,  DE434,  DE435,
        DE500-XA,  DE500-AA,  DE500-BA  PCI  Ethernet) LAN devices, so
        that more details are available to diagnose boot failures.

          Images Affected:[SYS$LDR]SYS$EWBTDRIVER.EXE

     o  Add  support  for  booting  the  Alpha  Personal  Workstation,
        XP-1000, over the embedded 21143 chip.

          Images Affected:[SYS$LDR]SYS$EWBTDRIVER.EXE

     o  The boot driver for the  DE500  PCI  Ethernet  device  is  not
        restarting  auto-negotiation after resetting the device, which
        results in the link  partner  (generally  an  auto-negotiating
        10/100  switch) selecting half-duplex mode and the boot driver
        selecting full-duplex mode.  The duplex  mode  mismatch  slows
        satellite booting considerably.

          Images Affected:[SYS$LDR]SYS$EWBTDRIVER.EXE


This kit requires a system reboot.  Compaq strongly recommends that
a  reboot  is performed immediately after kit installation to avoid
system instability

If you have other nodes in your OpenVMS cluster, they must also  be
rebooted  in  order  to make use of the new image(s).  If it is not
possible or convenient to reboot the entire cluster at this time, a
rolling re-boot may be performed.


Install this kit with the POLYCENTER Software installation  utility
by logging into the SYSTEM account, and typing the following at the
DCL prompt:


The kit location may be a tape drive, CD, or a disk directory that
contains the kit.

Additional help on installing PCSI kits can be found by typing
HELP PRODUCT INSTALL at the system prompt

Special Installation Instructions:

     o  Scripting of Answers to Installation Questions

        During installation,  this  kit  will  ask  and  require  user
        response  to  several  questions.  If you wish to automate the
        installation of this kit and avoid having to provide responses
        to  these  questions,  you must create a DCL command procedure
        that includes the following definitions and commands:



           -  Add  the  following  qualifiers  to  the  PRODUCT  INSTALL
              command and add that command to the DCL procedure.


           -  De-assign the logicals assigned

        For  example,  a  sample   command   file   to   install   the
        VMS73_LAN-V0300 kit would be:

          $ exit

All trademarks are the property of their respective owners.
Files on this server are as follows:
privacy statement using this site means you accept its terms