Server management over the network, bmc, ipmi, setup?

Question

Remote access

I set up a server on the intel sr1630hgp platform, OS: ubuntu server 10.04
in the technical documentation it is said that the platform supports the ipmi2.0 protocol
in the BIOS set up passwords for the root and anonymous user, enabled users, in the same tab set the IP settings as dynamic, because . DHCP is configured on my network,
I try to connect remotely - I can’t
try to reach locally through ipmitool - nothing either, maybe you need to install drivers in the OS for BMC and IPMI ...
if anyone has come across - please help, tell me which way to dig
, here are some details:

[email protected]:~$ ipmitool -I open channel info<br/>
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory<br/>
Unable to Get Channel Info

UPD:
There was progress, locally managed to get through:

[email protected]:~# ipmitool -I open chassis power status<br/>
Chassis Power is on<br/>
[email protected]:~# ipmitool -I open chassis status<br/>
System Power : on<br/>
Power Overload : false<br/>
Power Interlock : inactive<br/>
Main Power Fault : false<br/>
Power Control Fault : false<br/>
Power Restore Policy : always-on<br/>
Last Power Event :<br/>
Chassis Intrusion : inactive<br/>
Front-Panel Lockout : inactive<br/>
Drive Fault : false<br/>
Cooling/Fan Fault : false<br/>
Sleep Button Disable : not allowed<br/>
Diag Button Disable : allowed<br/>
Reset Button Disable : allowed<br/>
Power Button Disable : allowed<br/>
Sleep Button Disabled: false<br/>
Diag Button Disabled : false<br/>
Reset Button Disabled: false<br/>
Power Button Disabled: false

However, over the network it does not work:

Error: Unable to establish IPMI v2 / RMCP+ session<br/>

Answer 1

Basically, IPMI has its own IP and MAC address, so conflicts should not occur. Implementations are different: with reference to a real physical. interface or a completely separate interface. In the case of a separate external control, a separate cord is required. In the case of integration with a real port, situations of both dynamic binding and permanent binding are possible. With a permanent (physical) binding, except by poking the cable, do not correct the situation. And with dynamic, variations are possible when IPMI clings to any port that works when turned on, if only one of the two ports is enabled, otherwise it remains available on the default port. In the latest implementations, it is possible to reassign the default port, you can change it either from the BIOS or using the OpenIPMI package (Linux) or via jumpers.
At the very beginning, you need to determine what type your case belongs to, this can be found in the documentation for the mother.

Answer 2

have you tried loading impi kernel modules?

Answer 3

modprobe ipmi_msghandler
modprobe ipmi_devintf
modprobe ipmi_si type=kcs ports=0xca8 regspacings=4

what do you mean by kernel modules?
no cord, built-in controller, works on NIC1

Answer 4

Have you tried using https? Is encryption enabled? On one controller out of 20, it was approximately turned on.

Answer 5

1) Try the rmcpping utility (or any other utility that pings IP via rmcp - be it rmcpping or rmcp_ping) - utilities from different packages are simple. If he answers, then he listens.
2) Over the network - ipmitool -I lanplus -H hostname -U root chassis power status

Answer 6

yes, NIC2 was connected, unfortunately I have only 1 cable
, now when I connect via ssh I get into the SMASH console, from where I can perform the actions I need, configure the BIOS, view information from sensors and manage power , I can’t understand only, IPMI completely eats off IP or how? I didn't find any information on this topic.
->start /system1
COMMAND COMPLETED :
start /system1
ufip=/system1
Start: Target started successfully