Please enter search query.
Search <book_title>...
Veritas Access Release Notes
Last Published:
2020-10-16
Product(s):
Access (7.4.2)
Platform: Linux
- Overview of Veritas Access
- Fixed issues
- 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
- General issues
- GUI issues
- Installation and configuration issues
- Internationalization (I18N) issues
- Networking issues
- NFS issues
- ObjectAccess issues
- OpenDedup issues
- OpenStack issues
- Replication issues
- SDS known issues
- SmartIO issues
- Storage issues
- System issues
- Target issues
- Upgrade issues
- Veritas Data Deduplication issues
- Veritas Access known issues
- Getting help
The disk group import operation fails and all the services go into failed state when fencing is enabled
If the disks are not SCSI-3 compliant, the SCSI-3 persistent reservation inquiries have to be turned off from the Volume Manager side. Else, all the services go into faulted state when you try to enable fencing,
Workaround:
You can enable fencing with non-SCSI3 disks by following any one of the following methods.
To enable fencing with non-SCSI3 disks using the cluster> reboot all command
- Install Veritas Access without enabling fencing.
- Execute the vxdctl scsi3_pr off on all the nodes.
- From the Veritas Access command-line interface, execute the Cluster> reboot all.
- After the system restart, execute the Storage> fencing on majority from the Veritas Access command-line interface.
- Create the pool and the file system.
To enable fencing with non-SCSI3 disks without a restart
- Stop the cluster services.
# hastop -all
- After all the services go down, turn off the SCSI3 persistent reservations on all the nodes in the cluster.
# vxdctl scsi3pr off
- Get the process ID of vxconfigd and kill the vxconfigd process on all the nodes of the cluster.
- Restart vxconfigd on all the nodes of the cluster.
# /sbin/vxconfigd -k -x syslog
- Start all the nodes of the cluster.
# vxclustadm -m vcs startnode
Wait for the disk group to get imported.
- Start the HA service on all the nodes of the cluster.
#hastart
Now, you can enable fencing.