Migrating from NS 3000/V PAD Access to NS 3000/iX
MPE documents | |
 Complete PDF | |
| Table of Contents | |
| Index |
Make sure you have accounted for the differences that could affect your network as described in the previous sections of this appendix.
Make a list of the NS 3000/V PAD data that must be re-entered for the DTC. Refer to the section in this appendix called "To Save NS 3000/V PAD Parameters."
Using Host-Based Network Management
Use NMMGR to configure DTS parameters on the host.
Complete PAD configuration using NMMGR. For complete information on this, see Configuring and Managing Host-Based X.25 Links.
Remove PAD terminals from the NS 3000/V network directory.
Using PC-Based Network Management
Use NMMGR to configure DTS parameters on the host. For complete information on this, read Configuring Systems for Terminals, Printers, an Other Serial Devices.
Make a list of the DTS parameters configured on the host that must also be entered into the OpenView DTC Manager. Refer to the section in this appendix called "To Save DTS Parameters on the Host."
Configure the DTC by using the OpenView DTC Manager at your OpenView Windows Workstation.
Remove PAD terminals from the NS 3000/V network directory.
Saving NS 3000/V PAD Parameters
Make a list of the following NS 3000/V parameters that must be re-entered on the DTC:
PAD device X.25 addresses fro the NS 3000/V screen with the path: @NETXPORT.NI.niname.PROTOCOL.X25.SVCPATH
L.U.G. Inbound Address from the NS 3000/V screen with the path: @NETXPORT.NI.niname.PROTOCOL.LUGSPEC.INLUG
L.U.G. Outbound Address from the NS 3000/V screen with the path: @NETXPORT.NI.niname.PROTOCOL.X25.LUGSPEC. OUTLUG
PAD Access Migration Categories
The way you assign a PAD device depends on what the device is and how it will be used. Asynchronous devices attached to DTCs can either be configured with nailed or non-nailed logical device numbers on each of the MPE/iX host systems to which they have access. The following subsections describe the characteristics of nailed and non-nailed devices.
Non-Nailed Devices
A non-nailed device is a session-accepting device that is not permanently associated with an ldev number at configuration time. When the user at such a device logs on to an MPE/iX system, an ldev is assigned from a pool of ldevs set aside for this purpose at configuration time. The device characteristics of the PAD devices must match the non-nailed PAD terminal profile. The association between a non-nailed device and the assigned ldev exists only for the duration of the session. One advantage of the use of non-nailed device connections is that configuration is simplified, since it is not required that each non-nailed device be individually configured. The host cannot make an outbound call to a non-nailed device.Nailed Devices
A nailed device is one with a permanently assigned ldev. The assignment is configured on the MPE/iX host system. Nailed devices can be accessed programmatically through their ldev number. There is an ldev-to-25-address mapping. The host can support both inbound and outbound calls.Configuration of Nailed Versus Non-Nailed Devices
Following are some points to remember when configuring nailed and non-nailed PAD devices:Printer must be nailed.
Terminals may be nailed or non-nailed.
Programmatic access requires a nailed device.
Logon access may be either nailed or non-nailed.
Saving DTS Parameters
Make a list of the following DTS parameters configured n the host that must also be entered into the OpenView DTC Manager.
Local Node Name.
PAD Device Name.
PAD Device Type.
DTC Node Name.
DTC Card Number.
Configuring the DTC
If you are using PC-based network management, configure the DTC by using the OpenView DTC Manager at your OpenView Windows Workstation. For full details, see Using the OpenView DTC Manager. If you are using host-based network management, configure the DTC using NMMGR. For full details, see Configuring and Managing Host-Based X.25 Links.
|
PAD Support: NS 3000/V and NS 3000/iX |
Appendix D PCI 10/100Base-TX/3000 Quick Installation |