5. User Guide

5.1. Administration

5.1.1. User Management

Users can either be defined locally or in the LDAP-directory. To configure LDAP, see section Configuration.

To create new users or change existing ones, go to Administration and click on the Users-Button. When creating or changing a user, you will see the following form:

User Management

5.1.2. Roles

When creating a user, you need to assign a role. Smart Automation Manager for Hitachi knows 2 types of roles:

5.1.2.1. Operator

An Operator does see the ‘Storage Mgmt’- and the ‘Reports’-Tab. He can execute all storage management operations, but he does not see the ‘Administration’-tab and cannot execute admin-tasks.

5.1.2.2. Root

A user with the role ‘Root’ has access to everything in the application.

5.1.3. Storage Arrays

This menu is for managing the storage arrays. If you need to add new storage arrays, you have to do this here after they were added to the Smart Automation Manager for Hitachi. The form looks like the following picture:

Storage Arrays

When adding a new storage array, you need to specify at least the Device Type. This is the same model description as in the Hitachi Device Manager. If you leave the field “Command Device” empty, SAM4H tries to communicate by the IP-Command Device for Raidcom commands. Otherwise the application communicates over the command device path, which was provided in this field.

5.1.4. Storage Clusters

This menu is for adding new storage clusters. A storage cluster is a combination of 1 or 2 storage arrays. The form for adding a storage cluster looks the following:

Storage Clusters

5.1.5. Pools

In this menu you can enable and disable pools and change its tier prices for the charge back report:

Pools

Disabling a pool means, it is not available for provisioning. This is handy, if you run out of space in a pool and want to disable provisioning from this pool until you installed more disks.

The tier prices are used to calculate the costs in the charge back report. If you specify a price, it will be used for the calculation. But it is completely optional to specify a price. For example, if you don’t want to charge empty space, you just leave it blank. Then only the consumed tier space is used for the price calculation.

5.1.6. Server/Clusters

This menu is for creating and changing clusters. A Cluster is a combination of multiple HostGroups from different Storage Arrays.

Clusters

If Auto-Discover HSDs is enabled, all host-groups with the same name as this cluster-name will be assigned to it automatically. Host-groups, whose name does not have the same name anymore, will be removed from the cluster, if auto-discover is enabled.

Schedule Snap Resync lets you provide a weekday, where a snapshot resync will be triggered automatically. You can specify a Cost Center for each cluster. This field is used for the chargeback report.

5.1.7. Dp-Vol-Sizes

DpVol-Sizes are standard sizes in blocks for creating DP-Volumes The form will look like the following picture:

Dp-Vol-Sizes

5.1.8. DP-Vol Templates

DP-Vol Templates are configuration templates, where you specify how new DpVols are created. The form will look like the following picture. Please note, that some fields do only appear after certain selections are done.

Dp-Vol Templates

The following parameters can be configured:

5.1.8.1. Name

The name of the DP-Vol Template. A good way is to specify the type of use (e.g.: Oracle, Unix, SAP)

5.1.8.2. Storage Clusters

Specify the Storage Clusters, for which this template could be used.

5.1.8.3. Pools

Here you specify from which pool the new DP-Vol will be created. You can specify only one pool per Storage Array. If you specify multiple pools from multiple storage arrays, IW Storage Manage Hitachi will find out automatically the right pool when creating a new DP-Vol.

5.1.8.4. CU-Range

In this range the CU lies when a new DpVol is created. E.g.: If you have a CU-Range 10-20, then a new DpVol will be created between 10:00 and 20:FF. When all DP-Vol Template are configured to use its own CU-Range, it will be possible to identify the use of a Lun according its CU.

5.1.8.5. Start LUN-Nr.

The minimal Lun-ID of the mapped Lun. This can be used to identify the Lun according to its Lun-ID. E.g.: If you have a VmWare server, you can create one DP-Vol Template for the VmWare server LUNs and one DP-Vol Template for the VmWare guest LUNs. It is then possible to use a Lun-ID start address greater than 0 for the guest LUNs which will help the VmWare admin to identify the guest LUNs according to its LUN-ID.

