Veritas Access Release Notes
- Overview of Veritas Access
- Software limitations
- Flexible Storage Sharing limitations
- Limitations related to installation and upgrade
- Limitation related to replication
- Known issues
- Veritas Access known issues
- Admin issues
- Backup issues
- CIFS issues
- Deduplication issues
- FTP issues
- GUI issues
- Installation and configuration issues
- Internationalization (I18N) issues
- Manual page issues
- Networking issues
- NFS issues
- ObjectAccess issues
- OpenDedup issues
- OpenStack issues
- Replication issues
- SDS known issues
- SmartIO issues
- Storage issues
- System issues
- Target issues
- Veritas Access known issues
- Getting help
When CIFS server is configured with security as "ads" and the AD server is configured with IPv6, CIFS shares can be accessed only using virtual IPs hosted on the console node and you cannot use the virtual IPs from the non-console node to mount CIFS shares
When the AD server is configured with an IPv6 address, the CIFS server has this limitation. You cannot use any IPs from a non-console node to mount the CIFS shares, in both CTDB as well as the normal mode of CIFS server. If the master (console) node fails over to some other node, you have to remount using the virtual IPs hosted on the new node. For segregated shares, you are advised to use the virtual IPs from master node only. Segregated shares that are created using virtual IPs from the non-console node are not mountable.
Workaround:
There is no workaround for this issue.
You can use the Network> ip addr online command to shift the virtual IPs to the master node, so that they can be used to mount the CIFS shares. AD servers that are configured over IPv4 continue to work as before.