ETERNUS SF Storage Cruiser User's Guide 13.2 - Solaris (TM) Operating System / Linux / Microsoft(R) Windows(R) -

Contents Index

Chapter 11 Storage Volume Configuration Navigator

11.1 Outline

11.1.1 Features

The Storage Volume Configuration Navigator will standardize Storage device's complicated volume configuration methods varied from model to model and relieve administrators of the liability to create volumes through graphical operation windows.

Only specifying the required capacity and numbers of volumes can automatically create LogicalVolumes to the Storage device (Automatic creation of LogicalVolume configuration) without considering any difference in models.

In addition, configurations created through the automatic configuration function can manually be corrected (manual configuration).

Saving a configuration of operational environment in a file makes it possible to correct at Offsite. The configuration corrected at Offsite can be reflected at one time at Onsite.

11.1.2 Automatic creation of LogicalVolume configuration

Based on the specified capacity of a LogicalVolume, number of LogicalVolumes and RAID level, the automatic LogicalVolume configuration creation (hereafter referred to as the automatic configuration function) automatically creates LogicalVolumes and assigns them to a RAIDGroup. It is also possible to specify automatic creation of a RAIDGroup to which LogicalVolumes should be assigned. Using this function thus makes it possible to easily configure a RAIDGroup and LogicalVolumes with excellent serviceability and availability.

The automatic configuration function creates and assigns LogicalVolumes as follows:

1. Checking the hot spare disk capacity and creating a hot spare disk

   To secure sufficient availability, the automatic configuration function checks the hot spare capacity prior to LogicalVolume assignment. If a required hot spare disk does not exist or the capacity is too small, the function automatically configures a hot spare disk.

2. LogicalVolume assignment order

   LogicalVolumes with larger capacities are preferentially assigned to a RAIDGroup. By preferentially allocating LogicalVolumes with larger capacities, a RAIDGroup can be used effectively and efficiently.

   

3. LogicalVolume assignment areas within a RAIDGroup

   When two or more free spaces exist in a RAIDGroup, LogicalVolumes are assigned preferentially beginning from an area with smaller free space. Doing so enables the effective and efficient use of a RAIDGroup.

   

4. RAIDGroup allocation order

   A RAIDGroup is allocated according to LogicalVolume assignment as shown below. The RAIDGroup to be used can also be selected from a list of existing RAIDGroups.

   [Distribution to individual RAIDGroups]

   A RAIDGroup with the smallest allocation to LogicalVolumes is allocated preferentially.

   Distributing LogicalVolumes to RAIDGroups can distribute loads. If two or more RAIDGroups have the same size of LogicalVolume allocation, the one with the smallest RAIDGroup number is allocated preferentially.

   [Order of RAIDGroup numbers]

   RAIDGroups with smaller numbers are allocated preferentially.

5. Configuring a RAIDGroup (only when RAIDGroup configuration permission is given)

   The automatic configuration function configures a RAIDGroup by selecting disks evenly from individual groups to secure availability.

11.1.3 Manual configuration

The configurations of LogicalVolumes and RAIDGroups created by the automatic configuration function are automatically correctable. The following operations are manually available.

1. Create and delete RAID groups, and add and delete disks.

2. Create and delete LogicalVolumes.

3. Create and delete hot spares.

The above operations make it possible to create rough configurations at a time by the automatic configuration function and make correction of details by manual configuration.

11.1.4 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 4, "Mounting disks," does 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.

   • Supported RAID levels
     RAID1+0 and RAID1, RAID5 and RAID6 are supported.
     However, if an unsupported LogicalVolume (Snap Data Volume excluded) 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 a serial number

    To specify the real device for which the data of the device configuration created in the device unit is to be defined, enter the serial number of the real device in the device unit. For details, see "11.2.19 Entering a serial number" 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 serial number 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.

   • Supported RAID levels
     RAID1+0 and RAID1, RAID5 and RAID6 are supported.
     However, if an unsupported LogicalVolume (Snap Data Volume excluded) 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

   Make sure that the serial number 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".

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".

11.2 Menu List and Screen Explanation

The Storage Volume Configuration Navigator window configuration is explained below:

• Menu bar

  Used to give an operation instruction.

• Toolbar

  Displays the icons of frequently used functions so that each function can be started simply by clicking the corresponding icon.

• Unit stencil

  Displays the icons of the devices for which configuration design can be performed. Click the icon of the device for which configuration design is to be started, and the device unit is then displayed on the design window.

• Part stencil

  Displays the icons of the parts that configure the devices displayed on the unit stencil. Clicking a part icon while selecting the device icon on the design window adds the part to the device unit.

• Design window

  Used to perform configuration design.

• Status bar

  Provides examples of status displays on the design window.

11.2.1 Menu bar, toolbar, and pop-up menus

This section explains the operations that can be performed from the menu bar, toolbar, and pop-up menus.

*1 Only a privileged administrator can login.

*2 The user must login as a privileged administrator to execute operation.

11.2.2 Unit stencil

The unit stencil displays the icons of devices for which device configuration data can be newly created.

*1 If a device registered on the resource view is selected and started by selecting [To Send]-[Storage Volume Configuration Navigator] from the popup menu, only the device selected at start-up is operated.

11.2.3 Part stencil

The part stencil displays the icons of the parts that can be added to device units.

11.2.4 Display explanation

The state of each resource on the design window is indicated using color coding.

11.2.5 Starting and exiting

Storage Volume Configuration Navigator can be started using any one of the three methods below:

• Select a device registered on the resource view, and then select [To Send]-[Storage Volume Configuration Navigator] from the pop-up menu (*1).

• Select [File]-[Storage Volume Configuration Navigator] from the resource view.

• Click the icon of Storage Volume Configuration Navigator installed in the client (hereafter referred to as standalone start)

If a device registered on the resource view and started by selecting [To Send] -[Storage Configuration Navigator] from the pop-up menu, a device reading screen is displayed that specifies how to read the specified storage device into the design window. According to the screen, read the device configuration data to work on device configuration design.

Select [File] - [Quit(X)] to exit the Navigator.
In addition, if a device registered on the resource view is selected and started by selecting [To Send]-[Storage Volume Configuration Navigator] from the pop-up menu, the Storage Configuration Navigator will automatically exit by closing the dialog displayed when configuration is not let to read or cannot be read. Also, both when the Storage Volume Configuration Navigator is started from the previous operation and when the Storage Volume Configuration Navigator is started by selecting [File]-[Storage Volume Configuration Navigator] from the menu on the resource view, it will automatically exit by closing the dialog displayed in the same way even when start-up is not enabled.

* 1: If a device registered on the resource view is selected and started by selecting [To Send]-[Storage Volume Configuration Navigator] from the pop-up menu, it is necessary to select the device on the resource view in advance and execute [Register]-[Register SAN devices] from the pop-up menu.

11.2.6 Creating a device unit (for new designing offsite)

To design a new device configuration, first create the device unit to be designed on the design window. To do so, click the target device icon on the unit stencil as shown in the figure below.

When the device icon is clicked, a device creation window appears as shown below:

Enter the necessary information in the window.

1. Select the device model from the dropdown menu of [Model name].
   A model number ending with "*" (example: E320R10*) can be used as a device having the same model number before the "*".
   
   

2. Enter the name of the target device in the [Device name 1] field. The device name entered here is a temporary name used for identification on the design window. Executing the device matching operation replaces the name with the one defined on the administrative server. [Device name 2] is enabled only when a dual configuration model is specified. Enter the name of a device. The specified name is assigned to each of the duplicated devices.

3. Enter a memo in [Memo 1] as necessary. The memo information entered here is a memo on the design window and cannot be referenced on the resource view after a configuration is set for the device. [Memo 2] is enabled only when a dual configuration model is specified. Enter memo information.

4. Click the [OK] button.

The above operations create a device unit on the design window. Continue to perform the disk mount operation and then execute the automatic configuration function to automatically configure a RAIDGroup and LogicalVolumes. A RAIDGroup and LogicalVolumes can also be configured manually.

11.2.7 Mounting disks (for new designing offsite)

This section explains how to add a disk to the device unit and how to delete a disk from the device unit.

If the automatic configuration function is used to automatically configure a RAIDGroup and LogicalVolumes for the device unit that has been newly created, disks must be added in advance by this procedure according to the configuration of the real device.

This is because the automatic configuration function makes a configuration within the range of the disks already mounted. Disks must also be added in advance by this procedure even in cases where a RAIDGroup is to be configured manually.

A disk can also be added to, or deleted from, the real device unit displayed with the device load operation.

When a volume shortage occurs during operation, for instance, a RAIDGroup and LogicalVolumes need to be created. If free disks are required to create them do not exist, the required disks must be added to the real device. To be prepared for this type of situation, the user can use the procedure explained here to add disks to the disk mount positions and then execute the automatic configuration function or configure a RAIDGroup and LogicalVolumes manually. Doing so enables the user to create in advance the device configuration after disk addition without actually adding disks to the real device.

Mount a disk according to the following procedure:

1. While selecting a device unit, select [Design] - [Disk Operation] from the menu bar or select [Disk Operation] from the popup menu to open the disk operation window. The figure below shows how the disk operation window is opened.

   

2. Check whether a DE is already mounted at the position where a disk is to be mounted. If not, mount a DE by following the procedure below. If a DE is already mounted, this operation is not required.

   To delete an existing DE, select the [Select DE] check box, and click the [Delete] button.

   

3. Specify the type of the disk to be mounted. The disk type can be specified either for all disks (All disks) or for individual slots (Set individually).Select either [All disks] or [Set individually] from [Capacity(GB)/Rotation speed(rpm)/Type].When [All disks] is selected, click the down arrow and select the type of the disks to be added. When [Set individually] is selected, select the type of the disk to be added to each disk slot. Disk types are displayed as follows:

   Description on the screen	Disk type name
   FC	Fibre Channel Disk
   FC(N)	Nearline FC Disk
   SAS	SAS Disk
   SATA(N)	Nearline SATA Disk

   
   

   

4. After specifying the disk type, specify the position where the disks are to be mounted. The disk mount position can be specified either for all disk mount positions in a DE or for individual slots. After specifying the disk mount positions, click the [Create] button. The figure below shows how disks are mounted.

   

   To delete a disk, select the disk and click the [Delete] button.

11.2.8 Executing automatic configuration

The automatic configuration function can be used to automatically configure LogicalVolumes. This function automatically allocates a RAIDGroup and LogicalVolumes in an optimum configuration for the device unit. Automatic configuration is enabled for both a device unit created from the unit stencil and a device unit loaded from the real device with the device load function. For either type of device unit, automatic configuration can be performed even after the device configuration is changed by disk operation or RAIDGroup operation. The device configuration created by automatic configuration can also be reconfigured manually.

The following explains how to operate the automatic configuration function.

1. While selecting a device unit, select [Design] - [Auto Configuration(W)] from the menu bar or select [Auto Configuration] from the popup menu to open the disk operation window. The figure below shows how the disk operation window is opened.

   

2. Enter the necessary information on the auto configuration window. The auto configuration window is shown below.

   

   The following explains the meanings of individual parameters and how to use the window.

   1. Define LogicalVolumes

      Enter information on the LogicalVolumes to be created. Specify the capacity of a LogicalVolume for [Capacity(MB)]. Specify the number of LogicalVolumes to be created for [Number of create]. For [RAID Level], select the RAID level of the RAIDGroup to which the LogicalVolumes are to be assigned. After specifying the above parameters, click the [>>] button to move the specified LogicalVolume parameters to [LogicalVolumes to be created]. To delete a LogicalVolume parameter from [LogicalVolumes to be created], select the corresponding field and click the [<<] button.

   2. LogicalVolume Distribution

      Specify how the RAIDGroup and LogicalVolumes are to be configured.

      1. LogicalVolume assignment method

         Select a volume assignment method in [Please specify the usage of a RAIDGroup]. In other words, specify the RAIDGroup to which the LogicalVolumes specified in [Define LogicalVolumes] are to be assigned. Select one of the following two methods:

         [Create a new RAIDGroup]

         No existing RAIDGroups are used but free disks are used to create a RAIDGroup, after which the LogicalVolumes are assigned to the created RAIDGroup.

         [Use an existing RAIDGroup]

         LogicalVolumes are assigned by searching the existing RAIDGroups for free space. Clicking the [Select] button lists existing RAIDGroups. The user can uncheck a certain RAIDGroup to prevent it from being allocated to LogicalVolumes. (*1) If the option "If there is not enough free space create a new RAIDGroup" is selected, a new RAIDGroup is created for allocating LogicalVolumes only when the existing RAIDGroups run short of free space.

         *1: RAID groups that cannot be edited with Storage Volume Configuration Navigator are not displayed (for more information, see "11.1.4 Operation procedure").

      2. LogicalVolume assignment method

         Select one of the options under [Distribution]

         When [Distribute volumes evenly across RAIDGroups] is selected, LogicalVolumes are assigned to target RAIDGroups as evenly as possible.

         When [Assign volumes to the lowest available RAIDGroup number] is selected, LogicalVolumes are assigned in order of RAIDGroup numbers.

3. After entering all necessary parameters, click the [Execute] button.

   This completes the procedure for automatically allocating LogicalVolumes.

11.2.9 Creating a RAIDgroup (manual creation)

Select a device unit and click a RAIDGroup icon on the part stencil to open the RAIDGroup operation window. Alternatively, select a device unit and select [Design] - [RAIDGroup Operation] from the menu bar or select [RAIDGroup Operation] from the popup menu to open the RAID group operation window. The RAIDGroup operation window is shown below.

In the RAID group operation window displayed, create a RAID group as follows:

1. Select the RAID level of the RAIDGroup to be created. Select the RAID level from [RAID Level / Hot Spare]. If [Hot Spare] is selected here, a hot spare disk can be created.

2. Select the disks to be used. Clicking the button representing a disk puts the disk in the selected state, and clicking the button again deselects the disk.

3. After selecting all necessary disks, click the <Make> button.

This completes the procedure for creating the specified RAIDGroup or hot spare disk.

11.2.10 Adding disks to a RAIDgroup (manual operation)

To add a disk to a RAIDGroup, select the target RAIDGroup on the design window and select [Design] - [RAIDGroup Operation] from the menu bar or select [RAIDGroup Operation] from the popup menu. The RAIDGroup operation window is shown below.

The RAIDGroup operation window opens with the activated RAIDGroup displayed in the selected state. Add a disk to the RAIDGroup as follows:

1. Select the disk to be added to the RAIDGroup.

2. Click the [Add Disk] button.

This completes the procedure for adding the specified disk to the RAIDGroup.

11.2.11 Deleting a RAIDGroup (manual operation)

To delete a RAIDGroup, select the RAIDGroup to be deleted from the design window and select [Design] - [Delete] from the menu bar or select [Delete] from the popup menu. Gray LogicalVolumes cannot be deleted.

11.2.12 LogicalVolume creation (manual operation)

Select the RAIDGroup in which a LogicalVolume is to be created, and select [Design] - [Make LogicalVolume] or select [Make LogicalVolume] from the popup menu to open the LogicalVolume creation window.

The LogicalVolume creation window is shown below:

Create a LogicalVolume using the LogicalVolume creation window as follows:

1. From the RAIDGroup tree, select the free space to be allocated to a new LogicalVolume.

2. Select one of the following three methods of LogicalVolume creation:

   1. [Specify capacity and number]

      Specify the capacity of a LogicalVolume for [Capacity(MB)] and the number of LogicalVolumes for [Number to create].

   2. [Divide free space between volumes]

      The LogicalVolume capacity is allocated evenly according to the number specified for [Number to create] in the specified free space areas.

   3. [Specify details for each volume]

      The capacity of the LogicalVolumes to be allocated is entered only once to create LogicalVolumes.

3. After entering all necessary parameters for creating LogicalVolumes, click the [Add] button.

   This completes the procedure for assigning LogicalVolumes to the specified RAIDGroup.

11.2.13 Deleting a LogicalVolume (manual operation)

To delete a LogicalVolume, select the LogicalVolume to be deleted from the design window and select [Design] - [Delete] from the menu bar or select [Delete] from the popup menu. Gray LogicalVolumes cannot be deleted. The figure below shows how a LogicalVolume is deleted.

11.2.14 Creating a hot spare disk (manual operation)

While selecting a device unit, click the Hot Spare icon on the part stencil to open the hot spare disk operation window. The hot spare disk operation window is shown below.

Create a hot spare disk using the hot spare disk operation window as follows:

1. Select the disks to be used. Clicking the button representing a disk puts the disk in the selected state, and clicking the button again deselects the disk.

2. After selecting all necessary disks, click the [Make] button.

This completes the procedure for creating a hot spare disk. A hot spare disk can also be created using the RAIDGroup operation window.

11.2.15 AffinityGroup operation(manual creation)

Select a device unit and then select [Design] - [AffinityGroup Operation] from the menu or [AffinityGroup Operation] from the pop-up menu to start the AffinityGroup operation window.The AffinityGroup operation window is shown below.AffinityGroup cannot be operated by ETERNUS3000, ETERNUS6000, ETERNUS4000 Model 80 and Model 100.

Setting AffinityGroup in the Storage will allow it to set an access path by access path management functions. For access path management, see "6.3 Access Path Management"

The following are descriptions of the configuration of the AffinityGroup operation window.

1. LogicalVolume view

   A LogicalVolume view is displayed that is configured in the device unit selected at start-up of the Affinity operation window

   1. RAIDGroup number

      RAIDGroup numbers are displayed. RAIDGroups to which LogicalVolumes are not allocated are not displayed

   2. LogicalVolume numbers

      A LogicalVolume numbers is displayed by RAIDGroup.
      To a LogicalVolume to which LUN concatenation is executed is displayed [(Serial number/LogicalVolume concatenated total number)], following the LogicalVolume number.

      e.g.: If 0x0008(1/2) is displayed, a LogicalVolume Number is 0x0008, a serial number is 1 and a LogicalVolume concatenated total number is 2.

   3. LogicalVolume capacity

      The capacity of LogicalVolume is displayed. The unit is MB.

      Depending on the allocation to AffinityGroups, font colors vary as follows.

      Font color	Meaning
      Black	Allocated
      Blue	Unallocated
      Orange	Allocated to multiple AffinityGroups or to LUNMapping. (shared with LogicalVolume)

      A LogicalVolume to which LUN concatenation is executed is shown in [relevant amount/totoal amount].

2. AffinityGroup view

   The views of AffinityGroups and LUNMappings are displayed that are configured in the device unit selected at start-up of the AffinityGroup operation window.

   1. AffinityGroup number

      AffinityGroup numbers are displayed in decimal. If AffinityGroups are concatenated, all the numbers of concatenated AffinityGroups are displayed set off with commas.

      For LUNMappings, port names are displayed.

   2. AffinityGroup name

      Aliases of AffinityGroups and LUNMappings are displayed.

   3. LUN number

      A LUN number allocated to the LogicalVolume in a LogicalVolume view in the same row is displayed in decimal by AffinityGroup and by LUNMapping.

      The cell color changes as follows depending on the relevant LogicalVolume state.

      Cell color	Meaning
      White	LUN number is editable. Also, a relevant LogicalVolume is not allocated to multiple AffinityGroups or LUNMappings (Multiple LUN numbers are not allocated).
      Yellow	LUN number is editable. Also, a relevant LogicalVolume is allocated to multiple AffinityGroups or LUNMappings (Multiple LUN numbers are Allocated).
      Gray	LUN number is not editable. If a LUN number falls under the following, it is not editable. LogicalVolume of a type that is not supported by the Storage Volume Configuration Navigator. LUNMapping Concatenated AffinityGroup

The following are descriptions of operation procedures of the AffinityGroup operation window.

[AffinityGroup addition]

1. Press the <AffinityGroup addition> button on the AffinityGroup operation window.

2. Then, the AffinityGroup add dialog is displayed. Enter a group number and a group name. Group names are optional.

3. Press the <OK> button.

• Once the maximum number of AffinityGroups has been created no more can be added.

[Allocating LUN and changing LUN number]

1. If you want to allocate a LUN (or change a LUN number), focus on a cell at which a row of LogicalVolume and a column of AfiinityGroup are intersected.

2. Enter the LUN number you want to allocate.

[Automatic allocation of LUN]

1. Select multiple cells to which you want to allocate LUNs and at which multiple rows of LogicalVolume and multiple columns of AffinityGroup are intersected.

2. Select [Automatic allocation] from the pop-up menu displayed by right click of mouse.

For automatic allocation of LUN, LUN numbers are allocated in ascending order from the smallest LUN number that is not allocated in the relevant AffinityGroup.

[Unallocating LUN]

1. Focus on a cell to which you want to unallocated a LUN and at which a row of LogicalVolume and a column of AffinityGroup are instersected.

2. Press the delete key or the backspace key.

You cannot create any AffinityGroup without LUN.

[Unallocating multiple LUNs]

1. Drag multiple cells to which you want to unallocated LUNs and at which multiple rows of LogicalVolume and multiple columns of AffinityGroup are intersected.

2. Select [Unallocation] from the pop-up menu displayed by right click of mouse.

You cannot create any AffinityGroup without LUN.

[Changing AffinityGroup number and AffinityGroup name]

1. Press the <AffinityGroup edit> button with an AffinityGroup number or an AffinityGroup name you want to change selected. Or, select [AffinityGroup edit] from the pop-up menu.

2. Then the AffinityGroup change dialog is displayed. Enter a desired group number and a desired group name.

3. Press the <OK> button.

In the following case, AffinityGroup number is not changeable.

• AffinityGroup to which a host affinity is set.

In the following cases, AffinityGroup numbers and AffinityGroup names are not changeable.

• AffinityGroup to which a LogicalVolume is allocated that is allocated to an unsupported RAIDGroup.

• AffinityGroup to which an unsupported LogicalVolume is allocated.

• Concatenated AffinityGroup.

• LUNMapping

[Deleting AffinityGroup]

1. Press the <AffinityGroup deletion> button with an AffinityGroup number or an AffinityGroup name you want to delete selected. Or select [AffinityGroup deletion] from the pop-up menu.

2. Then the confirmation dialog to delete AffinityGroup is displayed. If it is all right, press the <OK> button.

In the following cases, AffinityGroups cannot be deleted.

• AffinityGroup to which a LogicalVolume that is allocated to an unsupported RAIDGroup is allocated.

• AffinityGroup to which an unsupported LogicalVolume is allocated.

• Concatenated AffinityGroup

• AffinityGroup to which a host affinity is set.

• LUNMapping

[Reflecting to the design window]

If you want to reflect created or corrected contents to the design window, press the <Execution> button.
Whenever the <Execution> button is pressed on the design window after the AffinityGroup operation window exits, the Return/Redo commands are executable.

[Exiting the operation window]

To exit the AffinityGroup operation window, press the <End> button. If the <End> button is pressed before the <Execution> button, created or corrected contents are not reflected to the design window but the window exits.

11.2.16 Copy Device

This function allows you to efficiently create a device configuration containing similar device units. First create an original device unit, use Copy Device to copy as many device units as desired, and then edit the devices (*1). Copy Device can be operated as shown below.

1. Selecting an original device unit of which you want to make a copy, select "Copy Device" from the menu bar and pop-up menu. The following Copy Device window then appears.

   

2. Enter the name you want to assign to a copied device unit in the [Name] text box. This is a temporary name used for identifying the device on the design window. The device matching operation renames the temporary names as device names specified in the operation management server.

3. Write any necessary information in the [Memo] text box. This memo information is only valid on the design window. You cannot browse this information on the resource view after configuring the devices.

4. Click [OK].

With these operations, the copied device unit is now created on the design window. Now you can edit the configuration.

*1 If a device registered on the resource view is selected and started by selecting [To Send]-[Storage Volume Configuration Navigator] from the pop-up menu, only the device selected at start-up is operable.

11.2.17 Displaying disk assignment information

Storage Volume Configuration Navigator can display how disks are currently assigned to a device unit. Select a device unit, and select [Information] - [Disk Map] from the menu bar or select [Disk Map] from the popup menu to open the disk map window. The disk map window is shown below.

11.2.18 Login

When Storage Volume Configuration Navigator is started in standalone mode, the user must login to the operation management server before reading the real device configuration, device matching, and device setting. Select [Design] - [Log in] from the menu bar to open the login window. The login window is shown below.

1. For [Administrative server], enter the address of the administrative server.

2. For [User name], enter the user name with administrator authority.

3. For [Password], enter the password.

4. Click [OK] to login.

If a device registered to the resource view is selected and started by selecting [To Send]-[Storage Volume Configuration Navigator] from the pop-up menu, or started by selecting [File]-[Storage Volume Configuration Navigator] from the menu on the resource view, login operation is not required.

11.2.19 Entering a serial number

The serial number of the real device must be specified as information required to associate the device unit created virtually with the real device. The device matching operation explained later searches for the real device that matches the serial number entered here, and maps the device unit to the detected real device.

To open the serial number entry window, select a device unit, and select [Design] - [Input Serial Number] from the menu bar or select [Input Serial Number] from the popup menu. The serial number entry window is shown below.

Make sure that the serial number to be entered matches that appearing on the label affixed to the real device. If the serial number of a real device differing from that of the target real device is entered, the device configuration will be destroyed and system operation will be very adversely affected.

Enter a serial number as follows:

1. Select a virtual device unit displayed on the design window.

2. Select [Input Serial Number] from the menu.

3. Enter a serial number.

4. Click [OK].

11.2.20 Device matching

The device matching operation checks or specifies the real device to which the settings of the device unit displayed in the edit window should be applied. For a device unit that has been created virtually, execute this operation after entering a serial number. If designing is performed offsite, login as a privileged administrator to the operation management server before executing this operation.

To open the device matching window, select the device unit to be matched, and select [Design] - [Device Matching(R)] from the menu bar or select [Device Matching] from the popup menu. The device matching window is shown below.

The device matching window displays information on the real device with a serial number that matches the one defined for the device unit selected on the design window. Check the IP address, serial number, and BOX ID displayed to make sure that the device is the right one for which the configuration setting is to be performed.

If a device different from the real target device is selected, the device configuration will be destroyed and system operation will be very adversely affected.

The operation procedure is explained below:

1. From the list of real devices, select the target device to verify the device matching.

2. Click [OK] to validate the device matching.

If the device name entered in the device unit creation window differs from that of the real device during device matching, a message indicating that the device name of the real device is to be replaced appears. Similarly, when you select a model number ending with an "*" in the device unit creation window, a message indicating that the product name of the real device is to be replaced also appears. Click the <OK> button.

11.2.21 Device setup

The device setup operation applies the device configuration of the device unit created on the design window to the real device associated with the device matching operation. To open the device setup window, select [Design] - [Device Setup] from the menu bar, or select the device setup icon from the toolbar. If designing is performed offsite, login as a privileged administrator to the operation management server before executing this operation. The device setup window is shown below.

The operation procedure is explained below:

1. The device configuration is applied sequentially to real devices from the upper to lower of the list. Use the [Move up] and [Move down] button to adjust the order of application. A device that need not be set up can be deleted using the [Delete] button.

2. Click [OK] to start device setup.

Before starting device setup, be sure to check the following to verify that there are no problems. Failure to do so may cause serious problems.

• Depending on the contents of the device configuration, executing device setup deletes a RAIDGroup or LogicalVolume together with the data retained in it. Make sure in advance that the reconfiguration will not cause any problems.

• Make sure in advance that the real device to which device configuration data is to be applied is correct. If an incorrect real device is selected for application of device configuration data, the data retained in the real device may be completely destroyed.

• When [New] is specified for the process type in the configuration load dialog box, the device configuration is once initialized. Therefore, all data is deleted. Make sure in advance that no problems occur if all data is deleted. "New" is displayed in red for a device for which new setup is to be performed.

After device setup is finished, the device setup result window appears. The data displayed in the device setup result window is as follows:

+Device setup result list

The device setup result is displayed for each device. The message displayed at [Setup result] is as follows:

11.2.22 General verification

The general verification function checks the configuration of the device unit displayed on the design window for problems.

To start general verification, select [General verification] from the menu or click the general verification icon on the toolbar.

The table below provides a summary of what items are checked and what messages are output as the result of checking. Note that device setup is possible even if a warning message with a message number of the type 4xxxxx has been displayed.

11.2.23 Device loading

The device configuration of a storage device is readable from the resource view. When starting up a single device, log in to the operation management server with a privileged administrator before operation.

The operation procedure is explained below:

1. Select one of the following modes from [Processing mode]:

   1. [Updating]

      When configuration data is set in the device, only the updated portions of the data are set in the device.

   2. [New]

      The device configuration data edited based on the device configuration that has been loaded is set in the real device after the real device configuration data is initialized. When newly executing device setup, make sure in advance that no LogicalVolumes exist in the real device.

2. Select one of the following methods from [The reading method]:

   1. [Only object device is read]

      Only the device configuration of the specified storage device is loaded.

   2. [Related device is also read]

      Configuration data for switches and hosts related to the specified storage device is also read.

3. Click the [OK] button.

A storage device in one of the following states cannot be loaded:

• Storage device whose device status is other than normal or warning

• Storage device using a hot spare disk, which means a storage device in one of the following states:

  • A RAIDGroup is using the hot spare disk.

  • The storage device is being copied back.

  • The storage device is being rebuilt.

• Storage device within which a LogicalVolume of LUN concatenation is being created.

11.2.24 Reading and saving a file

Device configuration data created on the design window can be saved by selecting [File]-[Save As] from the menu bar. The device configuration data thus saved can be read by selecting [File]-[Open] from the menu bar. (*1)

*1 If a device registered on the resource view is selected and started by selecting [To Send]-[Storage Volume Configuration Navigator] from the pop-up menu, only the device configuration data is allowed to save.

11.3 Messages

11.3.1 Information messages

22520: Could not connect to administrative server.

Explanation

The operation was attempted while the user was not logged in to the operation management server.

Response

Login to the operation management server and then reexecute the operation.

22521: Account information incorrect.

Explanation

The authentication information does not match that in the window in which the device to be loaded was specified.

Response

Match the authentication information, and reload the device.

22522: The device reading to Storage Volume Configuration Navigator that selects the device and was started cannot be operated.

Explanation

If a device registered on the resource view is selected and started by selecting [To Send]-[Storage Volume Configuration Navigator] from the pop-up menu, reading to the device is allowed by drag and drop.

Response

Perform the device load operation after starting Storage Volume Configuration Navigator by selecting it from the Start menu or by clicking the corresponding desktop icon, or start the storage device by selecting [File] - [Storage Volume Configuration Navigator] from the resource view.

22523: Error authenticating account. Check username and password.

Explanation

Authentication failed with the entered account information.

Response

Check the user information and password, and then retry the operation.

22526: Only privileged administrators can perform this operation.

Explanation

The specified account information does not indicate a privileged administrator.

Response

Make sure that the account information is of a privileged administrator, and then retry the operation.

22527: xxx is not found on the network. Check specified administrative server is valid.

Explanation

The specified operation management server name is not found in the network.

Response

Check the operation management server name, and then retry the operation.

22529: Specify logical volume information.

Explanation

Automatic configuration was executed without entering LogicalVolume information in the auto configuration window.

Response

Enter LogicalVolume information and then execute auto configuration.

22530: Invalid logical volume capacity.

Explanation

An invalid value was specified for the LogicalVolume capacity in the auto configuration window.

Response

Specify a valid value for the LogicalVolume capacity of the LogicalVolume information.

22531: Invalid number of logical volumes.

Explanation

An invalid value was specified for the number of LogicalVolumes in the auto configuration window.

Response

Specify a valid value for the number of LogicalVolumes of LogicalVolume information.

22532: Logical volume could not be assigned to this composition.

Explanation

The number of disks is insufficient for creating RAIDGroups to which the specified LogicalVolumes can be assigned.

Response

Add disks to the device.
For a real device, add disks to the real device, execute device loading, and then perform automatic configuration again.

22533: Disk not installed in specified device.

Explanation

No disks are mounted on the device for which automatic configuration is to be performed.

Response

Mount disks on the device.
For a real device, mount disks on the real device, execute device loading, and then perform automatic configuration again.

22534: Logical volume capacity exceeds the maximum capacity.

Explanation

The specified capacity of LogicalVolumes exceeds the maximum LogicalVolume capacity that can be assigned to the device.

Response

Specify a smaller value for the LogicalVolume capacity.

22535: The number of logical volumes exceeds the maximum that can be assigned to this device.

Explanation

The sum of the specified number of LogicalVolumes and the number of existing LogicalVolumes exceeds the maximum number that can be assigned to the device.

Response

Reduce the number of LogicalVolumes to be created.

22536: DE not installed.

Explanation

No DE is mounted on the device. Automatic configuration cannot be executed for a device without a DE.

Response

Mount DEs on the device.
For a real device, modify the real device configuration, execute device loading, and then perform automatic configuration again.

22537: DE composition invalid.

Explanation

The configuration of the DEs mounted on the device contains an error.

Response

Check and correct the DE configuration of the device.
For a real device, correct the real device configuration, execute device loading, and then perform automatic configuration again.

22538: Install disk between slot 0 and 3 in DE0x00.

Explanation

Disks must always be mounted as backup disks in DE0x00 Slot0 to Slot3.

Response

Perform disk operation to mount disks in DE0x00 Slot0 to Slot3.
For a real device, modify the real device configuration, execute device loading, and then perform automatic configuration again.

22539: Install disk between slot 0 and 1 in the DE.

Explanation

Disks are not mounted in DE0x10 or expansion DE Slot0 and Slot1.

Response

Perform disk operation to mount disks in DE0x10 or expansion DE Slot0 and Slot1.
For a real device, modify the real device configuration, execute device loading, and then perform automatic configuration again.

22540: Could not find hot spare disk with sufficient capacity.

Explanation

A hot spare disk could not be secured because any disk has a free space exceeding the largest disk capacity, from among the disks already allocated to the RAIDGroup.

Response

Perform disk operation to mount a disk having a free space exceeding the largest disk capacity among the disks already allocated to the RAIDGroup.
For a real device, modify the real device configuration, execute device loading, and then perform automatic configuration again.

22541: RAID group capacity is insufficient.

Explanation

The current capacity of the existing RAIDGroups is insufficient for assigning the specified LogicalVolumes.

Response

Perform RAIDGroup operation to create a RAIDGroup and then execute automatic configuration. Alternatively, execute automatic configuration by specifying that a new RAIDGroup be created.

22543: Install the two data disks in the first slots of the DE.

Explanation

Data disks must be mounted in the first two slots of each DE.

Response

Perform disk operation to mount data disks in the first two slots of each DE. System disks are not included.
For a real device, modify the real device configuration, execute device loading, and then perform automatic configuration again.

22555: The number of logical volumes exceeds the maximum that can be assigned per RAID group.

Explanation

The number of LogicalVolumes exceeds the maximum number of LogicalVolumes that can be assigned to a RAIDGroup.

Response

Reduce the number of LogicalVolumes to a number that can be assigned to a RAIDGroup.

22556: Selected disk cannot be used as a hot spare disk.

Explanation

Disks used as backup disks and system disks cannot be used for hot spare disks.

Response

Specify disks other than backup disks and system disks as hot spare disks.

22557: The capacity of the selected disk is insufficient for use as a hot spare disk.

Explanation

The specified disk cannot be defined as a hot spare disk because its capacity is too small.

Response

For the ETERNUS3000, specify the disk having the largest capacity, from among those mounted on the device.
For the ETERNUS6000, ETERNUS4000 and ETERNUS8000, specify a disk of the same Loop and of the maximum capacity.

22558: Selected composition invalid. Add the disk to a different loop on the same DA.

Explanation

For a RAID5 configuration of the ETERNUS6000, disks must be selected on the same DA.

Response

Select disks on the same DA. For information about the DA configuration, refer to the ETERNUS6000 SA/SE Handbook.

22559: Device name required.

Explanation

A required device name has not been specified.

Response

Specify a device name.

22560: Specified device name already in use.

Explanation

An existing device has the same name.

Response

Specify a unique name.

22563: RAID group capacity insufficient.

Explanation

The RAIDGroup does not have sufficient free space for creating the specified LogicalVolumes.

Response

Reduce the LogicalVolume capacity.

22564: Maximum number of RAID groups already exist.

Explanation

An attempt was made to create more RAIDGroups than permitted in the device.

Response

Create RAIDGroups within a range not exceeding the maximum number permitted in the device.

22565: Contains unsupported disks.

Explanation

An unsupported disk is mounted on the real device.

Response

Remove the unsupported disk from the real device, and then reload the device.

22566: Disks must be equally distributed across loops.

Explanation

The disks configuring of a RAIDGroup are not allocated evenly between loops.

Response

Select the disks configuring a RAIDGroup again so that they are allocated evenly.

22567: The specified number of logical volumes cannot be created.

Explanation

The RAIDGroup does not have sufficient free space for creating as many LogicalVolumes as specified.

Response

Create LogicalVolumes in a RAIDGroup that has sufficient free space.

22568: RAID1+0 requires an even number of disks to be assigned to the group.

Explanation

An odd number of disks were specified although a RAIDGroup with RAID level RAID1+0 must be created with an even number of disks.

Response

Specify an even number of disks to create a RAIDGroup, or add disks so that the total number of disks making up a RAIDGroup is an even number.

22569: Selected disk composition not recommended.The recommended composition is 4 per loop ID:0 and 4 per loop ID:1. Continue anyway?

Explanation

The selected disks do not meet a configuration recommended for a RAIDGroup. In consideration of performance and reliability, mount four disks each in Loop ID 0 and Loop ID 1.

Response

Mount four disks each in Loop ID 0 and Loop ID 1. Note that this configuration is not always required.

22570: Selected disk composition not recommended.Recommended composition is 8 or less per loop ID:0 and loop ID:1 respectively. Continue anyway?

Explanation

The selected disks do not meet a configuration recommended for a RAIDGroup. Eight or more disks are selected for each loop. In consideration of performance and reliability for this device, assign eight or fewer disks each to Loop ID 0 and Loop ID 1.

Response

Assign eight or fewer disks each to Loop ID 0 and Loop ID 1. Note that this configuration is not always required.

22571: The specified number of disks is not recommended. Recommended composition is 8.Selecting disks from different loops will enhance performance and reliability. Continue anyway?

Explanation

The selected disks do not meet a configuration recommended for a RAIDGroup. In consideration of performance and reliability, mount four disks each in Loop ID 0 and Loop ID 1.

Response

Mount four disks each in Loop ID 0 and Loop ID 1. Note that this configuration is not always required.

22572: The specified number of disks is not recommended. Recommended composition is 16.Selecting disks from different loops will enhance performance and reliability. Continue anyway?

Explanation

The selected disks do not meet a configuration recommended for a RAIDGroup. In consideration of performance and reliability, allocate 16 or fewer disks evenly in each loop.

Response

Allocate 16 or fewer disks evenly in each loop. Note that this configuration is not always required.

22573: The specified number of disks is not recommended. Recommended composition is 5. Continue anyway?

Explanation

The selected disks do not meet a configuration recommended for a RAIDGroup. It is recommended to allocate five disks.

Response

Allocate five disks evenly in each loop. Note that this configuration is not always required.

22574: The specified number of logical volumes could not be created because this will cause the total number to exceed the maximum allowable for the device.

Explanation

The specified number of LogicalVolumes to be created causes the total number to exceed the maximum allowable number for the device.

Response

Change the number of LogicalVolumes to be created so that the total number does not exceed the maximum allowable number, and then retry the operation.

22575: The specified number of disks is not recommended. Recommended composition is 5.Distribute disks evenly across loop ID:0 and loop ID:1 to enhance performance and reliability. Continue anyway?

Explanation

The selected disks do not meet a configuration recommended for a RAIDGroup. For RAID5, the recommended configuration consists of five disks, and disks are allocated evenly to loops.

Response

Select five disks for configuring a RAIDGroup in such a way that the disks are allocated evenly to individual loops. Note that this configuration is not always required.

22576: Specify the number of logical volumes to create.

Explanation

The number of LogicalVolumes to be created is not specified.

Response

Specify the number of LogicalVolumes and then retry the operation.

22577: Specify the logical volume capacity.

Explanation

The LogicalVolume capacity is not specified.

Response

Specify the LogicalVolume capacity and then retry the operation.

22578: The specified number of disks is not recommended. Recommended composition is 10. Continue anyway?

Explanation

The number of selected disks does not meet a configuration recommended for a RAIDGroup. The recommended number of disks is 10.

Response

Select 10 disks. Note that this configuration is not always required.

22579: Selected disk composition not recommended. It's also recommended to use disks of the same capacity. Continue anyway?

Explanation

The capacities of the selected disks are uneven. When the capacities of the disks making up a RAIDGroup are uneven, a RAIDGroup is configured based on the value of the disk with the smallest capacity. Disks with larger capacities cannot be used effectively.

Response

Configure a RAIDGroup with disks having the same capacities. Note that this configuration is not always required. Refer to the SA/SE Handbook for details.

22580: Selected disk composition not recommended. It's also recommended to use disks of the same speed. Continue anyway?

Explanation

The numbers of rotations of the selected disks are uneven. In this case, a RAIDGroup is configured based on the value of the disk with the smallest number of rotations and this may lead to a performance-related problem. Note that this is not checked if the configuration of a real device has been read from a file.

Response

Configure a RAIDGroup with disks having the same numbers of rotations. Note that this configuration is not always required. Refer to the SA/SE Handbook for details.

22581: Selected disk composition not recommended. It's also recommended to use disks of the same capacity and speed. Continue anyway?

Explanation

The capacities and the numbers of rotations of the selected disks are uneven. If the numbers of rotations making up a RAIDGroup are uneven, a RAIDGroup is configured based on the value of the disk having the smallest number of rotations and a problem may occur in performance. If the capacities are uneven, a RAIDGroup is configured based on the value of the disk with the smallest capacity and disks with larger capacities cannot be used effectively.

Note that this matter is not checked if the configuration of a real device is read from a file.

Response

Configure a RAIDGroup with disks having the same capacities and rotations. Note that this configuration is not always required. Refer to the SA/SE Handbook for details.

22582: Selected disk composition not recommended. To enhance performance and reliability, distribute disks evenly across loop ID:0 and loop ID:1. Continue anyway?

Explanation

The selected disks are not allocated evenly in each loop. Taking performance and reliability into consideration, allocate the disks as evenly as possible.

Response

Select disks again so that the disks are allocated evenly in each loop. Note that this configuration is not always required. Refer to the SA/SE Handbook for details.

22583: The RAID group cannot be created unless the DA has a redundant configuration.

Explanation

Since the selected disks within the DA are both located on the same path, both disks become unusable in case of a failure in the path.

Response

When using disks in the same DA (when the LoopID numbers are displayed in the same color), select disks that are located on different paths. (Select one disk having an even LoopID number and the other having an odd LoopID number.)

22584: The specified number of disks is not recommended. Recommended composition is 8. Continue anyway?

Explanation

The selected number of disks does not meet a recommended configuration. Eight disks are recommended.

Response

Select eight disks and reconfigure the RAIDGroup. Note that this configuration is not always required. Refer to the SA/SE Handbook for details.

22585: The selected composition cannot be created. Assign the disk to a different loop.

Explanation

For the ETERNUS6000, disks in the same loop cannot be selected to configure RAID1+0.

Response

Select disks from different loops and retry the operation. Refer to the SA/SE Handbook for details.

22586: RAID5 requires that disks be distributed evenly across loops.

Explanation

Deletion failed because deleting disks making up a RAIDGroup results in an unbalanced number of disks in each loop.

Response

Perform deletion so that the numbers of disks in individual loops are equal.

22587: The number of disks assigned to one loop must not exceed half of all disks making up a RAID group.

Explanation

A half or more of the disks configuring a RAIDGroup are specified in one loop. The number of disks assigned to one loop must not exceed half of all disks making up a RAIDGroup.

Response

Specify disks so that the number of disks assigned to one loop is less than half of all disks.

22588: Cannot change the composition of the RAID group that contains logical volumes.

Explanation

A RAIDGroup containing a LogicalVolume cannot be reconfigured.

Response

Delete the LogicalVolumes and then reconfigure the RAIDGroup.

22589: Selected disk composition not recommended. Selecting disks from a different loop will enhance performance and reliability.

Explanation

The selected disks are not allocated as recommended between loops. Distribute disks evenly to loops from the points of view of performance and reliability.

Response

Allocate disks again so that they are distributed evenly to loops. Note that this configuration is not always required.

22590: Hot spare disk with insufficient capacity found on loop ID:0 and loop ID:1.

Explanation

Recovery from a disk error will not be possible because the capacity of the disk configuring the RAIDGroup exceeds that of the existing hot spare disk.

Response

Assign to a hot spare disk, the disk having a capacity exceeding that of any disk configuring the RAIDGroup.

22591: Hot spare disk with insufficient capacity found on loop ID:0.

Explanation

Recovery from a disk error will not be possible because the capacity of the disk in Loop ID 0 configuring the RAIDGroup exceeds that of the existing hot spare disk.

Response

Assign to a hot spare disk in Loop ID 0, the disk having a capacity exceeding that of any disk in Loop ID 0 configuring the RAIDGroup.

22592: Hot spare disk with insufficient capacity found on loop ID:1.

Explanation

Recovery from a disk error will not be possible because the capacity of the disk in Loop ID 1 configuring the RAIDGroup exceeds that of the existing hot spare disk.

Response

Assign to a hot spare disk in Loop ID 1, the disk having a capacity exceeding that of any disk in Loop ID 1 configuring the RAIDGroup.

22593: A hot spare disk with insufficient capacity was found in the following loops:

Explanation

Recovery from a disk error will not be possible because the capacity of the disk configuring the RAIDGroup exceeds that of the existing hot spare disk.

Response

Assign to a hot spare disk, the disk having a capacity exceeding that of any disk configuring the RAIDGroup.

22594: RAID1+0 requires an even number of disks on each loop. Delete a disk.

Explanation

When deleting disks configuring a RAIDGroup in the RAID level RAID1+0, delete them so that each loop has the same number of remaining disks.

Response

Perform deletion again so that each loop has the same number of remaining disks.

22595: Delete a disk to ensure even number, as required for RAID1+0 RAID groups.

Explanation

The number of disks configuring a RAIDGroup in the RAID level RAID1+0 must be an even number.

Response

Perform deletion again so that the number of remaining disks configuring the RAIDGroup becomes an even number.

22596: Cannot delete disk because that would put the number of disks below the minimum required by RAID1+0.

Explanation

Deletion failed because the number of disks configuring a RAIDGroup in the RAID level RAID1+0 will be less than the number required for the minimum allowable configuration.

Response

Perform deletion again so that the number of remaining disks does not become smaller than that required for the minimum allowable configuration. For details of the number of disks, refer to the SA/SE Handbook for the respective device.

22597: Cannot delete disk because that would put the number of disks below the minimum required by RAID5.

Explanation

Deletion failed because the number of disks configuring a RAIDGroup in the RAID level RAID5 will be less than the number required for the minimum allowable configuration.

Response

Perform deletion again so that the number of remaining disks does not become smaller than that required for the minimum allowable configuration. For details of the number of disks, refer to the SA/SE Handbook for the respective device.

22598: Cannot delete one of the logical volumes.

Explanation

A LogicalVolume used by the server cannot be deleted.

Response

Release the LogicalVolume from the server and then delete the LogicalVolume.

22599: Cannot delete one of the RAID groups.

Explanation

The RAIDGroup cannot be deleted because it contains a LogicalVolume that cannot be deleted. Alternatively, the RAIDGroup cannot be deleted because it is not supported.

Response

An attempt was made to delete the RAIDGroup containing a LogicalVolume being used. Check the system configuration.

22600: RAID group maximum capacity exceeded.

Explanation

Using the selected disks exceeds the maximum capacity allowed for a RAIDGroup.

Response

Reduce the number of selected disks or select disks with smaller capacities to configure a RAIDGroup.

22601: Selected disk composition not recommended. Use the highest speed disks in the loop as hot spares. Continue anyway?

Explanation

The selected disks do not meet a recommended configuration. Selecting a disk featuring the fastest rotation speed in the loop as a hot spare disk prevents degradation of performance when the hot spare disk is incorporated into the RAIDGroup.

Response

Select the disk featuring the fastest rotation speed in the loop and then retry the operation.

22602: Different size disks cannot be used to create a RAID group.

Explanation

The capacities of the disks making up a RAIDGroup are not the same.
(ETERNUS6000)

Response

Select disks making up a RAIDGroup again in such a way that the capacities of individual disks are the same.

22603: Different speed disks cannot be used to create a RAID group.

Explanation

The numbers of rotations of the disks making up a RAIDGroup are not the same.
(ETERNUS6000)

Response

Select disks making up a RAIDGroup again in such a way that the numbers of rotations of individual disks are the same.

22604: Disks of different size and speed cannot be used to create a RAID group.

Explanation

The capacities and the numbers of rotations are not equal among the disks making up a RAIDGroup.
(ETERNUS6000)

Response

Select disks making up a RAIDGroup in such a way that the capacities and the numbers of rotations are equal among the disks.

22605: Are you sure you want to cancel composition?

Explanation

This message confirms whether the configuration currently displayed can be abandoned to load a new configuration onto the design window.

Response

If the configuration currently displayed on the design window is required, save the configuration into a file and then perform configuration load operation.

22606: Specified device already exists. Overwrite?

Explanation

This message confirms whether the configuration displayed on the design window can be overwritten when the device to be loaded is the same as the device unit displayed on the window.

Response

If you do not want to overwrite the configuration on the design window, save the configuration into a file and then perform configuration load operation.

22607: Cannot read from multiple devices simultaneously.

Explanation

More than one device cannot be selected for device load operation.

Response

Specify one device at a time for device load operation.

22608: Device not supported.

Explanation

The device that was specified for device load operation is not supported.

Response

Perform device load operation by specifying a supported device.

22609: Cannot read from device while it is in error state.

Explanation

The device in one of the following states cannot be loaded:

1. The status of the device is error.

2. The RAIDGroup is using a hot spare disk.

3. Copy-back is in progress.

4. Rebuilding is in progress.

5. Storage device within which a LogicalVolume of LUN concatenation is being created.

Response

Remove the problem cause and then reload the device.

22610: Save composition?

Explanation

Exiting was instructed before saving the configuration on the design window.

Response

To save the configuration on the design window, click OK.

22612: Serial number already in use.

Explanation

An existing device has the same serial number.

Response

Enter a valid serial number.

22617: There is no device on which device matching can be performed.

Explanation

The device used for device matching is not registered with the operation management server.

Response

Register the relevant device with the operation management server and then retry the operation.

22618: No device corresponds to specified serial number.

Explanation

The device with the specified serial number is not registered with the operation management server.

Response

Register the relevant device with the operation management server and then retry the operation.

22619: There was no device on which device matching could be performed.

Explanation

A device for which device matching has been performed is not found.

Response

Perform device matching and then retry the operation.

22620: Enter serial number.

Explanation

No serial number was specified for the device unit.

Response

Specify the serial number and then retry the operation.

22621: No RAID group can be selected.

Explanation

No RAIDGroup exists.

Response

Using the automatic configuration function, create a RAIDGroup to which LogicalVolumes can be assigned, and then retry the operation.

22622: Data is stored in the logical volume and the RAID group. When the logical volume and RAID group are deleted, all data contained in these groups will be erased. Continue anyway?

Explanation

This message warns that data will be deleted if a LogicalVolume is deleted.

Response

Make sure that deleting the specified LogicalVolume causes no problems, and then delete it.

22623: Cannot create RAID group with the selected RAID level using nearline FC disks.

Explanation

Nearline FC disks cannot be used at the selected RAID level.

Response

Confirm disks with which a RAID group of the selected RAID level can be created. For details, refer to the SA/SE handbook.

22625: Selected disk composition not recommended. Use the highest capacity disks in the loop as the hot spares. Continue anyway?

Explanation

The selected disk is not configured in the recommended way. For a hot spare disk, select the disk having the largest capacity in the loop.

Response

Select the disk having the largest capacity in the loop, and retry the operation.

22626: RAID group cannot be created for the selected composition.

Explanation

A RAIDGroup cannot be created with the selected disk configuration.

Response

Refer to the SA/SE Handbook, and specify a disk configuration with which a RAIDGroup can be created.

22627: Device cannot be copied because it contains an unsupported RAID group.

Explanation

The from-copy device unit cannot be copied because it contains an unsupported RAID group. RAID levels of the supported RAID group are RAID1+0, RAID1, RAID5 and RAID6.

Response

Unsupported RAID groups were found in the storage device configuration when loading the device configuration from real devices. Delete the unsupported RAID groups of the real devices, reload the device configuration, and then execute Copy Device again. Otherwise, create a new device unit and make copies of it.

22628: Device cannot be copied because it contains a volume consolidation.

Explanation

The from-copy device unit cannot be copied because it contains an unsupported linked volume.

Response

Linked volumes were found in the storage device configuration when loading the device configuration from real devices. Delete the linked groups of the real devices, reload the device configuration, and then execute Copy Device again. Otherwise, create a new device unit and make copies of it.

22629: Device cannot be copied because it contains a mainframe logical volume.

Explanation

The device cannot be copied because the device unit specified as the copy source contains an unsupported mainframe volume.

Response

Unsupported mainframe volumes are found in the storage device configuration because the device configuration was read from actual devices. Delete the unsupported mainframe volumes in the actual devices, reload the device configuration, and then execute Copy Device again. Or, create a new device unit and execute Copy Device again using the new device as a copy source.

22630: Cannot copy device.

Explanation

The device cannot be copied because the device unit specified as the copy source is a manual assembly unit or a storage device that cannot be edited.

Response

A manual assembly unit or a storage device that cannot be edited is found in the device configuration because the device configuration was read from actual devices. Create a new device unit and execute Copy Device again using the new device as a copy source.

22631: The file does not exist.

Explanation

The file to be opened is not found.

Response

Confirm that the file to be opened exists and try to open it again.

22632: File format is not supported.

Explanation

The unsupported format file was saved or opened.

Response

Select a ".cnc" file and try to save or open it again.

22633: It cannot create to selected device.

Explanation

The selected device unit cannot be edited. Therefore, you cannot specify the device to add components.

Response

Select the device unit you want to edit on the resource view, load it into Storage Volume Configuration Navigator, and then restart the job.

22634: It cannot operate other than the device you are editing.

Explanation

If a device registered on the resource view is selected and started by selecting [To Send]-[Storage Volume Configuration Navigator] from the pop-up menu, no other storage devices than the storage device specified at start-up are not editable.

Response

Perform the device read operation for the device to be edited by starting Storage Volume Configuration Navigator by selecting it from the Start menu or by clicking the corresponding desktop icon, or start the storage device by selecting [File] - [Storage Volume Configuration Navigator] from the resource view.

22635: RAID1 does not allow addition of disks.

Explanation

No disk can be added in the RAID1 level.

Response

Create a new RAID1.

22636: Cannot delete disk because that would put the number of disks below the minimum required by RAID1.

Explanation

No more disks can be deleted because doing so puts the number of disks that constitute the RAID group of RAID1 under the minimum configuration.

Response

No disks can be deleted because the current disks are required for the minimum configuration. For details of the number of component disks, refer to the SA/SE Handbook.

22637: Cannot delete one of the disks.

Explanation

Disks in an unsupported RAID level or in a RAID group containing an unsupported LogicalVolume cannot be deleted.

Response

Delete the disks in the unsupported RAID level or in the RAID group containing an unsupported LogicalVolume from the actual device, and then reread the device.

22638: Device cannot be copied because it contains an MVV logical volume.

Explanation

Copy Device failed because the device unit specified as the copy source contained an unsupported MVV volume.

Response

Unsupported MVV volumes are found in the storage device configuration because the device configuration was read from actual devices. Delete the unsupported MVV volumes from the actual devices, reload the device configuration, and then execute Copy Device again. Or, create a new device unit and execute Copy Device again using the new device as a copy source.

22639: Device cannot be copied because it contains an unknown logical volume.

Explanation

Copy Device failed because the device unit specified as the copy source contained an unsupported volume.

Response

Unsupported volumes are found in the storage device configuration because the device configuration was read from actual devices. Delete the unsupported volumes from the actual devices, reload the device configuration, and then execute Copy Device again. Or, create a new device unit and execute Copy Device again using the new device as a copy source.

22640: An invalid disk was specified for installation between slot 0 and 3 in DE0x00.

Explanation

From the disks specified for Slot0 through Slot3 of DE0x0, there is a disk that cannot be mounted as a backup disk.

Response

Using disk operation, specify a disk that can be mounted as a backup disk. For information on disks that cannot be mounted as a backup disk, refer to the "ETERNUS3000 SA/SE Handbook".

22643: Select disks from the same BRT pair.

Explanation

Disks in different pair BRTs (the disks have different Loop ID colors) cannot be selected.

Response

Select disks in the same pair BRT (the disks must have the same Loop ID color), and perform the operation again. For details, refer to the SA/SE handbook.

22646: Cannot add disk to the RAID group with the selected RAID level.

Explanation

Disks cannot be added to a RAID group of the selected RAID level.

Response

Create a new RAID group of the selected RAID level.

22647: Cannot remove disk from the RAID group with the selected RAID level.

Explanation

A disk that is a component of a RAID group of the selected RAID level cannot be deleted.

Response

A disk that is a component of a RAID group of the selected RAID level cannot be deleted.

22649: Select disks from different loop IDs in the BRT pair.

Explanation

The RAID group cannot be created by selecting disks with the same Loop ID in a pair BRT (the disks have the same Loop ID color).

Response

Select disks with different Loop IDs in the pair BRT (the disks must have the same Loop ID color), and perform the operation again. For details, refer to the SA/SE handbook.

22651: Select disks for disk pairs from different loop IDs.

Explanation

Disks that are to be paired are selected from the same Loop ID.

Response

Select disks to be paired from the different Loop IDs, and perform the operation again. For details, refer to the SA/SE handbook.

22652: Allocation of the selected disks is not recommended. Disks for disk pairs should be selected from a different BRT pairs. Continue anyway?

Explanation

Disks to be paired are selected from the same pair BRT (the disks have the same Loop ID color). Select disks to be paired from different pair BRTs (the disk must have different Loop ID colors).

Response

Perform again the configuration in which disks to be paired are selected from different pair BRTs (the disk must have different Loop ID colors). However, it is not necessary to always use such a configuration. For details, see the SA/SE handbook.

22654: Allocation of the selected disks is not recommended. Disks should be selected from the same loop ID. Continue anyway?

Explanation

Disks from different Loop IDs are selected. Allocate disks from the same LoopID.

Response

Perform again the configuration in which disks from the same Loop ID are selected. However, it is not necessary to always use such a configuration. For details, see the SA/SE handbook.

22655: Allocation of the selected disks is not recommended. An equal number of disks should be selected from different loop IDs. Continue anyway?

Explanation

Disks from the same Loop ID are selected. Allocate disks evenly from different Loop IDs.

Response

Perform again the configuration in which disks from different Loop IDs are selected evenly. However, it is not necessary to always use such a configuration. For details, see the SA/SE handbook.

22657: Cannot remove disk. Delete disks such that remaining paired disks are on different loop IDs.

Explanation

Since disks of the same Loop ID are to be paired in this configuration, they cannot be deleted.

Response

Perform the deletion in a way that disks to be paired are of different Loop IDs. For details, see the SA/SE handbook.

22658: Disks to be paired are allocated to the same BRT pair. The recommended configuration is the one in which disks to be paired are allocated to different BRT pairs.

Explanation

Disks to be paired are allocated from the same pair BRT (the disks have the same LoopID color). The recommenced configuration is the one in which disks to be paired are allocated in different pair BRTs (the disk must have different LoopID colors).

Response

Reselect disks in a way that disks to be paired are of different pair BRTs (the disk must have different LoopID colors). However, it is not necessary to always use such a configuration. For details, see the SA/SE handbook.

22660: Logical volume capacity is below the minimum.

Explanation

LogicalVolume was specified with a capacity with which creation is impossible.

Response

Perform the operation in a way that the capacity of the LogicalVolume to be created becomes no less than the minimum capacity. For details, see the SA/SE handbook.

22661: Cannot add disk because that would put the number of disks over the maximum required by RAID6.

Explanation

As the number of disks configuring RAID groups in RAID6 becomes larger than the maximum configuration, disks cannot be added.

Response

Disks cannot be added because of the maximum configuration. For details of the maximum configuration, refer to SA/SE handbooks for respective devices.

22662: Cannot delete disk because that would put the number of disks below the minimum required by RAID6.

Explanation

Disks cannot be deleted because the number of disks configuring RAID groups in RAID6 is less than the minimum configuration.

Response

Disks cannot be deleted because of the minimum configuration. For details of the minimum configuration, refer to SA/SE handbooks for respective devices.

22663: Allocation of the selected disks is not recommended. An equal number of disks should be selected from different loop IDs. Continue anyway?

Explanation

Arrange disks evenly with different LoopIDs.

Response

Retry to make a configuration where disks are evenly selected with different LoopIDs. In addition, it is not always necessary to make this configuration. For details, refer to the SA/SE handbook.

22664: The device cannot be copied because it contains the LUNMapping.

Explanation

Since an unsupported LUNMapping exists in a device unit specified by copy source, device copy is not allowed.

Response

It is when the configuration is being read from a real device that LUNMapping exists in the configuration of a storage device. After enabling the security setting for FC port on the real device, read the device configuration again to execute device copy.

22665: The device cannot be copied because it contains the concatenated AffinityGroup.

Explanation

Since an supported AffinityGroup exists in a device unit specified by the copy source, device copy is not allowed.

Response

It is when the configuration is being read from a real device that a concatenated AffinityGroup exists in the configuration of a storage device. After deleting the concatenated AffinityGroup in the real device, read the device configuration again and execute device copy. In addition, create a new device unit and retry device copy with the device unit as a copy source.

22666: Cannot delete one of the AffinityGroups.

Explanation

Since a LogicalVolume with an unallocated LUN is allocated to an AffinityGroup, the AffinityGroup cannot be deleted. Or it cannot be deleted because of a concatenated AffinityGroup or a AffinityGroup set by the Host AffinityGroup.

Response

The AffinityGroup or concatenated AffinityGroup to which a LogicalVolume in use is allocated is about to be deleted. Check the system configuration.

22667: An invalid disk was specified for installation. Install same capacity and speed disk between slot0 and 3 in DE0x00.

Explanation

The same capacity and speed disk must be installed between slot0 and 3 in DE0x00.

Response

The same capacity and number of rotations of a disk must be specified between slot0 and 3 in DE0x00.

22668: The specified number of disks is not recommended. Recommended composition is 6. Continue anyway?

Explanation

The specified number of disks is not recommended. Recommended composition is 6.

Response

The recommendation is to use 6 as the number of disks; however this is not a requirement.

22669: Hot spare disk with insufficient capacity found in following disk type. Create hot spare disk of following type.

Explanation

The disk capacity for the created RAID group configuration is greater than the hot space capacity of the existing same disk type so that a recovery cannot be performed when a disk error occurred.

Response

Define the maximum disk capacity within the device and use SAS and nearline SATA disks as the hot spare.

22670: An invalid disk was specified for installation on following slot.

Explanation

An attempt was made to install an invalid disk type.

Response

A valid disk type must be specified.

22671: The loop that has hot spare disk with insufficient capacity found in following disk type. Create hot spare disk of following type in each loop.

Explanation

The disk capacity for the created RAID group configuration is greater than the hot space capacity of the existing same disk type and loop.

Response

Specify the applicable maximum disk space for the type of hot spare disk used in the loop.

11.3.2 Warning messages

42520: Install disks in order from slot 0, starting with the lower number DEs (loop ID:0).

Explanation

When disks are mounted on the ETERNUS3000, check whether disks are mounted in ascending order of DE numbers in each loop and also in ascending order of slot numbers beginning from 0 in each DE. A disk that fails to satisfy these conditions exists in Loop ID 0.

Response

Mount disks in ascending order of DE numbers in each loop and also in ascending order of slot numbers beginning from 0 in each DE.

42521: Install disks in order from slot 0, starting with the lower number DEs (loop ID:1).

Explanation

When disks are mounted on the ETERNUS3000, check whether disks are mounted in ascending order of DE numbers in each loop and also in ascending order of slot numbers beginning from 0 in each DE. A disk that fails to satisfy these conditions exists in Loop ID 1.

Response

Mount disks in ascending order of DE numbers in each loop and also in ascending order of slot numbers beginning from 0 in each DE.

42530: Install the disks starting with the first one.

Explanation

Disks are not sequentially mounted (with some slots skipped) from the beginning in each DE. (ETERNUS6000)

Response

Mount disks sequentially without skipping a slot from the beginning of each DE. For details of the disk mounting method, refer to the SA/SE handbook.

42532: The loop ID:0 DEs were not installed in sequence.

Explanation

DEs are not continuously mounted in Loop ID 0. (ETERNUS3000)

Response

Mount DEs in ascending order of DE numbers in Loop ID 0 without skipping.

42533: The loop ID:1 DEs were not installed in sequence.

Explanation

DEs are not continuously mounted in Loop ID 1. (ETERNUS3000)

Response

Mount DEs in ascending order of DE numbers in Loop ID 1 without skipping.

42534: The DEs were not installed in sequence.

Explanation

DEs are not continuously mounted. (ETERNUS6000)

Response

Mount DEs in ascending order of DE numbers.

42535: One loop does not contain a hot spare disk.

Explanation

Although a hot spare disk must be mounted in each loop, a hot spare disk is missing in a certain loop.

Response

Mount a hot spare disk in each loop.

42536: Install 12 or more disks that are not nearline FC disks.

Explanation

The number of disks installed in the unit is less than the required number. It is necessary to install required number of disks or more.

Response

When nearline FC disks are mounted, it is necessary that at least 12 nearline disks (except the system disk) be mounted. For real devices, read the devices after correcting the configuration of the real devices. For details, see the SA/SE handbook.

42537: Install 24 or more disks that are not nearline FC disks.

Explanation

The number of disks installed in the unit is less than the required number. It is necessary to install the required number of disks or more.

Response

When nearline FC disks are mounted, it is necessary that at least 24 nearline disks (except the system disk) be mounted. For real devices, read the devices after correcting the configuration of the real devices. For details, see the SA/SE handbook.

42538: The hot spare of the SAS disk is not found.

Explanation

The maximum capacity of the SAS hot spare disk has not been defined.

Response

Define the maximum disk capacity for the SAS hot spare disk.

42539: The hot spare of the nearline SATA disk is not found.

Explanation

The maximum capacity of the nearline SATA hot spare disk has not been defined.

Response

Define the maximum capacity for the nearline SATA hot spare disk.

42540: One loop does not contain the hot spare of the fibre channel disk.

Explanation

A RAID group loop has been created without a hot spare fibre channel disk.

Response

Define a hot spare fibre channel disk (include a maximum capacity) in the RAID Group loop.

42541: One loop does not contain the hot spare of the nearline FC disk.

Explanation

A nearline FC disk RAID group has been created without a hot spare fibre channel disk.

Response

.Define a hot spare fibre channel disk (include a maximum capacity) in the nearline FC disk RAID group.

42542: One loop does not contain the hot spare of the nearline SATA disk.

Explanation

A nearline SATA disk RAID group has been created without a nearline SATA hot spare disk.

Response

Define a hot spare nearline SATA disk (include a maximum capacity) in the nearline SATA disk RAID group.

11.3.3 Error messages

62000: Unexpected Error occurred. msg

Explanation

An unexpected exception occurred.

Response

Collect this message and other information, and contact your Fujitsu certified service engineer to investigate the issues.

62001: Internal Program Error occurred.

Explanation

An internal error occured.

Response

Collect this message and other information, and contact your Fujitsu certified service engineer to investigate the issues.

62002: Network Error occurred. (node)

Explanation

An error occurred during communication between Manager and the operation target device node ("node" may not be displayed).

Response

Check the network environment for problems.

62056: Timeout error occurred in LogicalVolume format operation.

Explanation

Format processing was instructed to the device but start processing was not completed within the monitoring time.

Response

Check the formatting condition of the relevant volume. If the formatting has not begun, execute formatting again.

62057: LogicalVolume format operation failed

Explanation

Format processing that was instructed to the device terminated abnormally.

Response

Check the formatting condition of the relevant volume. If the formatting has not begun, execute formatting again.

62101: The device (name) does not supported by the Storage Volume Configuration Navigator

Explanation

A device that was not supported by Storage Volume Configuration Navigator was specified for operation.

Response

Start operation by specifying a device supported by Storage Volume Configuration Navigator.

62102: Failed to create the work directory(dir) for the Storage Volume Configuration Navigator.

Explanation

Processing was interrupted because a work directory could not be created.

Response

Check whether an error such as a space shortage occurred in the system volumes on the operation management server.

62103: Failed to create the work file(file) for the Storage Volume Configuration Navigator.

Explanation

Processing was interrupted because a work file could not be created.

Response

Check whether an error such as a space shortage occurred in the system volumes on the operation management server.

62104: Failed to read the work file(file) for the Storage Volume Configuration Navigator.

Explanation

Processing was interrupted because the work file could not be read.

Response

Check whether an error occurred in the system volumes on the operation management server.

62105: Unrecovered error occurred. msg

Explanation

Processing was interrupted because an unrecoverable error occurred.

Response

Collect the message and other information for an investigation, and contact your Fujitsu certified service engineer.

62121: CMnum not found in the configuration of the storage

Explanation

Regarding the CM module of the target storage device, the actual device configuration does not agree with the defined configuration data. The configuration data before configuration editing was probably inconsistent with the actual device configuration.

Response

The defined configuration data that was edited cannot be used because it is inconsistent with the actual device configuration. Save the latest configuration data and edit it again.

62122: CAnum1:Portnum2 not found in the configuration of the storage

Explanation

Regarding the CM module of the target storage device, the actual device configuration does not agree with the defined configuration data. The configuration data before configuration editing was probably inconsistent with the actual device configuration.

Response

The defined configuration data that was edited cannot be used because it is inconsistent with the actual device configuration. Save the latest configuration data and edit it again.

62123: The type of CAnum of the storage is type.

Explanation

Regarding the CM module type of the target storage device, the actual device configuration does not agree with the defined configuration data. The configuration data before configuration editing was probably inconsistent with the actual device configuration.

Response

The defined configuration data that was edited cannot be used because it is inconsistent with the actual device configuration. Save the latest configuration data and edit it again.

62124: DEnum1:Disknum2 not found in the configuration of the storage

Explanation

Regarding the disks of the target storage device, the actual device configuration does not agree with the defined configuration data. The configuration data before configuration editing was probably inconsistent with the actual device configuration.

Response

The defined configuration data that was edited cannot be used because it is inconsistent with the actual device configuration. Save the latest configuration data and edit it again.

62125: The capacity of DEnum1:Disknum2 of the storage is num3GB.

Explanation

Regarding the disk capacity of the target storage device, the actual device configuration does not agree with the defined configuration data. The configuration data before configuration editing was probably inconsistent with the actual device configuration.

Response

The defined configuration data that was edited cannot be used because it is inconsistent with the actual device configuration. Save the latest configuration data and edit it again.

62126: The disk type of DEnum1:Disknum2 of the storage is different.

Explanation

The actual disk type of the storage target disk does not match the type defined in configuration settings.

Response

The edited configuration settings data cannot be used because it conflicts with the configuration of the actual device. Save the previous configuration data and edit the configuration again.

62130: The configuration data is inconsistent.

Explanation

Processing was interrupted because an inconsistency was detected in the defined configuration data.

Response

Collect the message and other information for an investigation, and contact your Fujitsu certified service engineer.

62131: RAIDGroupnum2 assigned to LogicalVolumenum1 does not exist.

