Lab Guide for

Managing Hitachi Ops Center Administrator

TSI2929

Courseware Version: 5.3

Microcode Version: Hitachi Ops Center Administrator 10.5.0.00
Table of Contents

Lab 1 Overview……………………………………………………………..……..………………… 1-1

Lab 2 Administrator Installation (Optional) …………………….……..………………….……… 2-1
Lab 3 Resources Discovery………………………..……………………………………………… 3-1
Lab 4 Configuration Part 1………………………………………………………………………… 4-1
Lab 5 Configuration Part 2………………………………………………………………………… 5-1
Lab 6 Migration and Protection …………………………………………………………………… 6-1
Lab 7 Multipathing Management ……………….………………………………………………… 7-1
Lab 8 Adaptive Data Reduction (ADR) ..………………………………………………………… 8-1
Lab 9 Administer and Monitor …………………………………………………………………..… 9-1
Lab 10 Command Line Interface (CLI) ……………………………………………………………. 10-1

Hitachi Vantara
Corporate Headquarters Regional Contact Information
2535 Augustine Drive Americas: +1 866 374 5822 or [email protected]
Santa Clara, CA 95054 USA Europe, Middle East and Africa: +44 (0) 1753 618000 or [email protected]
www.HitachiVantara.com | community.HitachiVantara.com Asia Pacific: +852 3189 7900 or [email protected]

© Hitachi Vantara LLC 2021. All rights reserved. HITACHI is a trademark or registered trademark of Hitachi, Ltd. VSP is trademarks or registered trademarks of
Hitachi Vantara Corporation. All other trademarks, service marks and company names are properties of their respective owners.

L-ii
Lab 1: Overview

Objective
In this lab, you will discover Hitachi Ops Center Administrator GUI.
Time Allocated: 30 Minutes

Activities
• Activity 1: Navigate and Familiarize With Administrator GUI
• Activity 2: Review the Administrator Settings and Execute the Tasks

Resources
• Ops Center 10.5.x Documentation Library (Ops Center Administrator User Guide)

Important

• Pictures and screenshots are here for explanation purposes only. Therefore, Server IP Address,
Pools, LDEV ID, and other Storage systems or Servers details must be taken as an example.
• The instructor will provide lab environment details including:
o IP address of Ops Center Administrator

1-1
Lab 1: Overview

Activity 1 Navigate and Familiarize With Administrator GUI

In this activity, you will navigate Ops Center Administrator GUI and familiarize yourself with it.
1.1 Using your browser, open a new window to Administrator URL.

https://Administrator_IP_address:port

1.2 On the Dashboard, check if any resource is available in the Resource side panel. And verify if
any alert is shown in the Alert tiles.
1.3 Select the Jobs tab and examine the jobs activities, if any.

1.4 Further down in the center of the Dashboard, check out the different tabs for Tiers,
Protection and Savings and see if any values are available.

1-2
 Lab 1: Overview

1.5 When storage system is in the inventory, you would be able to hover on each tier and see
the available capacity.

1.6 Also, Protection tab would be available to show the amount of protected and unprotected
capacity.

End of Activity 1.

1-3
Lab 1: Overview

Activity 2: Review the Administrator Settings and Execute Tasks

In this activity, you will review the Administrator settings and execute tasks.

2.1 Under Administrator settings icon, check the available values for:

o Tier management editing the tiers names

o Security settings setting Domain User, Account Domain, SSL/TLS
o SNMP settings add a SNSMP Manager
o Change local password changing local system password
o Ops Center Protector settings account and connection information for Protectors
o Storage Launch Settings enable/disable launch by login user
2.2 With the available tools in Administrator GUI, search the information to help to execute the
following tasks:

a. Write down your Administrator version here: __________________

b. Which types of Fabric Switches and their OS version are supported? ________________
c. For Thin Image (HTI) pool, what is the maximum number of pool-VOLs can be created?
____
d. What are the three Provisioning Status of the Volumes? and their description?

_________________________________________
_________________________________________
_________________________________________

End of Activity 2
End of Lab 1

1-4
Lab 2: Administrator Installation (Optional)

Objective
In this lab, you will perform lab activities to install Hitachi Ops Center Administrator software.
Alternately a demo video is provided from this link: Installation demo video.
Time Allocated: 45 Minutes

Activities
• Activity 1: Perform Ops Center Administration Installation With Preconfigured Media standalone
Deployment
• Activity 2: Hitachi Ops Center Administrator’s Network Setup

Note: Hitachi Ops Center Administrator is now included in the Preconfigured Media for the complete Hitachi Ops
Center software package.

Resources
• Ops Center 10.5.x Documentation Library (Ops Center Administrator User Guide)

Important
• Pictures and screenshots are here for explanation purposes only. Therefore, Server IP Address,
Pools, LDEV ID, and other Storage systems or Servers details must be taken as an example.
• The instructor will provide lab environment details.

2-1
Lab 2: Administrator Installation (Optional)

Activity 1: Perform Ops Center Administration Installation With Preconfigured

Media Standalone Deployment
In this activity, you will install Administrator with preconfigured media.

1.1 Open VMware vSphere Client by clicking icon. (Access to VM environment could vary from
lab to lab.)

1.2 Login into the ESXi assigned with the provided credentials.

1.3 Click File and then select Deploy OVF Template. Browse the file to deploy. (Ask the instructor
for the location):

1.4 Install Administrator v10.5.X software by following path provided by the instructor.
( Z:\Software\Administrator\10.5.X\ops-center-administrator-10.5.X.ova)

2-2
 Lab 2: Administrator Installation (Optional)

1.5 Name your VM and select the Host/Cluster INF_Cluster and then the datastore suggested by the
instructor (INF_Datastore1) and click Next.

1.6 Select Thin Provision and network suggested by the instructor (INF_CorpPortGroup).
1.7 Select Power on after deployment.
1.8 At the summary screen- Ready to Complete, click Finish.

1.9 Wait a few minutes for the VM deployment.

1.10 The new deployed VM should have the green icon and the log should confirm the VM Power on
completed.

2-3
Lab 2: Administrator Installation (Optional)

End of Activity 1

2-4
 Lab 2: Administrator Installation (Optional)

Activity 2: Hitachi Ops Center Administrator’s Network Setup

In this activity, you will perform the network setup. There are two methods, either of which can be used
to perform the setup: Method 1 with the Administrator VAM ( Virtual Appliance Manager) and Method
2 is using a built-in script.
Note: If the integrated version with Ops Center is used, the URL for VAM will be the following:
https://Ops Center Ip_add:20961/vam and credentials are sysadmin/sysadmin

Method 1:
2.1 To open a console, right-click on the new VM:

2.2 Take note of the IP address assigned to the appliance and see the instructions on how to change
the IP address.

2-5
Lab 2: Administrator Installation (Optional)

