Filter
Top Products
Chapter 2 HPSS Planning
HPSS Installation Guide September 2002 53
Release 4.5, Revision 2
2.3.5.2 HPSS Non-DCE Mover Machine
1. Linux kernel 2.4.18
2. HPSS KAIO Patch
It will be necessary to apply the HPSS KAIO kernel patch (kaio-2.4.18-1). This patch adds
asynchronous I/O support to the kernel which is required for the Mover. The procedure
for applying this patch is outlined in Section 3.10: Setup Linux Environment for Non-DCE
Mover on page 195
2.3.5.3 HPSS Non-DCE Client API Machine
1. Redhat Linux, version 7.1 or later
2. C compiler
2.3.5.4 HPSS pftp Client Machine
1. Redhat, version 7.1 or later
2. C compiler
2.4 Hardware Considerations
This section describes the hardware infrastructure needed to operate HPSS and considerations
about infrastructure installation and operation that may impact HPSS.
2.4.1 Network Considerations
Because of its distributed nature and high-performance requirements, an HPSS system is highly
dependent on the networks providing the connectivity among the HPSS servers, SFS servers, and
HPSS clients.
For control communications (i.e., all communications except the actual transfer of data) among the
HPSS servers and HPSS clients, HPSS supports networks that provide TCP/IP. Since control
requests and replies are relatively small in size, a low-latency network usually is well suited to
handling the control path.
The data path is logically separate from the control path and may also be physically separate
(although this is not required). For the data path, HPSS supports the same TCP/IP networks as
those supported for the control path. For supporting large data transfers, the latency of the network
is less important than the overall data throughput.
HPSS also supports a special data path option that may indirectly affect network planning because
it may off-load or shift some of the networking load. This option uses the shared memory data