Modify the Network Management Configuration File

	MPE documents
	Complete PDF
	Table of Contents
	Glossary
	Index
⇓ Page Bottom

⇑ Page Top

Step 1: Begin the Configuration Process

1. Type NMMGR.PUB.SYS at the MPE/iX prompt (:).
2. Press [Return].

   NOTE: You cannot modify the X.25 iX transport and link configurations in NMCONFIG.PUB.SYS if the Network Services are active. Verify that the Network Services are not running by issuing the NETCONTROL STATUS command. You must have NM (Node Manager) capability to issue this command. If NS is down, you will see the following two messages in response to the NETCONTROL STATUS command: TRANSPORT NOT ACTIVE. (NETXPORTWARN 0001) ENCOUNTERED ONE OR MORE WARNINGS WHILE PROCESSING COMMAND. (CIWARN 4437)

Step 2: Open the Configuration File

1. Verify that the correct configuration file name, backup configuration file name, and network directory file name are in the appropriate fields
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.
3. Press the [Open Config] key.

   Fields

Configuration file name

The only configuration file name the system recognizes for use by the network subsystem is NMCONFIG.PUB.SYS. You can, however, create or modify a configuration file using a different name and save it as an offline configuration file. You can use offline configuration files as a means of creating and storing configurations that you want to use in the future or that you are preparing for use on a different system. When you are ready to use an offline configuration file, rename it as NMCONFIG.PUB.SYS, validate within NMMGR (SYSGEN cross-validation is done automatically within NMMGR). Use DTCCNTRL to shutdown and restart DTS or reboot the system.

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.PUB.SYS. The backup file will be automatically updated with the contents of the configuration file each time the configuration file is successfully validated.

Network directory file name

The network directory file must be configured for each new node (unless you will only be accessing the node using direct level 3 access). The network directory contains information that one X.25 node needs in order to communicate with other X.25 nodes. The only network directory file name supported by HP is NSDIR.NET.SYS. This file is part of a KSAM pair. A key file is created at the same time as this data file. The key file will automatically be named using the first six letters of the network directory file name, appended with the character K. For example, NSDIRK.NET.SYS is the name of the key file associated with the data file NSDIR.NET.SYS.

Write access password

The password is an optional feature. If a password has been assigned, you must enter it in the password field to update the configuration file. It is still possible to open the file without using an assigned password, but the file will be in read only mode and NMMGR will not accept any changes.

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

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

Step 3: Select NS Configuration

1. You should already have configured a local node name and entered the other information required for this screen. Verify that the information is correct
2. Press the [NS] key to select the NS configuration branch.

   Fields

Local HP 3000 node name

The local HP 3000 node name is the name by which the HP 3000 Series 900 computer is known in the network. The format of a node name is nodename.domain.organization where the total number of characters is 50 or fewer, and each field contains 16 or fewer characters (alphanumeric, underscore, or hyphens). The first character of each field must be alphabetic.

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.ITG.HP and LAB.ITG.HP are meaningful names for two nodes on the same Local Area Network (LAN) within Hewlett Packard. One node (MKTG.ITG.HP) is used by the marketing department. The other node (LAB.ITG.HP) is used by the lab. The domain field is the same because the nodes belong to the same network. The organization field is the same because the nodes belong to the same internetwork.

Are you using OpenView DTC Manager?

If you answer yes (Y) to this question, NMMGR assumes you are using a PC to manage your system and takes you to the corresponding set of screens. If you answer no (N), NMMGR assumes you are using host-based network management and takes you to the set of screens required for host configuration. If you are using this manual, you should have entered an N in response to this question when you configured your DTCs.

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

If you answer yes (Y) to this question, NMMGR assumes you are configuring X.25 connections and takes you to the set of screens required to configure DTC X.25 Network Access Cards when you configure DTS. If you answer no (N), NMMGR assumes you have no need to configure X.25 connections and takes you to a different set of screens. If you are using this manual, you should have entered a Y in response to this question when you configured your DTCs.

Step 4: Select Guided Configuration

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 local HP 3000 node name in this field.
2. Press the [Guided Config] key to proceed with guided configuration of X.25 iX System Access.

Fields

Local domain name

The name of this system in the ARPANET standard format. This name can be used by other nodes on the network to access this host.

The domain name is composed of labels, with each label separated by a period. Each label must start with a letter or digit, and have as interior characters only letters, digits, hyphens (-), or underbars (_). A domain name may have any number of labels, but its total length, including periods, is limited to 255 characters.

label[.label][...]

Domain names are not case sensitive.

Use of domain names is optional. If you are not using domain names for network access, leave the local HP 3000 node name in this field.

Step 5: Perform Guided Network Transport Configuration

1. Next to the words Enter a network interface:, enter a name for the network interface (for example, X25NI).
2. Next to the words Enter a network type:, enter a 3 to indicate that the NI is an X.25 NI.
3. Press the [Config Network] key. (There may be a short pause before the next screen appears.)

Fields

Enter a network interface

The network interface name (NI name) is used to easily identify one of the types of network interfaces: X.25, LAN, point-to-point (router), gateway half, SNA, or token ring. The name can be up to eight alphanumeric characters, starting with a letter. The maximum number of NIs that can be configured on a node is 12. One of the 12 allowable NIs is reserved for loopback. (Loopback is configured for you automatically.)

If a node interfaces to more than one network, give each NI on that node a unique name. Although all nodes on the same network do not have to have the same NI name, it will be easier to remember if you make the NI name the same for all nodes on the same network (for instance, X25net1). You will use the NI name with the NETCONTROL command to start the transport and network link.

NOTE: You can have more than one X.25 NIs configured for the same X.25 card on one MPE/iX system, but only one can be running at any one time.

Enter a network type

Number that indicates the type of network interface you are configuring. You must enter a network type if you are configuring a new network interface. Network type 3 is the only type used when configuring host-based X.25 links.

NOTE: The only link protocol that can be used as a gateway half is that of the NS Point-to-Point 3000/iX link. X.25 iX System Access cannot be configured as a gateway half. Yet, these two types of software can coexist on the same node. To configure an internetwork gateway half, refer to the HP3000/iX Network Planning and Configuration Guide.

Step 6: Configure X.25 Network

1. In the IP address field, enter the internet protocol (IP) address for the node being configured. An example of an address is: C 192.191.191 009
2. The IP subnet mask is optional. If entering one, tab to the IP subnet mask field and enter the number in the same format as an IP address. The 32-bit mask is grouped in octets expressed as decimal integers and delimited by either a period (.) or a space. The mask identifies which bits of an IP address will be used to define a subnetwork. To determine these bits, you first need to estimate how many subnetworks and nodes per subnetwork you need. For details on deriving an IP subnet mask, refer to the HP 3000/iX Network Planning and Configuration Guide.
3. Move to the first Link Name field. Enter a link name to represent the DTC/X.25 Network Access card for which you are configuring a link. This name must be unique to both the node and the DTC. The link name must be the same as the link name configured for this card on the DTC X.25 Card Configuration — Sys-to-Sys LUGs screen during the DTC configuration see Chapter 3 "Configuring DTCs Step-by-Step"
4. Enter the node name of the DTC that houses the DTC/X.25 Access card in the first DTC Node Name field the enter the slot number of the card in the Card Number field. Enter a link name, DTC node name, and card number for each link you are configuring.
5. When you are done adding links, press the [Save Data] key.
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 "Configure Neighbor Gateways."
7. If the network that this node is on contains NO internetwork gateways or if you have already configured gateways for this system, press the [Config Directry] key and proceed to the section in this chapter called "Configure X.25 Virtual Circuits".

Fields

Node name

Display only. This is the Local HP 3000 node name.

Network interface (NI) name

Display only.

IP address

The IP address is an address of a node on a network. An IP address has two parts: a network portion and a node portion. The network portion must be the same for all nodes on an X.25 network; the node portion must be unique for all nodes on an X.25 network.

HP assigns the network portion (initial nine digits) of IP addresses from ARPA Class C, though your addresses may also be of Classes A or B. The complete formats are:

 Class A:        nnn.xxx.xxx.xxx

 Class B:        nnn.nnn.xxx.xxx

 Class C:        nnn.nnn.nnn.xxx

 Where:          nnn = the network portion of the IP address

                 and

                 xxx = the node portion of the IP addres
          

Note: A space separates the network and node portions of the IP address.

For Class C, the node portion of the IP address must be between 000 and 255.

If you are adding your NS 3000/iX node to an existing NS 3000/V network, the network portion of each node's IP address should be the same. You will have to find out what this is, and use it in the network portion of the IP address of your NS 3000/iX node. Also, you will need to know the node portions of the IP addresses of each of the nodes (usually they will be numbered sequentially, such as 001, 002, and so on), so that you can specify a unique node portion for the IP address of your node. If you have a network map, it should provide a record of such items as the node name and IP address of each node. If there is no record, and if you want to find out each node's IP address, you will have to issue the following command (NM capability required) on each of the nodes:

NETCONTROL NET=NIname;STATUS

The last line of output from this command tells you what the complete IP address is for that node; the last three digits are the unique node portion of the address.

IP subnet mask

An IP subnet mask is specified in the same format as an IP address. The 32-bit mask is grouped in octets expressed as decimal integers and delimited by either a period (.) or a space. An IP mask is used when configuring subnetworks. The mask identifies which bits of an IP address will be used to define a subnetwork. To determine these bits, you first need to estimate how many subnetworks and nodes per subnetwork you need. For details on deriving an IP subnet mask, refer to the HP 3000/iX Network Planning and Configuration Guide.

Link Name

The link name identifies a specific DTC/X.25 Network Access card to be used for X.25 system-to-system connections. This link name must be the same as the link name you entered for this card on the DTC X.25 Card Configuration — Sys-to-Sys LUGs screen when you configured your DTCs, see Chapter 3 "Configuring DTCs Step-by-Step"

DTC Node Name

The DTC node name is the fully qualified nodename (name.domain.organization) of the DTC that contains the DTC/X.25 Network Access card with the configured link name.

Card Number

The DTC card number is the number of the DTC/X.25 Network Access card in the associated DTC. If the card is contained in a DTC 48, the DTC card number can be any number from 1 to 5. If the card is contained in a DTC 16, the card number must be 2. If the card is contained in a DTC 72, the DTC card number can be any number from 0 to 3.

Step 7: Configure X.25 Virtual Circuits

1. In the Remote node name field, enter, in turn, 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 HP 3000 node's name here as well.
2. For each remote nodename, type the IP address of the node in the Remote IP address field.
3. To specify that calls can be made to a node, enter its address key in the Address key field. Enter the node portion of the remote node's configured nodename.

   NOTE: An address key called POOL is already preconfigured for you though it doesn't show up on the screen. POOL allows the node being configured to receive any incoming calls even if the remote system's address is not configured on this screen. POOL will also allow you to use NetIPC to programmatically provide an X.25 address that is not configured on this screen. If you want to delete the POOL address key, in the last line of the X.25 Virtual Circuit Configuration screen enter a 3 (for switched VCs) and press the [Go To] key. That brings you to the X.25 SVC Address Key Paths screen where you can then remove the default name POOL by typing over it with spaces and then saving the data.

