System Management Console

The System Management Console is a system-specific web application that lets you monitor and manage HCP and its individual nodes. The Console shows you the status of the system in real time, so you can take action when necessary to ensure system health (for example, restarting a node that has failed). Through the Console, you can also modify various system settings, create tenants, and monitor repository usage across all namespaces. Changes you make through the Console take effect immediately.

Access to the System Management Console is available only through HTTP with SSL security (HTTPS).

Note: For you to access the HCP System Management Console in Internet Explorer® on a Windows server, Internet Explorer Enhanced Security Configuration must be disabled for administrators on that server.

Console access

To use the System Management Console, you need either:

A system-level user account defined in HCP.

If the HCP system is configured to support Windows Active Directory (AD), an AD user account for a user that belongs to one or more AD groups for which corresponding system-level group accounts are defined in HCP. In this book, such an AD user account is referred to as a recognized AD user account.

Your HCP user account or group account configuration includes settings that specify what you have permission to do in the Console. The menu options, pages, and panels that you see in the Console depend on the permissions that have been configured for your user or group account.

If an AD user belongs to multiple AD groups for which HCP group accounts exist, that user has all the permissions associated with all those group accounts.

For more information on user and group accounts, see About user and group accounts. For information on AD, see Configuring Active Directory to support HCP.

Console sessions

A System Management Console session begins when you take one of these actions:

Log into the Console using an HCP user account or recognized AD user account.

Access a Console page while logged into Windows with a recognized AD user account. This is called single sign-on. With single sign-on, you don’t need to explicitly log into the Console.

For single sign-on to work, your web browser must be configured to support it. For more information on this, see Browser configuration for single sign-on with Active Directory.

A session ends when you log out. During a session, you can perform any actions for which you have permission.

During a session, if you don’t take any action for a certain amount of time, the Console displays the Idle Timeout page. If you explicitly logged into the session, the Console automatically logs you out and, when you click on any tab on the Idle Timeout page, displays the login page. If you started the session by using single sign-on, when you click on any tab, the Console displays the requested page. The exact amount of idle time allowed is configurable. For information on setting this value, see Changing user account and login settings.

Note: Logging into or out of the System Management Console has no effect on HCP operation.

HCP management API

HCP includes an RESTful HTTP interface to a subset of its administrative functions. Using this interface, called the management API, you can create, modify, and delete tenants and manage replication. If a tenant has been configured to allow system-level users to manage it and search its namespaces, you can also view available service plans that can be assigned to that tenant, and you can create, modify, and delete namespaces, user and group accounts, and content classes for that tenant. Additionally, you can create, modify, and delete retention classes for namespaces owned by the tenant.

You use the HCP System Management Console to enable the management API. To use the management API, you need a user account that includes the applicable permissions for the actions you want to take.

If HCP is configured to support Active Directory authentication, applications can also use recognized AD user accounts to access HCP through the management API. To do this, however, an application must use the SPNEGO protocol to negotiate the AD user authentication itself. For more information on SPNEGO, see http://tools.ietf.org/html/rfc4559.

For information on enabling the management API, see Controlling access to HCP through the management API. For information on using the HCP management API, see HCP Management API Reference.

Hitachi Device Manager and Hitachi Tiered Storage Manager

As an alternative to the System Management Console, you can use Hitachi Device Manager (HDvM) to report on HCP storage usage. Additionally, when using USP or USP-V storage, you can use Hitachi Tiered Storage Manager to migrate repository content to different storage tiers.

You cannot make changes to the HCP configuration through HDvM or Hitachi Tiered Storage Manager.

HCP supports IPv4 and IPv6 network connections to HDvM servers. However, HDvM support for IPv6 network connections varies based on the HDvM server operating system. For information on requirements for HDvM servers that support IPv6 networks, see the applicable Hitachi Command Suite documentation.

For information on connecting HCP to HDvM, see Configuring the Hitachi Device Manager connection.

Hi-Track

Hi-Track® is an HDS product that enables both you and HCP support personnel to monitor your HCP system remotely. With Hi-Track, you can monitor nodes, back-end switches, and front-end switches. For SAIN systems, you can also monitor SAN arrays and Fibre Channel switches.

Hi-Track is for monitoring and error notification purposes only. It does not allow any changes to be made to the HCP system.

HCP supports IPv4 and IPv6 network connections to Hi-Track servers. However, Hi-Track support for IPv6 network connections varies based on the Hi-Track server operating system. For information on requirements for Hi-Track servers that support IPv6 networks, see the applicable Hi-Track documentation.

Trademark and LegalDisclaimer

© 2016 Hitachi Data Systems Corporation. All rights reserved.