5.1.8.6. Command Device

When this option is selected, the new LUN will be configured as a command device.

5.1.8.7. Replication

Let you specify if and how a LUN should be replicated.

5.1.8.8. Snapshot

Let you choose, if a snapshot should be created for the selected LUN.

5.1.8.9. DP-Vol Sizes

Here you can specify if the sizes of a new DP-Vol will be defined or can be freely chosen by the operator. If ‘size editable’ is selected, the operator can specify the size of the new DP-Vol either in blocks or GBs. When ‘size editable’ is not selected, you must specify at least one DP-Vol-Size. All selected DP-Vol-Sizes are then presented to the operator as a drop down when creating a new DP-Vol.

5.1.9. Host-Group Template

HSD Config templates are configuration templates for HSD creation. The form looks like the following picture:

Host-Group Templates

5.1.9.1. Name

The name of the HSD Config Template.

5.1.9.2. Storage Clusters

The Storage Clusters, where this template can be selected for.

5.1.9.3. Global Active Device

If checked, the hostgroup will be prepared for GAD. It creates a host_group for every server and port and take care of the ALUA options. If the HDLM-Option is checked, also the HostModeOption 78 (non preferred path) is set, if the server is not at the same site as the storage array.

5.1.9.4. Resource Groups

The resource group for each storage array, where the newly created host groups are configured in.

5.1.9.5. Host Mode

Drop down for selecting a Host Mode. The Host Modes are discovered automatically by a config reload but must be named in the ‘Host Mode’-admin-menu (see next chapter).

5.1.9.6. Host Mode Options

Select Host Mode Options which are applied to the newly created HostGroup. Configure Host Mode Options in the ‘Host Mode Options’-Admin-Menu.

5.1.10. Host Modes

Configure Host Modes which are used by the HSD Config Templates. The form looks like the following picture:

Host Modes

The following parameters can be configured:

5.1.10.1. Value

The value of the Host Mode. This is a string field.

5.1.10.2. Description

The description will be shown in the drop down.

5.1.11. Host Mode Options

Configure Host Mode Options which are used by the HSD Config Templates. The form looks like the following picture:

Host Mode Options

The following parameters can be configured:

5.1.11.1. Value

The value of the Host Mode Option in decimal.

5.1.11.2. Name

The name of the Host Mode Option.

5.1.11.3. Description

The description will be shown in the drop down.

5.1.12. Port Groups

When creating new HostGroups, a user can only select predefined PortGroups. This ensures an even configuration accross the different ports. The dialogue to configure Port Groups is found under administration and looks the following:

Create new Port Group

The following parameters can be configured:

5.1.12.1. Purpose

A free text which is displayed when creating new HostGroups.

5.1.12.2. Storage Cluster

The Storage Cluster for which the Port Group will be configured.

5.1.12.3. Port Pairs

The Port Pairs which belongs to the Port Groups. A Port Pair could only be used once on a Storage Cluster. If there are no more free Port Pairs, this List is empty. You must delete some Port Groups, to free up already used Port Pairs, if you want to reconfigure it.

5.1.13. Groups

Groups are for restricting the selection of possible DPV-Config-Templates for certain Servers/Clusers. All assigned Clusters of a Group will only see the assigned DPV-Config-Templates.

Create new Group

5.1.14. Cost Centers

Cost Centers are used in the Cost Center Chargeback Report. Here you can configure, which Servers/Clusters belongs to a Cost Center.

Create new Cost Center

5.1.15. Sites

Sites are used to Configure Servers/Clusters and Storage Arrays. A proper configuration ensures that the ‘Non Preferred Path Bit’ or the ALUA configuration is set correctly when new LUNs are provisioned.

Create new Site

5.1.16. Resync GADs

With this operation, all GAD replications could be resynced at once. This is handy, if a GAD failure occurred. If started, a wizzard-dialogue appears which will guide you through the whole operation.

Resync GADs

5.1.17. GAD Restore Repl Dir

With this operation, all GAD replications could be restored to its initial direction at once. This is handy, if a GAD failure occurred. If started, a wizzard-dialogue appears which will guide you through the whole operation.

Restore GAD-Replication Directions

5.1.18. Maintenance Mode

If Maintenance Mode is enabled, the Array Management functionality is not available anymore. This is handy, if you want to prevent changes are made by an operator during maintenance.

Maintenance Mode

5.1.19. Reset Task Queues

This operation will reset all task queues instantly. Already running tasks will stop immediately. Additionally, pending locks will be reseted.

5.2. Defining Rules

5.2.1. Overview

On of the main advantages of SAM4H is its rule based management function. This means, that a storage admin can define standard rules, which are applied when the storage management is used. Thanks to the rules, the configuration follows the defined standards and looks everywhere equal.

5.2.2. DP-Vol Config Templates

DP-Vol Config Templates are rules, which define how a new DP-Vol Config Templates has to be created. It defines which CUs are used, which sizes can be selected and from which pools a DP-Vol Config Templates will be created from. It consists also the information if and how a DP-Vol has to be mirrored.

DP-Vol Config Templates can be configured in the Admin-Menu (see chapter DP-Vol Templates in the section Administration).

5.2.3. Host-Group Templates

Host-Group Templates are used to predefine configurations for creating Host Groups. You can define, the Host Mode and the Host Mode Options.

Host-Group Template can be configured in the Admin-Menu (see chapter Host-Group Template in the section Administration).

5.3. Array Management

Array Management is the menu to configure all storage related things. This is the main menu for storage operators.

5.3.1. Main View

In the main view of Array Management you see the array management menu and all executed, running and pending tasks:

Array Management

5.3.1.1. successful

sucessfull

5.3.1.2. Pending

pending

This task is in the queue and will start when other tasks in the queue are finished.

5.3.1.3. Acquire Lock

acquire lock

The task is waiting for a lock.

5.3.1.4. Error

error

The task had an error. Error details are written in red next to the task description.

5.3.1.5. Running

running

This task is executing right now.

5.3.1.6. Rollback pending

rollback pending

This task is queued for rollback.

5.3.1.7. Rollback executed

rollback executed

This task was rollbacked successfully.

5.3.1.8. Rollback failed

rollback failed

This task had an error while it was rollbacked

5.3.2. Create (and map) LUNs

In this menu you will create new DP-Vols. The menu looks like the following picture:

Create (and map) Luns

You will need to select the following parameters to create and map a new DP-Vol.:

Cluster

Select one or more clusters for which the DP-Vol will be created. If you do not change the advanced settings, all created DP-Vols will be mapped to all HSDs of the of the selected clusters which belongs to the selected Storage Cluster.

Storage Cluster

If a Cluster has HSDs from multiple Storage Clusters, you have the select one. If the Cluster only has one Storage Cluster, it will be selected automatically (as shown in the picture above). When there are more than one Clusters selected, only Storage Clusters are shown, which are for all selected Clusters.

Config Template

Select the Config Template which defines how the DP-Vol will be created (see section Defining Rules). Only Config Templates are displayed, which has Pools from the selected Storage Cluster.

Replication Direction

If a Config Template defines replication, you have to select the replication direction. However, if you configured ‘auto_replication_direction = true’ in ‘config.yml’ (see section ‘auto_replication_direction’ in chapter ‘configuration’) the replication direction is determined automatically.

Size

Size defines the block size of the DP-Vol. DP-Vol-Sizes can be configured in the admin menu (see section ‘DP-Vol-Sizes’ in the chapter ‘Administration’)

Amount

The amount of DP-Vols which will be created

5.3.2.1. Advanced Options

This dialogue is hidden when you access the menu ‘create new DP-Vols’. To show it, simply click on the link ‘Advanced options’. A dialogue shown in the following picture appears:

