Skip to main content
Outside service Partner
Hitachi Vantara Knowledge

HCP administrative responsibilities


HCP administrative responsibilities consist of:

Managing HCP user and group accounts

Monitoring the HCP system

Configuring the system

Managing the system hardware

Managing tenants

Managing repository access across all namespaces

Ensuring HCP system recovery

Helping with troubleshooting

Most system configuration activities are one-time operations that you perform when HCP is first installed. Most monitoring and management activities are ongoing.

You perform configuration, monitoring, and management activities in the HCP System Management Console. For information on using this Console, see System Management Console.

Managing user and group accounts

HCP user and group accounts determine whether you can log into the HCP System Management Console, Tenant Management Console for the default tenant, or Search Console for access to the default namespace. For the System and Tenant Management Consoles, they also determine which actions you’re allowed to perform after logging in.

You use the System Management Console to create, modify, and delete system-level user and group accounts. For each HCP user account, you specify whether it’s authenticated locally or by RADIUS. To enable RADIUS authentication, you need to configure connections to one or more RADIUS servers.

You also use the System Management Console to configure login settings for the Console as a whole.

Additionally, you use the System Management Console to clear the AD cache. You may need to do this, for example, to immediately discontinue system access by a user whose AD user account is no longer valid.

For information on:

Managing user and group accounts and configuring login settings, see Account administration

Configuring connections to RADIUS servers, see Configuring connections to RADIUS servers

Clearing the AD cache, see Clearing the Active Directory cache

Monitoring the system

HCP is a self-monitoring, self-healing system that automatically alerts you to problems it cannot resolve itself. It also provides the means for you to monitor it. This type of monitoring entails:

Periodically checking the status of hardware, system resources, services, and available storage

Watching for alerts that may indicate conditions requiring human intervention

Periodically reviewing system resource usage and the system log to ensure that HCP is running smoothly and not exceeding its storage license.

Reviewing and, if required, responding to system log messages received through syslog servers, SNMP managers, or email

If SNMP is enabled, evaluating and, if required, responding to trap-generated event notifications

You can also generate chargeback reports. Typically, these reports are used as input to billing applications that need to determine charges for capacity and bandwidth usage at the tenant or namespace level. However, they are also a good source of information for system analysis, enabling you to adjust storage and bandwidth allocations based on usage patterns.

For information on these activities, see:

System-level administration

Hardware administration

System monitoring

System Management Console alerts

Configuring the system

Configuring HCP entails:

Optionally, making extended storage components such as NFS storage volumes and Amazon S3 cloud storage known to HCP so that content can be offloaded from primary storage onto each type of extended storage (see Storage administration)

Optionally, configuring user-defined networks so that you can segregate network traffic for different purposes (see Network administration)

Enabling or disabling access to the HCP nodes (see Setting network security)

Managing domains and SSL server certificates (see Managing domains and SSL server certificates)

Controlling access to the System Management Console (see Controlling access to the System Management Console)

Controlling access to the HCP management API (see Controlling access to HCP through the management API)

Configuring support for Windows AD or Windows workgroups (see Configuring Active Directory or Windows workgroup support)

Enabling or disabling the use of SNMP for modifying system settings (see Configuring SNMP)

Optionally, configuring HCP to send system log messages to syslog servers, SNMP managers, and/or specified email addresses (see Configuring syslog logging, Configuring SNMP, and Configuring email notification)

Scheduling and configuring HCP services to manage system load, ensure data and metadata integrity and availability, and optimize storage usage (see HCP services)

Managing the system hardware

An HCP system or any of its individual nodes may occasionally need to be shut down or restarted for a variety of reasons, including for hardware maintenance. When you want to retire a node or SAN array, you first need to migrate stored data off that device.

For information on these activities, see:

Shutting down or restarting HCP

Shutting down or restarting individual nodes

Migration service

Managing tenants

HCP system-level administrators create all tenants. Once a tenant is created, you can change only some of its features. Tenant-level administrators are responsible for most tenant management.

In addition to creating and modifying tenants, you can delete tenants, but only if they don’t own any namespaces.

For information on creating, modifying, and deleting tenants, see Tenant administration.

Managing repository access

Managing repository access entails:

Setting the systemwide permission mask, which provides the highest level of control over namespace access (see Setting the systemwide permission mask)

Optionally, enabling and configuring the metadata query engine and API and the HDDS search facility (see Search administration)

Controlling access to the Search Console for the default tenant (see Controlling access to the Search Console for the default tenant)

Ensuring HCP system recovery

Through its services, the HCP system is self-healing, so your intervention is not often required for recovery from unexpected events. Events that may require your intervention, however, include power outages and hardware failures.

To protect against a catastrophic failure of an HCP system, you can implement replication. When you do this, you are responsible not only for configuring the connections between the systems involved but also for managing failover and recovery should that become necessary. For information on using replication for business continuity and disaster recovery, see Replicating Tenants and Namespaces.

NoteWebHelp.png

Note: Default tenant administrators can use the NDMP protocol to back up and restore the default namespace.

Troubleshooting

From the system console for any HCP node, you can run selected diagnostics that can help you analyze and resolve issues with interactions between the node and other components in the HCP environment. Using these diagnostics, for example, you can troubleshoot problems with physical networks, virtual networking, external storage, and DNS.

Occasionally, you may need help resolving problems that occur with the HCP system. In such cases, your authorized service provider may ask you to download the logs HCP maintains internally and send them to the HCP support center.

You download the HCP internal logs from the System Management Console. You can also use the Console to insert comments into these logs to indicate when problems occur and describe their symptoms.

For information on:

Running diagnostics, see Running diagnostics

Adding comments to and downloading the HCP internal logs, see Working with the HCP internal logs

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.