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 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
- Episodic replication job failover and failback
- Configuring continuous replication
- How Access Appliance continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Configuring episodic replication
- Section X. Reference
Adding and configuring Access Appliance to the Kerberos realm
Kerberos authentication support on Access Appliance 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 Access Appliance can be used as a Kerberos client, the NFS service principal of Access Appliance has to be added to the KDC server. Use the Access Appliance 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 Access Appliance 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 Access Appliance 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 Access Appliance console node. - Use the network krb standalone set command to set the Kerberos configuration on Access Appliance.
The network krb standalone set command takes the KDC server name, Kerberos realm, and the location of the
keytab
that is located on the Access Appliance 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 Access Appliance cluster. The command then copies thekeytab
file to/etc/krb5.keytab
on all the nodes of the Access Appliance 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 Access Appliance for ID mapping for NFS version 4.
- Use the network krb standalone show command to show the Kerberos configuration.
- 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.