Troubleshooting
Problem
Two traces are typically required to debug IBM i NetServer problems. The two traces must be collected concurrently. They are:
1. An unfiltered SMB LIC trace (TRCINT).
2. A communications trace (TRCCNN) that is filtered for the IP address of the machine where the problem is being re-created.
1. An unfiltered SMB LIC trace (TRCINT).
2. A communications trace (TRCCNN) that is filtered for the IP address of the machine where the problem is being re-created.
Resolving The Problem
Take these steps before you collect the traces:
If the problem being debugged has anything to do with a failure to map the drive, make sure that the client has no record of those drives. First, ensure that all NetServer network drives, working or not, with device letters assigned or not, are disconnected from the PC before you start any tracing. To do that, run the following command from a Windows command prompt:
If the problem being debugged has anything to do with a failure to map the drive, make sure that the client has no record of those drives. First, ensure that all NetServer network drives, working or not, with device letters assigned or not, are disconnected from the PC before you start any tracing. To do that, run the following command from a Windows command prompt:
| 1. | NET USE The output of the NET USE command shows the status of all mapped network resources. There are four columns of information. The information in parentheses was added by IBM Support as a way of clarifying what those columns mean: Status (of the drive) Local (device ID) Remote (the UNC path) Network (provider being used) Disconnect any of the entries that have Remote values that refer to the NetServer name, host name, or IP address of the IBM i. |
| 2. | When there is a value in the Local column, use the following command to remove it:NET USE n: /Delete (where n: is really the local device ID that NET USE reported) |
| 3. | When there is no local device ID associated with the drive, use the UNC path from the Remote column instead. Run the following command:NET USE \\n.n.n.n\SHARE /Delete (where \\n.n.n.n\SHARE is replaced by the Remote path from the NET USE output). |
After you remove all of those connections, run the NET USE command once more to ensure that there are no connections associated with the NetServer before you start the traces.
Start the traces by using the following commands:
Note: Buffer space is allocated for TRCCNN as soon as the command is run (not dynamically as it is used). Confirm that enough DASD is available on the system before you start the traces. Trace size must not exceed 1000 *MB.
Note: To retrieve the IPv4 address of a PC, run the following command from the PC DOS command prompt:
ipconfig | find "IPv4 Address"| 1. | On the OS/400 command line, execute the TRCCNN and TRCINT commands as follows:TRCCNN SET(*ON) TRCTYPE(*IP) TRCTBL(TRCCNN) SIZE(500 *MB) TCPDTA(*TCP () () *N 'n.n.n.n') ...replacing n.n.n.n with the TCP/IP address of the PC where the issue is to be re-created.TRCINT SET(*ON) TRCTBL(NETSERVER) SIZE(512 *MB) TRCFULL(*WRAP) TRCTYPE(*SMBSVR) |
| 2. | Re-create the error. |
| 3. |
To end the traces, on the OS/400 command line, execute the TRCINT and TRCCNN commands as follows:
TRCINT SET(*OFF) TRCTBL(NETSERVER)There are two options for turning off the connection trace. The first creates two spooled files: TRCCNN SET(*OFF) TRCTBL(TRCCNN)The second option creates a packet capture format output to a stream file.: TRCCNN SET(*OFF) TRCTBL(TRCCNN) OUTPUT(*STMF) TOSTMF('/tmp/AnyFileName.pcap' *YES) ...replacing /tmp/AnyFileName.pcap with the IFS path and file name of your choice.In most cases, the QPCSMPRT, and QSYSPRT spooled files are the preferred output, but in some cases, an IBM i Support representative asks for the pcap file. |
| 4. | You might want to delay taking this step to delete the trace table until IBM confirms that the data received was valid trace data. To clear and delete the trace table after the trace output is spooled (otherwise the storage is not freed), on the OS/400 command line, execute the following:TRCCNN SET(*END) TRCTBL(TRCCNN)TRCINT SET(*END) TRCTBL(NETSERVER) |
Gathering the trace output files:
Ending the TRCCNN trace will create two spool files, both containing the same data: QSYSPRT and QPCSMPRT.
Ending the TRCINT trace creates one QPCSMPRT spool file.
IBM ACS "Printer Output" function can be used to download IBM i spool files.
Download the files to a PC as .txt because traces in .pdf format cannot be analyzed.
IBM ACS "Printer Output" function can be used to download IBM i spool files.
Download the files to a PC as .txt because traces in .pdf format cannot be analyzed.
Sending the output to IBM Support:
Use a file compression tool to compress the data.
| Upload all files to IBM Support by using your web browser and the interface found at: https://www.ecurep.ibm.com/app/upload |
| In the Case "tab", complete the case number as TSxxxxxxxxx (Example: TS123456789). Specify the same case number that the data was collected for. |
| Alternatively, attach the diagnostic data to the case using the Support Portal - https://www.ibm.com/mysupport |
[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CLSAA2","label":"Integrated File System-\u003ENetServer"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]
Historical Number
532581926
Was this topic helpful?
Document Information
Modified date:
04 January 2024
UID
nas8N1012803