Enhancements in 5.1.0

  • Updated on Jan 30, 2026
  • Published on Jan 28, 2026
  • 8 minute(s) read
Prev Next

Cluster Expansion

  • ORION-119705: Added a capability to specify the IPMI gateway during the cluster expansion procedure.

Element Store

  • ORION-111576: You can configure a view policy to grant read/write or read-only access to clients connecting from a particular virtual IP pool (or pools). To do so:

    • In VAST Web UI, open view policy settings (Element Store -> View Policies -> choose to create or edit a view policy) and in the General tab, select one or more virtual IP pools in the Virtual IP Pools field. In the grid that appears below the field, select Read/write or Read only in the Type of Access column.

    • In VAST CLI, run the viewpolicy create or viewpolicy modify command with the --permission-per-vip-pool option specified.

      Note

      The --vip-pool-ids option on viewpolicy create and viewpolicy modify is deprecated.

  • You can determine whether a view policy is to be used as the default view policy for S3 buckets created via VAST S3 API, as follows:

    • In VAST Web UI, toggle on or off the Use for new S3 buckets option in view policy settings (Element Store -> View Policies -> choose to create or edit a view policy -> go to S3 tab.)

    • In VAST CLI, run the viewpolicy create or viewpolicy modify command with the --enable-s3-default-policy or --disable-s3-default-policy option.

Quality of Service (QoS)

With VAST Cluster 5.1:

  • View QoS policies can be used for NFSv3, NFSv4.1, SMB and S3 views.

  • User QoS policies can be used for NFSv3, NFSv4.1, SMB and S3 users.

The following limitation has been removed:

  • ORION-139524: Setting a minimum limit for read operations does not limit write operations on the same view.

NFSv4.2

VAST Cluster 5.1 introduces support for NFS version 4.2 with the following client features supported:

  • NFSv4.2 Security Labels, Limited Server Mode

    For more information about this capability, see NFSv4.2 Security Labels.

NFSv4.2 support can be enabled or disabled per tenant as follows:

  • In  VAST Web UI, use the Enable NFSv4.2 option in the advanced tenant settings (Element Store -> Tenants -> choose to create or edit a tenant -> go to Advanced tab).

  • In VAST CLI, use the --enable-nfs-v4.2 or --disable-nfs-v4.2 options on the tenant create or tenant modify commands.

NFSv4.1

  • ORION-143964: VAST Cluster will now return the ACE4_IDENTIFIER_GROUP ACE flag for GROUP@ principals. Prior to this change, the flag was returned for principals identified with a GID but not for GROUP@.

NFSv3

  • ORION-94711: Added user controls to determine whether to include the root directory (/) in showmount response when the showmount output suppressing functionality is enabled:

    • In VAST Web UI, the Hide the "/" export option in cluster's general settings (Settings -> Cluster -> General)

    • In VAST CLI, with the --enable-showmount-hide-slash or --disable-showmount-hide-slash options on the cluster modify command.

SMB

  • ORION-154019: Added a capability to disable listing of snapshots (.snapshot) when listing contents of a directory.

S3

  • ORION-138816: Introduced a number of VAST S3 API action improvements:

    • Added support for the following AWS S3 actions:

      • GetObjectVersion

      • PutObjectVersionAcl

      • GetObjectVersionAcl

      • DeleteObjectVersion

      • PutObjectVersionTagging

      • GetObjectVersionTagging

      • DeleteObjectVersionTagging

    • The keyword for the action that returns metadata for object versions, has been changed from ListObjectVersions to ListBucketVersions to make it consistent with the name that AWS S3 uses. The legacy action name, ListObjectVersions, is still supported for backward compatibility. When you create or edit an identity policy in VAST Cluster, the software forces you to use the new keyword, ListBucketVersions.

    • The keyword for the action that lists parts of a multipart upload, has been changed from ListParts to ListMultipartUploadParts to make it consistent with the name that AWS S3 uses. The legacy action name, ListParts, is still supported for backward compatibility. When you create or edit an identity policy in VAST Cluster, the software forces you to use the new keyword, ListMultipartUploadParts.

  • Added the ability to select a tenant where an identity policy applies:

    • In VAST Web UI, select the tenant in the Tenant dropdown in policy settings (User Management -> Identity Policies -> choose to create or edit an identity policy).

    • In VAST CLI, specify the --tenant-id option on the identitypolicy create command.

  • ORION-121559: Added S3 tagging validation to block S3 requests that set an empty tag key or an empty tag value on an object.

VAST Database

  • ORION-172585: Added the following user controls to view and set the number of splits and subsplits used when processing VAST Database and VAST Catalog queries:

    • In VAST CLI, the cluster vast-db-configure and cluster vast-db-show-config commands

    • In VAST REST API, the /clusters/<cluster ID>/vast_db/ endpoint

    The following legacy user controls have been deprecated:

    • In VAST CLI, the splits option on the vastcatalogconfig modify command

    • In VAST REST API, the splits parameter for the /bigcatalogconfig/<ID>/ endpoint

  • ORION-150835: Added support for Trino release 429 and Starburst release 429-e LTS.

  • ORION-149159: Increased the maximum number of columns supported by VAST Database from 31936 to 63872.

Snapshots

  • ORION-150995: Improved the error message that appears when a user tries to create, update or delete a snapshot while the corresponding VAST Cluster services are in the cluster’s deny list. The message now reads: Snapshot, Replication, and Global Namespace services are currently degraded. Please contact VAST Support.

    Note that if you attempt to delete a snapshot while this error condition exist for the cluster, the snapshot can no longer be displayed in VAST Web UI or VAST CLI but remains on the host even after the error condition ends.