2.3 Open the internet browser with the IP address displayed on the console https://Administrator
Ip Address/vam (https://10.67.184.165/vam) and login with the default credentials.

User: service
Password: Chang3Me!

2.4 Change the Network settings accodantly to the Lab information provided and Submit.

2-6
 Lab 2: Administrator Installation (Optional)

Method 2:
2.1 At the initial console, press Alt +F2.

2.2 Login with the below credentials and then type the ip-change batch script.

User: service
Password: Chang3Me!

2.3 Change the network settings accordingly to the Lab information provided.

The VM will reboot, login after a few minutes when the reboot is completed.

2-7
Lab 2: Administrator Installation (Optional)

2.4 Change the root password immediately after installing Ops Center Administrator.
2.5 Either open an SSH connection to the VM or open the VMware console and press Alt+F2 to
reach the console.
2.6 Log in as root account using the default password: 3kO$Pe9dJyjy29HAi2mS
2.7 Run the command passwd root in the terminal
2.8 Enter the new password when prompted.
2.9 Login into Ops Center Administrator with the following URL and credentials:

https://<Ops Center Administrator ip Address>

User: sysadmin
Password: sysadmin

Ops Center Administrator installation has been completed.

End of Activity 2

End of Lab 2

2-8
Lab 3: Resources Discovery

Objective
In this lab, you will add resources (Storage System, Fabric switch, Server) with Ops Center Administrator.
Time Allocated: 30 Minutes

Activities
• Activity 1: Add a Storage System
• Activity 2: Add a Fabric switch
• Activity 3: Add a Server

Resources
• Ops Center 10.5.x Documentation Library (Ops Center Administrator User Guide)

Important:

• Pictures and screenshots are here for explanation purposes only. Therefore, Server IP Address,
Pools, LDEV ID, and other Storage systems or Servers details must be taken as an example.
• The instructor will provide lab environment details.

3-1
Lab 3: Resources Discovery

Activity 1: Add a Storage System

1.1 On the Administrator Dashboard, click Storage Systems on the left pane.

1.2 Click the plus sign (+) to add a storage system.

1.3 Enter values for the following parameters on the Onboard Storage System page:

• SVP IP Address: Enter the IP address of the external service processor for the storage
system you want to discover.
• Username and password: Log in as a user that has administrator privileges on this
storage system. For example, you can login as the user maintenance.

1.4 Click Submit.

1.5 On the Hitachi Ops Center Administrator Dashboard, click Storage Systems to see the inventory
of storage systems and capacity information.

End of Activity 1

3-2
 Lab 3: Resources Discovery

Activity 2: Add a Fabric Switch

You will add a fabric switch as a next step.
Before you begin:

• Verify that servers and ports are connected according to the manufacturer's
instructions.
• Verify that there is an active zone set with at least one dummy zone available.
• Verify the required information about the fabric switch: Virtual Fabric ID (required only
for Cisco switches), Fabric Switch Type, Fabric Switch IP Address, Port Number,
Username, and Password.
• Verify that you have the Admin role for the fabric switch.
2.1 On the Hitachi Ops Center Administrator Dashboard, select Fabric Switches to open the
Fabric switches page.

2.2 Click the plus sign (+) to open the Add Fabric Switches page.

2.3 Enter the following information from the configuration of the switch you are adding and
click the plus sign (+).

• Virtual Fabric ID: For Cisco switches, the VSAN ID. Not applicable to Brocade switches.
• Fabric Switch Type: Select Brocade or Cisco as the switch type.
• Fabric Switch IP Address: Enter the IP address for the switch.

2.4 To add or update a core switch, use the Management IP address of the switch or the Active
CP IP address.

• Port Number
• Username
• Password
2.5 Then, click Submit.

3-3
Lab 3: Resources Discovery

2.6 From Ops Center Administrator Dashboard, you should see the new FC Switch addition:

End of Activity 2

Activity 3: Add a Server

In this activity, you will:

• Add Server1, Server2 and Server3 by importing with a csv file as following:
Name, description, IP address, OS type, WWN
Server1,1,192.168.10.1, Win, physical WWN’s
Server2,1,192.168.10.2, Win, manufactured WWN’s
Server3,1,192.168.10.3, Win, manufactured WWN’s
Note: Check your server WWN’s or ask the instructor for Server1’s WWN’s

• Add Server4-6 by manually import as following:

Server names: Server4, Server5 (OS Type VMware OS) (192.168.10.4,192.168.10.5)
Server names: Server6 (OS Type Linux OS) (192.168.10.6)
Note: all manufactured WWN’s

Before you begin:

• If you choose to upload Host with CSV file, then make sure you have created a Host.csv
file with the server/s Name, Description, IP address, OS type and WWNs.
Example:

3-4
 Lab 3: Resources Discovery

3.1 On the Hitachi Ops Center Administrator Dashboard, click Servers to see the inventory of
servers.
3.2 Click the plus sign (+) to open the Add Servers page or click the plus sign (+) to CSV Import
and then select the appropriated CSV file.

For example:

3.3 For the Manual import option, click WWN list for selecting or editing known WWN’s.

3-5
Lab 3: Resources Discovery

3.4 From Ops Center Administrator Dashboard, you should see the new servers in the Server
inventory:

End of Activity 3

End of Lab 3

3-6
Lab 4: Configuration Part 1

Objective
In this lab, you will configure a Storage System with Ops Center Administrator.
Time Allocated: 60 Minutes

Activities
• Activity 1: Create Parity Groups
• Activity 2: Create Hot Spare Disk
• Activity 3: Create Pools
• Activity 4: Expand Pool and Change Pool Type

Resources
• Ops Center 10.5.x Documentation Library (Ops Center Administrator User Guide)

Important:
• Pictures and screenshots are here for explanation purposes only. Therefore, Server IP Address,
Pools, LDEV ID, and other Storage systems or Servers details must be taken as an example.
• The instructor will provide lab environment details.

4-1
Lab 4: Configuration Part 1

Configuration Check
Before you begin:
• Login into Ops Center Administrator and verify your existing configuration. Verify the storage
systems do not have any Parity Groups (except VSP F1xxx, G1xxx and VSP 5xxx), Pools, Internal
and External Volumes configured
• No Fibre Channel switches items are required for this Lab
• Report any misconfigurations or abnormalities to the instructor
• Your lab environment could consist of simulated storage system and check with your instructor
to make sure you are aware of any possible restrictions
• From the previous Lab 2 (Resources discovery), the student should have already imported 6
Servers in Ops Center Administrator as following:
Sever names:
o Server1, Server2, Server3 (3 servers for Windows OS)
o Server4, Server5 (2 servers for VMware OS)
o Server6 (1 server for Linux OS)

Activity 1: Create Parity Groups

In this activity, you will use the one of the midrange storage systems- VSP G200.
• Create parity groups (PG):
o 3xRAID5 (3+1) with FMD drives or HDDs drives with high RPM values (15Krpm)
o 1xRAID5 (3+1) with HDDs drives with low RPM values (10Krpm) and 1xRAID10(2+2) with
HDDs

• Use the Basic method to create all the RAID5 PG’s with FMDs or HDDs drives with high RPM
values (15Krpm) and Advanced method to create remaining RAID5’s and RAID10 with HDDs
• Choose any desired capacity for the parity groups
• Optionally, go to Storage Navigator (SN) and observe the content and status of the PG (Basic
Ldevs, size and status)
Basic Method (Default)

Important: Parity groups on VSP 5xxx and F1xxx or G1xxx storage systems cannot be created in
Administrator. They are created by an authorized service representative. They can be initialized in
Administrator.
1.1 On the Administrator Dashboard, select Storage Systems (midrange storage systems - VSP
G200) in the resource side panel to see the inventory of registered storage systems.
1.2 Click a Storage System to create and configure the parity groups for it.
1.3 Click Parity Groups to see the inventory of all parity groups in the storage system.

4-2
 Lab 4: Configuration Part 1

1.4 Click the plus sign (+). In the Create Parity Groups window.
1.5 Review the list of unused disk types in the storage system. This information is grouped by disk
type, disk speed, and disk capacity, and includes the following details:

a. Number of available disks.

b. Available spares detected for each disk type, disk speed and capacity.
c. Number of new or additional spares to reserve. This calculation is based on the total spares
needed based on recommended best practices and the number of existing spares in the
system.
d. The recommended RAID configuration for the disk type.
e. The number of parity groups that can be created.
f. The total usable capacity that is available based on the number of parity groups and the
RAID configuration.

1.6 Click Encryption ON (optional).

1.7 Decide if the recommended RAID configuration for each disk type is acceptable.
1.8 Click Submit.

Advanced Method

The advanced option allows you to fully configure the RAID layout of the parity group by selecting the
specific disks and hot spares to assign for parity group creation.
1.1 From the Parity Groups page, click the plus sign (+) to open the Create Parity Groups page.

4-3
Lab 4: Configuration Part 1

1.2 Click Advanced.

1.3 Select a RAID Type and a RAID Layout. (Optional) Click Encryption ON if encryption is available.
1.4 Choose available disks. Select enough disks to match the RAID Layout.
1.5 Click Submit.

Questions:

a. What is the total raw capacity, usable capacity?

b. What PG utilization figure shown by Administrator?
c. What is meaning of QFMT (Quick formatting) and PG initialization?
d. Is there any way to check the progress of QFMT?

End of Activity 1

Activity 2: Create Hot Spare Disk

In this activity, you will create a hot spare disk in your environment. Administrator allows to set free
disks to spare and spare to free. Recommended Spare Drive number:

2.1 Click a storage system tile and click Parity Groups.

2.2 At the top of the page click the icon Manage Spare Disk to open the Disk Management page
and view disks not being used in any parity group.

2.3 Click Disks to Set to Free or Disks to Set to Spare and select one or more disks. Selecting Disks to
Set to Spare will reserve the disks as a spare disk and they cannot be used for parity group
creation. Selecting Disks to Set to Free will unallocated the spare disks and return then to the
pool of available disks.
2.4 Click Submit.

4-4
 Lab 4: Configuration Part 1

End of Activity 2

Activity 3: Create Pool

In this activity, you will use the enterprise storage system (VSP G1000 or VSP 5000) to:

• Create 3 Pools:
o Pool1: Tiered Pool with Gold and Silver tiers
o Pool2: Thin Pool with 1xRAID5 FMDs or HDDs 15Krpm
o Pool3: Thin Pool with 1xRAID5 FMDs or HDDs 10Krpm

• Create the Pool1 with Basic Method and Pool2 and Pool3 with the Advanced method
• Change or verify the Tiering settings for Pool1 as follow:
o TIERING: Automatic
o CYCLE TIME: 4 Hours
o MONITORING: Continuous
o RELOCATION SPEED: 5 (Fastest)
o BUFFER SPACE FOR NEW PAGE ASSIGNMENT: T1 @8 (Default)
o BUFFER SPACE FOR RELOCATION: T1 @2 (Default)

• Change the following settings for Pool2 and Pool3:

o Utilization Threshold (Low) @80%
o Utilization Threshold (High) @90%
o Subscription Limit @200
Basic Method

Note: The selection of capacity with the Basic Method is dictated by the number of parity groups
available per tiers: minimum of four parity groups of the bronze, silver, or gold tiers, or one parity group
of the Platinum tier to create a pool using the Basic method.
If your environment does not allow the Basic Method selection, then use the Advanced Method instead.

3.1 On the Administrator Dashboard, click Storage Systems to see the inventory of registered
storage systems (VSP G1000 or VSP 5000).
3.2 Verify that all the Parity Groups are available and initialized.
3.3 Click a storage system to create a pool for it and click Pools.
3.4 Click the plus sign (+) to open the Create Pool page. Basic method is the default method.
3.5 Select the capacity based on the tiers, create two tiers for now. Set the Pool name. Adjust the
thresholds as needed. Then, click Submit.

4-5
Lab 4: Configuration Part 1

Gold Tier

Silver Tier

Advanced Method

3.1 At the Create Pool page select the Advanced tab.

3.2 Enter a pool label and Click the Type list and choose one of the following: Thin, Tiered, or Snap.
3.3 Choose whether to enable Active flash. Active flash enablement requires capacity from the
Platinum tier. Click Tier Management to see the definitions of disk type, capacity, and speed of
each pool category. Select one or more parity groups to use to create the pool. You can scroll
through the parity groups to use search and filter functions.

o For a Thin pool, select one or more parity groups with identical disk types.
o For a Tiered pool, select one or more parity groups with two or three disk types.
3.4 Set the utilization thresholds % and subscription Limit % values from the Task details. The
thresholds are used as the Warning and Critical thresholds for Capacity Monitoring.
3.5 Click Submit.

4-6
 Lab 4: Configuration Part 1

Questions:
a. In the pool, what is the best practice when Basic method is selected?
b. Can this be changed?
c. What information is not displayed in an environment that does not have an SVP?

End of Activity 3

Activity 4: Expand a Pool and Change Pool Type

In this activity, you will:

• Expand Pool2 by adding another PG 1xRAID5 FMDs or HDDs 15Krpm

• Change the pool type for Pool3 from Thin to Tiered pool. Optionally, add PG’s for more tiers

4.1 Select the pool (Pool2) for expansion and click to edit.

4.2 Select PG RAID5 available for expansion of Pool2.

4.3 Add the new PG to the tiered Pool2 to expand its capacity. Check the Job is completed.
4.4 Select Pool3 from the Pool inventory and click to edit.
4.5 Use the Advanced method tab change the pool type from Thin to Tiered and if available add any
new PG for more tiers

End of Activity 4

4-7
Lab 4: Configuration Part 1

Check Point
Now you should have several Parity Groups and Pools. Please check and see if the tables below match
your configuration.
Pools Quantity Name Type ID Capacity Note
1 Pool1 Tiered
1 Pool2 Thin
1 Pool3 Thin >>Tiered

End of Lab 4.

4-8
Lab 5: Configuration Part 2

Objective
In this lab, you will continue to configure a storage system with Hitachi Ops Center Administrator.
Time Allocated: 60 Minutes.

Activities
• Activity 1: Create Volumes
• Activity 2: Update and Expand Volume
• Activity 3: Verify and Change Port Settings
• Activity 4: Attach a Volume
• Activity 5: Change Host Group’s name
• Activity 6: Provisioning Workflow
• Activity 7: Create a Server Group
• Activity 8: Use an Existing LUN Path
• Activity 9: Change LUN Path
• Activity 10: Attach Like Volume
• Activity 11: Detach and Delete Volume
• Activity 12: Present LUN’s

Resources
• Ops Center 10.5.x Documentation Library (Ops Center Administrator User Guide)

Important:
• Pictures and screenshots are here for explanation purposes only. Therefore, Server IP Address,
Pools, LDEV ID, and other Storage systems or Servers details must be taken as an example.
• The instructor will provide lab environment details

5-1
Lab 5: Configuration Part 2

Configuration Check
• Login into Ops Center Administrator and verify your existing configuration. Verify the storage
systems do not have any Parity Groups (except VSP models F1xxx, G1xxx and 5xxx), Pools,
Internal and External Volumes configured.
• No Fibre Channel switches are required for this Lab.
• Report any misconfigurations or abnormalities to the instructor.
• Since your lab environment may include simulated storage system, check with you instructor to
make sure you are aware of any possible restrictions.
• From the previous Lab on Adding Resources, the student should have already imported 6 Severs
in Ops Center Administrator as following:
Sever names:

• Server1, Server2, Server3 (3 servers for Windows OS)

• Server4, Server5 (2 servers for VMware OS)
• Server6 (1 server for Linux OS)

Activity 1: Create Volumes

In this activity, you will:

• Create 10 Volumes @10GB from Pool1, with the label name: <studentlastname_1>
• Create 10 Volumes @20GB from Pool2, with the label name: <studentlastname_2>
• Create 10 Volumes @30GB from Pool3, with the label name: <studentlastname_3>
• Setting for all the volumes with label suffix=0, Volume ID/Range=Auto, if tiered pool set Tiering
Policy=0:all

1.1 From Volume inventory, click the plus sign (+) to open the Create Volumes page.

1.2 Complete the fields required for your new volumes with the details listed above and click the
plus sign (+).
1.3 When all the desired volumes have been defined, click Submit.

5-2
 Lab 5: Configuration Part 2

1.4 Verify the Volume inventory for accuracy of the volumes just created.

Questions:

• Why labeling the volumes is important?

End of Activity 1

Activity 2: Update and Expand Volume

In this activity, you will:

• Change volume labels:

o from <studentlastname_10> to <studentfirstname_10>
o from <studentlastname_30> to <studentfirstname_30>

• Practice the search volumes with the label names.

Note: Label names are case sensitive.
• Practice using the Filter tool to minimize the volume view.
• Work with the Column Settings to adjust the volume inventory output, for example add a
column for <Pool name> and remove for <Pool ID>.
• Expand Volume capacity by 3 times for volume <studentlastname_20> on Pool2 and change
the label as <studentfirstname_60>.

5-3
Lab 5: Configuration Part 2

2.1 Select the volume to be update (new capacity) from the volume inventory and click to edit

2.2 Change the label and the new capacity as earlier in this activity.
2.3 Search a desired volume by typing the Volume’s label in the Search window.
2.4 Click Filter drop down menu for selecting the desired options.
2.5 Select the Column Settings to change the inventory volume view.

Questions:
• What is the other option for filtering the volume inventory?
• Can the students locate the jobs in the Administrator (search jobs) where they had done
activities from 1 to 7?

End of Activity 2

5-4
 Lab 5: Configuration Part 2

Activity 3: Verify and Change Port Settings

In this activity, you will:

• With Ops Center Administrator, check the status of your Ports and make sure they are
configurated with Port Security=Enable
• Login with Storage Navigator and check other Port settings like Fabric=ON, Speed=Auto and
Connection type=P-to-P
3.1 On the Hitachi Administrator Dashboard, click Storage Systems to see the inventory of storage
systems and capacity information.
3.2 Click Ports to see the configured storage ports for the storage system.

3.3 Select one or more ports and edit Enable/Disable Security by clicking the icon .

3.4 For VSP F1xxx or G1xxx and VSP 5xxx models, you can update Port type attributes too:

VSP G/F1xxx VSP 5xxx

3.5 Select all the Fibre Channel ports and then click Enable Security and then click OK.
3.6 Login into Storage Navigator (SN) to check the other Port settings if needed.

5-5
Lab 5: Configuration Part 2

Questions:

• What are FLOGI and PLOGI processes?

• What happens when the port is connected to the switch?

End of Activity 3

Activity 4: Attach a Volume

In this activity, you will:

• Attach Volume <studentfirstname_10> to Server1 with Host Group (HG) name

<servername_studentlastname>
• Attach Volume <studentfirstname_30> to Server2 with HG name
<servername_studentlastname>
• Attach Volume <studentfirstname_60> to Server3 with HG name
<servername_studentlastname>

4.1 From the Volume inventory, select the volume to be attached and click the icon .

4.2 Start at Attach Volumes page and continue with the wizard while applying the volume name,
server name and Host Group name given above.

5-6
 Lab 5: Configuration Part 2

a. Select the server (choose the server).

b. Attach settings (define the HG and LUN optionally). Use the default settings except for
Host Group name.

c. Create Path (select a storage Port and a Server port to create a path) to attach to the
volume.

5-7
Lab 5: Configuration Part 2

4.3 The same activity can be performed from the Server inventory by selecting the appropriated
server where the volume(s) must be attached.

End of Activity 4

Activity 5: Change Host Group’s Name

In this activity, you will:

• Change all the HG’s names previously defined for each server:
from <servername_studentlastname> to <servername_studentfirstname>
5.1 From the Storage Systems page, select the Host Group tile:

5.2 Select the Host Group to be edit and click the icon and Edit Host Group.

5-8
 Lab 5: Configuration Part 2

5.3 An alternative method for editing the Host Group’s is from the Server inventory. Select the
Server and then expand the Volume menu by clicking the icon . At the next menu, click the
pencil icon to edit the Host Group.

End of Activity 5

Activity 6: Provisioning Workflow

In this activity, you will run the Provisioning Workflow to Create, Attach, and Protect volume(s) for:
• Server name: Server1
• Number of Volumes: 2
• Volume Capacity: @100GiB,
• Volume label: Studentfirstname_100
• From Pool: Pool1

6.1 On the Administrator Dashboard, click Servers to see the inventory of servers.

6.2 Select one server per details given at the beginning of this activity and click Attach Volumes.

5-9
Lab 5: Configuration Part 2

6.3 Then, select Create, Attach, and Protect Volumes with Local Replication.

6.4 Configure volumes based per the details given at the beginning of this activity and when you
have made your choices, click the plus sign (+) to add volume row to the list of volumes that will
be created.
6.5 Click Next.

6.6 In the Attach settings keep the default values and click Next.

5-10
 Lab 5: Configuration Part 2

6.7 At the Create Paths panel, you can view servers and their WWNs, along with ports on the
storage system.

6.8 When you are satisfied with the paths, click Next to view options for protecting volumes.
6.9 Select None for replication Type and Submit.

End of Activity 6

Activity 7: Create a Server Group

In this activity, you will:
• Create a Server Group (SG) with Server4 and Server5 and name <Server45_studentfirstname>
• Attach to SG <Server45_studentfirstname> the remaining 9 Volumes labelled
<studentlastname_31> to <studentlastname_39>
7.1 From the Server Inventory page, select the Server Group tab.

7.2 Click the plus icon (+) and then enter the parameters by adding Server4 and Server5 for the
<Server45_studentfirstname> Server Group.
7.3 Click Submit.

5-11
Lab 5: Configuration Part 2

7.4 From the Server Group inventory, select the Server Group created just now and click the icon
for attaching the Attach Existing Volumes.

7.5 Search the nine volumes described in the Task details and click Next and follow the wizard.

7.6 At the Attach Settings, keep the default values and click Next.

5-12
 Lab 5: Configuration Part 2

7.7 At the Create Paths, select any available ports as your choice and click Submit.

End of Activity 7

Activity 8: Use an Existing LUN Path

Note: The feature “Use existing LUN path” can be used between servers with the same OS type only.
In this activity, you will use an existing LUN Path. Server6 will use the existing path from Server2. Server6
OS type must be changed from Linux to Windows before the task begins.

8.1 From the Server inventory, select the Server6 and click the edit icon for changing the OS type:

8.2 Select Server6 and click Use Existing LUN Path.

8.3 At the Original Server, select Server2 and click Next.

5-13
Lab 5: Configuration Part 2

8.4 Complete the task by configuring the LUN Path for Server6.

8.5 Check that now Server6 is attached to the same volume <studentfirstname_30> as Server2.

End of Activity 8

Activity 9: Change LUN Path

In this activity, you will change the LUN path for volume <studentfirstname_60> attached to Server3
and then chose any other available ports from the storage system.
9.1 From the Server inventory, click on Server3.
9.2 Then, select the volume requested in task details.
9.3 Click the icon to edit the LUN path .

9.4 Next, keep the default settings and click Next.

9.5 At Create Path page, change the existing path by choosing a different Storage Port.
9.6 To delete the existing path; select the “blue” path with your cursor, the path change colour to a
“light blue”.
9.7 Click Delete Selected. Choose another storage port and click Submit.

5-14
 Lab 5: Configuration Part 2

End of Activity 9

Activity 10: Attach Like Volume

In this activity, you will:

• Execute the feature “Attach like volume” from the volume labelled <studentfirstname_60>
• Use the following details for completing the Create, Attach and Protect Volumes wizard:
o Label <studentfirstname_7>
o Capacity to @70GiB
o Keep the rest with the default settings, in other words, Pool2 and No protection (Snap)

10.1 From the Volume inventory, search and select the volume labelled <studentfirstname_60>.
10.2 Click the icon for Attach like volume with Local Replication.

5-15
Lab 5: Configuration Part 2

10.3 Verify the Volume parameters and make the changes given in the beginning of this activity
and then click Submit.

End of Activity 10

Activity 11: Detach and Delete Volume

In this activity, you will:
• Detach all the nine volumes attached to Server4 labeled <studentlastname_31> to
<studentlastname_39>
• Detach all the nine volumes attached to Server5 labeled <studentlastname_31> to
<studentlastname_39>
• Delete all the volumes with the following labels:
o <studentlastname_21> to <studentlastname_29>
o <studentlastname_31> to <studentlastname_39>

5-16
 Lab 5: Configuration Part 2

11.1 From the Server inventory for Server4 and Server5 select the attached volumes for each
server.
11.2 Click icon for Detach Volumes. Do not remove zones when at the prompted.

11.3 Search for the volume in the Task details and click icon for Delete Volumes.

End of Activity 11

5-17
Lab 5: Configuration Part 2

Check point
Now you should have several Servers, Volumes and Server Groups. Please check and see if the tables
below match your configuration

Volumes
Quantity Label On pool Capacity Status Server
name (GiB)
9 studentlastname_11-19 Pool1 10 unattached none
1 studentfirstname_10 Pool1 10 attached Server1
1 studentfirstname _30 Pool3 30 attached Server2 &
Server6
1 studentfirstname _60 Pool2 60 attached Server3
1 studentfirstname _70 Pool2 70 attached Server3
2 Studentfirstname_100-101 Pool1 100 attached Server1

Servers
Name OS Type ID Vol’s Server Group
attached
Server1 Windows 3 none
Server2 Windows 1 none
Server3 Windows 2 none
Server4 VMware 0 Server45_studentfirstname
Server5 VMware 0 Server45_studentfirstname
Server6 Linux>> Windows 1 None

5-18
 Lab 5: Configuration Part 2

Activity 12: Present LUNs

In this activity, you will:

• From Server1, present three LUN’s in the Windows server generated by the 2 Volumes @100GiB
and one Volume @10Gib from the previous activity
o Server name: Server1
o Number of Volumes: 3
o Volume Capacity: @100GiB and 10GiB
o Volume label: Studentfirstname_100-101 and Studentfirstname_10
o From Pool: Pool1

12.1 From Windows Disk Management under Action tab run Rescan Disks. On Windows 2012,
reset the HBA when presenting for the LUNs for the first time.
12.2 Open Device Manager and with Storage controllers, right click and disable /enable the HBA.

12.3 The three LUN’s should be in offline status and Unallocated.

5-19
Lab 5: Configuration Part 2

12.4 Right click to perform an Online and Initialize operation for each LUN’s.

12.5 Right click on each of the LUN to start the wizard of “New Simple Volume”.

12.6 Finally, all the drives are available in File Explorer:

End of Activity 12

End of Lab 5

5-20
Lab 6: Migration and Protection

Objective
In this lab, you will be creating Protection volume and configuring Migration volumes with Administrator.
Time Allocated: 90 Minutes

Activities
• Activity 1: Protection With Local Replication – Clone Now
• Activity 2: Protection With Local Replication – Snap
• Activity 3: Internal Volume Migration
• Activity 4: External Volume Migration

Resources
• Ops Center 10.5.x Documentation Library (Ops Center Administrator User Guide)

Important:

• Pictures and screenshots are here for explanation purposes only. Therefore, Server IP Address,
Pools, LDEV ID, and other Storage systems or Servers details must be taken as an example.
• The instructor will provide lab environment details.

6-1
Lab 6: Migration and Protection

Activity 1: Protection With Local Replication – Clone Now

In this activity, you will:

• Clone an attached volume and restore from the replica after a simulated error in the
primary volume. On Windows server, verify that the original data is correctly restored.
Follow the details and procedure below.
• Select a LUN mapped to Windows server (i.e. Drive F) and create six files naming
File1>>>>File6

1.1 Create six files called (File1>>>File6) in you Windows server drive.

1.2 In Storage Systems, select the corresponded volume (<studentname_100>) to drive F and run
Protect volume with Local Replication.

1.3 Select Clone Now and name your Replication Group name= studentname_clone.

6-2
 Lab 6: Migration and Protection

1.4 When the replication job is completed, click Replication Groups tile from storage inventory.
Check that replication status is suspended (PRI=PSUS & SEC=SSUS). At this point the Secondary
volume has the copy of your Primary with the original six files (File1>>>File6).

1.5 Now simulate a problem with the data in the Primary by deleting three files (i.e. File 4, 5 , 6)
from the Windows Drive.

>>>>>>>

1.6 From Disk manager, make the Windows drive offline before the Restore operation.

1.7 From the Replication Group page, expand the Policy Name menu and select the pairs to be
restored and then click the icon Restore Volume Pair.

1.8 When the Restore operation is completed, put the Windows drive online from Disk manager and
check that the six original files have been restored.

6-3
Lab 6: Migration and Protection

.>>>>>>

1.9 When the replication is completed, go to Replication group, and delete the Policy name.
<studentname_clone>.

End of Lab Activity 1

Activity 2: Protection With Local Replication – Snap

In this activity, you will:
 Snap an attached volume and restore from the replica after a simulated error in the primary
volume. In Windows server verify that the original data is correctly restored. Follow the details
and procedure below.
 Select a LUN mapped to Windows server (Drive F) and create six files called File1>>>>File6.

2.1 In Windows server, six files should be already available for your task otherwise repeat steps
1.1 and 1.2 from the previous activity.
2.2 Select Snap as a replication type and use the following Snap settings:

o Replication Group name= studentname_snap

o Schedule= Hourly
o Minute= closer minute to your local time
o Retention= 1
o Consistency= none

6-4
 Lab 6: Migration and Protection

2.3 The first Snap replica will be available with the minute set in the policy, have a look the time
by editing the policy and the message should be something like:

Snap will start every 1 hours of the UTC time. Current time in UTC is 09/24/20 01:39 PM.

2.4 When the replication job is completed, click Replication Groups tile from storage inventory.
Check the replication status is suspended (PRI=PSUS & SEC=SSUS). At this point the
Secondary volume has the copy of your Primary with the original six files (File1>>>File6).

2.5 Repeat the steps 1.5 to 1.8 from the previous activity.
2.6 Optionally, set another Snap replication with Retention=2, Hourly. Change your file between
the replication sessions and exercise the restore to see in Windows the drive contents.
2.7 Delete the Replication Group when the task is completed.

End of Lab Activity 2

Activity 3: Internal Volume Migration

In this activity, you will:
• Generate data for the LUN using either of the two options below:
Option 1: from Server1, start I/O meter to one of the LUN’s
Option 2: from Server1, start the video “Administrator_external_migration.mp4”

• Perform an internal migration on existing attached volume from a source pool to target
pool.

6-5
Lab 6: Migration and Protection

Before you begin:

• All selected volumes belong to a single storage system.
• All selected volumes will be migrated to a different pool of the same storage system.
• All selected volumes are attached to servers.
• The volumes are not protected. However, a clone pair can be migrated if the P-Vol status is
PSUS and the S-Vols status is SSUS.

Option 1:

3.1 From Server1, start IO meter by selecting the Icon in your desktop and select Drive E on Disk
Targets tab:

3.2 Define access specification by selecting All in one. The patten 0% write, modify it if needed by
selecting Edit.

3.3 Setting the Results Display.

Result of Test = Start of the test

Update Frequency= 1 Second

6-6
 Lab 6: Migration and Protection

3.4 Run the IO meter by clicking the Green Flag, define the result file and observe the Result Display:

Make sure I/O meter runs without interruptions through the internal migration task.

Option 2:
Copy the video “Administrator_external_migration.mp4” from your Windows server shared folder
to Server1, in drive E: (Volume@10GB, <studentname_10>), and then start the video.
(Video Length: -6:45 minutes) and audio is off, loop=on.

Important: Make sure the video runs without interruptions through the internal migration task.

3.1 On the Administrator Dashboard, select Storage Systems in the Resource side panel to see the
inventory of registered storage systems.
3.2 Click a Storage System and then Volumes. Select the volume for your migration
(<studentname_10>) and click Migrate Volumes.

6-7
Lab 6: Migration and Protection

3.4 In the Volume Settings section, leave all the Capacity Settings and Volume ID/Range in Auto.

3.5 In the Task Settings section, select Migrate now and name the Migration task. Click Submit.

3.6 Check that the video or I/O meter is still running.

3.7 Now a migration job will start.

6-8
 Lab 6: Migration and Protection

3.8 In the storage system inventory, the Migration Task icon is available for selection. Click
Migration Task tile for monitoring and managing the Migration activities. Confirm that the
activity status=Success, Pair=Migrated and check if the volume reside on the target Pool (TGT
Pool2 ID1).

Check also that the LDEV_ID has been swapped by going to the volume screen or the pool
screen.

3.9 Verify the I/O meter or the video is still running without interruptions until the migration is
completed. Then stop I/O meter or the video.

Questions:

• Name some of the reasons why internal migration is necessary?

End of Activity 3

6-9
Lab 6: Migration and Protection

Activity 4: External Volume Migration

In this activity, you will:
 Run an external migration on existing attached volume from a source storage system to target
storage system.
 From Server1, use an appropriated attached volume (<studentname_100> Drive F: @100GB with
File1>>File6) for your migration.

Before you begin:

• The target storage system must be onboarded in Administrator
• The source volumes must be virtualized and selectable as external volumes
• The target storage system must have at least one eligible pool (Thin or Tiered) with enough
space to migrate volumes

4.1 On the Administrator Dashboard, select Storage Systems in the Resource side panel to see the
inventory of registered storage systems.
4.2 from Storage System inventory, select your Source Storage and drill down to Volumes.
4.3 Select the volumes to be migrated and click Attach to Storage.

6-10
 Lab 6: Migration and Protection

4.4 Create paths between Source Storage port and Target Storage port and Submit.

4.5 In the Target Storage section, the volumes must be virtualized before migration, therefore, click
External Volumes and Discover External Storages and then select the ports that are
attached to the source storage system (CL8-E). Click Submit.

>>> >>>>

4.6 The Administrator will prompt with a message about discovering the External Storage, wait until
the Job is completed successfully.
4.7 At the External Volume page, click the plus sign (+) to add the External Volumes.

Now the Create External Volumes wizard will start.

4.8 At Select Volumes page, select Discovered Volumes information from the external storage
systems and Next.

4.9 At the Volume Settings page, label (studentname_1001) the volume and set the Volume
ID/Range if necessary and Next.

6-11
Lab 6: Migration and Protection

4.10 On the Select Servers page, select the server (Server1) to attach external volumes to be created
and click Next.

4.11 At the Select Path page, define the path to the server and Submit.

4.12 At the Target Storage, click the External Volume tile and the new discovered External Volume
should be ready for migration, select the volume and click Migrate Volumes.
Migrate Volumes

4.13 On the Select Target Pool page, select the pool (Pool1) where the Volume will be migrated and
then click Next.

4.14 On the Volumes Settings page, select Capacity Saving and Volume ID/Range if necessary and
then click Next.

6-12
 Lab 6: Migration and Protection

4.15 Finishing the Migration Volumes with the Task setting by naming the task and choose the
schedule and Submit.
4.16 Verify that the server (Server1) has the new volume (studentname_1001) and from Windows
server check the new LUN (Drive H:) has the same data (File1>>File6) from drive F:

Unvirtualizing volumes

Unvirtualizing volumes is cleaning up the environment after migration. You also need to delete
migration task before unvirtualizing the volumes.

4.17 In the Target Storage section, External Volume page, click Unvirtualize.

6-13
Lab 6: Migration and Protection

4.18 From the Source Storage main window, goto Volumes section. Then, select the volume used for
migration. Next, click Detach From Target Storage icon to remove the connection between
source and target storage systems.

End of Activity 4

End of Lab 6

6-14
Lab 7: Multipathing Management

Objective
In this lab, you will configure and use ALUA with Hitachi Ops Center Administrator.
Time Allocated: 30 Minutes

Activities
• Activity 1: Attach an ALUA Enabled Volume to a Host
• Activity 2: Observe ALUA Behavior on a Windows Host (optional)

Resources
• Ops Center 10.5.x Documentation Library (Ops Center Administrator User Guide)

Important:

• Pictures and screenshots are here for explanation purposes only. Therefore, Server IP Address,
Pools, LDEV ID, and other Storage systems or Servers details must be taken as an example.
• The instructor will provide lab environment details including:
o Server name to log on
o Tools to use for HBA monitoring

7-1
Lab 7: Multipathing Management

Activity 1: Attach an ALUA Enabled Volume to a Host

In this activity, you will attach an ALUA enabled volume to a host.
1.1 Setup ALUA attribute to a volume.

a. Using Ops Center Administrator, create a 1GiB volume and name it Test_ALUA.
b. Once the job has completed, go to the Volumes screen of the array, select the
Test_ALUA volume and edit it by clicking on the icon as shown below:

c. In the volume details, set ALUA SETTING=Enable by clicking on Enable as shown below:

 Wait for the job to complete.

7-2
 Lab 7: Multipathing Management

1.2 Attach the volume with two paths to the server.

a. Attach the Test_ALUA volume to your server using two paths as shown below:

 Wait for the job to complete.

1.3 Change the host group preferred path attribute.

a. In the summary page of your storage array, click on the HOST GROUPS/iSCSI TARGETS
tile.

7-3
Lab 7: Multipathing Management

b. You can sort the Host Group names by clicking on the column title.
c. Select the Host Group corresponding to the second path of the Test_ALUA volume to
your server, in this example the one on CL2-A for server “toulouse”.
d. Edit this Host Group by hover on the icon and choose Edit Host Group as shown
below:

e. Set the PREFERRED PATH attribute to Non Preferred by just clicking on Non Preferred as
shown below:

 Wait for the job to complete.

End of Activity 1

7-4
 Lab 7: Multipathing Management

Activity 2: Observe ALUA Behavior on a WINDOWS Host [optional]

In this activity, you will observe ALUA behavior on a Windows host.
Note: This lab activity requires a tool that allows you to reset the HBA and to view statistics on it.
Ask your instructor for the tool to use depending on the HBA installed on your server.
2.1 Discover the new volume and run the IO activity in the host.

a. Open the Windows disk management tool.

b. Rescan the disks to discover the new volume.
c. Put it Online, initialize it.
d. Create a new NTFS partition, name it ALUA_ldevid.

e. Run the IOMeter tool to generate read activity on this volume as shown below:

7-5
Lab 7: Multipathing Management

f. Choose large block size so that you will generate a large throughput on the HBA:

g. Start the activity by clicking on the green flag:

h. Once the test is running, you should observe a High Throughput on the Results Display
window:

7-6
 Lab 7: Multipathing Management

2.2 Observe I/O activity and port behavior.

a. Open the HBA utility (HBAnywhere if you have Emulex HBAs) and reset both adapters so
that statistics are reset to zero.

b. After having reset both adapters, go to the Statistics tab on both adapters and you will
see only one is the sending activity.

As you can see, the second adapter is not doing any I/O. This is the one corresponding to the
Non Preferred Path.
2.3 Reset the Host Group path attribute setting to Preferred.

a. In Ops Center Administrator, reset the host group you’ve set as Non Preferred Path in
the previous lab activity to PREFERRED.

 Wait for the job to complete.

b. Reboot your Windows server and run the IOMeter again using the same setup as used
before.

Note: The server needs to be rebooted if the ALUA settings are modified. A reset of the
HBA is not sufficient for the Operating System to probe the Asymmetric Access State.

7-7
Lab 7: Multipathing Management

c. Open HBAnywhere or the tool used to manage your HBAs (Fiber Channel Adaptor on
your server) and view the statistics on the ports.

You can see now that traffic is evenly dispatched on both ports.

End of Activity 2

End of Lab 7

7-8
Lab 8: Adaptive Data Reduction (ADR)

Objective
In this lab, you will be configuring and using Adaptive Data Reduction (ADR) with Ops Center
Administrator.
Time Allocated: 90 Minutes

Activities
• Activity 1: ADR Using Software Compression
• Activity 2: ADR Using Software Compression and Deduplication
• Activity 3: ADR Using Hardware Compression (Optional)

Resources
• Ops Center 10.5.x Documentation Library (Ops Center Administrator User Guide)

Important:

• Pictures and screenshots are here for explanation purposes only. Therefore, Server IP Address,
Pools, LDEV ID, and other Storage systems or Servers details must be taken as an example.
• The instructor will provide lab environment details including:
o Server name to log on
o Files to be used as sample files for ADR observation

8-1
Lab 8: Adaptive Data Reduction (ADR)

Activity 1 ADR Using Software Compression

In this activity, you will:

• With Ops Center Administrator, create a volume with Capacity Savings enabled with
compression only.
• Attach this volume to a server and write data on this volume to observe the compression
efficiency.
• View all the information given on software compression.

1.1 Create a volume with Capacity Savings set to compression.

a. See Configuration Lab Part 1 as a reference for creating volumes.

b. Choose or create a pool where Hardware compression, Compression and Deduplication
are not configured, as shown below. Name the pool Pool_Comp.

c. In this pool, create a 1TiB volume with compression enabled. Name this volume
Vol_Comp.

8-2
 Lab 8: Adaptive Data Reduction (ADR)

d. Attach the volume to your server and write data.

e. Attach the volume Vol_Comp to your server and copy and un-compress the file named
“Highly Compressible.zip” file on this volume as show below:

1.2 View the Pool_Comp ADR information.

o SOFTWARE SAVING metric is the product of all capacity savings metrics. This is the only
relevant metric on which Hitachi will take a commitment.
o As you can see here, there is no deduplication that took place. Software deduplication
ratio is 1:1 and no additional Subscribed Capacity is shown, only the size of the DP-VOL,
1Tib, which is 19% of 5.15TiB.
Take a 10 minutes break and go back to the pool menu.
The figures may have changed after deduplication process took place and Ops Center Administrator
values have been refresh.

End of Activity 1

8-3
Lab 8: Adaptive Data Reduction (ADR)

Activity 2: ADR Using Software Compression and Deduplication

In this activity, you will:

• With Ops Center Administrator, create a volume with Capacity Savings set as compression and
deduplication
• Write duplicated data on this volume to observe the capacity savings efficiency
• View all the information given on capacity savings
• Write zero filled data on this volume to observe the capacity savings efficiency
2.1 Create a volume using compression and deduplication.

a. Edit the previously used Vol_Comp volume and set Capacity Saving=Deduplication and
Compression as shown below.
b. Set the Volume Label to Vol_Comp_Dedup.

2.2 Write duplicated data on this volume to observe the capacity savings efficiency.

On the Windows volume corresponding to Vol_Comp_Dedup, copy and uncompress the file
named Highly Compressible.zip. Make several copies of this file in your partition so that you are
using some space on your Windows volume as shown below:

8-4
 Lab 8: Adaptive Data Reduction (ADR)

2.3 View all the information given on capacity savings.

a. In the pool screen, observe the indicators relating to capacity savings.

b. See how capacity saving metrics have changed, especially the software deduplication
due to duplicated files.
c. Observe the high percentage of Subscribed Capacity. This is only due to the DSD and FPT
system volumes that are included here in this metric.
d. Refresh the storage array information by clicking on the icon.

Note: The figures may have changed after deduplication process took place and Ops Center
Administrator values have been refreshed.
2.4 Write zero filled data on this volume to observe the capacity savings efficiency.

a. Still on the same Windows volume, copy and uncompress the file named Zero Filled
Large File.zip as shown below:

Note: This file is a so-called sparse file. It contains only zeros. You can find similar files used by
databases to store data into a file system.

8-5
Lab 8: Adaptive Data Reduction (ADR)

b. In the pool screen, observe the indicators relating to capacity savings.

• You can see the impact of zero filled files. The pattern matching metrics indicates blocks that are
matching certain patterns like “all zeros” and “all ones”.
• Wait 15 min and go to see if the figures change after a while.

End of Activity 2

Activity 3: ADR Using Hardware Compression (Optional)

In this activity, you will:

• With Ops Center Administrator, create a pool using Compression Enabled Parity Group
• View all the information given on hardware compression
• Create a volume on that pool and attach it to a server
• Write data on this volume and observe the compression efficiency

3.1 Create a pool using a parity group with enabled compression.

a. On the Hitachi Administrator Dashboard, click Storage Systems (select the one you are
using). Then, click Parity Groups.

8-6
 Lab 8: Adaptive Data Reduction (ADR)

b. Have a look at the compression column and check if there is a parity group with enabled
compression or at least of FMD DC2 disk type on which you can enable compression by
clicking on the icon below:

Note: At the first time, the parity group must be in a pool before Accelerated Compression can be
enabled.

c. Create a thin Pool by using this parity group. (see Configuration Lab Part 1 as a reference
for creating pools.) Name this pool Pool_Comp_HW.

3.2 View all the information given on Hardware compression.

a. In the created pool screen, observe the information relating to capacity savings.
b. Look at the FMD Compression screen.

8-7
Lab 8: Adaptive Data Reduction (ADR)

3.3 Create and attach a 1Tib volume from this pool.

Note: Set the Capacity Saving=Compression.

You will receive this message.

This message is a warning message indicating that software compression should not be
activated on Hardware Compressed Parity Groups. It’s better optimized to use only Hardware
Compression in that case. Moreover, if you compress the data by software operation, the data
cannot be further compressed by the FMD DC2.
c. Click Cancel.
d. Change the Capacity Savings parameter to No.

8-8
 Lab 8: Adaptive Data Reduction (ADR)

3.4 Write data on the volume and observe compression efficiency.

a. From your Windows host, write the file named Zero Filled Large File.zip on the
previously attached volume and uncompress the file.

Note: This file is a so-called sparse file. It contains only zeros. You can find similar files
used by databases to store data into a file system.

b. Take a note of the space used on your Windows volume as shown below:

c. In Ops Center Administrator pool screen, observe the impact of writing to the volume.

o FMD COMPRESSION is the compression ration achieved by FMD DC2.

8-9
Lab 8: Adaptive Data Reduction (ADR)

o FMD PATTERN MATCHING is indicating efficiency of pattern matching detected by the

FMD.
o FMD SAVINGS is the metric to use for commitment on capacity savings ratio when using
hardware compression. It is the product of FMD COMPRESSION and FMD PATTERN
MATCHING. It is also reported as the DATA REDUCTION metric.

End of Activity 3

End of Lab 8

8-10
Lab 9: Administer and Monitor

Objective
In this lab, you will explore monitoring function of Hitachi Ops Center Administrator and learn how to
use VAM for accessing Ops Center system tools.
Time Allocated: 30 Minutes

Activities
• Activity 1: Monitoring Using Ops Center Administrator
• Activity 2: Ops Center Administrator System Tools
• Activity 3: Gathering Ops Center Administrator Log Files

Resources
• Ops Center 10.5.x Documentation Library (Ops Center Administrator User Guide)

Important

• Pictures and screenshots are here for explanation purposes only. Therefore, Server IP Address,
Pools, LDEV ID, and other Storage systems or Servers details must be taken as an example.
• The instructor will provide lab environment details including:
o IP address of Ops Center Administrator

9-1
Lab 9: Administer and Monitor

Activity 1: Monitoring Using Ops Center Administrator

In this activity, you will explore the monitoring windows of different alert categories and learn how to
drill down to more detailed information.
1.1 Browse the alerts from the main Dashboard.

a. In the Ops Center Administrator Dashboard, examine the tiles on the upper side.

b. If one of those have a red circle, click on this one and examine the Alerts.
Note: It is not that easy to trigger an alert on Hardware Alerts or even on the Capacity or
Data Protection Alerts. It’s easier for Jobs.
c. When looking at the job alerts, drill down to the actual error message by clicking
consecutively on each message until the final error message as shown below:

9-2
 Lab 9: Administer and Monitor

1.2 Explore the Monitoring tab.

a. On the main Dashboard, click Monitoring.

b. On each tile, there is an arrow in the lower right corner, click on this one to expand the
tile and have more details as shown below:

End of Activity 1.

9-3
 Lab 9: Administer and Monitor

Activity 2: Ops Center Administrator System Tools

In this activity, you’ll access the Virtual Appliance Manager (VAM) to administer Ops Center
Administrator and configure, backup and restore this management tool.
2.1 Access the Virtual Appliance Manager (VAM).

Administration tasks on Ops Center Administrator are accessible from a specific URL which gives
access to the Virtual Appliance Manager (VAM). Depending on the deployment model used for
installing Ops Center Administrator, you’ll have two distinct URL and credentials:
o OVA deployment, Administrator is part of Ops Center VM
 URL: https://<OpsCenterIP@>:20961/vam
 user: sysadmin password: sysadmin
o Standalone deployment (OVA or Linux)
 URL: https://<AdministratorIP>/vam
 user: service password: Chang3Me!
a. Ask your instructor about the type of install of your Ops Center Administrator.
b. Log on to the VAM.

c. In Network tab, you can change the Network Settings of Ops Center Administrator.
d. Go and explore the other tabs, but don’t submit any change.

9-4
 Lab 9: Administer and Monitor

2.2 Backup and restore Ops Center Administrator.

a. Click on BACKUP.
(Be patient) After a few minutes, depending on your internet browser settings, a dialog
window will appear, or the backup file will be automatically downloaded to your
downloads folder.

b. To restore a backup file in Ops Center Administrator, log on the VAM and just click
RESTORE, a window opens as shown below:

c. Just drag and drop the configuration backup file and click on Submit.

Important: Don’t do it in your lab environment unless you’re the only user on your Ops
Center Administrator.
Restore operation will take a while and reboot the Ops Center Administrator.

9-5
Lab 9: Administer and Monitor

Activity 3: Gathering Ops Center Administrator Log Files

In this activity, you will gather audit and maintenance information log files.
3.1 Gather Audit logs.

a. On the main screen of the VAM, click on DOWNLOAD AUDIT LOGS as shown below:

Depending on your internet browser settings a dialog window will appear, or the backup file will
be automatically downloaded to your downloads folder.
3.2 Collect the Maintenance information logs.

a. Connect to your Ops Center Administrator server using SSH connection. (ask your
instructor for the root password)
b. Open an SSH connection to the VM.
c. Log in as root account (ask your instructor for the root password).
d. In the terminal, execute the following command:
/opt/rainier/bin/rainier-getlogs -dir [output-directory]

Important: The output directory must be empty.

e. Check the location of collected log file (rainier-logs.tar.gz) in the specified output
directory and copy the file to your client computer as required.
f. Name the created file should be named rainier-logs.tar.gz.

End of Activity 3

End of Lab 9

9-6
Lab 10: Command Line Interface (CLI)

Objective
In this lab, you will use Ops Center Administrator REST API CLI for storage and host provisioning.
Time Allocated: 90-120 Minutes

Activities
• Activity 1: Getting Started With Token Operations Using Administrator REST
• Activity 2: Perform Basic REST Activities:
o Token Operations
o Storage Operations
• Activity 3: Lab Project
o Check the solution to the Lab Project

Resources
• Ops Center 10.5.x Documentation Library (Ops Center Administrator User Guide)

Important:
• Pictures and screenshots are here for explanation purposes only. Therefore, Server IP
Address, Pools, LDEV ID, and other Storage systems or Servers details must be taken as an
example.
• The instructor will provide lab environment details.

10-1
Lab 10: Command Line Interface (CLI)

Note:
In this lab, we are using jq-win64.exe utility to view the json output. This utility is used to make json
output understandable and uses two ways to send parameters for some operations. To access it, copy
the file to the c:\curl\bin folder. No installation is required. You can specify the parameters in two ways.
Link to download the software is: https://stedolan.github.io/jq/download/
Curl is a command line utility to issue commands in REST. It is available for various OS. It can be
downloaded from https://curl.haxx.se/download.html. The curl is already downloaded on your local
machine and is in the c:\curl\bin folder. To use it, open a command prompt, and change the folder to
curl\bin

1. The IP Address of Ops Center Administrator or Ops Center Portal, depending on how
Administrator is installed.
2. OpsCenter Administrator is installed:
a. As a part of OpsCenter Portal (use https://<IP-opsCenter>:20961)
b. As an independent machine. (use https://<IP-Administrator>)

Activity 1: Getting Started With Token Operations Using Administrator REST

In this activity, you will understand generating and deleting Tokens using Administrator REST API.
1.1 Generate the token.

a. Use the token to do all the operations that you want

b. If the token expires, then go back to step a.

1.2 Then, delete the token. (or after some time, the token will expire)

Let us take an example to understand REST command syntax and return values.
C:\cURL\bin>curl -k -H "X-Auth-Token: 1b050ac9-ca47-4430-a085-
708d8aae1449" https://192.168.0.150:20961/v1/storage-
systems/410927/volumes/summary | jq-win64
{
"volumeCountByType": {
"THIN": 2
},
"numberOfVolumes": 2
}

The above command shows the list of DP-Vols in the system. Since there is no -X or -d, this is a
GET command. The -k is to ignore SSL. The X-Auth-Token is the authorization token. The

10-2
 Lab 10: Command Line Interface (CLI)

https://192.168.0.150:20961 is the base URI. V1 is the database. And then the resources are
listed. The resources can be nested. The json output is nested with curly braces.
volumeCountByType (nested field) and numberofVolumes (numeric) are fields. “THIN” is a
nested field under the volumeCountByType.
Note the next command. Without the jq-win64, the json is not clear. It may become
complicated to read sometimes (look at the answers for the project to see some samples).
C:\cURL\bin>curl -k -H "X-Auth-Token: 1b050ac9-ca47-4430-a085-
708d8aae1449" https://192.168.0.150:20961/v1/storage-
systems/410927/volumes/summary
{"volumeCountByType":{"THIN":2},"numberOfVolumes":2}

Another option this time (-i) to get us more information of the return header.
C:\cURL\bin>curl -ki -H "X-Auth-Token: 1b050ac9-ca47-4430-a085-
708d8aae1449" https://192.168.0.150:20961/v1/storage-
systems/410927/volumes/summary
HTTP/1.1 200
Server: nginx/1.18.0
Date: Tue, 29 Sep 2020 20:15:44 GMT
Content-Type: application/json;charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: POST, GET, OPTIONS, DELETE
Access-Control-Max-Age: 3600
Access-Control-Allow-Headers: Origin, X-Requested-With, Content-
Type, Accept
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
X-Frame-Options: DENY
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: 0
Strict-Transport-Security: max-age=31536000; includeSubdomains
Content-Security-Policy: block-all-mixed-content, frame-
ancestors 'self'

{"volumeCountByType":{"THIN":2},"numberOfVolumes":2}

10-3
Lab 10: Command Line Interface (CLI)

The HTTP/1.1 200 is the return value, where 200 means all is ok. The command worked
successfully.
You may get a common return value as 401. That means that your token has expired, and it
needs to be regenerated.

Activity 2: Performing Basic REST Activities

In this activity, you will perform basic REST operations related to Token and storage.
2.1 Generate the token. (POST)
2.2 Check the token. (GET)
2.3 Check which Storage System is registered (GET)
2.4 Register our Storage System (POST)
2.5 Check which Parity Groups are there in our Storage System (GET)
2.6 Check the drives in the box (GET)
2.7 Create a RAID5 (3+1) Parity group (POST)
2.8 Delete the Parity Group (DELETE)
2.9 Check if the Parity Group is deleted (GET)
2.10 Delete the Storage System (DELETE)
2.11 Check if the Storage System is removed (GET)
2.12 Delete the token. (DELETE)

10-4
 Lab 10: Command Line Interface (CLI)

Activity 3: Lab Project

In this activity, you will demonstrate that all operations of Ops Center Administrator can be done using
REST API.
Note:
It is recommended to use REST API for performing all the operations. In case you get stuck at some
activity, you may look at the solution given at the end or use GUI to perform the operation and continue
forward.
Resources:
Serial Number
SVP IP
C1/C2 IP (use this only if you are using a P2
machine without an SVP)
Authentication (user/password)
IP Address of Administrator?
Is it installed with OpsCenter If yes, use port number 20961, else do not use
the port number
Server name
Server WWNs
Which ports of storage are zoned to the server

Operations: (Please update after you complete each step)

Activity Completed
(Yes/No)
3.1 Generate a token.

3.2 Is your storage system registered?

3.3 Register your storage system, if 2 returns false.

3.4 Verify the storage system is registered.

3.5 List the drives in the system.

3.6 If you find 8 FREE drives, then create 2x3+1 Parity Groups.

3.7 List the Parity Groups. (you should see 2)

3.8 Use the first Parity Group and create a thin pool.

10-5
Lab 10: Command Line Interface (CLI)

3.9 List the pool details.

3.10 Now check if the server assigned to you has already been
entered in the system. If the server is not there, then we add a
server and verify if the addition is successful.

3.11 Now check if the Ports to which the storage is zoned has the
port security enabled? If it is not, then we enable the port
security.

3.12 Create and Allocate the two 25GB volumes to the server. Verify
that the server can see the attached volumes.

3.13 Expand the pool with the second Parity group. View the pool
details to verify if both Parity Groups are there in the pool.

3.14 At this stage, RDP to your server to check if the server can “See”
the volumes that you allocated to the server.

End of Activity 3

End of Lab 10

10-6
 Lab 10: Command Line Interface (CLI)

Solution to the Lab Project

This section contains the solution for the lab exercise given above.
How to use the solution?
1. Ensure that you replace the Administrator IP, with the one assigned to you.
2. Replace the storage to the one assigned to you.
3. Replace the server(s) and WWNs assigned to you.
4. Remember, cut and paste of the command will NOT work.

Serial Number 410927/G400

SVP IP 192.168.0.115
C1/C2 IP (use this only if you are using a P2 (192.168.0.113,114)
machine without an SVP)
Authentication (user/password) Maintenance/raid-maintenance
IP Address of Administrator? 192.168.0.150
Is it installed with OpsCenter If yes, use port number 20961 else don’t use
the port number
Server name Server53
Server WWNs 100000051e56c84e, 100000051e56c84f
Which ports of storage are zoned to the server 1A/2A

3.1 Generate a token.

C:\cURL\bin>curl -k -I --Basic
https://192.168.0.150:20961/v1/security/tokens -X POST -u
sysadmin:sysadmin

HTTP/1.1 200
Server: nginx/1.18.0
Date: Mon, 28 Sep 2020 17:33:52 GMT
Content-Type: application/json;charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
X-Auth-Token: 269d3723-7ec9-49fa-a4dd-86ba5e822f21
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: 0
X-Frame-Options: DENY
Strict-Transport-Security: max-age=31536000; includeSubdomains
Content-Security-Policy: block-all-mixed-content, frame-ancestors
'self'

10-7
Lab 10: Command Line Interface (CLI)

3.2 Check if the G400 (410927) is registered.

C:\cURL\bin>curl -k -H "X-Auth-Token: 269d3723-7ec9-49fa-a4dd-86ba5e822f21"

https://192.168.0.150:20961/v1/storage-systems

{"resources":[],"total":0,"nextToken":null}
(There is no storage system registered)
3.3 Register the VSP G400 system.

a. First, create a json file with the contents of storage that you wish to register.

File name: addg400.json (create using notepad and place it in c:\curl\bin

{
"password":"Parity-maintenance",
"username":"maintenance",
"ipAddress":"192.168.0.115"
}
b. Next, add the storage.

Note: Since it’s a POST command, instead of -X POST we can use -d. Also note that POST
is an async command. When you issue the command, the system creates a job. Check if
the job has completed.
c. When you issue the command, see that the job is IN PROGRESS.

C:\cURL\bin>curl -k -d @addg400.json -H "Content-type: application/json" -H

"X-Auth-Token: 269d3723-7ec9-49fa-a4dd-86ba5e822f21"
https://192.168.0.150:20961/v1/storage-systems

{"jobId":"31cfcfac-0739-4c6e-a8da-034100b6de70","title":{"text":"Create
storage
system","messageCode":"CreateStorageSystemsJobTitleMessage","parameters":{}},
"user":"sysadmin","status":"IN_PROGRESS","startDate":1601314842009,"endDate":
null,"parentJobId":null,"reports":[],"links":[{"rel":"_self","href":"/v1/jobs
/31cfcfac-0739-4c6e-a8da-
034100b6de70"}],"tags":[{"tag":"rainier"}],"isSystem":false}
d. Once the job is SUCCESSFUL, you can see the storage listed successfully. (Verify this in
the GUI as well). The jq-win64 makes the clear printing of json output. For the
remaining command to work on this storage, use the storageSystemId field that is
410927 in this case. (This is the serial number of the box)

C:\cURL\bin>curl -k -H "X-Auth-Token: 269d3723-7ec9-49fa-a4dd-86ba5e822f21"

https://192.168.0.150:20961/v1/storage-systems | jq-win64
{
"resources": [
{
"storageSystemId": "410927",

10-8
 Lab 10: Command Line Interface (CLI)

"storageSystemName": "G400-410927",
"accessible": true,
"model": "VSP G400",
"svpIpAddress": "192.168.0.115",
"rmiPortNumber": null,
"svpHttpsPortNumber": 443,
"gum1IpAddress": "192.168.0.113",
"gum2IpAddress": "192.168.0.114",
"unified": false,
"firmwareVersion": "83-05-26-40/00",
"horcmVersion": "01-55-03/03",
"cacheCapacity": 101200166912,
"totalUsableCapacity": 0,
"allocatedToPool": 0,
"unallocatedToPool": 0,
"usedCapacity": 0,
"availableCapacity": 0,
"subscribedCapacity": 0,
"unusedDisks": 10,
"unusedDisksCapacity": 126200000000000,
"statusMessage": null,
"gadSummary": "NOT_AVAILABLE",
"dataReductionSavingsRate": 0,
"capacityEfficiencyRate": 0,
"migrationTaskCount": 0,
"primaryGumNumber": 1,
"username": "maintenance",
"totalEfficiency": null,
"lastRefreshedTime": 1601314907400,
"svpFlashState": "FLASH_ONLY"
}
],
"total": 1,
"nextToken": null
}

10-9
Lab 10: Command Line Interface (CLI)

3.4 List the drives in the system.

(There are 95 drives in this system, so the output is truncated to show a few only).

Note: We need to create a diskID Parity Group. The purpose of a drive can be FREE, DATA or
SPARE. Only FREE drives can be used to create Parity Group. The drives in a Parity Group should
have the same model. (same disk type).
C:\cURL\bin>curl -k -H "X-Auth-Token: 269d3723-7ec9-49fa-a4dd-86ba5e822f21"
https://192.168.0.150:20961/v1/storage-systems/410927/disks | jq-win64
{
"resources": [
{
"diskId": "L0J85G5J",
"storageSystemId": "410927",
"serialNumber": "L0J85G5J",
"location": "HDD00-33",
"model": "DKR5E-J1R2SS",
"capacityInBytes": 1200000000000,
"version": "GC-GC",
"speed": 10000,
"type": "SAS",
"purpose": "SPARE",
"parityGroupId": null
},
{
"diskId": "L0JEAAXJ",
"storageSystemId": "410927",
"serialNumber": "L0JEAAXJ",
"location": "HDD00-11",
"model": "DKR5E-J1R2SS",
"capacityInBytes": 1200000000000,
"version": "GC-GC",
"speed": 10000,
"type": "SAS",
"purpose": "FREE",
"parityGroupId": null
},
{
"diskId": "L0H542YJ",
"storageSystemId": "410927",
"serialNumber": "L0H542YJ",
"location": "HDD00-57",
"model": "DKR5E-J1R2SS",
"capacityInBytes": 1200000000000,
"version": "GC-GC",
"speed": 10000,
"type": "SAS",
"purpose": "FREE",
"parityGroupId": null
},
{
"diskId": "S0M5E4V10000M542QP7H",
"storageSystemId": "410927",
"serialNumber": "S0M5E4V10000M542QP7H",
"location": "HDD01-00",

10-10
 Lab 10: Command Line Interface (CLI)

"model": "DKS5E-J600SS",
"capacityInBytes": 600000000000,
"version": "7F-0D",
"speed": 10000,
"type": "SAS",
"purpose": "FREE",
"parityGroupId": null
},
{
"diskId": "L0J8JE3K",
"storageSystemId": "410927",
"serialNumber": "L0J8JE3K",
"location": "HDD00-40",
"model": "DKR5E-J1R2SS",
"capacityInBytes": 1200000000000,
"version": "GC-GC",
"speed": 10000,
"type": "SAS",
"purpose": "FREE",
"parityGroupId": null
},
…………………………. Many lines from here are deleted…………………………………………………………….
{
"diskId": "Z1Z94NCE0000R547QP5Z",
"storageSystemId": "410927",
"serialNumber": "Z1Z94NCE0000R547QP5Z",
"location": "HDD02-05",
"model": "DKS2E-H4R0SS",
"capacityInBytes": 4000000000000,
"version": "7F-A6",
"speed": 7200,
"type": "SAS",
"purpose": "SPARE",
"parityGroupId": null
],
"total": 95,
"nextToken": null
}
3.5 Create two Parity Groups. Check if there are any Parity Group in the system.

C:\cURL\bin>curl -k -H "X-Auth-Token: 269d3723-7ec9-49fa-a4dd-86ba5e822f21"

https://192.168.0.150:20961/v1/storage-systems/410927/parity-groups | jq-
win64
{
"resources": [],
"total": 0,
"nextToken": null
}
a. First, create addrg1.json. (a file that contains the details)

File name : addrg1json (create using notepad and place it in c:\curl\bin)

{
"diskIds":[ "L0J8JE3K","L0JBS1JJ","L0JEAAXJ","L0H542YJ"],
"ParityLevel":"Parity5",
"ParityLayout":"3D+1P"
}

10-11
Lab 10: Command Line Interface (CLI)

b. Issue the command to create the Parity Group.

C:\cURL\bin>curl -k -d @addrg1.json -H "Content-type: application/json" -H

"X-Auth-Token: 269d3723-7ec9-49fa-a4dd-86ba5e822f21"
https://192.168.0.150:20961/v1/storage-systems/410927/parity-groups

{"jobId":"1e3fccd5-a555-45e9-805e-91153ffd3a83","title":{"text":"Create
parity
group","messageCode":"CreateParityGroupJobTitleMessage","parameters":{}},"use
r":"sysadmin","status":"IN_PROGRESS","startDate":1601315954412,"endDate":null
,"parentJobId":null,"reports":[],"links":[{"rel":"_self","href":"/v1/jobs/1e3
fccd5-a555-45e9-805e-
91153ffd3a83"}],"tags":[{"tag":"rainier"}],"isSystem":false}
Note: You can use this command to check the status of a job.
C:\cURL\bin>curl -k -H "X-Auth-Token: 269d3723-7ec9-49fa-a4dd-86ba5e822f21"
https://192.168.0.150:20961/v1/jobs/1e3fccd5-a555-45e9-805e-91153ffd3a83"
c. Create the second Parity Group. Modify the addrg1.json file to have the Parity Group
details.

File name : addrg1json

{
"diskIds":[ "L0JBJKSJ","L0J8GZRK","L0J8HS4K","L0JE6J6J"],
"ParityLevel":"Parity5",
"ParityLayout":"3D+1P"
}
d. Issue the command to create the Parity Group.

C:\cURL\bin>curl -kd @addrg1.json -H "Accept: application/json" -H "content-

type: application/json" -H "X-Auth-Token: 269d3723-7ec9-49fa-a4dd-
86ba5e822f21" -X POST "https://192.168.0.150:20961/v1/storage-
systems/410927/parity-groups" | jq-win64
{
"jobId": "23bac0ec-b30c-4532-a4b0-69161e227f8f",
"title": {
"text": "Create parity group",
"messageCode": "CreateParityGroupJobTitleMessage",
"parameters": {}
},
"user": "sysadmin",
"status": "IN_PROGRESS",
"startDate": 1601401688136,
"endDate": null,
"parentJobId": null,
"reports": [],
"links": [
{
"rel": "_self",
"href": "/v1/jobs/23bac0ec-b30c-4532-a4b0-69161e227f8f"
}
],
"tags": [
{
"tag": "rainier"

10-12
 Lab 10: Command Line Interface (CLI)

}
],
"isSystem": false
}

3.6 Verify if the Parity groups have been created successfully. Basic Volumes are automatically
created when the Parity Group is created.

C:\cURL\bin>curl -k -H "X-Auth-Token: 269d3723-7ec9-49fa-a4dd-86ba5e822f21" https://192.168.0.150:20961/v1/storage-

systems/410927/parity-groups | jq-win64

{
"resources": [
{
"parityGroupId": "1-1",
"storageSystemId": "410927",
"ParityLevel": "Parity5",
"ParityLayout": "3D+1P",
"diskSpec": {
"type": "SAS",
"speed": 10000,
"capacityInBytes": 1200000000000
},
"totalCapacityInBytes": 3458360672256,
"uninitializedCapacityInBytes": 786432,
"availableCapacityInBytes": 0,
"physicalCapacityInBytes": 3458360672256,
"status": "IN_USE",
"encryption": false,
"compression": false,
"nasBoot": false
},
{
"parityGroupId": "1-2",
"storageSystemId": "410927",
"ParityLevel": "Parity5",
"ParityLayout": "3D+1P",
"diskSpec": {
"type": "SAS",
"speed": 10000,
"capacityInBytes": 1200000000000
},
"totalCapacityInBytes": 3458360672256,
"uninitializedCapacityInBytes": 786432,
"availableCapacityInBytes": 3458359885824,
"physicalCapacityInBytes": 3458360672256,
"status": "QUICK_FORMATTING",
"encryption": false,
"compression": false,
"nasBoot": false
}
],
"total": 2,
"nextToken": null
}

Both the Parity groups are listed here.

10-13
Lab 10: Command Line Interface (CLI)

3.7 Using the PG 1-1, create a pool first.

File : addpool.json
{
"label":"Oracle",
"type":"THIN",
"parityGroupIds":["1-1"]
}
Note: For the parityGroupIds entry, the value is a list. A list is a collection. A Pool can be created
with many parity groups. These are listed within the square brackets. In the above example the
Pool is created with just one parity group. Also, we are creating a thin pool. A tiered or snap
pool can also be created.
C:\cURL\bin>curl -k -d @addpool.json -H "Content-type: application/json" -H
"X-Auth-Token: 269d3723-7ec9-49fa-a4dd-86ba5e822f21"
https://192.168.0.150:20961/v1/storage-systems/410927/storage-pools

{"jobId":"8ddad42c-a289-4a4f-8493-6852a439a744","title":{"text":"Creating
pool on Storage System
410927.","messageCode":"CreatePoolJobTitleMessage","parameters":{"storageSyst
emId":"410927"}},"user":"sysadmin","status":"IN_PROGRESS","startDate":1601316
839477,"endDate":null,"parentJobId":null,"reports":[],"links":[{"rel":"_self"
,"href":"/v1/jobs/8ddad42c-a289-4a4f-8493-
6852a439a744"}],"tags":[{"tag":"rainier"}],"isSystem":false}
Check the status of the job until it completes.
C:\cURL\bin>curl -k -H “Accept: application/json” -H "X-Auth-Token:
269d3723-7ec9-49fa-a4dd-86ba5e822f21"
https://192.168.0.150:20961/v1/jobs/8ddad42c-a289-4a4f-8493-6852a439a744" |
jq-win64

{
"jobId": "8ddad42c-a289-4a4f-8493-6852a439a744",
"title": {
"text": "Creating pool on Storage System 410927.",
"messageCode": "CreatePoolJobTitleMessage",
"parameters": {
"storageSystemId": "410927"
}
},
"user": "sysadmin",
"status": "IN_PROGRESS",
"startDate": 1601316839477,
"endDate": null,
"parentJobId": null,
"reports": [
{
"reportMessage": {
"text": "Creating pool.",
"messageCode": "CreatePoolPreStepMessage",
"parameters": {}
},
"severity": "INFORMATION",
"creationDate": 1601316839779
},

10-14
 Lab 10: Command Line Interface (CLI)

{
"reportMessage": {
"text": "Successfully created pool 0.",
"messageCode": "CreatePoolPostStepMessage",
"parameters": {
"storagePoolId": 0
}
},
"severity": "INFORMATION",
"creationDate": 1601316875476
}
],
"links": [
{
"rel": "_self",
"href": "/v1/jobs/8ddad42c-a289-4a4f-8493-6852a439a744"
}
],
"tags": [
{
"tag": "rainier"
}
],
"isSystem": false
}
3.8 List the pools to verify your pool is created. (Note that the name of our pool is Oracle.)

C:\cURL\bin>curl -k -H "X-Auth-Token: 269d3723-7ec9-49fa-a4dd-86ba5e822f21"

"https://192.168.0.150:20961/v1/storage-systems/410927/storage-pools" | jq-
win64
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left Speed
100 1443 0 1443 0 0 4399 0 --:--:-- --:--:-- --:--:--
4399
{
"resources": [
{
"storagePoolId": 0,
"storageSystemId": "410927",
"label": "Oracle",
"capacityInBytes": 3453896097792,
"usedCapacityInBytes": 0,
"availableCapacityInBytes": 3453896097792,
"usedSubscribedCapacityInBytes": 0,
"logicalCapacityInBytes": 3453896097792,
"usedLogicalCapacityInBytes": 0,
"availableLogicalCapacityInBytes": 3453896097792,
"type": "THIN",
"utilizationThreshold1": 70,
"utilizationThreshold2": 80,
"subscriptionLimit": {
"unlimited": false,
"value": 100
},
"usedSubscription": 0,

10-15
Lab 10: Command Line Interface (CLI)

"availableSubscription": {
"unlimited": false,
"value": 100
},
"status": "NORMAL",
"parityGroups": [
{
"id": "1-1",
"encryption": false,
"compression": false,
"compressionSupported": false
}
],
"externalParityGroupIds": [],
"tiers": [
{
"tierId": 3,
"tier": "Silver",
"capacity": null,
"usedCapacity": null,
"usage": null,
"bufferSpace": null,
"performanceUtilization": null
}
],
"tieringMode": "NONE",
"monitoringMode": "NONE",
"monitoringCycle": null,
"monitoringPeriodStart": null,
"monitoringPeriodEnd": null,
"relocationSpeed": null,
"activeFlashEnabled": false,
"ddmEnabled": false,
"encrypted": "NO",
"fmcCompressed": "NO",
"deduplicationEnabled": false,
"compressionDetails": {
"compressionRate": 1,
"deduplicationRate": 1,
"savingsPercentage": 0
},
"fmcCompressionDetails": {
"expansionRate": 1,
"compressionRate": 1,
"savingsPercentage": 0
},
"deduplicationSystemDataCapacityInBytes": 0,
"nasBoot": false,
"dataReductionSavingsRate": 0,
"capacityEfficiencyRate": 0,
"suspendSnapshot": true,
"totalEfficiency": null
}
],
"total": 1,
"nextToken": null
}

10-16
 Lab 10: Command Line Interface (CLI)

3.9 Check if your server is added. If not, then add the server.

C:\cURL\bin>curl -k -H "X-Auth-Token: 67331d98-80df-47f1-820e-22b626525486"

https://192.168.0.150:20961/v1/compute/servers | jq-win64
{
"resources": [],
"total": 0,
"nextToken": null
}
a. There are no servers. To add a server, create a json file.

File name : server.json

{
"servers":[
{
"protocol":"FIBRE",
"serverName": "server53",
"ipAddress":"192.168.0.53",
"osType":"WIN_EX",
"wwpns":["100000051e56c84e","100000051e56c84f"],
"description":"Windows 2016"
}
]
}
b. Next, add the server.

C:\cURL\bin>curl -kd @server.json -H "Content-type: application/json" -H "X-

Auth-Token: 67331d98-80df-47f1-820e-22b626525486"
https://192.168.0.150:20961/v1/compute/servers

{"jobId":"694a94b9-c8b5-452d-8631-29a6770637ed","title":{"text":"Onboarding
servers","messageCode":"CreateServersBulkJobTitleMessage","parameters":{}},"u
ser":"sysadmin","status":"IN_PROGRESS","startDate":1601393996915,"endDate":nu
ll,"parentJobId":null,"reports":[],"links":[{"rel":"_self","href":"/v1/jobs/6
94a94b9-c8b5-452d-8631-
29a6770637ed"}],"tags":[{"tag":"rainier"}],"isSystem":false}
c. Next, verify if the server is added successfully.

C:\cURL\bin>curl -k -H "X-Auth-Token: 67331d98-80df-47f1-820e-22b626525486"

https://192.168.0.150:20961/v1/compute/servers | jq-win64
{
"resources": [
{
"serverId": 2,
"protocol": "FIBRE",
"serverName": "server53",
"description": "Windows 2016",
"ipAddress": "192.168.0.53",
"wwpns": [
"100000051E56C84E",
"100000051E56C84F"
],
"iscsiNames": [],
"osType": "WIN_EX",

10-17
Lab 10: Command Line Interface (CLI)

"chapUser": null,
"attachedVolumeCount": 0,
"dataProtectionSummary": {
"replicationType": [],
"protection": "UNPROTECTED",
"hasFailures": false
},
"dpStatus": "Success"
}
],
"total": 1,
"nextToken": null
}

10-18
 Lab 10: Command Line Interface (CLI)

3.10 Now check if the Ports to which the storage is zoned has the port security enabled. If not, then
enable the port security. (Check for port CL1-A and CL2-A).

C:\cURL\bin>curl -k -H "Accept: application/json" -H "X-Auth-Token:

3ec3332e-b9fe-43ef-a7be-a2573ff6562c"
https://192.168.0.150:20961/v1/storage-systems/410927/storage-ports/CL1-A |
jq-win64

{
"storagePortId": "CL1-A",
"storageSystemId": "410927",
"wwn": "50060E80122AAF00",
"attributes": [
"RCU_TARGET_PORT",
"MCU_INITIATOR_PORT",
"TARGET_PORT",
"EXTERNAL_INITIATOR_PORT"
],
"speed": "AUTO",
"type": "FIBRE",
"loopId": "EF",
"topology": "FABRIC_ON_POINT_TO_POINT",
"securitySwitchEnabled": false,
"vsmPort": false,
"iscsiPortInformation": null,
"t10PiStatus": "DISABLED"
}

C:\cURL\bin>curl -k -H "Accept: application/json" -H "X-Auth-Token:

3ec3332e-b9fe-43ef-a7be-a2573ff6562c"
https://192.168.0.150:20961/v1/storage-systems/410927/storage-ports/CL2-A |
jq-win64

{
"storagePortId": "CL2-A",
"storageSystemId": "410927",
"wwn": "50060E80122AAF10",
"attributes": [
"RCU_TARGET_PORT",
"MCU_INITIATOR_PORT",
"TARGET_PORT",
"EXTERNAL_INITIATOR_PORT"
],
"speed": "AUTO",
"type": "FIBRE",
"loopId": "EF",
"topology": "FABRIC_ON_POINT_TO_POINT",
"securitySwitchEnabled": false,
"vsmPort": false,
"iscsiPortInformation": null,
"t10PiStatus": "DISABLED"
}

For both the ports the security switch (Port security) is disabled. This needs to be enabled.
a. For that, create a json file first.

10-19
Lab 10: Command Line Interface (CLI)

File : port.json
{
"securitySwitchEnabled":true
}
b. Next, we enable the port security for both the ports.

C:\cURL\bin>curl -kd @port.json -H "Accept: application/json" -H "content-

type: application/json" -H "X-Auth-Token: 3ec3332e-b9fe-43ef-a7be-
a2573ff6562c" https://192.168.0.150:20961/v1/storage-systems/410927/storage-
ports/CL1-A | jq-win64

{
"jobId": "d387f16b-6905-4ab1-a78e-b19a147bca84",
"title": {
"text": "Update Storage Port",
"messageCode": "UpdateStoragePortJobTitleMessage",
"parameters": {}
},
"user": "sysadmin",
"status": "IN_PROGRESS",
"startDate": 1601399108245,
"endDate": null,
"parentJobId": null,
"reports": [],
"links": [
{
"rel": "_self",
"href": "/v1/jobs/d387f16b-6905-4ab1-a78e-b19a147bca84"
}
],
"tags": [
{
"tag": "rainier"
}
],
"isSystem": false
}

We then run the command for port CL2-A

C:\cURL\bin>curl -kd @port.json -H "Accept: application/json" -H "content-

type: application/json" -H "X-Auth-Token: 3ec3332e-b9fe-43ef-a7be-
a2573ff6562c" https://192.168.0.150:20961/v1/storage-systems/410927/storage-
ports/CL2-A | jq-win64
{
"jobId": "804e546e-67be-44ca-b9fb-c63bc0bc9e11",
"title": {
"text": "Update Storage Port",
"messageCode": "UpdateStoragePortJobTitleMessage",
"parameters": {}
},
"user": "sysadmin",
"status": "IN_PROGRESS",
"startDate": 1601399167708,
"endDate": null,
"parentJobId": null,

10-20
 Lab 10: Command Line Interface (CLI)

"reports": [],
"links": [
{
"rel": "_self",
"href": "/v1/jobs/804e546e-67be-44ca-b9fb-c63bc0bc9e11"
}
],
"tags": [
{
"tag": "rainier"
}
],
"isSystem": false
}
c. Once the commands run successfully, we can verify if the port security has been
enabled.

C:\cURL\bin>curl -k -H "Accept: application/json" -H "X-Auth-Token:

3ec3332e-b9fe-43ef-a7be-a2573ff6562c"
https://192.168.0.150:20961/v1/storage-systems/410927/storage-ports/CL1-A |
jq-win64

{
"storagePortId": "CL1-A",
"storageSystemId": "410927",
"wwn": "50060E80122AAF00",
"attributes": [
"RCU_TARGET_PORT",
"MCU_INITIATOR_PORT",
"TARGET_PORT",
"EXTERNAL_INITIATOR_PORT"
],
"speed": "AUTO",
"type": "FIBRE",
"loopId": "EF",
"topology": "FABRIC_ON_POINT_TO_POINT",
"securitySwitchEnabled": true,
"vsmPort": false,
"iscsiPortInformation": null,
"t10PiStatus": "DISABLED"
}

C:\cURL\bin>curl -k -H "Accept: application/json" -H "X-Auth-Token:

3ec3332e-b9fe-43ef-a7be-a2573ff6562c"
https://192.168.0.150:20961/v1/storage-systems/410927/storage-ports/CL2-A |
jq-win64

{
"storagePortId": "CL2-A",
"storageSystemId": "410927",
"wwn": "50060E80122AAF10",
"attributes": [
"RCU_TARGET_PORT",
"MCU_INITIATOR_PORT",
"TARGET_PORT",
"EXTERNAL_INITIATOR_PORT"

10-21
Lab 10: Command Line Interface (CLI)

],
"speed": "AUTO",
"type": "FIBRE",
"loopId": "EF",
"topology": "FABRIC_ON_POINT_TO_POINT",
"securitySwitchEnabled": true,
"vsmPort": false,
"iscsiPortInformation": null,
"t10PiStatus": "DISABLED"
}

3.11 Create and Allocate the two 25GB volumes to the server. Verify that the server can see the
attached volumes. Note, we will not be protecting the volume, but from Administrator version
10.5, the create-attach method is deprecated, we need to create-attach-protect. See the json
file for more information.

a. First, we create the json file.

File : attach.json
{
"storageSystemId":"410927",
"ports":[{
"serverId":2, "serverWwns": ["100000051e56c84e"],
"portIds":["CL1-A"]
},
{
"serverId":2, "serverWwns": ["100000051e56c84f"],
"portIds":["CL2-A"]
}],
"volumes":[{
"poolType":"Silver",
"poolId":0,
"numberOfVolumes":2,
"label":"Project",
"sufix":0,
"capacity":"26843545600"
}],
"skipProtection":true
}
Note: The capacity is in bytes. The capacity here is 25GB. Multiply by 1024x1024x1024 to
get the capacity in bytes. The “skipProtection” is to mention that just want to create and
attach only.
C:\cURL\bin>curl -kd @attach.json -H "Content-type: application/json" -H "X-
Auth-Token: 67331d98-80df-47f1-820e-22b626525486"
https://192.168.0.150:20961/v1/volume-manager/create-attach-protect

{"jobId":"24b0618e-7f35-41f7-9cb5-ab788de88cf5","title":{"text":"Create
volumes, attach to servers and set up data
protection","messageCode":"CreateAttachAndProtectVolumesJobTitleMessage","par
ameters":{}},"user":"sysadmin","status":"IN_PROGRESS","startDate":16013974367
65,"endDate":null,"parentJobId":null,"reports":[],"links":[{"rel":"_self","hr

10-22
 Lab 10: Command Line Interface (CLI)

ef":"/v1/jobs/24b0618e-7f35-41f7-9cb5-
ab788de88cf5"}],"tags":[{"tag":"rainier"}],"isSystem":false}

b. Wait till we can verify that the job is a SUCCESS.

C:\cURL\bin>curl -k -H "Accept: application/json" -H "X-Auth-Token:

67331d98-80df-47f1-820e-22b626525486"
https://192.168.0.150:20961/v1/jobs/24b0618e-7f35-41f7-9cb5-ab788de88cf5 |
jq-win64
{
"jobId": "24b0618e-7f35-41f7-9cb5-ab788de88cf5",
"title": {
"text": "Create volumes, attach to servers and set up data protection",
"messageCode": "CreateAttachAndProtectVolumesJobTitleMessage",
"parameters": {}
},
"user": "sysadmin",
"status": "SUCCESS",
"startDate": 1601397436765,
"endDate": 1601397468616,
"parentJobId": null,
"reports": [],
"links": [
{
"rel": "_self",
"href": "/v1/jobs/24b0618e-7f35-41f7-9cb5-ab788de88cf5"
}
],
"tags": [
{
"tag": "rainier"
}
],
"isSystem": false
}
The allocation is a success.
c. Now check on the server side if the volumes are attached.

C:\cURL\bin>curl -k -H "Accept: application/json" -H "X-Auth-Token:

3ec3332e-b9fe-43ef-a7be-a2573ff6562c"
"https://192.168.0.150:20961/v1/compute/servers/attached-
volumes?q=serverId:2" | jq-win64

{
"resources": [
{
"volumeId": 2,
"storageSystemId": "410927",
"poolId": "0",
"poolName": "Oracle",
"label": "Project1",
"size": 26843545600,
"usedCapacity": 0,
"availableCapacity": 26843545600,

10-23
Lab 10: Command Line Interface (CLI)

"utilization": 0,
"attributes": [
"THIN"
],
"status": "NORMAL",
"type": "THIN",
"provisioningStatus": "ATTACHED",
"portIds": [
"CL1-A",
"CL2-A"
],
"hostGroupNames": [
"server53"
],
"luns": [
1
],
"numberOfLunPaths": 2,
"attachedVolumeServerSummary": [
{
"serverId": 2,
"paths": [
{
"storagePortId": "CL2-A",
"storageSystemId": "410927",
"lun": 1,
"hostGroupId": "CL2-A-1",
"name": "server53",
"hostMode": "WIN_EX",
"wwns": [
"100000051E56C84F"
],
"hostModeOptions": [
40,
73
],
"iscsiTargetInformation": null,
"preferredPath": true
},
{
"storagePortId": "CL1-A",
"storageSystemId": "410927",
"lun": 1,
"hostGroupId": "CL1-A-1",
"name": "server53",
"hostMode": "WIN_EX",
"wwns": [
"100000051E56C84E"
],
"hostModeOptions": [
40,
73
],
"iscsiTargetInformation": null,
"preferredPath": true
}
]

10-24
 Lab 10: Command Line Interface (CLI)

}
],
"dataProtectionSummary": {
"replicationType": [],
"volumeType": [
"UNPROTECTED"
],
"replicationGroupIdMap": {},
"hasFailures": false,
"secondaryVolumeCount": 0,
"secondaryVolumeFailures": 0
},
"gadSummary": {
"vsmId": null,
"virtualLdevId": null,
"volumeType": "NOT_AVAILABLE",
"pairStatus": "NONE",
"consistencyId": null
},
"dkcDataSavingType": "NONE",
"virtualStorageMachineInformation": {
"virtualStorageMachineId": "410927-VSPF400-F600andVSPG400-G600",
"storageSystemId": "410927",
"model": "VSP F400, F600 and VSP G400, G600",
"virtualVolumeId": 2
},
"resourceGroupId": 0,
"resourceGroupName": "meta_resource",
"migrationSummary": {
"ownerTaskId": null,
"migrationType": "NONE"
},
"aluaEnabled": false,
"tieringPolicy": {
"id": 0,
"name": "All",
"userDefined": false
},
"t10PiEnabled": false,
"serverId": 2,
"paths": [
{
"storagePortId": "CL2-A",
"storageSystemId": "410927",
"lun": 1,
"hostGroupId": "CL2-A-1",
"name": "server53",
"hostMode": "WIN_EX",
"wwns": [
"100000051E56C84F"
],
"hostModeOptions": [
40,
73
],
"iscsiTargetInformation": null,
"preferredPath": true

10-25
Lab 10: Command Line Interface (CLI)

},
{
"storagePortId": "CL1-A",
"storageSystemId": "410927",
"lun": 1,
"hostGroupId": "CL1-A-1",
"name": "server53",
"hostMode": "WIN_EX",
"wwns": [
"100000051E56C84E"
],
"hostModeOptions": [
40,
73
],
"iscsiTargetInformation": null,
"preferredPath": true
}
]
},
{
"volumeId": 3,
"storageSystemId": "410927",
"poolId": "0",
"poolName": "Oracle",
"label": "Project2",
"size": 26843545600,
"usedCapacity": 0,
"availableCapacity": 26843545600,
"utilization": 0,
"attributes": [
"THIN"
],
"status": "NORMAL",
"type": "THIN",
"provisioningStatus": "ATTACHED",
"portIds": [
"CL1-A",
"CL2-A"
],
"hostGroupNames": [
"server53"
],
"luns": [
2
],
"numberOfLunPaths": 2,
"attachedVolumeServerSummary": [
{
"serverId": 2,
"paths": [
{
"storagePortId": "CL2-A",
"storageSystemId": "410927",
"lun": 2,
"hostGroupId": "CL2-A-1",
"name": "server53",

10-26
 Lab 10: Command Line Interface (CLI)

"hostMode": "WIN_EX",
"wwns": [
"100000051E56C84F"
],
"hostModeOptions": [
40,
73
],
"iscsiTargetInformation": null,
"preferredPath": true
},
{
"storagePortId": "CL1-A",
"storageSystemId": "410927",
"lun": 2,
"hostGroupId": "CL1-A-1",
"name": "server53",
"hostMode": "WIN_EX",
"wwns": [
"100000051E56C84E"
],
"hostModeOptions": [
40,
73
],
"iscsiTargetInformation": null,
"preferredPath": true
}
]
}
],
"dataProtectionSummary": {
"replicationType": [],
"volumeType": [
"UNPROTECTED"
],
"replicationGroupIdMap": {},
"hasFailures": false,
"secondaryVolumeCount": 0,
"secondaryVolumeFailures": 0
},
"gadSummary": {
"vsmId": null,
"virtualLdevId": null,
"volumeType": "NOT_AVAILABLE",
"pairStatus": "NONE",
"consistencyId": null
},
"dkcDataSavingType": "NONE",
"virtualStorageMachineInformation": {
"virtualStorageMachineId": "410927-VSPF400-F600andVSPG400-G600",
"storageSystemId": "410927",
"model": "VSP F400, F600 and VSP G400, G600",
"virtualVolumeId": 3
},
"resourceGroupId": 0,
"resourceGroupName": "meta_resource",

10-27
Lab 10: Command Line Interface (CLI)

"migrationSummary": {
"ownerTaskId": null,
"migrationType": "NONE"
},
"aluaEnabled": false,
"tieringPolicy": {
"id": 0,
"name": "All",
"userDefined": false
},
"t10PiEnabled": false,
"serverId": 2,
"paths": [
{
"storagePortId": "CL2-A",
"storageSystemId": "410927",
"lun": 2,
"hostGroupId": "CL2-A-1",
"name": "server53",
"hostMode": "WIN_EX",
"wwns": [
"100000051E56C84F"
],
"hostModeOptions": [
40,
73
],
"iscsiTargetInformation": null,
"preferredPath": true
},
{
"storagePortId": "CL1-A",
"storageSystemId": "410927",
"lun": 2,
"hostGroupId": "CL1-A-1",
"name": "server53",
"hostMode": "WIN_EX",
"wwns": [
"100000051E56C84E"
],
"hostModeOptions": [
40,
73
],
"iscsiTargetInformation": null,
"preferredPath": true
}
]
}
],
"total": 2,
"nextToken": null
}

10-28
 Lab 10: Command Line Interface (CLI)

3.12 Expand the pool with the second Parity Group. View the pool details to verify if both Parity
Groups are there in the pool. Create the addpool.json file.

{
"parityGroupIds":["1-2"]
}
Next, we add the Parity group to the Pool.
C:\cURL\bin>curl -kd @addpool.json -H "Accept: application/json" -H "content-
type: application/json" -H "X-Auth-Token: 0832b0a9-67ec-4948-9a75-
7e3fd397e28b" "https://192.168.0.150:20961/v1/storage-
systems/410927/storage-pools/0" | jq-win64
{
"jobId": "241d682f-6538-4531-8c63-beae0d5724c5",
"title": {
"text": "Updating pool 0 on Storage System 410927.",
"messageCode": "UpdatePoolJobTitleMessage",
"parameters": {
"storageSystemId": "410927",
"storagePoolId": 0
}
},
"user": "sysadmin",
"status": "IN_PROGRESS",
"startDate": 1601401954886,
"endDate": null,
"parentJobId": null,
"reports": [],
"links": [
{
"rel": "_self",
"href": "/v1/jobs/241d682f-6538-4531-8c63-beae0d5724c5"
}
],
"tags": [
{
"tag": "rainier"
}
],
"isSystem": false
}
Once the job status is successful, issue the next command to check the pool.
C:\cURL\bin>curl -k -H "Accept: application/json" -H "content-type:
application/json" -H "X-Auth-Token: 0832b0a9-67ec-4948-9a75-7e3fd397e28b"
"https://192.168.0.150:20961/v1/storage-systems/410927/storage-pools/0" | jq-
win64

{
"storagePoolId": 0,
"storageSystemId": "410927",
"label": "Oracle",
"capacityInBytes": 6912196214784,
"usedCapacityInBytes": 0,
"availableCapacityInBytes": 6912196214784,
"usedSubscribedCapacityInBytes": 54081355776,

10-29
Lab 10: Command Line Interface (CLI)

"logicalCapacityInBytes": 6912196214784,
"usedLogicalCapacityInBytes": 0,
"availableLogicalCapacityInBytes": 6912196214784,
"type": "THIN",
"utilizationThreshold1": 70,
"utilizationThreshold2": 80,
"subscriptionLimit": {
"unlimited": false,
"value": 100
},
"usedSubscription": 0,
"availableSubscription": {
"unlimited": false,
"value": 100
},
"status": "NORMAL",
"parityGroups": [
{
"id": "1-1",
"encryption": false,
"compression": false,
"compressionSupported": false
},
{
"id": "1-2",
"encryption": false,
"compression": false,
"compressionSupported": false
}
],
"externalParityGroupIds": [],
"tiers": [
{
"tierId": 3,
"tier": "Silver",
"capacity": null,
"usedCapacity": null,
"usage": null,
"bufferSpace": null,
"performanceUtilization": null
}
],
"tieringMode": "NONE",
"monitoringMode": "NONE",
"monitoringCycle": null,
"monitoringPeriodStart": null,
"monitoringPeriodEnd": null,
"relocationSpeed": null,
"activeFlashEnabled": false,
"ddmEnabled": false,
"encrypted": "NO",
"fmcCompressed": "NO",
"deduplicationEnabled": false,
"compressionDetails": {
"compressionRate": 1,
"deduplicationRate": 1,
"savingsPercentage": 0

10-30
 Lab 10: Command Line Interface (CLI)

},
"fmcCompressionDetails": {
"expansionRate": 1,
"compressionRate": 1,
"savingsPercentage": 0
},
"deduplicationSystemDataCapacityInBytes": 0,
"nasBoot": false,
"dataReductionSavingsRate": 0,
"capacityEfficiencyRate": 0,
"suspendSnapshot": true,
"totalEfficiency": null
}

End of Solution

10-31
Lab 10: Command Line Interface (CLI)

This page is left blank intentionally.

10-32