HP StoreAll OS 6.5.1 Upgrade Guide

3 Troubleshooting upgrade issues
If the upgrade does not complete successfully, check the items described in this chapter. For
additional assistance, contact HP Support.
Segment evacuation task might fail after an upgrade
After upgrading the StoreAll operating system, the segment evacuation task might fail with the
message Completed with error. It could occur in a rare situation when the file system only
has two segments and both the source and destination segments contain the file and its replica.
To resolve this issue, add another segment and restart the evacuation process.
Node is not registered with the cluster network
Nodes hosting the agile Fusion Manager must be registered with the cluster network. If the
ibrix_fm command reports that the IP address for a node is on the user network, you will need
to reassign the IP address to the cluster network. For example, the following commands report that
node ib51-101, which is hosting the active Fusion Manager, has an IP address on the user
network (192.168.51.101) instead of the cluster network.
[root@ib51-101 ibrix]# ibrix_fm -i
FusionServer: ib51-101 (active, quorum is running)
==================================================
[root@ib51-101 ibrix]# ibrix_fm -l
NAME IP ADDRESS
-------- ----------
ib51-101 192.168.51.101
ib51-102 10.10.51.102
1. If the node is hosting the active Fusion Manager, as in this example, stop the Fusion Manager
on that node:
[root@ib51-101 ibrix]# /etc/init.d/ibrix_fusionmanager stop
Stopping Fusion Manager Daemon [ OK ]
[root@ib51-101 ibrix]#
2. On the node now hosting the active Fusion Manager (ib51-102 in the example), unregister
node ib51-101:
[root@ib51-102 ~]# ibrix_fm -u ib51-101
Command succeeded!
3. On the node hosting the active Fusion Manager, register node ib51-101 and assign the
correct IP address:
[root@ib51-102 ~]# ibrix_fm -R ib51-101 -I 10.10.51.101
Command succeeded!
NOTE: When registering a Fusion Manager, be sure the hostname specified with -R matches
the hostname of the server.
The ibrix_fm commands now show that node ib51-101 has the correct IP address and node
ib51-102 is hosting the active Fusion Manager.
[root@ib51-102 ~]# ibrix_fm -f
NAME IP ADDRESS
-------- ----------
ib51-101 10.10.51.101
ib51-102 10.10.51.102
[root@ib51-102 ~]# ibrix_fm -i
FusionServer: ib51-102 (active, quorum is running)
==================================================
44 Troubleshooting upgrade issues