 |
» |
|
|
|
The procedures that follow describe how to modify the NMMGR configuration
file for the introductory screens. Start NMMGR | |
Node manager (NM) or network administrator (NA) capabilities
are required to run this program. To run NMMGR: Type NMMGR.PUB.SYS at the system prompt (:). Press [RETURN].
Open Configuration File | |
The Open Configuration/Directory File screen (#1) in Figure 5-2 “Open Configuration/Directory File
Screen” is the first screen displayed when you run
NMMGR. Follow the steps listed here to enter data for this screen.
Refer to "Fields" subsection for detailed information
about each field on the screen. Verify that the correct configuration file
name, backup configuration file name, and network directory file
name are in the appropriate fields. 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. Press the [Open Config] key. If you are creating the configuration file for the
first time, NMMGR will ask you to verify creation. Press the [Open Config] key again to continue. 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 and reboot the system. (Keep in mind that any file you
use as a configuration file must be successfully validated before you
try to use it.) - Backup configurationfile name
A backup file name must be specified whenever a configuration
file is opened or created. The default backup configuration file
name is NMCBACK.group.account. 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
A network directory must be configured in the following circumstances: nodes not using domain name services nodes on a LAN network that do not support the HP-PROBE
protocol
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. If the name of the data file is less than six letters
long, then the entire file name would be appended with a K. - Write access password
The password is an optional feature. If a password
has been assigned, you must enter it in the password field to update
the configuration file or the directory file. It is still possible
to open an existing file without using an assigned password, but
the file will be in read only mode and NMMGR will not accept 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.
Select NS Configuration | |
To Select NS Configuration. The Main screen (#2) in Figure 5-3 “Main Screen” 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 “Open Configuration/Directory File
Screen”. Ensure that the information in the fields
on this screen is correct. If not, or if the information has not
been entered, specify the correct information and press the [Save Data] key. (See Configuring Systems for Terminals,
Printers, and Other Serial Devices for information about configuring
the information on this screen.) When you are satisfied with the information as configured,
press the [NS] key to select the NS configuration branch.
Fields- Local node name
The local node name is the name by which the HP e3000
computer is known in the network. The format of a node name is nodename.domain.organization where the total number of characters is 50 or fewer,
and each field contains 16 or fewer characters (alphanumeric, underscore,
or hyphens). The first character of each field must be alphabetic. The nodename portion of each node name must be unique within the
node's network. The nodename.domain portion of each node name must be unique within the
internetwork. HP recommends that all nodes on the network be assigned
the same domain and organization. Assign meaningful node names. For example, MKTG.BND.HP and LAB.BND.HP are meaningful names for two nodes on the same network
within Hewlett-Packard. One node (MKTG.BND.HP) is used by the marketing department. The other node (LAB.BND.HP) is used by the lab. The domain 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 to this question, NMMGR assumes you
are using a PC to manage your system and takes you to the corresponding
set of screens when you configure DTS. If you answer no, NMMGR assumes
you are using host-based network management and takes you to a different
set of DTS screens. You should already have answered this question
when you configured DTS. - Do you have X.25 system- to-system or PAD connections?
If you answer yes 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, NMMGR assumes you have no need to configure
X.25 connections and takes you to a different set of DTS screens.
You should already have answered this question when you configured
DTS.
Select Guided Configuration | |
The NS Configuration screen (#166) in Figure 5-4 “NS Configuration Screen” is
displayed if you press the [NS] key at the Main screen (#2) in Figure 5-3 “Main Screen”. 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. Press the [Guided Config] key to proceed with guided configuration of LAN.
Guided/Unguided Configuration | |
Hewlett-Packard recommends that you press the [Guided Config] key to select the guided configuration branch whenever
you need to initially configure a network interface. Guided configuration
supplies many default values for your configuration and requires
that you visit a minimal number of screens. This manual provides
information on every screen available to you through unguided NS
configuration. The [Unguided Config] key is used to modify configuration values that are not
available in the guided screens. To use the unguided configuration
screens, refer to the NS 3000/iX NMMGR Screens Reference
Manual. Fields- Local Domain Name
The name of this system in the ARPANET standard format.
This name can be used by other nodes on the network to access this
host. The domain name is composed of labels, with each label separated
by a period. Each label must start with a letter or digit, and have
as interior characters only letters, digits, hyphens (-), or underbars
(_). A domain name may have any number of labels, but its total length,
including periods, is limited to 255 characters. label[.label][...] Domain names are not case sensitive. Use of domain names is optional. If you are not using domain
names for network access, leave the local node name in this field.
Perform Guided Network Transport Configuration | |
The Network Transport Configuration screen (#42) in Figure 5-5 “Network Transport Configuration Screen” is displayed if you press the [Guided Config] key at the NS Configuration screen (#166) in Figure 5-4 “NS Configuration Screen”. Next to the words Enter a network interface:, enter a name for the selected network interface
(for example, LANNI). 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.) Press the [Config Network] key. (There may be a short pause before the next screen
appears.) Proceed to the chapter of the network interface selected
above for screen information. Refer to Chapter 6 “Configuring a LAN Node” for information
on LAN, Token Ring, FDDI, 100VG-AnyLAN, and 100Base-T; and other
chapters for information on Point-to-Point, X.25, and Gateway Half
respectively.
Fields- Enter a network interface
The network name (NI name) is used to easily identify one
of the types of network interfaces: LAN, Token Ring, FDDI, NS Point-to-Point,
X.25 or Gateway Half. The name can be up to eight alphanumeric characters, starting
with a letter. The maximum number of NIs that can be configured
on a node is 48. One of the 48 allowable NIs is reserved
for loopback. (Loopback is configured for you automatically.) If a node interfaces to more than one network, give each NI
on that node a unique name. Although all nodes on the same network
do not have to have the same NI name, it will be easier to remember
if you make the NI name the same for all nodes on the same network
(for instance, LANNET). You will use the NI name with the NETCONTROL command to start the transport and network link. - Enter a network type
Number that indicates the type of network interface you
are configuring. You must enter a network type if you are configuring
a new network interface. Refer to the following for what number
to enter: Enter
1 for a LAN NI (100Base-T, ThinLAN or 100VG-AnyLAN) Enter 2 for a Point-to-Point (router) NI Enter 5 for a Gateway Half NI Enter 6 for a Token Ring NI
|
Printable version
