HP 3000/iX Network Planning and Configuration Guide HP 3000 MPE/iX Computer Systems Edition 4 36922-90037 E1098 Printed in: 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 . . . . . . . . . . . . . . . . . . Line Speed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 4 LAN Network Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN Network Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN Network Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN Internet Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Token Ring Network Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . FDDI Network Worksheets . . . . . . . . . . . . . . . . . . .
Contents 6. Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure a LAN Network Interface . . . . . . . . . . . . . . . . . . . . . . . . 93 To Configure a Token Ring Network Interface. . . . . . . . . . . . . . . . . . . 98 To Configure an FDDI Network Interface . . . . . . . . . . . . . . . . . . . . . 102 To Configure a 100VG-AnyLAN Network Interface . . . . . . . . . . . . . 106 To Configure a 100Base-T Network Interface . . . . . . . . . . . . . . . . . .
Contents Additional Domain Name Configuration Files. . . . . . . . . . . . . . . . . . Network Name Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Protocol Name Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service Name Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 178 178 178 13. Configuring Logging To Access the Logging configuration Screens. . . . . . . . . . . . . . . . . . .
Contents Differences in X.25 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1980 Versus 1984 CCITT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Level 3 Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Level 3 Access with NetIPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security . . . . . . . . . . . . . . .
Contents E. NS X.25 Migration: NS 3000/V PAD Access to NS 3000/iX Release 2.0 or Later Differences Between NS3000/V and NS3000/iX PAD Support . . . . . 238 To Migrate from NS 3000/V PAD Access to NS 3000/iX Release 2.0 or later 239 If You are Using Host-Based Network Management . . . . . . . . . . . 239 If You are Using PC-Based Network Management . . . . . . . . . . . . 239 To Save NS 3000/V PAD Parameters . . . . . . . . . . . . . . . . . . . . . . . 239 PAD Access Migration Categories . . . . . . . . .
Figures Figure 2-1 . Class C Address with Subnet Number (Example 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 Figure 2-2 . Class C Address with Subnet Number (Example 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 Figure 2-3 . Gateway Configuration Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 Figure 3-1 . Internetwork Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures Figure 11-5 . Network Directory Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169 Figure 12-1 . Sample Resolver Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175 Figure 12-2 . Sample Hosts Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177 Figure 13-1 . Logging Configuration Screen Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Network Configuration Overview This manual provides step-by-step instructions you can use to configure an HP 3000 node for network communications. You can use the information to configure an IEEE 802.3/Ethernet, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T, Point-to-Point (router), or X.25 node. Before you begin configuration, you must ensure your network is physically set up and ready for network configuration. This chapter provides information you should know before you begin configuration.
Network Configuration Overview Pre-Configuration Hardware Check Pre-Configuration Hardware Check Hardware Check Before you begin the actual configuration process, check that the hardware components required for NS 3000/iX have been installed and verified according to the procedures in the hardware installation manuals listed in the preface to this guide.
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 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 Another option for nodes located in the same geographic location is to use hardwired (direct-connect) Point-to-Point links. You might wish to use a Point-to-Point network if the distance between some nodes on the network will be greater than the maximum distance allowed between nodes on a LAN. FDDI networks also offer greater distances than LAN, Token Ring, 100VG-AnyLAN, or 100Base-T networks.
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 (Example 2) Now, refer again to example 1. The subnet mask must indicate that three bits of the node portion of the IP address will be used for the subnet identifier. The subnet mask turns on (sets to 1) all the relevant bits for its subnet scheme. The subnet mask for example 1 is shown below. Note that the most significant three bits of the rightmost byte are set. Subnet Mask Binary 11111111.11111111.
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 I
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 You use NMMGR to perform the following network directory functions: • Add, modify, and delete entries in the directory. • Review and inspect directory information. • Merge a remote directory with a directory on the local node. • Automatically update directories on a group of remote nodes by using a background stream job controlled from a central administrative node.
Networking Concepts Address Resolution that you update the network directory in one place, then copy it to the rest of the world. The disadvantage is that network directories for large internets are going to be large. The recommended way to create and maintain your network directory using the centralized method is to assign a single node as the central administrative node. You configure the network directory on this node and then copy it to all other nodes on the network.
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 550 meters of each other? If so, consider connecting them with ThinLAN 3000/iX links. The maximum cable length for segments of ThinLAN 3000/iX cable is 185 meters, with a maximum of three segments connected by repeaters. 2.
Networking Concepts Network Design Questions 7. Do you need access to nodes on public or private X.25 networks? If so, consider using DTC/X.25 iX Network Links. 8. Is a subset of nodes either geographically or organizationally distanced from another subset of nodes? If so, you may wish to establish a network boundary between them in order to make them two separate networks joined by a full gateway or router.
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 Communication Between Networks Since the main purpose of the internetwork map is to show how networks are connected, gateway nodes are the only nodes you should label on the internetwork map. All other nodes and their networks can be represented by drawing sketches of the networks, as shown in Figure 3-1.
Planning Your Network Drawing an Internetwork Map Network Boundaries Once you have drawn your gateway nodes or routers, you have established network boundaries. Consider the example and look at Figure 3-1. Since node B in the example is a full gateway and belongs to both NET1 and NET2, the boundary between these two networks is at node B itself. The boundary between NET2 and NET5 is along the gateway-half link that connects gateway nodes G and H.
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 LAN Network Table Refer to the LAN network map to fill in the LAN network table (Table 3-2). The first column lists the names of all the nodes on NET1. Each node is assigned an IP address that is unique within the network. Only the node portion of the IP address is listed since the IP network address is noted at the top of the table. In the third column of Table 3-2, node B is shown as a proxy server.
Planning Your Network Network Worksheets LAN Internet Routing Table The purpose of the LAN internet routing table (Table 3-3) is to list all possible networks that can be reached from each gateway node on a LAN, such as NET1 in the example. As shown on the internetwork map, NET1 includes a gateway node, node B. In the IP Node Address column of the LAN internet routing table, the node portion of the gateway node’s IP address is listed.
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 Table 3-5 Point-to-Point Internet Routing Table NETWORK NAME: NET2 IP NETWORK ADDRESS C 192.006.250 XXX GATEWAY IP NODE ADDRESS B 001 G 005 54 DESTINATION HOPS TO DESTINATION NET1 C 192.006.001 XXX 1 NET4 C 192.006.002 XXX 2 NET3 C 192.006.251 XXX 2 NET5 C 192.006.252 XXX 3 NET6 C 192.006.003 XXX 2 NET5 C 192.006.252 XXX 1 NET3 C 192.006.251 XXX 2 NET1 C 192.006.001 XXX 3 NET4 C 192.006.002 XXX 4 NET3 C 192.006.
Planning Your Network Network Worksheets X.25 Network Worksheets One set of X.25 network worksheets should be used for each X.25 network in your internetwork. The X.25 worksheets consist of a map of the X.25 network and two tables. One table contains information about each node on the X.25 network. The other table contains network-specific internet routing information. X.25 Network Map Figure 3-4 is a drawing of the network map for NET3.
Planning Your Network Network Worksheets X.25 Network Table Refer to the X.25 network map to fill in the X.25 network table as shown in Table 3-6. We complete the first column by listing the names of all the nodes on NET3. Each node is assigned an IP address that is unique within the network. Only the node portions of the IP addresses are listed since the IP network address is listed at the top of the table. In the third column of the table, node H is indicated as a central administrative node. The X.
Planning Your Network Network Worksheets Table 3-7 X.25 Internet Routing Table NETWORK NAME: NET3 IP NETWORK ADDRESS C 192.006.251 XXX HOPS TO DESTINATION GATEWAY IP NODE ADDRESS DESTINATION B 004 NET1 C 192.006.001 XXX 1 NET4 C 192.006.002 XXX 2 NET2 C 192.006.250 XXX 2 NET5 C 192.006.252 XXX 3 NET5 C 192.006.252 XXX 1 NET2 C 192.006.250 XXX 2 NET1 C 192.006.001 XXX 3 NET4 C 192.006.
Planning Your Network Network Worksheets Figure 3-5 Gateway-Half Map Gateway Half Network Interface Table Table 3-8 is based on the map discussed in the previous section. Both gateway half nodes, the full IP addresses of the partner nodes, the connected networks, and the name of the link are listed. Usually, the link name will be the same from the perspective of each gateway half.
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 Field IP address Screen LAN Configuration; Token Ring Configuration; FDDI Configuration; 100VG-AnyLAN Configuration; 100Base-T Configuration; Point-to-Point Configuration; X.25 Configuration Description There are two methods of entering an internet protocol (IP) address within NMMGR: 1. Enter the fully qualified IP address (for example, Class C, C 192.191.191 009). OR 2.
Planning for Node Configuration Node Worksheet Information Field Screen Link name Description The link name represents a hardware interface card. This name must be unique to both the node and the network. The link name can have up to eight alphanumeric characters and the first character must be alphabetic. (LAN Link name) LAN Configuration This represents the LAN card for which you are configuring a link.
Planning for Node Configuration Node Worksheet Information Field Screen Description Local domain name NS Configuration The name of the system in ARPANET standard format. It is composed of labels, with each label separated by a period. Labels must start with a letter or digit and have as interior characters only letters, digits, hyphens(-), or underbars (_). There may be any number of labels, but the total length of the name, including periods, is limited to 255 characters.
Planning for Node Configuration Node Worksheet Information Field Screen Description Physical path of LANIC LAN Configuration This is the location of the LANIC device adapter card. Run IOMAP utility to determine the physical path for the LAN adapter. Refer to the system documentation for your HP 3000 model for further details regarding physical path. Physical path of device adapter FDDI Configuration This is the location of the FDDI device adapter card.
Planning for Node Configuration Node Worksheet Information Field Screen Description Use Auto-Negotiation 100Base-T Configuration Should the adapter attempt to auto-negotiate with the hub/switch. Use this feature ONLY if the hub/switch supports this feature also. Link Speed 100Base-T Configuration This is the desired speed at which link should operate. Valid values are 10 or 100 MBit/sec. This field is only needed if auto-negotiation is not used.
Planning for Node Configuration Node Worksheet Information Field Screen Security class X.25 Virtual Circuit Configuration For SVCs only. In the network directory, the security to be applied for connection establishment with the remote node. Speed Point-to-Point Configuration The line transmission speed is given in bits per second. For direct connect the value must be supported by the cable. Values are 1200, 2400, 4800, 9600, 19200, 38400, 56000, and 64000. The default is 56000.
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 IP network address This is the IP address of the gateway specified on the Neighbor Gateways 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.
5 Introductory Screens The introductory screens are the first few screens that are displayed when you configure a node using NMMGR. Figure 5-1 shows the screen flow of the introductory screens. [FUNCTION] denotes the function key used at a screen to invoke the next screen on the screen flow. This chapter describes the introductory screens relevant to configuring NS unguided networks.
Introductory Screens To Begin the Configuration Process To Begin the Configuration Process The procedures that follow describe how to modify the NMMGR configuration file for the introductory screens. To Start NMMGR Node manager (NM) or network administrator (NA) capabilities are required to run this program. To run NMMGR: 1. Type NMMGR.PUB.SYS at the system prompt (:). 2. Press [RETURN]. NOTE As of version 4.0 of the operating system, you can modify the link configurations in NMCONFIG.PUB.
Introductory Screens To Begin the Configuration Process Figure 5-2 Open Configuration/Directory File Screen Follow the steps listed here to enter data for this screen. Refer to “Fields” subsection for detailed information about each field on the screen. Step 1. Verify that the correct configuration file name, backup configuration file name, and network directory file name are in the appropriate fields. Step 2. If you have assigned a write access password, enter it in this field.
Introductory Screens To Begin the Configuration Process Backup configuration file name A backup file name must be specified whenever a configuration file is opened or created. The default backup configuration file name is NMCBACK.group.account. The backup file will be automatically updated with the contents of the configuration file each time the configuration file is successfully validated.
Introductory Screens To Begin the Configuration Process To Select NS Configuration To Select NS Configuration. The Main screen (#2) in Figure 5-3 is displayed after you create or open a configuration file by pressing the [Open Config] key from the Open Configuration Directory File screen (#1) in Figure 5-2. Figure 5-3 Main Screen NOTE NS/SNA is no longer offered as a product and has been removed from the Corporate Price List. The product is obsolete with no plans for support. Step 1.
Introductory Screens To Begin the Configuration Process contains 16 or fewer characters (alphanumeric, underscore, or hyphens). The first character of each field must be alphabetic. The nodename portion of each node name must be unique within the node’s network. The nodename.domain portion of each node name must be unique within the internetwork. HP recommends that all nodes on the network be assigned the same domain and organization. Assign meaningful node names. For example, MKTG.BND.HP and LAB.BND.
Introductory Screens To Begin the Configuration Process To Select Guided Configuration The NS Configuration screen (#166) in Figure 5-4 is displayed if you press the [NS] key at the Main screen (#2) in Figure 5-3. Figure 5-4 NS Configuration Screen Step 1. If you are using domain names for network access, replace the node name in the field at the bottom of the screen with this system’s domain name and press the [Save Data] key. If not using domain names, leave the node name as is. Step 2.
Introductory Screens To Begin the Configuration Process Fields Local Domain Name The name of this system in the ARPANET standard format. This name can be used by other nodes on the network to access this host. The domain name is composed of labels, with each label separated by a period. Each label must start with a letter or digit, and have as interior characters only letters, digits, hyphens (-), or underbars (_).
Introductory Screens To Begin the Configuration Process Step 1. Next to the words Enter a network interface:, enter a name for the selected network interface (for example, LANNI). Step 2. Next to the words Enter a network type:, enter the selected network type number indicated on the above screen. (For example, enter a 1 to indicate that the NI is a LAN NI.) Step 3. Press the [Config Network] key. (There may be a short pause before the next screen appears.
Introductory Screens To Begin the Configuration Process Enter 4 for an SNA NI Enter 5 for a Gateway Half NI Enter 6 for a Token Ring NI Enter 7 for an FDDI NI Enter 8 for 100VG-AnyLAN Enter 9 for 100Base-T 90 Chapter 5
6 Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node This chapter provides step-by-step instructions for configuring local area network (LAN), Token Ring, Fiber Distributed Data Interface (FDDI), 100VG-AnyLAN, and 100Base-T links. This manual assumes that you are using the guided configuration capabilities of NMMGR. Figure 6-1 shows the screen flow for configuring LAN, Token Ring, FDDI, 100VG-AnyLAN, and 100Base-T screens.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node Before using NMMGR to configure a link, you should complete the worksheets provided. See Chapter 4, “Planning for Node Configuration,” for more information on planning your configuration and filling out the configuration worksheets. This chapter includes step-by-step instructions to help you perform the following tasks: • Begin the configuration process. • Configure a LAN, Token Ring, FDDI, 100VG-AnyLAN, or 100Base-T network interfaces.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure a LAN Network Interface To Configure a LAN Network Interface The LAN Configuration screen (#41) in Figure 6-2 is displayed when you press the [Config Network] key at the Network Transport Configuration screen (#42) with an NI type of 1 (LAN). Refer to Chapter 5, “Introductory Screens,” for information on the Network Transport Configuration screen. Figure 6-2 LAN Configuration Screen Step 1.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure a LAN Network Interface Step 6. Tab down to the field called Enable Ethernet (Y/N). By default, ethernet is enabled. Change the field to N if you do not want ethernet enabled. Step 7. Tab down to field called Enable IEEE 802.3 (Y/N). By default, IEEE 802.3 is enabled. Change the field to N if you do not want IEEE 802.3 enabled. Step 8. Press the [Save Data] key to save the LAN link configuration.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure a LAN Network Interface HP assigns the network portion (initial nine digits) of IP addresses from ARPA Class C, though your addresses may also be of Classes A or B. The complete formats are: Class A nnn xxx.xxx.xxx B nnn.nnn xxx.xxx C nnn.mmm.mmm xxx Where: nnn = the network portion of the IP address and xxx = the node portion of the IP address. For Class C, the node portion of the IP address must be between 001 and 254.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure a LAN Network Interface configuring subnetworks. The mask identifies which bits of an IP address will be used to define a subnetwork. To determine these bits, you first need to estimate how many subnetworks and nodes per subnetwork you need. See Chapter 2, “Networking Concepts,” for details on deriving an IP subnet mask.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure a LAN Network Interface Disabling IEEE 802.3 has the effect of disabling the probe protocol as well and you will need to handle name to IP address resolution by other means.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure a Token Ring Network Interface To Configure a Token Ring Network Interface The Token Ring Configuration screen (#49) in Figure 6-3 is displayed when you press the [Config Network] key at the Network Transport Configuration screen (#42) with an NI type of 6 (Token Ring). Refer to Chapter 5, “Introductory Screens,” for information on the Network Transport Configuration screen. Figure 6-3 Token Ring Configuration Screen Step 1.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure a Token Ring Network Interface NOTE If the same Token Ring card is being used for both NS and SNA communications, you must use the same value for this field as is configured for the SNA Link. Step 5. Press the [Save Data] key to save the Token Ring link configuration. If you need to identify neighbor gateways, press the [Neighbor Gateways] key and proceed to the section in the chapter called “To Identify Neighbor Gateways.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure a Token Ring Network Interface address of your NS 3000/iX node. Also, you will need to know the node portions of the IP addresses of each of the nodes (usually they will be numbered sequentially, such as 001, 002, and so on), so that you can specify a unique node portion for the IP address of your node. If you have a network map, it should provide a record of such items as the node name and IP address of each node.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure an FDDI Network Interface To Configure an FDDI Network Interface The FDDI Configuration screen (#201) in Figure 6-4 is displayed when you press the [Config Network] key at the Network Transport Configuration screen (#42) with an NI type of 7 (FDDI). Refer to Chapter 5, “Introductory Screens,” for information on the Network Transport Configuration screen. Figure 6-4 FDDI Configuration Screen Step 1.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure an FDDI Network Interface Gateways.” Otherwise, proceed to Chapter 10, “Validating Network Transport and Cross-Validating with SYSGEN,” and press the [Validate Netxport] key. Optional Keys Press the [List NIs] key to list the names and types of already configured network interfaces. Press the [Delete NI] key to remove a configured network interface from the configuration file.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure an FDDI Network Interface B nnn.nnn xxx.xxx C nnn.mmm.mmm xxx Where: nnn = the network portion of the IP address and xxx = the node portion of the IP address. For Class C, the node portion of the IP address must be between 001 and 254. If you are adding your NS 3000/iX node to an existing network, the network portion of each node’s IP address should be the same.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure an FDDI Network Interface Physical Path of FDDI Device Adapter The physical path number corresponds to the slot location of a node’s FDDI device adapter. Recommended slot locations and physical path calculations vary according to the type of HP 3000 system you are running.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure a 100VG-AnyLAN Network Interface To Configure a 100VG-AnyLAN Network Interface The 100VG-AnyLAN Configuration screen (#287) in Figure 6-5 is displayed when you press the [Config Network] key at the Network Transport Configuration screen (#42) with an NI type of 8 (100VG-AnyLAN). Refer to Chapter 5, “Introductory Screens,” for information on the Network Transport Configuration screen.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure a 100VG-AnyLAN Network Interface “To Identify Neighbor Gateways.” Otherwise, proceed to Chapter 10, “Validating Network Transport and Cross-Validating with SYSGEN,” and press the [Validate Netxport] key. Optional Keys Press the [List NIs] key to list the names and types of already configured network interfaces. Press the [Delete NI] key to remove a configured network interface from the configuration file.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure a 100VG-AnyLAN Network Interface B nnn.nnn xxx.xxx C nnn.mmm.mmm xxx Where: nnn = the network portion of the IP address and xxx = the node portion of the IP address. For Class C, the node portion of the IP address must be between 001 and 254. If you are adding your NS 3000/iX node to an existing network, the network portion of each node’s IP address should be the same.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure a 100VG-AnyLAN Network Interface Proxy node Establishing a proxy node is a way of placing node name and address mapping information in a single location. If you are configuring an internetwork or a network with non-HP nodes, it may be easier to update your configurations if you have them located in a central place, that is, the proxy node. On an internetwork, the proxy node is usually a gateway.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure a 100Base-T Network Interface To Configure a 100Base-T Network Interface The 100Base-T Configuration screen (#297) in Figure 6-6 is displayed when you press the [Config Network] key at the Network Transport Configuration screen (#42) with an NI type of 9 (100Base-T). Refer to Chapter 5, “Introductory Screens,” for information on the Network Transport Configuration screen. Figure 6-6 100Base-T Configuration Screen Step 1.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure a 100Base-T Network Interface Step 6. Tab down to the field called Enable Ethernet (Y/N). By default, ethernet is enabled. Change the field to N if you do not want ethernet enabled. Step 7. Tab down to field called Enable IEEE 802.3 (Y/N). By default, IEEE 802.3 is enabled. Change the field to N if you do not want IEEE 802.3 enabled. Step 8. Press the [Save Data] key to save the LAN link configuration.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure a 100Base-T Network Interface HP assigns the network portion (initial nine digits) of IP addresses from ARPA Class C, though your addresses may also be of Classes A or B. The complete formats are: Class A nnn xxx.xxx.xxx B nnn.nnn xxx.xxx C nnn.mmm.mmm xxx Where: nnn = the network portion of the IP address and xxx = the node portion of the IP address.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure a 100Base-T Network Interface configuring subnetworks. The mask identifies which bits of an IP address will be used to define a subnetwork. To determine these bits, you first need to estimate how many subnetworks and nodes per subnetwork you need. See Chapter 2, “Networking Concepts,” for details on deriving an IP subnet mask.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure a 100Base-T Network Interface Disabling IEEE 802.3 has the effect of disabling the probe protocol as well and you will need to handle name to IP address resolution by other means.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure Neighbor Gateways To Configure Neighbor Gateways You need to visit the next two screens only if you are configuring a non-gateway node that is on the same network as a gateway. In this case, the non-gateway node needs to know the identity of any neighbor gateway. Neighbor gateways can be either full or half gateways. Gateways that are on the same network are called neighbor gateways.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure Neighbor Gateways Figure 6-7 Neighbor Gateways Screen Step 1. In the Gateway name field, enter the name of a gateway that is on the same network as the node that you are configuring. (Nodes are on the same network if the network portions of their IP addresses are the same.). Step 2. If you are adding the identified gateway for the first time, press the [Add] key.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure Neighbor Gateways To Identify Neighbor Gateway Reachable Networks The Neighbor Gateway Reachable Networks screen (#158) in Figure 6-8 is displayed when you press the [Add] or [Modify] key for a valid gateway name from the Neighbor Gateways screen (#152) in Figure 6-7. Figure 6-8 Neighbor Gateway Reachable Networks Screen Step 1.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure Neighbor Gateways Step 5. Repeat steps 2, 3, and 4 for each remote reachable network. The information configured in this screen can extend to more than one page, if necessary, to allow configuration of up to 2550 reachable networks per link (255 pages and 10 reachable nets per page). If you need to configure more than 10 networks, press the [Save Data] key then press the [Next Page] key to enter more networks. Step 6.
Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node To Configure Neighbor Gateways 118 Chapter 6
7 Configuring a Point-to-Point Node This chapter provides step-by-step instructions for configuring Point-to-Point links. (Point-to-Point links are sometimes referred to as router links.) This manual assumes that you are using the guided configuration capabilities of NMMGR. Figure 7-1 shows the screen flow for configuring Point-to-Point screens. Screens unique to Point-to-Point configuration are indicated by bold boxed screens.
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 To Configure a Point-to-Point Network Interface To Configure a Point-to-Point Network Interface The Point-to-Point Configuration screen (#44) in Figure 7-2 is displayed when you press the [Config Network] key at the Network Transport Configuration screen (#42) with an NI type of 2 (Point-to-Point). Refer Chapter 5, “Introductory Screens,” for information on the Network Transport Configuration screen. Figure 7-2 Point-to-Point Link Configuration Screen Step 1.
Configuring a Point-to-Point Node To Configure a Point-to-Point Network Interface Step 4. Tab down to the Physical Path field. Enter the physical path number corresponding to the SPU slot number of the programmable serial interface (PSI) card. Step 5. Tab to the Speed field. Enter the line transmission speed of this link. Step 6. Tab to the Type field. Enter DD for direct dial, SD for shared dial or DC for direct connection. Step 7. Press the [Save Data] key to record the data you have entered. Step 8.
Configuring a Point-to-Point Node To Configure a Point-to-Point Network Interface You need not enter the following items as NMMGR will fill these in: • Class A, B, C • Leading zeros for the network and node portion of the IP address. HP assigns the network portion (initial nine digits) of IP addresses from ARPA Class C, though your addresses may also be of Classes A or B. The complete formats are: Class A nnn xxx.xxx.xxx B nnn.nnn xxx.xxx C nnn.mmm.
Configuring a Point-to-Point Node To Configure a Point-to-Point Network Interface IP subnet mask Link name An IP subnet mask is specified in the same format as an IP address. The 32-bit mask is grouped in octets expressed as decimal integers and delimited by either a period (.) or a space. An IP mask is used when configuring subnetworks. The mask identifies which bits of an IP address will be used to define a subnetwork.
Configuring a Point-to-Point Node To Configure Neighbor Gateways To Configure Neighbor Gateways You need to visit the next two screens only if you are configuring a non-gateway node that is on the same network as a gateway. In this case, the non-gateway node needs to know the identity of any neighbor gateway. Neighbor gateways can be either full or half gateways. Gateways that are on the same network are called neighbor gateways.
Configuring a Point-to-Point Node To Configure Neighbor Gateways Figure 7-3 Neighbor Gateway Screen Step 1. In the Gateway name field, enter the name of a gateway that is on the same network as the node that you are configuring. (Nodes are on the same network if the network portions of their IP addresses are the same.). Step 2. If you are adding the identified gateway for the first time, press the [Add] key. If you are modifying the configuration of this node, press the [Modify] key.
Configuring a Point-to-Point Node To Configure Neighbor Gateways To Identify Neighbor Gateway Reachable Networks The Neighbor Gateway Reachable Networks screen (#158) in figure 7-4 is displayed when you press the [Add] key or the [Modify] key for a valid gateway name from the Neighbor Gateways screen (#152) in Figure 7-3. Figure 7-4 Neighbor Gateway Reachable Networks Step 1. In the Neighbor Gateway IP Internet Address field, enter the IP address of the gateway specified on the Neighbor Gateways screen.
Configuring a Point-to-Point Node To Configure Neighbor Gateways reachable networks per link (255 pages and 10 reachable nets per page). If you need to configure more than 10 networks, press the [Save Data] key then press the [Next Page] key to enter more networks. Step 6. After you have finished entering the IP addresses of all the reachable networks, press the [Save Data] key. Press the [Prior Screen] key to return to the Neighbor Gateways screen. Step 7.
Configuring a Point-to-Point Node To Configure Node Mapping To Configure Node Mapping The screens discussed in the following pages allow you to configure shared dial or direct connect and dial node mapping. These screens allow you to specify routes to target (destination) nodes and to indicate the priority of each route. The number of mappings you enter depends on how many links are on the node you are configuring.
Configuring a Point-to-Point Node To Configure Node Mapping To Configure Shared Dial Node Mapping The Shared Dial Node Mapping Configuration screen (#46) in Figure 7-5is displayed if you press the [Link Routing] key at the Point-to-Point Link Configuration screen (#44) for a link of type SD. Figure 7-5 Shared Dial Node Mapping Configuration Screen Each router NI can have up to 1024 mappings. However, 4096 is the absolute maximum number of unique phone numbers supported per NMCONFIG File. Step 1.
Configuring a Point-to-Point Node To Configure Node Mapping Step 7. Press the [Save Data] key to save the data on the screen. Proceed to Chapter 10, “Validating Network Transport and Cross-Validating with SYSGEN,” and press the [Validate Netxport] key. Optional Keys Press the [Next Link] key to call up another link when you want to configure information about its adjacent and non-adjacent nodes. Press the [Config Directry] key to configure the Network Directory screen.
Configuring a Point-to-Point Node To Configure Node Mapping D Three-second delay (used for European modems and automatic call units that require built-in delays). # Defined by local phone system. * Defined by local phone system. To disable outbound dialing, enter an exclamation point (!) by itself in the phone number field. Each router NI can have up to 1024 mappings. However, 4096 is the absolute maximum number of unique phone numbers supported per NMCONFIG File.
Configuring a Point-to-Point Node To Configure Node Mapping Figure 7-6 Direct Connect/Dial Node Mapping Configuration Screen Each router NI can have up to 1024 mappings. However, 4096 is the absolute maximum number of unique phone numbers supported per NMCONFIG File. Step 1. In the Route Name field, enter a symbolic name that represents a route between the node you are configuring and a destination node. Step 2.
Configuring a Point-to-Point Node To Configure Node Mapping Figure 7-7 Using an @ for Mapping Non-Adjacent Nodes Priority Number from 1 to 99 that indicates which route has precedence (priority) over another when there are multiple routes to a destination. A route to a destination that has a higher priority will take precedence over a route with a lower priority. Disable Route Y (yes) or N (no) indicator that allows you to temporarily disable a configured route.
8 Configuring an X.25 Node This chapter provides step-by-step instructions for configuring X.25 iX System Access for systems using PC-based network management. This manual assumes that you are using the guided configuration capabilities of NMMGR. Figure 8-1 shows the screen flow for configuring X.25 screens. Screens unique to X.25 configuration are indicated by bold boxed screens. [FUNCTION] denotes the function key used at a screen to invoke the next screen on the screen flow. Figure 8-1 X.
Configuring an X.25 Node Before using NMMGR to configure a link, you should complete the worksheets provided. See Chapter 4, “Planning for Node Configuration,” for more information on planning your configuration and filling out the configuration worksheets. This chapter includes step-by-step instructions to help you perform the following tasks: • Begin the configuration process. • Configure an X.25 network interface. • Configure neighbor gateways.
Configuring an X.25 Node To Configure an X.25 Network Interface To Configure an X.25 Network Interface The X.25 Configuration screen (#48) in Figure 8-2 is displayed when you press the [Config Network] key at the Network Transport Configuration screen (#42) with an NI type of 3 (X.25). Refer to Chapter 5, “Introductory Screens,” for information on the Network Transport Configuration screen. Figure 8-2 NS Configuration Screen Step 1.
Configuring an X.25 Node To Configure an X.25 Network Interface Step 5. When you are done adding links, press the [Save Data] key. Step 6. If the network that this node is on contains ANY internetwork gateway (either full or half) press the [Neighbor Gateways] key and proceed to the section in this chapter called “To Configure Neighbor Gateways.” Step 7.
Configuring an X.25 Node To Configure an X.25 Network Interface HP assigns the network portion (initial nine digits) of IP addresses from ARPA Class C, though your addresses may also be of Classes A or B. The complete formats are: Class A nnn xxx.xxx.xxx B nnn.nnn xxx.xxx C nnn.mmm.mmm xxx Where: nnn = the network portion of the IP address and xxx = the node portion of the IP address. For Class C, the node portion of the IP address must be between 001 and 254.
Configuring an X.25 Node To Configure an X.25 Network Interface IP subnet mask Link name DTC Node Name An IP subnet mask is specified in the same format as an IP address. The 32-bit mask is grouped in octets expressed as decimal integers and delimited by either a period (.) or a space. An IP mask is used when configuring subnetworks. The mask identifies which bits of an IP address will be used to define a subnetwork.
Configuring an X.25 Node To Configure an X.25 Network Interface Figure 8-3 X.25 Virtual Circuit Configuration Screen Step 1. In the Remote node name field, type in the nodename of each remote X.25 node on your network in the format nodename.domain.organization. Also, if you need to be able to perform a loopback DSLINE command to the local node, then enter the local node’s name here as well. Step 2. For each node, type the IP address of the node in the Remote IP address field. Step 3.
Configuring an X.25 Node To Configure an X.25 Network Interface a. In the Remote X.25 address field, enter the X.25 address of the remote host for X.25 public data networks or private networks. b. Make sure the name of the facility set you are using is in the Facility set field. You may either choose the default facility set (STDSFSET) or enter an alternative. If you are configuring a new facility set, enter a new name.
Configuring an X.25 Node To Configure an X.25 Network Interface must configure an X.25 address key for each remote node with which your node will be communicating. You have a combined maximum of 1024 X.25 address keys in the SVC and PVC path tables. The X.25 address key name must be eight characters or less and the first character must be alphabetic. A default address key called POOL allows any system to access the local system even if the remote system’s address is not configured.
Configuring an X.25 Node To Configure an X.25 Network Interface Security class The security class is the level of logical security you want to have when a connection is made to or from the specified remote node. A Security level is required for SVCs if you have specified an X.25 Address Key. The possible values are as follows: • IO—Both incoming and outgoing calls are accepted. This is the default value. • IN—Only incoming calls are accepted from this particular remote address.
Configuring an X.25 Node To Configure Neighbor Gateways To Configure Neighbor Gateways You need to visit the next two screens only if you are configuring a non-gateway node that is on the same network as a gateway. In this case, the non-gateway node needs to know the identity of any neighbor gateway. Neighbor gateways can be either full or half gateways. Gateways that are on the same network are called neighbor gateways. A non-gateway node on an X.
Configuring an X.25 Node To Configure Neighbor Gateways Figure 8-4 Neighbor Gateways Screen Step 1. In the Gateway name field, enter the name of a gateway that is on the same network as the node that you are configuring. (Nodes are on the same network if the network portions of their IP addresses are the same.). Step 2. If you are adding the identified gateway for the first time, press the [Add] key. If you are modifying the configuration of this node, press the [Modify] key.
Configuring an X.25 Node To Configure Neighbor Gateways Figure 8-5 Neighbor Gateway Reachable Networks Screen Step 1. In the Neighbor Gateway IP Internet Address field, enter the IP address of the gateway specified on the Neighbor Gateways screen. An example is: C 192.007.007 001 Step 2.
Configuring an X.25 Node To Configure Neighbor Gateways Step 7. Back at the Neighbor Gateways screen, after you have finished adding all of the neighboring gateways, press the [Prior Screen] key to return to the X.25 Configuration screen. Follow the instructions for step 7 in the section in this chapter titled “To Configure an X.25 Network.
9 Configuring a Gateway Half This chapter describes how to configure the interface between one gateway half and another gateway half. Gateway halves are one of the methods you can use to interconnect two separate networks. For information on configuring a node that is not a gateway half, use this manual. Figure 9-1 shows the screen flow for configuring gateway half screens. Screens unique to gateway half configuration are indicated by bold boxed screens.
Configuring a Gateway Half Configuring a node as a gateway half requires configuring two separate network interfaces: one for the interface between the two gateway halves, and a second for the gateway half ’s interface to its home network. If this gateway half interfaces to a LAN, Token Ring, FDDI, 100VG-AnyLAN, or 100Base-T network, you should have already configured its network interface according to the instructions in Chapter 6, “Configuring a LAN, Token Ring, FDDI, 100VG-AnyLAN, 100Base-T Node.
Configuring a Gateway Half To Configure a Gatehalf Network Interface To Configure a Gatehalf Network Interface The Gatehalf Configuration screen (#40) in Figure 9-2 is displayed when you press the [Config Network] key at the Network Transport Configuration screen (#42) with an NI type of 5 (Gateway Half). Refer to Chapter 5, “Introductory Screens,” for information on the Network Transport Configuration screen. Figure 9-2 Gatehalf Configuration Screen Step 1.
Configuring a Gateway Half To Configure a Gatehalf Network Interface Step 6. Enter the physical path of this node’s Programmable Serial Interface (PSI) card. Step 7. Tab down to the next field. In the Transmission speed field, either leave the default or enter the transmission speed in bits per second as a number from 1200 to 64000. Step 8. If this is a dial link, enter the phone number of this gateway half ’s partner. Step 9.
Configuring a Gateway Half To Configure a Gatehalf Network Interface Link name Name that represents the hardware link. The link name can have up to eight alphanumeric characters; the first character must be alphabetic. The link name must be unique to both the node and the network. Link type The link type for a gateway half can be either DD for direct dial or DC for direct connect. physical path The physical path of the gateway half ’s PSI card. See Chapter 8, “Configuring an X.
Configuring a Gateway Half To Configure a Gatehalf Network Interface 156 Chapter 9
10 Validating Network Transport and Cross-Validating with SYSGEN This chapter discusses the validation of the network transport configuration and cross-validation of NMCONFIG.PUB.SYS with the system configuration files within SYSGEN. Validating the network transport. This step checks data consistency between values entered on different NMMGR data entry screens. Cross-Validating with SYSGEN. Cross-validation ensures that there are no conflicts in the use of node names, device classes, and physical paths.
Validating Network Transport and Cross-Validating with SYSGEN To Validate the Network Transport To Validate the Network Transport The following procedure assumes that you have already configured and validated the Distributed Terminal Subsystem (DTS). The DTS must be validated before you can validate the network transport (Netxport) software. Upon configuring the selected screens for your network: Step 1. Press the [Validate Netxport] key. Refer to the list of screens with the [Validate Netxport] key.
Validating Network Transport and Cross-Validating with SYSGEN To Cross-Validate in SYSGEN To Cross-Validate in SYSGEN Cross-validation ensures that there are no conflicts in the use of node names, device classes, and physical paths between the data currently contained in NMCONFIG.PUB.SYS and the system configuration data. To cross-validate, use the SYSGEN facility (OP capability is required).
Validating Network Transport and Cross-Validating with SYSGEN To Cross-Validate in SYSGEN 160 Chapter 10
11 Configuring the Network Directory A network directory is used by the node for internetwork routing. Each entry in a network directory consists of a node name associated with an IP address, the network type, and an additional address, if necessary. The network directory uses the internet protocol (IP) address to transfer data between networks. See Chapter 2, “Networking Concepts,” for more information on network directory concepts and for guidelines as to when you need to configure a network directory.
Configuring the Network Directory To Open the Network Directory To Open the Network Directory The Open Configuration/Directory file screen (#1) in Figure 11-2 is the first screen displayed when you run NMMGR. Figure 11-2 Open Configuration/Directory File Step 1. Verify that the correct network directory file name is in the Network directory file name field. Step 2. If you have assigned a write access password, enter it in this field. If you are not using the password feature, leave this field blank.
Configuring the Network Directory To Open the Network Directory configuration file, rename it as NMCONFIG.PUB.SYS and reboot the system. (Keep in mind that any file you use as a configuration file must be successfully validated before you try to use it.) Backup configuration file name A backup file name must be specified whenever a configuration file is opened or created. The default backup configuration file name is NMCBACK.group.account.
Configuring the Network Directory To Select the Update Directory Function To Select the Update Directory Function The Network Directory Main screen (#8) in Figure 11-3 is displayed when you press the [Open Directry] function key at the Open Configuration/Directory File screen (#1) in Figure 11-2. This screen is also displayed if a network directory has already been opened and you type NETDIR in the command window of any screen and press the [Enter] key. Figure 11-3 Network Directory Main Step 1.
Configuring the Network Directory To Select the Update Directory Function the output to another device class or disk file. To set a file equation without leaving NMMGR, enter the appropriate MPE command in the command window and press the [Enter] key. Maint Mode Press this function key to enter the command interface to perform directory merging or to expand the size of your directory. See Using the Node Management Services (NMS) Utilities for details on maintenance mode.
Configuring the Network Directory To Add Nodes to the Network Directory File To Add Nodes to the Network Directory File The Network Directory Select Node Name screen (#9) in Figure 11-4 is displayed when you press the [Update Dir] function key at the Network Directory Main screen (#8) in Figure 11-3. The function of this screen is to display node names that are currently configured in the directory, and to allow you to delete, rename, add, or modify information about a node.
Configuring the Network Directory To Add Nodes to the Network Directory File Fields Node name The name of the node for which you want network directory information. The node name field must contain a fully qualified node name, in the form nodename.domain.organization, when used to add, modify, delete, or rename a node. The node name field when used with the Prev Page and Next Page function keys allows you to browse through a specified part of the network directory.
Configuring the Network Directory To Add Nodes to the Network Directory File depending on your configuration of local entries. When both local and global entries exist for the same node, the network transport uses the local entry. Default value: Y Range: Y or N New name (Required only when renaming an existing node name.) New name to be assigned to the node with the Rename function key. New global The global/local flag setting for the node named in the new name field. The acceptable values are Y or N.
Configuring the Network Directory To Configure Path Report Data for a Node To Configure Path Report Data for a Node The Network Directory Data screen (#10) in Figure 11-5 is displayed when you press the [Add] or the [Modify] function key at the Select Node Name screen (#9) in Figure 11-4. Figure 11-5 Network Directory Data The function of this screen is to configure path report data for the node name listed at the top of the screen. One path report is configured for each NI on a node.
Configuring the Network Directory To Configure Path Report Data for a Node 4 = NS/SNA 5 = ETHERNET (LAN 100VG, 100BT) 6 = Token Ring, 100VG/IEEE 802.5 7 = FDDI Step 4. If appropriate for the type of path you are configuring, enter an address in the Additional Address field. (Type 1 requires no additional address. Types 2, 5, and 6 require a station address. Type 3 requires an X.25 address key. Type 4 requires an LU name.) See additional explanation under “Fields.” Step 5. Press the [Save Data] key. Step 6.
Configuring the Network Directory To Configure Path Report Data for a Node IP address One IP address should be entered for each network interface configured on the remote node that is directly reachable from this node. Each address must match an IP address configured in the remote node’s configuration file. The path of the screen in the configuration file that contains IP addresses is NETXPORT.NI.NIname.PROTOCOL.IP.
Configuring the Network Directory To Configure Path Report Data for a Node Table 11-1 Path Type Configuration N1 Type Framing Protocols Type Point-to-Point (Router) N/A N/A 1 LAN, 100VG-AnyLAN, or 100Base-T 802.3 and Ethernet Either Probe or ARP 1 802.3 and Ethernet Neither Probe nor ARP 5 802.3 only Not Probe 2 Ethernet only Not ARP 5 X.
12 Configuring Domain Name Files If you are planning to use the domain name resolver for name to IP address resolution, you will need to configure a set of ASCII files on each node that contain needed information. To configure these files, you use any standard editor to modify existing sample files according to the instructions in this chapter. See Chapter 2, “Networking Concepts,” for more information on domain names. This chapter details: • How to modify the RSLVSAMP.NET.SYS file and save it as RESLVCNF.
Configuring Domain Name Files To Create or Modify the Resolver File To Create or Modify the Resolver File The resolver file (RESLVCNF.NET.SYS) is an initialization file for the domain name resolver. It contains information needed by the network to determine how to resolve a domain name to an IP address. This file is read by the resolver routines the first time they are invoked by a process. To create the resolver file, perform the following steps: Step 1. Copy the sample file, RSLVSAMP.NET.
Configuring Domain Name Files To Create or Modify the Resolver File Resolver queries will be attempted using each component of the search path in turn until a match is found. Note that this process may be slow and will generate a lot of network traffic if the servers for the listed domains are not local. Note also that queries will time out if no server is available for one of the domains. nameserver NOTE Enter the IP address of a name server the resolver should query.
Configuring Domain Name Files To Create or Modify the Hosts File To Create or Modify the Hosts File The host name data base file, (HOSTS.NET.SYS), associates internet addresses with official host names and aliases. This allows a user to refer to a host by a symbolic name instead of an internet address. When you have configured the name server, this file serves only as a backup when the server is not running. In this circumstance, it is a common practice that HOSTS.NET.
Configuring Domain Name Files To Create or Modify the Hosts File Figure 12-2 Sample Hosts Configuration File # This file contains information regarding the known hosts. # # The for for each entry is: # host IP address local host name host aliases # # Note: the entries cannot be preceded by a blank space. # 172.0.0.1 localhost loopback me myself local 192.41.12.100 basful.loc1.inet.com bashful 192.41.11.114 happy.loc1.inet.com happy 192.41.11.413 queezy.loc1.inet.com queezy 192.41.112.122 sneezy.loc2.
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.
13 Configuring Logging This chapter provides step-by-step instructions for configuring logging. Logging is configured for the purpose of recording events such as errors and console commands. Figure 13-1 shows the screen flow for configuring the logging screens. Screens unique to logging are indicated by bold boxed screens. [FUNCTION] denotes the function key used at a screen to invoke the next screen on the screen flow.
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 To Access the Logging configuration Screens To Access the Logging configuration Screens Use the following steps to reach the logging configuration screens: Step 1. Run NMMGR. The Open Configuration/Directory File screen is displayed. Step 2. Run NMMGR. The Open Configuration/Directory File screen is displayed. Step 3. Press the [NS] function key. The NS Configuration screen is displayed. Step 4. Press either the [Guided Config] or the [Unguided Config] function key. Step 5.
Configuring Logging To Modify the Logging Configuration To Modify the Logging Configuration The Netxport Log Configuration (1) screen (#61) in Figure 13-2 is displayed when you press the [Modify Logging] function key at the Network Transport Configuration screen. Figure 13-2 Netxport Log Configuration (1) Screen Use the fields and the function keys of the screen to configure logging for the subsystems represented on the screen.
Configuring Logging To Modify the Logging Configuration Disk Logging The value entered in this field specifies whether or not logging events for the subsystem and class listed beside the field will be logged to a disk file. A value must be entered for each subsystem and class listed. A Y (yes) enables logging to a file, N (no) disables logging to a file. The file name for the log file is NMLGnnnn.PUB.SYS, where nnnn is a number from 0000 to 9999.
Configuring Logging To Modify the Logging Configuration Enable or disable logging classes (or accept HP-recommended defaults). Press the [Save Data] key on each screen to create or modify the data record. Verify that the data record has been created by checking that the Data flag is Y. Fields Console Logging The value entered in this field specifies whether or not logging events for the subsystem and class listed beside the field will be logged to the system console.
Configuring Logging To Modify the Logging Configuration Figure 13-4 Netxport Log Configuration (3) Screen Use the fields and the function keys of the screen to configure logging for the subsystems represented on the screen. If the subsystem for which you want to enable logging does not appear on this screen, press the [Next Screen] function key to go to the next Netxport Log Configuration screen. There are a total of six logging configuration screens.
Configuring Logging To Modify the Logging Configuration system startup, or when a file is full, NMS creates a new NMLGnnnn.PUB.SYS file, naming each successive logging file by incrementing nnnn. When NMLG9999.PUB.SYS is full, NMS names the next logging file NMLG0000.PUB.SYS. The Netxport Log Configuration (4) screen (#68) in Figure 13-5 is displayed when you press the [Next Screen] function key from the Netxport Log Configuration (3) screen (#70) in Figure 13-4.
Configuring Logging To Modify the Logging Configuration Fields Console Logging The value entered in this field specifies whether or not logging events for the subsystem and class listed beside the field will be logged to the system console. A value must be entered for each subsystem and class listed. A Y (yes) enables logging to the console, N (no) disables logging to the console.
Configuring Logging To Modify the Logging Configuration Use the fields and the function keys of the screen to configure logging for the subsystems represented on the screen. If the subsystem for which you want to enable logging does not appear on this screen, press the [Next Screen] function key to go to the next Netxport Log Configuration screen. There are a total of six logging configuration screens. Enable or disable logging classes (or accept HP-recommended defaults).
Configuring Logging To Modify the Logging Configuration Figure 13-7 Netxport Log Configuration (6) Screen Use the fields and the function keys of the screen to configure logging for the subsystems represented on the screen. If the subsystem for which you want to enable logging does not appear on this screen, press the [Next Screen] function key to go to the next Netxport Log Configuration screen. There are a total of six logging configuration screens.
Configuring Logging To Modify the Logging Configuration system startup, or when a file is full, NMS creates a new NMLGnnnn.PUB.SYS file, naming each successive logging file by incrementing nnnn. When NMLG9999.PUB.SYS is full, NMS names the next logging file NMLG0000.PUB.SYS.
Configuring Logging To Enable Users for Individual Logging Classes To Enable Users for Individual Logging Classes The logging screens described previously in this chapter make it possible to completely configure logging for all subsystems by traversing only six screens. However, using these screens, it is not possible to configure logging so that messages generated by specific logging classes are sent to an individual user’s list device.
Configuring Logging To Enable Users for Individual Logging Classes Step 2. To enable console logging for this subsystem logging class, enter a Y in the Enable console logging? field. To disable console logging, enter an N. Be aware that changing the value in this field will override the previous setting for the logging class you are configuring. Step 3. To enable disk logging for this subsystem logging class, enter a Y in the Enable disk logging? field. To disable console logging, enter an N.
Configuring Logging To Activate Logging To Activate Logging NetIPC logging is automatically activated at system start up. Network Services logging is activated when the Network Services are initiated (that is, when the NSCONTROL START command is issued). Link manager logging and network transport logging are activated when you initiate the network transport (NETCONTROL START).
Configuring Logging To Activate Logging 194 Chapter 13
14 Operating the Network After you have completed the configuration process, you are ready to activate NS. This chapter shows you how to bring up an NS 3000/iX node and how to shut it down. It assumes you have successfully completed the configuration steps described previously. For more detailed information on starting, stopping, and operating an NS network, see the NS 3000/iX Operations and Maintenance Reference Manual.
Operating the Network To Start Links and Services To Start Links and Services To Start Software Loopback Issue the following command (NM capability required) to start software loopback: NETCONTROL START;NET=loopbackNIname This starts up the control process, the transport, and software loopback. Note: when you use guided NMMGR to create any NI, a loopback network interface (whose loopbackNIname is LOOP) is automatically generated.
Operating the Network To Start Links and Services To Start the Network Services Issue the following command (NM capability required) to start the network services: NSCONTROL START This starts the NS 3000/iX Network Services, such as Virtual Terminal, Network File Transfer, Remote File Access, and Remote Data Base Access. You may want to create a startup UDC or command file to activate software loopback, the link(s), and the network services.
Operating the Network To Test the Network Services To Test the Network Services In order to test that you have successfully configured and brought up your NS node, HP provides an NS validation test called QVALNS.NET.SYS. QVALNS is a program which modifies a file called TQVALNS and streams it as a temporary job (JQVALNS). The job purges and creates various files, and then runs a program called NSTEST. NSTEST tests the network services (VT, RFA, RDBA, and NFT).
Operating the Network To Shut Down the Network Services To Shut Down the Network Services To shut down NS, issue the following commands (NM capability required): DSLINE @;CLOSE NSCONTROL STOP NETCONTROL STOP The DSLINE command shown above closes connections for your session only. NSCONTROL STOP allows existing users to continue using the services until they finish their current task but prevents new uses of the services by these users or by new users.
Operating the Network To Shut Down the Network Services 200 Chapter 14
A MPE/V to MPE/iX Migration This appendix provides a quick overview of the planning and tasks you will need to do to migrate an NS 3000 network from an MPE/V system to an MPE/iX system. This appendix assumes that you are migrating your network as a whole; that is, replacing all MPE V systems with MPE/iX systems and maintaining the same basic network function. The following topics are covered by this appendix: • Differences between NS 3000/V and NS 3000/iX networks. • An overview of migration tasks.
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 Differences in Applications Support There are also differences in the implementations of NS 3000/V and NS 3000/iX that will affect certain applications that users may currently be running on your MPE V network. These differences are as follows: • NS 3000/iX supports PTOP for HPDESK only. On NS 3000/iX PTOP is not supported for applications other than HPDESK.
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 you Need to Convert Files If you have not successfully converted your files you will be notified that conversion is necessary when you try either to run NMMGR or to perform a NETCONTROL command.
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 rename it as the new NMCONFIG.PUB.SYS. Choose the NSCONF file that corresponds to the network configuration you want to use as your NS 3000/iX configuration. This new NMCONFIG.PUB.SYS file contains your NS configuration in a format acceptable to MPE/iX. You can now run NMMGR to configure the DTS subsystem, and to perform any needed modifications to the NS configuration. See “Reconfiguration Guidelines” later in this appendix.
MPE/V to MPE/iX Migration Reconfiguration Guidelines Reconfiguration Guidelines Once your MPE/V NS configuration files have been converted for use with the MPE/iX version of NS you will need to reconfigure your network to account for the implementation differences between NS 3000/V and NS 3000/iX. Run the NMMGR utility against the configuration file generated by the file conversion process and perform the following reconfiguration tasks: • Configure the physical path of all links for your network.
B NS X.25 Migration: NS 3000/XL Releases 1.0, 1.1, or 1.2 to NS 3000/iX Release 2.0 or Later This Appendix tells how to use the NMMGRVER utility to migrate (update) a node’s configuration file from NS 3000/XL releases 1.0, 1.1, or 1.2 to NS 3000/iX release 2.0 or later. This Appendix does not apply if any MPE V based node is being used as an X.25 server for NS 3000/XL based machines. Refer to the following appendixes depending on which X.
NS X.25 Migration: NS 3000/XL Releases 1.0, 1.1, or 1.2 to NS 3000/iX Release 2.0 or Later To Convert NS 3000/XL 1.X to 2.0 Files To Convert NS 3000/XL 1.X to 2.0 Files The following procedure describes the steps necessary for conversion. Step 1. At the MPE/iX prompt, type: Run NMMGRVER.PUB.SYS Step 2. At the prompt, enter the filenames to convert: Fileset to be scanned? For example, enter NMCONFIG.PUB.SYS, then press [RETURN].
C NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later This Appendix tells how to use the NMMGRVER utility to migrate (update) configuration files from a node running NS X.25 3000/V Link to a node that will be running NS 3000/iX release 2.0 or later. This appendix does not apply if an MPE V based node is being used as an X.25 server for NS 3000/XL based machines. Refer to the following appendixes depending on which X.
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later Differences Between NS 3000/V and NS 3000/iX Differences Between NS 3000/V and NS 3000/iX Differences Between NS 3000/V and NS 3000/iX The following paragraphs summarize differences between NS 3000/V and NS 3000/iX. Make sure that you account for these differences that could affect your network when migrating to NS 3000/iX. For information on operating system migration, refer to the MPE/iX Migration series.
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later Differences Between NS 3000/V and NS 3000/iX Windows Workstation (using the OpenView DTC Manager software). For more information on configuration using your OpenView Windows Workstation, read Using the OpenView DTC Manager. PAD devices on NS 3000/V are configured (using NMMGR) as part of the X.25 network configuration.
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later Differences in X.25 Support Differences in X.25 Support There are differences in X.25 support between NS 3000/V and NS 3000/iX which need to be considered when you migrate as described in the following paragraphs. 1980 Versus 1984 CCITT NS 3000/V supports CCITT 1980 and NS 3000/iX supports both 1980 and 1984. General Level 3 Differences In MPE V X.25, a Reset is sent to initialize or clear a Permanent Virtual Circuit. In MPE/iX X.
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later Differences in X.25 Support Facilities Following are the supported facilities of the DTC/X.25 XL Network Link. Supported Facilities 1984 CCITT X.25 Reference Extended packet sequence number 6.2 Incoming calls barred 6.5 Outgoing calls barred 6.6 Nonstandard default packet size 6.9 Nonstandard default window size 6.10 Flow control parameter negotiation 6.12 Throughput class negotiation 6.
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later Differences in X.25 Support Pad Support For complete information on migrating PAD support from NS 3000/V to NS 3000/iX Release 2.0 or later, refer to Appendix E, “NS X.25 Migration: NS 3000/V PAD Access to NS 3000/iX Release 2.0 or Later.
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later To Convert NS 3000/V Files to NS 3000/iX Release 2.0 or Later To Convert NS 3000/V Files to NS 3000/iX Release 2.0 or Later This conversion procedure can be used with NS 3000/V NMCONFIG and NSCONF files for version V-delta 3 or later. The procedures that follow are for updating (migrating) configuration files from a node running NS X.25 3000/V Link to a node that will be running NS 3000/iX release 2.0 or later.
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later To Save NS 3000/V X.25 Parameters To Save NS 3000/V X.25 Parameters Make a list of the following NS 3000/V parameters that must be re-entered on the DTC. • VC Assignment from the NS 3000/V screen with the path: @NETXPORT.NI.niname.PROTOCOL.X25.VCSPEC • X.25 Network type and Flow Control parms from the NS 3000/V screen with the path: @NETXPORT.NI.niname.PROTOCOL.X25.VCSPEC. FLOWCNTL • L.U.G.
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later To Copy NS 3000/V Configuration Files to NS 3000/iX System To Copy NS 3000/V Configuration Files to NS 3000/iX System Restore the NS 3000/V configuration files to the NS 3000/iX system. Name the NS 3000/V files with the same names they had on the NS 3000/V node, that is, NMCONFIG.PUB.SYS, and if present, NSCONF.PUB.SYS. Remember: This procedure assumes that there is no configuration file on the NS 3000/iX node yet.
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later To Use NMMGRVER To Use NMMGRVER To use the NMMGRVER utility to convert your NS 3000/V configuration file to NS 3000/iX release 2.0 or later, proceed as follows: Step 1. At the MPE/iX prompt, type: NMMGRVER.PUB.SYS Step 2. Do either steps a through c or steps d through g. If your NS 3000/V node had only an NMCONFIG file (but no NSCONF files), follow the instructions in steps a through c. a.
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later To Use NMMGRVER 4. On the screen with the path @LINK, add the LINK name and Type (X25) of the X25 link. Note: to migrate to NS 3000/iX release 2.2 or later, repeat this step and steps 5 through 7 for each DTC/X.25 Network Access card. 5. On the screen with the path @LINK.linkname, where the LINK name is the one added in the previous step, add the DTC Node name and card number for the DTC/X.25 Network Access card. 6.
NS X.25 Migration: NS 3000/V to NS 3000/iX Release 2.0 or Later To Configure the DTC To Configure the DTC If you are using PC-based network management, configure the DTC by using the OpenView DTC Manager at your OpenView Windows Workstation. For full details, see Using the OpenView DTC Manager. If you are using host-based network management, configure the DTC using NMMGR. For full details, see Configuring and Managing Host-Based X.25 Links.
D NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later This Appendix tells how to use the NMMGRVER utility to migrate a configuration file from any MPE V based node acting as an X.25 server for NS 3000/XL based machines (including the NS X.25 3000/XL Server product) to an NS 3000/iX node that will be running NS 3000/iX release 2.0 or later. This appendix assumes that you want to move the X.25 configuration from the MPE V-based X.
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later Differences Between NS 3000/V and NS 3000/iX Differences Between NS 3000/V and NS 3000/iX The following paragraphs summarize differences between NS 3000/V and NS 3000/iX. Make sure that you account for these differences that could affect your network when migrating to NS 3000/iX. For system migration issues, refer to the MPE/iX Migration series for more information.
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later Differences Between NS 3000/V and NS 3000/iX Workstation (using the OpenView DTC Manager software). For more information on configuration using your OpenView Windows Workstation, read Using the OpenView DTC Manager. PAD devices on NS 3000/V are configured (using NMMGR) as part of the X.25 network configuration.
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later Differences in X.25 Support Differences in X.25 Support There are differences in X.25 support between NS 3000/V and NS 3000/iX which need to be considered when you migrate as described in the following paragraphs. 1980 vs. 1984 CCITT NS 3000/V supports CCITT 1980 and NS 3000/XL supports both 1980 and 1984. General Level 3 Differences In MPE V X.25, a Reset is sent to initialize or clear a Permanent Virtual Circuit.
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later Differences in X.25 Support Facilities Following are the supported facilities of the DTC/X.25 XL Network Link. Supported Facilities 1984 CCITT X.25 Reference Extended packet sequence number 6.2 Incoming calls barred 6.5 Outgoing calls barred 6.6 Nonstandard default packet size 6.9 Nonstandard default window size 6.10 Flow control parameter negotiation 6.12 Throughput class negotiation 6.
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later Differences in X.25 Support PAD Support For complete information on migrating PAD support from NS 3000/V to NS 3000/iX Release 2.0, refer to Appendix E, “NS X.25 Migration: NS 3000/V PAD Access to NS 3000/iX Release 2.0 or Later.
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later To Convert MPE V-Based Server Files to NS 3000/iX Release 2.0 or later To Convert MPE V-Based Server Files to NS 3000/iX Release 2.0 or later The conversion procedure that follows is for moving an X.25 configuration from an MPE V-based X.25 server (including the NS X.25 3000/XL Server product) to an existing NS 3000/XL node and then upgrading it to NS 3000/iX 2.0. Only the X.
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later To Delete Secondary NIs (NS/XL Release 2.2 or later) To Delete Secondary NIs (NS/XL Release 2.2 or later) If you are migrating from NS X.25 3000/V (release V delta 7 or later) to NS 3000/iX release 2.2 or later, make a backup copy of your NS 3000/V NSCONF file. To migrate to NS 3000/iX release 2.2 or later, you must delete the secondary NIs in the NS 3000/V NSCONF file before you use NMMGRVER to convert it.
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later To Save NS 3000/V X.25 Parameters To Save NS 3000/V X.25 Parameters Make a list of the following NS 3000/V parameters that must be re-entered on the DTC. • VC Assignment from the NS 3000/V screen with the path: @NETXPORT.NI.niname.PROTOCOL.X25.VCSPEC • X.25 Network type and Flow Control parms from the NS 3000/V screen with the path: @NETXPORT.NI.niname.PROTOCOL.X25.VCSPEC. FLOWCNTL • L.U.G.
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later To Copy NS 3000/V Configuration Files to NS 3000/iX System To Copy NS 3000/V Configuration Files to NS 3000/iX System Restore the NS 3000/V NSCONF configuration file to the NS 3000/iX system. Name the NS 3000/V file with the same name it had on the NS 3000/V node, that is, NSCONF.PUB.SYS. Remember: This procedure assumes that there already is an NS 3000/XL 1.X NMCONFIG.PUB.SYS configuration file on the NS 3000/iX node.
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later To Use NMMGRVER To Use NMMGRVER To use the NMMGRVER utility to merge your NS 3000/V configuration file with the NS 3000/iX NMCONFIG file and convert it for use with release 2.0 or later, proceed as follows: Step 1. At the MPE/iX prompt, type: NMMGRVER.PUB.SYS Step 2. Merge your NS X.25 3000/XL Server NSCONF file with the existing NS 3000/XL NMCONFIG file, and convert it for use with NS 3000/iX release 2.
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later To Use NMMGRVER 7. On the screen with the path @NETXPORT.NI.niname.LINK.linkname, answer yes or no; then, press the Update key. To Save X.25 XL System Access Parameters on the Host Make a list of the following X.25 XL System Access Parameters on the host that must be re-entered on the DTC. • Local Node Name. • Link Name (the X25 link, not the DTSLINK). • DTC Node Name. • DTC Card Number. • X.25 User Facility Set Parameters.
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later To Configure the DTC To Configure the DTC If you are using PC-based network management, configure the DTC by using the OpenView DTC Manager at your OpenView Windows Workstation. For full details, see Using the OpenView DTC Manager. If you are using host-based network management, configure the DTC using NMMGR. For full details, see Configuring and Managing Host-Based X.25 Links.
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.
Glossary A access port A special interface card in the system cabinet through which the system console is connected. address A numerical identifier defined and used by a particular protocol and associated software to distinguish one node from another. address key See X.25 address key. address resolution In NS networks, the mapping of node names to IP addresses and the mapping of IP addresses to subnet addresses. address resolution protocol ARP.
Glossary backup configuration file A file that contains a copy of the information contained in the configuration file. The backup file, called NMCBACK.group.account by default, is updated each time the configuration file is successfully validated. banner A welcome message displayed on your screen. On the local OpenView workstation a banner appears when a remote connection is established with the OpenView DTC Manager. A banner also can appear when you log on to MPE.
Glossary the sending node. The address of the sending node is the calling address. carrier A continuous wave that is modulated by an information bearing signal. catenet See internetwork. CCITT Consultative Committee for International Telephony and Telegraphy. An international organization of communication carriers, especially government telephone monopolies, responsible for developing telecommunication standards by making recommendations.
Glossary NMMGR and, if PC-based X.25 connections are required, through the OpenView DTC Manager. configuration file The configuration file, which you create and update using the NMMGR utility, contains: 1) the information that the network needs in order to operate. 2) Information necessary for link-level and NetIPC logging. 3) Information required to connect terminals and printers to the system through one or more DTC. occurs when you enter SYSGEN to assure that information contained in NMCONFIG.PUB.
Glossary delivery acknowledgment of the packet is required from the local DCE or from the remote DTE. It therefore allows the choice between local and end-to-end acknowledgment. DCE Data circuit-terminating equipment. The interfacing equipment required in order to interface to data terminal equipment (DTE) and its transmission circuit. Synonyms: data communications equipment, dataset. DDX The national public PSN of Japan.
Glossary device name See PAD name. Dial ID protocol A proprietary Hewlett-Packard protocol that provides security checking and address exchange for dial links. dial link A connection made through public telephone lines. direct-connect device Asynchronous device that is connected directly to a DTC through an RS-232-C or RS-422 cable, with no intervening communications equipment. Also referred to as a “local connection.” direct connection A leased line, private line, or other non-switched link in a network.
Glossary DTC switching A facility enabling terminal users to select any host system that they want to connect to. DTC switching is available only when the OpenView DTC Manager is used for network management. DTC/X.25 Network Access he X.25 software that resides on the Datacommunications and Terminal Controller (DTC). To configure access to an X.25 network, you must configure two software components: the X.25 iX System Access (residing on the HP 3000 host), and the DTC/X.25 Network Access. DTC/X.
Glossary to the DTC switching user interface. The default is [CTRL]-K. This character is used only on networks managed by the OpenView Windows Workstation. facility set A facility set defines the various X.25 connection parameters and X.25 facilities that can be negotiated for each virtual circuit on a per-call basis.
Glossary file specification The name and location of a file. The full specification for a file includes the file name, group, and account. store and forward to transfer packets between each network that it belongs to. G file system The part of the operating system that handles access to input/output devices (including those connected through the DTC), data blocking, buffering, data transfers, and deblocking. gateway A node that connects two dissimilar network architectures.
Glossary H handshaking A communications protocol between devices or between a device and the CPU. Provides a method of determining that each end of a communications link is ready to transmit or receive data and that transmission has occurred without error. hop count See internet hop count and intranet hop count host-based network management Method of managing asynchronous communications for HP 3000 Series 900 computers.
Glossary IEEE 802.3 A standard for a broadcast local area network published by the Institute for Electrical and Electronics Engineers (IEEE). This standard is used for both the ThinLAN and ThickLAN implementations of the LAN. IEEE 802.3 multicast address A hexadecimal number that identifies a set of nodes. This address is used for multicast delivery. IEEE 802.3 nodal address A unique hexadecimal number that identifies a node on an IEEE 802.3 LAN. IEEE 902.
Glossary operating system resources and functions. Intrinsics perform common tasks such as file access and device control. IP See internet protocol. IP address Internet protocol address. An address used by the Internet Protocol to perform internet routing. A complete IP address comprises a network portion and a node portion. The network portion of the IP address identifies a network, and the node portion identifies a node within the network. IP subnet mask See subnet mask.
Glossary line speed Speed at which data is transferred over a specific physical link (usually measured in bits or kilobits per second). link name The name that represents a hardware interface card. The link name can contain as many as eight characters. All characters except the first can be alphanumeric; the first character must be alphabetic.
Glossary LUG See local user group. M map, network A drawing that shows the topology of the network. For networks managed by the OpenView DTC Manager, a network map must be created through use of the OVDraw capability provided with the management software. A network map is also a hardcopy drawing used when planning a network. It shows network topology, node and network names, addresses, network boundaries (for an internetwork map), and link types.
Glossary N nailed device A device with a permanently associated ldev that was assigned through the NMMGR configuration of the host system on which the association is established. Nailed devices can be accessed programmatically through their ldev number. In contrast, non-nailed devices have ldev numbers that are assigned from a pool of available ldev numbers for the life of their connection to a system. native mode The run-time environment of MPE/iX.
Glossary shows network topology, node and network names, addresses, network boundaries (for an internetwork map), and link types. contained in the configuration file (NMCONFIG.PUB.SYS). The backup file is updated each time the configuration file is successfully validated. Network Services NS. Software application products that can be used to access data, initiate processes, and exchange information among nodes in the network. The NS 3000/iX Network Services include RPM, VT, RFA, RDBA, and NFT. NMCONFIG.
Glossary created with NMMGR from an earlier version to the latest format. NMSAMP1.PUB.SYS Sample configuration file supplied with FOS that can be used as a template for DTS configuration. node A computer that is part of a network. The DTC is also considered to be a node and has its own address. node address The node portion of an IP address, which consists of a node portion and a network portion. node management services configuration manager See NMMGR.
Glossary information among nodes in a network. The services are RPM, VT, RFA, RDBA, and NFT. NS Point-to-Point 3000/iX Link Hardware and software necessary to create networks in which data is transmitted from node to node over a defined route until it reaches its destination. This technique is referred to as store and forward. Systems in a point-to-point network are connected by means of leased or dial-up telephone lines.
Glossary P packet A block of data whose maximum length is fixed. The unit of information exchanged by X.25 at level 3. There are DATA packets and various control packets. A packet type is identified by the encoding of its header. packet exchange protocol PXP. A transport layer protocol used in NS 3000/iX links to initially establish communication between nodes when NetIPC socket registry is used. packet-switched network name The name of a data communication network adhering to the CCITT X.
Glossary printer name Character string of up to 16 characters specified in the DTC Manager configuration (for networks using OpenView Network Management) to define a printer by name. Can be shared by several printers (port pool). probe proxy server A node on an IEEE 802.3 network that possesses a network directory. A probe proxy server can provide a node with information about other nodes on the same or other networks of an internetwork.
Glossary They define what functions are to be performed and how messages are to be exchanged. PSI See Programmable Serial Interface. PSN Packet-switching network. Any data communication network using packet-switching techniques wherein data is disassembled into packets at a source interface and reassembled into a data stream at a destination interface. A public PSN offers the service to any paying customer. PSS Packet-Switching System. The national public PSN of the United Kingdom.
Glossary router network See point-to-point. routing The path that packets, or fragments of a message, take through a network to reach a destination node. RPM Remote process management. A network service that allows a process to programmatically initiate and terminate other processes throughout a network from any node on the network. RS-232-C Electronic Industries Association (EIA) level 1 protocol specification that defines electrical circuit functions for 25 connector pins.
Glossary slaved device A device that shares the same DTC port as another device and is connected to the other device, referred to as its master, by a cable. The actions of the slaved device are controlled by the master device. spooled device A printer that is accessed through the spooling facility. The spooling facility allows a nonsharable device to be shared among several users by temporarily storing output data on disc and managing the selection of output spool files destined for the spooled device.
Glossary system configuration The way you tell the operating system what peripheral I/O devices are attached and what parameters are required for system operation. T TCP See transmission control protocol. telenet A proprietary public data network in the USA. termDSM Terminal online diagnostic support manager. A utility that provides diagnostic services for DTC connections by means of a series of commands accessible through the SYSDIAG utility. TermDSM is used only when DTCs are managed by a host system.
Glossary timer (T3) Length of time that a link can remain in an idle state. After the expiration of the timer, the link is considered to be in a non-active, non-operational state and is automatically reset. The value should be chosen carefully. In particular, it must be sufficiently greater than the retransmission timer (T1) so that no doubt exists about the link’s state. token ring collection of data communication systems sharing a common cable and communicating by means of the IEEE 802.5 protocol.
Glossary destination address. When this number (K) frame is reached, the same K frames are retransmitted. V-Series (V.##) CCITT A set of CCITT recommendations related to data communication over a voice-grade telephone network. unedited mode See transparent mode. VT See virtual terminal. V W V.24 The CCITT recommendation that defines the function of the interchange circuits between a DTE and a DCE.
Glossary address and its associated X.25 parameters. You have a combined maximum of 1024 X.25 address keys in the SVC and PVC path tables. to the sender if it is unable to continue to receive data. The sender suspends transmission until it receives an XON character (ASCII DC1). X.25 LUG address X.25 address of a node belonging to a local user group (LUG). X.Series (X.
Glossary 270 Glossary
Index A activating logging, 193 activating NS, 195 add directory entry, 166 add nodes to the network directory, 166 adding a node to the directory, 166 additional address field, 172 additional domain name configuration files, 178 address key, 62, 143, 145 address resolution, 35 domain name services, 35 network directory, 35 address resolution protocol, 38 administrative node, 37 ARP, 38 assigning node name, 86 assigning subnet masks, 27 B backup configuration file, 84, 163 backup configuration file name, 8
Index gateway name, 77, 116, 117, 128, 129, 148 gateway-half configuration, 33 gateways, 31 geographical location, 22 global field, 167 global network directory entries, 167 global/local flag, 167 Global?, 167 H home NI name, 154 hops, 79, 117, 129, 149, 150 host name data base file, 176 HOSTS.NET.
Index Network directory Select Node Name screen, 166 network directory worksheet, 59 network interface LAN, 89 Network Interface (NI) name, 65 network interface (NI) name X.
Index shared dial link, 23 limitations, 23 shut down Network Services, 199 shutting down NS, 199 Speed, 68 speed line, 22 point-to-point, 126 starting a host-based X.
