Overview

You can use virtual domains (VDOMs) to delegate administration for tenant deployments. This can be useful for large enterprises and multi-tenant deployments such as web hosting.

Virtual domains are not enabled by default. Enabling and configuring VDOMs can only be performed by the admin administrator.

VDOMs alter the structure and available functions in the GUI and CLI, according to whether or not you are logging in as the admin administrator, and, if you are not logging in as the admin administrator, the administrator account’s assigned access profile.

Table 20: Differences between administrator accounts when VDOMs are enabled
	admin account	Other administrators
Access to config global	Yes	No
Can create administator accounts	Yes	No
Can create and enter all VDOMs	Yes	No

If VDOMs are enabled and you log in as admin, the complete set of CLI commands appear, allowing unrestricted access and VDOM configuration. The admin administrator account cannot be restricted to a VDOM. Other administrators are restricted to their VDOM, and cannot configure VDOMs or global settings.

If VDOMs are enabled and you log in as any other administrator, you enter the VDOM assigned to your account. By default, administrator accounts other than the admin account are assigned to the root VDOM. A subset of the typical menus or CLI commands appear, allowing access only to only feature configuration, logs and reports specific to your VDOM. You cannot access global configuration settings or enter other VDOMs.