Changes between Version 16 and Version 17 of IPMI_FencingConfig


Ignore:
Timestamp:
05/22/11 00:47:02 (3 years ago)
Author:
digimer
Comment:

Fixed the last copy from the old wiki to work on the new Trac syntax.

Legend:

Unmodified
Added
Removed
Modified
  • IPMI_FencingConfig

    v16 v17  
    1 You have an IPMI BMC but you don't know how to make it work with linux-cluster?  Here's a quick how-to which should get you up and running. 
     1You have an IPMI BMC but you don't know how to make it work with linux-cluster or Red Hat's cluster software?  Here's a quick how-to which should get you up and running. 
    22 
    33== What is IPMI? == 
     
    3636ipmi device interface 
    3737}}} 
    38 Ok!  Moving, on... 
    39  
    40 == IPMI on Dell/IBM machines == 
     38If that works, proceed to configure IPMI for your hardware. 
     39 * [#dellibm Dell, Intel, and IBM machines (typical)] 
     40 * [#ilomp HP machines with iLO MP] 
     41 
     42Also, pay attention to the known bugs: 
     43 * [#bugs Known Bugs] 
     44 
     45== IPMI on Dell/IBM machines == #dellibm 
    4146=== LAN/LAN+ Configuration === 
    4247We need to configure the LAN device for network access.  First, take a look at the configuration: 
     
    95100Password for user 2: mypassword 
    96101}}} 
    97 == Preliminary Testing == 
     102=== Preliminary Testing === 
    98103The easiest thing to check is the power status.  Note - you CAN NOT issue IPMI-over-lan commands from the same machine.  That is, you must perform the following test from a ''different'' machine than the one you have just configured. 
    99104{{{ 
     
    101106Chassis Power is on 
    102107}}} 
    103 == Fencing Configuration == 
     108=== Fencing Configuration === 
    104109Now, we have a working IPMI configuration, we need to add it to cluster.conf.  Here is what the above configuration would look like, given that et-virt05 had an IPMI lan interface set to 10.10.10.52 and et-virt06 had its IPMI lan interface set to 10.10.10.62: 
    105110{{{ 
     
    127132        ... 
    128133}}} 
    129 == Known Bugs == 
    130 The [http://www.intel.com/design/servers/ipmi/pdf/IPMIv2_0_rev1_0_E3_markup.pdf IPMI Specification, Version 2.0, Section 28.3] states: 
    131 {{{ 
    132   [3:0] - chassis control 
    133           0h = power down. Force system into soft off (S4/S45) state. This is for 
    134           ‘emergency’ management power down actions. The command 
    135           does not initiate a clean shut-down of the operating system prior to 
    136           powering down the system. 
    137 }}} 
    138 The source code for ipmitool correctly passes 0x30 to the BMC.  However, most BMCs seem to ignore the fact that this operation is explicitly '''not''' a clean shutdown and generate an ACPI power-off event.  This causes the operating system to  initiate a clean shut down which is ''precisely what we [http://icanhascheezburger.files.wordpress.com/2007/03/captions03211.jpg do not want]''.  Because of this, it is important to disable operating system registration of ACPI.  For most users, simply stopping acpid will be sufficient: 
    139 {{{ 
    140 [root@et-virt05 ~]# chkconfig --level 2345 acpid off 
    141 [root@ayanami lhh]# /sbin/service acpid stop 
    142 Stopping acpi daemon:                                      [  OK  ] 
    143 }}} 
    144 If power off is not immediate during testing of IPMI, it may be necessary to disable ACPI entirely during boot. 
    145  
    146 == IMPI with ILO MP == 
    147 The ILO MP (Integrated Lights-Out Management Processor), which is present on some HP Integrity servers, has the ability to handle IPMI requests. Users that wish to configure fencing for machines with ILO MP will therefore want to use the fence_ipmilan agent. Note that the fence_ilo agent will not work with the ILO MP interface. 
     134 
     135== IMPI with ILO MP == #ilomp 
     136The ILO MP (Integrated Lights-Out Management Processor), which is present on some HP Integrity servers, has the ability to handle IPMI-over-LAN requests.  Users that wish to configure fencing for machines with ILO MP will therefore want to use the ''fence_ipmilan'' agent.  Note that the fence_ilo agent will not work with the ILO MP interface. 
    148137 
    149138The first step is to enable IPMI from with ILO MP. You will need to login to the ILO MP console in order to set this option. Once you are connected to the ILO MP console, enter the 'Command Menu' (CM). You can then enable IPMI by using the following command: 
     
    184173This command will set the password for userid "1", which is the only IPMI user. Note that userid "1" does not have an associated username. This is a limitation of the ILO MP device and it is not possible to set a username for userid "1". This is very important. The IPMI BMC on a ILO MP device will not recognize usernames, and therefore you will never want to pass a username to either ipmitool or fence_ipmilan. 
    185174 
     175=== Fencing Configuration === 
    186176Configuring your cluster to use fence_ipmilan with an ILO MP device is the same as described above with one small exception. As mentioned, you will not want to define a username since the ILO MP device has no notion of usernames. Therefore, when setting up your fencedevice in the cluster.conf file, do not pass a "login=" parameter to the fence agent. 
    187177 
     
    211201}}} 
    212202 
     203== Known Bugs == #bugs 
     204The [http://www.intel.com/design/servers/ipmi/pdf/IPMIv2_0_rev1_0_E3_markup.pdf IPMI Specification, Version 2.0, Section 28.3] states: 
     205{{{ 
     206  [3:0] - chassis control 
     207          0h = power down. Force system into soft off (S4/S45) state. This is for 
     208          ‘emergency’ management power down actions. The command 
     209          does not initiate a clean shut-down of the operating system prior to 
     210          powering down the system. 
     211}}} 
     212The source code for ipmitool correctly passes 0x30 to the BMC.  However, most BMCs seem to ignore the fact that this operation is explicitly '''not''' a clean shutdown and generate an ACPI power-off event.  This causes the operating system to  initiate a clean shut down which is ''precisely what we [http://icanhascheezburger.files.wordpress.com/2007/03/captions03211.jpg do not want]''.  Because of this, it is important to disable operating system registration of ACPI.  For most users, simply stopping acpid will be sufficient: 
     213{{{ 
     214[root@et-virt05 ~]# chkconfig --level 2345 acpid off 
     215[root@ayanami lhh]# /sbin/service acpid stop 
     216Stopping acpi daemon:                                      [  OK  ] 
     217}}} 
     218If power off is not immediate during testing of IPMI, it may be necessary to disable ACPI entirely during boot. 
     219 
     220=== BMC shutdown === 
     221Some new implementations of IPMI has interesting feature. Sending power down to BMC will case shutdown of machine and BMC. In such situation, powering on is no longer possible. It's possible to solve this by using -M (method) parameter with argument "cycle". 
     222 
    213223== References == 
    214224http://www.intel.com/design/servers/ipmi/ - IPMI Specification