Veritas Access Administrator's Guide
- Section I. Introducing Veritas Access
- Section II. Configuring Veritas Access
- Adding users or roles
- Configuring the network
- Configuring authentication services
- Section III. Managing Veritas Access storage
- Configuring storage
- Configuring data integrity with I/O fencing
- Configuring ISCSI
- Veritas Access as an iSCSI target
- Configuring storage
- Section IV. Managing Veritas Access file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Veritas Access as a CIFS server
- About Active Directory (AD)
- 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
- Configuring an FTP server
- Using Veritas Access as an Object Store server
- Configuring the NFS server
- Section V. Monitoring and troubleshooting
- Section VI. Provisioning and managing Veritas Access file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VII. Configuring cloud storage
- Section VIII. Provisioning and managing Veritas Access shares
- Creating shares for applications
- Creating and maintaining NFS shares
- Creating and maintaining CIFS shares
- Using Veritas Access with OpenStack
- Integrating Veritas Access with Data Insight
- Section IX. Managing Veritas Access storage services
- Compressing files
- About compressing files
- Compression tasks
- Configuring SmartTier
- Configuring SmartIO
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Veritas Access continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Compressing files
- Section X. Reference
Adding and configuring Veritas Access to the Kerberos realm
Kerberos authentication support on Veritas Access is available only if the Key Distribution Center (KDC) server is running on a standalone computer (in a non-AD (Active Directory) environment), and there is a single KDC server. Before Veritas Access can be used as a Kerberos client, the NFS service principal of Veritas Access has to be added to the KDC server. Use the Veritas Access cluster name (either the short name or the fully qualified domain name) in small letters as the host name when creating the NFS service principal.
For example, if access_ga_01 and access_ga_02 are two nodes in the Veritas Access cluster, then access_ga (or the fully qualified domain name access_ga.example.com) should be used for adding the NFS service principal. The Domain Name System (DNS) or /etc/hosts is then set up to resolve access_ga to all the virtual IPs of the Veritas Access cluster.
To configure the KDC server
- Create the NFS service principal on the KDC server using the kadmin.local command.
addprinc -randkey nfs/access_ga
- Create a
keytab
file for the NFS service principal on KDC.ktadd -k /etc/access.keytab nfs/access_ga
- Copy the created
keytab
file (/etc/access.keytab) to the Veritas Access console node. - Use the network krb standalone set command to set the Kerberos configuration on Veritas Access.
The network krb standalone set command takes the KDC server name, Kerberos realm, and the location of the
keytab
that is located on the Veritas Access console node. This command sets up the Kerberos configuration file/etc/krb5.conf
with the KDC server name and realm on all the nodes of the Veritas Access cluster. The command then copies thekeytab
file to/etc/krb5.keytab
on all the nodes of the Veritas Access cluster.Network> krb standalone set kdc_server TESTKDC.COM /home/support/krb5.keytab
The network krb standalone set command checks for the correct domain in the /etc/idmapd.conf file. If the domain is not set, the command gives a warning message saying that the DNS domain name needs to be set.
See Configuring Veritas Access for ID mapping for NFS version 4.
- Use the network krb standalone show command to show the Kerberos configuration.
- Use the following commands to stop and restart the NFS-Ganesha service:
NFS> server stop NFS> server start
- Use the network krb standalone unset command to reset the Kerberos configuration.
After the KDC server is configured, you can export the NFS shares with Kerberos authentication options.