NS 3000/iX Operations & Maintenance Reference Manual HP 3000 MPE/iX Computer Systems Edition 7 36922-90039 E1098 Printed in: U.S.A.
Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
Contents 1. Overview of NS 3000/iX Operations Creating Your Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Creation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The NS 3000/iX Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating Your Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtaining Information About Your Network . . . . . . . . . . . . . . . . . . .
Contents To Display Network Directory Configuration . . . . . . . . . . . . . . . . . Displaying Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Display Link Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To Display Network Transport Status . . . . . . . . . . . . . . . . . . . . . . . To Display General Transport Status . . . . . . . . . . . . . . . . . . . . . . To Display Status of a NET . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Line Opening Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Line Closing Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 NMS Utility Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Nodal Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Recent Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents To Use RESOURCE MONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 To Use SOCKINFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 To Use STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 To Use X25CHECK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 To Use X25STAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 To Use XPPERF . . . . . . . . . .
Contents Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents NSCONTROL LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 171 171 172 A. LINKCONTROL Command NS 3000/iX LAP-B Link Statistics . . . . . . . . . . . . .
Contents 10
Figures Figure 4-1 . Characterizing the Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 Figure 7-1 . The NETCONTROL Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115 Figure A-1 . LINKSTATE Command for LAP-B Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174 Figure A-2 . LAP-B CONFIGURATION Parameter Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 12
Tables Table 1-1. Tools for Obtaining Network Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 Table 5-1. Nodal Troubleshooting Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 Table 6-1. Differences in Tool Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 Table 6-2. The NETTOOL Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface Network Services for MPE/iX based systems are provided by an HP data communications product named NS 3000/iX. This manual describes the system-level commands and utilities used to perform network operations, maintenance, and troubleshooting after the initial network configuration. NS 3000/iX enables your HP 3000 Series 900 to communicate with other HP computer systems as part of a distributed network. These systems can be other HP 3000s, HP 9000s, HP 1000s, and PCs.
Organization of the Manual You can use this manual as either a command reference or a user’s guide, depending on your needs. It contains the following sections: • Chapter 1, “Overview of NS 3000/iX Operations,” provides a general description of the operations and maintenance functions required for your NS network. It includes a table that can help you determine which tool to use to obtain specific information about your network.
• HP36923A LAN 3000/iX Link and Terminal LAN Link Hardware Reference Manual • LAN Cable and Accessories Installation Manual • Central Bus Programmable Serial Interface Installation and Reference Guide • HP 28663A EtherTwist Hub Installation Guide For the NS 3000/iX Services • Using NS 3000/iX Network Services For Either the NS 3000/iX Links or Services • NS 3000/iX Error Messages Reference Manual For the Distributed Terminal Subsystem (DTS) • Configuring Systems for Terminals, Printers, and Other Serial Dev
Overview of NS 3000/iX Operations 1 Overview of NS 3000/iX Operations In the daily operations of the NS 3000/iX network communications products, you will need to perform a number of management tasks. These tasks include starting and stopping Network Services or links, verifying network connections, obtaining status information, and troubleshooting problems that might occur on the network. Hewlett-Packard provides a number of tools to help you in performing these functions.
Overview of NS 3000/iX Operations Creating Your Network Creating Your Network This manual assumes that you have a functional network with at least one NS 3000/iX link properly configured to allow data communications to occur between systems. If you have not yet created your network, or if you need to make modifications to your network configuration, you will need to use the HP 3000/iX Network Planning and Configuration Guide.
Overview of NS 3000/iX Operations Creating Your Network • X.25 iX System Access. Supports connections to X.25 public or private data networks. • Fiber Distributed Data Interface/iX. Provides a single-attach connection to an FDDI network through an FDDI concentrator. • HP-PB 100VG-AnyLAN Network Adapter. Connects an HP 3000 computer using the HP-PB backplane to a 100VG-AnyLAN network. • HP-PB 100Base-T Network Adapter. Connects an HP 3000 computer using the HP-PB backplane to a 100Base-T network.
Overview of NS 3000/iX Operations Operating Your Network Operating Your Network You perform most of the daily operations required by the NS network through the use of the provided NS 3000/iX network commands. Complete information on the syntax and function of all the commands is contained in Chapter 7, “Commands,” of this manual. The NETCONTROL START command allows you to initiate the network transport as well as the individual networks on an active transport.
Overview of NS 3000/iX Operations Obtaining Information About Your Network Obtaining Information About Your Network You may need to obtain many different kinds of information about your network and its operations. This information ranges from the version numbers of the software modules you are running to complete statistical summaries of events that are taking place on a specific link. The tools and commands that are available to help you obtain the various types of information are summarized in Table 1-1.
Overview of NS 3000/iX Operations Obtaining Information About Your Network To Get Information About... Use... Refer to...
Overview of NS 3000/iX Operations Obtaining Information About Your Network To Get Information About... Use... Refer to... Version numbers (network transport) NETCONTROL VERSION Chapter 3, 7 Version numbers (network services) NSCONTROL VERSION Chapter 3, 7 Version numbers (NMS) NMMAINT.PUB.SYS Chapter 3 X.25 connection response X25CHECK NETTOOL Chapter 3, 6 X.
Overview of NS 3000/iX Operations Troubleshooting Your Network Troubleshooting Your Network From time to time you may experience problems on your network. Often, you can easily diagnose and correct the problems without the need to contact a Hewlett-Packard service representative. You may choose to perform some troubleshooting operations on your own, following the guidelines provided in this manual.
Operating Your Network 2 Operating Your Network During normal operations of your network, you will need to do little more than to start and stop the network links and services. You may also need to verify a communications link or perform a quick validation of a Network Service. This chapter provides instructions for using the provided tools or commands to perform the following operations: • Start network links and services. • Verify network connections and services. • Stop network links and services.
Operating Your Network Starting Links and Services Starting Links and Services You use the NETCONTROL START command to start the network links and the NSCONTROL START command to start the Network Services. You must start at least one link before you can start Network Services. When you start the first link, the network transport is initiated as well.
Operating Your Network Starting Links and Services where function is one of the following: STARTX25 to start X.25 services; STARTPADSUP to start PAD support services; STARTBOTH to start X.25 and PAD support services. For more information on starting host-based X.25 links as well as other uses of the DTCCNTRL command, see Configuring and Managing Host-Based X.25 Links. NOTE If you are starting an X.25 link for a system using PC-based network management or if you are not starting an X.
Operating Your Network Verifying Network Connections and Services Verifying Network Connections and Services Several line verification tests are available to help you verify the operation of NS 3000/iX services and link products. NSLOGON establishes temporary connections to other nodes to verify that the network transport is operating correctly between the two nodes using the connection.
Operating Your Network Verifying Network Connections and Services XPVAL Line Test Error Messages Error messages for the XPVAL line tests appear in inverse video at the system console. Some errors allow the test to continue, so they may scroll off the top of the terminal screen. Copy the error message information for further diagnosis. Error Message Categories Errors from the XPVAL line tests fall into the following categories: • Packet verification errors. • Send and receive failures.
Operating Your Network Verifying Network Connections and Services Send and Receive Failures Most Send and Receive failures are timing-related. They usually do not abort the tests.
Operating Your Network Verifying Network Connections and Services Miscellaneous Test Errors Certain errors may appear in all software line tests which do not fit in the categories described above. They are listed here. MESSAGE: PCERRMSG FAILED (SOCKERR #) SOCKERR # CAUSE: Error message could not be acquired from the message catalogue SOCKCAT.NET.SYS. ACTION: Ensure that the message catalog exists. Examine errors returned to the console before and after this error.
Operating Your Network Verifying Network Connections and Services 3. Enter QVALNS to run the Network Services validation in batch mode. 4. When prompted, enter the name of the destination node to which you want to connect. (This is the same as entering the command RUN QVALNS.NET.SYS;INFO=nodename outside of NETTOOL.) 5. QVALNS will stream a job that tests the network services. The program will display any errors encountered on the system console.
Operating Your Network Verifying Network Connections and Services 4. After NSTEST completes, purge the database to save space on your disk.
Operating Your Network Stopping Links and Services Stopping Links and Services You use the NSCONTROL STOP command to stop the Network Services and the NETCONTROL STOP command to stop the links and transport. You should always stop all Network Services before you stop the network transport. To Stop Network Services NSCONTROL STOP allows all processes that are currently using the services to end normally before the services are actually terminated.
Operating Your Network Stopping Links and Services The NIname is the network interface name that you configured through NMMGR. Stop other interfaces as required by entering the command using the appropriate NI names. To Stop All Network Interfaces When you enter the STOP command with no keywords, all entities of the network transport are terminated. (You must terminate the Network Services before stopping the network transport.
Operating Your Network Stopping Links and Services 38 Chapter 2
Getting Information About the Network 3 Getting Information About the Network A great deal of information about the network and network connections is available to you through use of various commands and tools provided by the network. This chapter describes the various types of information that you might need access to, describes the tools available for displaying the information, and provides step-by-step instructions for obtaining information where appropriate.
Getting Information About the Network Verifying Software Versions Verifying Software Versions Each data communications product consists of a variety of software modules. Each module has an individual version number. The software modules of all Hewlett-Packard data communications products use a standard version stamp, with the following format: v The version number of the software. This corresponds to a major revision or a version for a new or revised system environment.
Getting Information About the Network Verifying Software Versions 2. If the version, update, and fix levels of these modules do not match, the subsystem will not work correctly. Include the information provided by NMMAINT in any service request (SR) you submit to Hewlett-Packard. See Appendix B, “Submitting an SR,” for information about submitting SRs.
Getting Information About the Network Displaying Configuration Information Displaying Configuration Information You can display information about the location configuration file or network directory file using the CONFIGURATION SUMMARY available as part of NETTOOL. You can also use this tool to compare one configuration file to another. You can access information about configured network names and addresses using the NAME-ADDRESS MANAGER which is also available through NETTOOL.
Getting Information About the Network Displaying Configuration Information The root menu will appear. 2. Enter CONFIG to run the CONFIGURATION SUMMARY tool. The CONFIG menu will appear. 3. Enter NETDIR to display a summary of the network directory configuration.
Getting Information About the Network Displaying Status Information Displaying Status Information Using the various commands and utilities available to you, you can obtain status displays on nearly every aspect of NS 3000/iX. Status displays can help you identify the entities of your network that are currently active or in use. They can also help you diagnose deficiencies in the configured resources that are required for network traffic, such as transmission buffers.
Getting Information About the Network Displaying Status Information To Display Status of a NET To display the status of a NET configured as LAN1, enter the following command at the MPE prompt: NETCONTROL STATUS;NET=LAN1 To Display Status of an NI To display the status of an NI configured as LAN1, enter the following command at the MPE prompt: NETCONTROL STATUS;NI=LAN1 To Display Protocol Status You can display the status of a general protocol (TCP or PXP), or of a network interface protocol (PROBE, ARP,
Getting Information About the Network Displaying Network Performance Information Displaying Network Performance Information You can display network performance information using a number of the tools available through NETTOOL. LOOPINIT, RESOURCE MONITOR, and XPPERF all provide performance monitoring features.
Getting Information About the Network Displaying Network Performance Information THU, MAR 12, 1992, 9:23:39 AM Item Subsystem Name G/N 1 NS XPORT TCP_CNTL (G) 2 NS XPORT CP_POOL_ (G) 3 NS XPORT 1088____ (G) 4 NS XPORT ROUTER__ (N) 5 NS XPORT ROUTER__ (N) 6 NS XPORT ROUTER__ (N) 7 NS XPORT GPROT (G) 8 NS XPORT TCP_SIP (G) 9 NS XPORT UDP (G) 10 NS XPORT TCP_PM (G) 11 NS XPORT ROUTER__ (G) 12 NS XPORT IP_NI (G) 13 NS XPORT IP_NI (G) 14 NS XPORT (G) 15 NS XPORT (G) 16 NS XPORT (G) [4]RESOURCE>> Description Con
Getting Information About the Network Displaying Connection Information Displaying Connection Information The PING tool allows you to confirm the reachability of a remote node that supports the internet protocol. You can also use PING to estimate the round trip times before proceeding with lengthy transactions. If you send four or more bytes of data with the echo request, PING displays the round trip times in milliseconds.
Getting Information About the Network Displaying Connection Information 100 100 100 100 100 100 100 100 100 100 byte(s) byte(s) byte(s) byte(s) byte(s) byte(s) byte(s) byte(s) byte(s) byte(s) from from from from from from from from from from $0F0D833B $0F0D833B $0F0D833B $0F0D833B $0F0D833B $0F0D833B $0F0D833B $0F0D833B $0F0D833B $0F0D833B : : : : : : : : : : icmp_seq icmp_seq icmp_seq icmp_seq icmp_seq icmp_seq icmp_seq icmp_seq icmp_seq icmp_seq = = = = = = = = = = 1, time = 2, time = 3, time = 4,
Getting Information About the Network Displaying Connection Information Error and Information Messages In addition to the normal reply message details and statistics, PING can display informational and/or error messages. These messages are given below, with an explanation and action to be taken for each message. User Input Errors (Menu-Driven) MESSAGE: Invalid IP address. Press RETURN to quit. CAUSE: An IP address with invalid syntax has been entered for the IP address prompt.
Getting Information About the Network Displaying Connection Information MESSAGE: Invalid IP address. CAUSE: An IP address with invalid syntax has been entered in the INFO string. The correct syntax for an IP address is A.B.C.D—where A, B, C, and D are decimal numbers in the range 0–255. ACTION: Pass a valid IP address within the INFO string. MESSAGE: Invalid number of packets. Valid range: 1–65534 CAUSE: An invalid number of packets value has been passed in the INFO string.
Getting Information About the Network Displaying Connection Information MESSAGE: Cannot resolve path to remote. Path Error, Parm = #Parm_Value. Refer PATH RESULT CODES table in NS 3000/iX Error Messages Manual. CAUSE: A suitable path out of the local node to reach the remote node could not be found. ACTION: Look up the table mentioned in the message, under the Parm_Value code, and take the action recommended therein. MESSAGE: Arithmetic trap Parm. Program Quitting. CAUSE: This is an internal error.
Getting Information About the Network Displaying X.25 Information Displaying X.25 Information Several special tools are available to you for use with X.25 network connections. X25CHECK allows you to verify connectivity between two nodes on an X.25 network. X25STAT allows you to monitor the status and statistics for X.25 NIs. You can run both X25CHECK and X25STAT standalone or from within NETTOOL. Running them from NETTOOL allows you to access help information about the tools.
Getting Information About the Network Logging and Tracing Logging and Tracing Both logging and tracing services are available to you for use as diagnostic and debugging aids. Logging records subsystem events as selected by the way you have configured logging through NMMGR. Use logging in problem determination and in monitoring network usage and resources. Tracing is provided at both the user level and at an internal level.
Getting Information About the Network Logging and Tracing Network Service tracing is used to trace messages generated by your applications. For more information, see Using NS 3000/iX Network Services. You enable tracing for NetIPC applications with the NetIPC intrinsic IPCCONTROL, which is explained in the NetIPC 3000/XL Programmer’s Reference Manual. You can selectively enable tracing for the network transport with the NETCONTROL command (see Chapter 7, “Commands,”).
Getting Information About the Network Logging and Tracing Host-Based X.25 Links for information on using the EVLOG formatter. If you are logging messages for an X.25 link with PC-based network management, see Using the OpenView DTC Manager for information.
Troubleshooting Process 4 Troubleshooting Process Troubleshooting data communications problems can be a very involved process since there are many hardware and software components to investigate. You will be able to quickly identify and resolve some problems, however. These include invalid software installation, version incompatibilities, insufficient MPE/iX resources, corrupt configuration files, programming or command errors, and file system errors. Other problems will require more investigation.
Troubleshooting Process To Identify Problems To Identify Problems The usual method of identifying problems is to characterize the situation in which the problem occurs and then investigate which of the possible causes are actually responsible for the problem. Finding the cause is often sufficient to suggest the resolution of the problem. For example, assume that the problem is characterized as “the user is unable to open a line with the DSLINE command.
Troubleshooting Process To Identify Problems 6. If more than one user is involved, does the problem affect all users? The entire node? If so, has anything changed recently? Some possibilities are: • New software and hardware installation. • Same hardware but changes to the software. Has the configuration file been modified? Has the MPE/iX configuration been changed? • Same software but changes to the hardware. 7.
Troubleshooting Process To Identify Problems Figure 4-1 Characterizing the Problem 60 Chapter 4
Common Network Problems 5 Common Network Problems This chapter presents strategies for dealing with some of the more common network problems. Once you have characterized a problem and identified a possible cause using the troubleshooting guidelines provided in Chapter 4, “Troubleshooting Process,” find the problem in this chapter and follow the strategy presented here to resolve the problem.
Common Network Problems Interactive or Programmatic Problems Interactive or Programmatic Problems The first step in investigating interactive or programmatic problems is to examine any error message returned. If you have received a specific error message, find it in the NS 3000/iX Error Messages Reference Manual and take the action recommended.
Common Network Problems Command Errors Command Errors If you are using the interactive capabilities of NS 3000/iX and associated links and receive an error, refer to “NS 3000/iX Network Services Error Messages” in the NS 3000/iX Error Messages Reference Manual. The command errors fit into four categories: • Syntax errors or invalid options. These errors result from user errors when issuing the command. They are readily corrected by checking for the correct syntax and reissuing the command. • Warnings.
Common Network Problems Command Errors • A network was not started by the local console operator, the remote console operator, or any intermediate nodes. Check that all required commands have been issued on the local, remote, and intermediate nodes. The network interfaces, the LAN NI, the loopback NI, point-to-point NI, X.25 NI, token ring NI, and gateway half NI, must be initialized with NETCONTROL START commands. The DTC/X.
Common Network Problems Command Errors • A REMOTE HELLO, DSCOPY or RPMCREATE will fail if the IP address of the remote node configured in the network directory does not match the IP address of the remote node configured in the NS Configuration file. • All virtual terminals on the remote node are already in use, which means there are no remote resources available to establish a remote session.
Common Network Problems Nodal Problems Nodal Problems The first step in investigating nodal problems is to examine any error message returned. Error messages returned by NS 3000/iX and associated links are listed in the NS 3000/iX Error Messages Reference Manual, along with their meaning and recommended recovery action. If you have received a specific error message, find it in the manual and take the action recommended.
Common Network Problems Nodal Problems Table 5-1 Nodal Troubleshooting Strategy Changes New installation Symptom Possible Causes Console locked or hung;serious failures. Software installation invalid. System abort Configuration incorrect, serious internal error. System abort Configuration incorrect, serious internal error. DSCOPY command aborts. NFTCAT.NET.SYS is bad; incompatible version, or MAKECAT was not done. Hardware changes Unable to use NS.
Common Network Problems Investigate the Link Investigate the Link The following is a strategy to use to identify and solve link problems. You should use this strategy if you are not sure what is causing the problem because many times errors in the upper level software are due to hardware problems. You can also use this strategy if you have identified a hardware-related possible cause and need to isolate the actual cause.
Common Network Problems Investigate the Link If the problem is easily reproducible, and link level tracing was inactive when the problem took place, turn on tracing using the LINKCONTROL command. When the problem has been reproduced, turn off trace and give this trace file to your Hewlett-Packard representative for additional analysis. If a hardware failure takes place while trace is active, give the files NMLGxx.PUB.SYS and NETDMPnn.PUB.SYS to your HP representative as well.
Common Network Problems Investigate the Link created while link level tracing was enabled. Send both the PSI dump file and the link trace file to your Hewlett-Packard representative for additional analysis. • Check the MPE/iX log file for I/O error logging. Format the log file. Keep a copy of the file and the output for your Hewlett-Packard representative to study.
Common Network Problems Investigate the Software Investigate the Software Follow the strategy described below to identify and solve any problems that might involve software. • There may be version incompatibilities between different software subsystems. This is essential to check for if new software has recently been installed on your node. Use the software verification utility NMMAINT to display the version identification numbers of the software modules.
Common Network Problems Investigate the Software • If the problem causes a system failure, take a full memory dump of the system. Format the system dump with the Dump Analysis Tool (DAT) and send the formatted tape to your HP representative.
Common Network Problems Common Problems and Actions Common Problems and Actions Invalid Software Installation A software installation may be invalid. Run NMMAINT.PUB.SYS to obtain a listing of version IDs for NMS and for all of the NMS dependent subsystems. Locate the overall version IDs for each subsystem. Check that these subsystems are the correct version for operation with the associated link.
Common Network Problems Common Problems and Actions After recovering the file, stop and restart the network transport as described in Chapter 2, “Operating Your Network,” of this manual. Incompatible Configuration File Version Run the NMMGRVER.PUB.SYS program to convert the old configuration file to the new format. Refer to the Using the NMS Utilities manual for more information.
Common Network Problems Common Problems and Actions If a retransmission error is returned in a log message or in an IPCCHECK error code for NetIPC applications, first check that the remote node is up and that its transport has been started. If so, check if the retransmission timeout error is an isolated event or an ongoing problem. Examine a formatted log file for the period up to and including the error.
Common Network Problems Common Problems and Actions is shut down. As a result, the processes that share a connection must cooperate to ensure that no data is lost. Indications of a faulty shutdown procedure on an individual or application level are: • If you receive log messages or NetIPC error codes where the recommended action for some of the log messages is to increase the number of TCP connections, and the connections are not currently active.
Using NETTOOL 6 Using NETTOOL The NETTOOL utility allows you to run a complete set of networking diagnostic programs under a common user interface. It provides help information on its commands and on its core functions. It also allows you to add your own applications, so that you can perform diagnostic operations common to your site while taking advantage of the NETTOOL user interface and facilities. This chapter describes NETTOOL and its operation.
Using NETTOOL The NETTOOL Tools The NETTOOL Tools Each of the NETTOOL tools provides a specific functionality that will assist you in troubleshooting network problems, monitoring resources, or simply accessing information about your network and its operations. Types of Tools There are three types of tools that run in the NETTOOL environment. Core tools and Associated tools are provided by Hewlett-Packard and are always available to you.
Using NETTOOL The NETTOOL Tools Table 6-1 Differences in Tool Types Core Associated User Consistent user interface Yes No No Access NETTOOL help within tool Yes No No Use NETTOOL global commands Yes No No Control-Y recognized Yes Tool dependent Tool dependent Run standalone No Yes Yes HP factory support Yes Yes No Available Tools Table 6-2 summarizes the tools available in NETTOOL, the type of each tool, and the function of each tool.
Using NETTOOL The NETTOOL Tools Tool Type Function SOCKINFO Associated Displays socket information. STATUS Core Displays the status of the network interfaces and the associated links. X25CHECK Associated Creates connections to remote X.25 nodes and verifies their response. X25STAT Associated Monitors the status and statistics for X.25 network interfaces. Also displays internal data structures. XPPERF Associated Provides a cursory performance measurement.
Using NETTOOL Using NETTOOL Using NETTOOL You can run NETTOOL either interactively or through a batch job. In interactive mode, you can take advantage of the flexibility provided by the NETTOOL menu structure. You can also access the available help information. If you need to perform a simple operation, however, you might choose to run in program mode, passing the information required to run the tool you have chosen in the run command.
Using NETTOOL Using NETTOOL If the same command is available in several menus, the help information you see will be the information that pertains to the way the command operates for the current menu. Abbreviations are not allowed for the command name.
Using NETTOOL Using NETTOOL DO Execute a specific command from the redo stack, using the syntax DO commandnumber. If no commandnumber is specified, execute the previous command. EXIT Step back one level in the command menus. If you enter this command from the root level, NETTOOL will prompt you to determine if you really meant to quit. HELP See a list of commands available. HELP ALL View all the help text for the current menu. HELP BROWSE Browse through the entire help file for all of NETTOOL.
Using NETTOOL Using NETTOOL REDO Make changes to last command and then execute the command again. You can choose a command from the redo stack by specifying its command number using the syntax REDO commandnumber. The “d”, “i”, and “r” edit commands are allowed as well as direct replacement. SETVAR Set variable to given value using the syntax SETVAR variable value. SHOWVARS Show the variables in use. VERSION Display the revision numbers of NETTOOL modules and of the NS transport.
Using NETTOOL Using NETTOOL Keep the following in mind when running NETTOOL in batch mode: • Be sure to consider any optional parameters. For example, if an output file for a command might already exist, you will need to tell the program whether or not to purge it. • Help is not available on the commands or user tools if an INFILE is active.
Using NETTOOL Using the NETTOOL Tools Using the NETTOOL Tools The following sections describe each of the available tools and provide information on their use. You can access additional information from within NETTOOL by asking for help on the tool from the main menu. NOTE You can use abbreviations for the NETTOOL commands. The abbreviations must uniquely identify the command at the current menu.
Using NETTOOL Using the NETTOOL Tools filters This option displays the current values of the global filters, conffile, altfile, and subtree, as well as the current settings of the global filters. conffile Use this option to select a configuration file for the SUMMARY and COMPARE options. altfile Use this option to select an alternate file for the COMPARE option. subtree Allows you to specify a subset of records to be compared by the COMPARE option. For example, if you specify NETXPORT.NI.
Using NETTOOL Using the NETTOOL Tools To Use IPCINT The IPCINT tool provides a command interface to IPC. To use this tool, perform the following steps. 1. Run NETTOOL by entering the program name at the MPE prompt: NETTOOL.NET.SYS The root menu will appear. 2. Select the IPCINT tool from the main menu. 3. Enter a NetIPC intrinsic abbreviation. You will be prompted for any parameters required by the intrinsic. 4. To exit the tool, type ex at the prompt.
Using NETTOOL Using the NETTOOL Tools To Use NAME-ADDRESS MANAGER The NAME-ADDRESS MANAGER tool provides options that let you display the local cache of node names and addresses. This tool is useful in detecting duplicate IP addresses and permits you to clear entries in the name cache if necessary. To use this tool, perform the following steps. 1. Run NETTOOL by entering the program name at the MPE prompt: NETTOOL.NET.SYS The root menu will appear. 2.
Using NETTOOL Using the NETTOOL Tools between 0 and 255 separated by periods or blanks (for example, 15.123.44.98). MAPPINGS Select this item to obtain information about the correspondence between IP addresses and link addresses or to delete mappings from the table. A new menu will appear presenting you with the choices as described: MAPPING Select to display all mappings between IP address and link address for those entries selected by subnetfilter and addrfilter.
Using NETTOOL Using the NETTOOL Tools GATELIST ??????? GATE UP ?????? GATE DOWN ?????? STATISTICS ?????? TOTALS Select to display total number of routings. filters Select to see current filter settings for this menu. Also displays the global settings (INFILE, OUTFILE, messages flag, data flag, and menus flag). networkfilter Select to set the networkfilter. Enter a single IP address or @ for all.
Using NETTOOL Using the NETTOOL Tools NOTE You cannot use NMDUMP to format X.25 log or trace files. For information on X.25 logging and tracing, refer to Using the OpenView DTC Manager for PC-based systems or to Configuring and Managing Host-Based X.25 Links for host-based systems. Perform the following steps to format records from the current log file. 1. At the MPE prompt, enter the SHOWNMLOG command to obtain the name of the current log file. Record this name.
Using NETTOOL Using the NETTOOL Tools 4. When prompted, enter the name of the destination node to which you want to connect. 5. When prompted, enter a logon string for the destination node. Enter other values as required. The tool will test the Network Service you selected. 6. Test other services as required. To Use NSLOGON The NSLOGON tool allows you quickly verify that the network transport is operating correctly.
Using NETTOOL Using the NETTOOL Tools PING This option sends ICMP echo requests to remote systems. On receiving the ICMP echo replies, the program displays the number of packets sent and received and the time that it took each packet to complete the round trip. You can specify the destination by name or by IP address. If you specify by name, you can choose a single node or a set of nodes by using wildcards (@, #, and ?). If you specify by address, the ping will go to that specific address.
Using NETTOOL Using the NETTOOL Tools 2. Run the NETTOOL utility by entering the program name: NETTOOL.NET.SYS The root menu will appear. 3. Enter QVALNS to run the Network Services validation in batch mode. 4. When prompted, enter the name of the destination node to which you want to connect. (This is the same as entering the command RUN QVALNS.NET.SYS;INFO=nodename outside of NETTOOL.) 5. QVALNS will stream a job that tests the network services.
Using NETTOOL Using the NETTOOL Tools item Use to select a particular item from the one-line display so that you can obtain detailed information on that item. refresh Use to set the number of times the program will display resource usage before returning control to you. Default is one cycle. ([CONTROL]-Y will also return control.) type Use to select which resource types the program will display in the one-line (non-verbose) mode. Default is to display all resource types.
Using NETTOOL Using the NETTOOL Tools 79 spool,unispool.sys system3.unispool.sys j138 de208 2 80 spool,unispool.sys system6.unispool.sys j138 de202 0 81 spool,unispool.sys system6.unispool.sys j138 de202 1 82 spool,unispool.sys system3.unispool.sys j138 de206 0 : etc... veruser.nmpascal vtserver.net.sys s570 lq152 1 447 --------------------------------------------------------------------------Totals: 153 processes, including 1 locked semaphore; 177 sockets. 4.
Using NETTOOL Using the NETTOOL Tools Y Define new timeout value, in seconds. (Default is 0 : disabled) 5. To return to NETTOOL, type E. To Use STATUS The STATUS tool provides options that let you display the status of the network interfaces and their associated links. To use this tool, perform the following steps. 1. Run NETTOOL by entering the program name at the MPE prompt: NETTOOL.NET.SYS The root menu will appear. 2. Select the STATUS tool from the main menu by entering the STATUS command.
Using NETTOOL Using the NETTOOL Tools PROBESTAT Use to display probe statistics for inbound and outbound packets for the network specified by niname. If you have not set niname, you will see statistics for all NIs. ARPSTAT Use to display ARP statistics for the network specified by the niname command. If you have not set niname, you will see statistics for all NIs. UDPSTAT Use to display global UDP statistics or to report UDP sockets statistics information for the network specified by niname.
Using NETTOOL Using the NETTOOL Tools To Use X25CHECK The X25CHECK tool creates connections to remote X.25 nodes and verifies their response. It also provides information that allows estimation of the performance of the network and its load. The remote node runs a background program, X25SERVR, that responds to X25CHECK. To use this tool, perform the following steps. 1. Run NETTOOL by entering the program name at the MPE prompt: NETTOOL.NET.SYS The root menu will appear. 2.
Using NETTOOL Using the NETTOOL Tools To Use XPPERF The XPPERF tool measures the performance of the TCP/IP protocol stack, the UDP/IP stack, or X.25 level 3 direct access. The program interfaces to the transport through the IPC intrinsics. You must run XPPERF on both the local system and a remote system for the test to work, with the program on the remote system started first. To use this tool, perform the following steps. 1.
Using NETTOOL Using the NETTOOL Tools 3. XPVAL will prompt you for information it needs to run the validation. Respond as required. 4. Make sure XPVAL is running on the remote node as well and have the remote user enter information about the remote node. 5. XPVAL will run a one minute connection test to verify the operation of the transport and report any errors it encounters. See Chapter 2, “Operating Your Network,” for a list of XPVAL line test error messages.
Using NETTOOL Adding Your Own Tools Adding Your Own Tools You can add you own diagnostic tools to by following some simple rules. You can also provide help information on the user-provided tools. To Add User Tools Information needed to run a user-provided tool must reside in USERINFO.NET.SYS. You can create this file with any text editor. It must have a record length of 80 characters or less. You can describe up to 20 user tools in the file.
Using NETTOOL Adding Your Own Tools To Add User Provided Help To provide help on user tools, you must create the file USERHELP.NET.SYS. This file should contain help text for all user tools defined in USERINFO.net.sys. Use the following format for help text: 1. There must be an \ENTRY=ROOT block which gives a one word list of the user-defined NETTOOL commands. These commands are the same as those defined in USERINFO.NET.SYS.
Using NETTOOL Adding Your Own Tools rename helpcat,userhelp.net.sys reset input Here, sourcefilename is your unformatted help file and helpcat is the file name reserved by MAKECAT for its output.
Using NETTOOL Adding Your Own Tools 106 Chapter 6
Commands 7 Commands This section describes the NS 3000/iX network commands for the NS 3000/iX services and associated links. The commands are listed in alphabetical order and described in Table 7-1. NOTE You must have NM capability to execute any of the following commands. Table 7-1 NS 3000/iX Network Commands Command Description LINKCONTROL Provides link information, or activates or deactivates link level tracing. LINKCONTROL STATUS Requests status information about the link.
Commands Command Description NSCONTROL LOADKEYS Loads the Network Services command keywords. Used for localization. NSCONTROL LOG Enables or disables detailed logging (configured as CLAS0004 of SUB0006) for the Network Services. NSCONTROL SERVER Alters the characteristics of the Network Services server processes. NSCONTROL START Initiates the Network Services. NSCONTROL STATUS Displays status information about the Network Services.
Commands LINKCONTROL LINKCONTROL Activates or deactivates link level tracing on a specified communications link. Provides link transmission error statistics and/or configuration information.
Commands LINKCONTROL command and its parameters can be found in Appendix A, “LINKCONTROL Command.” CONFIGURATION Prints the information displayed by the LINKSTATE parameter along with link configuration information for the link. The link configuration data consists mainly of the configuration information that was input for this link during NMMGR configuration. The fields that are displayed by this parameter are described in Appendix A, “LINKCONTROL Command.
Commands LINKCONTROL ON Turns link level tracing on. OFF Turns link level tracing off. Any subsequent subparameters are checked for syntax but are otherwise ignored. DATA (LAN and token ring links only) Traces all read and write requests. If neither DATA nor ALL is specified, DATA is the default. ALL (LAN and token ring links only) Traces all read, write, control, status, and exception requests. PARTIAL (Point-to-Point only) Trace all read, write, control, status, and exception requests.
Commands LINKCONTROL Discussion The LINKCONTROL command returns link statistics and configuration information or activates or deactivates link level tracing on the specified link. The NMCONFIG.PUB.SYS and the link must be active for this command to be operative. If a trace option that is inapplicable for a certain link is specified for that link, then the default for that link type will be used. The LINKCONTROL command does not work on an X.25 link because the link is in the DTC.
Commands NETCONTROL NETCONTROL Command used to initialize, terminate, and control the operation of the network transport. Syntax {function}[;function] NETCONTROL {entity }[;entity ] Use Available In Session? YES In Job? YES In Break? NO Programmatically? YES Breakable? NO Capabilities? NM Parameters function Only one of each type of function is recommended on a command line. Refer to function descriptions on the following pages.
Commands NETCONTROL GATE Specifies a group entity that consists of a configured gateway half network interface, and all the protocol modules that are configured for that network interface. Not all functions may be applied as a group; see the individual command functions for details. Note: This keyword cannot be used to select true “gateways” as configured in the INTERNET subtree under a network interface.
Commands NETCONTROL Figure 7-1 The NETCONTROL Entities Chapter 7 115
Commands NETCONTROL Example This example illustrates how each NETCONTROL command is used. See individual commands for further details and examples.
Commands NETCONTROL ADDLINK NETCONTROL ADDLINK Dynamically adds a configured network link to the active network interface. Syntax NETCONTROL ADDLINK=linkName; {NET=niName } {GATE=gatehalfName} Parameters ADDLINK=linkName Specifies the name of the link to be dynamically added to the specified active NI. The linkname must be a valid NI link name configured in the NMMGR Link Selection screen and also in the Network Interface Links screen under the specified “niname” or “gatehalfname” NI.
Commands NETCONTROL ADDLINK This function is mainly used with router NI types.
Commands NETCONTROL DELLINK NETCONTROL DELLINK Dynamically deletes a configured network link from the active network interface. Syntax NETCONTROL DELLINK=linkName; {NET =niName } {GATE=gatehalfName} Parameters DELLINK=linkName Specifies the name of the link to be dynamically deleted from the specified active NI. The linkname must be a valid NI link name configured in the NMMGR Link Selection screen and also in the Network Interface Links screen under the specified “niname” or “gatehalfname” NI.
Commands NETCONTROL DELLINK terminate if other links are still bound. The network interface and its protocols remain active until that NI is stopped using the NETCONTROL STOP command. This function is mainly used with router NI types.
Commands NETCONTROL START NETCONTROL START Initiates the network transport, including the control process, general protocols, network interfaces, and their protocols. Also initiates individual network interfaces on an active transport. Syntax NETCONTROL START [;{NET=niName }] {GATE=gatehalfName} Parameters START This function, if issued when transport is not active, initializes the control process and general protocols.
Commands NETCONTROL START Discussion In order for internetwork communications to be possible, you must activate at least one network interface using the NET keyword. When this command is entered with an X.25 NI name, the system accesses the DTC/X.25 Network Access subsystem to verify that the X.25 line is started. If the line is not started, the command fails. If the X.25 line is started, the command is successfully completed if everything is correct. This enables the X.
Commands NETCONTROL START example show creation of the general protocols. The START function always creates the control process and the general protocols, if they do not already exist, before acting on any of the other entities. :NETCONTROL STATUS TRANSPORT NOT ACTIVE. (NETXPORTWARN 0001) ENCOUNTERED ONE OR MORE WARNINGS WHILE PROCESSING COMMAND.
Commands NETCONTROL START ** NETXPORT Map Tbl; Mapping Table Created - Loc: 1; Class: 4; Parm= $95C80250; PortID: $95C80250 ** NETXPORT LAN NI; Network interface start - Loc: 28; Class: 4; Parm= $95CC8000; PortID: $FFFFFE88 ** NETXPORT IP; Protocol start - Loc: 102; Class: 4; Parm= $D4FD8000; PortID: $FFFFFE84 ** NETXPORT Probe; Protocol start - Loc: 35; Class: 4; Parm= $00000000; PortID: $FFFFDFF3 ** NETXPORT ARP; Protocol start - Loc: 3; Class: 4; Parm= $00000000; PortID: $FFFFDFF5 Example 5 Example 5 sh
Commands NETCONTROL STATUS NETCONTROL STATUS Displays status and configuration information for the transport entity specified. Syntax NETCONTROL STATUS[=ALL] [;{NI=niName [;PROT=niProt]} ] {NET=niname } {GATE=gatehalfname } {PROT=gProt } Parameters STATUS[=ALL] Specifies that any additional status information should be displayed, if additional data is available beyond the default. NI=niname Specifies the name of a configured network interface to display the status of.
Commands NETCONTROL STATUS IPU. If the specified protocol did not start or is not one of these inputs, an “ENTITY NOT ACTIVE” error will occur. If transport was not previously started, a “TRANSPORT NOT ACTIVE” warning will occur. Specifies the name of one network interface protocol to display the status of; must be used in conjunction with the NI=niname parameter. Valid inputs depend on the NI type, according to the table below.
Commands NETCONTROL STATUS NOTE HP does not recommend combining this function on the same command line as other functions, in an attempt to determine if the other function worked. NOTE The output format of all NETCONTROL commands is subject to change without notice. Programs which are developed to postprocess NETCONTROL output should not depend on the exact format (spacing, alignment, number of lines, upper or lower case, or spelling) of any NETCONTROL command output.
Commands NETCONTROL STATUS TRACE MASK : $00000000 DEVICE INFORMATION : DEVICE DEVICE TYPE LINK BUFFER SIZE PROTOCOLS CONNECTED PHONE NUMBER INDEX TRAN PORT INFO : : : : : : SYSLINK (# 0) $000005EA $00000004 $00000000 PORT ID $FFFFFF20 Example 3 Example 3 is a sample of the output that is displayed when the NETCONTROL STATUS command is issued and the LAN1 network interface and the PROBE protocol are specified.
Commands NETCONTROL STATUS Example 5 Example 5 is a sample of the output that is displayed when the NETCONTROL STATUS command is issued and the LAN1 network interface and the ARP protocol is specified.
Commands NETCONTROL STOP NETCONTROL STOP Terminates individual network interfaces on an active transport, or the entire transport and all its network interfaces. Syntax NETCONTROL STOP [;{NET=niName }] {GATE=gatehalfName} Parameters STOP This function, if issued without parameters when transport is active, irrecoverably stops the entire transport.
Commands NETCONTROL STOP When this command is entered with an X.25 NI name, the system accesses the DTC/X.25 Network Access Subsystem to disable the X.25 address that is associated with this system. The DTC/X.25 Network Access then no longer accepts connections for this system. There is no impact on the connections established between any other systems and the DTC/X.25 Network Access. Example 1 Example 1 shows how NETCONTROL fits into the process of terminating a node.
Commands NETCONTROL STOP Example 3 Example 3 shows what happens if the general transport and both network interfaces are active, and the user specifies the Loopback NI. Notice that the STOP function acts only on the Loopback NI entity. The general transport is still active.
Commands NETCONTROL TRACEON and TRACEOFF NETCONTROL TRACEON and TRACEOFF Enables or disables message tracing for the specified transport entity.
Commands NETCONTROL TRACEON and TRACEOFF NOTE Tracing to tape is no longer available on MPE/iX. filename (Optional). The name of the file to which trace data will be written. The default is to automatically create the next highest numbered NMTCnnnn.PUB.SYS file, where nnnn is a 4-digit number, for each TRACEON command entered. If you wish several TRACEON commands to trace to the same file, you must specify that filename using this parameter. You may choose an automatically created file for this purpose.
Commands NETCONTROL TRACEON and TRACEOFF NET=niName Specifies the name of a configured network interface which is not a gatehalf. Enter any valid NI name, as configured with NMMGR. Using this parameter, the function applies only to the network interface itself, not to any attached protocols. GATE=gatehalfname Specifies the name of a configured gateway half network interface to start tracing on. Enter any valid gatehalf NI name from the NMMGR Network Interface Configuration screen.
Commands NETCONTROL TRACEON and TRACEOFF NI Type: Valid Network Interface Protocol Names LAN IP, PROBE, ARP TOKEN IP, ARP FDDI IP, ARP 100VG-AnyLAN IP, PROBE, ARP 100Base-T IP, PROBE, ARP ROUTER IP, DIAL X.25 IP, X25 GATEHALF IP, DIAL LOOP IP Discussion The tracing functions allow you to enable collection of internal information about what the various transport modules are doing, or what packets are being sent and received at the transport level.
Commands NETCONTROL TRACEON and TRACEOFF Example To enable TCP tracing, enter :NETCONTROL TRACEON=MHD; PROT=TCP TRACE FILE IS NMTC0128.PUB.SYS. (NETXPORT 2000) To disable TCP tracing, enter :NETCONTROL TRACEOFF; PROT=TCP To enable control process tracing, TCP tracing, and IP tracing on the “LAN1” NI, all to the same file, enter :NETCONTROL START; NET=LAN1 :NETCONTROL TRACEON=MHDSBN TRACE FILE IS NMTC0129.PUB.SYS. (NETXPORT 2000) :NETCONTROL TRACEON=MHD,DISC,NMTC0129.PUB.
Commands NETCONTROL UPDATE NETCONTROL UPDATE Dynamically updates selected network transport parameters and configuration information. Syntax {INTERNET} {MAPPING } NETCONTROL UPDATE= {NETDIR }; {NET=niName } {X25 } {GATE=gatehalfName} {ALL } Parameters {INTERNET} {MAPPING } UPDATE = {NETDIR } {X25 } {ALL } Specifies which configuration areas will be dynamically updated. The areas possible depends on the network type.
Commands NETCONTROL UPDATE Address Key Paths screen, to the specified X.25 network interface’s mapping table and X.25 protocol module. This allows adding new SVC destinations or adding a new node to the L.U.G. (Local User Group) table. Valid for X.25 NI types only. ALL The control process will update all areas which apply to the specified network interface or gateway half's type. Areas not supported for that NI type will not be updated. Updating will occur in this order: INTERNET, MAPPING, NETDIR, X25.
Commands NETCONTROL UPDATE Table 7-2 NETCONTROL Update NI Type NOTE Valid Update Options LAN INTERNET, NETDIR, ALL TOKEN INTERNET, NETDIR, ALL FDDI INTERNET, NETDIR, ALL 100VG-AnyLAN INTERNET, NETDIR, ALL 100Base-T INTERNET, NETDIR, ALL ROUTER INTERNET, MAPPING, ALL X.25 INTERNET, X25, ALL GATEHALF INTERNET, ALL LOOP ALL Dynamic updating is additive, so obsolete data can accumulate, possibly resulting in table overflows.
Commands NETCONTROL VERSION NETCONTROL VERSION Displays the version numbers for the network transport software modules. Syntax NETCONTROL VERSION[=MOD] Parameters VERSION[=MOD] Displays the overall version of the network transport. If qualified with the MOD keyword, displays the version of each of the software modules of the network transport and the overall version.
Commands NETCONTROL VERSION NL procedure: Catalog file: CM program file: NL procedure: NL procedure: NM program file: Catalog file: SL procedure: SL procedure: NL procedure: SL procedure: NL procedure: SL procedure: NM program file: SL procedure: NL procedure: NL procedure: NL procedure: SL procedure: SL procedure: NL procedure: SL procedure: NL procedure: SL procedure: NL procedure: NL procedure: NL procedure: NL procedure: SL procedure: SL procedure: NL procedure: NL procedure: NL procedure: NL procedure:
Commands NSCONTROL NSCONTROL Initiates, terminates, and controls the Network Services subsystem of NS 3000/iX. Syntax NSCONTROL function[;function]… Use Available In Session? YES In Job? YES In Break? YES Programmatically? YES Breakable? NO Capabilities? NM Parameters function Only one of each type of function is recommended on a command line. Refer to function descriptions on the following pages.
Commands NSCONTROL Network Services or any NetIPC application can successfully execute. NetIPC depends on the network transport to identify sockets and exchange messages. Refer to the NETCONTROL START command, also described in this section.
Commands NSCONTROL ABORT NSCONTROL ABORT Immediately terminates all the servers and services of the Network Services. Syntax NSCONTROL ABORT Parameters ABORT Immediately terminates all NS servers and services without allowing existing processes to run to completion. Useful in cases where you need to terminate Network Services immediately regardless of whether or not existing processes terminate normally. Note that STOP is the normal way to shutdown Network Services.
Commands NSCONTROL ABORT Example 1 Issue a message to all users to stop using the Network Services. Use whatever method is appropriate for your installation. Then use the following to terminate the Network Services: NSCONTROL ABORT Prevents any users or programs from accessing Network Services. Example 2 If a remote session has been terminated by the user but still shows as active on a SHOWJOB display, use ABORTJOB to terminate the session.
Commands NSCONTROL AUTOLOGON NSCONTROL AUTOLOGON Enables or disables the autologon feature of certain NS 3000/iX services. Syntax NSCONTROL AUTOLOGON=[{ON } [,ALL]] [{OFF} [,service[,service]...] Parameters AUTOLOGON Enables or disables the automatic logon feature available with the NFT, RFA, and RPM services. If AUTOLOGON is not enabled, users must create a remote session with the REMOTE HELLO command prior to executing these services. ON Enables autologon for an NS 3000/iX service.
Commands NSCONTROL AUTOLOGON without executing logon UDC’s. With autologon disabled, remote users must first establish a remote session with the REMOTE HELLO command, and thus execute any preset logon UDC(s), before using an NS 3000/iX service. It is recommended that users with security logon UDCs disable autologon for all services in order to preserve the security of the system from remote users.
Commands NSCONTROL LOADKEYS NSCONTROL LOADKEYS Loads the Network Services command keywords. Syntax NSCONTROL LOADKEYS Parameters LOADKEYS Loads the Network Services command keywords from the ASCAT.NET.SYS catalog. You need to use this command only if the catalog is modified, such as for localization. Discussion The LOADKEYS function is only used to switch between pre-prepared ASCAT.NET.SYS catalogs.
Commands NSCONTROL LOG NSCONTROL LOG Enables or disables detailed event logging for the Network Services. Syntax [{,ALL } ] {ON } [{,RPM } {,LOW} ] NSCONTROL LOG={OFF} [{,ENV } {,HIGH}] [{,DSDAD } ] [{,VTSERVER} ] [{,DSSERVER} ] Parameters LOG Enables or disables NMS logging of Network Services detailed events, configured as SUB0006, CLAS0004 in the NMCONFIG.PUB.SYS configuration file. Detailed events are only used for troubleshooting and are normally disabled.
Commands NSCONTROL LOG HIGH—Same as LOW, plus all received service requests and internal messages between DSDAD and server processes. VTSERVER LOW—Logs internal initialization messages between DSDAD and user processes. HIGH—Same as LOW, plus all received messages from other processes. DSSERVER LOW—Logs internal initialization messages between DSDAD and user processes. HIGH—Same as LOW, plus all received messages from other processes.
Commands NSCONTROL SERVER NSCONTROL SERVER Alters the characteristics of the Network Services server processes. Syntax {servername} NSCONTROL SERVER= {ALL }[,minservers][,maxservers] Parameters SERVER Dynamically alters the minimum or maximum number of servers. serverName Specifies the type of server for which you want to alter the available number of server processes.
Commands NSCONTROL SERVER There may be additional servers to control if other network products, such as Personal Productivity Center, are installed. Refer to that network product’s documentation to obtain the appropriate server names. minservers The minimum number of servers which will be in existence at all times. This includes active and reserved servers. These servers are created immediately on the initiation of Network Services and are then kept in reserve until a service request is received.
Commands NSCONTROL SERVER the Network Services. If there are more concurrent users than the minimum number of servers specified, new users can use the Network Services, but there is a delay while the additional servers are created. There is no simple formula for determining how many precreated servers to specify.
Commands NSCONTROL SERVER Example If you execute the following command, there will be 10 server processes created for NFT, 10 for VTSERVER, 10 for DSSERVER, 10 for LOOPBACK, and 10 for NSSTATUS. Later, when users issue service requests (such as DSCOPY and REMOTE HELLO), they do not have to wait for the servers to be created. The maximum number of servers is unchanged.
Commands NSCONTROL START NSCONTROL START Enables the Network Services. Syntax NSCONTROL START[=service[,service]…] Parameters START[=services] Enables the Network Services (VT, Reverse VT, NFT, RFA, RDBA, RPM, LOOPBACK, and NSSTAT). The first START creates the Network Services control process, called DSDAD. The optional service list (services) allows you to select which of the services are enabled for local or remote use.
Commands NSCONTROL START VTA Allows remote users who are running the Virtual Terminal service over TCP implementations which only support the ARPA standard stream mode flow control mechanisms to log onto the local node. The services which allow users on the local node to use resources on remote nodes are: NFTL Allows local users to transfer files to or from remote nodes using the DSCOPY command and intrinsics.
Commands NSCONTROL START Example 1 Example 1 shows the command sequence necessary to start the Network Services. Enter the NETCONTROL START command to initiate the network transport before the NSCONTROL START command, as shown in the example. Issuing the NSCONTROL START creates the DSDAD process and starts all the user services. To successfully initialize a node, the commands must be issued in the order specified.
Commands NSCONTROL START Example 3 The network transport must be initialized before you can issue the NSCONTROL START command. If not, the error messages shown in example 3 are displayed.
Commands NSCONTROL STATUS NSCONTROL STATUS Displays information about the Network Services. Syntax [=USERS ] [=SERVICES] NSCONTROL STATUS [=SERVERS ] [=ALL ] [=SUMMARY ] Parameters STATUS Displays information about the Network Services. Can be used to check if the Network Services were successfully initiated, or to check on the current status using the following parameters: USERS Displays the sessions on the node that are associated with the Network Services.
Commands NSCONTROL STATUS Example 1 The following example shows the status of the Network Services. Local means the service gives local users access to remote resources; remote means the service gives remote users access to local resources. Server indicates the type of server, NFT or DSSERVER, used for the service. For this example, all the services were started as indicated by YES in the STARTED column of the display. A NO in that column would indicate that the service was not started.
Commands NSCONTROL STATUS 49 41 58 57 NFT DSSERVER 0 0 300 300 0 0 0 0 TOTAL NUMBER OF ACTIVE SERVERS: TOTAL NUMBER OF RESERVED SERVERS: TOTAL NUMBER OF SERVERS: RESERVED RESERVED RESERVED RESERVED OFF OFF 1 5 6 Example 3 In example 3, assume that a user has entered the following commands on NODE1: :HELLO MANAGER.SYS :DSLINE NODE2 :REMOTE HELLO MGR.TELESUP The result on NODE1 is: :NSCONTROL STATUS=USERS JOBNUM SESSION ID TYPE SERVICES USER.
Commands NSCONTROL STATUS Example 4 In the following example, the Network Services have not been started (no NSCONTROL START has not been issued). The system response to the NSCONTROL STATUS=USERS,SERVICES command shows that there are no Network Services users and no Network Services currently active. :NSCONTROL STATUS=USERS,SERVICES NO CURRENT NETWORK SERVICE USERS NO NETWORK SERVICES ARE CURRENTLY ACTIVE Example 5 Example 5 shows the brief summary of users, services, and servers information.
Commands NSCONTROL STOP NSCONTROL STOP Terminates Network Services subsystem. Syntax NSCONTROL STOP[=service[,service]…] Parameters STOP=services Terminates the Network Services subsystem. STOP executes a “graceful” shutdown of Network Services. Existing users of the service can continue until they complete their NS activity, but new users are prevented from using the services. The optional service list (services) allows you to select which of the services are disabled for local or remote use.
Commands NSCONTROL STOP VT Prevents remote users from logging onto the local node using the REMOTE HELLO command. VTR Prevents remote users from accessing local terminals using the Reverse VT service. VTA Prevents remote users who are running the Virtual Terminal service over TCP implementations which only support the ARPA standard stream mode flow control mechanisms to log onto the local node.
Commands NSCONTROL STOP Example 1 Example 1 shows NSCONTROL STOP without the service list. All Network Services are stopped. Any active servers are allowed to continue until finished with the current task, at which point they are terminated. No new service requests are accepted. When all the servers and services are stopped, the DSDAD process terminates. In the example, an NSCONTROL ABORT command is issued after the NSCONTROL STOP command to make sure all Network Services activity is stopped.
Commands NSCONTROL VERSION NSCONTROL VERSION Displays the version numbers for the Network Services software modules and the overall subsystem version. Syntax NSCONTROL VERSION[=MOD] Parameters VERSION[=MOD] Displays the overall version of the Network Services. If qualified with the MOD keyword, displays the version of each of the software modules of the Network Services as well as the overall version.
Commands NSCONTROL VERSION Example 2 To see the version numbers of the individual modules, you would specify the command using the MOD keyword.
Commands RESUMENMLOG RESUMENMLOG Resumes logging after a recoverable error. Syntax RESUMENMLOG Use Available In Session? YES In Job? YES In Break? YES Programmatically? YES Breakable? NO Capabilities? NM Discussion RESUMENMLOG causes the resumption of logging to the NM disk log file upon the correction of a recoverable I/O error. For example assume that the system is on line, NM logging is enabled, and a recoverable error occurs on NMLG file number 104.
Commands SHOWNMLOG SHOWNMLOG Displays the number and available space of the log file. Syntax SHOWNMLOG Use Available In Session? YES In Job? YES In Break? YES Programmatically? YES Breakable? NO Capabilities NM Discussion SHOWNMLOG displays the number of the current NMLG file and the percentage of available file space currently used.
Commands SWITCHNMLOG SWITCHNMLOG Closes the current log file and creates and opens a new one. Syntax [UPDATE ] SWITCHNMLOG [filenumber] Use Available In Session? YES In Job? YES In Break? YES Programmatically? YES Breakable? NO Capabilities? NM Parameters UPDATE Allows you to update logging configuration for all subsystems actively logging without stopping transport. To change the logging configuration, use the node management configurator (NMMGR).
Commands SWITCHNMLOG Discussion SWITCHNMLOG closes the current NMLG file and creates and opens a new one. When you enter SWITCHNMLOG, NMS displays the message: NMLG FILE NUMBER nnnn IS mm% FULL NMLG FILE NUMBER pppp ON where nnnn is the previous NMLG FILE number, mm is the percentage of file space used, and pppp is the newly opened file numbered one more than the last file number.
LINKCONTROL Command A LINKCONTROL Command This appendix defines the fields output by the LINKCONTROL STATUS command and its associated parameters. The LINKCONTROL STATUS command enables you to obtain link configuration and statistical data which you can use for monitoring and debugging the link. This command has several parameters, each of which provides different configuration or statistical data.
LINKCONTROL Command NS 3000/iX LAP-B Link Statistics NS 3000/iX LAP-B Link Statistics The following section describes the data that is output when you issue the LINKCONTROL command to obtain statistics relating to NS 3000/iX LAP-B Links.
LINKCONTROL Command NS 3000/iX LAP-B Link Statistics Figure A-2 provides an example of the data that is displayed when you issue the LINKCONTROL linkname;STATUS=CONFIGURATION command: Figure A-2 LAP-B CONFIGURATION Parameter Output Physical Path Phone Number Modulo Count Local Mode LAPB Parm K LAPB Parm T1 LAPB Parm N2 24 9D1D40898765432 8 HP-HP 7 300 hsec 20 Cable Type RS232 Buffer Size 1024 Bytes Connect Timeout 60 sec Local Timeout 900 sec Transmission Speed 64000 bps Phone Number.
LINKCONTROL Command NS 3000/iX LAP-B Link Statistics LAPB Parm K. The LAPB Parm K field displays the configured number of unacknowledged frames that are allowed in the network at any given time. For example, if this value is set to seven (7) for a node, and that node transmits seven (7) packet frames onto the network, it cannot transmit another frame until one or more of the transmitted frames are acknowledged. Connect Timeout.
LINKCONTROL Command NS 3000/iX LAP-B Link Statistics STATISTICS Parameter Fields The STATISTICS parameter for LAP-B links displays many fields in addition to the LINKSTATE parameter fields. The CONFIGURATION parameter fields are not displayed with this parameter.
LINKCONTROL Command NS 3000/iX LAP-B Link Statistics Data Frames Sent. The Data Frames Sent field displays the total number of transmitted data frames. Data Frames Received. The Data Frames Received field displays the total number of received data frames. Aborted Frames Sent. The Aborted Frames Sent field displays the number of frames which were aborted before they were received. Normally, this number should be quite low (below 3% of the total number of frames sent).
LINKCONTROL Command NS 3000/iX LAP-B Link Statistics DCD Carrier Losses. The DCD Carrier Losses field displays the number of times the PSI detected a temporary loss of the Data Carrier Detect (DCD) signal on the cable. On most lines, this will remain at a value of zero, although some modems will periodically drop signals for very short intervals. CRC Errors. The CRC Errors field displays the number of frames that were received with a bad Cyclic Redundancy Check (CRC) checksum.
LINKCONTROL Command NS 3000/iX LAN Link Statistics NS 3000/iX LAN Link Statistics The following section describes the data that is output when you issue the LINKCONTROL command to obtain statistics relating to NS 3000/iX LAN Links. LINKSTATE Parameter Fields Figure A-5 provides an example of the data that is displayed when you issue the LINKCONTROL linkname;STATUS=LINKSTATE command: Figure A-5 LINKSTATE Command for LAN Link Linkname: SYSLINK Linktype: IEEE802.3 Linkstate: CONNECTED Linkname.
LINKCONTROL Command NS 3000/iX LAN Link Statistics Physical Path. The Physical Path field displays the current physical path for the LAN card as specified in the NMMGR configuration file. Inbound Buffer Size. The Inbound Buffer Size field displays the current size of the receive buffer that are configured for this system through NMMGR. This field will not print for NIO cards, since there may be multiple inbound buffer sizes. Inbound Number of Buffers.
LINKCONTROL Command NS 3000/iX LAN Link Statistics Receive Filter k_pckts() (NIO card only). The Receive Filter k_pckts() filed is either enabled (1) or disabled (0). When enabled, the LAN card keeps frames received from the network media, even if no buffers are currently posted to the card. If this option is not enabled, the frames will be dropped. Receive Filter x_pckts() (NIO card only). The Receive Filter x_pckts() field is either enabled (1) or disabled (0).
LINKCONTROL Command NS 3000/iX LAN Link Statistics Transmits no error. The Transmits no error field specifies the number of frames that were successfully transmitted onto the medium. This includes the number of frames that were successfully transmitted on the first attempt, as well as frames that were successfully transmitted after being deferred or that experienced one or more collisions. The maximum value of this 32-bit field is 4294967295. Receives no error.
LINKCONTROL Command NS 3000/iX LAN Link Statistics Carrier losses. The Carrier losses field indicates that the transmitting node turned off the carrier signal on the cable. This occurred for one of the following reasons: • The stub cable is not connected to the frontplane connector. • The AUI (or AUI pigtail for ThinMAU) is not connected to the stub cable. • The MAU is broken.
LINKCONTROL Command NS 3000/iX LAN Link Statistics The reflectometer field, for a thick LAN cable, is calculated in the following manner: The ThickLAN velocity of propagation Where c (the speed of light) The bandwidth of a LAN = = = .77c 3x10 E8 10Mb/sec. Before determining the level of cable fault isolation, you must first determine how many meters of the cable are covered per bit time. You then divide .77c by 10Mb/sec.
LINKCONTROL Command NS 3000/iX LAN Link Statistics Transmits 16 collisions. The Transmits 16 collisions field indicates the number of times a frame or frames were not transmitted because 16 consecutive collisions occurred. This commonly occurs in the protocol during periods of high network utilization. If your node is experiencing continuous retry errors, the problem is most likely that a terminator has been removed from the cable.
LINKCONTROL Command NS 3000/iX LAN Link Statistics • An AUI cable that is shorted and sending an intermittent signal to any of the connectors. • Infinite deferral errors. • “Jabbering” MAU. • Noise from another node. • Bad chips. The value of the 802 chip restarts field provides information about the performance of the LAN card and the status of the LANCE chip status for overflow/underflow errors (this is monitored by firmware). Frame losses.
LINKCONTROL Command NS 3000/iX IEEE 802.5 Link Statistics NS 3000/iX IEEE 802.5 Link Statistics The following section describes the data that is output when you issue the LINKCONTROL command to obtain statistics relating to NS 3000/iX IEEE 802.5 Links. LINKSTATE Parameter Fields Figure A-8 provides an example of the data that is displayed when you issue the LINKCONTROL linkname;STATUS=LINKSTATE command: Figure A-8 LINKSTATE Command for IEEE 802.
LINKCONTROL Command NS 3000/iX IEEE 802.5 Link Statistics Current Station Address. The Current Station Address field is a display of the six (6) byte address to which the node is configured to respond. This address is used whenever frames are sent to the network media. The default station address is used unless it is overridden in the NMMGR link configuration screen. If this field is changed, then the station address of this node is changed.
LINKCONTROL Command NS 3000/iX IEEE 802.5 Link Statistics Receive errors. The Receive errors field specifies the number of transmission errors that were received from the link. The value in this field specifies the number of frames which were received, but were corrupted due to errors on the link. This value includes all frames which were discarded because of the setting of the current receive filter.
LINKCONTROL Command NS 3000/iX FDDI Link Statistics NS 3000/iX FDDI Link Statistics The following section describes the data that is output when you issue the LINKCONTROL command to obtain statistics relating to NS 3000/iX FDDI Links.
LINKCONTROL Command NS 3000/iX FDDI Link Statistics STATISTICS Parameter Fields The STATISTICS parameter for FDDI links displays many fields in addition to the LINKSTATE parameter fields. The CONFIGURATION parameter fields are not displayed when this parameter is used.
LINKCONTROL Command NS 3000/iX FDDI Link Statistics Receive errors. The number of all error frames that were detected by this station and no previous station. Receives lost. The number of frames received that had an error. Receives not copied. The number of frames addressed to this station but not copied into a receive buffer because there was no room for them. Receives discarded. The number of frames received by this station that were discarded due to errors, invalid addresses, or lack of resources.
LINKCONTROL Command NS 3000/iX FDDI Link Statistics Write bytes. The total number of bytes in all packets transmitted by the driver. The maximum value is one quadrillion (10^15). Read bytes. The total number of bytes in all packets received by the driver. The maximum value is one quadrillion (10^15). Unicast writes. The number of unicast packets transmitted by the driver. Unicast reads. The number of unicast packets received by the driver. Multicast writes.
LINKCONTROL Command NS 3000/iX FDDI Link Statistics Ring up time. The number of seconds the FDDI ring has been up since the driver was started. Subtracting this number from the Num of heartbeats value will provide the number of seconds that the ring has been down. Note the ring being down does not by itself indicate a problem with this node. The ring will not be up unless the FDDI concentrator and other nodes are configured and active. Read buffs in pool. The number of buffers in the inbound buffer pool.
LINKCONTROL Command NS 3000/iX FDDI Link Statistics Ring_op. The FDDI card is signaling that the FDDI ring is operational. Ctrl_response_pending. The driver has a control response pending on the card. Free_space_pending. A free space request is pending against the card. Bad_card_on. A problem with the FDDI card has been detected. Do_bind_on. The FDDI driver is being started and initialized. Download_on. The FDDI card firmware is being downloaded to the card. Statistics_on.
Submitting an SR B Submitting an SR For further assistance from HP, document the problem as an SR (service request) and forward it to your HP Service Representative. Include the following information where applicable: • A characterization of the problem. Describe the events leading up to and including the problem. Attempt to describe the source of the problem. Describe the symptoms of the problem and what led up to the problem.
Submitting an SR • Document your interim, or “workaround” solution. The cause of the problem can sometimes be found by comparing the circumstances in which it occurs with the circumstances in which it does not occur. • Create copies of any NS 3000/iX or NetIPC user trace, network transport trace and communication link trace files that were active when the problem occurred for your Hewlett-Packard representative to further analyze. • In the event of a system failure, a full memory dump must be taken.
Glossary A access port A special interface card in the system cabinet through which the system console is connected. address A numerical identifier defined and used by a particular protocol and associated software to distinguish one node from another. address key See X.25 address key. address resolution In NS networks, the mapping of node names to IP addresses and the mapping of IP addresses to subnet addresses.
Glossary backup configuration file A file that contains a copy of the information contained in the configuration file. The backup file, called NMCBACK.group.account by default, is updated each time the configuration file is successfully validated. banner A welcome message displayed on your screen. On the local OpenView workstation a banner appears when a remote connection is established with the OpenView DTC Manager. A banner also can appear when you log on to MPE.
Glossary the sending node. The address of the sending node is the calling address. carrier A continuous wave that is modulated by an information-bearing signal. catenet See internetwork. CCITT Consultative Committee for International Telephony and Telegraphy. An international organization of communication carriers, especially government telephone monopolies, responsible for developing telecommunication standards by making recommendations.
Glossary through use of NMMGR. Access to X.25 is configured in two parts. The X.25 MPE/iX System Access software is configured on the host through use of NMMGR. The DTC/X.25 Network Access software residing on the DTC is configured at the OpenView Windows Workstation through use of the OpenView DTC Manager. configuration file The configuration file contains the information that the network needs in order to operate. This file also contains information necessary for link- level and NetIPC logging.
Glossary therefore allows the choice between local and end-to-end acknowledgment. DCE Data circuit-terminating equipment. The interfacing equipment required in order to interface to data terminal equipment (DTE) and its transmission circuit. Synonyms: data communications equipment, dataset. A modem is an example of a DCE. DDX The national public PSN of Japan.
Glossary Dial ID protocol A proprietary Hewlett- Packard protocol that provides security checking and address exchange for dial links. dial link A connection made through public telephone lines. direct-connect device An asynchronous device that is connected directly to a DTC through an RS-232-C or RS-422 cable, with no intervening communications equipment. Also referred to as a “local connection.” direct connection A leased line, private line, or other non-switched link in a network.
Glossary DTC Manager See OpenView DTC Manager. DTC node name A unique name used to identify a DTC on a LAN. The node name format is nodename.domain.organization, with each of the three parts having up to 16 characters. The name begins with either a letter or a digit. DTC station address (802.3 address) A 12-digit hexadecimal number used to identify the DTC as a node belonging to the network configuration. Also called the LAN address or node address.
Glossary DTS restart The startup of the DTS subsystem using the DTCCNTRL command file after DTS has been shut down. DTS shutdown The shutdown of the DTS subsystem, including the release of all TIO-related resources, using the DTCCNTRL command file. duplex A transmission method that allows two-way communication. If both ends of the transmission link can transmit simultaneously, it is called full duplex. If only one end can transmit at a time, it is half-duplex transmission.
Glossary facility set A facility set defines the various X.25 connection parameters and X.25 facilities that can be negotiated for each virtual circuit on a per-call basis. fast select An optional packet-switching network facility by which user data can be transmitted as part of the control packets that establish and clear a virtual connection. FCS Frame Check Sequence. A sequence of bits generated by X.25 at Level 2 that forms part of the frame and guarantees the integrity of its frame’s contents.
Glossary store and forward to transfer packets between each network that it belongs to. G gateway A node that connects two dissimilar network architectures. A gateway can be either a single node (full gateway) or two gateway halves. gateway half A node that works in conjunction with another node on another network to form an internetwork. The only protocol used by gateway halves is the NS Point-to-Point 3000/iX Link. See also full gateway.
Glossary host computer The primary or controlling computer on a network. The computer on which the network control software resides. For HP purposes, it can also be used to distinguish the HP 3000 Series 900 system (host) from the DTC. IEEE 802.3 A standard for a broadcast local area network published by the Institute for Electrical and Electronics Engineers (IEEE). This standard is used for both the ThinLAN and ThickLAN implementations of the LAN.
Glossary internet communication Communication that occurs between networks. internet hop count The number of full gateways plus the number of gateway-half links that a packet must pass through in moving from source node to destination. internet protocol A protocol used to provide routing between different local networks in an internetwork, as well as among nodes in the same local network. The Internet Protocol corresponds to Layer 3, the Network Layer, of the OSI model. See also IP address.
Glossary developing international standards, including communication standards. LAP-B must also be used over direct-connect NS Point-to-Point 3000/iX Links. L LCI Logical Channel Identifier. Local value on a network node which identifies the channel used to establish a virtual circuit (SVC or PVC) through an X.25 network. LAN Local Area Network. A collection of data communication systems sharing a common cable whereby each system can communicate directly with another LAN address See station address.
Glossary local node The computer that you are configuring or that you are logged on to. local switching A feature of the DTC which permits back-to-back configuration (for connections to an HP 3000 MPE/V host), using two ports of the same DTC. See also closed user group. local user group A list defined for a particular DTC and card that specifies which remote nodes this DTC can send data to and also which remote nodes this DTC can receive data from.
Glossary capability provided with the management software. A network map is also a hardcopy drawing used when planning a network. It shows network topology, node and network names, addresses, network boundaries (for an internetwork map), and link types. mapping A set of characteristics that describe a route taken by messages to reach a destination node. This set of characteristics is configured with NMMGR at every node on a point-to-point network.
Glossary N nailed device A device with a permanently assigned ldev. The assignment is established through the system configuration of the MPE/iX host system. Nailed devices can be accessed programmatically through their ldev number. Nailed devices can also be assigned to more than one host. native mode The run-time environment of MPE/iX. In Native Mode, source code has been compiled into the native instruction set of the HP 3000 Series 900 computer.
Glossary network boundaries (for an internetwork map), and link types. backup file is updated each time the configuration file is successfully validated. Network Services NS. Software application products that can be used to access data, initiate processes, and exchange information among nodes in the network. The HP 3000/iX Network Services include RPM, VT, RFA, RDBA, and NFT. NMCONFIG.PUB.
Glossary NMSAMP1.PUB.SYS A sample configuration file supplied with FOS that can be used as a template for DTS configuration. NMSTART.PUB.SYS The file which contains maintenance mode commands executed during NMMGR startup. node A computer that is part of a network. The DTC is also considered to be a node and has its own address. node address The node portion of an IP address. The IP address consists of a node portion and a network portion. node management services configuration manager See NMMGR.
Glossary Point-to-Point 3000/ iX Link, and the Token Ring 3000/iX network link. Manager, and other applications, such as Switch/PAD Manager, Hub Manager, etc. NS 3000/iX Network Services OpenView Admin An OpenView Windows program that enables you to configure how your OpenView Windows applications will function. For example, it enables you to set a default map for the OpenView DTC Manager.
Glossary the Datacommunications and Terminal Controller (DTC). The configuration software that runs on this workstation is called the OpenView DTC Manager software. OSI model Open Systems Interconnection model. A model of network architecture devised by the International Standards Organization (ISO). The OSI model defines seven layers of a network architecture with each layer performing specified functions. P packet A block of data whose maximum length is fixed. The unit of information exchanged by X.
Glossary point-to-point A link that connects either two nodes in a NS Point-to-Point 3000/iX network or two gateway halves. port An outlet through which a device can be connected to a computer, consisting of a physical connection point and controlling hardware, controlling software, and configurable port characteristics. Ports can be thought of as data paths through which a device communicates with the computer.
Glossary programmatic device A device operating under control of a program running on a computer. Programmatic devices can be used for input, output, or both, depending on the device and how it is opened by the controlling program. protocol A set of rules that enables two or more data processing entities to exchange information. In networks, protocols are the rules that govern each layer of network architecture. They define which functions are to be performed and how messages are to be exchanged.
Glossary from a destination address before attempting to retransmit a frame. When choosing this value, factors like the line speed and maximum frame size should be taken into account. RFA Remote file access. A network service that allows users to access file and devices on remote nodes. router network See point-to-point. routing The path that packets or fragments of a message take through a network to reach a destination node. RMP Remote Maintenance Protocol. HP proprietary protocol used in DTC management.
Glossary shared dial A dial link that provides connection to more than one remote system, although to only one at a time. shared-line access The feature that allows two or more HP 3000 Series 900 hosts to use the same DTC/X.25 Network Access card on a DTC to access an X.25 network. SIC Serial Interface Card. A card installed in the front of the DTC that acts as an interface between a corresponding Connector Card (CC) and the DTC’s processor.
Glossary configured using the NMMGR utility and specified in the same format as an IP address. SVC Switched Virtual Circuit. The path through an X.25 network that is established at call set-up time. switching See DTC switching. Switching user interface The user interface available when DTC switching is enabled that allows terminal users to choose the HP 3000 Series 900 computer with which they want to establish a communication link.
Glossary the system-supplied terminal types, or you can create custom terminal types using the workstation configurator. ThinLAN A LAN that conforms to the IEEE 802.3 Type 10 BASE 2 standard LAN. ThinLAN 3000/iX Link Hardware and software necessary to create a broadcast network, which uses the IEEE 802.3 LAN cable to transmit messages to all the nodes on the network. The messages are then accepted only by the node or nodes to which they are addressed. Also includes the ThickLAN and StarLAN 10 options.
Glossary transparent mode A data transfer scheme in which only a limited number of special characters retain their meaning and are acted on by the system. All other characters are considered to be data and are passed through with no control actions being taken. transport, network Software that corresponds to layers 4 and 3 of the OSI network architecture model. It sends data out over the communications link, receives incoming data, and routes incoming or outgoing data to the appropriate destination node.
Glossary VPLUS Software used to generate screens such as those displayed by NMMGR. V-Series (V.##) CCITT A set of CCITT recommendations related to data communication over a voice-grade telephone network. VT See virtual terminal. W WAN Wide Area Network. A data communications network of unlimited size, used for connecting localities, cities, and countries.
Glossary X.29 Defines the interface for data exchange between a packet-mode DTE and a remote packet assembly/disassembly (PAD) facility over a packet-switching network. XON/XOFF protocol The flow control used by MPE/iX systems to protect against data overruns. XON/XOFF protocol is controlled by the data recipient who sends an XOFF character (ASCII DC3) to the sender if it is unable to continue to receive data. The sender suspends transmission until it receives an XON character (ASCII DC1). X.Series (X.
Glossary 228 Glossary
Index Numerics 802 chip restarts, 186 A aborted frames received, 178 aborted frames sent, 178 B Bad_card_on, 196 Bmgr_queued_aloc_on, 195 broadcast reads, 194 broadcast writes, 194 buffer size, 175 C cable type, 175 card, 68 carrier losses, 184 commands COMPARE, 86 DATA, 82 DEBUG, 82 DO, 83 EXIT, 83 HELP, 83 HELP ALL, 83 HELP BROWSE, 83 HELP command, 83 HELP COMMANDS, 83 INFILE, 83 LINKCONTROL, 107 LINKCONTROL STATUS, 107 LINKCONTROL TRACE, 107 LISTREDO, 83 MAIN, 83 MANUAL, 83 MENUS, 83 MESSAGES, 83 NETCON
Index NSLOGON, 30 NSTEST, 30 num of heartbeats, 194 num of power fails, 194 num of subset bufs, 194 number of users, 194 O online diagnostic, 68 Out of Rx bufs, 183 Out of Tx bufs, 183 outbound high water, 194 OUTFILE command, 83 overhead bytes received, 177 overhead bytes sent, 177 oversized frames received, 178 P Pfail_on, 195 phone number, 175 physical path, 181, 188, 191 Post_read_pending, 195 Q queued buffer reqs, 194 QUIT command, 83 QVALNS, 30 R read buffer size, 195 read buffs avail, 195 read buffs
