电磁学知识点总结上课讲义

电磁学第四版知识点总结一、磁场的基本概念1、磁体的周围存在磁场。

2、电流的周围也存在磁场。

3、变化的电场在周围空间产生磁场(麦克斯书)。

4、磁场和电场一样，也是一种特殊物质。

5、磁场不仅对磁极产生力的作用，对电流也产生力的作用。

6、磁场的方向一在磁场中的任一点，小磁针北极受力的方向，亦即小磁针静止时北极所指的方向，就是那一点的磁场方向。

7、磁现象的电本质:磁铁的磁场和电流的磁场样，都是由电荷的运动产生的。

二、磁场的基本性质磁场对放入其中的磁极或电流有磁场力的作用，(对磁极-定有力的作用:对电流只是可能有力的作用，当电流和磁感线平行时不受磁场力作用)。

1、磁极和磁极之间有磁场力的作用2、两条平行直导线。

当通以相同方向的电流时，它们相互吸引，当通以相反方向的电流时，它们相互排斥。

3、电流和电流之间，就像磁极和磁极之间一样，也会通过磁场发生相互作用。

4、磁体或电流在其周围空间里产生磁场，而磁场对处在它里面的磁极或电流有磁场力的作用。

5、磁极和磁极之间。

磁极和电流之间、电流和电流之间都是通过磁场来传递的。

三、磁感应强度(矢量)1、在磁场中垂直于磁场方向的通电导线，所受的安培力F安跟电流I和导线长度L的乘积儿的比值叫做磁感应强度B=IL/F安，(B ⊥L,LI小)。

2、磁感应强度的单位:特斯拉3、磁感应强度的方向:就是磁场的方向，小碰针静止时北极所指的方向，就是那一点的磁场方向，磁感线上各点的切线方向就是这点的磁场的方向。

也就是这点的磁感应强度的方向。

4、磁感应强度的叠加一类似于电场的叠加四、磁感线1、是在磁场中画出的一些有方向的曲线，在这些曲线上，每一点的切线方向都在该点的磁场方向上。

磁感线的分布可以形象地表示出磁场的强弱和方向。

2、磁感线上各点的切线方向就是这点的磁场的方向，也就是这点的磁感应强度的方向。

3、磁感线的密疏表示磁场的大小。

在同一个磁场的磁感线分布图上，磁感线越密的地方，表示那里的磁感应强度越大。

磁现象知识点1 简单的磁现象1．磁体任何磁体都具有两个磁极（N、S极）．磁极间的相互作用规律是：同名磁极互相排斥，异名磁极互相吸引．（1）磁体具有吸铁性（能吸引铁、钴、镍等物质）和指向性（受地磁的影响）．（2）磁体上磁极的磁性最强．2．磁场磁体周围空间存在着磁场，磁场具有方向性．磁场基本性质：对放入其中的磁体具有磁力的作用．（1）磁场看不见，摸不着，但它是客观存在的，可以通过一些现象来认识．例如：将一磁铁靠近一静止的小磁针，小磁针就会发生偏转，拿开磁铁，小磁针静止后又恢复原来的指向．（2）磁场的方向可由小磁针静止时的指向来表现：在磁场中的某一点，小磁针静止时N极的指向就是该点的磁场方向．3．磁感线是为形象描述磁场而画出的一些有方向的假想的曲线，磁感线上的任何一点的曲线方向都跟放在该点的小磁针N极所指的方向一致．磁体周围的磁感线都是从磁体的N极出来，回到S极；磁体内部的磁感线由磁体S极指向N极；磁感线是一些闭合的曲线，任何两条磁感线不能相交；磁感线在磁体周围空间是立体分布的，越密集的地方表示磁性越强．4．地磁场地球本身是一个巨大的磁体．在地球周围的空间里存在着磁场，这个磁场叫做地磁场．地球两极跟地磁两极并不重合．地磁的北极在地球南极附近，地磁的南极在地球的北极附近．水平放置的磁针的指向跟地球子午线间的交角叫做磁偏角．世界上第一个清楚而又准确地论述磁偏角的是我国宋代的科学家沈括．【例1】将挂着铁球的弹簧测力计在水平放置的条形磁铁上自左向右逐渐移动时，弹簧测力计的示数将．【例2】弹簧秤下悬挂一条形磁铁．使弹簧沿着水平放置的大条形磁铁从左端极开始，向右端极处逐渐移动时，弹簧秤示数将（）A．逐渐增大 B．逐渐减小C．先减小后增大 D．先增大后减小【例1】如图所示，小磁针处于静止状态，请在图中甲、乙处标出磁极极性（用"或S表示）并画出磁感线（每个磁极画两条）【例1】重为10N，边长为5cm的正方形磁铁吸附在铁板上，磁铁与铁板间的吸引力为15N，把它按图a放置，磁铁对铁板的压强是 Pa；按照图b那样放置，磁铁（在上）对铁板的压强是 Pa；按图c那样放置，磁铁（在下）对铁板的压强是 Pa．。

