You can secure the network traffic between an application instance and an external host by configuring a host-to-host IPsec tunnel between them, protecting agentless backup traffic.

See Configuring IPsec for application instances.

You can monitor LLT interconnect link health on multi-node appliances. Warning and critical alerts are sent through your configured email or SNMP alerts if an interconnect link goes down, helping you detect and resolve connectivity issues before they affect cluster availability.

See LLT interconnect link monitoring and alerting.

You can monitor disk I/O for appliance LUNs and for the volumes used by your application instances from the Storage page's I/O performance tab, so you can validate performance, troubleshoot slowdowns, and confirm that workloads are meeting their SLAs.

See Monitoring I/O performance.

You can select a transmit hash policy, Layer 2 or Layer 3+4, for network bonds that use 802.3ad (LACP) mode, to improve traffic distribution across the bonded links.

See About the transmit hash policy.

You can check the hardware and services health of every node at a glance from a new Node health widget on the Home page. The widget flags stale or unreachable health data and lets you drill into a detailed report, so you can spot and investigate hardware or services issues before they affect your applications.

See Viewing appliance health from the Home page.

You can see how the storage for your application instances is allocated across the appliance LUNs from the Storage page's Storage Allocation tab. It shows the enclosures and LUNs on the appliance, how much of each LUN is allocated, and which instance volumes are on which LUN, so you can decide whether instances should share a LUN, plan capacity, and investigate storage performance problems.

See Viewing instance storage allocation across LUNs.

You can move an individual application instance volume to a different LUN, so that you can resolve contention on a shared LUN or give a growing volume a dedicated LUN.

See About moving instance volumes between LUNs.

You can lock a LUN so that no new instance storage is placed on it, which lets you reserve a LUN for a planned workload or keep an instance on a LUN of its own.

See About locking LUNs.

You can paste passwords into the password fields in the Flex Appliance Console when you add a local user, change a local user password, or create an application instance.

See Entering passwords in the Flex Appliance Console.

You can restrict a personal API token or a predefined API token to specific IP addresses and subnets, limiting exposure if a token is compromised. You can update the allowed list at any time without reissuing the token.

See Restricting API token access to specific IP addresses.

If your appliance uses an external key management service (EKMS) and its KMS client certificate expires, you can unlock the appliance by retrieving a temporary certificate bundle from a remote host with SCP, instead of typing the encryption key at the console.

See Preparing a certificate bundle for unlock recovery.

You can let users from any domain in a multi-domain Active Directory forest sign in to the Flex Appliance Console through a single remote user domain that is connected to a global catalog server. In this configuration, a user in a nested group can sign in when you import the parent group, so you do not need to import every group in a chain.

See Using a remote user domain in a multi-domain Active Directory forest.