HP E3000-IX, E3000 MPE-IX User Manual

Download

HP e3000/iX Network Planning and

Conﬁguration Guide

HP e3000 MPE/iX Computer Systems

Edition 6

Manufacturing Part Number: 36922-90043

E0801

U.S.A. August 2001

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 ﬁtness 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 DFARS252.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.

Contents

1. Network Conﬁguration Overview

Pre-Conﬁguration Hardware Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Pre-Conﬁguration Software Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Conﬁguration Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2. Networking Concepts

Network Environment Design Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Line Speed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Geographical Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Special Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Shared Dial Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Non-HP e3000 Nodes (Including PCs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Applicable SYSGEN Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Dynamic Ldevs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Network Interface and Link Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Number of Network Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Priority of Network Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Subnetworks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Why Use Subnets?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

How Subnetting Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Assigning Subnet Masks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Internetworks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Full Gateways versus Gateway Halves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Gateway Conﬁguration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Identifying Neighbor Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Neighbor Gateway Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Conﬁguring a Gateway Half Pair. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Address Resolution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Domain Name Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Network Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

When a Network Directory is Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Planning the Network Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Copying and Merging Network Directory Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Probe and Probe Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Address Resolution Protocol (ARP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Enabling Probe and ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Network Design Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Software Conﬁguration Maximums . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3. Planning Your Network

Drawing an Internetwork Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Contents

Communication Between Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Network Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

IP Network Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Completing the Internetwork Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Drawing a Network Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Network Worksheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

LAN Network Worksheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

LAN Network Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

LAN Network Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

LAN Internet Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Token Ring Network Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

FDDI Network Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

100VG-AnyLAN Network Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

100Base-T Network Worksheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Point-to-Point Network Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Point-to-Point Network Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Point-to-Point Network Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

Point-to-Point Internet Routing Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

X.25 Network Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

X.25 Network Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

X.25 Network Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

X.25 Internet Routing Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

Gateway Half Pair Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Gateway Half Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Gateway Half Network Interface Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

Network Directory Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

4. Planning for Node Conﬁguration

Node Worksheet Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

LAN Conﬁguration Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Token Ring Conﬁguration Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

FDDI Conﬁguration Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

100VG-AnyLAN Conﬁguration Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

100Base-T Conﬁguration Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

Point-to-Point Conﬁguration Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

X.25 Conﬁguration Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

X.25 Virtual Circuit Conﬁguration Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Neighbor Gateway Worksheet Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

Neighbor Gateway Conﬁguration Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Neighbor Gateway Reachable Networks Worksheet Information . . . . . . . . . . . . . . . . . . . . . .77

Neighbor Gateway Reachable Networks Conﬁguration Worksheet . . . . . . . . . . . . . . . . . . .78

Contents

5. Introductory Screens

Begin Conﬁguration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Start NMMGR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Open Conﬁguration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Select NS Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Select Guided Conﬁguration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Guided/Unguided Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Perform Guided Network Transport Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

6. Conﬁguring a LAN Node

Conﬁgure a LAN Network Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Conﬁgure a Token Ring Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Conﬁgure an FDDI Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Conﬁgure Neighbor Gateways. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Identify Neighbor Gateways (If Any Are Present) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Identify Neighbor Gateway Reachable Networks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

7. Conﬁguring a Point-to-Point Node

Conﬁgure a Point-to-Point Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Conﬁgure Neighbor Gateways. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Specify Neighbor Gateways (If Any Are Present) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Specify Neighbor Gateway Reachable Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Conﬁgure Node Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Select a Node Mapping Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Conﬁgure Shared Dial Node Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Conﬁgure Direct Connect/Dial Node Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

8. Conﬁguring a X.25 Node

Conﬁgure an X.25 Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Conﬁgure X.25 Virtual Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Conﬁgure Neighbor Gateways. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Identify Neighbor Gateways (If Any Are Present) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Identify Neighbor Gateway Reachable Networks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

9. Conﬁguring a Gateway Half

Conﬁgure a Gatehalf Network Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

10. Validating and Cross-Validating with SYSGEN

Validate the Network Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Cross-Validate in SYSGEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Contents

11. Conﬁguring the Network Directory

Open Network Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153

Select Update Directory Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155

Add Nodes to Network Directory File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157

Conﬁgure Path Report Data for a Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160

12. Conﬁguring Domain Name Files

Create or Modify the Resolver File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166

Create or Modify the Hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168

Additional Domain Name Conﬁguration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170

Network Name Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170

Protocol Name Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170

Service Name Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170

13. Conﬁguring Logging

Access Logging Conﬁguration Screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173

Modify the Logging Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174

Enable Users for Individual Logging Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184

Activate Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186

14. Operating the Network

Start Links and Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188

Start Software Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188

Start a Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188

Start a Host-Based X.25 Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188

Start Network Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189

Test Network Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190

Shut Down Network Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191

A. MPE/V to MPE/iX Migration

Differences Between NS 3000/V and NS 3000/iX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194

Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194

Conﬁguration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194

Applications Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195

Obtaining Status Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195

Migration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196

Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196

File Migration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196

Additional Migration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196

File Conversion Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

When to Convert Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

Converting Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

Contents

Updating From a Previous MPE/iX Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Reconﬁguration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

B. NS X.25 Migration: NS 3000/V to NS 3000/iX

Differences Between NS 3000/V and NS 3000/iX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Unsupported Network Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Conﬁguration of Terminals and Printers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Conﬁguration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Network Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Obtaining Device Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Differences in X.25 Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

1980 Versus 1984 CCITT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

General Level 3 Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Level 3 Access with NetIPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Facilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Pad Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Converting NS 3000/V Conﬁguration Files to NS 3000/iX . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Deleting Secondary NIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Saving NS 3000/V X.25 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Copying NS 3000/V Conﬁguration Files to NS 3000/iX System . . . . . . . . . . . . . . . . . . . . . . 209

Using NMMGRVER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Updating X.25 XL System Access Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Saving X.25 XL System Access Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Adding Other Link Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Verifying DTS Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Conﬁguring the DTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

C. NS X.25 Migration: NS 3000/V PAD Access to NS 3000/iX

PAD Support: NS 3000/V and NS 3000/iX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Migrating from NS 3000/V PAD Access to NS 3000/iX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Using Host-Based Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Using PC-Based Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Saving NS 3000/V PAD Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

PAD Access Migration Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Non-Nailed Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Nailed Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Conﬁguration of Nailed Versus Non-Nailed Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Saving DTS Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Conﬁguring the DTC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Contents

D. PCI 10/100Base-TX/3000 Quick Installation

Notes on Manual Speed and Duplex Mode Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . .222

Notes on Autonegotiation and Autosensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223

Quick Troubleshooting Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225

Figures

Figure 2-1. Class C Address with Subnet Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Figure 2-2. Class C Address with Subnet Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Figure 2-3. Gateway Conﬁguration 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Figure 4-1. LAN Conﬁguration Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Figure 4-2. Token Ring Conﬁguration Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Figure 4-3. FDDI Conﬁguration Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Figure 4-4. 100VG-AnyLAN Conﬁguration Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Figure 4-5. 100Base-T Conﬁguration Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Figure 4-6. Point-to-Point Conﬁguration Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Figure 4-7. X.25 Conﬁguration Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Figure 4-8. X.25 Virtual Circuit Conﬁguration Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . 74

Figure 4-9. Neighbor Gateway Conﬁguration Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . 76

Figure 4-10. Reachable Network Conﬁguration Worksheet . . . . . . . . . . . . . . . . . . . . . . . . 78

Figure 5-1. NMMGR Screen Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Figure 5-2. Open Conﬁguration/Directory File Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Figure 5-3. Main Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Figure 5-4. NS Conﬁguration Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Figure 5-5. Network Transport Conﬁguration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Figure 6-1. Conﬁguring Screen Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Figure 6-2. LAN Conﬁguration Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Figure 6-3. Token Ring Conﬁguration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Figure 6-4. FDDI Conﬁguration Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Figure 6-5. Neighbor Gateways Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Figure 6-6. Neighbor Gateway Reachable Networks Screen . . . . . . . . . . . . . . . . . . . . . . 105

Figure 7-1. Point-to-Point Link Conﬁguration Screen Flow . . . . . . . . . . . . . . . . . . . . . . . 107

Figure 7-2. Point-to-Point Link Conﬁguration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Figure 7-3. Neighbor Gateway Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Figure 7-4. Neighbor Gateway Reachable Networks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Figure 7-5. Shared Dial Node Mapping Conﬁguration Screen. . . . . . . . . . . . . . . . . . . . . 119

Figure 7-6. Direct Connect/Dial Node Mapping Conﬁguration Screen . . . . . . . . . . . . . . 122

Figure 7-7. Using an @ for Mapping Non-Adjacent Nodes . . . . . . . . . . . . . . . . . . . . . . . . 123

Figure 8-1. X.25 Link Screen Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Figure 8-2. NS Conﬁguration Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Figure 8-3. X.25 Virtual Circuit Conﬁguration Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Figures

Figure 8-4. Neighbor Gateways Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Figure 8-5. Neighbor Gateway Reachable Networks Screen. . . . . . . . . . . . . . . . . . . . . . .137

Figure 9-1. Gateway Half Link Screen Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140

Figure 9-2. Gatehalf Conﬁguration Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142

Figure 11-1. Network Directory Conﬁguration Screen Flow. . . . . . . . . . . . . . . . . . . . . . .151

Figure 11-2. Open Conﬁguration/Directory File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Figure 11-3. Network Directory Main. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155

Figure 11-4. Network Directory Select Node Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157

Figure 11-5. Network Directory Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160

Figure 12-1. Sample Resolver Conﬁguration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167

Figure 12-2. Sample Hosts Conﬁguration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169

Figure 13-1. Logging Conﬁguration Screen Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Figure 13-2. Netxport Log Conﬁguration (1) Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Figure 13-3. Netxport Log Conﬁguration (2) Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Figure 13-4. Netxport Log Conﬁguration (3) Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Figure 13-5. Netxport Log Conﬁguration (4) Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Figure 13-6. Netxport Log Conﬁguration (5) Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Figure 13-7. Netxport Log Conﬁguration (6) Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Figure 13-8. Netxport Log Conﬁguration (7) Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Figure 13-9. Logging Conﬁguration: Class Data Screen . . . . . . . . . . . . . . . . . . . . . . . . . .184

Tables

Table 2-1. Valid Addresses of Example Subnetwork. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Table 2-2. Conﬁguration 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Table 3-8. Gateway Half Network Interface Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Table 3-9. Network Directory Information Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Table 4-1. Conﬁguration Worksheet Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Table 11-1. Path Type Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Table 13-1. Subsystem Activation/Deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Table B-1. Supported Facilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Tables

Preface

This manual documents functionality for the MPE/iX releases, for HP e3000 systems. It describes the concepts and terminology needed to design an NS 3000/iX network and to plan the conﬁguration process for that network. It also provides step-by-step instructions to assist you in conﬁguring the network links for HP e3000 systems.

Audience This manual is intended for network managers and planners who are

responsible for setting up and conﬁguring a communications network. To make the best use of this guide, you should be familiar with basic

MPE commands as well as with the NS 3000/iX product. You should also be familiar with NMMGR, the tool used to conﬁgure

network connections. If not, refer to Using the Node Management Services (NMS) Utilities for information.

Special Note MPE/iX, Multiprogramming Executive with Integrated POSIX, is the

latest in a series of forward-compatible operating systems for the HP e3000 line of computers.

In HP documentation and in talking with HP e3000 users, you will encounter references to MPE XL, the direct predecessor of MPE/iX. MPE/iX is a superset of MPE XL. All programs written for MPE XL will run without change under MPE/iX. You can continue to use MPE XL system documentation, although it may not refer to features added to the operating system to support POSIX (for example, hierarchical directories).

Finally, you may encounter references to MPE V,which is the operating system for HP e3000s, not based on the PA_RISC architecture. MPE V software can be run on the PA_RISC HP e3000s in what is known as compatibility mode.

Organization This manual is divided into the following chapters and appendixes:

Chapter 1 , “Network Conﬁguration Overview,” provides information you should know before you begin conﬁguration.

Chapter 2 , “Networking Concepts,” describes networking concepts and provides information you need to know to plan your conﬁguration.

Chapter 3 , “Planning Your Network,” will help you draw your network map and ﬁll out network worksheets as you plan your network, internetwork, gateway, and network directory conﬁguration.

Chapter 4 , “Planning for Node Conﬁguration,” describes how to ﬁll out node worksheets before you start conﬁguring network links for each node. It includes a table listing the parameters that you will need to enter during NMMGR guided conﬁguration.

Chapter 5 , “Introductory Screens,” provides step-by-step instructions for conﬁguring NMMGR introductory screens.

Chapter 6 , “Conﬁguring a LAN Node,” provides step-by-step instructions for conﬁguring IEEE802.3/Ethernet LAN, token ring, and Fiber Distributed Data Interface (FDDI) links.

Chapter 7 , “Conﬁguring a Point-to-Point Node,” provides step-by-step instructions for conﬁguring Point-to-Point (router) links.

Chapter 8 , “Conﬁguring a X.25 Node,” provides step-by-step instructions for conﬁguring X.25 links.

Chapter 9 , “Conﬁguring a Gateway Half,” provides step-by-step instructions for conﬁguring the interface between two gateway halves.

Chapter 10 , “Validating and Cross-Validating with SYSGEN,”provides step-by-step instructions for validating the network transport and cross-validating with SYSGEN.

Chapter 11 , “Conﬁguring the Network Directory,”provides step-by-step instructions for conﬁguring a network directory.

Chapter 12 , “Conﬁguring Domain Name Files,” provides instructions for conﬁguring the domain name resolver.

Chapter 13 , “Conﬁguring Logging,” provides step-by-step instructions for conﬁguring logging.

Chapter 14 , “Operating the Network,” shows you how to bring up and shut down NS 3000 links and services.

Appendix A , “MPE/V to MPE/iX Migration,” provides general MPE/V to MPE/iX migration information.

Appendix B , “NS X.25 Migration: NS 3000/V to NS 3000/iX,” provides X.25-speciﬁc information on migration 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. Appendix C does not apply if an MPE V-based node s being used as an X.25 server for NS 3000/XL-based machines.

Appendix C , “NS X.25 Migration: NS 3000/V PAD Access to NS 3000/iX,” tells how to migrate NS 3000/V versions of PAD access to NS 3000/iX release 2.0 or later.

Glossary, contains terms applicable to the network conﬁguration process.

Related HP Publications

The following manuals are referenced in this manual or may be of use to you as you plan and conﬁgure your network.

Networking • Using the Node Management Services (NMS) Utilities

• Conﬁguring and Managing Host-Based X.25 Links

• Managing Host-Based X.25 Links Quick Reference Guide

• NS 3000/iX NMMGR Screens Reference Manual

• NS 3000/iX Operations and Maintenance Reference Manual

• NS 3000/iX Error Messages Reference Manual

• NetIPC 3000/XL Programmer’s Reference Manual

• Berkeley Sockets/iX Reference Manual

• Using NS 3000/iX Network Services

Datacommunications and Terminal Subsystem

General Information

Hardware Installation Guides

Conﬁguring Systems for Terminals, Printers, and Other Serial Devices and Troubleshooting Terminal, Printer, and Serial Device Connections

Using the OpenView DTC Manager

System Startup, Conﬁguration, and Shutdown Reference Manual MPE/iX Commands Reference Manual

• PCI 100Base-T Network Adapter Installation and Service Guide

• HP-PB 100Base-T Network Adapter Installation and Service Guide

• 8-Port Serial PCI ACC Multiplexer Installation and User’s Guide

• HP-PB 100VG-AnyLAN Network Adapter Installation and Service

Guide

• HP-IB FDDI Adapter Installation Guide

1 Network Conﬁguration

Overview

This manual provides step-by-step instructions you can use to conﬁgure an HP e3000 node for network communications. You can use the information to conﬁgure an IEEE 802.3/Ethernet, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T, Point-to-Point (router), or X.25 node.

Before you begin conﬁguration, you must ensure your network is physically set up and ready for network conﬁguration.

This chapter provides information you should know before you begin conﬁguration. It tells you what preparations you must make and what items you will be conﬁguring.

This chapter contains the following conﬁguration information:

• Pre-conﬁguration hardware check.

• Pre-conﬁguration software check.

• Conﬁguration process overview.

Network Conﬁguration Overview

Pre-Conﬁguration Hardware Check

Before beginning the actual conﬁguration process, check that the hardware components required for NS 3000/iX have been installed and veriﬁed according to the procedures in the hardware installation manuals listed in the preface to this guide.

18 Chapter1

Network Conﬁguration Overview

Pre-Conﬁguration Software Check

Once you have veriﬁed 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 conﬁgured. If DTS has not been conﬁgured, refer to

Conﬁguring Systems for Terminals, Printers, and Other Serial Devices and conﬁgure 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 ﬁrst have to run a conversion program. The conversion program, called NMMGRVER (NMMGRVER.PUB.SYS), ensures that conﬁguration ﬁles created with an earlier version of NMMGR are converted to the latest format.

Chapter 1 19

Network Conﬁguration Overview

Conﬁguration Process Overview

The instructions in this guide explain how to conﬁgure each node on your network by using a “guided” branch of Hewlett-Packard’sNMMGR conﬁguration 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 Conﬁguration,” to record all the items NMMGR requires. (See Chapter 2 , “Networking Concepts,” for information on networking concepts.)

2. Conﬁgure the transport and link by using NMMGR to modify the NMCONFIG.PUB.SYS ﬁle. The instructions for this step are contained in this manual.

3. If the node being conﬁgured 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 ﬁle. See Chapter 11 , “Conﬁguring the Network Directory,” for information on conﬁguring the network directory, or if using DNS for nodename resolution.

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 and Cross-Validating with SYSGEN.”

5. Cross-validate NMCONFIG.PUB.SYS with the system conﬁguration ﬁles within SYSGEN. Cross-validation ensures that there are no conﬂicts in the use of node names, device classes, and physical paths. Even if validation and cross-validation were already done after conﬁguring DTS, you still have to validate and cross-validate again after you conﬁgure the network transport and link. Instructions for cross-validating are located in Chapter 10 , “Validating 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 NS services conﬁguration and conﬁrm network connectivity by running the QVALNS program. See Chapter 14 , “Operating the Network,” for information on running QVALNS.

20 Chapter1

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 conﬁguration 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 directory — Probe and probe proxy — Address Resolution Protocol (ARP)

Networking Concepts

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 trafﬁc between nodes, communications trafﬁc 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 speciﬁc links. They will also affect how you design your network layout. You may want to create subnetworks within your network by conﬁguring 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 inﬂuence 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 TokenRing 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.

Another option for nodes located in the same geographic location is to use hardwired (direct-connect) Point-to-Point links. You might wish to

22 Chapter2

Networking Concepts

Network Environment Design Considerations

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. Bridges, hubs and routers are commonly implemented to extend LANs.

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 e3000s 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 e3000 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, cannot dial out on SMUX, shared dial links cannot be used as gateway halves.

Non-HP e3000 Nodes (Including PCs)

LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T, and X.25 networks can access non-HP e3000 nodes. Point-to-Point networks must be composed of only HP e3000s.

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 conﬁgurable 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 conﬁgured 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 conﬁgured 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 Chapter2

Networking Concepts

Network Interface and Link Types

The network interface (NI), the software that provides an interface between a node and a network, speciﬁes the type and maximum number of links that can be conﬁgured for a node. Because a node’s network interface determines what links can be conﬁgured for the node, links are said to be conﬁgured underneath network interfaces.

There are nine types of network interfaces (in addition to loopback):

• LAN for IEEE 802.3 and Ethernet networks, 100VG-AnyLAN networks, and 100Base-T networks.

• Token Ring for IEEE 802.5 networks.

• FDDI for ﬁber 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 48 network interfaces (NI) conﬁgured. One of these network interfaces must be loopback. For each network interface, the maximum number of links you can conﬁgure and the kinds of links possible are determined by the network interface type, as follows:

• A LAN network interface can have only one link conﬁgured 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, 100BT allows a maximum distance of 100m between 2 nodes.

• A Token Ring interface can have only one link conﬁgured 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 conﬁgured 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 conﬁgured 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 conﬁgured, depending on the number of conﬁgured 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 conﬁgured 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 conﬁgured on a node, the network portions of the IP addresses conﬁgured for the interfaces should differ to correspond to the multiple networks to which the node belongs.

Refer to “Software Conﬁguration Maximums” at the end of this chapter for information on conﬁguration 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 ﬁnds ﬁrst.

26 Chapter2

Networking Concepts

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 speciﬁc 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 trafﬁc 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 conﬁgured.

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 ﬁrst must determine which bits of the node address will be used to contain your subnet numbers.

The bits that you designate for subnet identiﬁers compose the subnet mask. The subnet mask is conﬁgured 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.

Todetermine the subnet mask, you ﬁrst 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 ﬁve bits for the node numbers as shown in Figure 2-1.

Figure 2-1 Class C Address with Subnet Number

The 30 nodes per subnet will require at least ﬁve bits of the node portion of the IP address (30 <32, and 32=2

, therefore you need 5 bits). This leaves three bits remaining in the node portion of the IP address for use as the subnet identiﬁer. 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 (2

–2=6) when three bits are

used for the subnet identiﬁer.

Example 2 An IP address on a class B network with an 8-bit subnet mask

separates as shown in Figure 2-2.

28 Chapter2

Figure 2-2 Class C Address with Subnet Number

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 identiﬁer. 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 signiﬁcant three bits of the rightmost byte are set.

Subnet Mask

Networking Concepts

Subnetworks

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 conﬁguration. 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 ﬁve 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 ﬁfth 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 ﬁve 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

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

Decimal Value of Subnetwork

Possible Node Address on Subnetwork

Decimal Value of Rightmost Byte

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

NOTE

The subnet mask has already been deﬁned as:

255.255.255 224 1111 1111 1111 1111 1111 1111 1110 0000

Because the mask has all bits except the ﬁve rightmost bits set to 1, all bits except the ﬁve rightmost bits must match between nodes on the same subnet. Because the two example IP addresses from subnet 1 do match except for their ﬁve rightmost bits, they belong to the same subnet.

Subnet addressing can be used in internetworks (networks with gateways).

30 Chapter2

Networking Concepts

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 e3000 systems conﬁgured as gateways.

Gateways

One method of joining networks in an internetwork is by using gateways.An HP e3000 system can have up to 256 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 conﬁgured 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 conﬁgured.

A node that is a gateway half is conﬁgured 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 conﬁgured 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 Conﬁguration Overview

Gateway conﬁguration includes both identifying neighbor gateways in each node’s conﬁguration ﬁle and conﬁguring 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 conﬁguration, you may want to modify each node’s conﬁguration ﬁle so that the node is aware of all of its neighbor gateways (gateways on the same link). You accomplish this during conﬁguration of each network interface for which you want to allow communications over the gateway. You will ﬁnd step-by-step instructions for identifying neighbor gateways in each of the link conﬁguration sections of this manual.

An alternative to identifying neighbor gateways in every node’s conﬁguration ﬁle is to conﬁgure a default gateway for the node. Instructions for doing so are included in this manual.

The next pages show several examples of gateway conﬁguration.

Neighbor Gateway Examples

When using NMMGR to conﬁgure any node, you will be entering the identities of all the neighbor gateways into the conﬁguration of the node. The following examples illustrate several gateway conﬁguration scenarios based on the network represented in Figure 2-3.

• Example 1: The node you are conﬁguring 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 conﬁgured reachable networks reachable through gateway node C.

• Example 2: The node you are conﬁguring 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 conﬁgure the NI (in this case, node C is the neighbor gateway). You will also need to conﬁgure a gateway half NI for the node, as described under “Conﬁguring a Gateway-Half Pair.”

• Example 3: The node you are conﬁguring may be a full gateway,

such as nodes B and C in Figure 2-3. Though full gatewaysare never actually identiﬁed as such in the conﬁguration process, they too, must know about the other gateways. If you were conﬁguring node C, you would identify nodes B and E and neighbor gateways.

32 Chapter2

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 trafﬁc for which the network is unable to identify a destination. You must identify the node as a default gateway in the conﬁguration ﬁle of each node that will access it as the default gateway. If you were conﬁguring node D, you would identify node C as a default gateway by entering an at sign (@) in one of the IP address ﬁelds 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.

Conﬁguring a Gateway Half Pair

If you are conﬁguring a gateway half pair, you will need to conﬁgure a gateway half NI for each half of the gateway pair. You will ﬁnd step-by-step instructions for conﬁguring a gateway half NI in this manual.

In Figure 2-3, nodes E and F form a gateway half pair. When you conﬁgure a node as a gateway half, you enter its partner’s IP address into this gateway half’s conﬁguration in the Gatehalf Conﬁguration screen. If you were to conﬁgure node E in the ﬁgure, you would enter the IP address of node F.

Figure 2-3 Gateway Conﬁguration Scenarios

Chapter 2 33

Networking Concepts

Internetworks

Gateway halves require the conﬁguration 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 speciﬁc NI type, depending on the network type) and then follow the instructions to enter conﬁguration items speciﬁc to the gateway half NI.

Worksheets that will aid you in planning for internetwork communication are located in Chapter 4 , “Planning for Node Conﬁguration.”

34 Chapter2

Networking Concepts

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 conﬁgure 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).

