HP StoreAll OS 6.5.1 Release Notes

1. Enter the hpsp_couplet_info -i command to get a list of UUID for attached MSA
enclosures. Each enclosure is on a separate line, as shown in the following example of the
command and its output:
[root@ib25-02s1 security]# hpsp_couplet_info -i
500c0ff1390c0000
2. Install the credentials for a single MSA by running the following four commands once for
each MSA that the hpsp_couplet_info command lists in step 1. Replace
<MSA_SAS_BASE_ADDRESS> with one of the UUIDs as provided by the output of the
hpsp_couplet_info command.
hpsp_credmgmt --update-cred -s
couplet:couplet/array/<MSA_SAS_BASE_ADDRESS>/mgmtport_a/rw
--cred-type upwpair --cred-username manage --cred-password '!manage'
hpsp_credmgmt --update-cred -s
couplet:couplet/array/<MSA_SAS_BASE_ADDRESS>/mgmtport_a/ro
--cred-type upwpair --cred-username monitor --cred-password
'!monitor'
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
• If Fusion Manager (FM) is taking a long time to start and the logging for FM is showing APPARENT
DEADLOCK messages, purge the event database.
To purge the event database:
1. Enter the following CLI command:
ibrix_event -p [-o DAYS_COUNT]
If you want to change the number of days the event database is purged, include the -o
DAYS_COUNT option when you enter the command.
Events are removed starting with the oldest events. The default is to remove the oldest seven
days of messages. Purge the event database periodically to prevent it from becoming too
large.
2. After the events are purged, create a new FM Store archive by entering the following
command:
ibrix_fm -B
3. Wait for a few seconds to let the Store archive propagate through the cluster and then restart
the active FM.
Workarounds 19