 |
» |
|
|
|
Use NMMGR to enter asynchronous device configuration information
into the network management configuration file (NMCONFIG.PUB.SYS).
A step-by-step procedure for updating the host's network
management configuration file follows. | | | |  | NOTE: Before modifying the NMCONFIG.PUB.SYS
file, make a backup copy of it. If the modifications made to
the configuration file are successful, purge the backup copy. | | | | |
Step 2: Open the Network Management Configuration
File | |
The Open Configuration/Directory File screen is displayed
(Figure 5-1 “Open Configuration/Directory Screen”). This screen lets
you specify the configuration and backup file names. Figure 5-1 Open Configuration/Directory Screen Follow the steps listed here to enter data for this screen.
Refer to "Fields" subsection on the next page
for detailed information about each field on the screen. NMCONFIG.PUB.SYS
is the name required by the software. Verify that this name is displayed
in the Configuration file name
field. Verify that the name of the correct backup configuration
file is in the Configuration file name
field. The default is NMCBACK.group.account. Press the [Open Config]
function key. If the configuration file you are opening does not
exist, the following message will appear on the message line at
the top of the screen:
Config file does not exist; press Open Config again to create it. Press the [Open Config]
key again to confirm the creation of the file you specified. FieldsTitle not available (Step 2: Open the Network Management Configuration
File) - Configuration file name
The only valid configuration file name the system
recognizes for use by the network subsystem is NMCONFIG.PUB.SYS. You can 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. 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), and reboot the system or perform a DTS shutdown/restart
(see Chapter 4 “Dynamic Configuration and DTS Shutdown/Restart” for more
information on DTS shutdown/restart). - 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 X.25 node (unless you will only
be accessing the node using direct level 3 access). This
field is only used for X.25 network management. 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. - 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 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, refer to Using the Node Management
Services.
Step 3: Configure the Local Node Name | |
The Main screen is displayed after you press the [Open Config]
key (Figure 5-2 “Main Screen”). This screen lets
you specify the HP 3000 host's name. It also asks whether
you are using the HP 3000 host or an OpenView Windows Workstation
(PC) for DTC management, and if you are using X.25 or PAD. Assign a node name to the HP 3000 host in the "local HP 3000 node name"
field. Use the format nodename.domain.organization. If your HP 3000 host is the only computer in your network,
you may enter any node name. If you have several computers on your
network, you must make sure the node names for each host are unique.
Refer to Chapter 2 “Before Configuring Terminal and
Printer Connections” for
more information on node name. In the field after the question, "Are you using the OpenView DTC Manager?",
enter an N. This means that you will not use the
OpenView DTC Manager (that is, use a PC to manage your DTCs)
.
Instead, you will use the HP 3000 host to manage your DTCs. If you specify "Y"
for using OpenView DTC Manager refer to Chapter 6 “Configuring Serial Devices (for
PC-Based Management)” In the field after the question, "Do you have X.25 system-to-system or PAD connections?",
enter an N for
no. If you have X.25, refer to the Configuring and
Managing Host-Based X.25 Links manual. After you enter the information on the screen, press
the [Save Data] function key
to save your entries. After the data is saved (the Data
flag in the upper right-hand corner is Y),
press the [DTS] function key.
Step 4: Configure the Link | |
The Host Configuration screen is displayed when you press
the [DTS] function key at the
Main screen (Figure 5-3 “Host Configuration Screen (Host-Based)”). This screen is used to configure the Datacommunications and
Terminal Subsystem (DTS) on the HP 3000. DTS defines the interaction
between the system and any asynchronous devices, such as terminals
and printers. Figure 5-3 Host Configuration Screen (Host-Based) "Local HP 3000 node name"
is a display-only field. Verify that it is correct. The "Link name"
field displays DTSLINK.
This is used by the HP 3000 DTS subsystem. Use this default. In the "Physical path of LANIC"
field
,
type the slot number for the LANIC card
in the host. See the list on the next page for commonly used slot numbers. Press the [Save Data]
function key. Press the [Go to DTC] function
key to proceed to step 5: Select DTC Type.
Go to UserPortThe [Go To UserPort] key
is used to configure the user port (default ldev 21) on
the NIO console. Pressing this key takes you to the HP Support Modem
Port Screen for configuring the ldev, the line speed, modem type,
and parity of the user port. The configuration of user port is only
supported for the NIO LAN console card (for example, HP 3000 Series
9X7 and 9X7 LX). Refer to Chapter 9 “Describing Asynchronous Devices” for more information on the user port. Go to UPS PortThe [Go To UPS Port] key
takes you to the Uninterruptible Power Supply Port Screen. This
screen is used to configure the ldev number, line speed, and parity
on a port of the SCSI/Console LAN card (default ldev 22)
to support an uninterruptible power supply (UPS)
connection. This port is only available and supported on HP 3000
Series 9X8 systems. Refer to Chapter 9 “Describing Asynchronous Devices” and to the Performing System
Manager Tasks manual, for more information on the UPS. A UPS can also be connected to a DTC port via a configuration
process that does NOT use the [Go To UPS Port]
key. Refer to Chapter 9 “Describing Asynchronous Devices”
for information on how to connect a UPS to a DTC port. FieldsTitle not available (Step 4: Configure the Link) - Physical path of LANIC
This is the location of the DTS LANIC in the system's
backplane. The default physical path (slot numbers) for HP 3000 computers
are listed below. These defaults optimize performance and use of
the computer's cabinet space. Before moving the LANIC into
another slot, consult an HP representative.
HP
3000 Systems | Slot
Number |
|---|
920, 922,
935, 932, 935, or 949 with HPIB | 4.3 | 920, 925,
935, or 949 with ALINK | 4.2 | 9X7 | 56 | 9X8 | 56/56 | 930 | 8.4 | 950, 955,
960, 980 | 2/4.2 | 990/992,
991/995 | 0/40 |
Step 6: Specify DTC Configuration | |
The DTC Configuration screen is displayed after you select
the DTC type at the DTC Configuration Selection screen. Figure 5-5 “DTC Configuration Screen” shows the DTC Configuration
screen for a DTC 72MX. (DTC Configuration screens for DTC 16iX,
DTC 16MX/RX, DTC 16, and DTC 48 vary slightly). Figure 5-5 DTC Configuration Screen Enter the DTC's name in the "DTC name"
field. The DTC name can be up to eight alphanumeric characters,
beginning with a letter. The DTC name must be unique on
the system. It is acceptable (and common) to use the
nodename part of the DTC node name
as the DTC name.
See step 3 below for more information. Enter the DTC's LAN address
in the "DTC LAN station address"
field. The LAN address can be found on a label inside the front cover
or on the back panel of the actual DTC box. For DTC 16RX access to an HP 3000 in an MPE/iX host-based
management environment, use the value 00-00-00-00-00-00
as the DTC 16RX LAN address. Configuration of the DTC 16RX on the
HP 9000 host using DTC 16RX Manager
uses the DTC's IP address and not its LAN address. Type in the DTC's node name
in the "DTC node name"
field. Use the format
nodename.domain.organization, where nodename
identifies the DTC. If there is more than one DTC on the network,
the nodename of each DTC must be unique. The
following are examples of valid DTC node names on the same network: ALPHA.ACCTG.TEKLAB BETA.ACCTG.TEKLAB Note that "DTC name"
and "DTC node name"
are two different fields. However, it is acceptable (and common)
to use the nodename part of the "DTC node name"
as the "DTC name",
such as: DTC name = ALPHA DTC node name = ALPHA.ACCTG.TEKLAB (Optional) Enter an IP address for the DTC, if you
want this DTC to be able to respond to PING/iX requests.
Otherwise, leave the "DTC IP Address"
field blank. For DTC 16RX access to an HP 3000 in an MPE/iX host-based
management environment, the IP address of the DTC 16RX is configured
using the DTC 16RX Manager on the HP 9000 host and not on
the HP 3000. Any value entered in this field for the DTC 16RX
will be ignored. Refer to Chapter 2 “Before Configuring Terminal and
Printer Connections”
for more information on IP addresses. Enable the event logging classes
that you want. It is recommended that you enable classes 2 and 3
and disable classes 4 through 6. See "DTC Event Logging"
in Chapter 2 “Before Configuring Terminal and
Printer Connections” for information
on these event logging classes. Note that logging class 1 is not
configurable and is always enabled. Event logging classes do not apply for DTC 16RX access to
an HP 3000 in an MPE/iX host-based management environment;
any values entered in these fields for the DTC 16RX will
be ignored. Verify that the cursor is in the "Type"
field under "Enter card types as installed in the DTC."
Enter the card type for each card in the DTC The valid card types
are listed on the screen. Note that DTC 16iX/16MX/16RX does not have cards since its
port connectors are built directly onto the DTC backplane. Refer to Chapter 2 “Before Configuring Terminal and
Printer Connections”
for more information on card types for each DTC. Press the [Save Data]
function key. To configure a card in the DTC, enter the number
of the card you want to configure in the "To configure a card, enter a card number ..."
field at the bottom of the screen. The desired card number must
have a valid card type entered in the "type" field. Press the [Config Card]
function key. Proceed to step 7: Configure DTC Cards. To configure the ports on a DTC 16iX/16MX/16RX, simply press
the [Config Ports] function key.
Proceed to step 7: Configure DTC Cards. Repeat steps 1 through 8 above for every newly-added
DTC to be managed by the HP 3000 host. If you want to select
a DTC that has already been configured, enter the DTC's
name in the DTC name
field and press the [Read DTC]
function key.
Next Key LabelsWhen the [Next Key Labels]
key is pressed, another set of key labels are displayed, this allows
additional optional information to be configured for the DTC. These
keys provide access to the following configuration screens: - DNS/IP Routing
This key goes to a screen used to configure the
DTC to use Domain Name Services for IP address resolution and IP
routing configuration. These services are configured when back-to-
back connection through routers are used or connections
are to be made from DTC ports to HP 9000s or third party ARPA nodes.
See Chapter 8 “Additional DTC Configuration” for steps
to do this. - Tune DTC
This key goes to a screen to change the AFCP, TCP
and management timers for the DTC, if needed. Refer to Chapter 8 “Additional DTC Configuration” for steps to do
this. - DTC U I
This key goes to a screen that has information that
defines how the DTC user interface behaves. The DTC user interface
is used when a DTC port is configured as a switched port. See Chapter 1 “Introduction” for a description
of how switching is used and Chapter 7 “Terminal and Printer Profiles” for a description of how to configure
ports to allow switching. - Config SNMP
You may use the [Config SNMP]
key on the DTC Screen to configure the DTC to act as an SNMP agent.
This key goes to a screen to configure the DTC to act as an SNMP
agent. Refer to Appendix C “DTC User Interface”
for steps to do this. Refer to the DTC Technical Reference
Guide manual for more information on SNMP.
Step 7: Configure DTC Cards | |
When you press the [Config Card]
key at the DTC Configuration screen, NMMGR will display the corresponding
card configuration screen for the specified card in the DTC. Figure 5-6 “DTC Card Configuration Screen” shows an example of a
Card Configuration screen for DTC 72MX for asynchronous connect
card. (Screens vary slightly for DTC 16iX/16MX/16RX, DTC 16, and
DTC 48). The corresponding screen for a DTC 16iX/16MX/16RX is called
a Port Configuration Screen since DTC 16iX/16MX/16RX has port connectors
built directly onto the backplane and does not have connector cards. Use this screen to configure the ports in the specified card.
On this screen, logical device (ldev) numbers and profile names
are associated with individual ports on the card. Figure 5-6 DTC Card Configuration Screen Verify that the DTC name and card number displayed are correct. (Optional) Enter the port group type.
The valid types are D
for direct connect and M
for modem connect. The default is D. Press the [Tab]
key to move the cursor to the first port on the card. Enter an ldev
number
for this port in the "Ldev"
field. Ldev numbers used for each port on the DTC must be unique. For example, you can use ldev number 100 for port 0 of the
first card, and increment the ldev number by 1 for each consecutive
port. So a DTC 72MX with 3 asynchronous cards (a total of 72 ports)
would be assigned ldev numbers 100 through 123 for the 24 ports
on the first card, 124 through 147 for the ports on the second card
and 148 through 171 for the ports on the third card. For the second DTC, you would start with an ldev number greater
than 171. | | | | | NOTE: Pressing the [Show Ldevs]
key will display a list of all the ldev numbers configured in NMMGR
in addition to the DTC name, card type, and profile name. | | | | |
Enter the profile name
for each port in the "Profile Name"
field. A profile for the port defines the characteristics of the
device to be connected to that port. For direct terminals ports, the suggested profile to use is
TR10D96. For direct printer ports, the suggested
profile to use is PR18D96
(or PR22D24 for
HP printers with status checking). For a UPS connected to a DTC
port, the suggested profile is UP10D12. The tables in Chapter 7 “Terminal and Printer Profiles”
list terminal, printer and UPS profiles supplied by the system.
You may also create your own profiles. Refer to Chapter 7 “Terminal and Printer Profiles” for more information
on profiles. Repeat above two steps for every port in this card. Press the [Save Data]
function key to save the data on the screen. | | | |  | CAUTION: Before you exit this screen, make sure you press
[Save Data] if you want to keep
the data on the screen; otherwise your screen input will be lost.
This occurs even if you temporarily exit the screen to read [Help]
information. | | | | |
To configure another card, enter the card number
you want to configure in the field "To configure a different card, enter its number,..." .
The desired card number must have already been configured in the
previous section, "Step 6: Specify DTC Configuration."
The card is configured if a valid card type is entered in the "Type"
field on the previous DTC configuration screen. Press the [Config Card]
function key. The corresponding screen for the card number entered
in the last step will be displayed. If all the cards have been configured, press the
[Prior Screen] function key to
return to the DTC Configuration Selection screen to select another
DTC to configure. Otherwise, if every DTC has been configured, press
the [Validate DTS/LINK] function
key to validate the configuration file. | | | | | NOTE: NMMGR allows the configuration of up to 4649 terminal
I/O devices. The largest valid ldev number allowed is 4679. | | | | |
Step 8: Validate/Cross-Validate the Configuration
File | |
Validation ensures that no conflicts exist in the network
configuration file (NMCONFIG.PUB.SYS)
between the DTCs and other configuration parameters. After NMMGR
validates the network configuration file, it will automatically
cross-validate
the file with the system I/O devices configured through the SYSGEN
utility. This will take place only if the file opened at the start
of the NMMGR session is NMCONFIG.PUB.SYS
and validation is successful. Additionally, you must have System
Manager (SM) capability or the cross- validation will not occur.
The commands used for SYSGEN cross-validation are in the file NMGRXVAL.PUB.SYS
.
If this file does not exist, NMMGR will create the file for you
before cross-validating. You can edit this file as appropriate for
your environment. Refer to the MPE/iX manual, System Startup, Configuration,
and Shutdown Reference Manual, for information on SYSGEN. To validate the configuration file, press the [Validate DTS/LINK]
key at the Card Configuration Screen, or type validate
at the command line on top of any NMMGR screen and press [Enter].
(Note that the [Enter] key is
not the carriage return key.) The DTS validation
procedure starts by displaying the following on the terminal: -> Validation of DTS/LINK started. <- |
-> Validation of DTS/LINK finished. <- |
If errors were encountered in the configuration file, the
validation procedure will print out the total number of errors found.
Error messages will also be displayed explaining the problems found.
Refer to Appendix D “Error Messages” for
more information about these error messages. After validation of the network configuration file
is complete, the following will appear on the screen as the file
is cross-validated with the files created with SYSGEN (warning messages
may vary): NMMGR will now cross-validate the NMCONFIG file with SYSGEN.SYSGEN version E.02.00 : catalog version E.02.00 THU, DEC 4, 1997, 2:58 AMCopyright 1987 Hewlett-Packard Co. All Rights Reserved. **note** Retrieving NMMGR configuration data... ** First level command ** io log (lo) misc (mi) spu (sp) sysfile (sy) basegroup (ba) keep(ke) permyes (pe) show (sh) tape (ta) clear (cl)(c) exit (ex)(e) help (he)(h) oclose (oc) redo sysgen> PERMYES ON sysgen> BA CONFIG sysgen> SY ** SYSFILE configurator commands ** aauto (aa) aboot (ab) acmsl (ac) asprog (as) cmsl (cm) dauto (da) dboot (db) dcmsl (dc) dsprog (ds) lcmsl (lc) rauto (ra) rboot (rb) rcat (rc) rcmsl (rcm) rdcc (rd) ripl (ri) rnmlib (rn) rsprog (rs) show (sh) clear (cl)(c) exit (ex)(e) help (he)(h) hold (ho)sysfile> RDCC **note** Retrieving NMMGR configuration data...sysfile> HOsysfile> EX sysgen> KE keeping to group CONFIG.SYS Purge old configuration (yes/no)?Automatic yes ** configuration files successfully saved ** sysgen> EXCross-validation with SYSGEN was successful.Copying validated configuration file to backup file, please wait *** |
After successful validation and cross-validation,
and if the file in use is NMCONFIG.PUB.SYS,
the following prompt will appear: Do
you want DTS changes to be become active now (Y/N)? | | Y = | all changes
made take effect now | N = | all changes
made will take effect upon next dynamic configuration or system
boot | H = | help | | > |
Answer Y
if you want to invoke DTCCNTRL and make DTS changes take effect
now, or answer N
if you don't want DTS changes to take effect now. Note
any messages that describe additional actions needed for changes
to become active. After you exit NMMGR you can review any actions
needed by viewing the logs at the end of the file LOGDCC.PUB.SYS. If you answer N,
the DTS changes will take effect the next time DTCCNTRL is invoked,
a DTS shutdown/restart is done, or the system is rebooted. Type H
if you need more help to answer the question. See Chapter 4 “Dynamic Configuration and DTS Shutdown/Restart” for more information
on dynamic configuration. After viewing the messages describing what actions
are required, if any, enter [RETURN]
when you see the prompt: (Press RETURN when finished viewing screen contents.) You will return to the Validation screen. You may make additional
configuration changes or exit NMMGR.
Step 9: Ensure DTS Changes Become Active | |
If you answered Y
to the question "Do you want DTS changes to become active now (Y/N)?"
in step 8, refer to Table 4-1 “Dynamically Configurable
Tasks”
in Chapter 4 “Dynamic Configuration and DTS Shutdown/Restart” for a list
of configuration tasks and associated actions for changes to become
active. For those tasks indicating "No action; changes
take effect dynamically," no additional actions are required
for the DTS changes to become active. You will see a message on
the screen indicating that no other actions are required. For other
tasks requiring additional actions for changes to become active,
you will see messages on the screen indicating what actions must
be taken first.. First, logoff any sessions. To reset
the DTC, turn off the power and then turn on the power again for
the DTC. You may also use TermDSM, an online diagnostic program for
host-managed DTCs, to reset the DTC. Refer to Troubleshooting
Terminal, Printer, and Serial Device Connections for
more information. |
