Veritas Access Appliance Administrator's Guide
- Section I. Introducing Access Appliance
- Section II. Configuring Access Appliance
- Managing users
- Configuring the network
- Configuring authentication services
- Configuring user authentication using digital certificates or smart cards
- Section III. Managing Access Appliance storage
- Configuring storage
- Managing disks
- Access Appliance as an iSCSI target
- Configuring storage
- Section IV. Managing Access Appliance file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Access Appliance as a CIFS server
- About configuring CIFS for Active Directory (AD) domain mode
- About setting trusted domains
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- About managing local users and groups
- Using Access Appliance as an Object Store server
- Configuring the S3 server using GUI
- Configuring the NFS server
- Section V. Managing Access Appliance security
- Section VI. Monitoring and troubleshooting
- Configuring event notifications and audit logs
- About alert management
- Appliance log files
- Configuring event notifications and audit logs
- Section VII. Provisioning and managing Access Appliance file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- About managing application I/O workloads using maximum IOPS settings
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VIII. Provisioning and managing Access Appliance shares
- Creating shares for applications
- Creating and maintaining NFS shares
- About the NFS shares
- Creating and maintaining CIFS shares
- About the CIFS shares
- About managing CIFS shares for Enterprise Vault
- Integrating Access Appliance with Data Insight
- Section IX. Managing Access Appliance storage services
- Configuring episodic replication
- Configuring an episodic replication job using the GUI
- Episodic replication job failover and failback
- Configuring continuous replication
- How Access Appliance continuous replication works
- Configuring a continuous replication job using the GUI
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Configuring episodic replication
- Section X. Reference
Managing the FIPS mode using the command-line interface
You can view the FIPS status and enable and disable the FIPS mode from the Access command-line interface.
You can view the VxOS FIPS status for a cluster node and the FIPS status of NetBackup MSDP for each Veritas Data Deduplication server that is configured for the cluster.
To view the FIPS mode for VxOS and MSDP:
- Log in to the Access command-line interface as an administrator by opening an SSH session to the console IP.
- In the Access command-line interface, run the following command:
system security fips show
You can enable the FIPS mode for NetBackup MSDP for each Veritas Data Deduplication server that is configured for the cluster. A maximum of two Veritas Data Deduplication servers can be configured. When you enable FIPS for MSDP, all the backup and restore jobs that are in progress are terminated. After you enable the FIPS mode, restart the NetBackup services to restart the jobs.
To enable FIPS for MSDP:
- Log in to the Access command-line interface as an administrator by opening an SSH session to the console IP.
- In the Access command-line interface, run the following command:
system security fips enable MSDP [config_name]
config_name is the name of the deduplication server and is optional if only one deduplication server is configured for the cluster. By default the parameter value is set to vxdefault.
Disabling FIPS for MSDP:
- Log on to the Access command-line interface as an administrator by opening an SSH session to the console IP.
- In the Access command-line interface, run the following command:
system security fips disable MSDP [config_name]
config_name is the name of the deduplication server and is optional if only one deduplication server is configured for the cluster. By default the parameter value is set to vxdefault.