Applies To:

Operating System(s): Red Hat Enterprise Linux 5.x, Oracle Enterprise Linux  5.x

Database version(s): Oracle 11g R2

Author:

Phani MV

Problem:

How do I install, enable, and configure IPMI for Oracle 11g R2?

Solution:

1. In order to enable and configure the IPMI tool, please ensure the following prerequisities are met:

  • OpenIPMI-tools RPM is installed version 2.0.16.7 or higher

To check if the OpenIPMI-tools RPM is installed on your system please run the following command:

  • rpm -qa | grep OpenIPMI
NOTE Make sure the machine has BMC (Baseboard Management Controller) running firmware compatible with IPMI 1.5 or later and configured for remote control.

If the OpenIPMI-tools RPM is not installed, please install it using your yum repository via the following command:

  • yum install -y OpenIPMI-tools
NOTE This article assumes there is a yum repository already setup. If a yum repository is required, please visit wiki article http://en.community.dell.com/dell-groups/enterprise_solutions/w/oracle_solutions/1256.aspx for more information.

2. In order to configure the Open IPMI driver,

As root, run the commands:

  • chkconfig ipmi on
  • service ipmi start

3. One the IPMI service has been started, please confirm that the IPMI modules are loaded by running:

  • /sbin/lsmod | grep -i ipmi

The following output should be seen when the command is run:

     ipmi_devintf 44753 2
     ipmi_si 77453 1
     ipmi_msghandler 72985 2
     ipmi_devintf,ipmi_si

4. Ensure the system recognizes the IPMI device, using the following command:

  • ls -l /dev/ipmi0

 

If the IPMI device has been dynamically loaded, then the output should be similar to the following:

crw------- 1 root root 252, 0 Dec 23 16:41

/dev/ipmi0

Configuring the BMC using the IPMI tool

1. Login as root and make sure ipmitool is communicating with the BMC using the IPMI driver. The command to communicate with the BMC is the following:

  • # ipmitool bmc info

                Device ID : 32

                Device Revision : 0

                Firmware Revision : 0.20

                IPMI Version : 2.0

                Manufacturer ID : 674

                Manufacturer Name : Unknown (0x2a2)

                Product ID : 256 (0x0100)

NOTE If ipmitool is not communicating with the BMC ensure the IPMI driver is installed and running.

Enable IPMI Over LAN

1. Determine the channel number for IPMI over LAN. Beginning with channel 1, run the following command until you find the channel that displays the required LAN attributes, such as the IP address:

  • # ipmitool lan print 1

  . . .

IP Address Source: 0x01

IP Address: 140.87.155.89

NOTE On Dell PowerEdge Servers with iDRAC, the output of the above command on Channel 1 will either show the default or manually configured iDRAC IP settings.

 

NOTE On Dell PowerEdge Servers, Channel 1 is the default “out-of-band” channel that is also used by iDRAC. The same channel can be used for IPMI setup.


2. Enable LAN access for the channel found. For example, where the channel is 1:

  • # ipmitool lan set 1 access on

3. Configure IP address settings for IPMI using one of the following procedures:

NOTE If you have already configured a static iDRAC IP address, netmask and gateway parameter on Channel 1 then there is no need to set the LAN parameters again for IPMI. The iDRAC LAN parameter settings can be used for IPMI as well.


  • Using dynamic IP addressing—Dynamic IP addressing is the default assumed by Oracle Universal Installer (OUI). It is recommended that you select this option so that nodes can be added or removed from the cluster easily, as address settings can be assigned automatically.

For example, if the channel is 1, then enter the following command to enable DHCP and set the channel:

  • # ipmitool lan set 1 ipsrc dhcp

NOTE

Use of DHCP requires a DHCP server on the same subnet. Information on setting up a DHCP server is out of scope for this article.

  • Using static IP addressing—If the BMC shares a network connection with the operating system, then the IP address must be on the same subnet. One must set not only the IP address, but also the proper values for netmask, and the default gateway. For example, assuming the channel is 1:
    • # ipmitool lan set 1 ipaddr 192.168.0.55
    • # ipmitool lan set 1 netmask 255.255.255.0
    • # ipmitool lan set 1 defgw ipaddr

NOTE

The address specified in the example(192.168.0.55) is associated only with the BMC, and does not respond to normal pings.

4. Establish an administration account with a user name and password, using the following procedure (assuming the channel is 1):

a. Configure the BMC to authenticate password for Admin access over LAN.

For example:

  • # ipmitool lan set 1 auth ADMIN MD5,PASSWORD

b. List the account slots on the BMC, and identify an unused slot (a User ID with an empty user name field). For example:

  • # ipmitool channel getaccess 1

. . .

User ID : 4

User Name :

Fixed Name : No

Access Available : call-in / callback

Link Authentication : disabled

IPMI Messaging : disabled

Privilege Level : NO ACCESS

. . . 

NOTE

Though the ‘User Name’ for ‘User ID’ 1 might show empty, it is not configurable. Use any other slot with empty ‘User Name’.

 

c. Assign the desired administrator username and password and enable messaging for the identified slot. Once the administrator username and password are set, set the privilege level for that slot when accessed over LAN (channel 1) to ADMIN (level 4). For example:

  • # ipmitool user set name 4 bmcuser
  • # ipmitool user set password 4 password
  • # ipmitool user enable 4
  • # ipmitool channel setaccess 1 4 privilege=4
  • # ipmitool channel setaccess 1 4 link=on
  • # ipmitool channel setaccess 1 4 ipmi=on

d. Verify the setup using the command lan print 1. The following output must be displayed:

  • # ipmitool lan print 1

Set in Progress : Set Complete

Auth Type Support : NONE MD2 MD5 PASSWORD

Auth Type Enable : Callback : MD2 MD5

: User : MD2 MD5

: Operator : MD2 MD5

: Admin : MD5 PASSWORD

: OEM : MD2 MD5

IP Address Source : DHCP Address [or Static

Address]

IP Address : 192.168.0.55

Subnet Mask : 255.255.255.0

MAC Address : 00:14:22:23:fa:f9

SNMP Community String : public

IP Header : TTL=0x40 Flags=0x40 Precedence=…

Default Gateway IP : 192.168.0.1

Default Gateway MAC : 00:00:00:00:00:00

.

.

.

# ipmitool channel getaccess 1 4

Maximum User IDs : 10

Enabled User IDs : 2

User ID : 4

User Name : bmcuser

Fixed Name : No

Access Available : call-in / callback

Link Authentication : enabled

IPMI Messaging : enabled

Privilege Level : ADMINISTRATOR

 

5. Repeat all the above steps on all Oracle nodes within the cluster.

6. Verify that the BMC is accessible and controllable from a remote node in your cluster using the bmc info command. For example, if node2-ipmi is the network host name assigned to BMC for node2, then to verify the BMC on node2 from node1, enter the following command on node1:

 

  • #ipmitool -H <iDRAC-IP> -U <bmc_username> -P <bmc_password> bmc info

    NOTE  <iDRAC-IP> is either the DHCP or the statically assigned IP Address of the iDRAC on the remote node and <bmc_username> and <bmc_password> are the username/password that you set in step 4.c

 

If BMC is correctly configured, then the information about BMC on the remote node is displayed. If you see an error message, such as
Error: Unable to establish LAN session, check the BMC configuration on the remote node.