Setting up Managed Systems in ICE-Linux without the ProLiant Service Pack

When it is running with a full complement of ProLiant Support Pack agents, the daemon, augmented

with the PSP subagents, can take more time to respond. If the reply takes too much time, the

association between the management processor and the server might be lost.

If a node is found in the manageable state, but without MAC information, it can be verified by

consulting the nodes data collection results webpage. You can correct it by:

• Ensuring the agent or agents are running and available.

• Ensuring the server is lightly loaded.

• Running the the HP SIM Options→Data Collection… task manually on the node.

Verify that the MAC address information is displayed in the Task Results window for the data

collection task for that node.

An alternative is to switch the default behavior of the data collection scheduled tasks from wipe to

trend and to use only the most current information for the node. This is important if the network

interface cards (NICs) are ever replaced. However, the HP SIM table will grow and consume more

memory in the HP SIM execution space.

HP recommends that you do not disable the data collection tasks completely because they are also

responsible for keeping the information in the CMS tables current. Disabling them could cause stale

data in the CMS to be used and might result in the wrong tasks executed on the wrong nodes.

Disadvantages of Agentless Installation

The agentless install method does not offer all the advanced SNMP management capabilities

provided by the HP ProLiant Service Pack. You might be interested in the ability of the PSPs to set

performance metrics and tolerance parameters for monitoring and reporting

The agentless install method does not offer a method of communicating with the management

processor through its channel interface driver. This means you cannot use SNMP to obtain information

directly from the management processor. A hardware inventory will record its presence but it will be

unable to obtain its current network IP address or network configuration information.

All associations between a management processor and a server node will rely upon the management

processor entered into the CMS database by a separate mechanism. There are several ways in which

the management processor may be discovered. If the management processor supports it, it can be

configured to send traps of its own to the CMS through its web management console. HP SIM can

also discover the management processor by scanning the range of IP addresses that includes the

management processor. Finally, you can discover the management processor manually by using the

HP SIM web console and entering management processor’s IP address.

After a management processor is discovered, it rarely needs to be rediscovered. It must be manually

removed from the SIM system. There are no data collection events that cause the management

processor to become disassociated from its server.

Agentless Installation Mechanism

There are only four OIDs required in order to elevate a GNU/Linux operating system from

unmanaged to managed status; they are: