Recovering From A Changed Storage Cluster Uuid - HP StoreAll 8800 Administrator's Manual

10. On the server running the active Fusion Manager, execute the following command:
ibrix_pv
1 1. Use the Extend Filesystem Wizard in the GUI to complete the addition of the new storage.
Navigate to the wizard by selecting Filesystems in the upper Navigator and then selecting
Summary > Extend in the lower Navigator.
12. After storage expansion is complete, you must run the following Storage Provisioning Tool
(SPT) command on one server in the couplet on which the storage was expanded:
hpsp_spt
Executing this command resolves any duplicate volume naming that may exist.

Recovering from a changed storage cluster UUID

If the storage cluster ID changes, you must fix the vendor storage registration accordingly. Complete
the following steps:
1. List the current storage cluster IDs by executing the following command:
hpsp_couplet_info -i
Command output example:
048e88c2-0000-1000-b022-533457303031
2. Identify the nodes that are attached to the vendor storage containing the previous storage
cluster UUID by executing the following command:
ibrix_vs -l -s
Command output example:
[root@ib25-12s2 ~]# ibrix_vs -l -s
SERVER_NAME
-----------
ib25-12s1
ib25-12s2
Locate the vendor storage that is associated with the applicable cluster listed in the command
output of step 1. If the vendor storage does not match the applicable cluster storage ID, then
the node is attached to vendor storage with an older, invalid storage cluster ID. In this example,
the vendor storage listed applies to the first cluster listed in the output of step 1. The last four
digits of the vendor storage (3244) do not match the last four digits of the cluster storage ID
(3031); therefore, the vendor storage needs to be re-registered.
3. Delete the vendor storage containing the previous storage cluster UUID by executing the
following command:
ibrix_vs -d -n <previous cluster UUID>
Command output example:
[root@ib25-12s2 ~]# ibrix_vs -d -n
4. Run the autoregister script on each node that was connected to the affected vendor storage:
/usr/local/ibrix/bin/autoregister_chassis_and_vs
Script output example:
Sending request to Fusion Manager to register chassis ch_8800
###
### Please run the following commands to verify Chassis registration succeeded
for host ib25-12s2
### ibrix_chassis -l
### ibrix_chassis -l -s
###
Sending request to Fusion Manager to register vendor storage
vs_04a1fc68-0000-1000-b021-533457303031
###
### Please run the following commands to verify Vendor Storage registration
succeeded for host ib25-12s2
1 14 Maintaining the system
a
fn
VENDOR_STORAGE
---------------------------------------
vs_02e2ae05-0000-1000-b000-533457303244
vs_02e2ae05-0000-1000-b000-533457303244
vs_02e2ae05-0000-1000-b000-533457303244 Command succeeded!
HARDWARE_UNIT_TYPE
------------------
8800
8800