Hitachi cci download

The audit logs for embedded CCI are created when the SSH connection is opened or closed and when raidcom commands are used. The audit logs are stored in the storage system on the GUM processor. You can use the embedded CCI audit logs to identify the user client who executed a raidcom command. To identify the user client who executed an embedded CCI command:.

The following table lists and describes the error messages displayed when session errors occur in raidcom commands. For details about other error messages returned by raidcom commands, see the Command Control Interface User and Reference Guide.

This command cannot be executed in this session. Check if storage system is ready and log in again. About embedded CCI. Note This document describes and provides instructions for using the embedded CCI software. For details about the raidcom commands for example, syntax, options and parameters, output, examples , see the Command Control Interface Command Reference.

For details about provisioning operations, see the Provisioning Guide. Supported commands. Note The help command raidcom -h displays all of the raidcom command options, including the options not supported by embedded CCI. Shows the return value of the raidcom command. Notes and restrictions for raidcom commands.

The connection between embedded CCI and the storage system is disconnected when no raidcom command is issued for 60 minutes. To run raidcom commands after the timeout, you must disconnect and then make the SSH connection. The asynchronous command results are deleted when the SSH client is disconnected or when the timeout occurs. User-defined script files cannot be created in an embedded CCI environment.

If you want to use script files, use host-based CCI. Parameter ranges for CCI options. Troubleshooting with Command Control Interface. Wait a while, and then retry the operation. External volume for which the Data Direct Mapping attribute is enabled.

Normal volume for which accelerated compression is enabled. You have reached the maximum number of pairs that can be created for a consistency group. A pair that uses the same P-VOL is assigned to the specified consistency group.

You have specified a snapshot group which has reached the maximum number of pairs allowed in a group. A pair that uses the same P-VOL exists already in the specified snapshot group. You have specified a pool that does not exist. The volume is specified reservation attribute of a global-active device.

FF58 pairsplit, pairresync, pairresync -restore The command ended abnormally because the specified pair is a cascaded pair. FF72 paircreate, pairsplit, pairresync, pairresync -restore The Thin Image pair task failed because a snapshot tree is being deleted.

Notes on storing snapshot data, and on cloning pairs. Pair task. CCI command. HDvM - SN. Create pair. Create and split pair. Normal Copy. Reverse Copy. Delete pair. Assign an S-VOL to snapshot data. Cause of error. You cannot create a pair with the SLU attribute because a volume with the SLU attribute has been specified as a secondary volume.

You cannot create a pair because a volume with the ALU attribute has been specified as a primary volume or a secondary volume. You cannot operate on the specified volume because it is not the root volume of the Thin Image pair. You cannot perform the operation because there is an unsupported microcode version of the MP processor in the storage system. You cannot perform the operation because the storage system is in internal process, or the configuration changing processes are conflicting.

You cannot perform the operation because the local replication pair is being initialized. All commands. The execution status of the snapshot garbage data deletion processing defragmentation processing of the specified root volume is not in an operable status.

The command ended abnormally because shared memory Base is not added. The command ended abnormally because shared memory Base or greater is not added. You cannot restore the HTI pair because of one of the following reasons: You are storing snapshot data for the HTI pair that you want to restore using the consistency group to which the pair is assigned. You cannot create the HTI pair because of one of the following reasons: You were in the process of creating a new snapshot group but you reached the maximum number of snapshot groups that can be created.

If appropriate, you can use existing storage system resources, for example, Dynamic Provisioning pools and DP-VOLs that have already been created. Resource groups are created in the secondary storage system using the primary storage system's serial number and model as virtual information, so that the P-VOL and S-VOL of each pair share the same virtual storage machine information. A virtual storage machine is composed of multiple resource groups that have the same virtual information.

When you create a resource group and specify the virtual serial number and model, the resource group is registered in the virtual storage machine. If the virtual storage machine does not already exist in the storage system, it is created automatically when the resource group is created. The following illustration shows the creation of a resource group when the P-VOL is not already registered to a virtual storage machine.

Specify the primary storage system's serial number and model for the virtual storage machine you are creating on the secondary storage system. Display the information about the resource groups of the secondary storage system.