电磁学知识点汇总稳恒电流1、电流：（电荷的定向移动形成电流） 定义式： I =Qt微观式： I = nesv ，（n 为单位体积内的电荷数，v 为自由电荷定向移动的速率。

）（说明：将正电荷定向移动的方向规定为电流方向。

在电源外部，电流从正极流向负极；在电源内部，电流从负极流向正极。

） 2、电阻：定义式：R UI=（电阻R 的大小与U 和I 无关） 决定式：R = ρSL（电阻率ρ只与材料性质和温度有关，与横截面积和长度无关）3、电阻串联、并联的等效电阻：串联：R =R 1+R 2+R 3 +……+R n并联：121111nR R R R =++4、欧姆定律：（1）部分电路欧姆定律（只适用于纯电阻电路）：I UR=（2）闭合电路欧姆定律：I =ER r+ ①路端电压： U = E －I r = IR ②有关电源的问题： 总功率： P 总= EI输出功率： P 总= EI －I 2r = I R 2（当R =r 时，P 出取最大值，为24E r） 损耗功率： P I r r=2电源效率： η=P P 出总=UE= R R+r 5、电功和电功率：电功：W =UIt 电功率：P =UI 电热：Q=I Rt 2 热功率：P 热=2I R对于纯电阻电路： W= Q UIt=2I Rt U =IR对于非纯电阻电路： W >Q UIt >I Rt 2 U >IR （欧姆定律不成立）例 如图所示，M 、N 是平行板电容器的两个极板，R 0为定值电阻，R 1、R 2为可调电阻，用绝缘细线将质量为m 、带正电的小球悬于电容器内部。

闭合电键S ，小球静止时受到悬线的拉力为F 。

调节R 1、R 2，关 于F 的大小判断正确的是（ ） A ．保持R 1不变，缓慢增大R 2时，F 将变大B．保持R1不变，缓慢增大R2时，F将变小C．保持R2不变，缓慢增大R1时，F将变大D．保持R2不变，缓慢增大R1时，F将变小答案：B例如图所示，电动势为E、内阻不计的电源与三个灯泡和三个电阻相接。

1．电磁感应现象利用磁场产生电流的现象叫做电磁感应产生的电流叫做感应电流。

2．产生感应电流的条件①当闭合电路的一部分导体在磁场里做切割磁感线的运动时，电路中产生了感应电流。

