Hitachi Ops Center

Administrator
10.8.0

Getting Started Guide

This guide lists the minimum system requirements and provides the necessary procedures to get Ops
Center Administrator up and running.

MK-99ADM000-11
October 2021
© 2019, 2021 Hitachi, Ltd. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including copying and recording,
or stored in a database or retrieval system for commercial purposes without the express written permission of Hitachi, Ltd., or Hitachi Vantara LLC
(collectively “Hitachi”). Licensee may make copies of the Materials provided that any such copy is: (i) created as an essential step in utilization of the
Software as licensed and is used in no other manner; or (ii) used for archival purposes. Licensee may not make any other copies of the Materials.
“Materials” mean text, data, photographs, graphics, audio, video and documents.
Hitachi reserves the right to make changes to this Material at any time without notice and assumes no responsibility for its use. The Materials contain
the most current information available at the time of publication.
Some of the features described in the Materials might not be currently available. Refer to the most recent product announcement for information about
feature and product availability, or contact Hitachi Vantara LLC at [Link]
Notice: Hitachi products and services can be ordered only under the terms and conditions of the applicable Hitachi agreements. The use of Hitachi
products is governed by the terms of your agreements with Hitachi Vantara LLC.
By using this software, you agree that you are responsible for:
1. Acquiring the relevant consents as may be required under local privacy laws or otherwise from authorized employees and other individuals; and
2. Verifying that your data continues to be held, retrieved, deleted, or otherwise processed in accordance with relevant laws.
Notice on Export Controls. The technical data and technology inherent in this Document may be subject to U.S. export control laws, including the
U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Reader agrees to
comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain licenses to export, re-export, or import the
Document and any Compliant Products.
Hitachi and Lumada are trademarks or registered trademarks of Hitachi, Ltd., in the United States and other countries.
AIX, AS/400e, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, eServer, FICON, FlashCopy, GDPS, HyperSwap, IBM, Lotus, MVS, OS/
390, PowerHA, PowerPC, RS/6000, S/390, System z9, System z10, Tivoli, z/OS, z9, z10, z13, z14, z/VM, and z/VSE are registered trademarks or
trademarks of International Business Machines Corporation.
Active Directory, ActiveX, Bing, Excel, Hyper-V, Internet Explorer, the Internet Explorer logo, Microsoft, the Microsoft Corporate Logo, MS-DOS,
Outlook, PowerPoint, SharePoint, Silverlight, SmartScreen, SQL Server, Visual Basic, Visual C++, Visual Studio, Windows, the Windows logo,
Windows Azure, Windows PowerShell, Windows Server, the Windows start button, and Windows Vista are registered trademarks or trademarks of
Microsoft Corporation. Microsoft product screen shots are reprinted with permission from Microsoft Corporation.
All other trademarks, service marks, and company names in this document or website are properties of their respective owners.
Copyright and license information for third-party and open source software used in Hitachi Vantara products can be found at https://
[Link]/en-us/company/[Link].

Hitachi Ops Center Administrator Getting Started Guide 2

Contents

Preface......................................................................................................5
Intended Audience...............................................................................................5
Product version....................................................................................................5
Release notes......................................................................................................5
Document conventions........................................................................................ 5
Conventions for storage capacity values............................................................. 7
Accessing product documentation.......................................................................8
Getting help..........................................................................................................8
Comments............................................................................................................8

Chapter 1: Hitachi Ops Center Administrator environment....................... 9

Minimum system requirements............................................................................ 9
Port requirements.............................................................................................. 10
Supported storage systems............................................................................... 18
Supported microcode/firmware..........................................................................19
Supported file server..........................................................................................19
Supported fabric switches..................................................................................19
Supported servers..............................................................................................20
Supported scalability limits.................................................................................20

Chapter 2: Installing Ops Center Administrator...................................... 21

Installing Ops Center Administrator with the consolidated Ops Center
preconfigured media.......................................................................................... 21
Installing Ops Center Administrator with the application installer...................... 21
Example [Link] file for use with the application installer................. 27
Modifying the Ops Center Administrator port in virtual appliance
manager ...................................................................................................... 28
Installing Ops Center Administrator with stand-alone preconfigured media...... 29
Installing Hitachi Ops Center Administrator in a DHCP environment........... 29
Installing Hitachi Ops Center Administrator in a static environment.............31
Changing the root password immediately after installation............................... 33
Initial setup after installation.............................................................................. 34
Changing the Elasticsearch memory setting................................................ 34
Configuring SSO by integrating with Ops Center Common Services...........35
Registering the Ops Center Administrator server with Ops Center........ 36

Contents
Hitachi Ops Center Administrator Getting Started Guide 3
 Enabling SSO with the Ops Center portal...............................................37
Updating the Ops Center connection......................................................38
Setting up SSL..............................................................................................38
Setting up SSL when Ops Center Administrator is running on the
same server as Common Services......................................................... 38
Generating and installing a signed SSL certificate................................. 39
Installing a custom signed SSL certificate.............................................. 40
Changing the si token authentication time-out in Ops Center
Administrator................................................................................................ 41
Enabling and downloading audit logs...........................................................41
Changing the Docker network address........................................................ 42
Excluding directories from virus scanning.................................................... 42
Creating Ops Center Users, User Groups, and Roles................................. 42
Logging on to Ops Center Administrator........................................................... 43
Logging on when Ops Center Administrator is not available............................. 45

Chapter 3: Managing the Linux environment.......................................... 48

Updating your Linux OS environment using Yellowdog Updater, Modified
(YUM).................................................................................................................48
Updating your container using Yellowdog Updater, Modified (YUM)................. 48

Chapter 4: Upgrading Ops Center Administrator.................................... 51

Upgrading Ops Center Administrator by using the application installer.............51
Upgrading Ops Center Administrator by using backup and restore.................. 53

Chapter 5: Onboarding and configuring a storage system..................... 56

Overview............................................................................................................56
Adding the first storage system......................................................................... 57
Adding a fabric switch........................................................................................58
Adding servers ..................................................................................................60

Chapter 6: Removing Ops Center Administrator.................................... 64

Removing Ops Center Administrator files..........................................................65

Appendix A: Migrating to Ops Center Administrator............................... 66

Migrating host information to Ops Center Administrator.................................... 66
Copying server objects from Hitachi Storage Advisor Embedded to Ops
Center Administrator..........................................................................................67

Contents
Hitachi Ops Center Administrator Getting Started Guide 4
Preface
Hitachi Ops Center Administrator is an infrastructure management solution that unifies
storage management solutions such as storage provisioning, data protection, and storage
management; simplifies the management of large-scale data centers by providing smarter
software services; and is extensible to provide better programmability and control.

Intended Audience
This document is intended for system administrators, Hitachi Vantara representatives, and
authorized service providers who configure and operate Virtual Storage Platform storage
systems with Hitachi Ops Center Administrator.
Readers of this document should be familiar with the following:
■ RAID storage systems and their basic functions.
■ Volume creation and management.
■ Pool creation and management.
■ Parity group creation and management.

Product version
This document revision applies to Hitachi Ops Center Administrator version 10.8.0 or later.

Release notes
Read the release notes before installing and using this product. They may contain
requirements or restrictions that are not fully described in this document or updates or
corrections to this document.
Release notes are located on Support Connect at [Link]
Documents.

Document conventions
This document uses the following typographic conventions:

Preface
Hitachi Ops Center Administrator Getting Started Guide 5
 Document conventions

Convention Description

Bold ■ Indicates text in a window, including window titles, menus, menu

options, buttons, fields, and labels. Example:
Click OK.
■ Indicates emphasized words in list items.

Italic ■ Indicates a document title or emphasized words in text.

■ Indicates a variable, which is a placeholder for actual text provided
by the user or for output by the system. Example:

pairdisplay -g group

(For exceptions to this convention for variables, see the entry for
angle brackets.)

Monospace Indicates text that is displayed on screen or entered by the user.

Example: pairdisplay -g oradb

< > angle Indicates variables in the following scenarios:

brackets ■ Variables are not clearly separated from the surrounding text or
from other variables. Example:

Status-<report-name><file-version>.csv

■ Variables in headings.

[ ] square Indicates optional values. Example: [ a | b ] indicates that you can

brackets choose a, b, or nothing.

{ } braces Indicates required or expected values. Example: { a | b } indicates that

you must choose either a or b.

| vertical bar Indicates that you have a choice between two or more options or
arguments. Examples:
[ a | b ] indicates that you can choose a, b, or nothing.
{ a | b } indicates that you must choose either a or b.

This document uses the following icons to draw attention to information:

Icon Label Description

Note Calls attention to important or additional information.

Preface
Hitachi Ops Center Administrator Getting Started Guide 6
 Conventions for storage capacity values

Icon Label Description

Tip Provides helpful information, guidelines, or suggestions for

performing tasks more effectively.

Caution Warns the user of adverse conditions and/or consequences (for

example, disruptive operations, data loss, or a system crash).

WARNING Warns the user of a hazardous situation which, if not avoided,

could result in death or serious injury.

Conventions for storage capacity values

Physical storage capacity values (for example, disk drive capacity) are calculated based on
the following values:

Physical capacity unit Value

1 kilobyte (KB) 1,000 (103) bytes

1 megabyte (MB) 1,000 KB or 1,0002 bytes

1 gigabyte (GB) 1,000 MB or 1,0003 bytes

1 terabyte (TB) 1,000 GB or 1,0004 bytes

1 petabyte (PB) 1,000 TB or 1,0005 bytes

1 exabyte (EB) 1,000 PB or 1,0006 bytes

Logical capacity values (for example, logical device capacity, cache memory capacity) are
calculated based on the following values:

Logical capacity unit Value

1 block 512 bytes

1 cylinder Mainframe: 870 KiB

Preface
Hitachi Ops Center Administrator Getting Started Guide 7
 Accessing product documentation

Logical capacity unit Value

Open-systems
■ OPEN-V: 960 KiB
■ Others: 720 KiB

1 KiB 1,024 (210) bytes

1 MiB 1,024 KiB or 1,0242 bytes

1 GiB 1,024 MiB or 1,0243 bytes

1 TiB 1,024 GiB or 1,0244 bytes

1 PiB 1,024 TiB or 1,0245 bytes

1 EiB 1,024 PiB or 1,0246 bytes

Accessing product documentation

Product user documentation is available on the Hitachi Vantara Support Website: https://
[Link]/Documents. Check this site for the most current
documentation, including important updates that may have been made after the release of
the product.

Getting help
The Hitachi Vantara Support Website is the destination for technical support of products and
solutions sold by Hitachi Vantara. To contact technical support, log on to the Hitachi Vantara
Support Website for contact information: [Link]
[Link].
Hitachi Vantara Community is a global online community for Hitachi Vantara customers,
partners, independent software vendors, employees, and prospects. It is the destination to
get answers, discover insights, and make connections. Join the conversation today! Go to
[Link], register, and complete your profile.

Comments
Please send us your comments on this document to [Link]@[Link].
Include the document title and number, including the revision level (for example, -07), and
refer to specific sections and paragraphs whenever possible. All comments become the
property of Hitachi Vantara LLC.
Thank you!

Preface
Hitachi Ops Center Administrator Getting Started Guide 8
Chapter 1: Hitachi Ops Center Administrator
environment
The Ops Center Administrator environment must meet minimum requirements to support
management of various storage systems, servers, and fabric switches.

Minimum system requirements

Verify that the Ops Center Administrator server meets or exceeds the minimum requirements
to take advantage of all the Ops Center Administrator features.

Minimum system requirements (Docker and Podman)

Server Minimum requirements

®
Hypervisor operating system VMware ESXi 6.0 or higher, Microsoft
Hyper-V, Linux KVM

Note:
■ Use the product installers
when running Hyper-V or
KVM.
■ Only VMware supports OVA
installations.

Container runtime version for installation Docker

from tar file ■ Version 18 (minimum supported –
v18.09.6)
■ Version 19 (minimum supported –
v19.03.0)
■ Version 20 (minimum supported –
v20.10.5)
Podman
Version 3.0 (minimum supported – v3.0.0)

Chapter 1: Hitachi Ops Center Administrator environment

Hitachi Ops Center Administrator Getting Started Guide 9
 Port requirements

Server Minimum requirements

Operating system for installation from tar file Docker

Linux
Linux (Except for Red Hat Enterprise Linux
8)
Podman
Red Hat Enterprise Linux 8.1, 8.2, and 8.4

Access for installation from tar file Root user

Available disk space 80 GiB

100 GiB for installation using the application

installer. This additional capacity is required
for the installer file and image installation.
After installation is complete, the required
space is reduced to 80 GiB.

Memory 16 GiB RAM

Note: 32 GiB RAM is highly

recommended for an
environment where Ops Center
Administrator manages 20 or
more storage systems. For
details, refer to: Changing the
Elasticsearch memory setting
(on page 34).

CPU 4 vCPUs

A client computer that can run a supported One of the following:

browser ■ Google Chrome (latest version of the
stable channel)
■ Firefox ESR 78.0 or later
■ Internet Explorer 11 or later (requires
enabling the font download option)

Requirements for using program products

To use Hitachi Dynamic Tiering for pools and Hitachi Thin Image for snapshots, make sure
that the licenses are available and shared memory is installed.

Port requirements
The following lists the port requirements for Ops Center Administrator.

Chapter 1: Hitachi Ops Center Administrator environment

Hitachi Ops Center Administrator Getting Started Guide 10
 Port requirements

Ops Center Administrator ports and firewall settings

Ensure that the port numbers specified for use by the Ops Center Administrator server are
different from the port numbers used by other programs installed on the same computer.
Table 1 Ports used by the Ops Center Administrator server

Port number Description

80/tcp Used for accessing the Ops Center Administrator UI from Ops Center
Administrator clients.

443/tcp Used for accessing the Ops Center Administrator UI from Ops Center
Administrator clients.

161/tcp Reserved.

161/udp Reserved.

162/tcp Reserved.

162/udp Used for receiving SNMP traps from supported storage systems and file
servers.
You cannot change the settings by using Ops Center Administrator. If
products using these ports are installed on the same computer, change the
settings of those products.

8085/tcp Used to manage internal services included in the container runtime.

In an environment with firewalls set up in the network that connects the Ops Center
Administrator server, Ops Center Administrator clients, and storage systems, you must
register ports used by Ops Center products as firewall exceptions.
Table 2 Port numbers to register as firewall exceptions between the Administrator
server and the Administrator client

Originator Destination

Port number Machine Port number Machine

any/tcp Ops Center Administrator 80/tcp Ops Center Administrator

client server

any/tcp Ops Center Administrator 443/tcp Ops Center Administrator

client server

Chapter 1: Hitachi Ops Center Administrator environment

Hitachi Ops Center Administrator Getting Started Guide 11
 Port requirements

Table 3 Port numbers to register as firewall exceptions between the Administrator

server and storage systems

Originator Destination

Port number Machine Port number Machine Remarks

any/udp ■ VSP 5000 162/udp Ops Center -

series Administrator
server
■ VSP E series
■ VSP G1x00,
F1500
■ VSP G200,
G/F400, G/
F600, G/
F800
(controller)
■ VSP G/F350,
G/F370, G/
F700, G/
F900
■ VSP G200,
G/F400, G/
F600, G/
F800
(controller)
■ VSP N series
(controller)

any/tcp Ops Center 443/tcp ■ VSP 5000 You can change

Administrator series the port number
server for the following
■ VSP E series
models:
■ VSP G1x00, ■ VSP E series
F1500
■ VSP G200, G/
■ VSP G200, G/
F400, G/F600,
F400, G/F600,
G/F800 (SVP)
G/F800 (SVP)
■ VSP N series
■ VSP N series
(SVP)
(SVP)
■ VSP G200, G/
F400, G/F600,
G/F800
(controller)
■ VSP N series
(controller)

Chapter 1: Hitachi Ops Center Administrator environment

Hitachi Ops Center Administrator Getting Started Guide 12
 Port requirements

Originator Destination

Port number Machine Port number Machine Remarks

any/tcp Ops Center 1099/tcp ■ VSP E series -

Administrator ■ VSP G1x00,
server
F1500
■ VSP G200, G/
F400, G/F600,
G/F800 (SVP)
■ VSP N series
(SVP)

any/tcp Ops Center 11099/tcp VSP 5000 series -

Administrator
server

any/tcp Ops Center 51099/tcp ■ VSP 5000 -

Administrator series
server ■ VSP E series
■ VSP G1x00,
F1500
■ VSP G200, G/
F400, G/F600,
G/F800 (SVP)
■ VSP N series
(SVP)

any/tcp Ops Center 51100-51355/t ■ VSP 5000 Unused port

Administrator cp series numbers are
server allocated
■ VSP E series
automatically
■ VSP G1x00, from the
F1500 described range
during storage
■ VSP G200, G/
system
F400, G/F600,
registration and a
G/F800 (SVP)
firewall is also
■ VSP N series set. The allocated
(SVP) ports numbers
are used when
starting the
storage system.

Chapter 1: Hitachi Ops Center Administrator environment

Hitachi Ops Center Administrator Getting Started Guide 13
 Port requirements

Originator Destination

Port number Machine Port number Machine Remarks

For details on
how to confirm
the port numbers
that the SVP
uses, see the
documentation for
the storage
system.

34001-34008/ Ops Center 31001/udp ■ VSP 5000 -

udp Administrator series
server ■ VSP G1x00,
F1500

34001-34008/ Ops Center 31001-31002/ ■ VSP E series -

udp Administrator udp ■ VSP G200, G/
server
F400, G/F600,
G/F800
(controller)
■ VSP N series
(controller)

any/tcp Ops Center 8443/tcp ■ VSP E series This setting is

Administrator required when
■ VSP G200, G/
server using a NAS
F400, G/F600,
Manager that
G/F800
exists on a
(controller) in
storage system
which a NAS
with a built-in
Module is
NAS module.
included
■ VSP N series
(controller)

Chapter 1: Hitachi Ops Center Administrator environment

Hitachi Ops Center Administrator Getting Started Guide 14
 Port requirements

Table 4 Port numbers to register as firewall exceptions between the Ops Center
Administrator client and storage systems

Originator Destination

Port
number Machine Port number Machine Remarks

any/tcp Ops Center 443/tcp ■ VSP 5000 This setting is required

Administrator series when using SSL for
client Storage Navigator.
■ VSP E series
For
■ VSP G1x00,
F1500 ■ VSP E series
■ VSP G200, G/ ■ VSP G200, G/F400,
F400, G/F600, G/F600, G/F800
G/F800 (SVP) (SVP)
■ VSP N series ■ VSP N series
models (SVP) models (SVP). You
can also change the
port number.

any/tcp Ops Center 5443/tcp ■ VSP 5000 For VSP 5000 series
Administrator series and VSP G1x00,
client F1500, this setting is
■ VSP E series
required when running
■ VSP G1x00, the raidinf command
F1500 on the Ops Center
■ VSP G200, G/ Administrator client.
F400, G/F600,
G/F800 (SVP)
■ VSP N series
models (SVP)

any/tcp Ops Center 1099/tcp ■ VSP E990 -

Administrator ■ VSP G1x00,
client
F1500
■ VSP G200, G/
F400, G/F600,
G/F800 (SVP)
■ VSP N series
models (SVP)

any/tcp Ops Center 11099/tcp VSP 5000 series -

Administrator
client

Chapter 1: Hitachi Ops Center Administrator environment

Hitachi Ops Center Administrator Getting Started Guide 15
 Port requirements

Originator Destination

Port
number Machine Port number Machine Remarks

any/tcp Ops Center 51099/tcp ■ VSP 5000 -

Administrator series
client ■ VSP E990
■ VSP G1x00,
F1500
■ VSP G200, G/
F400, G/F600,
G/F800 (SVP)
■ VSP N series
models (SVP)

any/tcp Ops Center 51100-51355/t ■ VSP 5000 Unused port numbers

Administrator cp series are allocated
client automatically from the
■ VSP E990
described range during
■ VSP G1x00, storage system
F1500 registration and a
firewall is also set. The
■ VSP G200, G/
allocated ports
F400, G/F600,
numbers are used
G/F800 (SVP)
when starting the
■ VSP N series storage system.
(SVP)
For details on how to
confirm the port
numbers used, see the
documentation for your
storage system.

any/tcp Ops Center any/tcp ■ VSP 5000 This setting is required

Administrator series for secure
client communication
■ VSP E990
between the storage
■ VSP G200, G/ system and Ops Center
F400, G/F600, Administrator when
G/F800 (SVP) launching Storage
Navigator.
■ VSP N series
(SVP)

Chapter 1: Hitachi Ops Center Administrator environment

Hitachi Ops Center Administrator Getting Started Guide 16
 Port requirements

Table 5 Port numbers to register as firewall exceptions between the Ops Center
Administrator server and the Ops Center Protector server

Originator Destination

Port Port
number Machine number Machine Remarks

any/tcp Ops Center 443/tcp Ops Center This setting is

Administrator Protector required when adding
server server or deleting High
Availability pairs.

Table 6 Port numbers to register as firewall exceptions between the Ops Center
Administrator server and AD authentication servers

Originator Destination

Port Port
number Machine number Machine Remarks

any/tcp Ops Center 389/tcp AD server Currently, only Microsoft

