HP DECnet Phase IV for OpenVMS Alpha and OpenVMS I64, Version 8.3
HP DECnet for OpenVMS Alpha and OpenVMS I64, Version 8.3 SPD 48.48.11
more other adapters in the set remain idle. If the active
adapter fails, one of the idle adapters in the set auto-
matically takes over LAN traffic using the same address
as the failed adapter.
DECnet for OpenVMS Operation
DECnet for OpenVMS is implemented under the
OpenVMS operating system as an Ancillary Control Pro-
cess (ACP) and a network device driver with executive-
level components and user-level programs supplied by
HP.
The normal OpenVMS protection has been incorporated
in the operation of DECnet for OpenVMS. For example,
incoming connects including file access and file transfer
requests are protected by the normal OpenVMS login
and file protection mechanisms. Outgoing connects in-
cluding file access and file transfer requests can include
user password information that is implicitly specified via
NCP, or explicitly specified by the user for verification
on the remote node.
DECnet for OpenVMS Con figuration and Performance
The process of configuring a DECnet node is based pri-
marily on trade-offs of cost, performance, and function-
ality while satisfying the user’s application requirements.
It can be expected that network applications will range
from low-speed, low-cost situations to those of relatively
high performance and functionality. The performance of
a given DECnet for OpenVMS node is a function not
only of the expected network traffic and resultant pro-
cessing, but also of the amount of concurrent processing
specific to that node. Thus, node performance depends
on many factors including:
• CPU types
• Number and type of devices
• In an SMP environment, the overall load on the pri-
mary CPU is especially relevant because the Phase
IV NETACP can only be scheduled on that CPU.
• Number of device interrupts per unit time
• Communication line(s) characteristics
• Number and size of buffers
• Message size and frequency of transmission
• Applications in use
• Size and frequency of route-through traffic
It is important to note that the rate at which user data
can be transmitted (throughput) over a communications
line can sometimes approach, but will never exceed,
the actual line speed. The reason is that the actual
throughput is a function of many factors, including the
line quality, protocol overhead, topology, and network
application(s), as well as the factors cited in this section.
INSTALLATION
For the first installation of this product, HP recommends
the purchase of HP’s Installation Services. These ser-
vices provide for installation of the software product by
an experienced HP Software Specialist.
Customer Responsibilities
Before HP can install the software, the customer must:
• Ensure that the system meets the minimum hard-
ware and software requirements (as specified in the
relevant SPDs).
• Prior to installing HP hardware or software, obtain,
install, and demonstrate as operational any modems
and other necessary customer equipment or facilities
to which HP’s communication hardware or software
will connect.
• Designate one adjacent node to verify installa-
tion/connectivity.
• Make available for a reasonable period of time, as
mutually agreed upon by HP and the customer, all
hardware communication facilities and terminals that
are to be used during installation.
Delays caused by any failure to meet these responsibil-
ities will be charged at the then prevailing rate for time
and materials.
Installation for DECnet for OpenVMS will consist of the
following:
• Verification that all components of DECnet for
OpenVMS have been received.
• Verification that the necessary versions of the
OpenVMS software and documentation are avail-
able.
• Verification of the appropriate SYSGEN parameters.
Note: Should a HP Software Specialist be required
to modify the previously installed operating system
parameters, a time and materials charge will apply.
• Create any necessary DECnet accounts and direc-
tories.
• Enable software via License Product Authorization
Key (PAK) registration.
•Define and create a local node DECnet database.
• Modify the system’s startup command procedure to
include startup of the DECnet for OpenVMS network.
• Verify the proper installation of DECnet for OpenVMS
by running a series of tests to show connectivity to a
designated node.
Connectivity to all other nodes within the network is the
responsibility of the customer.
4