Please enter search query.
Search <book_title>...
Veritas Access Release Notes
Last Published:
2018-08-03
Product(s):
Appliances (7.3.2)
Platform: 3340
- Overview of Veritas Access
- Software limitations
- Limitations related to installation and upgrade
- Veritas Access language support
- File system limitation
- Limitation related to replication
- Known issues
- Veritas Access known issues
- Backup issues
- CIFS issues
- Enterprise Vault Attach known issues
- GUI issues
- Installation and configuration issues
- Networking issues
- NFS issues
- ObjectAccess issues
- OpenDedup issues
- OpenStack issues
- Replication issues
- SmartIO issues
- Storage issues
- System issues
- Target issues
- Access Appliance issues
- Access Appliance operational notes
- Veritas Access known issues
- Getting help
If a user is added on the target side, the initiator cannot see the LUNs
While discovering targets, the Veritas Access initiator does not ask for credentials, and takes the default credentials. Hence, the initiator is unable to log into the targets. As a result, the target status on the initiator becomes OFFLINE and LUNs are not visible to the initiator.
Workaround:
Log in from outside of the CLISH using the following iscsiadm commands. Execute this command on both nodes so that the disks (LUNS) become FSS disks.
# iscsiadm -m node -T <target-name> -p <portal-ip> --op=update --name node.session.auth.authmethod --value=CHAP iscsiadm -m node -T <target-name> -p <portal-ip> --op=update --name node.session.auth.username --value=username iscsiadm -m node -T <target-name> -p <portal-ip> --op=update --name node.session.auth.password --value=password