Installing and Configuring HCP Anywhere

and Hitachi Data Ingestor

HDI Cluster Initial Configuration

© Hitachi Vantara Corporation 2018. All rights reserved.

Module Objectives

 Upon completion of this module, you should be able to:

• Use Hitachi File Services Manager (HFSM) for initial setup
• Configure Hitachi Data Ingestor (HDI) cluster
 Integrate with Hitachi Content Platform (HCP) and tenant using management API
(MAPI)
 Create file system and namespace
 Integrate with active directory
 Create a common internet file system (CIFS) share and configure permissions
• Edit the migration task
• Configure the front-end network

© Hitachi Vantara Corporation 2018. All rights reserved.

Hitachi File Services Manager (HFSM)

© Hitachi Vantara Corporation 2018. All rights reserved.

Hitachi File Services Manager

HTTPS
Browser Some HFSM windows
connect directly
HDI
cluster
+
Hitachi Storage Array

HTTP(S)

Hitachi File Services Manager is an

HFSM
external application mandatory to
manage the HDI in cluster format. It
DB
Management server is only usable with HDI in cluster

© Hitachi Vantara Corporation 2018. All rights reserved.

Hitachi File Services Manager Installation

Note: Verify that the HFSM services are running

© Hitachi Vantara Corporation 2018. All rights reserved.

Configuration of Mozilla Firefox to Open HFSM

 To open the HDI integrated management console using Mozilla Firefox, you may need to
change the configuration of the web browser
 Introduce the URL: about:config
 Search the parameter: security.tls.insecure_failback_host and add the management IP
of Hitachi Data Ingestor (HDI)

© Hitachi Vantara Corporation 2018. All rights reserved.

Logging into HFSM

 Open the browser and enter the following URL:

http://IP_HFSM:23015/FileServicesManager/

Note: The case-sensitive and trailing

slash is mandatory.

User ID = system
Password = manager

© Hitachi Vantara Corporation 2018. All rights reserved.

HFSM Configuration Wizard

© Hitachi Vantara Corporation 2018. All rights reserved.

Configuration Wizard – Initial Screen

 Configuration Wizard opens Click icon to add picture

automatically if it is not
processing registered
nodes

 The wizard guides you

through the registration and
set up of the HDI cluster
system

© Hitachi Vantara Corporation 2018. All rights reserved.

 Configuration Wizard – Management IPs

 The management IP (physical

IPs) of nodes are assigned at
installation time

 The password for registration

of nodes is manager

 The storage system settings

are optional and only in case
you use Hitachi Unified
Storage (HUS) not for Hitachi
Virtual Storage Platform Gx00

0 © Hitachi Vantara Corporation 2018. All rights reserved.

 Configuration Wizard – Licenses

1 © Hitachi Vantara Corporation 2018. All rights reserved.

 Configuration Wizard – Cluster Names

 Select a name for the cluster

and names for each node

 HFSM automatically selects

the first logical device (LDEV)
allocated to the HDI cluster of
70GB size as cluster
management LU. But you can
change the selection

2 © Hitachi Vantara Corporation 2018. All rights reserved.

 Configuration Wizard – Virtual IPs for Mng0

 In this window, you can assign virtual

IPs to the management port (mng0)

 The virtual IPs are used to access the

shares of file system

 After this wizard, you can create

aggregates with the other ports of the
optional cards (front-end network) and
assign them virtual IPs (in other network
IP ranges)

 The virtual IPs and physical IPs belong

to the same network IP range

3 © Hitachi Vantara Corporation 2018. All rights reserved.

 Configuration Wizard – Optional Settings

• If the management network is not yet

connected to the front-end network,
select Default settings

• If the HCP is already configured with a

tenant for HDI, select Custom settings

4 © Hitachi Vantara Corporation 2018. All rights reserved.

 Configuration Wizard – DNS and Time

5 © Hitachi Vantara Corporation 2018. All rights reserved.

 Configuration Wizard – HCP Tenant Data

• Previously you created a tenant in

