| From: "OpenVMS.org Lists" <ovms-lists@openvms.org> | | Subject: VMS83A_LAN-V0200, ECO Kit Release | | Date: Wed, 03 Oct 2007 10:38:12 -0400 | | To: alerts@openvms.org |
|
 |
| The VMS83A_LAN-V0200 kit has been released. This kit should be
available on the following patch download site within 24
hours of receiving this announcement.
http://www.itrc.hp.com/service/patch/mainPage.do
ftp://ftp.itrc.hp.com/
Kit files are:
VMS83A_LAN-V0200.ZIPEXE
VMS83A_LAN-V0200.TXT
Following are the release notes for this kit.
****************************
ECO SUMMARY INFORMATION
****************************
Release Date: 3-OCT-2007
Kit Name: DEC-AXPVMS-VMS83A_LAN-V0200--4.PCSI$COMPRESSED;2
Kit Applies To: OpenVMS ALPHA V8.3
Approximate Kit Size: 3466 blocks
Installation Rating: INSTALL_2
Required Features: LAN
Reboot Required: Yes - rolling reboot
Superseded Kits: VMS83A_LAN-V0100
Mandatory Kit Dependencies: VMS83A_UPDATE-V0400 or later
Optional Kit Dependencies: None
Checksums:
VMS83A_LAN-V0200.ZIPEXE Checksum: 2874388759
DEC-AXPVMS-VMS83A_LAN-V0200--4.PCSI$COMPRESSED;2 Checksum: 4006655267
VMS83A_LAN-V0200.ZIPEXE MD5 Checksum:
6D9762649C812D2EBAB4B7D451855268
DEC-AXPVMS-VMS83A_LAN-V0200--4.PCSI$COMPRESSED;2 MD5 Checksum:
98412A967E85B847AD2C8FA29A3DDF5A
=======================================================================
Hewlett-Packard OpenVMS ECO Cover Letter
=======================================================================
1 KIT NAME:
VMS83A_LAN-V0200
2 KIT DESCRIPTION:
2.1 Installation Rating:
INSTALL_2 : To be installed by all customers using the
following feature(s):
- LAN
2.2 Reboot Requirement:
Reboot Required.
HP 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.
2.3 Version(s) of OpenVMS to which this kit may be applied:
OpenVMS ALPHA V8.3
2.4 New functionality or new hardware support provided:
Yes
3 KITS SUPERSEDED BY THIS KIT:
- VMS83A_LAN-V0100
4 KIT DEPENDENCIES:
4.1 The following remedial kit(s), or later, must be installed
BEFORE installation of this, or any required kit:
- VMS83A_UPDATE-V0400
Page 2
4.2 In order to receive all the corrections listed in this kit,
the following remedial kits, or later, should also be
installed:
- None
5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS83A_LAN-V0200
KIT
5.1 New functionality addressed in this kit
5.1.1 2/4-Port Mezzanine LAN Card
5.1.1.1 Functionality Description:
This LAN patch kit provides support for the 2/4-Port
Mezzanine LAN Card.
Images Affected:
- [SYSEXE]SYS$CONFIG.DAT
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
5.1.2 Add Shared Interrupt Support for BCM5715 Mezzanine Card
5.1.2.1 Functionality Description:
The 4-port BCM5715 mezzanine card requires the driver to
support shared interrupts for two of the ports. This kit
sets the bit that says the driver supports shared
interrupts.
Images Affected:
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
5.1.3 Trace Points Added
Page 3
5.1.3.1 Functionality Description:
When a VCI user successfully starts, the LAN common
routines complete the startup request and then report an
event to the VCI application indicating the port is
usable.
This VMS83A_LAN-V0200 patch kit adds a trace point before
the startup completion and another before the port usable
event report, enhancing diagnosis of problems in this
area by providing better tracking of how startup went.
Images Affected:
- [SYS$LDR]SYS$LAN.EXE
- [SYS$LDR]SYS$LAN_CSMACD.EXE
- [SYS$LDR]SYS$LAN_FDDI.EXE
5.1.4 Additional Debug and Monitoring Support
5.1.4.1 Functionality Description:
Added support for additional debug and monitoring
functionality, via _MON versions of drivers. If the _MON
version of the driver is copied to the non _MON version,
or if the system is booted with system parameter
SYSTEM_CHECK set to 1, the debug and monitoring
functionality will be available.
Images Affected:
- [SYS$LDR]SYS$EI1000_MON.EXE
- [SYS$LDR]SYS$EIDRIVER_MON.EXE
- [SYS$LDR]SYS$EW1000A_MON.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
5.1.5 Check for Non-standard Settings of the LAN_FLAGS System
Parameter
Page 4
5.1.5.1 Functionality Description:
Check for non-standard settings of the LAN_FLAGS system
parameter. If reserved bits are set, a warning message
is displayed. If the settings could adversely affect
driver operation, the driver ignores the setting. In
both cases, an error log entry is made with the hex value
0xDAFF, indicating the LAN_FLAGS setting is non-standard.
Images Affected:
- [SYSEXE]LANACP.EXE
- [SYSEXE]LANCP.EXE
- [SYSHLP]LANCP$HELP.HLB
- [SYSLIB]LAN$SDA.EXE
- [SYS$LDR]SYS$EIDRIVER.EXE
- [SYS$LDR]SYS$EIDRIVER_MON.EXE
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
- [SYS$LDR]SYS$EW1000A.EXE
- [SYS$LDR]SYS$EW1000A_MON.EXE
- [SYS$LDR]SYS$EWXFRAME.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
- [SYS$LDR]SYS$EWDRIVER.EXE
- [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
- [SYS$LDR]SYS$FWDRIVER.EXE
5.1.6 Receive Time Histogram Added
Page 5
5.1.6.1 Functionality Description:
Driver internal counters have been modified to add a
receive time histogram which records the time that
applications took to process receive completion.
Images Affected:
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
- [SYS$LDR]SYS$EW1000A.EXE
- [SYS$LDR]SYS$EW1000A_MON.EXE
- [SYS$LDR]SYS$EIDRIVER.EXE
- [SYS$LDR]SYS$EIDRIVER_MON.EXE
- [SYS$LDR]SYS$EWXFRAME.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
5.1.7 Transmit and Fork Histogram Data Modified
5.1.7.1 Functionality Description:
The histogram data for transmit and fork has been
modified to be displayed all of the time, not just when
the /DEBUG qualifier is specified.
Images Affected:
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
- [SYS$LDR]SYS$EIDRIVER.EXE
- [SYS$LDR]SYS$EIDRIVER_MON.EXE
- [SYS$LDR]SYS$EWXFRAME.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
- [SYS$LDR]SYS$FWDRIVER.EXE
- [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
Page 6
5.1.8 Mailbox size Increased
5.1.8.1 Functionality Description:
Mailbox size has been increased to account for a larger
volatile device database entry size to accommodate
cleared counters information. Note that this change
could require the BYTLM quota value to be increased for
the user account used to issue the LANCP counters
commands. If BYTLM is insufficient, a warning messages
will accompany the command output.
Images Affected:
- [SYSEXE]LANCP.EXE
- [SYSEXE]LANACP.EXE
- [SYSHLP]LANCP$HELP.HLB
5.1.9 CLEAR_COUNTERS and RESTORE_COUNTERS Qualifiers Added
5.1.9.1 Functionality Description:
Added support for CLEAR_COUNTERS and RESTORE_COUNTERS
qualifiers. The updated commands are:
LANCP> SHOW DEVICE/COUNTERS [/CLEAR_COUNTERS] -
[/RESTORE_COUNTERS]
LANCP> SHOW DEVICE/INTERNAL_COUNTERS [/CLEAR_COUNTERS] -
[/RESTORE_COUNTERS]
CLEAR_COUNTERS clears the counters (as seen by LANCP
only) after the counters are displayed.
RESTORE_COUNTERS restores the counters to the uncleared
state.
Images Affected:
- [SYSEXE]LANCP.EXE
- [SYSEXE]LANACP.EXE
- [SYSHLP]LANCP$HELP.HLB
Page 7
5.1.10 Retry Count and Timeout Values Increased
5.1.10.1 Functionality Description:
Retry count and timeout values increased for the LANCP
MOP CONNECT command to make connections more robust.
Images Affected:
- [SYSEXE]LANCP.EXE
- [SYSEXE]LANACP.EXE
- [SYSHLP]LANCP$HELP.HLB
5.1.11 Add New device IDs
5.1.11.1 Functionality Description:
Add the PCI device IDs for the AB385A, AD337A, AD338A,
AD339A, and NC364M LAN adapters.
Images Affected:
- [SYSEXE]SYS$CONFIG.DAT
5.2 Problems addressed in this kit
5.2.1 Intel Gigabit Transmit Timeout Error
5.2.1.1 Problem Description:
With certain packet sizes and under certain load
conditions, it is possible for the Intel gigabit chip to
lock up. This will result in a transmit timeout and
restart by the driver. In most cases, it is likely to
never happen or occur only rarely. In rare cases, it
might happen much more often, given application behavior
that uses the exact mix of packet sizes necessary to
induce the problem.
Images Affected:
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
Page 8
5.2.1.2 CLDs, and QARs reporting this problem:
5.2.1.2.1 CLD(s)
None.
5.2.1.2.2 QAR(s)
None.
5.2.1.3 Problem Analysis:
See problem description.
5.2.1.4 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS Alpha after V8.3
5.2.1.5 Work-arounds:
None.
5.2.2 Failover Sets Not Properly Read
5.2.2.1 Problem Description:
Failover sets that are defined in the LANCP permanent
database in prior versions of OpenVMS are not properly
read in V8.3. Executing a LANCP CONVERT DEVICE command
does not correct the problem.
Images Affected:
- [SYSEXE]LANCP.EXE
5.2.2.2 CLDs, and QARs reporting this problem:
5.2.2.2.1 CLD(s)
QXCM1000385682
5.2.2.2.2 QAR(s)
None.
Page 9
5.2.2.3 Problem Analysis:
As the LANCP device database has evolved, it has become
necessary for LANCP and LANACP to identify the version of
the database it is reading in order to properly interpret
it. Record size has been used to identify the version,
and the code has assumed that the record size will always
increase in size with each new version. In OpenVMS
version 8.3 the record size shrank, causing the
information at the end of previous version records to be
lost because the input buffer is too small.
5.2.2.4 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS Alpha after V8.3
5.2.2.5 Work-arounds:
None.
5.2.3 Network Applications Cannot be Started
5.2.3.1 Problem Description:
In a standalone system (not clustered), network
applications cannot be started without first starting an
application in the physical device hosting the VLAN.
This leads to applications, such as DECnet and TCPIP
failing to start.
Images Affected:
- [SYS$LDR]SYS$VLANDRIVER.EXE
5.2.3.2 CLDs, and QARs reporting this problem:
5.2.3.2.1 CLD(s)
None.
5.2.3.2.2 QAR(s)
None.
Page 10
5.2.3.3 Problem Analysis:
See problem description.
5.2.3.4 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS Alpha after V8.3
5.2.3.5 Work-arounds:
None.
5.2.4 Unnecessary System Crash
5.2.4.1 Problem Description:
On rare occasions, the entire return receive ring entry
is not written. When this happens the driver crashes the
system to avoid any possibility of bad data. However, a
crash is not necessary. The only problem is a failure to
update part of the ring entry, not writing data to the
wrong buffer. With the change in this kit, rather than
crashing the system, the driver will simply record a
hardware bug error log entry, reset the device and
continue.
Images Affected:
- [SYS$LDR]SYS$EW5700.EXE
5.2.4.2 CLDs, and QARs reporting this problem:
5.2.4.2.1 CLD(s)
None.
5.2.4.2.2 QAR(s)
None.
5.2.4.3 Problem Analysis:
See problem description.
Page 11
5.2.4.4 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS Alpha after V8.3
5.2.4.5 Work-arounds:
None.
5.2.5 Preferred CPU not Set Correctly for LL and VL LAN
Devices
5.2.5.1 Problem Description:
HP TCP/IP using an LL or VL (LAN Failover or VLAN) device
may run on the primary CPU because it thinks the LAN
device does not support fastpath.
Images Affected:
- [SYS$LDR]SYS$LAN.EXE
- [SYS$LDR]SYS$LAN_CSMACD.EXE
- [SYS$LDR]SYS$LAN_FDDI.EXE
5.2.5.2 CLDs, and QARs reporting this problem:
5.2.5.2.1 CLD(s)
QXCM1000404029
5.2.5.2.2 QAR(s)
None.
5.2.5.3 Problem Analysis:
When a VCI application (DECnet-Plus, TCP/IP, PEDRIVER,
LAT, LAST, et al) is started, the application is given
the address of the preferred CPU database. This allows
the application to determine which CPU the LAN device has
been affinitized to.
For LAN Failover and VLAN devices (LL and VL devices),
the LAN drivers do not initialize this cell correctly, so
VCI applications may not be aware that the LAN driver for
a particular device is running on a particular CPU.
Page 12
The change in this LAN kit corrects this initialization
defect, allowing VCI applications to rely on the
preferred CPU database field.
5.2.5.4 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS Alpha after V8.3
5.2.5.5 Work-arounds:
None.
5.2.6 SHOW DEVICE/CHARACTERISTICS and SHOW CONFIGURATION
Commands Report Incorrect Mode
5.2.6.1 Problem Description:
If the console mode for Intel 10/100 mbit EI devices is
set to 10 or 100 mbits/sec, full-duplex with
auto-negotiation disabled, i.e., EIx0_MODE set to 'Full
Duplex, Twisted Pair' or 'FastFD', then LANCP SHOW
DEVICE/CHARACTERISTICS and SHOW CONFIGURATION commands
report the device being set to half-duplex mode rather
than full-duplex mode.
In addition to setting the console mode, this problem
existed on Alpha and Integrity systems, when LANCP
commands are issued after boot to set the EI 10/100
devices to either half-duplex or full-duplex mode.
Images Affected:
- [SYS$LDR]SYS$EIDRIVER.EXE
- [SYS$LDR]SYS$EIDRIVER_MON.EXE
5.2.6.2 CLDs, and QARs reporting this problem:
5.2.6.2.1 CLD(s)
None.
5.2.6.2.2 QAR(s)
None.
Page 13
5.2.6.3 Problem Analysis:
See problem description.
5.2.6.4 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS Alpha after V8.3
5.2.6.5 Work-arounds:
None.
5.2.7 System Crash During Minimal Startup
5.2.7.1 Problem Description:
When booting under minimal startup modes, an INVEXCEPTN
bugcheck can occur in the LANACP process.
Images Affected:
- [SYSEXE]LANACP.EXE
5.2.7.2 CLDs, and QARs reporting this problem:
5.2.7.2.1 CLD(s)
QXCM1000402325
5.2.7.2.2 QAR(s)
None.
5.2.7.3 Problem Analysis:
Under minimal startup conditions, LAN devices may not be
initialized. If an event occurs that would normally
trigger LANACP to issue a console message, a crash will
occur because the NET$AR_LAN_VECTOR in uninitialized.
5.2.7.4 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS Alpha after V8.3
Page 14
5.2.7.5 Work-arounds:
None.
5.2.8 Cluster Performance Enhancement
5.2.8.1 Problem Description:
For DE500 devices, when the link is down, the DE500
driver should complete transmit requests with immediate
error status. The driver was always attempting to
transmit when the link was down which would delay
transmit completion by 3 seconds. This caused some
applications, particularly, PEDRIVER, considerable
difficulty since the application may wait for the
transmit completion before switching to an alternate
path.
In practice this problem caused severe cluster
performance problems when the cable was disconnected from
a DE500 device.
Images Affected:
- [SYS$LDR]SYS$EWDRIVER.EXE
- [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
5.2.8.2 CLDs, and QARs reporting this problem:
5.2.8.2.1 CLD(s)
None.
5.2.8.2.2 QAR(s)
None.
!
5.2.8.3 Problem Analysis:
See problem description.
5.2.8.4 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS Alpha after V8.3
Page 15
5.2.8.5 Work-arounds:
None.
5.2.9 Unnecessary Error Log Entry
5.2.9.1 Problem Description:
When the system is booted and the link becomes available
for the first time, the driver posts an error log entry
even though this is not an error condition. With the
change in this kit, the driver will not post an error to
the device and will not make an error log entry. An
error log entry will still be made for each transition to
"link up" and "link down".
Images Affected:
- [SYS$LDR]SYS$EIDRIVER.EXE
- [SYS$LDR]SYS$EIDRIVER_MON.EXE
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
- [SYS$LDR]SYS$EW1000A.EXE
- [SYS$LDR]SYS$EW1000A_MON.EXE
- [SYS$LDR]SYS$EWXFRAME.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
- [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
- [SYS$LDR]SYS$FWDRIVER.EXE
5.2.9.2 CLDs, and QARs reporting this problem:
5.2.9.2.1 CLD(s)
None.
Page 16
5.2.9.2.2 QAR(s)
None.
5.2.9.3 Problem Analysis:
See problem description.
5.2.9.4 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS Alpha after V8.3
5.2.9.5 Work-arounds:
None.
5.2.10 System Crash
5.2.10.1 Problem Description:
When an oversize packet is received, if the device has no
remaining buffers after receipt of the first buffer
segment, the driver does not discard the packet properly.
This results in a system crash shortly afterwards, when
subsequent receive processing continues. The changes
included in this kit will properly check for remaining
buffers, avoiding the crash.
Images Affected:
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
5.2.10.2 CLDs, and QARs reporting this problem:
5.2.10.2.1 CLD(s)
None.
5.2.10.2.2 QAR(s)
None.
Page 17
5.2.10.3 Problem Analysis:
See problem description.
5.2.10.4 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS Alpha after V8.3
5.2.10.5 Work-arounds:
None.
5.2.11 Corrupted Device Drivers
5.2.11.1 Problem Description:
The device counters displayed in the driver internal
counters get corrupted after a reset.
Images Affected:
- [SYS$LDR]SYS$EWXFRAME.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
5.2.11.2 CLDs, and QARs reporting this problem:
5.2.11.2.1 CLD(s)
None.
5.2.11.2.2 QAR(s)
None.
5.2.11.3 Problem Analysis:
See problem description.
5.2.11.4 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS Alpha after V8.3
Page 18
5.2.11.5 Work-arounds:
None.
5.2.12 Transmit timeout Problem
5.2.12.1 Problem Description:
A transmit could timeout if it was the last transmit and
there was no receive traffic.
Images Affected:
- [SYS$LDR]SYS$EWXFRAME.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
5.2.12.2 CLDs, and QARs reporting this problem:
5.2.12.2.1 CLD(s)
None.
5.2.12.2.2 QAR(s)
None.
5.2.12.3 Problem Analysis:
The interrupt for the transmit would be missed resulting
in a transmit timeout and a device reset and restart and
error log entry.
5.2.12.4 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS Alpha after V8.3
5.2.12.5 Work-arounds:
None.
5.2.13 Duplicated "link up" Message.
Page 19
5.2.13.1 Problem Description:
When auto-negotiation is in progress, the "link up"
message was displayed twice.
Images Affected:
- [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
5.2.13.2 CLDs, and QARs reporting this problem:
5.2.13.2.1 CLD(s)
None.
5.2.13.2.2 QAR(s)
None.
5.2.13.3 Problem Analysis:
See problem description.
5.2.13.4 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS Alpha after V8.3
5.2.13.5 Work-arounds:
None.
5.2.14 Incorrect Error Log Entry For "link down" Events.
5.2.14.1 Problem Description:
The error log entry code for "link down" events was 0xCA
"Connection Available" when it should have been 0xCD
"Connection Down".
Images Affected:
- [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
Page 20
5.2.14.2 CLDs, and QARs reporting this problem:
5.2.14.2.1 CLD(s)
None.
5.2.14.2.2 QAR(s)
None.
5.2.14.3 Problem Analysis:
See problem description.
5.2.14.4 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS Alpha after V8.3
5.2.14.5 Work-arounds:
None.
5.2.15 System Crash
5.2.15.1 Problem Description:
A system crash occurs when LANACP is run when no LAN
devices have been configured and DECnet-Plus has not been
initialized.
Images Affected:
- [SYSEXE]LANCP.EXE
- [SYSEXE]LANACP.EXE
- [SYSHLP]LANCP$HELP.HLB
5.2.15.2 CLDs, and QARs reporting this problem:
5.2.15.2.1 CLD(s)
None.
Page 21
5.2.15.2.2 QAR(s)
None.
5.2.15.3 Problem Analysis:
LANACP relies on the presence of the system cell,
NET$AR_LAN_VECTOR, which is created when DECnet-Plus is
initialized or when the first LAN device is initialized.
Withi this LAN kit, LANACP is modified to verify that
this field exists before attempting to access it.
5.2.15.4 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS Alpha after V8.3
5.2.15.5 Work-arounds:
None.
5.2.16 Only Last LL or VL Device Configured
5.2.16.1 Problem Description:
Only the last Logical LAN (LL) or VLAN (VL) device
present in the LAN permanent device database is
configured when LANACP is started. For example, if LLA,
LLB, VLA, VLB were defined in the LAN permanent device
database, only VLB would be configured on LANACP startup.
Images Affected:
- [SYSEXE]LANCP.EXE
- [SYSEXE]LANACP.EXE
- [SYSHLP]LANCP$HELP.HLB
5.2.16.2 CLDs, and QARs reporting this problem:
5.2.16.2.1 CLD(s)
None.
Page 22
5.2.16.2.2 QAR(s)
None.
5.2.16.3 Problem Analysis:
See problem description.
5.2.16.4 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS Alpha after V8.3
5.2.16.5 Work-arounds:
None.
5.2.17 Unsupported FCARP Qualifier Removed
5.2.17.1 Problem Description:
The unsupported FCARP qualifier has been removed.
Images Affected:
- [SYSEXE]LANCP.EXE
- [SYSEXE]LANACP.EXE
- [SYSHLP]LANCP$HELP.HLB
5.2.17.2 CLDs, and QARs reporting this problem:
5.2.17.2.1 CLD(s)
None.
5.2.17.2.2 QAR(s)
None.
5.2.17.3 Problem Analysis:
See problem description.
Page 23
5.2.17.4 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS Alpha after V8.3
5.2.17.5 Work-arounds:
None.
5.2.18 LANCP SHOW Output Modified
5.2.18.1 Problem Description:
The output from a LANCP SHOW command has been modified to
show consistent header output that also includes the time
and node name in the header.
Images Affected:
- [SYSEXE]LANCP.EXE
- [SYSEXE]LANACP.EXE
- [SYSHLP]LANCP$HELP.HLB
5.2.18.2 CLDs, and QARs reporting this problem:
5.2.18.2.1 CLD(s)
None.
5.2.18.2.2 QAR(s)
None.
5.2.18.3 Problem Analysis:
See problem description.
5.2.18.4 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS Alpha after V8.3
Page 24
5.2.18.5 Work-arounds:
None.
5.2.19 LANCP Hang Problem.
5.2.19.1 Problem Description:
It was possible for a LANCP PURGE DEVICE/ALL command to
hang scanning devices, requiring a Control-C or Control-Y
to terminate LANCP.
Images Affected:
- [SYSEXE]LANCP.EXE
- [SYSEXE]LANACP.EXE
- [SYSHLP]LANCP$HELP.HLB
5.2.19.2 CLDs, and QARs reporting this problem:
5.2.19.2.1 CLD(s)
None.
5.2.19.2.2 QAR(s)
None.
5.2.19.3 Problem Analysis:
See problem description.
5.2.19.4 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS Alpha after V8.3
5.2.19.5 Work-arounds:
None.
Page 25
5.2.20 MCR MCL SHOW CSMA-CD Port * All induced System Crash
5.2.20.1 Problem Description:
An "MCR MCL SHOW CSMA-CD Port * All" command can result
cause a system crash.
Images Affected:
- [SYS$LDR]NET$CSMACD.EXE
5.2.20.2 CLDs, and QARs reporting this problem:
5.2.20.2.1 CLD(s)
QXCM1000435837
5.2.20.2.2 QAR(s)
None.
5.2.20.3 Problem Analysis:
A "buffer overflow" occurred which corrupted a valid
Non-Paged Pool Packet. The crash can be seen in multiple
places since the Data Structure that succeeds the
Corrupted Packet will be different each time.
5.2.20.4 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS Alpha after V8.3
5.2.20.5 Work-arounds:
None.
6 PROBLEMS ADDRESSED IN PREVIOUS KITS
Problems addressed by previously released VMS83A_LAN ECO kits can
be found in the following files:
o VMS83A_LAN-V100.RELEASE_NOTES
Before kit installation, these files can be extracted from the kit
via the following commands:
o To extract all release notes files at once use:
PRODUCT EXTRACT RELEASE_NOTES VMS83A_LAN -
Page 26
[/file=destination_directory]
o To extract a single release notes file use:
PRODUCT EXTRACT FILE VMS83A_LAN -
/SELECT=[SYSUPD]release_note_name[/DESTINATION=destination_directory]
The names of individual RELEASE_NOTES files in the kit can be
found with:
PRODUCT LIST {PCSI Installation Name} /SELECT = *.RELEASE_NOTES
7 FILES PATCHED OR REPLACED:
o [SYSLIB]LAN$SDA.EXE (new image)
Image Identification Information
image name: "LAN$SDA"
image file identification: "X-46A1"
image file build identification: "0080070018"
link date/time: 30-JUL-2007 17:14:10.90
linker identification: "A13-03"
Overall Image Checksum: 33990527
o [SYSEXE]LANACP.EXE (new image)
Image Identification Information
image name: "LANACP"
image file identification: "X-25"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:14:01.44
linker identification: "A13-03"
Overall Image Checksum: 168064161
o [SYSEXE]LANCP.EXE (new image)
Image Identification Information
image name: "LANCP"
image file identification: "X-86"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:14:01.24
linker identification: "A13-03"
Overall Image Checksum: 2543990816
o [SYS$LDR]NET$CSMACD.EXE (new image)
Image Identification Information
image name: "NET$CSMACD"
image file identification: "X-17"
Page 27
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:14:00.78
linker identification: "A13-03"
Overall Image Checksum: 1551481584
o [SYS$LDR]NET$FDDI.EXE (new image)
Image Identification Information
image name: "NET$FDDI"
image file identification: "X-17"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:14:00.97
linker identification: "A13-03"
Overall Image Checksum: 985599072
o [SYS$LDR]SYS$EI1000.EXE (new image)
Image Identification Information
image name: "SYS$EI1000"
image file identification: "X-35"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:14:05.23
linker identification: "A13-03"
Overall Image Checksum: 753115268
o [SYS$LDR]SYS$EI1000_MON.EXE (new image)
Image Identification Information
image name: "SYS$EI1000_MON"
image file identification: "X-35"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:14:05.60
linker identification: "A13-03"
Overall Image Checksum: 1372773319
o [SYS$LDR]SYS$EIDRIVER.EXE (new image)
Image Identification Information
image name: "SYS$EIDRIVER"
image file identification: "X-54"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:14:09.49
linker identification: "A13-03"
Overall Image Checksum: 2020294479
o [SYS$LDR]SYS$EIDRIVER_MON.EXE (new image)
Image Identification Information
image name: "SYS$EIDRIVER_MON"
image file identification: "X-54"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:14:09.76
Page 28
linker identification: "A13-03"
Overall Image Checksum: 243258387
o [SYS$LDR]SYS$EW1000A.EXE (new image)
Image Identification Information
image name: "SYS$EW1000A"
image file identification: "X-69"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:14:02.66
linker identification: "A13-03"
Overall Image Checksum: 1136973627
o [SYS$LDR]SYS$EW1000A_MON.EXE (new image)
Image Identification Information
image name: "SYS$EW1000A_MON"
image file identification: "X-69"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:14:02.99
linker identification: "A13-03"
Overall Image Checksum: 2658936157
o [SYS$LDR]SYS$EW5700.EXE (new image)
Image Identification Information
image name: "SYS$EW5700"
image file identification: "X-76"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:14:03.65
linker identification: "A13-03"
Overall Image Checksum: 4241952435
o [SYS$LDR]SYS$EW5700_MON.EXE (new image)
Image Identification Information
image name: "SYS$EW5700_MON"
image file identification: "X-76"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:14:04.09
linker identification: "A13-03"
Overall Image Checksum: 3389588859
o [SYS$LDR]SYS$EWDRIVER.EXE (new image)
Image Identification Information
image name: "SYS$EWDRIVER"
image file identification: "X-5"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:13:51.13
linker identification: "A13-03"
Overall Image Checksum: 2197939335
Page 29
o [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE (new image)
Image Identification Information
image name: "SYS$EWDRIVER_DE500BA"
image file identification: "X-5"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:13:51.55
linker identification: "A13-03"
Overall Image Checksum: 3826019683
o [SYS$LDR]SYS$EWXFRAME.EXE (new image)
Image Identification Information
image name: "SYS$EWXFRAME"
image file identification: "X-26"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:14:07.47
linker identification: "A13-03"
Overall Image Checksum: 581742548
o [SYS$LDR]SYS$EWXFRAME_MON.EXE (new image)
Image Identification Information
image name: "SYS$EWXFRAME_MON"
image file identification: "X-26"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:14:07.47
linker identification: "A13-03"
Overall Image Checksum: 4211526779
o [SYS$LDR]SYS$FWDRIVER.EXE (new image)
Image Identification Information
image name: "SYS$FWDRIVER"
image file identification: "X-5"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:13:55.45
linker identification: "A13-03"
Overall Image Checksum: 2890372373
o [SYS$LDR]SYS$LAN.EXE (new image)
Image Identification Information
image name: "SYS$LAN"
image file identification: "X-9"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:13:29.45
linker identification: "A13-03"
Overall Image Checksum: 979384326
Page 30
o [SYS$LDR]SYS$LAN_CSMACD.EXE (new image)
Image Identification Information
image name: "SYS$LAN_CSMACD"
image file identification: "X-9"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:13:37.13
linker identification: "A13-03"
Overall Image Checksum: 3825344595
o [SYS$LDR]SYS$LAN_FDDI.EXE (new image)
Image Identification Information
image name: "SYS$LAN_FDDI"
image file identification: "X-5"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:13:46.28
linker identification: "A13-03"
Overall Image Checksum: 2538784841
o [SYS$LDR]SYS$LAN_TR.EXE (new image)
Image Identification Information
image name: "SYS$LAN_TR"
image file identification: "X-5"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:13:47.30
linker identification: "A13-03"
Overall Image Checksum: 2226374367
o [SYS$LDR]SYS$VLANDRIVER.EXE (new image)
Image Identification Information
image name: "SYS$VLANDRIVER"
image file identification: "X-16"
image file build identification: "XBCA-0080070018"
link date/time: 30-JUL-2007 17:13:59.41
linker identification: "A13-03"
Overall Image Checksum: 1532460429
o [SYSHLP]LANCP$HELP.HLB (new file)
o [SYSEXE]SYS$CONFIG.DAT (new file)
8 INSTALLATION INSTRUCTIONS
Page 31
8.1 Test/Debug Image Loss
In the course of debugging problems reported to OpenVMS
Engineering, customers may be given debug or point-fix images to
install. Typically, these images do not have the same image
generation flags contained in images released via the OpenVMS
remedial patch process. Because of this, any debug or point-fix
image that is in the SYS$COMMON area, will be replaced by any image
of the same name installed by this kit. If this occurs, you will
lose any functionality that is provided by the replaced image. If
you wish to retain these debug or point-fix images, you can take
the following steps:
o Prior to installing this kit, move the test/debug image(s) to
be saved to the SYS$SPECIFIC area.
o During kit installation, you will be asked if you wish to
delete the image(s) in SYS$SPECIFIC. You should answer NO for
each image that you want to keep.
o After installation completes, but before rebooting the system
(if required), move the image(s) from SYS$SPECIFIC back to
SYS$COMMON.
8.2 Compressed File
This kit is provided as a Self Extracting ZIPEXE kit. To expand
this file to the installable .PCSI file, run the file with the
following command:
$ RUN VMS83A_LAN-V0200.ZIPEXE
8.3 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 VMS83A_LAN[/SOURCE=location of Kit]
Note that this kit will install with the /SAVE_RECOVERY_DATA option
turned on. Using this qualifier will allow easy removal of the kit
from the system in the event of problems. If you wish to disable
this option you must use the /NOSAVE_RECOVERY_DATA qualifier on the
PRODUCT INSTALL command. The /SAVE_RECOVERY_DATA qualifier is
optional but highly recommended. Using this qualifier will allow
easy removal of the kit from the system in the event of problems.
The kit location may be a tape drive, CD, or a disk directory that
contains the kit. The /SOURCE qualifier is not needed if the
PRODUCT INSTALL command is executed from the same directory as the
kit location.
Page 32
Additional help on installing PCSI kits can be found by typing HELP
PRODUCT INSTALL at the system prompt.
8.4 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
logical name definitions and commands:
o To avoid the BACKUP question, define the following:
$ DEFINE/SYS NO_ASK$BACKUP TRUE
o To avoid the REBOOT question, define the following:
$ DEFINE/SYS NO_ASK$REBOOT TRUE
o To save replaced files as *.*_OLD define the following logical
name as YES. If you do not wish to save replaced files, define
the logical name as NO. Note that if you use the
/SAVE_RECOVERY_DATA qualifier (recommended) on the PRODUCT
INSTALL command all replaced files will be saved as part of
that operation. There is no need to also save files as
*.*_OLD:
$ DEFINE/JOB ARCHIVE_OLD NO
o Add the following qualifiers to the PRODUCT INSTALL command and
add that command to the DCL procedure.
/PROD=DEC/BASE=AXPVMS/VER=V2.0 [/SOURCE=location of Kit]
o De-assign the logical names assigned
For example, a sample command file to install the VMS83A_LAN-V0200
kit would be:
$ DEFINE/SYS NO_ASK$BACKUP TRUE
$ DEFINE/SYS NO_ASK$REBOOT TRUE
$ DEFINE/JOB ARCHIVE_OLD NO
$!
$ PROD INSTALL VMS83A_LAN/PRODUCER=DEC/BASE=AXPVMS/VER=V2.0"
$!
$ DEASSIGN/SYS NO_ASK$BACKUP
$ DEASSIGN/SYS NO_ASK$REBOOT
$!
$ exit
$!
Page 33
9 COPYRIGHT AND DISCLAIMER:
(C) Copyright 2007 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 HP 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.
|
|