5.5.4 HP X9000 Series Release Notes (TA768-96054, September 2011)

Management console
If the management console service is stopped on the active management console and, within a
minute, the passive management console experiences a shutdown or reboot, the passive
management console will become active when the node is restarted. When the fusionmanager
is started on the formerly active management console (or that node is rebooted), that management
console will also be in active mode. Although both management consoles are active, only one of
these consoles will control the cluster virtual interface.
To recover from this scenario, take the following steps:
1. Determine which management console is running the cluster virtual interface:
ifconfig -a
In the output, check for a configured bond0:1 virtual interface.
2. Place the management console that is not running the cluster interface into maintenance
mode, and then place it into passive mode:
ibrix_fm -m maintenance
ibrix_fm -m passive
If the recovery is not successful, contact HP Support.
If your cluster uses a dedicated management console, and you want to apply quotas to users and
groups from your Active Directory (AD) domain, take the following steps before assigning the
quotas:
1. Install the likewise-cifs.x86_64.rpm. (This RPM is in the /usr/local/ibrix/
installation/ibrix/distrib/engine/RHEL5/x86-64 directory in the X9000
Software distribution.)
rpm i likewise-cifs.x86_64-X9000_v5.5.rpm
2. Join the management console to the AD domain manually:
/opt/likewise/bin/domainjoin-cli join <domain name> <domain account
to join domain>
3. Stop Likewise:
/opt/likewise/bin/lwsm stop lwreg && /etc/init.d/lwsmd stop
4. Start Likewise:
/etc/init.d/lwsmd start && /opt/likewise/bin/lwsm start srvsvc
5. Restart the management console:
/etc/init.d/ibrix_fusionmanager restart
The management console will now recognize the Active Directory users and groups, and you can
assign quotas to them.
For configurations with two management consoles, if the node hosting the active management
console goes down, it is important to reboot it as soon as possible. The management console on
that node can then assume a passive role and receive updates from the new active management
console. If the node remains down and the node hosting the active management console also
goes down, the cluster configuration data may become inconsistent, depending on the order in
which the nodes are rebooted.
When the active management console is moved to maintenance mode, a passive management
console will transition to active mode. Be sure that this transition is complete before you move the
previously active management console from maintenance mode to passive mode. (Use the
nl
ibrix_fm -i command to check the mode of each management console.) If the passive
management console has not yet assumed active mode, the management console being moved
from maintenance to passive mode will become active again.
Fixes 11