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
Configuring entries for Veritas Access DNS for authenticating to Active Directory (AD)
Name resolution must be configured correctly on Veritas Access. Domain Name System (DNS) is usually used for name resolution.
To configure entries for Veritas Access DNS for authenticating to Active Directory
- Create an entry for the Veritas Access cluster name.
The cluster name is chosen at the time of installation, and it cannot be reset afterwards. It is also the NetBios name of the cluster, hence it must resolve to an IP address.
- Configure the Veritas Access cluster name in DNS so that queries to it return the Virtual IP Addresses (VIPs) associated with the Veritas Access cluster in a round-robin fashion.
This is done by creating separate A records that map the cluster name to each VIP. So, if there are four VIPs associated with the Veritas Access cluster (not including special VIPs for backup, replication for Veritas Access, and so on), then there must be four A records mapping the cluster name to the four VIPs.
- Verify that the DNS server has correct entries for Veritas Access by querying from a client:
# nslookup cluster name
After configuring the DNS server correctly, Veritas Access must be configured as a DNS client.
This is done during installation, but may be modified by using the following commands:
Network> dns set domainname domain_name
Network> dns set nameservers IP address
Network> dns enable
- Verify that DNS client parameters are set correctly by entering the following command:
Network> dns show
- Ensure host resolution is querying DNS by checking nsswitch:
Network> nsswitch show
In the above scenario, host resolution first looks at files, and then DNS.
Configuring name resolution correctly is critical in order to successfully join Veritas Access to Active Directory.