6.1.4 HP IBRIX X9000 Storage Release Notes

components to toggle from Up, to Stale, and back to Up. Common causes of failures in the
monitoring system include:
◦ Reboot of a file-serving node
◦ Network connectivity issues between the management console and a file serving node
◦ Resource exhaustion on a file serving node (CPU, RAM, I/O or network bandwidth)
While network connectivity and resource exhaustion issues should be investigated, they can occur
normally due to heavy workloads. In these cases, you can reduce the frequency at which
vendorstorage components are monitored by using the following command:
ibrix_fm_tune -S -o vendorStorageHardwareStaleInterval=1800
The default value of this command is 900; the value is in seconds. A higher value reduces the
probability of all components toggling from Up to Stale and back to Up because of the conditions
listed above, but will increase the time before an actual component failure is reported.
SNMP
• When the IBRIX SNMP agent is configured, do not restart snmpd. If the snmpd restart command
is run on the active node, you will need to take one of these steps:
◦ If Phone Home was configured, reconfigure it.
◦ If Phone Home was not configured, reconfigure the IBRIX SNMP agent.
HP Insight Remote Support
• After HP Insight Remote Support is configured, do not restart snmpd. See “SNMP” (page 17) for
more information.
• In certain cases, large number of error messages such as the following appear in /var/log/
hp-snmp-agents/cma.log:
“Feb 08 13:05:54 x946s1 cmahostd[25579]: cmahostd: Can't update OS
filesys object: /ifs1 (PEER3023)”
This error message occurs because the file system exceeds <n> TB. (This situation will be corrected
in a future release.) To disable logging, edit the script /opt/hp/hp-snmp-agents/server/
etc/cmahostd and remove the option -l <logname>. Then restart the agents using service
hp-snmp-agents restart.
If you want to keep logging enabled, be aware that the log messages occur frequently, and you
will need to monitor and clean up the log file regularly to avoid filling the file system.
• If Fully Qualified Domain Name (FQDN) resolution is not configured properly for the hosts, the
following error appears when hpsmhd is restarted:
Could not reliably determine the server's fully qualified domain name,
using <ip> for ServerName
To configure FQDN resolution, use either the /etc/hosts file or the Domain Name Service.
• 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 restart the SNMP service:
Workarounds 17