DECnet/OSI DNA_ECO1030 OSF/1 ECO Summary
Copyright (c) Digital Equipment Corporation 1995. All rights reserved.
PRODUCT: DECnet/OSI for DEC OSF/1 AXP, V3.0
OP/SYS: DEC OSF/1, V3.0 and V3.2
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: DNA_ECO1030
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 7760 Blocks
Kit Applies To: DECnet/OSI V3.0
System Reboot Necessary: Yes
ECO KIT SUMMARY:
An ECO kit exists for DECnet/OSI V3.0 on DEC OSF/1 V3.0, V3.2. This
kit addresses the following areas:
o DNABASE (DECnet/OSI Base Components)
o DNANETMAN (DECnet/OSI Network Management)
o DNAAPP (OSI Applications)
o DNAAPPGWY (OSI Applications Gateways)
o DNAINETGW (DECnet-Internet Gateway)
o DNAAPPMAN (OSI Applications Reference Pages)
The following sections give a description of problems fixed by this ECO.
Using DECnet/OSI in a DMS Environment
If you are creating a DMS environment that includes DECnet/OSI,
you need to apply the subsets in this ECO for DECnet/OSI to work
properly. You must install the subsets from both the DECnet/OSI
kit and this ECO before creating any DMS clients. If clients have
already been created, you must delete them, install the subsets,
and recreate the clients. You must also install DECnet/OSI on the
server system itself before installing it into the DMS environment
Finally, when configuring a client, you must select a kernel
build area of type "none" for DECnet/OSI to work properly.
DNABASE301
o Systems running DECnet/OSI or DEC X.25 LLC2 over Token Ring
could panic. The cause of the panic is memory corruption and
there is no specific telltale entry on the stack. If you are
running this configuration, you should install this ECO.
o The dnascd daemon could core dump when trying to change the
"Naming Search Path" attribute of the Session Control entity.
o Systems with more than 2 gigabytes of physical memory would
panic if DECnet/OSI was installed.
o The DNS advertiser process (dnsadv) would occasionally core
dump.
o Systems could panic in routing. There were two possible
crashes, one in multicircuit configurations, and another that
reflected a changing network topology due to events taking
place outside the system itself. The first crash would show
routine rouv_duplicate_txarg() on the stack trace, while the
latter would list rouv_choose_phasev_adj().
o Previously systems would be able to communicate with Phase IV
systems on the same LAN, but would not be able to communicate
off-LAN via a Phase IV router adjacency. This problem has now
been corrected with this ECO.
o The oping utility does not work for DECnet/OSI V3.0 systems.
o If the environmental variable "fal_mapnames" is defined when
fal is invoked, fal will map OSF/1 file specs into their VMS
equivalents when communicating with a VMS system. That is, when
accessing files from a VMS system, OSF/1 will try to make its
responses look like they are coming from another VMS system.
DNANETMAN301
o The "read" command could not be accessed by NCL help.
o The network management database used by NCL and EVL is updated
with the most current information.
o To display cached information for remote systems from which
data has been recently received, the following NCL command must
be used from OpenVMS platforms:
ncl> show routing destination cache * all
The system will not respond to queries for individual records.
o NCL does not properly parse all legal values for the "Naming
Search Path" attribute of the Session Control Entity. Also, NCL
now accepts hex and binary integer values (in the form 0x...
and 0b... respectively).
DNAAPP301
FTAM has been modified so that it can interoperate with other
OSI implementations that do not support the full range of BER
encodings.
DNAAPPMAN301
In DECnet/OSI FTAM and Virtual Terminal Use and Management,
Appendix B, there should be three additional options listed for the
ocp command. These options are:
Option______Description____________________________________________
-B sleep Default is 180 seconds. The number of seconds that the
initiating entity will "sleep" or wait after a Class-
3 error is received and before attempting to recover
the association. This reinitialize sleep value may
instead be set via the OSIF_REINIT_SLEEP environmental
variable.
-K max- Default is 5. The number of times that the initiating
retry entity will "retry" to re-establish the association
with the responding entity after a Class-3 failure.
This maximum number of reinitialize attempts value may
instead be set via the OSIF_REINIT_MAX_RETRY environ-
mental variable.
-W time- Default is 120 seconds. The number of seconds that
out initiating entity will wait for a response from the
responding entity after attempting to recover the asso-
ciation. This wait for reinitialize response value may
instead be set via the OSIF_REINIT_TIMEOUT
environmental_variable.
INSTALLATION NOTES:
In order for the corrections in this kit to take effect, the system
must be rebooted.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
dna_eco1030.README
dna_eco1030.CHKSUM
dna_eco1030.tar
|