Create (and map) Luns Advanced Options

The following parameters can be configured in the ‘advanced options’ dialogue:

Map?

If set to no, the new DP-Vols will only be created and not mapped.

Explicit LUN-Nr.

Set an explicit start Lun-Nr. for the mapping. E.g.: If you create 3 new DP-Vols and you set the Explicit Lun-Nr. to 10, then the new DP-Vols will be mapped to Lun-ID 10,11 and 12. If you leave this field blank, the next 3 free continuous LUN-IDs will be taken.

Map to Host Groups

Deselect the Host Groups to which you do not want the new DP-Vols mapped. This is only relevant, if you set the Map?-value to ‘yes’.

5.3.3. Map LUNs

This menu is for mapping existing LUNs (DP-Vols and LDEVs) to a cluster. The menu looks like the following picture:

Map LUNs

5.3.4. Unmap LUNs

This menu is for unmapping LUNs from a cluster. Due to safety reasons, unmapping is not done as a cluster operation. This means, that you need to unmap every storage array individually. The dialogue looks like the following picture:

Unmap LUNs

You will need to select the following parameters to unmap a LUN from a storage array:

5.3.5. Cluster

Select a cluster from which you want to unmap LUNs.

5.3.6. Storage Array

The storage array where you want to unmap LUNs from.

5.3.6.1. LUNs

All LUNs which are mapped from the selected storage array to the selected cluster. Select the LUNs to unmap.

5.3.7. Expand DP-Vols

This menu is for resizing DP-Vols. If the selected DP-Vol is from a storage cluster, both DP-Vols will be resized at the same time. If the DP-Vol is replicated, the mirror will be splitted, resized and replicated again. The dialogue looks like the following picture:

Expand DP-Vols

You will need to select the following parameters to resize a DP-Vol:

Cluster

Select the cluster from which you want to resize LUNs.

Storage Cluster

If a Cluster has Host Groups from multiple Storage Clusters, you have to select one. If the Cluster only has one Storage Cluster, it will be selected automatically (as shown in the picture above). When there are more than one Clusters selected, only Storage Clusters are shown, which are for all selected Clusters.

DP-Vols

The DP-Vols you want to resize. If you select multiple DP-Vols, all of them will be resized by the amount of additional capacity specified in the field ‘Additional Space’.

Size

The target size of the selected LUNs.

5.3.8. Delete LUNs

Use this action for either deleting unmapped LUNs or for unmapping LUNs and delete them in one step. For safety reasons, this action could only be executed on one StorageArray and non on StorageClusters.

5.3.8.1. Delete unused LUNs

When deleting unused DP-Vols. The dialogue looks like the following picture:

Delete LUNs

Storage Array

Select the storage array from which you want to delete LUNs.

Unused DP-Vols

The DP-Vols to delete. Only unmapped DP-Vols are displayed.

5.3.9. Auto Unmap

If you choose to unmap and delete in one step, The dialogue looks like the following picture:

Delete LUNs

You will need to change the following parameters to delete a LUN (depending on the chosen action, not all parameters must are displayed):

Cluster

Select a cluster from which you want to unmap and delete the LUNs.

Storage Array

Select the storage array from which you want to delete LUNs.

DP-Vols

The DP-Vols to delete. Only DP-Vols which are mapped on the selected Cluster are displayed.

5.3.10. Create Hostgroup

This menu is for creating a new HSD. You can choose between Create a new server/cluster or Add hostgroup(s) to a server/cluster

Create Host Group

5.3.10.1. Create new server / cluster

_images/hostgroup_create_new_server_cluster.png

The following parameters must be specified:

Name

The name of the new Hostgroup.

Description

An optional short description of the Hostgroup. It will be included in the generated report.

Asset Nr.

An optional asset number of the Hostgroup.

Cost Center

The coast center which will be charged.

Storage Cluster

The Storage Cluster, where the new HSD will be created for.

Host Group Config Template

