IPMI - Revision history

Digimer at 20:14, 12 April 2014

2014-04-12T20:14:20Z

Digimer: /* Configuring User Authentication = */

2011-12-09T19:01:12Z

Configuring User Authentication =

← Older revision		Revision as of 19:01, 9 December 2011
Line 449:		Line 449:
	At this point, I add the IP address to my cluster nodes' <span class="code">/etc/hosts</span> file (or to [[DNS]] where available).		At this point, I add the IP address to my cluster nodes' <span class="code">/etc/hosts</span> file (or to [[DNS]] where available).

	=== Configuring User Authentication ====		=== Configuring User Authentication ===

	Last part of the configuration is to setup user access. To do is get a list of what user accounts exist on the BMC (remember that we're using channel <span class="code">2</span>), we can run the following command;		Last part of the configuration is to setup user access. To do is get a list of what user accounts exist on the BMC (remember that we're using channel <span class="code">2</span>), we can run the following command;

Digimer at 18:53, 9 December 2011

2011-12-09T18:53:22Z

← Older revision		Revision as of 18:53, 9 December 2011
Line 8:		Line 8:

	If you have already configured your IPMI BMC using software provided by your vendor or via the server's [[BIOS]], you will be able to skip the installation and go directly to the section on testing and using IPMI.		If you have already configured your IPMI BMC using software provided by your vendor or via the server's [[BIOS]], you will be able to skip the installation and go directly to the section on testing and using IPMI.

	~~== EL6 ==~~

	This covers the installation and usage of IPMI on [[EL6]] (version 6.x of [[RHEL]], [[CentOS]] and the like). This was written using two [http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/15351-15351-3328412-241644-3328421-4091396.html HP Proliant DL165 G7] servers, which use basic IPMI instead of [[iLO]].		This covers the installation and usage of IPMI on [[EL6]] (version 6.x of [[RHEL]], [[CentOS]] and the like). This was written using two [http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/15351-15351-3328412-241644-3328421-4091396.html HP Proliant DL165 G7] servers, which use basic IPMI instead of [[iLO]].

	=== Install IPMI ===		== Install IPMI ==

	Installing IPMI is quite simple;		Installing IPMI is quite simple;
Line 23:		Line 21:
	</source>		</source>

	=== Talking to the BMC ===		== Talking to the BMC ==

	We can check to make sure that we've got access to the local BMC using <span class="code">ipmitool</span>;		We can check to make sure that we've got access to the local BMC using <span class="code">ipmitool</span>;
