Как установить ipmiview linux

komivlad.net

Как писал ранее, приобрели новые сервера с поддержкой ipmi на борту, под виндой есть спец утилита для работы с этой приблудой, а вот под убунту, которую я начал пробовать использовать как рабочую станцию думал будет проблематично найти софтинку, оказалось не так страшен черт как его . ну вобщем вы знаете :)))
Оказывается на фтп supermicro есть и под линукса ipmiview, на момент написания статьи ссылка на линуксовую версию была ТУТ . кому влом заморачиваться, можете использовать браузер, но мне не удобно, т.к. необходима систематизация, что реализовано в ipmiview (на скрине кусок браузерной версии)

В общем слова словами, приступим к установке.

Первым делом надо скачать саму софтинку, думиаю с этим проблем у вас не возникло, можете скачать архив, лично я слил себе *.bin файлик. Напомню что раньше никогда не сталкивался с линуксом и пришлось почитать как устанавливать приложения из bin.
Открываем консоль, и переходим в директирию куда скачали bin файл (если качали архив, то распаковываем архив и переходим в директорию куда распаковали)

Далее по скринам, смотрим, делаем ТОЧНО также, и все получится :)))))
Инициализируется инсталятор:

Появилось окно инсталятора:

Читаем соглашение, принимаем его. ))))

Выбираем директорию куда ставить, я затупил и поставил в корень Programs (эту папку надо создать самому, телодвижения как и под виндой, инсталятор позволяет)

Инсталяция завершена:

После инсталяции топаем в директорию куда установили и пробуем запустить IPMIview20.bin
получаем следующую ошибку:

я вылечил таким образом, нажимаем на кнопку «Выбрать приложение»
и в открывшемся окне, в поле Использовать собственную команду, ввел sh (смотри на нижний скрин)

и клацем в кнопку Открыть
Тратата))) запустилась наша софтинка:

Настройка ничем не отличается от своего виндового собрата.
Думаю в одной из следующих статей опишу процесс добавления нового девайса в ipmiview

Поделись с друзьями:

Смотрите также:

4 комментария

Подписаться на комментарии по RSS

статья написана с установкой именно под такой осью, сейчас у меня 10.04, проблем также не было с инсталяцией

У меня Ubuntu 11.04. А у вас?

Кстати, с просто ‘sh’ в кнопке запуска не запускается, только с ‘gksu sh’, т.е. от root’а.

Какая Java установлена у вас?

такой проблемы не встречал, сколько раз ставил на бубутну запускалось с полпинка, возможно проблема с явой, переустановите ее

По инструкции все поставил. Программа запустилась. Добавляю сервер. Работает все кроме запуска КВМ консоли 🙁 (последняя вкладка).

Источник

Adam Sweet’s Wiki

User Tools

Site Tools

Table of Contents

Running IPMI on Linux

What is IPMI?

IPMI is standard which allows remote server management, primarily developed by Intel. IPMI cards, known as Baseboard Management Cards (BMCs) are primitive computers in their own right and are operational all the time, so long as the server has a power source. The server itself does not need to be powered on, or the operating system operational for the BMC to work, it just needs a power source to be connected to the server.

The primary benefits of IPMI are:

Essentially, IPMI will save you from a few hundred to over a thousand GBP instead of buying a remote power control unit and SOL will save you the same amount again over buying an IP KVM.

IPMI Revisions