HCP, a tenant user with all the roles
assigned and MAPI enabled

• From HFSM, you are able to change

the password of the tenant user

6 © Hitachi Vantara Corporation 2018. All rights reserved.

 Configuration Wizard – Authentication

7 © Hitachi Vantara Corporation 2018. All rights reserved.

 Configuration Wizard – User Mapping RID

• The relative ID (RID) is part

of the user and group
security identifier (SID) of
windows

• HDI generates an automatic

user mapping SID to user
identifier (UID) or group
identifier (GID) using the
RID

8 © Hitachi Vantara Corporation 2018. All rights reserved.

 Configuration Wizard – Completion

9 © Hitachi Vantara Corporation 2018. All rights reserved.

 HFSM GUI Console

 Verify that the Hardware Status is Normal

 Verify that the Processing Node Status is Online

0 © Hitachi Vantara Corporation 2018. All rights reserved.

 Cluster Nodes Physical Status

 Verify the hardware status in detail

1 © Hitachi Vantara Corporation 2018. All rights reserved.

 Cluster Management

2 © Hitachi Vantara Corporation 2018. All rights reserved.

 Resource Groups

 There are 2 resource groups (RGs), one in each node

Normal Resource Group #2

Resource group #1
status Node1 Node2
Fixed IP: Virtual IP: Fixed IP: Virtual IP:
192.168.11.2 192.168.11.4 192.168.11.3 192.168.11.5

End user access

2º) Failback, manually only
through the
Virtual IP
1º) Automatically triggered by node failure
as well as manual failover

When failover
occurred Not available
Resource Group #1
Node1 Node2
Resource Group #2

Fixed IP: Virtual IP: Fixed IP: Virtual IP:

192.168.11.2 192.168.11.4 192.168.11.3 192.168.11.5

End user access through the Virtual IP

3 © Hitachi Vantara Corporation 2018. All rights reserved.
 Cluster Management

4 © Hitachi Vantara Corporation 2018. All rights reserved.

 Cluster Management

Each resource group is in its default node. The names

match and there is no failover.

5 © Hitachi Vantara Corporation 2018. All rights reserved.

 Cluster Management – Failover

The first resource group is not in its default node

The names do not match, but it is online, and there is a failover

6 © Hitachi Vantara Corporation 2018. All rights reserved.

 Cluster Management – Failback

After resolving the physical

problem, the node is ready for
failback (but the failback is manual)

7 © Hitachi Vantara Corporation 2018. All rights reserved.

 Front-End Network: Ports, Trunking, IPs
and VLAN

8 © Hitachi Vantara Corporation 2018. All rights reserved.

 HDI Cluster – Ethernet Port Names

HDI Cluster - 1GbE (4 ports) x 2

eth12 eth13 eth14 eth15

fc0002 fc0003 eth8 eth9 eth10 eth11

RAID Card Mezzanine
pm0 hb0 mng0 pm1 BMC

HDI Cluster - 10GbE (2 ports) x 2 + 1GbE (4 ports) x 1

xgbe8 xgbe9

xgbe4 xgbe5

fc0002 fc0003 eth8 eth9 eth10 eth11

RAID Card Mezzanine
pm0 hb0 mng0 pm1 BMC

9 © Hitachi Vantara Corporation 2018. All rights reserved.

 Ethernet Interfaces List

 Verify the
hardware
status in
detail

0 © Hitachi Vantara Corporation 2018. All rights reserved.

 HDI Cluster – Front-End Network

 Create new virtual ports (agrN or rdnN) as aggregates of front-end physical ports

DNS/DC Client
Front-end LAN
(Router)
agr1 agr1
HCP SMTP
pm0 xgbe4 xgbe5 pm0 xgbe4 xgbe5
Server
HDI Node 1 hb0 hb0 HDI Node 2 NTP
pm1 BMC mng0 pm1 BMC mng0