②当磁体相对静止的闭合电路运动时，电路中产生了感应电流．③当磁体和闭合电路都保持静止，而使穿过闭合电路的磁通量发生改变时，电路中产生了感应电流．其实上述①、②两种情况均可归结为穿过闭合电路的磁通量发生改变，所以，不论用什么方法，只要穿过闭合电路的磁通量发生变化，闭合电路中就有电流产生．3．电磁感应现象中的能量守恒电磁感应现象中产生的电能不是凭空产生的，它们或者是其他形式的能转化为电能，或者是电能在不同电路中的转移，电磁感应现象遵循能量守恒定律．Microsoft iSCSI Software Initiator 2.xUsers GuideMicrosoft CorporationPublished: June 2005Updated: October 2005The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT.Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.© 2003 Microsoft Corporation. All rights reserved.Microsoft, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.The names of actual companies and products mentioned herein may be the trademarks of their respective owners.Introduction (6)References and Resources (6)Architectural overview and features (6)Requirements (7)Services that depend upon iSCSI devices (8)What has been tested and determined to work (8)Tested Configurations: (8)Not supported by the software initiator: (10)Installation (11)How the iSCSI Initiator Service Manages Targets (14)Node Names (14)Initiator Instance (15)Discovery mechanisms (15)How targets are organized (16)Security (17)Using the Microsoft iSCSI Initiator Service (18)Initiator IQN Name (18)Persistent Targets (19)Running automatic start services on iSCSI disks (19)Management applications/Interfaces (20)iSCSI Control Panel Applet (20)iSCSI Property Pages (20)iSCSICLI (20)WMI (20)Perfmon/Sysmon (23)Multipathing I/O (23)Troubleshooting (46)Terminal Services on Windows 2000 (46)Eventlog (46)Debug Logging (46)Installation (47)Other Areas (49)Appendix A - Event Tracing in MS iSCSI Drivers (53)Appendix B - iSCSI Eventlog messages (54)Microsoft iSCSI Initiator Service (54)Microsoft Software Initiator Kernel Mode Driver (56)Appendix C – iSCSICLI command reference (64)Appendix D – Microsoft iSCSI Software Initiator Error Codes (84)IntroductionThe Microsoft iSCSI Software Initiator package adds support to the Windows operating system for using iSCSI targets that support 1.0 of the iSCSI spec. This user‟s guide will briefly explain the architecture, the requirements, functionality, interfaces and usages of the product. It also includes a troubleshooting section that may be useful in case errors or problems occur. References and ResourcesThe following link contains various resources and references related to iSCSI including whitepapers and support guides/windowsserver2003/technologies/storage/iscsi/default.mspxLink to download the Microsoft iSCSI Software Initiator:/downloads/details.aspx?FamilyID=12cb3c1a-15d6-4585-b385-befd1319f825&DisplayLang=enThe latest version is always maintained at this link. This page will include links to previous versions or QFEs if applicable.Microsoft Designed for Windows Logo Program for iSCSI DevicesTo ensure Microsoft support, users must make sure that the iSCSI target and any iSCSI HBA or multifunction device are listed on in the Windows Catalog. To determine if the iSCSI target, iSCSI bridge device or iSCSI HBA you are using has received the Designed for Windows Logo, you can search for it here:/windows/catalog/server/default.aspx?xslt=category&subid=22&pgn=72f496f6-369e-4657-8fe4-7603a28ab667Alternatively, a list of targets is also maintained at this location to as a backup since there are sometimes problems with the Windows Catalog Search. < >Vendors who have not yet Logo‟d their iSCSI hardware device, should review the iSCSI Logo requirements and Logo testing required in HCT 12.1 available at this website:/whdc/hwtest/default.mspxArchitectural overview and featuresThe Microsoft iSCSI Software Initiator package is composed of four main components●Software initiator kernel mode driver (mini-port driver - msiscsi.sys)An optional iSCSI device driver component that is responsible for moving data from the storage stack over to the standard network stack. This initiator is only used when iSCSI traffic goes over standard network adapters, not when specialized iSCSI HBA adapters are used.●iSCSI port driver (iscsiprt.sys)A port driver that implements Windows specific functionalities such as Plug and Play, Power Management, Command Queuing, etc. The software initiator driver (msiscsi.sys) and some multi-function HBA drivers (bus and mini-port) will use this port driver.●Initiator service (iscsiexe.exe)A service that manages all iSCSI initiators (including network adapters and HBAs) on behalf of the OS. Its functions include aggregating discovery information and managing security. It includes an iSNS client, the code required for device discovery.●Management applicationsThe iSCSI command line interface (iSCSICLI), property pages for device management, Windows Management Instrumentation (WMI), and a control panel application.●Microsoft MPIO Multipathing Support for iSCSI (MPIO and iSCSI DSM drivers)MPIO provides high availability and load balancing to storage devices.Both the management api interfaces and the kernel mode initiator driver interfaces are very well defined and thus allow Independent Software Vendors (ISVs) and Independent Hardware Vendors (IHVs) to leverage these interfaces to produce value add components. The Microsoft iSCSI Software Initiator package includes a software based iSCSI kernel mode initiator driver that uses the Windows TCP/IP stack and one or more network interface cards (NICs) exposed to Windows. IHVs can build specialized iSCSI initiator hardware (iSCSI HBA) and write a SCSIport miniport or Storport miniport driver that can be used by the iSCSI initiator service. Microsoft recommends the use of Storport miniports on Windows Server 2003 and Windows XP, x64. Storport is not available on Windows 2000 or Windows XP, so SCSIport must be used on those platforms. These drivers must support the Microsoft iSCSI driver interfaces in order to work properly with the iSCSI Initiator service. These iSCSI HBA drivers can be used in place of the software initiator driver or in conjunction with the software initiator driver. Since the iSCSI initiator service aggregates all kernel mode initiator drivers to coordinate iSCSI management in Windows, a management application vendor can include iSCSI support in its management application by writing directly to the iSCSI management interfaces and thus be able to manage both hardware and software initiator drivers in a common way. Microsoft only supports the use of iSCSI HBAs that have been Logo‟d under the Designed for Windows Logo Program.Note: Microsoft does not support the use of 3rd party iSCSI software initiators on Windows.RequirementsThe Microsoft iSCSI Software Initiator package runs with Windows 2000 SP4 or higher, Windows XP SP1 or higher and Windows 2003 Server or higher. To use the iSCSI software initiator kernel mode driver, the system must include a qualified Designed for Windows NIC and this card must be configured to use the TCP/IP protocol. To use an HBA with the Microsoft iSCSI initiator service, the HBA must implement the required Microsoft iSCSI driver interfaces as outlined in the Microsoft iSCSI Driver Development Kit. The software initiator kernel mode driver supports version 1.0 of the iSCSI specification (RFC 3790) recently ratified by the Internet Engineering Task Force (IETF). An iSCSI target that also supports version 1.0 of the iSCSI specification is also required.Services that depend upon iSCSI devicesA special note should be made regarding the timing of the availability of devices that are connected to the system via the MS iSCSI software initiator. These iSCSI devices are presented to Windows later in the boot process than direct attached storage is presented. There are some applications and services that make assumptions about the timing of the availability of the devices at boot. The iSCSI initiator service and the Windows Service Control Manager include functionality for helping these services and applications synchronize with the arrival of devices and volumes hosted on iSCSI targets.The basic mechanism works as follows. The iSCSI initiator service is configured to be automatically started by the service control manager during system startup. This service can be configured to delay completing its service startup sequence until a list of devices and disk volumes has completed initialization. If there is another service that is configured to be automatically started during system startup and this service has an assumption that all devices and disk volumes are available before it starts or a service whose code or data is installed on an iSCSI disk volume then that service must be configured to start after the iSCSI initiator service completes its initialization. On Windows 2000 this is accomplished by making the services dependent upon the iSCSI initiator service. On Windows XP and 2003 the iSCSI initiator service is configured to start in a load order group and thus will always be started before any services that are not in a load order group. So in this case there is no need to change any service dependencies.What has been tested and determined to workTested Configurations:The following have been tested by Microsoft and are known to work with the Microsoft iSCSI initiator service, with the following notes. This is not an inclusive list, just what Microsoft has tested and verified in its lab.Microsoft ClustersMicrosoft Server Cluster (MSCS) shared storage (including the quorum disk) can beimplemented using iSCSI disk volumes as the shared storage so long as the iSCSItarget supports the SCSI RESERVE and RELEASE commands. There is no specialiSCSI, cluster or application configuration needed to support this scenario. Since thecluster service manages application dependencies, it is not needed to make any clustermanaged service (or the cluster service itself) dependent upon the Microsoft iSCSIservice.Microsoft MPIO and the Microsoft iSCSI DSM can be used with MSCS. OnWindows 2000 only the failover load balance policy is supported. Note that Microsoftdoes note support the use of iSCSI Server clusters with Windows 2000. BecauseiSCSI Server clusters are just now being introduced, we anticipate that mostdeployments will use Windows Server 2003. Technically iSCSI clusters work wellfor both Windows 2000 and Windows Server 2003 but because of the anticipateddeployments and the desire of avoiding various testing, administrative and supportcosts, Microsoft has decided to focus our efforts on Win2003 and to not supportWindows 2000. Please see this link for more information:/windowsserver2003/technologies/storage/iscsi/iscsicluster.mspxOn Windows 2003, all other load balance policies are supported if the iSCSI targetsupports SCSI PERSISTENT RESERVE and PERSISTENT RELEASE and thepersistent reserve key is established on all nodes of the cluster. To configure thepersistent reservation key for your cluster, you need to assign 8 byte keys to all nodes in the cluster. Pick a 6 byte value that is specific to that cluster and a different 2 byte values for each node in the cluster. The cluster specific value should be different for different clusters on your SAN to protect a cluster from using the wrong storagedevice.To configure the persistent reservation key for your cluster:1. Select a 16-byte value that is unique to that cluster.2. Locate the following registry key:HKLM\System\CurrentControlSet\Services\MSiSCDSM\PersistentReservation3. Add the following values:a. UsePersistentReservation REG_DWORD 1Setting this value to 1 enables Persistent Reservation.b. PersistentReservationKey REG_BINARY <PR key>This is a 16-byte binary value that is unique to the cluster. The same binary value must be usedon all nodes in the cluster.Note:These registry values must be added to all nodes in the cluster.<PR Key> is an 8 byte binary value that is composed of a 6 byte part that is specificto the cluster and a 2 byte part that is specific to the node. For example if you have a three node cluster you could assign 0xaabbccccbbaa as the cluster specific part. Thenodes could then have the following PR keys:Node 1: 0xaabbccccbbaa0001Node 2: 0xaabbccccbbaa0002Node 3: 0xaabbccccbbaa0003ExchangeMicrosoft Exchange Server can store its program files, mailboxes, public folders, logs and other data on iSCSI disk volumes in both cluster and non cluster configurations.Since Microsoft Exchange has a service component, in a non cluster configuration,the Exchange service needs to be configured with a dependency on the iSCSI initiator2.0 service on Windows 2000. When using the Microsoft iSCSI Software Initiator 2.0with Windows 2003, the dependency is not needed. In an MSCS configuration, thedependency does not need to be configured since the dependency on the disk ishandled by the cluster service.SQLMicrosoft SQL Server can store its program files, logs and other data on iSCSI diskvolumes in both cluster and non cluster configurations. Since Microsoft SQL Serverhas a service component, in a non cluster configuration, the SQL service needs to beconfigured with a dependency on the iSCSI initiator service on Windows 2000. Whenusing the Microsoft iSCSI Software Initiator 2.0 with Windows 2003, the dependencyis not needed. In an MSCS configuration the dependency does not need to beconfigured since the dependency on the disk is handled by the cluster service.File shares/DFSThere is a special requirement if file shares are exposed on iSCSI disk volumes usingthe Microsoft software iSCSI initiator. For example, if you have an iSCSI diskvolume that is exposed as drive I: and have a file share point I:\Documents then youwill need to configure the lanmanserver service to have a dependency on the msiscsi(Microsoft iSCSI initiator) service on Windows 2000. When using the MicrosoftiSCSI Software Initiator 2.0 with Windows 2003, the dependency is not needed.Not supported for use with the Microsoft iSCSI Software Initiator:(These are not supported by the Microsoft software iSCSI initiator; they may be supported by a hardware-based iSCSI initiator (HBA))Dynamic disks (applies to Windows 2000 and Windows Server 2003)Configuring volumes on iSCSI disks as Dynamic disk volumes using the Microsoftsoftware iSCSI initiator is not currently supported. It has been observed that timingissues may prevent dynamic disk volumes on iSCSI disks from being reactivated atsystem startup.Hardware-based iSCSI initiators (iSCSI Host Bus Adapters or “HBA s”) can typicallymake the devices that it connects to available much earlier during the system startupprocess than the iSCSI software initiator can. Therefore, iSCSI HBAs may providesupport for dynamic disk volumes.BootCurrently, it is not possible to boot a Windows system using an iSCSI disk volumeprovided by the Microsoft software iSCSI initiator kernel mode driver. It would bepossible to boot a Windows system using an iSCSI disk volume provided by an iSCSIHBA that supports booting via Int 13h BIOS extensions. The only currentlysupported method for booting a Windows system using an iSCSI disk volume is via asupported HBA (currently, an HBA that implements the required iSCSI driverinterfaces and uses a storage miniport is a supported HBA).NIC TeamingMicrosoft does not support the use of NIC teaming on iSCSI interfaces. Microsoftrecommends as an alternative that you use dual ported NICs and allow MicrosoftWindows components to control fail-over and redundancy to ensure consistentvisibility into the data path. Those mechanisms can include Microsoft MPIO, MCS(multiple connections per session, or MSCS (Microsoft Server Cluster Service).InstallationTo install the iSCSI Initiator package, run the appropriate installer package for yourcomputer by typing its name on the command line or double-clicking on the file iconfrom an Explorer window. Administrator privileges are required to install theMicrosoft iSCSI Software Initiator package.The installer package uses the Software Update Installation Wizard based onupdate.exe technology to install or upgrade the Microsoft iSCSI initiator. Theinstaller can be run in interactive, passive, or quiet mode. The interactive mode allowsthe user to select the installation options from the wizard, while the passive and quietmodes allow installation options to be selected by environment variable settings. iSCSI-2.0-ia64chk.exe - Checked (Debug) version for computers based on the ia64 processor architecture. This will install only on a free (retail) build of Windows.iSCSI-2.0-ia64fre.exe - Free (Retail) version for computers based on the ia64 processor architecture. This will install only on a free (retail) build of Windows.iSCSI-2.0-x86chk.exe - Checked (Debug) version for computers based on the x86 processor architecture. This will install only on a free (retail) build of Windows.iSCSI-2.0-x86fre.exe - Free (Retail) version for computers based on the x86 processor architecture. This will install only on a free (retail) build of Windows.iSCSI-2.0-amd64chk.exe - Checked (Debug) version for computers based on the x64 processor architecture. This will install only on a free (retail) build of Windows.iSCSI-2.0-amd64fre.exe - Free (Retail) version for computers based on the x64 processor architecture. This will install only on a free (retail) build of Windows.The installer package uses the Software Update Installation Wizard to effect the installation or upgrade of the Microsoft iSCSI Software Initiator. To use the wizard you click Next to advance to the next page, Back to revert to the previous page and Cancel to cancel the installation or upgrade. The installer can be run in an interactive mode, a passive mode and a quiet mode. The interactive mode allows the user to select the installation options from the wizard while the passive and quiet modes allow the installation options to be selected via an environment variable.Four selections are presented in the wizard:iSCSI Port Driver (iscsiprt)– This is always checked and cannot be unchecked. All configurations require the port driver and thus it is always installed.Initiator Service (iscsiexe.exe)– This is the usermode iSCSI initiator service and is required for all iSCSI Software Initiator installations using iSCSI HBA or the iSCSI software Software Initiator.Software Initiator (msiscsi.exe)- This is the kernel mode iSCSI software initiator driver and is used to connect to iSCSI devices via the Windows TCP/IP stack using NICs. If this option is selected then the Initiator Service option is also selected automatically.Microsoft MPIO Multipathing Support for iSCSI. –The following drivers are installed when you install the Microsoft MPIO component:●Mpio.sys (multipath bus-driver)1.Acts as a …pseudo-bus‟ driver and is responsible for creating and controlling themultipath physical disk device objects.municates with the other drivers that are part of the multipath solution.3.Co-ordinates PnP and Power operations that affect multiple multipath components.4.Provides a method (via WMI) for vendors to monitor and manage their StorageEnclosures and the associated iSCSI DSM●Mpspfltr.sys (port-driver filter)1.Ensures that PnP and Power IRPs sent to te HBA‟s miniport driver or ISCSI softwareinitiator driver are properly handled by the rest of the multipath solution.2.Provides notifications from the port driver to the multipath bus-driver for such eventsas enumeration of the bus, power operations, and various PnP events.●Mpdev.sys (replacement disk driver)1.Forwards PnP and Power events to the multipath bus-driver2.Responds to directives from the multipath physical device object to which it isassociated.3.Forwards I/O requests from the multipath physical device object and disallowsrequests from other upper-layer software.●Msiscdsm.sys (device specific module driver for iSCSI)1.Responsible for implementing the load balance policies and maintaining the settingsduring a reboot.2.Provides routing information to Mpio.sys such as which path to a device should bechosen to process a request.3.Handles device-specific initialization.4.Interprets or issues commands such as reserve or release.5.Identifies conditions requiring a request to be retried or when a fail-over is warranted.6.Handles failing over to another path.7.Provides an optional interface via WMI to a user-mode administrative application. This installs the core MS MPIO files and the Microsoft iSCSI Device Specific Module (DSM). This will enable the MS iSCSI software initiator and HBA to perform session based multipathing to a target that supports multiple sessions to a target. If the version of MS MPIO core files is later than the version installed on the computer then the core MS MPIO files will be upgraded to the latest version that is part of the installation package. Microsoft MPIO is supported on Windows 2000 Server platforms, Windows Server 2003 platforms, and future Windows Server platforms. Microsoft MPIO is not supported on Windows XP or Windows 2000 Professional. When installing the Microsoft iSCSI Software Initiator package on either Windows XP or Windows 2000 Professional, the Microsoft MPIO check-box will be greyed out.To add or remove specific MS iSCSI Software Initiator components run the setup package executable and configure the checkboxes to match the desired installation. The app should autocheck the boxes for components that are already installed. For example if you want to add the MS MPIO component then you‟d leave the other checkboxes alone and just check the MS MPIO checkbox. Note that if the MS MPIO checkbox is not checked then the installer will attempt to uninstall the Microsoft iSCSI DSM and the core MS MPIO files. However if there is another DSM installed then the core MS MPIO files will not be uninstalled. The setup app determines if another DSM is installed by checking the MS MPIO supported device list.To completely uninstall the MS iSCSI Software Initiator package go to the Add/Remove program applet in the control panel and click on the remove button for the MS iSCSI Software Initiator package. The uninstall will completely uninstall the iSCSI initiator package including the kernel mode driver, initiator service and MS MPIO support, although if there is another DSM then the core MS MPIO files will not be uninstalled.If the MS iSCSI Initiator package version 1.06 is installed the installer package will upgrade it. Note that if you uninstall the 2.0 initiator package then both 1.06 and 2.0 versions of iSCSI initiator package are uninstalled. It is not possible to rollback to 1.06.If you have a multifunction iSCSI adapter that depends upon the iSCSI port driver then you should install the iSCSI initiator installation package first before plugging in the multifunction iSCSI adapter. If you did plug in the adapter first then you will need to update drivers for the adapter after installing the Microsoft iSCSI port driver.The Microsoft iSCSI Software Initiator package installation program supports two types of unattended operations, passive mode and quiet mode. Passive mode will show UI but will not interact with the user but instead use default values for any user prompts. Quiet mode will not show any UI and will not interact with the user and will use default values for any user prompts. Note that in both passive and quiet modes that if the installer is instructed to reboot the PC then the PC will be reboot automatically when the installer completes.In unattended installations, the installer uses command line switches defined in the below table and specified in the environment variable ISCSI_SETUP_OPTIONS to select components for installation.If switches are specified in the ISCSI_SETUP_OPTIONS environment variable, then the installer will cause the corresponding checkboxes to be selected. If switch are not specified in theenvironment variable, then the installer will cause the corresponding checkboxes to be unselected. For example, including the /Service and /SoftwareInitiator switches in the environment variable will check the Initiator Service and the Software Initiator Kernel Mode driver checkboxes and uncheck the MPIO checkbox. If the installer is then run in passive or quiet mode, the Initiator Service and Kernel Mode Software Initiator driver will be installed and iSCSI MPIO support will be uninstalled.If the environment variable is not set, the installer will determine which components are already installed and set checkboxes for each installed component. If the installer is run in passive or quiet mode then previously installed components will be upgraded and components that were not previously installed will not be installed.Running Quiet Mode Unattended InstallationTo perform an unattended install using quiet mode and install all of the components included with iSCSI initiator package, enter the following commands:set ISCSI_SETUP_OPTIONS=/Service /SoftwareInitiator /MPIO%PATHTOPACKAGE%\2.00-initiator-x86fre.exe /quietIf you upgrade the initiator, the server may automatically restart once the installation is complete. If you want to prevent the server from automatically restarting, add the /norestart switch:%PATHTOPACKAGE%\2.00-initiator-x86fre.exe /quiet /norestartIf the installer needs a reboot to complete installation, but a reboot is not performed then the iSCSI initiator package will be in an undefined state and may not work properly.If you receive an error during the installation, you should consult the installer logfile %windir%\iscsiins.log. Additional information may be recorded in the update package logfile %windir%\iscsi200.log and the setupapi log file %windir%\setupapi.log.To perform an unattended uninstall, enter the following command:%windir%\$NtUninstalliscsi200$\spuninst\spuninst.exe /passive or /quiet /forcerestartHow the iSCSI Initiator Service Manages TargetsNode NamesThe MS iSCSI initiator service strictly follows the rules specified for iSCSI node names. The rules are applied for both the initiator‟s node name and any target node names discovered. Rules for building iSCSI node names are described in the iSCSI specification and the “String Profile for iSCSI Names” internet draft. In summary the rules ar e as follows:-Node names are encoded in the UTF8 character set. Note the initiator service does not support UCS-4 characters. RFC 2044 describes UTF8 encoding.-Node names are 223 bytes or less-Node names may contain alphabetic characters (a to z), numbers (0 to 9) and three special characters: ….‟, …-…, and …:‟.-Uppercase characters are always mapped to lowercase.。