Administrator Active Directory is supported
server for LDAP authentication.
This port number is generally
used. However, a different
port number might be used for
an authentication server.

any/tcp Ops Center 53/tcp DNS The DNS server is required

Administrator server when using AD
server authentication.

any/udp Ops Center 53/udp DNS The DNS server is required

Administrator server when using AD
server authentication.

Chapter 1: Hitachi Ops Center Administrator environment

Hitachi Ops Center Administrator Getting Started Guide 17
 Supported storage systems

Table 7 Port numbers to register as firewall exceptions between the Ops Center
Administrator server and fabric switches

Originator Destination

Port Port
number Machine number Machine Remarks

any/tcp Ops Center 22/tcp* Fabric This setting is required when

Administrator switch changing zone settings
server according to attaching or
detaching volumes.
This port number is generally
used. However, a different port
number might be used for
fabric switches.

Table 8 Port numbers to register as firewall exceptions between the Ops Center
Administrator server and SNMP managers

Originator Destination

Port Port
number Machine number Machine Remarks

any/udp Ops Center 162/udp SNMP This setting is required

Administrator manager when an SNMP manager
server receives SNMP traps from
Ops Center Administrator.

Supported storage systems

Hitachi Ops Center Administrator supports the Virtual Storage Platform (VSP) family storage
systems.
Initial startup and initial setup of any supported storage system must be completed by a
Hitachi Vantara representative or an authorized service provider.
Hitachi Ops Center Administrator supports the following storage systems:
■ VSP 5000 series
■ VSP E series
■ VSP G1x00, F1500
■ VSP G/F350, G/F370, G/F700, G/F900
■ VSP G200, G/F400, G/F600, G/F800

Chapter 1: Hitachi Ops Center Administrator environment

Hitachi Ops Center Administrator Getting Started Guide 18
 Supported microcode/firmware

■ VSP G400, G600, G800 with optional NAS modules

■ VSP N series

TLS
The supported version of TLS is 1.2.

Supported microcode/firmware
Ops Center Administrator supports the following:
■ VSP 5200, 5600, 5200H, 5600H with microcode version 90-08-0x or later.
■ VSP 5100, 5500, 5100H, 5500H with microcode version 90-01-4x or later.
■ VSP E990 with microcode version 93-01-0x or later.
■ VSP E590, E790, E590H, E790H with microcode version 93-03-21 or later.
■ VSP G/F350, G/F370, G/F700, G/F900 with firmware version 88-01-0x or later.
■ VSP G200, G/F400, G/F600, G/F800 with microcode version 83-04-2x or later.
■ VSP G1x00, F1500 with microcode version 80-05-2x or later.
■ VSP N series with microcode version 83-06-0x or later.

Note: After a storage system firmware/microcode upgrade, any new features are
not supported until you upgrade Ops Center Administrator.

Supported file server

To use any new features included in a storage system firmware/microcode upgrade, you must
also upgrade Ops Center Administrator.
Hitachi Ops Center Administrator supports the following file server configuration:
■ Hitachi NAS platform (HNAS) firmware version: 13.1
■ System management unit (SMU) software: version 13.1

Supported fabric switches

Ops Center Administrator supports the following Brocade® and Cisco® fabric switches.
■ Brocade: Fabric OS 7.x through 8.2.2a
■ Cisco: MDS NX-OS Release 6.2(9) or later

Chapter 1: Hitachi Ops Center Administrator environment

Hitachi Ops Center Administrator Getting Started Guide 19
 Supported servers

Supported servers
You can use Hitachi Ops Center Administrator to provision storage to servers running the
following operating systems:
®
■ VMware
®
■ Windows
™
■ HP-UX
™
■ Oracle Solaris
®
■ NetBSD
®
■ TRU64 UNIX
®
■ Novell NetWare
® ®
■ IBM AIX
®
■ Linux
®
■ IRIX

Supported scalability limits

The following table lists the maximum number of resources supported in Ops Center
Administrator.

Resource Scale

Storage systems 50

Servers 10,000

Volumes 1,500,000 over 50 storage systems

Chapter 1: Hitachi Ops Center Administrator environment

Hitachi Ops Center Administrator Getting Started Guide 20
Chapter 2: Installing Ops Center Administrator
Ops Center Administrator is deployed on a virtual machine and accessed by a client
computer. Review the minimum requirements before installing.
You install Ops Center Administrator by using one of the following options:
■ Installing Ops Center Administrator with the consolidated Ops Center preconfigured media
(on page 21)
■ Installing Ops Center Administrator with the application installer (on page 21)
■ Installing Ops Center Administrator with stand-alone preconfigured media (on page 29)

Installing Ops Center Administrator with the consolidated

Ops Center preconfigured media
If you are installing Ops Center Administrator as part of the Ops Center consolidated OVA,
see the Hitachi Ops Center Installation and Configuration Guide for detailed information on
installation and configuration. When you use the Ops Center consolidated OVA, Ops Center
Administrator is automatically registered in Common Services on the same host. This means
that Single Sign-On (SSO) is also automatically enabled. After you finish installing and
configuring the consolidated OVA, return to this document and complete the Administrator-
specific configuration as described in Initial setup after installation (on page 34).

Installing Ops Center Administrator with the application

installer
You can install Ops Center Administrator in a Linux environment that is running a supported
version of a container runtime.
To enable maximum control of the environment, the application installer does not include a
container runtime, an operating system, or a VM.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 21
 Installing Ops Center Administrator with the application installer

Before you begin

■ Do not install multiple container runtimes such as Docker and Podman to the host OS.
Always use a single container runtime.
■ If you want to register Ops Center Administrator with Ops Center Common Services, do
the following:
● Install Python3 before running the installer.
● Make sure that the host name of Ops Center Common Services is resolvable from the
Ops Center Administrator server. If you want to use a host name that is not FQDN, set
the IP address and the host name in the /etc/hosts file for name resolution.

Note: After modifying the /etc/hosts file, run the following command to
restart the container service. For the Docker service, run:
# systemctl restart docker
For the Podman service, run:
# systemctl restart rainier
● Make sure that you have a user account with Ops Center Common Services that has
the "Application Administrator" role to run the script.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 22
 Installing Ops Center Administrator with the application installer

Verify the following:

■ You have root access to the OS where you plan to install Ops Center Administrator.
■ IP forwarding and br_netfilter for the IP V4 network is installed on the operating
system.
Verify by using the sysctl command (1 means enabled):

# sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 1
# sysctl [Link]-nf-call-iptables
[Link]-nf-call-iptables = 1

■ The OS running firewalld (for example, RHEL 7 or later) is configured to allow

communication between containers as follows:
● Enable communication by adding the following to the trusted zone:
■ For Docker, add docker0.
■ For Podman add cni-podman0 .
The following example is for Docker:

# firewall-cmd --zone=trusted --change-interface=docker0 –permanent

# firewall-cmd --reload

● Enable IP masquerading for the default zone:

# firewall-cmd --add-masquerade –permanent

# firewall-cmd --reload

■ A supported version of container runtime is installed in a Linux environment.

When using Docker:
■ Do not set the following service options to false:
● icc: Enable inter-container communication (default true).
● ip-forward: Enable net.ipv4.ip_forward (default true).
● icc: Enable IP masquerading (default true).
● iptables: Enable addition of iptables rules (default true).
■ The recommended settings for using the application installer are as follows:
● If you use the JSON-file logging driver, set the maximum log size to 50 MiB and the
maximum number of files to 3.

--log-opt max-size=50m --log-opt max-file=3

● Set ExecReload.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 23
 Installing Ops Center Administrator with the application installer

ExecReload=/bin/kill -s HUP $MAINPID

● Set Delegate to yes.

Delegate=yes

● Set KillMode to process.

KillMode=process

● Set Restart.

Restart=on-failure

Refer to the example provided for general information about the [Link] file.
■ The available space on the server is 100 GiB (recommended). This additional capacity is
required for the installer file and container runtime requirements for image installation.
After installation is complete, the required space is reduced to 80 GiB.
■ 16 GiB RAM

Note: Before starting the installation, note the following:

■ 32 GiB RAM is highly recommended for an environment where Ops Center
Administrator manages 20 or more storage systems. For details, refer to:
Changing the Elasticsearch memory setting (on page 34).
■ As a best practice, do not install Ops Center Administrator in a location
running other applications.

Procedure
1. In the Linux environment, configure the network interface that will access Ops Center
Administrator.
Ops Center Administrator supports user interface and API access by using an IPv4
address.
2. Copy the tar file [Link] from the installation
media to any folder in the Linux environment and unzip it.
3. Navigate to the unzipped folder and run [Link].
At the prompts, enter the following:
a. Enter the username for the installer:
Enter sysadmin

b. Enter the user password:

Enter sysadmin

c. Enter host's IP:

Enter the IP address for Ops Center Administrator. This IP address is also used for
SNMP communications with the storage system.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 24
 Installing Ops Center Administrator with the application installer

d. Enter the Service port number (HTTPS, default 443):

Enter the service port for accessing Ops Center Administrator. The default service
port is HTTPS, 443. You can proceed with the default service port or enter your
own.

Note: If you are using Administrator with Ops Center Common

Services or Ops Center Protector, you must enter a port other than the
default (443), which causes a conflict. We suggest 20961.

e. If you want to register Ops Center Administrator with Ops Center Common
Services during installation, enter y at the prompt:

Do you wish to configure Ops Center [y/n]

You are then prompted to enter a user name and password for Ops Center
Common Services and the name and description of the Ops Center Administrator
instance to register.

The installation may take a few minutes. At completion, messages indicate the following:
■ The application was successfully added.
■ The API is ready.
■ Any pre-existing app manager containers have been removed.

4. Set the SNMP IP address in the virtual appliance manager tool:

a. Open a browser and enter [Link] in the address bar.
The login credentials are sysadmin/sysadmin.
b. In the Network tab, enter the SNMP IP address for the storage system.

Troubleshooting the installation

If the installation fails, try the following:
■ If the installation fails with the (401) error code, the user name and password specified by
the installer was incorrect. Retry the installation and ensure that the credentials used are
sysadmin/sysadmin.
■ Check your container network configuration and make sure your container runtime is
working properly. Container runtime requires its network interface (docker0 for Docker, or
cni-podman0 for Podman) to be in a trusted zone in your operating system.
■ Delete all Ops Center Administrator containers, images, and files and then start the
installation again.
■ Check the Docker or Podman logs.
■ Consult the documentation of your container runtime for more information on how to do
this.
■ Journal entries may have additional information about the error. To view the journal log,
connect to the host with the root account and run these commands:
● Docker: journalctl --no-pager -u docker
● Podman: journalctl --no-pager -u rainier

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 25
 Installing Ops Center Administrator with the application installer