Management
PC
DC: data cache Management Switch
SMTP: simple mail
transfer protocol
HFSM SNMP
SNMP: simple network Management LAN
management protocol Station
1 © Hitachi Vantara Corporation 2018. All rights reserved.
 Flexible HDI Front-End Network: Trunking

 On an HDI system, link aggregation (agr) or link alternation (rdn) can be

used to perform trunking
• Link aggregation (IEEE 802.3ad): agr
 Increases the amount of bandwidth
 Uses each port part of the agr simultaneously (active-active)
 Creates virtual ports: agrN (agr0, agr1 and so on)

Note: If a link error occurs on some ports, processing can continue

by using other ports, connected to the same switch.

2 © Hitachi Vantara Corporation 2018. All rights reserved.

 Flexible HDI Front-End Network: Trunking

 Link aggregation (agr) is adequate if all the physical port components of

the same aggregation are connected to the same switch or splitting the
connections between 2 united switches using a technology that creates
a logical switch
• In this scenario the agr can be used as if this is only one switch, and all
interfaces are active

 Examples of technologies that can virtualize 2 physical switches that

behaves as one logical switch: Cisco virtual port channel (VPC) or
virtual switching system (VSS), Nortel split multilink trunking (SMLT) or
brocade multichassis trunking (MCT)

3 © Hitachi Vantara Corporation 2018. All rights reserved.

 Flexible HDI Front-End Network: 2 Independent
Switches

ID ID

STATUS STATUS 1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8 Cisco Nexus B22F Cisco Nexus B22F

xgbe4 xgbe5

Note: You cannot split the link aggregation

agr1 (Act-Act)
groups (LAG) to another independent switch.

4 © Hitachi Vantara Corporation 2018. All rights reserved.

 Flexible HDI Front-End Network: One Logical
Switch
VPC or VSS, SMLT, MCT result in one logical switch

ID ID

STATUS STATUS 1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8 Cisco Nexus B22F Cisco Nexus B22F

Note: It is only possible to split the LAG when xgbe4 xgbe5

there is a technology that generates a logical
switch with 2 physical switches.
agr1 (Act – Act)

5 © Hitachi Vantara Corporation 2018. All rights reserved.

 Creation of a Link Aggregation – Agr

6 © Hitachi Vantara Corporation 2018. All rights reserved.

 Setting Up Front-End Network Connectivity

1. Select Trunking Setup.

a) Select all available network ports.
b) Create a new link aggregate agr or
link alternation rdn.

2. Select Interface Management.

a) Add a new interface.
b) Pick agr0 as the underlying port and
provide IPs.

3. Select Routing Setup.

a) Add default route to agr0.

7 © Hitachi Vantara Corporation 2018. All rights reserved.

 Creation of a Link Aggregation – Agr

8 © Hitachi Vantara Corporation 2018. All rights reserved.

 Flexible HDI Networks: Link Alternation (Rdn)

 Link alternation – rdn

• One port is active and the other is kept as standby (active-passive)
• Increases the availability
• Creates virtual ports: rdnN (rdn0, rdn1, and so on)
• Ports are switched automatically

9 © Hitachi Vantara Corporation 2018. All rights reserved.

 Flexible HDI Networks: Link Alternation (Rdn)

 Adequate link alternation

• If the physical port component of the same aggregation is connected to
different physical switch (without creating a logical switch)

 Supports cascade trunking configuration:

xgbe4
(Active) Switch 1
IP1 /
agr1 xgbe5
VLAN X
rdn1
xbge8 Switch 2
agr2
(Standby) xgbe9

0 © Hitachi Vantara Corporation 2018. All rights reserved.

 Flexible HDI Front-End Network: 2 Independent
Switches
 Rdn (Availability)

ID ID

STATUS STATUS 1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8 Cisco Nexus B22F Cisco Nexus B22F

xgbe4 xgbe5

rdn1 (active – passive)

1 © Hitachi Vantara Corporation 2018. All rights reserved.

 Creation of a Link Alternation – Rdn

2 © Hitachi Vantara Corporation 2018. All rights reserved.

 Front-End Network VLAN Integration

 VLANs and IPs

