Linux Best Management Practices for HP ProLiant Gen8 Servers and Red Hat Enterprise Linux

Technical white paper | Linux Best Management Practices: HP ProLiant Gen8 Servers and Red Hat Enterprise Linux
Figure 3: Configuring SNMP parameters to enable HP SIM 7.0 to manage an HP ProLiant Gen8 server using HP AMS
Running SNMP pass through, with OS-based SNMP agents
This configuration option provides an alternative configuration that uses the legacy agents. When configured, SNMP requests received
by the iLO 4 are “tunneled” through to the legacy SNMP service on the host. This provides equivalent access to the legacy SNMP
agents using the host NIC, and allows HP SIM to immediately associate an iLO with a server.
Running HP AMS and legacy SNMP agents
The HP Agentless Management Service can run concurrently with the OS-based management software; however, HP recommends
running only one: either HP Agentless Management Service or the OS-based management software. Running both concurrently
consumes more memory and processor cycles. Additionally, using HP Agentless Management, status agreement, and the SNMP agents
concurrently might result in duplicate alerts in HP SIM. Different alerts for similar conditions might lead to confusion. For example, the
iLO handles redundant components differently than do OS SNMP agents.
When HP SIM detects HP Agentless Management is in use, HP SIM first queries the iLO BMC to gather data. If the iLO BMC and
SNMP agents are running concurrently, and both are monitoring a particular component, HP SIM might receive duplicate trap data, a
subset of data, or a superset of data for that component. (What is considered a complete set of data by the OS agent might be a subset
of data to the iLO agent; conversely, a complete set of data for the iLO agent is a superset of the data for the OS agent.)
To eliminate duplication of monitoring and prevent over consumption of iLO devices, perform any of the following procedures:
Stop or uninstall the HP Agentless Management Service. Stopping the HP Agentless Management Service stops the service until you
reboot the server. Upon reboot, the service is re-started.
Uninstall the Agents or providers by using the appropriate software removal tool (yum, rpm, rhn).
There can also be situations where all channels used to communicate with the iLO are being used by agents, the health daemon, and
HP AMS . To eliminate this situation:
Reduce the number of channels in use by not running both hp-snmp-agents and hp-ams at the same time, without modifying
which sub-agents are configured to run when hp-snmp-agents starts. For more information, seeCustomizing which SNMP
sub-agents are startedand “Running only legacy agents not provided by HP AMS and iLO 4”.
7