Copyright 2007 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license required from HP 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.
The information contained herein is subject to change without notice.
The only warranties for HP products and services are set forth in the
express warranty statements accompanying such products and services.
Nothing herein should be construed as constituting additional warranty.
HP shall not be liable for technical or editorial errors or omissions
contained herein.
Oracle is a registered US trademark of Oracle Corporation, Redwood
City, California.
The Hewlett-Packard X.25 link for HP 9000 systems provides
networking link hardware and software to allow HP computer systems to
communicate with other HP and non-HP computers over X.25 packet
switching networks.
The X.25 link implements the CCITT X.25 Recommendations and
contains the components necessary to connect an HP 9000 to a public or
private packet switching network conforming to the CCITT X.25 Recommendation (1980, 1984 or 1988), or to another system in a
back-to-back configuration.
The information in this manual applies to HP 9000 Series 700 and 800
systems that use single, dual, or quad-port communications hardware.
Any differences are specifically noted.
NOTEIn a diskless cluster, X.25 software is only supported on the server
system. It is not supported on client systems for this type of
environment.
The following diagram illustrates the X.25 link architecture where:
•solid white boxes represent the product’s integral components.
•lightly shaded boxes represent the product’s protocol components.
•heavily shaded boxes represent optional components (external to the
product) that can be added to the product.
Each component depends on the component(s) below it and must be
installed and running in order to support higher-level components.
Chapter 116
Figure 1-1X.25 Link Architecture
About the X.25 Product
Introduction
OSI Services
OTS/9000
OTS-to-PLP
Translator
X.25
PAD
Services
X.25
Programmatic Access
BSD-to-PLP Translator
X.25 Packet Level Protocol (PLP)
X.25 Link Access Procedure-Balanced Protocol (LAP-B)
User
Written
L3
BSD IPC
User
Written
L4
IP-to-PLP Interface
Internet
Services
TCP/UDP
Network
Services NS
X.25 Communications Hardware
Chapter 117
About the X.25 Product
Application (L7), Presentation (L6), and Session (L5) Levels
Application (L7), Presentation (L6), and
Session (L5) Levels
The X.25 link does not provide any components for the general support of
the application and presentation levels (levels 7 and 6, respectively),
although X.25/9000 PAD Services do provide some of the functionality of
these levels.
User-written application programs, Internet Services/Berkeley Services
(via BSD Sockets) and NS (via NetIPC Sockets), are accessed by means
of TCP or UDP Transport Level (level 4) protocols.
For application level services, you can install OSI Services to run over
the X.25 network (for more information, refer to OSI Services
documentation). The OTS/9000 product provides access to X.25 for OSI
Services. You can install application level services such as
Internet/Berkeley Services and Network Services (for more information,
refer to the documentation for these products).
BSD IPC (Berkeley Software Distribution InterProcess Communication)
allows direct programmatic access to the X.25 packet level (level 3), or
TCP/UDP at the transport level (level 4), for user-written application
programs.
NetIPC sockets also provides a programmatic interface to TCP/UDP at
the transport level.
Chapter 118
About the X.25 Product
Transport Level (L4)
Transport Level (L4)
At the transport level (level 4), the X.25 link provides TCP (based on the
DARPA standard) and UDP. These Transport level protocols are used by
Internet/Berkeley Services, by NS, and by user application programs
that access the TCP/UDP and IP protocols.
The TCP protocol is a connection-based protocol. TCP verifies that all
data is delivered without duplication to its destination. The UDP
protocol, unlike TCP, has no concept of a connection. Messages are sent
as a unit with source and destination information in the header.
The X.25 link provides a BSD to PLP (Packet Level Protocol) translator
to allow access to PLP at level 3 for user-written application programs
via BSD IPC.
The X.25 link also provides an OTS to PLP translator to allow access to
PLP at level 3 for OSI Services via Xport OSI.
Chapter 119
About the X.25 Product
Packet/network Level (L3)
Packet/network Level (L3)
At the packet/network level (L3), X.25 link provides direct X.25
programmatic access via BSD IPC. For full details on X.25 programmatic
access, refer to the X.25/9000 Programmer’s guide (customer order
number: 36960-90050).
The X.25 link also provides IP access to TCP or UDP Transport protocols
for programs such as Internet/Berkeley Services and NS, allowing
communication over X.25 in accordance with RFC 877.
Chapter 120
About the X.25 Product
Data link (L2) and Physical (L1) Levels
Data link (L2) and Physical (L1) Levels
At the data link level (level 2), the X.25 link provides the LAP-B (Link
Access Procedure-Balanced) protocol. LAP-B is a data link protocol,
specified by the 1980 CCITT X.25 recommendations, that determines
frame exchange procedures.
At the physical level (level 1), the X.25 link provides support for X.21,
X.21bis, and V.35 interfaces (depending on your particular
communications hardware). These sets of recommendations define the
standards for X.25 at the physical level and apply specifically to
connections to a packet switching network. X.21bis (equivalent to V.24
and RS-232) is applicable to X.25 physical interfaces with transmission
speeds up to 64 kb/s. V.35, RS-449, X.21 and RS-530 supports
transmission speeds up to 2Mb/s. Other standards may also be supported
as they become available.
Chapter 121
About the X.25 Product
Data link (L2) and Physical (L1) Levels
Chapter 122
2Installation
Chapter 223
Installation
Before you Install the software
Before you Install the software
Before installing the X.25 link software, check the requirements below to
make sure that all required software and hardware has been correctly
installed and configured.
NOTEThis product is only supported on the system that is acting as a server. It
is not supported on client systems.
Hardware Requirements
This section describes the hardware requirements of the J2793B X.25
software for HP 9000 server systems.
If you have not already done so, install the X.25 interface card as
described in the hardware installation guide for your X.25 product. If you
are installing multiple X.25 cards, check the requirements in “Installing
Multiple X.25 Interface Cards” below.
If a modem connection is required, connect the X.25 card to the modem
or the modem eliminator according either to the modem vendor’s
specification sheet, or the instructions provided by the network provider.
Installing Multiple X.25 Interface Cards
When installing multiple X.25 cards,
•Always install the cards in adjacent slots in ascending slot order.
•Always install X.25 cards with the system shut down.
•Do not skip slots between X.25 cards.
Hardware Compatibility
•HP 9000 PCI bus
The High Availability feature can run on:
•PCI hardware cards, Product Numbers J3525A (2-ports) and J3526A
(4-ports)
Chapter 224
Installation
Before you Install the software
OS Platform and Version Compatibility
The version of the X.25 link software you’re installing must be
compatible with the version of HP-UX you’re running (for example,
HP-UX version 11.00 for B.11.00.05)
•Disk space required to install: 7 Mb
•Software install with system up or down? Up
•Single-user state required or recommended? No
•Reboot? Yes
Memory
Your X.25 link supports a high number of virtual circuits operating at
high baud rates. Since both X.25 and the BSD sockets API may store a
certain amount of data for each socket/circuit, HP recommends that you
check that your system has enough memory to handle the number of VCs
you plan to use. A few guidelines to help you are provided below.
Related Parameters
•Level 3 window size (W in formulas below) as configured in the
x25config file
•Level 3 packet size (P in formulas below) as configured in X.25
configuration file
•Socket buffer size (B in formulas below) used in your applications
(setsockopt() system call). The default is 4 Kb.
Evaluation Formulas The following formulas can be used to evaluate
X.25 memory requirements:
Memory for each VC (MVC) in bytes:
MVC = (B x 3) + (2 x (W + 1) x P)
Total Memory (TM) for X.25 in bytes:
TM = sum (MVC) + Number of cards x 5120
NOTEThese figures are only for protocol and API requirements. You should
also consider the memory required by your applications.
Chapter 225
Installation
Before you Install the software
Shortcut Method Assuming B = P for all VCs, TM can be rounded to:
•If B < 512, TM = approx. (1,536 + (2 x W + 2) x B) x No. of VCs
•If B > or = 512, TM = approx. (2 x W + 5) x B x No. of VCs
The following table (in bytes/VC) provides a quick guide:
Tab l e 2-1
Buffer Size (B) = Packet Size (P) in bytes
128256512102420484096
Window (W)
size
Example 2-1Example:
A system has two X.25 cards configured as follows:
Card 1:
Window = 2
Packet size = 1024
Socket buffer size = 4096 (default)
200 VCs are used
Card 2:
Window = 4
Packet size = 128
Socket buffer size = 4096 (default)
400 VCs are used
12 K2.5 K3.5 K7 K14 K28 K
22.3 K3 K4.5 K9 K18 K36 K
32.5 K3.5 K5.5 K11 K22 K44 K
42.8 K4 K6.5 K13 K26 K52 K
53 K4.5 K7.5 K15 K30 K60 K
63.3 K5 K8.5 K17 K34 K68 K
73.5 K5.5 K9.5 K19 K38 K76 K
Chapter 226
TM = (4096 x 3) + (2 x 3 x 1024)) x 200
+ ((4096 x 3) + (2 x 5 x 128)) x 400
+ (2 x 5120)
TM = 9,123,840 (8.7 Mb)
Installation
Before you Install the software
Chapter 227
Installation
Software Requirements
Software Requirements
Before installing the X.25 link product, make sure that the software
listed below has been correctly installed on your system. Refer to the
related publication if you need more information about any of these
products. If you cannot find the software or information you need,
contact your HP representative.
•HP-UX operating system version 11i or later – see HP-UX11i
Installation and Update Guide for HP Integrity Servers and HP 9000
Servers.
Chapter 228
Installation
Installing the X.25 Link Software
Installing the X.25 Link Software
Follow the steps below to install the X.25 link software:
Step 1. Insert the software media (tape or disk) in the appropriate drive.
Step 2. Type: swinstall.
(See the man page on swinstall for more information on this
command).
Step 3. Click on OK on the “Specify Source” window.
Step 4. Highlight J2793B in the “Software Selection” dialog, then select Mark
For Install from the Actions menu to install all file sets in the bundle.
If you want to select only certain file sets, double-click on the product
name to access the file sets that you want to mark for installation (each
time you double-click, you go down one level in the bundle structure).
Step 5. When you have marked the product components you want to install,
select Install (analysis) from the “Actions” menu.
Step 6. When you have successfully completed the analysis, click on OK from the
Analysis dialog to load the X.25 file sets.
The swinstall utility loads the file sets, runs the customized scripts for
the file set, and builds the kernel. Estimated time for processing: 8 to 10
minutes.
If the kernel build is not successful, the swinstall program returns you
to a new shell. The cause of the failure will appear at the end of the
/var/adm/sw/swinstall.log file.
Chapter 229
Installation
Installing the X.25 Link Software
Chapter 230
Loading...
+ 239 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.