Line 286:		Line 284:
	Perfect, we're now confident that our BMC is available and working properly.		Perfect, we're now confident that our BMC is available and working properly.

	=== Configure the BMC ===		== Configure the BMC ==

	'''BMC''' is an acronym for "'''B'''aseboard '''M'''anagement '''C'''ontroller", which is the name of the actual IPMI controller found inside your server. It can be thought of as a fully separate device, despite residing within the server or even integrated on the mainboard itself. It has it's own [[MAC]] and [[IP]] addresses, access credentials and so forth.		'''BMC''' is an acronym for "'''B'''aseboard '''M'''anagement '''C'''ontroller", which is the name of the actual IPMI controller found inside your server. It can be thought of as a fully separate device, despite residing within the server or even integrated on the mainboard itself. It has it's own [[MAC]] and [[IP]] addresses, access credentials and so forth.

	==== Finding the BMC's Channel ====		=== Finding the BMC's Channel ===

	We will need to configure the BMC's access credentials so that we can talk to it from other nodes. To do this, we need to know which ''channel'' our BMC uses. This depends on your vendor, so we'll need to do a little poking around.		We will need to configure the BMC's access credentials so that we can talk to it from other nodes. To do this, we need to know which ''channel'' our BMC uses. This depends on your vendor, so we'll need to do a little poking around.
Line 341:		Line 339:
	Hit! So our BMC uses channel <span class="code">2</span>. Knowing this, we can now configure the BMC!		Hit! So our BMC uses channel <span class="code">2</span>. Knowing this, we can now configure the BMC!

	==== Configuring Network Details ====		=== Configuring Network Details ===

	Knowing that we're using channel <span class="code">2</span>, we can now configure the BMC's network settings.		Knowing that we're using channel <span class="code">2</span>, we can now configure the BMC's network settings.
Line 451:		Line 449:
	At this point, I add the IP address to my cluster nodes' <span class="code">/etc/hosts</span> file (or to [[DNS]] where available).		At this point, I add the IP address to my cluster nodes' <span class="code">/etc/hosts</span> file (or to [[DNS]] where available).

	==== Configuring Authentication =====		=== Configuring User Authentication ====

	Last part of the configuration is to setup user access. To do is get a list of what user accounts exist on the BMC (remember that we're using channel <span class="code">2</span>), we can run the following command;		Last part of the configuration is to setup user access. To do is get a list of what user accounts exist on the BMC (remember that we're using channel <span class="code">2</span>), we can run the following command;
Line 486:		Line 484:
	Now we're ready to ''use'' IPMI!		Now we're ready to ''use'' IPMI!

	=== Testing Remote IPMI Access and Control ===		== Testing Remote IPMI Access and Control ==

	Now from another machine, let's check the power status of the node we just configured. In my case, my two nodes are called <span class="code">il0051</span> and <span class="code">il0052</span> and I've created entries is <span class="code">/etc/hosts</span> for <span class="code">il0051.ipmi</span> and <span class="code">il0052.ipmi</span>, which I use below.		Now from another machine, let's check the power status of the node we just configured. In my case, my two nodes are called <span class="code">il0051</span> and <span class="code">il0052</span> and I've created entries is <span class="code">/etc/hosts</span> for <span class="code">il0051.ipmi</span> and <span class="code">il0052.ipmi</span>, which I use below.

Digimer at 18:52, 9 December 2011

2011-12-09T18:52:17Z

Show changes

Digimer: /* IPMI Setup for Remote Access and Fencing */

2011-06-03T02:58:09Z

IPMI Setup for Remote Access and Fencing

← Older revision		Revision as of 02:58, 3 June 2011
Line 18:		Line 18:
	You can check that IPMI is working now by running:		You can check that IPMI is working now by running:

	~~'''~~ipmitool chassis status~~'''~~		<source lang="bash">
			ipmitool chassis status
			</source>
	<source lang="text">		<source lang="text">
	System Power : on		System Power : on
Line 102:		Line 104:

	<source lang="bash">		<source lang="bash">
	~~digimer@lework:~$~~ ipmitool -I lan -H 10.255.135.12 -U admin -P secret chassis power status		ipmitool -I lan -H 10.255.135.12 -U admin -P secret chassis power status
			</source>
			<source lang="text">
	Chassis Power is on		Chassis Power is on
	~~digimer@lework:~$~~ ipmitool -I lan -H 10.255.135.13 -U admin -P secret chassis power status		</source>
			<source lang="bash">
			ipmitool -I lan -H 10.255.135.13 -U admin -P secret chassis power status
			</source>
			<source lang="text">
	Chassis Power is on		Chassis Power is on
	</source>		</source>
Line 112:		Line 120:
	Now to reboot or power off a given server, you can call either:		Now to reboot or power off a given server, you can call either:

			Reboot node1
	<source lang="bash">		<source lang="bash">
	~~# Reboot node1~~
	ipmitool -I lan -H 10.255.135.12 -U admin -P secret chassis power cycle		ipmitool -I lan -H 10.255.135.12 -U admin -P secret chassis power cycle
	~~# or~~ Power off node2		</source>

			Power off node2
			<source lang="bash">
	ipmitool -I lan -H 10.255.135.13 -U admin -P secret chassis power off		ipmitool -I lan -H 10.255.135.13 -U admin -P secret chassis power off
	</source>		</source>

Digimer at 05:15, 19 August 2010

2010-08-19T05:15:30Z

← Older revision		Revision as of 05:15, 19 August 2010
Line 4:		Line 4:

	IPMI is used as the basis of numerous OEM remote access technologies. To learn more, please see the [http://en.wikipedia.org/wiki/Intelligent_Platform_Management_Interface wikipedia entry].		IPMI is used as the basis of numerous OEM remote access technologies. To learn more, please see the [http://en.wikipedia.org/wiki/Intelligent_Platform_Management_Interface wikipedia entry].

			= IPMI Setup for Remote Access and Fencing =

			'''Note''': This applies to CentOS 5.x and is copied from another document. It needs serious cleanup.

			Install IPMI:
			<source lang="bash">
			yum install freeipmi.x86_64 freeipmi-bmc-watchdog freeipmi-ipmidetectd OpenIPMI.x86_64 OpenIPMI-libs.x86_64 OpenIPMI-perl.x86_64 OpenIPMI-tools.x86_64
			chkconfig ipmi on
			/etc/init.d/ipmi start
			</source>

			You can check that IPMI is working now by running:

			'''ipmitool chassis status'''
			<source lang="text">
			System Power : on
			Power Overload : false
			Power Interlock : inactive
			Main Power Fault : false
			Power Control Fault : false
			Power Restore Policy : always-off
			Last Power Event :
			Chassis Intrusion : inactive
			Front-Panel Lockout : inactive
			Drive Fault : false
			Cooling/Fan Fault : false
			</source>

			Now setup the IPMI BMC.

			'''Node1''':
			<source lang="bash">
			ipmitool -I open lan set 1 macaddr 00:22:15:d6:32:a8
			ipmitool -I open lan set 1 ipsrc static
			ipmitool -I open lan set 1 ipaddr 10.255.135.12
			ipmitool -I open lan set 1 defgw ipaddr 10.255.255.254
			ipmitool -I open lan set 1 netmask 255.255.0.0
			ipmitool -I open lan set 1 password secret
			ipmitool -I open user set password 2 secret
			ipmitool -I open lan set 1 snmp iplink
			ipmitool -I open lan set 1 access on
			ipmitool mc reset cold
			sleep 5
			ipmitool -I open lan print 1
			</source>

			'''node2''':
			<source lang="bash">
			ipmitool -I open lan set 1 macaddr 00:22:15:d6:32:a9
			ipmitool -I open lan set 1 ipsrc static
			ipmitool -I open lan set 1 ipaddr 10.255.135.13
			ipmitool -I open lan set 1 defgw ipaddr 10.255.255.254
			ipmitool -I open lan set 1 netmask 255.255.0.0
			ipmitool -I open lan set 1 password secret
			ipmitool -I open user set password 2 secret
			ipmitool -I open lan set 1 snmp iplink
			ipmitool -I open lan set 1 access on
			ipmitool mc reset cold
			sleep 5
			ipmitool -I open lan print 1
			</source>

			Both should finish showing something like:

			<source lang="text">
			Set in Progress : Set Complete
			Auth Type Support : NONE MD2 MD5 PASSWORD
			Auth Type Enable : Callback : NONE MD2 MD5 PASSWORD
			: User : NONE MD2 MD5 PASSWORD
			: Operator : NONE MD2 MD5 PASSWORD
			: Admin : NONE MD2 MD5 PASSWORD
			: OEM : NONE MD2 MD5 PASSWORD
			IP Address Source : DHCP Address
			IP Address : 10.255.135.12
			Subnet Mask : 255.255.0.0
			MAC Address : 00:22:15:d6:32:a8
			SNMP Community String : iplink
			IP Header : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10
			BMC ARP Control : ARP Responses Enabled, Gratuitous ARP Disabled
			Gratituous ARP Intrvl : 2.0 seconds
			Default Gateway IP : 10.255.255.254
			Default Gateway MAC : 00:00:00:00:00:00
			Backup Gateway IP : 0.0.0.0
			Backup Gateway MAC : 00:00:00:00:00:00
			RMCP+ Cipher Suites : 0,1,2,3,6,7,8
			Cipher Suite Priv Max : uaaaXXaaaXXXXXX
			: X=Cipher Suite Unused
			: c=CALLBACK
			: u=USER
			: o=OPERATOR
			: a=ADMIN
			: O=OEM
			</source>

			Now test access to both machines from a remote workstation in the Interlink office by calling:

			<source lang="bash">
			digimer@lework:~$ ipmitool -I lan -H 10.255.135.12 -U admin -P secret chassis power status
			Chassis Power is on
			digimer@lework:~$ ipmitool -I lan -H 10.255.135.13 -U admin -P secret chassis power status
			Chassis Power is on
			</source>

			If you don't see: '''Chassis Power is on''' for both, something has gone wrong.

			Now to reboot or power off a given server, you can call either:

			<source lang="bash">
			# Reboot node1
			ipmitool -I lan -H 10.255.135.12 -U admin -P secret chassis power cycle
			# or Power off node2
			ipmitool -I lan -H 10.255.135.13 -U admin -P secret chassis power off
			</source>

			Done! That command above also doubles as the fence command

	{{footer}}		{{footer}}

Digimer: Created page with '{{header}} IPMI is an acronym for '''I'''ntelligent '''P'''latform '''M'''anagement '''I'''nterface. This is a technology built into many server-grade mainboards, sometimes via …'

2010-08-13T15:33:01Z

Created page with '{{header}} IPMI is an acronym for '''I'''ntelligent '''P'''latform '''M'''anagement '''I'''nterface. This is a technology built into many server-grade mainboards, sometimes via …'

Páàjì titun

{{header}}

IPMI is an acronym for '''I'''ntelligent '''P'''latform '''M'''anagement '''I'''nterface. This is a technology built into many server-grade mainboards, sometimes via an optional add-in card, that allows "out of band" access to a server. This means that, via an IPMI interface, a user can remotely connect to a server regardless of it's power state. Through this interface the user can check the power state of the server plus one or more of it's sensors. The user can initiate a reboot, power off, power on and so forth.

IPMI is used as the basis of numerous OEM remote access technologies. To learn more, please see the [http://en.wikipedia.org/wiki/Intelligent_Platform_Management_Interface wikipedia entry].

{{footer}}