6.3.3 HP StoreAll OS Release Notes (AW549-96082, January 2014)

hpsp_credmgmt --update-cred -s
couplet:couplet/array/<MSA_SAS_BASE_ADDRESS>/mgmtport_b/rw
--cred-type upwpair --cred-username manage --cred-password '!manage'
hpsp_credmgmt --update-cred -s
couplet:couplet/array/<MSA_SAS_BASE_ADDRESS>/mgmtport_b/ro
--cred-type upwpair --cred-username monitor --cred-password
'!monitor'
3. To verify your installation of the credentials, list the credentials by entering the following
command:
hpsp_credmgmt --get-cred -s couplet:couplet/* --output-sl
The command displays the credentials for your system. Your output would differ from the
following example to reflect your system configuration:
10.125.2.221|monitor|!monitor|couplet:couplet/array/500c0ff1390c0000/mgmtport_b/ro
10.125.2.221|manage|!manage|couplet:couplet/array/500c0ff1390c0000/mgmtport_b/rw
10.125.2.220|monitor|!monitor|couplet:couplet/array/500c0ff1390c0000/mgmtport_a/ro
10.125.2.220|manage|!manage|couplet:couplet/array/500c0ff1390c0000/mgmtport_a/rw
General
• A crash might occur if there is a change in ownership of the file while a quota is being enabled.
There are plans to provide a fix in a future release.
• After the files are archived, evacuation might fail and you might see an RO lock error message
when you attempt to access the files from the second node.
To resolve this issue:
1. Unload the CommVault driver from all nodes on hosts that control segments for this file system.
2. Run segment evacuation. See the Administrator Guide for your platform for additional
information.
3. Reload the CommVault driver. Refer to the CommVault documentation for additional
information.
• Any object store user can get a container listing for any object store user on an object mode REST
API share. Permission changes are not allowed on the account level directory.
To prevent a user other than the account owner from seeing any containers, change the directory
permission (chmod) of the account directory to 700 after the directory has been created. The
account directory is created after the account owning user creates their first container. This
permission change also prevents other users from reading or writing objects in any containers,
even if you grant such permission to the containers via the API.
For example, after the first container creation for user2 whose UID is 3002, if the object store
share’s directory path is /objModeFS/objStore, the /objModeFS/objStore/3002 account
directory will be created with 777 permission, giving full read, write, and execute permission to
all users. Changing permission to 700 removes all permissions for all other users, for both container
listings and object access within containers.
To grant other users in the same group read and/or write permission to objects in any containers,
turn on the group execute bit, for the account directory. Then, change the permissions of the
containers to which you wish to grant access via the API’s Set Container Permission request. If
you also want those group users to be able to list containers, then also turn on the group read
bit. Similarly for other users outside the group, turn on the world execute bit to allow object access,
and turn on the world read bit to enable container listings.
• You might not be able to mount a file system after an unmount if you:
22 Workarounds