Filter
Top Products
Setting Up HPI Clients Software Installation and Configuration
System Management Interface Based on HPI-B (Centellis 4620) User’s Guide (6806800D85A)
19
The corresponding section in the configuration file is called ipmidirect. Within ipmidirect,
you need to adapt the entries addr and port, where addr is the IP address and port is the
port.
In a Centellis 4620 shelf the virtual IP address used to access the SAMs via RMCP is
192.168.24.11 and the port number is 623, by default. Thus, an entry in your configuration file
should look as follows:
handler ipmidirect {
entity_root = "{ADVANCEDTCA_CHASSIS,0}"
name = "lan" # RMCP
addr = "192.168.24.11"
port = "623" # RMCP port
...
Both SAMs are operated in an active/stand-by mode. An internal redundancy mechanism
ensures that the HPI-B daemon is always connected to the currently active SAM. Since a virtual
IP address is used, this is transparent to the HPI-B daemons and HPI-B client applications.
2.3 Setting Up HPI Clients
This section describes how to install/configure HPI clients on node blades.
2.3.1 Installing HPI Clients
Procedure
In order to install/upgrade an HPI-B client package on a node blade, proceed as follows.
1. Connect to the node blade where you wish to install the HPI-B client package.
2. Copy the RPM file that you wish to install to the node blade. Refer to Table " RPM
Files for HPI-B Clients and Daemons" on page 17 for details on available RPM files
for your particular node blade.
3. If applicable, enter rpm -e <Old HPI-B client package name> to uninstall
an already installed client package
4. Enter rpm -i <New HPI-B client RPM file name>
This installs the HPI-B library package.
The following table lists the directories and their content available on the blade after installing
the package.
Table 2-3 Overview of HPI-B Directories and Files on Node Blades
Directory Description
/opt/motorola/lib Contains example applications and shared libraries needed to run
clients