Veritas Flex Appliance Getting Started and Administration Guide
- Product overview
- Release notes
- Getting started
- Managing network settings for instances
- Managing users
- Managing Flex Appliance Console users and tenants
- Managing multifactor authentication
- Using Flex Appliance Console accounts for API automation
- Using Flex Appliance
- Managing the repository
- Managing application instances from Flex Appliance
- Upgrading application instances
- About Flex Appliance updates
- Remote replication
- Managing remote replication
- Appliance security
- Monitoring the appliance
- Configuring alerts
- Viewing the hardware status
- Reconfiguring the appliance
- Troubleshooting guidelines
Flex Appliance 6.0 new features, enhancements, and changes
The following list describes the new features, enhancements, and changes in the Flex Appliance 6.0 release:
You can now view performance metrics of your application instances from the Home page on the Flex Appliance Console.
You can now change the BIOS password on Veritas 5260 and 5360 appliances. If you don't change the password, the default password is the node's serial number. See Changing the BIOS password.
As part of this change, a new BIOS administrator extended user role is available. See Managing Flex Appliance Console users and tenants.
When you perform a firmware update, you are now prompted for the BIOS password on Veritas 5260 and 5360 appliances if you have set a non-default password.
You can now see the revision number of uploaded applications on the Repository page for NetBackup 10.3 revision 67 and later. Earlier versions do not show the revision numbers.
All outbound connections from the appliance except for SNMP connections now support TLS anonymous authentication version 1.3. Version 1.3 is used by default, while version 1.2 is available for backwards compatibility.
The Fibre Channel interfaces page on the Flex Appliance Console has been enhanced to more accurately show the status of the Fibre Channel ports. The Used for column now indicates whether assigned ports are used as targets or initiators. For unassigned ports, the Used for column is blank.
Additionally, the show hardware-health node component=FibreChannel command in the Flex Appliance Shell shows the Mode of all ports as Initiator, Target because it shows the hardware capability of the ports, not how they are currently used.
The following APIs are no longer available:
DELETE /v1/users/local/{username}
Use
DELETE /v2/users
instead.POST /v1/users/local/{username}
Use
POST /v2/users
instead.GET /v1/network/vlans
Use
GET /v1/networks
instead.POST /v1/network/vlans/{vlan-tag}
Use
PUT /v1/networks/{interface}
instead.DELETE /v1/network/vlans/{vlan-tag}
Use
DELETE /v1/networks/{interface}
instead.GET /v1/instances
andGET /v2/instances
Use
GET /v3/instances
instead.GET /v1/instances/{instance-id}
Use
GET /v3/instances/{instance-id}
instead.PUT /v1/users/active-directory
Use
PUT /v1/user-domains
instead.GET /v1/users/active-directory
Use
GET /v1/user-domains
instead.POST /v1/users/active-directory
Use
POST /v1/user-domains
instead.DELETE /v1/network/bonds/{bond-name}
Use
DELETE /v1/networks/{interface}
instead.POST /v1/network/bonds/{bond-name}
Use
PUT /v1/networks/{interface}
instead.DELETE /v1/users/password
Use
DELETE /v2/users/password
instead.PUT /v1/network/{interface}/mtu
Use
PUT /v1/networks/{interface}/mtu
instead.GET /v1/network/interfaces
Use
Get /v1/networks
instead.
Check Veritas SORT for more information on the APIs.