Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Managing multi-tenancy

Managing multi-tenancy on the NAS server and EVSs.

Multi-tenancy is an operational mode for the NAS server, which allows the NAS server to support multiple tenants, each with at least one EVS. Multi-tenancy supports tenant configurations in logically separate serving environments on a single physical server or cluster. Each EVS has an individual configuration and is managed as an individual unit, without sharing a global configuration. In stand-alone (single tenant) mode, the NAS server has a global configuration which can be shared by EVSs.

Multi-tenancy management interfaces

Currently NAS Manager does not include support for enabling and disabling multi-tenancy; to use this feature, you must use CLI commands. See the following CLI man pages for detailed information on configuring and using multi-tenancy:

The following commands are used to manage multi-tenancy at the NAS server level:

  • multi-tenancy-disable
  • multi-tenancy-enable
  • multi-tenancy-show

For more information about these commands, refer to the Command Line Reference. For an overview of multi-tenancy related commands and other related information, see the multi-tenancy command in the Command Line Reference.

Viewing HNAS multi-tenancy status

Use the multi-tenancy-show command to view the status of the multi-tenant environment.

Command example:

server:$ multi-tenancy-show
Multi-tenancy is disabled.
server:$

Considerations for enabling HNAS multi-tenancy

In most cases, this command will only be run when first configuring a new system.

Enabling the multi-tenant environment causes a temporary loss of service to all EVSs while they are enabled for use.

NoteAll connections to the server are disconnected during the enabling process. This includes the connection that may be used to execute the enabling command.

HNAS multi-tenancy limits

Multi-tenancy can only be enabled if all cluster nodes are multi-tenant capable, and are all online. It also requires an EVS Security license.

Multi-tenancy cannot be enabled:

  • if any EVS is configured with global security settings. Resolve this by setting the EVSs to individual security by issuing the evs-security command and copying the required configuration.

  • if a deprecated VLAN subnet is still configured in the system, a VLAN interface must be used. Remove VLAN subnets by using the vlan remove-all command. Create appropriate VLAN interfaces using the using vlan-interface-create command.
  • If a cluster namespace is configured, issue the namespace-delete command before enabling multi-tenancy.

Enabling HNAS multi-tenancy

To enable HNAS multi-tenancy, issue the multi-tenancy-enable command.

Enabling the multi-tenant environment will cause a temporary loss of service to all EVSs while they are enabled for use.

Command Example:

server:$ multi-tenancy-enable
Warning: Enabling multi-tenancy significantly affects the configuration of the HNAS.
Have you read and understood the multi-tenancy man page?(Y/N)[N]:
y
Have you read and understood the multi-tenancy-enable man page?(Y/N)[N]:
y
Do you understand that once enabled, multi-tenancy cannot be disabled until all file serving EVSs have been deleted?(Y/N)[N]:
y
Warning: All active connections, including any remote console sessions, will be disconnected to allow the network service to support multi-tenancy.
Do you want to proceed?(Y/N)[N]:
y
Enabling multi-tenancy.
Operation successful.
server:$

Managing multi-tenancy on the NAS server

The administration of the NAS server is performed by the NAS server administrator of the application service provider (ASP), who has access to the administrative EVS. The NAS server administrator of the ASP is responsible for managing the storage, file systems, shares, and exports for the tenant.

NAS server multi-tenancy is enabled and managed through CLI commands. Management of shares, exports, file systems, and storage pools/spans, replication, migration, and any other functions that are not EVS-specific performed in the same way regardless of whether the NAS server is operating in multi-tenant mode or in single tenant (stand-alone) mode.

The following commands are used to manage multi-tenancy at the NAS server level:

  • multi-tenancy-disable
  • multi-tenancy-enable
  • multi-tenancy-show

For more information about these commands, refer to the Command Line Reference. For an overview of multi-tenancy related commands and other related information, see the multi-tenancy command in the Command Line Reference.

Managing multi-tenancy for an EVS

Multi-tenancy extends HNAS individual security mode to provide true separation by maintaining per EVS variables and connection states. Each EVS has its own complete and separate environment which is configured as required (for example, network interfaces, routing, and security aspects are set on a per-EVS basis, instead of a global configuration).

When managing an EVS through the command line interface, the individual EVS context (label) is displayed on the command line prompt, and commands will affect only that EVS. Use the console-context command to change the current context.

The following commands are used to manage the EVS when multi-tenancy is enabled:

  • evsipaddr
  • set-for-evs
  • routing-by-evs
  • routing-by-evs-disable
  • routing-by-evs-enable
  • routing-by-evs-show

For more information about these commands, refer to the Command Line Reference. For an overview of multi-tenancy related commands and other related information, see the multi-tenancy command in the Command Line Reference.

 

  • Was this article helpful?