Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments

Displaying NDMP debug messages

What debug messages are  Top

NDMP debug messages provide a detailed description of all active NDMP sessions. The amount of information displayed by a debug message is determined by the ndmpd debug level specified by the user. By default, debug messages are disabled.

Where the filer saves debug messages  Top

Debug messages can be output to the filer console, the NDMP session log file, or both. The ndmpd debug command is used to specify where debug messages will be output. By default, debug messages are output to both the filer console and the NDMP session log.

About the NDMP session log files  Top

NDMP session log files are stored in the /etc/log directory. The file name is ndmplog.yyyymmdd, where yyyy is the year, mm is the month, and dd is the date. For example, the session log file generated on December 5, 2000, is named ndmplog.20001205. The session log file can contain information about one or more NDMP sessions. If multiple NDMP sessions take place on the same day, Data ONTAP saves the information about all sessions to the same session log file. Before generating a fresh NDMP session log file, Data ONTAP deletes all files more than eight days old. Data ONTAP keeps a maximum of eight session log files: one each for the past seven days plus the current day.

Enabling the NDMP debug log messages  Top

To enable NDMP debug logging, complete the following step.

Step

Action

1

Enter the following command:

ndmpd debug n	 

n specifies the debug level from 0 to 70. The default level is 0.

Use 0 for the level to turn the debug messages off. Use a nonzero value for the level to turn the debug messages on.

The levels supported are:

10--Displays connections being made and connections being closed.

30--Displays information regarding the actual NDMP messages such as the message type, sequence numbers, and timestamps. This level also prints out the NDMP errors and some of the relevant fields of the NDMP message.

50--Same as level 30, but includes display of environment variables as well as any exceptions issued by the NDMP server implementation.

70--Same as level 50, but includes display of tape and SCSI command descriptor blocks (CDBs) sent.

Note
CDBs are used for low-level tape and medium changer control.

Displaying the NDMP debug log level  Top

To see the NDMP debug levels currently set, complete the following step.

Step

Action

1

Enter the following command:

ndmpd debug

Result

The current NDMP debug level and toggles are displayed.

Example

filerA> ndmpd debug
ndmpd debug verbose: 0
ndmpd debug stack trace: false
ndmpd debug screen trace: true
ndmpd debug file trace: true

Changing NDMP debug log messages  Top

You use the ndmp debug command to choose whether to display the debug messages on the filer console, to write the debug messages into the NDMP debug log file, and to print out stack traces for any exceptions issued by the NDMP server implementation. To toggle these options, complete the following step:

Step

Action

1

Enter the following command:

ndmpd debug stack|screen|file

stack toggles stack trace printouts on or off.

screen toggles printouts to the filer console on or off.

file toggles printouts to the NDMP log file on or off.

Displaying an NDMP session log file  Top

To display an NDMP session log file, complete the following step.

Step

Action

1

From a UNIX environment...

From an NT environment...

Mount the root volume of the filer to a UNIX client and view the contents of the NDMP session log file using the cat or more UNIX commands or a text editor.

Map the root volume of the filer to the NT system and view the contents of the NDMP session log file using WordPad, Notepad, or an equivalent text-viewing application.

Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments