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

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

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

connection tools
» nameserver lookup
» traceroute
» ping


Find Support Information and Customer Communities for Presario.
Content starts here
OpenVMS VMS731_LAN-V0700 Alpha V7.3-1 LAN ECO Summary
TITLE: OpenVMS VMS731_LAN-V0700 Alpha V7.3-1 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:       24-SEP-2003
Modification Date:  26-SEP-2003
Modification Type:  Abstract modified for Special Installation notes

(C) Copyright 2003 Hewlett-Packard Development Company, L.P.
 
    Confidential computer software.  Valid license from HP  and/or
    its subsidiaries required for possession, use, or copying.

    Consistent with FAR 12.211  and  12.212,  Commercial  Computer
    Software,  Computer Software Documentation, and Technical Data
    for Commercial Items are  licensed  to  the  U.S.   Government
    under vendor's standard commercial license.

    Neither HP nor any of its subsidiaries  shall  be  liable  for
    technical  or  editorial errors or omissions contained herein.
    The information in this document is provided "as  is"  without
    warranty  of any kind and is subject to change without notice.
    The warranties for HP products are set forth  in  the  express
    limited   warranty   statements  accompanying  such  products.
    Nothing  herein  should  be  construed  as   constituting   an
    additional warranty.

    DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY

    THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY  OF  ANY  KIND.
    ALL   EXPRESS   OR  IMPLIED  CONDITIONS,  REPRESENTATIONS  AND
    WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY,
    FITNESS  FOR  PARTICULAR  PURPOSE,  OR  NON-INFRINGEMENT,  ARE
    HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW.  IN
    NO EVENT WILL COMPAQ BE LIABLE FOR ANY LOST REVENUE OR PROFIT,
    OR  FOR  SPECIAL,  INDIRECT,  CONSEQUENTIAL,   INCIDENTAL   OR
    PUNITIVE  DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY
    OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR
    TO THE USE OF SUCH PATCH.


OP/SYS:     OpenVMS Alpha

COMPONENT:  LAN

SOURCE:     Hewlett-Packard Company

ECO INFORMATION:

     ECO Kit Name:  VMS731_LAN-V0700
                    DEC-AXPVMS-VMS731_LAN-V0700--4.PCSI
     ECO Kits Superseded by This ECO Kit:  VMS731_LAN-V0600
     ECO Kit Approximate Size:  5136 Blocks
     Kit Applies To: OpenVMS Alpha V7.3-1
     System/Cluster Reboot Necessary:  Yes
     Rolling Re-boot Supported:  Yes
     Installation Rating:  INSTALL_2
                            2 : To  be  installed  by   all  customers  using  the  following
           			feature(s):

                               -  LAN

          This installation rating, based upon current  CLD  information,  is
          provided  to  serve as a guide to which customers should apply this
          remedial kit.   (Reference  attached  Disclaimer  of  Warranty  and
          Limitation of Liability Statement)


     Kit Dependencies:

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

         VMS731_PCSI-V0100

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

         None 



