0% found this document useful (0 votes)
429 views

HP Sssu Commands

This document provides instructions for using various commands in the HP EVA SSSU (Storage System Simple Utility) interface. It describes how to log in, search for arrays, capture configurations, add folders, hosts, systems, containers, virtual disks, copies, LUNs, disk groups, and data replication groups using related commands. Options for each command are also outlined.

Uploaded by

pega_001
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
429 views

HP Sssu Commands

This document provides instructions for using various commands in the HP EVA SSSU (Storage System Simple Utility) interface. It describes how to log in, search for arrays, capture configurations, add folders, hosts, systems, containers, virtual disks, copies, LUNs, disk groups, and data replication groups using related commands. Options for each command are also outlined.

Uploaded by

pega_001
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

HP EVA SSSU Commands

Compiled by Jeffrey Leung

Logging into the SSSU:

When opening the SSSU program, you will be asked to enter the following information:
• Manager – Server name or IP of management server. If already logged in, use
“localhost”
• Username – HP Command View EVA account
• Password – HP Command View EVA password

To search for the list of manageable arrays, use the LS SYSTEM command. Then select
a system by using the SELECT SYSTEM system_name command.

Capturing the Configuration:

CAPTURE CONFIGURATION file_name

The CAPTURE CONFIGURATION command enables you to capture, save, and re-
create an array configuration by querying the selected array and generating up to five
scripts. Not all arrays require all five scripts. You can use these scripts to re-create the
original configuration, and in some cases, to assist in recovery. HP recommends that
you run the CAPTURE CONFIGURATION command after you initialize an array to save
a copy of the configuration.

To add a folder:

ADD FOLDER folder_name


You can only create folders under the Virtual Disks and Hosts root folders. You cannot
create root folders.

Options:

COMMENT=

Example:
In this example, the new folder is created under the Virtual Disks root folder.

To add a host:

ADD HOST host_name WORLD_WIDE_NAME= FCA-WWN

The ADD HOST command adds a host and its WWN to the list of hosts that can connect
to virtual disks in the current array.
The ADD HOST command adds one Fibre Channel adapter only. Use the SET HOST
command to add each subsequent FCA.

Options:

COMMENT=
IP=
• The network IP address, if not specified the name of the host is used as a DNS
name
OPERATIONG_SYSTEM=
• Operating system of the specified host
o HPUX
o IBMAIX
LINUX
o
OPEN_VMS
o
SOLARIS
o
TRU64
o
UNKNOWN
o
WINDOWS
o
WINDOWSLH
o
CUSTOM= (You must include the equal sign after CUSTOM and the
o
value must be 16-digit hexadecimal characters)
WORLD_WIDE_NAME=
• The WWN of the FCA

Example:
In this example, “dummyhost” is created with a WWN of 5000_1fe1_ff00_0000.

To add a system:
ADD SYSTEM system_name

ADD SYSTEM command initializes an array and creates a default disk group. An
uninitialized array must be selected before using ADD SYSTEM.

Use the LS SYSTEM command to display a list of uninitialized arrays.

Use the SELECT SYSTEM command to reselect the array after it has been initialized.

Options:

COMMENT=
CONSOLE_LUN_ID=
• The LUN used for console communication after array creation. If set to zero, no
console LUN is presented to the host.
DEVICE_COUNT=
• The number of physical disks to use for this group. The limit is the number of
available disks in the array. The default and minimum value is 8.
DISKGROUP_DISKTYPE=
• Determines the types of disks to be considered for creating the disk group.
o Online – only online fibre channel disks are considered for creating the
default disk group.
o Near_online – only near-online fibre channel disks are considered for
creating the default disk group.
SPARE_POLICY=
• Determines the amount of storage space, if any, set aside for use in the event
that disks fail. It is the equivalent amount of storage space spread across all
disks.
o None – reserves no space within a disk group to allow for data
reconstruction in case of a disk failure. Can cause data loss and is not
recommended
o Single – reserves space within a disk group to allow for data
reconstruction in case of failure of one disk drive.
o Double – reserves space within a disk group to allow for data
reconstruction in case of a failure of two disk drives

Example: Create the initialized array payroll with 12 physical disks and a spare policy of
single:
• ADD SYSTEM payroll DEVICE_COUNT=12 SPARE_POLICY=single

To add a container:
ADD CONTAINER container_name

Options:

DISK_GROUP=
• Name of disk group you want to create container in.
REDUNDANCY=
• Vraid0
• Vraid1 (default)
• Vraid5
SIZE=
• Size in GB.

To add a virtual disk:

ADD VDISK vdisk_name SIZE= vdisk_size

