IPX/SPX Configuration and Management Manual

Configuration Quick Start

IPX/SPX Configuration and Management Manual—425731-001

1-4

Task 2: Install and Configure NonStop™ IPX/SPX

1. Install the physical connection between the NonStop™ Himalaya S-series server and

the NetWare LAN, if it does not already exist. For an Ethernet LAN, you must have

an Ethernet 4 ServerNet adapter (E4SA) on the system for each physical connection

to a NetWare network. For a token-ring LAN, you must have a Token-Ring

ServerNet adapter (TRSA) on the system for each physical connection to a NetWare

network. For more information on installing the ServerNet adapters, see the

Ethernet Adapter Installation and Support Guide for an Ethernet LAN, or the Token-

Ring Adapter Installation and Support Guide for a token-ring LAN.

2. Install the supplied software. See the DSM/SCM User’s Guide and the Gnn.nn

Software Installation and Upgrade Guide for details on software installation. Verify

that the following files are installed:

•

IPXMGR and IPXPROTO in $SYSTEM.ZIPXPRO

IPXMGR is the program file for the manager process of the NonStop™ IPX/SPX

subsystem. It processes incoming management requests and routes each request

to the proper IPXPROTO process.

IPXPROTO is the program file for the NonStop™ IPX/SPX protocol process.

These protocol processes communicate with NetWare clients or servers. You can

configure multiple IPXPROTO processes, limited only by the number of LAN

filters supported on the system.

•

ZIPXSCF and ZIPXTEXT in $SYSTEM.SYSTEM

ZIPXSCF is the NonStop™ IPX/SPX SCF object file.

ZIPXTEXT is the NonStop™ IPX/SPX SCF error and help data file.

•

ZIPXTMPL in $SYSTEM.ZTEMPL

ZIPXTMPL is the SPI definitions template object file.

3. Start the IPX Manager (IPXMGR) as either a generic process or a TACL process:

•

Starting IPXMGR as a generic process:

You can start the IPX Manager as a generic process configured as a process pair.

This is done by entering an SCF ADD command that specifies attributes to

customize the process. Entering a START command causes the $ZPM

persistence manager to start and maintain the process. After it is started, its

persistence is managed by the Kernel subsystem; hence, generic processes are

sometimes called system-managed processes.

Note. Before you begin installing the NonStop™ IPX/SPX subsystem, you should initiate the

Event Management Service (EMS) Printing Distributor to display events that may be generated

during installation. (See the EMSDIST utility program in the EMS Reference Summary.)