There are currently 3 IPMI revisions (with details taken from http://www.ecst.csuchico.edu/

IPMI version 2.0 is desirable as it allows you to use SOL to get a remote console on the server as though it were local in cases where the operating system locks up and SSH or (heaven forbid) telnet access are not available due to the operating system being inoperable. v2.0 also allows you to encrypt the contents of the IPMI packets sent to remote systems and so protects the BMC passwords and your commands on the network. IPMI v1.5 still allows to you to power the system on and off and view sensor output, but does not support packet encryption (and therefore sends your BMC password over the network in plain text) and does not support SOL in any standardised way. Both 2.0 and 1.5 are in common usage and are both still sold on new servers.

Glossary

List of IPMI terms. Taken wholesale from http://www.ecst.csuchico.edu/

Installation

This guide covers the installation of IPMI tools on Dell 1425 servers and Supermicro servers with a PDSMi+ motherboard. The instructions will be relevant for other server models, but I make no promises. I make references in the links section to Supermicro X7DVL based hardware which comes with a different IPMI BMC but I haven’t spent much time investigating the hardware.

For Supermicro servers, open up the server chassis and make a note of the MAC address on the IPMI port. You’re supposed need this later when flashing the BMC with it’s firmware, however I found that it wasn’t necessary to tell the BMC it’s MAC address as it already knew and offered it as a default when asking for it. The wise amongst you will write this down anyway and compare it to what the flashing utility says. Beware also that the Supermicro docs erroneously tell you to get the MAC address from the LAN ports, not the BMC socket, this is wrong, you need the MAC written on the BMC’s socket.

In the BIOS, set the console redirection to COM2, which is the BMC console port, it doesn’t physically exist). Disable BIOS redirection after POST, choose a baud rate (19200 is default on PDSMI+ motherboards, so we used it as a default on everything to keep things tidy, Supermicro X7DVL motherboards which use a SIMIPMI BMC could use a number of different baud rates, your choice is up to you), a terminal type (vt100 works ok for me) and leave the other settings as they are.

When the process finished, use the ipnmac utility while still booted from the CD, by typing ipnmac (if you’re not in the right directory you’ll have to navigate using cd and dir commands to find it). Give it a unique IP address from any other interface on the machine or on your network. The BMC needs to be network addressable in its own right. Also give it the MAC address you took from the IPMI socket on the motherboard, not the one written on the LAN ports as suggested by the official Supermicro docs. As I said before, I found that the flashing utility offered the correct MAC address as a default at this stage, but it would be wise to check it against what you wrote down earlier.

Once this step is done, hit CTRL-Alt-Del and remove the CD.

For Dell 1425 servers (and probably other Dells), hit Alt-3 when prompted to enter the BMC setup and give it some unique network settings and some user settings (make your passwords secure!).

You can boot now into Linux, or from a Linux installer CD.

Note on network configuration:

Once booted into Linux, install openipmi on all machines with a BMC and ipmitool on every machine from which you wish to run IPMI commands locally or to send IPMI commands to a remote machine. Red Hat, FC and Centos users will have to install OpenIPMI and OpenIPMI-tools. SUSE and other Linux users will have figure out what to do themselves for ipmitool. There are IPMItool packages on the website if they’re not in your package-shallow distros ;). OpenIPMI is not required to send ipmi commands to remote machines. You only need OpenIPMI where you want to run IPMI commands locally, manage the BMC locally from the OS (which you want to do if you have a BMC in the machine) or I presume to do console redirection over the BMC.

Next you need to load the kernel modules. Fedora/Red Hat/Centos people just need to run setup, open the services tool and check the ipmi box then run /etc/init.d/ipmi start. On Ubuntu I had to do the following, Red Hat and derivatives could try this if their devices aren’t found when starting the service. Try modprobing ipmi_si without any options at first, then build up the options if it fails. If you’re not sure which method your BMC uses, try leaving out the type= parameter as the module will figure it out.

If ipmi_si won’t load, you may need to use:

Or look at the output of dmidecode for the base address of your IPMI BMC and then use that base address for the ports= module option. The default ports option is 0xca2 so if your BMC is at that address according to dmidecode , then you don’t need this option. A SLES 10 user tells me that they did have to specify the ports value 0xca2 on an HP DL380 G5, so perhaps it isn’t always the default.

Kernel 2.4 people will have to follow the Debian IPMI instructions, as you’re living in a world I haven’t encountered with IPMI. You should note that ipmi_si is called ipmi_si_drv and its regspacings option is called si_regspacings. You may also have to make your own device node if you’re not using devfs, as documented in the Debian instructions. After modprobing the relevent modules successfully, ls -l /dev/ipmi0 to see if you have a device node before trying to create one.

If this works without errors then Fedora/RH/Centos people are set, Ubuntu/Debian people need to add the modules and options to /etc/modules or maybe add the modprobe commands to /etc/init.d/local if you have no other way.

If you then cat /proc/devices , you should see your IPMI device listed and ls -l /dev/ipmi0 should show your device node.

Setting Up Serial Consoles

Neither of the 2 brands of BMCs I have set up have a physical serial port, they are logical and are managed by the BMC.

You should have set up your BIOS for console redirection earlier, so now we will do the bootloader and init.

To allow your bootloader to redirect over the BMC’s serial port, for Grub v1, edit /boot/grub/grub.conf, sometimes known as /boot/grub/menu.list add the following lines to grub.conf or menu.list:

