Windows 2000 known problems and issues Attaching to a Microsoft Windows 2000 or 2003 host

This information provides information about known problems and issues when attaching to a Windows 2000 host.

It is strongly recommended that you create VDisks using the command line interface, and specify the -scsi parameter. Otherwise, the VDisks may be assigned to the wrong SCSI LUN, and cause the Microsoft Clustering Services to fail.

Example

After creating two VDisks using the command line interface, you enter these commands to assign your VDisks to a host:

  1. svctask mkdiskhostmap -host host1 VDISK1
  2. svctask mkdiskhostmap -host host1 VDISK2
  3. svctask mkdiskhostmap -host host2 VDISK2
  4. svctask mkdiskhostmap -host host2 VDISK1

In this example, host2 will assign VDISK2 to SCSI LUN 0 by default because it will be the first assigned disk. There will be a conflict because host1 has VDISK2 assigned to SCSI LUN 1.

To avoid this problem, issue the commands as follows:

  1. svctask mkdiskhostmap -host host1 -scsi 0 VDISK1
  2. svctask mkdiskhostmap -host host1 -scsi 1 VDISK2
  3. svctask mkdiskhostmap -host host2 -scsi 0 VDISK1
  4. svctask mkdiskhostmap -host host2 -scsi 1 VDISK2
Related topics Attaching to a Microsoft Windows 2000 or 2003 host

(C) Copyright International Business Machines Corporation 2003, 2004