HP 3000 Manuals

To Use NMMGRVER [ HP3000/iX Network Planning and Configuration Guide ] MPE/iX 5.0 Documentation


HP3000/iX Network Planning and Configuration Guide

To Use NMMGRVER 

To use the NMMGRVER utility to convert your NS3000/V configuration file
to NS3000/iX release 2.0 or later, proceed as follows:

   1.  At the MPE/iX prompt, type:  NMMGRVER.PUB.SYS

   2.  Do either steps a through c or steps d through g.

       If your NS3000/V node had only an NMCONFIG file (but no NSCONF
       files), follow the instructions in steps a through c.

          a.  To convert the NMCONFIG file enter the file name:
              NMCONFIG.PUB.SYS.

          b.  Enter Y to proceed when prompted.

          c.  Select type 2 for NMCONFIG type file.  The converted file
              will be saved with the file name you entered.  In this case
              it is NMCONFIG.PUB.SYS. This is the only filename that the
              node will recognize as its configuration file.

              If your NS3000/V node had one or more NSCONF files, follow
              the instructions in steps d through g.   

          d.  Merge your NS3000/V NSCONF file with the NS3000/V NMCONFIG
              file, and convert it for use with NS3000/iX release 2.0
              or later by entering a file name, for example:
              NSCONF1.PUB.SYS.

          e.  Enter Y to proceed when prompted.

          f.  Select type 1 for NSCONF type file.  NMMGRVER will merge
              the contents of the existing NMCONFIG file with the NSCONF
              file you specified.  It will be saved in the NSCONF file
              you specified.  In this example, NSCONF1.

          g.  If you converted more than one NSCONF file, decide which
              one will be the network configuration you want on the
              NS3000/iX system.  Rename the file to NMCONFIG.PUB.SYS.

To Update X.25 XL System Access Parameters 

On the NS3000/iX host, use NMMGR to change the following parameters to
provide X.25 XL System Access:

   1.  If migrating from any NS3000/V release before release V delta 7,
       modify the screen at path @NETXPORT.NI.niname.PROTOCOL.X25 to
       change the inactivity timer from minutes to seconds.

   2.  On the screen with the path @LINK, verify that the DTSLINK is
       defined.

   3.  On the screen with the path @LINK.DTSLINK, verify that the
       physical path is correctly defined.

   4.  On the screen with the path @LINK, add the LINK name and Type
       (X25) of the X25 link.  Note:  to migrate to NS3000/iX release 2.2 
       or later, repeat this step and steps 5 through 7 for each DTC/X.25 
       Network Access card. 

   5.  On the screen with the path @LINK.linkname, where the LINK name is
       the one added in the previous step, add the DTC Node name and card
       number for the DTC/X.25 Network Access card.

   6.  On the screen with the path @NETXPORT.NI.niname.LINK, add the LINK
       name entered in Step 4.

   7.  On the screen with the path @NETXPORT.NI.niname.LINK.linkname,
       answer yes or no; then, press the Update key.

To Save X.25 XL System Access Parameters on the Host 

Make a list of the following X.25 XL System Access Parameters on the host
that must be re-entered on the DTC.

   *   Local Node Name.

   *   Link Name (the X25 link, not the DTSLINK).

   *   DTC Node Name.

   *   DTC Card Number.

   *   X.25 User Facility Set Parameters.

To Add Other Link Types As Needed 

For LAN and point-to-point link types, run NMMGR and add the physical
paths.  See sections of this manual for the correct values to be entered
for the physical path.

To Verify DTS Configuration on the Host 

If the datacommunications and terminal subsystem (DTS) has not been
configured, configure the DTS parameters on the host according to the
requirements of your network.  For more information, refer toGetting 
Started with the DTC and Configuring Systems for Terminals, Printers, and 
Other Serial Devices if you are using PC-based network management.  Refer
to Configuring and Managing Host-Based X.25 Links if you are using
host-based network management.



MPE/iX 5.0 Documentation