VAST Dataspace

  • ORION-143709: Added validations to ensure the name of a cluster being connected to VAST Dataspace complies with the following requirements:

    • The cluster name can only contain alphanumeric characters (in lower or upper case) and hyphens.

    • The cluster name starts with an alphabetic character.

    • The cluster name is up to 128 characters long.

Authentication & Authorization

  • ORION-146051, ORION-138903: Added options to allow IO by users with disabled and/or locked accounts in Active Directory:

    • In VAST Web UI, the Locked users and Disabled users checkboxes in the Locked Accounts in Active Directory pane in tenant settings (Element Store -> Tenants -> choose to create or edit a tenant).

    • In VAST CLI, the following options on the tenant create or tenant modify command:

      • --allow-locked-users

      • --prohibit-locked-users

      • --allow-disabled-users

      • --prohibit-disabled-users

  • ORION-132627: Names of users' domains are now included in data flow analytics.

  • ORION-118289: Updated the mechanism of matching NIS and Active Directory group names so that the matching is now case-insensitive. For example, a group named Abc in NIS and a group named abc in Active Directory are now considered a match for authorization purposes.

VMS

  • ORION-151158: Metrics that were reported per mille (parts of thousand), are now shown as a percentage.

  • ORION-134765: Updated the Rows filtered out and Rows scanned metrics in the VAST DB Row Metrics analytics report to show the number of rows per second instead of the total number of rows (similar to other metrics included in the report).

VAST Web UI

  • ORION-144680: The Active Directory page (User Management -> Active Directory) now features a new column named NTLM Enabled that shows whether NTLM is enabled or disabled for the provider.

  • ORION-139534: Moved the Group membership source option to the NFS tab of view policy settings (Element Store -> View Policies -> choose to create or edit a view policy).

  • ORION-137659: Improved usability when selecting columns to be displayed in VAST Web UI grids. Now the button to open the column selector is located in the top right corner just above the grid.

VAST CLI

  • ORION-176486: Added the --tenant-id option to the cluster stat command. The new option lets you view cluster details per tenant.

  • ORION-143820: Added support for specifying a user in the ‘domain\username’ format when deleting ACEs via VAST CLI.

  • ORION-137642: Added indication of whether developer metrics are being collected or not on the cluster to the cluster show command output.

    Note

    You can enable or disable collection of developer metrics using the cluster modify --enable-metrics or --disable-metrics options.

Platform & Control

  • ORION-164851: Added a validation to ensure that VMS does not allow adding a Mavericks TLC DBox with Rocky Linux-based VAST OS during cluster expansion or node replacement procedures.

  • ORION-139490, ORION-122915, ORION-122663: Expanded hardware listings in VMS to include information about racks where the hardware resides, as follows:

    • In VAST Web UI, the Infrastructure page now features a new tab named  Racks that provides rack details.  

    • VAST CLI has new commands to view and rename racks: rack list, rack show, rack rename.

    • The VAST REST API includes new endpoints that lets you manage racks:

      • /racks/

      • /racks/{id}/

      • /racks/{id}/rename/

    • The CBox and DBox details now include information about the rack where the box resides.

  • ORION-136819: Fine-tuned the internal settings responsible for the number of handles that can be allocated before triggering the SCARCE and HALT WRITES mode alerts.

  • ORION-76775: Added a validation to ensure that all CNodes in a cluster run the same NIC firmware version. If a mismatch is encountered, VMS raises an alarm.

  • ORION-106640: Enhanced the CBox and DBox naming logic to ensure that there are no duplicate box names in the cluster. The DBox or CBox name now consists of a prefix denoting the box type (dbox- or cbox-) and the box’s UID (non-truncated).

  • ORION-56561: Added an internal mechanism for denylisting RAID stripes.

Call Home & Support

  • ORION-176678: Starting with VAST Cluster 5.1.0, you are required to register with Uplink to be able to use the Call Home capability of your VAST cluster.

  • ORION-156423: The Upload via VMS capability now does not require a proxy to be configured.

  • ORION-146448, ORION-109313: Added a capability to automatically upload any additional VAST Cluster log files that have been manually collected per VAST Support direction. To do so:

    1. Under the path /vast/bundles, create a directory named extra_auto_upload. This is the directory from which to upload the manually collected log files.

    2. Put the log files into the newly created directory.

    3. Complete the procedure to create a support bundle in VAST Web UI.

      The manually collected log files will be added to the support bundle tar.gz file and uploaded to VAST Support server.

      When upload is complete, a new directory is created that contains the uploaded log files: /vast/bundles/extra_auto_upload.completed.

  • ORION-149321: The option to save an aggregated call home bundle is now deprecated.

  • ORION-115292: Added indication of the client IP address to various trace messages to simplify troubleshooting.

Related articles
  • Enhancements in 5.2.0
    VAST Cluster > Version 5.2 > VAST Cluster 5.2 Release Notes > VAST Cluster 5.2.0 Release Notes
  • Enhancements in 5.3.0
    VAST Cluster > Version 5.3 > Version 5.3 Release Notes > VAST Cluster 5.3.0 Release Notes
  • Enhancements in 5.2.2
    VAST Cluster > Version 5.2 > VAST Cluster 5.2 Release Notes > VAST Cluster 5.2.2 Release Notes