Linux ha fence设备测试.docx

另外，在配置RHCS5.3时，Fence设备只ping通还不行，还必须经过测试，我在网上找了一篇IPMI的文章，现粘贴如下：What is IPMI?Intelligent Platform Management InterfaceeditAdvantagesLow cost. Available on most recent server systems. editDisadvantagesThere is no way to retain power to the IPMI BMC if power to the host is lost. If power is lost to the host, fencing will fail. This will delay cluster recovery. It is recommended to either have a second fencing device (external power switch) or a server with multiple power supplies when using IPMI over LAN for fencing. Some IPMI implementations share an ethernet interface with the host operating system. If this interface is the same one used for the cluster communication, a loss of connectivity to this port will cause a need for fencing but also cause fencing to fail, delaying cluster recovery. It is recommended that the ethernet interface the BMC uses be reserved exclusively for BMC use; that is, the host operating system should not use the BMCs NIC. editPrerequisitesYou will need the OpenIPMI packages and the ipmitool utility in order to use this mini-howto. On Red Hat Enterprise Linux 5 and CentOS 5, the packages you need are: OpenIPMIOpenIPMI-toolsYou will also need some free IP addresses which you assign to IPMI devices. This mini-HOWTO is for machines which have not had IPMI-over-LAN set up before. editBasic ConfigurationSee if you can start ipmi:rootet-virt05 # service ipmi startStarting ipmi drivers: OKIf it fails (FAILED), go have a beer or something, because the rest of this howto will not help you. If it succeeds, you should see something like this (may differ by hardware) in dmesg output:ipmi message handler version 39.1IPMI System Interface driver.ipmi_si: Trying SMBIOS-specified kcs state machine at i/o address 0xca8, slave address 0x20, irq 0ipmi: Found new BMC (man_id: 0x0002a2,prod_id: 0x0000, dev_id: 0x20)IPMI kcs interface initializedipmi device interfaceOk! Moving, on.editLAN/LAN+ ConfigurationWe need to configure the LAN device for network access. First, take a look at the configuration:rootet-virt05 # ipmitool lan print 1Set in Progress : Set CompleteAuth Type Support : NONE MD2 MD5 PASSWORDAuth Type Enable : Callback : MD2 MD5 : User : MD2 MD5 : Operator : MD2 MD5 : Admin : MD2 MD5 : OEM : MD2 MD5 IP Address Source : Static AddressIP Address : 0.0.0.0 - need to set this Subnet Mask : 0.0.0.0 - also need to set thisMAC Address : 00:13:72:50:05:f0SNMP Community String : publicIP Header : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10Default Gateway IP : 0.0.0.0 - Might need to set thisDefault Gateway MAC : 00:00:00:00:00:00Backup Gateway IP : 0.0.0.0Backup Gateway MAC : 00:00:00:00:00:00802.1q VLAN ID : Disabled802.1q VLAN Priority : 0Cipher Suite Priv Max : Not AvailableNow we need to set the IP address, netmask, gateway, etc. of the LAN interface. Things to remember:The IP address must not be used anywhere else on the network. If you are using DHCP for the host, you may usually not use DHCP for IPMI-over-LAN and vice-versa. This is because of the fact that some machines share a MAC address between the IPMI-over-LAN device and the device used by the operating system. I used static addresses on the IPMI devices. rootet-virt05 # ipmitool lan set 1 ipsrc staticrootet-virt05 # ipmitool lan set 1 ipaddr 10.10.10.52Setting LAN IP Address to 10.10.10.52rootet-virt05 # ipmitool lan set 1 netmask 255.255.255.0Setting LAN Subnet Mask to 255.255.255.0rootet-virt05 # ipmitool lan set 1 arp respond onrootet-virt05 # ipmitool lan set 1 arp generate onrootet-virt05 # ipmitool lan set 1 arp interval 5Finally, we have to enable the interface:rootet-virt05 # ipmitool lan set 1 userrootet-virt05 # ipmitool lan set 1 access oneditUser ConfigurationFirst, we need to list the users and get the user ID of the administrative user for IPMI:rootet-virt05 # ipmitool user listIDName CallinLink AuthIPMI Msg Channel Priv Limit2 root true true true ADMINISTRATORIf you dont already know the password for the root user, you can set it from the command line as well. This should NOT be the same as the root user password for the system). Note the 2 in the command line - this matches the administrator / root account from above:rootet-virt05 # ipmitool user set password 2Password for user 2: mypasswordPassword for user 2: mypasswordeditPreliminary TestingThe 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.rootet-virt06 yum# ipmitool -H 10.10.10.52 -I lan -U root -P mypassword chassis power statusChassis Power is oneditFencing ConfigurationNow, 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: . .editKnown BugsThe IPMI Specification, Version 2.0, Section 28.3 () states:3:0 - chassis control 0h = power down. Force system into soft off (S4/S45) state. This is for emergency management power down actions. The command does not initiate a clean shut-down of the operating system prior to powering down the system.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 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:rootet-virt05 # chkconfig -level 2345 acpid offrootayanami lhh# /sbin/service acpid stopStopping acpi daemon: OKIf power off is not immediate during testing of IPMI, it may be necessary to disable ACPI entirely during boot.Getting the OS prepared:1) Install IPMItool and the startup scripts. On Red Hat Enterprise Linux install the OpenIPMI, OpenIPMI-tools, OpenIPMI-libs, and OpenIPMI-devel packages. That will get you everything you need. There are similar packages available for other distributions (SuSE, Ubuntu, CentOS, etc.). Youll need IPMItool on any machine you want to configure, and any machine you want to send commands from.2) Enable the IPMI service:/sbin/chkconfig ipmi on3) Start the IPMI service, which will load the kernel modules for you:/sbin/service ipmi startConfigure the BMC for Remote Usage:1) There are two ways to configure the BMC. You can configure it through the boot-time menu (Ctrl-E), where you can set the management password and IP address information. Or, you can configure it with ipmitool from the OS. Replace my sample IP address, gateway, and netmask with your own:/usr/bin/ipmitool -I open lan set 1 ipaddr 192.168.40.88/usr/bin/ipmitool -I open lan set 1 defgw ipaddr 192.168.40.1/usr/bin/ipmitool -I open lan set 1 netmask 255.255.255.0/usr/bin/ipmitool -I open lan set 1 access on2) Secure the BMC, so unauthorized people cant power cycle your machines. To do this you want to change the default SNMP community, the “null” user password, and the root user password. First, set the SNMP community, either to a random string or something you know:/usr/bin/ipmitool -I open lan set 1 snmp YOURSNMPCOMMUNITYThen set the null user password to something random. Replace CRAPRANDOMSTRING with something random and secure:/usr/bin/ipmitool -I open lan set 1 password CRAPRANDOMSTRINGLast, set the root user password to something you know:/usr/bin/ipmitool -I open user set password 2 REMEMBERTHISDouble-check your settings with:/usr/bin/ipmitool -I open lan print 1Trying it:1) You can set an environment variable, IPMI_PASSWORD, with the password you used above. That will save some typing:export IPMI_PASSWORD=REMEMBERTHISIf you use this substitute the “-a” in the following commands with a “-E”.2) From another machine issue the following command, obviously replacing the IP w