New Features in 5.3.2

  • Updated on Jan 30, 2026
  • Published on Jan 26, 2026
  • 2 minute(s) read
Prev Next

The following features are first introduced in VAST Cluster 5.3.2:

VAST Cluster 5.3.2 also include features that were first introduced in release 5.2.2:

Performance QoS Limits for Tenants

  • Added an ability to set performance QoS limits per tenant. The limits are static and include maximum allowed bandwidth and IOPS, including corresponding bursts and credits, for read and/or write operations (separately or in total). Tenant QoS is supported for NFSv3, NFSv4, SMB and S3 workloads.

    To set or update performance limits for a tenant:

    • In VAST Web UI, go to tenant settings (Element Store -> Tenants -> choose to create or edit a tenant) and open the Tenant Limitation tab. Toggle the Enable performance rules option on and set the limits in the fields provided.

    • In VAST CLI, use the --static-limits option on the tenant create or tenant modify command, or the --no-static-limits option on the tenant modify command.

Host NQN-Based Tenant Resolution

VAST Cluster 5.3.2 can route block access requests to correct tenants based on the host NQN. Prior to this change, the correct tenant was determined based on the IP addresses in the request.

Host NQN-based tenant resolution lets you set up a block access environment where multiple VAST tenants share the same virtual IP pool and the same client IP range.

The following prerequisites must be met for successful tenant resolution by host NQN:

  • The tenants participating in tenant resolution share a single virtual IP pool flagged as an all-tenants pool.

    To configure an all-tenants pool in VAST Web UI, select All Tenants option in the Tenant dropdown in virtual IP pool settings.

  • No tenant-specific client IP range is configured for each of the participating tenants.

    To verify this in VAST Web UI, open tenant settings and check that there are no IPs set in the IP Addresses for Client Data Access tab.

  • Each host has an NQN that is unique across the participating tenants.

    Ensure that the cluster does not have any hosts sharing the same host NQN across the tenants. If there are some, delete them manually and recreate using a unique cluster-wide NQN for each host.

    Hosts being created with VAST Cluster 5.3.2 are automatically validated to ensure their NQNs are unique. To disable automatic validation, contact VAST Support.

  • The --hostid used on an nvme discover or nvme connect request is paired with one and only one host NQN.

  • Host NQN-based tenant resolution is enabled for the cluster.

    The feature is by default disabled. To enable it, contact VAST Support.

Related articles