Microsoft iSCSI Software Target 3.3 Troubleshooting Guide

Internet Small Computer Systems Interface (iSCSI) is a protocol that supports access to storage devices over a TCP/IP network, which facilitates storage consolidation and sharing of storage resources across an organization. The Microsoft iSCSI Software Target 3.3 (iSCSI Software Target is a service (WinTarget.exe) that implements the iSCSI protocol for storage provision to an iSCSI Initiator.

The iSCSI Software Target is supported on appliances running Windows® Storage Server® 2008 R2, for both standalone and clustered configurations. This document is designed to assist support personnel to troubleshoot and resolve usage issues for the Microsoft iSCSI Software Target on Windows Storage Server 2008 R2.

See the Release Notes provided with the iSCSI Software Target 3.3 Application Package for known issues and late-breaking information about Microsoft iSCSI Software Target 3.3. You can also find more information on the Windows Storage Server blog (http://go.microsoft.com/fwlink/?LinkId=148933).

Basic tracing settings

The Microsoft iSCSI Software Target logs diagnostic messages using the Event Tracing for Windows (ETW) infrastructure.  ETW tracing should be used when the event logs do not provide enough information to determine the cause of the problem.  When you enable ETW tracing for the WinTarget service, you can select from seven different reporting levels, depending on how much (and what type) of information you want to review:

  • 0x01 - Error messages

  • 0x02 - Warning messages

  • 0x04 - Informational messages

  • 0x08 - Verbose messages

  • 0x10 - Network related messages

  • 0x20 - Hex dump iSCSI and iSNS PDUs

  • 0x40 - Dump SCSI CDBs 

  • 0x80 – IO size histogram tracing

  • 0x100 – IO size histogram tracing

Here are the ETA tracing flags for the localmount driver:

  • 0x01 - Error messages

  • 0x02 - Warning messages

  • 0x04 - Informational messages

  • 0x08 - Verbose messages

It is highly recommended that when investigating iSCSI Software Target issues, you should set the ETW settings so that Error and Warning messages are obtained from the iSCSI Software Target. This level of detail can help you during postmortem debugging.

Use the logman.exe utility that is available with Windows Server 2008 R2 to start or stop the collection of ETW data.  Viewing the trace file requires the Trace Format tool (tracefmt.exe) that is available in the IDW toolkit, or in the Windows 2008 R2 platform SDK. Use the Windows 7 version of the IDW toolkit, available at \\winbuilds\release\win7_rtm\7600.16385.090713-1255\amd64fre\bin\idw. The ETW tools combine the trace file with the trace message format (TMF) files to generate readable text.  The TMF files are created as part of the build process under \\winbuilds\release\oob\zamfir\latest\amd64fre\Symbols.pri\TraceFormat.   It is important that you use the TMF files from the correct build.

There are three steps involved in tracing: start tracing, stop tracing and format the trace file. Starting the tracing involves enabling ETW providers and binding them to a tracing session. Multiple providers can be enabled and bound to the same tracing session. In Windows Storage Server 2008 R2, the Local-Mount-Driver WTLmDrv.sys has been added to the available providers.

notePoznámka
For more information about Software tracing, see Getting Started with Software Tracing in Windows Drivers (http://www.microsoft.com/whdc/DevTools/tools/WPP_Intro.mspx).

Provider List file

Use the following GUIDS to individually identify the iSCSI providers:

  • For multiple providers: {bbf8051f-1f47-44ca-ac73-92658cd4e4f8}  0xf 0x0

  • For the local mount driver (Wtlmdrv.sys): {82FB2F8C-A21C-453B-ACBD-7EF49493D727} 0x3f 0x0

Start Tracing - single provider - WinTarget

To start collecting ETW tracing data from the iSCSI Software Target, as an administrator, type the following command line:

logman start <session_name> -p {82fb2f8c-a21c-453b-acbd-7ef49493d727} <trace_flags> 0x0 -o <trace_file_name> -ets

The following table describes the supported command parameters:

 

Argument Description

<session_name>

User-defined name that uniquely identifies this tracing session.

<trace_flags>

Specifies which messages to log to the trace file. It can be one or more of the following:

  • 0x01 - Error messages

  • 0x02 - Warning messages

  • 0x04 - Informational messages

  • 0x08 - Verbose messages

  • 0x10 - Network related messages

  • 0x20 - Hex dump iSCSI and iSNS PDUs

  • 0x40 - Dump SCSI CDBs

  • 0x80 – IO size histogram tracing

  • 0x100 – IO size histogram tracing

<trace_file_name>

The user-defined name of the trace file.

Start tracing - single provider - Wtlmdrv

To start collecting ETW tracing data on multiple iSCSI providers, type the following command from a command line:

logman start <session_name> -p {bbf8051f-1f47-44ca-ac73-92658cd4e4f8} <trace_flags> 0x0 -o <trace_file_name> -ets

The following table describes the supported command parameters:

 

Argument Description

<session_name>

A user-defined name that uniquely identifies this tracing session.

<trace_flags>

Specifies which messages to log to the trace file. It can be one or more of the following:

  • 0x01 - Error messages

  • 0x02 - Warning messages

  • 0x04 - Informational messages

  • 0x08 - Verbose messages

<trace_file_name>

The user-defined name of the trace file.

Start tracing - multiple providers

To start collecting ETW tracing data on multiple iSCSI providers, as an administrator, type the following command from a command line:

logman start <session_name> -pf <guid_file> -o <trace_file_name> -ets

The following table describes the supported command parameters:

 

Argument Description

<session_name>

A user-defined name that uniquely identifies this tracing session.

<guid_file>

A text file with a triple on each line. The triple is <guid> <feature-bits> <tracing-level> The feature bits are documented above for the providers that are relevant for Windows Storage Server 2008 R2. The tracing level is zero or unused for Windows software trace preprocessor (WPP)-based ETW-Classic providers.

<trace_file_name>

The user-defined name of the trace file.

Stop tracing

To stop collecting ETW tracing data from the iSCSI Software Target, as an administrator, type the following command from a command line:

logman stop <session_name> -ets

The following table describes the supported command parameters:

 

Argument Description

<session_name>

The user-defined session name that was specified when the trace was started

Format trace file in text format

To format tracing data (in text format), as an administrator, type the following command from a command line:

tracefmt -o <output_text_file> -p <trace_format_files_path> <trace_file_name>

The following table describes the supported command parameters:

 

Argument Description

<output_text_file>

The name of the output text file.

<trace_format_files_path>

The path to the folder that contains the trace formatted file.

<trace_file_name>

The name of the trace file to be processed.

Format trace file in CSV format

To format tracing data (data that is the TBD format), as an administrator, type the following command from a command line:

tracerpt -of CSV -tp <trace_format_files_path> <trace_file_name> -o <output_text_file>

The following table describes the supported command parameters:

 

Argument Description

<output_text_file>

The name of the output text file

<trace_format_files_path>

The path to the folder that contains the trace format file.

<trace_file_name>

The name of the trace file to be processed.

Sample usage

The following two examples show how to use the ETW tool to collect ETW tracing data and process it for use. The first example specifies a single GUID. The second example shows how you can obtain data from multiple GUIDs, combine them into one file and view them in one ETW tracing session.

Example 1:

logman start targettrace -p {82fb2f8c-a21c-453b-acbd-7ef49493d727} 0x03 0x0 -o target.etl -etslogman stop targettrace -etstracefmt -o target.txt -p d:\bins.iscsi-3.2-qfe.amd64chk\iscsi\sapporo\Symbols.pri\TraceFormat target.etl

Example 2:

logman.exe staRT WinTargetTrace -pf guids.txt -ets -o %temp%\WinTargetTrace.etllogman.exe stop WinTargetTrace  -etstracerpt.exe -of CSV -tp <Symbols.pri>\TraceFormat %temp%\WinTargetTrace.etl -o %temp%\WinTargetTrace.txt

Debugging tips

This section provides information of how to use the New Technology Symbolic Debugger (NTSD) or the kernel debugger (KD) to debug major issues that could occur between an iSCSI Initiator and the iSCSI Software Target.

This section includes the following information:

  • Install the latest debugger

  • Obtain the latest operating system symbols

  • Debug memory leaks

  • Debug handle leaks

  • Debugging a DLL

  • Debugging optimized code

  • Debugging WinTarget.exe Using the KD

notePoznámka
Some tips are not specifically applicable to debugging the iSCSI Software Target. However, for the purposes of completeness and convenience to support personal, they are listed here.

Install the latest version of the debugger

Install the latest debugger package available here:

\\dbg\privates\latest\dbginstall.cmd

By default, this installs the debugger to C:\Debuggers.

Obtain the current operating system symbols

Debugging is easier when you have the operating system symbols. Operating system symbols can be accessed from the Symbols server (http://msdl.microsoft.com/download/symbols).

Debugging memory leaks

Debugging a memory leak requires taking a snapshot of the memory before the operation that causes the leak, then taking another snapshot after the operation and finally comparing the two.  An effective tool to accomplish this job is umdh.exe which is a part of the debugger package.

notePoznámka
See this KB article for more detailed information: Umdhtools.exe: How to use Umdh.exe to find memory leaks (http://go.microsoft.com/fwlink/?LinkId=200147).

Debugging handle leaks

The process of finding the source of leaking handles is similar to that of a memory leak. The only difference resides in the tool that is used.  The tool of choice is the !htrace debugger extension.  See debugger Help for usage-specific details about this command.

Debugging a DLL

In some cases, a DLL that you need to debug is not yet loaded when you open the process.  An example of this is trying to debug the self-registration code of a DLL using the regsvr32.exe process.  If the DLL is not yet loaded into memory, you cannot set a breakpoint because the debugger does not have the symbols for it yet.  You first have to make the debugger break into the process when it loads the DLL using the command "sxe ld:<DLL name>". Once the debugger has broken into the DLL, you can then set breakpoints as you normally do.

Debugging Wintarget service startup

To debug the service startup code, you must do the following:

  1. Use Regedit to change the Service Control Manager (SCM) Timeout value to a large number so the SCM does not think the service is hung and tries to kill it.

    HKLM\System\CurrentControlSet\Control      Value Name: ServicesPipeTimeout      Type: REG_DWORD      Value: 3600000 (1 hour in milliseconds)

  2. Use gflags.exe (part of the debugger package) to attach a debugger to the service process when it starts by specifying a debugger in the Image File tab.  Set the debugger to the following:

    c:\debuggers\cdb.exe -server tcp:port=9999

  3. Start the service.  The starting of the service will appear to hang but it's actually broken into the debugger.

  4. Attach a debugger to the remote session created by cdb by typing the following command at a command prompt:

    c:\debuggers\windbg.exe -remote tcp:port=9999

Debugging optimized code

Local variables look different in source code than they do in the debugger stack when optimization is turned on. Here's a blog that gives tips on how to debug optimized code: Challenges of Debugging Optimized x64 Code (http://go.microsoft.com/fwlink/?LinkId=200151).

Debugging Wintarget.exe using the KD

The following commands show how to debug Wintarget.exe:

To view stacks:

!process 0 1f WinTarget.exe

To set stack context:

.thread /p /r <thread-address>

To reload user-mode symbols:

.reload /user

To display stack trace:

. knSet frame context:.frame /r

Using iscsitgtext.dll debugger extension

The debugger extension can be found at this location:

\\winbuilds\release\oob\zamfir\<build>\amd64fre\dbg\files\bin\pri\iscsitgtext.dll

Once in the context of the WinTarget.exe process, and assuming that the symbol path has already been set-up to include the iSCSI Software Target-related symbols, you can use the following commands:

HostMgr – Lists the configured targets, initiators and VHD’s associated with it.

0:013> !iscsitgtext.hostmgr
wintarget!CHost 0000000004119a50
    TargetIQN iqn.1991-05.com.microsoft:ivanbrug-t-clu0-clu00-target
    IDMethods:
           +0x000 eMethod : 4 ( IDIQN )
           +0x004 szValue : [512]  "*"
    LUN Mappings:
      wintarget!CWTDisk 0000000003fa90e0
        m_dwWTD         0
        m_ResourceName  VHD 0
        m_ResourceState 2
      wintarget!CWTDisk 0000000003edd0e0
        m_dwWTD         1
        m_ResourceName  VHD 1
        m_ResourceState 2
      wintarget!CWTDisk 00000000040010e0
        m_dwWTD         2
        m_ResourceName  VHD 2
        m_ResourceState 2
      wintarget!CWTDisk 00000000040e90e0
        m_dwWTD         3
        m_ResourceName  VHD 3
        m_ResourceState 2
      wintarget!CWTDisk 0000000003edf0e0
        m_dwWTD         4
        m_ResourceName  VHD 4
        m_ResourceState 2
    Active sessions:
      m_Sessions[00]
        wintarget!CSession 0000000003eb1d40
          +0x490 m_pHost                  : 0x00000000`04119a50 CHost
           +0x498 m_ActualIdMethod         : 4 ( IDIQN )
           +0x4ac m_szInitiatorDnsName     : [261]  ""
           +0x6b6 m_szInitiatorIpAddress   : [261]  ""
           +0x8c0 m_szInitiatorMacAddress  : [261]  "00-06-4F-64-17-A9"
           +0xaca m_szInitiatorIqn         : [224]  "iqn.1987-05.com.intel:001517CBCD98"
           +0xc8a m_szInitiatorIpv6Address : [261]  "2001:4898:f0:1001:1ee:a893:7660:7a6"
           +0xe94 m_szTargetIqn            : [224]  "iqn.1991-05.com.microsoft:ivanbrug-t-clu0-clu00-target"


Diskmgr – Lists currently configured VHDs and their backend storage implementation. For example, if it’s fixed, differencing or snapshot.

0:013> !iscsitgtext.diskmgr
    wintarget!CWTDisk 0000000003fa90e0 - 'VHD 0'
       +0x058 m_pDevice          : 0x00000000`03ea5fa0 CScsiDevice
       +0x060 m_dwWTD            : 0
       +0x47e m_szDevicePath     : [512]  "r:\HyperVHostDisk0.vhd"
       +0x888 m_eLMType          : 0 ( DoNotMount )
       +0xa9c m_eLMStatus        : 0 ( DoNotMount )
       +0xad4 m_ShadowSnapshotId : _GUID {00000000-0000-0000-0000-000000000000}
       +0xd00 m_szResourceName   : [261]  "VHD 0"
       +0xf10 m_ResourceState    : 2 ( ClusterResourceOnline )

       wintarget!CFixedVhdDevice 0000000003ea5fa0
           +0x00c m_dwWTD                  : 0
           +0x010 m_eDeviceType            : 1 ( FileDevice )
           +0x1b00 m_bIsDeviceValid         : 0n1
           +0x1b70 m_hDevice                : 0x00000000`00000460 Void
           +0x1b78 m_pVhdFooter             : 0x00000000`03e7cc00 _VHD_FOOTER
           +0x1b80 m_pVhdDynHeader          : (null)
           +0x1fe0 m_Bat                    : (null)
           +0x1fe8 m_BatSize                : 0
           +0x1ff0 m_SectorBitmapLookup     : (null)
           +0x1ff8 m_SectorBitmapLookupSize : 0

    wintarget!CWTDisk 0000000003edd0e0 - 'VHD 1'
       +0x058 m_pDevice          : 0x00000000`03f3ffa0 CScsiDevice
       +0x060 m_dwWTD            : 1
       +0x47e m_szDevicePath     : [512]  "S:\HyperVHostDisk0.vhd"
       +0x888 m_eLMType          : 0 ( DoNotMount )
       +0xa9c m_eLMStatus        : 0 ( DoNotMount )
       +0xad4 m_ShadowSnapshotId : _GUID {00000000-0000-0000-0000-000000000000}
       +0xd00 m_szResourceName   : [261]  "VHD 1"
       +0xf10 m_ResourceState    : 2 ( ClusterResourceOnline )

       wintarget!CFixedVhdDevice 0000000003f3ffa0
           +0x00c m_dwWTD                  : 1
           +0x010 m_eDeviceType            : 1 ( FileDevice )
           +0x1b00 m_bIsDeviceValid         : 0n1
           +0x1b70 m_hDevice                : 0x00000000`00000470 Void
           +0x1b78 m_pVhdFooter             : 0x00000000`0404bc00 _VHD_FOOTER
           +0x1b80 m_pVhdDynHeader          : (null)
           +0x1fe0 m_Bat                    : (null)
           +0x1fe8 m_BatSize                : 0
           +0x1ff0 m_SectorBitmapLookup     : (null)
           +0x1ff8 m_SectorBitmapLookupSize : 0

    wintarget!CWTDisk 00000000040010e0 - 'VHD 2'
       +0x058 m_pDevice          : 0x00000000`03f09fa0 CScsiDevice
       +0x060 m_dwWTD            : 2
       +0x47e m_szDevicePath     : [512]  "U:\HyperVHostDisk0.vhd"
       +0x888 m_eLMType          : 0 ( DoNotMount )
       +0xa9c m_eLMStatus        : 0 ( DoNotMount )
       +0xad4 m_ShadowSnapshotId : _GUID {00000000-0000-0000-0000-000000000000}
       +0xd00 m_szResourceName   : [261]  "VHD 2"
       +0xf10 m_ResourceState    : 2 ( ClusterResourceOnline )

       wintarget!CFixedVhdDevice 0000000003f09fa0
           +0x00c m_dwWTD                  : 2
           +0x010 m_eDeviceType            : 1 ( FileDevice )
           +0x1b00 m_bIsDeviceValid         : 0n1
           +0x1b70 m_hDevice                : 0x00000000`0000046c Void
           +0x1b78 m_pVhdFooter             : 0x00000000`03fcbc00 _VHD_FOOTER
           +0x1b80 m_pVhdDynHeader          : (null)
           +0x1fe0 m_Bat                    : (null)
           +0x1fe8 m_BatSize                : 0
           +0x1ff0 m_SectorBitmapLookup     : (null)
           +0x1ff8 m_SectorBitmapLookupSize : 0

    wintarget!CWTDisk 00000000040e90e0 - 'VHD 3'
       +0x058 m_pDevice          : 0x00000000`03f1bfa0 CScsiDevice
       +0x060 m_dwWTD            : 3
       +0x47e m_szDevicePath     : [512]  "T:\HyperVHostDisk0.vhd"
       +0x888 m_eLMType          : 0 ( DoNotMount )
       +0xa9c m_eLMStatus        : 0 ( DoNotMount )
       +0xad4 m_ShadowSnapshotId : _GUID {00000000-0000-0000-0000-000000000000}
       +0xd00 m_szResourceName   : [261]  "VHD 3"
       +0xf10 m_ResourceState    : 2 ( ClusterResourceOnline )

       wintarget!CFixedVhdDevice 0000000003f1bfa0
           +0x00c m_dwWTD                  : 3
           +0x010 m_eDeviceType            : 1 ( FileDevice )
           +0x1b00 m_bIsDeviceValid         : 0n1
           +0x1b70 m_hDevice                : 0x00000000`00000224 Void
           +0x1b78 m_pVhdFooter             : 0x00000000`03e68c00 _VHD_FOOTER
           +0x1b80 m_pVhdDynHeader          : (null)
           +0x1fe0 m_Bat                    : (null)
           +0x1fe8 m_BatSize                : 0
           +0x1ff0 m_SectorBitmapLookup     : (null)
           +0x1ff8 m_SectorBitmapLookupSize : 0

    wintarget!CWTDisk 0000000003edf0e0 - 'VHD 4'
       +0x058 m_pDevice          : 0x00000000`03fabfa0 CScsiDevice
       +0x060 m_dwWTD            : 4
       +0x47e m_szDevicePath     : [512]  "V:\HyperVHostDisk0.vhd"
       +0x888 m_eLMType          : 0 ( DoNotMount )
       +0xa9c m_eLMStatus        : 0 ( DoNotMount )
       +0xad4 m_ShadowSnapshotId : _GUID {00000000-0000-0000-0000-000000000000}
       +0xd00 m_szResourceName   : [261]  "VHD 4"
       +0xf10 m_ResourceState    : 2 ( ClusterResourceOnline )

       wintarget!CFixedVhdDevice 0000000003fabfa0
           +0x00c m_dwWTD                  : 4
           +0x010 m_eDeviceType            : 1 ( FileDevice )
           +0x1b00 m_bIsDeviceValid         : 0n1
           +0x1b70 m_hDevice                : 0x00000000`00000468 Void
           +0x1b78 m_pVhdFooter             : 0x00000000`04045c00 _VHD_FOOTER
           +0x1b80 m_pVhdDynHeader          : (null)
           +0x1fe0 m_Bat                    : (null)
           +0x1fe8 m_BatSize                : 0
           +0x1ff0 m_SectorBitmapLookup     : (null)
           +0x1ff8 m_SectorBitmapLookupSize : 0

sessmgr: commend that reports active iSCSI session information, that include related targets, pending IOs (both towards the network or disk)

0:013> !iscsitgtext.sessmgr
  00000000 - 0000000003f8ff50 (0000000003df6f50,0000000003ddef50,0000000003df6f50)
  wintarget!SOCKADDR_STORAGE 0000000003f8ff68
    10.121.24.89:3260
    Index: 02
  00000001 - 0000000003ddef50 (0000000003f8ff50,0000000003f3df50,00000000041e3f50)
  wintarget!SOCKADDR_STORAGE 0000000003ddef68
    10.121.26.123:3260
    Index: 03
  00000002 - 00000000041e3f50 (0000000003df6f50,0000000003ddef50,0000000003df6f50)
  wintarget!SOCKADDR_STORAGE 00000000041e3f68
    10.121.26.245:3260
    Index: 07
  00000003 - 0000000003f3df50 (0000000003ddef50,0000000003df6f50,0000000003f31f50)
  wintarget!SOCKADDR_STORAGE 0000000003f3df68
    [2001:4898:f0:1001:5fb:d71:da51:d7ff]:3260
    Index: 00
  00000004 - 0000000003f43f50 (0000000003df6f50,0000000003f31f50,0000000003df6f50)
  wintarget!SOCKADDR_STORAGE 0000000003f43f68
    [2001:4898:f0:1001:1c1a:385d:4259:cd8a]:3260
    Index: 05
  00000005 - 0000000003f31f50 (0000000003f43f50,0000000003f3df50,0000000003df6f50)
  wintarget!SOCKADDR_STORAGE 0000000003f31f68
    [2001:4898:f0:1001:3e34:a217:142d:54e3]:3260
    Index: 01
   wintarget!CSession 0000000003eb1d40
       +0x490 m_pHost                  : 0x00000000`04119a50 CHost
       +0x498 m_ActualIdMethod         : 4 ( IDIQN )
       +0x4ac m_szInitiatorDnsName     : [261]  ""
       +0x6b6 m_szInitiatorIpAddress   : [261]  ""
       +0x8c0 m_szInitiatorMacAddress  : [261]  "00-06-4F-64-17-A9"
       +0xaca m_szInitiatorIqn         : [224]  "iqn.1987-05.com.intel:001517CBCD98"
       +0xc8a m_szInitiatorIpv6Address : [261]  "2001:4898:f0:1001:1ee:a893:7660:7a6"
       +0xe94 m_szTargetIqn            : [224]  "iqn.1991-05.com.microsoft:ivanbrug-t-clu0-clu00-target"
       wintarget!CBufferPool 0000000003eb1d80 - PduBuffer
            AvailableBuffers - (part of the Allocated ones)
            AllocatedBuffers
            wintarget!PDU_BUFFER - pData : References
            00000000146c0000 - 00000000146c0fd0 : 1
            0000000015b30000 - 0000000015b30fd0 : 1
            0000000015b50000 - 0000000015b50fd0 : 1
            0000000015b90000 - 0000000015b90fd0 : 1
            0000000015bd0000 - 0000000015bd0fd0 : 1
            0000000015c10000 - 0000000015c10fd0 : 1
            0000000015e30000 - 0000000015e30fd0 : 1
            00000000179e0000 - 00000000179e0fd0 : 1
            0000000017a20000 - 0000000017a20fd0 : 1
            0000000017d00000 - 0000000017d00fd0 : 1
            0000000018620000 - 0000000018620fd0 : 1
       wintarget!CBufferPool 0000000003eb1de0 - Pdu
            AvailableBuffers - (part of the Allocated ones)
            AllocatedBuffers
            wintarget!PDU
            000000000bf48fe0
       wintarget!CBufferPool 0000000003eb1e40 - ScsiDataSmall
            AvailableBuffers - (part of the Allocated ones)
            AllocatedBuffers
            wintarget!LPBYTE   0x1000
            0000000009c70000
       wintarget!CBufferPool 0000000003eb1ea0 - ScsiDataMedium
            AvailableBuffers - (part of the Allocated ones)
            AllocatedBuffers
            wintarget!LPBYTE  0x10000
            000000000aec0000
       wintarget!CBufferPool 0000000003eb1f00 - ScsiDataLarge
            AvailableBuffers - (part of the Allocated ones)
            AllocatedBuffers
            wintarget!LPBYTE 0x100000
            0000000015490000
       wintarget!CBufferPool 0000000003eb1f60 - FileIoCtx
            AvailableBuffers - (part of the Allocated ones)
            AllocatedBuffers
            wintarget!_FILE_IO_CONTEXT Pdu.pBuffer pNextUnAcked pDataInHead
            000000000bbb1ca0 - 0000000015b30000 0000000000000000 0000000000000000
       + wintarget!CConnection 0000000004079ea0
             m_PendingReadsBufferPool
            AvailableBuffers - (part of the Allocated ones)
            AllocatedBuffers
            wintarget!_SOCK_RECV_CONTEXT - pPduBuffer : dwPduBufferSize
            0000000001ad7fb0 - 00000000060a0000 : 00010038
            0000000001c3bfb0 - 0000000015f50000 : 00010038
            0000000001c7ffb0 - 00000000175a0000 : 00010038
            0000000001f73fb0 - 0000000016110000 : 00010038
            00000000025a0fb0 - 0000000015990000 : 00010038
            00000000026eafb0 - 0000000015b90000 : 00010038
            00000000026ecfb0 - 0000000015ed0000 : 00010038
            0000000002792fb0 - 0000000014780000 : 00010038
            000000000b12dfb0 - 00000000146c0000 : 00010038
            000000000b155fb0 - 0000000018620000 : 00010038
            000000000b1f4fb0 - 00000000160f0000 : 00010038
            000000000b20afb0 - 0000000005fe0000 : 00010038
            000000000b250fb0 - 0000000008ae0000 : 00010038
            000000000b39bfb0 - 0000000016050000 : 00010038
            000000000b41bfb0 - 0000000015c70000 : 00010038
            000000000b453fb0 - 0000000017d00000 : 00010038
            000000000b4abfb0 - 0000000016230000 : 00010038
            000000000b4bffb0 - 0000000008ae0000 : 00010038
            000000000b57bfb0 - 0000000016210000 : 00010038
            000000000b5a7fb0 - 0000000017980000 : 00010038
            000000000b615fb0 - 0000000015c10000 : 00010038
            000000000b629fb0 - 0000000015e30000 : 00010038
            000000000b799fb0 - 0000000018620000 : 00010038
            000000000b803fb0 - 00000000160d0000 : 00010038
            000000000b805fb0 - 0000000015f30000 : 00010038
            000000000b82afb0 - 000000000ae80000 : 00010038
            000000000b84afb0 - 0000000015ef0000 : 00010038
            000000000b8b1fb0 - 00000000176e0000 : 00010038
           000000000ba08fb0 - 0000000007710000 : 00010038
            000000000ba10fb0 - 0000000015b50000 : 00010038
            000000000ba4cfb0 - 0000000016170000 : 00010038
            000000000ba7dfb0 - 0000000015eb0000 : 00010038
            000000000baabfb0 - 0000000018260000 : 00010038
            000000000bba7fb0 - 0000000016130000 : 00010038
            000000000bbdffb0 - 0000000015e70000 : 00010038
            000000000bbedfb0 - 0000000016070000 : 00010038
            000000000bc21fb0 - 0000000016190000 : 00010038
            000000000bc2bfb0 - 0000000015f10000 : 00010038
            000000000bc39fb0 - 000000000e180000 : 00010038
            000000000bc65fb0 - 0000000015bd0000 : 00010038
            000000000bd23fb0 - 0000000015c10000 : 00010038
            000000000bd27fb0 - 00000000161f0000 : 00010038
            000000000bd4cfb0 - 0000000017ba0000 : 00010038
            000000000bd60fb0 - 00000000160b0000 : 00010038
            000000000bd68fb0 - 0000000016030000 : 00010038
            000000000bde6fb0 - 00000000161b0000 : 00010038
            000000000be0ffb0 - 0000000015e70000 : 00010038
            000000000be3dfb0 - 0000000015b10000 : 00010038
            000000000be47fb0 - 00000000161d0000 : 00010038
            000000000be5cfb0 - 0000000015c50000 : 00010038
            000000000bf50fb0 - 0000000015f90000 : 00010038
            000000000bf52fb0 - 0000000017d00000 : 00010038
            000000000bf69fb0 - 00000000179e0000 : 00010038
            000000001662afb0 - 0000000017a20000 : 00010038
           00000000170cbfb0 - 0000000015f70000 : 00010038
            0000000017128fb0 - 0000000016150000 : 00010038
            000000001712afb0 - 0000000016090000 : 00010038
            00000000171f4fb0 - 0000000014d10000 : 00010038
             m_pPendingReadsHead
                 wintarget!_SOCK_RECV_CONTEXT 000000000ba10fb0
                 wintarget!_SOCK_RECV_CONTEXT 000000001662afb0
                 wintarget!_SOCK_RECV_CONTEXT 000000000bc65fb0
                 wintarget!_SOCK_RECV_CONTEXT 00000000026eafb0
                 wintarget!_SOCK_RECV_CONTEXT 000000000b629fb0
                 wintarget!_SOCK_RECV_CONTEXT 000000000b12dfb0
                 wintarget!_SOCK_RECV_CONTEXT 000000000b799fb0
                 wintarget!_SOCK_RECV_CONTEXT 000000000bf69fb0
                 wintarget!_SOCK_RECV_CONTEXT 000000000bf52fb0
                 wintarget!_SOCK_RECV_CONTEXT 000000000b615fb0
0:013>

Logdevmgr – reports the target portals and their current status

0:013> !iscsitgtext.locdevmgr
  00000000 - 0000000003ff5e10 (0000000003e00e10,0000000003f2de10,0000000003e00e10)
  wintarget!PORTAL 0000000003ff5e50
   +0x000 Guid             : _GUID {0f378573-d552-4df9-b7b8-e502aa1d53b5}
   +0x010 szIpAddress      : [128]  "10.121.24.89"
   +0x110 dwPort           : 0xcbc
   +0x114 bListen          : 0n1
   +0x118 bSecure          : 0n0
   +0x11c bValid           : 0n1
  00000001 - 0000000003f2de10 (0000000003ff5e10,0000000003e00e10,0000000004115e10)
  wintarget!PORTAL 0000000003f2de50
   +0x000 Guid             : _GUID {9e7adf2a-60b7-401b-8ebe-262128e63459}
   +0x010 szIpAddress      : [128]  "10.121.26.123"
   +0x110 dwPort           : 0xcbc
   +0x114 bListen          : 0n1
   +0x118 bSecure          : 0n0
   +0x11c bValid           : 0n1
  00000002 - 0000000004231e10 (0000000003e00e10,0000000004011e10,0000000003e00e10)
  wintarget!PORTAL 0000000004231e50
   +0x000 Guid             : _GUID {8ea58742-2e89-4b7f-9e56-984cbc770208}
   +0x010 szIpAddress      : [128]  "10.121.26.245"
   +0x110 dwPort           : 0xcbc
   +0x114 bListen          : 0n1
   +0x118 bSecure          : 0n0
   +0x11c bValid           : 0n1
  00000003 - 0000000004011e10 (0000000004231e10,0000000004115e10,0000000003e00e10)
  wintarget!PORTAL 0000000004011e50
   +0x000 Guid             : _GUID {fa422277-1c32-438d-b040-c2544cfa330b}
   +0x010 szIpAddress      : [128]  "2001:4898:f0:1001:1c1a:385d:4259:cd8a"
   +0x110 dwPort           : 0xcbc
   +0x114 bListen          : 0n1
   +0x118 bSecure          : 0n0
   +0x11c bValid           : 0n1
  00000004 - 0000000004115e10 (0000000004011e10,0000000003f2de10,0000000004005e10)
  wintarget!PORTAL 0000000004115e50
   +0x000 Guid             : _GUID {bc25e3e8-fbac-4a46-af4b-a7e4e856d748}
   +0x010 szIpAddress      : [128]  "2001:4898:f0:1001:3e34:a217:142d:54e3"
   +0x110 dwPort           : 0xcbc
   +0x114 bListen          : 0n1
   +0x118 bSecure          : 0n0
   +0x11c bValid           : 0n1
  00000005 - 0000000004005e10 (0000000003e00e10,0000000004115e10,0000000003e00e10)
  wintarget!PORTAL 0000000004005e50
   +0x000 Guid             : _GUID {a9e800a8-ed46-42ce-95c6-18891f72e120}
   +0x010 szIpAddress      : [128]  "2001:4898:f0:1001:5fb:d71:da51:d7ff"
   +0x110 dwPort           : 0xcbc
   +0x114 bListen          : 0n1
   +0x118 bSecure          : 0n0
   +0x11c bValid           : 0n1

Zobrazit: