Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
home_server:home_server_setup:other_services:ipmi [2020-05-13 Wed wk20 13:47] – [Usage:] baumkp | home_server:home_server_setup:other_services:ipmi [2023-12-23 Sat wk51 21:07] (current) – [Usage:] baumkp | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | {{tag> | + | {{tag>linux IPMI, IPMITOOL, CLI, BMC}} |
======IPMI CLI Tools====== | ======IPMI CLI Tools====== | ||
- | Much copied from Adam Sweet' | + | Much copied from Adam Sweet' |
+ | |||
+ | ====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: | ||
+ | *View server chassis and motherboard sensor output remotely, such as chassis status and intrusion detection. | ||
+ | | ||
+ | | ||
+ | |||
+ | Essentially, | ||
+ | |||
+ | Some downside of IPMI: | ||
+ | *In general systems fitted with IPMI are substantially more expensive than those without | ||
+ | *The IPMI controller does use power, about 4-6W | ||
+ | *The IPMI is another security risk vector | ||
+ | |||
+ | ====IPMI Revisions==== | ||
+ | |||
+ | There are currently 3 IPMI revisions (with details taken from http:// | ||
+ | |||
+ | *IPMI v1.0 - Autonomous access, logging and control. IPMI messaging command sets, sensor data records and event messages. Access through system interfaces like memory mapped IO, I2C bus etc. | ||
+ | *IPMI v1.5 - Ability to send IPMI messages to BMC over LAN, LAN alerting. No SOL as part of the standard' | ||
+ | *IPMI v2.0 - Serial Over LAN enabling console redirection, | ||
+ | |||
+ | 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. | ||
====Usage: | ====Usage: | ||
Line 9: | Line 36: | ||
* List available chassis commands:'' | * List available chassis commands:'' | ||
* List chassis policy options '' | * List chassis policy options '' | ||
- | * Lists currnet | + | * Lists current |
* List all current chassis info: '' | * List all current chassis info: '' | ||
* List available power commands'' | * List available power commands'' | ||
Line 45: | Line 72: | ||
(the '' | (the '' | ||
- | < | + | < |
#!/bin/bash | #!/bin/bash | ||
Line 101: | Line 128: | ||
(the '' | (the '' | ||
- | < | + | < |
#!/bin/bash | #!/bin/bash | ||
Line 151: | Line 178: | ||
</ | </ | ||
====Test Script==== | ====Test Script==== | ||
- | < | + | < |
#!/bin/bash | #!/bin/bash | ||
Line 178: | Line 205: | ||
*041 010 kpts | *041 010 kpts | ||
*042 001 Router | *042 001 Router | ||
- | ====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: | ||
- | *View server chassis and motherboard sensor output remotely, such as chassis status and intrusion detection. | ||
- | | ||
- | | ||
- | |||
- | Essentially, | ||
- | |||
- | Some downside of IPMI: | ||
- | *In general systems fitted with IPMI are substantially more expensive than those without | ||
- | *The IPMI controller does use power, about 4-6W | ||
- | *The IPMI is another security risk vector | ||
- | |||
- | ====IPMI Revisions==== | ||
- | |||
- | There are currently 3 IPMI revisions (with details taken from http:// | ||
- | |||
- | *IPMI v1.0 - Autonomous access, logging and control. IPMI messaging command sets, sensor data records and event messages. Access through system interfaces like memory mapped IO, I2C bus etc. | ||
- | *IPMI v1.5 - Ability to send IPMI messages to BMC over LAN, LAN alerting. No SOL as part of the standard' | ||
- | *IPMI v2.0 - Serial Over LAN enabling console redirection, | ||
- | |||
- | 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==== | ====Glossary==== |