6.1.4 HP IBRIX X9000 Storage Release Notes

service snmpd restart
• On X9320/X9720 systems, the virtual SAS manager and VC connect manager must be configured
manually for HP Support.
• On HP SIM 7.1, X9320/X9300 nodes are discovered as “HP X9320 NetStor FSN” if MSA
storage is registered on the cluster nodes. This does not affect sending alerts to HP Support.
Upgrades
• If clients previously mapped a CIFS share using the hostname/FQDN, they will be prompted
continuously to enter their credentials when attempting to access the CIFS share after the upgrade.
(The share can be accessed successfully using the IP address.) To workaround this situation, disjoin
and then rejoin all file serving nodes to the Active Directory domain. This can be done using the
GUI or the ibrix_auth command.
X9000 Windows clients
• Reading of snaps as memory mapped files is not supported. Undesired results can occur if a snap
file is used as memory mapped file while the current version of the file is being modified by a
different instance.
General
• The ibrix_pv -a -o mpath command does not recognize a multipath device. The command
works properly when an argument is added to ignore the standard SCSI devices. Execute the
command as follows, specifying the path to your device.
ibrix_pv -a -o accept:/dev/mapper/mpath10,~standard
• HP-OpenIPMI does not work with the HP-Health service. For example, Proliant health check tools
such as SMH and SIM and hpasmcli commands such as SHOW POWERSUPPLY do not report
errors. This situation occurs because X9000 Software requires standard RHEL IPMI. Remove the
HP-OpenIPMI RPM (execute rpm -e HP-OpenIPMI), and then start the standard RHEL IPMI
(execute /etc/init.d/ipmi start). The standard RHEL IMPI will now start automatically
when the server is booted.
• During server migration or failover, certain cluster events will be reported as alerts. These events
are expected and normal, and are reported temporarily as a server is failing over to another
server.
• Node failover does not occur when a node has a complete loss of power (for example, removing
power cords or pulling a blade from a chassis). Do not test high availability in this manner.
• The log files for user-initiated tasks (such as running ibrix_fsck and migrating or rebalancing
segments) are not rotated automatically. To control the space used by these log files, you will
need to maintain them manually. The log files are located in /usr/local/ibrix/log.
• NFS locks may return an error code (37) after an unlock operation even though the lock was
correctly released. If other results are normal, you can ignore this error code.
• On X9730 systems, the iLO can fail to power up a server when directed to do so from the iLO
web page or the iLO's Integrated Remote Console. To correct this condition, reset the iLO processor.
This can be done from the iLO web UI; select Reset on the Diagnostics page.
• After a server is rebooted following a QR install and before the server is configured, an error
message reports that the SRVSVCD service failed to load. The failure occurs because the service
requires that the network subsystem be configured. The error message can be safely ignored.
After the network is configured, restart the CIFS service.
18 Workarounds