Sessions and instances for embedded CCI

Virtual Storage Platform One Block Administrator User Guide

Version

A3-02-2x

Audience

anonymous

Part Number

MK-23VSP1B001-00

User sessions

An embedded CCI user session is started when the SSH connection to the ESM processor is successfully established. If the session fails to start (because the SSH connection did not succeed), the raidcom command returns the [EX_ESNRDY] error message. If you run a raidcom command after the session has ended, the [EX_ESSINV] error message is returned.

The user session is ended when any of the following events occurs:

The SSH connection is disconnected.
The session times out (no raidcom command is issued for 60 minutes).
The storage system is rebooted.

Instances

Embedded CCI does not use instance numbers. An error occurs when an instance with an instance number is specified.

The startup and shutdown of instances are automatic. The following table lists the triggers for starting and stopping embedded CCI instances.

Start/Stop	Trigger
Instance Start	When the ESM processor is booted, the embedded CCI instance starts. If you issue a raidcom command while the instance is not yet started, the [EX_ATTHOR] error message is returned. If the ESM processor fails to boot, an instance retries to start every 10 minutes.
Instance Stop	When the ESM processor is turned off, the embedded CCI instance ends.
Instance Restart	When the internal address of the ESM processor is changed, the embedded CCI instance restarts.

Start/Stop

Trigger

Instance Start

When the ESM processor is booted, the embedded CCI instance starts.

If you issue a raidcom command while the instance is not yet started, the [EX_ATTHOR] error message is returned.

If the ESM processor fails to boot, an instance retries to start every 10 minutes.

Instance Stop

When the ESM processor is turned off, the embedded CCI instance ends.

Instance Restart

When the internal address of the ESM processor is changed, the embedded CCI instance restarts.

Note: The configuration definition file (HORCM file) for embedded CCI is created automatically on the ESM processor when an instance starts. You do not need to create the configuration definition file, and you cannot edit the file.