6.3.3 HP StoreAll OS Release Notes (AW549-96082, January 2014)

• If SNMP is logging excessively, add the following command to the file /etc/sysconfig/
snmpd.options to stop the logging:
OPTIONS="-LS 0-4 d -Lf /dev/null -p /var/run/snmpd.pid -a"
To enable the default SNMP logging, add a pound sign (#) to the following command in the file
/etc/sysconfig/snmpd.options and save the file:
# OPTIONS="-LS 0-4 d -Lf /dev/null -p /var/run/snmpd.pid -a"
Then do the following:
◦ If Phone Home was configured, reconfigure it.
◦ If Phone Home was not configured, and the StoreAll SNMP agent is configured, reconfigure
the StoreAll SNMP agent.
◦ If both Phone Home and the StoreAll SNMP agent are not configured, restart the snmpd
service:
service snmpd restart
service snmpd restart
• On 9320/X9720 systems, the virtual SAS manager and VC connect manager must be configured
manually for HP Support.
• On HP SIM 7.1, 9320/9300 nodes are discovered as “HP 9320 NetStor FSN” if MSA storage
is registered on the cluster nodes. This does not affect sending alerts to HP Support.
ibdircheck
• The output from the ibdircheck command might show incorrect statistics counters. For some
conditions the number of errors does not match the number of corrections. There are plans to fix
this issue in a subsequent patch. If you encounter this issue, contact HP support for analysis of the
ibdircheck logs to determine if you have a benign situation or if you have any file system errors
truly left uncorrected.
• HP recommends that you do not run rebalancer, segment evacuation and/or data tiering tasks
with ibdircheck.
ibrix_collect
• If collection does not start after a node recovers from a system crash, check the /var/crash/
<timestamp> directory to determine whether the vmcore is complete. The command
ibrix_collect does not process incomplete vmcores. Also check /usr/local/ibrix/log/
ibrixcollect/kdumpcollect.log for any errors.
• If the status of a collection is Partially_collected, typically the management console service
was not running or there was not enough space available in the /local disk partition on the
node where the collection failed. To determine the exact cause of a failure during collection, see
the following logs:
◦ /usr/local/ibrix/log/fusionserver.log
◦ /usr/local/ibrix/log/ibrixcollect/ibrixcollect.py.log
• Email notifications do not include information about failed attempts to collect the cluster
configuration.
• In some situations, ibrix_collect successfully collects information after a system crash but
fails to report a completed collection. The information is available in the /local/ibrixcollect/
archive directory on one of the file serving nodes.
24 Workarounds