32344 90002 NS3000 V Network Manager Reference Manual Vol1 May1987

32344-90002_NS3000_V_Network_Manager_Reference_Manual_Vol1_May1987 32344-90002_NS3000_V_Network_Manager_Reference_Manual_Vol1_May1987

User Manual: manual pdf -FilePursuit

Open the PDF directly: View PDF .
Page Count: 524

Download
Open PDF In Browser	View PDF

HEWLETT
(Ap] PACKARD

HP AdvanceNet

NS3000/V.

Networ k Manager Refere
Volume I

nee Manual
.

·,·~_II

READER COMMENT SHEET
UP AdvanceNet

NS3000/V Network Manager Reference Manual
Volume I
32344-90002 MAY 87

We welcome your evaluation of this manual Your comments and lugaestions help us to improve our
publications. Please explain your answers under Comments. below. and use additional pages if necessary.
b this manual technically accurate?

Dyes 0

Are the concepts and wording easy to understand?

o Y.

Is the format of this manual convenient in size. arrangement. and readability?

Dyes D No

DNo

Comments:

r
ThiI form requires no postage stamp if mailed in the U. S. For locations outside the U. s.. your local HP
representative will ensure that your comments are forwarded.
PROM:

Name
Company

Addrea

Date

-----

FOLD

111111

NO POSTAGE
NECESSARY
IF HAILED
IN THE
UNITED STATES

BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO. 1070 CUPERTINO. CA
POSTAGE WILL BE PAID BY ADDRESSEE
PUblications Manager
Hewlett-Packard Company
Infonaation Networks Division
19420 HOMstead Road
Cupertino. Calif. 95014

FOLD

HP AdvanceNet

NS3000/V
Network Manager Reference Manual
Volume I

~il~:~K':~
19420 Homestead Road, Cupertino. CA 95014

Part No. 32344-90002
E0587

Printed in U.S.A. JUN 1985
Edition 2. MAY 1987

NOTICE
The information contained in this document is subject to change without notice.
HEWLEIT-PACKARD MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS
MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not
be liable for errors contained herein or for incidental or consequential damages in connection with the
furnishing, performance or use of this material.
Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that
is not furnished by Hewlett-Packard.

This document contains proprietary information which is protected by copyright. All rights are
reserved. No part of this document may be photocopied. reproduced or translated to another language
without the prior written consent of Hewlett-Packard Company.
Copyright C> 1985,1986,1987 by HEWLETT PACKARD COMPANY

PRINTING HISTORY

New editions are complete revisions of the manual. Update packages, which are issued between editions,
contain additional and replacement pages to be merged into the manual by the customer. The dates on
the title page change only when a new edition or a new update is published. No information is
incorporated into a reprinting unless it appears as a prior update; the edition does not change when an
update is incorporated.
The software code printed alongside the date indicates the version level of the software product at the
time the manual or update was issued. Many product updates and fixes do not require manual changes
and, conversely, manual corrections may be done without accompanying product changes. Therefore, do
not expect a one to one correspondence between product updates and manual updates.

First Edition. . . .. .
JUN 1985
NOV 1985
Update 1.
Update 2. . . . . . .
.
JULY 1986
Update 3
NOV 1986
Second Edition. . . . . . . . . . . . .. MAY 1987. . . . ..

32344A. 00. 00
32344A. 00. 00
32344A. 00. 00
32344A. 00. 02
32344A. 00. 04

iii

LIST OF EFFECTIVE PAGES

The List of Effective Pages gives the date of the current edition and of any pages changed In updates to
that edition. Within the manual, any page changed since the last edition is indicated by printing the date
the changes were made on the bottom of the page. Changes are marked with a \fertlcal bar in the margin.
If an update IS incorporated when an edition is reprinted, these bars Are relTluved but the dates remain.
No information is incorporated Into a reprinting unless it appears as H prior update. To verify that your
manual contains the most current Information, check that the date printed at the bottom of the rage
matches the date listed below for that page.

Effective Pages
all

Date
.

MAY 1987

~
'-

PREFACE
Hewlett-Packard AdvanceNet .t. ·l combination of hardware and software products that make it possible
for Hewlett-Packard computer ~ystems to communicate with one another and with IBM mainframes.
The system to system or sYstem to network connections can be made over the coaxial cable of a local area
network, over hardwired \.lr leased lines, over the public telephone facility, or across X.21 or X.25
compatible Packet Switching Networks (PSNs), in any mixture.
This capability, coupled with
remote-entry capability to IBM computer systems, pnl\ Ides a total solution to large-company electronic
data processing (EDP) needs.
HP AdvanceNet allows a large
network of computer systems.
industrial functions within each
larger sense of tying together the

multidivisional corporation to have a truly coordinated world-wide
They are coordinated in the sense that the various commercial and
division and factory are tied together; they are also coordinated in the
various divisions and factories at the corporate level.

For example, imagine a large corporation which has factories in the United States, Canada. I'rance, and
West Germany. Within each factory there are HP 3000 computer systems performing such functions as
inventory control, factory data collection, and operations management.
With Hewlett-Packard
AdvanceNet data communications products, these manufacturing information sy--tems can be connected to
an HP 3000 system which handles the factory's administrative functions (such a~ finance and accountin,l
The administrative systems of each factory can, in turn, be connected not only to one another (via a 1000al
area network) but also (via remote job entry) to a large computer facility at corporate headquarters. This
overall networking capability makes it possible to perform financial analysis and control at a group and
corporate level as well as at the individual factories.

vii

I PREFACE (continued)
HP Network Services for MPE-V/E Based Systems CNS3000/V) is the HP data communications product
that enables your UP 3000 to communicate with other HP computer systems as part of a distributed
network. These systems can be other HP 3000s. HP 90005, HP 1000s and PCS. Networks that operate
over NS3000/V links can be interconnected to form a catenet, or internetwork. There are several
network link products for NS3000/V, as described below.
The following link products connect computers on a local area network using the IEEE 802.3 networking
standard:
• ThinLAN/3000 Link (includes ThickLAN option for thick coaxial cable)
• StarLAN/3000 Link
Two other link products enable you to establish remote connections to HP 3000s, as well as local
connections, uSing polnt-to-point networking technology:
• Asynchronous SERIAL Network Link for MPE-V IE based systems (Asynchronous 3000/V Link)
• NS Point-to-Point Network Link for MPE-V IE based systems (NS Point-to-Point 3000/V
Link).
Intended Audienee of this Manual
This manual is intended for those with a good deal of knowledge in data communications. Also required
is knowledge of the MPE-V operating system at the system supervisor level, and a familiarity with the
SYSDUMP dialogue, resource management and console commands.
Related Publications
The following HP pUblications contain additional information about Network Services (NS3000/V), the
MPE-V operating system, and the link products used with NS3000/V.

viii

PREFACE (continued)

General NS3000/V Link Manuals:
• NSJOOO/V Network Manager Reference Manual, Volume 1 (32344-90002)
• NSJOOO/V Network Manager Reference Manual, Volume 11 (32344-90012)
• NetIPCJOOO/V Programmer's Reference Manual (5958-8581)
• NS Message Formats Reference Manual (5958-8523)

Network Services Manuals:
• NS3000/V User/Programmer Reference Manual (32344-90001)
• NS Cross-System NFT Reference Manual (5958-8563)
• NS Cros.-System Network Manager Reference Manual (5958-8564)

HP ThickLAN Manuals:
• LAN Cable and Accessories Installation Manual (5955-7680) (For use with coaxial cable LAN

links)
• LAN3OO0/Y Diagnostic QIId Troubleshooting Guide (30242-90003)

(This manual is referred to as LAN/3000 Diagnostic and Troubleshooting Guide throughout this

manual set.)
• LAN Unk Hardware Troubleshooting Manual (5955-7681)

HP StarLAN Manuals:
• HP S'tuLAN PC

'0 HP 3000 Network Configuration Gulde (50906-90000)

• HP SttuLAN PlaMln, Gulde for PCs (50906-90020)
• HP StarLAN Hardware lutallatlon Manual for PCs (5959-2222)
• HP StarLAN PC Server Installation. Configuration, and Operation Guide (50904-90000)
• HP StarLAN PC Worlcnatlon Installation QIId Confl,uratlon Gulde (50906-90040)
• HP SIarLAN U.er's Gldde for PC. (50905-90000)
• HP StarLAN Dia,nostics and Troubleshooting Manual for PCs (50906-90060)
• HP 28647.4 Brid,e Inslallatlon and Reference Manual (28647-90001)
• HP 3026SA StarLAN/3000 UnIc Installation and Reference Manual (30265-90001)

IPREFACE (continued)
HP ThinLAN Manuals:
• HP30240A ThlnLAN/3000 Local Area Network Interface Contr'oller (LANIC} InstaUatlon and
Service Manual (30240-90001) (For sertes 37/MICR03000 vystems, part number 30240-90100).
• PC to HP 3000 Network Configuration Guide (S090Q-QO,:OO)
• HP ThinLAN Planning and Hardware Guide lor PCs (50909-90020)
• HP ThinLAN PC Server Installation, Configuration, and Operauon Guide (S0907-90000)
• HP ThinLAN Workstation Installation and Configuration Guide for PCs (S0909-90040)
• HP ThinLAN User's GUide lor PCs (50908-90000)
• HP ThinLAN Diagnostics and Troubleshooting Manual for PCs (50909-90060)
• HP2864SA ThlnLAN Hub Installation Manual (2864S-90000

UP SERIAL Manuals:
• HP SERIAL Network PC to HP 3000 Network Configuration Guide (50911-90000)
• HP SERIAL Network Planning and Hardware Guide (50911-90020)
• HP SERIAL Network PC Workstation Installation and Configuration Guide (50911-90040)
• HP SERIAL Network User's Guide (50910-90000)
• HP SERIAL Network Troubleshooting Guide (50911-90060)

Resource Sharing Manuals:
• Resource Swing: System Management (32597-90001)
• Resource Sharln,: Utilities (32597-90002)
• Resource Sharln,: HOlt Dla,nostics (32597-90003)
• Resource Sharing: Tape Backup User's Guide (35460-90902)
• Re60urce Sharln,: Tape Baclcup Administration (35460-90903)

PREFACE (continued) I

You may also wish to consult the following DS and DS-related reference manuals:
• DS/3000 HP 300010 HP 3000 User/Programmer Rejerence Manual (32185 -90001)
• DS/3000 HP 3000 to HP 1000 Rejerence Manualjor HP 3000 Users (32185-90005)
• DS/3000 HP 3000 to HP 3000 Network Administrator Manual (32185-90002)
• X.25 LIM for the HP 3000 Rejerence Manual (32187-90001)
• DS/IOOO-IY U,er's Manual (91750-90002)

These additional reference manuals provide documentation for the MPE operating system and several
subsystems available on the HP 3000:
• Fundamental Data Communications Handbook (5957-4634)
• HP 3000 Computer Systems. MPE JI Commands Rejerence Manual (32033-90006)
• HP 3000 Computer Systems. MPE V Intrinsics Reference Manual (32033-90007)
• HP 3000 Computer Systems, MPE Y System Operation and Resource ManGgement Reference
Manual (32033-90005)
• IMAGE/3000 Reference Manual (322 J 5-90003)
• QUBRY/3000 Reference Manual (30000-90042)
• KSAM/3000 Reference Manual (30000-90079)
• TwbolMAGE Reference Manual (32215-90050)
• Y /3000 Reference Manual (32209-90001)
• MPB File System Reference Manual (30000-90236)
• Workstation Conflgurtltor Reference Manual (30239-90001)

INP Manuals:
• HP 30020.4 INP Installation and Service Manual (30010-90001)
• HP 30020B INP Installation and Service Manual (30020-90005)
• HP 30244M INP Series 37 Installation and Service Manual (30244-90002)

I PREFACE (continued)
ATP Manuals:
• Point-To-Point Workstation I/O Reference Manual (30000-90250)
• Terminal (TERMDSM) On-Lme Diagnostic/Support Monito" Reference Manual (For MPE VIE:

30144-90013)
• HP 3000 Distributed Systems Network/Advanced Terminal Processor Off-line Diagnostic
Procedures Manual (30144-90003)
• Asynchronous Data Communications Channel-Main and Asynchronous Data Communications
Channel-Extended Diagnostic Manual (30010-90037)
• Advanced Terminal Processor (ATPj In.~tallation Manual (30144-900(;2)

Organization of the Manual
This manual is divided into two volumes. Volume I, wh ..;h describes network design and configuration,
contains the following sections:
Section I, Introduction, of this manual introduces the network architecture and product structure of
NS3000/V and associated links and describes each of the products in detail.
Section 2, Network Management, provides an overview of the tasks of network management. This section
also provides references to other sections that cover certain areas of network management in greater
detail.
Section 3, Network Planning and Configuration, explains concepts you will need to understand before
planning, configuring, and installing an NS3000/V network or catenet.
I

Section 4, System Configuration, discusses changes and additions to your original system configuration
which may become necessary due to changing circumstances at your installation. This section includes a
detailed explanation of I/O configuration for the drivers and virtual terminals. System parameters and
the SYSDUMP dialogue are also discussed.
Section 5, the Node Management Configurator (NMMGR), describes the operation of NMMGR, a utility
program that provides a series of VPLUS/3000 block-mode screens to display and accept configuration
information. The operation of NMMGR and the specifics of the utility screens are described.

xii

PREFACE (continued) I

Sections 6, 7, 8, 9, 10, 11, 12, and 13 provide the field definitions of the configuration screens used to
define the network configuration. These sections are organized as follows:
•
•
•
•
•
•
•
•

Section
Section
Section
Section
Section
Section
Section
Section

6, Guided Configuration
7, Link Configuration
8, Network Transport Configuration
9, LAN 802. 3 Network Interface Configuration
10, Router Network Interface Configuration
11, Gateway Half Network Interface Configuration
12, Loopback Network Interface Configuration
13, Logging Configuration

Section 14, Network Directory, describes how to create and maintain a master network directory of your
installation's network configuration.
Appendix A contains blank configuration worksheets to help you prepare for configuring you network as
described in Volume I, Section 3, "Network Planning and Configuration. II
Appendix B lists the supported modems for the NS3000/V product.
Appendix C describes how to convert configuration files.
Appendix D describes PC-to-HP 3000 communication.
Appendix E discusses NS versus DS INP configuration.
Volume II, which describes tasks performed after initial network configuration, contains the following
sections:
Section 1, Commands, describes the MPE commands for NS3000/V link products.
Section 2, Software and Line Verification, describes both the utilities available for software verification
and the line tests used to check that a node is communicating correctly with a network.
Section 3, Logging and Tracing, describes the NMS Trace/Log File Analyzer (NMDUMP).
Section 4, Changing the Network, describes how to change the network topology.
A glossary also is provided. For your convenience, the glossary is included with both volumes of this
manual.

xiii

',Y

!~
- ./

CONVENTIONS USED IN THIS MANUAL

NOTATION

DESCRIPTION

nonitallcs

Words in syntax statements which are not in italics must be entered exactly as
shown. Punctuation characters other than brackets. braces and ellipses must also be
entered exactly as shown. For example:

EXIT;

italics

Words in syntax statements which are in italics denote a parameter which must be
replaced by a user-supplied variable. For example:

CLOSE filename

[ ]

An element inside brackets in a syntax statement is optional. Several elements
stacked inside brackets means the user may select anyone or none of these elements.
For example:
[:]

( )

...

User mtI)' select A or B or neither.

When several elements are stacked within braces in a syntax statement, the user·must
select one of those elements. For example:

{A~}

User must select A or B or C.

A horizontal ellipsis in a syntax statement indicates that a previous element may be
repeated. For example:

[,itemname] ••• ;
In addition, vertical and horizontal ellipses may be used in examples to indicate that
portions of the example have been omitted.

A shaded delimiter preceding a parameter in a syntax statement indicates that the
delimiter must be supplied whenever (a) that parameter is included or (b) that
parameter is omitted and any other parameter which follows is included. For
example:

itema(litemb] [Iitemo]
means that the following are allowed:

itenr.r
itenrz,itemb
itema,itemb,itemo
i tenr:z , , i temo

ICONVENTIONS (continued)
When necessary for clarity, the symbol ~ may be used in a syntax statement to
indicate a required blank or an exact number of blanks. For example:
SET[(modifier)]6(~riable);

underlining

When necessary for clarity in an example, user input may be underlined.
example:

For

NEW NAME? ALPHA
Brackets, braces or ellipses appearing in syntax or format statements which must be
entered as shown will be underlined. For example:

LET

~r[lsubscriptl]

= value

Output and input/output parameters are underlined. A notation in the description
of each parameter distinguishes input/output from output parameters. For example:

CREATE (parmI ,parm2 ,ll:!Y1.!,error)
Shading represents inverse video on the terminal's screen. In addition, it is used to
emphasize key portions of an example.
) may be used to indicate a key on the terminal's keyboard. For
The symbol I
example, (RETURN) indicates the carriage return key.
IcomoLichar

xvi

Control characters are indicated by (CONTROLI followed by the character. For example,
(CONTROLlY means the user presses the control key and the character Y simultaneously.

CONTENTS

r-"
Section 1

INTRODUcnON
System Requirements. . . . . . . .. .
. . . . . . . . . . . .
. . 1-2
Network Architecture . . . . . . . .
.. . . . . . . .. . . . . . . .
. . . 1-3
The OSI Model . . . . . . . . . . ..
1-4
Types of Networks. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . 1-5
NS3000/V Network Types. . . • . • . . . . . . . . .
• . . • • 1-5
. . . . . 1-6
Network. Topology . . . . . . . . . . . . . • . . . . . . . . . . . . . .
Catenetl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .
. . . . . 1-7
Gateways and Gateway Halves. . . . . . . . . .
.
1-8
NS3000/V Architecture. . . . . . . . . . . . . .
.
1-9
Protocols. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . 1-1 0
1-11
051 Layer 4 (Transport Layer) Protocols
OSI Layer 3 (Network Layer) Protocols
. . . . . . . ..
I -II
OSI Layer 2 (Data Link Layer) Protocols. . . . . . . . . . . . . . . . . . . .
I -12
OSI Layer 1 (Physical Layer) Protocols . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Auxiliary Protocols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 3
Network Links.
.
1-14
Common Link Software . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . 1-14
IEEE 802. 3 Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
1-1 5
1-18
Medium Access Method for IEEE 802. 3 Links ..
Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Link Level Software. . . . . . . . . . . . .
. . . . . . . . . . . . I-I 9
1-20
NS Point-to-Point 3000/V Link. . . . . . . .. .
Direct Connect Links . . . . . . . . . • . . . . . . . . . . . . . • . . . . . . . • . . . 1-21
Dial Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Leased Lines. . . . . . . . . . . . . . • . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Hardware and Cables for Dial Links and Leased Lines
1-22
Asynchronous SERIAL Network Link . . . .. .
1-22
Hardware and Cabling . . • . . . . . . . . . . ..
.
1-23
Link Level Protocol . . . . . . . . . . . . . . . . . . . . • • . . . . . . . . . . . . . . 1-24
.Optional DS-Compatible Linb. . . . . . . . . • . . . . . . . . . . . . . . . . . . . . • 1-24
Personal Computers as NS3000/V Nodes . . . . . . . . • . . • . . . . . . . . . • . . . . 1-25
NS3000/V Network Services. . . . . . . • • . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
Services Available . . . • . • • . . . . . . . . . . . • • . . . . . . . . . . . . . . . . . 1-26

Section Z
NETWORK MANAGEMENT
Network Management Tasks . . . . • . . . . . . . . . . . . . • • . . • . . . . . . . • . • . . 2-2
The Network and Catenet Management Lifecycle. • . . . . . • . . • .. . .•... 2-3
Network Management Tools. . • . . . . . . . . . . . . . . . . . . . . . .
. . . . . . 2-3
MPE Commands and Utilities . . . . . • . • . • • . • . . • . . . . • . • . . . . • . . . 2-4
Node Management Servicea • . • • . . . . • • • . • . . . • • • . • • • . . . . . • . . . 2-5
CS/3000 Utilities. •.•...•••••••.•.•.••....•.••.••.••.•... 2-6
Link Level Toola and Utilities . . • . . . . . • . . • . . . . • . . . . . . . • . . . . . . 2-6

xvii

CONTENTS (continued)

Installing NS3000/V Links. . . . . . . .
.
Customer Installation Tasks for All NS3000/V Links
Additional Tasks for IEEE 802.3 Links
HP Installation Tasks.
.
Installing Network Services . . . . . . . . . . . . . . . . . . .
Configuration and Initialization Overview
Network and Configuration' Planning
System Configuration. . . . . . . . . . . . . . . . . . . . .
Network Configuration with NMMGR. . . . . . . . . .
Configuration Verification
Network Directory

'
' ..
... .
.. . .
.. . .

2-7
2-7
2-9
. . . . . . . ..
2-9
. . . . . . . . . . 2-10
2-10
2-13
.. .
2-13
. .. .
2-14
2-14
2-15

Section 3
NETWORK PLANNING AND CONFIGURATION
3-2
Software Components.
NS3000/V Software Subsystems. . . . . . . . . . . . . . . . . . . . . .
3-2
Configuration Files .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
. 3-2
Configuration Concepts
3-3
NS R.outing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • . . . . . 3-4
Intranet Routing
3-4
Internet Routing
3-5
Symbolic; Names
3-6
Node Names
3-6
Other Names
3-7
Network Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • . . . 3-8
IP Address Format and Assignment
3-8
IEEE 802.3 Station Address Format and Assignment
'•.... 3-10
Address Resolution
3-10
Node Name to IP Address Resolution
3-10
IP to Subnet Address Resolution
3-12
Configuration Terminology
~
3-13
General Terms . . . . . . . . . • . . . . . . . . . . . . . . . . . . . . . . . • . . . . . 3-13
Dial Link Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 3
Router Network Terms
3-14
Gateway Terms
3-1 S
Non-Operational Links
3-16
Router Network Automatic Rerouting . . . . . . . . . . . . . . . . . . • . . . . . 3-16
Internet Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • . . . . 3-19
Network Installation and Administration . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ~ . . • . . . . . . . 3-24
Software and Hardware Installation. . . . . . . . . . . . . • . . . . . . • . . . . . . . 3-24
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . • . . . . . . . . . . • • • . . . 3-25
SYSDUMP Configuration. . • . . . . . . . . . . . . • . . . . . . . • . • . . • • • . . 3-26
NMMGR Configuration . . . . . . . . . . . . . . . . . . . . . . . . . • . . . . . . . 3-26
Nodal Validation t Verificatio~ and Synchronization . . . • . . . . . . . • '..•.. 3-17

xviii

CONTENTS (continued)

Network Startup. .
Line Verification
. . . ..
.
Network and Catenet Design Considerations. . . . .
.
Line Speed. . . . . . . . . . . . . . . . . . . . . . . .
.
Geoaraphical Location. . . . . . . . . . . . . . . .. .
Special Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dial Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .
Personal Computers. . . . . . . . . . . . . . . . . . . . . . . . . . .. .
Other Non-HP 3000 Nodes. . . . . . . . . . . . . .
.
OS-Compatible Links. . . . . . . . . . . . . . . . . . .
... . . . •. . . .
Network Interfaces and Design. . . . . . . . . . . . . . ..
.. . . . . . . . . . .
Number of Network Interfaces. . . . . . . .
. . . . . . . . . . . . . . . .
Gateways. . . . . . . . . . . . . . . . .. ....
. . . . . . . . . . . . . . ..
Network Boundaries. .. . . . . .
. .. . . . . . . . . . . . . . . . . . . . . . .
Network Implementation and Support Plan
Network Maps and Configuration Worksheets
Configuration Worksheets: Terminology
Confiauration Worksheets: Instructions
Catenet Worksheets. . . . . .
Catenet Map
Communication Between Networks . . . . . . . . . . . . . . . . . . . . . . • . . .
Network Boundaries. . . . . . . . . . . . . . . . . . . . . .. . . . . . . • . . . • .
IP Network Addresses. . . . . . . . . . . . .
. ...........•..•.
Completing the Catenet Table. . . . . . . . .
.
Network Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . • . . . . . . . . . .
LAN Network Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . • . . . .
Router Network Worksheets. . . . . . . . . . . . . . . . . . . . . . . . . • • . . . .
Gateway-Half Pair Worksheets
Node Worksheets. . . . . . . . . . . . . . . . . . . . . . . .. .
LAN Node Internet Routing. . . . . . . . . . . . .. .
Router Node Routing Information . . . . . . . . . . . . . . . . . • . . . • . . . . .
Gateway Half Information for Node Worksheets ...••..•...••.••..

3-28
3-28
3-29
3-29
3-29
3- 30
3-30
3-30
3-30
3- 30
3-31
3- 31
3-31
3- 32
3-33
3-33
3-36
3-38
3- 39
3-39
3-39
3-40
3-40
3-41
3-43
3-44
3-47
3-53
3-57
3-59
3-62
3-69

Section 4
SYSTEM CONFIGURATION
System Configuration. . . . . . . . • . . . . . . . . . . • . • • • • . . • . . . . . . • . . . . . 4- 2
I/O Configuration. . . . . . . . . . .. . . . • . . . . • . . . . . . . • . . • • • . . . • . 4- 3
Type 16, Subtype 0, 8 -- Virtual Terminals . . . . . . • . . • . . . . • . . • . . • • 4-9
Type 17, Subtype 9 -- LANIC Driver. . . . . . . . . . • . . • • . • . • • . . . . . . 4-9
Type 17, Subtype 0, 1, 3 - - INP Driver. • . . . . . • . • . . . • . . . . . . . . . . 4-10
Type 41, Subtype 0, 1 -- Communications Driven . • . . . . . . . . . . . . . . 4-13
Type 42, Subtype 0, 1,2 -- ATP Devices. . . . • . . • . . . . . . . . . . • . . . . 4-14
Recommendations for System Parameten . . . .. ..••...•...••..•.. 4-15
Virtual Terminal Configuration Dialogue. • . . .. .... . . . . . . . • • . • . . . 4-19
LANIe Configuration Dialogue . . . . . . • . . • • • • • . • • . . • . • . . . • • . . . . . 4- 21
INP Configuration Dialogue ..••..•...••.....•••••••..••.••.•• 4-22
l>evice Driver (IOINPO). . . . . . . . . . . . . . . . . • . • • • • • • . • • • • • • • • • • 4-22
Communications Driven (lODSO and 10DSX). . • . . . . • . . • . . . . • . . . . . . 4-25

xix

I CONTENTS (continued)

ATP Configuration Dialogue
4-27
Completing the SYSDUMP Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4- 30
Configuration Examples
4-34

Section 5
THE NMS CONFIGURATOR (Nr.IMGR)
Getting Started with NMMGN.
5-2
The Open Configuration/Directory File Screen
5- 3
Specifying the Configuration File Name
5-5
Opening or Creating the Configuration File
5-6
The Main Menu Screen
5-6
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • . . . . . . . 5-7
NMMGR Screen Structure
5-8
Configuration Files . . . . . . . . . . . . ..
.
5-9
Using NMMGR Configuration Screens. . . . . . . . . . . . . . . . . . . . . . . . . .. 5-12
General Operation of Screens
5-12
The Header and Message Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Data Flag
5-13
Path Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • . . . . . . . . 5-13
File Name
5-14
Command Window and the Enter Key
5-14
Screen Fields
5-17
Prior Screen Key
5-18
Refresh Screen Key
5-19
Menu Screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • . • . • . . 5-19
Select Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • . • . 5-20
Data Screens
5-23
Using NMMGR Utility Screens
5-26
Output Configuration File
5-27
Print Tree and Display Tree
5-28
Print Data ..•••........•.•...•..•••.••..•••..••••••. 5- 30
Print Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . • . . . . . . . . . . 5- 30
PrintSubtree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • . • . . . 5-33
Compress Configuration File . . . . . . . . . . . . . . . . . . . . . . . . • • . . • . . . 5-33
Validate Configuration File . . • . . . . . . . . . . . . . . . . . . • • . . . . . . . . . . 5-35
Configuration Subtree Copy. . . . • . . . . . . . . . . . . . . . . • . • . . • . • . . . • 5-40
The Error Information Screen. . . . . . . . . . . . . . • . . . . . . . . • . • . • . . . . 5- 43
Copying Configuration Data ...........•..••..••••.••...•..•.. 5-46
Making Configuration Changes ..............•..•..•..•.•...••. 5-48

section 6
GUIDED CONFIGURATION
Conecting Configuration Erron...•.....•...•••••..•••..••..•... 6-4
Netxport Configuration . . . . . • . . . . . . . . . . . . . . . . . . . . . . . • . • . . . • . . 6-5
Netxport Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • . . . . . • . . • 6-13

CONTENTS (continued)

Section 7
LINK CONFIGURATION
Link Configuration
Link Configuration:
Link Configuration:
Link Configuration:
Link Configuration:
Link. Configuration:
Link Configuration:
Link Configuration:
Link Configuration:
Link Configuration:
Link Configuration:
Link ConfiguratIon:

LAN 802. 3 Link Data. . . . .
LAN802.3 Link Trace Data.
BSC Link Data. . .
BSC Link Trace Data. . . .
Bse Link Phone Data. . . ..
LAP-B Link Data
LAP-B Link Trace Data. . .
LAP-B Link Phone Data. . .
ASNP Link Data. . . . . . . .
ASNP Link Trace Data
ASNP Link Phone Data

. . . . . . . . . . . . . . . . . . "
.
. . . . . . . . . . .. .
. . . . . . . . . . . . . . ..
. ..
. . . . . . . . . .
. . . . . . . . .
. . . . . . . . . .

.
.
. . . . . .

7-3
7-6
7-8
7-11
7-14
7-17
7-19
7-22
7-25
7- 27
7-29
7-32

Section 8
NETWORK TRANSPORT CONFIGURATION
Network Transport Configuration Selection . . . . . . . . . . . . . . . . . . . . . ..
Node Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .
Node Name Configuration
Global Transport Configuration
General Protocol Configuration
Internet Protocol Update Configuration
Packet Exchange Protocol (PXP) Configuration. . . . . . . . . . . . . . . . . . . . . ..
Transmission Control Protocol (TCP) Configuration
Network Interface Configuration

. 8-3
8-4
8-5
8-7
8-10
8-11
8-14
8-17
8-21

Section 9
LAN802.3 NETWORK INTERFACE CONFIGURATION
LAN 802. 3 Network Interface Configuration. . . .
Protocol Configuration. . . . . . . . . . . . . . . . . .
Internet Protocol Configuration
Probe Protocol Configuration
LAN 802. 3 Network Interface Link
Lan Link Configuration
Neighbor Gateways
Neighbor Gateway Reachable Networks. . . . . . .
LAN802.3 Mapping Configuration. . . . . . . . . .
Static Neighbor Node Configuration (LAN 802. 3)

. . . .. .
. . . . . . . . ..

.. . . . . .
. . .

. . . ..

.
.

9- 3
9-6
9-7
9-10
9-13
9-15
9-17
9-19
9-22
9-24

xxi

ICONTENTS (continued)
Section 10
ROUTER NETWORK INTERFACE CONFIG\JRATION

Router Network Interface Configuration
Router Network Interface Protocol Configuration
Internet Protocol Configuration
Dial ID Protocol Configuration. . . . . . . . . . . . .
Security String(s) Configuration
Router Network Interface Links. . . . . . . . . . . .
Direct Connect Link Configuration. . . . . . . . . .
Router Dial Link Configuration. . . . . . . . . . . .
Neighbor Gateways
Neighbor Gateway Reachable Networks
Router Mapping Configuration..
Router Reachable Nodes. . . .
....... ... .

10-3
. . . . . . . . . . . . . . . . . . . . 10-7
10-8
. . . . . . . . . . . . . . . . . . . 10-11
10-14
..
.. . . . . . . . . . . . . . 10-16
. . . . . . . . . . . . . . . . . . . 10-19
. . . . . . . . . . . . . . . . . . . 10-21
10-23
10-25
10- 28
. . . . . . . . . . . . . . . . . . . 10- 32

Section 11
GATEWAY HALF NETWORK INTERFACE CONFIGURATION

Gateway Half Network Interface Configuration.
Protocol Configuration. . . . . . . . . . . . . . . . .
Internet Protocol Configuration . . . . . . . . . . .
Dial ID Protocol Configuration. . . . . . . . . . . .
Security String(s) Configuration
Gateway Half Network Interface Link. . . . . . .
Direct Connect Link Configuration. . . . . . . . .
Gateway Half Dial Link Configuration
Neighbor Gateways. . . . . . . . . . . . . . . . . . .
Neighbor Gateway Reachable Networks

.
.
.
.

. 11-3
. 11-6
. 11-7
11 -10
11-13
. . . . . . . . . . . . . . . . . . . . 11-15
. . . . . . . . . . . . . . . . . . . . 11-1 7
11-19
. . . . . . . . . . . . . . . . . . . . 11- 22
11-24

Section 12LOOPBACK NETWORK INTERFACE CONFIGURATION

Loopback Network Interface Configuration
12-2
Protocol Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . • . . . . . . . . . . 12-4
IP Protocol Configuration
12-5
Section 13
LOGGING CONFIGURATION

Logging Subsystems Selection
13-4
Logging Classes Selection
13-6
Logging Class Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • . . . . . . . . 13-8

xxii

CONTENTS (continued)

Section 14
NETWORK DIRECfORY

What a Network Directory Provides
Path Report Lists. . . . . . . . . . . . .
Global and Local Entries. . . . . . . .
Roles and Interfaces. . . . . . . . . . .
Configuration Screens
Network Directory Main Screen. . . . .
Select Node Name Screen • . . . . . . . .
Network Directory Data Screen
Directory Maintenance Mode Interface
OPENDIR. Command . . . . . .
DELETENODE Command. . . . . . .
MERGEDIR Command. . . . . . . . .
LISTDIR Command. . . . . . . . . . .
EXPANDDIR Command. . . . . . . .
HELP Command. .
:MPE Command • . . . • . . . . . . . .
EXIT Command . . . . • . . . .
MAKESTREAM Command .
LISTDIR Command Sample Output
0

•

14-2
. . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
. . . . . . . . . . . . . . . . . . . . . . . . . . . 14- 3
. . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
14-6
. . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7
.. . . . . . . . . . . . . . .
14-9
14-11
. . . . . . . . . . . . . . . . . . . . . . . . . . 14-14
14-1 S
. . . . . . . . . . . . . . . . . . . . . . . . . . 14-1 S
. . . . . . . . . . . . . . . . . . . . . . • . . . 14-16
. . . . . . . . . . . . . . . . . . . . . . . . . . 14-17
. . . . . . . . . . . . . . . . . . . . . . . . . 14-1 7
14-1 8
14-1 8
14-1 9
14-19
14-22
0

•

••••••••••••••

•••••••

•

Appendix A
WORKSHEETS

Appendix B
SUPPORTED MODEMS

Appendix C
CONVERTING CONFIGURATION FILES

Using the Conversion Proaram ...

•

C-l

Diii

CONTENTS (continued)

Appendix D
PC-TO-HP 3000 COMMUNICATION
Requirements for ThinLAN/3000, StarLAN/3000, SERIAL links. . . . . . . . .. D-2
Software Required
D-2
HP 3000 Server Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. D-2
HP 3000 Host Software
D-2
Software for a PC Workstation Using Server Resources
D-2
Software for a PC Workstation Used as a Terminal . . . . . . . . . . . . . . .. D-3
Related Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. D-4
Hardware and Software Installation. . . . . . . . . . . . . . . . . . . . . . . . . . .. D- S
For HP 3000s
D-S
For PC Workstations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • . . . D-6
HP 3000 Logon and Shortname Correspondence
D-6
Configuration Procedures Summary
D-7
PC Workstation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. D-7
Configuring the HP 3000
D-8
Configuring Additional Virtual Terminals. . . . . . . . . . . . . . . . . . . . .. D-8
Configuring the UP 3000 Network Config. File (NSCONF. NET. SYS) . • .. D-9
Assigning HP 3000 Logons. . . . . . . . . . . . . . . . . . . . . . . . . . . . • . . . . . D-l S
Appendix E
DS vs NS INP Configuration

Glossary

Xliv

_I_N_TR_O_D_U_C_TI_O_N

HP Network Services for MPE-V Based Systems (NS3000/V) is an HP data communications product that
provides networking capabilities to interactive users and applicatlon programs on HP 30008 running the
MPE-V operating system. Through the use of NS3000/V, these HP 30001 can be connected to other HP
computer systems in a distributed network.
NS3000/V consists of two parts: NS3000/V Services and NS3000/V links. NS3000/V Network Services
consilt of software that enables usen to access data, initiate processes, and exchange information among an
the lYItems on a network. NS3000/V links provide connections among systems (either HP 30008 or
penonal compulen) in the same network. To use NS3000/V Services, the systems must be connected by
an NS3000/V network link.
A variety of network link products are available with NS3000/V. The link product that connects
individual systems in an NS3000/V network can be any of the following:
• NS Point-to-Point Network Link for MPE-V Based Systems (NS Point-to-Point 3000/V Link)
• Asynchronous SERIAL Network Link
• StarLAN/3000 Link
• ThinLAN/3000 Link (includes ThickLAN option for thick coaxial cable, described below)

The link products listed above can all be used to connect HP 30008 to one another.
The Asynchronous SER.IAL Network Link, StarLAN/3000, and ThinLAN/3000 can connect HP 30008 to
penonal computen as well as to other HP 30008.
The ThinLAN/3000 Link, including the ThickLAN option, can also connect HP 30008 with HP 1000s
and HP 90008.
ThinLAN/3000 Link. connections are usually made with thin (.18 inch) coaxial cable; however, you can
also use thicker (.4 inch diameter) coaxial cable, available by ordering the ThickLAN option of
ThinLAN/3000.
Table 1-1 shOWI available links and the kinds of connections they can make-- whether between HP
30001 or between HP 30008 and penonal computers.

1-1

Introduction
Table 1-1. Link Types and Connections
Link Type

3000 to 3000

NS Point-to-Point 3000/V Link

Asynchronous SERIAL Network Link

ThinLAN/3000 Link (including
ThickLAN option)

StarLAN/3000 Link

PC to 3000

(MICRO 30005,
MICRO 3000XEs, Series
37s, and Series 37XEs
only)

Although NS3000/V Services all require a network link to operate, network links can be purchased
without the concurrent purchase of NS3000/V Services.
Network links differ in their supporting hardware, software and in some cases, function. Later subsections
of this "Introduction" describe these links and discuss the differences among them.

SYSTEM REQUIREMENTS
NS3000/V is supported on the HP 3000 Series 37/37XE/39/40/42/44/48/58/64/68/70 and the
MICRO 3000 and MICRO 3000XE, executing the MPE-V/E operating system, V. U.F. G. 02. 03
(U-B-delta-3) MIT or later versions. The system must have a minimum of two megabytes of memory and
the Expanded System Table Microcode. (Systems that are now memory-limited should add one megabyte
to maintain current performance.)

1-2

Introduction

NETWORK ARCHITECTURE
Before you understand the details of NS3000/V links and services, you should understand some general
concepts about network architecture and NS3000/V. This section will familiarize you with concepts and
terms you will encounter later in this manual.
A network is a group of computer systems connected in such a way that they can exchange information
and share resources. In a distributed network, as opposed to a centralized one, the connected systems are
independent and equal. One system does not control another system.
NS3000/V networks are distributed networks. Systems that are configured into an NS 3000 network are
called nodes. Through participation in a distributed network, users on your system. or loealnode, can use
the processing and storage facilities of another system, or remote node; usen at remote nodes can take
advantage of the resources of your local node.
A "oup of networks that are connected to each other is called a eatenet One network is connected to
another by means of a node called a gateway node.
The plan that defines the characteristics and interactions of the hardware and software used to connect
nodes into a network is called a network architecture. Typically, the software is organized as a series of
layen. The user interface is integrated into the top layer and the hardware is integrated into the lowest
layer. Hence, a message, composed of data and information necessary to transmit the data to its
destination, is sent from the user down through the layers and out onto the network; when the message is
received at the remote node, it is passed up through the layers to the remote user.
Layers are required to handle the many tasks involved in translating a message into a form appropriate
for the hardware connection to the network, or back into a form understandable to the remote user,
depending on whether the message is incoming or outgoing. Each of the layers between the user and the
hardware is assigned certain well-defined tasks. Each layer must accomplish its task and pass the message
on, in a particular format, to the layers above or below it.
The rules and conventions that define the functions to be performed and the format of messages that are
exchanged by each architectural layer are called protocols.
Individual layers can be designed,
implemented, changed, or updated in any manner their creators choose, as long as they provide the data in
the correct formal This also makes it easy to pinpoint and correct errors. because each task is done in a
specific layer of the architecture.
Until recently, each computer products company developed its own network architecture as part of the
design of its data communications products. For example, Hewlett-Packard developed the Distributed
Systems Network (DSN) architecture, a five layered design that uses HP proprietary protocols. The DSN
architecture is used by all HP Distributed System Network products, such as DS Network Services for the
HP 3000 (DS/3000) and DS/IOOO-IV. Similarly, IBM developed the System Network Architecture
(SNA), a six layered design that uses IBM proprietary protocols. Many HP data communications products
can communicate in an SNA environment, such as SNA Link Services for the HP 3000 (SNA Link) and
Network Remote Job Entry for the HP 3000 (SNA NRJE).
However, using proprietary protocols and designs can be limiting for data communications applications.
Over time, standards have been developed for the tasks and protocols of data communications, ltartina
with the physical connectors. An internationally accepted set of standards based on an architecture
known as the IOSI model" is under development by participants from many c=ountries.

1-3

Introduction

The OSI Model
The International Standards Organization (ISO), an agency of the United Nations, developed the first step
in the standardization of network architectures by defining the Open Systems Interconnection (OSO
Reference Model. The OSI model defines seven architectural layers and specifies the function of each.
Figure 1-1 illustrates the 051 model.

Layer

Task

Application

Presentation

Session

Transport

Network

Data Link

Physical
Figure 1-1. The Seven Layers of the 051 Model

• Layer "1 (Application) is the user interface to remote services.
• Layer 6 (Presentation) manipulates ·user data, such as in text compression and encryption.
• Layer 5 (Session) negotiates connection establishment at remote nodes.
• Layer 4 (Transport) is responsible for end-to-end data integrity. This means that the Transport
Layer is responsible for ensuring that the message arrives at the correct remote node, without
erro~ even if the message had to pass through any intermediate nodes.
Layers S - 7 also provide end-to-end services, while Layers 1 - 3 are only responsible for data
integrity between each node.
Layer 4 protocols can provide the following services to upper layen: in-order message delivery,
retransmission of lost messages. suppression of duplicate messages and flow control.
• Layer 3 (Network) determines the routes messages take to get from one node to another. This
layer ean be split into two sub-layers: 31 and 3s. Layer 3i handles routing between networks
(internetwork), and 3s handles routing within a network (intranetwork).
• Layer 2. (Data Link) eheeks for and correets transmission errors over the physical link.
• Layer 1 (Physical) transmits the electrical signals over the link.
The funetions of each layer are performed by software that adheres to established protocols. The protocols
used by NS3000/V are described later in this section.

1-4

Introduction

Types of Networks
Computer networks can be broadly classed as of two typa: broadcast networks and point-to-point
networkl. Nodes on a broadeast Detwork share the .me communicatioDi chaDDel, over which data iI
transmitted to an the nodes in the network. Networks usin, lIP ThiDLAN. includin, the ThickLAN
option, or HP StarLAN links are broadcast networks; the protocol that they use ",OtUlctUl6 me-ps to aD
the systems on the LAN.
Point-to-point Detworks, on the other hand. are networks in which data is transmitted from node to node
in a network over a defined route until it reaches a specific destination. Because data is paaed from one
node to another, one node at a time, the meanlof tranlmittin. data over point-to-point networks iI caned
the store and forward technique. When a message is received at an intermediate node, it is forwarded to
either another intermediate node or to ita final destination. Point-to-point networks are IOmetim.
referred to as router networks. The term route, is used within this manual to refer to point-to-poiat
networks. The Point-to-Point 3000/V Link and the AsynchronoUi SEIUAL Network Link can both be
used to connect nodes in a router network.

NSlOOO/V Netwodt 'fypes

An NS3000/V network can be of two types:

• A router network

An IEEE BOZ.3 local area network

These types COrresPOnd to the types of networks--broadcast and point-to-point --previoUlly described.
The NS3000/V IEEE 802. 3 local area network is a broadcast network based on standards published by
the Institute of Electrical and Electonics Engineers (IEEE). The standards are called '1EEE 802. 3- (and a
related standard is called IEEE 802. 2~ therefore, the kind of network it specifies is called an "IEEE 802. 3
network. II
The NS3000/V router network is a point-to-point network that uses the store-ud-forward technique.
Certain NS3000/V link types can be used for each network type, as shown in Table 1-2:

1-5

Introduction
Table l-Z. Network and Link Types
NS3000/V Network Type
Router

IEEE802.3

NS3000/V Link Type
NS Point-to-Point 3000/V Link
Asynchronous SERIAL Network Link
ThinLAN/3000 Link
(including ThickLAN option)
StarLAN/3000 Link

As Table 1-2 shows, NS3000/V router networks can use NS Point-to-Point 3000/V and Asynchronous
SER.IAL Network Links to connect nodes. IEEE 802.3 networks can use the ThickLAN option,
ThinLAN/3000, and StarLAN/3000 Links.

Network Topology
The topology of a network refers to the physical arrangement of its nodes. For example, one type of
common topology is a bus topology, in which all nodes are directly linked. Another type is a star topology,
in which all nodes are linked in a radiating fashion to a central node or switching device.
The possible topologies for a given network are determined by the type of link used to connect the
network's nodes.
For example, a bus topology can be used only for a broadcast network, such as an IEEE 802.3 network.
Figure 1-2 shows a bus topology, in which network nodes (represented by numbered circles) are joined to a
common bus.

Figure 1-2.. Bus topology.
Point-to-point networks cannot use a bus topology. Instead, point-lo-point networks must use a topology
in which each network node is connected to at least one other node. Data is passed from one node to
another, including through any intermediate nodes, until it reaches its destination. NS Point-to-Point
3000/V and Asynchronous SER.IAL Network Links can be used to create point-to-point, or router
networks.

1-6

Introduction

The actual topolopes that can be used for point-to-point networks are widely varyiq; poaibilitia
include star, ring, hierarchical (sometimes referred to u a tree topology) and string. Any arranpment of
nodes will work as long as each node is connected to at least one other node in the laDle network. Figure
1-3 WUltrateB several possible topologies for point-to-point networks.

Ring

Complete

Irregular

Star

String

Hierarchical

Figure 1-3. Point-to-point topolOlies.
Nodes that are directly connected to only one other node in point-to-point networks are referred to u
leo/llOde8. In the illustration above, each of the endpoints of the star topology are leaf nodes. u are lOme

of the nodes in the string, hierarchical, and irregular topologies.
computen ean be used only as leaf noeles.

In NS3000/V networb. personal

eatenets
Two or more networkl ean be linked together to form an internetwork or eate.t (derived from
co~atelUlt«l networks). For example, if you wanted to connect the noda in a router network with the
noda in an IEEE 802. 3 network, the combination of the two networks would be called • catenet.
Creation of a catenet allows any Dode on one network to communicate with any node on another network
that is part of the a.me catenet. Up to 256 individual networb c:an belon, to the l&IIle NS3000/V
catenet.
The divisions between the networks in a catenet are called network boundartea. Figure 1-4 moWi a
catenet, with a network boundary indicated by a dashed line.

1-7

Introduction

Gateways and Gateway Halves
Networks in the same internetwork are joined together by gateway nodes. A gateway node is a node that
is a member of two or more networks and allows communication between the networks to which it
belongs. Communication between networks is also called internetwork communication. For example. in
Figure 1-4. Node II belongs to Network C and to Network D; it serves as a gateway between Networks C
and D. Internetwork protocols determine how data and associated messages are routed through multiple
networks. In the example (Figure 1-4). the internet protocol used determines how data and associated
messages are routed from one network to the other. NS3000's Internet Protocol (I') is based on the
DARPA (Defense Advanced Research Projects Agency) standard for an internetwork protocol.

If Node 7 in Network C wants to send a message to Node 14 in Network D, Node 7'8 message would be
sent to Node 11. Node II would then send the message to Node 14. All datacomm traffic from Network
C to Network D must go through Node 11. the gateway to Network D.

Network C

Network D

Figure 1-4. Gateway (Node 11).
Networks can also communicate via gateway halves. A gateway half is a degenerate case of a gateway;
instead of·..one gateway node providing internetwork communication. two gateway halves are needed.
Each gateway half belongs to only one of the networks that it links; each has a Gateway Half link over
which it is connected to the other gateway.

Network C

Network D

Figure 1-5. Gateway Halves (Nodes 11 and 12.).

1-8

Introduction
For example. in Filure 1-5. Node 11 is a gateway halt t ltat btal~tnp to Network C. and Node 11 ia a
pteway half that belonll to Network D. The lint between Nodes J 1 and 12 is a Gateway Half lint.
Messales from Network. C destined for Network D are fint sent to Node 11. the lateway half for
Network C. Node 11 lends the me_Ie to Node 11. which is Network. 0-, pteway half. Node 12 then
routa the meaaae to the appropriate node in Network D
A node can be a pteway and a gateway half. If a node has three linb and beloll" to two networu. it
would be a pteway to the two networks that it belonls to, but a pteway half to the network to which it
did not beiOBl. For eomple. in Filure 1-6. Node 5 is a member of Networks A and B. and ia a pteway
between them. A1thou.h Node 5 bas a link to Network C, it does not belonl to Network. C ud 10 iI a
p.teway holt to that network.
Networt< 8

Network A

Network C

Figure 1-6. Catenet.

NS3000/V Architecture
NS3000/V is composed of two Part&: NS3000/V Services and NS3000/V Links. NS3000 Servicea perform
functions of layer 5 (Session layer~ layer 6 (Presentation layer~ and layer 7 (application layer) of the OSI
modeL Each of the available NS3000/V links performs the functions of layen 1 throulh 4 of the OS!
modeL Pipre 1-7 shoWi the relationship of NS3000/V Services and Links to the OSI modeL

1-'

Introduction

Network ServIces

Network Sentcea

0234~tJR)

I
NetiPC
I

TCP

pxp
Network

Transport

I
I

COSIlavers
3 and 4

Probe

}

lAP-a
or
esc

ASNP

lANlC

INP

ATP

IEEE
802.3

Network
link
(OSllayers

I
8tIILW3OOO
C3O&AI

Paint...,

NS"*'t...-

Aaync:tnnu

SERIAL
NItwartc U*
e:torlOCJ:W

ThiOHI3OOO
C3024CW
1NllMNt
aptIanaf
1IIMNU3OQO

tandZ

c:JQ2IMA-fcIr
Nb'o 3000

trdSerta3n

C3028M-r.
8IrtII3I-Ja

Figure 1-7. NS3000/V Architecture.

Protocols
The protocols, or rules that specify the format of each NS3000/V architectural layer ensure that
NS3000/V communication occurs successfully. Some protocols, such as the protocols for layers 3 and 4
(the Network and Transport Layers. resp ectively) are used by all network nodes, regardless of the type of
links that connect them. Other protocols, such as those for layers 1 and 1 (the Physical and Data Link
Layers. respectively), differ depending on what kind of link and what kind of network is beina used.

1-10

Introduction
This section briefly describes the protocols used by NS3000/V fUI various network layen, and explains the
variations associated with different network link types. I·'igure 1-7 shows the protocols used for each
type of network link. Figure 1-7 also shows the composition of NS3000/V link products. Each link
product consists of software and hardware that performs the functions of layers I through 4 of the OSI
model. NS3000/V Network Servicel consists of software that pp"fnrms the functions of layen 5 throuah
7 of the OSI model.
As Figure 1-7 also shows, the software and hardware comprising each NS3000/V link product can be
divided into two main portions: the Network Transport and tht Network Link. The Network Transport
software performs the functions of layers 3 and 4 of the OSI model. The Network Link hardware and
software performs the functions of layers 1 and 2 of the OSI model.

The protocols that are implemented by the Network Transport and Network Link software and hardware
are described in the following sections.

OSI Layer 4 (Transport Layer) Protocol~

All NS3000/V communication makes use of one or both of two protocols for the Transport Layer; i.e., the
network layer that is responsible for ensuring that a message arrives at the correct remote computer.
All NS3000/V communication uses TCP (Transmission Control Protocol), TCP is a reliable, end-to-end,
connection-oriented protocol. This means that the protocol recovers from transmission errors and delivers
packets of data to their final destination in the correct sequence: It also means that when data is being
sent from one node to another, the TCP modules residing on the source and destination nodes maintain
status information about the transmission of that data. The combination of information maintained at
each endpoint is called a connection. TCP is also flow-controlled, which means that it regulates the now
of data, breaking messages into fragments if necessary, and reassembling them correctly at their
destination,
TCP, which is the Defense Advanced Research Projects Agency (DARPA) standard for a Transport Layer
protocol, is used by NS3000/V services and can be accessed directly by programs that use NetlPC
intrinsics. The use of these intrinsics is described in the NetIPCJOOO/V Programmer'$ Reference ManlUlJ.
The other Transport Layer protocol used by NS3000/V is called PXP, for Packet Exchange Protoeol
PXP is a request/reply datagram protocol used indirectly by programs using the socket registry mechanism
of NetiPC ( I PC LOOKUP intrinsic), PXP is an HP proprietary protocol that cannot be directly accessed by
user programs.

081 Layer 3 (Network Layer) Protocols
The Network Layer of the OSI model is divided into two sublayerc 3i, which routes messages between
networks (internetwork), and 31, which provides routing within a network. The routing provided by. level
3s is often called intranetwork or subnet routing.
Internet Protoeol (lp). The NS3000/V protocol used for layer 31 (the internetwork layer) and for layer 3s
(the intranetwork layer) in router networks is called the Internet Protocol (IP). Just as TCP is the DARPA
(Defense Advanced Research Projects Agency) standard for a Transport Layer protocol,lP is the DARPA
standard for an internetwork protocol.
The purpose of the IP protocol is to route data from source nodes to destination nodes throu.hout the
catenet. IP determines the route that a packet of data should take through the catenet based on

1-11

Introduction
addresses. Each node in the catenet is assigned a unique address. Each data packet also includes a
destination address, which is compared with the addresses of the nodes the data passes through. When the
addresses match, it means that the data has reached its destination. NS3000/V uses IP for internet
routing (routing between networks in the catenet) and for intranet routing in router networks.
Section 3 of this manual discusses IP routing and addressing in more detail.
Although NS3000/V uses IP to provide routing information for nodes within the same router network.
additional protocols must be used to provide intranet routing for other network types. For example, IEEE
802. 3 networks use the protocols defined in the IEEE 802. 3 standard for which these networks are
named. These protocols are described below.
IEEE 802..3 Local Area Network Protocols. The ThickLAN, ThinLAN/3000, and StarLAN/3000 links
all use protocols defined in the IEEE 802.3 standard for layer 38, as well as for layen I and 2. (The IEEE
802.3 standard encompasses standards for layers I, 2, and 3 of the OSI model.)

OSI Layer 2 (Data Unk Layer) Protocols
The protocols used for the data link layer, which is responsible for getting data from one side of a phYsical
link. to another without error, vary according to the type of NS3000/V link product that is providing the
connection. The three layer 2 (link-level) protocols used for NS3000/V links are called LAP-B, BSC, and
ASNP.
LAP-Il NS Point-to-Point 3000/V links use a protocol called LAP-a, for Link Access Procedure.
Balanced. LAP-B is a bit-oriented, full-duplex protocol.
Direct-connect (hardwired) and leased line NS Point-to-Point 3000/V Links use the LAP-B protocol.
BSC. The BSC protocol (someiilnes also called Bisync) is a character-oriented, half-duplex protocol. It
can be used by NS Point-to-Point 3000/V Links that are using dial links. Dial links use public, switched
telephone lines to carry data.
ASNP. Finally, Asynchronous SERIAL Network Links use a data link layer protocol called the
Asynchronous Serial Network Protocol, or ASNP. ASNP ensures error detection and data integrity by
using a 16-bit cyclic redundancy checksum polynomial.
OS(

Layer 1 (Physical Layer) Protocols

As with data link layer protocols, protocols for the OSI physical layer vary, and depend on the type of

NS3000/V link in use. Figure 1-7 shows the Hewlet-Packard hardware interface cards that implement
physical layer protocols: the Advanced Terminal Processor (ATP) for the Asynchronous SERIAL Network
Link, the Intelligent Network Processor (INP) for the NS Point-to-Point 3000/V Links, and the Local
Area Network Interface Controller (LANIC) for ThinLAN/3000, the ThickLAN option, and
StarLAN/3000 links.
The layer 1 protocols supported by each interface card are standards for physical connectoR. Table 1- 3
lists the standards supported by each interface card that can be used for NS3000/V links:

1-12

Introduction
Table 1-3. Interface Cards and Connection Standards
Card
INP

Connection Standards
EIA RS-232 ··r
EIA RS-422

CCITT V. 24/V. 28
CCITT V.3S
LANIC
ATP

IEEE 802.3
EIA R5-232-C
EIA RS-422

Auxlllary Protocols
Two additional protocols are used by NS3000/V link products. These are the Probe protocol and the DIal
10 protocol.

Probe Protocol. The Probe protocol is a proprietary Hewlett-Packard protocol used by IEEE 802. 3 links.
It is a connectionless protocol that provides name-to-address resolution and information about which

networking protocols are used on a given remote node. The Probe protocol broadcasts a request to all the
nodes on the network, and the correct node responds. Depending on the request the response provides
either the IP address that corresponds to a given node name, or the IEEE 802.3 address that COrresPOnds to
a particular IP address.
Dial 10 Protocol. Both the NS Point-to-Point 3000/V Link and the Asynchronous SERIAL Network
Link can be used over direct -connect (hardwired) or telephone lines. When used over telephone lines (dial
links), a Hewlett-Packard protocol called the Dial 10 protocol provides security checking and IP address
exchange.

1-13

Introduction

NETWORK LINKS
As noted previously, NS3000/V operates over the following network links:
• ThinLAN/3000 Link, including the thicker cable ThickLAN option
• StarLAN/3000 Link
• NS Point-to-Point 3000/V Link
• Asynchronous SERIAL Network Link
Each link. product consists of both hardware and software components. Later sections of this chapter
deseribe the software and hardware that is specific to each link product. However, some of the software
comprising each link is common to all link products. This software is described below.

Common Link Software
The following software is common to all NS3000/V link products:
• Network Interprocess Communication (NetlPC) is a peer-to-peer communications interface.
NetiPC allows programs, running concurrently, to exchange information and synchronize actions.
• The Network Transport provides the functionality of the network and transport layers (OSI
Layers 3 and 4), respectively. The Network Transport moves the data from a user's application
out to the communications link and receives data from the communications link, routing it to the
appropriate user. It implements the specifications of the Transmission Control Protocol (TCP) and
Internet Protocol UP).
• Node Management Services provides configuration file version checking and logging. Logging
enables network transactions to be "logged," or recorded, in a disc file. Such a record can be used
to assist in network troubleshooting.
• Node Management Configurator. The Node Management Configurator subsystem provides
NMMGIl, the Node Management Configurator program that allows you to configure each node
on the network..
• The Link Support Services subsystem contains software that opens, closes, and otherwise controls
physical links.
• Communication Services (CS/3000). CS/3000 provides some of the diagnostic and link
management software required for NS3000/V links. CS/3000 is also used by DS-ComPatible
links.

1-14

Introduction

IEEE 802.3 Links
NOTE

The information contained in this subsection is d, .ided Into three
headings--ThickLAN. ThinLAN/3000 Link. an." "itarLAN/3000 Link.
Because these link products are all based on the IEEE 802.3 local area
networking standard. they are similar in many respects. As a result, the
information stated for ThickLAN applies to ThlnLAN/3000 and
StarLAN/3000 except where differences are noted.
Note. however. that this section discusses the use 01 ThinLAN/3000 and
StarLAN/3000 to connect multiple HP 30008; it doe, 1I0t describe the use
of UP ThinLAN for PCs or HP StarLAN for PCs. Both of these products
can be used to connect personal computers in a networK Refer t,.. ~he HP
ThinLAN and HP StarLAN publications listed tn the Preface for complete
information about HP ThinLAN for PCs and HP StarLAN for PCs.

ThtckLAN. The ThickLAN option of ThinLAN/3000 Includes all the components to connect an
HP 3000 to a coaxial cable based on the Institute of Electrical and Electronics Engineers (IEEE) 802. 3
standard. This standard specifies a 10 million bits per second baseband local area network (LAN) with a
bus topology. The LAN uses a shielded 0.4 inch diameter coaxial cable as the data transmission medium
and the carrier Sense. Multiple Access with Collision Detect (CSMA/rl») medium access method.

Figure 1-8 shows the hardware components (described below) that the ThickLAN provides to connect an
UP 3000 to an IEEE 802.3 coaxial cable.
ThinLAN/3000 Link. Same as ThickLAN except that ThinLAN/3000 Link uses a O. 18-inch diameter
coaxial cable. Figure 1-9 shows the hardware components that ThinLAN/3000 provides to connect an
HP 3000 to an IEEE 802. 3 coaxial cable.
StarLAN/3000 Link.
The StarLAN/3000 Link allows personal computers and MICRO 3000s,
MICRO 3000XEs. and Series 37s to operate as an IEEE 801 3 local area network with connections among
systems made via twisted-pair telephone wires. Figure 1-9 'Jh~ws a St.arLAN network that 18 attached to
a ThinLAN/3000 link. Hewlett-Packard has published a manual set );)ecifically addressing the StarLAN
networks. Refer to the appropriate manuals as listed in the Preface for more information. The
configuration of an HP 3000 as a node in a StarLAN network is described in Sections 7 through 14 of this
manual.

1-15

Introduction

HP 3000

L
A

I
C

AUI
cable

MAU/TAP

MAU/TAP
MAU/TAP
~

HP 3000
AUI
L

cable

A
N
I
C

Figure 1-8. ThickLAN Hardware Components

1-16

Thick
COAXIAL CABLE

Introduction

ThinLAN/3000

HP 3000

lany
suppOrting
NS)

(any
supporting
. NS)

AUI integrated
with ThinMAU

Thin coaxial
cable

ThinMAU

StarLAN/3000
........_ _- - - - 1 1

StarLAN
10 mbit-to-1 mbit
Bridge

StarLAN
Header
Hub

_______l l ' Un.shi~l~
~

twisted

p8lrWlnng

StarLAN
Intermediate
Hub

HP 3000
(Series 37,37XE,

Micro 3000 or
Micro 3000 X8

HP 3000
(Series 37,37XE.
Micro 3000 or
Micro 3000 X8

Flpre 1-9. n'.LAN/3000 and StarLAN/3000 Hardware Components

1-17

Introduction

Medium Access Method for IEEE 802.3 Links
The IEEE 802. 3 standard specifies the Carrier Sense» Multiple Access with Collision Detect (CSMA/CD)
medium access method. This method provides an ideal means of transmitting bursts of data at high speeds
between nodes on a LAN. With CSMA/CD, all nodes have equal access to the network (Multiple Access~
there is no central control node. Before transmitting data» a node monitors the network to verify that no
other node is transmitting data (Carrier Sense). If a signal is sensed» the node desiring access defers its
transmission. Although the carrier sense makes collisions unlikely, they can occur when two nodes sense
that no other carriers are on the network and begin transmitting simultaneously. To deal with this
possibility, nodes listen for collisions while transmitting (Collision Detect). If one is detected» the node will
initiate a jam signal to warn the entire network. All nodes must then cease their transmission. Each
delays for a random period of time and then restarts its transmission. This means that each node
eventually gets to transmit its data.
Although nodes in an Ethernet network also use CSMA/CD, a node based on IEEE 802.2/802.3 cannot
communicate with an Ethernet node. Nonetheless, both nodes may coexist on the same network cable.
This is because there is an incompatibility in the frame format at the data link level (OSI Layer 2) that
interferes with communications but not with transmissions. The frame format specified by IEEE
802.2/802. 3 provides for higher network reliability.

Hardware Components
ThickLAN. There are three major hardware components of ThickLAN. These are:

• Local Area Network Interface Controller (LANIe). The LANIC is a microprocessor-based
communication controller that plugs into the HP 3000 backplane. It handles link-level
buffering, error checking, the IEEE 802.2 and 802.3 protocols and includes a built-in self-test.
When addressed by another node on the network» the LANIC receives the frames of information
and checks them for accuracy before passing them to the HP 3000. When transmitting, an
addressed frame is passed to the LANIC where error checking information is added. The LANIC
then tests to see if the cable is busy and if not, transmits the frame.
• Medium Attachment Unit (MAU). The MAU provides the physical and electrical connection to
the coaxial cable; it is powered by the LANIC through the AUI (Attachment Unit Interface)
cable. The MAU receives signals from and sends signals to the coaxial cable. It also detects
collisions resulting from two nodes starting to transmit simultaneously. A MAU is attached to
the coaxial cable with a cable tap and can remain permanently attached to the cable. A MAU
can be attached on an active network without interrupting network traffic.
• Attachment Unit Interface (AUI) Cable. The AUI cable and two-meter internal LANIC cable
attach the LANIC to the MAU. It can be up to 48 meters in length. It is available with either
FEP coating for installation in passages restricted for breathable air or with PVC coating for
installation in less restricted spaces.
ThinLAN/3000 Link. There are two major hardware components of ThinLAN/3000 Link, as follows:

• Local Area Network Interface Controller (LANIC)--same as for ThickLAN.

1-18

Introduction
• Thin Medium Attachment Unit (ThinMAU). The ThinMAU provides the connection from the
LAN hardware to the thin coaxial cable. The ThinMAU connects to the LANIC with an AUf
cable. The AUI cable is one meter in length and is integrated with the ThinMAU. Additional or
alternate cables are not supported. The AUI cable attaches to a two-meter internal LANIC
cable.

StarLAN/3000 Link. StarLAN/3000 Link includes the following hardware:
• Local Area Network Interface Controller (LANIC). An interface card similar to that provided
with ThickLAN and ThinLAN/3000 Link except it provides connection to an HP StarLAN
twisted-pair cable, and it applies to UP 3000 Series 37, 37XE, MICRO 3000, and MICRO
3000XE systems only. The LANIC comes with all StarLAN/3000 Links.
Other StarLAN-related hardware which must be ordered separately to correspond to the needs of the
network design includes:
• Cabling. StarLAN cabling consists of unshielded twisted-pair wiring that conforms to the IEEE
802.3 Type IBASE5 standard (draft).
• StarLAN Bridge. A bridge is a device that allows connection between different types of LANa,
but is transparent to the nodes that communicate across it. For example, a Bridge permits the
connection of a coaxial cable LAN to a StarLAN, allowing Series 4x/5x/6x/70 HP 30008 to
communicate with StarLAN nodes. In this case, the Bridge connects to the coaxial cable LAN
through a MAU/ThinMAU and AUI cables, as appropriate, and to the StarLAN via a StarLAN
cable to a StarLAN Hub. In addition, it compensates for differences in transmission speeds
between the LANs, for example, the 10 Mbit/second coaxial cable LAN and the 1 Mbit/second
StarLAN.
• StarLAN Hub. A Hub is a central device on a StarLAN. Using StarLAN cables, a single Hub can
be connected with up to 11 nodes (personal computers or the supported 8P30008) or other Hubs.
With multiple Hubs connected, up to 50 nodes on a StarLAN can be supported.
Figure 1-9 illustrates an HP StarLAN attached via a Bridge to a ThinLAN.

Unk Level Software
TbtetLAN. The link level software implements the specifications of IEEE 802.2 and 802.3, the protocols
used for OSllayers 1 and 2, the physical and data link layers, respectively.
ThtnLAN/3000.
applications.

Same as for ThickLAN, plus software that provides PC acuss to most UP 3000

StarLAN/3000.
applications.

Same as for ThickLAN, plus software that provides PC access to most HP 3000

1-19

Introduction

NS Polnt-to-Polnt 3000/V Link
The Point-to-Point 3000/V Link is, as its name implies, a polnt-to-point link. Point-to-point links
transfer data by sending it from one node in a network to another until it reaches its destination.

Three types of Point-to-Point 3000/V Links are available; they are distinguished by the kind of physical
connections that exist between nodes on the network:
• Direct connect links, which use direct connect cable to connect nodes in the network. Such
connections are often referred to as IIhardwiredll connections.
• Dial links. in which a modem attached to a node is used to transmit and receive data carried
across telephone wires. Dial links are also referred to as switched lines.
• Leased lines, in which data is sent over data-grade lines leased from a private carrier.
Figure 1-10 shows a router network consisting of some NS Point-to-Point 3000/V Links, as well as
Asynchronous SERIAL Network Links.
NS Point-to-Point 3000/V links use an UP 3000 Intelligent Network Processor (INP) to perform
link-level communications protocol management. The INP is a hardware card that fits Into the
backplane of the UP 3000. Software that implements a particular link-level protocol ii downloaded from
the HP 3000 when the system is being installed as part of the network. Each HP 3000 with a
Point-to-Point 3000/V link must have an INP installed.
The direct connect, dial, and leased Point-to-Point 3000/V links differ in the link-level protocols
available and in the hardware additional to the INP that is used to interconnect systems. The following
sections describe these differing features.

1-20

Introduction

HP 3000

Polnt-to-Polnt 3OfX)N Unk
UP-iJ. chct connd

Point-to-Point
3fYXN'J Unk
~cIIIO

HP 3000

Asynchronous SERIAl
Network Unk

HP 3000

.......

.......,--.1

......

Asynchronous SERIAL
Network Unk
"'D

Figure 1-10. Router network with NS Point-to-Point and SERIAL Links.

DIrect Connect Unks
Link Level Protoeol. The direct connec;t NS Point-to-Point 3000/V Link uses the LAP-B link-level
protocoL LAP-B is a bit-oriented. full duplex. peer-to-peer protocoL
Hardware and Cables. As noted previously. each HP 3000 with an NS Point-to-Point 3000/V link,
inc;ludiDI those using direct connect links, requires its own INP. Direct connect cable terminated by ElA .
RS-422 connectors connec;ts the systems in the network. These cables must be ordered separately from
the NS Point-to-Point 3000/V Link.

1-21

Introduction

Dial Unks
Dial links can be implemented using either direct dial modems, for which the telephone number of a
connected node is manually dialed by the user, or autodial modems, in which the telephone number of a
connected node is configured into NS3000/V network management configuration software. Whether
direct dial or autodial connections are used depends upon the features of the modem connected to a
particular node.
Link Level Protocols. Both the LAP-B and BSe protocols can be used as link-level protocols to support
NS Point-to-Point 3000/V dial links.
LAP-B is a full-duplex protocol. Because data can be transmitted in two directions at once using a
full-duplex protoco~ and in only one direction at a time using a half-duplex protocol, better throughput
is achieved using the LAP-B protocol Full-duplex modems are required when using LAP-B.
BSC is a half-duplex protocol; it therefore can operate over half-duplex modems. However, better
throughput (although poorer than with LAP-B) can be achieved by using Bse over full-duplex modems.
See Appendix B, ''Supported Modems," for a list of the modems supported for each link-level protocol.

Leased Unes
The company that owns a leased line allocates use of the line specifically for a subscriber's data
communication needs. A cable from the INP to a modem that is attached directly to the leased line
connects the HP 3000 to the leased line.
Link Level Protocol. HP only supports the use of the LAP-B protocol over leased lines for NS
Point-to-Point 3000/V Links. Due to greater throughput efficiency, LAP-B is the preferred link level
protocol for leased lines.
LAP-B requires the use of full-duplex modems. See Appendix B, "Supported Modems," for a list of the
modems supported for LAP-B.

Hardware and Cables for Dial Unks and Leased Lines
As previously noted, each UP 3000 with· an NS Pointe-to-Point 3000/V link, including those using
switched (dial links) or leased lines, requires its own INP (HP part number 30020B for Series 39-70, part
number 30244M for MICRO 3000, MICRO 3000XE, Series 37, and Series 37XE). In addition, each UP
3000 connected via a modem link requires a modem and cable connecting the modem to the INP. These
cables are direct connect and are terminated by connectors adhering to the EIA RS-232-C standard.
Direct dial modem links require a telephone; autodial and leased line modem links require only a modem.
Refer to Appendix B of this manual for a list of supported modems.

Asynchronous SERIAL Network Link
The Asynchronous SERIAL Network Link for the HP 3000 provides asynchronous data transfer between
UP 30005 and between personal computers and HP 30008.

1-22

Introduction
The Asychronous SERIAL Network Link uses the Advanced Terminal Processor (ATP) hardware
subsystem to make connections. The ATP is a terminal/printer controller used on MICRO 3000, MICRO
3000XE. Series 31, 31XE. 39, 4x, Sx, 6x, and 7(, I,t' 30008. It is the only controller available for MICRO
3000, MICRO 3000XE, Series 31, 37XE, 64, 68, and 70 systems. Note that the ADCC, which is another
terminal/printer controller available on Series 39, 4x, and Sx HP 3000s, does not support the
Asynchronous SERIAL Network Link. One port on the A.TP 18 needed for each system-to-system or
system-to-PC connection.
Like the NS Point-to Point 3000/V Link, the Asynchronous SERIAL Network Link uses the store and
forward technique to transfer data among nodes in a network. The Asychronous SERIAL Network Link iI
therefore also considered a "point-to-pointU link even though it is not part of the NS Point-to-Point
3000/V Link product. An NS3000/V router network can consist of a combination of NS Point-to-Point
3000/V links and Asychronous SERIAL Network links.
The Asychronous SERIAL Network Link can be of three types:
• Dial link (switched line)

• Leased line (non-switched)
• Direct connect (from PCB to UP 30008 onlv)
Dial links can use either direct dial modems, for which the user dials a telephone number to initiate a
connection to a remote node, or autodial modems, for which the remote node's telephone number is
configured into network management software,;o that dialing is not necessary.
Leased lines, for which a data-grade line is allocated specifically for a subscriber's needs, can be attached
to the HP 3000 by a modem. The router network shown in Figure 1-10 contains two Asynchronous
SERIAL Network Links: one is a dial link, and the other is a leased line.
Direct connect links can be used to connect PCs to UP 3000s; however, HP only recommends using
ThinLAN/3000 or StarLAN/3000 Links for local-area PC-to-UP 3000 communication.

Hardware and Cabling
To operate, the Asychronous SER.IAL Network Link requires the installation of an ATP. Because the
ATP supports a number of asynchronous point-to-point data communication functions such as hardwired
and dial connections between HP 30008 and terminals, your system may have had an ATP before you
purchased an Asychronous SER.IAL Network Link.
The ATP consists of cards that fit into the backplane of the UP 3000. The minimum ATP Bubsyltem
consists of one System Interface Board (SIB) and one Port Controller. Each Port Controller (Direct
Connect or Modem) can provide connection to the HP 3000 for up to 12 personal computen or additional
HP 30008. Each UP 3000 can support more than one Port Controller to increase the number of nodes
supported by the system up to a maximum of 40.
The maximum number of PC workstations supported for each UP 3000 acting as a SERIAL network
server/host is as follows:
MICRO 3000, MICR.O 3000XE, Series 37 and 37XE

1-23

Introduction
Series 39, 42, 44, 48, 52, 58

Series 64, 68, 70

See your HP representative to discuss the recommended number of SERIAL connections to PCs given your

network and application load.
Dial Link and Leased Line Modems and Cabling. Any node (which can be either a personal computer or
an HP 3000) connected to the network using an Asynchronous SERIAL Network Link requires a modem
and connecting cable. The cable connects the system's Port Controller to the modem using UP DirectConnect 232 connectors at both ends.
Refer to Appendix B of this manual for a list of
supported modems.
PC-to-HP 3000 Links. The following personal computers can operate as nodes on an Asynchronous
SERIAL Network: HP 150s, HP Vectra personal computers, and IBM personal computers. Refer to the
HP SERIAL Network PC-to-HP 3000 Network Configuration Guide for a summary of the steps required
to attach a PC to an HP 3000 with the Asynchronous SERIAL Network Link. Refer to Sections 6
through 14 of this manual, however, for information about configuring an Asynchronous SERIAL
Network Link for an UP 3000.

Unk Level Protocol
The Asynchronous SERIAL Network Link uses the ASNP protocol as a link-level protocol. (Refer to
"Protocols" earlier in this chapter for a description of ASNP.)

Optional DS-Compatlble Links
Hewlett-Packard's AdvanceNet Architecture includes UP data communications products based on the
principles of the OSI model, as well as extensions for the AdvanceNet predecessor, DSN. Each HP data
communications product uses one or more of the different network architectures encomPassed in the HP
AdvanceNet Architecture. Communication is possible only between data communications products using
the same architecture. As a result, it is important to know which architecture is used by which data
communications product.
NS3000/V Network Services includes DS Services software as a subset. This enables applications that
have b~en written for operation over DS links to operate over NS links with little or no modification.
However, only NS links support the full capabilities of each network service. (Refer to the NS3000/Y
User/Programmer Reference Manual for information on the differences between using various services
over NS or DS links.)
DS-Compatible Links can be used to connect a node on a network connected by an NS link to an HP
system using D5. The systems and links that can connect them are as follows:
• UP 3000 or HP 1000 with the Point-to-Point Hardwired Link (HP 30270A),
• UP 3000, HP 1000, or UP 9845 with the OS Point-to-Point Modem Link (HP 30271A),
• UP 3000 or UP 1000 with the DS X. 25 Network Link (HP 32187A),
• HP 3000 with the DS Satellite Network Link (HP 32188A).

1-24

Introduction
Because these links use the DSN architecture and also work with DS/3000, they will be referred to as
OS-Compatible Links in this manual.
Each DS-Compatible Link provides all the components needed for one side of a connection:
management software, the Intelligent Network Processor (INP) hardware interface card and cables.

link

A node can have both DS and NS links configured; this allows nodes connected to the node by DS links to
communicate with other nodes connected to the same node by NS links.

However, nodes that are using an INP for NS3000/V communication cannot use the same INP for DS
communication concurrently. If the node has multiple INPs, it can have DS and NS links operating
concurrently; each INP must be used for a different NS or DS link. Figure 1-11 shows a network
consisting of both DS and NS links. Node B is shown as supporting both NS and DS because it has two
1NPs; one INP is configured to support the DS link with node A, and the other INP is configured to
supPOrt the NS link with node C.

Node A

NodeS

DSUnk

NS Unk

NodeC

Node 0

Figure 1-11. Network with NS and OS Links.
Refer to the publications listed in the Preface of this manual for more information on DS-COmpatible
links.

PERSONAL COMPUTERS AS NS3000/V NODES
When used as nodes in NS3000/V networks personal computers (Pes) provide a subset of the network
communication functions provided by HP 30008.
Unlike HP 3000s, Pes cannot provide transparent internet or intranet point-to-point communication.
Instead, a PC must establish communication with the HP 3000 to which it is adjacent (this means a link
extends from a particular HP 3000 directly to the PC). In addition, Pes do not accept inbound
communication; that is, communication with other nodes must always be initiated from the PC.

1-25

Introduction
As a result, PC users must log on to the adjacent UP 3000 from the PC (using the: DSLINE command); HP
3000 users cannot log on to the PC from an UP 3000 terminal. Once the PC user has logged on to the HP
3000, he or she can access other nodes in the network by using Network Services commands initiated at
the HP 3000.
Note that Pes must therefore be leaf nodes in the network; they cannot be used as intermediate nodes on
a point-to-point router network or as gateways between networks.

NS3000/V NETWORK SERVICES
NS3000/V Network Services extend the capabilities of the UP 3000 operating system (MPE) and permit
usen to share information, programs, processing capabilities, storage facilities, and other resources provided
by the various nodes of the distributed network.
The logical environment in which a user or an application process gives instructions to the computer is
called a session. In Hewlett-Packard networks, sessions which are established on remote nodes for the
purpose of carrying out data communications tasks are called environments. The remote environments
mayor may not be interactive, depending on the task involved. To accomplish a desired task, usen or
processes issue instructions similar to those they would use on their own system. In fact, all MPE-V
commands and most MPE-V intrinsics can be executed on a remote node once the remote environment is
established. In addition, a variety of NS3000/V services include commands or intrinsics to be used for
specific tasks on remote nodes. This variety allows the user or programmer to choose the right tool for
the task.

ServIces Available
The following services are provided by NS3000/V over 3000/V links:
• Remote Process Management (RPM). Allows a process to programmatically initiate and
terminate other processes throughout a network from any node on the network. RPM is
normally used in conjunction with NetlPC.
• Virtual Terminal (VT and VTR). Gives the user interactive capabilities on the remote node,
even though the user's terminal is physically connected to the local node. Reverse VT (VTR)
refen to programmatic access of remote terminals.
• Remote File Access (RFA). Allows a user to access files and devices on remote nodes.
• Remote Data Base Access (RDBA). Allows a user to access data bases on remote nodes. The same
security protection used for data bases on the local node applies to remote access.
• Network File Transfer (NFT). A facility that efficiently transfers disc files between nodes on the
network.
Nfl is supported for UP 3000-to-HP 1000, HP 3000-to-HP 9000 (Series 300
and SOO) and HP 3000-to- DEC VAX· computers.
.• Pl'ogram-to-Program Communication (PTOP). Permits programs residing on different nodes to
exchange information with one another in a master/slave relationship.
*DEC and VAX are U. S. registered trademarks of Digital Equipment Corporation.

1-16

Introduction
These services enable users and programmers to perform essential functions in a network- and
catenet-wide context. When used over OS-Compatible links. NS3000/V services observe the features and
syntax used for the DSN architecture, whether the communication is between NS3000/V and NS3000/V
or between NS3000/V and other products using the OSN architecture, such as DS/3000 and DS/I000.
However, communication through intermediate nodes is not transparent to the user, as it is when
NS3000/V links are used. For details on using these services, refer to the NS3000/V User/Programmer
Reference Manual.

1-27

~
............

_N_E_T_W_O_R_K_M_A_N_A_G_E_M_EN_T

The advantages of a distributed network are accompanied by the responsibilities of network management,
the management of systems in a distributed network. These responsibilities are assigned to the user
identified as the network manager. just as the system management of the UP 3000 is primarily the
responsibility of those users identified as the system manager and the system supervisor/operator. The
network manager's role can be further subdivided by delegating certain tasks to additional usen:
• Usen called node managers can be assigned to perform network management tasks required for
each node on the network.
• If the network is part of a catenet, tasks related to coordinating individual network operation
with the operation of the catenet can be assigned to a catenet administrator.

• If a personal computer network uses an HP 3000 as a server, the management of the PC network
will be assigned to a PC network manager.
These collective network management responsibilities can be distributed among several individuals, as
described above, with coordination among them provided by the network manager. Or, the node manager
for a particular node can also manage the entire network. An alternative to any such division of
responsibility is where the single network manager can perform all functions: that of node manager for
all the nodes on the network, that of network manager. and that of catenet administrator. The PC
network manager should coordinate the operation of the PC network with the network manager.
Remember that system management of a single HP 3000 is assigned to a user identified as the system
manager and the system supervisor/operator. As a result, it may be appropriate to assign one of these
usen the role of node manager for an individual system.
All of these system management and network management role assignments are based on the MPE
capabilities they require to perform their functions:
• system manager (8M) capability for system manager
• Operator (OP) capability for system supervisor/operator
• node manager (NM) capability for node manager
• network administrator (NA) capability for network manager

NOTE

Although this manual refers to the person responsible for managing the
network as the network manager, this title and other titles defined in this
section are only used for convenience.
The person responsible for
maintaining the operation of the network, the PC network, or the catenet
needs no particular title, as long as it is clearly defined who is responsible
for various parts of the network's operation.

2-1

Network Management

Node manager (NM) and network administrator (NA) capabilities currently provide almost identical access
rights. The single difference is that NA capability is required to access and update the network directory.
part of the NMMGR utility. The node manager should therefore be assigned NM capability; the network
manager should be assigned NA capability. (You might want to call your network manager a "network
administrator," to correspond to the NA capability provided by MPE.) By logging on as a user that is
assigned the MPE capability of NM or NA, the network manager can execute the utilities and commands
needed for the operation of NS3000/V services and link products. In this manual, it is assumed that one
person, the network manager, will be completing the tasks required to establish a working NS3000/V
network.

)

As previously noted, these responsibilities may be distributed among several individuals or may be assigned
to one person at your installation.

Later portions of this chapter describe the tasks required of the network manager, covering the following
topics:
• The Network Management Lifecycle
• Network Management Tools
• Configuration and Initialization Overview
In addition to explaining each major functional area and the corresponding commands or utilities that
make up the network manager's job, this section explains background information as needed. Other
complex subjects can only be introduced here. In such cases, you will be referred to appropriate additional
sources.

NETWORK MANAGEMENT TASKS
As the network manager, you are directly responsible for executing the utilities and commands needed for
the operation of NS3000/V services and link products for all the nodes directly connected to your
network. In addition, your network may be linked (via gateway nodes) to other networks in the same
catenet. DS-Compatible Links may also link your network to DS networks.

The catenet administrator is responsible for the coordination of tasks among all networks that ensure the
complete operation of the entire catenet.
As the network manager, you are also responsible for coordination with any network, possibly through the
catenet administrator, with which your local network can communicate.

Although the network manager does not have full responsibility for the other networks with which the
local network can communicate, he or she needs to be aware of the requirements of establishing
connections. such as the naming or addressing conventions used by each type of network.

2-2

)

Network Management

The Network and Catenet Management Llfecycle
To understand the responsibilities of network and catenet management, it is helpful to examine the major
stages of development in a typical network or catenet, generalized into the network/eatenet life cycle
shown in Figure 2-I.

Design

Operation

Implementation
~

-t

---t

Tuning
Ie Growth

10-

f
Figure 2,-1. The Network/Catenet Life Cycle
Both networks and catenets evolve in much the same way as is illustrated in Figure 2-1. Fint is the
design stage, a time of defining requirements and designing a network to meet those requirements. This
stage is followed by the implementation stage. During the implementation stage, each network manager is
responsible for managing the installation, configuration, and initialization of all the nodes in the network.
The catenet administrator is responsible for managing the overall installation, configuration. and
initialization of all networks in the catenet. This includes informing all network managers of
configuration information that must be coordinated to achieve internetwork communication. Once the
network or catenet is established, management consists of two main tasks:
• Ensuring network availability. Each network manager is responsible for changing configurations,
controlling the operation of the data communications products on each node, and resolving any
problems.
• Maintaining performance levels.
The network manager monitors performance to ensure
consistent response time. The catenet administrator can monitor performance internetwork
traffic.
Eventually, in response to the requirements of these tasks, the network manager determines the need for
growth or tuning of a particular network, returns to the design stage, and the cycle begins again.
Similarly, the catenet administrator must determine the need for growth, tuning, or other alteration of the
catenet, and must as a result return to the design stage and begin the cycle again.
Thus, network and catenet management requirements change over time, depending on where your
network or catenet is in the network life cycle.

Network Management Tools
The responsibilities of managing a node in a network and coordinating with remote nodes and networks
may require the network manager to use a combination of software utilities, data communications test
equipment, and network support services. The network manager has a variety of tools and utilities
available to supervise the operation of NS3000/V services and link products. Some are provided with the
data communications products and some are provided with the HP 3000.

1-3

Network Management

MPE Commands and Utilities
The responsibilities of the network manager, node manager and the system superviser/operator tend to
overlap because of the similarities of their roles. NA, NM, and OP capabilities allow users to issue MPE
commands and interact with the system to fulfill designated responsibilities.
A variety of utilities and commands used by the system supervisor/operator are also available to the
network manager (and/or node manager, network administrator, or catenet administrator) for use in
managing NS3000/V networks. These include:
• SYSDUMP--the system I/O configuration utility used to add devices and change system tables.
The SYSDUMP responses necessary for NS3000/V services and link products are documented in
Section 4 of this manual.
• MPE Networking Commands. There are MPE commands specifically designed for starting and
stopping NS3000/V link products, and for specifying the operation of certain components. Table
2-1 lists these networking commands. They are described in Volume II, Section 1 of this manuaL
Additional MPE commands, such as SHOWDEV and ALLOW, may also be helpful in managing
NS3000/V services and link products. Refer to the MPB Y Commands Reference Manual for
information about commands not explained in Volume II of this manual
• Software Dump Facility (SDF), DPAN 5 and NSDPAN. The SDF utility provides a memory dump
of the HP 3000. It is used following a system failure, halt, or other abnormal condition. DPANS
is the system utility used to format a memory dump. NSDPAN is an enhanced version of
DPANS. NSDPAN formats the data structures important for analyzing memory dumps from
NS3000/V link products and services. If the problem is related to NS3000/V services or link
products, a memory dump needs to be submitted with the Service Request. The memory dump
should be formatted with NSDPAN rather than DPAN5. The NS3000/V Error Message and
Recovery Manual describes these programs in more detail.
• LISTLOG S. This utility analyzes files in the MPE system log files. An MPE log file records
events such as session or job initiation and termination, process termination, file closure, I/O
errors, and system shutdown.
Refer to the MPB V System Operation and Resource Management Reference Manual (32033-90005) and
MPB V Commands Reference Manual (32033-90006) for more information.

2-4

Network Management

TABLE 2-1.

~SJOOO/~

NETWORKING COMMANDS

Command Name

Description

DSCONTROL

Initiates, terminates, and controls the operation of the OS
Compatible Links.

LINKCONTROL

Activates or deactives link level tracing on the specified
communications line. The line must already be initialized.

NETCONTROL

Initiates, terminates, and controls the operation of the Network
Transport subsystem of NS3000/V.

NSCONTROL

Initiates, terminates, and controls the operation of the Network
Services subsystem of NS3000/V.

RESUMENMLOG

Resumes NMS logging after a recoverable error.

SHOWCOM

Displays the status of a communications device.

SHOWNMLOG

Displays the identification number and available space for the
NMS log file.

SWITCHNMLOG

Closes the current NMS log file and creates and opens a new
one.

Node Management Services
Node Management Services (NMS), used by the network manager to configure, initialize. and maintain
NS3000/V services and link products are used in much the same way that MPH operating system utilities
are used by the system supervisor for similar tasks. For example, the SYSDUMP utility is used to
configure system hardware into MPE; the network equivalent is the Node Management Configurator,
abbreviated NMMGR, which is used for network configuration. The utilities and commands combined as
Node Management Services include:
• The Node Management Configurator (NMMGR). NMMGR is a menu driven configuration
utility that is used to create and enter information into a configuration file. The information in
a configuration file is used by the data communications product, when it 18 active, to determine its
operating characteristics.
• The NMS Conversion Utility (NMMGRVER). NMMGRVER converts a configuration file
created with earlier versions of NMMGR to the format required by NMMGR, version A. Ol. 00.
Refer to Appendix C for more i~formation.
• The NMS Trace/Lo. Formatter (NMDUMP~ The diagnostic functions of logging events and
tracing messages are handled by NMS using a common set of internal intrinsics. NMS provides
the NMDUMP formatting utility to format the fileR created by logging or tracing operations.
Refer to Volume II, Section 3 of this manual for more Information.

2-5

Network Management
• The NMS Maintenance Utility (NMMAINT). This utility provides a list of software module
version numbers and verifies that all modules are current and compatible. Refer to Volume II,
Section 2 of this manual for more information.
• The NODESTAT Utility. You can use a utility called NODESTAT to display information about
the network activities occurring on a node as a troubleshooting aid.

CS/3000 Utilities
There are also several utilities supplied with the Communications Systems (CS/3000) that supplement the
diagnostic capabilities provided by NMS. These utilities are:
• CSLIST and DSLlST. These utilities supplement the information provided by NMMAINT. They
provide a list of software module'version numbers for the DS-Compatible Links. These utilities
also verify that all modules are current and compatible. Refer to Volume II, Section 2 of this
manual for more information.
• The CS/3000 Trace Facility (CSTRACE). This utility is used to provide a record of the line
actions, states and events that occur during link operation. CS/3000 link tracing is enabled
during configuration with NMMGR or with the MPE command LINKCONTROl (refer to Volume
II, Section 1.)
• CSDUMP. The diagnostic function of tracing messages is handled by CS using a common set of
internal intrinsics. CS provides the CSDUMP formatting utility to format the files created by
CSTRACE link tracing operations. Refer to the LAN/3000 Diagnostic and Troubleshooting
Guide for LAN/3000 Link tracing; refer to the DS/3000 HP 3000 to HP 3000
Network Administrator Manual for DS-Compatible Link tracing.

1JDk Level Tools and Utilities
This manual coven those aspects of network management used by the network manager on a day-to-day
basis. There are also a variety of link-specific troubleshooting tools that are beyond the scope of this
manual. However, because it may be helpful to know what is available, the link-level tools are listed
here, with references to the appropriate manuals.
IEEE 802..3 Links. For IEEE 802. 3 links, the following tools are available:
• LANIC Dump Analysis (LANDPAN). This utility is used to generate a formatted dump of a
LANIC log file. These files are produced when an error occurs and contain the contents of the
LANIC memory.
• LANIe Self Test. This test exercises the major portion of the LANIC hardware and reports
status.
• LAN Node Diagnostic (LANDIAG). This utility is an interactive on-line program designed to
help identify any malfunctioning hardware units of the LAN3000/V Link.
• Time Domain Reflectometer (TDR). The TDR that HP recommends is the TEKTRONIX 1503
Cable Fault Locator.

2-6

)

Network Management
Refer to the LAN/3000 Diagnostic and Troubleshootin, (-h,j,.te for more information on these tools. For
information on troubleshooting DP StarLAN links connecting personal computers, refer to the HP
StarLAN Diagnostics and Troubleshooting Manual tor pes.

Links Using an INP. The NS Point-to-Point 3000/V Link and DS-Compatible links use the Intelligent
Network Processor (INP) card to perform lower-level data comoAunication functions. The fonowing
utilities are available for INP troubleshooting:
• INP Dump Analysis (INPDPAN). This utility is used to generate a formatted dump of an INP log
file. These files are produced when an error occurs and contain the contents of the INP memory.
• INP Diagnostic Support Monitor (DSM,. This utility is an interactive on-line program designed
to help identify any malfunctioning hardware units of the INP.
• DSDUMP. When formatted with DSDUMP, instead of CSDUMPt the link trace file created by
CSTRACE can provide additional information on the data link and network levels of the BSC
and X. 2S protocols.
Refer to the DS/3000 HP 3000 to HP 3000 Network Administrator Manual and the INP Dla,nonlc
Procedures Manual for more information.
Asynchronous SERIAL Network Link. The following tool is available specifically for troubleshooting
Asynchronous SERIAL Network Links:
TERMDSM. The TERMDSM utility is the diagnostic tool for the ATP card used by Asynchronous
SERIAL Network Links. Refer to the TERMDSM On-Line Diagnostic/Support Monitor Reference
Manual for instructions on using TERMDSM.

Installing NS3000/V Links
The'installation procedure for each NS3000/V link product specifies responsibilities of the customer and
ofDP.

Customer InstanatJon Tasks for All NS3000/V Unks
You must complete the tasks listed in Table 2-2 before your HP representative begins to install any
NS3000/V link product:

2-7

Network Management
TABLE z,-z,. Customer Installation Tasks
Required Steps

References

Install modems and phone lines for
remote NS3000/V links, if any.

Refer to the appropriate cabling, modern, or auto-dial
unit or reference guide.

Install extemal interconnect cable
between HP 3000 system for
hardwired NS Point-to-Point
3000/V connections, it any.

HP 30020B Intelligent Network Processor (INP)
Installation and Service Manual (30020-90005)
HP 30244M Intelligent Network Processor (INP)
Installation and Service Manual (30244-90002)

If installing any of the optional DS
Compatible Links, install the
communications line and test that the
line is functioning correctly.

Refer to the appropriate cabling, modem, auto-dial unit
reference manual or other guide for any components to
be installed.
For the DS X. 25 Link, refer to X. 25: The PSN
Connection (5958-3402) and X. 25 Link for the
H P 3000 Reference Manual (32187 - 9000 I).
For the DS Point-to-Point Links, refer to DS/3000
HP 3000 to HP 3000 Network Administrator Manual
(32185-90002).
If connecting to an HP 1000, refer to the DS/3000
HP 3000 to HP 1000 User/Programmer Reference
Manual (32185-90005).

Perform a system backup (including
MPE and @. PUB. SYS) and make the
system available for installation of
the data communications software,
interface card(s), and cable.

MPE JI System Operation and Resource Management
Reference Manual (32033-90005)
LANIC Installation and Service Manual (30242-90001)
Option 100 LANIC Installation and Service Manual

(30242-90100)
LANIC Installation and Service Manual (30240-90001)
Option 100 LANIC Installation and Service Manual

(30240-90100)
StarLAN/3000 Link Installation and Service Manual

(30265-90001)
HP 30244M Intelligent Network Processor (INP)
Installation and Service Manual (30244-90002)
HP 30020B INP Installation and Service Manual

(30020-90005)
In addition, if any NS3000/V links will be used to connect personal computers to an HP 3000, the
customer is responsible for installing the personal computers.
It is also the customer's responsibility to install some hardware and cables for IEEE 802.3 links, as
described below.

2-8

Network Management

Additional Tasks for IEEE 802.3 IJnks

Table 2-3 lists the steps you must complete before beginning to install the software for ThinLAN/3000
(or the ThickLAN, option) and StarLAN/3000 links:
TABLE %--3. IEEE 801.3 Link Customer Installation Tasks
Required Steps

References

TblckLAN: Install the coaxial cable.
MAU/tap, and AUI cables. Test that
the line is functioning correctly.

LAN/3000 Design Guide (5955-7689)
LA1tJ Cable and Accessories In81aUation MaINUII
(5955 -7680) or Local Area Network CGblbag GIld
Installation Guide (30242-90002)
LAN/3000 Diagnostic and Troubleshootln, Gukle

(30242-90003)
LAN Link Hardware Troubleshootin, Manual. IEEE
802.3 Coaxial Cable LAN (5955-7681)

ThinLAN/3000: Install the thin
coaxial cable and ThinMAU. Test
that the line is functioning correctly.

LAN/3000 Design Guide (5955-7689)
LAN Cable and Accessories InstaUation MfJIIlIal

(5955-7680)
LAN/3000 Diagnostic and Troubleshooting Gulde

(30242-90003)
LAN Link Hardware Troubleshooting Manual.IEBE
802.3 Coaxial Cable LAN (5955-76811

StarLAN/3000: Install the Hubs and
unshielded twisted-pair cable. Test
that the line is functioning correctly.
If necessary, install the HP StarLAN
Bridge.

HP 28647 A Bridge InstaUatwII and Reference MfJIIlIal

(28647-90001)

After the hardware described in Table 2-3 has been installed, you must perform a system backup, as
described in Table 2-2.

UP installation Tasks
During the installation of NS3000/V links. UP is responsible for:
• Taking the system down and performing a system update to add the product software modules to
the system if the system is on the current release. otherwise a full system update will be
performed.
• Creating the DADCONF. NET. SYS configuration file to allow the initiation of all purchased
network services. See the note on the following page for details.
• Verifying that the correct number and version of the software modules have been installed.

r"
2-9

Network Management
• Installing the link product hardware. with the exception of the IEEE 802. 3 link hardware
described in Table 2-3. modems and phone lines. and external interconnect cable between
hardwired HP 30008.
• Adding the link product hardware into the I/O software configuration and configuring it in
accordance with the customer·s intended use.
• Initially configuring the software in accordance with the network links used.
• Connecting the network link to the communication line (only if the line is available).
• Verifying that a link properly connects a personal computer to the HP 3000. HP can verify this
only if the personal computer has been previously been wired to the HP 3000 and if the personal
computer is available for testing.
• Verifying that the product properly opens the line when started by command.

Installing Network Services
For UB-MIT and later installations of NS3000/V services and link products, an additional configuration
file is required. This file is DADCONF. NET.SYS. Without this file. NS3000/V Network Services will
not operate.
DADCONF. NET. SYS is required to initiate the services purchased, such as VT (virtual terminal)-only for
ThinLAN/3000 Link. These services become available only when NS3000/V recognizes their existence
by means of DADCONF. NET. SYS. This file must be created after product installation because the file
defines the services purchased. A configuration file specifying an incorrect set of services may result in
unusable purchased services or error messages.
The time to create DADCONF. NET. SYS is after the final SYSDUMP tape has been loaded and the system
is fully up (and before NMMGR configuration). Enter the command STREAM CONFJOB. NET. SYS.
Passwords for MANAGER. SYS t NET should be added to the JOB logon string when appropriate. The job
should take two or three minutes to run and should return a message to the console telling you if your file
has been successfully created. If a failure occurs. try streaming the job again. If another failure occurs,
contact your SEA
You may encounter a situation where you have ThinLAN/3000 Link with incoming VT as your only
service, and then you decide to purchase all services for system-to-system communications. To revert
from having a VT-only service to having all services. restore @. NET. SYS, and then perform STREAM
CONFJOB.NET .SYS.

Configuration and Initialization Overview
Configuration and initialization of an NS3000/V network is a complex process. The configuration
portion of this process is made as easy as possible through the use of NMMGR, a utility that enables you to
interactively enter configuration information. Once each node in the network has been correctly
configured. the network can be initialized. Initialization is accomplished through the use of MPH
network commands.
Configuring and initializing an NS3000/V network involves the following major steps:

2-10

Network Management
• Network and configuration planning
• System Configuration
• Configuring the network with NMMGR
• Verifying network configuration with software utilities and tests
• Maintaining an up-to-date network directory through the use of the NS3000/V network
directory utility
Table 2-4 summarizes the required configuration and initialization steps, which are also briefly described
in the following subsections. Table 2-4 lists the appropriate sections of this manual where you will find
the information required to complete each step. In addition, for each step there is a list of the additional
references that you can consult for more or related information. The sections of this manual are arranged
in an order that closely corresponds to the steps required to configure and operate NS3000/V.

2-11

Network Management
TABLE 2-4. CONFIGURATION AND INITIALIZATION SUMMARY
Required Steps

References

Create the configuration file required
for initiating purchased services.

"Installing Network Services," earlier in this section.

Prepare for network configuration
using worksheets and
network/catenet maps.

Volume I, Section 3, Network Planning and
Configuration

Configure the link hardware devices
and pseudo-devices into the HP 3000
operating system.

Volume I, Section 4, System Configuration
For additional information:
MPE V System Operation and Resource Management
Reference Manual (32033-90005)

Study the use of the Node
Management Configurator, NMMGR.

Volume I, Section 5, NMS Configurator (NMMGR)

Using NMMGR, prepare the
configuration files required for
NS3000/V service and link
operation.

(All of the following are in Volume 1 of this manual.)
Section 6, Guided Configuration
or
Section 7, Link Configuration
Section 8, Network Transport Configuration
and one or more of
Section 9, IEEE 802.3 Network Interface Configuration
Section 10, Router Network Interface Configuration
Section 11, Gateway Half Network Interface
Configuration
Section 12, Loopback Network Interface Configuration

Create a network directory for nodes
requiring one; synchronize network
directories among all nodes in
network and catenet.

2-12

Volume I, Section 14, Network Directory
Volume I, Section 3, Network Planning and
Configuration

Network Management
TABLE 2-4. CONFIGURATION AND INITIALIZATION SUMMARY, continued
Required Steps

References

Configure any installed DS X. 2S
Link(s) using NETCONF'.

(32187-90001)

X.2S Unk for the HP 3000 Reference Manual

Initialize the Network Transport with
NETCONTROL) then the Network
Services with NSCONTROL.

Volume II, Section I, Commands

Initialize any optional DS Compatible
Links with DSCONTROL.

Volume II, Section I, Commands

Network and Configuratlon Planning
Before beginning configuration with NMMGR, you should prepare for the configuration activity by
completing the configuration worksheets included in Section 3. These worksheets will enable you to
collect and consolidate the information you will need to interactively enter via NMMGR.

System Configuratlon
Before starting a node's network configuration with NMMGR, you must define to the MPE operating
system all of the peripheral devices and software upseudo-devices" attached to the HP 3000 required for
input or output of data (I/O). This definition process is referred to u system configuratioll. SYStem
configuration is accomplished via the interactive SYSDUMP utility. Using SYSDUMP you can configure
software drivers for the INP (for Point-to-Point 3000/V, X.2S 3000/V, and DS-Compatible links), the
ATP (for the ASN 3000/V link), and the Lanic Local Area Network Interface Controller (LANIC), for
StarLAN/3000 and ThinLAN/3000 links (including the ThickLAN option of ThinLAN/3000).
HP 3000 data communications connections require pseudo-devices called virtual terminals which consist
of software that simulates the function of terminals. NS3000/V links and DS-Compatible links require
virtual terminals, which can be configured with SYSDUMP.
Finally, NS3000/V and its links may require changes to MPE system tables. This. too, can be
accomplished with SYSDUMP. System configuration for NS3000/V is described in detail in Section 4 of
this manual.

2-13

Network Management

Network Configuration with NMMGR
The information required for an HP 3000 to function as a network node is stored in a file called a
configuration file. This file can be created and subsequently modified using NMMGR. NM or NA
capability is required to run NMMGR, which uses a series of VPLUS/3000 block-mode screens to display
and accept configuration information. Use of NMMOR can be divided into three kinds of configuration:
• Link configuration, which defines link level parameters.
• Transport configuration, which defines network transport (OSllayer 3 and 4) information.
• LOlging configuration, which enables you to define which information about network activity
should be recorded. This information can be printed displayed on a terminal, or routed to a file.
This information is useful for network analysis and troubleshooting.
You can access NMMGR in two ways: using a function called Guided Configuration, or through what is
referred to as manual configuration. Guided Configuration enables you to configure the network more
quickly by automatically using default values for certain required configuration parameten, and by
automatically bypassing certain optional configuration tasks. To accomplish any of the tasks bypassed by
Guided Configuration, you will need to use manual configuration.

NOTE

Guided Configuration is described in Section 6, manual configuration for network links and transport are
described in Sections 7 through 13, and manual configuration for network logging is described in Section
14 of this manual.
Section 5 of this manual provides a more detailed introduction to NMMGR.

Configuration Verification
After you have completed hardware installation, system configuration with SYSDUMP and network
configuration with NMMGR, you will need to verify that each node is communicating correctly with
other nodes on the network and that all the installed software modules are current and compatible.
Utilties and tests for this software and line verification are described in Volume II, Section 2

2-14

Network Management

Network Directory
A network directory is a file containing information about other nodes in the network. All nodes with
point-to-point router links must have a network directory: if an IEEE 802.3 network is part of a catenet,
at least one node on the network must have a network diref.,tory. (Section 3 explains the function of the
network directory in more detail; Section 14 fully describes the network directory and the commands you
can use to modify this file.)
One of the tasks of both network managers and catenet administrators is to make sure that the network
directories residing on all nodes in the network and catenet, respectively, are up-to-date. This means that
when node information changes, and when nodes are either added or deleted, all network directories must
be updated to reflect the changes. Updating can be accomplished in several ways: by using the copy
subtree utility of NMMGR, by sending tapes of updated directories to the people responsible for
maintaining a node or network (such as the node manager or network manager), or by relating the
information that must change to each responsible person. Refer to Section 14 for more information about
the network directory.

2-15

NETWORK PLANNING
-.....-A_ND_C_O_N_FI_G_U_RA_T_I_ON

........

This section of the NS3000/V Network Manager Reference Manual explains concepts you will need to
undentand before you plan and install an NS3000 network or catenet.
This section will introduce and describe the following topics:

• Software Component~ including NS3000/V software subsystems and configuration files.
• Configuration concepts, including Internet and intranet routing, and the relationship of
symbolic names to network addresses.
• Network and eatenet configuration and administration tasks. Configuration tasks include
the procedures required to configure software on each network node, verify that the network is
functioning correctly, and start the network. Administration tasks include making sure that
changes to network nodes are recorded and that changes are coordinated among all network
nodes, when necessary.
• Network design, including guidelines to follow when designing a network or catenet.
• Configuration worksheets. The last section in this chapter contains worksheets that can assist
you in designing a network or catenet, and that you can use to prepare for configuration
with the configuration program NMMGR. The worksheet process includes the creation of a
network or catenet map that shows the placement of nodes and connecting links.

3-1

Network Planning and Configuration

SOFTWARE COMPONENTS
The following section describes the software components that make up NS3000/V services and link
products.

NS3000/V Software SUbsystems
The software and associated protocols that enable an NS3000 network to operate are divided into
units referred to as subsystems. Separate copies of these subsystems reside on each node in the network.
The following subsystems make up NS3000/V services and links:
• Network Services. The Network Services subsystem provides servIces that include Network File
Transfer (NFT) and Remote File Access (RFA). The Network Services subsystem will be
present on a node only if Network Services have been purchased (separately from the link) for
that node.
•

Network Transport. The Network Transport subsystem contains the protocol modules
corresponding to layers 1 through 4 of the 051 model. Network Interprocess Communication
(NetlPC) is part of the Network Transport subsystem.

•

Node Management Services. The Node Management Services subsystem provides configuration
file version checking, logging, and tracing. Logging enables network transactions to be Ulogged,"
or recorded, in a disc file. The recorded information can be used to assist in network
troubleshooting.

•

Node Management Configurator. The Node Management Configurator subsystem provides the
software that enables you to configure an HP 3000 as a network node. This subsystem includes
NMMGR, the Node Management Configurator program.

• Link Support Services. The Link Support services subsystem contains two software modules: the
Link Manager and the PC Link Manager. Both of these modules open, close, and otherwise
control physical links. The PC Link Manager performs these functions for NS
Asynchronous SERIAL Network Links; the Link Manager performs them for other NS3000/V
links.
• Communication Services (CS/3000). CS/3000 provides some of the diagnostic and link
management software required for NS3000/V links. CS/3000 is also used by DS-Compatible
links.

Configuration Flies
Part of the network installation process involves configuring the network using NMMGR interactive
configuration software. Through the use of NMMGR, several files containing information about the node
and the rest of the network to which it belongs will be created on each node. The information in these
files is accessed by various network subsystems while the network is operating. It is the information
provided by the configuration files that enables the network software to send and receive data in a
suitable form for each node and network link, and to direct data to the correct destination nodes.

Network Planning and Configuration
Three files can be created
NSCONF. NET.SYS.

each

network node: NMCONFIG. PUB. SYS, NSDIR. NET. SY8, and

NOTE

The filename NS{;ONF.NET.SYS is a default filename, and is the name
that HP recommends that you use for this configuration file. However, a
different filename can be used, as long as the file is located in the NET
group of the SYS account. The NSDIR.NET.SYS file that is active, i.e., is
in use when the network is running, must be named NSDIR. NET. SYS.
For purposes of discussion,
the names
NSCONF. NET. SYS
and
NSDIR. NET.SYS will be used to refer to these files throughout this

manuaL
Each of the files is described below:
NSCONF.NET.SYS. This file contains configuration information needed by the Network Transport
subsystem. This information enables the system to operate as a network node. Information rangin, from
the amount of data buffers to allocate for certain network functions to the telephone number of a
dial-up link are contained in this file. Most of the information configured via NMMGR is contained in
this file.
NSDIR. NET. SYS. This file, also called a network directory, contains information that enables network
software to translate node names (a node name is a symbolic ASCII-character name given to each
system in the network that identifies it to the rest of the network and to network users) into protocol and
address information. NSDIR. NET. SYS is actually the data file of a KSAM data file and key file pair.
The key file that will be created at the same time as the data file will be named using the first 6
characten of the data file, appended with the character K. For example, if the default data file
name is used, the key file will be named NSDIRK.

This file contains information needed for link level and NetlPC logging.
Parameten such as what network activities to record and where to record them are provided by this file.

NMCONFIG.PUB.SYS.

NOTE

Another file, called DADCONF. NET. SYS, is required to initialize
NS3000/V Network Services. Refer to Section 2 for information about
this file.

CONFIGURATION CONCEPTS
Before beginning network pla~ning and configuration, you must understand certain terms and
concepts that may influence your network', design and the values you enter for various configuration
parameten. This section describes the most important of these terms and concepts --and those that you
should understand in order to fully understand NS 3000/V networks. (Additional terms not included

3-3

Network Planning and Configuration
in this section are described in individual network configuration sections of this manual: Sections 7
through 13.)

NS Routing
Routing refers to the process used to determine the path that packets, or fragments of a message, take
through a network or catenet to reach a destination node. Routing between multiple networks in the
same catenet is referred to as internet routing; routing between nodes in the same network is referred to
as intranet routing. The routing mechanism used by a particdlar network is based on its network type.
The NS Network Transport subsystem provides intranet and internet routing. However, a message's
complete source-to-destination route is not determined before it is sent to its destination (unless the
destination is a logically adjacent node), because each node possesses information about only the path
that should be taken to the next node on the way to a destination.
The information about which node a packet should be directed to next is obtained by the Network
Transport from the NSCONF. NET.SYS configuration file. The information in this file is derived from
values configured using NMMGR. The values entered must therefore reflect the physical design of
your network. (Network design is further discussed later in this chapter.)

Intranet Routing
Intranet routing involves all the processes required to route a packet from one node in a network to
another node in the same network. Intranet routing can be very simple, as for an IEEE 802.3 network, or
potentially very complex, as for a point-to-point router network.
For an IEEE 802.3 network, in which each node is attached to a common bus (the cable) that is shared by
all the nodes, routing occurs as follows: Each node that has data to send acquires control of the bus, adds a
subnet address identifying the node (called a station address) to the packet, and sends it on the bus. After
the packet has been sent, the sending node relinquishes control of the bus. Each node will check every
packet that is sent on the bus for a station address that matches its own, and will receive only those
destined for it. Figure 3-1 illustrates an IEEE 802.3 network; note that the nodes on the network are all
logically adjacent to one another.

Figure 3-1. IEEE 802.3 Network
~
For point-to-point networks, nodes are connected to other nodes in the network via one or more
point-to-point links. A route may therefore include one or more intermediate nodes through which a ]

3-4

Network Planning and Configuration

"
"

packet must pass on its way to its destination. The routes to various remote nodes are configured into
nodal routing tables at each node. At an intermediate node, a packet will be received and forwarded to
the next node in the network based on the routing information configured at that intermediate node for
the destination node. Information about more than one route to the same destination node can be
configured into a node's routing table. If so, an internal algorithm selects the best possible route to the
destination node. Figure 3-2 shows an example point-to-point network. Note that more than one
possible route exists between nodes.
Alternate Routes. At each node, you can configure the name of the link that a packet should take to get
to a given remote node. By configuring multiple alternative links to reach the same destination, you can
provide several routes for packets to take to reach a destination. NMMGR allows you to specify an "entry
priority" for each alternate link to indicate the order of preference for configured outbound links to the
same destination.
Alternate routes can be useful if a link on the network becomes non-operational because of an intentional
shut down or a link failure. Refer to "Non-Operational Links'liater in this chapter for information about
how alternate routes can be used to circumvent non-operational links.

Figure 3-2-. Point-to-Point Router Network

Internet Routing
Internet routing involves all the processes required to route a packet from a node on one network to a
destination node on another network. Networks are connected to other networks via gateway nodes,
which are nodes that are configured either as a member of multiple networks or as a gateway half in
addition to another network. Internet routing is therefore concerned with which gateways and which
networks a packet will pass through to reach its final destination.
Internet routing decisions are made at both the node that originates the packet and at intermediate
ptewa,.. The destination network address is checked against a table that contains an entry for each
remote network in the catenet and specifies the gateway(s) on the network that can reach each remote
network. Because the purpose of internet routing is to get the packet to the correct destination network,
the packet will be forwarded to' the appropriate gateway. This will be repeated, if necessary, until the
packet reaches the gateway that is a member of the destination network. At this point, intranet routing
takes over to get the packet to the correct (and final) destination node.

3-5

Network Planning and Configuration

Symbolic Names
A name, when used in the context of NS3000/V networks, is a character string which identifies some
portion or component of a network or catenet. Names, because they can be defined by the user (in this
case, the Node or Network Manager) can be chosen to represent some meaningful and easily recognizable
concept. For example, if you had three networks in a catenet. you ~viJld name them NETt, NET2, and
NET3. Or, perhaps in your Installation three nodes "belonged" to the marketing, finance, and
manufacturing departments, respectively. You might choose t~ name them NODEMKTG, NODEFIN,
and NODEMFG.
Configuration of NS3000/V networks requires that you use NMMGR to configure each node. Many of
the items to be entered via NMMGR's interactive user interface (discussed in detail in Section S) are
names. The following sections describe the names that NMMGR will require you to configure.
Node Names
The node name is used to identify each system that is a node in the network or catenet. Each node name
used to designate a computer in the network or catenet must be unique, although a single node can be
identified by multiple names. Besides being used for configuration, node names are used in Network
Services commands (for example, the : DSLINE command) and intrinsics to designate upon which node a
particular networking activity is to occur. A complete node pame consists of three parts, which together
can be no more than SO characters, as described in detail in the following section.
NOTE

Other UP networking documentation may use the term "computer namell
instead of linode name. II A computer name is the same as a node name.

Node Name Format and Assignment. Each node in the network must be assigned at least one unique
node name. A fully qualified node name consists of three fields, each separated by a period:

nodename.domain.organization
When specifying node names, you must enter the delimiting periods. Each field can be up to 16
characters (alphanumeric, underscore or hyphens); the first character must be alphabetic.
Just as an MPE filename has a singular name, filename, and a fully qualified name,
filename. groupname. acctname, a nodename also has a singular name, nodename, and a fully qualified
name, nodename. dom:rin. organizat ion. The nodename must be unique for each node on the
network. The domain and organization do not need to be unique. You might choose a unique donain
name for each network in the catenel Note that if the default domain and organization of all the
nodes match they do not need to be specified in commands and intrinsic calls originating from nodes with
the same donrzin and organization names. If a user does not supply domain and organization fields the
fields will default to the local node's assigned domain and organization. This allows users to issue
commands or intrinsics with just the single portion of the nodename, nodename.
HP recommends that you use some convention when assigning names; for example, all nodes in the same
network could have the same domain name and all nodes in the same catenet could have the same
organization name.

3-6

Network Planning and Configuration
Multiple Node Names. A single node can be assigned more than one node name by specifying two (or
more) node names in the network directory. Although the node may have multiple node nam~ it can
have only one IP address (described in "Network Addresses" later in this section) unless it is a gateway
node, which will have more one IP address configured for each network it belongs to. Using more than
one .node name may be useful if you need to isolate sets of network traffic received or generated by the
same node. For example, if you previously had two UP 3000s but have consolidated their activities on a
single, more powerful HP 3000, you might have application software that uses two node names that
correspond to node names of your previous two computen. By using two node names for the single new
system, you could avoid having to modify existing software to accommodate the change.

Otller Names
During configuration with NMMGR., you will be asked for several other names in addition to a node
name. The node name is the only name that is exchanged between nodes and used by software on remote
systems; these additional names are required by only the software within the SYStem being configured.
The names described below must be composed of up to eight alphanumeric characters. and must begin
with a letter.
Network Interface Name. The network interface name is used to identify the software on a node that
provides an interface to a particular network. A useful convention is to name a network interface for the
network to which it provides an interface. For example. if you are configuring a node as a member of a
network named NETt, the name of the network interface to that network should be NETt. The network
interface name is used during configuration and as part of some commands that control network
operation. A node requires one network interface for each network to which it belongs. and one
network interface corresponding to the software loopback function. A node's multiple interfaces are
distinguishable by the use of a different network interface name for each.
During configuration, you may also be required to enter a home network name, which is simply the name
of one of the node's network interfaces. A home network name refers to the network interface name
that corresponds to one of the networks to which a gateway half node belongs. One of the networks to
which the gateway half belongs must be designated the home network to establish a source network
address for packets originating from the gateway half.
Link Name. A link Dame is given to each of the links connecting a node to other nodes on the same
network. Links should be named according to some convention you have defined. For example, for a
relatively simple network, you might choose to use the same name on different connected nodes to refer to
the link which connects them. In a more complex network, you might choose to name the link by a
combination of its protocol and logical device Udev) number. For example, BSC32 might refer to a link
using the sse protocol that is assigned Idev 32 during SYSDUMP configuration.
Router Node Name, Static Neighbor Node Name, Gateway Name. Configuration sometimes requires that
you specify the name of a node that belongs to a particular category. For example, a router node
name is the name of a node that can be reached via one or more router links from the node being
configured. A static neighbor node name is the name of a node that is on the same IEEE 802. 3
network as the node being configured. A gateway Dame is a name that refers to a node acting as a
gateway for the node being configured. These names need not be identical with the node name
configured for a node; these names identify subsets of configuration data related to a particular node.

3-7

Network Planning and Configuration

Network Addresses
An address, in the networking sense, is a numerical identifter defined and used by a particular protocol
and associated software to distinguish one node from another Addresses of different kinds can vary in
complexity depending on the need. For example, two of the protocols used by NS require addresses: the IP
protocol and the IEEE 802.3 protocol. The address used by the IP protocol is hierarchical; it identifies
both individual nodes and the network to which each belongs. The address used by the IEEE B02. 3
protocol is not hierarchical; it provides information only about nodes in a particular IEEE 802.3 network.

IP Address Format and Assignment
An IP address consists of two components: a network portion, whIch Identifies the network, and a node
portion, which identifies a node within a network. The terms network address and node address are
commonly used to describe these two components of the IP address. Together, they uniquely identify a
node within a catenet.
IP Address Classes. There are three IP address classes, each accommodating a different number of
network and node addresses. The address classes are defined by the most significant bits of the address, as
follows:
Class A--

El ::::::I::::::::::::::::::::::: I
1------ - - - - - I
II

Network Address

Node Address

Class B--

rn :::::::::::::
I:::: :: :: : : : :: : : I
1---- ------I
II

Network Address

Node Address

Class C--

~o:

::::::::::::::::::::
I:::::::I
l---.-.II
II

I000o..--

Network Address

Node Address

The address classes can also be broken down by address ranges. IP addresses are represented in NS3000/V
software by converting the bits to decimal values one octet at a time and separating each octet's decimal
value by a period ( • ) except between the node and network portions, which are separated by a space.

3-8

Network Planning and Configuration
Table 3-1 lists the number of networks and nodes and the address ranges for each address class:
Table 3-1. IP Address Classes
Class

Number of
Networks

Number of
Nodes

Address Range

127

16777215

000 000.000.000 - 127 255.255.255

16383

65535

128.000000.000 - 191.255255.255

2097151

255

192.000.000000 - 223.255.255 25S

224.000.000.000 - 255.255.255.255*

Reserved

*Note: The 'address 255.255.255.255 is reserved for NS3000/V loopback. Loopback is described in
Section 12.
To determine a network address and node address from an IP address, you must separate the network and
node address fields. For example, the bit representation of IP address 192.006.001 001 is separated as
follows:

indicates
Class C

),
1 1 000 0 0 0 . 00000 1 10. 0 000 000 1
I

Network Address

= 192.006.001

000 0 0 0 0 1
I

Node Address = 1

AssIgning IP Addresses. You must assign an IP address for each node on the catenet. To assign IP
addresses, you must determine network and node addresses.
To determine network addresses for each network, you must first determine how many networks your
catenet contains and where your network boundaries are. Each network m.ust be assigned a unique
network address. All nodes in the same network must be assigned the same network address.
UP has obtained a block of Class C addresses from the Defense Advanced Research Projects Agency
(DARPA). Even if you do not anticipate connection to DARPA's ARPANET (Advanced Research Projects
Agency Network), HP recommends that you obtain IP network addresses from the HP Network
Administration Office (NAO) to guarantee unique network addresses. To do this, contaet your lIP
representative or write to the NAO at the following address:
Network Administration Office, Department NET
Information Networks Division
Hewlett-Packard Company
19420 Homestead Road
Cupertino, California U.S.A. 95014
(408) 725-8111

3-9

Network Planning and Configuration

Do not assign any network and node addresses consisting of all Is or all Os. In NS3000/V software. the
node address 0 is reserved for messages that are broadcast to all nodes; the address of all Is is reserved for
loopback. (Note that the 3-digit decimal address of 2SS represents a byte of all Is.) ARPA standards also
reserve these addresses: all Is signifies messages for all nodes on the network. and all Os signifies messages
for the same node that originatpd the message or the same network ~s the originating node.

'~,

Node addresses must be unique only within each network. For example, you could have a node with node
address 5 in network 1 and another node with node address S in network 2. You can assign node
addresses according to your own needs, but they must be within the ranges for the IP address class that
you are using.

IEEE 802.3 Station Address Fonnat and Assignment
An IEEE 802.3 station address is assigned to every node on an IEEE 802.3 network. When a packet is
sent on the network, only the node whose station address matches the destination address in the packet
receives the packet. Hewlett Packard assigns a station address to each IEEE 802. 3 interface card during
manufacturing. The station address is used for network addressing on the IEEE 802. 3 network bus, and
has the following format:

hh-hh-hh-hh-hh-hh
where

h is a hexadecimal digit (0 -

9, A - F).

For HP 3000s, this factory-configured station address is in ROM on the LANIC interface card. You have
the option of specifying a different station address by using NMMGR (refer to Section 9). Each time the
card is initialized, either the factory-supplied station address or the NMMGR-configured address is
activated for use on the IEEE 802. 3 network.
In addition to checking the interface card, you can find out what your system's station address is by using
the LANDIAG diagnostic utility. After the HELP command and LANDIAG tests 1, 2, 3 and 13 are
performed, the utility displays the station address at the bottom of the display screen. Refer to the
LAN/3000 Diagnostic and Troubleshooting Guide for information on using the LANDIAG utility. Note:
Network Services and the Network Transport must be shut down before using LANDIAG.

Assigning Station Addresses.

HP recommends that you use the factory-configured station address
assigned to the LAN interface card. If you decide to assign your own address contact your HP
representative for more information.

Address Resolution
Address resolution in NS networks refers to the mapping of node names to IP addresses and the mapping
of IP addresses to subnet addresses. Two kinds of address resolution can occur on a node in an NS
network: First, the destination node's nodename must be mapped to the node's IP address. ~ond, for
some types of networks, the IP address must be mapped to a subnet address that identifies a node for the
protocols used by the subnet.

Node Name to IP Address Resolution
NS3000/V routes packets throughout catenets and networks based on the internet and intranet addresses
of each message·s destination node. However, network users and application programs use node names to

3-10

Network Planning and Configuration
designate the destination of a message.
corresponding addresses.

As a result, a method is required to map node names to their

The Network Transport uses one of three available methods to determine the addresses that corresPOnd
to a node name:
1. From the network directory (NSDIR. NET. SYS file) that resides on the node from which
communication originates. Every node with a point-to-point link must have a network
directory. This includes all nodes on router networks and any node functioning as a gateway
half.

2 By the use of the Probe protocol. The Probe protocol can be used only on IEEE 802. 3 networks.

3. By the use of a Probe proxy server. This method combines methods I and 2 listed above. A
Probe proxy server is a node on an IEEE 802.3 network that possesses a network directory and is
designated a Probe proxy server during configuration. Other nodes on the IEEE 802.3 network
can use Probe proxy requests to obtain information contained in the network directory that may
not be available elsewhere.
For each node, a choice from the above methods and the preferred order they are used can be configured
withNMMGR.

Name-to-address information for each node is contained in a data structure called a patb report. In
addition to a node's addressing information, each path report specifies the networking protocols used on
the node. When a connection is established between two nodes, the destination node's path report is
obtained by one of the three methods listed above. Once a node has received another node's path report,
the node receiving the information retains it so that a path report does not have to be obtained every time
a connection is established with the same destination node.

The network directory. The network directory file NSDIR. NET. SYS, which you can initially create with
NMMGR, contains a node's network directory. The network directory contains entries for remote nodes
that each include a remote node's node name and its path report. The first time a connection is initiated
from a node that has a network directory, the Network Transport software searches the NSDIR. NET.SYS
file for the destination node's node name and associated path report. The path report contains the IP
addreAies) associated with the destination node name. Every node having a point-to-point link (every
node on a router network, and every full or half gateway) must possess a network directory. However,
nodes on IEEE 802. 3 networks do not each require network directories. Instead, they can use the Probe
protocol to obtain path reports.
The Probe Protocol. IEEE 802. 3 nodes can use the Probe protocol to obtain path reports specifying
the names and corresponding addresses of other nodes on the network. When a node configured to use
the Probe protocol needs to establish a connection, it first multicasts a query to all the nodes on the
network, requesting a response from the node whose name matches the name in the message to be sent.
(Multicasting is similar to broadcasting, except that a message is sent to only a subset of nodes instead of
an nodes on the network.) If the name of a node on the IEEE 802. 3 network matches the destination
node name. it responds to the query by sending back its path report. The node sending the message then
uses this information to resolve the destination node·s address, ensuring that messages arrive at the
eorrect destination.
Probe Proxy Server Nodes. By itself, the Probe protocol can only obtain information about nodes on the
same IEEE 80L 3 network; to obtain information about nodes on other networks in the same catenet
requires additional help from a network directory. Therefore. if an IEEE 802 3 network is part of a
catenet, a network directory must reside on at least one of the IEEE 8023 network's nodes for messages
to be sent to nodes in other networks. If another node on the IEEE 802 3 network needs to establish a

3-11

Network Planning and Configuration
connection with a destination node that belongs to a different network on the catene~ the node with the
network directory can provide the sending node with addressing information about the destination node.
The node on the IEEE 802.3 network that performs this function is called a Probe proxy server. In
addition to possessing a network directory, the Probe proxy server must be designated as such during
configuration. HP recommends that the IEEE 802. 3 network's gateway node be used as the Probe proxy
server. HP also recommends that you create more than Olae Probe proxy server on each IEEE 802. 3
network so that if one of them is shut down, network directory information will still be available.

"""
)

Figure 3-3 shows an IEEE 802.3 network with two Probe proxy nodes. Probe requests (illustrated by a
dashed line) are sent to nodes that are configured to use the Probe protocol. Probe proxy requests
(illustrated by a dotted line) are sent to nodes that are configured as Probe proxy servers. Node A can
obtain a path report about node E, on another network, from nodes B or D. To send a message to node C.
information is obtained from node C itself; the use of a Probe proxy server is not needed.
HE_31M

/
,

,/
/

Figure 3-3. IEEE 802.3 Network Probe and Probe Proxy Requests

IP to Subnet Address Resolution
Once a packet is routed to the correct destination network, it needs to be directed to the correct
destination node within that network. For router networks, the IP address is the only address needed to
route the message within the router subnet. However, in IEEE 802.3 networks, the destination node's IP
address must be mapped to its IEEE 802.3 addre..
IEEE 802.3 Address Resolution with Probe Protocol. In addition to providing node name to IP address
resolution, the Probe protocol provides IP to IEEE 802.3 address resolution. The mapping of a given IP
address to an IEEE 802.3 address occurs as a result of a Probe request for address information.
IEEE 802.3 Address Resolution for Non-HP Systems. During configuration of IEEE 802. 3 nodes with
NMMGR, you will encounter an interactive configuration display screen that allows you to enter
addressing information about other nodes on the IEEE 802.3 network. This information resides in the
node's NSCONF. NET. SYS configuration file. It is only necessary to configure this screen if a remote

3-12

.~.

)

Network Planning and Configuration
node on the network does not support the Probe protocol and the remote node's IEEE 802. 3 address is
not configured in the network directory of either the source or Probe proxy server nodes. UP computers
support the Probe protocol; therefore, configuration of this information in NSCONF. NET.SYS may be
required only if a non-HP node is part of the network.

Configuration Terminology
The following subsections describe concepts and terms you will encounter during configuration of a
node with NMMGR. You will also need to be familiar with the concepts described when you plan
your network or catenet. Use these subsections to gain general familiarity with the terms and ideas
before beginning to plan or configure the network or catenet; you may also wish to use these
descriptions for reference in later stages of the planning and configuration process.

General Terms
Remote Node and Local Node. The term local node usually means the node that you are configuring or
to which you are logged on. A remote node is any othe,. node in the catenet; that is. any node other
than the local node.
Buffers. A buffer is a logical grouping of a system's memory resources used by NS3000/V. There are
several kinds of NS3000/V buffers: inbound transport buffers, outbound transport huffers, and store
and forward buffers. The amount of space allocated for these buffen can be specified using NMMGR.
Inbound and outbound buffers are allocated for each network interface on a node, regardless of the type
of network(s) to which the node belongs. Inbound buffers hold data being received by a node until it is
used by a particular protocol or a user process. Outbound buffers hold data that will be sent on a link (or
through loopback) from the originating node. The number of both outbound and inbound buffers can be
specified during configuration with NMMGR.
Store and forward buffers are allocated on gateway nodes (full and half) and on nodes belonging to
router networks. The number of store and forward buffers can be changed (via NMMGR.) to allow for
tuning to achieve better network performance.
Loopback. Software loopback enables a node to communicate with itself; in other words, it allows a single
node to be both the source and destination of a message. A network interface (see definition below) must
be configured to provide the loopback function.
Network Interface. The term network interface refers to the software that interfaces a node to a
network. On each node, one network interface is required for each network or gateway half connection,
and for the software loopback function. Most nodes, therefore, require two network interfaces: one for
the network the node belongs to and one for loopback. A full gateway requires a network interface for
every network to which it belongs. A gateway half requires a network interface for the gateway of which
it forms a part) and for the other networks to which it belongs. The term network interface is
often abbreviated as "Nf' throughout this manual.

Dial IJnk Terms
You should undentand the following terms used to desCribe dial (also referred to as switched) links:

3-13

Network Planning and Configuration
Direct Dial and Shared Dial. A direct dial link provides connection to a single remote system over a
phone line. The telephone number dialed by the local node to reach the remote node never changes unless
it is reconfigured with NMMGR. A sbared dial link provides connection to more than one remote system,
although to only one at a time. The link is thus shared by more than one remote node.
Autodial and Manual Dial. An autodial link refers to a link using automatic dialing hardware. This
hardware enables a remote phone number to be dialed without requirlllg a user to manually dial a
telephone number. Instead, the telephone number of the receiving modem IS entered during a node's
configuration, and when a connection must be made, the telephone number is read from the
NSCONF. NET. SYS configuration file and IIdialedtl automatically. In contrast, a manual dial link requires
human intervention; the receiving node's telephone number must be dialed at the sending node's location.
NS software will display a message at the system console requesting the system operator to dial the
number. Whether or not a link is autodial or manual dial depends on the capabilities of the hardware
(such as the modem or any additional devices) that is used.
Note that whether a link is direct or shared dial is independent of whether the link is autodial or manual
dial.
NOTE

In contrast to any dial links is a direct connect link, which does not rely
on switched public telephone lines but instead depends on "hard-wiredu
cable or leased lines to connect one node with another. Refer to Section I
for more details about direct connect, leased lines, and dial links for each
NS3000/V link type.

Dial ID Protocol. The Dial ID protocol is a proprietary Hewlett-Packard protocol used to provide
security for dial links. The protocol verifies the identity of nodes dialing in to a receiving node, and
ensures that both the local and remote node have the required security access. HP computers support
the Dial ID protocol; however, other computer systems may not support it. The DialiD protocol must be
disabled (during configuration) if the node being configured will be connecting to a node that does not
support this protocol.
Security String. A security string is an alphanumeric ASCII character string that acts as a password for
dial links. The security string is used by the Dial ID protocol. When a node attempts to connect to
another node via a dial link, security strings are exchanged between the nodes. Each node checks the
security string it receives against a configured list of valid security strings. If a match is found by both
nodes, the link can be used. If one or both of the security strings fail this check, then the link is
disconnected.
Security string checking can be disabled at any node (via configuration) if desired.

Router Network Terms
You will encounter most of the following terms during planning and configuration of a router network:
Hop Count. The term hop count is used in two ways: (1) an Intranet hop count is the maximum number
of intermediate nodes that lie between a source and destination node on the same router network;
and (2) an internet hop count is the number of gateways that are used to route a message to its
destination network. Because two partner gateway halves perform the function of a full gateway, they

3-14

Network Planning and Configuration
are counted together as a single internet hop. Note that if no intermediate nodes lie between a source and
destination, the hop count is zero.
Non-Adjacent and Adjacent. The term adjacent, when used in the context of configuring routing for a
router network, refen to a node that is separated from a given node by no intermediate nocles. In other
words, the adjacent node lies at the other end uf a link connected to a given node. A non-adjacent nocle.
in contrast, is a node that is separated from a given node by intermediate nodes.
Directly Connected. The term directly connected describes nodes that are members of the same network.
For example, if node A is directly connected to node H, A and H must be members of the same network.
Do not confuse the term "directly connectedl' with the term "direct connect," which describes a
non-switched point-to-point link (hardwired or leased line).
Entry Priority. During configuration of router networks, you must define the route used to
transmit information from the node you are configuring to the other nodes in the network. If
desired, you can configure more than one route to the same node. If you do so. you can specify which
of the multiple routes should be chosen first. For example. if one route has a greater number of
intranet hoPIJ you might wish to give it a lower priority (specified as a lower numerical value) than
another route with fewer hops. If for some reason the route given the highest priority is not available,
the message will be routed to its destination with the alternate (but lower entry priority and greater
number of hops) route.
If the same value is used for all entry priorities, the Network Transport software chooses the route to be
used. The choice is based on an internal algorithm that selects the best route by taking into account some
of the configured characteristics of the intervening links.

Gateway Tenns
You will need to undentand the following terms if the node you will be configuring will be Part of a
catenet:
Reachahle Networks. A reachable network is a network that can be accessed (with additional intemet
hops possibly required) by a particular gateway.
Neighbor Gateway. A neighbor gateway is a gateway node (full or half) on the same network as the
nocle being configured.
Gateway Half. A gateway half is a node on which a gateway half network interface has been configured
with NMMGR. Together, two gateway half nodes joined by the same link perform the function of a
gateway. which is to connect two networks.
Gateway Half Pair. Two gateway halves connected by a gateway half link are considered a aateway half
pair.
Gateway Half Link. A gateway half link is a link that joins two gateway halves. A gateway half link
must be either an NS Point-to-Point 3000/V Link or an Asynchronous SERIAL Network Link.

3-15

Network Planning and Configuration

Non-Operational Links
Network links may be non-operational because of any of the following: (1) the link was intentionally shut
down with the NETCONTROL command, (2) a link failure has occurred or (3) the link has not been started.
A non-operational (or "downed") link can affect the routes that messages take to reach their destinations.
Router networks can automatically reroute packets around a non-operational link. Rererouting will occur
if alternate links to a destination have been configured at the nodes that are the endpoints of the
non-operational (or "downed") link. This rerouting over alternate links is called automatic rerouting.
N53000/V can also provide rerouting for lnternet packets. Messages reaching a gateway that are
Intended for a downed link (at that gateway) will be redirected to another gateway on the same network
that can reach the remote network.

Router Network Automatic Rerouting
Router network automatic rerouting will reroute packets in a router network around non-operational
router links. This rerouting will occur whether or not the destination node is a member of the router
network.
The two nodes at the ends of a downed link will detect the fact that the link is down. If alternate links
to the destination are configured at nodes that detect a downed link, the nodes will reroute packets over
these alternate links. For router network rerouting, only the nodes that detect the downed link can select
an alternate link. For messages that originate at some other node, configuration adjustments may need to
be made to bypass the link that is not operating.
No immediate indication that a link is not operational will occur at other nodes (besides those directly
connected by the IIdownedu link) on the network or catenet. However, messages will not reach their
destinations and a timeout error will occur for the connection.
Alternate Links. The link that a router node uses to reach another node in the network is configured via
NMMGR. If the node can use more than one link to reach another node, the link used is the link that is
up with the highest value in the Entry Priority field of the Router Reachable Nodes configuration screen.
The other configured links are the alternate links.
If the destination node is a member of the same network as the node that detects the downed lin~ the
selected link is an alternate link configured for the destination node. If the destination node is not a
member of the same network, the selected link is an alternate link configured for the appropriate gateway
to the destination node (the local destination).
Example 1: Automatic Rerouting. In Figure 3-4, LINK! has been configured at NODEA (UNode AI? as
the first link to use to reach NODEC (because LINK2 is a slower link than LINKl). LINK2 has been'
configured as the second link to use. At NODEB. LINK3 has been configured as the first link to use to
reach NODEC. with LINK 4 as the second link to use. If there is a transaction between NODEA (the
source) and NODEC (the destination), the packets would be transmitted over LINK! and LINK 3. If
LINK3 is down. NODES will automatically reroute the packets over LINK4 (Figure 3-5).

3-16

Network Planning and Configuration

UNK4

Figure 3-4. Router Network with Alternate Links

UNK4

Figure 3-5. Router Network with Rerouting
Example Z: Non-Detecting Nodes. As previously noted, only the nodes that detect the downed link can
select an alternate link.
If a packet is rerouted (by a node that detected a downed link) to a node that did not detect the failure,
the node that did not detect the failure will not automatically reroute the packet over a different link
than that used originally. This is because the node that did not detect the failure has no way of knowing
of the downecllink.
Figure 3-6 illustrates this situation. Figure 3-6 is similar to Figure 3-5, except that there is only one
link between NODES and NODEC (LINK 3). Again, NODEA has LINK 1 configured as the first link to
use to reach NODE<=, with LINK2 as the second link to use. NODES has LINK3 configured as the
primary link to use to reach NODEC, and LINKI as a secondary link. (L1NK3 has a higher number
configured for its Entry Priority than LINKl.) In this network, if there is a transaction between NODEA
(the source) and NODEC (the destination), and LINK3 is down, packets would not reach NODEC.
Although packets will be rerouted from NODER over LINK 1 to NODEA. and NODEA could use LINK2
to reach NODEC. the packets will not be rerouted because NODEA has no knowledge of the failure of
LINK3.
A variation would exist if NODED did not have an alternate route to NODEC configured (i.e.. LlNKl).
In this case, no automatic rerouting would occur. Packets would not be rerouted to NODEA from
NODEB.
In both of the above situations, a timeout error would eventually occur for the connection. An error
message indicating this would appear at NODEA, the source node.

3-17

Network Planning and Configuration

UNK2

Figure 3-6. Packets from NODEA to NODEC are not rerouted.
Adjusting for Non-operational Links. If a link is either shut down via NETCONTROL or if it fails, the
routing tables used by each affected intermediate node will reflect inaccurate information in that the
tables will indicate that the non-operational link should be used.
To change these routing tables so that messages are not sent out over downed links, you can reconfigure
the routing information entered via NMMGR. The reconfigured routes should include only those links
that are operational. Use the online configuration branch of Guided Configuration to most easily make
required changes.
In the above situations, (Example 2), the node manager could use the online configuration branch of
NMMGR Guided Configuration and the NETCONTROL UPDATE command to change a node's router
network tables. For the situation in which an alternate route to NODEC is configured at NODEB but not
at NODEA, the manager could change NODEA's configuration to indicate that LINK2 should be used to
reach NODEC.
For the situation in which no alternate route to NODEC is configured at NODEB, the manager could
change NODEB's configuration to indicate that LINK 1 should be used to reach NODEC. NODEA would
also need to have LINK2 configured as the link to reach NODEC for packets from NODEB to reach
NODEC.
Effect on Internet Transactions. Packets will be rerouted in a router network even if the source and
destination nodes are not members of that router network.
As noted previously, if the destination node is not a member of the same network, the alternate link will
be another link configured for the appropriate gateway to reach the destination node.

For example, in Figure 3-7, packets from NETX arriving at NODEA to NETZ will be rerouted around
LINK3 to get to NODEC, the gateway to NETZ.

3-18

Network Planning and Configuration

UNk2

NETY

Figure 3-7. Packets forwarded through NETY are rerouted.
Router Network Automatic Rerouting Summary. In summary, router network automatic rerouting has
the following characteristics:
• Only the nodes that detect the downed link can select an alternate link.
• Automatic rerouting occurs when the node (or nodes) that detects a downed link can use an
alternate route to reach the destination node or appropriate gateway.
• If other nodes are affected by a downed link and have alternate links that they can use, the
operator can intervene and manually change the routing table at that node.
• Packets win be rerouted in a router network even if the source and destination nodes are not
members of that router network.

Internet Redlrectloo
Intemet redirection is the redirection of packets from one gateway to another gateway. If a gateway's
link to a remote network is down, and the gateway's configuration file indicates another gateway on the
local network that can reach the remote network, the fint gateway will rebuild its internet routing table
to show the other gateway as the gateway to use to reach the remote network.
This facility can be used to compensate for a gateway's downed link by redirecting packets to another
gateway. If a gateway receives a packet for a remote network and its internet routing table shows
another gateway (on its network) to use to reach the remote network, IP will redirect packets to the
remote network through the other gateway. The other gateway is called the redirect gateway. This
redirection will occur even if the redirect gateway and the source node are not on the same network.
Example 3: Internet Redirection. For an example of what happens when an internet packet is redirected,
refer to Figure 3-8.
As shown, NODEC and NODED are gateways to NETZ.
At NODED, NODEC is confiaurecl
as the gateway to use to reach NETZ. NODEC is configured as a member of NETY and NEn, and bas

3-19

Network Planning and Configuration
LINKCE configured as the link to reach NODEE. NODEC also has NODED configured as a gateway to
reach NETZ.
A packet from NODES to NODEE would take the following path:
NODES to NODEC
NODEC to NODEE
NEll
NETY

""
NElX

" " ..

" .. .

.. ..

. ..

Figure 3-8. Packets from NODES to NODEE go through NODEC.

If LINKCE goes down (Figure 3-9), NODEC will rebuild its internet routing table to show that packets to
NETZ should be routed to NODED. If NODEC then receives a packet with NODEB as the source node
and NODEE as the destination node, NODEC will redirect the packet to NODED. A packet from
NODEB to NODEE would then take the following path:
NODEB to NODEC
NODEC to NODED
NODED to NODEE
NEll
NETY

" ...
NElX

" " ...

. ...

.. ...

.. ..

. ..

.. ..

.. ,
... ,

" .. ..

" ..

"I..

Figure 3-'. NODEC redirects packets for NODEE to NODED.

3-20

Network Planning and Configuration
If redirected packets must go through a a node that has no knowledge of the downed link, the packets
may not reach the alternate gateway. For example, if the link between NODEC and NODED did not
exist, packets redirected by NODEC would have to be sent to NODER. However, NODER has no
knowledge that LINKCE is down. NODEB will therefore not forward the packets to NODED. Because
no packets will ever arrive at NODEE, a timeout will eventually occur for the connection. An error
message indicating this would be displayed at the source node, NODER.
In the above situation, the node manager at NODEB could use the online configuration branch of
NMMGR Guided Configuration and the NETCONTROL UPDATE command to change NODEB's internet
routing tables so that NODEB will route packets for NETZ to NODED.
Redirection of Subsequent Packets on IEEE 802.3 Networks. If a gateway on an IEEE 802. 3 network
receives a packet that it redirects to another gateway, it also sends a message to the source node telling it
to route subsequent packets for the remote network through the alternate gateway. Such a message,
informing a node that all future communication should occur through another gateway, is called an ICMP
(for Internet Control Message Protocol) redirect message. Redirect messages will be sent only if the
source, original gateway and redirect gateway are all on the same IEEE 802. 3 network.
When the source node receives the redirect message, it will alter its internet routing table to show the
redirect gateway as the gateway to use to reach the remote network. Subsequent packets from the source
node to the remote network will be sent directly to the redirect gateway.
Alterations to the internet routing table based on redirect messages are temporary. If any event OCCUR
that causes that node to rebuild its internet routing table (link up, fails, link started or deleted. network
interface started or shut down, NETCONTROL UPDATE command), the node will rebuild the table based on
NMMGR. configuration values that were read when its network interfaces were started (or the last
NETCONTROL UPDATE command was entered). If, because a link is still down, a gateway sends a redirect
message to the node, the node will again alter its internet routing table.
Note that the redirect gateway will be entered in the internet table even if the source node did not have
the redirect gateway originally configured as a gateway.
Example 4: Redirect Messages. R.efer to Figure 3-10 for an example of a redirect message being sent on
an IEEE 802. 3 local area network. As shown in Figure 3-10, NODES has been configured 80 that a
packet from NODEB to NODEE would take the following path:
NODED to NODEC
NODEC to NODEE
If LINKCE were down. NODEC would rebuild its internet routing table so that NODED is the pleway to
NETZ. If NODEC then receives a packet with NODER as the Bource node and NODEE as the destination
node, NODEC will redirect the packet to NODED. NODEC will also send an ICMP redirect message to
NODEIl NODER will update its routing table so that NODED is the gateway to NETZ, and will send
subsequent packets to NODEE through NODED.

3-21

Network Planning and Configuration

NEll

,,
NElX

NElY

,
'

, ...

...

, ...

... ...

... ,

Figure 3-10. Packets from NODER to NODEE go through NODED.
Note that ICMP redirect messages are sent only when the IP protocol determines that the source, gateway
and redirect gateway node are members of the same IEEE 802.3 network. IP determines network
memberships in this situation according to the IP addresses used for the transaction. If the source nocle
has more than one IP address (it is a member of more than one network), and it must use a gateway to
reach the destination node, the source nocle will select its IP address so that the network portion will
match the network portion of the gateway's IP address.
In Figure 3-11, a packet is ~nt from NODEA to NODEE. and LINKCE is down. Since NODEA (the
source) is not on the same network as NODEC. no redirect message would be sent. A packet from
NODEA to NODEE would take the following path:
.NODEA to NODEB
NODEB to NODEC
NODEC to NODED
NODED to NODEE

3-22

Network Planning and Configuration

N£TV

""
tETX

" ...

" ... ...

.. ...

.
.. ...

. ..

" ... .
" .. ..

...

Figure 3-11. Packets from NODEA to NODER go through NODRC and

~ODED.

However, once a message originating from NODEB was sent to NETZ, NODEB would receive a redirect
message and NODEI would update its internet routing table so that it used NODED as the gateway to
NETZ. Subsequent packets originating from either NODEA or NODEB would then be sent to NODED on
their way to NETZ.

Intemet Rerouting Summary. In summary, internet rerouting has the following characteristics:
• If a gateway's link to a remote network is down, and the gateway had another gateway on its
network configured to the remote network, it will rebuild its internet routing table to show the
other gateway as the new gateway to the remote network.
• If a gateway receives a packet for a remote network and its internet routing table shows another
gateway (on its network) to use to reach the remote network, IP will redirect packets to the
remote network through the other gateway (the redirect gateway). This redirection will occur
even if the redirect gateway and the source node are not on the same network.
• If a gateway on an IEEE 802. 3 network receives a packet that it redirects to another gateway, it
also sends a redirect message to the source node if IP determines that the source, gateway and
redirect gateway are all on the same IEEE 802. 3 network.

NETWORK INSTALLATION AND ADMINISTRATION
Many tasks must be completed before a network or catenet is ready to operate. If there is more than one
network (i. e., a catenet is being created), the catenet administrator is responsible for overseeing the
completion of the tasks. If you are the catenet administrator or network manager, it is your
responsibility to make sure that the configuration of network software at each node is consistent and
correct and that software and hardware is correctly installed before catenet or network operation
begins. If you are a node manager, it is your responsibility to make sure that the software and hardware
instaUecl and configured on your node (or nodes) is correct, and consistent with the plans for the network
u determined by the network manager.

3-23

Network Planning and Configuration
This section provides an overview of the tasks that must be completed to start network or catenet
operation. Details of the steps summarized here can be found in other sections of this manual.
Initial installation can be divided into six main parts:
1. Planning
2. Software and hardware installation
3. Configuration
4. Nodal validation, verification, and synchronization

S. Network startup
6. Line verification

Planning
Planning a network or catenet is an important process that must be done with care to ensure that the
network meets the needs of your organization. Many factors must be taken into consideration when
planning the network or catenet: for example, volume of usage over particular links, volume of
non-network usage of each node, physical layout needs and limitations (such as geographical distances),
and desirability of connections to non-NS3000/V nodes. These and other factors are discussed in
IINetwork and Catenet Design" later in this c~apter.
This manual contains worksheets that you can use to assist in network and catenet planning and
configuration. You should already have a network design (including physical topology and types of
links) in mind before you use the worksheets. However, you will need to draw a plan of the network,
called a network map, before you begin filling out the worksheets. An example of a network map and
specific directions for creating your own map are included in nConfiguration Worksheets" later in this
chapter.

Software and Hardware Installation
After you have determined the network or catenet's design, software and hardware must be installed
on each node. Make sure that each node has the following hardware, as appropriate, for the particular
kind of link:
• Hardware interface card(s). For NS Point-to-Point 3000/V links this is an INP; for
StarLAN/3000, and ThinLAN/3000 (including ThickLAN option) links this is a LANIC; for NS
Asynchronous SERIAL Network links, this is is an ATP.
• Cables. For NS Point-to-Point 3000/V and NS Asynchronous SERIAL 3000/V links, this is
hardwire cable for whatever length necessary to reach between every pair of nodes. For
ThinLAN/3000 this is .18 em. coaxial cable; for ThickLAN this is .4 em. coaxial cable. For
StarLAN/3000, this is unshielded twisted-pair wire. If any nodes are dial (modem) links, you
win need cable to connect the modem with the HP 3000.
• Modems and other dial link devices. You will need a modem for each telephone line that a node
is connected to. If desired, and if it is not a function performed by your modem, you might also

3-24

!~/"(

Network Planning and Configuration
need a device that performs automatic dialing (usually called an autocall unit). See AppendixB
for a list of supported modems and autocall units.
• Other hardware. You may need additional hardware, depending upon the types of links you plan
to instalL For example, ThickLAN links require devices called MAUs (Media Attachment Units~
Networks using StarLAN/3000 might require a device called a Bridge. Refer to the hardware
installation manuals listed in the Preface of this manual for detailed hardware requirements of
the type of network you are installing.
The node must have the following software installed before configuration and subsequent network startup

Cian occur:
• The software products that are provided on MPE Fundamental Operating System (FOS) tapes
• The software provided on a subsystem tape containing NS3000/V link product software and
services, if applicable.

Configuration
Network configuration tasks must be completed on each node on the network or catenet. Network
configuration consists of using two utilities: SYSDUMP, which should be installed on your HP 3000, and
is used for configuration of non-network hardware devices as well as network devices, and NMMGR,
which is used to configure NS3000/V software.

3-25

Network Planning and Configuration

SYSDUMP Configuration
Specifically. SYSDUMP allows you to configure:
•

Logical device (LDEV) numbers to refer to hardware peripherals, Including communications
cards;

• Virtual terminal (VTERM) numbers to correspond to virtual terminals. software that simulates
the function of terminals;
• MPE system table resources.

NMMGR Configuration
NMMGR allows you to configure items such as:
• Node names and addresses
• Link types (so that network software responds in accordance with the hardware providing the
link to another node)
• Buffer sizes
• Timeout values
• Preferred point-to-point routes to get from one node to another
• Intranet and internet routes
• Network directory entries
• Probe proxy server nodes
• Logging parameters, such as which subsystems should be logged
Guided Configuration and Manual Configuration. NMMGR provides two methods of configuring a
node: with Guided Configuration. or through manual configuration. Guided Configuration enables you to
configure the network more quickly by automatically using default values for certain required
configuration parameters, and by automatically bypassing certain optional configuration tasks. To
accomplish any of the tasks byPaSSed by Guided Configuration. you will need to use manual
configuration. Also, to configure the network directory. you will need to use manual configuration.

3-26

Network Planning and Configuration
NOTE

UP strongly recommends that you use Guided Configuration to initially
configure each node, and for most network maintenance and updating. Use
manual configuration onl, if Guided Configuration does not provide access
to the configuration data you need to change.

...

The defaults used by guided configuration are the defaults indicated in sections 7 through 13 of this
manual
Manual configuration with NMMGR can be divided into five parts:
•

Link configuration.

• Configuration of Network Transport parameten that must be completed for every node,
regardless of link type. This is referred to as transport configuration.
•

Network Interface (NJ) configuration. This consists of configuring parameten used by each of
the node's network interfaces. These parameten differ for different types of links. 80 NI
configuration is separated from configuration of Network Transport items that must be
configured for all link types. If a node is a gateway (either full or half), separate NI
configuration is needed for each of its links (one for each network or gateway half link).

•

Logging configuration. Logging configuration for each NS3000/V subsystem can be configured
during this portion of network configuration tasks.

•

Network directory configuration. Configuration of each node's network directory (for nodes on
router networks. proxy server nodes on IEEE 802. 3 networks, and for full or half gateway nocles)
consists of entering node names. their IP address(es), and the protocols used on each node.

Section S of this manual explains how to use NMMGR. Section 6 explains how to use guided
configuration; sections 7 through 13 illustrate the interface displayed when manual configuration is used.
Section 14 shows and describes the interface used for configuring the network directory. Sections 6
through 14 all explain the parameten you need to configure for each configuration task.

Nodal Validation, Verification, and Synchronization
After a node's network hardware and software has been installed and it has been configured using
SYSDUMP and NMMGR, certain tests need to be performed to ensure that the software and
hardware are operating correctly. These tests should be performed before the Network Transport is
started.
Each node manager should perform the following tests on his or her node:
•

Validation of the configuration files using the NMMGR Validate Configuration File screen.
This validation utility, which is part of NMMGR, is described in Section S. It checks that
certain configuration file items are correct and consistent.

• Synchronize network directories on each node. The network manager (or catenet administrator,
for a multi-network catenet) should make sure that every network directory is the same. HP

3-27

Network Planning and Configuration
recommends that you accomplish this by physically giving tapes containing copies of a master
network directory to the node managers of every node that will contain a network directory.
This master network directory should be configured by the network manager (or catenet
administrator) on a node that is designated the Central Administrative Node--which means
that it will always contain the most up-to-date ver,non of the network directory. This
node's network directory should actually be a catenet directory--it should contain entries for
each node in the catenet.
If a protocol and addressing information for a particular node is missing from a network
directory, messages will not be able to reach that node in cases in which their correct transmission
depends on receiving information from that network directory.

NOTE

If configuration files created with a previously released version of NMMGR
currently reside on your system, you must convert the files so that they are
compatible with the current version of NMMGR and other Node
Management Services software. A utility called NMMGRVER can convert
your files; Appendix C of this Volume describes NMMGRVER and explains
how to use it.

Network Startup
After the node manager has determined that the network software on each node is functioning correctly,
the network can be started. To start the network, you must issue the following commands on each node:
•

NETCONTROL to start the Network Transport software

•

NSCONTROL to start Network Services

The syntax and use of these commands is described in Volume II, Section I of this manual.

Line Verification
After each node's Network TransPOrt software has been started, the network manager (and, if
applicable, the catenet administrator) should perform the line verification tests described in Volume 0,
Section 2 of this manual. These include:
• Start software loopback.
• Test the operation of Network Transport by performing the fPC and XPT line tests.
• Use the QuickVal utility to check for correct operation of Network Services.

3-28

Network Planning and Configuration

• Start other network interfaces (either on this node or other nodes~ use the NSLOGON diagnostic
to ensure that connectivity exists between network interfaces.
• If desired, perform the IPe, XPT, and QuickVal tests to test for connectivity to remote nodes.

NETWORK AND CATENET DESIGN CONSIDERATIONS
Network and catenet design must take many factors into consideration: the desired physical location of
the computers comprising the network or catenet's nodes; the volume of projected communications traffic
between nodes; communications traffic patterns; and the possibility of connections to other nodes (such u
those in a public data network) are just some of the criteria to consider.
These factors will affect your choice of NS network type (IEEE 802.3, router) as well as choice of
specific links. You may also want to consider using DS-Compatible links for specific purposes, such u
satellite or X. 2 S connections.
Some design decisions depend upon the capabilities of NS links. These capabilities and corresponding
restrictions are described in the following sections.

Line Speed
Line speed is a measure of the rate at which data is transmitted by a physical link (usually measured in
bits or kilobits per second). The maximum line speed varies among different NS links. Line speed
may therefore influence your choice of link. Although line speed does not indicate the exact throughput
of a particular link, it can be used on a comparative basis to indicate relative throughput. ThickLAN
links have the highest line speed, at 10 megabits/second. StarLAN/3000 links have a line speed of I
megabit/second. In general, an IEEE 802. 3 link will be faster than a point-to-point router link because
the bus topology provides a faster routing mechanism than a series of point-to-point hops. Among
pteway half and router links, Point- to-Point 3000/V links have higher line speeds than Asynchronous
SEIlIAL Network links due to ASNP protocol limitations. Point-to-Point links using the LAP-B
protocol, which allows full-duplex transmission, are faster than links using the BSC protocol, which
allows only half-duplex transmission. Links using leased lines will have a higher line speed than links
using normal telephone lines.
Consult your UP representative for line speeds and the most up-to-date performance data for various
links.

Geographical Location
The geographical location of the computers that will be part of your network or catenet will be an
important factor in deciding both the physical topology and the kinds of links comprising the
network or catenet.
If all of the nodes you want to connect are located relatively close to each other (in the same building.
for example), you might choose to connect them via a ThickLAN or ThinLAN/3000 link. If you wish
to connect Pes to the IEEE 802.3 network, you can use ThinLAN/3000 or StarLAN/3000 links to
connect one or more Pes to an UP 3000.

3-29

Network Planning and Configuration
Another option for nodes located in the same geographic k.catlon are hardwired (direct-connect) router
links. You might wish to use a point-to-point router n~twork if the distance between some nodes on
the network will be greater than the maximum distance allowed between nodes on an IEEE 802.3
network.
If, on the other hand, you need to connect nodes that are geographically distant--for example, UP
3000s located in different cities--you might choose to connect them via a dial link. For NS dial links,
you can choose either an NS Point-to-Point 3000/V or an Asynchronous SERIAL Network link.
Finally, if you need to use satellite transmission, due to the large geographical distance between nodes, or
if you need to have access to other nodes on a public or private X.25 network, you might choose to use
DS links.

Special Cases
The following sections describe certain design requirements for special situations, such as shared dial
links, personal computers, and using non-UP 3000 minicomputers on an NS network.

mal

LInks

Shared dial links have two limitations that must be considered when designing a network. First, a shared
dial link cannot be used as an intermediate link in a router network. Any other kind of dial link can be
used for intermediate links, but shared dial links should only be used to connect leaf nodes--that is,
nodes that only receive messages targeted for themselves. Second, shared dial links cannot be used as

~Q~~

Personal Computers
Personal computers (PCs) can be used as nodes by being connected to UP 3000s with ThinLAN/3000,
StarLAN/3000, and Asynchronous SERIAL Network links. PCS cannot be used as intermediate nodes
in router (Asynchronous SERIAL Network link) networks. Like a shared dial link, a personal
computer must be used as a node that receives only those messages targeted for itself.

Other Non-HP 3000 Nodes
Non-UP 3000 minicomputers, such as UP 1000s and HP 90008, can operate as nodes on NS IEEE
802. 3 network~. If you want to include one of these computers in your catenet, it must be part of an
IEEE 802. 3 network. Router networks must be comPOsed of only UP 30008 (and Pes, if
applicable).

DS-CompaUble LInks
DS/3000 links cannot be used as store-and-forward links on a router network. An UP 3000 can be
configured to have both a DS link and an NS link; however, HP recommends that nodes with DS links
configured be used as leaf nodes.

3-30

Network Planning and Configuration

Network Interfaces and Design
The network interface (NI), the software that provides an interface between a node and a network,
specifies the type and maximum number of links that can be configured for a node. Because a node's
network interface(s) determine what links can be configured for the node, links are said to be
configured underneath network interfaces.
Remember, there are three kinds of network interfaces (in addition to loopback):
•

LAN80Z,.3 for IEEE 802.3 networks

• Router for networks that use point-to-point routing
• Gateway half for nodes that function as gateway halves
Each HP 3000 must have at least one non-gateway half network interface configured. This network
interface must be associated with the network to which the system belongs.

Number

Network Interfaces

A node can have up to eight network interfaces configured. For each network interface, the maximum
number of links you can configure and the kinds of links possible are determined by the network
interface type, as follows:
•

A LAN802. 3 network interface can have only one IEEE 802.3 link configured under it;
however, each IEEE 802. 3 link can support a large number of nodes. ThickLAN cable supports
up to 100 nodes per segment; ThinLAN cable can be used for up to 30 nodes per segment; and
each StarLAN should be used for up to 50 nodes.

• A router network interface can have up to 40 links configured under it. Router links can be
NS Point-to-Point 3000/V or Asynchronous SERIAL Network links.
• A gateway half network interface can have only one link configured under it--the gateway half
link. Links connecting two gateway halves can be only NS Point-to-Point 3000/V or
Asynchronous SERIAL Network links.

Gateways

If more than one (non-loopback) network interface is configured on a node, the network portions of
the IP addresses configured for the interfaces should differ to corresPOnd to the multiple networks to
which the node belongs.
A network can have up to 16 gateways (combined number of full gateways and gateway halves).
Full Gateways versus Gateway Halves. NS3000/V allows you to choose between connecting two
networks with a full gateway, and connecting them with two gateway halves. A full gateway is a node
configured as a full member of two (or more) networks. The node is considered a member of each of
the networks for which it is configured.

3-31

Network Planning and Configuration
A node that is a gateway half is configured as a member of a network and as a partner of another
gateway half. A gateway half link that joins two networks connects two nodes (a gateway half pair) by a
~,\
point-to-point link (NS Point-to-Point 3000/V or Asynchronous SERIAL Network link). The gateway')
half link and pair is not considered a network itself. Each of the paired gateway halves is configured as a
member of a different network--the two networks to be connected- -and as a gateway half on the same
gateway half link. Together, the two gateway halves function a.s a full gateway.
The following subsections explain situations in which you might want to use a gateway half pair rather
than a full gateway to connect networks:
Gateways Connecting Router Networks. If you need to connect two router networks, fewer catenet
administrative tasks might be required if the networks are connected via two gateway halves rather than
one full gateway. A full gateway must possess mtranet routing information about nodes on all of the
networks to which it belongs; a gateway half, in contrast, needs to possess only intranet routing
information for the network to which it belongs. Making a node a gateway half therefore reduces the
amount of configuration changes that must be made to it. If the change occurs to the network to which
the node's partner gateway half belongs, the node's NSCONF. NET.SYS configuration file does not have to
be updated. You might choose to use a gateway half link between two geographically or organizationally
distanced networks for this reason, to reduce the amount of information that has to be passed between
different network managers.
Gateways Connecting IEEE 8020.3 Networks. IEEE 802.3 networks must use gateway halves to connect
to adjacent IEEE 802.3 networks in the same catenet. This is because no more than one LAN802.3
network interface can be configured per node.

Network Boundaries
The term network boundary refers to the divisions between multiple networks. For example, you might
think of two networks in the same catenet as being logically disjoint; hence divided from each other by a
network boundary. Nodes in each network, of course, will have the same network address (network
portion of the IP address), which will differ on the two networks. The networks will be connected by
appropriate link or links; by either a gateway half link or a node acting as a full gateway.
The location of some network boundaries is sometimes dictated by the differences in link types used in
two adjacent networks: for example, an IEEE 802. 3 local area network must be logically disjoint from a
router network. Two such networks, connected by a gateway half link or a full gateway, are separated by
a network boundary.
You may wish to establish network boundaries even among links connected by the same link type so that
one group of nodes is isolated from another for administrative purposes. For example, you might divide a
group of nodes into two router networks instead of one network because you want two different
individuals (network managers) to be responsible for each of two smaller groups of nodes. The following
are other situations in which it might be useful to establish additional network boundaries:
• Situations in which you want to place nodes that will frequently communicate with each other
into the same groups. Such groups might reflect your installation's organization. Separating
nodes that need to communicate infrequently can result in less distance, in terms of intranet hops,
between nodes that do communicate frequently, resulting in improved performance within each
network.
• Situations in which the arrangement and configuration of one group of nodes is not expected to
change often, and the arrangement of another group is expected to change fairly often for some
extended period of time. Separating the nodes into two networks can isolate the stable nodes

3-32

~.\

Network Planning and Configuration
from those whose configuration has to change to reflect the addition or deletion of nodes.
Changes made to the frequently changing network need be reflected in additions to only the
network directories on the more stable network, instead of to the NSCONF..NET. SYS
configuration file for each node.
• Situations in which you want to restrict access to a group of nodes.

Network Implementation and Support Plan
Once you have designed your network or catenet, your UP representative will submit the design
specifications and other information to UP as part of your Network Implementation and Support Plan
(NISP). Networking consultants will review the plans for your network and inform your own HP
representative of any changes that need to be made to the design for the network or catenet to operate
effectively.

Network Maps and Configuration Worksheets
The remainder of this chapter consists of worksheets intended to assist you with both designing your
network and preparing to configure your node. Included in the worksheets are instructions on how to
construct network and catenet maps that illustrate the network and catenet's design. Creating these maps
will enable you to visually check your design.
NOTE

You may wish to use copies of the network and catenet maps you submitted
with your NISP for use with the worksheets. instead of redrawing them.
Once you have drawn the map, ask yourself the following questions to make sure your design adheres to
the considerations mentioned above:

1. Are all of the nodes in the network within roughly SSO meten of each other?
If 80, consider connecting them with ThinLAN/3000 links. The maximum cable length for
segments of ThinLAN/3000 cable is 18 S meters, with a maximum of three segments connected
by repeaters.
2. Are all of the nodes in the network within roughly 1SOO meters of each other?

If 80, consider connecting them with ThickLAN (thick coaxial cable~ The maximum cable length
for each segment of ThickLAN coaxial cable is SOO meters, with a maximum of three segments
connected by repeaters.

3. Are nodes located at remote sites? (For example, in different buildings in the same city, or in
different cities?)

3-33

Network Planning and Configuration
If so, consider installing a router network using dial links or leased lines. Choose leased lines if
you have a critical need for clear transmission or if the volume of data to be transmitted is
relatively large.
4. Is the set of nodes you wish to connect composed of some nodes that are in close proximity to one
another (for example, in the same building) and other nodes that are geographically distanced
(for example, in different buddings or different cities)?

If so, you may wish to use a combination of HP StarLAN or UP ThinLAN networks (for nodes
that are located near one another) and dial links (for nodes in different buildings or cities).
Do you need to connect personal computers to the network?
If so, proceed to the following questions:
(a) Do you want some personal computers to communicate directly with each other without
having to go through an HP 3000?
If so, consider either HP StarLAN or HP ThinLAN. Networks of personal computers can be
created using HP StarLAN or HP ThinLAN links. One or more of the personal computers
can also be connected to one or more UP 3000s using StarLAN/3000, an UP StarLAN Bridge, or
ThinLAN/3000 links.
(b) Will you need to connect personal computers to UP 3000s over dial links (if, for example,
personal computers are located at remote sites)?
If so, choose the HP SERIAL Network.

6. Will HP 90005, HP 1000s, or other minicomputers (such as Digital Equipment VAX (TM)
minicomputers) need to be part of the network?
If so, you will need to use them as nodes on a coaxial cable local area network (HP ThinLAN or its
ThickLAN option).
7. Do you need access to nodes on public or private X. 25 networks?

If so, consider using DS/3000 X. 25 links.
8. Do you need to use satellite connections (because of distance and speed requirements)?
If so, you will need to use DS/3000 Satellite links.
9. Is a subset of nodes either geographically or organizationally distanced from another subset of
nodes?

If so, you may wish to establish a network boundary between them in order to make them two
separate networks joined by a full gateway or two gateway halves.
10. If you decide to connect two networks via a gateway, would it be administratively easier (and
require less configuration if changes occur) to join the two networks by a gateway half link
rather than a full gateway?

3-34

Network Planning and Configuration

11. If you have decided you need an IEEE 802. 3 network, do you need to connect any nodes on it
with nodes that are part of another IEEE 802. 3 network?
If so, one of the nodes on the IEEE 802. 3 network must be a gateway half which connects to
another gateway half that is a node on the remote IEEE 802.3 network.
12. If you need to use a gateway half, is the partner gateway half in the same building or further
away?
If the two gateway halves are in the same building, you can use a direct connect link between
them. If the two gateway halves are further away, you will need to use a dial link or leased line
between them.

3-35

Network Planning and Configuration

CONFIGURATION WORKSHEETS: TERMINOLOGY
Here are brief descriptions of some key terms used In the "Configuration Worksheets: Instructions"
subsection, which follows.
catenet--A set of interconnected networks.
central administrative node--A node on a non-LAN network designated for keeping an up-to-date
network directory.
full gateway--A node that belongs to more than one network and can communicate with each network to
which it belongs by using store and forward. A full gateway has one IP address for each network.
gateway--A term that refers to either a full gateway or a gateway-half pair.
gateway balf--A node that belongs to at least one network and also has a gateway half network interface
configured. The gateway half network interface includes a point-to-point link connecting the node to
another gateway half node, called a partner gateway half. Together, the gateway half partners function
as a full gateway by performing store and forward over their connecting link.
gateway-half link--A term that refers to a point-to-point link connecting two gateway-half nodes.
gateway-balf pair--A term that refers to two gateway half nodes connected by a point-to-point link
and together functioning as partners to act as a full gateway.
internet hop count--The number of full gateways plus the number of gateway-half links that a packet
must pass through in moving from one network to another.
internet routing--The routing of a packet from one network to another network.
intranet hop count--The number of intervening nodes on a router network between a source node and
destination node.
intranet routing--The routing of a packet from one node to another node on the same network.
IP address--A complete IP address comprises a network address and a node address. The network address
identifies a network, and the node address identifies a node within a network. IP addresses are divided
into three classes. Each class accommodates a different number of network and node addresses. IP
network addresses can be obtained from the HP Network Administration Office to guarantee unique
network addresses. IP node addresses can be assigned according to your own needs but they must be
within the ranges for the IP address class you are using.
link name--The name of a gateway-half link or a router link. The link name can contain as many as
eight characters. All characters except the first can be alphanumeric; the first character must be
alphabetic.
network--A group of computers connected so that they can exchange information and share resources.
network directol'y--A repository with connection information about all nodes in a catenet.
network name--The name of a network in your catenet. This name can contain as many as eight
characters. All characters except the first can be alphanumeric; the first character must be alphabetic.

3-36

Network Planning and Configuration
node--A computer in a network.

node name--A node name consists of three fields, each separated by a period:

node.demain.organization
When specifying a node name, you must enter the delimiting periods. Each field can contain as many as
16 characten (alphanumeric, underscore or hyphens); the first character must be alphabetic.

,oIDt-to-,oI..t lI..k--A link connecting either two nodes in a router network or two gateway halves.
proxy server--A node on a LAN which provides network directory information to a requesting node on
the same LAN.

3-37

Network Planning and Configuration

CONFIGURATION WORKSHEETS: INSTRUCTIONS
You should use configuration worksheets to help you carefully plan your catenet and to make the
NMMGR configuration process as easy as possible. HP recommends that you use all worksheets, even if
you are an experienced user. The term worksheets is used loosely here and pertains to maps, tables, and
sheets where you will list values you plan to configure.
Figure I is an overview of the worksheet process and depicts a catenet with a four-node LAN, a
three-node router network, and two gateway halves that form a gateway-half pair. You will need one
set of worksheets for your catenet, one set of worksheets for each network in your catenet, one set of
worksheets for each gateway-half pair in your catenet, and one set of worksheets for each network
interface on each node. Appendix A contains worksheets you will need. Keep the sheets in Appendix A
intact, but make copies of the sheets as needed.

CATENET

NETWORK WORKSHEETS
LAN802.3

ROUTER

GATEWAY-HALf
PAIR

NODE WORKSHEETS

I I

NODE NODE NODE NODE

NODE NODE NODE

I
NODE

Figure 1. Overview of Worksheet Process
You should complete the catenet worksheets first because the network worksheets and gateway-half pair
worksheets are derived from information on the catenet worksheets. Node worksheets are derived from
information on the catenet, network and gateway-half pair worksheets.
We will illustrate the instructions that follow by completing some sample worksheets. The table numbers
and figure numbers we reference will be based on an example.

3-38

Network Planning and Configuration

r:\

Catenet Worksheets
The catenet worksheets consist of a catenet map, used to show an overview of your catenet. and a catenet
table. Vou will take the following steps when filling out the catenet worksheets.
• Draw sketches of each network in the catenet (Catenet Map)
• Write network names, IP network addresses and network types (Catenet Map)
• Draw gateway nodes (Catenet Map)
• Indicate network boundaries (Catenet Map)
• Complete Catenet Table (Table I)

C8tenet Map
Figure 2 is an example of a catenet map. We will use this sample catenet throughout the instructions to
help explain the other drawings and tables that make up the configuration worksheets.
Before you can draw your catenet map. you must know how many networks your catenet will contain.
and you must know each network type (router or LAN). The catenet in our example (Figure 2) contains
three networks. NET 1 is a LAN. NET2 is a router network and NET 3 is a LAN.
Vou must decide where you want your networks to be physically located and how they will be physically
connected. Therefore, you must determine which nodes will be used as gateway nodes (full gateways or
pteway halves) to communicate with remote networks.

Communication Between Networks
Because the main purpose of the Catenet Map is to show how the networks are connected. gateway nodes
are the only nodes you should draw on the Catenet Map. All other nodes and their networks can be
represented by drawing sketches of the networks, as shown in Figure 2.
In our example, Node C is a full gateway that belongs to NET 1 and NET2. Nodes G and H are gateway
halves that belong to NET2 and NET3, respectively. Nodes X and Yare gateway halves that belong to
NETI and NET3. respectively.
NOTE

For reasons of simplicity. we have used single letters to represent node
names in our example. Actual node names must be of the form listed in the
terminology subsection. As for addresses, the network portions of IP
addresses used in our examples have been reserved for such use. You should
not use C 192. 006. 001, C 192.006.250, C 192.006.251. C 192.006.252, C
192. 006. 253 or C 192.006.254 for your actual network addresses.

3-39

Network Planning and Configuration

Network Boundaries
Once you have drawn your gateway nodes. you have established network boundaries.
Let us again consider our example and look at Figure 2. Because Node C in our example is a full gateway
and belongs to both NET 1 and NET2. the boundary between these two networks is at Node C itself. For
purPOses of the map. we have drawn this boundary through the middle of Node C. The boundary between
NET2 and NET3 is along the gateway-half link that connects gateway nodes G and H. The boundary
between NETt and NET3 is along the gateway-half link that connects gateway nodes X and Y. Network
boundaries can be depicted with dotted lines. as we have done in Figure 2.

IP Network Addresses
Each network in your catenet must have a unique IP network address. Add these IP addresses to your
catenet map.
In our example, we assume that we have been assigned the Class C IP network addresses shown in Figure
2. The specific IP node addresses do not need to be shown until completion of specific parts of the
network worksheets, so we will represent node portions of IP addresses with XXX in some maps and tables.

3-40

Network Planning and Configuration

CATENET MAP

---------------------------,----------------------------------------•
NET1
C 192.006.001 XXX
LAN

•
•
••

NET2
C 192.006.250 XXX
ROUTER

r-------------- ----------- ---------------------------------

-------~

NET3
C 192.006.251 XXX
LAN
•~~~-~-----------~------~--------------------~-----------------------Figure Z. Catenet Map

CompleUng the Catenet Table
Once your catenet map contains the information just described, you are ready to complete the Catenet
Table (Table I).
The information requested for the fint three columns of the Catenet Table can be taken directly from the
Catenet Map, as we have done in our example. As for the Implementation Priority column, consider
which networks must be operational in as little time as possible. You also may want to consider which

3-41

Network Planning and Configuration
networks will be the easiest to initiate. AnalyzIng these and other factors important to you) determine
the order in which you plan to initiate your networks, and then enter the information in the
Implementation Priority column of the '- atenet Table.
When you have completed both the Catenet Map and the Catenet Table, you have finished the catenet
worksheets.

TABLE 1.

NETWORK

NET1

NET2
NET3

3-42

CATENET TABLE

NETWORK TYPE
(LAN. ROUTER)

LAN
ROUTER
LAN

IP NETWORK ADDRESS

IMPLEMENTATION
PRIORITY

C 192.006.001 XXX
C 192.006.250 XXX
C 192.006.251 XXX

1
2
3

Network Planning and Configuration

Network Worksheets
For each network in your ca.tenet. you are asked to draw a map of the network and to complete two
tables. One table lists nocle-specific information, and one table lists network routing information.
You also are asked to complete worksheets for each gateway-half pair in your ca.tenet. The worksheets
for a gateway-half pair consist of a map of the gateway-half nodes and their connecting link, and a table
containing information about the gateway-half network interfaces.
For our sample catenet, five sets of network worksheets need to be completed--one set for each of the two
LANa, one set for the router network, and one set for each of the two gateway-half pairs.
You wm take the foDowing steps when fiDing out a set of network worksheets.
• Draw your map. showing all nodes and node names. (For router networks. also show all router
links and link umes. For a gateway-half pair, include the link name.)
• Use dottecllines on your map to indicate connected networks.
• Complete the table(s)--two for each network, one for each gateway-half pair.

3-43

Network Planning and Configuration

LAN Network Worksheets
One set of LAN network worksheets should be used for each LAN in your catenet. The LAN network
worksheets consist of a map of the LAN and two tables. One table contains information about each node
on the LAN, and one table contains network-specific internet routing information. We now refer to
NET1, one of the LANs in our sample catenet, to describe thp "AN Network Worksheets in detail. Use
the discussion of our sample LAN Network Worksheets as a gUide for filling out your own LAN Network
Worksheets.
LAN Network Map. Figure 3 is a drawing of the network map for NETt. The network map is a more
detailed drawing of the same network. shown in the Catenet Map (Figure 2). The network name, the IP
network address and the network type are listed at the top of the network map. This information is
derived from the Catenet Map, which should be kept available at all times.
In our example, the Catenet Map shows that nodes C and X are gateway nodes. We mark them as such on
the NETl network map and draw dotted lines to show the networks that the gateway nodes can reach.
We then add the remaining NETl nodes and their names to the network map. We also indicate that
nodes C and X are proxy servers.

LAN NETWORK MAP

r----------

I
I
I

NET1
C 192.006.001 XXX

•

LAN

I
I

NET2

•
•

GATEWAY NODE
lONETt

PROXY SERVER

C·
I
I
Ito

GATEWAY NODE

TONET3i
PROXY SERVER

- - -- ---- --- -- ---- - - --.
NET3

•

I
I

•
Figure 3. LAN Network Map

'~
;

~-44

Network Planning and Configuration

LAN Network Table. We refer to the LAN Network Map to fill in the LAN Network Table (Table 2).
We complete the first column by listing the names of all the nodes on NET 1. We then assign to each node
an IP address that is unique within the network. We list only the node portions of the IP addressea
because we have listed the IP network address at the top of the table. In the third column of Table 1, we
indicate that nodes C and X are proxy servers. In the fourth column, we indicate that nodes C and X also
are gateway nodes. For the Implementation Priority column, we rank the nodes in the order we think
they should be configured.

TABLE 2.
NETWORK

LAN NETWORK TABLE
NAME:

NET1

IP NETWORK ADDRESS:

NODE NAME

A
B
C

C 192.006.001 XXX

IP NODE ADDRESS

001
002
003
004

PROXY SERVER

GATEWAY NODE

(YIN)

IMPLEMENTATION

(YIN)

PRIORITY

YES
YES

4
1
2

3-45

Network Planning and Configuration
LAN Internet Routing Table. The purpose of the LAN Internet Routing Table (Table 3) is to list all
possible networks that can be reached from each gateway node on a LAN. such as NET! in our example.
As shown on the Catenet Map. NETt includes two gateway nodes, C and X. We indicate in our LAN
Internet Routing Table that NETt nodes using Node C as a gateway can reach NET2 in one hop and
NET3 in two hops. In the IP Node Address column of the LAN Internet Routing Table, we list the node
portion of Node C's IP address.

For Node X, we list the same type of information in the LAN Internet Routing Table.

TABLE 3.

LAN INTERNET ROUTING TABLE

NETWORK NAME:

NET1

IP NETWORK ADDRESS:

C 192.006.001 XXX

THROUGH
GATEWAY NODE

IP NODE ADDRESS

003

DESTINATION
NETWORK/ADDRESS

NET2/
C 192.006.250 000

NET3/
192.006.251 000

NET3/
C 192.006.251 000

NET2/
192.006.250 000

004

3-46

HOPS NEEDED TO REACH
DESTINATION NETWORK

Network Planning and Configuration

NOTE

For NET3) the other LAN in our sample catene~ we follow the same
protedures. Figure S shows the network map for NET3, and tables 6 and 7
are the network and internet fallting tables for NET3.

Routes" Network Worksheets
One set of Router Network Worksheets should be used for each router network in your catenet. The
router network worksheets consist of a map of the router network and two tables. One table contains
information about each node on the router networ~ and one table contains network-specific internet
routing information. We now will refer to the router network °'in our sample catenet to describe the
Router Network Worksheets in detail. Use the discussion of our ample Router Network Worksheets as a
guide for filling out your own Router Network Worksheets.
Router Network Map. NET2 is the router network in our sample catenet. Figure 4 is a drawing of the
network map for NET2. The network map is a more detailed drawillg of the same network shown in the
Catenet Map (Figure 2). The network name, the IP network address and the network tyPe are listed at
the top of the network map. This information is derived from the Catenet Map, which should be kept
available at all times.
In our example, the Catenet Map shows that nodes C and G are gateway nodes. We mark them as such on
the NET2 network map and draw dotted lines to show the networks that the gateway nodes can reach.
We then add the remaining NET2 nodes and their names to the network map. We also indicate that Node
G is a central administrative node.

ROUTER NETWORK MAP

------.,•

~1BMYNODE
• TONE1\

NET1

UNK2

UNK3

(iA1'EW\Y NOOE

1OHET3:

--.•

~ANL

i-------------------- - - -- -

••
•
•

NET3

••
•

Figure 4. Router Network Map

3-47

Network Planning and Configuration

Router Network Table. We refer to the Router Network Map to fill in the Router Network Table (Table
4). We complete the first column by listing tht names of all the nodes on NET2. We then assign to each
node an IP address that is unique within the network. We list only the node portions of the IP addresses
because we have listed the IP network address at the top of the table. In the third column of Table 4, we
indicate that Node G is a central administra tive node. In the fourth column, we indicate that nodes C
and G are gateway nodes. For the Implementation Priority column, we rank the nodes in the order we
think they should be configured.

TABLE 4.

NET2

IP NETWORK ADDRESS:

C 192.006.250 XXX

NODE NAME

IP NODE ADDRESS

001

002
003
004

F
G

.:)

ROUTER NETWORK TABLE

NETWORK NAME:

005

CENTRAL ADMIN.
NODE? (YIN)

GATEWAY NODE
(YIN)

YES

IMPLEMENTATION
PRIORITY

3
4

YES

5
1

3-48

Network Planning and Configuration
Router Internet Routing Table. The purpose of the Router Internet Routing Table (Table S) is to list all
possible networks that can be reached from each gateway node on a router network, which is NET2 in our
example.
As shown on the Catenet Map. NET2 includes two gateway nodes. C and G. We indicate in our Router
Internet Routing Table that NET2 nodes using Node C as a gateway can reach NETt in one hop and
NET3 in two hops. In the IP Node Address column of the Router Internet Routing Table, we list the node
portion of Node C's IP address.

For Node G. we list the same type of information in the Router Internet Routing Table.

TABLE 5.

ROUTER INTERNET ROUTING TABLE

NETWORK NAME:

NET2

IP NETWORK ADDRESS:

C 192.006.250 XXX

THROUGH
GATEWAY NODE

IP NODE ADDRESS

DESTINATION
NETWORK/ADDRESS

001

NET1/
192.006.001 000

NET3/
C 192.006.251 000

NET1/
C 192.006.001 000

005

HOPS NEEDED TO REACH
DESTINATION NETWORK

3-49

Network Planning and Configuration

LAN NETWORK MAP
~
C 192.006.251 XXX

NET2

NET1
GATEWAY NODE
TO NET1:
PROXY SERVER

GATEWAY NODE
J

Figure 5. LAN Network Map (NET3 in example)

3-50

TO NET2;
PROXY SERVER

Network Planning and Configuration

~
... ""

\.~•. -

TABLE 6.

NETWORK NAME:

NET3

IP NETWORK ADDRESS:

C 192.006.251 XXX

NODE NAME

I P NODE ADDRESS

PROXY
SERVER (V/N)

GATEWAY NODE
(YIN)

001
002
003
004
005
006

YES

I
J

LAN NETWORK TABLE

K
L
Y

IMPLEMENTATION
PRIORITY

1
3
4

YES

5
6
2

3-51

Network Planning and Configuration

TABLE 7.

LAN INTERNET ROUTING TABLE

NETWORK NAME:

NET3

IP NETWORK ADDRESS:

192.006.251

THROUGH
GATEWAY NODE

IP NODE ADDRESS

001

XXX

DESTINATION
NETWORK/ADDRESS

HOPS NEEDED TO REACH
DESTINATION NETWORK

NET2/
C 192.006.250 000

NET1/

C 192.006.001 000

006
C

NET2/
C 192.006.250 000

3-52

NET1/
192.006.001 000
2

Network Planning and Configuration

Gateway-Half Pair Worksheets
One set of Gateway-Half Pair Worksheets should be used for each gateway-half pair in your catenet.
The Gateway-Half Pair Worksheets consist of a map of the two gateway half nodes and their connecting
link, and one table that contains information about the gateway half network interfaces. We now refer
to one of the gateway-half Pairs in our sample catenet to describe the Gateway-Half Pair Worksheets in
more detail. Use the discussion of our sample Gateway-Half Pair Worksheets as a guide for filling out
your own Gateway-Half Pair Worksheets.
Gateway Half Map. Our sample catenet contains two gateway-half pairs, as shown in our Catenet Map.
One gateway-half pair is made up of nodes G and H and their connecting link, and the other
gateway-half pair is made up of nodes X and Y and their connecting link. Let us focus on the G and H
gateway-half pair.
Figure 6 is a drawing of this gateway-half pair. We show the two nodes and the networks to which they
belong. In addition, we select a name for the link. We have decided to name the link LINK.R.Ll.

GATEWAY HALF MAP

NET2
C 192.006.250 XXX

ROUTER

UNKRL1
.---~--------------~---~-------

------------------~----------

H
NET3
C 192.006.251 XXX

LAN
JFiaure 6. Gateway-Half Map

3-53

Network Planning and Configuration

Gateway-Half Network Interface Table. ThIs table (Table 8) is based on the map we have just discussed.
We list both gateway-half nodes, the fulllP addresses of the partner nodes, the connected networks, and
the name of the link. Usually, the link name will be the same from the perspective of each gateway half.
·The reason we list the address of the partner gateway half is that the partner's address is entered during
configuration of a gateway half network interface.

'TABLE 8.

GATEWAV-HALrNETWORK INTERFACE TABLf

NETWORK NAMES:

NET2 t NET3

GATEWAY NODE

G/NET 2
H/NET 3

3-54

FULL IP ADDRESS
or PARTNER

C
C

192.006.251 001
192.006.250 005

CONNECTED NETWORK

NET3

NET2

LINK NAME

LINKRL1
LINKRL1

Network Planning and Configuration
NOTE

Figure 7 and Table SA pertain to the other gateway-half pair in our
sample catenet.

GATEWAY HALF MAP

NET1
C 192.006.001 XXX
LAN

'. - .. --- -- - - -- - --- ---

NET3
C 192.006.251 XXX
LAN
Figure 7. Gateway BaH Map

3-55

Network Planning and Configuration

TABLE SA.

GATEWAY-HALF NETWORK INTERFACE TABLE

NETWORK NAMES:

GATEWAY NODE

X/NET 1
Y/NET 3

NET1 t NET3

FULL IP ADDRESS
OF PARTNER

C 192.006.251 006

C 192.006.001 004

CONNECTED NETWORK

LINK NAME

NET 3
NET 1

LINKRL2
LINKRL2

3-56

Network Planning and Configuration

Node Worksheets
The main purpose of the node worksheets is to determine ahead of time the information you will need to
configure during NMMGR's Guided Configuration. This information depends on the type of network to
which a node belongs. Guided Configuration includes information for routing, links, and protocols.
You take the following steps when you start to complete the node worksheets.
• Fill in the necessary internet routing information (intranet routing information also for nodes on
a router network).
• Determine the values for fields you will configure during Guided Configuration.
• Perform the actual Guided Configuration.
Node worksheets contain routing information, screen names, NMMGR paths, fields you will configure, and
instructions on how to determine values for these required fields. The worksheets list only the fields you
a-n configure during Guided Configuration, which allows you to configure your nodes as quickly as
possible. Detailed descriptions of all fields are located in other sections. Screen names are given in
uppercase letters, and the NMMGR path used to reach a screen is listed in parentheses following the
screen name. Figure numbers and page numbers are also given.
We will continue to refer to our example as we discuss the node worksheets, and figure numbers and table
numbers still will be based on the example. Descriptions of fields should be applicable to all situations.

NOTE

To demonstrate our example, we have filled out values on the following
node-worksheet pages based on previous worksheet information. In cases
where information could not be taken from previous worksheets, values
have been left blank.

3-57

Network Planning and Configuration
After you choose to perform Guided Configuration, you select the ppmmtri!l!lINI.~::. ::~ function key to
perform first-time configuration of a node. You then select an N.....
press the appropriate
topology function key. For NI names, use the network names on the network maps. This way, you will
be able to keep track of the NI names you enter. You will then visit the Node Name Configuration
Screen, shown below. (This screen is always visited dUring loopback guided configuration, but is visited
for LAN, router, PC-router and gateway half guided configurations only if a node name has not already
been configured. )

name..··and

NODE NAME CONFIGURATION (NETXPORT. NODE. NAME) Fig 8- 3, p. 8- S
Nooe~me

Name of the node you are configuring. Must be in the form node.donr1in.organization.

3-58

Network. Planning and Configuration

LAN Node Internet Routing
As an example of a LAN nodets routing worksheet t look at Table 9. This table shows the internet routing
information that we plan to configure for Node B on NETt in our example. We see from our LAN
Internet Routing Table (Table 3) that NET 1 includes nodes C and X as gateway nodes. This table also
shows that NET I nodes can use Node C as a gateway to reach NET2 in one hop and NET 3 in two hoPit
and that Node X can be used to reach NET3 in one hop and NET2 in two hops. We decide to configure
each gateway to reach both networks, which means that more than one gateway is available for Node B to
reach the same remote network. We are not required to configure multiple gateways to reach the same
network. It is our choice. When multiple gateways are configuredt the software determines which route
to use--usually the one with the fewest hop counts.

Internet routing information is not necessarily the same for all nodes on a network. Suppose we do not
want Node A in NETI ever to communicate with any node on NET3. When completing the internet
routing table for Node At we would not list NET3 as a destination network and we would not use Node X
as a gateway node because it would route packets to NET3.

TABLE 9.

LAN NODE INTERNET ROUTING

NODE NAME:

IP ADDRESS:

C 192.006.001 002

NETWORK

NAME:

NET1

GATEWAY NODE/IP ADDRESS

DESTINATION NETWORKS/
IP ADDRESSES

HOP COUNT

C/ C 192.006.001 003

NET2/C 192.006.250 000
NET3/C 192.006.251 000

1
2

X/ C 192.006.001 004

NET2/C 192.006.250 000
NET3/C 192.006.251 000

2
1

3-59

Network Planning and Configuration
LAN CONFIGURATION SCREENS
As an example of filling out configuration fields for a LAN node, we have chosen Node B on NET!.
Only information derived from previous worksheets has been filled out.

LINK CONFIGURATION (LINKCONF) Fig. 7-1. p. 7-4
Link Name

Assign a link name that is eight alphanumeric characters or fewer; the first character must be
alphabetic.
IEEE802. 3 LINK DATA (LINKCONF .linkname) Fig. 7-2, p. 7-6
Logical Device

The ldev number of the LANIC that will be configured in SYSDUMP.
PROBE PROTOCOL CONFIGURATION (N ETX PORT • NI. niName. PROTOCOL. PROBE) Fig. 9-4. p. 9-10
Proxy Enabled _ _~

Answer Y if this node will be a proxy server (will have a network directory). Refer to the LANl
Network Map (Figure 3).
IP PROTOCOL CONFIGURATION (NETXPORT. NI • niName. PROTOCOL. I P) Fig. 9- 3. p. 9-7
IP Address

C 192.006.001 002

FulllP address of the node being configured. Refer to LAN Network Table (Table 2).

3-60

Network Planning and Configuration
Note: This page contains information for one gateway. Additional Bateways need their own information,
but we will focus on only one gateway for this example. During Guided Configuration. press the
l':~·
;.<;j~i~ function key when finished configuring information for a gateway. This returns you to
the first screen shown on this page. If you are finished for all gateways, press the
key
again.

III;'

LAN CONFIGURATION SCREENS (cont'd)
NEIGHBOR GATEWAYS (NETXPORT. HI .niName. INTERNEn FiB. 9-7. p. 9-18
Gateway Name __-YATEC

Assign a name (maximum eight characters) to reference a gateway that is on the network to which the
node belongs. Refer to Catenet Map (Figure 2) and LAN Network Map (Figure 3).
NEIGHBOR GATEWAY REACHABLE NETWORKS (H ETX PORT •NI • niName. INTERNET. gatewayn)
Fig. 9-8, p. 9-19
Neighbor Gateway IP Internet Address _ C1.92.006.00 I 003_ _
Full IP address of the gateway node. Refer to LAN Network Table (Table 2).
IP Network Address
C 192. 006. 2S0 000
_ _ ~ 192.006. 2i.t.900

W
.ill

-------------------~
The IP addresses of all reachable networks in the catenet, through the gateway node named above.
Refer to LAN Node Internet Routing Table (Table 9). We have filled in the node portion for each IP
network address with zeroes because the node portion will be ignored in this field during
configuration. A node portion still must be entered. however.
Hops
1

Refer to LAN Node Internet Routing Table (Table 9) for Hop Count. The numbers in Parentheses
corresPOnd to the numbers regarding IP network addresses.

3-61

Network Planning and Configuration

Router Node Routing Information
Tables 10 and 11 show routing informatIon for Node E on NET2 in our example.
Because NET2 is a router network, Intranet and internet routing information is needed. Intranet routing
is shown in Table 10. Using information from the NET2 network map (Figure 4) and the Router
Network Table (Table 4), we obtain the destination node names, the router link names and the IP addresses
needed for completing Table 10. Let us look at some examples from Table 10. Node E can reach Node F
(Ip address C 192.006. 2S0 004) by sending a packet over Link3. This is all the information needed in
Node E's intranet routing table for sending packets to Node F. The reason for this is that, once the packet
crosses over LINK3 and arrives at Node D, Node D will use its own intranet routing information to
continue moving the packet toward its destination node.
Notice the Entry Priority column. This column becomes important when multiple link names are
configured. When multiple link names are configured, the highest entry-priority number is the
top-priority link. For example, we see from our Router Network Map (Figure 4) that Node E can reach
Node D directly by using LINK3 and indirectly by using LINK4 and then LINKS. We decide to
configure this indirect link and list it as entry priority 30 in Table 10. Unless LINK3 should go down,
LINK4 will never be used because it has a lower priority number than LINK3. We are not required to
configure this secondary link. It is our choice. The reason we have used priority numbers 30 and SO in
Table lOis to allow for possible additions with higher or lower priority numbers; SO is the default.

3-62

Network Planning and Configuration

TABLE 10.

ROUTER NODE INTRANET ROUTING TABLE

NODE NAME:

IP ADDRESS:

C 192.006.250 003

NETWORK NAME:

NET2

DESTINATION NODE

D
D
G
G
C
f

LINK NAME

LINK3
LINK4
LINK4
LINK3
LINK3
LINK3

DESTINATION NODE'S
IP ADDRESS

002
002
005
005
001
004

ENTRY
PRIORITY

50
30
50
30
50
50

Now we proceed to Node E's Internet Routing Table (Table 11~ Remember that Node E belongs to
NET2. We see from our Router Internet Routing Table (Table S) that NET2 includes nodes C and G as
,ateway nodes. This table also shows that NET2 nodes using Node C as a gateway can reach NET t in one
hop and NET3 in two hops, and that Node G can be used to reach NET3 in one hop and NETt in two
hops. We decide to configure each gateway to reach both networks. which means that more than one
gateway is available for Node E to reach the same remote network. We are not required to configure
multiple gateways to reach the same network. It is our choice. When multiple gateways are configured.
the software determines which route to use--usually the one with the fewest hop counts.

3-63

Network Planning and Configuration
Internet routing information is not necessarily the same for all nodes on a network. Suppose we do not
want Node D in NET2 ever to communicate with any node on NET3. When completing the internet
routing table for Node D, we would not list NET3 as a destination network and we would not use Node G
as a gateway node because it would route packets to NET3.

TABLE 11.

"')

ROUTER NODE INTERNET ROUTING

NODE NAME:

IP ADDRESS:

C 192.006.250 003

NETWORK NAME:

NET2

GATEWAY NODE/IP ADDRESS

C/001

G/005

DESTINATION NETWORKS/
IP ADDRESSES

HOP

COUNT

NET1/C 192.006.001 000
NET3/C 192.006.251 000

2
1

"J
3-64

Network Planning and Configuration
ROUTER CONFIGURATION SCREENS
As an example of filling out configuration fields for a router node, we have chosen Node E on NET2,.
Only information derived from previous worksheets has been filled out.
LINK CONFIGURATION (LINKCONF) Fig. 7-1, p. 7-4
Link Name

LINK3

Assign a link name that is eight characters or fewer. The first character must be alphabetic. This
link name corresponds to one link the node belongs to. After you have been taken to all the necessary
screens for this link, Guided Configuration will bring you back to this screen to configure other links
connected to this node. Refer to Router Network Map (Figure 4). When you are finished configuring
the links for this node, press the ~~~~:!m~~;~,.~ function key.
Circle one.
ASNP LINK DATA (LINKCONF .linkname) Fig. 7-12, p. 7-27
Logical Device

The Idev number that will be configured in SYSDUMP.
OR
LAP-B LINK DATA (LINKCONF .linkname) Fig. 7-9, p. 7-19
Logical device

The Idev number that will be configured in SYSDUMP.
Local Mode (SmDTE, 6 DCE, llcHP Point to Point)
g

HP recommends that you use the default, UP Point to Point. If so, both sides of the link must be
configured as UP Point to Point.
OR
BISYNC LINK DATA (LINKCONF .linkname) Fig. 7-6, p. 7-11
Logical Device

The Idev number that will be configured in SYSDUMP.

3-65

Network Planning and Configuration
ROUTER CONFIGURATION SCREENS (eont'd)

NETWOIlK INTERFACE LINKS (NETXPORT.NI.niName.LINI<) Fig. 10-6, p. 10-17
Type

DD--Direct

Dia~

DC--Direct Connect, or SD--Shared Dial.

DIRECT CONNECT LINK CONFIGURATION (NETXPORT .NI .niName. LINK.linkname) Fig. 10-7, p.
·10-19
No fields required to configure.
OR
ROUTER DIAL LINK CONFIGURATION
10-21

(NETXPORT. NI. niName. LINK. l inkname) Fig. 10- 8, p.

No fields required to configure.
ROUTER. NETWORK INTERFACE CONFIGURATION (NETXPORT. NI • niName) Fig. 10-1, p. 10- 3
Network Hop Count

The greatest possible number of intermediate nodes between the two nodes farthest apart on the
network. See the Router Network Map (Figure 4).
Idle Device Timeout Value (Minutes)

For dial links, this is the number of minutes a device can remain inactive before shutting down. A
value of zero will disable the idle device timer for all devices on this network interface. (Enter 0 for
Direct Connect links.)
IP PROTOCOL CONFIGURATION (NETXPORT. NI. niName. PROTOCOL. IP) Fig. 10-3, p. 10-8
IP Address

C 192.006. 250

003~_

Full IP address of the node being configured. Refer to Router Network Table (Table 4).

3-66

Network Planning and Configuration

ROUTER CONFIGURATION SCREENS (c:ont'd)
Note: Mapping configuration is required for each local link the node can use to reach each remote node
on the router network. Therefore, make enough copies of this sheet before you fill in any information.
After configuring mapping information for one node, Guided Configuration will bring you back to the
first screen on this page. Repeat the process until you have completed all mapping configuration, then
press the N~~1mm: ;;~::::i~ function key.

MAPPING CONFIGURATION (NETXPORT. NI .niName.MAPPING) Fig. 10-12, p. 10-30
Router Node Name

AS81gn a name (maximum eight characters) to represent a node you wish to be able to reach from your
node. Refer to Router Node Intranet Routing Table (Table 10).
ROUTER. REACHABLE NODES (NETXPORT .NI .niName.MAPPING.tmpentry) Fig. 10-13t p. 10-32
IP Internet Address __ C..L92...Q.06:.lS0~02

FulllP address of the destination node named above. Refer to Router Node Intranet Routing Table
(Table 10).

Link Name

LINK3

Name of the link used to reach the destination node. Must match a link name that you configured on
the link configuration screen. If more than one link is required to reach the destination nodet list only
the first link to be used.
Adjacent (0)/ Non-adjacent (1) __ .-Q

If the destination node is not directly connected to the link just namedt enter 1. Otherwise, enter O.
Refer to Router Network Map (Figure 4).
Entry Priority

Important when alternate local links are configured to reach a remote node. R.efer to the Router
Node Intranet Routing Table (Table 10). If no alternate links will be configured, use the default of SO
for the priority so that you allow for possible additions with higher or lower priority numbers.
Phone Number

The phone number of the destination node is required if the destination node is directly connected to
the other end of the link and if the link is a direct dial or a shared dial link.

3-67

Network Planning and Configuration
ROUTER CONFIGURATION SCREENS (cont'd)
Note: This page contains information for one gateway. Before you proceed. make copies of this page for
additional gateways. During Guided Configuration, press the N~~~-"S~I""!~~ function key when finished
configuring information for a gateway. This returns you to the first screen shown on this page. If you
are finished for all gateways. press the ~~~l;::;~~'r~,! key again.
NEIGHBOR GATEWAYS (NETXPORT .NI .niName. INTERNEn Fig. 10-9, p. 10-24
Gateway Name

GATEG

Assign a name (maximum eight characters) to a gateway that is on the network to which the node
belongs. Refer to Catenet Map (Figure 2) and Router Network Map (Figure 4).
NEIGHBOR GATEWAY REACHABLE NETWORKS (NETXPORT .NI .niName. INTERNET .gatellJayn)
Fig. 10-10. p. 10-25
Neighbor Gateway IP Internet Address __~.J 91:.006. 25..Q..OOJ.._ _
Full IP address of the gateway node. Refer to Router Network Table (Table 4).
IP Network Address

_ _ _~191:.006. 001.. 000

_____~191:.006.2UOOO

-------------------~

------------------~
The IP addresses of all reachable networks in the catenet, through the gateway node named above.
Refer to Router Node Internet Routing Table (Table 11). We have filled in the node portion for each
IP network address with zeroes because the node portion will be ignored in this field during
configuration. A node portion still must be entered. however.
Hops
2

-------~-----------~
------------------~
(4)

Refer to Router Node Internet Routing Table (Table 11) for Hop Count. The numbers in parentheses
correspond to the numbers regarding IP network addresses.

3-68

Network Planning and Configuration
Gateway Half Infonnation for Node Worksheets

As an example of the information needed for every gateway half in the catenet, look at Table 12. This
table shows internet routing information for Node G, which is a gateway half on NET2. Referring to our
Gateway Half Map (Figure 6) and our Gateway-Half Network Interface Table (Table 8), we indicate in
Table 12 that Node H is a gateway half that is connected to Node G. We also see that we have named the
gateway-half link LINKRLI. We see from our Catenet Map that, from Node G, we can reach NETI in
one hop. The reason NET3 is not included in Table 12 is that Node G can reach NET3 in zero hops. This
is because Node G is a partner gateway half with Node H, and Node H is a member of NET3. Therefore,
Node G is considered to be directly connected to NET 3 and does not require a hop to reach NET3.

TABLE 12.

GATEWAY-HALf NODE INTERNET ROUTING TABLE

NAME Of GATEWAY-HALf NODE:

IP ADDRESS:

192.006.250 005

NETWORK NAME:

NET2

CONNECTED GATEWAY-HALf NODE/
IP ADDRESS

H/192.006.251 001

GATEWAY-HALf
LINK NAME

DESTINATION
NETWORKS/
IP ADDRESSES

HOP
COUNT

LINKRL1

NET1/
C 192.006.001 000

3-69

Network Planning and Configuration
GATEWAY-HALF CONFIGURATION SCREENS
As an example of filling out configuration fields for a gateway half. we have
Only informatioD derived from previous worksheets has been completed.

~hosen

Node G on

NET~.

GLOBAL TRANSPORT CONFIGURATION (NETXPORT •GLOBAL) Fig. 8-4, p. 8-7
Home Network Name

~ET2

Enter the name of a network the node belongs to, which is the same as the corresponding NI name.
Refer to the appropriate maps. If the node belongs to more than one network, the home network
should be the one that will allow the greatest number of destination networks a short return route to
the node.
LINK CONFIGURATION (LINKCONF) Fig. 7-1, p. 7-4
Link Name

!.INKRL 1

Assign a link name that is eight alphanumeric characters or fewer; the first character must be
alphabetic. Refer to the Gateway-Half Link Map (Figure 6).

ASNP LINK DATA (LINKCONF .linkname) Fig. 7-12, p. 7-27
Logical Device

The Idev number that will be configured in SYSDUMP.
OR
LAP-B LINK DATA (LINKCONF .linkname) Fig. 7-9, p. 7-19
Logical Device

The ldev number that will be configured in SYSOUMP.
Local Mode (S-OTE, 6a DCE, 11 =HP Point to Point)

HP recommends that you use the default, HP Point to Point. If so, both sides of the link must be
configured as HP Point to Point.

3-70

Network Planning and Configuration

GATEWAY-HALF CONFIGURAnON SCREENS (cont'd)
BISYNC LINK DATA (LINKCOHF .linkname) Fig_ 7-6, p. 7-11
Logical Device

The Idev number that will be configured in SYSDUMP.

NETWORK INTERFACE LINKS (NETXPORT. NI • niName. LI Nt<) Fig. 11-6, p. 11-16
Type
DD--Direct Dial, or DC--Direct Connect

GATEWAY-HALF DIAL LINK CONFIGURATION (NETXPORT.NI.niName.lINK.linlcnams) Fi,.
11- 8, p. 11 -1 9
Gateway Phone

The phone number of the remote gateway-half node.
Security String _ _,
Security String of the remote gateway-half node.

DIRECT CONNECT CONFIGURATION (NETXPORT. HI .niName. LINK.linkname) Fig. 11-7, p. 11-17
No fields required to configure.
GATEWAY-HALF NETWORK INTERFACE CONFIGURATION (NETXPORT. NI • niName) Fig. 11-1, p.

11-3
Idle Device Timeout Value (Minutes)

IP PROTOCOL CONFIGURAnON (NETXPORT •NI • niName. PROTOCOL. I P) Fig. 11- 3, p. 11-7
IP Address

C 192.006.251 001

Full IP address of the partner gateway-half node (the node connected to the aateway half being
configured). Refer to Gateway-Half Network Interface Table (Table 8).

3-71

Network Planning and Configuration
GATEWAY-HALF CONFIGURATION SCREENS (cont'd)

NEIGHBOR GATEWAYS (NETXPORT. NI.niName.INTERNET) Fig. 11-9. p. 11-23
GATEH

oa~wayName

Assign a name (maximum eight characten) to represent the partner pteway half whose address was
just listed in the previous field. Refer to the Catenet Map (Figure 2) and Gateway-Half Link Map
(Figure 6).
NEIGHBOR GATEWAY REACHABLE NETWORKS (NETXPORT •NI • niName. INTERNET. gatellJa!Jn)
Fig. 11-10. p. 11-24
Neighbor oa~way IP Internet Address

C 192.006.251 001

Fun IP address of the gateway node named above; same as the address in the IP Address field. listed
previously.
IP Network Address
_ _ _ _ _ C 192.006.001

___--ill
{2)

--------------------~
,--~
The IP addresses of all reachable networks in the catenet. through the gateway node named above.
Refer to Gateway-Half Node Internet Routing Table (Table 12~ We have filled in the node portion
for each IP network address with zeroes because the node portion will be ignored in this field during
configuration. A node portion still must be entered, however.
Hops
1

ill

rn
rn
~

Refer to Gateway-Half Node Internet Routing Table (Table 12) for Hop Count. The numbers in
parentheses COrresPOnd to the numbers regarding IP network addresses.

3-72

_S_Y_S_T_E_M_C_O_N_F_IG_U_R_AT_I_O_N

System configuration is the means of defining to MPE all of the peripheral devices attached to the
HP 3000 for the input or output of data, or I/O, as well as defining the system parameters required for
operation. Each device is defined in terms of its associated software, or driver, which controls the device
operation and manages the interface with MPE. Incomin, data communications connections also require
pseudo-devices, called virtual terminals, which consist ot software to simulate the functionality of
terminals. Hence, for NS3000/V and associated links, the system configuration consists of configuring the
driven associated with each device and enough virtual terminals to handle incoming data communications
needs.

System configuration is accomplished by using the System Configurator (or SYSDUMP) dialogue. which
you initiate with the SYSDUMP command. The information provided here is for situations where you need
to change or add to that configuration because of changing circumstances at your installation. This
section, therefore, begins with a detailed explanation of I/O configuration for the drivers and virtual
terminals. Recommendations for the modification of system parameters are also provided. This
information is followed by the SYSDUMP dialogue and the specific responses required to configure the
driven and virtual terminals needed for NS3000/V and associated links. The subsections are:
• System Configuration
• I/O Configuration
• Recommendations for System Parameters
• Virtual Terminal Configuration Dialogue
• LANIC Configuration Dialogue
• INP Configuration Dialogue
• Device Driver (IOINPO)
• Communications Drivers (IODSO and 10DSX)
• ATP (ASNP) Configuration Dialogue
• Completing the SYSDUMP Dialogue
• Configuration Examples
If you are already familar with I/O configuration, turn to the specific dialogue for the device or virtual
terminal you need to configure. For more information, or if you are making any other changes to the
system configuration, refer to the MPE JI System Operation and Resource Management Reference Manual
or the Fundamental Data Communications Handbook.

4-1

System Configuration

SYSTEM CONFIGURATION
The system configuration of NS3000/V and associated links involves configuring the following:
• Local Area Network Interface Controller (LANIC). The LANIC is the MPE-V communications
device used for the IEEE 802. 3 links. You must configure the device drivert 10LANO.
• Intelligent Network Processor (I NP). The INP is the communications device used for NS
Point-to-Point 3000/V Links, and DS-Compatible Links. You must configure the device driver
(IOINPO) for each such link your node will have. For OS-Compatible links, you must also
configure the communications drivers: IOOSO for the Point-to-Point links or IOOSX for the X.2S
and Satellite links.
• Advanced Terminal Processor (ATP). The ATP is a communications device that provides data
transfer between HP 30008, or between personal computers and an HP 3000, over the
Asynchronous SERIAL Network Link. It consists of a System Interface Board (SIB) and at least
one Asynchronous Interface Board (AlB). You must configure the device driver (HIOASNPO).
• Virtual Terminals. These pseudo devices are configured in pools. For NS links, the pool of
virtual terminals is shared by all NS communications devices. You must configure as many
IOVTERMO virtual terminals as needed for concurrent access over all NS links combined.
For each DS-Compatible Point-to-Point Link, you must configure a separate pool of IOOSTRMO
virtual terminals, back-referenced to the INP for that link. For each DS-Compatible X. 2S and
Satellite Link. a pool of IODSTRMX virtual terminals must be configured, again with each virtual
terminal back-referenced to the INP corresponding to the specific link.
Note that whereas the pool of virtual terminals for NS links is shared across all NS links, virtual
terminals configured for OS links are dedicated to a specific link corresponding to the
back-referenced INP.
• System Table Changes.
Changes may be required for NS3000/V and associated links.
Recommendations are provided that you can use to check your existing configuration.
The drivers and virtual terminals are configured into MPE using the SYSDUMP dialogue. You initiate
the SYSDUMP dialogue by issuing the SYSDUMP command. which requires a user with OP capability. As
the questions or prompts appear on your screen, enter the appropriate replies for the desired system
configuration. In all responses, Y or N can be used for YES or NO. A (RETURN) indicates NO or keeps the
existing value. Explanations for each of the I/O configuration' prompts and recommendations on
modifying the system tables are provided below. If you are familiar with this information, skip ahead to
the specific dialogue you need.
For any data communications subsystem to function, a compatible version of Communications Systems
software (CS/3000) must be present on the system; it' is presumed in this configuration description that
CS/3000 is installed. Refer to Volume lit Section 2 of this manual for instructions on how to verify that
the installed version of CS/3000 is the correct version needed for the· operation of NS3000/V and
associated links.

4-2

System Configuration

I/O Configuration
When you enter SYSDUMP you are asked a series of questlons. Your answers provide the information
required by MPE for the I/O configuration of each device as well as general system configuration.
The SYSDUMP dialogue begins as listed below. Prompts are showr on the left and recommended
responses are underlined and/or explained on the right.

:SYSDUMP
ANY CHANGES?

YES

SYSTEM ID = HP320331J.uu.ff?

[RETURN)

MEMORY SIZE= nnnn (MIN=nnn,
MAX=nnnn)?

[RETURN) (unless additional main memory has been added for the
products you are configuring).

I/O CONFIGURATION CHANGES?

YES

LIST I/O DEVICES?

Enter YES to print a listing of the current I/O configuration. Enter
NO or [RETURN) to continue. Refer to the example listing at the end
of the section.

LIST CS DEVICES?

Enter YES to print a listing of all the CS devices currently
configured. Enter NO or [RETURN) to continue. Refer to the example
listing at the end of the sectIon.

LIST DEVICE DEfAULTS?

(RETURN)

HIGHEST DRT= nnn (MIN=mm,
MAX=ppp)?

Check to see if the value listed here as nnn is large enough to
include all the data communications devices you are going to
configure. INPs) LANICs) and ATP devices all use DRT numbers.
Refer to their respective dialogue listings (later in this section) for
more information.

LOGICAL DEVICE I?

To specify a device to be added or removed, enter the logical device
number (ldev) of that device.
Entering 0 or (RE'TURN) ends the I/O Configuration Changes
procedure;the dialogue skips to the next set of prompts. Refer to
"Completing the SYSDUMP Dialoguell (later in this section) for the
continuation of questions after all devices have been configured.

The set of questions beginning with the LOGICAL DEVICE I? prompt is the key section of SYSDUMP
dialogue for data communications devices. The dialogue for each type of device or driver is explained
step-by-step later in this section.
Figure 4-i shows an overview of the components of the Network Links that are used for I/O and
therefore must be defined to MPE.
Each communications device requires a device driver t(~ .llUi uage the device operation. Device driver
names are as follows: IOLANO for'the LANIC; IOINPO for the INP; and HIOASNPO for the ATP.

4-3

System Configuration
For NS links, the device driver also handles the link-level protocol for the particular device associated
with each link; no additional software driver is required. For the DS-Compatible links, however, the INP
requires a separate communications driver, which must be Individually configured and back-referenced to
the Idev number of the INP. The communications driver IOOSO handles the Bisync (BSC) protocol used by
the DS-Compatible Point-to-Point Modem and Hardwired Links, while IODSX handles the LAP-B
protocol used by the X.25 and Satellite links. The proper communications driver is downloaded to the
INP at the time the OS-Compatible link is activated (that is, when you issue the : OSCONTROL OPEN
command).

NOTE

A single INP can be used by two link products, although not concurrently.
The method used to configure the same INP to be used by two or more link
products (or two references in the same product) is essentially the same.
Any constraints are detailed under IIINP Configuration Dialogue" in this
section. An example of an INP used by two NS links is described under
"Configuration Examples" later in this section.

Virtual terminals are also shown in Figure 4-1. The virtual terminal driver used for communication over
every NS link is IOVTERMO. If you have any OS-Compatible Links installed, the appropriate virtual
terminal driver is IODSTRMO for Point-to-Point and IOOSTRMX for X. 25.
There are three things to consider for virtual terminals. First, virtual terminals are configured much the
same as actual terminals, although many of the parameters which apply to actual terminals are not used
for virtual terminals. Second, when configuring virtual terminals, consider the maximum number of
terminals supported by your node. Each virtual terminal is added to the total number of terminals
already configured on the system. (Information is available from your HP representative as to the
maximum number supported on your system.) Third, the number of virtual terminals you configure
depends on the number of concurrent in-coming data communications requests your node normally
receives. This means that you must configure a maximum number of IOVTERMO virtual terminals for
concurrent access over all NS links on your node, as well as a maximum number of IOOSTRMO and/or
IODSTRMX virtual terminals for any respective OS-Compatible links installed.

4-4

System Configuration

NS Links

I/O

Virtual Terminals
(IOVTERMO)
M

P
E

I/O

OS Compatible Links

.-.

Virtual Terminals
(IODSTRMO or IODSTRMX)

...
.-.

Device Driver
(IOLANO. IOINPO.
HIOASNPO)

Communications Driver
(10050 or IOOSX)
Device Driver
(IOINPO)

~mmunlcauon.
(IMP)

Communications Device
(LAMIe. IMP. ATP)

Device

Figure 4-1. I/O Configuration for the Network Links

When configuring each of the driven and virtual terminals. you must provide the following information:
• LOGICAL DEVICE NUMBER. This is the value by which MPE recognizes a particular device.
You need to assign a unique logical device number, or ldev, for each device and psuedo-device
you configure. The choice of ldev number is arbitrary; however. many installations follow the
numbering convention that Idev numbers 1-20 are reserved for system use. with all other
numben assigned in sequence as they are needed.
NOTE

If the same INP card will be used by two different link products, it is not
necessary to configure a separate IOINPO device driver for each link.
When a NETCONTROL START or DSCONTROL OPEN command is attempted
on a device already in use. a "DEVICE UNAVAILABLE" message will be
sent to the console. Refer to Volume II. Section 1 of this manual for the
proper command sequence in stopping and starting shared devices.

• DEVICE REFERENCE TABLE (DRT) ENTRY NUMBER. The DRT number is only used for the
device driver. You do not enter the DRT number when configuring virtual terminals or
communications drivers. Instead, you enter the ldevof the device driver preceded by a number
sign ('). This is called "back-referencinglt and ind icates to MPE which device the virtual terminal
or communications driver will use.

4-5

System Configuration
NOTE

For NS links, back-reference the IOVTERMO virtual terminals to the
console; this allows the pool of IOVTERMO virtual terminals to be shared
across all NS links. IODSTRMO and IODSTRMX virtual terminals must be
back-referenced to a specific INP device driver configured as a DS link.

The DRT number is supplied by your CE and is derived from the actual hardware address of the
device. During installation, the CE sets switches and jumpers on the device to correspond to that
hardware address. The formula used for calculating the DRT number is included in the
configuration dialogues later in this section.
• DEVICE NAME/DEFAULTS. Device defaults are not defined for the INP or LANlC; these
prompts are not used. They are presented in the I/O configuration because many of the devices
configured with MPE can be automatically configured. This means that the device configuration
is created for you, without your actually having to type in values to answer some SYSDUMP
dialogue questions.
• UNIT NUMBERS. Enter zero when configuring any of the driven except the ATP driver
(HIOASNPO~ unit numben are not used for the LANIC or INP communications devices. This is
because the unit number is a hardware-dependent characteristic determined by the physical
connection of a device to its controller. If there is only one device per controller, as is the case
with communications devices, then a unit number of 0 is assigned.
For the ATP driver (HIOASNPO), enter a number between 0 and 95. The exact number to enter
will depend on how many SIBs and AIBs are installed. Refer to the "ATP Configuration
Dialogue" later in this section for details.
• SOFI'WARE CHANNEL NUMBER. Enter zero when configuring any of the drivers. The
channel number is used for other products or to deal with special configuration situations; it does
not apply to NS3000/V and associated links.
• TYPE/SUBTYPE. Each device is assigned a device type and a subtype. In general, these numben
indicate the features the device supports and how MPE can access it. Table 4-1 describes the
type and subtype for each device required by NS3000/V and associated links. The SYSDUMP
dialogue may have additional prompts, depending on the type or subtype entered. The additional
information requested for each type/subtype is described later in this section.
• DRIVER NAME. The driver is the software that serves as an interface between the device and
MPE. Table 4-2 shows the names of the drivers used by each of the Network Links available
with NS3000/V.

4-6

System Configuration
TABJ.E 4-1. TYPES 4ND SUBT"PES
Driver

Type

Subtype

Description

Virtual Terminals
(IOVTERMO. IODSTRMO.
IODSTRMX)

Virtual terminal. Also used for directly
connected terminals with speed-sensing.

Virtual Terminal
(lODSTRMO)

Allows use of block mode when
connecting to a DS/ 1OOO-IV node.
Checked by VPLUS/3000.

LANIC device driver
(lOLANO)

Indicates a LAN connection -- no CS
configuration required.

INP device driver
(IOINPO)

Indicates communication is with modems
used over a switched (dial-up) line.

Indicates a non-switched (leased or
digital) line with a modem cable or a
direct connection with a modem
eliminator cable.

Indicates a hardwired line, synchronous
transmission.

Indicates a hardwired line, asynchronous
transmission.

Indicates communication is with modems
used over a switched (dial-up) or
non-switched (leased or digital) line with
a modem cable. It can also be a direct
connection using a modem cable.

Indicates communication is with a CCITI'
standard modem.

Indicates no data compression.

Indicates data compression is enabled.

ATP (ASNP) device driver
(HIOASNPO)

Communications driven
(lODSO and IODSX)

~
.....

4-7

System Configuration

TABLE 4-2. DRIVERS REQUIRED FOR EACH NETWORK LINK

DRIVERS
Device
Driver

Virtual
Terminal

IOlANO

IOVTERMO

none

HIOASNPO

IOVTERMO

none

Polnt-to-Polnt
(NS/3000)

IOINPO

IOVTERMO

none

Point-to-Polnt
(05/3000)

IOINPO

IODSTRMO

IOOSO

X.25 link
(05/3000)

IOINPO

IODSTRMX

IODSX

NETWORK lINKS
ThicklAN
HP StarLAN
HP ThlnlAN
HP Serial Network

Communications
Driver

NOTE

The OS-Compatible X.2S Link can be used with a Packet
Assembler/Disassembler (PAD). If you are using the X.2S Link with a
PSN-supplied PAD or an HP 2334 Cluster Controller PAD, there are two
virtual terminal drivers used instead of IODSTRMX. These are IOPADO
for PAD to terminal connections and IOPADl for PAD to printer
connections. Refer to the X.2S Link lor the HP 3000 Relerence Manual
for information on using the X. 2S Link with a PAD.
• DEVICE CLASSES. The IOVTERMO virtual terminal driver uses the device class designator
VTERM to define a pool of virtual terminals available for use over NS3000/V links. Because of
this, you must enter VTERM as the device class for each IOVTERMO virtual terminal that you
configure. Additional device class names are allowed.
The device driven for the NS3000/V Links do not have any special considerations as to the
device class. Any device class designator configured for the device driven IOLANO, IOINPO, or
HlOASNPO can be used in commands or intrinsics which allow device class designaton.
For the DS-Compatible Links, you can configure the device class for the device driver IOINPO,
the IODSTRMO and IODSTRMX virtual terminals, and the communications driver IODSO. These
configured device class designaton are used in certain commands and intrinsics, including
DSCONTROL and DSlINE, when any member of a group of devices can be referenced.
The exception is the IODSX communications driver used by the DS-Compatible X.2S and
Satellite Links. It is recommended that device class not be configured and that usen or
proarammen use X.2S nodenames whenever a dsde&1ice parameter is required in a command or

4-8

}

System Configuration
intrinsic. If you do configure device class designators for IODSX, do not use X. 25 nodenomes as
the device class designators. The X. 25 nodenames referred to are those defined in the Remote
Node (RN) Table as part of the network configuration of the OS-Compatible X.25 and Satellite
Links. The RN Table is configured with the NETCONF utility and stored in a TurboIMAGE
data base. To find out what X.25 nodenames are configured on your node, issue the following
command:

:RUN NETCONF.PUB.SYS
>LIST
A listing of all configured X. 25 nodenames is displayed. Refer to the X.25 Unle for tile HP 3000
Reference Manual for information on DS/3000 X. 25 and Satellite network configuration.

Type 16, SUbtype 0, 8 - VIrtual Terminals
Additional information required for each virtual terminal for either subtype:
• TERMINAL TYPE OR. DESCR.IPTOR FILE NAME. Enter zero; virtual terminals do not use
terminal types. The terminal type, or tenntyPe, refers to the HP assigned numbers used to
classify actual terminals based on their characteristics. The descriptor filename is used to specify
a user-created termtype, as described in the Workstation Configurator Reference Mdlaual.
• SPEED IN CHARACTERS PER SECOND. Enter zero; virtual terminals do not use this item.
The SPeed refers to the fact that for actual terminals you must enter the transmission speed.
• RECORD WIDTH. Enter 40 for virtual terminals. This is a decimal value which specifies words,
not bytes. While virtual terminals are not bound by the physical constraints of CRTs, many
applications do not distinguish between virtual and actual terminals and expect data in the
standard terminal record width of 40 words (80 characters).
• OUTPUT DEVICE. Enter the value used for the logical device number. You must specify a
corresponding output device if a device is used to initiate jobs or sessions.
• MODE. Each device may have five modes: job/session accepting, data accepting, interactive,
duplicative, and spooled. Configure the virtual terminal in accordance with its intended use,
normally: job/session - I§; data - NO; interactive - Y§ duplicative - YES; spooled - NO.
• AUTO REPLY. Press (RETURNI. This is not used for virtual terminals. It enables automatic
replies to any tape requests.

Type 17, SUbtype 9 - LANIC Driver
No further information (in addition to Idev, tYP'J subtype, and driver name) is required in SYSDUMP.
R.efer to Network Configuration in Section 5.

4-9

System Configuration

Type 17, &lbtype 0, 1, 3 - INP DrIver
Additional information required for the INP for all three subtypes:
• RECEIVE TIME OUT. For NS Point-to-Point Links, enter (RETURN); the default value will be
overridden by NMMGR. For OS-Compatible Point-to-Point Links, use the default value of 20
byenteringlRETURNI. This means that the INP waits 20 seconds for data to be received from the
remote. following a transmission.
Do not enter O.
This timeout is not used for the
DS-Compatible X. 25 and Satellite Links.

• LOCAL TIME OUT. For NS Point-to-Point Links, enter (RETURN); the default value will be
overridden by NMMGR. For the OS-Compatible Links, use the default of 60 seconds. This
timeout refers to the length of time the INP allows between completion of one I/O request and
the initiation of the next one. This is used by the INP to determine if the HP 3000 is responding;
if not. the INP will close the link gracefully. The range is 5-900; entering 0 disables the timer.
• CONNECT TIME OUT. For NS Point-to-Point 3000/V links enter (RETURN), and the default wiD
be overridden by NMMGR. For the OS-Compatible Links you should enter 300 for Subtype 0;
enter 120 for Subtype 1 and 3. This means that the local node waits the configured number of
IeCOnda after one attempt to make a physical connection to a remote node. It applies to the
manipulation of the control lines across the OTE/DeE interface rather than a protocol exchange.
Do not use the default of 900; the range is 60-900; entering 0 disables the timer. Under most
conditions. you do not need to adjust these timeout values. However. if the timeout is not
sufficient. CS/3000 displays an error.
• TRANSMISSION MODE. For NS Point-to-Point Links, enter zero; any value entered here will
be overridden by NMMGR. For DS-Compatible Links, interpret this question as asking you:

lila the INP a full-duplex (0) or half-duplex device (1)1"
Since the INP is full-duplex, capable of transmitting and receiving simultaneously. the usual
response is 0 for full-duplex. However, if you are connecting the INP to a half-duplex modem or
to a OS/3000 node using the Synchronous Single Line Controller (SSLC) communications device
you need to enter 1 for half-duplex.
Configure the INP to operate in full duplex if the communications link provides two
simultaneous main channels, one for transmit and one for receive. This is usually the case in one
of the following:
• A leased line with four-wire, point-to-point installation.
• A dial network with two lines (four-wire equivalent).

• A dial network with Wide Band Service.
• Any direct connect cable between two INPs.
• A dial network or a 2-wire leased line with a special 2-wire full duplex modem. Typically
these operate at 1200 bps (bits Per second).
Configure the communications interface to operate in half duplex if your communications link
does not provide two simultaneous main channels, one for transmit and one for receive. This is
usually the case in the following:

4-10

System Configuration

• A dial network with a half duplex type modem that uses a single line. Usually this is a
2400 or 4800 bps modem.
• A connection to a DS/3000 node that is an HP 3000 Series II or III using a SSLC
communications device.
Your response must agree with the remote system·s configuration and with the characteristics of
the communications line.
• SPEED CHANGEABLE/TRANSMISSION SPEED. The speed of the INP is changeable. For NS
links, you must enter YES to the SPEED CHANGEABLE? prompt. Any value you enter for
TRANSMISSION SPEED will be overridden by NMMGR. (Refer to Section 7 for details.)
For DS-Compatible links. the value you enter is determined by whether the INP is used for a
hardwired or modem connection. and the characteristics of the communications line. If you are
configuring an INP connection to a modem (Subtype 0 or 1). first determine if the modem has
internal clocking signals. If so. the transmission speed is ignored. although you need to enter some
value. This allows modems of different speeds to be used without reconfiguration. If the modem
does not provide internal clocking SIgnals you need to determine the correct speed for the modem.
Enter that value.
If you are configuring an INP hardwired connection (Subtype 3) you need to specify a line speed
appropriate for the connection. The speed you specify becomes the default For Subtype 3 you
can also specify that the speed is changeable. which is recommended. This allows the Operator to
override the default by including the speed parameter in the DSCONTROL command. (Refer to
Volume II. Section 1 of this manual for details on the DSCONTROL command.)
Note that the value you enter for transmission speed is in bytes. not bits. per second. For
example. 4800 bits/second must be entered as 600 bytes/second. The possible values are 150,
300. 600. 900, 1200. 2400. 3600. 4800, 7000. Your response must agree with the configuration
of the remote node and with the characteristics of the communications line.
• BUFFER SIZE.
NMMGR.

For NS links, enter 1024; any value entered here will be overridden by

For DS-Compatible Point-to-Point Links, the buffer size must be between 304 and 1024 words.
For best performance. the maximum size of 1024 is recommended. The size of this buffer
determines the maximum amount of data that can be sent or received in a single physical
transmission over the line. Note that although large buffer sizes increase transmission efficiency,
they also use up memory space. (In cases where noisy phone lines contribute to high transmission
error rates, a smaller buffer size may increase efficiency by reducing the error rate.) Match
buffer sizes for sender and receiver whenever possible, since the effective buffer size that can be
utilized is the smaller of the two.
The configured buffer size can be overridden by the first user to issue a DSLINE command (with
the lINEBUF'=buffersize parameter) after the line is initialized. Once overridden. the buffer
size cannot be changed again until the first user (and any subsequent usen) has closed the
connection. Refer to the NS3000/Y User/Programmer Reference Mamud for information on
DSLINE.
For DS-Compatible X. 25 and Satellite Links, any value entered here is ignored. The buffer size
used for the line is calculated depending on the packet size defined in the network configuration
(using the NETCONF utility). Refer to the X. 25 LInk for the H P 3000 Reference MGIUUJI for
information on X. 25 and satellite network configuration.

4-11

System Configuration
• DRIVER CHANGES. Press

lRETURNI.

• DRIVER OmONS. Enter zero.
For Subtype 1, which' means the connection is over a nonswitched line with modem cable or modem
eliminator cable, the following additional information is needed:
• DUAL/HALF SPEED. This is to establish if the modem used for this connection operates at
lingle or dual speed. Many European modems operate with dual speeds. If you are using a dual
speed modem, you are also asked if the modem is to operate at half or full speed. Answer in
accordance with the features available on the modem used for the connection.
For Subtype 0. which means the connection is over modems used with a switched line. the followinl
additional information is needed:
• DIAL FACILITY. The INP20B has auto-dial capability. If you are using this feature, you enter
the Idev of the INP. Otherwise, answer whether the modem requires manual dial-up or not.
• ANSWER FACILITY/AUTOMATIC ANSWER. This refers to modems that can answer incoming
calls, manually or automatically. Answer in accordance with the features available on the
modem used for the connection.
• PHONE-LIST/PHONE NUMBER. If you answer that you want to list a phone number, you can
supply one number, usually a frequently dialed number. to be used as the default when the line is
opened. If you configured auto-dial, you must enter a phone number. The phone number is
entered as a string of numbers and hyphens, up to a maximum of 30 characters. The followinl
special characters may also be part of the phone number:

Separator used for automatic call units that have a second dial tone detect.

E Optional end-of-number indicator.

D One-second delay.

Used for European modems and automatic call units that require

built-in delays.
, Defined by the local telephone system.
• Defined by the local telephone system.
• LOCAL/REMOTE ID SEQUENCE. For NS Point-to-Point Links, enter [RETURN) because this
information is provided through NMMGR in the form of "security strings. II Local/remote ID
sequences confilured for DS point-to-point links are ignored by NMMGR. ID sequences are not
Local/remote ID sequences are used with DS
used for DS X.2S and satellite Links.
point-to-point links as part of the DSLI HE command. For more information, see the DS manuals
listed in the Preface of this manual.
This additional information for Subtype 0 is necessary due to the complexity of establishing a connection
UIiDa a dial-up modem. The typical sequence of steps is as follows:

1. The Uler issues a DSLINE command. Refer to the NS3000/V User/Programmer Reference
MGIJIUIl for information on this command.

4-12

System Configuration
2. The command contains a phone number (PHNUM),
system configuration is used.

If not, the phone number supplied during

3. Without auto-dial, the phone number is displayed at the console; the Operator dials the number
at the modem and then enters YES at the console The keyboard of the user terminal is disabled
until the Operator responds. With auto-dial, meaning the INP or the modem has auto-dial and
the line is configured for auto-dial, the number is dialed immediately.
Notice that the configured phone numbers are used as defaults; usen mayor may not supply the required
numben as parameten on the command used to request the connection. It is strongly recommended that
you configure default phone numbers for any dial-Up lines installed on your node. If neither defaults nor
supplied values are available then the remote connection cannot be made successfully. This means that
the INP and the terminal are tied up during the length of time configured for the connect timeout.

Type 41. Subtype O. 1 -

Communications Drivers

Additional information required for the communications drivers for both subtypes:
• RECORD WIDTH. Enter; 128 for communications drivers. This is a decimal value which must
be SPecified in words. not bytes.
• OUTPUT DEVICE.

Enter~.

• MODE. Each device may have five modes: job/session accepting, data accepting, interactive,
duplicative, and spooled. Configure the communications driver in accordance with its intended
use, normally: job/session - YES; data - NO; interactive - YES; duplicative - X§; spooled NO.
• AUTO REPLY. Press (RETURNI. This is not used for communications drivers.
automatic replies to any tape requests.

It enables

The configured subtype establishes the default data compression for the line, where subtype 0 is no
compression and subtype I is compression enabled. Compression is allowed only if both nodes are capable
of performing compression. The default established during configuration can be overridden with the
DSCONTROL used to open the line by specifYing COMP or NOCOMP, as described in Section 1, Commands, in
Volume II of this manual set.
On a non-exclusive line, a user can specify data compression without affecting any other usen of that
line. This is done by specifying COMP or NOCOMP on the DSLINE command, as described in the NS3000/Y
User/Programmer Reference Manual. Note that the default for DSLINE is NOCOMP. If you configure the
line for data compression you need to notify users to specify COMPo Otherwise, the configured default is
always overridden by the default on the DSLINE command.

Compression can increase throughput by reducing redundancy in the data, which results in a reduction in
the number of characters being transmitted over the link. The compression technique compresses any
occurrence of three or more consecutive characters. ObViously, the savings depends on the amount of
redundancy in the files, which may vary significantly. Source or listing files may be compressed by as
much as 75 percent, but a savings of 2S percent is more usual. The savings also depends on the system
load. Using compression and decompression increases the ~ystem overhead at both ends of the link.
The decision on whether to use compression or not depends on the communications link data rate, system
load, and the amount of redundancy in the data being transmitted. Often a test of relative throughput
with normal system load and typical data provides an indication of the benefits of using compression.

4-13

System Configuration

Type 42. Subtype O. 1, 2 -

ATP Devices

Additional information is required for each device used by the ASNP drivel:
NOTE

These values will be overwritten by information in the configuration file as
specified through NMMGR.

• RECORD WIDTH. Enter 40 for ATP devices. This is a decimal

valu~

expressed in words, not

bytes.

• OUTPUT DEVICE. Enter

• MODE. Each device may have five modes: job/session accepting, data accepting, interactive,
duplicative, and spooled. Press [RETURN) for each of the five modes.
• AUTO REPLY. Press (RETURNI. This is not used for ATP devices. It enables automatic replies to
tape requests.
The configured subtype (0, I, or 2) indicates the type of line and modem being used on the ports associated
with this device driver.
NOTE

For the Asynchronous SERIAL Network Link, you must also configure as
many virtual terminals (IOVTERMO) as will access the HP 3000
concurrently over this link. These are in addition to those virtual terminals
Remember to back-reference
configured for any other NS links.
IOVTERMO virtual terminals to the console.

4-14

System Configuration

Recommendations for System Parameters
Before configuring and activating NS3000/V services and links, check the limits on your system tables.
Since DS/3000 is included with NS3000/V,
whether you already have DS/3000 on the
provided with NS3000/V link products are
resources depend on whether you already have

the additional table resources for NS3000/V depend on
system. Similarly, since the node management services
also provided with the SNA Link, the additional table
the SNA Link on the system.

The following guidelines indicate the additional entries needed in the Code Segment Table (CST), Data
Segment Table CDST), Process Control Block Table (PCB), and I/O Queue Table (IOQ). An explanation of
the items shown in italics follows the list of guidelines. Refer to "Configuration Examples" later in this
section for some practical examples.
One or more NS3000/V Link Products:

CST:

DST:

10 + (1.2 • NumConn)

PCB:

100:

If you do not already have products using Node Management Servicett

CST:
DST:
PCB:

100:

7
14 + (12 • Numtinks)
4 + NumLinks

For each Network Interface configured:

CST:
DST:
PCB:

IOQ:

0
NumBuff/40
0
0

For each concurrently active NS link device:

CST:
DST:

0
0

PCB:

100:

2 + NumReads + Nutrllrites

NS3000/V Services or the OfficeShare family of products (Asynehronous SERIAL Network Link.
ThinLAN/3000 Link. or StarLAN/3000 Link):

CST:

DST:

7 + (3 • NunConn)
1 + NunConn
0

PCB:

IOQ:

4-15

System Configuration

If you do not already have D5/3000:

CST:
DST:
PCB:

IOQ:

10
2 + (3 • NumLinks) + Num~ds&Tenms + NumSess + NumoSlines

NumLinlc.s
5 + NumSess

Note that in the case of DST and PCB entries, additional entries are used for active traces and for active

uen of node management services (NMMGR, NMDUMP, NMMAINT, NMMGRVER).

NOTE
The number of PCB entries should never be less than (NunConn/2) + 4.
An explanation of the items shown above in italics follows:

•

N~onn is the number of TCP connections. The maximum number of TCP connections is
through
NMMGR
on
the
Network
Transport
TCP
screen
configured
(~imum Number of Connections). You may want to use the maximum value for Nu~onn
when calculating table entries in order to ensure that sufficient resources will always be
available. The UP default value for the maximum number of connections is 128.

• NumBuffis the number of buffers used by each Network Interface.
For the LOOPBACK NI, NumBuff is simply the value configured in the Loopback Network
Interface data screen (Number of Buffers). The NMMGR default value is 256.
For the 802. 3. Router and Gateway NIs, NumBu!! is calculated by the addition of the two buffer
values in the Network Interface data screens (Number of Inbound Buffers and Number of
Outbound Buffers) added to the Number of Buffers in the LINKCONF data screen. The
NMMGR default for inbound buffers and outbound buffers is 256 for the 802. 3, Router and
Gateway NIB.
The default number of buffers for each link is as follows:

Link
802.3

LAP-B
BSC
ASNP

Numbe r

of Buffers
42
12
12
20

For an 802. 3 link, only one link is configured. Using the defaults, the Numbuf! would be:

Number of Inbound Buffers + Number of Outbound Buffers + Number of
Buffers (for the 802.3 link)
256 + 256 + 42 = 554 buffers

4-16

~
/

System Configuration

NumBuff for a Router NI with two associated LAP-B links would be:
Number of Inbound Buffers + Number of Outbound Buffers +
Number of Buffers (for fint LAP-B link) +
Number of Buffers (for the second LAP-B link)
Using the default values, this would be:
256 + 256 + 50 + 50

III

612 buffen

• NumReads and Nuttllri tes are the number of outstanding reads and the number of outstanding
writes. respectively. Both are configured through NMMGR in the LINKCONF IEEE 801. 3 and
ASNP data screens (Na~imum Outstanding Reads and Na~imum Outstanding llrites).
The NMMGR. default values for each link are:

Link

Maximum outstanding
Reads

Maximum outstanding
Writes

802.3

ASNP

7
5

BSC

3 (not configurable)
3 (not configurable)

LAP-B

For BSC and LAP-B use the value 3 for both the number of outstanding reads and writes in the
SYSOUMP dialogue.

• NumL inks is the maximum number of links concurrently open.
• NumPads&Terms is the maximum number of pads and virtual terminal devices.
• Numsess is the average number of jobs or sessions using 05/3000.
• NumDSlines is the average number of open OS lines on the system.
In addition to the above, the fonowing are recommended for NS3000/V services and links:

System Table Microcode: The Expanded System Table Microcode is required.
Memory: A minimum of two megabytes of memory is required.

4-17

System Configuration
Virtual Memory: If you use the d~fault number of TCP connections, 128, configure 60K sectors of
virtual memory. If the number of TCP connections is more than or less than 128, use the following
table to estimate the total virtual memory required for the system. These figures take into account
the requirements of MPE, the transport, and the network services.
In the following table. Sectors takes into account one NI plus one loopback NI.
additional NI. add in the amount listed under Sectors per Additional NIs.

Number of
Connections

64
128
512
1024

Sectors

35K
60K
200K
400K

Sectors for
Each Additional HI

1.2K
2.5K
10.0K
20.0K

Maximum Extra Data Segment Size: Increase to 32764 words.
IDtenupt Control Stack: Configure the maximum value for your system.

4-18

For each

System Confiluration

VIRTUAL TERMINAL CONFIGURATION DIALOGUE
For more information on virtual terminal confiluration, refer to I/O Configuration earlier in this section.
In the dialogue below, prompts are shown on the left, and recommended responses are underlined and/or
explained on the riaht.

LOGICAL DEVICE I?

To specify a device to be added or removed, enter the logical device
number (Idev) of that device.
Entering 0 or (RETURN) ends the I/O Configuration Changel
procedure;the dialogue skips to the next set of prompts, shown later
under ncompleting the SYSDUMP Dialosue. II

DEVICE NAME?

(RETURN)

DRT I?

For any of the IEEE 802. 3 lints. the Asynchronous SERIAL
Network Link, or the NS3000/V Point-to-Point Link (all of which
use the IOVTERMO virtual terminal), enter the Idev number of the
console preceded by a number sign (I).
For DS-Compatible links, which use 10DSTRMO or IODSTllMX
virtual terminals, you must enter the lclev number of the
corresponding INP preceded by a number sign (I).
To remove a device, enter!!; the dialogue returns to the
DEVICE '1 prompt.

LOGICAL

UNIT It

SOfTWARE CHANNEL I?

TYPE?

SUBTYPE?

Enter 0 in an cases except when connectina a OS-Compatible Link
to a oS/lOOO-IV node. in which case enter 8. Subtype 8 iI checked
by VPLUS/3000.
-

ENTER [TERM TYPE I] t
[DESCRIPTOR FILENAME] ?

SPEED IN CHARACTERS
PER SECOND?

Enter ..Q..for virtual terminals.
Default 240.

RECORD WIDTH?
OUTPUT

DEVICE?

40
Enter the same Idev u the

ACCEPT JOSS/SESSIONS?

YES

ACCEPT DATA?

LOGICAL DEVICE I requested above.

4-19

System Configuration

INTERACTIVE?

YES

DUPLICATIVE?

YES

INITIALLY SPOOLED?

AUTO REPLY!

-NO

DRIVER NAME?

Enter the appropriat, name:

IOVTERMO virtual terminal for: IEEE 802.3 Links,
NS Point-to-Point 3000/V Link,
Asynchronous SERIAL Network Link
IODSTRMO virtual terminal for: Point-to-Point
Modem or Hardwired Link (DS-Compatible)
IODSTRMX virtual terminal for: X. 25 or Satellite
Link (DS-Compatible)

DEVICE CLASSES?

For all NS links, enter device elass VTERM for each eoDfigured
IOVTERMO virtual terminal. Additional device class names are
allowed.
For the virtual terminals used with the DS-Compatible Links, enter
a list containing a device class name (up to eight alphanumeric
characters, beginning with a letter~ Class names are separated from
each other by commas. Note that VTERM and other class names
that are reserved for system devices are not permitted.

LOGICAL DEVICE '1

4-20

If all I/O configuration is complete, press (RETURN) and the I/O
configuration portion of the SYSDUMP dialogue will end.
Subsequent prompts in the dialogue are discussed under "Completing
the SYSDUMP DialogueU later in this section. If I/O configuration
is not yet complete, enter a logical device number and repeat the
above configuration procedure (or one of the other procedures listed
on the following pages).

System Configuration

LANle CONFIGURATION DIALOGUE
For more information on LANIC configuration, refer to I/O Configuration earlier in this section, or to
the LANIC Installation and Service Manual. In the dialogue below, prompts are shown on the left, and
recommended responses are underlined and/or explained on the right.

LOGICAL DEVICE ,?

To specify a device to be added or removed, enter the logical device
number (ldev) of that device.
Entering 0 or (RETURN) ends the I/O Configuration Changes
procedure;the dialogue skips to the next set of prompts, shown later
under l'Completing the SYSDUMP Dialogue. II

DEVICE NAME?
DRT

[RETURN)

To add a device, enter its DRT entry number. This number is
supplied by your C.B. The formula used to calculate the DRT
number from the hardware address is:

(IMS' •

128) +

(channel'.

To remove a device, enter
LOGICAL DEVICE '1 prompt.

8) + d.~ice

the dialogue returns to the

UNIT 11

SOFTWARE CHANNEL '1

TYPE?

SUBTYPE?

DRIVER NAME?

IOLANO

DEVICE CLASSES?

Enter a list containing a device class name (up to eight
alphanumeric characters, beginning with a letter~ Class names are
separated from each other by commas.

LOGICAL DEVICE I?

If all I/O configuration is complete, press (RETURN) and the I/O
configuration portion of the SYSDUMP dialogue will end.
Subsequent prompts in the dialogue are discussed under "Completing
the SYSDUMP Dialogue" later in this section. If I/O confipration
is not yet complete, enter a logical device number and repeat the
above configuration procedure (or one of the other procedures in
this section).

4-21

System Configuration

INP CONFIGURATION DIALOGUE
For more information on INP configuration. refer to I/O Configuration earlier in this section. or to the
INP llUtaUatloll and Service Manual.

Device Driver (IOINPO)
In the dialogue below, prompts are shown on the left, and recommended responses are underlined and/or
explained on the right.

LOGICAL DEVICE '1

DEVICE NAME?

(RETURN)

DRT '1

To add a device, enter its DRT entry number. This number is
supplied by your C.E. The formula used to calculate the DRT
number from the hardware address is:

(IMB# •

128) +

(ohannell •

8)+ de~ice'

To remove a device, enter ~ the dialogue returns to the
LOGICAL DEVICE '1 prompt.

UNIT '1

SOfTWARE CHANNEL '1

TYPE?

SUBTYPE?

For NS links. any value is overridden by NMMGR.
OS-Compatible links, .Q, 1 or ~ where:

o
1

For

= switched line with modem

= non-switched line with modem cable or direct connection

using modem eliminator cable
3 = hardwired line, synchronous transmission

RECEIVE TIMEOUT?

(RETURN)

Default: 20 (Do not enter 0.)
overridden by NMMGR.

LOCAL TIMEOUT?

For NS links, this default is

(RETURN)

Default: 20. For NS links, this default is overridden by NMMGR.
Range: 5-900 seconds; 0 disables the timer.

4-22

System Configuration

CONNECT TIMEOUT?

For NS links, enter· [RETURN) (the default value is overridden by
NMMGR). For DS-Compatible links, enter 300 for Subtype 0; ill
for Subtype I and 3.
Default: 900
Range: 60-900 seconds~ 0 disables the timer.

DIAL FACILITY?
(Subtype 0 only)

ANSWER FACILITY?
(Subtype 0 only)

AUTOMATIC ANSWER?
(Subtype 0 only)

DUAL SPEED?
(Subtype 1 only)

HALF SPEED?
(Subtype 1 only)

Enter the Idev number 01 the INP if the AUTO DIAL feature is
used.
Enter YES if manual dial-up is required.
Enter NO if no dial facility is required.
Enter YES if the local modem can answer calls, either manuany or
automaticany.
Enter NO if it cannot. A NO response causes the next step to be
skipped-:Enter YES if the local modem can automatically answer calls.
Enter NO if manual answering is required.
Enter YES if the local modem is dual speed (European models~
Enter NO if it is single speed. A NO response causes the next step to
be skipped.
Enter YES if the local modem is to operate at half speed.
Enter NO if it is to operate at full speed.

SPEED CHANGEABLE?

For all NS Point-to-Point 3000/V Links. you must enter YES. For
OS-Compatible links. you must enter YES to allow the speed of the
line to be changeable with the DSCONTROL command.
Enter NO for fixed line SPeed.

TRANSMISSION SPEED?

Enter the transmission speed of the line in characters per second (Bit
Rate/8). (For NS links. this value is overridden by NMMGR.)
Default: The speed specified is ignored for connections with modems
that provide internal clocking signals. For all other connections, the
speed you specify becomes the default. (Note also that for NS links,
this default is overridden by NMMGR.)

Speeds: 1SO. 300. 600. 900, 1200, 2400, 4800, 7000

TRANSMISSION MODE?

Enter 0 for full-duplex or 1 for half-duplex. (For NS links, always
enter 0:)
-

PREFERRED BUFFER SIZE?

1024 words. (For NS links, this value is overridden by NMMGR.)

DRIVER CHANGEABLE?

DRIVER OPTIONS?

DRIVER NAME?

IOINPO

4-23

System Configuration

PHONELIST?
(Subtype 0 only)

Enter YES to enter a phone number -- required for auto-dial. A
NO response causes the next step to be skipped.

PHONE NUMBER?

Enter the phone number.

(Subtype 0 only)
Up to 30 characters are allowed, consisting of a string of numbers,
hyphens, and special characters (I, E, 0, " *).

LOCAL ID SEQUENCE?
(Subtype 0 only)

REMOTE ID SEQUENCE?
(Subtype 0 only)

For NS Point-to-Point Dial links, this information is configured
through NMMGR as security strings, press [RETURNJ.
For a DS point-to-point link, enter a valid local ID sequence or
press (RETURN) for a nulllD sequence.
For NS Point-to-Point Dial links, this information is configured
through NMMGR as security strings, press [RETURN).
For a DS point-to-point link, enter a valid remote ID sequence or
press [RETURN) for a nulllD sequence.

DEVICE CLASSES?

Enter a list containing a device class name (up to eight
alphanumeric characters, beginning with a letter). Class names are
separated from each other by commas.

LOGICAL DEVICE I?

If all I/O configuration is complete, press [RETURN) and the I/O
configuration portion of the SYSDUMP dialogue will end.
Subsequent prompts in the dialogue are discussed under "Completing
the SYSDUMP Dialogue" later in this section. If I/O configuration
is not yet complete, enter a logical device number and repeat the
above configuration procedure (or one of the other procedures in
this section),

4-24

System Configuration

Communications Drivers (IODSO and IODSX)
In the dialogue below, prompts are shown on the left, and recommended responses are underlined and/or
explained on the right.

LOGICAL DEVICE ,?

To specify a device to be added or removed. enter the logical device
number (Idev) of that device.
Entering 0 or (RETURNI ends the I/O Configuration Changes
procedure; the dialogue skips to the next set of prompts, shown later
under "Completing the SYSDUMP Dialogue. II

DEVICE NAME?

[RETURNI

DRT ,?

You must assign the ldev number of the corresponding IN, preceded
by a number sign (I).

UNIT If

SOFTWARE CHANNEL ,?

TYPE?

SUBTYPE?

Enter!! for No data compression or ! for data compression.

RECORD WIDTH?

128

OUTPUT DEVICE?

For a communications driver. enter !!.

ACCEPT JOBS/SESSIONS?

YES

ACCEPT DATA?

INTERACTIVE?

YES

DUPLICATIVE?

YES

INITIALLY SPOOLED?

AUTO REPLY?

DRIVER NAME?

Enter the appropriate name:

IOOSO: Point-to-Point communications driver
IOOSX: X. 25 and Satellite communications driver
DEVICE CLASSES?

Enter a list containing a device class name (up to eight
alphanumeric characters, beginning with a letter). Class names are
separated from each other by commas.

4-25

System Configuration

LOGICAL DEVICE

4-26·

If all I/O configuration is . ;omplete, press (RETURNI and the I/O
configuration portion of the SYSDUMP dialogue will end.
Subsequent prompts in the dialogue are discussed under "Completing
the SYSDUMP DialogueU later in this section. If I/O configuration
is not yet complete, enter a logical device number and repeat the
above configuration procedure (or one of the other procedures in
this section).

System Configuration

ATP CONFIGURATION DIALOGUE
For more information on ATP (ASNP) configuration. refer to I/O Configuration earlier in this section.
In the dialogue below, prompts are shown on the left. and recommended responses are underlined and/or
explained on the right. Do not configure your remote support ATP port as an Asynchronous SERIAL
Network Link.

LOGICAL DEVICE

To specify a device to be added or removed, enter the logical device
number Udev) of that device.
Entering 0 or (RETURNI ends the I/O Configuration Changes
procedure;the dialogue skips to the next set of prompts.

DEVICE NAME?

{RETURNI

DRT If

To add a device. enter its DRT entry number. For the ASNP driver,
enter the DRT number that results from the following formula.
making sure that the number you enter is less than or equal to the
current highest allowable DRT number.
For Series 6x/70: (1MB' * 128) + (channell
For Series 39/58: (channel' * 8)

The channel number is the number set on the SIB's thumbwheel
switch. For Series 6x and 70. the first ATP is channel number I,
the second is 4, and additional ATPs are channel numbers greater
than 4. The ATP's Device number is always 0 and is not included
in the formula. (The SIB always returns Device number 0 to the
1MB.) The first 1MB number is O. the second is 1, and so on.
For Series 37. Micro 3000, Micro 3000 XE:
For the ATP37, the channel
cabinet where the ATP37
channel number 1, and a
allowed. The ATP's Device
in the formula.

(channel'. 8)

number is the number of the slot in the
board is placed. The first ATP37 is
maximum of four ATP37 boards are
number is always 0 but is not included

NOTE

Another way to find the DRT
number of the ATP is by giving a
"yesl! response to the I OMAP prompt
during system startup.

To remove a device. enter .Q; the dialogue returns to the LOGICAL
DEVICE
prompt.

4-27

System Configuration

UNIT I?

o -

95 for ATP. Unit numbers 0 through II correspond to ports
lion AlB number zero, unit numbers 12 through 23
~orrespond to ports 0 through lion AlB number one, and so on.

o through

o - 7 for ATP37. Unit numbers 0 through 7 correspond to ports 0
through 7.
SOfTWARE CHANNEL I?

TYPE?

SUBTYPE?

0, 1, or 2, where

= hardwired direct connection
= switched or non-switched

line with modem cable or
1
direct connection with modem cable
2

= line with a CCITT standard modem
NOTE

These subtypes will be overwritten by
information
in
the
network
configuration file
as specified
through NMMGR.

ENTER [TERM TYPE Il,
[DESCRIPTOR fILENAME] ?

SPEED IN CHARACTERS
PER SECOND?

RECORD WIDTH?

OUTPUT DEVICE?

ACCEPT JOBS/SESSIONS?

[RETURN)

ACCEPT DATA?

(RETURN)

INTERACTIVE?

(RETURN)

DUPLICATIVE?

(RETURN)

INITIALLY SPOOLED?

[RETURN)

AUTO REPLY?

(RETURN)

DRIVER NAME?

HIOASNPO

4-28

System Configuration

DEVICE CLASSES?

Any non -reserved device class names are allow~ up to eight
alphanumeric characters each (beginning with a letter), separated by
a comma.

LOGICAL DEVICE '1

If all I/O configuration is ~omplete, press lRETURNI and the I/O
configuration portion of the SYSDUMP dialogue will end.
Subsequent prompts in the dialogue are discussed under "Completing
the SYSDUMP Dialogue" on the following page.
If I/O
configuration is not yet complete. enter a logical device number and
repeat the above configuration procedure (or one of the other
procedures in this section).

NOTE

For the Asynchronous SERIAL Network Link, you must also configure as
many virtual terminals (IOVTERMO) as will access the HP 3000
concurrently over this link. These are in addition to those virtual terminals
configured for any other NS links. Remember that all IOVTERMO virtual
terminals should be back -referenced to the console.

4-29

System Configuration

COMPLETING THE SYSDUMP DIALOGUE
After alll/0 Configuration Changes are complete. the dialogue proceeds as shown below. Refer to the
"Ilecommendations for System Parameters" earlier in this section to check if any other chaR8es are
required.

LOGICAL DEVICE ,?

(RETURN)

MAX , OF OPENED SPOOLFILES
(MIN=nn. MAX=nnn)?

[RETURN)

LIST OF I/O DEVICES?

Enter YES to print a listing of the new I/O device configuration.

LIST CS DEVICES?

Enter YES to list the characteristics of the new CS device
configuration.

TERMINAL TYPE CHANGES?

(RETURN)

CLASS CHANGES?

(RETURN)

LIST I/O DEVICES?

(RETURN)

ADDITIONAL DRIVER CHANGES?

[RETURN)

I/O CONFIGURATION CHANGES?

IRETUR!J

SYSTEM TABLE CHANGES?

YES

CST = nnn (MIN=mm.
MAX=pppp)?

Increase the number listed here as nnn to match the number of
additional CST entries needed (calculated earlier in this section
under --System Parameters-,.

EXTENDED CST = nnnn (MIN=
nrn. MAX=pppp)?

lRETURN)

O5T = nnnn (MIN=mm.
MAX= pppp)?

Increase the number listed here as nnnn to match the number of
additional DST entries needed (calculated earlier in this section
under "System Parameten".

PCB = nnn (MIN=mm.
MAX=pppp)?

Increase the number listed here as nnn to match the number of
additional PCB entries needed (calculated earlier in this section
under l'System Parameten?

I/O QUEUE = nnn (MIN=mm.
MAX=pppp)?

Increase the number listed here as nnn to match the number of
addtional I/O Queue entries needed (calculated earlier in this
section under --System Parameted?

DISC REQUEST QUEUE = nnn
(MIN=nrn. MAX=ppp)?

[RETURN)

TERMINAL BUFFERS PER PORT =
n (MIN=m. MAX=pp)?

(RETURN)

=nnn

4-30

System Configuration

SYSTEM BUFFERS = nn (MIN=
m, MAX=ppp)?

lRETURN)

SWAP TABLE = nnnn (MIN=
"""', MAX=pppp)?
PRIMARY MESSAGE TABLE = nnn
(MIN=mm, MAX:pppp)?
SECONDARY MESSAGE TABLE
nn (MIN=mm, MAX:pppp)?

(ReruRN)

SPECIAL REQUEST TABLE : nnn
(MIN=mm, MAX=pppp)?

(RETURNI

ICS = nnnn (MIN=mmm,
MAX=pppp)?

Increase I the current value, listed here as """". to the maximum
value, listed here as pppp.

LOADER SEGMENT TABLE =
nnnnn (MIN=mmmm, MAX=
ppppp)?

(RETURN)

UCOP REQUEST QUEUE
(MIN=m, MAX=pppp)?

lRETURN)

= nnn

(RETURNI

TIMER REQUEST QUEUE =
nnn (MIN=m, MAX=pppp)?

[RETURN)

BREAKPOINT TABLE = nn (MIN=
m, MAX=pppp)?

[mouRN)

MAX NUMBER OF USER LOGGING
PROCESSES = nn (MIN=m,
(MAX=pp)?

[RETURNI

MAX NUMBER or USERS PER
[RETURN)
LOGGING PROCESS = nnn (MIN=m,
MAX= ppp)?
MISC CONFIGURATION CHANGES?

[~RN)

LOGGING CHANGES?

lRETURNI

DISC ALLOCATION CHANGES?

YES

MAX DIRECTORY SIZE (SECTORS) lRETURNI
= """" (MIN=nrmm, MAX= ppppp,
USED=qqqq)?
LIST VOLUME TABLE?

(RETURNI

DELETE VOLUME?

{RETURNI

ADD VOLUME?

[RETURNI

4-31

System Configuration

LIST VOLUME CHANGES?

(RETURN)

VIRTUAL MEMORY CHANGES?

YES

LIST VIRTUAL DEVICE
ALLOCATION?

(RETURN) (If you respond YES, each volume is listed WIth its ldev and
current virtual memory allocation.)

ENTER VOLUME ~AME , SIZE IN
KILOSECTORS ( MAX = nnn)?

At least 30 additional sectors need to be allocated to virtual
memory for NS products.

VIRTUAL MEMORY CHANGES?

(RETURN)

MAX , OF SPOOLFILE
KILOSECTORS = nnnn (MIN=O,
MAX=""""",)?

(RETURN)

, OF SECTORS PER SPOOLFILE
EXTENT = nnnn (MIN=mmm,
MAX=ppppp)?

(RETURNI

SCHEDULING CHANGES?

(RETURN)

SEGMENT LIMIT CHANGES?

YES

MAX' OF' CONCURRENT RUNNING
PROGRAMS = nn (MIN=1, MAX=

(RETURN)

""",)?

MAX CODE SEGMENT SIZE =
(RETURN)
nnnnn (MIN=mmmm, MAX= ppppp)?
MAX , OF' SEGMENTS/PROCESS =
nn (MIN=1, MAX=mmm)?

(RETURN)

MAX STACK SIZE = nnnnn
(MIN=mmm, MAX=ppppp)?

(RETURNI

MAX EXTRA DATA SEGMENT SIZE
= nnnnn (MIN=O, MAX=""",,,,,)?

32764

MAX' OF' EXTRA DATA SEGMENTS
/PROCESS = nnn (MIN=O,
MAX=""",)?

(RETURNI

STO STACK SIZE :: nnnn (MIN=
"""', MAX=pppp)?

(RETURN)

SYSTEM PROGRAM CHANGES?

(RETURN)

SYSTEM SL CHANGES?

[RETURN)

ENTER DUMP DATE?

Enter the appropriate response from the four possible listed here:

4-32

System Configuration
1) (RETURN) C(lpi~ the modified MPI< When this copy is used to
COLDSTART the system, the Slccount structure and all files remain
intact
2) mm/dd/yy where .nm/dd/YY is some date in the future. Copies
the modified MPE and the current accounting, but no files.

3) mm/dd/~y where mm/dd/yy is usually the date of the most
recent system backup Copies the modified MPE. the current
accounting structure, and an)' files that were changed on or since
the specified date.
4) 0 Copies the entire system (MPE. the current accountinl
structure and all files).

ENTER DUMP FILE SUBSETS?

Press rREfuRNI, or enter a filename or series of filenames. (Example:
@. PUB. SYS)

LIST FILES DUMPED?

YES or NO

The console operator must now use the =REPLYcommand to assign the magnetic tape drive on which you
have arranged for a tape reel to be mounted
After the SYSDUMP is complete, the tape produced should be used to COLDSTART the system. Durina
COLDSTART, the existing I/O device configuration is replaced with the new one from your SYSDUMP
tape. Refer to the MPE Y System Operation and Resource Management Reference Manual.

4-33

System Configuration

CONFIGURATION EXAMPLES
The following examples illustrate possible configurations for nodes with multiple Nis and multiple link
products installed. For each example, please refer to Figure 4- 3, which shows a simplified catenet.

(HP3000 Series 110

INTERNET MAP

r------------------------I
I

(LAN)

,~-----------------------------,
I
I

NET1

OS-Compatible
Point-to-Point

.
I
I

NET2

(ROUTER)

••
•
I

--~--------- E

I
I

I
I
I

•
•I
•1

--~-------------------------------------------~------~-

~--------------------------------------

- ------_.

---------------

------------------------------------------------

Figure 4.3 Example Network

4-34

••

I
I

System Configuration

Example 1
This example shows a SYSDUMP listing of the I/O devices on Nod~ C in Figure 4- 3. Node C is a fuU
gateway between a LAN (Net I) and a Router Network (Net 2). Node C has NS 3000/V installed, with
the following link products: ThinLAN/3000 Link, N~ POlnl -to-Point 3000/V Link. and one
DS-Compatible Point-to-Point Modem Link to an HP 3000 Setles III (Node B).
Either of the INPs configured can be used as back-up NS links to Node F. Note that I/O configuration in
SYSDUMP does not indicate which devices are shared. In this example, the DEVICE CLASS field has been
used to indicate possible shared links. Alternatively, an INP configured for an existing DS-compatible
link could be used as an NS point-to-point link.. but not at the same time. The SYSDUMP items you
must verify for consistency from DS to NS are decribed in Appendix E, OS vs NS INP Configuration.

LIST I/O DEVICES? Y
LOG DRT U C T SUBREC
DEV , N H Y TYPE TERMINAL WIDTH
,
I AP
TYPE SPEED
T

N E

0 0

OUTPUT
DEV

128

26 0 0 3 8

128

0 24 0

128

145 1 0 24 0
10 73 2 0 24 0
14 167 0 0 32 8

128
128
66

6
7

155 0

0 3

90 0 0 32 13
145 0

MODE

o
PP

JA
S

DRIVER
NAME

DEVICE
CLASSES

*HIOMDSC1 SYSOISC
SPOOL
HIOMOSC2 SPOOL
DISC
HIOMDSC2 SPOOL
DISC
HIOCIRRO LP
SLOWLP
HIOTAPEO TAPE
DDUMP
HIOTAPEO TAPE
HIOTAPEO JOBTAPE
HIOPPRTO PP
EPoe

20 8

0 0 16 0

960

JAID

1 0 16 0

960

JAID

HIOTERM1 ATPTERM
CONSOLE
HIOTERM1 ATPTERM

(configured terminals, ldev 22-99, not shown)

100 8 80 0 16 0
109 48 0 0 17 9
110 41 0 0 17 0
11"'10
112"'0
113"10
1141110
115"10

0
0
0
0
0

41
16
16
16
16

0
0
0
0
0

0
0
0
0

960

240
240
240
240

128
40
40
40
40

112
113
114
115

JAIO

JAIO
JAID
JAIO
JAIO

HIOTERM1 ATPTERM
IOLANO
LANIe
IOINPO
INP
TONODEB
TONODEf
IOOSO
NODEB
IOOSTRMO OSTERM
IODSTRMO OSTERM
IODSTRMO OSTERM
IODSTRMO OSTERM

4-35

System Configuration

120 42

o 17 3

121'20
122'20
123120
124120
125'20
126'20
127120
128120
129120
130'20
131'20
132120
133120
134120
135'20
136120
137120
138120
139120

0
0
0
0
0
0
0

o 16
o 16
o 16
o 16
o 16
o 16
o 16
o 16
o 16
o 16
o 16
o 16
o 16
o 16
o 16
o 16
o 16
o 16
o 16

0
0
0
0
0
0
0
0
0
0
0

0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

0
0
0
0
0
0
0
0
0
0
0

0
0
0
0
0
0
0
0

240
240
240
240
240
240
240
240
240
240
240
240
240
240
240
240
240
240
240

40
40
40
40
40
40
40
40
40
40
40
40
40
40
40
40
40
40
40

121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139

IOINPO
J
J
J
J
J
J
J
J
J
J
J
J
J

J
J
J
J
J

10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10

IOVTERMO
IOVTERMO
IOVTERMO
IOVTERMO
IOVTERMO
IOVTERMO
10VTERMO
IOVTERMO
IOVTERMO
10VTERMO
IOVTERMO
IOVTERMO
IOVTERMO
IOVTERMO
IOVTERMO
IOVTERMO
IOVTERMO
IOVTERMO
IOVTERMO

INP
TONODED
TONODEF'
VTERM
VTERM
VTERM
VTERM
VTERM
VTERM
VTERM
VTERM
VTERM
VTERM
VTERM
VTERM
VTERM
VTERM
VTERM
VTERM
VTERM
VTERM
VTERM

The preceding thirteen columns display the following information:

• LOG OEV ,-- Logical device number.
• The ldev numbers for the INP devices are 110 and 120. The first INP, Idev 110, is used by
a DS-Compatible link to a Series III (Node B in our sample catenet). Ldev 111 is the
associated IODSO communications driver for this INP. There are also four IODSTRMO
virtual terminals for this INP, configured as Idev numbers 112-115, and back-referenced to
ldev 110.
The second INP, ldev 120, is used by an NS Point-to-Point Link to Node D and requires no
separate communications driver.
• The Idev number for the LANIC in this example is 109.
• The ldev numbers for the pool of virtual terminals shared by the NS links are 121 -139.
Note that these virtual terminals are each back-referenced to the console.

• ORT 1 -- Device Reference Table'(DRT) number. The DRT number for the LANIC is 48. The
DRT numbers for the INP devices are 41 and 42. The communications driver (lOOSO) and the
virtual terminals (IOOSTRMO and IOVTERMO) display the Idev number of the appropriate device,
preceded by a I, in place of the DRT number..
• UNIT and CHAN -- Device Unit Number and Hardware Channel Number. Channel number is

unused and always set to 0; unit number is unused and set to 0 except in the case of ports
configured for an ATP. (Refer to Example 2 for the way unit number is used with the NS
Asynchronous 3000/V Link.)

4-36

System Configuration
• TYPE and SUBTYPE -- Device Type and Subtype 'the LANIC is configured as type , 7., subtype
9. The INP device used for a NS link is configured as type 17., subtype 3; the INP used for a

switched modem connection is configured as type I 7, subtype O. The communications driver
(IOOSO) is configured as type 41, subtype 0., which means a default of no data compression. All

the terminals and virtual terminals are configured as type '6t subtype O.
• TERMINAL TYPE and SPEED -- Terminal Type and Speed.

These columns only apply to

terminals.
• REC WIDTH -- Record Width.

ThIS value is expressed in words. The virtual terminals are
configured at 40; the communications driver is configured at 128. For INPs and the LANle, the
record width is set to zero.

• OUTPUT DEV -- Corresponding Output Device. Notice that the virtual terminals all have their
ldev number entered as their corresponding output device.
• MODE - - Device Mode.
• DRIVER NAME -- Device Draver Name.
• DEVICE CLASSES -- Device Classes.
configured with device class VTERM.

As required, all the IOVTERMO virtual terminals are

4-37

System Configuration

CS Device Listing
The SYSDUMP listing of CS devices on Node C would show the following:
LIST CS DEVICES? V
LON PM PRT lCL TC RV
LCL
CON MODE
MOD
TMOUTTMOUTTMOUT
0
109 0 X
X X 0
0
110 0 X
60
120
X X 20
120 0 X
X X 20
60
120

TRANSMIT
SPEED
0
C
C

7000
7000

TM BUFrER 0 DRIVER
SIZE C OPTIONS
N 0
0 0

0
0

1024
1024

N
N

0
0

The CS listing provides information primarily on the INP configuration, which is described earlier in this
section. Specifying subtype 9 for the LANIC skips the CS prompts in the SYSDUMP dialogue; the values
for the LANIC (ldev number 109) are set to zero in the CS listing. The headings for the fourteen columns
of information are:

4-38

• LON -- Logical Device Number.

• CON TMOUT - - Connect Timeout.

• PM - - Port Mask.

• MODE -- Mode.

• PRT - - Protocol.

• TRANSMIT SPEED -- Transmit Speed.

• lCL MOD -- Local Mode.

• TM - - Transmission Mode.

• TC -- Transmission Code.

• BUrrER SIZE -- Buffer Size.

• RV TMOUT -- Receive Timeout.

• DC -- Driver Changable.

• LCL TMOUT - - Local Timeout.

• DRIVER OPTIONS -- Driver Options.

System Configuration

Example 2
This example shows a SYSDUMP listing for the I/O devices on Node G in Figure 4-3. Node G is a
member of the Router Network. Net 2. and forms a gateway half node between Net 2 and Net 3. Node G
has NS3000/V installed, with the following links products: NS Point-to-Point 3000/V. NS Aynchronous
3000/V Link, and one DS-Compatible link for support of PAD terminals in the X. 2S network.
Either of the INPs configured can be used as back-up NS links to Node F. Note that I/O configuration in
SYSDUMP does not indicate which devices are shared. In this example. the DEVICE CLASS field has been
used to indicate possible shared links. Alternatively. an INP configured for an existing DS-compatible
link could be used as an NS point-to-point link, but not at the same time. The SYSDUMP items you
must verify for consistency from OS to NS are decribed in Appendix E. DS vs NS INP Configuration.

LIST I/O DEVICES? Y
LOG ORT U C T SUBREC
DEV , N H Y TYPE TERMINAL WIDTH
,
I AP
TYPE SPEED
T

OUTPUT
OEV

N E

25 0 0 0 9

128

26 0 0 3 8

128

155 0 0 3 8

128

0 32 13

0 24 0

128

8 145 1 0 24 0
10 73 2 0 24 0
14 167 0 0 32 8

128
128

6
7

145 0

MODE

JA
S

DRIVER
NAME

DEVICE
CLASSES

*HIOMDSC1 SYSDISC
SPOOL
HIOMDSC2 SPOOL
DISC
HIOMDSC2 SPOOL
OISC
HIOCIRRO LP
SLOWLP
HIOTAPEO TAPE
DDUMP
HIOTAPEO TAPE
HIOTAPEO JOBTAPE
HIOPPRTO PP
EPOC

20 8

0 0 16 0

960

JAID

1 0 16 0

960

JAID

HIOTERM1 ATPTERM
CONSOLE
HIOTERM1 ATPTERM

(configured tenminals, Idev 22-99, not shown)
100 8

110 41
""20
112'20
113'20
114120

115'20
116'20
,117'20

118'20

0 16 0
0 0 17 3

0 16
o 0 16
o 0 16
o 0 16
o 0 16
o 0 16
o 0 16
o 0 16

960

0
0
0

o
o
o

0
0
0
0

o
o

240
240
240
240
240

240
240
240

40
40
40
40
40
40

40
40

111
112

113
114
115
116
117

118

JAID

J ID
J
J
J
J
J
J
J

10
10

ID
10

ID
ID
10

HIOTERM1 ATPTERM
IOINPO
INP
TONODED
TONODEF
IOVTERMO VTERM
IOVTERMO VTERM
IOVTERMO VTERM
IOVTERMO VTERM
IOVTERMO VTERM
IOVTERMO VTERM
IOVTERMO VTERM
IOVTERMO VTERM

4-39

System Configuration

0
0

119'20
130 43

0 16 0
0 17 1

o 41

0
0
0
0
0
0

150 8

84 0 42 0

o 16 0

16
16
o 16
o 16

240

131"30
'32"30
133"30
1341130
135'.130
'36"30

o
o

0
0
0
0

11
11
11
11
11

40
0

119
0

128
40
40
40
40
40

0
132
133
134
135
136

J 10

J
J
J
J
J

10
10
10
10

IOVTERMO VTERM
IOINPO INP
TONODEH
IODSX
X25
IOPADO PADTERM
IOPADO PADTERM
IOPADO PADTERM
IOPADO PADTERM
IOPADO PADTERM
TONOOEF
HIOASNPO RASP
TONODEE

The preceding thirteen columns display the following information:

• LOG DEV , -- Logical device number.
• The ldev numbers for the INP devices are 110 and 130. The first INP, Idev 110, is used by
an NS Point-to-Point Link to Node D in Net 2.
The second INP, ldev 130, is used by aDS-Compatible X. 25 Link for communication with
PAD terminals in Net 3 through node H. Ldev number 131 is the required communications
driver (IODSX) associated with this INP. Five IOPADO virtual terminals, Idev's 132-136,
are also back- referenced to this INP.
• The Idev number for the ATP in this example is 150. This ATP is used by an Asynchronous
Link to Node E.
• The Idev number for the pool of virtual terminals shared by the NS links are 111-119.
Note that these virtual terminals are back-referenced to the console.

• ORT , -- Device Reference Table (DRT) number. The DRT number for the ATP device is 8.
DRT numbers for the INP devices are 41 and 43. The communications driver (IODSX) and the
virtual terminals (IOVTERMO and IOPADO) display the ldev number of the appropriate device,
preceded by a', in place of the DRT number.
• UNIT and CHAN -- Device Unit Number and Hardware Channel Number. Channel numbers are
unused and are set to 0; unit numbers are unused and are set to 0, except in the case of ports

configured for the ATP. Units 0 through 11 correspond to ports 0 through 11 on AlB 0, unit
numbers 12 through 23 correspond to ports 0 through 11 on AlB I, and so on. In our example,
the ATP driver (HIOASNPO) is configfured as unit 84 (port 0 of AlB 7).
is configured as type 42, Subtype o.
INP devices used for NS links are configured as type 17, subtype 3; the INP used for a switched
modem connection is configured as type 17. subtype O. The communications driver (IODSX) is
configured as type 41, subtype 0, which means a default of no data compression. All terminals
and virtual terminals are configured as type 16, subtype O.

• TYPE and SUBTYPE -- Device Type and Subtype. The ATP

• TERMINAL TYPE and SPEED -- Terminal Type and Speed.

These columns only apply to

terminals.

• REC WIDTH -- Record Width. This value is expressed in words. The virtual terminals are
configured at 40; the communications driver is configured at 128. For INPs the record width is
set to zero.

4-40

System Configuration

• OUTPUT DEV -- Corresponding Output Device. Notice that the virtual terminals all have their
ldev number entered as their correspondIng output device.

• MODE - - DevIce Mode.
• DRIVER NAME -- Device Driver Name.
• DEVICE CLASSES -- Device Classes.
configured with device class VfERM.

As required. all tht tOVTERMO virtual terminals are

CS Device Listing
The SYSDUMP listing of CS devices on Node G would show the following:

LIST CS DEVICES? Y
LON PM PRT LCL TC RV
LCL CON MODf
MOD
TMOUT TMOU' TMOUT
110 0 X
X X 20
60
120
130 0 X
X X 20
60
120

rRANSMIT TM BUffER 0 DRIVER
SPEED
SIZE C OPTIONS
C 7000
7000

0
0

1024
1024

N
N

0
0

The CS listing provides information primari~ \" on the INP devices. Information on the ATP does not
appear in this listing. However, status information about . he ATP is displayed when the : SHOWCOM
command is entered. The headings for the fourteen column~ of Information are:

• LON - - Logical Device Number.

• CON TMOUT -- Connect Timeout.

• PM - - Port Mask.

• MODE - - Mode.

• PRT - - Protocol.

• TRANSMIT SPEED -- Transmit Speed.

• LCL MOD -- Local Mode.

• TM - - Transmission Mode.

• TC - - Transmission Code.

• BUffER SIZE -- Buffer Size.

• RV TMOUT -- Receive Timeout.

• DC -- Driver Changable.

• LCL TMOUT -- Local Timeout.

.• DRIVER OPTIONS -- Driver Options.

SHOWCOM Listing
The following is a sample listing of the MPE SHOWCOM command when used for the above ATP:

:SHOWCOM 150
LON - 150
MESSAGES SENT 391680
MESSAGES RECVO
LAST RECOVERABLE ERROR
0
LAST IRRECOVERABLE ERROR 0
LINE IS CONNECTED

270·89

4-41

...

~E NMS CONFIGURATOR (NMMGR)

1~51

This section describes the operation of the Node Management Services Configurator (NMMGR), a utility
program that provides a series of VPLUS/3000 block-mode screens to display and accept configuration
information. The data entered into these configuration screens are stored in a configuration file, which is
a data file with a hierarchical structure and MPE file code NCONF The configuration information is
used for initializing the NS3000 network transport.
Configuration is divided into three parts:
• Defining the operating parameters required for the Link Services subsystem.
• Defining the operating parameters required for the Network Transport subsystem.
• Enabling/disabling logging classes for each of the NMS subsystems of NS3000/V and NS3000/V
links.
NMMGR includes utility screens that enable you to perform such tasks as compressing and expanding a
configuration file, printing a listing of the data entered, and displaying errors.
This section contains the following subsections:
• Getting Started with NMMOR
• The Open Configuration/Directory File Screen
• The Main Menu Screen
• Oetting Help
• NMMGR Screen Structure
• Configuration Files
• Using NMMGR Configuration Screens
• General Operation of Screens
• Menu Screens
• Select Screens
• Data Screens

5-1

The NMS Configurator (NMMGR)
• Using NMMGR Utility Screens
• Output Configuration File
• Compress Configuration File
• Validate Configuration File
• The Configuration Subtree Copy Screen
• The Error Information Screen
• Copying Configuration Data
• Making Configuration Changes
For field descriptions of configuration screens, refer to Sections 7 through 13. Section 7 describes the link
configuration screens. Section 8 describes the network transport configuration screens that apply to all
network interface types (LAN, router, gateway half and loopback). You should read Section 8 before
proceeding to the next four sections (9 through 12). Each of these four sections is devoted to the network
traDSPOrt configuration screens of one network interface type. Section 13 describes the logging
configuration screens.
Section 6 describes how guided configuration operates. Section 14 describes the Network Directory,
including how to create and modify network directory files.
This section describes how to create and modify regular configuration files.

GETTING STARTED WITH NMMGR
You must have MPE Node Manager (NM) or Network Administrator (NA) capability to run NMMGR.
Enter the following command in response to an MPE prompt:

:RUN HMMGR.PUB.SYS
After MPE accepts the run command, NMMGR displays the following message:

NMS Configuration Manager

32098-20012 A.02.00 (e) Hewlett Packard Co. 1986

NMMGR then clears the terminal screen and displays the Open Configuration/Directory File screen
(Figure 5-1). The OPen Configuration/Directory File screen enables you to specify a configuration file or
network directory file to open or create. Specifying a configuration file name and pressing the [ t I l
.',' or the [ t 2 I I
,,:.:"': key takes you to the Main Menu screen.
The Main Menu
(Figure 5-2) allows you to proceed to either manual configuration, utility screens, or guided
configuration.

S-2

The NMS Configurator (NMMGR)

The Open Configuration/Directory File Screen
After you open or create a configuration file using the Open Configuration/Directory File screen. the file
is directly accessed. and any changes you make are immediately written to the file.
If you create a configuration file for a new network. your configuration takes effect when the network is
brought up for the first time. You can modify routing information for an existing configuration without
bringing down the network by using the Update branch of guided configuration, followed by the
NETCONTROL UPDATE command. To activate or deactivate configured links without bringing down the
network, you can use the NETCONTROL ADDLINK and NETCONTROL DELLINK commands. These three
commands can be issued from the MPE prompt and are the only means of modifying a configuration
while the transport is active. These commands are fully described in Volume D. Section 1.
NOTE

For recommendations on making configuration changes, refer to the
"Making Configuration Changes" subsection later in this section.

Configuration file name
NMCONFIG.PUB.SYS
NSCONF.NET.SYS

default for LOGGING, NRJE, SNANODE, APPC.
default for NETXPORT.

Network Directory file name

Figure 5-1. Open Configuration/Directory File SCreen

5-3

The NMS Configurator (NMMGR)
At the top of each screen is a header, which identifies the version number of the NMMGR program and
the screen name.
In Figure 5-1, the version number is A.02.00 and the screen name is
OPEN CONFIGURATION/DIRECTORY FILE.
The fields labeled Configuration file name and
Network Directory file name are used to specify the configuration/network director) file to be
~reated or modified. The bottom of each screen includes function key labels, which identify the functions
that NMMGR assigns to keys [ f' I through [ t, I on your terminal. These functions vary from
screen to sereen. The function keys of the Open Configuration/Directory File screen are described in
Table 5-1. If the labels are blank, the function keys are unused.
TABLE 5-1. FUNCTION KEYS FOR THE OPEN CONFIGURATION/DIRECTORY FILE SCREEN

Key

Function

Description

This key opens an existing configuration file, named in
the Configuration file name field. The file must
already exist.

This key creates a new configuration file, named in the
Configuration file name field. The file must not
already exist.

This key opens an existing network directory file, named
in the Network Directory file name field. The file
must already exist.

This key creates a new Network Directory file, named in
the Network Oi rectory fi Ie name field. The file
must not already exist.

This key refreshes the current screen to its default or
original data. This key is described in more detail later
in this section.

This key exits NMMGR. If you have an open
configuration file, NMMGR closes it. Any
modifications made while the file was open are saved.

NOTE
An NMMGR screen is 24 lines long. If your terminal screen is longer than
14 lines, the NMMGR labels appear to be four lines tall with blank labels
on the bottom two lines. These lines are blank because the functions
assigned by NMMGR clear any existing functions. Any user-defined
functions are saved and are restored after exiting NMMGR.

5-4

~.'.':'

The NMS Configurator (NMMGR)

SpecIfying the Configuration FOe Name
Three configuration files are required for the operation of NSJUOO/V Network Services and NS3000/V
link products. Two of them are created with NMMGR, and are described below.
• One configuration file is used to define the link configuration and Network TransPOrt
confjguration. This file must reside In the NET group of the SYS account. HP recommends that
you name the file NSCONF which is the file name that the Network Transport looks for at
initiation if one is not SPecified. This file is also used to define the logging configuration for the
Network Transport subsystem.
• The other required configuration file defInes the Loggins oonfiguration for the Network Services,
NetlPC, and the NMS Link Services. This second file must be named NMCONFIG. PUB.SVS.
The third configuration file is named DADCONF. NET .SYS, and is necessary for the operation of Network
Services. For more information on DADCONF. NET. SYS, refer to Section 2, "Network Management. It

~ CAUTION

NMCONFIG. PUB.SVS is also required for the following HP-to-IBM data
communications products: SNA Link, SNA IMF, SNA NRJE, and LV 6.2
Base. If you have one or more of these products installed, this file is in use
and must not be modified while the HP-to-IBM products are active. If you
use the logging configuration recommended by HP, it should not be
necessary to modify this file.
Only the logging information of
NMCONFIG. PUB.SVS is used by NS3000/V services and link products.
However, if you do need to modify logging, make sure that the file is not in
use, and exercise great care not to modify any of the configuration
specifications used for the HP-to-IBM products. Refer to the SNA Link
Services Reference Manual for information on the configuration of
UP-to-IBM products.

A sample configuration file, NMSAMP1 • PUB. SYS, is supplied with NS3000/V links. This file shows you
the recommended values for the NMCONFIG. PUB.SVS configuration file, used to configure NMS logging
for the Network Services, Network Interprocess Communication, and Link Support Services subsystems.
The values in this file are set to optimize performance of NS3000/V and NS3000/V links during normal
operation. UP recommends that you do not change the values specified in this sample file, except on the
advice of your HP representative.
Also supplied is the file SAMPCONF. NET. SYS. an example of the file NSCONF. NET. SYS (or
filename. NET. SYS). The contents of SAMPCONF. NET. SYS correspond to Node G of the example catenet
described in the "Configuration Worksheets" portion of Section 3. This example file is to be used only as a
reference and not as a base for building your own file. To see the contents of SAMPCONF. NET. SYS,
simply run NMMGR. enter the file name in the Configuration file name field of the Open
ConfigurationlDirectory File screen, and press the (r' ,:~j~~:" """7'"' function key.

s-s

The NMS Configurator (NMMGR)

Opeaing or Creating Ole Configuration

Enter the name of the configuration file that you want to work on and press (l r, I) 1.11:
' if it
is an existing file, or (I (a I) ';',::,,'
'j!'H if it is a new file. NMMGR qualifies the file name with
your 1010n group and aceount if you do not specify the group or account
NMMGR performs the following checks before creating or opening the specified configuration file:
• NMMGR checks the appropriate MPE file security specifications.

l',

• If you pressed
II,:
NMMGR checks that the file specified exists and that it is a
configuration file (file code NCONF).
If currently accessing a different configuration file, NMMGR closes the file before opening the specified
configuration file. If the specified configuration file fails one of the checks listed above, an error message
is displayed in the line immediately below the screen title. For more detailed information on an error
encountered, use the Error Information screen, described later in this section.

The Main Menu Screen
Once the configuration file is successfully opened or created, NMMGR displays the second screen, the
Main Menu screen (Figure 5-2). As indicated by the three choices on the main menu, the NMMGR
screens have been divided into three distinct groups of screens. The configuration screens are arranged
hierarchically, with a structure that corresponds to the configuration file structure. Use the screens to
examine or modify a configuration file.

5-6

The NMS Configurator (NMMGR)

CONfIGURATION

- Modify or examine a Configuration file.

UTILITY

- Configuration file Utility functions(output,compres8,valldate).

GUIDED CONfIG

- Guided Configuration of 8ubsyeteme.

file:

filename. group. acct

Filure 5-2.. Main Menu Screen
allows you to proeeed to any confisuration screen.
The function key I , . I
overview and descriptions of the features of each screen ean be found in sections 7 through 13.

key allows you to access the utility screens. Use the utility screens to
The I , 2 I·
compress. output and validate a configuration file. and to copy a portion of it to another configuration
file.

The I
I
' key takes you to Guided Configuration. This function SUides you through
the sereens used to configure a node in a network subsystem. Guided Configuration is described in detail
in Section 6. Because guided configuration is faster than manual configuration, you should use auiclecl
configuration whenever possible.

Getting Help
NMMGR provides an online help function. You can use this function to obtain information about
commands, and other topjea pertaining to NMMGR. You can access the help function from the
command line of any ICreen.

ICreellS,

• Enter HELP from the command line to brins up help text for the current screen, including all
field descriptions for the screen.

5-7

The NMS Configurator (NMMGR)

• Enter HELP and either a keyword or a keyword with a qualifier to bring up help text about a
specific topic, not necessarily the current screen. The topics fall into four main categories. all of
which are keywords. These are OVERVIEW, 1l0ADMAP. COMMANDS. and MAiNT.
If you enter HELP OVERVIEW you will see a brief explanation of the operation of NMMGR.
If you enter HELP ROAOMAP you will receive a map of the screen structure of NMMGIl. You
will also receive a list of additional keyword~ consisting of the subsystems supported by
NMMGR. Each of these subsystem names, such as LINKCONF, can be used as a qualifier to
obtain a map of the screens pertaining to the listed subsystem. A qualifier, which also is
considered a keyword, must follow the main keyword with a comma separating the two
keywords. For example, if you wanted to see a map of LINKCONF screens, you would enter
HELP ROADMAP,LINKCONF' in the command window. Every sereen name shown in these sereen
maps is a keyword of its own, and ean be used with the HELP eommand and the FIELDS
qualifier. For example, if you wanted to see field descriptions for the screen called LAN, you
would enter HELP LAN ,FIELDS in the command window.
If you enter HELP COMMANDS you will obtain a list of commands available from within the
VPLUS interface. For information about a specific command. enter the name of the command as
a keyword following the word HELP in the command window.
If you enter HELP MAINT you will see a list of commands available within maintenanc;e mode.
For information about a specific command. enter the name of the command as a keyword
fonowing the word HELP in the command window. If you do obtain information about a
specific command, the help· text will list any qualifier~ such as PARMS, OPERATION,
EXAMPLE, and ALL. You then could enter the command again. this time followed by a comma
and a qualifier, to obtain even further information.'

• Enter a question mark (1) from the command line to put you in help mode. In this mode, you can
browse through various topics until you terminate help mode by typing "end", "exit", or ":".
Terminating help mode returns you to the screen you entered from.

NMMGR Screen Structure
Figure 5-3 shows the screen structure of NMMGR used to define the network configuration of
NS3000/V and NS3000/V links. This is a subset of the complete NMMGR scree" structure, which
Include. ,creens for other HP data communications products. The Open Configuration/Directory File
screen is shown at the top of the screen structure because it is the first screen displayed when you run
NMMGR.
In Figure 5- 3, the function key used to reach each screen below the Main Menu is listed in the top part of
the screen'. box. To keep Figure 5-3 easy to follow, not all lower-level screens are shown. Where
screens exist at any level beneath a box but are not shown, the section number of this volume is listed as a
reference to these other screens. How to proceed from screen to screen is described in more detail under
"General Operation of Screensu later in this section.

5-8

The NMS Configurator (NMMGIl)

1)pI ERRORS "

...

0pIn Conf9n~

CICNIIftInd . . . of

DIrectory fie

'1tf~and~

ENTERto--=

1-=1Of1

Mlin

......
I

Go to CarIlla

Go to UtilitY

Goto~

CDnffIpnUcln

Utity Menu

CSectian Sl

Guided
Conftgntlon ......

I
CD to l.iIImDnf

UnkNlN
&elect
CSectIon n

to lJMICIIna
logging

~Sellct

CSecUon oa

CD to·
Network

Transport Menu

Go to Net Con
QidId
Network Interf80e
ConftIpauan

I
GIl tDLbllte

Onb
CDnffIpntlan
QIanga

L- s.otIon 6 ---J

Go to NadIt
Node

Go to Global

Go to GPROT

Go tDNI

NameMni
Section.

GIobII
Transport Data

GonnI
Protocol Mn.I

Intltface SMt

(Sectfon 8)

Network

Add or UDdate
Loopbadc
NIOIta

Add or UDdate
lAN802.3

Add or UDdate

Add_UDdID

Router

GltwwrHllf

NlOIta

MOIta

NlDIta

Figure 5-3. NMMGR Sereen Structure

Configuration Flies
NMMGIl is used to create and modify configuration files. Configuration files are data files with a
hierarchical structure which are file code NCONF. They are created with 2048 32-byte records. The
hierarchical structure, called a template, is provided by NMMGR when the configuration file is created.
Figure 5-4 shows the configuration file template used for NS3000/V network configuration. Note that
this is only a subset of the complete configuration file template provided with NMMGR.; templates are
provided for other HP data communications products, and for the other NI types available with
NS3000/V.
The template defines groups of information, called cells, with identifiers of up to eight characters. The
cells are arranged in a hierarchical structure. When the configuration file is created, some of the ceUs.
called fixed cells, are already identified. In Figure 5-4, uppercase letteR denote fixed cells, such as
LINKCONF.

5-9

The NMS Configurator (NMMGR)
Other ce~ called select cells. need identifiers specified for one or more items that are associated with the
~
cell In Figure 5-4. select cells are shaded. The maximum number of items for each select cell is shown
in square brackets. For example. the number 8 is shown next to the cell called sUBl~' in Figure 5-4.":}
This means you can oonfigure as many as eight logging classes for CLAslItA which is the select cell below
suBIIII You use select screens. described later. to specify identifiers. Thus. the template can be thought
of as a framework that determines the overall structure of the configuration file.
Each cell in the template corresponds to a configuration screen. The hierarchical structure of the
configuration file is provided so that any screen can be accessed by defining its path in the template. A
path is a sequential list of the identifiers used to reach a specific screen. Paths are described in more
detail later in this section.
Data is stored in the configuration file in data records. These data records are' associated with the
appropriate identifiers for the cells marked with an asterisk in Figure 5-4. When the configuration file is
created. its structure is established by the template. but its data records are empty. You use data screens.
described later. to create or modify data records in the configuration file.

5-10

The NMS Configurator (NMMGR)

I
LINKCONF[256]

-:--:1.* (LAN802 .3)
:rRACEDAT·

(ROOT)
I

LOGGING [256]
L.sU8ti_~[8]

LC[Asl§lg*

(specified as @)

NETXPORT
ODE
LNAME·
LOBAL·
PROT
IPU•
PXP*
:rep*
NI [8]

(LAN802. 3 )
PROTOCOL
IP*
PROBE·
LINK[1]
4j~
•
-INTERNET

L.Jj~Nii!.

APPING

Figure 5-4. Example of a LAN Configuration File Template

* Cell with data record

5-11

The NMS Configurator (NMMGR)

USING NMMGR CONFIGURATION SCREENS
From the Main Menu screen you can proceed to the menu used to a~ the screens for manual
configuration. Press ''',.! "~·;·~::~E~lffI~ at the Main Menu screen to display the Configuration screen (Figure
5-5).

Path:
LINKCONF -

Configure LINK MANAGER Subsystem.

LOGGING

Configure LOGGING for all SUbsystems.

NRJE

Configure NRJE Subsystem.

SNANOOE

Configure SNA Subsystem.

NETXPORT -

Configure NETWORK TRANSPORT Subsystem.

APPC

Configure APPC Subsystem.

File:

filename.group.aeet

Figure 5-5. The Configuration Screen

General Operation of Screens
Figure 5-6 shows a generalized NMMGR screen that illustrates the common features of all configuration
screens. It also indicates the features that vary depending on the type of screen. An NMMGR.
configuration screen can be classified as one of three types:
• Menu screen
• Select screen
• Data screen
Menu screens show the fixed cells available on the path below your current level as you traverse the
NMMGR. screens. Select screens are used to specify identifiers for the select cells of the configuration
file. Data screens are used to enter data into the data records associated with cells in the configuration
file. The layout of the fields and the labels of the first six function keys Oabeled .
in Figure

5-12

The NMS Configurator (NMMGR)

5-6) are different for the three types of screens. The rest of the futures (except the data
Figure 5-6 and described below, are common to all three screen types.

f1ag~ shown

Path: LEVEL1.ueereelect.LEVEL3
Layout and function keye (1-6) depend on the type of acreen:

File:

Data fields and definitions for DATA screens

Menu choices for MENU screens

Name select fields for SELECT screens.

filename.group.acct

Figure 5-'. A Typical NMMGR Configuration Sereen

The Reade.- and Message lJnes
The top line of each NMMGR screen is the header, which identifies the NMMGR version number
(A. 02.00) and the screen title. Below the header is the message field, where NMMGR prints errors,
warnings. prompts. and other messages.

Data Flag
On data screens only, the header line also contains the Data Flag, which is shown as " ,.~ followed by I
in Figure 5-6. A II indicates that the data record has been created for that cell of the configuration file;
an II indicates that the data record has not been created. You I'mUt check the data nag to know if the
data record has been created. No data 18 entered into the configuration file until the data record 18 created.

Refer to "Data Sereeu'later in this section.

Patb Name
The path name is shown on each configuration screen in the Path: field. The path name for each screen
consists of all the cell identifien (separated by periods) between the root and the specific cell in a
configuration file. The NMMGR screen structure is similar to the configuration file structure. The root

5-13

The NMS Configurator (NMMGR)
of the configuration file template (Figure 5-4) corresponds to the Configuration Menu in the NMMGR
screen structure (Figure 5-3). Therefore, a path name corresponds to both a cell in a configuration file
and an NMMGR screen. In Figure 5-6, the path name is shown as LEVEL 1•userS8 lect. LEVEL3; where
LEVEL 1 and LEVEL3 indicate fixed cell identifiers and userselect indicates a select cell identifier.

)

me Name
NMMGR displays the name of the configuration file that you are working on in the area called file: at
tbe bottom of each screen. This name is shown as filename. group.acct in Figure 5-6; in practice, the
actual file name entered in the Open Configuration/Directory File screen is displayed. Note that the file
name is not a field; to change your working file, you must use the Open Configuration/Directory File
screen.

Command Window and the Enter Key
Each screen includes a field labeled loiijiij111~1 below the message line. This field, called the command
window, is displayed in half-bright inverse video. NMMGR accepts three types of commands:
• NMMGR commands
• MPE commands
• NMMGR path commands (Direct Path Branching and Brother Branching)
You can type any of the accepted types of commands in the command window and press [ENTERI to
execute the command.
NMMGR Commands. NMMGR provides commands that transfer you to other screens or perform specific
functions. Refer to Table 5-3 for a list of the NMMGR commands. NMMGR recognizes the
unambiguous prefix of any command in Table 5-3. For example, you can enter ER to transfer to the
Error Information screen; you cannot enter E because you might mean EXIT, not ERRORS. The optional
portions of the commands are indicated by brackets.
MPE Commands. You can enter any programmatically executable MPE command in the command
window and preface it with a colon. For example, suppose you want to see if a configuration file is active
before you access it You are already running NMMGR. You could enter the MPE command:

in the command window and press [ENTER I. Your terminal screen is cleared and the information is
displayed. When MPE is finished processing your command, NMMGR prompts you to press lRETURNI to
return to the screen interface. You can process only one MPE command at a time.

NMMGR Path Commands. NMMGR provides two path commands that allow you to transfer freely
among configuration screens that have path names: direct path branching and brother branching.
Direct path branching allows you to enter @pathname in a command window to transfer to the screen
addressed by the path name. Look at the template in Figure 5-4 and find the cell called NAME, near the
upper-right corner of the template. This cell corresponds to a data screen called the Node Name
Configuration screen. To transfer to this screen, you would tyPe the pathname, preceded by an @, in the
command window of any screen. The command window would look like:

5-14

The NMS Configurator (NMMGR)

After pressing [ENTER I, the Node Name Configuration screen would be displayed.
Path names can include both fixed cells and user-specified cell identifiers. In order to use direct path
branching, you must be familiar with the structure of the configuration file for your node. You use an
output utility, described later, to provide a tree structure of your file. You must know all cell identifiers
to specify a correct path name.
Brother Branching. Configuration screens that share a common parent screen are referred to as brothers.
If you are working in a screen with one or more brothers. you can use the NEXT command to transfer to
the next brother screen. This feature is called brother branching_
Look again at the template in Figure 5-4. Notice that the cell NETXPORT in the upper right-hand corner
haa four children (referred to by their path names~ NETXPORT •NODE,
NETXPORT. GLOBAL,
NETXPORT. GPROT, and NETXPORT. NI.
These four screens are brothers.
To transfer to
NETXPORT. GLOBAL from NETXPORT. NODE, you would simply type next on the command line and press
[ENTER I. The command would look like this:

After pressing (ENTERI, the NETX PORT •GLOBAL screen would be displayed. Typing NEXT on the command
line of the NETXPORT. GLOBAL screen and pressing [ENTER I would transfer you to NETXPORT. GPROT. You
could use the same command to transfer from NETXPORT •GPROT to NETX PORT • NI.
The screens are visited in the order their names appear on the parent screen. Typing NEXT at the
command line will transfer you to the next brother as long as one exists. If you try to transfer from the
last brother screen to the first, you will receive an error message telling you that there are no more
brother screens to transfer to.

5-15

The NMS Configurator (NMMGR)
TABLE 5-3. NMMGR COMMANDS
NMMGR Command

Aetion

: HP£COtrrrrlnd

Execute /tIP£COfI'I'Tand /tIP£Conrmnd must be a
programmatically executable MPE command.

COM(PRESS)

Transfer to Compress screen.

CON [FIGURATION]

Transfer to Configuration screen.

or'

5-16

COP[YSUB]

Transfer to Configuration Subtree Copy screen.

ER[RORS]

Brings up Error Information screen.

EX[IT]

Exit from NMMGR.

H[ELP]
or?

Calls up help function. (Refer to uGetting Help"
subsection earlier)

M[AIN]

Transfer to Main Menu screen.

NEX[T]

Transfer to brother screen. (Refer to the subsection
IINMMGR Path Commandsll earlier)

NET[DIR]

Transfer to Network Directory Main screen. Refer to
Section 14 for more information.

NIG[UIDE]

Transfer to Guided Network Interface Configuration
screen. Refer to Section 6 for more information.

NIU[PDATE]

Transfer to Guided Network Update Configuration
Screen. Refer to Section 6 for more information.

NM[MGRCMD]

Transfer to maintenance mode interface. Refer to
section 14 for more information.

OP[EN]

Transfer to Open Configuration/Directory File screen.

OU[TPUT]

Transfer to Output Configuration File screen.

The NMS Configurator (NMMGR)
TABLE 5-3. NMMGR COMMANDS (cont.)
NMMGR Command

Action

P[RIOR]

Same as pressing ~r.~~t:lll~~jli:'i~. See explanation
below.

Q[UIT]

Exit from NMMGR (Same as EXIT.)

R[EFRESH]

Same as pressing RI~!.I~[lill~l.I'. See explanation
below.

STrOp]

Stop Guided Configuration Process. Refer to Section 6
for more information.

SU[BGUIDE]

Transfer to Guided Configuration of Subsystem screen.

U[TILITY]

Transfer to Utility screen.

VA[LIDATE]

Transfer to Validate Configuration File screen.

VE[RSION]

Display version information.

SCreen Fields
You enter data or item names into the appropriate fields in data screens or select screens. You can enter
information only into "unprotected" fields; the rest of the screen is protected against modification. If your
terminal has the required capability, the unprotected fields are easy to identify because they are shown in
half-bright inverse video and appear grey. All half-bright inverse video fields are unprotected fields.
with the exuption of the header and function key labels. Full-bright inverse video fields. which appear
White, are used for display-only information.
On terminals without half-bright inverse video capability, unprotected fields are displayed in fun-bright
inverse video and appear white. For screens with more than one unprotected field, the cursor
automatically moves to the next unprotected field when you reach the end of the present field, or if you
press I 188 I.
Generally, you use the I T8B I key to step through the fields from the top of the screen to the bottom.
For the reverse, the keys to use depend on the type of terminal -- use the ISH I FT)( I8B I keys for
HP 262X terminals, use the ICO_TROLI( T8B I keys for HP 264X terminals. A convenient method of
positioning the cursor at the glllll';~l window is to home the cursor (press the key on your terminal with
the diagonal arrow). For more information, consult your terminal reference manual

5-17

The NMS Configurator (NMMGR)

PrIor Saeen Key
The IB'
._.' key displays the screen most recently displayed 'before the current one. In order to
show the correct screen. NMMGR maintains a prior screen list, which is a sequential list of the screens
that have been displayed. Pressing the Bil~
.::~H key displays the most recent screen in the prior
screen list, and removes that screen from the list. The most recent screen in the list is the screen that was
visited just prior to the current screen, with three exceptions:
• When you display the Error Information screen, NMMGR does not put this screen in your prior
screen list. Thus, pressing 1illJ1~;' ,~;:~~~::~:~~~ never transfers you to the Error Information screen,
even if it wu the latest screen you displayed.
• After reaching the Validate screen in guided configuration, the prior screen becomes the screen
with which you began the guided configuration.
• If you use the command window to return to a screen already visited, NMMGR drops from the
prior-screen list any screens that you visited after this screen. For example, suppose you run
NMMGR; NMMGR displays the Open Configuration/Directory File screen. The prior-screen list
is empty. You open a file and NMMGR displays the Main Menu screen. The prior-screen list
now contains:
Open Configuration/Directory File
You then display the Configuration screen, and the prior-screen list contains:
Main Menu
Open Configuration/Directory File
with the latest screen on top.
You then display the Link Configuration (select) screen, and the prior-screen list contains:
Configuration
Main Menu
Open Configuration/Directory File
You then display an associated Link Configuration data screen ~nd the prior-screen list contains:
Link Configuration (select)
Configuration
Main Menu
Open Configuration/Directory File
If you then use the command window to transfer to the Main Menu screen. NMMGR truncates
the prior-screen list so that it contains only:

Open Configuration/Directory File
Now. if you press
File screen.

5-18

NMMGR transfen you to the Open Configuration/Directory

The NMS Configurator (NMMGR.)
The Error Information screen, described later, does not include a r,~o;r·:·~~!i'-.I key. Instead, it contains
a key labeled ~il~!~;:;i: ..: :~~::t!!, also described later.
[

NOTE

During Guided Configuration. this key is labeled N!~
performs a different function.

,..,,1 and
• ,"F'i

Refresb SCreen Key
All screens include a 1,~:::::l!m! . :::~m~I~~~ key «( r 1 I). You can use this key to redisplay a screen with
current configuration file data. A common use of M
..t~ltimlll~!~i~ is to "clean up" a screen after a
TEll message or other interference has appeared on it. Because NMMGR uses VPLUS/3000 screens, you
must press ~lt:Lg,."'i='" .:~,.,,,.,~~::~~ after a terminal hard reset is I-~rformed and after a terminal power failure.

I CAUTION I
If you make changes to a 8elect screen and press fif~' '!l""::n.
. before
pressing ,;,;, .~~I or one of the other function keys, the identifier that you
entered is cleared and is not entered into the configuration file. As for a
data screen, any changes not saved with il~':'
'i cause a warning to
be displayed in the message line. If you ignore the warning and press
i again or a function key other than
' the
d~ta is not written to the configuration file.
.,1 ,

Menu Screens
Menu screens, such as the Main Menu screen in Figure S- 2, allow you to select an NMMGR function.
the Main Menu screen, for example, three functions are available.

The text in the middle of menu screens describes the functions of the screens to which you can transfer.
Select a screen by pressing the corresponding function key. The function keys available on menu screens
are shown in Table 5-4.

5-19

The NMS Configurator (NMMGR)
TABLE 5-4. MENU SCREEN FUNCTION KEYS
Function
Transfers you to the next screen "below" the current screen. Labels are
dependent on specific screen.
Redisplays screen with current configuration file data.
Displays the most recent screen in the prior-screen list. Refer to the earlier
description of this key for examples.

Select Screens
Select screens allow you to select identifien to add, delete, update or rename. Some select screens also
include a field where you must specify the type of identifier you are selecting. Figure 5-7 is an example
of such a select screen. You must specify a network interface type in addition to a network interface
name. Some of the screens that follow such a select screen depend on the type of network interface you
select.

Type

Network Interface Name
New Name

LOOP,LAN802.3,
ROUTER,GATEHALF
(if new)

Configured Network Interfaces
Name

Type

Name

Type

Figure 5-7. Select Sereen

5-20

Name

Type

The NMS Configurator (NMMGR)
In this screen, the select field is labeled:

Network Interface Name
Item names can contain as many as eight alphanumeric characters, and the first character must be
alphabetic. NMMGR does not differentiate between uppercase and lowercase letters when you enter item
names; it upshifts allietten in item names and stores them in uppercase letters.
The type field in this screen is labeled:

LOOP.LAN802.3.
Type : ROUTER.GATEHALF
(if new)
To delete or update an identifier, enter the name of the item In the select field and press the appropriate
function key. To add, enter the name of the item and its type and press III. Refer to Table 5-5 for a
list of function keys for select screens. If you press ",il! ":= or .18, NMMGR transfers you either to a
data screen so that you can enter or update configuration data for that item. or to another select screen 80
that you can further specify what you want to configure. If yos~ press R~I~", NMMGR asks you to
press ~..
again to confirm. If you do, NMMGR deletes the item specified in the select field and any
data associated with it from the configuration file. NMMGR then confirms that you have deleted the
item by printing the following message in the message field:
'''i

Item deleted.
Below the select field is the rename field. In Figure S-7, the rename field is:

New name
To rename an item, enter the name of the item in the select field and enter the new name in the rename
field; then press the lI~t, :. key. NMMGR confirms that you have renamed the item by printing the
following message in the message field:

Item renamed.

5-21

The NMS Configurator (NMMGR)

TABLE 5-5. SELECT SCREEN FUNCTION KEYS

Key

Funetion
Displays the next set of items.

Displays the previous set of items.

When pressed twice in succession (to confirm deletion), deletes the item
specified in the select field. NMMGR deletes the item and any data
associated with it from the configuration file.
Renames the item specified in the select field with the name specified in
the rename field.
Adds an item to the configuration file, with the name specified in the select
field. Transfers you either to a data-entry screen so you can enter
configuration information for the item, or to a select screen ubelov· the
current screen.
Transfers you either to a data-entry screen so you can update configuration
information about the item specified in the select field, or to a select screen
IIbelow u the current screen.
Redisplays the screen with current configuration file data.

Displays the most recent screen in the prior-screen list. Refer to the earlier
description of this key.

The lower half of a select screen displays, in alphabetical order, names of items that are currently
configured in the file. If your configuration file contains more items than can be displayed in one screen,
you can display the next set by pressing ... ·liP;"!!!!'· ~: .:,," To display the previous set, press .
",

The maximum number of items possible for a select cell is 2S6, but some have lower limits--such as 8 for
the Logling Configuration class select cells (CLASbbbb).

5-22

The NMS Configurator (NMMGR.)

Data Screens
Data screens are used to configure data r~rds for items that r\;"uire data. The cells in Figure 5-4 that
have data records associated with them are denoted with aste.-isks. Data-entry screens allow you to enter
configuration data into unprotected fields. Figure 5-8 is an e1ample of a data-entry screen.
You must press ~~!;''';l;l',: 'i' 'li'r~ to create a data record. Tbe data flag in the upper-right cor~er of each
data screen is set to III only when a data record bas been created. Otherwise, the flag is set to I. Before a
data record is created, any values displayed in the data fields are only recommendations -- they are not
yet part of the configuration file.

Number Of Inbound Buffers
Number Of Outbound Buffers
Number Of Routing Table Entries
Network Hop Count
Idle Device Timeout Value (Minutes)
o = Timer Disabled For All Devices

file: filename.NET.SYS

Figure 5-8. Data-entry screeD

The
!ijji,,,;,,.,:,;,,:1 key is used to add or update information in a data record. The lENTER) key can also
be used to update the data record if the command line is blank. NMMGR. confirms that you have
updated the configuration file by printing the following message in the message field:
!n:

,,!

Configuration data updated.

5-23

The NMS Configurator (NMMGR)
If you enter data in a field and then try to transfer to another screen (by pressing a function key or by
using the command window) before p ressing ~,,:,,''''''
I'f~~t";:~i .,._,;::i~
,-:;;::ji.~ NMMGR p rints:

Warning:

Screen changed. Use UPDATE to save data. (NMGRWARN7)

This warning cautions you against unintentionally leaving a data screen before you have updated the
confiluration file. If you decide you do Dot want to update the configuration file with the data on the
screen, you can ignore the warning and repeat the action to transfer to another screen.

If you enter the wrong type of data in any field and try to update the configuration file. NMMGR prints
an error message corresponding to the first field with invalid data. highlights and underlines the fields
with invalid data, and positions the cunor at the first field with invalid data. For example. suppose you
enter an alphabetic character in a location that must contain an inteler. When you try to update the file.
NMMGR may print:

The field can contain only digits.
The :
key redisplays a data screen. and shows its current configuration file data. Suppose
you have changed some values on a data screen. but then decide to modify these values before actually
entering them into the configuration file. Press '-:';:
P;;;;';"e.n. NMMGR will warn you that the
:.,'::i-I, again; NMMGR refreshes the screen
screen has changed since you last updated it. Press :w~:___
and shows its current configuration file data.
Refer to Table 5-6 for a list of function keys for data-entry screens.

5-24

The NMS Configurator (NMMGIl)
TABLE 5-6. DATA SCREEN FUNCTION KEYS

"
\

Function

Key

Transfers you to the next ICreeD "below" the current screen. Labels are
screen specific.
Displays the next set of itemL

Displays the previuus set of items.

Displays the first set of items. (Function available for Neighbor Gateway
Reachable Networks Screen.)
Displays the last set of items. (Function available for Neighbor Gateway
Reachable Networks Screen.)
Condenses the current set of items. (Function available for Neighbor
Gateway Reachable Networks Screen.)
Writes screen data to configuration file. This key ".,,81 be used to create or
update the data record.
Redisplays screen with current configuration file data.

Displays the most recent screen in the prior-screen list. Refer to the earlier
description of this key.
Appears on some screens; removes data configured on the ICreeD from the
configuration file.

5-25

ne NMS Confiaurator (NMMGR)

USING NMMGR UTILITY SCREENS
The Utility Screen (Figure 5-9) is a menu screen from which you can transfer to the OUtput, Compress.
Validate, or Configuration Subtree Copy ecreena. To display the Utility Screen, you GUl select
at the Main Menu screen, or you can type UTILITY in the command window of any
screen and press IENTER I.

OUTPUT

- Output a configuration file listing to terminal or printer.

COMPRESS

- Compress or eKpand a configuration file.

VALIDATE

- Validate subsystem configuration data.

COpy SUBTREE - Copy Configuration data from file to file.

File:

filename.group.acct

Figure 5-'. Utility Screen
The Output screen allows you to display or print the configuration file tree structure or the data screeM
associated with a configuration file.
The Compress screen allows you to compress or expand the configuration file. which is helpful if you run
out of record splce.
The Validate screen allows you to see if the configuration of a specified subsystem is valid.
The Configuration Subtree Copy screen allows you to copy configuration data from one contiguntion file
to another.
Determine the function you wish to perform and press the corresponding function key.

5-26

The NMS Configurator (NMMGR)

Output Configuration File

The Output Configuration File screen (Figure 5-10) allowf. 10U to list or print the configuration file tree
structure, to print the NMMGR data screens associated with a configuration file, and to print a critical
summary of the configuration file data. Refer to Table 5-7 for a list of funclton keys for this screen.
You may want to issue a file equation for the output file fORMLIST on the command line. For example,
you could type:

:fILE fORMLIST;DEV=PP
If you then pressed 1Wff!~.Jj!u~.:il!lIli the output would be sent to the device PP.
!...
i!;

For another example, you could type:

:fILE fORMLIST;DEV=DISCjSAVE
:::;~&

the output would be stored on disc under the file name FORMLIST.

DISPLAY TREE PRINT TREE

Display configuration file tree structure to terminal.
Print config file tree structure to line printer or FORMLIST.

PRINT DATA

Print data screens to line printer or FORMLIST.
Subsystem 11~:J.f 111!111111 II; r ... ..1
0: All subsystems
3: NRJE
6: APPC
1: LINKCONF
4: SNANODE
2: LOGGING
5: NETXPORT

PRINT SUMMARY -

Print critical summary of data for subsystem
to line printer or FORMLIST.

PRINT SUBTREE -

Print data screens for a subtree to line printer or FORMLIST.
Enter the path of the screen at the top of the subtree:

file:

III

file.group.acct

Figure 5-10. Output Configuration File Screen

5-27

The NMS Configurator (NMMGR)
The tree structure printed by the 1~l."l~:;;Tt7'~ key shows the identifiers that are configured for each cel~
but does not show any data that "is·configured. This key is useful for finding out which identifiers are
already configured in a file, and for guidance in direct path branching, described earlier. To generate a
printed listing of all the data screens In the file, use the ~~;~"~:ii!:J)aia key.
TABLE 5-7. OUTPUT FUNCTION KEYS

Function
Displays the configuration file tree structure to your terminal. Refer to
Figure 5-II for an example.
Prints the configuration file tree structure to the line printer (default
system device LP, or FORMLIST--Formal File Designator). Refer to
Figure 5-11 for an example.
Prints the NMMGR data screens associated with the configuration file to
LP or FORMLIST. By default, output goes to the device LP. Refer to
Figure 5-12 for an example.
Prints critical summary of data for Network Transport to line printer or
FORMLIST. By default, output goes to the device LP.
Prints the NMMGR data screens for a specified Bubtree to LP or
FORMLIST. Default output device is LP.

NMMGR presents the hierarchical structure and data screens of a file by doing a depth-first traversal of
the tree. The cells on each level are presented in the order they were configured.
If you press
.:: ~li::; ItIlll/~H~i PlI~'"];«~' .~"f~ or :~::" .:llj!I!![q~'I: .:~", NMMGR prints the
following message in the message field when it has finished listing the output:

Output listing completed.

Prlnt Tree and Display Tree
Figure 5-11 is an example of a tree structure produced by pressing I;
. ~:~I or .:, n':u:.•"i:::;::':
.
this example, the user has configured a node on an IEEE 802.3 LAN. Thus, the structure corresponds to
that seen in the template in figure 5-4. The level of each cell is printed on the left, in square brackets.
The tree structure shows the identifiers of all the configured cells and items and those of the fixed cells
reachable from the configured cells and items. The entries are indented according to their level in the
tree structure.

5-28

~""'."
}

The NMS Confilurator (NMMGR)

[1] LINKCONF'
(2) LANLINK
[3] TRACEDAT
(1) LOGGING
[2J SUB0003
[3J
CLAS0001
[3J CLAS0002
[3]
CLAS0003
(3]
CLAS0004
[3]
CLASOOOS
[3]
CLAS0006
(1J NRJE
[1] SNANODE
[1 J NETXPORT
[2] NODE
[3]
NAME
(2) GLOBAL
[2J GPROT
[3]
IPU
[3]
PXP
[3]
TCP
[2] NI
[3J
LAN1
[4 ]
PROTOCOL
[5]
IP
[5]
PROBE
[4]
LINK
[5]
LANLINK
[4]
INTERNET
[5]
LANINET
[4]
MAPPING
[5]
LANMAP
Figure 5-11. Example of Confiluration File Tree Structure

5-19

The NMS Configurator (NMMGR)

Print Data
The :.'~:
. :':~::~~ key allows you to print the data screens of a configuration file. If data is present in the
(;Onfiguration file, the actual data is printed on the appropriate data screen, and the Data Fla. is IHowever, where no data is present, the recommended values (screen default values) are printed on the
appropriate data screens, and the Data Flag is ".
Figure 5-12 is an example of a data screen printed by ~t'~6~::ij.~~':

NMMGR/3000 (A.01.00)

GLOBAL TRANSPORT CONFIGURATION

Data: Y

fill in fields and press Update to configure the data for this item.
Command:
Path: NETXPORT.GLOBAL
[LAN1

] Home Network Name

[2][3][1]

Name Search Methods And Order
1 - Network Directory
2 - Probe

[100 ]
[100]
[100]

File:

3 - Probe Proxy
0 - Choice Omitted

Maximum Directly Connected Nodes
Maximum Outbound Destinations
Maximum Inbound Destinations

fllename.NET.SYS
Update
Data

Refresh
Screen

Prior
Screen

Figure 5-1Z. Print Data Screen Example

Prlnt Summary
The , . . . . . ~ji'.: key allows you to print what is known as a critical summary--a listing of screens
and configured field values for your configuration file. The example that follows is a sample critical
summary for a full-gateway node that has been configured with a router NI and a LAN Nt The IP
addresses shown have been reserved for use in examples only.

CRITICAL SUMMARY - NETXPORT CONFIGURATION
CONFIGURATION FILE NAME: NSCONF.NET.SYS
NODE NAME: FLAGSTAFF.ROUTE66.U5A

5-30

The NMS Configurator (NMMGR)

TRANSPORT GLOBAL CONFIGURATION:
Name Search Method: 1. Probe
2. Probe Proxy
3. Network Directory
Maximum Directly Connected Nodes: 100
Maximum Outbound Destinations:
100
Maximum Inbound Destinations:
100
IP UPDATE (IPU) CONFIGURATION:
Maximum Number of Networks in Internet: 64
Maximum Gateway Nodes Per Network:
16
PACKET EXCHANGE PROTOCOL (PXP) CONFIGURATION:
Retransmission Interval (Secs):
10
Maximum Retransmissions Per Request: 4
TRANSMISSION CONTROL PROTOCOL (Tep) CONFIGURATION:
Maximum Number of Connections:
128
Retransmission Interval Upper Bound (Secs):
120
Retransmission Interval Lower Bound (Sees):
4
Initial Retransmission Interval:
4
Maximum Number of Retransmissions:
4
Connection Assurance Interval:
600
Maximum Connection Assurance Retransmissions: 3
CONFIGURED NETWORK INTERFACES:
Network Interface Type:
Network Interface Name:
Network Interface IP Address:
Network Segment Size:
Number of Inbound Buffers:
Number of Outbound Buffers
Number of Store and Forward Buffers:
Maximum Number of Nodes in Network:
PROBE PROTCOL CONFIGURATION:
Proxy Enabled:
NETWORK INTERFACE LINKS:
Link Name LDEV
Link Type
LAN LINK

150

LAN
LANA
C 192.006.001 000
1497

256
256
20
100

Yes
Buffer Size

Line Speed Dial Enabled

LAN LAN802.3

IEEE 802.3 MAPPING:
IP Internet Address

IP SAP

IEEE802.3 Address

(None configured)

5-31

The NMS Configurator (NMMGR)

CONFIGURATION:
Neighbor Gateway Name: NODE2
Reachable Networks:
IP Network Number Hops
C 192.006.250 000

Gateway IP Address: C 192.006.001 001

IP Network Number

Hops

C 192.006.251 000

Network Interface Type:
Router
Network Interface Name:
ROUTE66
Network Interface IP Address:
C 192.006.252 006
Number of Inbound BUffers:
256
Number of Outbound Buffers:
256
Number of Store and Forward Buffers: 20
Number of Route Table Entries:
100
Network Hop Count:
10
DIAL PROTOCOL INFORMATION:
Maximum Retransmissions Per Packet: 2
Retransmission Timeout (Sees):
5
Security On:
Yes
Security Strings:
HP
NETWORK INTERFACE LINKS:
Link Name LDEV
Link Type

---------

NEWMEX
ARIZONA

Line Speed Dial Enabled

------------ ------------------------------1024
56000
Yes

151 SO LAPB
152 DO ATP/ASNP

ROUTER REACHABLE NODES:
Node Name
IP Address
CHICAGO
STLOUIS
OKCITY
AMARILLO
GALLUPNM
WI NOMA
KINGMAN
BARSTOW
SANBERNA
LA

Buffer Size

C
C
C
C
C
C
C
C
C
C

242

Link Name

192.006.252
192.006.252
192.006.252
192.006.252
192.006.252
192.006.252
192.006.252
192.006.252
192.006.252
192.006.252

001
002
003
004
005
007
008
009
010
011

NEWMEX
NEWMEX
NEWMEX
NEWMEX
NEWMEX
ARIZONA
ARIZONA
ARIZONA
ARIZONA
ARIZONA

1200
Adjacent?

Yes
Phone Number

Security
String

Nonadjacent
Nonadjacent
Nonadjacent
Nonadjacent
71-555-555-5555
Adjacent
71-888-888-8888
Adjacent
Nonadjacent
Nonadjacent
Nonadjacent
Nonadjacent

HP
HP
HP
HP
HP
HP
HP
HP
HP
HP

INTERNET CONFIGURATION:
Neighbor Gateway Name: CHICAGO
Reachable Networks:
IP Network Number Hops
C 192.006.253 000

5-32

Gateway IP Address: C 192.006.252 001
IP Network Number Hops
C 192.006.254 000

The NMS Configurator (NMMGR)

Print &lbtree

~_~~""

The
"];MJilB, key allows you to print the NMMGR data screens for a specified subtree. R.efer to
Figure 5-12 for an example of how a data screen is printed.

Compress Configuration File
The Compress screen (Figure 5-13) allows you to compress or expand configuration files. To perform
these functions. you must be the creator of the file.

2048

Current File Size

2028

Number of Free Records

Number of Additional Records
Use a negative value
to contract file
File:

filename.group.acct

Figure 5-13. Compress Screen

Fields
Current file Size
NU.ber

(Display field.) Size of the file, in 32-byte record&

of" free Recorda (Display field.) Number of free records at the end of the configuration file.

Number of" Additional
Records

Enter the number of records that you want to add to the file (positive
integer) or the number of unused records that you want to delete from the
file (negative integer). To simply compress the file, enter 0 (zero). If you
are adding recor~ the file cannot end up containing more than 65,535
records.

5-33

The NMS Configurator (NMMGR)

Default: 0
Range: -32767 to 32767.
The Compress screen can compress, or expand configuration files. NMMGR compresses files before adding
or deleting records, as explained below.
Configuration files initially contain 2048 32-byte records. As you configure items in a file, records are
used sequentially from the begInning of the file. As the file size increases. the number of free records at
the end of the file decreases.
If you delete items from a configuration file, the records are not immediately recovered, and the middle of
your file may contain some unused records. Unused records are not reflected in the Number of F"ree
Records count. If you then compress the file (by specifying 0 for Number of Additional Records
and pressingli~p:5:~I!ml~i~!~~)J all data are stored in a contiguous block of records, and all unused records
are now located at the end of the file. Thus, compressing a file enables you to determine the actual
number of free records in a file before adding or deleting records.

When you press : ; ;i~~~ii!'1~~:~~, NMMGR begins compressIng the file immediately. The terminal is
locked to indicate that NMMGR is not available until finished. When NMMGR. has finished compressing
a file, it prints the following message in the message field:
Configuration file compressed.

NOTE

Compress time is based on the number of entries in the file. For a file that
contains a small amount of data, compression usually takes fewer than 30
seconds. However, compressing a file with a lot of data can take several
minutes.

S-34

The NMS Configurator (NMMGR)

Validate Configuration File
The Validate Configuration File screen (Figure 5-14) allows you to test the validity of a specified
subsystem configuration.

111111 Output to line printer or VALILIST in addition to terminal
(V for VES, N for NO)
VALIDATE NETXPORT

File:

- Validate NETXPORT configuration data.

filename.group.aeet

Figure 5-14. Validate Configuration File ~reen

At present, you can specify only the Network Transport subsystem for validation. The purpose of the
validation process is to ensure that your configuration data is syntactically and logically correct before
you activate the node. The Link configuration must be complete before you attempt to validate the
Network Transport configuration. This is because the Network Transport validation process uses Link
configuration data.
The validation process creates a listing of error messages to pinpoint invalid items. One possible message.
for instance. states that a phone number has not been configured for a Dial-type link. When you press
the i~;.
: : : , ,;':"",,;,:~ key you enter character mode, in which validation errors are listed at your
terminal If you want the listing to be sent to a device in addition to your terminal, change the value to I
in the box next to Output to VALILIST in addition to terminal on the Validate Configuration
File screen. You can have the listing sent to disc or a printer by setting a file equation, or you can have it
routed to the default device. which is LP.

5-35

The NMS Configurator (NMMGR)
After viewing the messages, if any, press (RETURN) to go back to block mode. The message near the top of
the Validate Configuration File screen now tells you if the validation process has completed and, if BO, if
the configuration is valid. It is possible you will see a message indicating that the validation routine never
took place, possibly due to a load error or internal errors. Yeu must see the following message to be sure
that your configuration file is valid:

)

Validation completed; configuration of the selected subsystem is valid.
If you do not see the above message, you see one of these messages:

Validation completed; configuration of the selected subsystem is not valid.
Internal errors occurred during validation.
Cannot invoke subsystem validation routine.
Remember to refer, whenever necessary, to the NS3000/V Error Message and Recovery Manual. If you
encounter errors that you cannot resolve, notify your UP representative.
The following items are checked during the validation procedure.
• These paths must exist:

LINKCONF'
NETXPORT
NETXPORT.GLOBAL
NETX PORT. NODE
NETXPORT.NODE.NAME
NETXPORT. GPROT. TCP
NETXPORT.GRPOT.PXP
NETXPORT.GPROT.IPU
NETXPORT.NI
• Paths expected to have a defined data length are checked. These include:
A path which contains data that should not contain data.
A path which does not contain data that should contain data.
A path which has an incorrect data length.
• At least one NI must be configured for each node. (NETXPORT .NI .niName)

5-36

The NMS Configurator (NMMGR)
• The TCP retransmission lower bound must be less than the TCP retransmission upper bound.
(HETXPORT •GPROT •TCP)
• The TCP initial retransmission timer must be in the range of the lower and upper bound
retransmissions timers. (H ETX PORT •GPROT •TCP)
• An unknown path will cause a validation error.
• If
the
number
of
internet
reachable
networks
configured
for
an
NI
(HETXPORT .NI .niName. INTERNET .gatewayn) is greater than the configured maximum number
of networks in the catenet (NETXPORT. GPROT • I PU), routing information will exceed the allocated

space in the routing tables.
• If the number of internet gateways for an NI (NETXPORT. HI .niName. INTERNET) is greater than
the configured maximum number of gateways in the network (NETXPORT .GPORT. IPU), routing

information will exceed the allocated space in the routing tables.
• If the number of mapping entries for a router NI (NETXPORT.NI.niName.INTERNE11 is greater
than the number of routing table entries for that NI (NETXPORT. HI .niName for Routed, there
will be insufficient space in the routing tables.
• For Router mapping entries:
The link name must be configured for that NI
(NETXPORT. HI .niName. LINK for Router, and LINKCONf).
The IP network address must mat.ch that Nfs network
number (NETXPORT .NI .niName. PROTOCOL. IP).
If Local and DIAL is enabled for the link, there must be a phone number
(in the screen NETXPORT .NI .niName.MAPPING.nrzpentry).
If Local and DIAL is enabled for the link, and Security is enabled in
dial protocol, there la1ust be a security
string (NETXPORT. HI .niName.MAPPIHG.nrzpentrll).
The wildcard address, u@u, is allowed only when a single link is configured
for the network interface (NETXPORT. NI .niName. LINK).
When the wildcard address is configured, exactly two router mappings
must be configured for the network interface
(NETXPORT .NI • niName. MAPPING).
There can be at most one mapping entry with the wildcard address
configured for each router NI.
• The network address of an internet gateway must be the same as that Nl's IP network address.

5-37

The NMS Configurator (NMMGR)
• For each NETXPORT. HI .niName. LINK entry:
The corresponding LINKCONF link must be configured
(LINKCONF. l inkname).

If the network interface type is LAN802. 3, the link type
must be LAN and the link name must correspond
to a LAN 802. 3 link from LINKCONF.
If the link entry corresponds to a Bisync link from LINKCONF,
the link-entry type must be Direct Dial or Shared Dial.
If the type is Direct Dial or Shared Dial
(NETXPORT. NI • niName. LINK), the corresponding
LINKCONF entry must have
phone data configured (LINKCONf .linkname. PHONEDAT).

If the type is Direct Connect, the corresponding LINKCONF
entry must not have phone data configured.
If the type is Direct Dial or Shared Dial. and DIAL is enabled
for the link, then the Dial Protocol must be configured.
If the type is Direct Dial or Shared Dial and the LINKCONF type
is ATP/ASNP, the LINKCONF subtype must be either modem
or European modem.
• If Dial Protocol is configured and security is enabled, there must be a security string c;onfigured
(NETXPORT. niName. PROTOCOL. DIAL. SECURITY).

• A home network must be configured if there is a Gatehalf type Nt, and the home network must
not correspond to the Gatehalf NI or a Loopback NI.
• If Proxy is enabled, and the inbound Proxy multicast address is not present in the c;onfiguration
file, then a validation warning message will be printed. See the NS3000/V Error Message and
Recovery Manual for further details.
• If a LAN NI is configured and the Probe multicast address is not present in the configuration file.
then a validation warning message will be printed. See the NS3000/V Error Message and
Recovery Manual for further details.

• If a node has two or more Nls or a router NI with two or more links, and if no IP
store-and-forward buffers are configured, then a validation warning message will be printed.
See the NS3000/V Error Message and Recovery manual for further details.
• If there is a Router-type NI, then there must be one or more configured mapping entries.
• For LINK.CONF LAP-B entries:
-The T I timer parameter should be greater than or equal to the recommended formula value:
400[(Buffer Size * 8) / Baud Rate]--in hundredths of a second.
-The maximum number of reads and writes must always be 3 in the data record.
-The line speed must not be zero.

5-38

The NMS Configurator (NMMGR)
• The IP Network number for the NETXPORT. HI. niName. MAPPING entry must be the same as the
IP Network number for that NI.
• If Proxy is not enabled on the Probe Protocol Screen ('.nd the inbound Proxy multicast address is
present in the configuration file. then a validation warning message will be printed. See the
NS3000!y Error Messa,e GIld Recover, Manual fur further details.
• Subsystem 3 logging must be configured) anti at least one logging class must be configured under
subsystem 3.

5-39

The NMS Configurator (NMMGR)

Configuration Subtree Copy
The Configuration Subtree Copy Screen (Figure 5-1 S) allows you to copy specified parts of a
configuration subtree into either the same configuration file or a different configuration file. The target
file can be on a remote node in the network.

Source file:
Source path:

Destination file l!
~stina~ion

path:

Overwrite existing subtree
File:

!lllml

filename.group.acct

Figure 5-15. Configuration Subtree Copy Screen

Description
This screen is used to copy the subtree which begins at the end of the source path. to a subtree which
begins at the end of the destination path. The user starts the copy by pressing [71 I.

Fields
Source file

This field contains the name of the file where configuration data
will be copied from. If this field is left blank, the current
configuration file that is open in NMMGR is assumed.
If the file is on a remote node. you must use a file equation, and
prefix the file name with an *. You may use an MPE command
from the command line to set a file equation without having to
leave NMMGR.

5-40

The NMS Configurator (NMMGR)

Source Path

The source path t a required field t is composed of eight NMMGR
path identifier slots. Enter one path identifier in each slott leaving
blanks at the end of each identifier. Leave any unused identifier
slots empty.

Destination file

This field contains the name of the file the configuration data will
be copied to. If this field is left blank, the current configuration
file that is open in NMMGR is assumed.
If the file is on a remote node, the user must use a file equation, and
prefix the file name with an *.

Destination Path

The destination path is also composed of 8 path identifiers. You
need to enter only those identifiers that are different from the
source path. To copy data from the source file to the identical
location in the destination file, leave this field blank. If you wish to
change the fifth path identifier, then the fifth slot in the
destination path should contain data. Only user-selected names can
differ among corresponding identifiers in the source and destination
paths. User-selected types must match. For example, if the source
path includes a direct connect link, the corresponding identifier in
the destination path must also be a direct connect link.

Overwrite existing subtree

This required field indicates whether or not existing data in the
destination configuration file is to be overwritten when the copy is
performed. A Y will overwrite the data, an N will not allow the copy
to continue if data exists where the destination subtree starts. The
default is N.

NOTE
To perform a copy within the configuration file (which was opened by
NMMGR), leave both the source and destination fields blank.

Example
In this example, a subtree copy is being performed from node A to node B. Since the copy is being made
to a remote node, the user must make a : DSLINE connection to node B, and set up a file equation to
represent node B's configuration file. These steps are shown below. They are shaded because you would
see them in inverse video on the screen.

The source file and path on node A are entered into the Source file and Source path fields. They appear
below.

Source file:
~th:
~.
Wiifi~~

Sourc:e

5-41

The NMS Configurator (NMMGR)

The diagram in Filure 5-16 shows the subtree specified by the path above.

SOURCE: before and after copy (node A)

NETXPORT

I
I
LAN1
I

INTERNET

LINK

LINKABC

GATE 1

GATE 2
Figure 5-16. Source Subtree

For this copy, the destination file and path were specified as below:

Destination file

lEi·

Destination path:
The diagram in Figure 5-17 illustrates the results of the copy.

DESTINATION: before copy (node B)

DESTINATION: after copy (node B)

NETXPORT

I
I
LAH2
I

I
I
LAN2
I

LINK

LANLINK

INTERNET

LINK

INTERNET

LAN lINK

GATE1
Figure 5-17. Destination Subtrees Before aDd After Copy

5-42

GATE2

The NMS Configurator (NMMGR)
When subtrees contain several records, copies that occur over : DSL I NE connections will take considerably
longer than copies between two local configuration files. I· IS several tImes faster to DSCOPY the
configuration file to the destination node, and then perfe.m t.he subtree copy between two local
configuration files.
NOTE

If you are performing a subtree copy with a remote file which is locked by
the network transport on the remote system, you will not be able to access
this file remotely. However, you can log on to the remote system to copy
subtree data. It is not possible to directly copy between two configuration
files on different systems which are both locked open. In this case, the steps
you would take to copy remote configuration data to a local configuration
file are: 1) Log on to the remote system. 2) Run NMMGR and create a new
configuration file, which we will call CONFIG 1 for purposes of this
discussion. 3) While running NMMGR on the remote system, copy the
desired subtree into CONFIG 1. (If you are unable to copy data, the file may
have been opened for exclusive access only, or the network transport may
be performing a validation on the file. 4) Exit NMMGR. 5) Return to the
local system. (At this point, you may wish to DSCOPY the new file back to
the local system so that you can perform a fast Bubtree copy into the
destination file.) 6) Run NMMGR on the local system, and open the file
into which you want to copy data. 7) Still in NMMGR, copy subtree data
from CONFIG 1 into your destination file.

The Error Information Screen
The Error Information Screen displays the last error that NMMGR encountered and associated error
messages. if any. It does not display the prompts that are a result of entering invalid data types in fields.
This screen is displayed when you type ERRORS in the command window of any screen and press IENTER I.
Figure 5-18 shows an example of an Error Information Screen; Table 5- 8 provides a description of the
Error Information SCreen function keys.

r
5-43

The NMS Configurator (NMMGR)

The moat recent sequence of errors is:
Cannot compre88 NM configuration file.

(NMGRERR 24)

Unable to rename old datafile prior to replacement.
USER IS NOT CREATOR

File:

(NMFSERR 27)

(FSERR 94)

SAMPCONF.NET.SYS

Figure 5-18. Error Information kreen
Figure 5-18 shows the error messages displayed on the Error Information screen if a user who was not the
creator of SAMPCONF. NET. SYS tries to compress the file.

5-44

The NMS Configurator (NMMGR)
TABLE 5-8. ERROR INFORMATION FUNCfION KEYS

Key

Function
Redisplays screen with current configuration file data.

Leaves the Error Information Screen and returns to the screen from which
you called the Error Information Screen.

In most cases, you do not need to use the Error Information Screen because NMMGR error messages
displayed on other screens usually contain enough information for you to correct the error and continue
operation. However. if you do not know the cause of the error. or if a more serious error is encountered.
use the Error Information Screen to see if any other error messages are associated with the NMMOR
error. As many as five levels of error messages can be displayed in the Error Information Screen.
depending on where the error occurred in the software. The hierarchy of erron returned by NMS is
shown in Figure 5-18. The top level is the NMMGR error message. and the other levels come from
software accessed by NMMGR.

~
...
'

5-45

The NMS Configurator (NMMGR)

COPYING CONFIGURATION DATA
NMMGR features a configuration file copy utility named COPYCONF. COPYCONF' allows you to perform
same kinds of copies you would execute from the Configuration Subtree Copy screen. Since it can be

~he

invoked from a stream file, you can use it to transfer configuration data to multiple nodes automatically.
Note that this utility is accessed through maintenance mode. Maintenance mode is discussed in Section
14.
The syntax is shown below.
Syntax:

COPYCONF spath:sfilename, dpath:dfilename [;KEEP]

Parameters
spath:sfilename

dpath:dfilename

The path to the beginning of the subtree to be copied from, and the name
of the file in which it resides. The path is composed of up to eight
NMMGR path identifiers. Enter the NMMGR path identifiers that will
lead to the beginning of the subtree to be copied. The file name must be
separated from the path by a colon and must be specified in
filename.group.account form, or, in place of the file name, an asterisk
can precede a formal designator to specify a file equation.
The path to the beginning of the subtree to be copied to, and the name of
the file in which it resides. The destination path is also composed of up to
eight NMMGR path identifiers. Enter the NMMGR path identifiers that
lead to the beginning of the destination path. The file name must be
separated from the path by a colon and must be specified in
filename.group.account form. or, in place of the file name, an asterisk
can precede a formal designator to specify a file equation.
NOTE

All type select parameten in the path that
specifies the root of the subtree to be copied
must be of the same type for the source and
destination configuration files. If they are
not, an error will be flagged, and no copy win
take place.

KEEP

(Optional.) A parameter that prevents the copy if it would overwrite
existing data.

~"')
,.

•.

The NMS Configurator (NMMGR)
NOTE

If you do not specify this parameter, and data
exists in the ~ubtree specified, it will be
overwritten.

When subtrees contain several records, copies that occur over DSLINE connections will take considerably
longer than copies between two local configuration files. It is several times faster to DSCOPY the
configuration file to the destination node, and then perform the subtree copy between two local
configuration files.

Example
The example in "Configuration Subtree Copy" is used again to ilhd.t.rate how the same subtree copy would
be performed using the COPYCONf command. Again, the: DSLINE connection and file equation would be
prepared as seen below.

The COPYCONF command would be entered all follows, at the prompt NMMmlil

To see an illustration of the source subtree, see Figure 5-16. To see the destination subtree before and
after the copy has taken place, see Figure S-1 7.

5-47

The NMS Configurator (NMMGR)

MAKING CONFIGURATION CHANGES
As mentioned earlier in this section. the network transport permits on-line reconfiguration of mapping
and internet information but does not permit configuration changes to non-reconfigurable items while
the transport is active. Special guided configuration options have been provided in order to permit
on-line changes on allowable items.
This subsection describes a method for handling both on-line and off-line configuration changes
network operation is mInimally interrupted.

that

The basic approach is to create a configuration file that is used for making all configuration changes. We
will refer to such a file as NSCONfM. NET. SYS. When the transport requires reconfiguration) changes can
be made to NSCONfM, then copied into the NSCONf •NET. SYS file. If you are making changes to mapping
and internet information only, you can perform the file copy while the transport is active; if you are
making more extensive changes. you first must deactivate the transport.
"1;;~:~~~g key. Then) assuming you
To create an NSCONfM file, simply run NMMGR and use the ~;~~.
already have an NSCONF file, you can use the subtree copy facility from the Utility screen to copy
network transport data (NETXPORT, LINKCONF and LOGGING branches) from NSCONf •NET .SYS to
NSCONfM. NET. SYS.

Once NMCONfM contains the complete transport configuration, use the Netxport Update branch of Guided
Configuration to modify mapping or internet data; use the Netxport Configuration branch of Guided
Configuration to make more extensive changes. Be certain to validate your configuration.
If you make mapping and internet configuration changes only, run NMMGR with a command file to copy
these subtrees into your active configuration file. For example. a UDC could be written as such:
ONLINECHANGES
(udc name)
rILE NMMGRCMD=
RUN NMMGR.PUB.SYS
RESET NMMGRCMD
NETCONTROL UPDATE=INTERNET;NET=niName
NETCONTROL UPDATE=MAPPING;NET=niName
The command file should contain statements for each network interface. An example of a command file
is shown below. Also, niName above should be replaced with the name of the desired network. For
simplicity, one command file could be written to copy the mapping and internet data for all networks,
even if changes occur to only one network. While the transport is active) LAN and Gatehalf network
interface types permit internet reconfiguration; router network interface types permit internet and
mapping reconfiguration.
The following sample command file contains typical COPYCONF commands showing how internet and
mapping information could be copied from NSCONFM. NET. SYS to NSCONF. NET. SYS. For readability,
each command is broken into two lines, but NMMGR requires that the entire command be shown on a
single line in your command file.
COPYCONF NETXPORT.NI.niname.INTERNET:NSCONfM.NET.SYS,
NETXPORT.NI.niname.INTERNET:NSCONf.NET.SYS
COPYCONF NETXPORT.NI.niname.MAPPING:NSCONfM.NET.SYS,

5-48

The NMS Configurator (NMMGR)

NETXPORT.NI.niname.MAPPING:NSCONF.NET.SYS
EXIT

If more extensive changes must be made, it is easiest to replace the entire configuration file. For example,
if you have finished making changes to the NSCONFM file with NMMGR, the changes will take effect
when the following commands are executed:
OFF'LINECHANGES (udc name)
NETCONTROL STOP
PURGE OLDCONF'.NET.SYS
F'COPY F'ROM=NSCONF'. NET. SYS; TO=OLDCONF' • NET. SYS; NEW (backup copy)
PURGE NSCONF'.NET.SYS
F'COPY F'ROM=NSCONF'M. NET. SYS; TO=NSCONF • NET. SYS; NEW (move into place)
NETCONTROL START;NET=niNamel
NETCONTROL START;NET=niName2 (etc.)

The reason for making a backup copy of the existing NSCONF file is that the backup copy can be used if
you ever need to go back to your original configuration. Be aware that you cannot FCOPY a configuration
file if you are still making changes with NMMGR. To quickly exit NMMGR, type "q" in the command
window and press (ENTER J.
NOTE

Each time subtrees overwrite existing subtrees, the amount of available
space within the configuration file becomes smaller. If you are frequently
reconfiguring your mapping or internet data, you may want to expand the
NSCONF and NSCONFM files to avoid running out of available file space.
The Compress function within the Utility screen of NMMGR can be used
to change the size of a file; in addition, it removes inactive subtrees left by
prior subtree copy operation. A file cannot be expanded while it is open.
If your operators are accustomed to making on-line changes on their own,
they should follow set procedures like those listed above. This way, you can
avoid situations where on-line changes might be made directly to NSCONF,
then subsequently overwritten with a potentially out-of-date NSCONfM
file.

5-49

.~
"~.

L...--G_U_I_DE_D_C_O_N_F_IG_U_R_A_T_IO_N

Guided Configuration is an NMMGR procedure that automates significant portions of the configuration
process. Guided Configuration assumes and supplies default values wherever possible to furnish most of
the configuration file's data. You are then led through a predetermined sequence of configuration screens
and asked to supply a minimal number of specific field values to complete the network interface being
configured or the online configuration changes. Each configuration sequence finishes with the Validation
screen, in which the configured data is checked for logical and Internal consistency. NMMGR will
indicate the presence, nature, and location of any errors found, and will indicate whether or not the
configuration is valid accordingly.
The required values for the Guided Configuration screens can be supplied directly from the Configuration
Worksheets (refer to Section 3 and Appendix A), which should be completed before attempting any new
network configuration. Fields for which you are required to supply values are distinguished from
defaulted fields by underlining, as follows:

[-------~].
The Guided Subsystem Configuration Screen is reached by selecting oo:!Hmfl!~GUIRD from the Main Menu
screen (refer to Figure 5-2). Figure 6-1 shows the Guided SUbsyste~'C~~i'ig~'~;i'i~~ Screen.

NETXPORT CONfIGURATION - Network Interface Configuration.
NETXPORT UPDATE

File:

- Online Configuration Changes.

fILENAME.NET.SYS

Figure 6-1. Guided Subsystem Conflauration

6-1

Guided Configuration
NOTE

HP strongly recommends that you use Guided Configuration to initially
configure each node, and for most network maintenance and updating. Use
manual configuration only if Guided Configuration does not provide access
to the configuration data you need to change.
Guided configuration comprises two branches: NETXPORT CONFIGURATION and NETXPORT UPDATE. The
first of these two branches, NETXPORT CONFIGURATION, allows you to create or modify the configuration
file for all network interface types:
• Loopback (labeled LOOP)
• IEEE 802. 3 (labeled LAN802. 3)
• Router--two kinds of guided configuration exist for router networks. One kind (labeled
PC ROUTER) is for a router network consisting of an HP 3000 with Asynchronous SERIAL
Network Links to personal computers. The other kind (labeled ROUTER) is for a router network
with only HP 30005.
• Gateway half (labeled GATEHALF)
The sequence of screens that you will encounter as you proceed through guided configuration for each of
these network interfaces includes the screens necessary for link and network transport configuration, and
validation of the completed configuration file.
The second branch of guided configuration, NETXPORT UPDATE, provides a guided configuration interface
for the following two types of online configuration changes (changes that you can make to an active file~
• Updating internet data for network interfaces (labeled UPDATE I NTERNEn
• Updating mapping data for router network interfaces (labeled UPDATE ROUTER MAPPING)
The top three levels of the Guided Configuration tree are shown in Figure 6- 2.

6-2

Guided Configuration

GUIDED
CONFIGURATION

HETXPORT
UPDATE

NETXPORT
CONFIGURATION

LOOP LAN802.3 ROUTER GATEHALF

ROUTER

UPDATE
INTERNET

UPDATE
ROUTER MAPPING

Figure 6-2,. Guided Confiauration Tree

NOTE

The ROUTER branch and the PC ROUTER branch of Guided Configuration
are similar; however, the PC ROUTER branch is designed for configuration
of a router network specifically composed of personal computen connected
to the HP 3000 via Asynchronous SER.IAL Network Links. The defaults
imposed by using the PC ROUTER branch are those that HP recommends for
such a network, and they differ from the defaults imposed by using the
ROUTER branch. In addition, using the PC ROUTER branch allows you to
bypass certain screens included in the ROUTER branch, such as those
required to configure internet data, since no transparent internet
communication can be initiated from or directed to personal computers.

6-3

Guided Configuration

CORRECTING CONFIGURATION ERRORS
Beyond the Configuration or Update level of the configuration tree, Guided Configuration is forced to
proceed in a forward sequence. The
$~reen key, which is common to most screens in the normal
configuration process, is disabled. Furthermore, while in Guided Configuration, you will not be able to
branch to other configuration screens by specifying their path in the command line. These restrictions are
necessary to enable the configuration to be completed in an orderly and directed fashion.

'P:rio'r

If it is necessary to leave NMMGR altogether before the configuration is completed, issue the EXIT
command in the command line and press {ENTER I. You will be warned that you are in the middle of
Guided Configuration, and asked to repeat the command if you still want to exit. Exiting in the middle of
Guided Configuration will result in an incomplete and unvalidated configuration file.
If you have started a configuration and find that you have made a mistake, type STOP on the command
line and press (ENTER). Guided Configuration will stop. Then, by typing @NIGUIDE and pressing (ENTER),
you can restart the Guided Configuration, fixing any errors on screens you revisit.
If errors occur during validation, a path name will be displayed as part of the error message, identifying
the data screen where the error has apparently occurred. Note (or print out) the screen path name(s). Press
the .:'::::
,]~;~~~ key to return to the Guided Configuration screen where you started. Re-enter your
network inierface'·'name and press the corresponding function key. This will allow you to go back and fix
any errors in the configuration you just created. You also have the option of using direct branching to
visit the screens on which the validation routine reported errors.
If internal errors or errors that prevent Guided Configuration from continuing occur, you will be
returned to your initial Guided Configuration screen and an error message will be printed. Type ERRORS
in the command window and press (ENTER I to see other possible errors. The problem in most cases is
either that the configuration file is locked or that a file is not properly installed. One situation that
would cause a file-locking error is if you tried to update information other than internet data or router
mapping data while the transport still was active. In this case, you should follow the procedures in
Section S for making configuration changes. As for installation errors, you can check these by running
NMMAINT. PUB.SYS ;PARM=24. For NMMAINT information, refer to Volume II, Section 2.

6-4

Guided Configuration

NETXPORT CONFIGURATION
The Netxport Configuration branch directs the gUIded conhgur& rion of loopback, LAN, router, gateway
half, and PC router networks. This branch can also be used to modify any of these networks in an existing
configuration file. NetxPOrt Configuration is reached by selecting ~~li~~l~~_ from the Guided
Subsystem Configuration screen shown in Figure 6-1. The network interface selection is made from the
Guided Network Interface Configuration screen shown in Figure 6- ~

Network Interface Name li~:...l'~lrnll~l!~~!mmmj,~
LOOP

Guided Configuration Of lOOPBACK.

LAN802.3

Guided Configuration Of Local Area Network.

ROUTER

Guided Configuration Of Router.

GATEHALF

Guided Configuration Of Gateway Half.

PC ROUTER -

Guided Configuration Of ASNP Route,· For Pes.

NOTE: Be certain to use uNETXPORT UPDATE" to reconfigure an active network.
File:

FILENAME.NET.SYS

Figure 6-3. Guided Network Interface ConfiguratioD
You must supply a name for the network interface, and then select the type of network interface by
pressing the corresponding function key i f J I to Its I. If you want to modify an existing network
interface, you ean review the configured network interface names by typing 'NETXPORT.NI in the
command line and pressing I ENTER I. When you are finished. press the ..
.~I key to return to the
Guided Configuration screen. If you are configuring a new network interface. Guided Configuration
immediately begins suppl)'ing appropriate default values to the configuration subsystems. Guided
Configuration then proceeds to the screen sequence relevant to the type selected.
Tables 6-1 through 6- S show the sequence of steps for each of the five Guided Network Interface
Configuration routines. For each step. the tables show the sereen or screens a~ssed and the fields for
which you must supply a value. The table also provides a reference figure for each step. You must refer to
that figure to see the actual screen displal and read the detailed descriptions of the required fields in that
screen.

6-5

Guided Configuration

TABLE 6-1 NETXPORT CONFIGURATION - LOOPBACK NI

Step
1

6-6

Screen Name
GUIDED NETWORK
INTERFACE
CONFIGURATION

Required Values
NIName

Reference
Figure 6-3
(p. 6- 5)

(Choose LOOP)

NODE NAME
CONFIGURATION

Local Node Name

Figure 8-3
(p. 8-5)

VALIDATE
CONFIGURATION FILE

None

Figure 5-14
(p. 5-35)

Guided Configuration
TABLE 6-2 NETXPORT CONFIGURATION - LAN 802. 3 NI
Step

Screen Name
GUIDED NETWORK
INTERFACE
CONFIGURATION

Required Value
NIName

Reference
Figure 6-3
(p. 6- 5)

(Choose LAN 802. 3)

NODE NAME
CONFIGURATION
(Visited only if not
previously configured)

Local Node Name

Figure 8-3
(p. 8-5)

LINK CONFIGURATION

Link Name

Figure 7-1
(p. 7-4)

LINK DATA

LDEV /I

Figure 7-2
(p. 7-6)

PROBE PROTOCOL
CONFIGURATION

Proxy Enabled

Figure 9-4
(p. 9-10)

IP PROTOCOL
CONFIGURATION

IP Internet Address

Figure 9-3
(p. 9-7)

NEIGHBOR GATEWAYS
(Repeat for each gateway;
NEXT SCREEN to continue
to Step 9)

Gateway Name

Figure 9-7
(p. 9-18)

NEIGHBOR GATEWAY
REACHABLE NETWORKS
(Repeat for each network;
NEXT SCREEN to return
to step 7)

Neighbor Gateway IP
Internet Address
IP Network Address
Number of Hops

Figure 9-8
(p. 9-19)

VALIDATE
CONFIGURATION FILE

None

Figure 5-14
(p. 5-35)

6-7

Guided Configuration

TABLE 6-3 NETXPORT CONFIGURATION - ROUTER NI

.~
Step
1

Screen Name

GUIDED NETWORK
INTERFACE
CONFIGURAnON

Required Values
NI Name

Reference
Figure 6-3
(p. 6-5)

(Choose ROUTER)

NODE NAME
CONFIGURATION
(Visited only if not
previously configured)

Node Name

Figure 8-3
(p. 8-5)

LINK CONFIGURATION
(Repeat Steps 3-6 for each
link; NEXT SCREEN to
continue to step 7)

Link Name
Protocol Type

Figure 7-1
(p. 7-4)

LINK CONFIGURATION:
LINK DATA

LDEV II

Figure 7-6 (Bisync)
(p. 7-11)
Figure 7-9 (LAP-B)
(p. 7-19)
Figure 7-12 (ASNP)
(p. 7-27)

ROUTER NETWORK
INTERFACE LINKS

Link Name
Connection Type

Figure 10-6
(p. 10-17)

DIRECT CONNECT LINK
CONFIGURATION

None

Figure 10- 7 (Direct)
(p. 10-19)

or
Figure 10- 8 (Dial)
(p. 10-21)

ROUTER DIAL LINK
CONFIGURATION

6-8

ROUTER NETWORK
INTERFACE
CONFIGURATION

Network Hop Count
Idle Device Timeout

Figure 10-1
(p. 10-3)

IPPROTOCOL
CONFIGURATION

IP Internet Address

Figure 10-3
(p. 10-8)

ROUTER MAPPING
CONFIGURATION
(Repeat as applicable; NEXT
SCREEN to continue to step
11)

Router Node Name

Figure 10-12
(p. 10-30)

Guided Configuration
TABLE 6-3 NETXPORT CONFIGURATION - ROUTER NI (cont.)

Step

Screen Name

Required Values

Reference

R.OUTER. REACHABLE
NODES

IP Internet Address
Link Name
Adjacent/Non -adjacent
Phone # (if applicable)

Figure 10-1 3
(p. 10-32)

NEIGHBOR GATEWAYS
(Repeat for each gateway;
NEXT SCREEN to continue
to step 13)

Gateway Name

Figure 10-9
(p. 10-24)

NEIGHBOR GATEWAY
REACHABLE NETWORKS
(Repeat for each network;
NEXT SCREEN to return
to step 11)

Neighbor Gateway Internet
Address
IP Network Address
Number of Hops

Figure 10-10
(p. 10-25)

VALIDATE
CONFIGURATION FILE

None

Figure 5-14
(p. 5-35)

6-9

Guided Configuration
TABLE 6-4 NETXPORT CONFIGURATION - GATEHALF NI

Step
1

Screen Name
GUIDED NETWORK
INTERFACE
CONFIGURATION

Required Values
NIName

Reference
Figure 6-3
(p. 6- S)

(Choose GATEHALF)

GLOBAL TRANSPORT
CONFIGURATION

Home Network Name

Figure 8-4
(p. 8-7)

NODE NAME
CONFIGURATION
(Visited only if not
previously configured)

Local Node Name

Figure 8-3
(p. 8- 5)

LINK CONFIGURATION
(Repeat steps 4-7 for each
link; NEXT SCREEN to
continue with step 8)

LInk Name
Protocol Type

Figure 7-1
(p. 7-4)

LINK CONFIGURATION:
LINK DATA

LDEV II

Figure 7- 6 (Bisync)
(p. 7-1 J)
Figure 7-9 (LAP-B)
(p. 7-19)
Figure 7-12 (ASNP)
(p. 7-27)

GATEWAY HALF
NETWORK INTERFACE
LINKS

Line Name
Connection Type

Figure 11-6
(p. 11-16)

DIRECT CONNECT LINK
CONFIGURATION

None

Figure 11-7 (Direct)
(p. 11-17)

GATEWAY HALF DIAL
LINK CONFIGURATION

Phone Number

Figure 11 - 8 (Dial)
(p. 11-19)

GATEWAY HALF
NETWORK INTERFACE
CONFIGURATION

Idle Device Timeout Value

Figure 11-1
(p. 11-3)

IPPROTOCOL
CONFIGURATION

IP Internet Address

Figure 11-3
(p. 11-7)

6-10

Guided Configuration

TABLE 6-4 NETXPORT CONFIGURATION - GATEHALF NI (cont.)
Step

Screen Name

NEIGHBOR GATEWAYS
(Repeat for each gateway;
NEXT SCREEN to continue
to step 12)

Gateway Name

Figure 11-9
(p. 11-23)

NEIGHBOR GATEWAY
REACHABLE NETWORKS
(Repeat for each network;
NEXT SCREEN to return
to Step (0)

Neighbor Gateway IP
Internet Address
IP Network Address
Number of Hops

Figure 11 -1 0
(p. 11-24)

VALIDATE
CONFIGURATION FILE

None

Figure 5-14
(p. 5-35)

Required Values

Reference

6-11

Guided Configuration
TABLE 6-5 NETXPORT CONFIGURATION - PC ROUTER
Step
1

Screen Name
GUIDED NETWORK
INTERFACE
CONFIGURATION

Required Values
NIName

Reference
Figure 6-3
(p. 6-5)

(Choose PC ROUTER)

NODE NAME
CONFIGURATION
(Visited only if not
previously configured)

Node Name

Figure 8-3
(p. 8-5)

LINK CONFIGURATION
(Repeat Steps 3-6 as
applicable; NEXT SCREEN
to continue to step 7)

Link Name

Figure 7-1
(P. 7-4)

LINK CONFIGURATION:
LINK DATA

LDEVN

Figure 7-12
(p. 7-27)

ROUTER NETWORK
INTERFACE LINKS

Link Type

Figure 10-6
(p. 10-17)

DIRECT CONNECT LINK
CONFIGURATION

None

Figure 10-7 (Direct)
(p. 10-19)

or
Figure 10-8 (Dial)
(p. 10-20

ROUTER DIAL LINK
CONFIGURATION
7

IP PROTOCOL
CONFIGURATION

IP Internet Address

ROUTER MAPPING
CONFIGURATION
(Repeat as applicable; NEXT
SCREEN to continue with
step 10)

Router node name

ROUTER REACHABLE
NODES
(Repeat as applicable; NEXT
SCREEN to return to Step

IP Internet Address
Link Name

Figure 10-3
(p. 10-8)
Figure 10-12
(p. 10-30)

Figure 10-13
(p. 10-32)

8)
10

6-12

VALIDATE
CONFIGURATION FILE

None

Figure 5-14
(p. 5-35)

Guided Configuration

",I'
. . .' ..

NETXPORT UPDATE
" ..

The Netxport Update branch directs the Guided Configuration process for two online configuration
updates.

UPDATE INTERNET leads to the screen sequence for updating gateway internet data on configured LAN
or router networks or on gateway halves.
UPDATE ROUTER MAPPING leads to the screen sequence for updating mapping data on configured
router networks.
It is important to note the different purposes of the two Guided Configuration branches. The Netxport
Configuration branch adds or updates entire network interface configurations, and may not be used to
update an active configuration file. The Netxport Update branch, on the other hand. performs guided
updates of a selected part of existing. validated networks, and is intended for use in updating the active
configuration.
Select .' ':' "':";~i!i~':"'~~1i in the Guided Subsystem Configuration screen to reach the Guided Configuration
Update screen. Select the desired update path by pressing the corresponding function key. I , 1 I or
I
I. as shown in Figure 6-4.

Tables 6-6 and 6-7 show the sequence of steps followed by each of the two Guided Configuration
Updates. For each step. the tables show the screen or screens accessed and the fields for which you must
supply a value. The table also provides a reference figure for each step. You must refer to that figure to
see the actual screen display and read the detailed descriptions of the required fields in that screen.

6-13

Guided Configuration

UPDATE INTERNET

- Update Internet Data for Specified Network Interface.

UPDATE ROUTER MAPPING - Update Mapping Data for Specified Router Network
Interface.

File:

fILENAME.NET.SYS

Figure 6-4. Guided Configuration Update

6-14

Guided Configuration
TABLE 6-6 NETXPORT UPDATE - UPDATE INTERNET

Required Values

kreen Name

Step

GUIDED NETXPORT
UPDATE

NIName

Referenee
Figure 6-4
(po 6-14)

(Choose INTER NET)

NEIGHBOR GATEWAYS
(Repeat as desired; NEXT
SCREEN to continue to step
4)

Gateway Name

Figure 11-9
(po 11-23)

NEIGHBOR GATEWAY
REACHABLE NETWORKS
(Repeat as desired; NEXT
SCREEN to return to Step

Neighbor Gateway Internet
Address
IP Network Address
Number of Hops

Figure 11-1 0
(po 11-24)

None

Figure 5-14
(po 5-35)

2)
4

VALIDATE
CONFIGURATION FILE

6-15

Guided Configuration
TABLE 6-7 NETXPORT UPDATE - UPDATE MAPPING
Step
1

Screen Name
GUIDED NETXPORT
UPDATE

Required Values
NIName

Reference
Figure 6-4
(p. 6-14)

(Choose RTR MAP)
2

ROUTER MAPPING
CONFIGURATION
(Repeat as applicable; NEXT
SCREEN to continue to step

Router node name

Figure 10-12
(p. 10-30)

6-16

ROUTER REACHABLE
NODES

IP Internet Address
Link Name
Entry Priority
Phone 1/ (if applicable)

Figure 10-13
(p. 10-32)

VALIDATE
CONFIGURATION FILE

None

Figure 5-14
(p. 5-35)

LINK CONFIGURATIO_N

The screens described in this section are used for hnk configuration. NMMGR provides four kinds of
screens for configuration of each link. Which screens you are 'p.d to iepends on what you enter in the
fint 8Creen. the LINK CONfIGURATION screen; however. ynu will always proceed to a screen in which you
must configure link data. From there, you can proceed to a screen in which you configure data about
tracing. and (except for IEEE 802.3 links) to a screen to whIch you configure Information about the
telephone connection, for dial links.
The four kinds of screens are descnbed below, with the level of indentation indicating each screen's place
in the configuration tree:

LINK CONFIGURATION - allows you to specify the links configured for this node, including the link's
identifying name and whether it uses IEEE 802.3. BSe, LAP-B, or ASNP as a link-level protocol.
LINK DATA (One of four screens corresponding to t.i'le 111 It... level protocol chosen in the LINK
CONfIGURATION screen.) Ecl~h LINK DATA screen allows you to configure data necessary for
link level software. such as the logical device (Ldev) number of the hardware card, the number
of buffen (which determines the amount of data accepted at the link level before packets are
discarded). and parameters specific to the link -level protocol being used.
LINK TRACE DATA - From each LINK DATA screen, you can proceed to the LINK
TRACE DATA screen for the link being configured. This screen allows you to enable
link level tracing for this link, specify which link level activities will be recorded, and
sp"ify the name of the trace file.

LINK PHONE DATA - From each LINK DATA screen except that for IEEE 802.3 links,
you can proceed to the LINK PHONE DATA screen for the link being configured. This
screen allows you to specify whether the dial connection to a remote node is initiated
by manual dial (in which a system operator must dial the telephone number) or auto
dial (in which the number is automatically dialed by a device with auto dial
capability).
NOTE

Configurable fields described in this manual are required unless otherwise
stated.
II

All fields In the Link Configuration screens are noted as "HP modifiable. II
and should be ehanged onl)' upon the reeommendation of your UP
representative.
On the screens shown in this section, fields that must be configured when
performin'luided configuration are underlined.

7-1

Link Configuration
NOTE

Information that you specify in the NMMGR program always overrides any
similar information entered within the SYSDUMP facility.

'~":':y

7-2

Link Configuration

LINK CONFIGURATION
The select screen in Figure 7-1 is displayed when you press the function key for :.:.
Configuration Menu Screen. It is also displayed when you type the Path name:

; at the

@LINKCONF'
in the command window of any screen and press (ENTER I
Use the fields and the function keys of the select screen to perform the desired action.
.• To define a new link configuration, specify the link name and the type; then press lit. The path
for the selected link name is added ~o the configuration file and the data screen for the type
specified is displayed.
• To modify an existing link configuration, specify the link namp: then press Y~I_. The data
screen on the path for the specified link name is displayed.
• To change the name of an existing hnk configuration, specify the link name and a new name;
then press .~~. The previously configured link name is replaced and the screen displays the
new name in the display fields labeled Configured links.
• To delete an existing link configuration, specify the link name, then press :
The
previously configured link name is deleted and is no longer displayed in the display fields labeled
Configured Links.

7-3

Link Configuration

M"'MGftJ~OOQ:):(;'Jb.r~;OQr 'LI NI<>CONf I 9~RATI~"
:
[l·Pe./:.~~::;:;b~~~:;::q,~i:r:l~~m to 'Update, '~letet.::Qr Rename;
~qiR~""d;;:!!ili!mi!11m:;~~l!m::mmjlm1~:::~;Ji::;
",:::':.. '::'
.....
Path:

LINKCONF

:..1

Link name
New name

SNA/SDLC.LAN802.3
Types: BSC.LAPB.ATP/ASNP
(i f new)

Configured Links

Name

Type

Name

Type

mi:~ena~Ci('
I:;::::::~;::·;·,~ .~

';l;;:H;J:

Figure 7-1. Link Configuration Screen

Fields
link name

(HP modifiable) Select the link name for one of the following: 1) LAN802. 3
link, 2) BSC link, 3) LAP-B link, or 4) ATP/ASNP link.
The link name can contain as many as eight alphanumeric characters, and
the first character must be alphabetic. The link name must match the link
name configured in the corresponding network transport configuration
screen.

Types

(HP modifiable.) Required only when adding a link. Enter the type shown
on the screen that corresponds to your link. Choose LAN802.3 if you are
using StarLAN/3000, ThinLAN/3000, or the ThickLAN option.
Choose LAP-B if you are using an NS Point-to-Point 3000/V Link with
the LAP-B protocol.
Choose BSC if you are using an NS Point-to-Point 3000/V Link with the
DSC protocol.
Choose ATP/ASNP if you are using an Asynchronous Serial Network Link.
For the SMA/SOLC choice, follow the instructions for choosing your link
type according to the SNA Link Services manual (part number
30246-90003).

7-4

Link Configuration
New name

(HP modifiable.) Required only when renaming a link. Enter a new link
name. The new name can contain as many "as eight alphanumeric
characters, and the first cbs ractel must be alphabetic.

7-5

Link Configuration

LINK CONFIGURATION: LAN802.3 LINK DATA
The screen in Figure 7- 2 is displayed when you select a link name and the link type LAN802. 3 at the
Link Configuration Screen (Figure 7-1) and press a~d or p.pc.J~'t;.. It is also displayed when you type the
path name:

@lINKCONF.linkname
in the command window of any screen and press
link name.

(ENTER J,

where l inkname is the configured LAN 802. 3

You must press ~:~-.~!:;m~~~ to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the ~t..:;!
flag is set to I.
... ... .

Path: LINKCONF.linkname

~!,!

Logical Device
(1-999)
Driver Options in Hex (0 - normal mode ope·ration)
Maximum Outstanding Reads (7-64)
Maximum Outstanding Writes (7-64)
Number of Buffers (16-138)
Use factory-Configured Local Station Address? (YIN)

11~~!rtD'c~f~;~rllTiliili~~~~fii] ~~~:~a~~a~~~:u~~d ~~s:b~~eH:X N)

File:

filename.NET.SYS

Figure 7-2. LAN80Z.3 Link Data Screen.

Fields
Logical Device

(HP modifiable.) Enter the logical device number of the LANIC as
configured in SYSDUMP.
Range: 1 -999

7-6

Link Configuration

Driver Options

In Hex

(HP modifiable.) Enter 0 for normal mode. of operation. All other options

are reserved.
Default Value: 0
Range: 0-9. A-F hexadecimal

Maximu. Outstanding
Reads

(HP modifiable.) Specifies the maximum number of reads that can be

outstanding at any given time.
Default Value: 16
Range: 1-64

Haxi.u. Outstanding
Mrites

(HP modifiable.) Specifies the Dlaximum number of writes that can be

outstanding at any given time.
Default Value: 1
Range: 1-64

NU.ber of Buffers

(HP modifiable.) The maximum amount of incoming data that the link

level can accept before discarding packets. The number of buffers to
configure can be calculated with the following formula:

numBuffers

:= 2 x

maximum outstanding reads +

where:

numBuffers is the number of buffers to be configured,
Default Value: 42
Range: 16-138

Factory-Configured
Local Node Address?

(HP modifiable.) The LANIC board is supplied with a 48-bit station
address. These are guaranteed to be unique. Do not change the factory

configured local node address except on the specific instructions of your
HP representative.
Default Value: Y

Local Node Add ress

(UP modifiable.) This field is to be used only with specific instructions
from your UP representative. It allows you to enter a station address to
replace the factory configured address. The format must be compatible
with HP software requirements. Your HP representative will supply
instructions in the unlikely event that you need to enter an address to
replace the default.

7-7

Link Configuration

LINK CONFIGURATION: LAN802.3 LINK TRACE DATA
The screen in Figure 7-3 is displayed when you press the function key for pp~::imr9:.:::1R~c;.~~iit at the
LAN802.3 Link Data Screen (Figure 7-2). It is also displayed when you type the path name:

@LINKCONF.linkname.TRACEOAT
in the command window of any screen and press
link name.

(ENTER I,

where l inkname

the configured LAN 802. 3

You must press q·~.~~m!l~~~ to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the ~t!~
flag is set to ~.

":"'~~:i~~~~1~~~~il,:~~~l;;I~;~~~~~i~,,:~~~~[~~I,
Path: LINKCONf.linkname.TRACEDAT
~IN~t

Link trace enabled?
(YIN)
Trace ALL or ERRORS only? (O=ERRORS; 1=ALL)
II )0.:: 1 WRAP or DISCARD overflow? (O=DISCARD; 1=WRAP)
PRCT? (YIN) Receive Control Entries
PRTX? (YIN) Receive Text Entries
PSCT? (YIN) Send Control Entries
PSTX? (YIN) Send Text Entries
ICD? (YIN) Interconnect Driver Entries
:It.~!I,

J Trace
File:
--

File

filename.NET.SYS

Figure 7-3. LAN802. 3 Link Trace Data Screen.

7-8

Link Configuration
After configuring link data. you can configure tracing for the link. The Link Trace' Data Screen allows
you to specify the events to trace and the name of the file for storin8 the tracing information. For best
performance. do not enable tracing. You can override NMMGR activated link tracing by using the
LINKCONTROL TRACE=OFF command. Using the lINKCONTROL command to enable and disable link
tracing is described in the "Commands" section lSectiol, 1) of Volume II of this manual set. For
Information on formatting the link trace file. refer to the LAN/3000 Diagnostic and Troubleshootin,
Guide.

Fields
Link trace enabled?

(HP modifiable.) Enter Y (YES) to enable link tracing. N (NO) otherwise.

Can be overridden with the lINKCONTROL command. If you do enable link
tracing, you are required to enter a trace file name. For best performance.
do not enable tracing.
Default Value: N

Trace ALL
or ERRORS only

(HP modIfiable.) Enter 1 (ALL) to tl'ar.e all events, 0 (ERRORS) to trace
errors only.
Default Value: 0

MRAP or
DISCARD overflow?

(HP modifiablp ) Enter 1 (WRAP) to overlay previous internal record entries

with overflow trace entries, 0 (DISCARD) if you want it to discard the
overflow.
Default Value: 0

PRCT?

(HP modifiable.) Enter Y (YES) to record Receive Controls (PRCTs) received
on the line, N (NO) otherwise.
Default Value: Y

PRTX?

(HP modifiable.) Enter Y (YES) to record Receive Text (PRTXs) received on
the line, N (NO) otherwise.
Default Value: Y

PSCT?

(HP modifiable.) Enter Y (YES) to record Send Controls (PSCTs) sent on the

line, N (NO) otherwise.
Default Value: Y

PSTX?

(HP modifiable.) Enter Y (YES) to record Send Text (PSTXs) sent on the line,
N (NO) otherwise.
Default Value: Y

ICD?
(HP modifiable.) Enter Y (YES) to record Interconnect Driver Entries (ICDs),
N (NO) otherwise.
Default Value: N

7-9

Link Configuration

Trace file

(HP modifiable.) Required if link trace is enabled. Name of the disc file in
which you want to record tracing. Must be a valid MPE file name. Enter
the filename in the format filename.groupname.acctname. The fully
qualified file name can be as many as 26 characters. Lockwords are not
allowed for trace files.
Do not specify the same file name with the NMMGR configuration as
specified with the l I NKCONTROl command.
Only one active trace is allowed per link. Refer to LAN/3000 Diagnostic
and Troubleshooting Guide for information on how to format the trace file.

7-10

Link Configuration

LINK CONFIGURATION: SSC LINK DATA
The screen in Figure 7-6 is displayed when you select a link name and the link type esc at the Link
Configuration Screen (Figure 7-1) and press Add or Update It IS also displayed when you type the path
name:

@lINKCONF.linkname
in the command window of any screen and press (ENTER I, where l inkname is the configured BSC link
name.
You must press Update ~ta to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the ~J.l
flag is set to ~.

Path: lINKCONF.linkname
logical device
(1-999)
Connect timeout
(60-900 seconds or 0)
Number of error recovery retries
(1-255)
Clear to send delay
(0-20 tenths of a second)
Data set ready delay (Y/N)
Buffer size (32-1500 bytes)
Number of buffers
(10-50)
Line speed in bits/second (1200,2400,4800,9600,19200,38400,56000)
leading SYN characters (0=4 SYN, 1=8 SYN, 2=12 SYN, 3=16 SYN)

file:

filename.NET.SYS

Figure 7-6. BSC Link Data Screen

Fields
Logical device

(UP modifiable.) Enter the logical device number of the INP card as
configured in SYSDUMP.
Range: 1-999

7-11

Link Configuration

Connect timeout

(HP modifiable.) During link initialization, this value specifies the amount
of time the INP will wait for a response from the remote station. If this
time lapse is excee.ded, it is assumed that the remote station is not
responding.

.'~

Default Value: 900
Range: 60-900 seconds or 0

NUliber of error
recovery retries

(HP modifiable.) The total number of times a block will be retransmitted
due to the lack of an acknowledgement. If this number is exceeded, it is
assumed that the remote station is not responding.
Default Value: 15
Range: 1-255

Clear to send delay

(HP modifiable.) User selectable. When initializing the link, this value
specifies the amount of time the INP will wait for the DCE to raise Clear
To Send (CTS) after raising Request To Send (RTS).
Default Value: 0 (Delay determined by modems)
Range: 0-20 tenths of a second

Data set ready delay

User selectable.
(HP modifiable.) This value specifies the time lapse allowed for DCE to

raise Data Set Ready after the INP raises Data Terminal Ready (DTR).
Default Value: N

Buffer size

(HP modifiable.) Size, in bytes, of the buffers used to hold user data, plus
layer 3 and layer 4 protocol headers. The size of the packets transmitted

over the link is the buffer size plus the layer 2 header.
Default Value: 1500

Range: 32-1500

Number of Buffers

(HP modifiable.) This field specifies the number of buffers used to transfer

blocks of data to and from the INP. The field specifies the number of
buffers to be allocated on the HP 3000 not the INP.
Default Value: 12
Range: 10-50

Line speed

(HP modifiable.) This is the line-transmission speed in bits per second. It
may be overridden by whichever device is providing clocking. The INP
simply transmits using the provided clock source.
Default Value: 9600

7-12

Link Configuration
Leading SYN characters (HP modifiable.) This field sp~"lhes the number of leading synchronization
characters (SYN) that will precede each block transmission. These SYN
characters are used by the receiving station to establish character-phase
synchromzation. If the receiving station is ua ving difficulty establishing
character phase syncronization. in"reasing the value of this field may help.
Default Value: 0

7-13

Link Configuration

LINK CONFIGURATION: SSC LINK TRACE DATA
The screen in Figure 7-7 is displayed when you press the function key for (;o"'TiO'.;taACEDAt at the BSC
Link Data Screen (Figure 7-6). It is also displayed when you type the path name':' ..
"d'

••

@LINKCONf.linkname.TRACEDAT
in the command window of any screen and press
name.

(ENTER I,

where l inkname is the configured BSC link

You must press P~~.~i.;::l~~i to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the ~t,:i.;~~
flag is set to ~.
.
dl ••

r!el'~~~~;~~I~~;~~~!i;!;~~~~i~~ti~~;,~~;~~~j~~~I~~~~i~:]~i~~t t:~~~~:~~i~jl,~i!iii~ili~l~!:!!i~,!ii
Path: LINKCONf.linkname.TRACEDAT

Trace File
file:

filename.NET.SYS

Figure 7-7. BSC Link Trace Data Screen.
After configuring link data, you can configure tracing for the link. The Link Trace Data SCreen allows
you to specify the events to trace and the name of the file for storing the tracing information. For best
performance. do not enable tracing.

The link tracing facility provides a method of monitoring the communication line. When collecting data
to diagnose a problem, always set the "Trace ALL or ERRORS only" field to ALL (choice number I); set
the STN, RCT, RTX, SeT, and STX entries to Y (YES), and set ICD to N (NO) unless specifically instructed
by Hewlett-Packard to do otherwise. You can override NMMGR activated link tracing by using the
LINKCONTROL TRACE=OfF' command. Using the LINKCONTROL command to enable and disable link

7-14

Link Configuration
tracing is described in the "Commands" section (section 1) of Volume II of this manual set. For
information on formatting the link trace file, refer to the Fundamental Data Communications Handbook.

Fields
Link trace enabled?

(UP modifiable.) Enter Y (YES) to enable link tracing, N (NO) otherwise.
Can be overridden with the lINKCONTROL command. If you do enable link
tracing, you are required to enter a trace file name. For best performance,
do not enable tracing.
Default Value: N

Trace ALL
or ERRORS only

(UP modifiable.) Enter 1 (ALL) to trace all events, 0 (ERRORS) to trace
errors only.
Default Value: 0

Entries per record

(HP modifiable.) Enter the number of entries you want formatted per
record.
Default Value: 24

MRAP or
DISCARD overflow?

(HP modifiable.) Enter 1 (WRAP) to overlay previous internal record entries
with overflow trace entries, 0 (DISCARD) if you want it to discard the
overflow.
Default Value: 0

STH?

(HP modifiable.) Enter V (YES) to record State Transitions (STNs), N (NO)
otherwise. Hewlett-Packard use only.
Default Value: N

OPR

and

EDT?

(HP modifiable.) Enter V (YES) to record operand and editor entries; N (NO)
otherwise.
Default Value: N

RCT?

(HP modifiable.) Enter Y (YES) to record Receive Controls (RCTs) received
on the line, N(NO) otherwise.
Default Value: Y

RTX?

(HP modifiable.) Enter V (YES) to record Receive Text (RTXs) received on
the line, N (NO) otherwise.
Default Value: V

SCT?

(JlP modifiable.) Enter V (YES) to record Send Controls (SCTs) sent on the
lin", N (NO) otherwise.
Default Value: Y

7-IS

Link Configuration
STX?

(HP modifiable.) Enter Y (YES) to record Send Text (STXs) sent on the line.
N (NO) otherwise.
Default Value: Y

ICD?

(HP modifiable.) Enter Y (YES) to record Interconnect Driver Entries (ICDs),
N (NO) otherwise. The ICD entry is for Hewlett-Packard use only.
Default Value: N

Trace File

Only one active trace is allowed per link. Refer to the Fundamental Data
Communications Handbook for information on how to format the trace file.

7-16

Link Configuration

LINK CONFIGURATION: BSC LINK PHONE DATA
The screen in Figure 7-8 is displayed when you press the function key for ~:Wf:r9'd~~~~! at the
Link Data Screen (Figure 7-6). It is also displayed when you type the path name:

sse

@lINKCONF.linkname.PHONEDAT
in the command window of any screen and press (ENTER I) where
name.

1inkname is

the configured

sse

link

You must press :. ,,' .i~e:~:;~I)ifJ.i to transfer the data displayed on the screen to the configuration file you
are creating or updating~"""y'ou verify that the data record has been created by checking that the Ii~i!~:
flag is set to ~.

-Path:

LINKCONF.linkname.PHONEDAT
manual or autodial?

File:

(O=Manual, 1=Autodial)

filename.NET.SYS

Figure 7-8. BSC Link Phone Data Screen.

Fields
.anual or autodlal?

(HP modifiable.) Enter 1 if you want the INP to automatically dial the
phone number without intervention from the system operator. Enter 0 if
you want the link manager to display the phone number on the console for
the system operator to dial.
Default Value: 1

7-17

Link Configuration
Related Screens:

- NETX PORT .NI .niName.MAPPING.nrzpentry
This Router Reachable Node screen is where you enter phone numben
of destination nodes.
- NETXPORT .NI .niName. LINK.nilink
This Gateway Half Dial Link Configuration screen is where you enter
phone numbers of destination nodes.

.;~

7-18

Link Configuration

LINK CONFIGURATION: LAP-B LINK DATA
The screen in Figure 7-9 is displayed when you select a link name and the link type LAP-B at the Link
Configuration Screen (Figure 7-I) and press ~~~ or Ylij!h;~~". It is also displayed when you type the path
name:

@LINKCONF.linkname
in the command window of any screen and press (ENTER ), where l inkname is the configured LAP-B link
name.
You must press If.li~;,:·· . . u.,.:::~~ to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the .':" ."".,'
flag is set to ~.

Path: LINKCONF.linkname
Logical device
(1-999)
Connect timeout
(60-900 seconds or 0)
local timeout
(5-900 seconds or 0)
LAP-B parameter T1 (5-3000 hundredths of a second)
LAP-B parameter K - Maximum outstanding frames (1-1)
LAP-B parameter N2 - retry count (1-255)
Clear to send delay (0-20 tenths of a second)
Buffer size
(32-1024 bytes)
Number of buffers (10-50)
Local mode
(5=DTE, 6=DCE, 11=Point to Point)
Line speed in bits/second (1200,2400,4800,9600,19200,38400.56000)

File:

filename.NET.SYS

Figure 7-9. LAP-B Link Data Screen

Fields
Logical device

(HP modifiable.) Enter the logical device number of the INP card u
configured in SYSDUMP.
Default Value: N
Range: 1-999

7-19

Link Configuration

Connect timeout

(HP modifiable.) During link initialization, this value specifies the amount
of time the INP will wait for a response. from the remote station. If this
time lapse is exceeded, it is assumed that the remote station is not
responding.
Default Value: 900
Range: 60-900 seconds or 0

Local timeout

(HP modifiable.) Timer on the INP-to-HP 3000 communications path.
If the INP and the HP 3000 do not communicate during this time, LED 1
on the INP will flash, and the INP will no longer attempt to communicate.
Default Value: 60
Range: 5-900 seconds or 0

LAP-B parameter T1

(HP modifiable.) Response timeout in hundredths of a second. This is the
maximum amount of time that the transmitter should wait for an
acknowledgement before initiating a recovery procedure. This delay must
account for 3 frame transmissions and 2 frame-processing delays. An
approximation of this value is 3 seconds for line speeds greater than or
equal to 9600 bits per second and 4 seconds for line speeds less than 9600
bits per second. The formula for the approximation in hundredths of a
second is: 400 x [(buffer size x 8)/line speed]. The configuration validation
program will issue a warning if the set value does not comply to this
specification.
Default Value: 300
Range: 5-3000

LAP-B parameter K

(HP modifiable. ) This parameter specifies the maximum number of
sequentially numbered franles that the configured node may have
unacknowledged at any given time. This parameter is also called the Level
2 window size.
Default Value: 1
Range: 1-7

LAP-B parueter N2

(HP modifiable.) This field specifies the maximum number of times to
retransmit a frame if the T I timer expires. The recovery procedure
mentioned in IILAP-B parameter T III usually refers to the retransmission of
the oldest unacknowledged frame. The value of N2 specifies the total
number of times that the Tl timer expires and a frame is retransmitted in
determining that the other side is not responding.
Default Value: 20
Range: 1-255

Clear to send delay

7-20

(HP modifiable.) User selectable.

When initializing the link, this value

Link Configuration
specifies the amount of time the INP will wait for the DCE to raise Clear
To Send (CTS) after raising Request To Send (RTS).
Default Value: 0 (Delay determined by modems)
Range: 0-20 tenths of a second

Buffer size

(HP modifiable.) Size, in bytes, of the buffers used to hold user data, plus
layer 3 and layer 4 protocol headers. The size of the packets transmitted
over the link is the buffer size plus the layer 2 header.
Default Value: 1024
Range: 32-1024
(HP modifiable.) This field specifies the number of buffers used to transfer
blocks of data to and from the INP. The field specifies the number of
buffers to be allocated on the HP 3000 not the INP.
Default Value: 12
Range: 10-50

Local lMXIe

(HP modifiable.) For HP Point-to-Point (all NS links) enter 11. If you are
HP point-to-point, the other side must also be HP point-to-point. Enter 5
if the local station is acting as DTE, and enter 6 if the local station is acting
as DCE. If you are DCE, the other side must be DTE. If you are DTE, the
other side must be DeE. HP recommends using HP point-to-point because
the system handles the designation for which side is DTE and DCE.
Default Value: 11
Range: Point-to-Point. DTE, or DeE

Line speed

7-21

Link Configuration

LINK CONFIGURATION: LAP-B LINK TRACE DATA
The screen in Figure 7-10 is displayed when you press the function key for Q~:{;itrc('TRActI)AT at the
LAP-B Link Data Screen (Figure 7-9). It is also displayed when you type the path

name:···· .

@lINKCONF.linkname.TRACEDAT
in the command window of any screen and press I ENTER I. where l ink.name is the configured LAP-B link
name.
You must press P:r8.:t;!i::l:~~'- to transfer the data displayed on the screen to the configuration file you
are creating uor updating. You verify that the data record has been created by checking that the Dit!ilt
flag is set to i",'
~"":.:,,,,"",J;:"=

~~f'~E~I~I~~~I~~~~~~III-_m.
Path: LINKCONF.linkname.TRACEDAT
link trace enabled?
(Y IN)
Trace ALL or ERRORS only? (O=ERRORS; 1=ALl)
I[[~~l: Entries per record
(Ot at 16, 24)
'iOO~'~: WRAP or DISCARD overflo~?
(O=DISCARD; 1=WRAP)
l;iN:: STH? (V/N) State Transltlon Entries
: . RCT? (YIN) Receive Control Entries
RTX? (YIN) Receive Text Entries
SCT? (YIN) Send Control Entries
STX? (YIN) Send Text Entries
ICD? (V/N) Interconnect Driver Entries
!~N~:

11l~U:

File:

filename.NET.SYS

Figure 7-10. LAP-B Link Trace Data Screen.
After configuring link data, you can configure tracing for the link. The Link Trace Data Screen allows
you to specify the events to trace and the name of the file for storing the tracing information. For best
performance. do not enable tracing.

The link tracing facility provides a method of monitoring the communication line. When collecting data
to diagnose a problem, always set the ''Trace ALL or ERRORS only" field to ALL (choice number 1~ set
the STN, RCT, RTX, SCT, and STX entries to V (YES~ and set leo to N (NO) unless specifically instructed
by Hewlett-Packard to do otherwise. You can override NMMGR activated link tracing by using the
LINKCONTROL TRACE=OFF command. Using the LINKCONTROL command to enable and disable link

7-22

Link Configuration
tracing is described in the "Commands" section (Section 1) of Volume II of this manual set. For
information on formatting the link trace file, refer to the Fundamental Data Communications Handbook.

Fields
Link trace enabled?

(HP modifiable.) Enter V (\' ES) to enable link tracing, N (NO) otherwise.
Can be overriddt"rI with the LINKCONTROL command. If you do enable link
tracing, you are required to enter a trace file name. For best performance,
do not enable tracing.
Default Value: N

Trace ALL
or ERRORS only

(HP modifiable.) Enter 1 (ALL) to trace all events. 0 (ERRORS) to trace
errors only.
Default

Entries per record

Valu~;

(HP modltlable.) Enter the number of entries you want formatted per
record.
Default Value: 24

MRAP or
DISCARD overflow?

(HP modifiable.) Enter 1 (WRAP) to overlay previous internal record entries
with overflow trace entries, 0 (DISCARD) if you want it to discard the
overflow.
Default Value: 0

STN?

(HP modifiable.) Enter V (YES) to record State Transitions (STNs), N (NO)
otherwise. The STN enttry is for Hewlett-Packard use only.
Default Value: N

ReT?

(HP modifiable.) Enter V (YES) to record Receive Controls (RCTs) received
on the line, N (NO) otherwise.
Default Value: V

RTX?

(HP modifiable.) Enter V (YES) to record Receive Text (RTXs) received on
the line, N (NO) otherwise.
Default Value: V

scrf

(HP modifiable.) Enter Y (YES) to record Send Controls (SCTs) sent on the
line, N (NO) otherwise.
Default Value: V

sncf

(HP modifiable.) Eater V (YES) to record Send Text (STXs) sent on the line,
N (NO) otherwise.
Default Value: Y

7-23

Link Configuration

ICD?

(HP modifiable.) Enter Y (YES) to record Interconnect Driver Entries (leDs),
N (NO) otherwise. The leD entry is for Hewlett-Packard use only.

Default Value: N

Trace file

Only one active trace is allowed per link. Refer to the Fundamental Data
Communications Handbook for information on how to format the trace file.

7-24

Link Configuration

LINK CONFIGURATION: LAP-B LINK PHONE DAT A
The screen in Figure 7-II is displayed when you press the function key for ~ji;E:r:p. m~~~I:I)1 at the
LAP-B Link Data Screen (Figure 7-9), It is also displayed when you type the path name:

@LINKCONf.linkname.PHONEDAT
in the command window of any screen and press (ENTER I, where 1inkname is the configured LAP-B link
name.
You must press ~!rMi~~!![!l~~~i to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the 1I~~il
flag is set to I.

Path: LINKCONf.linkname.PHONEDAT
manual or autodial?

file:

(O=Manual, 1=Autodial)

filename.NET.SYS

Figure 7-11. LAP-B Link Phone Data Screen.

Fields
manual or autodlal?

7-25

Link Configuration
Related Screens:

- NETX PORT. NI • niName. MAPPI NG. m:zpen t ry
This Router Reachable Node screen is where you enter phone numbers
of destination nodes.
- NETXPORT. NI • niName. LINK. ni link
This Gateway Half Dial Link Configuration screen is where you enter
phone numbers of destination nodes.

7-26

Link Configuration

LINK CONFIGURATION: ASNP LINK DATA
The screen in Figure 7-12 is displayed when you select a link name and the link type ATP/ASNP at the
Link Configuration Screen (Figure 7-1) and press ~d,C:i or ~M~~~. It is also displayed when you type the
path name:

@LINKCONf.linkname
in the command window of any screen and press (ENTER), where linkname is the configured ATP/ASNP
link name.
You must press Y:iI'~~:llll~~. to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the . .
flag is set to Ij.

Path: LINKCONf.linkname
Logical Device (1-999)
Subtype (O=Hardwired t 1=Modem t 2=European Modem)
Linespeed in bits/second (1200 t 2400 t 9600)
Connect timeout (0-900 seconds)
Maximum Outstanding Reads (1-32)
Maximum Outstanding Writes (1-32)
Buffer size in bytes (1-1024)
Number of Buffers (2-128)

file:

filename.NET.SYS

Figure 7-12.. ASNP Link Data Screen

Fields
Logical Device

(MP modifiable.) Enter the logical device number of the link as configured

in SYSDUMP.
Default Value: N
Range: 1-999

7-27

Link Configuration

SUbtype

(HP modifiable.) Enter the number shown on the screen that corresponds to
your subtype.
Default Value: 1

Linespeed

Must be a value supported by the modem.
Default Value: 1200
Range: 1200, 2400, 9600

Connect timeout

(HP modifiable.) The number of seconds the operator has to dial the phone
number of the remote node after the DTR signal goes on.
Default Value: 0
Range: 0-900

Maximum Outstanding
Reads

(MP modifiable.) Specifies the maximum number of reads that can be

outstanding at any given time.
Default Value: 5
Range: 1-32

Maximum Outstanding
Writes

(MP modifiable.) Specifies the maximum number of writes that can be

outstanding at any given time.
Default Value: 5
Range: 1-32

BUffer size

(MP modifiable.) Size, in bytes, of the buffers used to hold user data, and

layer 3 and layer 4 protocol headers. The size of the packets transmitted
over the link is the buffer size plus the layer 2 header.
For PC connections, use the default value of 242 bytes. For connections to
other HP 30008, the suggested value is S12 bytes. This configured buffer
size should be the same as the buffer size configured for the remote
HP 3000. You may choose to increase the buffer size for HP 3000 to
HP 3000 connections if you are using high-quality lines.
Default Value: 242
Range: 1-1024

Nu.ber of Buffers

(HP modifiable.) The maximum amount of incoming data that the link
level can accept. Determines the total amount of space in virtual memory
used for incoming data. The count is also dependent on the maximum
outstanding reads. It should be equal to or greater than 2 times the amount
of outstanding reads.
Default Value: 20
Range: 2-128

7-28

Link Configuration

LINK CONFIGURATION: ASNP LINK TRACE DATA
The screen in Figure 7-13 is displayed when you press the function key for ~mIJt~~m~lfj,~.'T at the
ASNP Link Data Screen (Figure 7-12). It is also displayed when you type the path name:

@LINKCONf.linkname.TRACEDAT
in the command window of any screen and press [ENTER I, where l inJc.name is the configured ATP/ ASNP
link name.
You must press ~lfl~~~'·:;i~'. to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the ..
flag is set to I.

I~. ;":~;"'ffi""~;~~-il,~~I~:~!!;~~1~5~I~~~i:i!~~~~~i~.'!1::::;,;,
m

•••••••••••

Path: LINKCONF.linkname.TRACEDAT

tfN.:l Link trace enabled?

(V IN)
Trace ALL or ERRORS only? (ERRORS=O; ALL=1)
'; ;0;1 I WRAP or DISCARD overflow? (OISCARD=O; WRAP=1)
i:
PRCT? (V IN) Receive Control Entries
PRTX? (V/N) Receive Text Entries
PSCT? (V/N) Send Control Entries
PSTX? (YIN) Send Text Entries
leO? (YIN) Internal Driver Entries

llg!'-:
~.
\

Trace File

File:

filename.NET.SYS

Figure 7-13. ASNP Link Trace Data Screen.
After configuring link data, you can configure tracing for the link. The Link Trace Data Screen allows
you to specify the events to trace and the name of the file for storing the tracing information. For ben
performance. do not enable tracing. You can override NMMGR. activated link tracing by using the
LINKCONTROL TRACE=OFF command. Using the LINKCONTROL command to enable and disable link
tracing is described in the "Commands" section (Section 1) of Volume II of this manual set. For
information on formatting the link trace file, refer to the Fundamental Data Communications Handbook.

7-29

Link Configuration

Fields
Link trace enabled?

(HP modifiable.) Enter Y (YES) to enable link tracing, N (NO) otherwise
Can be overridden with the LINKCONTROL command. If you do enable link
tracing, you are required to enter a trace file name. For best performance,
do not enable tracing.
Default Value: N

Trace ALL
or ERRORS only

(HP modifIable.) Enter 1 (ALL) to trace all events, 0 (ERRORS) to trace
errors only.
Default Value: 0

WRAP or

DISCARD overflow?

(HP modifiable.) Enter 1 (WRAP) to overlay previous internal record entries
with overflow trace entries, 0 (DISCARD) if you want it to discard the
overflow.
Default Value: 0

PReT?

(HP modifiable.) Enter Y (YES) to record Receive Controls (PRCTs) received
on the line, N (NO) otherwise.
Default Value: Y

PRTX?

(HP modifiable.) Enter Y (YES) to record Receive Text (PRTXs) received on
the line, N (NO) otherwise.
Default Value: Y

PSCT?

(HP modifiable.) Enter Y (YES) to record Send Controls (PSCTs) sent on the
line, N (NO) otherwise.
Default Value: Y

PSTX?

(HP modifiable.) Enter Y (YES) to record Send Text (PSTXs) sent on the line,
N(NO) otherwise.
Default Value: Y

ICD?

(HP modifiable.) Enter Y (YES) to record Interconnect Driver Entries (lCDs),
N (NO) otherwise.
Default Value: N

Trace File

7-30

Link Configuration
Only one active

trCtC~

is allowed per link. Refer to the Fundamental Data

Communicationg Handbook

for information 01'\ how to format the trace file.

7-31

Link Configurahon

LINK CONFIGURA TION: ASNP LINK PHONE DA T A
The screen in Figure 7-14 is displayed when you press the function key for 09 T9.'.f>tION.EOl'T at the
ASNP Link Data Screen (Figure 7-12). It is also displayed when you type the paih name:
.

@LINKCONf.linkname.PHONEDAT
in the command window of any screen and press (ENTER )t where l inkname is the configured ATP/ ASNP
link name.
You must press Upclite:,:oata to transfer the data displayed on the screen to the configuration file you
are creating or updating. This is necessary if you are planning to use either the direct dial or shared dial
link. Verify that the data record has been created by checking that the Oa~.~ flag is set to y.

Path: LINKCONf.linkname.PHONEDAT
11;~iJ

file:

manual or autodial?

(O=Manual, 1=Autodial)

filename.NET.SYS

Figure 7-14. ASNP Link Phone Data Screen.

Fields
manual or autodlal?

(MP modifiable.) Display only. This field is currently always set to 1; hence
no messages for the system operator will appear on the console for manual
dial. For RASP. dial manually after the network comes up.
Default Value: 1

7-32

NETWORK TRANSPORT
'---C_ON_F_I_GU_R_A_T_IO_N

CTI

This section contains information about the NMMGR configuration screens that are common to all
network interface types. The network transport configuration branch of NMMGR begins with a screen
called the NETWORK TRANSPORT CONfIGURATION SE lECTION screens. This screen, and those to which it
leads, are listed and described below. The level of indentation shown in the following list indicates the
place held by each screen in the configuration tree.
NETWORK TRANSPORT CONFIGURATION SELECTION - This screen presents a selection of four
configuration branches: for configuration of nodal identity information, global transport information.
general protocols (TCP, PXP, and IP Update protocols), and configuration of network interfaces.
NODE CONFIGURATION - This screen, which you will re~ch by pressing ~:m~~_~I. on the
NETWORK TRANSPORT CONfIGURATION SELECTION screen, requires you to press a function key

to proceed to the next screen
NODE NAME CONFIGURATION - This screen allows you to enter the node name of the

node being configured.
CONFIGURATION - This screen. which you reach by pressing
on the NETWORK TRANSPORT CONfIGURATION SELECTION screen. allows you
to enter information used for transferring data between nodes. For example. it enables you to
specify and prioritize the methods used to resolve names and IP adresses. the name of a home
network (needed only if this node is used as a gateway half), and the maximum number of nodes'
expected to be communicating concurrently with the node you are configuring.

GLOBAL

TRANSPORT

~'::'To GL()B.~L

PROTOCOL CONFIGURATION - This screen allows you to specify which of three
protocols to configure next: IPU (lP Update), PXP, or TCP.

GENERAL

IP UPDATE CONFIGURATION - Information entered on this screen specifies the upper
limit of memory that will be reserved for the IPU module, which creates and maintains
internet routing tables for this node.
PACKET EXCHANGE (PXP) CONFIGURATION - This screen allows you to configure
information needed by the PXP protocol running on this node.
TRANSMISSION CONTROL PROTOCOL (TCP) CONFIGURATION - This screen allows

you to configure information used by the TCP protocol running on this node.
NETWORK INTERFACE CONFIGURATION - This screen, which you will reach by pressing
~~iF:~Q::r~:r on the NETWORK TRANSPORT CONfIGURATION SELECTION screen. allows you to
specify a network interface name and Its type for each of the node's network interfaces. Each

time you specify an interface, NMMGR allows you to proceed through the series of
configuration screens necessary for configuring the specified interface type. The configuration
screens for each type are described in Sections 9, 10, 11, and 12 of this manual.
The network transport must be configured in the configuration file that is also used for the link
configuration. This configuration fde must be located In the NET group of the SYS account. The
recommended file name for the actual configuration file that contains the link. and network transport
configurations is NSCONF. NET. SYS. If you use a different filename, you need to specify the filename
with the CONF keyword when you use the NETCONTROL START command to initiate a network

8-1

Network Transport Configuration
connection. A description of the NETCONTROl command is contained in Section 1, Volume II of this
manual.
To reach the network transport configuration screens, follow these steps:
• Issue the run command for NMMGR; the Open Configuration/Directory File Screen is displayed.
• Enter

the

name

the

configuration

file

created

updated

the

Conf igu ra t ion F'i Ie Name field.

• Press the appropriate function key (Open Cpnflg or Create ~onfi9); the Main Menu Screen is
displayed.
• Press the function key for Go

Io: CoHFIG; the Configuration Menu Screen is displayed.

• Press the function key for GO,. ::To'NETXPORT; the Network Transport Configuration SelectIon
.. .....
Screen is displayed.
For more general information on NMMGR, refer to "Getting Started with Nl\1MGRll in Section 5.
NOTE

Configurable fields described in this manual are required unless otherwise
stated.
Fields described as ItUP modifiable" should be changed only upon the
recommendation of your UP representative.
On the screens shown in this section) fields that must be configured when
performing guided configuration are underlined.

8-2

Network Transport Configuration

NETWORK TRANSPORT CONFIGURATION SELECTION
The menu screen shown in Figure 8-1 is displayed when you press the function key for ~alli~mt«~
at the Configuration Menu Screen. It is also displayed when you type the path name:

@NETXPORT
in the command window of any screen and press

(ENTER I.

From this screen you proceed to the screens used to configure the network transport.

•~l~,~~" ~mj~~i~i~!:r:~~r;~;il:~L1~i~i[~i~[~~
Path:
NODE

NETXPORT
-

GLOBAL

Configure Nodal Identity Information
Configure Global Transport Information

GPROT

Configure General Protocols (TCP,PXP,IPU)

Configure Network Interfaces

NOTE:

Be certain to use IINETXPORT UPDATE" to reconfigure an active network.
Type uNIUPDATE" in the command window and press enter to use this
Guided Configuration feature.

File:
-

filename.NET.SYS

Figure 8-1. Network Transport Configuration Selection Screen
Choose the item you wish to configure and press the corresponding function key.

8-3

Network Transport Configuration

NODE CONFIGURATION
The menu screen shown in Figure 8-2 is displayed when you press the function key for ,.;,
. : at
the Network Transport Configuration Selection Screen (Figure 8-1). It is also displayed when you type
the path name:

@NETXPORT.NODE
in the command window of any screen and press (ENTER I.
From this screen press
node.

Path:
NAME

File:
-

_m::!fJiillll.i to

proceed to the screen used to configure a unique name for this

NETXPORT. NODE
-

Configure The Local Node Name

filename.NET.SYS

Figure 8-2.. Node Configuration Screen

8-4

Network Transport Configuration

NODE NAME CONFIGURATION
The screen in Figure 8-3 is displayed when you press the function key for ~';ml1tQ'::::"~£ at the Node
Configuration Screen (Figure 8-2). It is also displayed when you type the path

nam;:···n

@NETXPORT.NODE.NAME
in the command window of any screen and press [ENTER I.
You must press ~;~.~'::;:;~~i to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the _
flag is set to ~.

Local Node Name

File:

filename.NET.SYS

Figure 8-3. Node Name Configuration Screen.

8-5

Network Transport Configuration

Fields
Local Node Name

The format of a node name is name.dotmin.organization where the
total number of characters is 50 or fewer, and each field can contain as
many as 16 characters (alphanumeric, underscore or hyphens). The first
character of each field must be alphabetic.
The name portion of each node name must be unique within the node's
network, and the name. domain portion of each node name must be unique
within the catenel
HP recommends that all nodes on the same network be assigned the same

donrzin and organization. You should assign meaningful names. For
example, MKTG. LAN 1• HP and LAB. LAN 1• HP would be reasonable names for
two nodes on the same Local Area Network at Hewlett Packard. One node
in this example would be used by a marketing department, and one node
would be used by a lab. The organization fields in this example are the
same because the nodes belong to the same catenet. Refer to Section 3,
Volume 1 for rnore information about node names.

8-6

Network Transport Configuration

GLOBAL TRANSPORT CONFIGURATION
The screen in Figure 8-4 is displayed when you press the function key for ~::[(q~~~.~ at the Network
Transport Configuration Selection Screen (Figure 8-1). It il also displayed when you type the path name:

@NETXPORT.GlOBAL
in the command window of any screen and press (ENTER I.

The purpose of this data-entry screen is to enter information that
between nodes.

used for transferring information

You must press lr:'~':' .,,,.:.:~:!::~I~ to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the
flag is set to ~.

~~!RI~~:;'i. . . c·~';~'~~lr'~~~~';;i;;:llr~9T~'"
Path:

NETXPORT.GLOBAL

Name Search Methods And Order
1 - Network Directory
2 - Probe

3 - Probe Proxy
o - Choice Omitted

Maximum Directly Connected Nodes
Maximum Outbound Destinations
Maximum Inbound Destinations

file:

filename.NET.SYS

Figure 8-4. Global Transport Configuration Sereen

Fields
Home Network Na.e

Leave this field blank if there are no gateway-half Nls configured for this
node. Otherwise, enter the name of a configured LAN802. 3 Nlor router
NI.

8-7

Network Transport Configuration
The Home Network Name is required when configuring a gateway half to
determine the source IP address for packets originating from the node over
the gateway half Link. The source IP address that will be used will be the
one configured for the Home Network IP protocol.

~
. _.

The name you enter in this field should give the greatest number of
destination networks a short return path to this node.
Related Screens:

- NETXPORT. NI
NI names configured here
Hue Search Hethods

and Order

The Name Search Methods and Order field is used to select the method and
relative order by which node names (specified in the DSLINE command and
the NetiPC IPCConnect intrinsic) will be resolved into transport addressing
information. This addressing information is contained in a structure called
a path report.
The path report for a particular node name may be retrieved by one of
three methods: the Network Directory, the Probe Protocol or the Probe
Protocol Proxy. Refer to section 3 for information about these methods.
Configurable values are:
1 Network Directory
2 Probe
3 Probe Proxy
o sa Choice Omitted
II

lOll

Default Value: 2.3.1 Probe, Probe Proxy, Network Directory)
Range: 0-3

Maximum Directly
Connected Nodes

This field controls the allocation of data structures needed to communicate
with nodes directly connected to this node. A node is directly connected
when it is a member of the same network(s) as the local node. This field
need only reflect the maximum number of directly connected nodes that
will be communicated with simultaneously. If this node can communicate
to all other nodes in the network simultaneously, the maximum number can
be computed as follows:

Type Of NI
Loopback
Gateway Half
LAN

ROUTER

8-8

, Directly Connected Nodes
1
1

Maximum Number Of Nodes In Network
(Taken From LAN802.3 NETWORK
INTERFACE CONfIGURATION SCREEN)
Maximum Number Of Links Configured
under the HI

Network Transport Configuration

To the above computation an additional amount should be added. This
amount is computed as follows:
10 + (I 0 * each configured NI)
This field should be configured relatively large and reviewed whenever the
network(s) of which this node is a member expands..
Related Screens:
- NETXPORT. NI .lan
Maximum nodes in network
- NETXPORT. NI. router. LINK
Number of links configured
Default Value: 100
Range: 1-1 024

Maxlmu. Outbound
Destinations

This is the maximum number of nodes that this node expects to be
communicating with concurrently, with this node initiating
communication. It includes both directly and non-directly connected
nodes.
This field should be configured relatively large to allow for future
communication expansion. Note that changes to this field will not take
effect until the operating system is restarted.
Default Value: 100
Range: 2-400

Haxl.u. Inbound
Destinations

This is the maximum number of nodes that this node expects to be
communicating with concurrently. with the other nodes initiating
communication. It includes both directly and non-directly connected
nodes.
This field should be configured relatively large to allow for future
communication expansion. Note that changes to this field will not take
effect until the operating system is restarted.
Default Value: 100
Range: 2-600

~
..... ,
flF'·
.

8-9

Network Transport Configuration

GENERAL PROTOCOL CONFIGURATION
The menu screen in Figure 8- 5 is displayed when you press the function key for ~<:.Tc)::"c)PdQT at the
Network Transport Configuration Selection Screen (Figure 8-1), It is also displayed"" "when 'you type the
path name:

@NETXPORT.GPROT
in the command window of any screen and press

(ENTER J.

From this screen you proceed to the screens used to configure the general protocols of the network
transport. All three general protocols must be configured for each node.

Path: NETXPORT.GPROT
IPU

Configure IP Update Protocol

PXP

Configure Packet Exchange Protocol

rcp

Configure Transmission Control Protocol

file:

filename.NET.SYS

Figure 8-5. General Protocol Configuration Screen
Choose the protocol you wish to configure and press the corresponding function key.

8-10

Network Transport Configuration

INTERNET PROTOCOL (lP) UPDATE CONFIGURATION
The screen in Figure 8-6 is displayed when you press the function key for R~II
"'T at the General
Protocol Configuration Screen (Figure 8-5). It is also displayed when you type the path name:

@NETXPORT.GPROT.IPU
in the command window of any screen and press (ENTER J.
This screen is used to supply information to the IPU module. The IPU module is responsible for the
creation and maintenance of the IP internet routing tables which are used to establish connectivity to
remote networks through local network gateways. The information supplied by this screen is required to
put a limit on the memory to be reserved for these tables.
Reserved routing table space is based on the product of the two values configured on this screen.
NOTE

Note that if both maximum values are configured) the space required would
exceed internal memory limitations. The product of the two values should
not exceed 2000.
You must press
to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the :
naB is set to I.

8-11

Network Transport Configuration

'"i!!~~'';'~:;ij~~:;::~~;~~li,i;~!~!:~'!:'''''''''
NETXPORT.GPROT.IPU

Maximum Number Of Networks In Catenet
Maximum Gateway Nodes Per Network

file:

filename.NET.SYS

Figure 8-6. IP Update Configuration Screen

Fields
MaxilDum Number Of
Networks In Catenet

This is the maximum number of networks that the catenet might be
expected to contain. The number is used to allocate routing table space.
Note that networks can be added dynamically (by using the NETCONTROL
UPDATE command) but allocated table space cannot be altered without
stopping the entire transport. It is wise, then, to anticipate growth when
configuring this value to minimize the need to take down the transport to
reconfigure the size of the internet tables.
If more networks are added (via NETCONTROl UPDATE) than there is space
allocated for, a log message will indicate that adding the network would
have exceeded the allocated space and that the IPU module ignored the
uPdate. Consult the NS3000/Y Error Message and Recovery Manual for
the specific IP log message in question.

Default Value: 64
Range: 1-256

8-12

Network Transport Configuration
Related Screens:
- NETXPORT. NI. niName. INTERNET .gatellJayn

This field specIfies networks reachable through a particular gateway. If
more reachable networks are configured than Maximum Networks.
configuration validation will fail.

ltaxl.u. Gateway
Nodes Per Network

This is the maximum number of gateways that there might be on any
network that the node is directly connected to. The number is used,
together with Maximum Networks above, to allocate routing table space.
Note that gateways can be added dynamically (by using the NETCONTROL
UPDATE command) but allocated table space cannot be altered without
stopping the entire transport. As with Maximum Networks above, it is wise
to anticipate growth when configuring this value to minimize the need to
take down the transport to reconfigure the size of the internet tables.
Default Value: 16
Range: 0-64
If more gateways are added (by using the NETCONTROl UPDATE command)
than there IS space allocated for, a log message will indicate that adding the
gateway would have exceeded the allocated space and that the IPU module
ignored the UPDATE.
Consult the NS3000/V Error Meslage and
Recovery Manual for the specific IP log message in question.

8-13

Network Transport Configuration

PACKET EXCHANGE PROTOCOL (PXP) CONFIGURATION
The screen in Figure 8-7 is displayed when you press the function key for ~illlr~l!m~~ at the General
Protocol Configuration Screen (Figure 8-5). It is also displayed when you type the path name:

@NETXPORT.GPROT.PXP
in the command window of any screen and press (ENTER I.
This screen contains the information necessary to configure Packet Exchange Protocol (PXP) for the node.
This screen provides the necessary information for the operation of the PXP protocol. The information
configured falls into two categories:
• Reliability (checksum field)
• Performance parameters (retransmission fields)

NOTE

This protocol must be configured in order for the network transport to
function.
You must press ~i
are creating or updating.
flag is set to

8-14

j,..:... :

to transfer the data displayed on the screen to the configuration file you

You verify that the data record has been created by checking that the '~:'i"'l

Network Transport Configuration

NETXPORT.GPROT.PXP
Checksum Enabled

(V for VESt N for NO)

;I:~

Retransmission Interval (Sees)

I,.

Maximum Retransmissions Per Request

File:

filename.NET.SVS

Figure 8-7. Packet Exchange Protocol Configuration Screen

Fields
Checkau. [nabled

(UP modifiable). Checksumming is a method of error checking. PXP
checksumming causes significant overhead, and is not normally needed for
this protocol. Also, error checking is provided for at the link level. For
these reasons, UP recommends the default value (N) for this field so that
checksumming will be disabled for this protocol.
Default Value: N

Retrana.lssion
Interval (Secs)

The time in seconds to wait for a reply from a remote node before
retransmitting a request. In general, the value to configure should reflect
the load on the local system, the remote system, and the networks through
which the request and the reply must travel.
If the value is set too low, needless retransmissions may occur, or
IPCLOOKUP calls may fail. If the value is set too high, an unneussarily
long delay will occur when a packet is lost and a retransmission is
necessary.

8-IS

Network Transport Configuration
Frequent log messages indicating that retransmissions are taking place or
that requests are failing indicates that the value needs to be increased.
Default Value: 10
Range: 1-600

"8JClmulD
Retrans.lsslons
Per Request

This is the number of times that PXP will retransmit a request when a
reply has not been received within the retransmission interval (explained
above).
As in the discussion of Retransmission Interval above, this field is a tuning
parameter. The two values work together to determine the maximum time
that a PXP user will wait for a reply.
This maximum reply time is calculated as follows:
RTXinterval + (RTXinterval * MAXRTX)
where:
RTXinterval is the configured retransmission interval and MAXRTX is the
configured maximum retransmissions per packet.
Default Value: 4
Range: 1-100

8-16

"'J

Network Transport Configuration

TRANSMISSION CONTROL PROTOCOL (TCP) CONFIGURATION
The screen in Figure 8- 8 is displayed when you press the function key for Qo To TCP at the General
Protocol Configuration Screen (Figure 8-5). It is also displayed when you type the path name:

@NETXPORT.GPROT.TCP
in the command window of any screen and press

(ENTER J.

This screen contains the information necessary to configure Transmission Control Protocol (TCP) for the
node.
NOTE

This protocol is required in order for the network transport to function.
You must press ~pda~,"'''.:'''~~ to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been ~reated by checking that the DlltJ11~
flag is set to
.~.":'.:

:::. : ':':

This screen provides the necessary information for the operation of the TCP protocol. The information
configured falls into three categories:
• Reliability (Checksum field)
• Sizing parameters (Maximum connections fields)
• Performance parameters (Retransmission fields)
The TCP retransmission algorithm is as follows. Per connection, TCP calculates the average packet
acknowledgement delay. It then doubles this time for use as the retransmission timer. For each time that
a particular packet must be retransmitted, the timer set is increased again by the amount of the delay.
For example, should the remote side of an active connection with a calculated delay of 1 second fail, the
retransmission of an outstanding packet would be at intervals of 2, 4, 6, and 8 seconds. A final timer of
10 seconds will be set to wait for the fourth retransmission, bringing the total interval to 30 seconds.
The various configuration retransmission fields work together to establish the initial, minimum and
maximum values for the retransmission timers, and the number of retransmissions that are to be
performed before a connection is broken. If the values are set too low, needless retransmissions may occur,
or connections may be prematurely aborted. If the values are set too high, an unnecessarily long delay
will occur when a packet is lost, and a retransmission will be necessary. All of these retransmission fields
are configurable to optimize connection performance. Values to be entered for the retransmission fields
should, in general, reflect the average load on system resources at the local node, the remote node, and the
intervening network(s), if any. The optimal values for these fields can be determined only by experience
for each node.

8-17

Network Transport Configuration

Path:

NETXPORT. GPROT. TCP
Checksum Enabled

(Y For YES, N For NO)

Maximum Number Of Connections
Retransmission Interval Lower Bound (Sees)
Retransmission Interval Upper Bound (Sees)
Initial Retransmission Interval
(Sees)
Maximum Retransmissions Per Packet
Connection Assurance Interval (Sees)
Maximum Connection Assurance Retransmissions
file:

filename.NET.SYS

Figure 8-8. Transmission Control Protocol Configuration Screen

Fields
Checksu. Enabled

Checksumming is a method of error checking. TCP checksumming causes
significant overhead, and is not normally needed for this protocol. Also,
error checking is provided for at the link level. For these reasons, UP
recommends the default value (N) for this field so that checksumming will
be disabled for this protocol.
The checksum decision for a given connection is determined from several
sources: I) The destination path report, 2) the local configuration (as
specified in this screen) and 3) the values specified in the NetIPC intrinsics,
IPCCONNECT and IPCRECVCN. Should any of these sources indicate
checksumming enabled, the connection will be checksummed.
Note then, that the effect of disabling checksum in the configuration is not
to prohibit checksumming, but to simply allow each connection to choose
for itself. The NS Services specify checksumming disabled in their NetiPC
calls thereby allowing control to be taken through the configuration and
network directory. Therefore, TCP checksumming for NS Services must be
specified in the TCP Configuration screen (via the checksum enabled field),
or within the network directory.
Default Value: N

Range: Y or N

8-18

Network Transport Configuration

Haxi.u. Number of
Connections

All TCP communication occurs over connections.
Each connection
functions as a separate entity in regard to destination, flow control and
retransmissions. There is a one-lo-one correspondence between TCP
connections and NetlPC calls to IPCCONNECT) and therefore between each
NS Service invoked by each user. There is no multiplexing of user or NS
Services data over shared connections.
The number of connections configured should reflect an estimation of the
number of NS Services and NetlPC users that will be active simultaneously.
This includes both outbound and inbound connections. The field should be
configured relatively large to accommodate expansion.
Note that the allocation of buffers is related to the number of TCP
connections. Should this field be modified. the NI screens controlling buffer
allocation (HETXPORT. HI .niName.) must be updated.
Default Value: 128
Range: 1-1024

Ret-rana.laaion Interval The retransmission interval is the time in seconds that a TCP connection

Lower Bound (Sees)

will wait for a reply from a remote node before retransmitting a packet.
The retransmission interval is dynamically adjusted by TCP for each
connection, depending on a number of factors. This field sets the lower
bound for the readjustment.
A general discussion of retransmissions is provided in the overall description
of this screen above.
Default Value: 4
Range: 2-600

Retrana.laslon Interval The retransmission interval is dynamically adjusted by TCP for each
Upper Bound (Sees)

connection, depending on a number of factors. This field sets the upper
bound for the readjustment.
A general discussion of retransmissions is provided in the overall description
of this screen above.
Default Value: 120
RaDle: 2-600

Initial Retrans.18sion This field sets the initial amount of time that TCP will wait for a reply
from a remote node before attempting to retransmit a packet. This value is
Interval (&ees)
used for connection setup when the retransmission interval has not yet been
calculated. It must be in the range of the lower and upper bound The
default of 4 with the default Maximum Retransmissions Per Packet of 4
will cause TCP to wait a total of 60 seconds when attempting a connection
to a non-responding system.

8-19

Network Transport Configuration

A general discussion of retransmissions is provided in the overall description
~
of this screen a b o v e . ' )
Default Value: 4
Range: 2 -600

Haxi.u.
Retrans.lsslons
Per Packet

This is the maximum number of times that TCP will retransmit a packet
before aborting the connection. Together with the Lower and Upper
Bound configuration) and the dynamically calculated delay) it controls the
total time interval TCP will wait before aborting a non-responding
connection.
Default Value: 4
Range: 1-100

Connection Assurance
Interval (Secs)

(HP modifiable.) The TCP protocol guarantees the integrity of connections
so long as they are actively in use through the use of TCP)s retransmission
timer. However, guaranteeing the integrity of idle connections requires
that TCP exchange protocol packets at some timed interval. This field
allows the configuration of the interval at which these connection
assurance packets will be exchanged.
Default Value: 600
Range: 1-600

Haxi.um Connection
Assurance
Retrans.lsslons

(HP modifiable.) This is the maximum number of times that TCP will
transmit a connection assurance packet to a non-responding remote system.
Together with the Connection Assurance Interval, this field defines the
time it will take for an idle connection to abort if the remote TCP fails to
respond. Unlike the retransmission timer, a backoff algorithm is not used.
Therefore, the timeout period is calculated as follows:
CAinterval + (CAinterval * MAXCARTX)
Default Value: 3
Range: 1-100

8-20

Network Transport Configuration

NETWORK INTERFACE CONFIGURATION
The select screen in Figure 8-9 is displayed when you press the function key for ~~::
I at the
Network Transport Configuration Selection Screen (Figure 8-1). It is also displayed when you type the
path name:
@NETXPORT.NI

in the command window of any screen and press

(ENTER J.

Use the fields and the function keys of the select screen to perform the desired action.
• To define a new NI configuration, specify the NI name and the NI type; then press III. The
path for the selected NI name is added to the configuration file. and the data screen on that path
is displayed.
• To modify an existing NI configuration, specify the NI name; then press _ . The data screen
on the path for the specified NI name is displayed.

;.':.

• To change the name of an existing NI configuration, specify the NI name and a new name; then
press ~.,r
The previously configured Nt name is replaced and the screen displays the new
name'Iil'a"display field under the label Configured Network Interfaces.
• To delete an existing NI configuration, specify the NI name; then press :n! ".. "",,,,. :. Press ;: ,:
again to confirm the deletion. If you do not press ~l~~~~ a second time. the deletion will not
occur. The previously configured NI name is deleted and is no longer displayed in a display field
under the label Configured Network Interfaces.
The network interface is responsible for providing the interface between network transport protocols and
link protocols. It also provides the software loopback capability.

8-21

Network Transport Configuration

~.~: ')

Network Interface Name
New Name

:::~;lli!J.:

LOOP,LAN802.3,
Type : ROUTER ,GATEHALf'

(if new)

Configured Network Interfaces
Name

Type

Name

Type

Name

Type

Figure 8-9. Network Interface Configuration Screen

Fields
Network Interface
Nue

Select the network interface name for one of the following: 1) software
loopback capability, 2) LAN 802. 3 network connection, 3) router network
or 4) gateway half.
The Network Interface Name can contain as many as eight alphanumeric
characters; first character must be alphabetic.

Type (LOOP,

(Required only when adding.) Enter the appropriate type:

LAN802.3,
ROUTER, or
GATEHALF)

LOOP to identify the software loopback capability.
LAN802.3 to identify the LAN 802. 3 network connection.
ROUTER to identify a router network.
GATEHALF to identify a gateway half.

New Halle

8-22

(Required only when renaming.) Enter a new NI name. The new name can
contain as many as eight alphanumeric characters, and the first character
must be alphabetic. You need to specify a new name only when renaming
an existing Nt

LAN802.3 NETWORK
L---IN_T_E_RF_A_C_E_C_O_N_F_IG_U_R_A_T_IO_N

The screens described in this section are used for configuring a node with a LAN802. 3 network interface.
All IEEE 802.3 networks must have a LAN802.3 network interface configured for each node. This
includes nodes using ThinLAN/3000 Links (including ThickLAN) and StarLAN/3000 Links.
Configuration of the LAN 802.3 network interface branch of NMMGR begins with the LAN802. 3
NETWORK INTERfACE CONfIGURATION screen. From this screen, you can proceed to a number of other
screens needed to complete network interface configuration. The screens are listed and briefly described
below, with the level of indentation shown indicating each screen's place in the configuration hierarchy.

LAN802.3 NETWORK INTERFACE CONfIGURATION - This screen allows you to configure items needed
for any IEEE 802. 3 network interface: numbers of buffers, the maximum number of nodes in the
network, an address used by the Probe protocol, and whether to load IP to IEEE 802.3 address information
from the node's network directory. From this screen, you can choose to go to one of four screens that
begin lower branches of configuration.
PROTOCOL CONfIGURATION - This screen, which you reach by pressing ~:m:1t~:;;~:~gt~~~ on
the previous screen, allows you to proceed to configure the IP or Probe protocols.
IP PROTOCOL CONFIGURATION - This screen enables you to enter information needed
for the operation of the IP protocol on this node.
PROBE PROTOCOL CONfIGURATION - This screen enables you to enter information
needed for the operation of the Probe protocol on this node.
NETWORK INTERfACE LINKS - This screen, which is displayed after you press ~ '1"
']1.1 on
the LAN802. 3 NETWORK INTERfACE CONfIGURATION screen, allows you to specify a link 'name
(as configured in the link configuration branch of NMMGR), and to specify that it is of type
LAN (used for all IEEE 802.3 links).
LAN LINK CONFIGURATION - This screen contains default values for the LAN link
defined in the previous screen that cannot be changed.
NEIGHBOR GATENAYS - This screen appears after you press :::,::"" ';~;:;f:it~N.UII. on the LAN802. 3
NETWORK INTERfACE CONfIGURATION screen. It begins·'ihe branch·'ofI~'AN802. 3 network
interface configuration that allows you to configure internet information. In this screen, you
can identify the nodes in the network that will be functioning as gateways to other networks.
Note: Internet configuration is not needed if this network is not connected to any other
networks, or if its nodes are connected to other personal computers only, and not to other HP
3000s or other computers that perform internet routing.
NEIGHBOR GATEWAY REACHABLE NETHORKS - You must configure an instance of this
screen for each of the gateways identified in the previous screen. In this screen. you
will specify information about each of the networks that can be reached by a
particular gateway.
LAN802.3

HAPPING

CONFIGURATION - This screen, which you will reach by pressing
NETWORK INTERFACE CONfIGURATION screen, begins a
branch of configuration that enables you to provide information about a non-UP computer's
addresses.
For UP computers, this information is provided by the Probe protocol, and
~. roJ~"P.PI"G on the LAN802.3

9-1

LAN802.3 Network Interface Configuration

configuration of this and the subsequent screen in thIs branch is unnecessary. In this screen. you
will identify the non -HP node.
STATIC NEIGHBOR NODE CONFIGURATION (LAN802.3) - An instance of this screen
must be configured for every non-liP node identified on the previous screen. You will
configure a node's IP and IEEE 802. 3 addresses here.

NOTE
Configurable fields described in this manual are required unless otherwise
stated.

Fields described as "liP modifiable" should be changed only upon the
recommendation of your UP representative.
On the screens shown in this section, fields that must be configured when
performing guided confjguration are underlined

9-2

LAN 802. 3 Network Interface Configuration

LAN802.3 NETWORK INTERFACE CONFIGURATION
The screen in Figure 9-1 is displayed when you select an NI name and the NI type LAN802. 3 at the

Network Interface Configuration SCreen (Figure 8-9) and press. or
you type the path name:

IIIIB.

It is also displayed when

@NETXPORT.NI.niName
in the command window of any screen and press
NI name.

(ENTER).

where the niNams is the configured LAN801. 3

Use the screen in Figure 9-1 to configure a LAN network interface. The LAN 802. 3 Network Interface
(NJ) module serves to interface the upper layers 'of the transport product to the 1£££801. 3 link layer.

Thil screen supplies the information required for that interface. All of the fields, with the exception of
the lIP UPC Number. are used for internal resource allocation.
You must press .
~:'::~;II to transfer the data displayed on the screen to the configuration file you
are creating or updating. After pressing ,,;:~!""W
"::111 verify that the data record has been c;reated by
cheeking that the .illl flag is set to !flo
From this screen you proceed to the screens used to configure the LAN link. internet routina. and the
IEEE802. 3 address mapping&.

!!!hi NETXPORT.NI.niName
Network Segment Size (Bytes)
Number Of Inbound Buffers
Number Of Outbound Buffers
Maximum Number Of Nodes In Network
HP UPC Number (Hex XX-XX-XX)

File:

fllename.NET.SYS

Figure 9-1. LANaO".3 Network Interface Configuration Screen

9-3

LAN802. 3 Network Interface Configuration

Choose the item you wish to configure, and press the corresponding key.
The only time you need to press ~~l!I!!~o=','M~·p:p~"9. is when your LAN includes non-HP nodes. You do not
need to configure mapping if any proxy node in the network already includes the mapping information in
its network directory. Non-HP nodes do not support the Probe protocol. Therefore, you must configure
mapping information about non-HP nodes so that other nodes on your LAN can communicate with them.

Fields
Network Segment
Size

(HP modifiable). This field specifies the largest packet (data + protocol
headers and not including the IEEE802.3 header) that will be sent by the
LAN device (LANIC board).
The only reason for entering a value smaller than 1497 is to make better
use of memory for those systems where it is known that upper layer services
will always send shorter messages. Note that whenever packets larger than
the network segment size are sent, they will be fragmented to the network
segment size, thus incurring fragmentation overhead at the source and
assembly overhead at the destination node.
Default Value: 1497 bytes
Range: 300-1497

Number Of'
Inbound Buffers

This field specifies the number of buffers to be allocated for inbound data.
Buffer configuration is based on the number of TCP connections that will
use a given network interface. An allocation of two buffers per connection
will suffice for typical usage.
The default value is based on the assumption that the network manager
desires to allow no more than the default number of TCP connections (see
Related
Screens
below)
to
use
the
LAN NI.
Hence
the default is 128 (default TCP connections) 2 256 buffers. When there
is more than one NI, this value should probably be adjusted downward, since
the connections might reasonably be expected to be using more than one NI
at anyone time. If the number of TCP connections is changed from the·
default value, the number of inbound buffers for all NI's should be
reconsidered.

Whenever there are not enough buffers to support inbound traffic, an IP
log message will indicate that the node is congested and the packet had to
be discarded. See the NS3000/V Error Message and Recovery Manual for
the exact IP log location and message. Repeated occurrence of this log
message indicates that more inbound buffers need to be configured
Related Screens:
- NETXPORT •GPROT •TCP

Maximum Number Of Connections is configured here. Default value is
128.
Default Value: 256

9-4

LAN 802. 3 Network Interface Configuration

Range: 32-2048

Nu.ber Of
Ou\bound Buffers

This field specifies the number of buffers to be allocated for outbound
data. Outbound buffers are used for outbound data packets and are held
by the transport until they are acknowledged by the destination node.
Underallocation may adversely affect TCP throughput. Calculation of
default values is as described above for inbound buffers.
Related Screens:

-NETXPORT.GPROT.TCP
The Maximum Number Of Connections is configured bere. If it is
increased, consider increasing the number of outbound buffen also.
Default Value: 256
Range: 32-2048

ttaxl.u. Nu.ber Of
Nodes In Network

This number should equal the anticipated maximum number of nodes on
the LAN. The number is used to allocate space for IP to IEEE802. 3
address mappings that are obtained by the Probe protocol If the maximum
number of nodes is set too low and there is not enough room in the mapping
table when a mapping entry needs to be made, a Probe error message is
logged. See the NS3000/V Error Message and Recover, Manual for the
exact log location and message.
It is wise to anticipate growth when configuring this value to minimize the
need to shut down the transport subsystem to reconfigure this field.
Related Screens:

- NEXPORT. GLOBAL
Maximum Number Of Nodes In Network is a component of the
computation of Haxlmu. Direct.ly Connected Nodes on the
NETXPOR.T. GLOBAL screen.
Default Value: 100
Range: 1-1024

HP UPC Nullber

(UP modifiable.) The UP universal product code, which is used to establish
an UP-unique address used by the Probe protocol.
Default Value: 08-00-09
Only change the default in rare circumstances. If all nodes on the
IEEE802.3 LAN are not configured with identical HP UPC numbers, Probe
multicasts will not be be universally recognized on the LAN.

9-5

LAN802.3 Network Interface Configuration

PROTOCOL CONFIGURATION
The menu screen in Figure 9-2 is displayed when you press the function key for ~..
;~9:~Q~ at the
LAN 802. 3 Network Interface Configuration Screen (Figure 9-1). It is also displayed when you type the
path name:

@NETXPORT.NI.niName.PROTOCOL
in the command window of any screen and press [ENTER I, where niNa". is the configured LAN802. 3 NI
name.
For the LAN802.3 NI, you must configure both the IP and Probe protocols.
If'
._
and the :~:::~. :m~'ie function key labels are displayed.

-Path:

NETXPORT. NI •niName. PROTOCOL

Configure Internet Protocol

PROBE

Configure PROBE Protocol (LAN Only)

DIAL

Configure DIAL Protocol (Router/Gateway Half Only)
Necessary Only If There Are Any Switched Links

File:
--

filename.NET.SYS

Figure 9-20. Protocol Configuration Sereen
Choose the protocol to configure, and press the corresponding function key.

9-6

Therefore. both the

LAN802. 3 Network Interface Configuration

INTERNET PROTOCOL CONFIGURATION
The screen in Figure 9-3 is displayed when you press the function key for.
Configuration Screen (Figure 9-2~ It is also displayed when you type the path name:

. at the Protocol

@NETXPORT.NI.niName.PROTOCOL.IP
in the command window of any screen and press (ENTERI. where ni'QftI is the configured LAN801. 3 NI

name.
This data-entry screen is used to supply information to the IP protocol instance for the network being
configured. Each Nt has an IP protocol The IP address field is a key element in IP routing and datagram
delivery algorithms. The other fields are useful for internal resource allocation and performance tuning.

. to transfer the data displayed on the screen to the configuration file you
You must press ,
are creating or uPdating- You verify that the data record has been created by checking that the
nag is set to I_

-Path:

NETXPORT.NI.niName. PROTOCOL. IP
Store • forward Buffers
(Enter 0 To Disable Store • fonward)
IP Internet Address
Internal Message Queue Length
Fragment Assembly Queue Elements

f!!!l

filename.NET.SVS

Filure 9-3. IP ProtGOOl ConfilUrattoR Screen

9-7

LAN802.3 Network Interface Configuration

Fields
Store & Forward
Bufters

(HP modifiable.) This field allocates buffers to support store-and-forward
over the network interface being configured. You do not need to allocate
store-and-forward buffers if the node you are configuring is a
non-gateway node on this IEEE 802.3 network. You will need to allocate
store and forward buffers if the node being configured is an internet
gateway and packets from another network will be forwarded over this
network interface.
This number of store-and-forward buffers is configurable to allow
performance tuning for different network types.
However, UP
recommends that you use the default number of store-and-forward buffen
(20), and that you consult your HP representative before modifying this
value.
Default Value: 20

NOTE

If this node is a non-gateway node on an
IEEE 802. 3 network and you are concerned
about conserving MPE resources, you may
No
wish to set this field to O.
store-and -forward buffers will then be
allocated.

Range: 0-50

IP Internet Address

Enter the internet protocol (IP) address for the network interface being
configured.
Addresses are made up of a network portion and a node portion. The
supported classes of network addresses have the following forms (Note: 4.
space):

Class C
Class B
Class A

C4nnn.nnn.nnn4xxx
B4nnn.nnn4xxx.xxx
A4nnn4xxx.xxx.xxx

where nnn is a value ranging from 0 to 255, representing eight bits of the
network portion of an address. The leftmost group of nnn has the
following ranges for each address class:
I

Class C:
Class B:
Class A:

192-223
128-191
0-127

where xxx is a value rangIng from 0 to 255, representing the node portion
of the address.

9-8

LAN802.3 Network Interface Configuration

Default Value: N

Internal Hessage
Queue Length

(HP modifiable.) This field puts a limit on the number of internal resourus
that the IP protocol may hold while awaiting some other protocol module
action. It is a tuning parameter that should be modified only upon the
recommendation of your HP representative.
The default is set to handle most cases; if it is too low for your network.
packets will be discarded and you will receive a logging error message.
Consult the NS3000/Y Error Message and Recovery Manual for the
specific log message.
Default value: 4
Range: 0-20

Frau-ent Asse.bly
Queue [leaaenta

(HP modifiable.) This field specifies the maximum number of incomplete
message fragments that this IP instance may hold.
HP recommends that you use the default of 20 for this field. For purposes
of tuning your network·s performance. and upon the recommendation of
your HP representative. you may wish to alter the number of Fragment
Assembly Queue Elements.
You may wish to configure a higher value if traffic conditions on your
network are less than optimal; e.g.• if internet routes are heavily loaded and
intermediate nodes are congested. If conditions on your network are less
busy. you may wish to configure a lower value. Only configure 0 if no
fragmented messages will ever be received by the node you are configuring.
If message fragments are discarded. (indicating that the value configured in
this field is too low) a log message will be recorded. Refer to the
NS3000/V Error Message and Recovery Manual for a description of the
message you receive.
Default value: 20
Range: 0-100

9-9

LAN 802. 3 Network Interface Configuration

PROBE PROTOCOL CONFIGURA TION
The screen in Figure 9-4 is displayed when you press the function key for O,o:·To···:~Q. at the Protocol
Configuration Screen (Figure 9-2). It is also displayed when you type the path name:···· .......

@NETXPORT.NI.niName.PROTOCOL.PROBE
in the command window of any screen and press [ENTER I) where niName is the configured LAN 802. 3 NI
name.
This data-entry screen allows you to configure the information required for the Probe protocol. The
Probe protocol exists on a LAN 802. 3 network to provide a means of exchanging addressing and naming
information between nodes.
You must press V~~~i;~::Pa.;~' to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the fi~t.:l~
flag is set to II.

f!!hl

•

NETXPORT.NI.niName.PROTOCOL.PROBE
Proxy Enabled

Probe Requests

(V For VES, N For NO)

Proxy Requests
I."

r!.;·

I.,:, .
i• •.!ih:::

File:

Retransmission Maximum
Retransmission Timeout (X100ms)

filename.NET.SVS

Figure 9-4. Probe Protocol Configuration Screen

9-10

LAN 802. 3 Network Interface Configuration

Fields
Proxy Enabled

Proxy nodes exist on LANs to provide node name and address mapping
facilities for nodes that do not have local network directories. Proxy
requests are multicast on the LAN to request information about a third
party node from a proxy node.
YES enables this node to be a proxy server and to answer all proxy requests
on this LAN. NO means that this node will ignore all proxy requests on this
LAN network.
Other proxy related fields on this screen are:
- Proxy Requests Retransmission Maximum
- Proxy Requests Retransmission Timeout
Proxy related fields on other screens are:
- HP UPC Number on LAN802. 3 Network Interface screen
Default Value: N
Range: V or N

Probe Requests
Retrans.isslon
Maxi.u.

This is the maximum number of retransmissions of Probe requests (Name
Requests and Address Requests) before a Probe failure is reported.
Because it is unlikely that Probe-request data is being lost. HP recommends
that you keep the maximum number of retransmissions low.
Default Value: 2
Range: 1-10

Probe Requests
Retrans.isslon
TilleOut
(x 100•• )

This field is for specifying the time limit between retransmissions of Probe
requests. This is the time interval (in tenths of a second) that the Probe
protocol will wait for a reply before attempting to retransmit a request.
The value should be set sufficiently large to avoid retransmissions in a
temporarily overloaded environment. yet small enough to get a timely
failure report when failure is inevitable.
Default Value: 10
Range: 1-100

9-11

LAN802.3 Network Interface Configuration

Proxy Requests
Retran••lsslon
Haxl.u.

The maximum number of retransmissions of proxy requests before a Probe
failure is reported.
Because it is unlikely that Probe-request data is being lost. UP recommends
that you keep the maximum number of retransmissions low.
Default Value: 2
Range: 1-10

Proxy Requests
Retrans.lsslon
TilleOut
(x 100•• )

The time interval (in tenths of a second) that the Probe protocol will wait
for a reply before attempting to retransmit a proxy request. The value
should be set sufficiently large to avoid retransmissions in a temporarily
overloaded environment, yet small enough to get a timely failure report
when failure is inevitable.
The default value is set somewhat higher than for Probe requests timeout
because proxy requests involve a network directory lookup and
consequently more time than regular Probe requests.
Default Value: 40
Range: 1-1 00

9-12

LAN 802. 3 Network Interface Configuration

LAN802.3 NETWORK INTERFACE LINK
The select screen in Figure 9-5 is displayed when you press the function key for IL~~
j' :"'~ at the
LANI02.3 Network Interface Configuration Screen (Figure 9-1). It is also displayed when you type the
path name:

@NETXPORT.NI.niName.LINK
in the command window of any screen a·nd press [ENTER., where niName is the configured LAN801. 3 NI
name.
Use the fields and the function keys of this select screen to perform the desired action.
• To define a new link configuration, specify the link name; then press III. The path for the
selected link name is added to the configuration file, and the data screen on the path is displayed.
• To modify an existing link configuration, specify the link name; then press ....'
"~I
screen on the path for the specified link is displayed. .

"The data

••••

• To change the link name of an existing link configuration, specify the link name and a new name;
then press::l. .b::"::::.:=:::' The previously configured name is replaced, and the screen displays the new
name in a display field under the label Configured Network Links.
• To delete an existing link configuration, specify the link name; then press 1111111. Press
again to confirm the deletion. If you do not press :::.::
'fl a second time, the deletion will not
occur. The previously configured name is deleted and is no longer displayed in a display field
under the label Configured Network Links.

9-13

LAN802.3 Network Interface Configuration

•

,.~

Path:

NETXPORT.NI.niName.LINK
Link Name
New Name

LAN - LAN

(if new)
Configured Network Links

Name

Type

Name

Figure

Type

Name

Type

'-5. LAN802.3 Network Interface Link Screen

Fields
Link Hue

Enter the link name from the LAN802. 3 Link configuration to allow the
Network Transport to associate the correct link with the LAN 802. 3 Nt.
The link name can contain as many as eight alphanumeric characters, and
the first character must be alphabetic.
The link name is used by the Network Transport when establishing
connections.
Related Screens:
The Link name on this screen must match the link name in the Link name
field of the LINK CONFIGURATION screen whose pathname is LINKCONF.

Type

(Required when adding.) Enter LAN as the link type.

New Nue

(Required when renaming.) Enter a link name. This new link name is used
in place of the current link name for an existing link configuration. The
name can contain as many as eight alphanumeric characters, and the first
character must be alphabetic.

9-14

LAN 802. 3 Network Interface Configuration

LAN LINK· CONFIGURATION
The screen In Figure 9-1) IS displayed when you select an NI link name at the LAN802.3 Network
Interface Link Screen (Figure 9-5) and press l\~d or P,~.·~~,. It is also displayed when you type the path
name:
.

@NETXPORT.NI.niName.LINK.nilink
in the command window of any screen and press (ENTER I, where niName is the configured LAN 802. 3 NI
name and nil ink is the configured LAN802. 3 Nilink name.
This screen supplies the information required to interface the LAN NI to a LAN802. 3 link.
You must press U~a,~qala to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the bi£._~;j
flag is set to ~ . ' ' ' ' ' ' ' '
...
q • •-

Path:

NETXPORT.NI.niName.LINK.nilink

i:r~l

Start Device On Network Initialization (yIN)

1~;J-

Enable Idle Device Timer (YIN)

File:

filename.NET.SYS

Figure 9-6. LAN Link Configuration Screen

9-15

LAN802.3 Network Interface Configuration

Fields
Start Device

(Display only.) A YES value means that the device is to be started when a
NETCONTROL START command is issued for the network interface. For the
LAN, this is always the case, and therefore this field cannot be changed.
Default Value: Y

Enable Idle
Device Tiller

(Display only.)
Specifies whether the device is to be disconnected
automatically if no packets are received or transmitted over the link during
a specified time period. This does not apply to the LAN.
Default Value: N

9-16

LAN802.3 Network Interface Configuration

NEIGHBOR GATEW A YS
The select screen in Figure 9-7 is displayed when you press the function key for ~;:':~~~;j:::l,~lI"f:il~Iat the
LAN802.3 Network Interface Configuration Screen (Figure 9-1). It is also displayed when you type the
path name:

@NETXPORT.NI.niName.INTERNET
in the command window of any screen and press (ENTER I, where the niName is the configured LAN 802. 3
NI name.
You only need to configure this screen) and the screens that follow it, if the node you are configuring is a
gateway (full or half) node.
Use the fields and the function keys of this select screen to perform the desired action.
• To define a new gateway configuration, specify the gateway name; then press ilc.I~. The path for
the selected gateway name is added to the configuration file, and the data screen on the path is
displayed.
• To modify an existing gateway configuration) specify the gateway name; then press
data screen on the path for the specified gateway is displayed.

_tli.

The

• To change the gateway name of an existing gateway configuration, specify the gateway name and
a new name; then press A~"am... The previously configured name is replaced, and the screen
displays the new name in a"dlsp'tay field under the label Configured Gateways.
• To delete an existing gateway configuration, specify the gateway name; then press ::' . ;r~~I~. Press
. :"::'::~~ again to confirm the deletion. If you do not press . . .::'J~i a second time, the deletion
will not occur. The previously configured name is deleted and is no longer displayed in a display
field under the label Configured Gateways.
From this screen you proceed to the screen used to configure names of all networks reachable from this
gateway node.

9-17

LAN802.3 Network Interface Configuration

~1~li~~~~~i!~~~~,::~,~;~~;;~,:~!1~~~']~~i::;,:,,;:;:,,~;~H;'~;;,:":;fm!;~~i;ij~~;i:i!i~~~i[~'i!i~~~J~~~~~;~~f!~;:"
Path:

NETXPORT.NI.niName.INTERNET

Configured Gateways

Figure 9-7. Neighbor Gateways Screen

Fields
Gateway Name

Enter a name to represent a gateway on this LAN802. 3 network, through
which one or more remote networks can be reached. A gateway name can
contain as many as eight alphanumeric characters; the first character must
be alphabetic.

New Name

(Required only when renaming.) Enter a gateway name to represent a
neighbor gateway. This new gateway name is used in place of the current
gateway name for an existing gateway configuration. The name can
contain as many as eight alphanumeric characters; the first character must
be alphabetic.

9-18

LAN 801.3 Network Interface Configuration

NEIGHBOR GATEW A Y REACHABLE NETWORKS
The screen in Figure 9-8 is displayed when you select a gateway name at the Neighbor Gateways Screen
(Figure 9-7) and press A~I or IJI~I•. It is also displayed when you type the path name:
@NETXPORT.NI.niNam8.INTERNET.gate~yn

in the command window of any screen and press (ENTER J, where niName is the configured LAN 801. 3 NI
name, and gatelJayn is the configured LAN801. 3 NI gateway name.

':lilt/I to transfer the data displayed
After you have entered all the required data, you must press ~H~I;:
on the screen to the configuration file you are creating or updating. Y~;;:;~erify that the data record has
been created by checking that the .",,···;:::::l~: flag is set to II.

Neighbor Gateway IP Internet Address
Configured Reachable Networks
IP Network Address

Hops

PAGE 1

IP Network Addre88

Hops

Figure 9-8. Neighbor Gateway Reacbable Networks ScreeD

9-19

LAN802.3 Network Interface Configuration
NOTE

The information configured in this screen can extend to more than one
page, if necessary, to allow configuration of more than 10 reachable
networks. Press N~~~~ji;:~ge to proceed to a new page. Press :~~~:~m!bl~ to
display a prior page. Use ~.~:rsi"·;!:·~ge to display the first page (for
example, if you are viewing the third page, pressing ~;~lf..~·::;::~9~ will
immediately display the first page). Press ~~iJ,;jl!it~l! to display the last
page of reachable networks that has been configured. To consolidate
reachable networks entries (from several pages, for example) press
~~n~~ii~:U:[~gi·

Fields
Neighbor Gateway
IP Internet Address

Enter the full network address of a gateway node (on this network) that is
to be used to reach other networks (any network in the same catenet other
than the network of which this node is a member). The network portion of
the address must be the same as that entered on the IP Protocol
Configuration screen for the network interface you are configuring (see
Related Screens, below).
Addresses are made up of a network portion and a node portion. The
possible classes of network addresses have the following forms (4a a space~

Class C
Class B
Class A

C4nnn.nnn.nnn4xxx
84nnn.nnn4xxx.xxx
A4nnn4xxx.xxx.xxx

where nnn is a value ranging from 0 to 255, representing eight bits of the
network portion of an address, and xxx is a value ranging from 0 to 255,
representing the node portion of the address. The leftmost group of nnn
has the following ranges for each address class:

Class C:
Class B:
Class A:

192-223
128-191
0- 127

Default Value: None
Related Screens:
- NETXPORT .NI .niName. PROTOCOL. IP
The network address (network portion of the IP address) configured in this
screen must match the Neighbor Gateway IP Internet Address configured in
the current screen.

9-20

LAN 802.3 Network,lnterface Configuration

Configured Reachable
Networks IP Network
Address

Enter the internet addresses of the remote networks that can be reached
through the gateway whose network address is configured in the previous
field. Only the internet portion of the network address is significant for
this field (see above for valid formats of internet addresses). The node
portion must be entered; however, it may be set to all zeros.
Related Screens:
- NETXPORT .NI .niName. INTERNET

This pathname corresponds to the Neighbor Gateways screen. A Neighbor
Gateway Reachable Networks screen must be configured for each gateway
configured in the Neighbor Gateways screen.

Configured Reachable
Networks Hops

Enter the internet hop count to the reachable network whose IP address is
configured to the left of the Hops field. (The internet hop count is the
number of full internet gateways that will be used to route a message to the
destination network. If two partner gateway halves are used as part of the
internet route, they are counted as one hop.)
Hop count is used internally to determine which neighbor gateway (if more
than one exists) is on the shortest path to the remote network. If more than
one gateway can reach a given remote network, and the number of hops to
the remote network is equal for each gateway, you can specify which
gateway the Network Transport will use by configuring an artificially high
hop count. The Network Transport will always use the gateway with the
lowest hop count.
If the same hop count value is configured for multiple gateways, then the
Network Transport will choose internally from among the routes with
equal hop counts.
Default Value: None

Range: 1-32167

NOTE

To delete a reachable network entry, fill the field to be deleted with blanks
and press ~Pd.~te'f;i~:t.a.

9-21

LAN 802. 3 Network Interface Configuration

LAN802.3 MAPPING CONFIGURATION
The select screen in Figure 9-11 is displayed when you press the function key for :;... ;';'i:;;~:::J"A:el'~~ at the
LAN 802.3 Network Interface Configuration Screen (Figure 9-1). It is also displayed when you type the
path name:

@NETXPORT.NI.niName.MAPPING
in the command window of any screen and press (ENTER I) where the niName is the configured LAN 802. 3
NI name.
Mapping information is required only when you have non-UP nodes on a LAN. This is because non-UP
nodes do not support the Probe Protocol) and they do not have LAN802.3 addresses configured in the
network directory. Mapping information pertaining to a non-HP node is used by other nodes to
communicate with the non-UP node.
Use the fields and the function keys of this select screen to perform the desired action.

• To define a new mapping configuration) specify the mapping name; then press ~~~. The Path for
the selected mapping name is added to the configuration file) and the data screen on the path is
displayed.

9-22

LAN 802. 3 Network Interface Configuration

Static Neighbor Node Name
New Name
Configured Mappings

Figure 9-11. Mapping Configuration Screen

Fields
Static Neigbor
NodeNue

Enter a mapping name to represent the non-UP node for which you are
configuring mapping information. A mapping name can contain as many
as eight alphanumeric characters. and the first character must be
alphabetic.

New N..-

(Required only when renaming.) Enter a mapping name. This new
mapping name is used in place of the current mapping name for an existing
mapping configuration.
The name can contain as many as eight
alphanumeric characters, and the first character must be alphabetic.

9-23

LAN 802. 3 Network Interface Configuration

STATIC NEIGHBOR NODE CONFIGURATION (LAN802.3)
The screen in Figure 9-12 is displayed when you select a mapping name at the Mapping Configuration
Screen (Figure 9-11) and press ~~~ or P,~~~•. It is also displayed when you type the path name:

@NETXPORT.NI.niName.MAPPING.neighbor
in the command window of any screen and press (ENTER I, where niName is the configured LAN 802. 3
network interface name, and neighbor is the configured mapping name.
This screen provides IP-to-IEEE802. 3 address mapping for other nodes on the LAN. This mapping is
normally provided by the Probe protocol. To reach non -HP nodes (that do not support the Probe
protocol), the mapping can be configured in the local network directory. Should a node choose not to
support a network directory, this screen is the last alternative to supply address mappings.
You must press ~;~!~~:llll: 'i~i to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the 1!~ll~1
flag is set to I.

IP Internet Address
i!(!~llJ~

I EEE802 • 3 I P SAP (Hex)

ll[:liilmmr

I EEE802 • 3 Add res s

File:

filename.NET.SYS

Figure 9-12. Static Neighbor Node Configuration Screen

9-24

LAN802.3 Network Interface Configuration

Fields
IP Internet Address

This is the full network address of a non-HP node. Note that the network
portion of the address must be the same as that entered on the IP Protocol
Configuration screen. (See related screens below.)
Addresses are made up of a network portion and a node portion. The
supported classes of network addresses have the following forms:

Class C
Class B
Class A
Loopback

C4nnn.nnn.nnn4xxx
84nnn.nnn6xxx.xxx
A4nnndxxx.xxx.xxx
E4255.255.255.255

where 4 denotes a blank space, and nnn is a value ranging from 255,
representing eight bits of the network portion of an address. The leftmost
group of nnn has the following ranges for each address class:

Class C:
Class B:
Class A:

192-223
128-191
0-121

and xxx is a value ranging from 0 to 255, representing the node portion of
the address. Note also that a space is used to delimit the boundary between
the network portion and the node portion of the address.
Default Value: N
Related Screens:

- NETXPORT. NI. niName. PROTOCOL. IP. The network address (network
portion of the IP address) in this screen must match the IP internet address
configured in the current screen.

1[[[802.3 IP SAP

(HP modifiable). The protocol ID assigned to the Internet Protocol (IP) by
ARPA.
Default Value: 06

1[[[802.3 Address

The IEEE802. 3 station address of the destination node.

9-25

.~
,-.

ROUTER NETWORK
L- INTERFACE CONFIGURATION

The screens described in this section are used for configuring a node with a router network interface.
There are four main branches of router network interface configuration. These are reached by choosing
different function keys displayed on the first screen, called the ROUTER NETWORK INTERFACE screen.
All of the router network interface configuration screens are listed below, with their places in the
configuration tree indicated by indentation.

ROUTER NETWORK' INTERFACE 'CONFIGURATION - This screen enables you to configure information
about a router network interface. such as the number of inbound and outbound buffers. the size of an
internal table that holds information about routes, and the network hop count. From this screen, you can
proceed to one of four branches of router NI configuration: protocol configuration. link configuration,
internet configuration. and mapping configuration.
PROTOCOL CONFIGURATION - You will reach this screen if you press ~l!jmtl;Jmft~~~~ on the
ROUTER NETWORK INTERfACE CONFIGURATION screen. This screen allows you', to choose to
proceed to either IP or DIAL protocol configuration.
IPPROTOCOL CONFIGURATION - This screen. which you will reach by pressing
XP on the previous screen. enables you to configure the number of store and
forward' buffers on this node, the node·s IP address, and tuning parameters for the IP
protocol.
~,To

DIAL ID PROTOCOL CONFIGURATION - This screen enables you to configure
information about a dial link that is used by the Dial ID protocol--retransmission
information, and whether security is in effect.
SECURITY STRING(S) CONFIGURATION - This screen allows you to specify
the security strings used by the Dial ID protocol.
ROUTER NETWORK INTERFACE LINKS - This screen. which you will reach by pressing
9oT9.Link on the ROUTER NETWORK INTERfACE CONfIGURATION screen, allows you to
specify the name of the link (as previously configured in the LINK CONFIGURATION screen). and
whether the link is a direct dial, shared dial, or direct connect link.
DIRECT CONNECT LINK CONFIGURATION - This screen, which NMMGR displays
when you specify a direct connect link in the previous screen. allows you to enter
information pertaining to the direct connect link.
ROUTER DIAL LINK CONFIGURATION - This screen. which NMMGR displays when
you specify a direct dial or shared dial link in the previous screen. allows you to enable
or disable the Dial ID protocol.
NEIGHBOR GATEWAYS - This screen, which you will reach by pressing ~:;:[Ilt:~mi,'~~J'H."g on the
ROUTER NETWORK INTERfACE CONfIGURATION screen. permits you to specify the nodes that
will be functioning as gateways to other netw<;>rks.
NEIGHBOR GATEWAY REACHABLE NETWORKS - One instance of this screen will be
configured for each gateway entered in the previous screen. This screen provides data

10-1

Router Network Interface Configuration

about the networks that can be reached from the gateway, and the gateway's IP
addres.c;
ROUTER HAPPING CONrIGURATION - This screen, which you will reach by pressing
.To. MAPP.ING, begins the NMMGR branch that allows you to specify information about
routes between the node you are configuring and other nodes on the same router network. This
screen in particular allows you to specify a name that Identifies each route.
~

ROUTER REACHABLE NODES - This screen, which is revisited for each route specified
in the previous screen, allows you to enter data about each route.

NOTE
Configurable fields described in this manual are required unless otherwise
stated.
Fields described as "HP modifiable" should be changed only upon the
recommendation of your HP representative.
On the screens shown in t.hls section, fields that must be configured when
performing guided configuration are underlined.

10-2

Router Network Interface Configuration

ROUTER NETWORK INTERFACE CONFIGURATION
The router network interface (NO serves to interface the upper layen of the transport protocol to the data
link layer. The router NI screen (shown below) supplies the information required for that interface. The
screen is displayed when you select an NI name and the NI type ROUTER at the Network Interface
Configuration Screen (Figure 8-9) and press ~~~ or ~.'~j. It is also displayed when you type the path
name:

@NETXPORT.NI.niName
in the command window of any screen and press (ENTER I, where the niName is the configured router NI
name.
You must press g;jlI~.!']~J.. to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record hu been created by checking that the 11111
flag is set to ~.
From this screen you proceed to the screens used to configure the router network interface.

Path:
-

NETXPORT.NI.niName
Number Of Inbound Buffers
Number Of Outbound Buffers
Number Of Routing Table Entries

11~11~1I

Network Hop Count
Idle Device Timeout Value (Minutes)
o = Timer Disabled For All Devices

File: filename.NET.SYS

Figure 10-1. Router Network Interface Configuration Screen

Choose the item you wish to configure and press the corresponding function key.

10-3

R.outer Network Interface Configuration

Fields
NUllber of
InbOund BUffers

This field specifie~ the number of buffers to be allocated for inbound data.
Buffer configuration is based on the number of TCP connections that will
use a given network interface. An allocation of two buffers per connection
will suffice for typical usage.
The default value is based on the assumption that the Network Manager
desires to allow no more than the default number of TCP connections (128)
to use the router NI (see related screens, below). Hence the default is 128 *
2 r:a 256 inbound buffers. When there is more than one NI, this value
should probably be adjusted downward, since the connections might
reasonably be expected to be spread over all the Nls rather than be
concentrated over only one NI. If the number of TCP connections is
changed from the default value, the number of inbound buffers for an NI's
should be reconsidered.
Whenever there are not enough buffers to support inbound traffic, an IP
log message will Indicate that the node is congested and the packet had to
be discarded. (See the NS3000/V Error Message and Recovery Manual for
the exact IP log location and message.) Repeated occurrence of this log
message indicates that more inbound buffers should be configured.
Related Screens:
- NETXPORT. GPROT •TCP

The maximum number of TCP Connections is configured here. The
default value is 128.
Default Value: 256
Range: 32-2048

NUlDber of
Outbound BUffers

This field specifies the number of buffers to be allocated for outbound
data. Outbound buffers are used for outbound data packets and are held
by the transport until acknowledged by the destination. Not allocating
enough outbound buffers may adversely affect TCP throughput.
Calculation of the default value is the same as described above for inbound
buffers.
Related Screens:
- NETXPORT •GPROT •TCP

The default value for maximum TCP connections is configured here.
If it is increased, the number of outbound buffers must also be
increased.
Default: 256
Range: 32-2048

10-4

Router Network Interface Configuration

Nu.ber of Routing

Table Ent.rlea

This is the number of routing table entries necessary to support the router
network eonfiguration. The router NI uses this value to allocate memory
for the routin. table.
This ~alue should be at least as large as the total number of router
reachable nodes that are eonfigured. In addition, future growth should be
anticipated. If insufficient space is allocated. the router Nllop a meaage
indicating this. (See the NS3000!V Error Message and Recover, MtJIIlUII
for the specific Nllog message details.)
Related Screens:
- NETXPORT •NI. NiName. MAPPING.m:rpentry
Reachable nodes are configured here.
- NETXPORT •GLOBAL
The number of path descripton configured in this screen is related to
the maximum number of nodes in the network.

Default Value: 100
Range: 1-1024

Network Hop Count

This is the maximum number of hops that a packet entering the network
can make. It is the distance between the two most remotely separated
nodes on the network. Distance is measured in terms of "hops," where each
intermediate node between two end nodes is counted as a "hop. It
The network hop count determines a packet's time to live, that is, the time
(in numbers of hops) that a packet is allowed to remain in the network. A
packet whose time to live has expired can be assumed to be undeliverable
because of some undetected routing anomaly, and will be discarded.
If this value is set too low, the danger exists that packets will be discarded
prematurely (that is, before they reach their destination). If the value is set
too high, an undeliverable packet may remain in the network too long, and
possibly contribute to network congestion.
Default Value: None
Range: 1-1024

10-5

R.outer Network Interface Configuration

Idle Device
Tl.eout Value ("ins)

This field is relevant only if the link is a dial link. For those devices that
have the Idle Device Timer enabled, if there is no activity during this time
interval, the device is considered to be inactive and will be shut down. A
timeout value of zero disables the Idle Device Timer for the link on this
network interface, thus overriding any enabled device timer (see R.elated
Screens, below). The purpose of the Idle Device Timer is to shut down dial
links that have become idle.
Related Screens:
- NETXPORT .NI.niName. LINK.nilink

An entry in this screen enables/disables Idle Device Timer for the
device.
- NETXPORT •GPROT •Tep

The Connection Assurance Interval set in this screen must be less than
the Idle Device Timeout value configured in the current screen. Note
that one value (Connection Assurance) is configured in seconds, the
other (Idle Device Timeout) is configured in minutes. You must
convert to the same units to compare the values.
Default Value: None
Range: 0-720

10-6

Router Network Interface Configuration

ROUTER NETWORK INTERFACE PROTOCOL CONFIGURATION
The menu screen in Figure 10-2 is displayed when you press the function key for i~";'"
I.Q;~ at
the Router Network Interface Configuration screen (Figure 10-1). It is also displayed when you type the
path name:
'),:,

@NETXPORT.NI.niName.PROTOCOL
in the command window of any screen and press (ENTER I, where niName is the configured router NI
name.
For the router NI, you must configure the IP protocol. The Dial protocol must be configured only if you
have any switched lines. The :::::::~i!
~~I~ and ';,:::, :i:~~:, .::.:;: function key labels are displayed.

!!!hl NETXPORT.NI.niName.PROTOCOL
IP

Configure Internet Protocol

PROBE

Configure PROBE Protocol (LAN Only)

DIAL

Configure DIAL Protocol (Router/Gateway Half Only)
Necessary Only If There Are Any Switched Links

File:

filename.NET.SYS

Figure 10-2. Protocol Configuration Screen
Choose the protocol to configure and press the corresponding function key.

10-7

Router Network Interface Configuration

INTERNET PROTOCOL CONFIGURATION
Internet Protocol information must be supplied for each configured NI. The key field in the screen shown
below is the IP Internet Addresst which is used in IP routing and datagram delivery algorithms. Data in
the other fields are used for internal resource allocation and performance tuning.
The IP Protocol screen is displayed when you press the function key for ~!limt~:::!~l:P at the Protocol
Configuration Screen (Figure 10-2), It is also displayed when you type the path' name:""'' '

@NETXPORT.NI.niName.PROTOCOL.IP
in the command window of any screen and press [ENTER I, where niName is the configured router NI
name.
You must press ~M"llm~f~ to transfer the data displayed on the screen to the configuration file you
are creating or ,ij;(lating~" "'V'OU verify that the data record has been created by checking that the 11I~' :~
flag is set to II.

NETXPORT.NI.niName.PROTOCOL.IP
Store & forward Buffers
(Enter 0 To Disable Store & Forward)
LW~~~

IP Internet Address
Internal Message Queue Length
fragment Assembly Queue Elements

File:

fllename.NET.SYS

Figure 10-3. IP Protocol Configuratton SerNn

10-8

Router Network Interface Configuration

Fields
Store & Forward
BUffers

(HP modifiable.) This field allocates buffers to support store-and-forward
over the network interface being configured.
You must allocate store-and-forward buffers if (a) this is a node with two
or more router links or (b) the node being configured is an internet gateway
and packets from another network will be forwarded over this network
interface.
This number of store-and-forward buffers is configurable to allow
performance tuning for different network types.
However, UP
recommends that you use the default number of store-and-forward buffen
(20), and that you consult your UP representative before modifying this
value.
Default Value: 20

Range: 0-50

IP Internet Address

Enter the internet protocol UP) address for the network interface being
configured.
Addresses are made up of a network portion and a node portion. The
supported classes of network addresses have the following forms:

Class C
Class B
Class A

C~nnn.nnn.nnn4xxx
B~nnn.nnn4xxx.xxx

A~nnn4xxx.xxx.xxx

where ~ denotes a blank, and nnn is a value ranging from 0 to 255,
representing eight bits of the network portion of an address. The leftmost
group of nnn has the following ranges for each address class:

Class C:
Class B:
Class A:

192-223
128-191
0-127

where xxx is a value ranging from 0 to 255, representing the node portion
of the address.
Default Value: None

Internal Message
Queue Length

(HP modifiable.) This field puts a limit on the number of internal resources
that the IP protocol may hold while awaiting some other protocol module
action. It is a tuning parameter that should be modified only upon the
recommendation of your UP representative.
The default is set to handle most cases; if it is too low for your network,
packets will be discarded and you will receive a logging error message.

10-9

Router Network Interface Configuration
Consult the NS3000/V Error Message and Recovery Manual for the
specific log message.
Default value: 4
Range: 0-20

Fragment Assembly
Queue Elements

(HP modifiable.) This field specifies the maximum number of incomplete
message fragmentR that. this fP Instance may hold.
HP recommends that you use the default of 20 for this field. For purposes
of tuning your network's performance, and upon the recommendation of
your HP representative, you may wish to alter the number of Fragment
Assembly Queue Elements.
You may wish to configure a higher value if traffic conditions on your
network are less than optimal; e.g., if internet routes are heavily loaded and
intermediate nodes are congested. If conditions on your network are less
busy, you may wish to configure a lower value. Only configure 0 if no
fragmented messages will ever be receivP-d by the node you are configuring.
If message fragments are discarded, (indicating that the value configured in
this field is too low) a log message will be recorded. Refer to the
NS3000/V Error Message and Recovery Manual for a description of the

message you receive.
Default value: 20
Range: 0-100

10-10

Router Network Interface Configuration

DIAL 10 PROTOCOL CONFIGURATION
~

Along with other information, the Dial 10 Protocol Configuration screen provides a means of verifying
that the remote node is indeed the intended remote node and that both local and remote nodes have
proper security access. This screen, shown below, is displayed when you press the function key for
g~~,
·'M at the Protocol Configuration Screen (Figure 10-2). It is also displayed when you type the
path name:

@NETXPORT.NI.niName.PROTOCOL.DIAL
in the command window of any screen and press (ENTER), where niName is the configured router NI
name.
You must press gp~:h~I~;ml~l, to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the ~~g
flag is set to I.
After the data has been updated, press Go.:·:·t!o;;:$~~Ya:~~ to proceed to the next screen.

~;':'. j~;~~I'i1~~~~~~~!'~i~~~~i~~~~::~!lr~!i'
Path: NETXPORT.NI.niName.PROTOCOL.DIAL
Maximum Retransmissions Per Packet
ll~m!~j

Retransmission Timeout (Sees)

~~~I.

Security On (V/N)

File:

filename.NET.SYS

Figure 10-4. DiaiiD Protocol Configuration Screen

10-11

Router Network Interface Configuration

Fields
Maximum
Retransmissions
Per Packet

(UP modifiable. J This is the maximum number of times that a Dial ID
Protocol packet will be retransmitted. If the expected response to a packet
is not received after this number of retnnsmissions, the link device it is
using is closed. This value is related to the Retransmission Timeout value
discussed below. Multiplying these values results in the total time that
passes before a failure is reported (an error message will be recorded).
UP recommends that you alter this value only upon the recommendation of
your HP representative. However, nob: that if the value is set too low, dial
connections may fail unnecessarily when response times are temporarily
slowed by transient conditions such as an abnormally high volume of
traffic. The higher the value, the longer it will take to be notified of a link
failure if one occurs.
Default Value: 2
Range: 1-10

Retransmission
Timeout (sees)

(HP modifiable.) The Retransmission Timeout is the time interval that
passes between retransmissions of a Dial ID protocol packet.
Mulhplying t.he values configured for Maximum Number of
Retransmissions Per Packet (described above) and Retransmission Timeout
results in the total time that passes before a failure is reported (an error
message will be recorded).

HP recommends that you alter this value only upon the recommendation of
your HP representative. However, note that if the value is set too low, dial
connections may fail unnecessarily when response times are temporarily
slowed by transient conditions such as an abnormally high volume of
traffic. The higher the value. the longer it will take to be notified of a link
failure if one occurs.
Default Value: S
Range: 1- 10

Security On (YIN)

A Y (Yes) value in this field indicates that security strings are to be
exchanged and validated between the node being configured and a remote
node.
When a dial connection is initiated by a remote node, the security string
sent by the remote node is checked against the list of valid security strings
configured for the Dial ID Protocol for this network interface. (See
Related Screens, below).
When a dial connection is initiated by this node, the local DiaiiD protocol
sends the destination's security string (as configured on this node) to that
node. (Related Screens, below, indicates the pathname of the screen in

10-12

Router Network Interface Configuration

which you can configure security strings.)
If security validation fails, an error message is logged. where PARM indicates
whether the failure was local or remote. (See the NS3000/V Error
Message and Recovery Manual for a description of any error message
received.
Related Screens:
- NETXPORT .NI.niName. PROTOCOL. DIAL.SECURITY
Security Strings valid for this network are configured in this screen.
- NETXPORT .NI.niName.MAPPING.mpentry
The remote node·s security string is configured in this screen.

Default Value: Y
Range: Yor N

10-13

Router Network Interface Configuration

SECURITY STRING(S) CONFIGURATION
The Security String(s) Configuration screen supplies the security string required by the Dial 10 protocol
for the node you are configuring. (Note that the security string is not required if OiaiiD protocol is not
enabled.) This screen) shown below) is displayed if you pressed ~:lj\l!; ::;:i~i;~~1.1 in the preceding Dial ID
Protocol Configuration Screen (Figure 10-4). It is also displayed when you type

@NETXPORT.NI.niName.PROTOCOL.DIAL.SECURITY
in the command window of any screen and press (ENTER ., where niName is the configured router NI
name.

..:~~:Mll to transfer the data displayed on the screen to the configuration file you
You must press P·"!~~··.
are creating or u·Pdating. ·····You verify that the data record has been created by checking that the ~~i*l
flag is set to ~.

Path: NETXPORT.NI.niName.PROTOCOL.DIAL.SECURITV
Configured Security Strings
lIfl:F{)i;i[:i':::::mmmJ

;I:ml:\mmmm:i'

i[i:jlL::liHi:i!:;;::;;:Ul~kl

-t:~._. :::';::;i:::i:;;1;!::~l~;1m[!:l

Ill;:i1.n:~lm~m::::;i·::mm~ll:
!f.Jt;j;);mli:-;;~:(' .m:1:il

File: filename.NET.SYS

Figure 10-5. Security String(s) Configuration Screen

10-14

Router Network Interface Configuration

Fields
Configured Security
Strings

Enter the security string that remote nodes must use to sain dial link access
to the node you are configuring. The string can contain up to eight
alphanumeric characters-left justified, with no embedded blanks.
Default Value: HP
Related Screen:
- NETXPORT. Nt. niName. LI NK niL ink

The DiallD protocol is enabled/disabled on this screen.

NOTE

To delete a security string, blank out the field that contains the string you
want deleted, and press ( f 6 I ~~~~! :::.:.:."'..:

10-IS

Router Network Interface Configuration

ROUTER NETWORK INTERFACE LINKS
The select screen in Figure 10-6 is dl~pldled when you pre~ the funeuoll key for ~;::::];9,:~;jl~;J.H~ at the
Router Network Interface ConflguratioCl Screen (Figure 10-1) It is also displayed when you type the
path name:
@NETXPOR~

HI niName.LINK

in the command window of an) screfn clnd press
name.

CEN"fEiD,

where niName

the configured router NI

Use the fields of this select screen in combination with the futlcrion keys to perform the desired action.
• To define a new link configuration, specify the Hnle name; then press U~. The path for the
selected link name is added to the configuration fde, and the data screen on"ihe path is displayed.
• To modify an existing link configuration, specify the link name; then press Y;~~~i. The data
screen on the path for the specifIed link is displayed.
• To change the hnk name of an existing link configuratiol1, specify the link name and a new name;
~~. The previously configured name is replaced, and the screen displays the new
then press
name in a display 'field under the label Configured Network Links.

6.en..

• To delete an existing link configuration, specify the link name; then press ~:~~I~. The
previously configured name is deleted and is no longer displayed in a display field under the label
~a~:f:f~~;td Network Links. Press !)!l;~litt~ again to confirm; otherwise, the deletion will not

10-16

Router Network Interface Configuration

Path:
-

NETXPORT.NI.niName.LINK
J:!f:;~::m~!lY!::':::':i:U!:i;~;:mll

Link Name
New Name

DO
Types: DC
SO

- Direct Dial
Di rect Connect
- Shared Dial
(if new)

Configured Network Links
Name

Type

Name

Type

Name

Type

Figure 10-6. Router Network Interface Links Screen

Fields
Link Name

Enter the link name that pertains to this NI as specified in the link
configuration screen. This enables the Network Transport to associate the
correct link with this router NI. The name can contain as many as eight
alphanumeric characters) and the first character must be alphabetic.
The link name is used by the Network Transport when establishing
connections and must match the link name configured for the router link
configuration.
Related Screens:

- LINKCONf
A link name specified in this screen (and specified as a
ATP/ ASNP type) must match the link name here.

LAP-B) or

- NETXPORT. NI • niName. MAPPING.napentry

This screen specifies which link to use to reach a specific node on the
router network. The link specified must be one entered on the current
screen.
Types

Enter DO if only one remote node can be reached over a dial link.

10-17

Router Network Interface Configuration

Enter SO if more than llne remote node can be reached over a dial link.
Enter DC if the lank. is direct-connect (hardwired) or a leased line.
Related Sc:reens:

- NETXPORT. NI .ntName.MAPPING.nrzpentry
This screen maps router links to destination nodes. If multiple
destlnalions are mapped to a single bnk., the link must be configured as
a shared dial (SO) link in the current screen.
New Naae

10-18

(Requiretl only when renaming.) Enter a link name. This new link name is
used in place of the current link name for an existing link configuration.
The name can contain as many as eight alphanumeric characters, and the
first character must be alphabetic.

Router Network Interface Configuration

DIRECT CONNECT LINK CONFIGURATION
The DIrect Connect Link Configuration Screen supplies the information required to interface a router NI
to a non-dial link (that is, a leased line or a hardwired connection). This screen, shown below, is displayed
when you select an NI link name and the link type DC at the Network Interface Links Screen (Figure
10-6) and press M~ or .!~~. It is also displayed when you type the path name:

@NETXPORT.NI.niName.LINK.nilink
in the command window of any screen and press [ENTER I, where niName is the configured router Nt
name, and nilink is the configured router Nllink name.
You must press ",.~,~~/~~, to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the IiJI.II!~
flag is set to 1=.

Path:

!ll!
!![N;]:

rile:

NETXPORT.NI.niName.LINK.nilink
Start Device On Network Initialization (yIN)
Enable Idle Device Timer

filename.NET.SYS

Figure 10-7. Direct Connect Link Configuration Screen

10-19

Router Network Interface Configuration

Fields
Start Device
On Network
Initialization (YIN)

A V (Yes) value means that the device IS to be started when a NETCONTROL
START command is issued for th~ network interface being configured. An
N (No) means that a NfTCONTROL ADDLINK command must be used to start
the device.
Default Value" Y
Range: Yor N

Enable Idle
Device Timer

This field specifit;:a whether thp dev~ 'C is to be disconnected automatically if
no packets have been received or transmitted over the hnk during a
specified time period. This field is relevant only if a timeout value has
been entered in the network interface screen listed below.
Related

screen~'

- NETXPORT. NI. niNatne
The Idle Device Timeout value is configured on this screen.

Default Va lue; N
Range: Y or N

10-20

Router Network Interface Configuration

ROUTER DIAL LINK CONFIGURATION
Dial Link Configuration provides the information necessary to interface the router NI to a dial link. This
screen. shown below, is displayed when you select an Nllink name and link type DO or link type SO at the
Network Interface Links Screen (Figure 10-6) and press ~~~ or g;~I~~. It is also displayed when you
type the path name:

@NETXPORT.NI.niName.LINK.nilink
in the command window of any screen and press l ENTER ), where niName is the configured router NI
name, and nil ink is the configured router Nllink name.
You must press ~'Pda t~::.~t .. to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the Ii~i~~
flag is set to ~.
. _.._ -

Path:

NETXPORT.NI.niName.LINK.nilink

llm~I~!

Enable DIAL 10 Protocol (yIN)

11f.~iil

Start Device On Network Initialization (YIN)

1!f.~IJ;

Enable Idle Device Timer

File:

filename.NET.SYS

Figure 10-8. Router Dial Link Configuration Screen

Fields
Enable Dial ID
Protocol

(HP modifiable.) A Y (Yes) value activates the Dial ID Protocol for a dial
link. The Dial ID protocol verifies the identity of a remote node and
ensures that both local and remote nodes have the required security access.
The Dial ID Protocol should be disabled (by entering a NO value) only to

10-21

R.outer Network Interface Configuration

connect a dial link to a remote node that does not support the Dial ID
Protocol (that is, a non-UP node).
Related Screens:
- NETXPORT .NI.niName LINK

Configures a link name and link type. The link name specified leads
to this screen.
- NETXPORT. NI. niName. PROTOCOL. DIAL. SECURITY
Configures security striC\gs for this node.
- NETXPORT. NI.niName.MAPPING
Configures infermation about reachable router nodes. Remote nodes'
secullt.y stnngs are configured on thIS screen.
Default Value: Y
Range: Yor N

Start Device
On Network
Initialization
(YIN)

A Y (Yes) value m~ans that the device is to be started when a NETCONTROL
STAHT command is issued for this network interface. An N (No) means that
a NETCONTROL ADDLINK command must be used to start the device.

Default Value: Y
Range: Yor N

Enable Idle
Device Timer

This field specifies whether the device is to be disconnected automatically if
no packets have been received or transmitted over the link during a
specified time period. It is relevant only if a timeout value has been
entered an the router NI screen (see Related Screens below).
Related Screens:
- NETXPORT. NI. niName

Configures router network interface information.
The value
configured for Idle Device Timeout is configured on this screen.
Default Value: Y
Range: Yor N

10-22

Router Network Interface Configuration

NEIGHBOR GA TEW A YS
The select screen in Figure 10-9 is displayed when you press the function key for ~'~nt9.mm~m8H~T at
the Router Network Interface Configuration screen (Figure 10-1). It is also displayed when you type the
path name:

@NETXPORT.NI.niName.INTERNET
in the command window of any screen and press
name.

(ENTER I,

where the niName is the configured router NI

Use the fields and the function keys of this select screen to perform the desired action.
• To define a new gateway configuration, specify the gateway name; then press ld~. The path for
the selected gateway name is added to the configuration file, and the data
on the path is
displayed.

screen

• To modify an existing gateway configuration, specify the gateway name; then press Y:~~~I. The
data screen on the path for the specified gateway is displayed.
• To change the gateway name of an existing gateway configuration, specify the gateway name and
a new name; then press B.i"~m~. The previously configured name is replaced, and the screen
displays the new name in a'dlsplay field under the label Configured Gateways.
• To delete an existing gateway configuration, specify the gateway name; then press ~;~I.~". The
previously configured name is deleted and is no longer displayed in a display field under the label
Configured Gateways. Press pe,~,t;e again to confirm; otherwise, the deletion will not take
effect.

10-23

R.outer Network Interface Configuration

1,-~::~~~O~~~~~l~i~~~1~:!Ni~·:;;V~:;;:i~ .;~";~~;i.~,it~=~"~~:-,~;~j!i;~'" '- ',;,","-'
Path:

NETXPORT.NI.niName.INTERNET
Gateway Name
New Name
Configured Gateways

File:
-

filename.NET.SYS

Figure 10-9. Neighbor Gateways Screen

Fields
Gateway Name

Enter a name to represent a gateway node on this router network. through
which one or more remote networks can be reached. A gateway name can
contain as many as eight alphanumeric characters; the first character must
be alphabetic.

New Hue

(Required only when renaming.) Enter a name to represent a gateway node
on this router network. This new gateway name is used in place of the
current gateway name for an existing gateway configuration. The name
can contain as many as eight alphanumeric characters; the first character
must be alphabetic.

10-24

Router Network Interface Configuration

NEIGHBOR GATEWA Y REACHABLE NETWORKS
The Neighbor Gateway Reachable Networks screen is used to enter internet routing information. It
supplies the internet address of a neighbor internet gateway, remote networks which are reachable
through that gateway, and the distances to those remote networks. A neighbor gateway is a gateway node
belonging to the same network as the node you are configuring. This means that the network portion of
the gateway's internet address is the same as the network portion of the address you entered for the
network interface now being configured.
The screen in Figure 10-10 is displayed when you select a gateway name at the Neighbor Gateways
Screen (Figure 10-9) and press ~~~ or Q~~~~. It is also dIsplayed when you type the path name:

@NETXPORT.NI.niName.INTERNET.gatewayn
in the command window of any screen and press (ENTER I, where niName is the configured router NI
name, and gatetrJayn is the configured router NI gateway name.
You must press UPdate;::'Oa't~ to transfer the data displayed on the screen to the configuration file you
are creating .or updating. You verify that the data record has been created by checking that the ~~"l
flag is set to y..

;ai~~~:~;~~~~~~~~:·;!~:~;~~~t;~~~~!~~~~~~~~i~~~~~~~~i:I~~~~~jilli~i"'"
~

Path:

NETXPORT.NI.niName.INTERNET.gatewayn

I;:~:11;:;:~:.!:;::;<:·:i~;'~,,!ii;<·:<:;;::·T::!!:1!::::1::::,:::::::]

Ne i gh bo r Gat eway I PIn terne t Add res s
Configured Reachable Networks

IP Network Address

file:

Hops

PAGE

IP Network Address

Hops

filename.NET.SYS

Figure 10-10. Neighbor Gateway Reachable Networks Screen

10-25

Router Network Interface Configuration

NOTE

The information configured in this screen can extend to more than one
page, if necessary, to allow configuration of more than 10 reachable
networks. Press Nex~ .:::Page to proceed to a new page. Press ·Pre~.::~·f,*9~ to
display a prior page. Use r·~r~~::;:-~~ge to display the first page (for
example, if you are viewing the third page, pressing fil~~!r~:t.;:~9~ will
immediately display the first page). Press ~ii~;!;;~~9~ to display the last
page of reachable networks that has been configured. To consolidate
reachable networks entries (from several pages, for example) press
~qp.~~"i~:~;·]~~a~·

Fields
Neighbor Gateway
IP Internet Address

Class C
Class B
Class A

C4nnn.nnn.nnn4xxx
B4nnn.nnn4xxx.xxx
A4nnn4xxx.xxx.xxx

Class C:
Class B:
Class A:

192-223
128-191
0- 127

10-26

Router Network Interface Configuration

Configured Reachable
Networks IP Network
Address

Enter the internet addresses of the remote network.s that can be reached
through the gateway whose network address is configured in the previous
field. Only the internet portion of the network address is significant for
this field (see above for valid formats of internet addresses). The node
portion must be entered; however, it may be set to all zeros.
Related Screens:
- NETXPORT. NI .niName. INTERNET

This pathname corresponds to the Neighbor Gateways screen. A Neighbor
Gateway Reachable Networks screen must be configured for each gateway
configured in the Neighbor Gateways screen.

Configured Reachable
Networks Hops

NOTE

To delete a reachable network entry, fill the field to be deleted with blanks
and press ~.~~!~ •.:~t~.

10-27

Router Network Interface Configuration

ROUTER MAPPING CONFIGURATION
The screen in Figure 10-12 is displayed when you press the function ke) t·or (lQfJi:itQ:~::MA~1.H(; at the
Router Network Interface Configuration Screen (Figure 10-1). It is also displayedoo"wheo"you' type the
path name:

@NETXPORT.NI.niName.MAPPING
in the command window of any screen and press . ENteR), where the niName is the configured router NI
name. The screen following this one allows you to configure a set of characteristics for a route from the
local node to a remote node. Each set of route characteristics is referred to as a "mapping. II The router
node name entered on this screen is used to identify a mapping that is configured in the next screen. You
must configure one mapping for each non -adjacent node that you want to reach through a link to a given
adjacent node. as well as mappings for each adjacent node. There may be multiple routes to a destination
node; if the routes are through different adjacent nodes, a mapping must be configured for each of them.
For example, Figure 10-11 shows a router network that could have eight mappings configured at node A.

Figure 10-11. Configuring Mapping
If node A is the node being configured, mappings are needed for routes to both node B and node C, and for
routes through nodes Band C to any other node. A mapping could be configured for each of the
following routes (the rightmost node in these sets is the destination node):

Routes to adjacent nodes:
A-B
A-C

(uses Link 1)
(uses Link 3)

Routes to non-adjacent nodes through B:
A-B-D
A-B-D-E

(uses Link 1)
(uses Link 1)

Routes to non-adjacent nodes through C:
A-C-D
A-C-E

(uses Link 3)
(uses Link 3)

Alternate routes to adjacent nodes.
A-C-D-B
A-B-D-C

10-28

(uses Link 3)
(uses Link 1)

Router Network Interface Configuration
Note that it is not necessary to configure alternate routes to nodes Band C; however, you can configure
the routes listed above (A-C-O-B and A-B-D-C) to allow for the possibility that the link used for the
primary route becomes non-operational. Refer to the section ClNon-Operational Linklf' in Section 3 of
this manual for more information about alternate routes.

10-29

Router Network Interface Configuration

Use the fields and the function keys of this select screen to perform the desired action, as follows:

• To define a new mapping configuration, specify a name for the route (called a router node name
on the screen); then press ~dd. The path for the selected route is added to the configuration file,
and NMMGR displays a mapping data screen (called the Router Reachable Nodes screen). This
screen must be configured to define the specified route.
• To modify an existing mapping configuration, specify the name of the route {router node
then press ~:~~~~. NMMGR displays the data screen corresponding to the specified name.

name~

• To change the name of an existing mapping configuration, specify the existing router node name
and a new name; then press ~~n.~~~. The previously configured name is replaced, and the screen
displays the new name in a ciisplay""field under the label Configured Mappings.
• To delete an existing mapping configuration, specify the existing router node name name; then
press I)i:~~~~. Press ~:l"\~ again to confirm; otherwise, the deletion will not take effect. The
previoli"sly·configured·oname °is deleted and is no longer displayed in a display field under the label
Conf igu red Mappings.

'~~;·;':~~~~l~!~:~~!~'~~i~;!.I!i~~~~~~~~.~.i~ltf~,~ili~~;;:i:m:i~~i~ii!!i!'!!ii!ii:~~~,~l~ii~·w,
Path:

NETXPORT.NI.niName.MAPPING
Name

Configured Mappings

I!;;:r~~.~:~~i~~!

~~~1~1,

Figure 10-12. Router Mapping Configuration Screen

10-30

Router Network Interface Configuration

Fields
Router Node Nue

Enter a name to represent a route between the node you are configuring
and another node on the router network. This name can contain as many
as eight alphanumeric characters; the first character must be alphabetic.

New Name

(Required only when renaming.) Enter a new router node name. This new
name is used in place of the current name for an existing route. The name
can contain as many as eight alphanumeric characters. and the first
character must be alphabetic.

"
\<

10-31

Router Network Interface Configuration

ROUTER REACHABLE NODES
The screen shown in Figure 10-1 3 is used to
the router network. You must configure one
you want to reach through a link to a given
The name of the link connecting this node to
of this screen.

configure the route characteristics to a destination node on
mapping (i.e. one instance of this screen) for each node that
adjacent node, as well as mappings for each adjacent node.
the adjacent node is what you enter in the Link Name field

Because at least one route should be defined to every other node on the network, this screen will be visited
at least as many times as there are other nodes in the router network. There may be multiple routes to a
non-adjacent destination node; if the routes are through different adjacent nodes, a mapping must be
configured for each of them. The screen shown below is displayed when you select a router node name at
the Router Mapping Configuration screen (Figure 10-1 2) and press ~~ or ~;pc;I~~~. It is also displayed
when you type the path name:

@NETXPORT.NI.niName.MAPPING.mapentry
in the command window of any screen and press [ENTER I, where niName is the configured router NI
name, and napentry is the router node name configured in the Router Mapping Configuration screen
(Figure 10-12). You must press ~;U?~~,,':m~~~ to transfer the data displayed on the screen to the
configuration file you are creating or updating. You verify that the data record has been created by
checking that the ~~.J flag is set to y.

Path: NETXPORT.NI.niName.MAPPING.mapentry
IP Internet Address
Link Name
Adjacent (0)/ Non-adjacent (1)
Entry Priority
Phone Numbe r
Security String
Route Disabled

(V for VeSt N for No)

file: filename.NET.SYS

Figure 10-13. Router Reachable Nodes Screen

10-32

Router Network Interface Configuration

Fields
IP Internet Address

This is the internet address of the destination node to which a route is being
defined.
Addresses are made up of a network portion and a node portion. The
supported classes of network addresses have the following forms (Note: /1. a
space):

Class C
Class B
Class A

Cll nnn. nnn •nnntu(xx
Bll nnn. nnnf1xxx. xxx
Ad

nnnAxxx. xxx. xxx

Class C:
Class B:
Class A:

192-223
128-191
0-127

If the link specified in the Link Name field is the only link configured for
this network interface, you can enter a "wildcard" symbol by specifying an
"at sign" (@) in place of the IP address. The @ in this field indicates that
multiple non -adjacent router nodes on this network can be reached via this
link (specified in the Link Name field). Using the @ wildcard enables you
to configure this screen only once for all non-adjacent nodes reachable by
the specified link. Use the @ only if the link specified is the only link for
this network interface. The @ must be left-justified in the IP Internet
Address field. Make sure you separately configure the mapping to the
adjacent node from which the non-adjacent nodes can be reached.

For example, Figure 10-14 shows a router network. From node A, all other
nodes on the network must be reached through node B.
During
configuration of node A, the @ could be entered to indicate that all
communication to non-adjacent nodes originating from A must be routed
through node B (over Link 1). In addition to this mapping, only one
additional mapping would have to be configured at node A--the mapping
from node A to the adjacent node B.

Figure 10-14. Using an @ for Mapping Configuration
Default Value: None

10-33

Router Network Interface Configuration
Link Name

The name of the link on this node over which packets to the destination
node must be sent. The name of the link IS configured separately (see
related screens below).
Related Screens
- NETXPORT. NI. niName. LINK
This screen configures the link name.
- LINKCONF.nilink
ThIs screen configures link attributes

Default Value: None
AdJacent/Non-adJacent

This field indicates whether the destination is an adjacent node to the node
being configured (0) or if it is non -adjacent, i. e., the destination must be
accessed through intermediate nodes (1).
Default Value: None
Range: 0 or 1

Entry Priority

This field IS useful when alternate routes are configured to a destination
node. It is the primary means of influencing the choice of route over the
router network. Priority is considered before any other route characteristic
(direct connect link, dial connection, number of hops, etc.) in choosing a
route. Links having higher priority values are chosen over lower priority
links.
A default value of 50 allows for the addition of either lower or higher
priority nodes or routes.
Default Value: 50
Range: 1-99

Phone Number

This is the telephone number of the destination node. It is required if the
destination is local and the link is a dial link. Enter the telephone number
as a combination of decimal numbers (0 through 9), dashes, and the
following special characters:
/ Separator used for automatic call units that
have second dial-tone detect.
E Optional end-of-number Indicator.

o One second delay (used for European modems
and automatic call units that require built -in
delays).
, Defined by local phone system.
• Defined by local phone system.

10-34

Router Network Interface Configuration

Enter! to disable outbound dialing. A! is required if the destination node
is a personal computer.
Default Value: None

Security String

This is the security string of the destination node. It is relevant only if all
of the following are true: the destination is local, the link is a dial link,
DIAL ID protocol is enabled, and security is enabled. It is ignored when
security IS not enabled at the local node.
The security string can contain as many as eight alphanumeric characters.
It must be left justified and contain no embedded blanks.
Related Screens:

- NETXPORT .NI.niName. LINK. nilink
DiallD protocol is enabled/disabled on this screen.
- NETXPORT. NI. niName. PROTOCOL. DIAL
Security validation is enabled/disabled on this screen.
Default Value: HP

Route Disabled

This field may be used to disable routing to the remote node. This might be
useful if you are testing another link» and want to temporarily disable this
one.
Default Value: N
Range: Yor N

10-35

.~
"".

GATEWAV HALF NETWORK
L---IN_T_ER_F_A_C_E_C_O_N_F_IG_U_R_A_T_IO_N

-----IOD

The screens described in this section are used for configuring a node with a gateway half network
interface.
There are three main branches of gateway half network interface configuration. These are reached by
choosing different function keys displayed on the first screen, called the GATEWAY HALF' NETWORK
INTERfACE CONfIGURATION screen. All of the gateway half network interface configuration screens
are listed below, with their places in the configuration tree indicated by indentation.

GATENAY HALF NETWORK INTERFACE CONFIGURATION - This screen enables you to configure
information about a gateway half network interface, such as the number of inbound and outbound
buffers. From this screen, you can proceed to one of three branches of gateway half NI configuration:
protocol configuration, link configuration, and internet configuration.
PROTOCOL CONFIGURATION - You will reach this screen if you press ~~!!II!~II!!IIIl~1t~~1+ on the
GATEWAY HALF NETWORK INTERFACE CONFIGURATION screen. This screen allows you to
choose to proceed to either IP or DIAL protocol configuration.
IP

PROTOCOL CONFIGURATION - This screen, which you will reach by pressing
]~ on the previous screen, enables you to configure the number of store and
forward buffers for the network interface, the partner gateway half's IP address, and
tuning parameters for the IP protocol.

Ill!

DIAL 10 PROTOCOL CONFIGURATION - This screen enables you to configure
information about a dial link that is used by the Dial 10 protocol--retransmission
information, and whether security is in effect.
SECURITY STRING(S) CONFIGURATION - This screen allows you to specify
the security strings used by the DialiD protocol.
GATEMAV HALF NETWORK INTERFACE LINK - This screen, which you will reach by pressing
'i
on the GATEWAY HALF NETWORK INTERfACE CONFIGURATION screen, allows you
to specify ih~ name of the link (as previously configured in the LINK CONFIGURATION screen),
and whether the link is a direct dial link or a direct connect link.
DIRECT CONNECT LINK CONFIGURATION - This screen, which NMMGR displays
when you specify a direct connect link in the previous screen, allows you to enter
information pertaining to the direct connect link.
GATEHAY HALF DIAL LINK CONFIGURATION - This screen, which NMMGR displays
when you specify a direct dial link in the previous screen, allows you to enable or
disable the DiailD protocol.
NEIGHBOR CATENAYS - This screen, which you will reach by pressing ~mmr'~?'m~!I~~~~H on the
GATEWAY HALF NETWORK INTERFACE CONfIGURATION screen, permits you to specify a
gateway name to represent the node's partner gateway half.
NEICHBOR GATEWAY REACHABLE NETWORKS - This screen provides data about the
networks that can be reached through the partner gateway half specified on the
previous screen.

11-1

Gateway Half Network Interface Configuration
NOTE

Configurable fields described in this manual are required unless otherwise
stated.
Fields described as "UP modifiable" should be changed only upon the
recommendation of your UP representative.
On the screens shown in this section, fields that must be configured when
performing guided configuration are underlined.

11-1

Gateway Half Network Interface Configuration

GATEWAY HALF NETWORK INTERFACE CONFIGURATION
The gateway-half network interface (NI) interfaces the upper layers of the transport protocol to the data
link layer. The screen shown in Figure 11-1 supplies the information required for that interface. The
screen is displayed when you select an NI name and the NI type GATEHALF' at the Network Interface
Configuration screen (Figure 8-9) and press Irs I ~~~ or I r 8 I ~~i~". It is also displayed when
you type the path name:

@.NETXPORT.NI.niName
in the command window of any screen and press I ENTER I. where the niName is the configured
gateway-half NI name.
You must press ~:~a~lIP.;!;:~~' to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the .'<:... ~I
flag is set to ~.
. . . -"
From this screen you proceed to the screens used to configure the gateway-half network interface.

I~fu~;~~~:'
.~i~ffi~m~~

Path:

I~;.;"
I~;::=::

NETXPORT.NI.niName

",:

Number Of Inbound Buffers
Number Of Outbound Buffers
Idle Device Timeout Value (Minutes)
o =Timer Disabled for All Devices

File:

filename.NET.SYS

Figure 11-1. Gateway-Half Network Interface Configuration Screen

11-3

Gateway Half Network Interface Configuration

Fields
Number of

Inbound Buffers

This field specifies the number of buffers to be allocated for inbound data.
Buffer configuration is based on the number of TCP connections that will
use a given network interface. An allocation of two buffers per connection
will suffice for typical usage.
The default value is based on the assumption that the Network Manager
desires to allow no more than the default nun!ber of TCP connections (128)
to use the gateway-half NI (see Related Screens, below). Hence the default
is 128" 2 256 inbound buffers. When there is more than one NI, this
value should probably be adjusted downward, since the connections might
reasonably be expected to be spread over all the Nis rather than be
concentrated over only one NI. If the number of TCP connections is
changed from the default value, the number of inbound buffers for all Nis
should be reconsidered.
D

Whenever there are not enough buffers to support inbound traffic, an IP
log message will indicate that the node is congested and the packet had to
be discarded. (See the NS3000/V Error Message and Recovery Manual for
the exact IP log location and message.) Repeated occurrence of this log
message indicates that more inbound buffers should be configured.
Related Screens:

- NETXPORT. GPROT . rep
The maximum number of TCP Connections is configured here. The
default value is 128.
Default Value:

256

Range: 32-2048

Number of

Outbound Buffers

-NETXPORT.GPROT.TCP
The default value for maximum TCP connections is configured here.
If it is increased, the number of outbound buffers must also be
increased.
Default:
Range:

11-4

256
32-2048

Gateway Half Network Interface Configuration

Idle Device
Tlaeout Value (Hlns)

If the Idle Device Timer has been enabled (see related screens below). and if
there is no activity during this time interval, the device is considered to be
inactive and will be shutdown. A timeout value of zero disables the Idle
Device Timer for the link on this network interface. The Idle Device timer
is useful for shutting down dial links that have become idle. This field is
relevant if the link is a dial link.
Related Screens:
- NETXPORT .NI .niname. LINK.linkname

Enables/disables Idle Device Timer for the device.
- NETXPORT. GPROT •TC P

The Connection Assurance Interval set in this screen must be less than
the Idle Device Timeout value configured in the current screen. Note
that one value (Connection Assurance) is configured in seconds. the
other (Idle Device Timeout) is configured in minutes. You must
convert to the same units to compare the values.
Default Value: None

Range: 0-720

11-5

Gateway Half Network Interface Configuration

PROTOCOL CONFIGURATION
The menu screen in Figure 11- 2 is displayed when you press the function key for ~~;:[Jt9.1':i;~~'t~~~ at
the gateway-half Network Interface Configuration screen (Figure II-I). It is also displayed when you
type the path name:

@NETXPORT.NI.niName.PROTOCOL
in the command window of any screen and press [ENTER I. where niName is the configured gateway-half
NI name.
For the gateway-half NI. you must configure the IP protocol. The Dial protocol must be configured only
if you have any switched lines. The ( t, I ~;:mit~!j~j~~ and ( r 2 I ~!ll!lt~:i:[i~_~ function key labels are
displayed.

Path:

NETXPORT.NI.niName.PROTOCOL

Configure Internet Protocol

PROBE

Configure PROBE Protocol (LAN Only)

DIAL

Configure DIAL Protocol (Router/Gateway Half Only)
Necessary Only If There Are Any Switched Links

File:

filename.NET.SYS

Figure 11-2. Protocol Configuratioll Screen
Choose the protocol to configure and press the corresponding function key.

11-6

Gateway Half Network Interface Configuration

INTERNET PROTOCOL CONFIGURATION
Internet Protocol information must be supplied for each configured NI. The key field in the screen in
Figure 11-3 is the IP Internet Address, which is used in IP routing and datagram delivery algorithms.
Data in the other fields are used for internal resource allocation and performance tuning.
The IP Protocol screen is displayed when you press the function key for ~;;;;r:r.~:r.~f at the Protocol
Configuration screen (Figure 11-2). It is also displayed when you type the path name:

@NETXPORT.NI.niName.PROTOCOL.IP
in the command window of any screen and press (ENTERl, where niName is the configured gateway-half
NI name.
You must press U.pd.te./.patj to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the ~~ir~
flag is set to ~.
.
..

Path:

NETXPORT.NI.niName.PROTOCOL.IP
Store & forward Buffers
(Enter 0 To Disable Store & forward)

lii::>::[;:j~T:llW;i1i~:~mii::;.)-:>:.. '>

,,J. I P Internet

Add ress

~I'f:::;~:lm~j

Internal Message Queue Length

1~~JWill:j~;

fragment Assembly

file:

Queue Elements

filename.NET.SYS

Figure 11-3. IP Protocol Configuration Screen

11-7

Gateway Half Network Interface Configuration

Fields
Store & Forward
BUffers

(UP modifiable.) This field allocates buffers to support store-and-forward
over the network interface being configured.
You must allocate store-and-forward buffers for all gateway half network
interfaces.
This number of store-and-forward buffers is configurable to allow
performance tuning for different network types.
However, UP
recommends that you use the default number of store-and-forward buffers
(20), and that you consult your UP representative before modifying this
value.
Default Value: 20
Range: 0-50

IP Internet Address

Enter the internet protocol (IP) address for the network interface being
configured.
Because you are configuring a gateway half NI, enter the IP address of this
gateway half's partner gateway half. This is the IP address of the network
for which the partner serves as a gateway half. In other words, the address
to enter is the network address of the partner's home network.
Addresses are made up of a network portion and a node portion. The
supported classes of network addresses have the following forms:

Class C
Class B
Class A

Cdnnn.nnn.nnn4xxx
Bdnnn.nnn4xxx.xxx
Adnnn4xxx.xxx.xxx

where 4 denotes a blank, and nnn is a value ranging from 0 to 255,
representing eight bits of the network portion of an address. The leftmost
group of nnn has the following ranges for each address class:

Class C:
Class B:
Class A:

192-223
128-191
0-127

Where xxx is a value ranging from 0 to 255, representing the node portion
of the address.

Default Value: None

11-8

Gateway Half Network Interface Configuration

Internal Hessage
Queue length

(HP modifiable.) This field puts a limit on the number of internal resources
that the IP protocol may hold while awaiting some other protocol module
action. It is a tuning parameter that should be modified only upon the
recommendation of your HP representative.
The default is set to handle most cases; if it is too low for your network,
packets will be discarded and you will receive a logging error message.
Consult the NS3000/V Error Message and Recovery Manual for the
specific log message.
Default value: 4
Range: 0-20

Fragment Assembly
Queue Eletlents

(HP modifiable.) This field specifies the maximum number of incomplete
message fragments that this IP protocol may hold.

HP recommends that you use the default of 20 for this field. For purposes
of tuning your network's performance. and upon the recommendation of
your HP representative. you may wish to alter the number of Fragment
Assembly Queue Elements.
You may wish to configure a higher value if traffic conditions on your
network are less than optimal; e. g.• if internet routes are heavily loaded and
intermediate nodes are congested. If conditions on your network are less
busy. you may wish to configure a lower value. Only configure 0 if no
fragmented messages will ever be received by the nocle you are configuring.
If message fragments are discarded, (indicating that the value configured in
this field is too low) a log message will be recorded. Refer to the
NS3000/V Error Message and Recovery Manual for a description of the
message you receive.

Default value: 20
Range: 0-100

r·
11-9

Gateway Half Network Interface Configuration

DIAL ID PROTOCOL CONFIGURATION
Along with other protocol information, the Dial ID Protocol Configuration screen provides a means of
verifying that the remote node is indeed the intended remote node and that both local and remote nodes
have proper security access. This screen, shown in Figure 11-4, is displayed when you press ( t 2 I for
q~:!~:1t~~[i!~~:~~ at the Protocol Configuration screen (Figure 11-2). It is also displayed when you type the
path name:

@NETXPORT.NI.niName.PROTOCOL.OIAL
in the command window of any screen and press (ENTER I, where niName is the configured gateway-half
NI name.
You must press ~:~"\Wt .:::::~~ to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the Ili~"~~!
flag is set to ~.

Path: NETXPORT.NI.niName.PROTOCOL.DIAL
IW~iil!!lli

Maximum Retransmissions Per Packet

11~:ii:!:JI

Retransmission Timeout (Sees)

IYl

Security On (YIN)

File:

filename.NET.SYS

Figure 11-4. Dial Protocol Configuration Screen

Fields
Maximum
Retransmissions
Per Packet

11-10

(HP modifiable.) This is the maximum number of times that a Dial ID
Protocol packet will be retransmitted. If the expected response to a packet
is not received after this number of retransmissions, the link device it is

Gateway Half Network Interface Configuration
using is closed. This value is related to the Retransmission Timeout value
discussed below. Multiplying these values results in the total time that
passes before a failure is reported (an error message will be recorded).
HP recommends that you alter this value only upon the recommendation of
your HP representative. However, note that if the value is set too low, dial
connections may fail unnecessarily when response times are temporarily
slowed by transient conditions such as an abnormally high volume of
traffic. The higher the value, the longer it will take to be notified of a link
failure if one occurs.
Default Value: 2
Range: 1-10

Retransmission
TilleOut (Sees)

(HP modifiable.) The Retransmission Timeout is the time interval that

passes between retransmissions of a DiaiiD protocol packet.
Multiplying the values configured for Maximum Number of
Retransmissions Per Packet (described above) and Retransmission Timeout
results in the total time that passes before a failure is reported (an error
message will be recorded).
HP recommends that you alter this value only upon the recommendation of
your UP representative. However, note that if the value is set too low, dial
connections may fail unnecessarily when response times are temporarily
slowed by transient conditions such as an abnormally high volume of
traffic. The higher the value, the longer it will take to be notified of a link
failure if one occurs.
Default Value: 5
Range: 1- 10

security On (YIN)

A Y (Yes) value in this field indicates that security strings are to be
exchanged and validated between the node being configured and a remote
node.

When a dial connection is initiated by a remote node, the security string
sent by the remote node is checked against the list of valid security strings
configured for the Dial ID Protocol for this network interface. (See
Related Screens, below).
When a dial connection is initiated by this node, the local DiallD protocol
sends the destination's security string (as configured on this node) to that
node. (Related Screens, below. indicates the pathname of the screen in
which you can configure security strings.)
If security validation fails, an error message is logged, where PARM indicates
whether the failure was local or remote. (See the NS3000/V E,ror
Message and Recover, Manual for a description of any error message

11-11

Gateway Half Network Interface Configuration
received.
Related Screens:
- NETXPORT .NI.niName. PROTOCOL.DIAL.SECURITY

Security Strings valid for this network are configured in this screen.
- NETXPORT .NI.niName.MAPPING.tmpentry

The remote node's security string is configured in this screen.
Default Value: Y
Range: Yor N

11-12

Gateway Half Network Interface Configuration

SECURITY STRING(S) CONFIGURATION
The Security String(s) Configuration screen supplies the security string required by the Dial ID protocol
for the node you are configuring. (Note that the security string is not required if DiallD protocol is not
enabled.) This screen, shown in Figure 11- 5, is displayed if you press ( t 1 I ~ffiht.i11mlS~c.~:I~ on the
preceding DiailD Protocol Configuration screen (Figure 11-4). It is also displayecfwh'en'you"type'-

@NETXPORT.NI.niName.PROTOCOL.DIAL.SECURITY.
in the command window of any screen and press
NI name.

(ENTER I,

where niName is the configured gateway-half

You must press ~1~~j,!;;!~i~~1 to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the .~,r.~
flag is set to lr~~1
_ .

Path: NETXPORT.NI.niName.PROTOCOL.DIAl.SECURITY
Configured Security Strings

]~l::mmm:!: · ....i;lm::l

!I' . ;:mmmmm~~ll~il.'
i[~"""';"'

. It:i!~·

File: filename.NET.SYS

Figure 11-5. Security String Configuration Screen

11-13

Gateway Half Network Interface Configuration

Fields
Configured Security
Strings

Enter the security stnng that remote nodes must use to gain dial link aecess
to the node you are configuring. The string can contain up to eight
alphanumeric characters, left justified, with no embedded blanks.
Default Value: HP

Related Screen:

- NETXPORT. NI. niName. LINK. niL ink.

The DiailD protocol is enabled/disabled on this screen.

NOTE

To delete a security string, blank out the field that contains the string you
want deleted,and
I ~~11~ili
.f~.
Press (
~ell'::""''''" ":lI"'''''"'

11-14

Gateway Half Network Intert'ace Configuration

GATEWAY HALF NETWORK INTERFACE LINK
The select screen in Figure 11-6 is displayed when you press ( t 2 I:
.1 at the Gateway Half
Network Interface Configuration screen (Figure 11-1). It is also displayed when you type the path name:
h

@NETXPORT.NI.niName.LINK

in the command window of any screen and press
link network interface name.

(ENTER I,

where niName is the configured gateway half

Use the fields of this select screen in combination with the function keys to perform the desired action.
• To define a new link configuration. specify the linle. name; then press ( t 5 1111. The path for
the selected link name is added to the configuration file. and the data screen on the path is
displayed.
• To modify an existing link configuration, specify the link name; then press
screen on the path for the specified link is displayed.

j!!!11

The data

• To change the link name of an existing link configuration. specify the link name and a new name;
then press liili!~i. The previously configured name is replaced, and the screen displays the new
name in a display field under the label Configured Network Links.
• To delete an existing link configuration, use the delete key. Specify the link name. then press
. , ~~I; when NMMGR prompts you for confirmation. press . . .
again. The previously
configured name is deleted and is no longer displayed in a display "field under the labeled
Configured Network Links.

11-15

Gateway Half Network Interface Configuration

~.!t~~it~~;~;ttit~rm~~~~f;'~~~~~1;~~;;f~~;:'.;:~~~I~e~t~~~~~:~~;j
Path:

NETXPORT.NI.niName.lINK
DO

~;::ji:;:::::m::mi:!:!:UiL,;,;;l

link Name
New Name

- Direct Dial
Types: DC - Di rect Connect
(if new)

Configured Network Links
Name

Type

Name

Type

Name

Type

Figure 11-6. Network Interface Links Screen

Fields
Link Name

Enter the link name from the link configuration of a gateway half; this
enables the Network Transport to associate the correct link with the
gateway half network interface. The name can contain as many as eight
alphanumeric characters, and the first character must be alphabetic.
The link name is used by the Network Transport when establishing
connections and must match the link name configured for the link
configuration of a gateway half.
Note that only one gateway-half NI may be configured per network.

Types

Enter DO for a direct dial link, or DC for a direct connect link.

New Name

Enter a link name. This new link name is used in place of the current link
name for an existing link configuration. The name can contain as many as
eight alphanumeric characters, and the first character must be alphabetic.

11-16

Gateway Half Network Interface Configuration

DIRECT CONNECT LINK CONFIGURATION
The Direct Connect Link Configuration screen supplies the information required to interface a
gateway-half NI to a non-dial link (that is, a leased line or a hardwired connection). This screen) shown
in Figure 11-7) is displayed when you select an NI link name and the link type DC at the Gateway Half
Network Interface Link screen (Figure 11-6) and press Its I mI~ or ( t 6 I 16i[; 'm. It is also
displayed when you type the path name:

@NETXPORT.NI.niName.LINK.nilink
in the command window of any screen and press I ENTER I, where niName is the configured gateway-half
NI name, and nil ink is the configured gateway-half Nilink name.
You must press
!:mli::~:1 to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the
flag is set to I.

Path:
~

NETXPORT.NI.niName.LINK.nilink
Start Device On Network Initialization (YIN)

I..

File:

Enable Idle Device Timer

filename.NET.SYS

Figure 11-7. Direet Connect Link Configuration Screen

11-17

Gateway Half Network Interface Configuration

Fields
Start Device
On Network
Initialization (YIN)

A Y(Yes) value means that the device is to be started when a NETCONTROL
START command is issued for the network interface being configured. An
N (No) means that a NETCONTROL ADDLINK command must be used to start
the device.
Default Value: Y
Range: Yor N

Enable Idle
Device Tiller

This field specifies whether the device is to be disconnected automatically if
no packets have been received or transmitted over the link during a
specified time period. This field is relevant only if a timeout value has
been entered in the network interface screen listed below
Related screens:
- NETXPORT .NI .niName

The Idle Device Timeout value is configured on this screen.
Default Value: N
Range: Yor N

11-18

Gateway Half Network Interface Configuration

GATEW A Y HALF DIAL LINK CONFIGURATION
Dial link configuration provides the information necessary to interface the gateway-half NI to a dial
link. This screen, shown in Figure II - 8, is displayed when you select an NI link name and link type DD at
the Gateway Half Network Interface Link screen (Figure 11-6) and press ( t 5 I ti~~ or ( (6 I
rjlit!. It is also displayed when you type the path name:

@NETXPORT.NI.niName.LINK.nilink

in the command window of any screen and press (ENTER), where niName is the configured gateway-half
NI name. and nil ink is the configured gateway-half Nllink name.
You must press ~.~i~!m;:~~~ to transfer the data displayed on the screen to the configuration file you
are creating or updating. You verify that the data record has been created by checking that the ....
flag is set to ~.

,;;~,:~",,:,119Q;~~~~:'~l~~~~~··
~Qg..D.a:;ltI~~~ill~~!m~i~;

Path:

NETXPORT.NI.niName.LINK.nilink
Enable DIAL 10 Protocol (YIN)

l!l~lli

::~:~::

Security String

Start Device On Gateway Half Initialization (YIN)

:[1'' 1::

Enable Idle Device Timer (YIN)

~
i" ~
:'..::.:."

File:

filename.NET.SYS

Figure 11-8. Gateway Half Dial Link Configuration Screen

Fields
Enable Dial ID
Protocol

A Y (Yes) value activates the DiallD Protocol for a dial link. The Dial m
protocol verifies the identity of a remote node and insures that both local
and remote nodes have the required security access.
The Dial 10 Protocol should be disabled (by entering N [NOD only to
connect a dial link to a remote node that does not support the Dial ID
Protocol (that is, a non-HP node).

11-19

Gateway Half Network Interface Configuration

Related Screens:
- NETX PORT .NI.niName. LINK
Configures a link name and type. Is on path to this screen.
- NETX PORT •NI. niName. PROTOCOL. DIAL. SECURITY
Configures security strings for this node.

Default Value: Y
Range: Yor N
This is the telephone number of this node)s partner gateway half. Enter the
telephone number as a combination of decimal numben (0 through 9),
dashes, and the following special characters:

Separator used for automatic call units that have second
dial-tone detect.

E Optional end-of-number indicator.

o One second delay (used for European modems and automatic
call units that require built-in delays).
, Defined by local phone system.

Defined by local phone system.

Enter' to disable outbound dialing.
is a personal computer.

A' is required if the destination node

Default Value: None

Security String

This is the security string of this node)s partner gateway half. It is relevant
if and the Dial ID protocol is enabled and security is enabled. The security
screen can contain as many as eight alphanumeric characteR. It must be
left justified and contain no embedded blanks.
Related Screens:
- NETXPORT .NI .gatename. LINK.linlcname
Dial ID protocol is enabled/disabled here
- NETXPORT. NI .gatename. PROTOCOL. DIAL
Security validation is enabled/disabled here.

Default Value: HP

Start Device

A Y (Yes) value means that the device is to be started when a NETCONTROL
START command is issued for this network interface. A N (No) means that
a NETCONTROL ADDLINK command must be used to start the device.

Default Value: V
Range: Vor N

11-20

Gateway Half Network Interface Configuration

Enable Idle
Device Timer

This field specifies whether the device is to be disconnected automatically if
no packets have been received or transmitted over the link during a
specified time perIod. It is relevant only if a nonzero timeout value has
been entered in the Gateway Half NI screen (see related screens below).
Related Screens:
- NETXPORT. NI. niName
Configures router network interface information.
The value
configured for the Idle Device Timeout is configured on this screen.

Default Value: V
Range: Yor N

11-21

Gateway Half Network Interface Configuration

NEIGHBOR GATEW A YS
The select screen in Figure 11-9 is displayed when you press the function key for 9o:·To... ·J"JiER~Et at
the Gateway-Half Network Interface Configuration screen (Figure 11-1). It is also displayed when you
type the path name:

@NETXPORT.NI.niName.INTERNET
in the command window of any screen and press (ENTER I. where the niName is the configured
gateway-half NI name.
Use the fields and the function keys of this select screen to perform the desired action.
• To define a new gateway configuration, specify the gateway name; then press ICici. The path for
the selected gateway name is added to the configuration file, and the data screen on the path is
displayed.
• To modify an existing gateway configuration, specify the gateway name; then press y.~.~~. The
data screen on the path for the specified gateway is displayed.
• To change the gateway name of an existing gateway configuration, specify the gateway name and
a new name; then press ft~h~me. The previously configured name is replaced, and the screen
displays the new name in display field under the label Configured Gateways.

• To delete an existing gateway configuration, use the delete key. Specify the gateway name, then
press ~elet.4!; when NMMGR prompts you for confirmation, press pelet~ again. The previously
configured'" 'name is deleted and is no longer displayed in a display .field under the label
Configured Gatewaya

11-22

Gateway Half Network Interface Configuration

Path:

NETXPORT.NI.niName.INTERNET

Configured Gateways

Figure 11-9. Neighbor Gateways Sereen

Fields
Gateway Name

Enter a name to represent this node's partner gateway half, through which
one or more remote networks can be reached. A gateway name can contain
as many as eight alphanumeric characters; the first character must be
alphabetic.

New Hue

(Required only when renaming.) Enter a gateway name to represent this
node's partner gateway half. This new gateway name is used in place of the
current gateway name for an existing gateway configuration. The name
can contain as many as eight alphanumeric characters; the first character
must be alphabetic.

11-23

Gateway Half Network Interface Configuration

NEIGHBOR GATEWAY REACHABLE NETWORKS
The Neighbor Gateway Reachable Networks screen is used to enter internet routing information. It
supplies the internet address of a neighbor internet gateway, remote networks which are reachable
through that gateway, and the distances to those remote networks. For the gateway-half NI there is only
one neighbor gateway, the partner gateway half.
The screen in Figure II-lOis displayed when you select a gateway name at the Neighbor Gateways
screen (Figure 11-11) and press ~~~ or Y~ii!. It is also displayed when you type the path name:
@NETXPORT.NI.niName.INTERNET.gate~yn

in the command window of any screen and press (£NJEiD, where niName is the configured gateway-half
NI name, and gatelJJayn is the configured gateway-half NI gateway name.
You must press ~:Fi!I~l!rr :~, to transfer the data displayed on the screen to the configuration file you
are creating or updating.
verify that the data record has been created by checking that the ::;:::'
flag is set to ~.

You

Path:

NETXPORT.NI.niName.INTERNET.gatewayn
Neighbor Gateway IP Internet Address
Configured Reachable Networks

IP Network Address

Hops

PAGE 1

IP Network Address

Figure 11-10. Neighbor Gateway Reachable Networks Screen

11-24

Hops

Gateway Half Network Interface Configuration

NOTE

The information configured in this screen can extend to more than 1 page)
if necessary) to allow configuration of more than 10 reachable networks.
Press ~i~~:!j[!~9" to proceed to a new page. Press ~~~l~l!~i~ to display a
prior page. Use tlr.~~:;;::·~g~ to display the. first. page (for example, if you
are viewing the third page, pressing ~'~1~!l.~:~9~ will immediately display
the first page). Press ~L.~~1.::;m~9~ to display the last page of reachable
networks that has been configured. To consolidate reachable networks
entries, press ~p.~~~~~i:;::~~~~.

Fields
Neighbor Gateway
IP Internet Address

Enter the IP address of this node s partner gateway half. This is the IP
address of the partner s home network) and is the same IP address that you
have already configured in the Internet Protocol Configuration screen for
the current NI.
Addresses are made up of a network portion and a node portion. The
possible classes of network addresses have the following forms (4. space~

Class C
Class B
Class A

CAnnn.nnn.nnnAxxx
BAnnn.nnnAxxx.xxx
AAnnnAxxx.xxx.xxx

where nnn is a value ranging from 0 to 25S) representing eight bits of the
network portion of an address, and xxx is a value ranging from 0 to 25S)
representing the node portion of the address. The leftmost group of nnn
has the following ranges for each address class:

Class C:
Class B:
Class A:

192-223
128-191
0-127

Default Value: None
Related Screens:
- NETX PORT •NI •niNamePROTOCOL • I P
The network address (network portion of the IP address) configured in this
screen must match the Neighbor Gateway IP Internet Address configured in
the current screen.

Reachable
Networks IP Network
Address
Con~lgured

Enter the internet addresses of the remote networks that can be reached
through the gateway half whose network address is configured in the
previous field. (Enter one address per line.) Only the internet portion of
the network address is significant for this field (see the description of the
Neighbor Gateway IP Internet Address field for valid formats of intemet

11-2S

Gateway Half Network Interface Configuration
addresses). The node portion must be entered; however, it may be set to all
zeros.

Configured Reachable
Networks Hops

Enter the internet hop count to the reachable network whose IP address is
configured to the left of the Hops field. (The internet hop count is the
number of full internet gateways that will be used to route a message to the
destination network. If two partner gateway halves are used as part of the
internet route, they are counted as one hop.)
Hop count is used internally to determine which neighbor gateway (if more
than one exists) is on the shortest path to the remote network. If more than
one gateway can reach a given remote network, and the number of hops to
the remote network is equal for each gateway, you can determine which
gateway the Network Transport will use by configuring an artificially high
hop count. The transport always uses the gateway with the smallest hop
count.
If the same hop count value is configured for multiple gateways, then the
Network Transport will choose internally from among the routes with
equal hop counts.
Default Value: None
Range:

1-32161

NOTE

To delete a reachable network entry, fill the field to be deleted with blanks
and press ~~~~~l!ij[~~i

11-26

LOOPBACK NETWORK
L--IN_T_E_R_FA_C_E_C_O_N_FI_G_U_R_AT_I_O_N

----I@]

The screens described in this section are used for configuring the loopback network interface. There is
only one branch of loopback network interface configuration. This is the protocol configuration branch,
which can be reached by pressing the ~:"tqd:·~OT()COL key on the LOOPBACK NETWORK INTERfACE
CONFIGURATION SCREEN. All of the loopback network interface configuration screens are Isited below,
with their places in the configuration tree indicated by indentation.

LOOPBACK NETWORK INTERFACE CONFIGURATION - This screen enables you to configure information
about a loopback network interface, such as network segment size and the number of buffers to be
allocated for loopback. From this screen, you can proceed to the protocol configuration branch.
PROTOCOL CONfIGURATION - You will reach this screen if you press ~;;!;:r~:'~ft,c)~ on the
LOOPBACK NETWORK INTERfACE CONfIGURATION screen. This screen allows you to choose to
proceed to IP protocol configuration.

PROTOCOL CONfIGURATION - This screen, which you will reach by pressing
on the previous screen, contains loopback default values which should not be
changed.
~.;,Jel;41!

NOTE

12-1

Loopback Network Interface Configuration

LOOPBACK NETWORK INTERFACE CONFIGURATION
The screen in Figure 12-1 is displayed when you select an NI name and the NI type LOOP at the Network
Interface Configuration Screen (Figure 8- 9) and press ~~~ or y~~\~. It is also displayed when you type
the path name:

@.NETXPORT.NI.niName
in the command window of any screen and press
NI name.

(ENTER It

where the niNams is the configured loopback

Whenever a transport user makes a connection to a user process on the same nodet all outbound packets on
this connection are turned around at the NI level and passed back up through the protocol stack to the
destination user. This screen supplies information necessary for this operationt performed by the
Loopback NI.
You must press "'R~~!!!j!l~~' to transfer the data displayed on the screen to the configuration fi"!~,,"r~~~
are creating or updating. You verify that the data record has been created by checking that the ~~~~;J
flag is set to ~.
From this screen you proceed to other screens used to configure the loopback network interface.

Network Segment Size (Bytes)
Number Of Buffers

File: filename.NET.SYS

Figure 12.-1. Loopback Network Interface Configuration Sereen
Press the

12-2

";_.:I.un:i~
'O'f:iViii!tj

function key.

Loopback Network Interface Configuration

Fields
Network Segment
Size

(HP modifiable) This is the size of the physical buffer for the loopback
network interface. No fragmenting or fragment assembly is performed on
the loopback NI. There is no limitation that only single physical buffers
(not chained buffers~ for example) can be passed across the I/O interface to
the board, because outbound data is turned around at the NI layer.
Therefore, if user data exceeds the physical buffer size, it is put into logical
buffers (chained physical buffers) that are the size of the user data.
Default value: 1024
Range: 1024-4224

Number Of
Buffers

This field specifies the number of buffers to be allocated for loopback. For
the loopback NI, there is no differentiation between outbound and inbound
buffers because an outbound buffer, when it is turned around at the NI
level, becomes an inbound buffer. As with other network types, buffer
configuration is based on the number of TCP connections that will use the
network interface. An allocation of two buffers per connection will suffice
for typical usage.
The default value is based on the assumption that the Network Manager
desires to allow no more than the default number of TCP connections (see
related screens below) to use the Loopback NI. Therefore, the default is
128 (default TCP connections) * 2 a 256 buffers. When there is more than
one NI, this value should probably be adjusted downward because the
connections might reasonably be expected to be spread over all the NIB
rather than be concentrated over only one NI. If you change the number
of TCP connections from the default value, you should reconsider the
number of inbound buffers for all NI's.
Related Screens

NETXPORT.GPROT.TCP
Maximum Number of Connections (default value of
configured on this related screen.

128) is

Default value: 256
Range: 32-2048

12-3

Loopback Network Interface Configuration

PROTOCOL CONFIGURA TION
The menu screen in Figure 12-2 is displayed when you press the function key for gq.~'t,q;;ri:.·.Ji;'.i:::.;·"'". . _: at
the Loopback Network Interface Configuration Screen (Figure 12-1). It is also dispi'aye'd"V;hen"'you 'iirPe
the path name:

@NETXPORT.NI.niName.PROTOCOL
in the command window of any screen and press [ENTER I, whf't"C "iName is the configured loopback NI
name.
For the loopback NI, you must configure the IP protocol. The ~~;

Path:
-

NETXPORT.NI.nlName.PROTOCOL

Configure Internet Protocol

PROBE

Configure PROBE Protocol (LAN Only)

DIAL

File:

":;":, function key label is displayed.

Configure DIAL Protocol (Router/Gateway Half Only)
Necessary Only If There Are Any Switched Links

filename.NET.SYS

Figure 12-2. Protocol Configuration Screen

Press the ~;:iil1~()~:~ function key.

12-4

Loopback Network Interface Configuration

IP PROTOCOL CONFIGURATION
The screen in Figure 12-3 is displayed when you press the function key for ~;::l;r-q!;;~;~'p at the Protocol
Confjguration Screen (Figure 12- 2). It is also displayed when you type the path···name:.. · . ·

@NETXPORT.NI.niName.PROTOCOL.IP
in the command window of any screen and press
name.

(ENTER I,

where niName is the configured loopback NI

This data-entry screen is used to supply information to the IP protocol instance for the network being
configured. Each NI has an IP protocol. The IP address field is a key element in IP routing and datagram
delivery algorithms. The other fields are useful for internal resource allocation and performance tuning.
You must press ~l~f~~~~:llillii~i to transfer the data displayed on the screen to the configuration fjle you
are creating or updating. You verify that the data record has been created by checking that the ;"r:".~ ';""
flag is set to ~.

'-:'i:!~l~;ql~f~~!~ii"":
ilil!!j!···....:··;::;;
NETXPORT.NI.niName.PROTOCOl.IP
Store & forward Buffers
(Enter 0 To Disable Store & Forward)
,]~§'~;~f:'" 'i' "::~~:l.l

I PIn te rnet Add res s
Internal Message Queue length
Fragment Assembly Queue Elements

File:

filename.NET.SYS

Figure 12-3. IP Configuration Screen

12-5

Loopback Network Interface Configuration

Fields
Store & Forward
Buffers

No store-and-forward buffen need to be configured for loopback.

Default value: 0

IP Internet. Address

The loopback address is always E 25 S. 25 S. 2SS. 2SS.

Default value: E 255.255.255. 2SS

Internal Message
Queue Length

This field should be 0 for loopback.

Default value: 0

Fragment Assembly
Queue Elements

This field should he 0 for loopback.

Default value: 0

12-6

1"--'-----------'~
LOGGING

CONF~GURA TION

Logging is configured for the purpose of recording events such as errors and console commands. You
configure logging for each of the subsystems of NS3000 and for NS3000 links. Each subsystem includes
different classes of events (such as internal errors). You can record logging to a disc file, the system
console and the logon device of a user. account. If you configure a logging class so that logging is
recorded to a user.account, the user will receive logged messages any time there is an active session for
that user.account. Table 13-1 provides a summary of the logging classes and guidelines for
configuration.
The logging configuration for the network transport (subsystem ID 3) must be in the same configuration
file as the network transport configuration, which must be in the group NET of the account SYS. The
recommended filename for the actual configuration file that contains the link and network transport
configuration is NSCONF. NET. SYS. If you use a different filename, you need to specify the configuration
filename with the CONF keyword each time you use the NETCONTROL START command to initiate the
network connection. Refer to the "Commands" section in Volume II.
The logging configuration for Network IPC (subsystem 10 5), Network Services (subsystem ID 6) and Link
Manager (subsystem 10 8) must be in the same configuration file, which must be named
NMCONFIG. PUB. SYS. This file is shared with other data communication subsystems that use NMS, such
as SNA NRJE. If you do not want to manually configure logging, Guided Configuration, described in
Section 6, will configure logging data for you. Logging data for subsystem IDs 5, 6 and 8 will be placed in
NMCONFIG. PUB. SYS, while logging data for the network transport (subsystem ID 3) will be placed in your
other configuration file (recommended name of NSCONF. NET. SYS).
Always work on a copy of your configuration file, not the actual file.
Follow these steps to reach the logging configuration screens for manual configuration.
• Issue the run command for NMMGR; the Open Configuration/Directory File Screen is displayed.
• Enter the name of the configuration
Con f i gu ra t ion f lIe name field.

file

created

updated

the

• Press the appropriate function key (~~~li~~i!i.:tl9 or ~;~~~".!j!ll~~~).j:i.ti);the Main Menu SCreen is
displayed.
• Press the function key for

~;i;l[1Jf!':

:;;~~ti;

the Configuration Screen is displayed.

• Press the function key for ~!!:!['t~I!m~~~~I~;the Logging Configuration Screen is displayed.
For more information on these steps. refer to "Getting Started with NMMGR" in Section 5.

13-1

Logging Configuration

Three screens are used for logging configuration. These screens are listed below.

LOGGING CONFIGURATION - This screen allows you to add, delete, rename or update a subsystem ID
logging configuration.

LOGGING CONfIGURATION: LOGGING CLASSES - This screen allows you to select the classes of 10iBing
events you wish configure for each subsystem.

LOGGING CONfIGURATION: CLASS DATA - This screen allows you to configure where you want logging
events listed for a particular logging class.
NOTE
NetlPC logging is activated at system startup, Network Services logging is
activated when the Network Services are initiated (NSCONTROL START
command), Link Manager logging is activated when you initiate the
Network Transport (NETCONTROl START), and Network Transport logging
is activated with NETCONTROL START. (Guided configuration, described in
Section 6, automatically configures logging for you.) You may change
logging configuration using NMMGR. For a new logging configuration to
take effect for a specific subsystem, the subsystem must be deactivated and
restarted. The steps that must be taken for each subsystem are:

Subsystem

Steps

Network Transport

NETCONTROl STOP (if already active)
NETCONTROl START

NetlPC (sockets)

restart the system (warmstart, coolstart, update start or coldstart)

Network Services

NSCONTROL STOP (if already active)
NSCONTROL START

Link Manager

NETCONTROL STOP (if active)
SNACONTROL STOP;NOOE=nodename
repeat until all SNA nodes are stopped

SNACONTROL START;NOOE=nodename
NETCONTROL START

13-2

Logging Configuration

TABLE 13-1. LOGGING CONFIGURATION GUIDELINES
Subsystem
Name

Class Name

Events

Enable
Console
Logging?

Enable Disc
Logging?

SUBOOO3

CLASOOO1

Serious Internal Error -Causes SYSFAIL #969.

YES

Network
Transport

CLASOOO2

Internal Error/Operator
Attention

YES

CLASOOO3

Non-Critical Errors.

YES

CLASOOO4

Nodal Messages (Start/Stop).

YES

CLASOOO5

Informative Messages.

CLASOOO6

Statistical Information.

YES

SUBOOO5

CLASOOOO

Internal Errors.

YES

Network fPC

CLASOOO1

Resource Errors.

YES

CLASOOO2

Informative Messages.

SUBOOO6

CLASOOO2

Resource Errors.

YES

Network
Servius

CLASOOO3

Internal Errors.

YES

CLASOOO4

Detailed Events. (Enable
with NSCONTROL LOG.)

YES

CLASOOO5

NetlPC Internal Errors.

YES

Internal Errors.

YES

SUBOOO8
Link
Manager

CLASOOOO

PC Link
Manager

CLASOOO1

The logging classes are described in detail in Section 3 of Volume II. How to use the log messages for
troubleshooting is described in the NS3000!Y Error Message and Recovery MaltU~ and how to format
the lOB file for examination is described in Section 3 of Volume II.

13-3

Loggm, Configuration

LOGGING SUBSYSTEMS SELECTION
The screen in Figure 13-1 is displayed when you press the function key for
Configuration Screen. It is also displayed when you type the path name:

@LOGGING
in the command window of any screen and press

OCNfEiD.

Use the fields and the function keys of the select screen to perform the desired action.
• To select a new subsystem ID for logging configuration. enter the subsystem ID number, then
press
The path for the selected subsystem 10 is added to the configuration file, and the
LOlging Classes Screen on that path is displayed. For NS3000 and NS3000 links, valid subsystem
IDs are SUB0003 (Network Transport), SUBOOOS (Network IPC). SUB0006 (Network Services), and
SUB0008 (Link Manager). NMMGR prompts you for the correct format of a subsystem ID
(SUB:t:::c=) but does not check that the lSubsystem ID you enter is a valid NS3000 or NS3000 link
subsystem 10.

DI.

• To modify an existing subsystem ID logging configuration. specify the subsystem ID; then press
"'m"'
The Logging Classes Screen on the path for the specified subsystem ID is displayed.
• To change the name of an existing subsystem 10 logging configuration. specify the subsystem ID
and a new subsystem ID; then press R.n.iml. The new subsystem ID replaces the previously
.
.
configured subsystem 10.
• To delete an existing subsystem 10 logging configuration. specify the subsystem ID. then press
.
_,' The previously configured subsystem ID is deleted.

13-4

Logging Configuration

~
Path:

LOGGING
Subsystem name
New name
Subsystems Configured for Losging

File:

filename.group.acct

Figure 13-1. LOiging Configuration Sereen

r
13-5

Lo"in, Configuration

LOGGING CLASSES SELECTION
'~
The screen in Figure 13-2 is displayed after you specify a subsystem ID on the Log,ing Configuration
Screen (Figure 13-1) and press I~i or Iii.. It is also ~isplayed when you type:

@LOGGING.SUBbbbb
in the command window of any screen and press enter. where SUBbbbb 11 the subsystem ID number of the
configured subsystem.
The Logging Classes Screen allows you to select the classes of logging events you wish to configure for
each subsystem.
Use the fields and the function keys of the select screen to perform the desired action.
• To define a new logging class to configure, specify the class name. then press lid. The path for
the selected class name is added to the configuration file and the data screen on the path for the
specified class is displayed. Refer to Table 13-1 for valid classes of each NS3000 subsytem and
an NS3000 link. NMMGR prompts you for the correct format of a class name (CLASbbbb) but
does not check that the class name you enter is valid for the subsystem you are configuring. Use
Table 13-1 to check that a class name is valid for the subsystem you are configuring.
• To modify an existing class configuration. specify the class name; then press ~lIIil:l. The data
screen on the path for the specified class name is displayed.
• To change the name of an existing class configuration. specify the class name and a new name;
m:!!. The new class name replaces the previously configured class name.
then press' . .:
• To delete an existing class configuration. specify the class name. then press :~.:::::"' J,]jI.
previously configured class name is deleted.

13-6

The

Logging Configuration

Configured Logging Classes (Under Subayatemt

Figure

13-~.

LOlling Classes sereen

13-7

Logging Configuration

LOGGING CLASS DATA
The screen in Figure 13- 3 is displayed after you specify a class name on the LOlging Classes Screen
(Figure 13- 2) and press M~ or ~EI~'. It is also displayed when you type:

@LOGGING.SUBbbbb.CLASbbbb
in the command window of any screen and press enter, where SUBbbbb is the subsystem ID number of the
configured subsystem. and CLASbbbb is the configured class name.
.
You must press p';~,,~!!m!ti~! to transfer the data displayed on the screen to the configuration file yo..~
are creating or updating. You verify that the data record has been created by checking that the;"::
flag is set to I.

Path:

LOGGING.SUBbbbb.CLASbbbb
i;:'

Enable Console Logging? (YIN)
Enable Disc Logging? (YIN)
Current number of users enabled for logging

Users enabled for logging (User.Account):

File:

filename.group.acct

Filure 13-3. Logging Configuration: Class Data screen
This screen allows you to configure where you want logging events listed for the class. Vou can list these
events to a disc file for later analysis and to the system console so that the system operator receives the
logging messages. In addition. you can display logging events at users'list devices. This may be valuable
to allow the network manager to monitor NS console activity from an alternate terminal. This screen
displays the users enabled for logging.

13-8

Logging Configuration

Fields
Enable Console
Logging?

(Required.) Enter Y (YES) if you want logging events for this class to be
displayed at the system console, N (NO) otherwise.
Refer to Table 13-1 for guidelines.
Default: N.

Enable Disc logging?

(Required.) Enter Y (YES) if you want logging events for this class to be
recorded in a disc file, N (NO) otherwise. The filename that NMS uses is
NMLGnnnn. PUB. SYS, where nnnn is a number from 0000 to 9999. This
file is used for logging by all logging classes in all subsytems. At each MPE
system startup, or when a file is full, NMS creates a new
NMLGnnnn. PUB. SYS file, naming each successive logging file by
incrementing nnnn. When NMLG9999. PUB.SYS is full, NMS names the
next logging file NMLGOOOO. PUB. SYS
Refer to Table 13-1 for guidelines.
Default: Y.

Current number of
users enabled
for logging

(Display only.) This field is provided for your information.

Users enabled for
logging

You can display logging events for this class at usen'list devices. Enter as
many as three user names in the form user. account. Use only
alphanumeric characters; you cannot use MPE wildcard characters.
NMMGR sorts this list alphabetically and deletes duplicate entries after
you press M·~.·~'.:i;;~~~.

NOTE

The logging configuration guidelines in Table 13-1 should be followed
unless your UP representative tells you otherwise. Not following these
guidelines may result in the degradation of system performance.

13-9

I~N_E_T_W_O_R_K_D_IR_E_C_T_O_R_y

A network directory contains information required for one node to communicate with another node in

the same catenet. This catenet-wide data is managed through two interfaces--VPLUS screens for
interactively configuring the network directory, and a command-driven interface to collect and merge
directory information from remote nodes into the directory on the local node.
NMMGR provides the following functions regarding the network directory.
• The ability to add, uPdate and delete entries in the directory by node name. This can be used by
a Network Manager to maintain a master network directory.
• A means of presenting directory information for review and inspection.
• The ability to merge a remote directory with a directory on the local node.
• A mechanism to automatically update directories on a group of remote nodes by using a
background stream job, controlled from a central administrative node. Central administrative
nodes are described in more detail later in this section.
The file structure that accompanies the network directory functionality is quite different from that used
throughout the rest of NMMGR. The directory resides in its own file. With the directory. there is no
screen-to-record correspondence and no concept of a hierarchical file organized u a tree structure with
associated paths.
NOTE

The network directory uses a KSAM file pair. Therefore, if coPyilll the
directory. be sure to copy both the data file and the key file.

14-1

Network Directory

WHAT A NETWORK DIRECTORY PROVIDES
A Network Directory is a repository for information about nodes in a catenet. Each entry in a directory
consists of a node name and one or more path reports, called a path report list. A path report list contains
the basic information about a node. These path reports are used by the transport to establish
internetwork connections.
Not all nodes require a network directory. A node on a LAN can determine connection information
about a node on the same LAN by multicasting a Probe request to the target node. The target node, in
response to a Probe request, will supply the connection information by multicasting a Probe reply back to
the requesting node. The Probe request/reply mechanism is sufficient to obtain connection requirements
in a LAN environment.
The non-LAN network interface types supported by NS3000 do not use demand requests such as Probe.
Therefore, a directory of information about all nodes in the catenet is required to provide the same type
of information that LAN Probe requests provide.
Probe requests can be used only when the source and destination nodes are on the same LAN. Also, they
must both be HP nodes because non-HP nodes do not support Probe. Not all LAN nodes that support the
Probe protocol need to contain a network directory because they can request the use of a directory from
another node, called a proxy server, on the same LAN. A proxy server is a node on a LAN that contains a
network directory and has been configured as a proxy server. By using the Probe protocol, a LAN node
without a directory can multicast a request for a proxy server. For good measure, you should designate at
least two nodes on a LAN to be proxy servers.
For details on the configuration of path resolution methods (Probe, Proxy Server, Network Directory) for a
given node, refer to the Global Transport Configuration Screen in Section 8.

Path Report Lists
A path report list describes the addressing information and protocol stacks for a given node. Protocol
stacks define the layers in a machine's architecture, and the protocols in those layers, that information can
pass through. An example of a protocol stack is TCP with checksum error checking (level 4) over IP (level
3i) over IEEE802. 3 (level 3s), commonly indicated in the format: TCP.IP.IEEE802. 3.
In the network directory, node names must be unique so that a single path report list can be identified.
Many of the protocols on different hosts will be the same, but the addresses of the machines will not be
the same.
A path report list is broken down into path reports. One path report list comprises all path reports for a
given node. A node has one IP address and normally one path report for each network it belongs to. A
node may be a member of as many as eight networks. The following figure shows the organization of
path reports in the network directory.

14-2

Network Directory

NODE 1
IPAddr 1

Path(s)
IPAddr 2

Path(s)
IPAddr 8

Path(s)

NODE 2
IPAddr 1

Path(s)
NODE n

Figure 14-1. Organization of Path Reports

Global and Local Entries
Path report lists can be configured as either Global or Local entries in the network directory. Global
entries (the default) can be merged into other directories.
Local entries are introduced for configuring localized network directory entries, thus providing a
mechanism to restrict directory data from being propagated throughout the network. Let us consider
some situations where this type of restriction could be useful. Suppose a network manager wants to
change the configuration for users on a single host, but not for everyone else. He can configure two
network directory entries- -one Local, used by host users, and one Global, used by everyone else when
establishing connections to the host. For example, suppose Node A sets up a new link to Node C, but Node
A doesn't want other nodes (already connected to A) to know about Node C until the new link is tested.
Users on Node A can configure a Local entry, which will contain information about the new link not
included in the Global entry configured for users on other nodes. Other uses of local entries could include
adding node names for local-node use only, or being able to direct which way to access remote nodes
depending on your configuration of local entries.
When both local and global entries entries exist in the directory, the Network Transport will use the
LOCAL entry.
Whenever a user activates the Network Transport subsystem on a node, a path report list describing the
current node is automatically generated and entered into the local configuration file. The path report
can be copied from the configuration file into the Network Directory using the MERGEDIR command,
described in detail later in this section. The MERGEDIR command allows a user to configure the directory
easily in most cases. Exceptions are configuring non -HP nodes and first -time links, where information
cannot be taken from a remote directory file and merged) but must be entered manually.
The MERGEDIR command is part of a maintenance interface provided primarily to support the updating of
directories from within a batch job. Using this method, a job or series of jobs can be scheduled at regular
intervals to copy and then merge remote directories into the local-system directory. In this way, the
collecting and merging of network-wide data is somewhat automated.

14-3

Network Directory

Roles and Interfaces
The network directory interface you use--screens or commands--will depend on your job function and
whether you are creating or updating a directory. In general. the network directory configuration screens
will be used by node managers when creating directories, and the maintenance mode interface (commands)
will be used by a catenet administrator and network managers when updating directories.
The reason that screens, not commands. are used to create a directory is that a new node is at first
unknown to existing nodes. This means that an existing node cannot use only commands to merge its
directory to a new node. The node manager of a new node must use configuration screens to manually
enter path report information about at least one existing node. Then. the new node would be able to
merge its directory with the directory of the existing node. provided that someone also enters path report
information about the new node into the directory of the existing node.
When a new node is added to a network, or when an existing node changes its configuration, the network
manager must be notified of the new path report information. This exchange of information should take
place within each network in the catenet so that, periodically, each network manager can pass this
information to the catenet administrator. The catenet administrator can then stream a job, using
commands from the maintenance mode interface, to update the central administrative node on each
network. Each network should have one node designated as a central administrative node. as shown in
Figure 14-2. This is the node that will be updated first, in terms of any global information that can be
shared among all nodes on its network. This can include internet routing information in addition to
network directory information.
Figure 14-2 shows the central administrative nodes of two router networks that are connected by a
gateway-half link.

14-4

Network Directory

NET 2

NET 1
(Central

AdminJ

Figure 14-2,. Central Administrative Nodes
Once the central administrative node on each network has been updated with new catenet-wide
information. these nodes can be used to update all other nodes. Each network manager can stream a job
to merge the newly updated directory from the central administrative node into the other directories on
the network.
This is just a general discussion of how directories can be updated on a periodic basis. Of course. a specific
directory may need to be updated sooner. For example. suppose you add a new node and manually
configure its directory. Now. you have path report lists about other nodes. but they do not have your
path report list. If you need to set up immediate communication with a node or group of nodes and
cannot wait until the periodic update. you can send your connection information to the desired nodes so
that they can enter your path report list. Or. you can send your connection informq.tion to one directly
connected node. In this case. the directory of the directly connected node (first-time [nk situation) can
be updated manually. then merged into other directories to include information about the new node.

14-5

Network Directory

CONFIGURA TION SCREENS
The figure below shows the relationship of the vanous VPLU5 screens used in configuring the directory
through the NMMGR block mode interface:

OPEN FILE (directory)

j
Print Dir

.~-------

NETWORK DIRECTORY MAIN
UPdate
Dir

--------.~

Maintenance
Mode

NETWORK DIRECTORY SELECT NODE NAME
Delete, Rename,
Add, Update

NETWORK DIRECTORY DATA
Update Data
Figure 14-3. Network Directory Screens

Following are the configuration screens and descriptions of the fields on each screen. There are two ways
to access the Network Directory functions: 1) open or create a directory file on the initial NMMGR
screen, the Open Configuration/Directory File Screen, 2) issue the NETDIR command from any screen, at
any time alter having opened a network directory file. Either action will bring you to the first screen in
sequence, the Network Directory Main Screen.

14-6

Network Directory

NETWORK DIRECTORY MAIN SCREEN
This screen is displayed when you press the function key for 9pel1,:WJ).~r~~.~:ri or ~f~~~~t~;P:~!~~~l~ at
the Open Configuration/Directory File Screen. This screen is the main select screen from which all
directory functions are accessed. The currently opened directory is displayed at the bottom of this screen
and all subsequent Network Directory screens. The percentage of the Network Directory that is full is
shown in the lower right corner of the screen.

UPDATE

Modify the directory (Add, Delete, Update).

Print the directory to FORMLIST.

MAINTENANCE -

Enter maintenance mode interface (Merge, Expand, etc.)

Directory is

full

Directory: NSDIR.PUB.SYS
j:;:I>R I NT:;;:;:MAI NT .
:~;;~i~Q~l~c;:H~I[~[[ J::;;'Q~ f>!{i:~~il. ,':J4ode
:~:~tJP.oA it':::i

Figure 14-4. Network Directory Main Screen

I, Update Dir to modify the contents of the directory by adding, deleting and updating node
Press ("
names and path reports. If you press this function key. you will be taken to another screen, the Select
Node Name Screen, from which you can visit the Network Directory Data Screen. The Network
Directory Data Screen allows you to manually configure path reports about other nodes in the catenet.
Although you often will use job streams or simple commands for adding information to your network
directory, there are times when manual configuration is required or desirable. It is required when a new
node has been added to the catenet, and you wish to update another node·s directory with information
about this new node. You cannot use the MERGEDIR command until this new information has been added
to the existing directory. Therefore) you need to physically receive the path report lists from the node
manager of the new node or from that node)s network manager. After obtaining this information, you
can use the screens to configure the path reports about the new node. Once you have done this, you can
use MERGEDIR in the future for updating purposes because you now have this new node's connection
information in your network directory.

14-7

Network Directory
Whenever you do not have access to the necessary configuratton file or directory file, you are required to
use the screens for configuring directory information.
There may also be situations when you choose to use the screens to update your file even when other
methods are available. For example, if you are updating one path report list, it might be easier to use the
screens than to use commands.
Press ( t 2 " Print Dir to print out a copy of the riirectory to formal designator FORMLIST, device class
LP. The output is the same as for the lISTDIR l.\Hl1mand. See the "LISTDIR Command Sample Output"
subsection for an example of LISTDIR output. You can lJSe a file equation for FORMLIST to redirect the
output to another device class or disc file. To set a fdt et4uatlon without leaving NMMGR, use the
appropriate MPE command in the command window
Press ( t 3 " Maint Mode to enter the command interface to perform directory merging or to expand the
size of your directory. Once entered, you can return to this point only by issuing the maintenance mode
EXIT command. Within the maintenance mode interface, command input is read from the formal
designator NMMGRCMD, which defaults to $STDINX.

14-8

Network Directory

SELECT NODE NAME SCREEN
This screen is displayed when you press QPdate::~plt at the Network Directory Main Screen for the
purpose of modifying your directory using manual configuration. The function of this screen is to display
node names that are currently configured in the directory) and to allow you to delete) rename) add) or
update information about a node.

Node Name
New Name

'[1:1 Globa I?

!ooJ;~~;

New Global

Configured Entries

Node Names

Figure 14-5. Network Directory select Node Name Screen
Press ( }' 1 I) Next Page and [ }' 2 I, Prev Page to see additional nodes that have already been
configured. The Node Name and Global? fields can be used in conjunction with these keys to browse
through the directory efficiently. See the discussion below under the Node Name field.
Press ( }' 3 I, Delete to delete the named node from the directory. Deletions are confirmed by a second
press of the key.
Press [ t 4 ., Rename to change the name and or Global/Local flag setting for the entry. You generally
will not have reason to change a node name) unless you previously made a typographical error. You
occasionally may need to change a Global/Local flag setting. Refer to the "Global and Local Entries"
subsection for a discussion of Global and Local path reports.
Press [ }' 5 I, Add to add the named node to the directory. You are taken to the Network Directory Data
screen.

14-9

Network Directory
Press ( f 6 I) Update to update path reports for the named node. This includes deleting part, but not all,
of a node's path report list. You are taken to the Network Directory Data Screen.

Fields
Node Name

The name of the node on which to perform a function. This field can be
used in two ways) depending on which function key you use.
\Jse the Add; Delete, Rename and Update functions as described above to
change the current information in your network directory. When used in
conjunction with these fields, the Node Name field must contain a fully
qualified node name.
The Node Name field serves a different purpose when used with the
Prev Page and Next Page functions. When used with these function keys,
the Node Name field is used to browse through a specified part of your
network directory. You can enter part of a node name in this field to
designate which node names you want displayed. For example, if you enter
the value MAY, and press Next Page, the list of nodes will begin with the
first matching node name--MAYTAG. fI NANCE. IND, for example-- and
continue throught the rest of the alphabet until all node names between the
letters MAY and Z are listed.
Your node names do not need to be fully qualified with domain and
organization fields when used with the Prev Page and Next Page functions.
Default value: None

Global?

The Global/Local setting for Node Name. The acceptable values are Y or
N. When the Prev Page and Next Page function keys are used, only node
names whose Global/Local setting matches the value in this field will be
displayed. Therefore, set this field accordingly when displaying node
names.
Default Value: Y

New Name

New name to be assigned to the node with the Rename function. The only
time this field is used is when you use Rename.
Default value: None

New Global

The Global/Local flag setting for the node named in the New Name field.
The acceptable values are Y or N. The only time this field is used is when
you use Rename. The New Name field can be left blank if you wish to
change only the Global/Local setting.
Default value: None

Configured Node Names
& Global Flaa

14-10

Display-only fields that show node names and their Global/Local Flag
sethngs that are already configured in the directory.

,~,

.....
.~:~)

Network Directory

NETWORK DIRECTORY DATA SCREEN

te.

This screen is displayed when you press Add or Upcl~ at the Select Node Name Screen. The function of
this screen is to configure path report data for a node. The Node Name field at the top of the screen
shows the name of the node that corresponds to the other data on the screen.
Transport Services are set for all paths.
Below Transport Services on the screen are the fields- - I P Add res s, Ty pe, and Add it iona 1
Address--that make up path reports. One path report is configured for each NI on a node. Therefore,
because the maximum number of Nls per node is eight, each node can contain as many as eight path
reports. When adding or updating a path report, make sure that the I P Add resa and type fields are
configured. and that the Additional Address field is configured when necessary. The description of
the Add it iona I Add ress field cites the case when this field can remain blank.
To delete a path report, clear all three path report fields to blanks.
Once you have completed entering. information on this screen, you must press V~~~'- ~~.. for this
information to actually be entered into your network directory file.

Node Name:

mm.

Transport Services:
II:v:J TCP
ilt,u Checksum for TCP required (Y) or optional (N)
Ilitl PXP
IP Address

• 1
2

= IP
= IP/IEEE802.3

Directory: NSDIR.NET.SYS

I[~il~~~ti~:~~
Figure 14-6. Network Directory Data Screen

14-11

Network Directory

Fields
Transport services

These three fields describe the Transport Services that should be configured
in each path. AU customers should have TCP and PXP configured. The
Checksum setting indicates whether checksumming is optional (N) or
req uired (Y) for TCP
Note that the selection of Transport Services here nlust match the settings
in the remote node's configura tion file. The path of the data screen that
contains TCP configuration is NETXPORT. GPROT •TCP, and the path of the
data screen that contains PXP configuration is NETXPORT. GPROT • PXP.
Because the same data must appear on more than one screen, it would be
safest to use the default values to help avoid mismatched values.
Mark the selected services with a Y or an N. The Transport Services and
their default settings are:
TCP: Transmission Control Protocol (default Y)
TCP Checksumming optional or required (default N)
PXP: Packet Exchange Protocol (default Y)

IP Address

One IP address should be entered for each LAN or Router network
interface configured on the node. Each address must match an IP address
configured in the node's configuration file. The path of the screen in the
configuration
file
that
contains
IP
addresses
is
NETXPORT. NI • niname. PROTOCOL. I P.

Default Value: None
Type

A number indicating the type of path to configure:
1: I P. This path type should be selected when the network interface type
is ROUTER, or LAN with the Probe protocol configured.
2: I P/ I EEE802 • 3. This path type should be selected when the network
interface type is a LAN and the node is a non-HP node, which does not
support the Probe protocol.

14-12

Network Directory
Additional Address

A lower-level address, which depends on the Type.

Type 1 paths do not contain lower-level addressing information. You can
leave the field blank, or the keyword "NONE" can be entered.
Path type 2 requires a station address, which is a string of six hexadecimal
bytes, separated by dashes (XX-XX-XX-XX-XX-XX). This path type is used
only for a LAN non-HP node, which does not support the Probe protocol.
The station address must be the same as the station address entered in the
node's configuration file (screen path LINKCONF.l ink.name for IEEE802. 3;
field Local Node Address In Hex).

14-13

Network Directory

DIRECTORY MAINTENANCE MODE INTERFACE
Several commands are available for updating information in a network directory. These commands
primarily will be used within batch jobs for updating directory information on remote nodes.
The main features of this utility are:
• It generates a job stream to sequentially update a list of nodes.
• The list of nodes to update is user-defined.
• The process provides logging information.
• The process is "recoverable. II
• Commands executed on the remote system are user-defined.
You provide a list of node names that are to be updated (which can be easily generated) in addition to the
name of a command file to be executed from the NMMGR Maintenance Mode interface. From these two
files, a job stream file is generated which, when executed, attempts to log on to each node named in the
list and apply the commands read from the command file. The success or failure status of each nodal
update is recorded in the node list file, along with the date and time of the event. This node list "control"
file may be used again to retry updates on failed nodes, after the source of the failure has been
determined and corrected.
In order to use these commands on a remote node, your local node's network directory file must contain an
entry for the node whose directory you wish to update. Without an entry, you would not be able to log
on to the remote node because you would not have its connection information. For this reason, the
commands are generally used for updating directories on existing nodes. However, it is possible that these
commands can be used to create a directory on a remote node. To accomplish this, the node manager of
this new node would have to verbally notify you of this new node's existence. You then would have to
enter the new node's connection information into your network directory. Once this information is
entered into your directory, you have the capability to log on to the new node and merge your entire
directory to create a version of this directory on the new node.
The network directory command interface is directly accessible by running NMMGR. PUB. SYS from a
stream job, by pressing the Malnt Mode key at the Network Directory Main SCreen, or by running
NMMGR.PUB.SYS with a file equation' for the formal designator NMMGRCMD set to a command file. An
example of such an equation is : FILE NMMGRCMD=CMDFILE.
Command input is echoed to $STDLIST if run from within a stream job or when the input is read from a
command file. Blank command lines may be entered freely.

14-14

Network Directory

OPENDIR Command
The OPENDI R command is used to gain access to a Network Directory file. For example, suppose your
node's configuration has changed, and you want to update a remote node's directory to reflect this change.
You can log on to the remote node and open its directory file using the OPENDIR command. Syntax:

OPENDIR dirname

The format for dirname is a standard MPE file system name: FILENAME[.GROUP[.ACCOUNT]]. A file
lockword cannot be specified. A file equation may be used.
Any currently opened directory is closed and dirname is opened for read/write and share access. If the
directory does not exist, then an attempt to create it is made; the file is then opened for read/write and
share access.
The capacity of the network directory is 500 entries.

DELETENODE Command

" ...' . "
"

The DELETENODE command removes an entry from the directory. For example, suppose you have logged
on to a remote node and opened its directory using the OPENDI R command. Using DELETENODE, you can
now delete a node from this remote directory. Syntax:

"
LOCAL}
DELETENODE [nodename] [; { GLOBAL]

If you omit the nodename option. all path reports for all nodes will be deleted.
If you omit the nodename option while running the DELETENODE command from a session, the
confirmation message Are you sure? will be displayed, requiring a response. However. if you are
running a batch job, no opportunity for confirmation is available. Therefore, be especially careful not to
omit the nodename option unless you really intend to delete all entries in the opened directory.
When the nodename option is supplied, only the path reports for the specified node will be deleted.

LOCAL and GLOBAL are optional and qualify which entry is to be deleted when the same node name has a
LOCAL entry and a GLOBAL entry.

14-15

Network Directory

MERGEDIR Command
The MERGEDIR command is used to merge one or more entries from one directory file into the currently
opened directory file, or to merge a single entry from a configuration file into the opened directory file.
Syntax:

. [tnodenamel} [;{LOCAL}l [; {KEEP
MERGEDIR {othe~t~
NOKEEP } 1
conftgftle
GLOBAL
TIMESTAMP

The parameter otherdir is the name of the directory from which entries are to be merged into the
opened directory. The option nodename is the name of a single node entry to be merged; if omitted, all
entries in otherdir are merged.
The parameter configfile is the name of a node's configuration file from which to merge the path
report list of the node. As a rule, you should perform this type of merge on the same node's network
directory immediately after you have activated the network transport. When the network transport is
activated, a path report list is automatically entered into the configuration file. By performing this type
of merge, you are bringing the path report of the node into the network directory of the same node. A
node having connection information about itself is not really needed except for loopback, but having it in
'~."
the directory is necessary so that this information will be included if this directory is merged into the
directory of another node. The option nodename cannot be supplied if merging from a configuration f i l e . ]
Both of the file names must be standard MPE file system names. Lockwords are not permitted. A file
equation may be used for otherdir, but not for configfile.
Either otherdir or configfile, but not both, may be specified.

LOCAL and GLOBAL define which class of entry is to be merged if the source is a directory file, and define
the flag setting in the target directory if the source is a configuration file. The default is GLOBAL
The last three options, which can be specified only when merging from another network directory file,
define the manner in which duplicate entries are to be handled.

KEEP

Duplicate entries found in otherdir are ignored; the corresponding entries in

dirname are not changed.

NOKEEP

Unconditionally replaces duplicate entries in dirname with the corresponding
entries from otherdir.

TIMESTAMP

R.eplaces duplicate entries in dirname only when timestamp information indicates
that a corresponding entry in otherdir was created more recently.

If no option is specified, TIMESTAMP is assumed.

The node name of each duplicate entry is displayed, along with the action taken, either REPLACED or

UNCHANGEn

14-16

Network Directory
Entries that exist in otherdir (or configfile), but not in dirname, are entered into dirname and are
displayed along with the word ADDEO.
After all entries have been examined, a summary is displayed, indicating the total number of entries added
and replaced.

LISTDIR Command
The LISTOI R command displays information about entries configured in the directory.
Syntax:
LISTDIR [nodename]

If the nodename option is omitted, all entries in the directory are listed.
If the nodename option is supplied, the information about this node will be displayed.
The output is directed to formal designator fORMLIST, which defaults to $STDLIST, but may be
redirected with a file equation. See the "LISTDIR Command Sample Outputll subsection for an example
of LISTOI R output.

EXPANDDIR Command
The EXPANDDIR command increases the capacity of the currently OPened directory file.
Syntax:
EXPANDDIR numrecs

The parameter numrecs is the number of records to be added to the network directory file. The number
of records used by one node's network directory entry is one greater than the number of network addresses
belonging to the node.
NOTE

To run this command, you must be logged on to the account that contains
the directory file, and you must have exclusive acceSs to the file. Given
this second constraint, the standard network directory file NSDI R. NET. SYS
may not be expanded while the network transport is activated because the
transport needs access to this directory. Therefore, the transport must be
stopped to increase the capacity of this directory file.

14-17

Network Directory

HELP Command
The HELP command displays help text about MPE commands and network directory commands.
Syntax:
HELP [corrrmndname [,qualifier]]

Typing the HELP command by itself allows you to enter the MPE help facility. At this point, an overview
of available commands is displayed, and command names may be entered at the prompt. Type EXIT to
return to the NMMGR prompt.
The cOtmandname option may be included to obtain an overview and the syntax for a specific command.
In addition. one of the optional qualifiers-- PARMS, OPERATION, EXAMPLE, or ALL-- may be included to
receive more detailed information about a command. You are returned to NMMGR's prompt after help
text is displayed.

:MPE Command
Syntax:
:mpecorrrmnd

The parameter mpeoOlTl'mnd is any command that can be executed by means of the MPE COMMAND
intrinsic. Examples of how this can be useful include embedding comments in a sequence of commands
using :comment •.. , or executing :listf or :tell, or executing :file for redirecting output of the
LI STDI R command.

14-18

Network Directory

EXIT Command
The EXIT command terminates the command interface.
Syntax:
EXIT

If you have lnvoked the interface from an NMMGR screen. you are returned to the Network Directory

Main Screen if a directory file was left open upon exit; if no file is currently open, you are returned to the
Open Configuration File/Directory Screen.
If you have invoked the interface directly from the MPE command interpreter. the EXIT command closes

any opened directory file, and the program terminates.

MAKESTREAM Command
The MAKESTREAM command generates a stream job to update remote directories or configuration files.
Syntax:
MAKESTREAM streamfile~

nodefile, cmdfile

All three file names must be in standard MPE file name format.
The parameter streamfile is the name of a file to receive the job stream text. The file must not
already exist.
The parameter nodefile is the name of an ASCII editor-type file that contains a list of nodes to be
updated. It also serves as a log file. Note that the file name must be qualified with group and account
names to the extent that the job (default logon: NETADMIN. SVS) requires it.
The simplest way to generate this file is to redirect the output of a LISTDIR command into an ASCII file:

NMMGR> :file formlist=nodelist;dev=disc
NMMGR> 1istdir (RETURN)
NMMGR> : reset formlist (RETURNI

~ETURN)

The file is processed by the MAKESTREAM command as follows:
1. Only lines that begin with an alphabetic character in the first column are considered node name
entries; all other lines are deleted.

14-19

Network Directory
2. For those lines that qualify in the step above, the node name is delimited by the first blank
encountered. All information after the node name is ignored and stripped away.
3. Locally designated node names - - those names followed by a singIe spac.;e. t hell (L) - - are discarded.

4. Duplicate node names are deleted.
5. The logging information string "NOT UPDATED" is added to the list for each node name.
A sample processed file is shown below:

ANIMAL.FINANCE.IND
ASTRO.MARKETING.IND
CECIL.FINANCE.IND
RODAN.MARKETING.IND
SAKURA.MARKETING.IND
STANDALONE.MARKETING.IND
TIGGER.FINANCE.IND
VENUS.FINANCE.IND

NOT
NOT
NOT
NOT
NOT
NOT
NOT
NOT

UPDATED
UPDATED
UPDATED
UPDATED
UPDATED
UPDATED
UPDATED
UPDATED

These are the nodes shown in Figure 14-7, a two-network catenet. Let us assume that these nodes are
entries in the directory on ANIMAL. FINANCE. IND, which we have designated as the central administrative
node of NETl. Suppose we want to use the directory on ANIMAL to update only those nodes on the same
network, NET 1. We would need to edit nodefi le manually to remove the NET2 node names. We also
would remove the name ANIMAL because we are assuming its directory has been updated and we are using
it to update other directories. Meanwhile, the network manager of NET2 could perform a parallel
function to update only the NET2 nodes, using SAKURA as the central administrative node on NET2. (In
many cases, however, one central administrative node could be used to update all nodes in the catenet,
meaning that nodefile would not need to be edited.)
The parameter cndfile is the name of an NMMGR Maintenance Mode command file. This name also
must be qualified with group and account names to the extent that the job will require them. Below is an
example of a command file that could be used to merge the local directory file NSDI R. NET. SYS with
directory files of the same name on other nodes (listed in nodefile).

OPENDIR NSDIR.NET.SYS
:fILE SOURCE=NSDIR.NET.SYS:$BACK
MERGEDIR *SOURCE
EXIT
When using $BACK, the network directory on the remote nod.e must have the local node name configured.
Typical commands included in a command file are MERGEDIR, COPYCONF and DElETENODE. Any
command, however, may be used.
Once the job stream has been created using MAKESTREAM, it may be optionally customized, then executed.
You may change certain parameters in the job stream that are defaulted, like the remote logon string.
Another default is that progress messages are sent to OPERATOR. SYS. MAKESTREAM supplies a default
logon of NETADMIN. SYS t NET with no llser. group or account passwords. If you have very demanding
security needs, you can substitute a different logon for each node that will be updated. If defaults are
changed, the appropriate user/account capabilities are assumed to be in place. (For example, updating a
network directory requires NA capability; copying configuration file information requires NM capability;
both actions require BA and IA capability.

14-20

Network Directory
Each node listed in nodefile is logged onto with a REMOTE HELLO. Files local to the node on which the
stream job is run may be accessed remotely using RFA and file equations. The NMMGR Maintenance
Mode process is run on the remote side of the connection.
Each line entry in nodefile IS updated with the loggIng string "UPDATED" if all commands are executed
successfully. After the completion of the job stream, nodefile may be inspected for the results of all
updates. A sample, based on using ANIMAL in Figure 14-7 to update the other NETI nodes, is shown
below:

UPDATED
10/21/86 4:55 PM
UPDATED
10/21/86 5: 11 PM
NOT UPDATED 10/21/86 4:49 PM

CECIL.fINANCE.INO
TIGGER.FINANCE.IND
VENUS.FINANCE.INO

Any nodes that could not be updated are noted; the job stream should be consulted to determine the cause
of a failure. Once the problem has been corrected, the same job can be re-streamed. Only for those nodes
with the logging string "NOT UPDATED" will a logon and update be attempted. This process can be
repeated until all nodes have been satisfactorily updated.
The stream job can be re-created each time an update is desired, or the same job can be used after editing
the nodefile to reset the UPDATED strings to NOT UPDATED. For highly customized environments, the
latter will be easiest.

NET 2

NET 1
(Central

Admin.)

Standalone

Astro

Animal

Sakura

Venus

ngger

Rodan

Figure 14-7. Two-network Catenet

14-21

Network Directory

LISTDIR COMMAND SAMPLE OUTPUT
The following is a sample listing produced by the NMMGR Maintenance Mode Interface LISTDIR
command and the fRl~T;i:QJ.r key of the Network Directory Main Screen.
The top of the listing contains information that pertains to the directory as a whole, including its name.
when and where it was most recently updated, and the amount of space available.
Each entry in the directory is listed alphabetically with its local/global classification. For each entry, the
name. an indication if it is a local entry (l), and one to eight path reports are shown. For each path
report, the IP Address, network type, additional address and Transport Services (if applicable) are shown.

GLOBAL NETWORK DIRECTORY INFORMATION
01 rectory File:
Modification Date:
Modification Node:
Records Used:
Records Available:
Capacity:

NSDIR.NET.SYS
FRI, AUG 22, 1986, 12:32 PM
ERNIE.Del.INO
20
980
2% full

T C P

Node Name

IP Address

Net Type

Additional Addr

ERNIE.DCl.IHO

C 192.001.000 004

NONE

TIGGER.OCl.IND

C 203.154.017 006
C 198.001.000 007

IP/IEEE802.3
IP

14-2B-20-4E-C9-53
NONE

14-22

C H X
P K P

XX
XX

I...-W_OR_K_S_H_EE_T_S

This appendix contains worksheets necessary for configuration of nodes in your catenet. Do not fill out
these sheets. but make copies as needed. All necessary tables and required fields are included, as well as
blank sheets for all necessary maps.
References to tables and maps are generic in this appendix. For example, references are made to the
Router Network Map. If your catenet contains two router networks. you will have two router network
maps. but each map will include a unique network name.

A-I

'Wor~~ets.· .

CATENET:MAP

A-1

Worksheets

CATENET TABLE

NETWORK

NETWORK TYPE
(LAN, ROUTER)

IP NETWORK ADDRESS

IMPLEMENTATION
PRIORITY

A-3

Worltsheets

LAN NETWORK MAP

A-4

Worksheets

LAN NETWORK TABLE
NETWORK NAME:
IP NETWORK ADDRESS:

NODE NAME

IP NODE ADDRESS

PROXY SERVER
(V IN)

GATEWAY NODE
(V IN)

IMPLEMENTATION
PRIORITY

A-S

Worksheets

LAN INTERNET ROUTING TABLE
NETWORK NAME:
IP NETWORK ADDRESS:

THROUGH
GATEWAY NODE

A-6

IP NODE ADDRESS

DESTINATION
NETWORK/ADORESS

HOPS NEEDED TO REACH
DESTINATION NETWORK

Worksheeis
("':,

'r'J

ROUTER NETWORK MAP

Worksheets

ROUTER NETWORK TABLE
NETWORK NAME:
IP NETWORK ADDRESS:

NODE NAME

A-8

IP NODE ADDRESS

CENTRAL ADMIN.
NODE? (YIN)

&ATEWAY NODE

(YIN)

IMPLEMENTATION
PRIORITY

Worksheets

ROUTER INTERNET ROUTING TABLE
NETWORK NAME:
IP NETWORK ADDRESS:

THROUGH
GATEWAY NODE

IP NODE ADDRESS

DESTINATION
NETWORK/ADDRESS

HOPS NEEDED TO REACH
DESTINATION NETWORK

A-9

Worksheets
GATE~AY-HAlF

A-IO

MAP

Worksheets

GATEWAY-HALF NETWORK INTERFACE TABLE
NETWORK NAMES:

GATEWAY NODE

FULL IP ADDRESS
OF PARTNER

CONNECTED NETWORK

LINK NAME

A-II

Worksheets
After you choose to perform Guided ConfiguratlvD, you select the lII~mro.ij:i!"E;T;;:!tON. function key to
perform first-time configuration of a node )'ou then select an Nf"na'me"'and press the appropriate
topology function key. For NI names, use tht network names on the network maps. This way, you will
be able to keep track of the NI nam'~ you enteL You will then VIsit the Node Name Configuration
Screen, shown below. (This screen is always visited during loopbac.;k guided configuration, but is visited
for LAN, router, PC-router and gateway half guided confi~n rations only if a node name has not already
been configured.)
NOTE

References to figure numbers and page numbers pertaJn to Volume I.

NODE NAME CONFIGURATION (NETX PORT. NODE. NAME) Fig. 8- 3, p. 8- 5
Node Name

Name of the node you are configuring. Must be in the form node.domain.organization.

A-12

Worksheets

LAN NODE INTERNET ROUTING
NODE NAME:
IP ADDRESS:
NETWORK NAME:

GATEWAY NODE/IP ADDRESS

DESTINATION NETWORKS/
IP ADDRESSES

HOP COUNT

A-13

Worksheets

LAN CONFIGURATION SCREENS

LINK CONFIGURATION (LINKCONF) Fig. 7-1, p. 7-4
Link Name

Assign a link name that is eight alphanumeric chclracters or fewel, the first character must be alphabetic.
LAN802.3 LINK DATA (LINKCONF .linkname) Fig. 7-2, p. 7-6
Logical Device

.._ .

The Idev number of the LANIC that will be configured in SYSDUMP.
PROBE PROTOCOL CONFIGURATION (NETXPORT. NI niName. PROTOCOL. PROBE) Fig. 9-4, p. 9-10
Proxy Enabled

Answer Y if this node will be a proxy server (will have a network directory). Refer to LAN Network
Map.
IP PROTOCOL CONFIGURATION (NETXPORT. NI .niName. PROTOCOL. IP) Fig. 9-3, p. 9-7
IP Address

Full IP address of the node being configured. Refer to LAN Network Table.

A-14

Worksheets
LAN CONFIGURATION SCREENS (cont'd)

Note: This page contains information for one gateway. Before you proceed, make copies of this page for
additional gateways. During Guided Configuration, press the N"it;]lj;l~~jjlliP. function key when finished
configuring information for a gateway. This returns you to the fint screen shown on this page. If you
are finished for all gateways, press the ~~~~~d;~~!~~o. key again.
NEIGHBOR GATEWAYS (NETXPORT. HI .niName. INTERNET) Fig. 9-7, p. 9-18
Gateway Name

Assign a name (maximum eight characters) to reference a gateway that is
node belongs. Refer to Catenet Map and LAN Network Map.

the network to which the

NEIGHBOR GATEWAY REACHABLE NETWORKS (N ETX PORT .NI .niName. INTERNET.gatewayn)
Fig. 9-8, p. 9-19
Neighbor Gateway IP Internet Address

Full IP address of the gateway node. Refer to LAN Network Table.
IP Network Address

('.

J!l

-------------------~

-------------------~
-------------------~
The IP addresses of all reachable networks in the catenet, through the gateway node Damed above. Ilefer
to LAN Node Internet Routing Table. You need to fill out a node portion for each IP Network Address.
even though the node portion is ignored. You can simply enter zeros for these node portions.
Hops

-------------------~
-------------------~
-------------------~

-------------------~
Refer to LAN Node Internet Routing Table for Hop Count. The numbers in parentheses correspond to
the numbers regarding IP network addresses.

A-IS

Worksheets

SUBSEQUENT LAN NODES

If you are adding a LAN node, be sure to complete this information and
update the corresponding maps and tables.

Link Name

-------------------__

Logical Device
Proxy Enabled?

IP Address of the node being configured

Gateway Names 1) _ _ _ _ _ _ 2) _ _ _ _ _ _ 3)
Neighbor Gateway IP Internet Addresses
1)

2) _ _ _ _ _ _ _ 3)

for first gateway:
IP Network Address

Hops

IP Network Address

Hops

IP Network Address

Hops

IP Network Address

Hops

Be sure to add IP network addresses and hops for other specified gateways.

A-16

Wortsheetl

ROUTER NODE INTRANET ROUTING TABLE
NODE NAME:
IP ADDRESS:
NETWORK NAME:

DESTINATION NODE

LINK NAME

DESTINATION NODE'S
IP ADDRESS

ENTRY
PRIORITY

A-I?

Worksheets

ROUTER NODE INTERNET ROUTING

NODE NAME:
IP ADDRESS:
NETWORK NAME:

GATEWAY NODE/IP ADDRESS

A-18

DESTINATION NETWORKS/
IP ADDRESSES

HOP COUNT

Worksheets

ROUTER CONFIGURATION SCREENS

LINK CONFIGURATION (LINKCONf) Fig. 7-1, p. 7-4
Link Name __.

Assign a link name that is eight characters or fewer. The first character must be alphabetic. This link
name corresponds to one link the node has configured. After you have been taken to all the necessary
screens for this link, Guided Configuration will bring you back to this screen to configure any other links
for this node. The fields on this page and the first field on the next page may need to be copied so that
you can fill out the appropriate information for other links. Refer to Router Network Map. When you
are finished configuring the links for this node, press the ~e~~~~~~~ function key.
Circle one.
ASNP LINK DATA (LINKCONF .linkname) Fig. 7-12, p. 7-27
Logical Device

The ldev number that will be configured in SYSDUMP.
OR

LAP-B LINK DATA (LINKCONF .linkname) Fig. 7-9, p. 7-19
Logical device

The Idev number that will be configured in SYSDUMP.
Local Mode (SmDTE, 6=DCE, lla:HP Point to Point)

HP recommends that you use the default. HP Point to Point. If so, both sides of the link must be
configured as HP Point to Point.
OR

BISYNC LINK DATA (LINKCONF .linkname) Fig. 1-6, p. 1-11
Logical Device

The Idev number that will be configured in SYSDUMP

A-19

Worksheets
ROUTER CONFIGURATION SCREENS (cont'd)

NETWORK INTERFACE LINKS (NETXPORT .NI .niName. LINK) Fig. 10-6, p. 10-17
Type

DD--Direct Dial, DC--Direct Connect. or SD--Shared Dial
DIRECT CONNECT LINK CONFIGURATION lNETXPORT .NI .niName. LINK.linkname) Fig. 10-7, p.
10-19
No fields required to configure.
OR
ROUTER DIAL LINK CONFIGURATION
10-21

(NETXPORT.NI.niName.LINK.linkname) Fig. 10-8, p.

No fields required to configure.
ROUTER NETWORK INTERFACE CONFIGURATION (NETXPORT.NI .niName) Fig. 10-1, p. 10-3
Network Hop Count

The greatest possible number of intermediate nodes between the two nodes farthest apart on the network.
See Router Network Map.
Idle Device Timeout Value (Minutes)

For dial links, this is the number of minutes a device can remain idle (no traffic) before shutting down. A
value of zero will disable the idle device timer for all devices on this network interface. (Enter 0 for
Direct Connect links.)
IP PROTOCOL CONFIGURATION (NETXPORT. NI .niName. PROTOCOL. IP) Fig. 10-3, p. 10-8
IP Address

FulllP address of the node being configured. Refer to Router Network Table.

A-20

Worksheets
ROUTER CONFIGURATION SCREENS (cont'd)

Note: Mapping configuration is required for each local link the node can use to reach each remote node
on the router network. Therefore, make enough copies of this sheet before you fill in any information.
After configuring mapping information for one node, Guided Configuration will bring you back to the
first screen on this page. Repeat the process until you have completed all mapping configuration, then
press the ~'~~·::Sc~r:4!e6 function key.

MAPPING CONFIGURATION (NETXPORT.NI .niName.MAPPING) Fig. 10-12, p. 10-30
Router Node Name

Assign a name (maximum eight characters) to represent a node you wish to be able to reach from your
'lode. Refer to Router Node Intranet Routing Table.
ROUTER REACHABLE NODES (NETXPORT. NI .niName.MAPPING.mpentry) Fig. 10-13, p. 10-32
IP Internet Address

FulllP address of the destination node named above. Refer to Router Node Intranet Routing Table.
Link Name

Name of the link used to reach the destination node. Must match a link name that you configured on the
link configuration screen. If more than one link is required to reach the destination node, list only the
first link to be used.
Adjacent (0)/ Non-adjacent (1)

If the destination node is not directly connected to the link just named, enter 1. Otherwise, enter 0.
Refer to Router Network Map.
Entry Priority

Used when alternate local links are configured to reach a remote node. Refer to the Router Node
Intranet Routing Table. If no alternate links will be configured, use the default of SO for the priority so
that you allow for possible additions with higher or lower priority numbers.
Phone Number

The phone number of the destination node is required if the destination node is directly connected to the
other end of the link and if the link is a direct dial or a shared dial link.

A-21

Worksheets
ROUTER CONFIGURATION SCREENS (cont'd)

Note: This page contains information for one gateway. Before you proceed, make copies of this page for
additional gateways. During Guided Configuration, press the _~~~:im$.~:~.~~ function key when finished
configuring information for a gateway. This returns you to the first screen shown on this page. If you
are finished for all gateways, press the ~~~~:m~$~:r~e.~ key again.
NEIGHBOR GATEWAYS (NETXPORT. NI .niName. INTERNET) Fig. 10-9, p. 10-24
Gateway Name

Assign a name (maximum eight characters) to reference a gateway that is on the network to which the
node belongs. Refer to Catenet Map and Router Network Map.
NEIGHBOR GATEWAY REACHABLE NETWORKS (NETXPORT.NI.niName.INTERNET.gatelAklyn)
Fig. 10-10, p. 10-25
Neighbor Gateway IP Internet Address

Full IP address of the gateway node. Refer to Router Network Table.
IP Network Address

-------------------~

-------------------~
-------------------~
-------------------~
The IP addresses of all reachable networks in the catenet, through the gateway nocie named above. Refer
to Router Node Internet Routing Table. You need to fill out a node portion for each IP Network Address,
even though the node portion is ignored. You can simply enter zeros for these node portions.
Hops

---------------------~
-------------------~
-------------------~

-------------------~
Refer to Router Node Internet Routing Table for Hop Count. The numben in parentheses correspond to
the numbers regarding IP network addresses.

A-22

Worksheets

SUBSEQUENT ROUTER NODES

If you are adding a router node, be sure to complete this
information and update the corresponding maps and tables.
Link Name

-------------------

Type = ASNP, LAP-B or BSC

Logical Device

Circle one.

----------------------------------------

OTE/OCE for LAP-B

Is link Direct Dial, Direct Connect, or Shared Dial?
(Must repeat all of above information for all links belonging to the node.)
Network Hop Count
Idle Device Timeout Value
IP Address of the node being configured

Router Node Name
(This name is for--~-~~--~--~~--~-----mapping information to follow; the name represents a
destination node on the network.)
IP Internet Address of the destination node

-----------

Link name used to reach the destination node

-----------

Adjacent (0)/ Non-adjacent (1)
Entry Priorty
Phone Number

-----------

From Router Node Name, above, to this point, information must be repeated for
all mappings to be configured.
See next page for additional router fields.

A-23

Worksheets

SUBSEQUENT ROUTER NODES (cont'd)

Gateway Names 1)

------- 2) -------- 3)

Neighbor Gateway IP Internet Addresses
1)

2) _ _ _ _ _ _ _ _ 3)

For first gateway:
IP Network Address _ _ _ _ _ _ _ _ _ _ _ Hops

IP Network Address _ _ _ _ _ _ _ _ _ _ _ Hops

Be sure to add IP network addresses and hops for other specified gateways.

A-24

Worksheets

NODE WORKSHEET

GATEWAY-HALf NODE INTERNET ROUTING TABLE
NAME Of GATEWAY-HALf NODE:
IP ADDRESS:
NETWORK NAME:

CONNECTED GATEWAY-HALf NODE/
IP ADDRESS

GATEWAY-HALf
LINK NAME

DESTINATION
NETWORKSI
IP ADDRESSES

HOP
COUNT

A-25

Worksheets
GATEWAY-HALF CONFIGURATION SCREENS

GLOBAL TRANSPORT CONFIGURATION (NETXPORT •GLOBAL) Fig. 8-4, p. 8-7
Home Network Name

Enter the name of a network the node belongs to; the node must have a corresponding LAN or Router NI
name configured. Refer to the appropriate maps. If the node belongs to more than one network, the
home network should be the one that will allow the greatest number of destination networks a short
return path to the node.
LINK CONFIGURATION (LINKCONf) Fig. 7-1, p. 7-4
Link Name

Assign a link name that is eight alphanumeric characters or fewer; the first character must be alphabetic.
Refer to Gateway-Half Map.
Type: ASNls. LAP-JL...BSC

Circle one.

ASNP LINK DATA (LINKCONF .linkname) Fig. 7-12, p. 7-27
Logical Device

The Idev number that will be configured in SYSDUMP.

OR
LAP-B LINK DATA (LINKCONF .linkname) Fig. 7-9, p. 7-19
Logical Device

The Idev number that will be configured in SYSDUMP.
Local Mode (SaDTE, 6aDCE, 11 HP Point to Point)
g

HP recommends that you use the default, HP Point to Point. If so, both sides of the link must be
configured as HP Point to Point.
OR

BISYNC LINK DATA (LINKCONF .linkname) Fig. 7-6, p. 7-11
Logical Device

The Idev number that will be configured in SYSDUMP.

A-26

Worksheets

G ATEWAY-HALF CONFIGURATION SCREENS (cont'd)

NETWORK INTERFACE LINKS (NETXPORT •NI • niName. LI NK) Fig. 11-6, p. 11-16

Type

DD--Direct Dial, or DC--Direct Connect
GATEWAY-HALF DIAL LINK CONFIGURATION (NETXPORT.NI.niNams.LINK.linkname) Fil.
II - 8, p. 11- 19

Gateway Phone

The phone number of the remote gateway-half node
security String

Security String of the remote gateway-half node.

OR
DIRECT CONNECT CONFIGURATION (NETXPORT. NI .niName. LINK.linkname) Fig. 11-7. p. 11-17

No fields required to configure.
GATEWAY-HALF NETWORK INTERFACE CONFIGURATION (N ETX PORT .NI .niName) Fig. II-I. p.

11-3
Idle Device Timeout Value (Minutes)

For diallink~ this is the number of minutes a device can remain idle (no traffic) before shutting down. A
value of zero will disable the idle device timer for all devices on this network interface. (Enter 0 for
Direct Connect links.)
IP PROTOCOL CONFIGURATION (NETXPORT .NI .niName. PROTOCOL. IP) Fig. 11-3. p. 11-7

IP Address

Fun IP address of the partner gateway-half node (the node connected to the gateway half beinl
configured). Refer to Gateway-Half Network Interface Table.

A-27

Worksheets
GATEWAY-HALF CONFIGURATION SCREENS (cont'd)

NEIGHBOR GATEWAYS (NETXPORT .NI .niName. INTERNET) Fig. 11-9. p. 11-23
Gateway Name

:.-_ .

Assign a name (maximum eight characters) to reference a gateway half that. IS connected to the node by
the gateway-half link previously named. Refer to Catenet Map and Gateway-Half Map.
NEIGHBOR GATEWAY REACHABLE NETWORKS (NETXPORT.NI.niName.INTERNET.gatelltrf/n)
Fig. 11-10, p. 11- 24
Neighbor Gateway IP Internet Address

Full IP address of the gateway node named above. Refer to Gateway-Half Network Interface Table.
This address will match the address configured in the IP Address field listed above.
IP Network Address

____________________ill

____________________m
____________________m
---------------------~

The IP addresses of all reachable networks in the catenet, through the gateway node named above. Refer
to Gateway-Half Node Internet Routing Table. You need to fill out a node portion for each IP Network
Address, even though the node portion is ignored. You can simply enter zeros for these node portions.
Hops

_____________________ill

____________________m
m
--------------------~
Refer to Gateway Half Node Internet Routing Table for Hop Count.
correspond to the numbers regarding IP network addresses.

A-2S

The numbers in parenthesea

Worksheets

SUBSEQUENT GATEWAY-HALF NODES

Home Network Name
Link Name
Type

----------------------------------

= ASNP.

LAP-B or BSC

Circle one.

Logical Device

OTE/DeE for LAP-B

Is link Direct Dial or Direct Connect

-------------__

If Dial. phone number of remote gateway-half node

If Dial. security string of remote gateway-half node
Idle Device Timeout Value

-----------------

IP Address of partner gateway half

Gateway name

Neighbor Gateway IP Internet Address

IP Network Address _______________ Hops

IP Network Address _ _ _ _ _ _ _ _ _ _ Hops

IP Network Address _________________ Hops

A-29

Worksheets
NETWORK DIRECTORY INFORMATION

After reading the Network Directory section (Section 14). yo" can complete the information below for all
nodes you wish to manually configure into your network directory file.
"Type: !=IP, 2a IP/LAN802. 3

Node
Name

A-30

Global or
Local

IP Address

Type*

Additional
Addres8

___S_U_P_P_OR_T_E_D_M_O_D_EM_S

The following modems are supported for NS Point-to-Point 3000/V links:

Line speed (bits/sec)

Modem

4800

AT&T 2248A

LAP-B

4800

AT&T Dataphone 4800
or AT&T 208B-compatible
modems

SSC

9600

CODEX 2640

LAP-B

56000

GTE L500A DSU

LAP-B

Link Protocol

AT&T 2248A is the only modem supported for use with LAP-B over full-duplex dial links. Autodial
capability is supported by the Bell 80 I C Auto Call Unit.
The following modems are supported for Asynchronous SERIAL Network links, which use the ASHP
protocol:

Line speed

Modem

1200

Hayes 1200 (HP 92005A) or any other 1200
baud modem that is ATP-compatlble

2400

Hayes 2400 (HP 920058)

2400

u.s.

1200

HP Remote Support link modem (HP 3712A)

Robotics Courier 2400

Autodial capability is supported by the Hayes and U. S. Robotics modems. To use autoclial, Hayes 1200
baud modems and U.s. Robotics Courier 2400 modems must use the switch settings shown in Fiaure 8-1;
the Hayes 2400 baud modem must receive the commands shown in Figure 8-2.
For modem settings for manual dial links, refer to the documentation provided with your modem.

8-1

Supported Modems

HAYES SMARTMODEM 1200/U.S. ROBOTICS COURIER

2400 for Asynchronous SERIAL Network Unk
Switch

Setting

Meaning

Switch 1

Switch 2

DOWN

Digit result codes

Switch 3

DOWN

Result codes displayed

Switch 4

DOWN

No echo unless half-duplex is selected
and modem is on-line

Switch 5

DOWN

Modem will not auto answer a call

Switch 6

Reads status of the RS-232C Carrier
Detect lead (Carrier Detection enabled)

Switch 7

Setting for single line telephone installations
connected to an RJ 11 jack

Switch 8

DOWN

Switch 9

UP or DOWN

Switch 10

UP or DOWN

Supports RS-232C OTR lead

Enables modem command recognition

Figure 8-1. Autodial Switch Settings, Hayes lZOO/U.S. Robotics Z400

B-2

Supported Modems

HAYES SMARTMODEM 2400 for

Asynchronous SERIAL Network Unk

Command

r'.

Meaning

AT&F

Set to factory setting

AT&C1

Reads status of carrier

AT&D3

Support DTR Lead

ATV

Digit result codes

ATEO

Disable echo

AT&W

Write active to nonvolatile memory

Figure B-Z,. Autodial Commands, Hayes 1400

r
B-3

.~
,---"

I~
,

....

_C_O_N_V_E_R_T_IN_G_C_O_N_F_IG_U_R_A._T_IO_N_FI_L_ES_---,I~
NMMGRVER. PUB. SYS is a conversion program that enables earlier versions of subsystems to be used with
the current version of NMS.
You need to convert files if you open an
message:

eXlstin~

configuration file while using NMMGR and receive this

Version mismatch found on specified subsystem.

Please run NMMGRVER.
(NMGRERR 53)

Also, you need to convert files if you are performing NETCONTROL and recieve the following class 2
logging message at the console:
Bad CONFIG File Version

USING THE CONVERSION PROGRAM
To use this, do the following:
1. Make a backup copy of the existing configuration files
before proceeding.

2. Execute NMMGRVER. PUB. SYS by entering:
:RUN NMMGRVER.PUB.SYS

NMS Configuration File Conversion Utility 32099-11018 A.02.00
(C) Hewlett-Packard Co. 1985
3. Respond to the dialogue:
Fl1eset to be scanned?
by either pressing the (RETuRNI key, which ends the conversion program, or by
entering one of the following filesets:

filename [.groupname [.acctname]]
file prefi%' [.groupname [.acctnamell
(I

(.groupname [.acctname]]

,.,.,

,., [.acetname 1

C-l

Converting Configuration Files
NMMGRVER searches for files of type NCONf in the specified flleset

For each file found, it asks:

OK to convert filename.groupname.acctname?
Enter either Y for yes or Nfor no.
Pressing the

(RETURN)

key is the same as entering Nfor no.

4. Continue to enter either Y, N, or lREfURN) until you have converted all files.
S. Use NMMGR CA. 02. 00) for configuration. if needed.

C-2

~P_C_-_T_O_-_H_P_3_0_00_C_O_M_M_U_NI_C_A_T_IO_N_ _I~
This appendix summarizes the tasks required for connecting personal computers (PCs) to UP 30009 over
ThinLAN/3000, StarLAN/3000 and Asynchronous SERIAL networking links. Connecting PCs and HP
30008 over these links enables PC users to take advantage of Hewlett-Packard software products that
make resources and programs operating on the HP 3000 available to PCs. For full details about the HP
3000 tasks that this appendix summarizes) read and follow the instructions given earlier in this manual.
NOTE

This appendix discusses the tasks required for the configuration of an UP
3000 connected to a PC workstation over a ThinLAN/3000.
StarLAN/3000 or Asynchronous SERIAL Network Link. For workstation
configuration tasks, refer to eIther the H P ThinLAN Workstation
Installation and Configuration Guide lor PCs (part no. 50909-90040). the
HP StarLAN PC Workstation Installation and Configuration Guide (part no.
50906-90040), or the HP SERIAL Network Workstation Installation and
Configuration Guide (part no. 50911-90040). For PC server configuration
tasks, refer to either the HP ThinLAN PC Server Installation. Con/lguration.
and Operation Guide (part no. 50907-90000) or the HP StarLAN PC
Server Installation, Configuration and Operation Guide (part no.
50904-90000).
The procedures summarized in this appendix will normally be completed by the individual responsible for
managing the networking capabilities of the UP 300Q--usually the UP 3000 network manager or UP
3000 system manager. The actual titles and responsibilities of people at your installation may differ from
those used here.
Your UP systems engineer may already have completed some or all of these procedures for your network
instanation. Consult your systems engineer to determine which tasks, if any, already have been
completed.

D-I

PC-To-HP 3000 Communication

REQUIREMENTS FOR THINLAN/3000, STARLAN/3000, SERIAL LINKS

Software Required
Resource Sharing and virtual terminal access reqtJlre several Hewlett-Packard software packages. The
following lists indicate the software required for different uses of PCs and HP 30005.

UP 3000

server

Software

An HP 3000 is used as a server with Resource Sharing to provide shared discs, shared printers, and an HP
3000 backup facility. The following software is required for the UP 3000:
• Expanded System Table Microcode (except for the Series 37)
• MPE VIE (UB-Delta-l MIT) operating System or later versit''' for ThinLAN; UB-Delta-l MIT
or later for StarLAN.
• NS3000/V Network Services or the services software included with either ThinLAN/3000 Link
or StarLAN/3000 Link.
• Productivity Services/3000 Resource Sharing

UP 3000 Host Software
An HP 3000 is used as a host over ThinLAN/3000 Link, StarLAN/3000 Link or Asynchronous SERIAL
Network Link for products such as Information Access and AdvanceMail. The following software is
required on the UP 3000 when operating as a host over these links:
• Expanded System Table Microcode (except for the Series 37)
• MPE VIE (UB-Delta-l MIT) Operating System or later version for ThinLAN and StarLAN
(Note: If AdvanceLink is the only host-to-PC product in use, the U-MIT version of MPE VIE is
acceptable.) For SERIAL, UB-Delta-3 MIT or later 18 needed.
• NS3000/V Network Services or the services software included with either ThinLAN/3000 Link,
StarLAN/3000 Link, or Asynchronous SERIAL Network Link.

Software for a PC Workstatlon Using Server Resources
A PC used as a workstation on the network can use the network to perform certain tasks. The following
software is required for the PC if it is using a PC server's or HP 3000 server's shared resources:

D-2

PC-To-HP 3000 Communication

For ThinLAN
• Version 3. 1 or later (Version 3. 2 recommended) of the DOS operating system and utilities
• Version A. 03. 00 or later of the HP ThinLAN User Link Software for Vectra/IBM Pes or Version
A. 03. 00 or later of the HP ThinLAN User Link Software for Touchscreen PCS
For StarLAN

• Version 3.1 or later (Version 3.2 recommended) of the DOS operating system and utilities, and
• Version A. 01. 00 or later of the HP StarLAN User Link Software for Vectra/IBM Pes

For SERIAL
• Version 3.1 or 3.2 of the DOS operating system and utilities.
• Version A. 01. 00 or later of the HP SERIAL Network User Link Software for Vectra/IBM PCa or
Version A. 03. 00 or later of the HP SERIAL Network User Link Software for Touchscreen PCs

Software for a PC Workstation Used as a Terminal
A PC workstation can use AdvanceLink to communicate with an HP 3000 host computer as though the
workstation were a terminal connected to the HP 3000 by RS-232 cable. When used as a terminal, the
following software is required for the PC:
For ThinLAN
• Version 3.1 or later (Version 3.2 recommended) of the DOS operating system and utilities
• Version A. 03. 00 or later of the HP ThinLAN User Link Software for Vectra/IBM PCs or
Version A. 03.00 or later of the HP ThinLAN User Link Software for Touchscreen PCa
• Version A. 03. 02 or later of the HP AdvanceLink (for HP Touchscreen Pes) or HP AdvanceLink
2392 (for HP Vectra PCS and IBM PC/XT/ATs).
For StarLAN
• Version 3.1 or later (Version 3.2 recommended) of the DOS operating system and utilities
• Version A.Ol.OO or later of the HP StarLAN User Link Software for Vectra/IBM PCs
• HP AdvanceLink 2392 (for HP Vectra PCs and IBM PC/XT/ ATs).

D-3

PC-To-HP 3000 Communication
For SERIAL

• Version 3. 1 or 3.2 of the DOS operating system and utilities.
• Version A. 0 I. 00 or later of the HP SERIAL Network User Link Software for Vectra/IBM PCs or
Version A. 03.00 or later of the HP SERIAL Network User Link Software for Touchscreen Pcs.
• Version A. 03. 02 or later of the HP AdvanceLink (for HP Touchscreen PCs) or HP AdvanceLink
2392 (for HP Vectra PCs and IBM PC/XT/ ATs).

NOTE
A PC being used as both a terminal and as a workstation sharing a server's

resources requires the software listed under "For a PC Workstation Used as
a Terminal." One copy of DOS and utilities and either HP ThinLAN User
Link Software, HP StarLAN User Link Software, or HP SERIAL Network
User Link Software is needed for each workstation.

Related Publications
You should refer to the following Hewlett-Packard documentation when configuring a PC workstation or
HP 3000:
HP ThinLAN for pes

• HP ThinLAN Workstation Installation and Configuration Guide for PCs (part no. 50909-90040)
• HP ThinLAN Planning and Hardware Guide for PCs (part no. 50909-90020)

HP StarLAN for PCS
• HP StarLAN PC Workstation Installation and Configuration Guide (part no. 50906-90040)
• HP StarLAN Planning Guide for PCs (part no. 50906-90020)
• HP StarLAN Hardware Installation Manual for PCs (part no. 5959-2222)

HP SERIAL Network
• HP SERIAL Planning and Hardware Guide (part no. 50911-90020)
• HP SERIAL Network Workstation Installation and Configuration Guide (part no. 50911-90040)
• HP StarLAN Quick Reference (part no. 5959-2227)
• Quick Task Reference Card (part no. 5959-1504)

D-4

PC-To-HP 3000 Communication
Resource Sharing

• Resource Sharing: System Management (part no. 32597-90001)
• Resource Sharing: Utilities (part no. 32597-90002)

NS3000ty Links
• NS3000/V Network Manager Reference Manual (part no. 32344-90002)

Other HP manuals describe additional products that use the UP 3000 as a host. Consult your HP
representative for information on additional products and the publications that describe them.
NOTE

Although this appendix outlines required PC configuration tasks, the tasks
are described in detail in only the manuals listed above for HP ThinLAN
for PCs, HP StarLAN for PCs and HP SERIAL networks. The SPecific
manual or sections of this manual to which you should refer for more
information about a particular task are noted throughout this appendiL

Hardware and Software Installation
Before you can attempt the procedures summarized in this appendix, the installation of certain hardware
and software already must be completed on either each PC workstation being configured or on the UP
3000. Before you begin the procedures summarized on the following pag~ make sure that:
For UP 30005

• A hardware card (LANIC for IEEE802.3 networks, ATP for SERIAL networks) is properly
installed in the backplane of the UP 3000
• Resource Sharing is installed on the HP 3000, if Resource Sharing will be used
• (For Resource Sharing only) Public shared discs and shared printers, if applicable, have been set up
on the HP 3000 with the RESMGR utility
• Modems for remote UP SERIAL Network Links have been set up.

D-S

PC-To-HP 3000 Communication
For PC Workstations

• The network is planned as described in the HP ThinLAN Planning and Hardware Guide for PCs,
the HP StarLAN Planning Guide for PCs or the HP SERIAL Planning and Hardware Guide, and a
"User Reference Worksheet" has been filled out for each workstation.
• The required network hardware is set up, as described in the HP ThinLAN Planning and
Hardware Guide for PCs, the HP StarLAN Hardware Installation Manual for pes, or the HP
SERIAL Planning and Hardware Guide.

• Each workstation's software is installed, either on work discs or on a fixed disc, as described in the
HP ThinLAN Workstation Installation and Configuration Guide for PCs, the HP StarLAN PC
Workstation Installation and Configuration Guide, or the HP SERIAL Network Workstation
Installation and Configuration Guide.

If PC servers are also being used as part of the network, they should also be configured before the tasks
described in this appendix are begun. For more information on configuring PC servers, refer to either the
HP ThinLAN PC Server Installation. Configuration. and Operation Guide or the HP StarLAN PC Server
InstaUation. Configuration. and Operation Guide.

UP 3000 Logon and Sltortname Correspondence
The PC network manager and HP 3000 system manager should agree upon UP 3000 account pathnames
(user logons, groups, accounts, and access permissions) and corresponding shortnames before the tasks
summarized in the following pages are begun.

D-6

)

PC-To-HP 3000 Communication

CONFIGURATION PROCEDURES SUMMARY
The following sections summarize the tasks that must be completed to configure PC workstations and HP
30005 in order to use the UP 3000 as a server to PC workstations (via Resource Sharing), to use UP
AdvanceLink, and for other software products that use the HP 3000 as a host.
The configuration tasks can be divided as shown in the table below and as described in the following
sections.

Task
Configuring the PC
workstation with the
USRCONFG utility and
loading PC workstation
network software

Done By

PC network manager

Reference
For ThinLAN-- HP
ThinLAN Workstation
Installation and Configuration
Guide for PCs
For StarLAN-- HP StarLAN
PC Workstation Installation
and ~onfigurat;on Guide
For SERIAL-- HP SERIAL
Network Workstation
Installation and Configuration
Guide

Configuring the HP 3000

UP 3000 network manager

Sections 5-14 of this manual
Resource Sharing: System
Management (for Resource

Sharing only)
Assigning HP 3000 Logons

UP 3000 system manager

System Operation and
Resource Management
Reference Manual

PC Workstation Tasks
After the HP 3000 has been configured, configure the PC workstation and load PC workstation network
8Ofiware. Refer to the manuals listed above.

D-7

PC-To-HP 3000 Communication

Configuring the HP 3000
(UP 3000 network manager)
Two utilities are used to configure the UP 3000: SYSDUMP and NMMGR. SYSDUMP is used to
configure the hardware card that has been installed in the backplane of the UP 3000.
NOTE

A hardware card must be installed on the HP 3000 before any further
configuration tasks can be performed. Consult your UP 3000 network
manager or HP Systems Engineer for more information.

Refer to Section 4 of this volume for instructions on configuring the hardware card with SYSDUMP.
Once the hardware card has been installed, configuring the HP 3000 to support Resource Sharing,
AdvanceLink, or other products that use the HP 3000 as a host consists of two main tasks:
• Configuring additional virtual terminals (VTERMs) with the SYSDUMP utility
• Configuring the HP 3000 as part of an NS3000/V network with the NMMGR utility. (Note:
this appendix assumes that the HP 3000 has not been previously configured as a node on an
NS3000/V network. If the UP 3000 has been configured already, some configuration changes
may be required. These are noted later in this appendix.)

Configuring Additional Virtual Tennlnals
To configure additional virtual terminal (VTERM) devices, you must run the HP 3000 SYSDUMP utility.
The following paragraphs explain how to determine the number of additional VTERMs needed:
At least one additional VTERH is required for each PC workstation. This includes PCB that are
using the UP 3000 as a server, as a host for various application software, and for PCs using
AdvanceLink for terminal access to the HP 3000.
You may choose to configure more VTERMs than will be currently required by your network
installation so that if PC workstations are later added to the network, you will not always have to
reconfigure the number of VTERMs. UP suggests that to allow for your network's future growth,
you use a formula such as the following to determine the number of additional VTERMs to
configure:
1. Calculate a value based on the number of PCs using the UP 3000 as a server: For the first
PC using the UP 3000 as a server, the number of virtual terminals required is 6. Each
additional PC using the HP 3000 as a server (via Resource Sharing) requires 1.5 additional
VTERMs.

D-8

PC-To-HP 3000 Communication
2. Calculate a value based on the number of PCs uSing AdvanceLink or other software using
the HP 3000 as a host: For each PC using AdvanceLink or other software using the UP 3000
as a host, the number of virtual terminals required is 1.
3. Add the values determined in steps 1 and 2, and round up to the next highest whole number
i( necessary.
For example, if four PC workstations will be using Resource Sharing and two of those will be
using AdvanceLink, and a fifth PC will be using only AdvanceLink, you would configure:

4 PCs using Resource Sharing:

6 + 1.5 + 1.5+ 1.5

3 PCs (total) using AdvanceLink:

1 + 1 + 1

Total:

= 10.5
= 3.0
13.5

Rounded up

= 14

VTERMs

Refer to Section 4 for information on running SYSDUMP for network configuration.

Configuring the UP 3000 Network Configuration File (NSCONF.NET.SYS)
This subsection describes the minimum tasks that must be performed to configure an HP 3000 as a node
on an NS3000/V IEEE802.3 network or an NS3000/V Asynchronous SERIAL network. For details,
refer to sections 5-10, 13 and 14.
Consult your UP 3000 network manager or your UP systems engineer before attempting the tasks
described here.
NMMGR is a screen-based utility. This means that as you press function keys or type in commands, a
series of display screens appear at your terminal. Various fields displayed within each screen correspond
to configurable items; configuration occurs when values are typed into the fields and recorded.
The following tables contain two types of fields in the Item column. One type is a field that must be
user-configured as part of a minimum network configuration. These are items for which no default
value is supplied. Guided Configuration visits all screens that include such items. The other type is a
field that has a default value but may need to be changed depending on the size of the network. The
tables include the type of the item in the Requirement Status column. The screen on which an item
appears is listed in the Screen column.
To reach screens not visited by guided configuration, you need to use manual configuration. See Section 5
for details.

0-9

PC-To-HP 3000 Communication
NOTE

If your HP 3000 is already part of an NS3000/V network, you may have to
alter some fields in the following tables, but you will not need to configure
the HP 3000 node name, IP address, or LDEV number, as they will have
been configured already.
Internet screens and LAN mapping screens are not shown in the table
because they are not necessary for this discussion of PC-to-UP 3000
communication. However, when configuring the UP 3000 as part of
a LAN, mapping must be configured about any nodes on the LAN that do
not support the Probe Protocol (e.g. non-UP 3000 nodes). Internet routing
screens, no matter what network type, must be visited if you want the UP
3000 to be able to communicate with other networks that are part of the
same catenet. See sections 9 and 10 for more information.
Also, the Probe Protocol screen is not included in the LAN table. This
screen, described in detail in Section 9, is used when you want to configure
an HP 3000 as a proxy server containing directory information about all
nodes in the catenet.
The term "node name" in this appendix has the same meaning as "computer
name" in HP networking PC manuals.

D-IO

PC-To-HP 3000 Communication

For ThinLAN and StarLAN Networks

Item

Screen

Requirement Status

GUIDED NETWORK
INTERFACE
CONFIGURAnON

Network interface name.

Required.

NODE NAME
CONFIGURAnON

HP 3000 node name.

Required. Keep track of this
node name, including its
dOtmin and organizat ion
fields, because you will need it
during configuration of a PC
workstation with the
USRCONFG utility.

LINK CONFIGURATION

Link Name.

Required.

LINK CONFIGURATION:
IEEE 802.3 LINK DATA

ILANIC card's LDEV number.

Required.

IP PROTOCOL
CONFIGURAnON

HP 3000 IP address.

Required.

D-l1

PC-To-HP 3000 Communication
For ThinLAN and StarLAN Networks (continued)

-""':j
Screen

D-12

_---_.

Item

Requirement Status

GLOBAL TRANSPORT
CONFIGURATION

Maximum directly connected
nodes and maximum inbound
destinations. (Values for
these fields should be streater
than or equal to the number
of nodes, InCI uding PC
workstations and PC servers,
in the network.)

Use the default unless number
of network nodes (including
PC workstations and serven)
exceeds 100.

TRANSMISSION CONTROL
PROTOCOL (TCP)
CONFIGURATION

Maximum number of
connections.

Use the default unless
maximum number of
connections in use at one time
will exceed 128 (the default).
This value should allow for
two connections for each
concurrent usage of Resource
Sharing and one connection
for each concurrent usage of
other network applications
and services.

LAN802.3 NETWORK
INTERFACE
CONFIGURATION

Maximum number of nodes in
network (to include all PC
workstations and servers).

Use the default unless number
of nodes in network exceeds
100 (the default).

Number of outbound buffers.

Use the default unless
maximum number of
connections configured in
TRANSMISSION CONTROL
PROTOCOL (TCP)
CONFIGURATION screen is
greater than 128.

PC-To-HP 3000 Communication

For SERIAL Networks
Screen

Item

Requirement Status

GUIDED NETWORK
INTERFACE
CONFIGURATION

Network Interface Name.

Required.

NODE NAME
CONFIGURAnON

HP 3000 node name.

Required. Keep track of this
node name. including its
donrzin and organization
fields. because you will need it
when you configure the PC
workstation with the
USRCONFG utility.

LINK CONFIGURATION
SCREEN

Link Name.

Required.

LINK CONFIGURATION:
ASNP LINK DATA

Logical Device (LDEV)
number.

Required.

Subtype (hardwired. modem.
European modem).

Check that the default is
correct for your
implementation.

ROUTER NETWORK
INTERFACE LINKS

Link name and link type to be
established between the HP
3000 and the PC workstation.
NMMGR offers three options
to indicate the type of link to
be established: Direct Connect.
Shared Dial. and Direct Dial.

Required. This value must
also be entered in the
USRCONFG utility.

IPPROTOCOL
CONFIGURAnON

UP 3000 IP address.

Required.

D-13

PC-To-HP 3000 Communication

For SERIAL Networks (continued)
Screen

Item

Requirement Status

GLOBAL TRANSPORT
CONFIGURATION

Maximum directly connected
nodes and maximum inbound
destinations. (Values for
these fields should be greater
than or equal to the number
of nodes, including PC
workstations and PC servers.
in the network.)

Use the default unless number
of network nodes (including
PC workstations and servers)
exceeds 100.

TRANSMISSION CONTROL
PROTOCOL (TCP)
CONFIGURATION

Maximum number of
connections.

DIAL ID PROTOCOL
CONFIGURATION

YES/NO decision for an HP
3000 security string.

If you want a security string.
enter yes. If you do not want
a security string. enter no.
The YES or NO entry. must
also be entered in the
USRCONFG utility.

SECURITY STRlNG{S)
CONFIGURATION

HP 3000 security string.

Required if the Security On
Field has been set to YES.

D-14

PC-To-HP 3000 Communication
For SERIAL Networks (continued)
Item

Screen

Requirement Status

ROUTER MAPPING
CONFIGURAnON

Node name of the PC
workstation (or a name to
represent a route to the PC
workstation. )

Required for NMMGR. The
actual nodename of the
workstation is required in the
USRCONFG utility.

ROUTER REACHABLE
NODES

The IP address of the PC
workstation.

Required. This value must
also be entered in the
USRCONFG utility.

Link Name.

Required.

Entry priority.

Use default unless more than
one phone number has been
allocated to a single IP
address.

NOTE

An HP 3000 on a SERIAL network also must have a network directory
configured. On an IEEE802. 3 network, a directory needs to be configured
only if the HP 3000 will be a proxy server. Section 14 describes the
network directory. The network directory must contain the node name of
each PC connected to an HP 3000, as well as the proper IP address
associated with the PC.
For information on configuring additional items, as well as complete information on configuring with
NMMGR, refer to sections 5-14.
For information on configuring the HP 3000 as a node on the network in order to operate Resource
Sharing, refer to Resource Sharing: System Management.

Assigning HP 3000 Logons
(UP 3000 system manager)

For each PC user using AdvanceLink or AdvanceLink 2392 for UP 3000 access, the UP 3000 System
Manager should assign a user logon. Refer to the System Operation and Resource Management Reference
Manual for information about assigning user logons.
For each PC user using Resource Sharing, assign Resource Sharing automatic 10gons with the RESMGR
utility. Refer to Resource Sharing: Utilities for more information.

D-15

PC-To-HP 3000 Communication
The configuration of PC user logonsmay. vary for different·· application· software products. Refer to the
documentation provided for a particular product for information about logon configuration.

....

D-16

~ vs NS INP Configuration

I~E'

The SYSDUMP items described in the following table used to configure an INP for a DS point-to-point
link must be examined for consistency with NS if you choose to use the same INP for an NS
point-to-point link. Note that some values entered in SYSDUMP are overridden in NMMGR for an NS
link.
Table E-l. DS vs NS INP Configuration
Item in
SYSDUMP

DS
Default

NMMGR(NS)
Default

NMMGR Screens, Fields,
and Comments

Subtype

none

Not confjgurable. NMMGR
overrides any value entered
in SYSDUMP

Receive Timeout

20 sec.

Not configurable (usually
overridden by subsystem)

Local Timeout

60 sec.

60 sec. (for
LAP-B)
BSC not
configurable

Local timeout field on
LAP-B Link Data screen

Connect Timeout

300 sec. for dial
links, 120 for
non -dial links

900 sec. (for
LAP-B and BSC)

Connect Timeout field in
LAP-B Link Data screen, or
BSC Link Data screen

Speed Changeable

none

For NS links must enter
YES in SYSDUMP.

Dial Facility

none

autodial (LAP-B
&BSC)

Manual or Autodial field in
LAP-B Link Phone Data
screen, or BSC Link Phone
Data screen.

Transmission Mode

none

Not configurable.
Hard-coded:
LAP-B: full duplex
BSC: half duplex

Transmission Speed

none; value is
specified in
bytes/second

9600 bits/
second

Line speed in bits/second
field LAP-B Link Data
screen, or BSC Link Data
screen

E-I

os vs NS INP Configuration
Table E-l. DS vs NS INP Configuration

E-2

Item in
SYSDUMP

DS
Default

NMMGR(NS)
Default

NMMGR Screens, Fields
and Comments

Phonelist/ Phone
Number

none

Phone Number field in
Router Reachable Nodes
screen or Gateway Dial
Link Configuration screen.

Local/Remote ID
Sequence

none

Security String field in
Router Reachable Nodes
screen, or Gateway Dial
Link Configuration screen.
For an INP used both as a
DS and a NS link,
local/remote ID sequences
are ignored by NS but are
still valid for DS.

Virtual terminal
configured for INP
DRT#

none

For NS links, back reference
to the console. Do not back
reference to a OS link INP.

GLOSSARY

A
address - in networking. a numerical identifier defined and used by a particular protocol and
associated software to distinguish one node from another.
address resolution - in NS networks. the mapping of node names to IP addresses and the
mapping of IP addresses to subnet addresses.
adjacent - describes a node on a router network that is connected to another node by a single
link, with no intervening nodes.
Advanced Terminal Processor (ATP) - a hardware card that fits into the backplane of the UP
3000 and that provides a physical layer interface for Asynchronous SERIAL Network Links.
Asynchronous Serial Network Protocol (ASNP) - a Data Link Layer protocol used for
Asynchronous SERIAL Network Links.
ASNP - see Asynchronous Serial Network Protocol
ATP - see Advanced Terminal Processor
autodial - describes a dial link in which the remote node's telephone number is automatically
dialed by modem or other device with this capability.
AUf cable - Attachment Unit Interface cable, a cable joining the LANIC to the MAU (Media
Attachment Unit) for coaxial cable IEEE 802.3 local area network links.

B
Bisynchronous Communication protocol - see BSC protocol.
boundary - see network boundary.
broadcast - a method of communcation in which all nodes on the network share the same
communcications channel (referred to as the communications bus). Messages are transmitted to
all nodes on the same bus at the same time. IEEE 802.3 networks are broadcast networks.
brother branching - the process of proceeding to another screen in NMMGR by using the NEXT
command. The screen displayed after entering NEXT will be one on the same hierarchal level as
the current screen in the configuration tree structure.
BSC protoool - a data link layer protocol that can be used over NS Point-to-Point 3000/V
Links that use dial links (switched lines). BSC is an acronym for the Bisynchronous
Communication protocol.
buffer - a logical grouping of a system's memory resources used by NS3000/V.

GLOSSARY-I

Glossary

c
catenet - a group of computer networks that are conneoted to one another.
Catenet Administrator - the person having responsibility for coordinating network management
tasks among all networks in the catenet.
catenet lifecycle - see lifecycle, network/catenet
central administrative node - a node designated as the node in the catenet to be the first one
updated with new or changed internet routing and network directory information about any
other nodes in the network.
Communications Services (CS/3000) - software included with NS3000/V links that provides
some diagnostic and link management software.
computer name - term used in some HP networking documentation to refer to node name. (See
node name.)
computer network - a group of computer systems connected in such a way that they can
exchange information and share resources.
configuration - the process of defining the characteristics of the network in software. Two
kinds of configuration must be performed for each node in an NS3000/V network: system
configuration, accomplished with the SYSDUMP utility, and network configuration,
accomplished with the NMMGR utility.
CSLIST - a utility that lists version numbers for the software modules of the CS/3000
subsystem, and provides information on the INP and LANIC download files.

CSDUMP - A utility that formats files created by the CSTRACE utility, which traces link
activities.
DADCONF. PUB. SYS configuration file - a file that must be installed to allow initialization of
purchased network services. This file must be created after system configuration has occurred,
and the SYSDUMP tapes are loaded, and before network configuration with NMMGR.

D
data screen - a type of screen displayed by NMMGR that allows you to configure data.
Dial 10 protocol - a proprietary Hewlett-Packard protocol that provides security checking and
address exchange for dial links.
dial link - a connection between network nodes made through pubic telephone lines.
direct path branching - the process of proceeding from screen to screen in NMMGR. by entering
path names in the Path: field.
directly connected - describes nodes that are members of the same network.
distributed network - a computer network in which connected systems are independent and
equally in control of the network's operation.

GLOSSARY-2

"'"
)

Glossary

DSLIST - a utility that lists the version numbers of software modules that are part of the DS
subsystem of NS3000/V.
DSDUMP - a utility that can format link trace files created with CSTRACE. Formatting with
DSDUMP rather than CSDUMP provides more information on the data link and network level
activities when the BSC or X. 25 protocols are in use.
DSM - the INP Diagnostic Support Monitor, a utility used to test INP cards.
driver - software that controls I/O devices) including NS3000/V links.

E
entry, network directory - the data in a network directory that consists of a node's name and its
path report list.
entry priority - the ranking used to identify the most desirable to the least desirable routes used
to reach a given remote node from a given local node in a router network.
environment - a session established on a remote node.

F
full gateway - a node that is a member of more than one network. Because it is a member of
more than one network, the node can pass messages from one network to another.

G
gateway - a node that can provide communication between networks. A gateway can be either
a full gateway or a gateway half.
gateway half - a node that, in conjunction with another node on another network, performs the
function of a gateway. Together, two gateway halves can link two networks in the same catenel
gateway half link - A link that joins two nodes that form a gateway half pair. The link must
be configured as the link used for the gateway half network interface at each of the two nodes.
The NS Point-to-Point 3000/V Link and the Asynchronous SERIAL Network Link can be used
as gateway half links.
gateway balf pair - a set of two nodes that are joined by a gateway half link. Each node in the
pair must have a gateway half network interface configured, using that link.
gateway node - a node used to connect networks in the same catenet. To be a gateway node on
an NS3000/V network, a node must be configured as part of more than one network, or must be
configured as a gateway half in conjunction with another gateway half node on another
network.
general protocols - protocols used by an NS 3000/V node regardless of link type: these are the
IPU UP Update), TCP, and PXP protocols.

GLOSSAR.Y- 3

Glossary
global entry - a network directory entry that can be merged into other directories. and that can
therefore be used by other nodes in the network.

Guided Configuration - a method of configuring a nooe in which a subset of the complete
NMMGR Interface is presented. and in which defaults of configurable values are used
automatically.

H
hop count - see internet hop count and intranet hop count.

I
IEEE 80Z.3 - a standard for a broadcast looal area network published by the Institute for
Electrical and Electronics Engineers (IEEE).
IEEE 802.3 networkF.- net\\\lrks whose operation is based on the IEEE 802. 3 standard for looa1
area networks. ThinLAN/3000, LAN3000/V, and StarLAN/3000 are NS3000/V links that
can be used to create IEEE 802.3 networks.
inbound - pertaining to data being received at a given node.
INPDPAN - INP Dump Analysis, a utility that generates a formatted dump of an INP log file.
An INP log file is generated when an error occurs; it contains the contents of the INP memory.
Intelligent Network Processor (lNP) - a hardware card that fits into the backplane of the UP
3000 and provides a physical layer interface for NS Point-to-Point 3000/V Links. The INP is
also used for DS links; however, a single INP cannot provide an interface for an NS link and a
DS link concurrently.
internet communication - communication that occurs between networks.
Internet Protocol (IP) - a protocol used to provide routing among different networks in the same
catenet, as well as among nodes in the same router network. The Internet Protocol corresPOnds to
layer 3, the Network Layer, of the OSI model.
internet bop count - the number of gateways that are used to route a message to its destination
network.
intranet communication - communication that occurs between nodes in a single network.
intranet hop count - the number of intermediate nodes that lie between a source and
destination node on the same router network.

IP address - an address used by the Internet Protocol to perform internet routing, and used to
provide intranet addresses in NS3000/V router networks.
IP - see Internet Protocol.
IPC line test - a software program that tests whether the Network Transport is operating
correctly.

GLOSSARY-4

Glossary

L
LANDPAN - LANIC Dump Analysis a utility that generates a formatted dump of a LANIC log
file. The LANIC log file is produced when an error occurs; it contains the contents of the
LANIC memory.
J

LANIC - see Local Area Network Interface Controller
LANIC Self-Test - a ROM-based program on the LANIC card that tests and reports the statu8
of LANIC hardware.
LANDIAG - LAN Node Diagnostic, an interactive utility designed to help identify
malfunctioning hardware components of the LAN 3000/V Link.
LAP-B (Link Access Procedure, Balanced) protocol - a data link layer protocol that can be used
by NS Point-to-Point 3000/V Links. LAP-B must be used over direct-connect NS
Point-to-Point 3000/V Links.
leased line - data -grade telephone lines leased directly to a subscriber and allocated SPeCifically
for the subscriber's needs.
lifecycle, network/catenet management - the stages of development of a network or catenet.
The four stages consist of design, implementation, operation, and tuning and growth.
line speed - a measure of the rate at which data passes through a physical link (usually measured
in bits or kilobits per second).
link product - one of the NS3000/V Links: the NS Point-to-Point 3000/V Link, the
ThinLAN/3000 Link (including the LAN3000/V thick cable option). and the
Asynchronous SERIAL Network Link. Each link product consists of software and hardware
that together perform the functions of layers 1 through 4 of the 051 7-layer networking
model.
Link Support Services - an NS3000/V software subsystem that opens, closes, and otherwise
controls physical links.
Local Area Network Interface Controller (LANIC) - a hardware card that fits into the
backplane of the HP 3000 and provides a physical layer interface for IEEE 802. 3 local area
networks.
local entry - a network directory entry that cannot be distributed to other nodes in the
network.
local node - the node (computer that is part of a network) that you are currently using or
referring to.
logging - the process of recording the usage of network resources. NS3000/V logging is
performed at three levels: network, event, and link levels.
log class - a designation indicating the subset of information that will be logged.
loopback - the routing of messages originating from a node to that node itself.

GLOSSARY-S

Glossary

M
manual dial - describes a dial connection in which the remote node's telephone number must be
physically entered by someone such as the system operet{or
map, catenet or network - a drawing of a network or catenet that shows its topology, node and
network names, addresses, network boundaries (for a catenet map), and link types.
mapping - A set of characteristics that describe a route taken by Inessages to reach a destination
node. This set of characteristics is configured witl- NMMGR .t:. every node on a router network.
One mapping is configured at each node for ever) other node on the network to which messages
will be sent.
MAU - Media Attachment Unit. a device attached to a coaxial cable for a LAN3000/V Link.
The MAU provides physical and electrical connection from the AUI cable to the coaxial cable.

menu screen - a type of screen displayed by NMMGR that allows you to select an NMMGR
function. such as proceeding to a certain configuration branch, refreshing the screen display. or
returning to the previously displayed screen.
MPE-V - Multiprogramming Executive V. the operating system of Series 37 through 70 HP
30008 and MICRO 30009. NS3000/V operates in conjunction with the MPE-V operating
system.

N
name - In the context of NS3000/V networks. a name is a character string used to identify some
portion or component of a network or catenet.
neighbor gateway - a gateway that is in the same network as a given node.
neighbor node - a node that is in the same network as a given node.
NetiPC - Network Interprocess Communication. software that enables programs to access
network transport protocols.

network - see computer network.
network address - the network portion of the IP address. The IP address consists of a network
portion and a node portion.
network architecture - the plan that defines the characteristics and interactions of the
hardware and software used to create a network.
network boundary - the logical division between networks in a catenet.
network directory - a file containing information required for one node to communicate with
another node in the catenet. The active network directory on a node must be named
NSDIR. NET. SYS.
network interface - the collective software that provides an interface between a system and a
network. A node will possess a network interface for each of the networks to which it belonlS,
and for each of the gateway half links of which it is a part.

OLOSSARY-6

Glossary
network management - the collective tasks required to design, install, configure, maintain, and
if necessary, change a network.
network management lifecycle - see lifecycle. network/catenet
network manager - the person responsible for performing and coordinating network
management tasks for an entire network.
Network Transport - software that corresponds to layers 3 and 4 of the OSI network
architecture model. The function of this software is to send data out over the appropriate
communications link, and to receive incoming data, and to route the incoming or outgoing data
to the appropriate destination node.
NFT - Network File Transfer, the Network Service that transfers disc files between nodes on
the network.
NMCONFIG.PUB.SYS configuration file - The configuration
needed for link level and NetlPC logging.

file containing information

NMDUMP - a utility used to format log and trace files.
NMMAINT - a utility that lists the software module version numbers for all UP AdvanceNet
products, including NS3000/V.
NMMGR - see Node Management Configurator
node - a computer that is part of a network.
node address - the node portion of the IP
network portion.

addre~

which consists of a node portion and a

Node Management Configurator (NMMGR) - an NS3000/V software subsystem that enables
you to configure each node on a network.
Node Management Services - an NS3000/V software subsystem that provides configuration file
version checking and logging.
Node Manager - the person responsible for performing network management tasks for a node on
a network.
node name - a character string used to identify each system that is a node in a network or
catenet. Each node name in a network or catenet must be unique; however, a single node can be
identified by more than one node name.
non-adjacent - describes a node on a router network that is separated from a given node by
intervening, or intermediate nodes.
NSCONF.NET.SYS - Default name, and name recommended by HP for the network transport
configuration file residing on each node. This name is used throughout the NSJOOO/Y Network
Manager Reference Manual to refer to this configuration file.
NSDIR.NET.SYS - Name of the active network directory file. For convenience, this name is
used throughout the NSJOOO/Y Network Manager Reference Manual to refer to the network
directory file.

GLOSSARY-7

Glossary
NS3000/V - a Hewlett-Packard data communications product that provides networking
capabilities for HP 3000 minicomputers. NS3000/V also provides communication between HP
3000s and other types of computers
NS3000/V Network Services - software applications that can be used to access data, initiate

processes. and exchange information among nodes in the network.
RFA, RDSA, NFT, and PTOP.

The services are: RPM, VT,

NS3000/V Link

- software and hdrdware tnat provides the connection between nodes on a
network. Four NS3000/V links are available; the NS Point-to-Point 3000/V Link, the
ThinLAN/3000 Link (including the ThickLAN thick cable option), StarLAN/3000 Link, and
the Asynchronous SERIAL Network Link.

o
outbound - pertaining to data being sent from a given node.
OSI (Open Systems Interconnection) model - a model ot network architecture devised by the
International Standardards Organization (ISO). The OSI model defines seven layers of a network
architecture, each layer performing specified functions.

p
Packet Exchange Protocol (PXP) - a Transport Layer protocol used in NS3000/V links to
initially establish communication between nodes when the NetlPC socket registry is used.
partner gateway half - two gateway halves connected by a link and configured to provide
communication between two networks are partner gateway halves.
path name - in configuration with NMMGR, a string that can be typed in the UPath:" field of
NMMGR display screens that causes another screen to appear. Each screen has a unique path
name that corresponds to its location in the hierarachy of configuration screens presented by
NMMGR.
path report - a data structure containing name-to-address mapping information for a node, as
well as the networking protocols used by the node for its interface to a given network.
path report list - the set of all path reports for a node, which includes path reports for all the
networks the node belongs to.
point-to-point network - networks in which messages are transmitted from node to node in the
network over a defined route until reaching their destination.
pool - virtual terminals are configured in groups called pools. A pool of virtual terminals is
shared by all NS communications devices on a system.
Probe protocol - an HP protocol used by nodes on NS3000/V IEEE 802.3 networks to obtain
information about other nodes on the network.
Probe proxy server - a node on an IEEE 802.3 network that possesses a network directory and is
therefore used to provide information about nodes on other networks in the catenet to nodes on
the IEEE 802. 3 network.

GLOSSARY-8

.~"

Glossary
protocols - the rules and conventions that define the functions to be performed and the format
of messages exchanged by each layer of network architecture.
PTOP - Program-to-Program Communication. the Network Service that allows programs
residing on different nodes to exchange information with one another in a master/slave
relationship.
PXP - see Packet Exchange Protocol.

Q
QuickVal - a software program that tests whether Network Services are operating correctly
between nodes.

R
RDBA - Remote Data Base Access. the Network Service that allows users to access data bases on
remote nodes.
reachable network - a network that can be accessed (with additional internet hops possibly
required) by a particular gateway.
remote node - a node on the network other than the node you are currently using or referring
to.
resolution, of names and addresses - see address resolution.
RFA - Remote File Access, the Network Service that allows users to access files and devices on
remote nodes.
RPM - Remote Process Management, the Network Service that allows a process to
programmatically initiate and terminate other processes throughout a network from any node on
the network.
router network - one of the types of networks that can be created with NS3000/V link
products. Router networks are point- to-point networks. The NS Point-to-Point 3000/V Link
and the Asynchronous SERIAL Network Link can be used to create router networks.
routing - the process used to determine the path that packets, or pieces of a message, take
through a network or catenet to reach a destination node.

s
security string - an alphanumeric character string that functions as a password for dial links.
The security string is used by the DiallD protocol.
select screen - a type of screen displayed by NMMGR that allows you to select identifien (such
as names) to add, delete, rename, or update.
shared dial - describes a dial link that provides connection to more than one remote system,
although to only one at a time.

GLOSSARY-9

Glossary

statton address - a link-level address used by the IEEE 802. 3 protocol that is assigned to every
node on an IEEE 802.3 network.
store-and-forward - a technique In wtlal~h me~4ges are passed from one node to another in a
network to reach their \1estination.
POint-to p:Jlnt networks use the store-and-forward
technique to transmit messages.
subnet - another name for a network especially if the network is part of a catenet. The word
subnet is also a synonym for Intranet
synchronization - the process of creating and modifying network directories so that all
directories in the network or catenet are identical or at least contain the information required
for the network to operate as planned.
SYSDUMP - the software program that allows you to perform system configuration on UP
3000s.
system configuration - the means of defining to M·PE-V the peripheral devices attached to the
UP 3000 for the input and output of data, and the parameters required for system operation.

T
TCP - see Transmission Control Protocol
TERMDSM - a utility used to diagnose problems with the ATP. The ATP is a card installed in
the UP 3000 for Asynchronous SERIAL Network links.
topology - the physical arrangement of nodes in a network. Some common topologies are bus,
star, and ring.
Transmission Control Protocol (TCP) - a network protocol that establishes and maintains
connections between nodes. Tep regulates the flow of data, breaks messages into smaller
fragments if necessary (and reassembles the fragments at the destination), detects errors, and
retransmits messages if errors have been detected.

u
utility, NMMGR - NMMGR utilities, which are accessed from the UTILITY menu screen, consist
of Output Configuration File, Compress, Validate, and Configuration Subtree Copy utilities.

v
validation - the process of ascertaIning whether the transport configuration file hu been
correctly configured. This is accomplished by using the NMMGR Validate Configuration File
screen.
virtual terminal - sof' \od"P' that simulates the function of a terminal to MPH. Devices that
provide incoming data to a system require the COafl~U,.·~tlnn of virtual terminals.
VPLUS - software used to generate screens such as those displayed by NMMGR.

GLOSSARY-lO

Glossary

x
XPT liDe test - a software program that tests whether the Network Transport is operating
correctly.

GLOSSARY-II

INDEX

A
address, IP, format of, 3-8
administration, network, overview of, 3-24
alternate gateways, 3-19
alternate links, 3-16
alternate routes, intranet, 3- 5
alternate routes, router network, 3-5
assignment, of node names, 3- 6
autodial, 3-14
automatic rerouting, 3-16
Add (key), 5-22
Adding a device, 4-21, 4-22
Adding a virtual terminal, 4-21, 4-22
Adding devices
and maximum number of devices, 4-19, 4-25, 4-27
Addresses
IEEE 802. 3, 3-10
network, 3-9
node, 3-10
Architecture
network, 1- 3
051 model, 1-4
ARPA, 1- 8, 1-11
Asynchronous Serial Network Protocol, 1-12
ASNP link trace data, fields, 7-29
ASNP Link data, 7-27
ASNP, 1-12
ATP, protocols, 1-12
ATP, configuration dialogue, 4-27
AUI, LAN 3000/V Link (ThickLAN), 1-18

B
buffers, 3-13
Binary Synchronous Communication protocol, 1-12
Bisync, 1-12
Brother branching, 5-1 5
BSC link trace data, fiel~ 7-15
BSC Link data, 7-11
BSC,I-12
Buffer size, 4-11

c
central administrative node, 14-4
classes
internet address, 3- 8

INDEX-I

Index

IP address, 3- 8
command window, 5-14
command, COPYCONF, 5-46
commands, HELP, 5-7
confIguration files, 3- 2
configuration file, use for address resolution, 3-12
configuration terminology, 3-13
configuration updates/gateway half, 6-13, 6-15
configuration updates/router mapping, 6-13
configuration updates/router, 6-16
configuration
data, copying, 5-40, 5-46
dial ID protocol, I 1- 10
direct connect link, 11 -1 7
files, 5-9, 5-27
gateway half dial link, 11 - I 9
gateway half, 11- 3
general protocol, 8-1 0
global transport, 8-7
internet protocol, 11-7
internte protocol, 8-11
neighbor gateway reachable networks, 11-24
neighbor gateways, 11-22
network interface links, 11-15
network interface, 8-21
packet exchange protoco~ 8-14
protocol, 11 - 6
PXP,8-14
security strings, 11-13
transmission control protocol, 8-17
with NMMGR, overview of, 3-26
configuration, overview of, 3- 26
copying configuration data, 5-40, 5-46
dsline connections, 5-43, 5-47
type select parameters, 5-46
current file size (field), 5-33
Checksum Enabled (screen), 8-15
Checksum Enabled (field), 8-18
Commands, NMMGR, 5-16
Commands, MPE, 2- 5
Communications drivers, 4-25
Communications Systems, utilities, 2-6
Compress (screen), 5- 33
Condense Page (key), 5-22
Configuration Menu screen, 5-12
Configuration Subtree Copy (screen), 5-40
Configuration, 3-72
examples, 4-34

1/0,4-3
logging, 13-1
Configuration, NS3000/V, 2-10
Configured Reachable Networks Hops (field), 11-26
Configured Reachable NetworkslP Network Number (field), 11-25
Connection Assurance Interval (field), 8-20

INDEX-2

Index
Correcting Guided Configuration Errors, 6-4
COLDSTART,4-33
COPYCONF, 5-46

D
data flag, 5-23
data
dial ID protocol, II -1 0
internet protocol, 11-7
network interface link, 11-1 7
NI link, I 1-1 7
transmission control protocol, 8-11
TCP,8-11
definitions, of configuration terms, 3-13
design considerations
geographical location, 3-29
line speed, 3- 29
design, network and catenet, 3-29
destination file (field), 5-41
destination path (field), 5-41
diallD protocol configuration, 11-10
dial links, I-I 3
dial links, and network design, 3- 30
dial links, terminology for, 3-13
dial
autodial, 3-14
direct, 3-13
manual, 3-14
shared, 3- 13
direct connect link configuration, 11-1 7
direct connect, 3-14
direct dial, 3- 13
direct path branching, 5-14
directly connected, definition of, 3-15
domain, in node name, 3- 6
downed links, 3-16
dpath:dfilename (parameter), 5-46
Data
internet protocol, 9-1, I 0- 8, 12- 5
Nllink, 9-15,10-19
packet exchange protocol, 8-14
Probe protocol, 9-1 0
DARPA, 1-8, I-II
Default speed, overriding, 4- 23
Defense Advanced Research Projects Agency, 1-8, 1-11
Delete (key), S- 22
Device classes, 4- 8
Device
adding, 4-21, 4-22
removing, 4-21, 4-22
Devices, switched, 4- 23
DELETENODE command, 14-15

INDEX-3

Index
Dial ID protocol, 1- 13, 3-14
Dial Protocol Configuration (screen), 11-10
Direct Connect Link Configuration (screen), 11-1 7
DPAN5, 2-4
Drivers
communications, 4-13, 4- 25
Drivers, I/O configuration, 4- 8
DRT entry number, 4-5
DRT number, 4-3
DS-compatible links, 1-24
modem, 1-24
point-to-point, 1-24
satellite link, 1-24
X.25, 1-24
DS-Compatible links, and network design, 3-30
Dump date, 4-32

E
entry priority, 3-16
entry priority, definition of, 3-1 5
Enable console logging, 13-8
Enable disc logging, 13- 8
ENTER (key), 5-14
Error Information (screen), 5-43
Examples, configuration, 4-34
EXIT command, 14-1 9
EXPANDDIR command, 14-1 7

F
failures, link, 3-16
format, node name, 3-6
Fields
ASNP link trace data, 7- 29
BSC link trace data, 7-1 5
IEEE 802. 3 link trace data, 7-9
link name, 7-4
new name, 7-4
Nllinks, 9-14, 9-18, 9-23,10-17,10-24,10-31,11-23
File (field), 5-14
First Page (key), 5-22
Formats, IP addresses, 3-8
Fragment Assembly Queue Elements (field), 11-9
Full Duplex, 4-23

G
gateway half configuration, 11- 3
gateway half dial link configuration, 11-19
gateway half partner, 3-15

INDEX-4

Index
gateway half partners~ 3- 32
gateway halves, and network design, 3- 31
gateway name, 3-7
gateway, neighbor, definition of, 3-1 S
gateways
and network design, 3- 31
maximum number per network, 3- 31
gateways, alternate~ 3-19
gateways, redirect, 3-21
gateways, terminology for, 3-15
guided configuration, overview of, 3- 26
Gateway Half Dial Link Configuration Screen (screen). 11-19
Gateway-Half Network Interface Configuration (screen). 11-4
General Protocol Configuration (screen). 8-10
Global transport configuration, 8-7
Guided Configuration Tree, 6- 3
Guided Configuration, 6-1
gateway half, 6-11
loopback, 6-6
LAN 802. 3, 6-7
Netxport Configuration, 6- 5
Netxport Update, 6-13
PC router, 6-12
router, 6-9

H
home network name~ 3-7
hop count
internet, 3-14
intranet, 3-14
Hardware components, LAN 3000/V Link (ThickLAN), 1-18
Hardware components, ThinLAN, 1-19
HELP, 5-7
Home Network Name (field), 8-7
HP ThinLAN , medium access method, 1-18

I
inbound buffers, definition of~ 3-13
installation, network, overview of, 3-23
installation. software and hardware. overview of, 3-24
internet addresses, classes, 3- 8
internet address, format of, 3-8
internet protocol configuration, 11-7
internet Protocol UP) Update Configuration (screen), 8-12
internet rerouting. 3-19
internetwork, 1-11
I/O configuration, 4- 3
device classes, 4- 8
drivers, 4- 8
DRT entry number, 4-5

INDEX-S

Index
logical device number, 4-5
types and substypes, 4-6
ICMP redirect message, 3- 21
ICMP,3-21
Idle Device Timeout Value (field), 11- S
IEEE 802. 3 addresses. 3-10
IEEE 802.3 link trace data, fields, 7-9
IEEE 802. 3 local area network, protocols, 1-12
IEEE 802.3 Link data, 7-6
IEEE 802.3
link data fields, 7-6
link data screen, 7- 6
Initial Retransmission Interval (field), 8-19
Initialization, NS3000/V, 2-10
Installation, NS3000, 2-7
Intelligent Network Processor, 4-22, 4-23
adding, 4- 21, 4- 22
Internal Message Queue Length (field), 11-9
Internet protocol data, 9-7,10-8,12-5
Internet protocol update, data, 8-11
Internet Protocol, 1- 8, 1-11
INP driver, 4-10
INP, 4-22, 4-23
adding, 4-21, 4-22
configuration dialogue, 4- 22
protocols, 1-1 2
IP addresses
assigning, 3-9
classes, 3- 8
IP address, format of, 3- 8
IP Internet Address (field), 11- 8
IP Protocol Configuration (screen), 11-7
IP, 1- 8, I -111

K
keep (parameter), 5-46

L
link failures, 3-16
link name, 3-7
link selection, network interface, 11-15
link software, 1-14
links, alternate, 3-16
local node, 3-1 3
local, in router link configuration, 3-15
logging configuration
classes, 13- S
subsystems, 13-3
Last Page (key), 5-22
Layers, 1-3, 1-4

INDEX-6

Index
Protocols, I - 3
LAN 3000/V Link (ThickLAN), 1-15
AU., 1-18
hardware components~ 1-18
LANIC, 1-18
medium access method, 1-18
MAU~ 1-18
LAN 3000/V (ThickLAN), software components, 1-19
LAN802.3 data, NI, 9-3
LAN.C~ configuration dialogue~ 4- 21
LANIC~ LAN 3000/V Link (ThickLAN), 1-18
LANIC, ThinLAN, 1-19
LAP-B Link data, 7-19
LAP-B,I-12
Leaving system I/O configuration, 4-21, 4-22
Leaving SYSDUMP, 4-21, 4-22
Link configuration screen, 7- 3
Link data
ASNP, 7-27
BSC~ 7-11
IEEE 802.3,7-6
LAP-B, 7-19
Link name, 7-4
Link Name (field), 11-16
Link selection
network interface, 9-13, 10-16
Link Support Services subsystem, 3- 2
LISTDIR command~ 14-17~ 14- 22
LISTLOG5, 2-5
Local Node Name (field)~ 8-6
Logging classes, screen, 13-7
Logging config, .,class data screen, 13- 8
Logging configuration
classes, I 3- 7
guidelines, 13-1
overview, I 3- 1
screen, 13- 5
Logical device number, 4- 5

M
maintenance mode interface, 14-14
manual configuration, overview of, 3- 26
manual dial, 3-14
map, of network or catenet, 3-24
multicast~ for Probe requests~ 3-11
Main Menu screen, 5-6
Maximum Connection Assurance Retransmissions (field)~ 8-20
Maximum Directly Connected Nodes (field)~ 8-8
Maximum Gateway Nodes Per Network (field), 8-13
Maximum Inbound Destinations (field)~ 8-9
Maximum number of devices~ 4-19, 4-25, 4-27
Maximum Number of Connections (field)~ 8-18

INDEX-7

Index
Maximum Number of Networks in Catenet (field), 8-12
Maximum Outbound Destinations (field), 8-9
Maximum Retransmissions Per Packet (field). 8-20
Maximum Retransmissions Per Request (field), 8-16
MAKESTREAM command, 14-19
MAU. LAN 3000/V Link (ThickLAN), 1-18
Medium access method. UP ThinLAN • 1-18
Medium access method, LAN 3000/V Link (ThickLAN). 1-18
Menu screens. 5-1 9
Menu
general protocol. 8-1 0
NI protocol. 9-6.10-7,11-6.12-1
MERGEDIR command. 14-16
Modems, with internal clocking signals, 4-23
MPE commands, 2-4. 2-5
MPE- V. version required. 1-2

N
name
home network, 3-7
link. 3-7
network interface, 3-7
NI.3-7
name-to-address resolution. 3-10
names and addresses, 3- 5
names, other. 3-7
names. definitions of, 3-5
neighbor gateway reachable networks configuration. 11-24
neighbor gateways configuration, 11-22
neighbor gateway. definition of, 3-15
network administration. overview of. 3-24
network and catenet design. 3-29
network boundary. and design. 3-32
network boundary. definition of, 3-32
network configuration worksheets, 3-33
network design
and gateways, 3- 31
and network interfaces, 3- 31
dial links, 3- 30
DS-Compatible links, 3- 30
gateway halves. 3-31
non- UP 3000 nodes, 3-30
personal computers, 3-30
network directories, synchronization of, 3-27
network directory
central administrative node. 14-4
data screen. 14-11
DELETENODE command. 14-1 S
EXIT command. 14-19
EXPANDDIR command, 14-17
file structure. 14-1
for name-to-address resolution. 3-11

INDEX-8

Index
functions of, 14-1
global entries, I 4- 3
HELP command, 14-18
interfaces, 14-4
local entries, 14- 3
LISTDIR command, 14-17, 14-22
maintenance mode interface, 14-14
Main screen, 14-7
MAKESTREAM command, 14-19
MERGEDIR command, 14-16
OPENDIR command, 14-1 5
path report lists, 14-2
path reports, 14-2
roles, 14-4
Select Node Name Screen, 14-9
network installation, overview of, 3-23
network interface link configuration, 11-15
network interface name, 3-7
network interface
configuration, 8- 21
link data, 11-1 7
link selection, 11-1 5
protocol menu, 11- 6
network interfaces, and network design, 3-31
network interface, definition of, 3-13
network links, 1-14
network manager
link level tools, 2-6
link level utilities, 2-6
network life cycle, 2-3
tools, 2-3
network map, 3-24
network maps, overview of, 3-33
network planning and configuration, 3-1
network startup, overview of, 3-28
non-HP 3000 nodes, and network design, 3- 30
number of additional records (field), 5- 33
number of free records (field), 5-33
NCONF files, 5-9
Neighbor Gateway Reachable Networks (screen), 11-24
Neighbor Gateways (screen), 11-23
Network addresses, 3-9
Network architecture, 1-3
Network Administration Office, address of, 3-9
Network Administration Office, of Hewlett Packard, 3-9
Network Architecture
Layers, 1-3
OSI model, 1-4
Network File Transfer, 1-26
Network interface
link data, 9-15, 10-19
link selection, 9-1 3, 10-16
links fields, 9-14, 9-18, 9-23,10-17,10-24,10-31,11-23
links screen, 9-14, 9-18, 9-23, 10-17, 10-24, 10-31, 11-23

INDEX-9

Index
LAN 802. 3 data, 9-3
protocol config. screen, 9-6, 10-7, 12-4
Network Implementation and Support Plan, 3-33
Network Interface Links (screen), 11-16
Network Interface Name (field), 8-22
Network Interface
protocol menu, 9-6,10-7,12-1
Network life cycle, 2-3
Network Layer, 1-11
Network management, responsibilities of, 2-3
Network Management, 2-1
Network Services subsystem, 3-2
Network Services, 1-1
Network Transport Configuration Selection (screen), 8-3
Network Transport subsystem, 3-2
Network, 1-3
Netxport Configuration, 6- 2
Netxport Update, 6-2,6-13
New Name (field), 11-16
Next Page (key), 5-22
NEXT, 5-15
NFT,I-26
NMCONFIG. PUB. SYS configuration file, 3- 3
NMMGR commands, 5-16
NMMGR Path Commands, 5-14
NMMGR screens
Compress, 5-33
Configuration Subtree Copy, 5-40
data entry, 5-23
Output Configuration File, 5- 27
simple-select screens, 5-20
typed -select, 5- 21
Utility, 5-26
NMMGR, 5-1
Add (key), 5-22
command window, 5-14
configuration files, 5-9
configuration screens, 5-12
Condense Page (key), 5- 22
data entry screens, 5-23
data flag, 5-23
Delete (key), 5-22
ENTER (key), 5-14
file (field), 5-14
First Page (key), 5-22
Last Page (key), 5-22
Next Page (key), 5-22
Ptev Page (key), 5-22
run string, 5- 2
Refresh Screen (key), 5-19
Rename (key), 5-22
screen structure, 5- 8
screens, 5-12
simple-select screens, 5- 20

INDEX-I 0

Index
typed -select, 5- 21
utilities, 5-26
Update Config (key), 5-24
Update (key), 5-22
Node addresses, 3-10
Node Configuration (screen). 8-4
Node management services, 2- 5
Node management services. commands. 2-5
Node management services, utilities, 2-5
Node Management Configurator subsystem, 3-2
Node Name Configuration (screen), 8-5
Non-operational links, 3-16
NS3000/V, 1-26
configuration, 3-72
environment, 1-26
initialization, 2-1 0
I/O configuration, 4- 3
services, 1-26
session, 1-26
system configuration, 4- 2
system requirements, 1-2
NS3000
configuration, 2-10
installation. 2-7
NSCONF.PUB.SYS configuration file. 3-3
NSDIR.PUB.SYS file, 3-3
NSDPAN/ETOD, 2-4
Number of Inbound Buffers (field), 11-4
Number of Outbound Buffers (field), 11-4

o
organization. in node name. 3-6
outbound buffers, definition of. 3-13
overwrite existing subtree (field), 5-41
Open Configuration/Directory File screen, S- 3
OPENDIR command, 14-15
OSI model, layers, 1-4
OSI Model, 1-4
Output Configuration File (screen), 5-27
Overriding default speed, 4-23

p
packet exchange protocol
configuration, 8-14
data. 8-14
partner, of a gateway half, 3-1 S
path report lists, 14-2
path reports, 14-2
path report, definition of, 3-11
personal computers, and network design, 3-30

INDEX-II

Index
personal computers) as nodes, 1-25
physical layer protocols. 1-12
planning) of network. catenet. 3- 24
priority) of router network route entries. 3-15
protocol configuration) 11-6
protocol) DialID, 3-14
protocols. bisync) 1- 24
protocol) Probe, 3-11
proxy server. for Probe protocol. 3-11
Packet Exchange Protocol (PXP) Configuration (screen). 8-1 S
Packet Exchange Protocol. I-II
Path commands) NMMGR. 5-14
Phone number) 4-12
PhoneJist. 4-12
Prev Page (key» 5-22
Probe protocol) 1-13) 3-11
data. 9-10
Probe proxy server) 3-11
Program -to-Program Communications. 1- 26
Protocol Configuration (screen). 11-6
Protocols, 1- 3
PTOP.I-26
PXP configuration screen. 8-15
PXP configuration, 8-14
PXP. 1-11

R
reachable networks) definition of. 3-1 S
redirect gateways. 3- 21
redirect message, 3- 21
redirection) of internet packets, 3-19
remote node. 3-13
remote. in router link configuration. 3-1 5
requirements
software. 1- 2
system. 1-2
rerouting. 3-16
rerouting. for IEEE 802.3 gateways. 3-21
rerouting. for router networks. 3-16
rerouting. internet. 3-19
resolution. of names and addresses, 3-10
router links, terminology. 3-14
router node name. 3-7
routes. alternate. 3- 5
routing
broadcast. 3- 5
intranet. 3-4
routing. of messages. 3- 4
RDBA, 1-26
Refresh Screen (key). 5-19
Remote Data Base Access. 1- 26
Removing a device. 4-21. 4-22

INDEX-12

Index
Rename (key), 5- 22
Retransmission Interval Lower Bound (field), 8-19
Retransmission Interval Upper Bound (field), 8-19
Retransmission Interval (field), 8-15

s
screens
configuration menu, 5-12
Error Information, 5-43
global transport configuration, 8-7
General Protocol Configuration, 8-10
Internet Protocol (IP) Update Configuration, 8-12
main menu, 5-6
network interface links, 11- 16
Network Transport Configuration Selection, 8-3
NI links, 11 - 16
Node Configuration, 8-4
Node Name Configuration, 8-5
Open Configuration/Directory file, 5- 3
Packet Exchange Protocol (PXP) Configuration, 8 -1 5
Protocol Configuration, 11-6
PXP configuration, 8-15
TCP configuration, 8-18
Transmission Control Protocol Configuration, 8-18
validate configuration file, 5- 3 5
security strings configuration, 11-13
security string, definition of, 3-14
shared dial, 3-13
and network design, 3-30
software requirements, 1-2
software, link, 1-14
software, of NS3000/V, 3-2
software, required, 3-25
source file (field), 5-40
source path (field), 5-41
spath:sfilename (parameter), 5-46
starting the network, overview of, 3-28
static neighbor node name, 3-7
store-and-forward buffers, definition of, 3-13
subsystems, software, 3- 2
synchronization, of network directories, 3-27
syntax, node name, 3-6
Screens
IEEE 802. 3, 7-6
link configuration, 7- 3
logging configuration, 13- 5
logging config.,class data, 13-8
logging config. ,logging classes, 13-7
NIlinks, 9-14, 9-18, 9-23,10-17,10-24,10-31,11-23
NI protocol config., 9-6, 10-7, 12-4
Security String Configuration Screen (screen), 11-13
Services

INDEX-13

Index

Network File Transfer, 1-27
PTOP Communication, 1- 27
Remote Data Base Access. 1- 27
Remote File Acce~ 1-27
Remote Process Management, 1-16
Virtual Terminal, 1-26
Services, node management, 2- 5
Software components, UP ThinLAN, 1-19
Software components, LAN 3000/V Link (ThickLAN), 1-19
Software Dump facility, 2-4
Speed, overriding default, 4- 23
StarLAN/3000 Link, 1-15
StarLAN/3000, protocols, 1-12
StarLAN, 1-1 S
Store & Forward Buffers (field), 11-8
Subtype, 4-22
Switched devices, 4-23
System configuration, 4- 2
System I/O configuration
leaving, 4-21,4-22
SYSDUMP, 2-4,4-1,4-2
leaving, 4-21. 4-22
SYSDUMP, configuration with, overview of, 3- 26
SYSDUMP, dialogue, 4- 30

T
terminology, for configuration, 3-13
transmission control protocol configuration, 8-17
transmission control protocol data, 8-17
type select in configuration copy, 5-46
TCP configuration screen, 8-1 8
TCP, I-II
data, 8-11
ThickLAN, 1-1 5
TbinLAN link, software components, 1-19
ThinLAN/3000 Link, 1-1 S
ThinLAN/3000
hardware components, 1-19
protocols, 1-12
ThinLAN, I-IS
LANIC, 1-19
ThinMAU, 1-19
ThinMAU, ThinLAN, 1-19
Transmission Control Protocol Configuration (screen), 8-18
Transmission Control Protocol, 1-11
Transmission mode, 4-10
Transmission speed, 4-11
Transport Layer protocols, 1-11
Type 16, 4-19
Type (LOOP, LAN802. 3, ROUTER, or GATEHALF) (field~ 8-11
Type, 4-21, 4-22

INDEX-I 4

Index
Types and subtypes, 4-6
Types (field), 11-16

u
Update (key), 5-22
Users enabled for logging, 13- 8
Utility (screen), 5-26

v
validation, of a node, 3-27
verification, of a node, 3- 27
Validate Configuration File screen, 5-35
Virtual terminal
adding, 4- 21, 4- 22
Virtual terminals, 4-9
Virtual terminal, configuration dialogue, 4-19
Virtual Terminal, 1- 26

w
worksheets
instructions, 3- 38
terminology, 3- 36
worksheets, network configuration, overview, 3-33

INDEX-IS

SALES & SUPPORT OFFICES

Arranged alphabetically by country

Product Line Sales/Support Key

Brisbane, Queensland
Office

Ke, Product Line
A Analytical
CM Components
C Computer S,stlms
E Electronic Instruments a Measurement Systems
M Medical Products
P Personal Computation Products
t
Sales only for specific product line
t.
Support only for specific product line

Hewlett-Packard Australia Ltd.
10 Payne Road
THE GAP, Queensland 4061
Tel: 61-7-300-4133
Telex: 42133
Cable: HEWPARO Brisbane
A.C.CM.E.M.P

IMPORTANT:TheIe s,mbols delignlte general product line capability.The, do not insure sales or
support availability tor all products within aline, at alilocations.Conlact ,our locallalel office tor
information regarding locations where HP support is available tor specific products.

HEADQUARTERS OFFICES
If there is no sales office listed for your area. contact one of these
headquarters offices.

ASIA

UNITED KINGDOM

ANGOLA

Hewlett-Packard Asia Ltd.
47/F, 26 Harbour Rd.•
Wanchai. HONG KONG
G.p.e. Box 863. Hong Kong
Tel: 5-8330833
Telex: 76793 HPA HX
Cable: HPASIAl TO

Hewlett-Packard Ltd.
Nine Mile Ride
WOKINGHA..
Berkshire. RG 113ll
Tel: 0344 773100
Telex: 848805/848814/848912

Telectra Angola lOA
Empresa Tecnica de Equipamentos
16 rue Cons. Julio de Vilhema
LUANDA
Tel: 35515.35516
Telex: 3134
E.P

CANADA
Hewlett-Packard (Canada) Ltd.
6877 Goreway Drive
MISSISSAUGA, Ontario l4V lM8
Tel: (416) 678-9430
Telex: 069-8644

EASTERN EUROPE
Hewlett-Packard Gas.m.b.h.
Lieblgasse 1
p.e.Box 72
A-1222 VIENNA, Austria
Tel: (222) 2500-0
Telex: 134425 HEPA A

NORTHERN EUROPE
Hewtett-Packard S.A.
V. o. Hooplaan 241
p.e.Box 999
Nl-118 LN 15 AMSTELVEEN
The Netherlands
Tel: 20 5479999
Telex: 18919 hpner

SOUTH EAST EUROPE
Hewtett-Packard S.A.
World Trade center
110 Avenue louis-Casai
1215 Cointrin. GENEVA, Switzerland
Tel: (022) 98 96 51
Telex: 27225 hpser
Mail Address:
P.O. Box
CH-1217 Meyrin 1
GENEVA
Switzerland

MIDDLE EAST
AND CENTRAL AFRICA
Hewlett-Packard S.A.
Middle East/central
Africa Sales H.C.
7. rue du Bois-du-lan
P.O. Box 364
CH·1217 Meyrin 1
GENEVA
Switzerland
Tel: (022) 83 12 12
Telex: 27835 hmea ch
Telefax: (022) 83 1535

UNITED STATES OF
AMERICA
Customer Information center
(800) 752-0900
6:00 AM to 5 PM Pacific Time

EASTERN USA
Hewlett-Packard Co.
4 Choke Cherry Road
ROCKVILLE, MD 20850
Tel: (301) 948-6370

MIDWESTERN USA
Hewlett-Packard Co.
5201 Tollview Drive
ROWNG MEADOWS, Il 60008
Tel: (312) 255-9800

SOUTHERN USA
Hewlett-Packard Co.
2000 South Park Place
ATLANTA, GA 30339
Tel: (404) 955-1500

WESTERN USA
Hewlett-Packard Co.
5161 lankershim Blvd.
NORTH MOLLYWOOD, CA 91601
Tel: (818) 505-5600

OTHER
INTERNATIONAL
AREAS
Hewtett-Packard Co.
Intercontinental Headquarters
3495 Deer Creek Road
PALO ALTO, CA 94304
Tel: (415) 857-1501
Telex: 034-8300
Cable: HEWPACK

ALGERIA
Hewlett-Packard Trading S.A.
Bureau de Liaison Alger
Villa des Lions
9. Hai Galloul
DZ-aORDJ EL BAHRI
Tel: 760336
Telex: 63343 dUon dz

ARGENTINA
Hewlett-Packard Argentina S.A.
Montaneses 2140/50
1428 BUENOS AIRES
Tel: 541-11-1441
Telex: 22796 HEW PAC-AR
A.C.E.P
Biotron S.A.C.l.M.e.l.
Av. Paso Colon 221. Piso 9
1399 BUENOS AIRES
Tel: 541-333-490.
541-322-587
Telex: 17595 BIONAR
M
Laboratorio Rodriguez
Corswant S.R.L.
Misiones.1156-1876
Bernal. oeste
BUENOS AIRES
Tel: 252-3958. 252-4991
A
Intermaco S.R.L.
Florida 537/71
Galeria Jardin - local 28
1005 BUENOS AIRES
Tel: 393-4471/1928
Telex: 22796 HEW PAC-AR
P(Calculators)
Argentina Esanco S.R.L.
A/ASCO 2328
1416 BUENOS AIRES
Tel: 541-58-1981. 541-59-2767
Telex: 22796 HEW PAC-AR
A
All Computers S.A.
Montaneses 2140/50 5 Piso
1428 BUENOS AIRES
Tel: 781-4030/40391783-4886
Telex: 18148 Ocme
P

AUSTRALIA
Adelaide, South
Australia Office
Hewlett-Packard Australia Ltd.
153 Greenhill Road
PARKSIDE, S.A. 5063
Tel: 61-8-272-5911
Telex: 82536
Cable: HEWPARD Adelaide
A· ,C.CM.E.P

Canberra, Australia
Capital Territory
Office
Hewlett-Packard Australia ltd.
Thynne Street. Fern Hili Park
BRUCE, A.C.T. 2617
P.O. Box 257.
JAMISON, A.C.T. 2614
Tel: 61-62-80-4244
Telex: 62650
Cable: HEWPARO Canberra
C.CM.E.P

Melbourne, Victoria
Office
Hewlett-Packard Australia Ltd.
31-41 Joseph Street
P.O. Box 221
BLACKBURN, Victoria 3130
Tel: 61-3-895-2895
Telex: 31-024
Cable: HEWPARD Melbourne
A.C.CM.E.M,P

Wael Pharmacy
P.O. Box 648
MANAMA
Tel: 256123
Telex: 8550 WAEl BN
E.M
Zayani Computer Systems
218 Sheik Mubarak Building
Government Avenue
P.O. Box 5918
MANAMA
Tel:- 276278
Telex: 9015 plans bn
P

BELGIUM
Hewlett-Packard Belgium S.A.lN.V.
Blvd de la Woluwe. 100
Woluwedal
B-12oo BRUSSELS
Tel: (02) 32-2-761-31-11
Telex: 23494 hewpac
A.C.CM,E.M.P

BERMUDA
Applied Computer Technologias
Atlantic House Building
P.O. Box HM 2091
Par-la-Ville Road
HAMILTON 5
Tel: 295-1616
Telex: 380 3589/ACT BA
P

Perth Western Australia BOLIVIA
_ '

Office
Hewlett-Packard Australia ltd.
Herdsman Business Park
CLAREMONT, W.A. 6010
Tel: 61-9-383-2188
Telex: 93859
Cable: HEWPARD Perth
C,CM,E,P

Sydney, New South
Wales Office
Hewlett-Packard Australia Ltd.
17-23 Talavera Road
P.O. Box 308
NORTH RYDE, N.S.W. 2113
Tel: 61-2-888-4444
Telex: 21561
Cable: HEWPARO Sydney
A.C.CM.E.M.P

AUSTRIA
Hewlett-Packard Gas.m.b.h.
Verkaufsbuero Graz
Grottenhofstrasse 94
A-8052 GRAl
Tel: 43-316-291-5660
Telex: 312375
C.E
Hewlett-Packard Gas.m.b.h.
Lieblgasse 1
P.O. Box 72
A-1222 VIENNA
T(!I: 43-222-2500
Telex: 134425 HEPA A
A.C.CM.E,M,P

BAHRAIN
Green Salon
P.O. Box 557
MANAMA
Tel: 255503-250950
Telex: 84419
P

Arrellano Ltda
Av. 20 de OCtubre #2125
Casllla 1383
LA PAl
Tel: 368541
M

BRAZIL
Hewlett-Packard do Brasil S.A.
Alameda Rio Negro. 750-1. AND.
ALPHAYIW
06400 Baruerl SP
Tel: (011) 421.1311
Telex: (011) 71351 HPBR SR
Cable: HEWPACK Sao Paulo
CM,E
Hewlett-Packard do Brasil S.A.
PraJa de Botafago 228-A-614
6. AND.-CONJ. 601
Edlficio Argentina - Ala A
22250 RIO DE JANEIRO, RJ
Tel: (021) 552-6422
Telex: 21905 HPBR BR
Cable: HEWPACK Rio de Janeiro
E
Van Den Clentiflca ltda.
Rua Jose Bonifacio, 458
Todos os Santos
20771 RIO DE JANEIRO, RJ
Tel: (021) 593-8223
Telex: 33487 EGlB BR
A

ANAMED I.C.E.I. Ltda.
Rua Vergueiro, 360
04012 SAO PAULO, SP
Tel: (011) 572-1106
Telex: 24720 HPBR BR
M
Datatronix Electronica Ltda.
Av. Pacaembu 746-C11
SAO PAULO, SP
Tel: (118)260111
CM

BRUNEI
Komputer Wisman Sdn Bhd
G6, Chandrawaseh Cmplx,
Jalan Tutong
P.O. Box 1297,
BANDAR SERI BEGAWAN
NEGARABRUNIDARUSSALAM
Tel: 673-2-2000-70/26711
C,E,P

CAMEROON
Beriac
B. P. 23
DOUALA
Tel: 420153
Telex: 5351
C,P

CANADA
Alberta
Hewlett-Packard (Canada) Ltd.
3030 3rd Avenue N.E.
CALGARY, Alberta T2A 6T7
Tel: (403) 235-3100
A,C,CM,E* ,M,P*
Hewlett-Packard (Canada) Ltd.
11120-178th Street
EDMONTON, Alberta T5S 1P2
Tet: (403) 486-6666
A,C,CM,E.M.P

British Columbia
Hewlett-Packard (Canada) Ltd.
10691 SheUbridge Way
RICHMOND,
British Columbia V6X 2W8
Tel: (604) 270-2277
Telex: 610-922-5059
A,C.CM,E* ,M,P*
Hewlett-Packard (Canada) Ltd.
121 - 3350 Douglas Street
VICTORIA, British Columbia V8Z 3L1
Tel: (604) 381-6616
C

Manitoba
Hewtett-Packard (Canada) Ltd.
1825 Inkster Blvd.
WINNIPEG, Manitoba R2X 1R3
Tel: (204) 694-2777
A,C,CM.E.M,P*

New Brunswick
Hewlett-Packard (Canada) Ltd.
814 Main Street
MONCTON, New Brunswick E1C 1E6
Tel: (506) 855-2841

Nova Scotia
Hewlett-Packard (Canada) Ltd.
Suite 111
900 Windmill Road
DARTMOUTH, Nova Scotia B3B 1P7
Tel: (902) 469-7820
C,CM,E* ,M,P*

Ontario
Hewlett-Packard (Canada) Ltd.
3325 N. Service Rd., Unit W03
BURUNGTON, Ontario L7N 3G2
Tel: (416) 335-8644
C,M*
Hewlett-Packard (Canada) Ltd.
552 Newbold Street
LONDON, Ontario N6E 2S5
Tel: (519) 686-9181
A,C,CM,E* ,M.P*

Hewlett-Packard (Canada) Ltd.
6877 Goreway Drive
MISSISSAUGA, Ontario L4V 1M8
Tel: (416) 678-9430
Telex: 069-83644
A,C,CM,E,M.P
Hewlett-Packard (Canada) Ltd.
2670 Queensview Dr.
OTTAWA, Ontario K2B 8K1
Tel: (613) 820-6483
A,C,CM,E* ,M.P·
Hewlett-Packard (Canada) Ltd.
3790 Victoria Park Ave.
WlLLOWDALE, Ontario M2H 3H7
Tel: (416) 499-2550
C,E

Quebec
Hewlett-Packard (Canada) Ltd.
17500 Trans Canada Highway
South Service Road
KIRKLAND, Quebec H9J 2X8
Tel: (514) 697-4232
Telex: 058-21521
A,C,CM,E,M,P·
Hewlett-Packard (Canada) Ltd.
1150 rue Claire Fontaine
QUEBEC CITY, Quebec G1R5G4
Tel: (418) 648-0726
C
Hewlett-Packard (Canada) Ltd.
130 Robin Crescent
SASKATOON, Saskatchewan S7L 6M7
Tet: (308) 242-3702
C

CHILE

China Hewlett-Packard Co., Ltd.
P.O. Box 9610. Beijing
4th Floor, 2nd Watch Factory Main
Shuang Yu Shou, Bei San Huan Road
Hai Dian District
BEIJING
Tel: 33-1947 33-7426
Telex: 22601 CTSHP CN
Cable: 1920 Beijing
A,C,CM,E.M,P
China Hewlett-Packard Co., Ltd.
CHP Shanghai Branch
23/F Shanghai Union Building
100 Yan An Rd. East
SHANG·HAI
Tel: 265550
Telex: 33571 CHPSB CN
Cable: 3416 Shanghai
A,C,CM,E,M,P

COLOMBIA
Instrumentaci6n
H. A. Langebaek &Kler S.A.
Carrerra 4A No. 52A-26
Apartado Aereo 6287
BOGOTA 1, D.E.
Tel: 212-1466
Telex: 44400 INST CO
Cable: AARIS Bogota
CM,E,M
Nefromedlcas Ltda.
Calle 123 No. 98-31
Apartado Aereo 100-958
BOGOTA D.E., 10
Tel: 213-5267, 213-1815
Telex: 43415 HEGAS CO
A

ASC Ltda.
Austria 2041
SANTIAGO
Tel: 223-5946, 223-6148
Telex: 392-340192 ASC CK
C,P

Compumundo
Avenida 15 # 107-80
BOGOTAD.E.
Tel: 57-214-4458
Telex: 39645466 MARCO

Jorge Calcagni yCia
Av. ItaUa 634 Santiago
Casilla 16475
SANTIAGO 9
Tet: 9-011-562-222-0222
Telex: 392440283 JCYCL CZ
CM,E,M

Carvajal, S.A.
Calle 29 Norte No. 6A-40
Apartado Aereo 48
CAU
Tel: 9-011-57-3-621888
Telex: 39855850 CUJCL CO
C,E,P

Metrolab S.A.
Monjltas 454 of. 206
SANTIAGO
Tel: 395752, 398296
Tetex: 340866 METLAB CK
A
Olympia (Chile) Ltda.
Av. Rodrigo de Araya 1045
Casilla 256-V
SANTIAGO 21
Tet: 225-5044
Telex: 340892 OLYMP
Cable: Olympiachile Santlagochile
C,P

CONGO

CHINA, People's
Republic of
China Hewlett-Packard Co., Ltd.
47/F China Resources Bldg.
26 Harbour Road
HONG KONG
Tel: 5-8330833
Telex: 76793 HPA HX
Cable: HP ASIA LTD
A*,M*

serlc-Congo
B. P. 2105
BRAZZAVlW
Tel: 815034
Telex: 5262

COSTA RICA
Cientifica Costarricense S.A.
Avenida 2, Calle 5
San Pedro de Montes de Oca
Apartado 10159
SAN JOsE
Tel: 9-011-506-243-820
Telex: 3032367 GALGUR CR
CM,E,M
O. Fischel R. Y. Cia. S.A.
Apartados 434-10174
SAN JOSE
Tel: 23-72-44
Telex: 2379
Cable: OFIR
A

CYPRUS
Telerexa Ltd.
P.O. Box 1152
Valentine House
8Stassandrou St.
NICOSIA
Tel: 45 628, 82 898
Telex: 5845 tlrx cy
E.M,P

DENMARK
Hewlett-Packard A/S
Kongevejen 25
DK-3460 BIRKEROD
Tel: 45-02-81-6840
Telex: 37409 hpas dk
A,C,CM,E,M,P
Hewlett-Packard A/S
Rollghedsvej 32
DK-8240 Rl88KOV, Aarhus
Tel: 45-08-17-8000
Telex: 37409 hpas dk
C,E

International Engineering Associates
6 EI Gamea Street
Agouza
CAIRO
Tel: 71-21-68134-80-940
Telex: 93830 lEA UN
Cable: INTEGASSO
E
Sakrco Enterprises
70 Mossadak Street
Dokki, Giza
CAIRO
Tel: 706440, 701 087
Telex: 9337
C
S.S.C. Medical
40 Gazerat EI Arab Street
Mohandessin
CAIRO
Tel: 803844, 805998,810283
Telex: 20503 SSC UN
M*

DOMINICAN REPUBLIC EL SALVADOR
Mlcroprog S.A.
Juan Toma Mejfa y Cotes No. 60
Arroyo Hondo
SANTO DOMINGO
Tel: 585-6288
Telex: 4510 ARENTA DR (RCA)

IPESA de EI Salvador S.A.
29 Avenida Norte 1223
SAN SALVADOR
Tel: 9-011-503-266-858
Telex: 301205391PESA SAL
A,C,CM,E.P

ETHIOPIA

ECUADOR

seric-Ethlopla
P.O. Box 2764
ADDIS ABABA
Tel: 185114
Telex: 21150
C.P

CYEDE Cia Ltda.
Avenlda Eloy Alfaro 1749
y Belglca
Casilla 6423 CCI
QUITO
Tel: 9-011-593-2-450975
Telex: 39322548 CYEDE ED

U
Medtronlcs
Valladolld 524 Madrid
P.O. 9171, QUITO
Tel: 2-238-951
Telex: 2298 ECUAME ED
A
Hospitalar S.A.
Robles 825
Casilla 3590
QUITO
Tel: 545-250, 545-122
Telex: 2485 HOSPTL ED
Cable: HOSPITALAR-Quito
M
Ecuador Overseas Agencies C.A.
Calle 9 de Octubre 1818
P.O. Box 1296, Guayaquil
QUITO
Tel: 308022
Telex: 3381 PBCGYE ED
M

EGYPT
Sakrco Enterprises
P.O. Box 259
ALEXANDRIA
Tet: 802908.808020.805302
Te1ex: 54333
C

FINLAND
Hewtett-Packard Finland
R~~
Nllttytanpolku 10
00620 HELSINKI
Tet: (90) 757-1011
Telex: 122022 Field SF
CM
Hewlett-Packard Oy
Plispankalllontle 17
02200 ESPOO
Tel: (90) 887-21
Telex: 121563 HEWPA SF
A, C, E, M, P

FRANCE
Hewlett-Packard France
Z.I. Mercure B
Rue Berthelot
13763 Les Milles Cedex
AlX-EN-PROVENCE
Tel: 33-42-59-4102
Telex: 410770F
A,C,E,M
Hewlett-Packard France
64, Rue Marchand Saillant
F-61000 ALENCON
Tel: (33) 29 0442

C··
Hewlett-Packard France
Batlment Levitan
2585. route de Grasse
Bretetle Autoroute
06800 ANTlIES
Tel: (93) 74-59-19
C

SALES & SUPPORT OFFICES
Arranged alphabetically by country

FRANCE (Cont'd)
Hewlett-Packard France
28 Rue de la Republique
Boite Postale 503
25026 BESAN~ON CEDEX, FRANCE
Tel: (81) 83-16-22
Telex: 361157
C,E*
Hewlett-Packard France
ZA Kergaradec
Rue Fernand Forest
F-29239 GOUEESNOU
Tel: (98) 41-87-90
E
Hewlett-Packard France
Chemin des Moullles
Boite Postale 162
69131 ECULLY Cedex (Lyon)
Tel: 33-78-33-8125
Telex: 310617F
A,C,E,M,P*
Hewlett-Packard France
Parc d'activites du Bois Briard
2 Avenue du Lac
F-91040 EVRY Cedex
Tel: 3311/6077 9660
Telex: 692315F

C
Hewlett-Packard France
Application Center
5, avenue Raymond Chanas
38320 EYBENS (Grenoble)
Tei: (76) 62-57-98
Telex: 980124 HP GRENOB EYBE

C
Hewlett-Packard France
Rue Fernand. Forest
Z.A. Kergaradec
29239 GOUESNOU
Tel: (98) 41-87-90
Hewlett-Packard France
Pare Club des Tanneries
Batlment B4
4, Rue de la Faisanderie
67381 UNCOlSHEl1i
(Strasbourg)
Tel: (88) 76-15-00
Telex: 890141F
C,E*,M·,PHewlett-Packard France
Centre d'affaires Paris-Nord
Bitiment Ampere
Rue de la Commune de Paris
Boite Postale 300
93153 LE BLANC-MESNll
Tel: (1) 865-44-52
Telex: 211032F
C,E,M
Hewlett-Packard France
Parc d'actlvltes Cadera
Quartler Jean-Mermoz
Avenue du President JF Kennedy
33700 BRIGNAC (Bordeaux)
Tel: 33-56-34-0084
Telex: 550105F
C,E,M

Hewlett-Packard France
3, Rue Graham Bell
BP 5149
57074 METZ Cedex
Tel: (87) 36-13-31
Telex: 860602F
C,E
Hewlett-Packard France
Miniparc-ZIRST
Chemin du Vieux Chene
38240 MEYLAN (Grenoble)
Tel: (76) 90-38-40
980124 HP Grenobe
C
Hewlett-Packard France
Bureau vert du Bois Briand
Cheman de la Garde
- CP 212 212
44085 NANTES Cedex
Tel: (40) 50-32-22
Telex: 711085F
A,C,E,CM-,P
Hewlett-Packard France
125, Rue du Faubourg Bannier
45000 ORLEANS
Tel: 33-38-62-2031
E,PHewlett-Packard France
Zone Industrielle de Courtaboeuf
Avenue des Tropiques
91947 lES UUS Cedex (Orsay)
Tel: 33-6-907 7825
Telex: 600048F
A,C,CM,E,M,P· Hewlett-Packard France
15, Avenue de L'Amiral-Bruix
75782 PARIS Cedex 16
Tel: 33-15-02-1220
Telex: 613663F
C,PHewlett-Packard France
242 Ter, Ave J Mermoz
64000 PAU
Tel: 33-59-80-3802
Telex: 550365F
C,EHewlett-Packard France
6, Place Sainte Croix
86000 POITIERS
Tel: 33-49-41-2707
Talex: 792335F
C,EHewlett-Packard France
47, Rue de Chativesle
51100 REIIiS
Tel: 33-26-88-6919

C, p.
Hewlett-Packard France
Parc d'activites de la Poterie
Rue Louis Kerautel-Botmel
35000 RENNES
Tel: 33-99-51-4244
Telex: 740912F
A·tC,E,M,P·
Hewlett-Packard France
98 Avenue de Bretagne
76100 ROUEN
Tel: 33-35-63-5766
Telex: 770035F
C,E

Hewlett-Packard France
4, Rue Thomas-Mann
Boite Postale 56
67033 STAASBOUAG Cedex
Tel: (88) 28-56-46
Telex: 890141F
CtE,M,P·
Hewlett-Packard France
Le Peripole III
3, Chemin du Pigeonnier de la capiere
31081 TOULOUSE Cedex
Tel: 33-61-40-1112
Telex: 531639F
A.C,E,M,P·
Hewlett-Packard France
Les Cardoullnes
Batiment B2
Route des Oolines
Parc d'activite de Valbonne
Sophia Antipolis
06560 VALIONNE (Nice)
Tel: (93) 65-39-40
C
Hewlett-Packard France

9, Rue Baudin
26000 VALENCE
Tel: 33-75-42-7616

C··

Hewlett-Packard GmbH
Verbindungsstelle Bonn
Friedrich-Ebert-Allee 26
5300 BONN
Tel: (0228) 234001
Telex: 8869421
Hewlett-Packard GmbH
Vertriebszentrun Sudwest
Schickardstrasse 2
0-7030 BOBLINGEN
Postfach 1427
Tel: (07031) 645-0
Telex: 7265 743 hep
A,C,CM.E,M,P
Hewlett-Packard GmbH
Zeneralbereich Mktg
Herrenberger Strasse 130
0-7030 BOILINGEN
Tel: (07031) 14-0
Telex: 7265739 hep
Hewlett-Packard GmbH
Geschlftsstelle
Schleefstr. 28a
0-4600 DORTMUND-41
Tel: (0231) 45001
Telex: 822858 hepdod
ACE

' ,

Hewlett-Packard France
Carolor
. .
ZAC de BOIS Briand
57640 VIGY (Metz)
Tel: (8) 771 2022
C

Tel: (069) 500001-0
Telex: 413249 hpffm

Hewlett-Packard France
Parc d'activite des Pres
1, Rue Papin Cedex
59658 VillENEUVE D'ASCQ
Tel: 33-20-91-4125
Telex: 160124F
C,E,M,P

Hewlett-Packard GmbH
Vertriebszentrum Nord
Kapstadtring 5
0-2000 HAMBURG 60
Tel: 49-40-63-804-0
Telex: 021 63 032 hphh d
A,C,E,M,P

Hewlett-Packard France
Parc d'activites Paris-Nord 11
Boite Postale 60020
95971 Roissy Charles de Gaulle
VlllEPINTE
Tel: (1) 48 63 80 80
Telex: 211032F
C,E,M,P·

Hewlett-Packard GmbH
GeschAftsstelle
Heidering 37-39
0-3000 HANNOVER 61
Tel: (0511) 5706-0
Telex: 092 3259 hphan
A,C,CM,E,M,P
Hewlett-Packard GmbH
Geschlftsstelle
Rosslauer Wag 2-4
0.6800 MANNHEIM
Tel: 49-0621-70-05-0
Telex: 0462105 hpmhm
A,C,E
Hewlett-Packard GmbH
Geschlftsstelle
Messerschmittstrasse 7
0-7910 NEU UlM
Tel: 49-0731-70-73-0
Telex: 0712816 HP ULM-O
A,C,E-

GABON
Sho Gabon
P.O. Box 89
UBAEVILLE
Tel: 721 484
Telex: 5230

GERMAN FEDERAL
REPUBLIC
Hewlett-Packard GmbH
Vertriebszentrum Mitte
Hewlett-Packard-Strasse
0-6380 BAD HOMBURG
Tel: (06172) 400-0
Telex: 410844 hpbhg
A,C,E,M,P
Hewlett-Packard GmbH
Geschlftsstelle
Keithstrasse 2-4
0-1000 BERUN 30
Tel: (030) 219904-0
Telex: 018 3405 hpbln d
A,C,E,M,P

Hewlett-Packard gmbH
Reparaturzentrum Frankfurt
Berner Strasse 117
6000 FRANKFURTIMAIN 80

Hewlett-Packard GmbH
Geschlftsstelle
Emmericher Strasse 13
0-8500 NURNBERG 10
Tel: (0911) 5205-0
Telex: 0623 860 hpnbg
C,CM,E,M,P

Hewlett-Packard GmbH
Vertriebszentrum Ratingen
Berliner Strasse 111
0-4030 RATINGEN 4
Postfach 31 12
Tel: (02102) 494-0
Telex: 589 070 hprad
A,C,E,M,P
HeWlett-Packard GmbH
Vertriebszentrum Muchen
Eschenstrasse 5
0-8028 TAUFKIACHEN
Tel: 49-89-61-2070
Telex: 0524985 hpmch
A,C,CM,E,M,P
Hewlett-Packard GmbH
Geschlftsstelle
ErmIisallee
7517 WALDBRONN 2
Postfach 1251
Tel: (07243) 602-0
Telex: 782 838 hepk
A,C,E

GREAT BRITAIN
See United Kingdom
GREECE
Hewlett-Packard A.E.
178, Kifissias Avenue
6th Floor
Halandri-ATHENS
Greece
Tel: 301116473 360, 301116726090
Telex: 221 286 HPHLGR
A,C,CM· -,E.M,P
Kostas Karaynnis S.A.
8, Omirou Street
ATHENS 133
Tel: 3230303,3237371
Telex: 215962 RKAR GR
A,C·,CM,E
Impexin
Intelect Div.
209 Mesogion
11525 ATHENS
Tel: 6474481/2
Telex: 216286
P
Haril Company
38, Mihalakopoulou
ATHENS 612
Tel: 7236071
Telex: 218767

M·
Hellamco
P.O. Box 87528
18507 PIRAEUS
Tel: 4827049
Telex: 241441

GUATEMALA
IPESA DE GUATEMALA
Avenida Reforma 3-48, Zona 9
GUATEMALA CITY
Tel: 316627, 317853.66471/5
9-011-502-2-316627
Telex: 30557651PESA GU
A,C,CM.E,M,P

0
3

HONG KONG
Hewlett-Packard Hong Kong, Ltd.
G.P.O. Box 795
5th Aoor, Sun Hung Kat Centre
30 Harbour Road, Wan Chai
HONG KONG
Tel: 852-5-832-3211
Telex: 66678 HEWPA HX
Cable: HEWPACK HONG KONG
E,C,P
CET ltd.
10th Aoor, Hua AsIa Bldg.
64-66 Gloucester Road
HONG KONG
Tel: (5) 200922
Tatex: 85148 CET HX
CM
Schmidt & Co. (Hong Kong) ltd.
18th Aoor, Great Eagle Centre
23 Harbour Road, Wanchai
HONG KONG
Tel: 5-8330222
Telex: 74766 SCHMC HX
A,M

ICELAND
Hewtett-Packard Iceland
Hoefdabakka 9
112 REYKJAVIK
Tel: 354-1~7-1000
Telex: 37409
A,C,CM,E,M,P

Blue Star ltd.
133 Kodambakkam High Road
MADRAS 600 034
Tel: 472056, 470238
Telex: 041-379
Cable:BLUESTAR
A,M

Hewlett-Packard Ireland ltd.
Temple House, Temple Road
Blackrock, Co. DUBLIN
Tel: 88/333/gg
Telex: 30439
C,E,P

Blue Star Ltd.
13 Community center
New Friends Colony
NEW DELHI 110 065
Tel: 682547
Telex: 031-2463
Cable: BlUEFROST
A,C*,CM,E,M
Blue Star ltd.
15/16 C Wellesley Rd.
PUNE411 011
Tel: 22775
Cable: BLUE STAR
A

Blue Star ltd.
2-2-47/1108 Bolarum Rd.
SECUNDERABAD 500 003
INDIA
Tel: 72057, 72058
Computer products are sold through
Blue Star ltd.AlI computer repairs Telex: 0155-459
and maintenance service is done Cable: BlUEFROST
A,C,E
through Computer Maintenance Corp.
Blue Star ltd.
Blue Star ltd.
T.C. 7/603 Poornirna
B. D. Patel House
Maruthunkuzhi
Near Sardar Patel Colony
TRlYANDRUII695 013
AHIIEDABAD 380 014
Tel: 65799, 65820
Tel: 403531, 403532
Telex: 0884-259
Telex: 0121-234
Cable:BLUESTAR
Cable: BLUE FROST
E
A,C,CM,E
Computer Maintenance Corporation
Blue Star ltd.
ltd.
40/4 lavelle Road
115, Sarojini Devi Road
BANGALORE 560 001
SECUNDERABAD 500 003
Tel: 57881, 867780
Tel: 310-184, 345-774
Telex: 0845-430 BSlBIN
Telex: 031-2960
Cable: BlUESTAR
C"
A,C*,CM,E
Blue Star Ltd.
Band Box House
Prabhadevi
BOIIBAY 400 025
Tel: 4933101, 4933222
Telex: 011-71051
Cable: BLUESTAR
A,M
Blue Star ltd.
Sahas
414/2 Vir Savarkar Marg
Prabhadevi
BOIIIAY 400 025
Tel: 422~155
Telex: 011-71193 BSSS IN
Cable: FROSTBlUE
A,CM,E,M
Blue Star Ltd.
K2'?an, 19 VIShwas Colony
Alkapuri, BORODA, 390 005
Tel: 65235, 65236
Cable: BLUE STAR

IRAQ

Blue Star ltd.
7 Hare Street
P.O. Box 506
CALCUTTA 700 001
Tel: 230131, 230132
Telex: 031~112O BSNF IN
Cable: BlUESTAR
A,M,C,E

INDONESIA
BERCA Indonesia P.T.
P.O.Box 496/Jkt.
JI. Abdul Muis 62

JAKARTA
Tel: 21-373009
Telex: 46748 BERSAllA
Cable:BERSALJAKAATA
P
BERCA Indonesia P.T.
P.O.Box 24971Jkt
Antara Bldg., 12th Floor
JI. Medan Merdeka Selatan 17
JAKARTA-PUSAT
Tel: 21-340417
Telex: 46748 BERSAL IA
A,C,E,M,P
BERCA Indonesia P.T.
Jalan Kutai 24
IURABAYA
Tel: 67118
Telex: 31146 BERSAL SB
Cable: BERSAl-SURABAYA
A*,E,M,P

Hewlett-Packard Trading S.A.
Service Operation
AI Mansoor City 9B/3/7
BAGHDAD
Tel: 551-49-73
Telex: 212-455 HEPAIRAQ IK

IRELAND

Hewlett-Packard Ltd.
75 Belfast Rd, Carrickfergus
Belfast BT38 8PH

NORTHEIUIIREUND
Tet: 09603-67333
Telex: 747626
M

ISRAEL
Eldan Electronic Instrument Ltd.
P.O.Box 1270
JERUSALEII91000
16, Ohaliav SI.
JERUSALEII94467
Tel: 533 221, 553 242
Telex: 25231 AB/PAKRD Il
A,M
Computation and Measurement
Systems (CMS) Ltd.
11 Masad Str.t
67060
TEL-AVIV
Tel: 388 388
Telex: 33569 Motilll
C,CM,E,P

ITALY
HewleU-Packard Itallana S.p.A
Traversa 99C
Via Giulio Petroni, 19
1-70124 BAlI
Tel: (080) 41-07-44
C,M
Hewlett-Packard Italiana S.p.A.
Via emilia, 51/C
1-40011 BOLOGNA Anzola DelI'Emilia
Tel: 39-051-731061
Telex: 511630
C,E,M
Hewlett-Packard Italiana S.p.A.
Via Principe Nicola 43G/C
1-95126 CATANIA
Tet: (095) 37-10-87
Telex: 970291
C
Hewlett-Packard ItaJiana S.p.A.
Via G. di Vittorio 10
20094 CORIICO (Milano)
Tel: 39-02-4408351
Hewlett-Packard Italiana S.p.A.
Viate Brlgata Bisagno 2
16129 GENOVA
Tel: 39-10-541141
Telex: 215238
Hewlett-Packard Italiana S.p.A.
Viale G. Modugno 33
1-16156 GENOVA PEGU
Tel: (010) 68-37-07
Telex: 215238
C,E

Hewlett-Packard Italiana S.p.A.
Via G. di Vittorio 9
1-20063 CERNUSCO SUL
NAYIGUO
(Milano)
Tel: (02) 923691
Telex: 334632
A,C,CM,E,M,P
Hewlett-Packard ItaJiana S.p.A.
Via Nuova Rivoltana 95
20090 LllllTO (Milano)
Tef: 02-92761
Hewlett-Packard Italiana S.p.A.
Via Nuova San Rocco a
Capodimonte, 621A
1-80 131 NAPOLI
Tel: (081) 7413544
Telex: 710698
A··,C,E,M
HewleU-Packard Italiana S.p.A.
Via Orazio 16
80122NAPOU
Tel: (081) 7611444
Tetex: 710698
Hewlett-Packard Italiana S.p.A.
Via Pellizzo 15
35128'ADO'A
Tel: 39-49-684-888
Telex: 430315
A,C,E,M
HewleU-Packard ItaJiana S.p.A.
ViaJe C. Pavese 340
1-00144 ROllA &III
Tel: 39-65-48-31
Telex: 610514
A,C,E,M,P·
Hewlett-Packard ltaliana S.p.A.
Via di C8seilina 57/C
500518 SCANDICCI-FIRENZE
Tel: 39-55-753863
C,E,M
Hewlett-Packard Italiana S.p.A.

Corso SYizzera, 185
1-10144 TORIIO
Tel: 39-11-74-4044
Telex: 221079
A*,C,E

IVORY COAST
S.I.T.E.L
Societe Ivoirienne de
Telecommunications
Bd. Giscard d'Estaing
Carrefour Marcory
Zone4.A.
Boite postate 2580
AlllNM01
Tel: 353600
Telex: 43175
E
S.I.T.I.
Immeubl8 "le General"
Av. du General de Gaulle
01BP 161

ABlD.IMOl
Tel: 321227
Telex: 22149
C,P

JAPAN
Yokogawa-Hewlett-Packard Ltd.
152-1, Onna
ATIUGI, Kanagawa, 243
Tel: (0462) 25-0031
C,CM,E

Yokogawa-Hewlett-Packard Ltd.
Meill-Seimei Bldg. 6F
3-1 Motocniba-eho
CHIBA,28O
Tel: (0472) 257701
C,E
Yokogawa-Hewlett-Padcard Ltd.
Yasuda-Seimel Hiroshima Bldg.
6-11, Hon-dorl, Naka-ku
HIROSHIIIA, 730
Tel: (082) 241-0611
Yokogawa-Hewlett-Packard ltd.
Tewa Building
2-2-3 Kaigan-dorl, Chuo..ku
KOBE, 650
Tet: (078) 392-4791
C,E
Yokogawa-Hewlett-Packard Ltd.
Kumagaya Asahi 82 Bldg.
3-4 Tsukuba
KUIlAGAYA, Saitama 360
Tel: (0485) 24-6563
C,CM,E
Yokogawa-Hewlett-Packard Ltd.
Asahi Shlnbun Daiichi 5eimei Bldg.
4-7, Hanabata-cho
KUIWIOTO,860
Tel: 96-354-7311
C,E
Yokogawa-Hewfett-Packard Ltd.
Shin-Kyoto center Bldg.
614, Hlgashi-8hlokoji-cho
Katasuma-Nishilru
KYOTO,600
Tel: 075-343-0921
C,E
Yokogawa-Hewlett-Packard ltd.
Mito Mitsui Bldg.
1-4-73, Sanno..maru
Ibarald 310
Tel: (0292) 25-7470
C,CM,E

mo,

Yokogawa-Hewlett-Packard ltd.
Meili-Seimei Kokubun Bldg.
7-8 Kokubun, 1Chome, Sendai
IIYAGI, '980
Tel: (0222) 25-1011
C,E
Yokogawa-Hewlett-Packard Ltd.
GOOda Bldg. 2F
1-2-10 Gohda Okaya-8hi
Okaya-8hi
NAQANO,394
Tet: (0266) 23 0851
C,E
Yokogawa-Hewtett-Packard Ltd.
Nagoya Kokusai Center Building
1-47-1, Nagono, Nakamura-ku
NAGOYA, AlCII450
Tel: (052) 571-5171
C,CM,E,M
Yokogawa-Hewlett-Packard ltd.
Sal-Kyo..Ren Building
1-2 Dote-cho

OOIIYA" SAlTAlIA 330
Tel: (0486) 45-8031

SALES & SUPPORT OFFICES
Arranged alphabetically by country

JAPAN (Cont'd)

JORDAN

LEBANON

Yokogawa-Hewlett-Packard ltd.
Chuo Bldg., 5-4-20 Nishi-Nakajima
4-20 Nlshinaka;ima, 5 Chome,
Yodogawa-ku
OSAKA. 532
Tel: (06) 304-6021
Telex: YHPOSA 523-3624
C,CM,E,M,P·

Scientific and Medical Supplies Co.
P.O. Box 1387
AMMAN
Tel: 24907, 39907
Telex: 21456 SABCO JO
C,E,M,P

Computer Information Systems S.A.L.
Chammas Building
P.O. Box 11-6274 Dora
BEIRUT
Tel: 894073
Telex: 42309 chacis Ie
C,E,M,P

Yokogawa-Hewlett-Packard Ltd.
1-27-15, Yabe
SAGAliIHARA Kanagawa, 229
Tel: 0427 59-1311
Yokogawa-Hew1ett-Packard ltd.
Hamamtsu Motoshiro-Cho Oatchi
Seimei Bldg 219-21, Motoshiro-Cho
Hamamatsu-shi
SHIZUOKA,430
Tel: (0534) 561771
C,E
Yokogawa-Hewlett-Packard ltd.
Shinjuku OaUchi Seimei Bldg.
2-7-1, Nishi Shinjuku
Shinjuku-ku,TOKYO 163
Tel: 03-348-4611
C,E,M
Yokogawa Hewlett-Packard Ltd.
9-1, Takakura-cho
Hachioji-shi, TOKYO, 192
Tel: 81-426-42-1231
C,E
Yokogawa-H8Wtett-Packard Ltd.
3-29-21 Takaido-Higashi, 3 Chome
Suginami-ku TOKYO 168
Tel: (03) 331-6111
Telex: 232-2024 YHPTOK
C,CM,E,P·
Yokogawa Hokushin Electric
Corporation
Shinjuku-NS Bldg. 10F
4-1 Nishi-5hinjuku 2-Chome
Shinjuku-ku
TOKYO, 163
Tel: (03) 349-1859
Telex: J27584
A
Yokogawa Hokushin Electric Corp.
9-32 Nokacho 2 Chorne
Musashino-shi
TOKYO, 180
Tel: (0422) 54-1111
Telex: 02822-421 YEW MTK J
A
Yokogawa-Hewlett-Packard ltd.
Meiji-Seimei
Utsunomiya Odori Building
1-5 Odori, 2 Chome
UTSUNOIIIYA, Tochigi 320
Tel: (0286) 33-1153
C,E
Yokogawa-Hewlett-Packard ltd.
Yasuda Seimei Nishiguchi Bldg.
30-4 Tsuruya-cho, 3 Chorne
Kanagawa-ku, YOKOHAMA 221
Tel: (045) 312-1252
C,CM,E

KENYA
ADeOM Ltd., Inc., Kenya
P.O.Box 30070
NAIROBI
Tel: 331955
Telex: 22639
E,M

KOREA
Samsung Hewlett-Packard Co. ltd.
Oongbang Yeoeuido Building
12-16th Roors
36-1 Yeoeuido-Dong
Youngdeungpo-Ku
SEOUL
Tel: 784-4666, 784-2666
Telex: 25166 SAMSAN K
C,CM,E,M,P
Young In Scientific Co., Ltd.
Youngwha Building
547 Shinsa Dong, Kangnam-Ku
SEOUL 135
Tel: 546-7771
Telex: K23457 GINSCO
A
Oongbang Healthcare
Products Co. Ltd.
Suite 301 Medical Supply Center
Bldg. 1-31 Oongsungdong
Jong Ro-gu, SEOUL
Tel: 764-1171, 741-1641
Telex: K25706 TKBKO
Cable: TKBEEPKO
M

KUWAIT
AI-Khaldiya Trading &Contracting
P.O. Box 830
SAFAT
Tel: 424910, 411726
Telex: 22481 AREEG KT
Cable: VISCOUNT
E,M,A
Gulf Computing Systems
P.O. Box 25125
SAFAT
Tel: 435969
Telex: 23648
P
Photo & Cine Equipment
P.O. Box 270
SAFAT
Tel: 2445111
Telex: 22247 MATIN KT
Cable: MATIN KUWAIT
P
W.J. Towell Computer Services
P.O. Box 5897
SAFAT
Tel: 2462640/1
Telex: 30336 TOWELL KT
C

LIBERIA
Unichemicals Inc.
P.O. Box 4509
MONROVIA
Tel: 224282
Telex: 4509
E

LUXEMBOURG
Hewlett-Packard Belgium S.A./N.V.
Blvd de la Woluwe, 100
Woluwedal
B-12oo BRUSSELS
Tel: (02) 762-32-00
Telex: 23-494 paloben bru
A,C,CM,E,M,P

MADAGASCAR
Technique et Precision
12, rue de Nice
P.O. Box 1227
101 ANTANANARIVO
Tel: 22090
Telex: 22255
P

MALAYSIA
Hewlett-Packard Sales (Malaysia)
Sdn. Bhd.
9th Floor
Chung Khiaw Bank Building
46. Jalan Raja Laut
50736 KUALA LUMPUR, MALAYSIA
Tel: 03-2986555
Telex: 31011 HPSM MA
A,C,E,M,P·
Protei Engineering
P.O.Box 1917
Lot 6624, Section 64
23/4 Pending Road
Kuching, SARAWAI
Tel: 36299
Telex: 70904 PROMAL MA
Cable: PROTELENG
A,E,M

MALTA
Philip Toledo ltd.
Kirkirkara P.O. Box 11
Notabile Rd.
MRIEHEL
Tel: 447 47, 455 66, 491525
Telex: Media MW 649
E,M,P

MAURITIUS
Blanche Birger Co. ltd.
18, Jules Koenig Street
PORT LOUIS
Tel: 20828
Telex: 4296
P

MEXICO
Hewlett-Packard de Mexico,
S.A. deC.V.
Rio Nio No. 4049 Oesp. 12
Frace. Cordoba
JUAREZ
Tel: 161-3-15-62
P

Hewlett-Packard de Mexico,
S.A. deC.V.
Condominio Kadereyta
Circuito del Mezon No. 186 Desp. 6
COL DEL PRADO - 76030 Oro.
Tel: 463-6-02-71
P
Hewlett-Packard de Mexico,
S.A. de C.V.
Monti Morelos No. 299
Fraccionamiento Loma Bonita 45060
GUADALAJARA, Jalisco
Tel: 36-31-48-00
Telex: 0684186 ECOME
P
Microcomputadoras
Hewlett-Packard, S.A.
Monti Pelvoux 115
LOS LOMAS, Mexico, O.F.
Tel: 520-9127
P
Microcomputadoras Hewtett-Packard,
S.A. deC.V.
Monte Pelvoux No. 115
Lomas de Chapultepec, 11000
MEXICO, D.F.
Tel: 520-9127
P
Hewlett-Packard de Mexico,
S.A. deC.V.
Monte Pelvoux No. 111
Lomas de Chapultepec
11000 MEXICO, D.F.
Tel: 5-40-62-28, 72-66, 50-25
Telex: 17-74-507 HEWPACK MEX
A,C,CM,E,M,P

MOROCCO
Etablissement Hubert 001 beau & Fils
81 rue Karatchi
B.P.11133
CASABLANCA
Tel: 3041-82, 3068-38
Telex: 23051, 22822
E
Gerep
2, rue Agadir
Boite Postale 156
CASABLANCA 01
Tel: 272093, 272095
Telex: 23 739
P
Sema-Maroc
Dept. Seric
6, rue Lapebie
CASABLANCA
Tel: 260980
Telex: 21641
C,P

NETHERLANDS
Hewtett-Packard Nedertand B.V.
Startbaan 16
Nl-1187 XR AllSTELYEEN
P.O. Box 667
Nl-1180 AR AMSTELYEEN
Tel: (020) 547-6911
Telex: 13216 HEPA Nl
A,C,CM,E,M,P

Hewlett-Packard Nederland B.V.
Bongerd 2
P.O. Box 41
Nl2900AA CAPELLE AID IJSSEL
Tel: 31-20-51-6444
Hewtett-Packard De Mexico (Polanco)
Telex: 21261 HEPAC Nl
Avenida Ejercito Nacional #579
C,E
2d8y3er piso
Hewlett-Packard Nederland B.V.
Colonia Granada 11560
Pastoor Petersstraat 134-136
EXlCOD.F.
P.O. Box 2342
Tel: 254-4433
Nl5600 CH EINDHOVEN
P
Tel: 31-40-32-6911
Hewlett-Packard de Mexico,
Telex: 51484 hepae nl
S.A. deC.V.
C,E,P
Czda. del Valle
NEW ZEALAND
409 Ote. 4th Piso
Hewlett-Packard (N.Z.) Ltd.
Colonia del Valle
5 Owens Road
Municipio de Garza
P.O. Box 26-189
Garcia Nuevo leon
Epsom, AUCKLAND
66220 MONTERREY, Nuevo le6n
Tel: 64-9-687-159
Tel: 83-78-42-40
Cable: HEWPAK Auckland
Telex: 382410 HPMY
C,CM,E,P·
C
Infograficas y Sistemas
del Noreste, S.A.
Rio Orinoco #171 Oriente
Despacho 2001
Colonia Del Valle
MONTERREY
Tel: 559-4415, 575-3837
Telex: 483164
A,E
Hewlett-Packard de MeXico,
S.A. deC.V.
Blvd. Independencia No. 2000 Ote.
Col. Estrella
TORREON, COAM.
Tel: 171-18-21-99
P

Hewtett-Packard (N.Z.) ltd.
184-190 WIllis Street
WEWNGTON
P.O. Box 9443
Courtenay Place, WEWHGTON 3
Tel: 64-4-887-199
Cable: HEWPACK Wellington
C,CM,E,P
Northrop Instruments & Systems ltd.
369 Khyber P~ Road
P.O. Box 8602
AUCKLAND
Tel: 794-091
Telex: 60605
A,M

G
5

Northrop Instruments & Systems Ltd.
110 Mandeville St.
P.O. Box 8388
CHRISTCHURCH
Tel: 488-873
Telex: 4203
A,M
Northrop Instruments & Systems Ltd.
Sturdee House
85-87 Ghuznee Street
P.O. Box 2406
WEWNGTON
Tel: 850-091
Telex: NZ 3380
A,M

NIGERIA
Elmeco Nigeria Ltd.
45 Saka Tlrubu 51.
Victoria Island
LAGOS
Tel: 61-98-94
Telex: 20-117
E

Mushko & Company Ltd.
Cosman Chambers
Abdullah Haroon Road
URACIl 0302
Tel: 524131, 524132
Telex: 2894 MUSKO PK
Cable: COOPERATOR Karachi
A,E,P·

PANAMA
Electronico Balboa, S.A.
Calle Samuel Lewis, Ed. Alta
Apartado 4929
PANAIIA CITY
Tel: 9-011-507-836613
Telex: 388 3483 ELECTRON PG
CM,E.M,P

PERU

NORWAY

Cia Electro M6d1ca S.A.
Los Ramencos 145, Ofc.301/2
San Isidro
Casilla 1030
LIlIA 1
Tel: 9-011-511-4-414325, 41-3705
Telex: 39425257 PE PB SIS
CM,E,M,P

Hewtett-Packard Norge AlS
Folke Bemadottes wi 50
P.O. Box 3558
N-5033 FYLLINGSDALEN (Bergen)
Tel: 0047/5/16 55 40
Telex: 76621 hpnas n
C,E,M

SAMSS.A.
Arenlda Republica de Panama 3534
San Isidro, LIlIA
Tef: 9-011-511-4-229332/4139841
413226
Telex: 39420450 PE LIBERTAD
A,C,P

NORTHERN IRELAND
See United Kingdom

Hewlett-Packard Norge AIS
Ostemdalen 16-18
P.O. Box 34
N-1345 OEiTERAAS
Tel: 47-2-17-1180
Telex: 76621 hpnas n
A,C,CM,E,M,P
Hewlett-Packard Norge A/S
Boehmergt. 42
Box 2470
N-5037 SOLHEIIISVIK
Tel: 0047/5/29 00 90

OMAN
Khimjil Ramdas
P.O. Box 19
MUSCAT/SULTANATE OF OMAN
Tel: 795 901
Tefex: 3489 BROKER MB MUSCAT
P
Suhail &Saud Bahwan
p.a.Box 169
MUSCAT/SULTAMATE OF OMAN
Tel: 734 201-3
Tefex: 5274 BAHWAN MB
E
ImtacLLC
P.O. Box 9196
IIINA AL FAHAL/SULTAMATE

OFOIIAN
Tel: 70-77-27, 70-77-23
Telex: 3865 Tawoos On
A,C,M

PAKISTAN
Mushko &Company Ltd.
House No. 16, Street No. 18
Sector F-6/3

ISLAIIABAD
Tel: 824545
Telex: 54001 Muski Pk
Cable: FEMUS Islamabad
A,E,P·

PUERTO RICO

SINGAPORE

Hewtett-Packard Puerto Rico
101 Munoz Rivera Av
Esu. Calle Ochoa
HATO REV. Puerto Rico 00918
Tel: (809) 754-7800
A,C,CM,M,E,P

Hewlett-Packard Singapore (Sales)
Pte. Ltd.,
1150 Depot Road
SINGAPORE. 0410
Tel: 4731788
Telex: 34209 HPSGSO RS
Cable: HEWPACK, Singapore
A,C,E,M,P

QATAR
Computer Arabia
P.O. Box 2750
DOHA
Tel: 428555
Tetex: 4808 CHPARB
P
Nasser Trading &Contracting
P.O.Box 1563
DOHA
Tel: 422170
Telex: 4439 NASSER DH
M

SAUDI ARABIA
Modem 8ectronlcs Establishment
Hewlett-Packard OMslon
P.O. Box 281
Thuobah
AL-KHOBAR 31952
Tel: 895-1760, 895-1764
Telex: 671 106 HPMEEK SJ
Cable: ELECTAAL-KHOBAR
C,E,M
Modern Electronics establishment
Hewtett-Packard DivIsion
P.O. Box 1228
Redec Plaza, 6th Roor

PHILIPPINES

JEDDAH

The Online Advanced Systems Corp.
2nd Roar, Electra House

Tet: 644 96 28
Telex: 402712 FARNAS SJ

115-117 Esteban Street
P.O. Box 1510
Legaspi Village, Makati
Metro IIAI&A
Tel: 815-38-10 (up to 16)
Telex: 63274 ONLINE PN
A,C,E,M,P

PORTUGAL
Mundlnter Intercambio
Mundlal de Com6rclo S.A.R.L
Av. Antonio Augusto AgUiar 138
Apartado 2781

US80N
Tel: (19) 53-21-31,53-21-37
Telex: 16691 munter p
M
Soquimica
Av. da Uberdade, 220-2
1298 LI8BOA Codex
Tet: 56-21-82
Telex: 13316 SABASA
A
Telectra-Empresa T6cnIca de
Equlpmentos El6ctricos S.A.R.L
Rua Rodrigo da Fonseca 103
P.O. Box 2531
U880N 1
Tet: (19) 88-80-72
Telex: 12598
CM,E
C.P.C.S.I.
Rua de Costa Cabral 575
4200 PORTO
Tel: 499174/495173
Telex: 28054
C,P

Cab~:ELECTAJEDDAH

A,C,CM,E,M,P
Modem Electronics establishment
Hewtett-Packard Division
P.O.Box 22015
RIYADH 11495
Tel: 491-97 15,491-83 87
Tetex: 202049 MEERYD SJ
C,E,M
Abdul Ghani EI Ajou Corp.
P.O. Box 78

RIYADH
Tel: 40 41717
Telex: 200 932 EL AJOU
P

SCOTLAND
See United Kingdom

SENEGAL
Societe Hussein Ayad &Cle.
76, Avenue Georges Pompidou
B.P.305

DAKAR
Tel: 32339
Cable: AYAD-Oakar
E
Moneger Distribution S.A.
1, Rue Parent
B.P.148

DAKAR
Tel: 215871
Telex: 587
P
Systeme 8ervice Conseil (sse)
14, Avenue du Parachois

DAKAR ETOILE
Tel: 219976
Telex: 577
C,P

Oynamarlnternational Ltd.
Unit 05-11 Block 6
Kolam Ayer Industrial Estate
SINGAPORE 1334
Tet: 747-6188
Telex: 26283 RS
CM

SOUTH AFRICA
Hewlett-Packard So Africa (Pty.) Ltd.
P.O. Box 120
Howard Place, CAPE PROVIICE
7450 South Africa
Tel: 27 121153-7954
Telex: 57-20006
A,C,CM,E,M,P
Hewtett-Packard So Africa (Pty.) Ltd.
2nd Floor Juniper House
92 Overport Drive
DURlAN4067
Tel: 27-31-28-4178
Telex: 6-22954
C
Hewlett-Packard So Africa (Pty.) ltd.
Shop 6 Linton Arcade
511 Cape Road
Linton Grange
PORT ELIZABETH 6001
Tel: 27141130 1201
Telex: 24-2916
C
Hewlett-Packard So Africa (Ply.) ltd.
Fountain Center
Kalkoen Str.
Monument Park Ext 2
PRETORIA 0105
Tel: (012) 45 5725
Telex: 32163
C,E

Hewlett-Packard Esp.mola, S.A.
Avda. S. Francisco Javier, SIN
Planta 10. Edlficio Sevilla 2

E·SEYIW 5. SPAIN
Tel: 54/64 44 54
Tefex: 72933
A,C,M,P
Hewlett-Packard EspaftoIa, S.A.
lsabet La Catollca, 8
E-46004 VALENCIA
Tet: 34-6-3611354
Tetex: 63435
C,P
Hewlett-Packard Espailola, S.A.
Av. de Zugazarte, 8
Las Arenas-Guecho
E-4893O VIlCAYA
VIlCAYA
Tel: 34-423-83 06
Telex: 33032

SWEDEN
Hewlett-Packard Sverlge AB
astra Tullgatan 3
5-2001111AU16
Box 8132
Tel: 46-40-702-70
Telex: (854) 17888 (via SpAnga
office)
C,P
Hewlett-Packard Sverige AB
Elementvagen 16
S-7022 76REBRO
Tel: 49-019-10-4820
Telex: (854) 17886 (via SpAnga office)
C
Hewlett-Packard SVerige AB
Skalholtsgatan 9, Kista
P.O. Box 19
5.16393 SPANGA
Tel: (08) 750-2000
Telex: (854) 17886
Telefax: (08) 7527781
A,C,CM,E,M,P

Hewtett-Packard SVerige AB
Box 266
Topasgatan 1A
8.42123 ViSTRA-FR6LUNDA
Hewlett-Packard So Africa (Pty.) Ltd. (Gothenburg)
Private Bag Wendywood
Tel: 46-031-89-1000
SANDTON 2144
Telex: (854) 17886 (via SpAnga
Tel: 27-11-802-5111, 27-11-802-5125 office)
Telex: 4-208n SA
A,C,CM,E,M,P
Cable: HEWPACK Johannesburg
SUDAN
A,C,CM,E,M,P
Mediterranean Engineering
SPAIN
&Trading Co. ltd.
Hewtett-Packard Espailola, S.A.
P.O. Box 1025
Calle Entenza. 321
KHARTOUM
E.-8ARCELONA 29
Tel: 41184
Tef: 3/322 24 51, 321 7354
Tetex: 24052
Tetex: 52603 hpbee
C,P
A,C,E.M,P
Hewlett-Packard EspaftoIa. S.A.
Calle san Vicente SIN
Edlflclo Albia 11-78
48001R8AO
Tef: 4/423 83 06
A,C,E.M
Hewlett-Packard EspaftoIa, S.A.
Crta. N-VI, Km. 16, 400
Las Rozas
E-IIADRID
Tel: (1) 637.00.11
Tetex: 23515 HPE
C,M

SWITZERLAND
Hewlett-Packard (SChweiz) AG
Clarastrasse 12
CH-4058IAIEL
Tef: 41-61-33-5920
A,C,E.P
Hewtett-Packard (SChweiz) AG
7, rue du Bois-du-Lan
case postale 365-1366
CH-12171EYR1N 1
Tel: (0041) 22-83-11-11
Tetex:27333 HPAG CH
A,C,CM,E,M,P

SALES & SUPPORT OFFICES ~
Arranged alphabetically by country

SWITZERLAND (Cont'd) TOGO
Hewlett-Packard (SChweiZ) AG
Allmend 2
CH-8967 WIDEN
Tel: 41-57-31-2111
Telex: 53933 hpag ch
Cable: HPAG CH
A.C.CM,E,M.P
Hewlett-Packard (Schweiz) AG
Schwamendlngenstrasse 10
CH·8050 ZURICH
Tel: 41·1·315-8181
Telex: 823 537 HPAG CH
C.p

SYRIA
General Electronic Inc.
Nun Basha Ahnaf Ebn Kays Street
P.O. Box 5781
DAMASCUS
Tel: 33-24-87
Telex: 44·19-88
Cable: ELECTROBOR DAMASCUS
E
Middle East Electronics
P.O.Box 2308
Abu Rumanth
DAMASCUS
T.: 33 4592
Telex: 411 771 Meesy

TAIWAN
Hewlett-Packard Taiwan Ltd.
THM Office
2. Huan Nan Road
CHUNG U. Taoyuan
Tel: (034) 929-666

C
Hewlett-Packard Taiwan Ltd.
Kaohsiung Office
11/F, 456. Chung Hsiao 1st Road

KAOHSIUNG
T.: (07) 2412318
C,E
Hewlett·Packard Taiwan Ltd.
8th Floor. Hewlett·Packard Building
337 Fu, Hsing North Road
TAIPEI
T.: (02) 712-0404
Telex: 24439 HEWPACK
Cable:HEWPACK Taipei
A.C.CM.E.M.P
Ing Lih Trading Co.
3rd Floor, No.7, Sect. 2
Jen Ai Road
TAIPEI 100
Tel: (02) 394-8191
Telex: 22894 SANKWANG
A

Societe Africaine De Promotion
Immeuble Sageb
Rue d'Atakpame
P.O. Box 4150
LOME
Tel: 21·62·88
Telex: 5357
P

TRINIDAD & TOBAGO
Caribbean Telecoms Ltd.
Corner McAllister Street &
Eastern Main Road. Laventille
P.O. Box 732
PORT-oF-SPAIN
Tel: 624-4213
Telex: 22561 CARTEL WG
Cable: CARTEL. PORT OF SPAIN
CM.E.M.P
Computer and Controls Ltd.
P.O. Box 51
1Taylor Street
PORT-oF·SPAIN
Tel: (809) 622·7719/622-7985
Telex: 38722798 COMCON WG
LOOGO AGENCY 1264
A,P
Feral Assoc.
8 Fitzgerald Lane
PORT-oF·SPAIN
Tel: 62·36864. 62·39255
Telex: 22432 FERALCO
Cable: FERALCO
M

TUNISIA
Tunisie Electronique S.A.R.L.
31 Avenue de la Liberte
TUNIS
Tel: 280-144
C.E,P
Tunisie Electronlque S.A.R.L.
94. Av. Jugurtha. Mutuelleville
1002 TUNiI-BEL¥lDERE
Tel: 280144
Telex: 13238
C,E.P
CoremaS.A.
1ter. Av. de Carthage
TUNIS
Tel: 253-821
Telex: 12319 CABAM TN
M

TURKEY

THAILAND

E.M.A
Medlha Eidem Sokak No. 41/6
Yenisehir
ANKARA
Tel: 319175
Telex: 42321 KTX TR
Cable: EMATRADE ANKARA
M

Unimesa Co. Ltd.
30 Patpong Ave., Suriwong
BANGKOK 5.
Tel: 235-5727. 234-0991/3
Telex: 84439 Simonco TH
Cable: UNIMESA Bangkok
A.C,E.M

Teknim Company Ltd.
Iran Caddesi No. 7
Karaklidere
ANKARA
Tel: 275800
Telex: 42155 TKNM TR
C,E

Bangkok Business Equipment Ltd.

5/:·6 Dejo Road
BANGKOK
Tel: 234-8670, 234-8671
Telex: 87699-BEQUIPT TH
Cable: BUSIQUIPT Bangkok
P

Kurt &Kurt A.S.
Mithatpasa Caddesi No. 75
Kat 4 Kizilay

ANKARA
Tel: 318875/6/7/8
Telex: 42490 MESR TR
A

Saniva Bilgisayar Sistemlen A.S.
Buyukdere Caddesi 103/6
Gayrettepe
ISTANBUL
Tel: 1673180
Telex: 26345 SANI TR
C,P
Best Inc.
Esentepe. Gazetecller Sitesl
Keskin Kalem
Sokak 6/3. Gayrettepe
ISTANBUL
Tel: 172 1328. 1733344
Telex: 42490
A

UNITED ARAB
EMIRATES
Emitac Ltd.
P.O. Box 1641
SHARJAH
Tel: 591181
Telex: 68136 EMITAC EM
Cable: EMITAC SHARJAH
E.C,M.P,A
Emitac Ltd.
P.O. Box 2711
ABU DHABI
Tel: 820419-20
Cable: EMITACH ABUDHABI
Emltac Ltd.
P.O. Box 8391
DUBAI,
Tel: 377591
Emitac Ltd.
P.O. Box 473
HAS AL KHAIMAN
Tel: 28133. 21270

UNITED KINGDOM
ENGLAND
Hewlett-Packard Ltd.
Miller House
The Ring. BRACKNELL
Berks RG12 1XN
Tel: 44/344/424-898
Telex: 848733
E
Hewlett-Packard Ltd.
Elstree House, Elstree Way
BOREHAIIWOOD, Herts WD6 1SG
Tel: 01 2075000
Telex: 8952716
C,E
Hewlett-Packard Ltd.
Oakfield House, Oakfield Grove
Clifton BRISTOL. Avon BS8 2BN
Tel: 44-272·736806
Telex: 444302
C,E,P
Hewlett-Packard Ltd.
9 Bridewell Place
LONDON EC4V 6BS
Tel: 44-01·583-6565
Telex: 298163
C.p
Hewlett-Packard Ltd.
Pontefract Road
NORMANTON, West Yorkshire WF6 1RN
Tel: 44/924/895 566
Telex: 557355
C,P

Hewlett-Packard Ltd.
The Quadrangle
106-118 Station Road
AEDHILL. Surrey RH 1 1PS
Tel: 44-737-686-55
Telex: 947234
C,E,P
Hewlett-Packard Ltd.
Avon House
435 Stratford Road
Shirley, SOLIHULL, West Midlands
B90 4BL
Tel: 44·21·745-8800
Telex: 339105
C,E,P
Hewlett-Packard Ltd.
Heathside Park Road
Cheadle Heath. Stockport
SK3 ORB, United Kingdom
Tel: 44-061-428-0828
Telex: 668068
A,C,E.M.P
Hewlett-Packard Ltd.
Harmon House
No. 1George Street
UXBRIDGE. Middlesex UX8 lYH
Tel: 895 720 20
Telex: 893134/5
C.CM,E.M,P
Hewlett-Packard Ltd.
King Street Lane
Wlnnersh. WOKINGHAM
Berkshire RG 11 5AR
Tel: 44/734/784774
Telex: 8471789
A,C,E.M.P

NOATHERNIRELAND
Hewlett-Packard (Ireland) Ltd.
Carrlckfergus Industrial Centre
75 Belfast Road, Carrickfergus
CO. ANTRIM BT38 8PM
Tel: 09603 67333
C,E
Cardiac Services Company
95A Finaghy Road South
BELFAST, BT10 OBY
Tel: 0232-625566
Telex: 747626
M

SCOTLAND
Hewlett-Packard Ltd.
1/3 Springburn Place
College Milton North
EAST KILBRIDE, G74 5NU
Tel: 041-332·6232
Talex: 779615
C.E
Hewlett-Packard Ltd.
SOUTH QUEEN.FERRY
West Lothian. EH30 9TG
Tel: 0313311188
Telex: 72682 HPSQFYG
C,CM,E,M.P

UNITED STATES
Hewlett-Packard Co.
Customer Information Center
Tel: (800) 752-0900
Hours: 6:00 AM to 5:00 PM
Pacific Time

Alabama
Hewlett-Packard Co.
2100 Riverchase center
Building 100 • Suite 118
BIRMINGHAM. AL 35244
Tel: '(205) 988-0547
A,C,M,P*
Hewlett-Packard Co.
420 Wynn Drive
HUNTSVILLE, AL 35805
Tel: (205) 830-2000
C.CM.E.M*

Alaska
Hewlett·Packard Co.
4000 Old Seward Highway
Suite 101
ANCHORAGE, AK 99503
Tel: (907) 563-8855
C,E

Arizona
Hewtett-Packard Co.
8080 Pointe Parkway West
PHOENIX, AZ 85044
Tel: (602) 273-8000
A,C.CM.E.M.P
Hewtett-Packard Co.
3400 East Britannia Dr.
Bldg. C. Suite 124
TUCSON, AZ 85706
Tel: (602) 573·7400
C.E,M--

California
Hewlett-Packard Co.
99 South Hill Dr.
BRISBANE, CA 94005
Tel: (415) 330-2500

C
Hewlett-Packard Co.
1907 North Gateway Blvd.
FRESNO, CA 93727
Tel: (209) 252-9652
C.M
Hewlett-Packard Co.
1421 S. Manhattan Av.
FULLERTON, CA 92631
Tel: (714) 999-6700
C.CM,E.M
Hewtett-Packard Co.
7408 Hollister Ave. #A
GOLETA, CA 93117
Tel: (805) 685-6100
C,E
Hewlett-Packard Co.
2525 Grand Avenue
LONG BEACH, CA 90815
Tel: (213)498-1111

C
Hewlett-Packard Co.
5651 West Manchester Ave.
LOS ANGELES, CA 90045
Tel: (213) 337-8000
Hewlett·Packard Co.
3155 Porter Drive
PALO ALTO, CA 94304
Tel: (415) 857-8000
C,E

Hewlett-Packard Co.
5725 W. Las Positas Blvd.
PLEASANTON, CA 94568
Tel: (415) 460-0282
C
Hewlett-Packard Co.
4244 So. Market Court, Suite A
SACRAMENTO, CA 95834
Tel: (916) 929-7222
A·,C,E,M
Hewlett-Packard Co.
9606 Aero Drive
SAN DIEGO, CA 92123
Tel: (619) 279-3200
C,CM,E,M
Hewlett-Packard Co.
3003 Scott Boulevard
SANTA CLARA, CA 95054
Tel: (408) 988-7000
Telex: 910-338-0586
A.C,CM.E
Hewlett-Packard Co.
2150 W. Hillcrest Dr.
THOUSAND OAKS, CA 91320
(805) 373-7000
C,CM,E

Colorado
Hewlett-Packard Co.
2945 center Green Court South
Suite A
BOULDER, CO 80301
Tel: (303) 499-6655
A,C,E
Hewlett-Packard Co.
24 Inverness Place, East
ENGLEWOOD, CO 80 112
Tel: (303) 649-5000
A,C,CM,E,M

Connecticut
Hewlett-Packard Co.
500 Sylvan Av.
BRIDGEPORT, CT 06606
Tel: (203) 371-6454
C,E
Hewlett-Packard Co.
47 Barnes Industrial Road South
WAWNGFORD, CT 06492
Tel: (203) 265-7801
A,C,CM,E,M

Florida
Hewlett-Packard Co.
2901 N.W. 62nd Street
FORT LAUDERDALE, FL 33309
Tel: (305) 973-2600
C,E,M,P·
Hewlett-Packard Co.
6800 South Point Parkway
Suite 301
JACKSONVILLE, FL 32216
Tel: (904) 636-9955
C·,M"
Hewlett-Packard Co.
255 East Drive, Suite B
MELBOURNE, FL 32901
Tel: (305) 729-0704
CM,E
Hewlett-Packard Co.
6177 Lake Ellenor Drive
ORlANDO, FL 32809
Tel: (305) 859-2900
A,C,CM,E,P·

Hewtett-Packard Co.
4700 Bayou Blvd.
Building 5
PENSACOLA, FL 32503
Tel: (904) 476-8422
A.C.M
Hewlett-Packard Co.
5550 W.ldlewlld, #150
TAMPA, FL 33614
Tet: (813) 884-3282
C.E.M,P

Iowa

Minnesota

Hewlett-Packard Co.
4070 22nd Av. SW
CEDAR RAPIDS, IA 52404
Tel: (319) 390-4250
C,E,M

Hewlett-Packard Co.
2025 W. Larpenteur Ave.
ST. PAUL, MN 55113
Tel: (612) 644-1100
A,C,CM.E,M

Hewlett-Packard Co.
4201 Corporate Dr.
WEST DES MOINES, IA 50265
Tel: (515) 224-1435
A··,C.M··

Georgia

Kansas

Hewlett-Packard Co.
2015 South Park Place
AnANTA, GA 30339
Tel: (404) 955-1500
Telex: 810-766-4890
A,C,CM.E,M,P·

Hewlett-Packard Co.
North Rock Business Park
3450 N. Rock Rd.
Suite 300
WICHITA, KS 67226
Tel: (316) 684-8491
C,E

Hewlett-Packard Co.
3607 Parkway Lane
Suite 300
NORCROSS, GA 30092
Tel: (404) 448-1894
C,E,P

Hawaii
Hewlett-Packard Co.
Pacific Tower
1001 Bishop St.
Suite 2400
HONOLUlU, HI 96813
Tet: (808) 526-1555
A,C,E,M

Idaho
Hewlett-Packard Co.
11309 Chlnden Blvd.
BOISE, 10 83714
Tet: (208) 323-2700
C

Illinois
Hewlett-Packard Co.
2205 E. Empire St.
P.O. Box 1607
BLOOMINGTON, IL 61702-1807
Tel: (309) 662-9411
A.C,E.M-·
Hewlett-Packard Co.
525 W. Monroe, #1308
CHICAGO, IL 60606
Tel: (312) 930-0010
C
Hewlett-Packard Co.
1200 East Diehl Road
NAPERVIUt IL 60566
Tel: (312) 357-8800
C
Hewtett-Packard Co.
5201 Tollview Drive
ROWNG MEADOWS, IL 60008
Tel: (312) 255-9800
Telex: 910-687-1066
A,C,CM,E,M

Kentucky
Hewlett-Packard Co.
305 N. Hurstbourne Lane,
Suite 100
LOUISVILLE, KY 40223
Tel: (502) 426-0100
A,C,M

Louisiana
Hewlett-Packard Co.
160 James Drive East
ST. ROlE, LA 70087
P.O. Box 1449
KENNER, LA 70063
Tel: (504) 467-4100
A.C,E,M,P

Maryland

Hewlett-Packard Co.
13001 Hollenberg Drive
BRIDGETON, MO 83044
Tel: (314) 344-5100
A,C,E,M

Nebraska
Hewlett-Packard
11626 Nicholas St.
OMAHA, NE 68154
Tel: (402) 493-0300
C,E,M

New Jersey
Hewlett-Packard Co.
120 W. century Road
PARAMUS, NJ 07652
Tel: (201) 265-5000
A,C,CM.E.M
Hewlett-Packard Co.
20 New England Av. West
PISCATAWAY, NJ 08854
Tel: (201) 562-6100
A,C.CM.E

NewMexlco

Hewlett-Packard Co.
3701 Koppers Street
BALTIMORE, Mo 21227
Tet: (301) 644-5800
Telex: 710-862-1943
A,C.CM,E,M

Hewlett-Packard Co.
7801 Jefferson N.E.
ALBUQUERQUE, NM 87109
Tet: (505) 823-6100
C,E,M

Hewlett-Packard Co.
2 Choke Cherry Road
ROCKVILLE, Mo 20850
Tel: (301) 948-6370
A,C,CM,E,M

Hewlett-Packard Co.
1362-e Trinity Dr.
LOS ALAMOS, NM 87544
Tel: (505) 662-6700
C.E

Massachusetts

New York

Hewtett-Packard Co.
1775 Minuteman Road
ANDOVER, MA 01810
Tel: (617) 682-1500
A.C,CM,E.M,P·

Hewlett-Packard Co.
5 Computer Drive South
ALBANY, NY 12205
Tel: (518) 458-1550
A,C,E,M

Hewlett-Packard Co.
29 Burlington Mall Rd
BURUNGTON, MA 01803-4514
Tel: (617) 270-7000
C,E

Hewlett-Packard Co.
9600 Main Street
CLARENCE, NY 14031
Tel: (716) 759-8621
C,E,M
Hewlett-Packard Co.
200 Cross Keys Office Park
FAIRPORT, NY 14450
Tet: (716) 223-9950
A,C,CM,E,M

Michigan

Hewlett-Packard Co.
11911 N. Meridian 51.
CARMEL, IN 46032
Tel: (317) 844-4100
A,C,CM,E,M

Hewlett-Packard Co.
4326 Cascade Road S.E.
GRAND RAPIDS, M149506
Tel: (616) 957-1970
C.M
Hewlett-Packard Co.
39550 Orchard Hili Place Drive
NOVl, MI 48050
Tel: (313) 349-9200
A,C,E,M

Hewlett-Packard Co.
111 E. Ludwig Road
Suite 108
FT. WAM, IN 46825
Tel: (219) 482-4283
C,E

Hewlett-Packard Co.
560 Kirts Rd.
Suite 101
TROY, MI 48084
Tel: (313) 362-5180
C

Indiana

Missouri
Hewlett-Packard Co.
1001 E. 101st Terrace Suite 120
KANSAS CITY, MO 64131-3368
Tel: (816) 941-0411
A.C.CM,E,M

Hewlett-Packard Co.
7641 Henry Clay Blvd.
UVERPOOL, NY 13088
TeJ: (315) 451-1820
A,C,CM,E,M
Hewlett-Packard Co.
No. 1Pennsylvania Plaza
55th Floor
34th Street & 7th Avenue
MOHAnAN NY 10119
Tel: (212) 971-0800
C,M-

Hewlett-Packard Co.
15 Myers Corner Rd.
Hollowbrook Park, Suite 20
WAPPINGERS FALLS, NY 12590
Tel: (914) 298-9125
CM,E
Hewlett-Packard Co.
2975 Westchester Ave
PURCHASE, NY 10577
Tel: (914) 935-6300
C,CM.E
Hewlett-Packard Co.
3 Crossways Park West
WOODBURY, NY 11797
Tel: (516) 682-7800
A,C,CM,E,M

North Carolina
Hewlett-Packard Co.
305 Gregson Dr.
CARY, NC 27511
Tel: (919) 467-6600
C,CM,E,M,P·
Hewlett-Packard Co.
9401 Arrow Point Blvd
Suite 100
CHARLOm, NC 28217
Tel: (704) 527-8780
C·
Hewlett-Packard Co.
5605 Roanne Way
GREENSBORO, NC 27420
Tel: (919) 852-1800
A,C,CM,E.M,P-

Ohio
Hewlett-Packard Co.
2717 S. Arlington Road
AKRON, OH 44312
Tel: (216) 644-2270
C,E
Hewlett-Packard Co.
4501Erskine Road
CINCINNAn, OH 45242
Tet: (513) 891-9870
C.M
Hewlett-Packard Co.
15885 Sprague Road
CLEVELAND, OH 44136
Tet: (216) 243-7300
A,C,CM,E.M
Hewlett-Packard Co.
9080 Springboro Pike
MIAMISBURG, OH 45342
Tet: (513) 433-2223
A,C,CM.E·,M
Hewlett-Packard Co.
One Maritime Plaza, 5th Floor
720 Water Street
TOLEDO,OH 43604
Tet: (419) 242-2200
C
Hewlett-Packard Co.
675 Brooksedge Blvd.
WESTERVILLE, OH 43081
Tel: (614) 891-3344
C,CM,E-

Oklahoma
Hewlett-Packard Co.
3525 N.W. 56th St.
SulteC-1oo
OKLAHOMA CITY, OK 73112
Tel: (405) 946-9499
C,E·,M

SALES & SUPPORT OFFICES
Arranged alphabetically by country

UNITED STATES
(Cont'd)
Hewlett-Packard Co.
6655 South Lewis,
Suite 105
TULSA, OK 74136
Tel: (918) 481-6700
A·· ,C,E,M·,P·

Oregon
Hewlett-Packard Co.
9255 S. W. Pioneer Court
WILSONVILLE, OR 97070
Tel: (503) 682-8000
A,C,E·,M

Pennsylvania
Hewlett-Packard Co.
Heatherwood Industrial Park
50 Dorchester Rd.
Route 22
HARRISBURG, PA 17112-2799
Tel: (717) 657-5900

C
Hewlett-Packard Co.
111 Zeta Drive
PITTSBURGH, PA 15238
Tel: (412) 782-0400
A,C,E,M
Hewlett-Packard Co.
2750 Monroe Boulevard
VALLEY FORGE, PA 19482
Tel: (215) 666-9000
A,C,CM,E,M

South Carolina
Hewlett-Packard Co.
Brookside Park, Suite 122
1Harbison Way
COLUMBIA. SC 29212
Tel: (803) 732-0400
C,M
Hewlett-Packard Co.
545 N. Pleasantburg Dr.
Suite 100
GREENVILLE, SC 29607
Tel: (803) 232-8002
C

Tennessee
Hewlett-Packard Co.
One Energy Centr. Suite 200
Pellissippi Pkwy.
KNOXVILLE. TN 37932
Tel: (615) 966-4747
A,C,E,M,P
Hewlett-Packard Co.
3070 Directors Row
Directors Square
MEMPHIS, TN 38131
Tel: (901) 346-8370
A,C,E,M
Hewlett-Packard Co.
44 Vantage Way,
Suite 160
NASHVILLE, TN 37228
Tel: (615) 255-1271
A,C,E,M,P

Texas
Hewlett-Packard Co.
1826-P Kramer Lane
AUSnN, TX 78758
Tel: (512) 835-6771
C,E,P·
Hewlett-Packard Co.
5700 Cromo Or
EL PASO, TX 79912
Tel: (915) 833-4400
C,E·,M··
Hewlett-Packard Co.
3952 Sandshell Drive
FORT WORTH, TX 76137
Tel: (817) 232-9500
C
Hewlett-Packard Co.
10535 Harwin Drive
HOUSTON, TX 77036
Tel: (713) 776-6400
A,C,E,M,P·
Hewlett-Packard Co.
3301 West Royal Lane
IRVING, TX 75063
Tel: (214) 869-3377
C,E
Hewlett-Packard Co.
109 E. Toronto, Suite 100
McALLEN, TX 78501
Tel: (512) 630-3030

Hewlett-Packard Co.
Tanglewood West Bldg.
Suite 240
3959 Electric Road
ROANOKE, VA 24018
Tel: (703) 774-3444
C,E,P

Hewlett-Packard de Venezuela, C.A.
Centro Ciudad Comercial Tamanaco
Nlvel C-2 (Nueva Etapa)
Local 53H05
Chuao, CARACAS
Tel: 928291
P

Washington

Albis Venezolana S.R.L.
Av. Las Marias, Ota. AUx,
EI Pedregal
Apartado 81025
CARACAS1080A
Tel: 747984, 742146
Telex: 24009 ALBIS VC
A
Tecnologica Medica del Caribe, C.A.
Multicentro Empresarlal del Este
Ave. Libertador
Edif. Libertador
Nucleo "Ctl - Oficina 51·52
CARACAS
Tel: 339867/333780
M

Hewlett-Packard Co.
15815 S.E. 37th Street
BELLEVUE, WA 98006
Tel: (206) 643-4004
A,C,CM,E,M
Hewlett-Packard Co.
1225 Argonne Rd
SPOKANE, WA 99212
Tel: (509) 922-7000
C

West Virginia
Hewlett-Packard Co.
501 56th Street
CHARLESTON. WV 25304
Tel: (304) 925-0492
A,C,M

Wisconsin
Hewlett-Packard Co.
275 N. Corporate Or.
BROOKFIELD, WI 53005
Tel: (414) 784-8800
A,C,E·,M

URUGUAY

Hewlett-Packard Co.
930 E. Campbell Rd.
RICHARDSON, TX 75081
Tel: (214) 231-6101
A,C,CM,E,M,P·

Pablo Ferrando S.A.C. e I.
Avenida Italla 2877
Casma de Correo 370
MONTEVIDEO
Tel: 59-82-802-586
Telex: 398802586
A,CM,E,M

Hewlett-Packard Co.
1020 central Parkway South
SAN ANTONIO, TX 78232
Tel: (512) 494-9336
A,C,E,M,P·

Utah
Hewlett-Packard Co.
3530 W. 2100 South St.
SALT LAKE CITY, UT 84119
Tel: (801) 974-1700
A,C,E,M

Virginia
Hewlett-Packard Co.
840 Greenbrier Circle
Suite 101
CHESAPEAKE, VA 23320
Tel: (804) 424-7105
C,E,M
Hewlett-Packard Co.
4305 Cox Road
GLEN ALLEN, VA 23060
Tel: (804) 747-7750
A,C,E,M,P·

Olympia de Uruguay S.A.
Maquines de Oficina
Avda. del Libertador 1997
Casilla de Correos 6644
MONTEVIDEO
Tel: 91-1809, 98-3807
Telex: 6342 OROU UY

VENEZUELA
Hewlett-Packard de Venezuela C.A.
3A Transversal Los Ruices Norte
Edificio Segre 2 & 3
Apartado 50933
CARACAS 1050
Tel: (582) 239-4133
Telex: 251046 HEWPACK
A,C,CM,E,M,P

Hewlett-Packard de Venezuela C.A.
Residencias Tia Betty local 1
Avenida 3 y con Calle 75
MARACAIBO, Estado ZUlia
Apartado 2646
Tel: 58-2-617-5669
Telex: 62464 HPMAR
C,E·
Hewlett-Packard de Venezuela C.A.
Urb. Lomas de Este
Torre Trebol - Piso 11
VALENCIA, Estado Carabobo
Apartado 3347
Tel: (5841) 222992
C,P

YUGOSLAVIA
00 Hermes
General Zdanova 4
YU-11000 BEOGRAD
Tel: (011) 342641
Telex: 11433
A,C,E,M,P

00 Hermes
Celovska 73
YU-61000 UUBUANA
Tel: (061) 553 170
Telex: 31583
A,C,E,M,P
Elektrotehna
Titova 51
YU-61000 UUIUANA
CM
00 Hermes
Kralja Tomislava 1
YU-71000 SARAJEVO
Tel: (071) 35859
Telex: 41634

CU,P

ZAIRE
Computer & Industrial Engineering
25, Avenue dela Justice
B.P.12797
KINSHASA. Gombe
Tel: 32063
Telex: 21552
C,P

ZAMBIA
R.J. Tilbury (zambia) Ltd.
P.O. Box 32792
LUSAKA
Tel: 215590
Telex: 40128

ZIMBABWE
Field Technical Sales (Private) Limited
45, Kelvin Road North
P.O. Box 3458
SAU88URY
Tel: 705 231
Tatex: 4-122 RH
E,P
September 1987

G
9

~. .

Part No. 32344-90002
Printed in U.S.A. 05/87

EOS8?

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.6
Linearized                      : No
XMP Toolkit                     : Adobe XMP Core 4.0-c321 44.398116, Tue Aug 04 2009 14:24:30
Modify Date                     : 2013:06:26 15:46:02-07:00
Create Date                     : 2013:06:24 12:46:43-07:00
Metadata Date                   : 2013:06:26 15:46:02-07:00
Creator Tool                    : ScanSnap Manager #S1500M
Format                          : application/pdf
Document ID                     : uuid:7ca1a546-9304-f04c-8b22-12ab774b1fbd
Instance ID                     : uuid:184e6933-1b02-a84e-8975-a98fcbf017c9
Producer                        : Adobe Acrobat 8.31 Paper Capture Plug-in
Page Count                      : 524
Creator                         : ScanSnap Manager #S1500M

EXIF Metadata provided by EXIF.tools

32344 90002 NS3000 V Network Manager Reference Manual Vol1 May1987

32344-90002_NS3000_V_Network_Manager_Reference_Manual_Vol1_May1987 32344-90002_NS3000_V_Network_Manager_Reference_Manual_Vol1_May1987

32344-90002_NS3000_V_Network_Manager_Reference_Manual_Vol1_May1987 32344-90002_NS3000_V_Network_Manager_Reference_Manual_Vol1_May1987

Navigation menu

Versions of this User Manual:

Views

Navigation