HP 3000 Manuals HP 3000 Manuals
Modify the Network Management Configuration File The network management configuration file (NMCONFIG.PUB.SYS) contains information that is referenced during system boot-up. A step-by-step procedure for creating or updating the host's network management configuration file follows.
NOTE Before modifying the NMCONFIG.PUB.SYS file, make a backup copyof it. If the modifications made to the configuration file are successful, purge the backup copy.
Step 1: Begin the Configuration Process Run the NMMGR program.Node manager (NM) or network administrator (NA) capabilities are required to run this program. To run NMMGR, enter the following command at the MPE prompt and then press the [Return] key. NMMGR.PUB.SYS
NOTE You must be logged on to the SYS account to modify the configuration file.
Step 2: Open the Network Management Configuration File The Open Configuration/Directory File screen is displayed (see Figure 3-1 ). This screen lets you specify the configuration and backup file names.Figure 3-1. Open Configuration/Directory File 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. 1. NMCONFIG.PUB.SYS is the name required by the software. Verify that this name is displayed in the Configuration file name field. 2. Verify that the name of the correct backup configuration file is in the Configuration file name field. The default is NMCBACK.PUB.SYS. 3. Press the [Open Config] function key. 4. 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. Fields Configuration file The only valid configuration file name the system name 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. Backup configuration A backup file file name 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 The Network directory filemust be configured for file name 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 The passwordis an optional feature. If a password 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 (NMS) Utilities manual (32022-90041). Step 3: Configure the Local Node Name The Main screenis displayed after you press the [Open Config] key (see Figure 3-2 ). 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.Figure 3-2. Main Screen 1. 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. 2. 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 the Configuring Systems for Terminals, Printers, and Other Serial Devices manual (32022-61000). 3. In the field after the question, "Do you have X.25 system-to- system or PAD connections?", enter an Y for yes. 4. After you enter the information on the screen, press the [Save Data] function key to save your entries. 5. After the data is saved (the Data flag in the upper right-hand corner is Y), press the [DTS] function key. Fields Local HP 3000 node The local HP 3000 node nameis the name by which the name 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. Assignmeaningful 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 If you answer yes (Y) to this question, NMMGR OpenView DTC assumes you are using a PC to manage your system Manager? 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 enter an N in response to this question. (If you are using a PC to manage your network, see Configuring Systems for Terminals, Printers, and Other Serial Devices for the correct configuration procedures.) Do you have X.25 If you answer yes (Y) to this question, NMMGR system-to- system or assumes you are configuring X.25 connections and PAD connections? takes you to the set of screens required to configure DTC X.25 Network Access Cards. 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 enter a Y in response to this question. (If you are not configuring X.25 connections, see Configuring Systems for Terminals, Printers, and Other Serial Devices manual (32022-61000) for the correct configuration procedures.) Step 4: Configure the Link The Host Configuration screen is displayed when you press the [DTS] function key at the Main screen (see Figure 3-3 ). 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 3-3. Host Configuration Screen (Host-based) 1. "Local HP 3000 node name" is a display-only field. Verify that it is correct. 2. The "Link name" fielddisplays DTSLINK. This is used by the HP 3000 DTS subsystem. Use this default. 3. In the "Physical path of LANIC" field, type the slot number for the LANICcard in the host. See the default list for commonly used slot numbers. 4. Verify that the cursor is in the Number of non-nailed PAD terminals field. Type the number of non-nailed PAD terminals, as listed on the worksheets. This is the maximum number of PAD terminals, not configured as nailed PAD terminals, that can logon to the computer. 5. Verify that the cursor is in the Non-nailed PAD terminal profile name field. Type the name of the terminal profile that the non-nailed PAD terminals will use, as listed on the worksheets. 6. Press the [Save Data] function key. Press the [Go to DTC] function key to proceed to Step 5: Select DTC Type.
NOTE The [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 the Configuring Systems for Terminals, Printers, and Other Serial Devices manual (32022-61000) for more information on the user port.
NOTE The [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 the Configuring Systems for Terminals, Printers, and Other Serial Devices (32022-61000) and to Performing System Manager Tasks (32650-90004) 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 the Configuring Systems for Terminals, Printers, and Other Serial Devices manual for information on how to connect a UPS to a DTC port. Fields This screen is used to configure the information that applies to the host system. This information defines the interaction between the system and its asynchronous devices, such as terminals and serial printers. Local HP 3000 node For display only. The local node nameis configured name on the Main screen. Link name The link namethat will be used when device connections, including PAD device connections, are established. It must start with a letter and can be up to eight alphanumeric characters. (Note that this link name is different from the X.25 link name that you will configure on the X.25 Configuration screen during NS configuration.) The default is DTSLINK Physical path of This is the location of the DTS LANIC in the LANIC 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. Table 3-2. -------------------------------------------------- | | | | HP 3000 Systems | Slot Number | | | | -------------------------------------------------- | | | | 920, 922, 935, 932, 935, or | 4.3 | | 949 with HPIB | | | | | -------------------------------------------------- | | | | 920, 925, 935, or 949 with | 4.2 | | ALINK | | | | | -------------------------------------------------- | | | | 9X7 | 56 | | | | -------------------------------------------------- | | | | 9X8 | 56/56 | | | | -------------------------------------------------- | | | | 930 | 8.4 | | | | -------------------------------------------------- | | | | 950, 955, 960, 980 | 2/4.2 | | | | -------------------------------------------------- | | | | 990/992, 991/995 | 0/40 | | | | -------------------------------------------------- Number of non-nailed The number of non-nailed PAD terminalsthat will be PAD terminals allowed to establish connections with this system over an X.25 network. Other than entering the non-nailed PAD terminal profile name, no additional configuration is needed for non-nailed connections. Non-nailed PAD The terminal profile that will be used for all terminal profile non-nailed PAD connections accepted by the system. name PAD terminals must use a profile that defines the terminal type as terminal type 24. Step 5: Select DTC Type The DTC Configuration Selection screen(see Figure 3-4 ) is displayed when you press the [Go To DTC] key at the Host Configuration screen. Here you specify the type of DTC to configure.Figure 3-4. DTC Configuration Selection Screen 1. Select the DTC type by pressing one of the function keys: [DTC16iX], [DTC16MX/RX], [DTC16], [DTC48], or [DTC72MX]. NMMGR will take you to the configuration screen for the specified DTC type.
NOTE You may use the [List DTCs] key on the DTC Configuration Selection screen to see a list of all DTC names configured on your system.
Step 6: Specify DTC Configuration The DTC Configuration screenis displayed after you select the DTC type at the DTC Configuration Selection screen. Figure 3-5 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 3-5. DTC Configuration Screen 1. Enter the DTC's namein 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". 2. Enter the DTC's LAN addressin 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, you must use the value 00-00-00-00-00-00 as the DTC 16RX LAN address. 3. Type in the DTC's node namein 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: Table 3-3. ------------------------------------------------ | | | | | 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: Table 3-4. ------------------------------------------------ | | | | | DTC name = ALPHA | | | | ------------------------------------------------ | | | | | DTC node name = ALPHA.ACCTG.TEKLAB | | | | ------------------------------------------------ 4. (Optional) Enter an IP addressfor 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 for the DTC 16RX in this field will be ignored. Refer to chapter 2 for more information on IP addresses. 5. Enable the event logging classesthat 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 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 access to an HP 3000 in an MPE/iX host-based management environment using a DTC 16RX; any values entered in these fields for the DTC 16RX will be ignored. 6. 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 for more information on card types for each DTC. 7. (Optional) Enter a password if you wish to require the users to provide a password when they attempt to establish a communication link to this DTC via a PAD device. The syntax that the user would use is described in PAD Profiles and Access Password in chapter 4. Refer to chapter 4 for the syntax that the user will enter at the PAD prompt to supply the password. 8. Press the [Save Data] function key. 9. 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. 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 10. Repeat steps 1 through 9 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.
NOTE You may use the [Tune DTC] keyon the DTC Configuration screen to change the AFCP and Management timersfor the DTC, if needed. Refer to the Configuring Systems for Terminals, Printers, and Other Devices manual (32022-61000) for more information.
NOTE You may use the [Config SNMP] key on the DTC Configuration screen to configure the DTC to act as an SNMP. This key will take you to a series of screens which will allow you to configure SNMP authorization filters, MIB parameters, and trap destinations. Refer to the Configuring Systems for Terminals, Printers, and Other Serial Devices manual and the DTC Technical Reference Guide for more information on SNMP. Fields This screen is used to configure a DTC's name and node name, to specify the card types that are installed in the DTC, and to configure logging for X.25 connections, if the DTC contains one or more DTC/X.25 Network Access cards. DTC name A name, up to eight alphanumeric characters, beginning with a letter, assigned to the DTC. For convenience, you may want to use the nodename portion of the DTC node name as the DTC name. Each DTC configured on the system must have its own unique DTC name. You can call up (and modify) data for a previously configured DTC by entering an existing DTC name in the DTC name field and pressing the [Read DTC] key. DTC LAN station The local station addressof the DTC. This is address a twelve character hexadecimal number. Each DTC's LAN station address is printed inside the DTC's front cover on a DTC48, or on the back panel of the DTC72MX or DTC16MX/iX/RX. DTC node name The fully qualified node nameof the DTC, in the form nodename.domain.organization. Each part of the name can be up to 16 characters. DTC IP Address The internet protocol (IP) addressof the DTC (Optional) being configured. An example of an address is: C 192.191.191 009. The IP addressis optional for the DTC, but one must be configured if the DTC is to be able to respond to PINGrequests. Enable logging class These fields, labeled 1 through 6, enablethe (Y/N) DTC to log various classes of events. Enter a Y to enable a class, N to disable. Only events falling into classes which you have explicitly enabled will be logged. Class 1 events are the most critical and will always be logged. Note that enabling class 5 will result in a substantial number of events being logged. HP suggests that you enable class 5 only when necessary and only for short periods of time. You should also avoid enabling logging class 5 simultaneously with an X.25 trace. Type (of card) The type of card installed in the DTC. Verify that the cursor is in the "Type" field under "Enter card types as installed in DTC." Enter the card type for each card in the DTC. The valid card types are listed on the screen. PAD access password A password, up to eight alphanumeric (optional) characters in length, that will be required when users connected to this DTC via a PADdevice attempt to establish a communication link. To configure a card, This parameter determines the next screen enter a card number that will appear after you have saved the then press Config data configured on the screen. Enter the Card number of the card you want to configureand press the [Config Card] key.
![[]](../../pic3k/M015314/FFN113c50.gif)
![[]](../../pic3k/M015314/FFN123c50.gif)
![[]](../../pic3k/M015314/FFN133c50.gif)
![[]](../../pic3k/M015314/FFN143c50.gif)
![[]](../../pic3k/M015314/FFN153c50.gif)