Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
 HP 9000 Networking: HP FTAM/9000 User's Guide > Chapter 6 Resolving FTAM Problems

Network and Resource Errors
» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

spacerspacerspacer
spacer
spacer
  		 
 

Network and resource errors occur when some aspect of the network which supports FTAM fails to operate correctly. Errors in this category include hardware failures and resource exhaustion. For example, if the network cable is damaged or disconnected, all network operations (including FTAM) will fail. Likewise, if the lower layers of the network are not running, FTAM failures will occur. Local failures can sometimes be attributed to resource constraints.

Network and resource errors are typically more involved than user errors, and require more time and expertise to analyze and correct. A system as complex as an OSI network has many potential points of failure. However, these all show up at the FTAM user interface as one of the following problems:

  • "Attempted operation failed."

  • "Connect attempt aborted."

  • "FTAM service provider unavailable."

  • "Ftam command: out of memory"

  • "No address for hostname."

  • "Datatransfer cancelled."

If you are in "verbose mode" you will also get the additional message "check log file with log instance log_instance_value". Log instances are discussed in “About FTAM Troubleshooting” later in this chapter.

What To Do with a Network or Resource Error

Hewlett-Packard recommends the following steps for troubleshooting network errors detected by FTAM:

  1. If you receive one of the errors listed above, retry the command that failed. Occasionally a transient problem will be cleared up by the time you retry the command. If the command continues to fail, you will have to initiate troubleshooting by following the next step.

  2. Turn on verbose mode (ftam> setv), reproduce the error, and write down the "log instance" number that appears in the error message. This number will be important as you begin further troubleshooting. See the section following for a general overview of troubleshooting.

  3. Turn to the OSI Troubleshooting Guide. That document contains detailed information about troubleshooting the network. Troubleshooting is easiest when performed by an experienced person.

About FTAM Troubleshooting

The information in this section is general. The OSI Troubleshooting Guide (part number: 32070-90020) provides more detailed information.

Troubleshooting a network error can be difficult and time-consuming, so Hewlett-Packard's OSI products (including HP FTAM/9000) provide substantial troubleshooting aids. When a network error occurs (say a cable gets accidently disconnected), some lower layer of the software detects the problem. It assigns the error a unique identifying number, called a "log instance ".

The error, and its log instance, are noted (or "logged") in a special file. Then the error is passed to the next layer in the network. As the error propagates up through the network layers, each layer logs the problem, and passes the error along. Eventually, the error appears at the interface as an error message with an associated log instance.

The log instance returned by the FTAM interface you are using directly corresponds to an FTAM error recorded in the product log files. By using this log instance to reference the log files, you can track the problem back through successive lower layers of the network, eventually to the source of the problem. The steps to accomplish this are covered in the OSI Troubleshooting Guide.

API Tracing

API tracing allows FTAM programmers and users to get detailed information about the interaction of an FTAM program with the HP FTAM API (Application Programmatic Interface) without having to access any source code. API tracing is of primary interest to FTAM programs and is explained in detail in the "Handling Errors" chapter of the HP FTAM/9000 Programmer's Guide. API tracing can be enabled or disabled during an interactive FTAM session as follows:

  • Setting the API to 0 disables API tracing.

  • Setting the API to 1 causes procedure entry and exit to be traced.

  • Setting the API to 2 causes input parameters, as well as procedure entry and exit, to be traced.

The following example causes procedure entry and exit to be traced:

set api 1



User Errors
  		 


Chapter 7 FTAM File Details  
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 1997 Hewlett-Packard Development Company, L.P.