NOTE

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 e3000 systems as well as with non-HP e3000 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 conﬁgure this name on the NS Conﬁguration screen (see conﬁguration chapters for details).

You will also need to create a set of ASCII ﬁles on each system which contain the addressing information the system will need. Instructions for creating these ﬁles are in Chapter 12 , “Conﬁguring Domain Name Files.”

Once you have conﬁgured 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.

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 conﬁgure the network directory as well.

Chapter 2 35

Networking Concepts

Address Resolution

Network Directory

The network directory is a set of ﬁles that contain information used by the node to communicate with other nodes in the internetwork.

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 , “Conﬁguring the Network Directory,” for more information on conﬁguring 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 conﬁgured 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 conﬁguring 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 conﬁgure a network directory for nodes using X.25.

Planning the Network Directory

There are two theories about how network directories should be planned and conﬁgured on a network, as follows:

• Centralized network directories.

• Decentralized network directories.

36 Chapter2

Networking Concepts

Address Resolution

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 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 conﬁgure 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 conﬁgured 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.

NOTE

Copying and Merging Network Directory Files

The ﬁrst time you conﬁgure the network directory, an entry for all remote IP addresses must be added manually using the NMMGR screens. After the ﬁrst network directory is conﬁgured, 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.)

The network directory uses a KSAM ﬁle pair.Therefore, when copying a directory, be sure to copy both the data ﬁle and the key ﬁle. The system names the key ﬁle automatically using the ﬁrst six letters of the network directory ﬁle name appended with a K. For example,

NSDIRK.NET.SYS is the name of the key ﬁle associated with the data ﬁle 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 sufﬁcient 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 e3000 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 conﬁguration 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 Chapter2

Networking Concepts

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 200 meters of each other?

If so, consider connecting them with 100Base-T links, or ThinLAN links with Ethertwist. For entry-level servers,choose ThinLAN since that adapter will ofﬂoad part of the CPU load.

2. 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.

3. 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.

4. 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.

5. 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-Pointnetwork 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.

Routers, switches, bridges and hubs are used to set up networks.

• Routers are used to route packets between networks and subnets

based on the packets destination address.

• Bridges are used to connect two LAN networks that are far apart.

• Hubs are multiport repeaters, used to build or extend a LAN

network. New nodes can be added to the LAN without disrupting the existing network.

Chapter 2 39

Networking Concepts

Network Design Questions

• To connect two networks that run on different protocol stacks, a gateway is needed. A gateway does conversion between the two protocols at every layer until the application layer.

6. 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.

7. 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.

8. Do you need access to nodes on public or private X.25 networks? If so, consider using DTC/X.25 iX Network Links.

9. Is a subset of nodes either geographically or organizationally distanced from another subset of nodes?

If so, you may wish to establish a network boundary between them in order to make them two separate networks joined by a full gateway or router. Alternatively, you may want to use subnets to divide one network into two or more physically distinct subnetworks.

10.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 Chapter2

Software Conﬁguration Maximums

The software maximums as shown in Table 2-2, must be adhered to when conﬁguring 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 Conﬁguration Maximums

Networking Concepts

Software Conﬁguration Maximums

NMMGR Screen Number/Description

#9 Network Directory Select Node Name

#44 Point-to-Point Link Conﬁguration

#45 Direct Connect/Dial Node Mapping Conﬁguration

#46 Shared Dial Node Mapping Conﬁguration

#48 X.25 Conﬁguration None 11 Links/X.25 NI #112 Network Interface

Conﬁguration #117 Gateway Half NI

Links #158 Neighbor Gateway

Reachable Networks #85 Link Selection LINK 256 Links/System

Path Maximum Limit

None File Size Limit

None 40 links/Router NI

(8 per screen)

None 1024 Mappings/Router

NETXPORT.NI 48 NI/system

NETXPORT.NI.

NETXPORT.NI. gatewayn

NIname

.LINK 1 link/Gateway Half NI

.INTERNET.

2550 networks/NI

Chapter 2 41

Networking Concepts

Software Conﬁguration Maximums

42 Chapter2

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 conﬁguration. You will need to consider a number of items as you plan your conﬁguration. 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 conﬁguring.

• Complete the network directory worksheet if a network directory is required.

• Update Domain name ﬁles if using DNS for node name resolution. Refer to Chapter 12 , “Conﬁguring Domain Name Files.”

Planning Your Network

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 ﬁlling 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 conﬁguration worksheets.

NOTE

Before you can draw your internetwork map, you must know how many networks your internetwork will contain, and you must know each network type (ThinLAN, 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, NET1 is 100Base-T LAN and NET5 is a ThinLAN, 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.

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 conﬁgured for X.25 links.

44 Chapter3

Figure 3-1 Internetwork Map

Planning Your Network

Drawing an Internetwork Map

NET4

C 192.004.002 XXX

TOKEN RING

DTC

C 192.001.001 XXX

Router

DTC

X.25 PSN

C 192.003.251 XXX

NET3

X.25

NET1

LAN

N2 N3

Router

NET2

C 192.002.250 XXX

POINT-TO-POINT

NET6

C 192.006.003 XXX

FDDI

DTC

C 192.005.252 XXX

NET5

LAN

NOTE

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.

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.

Network Boundaries

Once you have drawn your gateway nodes and 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.

Chapter 3 45

Planning Your Network

Drawing an Internetwork Map

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 speciﬁc IP node addresses do not need to be shown until completion of speciﬁc parts of the network worksheets, so node portions of IP addresses will be represented with XXX in some maps and tables.

46 Chapter3

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 ﬁrst 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 ﬁnished the internetwork worksheets.

Table 3-1 Internetwork Table

Planning Your Network

Completing the Internetwork Table

NETWORK NETWORK TYPE

(LAN, PT–PT, X.25, TOKEN RING)

NET1 LAN C 192.001.001 XXX 1 NET2 NS POINT-TO-POINT C 192.002.250 XXX 2 NET3 X.25 C 192.003.001 XXX 3 NET4 TOKEN RING C 192.004.001 XXX 4 NET5 LAN C 192.005.001 XXX 5 NET6 FDDI C 192.006.001 XXX 6

IP NETWORK ADDRESS

IMPLEMENTATION PRIORITY

Chapter 3 47

Planning Your Network

Drawing a Network Map

A network map provides information about the conﬁguration 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 conﬁguration and later as a record of your conﬁguration for both you and your HP support staff.

48 Chapter3

Planning Your Network

Network Worksheets

Foreach network in your internetwork, you are asked to draw a map of the network and to complete two tables. One table lists node-speciﬁc 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 ﬁlling 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.

2. Complete the two tables: for each network, for a gateway-half pair, include the link name.

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-speciﬁc 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 ﬁlling 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

GATEWAY NODE

TO NET4:

NET4

C 192.004.002.XXX

TOKEN RING

ROUTER

DTC

NET1

C 192.001.001.XXX

LAN

GATEWAY NODE

TO NET2:

NET2

C 192.002.250.XXX

POINT-TO-POINT

GATEWAY HALF

NET3

C 192.003.251.XXX

X.25

LAN Network Table

Refer to the LAN network map to ﬁll in the LAN network table (Table 3-2). The ﬁrst 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 conﬁguration.

Table 3-2 LAN Network Table

NETWORK NAME: NET1

IP NETWORK ADDRESS C 192.001.001 XXX

DTC

NET5

C 192.005.252.XXX

LAN

NODE NAME IP NODE

ADDRESS

PROXY SERVER (Y/N)

GATEWAY NODE (Y/N)

A 001 2 L1 002 3 L2 003 4 L3 004 5 B 005 YES YES 1

50 Chapter3

IMPLEMENTATION PRIORITY

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 neighbor gateway 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.001.001 XXX

Planning Your Network

Network Worksheets

GATEWAY IP NODE

ADDRESS

B 005 NET2

DESTINATION HOPS TO

C 192.002.250 XXX NET5

C 192.005.252 XXX NET3

C 192.003.251 XXX

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

DEFAULT

DESTINATION

1 YES

GATEWAY (Y/N)

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-speciﬁc 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

NET2

C 192.002.250 XXX

POINT-TO-POINT

GATEWAY NODE TO NET1

NET1

B P2

LINK1

LINK2

NET5

LINK5

LINK3

LINK4

GATEWAY NODE TO NET5;

Central Admin.

52 Chapter3

Point-to-Point Network Table

Refer to the Point-to-Point network map to ﬁll in the Point-to-Point network table (Table3-4). Wehave completed the ﬁrst 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 conﬁguration.

Table 3-4 Point-to-Point Network Table

NETWORK NAME: NET2

IP NETWORK ADDRESS C 192.002.250 XXX

Planning Your Network

Network Worksheets

NODE NAME IP NODE

ADDRESS

B 001 YES 2 P1 002 3 P2 003 4 P3 004 5 G 005 YES YES 1

PROXY SERVER (Y/N)

GATEWAY NODE (Y/N)

Point-to-Point Internet Routing Table

The purpose of the Point-to-Point internet routing table (Table3-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.

IMPLEMENTATION PRIORITY

Chapter 3 53

Planning Your Network

Network Worksheets

For Node G, the same type of information is listed.

Table 3-5 Point-to-Point Internet Routing Table

NETWORK NAME: NET2

IP NETWORK ADDRESS C 192.002.250 XXX

GATEWAY IP NODE

ADDRESS

B 001 NET1 C 192.001.001 XXX 1

G 005 NET5 C 192.005.252 XXX 1

DESTINATION HOPS TO

NET4 C 192.004.002 XXX 2 NET3 C 192.003.251 XXX 2 NET5 C 192.005.252 XXX 3 NET6 C 192.006.003 XXX 2

NET3 C 192.003.251 XXX 2 NET1 C 192.001.001 XXX 3 NET4 C 192.004.002 XXX 4 NET3 C 192.003.003 XXX 4

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-speciﬁc internet routing information.

DESTINATION

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.

54 Chapter3

Figure 3-4 X.25 Network Map

NET1

Planning Your Network

Network Worksheets

DTC

X.25 PSN

DTC

NET3

C 192.003.251 XXX

X.25

DTC

Central Admin

Node

NET5

X.25 Network Table

Refer to the X.25 network map to ﬁll in the X.25 network table as shown in Table 3-6. We complete the ﬁrst 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 ﬁfth 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.

Chapter 3 55

Planning Your Network

Network Worksheets

Table 3-6 X.25 Network Table

NETWORK NAME: NET3

IP NETWORK ADDRESS C 192.003.251 XXX

NODE NAME IP NODE ADDRESS CENTRAL ADMIN NODE

(Y/N)

H 001 Y 1234 I 002 5678 J 003 6879 B 004 9876

X.25 ADDRESS

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.

Table 3-7 X.25 Internet Routing Table

NETWORK NAME: NET3

IP NETWORK ADDRESS C 192.003.251 XXX

GATEWAY IP NODE ADDRESS DESTINATION HOPS TO

DESTINATION

B 004 NET1 C 192.001.001 XXX 1

NET4 C 192.004.002 XXX 2 NET2 C 192.002.250 XXX 2 NET5 C 192.005.252 XXX 3

H 001 NET5 C 192.005.252 XXX 1

NET2 C 192.002.250 XXX 2 NET1 C 192.001.001 XXX 3 NET4 C 192.004.002 XXX 4

56 Chapter3

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 ﬁlling 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.

Figure 3-5 Gateway-Half Map

Planning Your Network

Network Worksheets

NET2

C 192.002.250 XXX

POINT-TO-POINT

LINKRL1

C 192.005.252 XXX

NET5

LAN

Chapter 3 57

Planning Your Network

Network Worksheets

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 conﬁguration of a gateway half network interface.

Table 3-8 Gateway Half Network Interface Table

NETWORK NAMES: NET2, NET3

GATEWAY HALF NODE

G/NET2 C 192.005.250 005 NET5 LINKRL1 H/NET5 C 192.002.252 001 NET2 LINKRL1

FULL IP ADDRESS OF PARTNER

CONNECTED NETWORK

LINK NAME

58 Chapter3

Network Directory Worksheet

You can complete the network directory information table shown below for each network directory you are conﬁguring. 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 , “Conﬁguring the Network Directory,” for more information on NI types and additional addresses. Table 3-9 shows some of the network directory entries you might conﬁgure for node B of the internetwork shown in Figure 3-1.

Table 3-9 Network Directory Information Table

Planning Your Network

Network Directory Worksheet

NODE NAME

H GLOBAL C 192.005.252 001 1 I LOCAL C 192.005.252 002 1 J GLOBAL C 192.005.251 003 3 6879 A GLOBAL C 192.001.001 001 5 08-00-09-11-22-11 K GLOBAL C 192.004.002 001 1

GLOBAL OR LOCAL

IP ADDRESS TYPE ADDITIONAL

ADDRESS

Chapter 3 59

Planning Your Network

Network Directory Worksheet

60 Chapter3

4 Planning for Node Conﬁguration

This chapter describes how to complete node worksheets before you start conﬁguration. 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 conﬁgure for each node during NMMGR’s guided conﬁguration. This information depends on the type of network you have. For a description of the ﬁelds in these worksheets, see Chapter 6 , “Conﬁguring a LAN Node,” for information on LAN, Token Ring, and FDDI, and Chapter 7 , “Conﬁguring a Point-to-Point Node,” for information on Point-to-Point and Chapter 8 , “Conﬁguring a X.25 Node,” for information on X.25.

It is recommended that you make copies of these worksheets and ﬁll in the parameter information, then use these worksheets to guide you through conﬁguration in NMMGR.

Node worksheets list only the ﬁelds you can conﬁgure during guided conﬁguration, which allows you to conﬁgure your nodes as quickly as possible. For information on conﬁguration parameters that are available through non-guided conﬁguration, see the NS 3000/iX NMMGR Screens Reference Manual.

This chapter includes:

• Node worksheet information. — Node worksheet information.

— Token Ring conﬁguration worksheet — FDDI conﬁguration worksheet. — 100VG-AnyLAN conﬁguration worksheet. — 100Base-T conﬁguration worksheet. — Point-to-Point conﬁguration worksheet. — X.25 conﬁguration worksheet. — X.25 virtual circuit conﬁguration worksheet.

• Neighbor gateway worksheet information. — Neighbor gateway conﬁguration worksheet.

• Neighbor gateway reachable networks worksheet Information. — Neighbor gateway reachable networks conﬁguration worksheet.

Planning for Node Conﬁguration

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 conﬁguration chapters of this manual.

Table 4-1 Conﬁguration Worksheet Information

Field Screen Description

Address key X.25 Virtual Circuit

Conﬁguration

Card number X.25 Conﬁguration Slotnumber of the DTC/X.25 Network

DTC node name X.25 Conﬁguration Node name of the DTC in the form

Enable ethernet/ Enable IEEE 802.3

LAN Conﬁguration Both ethernet and IEEE 802.3 are

In the network directory, the name of each node listed in the remote node name ﬁeld. HP recommends that you use the node portion of the remote node’s node name as the address key.

Access card.

node.domain.organization. Must agree with node name conﬁgured through during conﬁguration 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.

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 ﬁeld next to the enable question.

Facility set X.25 Virtual Circuit

Conﬁguration

62 Chapter4

ForSVCs 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 Facilitysets to deﬁne parameters. It must match the parameters speciﬁed by your network subscription.

Table 4-1 Conﬁguration Worksheet Information

Field Screen Description

Planning for Node Conﬁguration

Node Worksheet Information

IP address LAN Conﬁguration;

Token Ring Conﬁguration; FDDI Conﬁguration; Point-to-Point Conﬁguration; X.25 Conﬁguration

There are two methods of entering an internet protocol (IP) address within NMMGR:

1. Enter the fully qualiﬁed IP address (for example, Class C, C 192.191.191 009).

2. Enter only the network ( 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 ﬁll 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.

nnn

) and

IP subnet mask LAN Conﬁguration;

Token Ring Conﬁguration; FDDI Conﬁguration; Point-to-Point Conﬁguration; X.25 Conﬁguration

Link name The link name represents a hardware

(LAN Link name) LAN Conﬁguration This represents the LAN card for

(Token Ring Link name)

Token Ring conﬁguration This represents the Token Ring card

Chapter 4 63

The IP subnet mask is optional. An IP subnet mask is speciﬁed in the same format as an IP address. The mask identiﬁes which bits of an IP address will be used to deﬁne a subnetwork. For more information refer, to the conﬁguration chapter for the type of link you are conﬁguring.

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 ﬁrst character must be alphabetic.

which you are conﬁguring a link.

for which you are conﬁguring a link.

Planning for Node Conﬁguration

Node Worksheet Information

Table 4-1 Conﬁguration Worksheet Information

Field Screen Description

(FDDI Link name) FDDI Conﬁguration This represents the FDDI card for

which you are conﬁguring a link.

(100VG-AnyLAN Link name)

(100Base-T Link name)

(X.25 Link name) X.25 Conﬁguration The name of the link used by X.25 iX

(Point-to-Point Link name)

Local node name Main The node name is the name by which

LAN Conﬁguration This represents the 100VG-AnyLAN

card for which you are conﬁguring a link.

LAN Conﬁguration This represents the 100Base-T card

for which you are conﬁguring a link.

System Access. It must match the link name conﬁgured during conﬁguration of the datacommunications and terminal subsystem (DTS).

Point-to-Point Conﬁguration This represents the PSI card for

which you are conﬁguring a link.

the HP e3000 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 ﬁeld contains 16 or fewer characters (alphanumeric, underscore, or hyphens). The ﬁrst character of each ﬁeld must be alphabetic.

Local domain name NS Conﬁguration 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 ﬁeld.)

64 Chapter4

Table 4-1 Conﬁguration Worksheet Information

Field Screen Description

Planning for Node Conﬁguration

Node Worksheet Information

Network directory name

Network Interface (NI) name

Permanent VC number

X.25 Virtual Circuit Conﬁguration

LAN Conﬁguration; Token Ring Conﬁguration; FDDI Conﬁguration; Point-to-Point Conﬁguration; X.25 Conﬁguration

X.25 Virtual circuit Conﬁguration

The network directory name must be conﬁgured 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.

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 conﬁgured on a node is 48. If a node interfaces to more than one network, give each NI on that node a unique name. Youwill use the NI name with the NETCONTROL command to start the transport and network link.

For PVCs only. In the network directory, the number of the permanent virtual circuit on the remote node.

Physical path Point-to-Point Conﬁguration This is the location of the

programmable serial interface. Refer to Chapter 7 , “Conﬁguring a Point-to-Point Node,” for further details regarding physical path.

Physical path of LANIC

Physical path of device adapter

Physical path of Token Ring device adapter

LAN Conﬁguration This is the location of the LANIC

device adapter card. Refer to the LAN section of Chapter 6 , “Conﬁguring a LAN Node,” for further details regarding physical path.

FDDI Conﬁguration This is the location of the FDDI device

adapter card. Refer to the FDDI section of Chapter 6 , “Conﬁguring a LAN Node,” for further details regarding the physical path.

Token Ring Conﬁguration This is the location of the Token Ring

device adapter card. Refer to the Token Ring section of Chapter 6 , “Conﬁguring a LAN Node,”for further details regarding physical path.

Chapter 4 65

Planning for Node Conﬁguration

Node Worksheet Information

Table 4-1 Conﬁguration Worksheet Information

Field Screen Description

Proxy node LAN Conﬁguration The proxy ﬁeld 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 conﬁguration chapter for LAN link.

Remote IP address X.25 Virtual Circuit

Conﬁguration

Remote node name X.25 Virtual Circuit

Conﬁguration

Remote X.25 address X.25 Virtual Circuit

Conﬁguration

Security class X.25 Virtual Circuit

Conﬁguration

Speed Point-to-Point Conﬁguration The line transmission speed is given

Type Point-to-Point Conﬁguration Enter DD (direct dial) if you always

In the network directory, the IP address of each node listed in the remote node name ﬁeld.

In the network directory, the name of each remote X.25 node on the network

For SVCs only. In the network directory, the X.25 address of the remote host for X.25 public data networks or private networks.

For SVCs only. In the network directory,the security to be applied for connection establishment with the remote node.

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.

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 reconﬁguring. 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.

66 Chapter4

LAN Conﬁguration Worksheet

Fill out the following worksheet (Figure 4-1) for each LAN link you are conﬁguring.

Figure 4-1 LAN Conﬁguration Worksheet

LAN Conﬁguration Worksheet

Node Name ___________________________________________________

Network Interface (NI) name ____________________________________

IP address ____________________________________________

IP subnet mask__________________________________ (optional)

Proxy name____________________ (Y/N)

Planning for Node Conﬁguration

Node Worksheet Information

Node Name ___________________________________________________

Link type ___________________________ (BT100, VG100LAN, LAN)

Physical path of LANIC ______________________________

Enable Ethernet _____________________________________ (Y/N)

Enable IEEE 802.3 __________________________________ (Y/N)

Chapter 4 67

Planning for Node Conﬁguration

Node Worksheet Information

Token Ring Conﬁguration Worksheet

Fill out the following worksheet (Figure 4-2) for each Token Ring link you are conﬁguring.

Figure 4-2 Token Ring Conﬁguration Worksheet

68 Chapter4

FDDI Conﬁguration Worksheet

Fill out the following worksheet (Figure 4-3) for each FDDI link you are conﬁguring.

Figure 4-3 FDDI Conﬁguration Worksheet

Planning for Node Conﬁguration

Node Worksheet Information

Chapter 4 69

Planning for Node Conﬁguration

Node Worksheet Information

100VG-AnyLAN Conﬁguration Worksheet

Fill out the following worksheet (Figure 4-4) for each 100VG-AnyLAN link you are conﬁguring.

Figure 4-4 100VG-AnyLAN Conﬁguration Worksheet

70 Chapter4

100Base-T Conﬁguration Worksheet

Fill out the following worksheet (Figure 4-5) for each 100Base-T link you are conﬁguring.

Figure 4-5 100Base-T Conﬁguration Worksheet

Planning for Node Conﬁguration

Node Worksheet Information

Chapter 4 71

Planning for Node Conﬁguration

Node Worksheet Information

Point-to-Point Conﬁguration Worksheet

Fill out the following worksheet (Figure 4-6) for each Point-to-Pointlink you are conﬁguring.

Figure 4-6 Point-to-Point Conﬁguration Worksheet

Point-to-Point Conﬁguration Worksheet

Node Name ___________________________________________________ (Specify local system)

Network Interface (NI) name _______________________________________

IP address ___________________________________IP subnet mask ____________ (optional)

Link name Link type Physical Path Speed Type

(LAPBMUX or LAPB)

72 Chapter4

X.25 Conﬁguration Worksheet

Fill out the following worksheet (Figure 4-7) for each X.25 link you are conﬁguring.

Figure 4-7 X.25 Conﬁguration Worksheet

Planning for Node Conﬁguration

Node Worksheet Information

Chapter 4 73

Planning for Node Conﬁguration

Node Worksheet Information

X.25 Virtual Circuit Conﬁguration Worksheet

Fill out the following worksheet (Figure 4-8) for each X.25 Virtual Circuit you are conﬁguring.

Figure 4-8 X.25 Virtual Circuit Conﬁguration Worksheet

74 Chapter4

Planning for Node Conﬁguration

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 conﬁguring nodes.

Gateway name

Enter the name of a gateway that is on the same network as the node that you are conﬁguring. (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 ﬁrst character must be alphabetic

New name

Configured Gateways

This is a list of gateways that are conﬁgured. Gateway names are automatically entered in these ﬁelds when they are entered above.

Chapter 4 75

Planning for Node Conﬁguration

Neighbor Gateway Worksheet Information

Neighbor Gateway Conﬁguration Worksheet

Fill out the following worksheet (Figure 4-9) for each neighbor gateway you are conﬁguring.

Figure 4-9 Neighbor Gateway Conﬁguration Worksheet

76 Chapter4

Planning for Node Conﬁguration

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 conﬁguring nodes.

Neighbor Gateway IP Internet Address

This is the IP address of the gateway speciﬁed on the Neighbor Gateways screen. The IP address is in the same format as the LAN Conﬁguration screen. An example of an address is: C 192.007.007 001

IP network address

The IP addresses of all the remote networks that can be reached through the gateway whose IP address is conﬁgured in the previous ﬁeld. If the gateway node is to serve as a default gateway, enter an at sign (@) in one of these ﬁelds.

IP mask

Hops

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.

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 77

Planning for Node Conﬁguration

Neighbor Gateway Reachable Networks Worksheet Information

Neighbor Gateway Reachable Networks Conﬁguration Worksheet

Fill out the following worksheet (Figure 4-10) for each neighbor gateway reachable network you are conﬁguring.

Figure 4-10 Reachable Network Conﬁguration Worksheet

78 Chapter4

5 Introductory Screens

The introductory screens are the ﬁrst few screens that are displayed when you conﬁgure a node using NMMGR.

Figure 5-1 shows the screen ﬂow of the introductory screens.

[FUNCTION] denotes the function key used at a screen to invoke the next

screen on the screen ﬂow. This chapter describes the introductory screens relevant to conﬁguring NS unguided networks.

Figure 5-1 NMMGR Screen Flow

Open Conﬁg/

Directory File Screen

[OPEN CONFIG]

Main Screen

[NS]

If you have not created the conﬁg ﬁle, then press the OPEN CONFIG key a second

time

DTS OSI IBM Utility

[GUIDED]

Network

Transport Conﬁg

[CONFIG NETWORK]

LAN Token Ring FDDI Point-to-Point X.25 Gateway Half

[MODIFY LOGGING]

NS Conﬁg

[UNGUIDED]

Unguided

Conﬁg*

[LIST NETWORK]

*For information speciﬁc to the unguided conﬁguration screens, refer to the

NS 3000/iX NMMGR Screens Reference Manual

Introductory Screens

Begin Conﬁguration Process

The procedures that follow describe how to modify the NMMGR conﬁguration ﬁle for the introductory screens.

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 (:).

NOTE

2. Press

You can modify the link conﬁgurations 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)

[RETURN].

80 Chapter5

Open Conﬁguration File

The Open Conﬁguration/Directory File screen (#1) in Figure 5-2 is the ﬁrst screen displayed when you run NMMGR.

Figure 5-2 Open Conﬁguration/Directory File Screen

Introductory Screens

Begin Conﬁguration Process

Follow the steps listed here to enter data for this screen. Refer to “Fields” subsection for detailed information about each ﬁeld on the screen.

Step 1. Verifythat the correct conﬁguration ﬁle name, backup conﬁguration ﬁle

name, and network directory ﬁle name are in the appropriate ﬁelds.

Step 2. If you have assigned a write access password, enter it in this ﬁeld. If

you are not using the password feature, leave this ﬁeld blank.

Step 3. Press the

[Open Conﬁg] key. If you are creating the conﬁguration ﬁle for

the ﬁrst time, NMMGR will ask you to verify creation. Press the

[Open Conﬁg] key again to continue.

Fields configuration file name

The only conﬁguration ﬁle name the system recognizes for use by the network subsystem is NMCONFIG.PUB.SYS. You can, however, create or modify a conﬁguration ﬁle using a different name and save it as an ofﬂine conﬁguration ﬁle. You can use ofﬂine conﬁguration ﬁles as a means of creating and storing conﬁgurations that you want to use in the future or that you are preparing for use on a different system.

Chapter 5 81

Introductory Screens

Begin Conﬁguration Process

When you are ready to use an ofﬂine conﬁguration ﬁle, rename it as NMCONFIG.PUB.SYS and reboot the

system. (Keep in mind that any ﬁle you use as a conﬁguration ﬁle must be successfully validated before you try to use it.)

Backup configurationfile name

A backup ﬁle name must be speciﬁed whenever a conﬁguration ﬁle is opened or created. The default backup conﬁguration ﬁle name is NMCBACK.group.account. The backup ﬁle will be automatically updated with the contents of the conﬁguration ﬁle each time the conﬁguration ﬁle is successfully validated.

Network directory file name

A network directory must be conﬁgured 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 ﬁle name supported by HP is NSDIR.NET.SYS. This ﬁle is part of a KSAM pair. A key ﬁle is created at the same time as this data ﬁle.The key ﬁle will automatically be named using the ﬁrst six letters of the network directory ﬁle name, appended with the character K. For example, NSDIRK.NET.SYS is the name of the key ﬁle associated with the data ﬁle NSDIR.NET.SYS. If the name of the data ﬁle is less than six letters long, then the entire ﬁle 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 ﬁeld to update the conﬁguration ﬁle or the directory ﬁle.It is still possible to open an existing ﬁle without using an assigned password, but the ﬁle will be in read only mode and NMMGR will not accept changes.

If a password has not been assigned, you should ignore the password ﬁeld.

If you want to assign a password for the system you are conﬁguring, see Using the Node Management Services (NMS) Utilities.

82 Chapter5

Select NS Conﬁguration

To Select NS Conﬁguration. The Main screen (#2) in Figure 5-3 is displayed after you create or open a conﬁguration ﬁle by pressing the

[Open Conﬁg] key from the Open Conﬁguration Directory File screen

(#1) in Figure 5-2.

Figure 5-3 Main Screen

Introductory Screens

Begin Conﬁguration Process

Step 1. Ensure that the information in the ﬁelds 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 Conﬁguring Systems for

Terminals, Printers, and Other Serial Devices for information about

conﬁguring the information on this screen.)

Step 2. When you are satisﬁed with the information as conﬁgured, press the

[NS] key to select the NS conﬁguration branch.

Chapter 5 83

Introductory Screens

Begin Conﬁguration Process

Fields Local node name

The local node name is the name by which the HP e3000 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 ﬁeld contains 16 or fewer characters (alphanumeric, underscore, or hyphens). The ﬁrst character of each ﬁeld 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 ﬁeld is the same because the nodes belong to the same network. The organization ﬁeld 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 conﬁgure 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 conﬁgured DTS.

Do you have X.25 system- to-system or PAD connections?

If you answer yes to this question, NMMGR assumes you are conﬁguring X.25 connections and takes you to the set of screens required to conﬁgure DTC X.25 Network Access Cards when you conﬁgure DTS. If you answer no, NMMGR assumes you have no need to conﬁgure X.25 connections and takes you to a different set of DTS screens. You should already have answered this question when you conﬁgured DTS.

84 Chapter5

Select Guided Conﬁguration

The NS Conﬁguration screen (#166) in Figure 5-4 is displayed if you press the

Figure 5-4 NS Conﬁguration Screen

[NS] key at the Main screen (#2) in Figure 5-3.

Introductory Screens

Begin Conﬁguration Process

Step 1. If you are using domain names for network access, replace the node

name in the ﬁeld 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 Conﬁg] key to proceed with guided conﬁguration of

LAN.

Chapter 5 85

Introductory Screens

Begin Conﬁguration Process

Guided/Unguided Conﬁguration

Hewlett-Packard recommends that you press the [Guided Conﬁg] key to select the guided conﬁguration branch whenever you need to initially conﬁgure a network interface. Guided conﬁguration supplies many default values for your conﬁguration and requires that you visit a minimal number of screens. This manual provides information on every screen available to you through unguided NS conﬁguration.

The

[Unguided Conﬁg] key is used to modify conﬁguration values that

are not available in the guided screens. To use the unguided conﬁguration screens, refer to the NS 3000/iX NMMGR Screens Reference Manual.

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 ﬁeld.

86 Chapter5

Perform Guided Network Transport Conﬁguration

The Network Transport Conﬁguration screen (#42) in Figure 5-5 is displayed if you press the screen (#166) in Figure 5-4.

Figure 5-5 Network Transport Conﬁguration Screen

[Guided Conﬁg] key at the NS Conﬁguration

Introductory Screens

Begin Conﬁguration 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

[Conﬁg Network] key. (There may be a short pause before the

next screen appears.)

Step 4. Proceed to the chapter of the network interface selected above for

screen information. Refer to Chapter 6 , “Conﬁguring a LAN 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.

Chapter 5 87

Introductory Screens

Begin Conﬁguration Process

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, 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 conﬁgured on a node is 48. One of the 48

allowable NIs is reserved for loopback. (Loopback is conﬁgured 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 conﬁguring. You must enter a network type if you are conﬁguring a new network interface. Refer to the following for what number to enter:

• Enter 1 for a LAN NI (100Base-T, ThinLAN or 100VG-AnyLAN)

• Enter 2 for a Point-to-Point (router) NI

• Enter 3 for an X.25 NI

• Enter 5 for a Gateway Half NI

• Enter 6 for a Token Ring NI

• Enter 7 for an FDDI NI

88 Chapter5

6 Conﬁguring a LAN Node

This chapter provides step-by-step instructions for conﬁguring 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 conﬁguration capabilities of NMMGR.

Figure 6-1 shows the screen ﬂow for conﬁguring LAN, Token Ring, FDDI, 100VG-AnyLAN, and 100Base-T screens. Screens unique to the conﬁguration of LAN, Token Ring, FDDI, 100VG-AnyLAN and 100Base-T are indicated by bold boxed screens. function key used at a screen to invoke the next screen on the screen ﬂow.

Figure 6-1 Conﬁguring Screen Flow

Open Conﬁg/

Directory File Screen

[OPEN CONFIG]

[FUNCTION] denotes the

[VALIDATE NETXPORT]

Main Screen

[NS]

NS Conﬁg

[GUIDED]

Network Transport

Conﬁg

[CONFIG NETWORK]

(Network Interface)

Link Selection

Conﬁg

[NEIGHBOR GATEWAY]

Neighbor Gateways

Link Selection

If you have not created the conﬁg ﬁle, then press the OPEN CONFIG key a second time.

Enter Network Interface: LAN, Token Ring or FDDI

Validate Link,

Cross-validate

with SYSGEN

[ADD or MODIFY]

Neighbor Gateway

Reachable Networks

Conﬁguring a LAN Node

Before using NMMGR to conﬁgure a link, you should complete the worksheets provided. See Chapter 4 , “Planning for Node Conﬁguration,” for more information on planning your conﬁguration and ﬁlling out the conﬁguration worksheets.

This chapter includes step-by-step instructions to help you perform the following tasks:

• Begin the conﬁguration process.

• Conﬁgure a LAN, Token Ring, FDDI, 100VG-AnyLAN,or 100Base-T network interface.

Once the above tasks are completed, refer to Chapter 10 , “Validating and Cross-Validating with SYSGEN,” for step-by-step instructions to help you perform the following validation tasks:

• Validate the network transport conﬁguration.

• Cross-validate in SYSGEN.

90 Chapter6

Conﬁgure a LAN Network Interface

The LAN Conﬁguration screen (#41) in Figure 6-2 is displayed when you press the Conﬁguration screen (#42) with an NI type of 1 (LAN). Refer to Chapter 5 , “Introductory Screens,” for information on the Network Transport Conﬁguration screen.

Figure 6-2 LAN Conﬁguration Screen

[Conﬁg Network] key at the Network Transport

Conﬁguring a LAN Node

Conﬁgure a LAN Network Interface

Step 1. In the IP address ﬁeld, enter the internet protocol (IP) address for the

node being conﬁgured. 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 ﬁeld 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 ﬁeld. Enter a link name to represent the LAN

card for which you are conﬁguring a link. This name must be unique to the node.

Step 5. Move to the Link type ﬁeld. Enter BT100 for a 100Base-T link, LAN

for a ThinLAN link, or VG100 LAN for a 100VG-AnyLAN link.

Chapter 6 91

Conﬁguring a LAN Node

Conﬁgure a LAN Network Interface

Step 6. Tab down to the ﬁeld called Physical path of LANIC. Enter the

physical path number corresponding to the SPU slot number where the LAN interface controller card is located.

Step 7. Tab down to the ﬁeld called Enable Ethernet (Y/N). By default,

ethernet is enabled. Change the ﬁeld to N if you do not want ethernet and the ARP protocol enabled.

Step 8. Tab down to ﬁeld called Enable IEEE 802.3 (Y/N). By default,

IEEE 802.3 is enabled. Change the ﬁeld to N if you do not want IEEE 802.3 and the Probe protocol enabled.

Step 9. Press the

[Save Data] key to save the LAN link conﬁguration. If you

need to identify neighbor gateways, press the and proceed to the section in this chapter called “To Identify Neighbor Gateways.” Otherwise, proceed to Chapter 10 , “Validating and Cross-Validating with SYSGEN,” and press the

Optional Keys

Fields Node name

Network Interface (NI) name

IP address

[Neighbor Gateways] key

[Validate Netxport] key.

Press the

[List NIs] key to list the names and types of

already conﬁgured network interfaces. Press the [Delete NI] key to remove a conﬁgured network

interface from the conﬁguration ﬁle. Press the [Read Other NI] key to call up a previously

conﬁgured Network Interface name.

Display only.

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 qualiﬁed IP address (for example, Class C, C 192.191.191 009).

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).

92 Chapter6

Conﬁguring a LAN Node

Conﬁgure a LAN Network Interface

You need not enter the following items as NMMGR will ﬁll 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.nnn.nnn 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 ﬁnd 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 ﬁnd 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.

IP subnet mask An IP subnet mask is speciﬁed 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 conﬁguring subnetworks. The mask identiﬁes which bits of an IP address will be used to deﬁne a subnetwork. To determine these bits, you ﬁrst 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.

Chapter 6 93

Conﬁguring a LAN Node

Conﬁgure a LAN 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 conﬁguring an internetwork or a network with non-HP nodes, it may be easier to update your conﬁgurations 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 conﬁgure a proxy node if you have conﬁgured domain names. See Chapter 12 , “Conﬁguring Domain Name Files,” for information on domain names.)

Link name The link name can have up to eight

alphanumeric characters and the ﬁrst character must be alphabetic.

Physical Path of LANIC The physical path number corresponds

to the slot location of a node’slocal area network interface controller (LANIC) card. Recommended slot locations and physical path calculations vary according to the type of HP e3000 system you are running.

For the various platforms, physical path syntax (examples only) look like:

Series 9x7: 48 Series 9x8: 56/44 Series 9x9: 10/4/16 Series 99x: 0/28/12 Series N4000: 1/10/0/0 Series A500: 0/2/0/0

If you are unsure of the slot location or of the physical path number to conﬁgure for your system, run the ofﬂine ODE MAPPER utility, see your system documentation, or consult your Hewlett-Packard service representative.

94 Chapter6

Conﬁguring a LAN Node

Conﬁgure a LAN Network Interface

Enable Ethernet? A Y in this ﬁeld 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 ﬁelds may not be set to N). Ethernet is enabled by default.

Disabling Ethernet has the effect of disabling the ARP protocol and you will need to handle both name to IP and IP to station (MAC) address resolution by other means.

Enable IEEE 802.3? A Y in this ﬁeld 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 ﬁelds 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 and you will need to handle both name to IP and IP to station (MAC) address resolution by other means.

Chapter 6 95

Conﬁguring a LAN Node

Conﬁgure a Token Ring Network Interface

The Token Ring Conﬁguration screen (#49) in Figure 6-3 is displayed when you press the Conﬁguration screen (#42) with an NI type of 6 (Token Ring). Refer to Chapter 5 , “Introductory Screens,” for information on the Network Transport Conﬁguration screen.

Figure 6-3 Token Ring Conﬁguration Screen

[Conﬁg Network] key at the Network Transport

NOTE

Step 1. In the IP address ﬁeld, enter the internet protocol (IP) address for the

node being conﬁgured. 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 ﬁeld and enter the number in the same format as an IP address.

Step 3. Move to the Link name ﬁeld. Enter a link name to represent the Token

Ring card for which you are conﬁguring a link. This name must be unique to the node.

Step 4. Tab down to the ﬁeld 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.

If the same Token Ring card is being used for both NS and SNA communications, you must use the same value for this ﬁeld as is conﬁgured for the SNA Link.

96 Chapter6

Conﬁguring a LAN Node

Conﬁgure a Token Ring Network Interface

Step 5. Press the [Save Data] key to save the Token Ring link conﬁguration. 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 and Cross-Validating with SYSGEN,” and press the

[Validate Netxport]

key. Optional Keys Press the

Fields Node name

Network Interface (NI) name

IP address

[List NIs] key to list the names and types of

already conﬁgured network interfaces. Press the [Delete NI] key to remove a conﬁgured network

interface from the conﬁguration ﬁle. Press the [Read Other NI] key to call up a previously

conﬁgured Network Interface name.

Display only.

Class A nnn xxx.xxx.xxx

B nnn.nnn xxx.xxx C nnn.nnn.nnn 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.

Chapter 6 97

Conﬁguring a LAN Node

Conﬁgure a Token Ring Network Interface

NOTE

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.

IP subnet mask

An IP subnet mask is speciﬁed 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 conﬁguring subnetworks. The mask identiﬁes which bits of the IP address comprise the network and subnetwork portion.

Link name

The link name can have up to eight alphanumeric characters and the ﬁrst 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 ﬁeld as is conﬁgured 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 e3000 system you are running.

If you are unsure of the slot location or of the physical path number to conﬁgure for your system, see your system documentation or consult your Hewlett-Packard service representative.

For the various platforms, physical path syntax (examples only) look like:

Series 9x7: 48 Series 9x8: 56/44 Series 9x9: 10/4/16 Series 99x: 0/28/12

98 Chapter6

Conﬁgure an FDDI Network Interface

The FDDI Conﬁguration screen (#201) in Figure 6-4 is displayed when you press the Conﬁguration screen (#42) with an NI type of 7 (FDDI). Refer to Chapter 5 , “Introductory Screens,” for information on the Network Transport Conﬁguration screen.

Figure 6-4 FDDI Conﬁguration Screen

[Conﬁg Network] key at the Network Transport

Conﬁguring a LAN Node

Conﬁgure an FDDI Network Interface

Step 1. In the IP address ﬁeld, enter the internet protocol (IP) address for the

node being conﬁgured. 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 ﬁeld and enter the number in the same format as an IP address.

Step 3. Move to the Link name ﬁeld. Enter a link name to represent the FDDI

card for which you are conﬁguring a link. This name must be unique to the node.

Step 4. Tab down to the ﬁeld 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.

Chapter 6 99

Conﬁguring a LAN Node

Conﬁgure an FDDI Network Interface

Step 5. Press the [Save Data] key to save the FDDI link conﬁguration. 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 and Cross-Validating with SYSGEN,” and press the

[Validate Netxport] key.

Optional Keys Press the

Fields Node name

Network Interface (NI) name

IP address

[List NIs] key to list the names

and types of already conﬁgured network interfaces.

Press the

[Delete NI] key to remove a

conﬁgured network interface from the conﬁguration ﬁle.

Press the

[Read Other NI] key to call up

a previously conﬁgured Network Interface name.

Display only.

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 qualiﬁed IP address (for example, Class C, C 192.191.191 009).

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 ﬁll these in:

• Class A, B, C

• Leading zeros for the network and node portion of the IP address.

100 Chapter6

HP E3000-IX, E3000 MPE-IX User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

2 Networking Concepts

Network Environment Design Considerations

Line Speed

Geographical Location

Special Cases

Shared Dial Links

Non-HP e3000 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

Identifying Neighbor Gateways

Neighbor Gateway Examples

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

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

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

Node Worksheet Information

Neighbor Gateway Worksheet Information

Neighbor Gateway Reachable Networks Worksheet Information

5 Introductory Screens

Start NMMGR