Hitachi G600 Administration Manual
Hitachi G600 Administration Manual
This guide explains user management, including the different types of system administrators, their
roles, and how to create and manage users. Note that some features apply only to individual
platforms and may not be applicable to your configuration.
MK-92HNAS013-11
September 2017
No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including
photocopying and recording, or stored in a database or retrieval system for commercial purposes without the express written permission
of Hitachi, Ltd., or Hitachi Vantara Corporation (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 Corporation at https://support.HitachiVantara.com/
en_us/contact-us.html.
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 Corporation.
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 to access relevant data; and
2) Verifying that 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.
EXPORT CONTROLS - Licensee will comply fully with all applicable export laws and regulations of the United States and other
countries, and Licensee shall not export, or allow the export or re-export of, the Software, API, or Materials in violation of any such laws
or regulations. By downloading or using the Software, API, or Materials, Licensee agrees to the foregoing and represents and
warrants that Licensee is not located in, under the control of, or a national or resident of any embargoed or restricted country.
Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries.
AIX, AS/400e, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, eServer, FICON, FlashCopy, IBM, Lotus, MVS, OS/390,
PowerPC, RS6000, S/390, System z9, System z10, Tivoli, z/OS, z9, z10, z13, 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 web site are properties of their respective owners.
3
Storage System User Administration Guide for Hitachi NAS Platform and VSP Gx00 and Fx00 with NAS Modules
Virtual Storage Platform G400, G600, G800 and Virtual Storage Platform
F400, F600, F800 storage systems can be configured with NAS modules to
deliver native NAS functionality in a unified storage platform. The unified VSP
Gx00 models and VSP Fx00 models automatically form a two-node cluster in
a single chassis upon installation, with no external cabling required.
Related Documentation
Release Notes provide the most up-to-date information about the system,
including new feature summaries, upgrade instructions, and fixed and known
defects.
Administration Guides
• System Access Guide (MK-92HNAS014)—Explains how to log in to the
system, provides information about accessing the NAS server/cluster CLI
and the SMU CLI, and provides information about the documentation, help,
and search capabilities available in the system.
• Server and Cluster Administration Guide (MK-92HNAS010)—Provides
information about administering servers, clusters, and server farms.
Includes information about licensing, name spaces, upgrading software,
monitoring servers and clusters, and backing up and restoring
configurations.
• Storage System User Administration Guide (MK-92HNAS013)—Explains
user management, including the different types of system administrator,
their roles, and how to create and manage these users.
Preface 5
Storage System User Administration Guide for Hitachi NAS Platform and VSP Gx00 and Fx00 with NAS Modules
Note: For a complete list of Hitachi NAS open source software copyrights and
licenses, see the System Access Guide.
Hardware References
• Hitachi NAS Platform 3080 and 3090 G2 Hardware Reference
(MK-92HNAS017) —Provides an overview of the second-generation server
hardware, describes how to resolve any problems, and replace potentially
faulty parts.
• Hitachi NAS Platform and Hitachi Unified Storage Series 4000 Hardware
Reference (MK-92HNAS030)—Provides an overview of the Hitachi NAS
Platform Series 4000 server hardware, describes how to resolve any
problems, and how to replace potentially faulty components
• Hitachi NAS Platform System Manager Unit (SMU) Hardware Reference
(MK-92HNAS065)—This document describes the usage and replacement
instructions for the SMU 300/400.
6 Preface
Storage System User Administration Guide for Hitachi NAS Platform and VSP Gx00 and Fx00 with NAS Modules
Preface 7
Storage System User Administration Guide for Hitachi NAS Platform and VSP Gx00 and Fx00 with NAS Modules
Getting help
Hitachi Data Systems Support Connect is the destination for technical support
of products and solutions sold by Hitachi Data Systems. To contact technical
support, log on to Hitachi Data Systems Support Connect for contact
information: https://support.hds.com/en_us/contact-us.html.
8 Preface
Storage System User Administration Guide for Hitachi NAS Platform and VSP Gx00 and Fx00 with NAS Modules
Thank you!
Preface 9
Storage System User Administration Guide for Hitachi NAS Platform and VSP Gx00 and Fx00 with NAS Modules
All administrators can connect to the NAS storage system through NAS
Manager, the browser-based management utility provided by the system
management unit (SMU). Additionally, Global Administrators on an external
Read-only users: The above roles (when defined for local users or Active
Directory groups) can be modified by making them read-only. A read-only
user has permission to view most pages of the NAS Manager; however, they
are not generally allowed to perform any actions on the NAS Manager that
would trigger a system or configuration change.
□ Read-only users
Read-only users can view the Details pages and see the objects on those
pages, but buttons that submit changes, such as the OK button, are
disabled. Read-only users may use the Cancel button on a Details page to
navigate away from the page.
Note: Once a user is assigned the read-only attribute, their status as read-
only may not be changed. To change a user's status from read-only, it is
necessary to delete the user or the Active Directory group and re-add them
with new read/write privileges.
Inaccessible pages
The following NAS Manager pages are not visible to read-only users:
• Send Test Event
Procedure
1. Navigate to Home > SMU Administration > SMU Users to display the
SMU Users page.
2. Click add to display the Add SMU User page:
Name The name of the new user account. This name will be requested when
logging in to the SMU. The rules for user names are:
• For Global administrators only, if the user will access the SMU
through the CLI, the user name:
○ Must start with a letter or an underscore, and may consist of up
to 31 alphanumeric characters and the underscore (_) and the
hyphen (-).
○ Cannot match certain special purpose names: root, manager,
postgres, nobody, or nfsnobody.
○ Cannot match certain special purpose user ID numbers: for
example, those with uid less than 502.
• For all types of administrators, if the user will access the SMU only
through NAS Manager, the user name may consist of alphanumeric
characters and/or the underscore (_), the hyphen (-), the equal sign
(=), parentheses "(" or ")", brackets ( [ or ] ), the pound sign (#)
and the exclamation point (!).
• Supervisor is a reserved system user name. It is not available as a
new user name.
Password Enter the password that will be used when this user account logs in. The
password cannot exceed 256 characters.
This field only applies when the User Type is selected to Local. It does
not apply when the RADIUS User Type is selected.
Confirm Password Confirm the password entered in the previous field by entering it in
again. Only applies when the Local User type is selected.
User Level Specify the level for the new administrator that you are creating. You
can select any one of the following:
• Global Administrators can manage everything in the system: file
systems, file services, or file system related features and functions,
storage devices and their components. Also, the Global Administrator
creates and manages SMU user profiles (Server Administrators,
Storage Administrators, Server+Storage Administrators, and other
Global Administrators). Global Administrators also control what
servers and storage devices each administrator can access.
• Storage Administrators manage storage devices, as specified in
the administrator profile created by the Global Administrator.
Read-Only User Defines the user as read-only. A read-only user may be given Global,
Server, Storage or Server+Storage access. Based on their defined role,
an individual user may or may not perform specific tasks, such as
viewing, creating, or modifying files and data. A read-only user has
permission to view most pages of the NAS Manager; however, they are
not generally allowed to perform any actions that would trigger a system
or configuration change.
Note: Read-only users can not access the CLI, and a user
with CLI access may not be read-only. If either of these options
is checked, the other one is disabled.
SMU CLI Access If the administrator is allowed to log in and access the SMU CLI of an
(for Global external SMU, select the SMU CLI Access check box.
Administrators
only)
Selected Managed For Server administrators, lists the servers that the administrator can
Servers manage. Note that a Server administrator cannot manage the storage
attached to these servers. Not available for Global administrators,
because Global administrators are allowed to manage all storage and all
servers.
For Storage administrators, lists servers that have attached storage that
the administrator can manage. Note that a Storage administrator cannot
manage these servers, only the storage attached to these servers.
3. Enter the user name for the new administrator in the Name field.
4. Specify if the administrator login is authenticated locally (by the SMU) or
by a RADIUS server by selecting the appropriate User Type.
5. If the User Type is local, specify the initial login password for the new
administrator by filling in the Password and the Confirm Password
fields.
6. Specify the user level for the new administrator that you are creating.
You can select one of the following:
• Global
• Storage
• Server
• Server+Storage
7. For Global Administrators only, if the administrator is allowed to log in
and access the SMU command line interface (CLI) of an external SMU,
select the SMU CLI Access check box.
8. Using the Available Servers and the Selected Servers lists, specify
the servers the administrator can access or the servers with the storage
the administrator can manage.
• To grant management privileges for a server or the storage attached
to a server, move the server from the Available Servers list to the
Selected Servers list.
• To revoke management privileges for a server or the storage attached
to a server, move the server from the Selected Servers list to the
Available Servers list.
• To move the server between the Available Servers and the Selected
Servers lists, select the server, and use the arrow buttons between
the lists.
9. Review the profile, and verify that it is correct.
• If the profile is correct, click OK to save and enable the user profile,
and then return to return to the SMU Users page.
Procedure
1. Navigate to Home > SMU Administration > SMU Users to open the
SMU Users page.
2. Click details to display the SMU User Details page for the user whose
profile you want to modify.
Item/Field Description
User Type Describes if the user is authenticated by the SMU itself (local
users), or if the user is authenticated by a RADIUS server.
Password and Confirm For users authenticated by the SMU only (local users). These
Password fields do not apply for users authenticated by a RADIUS server.
The password for the user. Characters are hidden, and the exact
same password must be entered in both fields. The password
cannot exceed 256 characters.
You cannot change the User Type or User Level of a user. If such a
change is needed, delete the old user and create a new user.
SMU CLI Access For global administrators only, when the check box is selected,
the administrator can access the SMU using the CLI as well as
NAS Manager.
Available HNAS Servers Not available for global administrators, because global
administrators are allowed to manage all storage and all servers.
Selected HNAS Servers Not available for global administrators, because global
administrators are allowed to manage all storage and all servers.
OK Saves the currently defined user profile and returns to the SMU
Users page.
Cancel Returns to the SMU Users page without saving the profile.
Note: For users authenticated by the SMU only (local users), not
available for users authenticated by a RADIUS server.
To edit the user’s password, type the new password in the Password
and Confirm Password fields.
4. For global administrators only, allow or disallow SMU CLI access.
When the check box is selected, the administrator can access the SMU by
using the CLI as well as NAS Manager.
5. Specify server and/or storage management rights.
• To grant management privileges for a server or the storage attached
to a server, move the server from the Available Servers list to the
Selected Servers list.
• To revoke management privileges for a server or the storage attached
to a server, move the server from the Selected Servers list to the
Available Servers list.
• To move the server between the Available Servers and the Selected
Servers lists, select the server, and use the arrow buttons between
the lists.
6. Click OK to save the profile and return to the SMU Users page.
Procedure
Field/Item Description
Current Password Displays a series of dots representing the currently specified password
(the actual password cannot be displayed).
New Password The new password. The password cannot exceed 256 characters.
Confirm New The new password again. Must be exactly the same as what you
Password entered in the New Password field.
Procedure
1. Navigate to Home > SMU Administration > SMU Users to display the
SMU Users page.
2. Click details to display the SMU User Details page.
Item/Field Description
User Type Describes if the user is authenticated by the SMU itself (local
users), or if the user is authenticated by a RADIUS server.
Password and Confirm For users authenticated by the SMU only (local users). These
Password fields do not apply for users authenticated by a RADIUS server.
The password for the user. Characters are hidden, and the exact
same password must be entered in both fields. The password
cannot exceed 256 characters.
You cannot change the User Type or User Level of a user. If such a
change is needed, delete the old user and create a new user.
SMU CLI Access For global administrators only, when the check box is selected,
the administrator can access the SMU using the CLI as well as
NAS Manager.
Available HNAS Servers Not available for global administrators, because global
administrators are allowed to manage all storage and all servers.
Selected HNAS Servers Not available for global administrators, because global
administrators are allowed to manage all storage and all servers.
OK Saves the currently defined user profile and returns to the SMU
Users page.
Cancel Returns to the SMU Users page without saving the profile.
Active Directory users are assigned full access rights to the SMU functionality.
For local and RADIUS users the user profile details are specified when the
user account is created.
After Active Directory connection settings and groups have been configured
for the SMU, it will allow logins from enabled users who supply their Active
Directory name and password. This is typically the same name and password
that the user would use to log into Windows and other enterprise
applications. Unlike SMU local and RADIUS user names, Active Directory user
names are case-insensitive. Active Directory passwords are case-sensitive
and cannot be changed from the SMU; they are maintained in the Active
Directory server.
There are a number of benefits for SMU users. The administrator does not
need to maintain a separate set of user details, because the SMU can just
make use of the Active Directory enterprise user database. Users can login
using their usual name and password instead of having to remember a
separate set of credentials for the SMU. And instead of configuring access for
individual users, the SMU administrator just has to specify the Active
Directory groups whose members have login rights.
Although the SMU supports RADIUS and Active Directory for external
authentication, they are mutually exclusive; it is not possible to have them
both configured for external authentication at the same time.
When a login attempt is made, the SMU first tries to authenticate the
credentials as a local user. If that fails, and Active Directory is configured,
they are authenticated as an Active Directory user.
In order to enable Active Directory use, the SMU administrator needs to know
the following information:
• The domain in which the Active Directory users and groups that will access
the SMU are located.
• The LDAP distinguished name and password of an Active Directory user
that has read access to users and groups on the Active Directory servers.
This is referred to as the Search User. The user can search for users or
groups under the supplied base distinguished name.
• The addresses of one or more Active Directory servers that maintain the
users and groups for the domain. The content of all configured servers
must be identical. If DNS servers have been configured for the SMU, then
the SMU should be able to automatically discover these server addresses
via the find servers button on the setup page. SRV records must be setup
in order for find servers to find the Active Directory servers.
• The Active Directory group or groups whose members are to be given the
right to log into the SMU.
• If RADIUS was previously in use and it is to be replaced by Active
Directory, then the RADIUS configuration must first be removed before
Active Directory can be configured. This is done from the Home>SMU
Administrator>RADIUS Servers page by clicking the remove all
settings button. No RADIUS user will be able to log into the SMU after
this is done.
Note: On the NAS system, local users and Active Directory groups can be
created with read-only access. A read-only user has permission to view most
pages of the NAS Manager; however, they are not generally allowed to
perform any actions on the NAS Manager that would trigger a system or
configuration change
Field/Item Description
Connection settings
Base Distinguished Name The LDAP root location for users and groups. The name is
recommended to contain just the domain components.
Use TLS to secure Active Uses encrypted LDAP communications for Active Directory
Directory connections authentication by default. Uncheck this option to use non-
secured LDAP communications for Active Directory
authentication.
Distinguished Name The LDAP distinguished name for a user that has search
capabilities.
Servers
IP Address or DNS Name The address of one or more Active Directory servers for the
domain. Each server should hold identical content. The
maximum number of servers is 20.
find servers Queries DNS to show the list of available Active Directory
servers for the domain.
Add Add an Active Directory server after you have entered its
fully qualified domain name or IP address.
apply Submit the page and save the connection settings and server
list to the SMU database.
Groups
Groups with access to the Shows groups with access to the SMU. Active Directory users
SMU who belong to these groups can access the SMU.
Modify groups Click to go to the Active Directory Groups page, where you
can add groups.
Actions
remove all settings Removes all Active Directory server settings, including server
list, connection settings, search user credentials and groups.
After this action, Active Directory users can no longer log into
the SMU.
6. If there is more than one server, the list can be prioritized using Move
Up or Move Down .
7. Click Apply to submit this page and save the connection settings and
server list to the SMU database.
The SMU will perform a connection test to check that it can access the
configured servers with the supplied details and display a warning if the
SMU cannot, giving the user the opportunity to modify the settings or to
save them as they are.
Note that the administrator is only able to configure groups after Active
Directory servers have been added on the Active Directory Servers page.
Procedure
Field/Item Description
details Click the details button in the right-hand column to view details
of the associated group.
2. Click add and use the Add Active Directory Group page to add
groups.
Field/Item Description
Base Distinguished Name The LDAP root location for users and groups. The name is
recommended to contain just the domain components.
Group Distinguished Name The LDAP root location for users and groups. The name is
recommended to contain just the domain components. Groups
can be added manually by entering their distinguished name and
then pressing the OK button. A maximum of 100 groups can be
added. Alternatively, groups can be added by using the find
group button.
find group Queries the Active Directory to show the list of available groups.
The list can be filtered by entering a partial group name. A
maximum of 1000 group names is displayed.
User Level for Group The user levels that can be assigned to group members are the
Members same as those that can be assigned to local or RADIUS users
and have the same meanings. The default is Global, but the
level can be modified by selecting one of the other radio buttons.
Read-Only Access Defines the group users as read-only. Members of the group may
log into the SMU, but with read-only access. Read-only users
may be given Global, Server, Storage or Server+Storage access.
Based on the defined roles in the group, read-only users may
not perform specific tasks, such as creating, or modifying a files
and data. Users in a read-only group have permission to view
most pages of the NAS Manager; however, they are not allowed
to perform any actions that would trigger a system or
configuration change. The Active Directory Group Details page
will not allow the read-only attribute to be modified. The group
would need to be deleted and re-added to change this attribute.
OK Click to save the group details. The SMU checks that the group
exists in Active Directory. If the group does not exist (or if the
SMU failed to access any AD server) the user is asked for
confirmation that they still wish to save it. After saving the
group, the updated group list page is displayed.
cancel Cancels input.
When displaying the group details, the SMU checks that the group exists
in Active Directory and displays a warning if it does not exist or if it could
not access an Active Directory server. The user level cannot be modified
once the group has been added. In order to modify the user level, the
group would have to be deleted, then added again. Click the cancel
button to return to the Active Directory Groups page.
Field/Item Description
You can specify and prioritize multiple RADIUS servers for authentication.
Note: The SMU contacts RADIUS servers in order of priority; the SMU will
always try to contact higher priority servers before lower priority servers, and
you cannot map SMU users to authenticate through a specific RADIUS server.
If you specify an incorrect secret or there are network problems that prevent
the SMU from communicating with the highest priority RADIUS server, the
SMU will try to contact the secondary RADIUS server, then the third RADIUS
Procedure
Procedure
RADIUS server IP To connect with the RADIUS server, specify an IPv4 or IPv6 address,
address or DNS name or a host name (host name is not recommended). An IP address is
preferred, both because it eliminates the dependency on the network
DNS sever(s), and to improve login performance.
The SMU Network Configuration page (navigate to Home > SMU
Administration > SMU Network Configuration) shows the active
IP addresses. It is recommended that IPv4 on eth0 and the current
IPv6 addresses be added to the "allowed client" list on each RADIUS
server. For more information on setting up the SMU Network
Configuration for IPv6, see the Network Administration Guide.
Port Specify the RADIUS server authentication port. The default RADIUS
server authentication port is 1812, but you should check with the
RADIUS server administrator to make sure that 1812 is the correct
port.
Timeout Specify the timeout, which is the number of seconds the SMU waits
before retrying (retying is re-transmitting the authentication request
to the same RADIUS server). The default is 3 seconds. If the timeout
is reached and there is no response from the first RADIUS server in
the list, the SMU attempts another retry.
Retry Count Specify the retry count. The default is 3. When the retry limit is
reached, the SMU sends the request to the next RADIUS server in the
list. When the retry limit for the second server is reached, the SMU
attempts to reach the next server in the list, until there are no more
servers to try. If there are no more servers to try, the user cannot be
authenticated, and the login fails.
OK When you are done making changes, click OK to test connectivity and
save the configuration for this RADIUS server and return to the
RADIUS Servers page.
Procedure
Field/Item Description
Timeout The number of seconds the SMU waits before retrying (retrying
is re-transmitting the authentication request to the same
RADIUS server). If the timeout is reached and there is no
response from the first RADIUS server in the list, the SMU
attempts another retry.
Retry Count When the retry limit is reached, the SMU sends the request to
the next RADIUS server in the list. When the retry limit for the
second server is reached, the SMU attempts to reach the next
server in the list, until there are no more servers to try. If the
timeout is reached, and there are no more servers to try, the
user cannot be authenticated, and the login fails.
Check connectivity Click to check the connectivity status of the RADIUS server.