Configuring the operating system to, Recognize virtual disk changes – HP StorageWorks EVA Controller HSG V8.8 Software User Manual

Page 77

Advertising
background image

Using the Storage Window

77

Command Console V2.5 User Guide

Configuring the Operating System to Recognize Virtual Disk

Changes

The Client does not perform all of the system configuration necessary to make
your subsystem's virtual disks visible to the user in the operating system.

When you create or delete virtual disks using either the Command Line Interface
(CLI) or Client, you are adding or removing “disks” in the subsystem in a manner
similar to plugging or unplugging physical disk drives on the host bus. In either
case, there are certain operating system configuration actions you must perform to
make these “disks” visible or invisible to the operating system's file system.

Windows NT/Windows 2000/Windows Server 2003 Configuration

On a Windows NT, Windows 2000, or Windows Server 2003 host, after you
create or delete a virtual disk, you must perform the following steps to properly
configure the file system to recognize your changes:

1. Start the host system. This action has the effect of forcing the Disk

Administrator or Disk Management to recognize added virtual disks as raw
disks, available for use. Deleted virtual disks are no longer present.

2. Create file system partitions on your disks. When you create a virtual disk in

the controller, you can partition it at the controller level in any way you wish
as long as you create at least one partition per disk. Each of the
controller-level partitions you create becomes a virtual disk, visible to the
host. In Disk Administrator, you must create partitions on these newly added
virtual disks at the Windows NT file system (NTFS) level.

3. After you create partitions on your drives in Windows NT, Windows 2000, or

Windows Server 2003, the file system assigns each drive a unique drive letter.
Make a note of the drive letters assigned.

4. Format your disks. You must format each newly added disk.

5. Start the Agent Configurator by double-clicking its icon in the Command

Console Start Menu group.

6. Navigate through the menus until a popup appears, prompting you to scan

your subsystems. Click Yes to perform the scan and display a list of
subsystems.

7. Make sure that the access device you have been using for your subsystem still

exists. If you inadvertently deleted it, you must assign another device in its
place. If no access device exists, the Client cannot communicate with your
subsystem unless the CCL is used.

Advertising