Veritas Access Appliance 8.3 Administrator's Guide
- Section I. Introducing Access Appliance
- Section II. Configuring Access Appliance
- Managing users
- Managing licenses
- 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
- Using Access Appliance as an Object Store server
- Configuring the S3 server using GUI
- Configuring the NFS server
- Section V. Managing Access Appliance security
- Managing security
- Setting up FIPS mode
- Configuring STIG
- Setting the banner
- Setting the password policy
- Immutability in Access Appliance
- Deploying certificates on Access Appliance
- Single Sign-On (SSO)
- Configuring multifactor authentication
- Section VI. Monitoring and troubleshooting
- Monitoring the appliance
- Configuring event notifications and audit logs
- About alert management
- Appliance log files
- 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 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 continuous replication
- Section X. Reference
Adding an SPN entry on the Windows client
You must configure a service principal name (SPN) in Windows to access a CIFS network share.
The SPN is a unique identifier of a service instance. Access Appliance uses Kerberos authentication to associate the Access virtual IP and match a fully qualified domain name to a service instance, such as CIFS.
To configure an SPN, you must have mappings of the virtual IP/FQDNs on the Access Appliance cluster. Each virtual IP must have a fully qualified domain name configured with DNS.
To configure an SPN entry
- Run the ip addr show to verify the mappings.
network> ip addr show
IP Netmask/Prefix Device Node Type Status FQDN -- ------------- ----- ---- ---- ------ ---- 192.168.10.130 255.255.255.0 eth4 va830a-01 Physical 192.168.10.132 255.255.255.0 eth5 va830a-01 Physical 192.168.10.120 255.255.255.0 eth1 va830a-01 Physical 192.168.10.131 255.255.255.0 eth4 va830a-02 Physical 192.168.10.133 255.255.255.0 eth5 va830a-02 Physical 192.168.10.121 255.255.255.0 eth1 va830a-02 Physical 192.168.10.124 255.255.255.0 eth1 va830a-02 Virtual ONLINE (Con IP) 192.168.10.140 255.255.255.0 eth4 va830a-01 Virtual ONLINE (Dedupe IP) 192.168.10.141 255.255.255.0 eth4 va830a-02 Virtual ONLINE (Dedupe IP) 192.168.10.142 255.255.255.0 eth5 va830a-02 Virtual ONLINE (CIFS IP) 192.168.10.143 255.255.255.0 eth5 va830a-01 Virtual ONLINE (CIFS IP) 192.168.10.144 255.255.255.0 eth4 va830a-01 Virtual ONLINE (Dedupe IP)
- Each IP that shows Virtual in the Type column should have a relevant DNS entry configured. The FQDNs field may be blank from Access, but each one of the virtual IPs should be resolvable via DNS or the nslookup command.
nslookup IP
- Add a CIFS SPN for each virtual IP that may be used to host a CIFS share. Attempting to connect to the CIFS share without a SPN defined results in a failed connection to the share.
In a DNS-enabled environment, the SPN must be set on the AD server (domain controller).
In a non-DNS enabled environment, each Windows client that is accessing the shares must define a local hosts entry for the FQDN and set a SPN entry per client.
You can add an SPN using the following command:
Windows CMD> setspn -T <Domain Workgroup> -s cifs/ <Fully Qualified Domain Name> <Access virtual clustername>
where:
You can find the workgroup name using the net config workstation command on the Windows client/server.
Run the network ad show command. In the output of the command, the value in the netbios name filed is the Access virtual cluster name.
- You can determine which IP/FQDN is being used for a CIFS share by listing the share details using the cifs share show and cifs share show <sharename> commands.
- You must define the SPN so that the Windows client can access the share.
setspn -T VTAS -s cifs/FQDN virtual cluster name
- Aliases can be configured in DNS, but an additional SPN must be defined to connect to a share via that alias.
C:\Users\Administrator> ping FQDN -n 1
C:\Users\Administrator> ping DNS alias -n 1
- List the currently defined SPNs.
C:\Users\Administrator> setspn -l DNS alias
- Add the alias as SPN.
C:\Users\Administrator>setspn -T VTAS -s cifs/DNS alias netbios name
- Map the share.
C:\Users\Administrator>net use * "\\aDNS alias\<sharename>"
Note:
Windows may cache credentials in open Windows Explorer or CMD windows. Ensure that you close all Explorer/cmd windows if the credentials are being accepted or rejected in an inconsistent manner.