• HDI provides plurality of subnets over the same agr or rdn by using VLANs
• Assign up to 256 different VLAN tags (from 1 through 4094) to same
port/agr/rdn (256 VLAN is the maximum per cluster)

3 © Hitachi Vantara Corporation 2018. All rights reserved.

 Front-End Network VLAN Integration

 Virtual LANs (VLANs) and IPs

• HDI can provide plurality of subnets over the same agr or rdn by using VLANs
• You can assign up to 256 different VLAN tags (from 1 through 4094) to the same port
or agr or rdn (256 VLAN is the maximum per HDI)
VLAN-1 Subnet 1 Subnet 2 VLAN-2

LAN Switch LAN Switch

xbge4 xgbe5
Note: The IP address used for the mng0, front-end
independent ports, the trunked virtual ports (agr or Node 1
rdn) and the virtual network interfaces for VLAN
File
(agr0) (VLAN1 and so on) must be in separate System #2
agr0 – IP1/VLAN1
network segments). agr0 – IP2/VLAN2

4 © Hitachi Vantara Corporation 2018. All rights reserved.

 Physical or Fixed IPs and Virtual IPs

5 © Hitachi Vantara Corporation 2018. All rights reserved.

 HDI Interface Management

6 © Hitachi Vantara Corporation 2018. All rights reserved.

 HDI Interface Management

7 © Hitachi Vantara Corporation 2018. All rights reserved.

 File System Creation

8 © Hitachi Vantara Corporation 2018. All rights reserved.

 HFSM File System Ownership

 File System Ownership

• Create file system through a node, and
use one or more logical units (LUs). The
Node 0 Node 1
resource group of this node is the owner resource group A resource group B
of the file system and owner of the LUs
components
• Only through this resource group, the file File File
system can be accessed system #1 system #2

• In HDI cluster, a LU cannot be shared by

LU without
multiple file systems (this means the LU FS
cannot be shared by the 2 nodes)
LU without
• The behavior of HDI cluster is like 2 HDI FS
singles

9 © Hitachi Vantara Corporation 2018. All rights reserved.

 HFSM File System Creation

0 © Hitachi Vantara Corporation 2018. All rights reserved.

 HFSM File System Creation

Hard Quota of the namespace

LU for file system

LU of 10GB as workspace for

active migration

Quotas enabled in this file

system after creation. If you
want to change, you must mount
the file system
1 © Hitachi Vantara Corporation 2018. All rights reserved.
 HFSM File System Creation

From version6.1 the migration task schedule is

hourly

A maximum duration of 0 means no time limit

Activates versioning in HCP for the

namespace. Users get .history in the
shares to recover files

Select Custom schedule

This sets a prune time for

the versioning in the
namespace (It controls the
oldest date under .history)

2 © Hitachi Vantara Corporation 2018. All rights reserved.

 HFSM File System Creation

Mark this box (By default it is not marked) if you

create common internet file system (CIFS) shares
in this file system. This enables advanced access
control list (ACL) into the file system

If you have selected

more than one LU for
file system with the
same characteristics
and size, use striping

In the storage Hitachi

Virtual Storage
Platform (VSP) Gx00
use 512KB

3 © Hitachi Vantara Corporation 2018. All rights reserved.

 HFSM File System

4 © Hitachi Vantara Corporation 2018. All rights reserved.

 HFSM File System Edition

5 © Hitachi Vantara Corporation 2018. All rights reserved.

 Namespace Hard Quota Modification

6 © Hitachi Vantara Corporation 2018. All rights reserved.

 Migration Task Edition

7 © Hitachi Vantara Corporation 2018. All rights reserved.

 Edit Migrations Tasks

8 © Hitachi Vantara Corporation 2018. All rights reserved.

 Edit Migrations Tasks

From v6.1 you can execute Migrate Immediately,

and Disable Task without editing the task.

9 © Hitachi Vantara Corporation 2018. All rights reserved.

 Edit Migrations Tasks

You can have more than one migration task