FILES PATCHED OR REPLACED:


      o  [SYSEXE]APB.EXE (new image)
          
         Image Identification Information
          
         image name: "APB"
         image file identification:  "X-8"
         image file build identification:  "X9EC-0060030004"
         link date/time: 17-DEC-2002 07:42:43.61
         linker identification:  "A11-50"

      o  [SYSEXE]DEBUG_APB.EXE (new image)
          
         Image Identification Information
          
         image name: "DEBUG_APB"
         image file identification:  "X-8"
         image file build identification:  "X9EC-0060030004"
         link date/time: 17-DEC-2002 07:42:44.14
         linker identification:  "A11-50"

      o  [SYSLIB]LAN$SDA.EXE (new image)
          
         Image Identification Information
          
         image name: "LAN$SDA"
         image file identification:  "X-13"
         image file build identification:  "0060030009"
         link date/time: 26-JUN-2003 13:46:50.65
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$EGBTDRIVER.EXE (new image)
          
         Image Identification Information
          
         image name: "SYS$EGBTDRIVER"
         image file identification:  "X-10"
         image file build identification:  "X9EC-0060030004"



         link date/time: 16-DEC-2002 15:49:38.55
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$EIDRIVER.EXE (new image)
          
         Image Identification Information
          
         image name: "SYS$EIDRIVER"
         image file identification:  "X-25A3"
         image file build identification:  "X9TD-0060030009"
         link date/time: 26-JUN-2003 13:46:49.83
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$EW1000A.EXE (new image)
          
         Image Identification Information
          
         image name: "SYS$EW1000A"
         image file identification:  "X-28C2"
         image file build identification:  "X9TD-0060030009"
         link date/time: 26-JUN-2003 13:46:48.68
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$EW5700.EXE (new image)
          
         Image Identification Information
          
         image name: "SYS$EW5700"
         image file identification:  "X-5A5"
         image file build identification:  "X9TD-0060030009"
         link date/time: 26-JUN-2003 13:46:49.02
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$EWDRIVER.EXE (new image)
          
         Image Identification Information
          
         image name: "SYS$EWDRIVER"
         image file identification:  "X-3"
         image file build identification:  "X9TD-0060030009"
         link date/time: 26-JUN-2003 13:46:38.88
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE (new image)
          
         Image Identification Information
          
         image name: "SYS$EWDRIVER_DE500BA"
         image file identification:  "X-3"
         image file build identification:  "X9TD-0060030009"
         link date/time: 26-JUN-2003 13:46:39.24
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$ERDRIVER.EXE (new image)

         Image Identification Information


         image name: "SYS$ERDRIVER"
         image file identification: "X-3"
         image file build identification: "X9TD-0060030009"
         link date/time: 26-JUN-2003 13:46:38.13
         linker identification: "A11-50"

      o  [SYS$LDR]SYS$FWDRIVER.EXE (new image)
          
         Image Identification Information
          
         image name: "SYS$FWDRIVER"
         image file identification:  "X-3"
         image file build identification:  "X9TD-0060030009"
         link date/time: 26-JUN-2003 13:46:42.42
         linker identification:  "A11-50"

      o  [SYS$LDR]APB_BOOTP.EXE (new image)

      o  [SYS$LDR]SYS$CONFIG.DAT (new file)

      o  [SYSUPD]VMSKITBLD.DAT (new file)



PROBLEMS ADDRESSED IN THIS KIT

New problems addressed in the VMS731_LAN-V0700 kit

     o  Bootblock      Corruption      after      un-installing
        VMS731_LAN-V0600 ECO kit

               
               If the VMS731_LAN-V0600 ECO kit is removed using PRODUCT
               UNDO PATCH, the boot block locaton is invalid after the
               UNDO completes.  This may prevent a system from rebooting
               if the origial bootblock gets overwritten with other
               data.

               Images Affected:[SYSUPD]POSTUNDO.COM





