A tenant can be configured to isolate load-balanced application configurations on the NSX Advanced Load Balancer. This is an optional configuration which should be chosen depending on the business requirements.
Please refer to the Isolation Model for Load-Balanced Applications before deciding.
The NSX Advanced Load Balancer will have the ‘admin’/ provider tenant configured by default.
This workflow is optional and is intended to be used only if implementing tenancy on the NSX Advanced Load Balancer.
Prerequisites
Verify that the Controller cluster is deployed and operational, refer to Create an NSX Advanced Load Balancer Controller Cluster section.
Procedure
(Option 1) Create a Tenant with ‘config isolation only’.
In a Linux shell, SSH to the Controller cluster VIP by using [email protected].
Specify the NSX Advanced Load Balancer CLI by executing ‘
shell –user admin –password <ENTER_PASSWORD>
’.Create a Tenant by executing the following CLI commands:
configure tenant <TENANT_NAME> config_settings se_in_provider_context tenant_access_to_provider_se no tenant_vrf save save
(Option 2) Create a Tenant with ‘config + data isolation’.
In a Linux shell, SSH to the Controller cluster VIP by using
[email protected]
Specify the NSX Advanced Load Balancer CLI by executing ‘
shell –user admin –password <ENTER_PASSWORD>
’Create a Tenant by executing the following CLI commands:
configure tenant <TENANT_NAME> config_settings no se_in_provider_context no tenant_access_to_provider_se no tenant_vrf save save