HP 3000 Manuals HP 3000 Manuals
Modify the Network Management Configuration File (Cont'd) Step 11: Configure X.25 System-to-System Information NMMGR displays the DTC X.25 Card Configuration- Sys-to-Sys LUGs screen (see Figure 3-10 ) if you press the [Go To SysLUG] key at the DTC X.25 Card Configuration screen or the DTC X.25 Card Configuration - Level 3 & Miscellaneous screen. On this screen, you specify information for X.25 system-to-system connections. You can also reach this screen by typing the following path at the Command line and pressing the [ENTER] key: @DTS.DTC.SELECT.dtcname.X25CARDn.SYSLUGFigure 3-10. DTC X.25 Card Configuration - Sys-to-Sys LUGs 1. Verify that the cursor is in the X.25 link name field. Enter the link name that will be used for X.25 iX System Access (X.25 system-to-system connections) for this DTC/X.25 Network Access card. This link name must be the same as the link name configured on the X.25 Configuration screen during NS configuration (see chapter 6). 2. Move the cursor to the Maximum number of Switched Virtual Circuit field. Enter the maximum number of SVC connections that will be supported for this card. 3. Move the cursor to the System X.25 address field. Enter the same X.25 address as entered in the X.25 card address field on the Level 3 and Miscellaneous screen unless your network application requires the address used for X.25 system-to-system communications to be different from that used for PAD communications. If the addresses must be different, enter the X.25 address that the local system will use for system-to-system connections in this field. Note that with certain networks (such as Transpac, in France) the called address is removed from incoming call packets and the calling address is added to outgoing call packets by the network. For these networks, enter only the subaddress in this field, not the full X.25 address. 4. Move the cursor to the first Address field under Enter remote X.25 addresses and security. Enter the X.25 address of a system that will be able to establish a system-to-system connection with the HP 3000 Series 900 you are configuring. 5. Move the cursor to the Sec. field next to the address you just entered. Enter the security level for connections between the remote X.25 address and the system you are configuring. Possible values are IN (accept calls from the address), OU (send calls to the address), and IO (accept calls from and send calls to the address). 6. Repeat steps 4 and 5 for each remote system that will be able to establish a system-to-system connection with the HP 3000 Series 900 you are configuring. If you need to enter more than eight remote system addresses, press the [Save Data] key to save the data on this screen, then use the [Next Page] key to move to a new data entry screen to configure additional addresses. 7. When you have entered all remote X.25 addresses and associated security, press the [Save Data] key to save the configuration. 8. Press the [Go To PAD] key to move to the DTC X.25 Card Configuration - Nailed PAD Connections screen. Fields This screen lets you configure X.25 system-to-system local user group(LUG) information for the DTC/X.25 Network Access card being configured. DTC name Display only. Card number Display only. X.25 link name The name of the link that will be used by the system being configured for X.25 system-to-system connections. Must be the same as the link name entered during NS configuration of X.25 iX System Access using the NS subbranch of NMMGR. The link name can be up to eight alphanumeric characters, beginning with a letter. Maximum number of The number of switched virtual circuits Switched Virtual (SVCs) that will be allowed through this Circuits DTC/X.25 Network Access card. Up to 32 SVCs are allowed for cards mounted in a DTC 16, up to 256 SVCs are allowed for cards mounted in a DTC 48 and up to 156 SVCs are allowed for cards mounted in DTC 72MX. The following factors must be considered in determining how many SVCs to allow: * The total number of SVCs which an X.25 board can establish depends on the packet size configured in the X.25 level 3 configuration. Upper limits for each DTC48 and DTC72MX card are: * 256 for packet sizes of 512 or less. * 150 for 1024 byte packets. * 100 for 2048 byte packets. * 54 for 4096 byte packets. Note that these limits are not affected by packet size negotiation. That is, if you have configured a packet size of 4096, and a packet size of 128 has been negotiated, you are still limited to the 54 SVCs supported with 4096 byte packets. * If you are also configuring PAD connections on this card, remember that PAD connections use SVCs out of the pool of available SVCs. You will need to balance your PAD support requirements with your system-to- system requirements to find the optimum configuration for your network. * The total number of SVCs available may also be limited by your PSN subscription. System X.25 address This is the X.25 address of the X.25 card, to be used for system-to-system connections. In most cases, this will be the same as the address entered on the Level 3 & Miscellaneous screen. If, however, your network application requires the address used for X.25 system-to-system communications to be different from the address used for PAD connections, enter a different address here. For most connections to public data networks, this will be the DTC/X.25 Network Access card address plus a unique subaddress for the host system. Note that with certain networks (such as Transpac, in France) the called address is removed from incoming call packets and the calling address is added to outgoing call packets by the network. For these networks, enter only the subaddress in this field, not the full X.25 address. Address The X.25 addresses of the remote systems in your X.25 network Sec. The security level associated with each remote X.25 address. To accept only incoming calls for call setup, enter IN in the security field beside the address. To allow only outgoing calls for call setup, enter OU. To allow both incoming and outgoing calls for call setup, enter IO. Step 12: Configure Nailed PAD Connections NMMGR displays the DTC X.25 Card Configuration- Nailed PAD Connections screen (see Figure 3-11 ) if you press the [Go To PAD] key from the DTC X.25 Card Configuration screen or the DTC X.25 Card Configuration - Sys-to-Sys LUGs screen. On this screen, logical device (ldev) numbers, profile names, device names, and remote X.25 addresses are permanently associated with individual PAD connections allowed through the card. Configure the connections as required. You can also reach this screen by typing the following path at the Command line and pressing the [ENTER] key: Table 3-6. ----------------------------------------------------- | | | | | @DTS.DTC.SELECT.dtcname.CARD012.PADn | | | | ----------------------------------------------------- | | | | | Or | | | | ----------------------------------------------------- | | | | | @DTS.DTC.SELECT.dtcname.CARD345.PADn | | | | -----------------------------------------------------Figure 3-11. DTC X.25 Card Configuration - Nailed PAD Connections 1. Verify that the cursor is in the first field under Ldev. Type the ldevnumber that the nailed connection will use in the Ldev field. 2. Move the cursor to the Profile field and enter the profile name the connection will use. _________________________________________________________________ NOTE To see a list of existing profiles, press the [Go To Profiles] key. If you need to create a new profile, see "Terminal and Printer Profiles" in chapter 4. _________________________________________________________________ 3. Move the cursor to the Device Name field and enter the unique name assigned to the remote device that will be using this nailed connection. 4. Move the cursor to the Remote Device (PAD) X.25 Address field and enter the X.25 address of the remote PAD that will be using this nailed connection. 5. If you want to associate a closed user group number with this nailed connection, move the cursor to the CUG No. field and enter the CUG number. 6. Repeat the above steps for every device attached to this card. (You can use the [Fill Cards] key to fill in ldev and profile information.) If you need to configure more than eight nailed PAD connections for this card, press the [Save Data] key to save the data on this screen, then use the [Next Page] key to move to a new data entry screen to configure additional nailed connections. You can configure up to 256 nailed PAD connections for each card. 7. When all nailed connections have been configured, press the [Save Data] key. 8. Press the [Go To Security] key to move to the DTC X.25 Card Configuration - PAD Security screen. Fields This screen is used to permanently associate ldev numbers and other information with individual connections that can be made through a DTC/X.25 Network Access card; that is, to configure nailed PAD connections. DTC name Display only. Card number Display only. Ldev The logical device (ldev) number to be associated with the connection. Each ldev number must be unique; it may not be duplicated by any other device configured on the system. Profile The PAD terminal or PAD printer profile name to be associated with the connection. The features defined by the profile must correspond to the actual operating features of the connection and the device. Device Name The name associated with the PAD-connected terminal or printer. The device name can be up to eight (8) characters and must be unique for each PAD connection. Remote Device (PAD) The X.25 address of the remote PAD device. Where X.25 Address devices are connected to a multiport PAD, include port subaddresses in this field. CUG No. (Optional) The closed user group number(0 to 99), if specified for your network subscription. Leave blank if your subscription does not specify a CUG number. Step 13: Configure PAD Security NMMGR displays the DTC X.25 Card Configuration - PAD Security screen (see Figure 3-12 )if you press the [Go To Security] key from the DTC X.25 Card Configuration screen or the DTC X.25 Card Configuration - Nailed PAD Connections screen. On this screen, you specify either a list of PAD calling addresses that will be accepted or a list of PAD calling addresses that will be rejected for connection through the DTC/X.25 Network Access card being configured. You can also reach this screen by typing the following path at the Command line and pressing the [ENTER] key: @DTS.DTC.SELECT.dtcname.X25CARDn.PADSECFigure 3-12. DTC X.25 Card Configuration - PAD Security 1. Verify that the cursor is in the Allow access field. If you want to accept calls only from the calling addresses listed below (and reject all other calls), enter a Y. If you want to reject calls only from the calling addresses listed below (and accept all other calls), enter an N. 2. In the fields under Enter remote X.25 calling address below:, enter the X.25 addresses of all remote PAD devices that will be accepted for connection, if Allow access is Y, or enter the addresses of all remote PAD devices that will be rejected for connection, if Allow access is N. If you need to configure more addresses than there is room for on this screen, press the [Save Data] key, then press the [Next Page] key to enter more device addresses. Up to 512 remote X.25 calling addresses can be configured. 3. If you have finished configuring PAD security for this card but still need to configure additional cards or DTCs, press the [Prior Screen] key until you return to the DTC Configuration screen so that you can select a different card or DTC to configure. 4. If all DTCs and all cards have been configured, press the [Validate DTS/LINK] key to validate the DTC configuration for the system. (See appendix A for validation error messages.) Fields DTC name Display only. Card number Display only. Allow access Specifies whether connection requests from devices whose addresses are listed will be accepted (Y) or rejected (N). If you enter Y, calls will only be accepted from devices whose addresses you list on this screen. If you enter Y and do not list any addresses, all calls will be rejected. If you enter N, calls will only be rejected from devices whose addresses you list on this screen. If you enter N and do not list any addresses, all calls will be accepted. If you do not update this screen (data flag is N, a default PAD security will be downloaded that allows all calls to be accepted. Enter remote X.25 Lists the X.25 addresses of all PAD devices calling address that will be accepted for connection if below Allow access is Y or rejected for connection if Allow access is N. Enter up to 32 remote addresses per screen and up to 512 per DTC/X.25 Network Access card. You can use the letter X as a wildcard character in place of any single digit. All systems with corresponding addresses will have the same access rights. The address check is sensitive to the length of the address. To manage addresses, you may enter pyramids of Xs where the base is the longest expected address and the peak is the shortest expected address. For example to control access to all PAD addresses of six, seven or eight digits starting with 1234: Table 3-7. ---------------------------- | | | | 1234XX | | | | | ---------------------------- | | | | 1234XXX | | | | | ---------------------------- | | | | 1234XXXX | | | | | ---------------------------- To control access to PADs with addresses of seven digits starting with 6789: 6789XXX Step 14: 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 DTS configuration in the configuration file, press the [Validate DTS/LINK] key at the Card Configuration screen. You can also reach the Validate Configuration File screen by typing validate at the command line on top of any NMMGR screen and pressing [Enter]. (Note that the [Enter] key is not the carriage return key.) While at the Validate screen press the [Validate DTS/LINK] key to validate the DTS configuration. The DTS validation procedure starts by displaying the following on the terminal: Table 3-8. --------------------------------------------------- | | | | | -> 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 A, "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 3-9. ---------------------------------------------------------------------------- | | | 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 3-10. ---------------------------------------------------------------- | | | 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. 4. After viewing the messages describing what actions are required, if any, enter [RETURN] when you see the prompt: (Press RETURN when finished view screen contents.) You will return to the Validation screen. You may make additional configuration changes or exit NMMGR.
![[]](../../pic3k/M015985/FFN203c50.gif)
![[]](../../pic3k/M015985/FFN213c50.gif)
![[]](../../pic3k/M015985/FFN223c50.gif)