HP 3000 Manuals HP 3000 Manuals
Modify the Netwark Management Configuration File Use NMMGR to enter asynchronous device connection information into the Network Management Configuration File NMCONFIG.PUB.SYS. The procedure for updating the configuration file follows. Step 1. Begin the Configuration Process To run NMMGR, enter the following command at the MPE/iX prompt and then press the [Return] key. NMMGR.PUB.SYS
NOTE You must be logged on to the SYS account to run NMMGR.
Step 2: Open the Network Management Configuration File After you invoke NMMGR, the Open Configuration/Directory File screen is shown, allowing you to specify the configuration file name.(See Figure 6-1 .)Figure 6-1. Open configuration/Directory Screen 1. Use the default configuration file name, NMCONFIG.PUB.SYS. 2. Enter a backup configuration file name. The default is NMCBACK.PUB.SYS. 3. Use the default network directory file NSDIR.NET.SYS for X.25 network management,if you have X.25 connection. 4. The Password fieldis optional. Refer to the Using the Node Management Services (32022-90041) manual if you want to set a password. 5. Press the [Open Config] key. Step 3: Configure the Local Node Name The Main screen is displayed (see Figure 6-2 ). This screen lets you specify the HP 3000's node name. It also asks whether you are using the HP 3000 or an OpenView Windows Workstation to manage the DTCs, and if you are using X.25 or PAD.Figure 6-2. Main Screen 1. Assign a node name to the HP 3000Make sure this node name is the same as the one you specified for this computer in the OpenView DTC Manager. 2. Enter Y to the question, "Are you using the OpenView DTC Manager?." 3. If you have PADor X.25, enter Y to the question, "Do you have X.25 system-to-system or PAD connections?." 4. Press the [Save Data] key. 5. Press the [DTS] key. Step 4: Configure the Link The Host Configuration screen is displayed when you press the [DTS] key at the Main screen (see Figure 6-3 ).Figure 6-3. Host Configuration Screen (PC-Based) 1. "Local HP 3000 node name" is a display-only field. Verify that it is correct. 2. Use the default link name, DTSLINK. 3. Enter the slot number of the LANIC in the "Physical path of LANIC" field.See chapter 2 for a list of suggested slot numbers to use. 4. Enter the desired number of non-nailed terminals to be allowed on the HP 3000. Currently, NMMGR allows the configuration of up to 4649 terminal I/O devices. 5. Enter the ldev number where the non-nailed pool should start. The non-nailed devices will be configured on ldevs with the starting ldev number and higher. For example if the number of ldevs is 2 and the starting number is 200 then the non-nailed ldev would be 200 and 201. If 201 is already configured as a nailed device then the non-nailed device would be 200 and 202. 6. Enter the profile to use for the non-nailed terminals. _________________________________________________________________ NOTE If you want the HP 3000 system to be able to accept connections from terminals on ARPA systems via a Telnet Express Server,you must use a modem profile for the non-nailed terminals, such as TR10U24. Note that you may use direct connect devices on a port with a modem profile. See the Host-Based Terminal Profiles table in chapter 7, for a list of available profiles. You may also create your own profile. For more information on profiles, refer to chapter 7, "Terminal and Printer Profiles." _________________________________________________________________ 7. Enter the desired number of non-nailed PAD terminals to be allowed on the HP 3000. Currently, NMMGR allows the configuration of up to 4649 terminal I/O devices. 8. Enter the ldev number where the non-nailed pool should start. The non-nailed devices will be configured on ldevs with the starting ldev number and higher. For example if the number of ldevs is 2 and the starting number is 200 then the non-nailed ldev would be 200 and 201. If 201 is already configured as a nailed device then the non-nailed device would be 200 and 202. 9. Enter the profile to use for the non-nailed PAD terminals. 10. Press the [Save Data] key. This concludes NMMGR configuration for PC-based management for this HP 3000 computer if this computer will not be accessing any nailed devices. If the HP 3000 computer needs to access nailed ports in one or more DTCs, press the [Go To DTC] key and proceed to Step 5 to configure the nailed ports. Note that printers and UPSs are nailed devices, so you need to configure any DTC that has printer or UPS ports.
NOTE You can type "help whatsnew" at the command line of this screen for more information on DTS dynamic configuration. You can also refer to chapter 4 for more information on how to make DTS configuration changes dynamically. Automatic DTC configuration is available for host-based environments only.
Step 5: Select DTC Type The DTC Configuration Selection screen (see Figure 6-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. You only need to configure DTCs with nailed ports that will be accessed by this HP 3000 computer.Figure 6-4. DTC Configuration Selection Screen 1. Select the DTC type by pressing one of these function keys: [DTC16iX], [DTC16MX/RX], [DTC16], [DTC48], or [DTC72MX]. NMMGR will take you to the corresponding configuration screen for the specified DTC type.
NOTE Automatic DTC configuration is not available for PC-based environments. If you answer Y to the question "Automatically add/configure a new DTC (Y/N)?" on this screen, you will see an error message.
Step 6: Specify DTC Configuration The DTC Configuration screen is displayed after you select the DTC type. Figure 6-5 shows a DTC Configuration screen for a DTC 72MX. (DTC 16iX/ 16MX/16RX, DTC 16 and DTC 48 screens vary slightly.)Figure 6-5. DTC Configuration Screen 1. Enter the DTC name in the "DTC name" field. 2. Enter the DTC's node name in the "DTC node name" field. 3. Enter the card type for each card in the DTC with nailed devices.(Printers and UPSs, and any terminals that will be accessed programmatically are nailed devices.) 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. 4. Press the [Save Data] function key. 5. To configure a card in the DTC, enter the card number in the "To configure a card, enter a card number ..." field. You only need to configure a card if the card contains nailed devices. Press the [Config Card] function key. Proceed to step 7: Configure DTC Cards. If you are configuring a direct or modem connect card the [Config Card] key will go to the screen described in the subsection Configure a Direct Connect Card. If you are configuring a X.25 card the [Config Card] key will go to the screen described in the subsection Configure a X.25 Card. To configure the ports on a DTC 16iX/16MX/16RX, simply press the [Config Ports] function key. Proceed to step 7: Configure DTC Cards. 6. Repeat steps 1 through 5 above for every newly-added DTC with nailed devices that will be accessed by this HP 3000 computer. 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] key on the DTC Configuration Screen to change the AFCP timers for the DTC, if needed. Refer to chapter 8 for steps to do this.
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 6-6 shows an example of a Direct Connect Card Configuration screen for DTC 72MX. (Screens for DTC 16iX/16MX/16RX, DTC 16 and DTC 48 vary slightly.) Figure 6-7 shows the screen for configuring nailed PAD devices on a X.25 card.
NOTE You only need to configure nailed ports (such as printer ports) in the DTC. If you do not have nailed ports on a card, you can skip this step.
Configure a Direct Connect Card. When you press the [Config Card] key at the DTC Configuration screen and the card is a direct or modem connect card, NMMGR will display the screen appropriate for the DTC. The screen for a DTC72MX is shown in Figure 6-6 (*).Figure 6-6. DTC Card Configuration Screen 1. Verify that the "DTC name" and "Card number" displayed are correct. 2. Use the [Tab] to move the cursor to the first nailed port on the card. Enter the ldev numberand profile for each nailed device. Ldev numbers used for each port on the DTCs must be unique. Up to 4649 terminal I/O devices may be configured on an HP 3000 Series 900. The largest valid ldev number is 4679. A profile for the port defines the characteristics of the device to be connected to that port. For direct terminal 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. Refer to chapter 7 for more information on profiles. 3. Press the [Save Data] key. 4. Enter the card number of a different card that needs to be configured in the "To configure a different card, enter a card number,..." field on the screen. 5. Press the [Config Card] function key. The corresponding screen for the card number entered in the last step will be displayed. 6. If all the cards with nailed ports have been configured, press the [Prior Screen] key to return to the DTC Configuration Selection screen to select another DTC with nailed ports to configure. Otherwise, if every DTC has been configured, press the [Validate DTS/LINK] key to validate the configuration file. Configure a X.25 Card. When a X.25 card is configured using PC-based management, you can use the screen in Figure 6-7 to configure nailed PAD devices. The screen is only available for a DTC 48, DTC 16 and DTC72MX.
NOTE Also refer to Using HP OpenView DTC Manager (D2355-90001) for all other X.25 and PAD configuration information.
Figure 6-7. DTC X.25 Card Configuration Screen 1. Verify that the "DTC name" and "Card number" displayed are correct. 2. Use the [TAB] key to move the cursor to the desired fields. Enter the ldev number, profile and device name in the fields on the screen for nailed device. Ldev numbers used for each port on all DTCs must be unique. Up to 4649 terminal I/O devices may be configured on the HP 3000 Series 900. The largest valid ldev number is 4679. The device name entered must match the PAD Device Name entered in the PAD Access screen on the OpenView DTC Manager. Refer to Using HP OpenView DTC Manager (D2355-90001). 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 (32650-90042), for information on SYSGEN. 1. 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 validationprocedure starts by displaying the following on the terminal: Table 6-2. --------------------------------------------------------------- | | | | | -> 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. 2. 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): Table 6-3. ------------------------------------------------------------------------ | | | NMMGR will now cross-validate the NMCONFIG file with SYSGEN. | | | ------------------------------------------------------------------------ | | | SYSGEN version E.00.00:catalog version E.00.00 FRI FEB 4, | | 1994 3:32 PM | | | ------------------------------------------------------------------------ | | | Copyright 1987 Hewlett-Packard Co. All Rights Reserved. | | | ------------------------------------------------------------------------ | | | | | | **warning** no NMCONFIG file in this | | | | configuration **warning** NMCONFIG.PUB.SYS | | | | is now the NMCONFIG file | | | | | | ------------------------------------------------------------------------ | | | | | ** 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 {Automatically reply YES} | | | ------------------------------------------------------------------------ | | | sysgen> SY {Go to the SYSFILE subsystem} | | | ------------------------------------------------------------------------ | | | | | ** SYSFILE configurator commands ** | | | | ------------------------------------------------------------------------ | | | | | | | | aauto (aa) | aboot (ab) | acmsl (ac) | asprog (as) | | | | | | | ------------------------------------------------------------------------ | | | | | | | | cms1 (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 {Set configuration file to NMCONFIG.PUB.SYS} | | | ------------------------------------------------------------------------ | | | sysfile> {HO} {Remove braces to HOLD RDCC command} | | | ------------------------------------------------------------------------ | | | sysfile> EX {EXit the SYSFILE subsystem} | | | ------------------------------------------------------------------------ | | | | | | configuration changes are not kept yet! | | | | still want to exit (yes/no)? Automatic yes | | | | | | ------------------------------------------------------------------------ | | | sysgen> BA CONFIG {Set BAse group to CONFIG} | | | ------------------------------------------------------------------------ | | | sysgen> KE {KEep the changed configuration data} | | | ------------------------------------------------------------------------ | | | | | keeping to group CONFIG.SYS | | | | ------------------------------------------------------------------------ | | | | | | Purge old configuration (yes/no)? Automatic | | | | yes ** configuration files successfully | | | | saved ** | | | | | | ------------------------------------------------------------------------ | | | sysgen> EX {EXit SYSGEN} | | | ------------------------------------------------------------------------ | | | | | Cross-validation with SYSGEN was successful | | | | ------------------------------------------------------------------------ | | | | | Copying validated configuration file to backup file, | | | please wait *** | | | | ------------------------------------------------------------------------ 3. After successful validation and cross-validation, and if the file in use is NMCONFIG.PUB.SYS, the following prompt will appear: Table 6-4. --------------------------------------------------------------- | | | Do you want DTS changes to 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 reboot | | | | --------------------------------------------------------------- | | | | 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 for more information on dynamic configuration. 4. 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/H)?" upon NMMGR exit in step 8, refer to Table 4-1 in chapter 4 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. Refer to the steps below for more information.
NOTE If you answered N to the question in step 8, thus choosing not to call DTCCNTRL, refer to chapter 4 for details on how to invoke DTCCNTRL outside NMMGR.
Performing a DTC Reboot. First, logoff any sessions. To resetthe 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 (32022-61002) for more information. Performing a DTS Shutdown/Restart. To perform a DTS shutdown and restart, use the DTCCNTRL command. Refer to chapter 4 for more information on how to use this command to perform a DTS shutdown/restart.
![[]](../../pic3k/M015956/FFN213c50.gif)
![[]](../../pic3k/M015956/FFN223c50.gif)
![[]](../../pic3k/M015956/FFN233c50.gif)
![[]](../../pic3k/M015956/FFN243c50.gif)
![[]](../../pic3k/M015956/FFN253c50.gif)
![[]](../../pic3k/M015956/FFN263c50.gif)
![[]](../../pic3k/M015956/FFN273c50.gif)