Top
ETERNUS SF Storage Cruiser 14.0 User's Guide

11.1.5 Operation procedure

Storage Volume Configuration Navigator designs and sets a storage device configuration according to the following steps:


How to perform and define configuration design in advance at Offsite

  1. Starting (offsite)

    Start Storage Volume Configuration Navigator by selecting it from the Start menu or clicking the corresponding desktop icon.

  2. Loading the device configuration

    If the real device configuration has been saved in advance to a file onsite, load the file. In this case, steps 3 "Creating a device unit" and step 4 "Mounting disks" do not need to be performed.

  3. Creating a device unit

    Click the icon of the device, whose configuration is to be designed and set, from the unit stencil to create a device unit on the design window. For more information, see "11.2.6 Creating a device unit (for new designing offsite)".

  4. Mounting disks

    Mount disks according to the real device configuration in the device unit. If a required DE has not been mounted on the location where a disk is to be mounted, mount a DE first. For more information, see "11.2.7 Mounting disks (for new designing offsite)".

  5. Configuring RAIDGroups and LogicalVolumes

    Configure RAIDGroups and LogicalVolumes in the device unit. Using the automatic configuration function can greatly simplify the designing process. See "11.2.8 Executing automatic configuration" for more information on the automatic configuration function. Manual configuration is also possible. In addition, editable RAID levels and LogicalVolumes in the Storage Volume Configuration Navigator are as follows.Unsupported RAID levels and LogicalVolumes are not editable. For details, see "11.1.2 Supported configurations".

    • Supported RAID levels
      RAID1+0, RAID1, RAID6, RAID5+0 and RAID5 are supported.
      However, if an unsupported LogicalVolume (except Snap Data Volume and SDPV) is associated with RAID groups, even a supported RAID level is not editable.

    • Supported LogicalVolumes
      Open Volumes are supported. However, even if it is an Open Volume, a concatenated volume is not supported.

    Follow the procedure below for manual configuration:

    1. Configuring RAIDGroups

      Configure RAIDGroups in the device unit. For details, see "11.2.9 Creating a RAIDgroup (manual creation)".

    2. Allocating LogicalVolumes

      Allocate LogicalVolumes to the RAIDGroups thus configured. For details, see "11.2.12 LogicalVolume creation (manual operation)".

    3. Creating a hot spare disk

      Create a hot spare disk in the device unit. For details, see "11.2.14 Creating a hot spare disk (manual operation)".

  6. Creating AffinityGroups and Allocating LUNs

    Create AffinityGroups within a device unit to allocate LUNs.
    When creating AffinityGroup, LogicalVolumes are required within the device unit.
    For details, see "11.2.15 AffinityGroup operation(manual creation)".

  7. Saving as a file

    Save the configuration whose design is complete as a file. For details, see "11.2.24 Reading and saving a file".

  8. Starting (onsite)

    Start Storage Volume Configuration Navigator by selecting it from the Start menu or clicking the corresponding desktop icon.

  9. Loading the file

    Load the file that was saved in Step 7. For details, see "11.2.24 Reading and saving a file".

  10. Login

    Log in to the operation management server at Onsite with a privileged administrator.

    For details, see "11.2.18 Login".

  11. Entering an IP address

    To specify the real device for which the data of the device configuration created in the device unit is to be defined, enter the IP addresss of the real device in the device unit. For details, see "11.2.19 Entering IP address". Note that this operation is not required if a device configuration was created by loading the real device configuration from the file.

  12. Device matching

    Make sure that the IP address entered in the device unit is correct and define the correspondence between the device unit and the real device on a one-to-one basis. For details, see "11.2.20 Device matching".

  13. Setting the device

    Set the data of the device configuration created in the device unit for the real device. For details, see "11.2.21 Device setup".

  14. Access path setting
    After setting device configuration data to a real device, an access path can be set through the access path management function. For details of access path management, see "6.3 Access Path Management".


How to perform and define configuration design at Onsite

  1. Changing the storage device configuration

    For changing hardware configurations such as adding disks or DE of a storage device, it is required to be executed before read operation of the device configuration.

  2. Starting Storage Volume Configuration Navigator and loading the device configuration

    Select a registered device on the resource view and then select [To Send] - [Storage Volume Configuration Navigator] from the pop-up menu to start. Or, select [File] - [Storage Volume Configuration Navigator] from the menu of the resource view to start, and drag and drop the device icons displayed on the resource view to the design window of the Storage Volume Configuration Navigator to read the device configuration data.

    For details, see "11.2.23 Device loading". In addition, when selecting "Storage Configuration Navigator" from the start menu or desktop icons to start, it is necessary to login with a privileged administrator before drag and drop.

  3. Offsite designing and saving of device configuration data to a file

    If you want to perform configuration design at Offsite based on the current Storage device configuration, save in a file the device configuration displayed on the design window. Start the Storage Volume Configuration Navigator at Offsite to design. For details, see "How to perform and define configuration design in advance at Offsite".

  4. Configuring RAIDGroups and LogicalVolumes

    Configure RAIDGroups and LogicalVolumes in the device unit. Using the automatic configuration function can greatly simplify the designing process. See "11.2.8 Executing automatic configuration" for more information on the automatic configuration function. Manual configuration is also possible. In addition, editable RAID levels and LogicalVolumes in the Storage Volume Navigator are as follows. Unsupported RAID levels and LogicalVolumes are not editable. For details, see "11.1.2 Supported configurations".

    • Supported RAID levels
      RAID1+0, RAID1, RAID6, RAID5+0 and RAID5 are supported.
      However, if an unsupported LogicalVolume (except Snap Data Volume and SDPV) is associated with RAID groups, even a supported RAID level is not editable.

    • Supported LogicalVolumes
      Open Volumes are supported. However, even if it is an Open Volume, a concatenated volume is not supported.

    Follow the procedure below for manual configuration:

    1. Configuring RAIDGroups

      Configure RAIDGroups in the device unit. For details, see "11.2.9 Creating a RAIDgroup (manual creation)".

    2. Allocating LogicalVolumes

      Allocate LogicalVolumes to the RAIDGroups thus configured. For details, see "11.2.12 LogicalVolume creation (manual operation)".

    3. Creating a hot spare disk

      Create a hot spare disk in the device unit. For details, see "11.2.14 Creating a hot spare disk (manual operation)".

  5. Creating AffinityGroups and Allocating LUNs

    Create AffinityGroups within a device unit to allocate LUNs.
    When creating AffinityGroup, LogicalVolumes are required within the device unit.
    For details, see "11.2.15 AffinityGroup operation(manual creation)".

  6. Device matching

    Define the correspondence between the device unit and the real device on a one-to-one basis. For details, see "11.2.20 Device matching".

  7. Setting the device

    Set the data of the device configuration created in the device unit for the real device. For details, see "11.2.21 Device setup".

  8. Access path setting

    After setting device configuration data to the real device, access path can be set with access path management functions. For details of access path management, see "6.3 Access Path Management".