Server and Cluster Administration Guide
- Last updated
- Save as PDF
This guide provides information about administering servers, clusters, and server farms. Includes information about licensing, name spaces, upgrading firmware, monitoring servers and clusters, the backing up and restoring configurations.
- Child Topics
- Using the SMU Setup Wizard
- Configuring SMU security (HNAS server only)
- Configuring SMU security
(NAS module only)
This screen allows you to change web application security settings.
- Disabling protocols and cipher suites
Use this procedure to disable individual protocols or cipher suites as by using the Security Options page in the SMU Administration menu.
- Configuring an SMTP relay for the SMU
- Displaying the SMU software version
- Selecting SMU-managed servers
- Changing the IP address of a managed server
- Using the SMU as an NTP server
- Cloning server settings (HNAS server only)
- Using the Server Setup Wizard
- Configuring server management access
- Configuring server identification
- Configuring server date and time
- Managing license keys
- Displaying storage server version information
- Clusters and server farms
- Clusters
- Server farms
- Using clusters
- Using cluster name space (CNS)
- Configuring read caching
- Secure virtual servers
- Secure EVS considerations
- Securing an EVS
- Removing an individual security context from a secure EVS
- EVS name spaces
- Creating an EVS
- Assigning a file system to an EVS
- Virtual server (EVS) management
- Displaying EVS details
- Migrating an EVS within a cluster
- EVS migration within a server farm (HNAS server only)
- Storage system status
- Configuring devices on the System Monitor
- Checking the system status
- Performance Information Reporting (PIR)
- Using the server status console
- Checking the status of a server unit
- Checking SMU status
- Monitoring multiple servers (HNAS server only)
- Monitoring storage subsystems with Hitachi Device Manager
- Management Auditing
- Available performance graphs
- Controlling the performance graph display
- Storage server statistics
- Event logging and notification
- Monitoring file system free space
The free space monitor will generate warnings in the Event log when the mount points reach their pre-configured thresholds.
- FTP auditing
- Monitoring Fibre Channel switches (HNAS server only)
- Generating a custom private key and SSL certificate
- Generating a certificate signing request (CSR)
- Accepting self-signing certificates
- Configuring cipher suites
You can restrict which cipher suites may be used to comply with your security policies.
- Configuring the SSL/TLS version
You can restrict which versions of SSL/TLS may be used to comply with your security policies.
- Obtaining and importing a CA-signed certificate
You may provide your own Certificate Authority (CA) signed certificates, instead of the default "self-signed" certificate.
- Understanding multi-tenancy
Multi-tenant architecture provides companies, such as application service providers (ASPs), the ability to support more than one customers' services on a single server, but still keep them logically separate.
- Understanding
HNAS multi-tenancy benefits
Using HNAS multi-tenancy can help you avoid some of the challenges faced with traditional multi-tenant environments.
- How multi-tenancy mode differs from stand-alone mode
The HNAS multi-tenancy mode option provides additional security and configuration enhancements.
- How multi-tenancy differs from per-EVS security
Both HNAS configuration modes provide per-EVS security.
- Multi-tenancy requirements
Requirements for enabling and using multi-tenancy mode.
- Disabling HNAS multi-tenancy
- Managing multi-tenancy
Managing multi-tenancy on the NAS server and EVSs.
- Overlapping IP address support for HNAS multi-tenancy
- Routing by EVS
Routing by EVS restricts the choice of source addresses available to the routing engine to those associated with the source EVS. Routing by EVS is always enabled in multi-tenancy mode. Routing by EVS can also be enabled when not in multi-tenancy mode.
- Configuring routes per EVS
Multi-tenancy causes the routing engine to keep routes by EVS, so it is necessary to maintain different sets of routes for each EVS. Gateway, network and host routes (IPv4 and IPv6) are configured per EVS when multi-tenancy is enabled using the following commands: route-gateway-add, route-net-add, and route-host-add.
- Understanding EVS crosstalk checking
The HNAS platforms support detection and prevention of EVS crosstalk. Crosstalk can cause the server to fail to respond. Crosstalk checking is especially important when duplicate IP ranges are being used.
- Multi-tenancy-aware protocols
The HNAS multi-tenancy mode feature recognizes and uses certain protocols. This mode extends the previous stand alone mode protocol support.
- Management Auditing events