If the installation produces any warnings, they may point to the cause of the problem. Correct
any issues the installer identifies, delete any Ops Center Administrator containers and
images, and start the installation again.
To remove files, run the command:

rm -f /opt/rainier/bin/rainier-getlogs

rm -f /opt/rainier/bin/rainier-replace-jdk

To remove container images and containers that you do not manage, run these commands
with the root account (use podman instead of docker depending on your container runtime):
1. docker stop $(docker ps --format "{{.ID}} {{.Image}}" -a | grep
"rdocker:6000/" | awk '{ print $1 }')
2. docker rm -fv $(docker ps --format "{{.ID}} {{.Image}}" -a | grep
"rdocker:6000/" | awk '{ print $1 }')
3. docker rmi $(docker images --format "{{.ID}} {{.Repository}}" |
grep "rdocker:6000/" | awk '{ print $1 }')
4. docker volume rm nginx-certificates
5. docker volume rm nginx-certificates-override
6. docker volume rm nginx-confd
7. docker volume rm nginx-log
If, after powering on or running ip-change, you attempt to execute to the container:

[root@hid ~]# docker exec -it d00be2ea7a01 /bin/bash

and the result is:

OCI runtime exec failed: exec failed: container_linux.go:296: starting

container process caused "process_linux.go:78: starting setns process
caused \"fork/exec /proc/self/exe: no such file or directory\"": unknown

For Docker, run the following to restart the service:

[root@hid ~]# service docker restart

Redirecting to /bin/systemctl restart [Link]

For Podman, run the following to restart the service:

[root@hid ~]# systemctl restart rainier

If the Ops Center Administrator installation succeeded, but registering with Ops Center
Common Services failed, run the setupcommonservice command after the upgraded Ops
Center Administrator goes online.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 26
 Example [Link] file for use with the application installer

Next steps
Required
■ Change the root password as described in Changing the root password immediately after
installation (on page 33).
■ Log on to Ops Center Administrator to verify the installation.
■ Generate and install a signed SSL certificate. By default, the Ops Center Administrator
installation package comes with a self-signed certificate that you can use to initially log in
to Ops Center Administrator.
Optional
■ For information on using the [Link] file, see Example [Link] file for
use with the application installer (on page 27).
■ For more information on changing the Ops Center Administrator port number, see
Modifying the Ops Center Administrator port in virtual appliance manager (on page 28).

Example [Link] file for use with the application installer

If you install Ops Center Administrator with the application installer, refer to the example
[Link] file contents for location and recommended Docker settings for log rotation,
Delegate, and KillMode.
This is an example of the location of recommended Docker settings for log rotation (if you use
the JSON-file logging driver), Delegate and KillMode. They are set in the /usr/lib/
systemd/system/[Link] file. This example is for CentOS and Fedora
operating systems.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 27
 Modifying the Ops Center Administrator port in virtual appliance manager

File path: /usr/lib/systemd/system/[Link]

[Unit]
Description=Docker Application Container Engine
Documentation=[Link]
BindsTo=[Link]
After=[Link] \
[Link] [Link]
Wants=[Link]
Requires=[Link]

[Service]
Type=notify
ExecStart=/usr/bin/dockerd \
--containerd=/run/containerd/[Link] \
––logopt max-size=50m --log-opt max-file=3
ExecReload=/bin/kill -s HUP $MAINPID
TimeoutSec=0
RestartSec=2
Restart=always
StartLimitBurst=3
StartLimitInterval=60s
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity
TasksMax=infinity
Delegate=yes
KillMode=process

[Install]
WantedBy=[Link]

Modifying the Ops Center Administrator port in virtual appliance

manager
You can change the port used by Ops Center Administrator to avoid conflicts.

Before you begin

You can change the Ops Center Administrator port for instances that were installed using the
application installer.

Procedure
1. Log in to virtual appliance manager using the IP address for your Ops Center
Administrator deployment: [Link]
The default credentials for an application installer installation are:
■ User name: sysadmin
■ Password: sysadmin

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 28
 Installing Ops Center Administrator with stand-alone preconfigured media

You must change your password after you log in.

2. In the Network tab, enter the HTTPS port you want to use.
3. Click Submit.

Result
Ops Center Administrator automatically restarts. You can log in using the new URL:
[Link]

Installing Ops Center Administrator with stand-alone

preconfigured media
Use the stand-alone preconfigured media installation to install in either a static environment
or in a DHCP environment.
You can also deploy the Ops Center Administrator OVA file as a VMware vSphere High
Availability cluster or configure vSphere Fault Tolerance.

Installing Hitachi Ops Center Administrator in a DHCP environment

If your environment includes DHCP servers, you can use the Virtual Appliance Manager to
set up your Ops Center Administrator server.

Before you begin

The initial setup of supported storage systems has been completed by an authorized service
provider.

Procedure
1. From the installation media, deploy the Ops Center Administrator OVA to the ESXi host.
2. Change the VM memory size to the recommended value: 16 GiB RAM.

Note: 32 GiB RAM is highly recommended for an environment where Ops

Center Administrator manages 20 or more storage systems. For details,
refer to: Changing the Elasticsearch memory setting (on page 34).

3. Start the Ops Center Administrator virtual machine.

®
4. In the vSphere client, wait for the System status to change to Online.
The status is just below the banner in the virtual machine console.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 29
 Installing Hitachi Ops Center Administrator in a DHCP environment

5. Open a browser and enter [Link] in the address bar.

The default credentials for a preconfigured media installation are:
■ User name: service
■ Password: Chang3Me!

6. Change your password.

a. Click User and select Change password.
b. Enter your new password.

7. From the Virtual Appliance Manager menu, click Network to configure the network
settings.

a. If your data center is using the IP address scheme 192.168.*.*, make sure you
provide another IP range that is not currently used in your environment. This is the
specified range used by Ops Center Administrator.
b. Set the host name for the virtual machine.
c. Set DHCP to On.
d. Click Submit.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 30
 Installing Hitachi Ops Center Administrator in a static environment

8. (Optional) From the Virtual Appliance Manager menu, click Time and add Network Time
Protocol (NTP) servers to the virtual machine.
Adding NTP servers verifies that the Ops Center Administrator servers are synchronized
with the storage system environment.

a. Click + to add a field for an NTP Server.

b. Enter the host name of the NTP server.
c. Click Submit.

Next steps
■ Change the root password as described in Changing the root password immediately after
installation (on page 33).
■ Log in to Ops Center Administrator to verify the installation.
■ Generate and install a signed SSL certificate. By default, the Ops Center Administrator
installation package comes with a self-signed certificate that you can use for the initial log
in to Ops Center Administrator.

Installing Hitachi Ops Center Administrator in a static environment

If you do not have a DHCP server, use the command-line interface to indicate the static IP
address of the Ops Center Administrator server.

Procedure
1. From the installation media, deploy the Ops Center Administrator OVA to the ESXi host.
2. Change the VM memory size to the recommended value: 16 GiB RAM.

Note: 32 GiB RAM is highly recommended for an environment where Ops

Center Administrator manages 20 or more storage systems. For details,
refer to: Changing the Elasticsearch memory setting (on page 34).

3. Start the Ops Center Administrator virtual machine.

®
4. In the vSphere client, wait for the System status to change to Online.
The status is just below the banner in the virtual machine console.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 31
 Installing Hitachi Ops Center Administrator in a static environment

5. Press Alt + F2.

6. Log in with the root account using the default password: 3kO$Pe9dJyjy29HAi2mS.
7. Enter the command ip-change.
The Change IP Address Utility opens.
8. Enter your settings at the prompts.
9. Restart the VM to ensure that it has the IP address.
10. Open a browser and enter [Link] in the address bar. The default
credentials for the preconfigured media installation are:
Username: service
Password: Chang3Me!
11. Change your password.
a. Click User and select Change password.
b. Enter your new password.

12. From the menu, click Network to configure the network settings.

a. If your data center is using the IP address scheme 192.168.*.*, make sure you
provide another IP range that is not currently used in your environment. This is the
specified range used by Ops Center Administrator.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 32
 Changing the root password immediately after installation

b. Set the host name for the virtual machine.

c. Set DHCP to Off.
d. Enter the IP address of the Ops Center Administrator server.
e. Click Submit.

13. (Optional) From the Virtual Appliance Manager menu, click Time and add Network Time
Protocol (NTP) servers to the virtual machine.
Adding NTP servers verifies that the Ops Center Administrator servers are synchronized
with the storage system environment.

a. Click + to add a field for an NTP Server.

b. Enter the host name of the NTP server.
c. Click Submit.

Next steps
■ Change the root password as described in Changing the root password immediately after
installation (on page 33).
■ Log on to Ops Center Administrator and onboard a storage system.
■ Get a digitally signed SSL certificate from a trusted certificate authority (CA) by sending
the CA a certificate signing request (CSR). After you obtain the signed certificate, you can
import it to the server. By default, the Ops Center Administrator installation package
comes with a self-signed certificate that you can use to initially log on to Ops Center
Administrator.

Changing the root password immediately after installation

You must change the root password after you finish the installation.

Procedure
1. Either open an SSH connection to the VM or open the VMware console and press Alt
+F2 to reach the console.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 33
 Initial setup after installation

2. Log in with the root account using the default password:

3kO$Pe9dJyjy29HAi2mS
3. Run the command passwd root.
4. Enter the new password when prompted.

Initial setup after installation

After installing Ops Center Administrator, continue by setting up the following as needed:
■ Elasticsearch memory
■ SSO
■ SSL
■ Si token authentication time-out
■ audit logging
■ Docker network address
■ users, groups, and roles
When you finish the setup, you can log in to the Ops Center Administrator UI.

Changing the Elasticsearch memory setting

If more than 16 GiB RAM is set on the Ops Center Administrator server, change the
Elasticsearch memory setting.

Procedure
1. Open the Ops Center Administrator server console:
■ For VM installations, either open an SSH connection to the VM or open the VMware
console and press Alt+F2 to reach the console.
■ For physical server installations, open the command prompt.

2. Log in by using the root account.

3. If you installed using the preconfigured media, go to the next step. If you installed by
using the application installer, copy the tar file ops-center-administrator-
[Link] from the installation media to any folder, unzip it, and navigate to the
unzipped folder.
4. From the command prompt, run the following command:
elasticsearch-memory-setting
5. At the prompts, enter the following:

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 34
 Configuring SSO by integrating with Ops Center Common Services

a. Enter username for the service account credentials:

Enter the service account user name.

■ For Ops Center preconfigured media or application installer installations, use the
sysadmin credentials.
■ For stand-alone preconfigured media installations, use the service credentials.
a. Enter <users> Password:
Enter the password for the user account.

b. Enter the Elasticsearch heap memory size[GiB]:

Enter half of the physical memory size. In the case of 32 GiB physical memory
size, enter 16.