New problems addressed in the VMS731_LAN-V0600 kit

     o  INVEXCEPTN, Exception while above ASTDEL in SYS$EW1000A

               
               During device initialization, if a DEGPA had a
               non-default setting in the LAN device database and MOP
               DLL enabled, it was possible for the initialization to
               not complete properly.  This resulted in an INVEXCEPTN
               bugcheck when the first receive completed.

               Crashdump Summary Information:
               ------------------------------
               Bugcheck Type:     INVEXCEPTN, Exception while above
                                  ASTDEL
               Current Process:   NULL
               Current Image:
               Failing PC:        FFFFFFFF.960F4B48 SYS$EW1000A+04B48
               Failing PS:        00000000.00000804
               Module:            SYS$EW1000A
                                  (Link Date/Time:
                            4-DEC-2000 14:46:27.28)
               Offset:            00004B48


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





                    
     o  Auto-negotiation never  completes  with  DE500  network
                 adapters

               
               For DE500 network adapters with external PHYs, if the
               link partner advertises 100base-T4 capability,
               auto-negotiation will never complete.

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

                	       [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE

                               [SYS$LDR]SYS$ERDRIVER.EXE



                    

     o  Cannot communicate with other nodes.

               If a user application enables 'all-multicast' mode, or if
               user applications enable more than 512 multicast address
               (which forces the driver to enable 'all-multicast' mode),
               the broadcast address is disabled.  If TCP/IP is running,
               it will not receive packets addressed to the broadcast
               address, resulting in the inability to communicate with
               other nodes.  Other applications may use the broadcast
               address as well, and may be similarly affected.

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


              
     o  LAN device initialization fails leaving device unusable

               
               If a LAN device started during a soft error, it was
               possible for the initialization to fail and leave the
               device in an unusable state until a reboot.

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

                                [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE

                                [SYS$LDR]SYS$ERDRIVER.EXE



               
     o  DMA Write Engine loss of synchronization

               
               Some Gigabit Ethernet LAN-on-Motherboard (LOM) and
               Network-Interface-Card (NIC) implementations may, in
               response to a rare trigger event, experience a DMA Write
               Engine loss of synchronization when transferring data
               from adapter/chip memory to host CPU memory.  This loss
               of synchronization can manifest itself in one or a
               combination of several ways:

                o  Data integrity problem

                o  System hang

                o  Transmit time-out

                o  System Crash, depending how the network connection is
                   used.

               This problem can occur on the following Gigabit Ethernet
               LAN-on-Motherboard (LOM) and Network-Interface-Card (NIC)
               implementations:

                o  DS25 GbE LOM Implementation, UTP copper

                o  3X-DEGXA-SA PCI GbE NIC, MMF

                o  3X-DEGXA-TA PCI GbE NIC, UTP copper


               In those situations where a non-data CRC checking
               protocol is being used, applications are at risk to
               produce indeterminate results stemming from the DMA Write
               Engine loss of synchronization.  Non-data CRC checking
               protocols include but are not limited to:

                o  OpenVMS Cluster - data CRC checking can be turned on,
                   but is off by default

                o  OpenVMS Pathworks

                o  DECnet

                o  LAT

                o  DLI

               In these situations there are no user-discernable
               symptoms.  Other causes of the problem can cause the
               following symptoms:


                -  Transmit Time-outs

                -  System Crash

                -  Unexplained Link Drops

                -  Apparent Loss Of Network Connection - in situations
                   where a data CRC checking protocol is being used, IP
                   for example, the network connection is effectively
                   disconnected from the network.  In this case, all
                   packets received subsequent to the trigger event are
                   discarded by the IP protocol stack.


               HP has observed this problem only in internal laboratory
               environments.  There are no known field/customer reports
               of this problem, or manifestations of this problem
               occurring.  While the likelihood of the trigger event
               occurring in a customer application environment is
               perceived to be low in most cases, the actual probability
               is not known it is not zero.  Because of this HP is
               advising customers of the anomaly so that they may take
               precautions to prevent it.

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

                               [SYSLIB]LAN$SDA.EXE


              
                    
     o  DE600 driver would restart the device incorrectly

               
               Occasionally, after supplying it with more receive
               buffers, the DE600 driver would restart the device
               incorrectly.  This resulted in a machine check.

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

                                [SYSLIB]LAN$SDA.EXE



     o  DE602-FA is not usable

               Link status is not being recognized properly for the
               DE602-FA causing the DE602-FA to be unusable.

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

                               [SYSLIB]LAN$SDA.EXE



               
Problems addressed in Previous LAN kits

     o  Problems addressed in previous V7.3-1 LAN ECO kits

               Problem information for problems addressed in previous
               V7.3-1 LAN kits can be found in the file
               [SYSHLP]VMS731_LAN-V0100_to_V0500.README.  These kits
               have been incorporated in the VMS731_UPDATE-V0100 ECO
               kit.


INSTALLATION INSTRUCTIONS:

Installation Command

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

     PRODUCT INSTALL VMS731_LAN /SOURCE=[location of Kit]

     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



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:

      -  $ DEFINE/SYS NO_ASK$BACKUP TRUE

      -  $ DEFINE/SYS NO_ASK$REBOOT TRUE

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

           /PROD=DEC/BASE=AXPVMS/VER=V7.0


      -  De-assign the logicals assigned

     For example, a sample command file to install the VMS731_LAN-V0700
     kit would be:

     $
     $ DEFINE/SYS NO_ASK$BACKUP TRUE
     $ DEFINE/SYS NO_ASK$REBOOT TRUE
     $!
     $ PROD INSTALL VMS731_LAN/PROD=DEC/BASE=AXPVMS/VER=V7.0
     $!
     $ DEASSIGN/SYS NO_ASK$BACKUP
     $ DEASSIGN/SYS NO_ASK$BACKUP
     $!
     $ exit


Special Installation Instructions:                                            |
                                                                             

     If you have already installed the VMS731_LAN-V0600 ECO kit there is     
     no  need  to install the VMS731_LAN-V0700 kit.  If you decide to use
     VMS731_LAN-V0600 instead, be aware that a boot problem exists when the
     UNDO function is used against it.  A workaround exists for v6.0 of the 
     ECO.  
     
     To correct the boot
     problems on the boot disk, execute an MC WRITEBOOT command  from  a     
     privileged account and answer the prompts as shown:                     
                                                                           

     $ MC WRITEBOOT                                                          

     Update VAX portion of boot block (default is Y) : N                     

     Update AXP portion of boot block (default is Y) : Y                     

     Enter AXP boot file :SYS$COMMON:[SYSEXE]APB.EXE                         

     $

All trademarks are the property of their respective owners.
Files on this server are as follows:
»dec-axpvms-vms731_lan-v0700--4.README
»dec-axpvms-vms731_lan-v0700--4.CHKSUM
»dec-axpvms-vms731_lan-v0700--4.pcsi-dcx_axpexe
privacy statement using this site means you accept its terms