4. If the address type is a switched virtual circuit, complete steps a through c, but if the address type is a permanent virtual circuit, skip to step 5.
   1. 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.
   2. Make sure the name of the facility set you are using is in the Facility set field. You may either choose the default facility set (STDSFSET) or enter an alternative. If you are configuring a new facility set, enter a new name. (To modify facility set parameters, enter a 5 in the last field on the screen and press the [Go To] key.)
   3. In the Security class field, enter the level of logical security you want to have on this particular entry. The possible values are IN (accept calls from the address), IO (accept calls from and send calls to the address, default), OU (send calls to the address, incoming calls are rejected), and LK (block calls to or from the address).
5. If the address type is a permanent virtual circuit (PVC), in the Permanent VC number field, enter the PVC number of the PVC on the remote node. This value cannot be greater than the number of PVCs for which you are subscribed. It must be within the PVC range you defined during DTC configuration.
6. After you have finished entering new information for each remote node, press the [Save Data] key. (Press the key once for each remote node you are configuring.)
7. If you have completed configuration of X.25 iX System Access, press the [Validate Netxport] key. Otherwise, press the [Prior Screen] key to return to the X.25 Configuration screen.

Fields

Network directory name

The network directory file that will be updated by the information entered through this screen.

Remote node name

You must enter the remote node name of each X.25 node into the network directory. Include entries for all remote nodes and, if you want to be able to perform loopback, the local HP 3000 node as well.

Remote IP address

Also in the network directory, you must enter the IP Address of each node whose identity you have entered into the network directory. For the format of this parameter, see the information in the "Fields" section under "X.25 Configuration."

Address key

The X.25 address key is the name of a remote node with which your local node will be communicating. Hewlett-Packard recommends that you make the name be the node portion of the remote node's name (where its full name is node.domain.organization). You must configure an X.25 address key for each remote node with which your node will be communicating. You have a combined maximum of 1024 X.25 address keys in the SVC and PVC path tables. The X.25 address key name must be eight characters or less and the first character must be alphabetic. A default address key called POOL allows any system to access the local system even if the remote system's address is not configured. POOL can also be used when level 3 programmatic access (NetIPC) provides an X.25 address.

Network interface (NI) name

Display only.

SVC or PVC Parameters

The parameters for assigning either SVCs or PVCs are described in the following paragraphs.

Remote X.25 address

The remote X.25 Address is the remote node's X.25 address. This address is required for SVCs if you have specified an X.25 address key. This address must be 15 digits or less.

Facility set

The facility set name is a name for a set of X.25 connection parameters. The parameters are determined by the type of X.25 network that you are subscribed to. You can configure options in a facility set so that specified options are available for every virtual circuit or negotiated for each virtual circuit on a per-call basis. This facility set will be used when a connection is made from your node to the specified remote node or from the specified remote node to your node. A Facility Set is required for SVCs if you have specified an X.25 Address Key. The facility set name must be eight characters or less, and the first character must be alphabetic. You can configure up to 128 facility sets.

To modify facility set parameters, enter a 5 in the field at the bottom of the screen and press the [Go To] key. This will take you to the X.25 User Facility Sets screen. From this screen you can create new or modify existing user facility sets. Refer to the NS 3000/iX NMMGR Screens Reference manual for more information.

Security Class

The security class is the level of logical security you want to have when a connection is made to or from the specified remote node. A Security level is required for SVCs if you have specified an X.25 Address Key. The possible values are as follows:

• IO — Both incoming and outgoing calls are accepted. This is the default value.
• IN — Only incoming calls are accepted from this particular remote address. Outgoing calls will be rejected.
• OU — Only outgoing calls are accepted to this particular remote address. Incoming calls will be rejected.
• LK — Entry is locked. No call is accepted, either inbound or outbound.

For PVCs

Permanent VC number

The PVC number identifies a permanent virtual circuit (PVC) on the remote node. If you have entered a name in the X.25 Address Key field and are configuring PVCs, then you also have to enter a value for the PVC number.

---

Chapter 6 Configuring X.25 Links Step-by-Step

Configure Neighbor Gateways