c. Ensure that the host memory size is twice as large as the

specified value. Do you want to proceed? [y/n]
Enter y.

Ops Center Administrator automatically restarts. Wait until the user interface is
accessible.

6. To confirm that the new value is applied to MEM USAGE of Elasticsearch, run the
following command:
Docker: docker stats
Podman: podman stats

Configuring SSO by integrating with Ops Center Common Services

Registering Ops Center Administrator with Ops Center Common Services enables you to use
Single sign-on (SSO), which controls the access of multiple related, yet independent,
software systems. Using SSO, you can log in with a single ID and password to view and
manage all registered Ops Center products as well as assign user access to them.

Note: If you installed using the consolidated Ops Center OVA, Ops Center
Administrator is already registered with Common Services and you can skip this
section.

You can either set up SSO when installing or upgrading Ops Center Administrator, or you can
do it after.
■ To set up SSO during installation or upgrade, enter the required information during the
procedure. The installation or upgrade script prompts you to input the information, if
necessary.
■ To set up SSO after installation or upgrade, run the setupcommonservice command.
Refer to Registering the Ops Center Administrator server with Ops Center (on page 36)
to learn how to use the command. If the host name, IP address, or port number of the
server where Common Services is installed changes, you must register Ops Center
Administrator again.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 35
 Registering the Ops Center Administrator server with Ops Center

Registering the Ops Center Administrator server with Ops Center

You can register the Ops Center Administrator server with the Hitachi Ops Center portal by
running a script that comes with the software. After running this script, you can access Ops
Center Administrator from the portal using the Ops Center credentials.

Note: If you installed using the Ops Center OVA, Administrator is already
registered in Common Services.

Before you begin

■ If Ops Center Administrator was installed with the application installer (not preconfigured
media), install Python3 to run the script.
■ Verify the following:
● Host name of Ops Center Common Services is resolvable from the Ops Center
Administrator server. If you want to use a host name that is not FQDN, set the IP
address and the host name in the /etc/hosts file for name resolution.

Note: After modifying the /etc/hosts file, run the following command to
restart the
Docker service:
# systemctl restart docker
Podman service:
# systemctl restart rainier
● Ops Center Administrator server and the Common Services server are running.
● Ops Center Common Services server is running v10.0.0-01 or later.
● A user account exists with Common Services that has the "Application Administrator"
role to run the script.
To register Ops Center Administrator with the Hitachi Ops Center portal:

Procedure
1. Either open an SSH connection to the VM or open the VMware console and press
Alt+F2 to reach the console.
2. Log in as root.
3. Run the /opt/rainier/bin/setupcommonservice script with the following
parameters:
csUsername
The Common Services username (optional). If you do not specify the
csUsername option, you can input the Common Services username using
interactive mode.

csUri
The URL of the Common Services server (required).

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 36
 Enabling SSO with the Ops Center portal

applicationHostAddress
The Ops Center Administrator server host name or an IP address (required).

applicationPort
The Ops Center Administrator port number (required).

applicationName
The Ops Center Administrator name to display in the Ops Center portal
(required).

applicationDescription
A description of the Ops Center Administrator server to display in the Ops Center
portal (optional).

tlsVerify
Indicates that Ops Center Administrator must perform SSL certificate verification
when communicating with Ops Center. If set, you must select the csUriCACert
option (optional).

csUriCACert
The CA certificate file to use for certificate verification when communicating with
Ops Center. This option is mandatory if you set the tlsVerify option.

4. After the command runs successfully, Ops Center Administrator is shown in the portal.

Example
The following is an example of running the command:

# /opt/rainier/bin/setupcommonservice --csUsername sysadmin --

applicationPort 443 --csUri [Link] --
applicationHostAddress [Link] --applicationName
MyAdministrator1 --applicationDescription foobar
Registering with following values:
Hostname: [Link]
Application Port: 443
Display Name: MyAdministrator1
Application Description: foobar
Registration Successful

Next steps
You can change the registered Ops Center Administrator server name and description in the
portal. If you want to change other properties such as host name, port number, and so on,
first remove Ops Center Administrator from the portal, and then run the script again with the
required parameters.

Enabling SSO with the Ops Center portal

To enable SSO between Ops Center Administrator and the Ops Center portal, the portal host
name must be resolvable by DNS or in the /etc/hosts file. Otherwise, SSO for Ops Center
Administrator may not work correctly.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 37
 Updating the Ops Center connection

Note: After modifying the /etc/hosts file, run the following command to restart
the service:
Docker:
# systemctl restart docker
Podman:
# systemctl restart rainier

If you want to use an IP address instead of the host name of the Ops Center portal, do the
following on the Ops Center portal server:

Procedure
1. Log in to the server running the Ops Center portal.
2. Run the [Link] command on the server.
For details on the [Link] command, see the Hitachi Ops Center
Installation and Configuration Guide.

Result
You can now sign on to Ops Center Administrator from the Ops Center portal.

Updating the Ops Center connection

If you already registered Ops Center Administrator with Ops Center, but need to update the
Common Services user name, password, address (FQDN or IP), SSL certificate, or other
parameters, you can run the setupcommonservice command as described in Registering
the Ops Center Administrator server with Ops Center (on page 36).

Setting up SSL
You can configure secure communications between each of the Ops Center servers and
clients. SSL certificates verify user identity and enhance security on the server. By default,
the server uses a self-signed certificate. You can get a digitally signed SSL certificate from a
trusted certificate authority (CA) by sending a certificate signing request (CSR). After you
obtain the signed certificate, you import it to the server.

Setting up SSL when Ops Center Administrator is running on the same server as
Common Services
Ops Center Administrator and the Ops Center Common Services must communicate over an
SSL connection. To use the Common Services, you must configure a secure connection in
the same way you configure secure connections with other servers. However, if Common
Services is on the same server as Ops Center Administrator, you can simplify the SSL
configuration by using the cssslsetup command. By using the cssslsetup command,
you can configure SSL communication for all Hitachi Ops Center products installed on the
same management server using a common secret key and server certificate.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 38
 Generating and installing a signed SSL certificate

For more information on the cssslsetup command and how to use it, see "Configuring SSL
communications by using the cssslsetup command" in the Hitachi Ops Center Installation and
Configuration Guide.

Generating and installing a signed SSL certificate

By default, the server uses a self-signed certificate. SSL certificates verify the user's identity
and enhance security on the server. You can get a digitally signed SSL certificate from a
trusted certificate authority (CA) by sending a certificate signing request (CSR). After you
obtain the signed certificate, you import it to the server.
The following is a sample procedure for generating and installing a signed SSL certificate.
The process of obtaining a certificate may be different within each organization.

Procedure
1. Open the virtual machine console and log in using root credentials.
2. Note the hostname of the VM (#hostname).
3. Run the openssl command and provide the Authentication sha1 or sha256, depending
upon the required security. Give the Fully Qualified Domain Name for host name.
# openssl req -nodes -newkey rsa:2048 -sha256 -keyout [Link]
-out [Link]
The system returns the message: Generating a
2048 bit RSA private key
4. Provide the information as prompted. For some fields there is a default value. Enter
period ".", to leave a field blank.
■ Country Name (two-letter code)
■ State or Province Name (two-letter code)
■ Locality name (City)
■ Organization Name (Company)
■ Organizational Unit Name (Section or department)
■ Common Name (Your name or the server host name)
■ Email Address

5. When you receive the CSR file, send it to a certificate authority to obtain an SSL
certificate.
If you need help with this step, consult with customer support or an authorized service
provider.
6. Open a browser and enter the virtual appliance manager URL in the address bar.
For example, [Link]
7. Click Advanced.
8. Click the Certificate Settings tab.
9. Import the certificate into the server.
a. Open the signed certificate (received from the certificate authority) in a text editor.
b. Open the private key file (generated in step 2) in a text editor.
c. Copy the certificate file contents into the Certificate text box.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 39
 Installing a custom signed SSL certificate

Note: Do not include the delimiters.

d. Open the private key.

# cat [Link]

e. Copy the private key file contents into the Private Key text box in the virtual
appliance manager.
f. Click Submit.

Installing a custom signed SSL certificate

Log in using SSH to the Administrator server to install a custom signed SSL certificate.

Before you begin

Because the current installation always searches for disk space under the “root” partition, you
must ensure that you have a partition with free space available. You cannot install
Administrator in a customized location.

Procedure
1. Log in using SSH to the Administrator server.
2. Get the [Link] file from the container:
a. Access the container by running the following command:
Docker: docker exec -it rainier-proxy-container-ip bash
Podman: podman exec -it rainier-proxy-container-ip bash

b. Obtain the [Link] file by running the following commands:

■ cd certificates
■ scp [Link] root@ism_server_ip/tmp
■ exit

3. Navigate to the /tmp folder and run the following command to create the [Link]
file:

# openssl req -new -newkey rsa:2048 -keyout [Link] -out [Link]

-nodes

4. Send the [Link] file to the certification authority to get the [Link] file.
5. Open the Administrator virtual appliance manager UI.
6. From the Advanced menu, click Certificate Settings.
a. Copy the [Link] (from Step 4) content into the Certificate area.
b. Copy the [Link] content into the [Link] area.

7. Click Submit and wait for five minutes.

8. Launch the Administrator UI and verify the SSL certificate from your browser.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 40
 Changing the si token authentication time-out in Ops Center Administrator

Changing the si token authentication time-out in Ops Center

Administrator
You can change the Si token authentication time-out in Ops Center Administrator.

Procedure
1. Log in to the virtual appliance manager at [Link]
■ For Ops Center preconfigured media or application installer installations, use the
sysadmin credentials.
■ For stand-alone preconfigured media installations, use the service credentials.

2. Select Advanced Option > Service Settings.

3. Change [Link] to 6000. The duration setting is in seconds.
4. Click Submit.

Enabling and downloading audit logs

Log in to the Ops Center Administrator virtual appliance manager to download an audit log to
the Ops Center Administrator server.

Before you begin

You must enable Audit Log Collection to collect log files. By default, the audit log is disabled.
The file downloaded from Download Logs is empty if the audit log is not collected.
The actions logged are as follows:
■ All Ops Center Administrator jobs
■ Ops Center Administrator server starts
■ Synchronous operations such as GET
■ Virtual appliance manager operations
■ Authentication (success / failure)
■ Storage system refresh

Procedure
1. Log into the virtual appliance manager at [Link]
■ For Ops Center preconfigured media or application installer installations, use the
sysadmin credentials.
■ For stand-alone preconfigured media installations, use the service credentials.

2. Click Logs and then click Audit Logs.

3. To enable audit log collection, click Enabled. You can change the Retention Period.
4. To download the log, click Download Audit Logs.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 41
 Changing the Docker network address

Changing the Docker network address

By default, the Ops Center Administrator Docker uses the [Link]/25 network. If you
must change the network address, do the following:

Procedure
1. On the Ops Center Administrator server open /etc/sysconfig/docker.
2. Change the OPTIONS expression:

OPTIONS='--selinux-enable --bip=new_network_address'

For example:

OPTIONS='--selinux-enable --bip=[Link]/24'

3. Save the file.

4. Reload the Docker daemon by running the following command:

# systemctl daemon-reload

5. Restart the Docker service by running the following command:

# systemctl restart docker

Excluding directories from virus scanning

Configure your antivirus application to exclude the following directories from scanning:
■ /opt/rainier
■ /var/logs
■ Volume data directory for container runtime:
● Docker: /var/lib/docker/volumes
● Podman: /var/lib/containers/storage

Creating Ops Center Users, User Groups, and Roles

This section describes how to create a user and user group, then assign the role of Ops
Center Administrator to the user group.
You can create users and user groups in Ops Center Common Services and assign roles to
user groups in Ops Center Administrator as follows:

Procedure
1. Log in to Ops Center Common Services using Security Administrator role credentials,
and click log in.
2. Click (+) to create a user.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 42
 Logging on to Ops Center Administrator

3. Enter the user information, then click Submit.

The new user shows in the list under USERS.
4. Click (+) to create a user group.
5. Enter the user group information, then click Submit.
The new user group shows in the list under GROUPS.
6. Click the user groups icon to assign a user group membership to the selected user.
7. Select and add a membership to the user group.
8. Search and select the user group created in Ops Center Common Services.
9. Select the roles to assign and then click Submit.

Logging on to Ops Center Administrator

If you have registered with Ops Center Common Services, you now have the option to log in
and launch all products in the Ops Center Suite. Each product handles its own role
management, but Common Services provides AD integration and Single Sign On (SSO)
support. To use the Ops Center SSO, you must register Ops Center Administrator with
Common Services.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 43
 Logging on to Ops Center Administrator

You can log in to Ops Center Administrator in the following ways:

■ Launch the product from the Ops Center portal– You can log in to Ops Center
Administrator and launch the product dashboard if your user group has already been
granted permission on the product security page. If you do not have the required
permission, you are sent to the product login window. The following image shows the new
login button that is shown after you register Ops Center Administrator with Ops Center.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 44
 Logging on when Ops Center Administrator is not available

Role-Based Access Control (RBAC) either allows or denies users (and associated user
groups) access to Ops Center Administrator based on the existing mapping between
Common Services groups and Administrator-specific user roles.
The Security window shows the mappings from Administrator groups to user roles, which
you can modify. This window is accessible only when you are logged in through SSO (in
which case the legacy Security window is not accessible). If you logged in using the
legacy login window, you cannot access this window. To open the Security page, click the
Settings icon in the top-left corner of the UI.

Note: The administrators listed do not see any group mappings made using
legacy authentication. If the administrator registered AD using legacy
authentication, those groups and users have previous permissions set. The
permission/access varies based on the login method. If AD is also registered
in Ops Center, those groups must be given new permissions.
■ Log in from the login screen of the product – If your user group has been granted
permission in the product security page, you can log in to the dashboard from the product
login screen by clicking login with {auth-server}. If you do not have the required
permission, you may not be able to see the dashboard and are sent to the product login
screen.
■ Log in using the legacy mechanism – You can log in to the existing system in the same
manner you did in previous releases.
Log in and verify that the installation is successful by accessing the Ops Center Administrator
interface from a browser.

Procedure
1. Open a web browser.
2. Enter the URL for Ops Center Administrator in the address bar:
[Link]
where:
■ ip-address is the IP address of the Ops Center Administrator server.
■ port-number is the port number of the Ops Center Administrator server. The default
port number is 443.

3. Log in to the virtual appliance manager at [Link]

■ For Ops Center preconfigured media or application installer installations, use the
sysadmin credentials.
■ For stand-alone preconfigured media installations, use the service credentials.

Logging on when Ops Center Administrator is not available

If Ops Center Administrator is not available and you have an administrator login account with
the required permissions, you can log in directly to Device Manager - Storage Navigator.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 45
 Logging on when Ops Center Administrator is not available

Before you begin

Verify the following:
■ You are managing one of the following storage systems:
● VSP 5000 series
● VSP E990
● VSP G1x00, F1500
● VSP G200, G/F400, G/F600, G/F800
● VSP G350, G370, G700, G900, VSP F350, F370, F700, F900
■ You have an Administrator login account with the required permissions. For information on
creating user accounts in Storage Navigator, see the documentation for your storage
system.

Procedure
1. Start a web browser.
2. Enter the URL:
■ For VSP E990 storage systems, enter [Link]
storage/9360004XXXXX/[Link] (where the model number is '936000'
and '4XXXXX' indicates the system serial number)
■ For VSP 5000 series or VSP G1x00, F1500 storage systems, enter: [Link]
address-or-host-name-of-the-SVP/sanproject/[Link]
■ For VSP G200 storage systems, enter: [Link]
of-the-SVP/dev/storage/8320004XXXXX/[Link] (where the model
number is '8320004' and '4XXXXX' indicates the system serial number)
■ For VSP G/F400, G/F600 or VSP N400, N600 storage systems, enter:
[Link]
8340004XXXXX/[Link] (where the model number is '8340004' and
'4XXXXX' indicates the system serial number)
■ For VSP G/F800, VSP N800 storage systems, enter: [Link]
host-name-of-the-SVP/dev/storage/8360004XXXXX/[Link]
(where the model number is '8360004' and '4XXXXX' indicates the system serial
number)
■ For VSP G/F350 storage systems, enter [Link]
of-the-SVP/dev/storage/8820004XXXXX/[Link] (where the model
number is '882000' and '4XXXXX' indicates the system serial number).
■ For VSP G/F370, G/F700, G/F900 storage systems, enter [Link]
or-host-name-of-the-SVP/dev/storage/8860004XXXXX/[Link]
(where the model number is '886000' and '4XXXXX' indicates the system serial
number).

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 46
 Logging on when Ops Center Administrator is not available

3. The following actions might be required to open the login dialog box, depending on your
environment:
■ If a message indicates that the enhanced security configuration is enabled on the
computer, select In the future, do not show this message and click OK.
■ If the SVP is set to support SSL-encrypted communication and security messages
appear, make sure the certificate is correct and follow the instructions in the dialog
box.
■ If a message indicates that certain web sites are blocked, make sure you have added
the SVP to the trusted sites zone.

4. Enter the user ID and password for the account.

5. Click Log In.
6. If the Security Information dialog box appears, click Yes.
7. If an Adobe Flash Player local storage area pop-up dialog box appears, click Allow to
open the Device Manager - Storage Navigator main window. The cache function of
Flash Player optimizes the process of Device Manager - Storage Navigator. Denying the
request might reduce processing speed.

Result
You are successfully logged in to Device Manager - Storage Navigator.

Note: If the login process fails three times by using the same user ID, Device
Manager - Storage Navigator stops responding for one minute. This is for security
purposes and is not a system failure. Wait, and then try again.

Chapter 2: Installing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 47
Chapter 3: Managing the Linux environment
You can update your Linux OS and container using the Yellowdog Updater, Modified (YUM).

Updating your Linux OS environment using Yellowdog

Updater, Modified (YUM)
Install and manage new software for your Linux OS environment using Yellowdog Updater,
Modified (YUM). YUM is a tool that automatically updates the Linux OS over a network.
Complete the following steps to use YUM to update your OS environment:

Procedure
1. Edit the YUM configuration file:
If you need a proxy server only, without a user, add the following line to the [main]
section of the /etc/[Link] file:

PROXY=[Link]

If the proxy requires a user name and password, add the following lines to the
[Link].

proxy_username=yum-user
proxy_password=yum-user-password

2. Complete the software updates.

yum update openssl
3. Validate the software version.
openssl version

Result
Your OS environment is updated.

Updating your container using Yellowdog Updater, Modified

(YUM)
Update your container using Yellowdog Updater, Modified (YUM).
Complete the following steps to use YUM to update your container:

Chapter 3: Managing the Linux environment

Hitachi Ops Center Administrator Getting Started Guide 48
 Updating your container using Yellowdog Updater, Modified (YUM)

Procedure
1. Edit the YUM configuration file:
If you need a proxy server only, without a user, add the following line to the [main]
section of the /etc/[Link].

PROXY=[Link]

If the proxy requires a user name and password, add the following lines to the
[Link] file.

proxy_username=yum-user
proxy_password=yum-user-password

2. Search for the container that requires updating:

docker ps -a | grep -i 'container_name'

docker exec -it container_id bash -IM0

3. Save the repository.

cd /etc/[Link].d

mv [Link] [Link]

touch [Link]

4. Copy the following contents to [Link]:

[Link]
#
The mirror system uses the connecting IP address of the client and the
update status of each mirror to pick mirrors that are updated to and
geographically close to the client. You should use this for CentOS
updates
unless you are manually picking other mirrors.
#
If the mirrorlist= does not work for you, as a fall back you can try
the
remarked out baseurl= line instead.
#
#

[base]
name=CentOS-7.2.1511 - Base
baseurl=[Link]
gpgcheck=1

Chapter 3: Managing the Linux environment

Hitachi Ops Center Administrator Getting Started Guide 49
 Updating your container using Yellowdog Updater, Modified (YUM)

gpgkey=[Link]

#released updates
[updates]
name=CentOS-7.2.1511 - Updates
baseurl=[Link]
gpgcheck=1
gpgkey=[Link]

5. Perform software updates.

yum install bind-utils

6. Validate the domain.

nslookup

[root@hid [Link].d]# nslookup [Link]

Server: [Link]
Address: [Link]#53

Non-authoritative answer:
Name: [Link]
Address: [Link]
Name: [Link]
Address: [Link]

Result
Your container is updated.

Chapter 3: Managing the Linux environment

Hitachi Ops Center Administrator Getting Started Guide 50
Chapter 4: Upgrading Ops Center Administrator
You can upgrade Ops Center Administrator by using the application installer or by restoring a
backup of the previous version. The upgrade method depends on which version of the
software you are currently running.
■ If you are upgrading from v3.4, 3.4.1, or 10.x or later, you can use the application installer
script as described in Upgrading Ops Center Administrator by using the application
installer (on page 51).
■ If you are upgrading from a version earlier than 3.4, or moving your Ops Center
Administrator instance, you must upgrade by creating a backup of your existing Ops
Center Administrator instance as described in Upgrading Ops Center Administrator by
using backup and restore (on page 53).
■ If you are migrating to a different container runtime (for example; migrating from Docker to
Podman), you must upgrade by creating a backup of your existing Ops Center
Administrator instance before uninstalling the older container runtime and installing a new
one. Refer to Upgrading Ops Center Administrator by using backup and restore (on
page 53) for more information.

Upgrading Ops Center Administrator by using the application

installer
When upgrading, you can upgrade from 10.0.x or later to 10.8.0. If you use 3.4.x, refer to the
document of the previous version for upgrade path.

Before you begin

Verify the following:
■ There is 10 GiB of available space and a temporary total of 40 GiB of available space.
■ The backup and restore operation is not running.
■ The Virtual Appliance Manager log level is set to INFO. Upgrading fails when the log level
is set to DEBUG or TRACE.

Chapter 4: Upgrading Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 51
 Upgrading Ops Center Administrator by using the application installer

Note: If you also want to upgrade the Docker version, upgrade Administrator first
and then upgrade Docker.
During installation, the following files are created under /tmp. Delete them if they
are no longer required:
■ Application log
■ Audit log
■ Backup file
The installation log is created under /var/logs/rainier-install.

Procedure
1. Either open an SSH connection to the VM or open the VMware console and press Alt
+F2 to reach the console.
2. Log in as root account.
3. Copy the tar file [Link] from the installation
media to any folder in the Linux environment and extract it. Navigate to the extracted
folder.
4. In the directory where the virtual appliance manager resides, run the command
sudo ./[Link]
5. Log in when prompted.
■ For Ops Center preconfigured media or application installer installations, use the
sysadmin credentials.
■ For stand-alone preconfigured media installations, use the service credentials.

6. At the prompt enter y at the following:

Do you want to upgrade? [y/n]:

Do you want to configure Ops Center [y/n]:

Ops Center Administrator begins upgrading.

Chapter 4: Upgrading Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 52
 Upgrading Ops Center Administrator by using backup and restore

Troubleshooting the upgrade

If the installation fails, try the following:
■ Check the error message and retry the installation.
■ Ensure to set the Virtual Appliance Manager log level to INFO. Upgrading fails when the
log level is set to DEBUG or TRACE.
■ Restart the Docker service, check that the older version is running and then retry the
installation.
■ Check the Docker logs.
Consult Docker documentation for more information on how to perform these actions.
■ Journal entries may have additional information about the error. To view the journal log,
connect to the host with the root account and run these commands:
● journalctl --no-pager
● journalctl --no-pager -u docker
■ If the installation produces any warnings or errors, they may point to the cause of the
problem. Correct any issues the installer identifies, delete any Ops Center Administrator
containers and images, and start the installation again.
■ If the problem persists even though issues are corrected, try a fresh installation.
1. Check that the backup file of the current version exists under the folder where
[Link] is located and download the backup file.
If the backup file does not exist, access the virtual appliance manager and download
the backup file.
■ For an environment where the application installer version was originally installed,
remove the older version and start a fresh installation.
■ For an environment where the preconfigured media installer version was originally
installed, discard the current environment and perform a preconfigured media
installation.

2. After the installation completes, apply the backup file.

Upgrading Ops Center Administrator by using backup and

restore
If you are moving your Ops Center Administrator instance, you must upgrade by backing up
your existing Ops Center Administrator instance, installing a newer version, and then
restoring the previous instance. When upgrading, you can upgrade from 10.0.x or later to
10.8.0.
If you are upgrading from a version earlier than 3.4, for details, refer to the document of the
previous version. When you reach 3.4, you can start using the application installer to
complete your upgrade, which is a simpler process. For details, see Upgrading Ops Center
Administrator by using the application installer (on page 51).

Chapter 4: Upgrading Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 53
 Upgrading Ops Center Administrator by using backup and restore

Procedure
1. Choose one of the following installation methods:
■ Use the preconfigured media ISO to deploy an OVA. The OVA installation deploys a
VM with an operating system, Docker, and Ops Center Administrator.
■ Use the application installer to enable maximum control of the environment. The
installer must be deployed in a Docker-compatible or a Podman-compatible
environment that contains only the Ops Center Administrator application.

Note: If you use the json-file logging driver, set the maximum log size to
50 MiB and the maximum number of files to 5.

2. From the currently installed version, access the virtual appliance manager at:
[Link]
■ For application installer installations, use the sysadmin credentials.
■ For stand-alone preconfigured media installations, use the service credentials.

3. When the virtual appliance manager opens in the browser, click Backup to download a
backup file of the currently installed version. The file may take a few seconds to start
downloading.

Note: Ensure the virtual appliance manager log level is set to INFO before
you upgrade. If it is set it to DEBUG or TRACE, the upgrade may fail with
errors.

4. After downloading the backup file, shut down the currently installed version.
■ If you used the Ops Center Administrator installer method, delete the Ops Center
Administrator containers and images on the system before running the new installer.
Refer to Removing Ops Center Administrator (on page 64) for more information.
■ If you used the Appliance model, the VM containing Storage Advisor or Ops Center
Administrator is shut down at this time. You may want to determine a maintenance
window to do this because the Ops Center Administrator product is unavailable until
the upgrade is complete.
■ If the current version was deployed by using the application installer and if you want
to migrate to a different container runtime (for example, migrating Docker to
Podman), uninstall the old container runtime and then install the new container
runtime on the host OS.

5. Deploy the next version in the upgrade path, using the method of your choice (virtual
appliance or installer).
Follow the instructions in the Getting Started content until the product is initialized and
ready to use.
6. In the new instance of Ops Center Administrator, log in to the virtual appliance manager
by using the default credentials.
■ For application installer installations, use the sysadmin credentials.
■ For stand-alone preconfigured media installations, use the service credentials.

Chapter 4: Upgrading Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 54
 Upgrading Ops Center Administrator by using backup and restore

7. When the virtual appliance manager opens in the browser, click Restore. You are
prompted to upload the backup file that was downloaded earlier. Choose the file and
upload it to the new Ops Center Administrator instance.
The Ops Center Administrator appliance restarts. It may take up to an hour to restore
the configuration. After the appliance is running, the upgrade is complete. (Optional) If
the upgrade completed successfully, you can delete the VM containing the previous
version of Ops Center Administrator.

Note: Do not cancel the restore operation. Cancellation may corrupt the Ops
Center Administrator instance. The progress bar may indicate 100%
completion even though the operation has not completed.

8. Repeat this entire procedure for each version listed in the upgrade path until you reach
the latest version.

Chapter 4: Upgrading Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 55
Chapter 5: Onboarding and configuring a
storage system
Onboarding a storage system is the process of associating it with Ops Center Administrator.
After the storage system is onboarded, you can manage it from the Ops Center Administrator
dashboard.
If the storage system includes NAS modules, the file storage is automatically added with the
block storage
Ops Center Administrator requires access to all resources groups on the storage system so
that the workflows function correctly. Verify that the service processor user name used to
onboard a storage system in Ops Center Administrator has access to all custom resource
groups and meta resource groups

Overview
Onboarding a storage system in Ops Center Administrator is more than adding a storage
system to a list. You must add at least one server before you can provision volumes to the
server on the storage system.
In the following workflow, the recommended path is marked by the solid arrows. The dashed
arrows indicate the optional paths. Before a storage system is available for use in the
network, you must complete all of the tasks in the workflow.

Chapter 5: Onboarding and configuring a storage system

Hitachi Ops Center Administrator Getting Started Guide 56
 Adding the first storage system

Adding the first storage system

You must onboard a storage system the first time you start Ops Center Administrator.

Before you begin

Ops Center Administrator needs access to all resources groups on the storage system so
that the workflows function correctly. Verify that the service processor (SVP) user name used
to onboard a storage system in Ops Center Administrator has access to all custom resource
groups and meta resource groups.
If a storage array includes block storage and NAS modules, the file storage is automatically
added with the block storage. You can then create pools and other file resources using the
Ops Center Administrator interface or by using the API.
Ops Center Administrator also supports onboarding of 4-node clusters, which is a
requirement for GAD Enhanced for NAS.
You can add multiple VSP E series and VSP G200, G/F400, G/F600, G/F800 models at the
same time by specifying an SVP IP address that has multiple storage systems. Storage
systems with different credentials cannot be added at the same time.

Note: To receive storage systems alerts in Ops Center Administrator, the storage
system must be set to SNMPv3. If storage systems have SNMPv1 or SNMPv2c
settings configured, you can still manage onboarded storage systems, but alert
information for these storage systems is not shown in Ops Center Administrator.
For Ops Center Administrator to receive alerts from onboarded storage systems,
you must change the SNMP setting to SNMPv3 and add the Ops Center
Administrator server as an SNMP trap destination.

Chapter 5: Onboarding and configuring a storage system

Hitachi Ops Center Administrator Getting Started Guide 57
 Adding a fabric switch

Procedure
1. On the Ops Center Administrator dashboard, click the plus sign (+) to add a storage
system.
2. Enter values for the following parameters in the Onboard Storage System window.
IP Address:
For a storage system with an SVP, enter the IP address (IPv4) of the external
service processor for the storage system you want to discover.

User name and password:

Log in as a user who has administrator privileges on this storage system. For
example, you can log in with the username maintenance.

Note: If the storage system has a virtual SVP, you can specify the
SVP access port number following the IP address in the IP address
field. The syntax is IP-address:Port-number.

3. Click Submit.
4. (Optional) Onboard other storage systems.

Result
The Jobs tab is updated with a job called Create Storage System. If you are adding
multiple storage systems, there a job for each one.
Wait a while for Administrator to add the storage system. Refresh the Jobs tab to verify that
the storage system has been onboarded.

Next steps
■ Verify the storage system initial settings.
■ Create parity groups.

Note: Parity groups for the following storage systems are created outside of
Ops Center Administrator by a service representative:
■ VSP 5000 series
■ VSP G1x00, F1500

Adding a fabric switch

You can add, update, or delete a fabric switch after onboarding a storage system in the Ops
Center Administrator interface.
After you add a fabric switch, you can choose to auto-create zones during volume
provisioning. A fabric switch is required for any process that uses auto-select, such as host
group creation and auto-selection of ports while attaching volumes to servers.

Chapter 5: Onboarding and configuring a storage system

Hitachi Ops Center Administrator Getting Started Guide 58
 Adding a fabric switch

Before you begin

Verify the following:
■ Servers and ports are connected according to the manufacturer's instructions.
■ There is an active zone set with at least one dummy zone available.
■ The Ops Center Administrator server is connected to the same IP network and has access
to the SNMP broadcast of Fibre Channel switches.
■ You have 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
● Password
■ You have the Admin role for the fabric switch.

Procedure
1. On the Ops Center Administrator dashboard, select Fabric Switches to open the
Fabric Switches window.
2. Click the plus sign (+) to open the Add Fabric Switches window.

3. Enter the following information from the configuration of the switch you are adding:
■ Virtual Fabric ID: For Cisco switches, the VSAN ID. Not applicable to Brocade
switches.
■ Fabric Switch Type: Select Brocade or Cisco.

Chapter 5: Onboarding and configuring a storage system

Hitachi Ops Center Administrator Getting Started Guide 59
 Adding servers

■ Fabric Switch IP Address

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

4. Click Submit.

Result
A job is created to add the fabric switch.

Adding servers
Add servers so you can attach volumes. You can add multiple server parameters from a file,
or add one server at a time.

Chapter 5: Onboarding and configuring a storage system

Hitachi Ops Center Administrator Getting Started Guide 60
 Adding servers

You can add servers using one of the following methods:

■ Manually add information for one server at a time.
■ Import a CSV (comma-separated values) file with information for one server in each row.
The CSV file must have the following headings:
● For Fibre: Name, OSType, WWNs (comma-separated list of WWNs).
Description and IPAddress are optional headings.
● For iSCSI: Name, OSType, IscsiName (comma-separated list of names).
Description, IPAddress, ChapUser, and ChapSecret are optional headings.
Valid OSType values are as follows:
● AIX
● HP_UX
● LINUX
● NETWARE
● OVMS
● SOLARIS
● TRU64
● VMWARE
● VMWARE_EX
● WIN
● WIN_EX

Note: When you use Internet Explorer, limit the number of servers in a CSV
file to 500 servers. If the browser does not work, reduce the number of servers
and try again.

Procedure
1. On the Ops Center Administrator dashboard, click Servers. Then click the plus sign (+)
to open the Add Server window.

Chapter 5: Onboarding and configuring a storage system

Hitachi Ops Center Administrator Getting Started Guide 61
 Adding servers

2. In the Add Server window, do one of the following:

■ Click the upper plus sign (+) to browse for the CSV file or drag the file to the plus
sign. The values from the file populate the window. Example:
Name,Description,IPAddress,OSType,WWNS
Esxi,ESXI HOST,[Link],VMWARE_EX,10:00:00:05:33:26:f7:21
Win,WINDOWS
HOST,[Link],WIN_EX,"10:00:00:05:33:26:f7:37,10:00:00:05:3
3:26:f7:36"
ESXi_Cisco_1,ESXi HOST connected to Cisco
Fabric,,VMWARE_EX,"10:00:00:05:33:26:e0:fc,10:00:00:05:33:26:e
0:fd"
ESXi_Cisco_2,ESXi HOST connected to Cisco
Fabric,,VMWARE_EX,"100000053326df1a,100000053326df1b"
■ To add both Fibre and iSCSI servers, use the following format:
Name,Description,IPAddress,OSType,WWNS,IscsiNames,CHAPUserName
,CHAPUserSecret
linux-iscsi,test dummy host,[Link],Linux,,"iqn. linux-
iscsi-1,iqn. linux-iscsi-2,eui.1234567890abCDef",,,,
-windows-iscsi-uni-chap,test dummy
host,[Link],Win,,"iqn.-windows-iscsi-uni-
chap",chapUserName,chapUserSecret,,
-windows-iscsi-bi-chap,test dummy host,[Link],Win,,"iqn.-
windows-iscsi-bi-
chap",chapUserName,chapUserSecret,chapUserName,chapUserSecret
-vmware-iscsi-longest,test dummy
host,[Link],VMWARE,,"iqn.12345678901234567890123456789012
34567890123456789012345678901234567890123456789012345678901234
56789012345678901234567890123456789012345678901234567890123456
78901234567890123456789012345678901234567890123456789012345678
9,eui.3234567890abCDef",,,,
ed801h,Windows,[Link],WIN,"10:00:00:90:fa:b4:a8:71"
ed800n,ESX Host,[Link],VMWARE,"10:00:00:90:fa:55:85:5d"
-linux,test dummy
host,[Link],Linux,10:10:10:10:10:10:10:10
-windows,test dummy
host,[Link],Win,10:10:10:10:10:10:10:20
-vmware,test dummy
host,[Link],VMWARE,10:10:10:10:10:10:10:30

Chapter 5: Onboarding and configuring a storage system

Hitachi Ops Center Administrator Getting Started Guide 62
 Adding servers

■ Click the plus sign (+) in the table to add a row and enter the required information for
Fibre Channel or iSCSI. You can add more servers by clicking the plus sign again.
■ (Optionally) You can use the WWN List to add/edit a server.

3. Click Submit to add the servers.

Next steps
Create volumes and attach them to the server.

Chapter 5: Onboarding and configuring a storage system

Hitachi Ops Center Administrator Getting Started Guide 63
Chapter 6: Removing Ops Center Administrator
To remove an Ops Center Administrator deployment that was installed with the application
installer, you must delete any Ops Center Administrator containers, images, and files.
To remove container images and containers that you do not manage, run the following
commands as the root account, in the order shown:

Procedure (Docker)
1. docker stop $(docker ps --format "{{.ID}} {{.Image}}" -a | grep
"rdocker:6000/" | awk '{ print $1 }')
2. docker rm -fv $(docker ps --format "{{.ID}} {{.Image}}" -a | grep
"rdocker:6000/" | awk '{ print $1 }')
3. docker rmi $(docker images --format "{{.ID}} {{.Repository}}" |
grep "rdocker:6000/" | awk '{ print $1 }')
4. docker volume rm nginx-certificates
5. docker volume rm nginx-certificates-override
6. docker volume rm nginx-confd
7. docker volume rm nginx-log

Procedure (Podman)
1. Log in to the OS with the root user account.
2. systemctl stop rainier
3. systemctl disable rainier
4. podman rm -fv $(podman ps --format "{{.ID}} {{.Image}}" -a | grep
"rdocker:6000/" | awk '{ print $1 }') 2>/dev/null
5. podman rmi $(podman images --format "{{.ID}} {{.Repository}}" |
grep "rdocker:6000/" | awk '{ print $1 }')
6. podman volume rm nginx-certificates
7. podman volume rm nginx-certificates-override
8. podman volume rm nginx-confd
9. podman volume rm nginx-log
If you installed Ops Center Administrator with Podman, run the following commands:
1. sudo rm -rf /var/log/rainier-audit-log
2. sudo rm -rf /var/logs/rainier-elastic-store
3. sudo rm -rf /var/run/[Link]
4. sudo rm -f /etc/systemd/system/[Link]

Chapter 6: Removing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 64
 Removing Ops Center Administrator files

Removing Ops Center Administrator files

As part of the removal process, remove files associated with Ops Center Administrator.
To remove existing files, run the following commands:
1. sudo rm -rf /opt/rainier
2. sudo rm -rf /var/log/rainier-audit-log
3. sudo rm -rf /var/logs/rainier-tool
4. sudo rm -rf /var/logs/rainier-elastic-store

Note: Ops Center Administrator uses rdocker:6000 as an image repository

If you have installed Ops Center Administrator with Podman, run the following commands as
well:
1. sudo rm -rf /var/log/rainier-audit-log
2. sudo rm -rf /var/logs/rainier-elastic-store
3. sudo rm -rf /var/run/[Link]
4. sudo rm -f /etc/systemd/system/[Link]

Chapter 6: Removing Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 65
Appendix A: Migrating to Ops Center
Administrator
When migrating your environment to Ops Center Administrator from another product such as
Hitachi Storage Advisor Embedded, Hitachi Device Manager, or Storage Navigator, one of
the key requirements is migrating host information. The following section describes how to
use the Ops Center Administrator Scan Host Groups function to migrate host information
when migrating from another product.

Migrating host information to Ops Center Administrator

When migrating, you must migrate host information, which can be done using the Scan Host
Groups feature.
This feature enables you to automatically add servers into Ops Center Administrator from
existing host groups in onboarded storage systems. (Ops Center Administrator creates or
updates server objects based on host groups.) The Scan Host Group job uses host group
information retrieved by using SVP and CCI.
Scan Host Groups does not change any storage configuration or related information (for
example, path information). Existing information is maintained and only differential
information is updated for server objects in Ops Center Administrator.
At a high level, the migration steps are as follows:
1. Install and configure Ops Center Administrator on a new server.
2. Onboard storage systems to Ops Center Administrator and temporarily manage storage
systems using both products (existing product and Ops Center Administrator).
3. Migrate host information using Host Scan Groups. For details on how to use Scan Host
Group as well as specifics about behavior when migrating information from different
environments, see "Scanning host groups" in the Hitachi Ops Center Administrator User
Guide.
4. As soon as you can manage the storage systems by using only Ops Center
Administrator, disconnect the storage systems from the previous products.

Note: For more information about removing storage systems, see the
documentation for the previous product.

Appendix A: Migrating to Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 66
 Copying server objects from Hitachi Storage Advisor Embedded to Ops Center Administrator

Copying server objects from Hitachi Storage Advisor

Embedded to Ops Center Administrator
When transitioning to Ops Center Administrator, Administrator automatically copies server
information from Hitachi Storage Advisor Embedded when you onboard the storage system in
Ops Center Administrator. Server object copy does not change any existing storage
configuration or related information (for example, path information) and only differential
information is updated for server objects in Ops Center Administrator.
Note that after you onboard the storage system and server object copy is complete, you must
manage your servers by using Ops Center Administrator. You can no longer manage servers
with Hitachi Storage Advisor Embedded because the provisioning function is disabled for
data integrity reasons.
Server object copy results depend on the configuration of server WWNs and iSCSI names
between Ops Center Administrator and Hitachi Storage Advisor Embedded for all storage
systems that you onboard. This means that before you onboard any storage system, you
must first ensure that the server configuration in Hitachi Storage Advisor Embedded including
the server name, WWNs and iSCSI name is consistent for all storage systems you plan to
onboard.
Because Ops Center Administrator's server information takes priority over the information in
Hitachi Storage Advisor Embedded, when server inconsistency is found, you may see
different server configuration information in Ops Center Administrator than you do in Hitachi
Storage Advisor Embedded.
Provisioning is reenabled for a storage system in Hitachi Storage Advisor Embedded after
you remove it from Ops Center Administrator. For detailed instructions on how to onboard a
storage system, see "Chapter 2: Adding a storage system" in the Hitachi Ops Center
Administrator User Guide. If server object copy fails when onboarding, try manually
refreshing the storage system.
For detailed instructions on how to switch to managing servers with Hitachi Storage Advisor
Embedded, access the documentation site: [Link]/Documents and
then select Storage > storage_system_type > System Management Using Embedded
Interfaces > Switching to server management that uses Storage Advisor Embedded from
another management tool.

Appendix A: Migrating to Ops Center Administrator

Hitachi Ops Center Administrator Getting Started Guide 67
Hitachi Vantara
Corporate Headquarters Contact Information
2535 Augustine Drive USA: 1-800-446-0744
Santa Clara, CA 95054 USA Global: 1-858-547-4526
[Link] | [Link] [Link]/contact