Explanation

Regarding the RAID group of the target storage device, the actual device configuration does not agree with the defined configuration data. The RAID group configuration of the device was probably changed after the actual device configuration data was saved.

Response

The defined configuration data that was edited cannot be used because it is inconsistent with the actual device configuration. Save the latest configuration data and edit it again.

62132: The Hot Spare Disk (DEnum1:Disknum2) is assigned to RAIDGroupnum3.

Explanation

Regarding the disk settings of the target storage device, the actual device configuration does not agree with the defined configuration data. The disk settings of the device were probably changed after the actual device configuration data was saved.

Response

The defined configuration data that was edited cannot be used because it is inconsistent with the actual device configuration. Save the latest configuration data and edit it again.

62133: Dynamic reconfiguration function was not started.

Explanation

Dynamic reconfiguration processing was instructed to the storage device but start processing was not completed within the monitoring time.

Response

Collect the message and other information, and contact your Fujitsu certified service engineer to investigate the issues.

62134: Dynamic reconfiguration change does not become effective.

Explanation

Dynamic reconfiguration processing that was instructed to the storage device was interrupted because an error response was made.

Response

Collect the message and other information, and contact your Fujitsu certified service engineer to investigate the issues.

62135: The function(%1) does not supported by the Storage Volume Configuration Navigator.

Explanation

The function (%1) is not supported by the Storage Volume Configuration Navigator.

%1 includes the following function.

"Joint AffinityGroup"

Indicates concatenated affinity group functions.

Response

Respond in accordance with the function included in %1.

Joint AffinityGroup:

The configuration at the Storage Volume Configuration Navigator is not changeable.
Change the configuration with reference to the Storage device manual.

62137: The devices, RAID cannot be putting set for the ECO Mode.

Explanation

Since the device or RAID was in Ecomode, processing was aborted.

Response

After cancelling Ecomode of the device or RAID, resume the operation.

62145: The main frame volume already exists in the storage.

Explanation

A new configuration cannot be set up because a mainframe volume exists in the storage device.

Response

Storage Volume Configuration Navigator does not permit a mainframe volume configuration already existing at the time of the new configuration setup to be deleted. Delete the mainframe volume while referring to the storage device manual, and re-execute this operation.

62146: The main frame volume (LogicalVolumenum)exists in the RAIDGroup.

Explanation

Reconfiguration was attempted for the RAID group containing the mainframe volume.

Response

Storage Volume Configuration Navigator does not permit the mainframe volume to be reconfigured. Reconfigure it while referring to the storage device manual.

62147: LogicalVolume exists in storage.

Explanation

A new configuration cannot be set up because a LogicalVolume exists in the target device.

Response

Storage Volume Configuration Navigator does not permit a LogicalVolume configuration already existing at the time of the new configuration setup to be deleted. Delete the LogicalVolume while referring to the storage device manual, and re-execute the operation.

62150: Specified RAIDGroup cannot be registered.

Explanation

A RAID group could not be created because of a disk status error.

Response

Check the storage device for disk status errors. If an error is found, maintain the relevant disk drive and then re-execute the operation.

62151: Specified LogicalVolume cannot be registered.

Explanation

A LogicalVolume could not be created because of a RAID group status error.

Response

Check the storage device for RAID group status errors. If an error is found, maintain the relevant RAID group and then re-execute the operation.

62152: Specified HotSpare cannot be registered.

Explanation

HotSpare could not be created because of a disk status error.

Response

Check the storage device for disk status errors. If an error is found, maintain the relevant disk drive and then re-execute the operation.

62153: Specified RAIDGroup cannot be deleted.

Explanation

The RAID group could not be deleted because of a RAID group status error.

Response

Check the storage device for RAID group status errors. If an error is found, maintain the relevant RAID group and then re-execute the operation.

62154: Specified LogicalVolume cannot be deleted.

Explanation

A LogicalVolume could not be deleted because of a RAID group or LogicalVolume status error.

Response

Check the storage device for RAID group or LogicalVolume status errors. If an error is found, maintain the relevant RAID group or LogicalVolume and then re-execute the operation.

62155: Specified HotSpare cannot be deleted.

Explanation

HotSpare could not be deleted because of a disk status error.

Response

Check the storage device for disk status errors. If an error is found, maintain the relevant disk drive and then re-execute the operation.

62521: Install the two data disks in the first slots of the DE.

Explanation

A DE consists of fewer than two disks. Two or more disks must be mounted on each DE.

Response

Perform disk operation to mount data disks in the first two slots of each DE. System disks are not included.
For a real device, modify the real device configuration and then execute device loading.

62522: The number of DEs is different in loop ID:0 and loop ID:1.

Explanation

The same number of DEs should be mounted in each loop but is not. (ETERNUS3000)

Response

Mount the same number of DEs in each loop.

62523: Install disk between slot 0 and 3 in DE0x00.

Explanation

Disks should be mounted as backup disks in slots 0 to 3 of the DE0x00 but are not.

Response

Mount disks in DE0x00 slots 0 to 3.

62524: Device matching failed.

Explanation

An error occurred in the operation management server during device matching.

Response

Make sure that the operation management server operates normally.

62525: Device setup not complete on one device.

Explanation

The relevant device cannot be set up because an error occurred before setup.

Response

Remove the error cause and retry the operation.

62526: Internal program error.

Explanation

An internal inconsistency occurred in the Storage Volume Configuration Navigator.

Response

Write down this message and contact your Fujitsu engineer.

62527: Could not read definition file.

Explanation

The configuration definition file could not be loaded.

Response

Write down this message and contact your Fujitsu engineer.

62528: Error in definition file.

Explanation

The configuration definition file may have been destroyed.

Response

Write down this message and contact your Fujitsu engineer.

62529: DE is not installed in sequence.

Explanation

DEs are not mounted in ascending serial order of the DE numbers (ETERNUS4000, ETERNUS8000 and ETERNUS2000).

Response

Mount DEs in ascending serial order of the DE numbers.

62530: One of the hot spare disks is not working.

Explanation

A hot spare disk was defined but did not function as a hot spare disk because its capacity was too small.

Response

Define the disk with the largest capacity in the loop as a hot spare disk.

62531: There are insufficient disks. There must be at least 4.

Explanation

The number of disks mounted on the device does not satisfy the requirements. More disks must be mounted.

Response

Mount four or more disks. For a real device, correct the configuration of the real device and then perform device loading.

62532: There are insufficient disks. There must be at least 5.

Explanation

The number of disks mounted on the device does not satisfy the requirements. More disks must be mounted.

Response

Mount five or more disks. For a real device, correct the configuration of the real device and then perform device loading.

62533: There are insufficient disks. There must be at least 8.

Explanation

The number of disks mounted on the device does not satisfy the requirements. More disks must be mounted.

Response

Mount eight or more disks. For a real device, correct the configuration of the real device and then perform device loading.

62535: There are insufficient disks. There must be at least 20.

Explanation

The number of disks mounted on the device does not satisfy the requirements. More disks must be mounted.

Response

Mount 20 or more disks. For a real device, correct the configuration of the real device and then perform device loading.

62536: There are insufficient disks. There must be at least 16.

Explanation

The number of disks mounted on the device does not satisfy the requirements. More disks must be mounted.

Response

Mount 16 or more disks. For a real device, correct the configuration of the real device and then perform device loading.

62537: There are insufficient disks. There must be at least 32.

Explanation

The number of disks mounted on the device does not satisfy the requirements. More disks must be mounted.

Response

Mount 32 or more disks. For a real device, correct the configuration of the real device and then perform device loading.

62538: There are insufficient disks. There must be at least 128.

Explanation

The number of disks mounted on the device does not satisfy the requirements. More disks must be mounted.

Response

Mount 128 or more disks. For a real device, correct the configuration of the real device and then perform device loading.

62539: Exception occurred.

Explanation

An unexpected exception occurred.

Response

Troubleshoot by referring to the following section in the manual below to collect necessary data, and then call your Fujitsu systems engineer (SE).
"ETERNUS SF Storage Cruiser User Guide" 9.1.1.1 How to collect data for trouble investigation

62540: IOException occurred.

Explanation

An I/O exception occurred. Any attempt to open a file will fail when the file is being opened. Any attempt to save a file will fail when the file is being saved.

Response

Check the target directory authority of the file.

62541: There are insufficient disks. There must be at least 176.

Explanation

The required number of disks mounted on the device is not met. More than the required number of disks is required.

Response

Mount 176 or more disks. In case of a real device, correct the configuration of the real device before device read.

62542: There are insufficient disks. There must be at least 184.

Explanation

The required number of disks mounted on the device is not met. More than the required number of disks is required.

Response

Mount 184 or more disks. In case of a real device, correct the configuration of the real device before device read.

62543: There are insufficient disks. There must be at least 192.

Explanation

The required number of disks mounted on the device is not met. More than the required number of disks is required.

Response

Mount 192 or more disks. In case of a real device, correct the configuration of the real device before device read.

62544: Hot spare disk with insufficient capacity found in SAS disk.

Explanation

The capacity of the hot spare in the defined SAS disk is insufficient so that the disk does not work as the hot spare.

Response

Define the correct maximum capacity for the hot spare disk.

62545: Hot spare disk with insufficient capacity found in nearline SATA disk.

Explanation

The capacity of the hot spare in the defined nearline SATA disk is insufficient so that the disk does not work as the hot spare.

Response

Define the correct maximum capacity for the hot spare disk.

62546: There are insufficient disks. There must be at least 6.

Explanation

The minimum number of disks (6) has not been mounted.

Response

Mount at lest 6 disks. Check the configuration of the actual device and then reload the device.

62547: One loop that has hot spare disk with insufficient capacity found in fibre channel disk.

Explanation

The capacity of the hot spare fibre channel disk is smaller than the capacity defined in the RAID Group on the same loop.

Response

Define the correct maximum capacity for the hot spare disk.

62548: One loop that has hot spare disk with insufficient capacity found in nearline FC disk.

Explanation

The capacity of the hot spare nearline FC disk is smaller than the capacity defined in the RAID Group on the same loop.

Response

Define the correct maximum capacity for the hot spare nearline FC disk.

62549: One loop that has hot spare disk with insufficient capacity found in nearline SATA disk.

Explanation

The capacity of the hot spare nearline SATA disk is smaller than the capacity defined in the RAID Group o n the same loop.

Response

Define the correct maximum capacity for the hot spare nearline SATA disk.

Contents Index