[ Contents ]

Assigning SPDs

Using drag and drop, you can assign an SPD to a new server, assign an SPD to a different server, and re-assign the LUN/volume either from one server to another or within the same server.

To assign an SPD to a new server using the drag and drop resource allocation method:

  1. Log in as a user with the privileges of an ssconfig user to assign storage resources. Login as ssconfig user to each server that is participating in storage resource assignment.

  2. Click the Resource View tab to go to the Resource View. Select the desired SPD icon from the available SPDs.

  3. Click an SPD icon and drag it to the desired server icon to be assigned.


  4. When the desired server icon is highlighted, release the icon.


  5. A confirmation prompt is displayed. If the information provided is correct, click OK.

  6. If you do not have ssconfig privileges, a login dialog may be displayed for you to login as an ssconfig user before the operation can be completed. If the SPD resource allocation succeeds, the SPD will be attached to the specified server. Now the SPD is associated with the specified server for this example. In this case, you could now format, create file systems and mount the file systems, or assign a drive letter for this device on the server.

To Assign SPDs to Different Server

  1. Make sure that no application running on the host is currently using the device on the SPD to be reassigned from one server to another.

    For example, under Windows NT, make sure that the drive letter assigned to this SPD is not currently in use.

    Under UNIX make sure that the file system on this SPD device is not mounted and in use.

  2. Select the SPD from the server from which you want it to be unassigned, and drag it to the server to which you want it to be assigned. When the desired server icon (drop target) is highlighted, release the icon.

    A confirmation prompt is then displayed. If the information provided is correct, click OK. If the SPD resource re-allocation succeeds, the SPD is now displayed under the specified server.

To reassign the LUN/volume either from one server to another or within the same server:

  1. Make sure that you have formatted and created file system or assigned drive letter to the device on the server that you want to re-assign.

    If the storage resource is not formatted for use by the operating system, then the resource cannot be dynamically reassigned and mounted or assigned drive letter for use by the application automatically.

    In the Resource View, each tree node is listed with a descriptive tag.


  2. Verify that the no application is using this storage resource before continuing.


  3. Select the SPD that you want re-assigned under the server and drag it to the Available SANpath Devices icon.

  4. If the file system on the resource to be reassigned is in use by any application, the following prompt appears (for example, if the device has a mounted file system, or application such as Windows Explorer currently has this drive selected.)

  5. If the operation succeeds, the SPD is displayed under Available SANpath Devices.

  6. Expand the SPD that was just moved to Available SANpath Devices. Display the servers to which this resource can be reassigned dynamically by double-clicking the server name.

  7. Click New MP/DL in the list box and specify the new mount point or the driver letter under which you want this resource to be reassigned on the server. Make sure that you press Enter after the new mount point or driver letter is entered to enable Apply.


  8. Click Apply and then close the view.


  9. Select this SPD icon and drag it to the server to which this resource is to be reassigned.
  10. Now the resource is available on the server under the new mount point or drive letter specified. Any application can access this resource for use.

    NOTE: Under Solaris, if you have made use of this dynamic LUN assignment feature, the table of file system defaults such as /etc/vfstab might have been modified to ensure the availability of the resource across system reboots. If you uninstall the SANpath software or reconfigure the SANpath, make sure to verify the entries in the file system table defaults file such as /etc/vfstab.

[ Contents ]