|
Mar 4 2010, 3:24 PM EST
|
|
|
edit |
1 word added
1 word deleted
|
|
Change: 20008,2008, make sure and check out this document:Configuring Dell PowerEdge 11G Servers Running Windows Server 2008 for iSCSI SAN BootBy Dell Storage Interoperability EngineeringThis section documents creating multipath connections to iSCSI LUNs on a Dell
View changes from previous version.
(Word count: 571)
|
|
Mar 4 2010, 3:05 PM EST
|
|
|
edit |
|
|
Change: There were only format changes (bold, italics, etc.) in this version. See this version for details.
(Word count: 571)
|
|
Feb 26 2010, 11:40 AM EST
|
|
|
edit |
8 words added
|
|
Change: The following document was written for Windows 2003. For Windows 20008, make sure and check out this document:Configuring Dell PowerEdge 11G Servers Running Windows Server 2008 for iSCSI SAN BootBy Dell Storage Interoperability EngineeringThis section documents creating multipath connections to
View changes from previous version.
(Word count: 571)
|
|
Feb 26 2010, 11:38 AM EST
|
|
|
edit |
28 words added
|
|
Change: Configuring Dell PowerEdge 11G Servers Running Windows Server 2008 for iSCSI SAN BootBy Dell Storage Interoperability EngineeringThis section documents creating multipath connections to iSCSI LUNs on a Dell PowerVault MD3000i using the
View changes from previous version.
(Word count: 563)
|
|
Sep 28 2007, 6:00 PM EDT
|
|
|
edit |
|
|
Change: There were only format changes (bold, italics, etc.) in this version. See this version for details.
(Word count: 535)
|
|
Sep 28 2007, 5:57 PM EDT
|
|
|
edit |
116 words added
7 images added
3 images deleted
|
|
Change: of any of the sessions: The load balance policy may be set by selecting Advanced. Round Robin with Subset is the default. Note that the two paths corresponding to the MD3000i controller that currently owns the LUN are Active; the other two are in Standby mode:
View changes from previous version.
(Word count: 535)
|
|
Sep 28 2007, 3:42 PM EDT
|
|
|
edit |
37 words added
2 images added
|
|
Change: not share virtual disks with other hosts: Upon creation a Virtual Disk was created on the MD3000i and mapped to the host. The final Host Topology is: Back on the Microsoft initiator on the host, the MD3000i Target was selected and Log On selected:
View changes from previous version.
(Word count: 402)
|
|
Sep 28 2007, 3:38 PM EDT
|
|
|
edit |
2 words added
1 word deleted
|
|
Change: like:like : The MDSM Configure Host Access (Manual) function was used to give the host access to the MD3000i. First, the host name and operating system type were entered: Then the host’s iSCSI initiator was added to the list of Selected iSCSI Initiators: On the next
View changes from previous version.
(Word count: 365)
|
|
Sep 28 2007, 3:34 PM EDT
|
|
|
edit |
82 words added
6 images added
2 images deleted
|
|
Change: The MDSM Configure Host Access (Manual) function was used to give the host access to the MD3000i. First, the host name and operating system type were entered: Then the host’s iSCSI initiator was added to the list of Selected iSCSI Initiators: On the next screen it
View changes from previous version.
(Word count: 365)
|
|
Sep 28 2007, 3:09 PM EDT
|
|
|
edit |
60 words added
4 images added
|
|
Change: appeared: After selecting the language the Select Installation Type screen came up: “Host” was selected since the MD3000i was already being managed from another server. Upon completion of the installation the Microsoft iSCSI Initiator was started: In the Discovery tab, the four IP addresses of the MD3000i were entered:
View changes from previous version.
(Word count: 282)
|
|
Sep 28 2007, 2:57 PM EDT
|
|
|
edit |
28 words added
2 images added
1 image deleted
|
|
Change: hard drive by clicking on the error message and then run. After rebooting the Resource CD was inserted again, “Install MD3000i Storage Software” was selected and the iSCSI timeout value was adjusted by selecting “OK” at the next prompt:
View changes from previous version.
(Word count: 222)
|
|
Sep 28 2007, 2:53 PM EDT
|
|
|
edit |
116 words added
2 images added
|
|
Change: The MD3000i uses its own Device Specific Module code and thus required special installation of the Microsoft iSCSI Initiator. Therefore, on the server being connected
View changes from previous version.
(Word count: 194)
|
|
Sep 28 2007, 2:47 PM EDT
|
|
|
edit |
65 words added
27 words deleted
1 image added
|
|
Change: LUN upwas hereserver soon.r3win2950b Inrunning 64-bit Windows Server 2003 R2. As shown below each MD3000i controller had two iSCSI ports, with one each in the meantime10.10.20 and if10.10.22 yousubnets. haveThe anyr3win2950b problemsconnected contactto meboth atnetwork dave_jaffe@dell.comsubnets.
View changes from previous version.
(Word count: 73)
|
|
Sep 13 2007, 11:10 PM EDT
|
|
|
edit |
29 words added
57 words deleted
1 image deleted
|
|
Change: Introduction to the topics on the pageblah blah blah
Topic Name Quick Links
Link1
Link3
Link3
Link4
<TOPIC> Whitepapers
More detailed topic links
Link1I -have Moresuccessfully detaileddone infothis onand Link1Link2will -capture Descriptionthe ofscreen whatshots Link2and is
View changes from previous version.
(Word count: 31)
|
|
Sep 13 2007, 11:08 PM EDT
|
|
|
create |
No content added or deleted. |
|
Change: Created by Sep 13 2007, 11:08 PM EDT for: no reason given
|