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
If duplicate PCI IDs are added for the PCI exclusion, the Cluster> add node name command fails
To add a new node that has unique PCI IDs to be excluded, you need to add these unique PCI IDs through the Veritas Access command-line interface by using the Network> pciexclusion add command. If these unique PCI IDs already exist in the PCI exclusion configuration of Veritas Access, the resulting configuration has duplicate entries. After the resulting configuration for the PCI exclusion, if you proceed with the added node, the operation fails. The Cluster> add node operation cannot handle the duplicate entries in the PCI exclusion configuration.
Workaround:
Contact Veritas Technical Support to remove the duplicated PCI IDs from the Veritas Access PCI exclusion configuration files. Then you can run the Cluster> add node command.