HP e3000/iX Network Planning and Configuration Guide HP e3000 MPE/iX Computer Systems Edition 6 Manufacturing Part Number: 36922-90043 E0801 U.S.A.
Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
Contents 1. Network Configuration Overview Pre-Configuration Hardware Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Pre-Configuration Software Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Configuration Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2. Networking Concepts Network Environment Design Considerations. . . . . . . . . .
Contents Communication Between Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 Network Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 IP Network Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 Completing the Internetwork Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 5. Introductory Screens Begin Configuration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Start NMMGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Open Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Select NS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 11. Configuring the Network Directory Open Network Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153 Select Update Directory Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155 Add Nodes to Network Directory File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157 Configure Path Report Data for a Node . . . . . . . . . . . . . . . . . . . .
Contents Updating From a Previous MPE/iX Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Reconfiguration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 B. NS X.25 Migration: NS 3000/V to NS 3000/iX Differences Between NS 3000/V and NS 3000/iX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents D. PCI 10/100Base-TX/3000 Quick Installation Notes on Manual Speed and Duplex Mode Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .222 Notes on Autonegotiation and Autosensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223 Quick Troubleshooting Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 Configuration Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Figure 3-1. Internetwork Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Figure 3-2. LAN Network Map . . . .
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 Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Figure 11-1.
Tables Table 2-1. Valid Addresses of Example Subnetwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Table 2-2. Configuration Maximums . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Table 3-1. Internetwork Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Table 3-2. LAN Network Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Table 3-3.
Tables 12
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 configuration process for that network. It also provides step-by-step instructions to assist you in configuring the network links for HP e3000 systems. Audience This manual is intended for network managers and planners who are responsible for setting up and configuring a communications network.
Chapter 5 , “Introductory Screens,” provides step-by-step instructions for configuring NMMGR introductory screens. Chapter 6 , “Configuring a LAN Node,” provides step-by-step instructions for configuring IEEE802.3/Ethernet LAN, token ring, and Fiber Distributed Data Interface (FDDI) links. Chapter 7 , “Configuring a Point-to-Point Node,” provides step-by-step instructions for configuring Point-to-Point (router) links. Chapter 8 , “Configuring a X.
Related HP Publications The following manuals are referenced in this manual or may be of use to you as you plan and configure your network. Networking • Using the Node Management Services (NMS) Utilities • Configuring and Managing Host-Based X.25 Links • Managing Host-Based X.
1 Network Configuration Overview This manual provides step-by-step instructions you can use to configure an HP e3000 node for network communications. You can use the information to configure an IEEE 802.3/Ethernet, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T, Point-to-Point (router), or X.25 node. Before you begin configuration, you must ensure your network is physically set up and ready for network configuration. This chapter provides information you should know before you begin configuration.
Network Configuration Overview Pre-Configuration Hardware Check Pre-Configuration Hardware Check Before beginning the actual configuration process, check that the hardware components required for NS 3000/iX have been installed and verified according to the procedures in the hardware installation manuals listed in the preface to this guide.
Network Configuration Overview Pre-Configuration Software Check Pre-Configuration Software Check Once you have verified that your hardware has been correctly installed, verify that the appropriate software is installed by performing the following steps: 1. Ensure that the Datacommunications and Terminal Subsystem (DTS) has been configured. If DTS has not been configured, refer to Configuring Systems for Terminals, Printers, and Other Serial Devices and configure the DTS before proceeding. 2.
Network Configuration Overview Configuration Process Overview Configuration Process Overview The instructions in this guide explain how to configure each node on your network by using a “guided” branch of Hewlett-Packard’s NMMGR configuration program. The principal steps in this process are as follows: 1. Plan your network before you begin NMMGR. Use the worksheets provided in Chapter 4 , “Planning for Node Configuration,” to record all the items NMMGR requires.
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.
Networking Concepts Network Environment Design Considerations Network Environment Design Considerations Network and internetwork design must take many factors into consideration: the desired physical location of the computers comprising the network, the volume of projected communications traffic between nodes, communications traffic patterns, and the possibility of connections to other types of nodes (such as those in a public data network) are just some of the criteria to consider.
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.
Networking Concepts Network Environment Design Considerations The maximum number of concurrent processes may limit the number of remote logons before the maximum number of dynamic I/O devices does. Dynamic Ldevs This is actually a system parameter that can be configured to 999 in SYSGEN. The default is 332, but the actual number that can be in use may be limited by the IDD/ODD limits. VT and NS use one dynamic ldev per remote session and one per LAN link and one per Point-to-Point link.
Networking Concepts Network Interface and Link Types Network Interface and Link Types The network interface (NI), the software that provides an interface between a node and a network, specifies the type and maximum number of links that can be configured for a node. Because a node’s network interface determines what links can be configured for the node, links are said to be configured underneath network interfaces. There are nine types of network interfaces (in addition to loopback): • LAN for IEEE 802.
Networking Concepts Network Interface and Link Types • An FDDI interface can have only one link configured under it; however, a single link can reach a large number of nodes. FDDI/iX Network Link can support up to 1000 nodes. Up to four FDDI NIs can be active at a time per system. • A Point-to-Point network interface can have up to 40 links configured under it.
Networking Concepts Subnetworks Subnetworks IP Subnets are used to divide one network into two or more distinct subnetworks. Subnet numbers identify subnetworks in the same way that network addresses identify physically distinct networks. Subnetting divides the node address portion of an IP address into two portions—one for identifying a specific subnetwork and one for identifying a node on that subnetwork. Why Use Subnets? The use of subnets is optional.
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.
Networking Concepts Subnetworks 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 identifier. The subnet mask turns on (sets to 1) all the relevant bits for its subnet scheme. The subnet mask for example 1 is shown below. Note that the most significant three bits of the rightmost byte are set. Subnet Mask Binary 11111111.11111111.11111111 11100000 Decimal 255.255.
Networking Concepts Subnetworks Table 2-1 Valid Addresses of Example Subnetwork Subnet Address of Subnetwork in Binary Decimal Value of Subnetwork Possible Node Address on Subnetwork Decimal Value of Rightmost Byte 1 001 (00000) 32 00001–11110 33–62 2 010 (00000) 64 00001–11110 65–94 3 011 (00000) 96 00001–11110 97–126 4 100 (00000) 128 00001–11110 129–158 5 101 (00000) 160 00001–11110 161–190 6 110 (00000) 192 00001–11110 193–222 By looking at the binary values of two
Networking Concepts Internetworks Internetworks Two or more networks of the same type or of different types can be linked together to form an internetwork or internet. For example, if you wanted to connect the nodes in a Point-to-Point network with the nodes on a LAN, the combination of the two networks would be called an internetwork. Creation of an internetwork allows any node on one network to communicate with any node on another network that is part of the same internetwork.
Networking Concepts Internetworks Gateway Configuration Overview Gateway configuration includes both identifying neighbor gateways in each node’s configuration file and configuring gateway half NIs for nodes that will serve as one half of a gateway half pair. These tasks are described as follows.
Networking Concepts Internetworks • Example 4: One of the gateways on your internetwork may be designated as a default gateway, such as node C in Figure 2-3. A default gateway is a gateway that is designated to receive any traffic for which the network is unable to identify a destination. You must identify the node as a default gateway in the configuration file of each node that will access it as the default gateway.
Networking Concepts Internetworks Gateway halves require the configuration of two separate network interfaces on each node: one for the gateway half, the other for the network it interfaces to (for example, a LAN or Point-to-Point NI). You will need to follow the instructions for the specific NI type, depending on the network type) and then follow the instructions to enter configuration items specific to the gateway half NI.
Networking Concepts Address Resolution Address Resolution Address resolution in NS networks refers to the mapping of node names to IP addresses and the mapping of IP addresses to lower level addresses (such as an X.25 address or a station address). Several address resolution methods are available for you to use individually or in combination with each other. You can configure these methods according to the needs of your network. The available address resolution methods are: • Domain name services.
Networking Concepts Address Resolution Network Directory The network directory is a set of files that contain information used by the node to communicate with other nodes in the internetwork. 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.
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.
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.
Networking Concepts Network Design Questions Network Design Questions Ask yourself the following questions to make sure your design adheres to the considerations mentioned above: 1. Are all of the nodes in the network within roughly 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 offload part of the CPU load. 2.
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.
Networking Concepts Software Configuration Maximums Software Configuration Maximums The software maximums as shown in Table 2-2, must be adhered to when configuring a supported link. These maximums may be further limited by the system hardware (number of available slots). Maximums are also documented throughout the manual for the appropriate screen.
Networking Concepts Software Configuration Maximums 42 Chapter 2
3 Planning Your Network This chapter will help you to draw your network map and contains worksheets to help you plan your network, internetwork, gateway, and network directory configuration. You will need to consider a number of items as you plan your configuration. This chapter provides guidelines to help you accomplish the following: • Draw an internetwork map. • Complete the internetwork table. • Draw a network map and complete network worksheets for each link that you are configuring.
Planning Your Network Drawing an Internetwork Map Drawing an Internetwork Map This section deals with the internetwork as a whole. The internetwork worksheets consist of an internetwork map, which shows an overview of your internetwork, and an internetwork table. You will take the following steps when filling out the internetwork worksheets: • Draw sketches of each network in the internetwork. • Write network names, IP network addresses, and network types. • Draw gateway nodes.
Planning Your Network Drawing an Internetwork Map Figure 3-1 Internetwork Map NET2 C 192.002.250 XXX POINT-TO-POINT K B A N1 NET4 C 192.004.002 XXX TOKEN RING N2 N3 G NET1 C 192.001.001 XXX LAN DTC C Router Router NET6 C 192.006.003 XXX FDDI H L X.25 PSN N5 DTC I DTC NET3 C 192.003.251 XXX X.25 NET5 C 192.005.
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 specific IP node addresses do not need to be shown until completion of specific parts of the network worksheets, so node portions of IP addresses will be represented with XXX in some maps and tables.
Planning Your Network Completing the Internetwork Table Completing the Internetwork Table Once your internetwork map contains the information just described, you are ready to complete the internetwork table (Table 3-1). The information requested for the first three columns of the internetwork table can be taken directly from the internetwork map, as in the example. In the Implementation Priority column, consider which networks must be operational immediately.
Planning Your Network Drawing a Network Map Drawing a Network Map A network map provides information about the configuration of the computers on the network and their access to remote computers. A network map can be invaluable when troubleshooting. Whenever you install a new system on your network, be sure you also update your network map. If you have not previously created a network map, create one now and keep it updated whenever you add or delete computers or interface cards or make cable changes.
Planning Your Network Network Worksheets Network Worksheets For each network in your internetwork, you are asked to draw a map of the network and to complete two tables. One table lists node-specific information, and one table lists network routing information. You also are asked to complete worksheets for each gateway half pair in your internetwork.
Planning Your Network Network Worksheets Figure 3-2 LAN Network Map NET1 C 192.001.001.XXX LAN GATEWAY NODE TO NET4: A N1 N2 GATEWAY NODE TO NET2: N3 B NET2 C 192.002.250.XXX POINT-TO-POINT NET4 C 192.004.002.XXX TOKEN RING G GATEWAY HALF H GATEWAY HALF DTC ROUTER NET5 NET3 C 192.005.252.XXX DTC C 192.003.251.XXX LAN X.25 LAN Network Table Refer to the LAN network map to fill in the LAN network table (Table 3-2). The first column lists the names of all the nodes on NET1.
Planning Your Network Network Worksheets LAN Internet Routing Table The purpose of the LAN internet routing table (Table 3-3) is to list all possible networks that can be reached from each gateway node on a LAN, such as NET1 in the example. As shown on the internetwork map, NET1 includes a 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.
Planning Your Network Network Worksheets Point-to-Point Network Worksheets One set of Point-to-Point network worksheets should be used for each Point-to-Point network in your internetwork. These network worksheets consist of a map of the Point-to-Point network and two tables. One table contains information about each node on the network and one table contains network-specific internet routing information. Point-to-Point Network Map NET2 is the Point-to-Point network in the sample internetwork.
Planning Your Network Network Worksheets Point-to-Point Network Table Refer to the Point-to-Point network map to fill in the Point-to-Point network table (Table 3-4). We have completed the first column by listing the names of all the nodes on NET2. Each node is assigned an IP address that is unique within the network. Only the node portions of the IP addresses are listed because we have listed the IP network address at the top of the table.
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 DESTINATION HOPS TO DESTINATION B 001 NET1 C 192.001.001 XXX 1 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 NET5 C 192.005.252 XXX 1 NET3 C 192.003.251 XXX 2 NET1 C 192.001.001 XXX 3 NET4 C 192.004.
Planning Your Network Network Worksheets Figure 3-4 X.25 Network Map B NET1 DTC NET3 C 192.003.251 XXX X.25 Central Admin Node X.25 PSN H DTC DTC NET5 I J X.25 Network Table Refer to the X.25 network map to fill in the X.25 network table as shown in Table 3-6. We complete the first column by listing the names of all the nodes on NET3. Each node is assigned an IP address that is unique within the network.
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) X.25 ADDRESS H 001 Y 1234 I 002 5678 J 003 6879 B 004 9876 X.25 Internet Routing Table The purpose of the X.25 internet routing table (Table 3-7) is to list the other networks in the internetwork that can be reached from the X.25 network, which is NET3 in the example.
Planning Your Network Network Worksheets 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.
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.
Planning Your Network Network Directory Worksheet Network Directory Worksheet You can complete the network directory information table shown below for each network directory you are configuring. For your node and for each destination node, you must make a full entry in the network directory. The entry includes the destination node’s name and IP address, its NI type, the global/local setting, and any additional address that is required based on the NI type.
Planning Your Network Network Directory Worksheet 60 Chapter 3
4 Planning for Node Configuration This chapter describes how to complete node worksheets before you start configuration. You will need to collect some information ahead of time to complete these tasks. The main purpose of the node worksheets is to determine the information you will need to configure for each node during NMMGR’s guided configuration. This information depends on the type of network you have.
Planning for Node Configuration Node Worksheet Information Node Worksheet Information Table 4-1, has a description of the information that needs to be gathered for the worksheets that are in this chapter. Check the worksheets to see which is the appropriate information to gather. This information is used in the configuration chapters of this manual. Table 4-1 Configuration Worksheet Information Field Screen Description Address key X.
Planning for Node Configuration Node Worksheet Information Table 4-1 Configuration Worksheet Information Field Screen Description IP address LAN Configuration; Token Ring Configuration; FDDI Configuration; Point-to-Point Configuration; X.25 Configuration There are two methods of entering an internet protocol (IP) address within NMMGR: 1. Enter the fully qualified IP address (for example, Class C, C 192.191.191 009). OR 2.
Planning for Node Configuration Node Worksheet Information Table 4-1 Configuration Worksheet Information Field Screen Description (FDDI Link name) FDDI Configuration This represents the FDDI card for which you are configuring a link. (100VG-AnyLAN Link name) LAN Configuration This represents the 100VG-AnyLAN card for which you are configuring a link. (100Base-T Link name) LAN Configuration This represents the 100Base-T card for which you are configuring a link. (X.25 Link name) X.
Planning for Node Configuration Node Worksheet Information Table 4-1 Configuration Worksheet Information Field Screen Description Network directory name X.25 Virtual Circuit Configuration The network directory name must be configured for each new node. The network directory contains information that one node needs in order to communicate with other nodes. The only network directory name supported by HP is NSDIR.NET.SYS.
Planning for Node Configuration Node Worksheet Information Table 4-1 Configuration Worksheet Information Field Screen Description Proxy node LAN Configuration The proxy field is optional. Enter Y (yes) only if your network has internetworks (networks with gateways) or non-HP nodes. Establishing a proxy node is a way of placing node name and address mapping information in a single location. For more information, see the configuration chapter for LAN link. Remote IP address X.
Planning for Node Configuration Node Worksheet Information LAN Configuration Worksheet Fill out the following worksheet (Figure 4-1) for each LAN link you are configuring.
Planning for Node Configuration Node Worksheet Information Token Ring Configuration Worksheet Fill out the following worksheet (Figure 4-2) for each Token Ring link you are configuring.
Planning for Node Configuration Node Worksheet Information FDDI Configuration Worksheet Fill out the following worksheet (Figure 4-3) for each FDDI link you are configuring.
Planning for Node Configuration Node Worksheet Information 100VG-AnyLAN Configuration Worksheet Fill out the following worksheet (Figure 4-4) for each 100VG-AnyLAN link you are configuring.
Planning for Node Configuration Node Worksheet Information 100Base-T Configuration Worksheet Fill out the following worksheet (Figure 4-5) for each 100Base-T link you are configuring.
Planning for Node Configuration Node Worksheet Information Point-to-Point Configuration Worksheet Fill out the following worksheet (Figure 4-6) for each Point-to-Point link you are configuring.
Planning for Node Configuration Node Worksheet Information X.25 Configuration Worksheet Fill out the following worksheet (Figure 4-7) for each X.25 link you are configuring. Figure 4-7 X.
Planning for Node Configuration Node Worksheet Information X.25 Virtual Circuit Configuration Worksheet Fill out the following worksheet (Figure 4-8) for each X.25 Virtual Circuit you are configuring. Figure 4-8 X.
Planning for Node Configuration Neighbor Gateway Worksheet Information Neighbor Gateway Worksheet Information The following is a description of the information that needs to be gathered for the worksheets that follow in this chapter. This information is used for configuring nodes. Gateway name Enter the name of a gateway that is on the same network as the node that you are configuring. (Nodes are on the same network if the network portions of their IP addresses are the same.
Planning for Node Configuration Neighbor Gateway Worksheet Information Neighbor Gateway Configuration Worksheet Fill out the following worksheet (Figure 4-9) for each neighbor gateway you are configuring.
Planning for Node Configuration Neighbor Gateway Reachable Networks Worksheet Information Neighbor Gateway Reachable Networks Worksheet Information The following is a description of the information that needs to be gathered for the worksheets that follow in this chapter. This information is used for configuring nodes. Neighbor Gateway IP Internet Address This is the IP address of the gateway specified on the Neighbor Gateways screen. The IP address is in the same format as the LAN Configuration screen.
Planning for Node Configuration Neighbor Gateway Reachable Networks Worksheet Information Neighbor Gateway Reachable Networks Configuration Worksheet Fill out the following worksheet (Figure 4-10) for each neighbor gateway reachable network you are configuring.
Introductory Screens 5 The introductory screens are the first few screens that are displayed when you configure a node using NMMGR. Figure 5-1 shows the screen flow of the introductory screens. [FUNCTION] denotes the function key used at a screen to invoke the next screen on the screen flow. This chapter describes the introductory screens relevant to configuring NS unguided networks.
Introductory Screens Begin Configuration Process Begin Configuration Process The procedures that follow describe how to modify the NMMGR configuration file 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 (:). 2. Press [RETURN]. NOTE You can modify the link configurations in NMCONFIG.PUB.SYS when the Network Services are active.
Introductory Screens Begin Configuration Process Open Configuration File The Open Configuration/Directory File screen (#1) in Figure 5-2 is the first screen displayed when you run NMMGR. Figure 5-2 Open Configuration/Directory File Screen Follow the steps listed here to enter data for this screen. Refer to “Fields” subsection for detailed information about each field on the screen. Step 1.
Introductory Screens Begin Configuration Process When you are ready to use an offline configuration file, rename it as NMCONFIG.PUB.SYS and reboot the system. (Keep in mind that any file you use as a configuration file must be successfully validated before you try to use it.) Backup configurationfile name A backup file name must be specified whenever a configuration file is opened or created. The default backup configuration file name is NMCBACK.group.account.
Introductory Screens Begin Configuration Process Select NS Configuration To Select NS Configuration. The Main screen (#2) in Figure 5-3 is displayed after you create or open a configuration file by pressing the [Open Config] key from the Open Configuration Directory File screen (#1) in Figure 5-2. Figure 5-3 Main Screen Step 1. Ensure that the information in the fields on this screen is correct.
Introductory Screens Begin Configuration 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 field contains 16 or fewer characters (alphanumeric, underscore, or hyphens). The first character of each field must be alphabetic. The nodename portion of each node name must be unique within the node’s network. The nodename.
Introductory Screens Begin Configuration Process Select Guided Configuration The NS Configuration screen (#166) in Figure 5-4 is displayed if you press the [NS] key at the Main screen (#2) in Figure 5-3. Figure 5-4 NS Configuration Screen Step 1. If you are using domain names for network access, replace the node name in the field at the bottom of the screen with this system’s domain name and press the [Save Data] key. If not using domain names, leave the node name as is. Step 2.
Introductory Screens Begin Configuration Process Guided/Unguided Configuration Hewlett-Packard recommends that you press the [Guided Config] key to select the guided configuration branch whenever you need to initially configure a network interface. Guided configuration supplies many default values for your configuration and requires that you visit a minimal number of screens. This manual provides information on every screen available to you through unguided NS configuration.
Introductory Screens Begin Configuration Process Perform Guided Network Transport Configuration The Network Transport Configuration screen (#42) in Figure 5-5 is displayed if you press the [Guided Config] key at the NS Configuration screen (#166) in Figure 5-4. Figure 5-5 Network Transport Configuration Screen Step 1. Next to the words Enter a network interface:, enter a name for the selected network interface (for example, LANNI). Step 2.
Introductory Screens Begin Configuration 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 configured on a node is 48. One of the 48 allowable NIs is reserved for loopback. (Loopback is configured for you automatically.
Configuring a LAN Node 6 This chapter provides step-by-step instructions for configuring local area network (LAN), Token Ring, Fiber Distributed Data Interface (FDDI), 100VG-AnyLAN, and 100Base-T links. This manual assumes that you are using the guided configuration capabilities of NMMGR. Figure 6-1 shows the screen flow for configuring LAN, Token Ring, FDDI, 100VG-AnyLAN, and 100Base-T screens.
Configuring a LAN Node Before using NMMGR to configure a link, you should complete the worksheets provided. See Chapter 4 , “Planning for Node Configuration,” for more information on planning your configuration and filling out the configuration worksheets. This chapter includes step-by-step instructions to help you perform the following tasks: • Begin the configuration process. • Configure a LAN, Token Ring, FDDI, 100VG-AnyLAN, or 100Base-T network interface.
Configuring a LAN Node Configure a LAN Network Interface Configure a LAN Network Interface The LAN Configuration screen (#41) in Figure 6-2 is displayed when you press the [Config Network] key at the Network Transport Configuration screen (#42) with an NI type of 1 (LAN). Refer to Chapter 5 , “Introductory Screens,” for information on the Network Transport Configuration screen. Figure 6-2 LAN Configuration Screen Step 1.
Configuring a LAN Node Configure a LAN Network Interface Step 6. Tab down to the field called Physical path of LANIC. Enter the physical path number corresponding to the SPU slot number where the LAN interface controller card is located. Step 7. Tab down to the field called Enable Ethernet (Y/N). By default, ethernet is enabled. Change the field to N if you do not want ethernet and the ARP protocol enabled. Step 8. Tab down to field called Enable IEEE 802.3 (Y/N). By default, IEEE 802.3 is enabled.
Configuring a LAN Node Configure a LAN Network Interface You need not enter the following items as NMMGR will fill these in: • Class A, B, C • Leading zeros for the network and node portion of the IP address. HP assigns the network portion (initial nine digits) of IP addresses from ARPA Class C, though your addresses may also be of Classes A or B. The complete formats are: Class A nnn xxx.xxx.xxx B nnn.nnn xxx.xxx C nnn.nnn.
Configuring a LAN Node Configure 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 configuring an internetwork or a network with non-HP nodes, it may be easier to update your configurations if you have them located in a central place, that is, the proxy node. On an internetwork, the proxy node is usually a gateway. (It is not necessary to configure a proxy node if you have configured domain names.
Configuring a LAN Node Configure a LAN Network Interface Enable Ethernet? A Y in this field enables ethernet for the LAN. You can enable either ethernet or IEEE 802.3 or both simultaneously. One or the other must be enabled (both fields may not be set to N). Ethernet is enabled by default. Disabling Ethernet has the effect of disabling the ARP protocol and you will need to handle both name to IP and IP to station (MAC) address resolution by other means. Enable IEEE 802.
Configuring a LAN Node Configure a Token Ring Network Interface Configure a Token Ring Network Interface The Token Ring Configuration screen (#49) in Figure 6-3 is displayed when you press the [Config Network] key at the Network Transport Configuration screen (#42) with an NI type of 6 (Token Ring). Refer to Chapter 5 , “Introductory Screens,” for information on the Network Transport Configuration screen. Figure 6-3 Token Ring Configuration Screen Step 1.
Configuring a LAN Node Configure a Token Ring Network Interface Step 5. Press the [Save Data] key to save the Token Ring link configuration. If you need to identify neighbor gateways, press the [Neighbor Gateways] key and proceed to the section in the chapter called “To Identify Neighbor Gateways.” Otherwise, proceed to Chapter 10 , “Validating and Cross-Validating with SYSGEN,” and press the [Validate Netxport] key.
Configuring a LAN Node Configure a Token Ring Network Interface 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 specified in the same format as an IP address. The 32-bit mask is grouped in octets expressed as decimal integers and delimited by either a period (.) or a space.
Configuring a LAN Node Configure an FDDI Network Interface Configure an FDDI Network Interface The FDDI Configuration screen (#201) in Figure 6-4 is displayed when you press the [Config Network] key at the Network Transport Configuration screen (#42) with an NI type of 7 (FDDI). Refer to Chapter 5 , “Introductory Screens,” for information on the Network Transport Configuration screen. Figure 6-4 FDDI Configuration Screen Step 1.
Configuring a LAN Node Configure an FDDI Network Interface Step 5. Press the [Save Data] key to save the FDDI link configuration. If you need to identify neighbor gateways, press the [Neighbor Gateways] key and proceed to the section in the chapter called “To Identify Neighbor Gateways.” Otherwise, proceed to Chapter 10 , “Validating and Cross-Validating with SYSGEN,” and press the [Validate Netxport] key.
Configuring a LAN Node Configure an FDDI Network Interface HP assigns the network portion (initial nine digits) of IP addresses from ARPA Class C, though your addresses may also be of Classes A or B. The complete formats are: Class A nnn xxx.xxx.xxx B nnn.nnn xxx.xxx C nnn.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.
Configuring a LAN Node Configure an FDDI Network Interface 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 If you are unsure of the slot location or of the physical path number to configure for your system, run the offline ODE MAPPER utility, see your system documentation, or consult your Hewlett-Packard service representative.
Configuring a LAN Node Configure Neighbor Gateways Configure Neighbor Gateways You need to visit the next two screens only if you are configuring a non-gateway node that is on the same network as a gateway. In this case, the non-gateway node needs to know the identity of any neighbor gateway. Neighbor gateways can be either full or half gateways. Gateways that are on the same network are called neighbor gateways.
Configuring a LAN Node Configure Neighbor Gateways Identify Neighbor Gateways (If Any Are Present) The Neighbor Gateways screen (#152) in Figure 6-5 is displayed when you press the [Neighbor Gateways] key at the selected Guided configuration screen for the LAN, Token Ring and FDDI networks. Figure 6-5 Neighbor Gateways Screen Step 1. In the Gateway name field, enter the name of a gateway that is on the same network as the node that you are configuring.
Configuring a LAN Node Configure Neighbor Gateways Identify Neighbor Gateway Reachable Networks The Neighbor Gateway Reachable Networks screen (#158) in Figure 6-6 is displayed when you press the [Add] or [Modify] key for a valid gateway name from the Neighbor Gateways screen (#152) in Figure 6-5. Figure 6-6 Neighbor Gateway Reachable Networks Screen Step 1. In the Neighbor Gateway IP Internet Address field, enter the IP address of the gateway specified on the Neighbor Gateways screen. C 192.191.
Configuring a LAN Node Configure Neighbor Gateways per page). If you need to configure more than 10 networks, press the [Save Data] key then press the [Next Page] key to enter more networks. Step 6. After you have finished entering the IP addresses of all the reachable networks, press the [Save Data] key. Press the [Prior Screen] key to return to the Neighbor Gateways screen. Step 7.
Configuring a Point-to-Point Node 7 This chapter provides step-by-step instructions for configuring Point-to-Point links. (Point-to-Point links are sometimes referred to as router links.) This manual assumes that you are using the guided configuration capabilities of NMMGR. Figure 7-1 shows the screen flow for configuring Point-to-Point screens. Screens unique to Point-to-Point configuration are indicated by bold boxed screens.
Configuring a Point-to-Point Node Before using NMMGR to configure a link, you should complete the worksheets provided. See Chapter 4 , “Planning for Node Configuration,” for more information on planning your configuration and filling out the configuration worksheets. This chapter includes step-by-step instructions to help you perform the following tasks: • Begin the configuration process. • Configure a Point-to-Point network interface. • Configure neighbor gateways. • Configure node mapping.
Configuring a Point-to-Point Node Configure a Point-to-Point Network Interface Configure a Point-to-Point Network Interface The Point-to-Point Configuration screen (#44) in Figure 7-2 is displayed when you press the [Config Network] key at the Network Transport Configuration screen (#42) with an NI type of 2 (Point-to-Point). Refer Chapter 5 , “Introductory Screens,” for information on the Network Transport Configuration screen. Figure 7-2 Point-to-Point Link Configuration Screen Step 1.
Configuring a Point-to-Point Node Configure a Point-to-Point Network Interface Step 5. Tab to the Speed field. Enter the line transmission speed of this link. Step 6. Tab to the Type field. Enter DD for direct dial, SD for shared dial or DC for direct connection. Step 7. Tab to the Card Type field. Enter LAPBMUX if ACC adapter is being used, or LAPB for a PSI adapter. Do not mix both Card Types under the same NI. Step 8. Press the [Save Data] key to record the data you have entered. Step 9.
Configuring a Point-to-Point Node Configure a Point-to-Point Network Interface You need not enter the following items as NMMGR will fill these in: • Class A, B, C • Leading zeros for the network and node portion of the IP address. HP assigns the network portion (initial nine digits) of IP addresses from ARPA Class C, though your addresses may also be of Classes A or B. The complete formats are: Class A nnn xxx.xxx.xxx B nnn.nnn xxx.xxx C nnn.nnn.
Configuring a Point-to-Point Node Configure a Point-to-Point Network Interface space. An IP mask is used when configuring subnetworks. The mask identifies which bits of an IP address will be used to define a subnetwork. To determine these bits, you first need to estimate how many subnetworks and nodes per subnetwork you need. See Chapter 2 , “Networking Concepts,” for details on deriving an IP subnet mask.
Configuring a Point-to-Point Node Configure a Point-to-Point Network Interface Type Chapter 7 Enter DD (direct dial) if you always want to call the same host over a dial link. If you choose DD the remote host does not have to be adjacent and other nodes can be accessed through the remote host. Enter SD if you want to call more than one adjacent remote node over a dial link without reconfiguring.
Configuring a Point-to-Point Node Configure Neighbor Gateways Configure Neighbor Gateways You need to visit the next two screens only if you are configuring a non-gateway node that is on the same network as a gateway. In this case, the non-gateway node needs to know the identity of any neighbor gateway. Neighbor gateways can be either full or half gateways. Gateways that are on the same network are called neighbor gateways.
Configuring a Point-to-Point Node Configure Neighbor Gateways Specify Neighbor Gateways (If Any Are Present) The Neighbor Gateways screen (#152) in Figure 7-3 is displayed when you press the [Neighbor Gateways] key at the Point-to-Point Link Configuration screen (#44) in Figure 7-2. Figure 7-3 Neighbor Gateway Screen Step 1. In the Gateway name field, enter the name of a gateway that is on the same network as the node that you are configuring.
Configuring a Point-to-Point Node Configure Neighbor Gateways Specify Neighbor Gateway Reachable Networks The Neighbor Gateway Reachable Networks screen (#158) in figure 7-4 is displayed when you press the [Add] key or the [Modify] key for a valid gateway name from the Neighbor Gateways screen (#152) in Figure 7-3. Figure 7-4 Neighbor Gateway Reachable Networks Step 1. In the Neighbor Gateway IP Internet Address field, enter the IP address of the gateway specified on the Neighbor Gateways screen.
Configuring a Point-to-Point Node Configure Neighbor Gateways Step 6. After you have finished entering the IP addresses of all the reachable networks, press the [Save Data] key. Press the [Prior Screen] key to return to the Neighbor Gateways screen. Step 7. Back at the Neighbor Gateways screen, after you have finished adding all of the neighboring gateways, press the [Prior Screen] key to return to the Point-to-Point Link Configuration screen.
Configuring a Point-to-Point Node Configure Node Mapping Configure Node Mapping The screens discussed in the following pages allow you to configure shared dial or direct connect and dial node mapping. These screens allow you to specify routes to target (destination) nodes and to indicate the priority of each route. The number of mappings you enter depends on how many links are on the node you are configuring.
Configuring a Point-to-Point Node Configure Node Mapping Configure Shared Dial Node Mapping The Shared Dial Node Mapping Configuration screen (#46) in Figure 7-5is displayed if you press the [Link Routing] key at the Point-to-Point Link Configuration screen (#44) for a link of type SD. Figure 7-5 Shared Dial Node Mapping Configuration Screen Each router NI can have up to 1024 mappings. However, 4096 is the absolute maximum number of unique phone numbers supported per NMCONFIG File. Step 1.
Configuring a Point-to-Point Node Configure Node Mapping Step 6. In the Disable Route field, leave the default alone unless you want to temporarily disable a configured route. Step 7. Press the [Save Data] key to save the data on the screen. Proceed to Chapter 10 , “Validating and Cross-Validating with SYSGEN,” and press the [Validate Netxport] key. Optional Keys Press the [Next Link] key to call up another link when you want to configure information about its adjacent and non-adjacent nodes.
Configuring a Point-to-Point Node Configure Node Mapping Phone Number Required if the link is a dial link. The field must be blank if the target node is non-adjacent. Enter the telephone number as a combination of decimal numbers (0 through 9), dashes, and the following special characters: / Separator used for automatic call units that have second dial-tone detect. E Optional end-of-number indicator. D Three-second delay (used for European modems and automatic call units that require built-in delays).
Configuring a Point-to-Point Node Configure Node Mapping Configure Direct Connect/Dial Node Mapping The Direct Connect/Dial Node Mapping Configuration screen (#45) in Figure 7-6 is displayed if you press the [Link Routing] key at the Point-to-Point Link Configuration screen (#44) for a link of type DD or DC. Figure 7-6 Direct Connect/Dial Node Mapping Configuration Screen Each router NI can have up to 1024 mappings.
Configuring a Point-to-Point Node Configure Node Mapping Step 7. Enter information for non-adjacent (remote) nodes in the same manner in the fields provided. (You do not configure a phone number or security string for non-adjacent nodes.) Step 8. Press the [Save Data] key to save the data on the screen. Proceed to Chapter 10 , “Validating and Cross-Validating with SYSGEN,” and press the [Validate Netxport] key.
Configuring a Point-to-Point Node Configure Node Mapping To disable outbound dialing, enter an exclamation point (!) by itself in the phone number field. Each router NI can have up to 1024 mappings. However, 4096 is the absolute maximum number of unique phone numbers supported per NMCONFIG File. Security String An optional security string that remote nodes must use to gain dial link access to the node. It can be up to eight alphanumeric characters, left justified, with no embedded blanks.
Configuring a X.25 Node 8 This chapter provides step-by-step instructions for configuring X.25 iX System Access for systems using PC-based network management. This manual assumes that you are using the guided configuration capabilities of NMMGR. Figure 8-1 shows the screen flow for configuring X.25 screens. Screens unique to X.25 configuration are indicated by bold boxed screens. [FUNCTION] denotes the function key used at a screen to invoke the next screen on the screen flow. Figure 8-1 X.
Configuring a X.25 Node Before using NMMGR to configure a link, you should complete the worksheets provided. See Chapter 4 , “Planning for Node Configuration,” for more information on planning your configuration and filling out the configuration worksheets. This chapter includes step-by-step instructions to help you perform the following tasks: • Begin the configuration process. • Configure an X.25 network interface. • Configure neighbor gateways.
Configuring a X.25 Node Configure an X.25 Network Interface Configure an X.25 Network Interface The X.25 Configuration screen (#48) in Figure 8-2 is displayed when you press the [Config Network] key at the Network Transport Configuration screen (#42) with an NI type of 3 (X.25). Refer to Chapter 5 , “Introductory Screens,” for information on the Network Transport Configuration screen. Figure 8-2 NS Configuration Screen Step 1.
Configuring a X.25 Node Configure an X.25 Network Interface Step 5. When you are done adding links, press the [Save Data] key. Step 6. If the network that this node is on contains ANY internetwork gateway (either full or half) press the [Neighbor Gateways] key and proceed to the section in this chapter called “To Configure Neighbor Gateways.” Step 7.
Configuring a X.25 Node Configure an X.25 Network Interface HP assigns the network portion (initial nine digits) of IP addresses from ARPA Class C, though your addresses may also be of Classes A or B. The complete formats are: Class A nnn xxx.xxx.xxx B nnn.nnn xxx.xxx C nnn.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.
Configuring a X.25 Node Configure an X.25 Network Interface nodes per subnetwork you need. See Chapter 2 , “Networking Concepts,” for details on deriving an IP subnet mask. Link Name The link name identifies a specific DTC/X.25 Network Access card to be used for X.25 system-to-system connections. This link name must be the same as the link name you entered for this card when you configured your DTCs. You may configure up to 11 links. (One link must be used for loopback.
Configuring a X.25 Node Configure an X.25 Network Interface Configure X.25 Virtual Circuits The X.25 Virtual Circuit Configuration screen (#47) in Figure 8-3 is displayed if you press the [Config Directry] key from the X.25 Configuration screen (#48) in Figure 8-2. This screen lets you configure the network directory. Figure 8-3 X.25 Virtual Circuit Configuration Screen Step 1. In the Remote node name field, type in the nodename of each remote X.25 node on your network in the format nodename.domain.
Configuring a X.25 Node Configure an X.25 Network Interface NOTE An address key called POOL is already preconfigured for you though it doesn’t show up on the screen. POOL allows the node being configured to receive any incoming calls even if the remote system’s address is not configured on this screen. POOL will also allow you to use NetIPC to programmatically provide an X.25 address that is not configured on this screen. If you want to delete the POOL address key, in the last line of the X.
Configuring a X.25 Node Configure an X.25 Network Interface Remote node name You must enter the remote node name of each X.25 node into the network directory. Include entries for all remote nodes and, if you want to be able to perform loopback, the local node as well. Remote IP address Also in the network directory, you must enter the IP Address of each node whose identity you have entered into the network directory.
Configuring a X.25 Node Configure an X.25 Network Interface Facility set The facility set name is a name for a set of X.25 connection parameters. The parameters are determined by the type of X.25 network that you are subscribed to. You can configure options in a facility set so that specified options are available for every virtual circuit or negotiated for each virtual circuit on a per-call basis.
Configuring a X.25 Node Configure Neighbor Gateways Configure Neighbor Gateways Use the next two screens only if you are configuring a node that is on an an X.25 network as a gateway. In this case, the local node needs to know the identity of any neighbor gateways. Gateways that are on the same network are called neighbor gateways. A non-gateway node on an X.25 network may need to go through a neighbor gateway in order to send messages to an entirely different network.
Configuring a X.25 Node Configure Neighbor Gateways Identify Neighbor Gateways (If Any Are Present) The Neighbor Gateways screen (#152) in Figure 8-4 is displayed when you press the [Neighbor Gateways] key at the X.25 Configuration screen (#48) in Figure 8-2. Figure 8-4 Neighbor Gateways Screen Step 1. In the Gateway name field, enter the name of a gateway that is on the same network as the node that you are configuring.
Configuring a X.25 Node Configure Neighbor Gateways Identify Neighbor Gateway Reachable Networks The Neighbor Gateway Reachable Networks screen (#158) in Figure 8-5 is displayed when you press the [Add] key or the [Modify] key for a valid gateway name from the Neighbor Gateways screen (#152) in Figure 8-4. Figure 8-5 Neighbor Gateway Reachable Networks Screen Step 1. In the Neighbor Gateway IP Internet Address field, enter the IP address of the gateway specified on the Neighbor Gateways screen.
Configuring a X.25 Node Configure Neighbor Gateways if necessary, to allow configuration of up to 2550 reachable networks per link (255 pages and 10 reachable nets per page). If you need to configure more than 10 networks, press the [Save Data] key then press the [Next Page] key to enter more networks. Step 6. After you have finished entering the IP addresses of all the reachable networks, press the [Save Data] key. Press the [Prior Screen] key to return to the Neighbor Gateways screen. Step 7.
9 Configuring a Gateway Half This chapter describes how to plan and configure the interface between one gateway half and another gateway half. Gateway halves is one of the early technologies used to connect two separate networks. For information on configuring a node as a gateway half, use this manual. Gateways are rarely used since the introduction of routers and the internet.
Configuring a Gateway Half Figure 9-1 Gateway Half Link Screen Flow Open Config/ Directory File Screen [OPEN CONFIG] Main Screen [NS] If you have not created the config file, then press the OPEN CONFIG key a second time.
Configuring a Gateway Half and Cross-Validating with SYSGEN,” for step-by-step instructions to help you perform the following validation tasks: • Validate the network transport configuration. • Cross-validate in SYSGEN.
Configuring a Gateway Half Configure a Gatehalf Network Interface Configure a Gatehalf Network Interface The Gatehalf Configuration screen (#40) in Figure 9-2 is displayed when you press the [Config Network] key at the Network Transport Configuration screen (#42) with an NI type of 5 (Gateway Half). Refer to Chapter 5 , “Introductory Screens,” for information on the Network Transport Configuration screen. Figure 9-2 Gatehalf Configuration Screen Step 1.
Configuring a Gateway Half Configure a Gatehalf Network Interface Step 7. Tab down to the next field. In the Transmission speed field, either leave the default or enter the transmission speed in bits per second as a number from 1200 to 64000. Step 8. If this is a dial link, enter the phone number of this gateway half ’s partner. Step 9.
Configuring a Gateway Half Configure a Gatehalf Network Interface Link name Name that represents the hardware link. The link name can have up to eight alphanumeric characters; the first character must be alphabetic. The link name must be unique to both the node and the network. Link type The link type for a gateway half can be either DD for direct dial or DC for direct connect.
Configuring a Gateway Half Configure a Gatehalf Network Interface Phone Number Telephone number of this gateway half ’s partner gateway half. Enter the telephone number as a combination of decimal numbers (0 through 9), dashes, and the following special characters: / Separator used for automatic call units that have second dial-tone detect. E Optional end-of-number indicator. D Three-second delay (used for European modems and automatic call units that require built-in delays).
Configuring a Gateway Half Configure a Gatehalf Network Interface 146 Chapter 9
10 Validating and Cross-Validating with SYSGEN This chapter discusses the validation of the network transport configuration and cross-validation of NMCONFIG.PUB.SYS with the system configuration files within SYSGEN. Validating the network transport. This step checks data consistency between values entered on different NMMGR data entry screens. Cross-Validating with SYSGEN. Cross-validation ensures that there are no conflicts in the use of node names, device classes, and physical paths.
Validating and Cross-Validating with SYSGEN Validate the Network Transport Validate the Network Transport The following procedure assumes that you have already configured and validated the Distributed Terminal Subsystem (DTS). The DTS must be validated before you can validate the network transport (Netxport) software. Upon configuring the selected screens for your network: Step 1. Press the [Validate Netxport] key. Refer to the list of screens with the [Validate Netxport] key.
Validating and Cross-Validating with SYSGEN Validate the Network Transport ** SYSFILE configurator commands ** aauto (aa) aboot (ab) acmsl (ac) asprog (as) cmsl (cm) dauto (da) dboot (db) dcmsl (dc) dsprog (ds) lcmsl (lc) rauto (ra) rboot (rb) rcat (rc) rcmsl (rcm) rdcc (rd) ripl (ri) rnmlib (rn) rsprog (rs) show (sh) clear (cl)(c) exit (ex)(e) help (he)(h) hold (ho) sysfile> RDCC **note** Retrieving NMMGR configuration data...
Validating and Cross-Validating with SYSGEN Cross-Validate in SYSGEN Cross-Validate in SYSGEN Cross-validation is automatically done on the KEEP, TAPE, I/O, and RDCC commands in SYSGEN. Cross-validation ensures that there are no conflicts in the use of node names, device classes, and physical paths between the data currently contained in NMCONFIG.PUB.SYS and the system configuration data. To cross-validate, use the SYSGEN facility (OP capability is required).
11 Configuring the Network Directory A network directory is used by the node for internetwork routing. It is one of several ways of specifying fixed/hardcoded addresses for specific node names, in cases where dynamic name resolution cannot be used. It is also used for specifying unique node names for a system which has multiple interfaces. Each entry in a network directory consists of a node name associated with an IP address, the network type, and an additional address, if necessary.
Configuring the Network Directory NOTE If you used the guided configuration facility to configure an X.25 link, you will already have configured the network directory for that link.
Configuring the Network Directory Open Network Directory Open Network Directory The Open Configuration/Directory file screen (#1) in Figure 11-2 is the first screen displayed when you run NMMGR. Figure 11-2 Open Configuration/Directory File Step 1. Verify that the correct network directory file name is in the Network directory file name field. Step 2. If you have assigned a write access password, enter it in this field. If you are not using the password feature, leave this field blank. Step 3.
Configuring the Network Directory Open Network Directory When you are ready to use an offline configuration file, rename it as NMCONFIG.PUB.SYS and reboot the system. (Keep in mind that any file you use as a configuration file must be successfully validated before you try to use it.) Backup configurationfile name A backup file name must be specified whenever a configuration file is opened or created. The default backup configuration file name is NMCBACK.group.account.
Configuring the Network Directory Select Update Directory Function Select Update Directory Function The Network Directory Main screen (#8) in Figure 11-3 is displayed when you press the [Open Directry] function key at the Open Configuration/Directory File screen (#1) in Figure 11-2. This screen is also displayed if a network directory has already been opened and you type NETDIR in the command window of any screen and press the [Enter] key. Figure 11-3 Network Directory Main Step 1.
Configuring the Network Directory Select Update Directory Function the output to another device class or disk file. To set a file equation without leaving NMMGR, enter the appropriate MPE command in the command window and press the [Enter] key. Maint Mode Press this function key to enter the command interface to perform directory merging or to expand the size of your directory. See Using the Node Management Services (NMS) Utilities for details on maintenance mode.
Configuring the Network Directory Add Nodes to Network Directory File Add Nodes to Network Directory File The Network Directory Select Node Name screen (#9) in Figure 11-4 is displayed when you press the [Update Dir] function key at the Network Directory Main screen (#8) in Figure 11-3. The function of this screen is to display node names that are currently configured in the directory, and to allow you to delete, rename, add, or modify information about a node.
Configuring the Network Directory Add Nodes to Network Directory File Fields Node name The name of the node for which you want network directory information. The node name field must contain a fully qualified node name, in the form nodename.domain.organization, when used to add, modify, delete, or rename a node. The node name field when used with the Prev Page and Next Page function keys allows you to browse through a specified part of the network directory.
Configuring the Network Directory Add Nodes to Network Directory File both local and global entries exist for the same node, the network transport uses the local entry. Default value: Y Range: Y or N New name (Required only when renaming an existing node name.) New name to be assigned to the node with the Rename function key. New global The global/local flag setting for the node named in the new name field. The acceptable values are Y or N.
Configuring the Network Directory Configure Path Report Data for a Node Configure Path Report Data for a Node The Network Directory Data screen (#10) in Figure 11-5 is displayed when you press the [Add] or the [Modify] function key at the Select Node Name screen (#9) in Figure 11-4. Figure 11-5 Network Directory Data The function of this screen is to configure path report data for the node name listed at the top of the screen. One path report is configured for each NI on a node.
Configuring the Network Directory Configure Path Report Data for a Node Step 4. If appropriate for the type of path you are configuring, enter an address in the Additional Address field. (Type 1 requires no additional address. Types 2, 5, and 6 require a station address. Type 3 requires an X.25 address key. See additional explanation under “Fields.” Step 5. Press the [Save Data] key. Step 6. Repeat steps 2, 3, and 4 for each path report for the specified node.
Configuring the Network Directory Configure Path Report Data for a Node Type A number indicating the type of path to configure: 1 Select this path type when the NI type is ROUTER (Point-to-Point); or when the NI type is LAN and the destination node supports probe or ARP; or when the NI type is TOKEN or FDDI and the destination node supports ARP. 2 Select this path type when the NI type is LAN, 100VG-AnyLAN or 100Base-T, the destination node does not support probe, and 802.3 framing is used.
Configuring the Network Directory Configure Path Report Data for a Node Additional address A lower-level address, which depends on the type. Type 1 does not contain lower-level addressing information. You can leave the field blank, or enter the keyword NONE. Types 2, 5, 6, and 7 require the destination node’s station address, which is a string of six hexadecimal bytes, separated by dashes (XX-XX-XX-XX-XX-XX). The station address must correspond to the address configured on the remote node.
Configuring the Network Directory Configure Path Report Data for a Node 164 Chapter 11
12 Configuring Domain Name Files If you are planning to use the domain name resolver for name to IP address resolution, you will need to configure a set of ASCII files on each node that contain needed information. To configure these files, you use any standard editor to modify existing sample files according to the instructions in this chapter. See Chapter 2 , “Networking Concepts,” for more information on domain names. This chapter details: • How to modify the RSLVSAMP.NET.
Configuring Domain Name Files Create or Modify the Resolver File Create or Modify the Resolver File The resolver file (RESLVCNF.NET.SYS) is an initialization file for the domain name resolver. It contains information needed by the network to determine how to resolve a domain name to an IP address. This file is read by the resolver routines the first time they are invoked by a process. To create the resolver file, perform the following steps: Step 1. Copy the sample file, RSLVSAMP.NET.SYS, to RESLVCNF.NET.
Configuring Domain Name Files Create or Modify the Resolver File Resolver queries will be attempted using each component of the search path in turn until a match is found. Note that this process may be slow and will generate a lot of network traffic if the servers for the listed domains are not local. Note also that queries will time out if no server is available for one of the domains. nameserver NOTE Enter the IP address of a name server the resolver should query.
Configuring Domain Name Files Create or Modify the Hosts File Create or Modify the Hosts File The host name data base file, (HOSTS.NET.SYS), associates internet addresses with official host names and aliases. This allows a user to refer to a host by a symbolic name instead of an internet address. When you have configured the name server, this file serves only as a backup when the server is not running. In this circumstance, it is a common practice that HOSTS.NET.
Configuring Domain Name Files Create or Modify the Hosts File Figure 12-2 Sample Hosts Configuration File # This file contains information regarding the known hosts. # # The for for each entry is: # host IP address local host name host aliases # # Note: the entries cannot be preceded by a blank space. # 172.0.0.1 localhost loopback me myself local 192.41.12.100 basful.loc1.inet.com bashful 192.41.11.114 happy.loc1.inet.com happy 192.41.11.413 queezy.loc1.inet.com queezy 192.41.112.122 sneezy.loc2.inet.
Configuring Domain Name Files Additional Domain Name Configuration Files Additional Domain Name Configuration Files In addition to the resolver file and the host name data base, three other files are available to allow you to configure additional information about your network. Each of these files is provided in sample format in the NET.SYS account. Each sample file contains an explanation of the format for the data and a sample entry. The available files and their functions are described as follows.
Configuring Logging 13 This chapter provides step-by-step instructions for configuring logging. Logging is configured for the purpose of recording events such as errors and console commands. Figure 13-1 shows the screen flow for configuring the logging screens. Screens unique to logging are indicated by bold boxed screens. [FUNCTION] denotes the function key used at a screen to invoke the next screen on the screen flow.
Configuring Logging This chapter includes step-by-step instructions to help you perform the following tasks: • Access the logging configuration screens. • Modify the logging configuration. • Enable users for individual logging classes. • Activate logging. Logging is configured for the purpose of recording events such as errors and console commands. You configure logging for each of the subsystems of NS 3000/iX and for NS 3000/iX links.
Configuring Logging Access Logging Configuration Screens Access Logging Configuration Screens Use the following steps to reach the logging configuration screens: Step 1. Run NMMGR. The Open Configuration/Directory File screen is displayed. Step 2. Press the [OPEN CONFIG] key. The Main screen is dispayed. Step 3. Press the [NS] function key. The NS Configuration screen is displayed. Step 4. Press either the [Guided Config] or the [Unguided Config] function key. Step 5.
Configuring Logging Modify the Logging Configuration Modify the Logging Configuration The Netxport Log Configuration (1) screen (#61) in Figure 13-2 is displayed when you press the [Modify Logging] function key at the Network Transport Configuration screen. Figure 13-2 Netxport Log Configuration (1) Screen Use the fields and the function keys of the screen to configure logging for the subsystems represented on the screen.
Configuring Logging Modify the Logging Configuration (no) disables logging to the console. Disk Logging The value entered in this field specifies whether or not logging events for the subsystem and class listed beside the field will be logged to a disk file. A value must be entered for each subsystem and class listed. A Y (yes) enables logging to a file, N (no) disables logging to a file. The file name for the log file is NMLGnnnn.PUB.SYS, where nnnn is a number from 0000 to 9999.
Configuring Logging Modify the Logging Configuration Use the fields and the function keys of the screen to configure logging for the subsystems represented on the screen. If the subsystem for which you want to enable logging does not appear on this screen, press the [Next Screen] function key to go to the next Netxport Log Configuration screen. There are a total of six logging configuration screens. Enable or disable logging classes (or accept HP-recommended defaults).
Configuring Logging Modify the Logging Configuration Figure 13-4 Netxport Log Configuration (3) Screen Use the fields and the function keys of the screen to configure logging for the subsystems represented on the screen. If the subsystem for which you want to enable logging does not appear on this screen, press the [Next Screen] function key to go to the next Netxport Log Configuration screen. There are a total of six logging configuration screens.
Configuring Logging Modify the Logging Configuration enables logging to a file, N (no) disables logging to a file. The file name that NMS uses is NMLGnnnn.PUB.SYS, where nnnn is a number from 0000 to 9999. All logging classes in all subsystems are logged to this file. At each system startup, or when a file is full, NMS creates a new NMLGnnnn.PUB.SYS file, naming each successive logging file by incrementing nnnn. When NMLG9999.PUB.SYS is full, NMS names the next logging file NMLG0000.PUB.SYS.
Configuring Logging Modify the Logging Configuration record. Verify that the data record has been created by checking that the Data flag is Y. Press the [Exit Logging] function key when you have finished modifying the logging configuration. Fields Console Logging The value entered in this field specifies whether or not logging events for the subsystem and class listed beside the field will be logged to the system console. A value must be entered for each subsystem and class listed.
Configuring Logging Modify the Logging Configuration Figure 13-6 Netxport Log Configuration (5) Screen Use the fields and the function keys of the screen to configure logging for the subsystems represented on the screen. If the subsystem for which you want to enable logging does not appear on this screen, press the [Next Screen] function key to go to the next Netxport Log Configuration screen. There are a total of six logging configuration screens.
Configuring Logging Modify the Logging Configuration value must be entered for each subsystem and class listed. A Y (yes) enables logging to a file, N (no) disables logging to a file. The file name that NMS uses is NMLGnnnn.PUB.SYS, where nnnn is a number from 0000 to 9999. All logging classes in all subsystems are logged to this file. At each system startup, or when a file is full, NMS creates a new NMLGnnnn.PUB.SYS file, naming each successive logging file by incrementing nnnn. When NMLG9999.PUB.
Configuring Logging Modify the Logging Configuration Fields Enable or disable logging classes (or accept HP-recommended defaults). Press the [Save Data] key on each screen to create or modify the data record. Verify that the data record has been created by checking that the Data flag is Y. Console Logging The value entered in this field specifies whether or not logging events for the subsystem and class listed beside the field will be logged to the system console.
Configuring Logging Modify the Logging Configuration Figure 13-8 Netxport Log Configuration (7) Screen Use the fields and function keys of the screen to configure logging for the subsystems represented on the screen. The subsystems 78 (PCI 100Base-T) and 82 (Sync MUX link) can be configured from this screen. Fields Enable or disable logging classes (or accept HP-recommended defaults). Press the [Save Data] key on each screen to create or modify the data record.
Configuring Logging Enable Users for Individual Logging Classes Enable Users for Individual Logging Classes The logging screens described previously in this chapter make it possible to completely configure logging for all subsystems by traversing only seven screens. However, using these screens, it is not possible to configure logging so that messages generated by specific logging classes are sent to an individual user’s list device.
Configuring Logging Enable Users for Individual Logging Classes Step 2. To enable console logging for this subsystem logging class, enter a Y in the Enable console logging? field. To disable console logging, enter an N. Be aware that changing the value in this field will override the previous setting for the logging class you are configuring. Step 3. To enable disk logging for this subsystem logging class, enter a Y in the Enable disk logging? field. To disable console logging, enter an N.
Configuring Logging Activate Logging Activate Logging NetIPC logging is automatically activated at system start up. Link manager logging and network transport logging are activated when you initiate the network transport (NETCONTROL START). Network Services logging is activated when the Network Services are initiated (that is, when the NSCONTROL START command is issued). Network Link logging is activated when the specific link is first started.
14 Operating the Network After you have completed the configuration process, you are ready to activate NS. This chapter shows you how to bring up an NS 3000/iX node and how to shut it down. It assumes you have successfully completed the configuration steps described previously. For more detailed information on starting, stopping, and operating an NS network, see the NS 3000/iX Operations and Maintenance Reference Manual.
Operating the Network Start Links and Services Start Links and Services Start Software Loopback Issue the following command (NM capability required) to start software loopback: NETCONTROL START;NET=loopbackNIname This starts up the control process, the transport, and software loopback. Note: when you use guided NMMGR to create any NI, a loopback network interface (whose loopbackNIname is LOOP) is automatically generated.
Operating the Network Start Links and Services NOTE If you are starting an X.25 link for a system using PC-based network management or if you are not starting an X.25 link, you do not need to use the DTCCNTRL command. Start Network Services Issue the following command (NM capability required) to start the network services: NSCONTROL START This starts the NS 3000/iX Network Services, such as Virtual Terminal, Network File Transfer, Remote File Access, and Remote Data Base Access.
Operating the Network Test Network Services Test Network Services In order to test that you have successfully configured and brought up your NS node, HP provides an NS validation test called QVALNS.NET.SYS. QVALNS is a program which modifies a file called TQVALNS and streams it as a temporary job (JQVALNS). The job purges and creates various files, and then runs a program called NSTEST. NSTEST tests the network services (VT, RFA, RDBA, and NFT). To run the NS validation test, follow the step below: Step 1.
Operating the Network Shut Down Network Services Shut Down Network Services To shut down NS, issue the following commands (NM capability required): DSLINE @;CLOSE NSCONTROL STOP NETCONTROL STOP The DSLINE command shown above closes connections for your session only. NSCONTROL STOP allows existing users to continue using the services until they finish their current task but prevents new uses of the services by these users or by new users.
Operating the Network Shut Down Network Services 192 Chapter 14
A MPE/V to MPE/iX Migration This appendix provides a quick overview of the planning and tasks you will need to do to migrate an NS 3000 network from an MPE/V system to an MPE/iX system. This appendix assumes that you are migrating your network as a whole; that is, replacing all MPE V systems with MPE/iX systems and maintaining the same basic network function. The following topics are covered by this appendix: • Differences between NS 3000/V and NS 3000/iX networks. • An overview of migration tasks.
MPE/V to MPE/iX Migration Differences Between NS 3000/V and NS 3000/iX Differences Between NS 3000/V and NS 3000/iX There are a number of differences between the way NS is implemented on MPE V systems and the way it is implemented on MPE/iX systems. These differences affect the network itself, some of the applications that users may run over the network, and the command used to obtain status information about the network.
MPE/V to MPE/iX Migration Differences Between NS 3000/V and NS 3000/iX Applications Support There are also differences in the implementations of NS 3000/V and NS 3000/iX that will affect certain applications that users may currently be running on your MPE V network. These differences are as follows: • NS 3000/iX supports PTOP for HPDESK only. On NS 3000/iX PTOP is not supported for applications other than HPDESK.
MPE/V to MPE/iX Migration Migration Overview Migration Overview There are a number of steps that you must take to successfully convert an MPE V network for use as an MPE/iX network. These tasks are summarized below, and described in more detail in the remainder of this appendix. Keep in mind that, depending on the needs of your installation, you may need to perform additional tasks to complete your migration.
MPE/V to MPE/iX Migration File Conversion Guidelines File Conversion Guidelines A file conversion utility called NMMGRVER.PUB.SYS allows you to convert earlier versions of subsystems for use with the current version of Node Management Services (NMS) by converting the files to an acceptable format. When to Convert Files If you have not successfully converted your files you will be notified that conversion is necessary when you try either to run NMMGR or to perform a NETCONTROL command.
MPE/V to MPE/iX Migration File Conversion Guidelines Step 4. The system will then prompt for the name of the configuration file to be converted by displaying the message: Fileset to be scanned? You can then choose to end the conversion program by pressing the [RETURN] key, or you can enter one of the following filesets: filename [.groupname [.acctname]] @ [.groupname [.acctname]] @.@ [.acctname] @.@.@ NMMGRVER searches for files of type nconf in the specified fileset.
MPE/V to MPE/iX Migration File Conversion Guidelines This new NMCONFIG.PUB.SYS file contains your NS configuration in a format acceptable to MPE/iX. You can now run NMMGR to configure the DTS subsystem, and to perform any needed modifications to the NS configuration. See “Reconfiguration Guidelines” later in this appendix.
MPE/V to MPE/iX Migration Reconfiguration Guidelines Reconfiguration Guidelines Once the MPE/V NS configuration files have been converted for use with the MPE/iX version of NS, reconfigure your network to account for the implementation differences between NS 3000/V and NS 3000/iX. Run the NMMGR utility against the configuration file generated by the file conversion process and perform the following reconfiguration tasks: • Configure the physical path of all links for your network.
B NS X.25 Migration: NS 3000/V to NS 3000/iX This Appendix tells how to use the NMMGRVER utility to migrate (update) configuration files from a node running NS X.25 3000/V Link to a node that will be running NS 3000/iX release 2.0 or later. This appendix does not apply if an MPE V based node is being used as an X.25 server for NS 3000/XL based machines. Refer to the following appendixes depending on which X.
NS X.25 Migration: NS 3000/V to NS 3000/iX Differences Between NS 3000/V and NS 3000/iX Differences Between NS 3000/V and NS 3000/iX The following paragraphs summarize differences between NS 3000/V and NS 3000/iX. Make sure that you account for these differences that could affect your network when migrating to NS 3000/iX. For information on operating system migration, refer to the MPE/iX Migration series.
NS X.25 Migration: NS 3000/V to NS 3000/iX Differences Between NS 3000/V and NS 3000/iX PAD devices on NS 3000/V are configured (using NMMGR) as part of the X.25 network configuration. On NS 3000/iX when PC-based network management is used, PAD devices are configured both on the host (using NMMGR) and on the OpenView Windows Workstation (using the OpenView DTC Manager software).
NS X.25 Migration: NS 3000/V to NS 3000/iX Differences in X.25 Support Differences in X.25 Support There are differences in X.25 support between NS 3000/V and NS 3000/iX which need to be considered when you migrate as described in the following paragraphs. 1980 Versus 1984 CCITT NS 3000/V supports CCITT 1980 and NS 3000/iX supports both 1980 and 1984. General Level 3 Differences In MPE V X.25, a Reset is sent to initialize or clear a Permanent Virtual Circuit. In MPE/iX X.
NS X.25 Migration: NS 3000/V to NS 3000/iX Differences in X.25 Support padded with blanks. Facilities The supported facilities of the DTC/X.25 XL Network Link are shown in Table B-1. Table B-1 Supported Facilities Supported Facilities 1984 CCITT X.25 Reference Extended packet sequence number 6.2 Incoming calls barred 6.5 Outgoing calls barred 6.6 Nonstandard default packet size 6.9 Nonstandard default window size 6.10 Flow control parameter negotiation 6.12 Throughput class negotiation 6.
NS X.25 Migration: NS 3000/V to NS 3000/iX Differences in X.25 Support Pad Support For complete information on migrating PAD support from NS 3000/V to NS 3000/iX Release 2.0 or later, refer to Appendix C , “NS X.25 Migration: NS 3000/V PAD Access to NS 3000/iX.
NS X.25 Migration: NS 3000/V to NS 3000/iX Converting NS 3000/V Configuration Files to NS 3000/iX Converting NS 3000/V Configuration Files to NS 3000/iX The procedures that follow are for updating (migrating) configuration files from a node running NS X.25 3000/V Link to a node that will be running NS 3000/iX release 2.0 or later. This conversion procedure can be used with NS 3000/V NMCONFIG and NSCONF files for version V-delta 3 or later. When updating a node running NS X.
NS X.25 Migration: NS 3000/V to NS 3000/iX Saving NS 3000/V X.25 Parameters Saving NS 3000/V X.25 Parameters Make a list of the following NS 3000/V parameters that must be re-entered on the DTC. • VC Assignment from the NS 3000/V screen with the path: @NETXPORT.NI.niname.PROTOCOL.X25.VCSPEC • X.25 Network type and Flow Control parms from the NS 3000/V screen with the path: @NETXPORT.NI.niname.PROTOCOL.X25.VCSPEC. FLOWCNTL • L.U.G. Incoming Calls from the NS 3000/V screen with the path: @NETXPORT.NI.niname.
NS X.25 Migration: NS 3000/V to NS 3000/iX Copying NS 3000/V Configuration Files to NS 3000/iX System Copying NS 3000/V Configuration Files to NS 3000/iX System Restore the NS 3000/V configuration files to the NS 3000/iX system. Name the NS 3000/V files with the same names they had on the NS 3000/V node, that is, NMCONFIG.PUB.SYS, and if present, NSCONF.PUB.SYS. Remember: This procedure assumes that there is no configuration file on the NS 3000/iX node yet.
NS X.25 Migration: NS 3000/V to NS 3000/iX Using NMMGRVER Using NMMGRVER To use the NMMGRVER utility to convert your NS 3000/V configuration file to NS 3000/iX release 2.0 or later, proceed as follows: Step 1. At the MPE/iX prompt, type: NMMGRVER.PUB.SYS and answer the questions. Step 2. Do either steps a through c or steps d through g. If your NS 3000/V node had only an NMCONFIG file (but no NSCONF files), follow the instructions in steps a through c. a.
NS X.25 Migration: NS 3000/V to NS 3000/iX Using NMMGRVER 3. On the screen with the path @LINK.DTSLINK, verify that the physical path is correctly defined. 4. On the screen with the path @LINK, add the LINK name and Type (X25) of the X25 link. Note: to migrate to NS 3000/iX release 2.2 or later, repeat this step and steps 5 through 7 for each DTC/X.25 Network Access card. 5. On the screen with the path @LINK.
NS X.25 Migration: NS 3000/V to NS 3000/iX Configuring the DTC Configuring the DTC If you are using PC-based network management, configure the DTC by using the OpenView DTC Manager at your OpenView Windows Workstation. For full details, see Using the OpenView DTC Manager. If you are using host-based network management, configure the DTC using NMMGR. For full details, see Configuring and Managing Host-Based X.25 Links.
C NS X.25 Migration: NS 3000/V PAD Access to NS 3000/iX This Appendix tells how to migrate NS 3000/V versions of PAD access to NS 3000/iX release 2.0 or later. For information on migrating X.25, refer to the following appendices, depending on which network configuration you have. • Migrating a configuration file from a node running NS X.25 3000/V Link to a node that will be running NS 3000/iX release 2.0 or later, refer to Appendix B , “NS X.25 Migration: NS 3000/V to NS 3000/iX.
NS X.25 Migration: NS 3000/V PAD Access to NS 3000/iX PAD Support: NS 3000/V and NS 3000/iX PAD Support: NS 3000/V and NS 3000/iX The following paragraphs summarize differences between NS 3000/V and NS 3000/iX PAD support. You must consider these differences when migrating to NS 3000/iX. For system migration issues, refer to the MPE/iX Migration series for more information. • PAD facility sets are not supported on NS 3000/iX. • The packet sizes supported on NS 3000/iX are 128, 256, and 512.
NS X.25 Migration: NS 3000/V PAD Access to NS 3000/iX Migrating from NS 3000/V PAD Access to NS 3000/iX Migrating from NS 3000/V PAD Access to NS 3000/iX There is no conversion tool for migrating NS 3000/V PAD access to NS 3000/iX Release 2.0 or later. The tasks you must do in order to migrate from NS 3000/V PAD access to NS 3000/iX release 2.0 or later are as follows: 1. Make sure you have accounted for the differences that could affect your network as described in the previous sections of this appendix.
NS X.25 Migration: NS 3000/V PAD Access to NS 3000/iX Migrating from NS 3000/V PAD Access to NS 3000/iX • L.U.G. Inbound Address from the NS 3000/V screen with the path: @NETXPORT.NI.niname.PROTOCOL.LUGSPEC.INLUG • L.U.G. Outbound Address from the NS 3000/V screen with the path: @NETXPORT.NI.niname.PROTOCOL.X25.LUGSPEC. OUTLUG PAD Access Migration Categories The way you assign a PAD device depends on what the device is and how it will be used.
NS X.25 Migration: NS 3000/V PAD Access to NS 3000/iX Migrating from NS 3000/V PAD Access to NS 3000/iX Saving DTS Parameters Make a list of the following DTS parameters configured n the host that must also be entered into the OpenView DTC Manager. • Local Node Name. • PAD Device Name. • PAD Device Type. • DTC Node Name. • DTC Card Number. Configuring the DTC If you are using PC-based network management, configure the DTC by using the OpenView DTC Manager at your OpenView Windows Workstation.
NS X.
PCI 10/100Base-TX/3000 Quick Installation D The PCI 10/100Base-TX adapter card (A5230A) for the HP e3000 supports 10Mbits/s and 100Mbits/s Fast Ethernet operation as well as full and half-duplex modes. Ensure that the speed, duplex, and autonegotiation settings of the associated data hub or switch match the settings on this card (as configured in the network configuration file, NMCONFIG.PUB.SYS).
PCI 10/100Base-TX/3000 Quick Installation 2. Prepare system for hardware installation and access the system card bay: • Login with appropriate system management capabilities and prepare system for shutdown (e.g., terminate any active jobs or sessions, etc.) • Issue a shutdown. Make sure the system is halted before continuing. • When the system has shutdown completely, power off the system by pressing the system off button. Unplug the system.
PCI 10/100Base-TX/3000 Quick Installation • On the 100Base-T “link configuration” screen, fill in the appropriate autonegotiation, speed, and duplex settings. (For more detailed information on the various screens, see the NS 3000/iX NMMGR Screens Reference Manual. • Perform configuration verification and exit NMMGR. 6. Verify the installation: • Verify that the link starts successfully by starting a network subsystem (e.g., NETCONTROL START; NET=LAN1) that uses the newly configured link.
PCI 10/100Base-TX/3000 Quick Installation Notes on Manual Speed and Duplex Mode Configuration Notes on Manual Speed and Duplex Mode Configuration Because this PCI 10/100Base-TX LAN card supports autonegotiation, you should not normally need to manually set the duplex mode. Sometimes you may need to manually set the duplex mode of the card — for example, if the switch is operating at full duplex but does not autonegotiate. Full-duplex mode is most commonly found in switches rather than hubs.
PCI 10/100Base-TX/3000 Quick Installation Notes on Autonegotiation and Autosensing Notes on Autonegotiation and Autosensing The PCI 10/100Base-TX/3000 product provides the means for interfacing various types of HP e3000 systems to either a 10Base-T or 100Base-TX network. 100Base-TX is a subset of 100Base-T networking defined by the IEEE 802.3u-1995 standard.
PCI 10/100Base-TX/3000 Quick Installation Notes on Autonegotiation and Autosensing If the PCI 10/100Base-TX/3000 card is connected to a device that does not support autonegotiation or a device that has autonegotiation disabled, the PCI card will autosense the speed of the link and set itself accordingly. The duplex mode of the card will be set to half-duplex in this case.
PCI 10/100Base-TX/3000 Quick Installation Quick Troubleshooting Tips Quick Troubleshooting Tips Problem: Incomplete version information displayed when :NMMAINT,78 command is issued. This indicates that the MPE/iX 7.0 software installation or update has not completed successfully. Consult your HP software support representative. Problem: When an attempt is made to bring up the link (e.g., via a :NETCONTROL START command for a LAN using that link), it does not connect successfully.
PCI 10/100Base-TX/3000 Quick Installation Quick Troubleshooting Tips 226 Appendix D
Index A activate logging, 186 activating logging, 186 activating NS, 187 add directory entry, 157 add nodes to the network directory, 157 adding a node to the directory, 157 additional domain name configuration files, 170 address key, 62, 131, 133 address resolution, 35 domain name services, 35 network directory, 36 address resolution protocol, 38 administrative node, 37 ARP, 38 assigning node name, 84 assigning subnet masks, 27 B backup configuration file, 82, 154 backup configuration file name, 82 C card
Index disable route direct dial links, 123 non-dialed links, 123 shared dial links, 120, 121 disk logging field, 175, 176, 181, 182, 183 domain keyword, 166 domain name configuration additional files, 170 overview, 165 domain name file configuration guidelines, 165 domain name resolver configure, 166, 168 domain name services, 35 draw a network map, 48 drawing a network map, 48 drawing an internetwork map, 44 DSLINE command, 191 DTC node name, 62, 127, 130 DTCCNTRL command, 188 E enable Ethernet, 62, 95 en
Index token ring, 98 IP subnets, 27 K keyword domain, 166 nameserver, 167 search, 167 keywords resolver file, 166 L LAN Configuration screen, 109 LAN configuration worksheet, 67 LAN internet routing table, 51 LAN Link name, 63 LAN network map, 49 LAN network worksheet, 49 leased line, 26 leaving maintenance mode, 156 line speed, 22 link manager logging, 186 link name, 63, 96, 99, 109, 127, 130 gateway half, 144 LAN, 94, 101, 112 token ring, 98 link type gateway half, 144 link types, 25 local domain name, 6
Index Network directory Select Node Name screen, 157 network directory worksheet, 59 network interface LAN, 87, 88 network Interface (NI) name, 65 network interface (NI) name X.
Index public data network, 132 PVC, 132, 134 PVC number, 132 PVC parameters, 133 PXP field network directory, 161 Q QVALNS.NET.SYS, 190 R redirect output, 156 remote IP address, 66, 131, 133 remote node name, 66, 131, 133 remote X.25 address, 66, 132, 133 RESLVCNF.NET.
Index X X.25 Configuration screen, 127 X.25 configuration worksheet, 73 X.25 internet routing table, 56 X.25 Link name, 64 X.25 network network directory, 36 X.25 network map, 54 X.25 network table, 55 X.25 network worksheet, 54 X.
