readme.txt

WMI implementation in a iSCSI miniport can be tested using the iscsicli.exe application, device ma

    WMI implementation in a iSCSI miniport can be tested using the iscsicli.exe 
application, device manager property pages, WBEMTEST.exe and scripts
generated by the wmimofck.exe tool.

See http://support.microsoft.com/default.aspx?scid=kb;EN-US;q252679 for more
information.

Below is the list of classes and those that are required to be implemented
and those that are recommended.

Core Functionality
    - Must implement
MSiSCSI_TCPIPConfig
MSiSCSI_HBAInformation
MSiSCSI_InitiatorSessionInfo
MSiSCSI_Operations
     (DeleteInitiatorNodeName and SetInitiatorNodeName method are optional)
MSiSCSI_PersistentLogins
MSiSCSI_TargetMappings
MSiSCSI_LUNMappingInformation
MSiSCSI_AdapterEvent
MSiSCSI_ConnectionStatistics (Windows 2003 Server only)
MSiSCSI_SessionStatistics (Windows 2003 Server only)
MSiSCSI_InitiatorLoginStatistics (Windows 2003 Server only)
MSiSCSI_InitiatorInstanceStatistics (Windows 2003 Server only)
MSiSCSI_NICPerformance (Windows 2003 Server only)


    - May implement
MSiSCSI_NICConfig
MSiSCSI_BootConfiguration
MSiSCSI_HBASessionConfig
MSiSCSI_InitiatorNodeFailureEvent
MSiSCSI_InitiatorInstanceFailureEvent

Discovery
    - Must implement if discovery is supported.
MSiSCSI_DiscoveryConfig
MSiSCSI_DiscoveryOperations

IPSEC/CHAP
    - Must implement if ipsec and/or CHAP are supported
MSiSCSI_SecurityCapabilities
MSiSCSI_SecurityConfigOperations
MSiSCSI_MMIPSECStats  (Windows 2003 Server only)
MSiSCSI_QMIPSECStats  (Windows 2003 Server only)
MSiSCSI_RADIUSConfig