IPX/SPX Configuration and Management Manual Abstract This manual describes the installation, configuration, management, and operation of the Compaq NonStop™ IPX/SPX subsystem. It includes an overview of Novell NetWare. This manual is for system managers and operators who need to install, configure, and manage the NonStop™ IPX/SPX subsystem. Product Version NonStop™ IPX/SPX G06 Supported Releases This manual supports G06 and all subsequent G-series releases until otherwise indicated in a new edition.
Document History Part Number Product Version Published 118608 NonStop™ IPX/SPX D40 NonStop™ IPX/SPX D40 NonStop™ IPX/SPX F40 NonStop™ IPX/SPX G05 NonStop™ IPX/SPX G06 NonStop™ IPX/SPX G06 December 1995 132181 139952 140944 425731-001 May 1997 February 1998 May 1998 May 2000 Ordering Information For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact your local sales representative.
IPX/SPX Configuration and Management Manual Glossary Index Figures Tables What’s New in This Manual ix Manual Information ix New and Changed Information ix About This Manual xi Who Should Use This Manual xi How This Manual Is Organized Related Manuals xi xii Your Comments Invited xvi Notation Conventions xvi Abbreviations xx 1.
3.
4.
A.
B. Event Messages for NonStop™ IPX/SPX Contents Other Services A-9 6530 Terminal Services A-9 Information Xchange Facility (IXF) File Transfer NetWare Print Services A-10 Fault-Tolerant Subsystem Operations A-11 A-12 IPXPROTO Process IPXMGR Process A-10 A-12 IPX Sockets A-12 SPX Sockets A-12 Examples of NonStop™ IPX/SPX Functions A-13 B.
D.
Glossary Contents IPXSPX 00012 D-9 IPXSPX 00018 D-10 IPXSPX 00019 D-10 IPXSPX 00020 D-10 Glossary Index Figures Figure i. Related Manuals for NonStop™ Himalaya S-Series Servers xii Figure ii. TSM Manuals and Online Help Figure 2-1. NonStop™ IPX/SPX Client–Server Environment Figure 2-2. NetWare LAN Components Figure 2-3. NonStop™ IPX/SPX Subsystem Figure 2-4. NonStop™ IPX/SPX Applications and Interfaces 2-6 Figure 2-5. 6530 Terminal Services for Workstations Figure 2-6.
Tables Contents Tables Table i. Manual Contents xi Table 1-1. Frame Types and Filter Protocols for Ethernet and Token-Ring LANs 1-2 Table 1-2. IPXPROTO Default Values Table 2-1. Frame Types and Filter Protocols for Ethernet and Token-Ring LANs 2-9 Table 3-1. Frame Types and Filter Protocols for Ethernet and Token-Ring LANs 3-9 Table 3-2. SCF Command Overview Table 3-3. NonStop™ IPX/SPX SCF Commands and Object Types Table 3-4. Well-Known Server Types Table 3-5.
What’s New in This Manual Manual Information IPX/SPX Configuration and Management Manual Abstract This manual describes the installation, configuration, management, and operation of the Compaq NonStop™ IPX/SPX subsystem. It includes an overview of Novell NetWare. This manual is for system managers and operators who need to install, configure, and manage the NonStop™ IPX/SPX subsystem.
What’s New in This Manual • • • • • • • • • • New and Changed Information In Section 1, changed the names and locations of some of the NonStop™ IPX/SPX files that are installed. See item 2 under Task 2: Install and Configure NonStop™ IPX/SPX on page 1-4. Changed the format for LAN and token-ring LIF names from LANxx and TOKxx format to L0xx. See Section 1, Configuration Quick Start and Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF).
About This Manual This manual describes the installation, configuration, management, and operation of the Compaq NonStop™ IPX/SPX subsystem. It includes an overview of Novell NetWare and NonStop™ IPX/SPX subsystem components and concepts. This manual describes the G06 release of NonStop™ IPX/SPX. Who Should Use This Manual This manual is intended for experienced NonStop™ Himalaya S-series server managers and operators who need to install, configure, and manage the NonStop™ IPX/SPX subsystem.
Related Manuals About This Manual Table i. Manual Contents (page 2 of 2) Section and Title Description Appendix B, Event Messages for NonStop™ IPX/SPX Explains how to access event messages reported by the NonStop™ IPX/SPX subsystem, gives a description of each event message, and provides examples of filters. Appendix C, SCF Command Syntax for NonStop™ IPX/SPX Provides a quick reference for SCF command syntax.
Related Manuals About This Manual Description of Prerequisite Manuals • Himalaya S-Series Planning and Configuration Guide This manual describes how to plan and configure a NonStop™ Himalaya S-series server and provides a case study documenting a sample system.
TSM Manuals and Online Help About This Manual • TCP/IP and IPX/SPX Programming Manual This manual describes how to develop sockets applications for the NonStop™ TCP/IP and NonStop™ IPX/SPX data communications subsystems. TSM Manuals and Online Help TSM manuals and online help provide information on using the Compaq Tandem Service Management (TSM) package, which is used to bring up and maintain NonStop™ Himalaya S-series servers. Figure ii shows the TSM manuals and online help. Figure ii.
TSM Manuals and Online Help About This Manual who are responsible for planning and configuring a NonStop™ Himalaya S-series server and system console for TSM operations. • TSM Online User Guide This hypertext online guide describes how to use the TSM client software package on a workstation. It describes how to perform tasks using the TSM application and contains information on TSM concepts, commands, and dialog boxes.
Your Comments Invited About This Manual Your Comments Invited After using this manual, please take a moment to send us your comments. You can do this by returning a Reader Comment Card or by sending an Internet mail message. A Reader Comment Card is located at the back of printed manuals and as a separate file on the Compaq User Documentation disc. You can either fax or mail the card to us. The fax number and mailing address are provided on the card.
General Syntax Notation About This Manual { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line.
Notation for Messages About This Manual !i and !o. In procedure calls, the !i notation follows an input parameter (one that passes data to the called procedure); the !o notation follows an output parameter (one that returns data to the calling program). For example: CALL CHECKRESIZESEGMENT ( segment-id , error ) ; !i !o !i,o. In procedure calls, the !i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program).
Notation for Management Programming Interfaces About This Manual { } Braces. A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed. The items in the list might be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LBU { X | Y } POWER FAIL process-name State changed from old-objstate to objstate { Operator Request.
Abbreviations About This Manual Abbreviations The following list defines abbreviations used in this manual and in other NonStop™ IPX/SPX manuals. Both industry-standard terms and NonStop™ Himalaya S-series terms are included. Not all of the terms shown here are used in this particular manual. API. application program interface BSD. Berkeley Software Distribution CLI. command language interface DDE. Dynamic Data Exchange DDL. Data Definition Language DLL. Dynamic Link Library DSC.
Abbreviations About This Manual ODBC. Open Database Connectivity PCT. PC6530 Terminal Emulator POET. Pathway Open Environment Toolkit QIO. Queued Input/Output RIP. Routing Information Protocol RSC. Remote Server Call SAC. ServerNet addressable controller SAP. Service Advertising Protocol SCF. Subsystem Control Facility SCP. Subsystem Control Point SMB. Server Message Block SNAP. Subnetwork Access Protocol SPI. Subsystem Programmatic Interface SPX. Sequenced Packet Exchange SQL.
Abbreviations About This Manual IPX/SPX Configuration and Management Manual—425731-001 xxii
1 Configuration Quick Start This section outlines the basic tasks you perform to install and configure the Compaq NonStop™ IPX/SPX subsystem. For an overview of Novell NetWare LAN and NonStop™ IPX/SPX architecture, see Section 2, Introduction to NonStop™ IPX/SPX.
Task 1: Plan Your Configuration Configuration Quick Start 3. What frame type does your NetWare LAN use? NonStop™ IPX/SPX supports the major frame types used on Ethernet and tokenring LANs. Each frame type has a corresponding filter protocol. A number of SCF commands require you to specify an IOPORTNAME value. IOPORTNAME takes the form LIF-name.filter-protocol. LIF-name indicates the name of the logical interface (LIF). An Ethernet or tokenring LIF name usually takes the form L0xx.
Task 1: Plan Your Configuration Configuration Quick Start Note. NonStop™ IPX/SPX supports both Ethernet or token-ring LANs. An Ethernet or tokenring LIF name usually takes the form L0xx. You can use the SCF INFO LIF command (with or without the DETAIL option) to verify the LIF type. You can change the LIF names, but we recommend that you do so only if you understand the system very well. To select a LIF, use the STATUS LIF command with the DETAIL option: ->STATUS LIF $ZZLAN.
Configuration Quick Start Task 2: Install and Configure NonStop™ IPX/SPX Task 2: Install and Configure NonStop™ IPX/SPX 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.) 1.
Task 2: Install and Configure NonStop™ IPX/SPX Configuration Quick Start The following example starts the IPX Manager with the same attributes as the TACL process (described next) but the persistence value of 5 causes it to be automatically restarted if the process is aborted abnormally. >SCF ->ADD PROCESS $ZZKRN.#ZMGR,& NAME $ZMGR,& PROGRAM $SYSTEM.ZIPXPRO.IPXMGR,& PRIMARYCPU 0,& BACKUPCPU 1,& INFILE $TERM.#T1,& OUTFILE $TERM.#T1,& HOMETERM $TERM.
Task 2: Install and Configure NonStop™ IPX/SPX Configuration Quick Start 5. Ensure that there is at least one NetWare file server running on the network. 6. Create and start the IPXPROTO process by either using SCF or using a TACL RUN command: • Starting IPXPROTO by using SCF: Start SCF and create and start the IPXPROTO process. a. Enter SCF at the TACL prompt: >SCF b. Enter the following commands to create and start the IPXPROTO process (in this example, $ZNV2) on the LIF.
Task 2: Install and Configure NonStop™ IPX/SPX Configuration Quick Start Table 1-2.
Task 3: Configure the NonStop™ Server for NetWare Users Configuration Quick Start Task 3: Configure the NonStop™ Server for NetWare Users 1. Configure user IDs and passwords for the workstations on the NetWare LAN that will be accessing the NonStop™ host. 2. Configure the services on the system that will be available to workstations on the NetWare LAN. (These services are described in Appendix A, Protocol Interfaces and Services for NonStop™ IPX/SPX.
Task 3: Configure the NonStop™ Server for NetWare Users Configuration Quick Start For more information on installing and configuring the Telserv software, refer to the Telserv Guide. • For LAN Print Spooler for NetWare: 1. Configure a user ID on the NetWare file server for the LAN Print Spooler for NetWare process. 2. Define NetWare print server queues and print attributes in your FASTCNFG spooler configuration file.
Configuration Quick Start Task 3: Configure the NonStop™ Server for NetWare Users IPX/SPX Configuration and Management Manual—425731-001 1- 10
2 Introduction to NonStop™ IPX/SPX The NonStop™ IPX/SPX subsystem allows a NonStop™ system to function as a faulttolerant database or transaction server on a Novell NetWare local area network (LAN). NonStop™ IPX/SPX provides connectivity to the NetWare LAN through an implementation of Novell’s proprietary protocol suite, Internetwork Packet Exchange/Sequenced Packet Exchange (IPX/SPX), over Ethernet or token-ring.
Introduction to NonStop™ IPX/SPX Overview of the NetWare LAN Overview of the NetWare LAN This section describes some of the basic features of the NetWare LAN environment. Local area networks (LANs) link individual workstations to allow them to share resources. A resource can be local to the workstation, such as a printer or disk drive; or a resource can be remote, such as a directory or a file on a server. The network operating system (NOS) manages users’ access to resources on the LAN.
Overview of the NetWare LAN Introduction to NonStop™ IPX/SPX Figure 2-2 shows the components of a NetWare LAN. Figure 2-2. NetWare LAN Components NetWare File Server Server Service NOS Software Client NetWare NOS Operating System Router Application Requestor Operating System Client Client CDT 004.CDD Each workstation on the LAN contains both driver software and a network interface card (NIC).
NonStop™ IPX/SPX Subsystem Architecture Introduction to NonStop™ IPX/SPX NonStop™ IPX/SPX Subsystem Architecture NonStop™ IPX/SPX runs on the NonStop™ Kernel operating system. Figure 2-3 shows a high-level view of the NonStop™ IPX/SPX subsystem and its relationship to the NetWare LAN. Figure 2-3.
Introduction to NonStop™ IPX/SPX IPX Protocol (IPXPROTO) Process IPX Protocol (IPXPROTO) Process NonStop™ Himalaya S-series applications that use the NonStop™ IPX/SPX subsystem must specify the name of the IPXPROTO process that is to be used for communicating with NetWare clients or servers. You can configure multiple IPXPROTO processes on the NonStop™ Himalaya S-series server. The maximum number of IPXPROTO processes you can have is limited only by the number of LAN filters supported on the system.
Programming Interfaces Introduction to NonStop™ IPX/SPX Figure 2-4 shows the relationships among the NonStop™ IPX/SPX applications and interfaces. Figure 2-4.
Introduction to NonStop™ IPX/SPX Service Advertising Protocol (SAP) Interface Service Advertising Protocol (SAP) Interface The SAP interface allows a NonStop™ server application to advertise its services to workstations on the NetWare LAN. Service nodes—such as file, print, and database servers—register their services and addresses in the SAP table. Each IPXPROTO process maintains a copy of the SAP table on the operating system and broadcasts SAP entries to other NetWare servers.
Introduction to NonStop™ IPX/SPX Distributed Systems Management (DSM) Interfaces Application processes request that the NonStop™ IPX/SPX software create a socket when needed. The NonStop™ IPX/SPX software returns a socket number that the application uses to refer to the new socket. The application then (optionally) binds the socket to a specific local address (the IPX or SPX socket) and sends or receives data on the socket.
Frame Types Introduction to NonStop™ IPX/SPX Frame Types NonStop™ IPX/SPX supports the four frame types used on Ethernet and token-ring LANs, as shown in Table 2-1. Table 2-1. Frame Types and Filter Protocols for Ethernet and Token-Ring LANs Frame Type Filter Protocol LAN Type Ethernet II (IEEE 802.3) ipxeth Ethernet only Logical Link Control (IEEE 802.2) ipx8022 Ethernet or token-ring IPX 802.3 (Raw 802.
Introduction to NonStop™ IPX/SPX Routing Information Protocol (RIP) On the client, NCP is called the NetWare shell or, more commonly, the requestor. Using NCP, the client sends a request to the NetWare file server. The server processes the request and sends a reply to the client. The client can have only one request outstanding at a time; it must wait for a response from the file server before sending another request.
6530 Terminal Services Introduction to NonStop™ IPX/SPX 6530 Terminal Services Compaq terminal emulators allow DOS-based or Windows-based workstations on a NetWare LAN to emulate Compaq 6530 terminals when connected to an operating system running NonStop™ IPX/SPX. Compaq provides the following terminal emulator software for the NetWare workstations: • • PC6530 Terminal Emulator (PCT) for MS-DOS workstations. Outside View with Compaq Tandem Terminal Emulator (TTE) for Microsoft Windows workstations.
File-Transfer Services Introduction to NonStop™ IPX/SPX File-Transfer Services The PC6530 Terminal Emulator (PCT) and Outside View with Tandem Terminal Emulator (TTE) programs also allow the transfer of files between operating systems and workstations on a NetWare LAN. On the NonStop™ Himalaya S-series server, the Information Xchange Facility (IXF) provides file-transfer support using Telserv and NonStop™ IPX/SPX, as illustrated in Figure 2-6.
Remote Server Call (RSC) Services Introduction to NonStop™ IPX/SPX Figure 2-7. RSC for Workstations POET DDE Gateway NonStop TM TS/MP NonStop TM Himalaya S-Series Server PC (Windows) RSC Application TDP RSC API NonStop TM IPX/SPX NonStop TM IPX/SPX CDT 007.CDD NetWare LAN (Ethernet or Token-Ring) RSC allows you, as a NetWare workstation user, to access TS/MP on the operating system. Clients (requestors) send transaction messages to the Pathway servers.
NonStop™ Open Database Connectivity (ODBC) Server Services Introduction to NonStop™ IPX/SPX NonStop™ Open Database Connectivity (ODBC) Server Services Open Database Connectivity (ODBC) is an industry-standard interface for database access. NonStop™ IPX/SPX allows workstation clients running Microsoft ODBC or Sybase DBLIB applications to access data stored in NonStop™ Structured Query Language (SQL) databases through the ODBC Server, as shown in Figure 2-8. Figure 2-8.
NetWare Print Services Introduction to NonStop™ IPX/SPX NetWare Print Services When you use a NonStop™ Himalaya S-series application, NonStop™ IPX/SPX allows you to use the Compaq Spooler subsystem to print jobs on a NetWare printer. This feature allows you to send files or jobs from operating systems to printers located on a NetWare LAN, as illustrated in Figure 2-9. Figure 2-9.
Introduction to NonStop™ IPX/SPX NetWare and NonStop™ System Requirements NetWare and NonStop™ System Requirements The remainder of this section describes the minimum Novell NetWare and NonStop™ system requirements for the NonStop™ IPX/SPX subsystem. For information on configuring NonStop™ IPX/SPX, see Section 1, Configuration Quick Start. NetWare Environment NonStop™ IPX/SPX is based on the Novell NetWare version 3.11 software. Only Ethernet or token-ring connections to a NetWare LAN are supported.
Introduction to NonStop™ IPX/SPX • • Operating System Environment ServerNet LAN systems access (SLSA) subsystem. Event Management Service (EMS). Before you install NonStop™ IPX/SPX, you should initiate the EMS Printing Distributor to display events that may be generated during installation. (See the EMSDIST utility program in the EMS Reference Summary.) The Compaq Tandem Failure Data System (TFDS) software is recommended but is not required (see the Tandem Failure Data System (TFDS) Manual).
Introduction to NonStop™ IPX/SPX Operating System Environment IPX/SPX Configuration and Management Manual—425731-001 2- 18
3 Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) You manage the NonStop™ IPX/SPX subsystem by using Subsystem Control Facility (SCF) commands to control the operation of subsystem objects. This section describes the NonStop™ IPX/SPX subsystem management interfaces, objects, and SCF commands. The latter part of the section describes routine management tasks.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) Subsystem Control Facility (SCF) Interface Figure 3-1 shows the SCF, SCP, and EMS management interfaces to NonStop™ IPX/SPX. Figure 3-1. NonStop™ IPX/SPX Management Interfaces EMS Distributor SCF EMS Collector Log File EMS Collector NonStop TM IPX/SPX SCP CDT 014.CDD Subsystem Control Facility (SCF) Interface SCF provides an interface for interactively managing NonStop™ Himalaya S-series data communications subsystems.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) Objects Objects To configure the NonStop™ IPX/SPX environment, you must understand the structure and hierarchy of the objects in the NonStop™ IPX/SPX subsystem. Each object has an object type, an object name, attributes, and operational (summary) states associated with it. NonStop™ IPX/SPX also supports object-name templates, which allow you to specify commands by using wildcards. (See Object-Name Templates and Wildcards on page 3-6.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) Object Attributes There can be multiple IPXPROTO processes on a NonStop™ Himalaya S-series server. You create each IPXPROTO process with either an SCF ADD PROCESS or a TACL RUN command. (See ADD PROCESS on page 3-13 or Starting an IPXPROTO process with a TACL RUN command: on page 1-6.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) Summary States State Transition Diagram The valid summary states for the PROCESS object are ABORTING, STARTED, STARTING, STOPPED, and STOPPING. Figure 3-3 shows the state-transition diagram for the PROCESS object. Once defined, the process enters the STOPPED state, in which the process is quiescent and nonoperational (use the START command to make the PROCESS object fully operational).
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) Object-Name Templates and Wildcards Object-Name Templates and Wildcards Normally, an SCF command line must include an object type and an object name. However, for some commands, the NonStop™ IPX/SPX subsystem accepts object-name templates. In an object-name template, you can use one object name to cause multiple objects of a given type to respond to a single command.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) Entering SCF Commands Entering SCF Commands You start SCF interactively by issuing the following command at the TACL prompt: 1>SCF You rarely need to specify SCF RUN parameters because the default values are appropriate for most situations. For a more detailed description of the TACL RUN command parameters that apply to SCF, refer to the SCF Reference Manual for G-Series Releases.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) Sensitive and Nonsensitive SCF Commands You cannot enter more than 2048 characters for any input command. Note. SCF accepts input from either a terminal or a disk (OBEY) file and directs output to a terminal, disk file, or printer. However, in this manual, all examples assume that you use a terminal for both input and output. Sensitive and Nonsensitive SCF Commands SCF commands are either sensitive or nonsensitive.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) • • SCF Command Descriptions The process name. Each process must be a Guardian-named process. The recommended form is $ZNVn, where n is an alphanumeric character. The IOPORTNAME, in the form LIF-name.filter-protocol. ° LIF-name displays the name of the logical interface (LIF). An Ethernet or token-ring LIF name usually takes the form L0xx.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) SCF Command Descriptions Table 3-2.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) ABORT Command Table 3-3. NonStop™ IPX/SPX SCF Commands and Object Types (page 2 of 2) Object Types NonStop™ IPX/SPX SCF Command Sensitive Command PROCESS SERVER (SAP) STOP Command on page 3-45 Yes X X* TRACE Command on page 3-47 Yes X X VERSION Command on page 3-52 No X X SUBSYS * Indicates that the SUB modifier must be used. ** STATS is sensitive when used with the RESET option.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) ABORT Command Example The following command aborts a process named $ZNV2: -> ABORT PROCESS $ZNV2 ABORT SUBSYS ABORT SUBSYS terminates the operation of an IPXPROTO process as quickly as possible. You must specify the SUB option when using the SUBSYS object.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) ADD Command Considerations • • • • • • • • The object-name template (wildcard notation) is supported for the ABORT command. (See Object-Name Templates and Wildcards on page 3-6.) All activities being performed by the specified objects are stopped immediately. Files may be left in an inconsistent or incomplete state. To reinitiate the operation of an aborted process, use the START command.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) ADD Command OUT file-spec directs any SCF output generated for this command to the specified file. file-spec must be a partially or fully qualified name. If you do not specify this option, the output goes to the home terminal. PROCESS $manager-name.$process-name is the fully qualified process name indicating the desired NonStop™ IPX/SPX process. When you first add the process, you must include the IPXMGR process name.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) ADD Command unresponsive SPX connection is disconnected after the fifth ping. The default is five minutes. For example, if SPXKEEPALIVETIMER is set to 7, SPX sends up to five pings at one-minute intervals if an SPX connection has not received a packet for seven minutes. SPXMAXBINDS integer is the number of concurrent, explicit binds to this particular IPXPROTO process.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) ALTER Command Considerations • • • When the ADD command is completed, the process is defined to the NonStop™ IPX/SPX subsystem and placed in the STOPPED summary state. To initiate the operation of the object, use the START PROCESS command. Use the STATUS PROCESS command to check the status of the new process. If the process you are trying to define already exists in the subsystem, an error is returned.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) ALTER Command IOPORTNAME LIF-name.filter-protocol LIF-name displays the name of the logical interface (LIF). An Ethernet or tokenring LIF name usually takes the form L0xx. filter-protocol displays the filter protocol name that supports the frame type of the NetWare network. Table 3-1 on page 3-9 lists each frame type and corresponding filter protocol along with the LAN type they support.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) DELETE Command SPXMAXCONN integer is the number of SPX connections allowed open simultaneously. The recommended value is the maximum number of concurrent SPX user sessions, including sessions established by higher-level protocols, such as Telserv, Remote Server Call (RSC), and Open Database Connectivity (ODBC). SPXMAXRESEND integer specifies the maximum number of times that SPX resends a data packet.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) DELETE Command PROCESS process-name is a valid process name indicating the desired IPXPROTO process. Example The following command deletes a process named $ZNV2: -> DELETE PROCESS $ZNV2 DELETE SUBSYS DELETE SUBSYS removes IPXPROTO processes from the NonStop™ IPX/SPX subsystem. You can delete only processes in the STOPPED summary state. Specify the SUB option when using the SUBSYS object.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) INFO Command Example The following command deletes processes subordinate to a subsystem named $ZMGR: -> DELETE SUBSYS $ZMGR, SUB ONLY Considerations • • • The object-name template (wildcard notation) is supported. (See Object-Name Templates and Wildcards on page 3-6.) Before you can delete an object, it must be in the STOPPED summary state. You can remove an IPXPROTO process from the system only with the DELETE PROCESS command.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) INFO Command INFO PROCESS Display Format The format of the display for the INFO PROCESS command without the DETAIL option is: -> INFO PROCESS $ZNV2 IPXSPX Info PROCESS Process Name $ZNV2 Primary CPU 2 Backup CPU 3 *I/O Port Name L018 IPXETH I/O Port Type ETHERNET Process Name displays the name of the IPXPROTO process for which the statistics are displayed.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) INFO Command INFO PROCESS Display Format With DETAIL -> INFO PROCESS $ZNV2, DETAIL IPXSPX Detailed Info PROCESS \IDC14.$ZNV2 Program File Name \IDC14.$SYSTEM.ZIPXPRO.IPXPROTO *I/O Port Name L018 IPX8023 QIO Lib...................N/A Primary CPU ............ 1 Backup CPU.............0 I/O Port Address ........%H0000 %H00FF I/O Port Type .........802.3 *IPX Max Sockets ........ 50 *QIO Limit (%)..........0 *SPX Max Binds ..........
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) INFO Command IPX Max Sockets is the maximum number of IPX sockets allowed open simultaneously. Use the STATS PROCESS command to check the current number of IPX opens. (Check the Open Sockets Count field in the IPX Layer display.) IPX Max Sockets is the value specified in the ADD or ALTER command parameter IPXMAXSOCKETS. SPX Max Binds displays the maximum number of concurrent explicit binds to this IPXPROTO process.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) INFO Command INFO SUBSYS INFO SUBSYS displays the current attribute values for the IPXMGR process. Command Syntax INFO [ / OUT file-spec / ] SUBSYS subsystem-name [ , DETAIL ] [ , SUB { ONLY | ALL | NONE | obj-type } ] OUT file-spec directs any SCF output generated for this command to the specified file. file-spec must be a partially or fully qualified name. If you do not specify this option, the output goes to the home terminal.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) INFO Command -> INFO SUBSYS $ZMGR IPXSPX Info SUBSYS Primary CPU 0 Backup CPU 1 Primary CPU displays the number of the processor in which the primary IPXPROTO process is running. The primary IPXPROTO process always runs in the same processor as the primary processor for the ServerNet Addressable Controller (SAC). Backup CPU displays the number of the processor in which the backup IPXPROTO process is running.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) LISTOPENS Command Mem Swapvol displays the name of the disk used for swapping of extended memory. Program File Name displays the fully qualified name of the program object file (that is, the codefile) that creates this IPXMGR process. Program File Mod displays the date and timestamp on which the codefile that created this IPXMGR process was last modified.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) LISTOPENS Command -> LISTOPENS PROCESS $ZNV0 IPXSPX Listopens PROCESS Openers \MFG.$ZMGR Primary CPU 2 Primary PIN 46 Backup CPU N/A Backup PIN N/A Openers displays the fully qualified process name of the opener. In this case, $ZNV0 is opened by the IPXMGR process, $ZMGR. Primary CPU displays the number of the processor in which the primary opener process is running.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) LISTOPENS Command SUB obj-type selects the subordinate objects the command affects. obj-type can be a subordinate object type or one of the keywords ONLY, ALL, or NONE. • • • • A subordinate object type causes the command to affect only objects of that type. ONLY causes the command to affect the subordinate objects. ALL causes the command to affect the named object and subordinate objects.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) NAMES Command Considerations • • • • The object-name template (wildcard notation) is supported for the LISTOPENS command. (See Object-Name Templates and Wildcards on page 3-6.) The object must be in the STARTED summary state in order to return opener information. LISTOPENS is a nonsensitive command. (See Sensitive and Nonsensitive SCF Commands on page 3-8.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) NAMES Command -> NAMES PROCESS $ZNV* IPXSPX Names PROCESS \HIMA.$ZNV0 PROCESS $ZNV0 SERVER $ZNV0.#SAP IPXSPX Names PROCESS \HIMA.$ZNV1 PROCESS $ZNV1 SERVER $ZNV1.#SAP NAMES SUBSYS NAMES SUBSYS displays a list of all object types and names defined by or known to the NonStop™ IPX/SPX subsystem.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) • START Command NONE specifies that the named object is displayed but none of the subordinate objects is displayed. If you omit obj-type, ALL is assumed. NAMES SUBSYS Display Format The format of the display for the NAMES SUBSYS command is: -> NAMES SUBSYS $ZMGR IPXSPX Names SUBSYS \HIMA.$ZMGR SUBSYS $ZMGR PROCESS $ZNV0 SERVER $ZNV0.#SAP PROCESS $ZNV1 SERVER $ZNV1.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) START Command START PROCESS START PROCESS initializes the protocol stack and links IPX with SPX. The successful completion of the START command leaves the process in the STARTED summary state. Command Syntax START [ / OUT file-spec / ] PROCESS process-name OUT file-spec directs any SCF output generated for this command to the specified file. file-spec must be a partially or fully qualified name.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) STATS Command SUB obj-type selects the subordinate objects the command affects. obj-type can be a subordinate object type or one of the keywords ONLY, ALL, or NONE. • • • • A subordinate object type causes the command to affect only objects of that type. ONLY causes the command to affect the subordinate objects. ALL causes the command to affect the named object and subordinate objects.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) STATS Command Any STATS command returns the time at which the current statistics were sampled and the time at which the counters were last reset. STATS is sensitive when used with the RESET option. STATS PROCESS STATS PROCESS displays the NonStop™ IPX/SPX subsystem statistics for each of the protocol layers.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) STATS Command -> STATS PROCESS $ZNV0, RESET IPXSPX Stats PROCESS \IDC14.$ZNV0 Reset Time .............. 24 Apr 2000, 18:39:19.955 Sample Time ............. 24 Apr 2000, 19:01:30.205 Number of Opens ......... 3 QIO Usage (%) ............... N/A NCP Layer: Inbound Packet Count ..... Inbound Packet Errors .... Open Count ............... Total Errors ............. 0 0 0 0 Outbound Packet Count ....... 0 Outbound Packet Errors ......
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) STATS Command Outbound Packet Errors displays the total number of times NCP was unable to send a packet to IPX. This condition occurs when the stream head is out of memory or is not initialized. Open Count displays the current number of NCP opens. This number is calculated as the number of NCP opens without a corresponding NCP close. Message Count displays the number of times a user request was received by the NCP Layer.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) • • • STATS Command No memory available Duplicate connection request SPX unable to reply to the sender Total Errors displays the sum of the following fields: • • • Send Failure Count Bad Incoming Packet Cnt Suppressed Packet Count Description of Statistics for the IPX Layer Inbound Packet Count displays the total number of inbound packets received by the IPX Layer.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) STATUS Command It is normal to see some dropped packets. If you are concerned about the number of dropped packets, use the QIO subsystem SCF STATUS SEGMENT command to check that the configured QIO size is large enough. Refer to the QIO Configuration and Management Manual for details on using the SCF commands for the QIO subsystem.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) STATUS Command OUT file-spec directs any SCF output generated for this command to the specified file. file-spec must be a partially or fully qualified name. If you do not specify this option, the output goes to the home terminal. PROCESS process-name is a valid process name indicating the desired IPXPROTO process. DETAIL specifies that the display is to include additional detailed information about the object.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) MEMORY STATUS Command The process could not get memory during initialization. Possible causes and recommended actions are • • NETWORK • • • UNKNOWN The QIOMON process may not be running. Use the QIO subsystem SCF STATUS MON command to check the status of the QIOMON process. A network problem prevents the PROCESS object from reaching the STARTED summary state.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) STATUS Command State displays the summary state of the specified process. Possible values are ABORTING The process is aborting. STARTED The process is started. It has communicated with a NetWare system and retrieved the network address of the nearest NetWare server. STARTING The process is starting. STOPPED The process is stopped. STOPPING The process is stopping.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) STATUS Command Trace File Name displays the name of the file to which trace records are being written by the primary IPXPROTO process. STATUS SERVER STATUS SERVER returns current information on the SERVER object. Command Syntax STATUS [ / OUT file-spec / ] SERVER server-name OUT file-spec directs any SCF output generated for this command to the specified file. file-spec must be a partially or fully qualified name.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) STATUS Command The node number identifies a specific machine within a network. On most LANs, this value is the same value as the MAC address. The node number is 6 bytes long. The socket number identifies the higher-level protocol and/or application within a specific node. The socket number is 2 bytes long. Type indicates the type of server, in hexadecimal.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) STATUS Command STATUS SUBSYS STATUS SUBSYS returns information on the current status of the IPXMGR process. Use the DETAIL option to display additional information. Command Syntax STATUS [ / OUT file-spec / ] SUBSYS subsystem-name [ , DETAIL ] OUT file-spec directs any SCF output generated for this command to the specified file. file-spec must be a partially or fully qualified name.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) STOP Command Backup State displays the summary state of the backup IPXMGR process. Possible summary states are: STARTED The SUBSYS backup process object is started. STOPPED There is no SUBSYS backup process object. STOPPING The SUBSYS backup process object is stopping. Takeover Count records the number of times a process has undergone an unplanned backup takeover since the process was started.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) STOP Command The STOP PROCESS command terminates the operation of the specified PROCESS object. You can stop a PROCESS object without restriction. The STOP SUBSYS command terminates the operation of all subordinate process objects. Specify the SUB option when you use the SUBSYS object. STOP is a sensitive command. STOP PROCESS STOP PROCESS normally terminates the activity of specified IPXPROTO processes.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) TRACE Command SUBSYS subsystem-name is a valid subsystem name indicating the desired IPXMGR process (always $ZMGR). SUB obj-type selects the subordinate objects the command affects. obj-type can be a subordinate object type or one of the keywords ONLY, ALL, or NONE. • • • • A subordinate object type causes the command to affect only objects of that type. ONLY causes the command to affect the subordinate objects.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) TRACE Command Caution. The trace operation can significantly increase processor use by the object being traced. To avoid problems with other processes in the processor, use the TACL ALTPRI command to lower the priority of the object being traced before issuing the SCF TRACE command. TRACE PROCESS TRACE PROCESS traces an IPXPROTO process.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) TRACE Command COUNT count specifies the number of trace records to be captured. count is an integer in the range -1 through 32767. If you omit this option or if count equals -1, records accumulate until the trace is stopped. NOCOLL indicates that the trace collector process should not be initiated. PAGES pages designates how much space, in units of pages, is allocated in the extended data segment used for tracing.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) TRACE Command TO file-spec specifies the name of the file into which the results of the trace operation are to be placed. This option is required if you don’t STOP. WRAP specifies that when the trace disk file end-of-file (EOF) is reached, trace data wraps to the beginning of the file and overwrites data.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) TRACE Command SUBSYS subsystem-name is a valid subsystem name indicating the desired IPXMGR process (always $ZMGR). STOP ends the trace operation. A TRACE command must include either the STOP or the TO option. COUNT count specifies the number of trace records to be captured. count is an integer in the range -1 through 32767. If you omit this option or if count equals -1, records accumulate until the trace is stopped.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) VERSION Command For more detailed information on the specific trace records captured by each existing SELECT option, including how these records are displayed by the PTrace program, refer to Section 4, NonStop™ IPX/SPX PTrace Facility. Examples The following command traces the assumed process, writes results into the file named $DATA1.TRC.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) VERSION Command DETAIL designates that complete version information is to be returned for the specified object. If you omit DETAIL, a single line of version information is returned for the object. VERSION PROCESS Command Display Format The format of the display of the VERSION PROCESS command without the DETAIL option is: -> VERSION PROCESS $ZNV0 VERSION PROCESS \IDC14.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) VERSION Command DETAIL designates that complete version information is to be returned for the specified object. If you omit DETAIL, a single line of version information is returned for the object. SUB obj-type selects the subordinate objects the command affects. obj-type can be a subordinate object type or one of the keywords ONLY, ALL, or NONE. • • • • A subordinate object type causes the command to affect only objects of that type.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) Routine Management Tasks Considerations • • • The object-name template (wildcard notation) is supported. (See Object-Name Templates and Wildcards on page 3-6.) VERSION is a nonsensitive command; any user on the system can issue this command. Issuing a VERSION command does not change an object’s summary state.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) Creating an IPXPROTO Process Creating an IPXPROTO Process To add an IPXPROTO process, you must specify a CODEFILE name, a process name, and an IOPORTNAME value for the PROCESS object: • • The process name must follow the Guardian naming conventions. The recommended form is $ZNVn, where n is an alphanumeric character. The IOPORTNAME takes the form LIF-name.filter-protocol.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) Modifying an IPXPROTO Process You also can use the SCF ABORT PROCESS command to terminate the operation of an IPXPROTO process quickly. All activities being performed by the aborted IPXPROTO process are halted; however, files may be left in an inconsistent or incomplete state. Use the SCF STOP PROCESS command if you want to stop the operation of the IPXPROTO process in a more controlled manner.
Managing NonStop™ IPX/SPX With the Subsystem Control Facility (SCF) • • • Displaying Event Messages The STATUS PROCESS command displays information on the current summary state of an IPXPROTO process (described on page 3-38). The STATUS SERVER command returns information on the current status of the SAP table. The SAP table contains information on the servers available on the NetWare LAN (described on page 3-42). The VERSION SUBSYS command displays product-version information (described on page 3-53).
4 NonStop™ IPX/SPX PTrace Facility This section provides an overview of the PTrace facility and explains how to use it to analyze NonStop™ IPX/SPX trace records. Overview of PTrace Trace files contain a record of the communications between processes. Each subsystem determines what information is recorded in its trace files. This information varies as to the type of events that are recorded, the amount of detail that is included, and other subsystem-specific parameters.
NonStop™ IPX/SPX PTrace Facility Recording and Displaying Trace Data Notes. The default record size (RECSIZE) of 120 bytes is too small to show the complete IPX/SPX data on a trace record. When starting a trace for an IPXPROTO process, use a RECSIZE of 1024 bytes. For the IPXMGR process, use a RECSIZE of 512 bytes. The default trace file size is 128 KB on disk. When the file is full, tracing automatically stops. The SCF TRACE command WRAP option allows the trace records to wrap around in the file.
NonStop™ IPX/SPX PTrace Facility Running PTrace Running PTrace Although the PTrace Reference Manual covers this subject in more detail, the descriptions that follow are enough information to get you started running PTrace. Starting a Noninteractive PTrace Session The syntax of the TACL or SCF RUN command for PTrace is PTRACE [ /run-option-list ] [ ptrace-command ] ... run-option-list is one or more NonStop™ Kernel run options, as described in the TACL Reference Manual.
NonStop™ IPX/SPX PTrace Facility Device Type and Subtype In the following example, the TACL RUN command instructs PTrace to read its commands from a file called PTRACE.FIRSTRUN and to write its display output to a file called PTRACE.FIRSTOUT. The NOWAIT option allows TACL to resume control of the session while PTrace is executing. PTRACE /IN PTRACE.FIRSTRUN, OUT PTRACE.FIRSTOUT, NOWAIT/ Starting an Interactive PTrace Session To start PTrace interactively, enter PTRACE at the TACL or SCF prompt.
NonStop™ IPX/SPX PTrace Facility PTrace Commands SETTRANSLATE TEST TEXT TRANSLATE Table 4-1 lists and summarizes all the PTrace commands supported by the NonStop™ IPX/SPX subsystem. Table 4-1. Summary of NonStop™ IPX/SPX PTrace Commands Command Description ALLOW Sets the number of errors or warnings permitted during the execution of a command. COUNT Counts the records in the trace file. ENV Displays the settings of the PTrace session parameters. EXIT Terminates a PTrace session.
NonStop™ IPX/SPX PTrace Facility HEX Command The remainder of this subsection describes in detail the subsystem-dependent commands supported by the NonStop™ IPX/SPX subsystem: HEX, LABEL, OCTAL, and SELECT. Each command description includes a brief explanation of what the command does, its syntax, and any special considerations. The commands are presented in alphabetical order. See the Notation Conventions on page xvi for a description of the notation scheme used here. Note.
NonStop™ IPX/SPX PTrace Facility LABEL Command LABEL Command LABEL controls the formatted display of trace records. The only way you can display NonStop™ IPX/SPX trace records is by using the LABEL command. Command Syntax LABEL [ ON | OFF ] ON turns on the formatted display of trace records. The default is ON. OFF turns off the formatted display of trace records, but the header for the trace record is displayed. Considerations • • • If you do not specify the LABEL command, ON is assumed.
NonStop™ IPX/SPX PTrace Facility SELECT Command Considerations • • • If you do not use the OCTAL command, OFF is assumed. If you specify OCTAL without the ON or OFF attribute, ON is assumed. The RESET and FROM commands set OCTAL to OFF. SELECT Command SELECT establishes the selection criteria that control which trace records are displayed. Command Syntax SELECT [ [ [ mask ] keyword ] ( keyword [ , keyword ] ...
NonStop™ IPX/SPX PTrace Facility Trace Record Formats keyword is one of the following for the SUBSYS object: ALL Traces all the options listed below. FILEIO Traces all file system requests and replies. SPIPROC Traces all commands issued by IPXMGR. SPIRPLY Traces a reply to the requestor. SPIRQST Traces all requests to IPXMGR. Considerations • • If you do not specify the SELECT command, the default is ALL. If you specify SELECT with no keywords, ALL is assumed.
File Header Record NonStop™ IPX/SPX PTrace Facility Each description includes the time when the record is generated, the record-type code, the text of the record, and the definitions of any values contained in the record. File Header Record The trace header record displays identification information specific to this trace file.
Header Format NonStop™ IPX/SPX PTrace Facility Header Format The format of the first line of all trace records is the same. Each trace record displayed is preceded by a header line of the following format: DateStamp TimeStamp >DeltaTime #TraceRecordNumber Type DateStamp displays the date at which the trace was captured. TimeStamp displays the time at which the trace was captured. DeltaTime displays the time lapsed (in seconds) since the previous trace was captured. If the time reaches 999.
Inbound Packet Trace Record NonStop™ IPX/SPX PTrace Facility OUTBOUND ipx indicates an outbound IPX packet with source and destination IPX addresses separated by ->. CheckSum displays the checksum of data in extended memory. This is set to FFFF (-1) by IPX implementations. This field is neither computed for sending data nor checked when receiving data. Length displays the total length of the IPX header plus data. The maximum packet length is set by the higher-level protocol layer (such as SPX or NCP).
NonStop™ IPX/SPX PTrace Facility Message System Interface Trace Records INBOUND ipx indicates an inbound IPX packet with source and destination IPX addresses separated by ->. CheckSum displays the checksum of data in extended memory. This is set to FFFF (-1) by IPX implementations. This field is neither computed for sending data nor checked when receiving data. Length displays the total length of the IPX header plus data.
NonStop™ IPX/SPX PTrace Facility Message System Request Trace Record 04/25/2000 19:22:26.297274 >001.929333 #613 Request MsgID: %H9EF8011FD LocID: 9 SRE_Reqctrlsize: 64 SRE_Reqdatasize: 0 DIALECT_FS_FS FS_FS_DEVINFO Request ctrl: 000: 0005 000C 0005 0001 0100 0000 0000 00C: 0000 0001 FF96 0000 0000 0000 0000 018: 0000 0000 0000 0000 8001 0080 3319 MsgT Interface 0063 0000 0063 0000 0000 0000 0000 Request Data: Request MsgID displays the NonStop™ Kernel message system ID of an incoming request.
NonStop™ IPX/SPX PTrace Facility Message System Reply Trace Record Message System Reply Trace Record The trace record for a message system reply is formatted as follows: 04/25/2000 19:22:26.354550 >000.
SAP Interface Trace Records NonStop™ IPX/SPX PTrace Facility Reply ctrl displays a hexadecimal dump of the reply’s control information. Reply data displays a hexadecimal dump of the reply’s data. SAP Interface Trace Records This subsection describes the trace records written by the Service Advertising Protocol (SAP) interface. SAP Processing Command Trace Record This trace record indicating that a command is being processed is formatted as follows: 04/25/2000 19:22:26.359915 >000.
NonStop™ IPX/SPX PTrace Facility Close SAP Interface Trace Record Server Added displays the name of the server being added to the SAP table. OCB displays the IPXPROTO process open control block (OCB) index for the NonStop™ Himalaya S-series client’s OCB. Server Address displays the address of the server being added. Server Type displays the type, in hexadecimal, of the server being added.
Update Server Trace Record NonStop™ IPX/SPX PTrace Facility Server Address displays the address of the server being deleted. Server Type displays the type, in hexadecimal, of the server being deleted. Update Server Trace Record The trace record indicating that a server is being updated in an IPXPROTO process SAP table is formatted as follows: 04/24/2000 15:21:26.078735 >000.
Socket Command Trace Record NonStop™ IPX/SPX PTrace Facility sock_handler SOCK_GETPEERNAME_ sock_handler_connect SOCK_GETSOCKNAME_ sock_handler_data SOCK_GETSOCKOPT_ sock_handler_listen SOCK_INFO_ sock_handler_disconnect SOCK_IOCTL_ sock_timeout SOCK_LISTEN_ SOCK_BIND_ SOCK_RECV_ SOCK_CLOSE_ SOCK_SEND_ SOCK_CONNECT_ SOCK_SETSOCKOPT_ SOCK_CREATE_ SOCK_SHUTDOWN_ type displays the socket type. The value is STREAM or DGRAM. state displays the current state of the socket.
Socket State Change Trace Record NonStop™ IPX/SPX PTrace Facility rmt displays the address of the remote endpoint. Socket State Change Trace Record The trace record indicating a state change for a socket is formatted as follows: 04/25/2000 20:58:26.281420 >000.000092 #195 SOCK Interface STATE CHNG: old: SO_OPEN new: SO_BOUND OCB: 2 sock_bind__ type: STREAM lcl: 0x00000001:08008E002F7F:4000 rmt: 0x00000000:000000000000:0000 STATE CHNG indicates a state change for a socket.
NonStop™ IPX/SPX PTrace Facility SPX Interface Trace Records rmt displays the address of the remote endpoint. SPX Interface Trace Records This subsection describes the trace records written by the SPX Protocol Layer. State Change Trace Record The trace record showing a state change for an SPX socket is formatted as follows: 04/24/2000 15:27:47.232881 >000.
NonStop™ IPX/SPX PTrace Facility Inbound Packet Trace Record Inbound Packet Trace Record The trace record showing an inbound SPX packet is formatted as follows: 04/25/2000 20:58:26.328377 >000.
NonStop™ IPX/SPX PTrace Facility Outbound Packet Trace Record SPX Data indicates that data is being received, in hexadecimal. Outbound Packet Trace Record The trace record showing an outbound SPX packet is formatted as follows: 04/25/2000 20:58:26.620294 >000.
Timer-Related Trace Record NonStop™ IPX/SPX PTrace Facility Length displays the length of the SPX header and data. SPX Data indicates that data is being sent, in hexadecimal. Timer-Related Trace Record This subsection describes the trace record written by the timer events. Expired Timer Trace Record The trace record showing the module that had a timer expire is formatted as follows: 04/24/2000 15:23:51.079900 >012.
A Protocol Interfaces and Services for NonStop™ IPX/SPX This appendix provides greater detail about the protocol interfaces and services supported by NonStop™ IPX/SPX and introduced in Section 2, Introduction to NonStop™ IPX/SPX.
Protocol Interfaces and Services for NonStop™ IPX/SPX Service Advertising Protocol (SAP) Table Service Advertising Protocol (SAP) Table SAP allows service nodes, such as file, print, and database servers, to register their services and addresses in SAP tables maintained by each server. The registration is done through SAP broadcasts every 60 seconds. If the broadcast of a specific service stops, all other servers purge the service from their SAP tables within about three minutes.
Protocol Interfaces and Services for NonStop™ IPX/SPX Routing Information Protocol (RIP) Internet address is the IPX address of the server. See IPX Addresses on page A-6. Hops to server is the number of routers that the packet must pass to reach the server. Time since changed removes entries for a server that started but has subsequently stopped advertising.
Protocol Interfaces and Services for NonStop™ IPX/SPX Routing Information Protocol (RIP) Figure A-2 shows an example of a router between networks A and B. Figure A-2. Router Example Network A Network B Router Node B Node A CDT 022.
Protocol Interfaces and Services for NonStop™ IPX/SPX IPX Packet Header Format The NonStop™ IPX/SPX subsystem uses RIP to broadcast the NonStop™ Himalaya Sseries server’s network address onto the NetWare LAN. RIP is also used to collect the addresses of other devices on the LAN and place them into the SAP table that is maintained by the IPXPROTO process.
Protocol Interfaces and Services for NonStop™ IPX/SPX IPX Packet Header Format Table A-2. IPX Packet-Type Field Identification PacketType Value (in Hex.) Higher-Level Protocol 01 Routing Information Protocol (RIP) 04 Service Advertising Protocol (SAP) 05 Sequenced Packet Exchange (SPX) 11 NetWare Core Protocol (NCP) 14 Network Basic Input/Output Service (NetBIOS) Destination Address is the IPX address of the destination. See IPX Addresses on page A-6.
Protocol Interfaces and Services for NonStop™ IPX/SPX IPX Packet Header Format Node identifies a specific machine within a network. The Node field is usually related to the physical address of the network adapter; on Ethernet and token-ring LANs, the Node field is the same as the MAC address of the adapter or controller. IPX uses the combination of the Network and Node fields to transmit packets within a NetWare internetwork.
Protocol Interfaces and Services for NonStop™ IPX/SPX SPX Packet Header Format IPX uses the MAC protocol to transmit packets from one node to another. A MAC header consists of a source node address and a destination node address. The node address is a 6-byte number that is usually assigned by the network interface card (NIC) vendor. SPX Packet Header Format An SPX packet header is 12 bytes. Figure A-5 shows the format of an SPX packet header. Figure A-5. SPX Packet Header Format Conn.
Protocol Interfaces and Services for NonStop™ IPX/SPX Other Services Allocation Number is used for flow control. The minimum SPX packet size is 42 bytes, which consist of the 30-byte IPX header plus the 12-byte SPX header. The maximum packet size is set by the higher-level protocol layer (such as SPX or NCP). NonStop™ IPX/SPX imposes this limit on the SPX packet size. SPX Socket Numbers SPX uses the IPX addressing scheme.
Protocol Interfaces and Services for NonStop™ IPX/SPX Information Xchange Facility (IXF) File Transfer Note. Printing from Telserv to NetWare printers is not supported. Information Xchange Facility (IXF) File Transfer IXF allows you to move data between a workstation and a NonStop™ Himalaya S-series server by using three commands: • • • GET—Copies data from a file or a device on a NonStop™ Himalaya S-series host to a file or a device on the workstation.
Protocol Interfaces and Services for NonStop™ IPX/SPX Fault-Tolerant Subsystem Operations Printers are connected through the NetWare network to • • • The print server A workstation on the network The network cable through a network interface card (NIC) The LAN Print Spooler for NetWare is a print process in the Spooler subsystem. The LAN Print Spooler for NetWare reads in information based on its configuration file (FASTCNFG).
Protocol Interfaces and Services for NonStop™ IPX/SPX IPXPROTO Process IPXPROTO Process The IPXPROTO process is implemented as a process pair. Because it relies on the Queued Input/Output (QIO) subsystem, the IPXPROTO process pair is tied to the location of the LAN controller. The IPXPROTO process must be configured on the same processor pair as the ServerNet LAN systems access input/output process (SLSA IOP). Whenever SLSA switches a processor, the IPXPROTO process also switches the same processor.
Protocol Interfaces and Services for NonStop™ IPX/SPX Examples of NonStop™ IPX/SPX Functions Examples of NonStop™ IPX/SPX Functions This section shows examples of how the NonStop™ IPX/SPX subsystem functions advertise a server application on the NetWare LAN and establish a connection between the application and a client. It describes the formation and processing of IPX protocol packets by the IPXPROTO process.
Protocol Interfaces and Services for NonStop™ IPX/SPX Examples of NonStop™ IPX/SPX Functions The ODBC Server uses the NonStop™ IPX/SPX Sockets library to access the IPXPROTO process and bind to an IPX or SPX socket. The server application specifies the name of the IPXPROTO process to be used for NetWare communications. This name is specified when configuring the ODBC Server. Once the socket is bound, the server can receive connection requests from workstation clients.
Protocol Interfaces and Services for NonStop™ IPX/SPX Examples of NonStop™ IPX/SPX Functions Figure A-7 shows an example of NonStop™ Himalaya S-series application users printing to a NetWare printer through the LAN Print Spooler for NetWare product. Figure A-7. Printing From a NonStop™ Application to a NetWare Printer NetWare Printer NetWare File Server 6 NonStop TM Himalaya S-Series Server 1 NonStop TM IPX/SPX subsystem is started. 2 Spooler processes are started.
Protocol Interfaces and Services for NonStop™ IPX/SPX Examples of NonStop™ IPX/SPX Functions IPX/SPX Configuration and Management Manual—425731-001 A -16
B Event Messages for NonStop™ IPX/SPX This section describes the contents and meaning of all event messages generated by NonStop™ IPX/SPX. For general information on how an application obtains event messages from subsystems that use the SPI common extensions (ZCOM) tokens, refer to the SPI Common Extensions Manual. In this section, command numbers, object types, and all tokens and their values are represented in Data Definition Language (DDL).
Event Messages for NonStop™ IPX/SPX Tokens in All Event Messages Table B-1. ZIPX Event Messages (page 2 of 2) Number ZIPX-EVT-event Description 5 ZIPX-EVT-NS-BKUP-TAKEOVERERR The backup IPXPROTO process cannot take over processing. 6 ZIPX-EVT-NS-BKUP-START-ERR The IPXPROTO process cannot start backup. 7 ZIPX-EVT-SOCKET-ERR The IPXPROTO process encountered an internal error on a socket.
Event Messages for NonStop™ IPX/SPX Event-Message Descriptions Refer to the SPI Programming Manual for descriptions of the ZSPI tokens and the EMS Manual for descriptions of the ZEMS tokens. Event-Message Descriptions The following pages explain in detail each event message that can be issued by the NonStop™ IPX/SPX subsystem. The descriptions appear in ascending order by event number; that is, in ascending order by the ZIPX-EVT- values.
Event Messages for NonStop™ IPX/SPX 1: ZIPX-EVT-PROCESS-AVAIL 1: ZIPX-EVT-PROCESS-AVAIL NonStop™ IPX/SPX issues this message whenever a process becomes available: Unconditional Tokens (excluding header tokens) Token: Value: ZEMS-TKN-CONTENT-STANDARD ZEMS-TKN-EMPHASIS ZEMS-TKN-NAME-MANAGER ZEMS-TKN-STATE-CURRENT ZEMS-TKN-STATE-PREVIOUS ZEMS-TKN-CHANGE-REASON ZSPI-TDT-ENUM ZSPI-TYP-BOOLEAN ZSPI-TYP-STRING ZSPI-TYP-ENUM ZSPI-TYP-ENUM ZSPI-TDT-ENUM Event-Message Text process name Object Available Reason:
1: ZIPX-EVT-PROCESS-AVAIL Event Messages for NonStop™ IPX/SPX ZEMS-TKN-STATE-PREVIOUS has one of the following values, depending on the previous state of the object: Value Meaning ZCOM-VAL-SUMSTATE-ABORTING Previous state was ABORTING. ZCOM-VAL-SUMSTATE-STARTED Previous state was STARTED. ZCOM-VAL-SUMSTATE-STOPPED Previous state was STOPPED. ZCOM-VAL-SUMSTATE-STOPPING Previous state was STOPPING.
2: ZIPX-EVT-PROCESS-UNAVAIL Event Messages for NonStop™ IPX/SPX 2: ZIPX-EVT-PROCESS-UNAVAIL NonStop™ IPX/SPX issues this message whenever a process becomes unavailable or a restart operation has failed. It indicates that the process is not available for use and specifies the reason.
2: ZIPX-EVT-PROCESS-UNAVAIL Event Messages for NonStop™ IPX/SPX ZEMS-TKN-CHANGE-REASON has one of the following values, depending on the cause of the failure: Value Meaning ZEMS-VAL-OPERATORINITIATED An SCF STOP or ABORT was issued to stop the process. ZEMS-VAL-UNDERLYINGFAILED The underlying service that this object depends on has failed. That service name is reported in ZEMS-TKN-UNDERLYING-OBJ-NAME.
Event Messages for NonStop™ IPX/SPX 2: ZIPX-EVT-PROCESS-UNAVAIL Cause. NonStop™ IPX/SPX issues this message whenever a process becomes unavailable or a restart operation has failed. It indicates that the process is not available for use and displays the reason. This event occurs after the process has been either stopped or aborted using SCF, when executing cleanup procedures due to a fatal error, or when the process cannot initialize. Effect. The desired process is not available for use. Recovery.
3: ZIPX-EVT-PROCESS-STATE-CHANGE Event Messages for NonStop™ IPX/SPX 3: ZIPX-EVT-PROCESS-STATE-CHANGE NonStop™ IPX/SPX issues this message whenever a process enters a state (other than available or unavailable) that requires operator intervention before its state can change or that persists in the same state long enough for the operator to take notice.
3: ZIPX-EVT-PROCESS-STATE-CHANGE Event Messages for NonStop™ IPX/SPX Value Meaning ZCOM-VAL-SUMSTATE-STARTING Current state is STARTING. ZCOM-VAL-SUMSTATE-STOPPED Current state is STOPPED. ZCOM-VAL-SUMSTATE-STOPPING Current state is STOPPING. ZEMS-TKN-STATE-PREVIOUS has one of the following values, depending on the previous state of the object: Value Meaning ZCOM-VAL-SUMSTATE-ABORTING Previous state was ABORTING. ZCOM-VAL-SUMSTATE-STARTED Previous state was STARTED.
Event Messages for NonStop™ IPX/SPX 4: ZIPX-EVT-NS-BKUP-CORRUPTED Cause. NonStop™ IPX/SPX issues this message whenever a process enters a state (other than available or unavailable) that requires operator intervention before it can change or that persists in the same state long enough for the operator to take notice. Effect. The state is something other than available or unavailable. Recovery. If the state change was caused by an underlying object, investigate the status of the object.
4: ZIPX-EVT-NS-BKUP-CORRUPTED Event Messages for NonStop™ IPX/SPX ZEMS-TKN-NAME-MANAGER has the value ZIPX-VAL-NAME-MANAGER, identifying the manager process of the object reported in the event. ZIPX-TKN-NS-ERR-CAUSE has the value ZIPX-VAL-NS-CAUSE-CHKPT-FAIL. ZIPX-TKN-NS-ERR-ACTION has one of the following values, depending on the recovery action to be taken: Value Meaning ZIPX-VAL-NS-RECOVABORTED Stop and restart the IPXPROTO process when convenient. The primary process continues to run.
Event Messages for NonStop™ IPX/SPX 5: ZIPX-EVT-NS-BKUP-TAKEOVER-ERR 5: ZIPX-EVT-NS-BKUP-TAKEOVER-ERR NonStop™ IPX/SPX issues this message when the backup process cannot take over processing.
6: ZIPX-EVT-NS-BKUP-START-ERR Event Messages for NonStop™ IPX/SPX Event-Message Text In the text message: process name indicates the name of the IPXPROTO process for which this event is generated. cause string indicates that the backup process cannot recover. recovery string specifies that the IPXPROTO process is to be restarted. Cause. NonStop™ IPX/SPX issues this message when the backup process cannot take over processing. Effect. The IPXPROTO process is aborted. Recovery.
Event Messages for NonStop™ IPX/SPX 6: ZIPX-EVT-NS-BKUP-START-ERR Token Descriptions ZEMS-TKN-CONTENT-USER has the value ZIPX-VAL-NONSTOP-PROCESSING, indicating that this event is generated by the NonStop™ IPX/SPX code that implements NonStop™ processing. ZEMS-TKN-EMPHASIS has the value ZSPI-VAL-TRUE, indicating that this is a critical event. ZEMS-TKN-NAME-MANAGER has the value ZIPX-VAL-NAME-MANAGER, identifying the manager process of the object reported in the event.
7: ZIPX-EVT-SOCKET-ERR Event Messages for NonStop™ IPX/SPX Recovery. Start and restart the IPXPROTO process, when convenient, in order to bring up the backup process. 7: ZIPX-EVT-SOCKET-ERR The IPXPROTO process encountered an internal error on a socket.
Event Messages for NonStop™ IPX/SPX Filter Examples opener process name indicates the process name of the opener of the local socket. Cause. The IPXPROTO process encountered an internal error on a socket. Effect. The socket connection is lost. The IPXPROTO process will reply to applications with the socket error EIO (4005) and release buffers associated with the socket. Recovery. Applications should close the socket and reopen.
Event Messages for NonStop™ IPX/SPX Example 2 Example 2 The following filter selects all the critical NonStop™ IPX/SPX event messages that have a particular process as their subject: -- Filter that selects only critical NonStop™ IPX/SPX event -- messages that have a particular process as their subject. [#SET zipx^val^ssid [zspi^val^tandem].[zspi^ssn^zipx].
C SCF Command Syntax for NonStop™ IPX/SPX This appendix summarizes the syntax of the Subsystem Control Facility (SCF) commands for the NonStop™ IPX/SPX subsystem. ABORT PROCESS Command Stops the operation of an IPXPROTO process abruptly. ABORT [ / OUT file-spec / ] PROCESS process-name ABORT SUBSYS Command Terminates the operation of the IPXPROTO processes as quickly as possible. You must specify the SUB option when you use the SUBSYS object.
ALTER PROCESS Command SCF Command Syntax for NonStop™ IPX/SPX ALTER PROCESS Command Changes the values of one or more attributes of an IPXPROTO process. ALTER [ / OUT file-spec / ] [ [ [ [ [ [ , , , , , , , PROCESS process-name IOPORTNAME LIF-name.filter-protocol IPXMAXSOCKETS integer ] QIOLIMIT integer ] SPXKEEPALIVETIMER integer ] SPXMAXBINDS integer ] SPXMAXCONN integer ] SPXMAXRESEND integer ] DELETE PROCESS Command Removes an IPXPROTO process from the NonStop™ IPX/SPX subsystem.
INFO SUBSYS Command SCF Command Syntax for NonStop™ IPX/SPX INFO SUBSYS Command Displays the attributes of an IPXMGR process. INFO [ / OUT file-spec / ] SUBSYS subsystem-name [ , DETAIL ] [ , SUB { ONLY | ALL | NONE | obj-type } ] LISTOPENS PROCESS Command Returns information about the openers of an IPXPROTO process. LISTOPENS [ / OUT file-spec / ] PROCESS process-name LISTOPENS SUBSYS Command Returns information about the openers of the IPXMGR process.
START PROCESS Command SCF Command Syntax for NonStop™ IPX/SPX START PROCESS Command Initiates the operation of an IPXPROTO process. START [ / OUT file-spec / ] PROCESS process-name START SUBSYS Command Initiates the operation of the IPXMGR process. You must specify the SUB option when you use the SUBSYS object.
STATUS SUBSYS Command SCF Command Syntax for NonStop™ IPX/SPX STATUS SUBSYS Command Displays the status of an IPXMGR process. STATUS [ / OUT file-spec / ] SUBSYS subsystem-name [ , DETAIL ] STOP PROCESS Command Terminates the operation of an IPXPROTO process in an orderly manner. STOP [ / OUT file-spec / ] PROCESS process-name STOP SUBSYS Command Terminates the operation of an IPXMGR process in an orderly manner. You must specify the SUB option when you use the SUBSYS object.
TRACE SUBSYS Command SCF Command Syntax for NonStop™ IPX/SPX TRACE SUBSYS Command Captures trace activity for an IPXMGR process. TRACE [ / OUT file-spec / ] SUBSYS subsystem-name { , STOP [, COUNT count [, NOCOLL [, PAGES pages [, RECSIZE size [, SELECT select-spec [, TO file-spec [, WRAP ] ] ] ] ] ] ] } VERSION PROCESS Command Displays version information for the IPXPROTO process.
D Error Messages for NonStop™ IPX/SPX This appendix describes the operator and error messages generated by the NonStop™ IPX/SPX subsystem. The appendix contains the following sections: • • NonStop™ IPX/SPX Operator Messages on this page NonStop™ IPX/SPX Error Messages on page D-7 Each message description in this appendix includes the syntax and its meaning along with information on the probable cause(s), effect, and recommended recovery actions.
Error Messages for NonStop™ IPX/SPX Backup Unable to Take Over Processing recovery string indicates whether the IPXPROTO process was able to recover automatically. If recovery did not occur, specifies that you should either restart the backup or stop and restart the IPXPROTO process. Cause. NonStop™ IPX/SPX issues this message when an error occurs that causes the backup process to become corrupted. The backup process is corrupted when the primary process cannot checkpoint data to the backup process.
Error Messages for NonStop™ IPX/SPX Object Available process name indicates the name of the IPXPROTO process for which this event is generated. cause string indicates that an error occurred when trying to create the backup process. err num indicates the file-system error that was received when trying to create the backup process. recovery string indicates that you should stop and restart the IPXPROTO process when convenient. Cause. The IPXPROTO process cannot start the backup process. Effect.
Error Messages for NonStop™ IPX/SPX Object Unavailable Object Unavailable process name Object Unavailable Cause: failure cause [ Underlying object: underlying obj-name ] [ Symptom: symptom string ] process name indicates the name of the IPXPROTO process for which this event is generated. failure cause indicates the reason for the failure. underlying obj-name specifies the name of the underlying object that failed. symptom string provides further details on the cause of the failure.
Error Messages for NonStop™ IPX/SPX NETWORK Summary State Change A network problem prevents the PROCESS object from reaching a STARTED summary state. Possible causes and recommended actions are: The NetWare server is not running. The process cannot start unless a NetWare server is running and configured using the same frame type as the IPXPROTO process. An invalid SLSA filter protocol was specified in the IOPORTNAME.
Error Messages for NonStop™ IPX/SPX Socket Error Effect. The state is something other than available or unavailable. Recovery. If the state change was caused by an underlying object, investigate the status of the underlying object. An SCF START command may be required to bring the state to STARTED. Socket Error process name Socket error Local: local ipxaddr Remote: remote ipxaddr Opener: opener process name process name indicates the name of the IPXPROTO process for which this event is generated.
Error Messages for NonStop™ IPX/SPX NonStop™ IPX/SPX Error Messages NonStop™ IPX/SPX Error Messages The following NonStop™ IPX/SPX error messages are presented in numerical order. Error messages are identified by number. You can use the SCF HELP command to display the text of a message.
Error Messages for NonStop™ IPX/SPX IPXSPX 00009 IPXSPX 00009 IPXSPX 00009 Token value is invalid. Cause. The subsystem has received a command message with a bad token; the token value is invalid. Effect. The command is not executed. Recovery. Check that you specify valid token values. IPXSPX 00010 IPXSPX 00010 START obj-name failed due to error = error obj-name is the name of the object you specified in a START command. Cause.
Error Messages for NonStop™ IPX/SPX IPXSPX 00011 IPXSPX 00011 IPXSPX 00011 ALTER obj-name failed due to error = error obj-name is the name of the object you specified in an ALTER command. Cause. The ALTER command failed for one of the following reasons. • • • The SLSA logical interface (LIF) is down, or the LIF is not accessible. The specified processors are not on the access list. The specified IOPORTNAME is incorrect. Effect. The command is not executed. Recovery.
Error Messages for NonStop™ IPX/SPX IPXSPX 00018 Cause. The ADD command failed for one of the following reasons. • • • The SLSA logical interface (LIF) is down, or the LIF is not accessible. The specified processors are not on the access list. The specified IOPORTNAME is incorrect. Effect. The command is not executed, so the IPXPROTO process is not defined to the NonStop™ IPX/SPX subsystem. Recovery. Verify that the specified IOPORTNAME exists, is configured for QIO, and is in the correct format.
Glossary ABORT. A sensitive command that terminates the operation of a NonStop™ IPX/SPX object abruptly without regard for interruption of data transfer. ABORTING. The state of an object, indicating that it is responding to an ABORT command or some type of malfunction. Access Control Server (ACS). An optional NonStop™ Himalaya S-series server process that can be used to grant or deny workstation access to the Remote Server Call (RSC) services on the NonStop™ Himalaya S-series server.
attribute Glossary attribute. In Distributed Systems Management (DSM), a characteristic of an entity. For example, two attributes of a communications line might be its hop count and its retry count. broadcast. A packet delivery system that delivers a copy of a given packet to all hosts that attach to it is said to broadcast the packet. Broadcast may be implemented with hardware or software. client. A workstation in a client-server environment. A program that requests operations from another program.
Distributed Systems Management (DSM) Glossary Distributed Systems Management (DSM). A set of tools used to manage NonStop™ systems and networks. DSM tools include the ViewPoint console application, Subsystem Control Facility (SCF), and Event Management Service (EMS) interfaces to the management processes for various NonStop™ Himalaya S-series subsystems. distributor.
filter Glossary filter. In Event Management Service (EMS), a file containing a list of criteria against which incoming event messages can be compared. The messages are allowed to pass (all criteria met) or not pass (one or more criteria failed). In the ServerNet LAN systems access (SLSA) subsystem, a filter provides a logical mechanism where frames received from the local area network (LAN) can be sorted and then delivered to a particular client. forwarding distributor.
LAN Manager (LANMAN) process Glossary LAN Manager (LANMAN) process. LANMAN is provided as part of the ServerNet LAN systems access (SLSA) subsystem. The NonStop™ Kernel subsystem starts LANMAN, and the Subsystem Control Facility (SCF) product module manages it. LANMAN is started as a generic process and runs as a NonStop™ process pair in the host system processors. LANMAN starts and manages the SLSA subsystem objects and starts the LAN Monitor (LANMON) process.
Media Access Control (MAC) address Glossary Media Access Control (MAC) address. A value in the Medium Access Control sublayer of the IEEE/ISO/ANSI LAN architecture that uniquely identifies an individual station that implements a single point of physical attachment to a local area network (LAN). MFIOB. See multifunction I/O board (MFIOB). multicast. A technique that allows copies of a single packet to be passed to a selected subset of all possible destinations.
noncritical event Glossary noncritical event. A Distributed Systems Management (DSM) event that is not crucial to system or network operations. Contrast critical event. nonsensitive command. A Subsystem Control Facility (SCF) command that can be issued by any user or program allowed access to the target subsystem—that is, a command on which the subsystem imposes no further security restrictions.
Open Database Connectivity (ODBC) Glossary Open Database Connectivity (ODBC). A Microsoft application program interface (API) for connecting to a database. The ODBC interface allows programmers to write a single set of code to access different Structured Query Language (SQL) databases. The NonStop™ Open Database Connectivity (ODBC) Server is a Compaq software product that processes ODBC requests. It replaces the Compaq SQL Server Gateway product. Outside View with Tandem Terminal Emulator (TTE).
predefined value Glossary predefined value. A commonly used value—for example, a value for a token or a field in a token—that is given a name in a set of definition files. print queue. In a NetWare network, a directory on the network on which print jobs are stored. A printer is assigned to a print queue. print server. In a NetWare local area network (LAN), a server that sends print jobs from a print queue to a network printer. printing distributor.
response Glossary response. In Distributed Systems Management (DSM), the information or confirmation supplied (as part of a response message) to an application by a subsystem in response to a DSM command. RIP. See Routing Information Protocol (RIP). Routing Information Protocol (RIP). A protocol used to control packet forwarding between routers in a network. RSC. See Remote Server Call (RSC). RSCCOM.
service Glossary service. A set of primitives (operations) that a layer provides to the layer above it. The service defines what operations the layer can perform on behalf of its users but not how these operations are implemented. A service relates to an interface between two layers: the lower layer is the service provider, and the upper layer is the service user. Compare protocol. Service Advertising Protocol (SAP).
STOPPED Glossary STOPPED. A summary state that indicates that an object is not ready for normal operations. STOPPING. A summary state that indicates that an object is in the process of being STOPPED. Structured Query Language (SQL). A set of commands that allows users to inquire about the contents of a database. Subnetwork Access Protocol (SNAP).
summary state Glossary summary state. In Distributed Systems Management (DSM) interfaces to Compaq data communications subsystems, one of the generally defined possible conditions of an object, with respect to the management of that object. Summary states for NonStop™ IPX/SPX objects include ABORTING, DEFINED, STARTED, STARTING, STOPPED, and STOPPING. TACL. See Tandem Advanced Command Language (TACL). TAL. See Transaction Application Language (TAL). Tandem Advanced Command Language (TACL).
token code Glossary token code. In Distributed Systems Management (DSM) programmatic interfaces, a 32-bit value that identifies a token. A token code consists of a token type (16 bits) and a token number (16 bits). In Pascal, TAL, C, COBOL85, and Tandem Advanced Command Language (TACL), names are used to represent token codes (ZSPI-TKN-SSID, for example). See also token map. token map.
ViewPoint console application Glossary ViewPoint console application. An extensible interactive application for operators, provided as part of Distributed Systems Management (DSM). ViewPoint allows a system or a network to be controlled from a single terminal.
$ZNET Glossary IPX/SPX Configuration and Management Manual—425731-001 Glossary -16
Index Numbers C 6530 terminal emulators 2-11 Clients on a NetWare LAN 2-2 Communications modes A-9 Conditional tokens B-3 Configuration LAN Print Spooler for NetWare 1-9 Open Database Connectivity (ODBC) 1-8 Tandem user IDs 1-8 Telserv 1-8 Connections, number supported 1-1 Console messages, relationship to event messages B-3 Conversational communications mode A-9 COUNT command (PTrace) 4-5 A ABORT command (SCF) 3-11/3-13 ABORT PROCESS 3-11 ABORT SUBSYS 3-12 Adapters, ServerNet 1-4 ADD command (SCF) 3-13
F Index Ethernet II 3-9 Ethernet LANs Ethernet 4 ServerNet adapter (E4SA) 1-4 frame types 3-8 IOPORTNAMEs 3-8 LIF names 3-8 multifunction I/O board (MFIOB) 1-4 Event Management Service (EMS) 3-2 Event messages 1 Process available B-4 2 Process unavailable B-6 3 Process state change B-11 4 Backup corrupted B-11 5 Backup takeover error B-13 6 Backup start error B-14 displaying on operator console 3-58 with ViewPoint 3-58 error lists B-3 filters B-17 relationship to console messages B-3 tokens in B-2 writing
L Index IPXPROTO processes configuring 1-6 connections supported 1-1 deleting 3-19, 3-57 modifying 3-57 specifying LIFs and primary and backup processors 1-2 stopping 3-56 switching A-12 ipxsnap 3-9 L LABEL command (PTrace) 4-5, 4-7 LAN driver software 2-3 LAN Print Spooler for NetWare 2-15, A-11 configuring user IDs for 1-8/1-9 LIMIT command (PTrace) 4-5 LISTOPENS command (SCF) 3-26/3-29 LISTOPENS PROCESS 3-26 LISTOPENS SUBSYS 3-27 Local area networks (LANs) 2-2 LOG command (PTrace) 4-5 Logical interfac
O Index O OBEY command (PTrace) 4-5 Objects 3-3/3-6 object types 3-3 PROCESS 3-3 SERVER 3-4 SUBSYS 3-3 object-name templates 3-6 summary states 3-4 OCTAL command (PTrace) 4-5, 4-7 Online transaction processing (OLTP) 2-13 Open Database Connectivity (ODBC) configuring 1-8 ODBC Driver Manager 2-14 using to access SQL databases 2-14 Opening a socket 2-8 Operator messages D-1/D-6 Backup Unable to Take Over Processing D-2 Corrupted Backup D-1 critical versus noncritical D-1 Object Available D-3 Object Unavaila
R Index R RECORD command (PTrace) 4-5 Recording trace data 4-1 Remote Server Call (RSC) 2-12 NonStop™ Transaction Services/MP (NonStop™ TS/MP) 2-12 Pathway Open Environment Toolkit (POET) 2-13 Requestors on network operating systems (NOSs) 2-2 RESET command (PTrace) 4-5 Routing Information Protocol (RIP) 2-10, A-3 RUN command (TACL) starting IPXMGR with 1-5 starting IPXPROTO with 1-6 starting PTrace with 4-3 S SCF commands entering 3-7 object-name templates in 3-6 overview of 3-9 sensitive versus nonsens
T Index Servers on a NetWare LAN 2-2 Service Advertising Protocol (SAP) and server applications 2-10 interface 2-7 registering services with 2-10 SAP tables A-2/A-3 displaying 1-7 tables 2-7 object names in 3-4 Socket numbers A-7 Sockets 2-7 Software requirements 2-16 Specifying logical interfaces (LIFs) for IPXPROTO processes 1-2 START command (SCF) 3-31/3-33 START PROCESS 3-32 START SUBSYS 3-32 Starting IPXPROTO processes 1-2 Starting PTrace 4-3 STATS command (SCF) 3-33/3-38 STATS PROCESS 3-34 IPX Layer
U Index Tracing 4-1/4-24 Transaction integrity with NonStop™ TM/MP 2-13 U Unconditional tokens B-3 User IDs, configuring 1-8 V VERSION command (SCF) 3-52/3-55 VERSION PROCESS 3-52 VERSION SUBSYS 3-53 W Wildcards 3-6 Workstations LAN driver software 2-3 logging onto host 2-11 network interface cards (NICs) 2-3 on a NetWare LAN 2-2 running NWPING 1-9 running NWSCAN 1-9 NS-BKUP-CORRUPTED B-11/B-12 NS-BKUP-START-ERR B-14/B-16 NS-BKUP-TAKEOVERERR B-13/B-14 PROCESS-AVAIL B-4/B-5 PROCESS-STATE-CHANGE B-11 PR
Special Characters Index IPX/SPX Configuration and Management Manual—425731-001 Index- 8