over the same file system with different
policies:
• Migrate only this path
• Migrate files with extensions and so on
• Time of modification and so on

0 © Hitachi Vantara Corporation 2018. All rights reserved.

 Define Migration Criteria

Some examples of criteria

1 © Hitachi Vantara Corporation 2018. All rights reserved.

 CIFS Shares and NFS Exports

2 © Hitachi Vantara Corporation 2018. All rights reserved.

 Create Shares

It is CIFS share and

NFS export

Optional: Assign a
quota to the directory
(visible as size of file
system)

If the directory does not

exist, do not forget to
mark Create directory

3 © Hitachi Vantara Corporation 2018. All rights reserved.

 Create Shares

• If you are sharing another directory other than the root

of the file system, and you have selected to Create
directory, it displays as the Directory tab where you
can configure the advanced ACL of the new directory
• After the folder creation, you cannot change this ACL
using GUI, but you can change it using CLI (Refer to
the CLI Module later in this course)
4 © Hitachi Vantara Corporation 2018. All rights reserved.
 Share Settings – Access Control

5 © Hitachi Vantara Corporation 2018. All rights reserved.

 Share Settings – Access Permissions
Set the default
permissions of every
new file and new
directories created
under this share
(or subdirectories)
Owner Group Everyone

6 © Hitachi Vantara Corporation 2018. All rights reserved.

 Directory Creation – ACL Permissions

7 © Hitachi Vantara Corporation 2018. All rights reserved.

 No Root Squashing for Network File System

Disabling the root squashing protection

mechanism. Some applications (running
as root in UNIX systems) verify root
ownership of the files after creation

8 © Hitachi Vantara Corporation 2018. All rights reserved.

 Share Settings – Advanced Options for CIFS

CIFS share name

(Other than name
of the shared
directory)

9 © Hitachi Vantara Corporation 2018. All rights reserved.

 CIFS Client

The client uses one of the

virtual IPs of the node owner of
the file system where you
created the share

0 © Hitachi Vantara Corporation 2018. All rights reserved.

 CIFS Client

If we change this quota…

The visible size from the Client is the

quota assigned to the Directory The visible size changes

1 © Hitachi Vantara Corporation 2018. All rights reserved.

 HCP Namespace System-Backup Creation

 A configuration backup namespace with name - system-backup is also

automatically created in the specified tenant. It contains a backup for the
configuration of HDI

2 © Hitachi Vantara Corporation 2018. All rights reserved.

 HCP and Active Directory Integration:
Wizard Further Configuration

3 © Hitachi Vantara Corporation 2018. All rights reserved.

 Reconfigure the Processing Node

 If initially it was not possible to finish the HCP integration as part of the configuration
wizard but after creating cluster and setting the front-end address, you can run the
configuration wizard again to continue

 Select the HDI cluster and press the Reconfigure Processing Node button

4 © Hitachi Vantara Corporation 2018. All rights reserved.

 Reconfigure the Processing Node

5 © Hitachi Vantara Corporation 2018. All rights reserved.

 Successful Completion

6 © Hitachi Vantara Corporation 2018. All rights reserved.

 Module Summary

 In this module, you should have learned to:

• Use Hitachi File Services Manager (HFSM) for initial setup
• Configure Hitachi Data Ingestor (HDI) cluster
 Integrate with Hitachi Content Platform (HCP) and tenant using management API
(MAPI)
 Create file system and namespace
 Integrate with active directory
 Create a common internet file system (CIFS) share and configure permissions
• Edit the migration task
• Configure the front-end network

7 © Hitachi Vantara Corporation 2018. All rights reserved.

 Questions and Discussion

8 © Hitachi Vantara Corporation 2018. All rights reserved.

 Module Review

1. It is possible to configure a cluster without HFSM. (True or False)

2. Explain the use of virtual IPs in the HDI cluster.

3. In HDI cluster, the work space for active file migration is taken from the
file system. (True or False)

9 © Hitachi Vantara Corporation 2018. All rights reserved.