Providing Access to VMS from the Data Network

  • Published on Feb 18, 2026
  • 2 minute(s) read
Prev Next

Overview

By default, the VAST Management Service (VMS) is accessed through a dedicated management subnet. In some environments, you may want to provide access to VMS on the data network as well.

VMS supports this requirement by allowing the configuration of an additional management virtual IP (VIP) on the data network. This data network VMS VIP listens for VMS traffic and operates independently of and in addition to the standard management VIP.

Key Characteristics and Limitations

  • Configuration is performed exclusively via the VAST CLI.

  • The current configuration can be viewed via the VAST CLI.

  • One data network management VIP can be configured at a time. The VIP may be configured with IPv4 or IPv6, but not both simultaneously.

  • The VIP is bound to the data interface of the same CNode as the standard management VIP.

  • The configuration can be removed.

High Availability and Failover Behavior

The data network management VIP is integrated with VAST high-availability mechanisms:

  • Persistence. The VIP persists across reboots. After a reboot, the VIP may move to a different CNode if required.

  • Failover. If the hosting CNode fails, the VIP automatically fails over to another active CNode, as well as the standard management VIP. The VIP can only reside on the same CNode as the standard management VIP.

  • Cluster changes. Newly added CNodes are eligible to host the VIP. If a CNode is deactivated or replaced and it was hosting the VIP, the VIP fails over automatically.

Configuring a Data Network Management VIP

  • To configure a data network management VIP with IPv4, use the vms modify command with the following options:

    • --mgmt-data-vip to specify the IPv4 address.

    • --mgmt-data-netmask to specify the netmask.

    • --mgmt-data-interface to specify which management interface on all CNodes on which to configure the IP.

    • --mgmt-data-vip-gateway to specify a gateway (optional).

    • --mgmt-data-vip-vlan to tag the interface with a VLAN (optional).

    For example:

    vcli: admin> vms modify --mgmt-data-interface bond0 --mgmt-data-vip 1.1.1.1 --mgmt-data-netmask 255.255.0.0

  • To configure a data network management VIP with IPv6, use the vms modify command with:

    • --mgmt-data-vip-ipv6 to specify the IPv6 address.

    • --mgmt-data-vip-prefix-ipv6 to specify the prefix for the IPv6 address.

    • --mgmt-data-interface to specify which management interface on all CNodes on which to configure the IP.

    • --mgmt-data-vip-gateway-ipv6 to specify a gateway (optional).

    • --mgmt-data-vip-vlan to tag the interface with a VLAN (optional).

    For example:

    vcli: admin> vms modify --mgmt-data-interface bond0 --mgmt-data-vip-ipv6 2001:db8::10 --mgmt-data-vip-prefix-ipv6 64 --mgmt-data-vip-gateway-ipv6 2001:db8::1

Viewing the Current Configuration

Use the  vms show or  vms list command without any parameters to see the current configuration of the data network management VIP.

Deleting a Data Network Management VIP

To delete a data network management VIP, use the vms modify command with the --delete-mgmt-data-vip option:

 vcli: admin> vms modify --delete-mgmt-data-vip

Related articles
  • Providing Access to VMS from the Data Network
    VAST Cluster > Version 5.3 > VAST Cluster 5.3 Administrator's Guide > Administrating VMS > VMS Settings and Preferences
  • vms modify
    VAST Cluster > Version 5.4 > VAST Cluster 5.4 CLI Command Reference > vms commands
  • vms modify
    VAST Cluster > Version 5.3 > VAST Cluster 5.3 CLI Command Reference > vms commands