To make kernel messages output over your BMC, add console=tty0 console=ttyS1,19200n8r to the end of your kernel lines, so it should look something like the following:

This gives you a serial console on the second serial port, which should be your BMC’s serial port, at 19200Kb per second, which should match what you chose in the BIOS. The order of the console options above is important. The last listed will be the system’s default console which will display the boot messages and kernel errors. This means that after halfway through the boot process, during shutdown and when there are kernel errors, only the serial console will see the messages. As you want to work remotely, this is the way it has to be. You can’t have more than one default console. You can however interrupt grub at boot time and edit the kernel line for a single boot with different parameters if you need to see the default console locally but remember that they will persist until you reboot, which means that if you reboot but still want to see them locally, you’ll have to interrupt and edit grub at boot time again and also, to see them remotely again, you need to remember to reboot.

About halfway through the bootup procedure, once the kernel has booted and loaded drivers for your hardware and has mounted the hard disks and so on, the bootloader hands over to init which brings up your services and network configurations etc. To get init and therefore your booting/booted Linux system redirecting the console over the BMC’s serial port, edit /etc/inittab and add the following line to the console section for Debian/Ubuntu:

For Fedora/Red Hat/CentOS:

This gives you a serial console on the second serial port, which should be your BMC’s serial port, for the BIOS as configured earlier, the bootloader and init. Again, change 19200 to whatever you chose in your BIOS.

Users of Ubuntu (and presumably Debian and it’s other derivative distributions) can read https://help.ubuntu.com/community/IPMI for assistance with all of this stuff. I guess it will be useful for everybody else too, if you can recognise where it is Ubuntu specific.

IPMI Commands

You should then be able to run some IPMI commands locally (probably need to be root as root owns the device node):

Thats pretty simple.

If that all works for you then you can a woop and a holler.

IPMItool has a familiar UNIX bash shell or Cisco IOS syntax, which allows you to complete the command as you go along. If you type in an incomplete command, IPMItool will provide you with a list of options that can be used to complete your command.

Simply typing ipmitool -I open will offer the top-level sub-commands, which you can then choose from to add to your command.

Setting Up the BMC

The Supermicro BMCs send out arp requests gratuitously which can degrade performance, so we will turn them off:

We will also set the BMC’s netmask as well as it’s default and backup gateways:

You can also set the gateway MAC addresses if you want to.

And now set it’s SNMP community name so that we can send SNMP traps:

Getting a Remote Console Using IPMI

SOL only works on IPMI 2.0 BMCs and so only works with devices which support the encrypted lanplus interface (though my Supermicro’s would do it without encryption using the graphical tool described below).

If SOL doesn’t work or you simply want to quit your SOL session, you can use the key sequence:

to get out. It seems that inside a SOL session, all of ipmitool’s SOL session commands start with the character

Alternatively you may use a graphical tool as described below.

Graphical IPMI

There is a Java application from Supermicro called IPMIView which allows you to graphically manage servers with IPMI BMCs. The primary advantage of this tool is that SOL works easily and you can issue graceful reboot and shutdown commands if you install Supermicro’s graceful shutdown daemon. The version of IPMIView which is shipped on the CD (as of late 2007) doesn’t work on FC6 or F7, however the latest version from the FTP site does. Another version, shipped on the Supermicro FTP site for our dual processor machines is at ftp://ftp.supermicro.com/CDR-SIMIPMI_1.11_for_SIM_IPMI/IPMI_Solution/Linux/Administrator and this appears to work with Fedora 7 also.

Install as a regular user using sudo from the command line (by uncommenting the following line from /etc/sudoers if need to):

…and adding your user to the wheel group:

Make the installer executable:

and run it as sudo:

It should now run. When the install finishes you need to chmod +x the bundled JRE directory as it’s root only by default:

Now you should be able to run

as a regular user and create a desktop icon for it by right-clicking the desktop, clicking Create Launcher and providing the command as above and any other meta-data you wish to add, like description, name and and a nice icon from the installation directory.

Using the IPMIView application is covered in the Supermicro documentation (seems to be the only thing covered in them too…)

Adding an IPMI User With IPMIView

You should now be able to search for the host’s IPMI device address in IPMIView and log in with the username and password of ADMIN. You should add a new user, change it’s user level to administrator and delete the ADMIN user.

Источник