NS X.25 Migration: NS 3000/V to NS 3000/iX

Differences Between NS 3000/V and NS 3000/iX

Differences Between NS 3000/V and NS 3000/iX

The following paragraphs summarize differences between NS 3000/V and NS 3000/iX. Make sure that you account for these differences that could affect your network when migrating to NS 3000/iX. For information on operating system migration, refer to the MPE/iX Migration series.

Hardware

Some NS 3000/V hardware components are not part of an NS 3000/iX network, such as the ATP for terminal connections, and the INP for network links.

On an NS 3000/iX network, the DTC provides connections for local or remote terminals and serial printers. The DTC also provides MPE/iX access to X.25 through a DTC/X.25 Network Access card. The Datacommunications and Terminal Subsystem (DTS) LANIC on the MPE/iX host is used for system-to-system X.25 connectivity.

Unsupported Network Connections

Before migrating your network, identify any unsupported network connections. The network connections that are not supported on NS 3000/iX networks are as follows:

Manual-dial modems.

Asynchronous SERIAL Network Link and bisynchronous link-level protocol. To ease migration, you can convert Asynchronous SERIAL network links to the NS 3000/V Point-to-Point links which can be converted to NS 3000/iX. Point-to-Point links use the LAP-B protocol.

Connections to DS/3000 nodes. DS network services are not supported on NS 3000/iX. If DS/3000 nodes are part of an existing network, either migrate them to NS 3000/V or maintain NS 3000/V connections to the DS/3000 nodes.

Configuration of Terminals and Printers

On NS 3000/V networks, the SYSDUMP program is used to perform I/O configuration which includes configuring terminals, printers, and other I/O devices and drivers. On NS 3000/iX, terminals and serial printers are configured on the host (using NMMGR) and on the OpenView Windows Workstation (using the OpenView DTC Manager software). For more information on configuration using your OpenView Windows Workstation, read Using the OpenView DTC Manager.

202

Appendix B