Search <book_title>...

Veritas Access Release Notes

Last Published: 2018-08-03

Product(s): Appliances (7.3.2)

Platform: 3340

Access Appliance operational notes

This section contains the topics that explain important aspects of Veritas Access Appliance 7.3.2 operations that may not be documented elsewhere in the documentation.

The following list contains the notes and the known issues that apply to this Access Appliance release:

If you have opened the following shares on the appliance node, you may experience a 'time-out' or 'denied' error when mounting the NFS share on your client computer:
```
Main > Manage > Software > Share
Main > Support > Logs > Share
```
The NFS server for the Access cluster may be offline. After the Access cluster configuration is completed, the NFS server is offline by default. If you want to access the NFS shares on the appliance nodes, you must ensure that the NFS server is online from the Access shell menu.
To check NFS status and start the service, log on to the Access shell menu and run the following commands:
```
ltra> nfs server status
NFS Status on ltra_01 : OFFLINE
NFS Status on ltra_02 : OFFLINE
ltra> nfs server start
Success.
ltra> nfs server status
NFS Status on ltra_01 : ONLINE
NFS Status on ltra_02 : ONLINE
```
Storage Connection appears twice under Infrastructure > Hardware in the Access GUI. The second instance is actually the Temperature menu.
The Ethernet interface names are not automatically reverted to default value, for example, eth4, eth5, after an appliance node is removed from cluster. Instead, the Access cluster Ethernet interface names remain, for example, priveth0, pubeth1.
To refresh the Ethernet interface status, you must restart the appliance after you remove the appliance node. Then, use the Network > Show Status command to check the latest Ethernet interface status.
When an appliance node leaves the Access cluster, the logon credential remains unchanged. The logon credential does not revert to the state before the node was added to the Access cluster. This behavior is by design.
To log on the node after the node has been removed from the cluster, use the same credential as what was used when the node was in the cluster.
In the following scenarios, the Manage > Cluster > Configure command is available, but running the command results in a failure.
- While the cluster configuration process is ongoing on one node, you run the Cluster > Configure command on another un-configured node of the Access Appliance.
  In this scenario, the Cluster > Configure command fails. However, you can safely ignore this failure because the existing cluster configuration process will not be affected.
- One node in a configured Access Appliance is factory reset without resetting the shared storage (the cluster is intact), and then you run the Cluster > Configure command on the factory state node in the appliance.
  In this scenario, the Cluster > Configure command fails. However, you can safely ignore this failure because it does not affect the node that remains in the Access cluster (single-node cluster).
If SSL is enabled for S3 and then you run the Support > Test Software command, the S3 Service test always shows [WARNING]. The following warning message appears incorrectly:
- [Warning] V-409-830-5451: The S3 service is not ready. Refer to the Access Appliance documentation for how to configure the S3 service.
To work around this issue, you can temporarily disable SSL for S3, and then run the test.
After an Access Appliance is configured, and S3 is ready, if you run the Support > Test Software command on one node while a software self-test is ongoing on another node, the following occur:
- The S3 Service test results on both nodes always incorrectly show [WARNING], and a [WARNING] message as follows:
  - [Warning] V-409-830-5451: The S3 service is not ready. Refer to the Access Appliance documentation for how to configure the S3 service.
- At the same time, a 'selftest' bucket is created on the shared storage. You cannot delete the bucket from the Access GUI. The 'selftest' bucket size is 5 GB. If you have changed the default bucket size before this issue occurred, this 'selftest' bucket size defaults to that size.
This issue does not affect the S3 service working. You cannot delete the 'selftest' bucket unless you do a full factory reset and re-configure the Access Appliance.
The file system type for S3 buckets must be set to Scale-Out FS from Access GUI or largefs-simple from Access shell menu. Otherwise, the bucket pool size can only be resized to 512 TB at maximum.
- When you create file system from the Access GUI, the default type is Scale-Out FS. Make sure that you use the default type.
- When you create file system from the Access shell menu, make sure that you specify the file system type as largefs-simple.