NS 3000/iX Operations and Maintenance Reference Manual HP e3000 MPE/iX Computer Systems Edition 8 Manufacturing Part Number: 36922-90042 E0801 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Verify Version of Data Communications Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 Verify Version of Network Transport Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 Verify Version of Network Services Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 Displaying Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Format Log and Trace Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Format X.25 Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 4. Troubleshooting Process Identifying Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Characterize the Problem . . . . . . . . . . . . . . . . . . . . . . . .
Contents Available Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82 Using NETTOOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 Running NETTOOL Interactively. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NETCONTROL ADDLINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139 NETCONTROL UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140 Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NSCONTROL START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175 A. LINKCONTROL Command NS 3000/iX LAP-B Link Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178 LINKSTATE Parameter Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178 CONFIGURATION Parameter Fields . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures Figure 4-1. Characterizing the Problem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Figure 7-1. The NETCONTROL Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 12
Tables Table 1-1. Tools for Obtaining Network Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Table 5-1. Nodal Troubleshooting Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Table 6-1. Differences in Tool Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Table 6-2. The NETTOOL Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Table 7-1.
Tables 14
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 e3000 to communicate with other HP computer systems as part of a distributed network. These systems can be other HP e3000s, HP 9000s, HP 1000s, and PCs.
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. • Chapter 2 , “Operating Your Network,” provides step-by-step instructions for starting and stopping network links and services and for verifying network connections and services.
• 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 Devices • Using the OpenView DTC Manager 17
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 e3000/iX Network Planning and Configuration Guide.
Overview of NS 3000/iX Operations Creating Your Network The NS 3000/iX Products An NS 3000/iX network consists of one or more of the available NS 3000/iX link products configured to allow communications between systems (nodes) on the network. The Network Services are available to allow users to perform applications across the network. Your network will include one or more of the following link products: • ThinLAN 3000/iX Link. Supports IEEE802.3/Ethernet LAN connections. • Token Ring/iX. Supports IEEE802.
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 Network Obtaining Information About 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 Network Table 1-1 Tools for Obtaining Network Information To Get Information About... Use... Refer to...
Overview of NS 3000/iX Operations Obtaining Information About Network Table 1-1 Tools for Obtaining Network Information To Get Information About... Use... Refer to... Transmission errors LINKCONTROL STATUS NETTOOL Chapter 3, 7 Chapter 6 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 Network Troubleshooting 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.
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 Receive failures” listed above, then your system may have hardware link problems; see “Investigating the Link” in the NS 3000/iX Error Messages Reference Manual. 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. SOCKERR # MESSAGE: PCERRMSG FAILED (SOCKERR #) CAUSE: Error message could not be acquired from the message catalogue SOCKCAT.NET.
Operating Your Network Verifying Network Connections and Services Validate Network Services in Batch Mode Perform the following steps to use QVALNS to check the Network Services. The services tested are VT, RFA, NFT, RPM, and RDBA. (Note that it is not possible to use passwords with QVALNS. If passwords are required, run NSTEST instead.) 1. Make sure the network transport and Network Services are running on all nodes that are to be a part of this test. 2.
Operating Your Network Verifying Network Connections and Services Test RDBA Using NSTEST To test RDBA, the data base RDBAT must reside in the home group of the remote system. This is not a problem when you run QVALNS, because that program creates the database and then purges it when it finishes. If you want to test RDBA using NSTEST, perform the following steps. 1. Obtain a temporary copy of the job JQVALNS.NET.SYS. If this file is not available, run QVALNS to create it. 2.
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. 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 Stop Network Interfaces Stop a Single Network Interface Issue the following command to stop a single network interface: NETCONTROL STOP;NET=NIname 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. Stop All Network Interfaces When you enter the STOP command with no keywords, all entities of the network transport are terminated.
Operating Your Network Stopping Links and Services 38 Chapter 2
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 Verify Version of Data Communications Software Use the NMMAINT utility to display the individual and overall version numbers for all software modules of NS 3000/iX, SNA IMF, and SNA NRJE Network Services, as well as the SNA and NS 3000/iX network link products. 1. Enter the command: RUN NMMAINT.PUB.SYS 2. If the version, update, and fix levels of these modules do not match, the subsystem will not work correctly.
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 Display Network Directory Configuration Perform the following steps to display a summary of the local system’s network directory configuration: 1. Run the NETTOOL utility by entering the program name: NETTOOL.NET.SYS 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 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 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 Display Protocol Status You can display the status of a general protocol (TCP or PXP), or of a network interface protocol (PROBE, ARP, IP, DIAL or
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 3. Enter DISPLAY to display resource usage.
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 Example 1 This example shows using an INFO string containing all three parameters. :RUN PING.NET.SYS;INFO="15.13.131.
Getting Information About the Network Displaying Connection Information Example 2 This example shows an INFO string containing the IP address, and five packets. Note that the number of bytes has been defaulted by omitting it in the info string. :RUN PING.NET.SYS;INFO="15.13.131.
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 Tracing Facility Tracing is provided for the Network Services subsystem, Network Interprocess Communication (NetIPC), the network transport subsystem, and the link subsystems. You enable tracing for the Network Services by the DSLINE command for each user’s services. Network Service tracing is used to trace messages generated by your applications. For more information, see Using NS 3000/iX Network Services.
Getting Information About the Network Logging and Tracing Format X.25 Log Files Messages for X.25 links are not recorded to the same logging file as messages for other links. If you need to format log messages for a host-based X.25 link, you should see Configuring and Managing 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.
Getting Information About the Network Logging and Tracing 58 Chapter 3
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 Identifying Problems Identifying 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 Identifying 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 Identifying Problems Figure 4-1 Characterizing the Problem 62 Chapter 4
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. This chapter provides strategies for dealing with the following types of network problems: • Interactive or programmatic problems.
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 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. This would cause a failure in a REMOTE HELLO or a DSCOPY or RPMCREATE that tried to automatically log on to a session. • Someone has exclusive access to the specified line or the user requested exclusive access to a line that is already in use.
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 Symptom Possible Causes New installation 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 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 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. Insufficient Configuration File Values Only change the configured values in the configuration file for a persistent or widespread problem. The configured values apply to communication over all the connections and with all the remote nodes in the internet.
Common Network Problems Common Problems and Actions the error. If the problem is ongoing, then take the appropriate action: • If the log messages show initial TCP connection failures due to a heavily loaded remote node, configure a longer Initial Retransmission Interval for the Transmission Control Protocol (TCP) Configuration Screen. This is in the NETXPORT branch of the NMMGR network configuration.
Common Network Problems Common Problems and Actions Indication of a faulty shutdown procedure on a nodal level is an incomplete shutdown of the network transport. Network Transport Shutdown Shutting down the network transport via the NETCONTROL STOP command requires that all NetIPC call sockets, all TCP connections, and all PXP sockets are closed. An error (Transport Shutting) is returned to all open sockets.
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 NETTOOL Tools 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 NETTOOL Tools Differences Table 6-1 summarizes the differences between core tools, associated tools, and user tools.
Using NETTOOL NETTOOL Tools Available Tools Table 6-2 summarizes the tools available in NETTOOL, the type of each tool, and the function of each tool. Table 6-2 The NETTOOL Tools Tool Type Function CONFIGURATION SUMMARY Core Displays a summary of the information in the configuration or directory file. filters Core Displays global filter setup. IPCINT Associated Provides a command interface to IPC. LOOPINIT Associated Monitors round-trip response time between nodes.
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 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 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. HELP COMMANDS See a list of commands with one line descriptions.
Using NETTOOL Using NETTOOL 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. : Interactively execute MPE commands. :MPEcommand Execute one or more MPE commands then return to NETTOOL. # Designates a comment. Comments may be inserted in a command string or in an INFILE record.
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 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. IPCINT creates a log file, IPCLOG, to track its actions.
Using NETTOOL Using the NETTOOL Tools 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 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 GATE UP A specific gateway (Active). GATE DOWN A specific gateway (Not Active). STATISTICS Display the statistics; IP Route statistics, IP update routing table etc. 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 NMDUMP NMDUMP is one of the node management services (NMS) utilities. You use this tool to decode and format log records or trace messages so that they can be more easily read and analyzed. 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.
Using NETTOOL Using the NETTOOL Tools The root menu will appear. 2. Select the NSTEST tool from the main menu. 3. When prompted, enter the name of the service you want to test. You should always test VT first so that NSTEST can set up a remote session. 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.
Using NETTOOL Using the NETTOOL Tools 2. Select the PING tool from the main menu by entering the PING command. A new menu will appear. 3. Select the menu item or items needed to perform the PING requests you want to perform. The available choices are described here. 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.
Using NETTOOL Using the NETTOOL Tools QVALNS The QVALNS tool allows you to test the Network Services in program mode. To use this tool, perform the following steps. 1. Make sure the network transport and Network Services are running on all nodes that are to be a part of this test. 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.
Using NETTOOL Using the NETTOOL Tools interpretation of resource usage and pointing to possible relationships with configurable parameters. Non-verbose mode displays current, maximum experienced (high-water mark), and maximum allowable usage for the resources specified. Default is non-verbose. item Use to select a particular item from the one-line display so that you can obtain detailed information on that item.
Using NETTOOL Using the NETTOOL Tools 3. If filters are not used, SOCKINFO will print a Global Display like the following: GLOBAL DISPLAY Host=sampsys Gsxds=$a.d5690000 10:30 am ------------------------------------------------------------------------Pin User Program Job Pri Skts 59 (system process) snmp.net.sys cq152 2 61 (system process) sockreg.net.sys lq149 1 63 (system process) dsdad.net.sys lq149 14 69 joe.mpe vtserver.net.sys s538 lq100 1 70 bob.mpeix vtserver.net.sys s546 lq100 1 79 spool,unispool.
Using NETTOOL Using the NETTOOL Tools not queue) R Enter Destination Display mode. (Must be in Process mode) S For an interpreted dump of a socket data structure. (Must be in Process Display mode) T Enable/disable tracing. V Print the SOCKINFO version number. Y Define new timeout value, in seconds. (Default is 0 : disabled) 5. To return to NETTOOL, type E. STATUS The STATUS tool provides options that let you display the status of the network interfaces and their associated links.
Using NETTOOL Using the NETTOOL Tools IPSTAT Use to display IP statistics for the network specified by niname. If you have not set niname, you will see statistics for all NIs. LKSTAT Use to display statistics for the link whose name has been set by lkname. If you have not set lkname you will see statistics for all links. (The statistics shown will be the same as those displayed by the LINKCONTROL command.
Using NETTOOL Using the NETTOOL Tools measurements will occur at one second intervals. You should view this parameter as a means of causing successive measurements to be space by at least the delay time. recent Use this filter to select whether the displayed statistics will be adjusted to show only the data which occurred recently. If the flag is not set (the default), the program will display all statistics totals. X25CHECK The X25CHECK tool creates connections to remote X.
Using NETTOOL Using the NETTOOL Tools display only the started X.25 NI.) 4. The program will display the contents of the internal X.25 tables. The information prints only once. To get new, updated information, you will need to run X25STAT again. 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.
Using NETTOOL Using the NETTOOL Tools XPVAL The XPVAL tool provides a quick validation of the transport by setting up a connection between two nodes. You must run XPVAL on both the local system and a remote system for the test to work, with the program on the local system started first. To use this tool, perform the following steps. 1. Run NETTOOL on the local system by entering the program name at the MPE prompt: NETTOOL.NET.SYS The root menu will appear. 2. Select the XPVAL tool from the main menu. 3.
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. 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 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 106 Chapter 6
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 Table 7-1 NS 3000/iX Network Commands Command Description 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 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 interface. Not all functions may be applied as a group; see the individual command functions for details. 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.
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 Discussion This command adds an already configured link to an active network interface without having to first bring down and then restart the network interface or the entire transport. This can be a link for a newly-configured node mapping, a link being shared with another subsystem such as RJE/iX or SNA/iX, or a link being restarted after an earlier failure due to link errors. Note that some link errors are so serious that an ADDLINK cannot restore use of the link.
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 Discussion This command deletes a previously configured and started link from an active network interface without having to bring down the entire network interface or transport. This command is particularly useful when making cabling or modem changes, to make a device unusable for security reasons, or when sharing a device with other subsystems such as RJE/iX or SNA/iX. Certain types of errors can also sometimes be cleared by a DELLINK followed by an ADDLINK.
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 2 Example 2 shows the events associated with the START function at initiation. As indicated in the status report, the general transport is not active. Therefore, the first events of initiation are to initialize the control process (CP) and the general protocols. Compare the displayed events to the defined entities of Figure 7-1. The events displayed in this example show creation of the general protocols.
Commands NETCONTROL START Example 4 In Example 4, the LAN NI, configured as LAN1, is started on the first NETCONTROL START command. Notice that the initiation events to initialize the general protocols are immediately followed by the start of the LAN NI with its associated protocols: IP, probe, and ARP. Compare the displayed events to the defined entities of Figure 7-1. The events displayed show creation of the control process, the general protocols, and the LAN NI entities.
Commands NETCONTROL START Example 6 Starting the LAN NI, configured as LAN1, when the general protocols are already active, gives you the following: :NETCONTROL START;NET=LAN1 ** NETXPORT Map Tbl; Mapping Table Created - Loc: 1; Class: 4; Parm= $D5C80250; Pin: 0 ** NETXPORT LAN NI; Network interface start - Loc: 28; Class: 4; Parm= $96430000; PortID: $FFFFFE81 ** NETXPORT IP; Protocol start - Loc: 102; Class: 4; Parm= $D5CD0000; PortID: $FFFFFE88 ** NETXPORT Probe; Protocol start - Loc: 35; Class: 4; Parm=
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 PROT=gProt PROT=niProt Specifies that a protocol is the pertinent entity for each specified function to act on. Enter the name of the protocol, as follows: Chapter 7 gprot Specifies the name of one transport general protocol to display the status of. Valid inputs are TCP, UDP, PXP, or IPU. If the specified protocol did not start or is not one of these inputs, an “ENTITY NOT ACTIVE” error will occur.
Commands NETCONTROL STATUS Discussion This command displays status and configuration data for the active transport, using several different output formats depending on the keywords specified. Some of the formats are specific to the control process, a network interface, or a specific protocol. Any entities which are not active cannot have their status displayed. This command differs from other NETCONTROL commands in that it produces warnings, not errors, if transport is not active.
Commands NETCONTROL STATUS :NETCONTROL STATUS;NI=LAN1 NETWORK INTERFACE REPORT NETWORK INTERFACE STARTED FLAGS NIB - PCB LINK INFO NIB - NIB LINK INFO NI PROTOCOLS MAPPING TABLE SIZE MAPPING TABLE ID OUTBOUND BUFFERS NETWORK INTERFACE TYPE PORT ID WRITE BUFFER INFO STORE/FORWARD BUFFER INFO TRACE ID'S NAME NETWORK IP ADDRESS NETWORK SUBNET MASK TRACE MASK : : : : : : : : : : : : : : : : : : DEVICE INFORMATION : DEVICE DEVICE TYPE LINK BUFFER SIZE PROTOCOLS CONNECTED PHONE NUMBER INDEX TRAN PORT INFO :
Commands NETCONTROL STATUS Example 4 Example 4 is a sample of the output that is displayed when the NETCONTROL STATUS command is used specifying the LAN1 network interface via the NET= parameter.
Commands NETCONTROL STATUS To report the status of the control process, enter :NETCONTROL STATUS GENERAL TRANSPORT STATUS : WED, JAN 26, 1994, 9:12 AM TRANSPORT STARTED : WED, JAN 26, 1994, 3:57 AM FLAGS MAX NETWORK INTERFACES MAX NODE NAMES LOG ID TRACE ID CONTROL PROCESS PORT ID : : : : : : $000014C0 32 360 $00000003 $00010081 $FFFFFC8E HOME NETWORK CONFIGURATION FILE TRACE MASK NODE NAME : : : : LAN1 NMCONFIG.PUB.SYS $00000040 NODE.DOMAIN.
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 Discussion If STOP is issued without the NET or GATE keyword, all entities of the network transport are terminated. If STOP is combined with the keyword NET, only the specified non-gatehalf network interface is terminated. If STOP is combined with the keyword GATE, only the specified gateway half is terminated. 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.
Commands NETCONTROL STOP - Loc: 2; Class: 4; Parm= $D5208250; PortID: $D5208250 ** NETXPORT IP Update; General protocol stop - Loc: 19; Class: 4; Parm= $00000000; PortID: $FFFFFE88 ** NETXPORT UDP; General protocol stop - Loc: 25; Class: 4; Parm= $00000000; PortID: $FFFFDFF3 ** NETXPORT Net Timers; Stopping - Loc: 4040; Class: 4; Parm= $96430000; PortID: $FFFFFE81 ** NETXPORT Control Process; Transport stop - Loc: 51; Class: 4; Parm= $00000000; PortID: $FFFFDFF0 Example 3 Example 3 shows what happens if th
Commands NETCONTROL TRACEON and TRACEOFF NETCONTROL TRACEON and TRACEOFF Enables or disables message tracing for the specified transport entity.
Commands NETCONTROL TRACEON and TRACEOFF filename parameter. DISC is the default and the only valid input. 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.
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 } Specifies which configuration areas will be dynamically UPDATE = {NETDIR } updated. The areas possible depends on the network type.
Commands NETCONTROL UPDATE X25 Adds all currently configured Network Directory (NSDIR.NET.SYS) entries having X.25 or IP address types and matching entries in the NMMGR X.25 SVC 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.
Commands NETCONTROL UPDATE Table 7-2 NOTE NETCONTROL Update NI Type 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 Example 2 To look at the version numbers of the individual modules, you specify the MOD keyword. You will see a display like the one shown in example 2. Note that the version numbers shown here are only examples, and should not be used to check any actual installation.
Commands NETCONTROL VERSION NL SL NL SL SL SL SL SL NL NM NM NL procedure: procedure: procedure: procedure: procedure: procedure: procedure: procedure: procedure: program file: program file: procedure: RLM_LOAD_TABLE_VERS RLM_FMT_VERS NET_FC_VERS SOCKIOVERS SOCKACCESSVERS SOCKMISC1VERS SUBSYS3FMTVERS SUBSYS5FMTVERS LEVEL2_RESOLVE_VERS ICMPSERV.NET.SYS NETTOOL.NET.
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 Discussion NS 3000/iX Network Services are composed of user services, each of which performs a specific task. These services are VT, Reverse VT, NFT, RPM, RFA, RDBA, LOOPBACK and NSSTAT. Refer to Using NS 3000/iX Network Services for details on Network Services. To function, Network Services require Network Interprocess Communication (NetIPC), the user interface included with NS 3000/iX links.
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 Discussion NSCONTROL AUTOLOGON allows the user the ability to disable and re-enable autologon for the NS 3000/iX services supporting this feature. Autologon is enabled at NS 3000/iX startup. NSCONTROL AUTOLOGON must be executed after the NSCONTROL START command. When the NS 3000/iX services are stopped, the autologon option resets to the default. Disabling autologon may be important on those systems that use a logon UDC to help enforce system security.
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 change 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 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 change request is received. Once the change request is completed, the server is returned to reserve status.
Commands NSCONTROL SERVER There is no simple formula for determining how many precreated servers to specify. Since each precreated server consumes one set of process resources, including process related system table entries and virtual memory for stack space, the number chosen must be a tradeoff between using system resources and allowing fast service response. The node manager needs to estimate, on the average, the number of concurrent users of each type of server.
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 change 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 51 49 41 58 57 NFT DSSERVER 0 0 300 300 0 0 0 0 RESERVED RESERVED RESERVED RESERVED RESERVED TOTAL NUMBER OF ACTIVE SERVERS: TOTAL NUMBER OF RESERVED SERVERS: TOTAL NUMBER OF SERVERS: 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 service. 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 Discussion NSCONTROL STOP is the normal way to shut down the Network Services. It allows existing users to continue using the services until they finish their tasks, but prevents any new users from using the services. The ABORT function, on the other hand, immediately terminates all the services and all the server processes. Anyone using a service will find their task (DSCOPY, for example) immediately terminated. See the discussion of NSCONTROL ABORT.
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.
Commands SWITCHNMLOG 176 Chapter 7
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 The following is an example of the data that is displayed when you issue the LINKCONTROL linkname;STATUS=CONFIGURATION command: Physical Path Phone Number Modullo 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 Connect Timeout Local Timeout Transmission Speed 1024 Bytes 60 sec 900 sec 64000 bps Phone Number — The Phone Number field displays the current automatic dial phone n
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.
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 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). A large number could point to a noisy line or a weak or bad clock signal sent by a modem.
LINKCONTROL Command NS 3000/iX LAP-B Link Statistics CRC Errors — The CRC Errors field displays the number of frames that were received with a bad Cyclic Redundancy Check (CRC) checksum. A large number (greater than 1% of the total number of packets) indicates that a problem may exist in the connection between the PSI and the modem, or between the two modems.
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 The following is an example of the data that is displayed when you issue the LINKCONTROL linkname;STATUS=LINKSTATE command: Linkname: SYSLINK Linktype: IEEE802.3 Linkstate: CONNECTED Linkname — The Linkname field specifies the name of the link.
LINKCONTROL Command NS 3000/iX LAN Link Statistics through NMMGR. This field will not print for NIO cards, since there may be multiple inbound buffer sizes. Inbound Number of Buffers — The Inbound Number of Buffers field displays the number of receive buffers that are configured for this system through NMMGR. This field will not print for NIO cards. Inbound Buffers Available — The Inbound Buffers Available field displays the number of unused or unassigned Inbound Buffers that are available to this system.
LINKCONTROL Command NS 3000/iX LAN Link Statistics Receive Filter x_pckts() (NIO card only) — The Receive Filter x_pckts() field is either enabled (1) or disabled (0). When enabled, any XID or TEST commands sent to DSAP 0 will be responded to by the driver, and not the card. Current Multicast Addresses — The Current Multicast Addresses field contains a list of all multicast addresses to which the LAN card responds. The default multicast address list contains no addresses.
LINKCONTROL Command NS 3000/iX LAN Link Statistics transmitted after being deferred or that experienced one or more collisions. The maximum value of this 32-bit field is 4294967295. Receives no error — This field specifies the number of frames that were successfully received over the medium. This includes the number of frames that were successfully received on the first attempt, as well as frames that were successfully received after being deferred or that experienced one or more collisions.
LINKCONTROL Command NS 3000/iX LAN Link Statistics • 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. • If using thick LAN cable, there may be a short close to the MAU (ThinLAN cable shorts show up as a retry error as described in the Transmits 16 collision field description). If the LAN continuously loses carrier, the problem is probably caused by a disconnected AUI or stub cable.
LINKCONTROL Command NS 3000/iX LAN Link Statistics 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. This translates into: 7x10E-2) x (3x10E8) __________________ 10E6 b/sec) = 231 meters Therefore, in order to pinpoint a fault in a thick LAN cable by the value of this field, multiply the field value by 231 meters.
LINKCONTROL Command NS 3000/iX LAN Link Statistics has been removed from the cable. Other possible causes include the following: • There is an opening in the cable. • If ThinLAN cable is used, the AUI may be disconnected. • The LAN cable may shorted. Whole byte errors — The Whole byte errors field is the number of frames received that were not an integer multiple number of bytes long. This occurs when an entire byte is not transmitted. This usually also causes the CRC error to be set.
LINKCONTROL Command NS 3000/iX LAN Link Statistics • 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 — The frame losses field indicates the number of times that the LAN controller chip indicated that it has lost a frame.
LINKCONTROL Command NS 3000/iX IEEE 802.5/Token Ring Link Statistics NS 3000/iX IEEE 802.5/Token Ring 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.
LINKCONTROL Command NS 3000/iX IEEE 802.5/Token Ring Link Statistics station address of this node is changed. Make sure that you note this new address in the system manager log. Default Station Address — The Default Station Address field is the default value for the Current Station Address described above. The default station address is determined by the specific Token Ring card. Functional Address Mask — Bits set in this 4 octet field indicate functional addresses to which the Token Ring card may respond.
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 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 Reads completed — The number of packets received from the FDDI card by the driver. The maximum value is two billion (2^31). 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.
LINKCONTROL Command NS 3000/iX FDDI Link Statistics Queued buffer reqs — The number of times the driver has made a queued buffer manager request. 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.
LINKCONTROL Command NS 3000/iX FDDI Link Statistics Post_read_pending — The driver is temporarily out of inbound buffers to post to the card. 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.
LINKCONTROL Command NS 3000/iX 100VG-AnyLAN Link Statistics NS 3000/iX 100VG-AnyLAN 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 100VG-AnyLAN Links.
LINKCONTROL Command NS 3000/iX 100VG-AnyLAN Link Statistics default station address is determined by the specific adapter card. It is also printed on a small label attached to a circuit board on the adapter card. If the adapter card is changed for any reason, the Default Station Address of this node will change. Current Multicast Address List — The Current Multicast Addresses field contains a list of all multicast addresses to which the adapter card responds.
LINKCONTROL Command NS 3000/iX 100VG-AnyLAN Link Statistics values in these fields reach their maximum possible value. When this occurs, these fields can only be reset manually. Transmit bytes norm — Total number of bytes successfully transmitted onto the medium at normal priority. This includes unicast, broadcast, and multicast frames. It also includes frames for which normal priority was requested, but which were later automatically boosted to demand priority by the 100VG-AnyLAN network.
LINKCONTROL Command NS 3000/iX 100VG-AnyLAN Link Statistics Transmits dropped — Total number of frames the link driver discarded because the transmit queue was full, or because the data to be sent was fragmented beyond recognition. The maximum value of this 32-bit field is 2147483647. It would be unusual for this statistic to contain a nonzero value.
LINKCONTROL Command NS 3000/iX 100VG-AnyLAN Link Statistics alignment errors occur frequently, one of the following may be the cause: • A 100VG-AnyLAN adapter card is not operating to within 802.12 specifications. • A 100VG-AnyLAN hub is performing poorly. • The 100VG-AnyLAN cable is not CAT-3 or CAT-5 grade. • A section of 100VG-AnyLAN cable contains wire pairs which are not properly twisted, paired, or of equal length.
LINKCONTROL Command NS 3000/iX 100VG-AnyLAN Link Statistics normal priority was originally requested by the sender, but which were later automatically priority-boosted by the 100VG-AnyLAN network. It does not include frames received by the adapter card but dropped because no upper layer protocol had requested those frames, or because the link was disconnected. The maximum printable value of this 64-bit field is 17 digits, or about 99 million Gbytes.
LINKCONTROL Command NS 3000/iX 100VG-AnyLAN Link Statistics PROBE. This does not include multicast frames received but dropped for any reason. Upper layer protocols register desired multicast addresses with the link driver during initialization. The maximum printable value of this 64-bit field is 17 digits, or about 99 million billion frames. In the previous example, 1.30 million multicast frames were received at normal priority and forwarded to upper layers.
LINKCONTROL Command NS 3000/iX 100VG-AnyLAN Link Statistics Recv dropped: buffer — Total number of frames received from the adapter card, but dropped because no data buffers were available from the upper layer protocol requesting to receive these frames. This is a relatively common occurrence, amounting to flow control for all protocols sharing those buffers. Many protocols include built-in mechanisms for detecting lost frames and requesting their retransmission from the remote side.
LINKCONTROL Command NS 3000/iX 100Base-T Link Statistics NS 3000/iX 100Base-T 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 100Base-T Links.
LINKCONTROL Command NS 3000/iX 100Base-T Link Statistics 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. Make sure that you note this new address in the system manager log. Default Station Address — The Default Station Address field is the default value for the Current Station Address described above. The default station address is determined by the specific adapter card.
LINKCONTROL Command NS 3000/iX 100Base-T Link Statistics Carrier losses Link disconnects Link speed Link duplex Link mode 0 0 10 Half 100Base-TX Recv Recv Recv Link Secs dropped: other deferred overruns auto sensed since clear 19 0 0 No 2602760 The following example of the LINKCONTROL output for a PCI 100Base-T link (some of the statistics differ for PCI).
LINKCONTROL Command NS 3000/iX 100Base-T Link Statistics frames. The maximum printable value of this 64-bit field is 17 digits, or about 99 million billion frames. In the previous example, 127700 frames were transmitted at normal priority. Transmits no error — Total number of frames the adapter card reports it successfully transmitted onto the medium. These adapter card statistics are periodically read, and are accumulated by the link driver.
LINKCONTROL Command NS 3000/iX 100Base-T Link Statistics previous example, 179 frames were transmitted after experiencing between 2 and 15 collisions. This statistic is not logged when the adapter card is operating in full duplex mode, and would print as 0. Trans 16 collisions — This field indicates the number of times a frame was not transmitted, because 16 consecutive collisions occurred. This can occur during periods of high network utilization.
LINKCONTROL Command NS 3000/iX 100Base-T Link Statistics Carrier losses — This field indicates that the transmitting node turned off the carrier signal on the cable. A carrier loss occurs when a receive carrier was not detected after a slottime from the start of transmission. The carrier must be present continuously from the start until the end of transmission to prevent an error.
LINKCONTROL Command NS 3000/iX 100Base-T Link Statistics Receives / Receives Unicast — Total number of unicast frames (addressed to this specific adapter card) which were successfully received over the medium and forwarded to an upper layer protocol such as IP. This includes unicast frames that were successfully received on the first attempt, as well as unicast frames that were successfully received after being deferred, or that experienced one or more collisions.
LINKCONTROL Command NS 3000/iX 100Base-T Link Statistics CRC or Maxsize error — Number of cyclic redundancy check (CRC) errors or oversized frames that were seen during reception by the link. A CRC error indicates that the frame was checked using CRC-32 frame-checking, but that the value obtained by the CRC did not match the CRC value contained at the end of the frame. CRC errors do not include frames having alignment or coding errors. Oversized frames are those longer than 1518 bytes.
LINKCONTROL Command NS 3000/iX 100Base-T Link Statistics based on address: about 63 percent of all frames received are then being dropped. This level would be considered high. Recv dropped: buffer — Total number of frames received from the adapter card, but dropped because no data buffers were available from the upper layer protocol requesting to receive these frames. This is a relatively common occurrence, amounting to flow control for all protocols sharing those buffers.
LINKCONTROL Command NS 3000/iX 100Base-T Link Statistics value of this 32-bit field is 2147483647. It would be unusual for this statistic to contain a nonzero value. The following receive statistics are only applicable for PCI 100Base-T links: Recv watchdg timeout — The number of times the adapter card tried to receive from the LAN for too long, and had to be forced to stop. This should only occur if the adapter card, the hub, or another adapter card on the network, are faulty.
LINKCONTROL Command NS 3000/iX 100Base-T Link Statistics Secs since clear — The number of seconds elapsed since statistics were last reset via the LINKCONTROL linkname; STATUS=RESET command. This gives the sample time over which the displayed statistics have been collected. Per-time-unit figures may then be calculated if desired. The maximum value of this 32-bit field is 2147483647, or about 68 years.
LINKCONTROL Command NS 3000/iX LAPBMUX Link Statistics NS 3000/iX LAPBMUX 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 LAPBMUX Links.
LINKCONTROL Command NS 3000/iX LAPBMUX Link Statistics linkname;STATUS=CONFIGURATION command: Linkname: PLAPLNK7 Linktype: Physical Path: Physical interface Transmission speed Clock source Local mode Connect timeout :sec Adapter timeout :sec PCI LAPBMUX 0/6/2/1.7 V.
LINKCONTROL Command NS 3000/iX LAPBMUX Link Statistics are as follows: • DTE, for connection to a device that is configured as a DCE. • DCE, for connection to a device that is configured as a DTE. Connect Timeout — The Connect Timeout field displays the current logical link level 2 connection timeout. The Connect Timeout parameter sets the amount of time a node will wait for a logical connection to a remote node to be established. If this timer expires, the node aborts the connection attempt.
LINKCONTROL Command NS 3000/iX LAPBMUX Link Statistics field can be set to a value of 8 or 128, meaning that frames are numbered from either 0 through 7, or 0 through 127. Buffer Size — The Buffer Size field displays the current buffer size. This value will be equal to the buffer size configured in the NMMGR Link screen plus 4 bytes of overhead that is added by the level 3 protocol.
LINKCONTROL Command NS 3000/iX LAPBMUX Link Statistics by Transmit ctrl bytes is distributed over this number of frames. The maximum printable value of this 64-bit field is 17 digits, or about 99 million billion frames. In the previous example, 0 control frames were transmitted at normal priority. Transmits overruns — Total number of frames that were deferred to other network traffic before their initial transmission onto the network.
LINKCONTROL Command NS 3000/iX LAPBMUX Link Statistics normal priority. Receive overruns — Total number of frames that were deferred to other network traffic before their initial transmission onto the network. This means that the 100Base-T card had to wait for carrier to drop and stay dropped for a few nanoseconds, before attempting to transmit the frame. The maximum printable value of this 64-bit field is 17 digits, or about 99 million billion frames.
LINKCONTROL Command NS 3000/iX LAPBMUX Link Statistics Recv deferred — Number of times an address-matched receive frame was temporarily held (queued) by the link driver, because of a momentary lack of DMA resources. Once those resources became available, the frame was automatically transferred to the host. The maximum printable value of this 64-bit field is 17 digits, or about 99 million billion frames. In the previous example, 123 frames were temporarily held.
LINKCONTROL Command NS 3000/iX LAPBMUX Link Statistics 226 Appendix A
B Submitting an CR For further assistance from HP, document the problem as an CR (change 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 CR 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. • Make any NI DMPxxx files available for your HP service representative.
Index Numerics 802 chip restarts, 190 A aborted frames received, 182 aborted frames sent, 182 B Bad_card_on, 199 Bmgr_queued_aloc_on, 198 broadcast reads, 197 broadcast writes, 197 buffer size, 179 C cable type, 179 card, 70 carrier losses, 187 clear to send (CTS), 182 code or align error, 204 commands COMPARE, 87 DATA, 84 DEBUG, 84 DO, 85 EXIT, 85 HELP, 85 HELP ALL, 85 HELP BROWSE, 85 HELP command, 85 HELP COMMANDS, 85 INFILE, 85 LINKCONTROL, 107 LINKCONTROL STATUS, 107 LINKCONTROL TRACE, 107 LISTREDO, 85
Index Do_bind_on, 199 Download_on, 199 DSR losses, 182 local mode, 179 local timeout, 180 loquix reinits, 198 E errors internal, 65 resource, 65 syntax, 65 EXIT command, 85 M MAIN command, 85 MANUAL command, 85 MENUS command, 85 MESSAGES command, 85 modulo count, 179 multicast reads, 197 multicast writes, 197 multicast writes.
Index read buffs avail, 198 read buffs in pool, 198 read bytes, 197 reads aborted, 197 reads completed, 197 receive byte count, 193 receive bytes hipri, 205 receive bytes norm, 204 receive errors, 193, 195 Receive File any, 185 bad, 185 broad, 185 multi, 185 receive filter k_pckts(), 185 receive filter x_pckts(), 186 receive overruns, 182 receives broadcast, 191 receives discarded, 196 receives dropped, 191 receives error, 187 receives hipri, 205 receives lost, 196 receives multicast, 191 receives no error
Index write bytes, 197 writes aborted, 197 writes completed, 196 X X.