The template specifies which host mode and which host mode options will be used for creating the HSD. See section Host Group Config Templates’ in chapter ‘Administration’ for details.

Port Groups

The ports for the HSDs. There will be one HSD per port for each storage array created.

WWNs

Assign the accessible WWN to the appropriate port group.

5.3.10.2. Add hostgroup(s) to a server/cluster

_images/add_hostgroups_to_a_server_cluster.png

The following parameters must be specified:

Cluster

Select the cluster you want to add the hostgroup to.

storage cluster

The Storage Cluster, where the new HSD will be created for.

Host Group Config Template

The template specifies which host mode and which host mode options will be used for creating the HSD. See section Host Group Config Templates’ in chapter ‘Administration’ for details.

Port Groups

The ports for the HSDs. There will be one HSD per port for each storage array created.

WWNs

Assign the accessible WWN to the appropriate port group.

5.3.11. Create Replications

This menu is for replicating two existing LUNs. The dialogue looks like the following picture:

Create Replications

The following parameters must be specified:

Cluster

Select the cluster for which you want to create a replication.

Storage Cluster

If a Cluster has HSDs from multiple Storage Clusters, you have the select one. If the Cluster only has one Storage Cluster, it will be selected automatically (as shown in the picture above). When there are more than one Clusters selected, only Storage Clusters are shown, which are for all selected Clusters.

Config Template

Select the Config Template which defines how the LUNs will be replicated (GAD, TrueCopy)

Replication Direction

Select the replication direction. If you configured ‘auto_replication_direction = true’ in ‘config.yml’ (see section ‘auto_replication_direction’ in chapter ‘configuration’) the replication direction is determined automatically.

Unmirrored LUNs

Select the LUNs which you want to replicate.

5.3.12. Split Replications

This menu is for splitting existing replications. The dialogue looks like the following picture:

Split Replications

The following parameters must be specified:

Cluster

Select the cluster for which you want to split replications.

Replications

Select the replications, which you want to split.

Simplex

Split simplex or suspend.

Reload Config

This dialogue is for reloading the configuration from the storage arrays.

TODO Describe what the difference between Fast and Detailed is.

5.3.13. Create Snapshot

Create Snapshot

5.3.14. Takeover Replications

Takeover Replication

5.3.15. Resync Replications

Resync Replications

5.4. Reports

5.4.1. Cluster LUN Report

This report displays an overview of the mapped LUNs on a Server / Cluster. It is divided into 4 sections:
  • Summary, which gives an overview of the mapped LUNs

  • Timeline, which displays the capacity growth over time

  • WWNs, which must be expanded by clicking on the title and gives information about the configured WWNs, Ports and Host-Mode-Options

  • LUN Table, which displays information about every mapped LUN

The columns of the LUN Table is configurable with the parameter cluster_lun_report_columns in the file config/config.yml (see section configuration).

5.4.2. Pool Report

The Pool Report displays information about all Pools an a storage cluster. It displays the overrpovisioning numbers and gives an overview of the amount of free logical capacity in the pool. The releasable capacity are LUNs, which have materialized space, but are not mapped to any hostgroup.

5.4.3. Pool Capacities Table

This report gives a nice overview of alle Pools from all storage arrays. It displays the most important capacity numbers.

5.4.4. GAD Report

The GAD Report is designed as a drill down report, to identify GAD-Replications, which are not paired. The first stage is an overview of all Storage Clusters. With a click on the storage cluster name, the second stage is displayd which gives an overview of all servers / clusters. The servers, which have unpaired GAD-Replications are always displayd on top.

5.4.5. Port Assignment Report

This report gives an overview about the ports on a storage cluster and where each server is configured.

5.4.6. Cost Center Chargeback Report

Servers / clusters could be assigned to a cost center. This is done either when a new server is created by SAM4H or under Administration / Servers/Clusters. Once the servers are assigned to a cost center, the numbers are aggregated for each cost center and displayed in the cost center chargeback report. There exists also the option to specify prices for each pool / tier under Administration / Pools.