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

The format of the directive is the command pass, followed by the OID in numeric form, followed by

the script to run. The script must be referenced with path information, it must be executable, and it

must return the following data:

1. The OID it is servicing

2. The data type of the response

3. The data

Here is an example for the external executable script, /etc/snmp/CntlrAgentLocation.sh:

#!/bin/sh

echo .1.3.6.1.4.1.232.9.2.2.10.0

echo integer

echo 1

The meaning of the data for the OIDs for CntlrAgentLocation.sh, MibStatusArray.sh, and

HostGUID.sh are not open to interpretation ― you must present them exactly as demonstrated. The

following defines these scripts:

CntlrAgentLocation

Instructs the CMS where the agents that respond are running, in this case,

on the server.

MibStatusArray

Instructs the CMS on the agents’ readiness for serving information to the

SNMP master agent

HostGUID

Provides the CMS with a composite of the product number and serial

number smashed together. This composite is used as a pseudo-unique

identifier and associates a server to a management processor. The

management processor also has access to the same information and

advertises it.

The HostGUID is built from information accessible and definable by an

end user from the BIOS console. The fields are editable but they cannot be

blank or else no association between a server and its management

processor will be possible. At runtime, this information is accessible from

dmidecode.

Furthermore, the BIOS console does not restrict the editing of these fields

to characters legal for use by HP SIM. HP SIM does not accept wildcards

and unusual 8-bit characters entered in the product number and serial

number fields of the BIOS console. The server’s proper product number

and serial number are usually located on a tag attached to the outside of

the server case. The product number and serial number must not be

identical to another server in the data center or accessible on the same

local network.

ProductName.sh

OID data is open for definition by the user, but it must be non-null in order

for the server to be elevated from unmanaged to managed status. The

ProductName is generally based on the dmidecode value for the

Product string.

The MibStatusArray is the most difficult OID value to replicate; HP strongly that you cut and paste

the examples to avoid the trouble of replicating it manually. The value is one continuous line and is

wrapped only for presentation in the documentation.