Options:
COMMENT=
• Associates a user-defined comment with the vdisk.
DISK_GROUP=
• The disk group in which you want to create the vdisk.
MIRRORCACHE=
• Mirrored - cache is mirrored between both controllers (default).
• Notmirrored - not mirrored.
NOPREFERRED_PATH
• Allows either controller to handle I/O (default).
NOREAD_CACHE
• Reads are always performed by the physical disks, not the controller’s cache.
NO_WAIT_FOR_COMPLETION
• Does not wait for the command to finish before displaying the utility command
prompt or running another command or script.
NOWRITE_PROTECT
• Allows writing to the vdisk from all presented LUNs and hosts (default).
OS_UNIT_ID=
• The ID presented to the host operating system. If set to zero, no ID is presented
to the host. This option is used for IBM AIX (set to 0), OpenVMS (required), and
Tru64 UNIX (recommended). Other host operating systems ignore this option.
PREFERRED_PATH=
• Path_A_Both
• Path_A_Failover
• Path_B_Both
• Path_B_Failover
READ_CACHE
• Reads are performed by the controller’s cache
REDUNDANCY=
• Vraid0
• Vraid1 (default)
• Vraid5
SIZE=
• Size in GB.
WAIT_FOR_COMPLETION
• Waits for the command to finish before displaying the utility command prompt or
running another command or script. For vdisks larger than 1 TB, using this option
can result in a long waiting period.
WORLD_WIDE_LUN_NAME=
• World wide LUN name of the vdisk.
WRITECACHE=
• Writethrough – operation completes when the data is written to the disk.
• Writeback – operation completes when the data is written to cache (default).
WRITE_PROECT
• Does not allow writing to the virtual disk from all presented LUNs and hosts.

Example:
In the example, “examplevdisk1” is created under the new folder created earlier.
The virtual disk is 1GB in size with RAID5 redundancy. The WAIT FOR COMPLETION
option is added at the end to finish creating the virtual disk before moving on when
running a script.

To create a vdisk copy:


ADD COPY copy_name VDISK= vdisk_name

Options:

CONTAINER=
• Name of container to be used for copy, must already exist.
DISK_GROUP=
• Name of disk group to create copy in, must already exist.
NOWAIT_FOR_COMPLETION
• Does not wait for command to finish before running another command or script.
OS_UNIT_ID=
REDUNDANCY=
• Vraid0
• Vraid1 (default)
• Vraid5
VDISK=
• Name of vdisk to be copied.
WAIT_FOR_COMPLETION
• Waits for command to finish before running another command or script.
WORLD_WIDE_LUN_NAME=
• The world wide LUN name of the vdisk.

Example:
Create a copy of payroll named wednesday_nite:
• ADD COPY wednesday_nite VDISK=”\Virtual Disks\payroll”
Create a copy of daily_biz named save_reports within the specified disk group:
• ADD COPY save_reports VDISK=”\Virtual Disks\daily_biz” DISK_GROUP=”\Disk
Groups\small_disks”

To add a LUN:

ADD LUN LUN_number HOST= host_name VDISK= vdisk_name

Example:
In this example, “examplevdisk1” is presented to “dummyhost” created earlier
and assigned LUN # 199.

To add a disk group:


ADD DISK_GROUP group_name

Options:

COMMENT=
DEVICE_COUNT=
• The number of physical disks to use for this group. Default minimum value of 8,
maximum is number of available disks in the array.
DISKGROUP_DISKTYPE=
• Determines the types of disks to be considered for creating the disk group.
Default value is online.
• Online – only fibre channel disks are considered for creating the default disk
group.
• Near-online – only near-online fibre channel disksa re considered for creating the
default disk group
OCCUPANCY_ALARM=
• The point when a defined percentage of space is used. When the point is
reached, an event is sent to the host or management server. Do not use % sign
after the number, default value is 95.
SPARE_POLICY=
• The amount of storage space set aside for use incase disks fail.
o None – reserves no space
o Single – reserves space for one disk drive failure (default)
o Double – reserves space for two disk drive failures

Example:
Create a new disk group, human_resources. It has 12 physical disks with one disk set
aside as a spare, and sends an event to the array when 75% capacity is reached.
• ADD DISK_GROUP “\Disk Groups\human_resources” DEVICE_COUNT=12
SPARE_POLICY=single OCCUPANCY_ALARM=75

To add a data replication group:


ADD DR_GROUP dr_group_name VDISK= vdisk_name DESTINATION_SYSTEM=
detination_array_name

Options:

ACCESSMODE=
• Access rights for a connected hosts. Default is disable, which is recommended
setting. In the user interface, the disable setting displays as none.
o presentonly
o readonly
o disable
COMMENT=
DESINTATION_DISK_GROUP=
• The disk group in which the virtual disk on the destination array is created.
DESTINATION_SYSTEM=
• The destination array on which the virtual disk is created.
DESTINATION_VDISK_NAME=
• The name of the virtual disk created on the destination array.
LINK_DOWN_AUTOSUSPEND=
• When enabled, DR group replication is automatically suspended if the link
between the arrays goes down. Replication remains suspended even if the link is
active again.
o enable
o disable
LOG_DESTINATION_DISK_GROUP=
• The disk group for the DR log disk on the destination array.
LOG_SOURCE_DISK_GROUP=
• The disk group for the DR log on the source array.
MAX_LOG_SIZE=
• The maximum size of the DR log disk. Value must be between 136 MB and
2097511 MB and entered in blocks of 512 bytes (278528 through 42949672965).
If left blank or set to 0, the controller software calculates the optimum log size for
the available space.
TARGETREDUNDANCY=
• Redundancy level of the virtual disk being created on the destination array.
VDISK=
• The name of the source virtual disk being added to the DR group.
WRITEMODE=
• The I/O interaction between the destination and the source.
o synchronus (default)
o asynchronus

Example:
The following example creates a DR group named Transactions that contains the source
virtual disk \Virtual Disks\Hawaii. This DR group will connect to the destination array
remote_scell, on which the destination virtual disk \Virtual Disks\Hawaii (same as the
source by default) is created and added to the destination DR group.
• ADD DR_GROUP Transactions DESTINATION_SYSTEM=remote_scell
VDISK=”\Virtual Disks\Hawaii”

To add an iSCSI controller:


ADD ISCSI_CONTROLLER

Options:

IP=
• IP address of an iSCSI controller or enter auto for automatic discovery

To add an iSCSI host:


ADD ISCSI_HOST iscsi_host_name ISCSO_IPHOST= iscsi_IP_host_name

Options:

COMMENT=
OPERATING_SYSTEM=
• HPUX
• LINUX (if using Mac OS X, select this)
• OPEN_VMS
• OTHER
• SOLARIS
• VMWARE
• WINDOWS

Example:
Add the iSCSI host named development with the iSCSI IP host named iqn.1991-
05.com.microsoft:aittest5.americas.mycompany.net:
• ADD ISCSI_HOST \Hosts\development ISCSI_IPHOST=iqn.1991-
05.com.microsoft:aittest5.americas.mycompany.net

To add iSCSI LUN:


ADD ISCSI_LUN VDISK= vdisk_name ISCSI_HOST= iSCSI_host_name

Example:
Present the payroll virtual disk to the iSCSI host development:
• ADD ISCSI_LUN VDISK=”\Virtual Disks\payroll” ISCSI_HOST=development

To add a mirror clone:

ADD MIRRORCLONE mirrorclone_name VDISK= vdisk_name CONTAINER=


container_name

ADD MIRRORCLONE command creates a copy of a source virtual disk. The mirror
clone can remain synchronized with the virtual disk or you can fracture the link to create
a point-in-time copy.

Example:
Create the mirrorclone test2 from the virtual disk payroll:
• ADD MIRRORCLONE test2 VDISK=”\Virtual Disks\payroll”
CONTAINER=container1

To add a multi snap:

ADD MULTISNAP snapname VDISK= source_vdisk_name CONTAINER=


container_name SNAPSHOT|SNAPCLONE snapname VDISK= source_vdisk_name
CONTAINER= container_name SNAPSHOT|SNAPCLONE snapname VDISK=
source_vdisk_name CONTAINER= container_name SNAPSHOT|SNAPCLONE
snapname …

Example:
Create a snapshot of the virtual disk payroll and snapclone of the virtual disk hrd and
finance:
• ADD MULTISNAP tonightsnap VDISK=”\Virtual Disks\payroll”
CONTAINER=container1 SNAPSHOT hrdkp VDISK=”\Virtual Disks\hrd”
CONTAINER=container2 SNAPCLONE financebkp VDISK=”\Virtual
Disks\finance” CONTAINER=container3 SNAPCLONE

To add a snapshot:
ADD SNAPSHOT snapshot_name VDISK= source_vdisk_name

ADD SNAPSHOT creates a dependent, point-in-time copy of a virtual disk. It is


dependent because data is not copied to the snapshot until it is overwritten on the
source.
• To delete snapshots, use the DELETE VDISK command
Options:

ALLOCATION_POLICY=
• Indicates how the space for the snapshot is to be allocated.
o Demand – array allocates only enough space to store the metadata and
pointers to the source data. As the source is overwritten, the array
allocates more space and copies the original data to the snapshot.
o Fully – the array allocates space equal to the capacity of the source
virtual disk, plus space for metadata and pointers to the source data. As
the source is overwritten, the array copies the original data to the
snapshot.
CONTAINER=
OS_UNIT_ID=
REDUNDANCY=
• If not specified, the default is the same as the source virtual disk
VDISK=
WORLD_WIDE_LUN_NAME=
Example:
Create the snapshot payroll_backup from the virtual disk payroll that uses capacity only
as needed:
• ADD SNAPSHOT payroll_backup VDISK=”\Virtual Disks\payroll”
ALLOCATION_POLICY=demand
Create the snapshot wed_night_biz from the virtual disk daily_biz while reserving all
capacity required to create the snapshot:
• ADD SNAPSHOT wed_nite_biz VDISK=daily_biz ALLOCATION_POLICY=fully

You might also like