Information about all resource groups is displayed. Confirm the resource group name, resource group ID, virtual serial number, and virtual model. You can create GAD pairs using volumes in virtual storage machines. Specify the serial number and model of the virtual storage machine to which the P-VOL is registered for the virtual storage machine you are creating on the secondary storage system.

Command for the sample configuration shown above:. Display information about the host group that is set to port CL1-C. Confirm that the port name, host group ID, and host group name are correct. As shown in this example, the host groups with host group ID 0 to 5 are reserved in resource group 1.

Actual volumes are defined for the host groups with host group ID 0 and 1. The host groups with host group ID 2 to 5 are reserved in the resource group, but actual volumes are not defined for them.

The host groups with host group ID 6 to are not displayed, because they are not reserved in resource group 1. In the newly created resource group, you will reserve an LDEV ID so that the volume is available to become the target volume of a global-active device pair.

The host group whose host group ID is 0 exists by default. Set a host mode to the host group Windows host mode shown , as follows:. Check command and output examples: Display the information about the host group that is set for the port CL1-C , and confirm that the host mode is correct.

A host group whose host group ID is 1 or higher does not exist by default. If you connect multiple server hosts of different platforms to a port, create a host group for each platform.

Set the host mode for the new host group Windows host mode shown. Display the information about the host group that is set for port CL1-C. After creating host groups, you must create a pool volume, format the volume, and create a Dynamic Provisioning pool. The capacity is GB.

Confirm that the new volume satisfies the following requirements:. Seeing examples of configuration definition files can help you when you edit your own configuration definition files. You must shut down both CCI instances before editing the configuration definition files. The following examples show the configuration definition files for a Windows host. The following information is important to know as you edit configuration definition files:. For example, for serial number , enter For VSP Gx00 models, specify the six-digit serial number that begins with 4 as is for example, The underlined lines below show the updates for the volumes in the sample configuration in this chapter.

Make sure to enter the information for your system in your configuration definition files. After editing the configuration definition files, restart both CCI instances. Before creating a GAD pair, check that the same virtual LDEV ID as that of the primary volume does not exist in the virtual storage machine of the secondary site, which has the same serial number and model as the primary storage system. Check that the same virtual LDEV ID as that of the primary volume does not exist in the virtual storage machine of the secondary site.

If the same virtual LDEV ID as the primary volume is displayed for the virtual storage machine of the secondary site, there might be errors in the GAD system implementation plan. Revise the system configuration. Check whether the same virtual LDEV ID as that of the primary volume is assigned to the virtual storage machine of the secondary site. Therefore, the user of the virtual storage machine does not have access authority.

To specify the preferred path in a cross-path configuration, you must enable the ALUA mode. To register GAD pairs to a consistency group, specify the -fg option when creating the pair.

If you create a pair and do not specify a consistency group ID, the ID for an unused consistency group in the storage system will be automatically assigned. The following example shows a command used to create a GAD pair without registering the pair to a consistency group:. Confirm that a GAD pair is created. Add an alternate path to the S-VOL on the host using the alternate path software. For some alternate path software the alternate path is added automatically.

Make sure that the host has recognized the GAD secondary volume correctly. In a cross-path configuration, if the ALUA mode is enabled for the first time, all paths including cross paths between a server and a storage system are set as the preferred path. Therefore, you need to set the asymmetric access status of the cross path as a nonpreferred path. By doing so, paths between the server and the storage system in the primary site and between the server and the storage system in the secondary site can be preferably used.

If differential data management fails due to insufficient pool capacity, you must release the differential data pages managed in the pool. Make sure that system option mode is set to OFF.

When system option mode is set to ON, you cannot reclaim zero pages. For details about setting system option modes, contact your Hitachi Vantara Corporation representative. Restore the blocked pool. For details, see the Provisioning Guide for the storage system. Release the V-VOL pages using the raidcom modify ldev command.

Releasing pages might take some time. Global-active device system configuration. Primary storage system settings. Secondary storage system settings. CCI server configuration. CCI instances and configuration definition files Instance number Configuration definition files Usage 0 horcm0.

External storage system settings. Workflow for creating a GAD environment. You can also issue GAD commands using the out-of-band method. Initial state. Adding the external storage system for the quorum disk. Verifying the physical data paths.

Creating the command devices. Creating the configuration definition files. HORCM file for the primary storage system: horcm0.