HP 3000/iX Network Planning and Configuration Guide

HP 3000/iX Network Planning and Configuration Guide
HP 3000/iX Network Planning and
Configuration Guide
HP 3000 MPE/iX Computer Systems
Edition 4
36922-90037
E1098
Printed in: U.S.A. October 1998
Notice
The information contained in this document is subject to change
without notice.
Hewlett-Packard makes no warranty of any kind with regard to this
material, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose. Hewlett-Packard
shall not be liable for errors contained herein or for direct, indirect,
special, incidental or consequential damages in connection with the
furnishing 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 reserved. Reproduction, adaptation, or translation
without prior written permission is prohibited, except as allowed under
the copyright laws.
Restricted Rights Legend
Use, duplication, or disclosure by the U.S. Government is subject to
restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in
Technical Data and Computer Software clause at DFARS 252.227-7013.
Rights for non-DOD U.S. Government Departments and Agencies are
as set forth in FAR 52.227-19 (c) (1,2).
Acknowledgments
UNIX is a registered trademark of The Open Group.
Hewlett-Packard Company
3000 Hanover Street
Palo Alto, CA 94304 U.S.A.
© Copyright 1991, 1992, 1994 and 1998 by Hewlett-Packard Company
Contents
1. Network Configuration Overview
Pre-Configuration Hardware Check . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Pre-Configuration Software check . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Configuration Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2. Networking Concepts
Network Environment Design Considerations . . . . . . . . . . . . . . . . . .
Line Speed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Geographical Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Special Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Shared Dial Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Non-HP 3000 Nodes (Including PCs). . . . . . . . . . . . . . . . . . . . . . .
Applicable SYSGEN Parameters . . . . . . . . . . . . . . . . . . . . . . . . . .
Dynamic Ldevs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Interface and Link Types . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Number of Network Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Priority of Network Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Subnetworks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Why Use Subnets? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How Subnetting Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assigning Subnet Masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Internetworks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Full Gateways versus Gateway Halves . . . . . . . . . . . . . . . . . . . . .
Gateway Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .
Identifying Neighbor Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . .
Neighbor Gateway Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring a Gateway Half Pair. . . . . . . . . . . . . . . . . . . . . . . . . .
Address Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Domain Name Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
When a Network Directory is Required. . . . . . . . . . . . . . . . . . . . .
Planning the Network Directory . . . . . . . . . . . . . . . . . . . . . . . . . .
Copying and Merging Network Directory Files . . . . . . . . . . . . . .
Probe and Probe Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Address Resolution Protocol (ARP) . . . . . . . . . . . . . . . . . . . . . . . . . .
Enabling Probe and ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Design Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software Configuration Maximums . . . . . . . . . . . . . . . . . . . . . . . . . . .
22
22
22
23
23
23
23
24
25
25
26
27
27
27
27
31
31
31
32
32
32
33
35
35
35
36
36
37
38
38
38
39
41
3. Planning Your Network
Drawing an Internetwork Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Communication Between Networks . . . . . . . . . . . . . . . . . . . . . . . . .
Network Boundaries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IP Network Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Completing the Internetwork Table . . . . . . . . . . . . . . . . . . . . . . . . . . .
Drawing a Network Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44
45
46
46
47
48
49
3
Contents
4
LAN Network Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Network Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Network Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Internet Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Token Ring Network Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . .
FDDI Network Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
100VG-AnyLAN Network Worksheets . . . . . . . . . . . . . . . . . . . . . . .
100Base-T Network Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Point-to-Point Network Worksheets . . . . . . . . . . . . . . . . . . . . . . . . .
Point-to-Point Network Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Point-to-Point Network Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Point-to-Point Internet Routing Table . . . . . . . . . . . . . . . . . . . . . .
X.25 Network Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
X.25 Network Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
X.25 Network Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
X.25 Internet Routing Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gateway Half Pair Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gateway Half Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gateway Half Network Interface Table . . . . . . . . . . . . . . . . . . . . .
Network Directory Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
49
49
50
51
51
51
51
51
52
52
53
53
55
55
56
56
57
57
58
59
4. Planning for Node Configuration
Node Worksheet Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Configuration Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Token Ring Configuration Worksheet . . . . . . . . . . . . . . . . . . . . . . . .
FDDI Configuration Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
100VG-AnyLAN Configuration Worksheet . . . . . . . . . . . . . . . . . . . .
100Base-T Configuration Worksheet. . . . . . . . . . . . . . . . . . . . . . . . .
Point-to-Point Configuration Worksheet . . . . . . . . . . . . . . . . . . . . . .
X.25 Configuration Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
X.25 Virtual Circuit Configuration Worksheet . . . . . . . . . . . . . . . . .
Neighbor Gateway Worksheet Information . . . . . . . . . . . . . . . . . . . . .
Neighbor Gateway Configuration Worksheet . . . . . . . . . . . . . . . . . .
Neighbor Gateway Reachable networks Worksheet Information . . . .
Neighbor Gateway Reachable Networks Configuration Worksheet
62
69
70
71
72
73
74
75
76
77
78
79
80
5. Introductory Screens
To Begin the Configuration Process . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Start NMMGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Open the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Select NS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Select Guided Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Guided/Unguided Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Perform Guided Network Transport Configuration . . . . . . . . . .
82
82
82
85
87
87
88
Contents
6. Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T
Node
To Configure a LAN Network Interface . . . . . . . . . . . . . . . . . . . . . . . . 93
To Configure a Token Ring Network Interface. . . . . . . . . . . . . . . . . . . 98
To Configure an FDDI Network Interface . . . . . . . . . . . . . . . . . . . . . 102
To Configure a 100VG-AnyLAN Network Interface . . . . . . . . . . . . . 106
To Configure a 100Base-T Network Interface . . . . . . . . . . . . . . . . . . 110
To Configure Neighbor Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
To Identify Neighbor Gateways (If Any Are Present). . . . . . . . . . . 115
To Identify Neighbor Gateway Reachable Networks . . . . . . . . . . . 117
7. Configuring a Point-to-Point Node
To Configure a Point-to-Point Network Interface . . . . . . . . . . . . . . .
To Configure Neighbor Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Identify Neighbor Gateways (If Any Are Present). . . . . . . . . . .
To Identify Neighbor Gateway Reachable Networks . . . . . . . . . . .
To Configure Node Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Select a Node Mapping Screen . . . . . . . . . . . . . . . . . . . . . . . . . .
To Configure Shared Dial Node Mapping . . . . . . . . . . . . . . . . . . . .
To Configure Direct Connect/Dial Node Mapping . . . . . . . . . . . . .
123
127
127
129
131
131
132
134
8. Configuring an X.25 Node
To Configure an X.25 Network Interface . . . . . . . . . . . . . . . . . . . . . .
To Configure X.25 Virtual Circuits . . . . . . . . . . . . . . . . . . . . . . . . .
To Configure Neighbor Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Identify Neighbor Gateways (If Any Are Present). . . . . . . . . . .
To Identify Neighbor Gateway Reachable Networks . . . . . . . . . . .
139
142
147
147
148
9. Configuring a Gateway Half
To Configure a Gatehalf Network Interface . . . . . . . . . . . . . . . . . . . . 153
10. Validating Network Transport and Cross-Validating with SYSGEN
To Validate the Network Transport . . . . . . . . . . . . . . . . . . . . . . . . . . 158
To Cross-Validate in SYSGEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
11. Configuring the Network Directory
To Open the Network Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Select the Update Directory Function . . . . . . . . . . . . . . . . . . . . . .
To Add Nodes to the Network Directory File . . . . . . . . . . . . . . . . . . .
To Configure Path Report Data for a Node. . . . . . . . . . . . . . . . . . . . .
162
164
166
169
12. Configuring Domain Name Files
To Create or Modify the Resolver File . . . . . . . . . . . . . . . . . . . . . . . . 174
To Create or Modify the Hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
5
Contents
Additional Domain Name Configuration Files. . . . . . . . . . . . . . . . . .
Network Name Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Protocol Name Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Service Name Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
178
178
178
178
13. Configuring Logging
To Access the Logging configuration Screens. . . . . . . . . . . . . . . . . . .
To Modify the Logging Configuration . . . . . . . . . . . . . . . . . . . . . . . . .
To Enable Users for Individual Logging Classes . . . . . . . . . . . . . . . .
To Activate Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
181
182
191
193
14. Operating the Network
To Start Links and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Start Software Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Start a Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Start a Host-Based X.25 Link . . . . . . . . . . . . . . . . . . . . . . . . .
To Start the Network Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Test the Network Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Shut Down the Network Services . . . . . . . . . . . . . . . . . . . . . . . . .
196
196
196
196
197
198
199
A. MPE/V to MPE/iX Migration
Differences Between NS 3000/V and NS 3000/iX . . . . . . . . . . . . . . .
Differences in the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Differences in Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . .
Differences in Applications Support . . . . . . . . . . . . . . . . . . . . . . . .
Difference in How to Obtain Status Information . . . . . . . . . . . . . .
Migration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Migration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Additional Migration Considerations . . . . . . . . . . . . . . . . . . . . . . .
File Conversion Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
When you Need to Convert Files . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Convert Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Update From a Previous MPE/iX Version . . . . . . . . . . . . . . . . .
Reconfiguration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
202
202
202
203
203
204
204
204
204
205
205
205
207
208
B. NS X.25 Migration: NS 3000/XL Releases 1.0, 1.1, or 1.2 to NS 3000/iX
Release 2.0 or Later
To Convert NS 3000/XL 1.X to 2.0 Files . . . . . . . . . . . . . . . . . . . . . . . 210
C. NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later
Differences Between NS 3000/V and NS 3000/iX . . . . . . . . . . . . . . . 212
Differences in Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Unsupported Network Connections. . . . . . . . . . . . . . . . . . . . . . . . . 212
Differences in Configuration of Terminals and Printers . . . . . . . . 212
Differences in Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Differences in Network Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
To Obtain Device Status Information . . . . . . . . . . . . . . . . . . . . . . . 213
6
Contents
Differences in X.25 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1980 Versus 1984 CCITT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General Level 3 Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Level 3 Access with NetIPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pad Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Convert NS 3000/V Files to NS 3000/iX Release 2.0 or Later . . .
To Delete Secondary NIs (NS/iX Rel. 2.2 or later) . . . . . . . . . . . . .
To Save NS 3000/V X.25 Parameters . . . . . . . . . . . . . . . . . . . . . . . . .
To Copy NS 3000/V Configuration Files to NS 3000/iX System . . . .
To Use NMMGRVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To Update X.25 XL System Access Parameters . . . . . . . . . . . . . . .
To Save X.25 XL System Access Parameters on the Host . . . . . . .
To Add Other Link Types as Needed. . . . . . . . . . . . . . . . . . . . . . . .
To Verify DTS Configuration on the Host . . . . . . . . . . . . . . . . . . . .
To Configure the DTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
214
214
214
214
215
215
216
217
217
218
219
220
220
221
221
221
222
D. NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX
Release 2.0 or later
Differences Between NS 3000/V and NS 3000/iX . . . . . . . . . . . . . . . 224
Differences in Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Unsupported Network Connections. . . . . . . . . . . . . . . . . . . . . . . . . 224
Differences in Configuration of Terminals and Printers . . . . . . . . 224
Differences in Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Differences in Network Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
To Obtain Device Status Information . . . . . . . . . . . . . . . . . . . . . . . 225
Differences in X.25 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
1980 vs. 1984 CCITT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
General Level 3 Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Level 3 Access with NetIPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
PAD Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
To Convert MPE V-Based Server Files to NS 3000/iX Release 2.0 or later
229
To Delete Secondary NIs (NS/XL Release 2.2 or later) . . . . . . . . . . . 230
To Save NS 3000/V X.25 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 231
To Copy NS 3000/V Configuration Files to NS 3000/iX System . . . . 232
To Use NMMGRVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
To Update X.25 XL System Access Parameters . . . . . . . . . . . . . . . 233
To Save X.25 XL System Access Parameters on the Host . . . . . . . 234
To Add Other Link Types as Needed. . . . . . . . . . . . . . . . . . . . . . . . 234
To Verify DTS Configuration on the Host . . . . . . . . . . . . . . . . . . . . 234
To Configure the DTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
7
Contents
E. NS X.25 Migration: NS 3000/V PAD Access to NS 3000/iX Release 2.0
or Later
Differences Between NS3000/V and NS3000/iX PAD Support . . . . . 238
To Migrate from NS 3000/V PAD Access to NS 3000/iX Release 2.0 or later
239
If You are Using Host-Based Network Management . . . . . . . . . . . 239
If You are Using PC-Based Network Management . . . . . . . . . . . . 239
To Save NS 3000/V PAD Parameters . . . . . . . . . . . . . . . . . . . . . . . 239
PAD Access Migration Categories . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Non-Nailed Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Nailed Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Configuration of Nailed Versus Non-Nailed Devices . . . . . . . . . 240
To Save DTS Parameters on the Host . . . . . . . . . . . . . . . . . . . . . . . 241
To Configure the DTC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Glossary
Index
8
Figures
Figure 2-1 . Class C Address with Subnet Number (Example 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Figure 2-2 . Class C Address with Subnet Number (Example 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Figure 2-3 . Gateway Configuration Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Figure 3-1 . Internetwork Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Figure 3-2 . LAN Network Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Figure 3-3 . Point-to-Point Network Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Figure 3-4 . X.25 Network Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Figure 3-5 . Gateway-Half Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
Figure 4-1 . LAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Figure 4-2 . Token Ring Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Figure 4-3 . FDDI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Figure 4-4 . 100VG-AnyLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Figure 4-5 . 100Base-T Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Figure 4-6 . Point-to-Point Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
Figure 4-7 . X.25 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Figure 4-8 . X.25 Virtual Circuit Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
Figure 4-9 . Neighbor Gateway Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Figure 4-10 . Reachable Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Figure 5-1 . NMMGR Screen Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Figure 5-2 . Open Configuration/Directory File Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Figure 5-3 . Main Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Figure 5-4 . NS Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Figure 5-5 . Network Transport Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Figure 6-1 . Configuring Screen Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
Figure 6-2 . LAN Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
Figure 6-3 . Token Ring Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
Figure 6-4 . FDDI Configuration Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102
Figure 6-5 . 100VG-AnyLAN Configuration Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106
Figure 6-6 . 100Base-T Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Figure 6-7 . Neighbor Gateways Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116
Figure 6-8 . Neighbor Gateway Reachable Networks Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Figure 7-1 . Point-to-Point Link Configuration Screen Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
Figure 7-2 . Point-to-Point Link Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
Figure 7-3 . Neighbor Gateway Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
Figure 7-4 . Neighbor Gateway Reachable Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129
Figure 7-5 . Shared Dial Node Mapping Configuration Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . .132
Figure 7-6 . Direct Connect/Dial Node Mapping Configuration Screen . . . . . . . . . . . . . . . . . . . . . .135
Figure 7-7 . Using an @ for Mapping Non-Adjacent Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136
Figure 8-1 . X.25 Link Screen Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137
Figure 8-2 . NS Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
Figure 8-3 . X.25 Virtual Circuit Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
Figure 8-4 . Neighbor Gateways Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148
Figure 8-5 . Neighbor Gateway Reachable Networks Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149
Figure 9-1 . Gateway Half Link Screen Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151
Figure 9-2 . Gatehalf Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153
Figure 11-1 . Network Directory Configuration Screen Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161
Figure 11-2 . Open Configuration/Directory File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162
Figure 11-3 . Network Directory Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164
Figure 11-4 . Network Directory Select Node Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
9
Figures
Figure 11-5 . Network Directory Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169
Figure 12-1 . Sample Resolver Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
Figure 12-2 . Sample Hosts Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177
Figure 13-1 . Logging Configuration Screen Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179
Figure 13-2 . Netxport Log Configuration (1) Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182
Figure 13-3 . Netxport Log Configuration (2) Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
Figure 13-4 . Netxport Log Configuration (3) Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185
Figure 13-5 . Netxport Log Configuration (4) Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186
Figure 13-6 . Netxport Log Configuration (5) Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187
Figure 13-7 . Netxport Log Configuration (6) Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189
Figure 13-8 . Logging Configuration: Class Data Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191
10
Tables
Table 2-1. Valid Addresses of Example Subnetwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Table 2-2. Configuration Maximums. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Table 3-1. Internetwork Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Table 3-2. LAN Network Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Table 3-3. LAN Internet Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Table 3-4. Point-to-Point Network Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Table 3-5. Point-to-Point Internet Routing Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Table 3-6. X.25 Network Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Table 3-7. X.25 Internet Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Table 3-8. Gateway Half Network Interface Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
Table 3-9. Network Directory Information Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Table 4-1. Configuration Worksheet Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
Table 11-1. Path Type Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172
Table 13-1. Subsystem Activation/Deactivation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193
1
Network Configuration Overview
This manual provides step-by-step instructions you can use to configure
an HP 3000 node for network communications. You can use the
information to configure an IEEE 802.3/Ethernet, Token Ring, FDDI,
100VG-AnyLAN, 100Base-T, Point-to-Point (router), or X.25 node.
Before you begin configuration, you must ensure your network is
physically set up and ready for network configuration.
This chapter provides information you should know before you begin
configuration. It tells you what preparations you must make and what
items you will be configuring.
This chapter contains the following configuration information:
• Pre-configuration hardware check.
• Pre-configuration software check.
• Configuration process overview.
17
Network Configuration Overview
Pre-Configuration Hardware Check
Pre-Configuration Hardware Check
Hardware Check Before you begin the actual configuration process,
check that the hardware components required for NS 3000/iX have
been installed and verified according to the procedures in the hardware
installation manuals listed in the preface to this guide.
18
Chapter 1
Network Configuration Overview
Pre-Configuration Software check
Pre-Configuration Software check
Once you have verified that your hardware has been correctly installed,
verify that the appropriate software is installed by performing the
following steps:
1. Ensure that the Datacommunications and Terminal Subsystem
(DTS) has been configured. If DTS has not been configured, refer to
Configuring Systems for Terminals, Printers, and Other Serial
Devices and configure the DTS before proceeding.
2. Check that the data communications software has been installed
properly by running the NMMAINT program (NMMAINT.PUB.SYS),
which is supplied as part of the node management services.
NMMAINT will tell you if any software modules are missing or
invalid. See the Using the Node Management Services (NMS)
Utilities manual for a discussion of the NMMAINT program.
3. Whenever you receive a new version of the node management
services (NMS) software (which includes NMMGR), and you have
earlier versions of NMS, you first have to run a conversion program.
The conversion program, called NMMGRVER
(NMMGRVER.PUB.SYS), ensures that configuration files created with
an earlier version of NMMGR are converted to the latest format.
Chapter 1
19
Network Configuration Overview
Configuration Process Overview
Configuration Process Overview
Configuration Process Overview. The instructions in this guide explain
how to configure each node on your network by using a “guided” branch
of Hewlett-Packard’s NMMGR configuration program. The principal
steps in this process are as follows:
1. Plan your network before you begin NMMGR. Use the worksheets
provided in Chapter 4, “Planning for Node Configuration,” to record
all the items NMMGR requires. (See Chapter 2, “Networking
Concepts,” for information on networking concepts.)
2. Configure the transport and link by using NMMGR to modify the
NMCONFIG.PUB.SYS file. The instructions for this step are contained
in this manual.
3. If the node being configured is part of an internet or is on a network
with non-HP nodes, add the path of the new node to its network
directory file. See Chapter 11, “Configuring the Network Directory,”
for information on configuring the network directory.
4. Validate the network transport. This step checks data consistency
between values entered on different NMMGR data entry screens.
Instructions for validating the network transport are located in
Chapter 10, “Validating Network Transport and Cross-Validating
with SYSGEN.”
5. Cross-validate NMCONFIG.PUB.SYS with the system configuration
files within SYSGEN. Cross-validation ensures that there are no
conflicts in the use of node names, device classes, and physical paths.
Even if validation and cross-validation were already done after
configuring DTS, you still have to validate and cross-validate again
after you configure the network transport and link. Instructions for
cross-validating are located in Chapter 10, “Validating Network
Transport and Cross-Validating with SYSGEN.”
6. Start the network (links and services) using the NETCONTROL and
NSCONTROL commands. See Chapter 14, “Operating the Network,”
for information on starting links and services.
7. Verify the configuration and network connectivity by running the
QVALNS program. See Chapter 14, “Operating the Network,” for
information on running QVALNS.
20
Chapter 1
2
Networking Concepts
Planning a network or internetwork (collection of networks) 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 internetwork:
for example, volume of usage over particular links, volume of CPU
usage of each node, physical layout needs and limitations (such as
geographical distances), and desirability of connections to
non-NS 3000/iX nodes.
This chapter provides information to help you design your network and
plan for configuration using NMMGR. The following network design
elements are discussed:
• Design considerations of the network environment.
• Network interface and link types.
• Subnetworks.
• Internetworks.
• Address resolution methods.
• Domain names.
• Network design questions.
• Probe and probe proxy.
• Address Resolution Protocol (ARP).
• Network directory.
21
Networking Concepts
Network Environment Design Considerations
Network Environment Design
Considerations
Network and internetwork design must take many factors into
consideration: the desired physical location of the computers
comprising the network, the volume of projected communications traffic
between nodes, communications traffic patterns, and the possibility of
connections to other types of nodes (such as those in a public data
network) are just some of the criteria to consider.
These factors will affect your choice of NS network type (LAN, Token
Ring, FDDI, 100VG-AnyLAN, 100Base-T, Point-to-Point, X.25) as well
as choice of specific links. They will also affect how you design your
network layout. You may want to create subnetworks within your
network by configuring IP subnet addresses. You may, on the other
hand, need to join several networks together to form an internetwork
or internet.
Line Speed
Line Speed is a measure of the rate at which data is transmitted by a
physical link (usually measured in kilobits or megabits 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.
In general, an IEEE 802.3/Ethernet LAN or Token Ring network will be
faster than a Point-to-Point or X.25 network because the bus or ring
topology provides a faster routing mechanism than a series of
Point-to-Point hops. FDDI, 100VG-AnyLAN, and 100Base-T links will
be an order of magnitude faster than LAN or Token Ring. Links using
leased lines will have a higher line speed than links using normal
telephone lines.
Consult your Hewlett-Packard 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 internet will be an important factor in deciding both the
physical topology and the link types that you should use.
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 LAN, Token Ring link, 100VG-AnyLAN, or
100Base-T.
22
Chapter 2
Networking Concepts
Network Environment Design Considerations
Another option for nodes located in the same geographic location is to
use hardwired (direct-connect) Point-to-Point links. You might wish to
use a Point-to-Point network if the distance between some nodes on the
network will be greater than the maximum distance allowed between
nodes on a LAN.
FDDI networks also offer greater distances than LAN, Token Ring,
100VG-AnyLAN, or 100Base-T networks. FDDI networks can be up to
200 kilometers in length, with nodes up to 2 kilometers apart.
If you need to connect nodes that are geographically distant (for
example, HP 3000s located in different cities) you might choose to
connect them via a dial link. For NS dial links, you can use the
Point-to-Point 3000/iX Network Link.
Finally, if you need to use satellite transmission because of 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 wish to use
the DTC/X.25 iX Network Link.
Special Cases
The following sections describe certain design requirements for special
situations, such as shared dial links, personal computers, and using
non-HP 3000 minicomputers on an NS network.
Shared Dial 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 Point-to-Point network. Any other kind of dial
link can be used for intermediate links, but shared dial links can be
used only to connect leaf nodes (that is, nodes that receive messages
targeted only for themselves, also referred to as end nodes). Second,
shared dial links cannot be used as gateway halves.
Non-HP 3000 Nodes (Including PCs)
LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T, and X.25
networks can access non-HP 3000 nodes. Point-to-Point networks must
be composed of only HP 3000s.
Applicable SYSGEN Parameters
VT terminals are not physical devices, instead they are virtual devices
created dynamically at remote logon, header entries are created for the
maximum number of VT terminals at system boot time. The exact
number of head entries created for VT terminals will depend on the
value of MAXDYNIO (which is configurable in SYSGEN).
The exact number of remote sessions which can be supported on a given
system will depend on the exact mix of jobs and sessions (remote and
local, active and inactive) on that system.
Chapter 2
23
Networking Concepts
Network Environment Design Considerations
The maximum number of concurrent processes may limit the number of
remote logons before the maximum number of dynamic I/O devices
does.
Dynamic Ldevs
This is actually a system parameter that can be configured to 999 in
SYSGEN. The default is 332, but the actual number that can be in use
may be limited by the IDD/ODD limits. VT and NS use one dynamic
ldev per remote session and one per LAN link and one per
Point-to-Point link.
NOTE
The result of having DYNAMIC IO DEVS configured too low for NS
VIRTUAL TERMINAL connections is VTERR 8 or VT INFORM 050.
Likewise the dynamic I/O device limit may be reached before the
concurrent process limit.
24
Chapter 2
Networking Concepts
Network Interface and Link Types
Network Interface and Link Types
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 determines what links can be configured for the node,
links are said to be configured underneath network interfaces.
There are nine types of network interfaces (in addition to loopback):
• LAN for IEEE 802.3 and Ethernet networks.
• Token Ring for IEEE 802.5 networks.
• FDDI for fiber optic networks.
• 100VG-AnyLAN for 100VG-AnyLAN networks.
• 100Base-T for 100Base-T networks.
• Point-to-Point for networks that use Point-to-Point routing.
• X.25 for X.25 networks.
• NS over SNA is no longer offered as a product and has been
removed from the Corporate Price List. The product is obsolete with
no plans for support.
• Gateway half for nodes that function as gateway halves.
Number of Network Interfaces
A system can have up to 12 network interfaces (NI) configured. One of
these network interfaces must be loopback. 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 LAN network interface can have only one link configured under it;
however, a single link can reach 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 Ethertwist 3000/iX
can be used for up to 50 nodes. Up to two LAN NIs can be active
at a time per system.
• A Token Ring interface can have only one link configured under it;
however, a single link can reach a large number of nodes. Token Ring
3000/iX Network Link can support up to 250 nodes per ring using
shielded twisted pair (STP) cabling at 4 or 16 Mbps and 50 nodes per
ring using unshielded twisted pair (UTP) cabling at 4 Mbps. Only
one Token Ring NI can be active at a time per system.
Chapter 2
25
Networking Concepts
Network Interface and Link Types
• An FDDI interface can have only one link configured under it;
however, a single link can reach a large number of nodes. FDDI/iX
Network Link can support up to 1000 nodes. Up to four FDDI NIs
can be active at a time per system.
• A Point-to-Point network interface can have up to 40 links
configured under it. Point-to-Point links may be dial links, in which
a modem attached to a node is used to transmit and receive data
carried across telephone wires, or leased lines, in which data is sent
over data-grade lines leased from a private carrier. Up to 11
Point-to-Point NI’s can be active at a time (one NI must be
loopback) for a total of 12 NI’s per system.
• An X.25 network interface can have from one to 11 links configured,
depending on the number of configured X.25 network interfaces on
the node. (A single node can have up to 11 NIs and up to 11 X.25
links.) Each link can be connected to as many as 1,024 remote nodes,
with communication allowed with as many as 256 nodes at the same
time. Up to 11 X.25 NI’s can be active at a time (one NI must be
loopback) for a total of 12 NI’s per system.
• 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/iX Network links. Only
one gateway half NI can be active at a time per system.
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.
Refer to “Software Configuration Maximums” at the end of this chapter
for information on configuration path maximums.
Priority of Network Interfaces
If it is possible to reach a destination through more than one active NI,
the network determines which NI to select according to the following
priority:
loopback
100VG-AnyLAN
100BASE-T
FDDI
LAN
Token Ring
X.25
Gateway Half
Point-to-Point (router)
If more than one NI of a given type is active, (for example, two X.25
NIs) the network will select the one that it finds first.
26
Chapter 2
Networking Concepts
Subnetworks
Subnetworks
IP Subnets are used to divide one network into two or more distinct
subnetworks. Subnet numbers identify subnetworks in the same way
that network addresses identify physically distinct networks.
Subnetting divides the node address portion of an IP address into two
portions—one for identifying a specific subnetwork and one for
identifying a node on that subnetwork.
Why Use Subnets?
The use of subnets is optional. Subnets are typically used in
organizations that have a large number of computers. You may want
two or more physically distinct networks to share the same network
address. This may occur, for example, if your organization has acquired
only one network number, but any of the following is true:
• A few nodes on a single network create the bulk of the network
traffic and you want to isolate those nodes on a subnetwork to reduce
overall congestion.
• You have a single LAN and have reached the limit of its technology
in terms of node numbers or cable length.
• LANs are located too far apart to be joined with bridges.
How Subnetting Works
You may use subnets to divide your current network into subnetworks
without informing remote networks about an internal change in
connectivity. A packet will be routed to the proper subnet when it
arrives at the gateway node. However, if you want a remote node to
know about only some of the subnets on your network, this must be
configured.
The network portion of an IP address must be the same for each
subnetwork of the same network. The subnet portion of an IP address
must be the same for each node on the same subnetwork.
Assigning Subnet Masks
Before you can determine subnet numbers, you first must determine
which bits of the node address will be used to contain your subnet
numbers.
The bits that you designate for subnet identifiers compose the subnet
mask. The subnet mask is configured with NMMGR. The remaining
part of the node address is used to identify the host portion of the IP
address.
Chapter 2
27
Networking Concepts
Subnetworks
The following rules apply when choosing a subnet mask and an IP
address:
• Although any bits in the node address can be used as the subnet
mask, Hewlett-Packard recommends aligning the subnet mask along
byte boundaries, adjacent to the network number.
• Although standards allow subnets on the same network to have
different subnet masks, Hewlett-Packard recommends that you
assign the same subnet mask to all subnets on a network.
• Do not assign an IP address where the network address and/or node
address bits are all off (all 0s) or all on (all 1s). Likewise, the subnet
address bits cannot be all 0s or all 1s.
To determine the subnet mask, you first need to estimate the number of
networks required and the number of nodes on each subnet. Allow
enough bits for both nodes and subnets, as described in example 1.
Example 1
Assume you are choosing a subnet mask for a class C network (three
bytes for network address, one byte for node address), and you need
four subnets with up to 30 nodes on each subnet. You will need to
reserve three bits for the subnet address (remember, all 0s and all 1s
cannot be used) and the remaining five bits for the node numbers as
shown in Figure 2-1.
Figure 2-1
Class C Address with Subnet Number (Example 1)
The 30 nodes per subnet will require at least five bits of the node
portion of the IP address (30 <32, and 32=25, therefore you need 5 bits).
This leaves three bits remaining in the node portion of the IP address
for use as the subnet identifier. Subnet parts of all 0’s or all 1’s are not
recommended because they can be confused with broadcast addresses.
Therefore, you can have up to six subnets (23 –2=6) when three bits are
used for the subnet identifier.
Example 2
An IP address on a class B network with an 8-bit subnet mask
separates as shown in Figure 2-2.
28
Chapter 2
Networking Concepts
Subnetworks
Figure 2-2
Class C Address with Subnet Number (Example 2)
Now, refer again to example 1. The subnet mask must indicate that
three bits of the node portion of the IP address will be used for the
subnet identifier. The subnet mask turns on (sets to 1) all the relevant
bits for its subnet scheme. The subnet mask for example 1 is shown
below. Note that the most significant three bits of the rightmost byte
are set.
Subnet Mask
Binary
11111111.11111111.11111111 11100000
Decimal
255.255.255 224
Table 2-1 shows valid addresses for the subnetwork in example 1. You
will need to know this information for NMMGR configuration. The
table shows the possible values of the rightmost byte of the IP address
for each of the subnets, given the criteria described in the example.
(Remember, an address of all 0s or all 1s is not valid).
Column 2 shows the values, in binary, of the six subnet addresses. Five
zeroes are shown in parentheses to indicate where the three
subnet-address bits are located in the byte. The equivalent decimal
value for each subnet address is shown in the third column. The fourth
column shows the range of possible values for the node address of each
subnet. The five rightmost bits make up the node portion, and the
range is the same for all subnets. By combining the subnet address with
the range of node addresses, the possible decimal values of the
rightmost byte are obtained and shown in the fifth column.
The table shows that subnets of 30 nodes each are possible given a
subnet mask of 255.255.255 224. This is derived from the column
that shows the range of possible values for the five bits that make up
the node portion of the IP address. The range for each of the six subnets
shows 30 possible values.
Chapter 2
29
Networking Concepts
Subnetworks
Table 2-1
Valid Addresses of Example Subnetwork
Subnet
Address of
Subnetwork in
Binary
Decimal Value of
Subnetwork
Possible Node
Address on
Subnetwork
Decimal Value
of Rightmost
Byte
1
001 (00000)
32
00001–11110
33–62
2
010 (00000)
64
00001–11110
65–94
3
011 (00000)
96
00001–11110
97–126
4
100 (00000)
128
00001–11110
129–158
5
101 (00000)
160
00001–11110
161–190
6
110 (00000)
192
00001–11110
193–222
By looking at the binary values of two IP addresses, it is easy to tell if
nodes belong to the same subnet. If they do, all the bits that make up
the subnet mask will be the same between IP addresses in the subnet.
Take, for example, two IP addresses (in decimal and in binary) of
subnet number 1 from Table 2-1:
192.6.12.41 1100 0000 0000 0110 0000 1100 0010 1001
192.6.12.55 1100 0000 0000 0110 0000 1100 0011 0111
The subnet mask has already been defined as:
255.255.255 224 1111 1111 1111 1111 1111 1111 1110 0000
Because the mask has all bits except the five rightmost bits set to 1, all
bits except the five rightmost bits must match between nodes on the
same subnet. Because the two example IP addresses from subnet 1 do
match except for their five rightmost bits, they belong to the same
subnet.
NOTE
Subnet addressing can be used in internetworks (networks with
gateways).
30
Chapter 2
Networking Concepts
Internetworks
Internetworks
Two or more networks of the same type or of different types can be
linked together to form an internetwork or internet. For example, if you
wanted to connect the nodes in a Point-to-Point network with the nodes
on a LAN, the combination of the two networks would be called an
internetwork. Creation of an internetwork allows any node on one
network to communicate with any node on another network that is part
of the same internetwork. Up to 256 individual networks can belong to
the same NS internetwork.
The divisions between the networks in an internetwork are called
network boundaries. Nodes in each network will have the same
network address (network portion of the IP address); however, each
network within the internetwork will have its own unique network
address.
The networks in an internetwork may be connected by a bridge or
router, or by HP 3000 Series 900 systems configured as gateways.
Gateways
One method of joining networks in an internetwork is by using
gateways. An HP 3000 system can have up to 14 gateways (combined
number of full gateways and gateway halves).
Full Gateways versus Gateway Halves
NS 3000/iX allows you to choose between connecting two networks with
a full gateway or connecting them with two gateway halves. A full
gateway is a node configured as a full member of two (or more)
networks for the purpose of passing information between the networks
to which it belongs. The node is considered a member of each of the
networks for which it is configured.
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/iX 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
as a full gateway.
Chapter 2
31
Networking Concepts
Internetworks
Gateway Configuration Overview
Gateway configuration includes both identifying neighbor gateways in
each node’s configuration file and configuring gateway half NIs for
nodes that will serve as one half of a gateway half pair. These tasks are
described as follows.
Identifying Neighbor Gateways
If you are including gateways in your internet configuration, you may
want to modify each node’s configuration file so that the node is aware
of all of its neighbor gateways (gateways on the same link). You
accomplish this during configuration of each network interface for
which you want to allow communications over the gateway. You will
find step-by-step instructions for identifying neighbor gateways in each
of the link configuration sections of this manual.
An alternative to identifying neighbor gateways in every node’s
configuration file is to configure a default gateway for the node.
Instructions for doing so are included in this manual.
The next pages show several examples of gateway configuration.
Neighbor Gateway Examples
When using NMMGR to configure any node, you will be entering the
identities of all the neighbor gateways into the configuration of the
node. The following examples illustrate several gateway configuration
scenarios based on the network represented in Figure 2-3.
• Example 1: The node you are configuring may be a non-gateway,
such as node D in Figure 2-3. You would need to enter the identities
of each of its neighbor gateways, in this case nodes C and E, at the
Neighbor Gateways screen. On the Neighbor Gateway Reachable
Networks screen, you would also enter the IP addresses of networks
1 and 3 as two of the configured reachable networks reachable
through gateway node C.
• Example 2: The node you are configuring may be a gateway half,
such as node E in Figure 2-3. You will still need to enter the
identities of the node’s neighbor gateways as you configure the NI (in
this case, node C is the neighbor gateway). You will also need to
configure a gateway half NI for the node, as described under
“Configuring a Gateway-Half Pair.”
• Example 3: The node you are configuring may be a full gateway,
such as nodes B and C in Figure 2-3. Though full gateways are never
actually identified as such in the configuration process, they too,
must know about the other gateways. If you were configuring
node C, you would identify nodes B and E and neighbor gateways.
32
Chapter 2
Networking Concepts
Internetworks
• Example 4: One of the gateways on your internetwork may be
designated as a default gateway, such as node C in Figure 2-3. A
default gateway is a gateway that is designated to receive any traffic
for which the network is unable to identify a destination. You must
identify the node as a default gateway in the configuration file of
each node that will access it as the default gateway. If you were
configuring node D, you would identify node C as a default gateway
by entering an at sign (@) in one of the IP address fields of the
Neighbor Gateway Reachable Networks screen. Only one gateway
may be designated as a default gateway for each node. The default
gateway must be on a LAN or Token Ring network.
Configuring a Gateway Half Pair
If you are configuring a gateway half pair, you will need to configure a
gateway half NI for each half of the gateway pair. You will find
step-by-step instructions for configuring a gateway half NI in this
manual.
In Figure 2-3, nodes E and F form a gateway half pair. When you
configure a node as a gateway half, you enter its partner’s IP address
into this gateway half ’s configuration in the Gatehalf Configuration
screen. If you were to configure node E in the figure, you would enter
the IP address of node F.
Figure 2-3
Gateway Configuration Scenarios
Chapter 2
33
Networking Concepts
Internetworks
Gateway halves require the configuration of two separate network
interfaces on each node: one for the gateway half, the other for the
network it interfaces to (for example, a LAN or Point-to-Point NI). You
will need to follow the instructions for the specific NI type, depending
on the network type) and then follow the instructions to enter
configuration items specific to the gateway half NI.
Worksheets that will aid you in planning for internetwork
communication are located in Chapter 4, “Planning for Node
Configuration.”
34
Chapter 2
Networking Concepts
Address Resolution
Address Resolution
Address resolution in NS networks refers to the mapping of node names
to IP addresses and the mapping of IP addresses to lower level
addresses (such as an X.25 address or a station address). Several
address resolution methods are available for you to use individually or
in combination with each other. You can configure these methods
according to the needs of your network.
The available address resolution methods are:
• Domain name services.
• Network directory.
• Probe (and probe proxy) (LAN, 100VG-AnyLAN, and 100Base-T
only).
• Address resolution protocol (ARP) (LAN, Token Ring, FDDI,
100VG-AnyLAN, and 100Base-T only).
Domain Name Services
The domain name services are a mechanism for resolving node names
to IP addresses. They conform to an open networking standard and will
facilitate communications between HP 3000 Series 900 systems as well
as with non-HP 3000 nodes.
To use the domain name services, you must assign a name, in
ARPANET standard format, to each system on the network or
internetwork. You configure this name on the NS Configuration screen
(see configuration chapters for details).
You will also need to create a set of ASCII files on each system which
contain the addressing information the system will need. Instructions
for creating these files are in Chapter 12, “Configuring Domain Name
Files.”
Once you have configured the domain name services, the network will
be able to access the node using its domain name and the domain name
service routines will resolve the domain name to the node’s IP address.
NOTE
Domain name services provide name to IP address resolution only. If a
lower level address is required for network communication (for
example, an X.25 address) you will need to configure the network
directory as well.
Network Directory
The network directory is a set of files that contain information used by
the node to communicate with other nodes in the internetwork.
Chapter 2
35
Networking Concepts
Address Resolution
You use NMMGR to perform the following network directory functions:
• Add, modify, and delete entries in the directory.
• Review and inspect directory information.
• Merge a remote directory with a directory on the local node.
• Automatically update directories on a group of remote nodes by
using a background stream job controlled from a central
administrative node.
See Chapter 11, “Configuring the Network Directory,” for more
information on configuring the network directory through NMMGR.
More information on merging directories and on central administrative
nodes is included in this chapter.
When a Network Directory is Required
A network directory must be configured in the following circumstances:
• nodes running on X.25
• nodes not using domain name services
• nodes on a LAN network that do not support the HP-PROBE
protocol
The network directory of a node in a Point-to-Point network must
contain the IP addresses of all other nodes that you want the node to be
able to reach.
When configuring the network directory for a Point-to-Point network,
make sure that the IP address you enter in the network directory
matches the data in the mapping screens (path name
NETXPORT.NI.NIname.MAPPING.mapentry).
For nodes on an X.25 network, the network directory maps the X.25
address key to an IP address to allow a node to communicate within the
X.25 network. You must configure a network directory for nodes using
X.25.
Planning the Network Directory
There are two theories about how network directories should be
planned and configured on a network, as follows:
• Centralized network directories.
• Decentralized network directories.
The centralized theory requires each node on the internet to have the
same network directory. This means that every node in the network
must have an entry in the network directory. The advantage to this is
36
Chapter 2
Networking Concepts
Address Resolution
that you update the network directory in one place, then copy it to the
rest of the world. The disadvantage is that network directories for large
internets are going to be large.
The recommended way to create and maintain your network directory
using the centralized method is to assign a single node as the central
administrative node. You configure the network directory on this node
and then copy it to all other nodes on the network. When the network
directory is updated, it is updated on the central administrative node,
then copied to the other nodes. This procedure decreases the possibility
of incompatible directories. You may want to assign a central
administrative node for each network or for the entire internet.
The decentralized theory suggests that each network directory be
configured individually on each node. The advantage to this is that you
can customize the network directory on each node for security purposes
using local and global entries. The network directory will also be
smaller because it will only contain entries for that particular node.
However, updates must be done manually on each node.
Copying and Merging Network Directory Files
The first time you configure the network directory, an entry for all
remote IP addresses must be added manually using the NMMGR
screens. After the first network directory is configured, you can use the
MPE STORE and RESTORE commands to copy the network directory to
other nodes. (This is assuming you have adopted the centralized
method of network directory maintenance. If you use the decentralized
method, you must always use NMMGR to create and maintain the
network directory.)
NOTE
The network directory uses a KSAM file pair. Therefore, when copying a
directory, be sure to copy both the data file and the key file. The system
names the key file automatically using the first six letters of the
network directory file name appended with a K. For example,
NSDIRK.NET.SYS is the name of the key file associated with the data
file NSDIR.NET.SYS.
Once a network directory has been established on each node in the
internet, you can set up a job stream to automate network directory
updates. The MERGEDIR command is part of a maintenance interface
provided primarily to support the updating of directories using 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. See the MERGEDIR and the MAKESTREAM
commands in Using the Node Management Services (NMS) Utilities.
Chapter 2
37
Networking Concepts
Address Resolution
Probe and Probe Proxy
NS 3000 LAN, 100VG-AnyLAN, and 100Base-T NIs with the
IEEE 802.3 protocol enabled are able to make use of a proprietary HP
protocol called probe. Probe makes it possible for nodes on an NS
IEEE 802.3 LAN, 100VG-AnyLAN, and 100Base-T to communicate
without a network directory or domain names. A node can determine
connection information about a node on the same LAN by sending a
multicast probe request out on the network. The target node recognizes
its address in the probe request and sends an individually addressed
probe reply with the necessary connection information to the
requesting node. The probe request/reply mechanism is sufficient to
obtain connection requirements within a network.
If the nodes on that LAN are to communicate with other networks, at
least one node on the network must have a network directory. The node
with the network directory is called a proxy server. By using the
probe protocol, a node without a network directory can multicast a
request for an internet address from the proxy server. For backup
purposes, you should designate at least two nodes to be proxy servers.
Address Resolution Protocol (ARP)
HP 3000 LAN, Token Ring, FDDI, 100VG-AnyLAN, AND 100Base-T
NIs are able to make use of a standard protocol called Address
Resolution Protocol (ARP). ARP provides IP address to station address
resolution. ARP is enabled when the Ethernet protocol or Token Ring is
enabled.
Enabling Probe and ARP
With the concurrent configuration of IEEE 802.3 and Ethernet on a
network, both the probe and ARP protocols are also enabled. Both
protocols broadcast requests to all nodes on the network to resolve the
address of a given remote node.
If you disable IEEE 802.3 on a LAN NI, you also disable the probe
protocol. Likewise, by disabling Ethernet, you disable the ARP protocol
associated with it. You cannot disable both of these protocols
simultaneously; at least one must be active to facilitate network
communications.
38
Chapter 2
Networking Concepts
Network Design Questions
Network Design Questions
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 550 meters of
each other?
If so, consider connecting them with ThinLAN 3000/iX links. The
maximum cable length for segments of ThinLAN 3000/iX cable is
185 meters, with a maximum of three segments connected by
repeaters.
2. Are all of the nodes in the network within roughly 1,500 meters of
each other?
If so, consider connecting them with ThickLAN (thick coaxial cable).
The maximum cable length for each segment of ThickLAN coaxial
cable is 500 meters, with a maximum of three segments connected
by repeaters.
3. Are all of the nodes in the network located within 2 kilometers of
each other?
If so, consider using FDDI/iX links. The maximum cable length for
each segment is 2 kilometers with a maximum network length of up
to 200 kilometers.
4. Are nodes located at remote sites? (For example, in different
buildings in the same city, or in different cities?)
If so, consider installing an X.25 network or a Point-to-Point 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.
5. 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 buildings or different cities)?
If so, you may wish to use ThinLAN 3000/iX, Token Ring 3000/iX,
FDDI, 100VG-AnyLAN, or 100Base-T networks for nodes that are
located near one another and Point-to-Point or X.25 links for nodes
in different buildings or cities.
6. Will HP 9000s or other minicomputers need to be part of the
network?
If so, consider ThinLAN 3000/iX (or its ThickLAN option),
Token Ring 3000/iX, FDDI/iX, 100VG-AnyLAN, 100Base-T, or
X.25/iX System Access.
Chapter 2
39
Networking Concepts
Network Design Questions
7. Do you need access to nodes on public or private X.25 networks?
If so, consider using DTC/X.25 iX Network Links.
8. 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 router. Alternatively, you may want to use subnets to
divide one network into two or more physically distinct subnetworks.
9. If you must 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.
40
Chapter 2
Networking Concepts
Software Configuration Maximums
Software Configuration Maximums
The software maximums as shown in Table 2-2, must be adhered to
when configuring a supported link. These maximums may be further
limited by the system hardware (number of available slots). Maximums
are also documented throughout the manual for the appropriate screen.
Table 2-2
Configuration Maximums
NMMGR Screen
Number/Description
Path
Maximum Limit
#9 Network Directory
Select Node Name
None
File Size Limit
#44 Point-to-Point Link
Configuration
None
40 links/Router NI
(8 per screen)
#45 Direct Connect/Dial
Node Mapping
Configuration
None
1024
Mappings/Router
#46 Shared Dial Node
Mapping Configuration
None
1024
Mappings/Router
#48 X.25 Configuration
None
11 Links/X.25 NI
#112 Network Interface
Configuration
NETXPORT.NI
12 NI/system
#117 Gateway Half NI
Links
NETXPORT.NI.NIname.LINK
1 link/Gateway
Half NI
#158 Neighbor Gateway
Reachable Networks
NETXPORT.NI.NIname.INTERNET.gatewayn
2550 networks/NI
Chapter 2
41
Networking Concepts
Software Configuration Maximums
42
Chapter 2
3
Planning Your Network
This chapter will help you to draw your network map and contains
worksheets to help you plan your network, internetwork, gateway, and
network directory configuration. You will need to consider a number of
items as you plan your configuration. This chapter provides guidelines
to help you accomplish the following:
• Draw an internetwork map.
• Complete the internetwork table.
• Draw a network map and complete network worksheets for each link
that you are configuring.
• Complete the network directory worksheet if a network directory is
required.
43
Planning Your Network
Drawing an Internetwork Map
Drawing an Internetwork Map
This section deals with the internetwork as a whole. The internetwork
worksheets consist of an internetwork map, which shows an overview of
your internetwork, and an internetwork table. You will take the
following steps when filling out the internetwork worksheets:
• Draw sketches of each network in the internetwork.
• Write network names, IP network addresses, and network types.
• Draw gateway nodes.
• Indicate network boundaries.
An internetwork map provides information about the whole
internetwork. Figure 3-1 is an example of an internetwork map. This
sample internetwork will be used throughout the instructions in this
chapter to help explain the other drawings and tables that make up the
configuration worksheets.
Before you can draw your internetwork map, you must know how many
networks your internetwork will contain, and you must know each
network type (LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T,
NS Point-to-Point, or X.25). The internetwork in the example (Figure
3-1) contains six networks. NET1 and NET5 are LANs, NET2 is a
Point-to-Point network, NET3 is an X.25 network, NET4 is a Token
Ring network, and NET6 is an FDDI network.
NOTE
If you have an X.25 network, you should indicate the presence of each
Datacomm and Terminal Controller (DTC) in your internetwork map,
as shown in this example (Figure 3-1). Both the NS 3000/iX node and
the DTC must be specially configured for X.25 links.
44
Chapter 3
Planning Your Network
Drawing an Internetwork Map
Figure 3-1
Internetwork Map
Communication Between Networks
Since the main purpose of the internetwork map is to show how
networks are connected, gateway nodes are the only nodes you should
label on the internetwork map. All other nodes and their networks can
be represented by drawing sketches of the networks, as shown in Figure
3-1. In the example, node B is a full gateway that belongs to NET1 and
NET2, node A is a full gateway that belongs to NET1 and NET4, and
node C is a full gateway that belongs to NET1 and NET6. Nodes G and
H are gateway halves that belong to NET2 and NET5, respectively.
NOTE
Single letters are used to represent node names in this example. Actual
node names must be in an accepted format. They may be either in the
form nodename.domain.organization or they may be in a valid
domain name format.
Chapter 3
45
Planning Your Network
Drawing an Internetwork Map
Network Boundaries
Once you have drawn your gateway nodes or routers, you have
established network boundaries. Consider the example and look at
Figure 3-1. Since node B in the example is a full gateway and belongs to
both NET1 and NET2, the boundary between these two networks is at
node B itself. The boundary between NET2 and NET5 is along the
gateway-half link that connects gateway nodes G and H.
IP Network Addresses
Each network in your internetwork must have a unique IP network
address. Add these IP addresses to your internetwork map.
In the example, assume that the Class C IP network addresses are
those shown in Figure 3-1. The specific IP node addresses do not need to
be shown until completion of specific parts of the network worksheets,
so node portions of IP addresses will be represented with XXX in some
maps and tables.
46
Chapter 3
Planning Your Network
Completing the Internetwork Table
Completing the Internetwork Table
Once your internetwork map contains the information just described,
you are ready to complete the internetwork table (Table 3-1).
The information requested for the first three columns of the
internetwork table can be taken directly from the internetwork map, as
in the example. In the Implementation Priority column, consider which
networks must be operational immediately. You also may want to
consider which 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 internetwork table.
When you have completed both the internetwork map and the
internetwork table, you have finished the internetwork worksheets.
Table 3-1
Internetwork Table
NETWORK
NETWORK TYPE
(LAN, PT–PT, X.25,
TOKEN RING)
IP NETWORK
ADDRESS
IMPLEMENTATION
PRIORITY
NET1
LAN
C 192.006.001 XXX
1
NET2
NS POINT-TO-POINT
C 192.006.250 XXX
2
NET3
X.25
C 192.006.001 XXX
3
NET4
TOKEN RING
C 192.006.001 XXX
4
NET5
LAN
C 192.006.001 XXX
5
NET6
FDDI
C 192.006.001 XXX
6
Chapter 3
47
Planning Your Network
Drawing a Network Map
Drawing a Network Map
A network map provides information about the configuration of the
computers on the network and their access to remote computers. A
network map can be invaluable when troubleshooting.
Whenever you install a new system on your network, be sure you also
update your network map. If you have not previously created a network
map, create one now and keep it updated whenever you add or delete
computers or interface cards or make cable changes.
In addition to maintaining a network map, you should also record
related system information on one of the network map worksheets,
provided later in this chapter. You can use the network map worksheet
as a guide for configuration and later as a record of your configuration
for both you and your HP support staff.
48
Chapter 3
Planning Your Network
Network Worksheets
Network Worksheets
For each network in your internetwork, you are asked to draw a map of
the network and to complete two tables. One table lists node-specific
information, and one table lists network routing information.
You also are asked to complete worksheets for each gateway half pair in
your internetwork. 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.
In the sample internetwork shown in Figure 3-1, six sets of network
worksheets need to be completed: one set for each of the six networks
and one set for the gateway half pair.
Take the following steps when filling out a set of network worksheets:
1. Draw your map, showing all nodes and node names. (For
Point-to-Point networks, also show all Point-to-Point links and link
names. For a gateway-half pair, include the link name.)
2. Complete the tables: two for each network, one for each gateway-half
pair.
LAN Network Worksheets
One set of LAN network worksheets should be used for each LAN in
your internetwork. 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.
In this example, we have shown the network map and worksheet for
NET1, one of the LAN networks shown in Figure 3-1. Use the
discussion of the sample LAN network worksheets as a guide for filling
out your own LAN network worksheets.
LAN Network Map
Figure 3-2 is a drawing of the network map for NET1. The network map
is a detailed drawing of the same network shown in the internetwork
map (Figure 3-1). The network name, the IP network address, and the
network type are listed at the top of the network map.
In the example, the internetwork map shows that node B is a gateway
node. It is noted on the NET1 network map and shows the network that
the gateway node can reach. Node B is also a proxy server. The
remaining NET1 nodes and their names are added to the network map.
Chapter 3
49
Planning Your Network
Network Worksheets
Figure 3-2
LAN Network Map
LAN Network Table
Refer to the LAN network map to fill in the LAN network table (Table
3-2). The first column lists the names of all the nodes on NET1. Each
node is assigned an IP address that is unique within the network. Only
the node portion of the IP address is listed since the IP network address
is noted at the top of the table. In the third column of Table 3-2, node B
is shown as a proxy server. The fourth column lists node B as a gateway
node. In the Implementation Priority column, the nodes are ranked in
the recommended order of configuration.
Table 3-2
LAN Network Table
NETWORK NAME:
NET1
IP NETWORK ADDRESS
C 192.006.001 XXX
NODE NAME
IP NODE
ADDRESS
A
001
2
L1
002
3
L2
003
4
L3
004
5
B
005
50
PROXY
SERVER (Y/N)
YES
GATEWAY
NODE (Y/N)
YES
IMPLEMENTATION
PRIORITY
1
Chapter 3
Planning Your Network
Network Worksheets
LAN Internet Routing Table
The purpose of the LAN internet routing table (Table 3-3) is to list all
possible networks that can be reached from each gateway node on a
LAN, such as NET1 in the example.
As shown on the internetwork map, NET1 includes a gateway node,
node B. In the IP Node Address column of the LAN internet routing
table, the node portion of the gateway node’s IP address is listed. The
LAN internet routing table shows that NET1 nodes using node B as a
gateway can reach NET2 in one hop, NET5 in two hops, and NET3 in
three hops. Node B is also designated as a default gateway.
Table 3-3
LAN Internet Routing Table
NETWORK NAME:
NET1
IP NETWORK ADDRESS
C 192.006.001 XXX
GATEWAY
IP NODE
ADDRESS
B
005
HOPS TO
DESTINATION
DEFAULT
GATEWAY
(Y/N)
NET2
C 192.006.250 XXX
1
YES
NET5
C 192.006.252 XXX
2
NET3
C 192.006.251 XXX
3
DESTINATION
Token Ring Network Worksheets
You may use the worksheets found in the LAN section for Token Ring.
It is important to note that Token Ring does not use a proxy server.
FDDI Network Worksheets
You may use the worksheets found in the LAN section for FDDI as well.
It is important to note that FDDI does not use a proxy server.
100VG-AnyLAN Network Worksheets
You may use the worksheets found in the LAN section for
100VG-AnyLAN.
100Base-T Network Worksheets
You may use the worksheets found in the LAN section for 100Base-T.
Chapter 3
51
Planning Your Network
Network Worksheets
Point-to-Point Network Worksheets
One set of Point-to-Point network worksheets should be used for each
Point-to-Point network in your internetwork. These network
worksheets consist of a map of the Point-to-Point network and two
tables. One table contains information about each node on the network
and one table contains network-specific internet routing information.
Point-to-Point Network Map
NET2 is the Point-to-Point network in the sample internetwork. Figure
3-3 is a drawing of the network map for NET2. The network map is a
detailed drawing of the same network shown in the internetwork map
(Figure 3-1). 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 internetwork map.
The internetwork map shows that nodes B and G are gateway nodes
and also shows the networks that the gateway nodes can reach. The
remaining NET2 nodes and their names are added to the network map.
Node G is a central administrative node.
Figure 3-3
Point-to-Point Network Map
52
Chapter 3
Planning Your Network
Network Worksheets
Point-to-Point Network Table
Refer to the Point-to-Point network map to fill in the Point-to-Point
network table (Table 3-4). We have completed the first column by listing
the names of all the nodes on NET2. Each node is assigned an IP
address that is unique within the network. Only the node portions of
the IP addresses are listed because we have listed the IP network
address at the top of the table. In the third column of Table 3-4, note
that node G is a central administrative node. In the fourth column,
nodes B and G are indicated as gateway nodes. For the Implementation
Priority column, the nodes are ranked in the recommended order of
configuration.
Table 3-4
Point-to-Point Network Table
NETWORK NAME:
NET2
IP NETWORK ADDRESS
C 192.006.250 XXX
NODE NAME
IP NODE
ADDRESS
PROXY
SERVER (Y/N)
B
001
P1
002
3
P2
003
4
P3
004
5
G
005
YES
GATEWAY
NODE (Y/N)
IMPLEMENTATION
PRIORITY
YES
2
YES
1
Point-to-Point Internet Routing Table
The purpose of the Point-to-Point internet routing table (Table 3-5) is to
list all possible networks that can be reached from each gateway node
on a Point-to-Point network, which is NET2 in the example. (Note that
there may be more than one route to a network.)
As shown on the internetwork map, NET2 includes two gateway nodes,
B and G. In the IP Node Address column of the Point-to-Point internet
routing table, the node portion of each gateway node’s IP address is
listed. The Point-to-Point internet routing table indicates that NET2
nodes using node B as a gateway can reach NET1 in one hop, NET4 in
two hops, and so on.
For Node G, the same type of information is listed.
Chapter 3
53
Planning Your Network
Network Worksheets
Table 3-5
Point-to-Point Internet Routing Table
NETWORK NAME:
NET2
IP NETWORK ADDRESS
C 192.006.250 XXX
GATEWAY
IP NODE
ADDRESS
B
001
G
005
54
DESTINATION
HOPS TO
DESTINATION
NET1
C 192.006.001 XXX
1
NET4
C 192.006.002 XXX
2
NET3
C 192.006.251 XXX
2
NET5
C 192.006.252 XXX
3
NET6
C 192.006.003 XXX
2
NET5
C 192.006.252 XXX
1
NET3
C 192.006.251 XXX
2
NET1
C 192.006.001 XXX
3
NET4
C 192.006.002 XXX
4
NET3
C 192.006.003 XXX
4
Chapter 3
Planning Your Network
Network Worksheets
X.25 Network Worksheets
One set of X.25 network worksheets should be used for each X.25
network in your internetwork. The X.25 worksheets consist of a map of
the X.25 network and two tables. One table contains information about
each node on the X.25 network. The other table contains
network-specific internet routing information.
X.25 Network Map
Figure 3-4 is a drawing of the network map for NET3. The network map
is a detailed drawing of the same network shown in the internetwork
map (Figure 3-1). The network name, the IP address, and the network
type are shown on the network map. This information is derived from
the internetwork map.
In the example, node B of NET1 and nodes H and I of NET5 are also
part of the X.25 network. The remaining NET3 nodes and their names
are added to the network map. The network map also shows node H as
a central administrative node.
Figure 3-4
X.25 Network Map
Chapter 3
55
Planning Your Network
Network Worksheets
X.25 Network Table
Refer to the X.25 network map to fill in the X.25 network table as
shown in Table 3-6. We complete the first column by listing the names
of all the nodes on NET3. Each node is assigned an IP address that is
unique within the network. Only the node portions of the IP addresses
are listed since the IP network address is listed at the top of the table.
In the third column of the table, node H is indicated as a central
administrative node. The X.25 (subnet) address for each node is listed
in the fifth column of the network table. The X.25 address is a decimal
number (up to 15 digits) identifying a node’s location on the X.25 subnet
for connections using switched virtual circuits (SVCs). Usually this
address is inserted in CALL packets to set up connections using SVCs.
If the network you will access is a public packet switching network
(PSN), these addresses (where appropriate) are recorded on the
network subscription form.
Table 3-6
X.25 Network Table
NETWORK NAME:
NET3
IP NETWORK ADDRESS
C 192.006.251 XXX
NODE NAME
IP NODE ADDRESS
CENTRAL ADMIN NODE
(Y/N)
X.25 ADDRESS
H
001
Y
1234
I
002
5678
J
003
6879
B
004
9876
X.25 Internet Routing Table
The purpose of the X.25 internet routing table (Table 3-7) is to list the
other networks in the internetwork that can be reached from the X.25
network, which is NET3 in the example. (Note that there may be more
than one route to a network.)
As shown in the internetwork map (Figure 3-4), NET3 includes two
gateway nodes, B and H. In the X.25 internet routing table note that
NET3 nodes using Node H can reach NET5 in one hop, NET2 in two
hops, and so on. In the IP Node Address column, the node portion of the
node’s IP address is listed.
56
Chapter 3
Planning Your Network
Network Worksheets
Table 3-7
X.25 Internet Routing Table
NETWORK NAME:
NET3
IP NETWORK ADDRESS
C 192.006.251 XXX
HOPS TO
DESTINATION
GATEWAY
IP NODE ADDRESS
DESTINATION
B
004
NET1
C 192.006.001 XXX
1
NET4
C 192.006.002 XXX
2
NET2
C 192.006.250 XXX
2
NET5
C 192.006.252 XXX
3
NET5
C 192.006.252 XXX
1
NET2
C 192.006.250 XXX
2
NET1
C 192.006.001 XXX
3
NET4
C 192.006.002 XXX
4
H
001
Gateway Half Pair Worksheets
One set of gateway half pair worksheets should be used for each
gateway half pair in your internetwork. 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. In the sample internetwork shown in
Figure 3-1, nodes G and H form a gateway half pair. Use the discussion
of the sample gateway half pair worksheets as a guide for filling out
your own gateway half pair worksheets.
Gateway Half Map
The sample internetwork contains one gateway half pair, as shown in
the internetwork map, which is made up of nodes G and H and their
connecting link. Figure 3-5 is a drawing of the gateway half pair
showing the two nodes and the networks to which they belong. In
addition, the map shows the link name, LINKRL1.
Chapter 3
57
Planning Your Network
Network Worksheets
Figure 3-5
Gateway-Half Map
Gateway Half Network Interface Table
Table 3-8 is based on the map discussed in the previous section. Both
gateway half nodes, the full IP addresses of the partner nodes, the
connected networks, and the name of the link are listed. Usually, the
link name will be the same from the perspective of each gateway half.
The address of the partner gateway half is shown to demonstrate that
the partner’s address is entered during configuration of a gateway half
network interface.
Table 3-8
Gateway Half Network Interface Table
NETWORK NAMES:
NET2, NET3
GATEWAY
HALF NODE
FULL IP ADDRESS
OF PARTNER
CONNECTED
NETWORK
LINK NAME
G/NET2
C 192.006.251 005
NET5
LINKRL1
H/NET5
C 192.006.252 001
NET2
LINKRL1
58
Chapter 3
Planning Your Network
Network Directory Worksheet
Network Directory Worksheet
You can complete the network directory information table shown below
for each network directory you are configuring. For your node and for
each destination node, you must make a full entry in the network
directory. The entry includes the destination node’s name and IP
address, its NI type, the global/local setting, and any additional address
that is required based on the NI type. See Chapter 11, “Configuring the
Network Directory,” for more information on NI types and additional
addresses. Table 3-9 shows some of the network directory entries you
might configure for node B of the internetwork shown in Figure 3-1.
Table 3-9
Network Directory Information Table
NODE
NAME
GLOBAL OR
LOCAL
IP ADDRESS
TYPE
H
GLOBAL
C 192.006.252 001
1
I
LOCAL
C 192.006.252 002
1
J
GLOBAL
C 192.006.251 003
3
6879
A
GLOBAL
C 192.006.001 001
5
08-00-09-11-22-11
K
GLOBAL
C 192.006.002 001
1
Chapter 3
ADDITIONAL
ADDRESS
59
Planning Your Network
Network Directory Worksheet
60
Chapter 3
4
Planning for Node Configuration
This chapter describes how to complete node worksheets before you
start configuration. You will need to collect some information ahead of
time to complete these tasks.
The main purpose of the node worksheets is to determine the
information you will need to configure for each node during NMMGR’s
guided configuration. This information depends on the type of network
you have. For a description of the fields in these worksheets, see
Chapter 6, “Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN,
100Base-T Node,” for information on LAN, Token Ring, and FDDI, and
Chapter 7, “Configuring a Point-to-Point Node,” for information on
Point-to-Point and Chapter 8, “Configuring an X.25 Node,” for
information on X.25.
It is recommended that you make copies of these worksheets and fill in
the parameter information, then use these worksheets to guide you
through configuration in NMMGR.
Node worksheets list only the fields you can configure during guided
configuration, which allows you to configure your nodes as quickly as
possible. For information on configuration parameters that are
available through non-guided configuration, see the NS 3000/iX
NMMGR Screens Reference Manual.
This chapter includes:
• Node worksheet information.
• Node worksheet information.
• Token Ring configuration worksheet
• FDDI configuration worksheet.
• 100VG-AnyLAN configuration worksheet.
• 100Base-T configuration worksheet.
• Point-to-Point configuration worksheet.
• X.25 configuration worksheet.
• X.25 virtual circuit configuration worksheet.
• Neighbor gateway worksheet information.
• Neighbor gateway configuration worksheet.
• Neighbor gateway reachable networks worksheet Information.
• Neighbor gateway reachable networks configuration worksheet.
61
Planning for Node Configuration
Node Worksheet Information
Node Worksheet Information
Table 4-1, has a description of the information that needs to be
gathered for the worksheets that are in this chapter. Check the
worksheets to see which is the appropriate information to gather. This
information is used in the configuration chapters of this manual.
Table 4-1
Configuration Worksheet Information
Field
Screen
Description
Address key
X.25 Virtual Circuit
Configuration
In the network directory, the name of
each node listed in the remote node
name field. HP recommends that you
use the node portion of the remote
node’s node name as the address key.
Card number
X.25 Configuration
Slot number of the DTC/X.25 Network
Access card.
DTC node name
X.25 Configuration
Node name of the DTC in the form
node.domain.organization. Must
agree with node name configured
through during configuration of the
datacommunications and terminal
subsystem (DTS). The node name
must be entered for each DTC/X.25
network access card that allows
system-to-system connections.
Enable ethernet/
Enable IEEE 802.3
LAN Configuration
100VG-AnyLAN Configuration
100Base-T Configuration
Both ethernet and IEEE 802.3 are
enabled by default. You may disable
one or the other but not both (one
must be enabled). To disable either
ethernet or IEEE 802.3, enter an N
(no) in the field next to the enable
question.
Facility set
X.25 Virtual Circuit
Configuration
For SVCs only. A name for a collection
of X.25 connection parameters in the
network directory. Use the default
(STDSFSET) or enter a different
name, then go to Facility sets to define
parameters. It must match the
parameters specified by your network
subscription.
62
Chapter 4
Planning for Node Configuration
Node Worksheet Information
Field
IP address
Screen
LAN Configuration;
Token Ring Configuration;
FDDI Configuration;
100VG-AnyLAN
Configuration; 100Base-T
Configuration; Point-to-Point
Configuration;
X.25 Configuration
Description
There are two methods of entering an
internet protocol (IP) address within
NMMGR:
1. Enter the fully qualified IP
address (for example, Class C,
C 192.191.191 009).
OR
2. Enter only the network (nnn)
and node (xxx) portions of the
IP address as four positive
integers between 0 and 255
separated by periods or blanks
(for example, 15.123.44.98).
You need not enter the
following items as NMMGR
will fill these in:
a. Class A, B, C
b. Leading zeros for the
network and node portion of
the IP address.
All nodes on the same network must
use the same class of IP address. The
network portion of the address must
be the same for all nodes on the same
network.
IP subnet mask
LAN Configuration;
Token Ring Configuration;
FDDI Configuration;
100VG-AnyLAN
Configuration; 100Base-T
Configuration; Point-to-Point
Configuration;
X.25 Configuration
Chapter 4
The IP subnet mask is optional. An IP
subnet mask is specified in the same
format as an IP address. The mask
identifies which bits of an IP address
will be used to define a subnetwork.
For more information refer, to the
configuration chapter for the type of
link you are configuring.
63
Planning for Node Configuration
Node Worksheet Information
Field
Screen
Link name
Description
The link name represents a hardware
interface card. This name must be
unique to both the node and the
network. The link name can have up
to eight alphanumeric characters and
the first character must be alphabetic.
(LAN Link name)
LAN Configuration
This represents the LAN card for
which you are configuring a link.
(Token Ring Link
name)
Token Ring configuration
This represents the Token Ring card
for which you are configuring a link.
(FDDI Link name)
FDDI Configuration
This represents the FDDI card for
which you are configuring a link.
(100VG-AnyLAN
Link name)
100VG-AnyLAN Configuration
This represents the 100VG-AnyLAN
card for which you are configuring a
link.
(100Base-T Link
name)
100Base-T Configuration
This represents the 100Base-T card
for which you are configuring a link.
(X.25 Link name)
X.25 Configuration
The name of the link used by X.25 iX
System Access. It must match the link
name configured during configuration
of the datacommunications and
terminal subsystem (DTS).
(Point-to-Point Link
name)
Point-to-Point Configuration
This represents the PSI card for
which you are configuring a link.
Local node name
Main
The node name is the name by which
the HP 3000 Series 900 computer is
known in the network. The format of a
node name is
nodename.domain.organization
where the total number of characters
is 50 or fewer, and each field contains
16 or fewer characters (alphanumeric,
underscore, or hyphens). The first
character of each field must be
alphabetic.
64
Chapter 4
Planning for Node Configuration
Node Worksheet Information
Field
Screen
Description
Local domain name
NS Configuration
The name of the system in ARPANET
standard format. It is composed of
labels, with each label separated by a
period. Labels must start with a letter
or digit and have as interior
characters only letters, digits,
hyphens(-), or underbars (_). There
may be any number of labels, but the
total length of the name, including
periods, is limited to 255 characters.
(If not using domain names for
network access, leave the local node
name in this field.)
Network directory
name
X.25 Virtual Circuit
Configuration
The network directory name must be
configured for each new node. The
network directory contains
information that one node needs in
order to communicate with other
nodes. The only network directory
name supported by HP is
NSDIR.NET.SYS.
Network Interface
(NI) name
LAN Configuration;
Token Ring Configuration;
FDDI Configuration;
100VG-AnyLAN
Configuration; 100Base-T
Configuration; Point-to-Point
Configuration;
X.25 Configuration
The network interface (NI) name is
used to easily identify a network
interface. The name can be up to eight
alphanumeric characters, starting
with a letter. The maximum number
of NIs that can be configured on a
node is 12. If a node interfaces to more
than one network, give each NI on
that node a unique name. You will use
the NI name with the NETCONTROL
command to start the transport and
network link.
Permanent VC
number
X.25 Virtual circuit
Configuration
For PVCs only. In the network
directory, the number of the
permanent virtual circuit on the
remote node.
Physical path
Point-to-Point Configuration
This is the location of the
programmable serial interface. Refer
to the system documentation for your
HP 3000 model to find the physical
path of the programmable serial
interface (PSI) card.
Chapter 4
65
Planning for Node Configuration
Node Worksheet Information
Field
Screen
Description
Physical path of
LANIC
LAN Configuration
This is the location of the LANIC
device adapter card. Run IOMAP
utility to determine the physical path
for the LAN adapter. Refer to the
system documentation for your HP
3000 model for further details
regarding physical path.
Physical path of
device adapter
FDDI Configuration
This is the location of the FDDI device
adapter card. Run IOMAP utility to
determine the physical path for the
FDDI adapter. Refer to the system
documentation for your HP 3000
model for further details regarding
the physical path.
Physical path of
Token Ring device
adapter
Token Ring Configuration
This is the location of the Token Ring
device adapter card. Run IOMAP
utility to determine the physical path
for the Token Ring adapter. Refer to
the system documentation for your
HP 3000 model for further details
regarding physical path.
Physical path of
device adapter
100VG-AnyLAN Configuration
This is the location of the
100VG-AnyLAN device adapter card.
Run IOMAP utility to determine the
physical path for the 100VG-AnyLAN
adapter. Refer to the system
documentation for your HP 3000
model for further details regarding
the physical path.
Link Speed
100VG-AnyLAN Configuration
This is the desired speed at which link
should operate. Valid values are 10 or
100 MBit/sec.
Full Duplex Mode
100VG-AnyLAN Configuration
If the link is operating in 10 MBit/sec,
should full duplex mode be used. This
is based on the capability of the
hub/switch to which the adapter is
connected.
Physical path of
device adapter
100Base-T Configuration
This is the location of the 100Base-T
device adapter card. Run IOMAP
utility to determine the physical path
for the 100Base-T adapter. Refer to
the system documentation for your
HP 3000 model for further details
regarding the physical path.
66
Chapter 4
Planning for Node Configuration
Node Worksheet Information
Field
Screen
Description
Use Auto-Negotiation
100Base-T Configuration
Should the adapter attempt to
auto-negotiate with the hub/switch.
Use this feature ONLY if the
hub/switch supports this feature also.
Link Speed
100Base-T Configuration
This is the desired speed at which link
should operate. Valid values are 10 or
100 MBit/sec. This field is only needed
if auto-negotiation is not used.
Full Duplex Mode
100Base-T Configuration
Should full duplex mode be used. This
is based on the capability of the
hub/switch to which the adapter is
connected. This field is only needed if
auto-negotiation is not used.
Proxy node
LAN Configuration
The proxy field is optional. Enter Y
(yes) only if your network has
internetworks (networks with
gateways) or non-HP nodes.
Establishing a proxy node is a way of
placing node name and address
mapping information in a single
location. For more information, see
the configuration chapter for LAN
link.
Remote IP address
X.25 Virtual Circuit
Configuration
In the network directory, the IP
address of each node listed in the
remote node name field.
Remote node name
X.25 Virtual Circuit
Configuration
In the network directory, the name of
each remote X.25 node on the network
Remote X.25 address
X.25 Virtual Circuit
Configuration
For SVCs only. In the network
directory, the X.25 address of the
remote host for X.25 public data
networks or private networks.
Chapter 4
67
Planning for Node Configuration
Node Worksheet Information
Field
Screen
Security class
X.25 Virtual Circuit
Configuration
For SVCs only. In the network
directory, the security to be applied for
connection establishment with the
remote node.
Speed
Point-to-Point Configuration
The line transmission speed is given
in bits per second. For direct connect
the value must be supported by the
cable. Values are 1200, 2400, 4800,
9600, 19200, 38400, 56000, and
64000. The default is 56000.
Type
Point-to-Point Configuration
Enter DD (direct dial) if you always
want to call the same host over a dial
link. If you choose DD the remote host
does not have to be adjacent and other
nodes can be accessed through the
remote host. Enter SD if you want to
call more than one adjacent remote
node over a dial link without
reconfiguring. If you choose SD, no
other remote nodes can be accessed
through the remote host; it is an end
point in the connection. Enter DC if
the link is a leased line, private line,
or other non-switched link.
68
Description
Chapter 4
Planning for Node Configuration
Node Worksheet Information
LAN Configuration Worksheet
Fill out the following worksheet (Figure 4-1) for each LAN link you are
configuring.
Figure 4-1
LAN Configuration
Chapter 4
69
Planning for Node Configuration
Node Worksheet Information
Token Ring Configuration Worksheet
Fill out the following worksheet (Figure 4-2) for each Token Ring link
you are configuring.
Figure 4-2
Token Ring Configuration
70
Chapter 4
Planning for Node Configuration
Node Worksheet Information
FDDI Configuration Worksheet
Fill out the following worksheet (Figure 4-3) for each FDDI link you are
configuring.
Figure 4-3
FDDI Configuration
Chapter 4
71
Planning for Node Configuration
Node Worksheet Information
100VG-AnyLAN Configuration Worksheet
Fill out the following worksheet (Figure 4-4) for each 100VG-AnyLAN
link you are configuring.
Figure 4-4
100VG-AnyLAN Configuration
72
Chapter 4
Planning for Node Configuration
Node Worksheet Information
100Base-T Configuration Worksheet
Fill out the following worksheet (Figure 4-5) for each 100Base-T link
you are configuring.
Figure 4-5
100Base-T Configuration
Chapter 4
73
Planning for Node Configuration
Node Worksheet Information
Point-to-Point Configuration Worksheet
Fill out the following worksheet (Figure 4-6) for each Point-to-Point link
you are configuring.
Figure 4-6
Point-to-Point Configuration
74
Chapter 4
Planning for Node Configuration
Node Worksheet Information
X.25 Configuration Worksheet
Fill out the following worksheet (Figure 4-7) for each X.25 link you are
configuring.
Figure 4-7
X.25 Configuration
Chapter 4
75
Planning for Node Configuration
Node Worksheet Information
X.25 Virtual Circuit Configuration Worksheet
Fill out the following worksheet (Figure 4-8) for each X.25 Virtual
Circuit you are configuring.
Figure 4-8
X.25 Virtual Circuit Configuration
76
Chapter 4
Planning for Node Configuration
Neighbor Gateway Worksheet Information
Neighbor Gateway Worksheet Information
The following is a description of the information that needs to be
gathered for the worksheets that follow in this chapter. This
information is used for configuring nodes.
Gateway name Enter the name of a gateway that is on the same
network as the node that you are configuring. (Nodes
are on the same network if the network portions of
their IP addresses are the same.) Each gateway name
can be as long as eight alphanumeric characters. The
first character must be alphabetic
New name
Configured
Gateways
Chapter 4
Enter the name of a gateway that is on the same
network as the node that you are configuring. (Nodes
are on the same network if the network portions of
their IP addresses are the same.) Each gateway name
can be as long as eight alphanumeric characters. The
first character must be alphabetic.
This is a list of gateways that are configured. Gateway
names are automatically entered in these fields when
they are entered above.
77
Planning for Node Configuration
Neighbor Gateway Worksheet Information
Neighbor Gateway Configuration Worksheet
Fill out the following worksheet (Figure 4-9) for each neighbor gateway
you are configuring.
Figure 4-9
Neighbor Gateway Configuration
78
Chapter 4
Planning for Node Configuration
Neighbor Gateway Reachable networks Worksheet Information
Neighbor Gateway Reachable networks
Worksheet Information
The following is a description of the information that needs to be
gathered for the worksheets that follow in this chapter. This
information is used for configuring nodes.
Neighbor
Gateway IP
Internet
Address
IP network
address
This is the IP address of the gateway specified on the
Neighbor Gateways screen. The IP address is in the
same format as the LAN Configuration screen. An
example of an address is: C 192.007.007 001
The IP addresses of all the remote networks that can be
reached through the gateway whose IP address is
configured in the previous field. If the gateway node is
to serve as a default gateway, enter an at sign (@) in one
of these fields.
IP mask
The IP mask allows you to specify a subnet mask for
each reachable network. This is in the same format as
an IP address. This mask is optional.
Hops
This is the number of hops (full gateways) that a packet
travels to reach a remote network from a local network.
Two partner gateway halves count as one hop.
Chapter 4
79
Planning for Node Configuration
Neighbor Gateway Reachable networks Worksheet Information
Neighbor Gateway Reachable Networks
Configuration Worksheet
Fill out the following worksheet (Figure 4-10) for each neighbor
gateway reachable network you are configuring.
Figure 4-10
Reachable Network Configuration
80
Chapter 4
5
Introductory Screens
The introductory screens are the first few screens that are displayed
when you configure a node using NMMGR.
Figure 5-1 shows the screen flow of the introductory screens.
[FUNCTION] denotes the function key used at a screen to invoke the
next screen on the screen flow. This chapter describes the introductory
screens relevant to configuring NS unguided networks.
Figure 5-1
NMMGR Screen Flow
81
Introductory Screens
To Begin the Configuration Process
To Begin the Configuration Process
The procedures that follow describe how to modify the NMMGR
configuration file for the introductory screens.
To Start NMMGR
Node manager (NM) or network administrator (NA) capabilities are
required to run this program.
To run NMMGR:
1. Type NMMGR.PUB.SYS at the system prompt (:).
2. Press [RETURN].
NOTE
As of version 4.0 of the operating system, you can modify the link
configurations in NMCONFIG.PUB.SYS when the Network Services
are active. However, the network must be stopped and restarted for the
changes made in NMMGR to be implemented.
If NS is down, you will see the following two messages in response to
the NETCONTROL STATUS command:
TRANSPORT NOT ACTIVE. (NETEXPORTWARN 0001) ENCOUNTERED
ONE OR MORE WARNINGS WHILE PROCESSING COMMAND.
(CIWARN 4437)
To Open the Configuration File
The Open Configuration/Directory File screen (#1) in Figure 5-2 is the
first screen displayed when you run NMMGR.
82
Chapter 5
Introductory Screens
To Begin the Configuration Process
Figure 5-2
Open Configuration/Directory File Screen
Follow the steps listed here to enter data for this screen. Refer to
“Fields” subsection for detailed information about each field on the
screen.
Step 1. Verify that the correct configuration file name, backup configuration file
name, and network directory file name are in the appropriate fields.
Step 2. If you have assigned a write access password, enter it in this field. If
you are not using the password feature, leave this field blank.
Step 3. Press the [Open Config] key. If you are creating the configuration file for
the first time, NMMGR will ask you to verify creation. Press the
[Open Config] key again to continue.
Fields
configuration
file name
The only configuration file name the system recognizes
for use by the network subsystem is
NMCONFIG.PUB.SYS. You can, however, create or
modify a configuration file using a different name and
save it as an offline configuration file. You can use
offline configuration files as a means of creating and
storing configurations that you want to use in the
future or that you are preparing for use on a different
system. When you are ready to use an offline
configuration file, rename it as NMCONFIG.PUB.SYS
and reboot the system. (Keep in mind that any file you
use as a configuration file must be successfully
validated before you try to use it.)
Chapter 5
83
Introductory Screens
To Begin the Configuration Process
Backup
configuration
file name
A backup file name must be specified whenever a
configuration file is opened or created. The default
backup configuration file name is
NMCBACK.group.account. The backup file will be
automatically updated with the contents of the
configuration file each time the configuration file is
successfully validated.
Network
directory
file name
A network directory must be configured in the following
circumstances:
• nodes running X.25
• nodes not using domain name services
• nodes on a LAN network that do not support the
HP-PROBE protocol
The only network directory file name supported by HP
is NSDIR.NET.SYS. This file is part of a KSAM pair. A
key file is created at the same time as this data file. The
key file will automatically be named using the first six
letters of the network directory file name, appended
with the character K. For example, NSDIRK.NET.SYS is
the name of the key file associated with the data file
NSDIR.NET.SYS. If the name of the data file is less
than six letters long, then the entire file name would be
appended with a K.
Write access
password
The password is an optional feature. If a password has
been assigned, you must enter it in the password field
to update the configuration file or the directory file. It is
still possible to open an existing file without using an
assigned password, but the file will be in read only
mode and NMMGR will not accept changes.
If a password has not been assigned, you should ignore
the password field.
If you want to assign a password for the system you are
configuring, see Using the Node Management Services
(NMS) Utilities.
84
Chapter 5
Introductory Screens
To Begin the Configuration Process
To Select NS Configuration
To Select NS Configuration. The Main screen (#2) in Figure 5-3 is
displayed after you create or open a configuration file by pressing the
[Open Config] key from the Open Configuration Directory File screen
(#1) in Figure 5-2.
Figure 5-3
Main Screen
NOTE
NS/SNA is no longer offered as a product and has been removed from
the Corporate Price List. The product is obsolete with no plans for
support.
Step 1. Ensure that the information in the fields on this screen is correct. If not,
or if the information has not been entered, specify the correct
information and press the [Save Data] key. (See Configuring Systems for
Terminals, Printers, and Other Serial Devices for information about
configuring the information on this screen.)
Step 2. When you are satisfied with the information as configured, press the
[NS] key to select the NS configuration branch.
Fields
Local node
name
Chapter 5
The local node name is the name by which the HP 3000
Series 900 computer is known in the network. The
format of a node name is
nodename.domain.organization where the total
number of characters is 50 or fewer, and each field
85
Introductory Screens
To Begin the Configuration Process
contains 16 or fewer characters (alphanumeric,
underscore, or hyphens). The first character of each
field must be alphabetic.
The nodename portion of each node name must be
unique within the node’s network. The
nodename.domain portion of each node name must be
unique within the internetwork. HP recommends that
all nodes on the network be assigned the same domain
and organization.
Assign meaningful node names. For example,
MKTG.BND.HP and LAB.BND.HP are meaningful names
for two nodes on the same network within
Hewlett-Packard. One node (MKTG.BND.HP) is used by
the marketing department. The other node
(LAB.BND.HP) is used by the lab. The domain field is
the same because the nodes belong to the same
network. The organization field is the same because the
nodes belong to the same internetwork.
Are you using
OpenView DTC
Manager?
If you answer yes to this question, NMMGR assumes
you are using a PC to manage your system and takes
you to the corresponding set of screens when you
configure DTS. If you answer no, NMMGR assumes you
are using host-based network management and takes
you to a different set of DTS screens. You should
already have answered this question when you
configured DTS.
Do you have X.25
systemto-system or PAD
connections? If you answer yes to this question, NMMGR assumes
you are configuring X.25 connections and takes you to
the set of screens required to configure DTC X.25
Network Access Cards when you configure DTS. If you
answer no, NMMGR assumes you have no need to
configure X.25 connections and takes you to a different
set of DTS screens. You should already have answered
this question when you configured DTS.
86
Chapter 5
Introductory Screens
To Begin the Configuration Process
To Select Guided Configuration
The NS Configuration screen (#166) in Figure 5-4 is displayed if you
press the [NS] key at the Main screen (#2) in Figure 5-3.
Figure 5-4
NS Configuration Screen
Step 1. If you are using domain names for network access, replace the node
name in the field at the bottom of the screen with this system’s domain
name and press the [Save Data] key. If not using domain names, leave
the node name as is.
Step 2. Press the [Guided Config] key to proceed with guided configuration of
LAN.
Guided/Unguided Configuration
Hewlett-Packard recommends that you press the [Guided Config] key to
select the guided configuration branch whenever you need to initially
configure a network interface. Guided configuration supplies many
default values for your configuration and requires that you visit a
minimal number of screens. This manual provides information on every
screen available to you through unguided NS configuration.
The [Unguided Config] key is used to modify configuration values that
are not available in the guided screens. To use the unguided
configuration screens, refer to the NS 3000/iX NMMGR Screens
Reference Manual.
Chapter 5
87
Introductory Screens
To Begin the Configuration Process
Fields
Local Domain
Name
The name of this system in the ARPANET standard
format. This name can be used by other nodes on the
network to access this host.
The domain name is composed of labels, with each label
separated by a period. Each label must start with a
letter or digit, and have as interior characters only
letters, digits, hyphens (-), or underbars (_). A domain
name may have any number of labels, but its total
length, including periods, is limited to 255 characters.
label[.label][...]
Domain names are not case sensitive.
Use of domain names is optional. If you are not using
domain names for network access, leave the local node
name in this field.
To Perform Guided Network Transport
Configuration
The Network Transport Configuration screen (#42) in Figure 5-5 is
displayed if you press the [Guided Config] key at the NS Configuration
screen (#166) in Figure 5-4.
Figure 5-5
Network Transport Configuration Screen
88
Chapter 5
Introductory Screens
To Begin the Configuration Process
Step 1. Next to the words Enter a network interface:, enter a name for
the selected network interface (for example, LANNI).
Step 2. Next to the words Enter a network type:, enter the selected
network type number indicated on the above screen. (For example,
enter a 1 to indicate that the NI is a LAN NI.)
Step 3. Press the [Config Network] key. (There may be a short pause before the
next screen appears.)
NOTE
NS/SNA is no longer offered as a product and has been removed from
the Corporate Price List. The product is obsolete with no plans for
support.
Step 4. Proceed to the chapter of the network interface selected above for
screen information. Refer to Chapter 6, “Configuring a LAN, Token
Ring, FDDI, 100VG-AnyLAN, 100Base-T Node,” for information on
LAN, Token Ring, FDDI, 100VG-AnyLAN, and 100Base-T; and other
chapters for information on Point-to-Point, X.25, and Gateway Half
respectively.
Fields
Enter a network
interface
The network name (NI name) is used to easily identify
one of the types of network interfaces: LAN, Token
Ring, FDDI, 100VG-AnyLAN, 100Base-T, NS
Point-to-Point, X.25 or Gateway Half. The name can be
up to eight alphanumeric characters, starting with a
letter. The maximum number of NIs that can be
configured on a node is 12. One of the 12 allowable
NIs is reserved for loopback. (Loopback is
configured for you automatically.)
If a node interfaces to more than one network, give each
NI on that node a unique name. Although all nodes on
the same network do not have to have the same NI
name, it will be easier to remember if you make the NI
name the same for all nodes on the same network (for
instance, LANNET). You will use the NI name with the
NETCONTROL command to start the transport and
network link.
Enter a
network type Number that indicates the type of network interface
you are configuring. You must enter a network type if
you are configuring a new network interface. Refer to
the following for what number to enter:
Enter 1 for a LAN NI
Enter 2 for a Point-to-Point (router) NI
Enter 3 for an X.25 NI
Chapter 5
89
Introductory Screens
To Begin the Configuration Process
Enter 4 for an SNA NI
Enter 5 for a Gateway Half NI
Enter 6 for a Token Ring NI
Enter 7 for an FDDI NI
Enter 8 for 100VG-AnyLAN
Enter 9 for 100Base-T
90
Chapter 5
6
Configuring a LAN, Token Ring,
FDDI, 100VG-AnyLAN, 100Base-T
Node
This chapter provides step-by-step instructions for configuring local
area network (LAN), Token Ring, Fiber Distributed Data Interface
(FDDI), 100VG-AnyLAN, and 100Base-T links. This manual assumes
that you are using the guided configuration capabilities of NMMGR.
Figure 6-1 shows the screen flow for configuring LAN, Token Ring,
FDDI, 100VG-AnyLAN, and 100Base-T screens. Screens unique to the
configuration of LAN, Token Ring, FDDI, 100VG-AnyLAN and
100Base-T are indicated by bold boxed screens. [FUNCTION] denotes the
function key used at a screen to invoke the next screen on the screen
flow.
Figure 6-1
Configuring Screen Flow
91
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
Before using NMMGR to configure a link, you should complete the
worksheets provided. See Chapter 4, “Planning for Node
Configuration,” for more information on planning your configuration
and filling out the configuration worksheets.
This chapter includes step-by-step instructions to help you perform the
following tasks:
• Begin the configuration process.
• Configure a LAN, Token Ring, FDDI, 100VG-AnyLAN, or 100Base-T
network interfaces.
Once the above tasks are completed, refer to Chapter 10, “Validating
Network Transport and Cross-Validating with SYSGEN,” for
step-by-step instructions to help you perform the following validation
tasks:
• Validate the network transport configuration.
• Cross-validate in SYSGEN.
92
Chapter 6
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure a LAN Network Interface
To Configure a LAN Network Interface
The LAN Configuration screen (#41) in Figure 6-2 is displayed when
you press the [Config Network] key at the Network Transport
Configuration screen (#42) with an NI type of 1 (LAN). Refer to Chapter
5, “Introductory Screens,” for information on the Network Transport
Configuration screen.
Figure 6-2
LAN Configuration Screen
Step 1. In the IP address field, enter the internet protocol (IP) address for the
node being configured. An example of an address is:
C 192.191.191 009.
Step 2. The IP subnet mask is optional. If entering one, tab to the IP subnet
mask field and enter the number in the same format as an IP address.
Step 3. The proxy node is optional. Enter Y only if your network has
internetworks (networks with gateways) or non-HP nodes and you are
not using domain name services.
Step 4. Move to the Link name field. Enter a link name to represent the LAN
card for which you are configuring a link. This name must be unique to
the node.
Step 5. Tab down to the field called Physical path of LANIC. Enter the
physical path number corresponding to the SPU slot number where the
LAN interface controller card is located.
Chapter 6
93
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure a LAN Network Interface
Step 6. Tab down to the field called Enable Ethernet (Y/N). By default,
ethernet is enabled. Change the field to N if you do not want ethernet
enabled.
Step 7. Tab down to field called Enable IEEE 802.3 (Y/N). By default,
IEEE 802.3 is enabled. Change the field to N if you do not want
IEEE 802.3 enabled.
Step 8. Press the [Save Data] key to save the LAN link configuration. If you
need to identify neighbor gateways, press the [Neighbor Gateways] key
and proceed to the section in this chapter called “To Identify Neighbor
Gateways.” Otherwise, proceed to Chapter 10, “Validating Network
Transport and Cross-Validating with SYSGEN,” and press the
[Validate Netxport] key.
Optional Keys
Press the [List NIs] key to list the names and types of
already configured network interfaces.
Press the [Delete NI] key to remove a configured network
interface from the configuration file.
Press the [Read Other NI] key to call up a previously
configured Network Interface name.
Fields
Node name
Display only.
Network
Interface NI)
name
Display only.
IP address
The IP address is an address of a node on a network. An
IP address has two parts: a network portion and a node
portion. The network portion must be the same for all
nodes on a LAN network; the node portion must be
unique for all nodes on a LAN network.
There are two methods of entering an internet protocol (IP) address
within NMMGR:
1. Enter the fully qualified IP address (for example, Class C,
C 192.191.191 009).
OR
2. Enter only the network (nnn) and node (xxx) portions of the IP
address as four positive integers between 0 and 255 separated by
periods or blanks (for example, 15.123.44.98).
You need not enter the following items as NMMGR will fill these in:
• Class A, B, C
• Leading zeros for the network and node portion of the IP address.
94
Chapter 6
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure a LAN Network Interface
HP assigns the network portion (initial nine digits) of IP addresses
from ARPA Class C, though your addresses may also be of Classes A
or B. The complete formats are:
Class
A nnn xxx.xxx.xxx
B nnn.nnn xxx.xxx
C nnn.mmm.mmm xxx
Where:
nnn = the network portion of the IP address and
xxx = the node portion of the IP address.
For Class C, the node portion of the IP address must be between 001
and 254.
If you are adding your NS 3000/iX node to an existing network, the
network portion of each node’s IP address should be the same. You will
have to find out what this is, and use it in the network portion of the IP
address of your NS 3000/iX node. Also, you will need to know the node
portions of the IP addresses of each of the nodes (usually they will be
numbered sequentially, such as 001, 002, and so on), so that you can
specify a unique node portion for the IP address of your node. If you
have a network map, it should provide a record of such items as the
node name and IP address of each node. If there is no record, and if you
want to find out each node’s IP address, you will have to issue the
following command (NM capability required) on each of the nodes:
NETCONTROL NET=NIname;STATUS
One of the lines of output from this command tells you what the
complete IP address is for that node; the last three digits are the unique
node portion of the class C address.
NOTE
To obtain a class B or C IP address, contact Government Systems,
Incorporated (GSI). To obtain an application form, write GSI at the
address below. Allow at least eight working days for GSI to process an
IP address request.
Government Systems, Inc.
Attn: Network Information Center
7990 Boeing Ct.
Vienna, VA 22183
(800) 364-3642 or FAX (703) 821-6161
IP subnet
mask
Chapter 6
An IP subnet mask is specified in the same format as
an IP address. The 32-bit mask is grouped in octets
expressed as decimal integers and delimited by either a
period (.) or a space. An IP mask is used when
95
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure a LAN Network Interface
configuring subnetworks. The mask identifies which
bits of an IP address will be used to define a
subnetwork. To determine these bits, you first need to
estimate how many subnetworks and nodes per
subnetwork you need. See Chapter 2, “Networking
Concepts,” for details on deriving an IP subnet mask.
Proxy node
Establishing a proxy node is a way of placing node
name and address mapping information in a single
location. If you are configuring an internetwork or a
network with non-HP nodes, it may be easier to update
your configurations if you have them located in a
central place, that is, the proxy node. On an
internetwork, the proxy node is usually a gateway. (It is
not necessary to configure a proxy node if you have
configured domain names. See Chapter 12,
“Configuring Domain Name Files,” for information on
domain names.)
Link name
The link name can have up to eight alphanumeric
characters and the first character must be alphabetic.
Physical Path of
LANIC
The physical path number corresponds to the slot
location of a node’s local area network interface
controller (LANIC) card. Recommended slot locations
and physical path calculations vary according to the
type of HP 3000 system you are running. If you are
unsure of the slot location or of the physical path
number to configure for your system, see your system
documentation or consult your Hewlett-Packard service
representative.
Enable Ethernet?
A Y in this field enables ethernet for the LAN. You can
enable either ethernet or IEEE 802.3 or both
simultaneously. One or the other must be enabled (both
fields may not be set to N). Ethernet is enabled by
default.
Disabling Ethernet has the effect of disabling the ARP
protocol as well and you will need to handle name to IP
address resolution by other means.
Enable
IEEE 802.3? A Y in this field enables IEEE 802.3 for the LAN. You
can enable either IEEE 802.3 or ethernet or both
simultaneously. One or the other must be enabled (both
fields may not be set to N). IEEE 802.3 is enabled by
default.
96
Chapter 6
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure a LAN Network Interface
Disabling IEEE 802.3 has the effect of disabling the
probe protocol as well and you will need to handle name
to IP address resolution by other means.
Chapter 6
97
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure a Token Ring Network Interface
To Configure a Token Ring Network
Interface
The Token Ring Configuration screen (#49) in Figure 6-3 is displayed
when you press the [Config Network] key at the Network Transport
Configuration screen (#42) with an NI type of 6 (Token Ring). Refer to
Chapter 5, “Introductory Screens,” for information on the Network
Transport Configuration screen.
Figure 6-3
Token Ring Configuration Screen
Step 1. In the IP address field, enter the internet protocol (IP) address for the
node being configured. An example of an address is
C 192.191.191 009.
Step 2. The IP subnet mask is optional. If entering one, tab to the IP subnet
mask field and enter the number in the same format as an IP address.
Step 3. Move to the Link name field. Enter a link name to represent the Token
Ring card for which you are configuring a link. This name must be
unique to the node.
Step 4. Tab down to the field called Physical Path of Token Ring Device
Adapter. Enter the physical path number corresponding to the SPU
slot number where the Token Ring device adapter is located.
98
Chapter 6
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure a Token Ring Network Interface
NOTE
If the same Token Ring card is being used for both NS and SNA
communications, you must use the same value for this field as is
configured for the SNA Link.
Step 5. Press the [Save Data] key to save the Token Ring link configuration. If
you need to identify neighbor gateways, press the [Neighbor Gateways]
key and proceed to the section in the chapter called “To Identify
Neighbor Gateways.” Otherwise, proceed to Chapter 10, “Validating
Network Transport and Cross-Validating with SYSGEN,” and press the
[Validate Netxport] key.
Optional Keys
Press the [List NIs] key to list the names and types of
already configured network interfaces.
Press the [Delete NI] key to remove a configured network
interface from the configuration file.
Press the [Read Other NI] key to call up a previously
configured Network Interface name.
Fields
Node name
Display only.
Network
Interface
(NI) name
Display only.
IP address
The IP address is an address of a node on a network. An
IP address has two parts: a network portion and a node
portion. The network portion must be the same for all
nodes on a LAN network; the node portion must be
unique for all nodes on a LAN network.
HP assigns the network portion (initial nine digits) of IP addresses
from ARPA Class C, though your addresses may also be of Classes A or
B. The complete formats are:
Class
A nnn xxx.xxx.xxx
B nnn.nnn xxx.xxx
C nnn.mmm.mmm xxx
Where:
nnn = the network portion of the IP address and
xxx = the node portion of the IP address.
For Class C, the node portion of the IP address must be between 001
and 254.
If you are adding your NS 3000/iX node to an existing network, the
network portion of each node’s IP address should be the same. You will
have to find out what this is, and use it in the network portion of the IP
Chapter 6
99
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure a Token Ring Network Interface
address of your NS 3000/iX node. Also, you will need to know the node
portions of the IP addresses of each of the nodes (usually they will be
numbered sequentially, such as 001, 002, and so on), so that you can
specify a unique node portion for the IP address of your node. If you
have a network map, it should provide a record of such items as the
node name and IP address of each node. If there is no record, and if you
want to find out each node’s IP address, you will have to issue the
following command (NM capability required) on each of the nodes:
NETCONTROL NET=NIname;STATUS
One of the lines of output from this command tells you what the
complete IP address is for that node; the last three digits are the unique
node portion of the class C address.
NOTE
To obtain a class B or C IP address, contact Government Systems,
Incorporated (GSI). To obtain an application form, write GSI at the
address below. Allow at least eight working days for GSI to process an
IP address request.
Government Systems, Inc.
Attn: Network Information Center
7990 Boeing Ct.
Vienna, VA 22183
(800) 364-3642 (703) 821-6161
IP subnet
mask
Link name
NOTE
An IP subnet mask is specified in the same format as
an IP address. The 32-bit mask is grouped in octets
expressed as decimal integers and delimited by either a
period (.) or a space. An IP mask is used when
configuring subnetworks. The mask identifies which
bits of the IP address comprise the network and
subnetwork portion.
The link name can have up to eight alphanumeric
characters and the first character must be alphabetic.
If the same Token Ring card is being used for both NS and SNA
communications, you must use the same name in this field as is
configured for the SNA Link.
Physical Path of
Device Adapter The physical path number corresponds to the slot
location of a node’s device adapter. Recommended slot
locations and physical path calculations vary according
to the type of HP 3000 system you are running. If you
are unsure of the slot location or of the physical path
number to configure for your system, see your system
documentation or consult your Hewlett-Packard service
representative.
100
Chapter 6
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure an FDDI Network Interface
To Configure an FDDI Network Interface
The FDDI Configuration screen (#201) in Figure 6-4 is displayed when
you press the [Config Network] key at the Network Transport
Configuration screen (#42) with an NI type of 7 (FDDI). Refer to
Chapter 5, “Introductory Screens,” for information on the Network
Transport Configuration screen.
Figure 6-4
FDDI Configuration Screen
Step 1. In the IP address field, enter the internet protocol (IP) address for the
node being configured. An example of an address is
C 192.191.191 009.
Step 2. The IP subnet mask is optional. If entering one, tab to the IP subnet
mask field and enter the number in the same format as an IP address.
Step 3. Move to the Link name field. Enter a link name to represent the FDDI
card for which you are configuring a link. This name must be unique to
the node.
Step 4. Tab down to the field called Physical Path of FDDI Device
Adapter. Enter the physical path number corresponding to the SPU
slot number where the FDDI device adapter is located.
Step 5. Press the [Save Data] key to save the FDDI link configuration. If you
need to identify neighbor gateways, press the [Neighbor Gateways] key
and proceed to the section in the chapter called “To Identify Neighbor
Chapter 6
101
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure an FDDI Network Interface
Gateways.” Otherwise, proceed to Chapter 10, “Validating Network
Transport and Cross-Validating with SYSGEN,” and press the
[Validate Netxport] key.
Optional Keys
Press the [List NIs] key to list the names and types of
already configured network interfaces.
Press the [Delete NI] key to remove a configured network
interface from the configuration file.
Press the [Read Other NI] key to call up a previously
configured Network Interface name.
Fields
Node name
Display only.
Network
Interface
(NI) name
Display only.
IP address
The IP address is an address of a node on a network. An
IP address has two parts: a network portion and a node
portion. The network portion must be the same for all
nodes on a FDDI network; the node portion must be
unique for all nodes on a FDDI network.
There are two methods of entering an internet protocol (IP) address
within NMMGR:
1. Enter the fully qualified IP address (for example, Class C,
C 192.191.191 009).
OR
2. Enter only the network (nnn) and node (xxx) portions of the IP
address as four positive integers between 0 and 255 separated by
periods or blanks (for example, 15.123.44.98).
You need not enter the following items as NMMGR will fill these in:
• Class A, B, C
• Leading zeros for the network and node portion of the IP address.
HP assigns the network portion (initial nine digits) of IP addresses
from ARPA Class C, though your addresses may also be of Classes A or
B. The complete formats are:
Class
102
A nnn xxx.xxx.xxx
Chapter 6
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure an FDDI Network Interface
B nnn.nnn xxx.xxx
C nnn.mmm.mmm xxx
Where:
nnn = the network portion of the IP address and
xxx = the node portion of the IP address.
For Class C, the node portion of the IP address must be between 001
and 254.
If you are adding your NS 3000/iX node to an existing network, the
network portion of each node’s IP address should be the same. You will
have to find out what this is, and use it in the network portion of the IP
address of your NS 3000/iX node. Also, you will need to know the node
portions of the IP addresses of each of the nodes (usually they will be
numbered sequentially, such as 001, 002, and so on), so that you can
specify a unique node portion for the IP address of your node. If you
have a network map, it should provide a record of such items as the
node name and IP address of each node. If there is no record, and if you
want to find out each node’s IP address, you will have to issue the
following command (NM capability required) on each of the nodes:
NETCONTROL NET=NIname;STATUS
One of the lines of output from this command tells you what the
complete IP address is for that node; the last three digits are the unique
node portion of the class C address.
NOTE
To obtain a class B or C IP address, contact Government Systems,
Incorporated (GSI). To obtain an application form, write GSI at the
address below. Allow at least eight working days for GSI to process an
IP address request.
Government Systems, Inc.
Attn: Network Information Center
14200 Park Meadow Drive
Chantilly, CA 22021
(800) 364-3642 (703) 802-4535
IP subnet
mask
Link name
Chapter 6
An IP subnet mask is specified in the same format as
an IP address. The 32-bit mask is grouped in octets
expressed as decimal integers and delimited by either a
period (.) or a space. An IP mask is used when
configuring subnetworks. The mask identifies which
bits of the IP address comprise the network and
subnetwork portion.
The link name can have up to eight alphanumeric
characters and the first character must be alphabetic.
103
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure an FDDI Network Interface
Physical Path
of FDDI
Device
Adapter
The physical path number corresponds to the slot
location of a node’s FDDI device adapter. Recommended
slot locations and physical path calculations vary
according to the type of HP 3000 system you are
running. If you are unsure of the slot location or of the
physical path number to configure for your system, see
your system documentation or consult your
Hewlett-Packard service representative.
104
Chapter 6
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure a 100VG-AnyLAN Network Interface
To Configure a 100VG-AnyLAN Network
Interface
The 100VG-AnyLAN Configuration screen (#287) in Figure 6-5 is
displayed when you press the [Config Network] key at the Network
Transport Configuration screen (#42) with an NI type of 8
(100VG-AnyLAN). Refer to Chapter 5, “Introductory Screens,” for
information on the Network Transport Configuration screen.
Figure 6-5
100VG-AnyLAN Configuration Screen
Step 1. In the IP address field, enter the internet protocol (IP) address for the
node being configured. An example of an address is:
C 192.191.191 009.
Step 2. The IP subnet mask is optional. If entering one, tab to the IP subnet
mask field and enter the number in the same format as an IP address.
Step 3. Move to the Link name field. Enter a link name to represent the
100VG-AnyLAN card for which you are configuring a link. This name
must be unique to the node.
Step 4. Tab down to the field called Physical path of device adapter.
Step 5. Press the [Save Data] key to save the 100VG-AnyLAN link
configuration. If you need to identify neighbor gateways, press the
[Neighbor Gateways] key and proceed to the section in this chapter called
Chapter 6
105
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure a 100VG-AnyLAN Network Interface
“To Identify Neighbor Gateways.” Otherwise, proceed to Chapter 10,
“Validating Network Transport and Cross-Validating with SYSGEN,”
and press the [Validate Netxport] key.
Optional Keys
Press the [List NIs] key to list the names and types of
already configured network interfaces.
Press the [Delete NI] key to remove a configured network
interface from the configuration file.
Press the [Read Other NI] key to call up a previously
configured Network Interface name.
Fields
Node name
Display only.
Network
Interface NI)
name
Display only.
IP address
The IP address is an address of a node on a network. An
IP address has two parts: a network portion and a node
portion. The network portion must be the same for all
nodes on a LAN network; the node portion must be
unique for all nodes on a LAN network.
There are two methods of entering an internet protocol (IP) address
within NMMGR:
1. Enter the fully qualified IP address (for example, Class C,
C 192.191.191 009).
OR
2. Enter only the network (nnn) and node (xxx) portions of the IP
address as four positive integers between 0 and 255 separated by
periods or blanks (for example, 15.123.44.98).
You need not enter the following items as NMMGR will fill these in:
• Class A, B, C
• Leading zeros for the network and node portion of the IP address.
HP assigns the network portion (initial nine digits) of IP addresses
from ARPA Class C, though your addresses may also be of Classes A
or B. The complete formats are:
Class
106
A nnn xxx.xxx.xxx
Chapter 6
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure a 100VG-AnyLAN Network Interface
B nnn.nnn xxx.xxx
C nnn.mmm.mmm xxx
Where:
nnn = the network portion of the IP address and
xxx = the node portion of the IP address.
For Class C, the node portion of the IP address must be between 001
and 254.
If you are adding your NS 3000/iX node to an existing network, the
network portion of each node’s IP address should be the same. You will
have to find out what this is, and use it in the network portion of the IP
address of your NS 3000/iX node. Also, you will need to know the node
portions of the IP addresses of each of the nodes (usually they will be
numbered sequentially, such as 001, 002, and so on), so that you can
specify a unique node portion for the IP address of your node. If you
have a network map, it should provide a record of such items as the
node name and IP address of each node. If there is no record, and if you
want to find out each node’s IP address, you will have to issue the
following command (NM capability required) on each of the nodes:
NETCONTROL NET=NIname;STATUS
One of the lines of output from this command tells you what the
complete IP address is for that node; the last three digits are the unique
node portion of the class C address.
NOTE
To obtain a class B or C IP address, contact Government Systems,
Incorporated (GSI). To obtain an application form, write GSI at the
address below. Allow at least eight working days for GSI to process an
IP address request.
Government Systems, Inc.
Attn: Network Information Center
7990 Boeing Ct.
Vienna, VA 22183
(800) 364-3642 (703) 821-6161
IP subnet
mask
Chapter 6
An IP subnet mask is specified in the same format as
an IP address. The 32-bit mask is grouped in octets
expressed as decimal integers and delimited by either a
period (.) or a space. An IP mask is used when
configuring subnetworks. The mask identifies which
bits of an IP address will be used to define a
subnetwork. To determine these bits, you first need to
estimate how many subnetworks and nodes per
subnetwork you need. See Chapter 2, “Networking
Concepts,” for details on deriving an IP subnet mask.
107
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure a 100VG-AnyLAN Network Interface
Proxy node
Establishing a proxy node is a way of placing node
name and address mapping information in a single
location. If you are configuring an internetwork or a
network with non-HP nodes, it may be easier to update
your configurations if you have them located in a
central place, that is, the proxy node. On an
internetwork, the proxy node is usually a gateway. (It is
not necessary to configure a proxy node if you have
configured domain names. See Chapter 12,
“Configuring Domain Name Files,” for information on
domain names.)
Link name
The link name can have up to eight alphanumeric
characters and the first character must be alphabetic.
Physical Path of
LANIC
The physical path number corresponds to the slot
location of a node’s local area network interface
controller (LANIC) card. Recommended slot locations
and physical path calculations vary according to the
type of HP 3000 system you are running. If you are
unsure of the slot location or of the physical path
number to configure for your system, see your system
documentation or consult your Hewlett-Packard service
representative.
Enable Ethernet?
A Y in this field enables ethernet for the LAN. You can
enable either ethernet or IEEE 802.3 or both
simultaneously. One or the other must be enabled (both
fields may not be set to N). Ethernet is enabled by
default.
Disabling Ethernet has the effect of disabling the ARP
protocol as well and you will need to handle name to IP
address resolution by other means.
Enable
IEEE 802.3? A Y in this field enables IEEE 802.3 for the LAN. You
can enable either IEEE 802.3 or ethernet or both
simultaneously. One or the other must be enabled (both
fields may not be set to N). IEEE 802.3 is enabled by
default.
Disabling IEEE 802.3 has the effect of disabling the
probe protocol as well and you will need to handle name
to IP address resolution by other means.
108
Chapter 6
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure a 100Base-T Network Interface
To Configure a 100Base-T Network
Interface
The 100Base-T Configuration screen (#297) in Figure 6-6 is displayed
when you press the [Config Network] key at the Network Transport
Configuration screen (#42) with an NI type of 9 (100Base-T). Refer to
Chapter 5, “Introductory Screens,” for information on the Network
Transport Configuration screen.
Figure 6-6
100Base-T Configuration Screen
Step 1. In the IP address field, enter the internet protocol (IP) address for the
node being configured. An example of an address is:
C 192.191.191 009.
Step 2. The IP subnet mask is optional. If entering one, tab to the IP subnet
mask field and enter the number in the same format as an IP address.
Step 3. The proxy node is optional. Enter Y only if your network has
internetworks (networks with gateways) or non-HP nodes and you are
not using domain name services.
Step 4. Move to the Link name field. Enter a link name to represent the LAN
card for which you are configuring a link. This name must be unique to
the node.
Step 5. Tab down to the field called Physical path of device adapter.
Chapter 6
109
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure a 100Base-T Network Interface
Step 6. Tab down to the field called Enable Ethernet (Y/N). By default,
ethernet is enabled. Change the field to N if you do not want ethernet
enabled.
Step 7. Tab down to field called Enable IEEE 802.3 (Y/N). By default,
IEEE 802.3 is enabled. Change the field to N if you do not want
IEEE 802.3 enabled.
Step 8. Press the [Save Data] key to save the LAN link configuration. If you
need to identify neighbor gateways, press the [Neighbor Gateways] key
and proceed to the section in this chapter called “To Identify Neighbor
Gateways.” Otherwise, proceed to Chapter 10, “Validating Network
Transport and Cross-Validating with SYSGEN,” and press the
[Validate Netxport] key.
Optional Keys
Press the [List NIs] key to list the names and types of
already configured network interfaces.
Press the [Delete NI] key to remove a configured network
interface from the configuration file.
Press the [Read Other NI] key to call up a previously
configured Network Interface name.
Fields
Node name
Display only.
Network
Interface NI)
name
Display only.
IP address
The IP address is an address of a node on a network. An
IP address has two parts: a network portion and a node
portion. The network portion must be the same for all
nodes on a LAN network; the node portion must be
unique for all nodes on a LAN network.
There are two methods of entering an internet protocol (IP) address
within NMMGR:
1. Enter the fully qualified IP address (for example, Class C,
C 192.191.191 009).
OR
2. Enter only the network (nnn) and node (xxx) portions of the IP
address as four positive integers between 0 and 255 separated by
periods or blanks (for example, 15.123.44.98).
You need not enter the following items as NMMGR will fill these in:
• Class A, B, C
• Leading zeros for the network and node portion of the IP address.
110
Chapter 6
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure a 100Base-T Network Interface
HP assigns the network portion (initial nine digits) of IP addresses
from ARPA Class C, though your addresses may also be of Classes A
or B. The complete formats are:
Class
A nnn xxx.xxx.xxx
B nnn.nnn xxx.xxx
C nnn.mmm.mmm xxx
Where:
nnn = the network portion of the IP address and
xxx = the node portion of the IP address.
For Class C, the node portion of the IP address must be between 001
and 254.
If you are adding your NS 3000/iX node to an existing network, the
network portion of each node’s IP address should be the same. You will
have to find out what this is, and use it in the network portion of the IP
address of your NS 3000/iX node. Also, you will need to know the node
portions of the IP addresses of each of the nodes (usually they will be
numbered sequentially, such as 001, 002, and so on), so that you can
specify a unique node portion for the IP address of your node. If you
have a network map, it should provide a record of such items as the
node name and IP address of each node. If there is no record, and if you
want to find out each node’s IP address, you will have to issue the
following command (NM capability required) on each of the nodes:
NETCONTROL NET=NIname;STATUS
One of the lines of output from this command tells you what the
complete IP address is for that node; the last three digits are the unique
node portion of the class C address.
NOTE
To obtain a class B or C IP address, contact Government Systems,
Incorporated (GSI). To obtain an application form, write GSI at the
address below. Allow at least eight working days for GSI to process an
IP address request.
Government Systems, Inc.
Attn: Network Information Center
7990 Boeing Ct.
Vienna, VA 22183
(800) 364-3642 (703) 821-6161
IP subnet
mask
Chapter 6
An IP subnet mask is specified in the same format as
an IP address. The 32-bit mask is grouped in octets
expressed as decimal integers and delimited by either a
period (.) or a space. An IP mask is used when
111
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure a 100Base-T Network Interface
configuring subnetworks. The mask identifies which
bits of an IP address will be used to define a
subnetwork. To determine these bits, you first need to
estimate how many subnetworks and nodes per
subnetwork you need. See Chapter 2, “Networking
Concepts,” for details on deriving an IP subnet mask.
Proxy node
Establishing a proxy node is a way of placing node
name and address mapping information in a single
location. If you are configuring an internetwork or a
network with non-HP nodes, it may be easier to update
your configurations if you have them located in a
central place, that is, the proxy node. On an
internetwork, the proxy node is usually a gateway. (It is
not necessary to configure a proxy node if you have
configured domain names. See Chapter 12,
“Configuring Domain Name Files,” for information on
domain names.)
Link name
The link name can have up to eight alphanumeric
characters and the first character must be alphabetic.
Physical Path of
LANIC
The physical path number corresponds to the slot
location of a node’s local area network interface
controller (LANIC) card. Recommended slot locations
and physical path calculations vary according to the
type of HP 3000 system you are running. If you are
unsure of the slot location or of the physical path
number to configure for your system, see your system
documentation or consult your Hewlett-Packard service
representative.
Enable Ethernet?
A Y in this field enables ethernet for the LAN. You can
enable either ethernet or IEEE 802.3 or both
simultaneously. One or the other must be enabled (both
fields may not be set to N). Ethernet is enabled by
default.
Disabling Ethernet has the effect of disabling the ARP
protocol as well and you will need to handle name to IP
address resolution by other means.
Enable
IEEE 802.3? A Y in this field enables IEEE 802.3 for the LAN. You
can enable either IEEE 802.3 or ethernet or both
simultaneously. One or the other must be enabled (both
fields may not be set to N). IEEE 802.3 is enabled by
default.
112
Chapter 6
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure a 100Base-T Network Interface
Disabling IEEE 802.3 has the effect of disabling the
probe protocol as well and you will need to handle name
to IP address resolution by other means.
Chapter 6
113
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure Neighbor Gateways
To Configure Neighbor Gateways
You need to visit the next two screens only if you are configuring a
non-gateway node that is on the same network as a gateway. In this
case, the non-gateway node needs to know the identity of any neighbor
gateway. Neighbor gateways can be either full or half gateways.
Gateways that are on the same network are called neighbor
gateways. A non-gateway node on a LAN, Token Ring, FDDI,
100VG-AnyLAN, or 100Base-T network may need to go through a
neighbor gateway in order to send messages to an entirely different
network. (Two nodes are on the same network if the network portion
of their IP addresses are the same.) All LAN, Token Ring, FDDI,
100VG-AnyLAN or 100Base-T nodes that are on the same network as a
neighbor gateway need to know the identity of any neighbor gateways.
When you configure a LAN, Token Ring, FDDI, 100VG-AnyLAN, or
100Base-T node, you enter into its configuration the identity of any
accessible neighbor gateways that share the same network. The
identified gateways may be either full or half gateways.
You may designate gateways as default gateways. Messages for a
network will be routed to a default gateway if there is no gateway
configured for the destination network. The default gateway will then
attempt to locate the destination of the message.
To Identify Neighbor Gateways (If Any Are
Present)
The Neighbor Gateways screen (#152) in Figure 6-7 is displayed when
you press the [Neighbor Gateways] key at the selected configuration
screen for the LAN, Token Ring, FDDI, 100VG-AnyLAN, and
100Base-T via screen numbers 41, 49, 201, 296, and 306 respectively.
114
Chapter 6
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure Neighbor Gateways
Figure 6-7
Neighbor Gateways Screen
Step 1. In the Gateway name field, enter the name of a gateway that is on the
same network as the node that you are configuring. (Nodes are on the
same network if the network portions of their IP addresses are the
same.).
Step 2. If you are adding the identified gateway for the first time, press the
[Add] key. If you are modifying the configuration of this node, press the
[Modify] key. The Neighbor Gateway Reachable Networks screen will be
displayed. Proceed to “Identify Neighbor Gateway Reachable
Networks.”
Step 3. Repeat steps 1 and 2 for each gateway that is on the same network as
the node that you are configuring. When you have finished, press the
[Next Screen] key to return to the selected configuration screen (LAN,
Token Ring, FDDI, 100VG-AnyLAN, or 100Base-T) and proceed to
Chapter 10, “Validating Network Transport and Cross-Validating with
SYSGEN,”
Fields
Gateway name Each gateway name can be as long as eight
alphanumeric characters. The first character must be
alphabetic.
Chapter 6
115
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure Neighbor Gateways
To Identify Neighbor Gateway Reachable
Networks
The Neighbor Gateway Reachable Networks screen (#158) in Figure 6-8
is displayed when you press the [Add] or [Modify] key for a valid gateway
name from the Neighbor Gateways screen (#152) in Figure 6-7.
Figure 6-8
Neighbor Gateway Reachable Networks Screen
Step 1. In the Neighbor Gateway IP Internet Address field, enter the IP
address of the gateway specified on the Neighbor Gateways screen.
C 192.191.191 009 is a typical address.
Step 2. In the IP Network Address fields under the title Configured
Reachable Networks, enter the IP addresses of all the remote
networks that can be reached through the gateway whose IP address is
configured in the previous field. If you want to designate this gateway
as a default gateway, enter an at sign (@) in one of the fields as well.
Step 3. The IP subnet mask is optional. If entering one, tab to the next field. In
the IP subnet mask field, enter the number in the same format as an
IP address.
Step 4. In the field labeled Hops, enter the number of hops (full gateways)
needed to get to the target network. Two partner gateway halves count
as one hop.
116
Chapter 6
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure Neighbor Gateways
Step 5. Repeat steps 2, 3, and 4 for each remote reachable network. The
information configured in this screen can extend to more than
one page, if necessary, to allow configuration of up to 2550
reachable networks per link (255 pages and 10 reachable nets
per page). If you need to configure more than 10 networks, press the
[Save Data] key then press the [Next Page] key to enter more networks.
Step 6. After you have finished entering the IP addresses of all the reachable
networks, press the [Save Data] key. Press the [Prior Screen] key to
return to the Neighbor Gateways screen.
Step 7. Back at the Neighbor Gateways screen, after you have finished adding
all of the neighboring gateways, press the [Prior Screen] key to return to
the selected configuration screen (LAN, Token Ring, FDDI,
100VG-AnyLAN, or 100Base-T). Proceed to Chapter 10, “Validating
Network Transport and Cross-Validating with SYSGEN,”
Fields
If you have identified any neighbor gateways, then you will also be
identifying: 1) the IP Network Addresses of all of the networks that you
can reach through that gateway, and 2) the number of hops
(corresponding to the number of gateways) that a packet passes
through to reach a remote network from the local network. Two
gateway halves count as one hop.
Neighbor Gateway
IP Internet
Address
The IP address of the gateway whose name you have
specified on the Neighbor Gateways Screen. The IP
address is in the same format as the selected
configuration screen (LAN, Token Ring, FDDI,
100VG-AnyLAN, or 100Base-T).
IP Network
Address
IP Mask
(Optional)
Hops
Chapter 6
In the fields under this heading, you list the IP
addresses of all of the networks that you will be able to
reach through the gateway you are configuring. You
also use this field to indicate whether or not the
gateway is to serve as a default gateway by
entering an at sign (@) to specify that it is a
default gateway. Only one gateway can be
designated as a default gateway for each HP 3000
Series 900 system.
The fields under this heading allow you to specify a
subnet mask for each reachable network. This mask is
optional.
In the fields under this heading, enter the number of
hops corresponding to the number of gateways that a
packet travels to reach a remote network from a local
network.
117
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node
To Configure Neighbor Gateways
118
Chapter 6
7
Configuring a Point-to-Point Node
This chapter provides step-by-step instructions for configuring
Point-to-Point links. (Point-to-Point links are sometimes referred to as
router links.) This manual assumes that you are using the guided
configuration capabilities of NMMGR.
Figure 7-1 shows the screen flow for configuring Point-to-Point screens.
Screens unique to Point-to-Point configuration are indicated by bold
boxed screens. [FUNCTION] denotes the function key used at a screen
to invoke the next screen on the screen flow.
Figure 7-1
Point-to-Point Link Configuration Screen Flow
121
Configuring a Point-to-Point Node
Before using NMMGR to configure a link, you should complete the
worksheets provided. See Chapter 4, “Planning for Node
Configuration,” for more information on planning your configuration
and filling out the configuration worksheets.
This chapter includes step-by-step instructions to help you perform the
following tasks:
• Begin the configuration process.
• Configure a Point-to-Point network interface.
• Configure neighbor gateways.
• Configure node mapping.
Once the above tasks are completed, refer to Chapter 10, “Validating
Network Transport and Cross-Validating with SYSGEN,” for
step-by-step instructions to help you perform the following validation
tasks:
• Validate the network transport configuration.
• Cross-validate in SYSGEN.
122
Chapter 7
Configuring a Point-to-Point Node
To Configure a Point-to-Point Network Interface
To Configure a Point-to-Point Network
Interface
The Point-to-Point Configuration screen (#44) in Figure 7-2 is displayed
when you press the [Config Network] key at the Network Transport
Configuration screen (#42) with an NI type of 2 (Point-to-Point). Refer
Chapter 5, “Introductory Screens,” for information on the Network
Transport Configuration screen.
Figure 7-2
Point-to-Point Link Configuration Screen
Step 1. In the IP address field, enter the internet protocol (IP) address for the
node being configured. An example of an address is:
C 192.191.191 009.
Step 2. The IP subnet mask is optional. If entering one, tab to the IP subnet
mask field and enter the number in the same format as an IP address.
Step 3. Move to the Link Name field. Enter a link name to represent the
Point-to-Point card for which you are configuring a link. This name
must be unique to both the node and the network interface (NI). Up to
40 network links are supported per Point-to-Point (router) NI.
(Up to eight network links are supported per screen. To
configure additional links, save the current screen and then
clear the screen to add additional links.)
Chapter 7
123
Configuring a Point-to-Point Node
To Configure a Point-to-Point Network Interface
Step 4. Tab down to the Physical Path field. Enter the physical path number
corresponding to the SPU slot number of the programmable serial
interface (PSI) card.
Step 5. Tab to the Speed field. Enter the line transmission speed of this link.
Step 6. Tab to the Type field. Enter DD for direct dial, SD for shared dial or DC
for direct connection.
Step 7. Press the [Save Data] key to record the data you have entered.
Step 8. If you need to identify neighbor gateways, press the [Neighbor Gateways]
key and proceed to the section in this chapter called “To Configure
Neighbor Gateways.”
Step 9. If you have already configured neighbor gateways for this link or your
network contains no neighbor gateways, press the [Link Routing] key
and proceed to the section in this chapter titled “To Configure Node
Mapping.”
Optional Keys
Press the [List NIs] key to list the names and types of
already configured network interfaces.
Press the [Delete NI] key to remove a configured network
interface from the configuration file.
Press the [Read Other NI] key to call up a previously
configured Network Interface name.
Fields
Node name
Display only.
Network
Interface
(NI) name
Display only.
IP address
The IP address is an address of a node on a network. An
IP address has two parts: a network portion and a node
portion. The network portion must be the same for all
nodes on a LAN network; the node portion must be
unique for all nodes on a LAN network.
There are two methods of entering an internet protocol (IP) address
within NMMGR:
1. Enter the fully qualified IP address (for example, Class C,
C 192.191.191 009).
OR
2. Enter only the network (nnn) and node (xxx) portions of the IP
address as four positive integers between 0 and 255 separated by
periods or blanks (for example, 15.123.44.98).
124
Chapter 7
Configuring a Point-to-Point Node
To Configure a Point-to-Point Network Interface
You need not enter the following items as NMMGR will fill these in:
• Class A, B, C
• Leading zeros for the network and node portion of the IP address.
HP assigns the network portion (initial nine digits) of IP addresses
from ARPA Class C, though your addresses may also be of Classes A or
B. The complete formats are:
Class
A nnn xxx.xxx.xxx
B nnn.nnn xxx.xxx
C nnn.mmm.mmm xxx
Where:
nnn = the network portion of the IP address and
xxx = the node portion of the IP address.
For Class C, the node portion of the IP address must be between 001
and 254.
If you are adding your NS 3000/iX node to an existing network, the
network portion of each node’s IP address should be the same. You will
have to find out what this is, and use it in the network portion of the IP
address of your NS 3000/iX node. Also, you will need to know the node
portions of the IP addresses of each of the nodes (usually they will be
numbered sequentially, such as 001, 002, and so on), so that you can
specify a unique node portion for the IP address of your node. If you
have a network map, it should provide a record of such items as the
node name and IP address of each node. If there is no record, and if you
want to find out each node’s IP address, you will have to issue the
following command (NM capability required) on each of the nodes:
NETCONTROL NET=NIname;STATUS
One of the lines of output from this command tells you what the
complete IP address is for that node; the last three digits are the unique
node portion of the class C address.
NOTE
To obtain a class B or C IP address, contact Government Systems,
Incorporated (GSI). To obtain an application form, write GSI at the
address below. Allow at least eight working days for GSI to process an
IP address request.
Government Systems, Inc.
Attn: Network Information Center
7990 Boeing Ct.
Vienna, VA 22183
(800) 364-3642 (703) 821-6161
Chapter 7
125
Configuring a Point-to-Point Node
To Configure a Point-to-Point Network Interface
IP subnet
mask
Link name
An IP subnet mask is specified in the same format as
an IP address. The 32-bit mask is grouped in octets
expressed as decimal integers and delimited by either a
period (.) or a space. An IP mask is used when
configuring subnetworks. The mask identifies which
bits of an IP address will be used to define a
subnetwork. To determine these bits, you first need to
estimate how many subnetworks and nodes per
subnetwork you need. See Chapter 2, “Networking
Concepts,” for details on deriving an IP subnet mask.
The link name can have up to eight alphanumeric
characters and the first character must be alphabetic.
Physical Path
The physical path number corresponds to the slot
location of a node’s programmable serial interface (PSI)
card. Recommended slot locations and physical path
calculations vary according to the type of HP 3000
system you are running. If you are unsure of the slot
location or of the physical path number to configure for
your system, see your system documentation or consult
your Hewlett-Packard service representative.
Speed
The line transmission speed is given in bits per second.
For direct connect the value, must be supported by the
cable. Values are 1200, 2400, 4800, 9600, 19200, 38400,
56000, and 64000. The default is 56000.
Type
Enter DD (direct dial) if you always want to call the
same host over a dial link. If you choose DD the remote
host does not have to be adjacent and other nodes can
be accessed through the remote host. Enter SD if you
want to call more than one adjacent remote node over a
dial link without reconfiguring. If you choose SD, no
other remote nodes can be accessed through the remote
host; it is an end point in the connection. Enter DC if the
link is a leased line, private line, or other non-switched
link.
126
Chapter 7
Configuring a Point-to-Point Node
To Configure Neighbor Gateways
To Configure Neighbor Gateways
You need to visit the next two screens only if you are configuring a
non-gateway node that is on the same network as a gateway. In this
case, the non-gateway node needs to know the identity of any neighbor
gateway. Neighbor gateways can be either full or half gateways.
Gateways that are on the same network are called neighbor
gateways. A non-gateway node on a Point-to-Point network may need
to go through a neighbor gateway in order to send messages to an
entirely different network. (Two nodes are on the same network if the
network portion of their IP addresses are the same.) All Point-to-Point
nodes that are on the same network as a neighbor gateway need to
know the identity of any neighbor gateways. When you configure a
Point-to-Point node, you enter into its configuration the identity of any
accessible neighbor gateways that share the same network. The
identified gateways may be either full or half gateways.
You may designate one gateway as a default gateway. Messages for a
network will be routed to the default gateway if there is no gateway
configured for the destination network. The default gateway will then
attempt to locate the destination of the message.
To Identify Neighbor Gateways (If Any Are
Present)
The Neighbor Gateways screen (#152) in Figure 7-3 is displayed when
you press the [Neighbor Gateways] key at the Point-to-Point Link
Configuration screen (#44) in Figure 7-2.
Chapter 7
127
Configuring a Point-to-Point Node
To Configure Neighbor Gateways
Figure 7-3
Neighbor Gateway Screen
Step 1. In the Gateway name field, enter the name of a gateway that is on the
same network as the node that you are configuring. (Nodes are on the
same network if the network portions of their IP addresses are the
same.).
Step 2. If you are adding the identified gateway for the first time, press the
[Add] key. If you are modifying the configuration of this node, press the
[Modify] key. The Neighbor Gateway Reachable Networks screen will be
displayed. Proceed to the section in this chapter titled “To Identify
Neighbor Gateway Reachable Networks.”
Step 3. Repeat steps 1 and 2 for each gateway that is on the same network as
the node that you are configuring. When you have finished, press the
[Prior Screen] key to return to the Point-to-Point Configuration screen
and proceed to the section in this chapter titled “To Configure Node
Mapping.”
Fields
Gateway name Each gateway name can be as long as eight
alphanumeric characters. The first character must be
alphabetic.
128
Chapter 7
Configuring a Point-to-Point Node
To Configure Neighbor Gateways
To Identify Neighbor Gateway Reachable
Networks
The Neighbor Gateway Reachable Networks screen (#158) in figure 7-4
is displayed when you press the [Add] key or the [Modify] key for a valid
gateway name from the Neighbor Gateways screen (#152) in Figure 7-3.
Figure 7-4
Neighbor Gateway Reachable Networks
Step 1. In the Neighbor Gateway IP Internet Address field, enter the IP
address of the gateway specified on the Neighbor Gateways screen. An
example of an address is: C 192.191.191 009.
Step 2. In the IP Network Address fields under the title Configured
Reachable Networks, enter the IP addresses of all the remote
networks that can be reached through the gateway whose IP address is
configured in the previous field.
Step 3. The IP subnet mask is optional. If entering one, tab to the next field. In
the IP subnet mask field, enter the number in the same format as an
IP address.
Step 4. In the field labeled Hops, enter the number of hops (full gateways)
needed to get to the target network. Two partner gateway halves count
as one hop.
Step 5. Repeat steps 2, 3, and 4 for each remote reachable network. The
information configured in this screen can extend to more than
one page, if necessary, to allow configuration of up to 2550
Chapter 7
129
Configuring a Point-to-Point Node
To Configure Neighbor Gateways
reachable networks per link (255 pages and 10 reachable nets
per page). If you need to configure more than 10 networks, press the
[Save Data] key then press the [Next Page] key to enter more networks.
Step 6. After you have finished entering the IP addresses of all the reachable
networks, press the [Save Data] key. Press the [Prior Screen] key to
return to the Neighbor Gateways screen.
Step 7. Back at the Neighbor Gateways screen, after you have finished adding
all of the neighboring gateways, press the [Prior Screen] key to return to
the Point-to-Point Link Configuration screen. Proceed to the section in
this chapter titled “To Configure Node Mapping.”
Fields
If you have identified any neighbor gateways, then you will also be
identifying: 1) the IP Network Addresses of all of the networks that you
can reach through that gateway, and 2) the number of hops
(corresponding to the number of gateways) that a packet passes
through to reach a remote network from the local network. Two
gateway halves count as one hop.
Neighbor Gateway
IP Internet
Address
The IP address of the gateway whose name you have
specified on the Neighbor Gateways Screen. The IP
address is in the same format as on the Point-to-Point
Configuration screen.
IP Network
Address
IP Mask
(Optional)
Hops
130
In the fields under this heading, you list the IP
addresses of all of the networks that you will be able to
reach through the gateway you are configuring. You
also use this field to indicate whether or not the
gateway is to serve as a default gateway by
entering an at sign (@) to specify that it is a
default gateway. Only one gateway can be
designated as a default gateway for each
900 Series HP 3000 system.
The fields under this heading allow you to specify a
subnet mask for each reachable network. This mask is
optional. See Chapter 2, “Networking Concepts,” for
details on deriving the IP mask.
In the fields under this heading, enter the number of
hops corresponding to the number of gateways that a
packet travels to reach a remote network from a local
network. Note: if you choose SD, no other nodes can be
accessed through the remote host; it is an end point in
the connection. Enter DC if the link is a leased line,
private line, or other non-switched link.
Chapter 7
Configuring a Point-to-Point Node
To Configure Node Mapping
To Configure Node Mapping
The screens discussed in the following pages allow you to configure
shared dial or direct connect and dial node mapping. These screens
allow you to specify routes to target (destination) nodes and to indicate
the priority of each route.
The number of mappings you enter depends on how many links are on
the node you are configuring.
Nodes Having Single Links
If you are configuring a node (call it Node A) that has only one
Point-to-Point link to a second node (call it Node B), you enter one route
name as the mapping to the adjacent node (Node B).
If there are additional nodes attainable beyond Node B, you would only
have to enter one more mapping: make up a route name, and then you
can indicate the additional (non-adjacent) nodes by specifying a
“wildcard” (@) in the destination IP address field of either the Dialed or
Non-dialed Node Mapping Configuration screens.
Nodes Having Multiple Links
If you are configuring a node that has more than one Point-to-Point
link, you could ultimately have several paths to a non-adjacent
destination node. Hence, if this node has more than one Point-to-Point
link, enter a symbolic route name for every other destination node on
the network.
The route name is only used during configuration of this node, and you
do not have to repeat it when you configure other nodes.
To Select a Node Mapping Screen
To begin configuring node mapping, you should be at the Point-to-Point
Link Configuration screen (#44) in Figure 7-2. You will configure node
mapping for each link you are configuring.
Step 1. Enter the name of a configured link in the field at the bottom of the
screen next to the words To configure router mapping enter
Link Name.
Step 2. Press the [Link Routing] key.
Step 3. If the Type specified for the selected link is SD, proceed to the section in
this chapter titled “To Configure Shared Dial Node Mapping.”
Step 4. If the Type specified for the selected link is DD or DC, proceed to the
section in this section titled “To Configure Direct Connect/Dial Node
Mapping.”
Chapter 7
131
Configuring a Point-to-Point Node
To Configure Node Mapping
To Configure Shared Dial Node Mapping
The Shared Dial Node Mapping Configuration screen (#46) in Figure
7-5is displayed if you press the [Link Routing] key at the Point-to-Point
Link Configuration screen (#44) for a link of type SD.
Figure 7-5
Shared Dial Node Mapping Configuration Screen
Each router NI can have up to 1024 mappings. However, 4096 is the
absolute maximum number of unique phone numbers supported per
NMCONFIG File.
Step 1. In the Route Name field, enter a symbolic name that represents a route
between the node you are configuring and destination node
Step 2. In the Destination IP Address field, enter the IP address of the
destination node for which a route is being specified.
Step 3. In the Priority field, enter a number from 1 to 99 to indicate the
priority of this route if there are multiple routes to a destination.
Step 4. In the Phone Number field, enter the telephone number of the
destination node. (Leave this field blank if the target node is
non-adjacent.)
Step 5. The Security String field is optional. You may enter a string that
remote nodes must use to gain dial link access to the node you are
configuring.
Step 6. In the Disable Route field, leave the default alone unless you want to
temporarily disable a configured route.
132
Chapter 7
Configuring a Point-to-Point Node
To Configure Node Mapping
Step 7. Press the [Save Data] key to save the data on the screen. Proceed to
Chapter 10, “Validating Network Transport and Cross-Validating with
SYSGEN,” and press the [Validate Netxport] key.
Optional Keys
Press the [Next Link] key to call up another link when
you want to configure information about its adjacent
and non-adjacent nodes.
Press the [Config Directry] key to configure the Network
Directory screen.
Fields
Route Name
A symbolic name, up to eight alphanumeric characters,
that represents a route between the node you are
configuring and a destination node. The route name is
only used within the NMMGR program. It is most
useful when the node you are configuring has more
than one possible way of accessing a target
(destination) node. It identifies different routes to
target nodes and is not the actual target node name. It
is used because you may need a way to identify more
than one route to a target node. There should be at
lease one symbolic route name for routes to every other
destination node on the network unless you use the “@”
wildcard destination IP address.
To help keep track of routes, you can use the
destination node name as the route name. If you have
more than one route to a given node, you can name the
routes nodename1, nodename2, and so forth.
Destination
IP Address IP address of the target (destination) node for which a
route is being defined.
Priority
Number from 1 to 99 that indicates which route has
precedence (priority) over another when there are
multiple routes to a destination. A route to a
destination that has a higher priority will take
precedence over a route with a lower priority. This field
is the primary means of influencing the choice of route.
Phone Number Required if the link is a dial link. The field must be
blank if the target node is non-adjacent. Enter the
telephone number as a combination of decimal numbers
(0 through 9), dashes, and the following special
characters:
Chapter 7
/
Separator used for automatic call units
that have second dial-tone detect.
E
Optional end-of-number indicator.
133
Configuring a Point-to-Point Node
To Configure Node Mapping
D
Three-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.
To disable outbound dialing, enter an exclamation point
(!) by itself in the phone number field.
Each router NI can have up to 1024 mappings.
However, 4096 is the absolute maximum number of
unique phone numbers supported per NMCONFIG File.
Security
String
An optional security string that remote nodes must use
to gain dial link access to the node. It can be up to eight
alphanumeric characters, left justified, with no
embedded blanks. The first character must be
alphabetic.
Disable Route
Y (yes) or N (no) indicator that allows you to temporarily
disable a configured route. Leave the default (N) alone if
you do not want to disable the route.
To Configure Direct Connect/Dial Node Mapping
The Direct Connect/Dial Node Mapping Configuration screen (#45) in
Figure 7-6 is displayed if you press the [Link Routing] key at the
Point-to-Point Link Configuration screen (#44) for a link of type DD or
DC.
134
Chapter 7
Configuring a Point-to-Point Node
To Configure Node Mapping
Figure 7-6
Direct Connect/Dial Node Mapping Configuration Screen
Each router NI can have up to 1024 mappings. However, 4096 is the
absolute maximum number of unique phone numbers supported per
NMCONFIG File.
Step 1. In the Route Name field, enter a symbolic name that represents a route
between the node you are configuring and a destination node.
Step 2. In the Destination IP Address field, enter the IP address of the
destination node for which a route is being specified.
Step 3. In the Priority field, enter a number from 1 to 99 to indicate the
priority of this route if there are multiple routes to a destination.
Step 4. In the Disable Route field, leave the default alone unless you want to
temporarily disable a configured route.
Step 5. If this is a dial link, in the Phone Number field, enter the telephone
number of the destination node.
Step 6. The Security String field is optional. You may enter a string that
remote nodes must use to gain dial link access to the node you are
configuring.
Step 7. Enter information for non-adjacent (remote) nodes in the same manner
in the fields provided. (You do not configure a phone number or security
string for non-adjacent nodes.)
Step 8. Press the [Save Data] key to save the data on the screen. Proceed to
Chapter 10, “Validating Network Transport and Cross-Validating with
SYSGEN,” and press the [Validate Netxport] key.
Chapter 7
135
Configuring a Point-to-Point Node
To Configure Node Mapping
Figure 7-7
Using an @ for Mapping Non-Adjacent Nodes
Priority
Number from 1 to 99 that indicates which route has
precedence (priority) over another when there are
multiple routes to a destination. A route to a
destination that has a higher priority will take
precedence over a route with a lower priority.
Disable Route
Y (yes) or N (no) indicator that allows you to temporarily
disable a configured route. Leave the default (N) alone if
you do not want to disable the route.
Phone Number Required if the link is a dial link. The field must be
blank if the target node is non-adjacent. 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.
D
Three-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.
To disable outbound dialing, enter an exclamation point
(!) by itself in the phone number field.
Each router NI can have up to 1024 mappings.
However, 4096 is the absolute maximum number of
unique phone numbers supported per NMCONFIG File.
Security
String
136
An optional security string that remote nodes must use
to gain dial link access to the node. It can be up to eight
alphanumeric characters, left justified, with no
embedded blanks. The first character must be
alphabetic.
Chapter 7
8
Configuring an X.25 Node
This chapter provides step-by-step instructions for configuring X.25 iX
System Access for systems using PC-based network management. This
manual assumes that you are using the guided configuration
capabilities of NMMGR.
Figure 8-1 shows the screen flow for configuring X.25 screens. Screens
unique to X.25 configuration are indicated by bold boxed screens.
[FUNCTION] denotes the function key used at a screen to invoke the
next screen on the screen flow.
Figure 8-1
X.25 Link Screen Flow
137
Configuring an X.25 Node
Before using NMMGR to configure a link, you should complete the
worksheets provided. See Chapter 4, “Planning for Node
Configuration,” for more information on planning your configuration
and filling out the configuration worksheets.
This chapter includes step-by-step instructions to help you perform the
following tasks:
• Begin the configuration process.
• Configure an X.25 network interface.
• Configure neighbor gateways.
Once the above tasks are completed, refer to Chapter 10, “Validating
Network Transport and Cross-Validating with SYSGEN,” for
step-by-step instructions to help you perform the following validation
tasks:
• Validate the network transport configuration.
• Cross-validate in SYSGEN.
NOTE
If you are configuring X.25 iX System Access on a system that is using
host-based network management (a PC running the HP OpenView
Network Manager is not part of the network), use Configuring and
Managing Host-Based X.25 Links instead of this manual for
step-by-step configuration instructions.
138
Chapter 8
Configuring an X.25 Node
To Configure an X.25 Network Interface
To Configure an X.25 Network Interface
The X.25 Configuration screen (#48) in Figure 8-2 is displayed when
you press the [Config Network] key at the Network Transport
Configuration screen (#42) with an NI type of 3 (X.25). Refer to Chapter
5, “Introductory Screens,” for information on the Network Transport
Configuration screen.
Figure 8-2
NS Configuration Screen
Step 1. In the IP address field, enter the internet protocol (IP) address for the
node being configured. An example of an address is:
C 192.191.191 009.
Step 2. The IP subnet mask is optional. If entering one, tab to the IP subnet
mask field and enter the number in the same format as an IP address.
Step 3. Move to the first Link name field. Enter a link name to represent the
DTC/X.25 Network Access card for which you are configuring a link.
This name must be unique to both the node and the DTC. It must also
be the same as the link name configured for this card when the
Datacommunications and Terminal Subsystem (DTS) was configured.
Step 4. Enter the node name of the DTC that houses the DTC/X.25 Access card
in the first DTC Node Name field then enter the slot number of the card
in the Card Number field. Enter a link name, DTC node name, and
card number for each link you are configuring.
Chapter 8
139
Configuring an X.25 Node
To Configure an X.25 Network Interface
Step 5. When you are done adding links, press the [Save Data] key.
Step 6. If the network that this node is on contains ANY internetwork gateway
(either full or half) press the [Neighbor Gateways] key and proceed to the
section in this chapter called “To Configure Neighbor Gateways.”
Step 7. If the network that this node is on contains NO internetwork gateways
or if you have already configured gateways for this system, press the
[Config Directry] key and proceed to the section in this chapter titled “To
Configure X.25 Virtual Circuits.”
Optional Keys
Press the [List NIs] key to list the names and types of
already configured network interfaces.
Press the [Delete NI] key to remove a configured network
interface from the configuration file.
Press the [Read Other NI] key to call up a previously
configured Network Interface name.
Fields
Node Name
Display only.
Network
Interface
(NI) name
Display only.
IP address
IP address is an address of a node on a network. An IP
address has two parts: a network portion and a node
portion. The network portion must be the same for all
nodes on an X.25 network; the node portion must be
unique for all nodes on an X.25 network.
There are two methods of entering an internet protocol
(IP) address within NMMGR:
1. Enter the fully qualified IP address (for example,
Class C, C 192.191.191 009).
OR
2. Enter only the network (nnn) and node (xxx)
portions of the IP address as four positive integers
between 0 and 255 separated by periods or blanks
(for example, 15.123.44.98).
You need not enter the following items as NMMGR
will fill these in:
• Class A, B, C
• Leading zeros for the network and node portion of
the IP address.
140
Chapter 8
Configuring an X.25 Node
To Configure an X.25 Network Interface
HP assigns the network portion (initial nine digits) of
IP addresses from ARPA Class C, though your
addresses may also be of Classes A or B. The complete
formats are:
Class
A nnn xxx.xxx.xxx
B nnn.nnn xxx.xxx
C nnn.mmm.mmm xxx
Where:
nnn = the network portion of the IP address and
xxx = the node portion of the IP address.
For Class C, the node portion of the IP address must be
between 001 and 254.
If you are adding your NS 3000/iX node to an existing
network, the network portion of each node’s IP address
should be the same. You will have to find out what this
is, and use it in the network portion of the IP address of
your NS 3000/iX node. Also, you will need to know the
node portions of the IP addresses of each of the nodes
(usually they will be numbered sequentially, such as
001, 002, and so on), so that you can specify a unique
node portion for the IP address of your node. If you
have a network map, it should provide a record of such
items as the node name and IP address of each node. If
there is no record, and if you want to find out each
node’s IP address, you will have to issue the following
command (NM capability required) on each of the
nodes:
NETCONTROL NET=NIname;STATUS
One of the lines of output from this command tells you
what the complete IP address is for that node; the last
three digits are the unique node portion of the class C
address.
NOTE
To obtain a class B or C IP address, contact Government Systems,
Incorporated (GSI). To obtain an application form, write GSI at the
address below. Allow at least eight working days for GSI to process an
IP address request.
Government Systems, Inc.
Attn: Network Information Center
7990 Boeing Ct.
Vienna, VA 22183
(800) 364-3642 (703) 821-6161
Chapter 8
141
Configuring an X.25 Node
To Configure an X.25 Network Interface
IP subnet
mask
Link name
DTC Node
Name
An IP subnet mask is specified in the same format as
an IP address. The 32-bit mask is grouped in octets
expressed as decimal integers and delimited by either a
period (.) or a space. An IP mask is used when
configuring subnetworks. The mask identifies which
bits of an IP address will be used to define a
subnetwork. To determine these bits, you first need to
estimate how many subnetworks and nodes per
subnetwork you need. See Chapter 2, “Networking
Concepts,” for details on deriving an IP subnet mask.
The link name identifies a specific DTC/X.25 Network
Access card to be used for X.25 system-to-system
connections. This link name must be the same as the
link name you entered for this card when you
configured your DTCs. You may configure up to 11
links. (One link must be used for loopback. Loopback
will be automatically configured during the guided
screen configuration.)
The DTC node name is the fully qualified nodename
(name.domain.organization) of the DTC that
contains the DTC/X.25 Network Access card with the
configured link name.
Card Number The DTC card number is the number of the DTC/X.25
Network Access card in the associated DTC. If the card
is contained in a DTC 48, the DTC card number can be
any number from 1 to 5. If the card is contained in a
DTC 16, the card number must be 2.
To Configure X.25 Virtual Circuits
The X.25 Virtual Circuit Configuration screen (#47) in Figure 8-3 is
displayed if you press the [Config Directry] key from the X.25
Configuration screen (#48) in Figure 8-2. This screen lets you configure
the network directory.
142
Chapter 8
Configuring an X.25 Node
To Configure an X.25 Network Interface
Figure 8-3
X.25 Virtual Circuit Configuration Screen
Step 1. In the Remote node name field, type in the nodename of each remote
X.25 node on your network in the format
nodename.domain.organization. Also, if you need to be able to
perform a loopback DSLINE command to the local node, then enter the
local node’s name here as well.
Step 2. For each node, type the IP address of the node in the Remote IP
address field.
Step 3. To specify that calls can be made to a node, enter its address key in the
Address key field. Enter the node portion of the remote node’s
configured nodename.
NOTE
An address key called POOL is already preconfigured for you though it
doesn’t show up on the screen. POOL allows the node being configured to
receive any incoming calls even if the remote system’s address is not
configured on this screen. POOL will also allow you to use NetIPC to
programmatically provide an X.25 address that is not configured on this
screen. If you want to delete the POOL address key, in the last line of the
X.25 Virtual Circuit Configuration screen enter a 3 (for switched VCs)
and press the [Go To] key. That brings you to the X.25 SVC Address Key
Paths screen where you can then remove the default name POOL by
typing over it with spaces and then saving the data.
Step 4. If the address type is a switched virtual circuit complete steps a
through c, but if the address type is a permanent virtual circuit, skip to
step 5.
Chapter 8
143
Configuring an X.25 Node
To Configure an X.25 Network Interface
a. In the Remote X.25 address field, enter the X.25 address of the
remote host for X.25 public data networks or private networks.
b. Make sure the name of the facility set you are using is in the
Facility set field. You may either choose the default facility set
(STDSFSET) or enter an alternative. If you are configuring a new
facility set, enter a new name. (To modify facility set parameters,
enter a 5 in the last field on the screen and press the [Go To] key.)
c. In the Security class field, enter the level of logical security you
want to have on this particular entry. The possible values are IN
(accept calls from the address), IO (accept calls from and send calls
to the address, default), OU (send calls to the address, incoming calls
are rejected), and LK (block calls to or from the address).
Step 5. If the address type is a permanent virtual circuit (PVC), in the
Permanent VC number field, enter the PVC number of the PVC on the
remote node. This value cannot be greater than the number of PVCs for
which you are subscribed. It must be within the PVC range you defined
during DTC configuration.
Step 6. After you have finished entering new information for each remote node,
press the [Save Data] key. (Press the key once for each remote node you
are configuring.)
Step 7. If you have completed configuration of X.25, press the [Validate Netxport]
key and proceed to Chapter 10, “Validating Network Transport and
Cross-Validating with SYSGEN.” Otherwise, press the [Prior Screen]
key to return to the X.25 Configuration screen.
Fields
Network
directory
name
The network directory file that will be updated by the
information entered through this screen.
Remote node
name
You must enter the remote node name of each X.25
node into the network directory. Include entries for all
remote nodes and, if you want to be able to perform
loopback, the local node as well.
Remote IP
address
Also in the network directory, you must enter the IP
Address of each node whose identity you have entered
into the network directory. For the format of this
parameter, see the information in the “Fields” section
under “Configure X.25 Network.”
Address key The X.25 address key is the name of a remote node with
which your local node will be communicating.
Hewlett-Packard recommends that you make the name
be the node portion of the remote node’s name (where
its full name is node.domain.organization). You
144
Chapter 8
Configuring an X.25 Node
To Configure an X.25 Network Interface
must configure an X.25 address key for each remote
node with which your node will be communicating. You
have a combined maximum of 1024 X.25 address keys
in the SVC and PVC path tables. The X.25 address key
name must be eight characters or less and the first
character must be alphabetic. A default address key
called POOL allows any system to access the local
system even if the remote system’s address is not
configured. POOL can also be used when level 3
programmatic access (NetIPC) provides an X.25
address.
Network
Interface
(NI) name
SVC or PVC
Parameters
For SVCs
Display only.
The parameters for assigning either SVCs or PVCs are
described in the following paragraphs.
Remote X.25
address
The remote X.25 address is the remote node’s X.25
address. This address is required for SVCs if you have
specified an X.25 address key. This address must be
15 digits or less.
Facility set The facility set name is a name for a set of X.25
connection parameters. The parameters are determined
by the type of X.25 network that you are subscribed to.
You can configure options in a facility set so that
specified options are available for every virtual circuit
or negotiated for each virtual circuit on a per-call basis.
This facility set will be used when a connection is made
from your node to the specified remote node or from the
specified remote node to your node. A Facility Set is
required for SVCs if you have specified an X.25 Address
Key. The facility set name must be eight characters or
less, and the first character must be alphabetic. You can
configure up to 128 facility sets.
To modify facility set parameters, enter a 5 in the field
at the bottom of the screen and press the [Go To] key.
This will take you to the X.25 User Facility Sets screen.
From this screen you can create new or modify existing
user facility sets. See the NS 3000/iX Screens
Reference Manual for more information.
Chapter 8
145
Configuring an X.25 Node
To Configure an X.25 Network Interface
Security
class
The security class is the level of logical security you
want to have when a connection is made to or from the
specified remote node. A Security level is required for
SVCs if you have specified an X.25 Address Key. The
possible values are as follows:
• IO—Both incoming and outgoing calls are accepted.
This is the default value.
• IN—Only incoming calls are accepted from this
particular remote address. Outgoing calls will be
rejected.
• OU—Only outgoing calls are accepted to this
particular remote address. Incoming calls will be
rejected.
• LK—Entry is locked. No call is accepted, either
inbound or outbound.
For PVCs
Permanent VC
number
The PVC Number identifies a permanent virtual circuit
(PVC) on the remote node. If you have entered a name
in the X.25 Address Key field and are configuring PVCs,
then you also have to enter a value for the PVC
Number.
146
Chapter 8
Configuring an X.25 Node
To Configure Neighbor Gateways
To Configure Neighbor Gateways
You need to visit the next two screens only if you are configuring a
non-gateway node that is on the same network as a gateway. In this
case, the non-gateway node needs to know the identity of any neighbor
gateway. Neighbor gateways can be either full or half gateways.
Gateways that are on the same network are called neighbor
gateways. A non-gateway node on an X.25 network may need to go
through a neighbor gateway in order to send messages to an entirely
different network. (Two nodes are on the same network if the network
portion of their IP addresses are the same.) All X.25 nodes that are on
the same network as a neighbor gateway need to know the identity of
any neighbor gateways. When you configure an X.25 node, you enter
into its configuration the identity of any accessible neighbor gateways
that share the same network. The identified gateways may be either
full or half gateways.
You may designate gateways as default gateways. Messages for a
network will be routed to a default gateway if there is no gateway
configured for the destination network. The default gateway will then
attempt to locate the destination of the message.
To Identify Neighbor Gateways (If Any Are
Present)
The Neighbor Gateways screen (#152) in Figure 8-4is displayed when
you press the [Neighbor Gateways] key at the X.25 Configuration screen
(#48) in Figure 8-2.
Chapter 8
147
Configuring an X.25 Node
To Configure Neighbor Gateways
Figure 8-4
Neighbor Gateways Screen
Step 1. In the Gateway name field, enter the name of a gateway that is on the
same network as the node that you are configuring. (Nodes are on the
same network if the network portions of their IP addresses are the
same.).
Step 2. If you are adding the identified gateway for the first time, press the
[Add] key. If you are modifying the configuration of this node, press the
[Modify] key. The Neighbor Gateway Reachable Networks screen will be
displayed. Proceed to the section titled “To Identify Neighbor Gateway
Reachable Networks.”
Step 3. Repeat steps 1 and 2 for each gateway that is on the same network as
the node that you are configuring. When you have finished, press the
[Prior Screen] key to return to the X.25 Configuration screen.
Fields
Gateway name Each gateway name can be as long as eight
alphanumeric characters. The first character must be
alphabetic.
To Identify Neighbor Gateway Reachable
Networks
The Neighbor Gateway Reachable Networks screen (#158) in Figure 8-5
is displayed when you press the [Add] key or the [Modify] key for a valid
gateway name from the Neighbor Gateways screen (#152) in Figure 8-4.
148
Chapter 8
Configuring an X.25 Node
To Configure Neighbor Gateways
Figure 8-5
Neighbor Gateway Reachable Networks Screen
Step 1. In the Neighbor Gateway IP Internet Address field, enter the IP
address of the gateway specified on the Neighbor Gateways screen. An
example is: C 192.007.007 001
Step 2. In the IP Network Address fields under the title Configured
Reachable Networks, enter the IP addresses of all the remote
networks that can be reached through the gateway whose IP address is
configured in the previous field.
Step 3. The IP subnet mask is optional. If entering one, tab to the next field. In
the IP mask field, enter the number in the same format as an IP
address.
Step 4. In the field labeled Hops, enter the number of hops (full gateways)
needed to get to the target network. Two partner gateway halves count
as one hop.
Step 5. Repeat steps 2, 3, and 4 for each remote reachable network. The
information configured in this screen can extend to more than one page,
if necessary, to allow configuration of up to 2550 reachable networks per
link (255 pages and 10 reachable nets per page). If you need to
configure more than 10 networks, press the [Save Data] key then press
the [Next Page] key to enter more networks.
Step 6. After you have finished entering the IP addresses of all the reachable
networks, press the [Save Data] key. Press the [Prior Screen] key to
return to the Neighbor Gateways screen.
Chapter 8
149
Configuring an X.25 Node
To Configure Neighbor Gateways
Step 7. Back at the Neighbor Gateways screen, after you have finished adding
all of the neighboring gateways, press the [Prior Screen] key to return to
the X.25 Configuration screen. Follow the instructions for step 7 in the
section in this chapter titled “To Configure an X.25 Network.”
Fields
If you have identified any neighbor gateways, then you will also be
identifying: 1) the IP Network Addresses of all of the networks that you
can reach through that gateway, and 2) the number of hops
(corresponding to the number of gateways) that a packet passes
through to reach a remote network from the local network. Two
gateway halves count as one hop.
Neighbor Gateway
IP Internet
Address
The IP address of the gateway whose name you have
specified on the Neighbor Gateways Screen. The IP
address is in the same format as the LAN
Configuration screen.
IP Network
Address
IP Mask
(Optional)
Hops
150
In the fields under this heading, you list the IP
addresses of all of the networks that you will be able to
reach through the gateway you are configuring. You
also use this field to indicate whether or not the
gateway is to serve as a default gateway by entering an
at sign (@) to specify that it is a default gateway. Only
one gateway can be designated as a default gateway for
each HP 3000 Series 900 system.
The fields under this heading allow you to specify a
subnet mask for each reachable network. This mask is
optional. For details on deriving an IP subnet mask, see
Chapter 2, “Networking Concepts.”
In the fields under this heading, enter the number of
hops corresponding to the number of gateways that a
packet travels to reach a remote network from a local
network.
Chapter 8
9
Configuring a Gateway Half
This chapter describes how to configure the interface between one
gateway half and another gateway half. Gateway halves are one of the
methods you can use to interconnect two separate networks. For
information on configuring a node that is not a gateway half, use this
manual.
Figure 9-1 shows the screen flow for configuring gateway half screens.
Screens unique to gateway half configuration are indicated by bold
boxed screens. [FUNCTION] denotes the function key used at a screen
to invoke the next screen on the screen flow.
Figure 9-1
Gateway Half Link Screen Flow
151
Configuring a Gateway Half
Configuring a node as a gateway half requires configuring two separate
network interfaces: one for the interface between the two gateway
halves, and a second for the gateway half ’s interface to its home
network.
If this gateway half interfaces to a LAN, Token Ring, FDDI,
100VG-AnyLAN, or 100Base-T network, you should have already
configured its network interface according to the instructions in
Chapter 6, “Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN,
100Base-T Node.” If this gateway half interfaces to a Point-to-Point or
X.25 network, you should already have configured its NI according to
instructions in Chapter 7, “Configuring a Point-to-Point Node,” and
Chapter 8, “Configuring an X.25 Node,” respectively. If you have not, do
so now and then return to this chapter.
This chapter includes step-by-step instructions to help you perform the
following tasks:
• Begin the configuration process.
• Configure a gatehalf.
Once the above tasks are completed, refer to Chapter 10, “Validating
Network Transport and Cross-Validating with SYSGEN,” for
step-by-step instructions to help you perform the following validation
tasks:
• Validate the network transport configuration.
• Cross-validate in SYSGEN.
152
Chapter 9
Configuring a Gateway Half
To Configure a Gatehalf Network Interface
To Configure a Gatehalf Network Interface
The Gatehalf Configuration screen (#40) in Figure 9-2 is displayed
when you press the [Config Network] key at the Network Transport
Configuration screen (#42) with an NI type of 5 (Gateway Half). Refer
to Chapter 5, “Introductory Screens,” for information on the Network
Transport Configuration screen.
Figure 9-2
Gatehalf Configuration Screen
Step 1. In the Partner’s IP address field, enter the internet protocol (IP)
address of this gateway half ’s partner.
Step 2. The IP subnet mask is optional. If entering one, tab down to the next
field. In the IP subnet mask field, enter the number in the same format
as an IP address.
Step 3. Tab to the Home NI name field. Enter a name that is the same as one of
the LAN, Point-to-Point, or X.25 network interface names of the node
being configured.
Step 4. Tab down to the Link name field and enter a link name to represent
each individual hardware interface card.
Step 5. Tab over to the Link type field. Enter DD for direct dial or DC for
leased lines, private lines, or other non-switched links.
Chapter 9
153
Configuring a Gateway Half
To Configure a Gatehalf Network Interface
Step 6. Enter the physical path of this node’s Programmable Serial Interface
(PSI) card.
Step 7. Tab down to the next field. In the Transmission speed field, either
leave the default or enter the transmission speed in bits per second as a
number from 1200 to 64000.
Step 8. If this is a dial link, enter the phone number of this gateway half ’s
partner.
Step 9. If this is a dial link, in the Security string field, either leave the
default, or enter a value that HP nodes must use to gain dial link access
to the node you are configuring.
Step 10. Press the [Save Data] key. Proceed to Chapter 10, “Validating Network
Transport and Cross-Validating with SYSGEN,” and press the
[Validate Netxport] key.
Optional Keys
Press the [List NIs] key to list the names and types of
already configured network interfaces.
Press the [Delete NI] to remove a configured network
interface from the configuration file.
Press the [Read Other NI] key to call up a previously
configured Network Interface name.
Fields
Partner’s IP
address
This is the internet protocol (IP) address of the node
that will be the other half of the gateway half you are
configuring. Enter the address in the same format as on
the Point-to-Point Configuration screen.
Partner’s IP
subnet mask Allows you to specify the subnet mask of this gateway
half ’s partner gateway half. The 32-bit mask is grouped
in octets expressed as decimal integers and delimited
by either a period (.) or a space. The mask identifies
which bits of an IP address will be used to define a
subnetwork. To determine these bits, you first need to
estimate how many subnetworks and nodes per
subnetwork you need. For details on deriving an IP
subnet mask, see Chapter 2, “Networking Concepts.”
Home NI name The home NI name will be used by the software to
determine which network address is the source
network address when packets are sent over the
gateway half. The home NI name cannot be either a
gateway half or loopback NI name, but it can refer to
any other type of network interface (LAN, Token Ring,
Point-to-Point, or X.25 network interface).
154
Chapter 9
Configuring a Gateway Half
To Configure a Gatehalf Network Interface
Link name
Name that represents the hardware link. The link
name can have up to eight alphanumeric characters;
the first character must be alphabetic. The link name
must be unique to both the node and the network.
Link type
The link type for a gateway half can be either DD for
direct dial or DC for direct connect.
physical path
The physical path of the gateway half ’s PSI card. See
Chapter 8, “Configuring an X.25 Node,” for information
on the physical path.
Transmission
speed
The line transmission speed is given in bits per second.
For direct connect the value, must be supported by the
cable. Values are 1200, 2400, 4800, 9600, 19200, 38400,
56000, and 64000. The default is 56000.
Phone Number Telephone number of this gateway half ’s partner
gateway half. 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.
D
Three-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.
Spaces, and left and right parentheses ( ) are also
allowed.
To disable outbound dialing, enter an exclamation point
(!) by itself in the phone number field.
Security
string
Chapter 9
This is a string containing up to eight alphanumeric
characters, left justified, with no embedded blanks. The
first character must be alphabetic. A value in this field
is required if the remote (destination) node is an HP
node (dial ID protocol is used). Remote HP nodes must
use the security string to gain dial link access to the
node you are configuring.
155
Configuring a Gateway Half
To Configure a Gatehalf Network Interface
156
Chapter 9
10
Validating Network Transport and
Cross-Validating with SYSGEN
This chapter discusses the validation of the network transport
configuration and cross-validation of NMCONFIG.PUB.SYS with the
system configuration files within SYSGEN.
Validating the network transport. This step checks data consistency
between values entered on different NMMGR data entry screens.
Cross-Validating with SYSGEN.
Cross-validation ensures that there are no conflicts in the use of node
names, device classes, and physical paths.
157
Validating Network Transport and Cross-Validating with SYSGEN
To Validate the Network Transport
To Validate the Network Transport
The following procedure assumes that you have already configured and
validated the Distributed Terminal Subsystem (DTS). The DTS must be
validated before you can validate the network transport (Netxport)
software. Upon configuring the selected screens for your network:
Step 1. Press the [Validate Netxport] key. Refer to the list of screens with the
[Validate Netxport] key.
LAN — Figure 6-2
Token Ring — Figure 6-3
FDDI — Figure 6-4
100VG-AnyLAN — Figure 6-5
100Base-T — Figure 6-6
Point-to-Point Shared Dial — Figure 7-5
Point-to-Point Direct Dial — Figure 7-6
X.25 — Figure 8-3
Gateway Half — Figure 9-2
Logging — Figure 13-2
Messages similar to the following ones will be displayed:
Searching for subsystem validation routine VALIDATENETXPOR
–> VALIDATION OF NETXPORT SUBSYSTEM STARTED
–> VALIDATION OF NETXPORT SUBSYSTEM FINISHED
Copying validated subsystems to backup configuration
file (Press RETURN when done viewing screen contents)
Step 2. See the NS 3000/iX Error Messages Reference Manual for explanations
of any validation errors. After viewing the messages, press [RETURN] to
return to the LAN, Token Ring, FDDI, 100VG-AnyLAN, and 100Base-T
Configuration screen.
Step 3. If you need to configure a network directory, proceed to Chapter 11,
“Configuring the Network Directory.” If you do not need to configure the
network directory, exit NMMGR, and proceed to the section in this
chapter titled “To Cross-Validate in SYSGEN.” To exit NMMGR, press
the [Prior Screen] key on successive screens until you reach the Open
Configuration Directory File screen where you should press the
[Exit Program] key.
158
Chapter 10
Validating Network Transport and Cross-Validating with SYSGEN
To Cross-Validate in SYSGEN
To Cross-Validate in SYSGEN
Cross-validation ensures that there are no conflicts in the use of node
names, device classes, and physical paths between the data currently
contained in NMCONFIG.PUB.SYS and the system configuration data.
To cross-validate, use the SYSGEN facility (OP capability is required).
To use SYSGEN, type the following commands at the MPE prompt
(user input is bold):
sysgen
sysgen> io
io> ld (optional)
io> exit
sysgen> exit
The optional ld (list devices) command allows you to verify the
NMMGR devices that are configured.
Cross-validation is done on the KEEP, TAPE, I/O, and RDCC commands
in SYSGEN. For more information, see System Startup, Configuration,
and Shutdown.
If you have completed the configuration process, proceed to Chapter 14,
“Operating the Network.”
Chapter 10
159
Validating Network Transport and Cross-Validating with SYSGEN
To Cross-Validate in SYSGEN
160
Chapter 10
11
Configuring the Network
Directory
A network directory is used by the node for internetwork routing. Each
entry in a network directory consists of a node name associated with an
IP address, the network type, and an additional address, if necessary.
The network directory uses the internet protocol (IP) address to
transfer data between networks. See Chapter 2, “Networking
Concepts,” for more information on network directory concepts and for
guidelines as to when you need to configure a network directory.
Figure 11-1 shows the screen flow for configuring the network directory
screens. Screens unique to the network directory configuration are
indicated by bold boxed screens. [FUNCTION] denotes the function key
used at a screen to invoke the next screen on the screen flow.
Figure 11-1
Network Directory Configuration Screen Flow
This chapter includes step-by-step instructions to help you perform the
following tasks:
• Open the network directory file.
• Select the update directory function.
• Add nodes to the network directory file.
• Configure path report data for a node.
NOTE
If you used the guided configuration facility to configure an X.25 link,
you will already have configured the network directory for that link.
161
Configuring the Network Directory
To Open the Network Directory
To Open the Network Directory
The Open Configuration/Directory file screen (#1) in Figure 11-2 is the
first screen displayed when you run NMMGR.
Figure 11-2
Open Configuration/Directory File
Step 1. Verify that the correct network directory file name is in the Network
directory file name field.
Step 2. If you have assigned a write access password, enter it in this field. If
you are not using the password feature, leave this field blank.
Step 3. Press the [Open Directry] key. If you are creating the file for the first
time, NMMGR will ask you to verify creation. Press the [Open Directry]
key again to continue.
Fields
Configuration
file name
The only configuration file name the system recognizes
for use by the network subsystem is
NMCONFIG.PUB.SYS. You can, however, create or
modify a configuration file using a different name and
save it as an offline configuration file. You can use
offline configuration files as a means of creating and
storing configurations that you want to use in the
future or that you are preparing for use on a different
system. When you are ready to use an offline
162
Chapter 11
Configuring the Network Directory
To Open the Network Directory
configuration file, rename it as NMCONFIG.PUB.SYS
and reboot the system. (Keep in mind that any file you
use as a configuration file must be successfully
validated before you try to use it.)
Backup
configuration
file name
A backup file name must be specified whenever a
configuration file is opened or created. The default
backup configuration file name is
NMCBACK.group.account. The backup file will be
automatically updated with the contents of the
configuration file each time the configuration file is
successfully validated.
Network
directory
file name
The only network directory file name supported by HP
is NSDIR.NET.SYS. This file is part of a KSAM pair. A
key file is created at the same time as this data file. The
key file will automatically be named using the first six
letters of the network directory file name, appended
with the character K. For example, NSDIRK.NET.SYS is
the name of the key file associated with the data file
NSDIR.NET.SYS. If the name of the data file is less
than six letters long, then the entire file name would be
appended with a K.
Write access
password
The password is an optional feature. If a password has
been assigned, you must enter it in the password field
to update the configuration file or the directory file. It is
still possible to open an existing file without using an
assigned password, but the file will be in read only
mode and no changes will be accepted.
If a password has not been assigned, you should ignore
the password field.
If you want to assign a password for the system you are
configuring, see Using the Node Management Services
(NMS) Utilities.
Chapter 11
163
Configuring the Network Directory
To Select the Update Directory Function
To Select the Update Directory Function
The Network Directory Main screen (#8) in Figure 11-3 is displayed
when you press the [Open Directry] function key at the Open
Configuration/Directory File screen (#1) in Figure 11-2. This screen is
also displayed if a network directory has already been opened and you
type NETDIR in the command window of any screen and press the
[Enter] key.
Figure 11-3
Network Directory Main
Step 1. Press the [Update Dir] function key to modify the contents of the
directory by adding, deleting and updating node names and path
reports.
Function Keys
This screen is the main select screen from which all directory functions
are accessed. The currently opened directory is displayed at the bottom
of all network directory screens. The percentage of the network
directory that is full is shown in the lower right corner of the screen.
Update Dir
Press this function key to go to the Network Directory
Select Node Name screen to add, delete, or modify
network directory node name entries and path reports.
Print Dir
Press this function key to print out a copy of the
directory to formal designator FORMLIST, device class
LP. You can use a file equation for FORMLIST to redirect
164
Chapter 11
Configuring the Network Directory
To Select the Update Directory Function
the output to another device class or disk file. To set a
file equation without leaving NMMGR, enter the
appropriate MPE command in the command window
and press the [Enter] key.
Maint Mode
Press this function key to enter the command interface
to perform directory merging or to expand the size of
your directory. See Using the Node Management
Services (NMS) Utilities for details on maintenance
mode.
Within the maintenance mode interface, command
input is read from the formal designator NMMGRCMD,
which defaults to $STDINX. Type EXIT and press the
[Enter] key to leave maintenance mode.
Chapter 11
165
Configuring the Network Directory
To Add Nodes to the Network Directory File
To Add Nodes to the Network Directory File
The Network Directory Select Node Name screen (#9) in Figure 11-4 is
displayed when you press the [Update Dir] function key at the Network
Directory Main screen (#8) in Figure 11-3. 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 modify information about a
node.
Figure 11-4
Network Directory Select Node Name
Step 1. In the node name field, type in the node name of one of the nodes on
your network for which you want network directory information.
Step 2. Set the global/local flag for the entry by setting the value in the
Global? field. Leave the default (Y) if you want to allow this entry to be
merged into other directories using the MERGEDIR command. Change
the setting to “no” (N) if this is a local entry and should not be copied to
other configurations.
Step 3. Press the [Add] function key. You may add new entries as long as room
remains in the file. If the file fills, you may use the Maintenance Mode
command EXPANDDIR to expand the file. Refer to Using the Node
Management Services (NMS) Utilities for details on maintenance mode.
Step 4. Repeat steps 1, 2, and 3 for each node name you want to enter in the
network directory.
166
Chapter 11
Configuring the Network Directory
To Add Nodes to the Network Directory File
Fields
Node name
The name of the node for which you want network
directory information. The node name field must
contain a fully qualified node name, in the form
nodename.domain.organization, when used to add,
modify, delete, or rename a node.
The node name field when used with the Prev Page
and Next Page function keys allows you to browse
through a specified part of the 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 NIK, and press the [Next Page]
function key, the list of nodes will begin with the first
matching node name, for example
NIKOLAI.FINANCE.IND, and continue through the
rest of the alphabet until all node names between the
letters NIK and Z are listed.
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 are
displayed.
Entries can be configured as either global or local in the
network directory. Global entries (the default) can be
merged into other directories using the MERGEDIR
command. Local entries are not merged into other
network directories. The local entries are used for
configuring localized network directory entries, thus
providing a mechanism to restrict directory data from
being propagated throughout the network.
A situation where this type of restriction could be
useful is when you want to change the configuration for
users on a single host, but not for everyone else. You
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 does not 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 contains information about the new link
not included in the global entry configured for users on
other nodes.
Other uses of local entries include restricting certain
nodes from communicating with the internet, or being
able to direct which way to access remote nodes
Chapter 11
167
Configuring the Network Directory
To Add Nodes to the Network Directory File
depending on your configuration of local entries. When
both local and global entries exist for the same node,
the network transport uses the local entry.
Default value: Y
Range: Y or N
New name
(Required only when renaming an existing node name.)
New name to be assigned to the node with the Rename
function key.
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 rename a node
or when you change the global/local setting of a node.
The new name field can be left blank if you wish to
change only the global/local setting.
Configured
Entries (node
names &
global flag) Display-only fields that show node names and their
global/local flag settings that are already configured in
the directory.
168
Chapter 11
Configuring the Network Directory
To Configure Path Report Data for a Node
To Configure Path Report Data for a Node
The Network Directory Data screen (#10) in Figure 11-5 is displayed
when you press the [Add] or the [Modify] function key at the Select Node
Name screen (#9) in Figure 11-4.
Figure 11-5
Network Directory Data
The function of this screen is to configure path report data for the node
name listed at the top of the screen. One path report is configured for
each NI on a node. Because the maximum number of NIs per node is
eleven (twelve including loopback), each node can contain as many as
eleven path reports.
NOTE
NS/SNA is no longer offered as a product and has been removed from
the Corporate Price List. The product is obsolete with no plans for
support.
Step 1. Verify that the yes and no indicators in the TCP, Checksum for TCP
required, and PXP fields are set correctly.
Step 2. In the IP address field, type in the IP address of the node listed in the
Node name field.
Step 3. In the type field, enter the number that indicates the type of the path:
1 = IP
2 = LAN/IEEE 802.3 (LAN, 100VG, 100BT)
3 = X.25 ACCESS
Chapter 11
169
Configuring the Network Directory
To Configure Path Report Data for a Node
4 = NS/SNA
5 = ETHERNET (LAN 100VG, 100BT)
6 = Token Ring, 100VG/IEEE 802.5
7 = FDDI
Step 4. If appropriate for the type of path you are configuring, enter an address
in the Additional Address field. (Type 1 requires no additional
address. Types 2, 5, and 6 require a station address. Type 3 requires an
X.25 address key. Type 4 requires an LU name.) See additional
explanation under “Fields.”
Step 5. Press the [Save Data] key.
Step 6. Repeat steps 2, 3, and 4 for each path report for the specified node.
If you need to make additional entries in the network directory, press
the [Prior Screen] key to return to the Network Directory Select Node
Name screen. If you have finished making network directory entries,
home the cursor and type EXIT in the command field, then press
[ENTER].
Fields
Transport
services
These three fields describe the transport services that
should be configured in each path.
TCP
TCP must be Y (yes) for all nodes. The
default is Y.
Checksum for
TCP
The checksum setting indicates
whether checksumming is optional (N)
or required (Y) for TCP. If this field is
set to N, then the use of checksums is
not requested when communicating
with this node. If this field is set to Y
then checksums are used when
communicating with this node.
Checksumming is required for
communication to non-HP systems. The
default is N.
PXP
PXP must be Y (yes) for all nodes. The
default is Y.
Note that the selection of transport services here must match the
settings in the remote node’s configuration file. If the checksum enabled
field in the path NETXPORT.GPROT.TCP of this node is set to Y, then
TCP checksum field in the network directory should also be set to Y.
170
Chapter 11
Configuring the Network Directory
To Configure Path Report Data for a Node
IP address
One IP address should be entered for each network
interface configured on the remote node that is directly
reachable from this node. Each address must match an
IP address configured in the remote node’s
configuration file. The path of the screen in the
configuration file that contains IP addresses is
NETXPORT.NI.NIname.PROTOCOL.IP.
Type
A number indicating the type of path to configure:
Chapter 11
1
Select this path type when the NI type
is ROUTER (Point-to-Point); or when the
NI type is LAN and the destination node
supports probe or ARP; or when the NI
type is TOKEN or FDDI and the
destination node supports ARP.
2
Select this path type when the NI type
is LAN, 100VG-AnyLAN or 100Base-T,
the destination node does not support
probe, and 802.3 framing is used.
3
Select this path type when the NI type
is X25.
4
NS/SNA is no longer offered as a
product and has been removed from the
Corporate Price List.
5
Select this path type when the NI type
is LAN, 100VG-AnyLAN or 100Base-T,
the destination node does not support
ARP or probe, and Ethernet framing is
to be used.
6
Select this path type when the NI type
is TOKEN and the destination node does
not support ARP.
7
Select this path type when the NI type
is FDDI and the destination node does
not support ARP.
171
Configuring the Network Directory
To Configure Path Report Data for a Node
Table 11-1
Path Type Configuration
N1 Type
Framing
Protocols
Type
Point-to-Point (Router)
N/A
N/A
1
LAN, 100VG-AnyLAN, or
100Base-T
802.3 and Ethernet
Either Probe or ARP
1
802.3 and Ethernet
Neither Probe nor ARP
5
802.3 only
Not Probe
2
Ethernet only
Not ARP
5
X.25
N/A
N/A
3
NS/SNA
N/A
N/A
4
Token Ring
N/A
ARP
1
N/A
Not ARP
6
N/A
ARP
1
N/A
Not ARP
7
FDDI
Additional
address
A lower-level address, which depends on the type.
Type 1 does not contain lower-level addressing
information. You can leave the field blank, or enter the
keyword NONE.
Types 2, 5, 6, and 7 require the destination node’s
station address, which is a string of six hexadecimal
bytes, separated by dashes (XX-XX-XX-XX-XX-XX).
The station address must correspond to the address
configured on the remote node.
Type 3 requires an X.25 address key, which is an ASCII
string of up to 15 characters. The X.25 address key
must correspond to an X.25 address key entered in the
NETXPORT.NI.NIname.PROTOCOL.X25.SVPATH or the
NETXPORT.NI.NIname.PROTOCOL.X25.PVCPATH
screen for the destination node.
Type 4 requires the destination node’s LU name. The
LU name is taken from the host generation file of the
IBM computer to which this HP 3000 is connected.
172
Chapter 11
12
Configuring Domain Name Files
If you are planning to use the domain name resolver for name to IP
address resolution, you will need to configure a set of ASCII files on
each node that contain needed information. To configure these files, you
use any standard editor to modify existing sample files according to the
instructions in this chapter. See Chapter 2, “Networking Concepts,” for
more information on domain names.
This chapter details:
• How to modify the RSLVSAMP.NET.SYS file and save it as
RESLVCNF.NET.SYS for use as the domain name resolver.
• How to modify the HOSTSAMP.NET.SYS file and save it as
HOSTS.NET.SYS for use as the domain name host file.
• Other files you can configure to make additional information
available to the network.
173
Configuring Domain Name Files
To Create or Modify the Resolver File
To Create or Modify the Resolver File
The resolver file (RESLVCNF.NET.SYS) is an initialization file for the
domain name resolver. It contains information needed by the network
to determine how to resolve a domain name to an IP address. This file is
read by the resolver routines the first time they are invoked by a
process.
To create the resolver file, perform the following steps:
Step 1. Copy the sample file, RSLVSAMP.NET.SYS, to RESLVCNF.NET.SYS.
Step 2. Modify RESLVCNF.NET.SYS using any ASCII editor so that it contains
information about the name servers, domain, and search order for your
network. The keywords included in the file are described under “Fields.”
To modify an already existing RESLVCNF.NET.SYS file, simply use your
editor to update and save the existing file.
Fields
Each entry in the resolver file consists of a keyword followed by a value
separated by white space. The keyword and its associated value must
appear on a single line and the keyword must start the line. Figure 12-1
shows an example of a resolver file. Comment lines start with a pound
sign (#).
domain
Enter the local domain name. Most queries for names
within this domain can use short names relative to the
local domain name. If the host name does not contain a
domain part, the root domain is assumed. If more than
one instance of the domain keyword is present, the last
instance will override.
The domain name is composed of labels, with each label
separated by a period. Each label must start with a
letter or digit, and have as interior characters only
letters, digits, hyphens (-), or underbars (_). A domain
name may have any number of labels, but its total
length, including periods, is limited to 255 characters.
label[.label][...]
Domain names are not case sensitive.
search
174
The search entry is optional and indicates the order in
which domains should be searched for host name
lookup. You should add a search entry if users on this
system commonly try to connect to nodes in other
domains. The search list is limited to six domains with
a total of 256 characters. If more than one instance of
the search keyword is present, the last instance will
override.
Chapter 12
Configuring Domain Name Files
To Create or Modify the Resolver File
Resolver queries will be attempted using each
component of the search path in turn until a match is
found. Note that this process may be slow and will
generate a lot of network traffic if the servers for the
listed domains are not local. Note also that queries will
time out if no server is available for one of the domains.
nameserver
NOTE
Enter the IP address of a name server the resolver
should query. The address must be in dot format, with
leading zeros omitted and a period between each
grouping. See example addresses in Figure 12-1.
It is very important that you omit the leading zeros in the network
addresses that you enter in the domain name resolver files. If you enter
leading zeros here, the domain name resolver will interpret the
numbers as octal numbers.
You can list up to three name servers, but you must use a separate
keyword entry for each. If there are multiple servers, the resolver will
query them in the order listed. If no nameserver entries are present,
the default is to use the HOSTS.NET.SYS file.
If you have no server, do not add any nameserver entries; the resolver
will immediately revert to the HOSTS.NET.SYS file.
Errors in the resolver file will be silently ignored by the resolver
routines.
Figure 12-1
Sample Resolver Configuration File
#resolv.conf file
#
domain loc1.inet.com
search loc1.inet.com inet.com
nameserver 192.255.25.33
nameserver 192.255.354.74
nameserver 192.15.360.75
NOTE
The IP addresses and domain names used in Figure 12-1 are for
purposes of the example only.
Chapter 12
175
Configuring Domain Name Files
To Create or Modify the Hosts File
To Create or Modify the Hosts File
The host name data base file, (HOSTS.NET.SYS), associates internet
addresses with official host names and aliases. This allows a user to
refer to a host by a symbolic name instead of an internet address.
When you have configured the name server, this file serves only as a
backup when the server is not running. In this circumstance, it is a
common practice that HOSTS.NET.SYS contains a few addresses of
machines on the local network.
To create the hosts file, perform the following steps:
Step 1. Copy the sample file, HOSTSAMP.NET.SYS, to HOSTS.NET.SYS.
Step 2. Modify HOSTS.NET.SYS using any ASCII editor so that it contains
information about the nodes on your network.
To modify an already existing HOSTS.NET.SYS file, simply use your
editor to update and save the existing file.
Enter a single line for each host, including the following information:
[internet address] [local host name] [aliases]
A line cannot start with a space. Items are separated by any number of
blanks and/or tab characters. A pound sign (#) indicates the beginning
of a comment.
Network addresses are specified in dot format, with leading zeros
omitted and a period between each grouping. (See example addresses in
Figure 12-2.)
Host names can contain any printable character other than a white
space, newline, or comment character.
NOTE
It is very important that you omit the leading zeros in the network
addresses. If you enter the leading zeros here, the domain name
resolver will interpret the numbers as octal numbers.
176
Chapter 12
Configuring Domain Name Files
To Create or Modify the Hosts File
Figure 12-2
Sample Hosts Configuration File
# This file contains information regarding the known hosts.
#
# The for for each entry is:
# host IP address
local host name
host aliases
#
# Note: the entries cannot be preceded by a blank space.
#
172.0.0.1
localhost loopback me myself local
192.41.12.100
basful.loc1.inet.com
bashful
192.41.11.114
happy.loc1.inet.com
happy
192.41.11.413
queezy.loc1.inet.com
queezy
192.41.112.122 sneezy.loc2.inet.com
sneezy
192.41.124.4
mpmndda.loc1.inet.com
mpmndda
moose
192.41.124.6
mpmndwa.loc1.inet.com
mpmndwa
wabbit
192.41.114.132 mpmtchq.loc1.inet.com
mpmtchq
foo
192.41.110.16
mpmndiv.loc1.inet.com
mpmndiv
zephyr
192.41.110.82
abacus.loc1.inet.com
abacus
spots
192.41.112.161 camelot.loc1.inet.com
camelot
192.41.112.166 bigblue.loc1.inet.com
bigblue
NOTE
The IP addresses and host names used in Figure 12-2 are for purposes
of the example only.
Chapter 12
177
Configuring Domain Name Files
Additional Domain Name Configuration Files
Additional Domain Name Configuration
Files
In addition to the resolver file and the host name data base, three other
files are available to allow you to configure additional information
about your network. Each of these files is provided in sample format in
the NET.SYS account. Each sample file contains an explanation of the
format for the data and a sample entry. The available files and their
functions are described as follows.
Network Name Database
The network name database, NETWORKS.NET.SYS, associates IP
addresses with official network names and aliases. This allows the user
to refer to a network by a symbolic name instead of an internet address.
To configure the network name database, modify the sample file
NETSAMP.NET.SYS.
Protocol Name Database
The protocol name database PROTOCOL.NET.SYS, associates protocol
numbers with official protocol names and aliases. This allows the user
to refer to a protocol by a symbolic name instead of a number. The
protocol number mappings are defined in RFC 1010 Assigned Numbers.
To configure the protocol name database, modify the sample file
PROTSAMP.NET.SYS.
Service Name Database
The service name database, SERVICES.NET.SYS, associates official
service names and aliases with the port number and protocol the
services use. Reserved port numbers 0 through 255 are assigned by
RFC 1010. To configure the service name database, modify the sample
file SERVSAMP.NET.SYS.
178
Chapter 12
13
Configuring Logging
This chapter provides step-by-step instructions for configuring logging.
Logging is configured for the purpose of recording events such as errors
and console commands.
Figure 13-1 shows the screen flow for configuring the logging screens.
Screens unique to logging are indicated by bold boxed screens.
[FUNCTION] denotes the function key used at a screen to invoke the next
screen on the screen flow.
Figure 13-1
Logging Configuration Screen Flow
179
Configuring Logging
This chapter includes step-by-step instructions to help you perform the
following tasks:
• Access the logging configuration screens.
• Modify the logging configuration.
• Enable users for individual logging classes.
• Activate logging.
Logging is configured for the purpose of recording events such as errors
and console commands. You configure logging for each of the
subsystems of NS 3000/iX and for NS 3000/iX links. Each subsystem
includes different classes of events (such as internal errors). You can
record logging to a disk file for later analysis, to the system console so
that the system operator receives the messages, or both.
You can also display logging events at individual users’ list devices.
This may be valuable to allow the network manager to monitor NS
console activity from an alternate terminal. 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. (Take care if you enable users for logging; doing so can
place a strain on system resources.)
The guided configuration process configures logging for you using
defaults. You can also configure or modify the logging subsystem using
either guided or unguided configuration.
180
Chapter 13
Configuring Logging
To Access the Logging configuration Screens
To Access the Logging configuration
Screens
Use the following steps to reach the logging configuration screens:
Step 1. Run NMMGR. The Open Configuration/Directory File screen is
displayed.
Step 2. Run NMMGR. The Open Configuration/Directory File screen is
displayed.
Step 3. Press the [NS] function key. The NS Configuration screen is displayed.
Step 4. Press either the [Guided Config] or the [Unguided Config] function key.
Step 5. Press the [Modify Logging] function key if you are in guided
configuration or the [Go To Logging] function key if you are in unguided
configuration. The first of six logging configuration screens is displayed.
NOTE
HP recommends that you use the default logging configuration values
unless your HP representative tells you otherwise. Not using the
recommended default values may result in the degradation of system
performance.
Chapter 13
181
Configuring Logging
To Modify the Logging Configuration
To Modify the Logging Configuration
The Netxport Log Configuration (1) screen (#61) in Figure 13-2 is
displayed when you press the [Modify Logging] function key at the
Network Transport Configuration screen.
Figure 13-2
Netxport Log Configuration (1) Screen
Use the fields and the function keys of the screen to configure logging
for the subsystems represented on the screen. If the subsystem for
which you want to enable logging does not appear on the first screen,
press the [Next Screen] function key to go to the next Netxport Log
Configuration screen. There are a total of six logging configuration
screens.
Enable or disable logging classes (or accept HP-recommended defaults).
Press the [Save Data] key on each screen to create or modify the data
record. Verify that the data record has been created by checking that
the Data flag is Y.
Fields
Console
Logging
182
The value entered in this field specifies whether or not
logging events for the subsystem and class listed beside
the field will be logged to the system console. A value
must be entered for each subsystem and class listed. A
Y (yes) enables logging to the console, N (no) disables
logging to the console.
Chapter 13
Configuring Logging
To Modify the Logging Configuration
Disk Logging The value entered in this field specifies whether or not
logging events for the subsystem and class listed beside
the field will be logged to a disk file. A value must be
entered for each subsystem and class listed. A Y (yes)
enables logging to a file, N (no) disables logging to a file.
The file name for the log file is NMLGnnnn.PUB.SYS,
where nnnn is a number from 0000 to 9999. All logging
classes in all subsystems are logged to this file. At each
system startup, or when a file is full, the node
management services subsystem (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 NMLG0000.PUB.SYS.
The Netxport Log Configuration (2) screen (#60) in Figure 13-3 is
displayed when you press the [Next Screen] function key from the
Netxport Log Configuration (1) screen (#61) in Figure 13-2.
Figure 13-3
Netxport Log Configuration (2) Screen
Use the fields and the function keys of the screen to configure logging
for the subsystems represented on the screen. If the subsystem for
which you want to enable logging does not appear on this screen, press
the [Next Screen] function key to go to the next Netxport Log
Configuration screen. There are a total of six logging configuration
screens.
Chapter 13
183
Configuring Logging
To Modify the Logging Configuration
Enable or disable logging classes (or accept HP-recommended defaults).
Press the [Save Data] key on each screen to create or modify the data
record. Verify that the data record has been created by checking that
the Data flag is Y.
Fields
Console
Logging
The value entered in this field specifies whether or not
logging events for the subsystem and class listed beside
the field will be logged to the system console. A value
must be entered for each subsystem and class listed. A
Y (yes) enables logging to the console, N (no) disables
logging to the console.
Disk Logging The value entered in this field specifies whether or not
logging events for the subsystem and class listed beside
the field will be logged to a disk file. A value must be
entered for each subsystem and class listed. A Y (yes)
enables logging to a file, N (no) disables logging to a file.
The file name that NMS uses is NMLGnnnn.PUB.SYS,
where nnnn is a number from 0000 to 9999. All logging
classes in all subsystems are logged to this file. At each
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 NMLG0000.PUB.SYS.
The Netxport Log Configuration (3) screen (#70) in Figure 13-4 is
displayed when you press the [Next Screen] function key from the
Netxport Log Configuration (2) screen (#60) in Figure 13-3.
184
Chapter 13
Configuring Logging
To Modify the Logging Configuration
Figure 13-4
Netxport Log Configuration (3) Screen
Use the fields and the function keys of the screen to configure logging
for the subsystems represented on the screen. If the subsystem for
which you want to enable logging does not appear on this screen, press
the [Next Screen] function key to go to the next Netxport Log
Configuration screen. There are a total of six logging configuration
screens.
Enable or disable logging classes (or accept HP-recommended defaults).
Press the [Save Data] key on each screen to create or modify the data
record. Verify that the data record has been created by checking that
the Data flag is Y.
Fields
Console
Logging
The value entered in this field specifies whether or not
logging events for the subsystem and class listed beside
the field will be logged to the system console. A value
must be entered for each subsystem and class listed. A
Y (yes) enables logging to the console, N (no) disables
logging to the console.
Disk Logging The value entered in this field specifies whether or not
logging events for the subsystem and class listed beside
the field will be logged to a disk file. A value must be
entered for each subsystem and class listed. A Y (yes)
enables logging to a file, N (no) disables logging to a file.
The file name that NMS uses is NMLGnnnn.PUB.SYS,
where nnnn is a number from 0000 to 9999. All logging
classes in all subsystems are logged to this file. At each
Chapter 13
185
Configuring Logging
To Modify the Logging Configuration
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 NMLG0000.PUB.SYS.
The Netxport Log Configuration (4) screen (#68) in Figure 13-5 is
displayed when you press the [Next Screen] function key from the
Netxport Log Configuration (3) screen (#70) in Figure 13-4.
Figure 13-5
Netxport Log Configuration (4) Screen
Use the fields and the function keys of the screen to configure logging
for the subsystems represented on the screen. If the subsystem for
which you want to enable logging does not appear on this screen, press
the [Next Screen] function key to go to the next Netxport Log
Configuration screen. There are a total of six logging configuration
screens.
Enable or disable logging classes (or accept HP-recommended defaults).
Press the [Save Data] key on each screen to create or modify the data
record. Verify that the data record has been created by checking that
the Data flag is Y.
Press the [Exit Logging] function key when you have finished modifying
the logging configuration.
186
Chapter 13
Configuring Logging
To Modify the Logging Configuration
Fields
Console
Logging
The value entered in this field specifies whether or not
logging events for the subsystem and class listed beside
the field will be logged to the system console. A value
must be entered for each subsystem and class listed. A
Y (yes) enables logging to the console, N (no) disables
logging to the console.
Disk Logging The value entered in this field specifies whether or not
logging events for the subsystem and class listed beside
the field will be logged to a disk file. A value must be
entered for each subsystem and class listed. A Y (yes)
enables logging to a file, N (no) disables logging to a file.
The file name that NMS uses is NMLGnnnn.PUB.SYS,
where nnnn is a number from 0000 to 9999. All logging
classes in all subsystems are logged to this file. At each
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 NMLG0000.PUB.SYS.
The Netxport Log Configuration (5) screen (#69) in Figure 13-6 is
displayed when you press the [Next Screen] function key from the
Netxport Log Configuration (4) screen (#68) in Figure 13-5.
Figure 13-6
Netxport Log Configuration (5) Screen
Chapter 13
187
Configuring Logging
To Modify the Logging Configuration
Use the fields and the function keys of the screen to configure logging
for the subsystems represented on the screen. If the subsystem for
which you want to enable logging does not appear on this screen, press
the [Next Screen] function key to go to the next Netxport Log
Configuration screen. There are a total of six logging configuration
screens.
Enable or disable logging classes (or accept HP-recommended defaults).
Press the [Save Data] key on each screen to create or modify the data
record. Verify that the data record has been created by checking that
the Data flag is Y.
Press the [Exit Logging] function key when you have finished modifying
the logging configuration.
Fields
Console
Logging
The value entered in this field specifies whether or not
logging events for the subsystem and class listed beside
the field will be logged to the system console. A value
must be entered for each subsystem and class listed. A
Y (yes) enables logging to the console, N (no) disables
logging to the console.
Disk Logging The value entered in this field specifies whether or not
logging events for the subsystem and class listed beside
the field will be logged to a disk file. A value must be
entered for each subsystem and class listed. A Y (yes)
enables logging to a file, N (no) disables logging to a file.
The file name that NMS uses is NMLGnnnn.PUB.SYS,
where nnnn is a number from 0000 to 9999. All logging
classes in all subsystems are logged to this file. At each
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 NMLG0000.PUB.SYS.
The Netxport Log Configuration (6) screen (#316) in Figure 13-7 is
displayed when you press the [Next Screen] function key from the
Netxport Log Configuration (5) screen (#69) in Figure 13-6.
188
Chapter 13
Configuring Logging
To Modify the Logging Configuration
Figure 13-7
Netxport Log Configuration (6) Screen
Use the fields and the function keys of the screen to configure logging
for the subsystems represented on the screen. If the subsystem for
which you want to enable logging does not appear on this screen, press
the [Next Screen] function key to go to the next Netxport Log
Configuration screen. There are a total of six logging configuration
screens.
Fields
Enable or disable logging classes (or accept HP-recommended defaults).
Press the [Save Data] key on each screen to create or modify the data
record. Verify that the data record has been created by checking that
the Data flag is Y.
Console
Logging
The value entered in this field specifies whether or not
logging events for the subsystem and class listed beside
the field will be logged to the system console. A value
must be entered for each subsystem and class listed. A
Y (yes) enables logging to the console, N (no) disables
logging to the console.
Disk Logging The value entered in this field specifies whether or not
logging events for the subsystem and class listed beside
the field will be logged to a disk file. A value must be
entered for each subsystem and class listed. A Y (yes)
enables logging to a file, N (no) disables logging to a file.
The file name that NMS uses is NMLGnnnn.PUB.SYS,
where nnnn is a number from 0000 to 9999. All logging
classes in all subsystems are logged to this file. At each
Chapter 13
189
Configuring Logging
To Modify the Logging Configuration
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 NMLG0000.PUB.SYS.
190
Chapter 13
Configuring Logging
To Enable Users for Individual Logging Classes
To Enable Users for Individual Logging
Classes
The logging screens described previously in this chapter make it
possible to completely configure logging for all subsystems by
traversing only six screens. However, using these screens, it is not
possible to configure logging so that messages generated by specific
logging classes are sent to an individual user’s list device.
The following steps describe the method used to configure users to
receive logging messages. Using this method, you can create a
configuration that allows messages from a single logging class, or a set
of classes, to be sent to a user’s list device.
To do so, you access and update the Logging Configuration Class Data
screen (#67) in Figure 13-7, according to the steps that follow.
Figure 13-8
Logging Configuration: Class Data Screen
Step 1. Type the path name:
LOGGING.SUBnnnn.CLASnnnn
in the command window of any screen and press the [ENTER] key, where
SUBnnnn is the subsystem ID and CLASnnnn is the class name of the
logging class you want directed to the user’s list device.
Chapter 13
191
Configuring Logging
To Enable Users for Individual Logging Classes
Step 2. To enable console logging for this subsystem logging class, enter a Y in
the Enable console logging? field. To disable console logging, enter
an N. Be aware that changing the value in this field will override
the previous setting for the logging class you are configuring.
Step 3. To enable disk logging for this subsystem logging class, enter a Y in the
Enable disk logging? field. To disable console logging, enter an N.
Be aware that changing the value in this field will override the
previous setting for the logging class you are configuring.
Step 4. Enter up to three names, in the form user.account, in the Users
enabled for logging fields. If these fields already contain names it
is because user names were previously configured using this screen. If
less than three user names are configured, type the new user name in
an empty field. If all fields are used, type over one of the old user names
to replace it with the new user name. (Note that the user name you type
over will no longer be enabled to receive these logging messages.)
Step 5. Press the [Save Data] function key to modify the data record.
Step 6. Press the [Prior Screen] key to return to the screen from which you
accessed the Logging Configuration: Class Data screen.
Repeat the above procedure for each subsystem logging class for which
you want to enable users.
CAUTION
Enabling users to receive logging messages can strain system
resources. Hewlett-Packard recommends that you use this capability
sparingly and only for short periods of time.
192
Chapter 13
Configuring Logging
To Activate Logging
To Activate Logging
NetIPC logging is automatically activated at system start up. Network
Services logging is activated when the Network Services are initiated
(that is, when the NSCONTROL START command is issued). Link
manager logging and network transport logging are activated when you
initiate the network transport (NETCONTROL START).
When you are changing a logging configuration for a specific subsystem,
the changes will normally take effect when you perform a
SWITCHNMLOG UPDATE command. In some cases, however, such as
when no logging is currently active, the subsystem may need to be
deactivated and restarted. The steps that must be taken for each
subsystem are shown in Table 13-1.
Table 13-1
Subsystem Activation/Deactivation
Subsystem
Steps
Network Transport
NETCONTROL STOP (if already active)
NETCONTROL START
NetIPC (sockets)
Restart the system (warmstart, coolstart,
update start, or coldstart)
Network Services
NSCONTROL STOP (if already active)
NSCONTROL START
Link Manager
NETCONTROL STOP (if already active)
SNACONTROL STOP;node=nodename (repeat
to the SNA Link/XL Node Manger’s Guide
SNACONTROL START;NODE=nodename
NETCONTROL START
How to use the log messages for troubleshooting is described in the
NS 3000/iX Error Messages Reference Manual. How to format the log
file for examination is described in Using the Node Management
Services (NMS) Utilities.
Chapter 13
193
Configuring Logging
To Activate Logging
194
Chapter 13
14
Operating the Network
After you have completed the configuration process, you are ready to
activate NS. This chapter shows you how to bring up an NS 3000/iX
node and how to shut it down. It assumes you have successfully
completed the configuration steps described previously.
For more detailed information on starting, stopping, and operating an
NS network, see the NS 3000/iX Operations and Maintenance
Reference Manual.
This chapter includes step-by-step instructions to help you perform the
following tasks:
• Start links and services.
• Start software loopback (optional).
• Start the links.
• Start Network Services.
• Test Network Services.
• Shut down links and services.
195
Operating the Network
To Start Links and Services
To Start Links and Services
To Start Software Loopback
Issue the following command (NM capability required) to start software
loopback:
NETCONTROL START;NET=loopbackNIname
This starts up the control process, the transport, and software loopback.
Note: when you use guided NMMGR to create any NI, a loopback
network interface (whose loopbackNIname is LOOP) is automatically
generated. The loopback NI must be started if you wish to perform local
loopbacks or to DSLINE to the local node.
To Start a Link
Issue the following command (NM capability required) to start a link:
NETCONTROL START;NET=NIname
This starts the link identified by the NI name. (If no previous
NETCONTROL START command was issued, then the control process and
transport are also started.) The NIname is the network interface (NI)
name that you supplied during NS configuration. You can start the link
before loopback if you want. Start other links as needed.
To Start a Host-Based X.25 Link
If your network includes X.25 links and you are using host-based
network management, you will need to use the DTCCNTRL command
before you issue the NETCONTROL START command. DTCCNTRL starts
X.25 and PAD support for the DTC/X.25 Network Access card. Issue the
following command (System Operator capability required):
DTCCNTRL DTC=dtcname;CARD=cardnumber;FUNC=function
where function is one of the following:
STARTX25
to start X.25 services;
STARTPADSUP to start PAD support services;
STARTBOTH
to start both X.25 and PAD support services.
For more information on starting host-based X.25 links as well as other
uses of the DTCCNTRL command, see Configuring and Managing
Host-Based X.25 Links.
NOTE
If you are starting an X.25 link for a system using PC-based network
management or if you are not starting an X.25 link, you do not need to
use the DTCCNTRL command.
196
Chapter 14
Operating the Network
To Start Links and Services
To Start the Network Services
Issue the following command (NM capability required) to start the
network services:
NSCONTROL START
This starts the NS 3000/iX Network Services, such as Virtual Terminal,
Network File Transfer, Remote File Access, and Remote Data Base
Access.
You may want to create a startup UDC or command file to activate
software loopback, the link(s), and the network services.
Chapter 14
197
Operating the Network
To Test the Network Services
To Test the Network Services
In order to test that you have successfully configured and brought up
your NS node, HP provides an NS validation test called
QVALNS.NET.SYS. QVALNS is a program which modifies a file called
TQVALNS and streams it as a temporary job (JQVALNS). The job purges
and creates various files, and then runs a program called NSTEST.
NSTEST tests the network services (VT, RFA, RDBA, and NFT).
To run the NS validation test, follow the step below:
Step 1. Run the NS validation test on your own node. This tests the software
loopback capability. Issue the following command, where node is the
node portion of your own node name:
RUN QVALNS.NET.SYS;INFO=node
Step 2. Run the NS validation test on another system on the same network.
Select a remote node on the network and make sure that the link and
the network services are up on the remote system by issuing the
following commands on that node (NM capability required):
NETCONTROL STATUS
NSCONTROL STATUS
If the link or network services have not been started, either pick
another node or start them.
Note the node name of the remote node (given in the last line of output
from the NETCONTROL STATUS command). If you followed the
configuration steps in this manual, the second and third portions of the
node name (the domain and organization) should be the same as the
second and third portions of the local node.
Step 3. Run the NS validation test across the link by issuing the following
command at the local node, where node is the node portion of the
remote node name:
RUN QVALNS.NET.SYS;INFO=node
If you encounter problems, see the NS 3000/iX Operations and
Maintenance Reference Manual and to the NS 3000/iX Error Messages
Reference Manual for information on diagnostics and troubleshooting.
198
Chapter 14
Operating the Network
To Shut Down the Network Services
To Shut Down the Network Services
To shut down NS, issue the following commands (NM capability
required):
DSLINE @;CLOSE
NSCONTROL STOP
NETCONTROL STOP
The DSLINE command shown above closes connections for your session
only.
NSCONTROL STOP allows existing users to continue using the services
until they finish their current task but prevents new uses of the
services by these users or by new users. Therefore, the services are not
actually stopped until all existing users finish using them. You can use
NSCONTROL ABORT instead if you wish to immediately terminate all
use of the services.
NETCONTROL STOP closes all open connections. To determine if there
are any sessions still active, enter: NSCONTROL STATUS. If you do not
want to wait until existing users are finished with their current tasks
before you bring down the system, issue NSCONTROL ABORT and then
NETCONTROL STOP.
If a host-based X.25 link is started, you will also need to issue a
DTCCNTRL command to stop X.25 and PAD support for the DTC/X.25
Network Access card. Enter the DTCCNTRL command after the
NSCONTROL STOP and NETCONTROL STOP commands. Enter the
command as:
DTCCNTRL DTC=dtcname;CARD=cardnumber;FUNC=function
where function is one of the following:
STARTX25
to start X.25 services;
STARTPADSUP to start PAD support services;
STARTBOTH
Chapter 14
to start both X.25 and PAD support services.
199
Operating the Network
To Shut Down the Network Services
200
Chapter 14
A
MPE/V to MPE/iX Migration
This appendix provides a quick overview of the planning and tasks you
will need to do to migrate an NS 3000 network from an MPE/V system
to an MPE/iX system. This appendix assumes that you are migrating
your network as a whole; that is, replacing all MPE V systems with
MPE/iX systems and maintaining the same basic network function.
The following topics are covered by this appendix:
• Differences between NS 3000/V and NS 3000/iX networks.
• An overview of migration tasks.
• Guidelines for converting files.
• Guidelines for reconfiguring a network.
NOTE
For information on migrating X.25 links, refer to the remaining
appendixes of this manual.
201
MPE/V to MPE/iX Migration
Differences Between NS 3000/V and NS 3000/iX
Differences Between NS 3000/V and
NS 3000/iX
There are a number of differences between the way NS is implemented
on MPE V systems and the way it is implemented on MPE/iX systems.
These differences affect the network itself, some of the applications that
users may run over the network, and the command used to obtain
status information about the network. Since it is helpful to understand
these differences as you prepare to move an existing MPE V network to
MPE/iX, they are summarized below.
Differences in the Network
A number of the methods available for making connections to an
MPE V network are not available with NS 3000/iX. If your MPE V
network includes one of these you will need to modify your network
configuration before attempting to use the network on MPE/iX systems.
More information on the specific steps required to modify or remove
unsupported links or connections can be found later in this appendix.
The connection methods that are not supported on NS 3000/iX are:
• Manual dial modems.
• Asynchronous Network Link.
• Bisynchronous link-level protocol.
In addition, while it is possible to access a DS/3000 node directly from
an NS 3000/V node, this capability is not supported on NS 3000/iX. A
user of an NS 3000/iX network who wants to access a DS/3000 node
must first access an MPE V NS node. This is because the DS/3000 code
that was included as a subset of the NS 3000/V code is not provided
with NS 3000/iX.
Differences in Configuration Files
NS 3000/V network configuration files are separated into two files, the
NMCONFIG file, which contains link information, and the NSCONF file,
which contains the transport configuration and other subsystems you
have purchased such as SNA.
NS 3000/iX systems have a single NMCONFIG.PUB.SYS file that
contains information for the network transport, for NetIPC and
link-level logging, and also for the Datacommunications and Terminal
Subsystem (DTS). NMCONFIG.PUB.SYS also contains information for
any other subsystems you have purchased such as SNA.
202
Appendix A
MPE/V to MPE/iX Migration
Differences Between NS 3000/V and NS 3000/iX
Differences in Applications Support
There are also differences in the implementations of NS 3000/V and
NS 3000/iX that will affect certain applications that users may
currently be running on your MPE V network. These differences are as
follows:
• NS 3000/iX supports PTOP for HPDESK only.
On NS 3000/iX PTOP is not supported for applications other than
HPDESK. Network users who are running PTOP programs will
need to convert them to NetIPC/RPM programs before running them
on an NS 3000/iX network. Refer to the NetIPC 3000/XL
Programmer’s Reference Manual and the Using NS 3000/iX
Network Services for more information.
• Nowait I/O RFA is not available with NS 3000/iX.
Privileged mode programs that use nowait I/O Remote File Access
over an MPE V network will need to be modified before they can be
run on an NS 3000/iX network. Refer to the Using NS 3000/iX
Network Services for more information.
Difference in How to Obtain Status Information
On MPE V systems the SHOWCOM command returns status information
about a communication device, and is used to determine line activity
and quality. This information is still available on NS 3000/iX, but is
accessed through a different command. Use the LINKCONTROL STATUS
command to access status information on NS 3000/iX.
Appendix A
203
MPE/V to MPE/iX Migration
Migration Overview
Migration Overview
There are a number of steps that you must take to successfully convert
an MPE V network for use as an MPE/iX network. These tasks are
summarized below, and described in more detail in the remainder of
this appendix. Keep in mind that, depending on the needs of your
installation, you may need to perform additional tasks to complete your
migration. For example, if you are adding communication links that did
not exist on your MPE V network you will also need to configure those
new links.
Before You Start
This guide provides an extensive overview of NS architecture and
networking concepts. It also furnishes configuration design checks,
planning worksheets and examples to aid you in organizing new
network configurations. You should be thoroughly familiar with this
material before you begin your migration.
File Migration Tasks
There are two primary tasks you will need to perform to migrate your
network configuration files. These are:
1. Run the NMMGRVER utility on the old configuration files to convert
them to the current software version. (You will first need to install a
copy of all configuration files used for your NS 3000/V network to the
MPE/iX network). Refer to “File Conversion Guidelines” later in this
Appendix.
2. Run the NMMGR utility on the new configuration file(s) to make any
changes required due to the differences between NS 3000/V and
NS 3000/iX. Refer to “Reconfiguration Guidelines” later in this
Appendix.
Additional Migration Considerations
This appendix does not discuss hardware migration considerations;
however, you will find a description of hardware components in this
manual. Additionally, details of hardware installation and
configuration can be found in the following manuals:
• LANIC Installation and Service Manual.
• LAN Cable and Accessories Installation Manual.
• Central Bus Programmable Serial Interface Installation and
Reference Manual.
204
Appendix A
MPE/V to MPE/iX Migration
File Conversion Guidelines
File Conversion Guidelines
A file conversion utility called NMMGRVER.PUB.SYS allows you to
convert earlier versions of subsystems for use with the current version
of Node Management Services (NMS) by converting the files to an
acceptable format.
When you Need to Convert Files
If you have not successfully converted your files you will be notified that
conversion is necessary when you try either to run NMMGR or to
perform a NETCONTROL command. If you attempt to run NMMGR
against an unconverted configuration file you will receive the message:
Version mismatch found on specified subsystem. Please
run NMMGRVER. (NMGRERR 53)
If you attempt to perform NETCONTROL while using unconverted files
you will receive the following message at the console:
Bad CONFIG File Version
In either case you should stop your current activity and run the
NMMGRVER.PUB.SYS file conversion utility on your configuration files.
WARNING
The conversion procedure that follows will not preserve any
previously configured Distributed Terminal Subsystem (DTS)
configuration values. If you are updating from an earlier
version of MPE/iX at the same time you are migrating from
NS 3000/V to NS 3000/iX, you should see the information under
“To Update From a Previous MPE/iX Version” later in this
Appendix before converting your configuration files.
To Convert Files
You should follow these steps to convert your configuration files using
NMMGRVER:
Step 1. Make a backup copy of the existing configuration files.
Step 2. Install a copy of the MPE/V NMCONFIG file to NMCONFIG.PUB.SYS on
the MPE/iX system, and then install copies of any NSCONF files.
Step 3. Execute NMMGRVER.PUB.SYS by entering:
RUN NMMGRVER.PUB.SYS
The system responds with the following banner:
NMS Configuration File Conversion Utility 32099-11018 V.uu.ff (C)
Hewlett-Packard Co. 1985
Appendix A
205
MPE/V to MPE/iX Migration
File Conversion Guidelines
Step 4. The system will then prompt for the name of the configuration file to be
converted by displaying the message:
Fileset to be scanned?
You can then choose to end the conversion program by pressing the
[RETURN] key, or you can enter one of the following filesets:
filename [.groupname [.acctname]]
@ [.groupname [.acctname]]
@[email protected] [.acctname]
@[email protected]@
NMMGRVER searches for files of type nconf in the specified fileset.
For each file found, it asks:
OK to convert filename.groupname.acctname?
where filename.groupname.acctname is the name of a
configuration file. Enter Y for yes, or enter either N or [RETURN] for no.
Step 5. NMMGRVER checks the configuration file to determine whether it is
an MPE/V or an MPE/iX configuration file. If it is an MPE/iX file the
conversion proceeds without further user input. If the file is an MPE/V
file, however, NMMGRVER prompts you for the type of MPE/V file you
are converting, as follows:
What is the type of this file?
1) MPE V NSCONF
2) MPE V NMCONFIG
3) skip this file
Enter a value between 1 and 3.
Enter the appropriate value.
Step 6. After each file is converted NMMGRVER will display the following
message:
FILE CONVERTED
Continue to enter either Y, N, or [RETURN] until you have converted all
files.
In the conversion process, NMMGRVER will merge the information
from each NSCONF file accepted for conversion with
NMCONFIG.PUB.SYS, and create new (converted) NSCONF files. If you
have converted more than one NSCONF file, you will need to choose the
file that corresponds to the network configuration you want, and
206
Appendix A
MPE/V to MPE/iX Migration
File Conversion Guidelines
rename it as the new NMCONFIG.PUB.SYS. Choose the NSCONF file that
corresponds to the network configuration you want to use as your
NS 3000/iX configuration.
This new NMCONFIG.PUB.SYS file contains your NS configuration in a
format acceptable to MPE/iX. You can now run NMMGR to configure
the DTS subsystem, and to perform any needed modifications to the NS
configuration. See “Reconfiguration Guidelines” later in this appendix.
To Update From a Previous MPE/iX Version
If you are updating from an earlier version of MPE/iX at the same time
you are migrating from NS 3000/V to NS 3000/iX, you will need to
make a choice between reconfiguring your Distributed Terminal
Subsystem (DTS) and reconfiguring your NS network. The choice is
necessary because MPE/V versions of NMCONFIG.PUB.SYS files do not
include DTS configuration values.
You should let the circumstances of your installation determine which
configuration values you preserve. If your NS network is complex, you
may decide to convert the existing MPE/V configuration files, and
reconfigure DTS. In this case you should follow the steps under “File
Conversion Guidelines” earlier in this appendix.
If, on the other hand, your DTS configuration is extensive, you may
decide to migrate your existing MPE/iX configuration files to the new
version of MPE/iX. You will then need to redo your NS network
configuration so that both the NS and DTS configurations are contained
in a single, valid, MPE/iX NMCONFIG.PUB.SYS file. In any case, you
will need to reconfigure either NS or DTS if you are both updating
MPE/iX and converting from an NS 3000/V network to an NS 3000/iX
network.
Appendix A
207
MPE/V to MPE/iX Migration
Reconfiguration Guidelines
Reconfiguration Guidelines
Once your MPE/V NS configuration files have been converted for use
with the MPE/iX version of NS you will need to reconfigure your
network to account for the implementation differences between
NS 3000/V and NS 3000/iX. Run the NMMGR utility against the
configuration file generated by the file conversion process and perform
the following reconfiguration tasks:
• Configure the physical path of all links for your network. This
configuration consists of a channel number (ccc) and subchannel
number (sss) in the form ccc.sss. There is no channel or
subchannel associated with NS on MPE V.
• Since the LAP-B protocol is the only point-to-point link-level protocol
supported on the MPE/iX computer, you must reconfigure links that
were configured as bisynchronous links on NS 3000/V as LAP-B
links, or remove them from the network configuration.
• Configure the Distributed Terminal Subsystem (DTS) according to
the needs of your installation. Refer to Configuring Systems for
Terminals, Printers, and Other Serial Devices for instructions on how
to configure the DTS.
The above configuration tasks are a general summary of what you will
need to do to reconfigure your network to run on MPE/iX. You should be
aware that there are many changes to individual screens and screen
fields. Refer to this guide for information on individual screens and
screen fields.
208
Appendix A
B
NS X.25 Migration: NS 3000/XL
Releases 1.0, 1.1, or 1.2 to
NS 3000/iX Release 2.0 or Later
This Appendix tells how to use the NMMGRVER utility to migrate
(update) a node’s configuration file from NS 3000/XL releases 1.0, 1.1,
or 1.2 to NS 3000/iX release 2.0 or later. This Appendix does not apply if
any MPE V based node is being used as an X.25 server for NS 3000/XL
based machines. Refer to the following appendixes depending on which
X.25 network products you currently have:
• For migrating a configuration file from a node running NS X.25
3000/V Link to a node that will be running NS 3000/iX release 2.0 or
later, refer to Appendix C, “NS X.25 Migration: NS 3000/V to
NS 3000/iX Release 2.0 or Later,” this appendix does not apply if an
MPE V based node is being used as an X.25 server for NS 3000/XL
based machines.
• For migrating a configuration file from any MPE V based node acting
as an X.25 server for NS 3000/XL based machines (including the NS
X.25 3000/XL Server product) to an NS 3000/iX node that will be
running NS 3000/iX release 2.0 or later, refer to Appendix D, “NS
X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX
Release 2.0 or later.”
• For migrating a configuration file from a node running NS 3000/V
PAD to an NS 3000/iX node that will be running NS 3000/iX
release 2.0 or later, refer to Appendix E, “NS X.25 Migration:
NS 3000/V PAD Access to NS 3000/iX Release 2.0 or Later.”
209
NS X.25 Migration: NS 3000/XL Releases 1.0, 1.1, or 1.2 to NS 3000/iX Release 2.0 or Later
To Convert NS 3000/XL 1.X to 2.0 Files
To Convert NS 3000/XL 1.X to 2.0 Files
The following procedure describes the steps necessary for conversion.
Step 1. At the MPE/iX prompt, type:
Run NMMGRVER.PUB.SYS
Step 2. At the prompt, enter the filenames to convert:
Fileset to be scanned?
For example, enter NMCONFIG.PUB.SYS, then press [RETURN]. You can
enter one file name or a set of files in the following form:
filename [.groupname [.acctname]]
@ [.groupname [.acctname]]
@[email protected] [.acctname]
@[email protected]@
Step 3. NMMGRVER creates a backup of the file and displays the following
message:
OK to convert filename.groupname.acctname?_
The backup files are named NMBACKA, NMBACKB, and so on. To proceed,
enter Y for Yes, then press [RETURN]. Press [RETURN] or type N,
[RETURN] to exit.
Step 4. NMMGRVER displays the following message:
Backup file is NMBACKY, temporary file is Nnnnn.
Step 5. The file conversion proceeds without further input. When complete, the
message:
CONVERSION COMPLETED SUCCESSFULLY
is displayed.
Step 6.
Rename the converted file if required. Make any updates to the DTS
subystem using NMMGR as required for your installation to complete
the conversion. For full details, refer to Configuring Systems for
Terminals, Printers, and Other Serial Devices if your system uses
PC-based network management, or to Configuring and Managing
Host-Based X.25 Links if your system uses host-based network
management.
210
Appendix B
C
NS X.25 Migration: NS 3000/V to
NS 3000/iX Release 2.0 or Later
This Appendix tells how to use the NMMGRVER utility to migrate
(update) configuration files from a node running NS X.25 3000/V Link
to a node that will be running NS 3000/iX release 2.0 or later. This
appendix does not apply if an MPE V based node is being used as an
X.25 server for NS 3000/XL based machines. Refer to the following
appendixes depending on which X.25 network products you currently
have:
• For migrating a node’s configuration file from NS 3000/XL releases
1.0, 1.1, or 1.2 to NS 3000/iX release 2.0 or later, refer to Appendix B,
“NS X.25 Migration: NS 3000/XL Releases 1.0, 1.1, or 1.2 to
NS 3000/iX Release 2.0 or Later.”
• For migrating a configuration file from any MPE V based node acting
as an X.25 server for NS 3000/XL based machines (including the NS
X.25 3000/XL Server product) to an NS 3000/iX node that will be
running NS 3000/iX release 2.0 or later, refer to Appendix D, “NS
X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX
Release 2.0 or later.”
• For migrating a configuration file from a node running NS 3000/V
PAD to an NS 3000/iX node that will be running NS 3000/iX
release 2.0 or later, refer to Appendix E, “NS X.25 Migration:
NS 3000/V PAD Access to NS 3000/iX Release 2.0 or Later.”
This Appendix also provides an overview of the differences between
networking functionality on an MPE V and an MPE/iX system you need
to consider for migration.
211
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later
Differences Between NS 3000/V and NS 3000/iX
Differences Between NS 3000/V and
NS 3000/iX
Differences Between NS 3000/V and NS 3000/iX The following
paragraphs summarize differences between NS 3000/V and
NS 3000/iX. Make sure that you account for these differences that could
affect your network when migrating to NS 3000/iX. For information on
operating system migration, refer to the MPE/iX Migration series.
Differences in Hardware
Some NS 3000/V hardware components are not part of an NS 3000/iX
network, such as the ATP for terminal connections, and the INP for
network links.
On an NS 3000/iX network, the DTC provides connections for local or
remote terminals and serial printers. The DTC also provides MPE/iX
access to X.25 through a DTC/X.25 Network Access card. The
Datacommunications and Terminal Subsystem (DTS) LANIC on the
MPE/iX host is used for system-to-system X.25 connectivity.
Unsupported Network Connections
Before migrating your network, identify any unsupported network
connections. The network connections that are not supported on
NS 3000/iX networks are as follows:
• Manual-dial modems.
• Asynchronous SERIAL Network Link and bisynchronous link-level
protocol. To ease migration, you can convert Asynchronous SERIAL
network links to the NS 3000/V Point-to-Point links which can be
converted to NS 3000/iX. Point-to-Point links use the LAP-B
protocol.
• Connections to DS/3000 nodes. DS network services are not
supported on NS 3000/iX. If DS/3000 nodes are part of an existing
network, either migrate them to NS 3000/V or maintain NS 3000/V
connections to the DS/3000 nodes.
Differences in Configuration of Terminals and
Printers
On NS 3000/V networks, the SYSDUMP program is used to perform I/O
configuration which includes configuring terminals, printers, and other
I/O devices and drivers. On NS 3000/iX, terminals and serial printers
are configured on the host (using NMMGR) and on the OpenView
212
Appendix C
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later
Differences Between NS 3000/V and NS 3000/iX
Windows Workstation (using the OpenView DTC Manager software).
For more information on configuration using your OpenView Windows
Workstation, read Using the OpenView DTC Manager.
PAD devices on NS 3000/V are configured (using NMMGR) as part of
the X.25 network configuration. On NS 3000/iX when PC-based
network management is used, PAD devices are configured both on the
host (using NMMGR) and on the OpenView Windows Workstation
(using the OpenView DTC Manager software).
Differences in Configuration Files
NS 3000/V network configuration files are separated into two files, the
NMCONFIG file, which contains link information, and the NSCONF file,
which contains the transport configuration and other subsystems you
have purchased such as SNA.
NS 3000/iX systems have a single NMCONFIG.PUB.SYS file that
contains information for the network transport, for NetIPC and
link-level logging, and also for the Datacommunications and Terminal
Subsystem (DTS). NMCONFIG.PUB.SYS also contains information for
any other subsystems you have purchased such as SNA.
Differences in Network Services
Differences in the support of network services between NS 3000/V and
NS 3000/iX can affect applications that users may currently be running
on the NS 3000/V network. These differences are:
• NS 3000/iX supports PTOP for HPDESK only. Network users who
are running PTOP programs will need to convert them to
NetIPC/RPM programs before running them on an NS 3000/iX
network. Refer to the NetIPC 3000/XL Programmer’s Reference
Manual and the Using NS 3000/iX Network Services for more
information.
• Nowait I/O RFA is not available with NS 3000/iX. Privileged mode
programs that use nowait I/O Remote File Access over an NS 3000/V
network will need to be modified before they can be run on an
NS 3000/iX network. Refer to Using NS 3000/iX Network Services
for more information.
To Obtain Device Status Information
On MPE V systems, the SHOWCOM command returns status information
about communication devices such as Local Area Network Interface
Controllers (LANICs). On NS 3000/iX systems, this information is
available with the LINKCONTROL...;STATUS command.
Appendix C
213
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later
Differences in X.25 Support
Differences in X.25 Support
There are differences in X.25 support between NS 3000/V and
NS 3000/iX which need to be considered when you migrate as described
in the following paragraphs.
1980 Versus 1984 CCITT
NS 3000/V supports CCITT 1980 and NS 3000/iX supports both 1980
and 1984.
General Level 3 Differences
In MPE V X.25, a Reset is sent to initialize or clear a Permanent
Virtual Circuit. In MPE/iX X.25, a Reset is not sent to initialize or clear
a Permanent Virtual Circuit.
MPE V X.25 has a timeout on an interrupt collision. MPE/iX X.25 does
not.
Level 3 Access with NetIPC
In addition to the X.25 features supported on NS 3000/V,
NetIPC 3000/XL provides the following CCITT 1984 features:
• Fast select facility.
• The capability of modifying and reading the facility field in call
packets.
• A new option in IPCDEST (called the destination network address
option) allows you to directly specify an X.25 address or PVC number
instead of a remote node name. See the NetIPC 3000/XL
Programmers Reference Manual for more information. If using this
feature, you can configure POOL as an X.25 Address Key with its
security option set to “O” (outbound) in the X.25 SVC Address Key
Paths screen to allow outbound calls to any destination address.
• IPCCONTROL request 12, reason for error or event, on NS 3000/V
can return 14 (network shutdown), 15 (restart sent by local
network), 16 (level 2 failure), 17 (restart sent by local protocol
module), and 18 (restart packet received). IPCCONTROL on
NS 3000/XL only returns 10 (Clear), 11 (Reset), or 12 (Interrupt).
• In NS 3000/V, IPCSHUTDOWN does not complete until a clear
confirmation arrives. In NS 3000/XL, IPCSHUTDOWN completes
immediately.
• In NS 3000/V, IPCCREATE requires that the network name be
padded with nulls. In NS 3000/XL, IPCCREATE requires the network
name be padded with blanks.
214
Appendix C
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later
Differences in X.25 Support
Facilities
Following are the supported facilities of the DTC/X.25 XL Network
Link.
Supported Facilities
1984 CCITT X.25 Reference
Extended packet sequence number
6.2
Incoming calls barred
6.5
Outgoing calls barred
6.6
Nonstandard default packet size
6.9
Nonstandard default window size
6.10
Flow control parameter negotiation
6.12
Throughput class negotiation
6.13
Closed user group selection (1980 CCITT)
6.14
Fast select request and acceptance
6.16–17
Reverse charging and acceptance
6.18–19
Local charging prevention
6.20
Hunt group
6.25
Supported Facilities with X.25 Level 3 Programmatic Access
Closed user group related facilities
6.14
Bilateral closed user groups
6.15
Network user identification
6.21
Called line modified address notification
6.26
Call redirection and notification
6.25–27
Transit delay selection and indication
6.28
Security
When configuring a host, you can now set security for each remote
system using the Security field on the X.25 SVC Address Key Paths
screen. System to System Local User Groups (LUGs) are now assigned
on the DTC instead of on the host. The LUG provides security in the
same way a CUG does, but you don’t have to subscribe to a CUG.
Appendix C
215
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later
Differences in X.25 Support
Pad Support
For complete information on migrating PAD support from NS 3000/V to
NS 3000/iX Release 2.0 or later, refer to Appendix E, “NS X.25
Migration: NS 3000/V PAD Access to NS 3000/iX Release 2.0 or Later.”
216
Appendix C
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later
To Convert NS 3000/V Files to NS 3000/iX Release 2.0 or Later
To Convert NS 3000/V Files to NS 3000/iX
Release 2.0 or Later
This conversion procedure can be used with NS 3000/V NMCONFIG and
NSCONF files for version V-delta 3 or later.
The procedures that follow are for updating (migrating) configuration
files from a node running NS X.25 3000/V Link to a node that will be
running NS 3000/iX release 2.0 or later. As mentioned, this appendix
does not apply if an MPE V based node is being used as an X.25 server
for NS 3000/XL based machines. When updating a node running NS
X.25 3000/V Link, all NS 3000/V LAN, Point-to-Point, or NRJE as well
as X.25 information will be updated to work with iX 2.0.
NOTE
If you are migrating a configuration file from any MPE V based node
acting as an X.25 server for NS 3000/XL based machines (including the
NS X.25 3000/XL Server product) to an NS 3000/iX node that will be
running NS 3000/iX release 2.0 or later, see Appendix D, “NS X.25
Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or
later.” In that case, you would be merging the server’s NS 3000/V
configuration file with an existing NS 3000/XL 1.X configuration file.
Furthermore, only X.25 information would be updated (not, LAN,
NRJE, or Point-to-Point). The procedures that follow assume that there
is no existing NS 3000/XL NMCONFIG file.
To Delete Secondary NIs (NS/iX Rel. 2.2 or later)
If you are migrating from NS X.25 3000/V (release V delta 7 or later) to
NS 3000/iX release 2.2 or later, make a backup copy of your NS 3000/V
NSCONF file. To migrate to NS 3000/iX release 2.2 or later, you must
delete the secondary NIs in the NS 3000/V NSCONF file before you use
NMMGRVER to convert it.
Appendix C
217
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later
To Save NS 3000/V X.25 Parameters
To Save NS 3000/V X.25 Parameters
Make a list of the following NS 3000/V parameters that must be
re-entered on the DTC.
• VC Assignment from the NS 3000/V screen with the path:
@NETXPORT.NI.niname.PROTOCOL.X25.VCSPEC
• X.25 Network type and Flow Control parms from the NS 3000/V
screen with the path:
@NETXPORT.NI.niname.PROTOCOL.X25.VCSPEC. FLOWCNTL
• L.U.G. Incoming Calls from the NS 3000/V screen with the path:
@NETXPORT.NI.niname.PROTOCOL.X25.LUGSPEC. INLUG
• L.U.G. Outgoing Calls from the NS 3000/V screen with the path:
@NETXPORT.NI.niname.PROTOCOL.X25.LUGSPEC. OUTLUG
218
Appendix C
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later
To Copy NS 3000/V Configuration Files to NS 3000/iX System
To Copy NS 3000/V Configuration Files to
NS 3000/iX System
Restore the NS 3000/V configuration files to the NS 3000/iX system.
Name the NS 3000/V files with the same names they had on the
NS 3000/V node, that is, NMCONFIG.PUB.SYS, and if present,
NSCONF.PUB.SYS.
Remember: This procedure assumes that there is no configuration file
on the NS 3000/iX node yet.
Appendix C
219
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later
To Use NMMGRVER
To Use NMMGRVER
To use the NMMGRVER utility to convert your NS 3000/V
configuration file to NS 3000/iX release 2.0 or later, proceed as follows:
Step 1. At the MPE/iX prompt, type: NMMGRVER.PUB.SYS
Step 2. Do either steps a through c or steps d through g.
If your NS 3000/V node had only an NMCONFIG file (but no NSCONF
files), follow the instructions in steps a through c.
a. To convert the NMCONFIG file enter the file name:
NMCONFIG.PUB.SYS.
b. Enter Y to proceed when prompted.
c. Select type 2 for NMCONFIG type file. The converted file will be saved
with the file name you entered. In this case it is
NMCONFIG.PUB.SYS. This is the only filename that the node will
recognize as its configuration file.
If your NS 3000/V node had one or more NSCONF files, follow the
instructions in steps d through g.
d. Merge your NS 3000/V NSCONF file with the NS 3000/V NMCONFIG
file, and convert it for use with NS 3000/iX release 2.0 or later by
entering a file name, for example: NSCONF1.PUB.SYS.
e. Enter Y to proceed when prompted.
f. Select type 1 for NSCONF type file. NMMGRVER will merge the
contents of the existing NMCONFIG file with the NSCONF file you
specified. It will be saved in the NSCONF file you specified. In this
example, NSCONF1.
g. If you converted more than one NSCONF file, decide which one will be
the network configuration you want on the NS 3000/iX system.
Rename the file to NMCONFIG.PUB.SYS.
To Update X.25 XL System Access Parameters
On the NS 3000/iX host, use NMMGR to change the following
parameters to provide X.25 XL System Access:
1. If migrating from any NS 3000/V release before release V delta 7,
modify the screen at path @NETXPORT.NI.niname.PROTOCOL.X25 to
change the inactivity timer from minutes to seconds.
2. On the screen with the path @LINK, verify that the DTSLINK is
defined.
3. On the screen with the path @LINK.DTSLINK, verify that the
physical path is correctly defined.
220
Appendix C
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later
To Use NMMGRVER
4. On the screen with the path @LINK, add the LINK name and Type
(X25) of the X25 link. Note: to migrate to NS 3000/iX release 2.2
or later, repeat this step and steps 5 through 7 for each
DTC/X.25 Network Access card.
5. On the screen with the path @LINK.linkname, where the LINK name
is the one added in the previous step, add the DTC Node name and
card number for the DTC/X.25 Network Access card.
6. On the screen with the path @NETXPORT.NI.niname.LINK, add the
LINK name entered in Step 4.
7. On the screen with the path @NETXPORT.NI.niname.LINK.linkname,
answer yes or no; then, press the Update key.
To Save X.25 XL System Access Parameters on the
Host
Make a list of the following X.25 XL System Access Parameters on the
host that must be re-entered on the DTC.
• Local Node Name.
• Link Name (the X25 link, not the DTSLINK).
• DTC Node Name.
• DTC Card Number.
• X.25 User Facility Set Parameters.
To Add Other Link Types as Needed
For LAN and Point-to-Point link types, run NMMGR and add the
physical paths. See sections of this manual for the correct values to be
entered for the physical path.
To Verify DTS Configuration on the Host
If the datacommunications and terminal subsystem (DTS) has not been
configured, configure the DTS parameters on the host according to the
requirements of your network. For more information, refer to Getting
Started with the DTC and Configuring Systems for Terminals, Printers,
and Other Serial Devices if you are using PC-based network
management. Refer to Configuring and Managing Host-Based X.25
Links if you are using host-based network management.
Appendix C
221
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later
To Configure the DTC
To Configure the DTC
If you are using PC-based network management, configure the DTC by
using the OpenView DTC Manager at your OpenView Windows
Workstation. For full details, see Using the OpenView DTC Manager.
If you are using host-based network management, configure the DTC
using NMMGR. For full details, see Configuring and Managing
Host-Based X.25 Links.
222
Appendix C
D
NS X.25 Migration: NS 3000/V and
NS 3000/XL Release 1.X to iX
Release 2.0 or later
This Appendix tells how to use the NMMGRVER utility to migrate a
configuration file from any MPE V based node acting as an X.25 server
for NS 3000/XL based machines (including the NS X.25 3000/XL Server
product) to an NS 3000/iX node that will be running NS 3000/iX
release 2.0 or later. This appendix assumes that you want to move the
X.25 configuration from the MPE V-based X.25 server to an existing
NS 3000/XL node and then upgrade it to NS 3000/iX 2.0.
This appendix does not apply if the MPE V node you want to migrate
from is not acting as an X.25 server for NS 3000/XL based machines.
Refer to the following appendixes depending on which X.25 network
products you currently have:
• For migrating a node’s configuration file from NS 3000/XL releases
1.0, 1.1, or 1.2 to NS 3000/iX release 2.0 or later, refer to Appendix B,
“NS X.25 Migration: NS 3000/XL Releases 1.0, 1.1, or 1.2 to
NS 3000/iX Release 2.0 or Later.”
• For migrating a configuration file from a node running NS X.25
3000/V Link to a node that will be running NS 3000/iX release 2.0 or
later, refer to Appendix C, “NS X.25 Migration: NS 3000/V to
NS 3000/iX Release 2.0 or Later.” This appendix does not apply if the
MPE V node you want to migrate from is acting as an X.25 server for
NS 3000/XL based machines.
• For migrating a configuration file from a node running NS 3000/V
PAD to an NS 3000/iX node that will be running NS 3000/iX
release 2.0 or later, refer to Appendix E, “NS X.25 Migration:
NS 3000/V PAD Access to NS 3000/iX Release 2.0 or Later.”
This appendix also provides an overview of the differences between
networking functionality on an MPE V and an MPE/iX system you need
to consider for migration.
223
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later
Differences Between NS 3000/V and NS 3000/iX
Differences Between NS 3000/V and
NS 3000/iX
The following paragraphs summarize differences between NS 3000/V
and NS 3000/iX. Make sure that you account for these differences that
could affect your network when migrating to NS 3000/iX. For system
migration issues, refer to the MPE/iX Migration series for more
information.
Differences in Hardware
Some NS 3000/V hardware components are not part of an NS 3000/iX
network, such as the ATP for terminal connections, and the INP for
network links.
On an NS 3000/iX network, the DTC provides connections for local or
remote terminals and serial printers. The DTC also provides MPE/iX
access to X.25 through a DTC/X.25 Network Access card. The
Distributed Terminal Subsystem (DTS) LANIC on the MPE/iX host is
used for system-to-system X.25 connectivity.
Unsupported Network Connections
Before migrating your network, identify any unsupported network
connections. The network connections that are not supported on
NS 3000/iX networks are as follows:
• Manual-dial modems.
• Asynchronous SERIAL Network Link and bisynchronous link-level
protocol. To ease migration, you can convert Asynchronous SERIAL
network links to the NS 3000/V Point-to-Point links which can be
converted to NS 3000/iX. Point-to-Point links use the LAP-B
protocol.
• Connections to DS/3000 nodes. DS network services are not
supported on NS 3000/iX. If DS/3000 nodes are part of an existing
network, either migrate them to NS 3000/V or maintain NS 3000/V
connections to the DS/3000 nodes.
Differences in Configuration of Terminals and
Printers
On NS 3000/V networks, the SYSDUMP program is used to perform I/O
configuration which includes configuring terminals, printers, and other
I/O devices and drivers. On NS 3000/iX, terminals and serial printers
are configured on the host (using NMMGR) and, if you are using
PC-based network management, on the OpenView Windows
224
Appendix D
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later
Differences Between NS 3000/V and NS 3000/iX
Workstation (using the OpenView DTC Manager software). For more
information on configuration using your OpenView Windows
Workstation, read Using the OpenView DTC Manager.
PAD devices on NS 3000/V are configured (using NMMGR) as part of
the X.25 network configuration. On NS 3000/iX with PC-based network
management, PAD devices are configured both on the host (using
NMMGR) and on the OpenView Windows Workstation (using the
OpenView DTC Manager software). (With host-based network
management, PAD devices are also configured using NMMGR.)
Differences in Configuration Files
NS 3000/V network configuration files are separated into two files, the
NMCONFIG file, which contains link information, and the NSCONF file,
which contains the transport configuration and other subsystems you
have purchased such as SNA.
NS 3000/iX systems have a single NMCONFIG.PUB.SYS file that
contains information for the network transport, for NetIPC and
link-level logging, and also for the Datacommunications and Terminal
Subsystem (DTS). NMCONFIG.PUB.SYS also contains information for
any other subsystems you have purchased such as SNA.
Differences in Network Services
Differences in the support of network services between NS 3000/V and
NS 3000/iX can affect applications that users may currently be running
on the NS 3000/V network. These differences are:
• NS 3000/iX supports PTOP for HPDESK only. Network users who
are running PTOP programs will need to convert them to
NetIPC/RPM programs before running them on an NS 3000/iX
network. Refer to the NetIPC 3000/XL Programmer’s Reference
Manual and the Using NS 3000/iX Network Services for more
information.
• Nowait I/O RFA is not available with NS 3000/iX. Privileged mode
programs that use nowait I/O Remote File Access over an NS 3000/V
network will need to be modified before they can be run on an
NS 3000/iX network. Refer to Using NS 3000/iX Network Services
for more information.
To Obtain Device Status Information
On MPE V systems, the SHOWCOM command returns status information
about communication devices such as Local Area Network Interface
Controllers(LANICs). On NS 3000/iX systems, this information is
available with the LINKCONTROL...;STATUS command.
Appendix D
225
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later
Differences in X.25 Support
Differences in X.25 Support
There are differences in X.25 support between NS 3000/V and
NS 3000/iX which need to be considered when you migrate as described
in the following paragraphs.
1980 vs. 1984 CCITT
NS 3000/V supports CCITT 1980 and NS 3000/XL supports both 1980
and 1984.
General Level 3 Differences
In MPE V X.25, a Reset is sent to initialize or clear a Permanent
Virtual Circuit. In MPE/iX X.25, a Reset is not sent to initialize or clear
a Permanent Virtual Circuit.
MPE V X.25 has a timeout on an interrupt collision. MPE/iX X.25 does
not.
Level 3 Access with NetIPC
In addition to the X.25 features supported on NS 3000/V, NetIPC
3000/XL provides the following CCITT 1984 features:
• Fast select.
• The capability of modifying and reading the facility field in call
packets.
• A new option in IPCDEST (called the destination network address
option) allows you to directly specify an X.25 address or PVC number
instead of a remote node name. See the NetIPC 3000/XL
Programmers Reference Manual for more information. If using this
feature, you can configure POOL as an X.25 Address Key with its
security option set to “O” (outbound) in the X.25 SVC Address Key
Paths screen to allow outbound calls to any destination address.
• IPCCONTROL request 12, reason for error or event, on NS 3000/V
can return 14 (network shutdown), 15 (restart sent by local
network), 16 (level 2 failure), 17 (restart sent by local protocol
module), and 18 (restart packet received). IPCCONTROL on
NS 3000/XL only returns 10 (Clear), 11 (Reset), or 12 (Interrupt).
• In NS 3000/V, IPCSHUTDOWN does not complete until a clear
confirmation arrives. In NS3 000/XL, IPCSHUTDOWN completes
immediately.
• In NS 3000/V, IPCCREATE requires that the network name be
padded with nulls. In NS 3000/XL, IPCCREATE requires the network
name be padded with blanks.
226
Appendix D
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later
Differences in X.25 Support
Facilities
Following are the supported facilities of the DTC/X.25 XL Network
Link.
Supported Facilities
1984 CCITT X.25 Reference
Extended packet sequence number
6.2
Incoming calls barred
6.5
Outgoing calls barred
6.6
Nonstandard default packet size
6.9
Nonstandard default window size
6.10
Flow control parameter negotiation
6.12
Throughput class negotiation
6.13
Closed user group selection (1980 CCITT)
6.14
Fast select request and acceptance
6.16–17
Reverse charging and acceptance
6.18–19
Local charging prevention
6.20
Hunt group
6.25
Supported Facilities with X.25 Level 3 Programmatic Access
Closed user group related facilities
6.14
Bilateral closed user groups
6.15
Network user identification
6.21
Called line modified address notification
6.26
Call redirection and notification
6.25–27
Transit delay selection and indication
6.28
Security
When configuring a host, you can now set security for each remote
system using the Security field on the X.25 SVC Address Key Paths
screen. System to System Local User Groups (LUGs) are now assigned
on the DTC instead of on the host. The LUG provides security in the
same way a CUG does, but you don’t have to subscribe to a CUG.
Appendix D
227
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later
Differences in X.25 Support
PAD Support
For complete information on migrating PAD support from NS 3000/V to
NS 3000/iX Release 2.0, refer to Appendix E, “NS X.25 Migration:
NS 3000/V PAD Access to NS 3000/iX Release 2.0 or Later.”
228
Appendix D
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later
To Convert MPE V-Based Server Files to NS 3000/iX Release 2.0 or later
To Convert MPE V-Based Server Files to
NS 3000/iX Release 2.0 or later
The conversion procedure that follows is for moving an X.25
configuration from an MPE V-based X.25 server (including the NS X.25
3000/XL Server product) to an existing NS 3000/XL node and then
upgrading it to NS 3000/iX 2.0.
Only the X.25 information will be taken from the MPE V-based X.25
server’s NSCONF configuration file. LAN, Point-to-Point, or NRJE
information will be updated from your existing NS 3000/XL NMCONFIG
file. After using NMMGRVER, you will then have to perform some
additional configuration steps that are described in the remainder of
this Appendix.
Appendix D
229
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later
To Delete Secondary NIs (NS/XL Release 2.2 or later)
To Delete Secondary NIs (NS/XL Release 2.2
or later)
If you are migrating from NS X.25 3000/V (release V delta 7 or later) to
NS 3000/iX release 2.2 or later, make a backup copy of your NS 3000/V
NSCONF file. To migrate to NS 3000/iX release 2.2 or later, you must
delete the secondary NIs in the NS 3000/V NSCONF file before you use
NMMGRVER to convert it.
230
Appendix D
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later
To Save NS 3000/V X.25 Parameters
To Save NS 3000/V X.25 Parameters
Make a list of the following NS 3000/V parameters that must be
re-entered on the DTC.
• VC Assignment from the NS 3000/V screen with the path:
@NETXPORT.NI.niname.PROTOCOL.X25.VCSPEC
• X.25 Network type and Flow Control parms from the NS 3000/V
screen with the path:
@NETXPORT.NI.niname.PROTOCOL.X25.VCSPEC. FLOWCNTL
• L.U.G. Incoming Calls from the NS 3000/V screen with the path:
@NETXPORT.NI.niname.PROTOCOL.X25.LUGSPEC.INLUG
• L.U.G. Outgoing Calls from the NS 3000/V screen with the path:
@NETXPORT.NI.niname.PROTOCOL.X25.LUGSPEC.OUTLUG
Appendix D
231
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later
To Copy NS 3000/V Configuration Files to NS 3000/iX System
To Copy NS 3000/V Configuration Files to
NS 3000/iX System
Restore the NS 3000/V NSCONF configuration file to the NS 3000/iX
system. Name the NS 3000/V file with the same name it had on the
NS 3000/V node, that is, NSCONF.PUB.SYS.
Remember: This procedure assumes that there already is an
NS 3000/XL 1.X NMCONFIG.PUB.SYS configuration file on the
NS 3000/iX node. Do not overwrite it with the NS 3000/V version!
232
Appendix D
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later
To Use NMMGRVER
To Use NMMGRVER
To use the NMMGRVER utility to merge your NS 3000/V configuration
file with the NS 3000/iX NMCONFIG file and convert it for use with
release 2.0 or later, proceed as follows:
Step 1. At the MPE/iX prompt, type: NMMGRVER.PUB.SYS
Step 2. Merge your NS X.25 3000/XL Server NSCONF file with the existing
NS 3000/XL NMCONFIG file, and convert it for use with NS 3000/iX
release 2.0 or later by entering a file name, for example:
NSCONF1.PUB.SYS
a. Enter Y to proceed when prompted.
b. Select type 1 for NSCONF type file.
NMMGRVER will merge the contents of the existing NMCONFIG file
with the NSCONF file you specified. It will be saved in the NSCONF
file you specified. In this example, NSCONF1.
Step 3. If you converted more than one NSCONF file, decide which one will be
the network configuration you want on the NS 3000/iX system. Rename
the file to NMCONFIG.PUB.SYS.
To Update X.25 XL System Access Parameters
On the NS 3000/iX host, use NMMGR to change the following
parameters to provide X.25 XL System Access:
1. If migrating from any NS 3000/V release before release V delta 7,
modify the screen at path @NETXPORT.NI.niname.PROTOCOL.X25 to
change the inactivity timer from minutes to seconds.
2. On the screen with the path @LINK, verify that the DTSLINK is
defined.
3. On the screen with the path @LINK.DTSLINK, verify that the
physical path is correctly defined.
4. On the screen with the path @LINK, add the LINK name and Type
(X25) of the X25 link. Note: to migrate to NS 3000/iX release 2.2
or later, repeat this step and steps 5 through 7 for each
DTC/X.25 Network Access card.
5. On the screen with the path @LINK.linkname, where the LINK name
is the one added in the previous step, add the DTC Node name and
card number for the DTC/X.25 Network Access card.
6. On the screen with the path @NETXPORT.NI.niname.LINK, add the
LINK name entered in Step 4.
Appendix D
233
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later
To Use NMMGRVER
7. On the screen with the path @NETXPORT.NI.niname.LINK.linkname,
answer yes or no; then, press the Update key.
To Save X.25 XL System Access Parameters on the
Host
Make a list of the following X.25 XL System Access Parameters on the
host that must be re-entered on the DTC.
• Local Node Name.
• Link Name (the X25 link, not the DTSLINK).
• DTC Node Name.
• DTC Card Number.
• X.25 User Facility Set Parameters.
To Add Other Link Types as Needed
For LAN and Point-to-Point link types, run NMMGR and add the
physical paths. See sections of this manual for the correct values to be
entered for the physical path.
To Verify DTS Configuration on the Host
If the datacommunications and terminal subsystem (DTS) has not been
configured, configure the DTS parameters on the host according to the
requirements of your network. For more information, refer to Getting
Started with the DTC and Configuring Systems for Terminals, Printers,
and Other Serial Devices if you are using PC-based network
management. Refer to Configuring and Managing Host-Based X.25
Links if you are using host-based network management.
234
Appendix D
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later
To Configure the DTC
To Configure the DTC
If you are using PC-based network management, configure the DTC by
using the OpenView DTC Manager at your OpenView Windows
Workstation. For full details, see Using the OpenView DTC Manager.
If you are using host-based network management, configure the DTC
using NMMGR. For full details, see Configuring and Managing
Host-Based X.25 Links.
Appendix D
235
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later
To Configure the DTC
236
Appendix D
Glossary
A
access port A special interface
card in the system cabinet
through which the system console
is connected.
address A numerical identifier
defined and used by a particular
protocol and associated software
to distinguish one node from
another.
address key See X.25 address
key.
address resolution In NS
networks, the mapping of node
names to IP addresses and the
mapping of IP addresses to
subnet addresses.
address resolution protocol
ARP. A protocol used by LAN
links with Ethernet enabled that
provides a means of exchanging
addressing information between
Ethernet nodes.
adjacent A node on a
point-to-point network that is
connected to another node by a
single link with no intervening
nodes.
ARP See address resolution
protocol.
ASCII American National
Standard Code for Information
Interchange. A character set
using 7-bit code used for
information interchange among
data processing and data
Glossary
communications systems. The
American implementation of
International Alphabet No. 5.
asynchronous Term used to
describe a device’s mode of
operation whereby a sequence of
operations are executed
irrespective of time coincidence
with any event. Devices that are
directly accessible by people (for
example, terminal keyboards)
operate in this manner.
attachment unit interface The
cable that runs between each
node (host, DTC, or other device)
and the Medium Attachment
Unit (MAU) that connects it to
the LAN in a ThickLAN
configuration.
AUI See attachment unit
interface.
autodial A dial link in which the
remote node’s telephone number
is automatically dialed by a
modem or other device with this
capability.
B
backbone LAN A thick LAN
cable conforming to the IEEE
802.3 Type 10 BASE 5 standard.
back-to-back configuration A
DTC configuration whereby MPE
users connected to one DTC can
communicate with a non-MPE/iX
system connected to another DTC
via the LAN. (See also Local
Switching)
243
Glossary
backup configuration file A
file that contains a copy of the
information contained in the
configuration file. The backup file,
called NMCBACK.group.account
by default, is updated each time
the configuration file is
successfully validated.
banner A welcome message
displayed on your screen. On the
local OpenView workstation a
banner appears when a remote
connection is established with the
OpenView DTC Manager. A
banner also can appear when you
log on to MPE.
baud Measure of the speed at
which information travels
between devices, most commonly
used in reference to terminal
speed settings. Baud represents
signal events per second. When
one bit represents each signal
change, baud is the same as “bits
per second”.
binary mode Data transfer
scheme in which no special
character processing is
performed. All characters are
considered to be data and are
passed through with no control
actions being taken.
bit Binary digit. A unit of
information that designates one
of two possible states, which are
represented by either 1 or 0.
block mode Terminal processing
mode in which groups, or “blocks,”
of data are transmitted all at
once.
244
BNC T-Connector Connector
used to connect a computer or a
component such as a DTC to the
LAN in a ThinLAN configuration.
boundry See network
boundary.
bps Bits per second. The number
of bits passing a point per second.
broadcast Communication
method of sending a message to
all devices on a link
simultaneously.
byte A sequence of eight
consecutive bits operated on as a
unit.
C
call In X.25, a call is an attempt
to set up communication between
two DTEs using a virtual circuit.
Also known as a virtual call.
call collision A conflict that
occurs at a DTE/DCE interface
when there is a simultaneous
attempt by the DTE and DCE to
set up a call using the same
logical channel identifier.
called address When a node
sends out a call request packet,
the packet contains the address of
the destination node. The address
of the destination node is the
called address.
calling address When a node
receives an incoming call packet,
the packet contains the address of
Glossary
Glossary
the sending node. The address of
the sending node is the calling
address.
carrier A continuous wave that
is modulated by an information
bearing signal.
catenet See internetwork.
CCITT Consultative Committee
for International Telephony and
Telegraphy. An international
organization of communication
carriers, especially government
telephone monopolies, responsible
for developing telecommunication
standards by making
recommendations. No carrier is
required to adhere to a CCITT
recommendation, although most
do so in their own interest.
CIB The channel input/output
bus in the backplane of an
HP 3000.
circuit-switching network A
type of data communications
network wherein a physical and
exclusive link is maintained
between two communicating
devices for the call duration. An
all-digital, circuit-switching
network is often referred to as an
X.21 network.
closed user group An X.25 user
facility that allows
communication to and from a
pre-specified group of users and
no one else.
compatibility mode Processing
mode on HP 3000 Series 900
computers that allows
Glossary
applications written for MPE
V/E-based systems to be ported
and run without changes or
recompilation.
computer network A group of
computer systems connected in
such a way that they can
exchange information and share
resources.
configuration 1) The way in
which computer equipment is
physically interconnected and set
up to operate as a system.
2) The layout of the computer
system, including the MPE table,
memory, and buffer sizes, that
tells which peripheral devices are
(or can be) connected to the
computer and how they can be
accessed.
3) The process of defining the
characteristics of a network in
software. For MPE/iX-based
computers, the operating systems
are configured through use of the
SYSGEN utility. Next, the
distributed terminal subsystem
(DTS) link is configured by using
NMMGR (running on the host)
and may, in addition, be
configured using the OpenView
DTC Manager software (running
on the OpenView Windows
Workstation) depending on the
type of network management you
use. If any of the NS link products
are installed on the system,
network configuration is
accomplished through use of
245
Glossary
NMMGR and, if PC-based X.25
connections are required, through
the OpenView DTC Manager.
configuration file The
configuration file, which you
create and update using the
NMMGR utility, contains:
1) the information that the
network needs in order to
operate.
2) Information necessary for
link-level and NetIPC logging.
3) Information required to
connect terminals and printers to
the system through one or more
DTC.
occurs when you enter SYSGEN
to assure that information
contained in NMCONFIG.PUB.SYS
agrees with system configuration
data.
CSMA/CD Carrier Sense
Multiple Access with Collision
Detect, transmission access
method used by the IEEE 802.3
LAN standard.;
CSN See circuit-switching
network.
CTB The cache transfer bus in
the backplane of an HP 3000.
CUG See closed user group.
D
The only file name that the
system recognizes as the
configuration file is
NMCONFIG.PUB.SYS.
control-X echo Three
exclamation marks (!!!) output
to the terminal screen when the
cancel character (normally
[CTRL]-X) is entered.
control-Y trap User-written
procedure to which control is
passed when the subsystem break
character (normally [CTRL]-Y) is
entered during execution of a
program with subsystem break
enabled.
cross-validate The process of
assuring that information
contained in two locations is
consistent where it is imperative
that it be consistent. For example,
an automatic cross-validation
246
data Basic elements of
information that can be processed
or produced by a computer.
datacommunications and
Terminal Controller See DTC.
data overrun Transmitted data
that is sent faster than the
equipment on the receiving end is
capable of receiving it. The
resulting overflow data is lost. See
also flow control.
Datapac The national public
PSN of Canada.
Datex-P The national public
PSN of West Germany.
D bit Delivery confirmation bit.
Used in the X.25 protocol, the
setting of the D bit in DATA
packets indicates whether
Glossary
Glossary
delivery acknowledgment of the
packet is required from the local
DCE or from the remote DTE. It
therefore allows the choice
between local and end-to-end
acknowledgment.
DCE Data circuit-terminating
equipment. The interfacing
equipment required in order to
interface to data terminal
equipment (DTE) and its
transmission circuit. Synonyms:
data communications equipment,
dataset.
DDX The national public PSN of
Japan.
dedicated printer A printer
that can be used by only one host
on the LAN; the one specified in
the Destination Node Name in
that printer’s configuration
screen.
default gateway One (and only
one) gateway accessible by a
system may be designated as a
default gateway. The network will
then send any transmitted
messages for which it is unable to
locate a destination through
normal means to the default
gateway in a final effort to
determine a transmission route.
demodulation The process by
which the information-bearing
signal is retrieved from a
modulated carrier wave. The
inverse of modulation.
Glossary
destination node name In DTS
configuration, it is either 1) the
name of a host that a user can be
connected to by default (if
switching is not enabled for that
user, or if automatic modem
connection is enabled), or 2) the
name of the only host that can
access a dedicated printer.
device class A collection of
devices that have some
user-defined relation. Device
classes are assigned through use
of the NMMGR configuration
utility.
device-dependent
characteristic A file
specification for which
modifications are restricted
because of the type of device on
which the file is opened. For
example, data directed to
terminals must have a blocking
factor of one.
device driver Software module
that controls a specific type of
input/output device including
NS 3000/iX links.
devicefile A file being input to or
output from any peripheral device
except a disk. MPE allows
operations to be performed on the
device itself as if it were a file.
device independence A
characteristic of the operating
system that allows users to
selectively redirect input/output
from a program, session, or job
without regard to the nature of
the device.
247
Glossary
device name See PAD name.
Dial ID protocol A proprietary
Hewlett-Packard protocol that
provides security checking and
address exchange for dial links.
dial link A connection made
through public telephone lines.
direct-connect device
Asynchronous device that is
connected directly to a DTC
through an RS-232-C or RS-422
cable, with no intervening
communications equipment. Also
referred to as a “local connection.”
direct connection A leased line,
private line, or other
non-switched link in a network.
direct dial A dial link through
which only one remote node can
be reached.
direct-path branching he
process of directly accessing any
screen in NMMGR by entering
path names in the Command:
field. The path name must be
preceded by an at sign (@).
domain name A name
designated for a system in
ARPANET standard format. This
name can be used by other nodes
on the network to access the host
for which it is configured.
download The process of loading
operating code and configuration
files into the DTC’s memory. The
DTC is downloaded by the host
computer for LANs using
248
host-based network management,
and by the PC for DTCs managed
by the OpenView DTC Manager.
driver See device driver.
DTC Datacommunications and
Terminal Controller. The DTC is
a hardware device, configured as
a node on a LAN, that enables
asynchronous devices to access
HP 3000 Series 900 computers.
Terminals can either be directly
connected to the DTC, or they can
be remotely connected through
modem or through a Packet
Assembler Disassembler (PAD).
DTC identifier An identifier
used only within NMMGR to
define the branch of the
configuration file containing
information about a particular
DTC. The identifier must begin
with a letter and can be up to
eight characters long.
DTC Manager See OpenView
DTC Manager.
DTC node name Unique name
used to identify a DTC on the
LAN. Node name format is
nodename.domain.organization,
with each of the three parts
having up to 16 characters and
beginning with either a letter or a
digit.
DTC station address (802.3
address) 2-digit hexadecimal
number used to identify the DTC
as a node belonging to the
network configuration. Also called
the LAN address.
Glossary
Glossary
DTC switching A facility
enabling terminal users to select
any host system that they want to
connect to. DTC switching is
available only when the
OpenView DTC Manager is used
for network management.
DTC/X.25 Network Access he
X.25 software that resides on the
Datacommunications and
Terminal Controller (DTC). To
configure access to an X.25
network, you must configure two
software components: the X.25 iX
System Access (residing on the
HP 3000 host), and the DTC/X.25
Network Access. DTC/X.25
Network Access is configured
through use of the OpenView
DTC Manager software for
systems using PC-based network
management or through NMMGR
for systems using host-based
network management.
DTC/X25 Network Access
Card This is the hardware card
and channel adapter that
provides X.25 Network Access. It
resides in the
Datacommunications and
Terminal Controller (DTC).
DTC/X.25 iX Network Link
Software and hardware that
provides access to private and
public X.25 networks. The X.25 iX
System Access software resides
on an HP 3000 host and is
configured through use of
NMMGR.
Glossary
DTE Data terminal equipment.
Equipment that converts user
information into
data-transmission signals or
reconverts received data signals
into user information. Data
terminal equipment operates in
conjunction with data
circuit-terminating equipment.
DTS Distributed terminal
subsystem. This consists of all the
Datacommunications and
Terminal Controllers (DTCs) on a
LAN, their LANIC cards
(attached to the host), the LAN
cable, and the host and DTC
software that controls all related
DTS hardware.
duplex Transmission method
that allows two-way
communication. If both ends of
the transmission link can
transmit simultaneously, it is
called full duplex. If only one end
can transmit at a time, it is
half-duplex transmission.
E
entry priority The ranking that
identifies the most desirable
route used to reach a given
remote node from a given local
node in a point-to-point network.
environment A session that is
established on a remote node.
escape from data transfer
character A character that
allows a user who is connected to
a host system through the DTC to
break that connection and return
249
Glossary
to the DTC switching user
interface. The default is [CTRL]-K.
This character is used only on
networks managed by the
OpenView Windows Workstation.
facility set A facility set defines
the various X.25 connection
parameters and X.25 facilities
that can be negotiated for each
virtual circuit on a per-call basis.
escape sequence A sequence of
characters beginning with the
escape character and followed by
one or more other characters,
used to convey control directives
to printers, plotters, or terminals.
fast select An optional
packet-switching network facility
by which user data may be
transmitted as part of the control
packets that establish and clear a
virtual connection.
Ethernet A Local Area Network
system that uses baseband
transmission at 10 Mbps over
coaxial cable. Ethernet is a
trademark of Xerox Corporation.
FCS Frame check sequence. A
sequence of bits generated by
X.25 at level 2 that forms part of
the frame and guarantees the
integrity of its frame’s content.
The FCS is also used by the
IEEE802.3 protocol to check the
validity of frames.
event log One of three circular
files stored on the OpenView
workstation containing lists of all
significant events reported by the
DTCs for which it is the owner;
that is, whose operating
software/configuration it has
downloaded.
extended packet sequence
numbering One of the optional
network subscribed facilities that
provides packet sequence
numbering using modulo 128. If
not subscribed, modulo 8 is used.
F
facility An optional service
offered by a packet switching
network’s administration and
requested by the user either at
the time of subscription for
network access or at the time a
call is made. Also known as user
facility.
250
FDDI Fiber Distributed Data
Interface. A set of ANSI
standards that define a 100 Mb/s
timed token passing protocol LAN
that uses fiber optic cable as the
transmission medium. FDDI is a
specification for a high-speed
fiber-optic ring network.
file equation Assignment
statement used to associate a file
with a specific device or type of
device during execution of a
program.
file number Unique number
associated with a file when the
file is opened. The file number is
returned in the FOPEN or
HPFOPEN call used to open the
file. It can be used to access that
file until the file is closed.
Glossary
Glossary
file specification The name and
location of a file. The full
specification for a file includes the
file name, group, and account.
store and forward to transfer
packets between each network
that it belongs to.
G
file system The part of the
operating system that handles
access to input/output devices
(including those connected
through the DTC), data blocking,
buffering, data transfers, and
deblocking.
gateway A node that connects
two dissimilar network
architectures. A gateway can be
either a single node (full gateway)
or two gateway halves.
flow control A means of
regulating the rate at which data
transfer takes place between
devices to protect against data
overruns.
gateway half A node that works
in conjunction with another node
on another network to form an
internetwork. The only protocol
used by gateway halves is the NS
Point-to-Point 3000/iX Link. See
also full gateway.
flow control negotiation One
of the network subscribed
facilities, selected at subscription
time. This facility allows the flow
control parameter to be
negotiated at call set-up time, as
opposed to having a predefined
value.
formal file designator Name
that can be used
programmatically or in a file
equation to refer to a file.
FOS Fundamental operating
system. The programs, utilities,
and subsystems supplied on the
master installation tape that
form the basic core of the
operating system.
full gateway A full gateway is a
node that belongs to more than
one network and has one IP
address for each network. It uses
Glossary
gateway-half link A link
between the two nodes of a
gateway-half pair. Each of the two
nodes of a gateway-half pair has a
configured link (hardware
interface card) that is used for the
gateway half network interface.
The NS Point-to-Point 3000/iX
Link is the only link that can be
used as a gateway-half link.;
gateway-half 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 the link.
guided configuration A method
of configuring a node in which a
subset of the complete NMMGR
interface is presented and
defaults of configurable values
are used automatically.
251
Glossary
H
handshaking A communications
protocol between devices or
between a device and the CPU.
Provides a method of determining
that each end of a
communications link is ready to
transmit or receive data and that
transmission has occurred
without error.
hop count See internet hop
count and intranet hop count
host-based network
management Method of
managing asynchronous
communications for HP 3000
Series 900 computers. All of the
control software is configured on a
single host and is downloaded to
the DTCs that are managed by
that host. With host-based
management, there is a
permanent relationship between
each DTC and the host, and
terminal users can access only
the single system that owns the
DTC their terminal is connected
to.
host-based X.25 The
management of X.25 network
connections from a host computer.
Host-based X.25 network
connections are made through a
DTC Network Access card
installed in a DTC managed by
the host. All configuration is
accomplished using the NMMGR
utility. It is not necessary for a PC
to be part of the LAN when you
are using host-based X.25.
252
host computer The primary or
controlling computer on a
network. The computer on which
the network control software
resides. For HP purposes, it may
also be used to distinguish the
HP 3000 Series 900 system (host)
from the DTC.
HP block mode Block mode
transmission method employed
by HP computers where the
system controls the block mode
handshake. When HP block mode
is used, the user program need
not concern itself with data
transfer protocol.
HP PPN Hewlett-Packard
Private Packet Network.
Hewlett-Packard’s own
packet-switching X.25 network,
which gives users full control over
the administration and security
of their data communications.
HP TS8 A terminal server that
can support up to eight
asynchronous serial connections.
When used in back-to-back
configuration, users can access
HP 3000 MPE/V systems on it via
a DTC.
I
idle device timeout Timeout
defined by the Configure: CPU
command. When the timer lapses,
a device connected to the DTC
user interface that is still inactive
will be disconnected.
Glossary
Glossary
IEEE 802.3 A standard for a
broadcast local area network
published by the Institute for
Electrical and Electronics
Engineers (IEEE). This standard
is used for both the ThinLAN and
ThickLAN implementations of
the LAN.
IEEE 802.3 multicast address
A hexadecimal number that
identifies a set of nodes. This
address is used for multicast
delivery.
IEEE 802.3 nodal address A
unique hexadecimal number that
identifies a node on an IEEE
802.3 LAN.
IEEE 902.5 A standard for a
token ring network published by
the Institute for Electrical and
Electronics Engineers (IEEE).
This standard is used for the
Token Ring 3000/iX Network
Link.
initialization string A sequence
of control characters used to
initialize a terminal, printer, or
plotter when a connection is
established from a host on the
network.
a packet must pass through in
moving from source node to
destination.
internet protocol A protocol
used to provide routing between
different local networks in an
internetwork, as well as among
nodes in the same local network.
The internet protocol corresponds
to layer 3, the network layer, of
the OSI model. See also IP
address.
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.
internetwork Two or more
networks joined by gateways,
bridges, or routers.
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
point-to-point network.
interactive communications
Processing that allows users to
enter commands and data at the
terminal and receive an
immediate response.
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.
internet hop count The
number of full gateways plus the
number of gateway-half links that
intrinsic System routine
accessible by user programs
which provides an interface to
Glossary
253
Glossary
operating system resources and
functions. Intrinsics perform
common tasks such as file access
and device control.
IP See internet protocol.
IP address Internet protocol
address. An address used by the
Internet Protocol to perform
internet routing. A complete IP
address comprises a network
portion and a node portion. The
network portion of the IP address
identifies a network, and the node
portion identifies a node within
the network.
IP subnet mask See subnet
mask.
ISO International Standards
Organization. An international
federation of national standards
organizations involved in
developing international
standards, including
communication standards
L
LAN Local Area Network. A
collection of data communication
systems sharing a common cable
whereby each system can
communicate directly with
another.
LAN address See station
address.
LANIC See Local Area
Network Interface Controller.
254
LANIC physical path The
physical location (slot number) of
the LANIC within the SPU.
LANIC self-test A ROM-based
program on a LANIC card that
tests and reports the status of the
LANIC hardware.
LAP Link access protocol. The
data link protocol specified by
older versions (prior to 1980) of
X.25 at level 2 but still permitted
and therefore usable. All new
implementations of X.25 must use
LAP-B, and all old
implementations must migrate to
LAP-B at a future date.
LAP-B Link access protocol balanced. The data link protocol
specified by the 1980 version of
X.25 at level 2 that determines
the frame exchange procedures.
LAP-B must also be used over
direct-connect NS Point-to-Point
3000/iX Links.
LCI Logical channel identifier.
Local value on a network node
which identifies the channel used
to establish a virtual circuit (SVC
or PVC) through an X.25
network.
ldev See logical device
number.
leased line Data-grade
telephone line leased directly to a
subscriber and allocated
specifically for the subscriber’s
needs.
Glossary
Glossary
line speed Speed at which data
is transferred over a specific
physical link (usually measured
in bits or kilobits per second).
link name The name that
represents a hardware interface
card. The link name can contain
as many as eight characters. All
characters except the first can be
alphanumeric; the first character
must be alphabetic.
Local Area Network Interface
Controller (LANIC) A
hardware card that fits into the
backplane of the HP 3000
Series 900 computer and provides
a physical layer interface for local
area networks.
local connection See direct
connection.
local node The computer that
you are configuring or that you
are logged on to.
local switching Feature of the
DTC which permits back-to-back
configuration (for connections to
an HP 3000 MPE/V host), using
two ports of the same DTC.
local user group A list defined
for a particular DTC and card
that specifies which remote nodes
this DTC can send data to and
also which remote nodes this DTC
can receive data from. (See also
Closed User Group).
logging The process of recording
the usage of network resources.
Events can be logged to both the
OpenView workstation and to the
MPE host.
logging class A number defining
the severity of any given event
logged. An operator uses the
logging classes to specify which
events are to be logged. Class 1
(catastrophic event) is always
logged.
logical device number (ldev)
A value by which the operating
system recognizes a specific
device. All DTC devices that are
configured as nailed devices
through the NMMGR
configuration have ldev numbers
permanently assigned. The DTC
devices can then be accessed
programmatically through use of
their ldev number. Non-nailed
devices have ldev numbers that
are assigned from a pool of
available ldev numbers for the
life of their connection to a
system. You cannot access
non-nailed devices
programmatically.
log off The termination of a job
or session.
log on The process of initiating a
job or session.
logon device See
session-accepting device.
loopback The routing of
messages from a node back to
itself.
Glossary
255
Glossary
LUG See local user group.
M
map, network A drawing that
shows the topology of the
network. For networks managed
by the OpenView DTC Manager, a
network map must be created
through use of the OVDraw
capability provided with the
management software. A network
map is also a hardcopy drawing
used when planning a network. It
shows network topology, node and
network names, addresses,
network boundaries (for an
internetwork map), and link
types.
mapping A set of characteristics
that describe a route taken by
messages to reach a destination
node. This set of characteristics is
configured with NMMGR at every
node on a point-to-point network.
One mapping is configured at
each node for every other node on
the network to which messages
will be sent.
MAU See medium attachment
unit.
M bit More data bit. Setting this
bit in a DATA packet indicates
that at least one more DATA
packet is required to complete a
message of contiguous data.
medium attachment unit A
device attached to a ThickLAN
coaxial cable that provides the
256
physical and electrical connection
from the AUI cable to the coaxial
cable.
MIT Master installation tape.
Magnetic tape containing the
fundamental operating system for
a HP 3000 Series 900 computer.
modem Modulator/demodulator.
A device that modulates and
demodulates signals. Primarily
used for modulating digital
signals onto carriers for
transmission and for performing
the inverse function at the
receiving end. Modems are
essential for transmitting and
receiving digital signals over
telephone lines.
modulo Value used as the
counting cycle for determining
the send sequence number (N(S))
of frames sent across an X.25
network.
modulation Process in which
certain characteristics of a carrier
signal are altered in accordance
with the changes of an
information-bearing signal.
MPE/iX MultiProgramming
Executive/integrated POSIX. The
operating system of HP 3000
Series 900 computers. The
NS 3000/iX network services
operate in conjunction with the
MPE/iX operating system.
multiplexer A device that allows
multiple communication links to
use a single channel.
Glossary
Glossary
N
nailed device A device with a
permanently associated ldev that
was assigned through the
NMMGR configuration of the host
system on which the association
is established. Nailed devices can
be accessed programmatically
through their ldev number. In
contrast, non-nailed devices have
ldev numbers that are assigned
from a pool of available ldev
numbers for the life of their
connection to a system.
native mode The run-time
environment of MPE/iX. In
Native Mode, source code has
been compiled into the native
instruction set of the HP 3000
Series 900 computer.
neighbor gateway A gateway
that is in the same network as a
given node.
NetIPC Network Interprocess
Communication. Software that
enables programs to access
network transport protocols
network A group of computers
connected so that they can
exchange information and share
resources.
network address This can be
either 1) the network portion of
an IP address as opposed to the
node portion, or 2) when referring
to X.25 networks, it is a node’s
X.25 address.
Glossary
network boundary The logical
division between networks in an
internetwork.
network directory A file
containing information required
for one node to communicate with
other nodes in 1) an internetwork,
2) an X.25 network, or 3) a
network that contains non-HP
nodes. The active network
directory on a node must be
named NSDIR.NET.SYS.
network interface (NI). The
collective software that enables
data communication between a
system and a network. A node
possesses one or more network
interfaces for each of the
networks to which it belongs.
Network interface types are LAN,
point-to-point (router), X.25,
token ring, SNA, loopback, and
gateway half. The maximum
number of supported NIs is 12,
one of which is reserved for
loopback.
network management The
collective tasks required to
design, install, configure,
maintain, and if necessary,
change a network.
network map A drawing that
shows the topology of the
network. For networks managed
by the OpenView DTC Manager, a
network map must be created
through use of the OVDraw
capability provided with the
management software. A network
map is also a hardcopy drawing
used when planning a network. It
257
Glossary
shows network topology, node and
network names, addresses,
network boundaries (for an
internetwork map), and link
types.
contained in the configuration file
(NMCONFIG.PUB.SYS). The
backup file is updated each time
the configuration file is
successfully validated.
Network Services NS. Software
application products that can be
used to access data, initiate
processes, and exchange
information among nodes in the
network. The NS 3000/iX
Network Services include RPM,
VT, RFA, RDBA, and NFT.
NMCONFIG.PUB.SYS A file
that contains all the network
configuration data for the
HP 3000 Series 900 computer on
which it resides. It includes
information about the DTCs that
can access the system as well as
information about any Network
Services (NS) products running
on the system. This is the only file
name allowed.
network subscribed facilities
A set of parameters that the user
chooses when he subscribes to the
X.25 network; they include flow
control negotiation, use of D-bit,
throughput class negotiation and
extended packet sequence
numbering.
network transport Software
that corresponds to layers 4 and 3
of the OSI network architecture
model. The function of this
software is to send data out over
the appropriate communications
link, to receive incoming data,
and to route incoming or outgoing
data to the appropriate
destination node.
NFT Network File Transfer. The
network service that transfers
disc files between nodes on a
network.
NI See network interface.
NMCBACK.PUB.SYS The
default file name for the file that
contains a copy of the information
258
NMDUMP Node management
services trace/log file analyzer. A
utility used to format log and
trace files.
NMMAINT Node management
services maintenance utility. A
utility that lists the software
module version numbers for all
HP AdvanceNet products,
including NS 3000/iX. It detects
missing or invalid software
modules.
NMMGR Node management
services configuration manager. A
software subsystem that enables
you to configure DTC connectivity
and network access parameters
for a HP 3000 Series 900
computer.
NMMGRVER Node
management services conversion
utility. A conversion program that
converts configuration files
Glossary
Glossary
created with NMMGR from an
earlier version to the latest
format.
NMSAMP1.PUB.SYS Sample
configuration file supplied with
FOS that can be used as a
template for DTS configuration.
node A computer that is part of a
network. The DTC is also
considered to be a node and has
its own address.
node address The node portion
of an IP address, which consists of
a node portion and a network
portion.
node management services
configuration manager See
NMMGR.
node name A character string
that uniquely identifies each
system in a network or
internetwork. Each node name in
a network or internetwork must
be unique; however, a single node
can be identified by more than
one node name.
node names list List defined on
the OpenView workstation and
subsequently downloaded to all
DTCs for which it is the “owner.”
The list specifies all the HP 3000
Series 900 hosts on the LAN that
are accessible from the DTCs.
non-adjacent Describes a node
on an NS Point-to-Point 3000/iX
network that is separated from a
given node by intervening or
intermediate node.
Glossary
non-nailed device A session
accepting device that is not
permanently associated with an
ldev number at configuration
time. When the user at such a
device logs on to a HP 3000
Series 900 , an ldev is assigned
from a pool of ldevs set aside for
this purpose at configuration
time. The association between a
non-nailed device and this
temporarily assigned ldev exists
only for the duration of the
session. One advantage of the use
of non-nailed device connections
is that configuration is simplified,
since it is not required that each
non-nailed device be individually
configured.
NS 3000/iX A Hewlett-Packard
data communication product that
provides networking capabilities
for HP 3000 Series 900
minicomputers. NS 3000/iX
consists of one or more links and
network services.
NS 3000/iX Link Software and
hardware that provides the
connection between nodes on a
network. Some of the NS 3000/iX
links available are the ThinLAN
3000/iX Link and its ThickLAN
option, the DTC/X.25 iX Network
Link, the NS Point-to-Point
3000/iX Link, and the Token Ring
3000/iX Network Link.
NS 3000/iX Network Services
Software applications that can be
used to access data, initiate
processes, and exchange
259
Glossary
information among nodes in a
network. The services are RPM,
VT, RFA, RDBA, and NFT.
NS Point-to-Point 3000/iX
Link Hardware and software
necessary to create networks in
which data is transmitted from
node to node over a defined route
until it reaches its destination.
This technique is referred to as
store and forward. Systems in a
point-to-point network are
connected by means of leased or
dial-up telephone lines. HP 3000
systems attach to the
point-to-point network via
HP 3000 Programmable Serial
Interface (PSI) cards that fit into
the back of each system’s SPU.
NSDIR.NET.SYS Name of the
active network directory file. See
Also network directory.
O
octet An eight-bit byte operated
upon as an entity.
OpenView DTC Manager
OpenView Windows application
that enables you to configure,
control, monitor, and troubleshoot
the operation of the
datacommunications and
terminal subsystems on the LAN.
OpenView Admin An
OpenView windows program that
enables you to configure how your
OpenView Windows applications
will function. For example, it
enables you to set a default map
for the OpenView DTC Manager.
260
OpenView Draw An OpenView
windows program that enables
you to draw the network map,
and to label the components on it.
OpenView Run An OpenView
windows program that covers
most of the control features used
by the DTC Manager, including
monitoring and diagnostic
functions.
OpenView Windows The set of
three programs: OV Admin, OV
Draw and OV Run, running on
the OpenView workstation under
MS Windows, that acts as the
platform for all OpenView
applications, such as DTC
Manager.
OpenView Windows
Workstation The personal
computer that provides software
downloads to enable operation of
the Datacommunications and
Terminal Controller (DTC). The
configuration software that runs
on this workstation is called the
OpenView DTC Manager
software.
OSI model Open Systems
Interconnection model. A model of
network architecture devised by
the International Standards
Organization (ISO). The OSI
model defines seven layers of a
network architecture, with each
layer performing specified
functions.
Glossary
Glossary
P
packet A block of data whose
maximum length is fixed. The
unit of information exchanged by
X.25 at level 3. There are DATA
packets and various control
packets. A packet type is
identified by the encoding of its
header.
packet exchange protocol
PXP. A transport layer protocol
used in NS 3000/iX links to
initially establish communication
between nodes when NetIPC
socket registry is used.
packet-switched network
name The name of a data
communication network adhering
to the CCITT X.25
recommendation. This can be a
PDN or a private network, such
as the HP PPN.
PAD (packet
assembler/disassembler) A
device that converts
asynchronous character streams
into packets that can be
transmitted over a packet
switching network (PSN).
PAD name A name of up to eight
characters that is associated with
a configured PAD device. The
PAD name is known to both the
DTC and the host systems that
the device can access.
PAD profile Terminal or printer
profile that specifies the
configuration characteristics for
PAD-connected devices.
Glossary
partner gateway half When
gateway halves are used, two
gateway halves are required in
order to provide communication
between two networks. Each is
the partner of the other.
path name When configuring
with NMMGR, you can type a
string in the COMMAND: field on
display screens to branch to
another screen. Each screen has a
unique path name that
corresponds to its location in the
hierarchy of configuration screens
presented by NMMGR.
PDN Public data network. A data
communication network whose
services are available to any user
willing to pay for them. Most
PDNs use packet switching
techniques.
point-to-point A link that
connects either two nodes in an
NS Point-to-Point 3000/iX
network or two gateway halves.
port An outlet through which a
device can be connected to a
computer, consisting of a physical
connection point and controlling
hardware, controlling software,
and configurable port
characteristics. Ports can be
thought of as data paths through
which a device communicates
with the computer.
Precision Architecture The
hardware design structure for the
HP 3000 Series 900 computer
family.
261
Glossary
printer name Character string
of up to 16 characters specified in
the DTC Manager configuration
(for networks using OpenView
Network Management) to define
a printer by name. Can be shared
by several printers (port pool).
probe proxy server A node on
an IEEE 802.3 network that
possesses a network directory. A
probe proxy server can provide a
node with information about
other nodes on the same or other
networks of an internetwork.
printer profile A set of
configuration characteristics that
can be associated with one or
more printers through the
NMMGR configuration. Printer
profile specifications include the
printer type, line speed, device
class assignment, and other
values relevant to printers
connected through a DTC.
profile method of grouping
device connection specifications
and characteristics so that the set
of characteristics can be easily
associated with groups of like
devices. See also printer profile,
terminal profile.
printer type A collection of
characteristics that cause a
printer connected to a HP 3000
Series 900 system to act and react
in a specified manner. You can
configure a printer to use one of
the system-supplied printer types
or you can create custom printer
types using workstation
configurator.
Programmable Serial
Interface PSI. A hardware card
that fits into the backplane of the
HP 3000 Series 900 computer. It
provides a physical layer
interface for NS Point-to-Point
3000/iX Links.
privileged mode A capability
assigned to accounts, groups, or
users allowing unrestricted
memory access, access to
privileged CPU instructions, and
the ability to call privileged
procedures.
probe protocol An HP protocol
used by NS 3000/iX IEEE 802.3
networks to obtain information
about other nodes on the network.
262
program captive device See
programmatic device.
programmatic device A device
operating under control of a
program running on a computer.
Programmatic devices can be
used for input, output, or both,
depending on the device and how
it is opened by the controlling
program.
protocol A set of rules that
enables two or more data
processing entities to exchange
information. In networks,
protocols are the rules and
conventions that govern each
layer of network architecture.
Glossary
Glossary
They define what functions are to
be performed and how messages
are to be exchanged.
PSI See Programmable Serial
Interface.
PSN Packet-switching network.
Any data communication network
using packet-switching
techniques wherein data is
disassembled into packets at a
source interface and reassembled
into a data stream at a
destination interface. A public
PSN offers the service to any
paying customer.
PSS Packet-Switching System.
The national public PSN of the
United Kingdom.
PVC Permanent virtual circuit. A
permanent logical association
between two physically separate
DTEs that does not require call
set-up or clearing procedures.
PXP See packet exchange
protocol.
Q
Q bit Qualified bit. When set in
DATA packets the Q bit signifies
that the packet’s user data is a
control signal for the remote
device, not a message for its user.
QuickVal A software program
that tests whether Network
Services are operating correctly
between nodes.
Glossary
R
RDBA Remote data base access.
A 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 connect device
Asynchronous device that is
connected to a DTC indirectly,
using a modem and telephone
hook-up, or a PAD.
remote node A node on an
internetwork other than the node
you are currently using or
referring to.
retransmission count (N2) The
maximum number of times a
frame will be retransmitted
following the expiration of the
retransmission timer, T1.
retransmission timer (T1)
Length of time the transmitter
will wait for an acknowledgment
from the destination address
before attempting to retransmit
the frame. When choosing this
value, factors like the line speed
and maximum frame size should
be taken into account.
RFA Remote file access. A
network service that allows users
to access files and devices on
remote nodes.
263
Glossary
router network See
point-to-point.
routing The path that packets,
or fragments of a message, take
through a network to reach a
destination node.
RPM Remote process
management. A network service
that allows a process to
programmatically initiate and
terminate other processes
throughout a network from any
node on the network.
RS-232-C Electronic Industries
Association (EIA) level 1 protocol
specification that defines
electrical circuit functions for 25
connector pins. HP provides two
implementations of this standard:
a 3-pin version for direct
connections up to a distance of 15
meters (50 feet), and a version
which makes use of additional
circuits and can be used for either
modem or direct connections.
RS-422 Electronic Industries
Association (EIA) level 1 protocol
specification implemented by HP
in a 5-pin version which can be
used for direct device connection
up to a distance of 1500 meters
(4000 feet).
S
security string An
alphanumeric character string
that functions as a password for
dial links. The security string is
used by the dial IP protocol.
264
serial device Any device that is
attached to and communicates
with a computer by means of a
serial transmission interface.
Terminals, printers, and plotters
are among the devices that
communicate serially with
HP 3000 Series 900 computers.
serial transmission Method of
transferring data in which
characters are transmitted one
bit at a time and received one bit
at a time in the order of
transmission. This transmission
scheme is employed by devices
connected to the system via the
DTC.
session-accepting device A
terminal or personal computer
running in terminal-emulation
mode that is able to establish an
interactive (conversational)
session with an HP 3000
computer. Also referred to as a
logon device.
shared dial A dial link that
provides connection to more than
one remote system, although to
only one at a time.
shared-line access Feature that
allows two or more HP 3000
Series 900 hosts to use the same
DTC/X.25 Network Access card
on a DTC to access an X.25
network.
SIC Serial interface card. Card
installed in the front of the DTC
that acts as an interface between
a corresponding connector card
(CC) and the DTC’s processor.
Glossary
Glossary
slaved device A device that
shares the same DTC port as
another device and is connected
to the other device, referred to as
its master, by a cable. The actions
of the slaved device are controlled
by the master device.
spooled device A printer that is
accessed through the spooling
facility. The spooling facility
allows a nonsharable device to be
shared among several users by
temporarily storing output data
on disc and managing the
selection of output spool files
destined for the spooled device.
start bit Data bit used to signal
the start of a character being
transmitted in an asynchronous
communication mode.
station address 12-digit
hexadecimal link-level address
used by the IEEE 802.3 protocol.
Every node on an IEEE 802.3
network has its own station
address.
stop bit Data bit used to signal
the end of a character being
transmitted in an asynchronous
communication mode.
store and forward A technique
in which messages are passed
from one node to another in a
network to reach their
destination. Point-to-point
networks use the store and
forward technique to transmit
messages.
Glossary
subnet Another name for a
network, especially if the network
is part of an internetwork. The
word subnet is also a synonym for
intranet.
subnet mask Grouping of bits
that determines which bits of the
IP address will be used to define a
subnetwork. The subnet mask is
configured using the NMMGR
utility and specified in the same
format as an IP address.
SVC Switched virtual circuit.
Path through an X.25 network
that is established at call set-up
time.
switching See DTC switching.
Switching user interface User
interface available when DTC
switching is enabled that allows
terminal users to choose the
HP 3000 Series 900 computer
with which they want to establish
a communication link.
synchronous A mode of
operation or transmission
whereby a continuous data
stream is generated without
intervals between characters. The
data stream is synchronized by
clock signals at the receiver and
transmitter. As a result, fast
transmission speeds (above
9600 bps) are attainable
SYSGEN The software program
that allows you to configure the
operating system on HP 3000
Series 900 computers.
265
Glossary
system configuration The way
you tell the operating system
what peripheral I/O devices are
attached and what parameters
are required for system operation.
T
TCP See transmission control
protocol.
telenet A proprietary public data
network in the USA.
termDSM Terminal online
diagnostic support manager. A
utility that provides diagnostic
services for DTC connections by
means of a series of commands
accessible through the SYSDIAG
utility. TermDSM is used only
when DTCs are managed by a
host system.
terminal name Character string
of up to 16 characters specified in
the OpenView DTC Manager
configuration (for networks using
OpenView Network
Management) to define a
terminal by name. May be shared
by several terminals (pool port).
terminal profile A set of
configuration characteristics that
can be associated with one or
more terminals through the
NMMGR configuration. Terminal
profile specifications include the
terminal type, line speed, device
class assignment, and other
values relevant to terminals
connected through a DTC.
266
terminal type A collection of
characteristics that cause a
terminal connected to an MPE
system to act and react in a
specified manner. You may
configure a terminal to use one of
the system-supplied terminal
types, or you may create custom
terminal types using the
workstation configurator.
ThinLAN LAN media that
conforms to the IEEE 802.3 Type
10 BASE 2 standard LAN.
ThinLAN 3000/iX Link
Hardware and software necessary
to create a broadcast network,
which uses the IEEE 802.3 LAN
cable to transmit messages to all
the nodes on the network. The
messages are then accepted only
by the node or nodes to which
they are addressed. Also includes
the ThickLAN and StarLAN 10
options.
throughput class A value
assigned to a given virtual circuit
that defines how many network
resources should be assigned to a
given call. It is determined by the
access line speed, packet and
window sizes, and the local
network’s internal mechanisms.
throughput class negotiation
One of the network subscribed
facilities defined at subscription
time. This allows the user to
negotiate the throughput class at
call set-up time.
Glossary
Glossary
timer (T3) Length of time that a
link can remain in an idle state.
After the expiration of the timer,
the link is considered to be in a
non-active, non-operational state
and is automatically reset. The
value should be chosen carefully.
In particular, it must be
sufficiently greater than the
retransmission timer (T1) so that
no doubt exists about the link’s
state.
token ring collection of data
communication systems sharing a
common cable and
communicating by means of the
IEEE 802.5 protocol. In a token
ring network, access is controlled
by the passing of a token from
node to node. Outgoing messages
are attached to the token and
passed with the token until they
arrive at the node to which they
are addressed.
Token Ring 3000/iX Network
Link Hardware and software
required to connect a HP 3000
Series 900 system to a token ring
network.
topology The physical
arrangement of nodes in a
network. Some common
topologies are bus, star, and ring.
detects errors, and retransmits
messages if errors have been
detected.
Transpac The national public
PSN of France.
transparent mode Data
transfer scheme in which only a
limited number of special
characters retain their meaning
and are acted on by the system.
All other characters are
considered to be data and are
passed through with no control
actions being taken.
transport, network Software
that corresponds to layers 4 and 3
of the OSI network architecture
model. The function of this
software is to send data out over
the appropriate communications
link, to receive incoming data,
and to route incoming or outgoing
data to the appropriate
destination node.
Tymnet A proprietary public
data network in the USA.
typeahead A facility that allows
terminal users to enter data
before a read is actually posted to
the terminal.
U
transmission control protocol
TCP. A network protocol that
establishes and maintains
connections between nodes. TCP
regulates the flow of data, breaks
messages into smaller fragments
if necessary (and reassembles the
fragments at the destination),
Glossary
unacknowledged frame
number (K) The number of
frames that can be transmitted
without receiving an
acknowledgment from the
267
Glossary
destination address. When this
number (K) frame is reached, the
same K frames are retransmitted.
V-Series (V.##) CCITT A set of
CCITT recommendations related
to data communication over a
voice-grade telephone network.
unedited mode See
transparent mode.
VT See virtual terminal.
V
W
V.24 The CCITT recommendation
that defines the function of the
interchange circuits between a
DTE and a DCE.
workstation configurator A
utility (TTUTIL) that allows
users to create customized
terminal and printer types by
entering data through a series of
VPLUS screens.
validation The process of
ascertaining whether the network
transport configuration file has
been correctly configured. In
guided NMMGR, you do this by
pressing the Validate Netxport
key.
VAN Value-added network. A
data communication network that
uses and pays for facilities
belonging to another carrier. The
value-added package is then sold
to a user.
VC See virtual circuit.
virtual circuit A logical
association between two
physically separate DTEs.
virtual terminal A network
service that allows a user to
establish interactive sessions on a
node.
VPLUS Software used to
generate screens such as those
displayed by NMMGR.
X
X.3 Defines the user facilities
that should be internationally
available from the packet
assembler/disassembler (PAD)
facility when this is offered by a
public data network.
X.21 Defines the physical
interface between a DTE and a
DCE of a public data network
where the access to the network
is made over synchronous digital
lines.
X.25 Defines the interface
between a DTE and a DCE for
packet mode operation on a public
data network (PDN).
X.25 address The X.25 address
provided by the network
administration if you are
connected to a public data
network (PDN).
X.25 address key An X.25
address key is a label that maps a
node’s IP address to its X.25
268
Glossary
Glossary
address and its associated X.25
parameters. You have a combined
maximum of 1024 X.25 address
keys in the SVC and PVC path
tables.
to the sender if it is unable to
continue to receive data. The
sender suspends transmission
until it receives an XON
character (ASCII DC1).
X.25 LUG address X.25 address
of a node belonging to a local user
group (LUG).
X.Series (X.##) CCITT
recommendations A set of
recommendations for data
communication networks
governing their services,
facilities, and the operation of
terminal equipment and
interfaces.
X.25 iX System Access The
software that works in
conjunction with the DTC/X.25
Network Access software to
provide access to X.25. The
software resides on an HP 3000
host and is configured through
use of NMMGR. To configure
access to an X.25 network, you
must configure two software
components: the X.25 iX System
Access (residing on the HP 3000
host), and the DTC/X.25 Network
Access. DTC/X.25 Network Access
is configured through use of the
OpenView DTC Manager
software for systems using
PC-based network management
or through NMMGR for systems
using host-based network
management.
X.29 Defines the interface for
data exchange between a
packet-mode DTE and a remote
packet assembly/disassembly
(PAD) facility over a packet
switching network.
XON/XOFF protocol Flow
control used by MPE/iX systems
to protect against data overruns.
XON/XOFF protocol is controlled
by the data recipient who sends
an XOFF character (ASCII DC3)
Glossary
269
Glossary
270
Glossary
Index
A
activating logging, 193
activating NS, 195
add
directory entry, 166
add nodes to the network
directory, 166
adding a node to the directory,
166
additional address field, 172
additional domain name
configuration files, 178
address key, 62, 143, 145
address resolution, 35
domain name services, 35
network directory, 35
address resolution protocol, 38
administrative node, 37
ARP, 38
assigning node name, 86
assigning subnet masks, 27
B
backup configuration file, 84, 163
backup configuration file name,
84
C
card number, 62, 142
central administrative node, 37
centralized network directory, 36
checksum for TCP, 170
classes of logging events, 180
command
DSLINE, 199
DTCCNTRL, 196
MAKESTREAM, 37
MERGEDIR, 37, 167
NETCONTROL START, 193,
196
NETCONTROL STATUS, 198
NETCONTROL STOP, 199
NSCONTROL START, 197
NSCONTROL STATUS, 198
NSCONTROL STOP, 199
RESTORE, 37
STORE, 37
SWITCHNMLOG UPDATE,
193
communication between
networks, 45
completing the internetwork
table, 47
configuration
administrative node, 37
domain name files, 173
Index
logging, 179
configuration file, 82
configuration file name, 83, 163
configuration process, 20
configure direct connect/dial node
mapping, 134
configure domain name resolver,
174
configure mapping
direct connect/dial, 134
configure network directory, 164
configure node mapping, 131
configure path report data, 169
configure shared dial node
mapping, 132
configured gateways, 77
configured reachable networks,
117, 118, 129, 130, 149, 150
configuring a gateway half, 151
configuring a gateway half pair,
33
configuring an X.25 node, 137
configuring domain name files,
173
configuring logging, 179
configuring the network directory,
161
console logging field, 182, 184,
185, 187, 188, 189
copying a network directory, 37
create network directory, 37
cross-validating in SYSGEN, 159
cross-validation, 20, 159
D
decentralized network directory,
37
default gateway, 33, 117, 118,
127, 129, 130
default gateways, 115, 147
define
directory entry, 166
design considerations, 22
destination IP address
direct dial links, 135
non-dialed links, 135
shared dial links, 132, 133
dial link, 23, 26
direct connect, 153
direct dial, 153
disable route
direct dial links, 136
non-dialed links, 136
shared dial links, 132, 134
disk logging field, 183, 184, 188,
190
domain keyword, 174
domain name configuration
additional files, 178
overview, 173
domain name file configuration
guidelines, 173
domain name resolver
to configure, 174, 176
domain name services, 35
drawing a network map, 48
drawing an internetwork map, 44
DSLINE command, 199
DTC node name, 62, 139, 142
DTCCNTRL command, 196
E
enable Ethernet, 62, 96, 109, 113
enable IEEE 802.3, 62
entering maintenance mode, 165
Ethernet, 96, 109, 113
event logging, 180
exit maintenance mode, 165
F
facility set, 62, 144
facility sets
defined, 145
FDDI Configuration screen, 102
FDDI configuration worksheet,
70, 71, 72, 73
FDDI Link name, 64
field
console logging, 182, 184, 185,
187, 188, 189
disk logging, 183, 184, 188, 190
fields
NETXPORT Log Configuration
screens, 182, 184, 185, 187,
189
NETXPORT Log configuration
screens, 188
Full Duplex Mode, 66, 67
full gateway
definition of, 31
full gateways versus gateway
halves, 31
G
Gatehalf Configuration screen,
153
gateway configuration, 32
gateway half
definition of, 31
gateway half map, 57
gateway half network interface
table, 58
gateway half pair worksheet, 57
271
Index
gateway name, 77, 116, 117, 128,
129, 148
gateway-half configuration, 33
gateways, 31
geographical location, 22
global field, 167
global network directory entries,
167
global/local flag, 167
Global?, 167
H
home NI name, 154
hops, 79, 117, 129, 149, 150
host name data base file, 176
HOSTS.NET.SYS, 176
I
identifying neighbor gateways, 32
interface types, 25
internetwork, 31
internetwork map, 44
internetwork table, 47
internetwork worksheets, 44
IP Address
network directory, 171
IP address, 63
definition of, 94, 99, 103, 107,
111, 124, 140
entering the gateway-half ’s
partner’s, 153
how to obtain, 95, 100, 104,
108, 112, 125, 141
LAN, 94, 99, 103, 107, 111, 124
X.25, 140
IP address field, 93, 98, 99, 102,
103, 106, 110, 123, 139
IP internet address, 79
IP mask, 79
neighbor gateway, 118, 130, 150
IP network address, 46, 117, 129,
149
neighbor gateway, 118, 130, 150
IP subnet mask, 63, 98, 102, 116,
117, 128, 129, 131, 149
100Base-T, 113
100VG-AnyLAN, 109
LAN, 96, 104, 126, 142
token ring, 100
IP subnets, 27
K
keyword
domain, 174
nameserver, 175
search, 175
keywords
resolver file, 174
L
LAN Configuration screen, 123
LAN configuration worksheet, 69
LAN internet routing table, 51
LAN Link name, 64
LAN network map, 49
LAN network worksheet, 49
LAN network worksheets, 49
leased line, 26
leaving maintenance mode, 165
line speed, 22
link manager logging, 193
link name, 64, 98, 102, 123, 139,
142
gateway half, 155
LAN, 96, 105, 109, 113, 126
token ring, 100
Link Speed, 66, 67
link type
gateway half, 155
link types, 25
Local domain name, 65
local entries
uses of, 167
local network directory entries,
167
Local node name, 64
local node name, 85
logging classes, 180
logging configuration
guidelines, 179
overview, 179
M
Main screen, 85
maint mode, 165
maintenance mode, 165
MAKESTREAM command, 37
map
internetwork, 44
point-to-point network, 52
MERGEDIR command, 37, 167
merging network directory files,
37
modify logging configuration, 182
modify network directory, 37
modify the domain name resolver,
174
multicast request, 38
multiple network interfaces, 26
N
nameserver keyword, 175
272
neighbor gateway configuration
worksheet, 78
neighbor gateway IP Internet
Address
X.25, 150
neighbor gateway IP internet
address, 79, 117, 118, 129,
130
neighbor gateway reachable
networks configuration
worksheet, 79, 80
Neighbor Gateway Reachable
Networks screen, 117, 129,
148
neighbor gateway worksheet
information, 77
neighbor gateways, 32
defined, 115, 127, 147
Neighbor Gateways screen, 115,
127, 147
NETCONTROL START
command, 193, 196
NETCONTROL STATUS
command, 198
NETCONTROL STOP command,
199
NetIPC logging, 193
netowrk interface type priority,
26
NETSAMP.NET.SYS, 178
network and internetwork design
considerations, 22
network boundaries, 46
network boundary, 31, 46
network directory, 35, 161
centralized, 36
configure, 164
configuring from NMMGR, 36
copying, 37
data screen, 169
decentralized, 37
file structure, 37
for X.25 networks, 36
global entries, 167
local entries, 167
planning, 36
Select Node Name screen, 166
Network Directory Data screen,
169
network directory entry, 161
network directory file name, 163
Network Directory Main screen,
164
Network directory name, 65
network directory name
X.25, 144
Index
Index
Network directory Select Node
Name screen, 166
network directory worksheet, 59
network interface
LAN, 89
Network Interface (NI) name, 65
network interface (NI) name
X.25, 145
network interface name, 89
guidelines for using, 89
network interfaces, 25
network map, 48
network name, 89
LAN, 89
network name database, 178
network planning, 21
Network Services, 197
starting, 197
testing, 198
Network Transport Configuration
screen, 88
network transport logging, 193
network type, 89
network worksheets, 49
NETWORKS.NET.SYS, 178
NETXPORT Log Configuration,
182
NETXPORT Log Configuration
screens, 182
new global field, 168
new name, 77, 168
for directory node entry, 168
NI name, 89
LAN, 89
NI type, 89
NI type priority, 26
NMCBACK.group.account, 84,
163
NMCONFIG.PUB.SYS, 83, 163
NMMGR, 19, 20, 82
node name, 167
network directory, 167
node worksheet information, 62
nodes having multiple links, 131
nodes having single links, 131
non-HP 3000 nodes, 23
NS Configuration screen, 87
NS validation test, 198
NSCONTROL START command,
197
NSCONTROL STATUS
command, 198
NSCONTROL STOP command,
199
NSDIR.NET.SYS, 84, 163
number of LAN links, 25
number of network interfaces, 25
Index
number of point-to-point links, 26
number of token ring links, 25
number of X.25 links, 26
O
offline configuration file, 83, 163
Open Configuration/Directory file
screen, 162
open network directory file, 37
operating the network, 195
overview of configuration, 20
P
partner’s IP address, 153, 154
partner’s IP subnet mask, 154
PASSWORD command, 84
path report data, 169
PDN, 144
Permanent VC number, 65
permanent VC number, 144, 146
permanent virtual circuit, 143,
144, 146
phone number
direct dial links, 135
gateway half, 155
shared dial links, 132, 133, 136
Physical path, 65
physical path
gateway half, 155
point-to-point, 126
Physical path of device adapter,
66
physical path of FDDI device
adapter, 105
Physical path of LANIC, 66
Physical path of Token Ring
device adapter, 66
physical path of token ring device
adapter, 101
physicall path of LANIC, 96, 109,
113
planning the network directory,
36
point-to-point configuration
worksheet, 74
point-to-point internet routing
table, 53
Point-to-Point Link name, 64
point-to-point network map, 52
point-to-point network table, 53
point-to-point network
worksheet, 52
print dir, 165
print network directory, 165
priority
direct dial links, 135, 136
non-dialed links, 135, 136
shared dial, 132, 133
priority of network interfaces, 26
probe, 38
probe protocol, 38
probe request, 38
programmable serial interface,
126
protocol name database, 178
PROTOCOL.NET.SYS, 178
PROTSAM.NET.SYS, 178
proxy
probe, 38
Proxy node, 67
proxy node, 96, 109, 113
proxy server, 38
PSI, 126
public data network, 144
PVC, 143, 146
PVC number, 144
PVC parameters, 145
PXP field
network directory, 170
Q
QVALNS.NET.SYS, 198
R
redirect output, 165
Remote IP address, 67
remote IP address, 143, 144
Remote node name, 67
remote node name, 143, 144
Remote X.25 address, 67
remote X.25 address, 144, 145
RESLVCNF.NET.SYS, 174
resolver file, 174
resolver file keywords, 174
RESTORE command, 37
route name
defined, 133
direct dial links, 135
non-dialed links, 135
shared dial links, 133
routename
shared dial links, 132
S
search keyword, 175
Security class, 68
security string
direct dial links, 135, 136
gateway half, 155
shared dial links, 132, 134
service name database, 178
SERVICES.NET.SYS, 178
SERVSAM.NET.SYS, 178
273
Index
shared dial link, 23
limitations, 23
shut down Network Services, 199
shutting down NS, 199
Speed, 68
speed
line, 22
point-to-point, 126
starting a host-based X.25 link,
196
starting a link, 196
starting links and services, 196
starting network services, 197
starting NS, 197
starting software loopback, 196
stop Network Services, 199
STORE command, 37
subnet masks
assigning, 27
determining, 28
subnetworks, 27
SVC, 143
SVC parameters, 145
switched virtual circuit, 143
SWITCHNMLOG UPDATE
command, 193
SYSGEN facility
use for cross-validation, 159
T
TCP checksum, 170
TCP field
network directory, 170
testing Network Services, 198
to access the logging configuration
screens, 181
to activate logging, 193
to add nodes to the network
directory, 166
to configure a 100VG-AnyLAN
network interface, 106
to configure a gatehalf network
interface, 153
to configure a LAN network
interface, 93, 110
to configure a point-to-point
network interface, 123
to configure a token ring network,
98
to configure an FDDI network,
102
to configure an X.25 network
interface, 139
to configure direct connect/dial
node mapping, 134
to configure neighbor gateways,
115, 127, 147
274
to configure path report data for a
node, 169
to configure shared dial node
mapping, 132
to configure the domain name
resolver, 174
to configure the hosts file, 176
to configure X.25 virtual circuits,
142
to draw a network map, 48
to enable users for individual
logging classes, 191
to enter maintenance mode, 165
to exit maintenance mode, 165
to identify neighbor gateway
reachable networks, 117, 148
to identify neighbor gateways,
115, 127, 147
to modify the domain name
resolver, 174
to modify the hosts file, 176
to modify the logging
configuration, 182
to open the configuration file, 82
to perform guided network
transport configuration
LAN, 88
to select guided configuration, 87
to select NS configuration, 85
to select the update directory
function, 164
to shut down Network Services,
199
to start a host-based X.25 link,
196
to start a link, 196
to start links and services, 196
to start network services, 197
to start NMMGR, 82
to start software loopback, 196
to test Network Services, 198
Token Ring Configuration screen,
98
token ring configuration
worksheet, 70
Token Ring Link name, 64
transmission speed
gateway half, 155
transport services, 170
Type, 68
type
network directory data, 171
users enabled for logging, 192
uses of local entries, 167
V
validate network transport, 20,
158
Virtual Circuit Configuration
screen, 142
W
worksheet
gateway half pair, 57
worksheets
internetwork, 44
LAN network, 49
write access password, 84, 163
X
X.25 Configuration screen, 139
X.25 configuration worksheet, 75
X.25 internet routing table, 56
X.25 Link name, 64
X.25 network
network directory, 36
X.25 network map, 55
X.25 network table, 56
X.25 network worksheet, 55
X.25 virtual circuit configuration
worksheet, 76
U
update dir, 164
update network directory, 164
Use Auto-Negotiation, 67
Index
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement