HP E3000-IX, E3000 MPE-IX User Manual

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

+ 202 hidden pages