| [Top] | [Contents] | [Index] | [ ? ] |
| 1. Introduction to the GNU FreeIPMI system | ||
| 2. Installing GNU FreeIPMI | Installing the software. | |
| 3. IPMI C library (libfreeipmi) | High-level C library for IPMI | |
| 4. ipmi-locate IPMI device probing tool | IPMI device probing tool. | |
| 5. FISH FreeIPMI SHell | FreeIPMI SHell. | |
| 6. bmc-config | Baseboard Management Controller configurator. | |
| 7. bmc-info | Baseboard Management Controller information. | |
| 8. bmc-autoconfig | Wizard-like frontend for bmc-config. | |
| 9. ipmi-raw | executes IPMI commands by hex values. | |
| 10. ipmi-sensors | IPMI sensors utility. | |
| 11. ipmi-sel | IPMI System Event Log. | |
| 12. bmc-watchdog | Watchdog daemon. | |
| 13. IPMI power control utility | IPMI power control utility. | |
| 14. ipmiping | IPMI ping reachability test utility. | |
| 15. rmcpping | RMCP ping reachability test utility. | |
| 16. Gratuitous ARP Daemon | ||
| 17. Trouble-shooting | Trouble-shooting tips. | |
| 18. Contact us | Contact Information. | |
| 19. Authors | FreeIPMI core team members. | |
| 20. Copying | GNU FreeIPMI is a Free Software. | |
| 21. Glossary | Conventions and terminologies. | |
| Concept index | Index of concepts. | |
| Program index | Index of programs. |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
GNU FreeIPMI is a Free Intelligent Platform Management System Software. It provides "Remote-Console" (out-of-band), "System Management Software" (in-band) and a development library confirming to Intelligent Platform Management Interface (IPMI v1.5) standards.
GNU FreeIPMI User's Guide concentrates installation, usage, troubleshooting and bug reporting. It corresponds to 0.2.0 release.
| 1.1 Who should read this guide? | ||
| 1.2 IPMI - Platform Management Standard | Platform Management Standard. |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
If you want to use the Intelligent Platform Management Interface functionalities available on modern motherboards running GNU or any POSIX compliant operating systems, this guide is right for you.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The IPMI specifications define standardized, abstracted interfaces to the platform management subsystem. IPMI includes the definition of interfaces for extending platform management between board within the main chassis, and between multiple chassis.
The term platform management is used to refer to the monitoring and control functions that are built in to the platform hardware and primarily used for the purpose of monitoring the health of the system hardware. This typically includes monitoring elements such as system temperatures, voltages, fans, power supplies, bus errors, system physical security, etc. It includes automatic and manually driven recovery capabilities such as local or remote system resets and power on/off operations. It includes the logging of abnormal or out-of-range conditions for later examination and alerting where the platform issues the alert without aid of run-time software. Lastly it includes inventory information that can help identify a failed hardware unit.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
You can obtain copies of source, binary, documentation and other useful information from the GNU FreeIPMI Home Page.
| 2.1 Dependencies | Dependent run-time and libraries. | |
| 2.2 Building the source package. | Compile and install from the source. | |
| 2.3 Test Fire | Test fire your installation. |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
GNU FreeIPMI is designed to have minimum dependencies on other libraries and tools. FreeIPMI Shell alone depends on GNU Guile and GNU Readline for the convenience of extension, scripting and GNU Bash like user interface. libfreeipmi library has virtually no dependencies at all.
List of dependencies under Debian GNU/Linux:
List of dependencies under Fedora or RedHat GNU/Linux:
List of dependencies under FreeBSD:
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
To compile the program, you must first run the configure
script included with the source tar ball. It works just like any other
standard GNU autoconf created script. See the more generic
configure related installation instructions below.
For complete list of options, try configure --help.
Note: Please run ./autogen.sh script before
./configure, if you are compiling FreeIPMI source from CVS.
# ./configure --prefix=/usr # make # make install |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Example:
tar xzvf freeipmi-0.1.3.tar.gz
cd freeipmi-0.1.3
env CFLAGS="-I/usr/local/include" \
LDFLAGS="-L/usr/local/lib -largp" \
./configure
gmake all
# su to root
gmake install
mkdir -p /var/lib/freeipmi
chmod 0700 /var/lib/freeipmi
touch /var/lib/freeipmi/ipckey
|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
i386_set_ioperm has known issues on FreeBSD 5.x (bus errors on io port access), so this patch uses io(4) to access io ports by default. To enable using i386_set_ioperm instead of io(4) specify USE_IOPERM copmilation option at configure time:
Example:
env CFLAGS="-DUSE_IOPERM -I/usr/local/include" \
LDFLAGS="-L/usr/local/lib -largp" \
./configure
|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
GNU FreeIPMI works both in-band (with-in the system) and out-of-band
(over the network). Easiest way to test if your system has IPMI
support or if the installation is OK is through bmc-info
command.
Test if IPMI works:
ipmitest:~# bmc-info
Device ID: 20
Device Revision: 1
[SDR Support]
Firmware Revision: 1.32
[Device Available (normal operation)]
IPMI Version: 1.5
Additional Device Support:
[Sensor Device]
[SDR Repository Device]
[SEL Device]
[FRU Inventory Device]
[IPMB Event Receiver]
[Chassis Device]
Manufacturer ID: B000157h
Product ID: 1Bh
Aux Firmware Revision Info: 10011500h
Channel Information:
Channel No: 0
Medium Type: IPMB (I2C)
Protocol Type: IPMB-1.0
Channel No: 1
Medium Type: Asynch. Serial/Modem (RS-232)
Protocol Type: IPMB-1.0
Channel No: 3
Medium Type: PCI SMBus
Protocol Type: IPMI-SMBus
Channel No: 4
Medium Type: System Interface (KCS, SMIC, or BT)
Protocol Type: KCS
Channel No: 6
Medium Type: 802.3 LAN
Protocol Type: IPMB-1.0
Channel No: 7
Medium Type: 802.3 LAN
Protocol Type: IPMB-1.0
ipmitest:~#
|
If you don't get the expected response from bmc-info command,
please refer to Trouble-shooting.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The Core of GNU FreeIPMI system consists of LAN, KCS, SMIC system interface device drivers, all packaged in a single portable C library. Management applications can access the BMC at various levels using higher level IPMI command APIs or raw read/write interface to the driver.
Library internally uses SM BIOS and PCI drivers to locate the system interfaces.
You should note that all the device drivers are completely written in user-space. If you already have any in-kernel IPMI drivers loaded, unload them before you launch any GNU FreeIPMI utility. Otherwise there are no other prerequisites.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
ipmi-locate tool tries to probe and display
KCS/SMIC/BT/SSIF
IPMI device interface informations by using various probing
techniques. The tool also displays default values of IPMI
device interfaces of most commonly used in BMC
manufacturers. This tool may not probe on some machines, but FreeIPMI
tools work on them with default values. This behavior has been seen
in Tyan motherboard with SMDC card.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
www:~# ipmi-locate Probing KCS device using SMBIOS... done IPMI Version: 1.5 IPMI locate driver: SMBIOS IPMI locate driver: 0 IPMI interface: KCS BMC I2C device: (null) BMC I/O base address: CA2 Register space: 1 Probing SMIC device using SMBIOS... FAILED Probing BT device using SMBIOS... FAILED Probing SSIF device using SMBIOS... FAILED Probing KCS device using ACPI... FAILED Probing SMIC device using ACPI... FAILED Probing BT device using ACPI... FAILED Probing SSIF device using ACPI... FAILED Probing KCS device using PCI... FAILED Probing SMIC device using PCI... FAILED Probing BT device using PCI... FAILED Probing SSIF device using PCI... FAILED KCS device default values: IPMI Version: 1.5 IPMI locate driver: DEFAULT IPMI locate driver: 0 IPMI interface: KCS BMC I2C device: (null) BMC I/O base address: CA2 Register space: 1 SMIC device default values: IPMI Version: 1.5 IPMI locate driver: DEFAULT IPMI locate driver: 0 IPMI interface: SMIC BMC I2C device: (null) BMC I/O base address: CA9 Register space: 1 BT device default values: SSIF device default values: IPMI Version: 1.5 IPMI locate driver: DEFAULT IPMI locate driver: 0 IPMI interface: SSIF BMC I2C device: /dev/i2c-0 BMC SMBUS slave address: 20 Register space: 1 www:~# |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Fish provides shell, extension/plug-in and scripting interface. As a shell, User has access to both in-band and out-of-band access to the host BMC through a rich set of IPMI commands.
Experienced System Administrators can quickly add features or limitlessly customize the system using the extension interface in Scheme language. For example, Pushing System Event Log data to a MySQL server, Triggering alarm upon Platform Chassis Intrusion, Generating email for critical platform events like processor temperature above threshold limit or fan failure or memory errors.... In fact, most of the functionalities and commands of this shell are themselves implemented through Fish extensions.
| 5.1 Command-line arguments to fish | ||
| 5.2 Setting default startup options | Sample configuration file. | |
| 5.3 Invoking fish | Different ways to invoke fish. |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Fish can be customized to great extent using Scheme language interface. You should refer to guile for advanced options.
Example configuration file: `/usr/etc/fish/fish.scm'
;; fish.scm: default fish configuration scm
;; Customize Fish:
(fi-set-prompt! "fish# ")
;; Set driver SMS IO Base port
; (fi-set-sms-io-base! #x0CA2)
;; Set Driver Internals:
; (fi-set-default-driver-poll-interval 10)
;; Example Group Aliases
; (set! sensors-group-alias-list
; '(
; (mysystem . (Processor Fan "Power Supply" Current Memory Chassis))
; (power . ("Power Supply"))
; (security . ("Platform Chassis Intrusion Platform Security Violation"))
; ))
|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Fish takes (GNU getopt-long style) command-line arguments and starts
as a shell by default with a neat readline interface. You can type
fish commands at the prompt. Type `--help' to get
help on list of available commands and `quit' to exit the
shell.
www:~# fish
FreeIPMI Shell [fish-0.2.beta1]
Copyright (C) 2003-2005 FreeIPMI Core Team
This program is free software; you may redistribute it under the terms of
the GNU General Public License. This program has absolutely no warranty.
fish# help sensors
sensors [--no-probing] [--driver-type=IPMIDRIVER]
[--driver-address=DRIVERADDR] [--driver-device=DEVICE]
[--hostname=IPMIHOST] [--username=USERNAME]
[--password=PASSWORD] [--auth-type=AUTHTYPE]
[--priv-level=PRIVILEGE-LEVEL] [--verbose] [--sdr-info]
[--flush-cache] [--list-groups] [--all] [--group=GROUP]
[--sensors=SENSORS-LIST] [--help] [--usage] [--version]
Displays current readings of sensor chips through BMC.
fish# quit
www:~#
|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
To start fish as a script interpreter, you can either include script
header or invoke with fish with
`--script-file=SCRIPT-FILE' option.
Example fish self executable script:
#! /usr/sbin/fish -s !# (bmc-info-main (fi-command-line)) (display "bmc-info exited with [") (display bmc-info-exit-status) (display "] status\n") (fi-exit bmc-info-exit-status) |
Example invoking through command-line:
debian-ia64:~# fish --script-file=/root/work/fish-examples/bmc-info.scm
Device ID: 20
Device Revision: 1
[SDR Support]
Firmware Revision: 1.32
[Device Available (normal operation)]
IPMI Version: 1.5
Additional Device Support:
[Sensor Device]
[SDR Repository Device]
[SEL Device]
[FRU Inventory Device]
[IPMB Event Receiver]
[Chassis Device]
Manufacturer ID: B000157h
Product ID: 1Bh
Aux Firmware Revision Info: 10011500h
Channel Information:
Channel No: 0
Medium Type: IPMB (I2C)
Protocol Type: IPMB-1.0
Channel No: 1
Medium Type: Asynch. Serial/Modem (RS-232)
Protocol Type: IPMB-1.0
Channel No: 3
Medium Type: PCI SMBus
Protocol Type: IPMI-SMBus
Channel No: 4
Medium Type: System Interface (KCS, SMIC, or BT)
Protocol Type: KCS
Channel No: 6
Medium Type: 802.3 LAN
Protocol Type: IPMB-1.0
Channel No: 7
Medium Type: 802.3 LAN
Protocol Type: IPMB-1.0
bmc-info exited with 0 status
debian-ia64:~#
|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Fish extensions are like normal Scheme programming with additional built-in IPMI primitives and procedures. You should refer to guile to learn more about writing extensions.
Example fish extension:
This simple extension upon loading, will dynamically add
bmc-info command to the fish shell.
;;
;; bmc-info.scm: fish extension to get BMC information.
;;
(define (bmc-info args)
"Show BMC information"
(fi-kcs-get-dev-id-display))
(fi-register-command! '("bmc-info" "bmc-info\n\t- Show BMC Information."))
|
Example: Loading the above `bmc-info.scm' extension.
fish# load /root/work/fish-examples/bmc-info.scm
fish# help bmc-info
bmc-info
Shows BMC Information.
fish#
|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
A command line BMC configuration utility. You can view, set and replicate the configuration.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
bmc-config emits current BMC configuration settings to
stdout in the same format as that of configuration file, when no file
argument is specified.
Example: Extracting BMC configuration to stdout.
debian-ia64:~# bmc-config --checkout Section User1 ## Give username Username Anonymous ## Give password or leave it blank to clear password Password ## Possible values: Yes/No Lan_Enable_Ipmi_Msgs Yes ## Possible values: Yes/No Lan_Enable_Link_Auth Yes ## Possible values: Yes/No Lan_Enable_Restrict_To_Callback No ## Possible values: Callback/User/Operator/Administrator/OEM_Proprietary/No_Access Lan_Privilege_Limit User ## Give valid number Lan_Session_Limit 0 ## Possible values: Yes/No Serial_Enable_Ipmi_Msgs Yes ## Possible values: Yes/No Serial_Enable_Link_Auth Yes ## Possible values: Yes/No Serial_Enable_Restrict_To_Callback No ## Possible values: Callback/User/Operator/Administrator/OEM_Proprietary/No_Access Serial_Privilege_Limit User ## Give valid number Serial_Session_Limit 0 EndSection Section User2 ## Give username Username ipmiuser ## Give password or leave it blank to clear password Password ## Possible values: Yes/No Lan_Enable_Ipmi_Msgs Yes ## Possible values: Yes/No Lan_Enable_Link_Auth Yes ## Possible values: Yes/No Lan_Enable_Restrict_To_Callback No ## Possible values: Callback/User/Operator/Administrator/OEM_Proprietary/No_Access Lan_Privilege_Limit Administrator ## Give valid number Lan_Session_Limit 0 ## Possible values: Yes/No Serial_Enable_Ipmi_Msgs No ## Possible values: Yes/No Serial_Enable_Link_Auth No ## Possible values: Yes/No Serial_Enable_Restrict_To_Callback No ## Possible values: Callback/User/Operator/Administrator/OEM_Proprietary/No_Access Serial_Privilege_Limit No_Access ## Give valid number Serial_Session_Limit 0 EndSection Section User3 ## Give username Username operator ## Give password or leave it blank to clear password Password ## Possible values: Yes/No Lan_Enable_Ipmi_Msgs No ## Possible values: Yes/No Lan_Enable_Link_Auth No ## Possible values: Yes/No Lan_Enable_Restrict_To_Callback No ## Possible values: Callback/User/Operator/Administrator/OEM_Proprietary/No_Access Lan_Privilege_Limit No_Access ## Give valid number Lan_Session_Limit 0 ## Possible values: Yes/No Serial_Enable_Ipmi_Msgs No ## Possible values: Yes/No Serial_Enable_Link_Auth No ## Possible values: Yes/No Serial_Enable_Restrict_To_Callback No ## Possible values: Callback/User/Operator/Administrator/OEM_Proprietary/No_Access Serial_Privilege_Limit No_Access ## Give valid number Serial_Session_Limit 0 EndSection Section User4 ## Give username Username user ## Give password or leave it blank to clear password Password ## Possible values: Yes/No Lan_Enable_Ipmi_Msgs No ## Possible values: Yes/No Lan_Enable_Link_Auth No ## Possible values: Yes/No Lan_Enable_Restrict_To_Callback No ## Possible values: Callback/User/Operator/Administrator/OEM_Proprietary/No_Access Lan_Privilege_Limit No_Access ## Give valid number Lan_Session_Limit 0 ## Possible values: Yes/No Serial_Enable_Ipmi_Msgs No ## Possible values: Yes/No Serial_Enable_Link_Auth No ## Possible values: Yes/No Serial_Enable_Restrict_To_Callback No ## Possible values: Callback/User/Operator/Administrator/OEM_Proprietary/No_Access Serial_Privilege_Limit No_Access ## Give valid number Serial_Session_Limit 0 EndSection Section LAN_Channel ## Possible values: Disabled/Pre_Boot_Only/Always_Available/Shared Volatile_Access_Mode Always_Available ## Possible values: Yes/No Volatile_Enable_User_Level_Auth Yes ## Possible values: Yes/No Volatile_Enable_Per_Message_Auth No ## Possible values: Yes/No Volatile_Enable_Pef_Alerting No ## Possible values: Callback/User/Operator/Administrator/OEM_Proprietary/No_Access Volatile_Channel_Privilege_Limit User ## Possible values: Disabled/Pre_Boot_Only/Always_Available/Shared Non_Volatile_Access_Mode Always_Available ## Possible values: Yes/No Non_Volatile_Enable_User_Level_Auth Yes ## Possible values: Yes/No Non_Volatile_Enable_Per_Message_Auth No ## Possible values: Yes/No Non_Volatile_Enable_Pef_Alerting No ## Possible values: Callback/User/Operator/Administrator/OEM_Proprietary/No_Access Non_Volatile_Channel_Privilege_Limit User EndSection Section LAN_Conf ## Possible values: Unspecified/Static/Use_DHCP/Use_BIOS/Use_Others Ip_Address_Source Static ## Give valid IP Address Ip_Address 192.168.1.60 ## Give valid MAC Address Mac_Address 00:0E:0C:21:81:B4 ## Give valid Subnet mask Subnet_Mask 255.255.255.0 ## Give valid IP Address Default_Gateway_Ip_Address 192.168.1.1 ## Give valid MAC Address Default_Gateway_Mac_Address 00:00:00:00:00:00 ## Give valid IP Address Backup_Gateway_Ip_Address 192.168.1.1 ## Give valid MAC Address Backup_Gateway_Mac_Address 00:00:00:00:00:00 EndSection Section LAN_Conf_Auth ## Possible values: Yes/No Callback_Enable_Auth_Type_None No ## Possible values: Yes/No Callback_Enable_Auth_Type_Md2 Yes ## Possible values: Yes/No Callback_Enable_Auth_Type_Md5 Yes ## Possible values: Yes/No Callback_Enable_Auth_Type_Straight_Password Yes ## Possible values: Yes/No Callback_Enable_Auth_Type_Oem_Proprietary No ## Possible values: Yes/No User_Enable_Auth_Type_None No ## Possible values: Yes/No User_Enable_Auth_Type_Md2 Yes ## Possible values: Yes/No User_Enable_Auth_Type_Md5 Yes ## Possible values: Yes/No User_Enable_Auth_Type_Straight_Password Yes ## Possible values: Yes/No User_Enable_Auth_Type_Oem_Proprietary No ## Possible values: Yes/No Operator_Enable_Auth_Type_None No ## Possible values: Yes/No Operator_Enable_Auth_Type_Md2 Yes ## Possible values: Yes/No Operator_Enable_Auth_Type_Md5 Yes ## Possible values: Yes/No Operator_Enable_Auth_Type_Straight_Password Yes ## Possible values: Yes/No Operator_Enable_Auth_Type_Oem_Proprietary No ## Possible values: Yes/No Admin_Enable_Auth_Type_None No ## Possible values: Yes/No Admin_Enable_Auth_Type_Md2 Yes ## Possible values: Yes/No Admin_Enable_Auth_Type_Md5 Yes ## Possible values: Yes/No Admin_Enable_Auth_Type_Straight_Password Yes ## Possible values: Yes/No Admin_Enable_Auth_Type_Oem_Proprietary No ## Possible values: Yes/No Oem_Enable_Auth_Type_None No ## Possible values: Yes/No Oem_Enable_Auth_Type_Md2 No ## Possible values: Yes/No Oem_Enable_Auth_Type_Md5 No ## Possible values: Yes/No Oem_Enable_Auth_Type_Straight_Password No ## Possible values: Yes/No Oem_Enable_Auth_Type_Oem_Proprietary No EndSection Section LAN_Conf_Misc ## Possible values: Yes/No Enable_Gratuitous_Arps Yes ## Possible values: Yes/No Enable_Arp_Response No ## Give valid number Gratuitous_Arp_Interval 4 EndSection Section Serial_Channel ## Possible values: Disabled/Pre_Boot_Only/Always_Available/Shared Volatile_Access_Mode Always_Available ## Possible values: Yes/No Volatile_Enable_User_Level_Auth Yes ## Possible values: Yes/No Volatile_Enable_Per_Message_Auth No ## Possible values: Yes/No Volatile_Enable_Pef_Alerting No ## Possible values: Callback/User/Operator/Administrator/OEM_Proprietary/No_Access Volatile_Channel_Privilege_Limit User ## Possible values: Disabled/Pre_Boot_Only/Always_Available/Shared Non_Volatile_Access_Mode Always_Available ## Possible values: Yes/No Non_Volatile_Enable_User_Level_Auth Yes ## Possible values: Yes/No Non_Volatile_Enable_Per_Message_Auth No ## Possible values: Yes/No Non_Volatile_Enable_Pef_Alerting No ## Possible values: Callback/User/Operator/Administrator/OEM_Proprietary/No_Access Non_Volatile_Channel_Privilege_Limit User EndSection Section Serial_Conf ## Possible values: Yes/No Enable_Basic_Mode Yes ## Possible values: Yes/No Enable_Ppp_Mode Yes ## Possible values: Yes/No Enable_Terminal_Mode No ## Possible Values: Modem_Connect/Direct_Connect Connect_Mode Direct_Connect ## Give valid number Page_Blackout_Interval 0 ## Give valid number Call_Retry_Time 60 ## Possible values: Yes/No Enable_Dtr_Hangup Yes ## Possible values: No_Flow_Control/RTS_CTS/XON_XOFF Flow_Control No_Flow_Control ## Possible values: 9600/19200/38400/57600/115200 Bit_Rate 115200 EndSection Section Misc ## Possible Values: Off_State_AC_Apply/Restore_State_AC_Apply/On_State_AC_Apply Power_Restore_Policy Restore_State_Ac_Apply EndSection debian-ia64:~# |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
`checkout" option generates a configuration file containing the current BMC settings. Configuration file is in plain text format with sections enclosing key-value pairs. Comments will guide you to choose appropriate values. Use your favorite editor (like GNU Emacs) to edit these fields. Comment character is `#'.
Example: Creating a BMC configuration file.
debian-ia64:~# bmc-config --checkout --filename=/tmp/bmc.conf |
Alternatively you can redirect stdout to the configuration file too.
debian-ia64:~# bmc-config --checkout > /tmp/bmc.conf |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
After customizing the BMC configuration file, you can update the BMC configuration using "commit" option.
Example using configuration file:
debian-ia64:~# bmc-config --commit -f /tmp/bmc.conf |
Example using a specific key:
debian-ia64:~# bmc-config --commit -k "LAN_conf:Ip_Address=192.168.1.60" |
Note: At this point of time, configuration settings can only be fed through a file or key-value pairs and not stdin.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
To compare the differences between current active BMC settings and the configuration file, use "diff" option
Example: Comparing the configuration file and BMC settings.
debian-ia64:~# bmc-config --diff -f /tmp/bmc.conf USER:Ip_Address=192.168.10.160 BMC :Ip_Address=192.168.1.60 differs USER:Default_Gateway_Ip_Address=192.168.10.1 BMC :Default_Gateway_Ip_Address=192.168.1.1 differs USER:Backup_Gateway_Ip_Address=192.168.10.1 BMC :Backup_Gateway_Ip_Address=192.168.1.1 differs debian-ia64:~# bmc-config --diff -k "User2:Username=guest" USER:Username=guest BMC :Username=ipmiuser differs debian-ia64:~# |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
bmc-config checkout in out-of-band may fail to retrieve some
BMC configuration options, because of default USER privilege level.
For such cases, use ADMIN privilege level.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
bmc-info command displays BMC/IPMI version information and
the list of additional devices supported. This command is mostly used
for checking if IPMI is supported or if BMC/FRU/SDR firmware upgrade
completed successfully.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
ipmitest:~# bmc-info
Device ID: 20
Device Revision: 1
[SDR Support]
Firmware Revision: 1.32
[Device Available (normal operation)]
IPMI Version: 1.5
Additional Device Support:
[Sensor Device]
[SDR Repository Device]
[SEL Device]
[FRU Inventory Device]
[IPMB Event Receiver]
[Chassis Device]
Manufacturer ID: B000157h
Product ID: 1Bh
Aux Firmware Revision Info: 10011500h
Channel Information:
Channel No: 0
Medium Type: IPMB (I2C)
Protocol Type: IPMB-1.0
Channel No: 1
Medium Type: Asynch. Serial/Modem (RS-232)
Protocol Type: IPMB-1.0
Channel No: 3
Medium Type: PCI SMBus
Protocol Type: IPMI-SMBus
Channel No: 4
Medium Type: System Interface (KCS, SMIC, or BT)
Protocol Type: KCS
Channel No: 6
Medium Type: 802.3 LAN
Protocol Type: IPMB-1.0
Channel No: 7
Medium Type: 802.3 LAN
Protocol Type: IPMB-1.0
ipmitest:~#
|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
bmc-autoconfig utility is a wizard-like frontend to the
bmc-config command, which has a curses/text based interfaced
questionaire asking for IP/Netmask/Gateway to be committed.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
ipmi-raw tool reads hex values of IPMI command
request data from standard input, executes it and displays hex values
of IPMI command response data. This tool works on in-band
and out-of-band.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
www:~# ipmi-raw 18 01 rcvd: 1C 01 00 20 81 01 20 51 9F 57 01 00 1B 00 00 15 01 10 www:~# |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
ipmi-sensors utility reports the monitored system health
information, such as temperatures and voltages, fan status, etc with
nominal, threshold max/min readings and status descriptions.
| 10.1 command-line arguments | Command-line arguments. | |
| 10.2 Setting default startup options | Sample configuration file. | |
| 10.3 ipmi-sensors in action | Examples. |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Example ipmi-sensors-conf.scm file:
;;; file: /usr/etc/fish/ipmi-sensors-conf.scm
;; ipmi-sensors-conf.scm: sensors configuration file
;; Sensors cache filename
; (set! sensors-sdr-cache-file "/path/to/cache-filename")
;; Example: Ignore these sensors
; (sensors-ignore! '(54 55 88))
;; Example: Group Aliases
(sensors-group-alias-list-append!
'(
; (mysystem . ("Processor" "Fan" "Power Supply" "Current Memory Chassis"))
(power . ("Power Supply"))
(security . ("Platform Chassis Intrusion" "Platform Security Violation"))
))
|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
CDC 6440 (A.K.A SR870BN4) - a Quad Itanium2 system has 136 sensors on board. GNU FreeIPMI running on Thunder supercomputer monitors 139264 sensors in total.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
www:~# ipmi-sensors 1: Power Unit (Power Unit): [OK] 2: BMC Watchdog (Watchdog 2): [OK] 3: Scrty Violation (Platform Security Violation): [OK] 4: Physical Scrty (Platform Chassis Intrusion): [LAN Leash Lost (system is unplugged from LAN)] 5: POST Error (System Firmware): [OK] 6: Critical Int (Critical Interrupt): [OK] 7: Memory (Memory): [OK] 8: Logging Disabled (Event Logging Disabled): [OK] 9: Baseboard 1.2V (Voltage): 1.2054 V (1.0682/1.3328): [OK] 10: Baseboard 1.25V (Voltage): 1.2642 V (1.0192/1.4896): [OK] 11: Baseboard 1.8V (Voltage): 1.7901 V (1.6029/1.9773): [OK] 12: Baseboard 1.8VSB (Voltage): 1.8135 V (1.6029/1.9773): [OK] 13: Baseboard 2.5V (Voltage): 2.5155 V (2.1645/2.8314): [OK] 14: Baseboard 3.3V (Voltage): 3.36 V (2.9925/3.64): [OK] 15: Baseboard 3.3AUX (Voltage): 3.3089 V (2.9232/3.6946): [OK] 16: Baseboard 5.0V (Voltage): 4.966 V (4.524/5.486): [OK] 17: Baseboard 5VSB (Voltage): 5.076 V (4.4415/5.6165): [OK] 18: Baseboard 12V (Voltage): 12.028 V (10.788/13.082): [OK] 19: Baseboard 12VRM (Voltage): 12.028 V (10.602/13.392): [OK] 20: Baseboard -12V (Voltage): -12.04 V (-13.84/-10.456): [OK] 21: Baseboard VBAT (Voltage): 3.069 V (2.6815/3.627): [OK] 22: Baseboard Temp (Temperature): 39.0 C (5.0/65.0): [OK] 23: FntPnl Amb Temp (Temperature): 22.0 C (5.0/45.0): [OK] 24: Basebrd FanBoost (OEM Reserved): 39.0 C (NA/NA): [OK] 25: FP Amb FanBoost (OEM Reserved): 22.0 C (NA/NA): [OK] 26: Baseboard Fan 1 (Fan): 5661.0 RPM (2703.0/NA): [OK] 27: Baseboard Fan 2 (Fan): 5661.0 RPM (2703.0/NA): [OK] 28: Baseboard Fan 3 (Fan): 5763.0 RPM (2703.0/NA): [OK] 29: Baseboard Fan 4 (Fan): 5559.0 RPM (2703.0/NA): [OK] 30: SCSI A Term Pwr (Voltage): 4.06 V (3.2/NA): [OK] 31: SCSI B Term Pwr (Voltage): 4.04 V (3.2/NA): [OK] 32: Power Supply 1 (Power Supply): [Presence detected] 33: Power Cage Fan (Fan): 6720.0 RPM (4500.0/NA): [OK] 34: Power Cage Temp (Temperature): 34.0 C (-10.0/65.0): [OK] 35: PwrCage FanBoost (OEM Reserved): 34.0 C (NA/NA): [OK] 36: Proc Missing (Board): [OK] 37: ACPI State (ACPI Power State): [S0/G0 "working"] 38: System Event (System Event): [OK] 39: Button (Button): [OK] 40: SMI Timeout (OEM Reserved): [OK] 41: Sensor Failure (OEM Reserved): [OEM State = 0000h] 42: NMI State (OEM Reserved): [OK] 43: SMI State (OEM Reserved): [OK] 44: FSB Mismatch (OEM Reserved): [OK] 45: Processor 1 Stat (Processor): [Processor Presence detected] 46: Processor 2 Stat (Processor): [Processor Presence detected] 47: Processor1 Temp (Temperature): 37.0 C (-10.0/80.0): [OK] 48: Processor2 Temp (Temperature): 39.0 C (-10.0/80.0): [OK] 49: Proc1 FanBoost (OEM Reserved): 37.0 C (NA/NA): [OK] 50: Proc2 FanBoost (OEM Reserved): 39.0 C (NA/NA): [OK] 51: Processor Vccp (Voltage): 1.4976 V (1.0296/1.9422): [OK] 52: CPU Therm Ctrl (Temperature): [State Deasserted] 53: DIMM 1B (Slot Connector): [Slot/Connector Device installed/attached] 54: DIMM 1A (Slot Connector): [Slot/Connector Device installed/attached] 55: DIMM 2B (Slot Connector): [OK] 56: DIMM 2A (Slot Connector): [OK] 57: DIMM 3B (Slot Connector): [OK] 58: DIMM 3A (Slot Connector): [OK] 59: Hot Swap Temp (Temperature): NA (NA/NA): [Unknown] 60: HSC Drv Status (Drive Slot): [Unknown] 61: HSC Drv Presence (Drive Slot): [Unknown] www:~# |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
www:~# ipmi-sensors -vv Record ID: 1 Record Type: 02h Sensor Name: Power Unit Group Name: Power Unit Sensor Number: 1 Slave Address/System Software ID: 10h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [OK] Record ID: 2 Record Type: 02h Sensor Name: BMC Watchdog Group Name: Watchdog 2 Sensor Number: 3 Slave Address/System Software ID: 10h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [OK] Record ID: 3 Record Type: 02h Sensor Name: Scrty Violation Group Name: Platform Security Violation Sensor Number: 4 Slave Address/System Software ID: 10h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [OK] Record ID: 4 Record Type: 02h Sensor Name: Physical Scrty Group Name: Platform Chassis Intrusion Sensor Number: 5 Slave Address/System Software ID: 10h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [LAN Leash Lost (system is unplugged from LAN)] Record ID: 5 Record Type: 02h Sensor Name: POST Error Group Name: System Firmware Sensor Number: 6 Slave Address/System Software ID: 10h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [OK] Record ID: 6 Record Type: 02h Sensor Name: Critical Int Group Name: Critical Interrupt Sensor Number: 7 Slave Address/System Software ID: 10h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [OK] Record ID: 7 Record Type: 02h Sensor Name: Memory Group Name: Memory Sensor Number: 8 Slave Address/System Software ID: 10h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [OK] Record ID: 8 Record Type: 02h Sensor Name: Logging Disabled Group Name: Event Logging Disabled Sensor Number: 9 Slave Address/System Software ID: 10h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [OK] Record ID: 9 Record Type: 01h Sensor Name: Baseboard 1.2V Group Name: Voltage Sensor Number: 16 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 98 R Exponent: -4 B Exponent: 2 Linear: 64 Analog Data Format: 0 Lower Critical Threshold: 1.0682 Volts Upper Critical Threshold: 1.3328 Volts Lower Non-Critical Threshold: 1.0976 Volts Upper Non-Critical Threshold: 1.2936 Volts Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: 0.0 Volts Sensor Max. Reading: 2.499 Volts Normal Min.: 1.1368 Volts Normal Max.: 1.2544 Volts Nominal reading: 1.1956 Volts Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 1.2054 Volts Sensor Status: [OK] Record ID: 10 Record Type: 01h Sensor Name: Baseboard 1.25V Group Name: Voltage Sensor Number: 17 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 98 R Exponent: -4 B Exponent: 2 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: 1.0192 Volts Upper Critical Threshold: 1.4896 Volts Lower Non-Critical Threshold: 1.0486 Volts Upper Non-Critical Threshold: 1.4504 Volts Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: 0.0 Volts Sensor Max. Reading: 2.499 Volts Normal Min.: 1.078 Volts Normal Max.: 1.4112 Volts Nominal reading: 1.2446 Volts Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 1.2642 Volts Sensor Status: [OK] Record ID: 11 Record Type: 01h Sensor Name: Baseboard 1.8V Group Name: Voltage Sensor Number: 18 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 117 R Exponent: -4 B Exponent: 2 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: 1.6029 Volts Upper Critical Threshold: 1.9773 Volts Lower Non-Critical Threshold: 1.6497 Volts Upper Non-Critical Threshold: 1.9188 Volts Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: 0.0 Volts Sensor Max. Reading: 2.9835 Volts Normal Min.: 1.6965 Volts Normal Max.: 1.872 Volts Nominal reading: 1.7901 Volts Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 1.7901 Volts Sensor Status: [OK] Record ID: 12 Record Type: 01h Sensor Name: Baseboard 1.8VSB Group Name: Voltage Sensor Number: 19 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 117 R Exponent: -4 B Exponent: 2 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: 1.6029 Volts Upper Critical Threshold: 1.9773 Volts Lower Non-Critical Threshold: 1.6497 Volts Upper Non-Critical Threshold: 1.9188 Volts Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: 0.0 Volts Sensor Max. Reading: 2.9835 Volts Normal Min.: 1.6965 Volts Normal Max.: 1.872 Volts Nominal reading: 1.7901 Volts Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 1.8135 Volts Sensor Status: [OK] Record ID: 13 Record Type: 01h Sensor Name: Baseboard 2.5V Group Name: Voltage Sensor Number: 20 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 117 R Exponent: -4 B Exponent: 2 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: 2.1645 Volts Upper Critical Threshold: 2.8314 Volts Lower Non-Critical Threshold: 2.223 Volts Upper Non-Critical Threshold: 2.7378 Volts Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: 0.0 Volts Sensor Max. Reading: 2.9835 Volts Normal Min.: 2.2815 Volts Normal Max.: 2.6793 Volts Nominal reading: 2.4804 Volts Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 2.5155 Volts Sensor Status: [OK] Record ID: 14 Record Type: 01h Sensor Name: Baseboard 3.3V Group Name: Voltage Sensor Number: 21 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 175 R Exponent: -4 B Exponent: 2 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: 2.9925 Volts Upper Critical Threshold: 3.64 Volts Lower Non-Critical Threshold: 3.08 Volts Upper Non-Critical Threshold: 3.535 Volts Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: 0.0 Volts Sensor Max. Reading: 4.4625 Volts Normal Min.: 3.15 Volts Normal Max.: 3.4475 Volts Nominal reading: 3.29 Volts Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 3.36 Volts Sensor Status: [OK] Record ID: 15 Record Type: 01h Sensor Name: Baseboard 3.3AUX Group Name: Voltage Sensor Number: 22 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 203 R Exponent: -4 B Exponent: 2 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: 2.9232 Volts Upper Critical Threshold: 3.6946 Volts Lower Non-Critical Threshold: 3.0044 Volts Upper Non-Critical Threshold: 3.5931 Volts Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: 0.0 Volts Sensor Max. Reading: 5.1765 Volts Normal Min.: 3.1465 Volts Normal Max.: 3.451 Volts Nominal reading: 3.2886 Volts Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 3.3089 Volts Sensor Status: [OK] Record ID: 16 Record Type: 01h Sensor Name: Baseboard 5.0V Group Name: Voltage Sensor Number: 23 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 26 R Exponent: -3 B Exponent: 2 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: 4.524 Volts Upper Critical Threshold: 5.486 Volts Lower Non-Critical Threshold: 4.68 Volts Upper Non-Critical Threshold: 5.33 Volts Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: 0.0 Volts Sensor Max. Reading: 6.63 Volts Normal Min.: 4.784 Volts Normal Max.: 5.226 Volts Nominal reading: 4.966 Volts Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 4.966 Volts Sensor Status: [OK] Record ID: 17 Record Type: 01h Sensor Name: Baseboard 5VSB Group Name: Voltage Sensor Number: 24 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 235 R Exponent: -4 B Exponent: 2 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: 4.4415 Volts Upper Critical Threshold: 5.6165 Volts Lower Non-Critical Threshold: 4.5825 Volts Upper Non-Critical Threshold: 5.452 Volts Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: 0.0 Volts Sensor Max. Reading: 5.9925 Volts Normal Min.: 4.794 Volts Normal Max.: 5.2405 Volts Nominal reading: 4.982 Volts Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 5.076 Volts Sensor Status: [OK] Record ID: 18 Record Type: 01h Sensor Name: Baseboard 12V Group Name: Voltage Sensor Number: 25 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 62 R Exponent: -3 B Exponent: 2 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: 10.788 Volts Upper Critical Threshold: 13.082 Volts Lower Non-Critical Threshold: 11.16 Volts Upper Non-Critical Threshold: 12.71 Volts Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: 0.0 Volts Sensor Max. Reading: 15.81 Volts Normal Min.: 11.408 Volts Normal Max.: 12.462 Volts Nominal reading: 11.842 Volts Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 12.028 Volts Sensor Status: [OK] Record ID: 19 Record Type: 01h Sensor Name: Baseboard 12VRM Group Name: Voltage Sensor Number: 26 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 62 R Exponent: -3 B Exponent: 2 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: 10.602 Volts Upper Critical Threshold: 13.392 Volts Lower Non-Critical Threshold: 10.912 Volts Upper Non-Critical Threshold: 12.958 Volts Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: 0.0 Volts Sensor Max. Reading: 15.81 Volts Normal Min.: 11.408 Volts Normal Max.: 12.462 Volts Nominal reading: 11.904 Volts Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 12.028 Volts Sensor Status: [OK] Record ID: 20 Record Type: 01h Sensor Name: Baseboard -12V Group Name: Voltage Sensor Number: 27 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: -160 M: 72 R Exponent: -3 B Exponent: 2 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: -13.84 Volts Upper Critical Threshold: -10.456 Volts Lower Non-Critical Threshold: -13.408 Volts Upper Non-Critical Threshold: -10.744 Volts Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: -16.0 Volts Sensor Max. Reading: 2.36 Volts Normal Min.: -12.616 Volts Normal Max.: -10.96 Volts Nominal reading: -12.04 Volts Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: -12.04 Volts Sensor Status: [OK] Record ID: 21 Record Type: 01h Sensor Name: Baseboard VBAT Group Name: Voltage Sensor Number: 28 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 155 R Exponent: -4 B Exponent: 2 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: 2.6815 Volts Upper Critical Threshold: 3.627 Volts Lower Non-Critical Threshold: 2.759 Volts Upper Non-Critical Threshold: 3.5185 Volts Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: 0.0 Volts Sensor Max. Reading: 3.9525 Volts Normal Min.: 2.8365 Volts Normal Max.: 3.441 Volts Nominal reading: 2.976 Volts Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 3.069 Volts Sensor Status: [OK] Record ID: 22 Record Type: 01h Sensor Name: Baseboard Temp Group Name: Temperature Sensor Number: 48 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 1 R Exponent: 0 B Exponent: 0 Linear: 0 Analog Data Format: 2 Lower Critical Threshold: 5.0 Degrees C Upper Critical Threshold: 65.0 Degrees C Lower Non-Critical Threshold: 10.0 Degrees C Upper Non-Critical Threshold: 60.0 Degrees C Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: -128.0 Degrees C Sensor Max. Reading: 127.0 Degrees C Normal Min.: 10.0 Degrees C Normal Max.: 55.0 Degrees C Nominal reading: 38.0 Degrees C Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 39.0 Degrees C Sensor Status: [OK] Record ID: 23 Record Type: 01h Sensor Name: FntPnl Amb Temp Group Name: Temperature Sensor Number: 50 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 1 R Exponent: 0 B Exponent: 0 Linear: 0 Analog Data Format: 2 Lower Critical Threshold: 5.0 Degrees C Upper Critical Threshold: 45.0 Degrees C Lower Non-Critical Threshold: 10.0 Degrees C Upper Non-Critical Threshold: 40.0 Degrees C Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: -128.0 Degrees C Sensor Max. Reading: 127.0 Degrees C Normal Min.: 10.0 Degrees C Normal Max.: 30.0 Degrees C Nominal reading: 25.0 Degrees C Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 22.0 Degrees C Sensor Status: [OK] Record ID: 24 Record Type: 01h Sensor Name: Basebrd FanBoost Group Name: OEM Reserved Sensor Number: 51 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 1 R Exponent: 0 B Exponent: 0 Linear: 0 Analog Data Format: 2 Lower Critical Threshold: NA Upper Critical Threshold: NA Lower Non-Critical Threshold: NA Upper Non-Critical Threshold: 60.0 Degrees C Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: -128.0 Degrees C Sensor Max. Reading: 127.0 Degrees C Normal Min.: 5.0 Degrees C Normal Max.: 55.0 Degrees C Nominal reading: 38.0 Degrees C Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 39.0 Degrees C Sensor Status: [OK] Record ID: 25 Record Type: 01h Sensor Name: FP Amb FanBoost Group Name: OEM Reserved Sensor Number: 54 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 1 R Exponent: 0 B Exponent: 0 Linear: 0 Analog Data Format: 2 Lower Critical Threshold: NA Upper Critical Threshold: NA Lower Non-Critical Threshold: NA Upper Non-Critical Threshold: 40.0 Degrees C Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: -128.0 Degrees C Sensor Max. Reading: 127.0 Degrees C Normal Min.: 5.0 Degrees C Normal Max.: 30.0 Degrees C Nominal reading: 25.0 Degrees C Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 22.0 Degrees C Sensor Status: [OK] Record ID: 26 Record Type: 01h Sensor Name: Baseboard Fan 1 Group Name: Fan Sensor Number: 64 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 51 R Exponent: 0 B Exponent: 0 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: 2703.0 RPM Upper Critical Threshold: NA Lower Non-Critical Threshold: 2856.0 RPM Upper Non-Critical Threshold: NA Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: 0.0 RPM Sensor Max. Reading: 13005.0 RPM Normal Min.: 4488.0 RPM Normal Max.: 5610.0 RPM Nominal reading: 4998.0 RPM Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 5661.0 RPM Sensor Status: [OK] Record ID: 27 Record Type: 01h Sensor Name: Baseboard Fan 2 Group Name: Fan Sensor Number: 65 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 51 R Exponent: 0 B Exponent: 0 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: 2703.0 RPM Upper Critical Threshold: NA Lower Non-Critical Threshold: 2856.0 RPM Upper Non-Critical Threshold: NA Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: 0.0 RPM Sensor Max. Reading: 13005.0 RPM Normal Min.: 4488.0 RPM Normal Max.: 5610.0 RPM Nominal reading: 4998.0 RPM Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 5355.0 RPM Sensor Status: [OK] Record ID: 28 Record Type: 01h Sensor Name: Baseboard Fan 3 Group Name: Fan Sensor Number: 66 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 51 R Exponent: 0 B Exponent: 0 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: 2703.0 RPM Upper Critical Threshold: NA Lower Non-Critical Threshold: 2856.0 RPM Upper Non-Critical Threshold: NA Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: 0.0 RPM Sensor Max. Reading: 13005.0 RPM Normal Min.: 4488.0 RPM Normal Max.: 5610.0 RPM Nominal reading: 4998.0 RPM Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 5661.0 RPM Sensor Status: [OK] Record ID: 29 Record Type: 01h Sensor Name: Baseboard Fan 4 Group Name: Fan Sensor Number: 67 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 51 R Exponent: 0 B Exponent: 0 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: 2703.0 RPM Upper Critical Threshold: NA Lower Non-Critical Threshold: 2856.0 RPM Upper Non-Critical Threshold: NA Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: 0.0 RPM Sensor Max. Reading: 13005.0 RPM Normal Min.: 4488.0 RPM Normal Max.: 5610.0 RPM Nominal reading: 4998.0 RPM Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 5559.0 RPM Sensor Status: [OK] Record ID: 30 Record Type: 01h Sensor Name: SCSI A Term Pwr Group Name: Voltage Sensor Number: 96 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 20 R Exponent: -3 B Exponent: 0 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: 3.2 Volts Upper Critical Threshold: NA Lower Non-Critical Threshold: NA Upper Non-Critical Threshold: NA Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: 0.0 Volts Sensor Max. Reading: 5.1 Volts Normal Min.: 3.84 Volts Normal Max.: 4.32 Volts Nominal reading: 4.08 Volts Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 4.06 Volts Sensor Status: [OK] Record ID: 31 Record Type: 01h Sensor Name: SCSI B Term Pwr Group Name: Voltage Sensor Number: 97 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 20 R Exponent: -3 B Exponent: 0 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: 3.2 Volts Upper Critical Threshold: NA Lower Non-Critical Threshold: NA Upper Non-Critical Threshold: NA Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: 0.0 Volts Sensor Max. Reading: 5.1 Volts Normal Min.: 3.84 Volts Normal Max.: 4.32 Volts Nominal reading: 4.08 Volts Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 4.04 Volts Sensor Status: [OK] Record ID: 32 Record Type: 02h Sensor Name: Power Supply 1 Group Name: Power Supply Sensor Number: 112 Slave Address/System Software ID: 10h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [Presence detected] Record ID: 33 Record Type: 01h Sensor Name: Power Cage Fan Group Name: Fan Sensor Number: 115 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 60 R Exponent: 0 B Exponent: 0 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: 4500.0 RPM Upper Critical Threshold: NA Lower Non-Critical Threshold: 4980.0 RPM Upper Non-Critical Threshold: NA Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: 0.0 RPM Sensor Max. Reading: 15300.0 RPM Normal Min.: 6000.0 RPM Normal Max.: 9540.0 RPM Nominal reading: 8220.0 RPM Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 6720.0 RPM Sensor Status: [OK] Record ID: 34 Record Type: 01h Sensor Name: Power Cage Temp Group Name: Temperature Sensor Number: 118 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 1 R Exponent: 0 B Exponent: 0 Linear: 0 Analog Data Format: 2 Lower Critical Threshold: -10.0 Degrees C Upper Critical Threshold: 65.0 Degrees C Lower Non-Critical Threshold: -1.0 Degrees C Upper Non-Critical Threshold: 60.0 Degrees C Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: -128.0 Degrees C Sensor Max. Reading: 127.0 Degrees C Normal Min.: 5.0 Degrees C Normal Max.: 55.0 Degrees C Nominal reading: 40.0 Degrees C Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 34.0 Degrees C Sensor Status: [OK] Record ID: 35 Record Type: 01h Sensor Name: PwrCage FanBoost Group Name: OEM Reserved Sensor Number: 119 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 1 R Exponent: 0 B Exponent: 0 Linear: 0 Analog Data Format: 2 Lower Critical Threshold: NA Upper Critical Threshold: NA Lower Non-Critical Threshold: NA Upper Non-Critical Threshold: 60.0 Degrees C Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: -128.0 Degrees C Sensor Max. Reading: 127.0 Degrees C Normal Min.: 5.0 Degrees C Normal Max.: 55.0 Degrees C Nominal reading: 40.0 Degrees C Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 34.0 Degrees C Sensor Status: [OK] Record ID: 36 Record Type: 02h Sensor Name: Proc Missing Group Name: Board Sensor Number: 128 Slave Address/System Software ID: 10h Event/Reading Type Code: 03h Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [OK] Record ID: 37 Record Type: 02h Sensor Name: ACPI State Group Name: ACPI Power State Sensor Number: 130 Slave Address/System Software ID: 10h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [S0/G0 "working"] Record ID: 38 Record Type: 02h Sensor Name: System Event Group Name: System Event Sensor Number: 131 Slave Address/System Software ID: 10h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [OK] Record ID: 39 Record Type: 02h Sensor Name: Button Group Name: Button Sensor Number: 132 Slave Address/System Software ID: 10h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [OK] Record ID: 40 Record Type: 02h Sensor Name: SMI Timeout Group Name: OEM Reserved Sensor Number: 133 Slave Address/System Software ID: 10h Event/Reading Type Code: 03h Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [OK] Record ID: 41 Record Type: 02h Sensor Name: Sensor Failure Group Name: OEM Reserved Sensor Number: 134 Slave Address/System Software ID: 10h Event/Reading Type Code: 73h Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [OEM State = 0000h] Record ID: 42 Record Type: 02h Sensor Name: NMI State Group Name: OEM Reserved Sensor Number: 135 Slave Address/System Software ID: 10h Event/Reading Type Code: 03h Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [OK] Record ID: 43 Record Type: 02h Sensor Name: SMI State Group Name: OEM Reserved Sensor Number: 136 Slave Address/System Software ID: 10h Event/Reading Type Code: 03h Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [OK] Record ID: 44 Record Type: 02h Sensor Name: FSB Mismatch Group Name: OEM Reserved Sensor Number: 137 Slave Address/System Software ID: 10h Event/Reading Type Code: 03h Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [OK] Record ID: 45 Record Type: 02h Sensor Name: Processor 1 Stat Group Name: Processor Sensor Number: 144 Slave Address/System Software ID: 10h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [Processor Presence detected] Record ID: 46 Record Type: 02h Sensor Name: Processor 2 Stat Group Name: Processor Sensor Number: 145 Slave Address/System Software ID: 10h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [Processor Presence detected] Record ID: 47 Record Type: 01h Sensor Name: Processor1 Temp Group Name: Temperature Sensor Number: 152 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 1 R Exponent: 0 B Exponent: 0 Linear: 0 Analog Data Format: 2 Lower Critical Threshold: -10.0 Degrees C Upper Critical Threshold: 80.0 Degrees C Lower Non-Critical Threshold: 0.0 Degrees C Upper Non-Critical Threshold: 75.0 Degrees C Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: -128.0 Degrees C Sensor Max. Reading: 127.0 Degrees C Normal Min.: 5.0 Degrees C Normal Max.: 59.0 Degrees C Nominal reading: 47.0 Degrees C Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 37.0 Degrees C Sensor Status: [OK] Record ID: 48 Record Type: 01h Sensor Name: Processor2 Temp Group Name: Temperature Sensor Number: 153 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 1 R Exponent: 0 B Exponent: 0 Linear: 0 Analog Data Format: 2 Lower Critical Threshold: -10.0 Degrees C Upper Critical Threshold: 80.0 Degrees C Lower Non-Critical Threshold: 0.0 Degrees C Upper Non-Critical Threshold: 75.0 Degrees C Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: -128.0 Degrees C Sensor Max. Reading: 127.0 Degrees C Normal Min.: 5.0 Degrees C Normal Max.: 59.0 Degrees C Nominal reading: 47.0 Degrees C Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 39.0 Degrees C Sensor Status: [OK] Record ID: 49 Record Type: 01h Sensor Name: Proc1 FanBoost Group Name: OEM Reserved Sensor Number: 160 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 1 R Exponent: 0 B Exponent: 0 Linear: 0 Analog Data Format: 2 Lower Critical Threshold: NA Upper Critical Threshold: NA Lower Non-Critical Threshold: NA Upper Non-Critical Threshold: 75.0 Degrees C Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: -128.0 Degrees C Sensor Max. Reading: 127.0 Degrees C Normal Min.: 5.0 Degrees C Normal Max.: 59.0 Degrees C Nominal reading: 47.0 Degrees C Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 37.0 Degrees C Sensor Status: [OK] Record ID: 50 Record Type: 01h Sensor Name: Proc2 FanBoost Group Name: OEM Reserved Sensor Number: 161 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 1 R Exponent: 0 B Exponent: 0 Linear: 0 Analog Data Format: 2 Lower Critical Threshold: NA Upper Critical Threshold: NA Lower Non-Critical Threshold: NA Upper Non-Critical Threshold: 75.0 Degrees C Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: -128.0 Degrees C Sensor Max. Reading: 127.0 Degrees C Normal Min.: 5.0 Degrees C Normal Max.: 59.0 Degrees C Nominal reading: 47.0 Degrees C Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 39.0 Degrees C Sensor Status: [OK] Record ID: 51 Record Type: 01h Sensor Name: Processor Vccp Group Name: Voltage Sensor Number: 184 Event/Reading Type Code: 01h Slave Address/System Software ID: 10h B: 0 M: 117 R Exponent: -4 B Exponent: 2 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: 1.0296 Volts Upper Critical Threshold: 1.9422 Volts Lower Non-Critical Threshold: 1.0881 Volts Upper Non-Critical Threshold: 1.8837 Volts Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: 0.0 Volts Sensor Max. Reading: 2.9835 Volts Normal Min.: 1.0881 Volts Normal Max.: 1.8369 Volts Nominal reading: 1.4859 Volts Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: 1.4976 Volts Sensor Status: [OK] Record ID: 52 Record Type: 02h Sensor Name: CPU Therm Ctrl Group Name: Temperature Sensor Number: 192 Slave Address/System Software ID: 10h Event/Reading Type Code: 03h Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [State Deasserted] Record ID: 53 Record Type: 02h Sensor Name: DIMM 1B Group Name: Slot Connector Sensor Number: 224 Slave Address/System Software ID: 10h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [Slot/Connector Device installed/attached] Record ID: 54 Record Type: 02h Sensor Name: DIMM 1A Group Name: Slot Connector Sensor Number: 225 Slave Address/System Software ID: 10h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [Slot/Connector Device installed/attached] Record ID: 55 Record Type: 02h Sensor Name: DIMM 2B Group Name: Slot Connector Sensor Number: 226 Slave Address/System Software ID: 10h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [OK] Record ID: 56 Record Type: 02h Sensor Name: DIMM 2A Group Name: Slot Connector Sensor Number: 227 Slave Address/System Software ID: 10h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [OK] Record ID: 57 Record Type: 02h Sensor Name: DIMM 3B Group Name: Slot Connector Sensor Number: 228 Slave Address/System Software ID: 10h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [OK] Record ID: 58 Record Type: 02h Sensor Name: DIMM 3A Group Name: Slot Connector Sensor Number: 229 Slave Address/System Software ID: 10h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [OK] Record ID: 59 Record Type: 01h Sensor Name: Hot Swap Temp Group Name: Temperature Sensor Number: 1 Event/Reading Type Code: 01h Slave Address/System Software ID: 60h B: -128 M: 1 R Exponent: 0 B Exponent: 0 Linear: 0 Analog Data Format: 0 Lower Critical Threshold: NA Upper Critical Threshold: NA Lower Non-Critical Threshold: NA Upper Non-Critical Threshold: NA Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: -128.0 Degrees C Sensor Max. Reading: 127.0 Degrees C Normal Min.: 15.0 Degrees C Normal Max.: 40.0 Degrees C Nominal reading: 30.0 Degrees C Negative Hysteresis: 2 Positive Hysteresis: 2 Sensor Reading: NA Sensor Status: [Unknown] Record ID: 60 Record Type: 02h Sensor Name: HSC Drv Status Group Name: Drive Slot Sensor Number: 2 Slave Address/System Software ID: 60h Event/Reading Type Code: 6Fh Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [Unknown] Record ID: 61 Record Type: 02h Sensor Name: HSC Drv Presence Group Name: Drive Slot Sensor Number: 9 Slave Address/System Software ID: 60h Event/Reading Type Code: 08h Negative Hysteresis: 0 Positive Hysteresis: 0 Sensor Status: [Unknown] Record ID: 62 Record Type: 08h Sensor Name: NONE Container Entity ID: 15h Container Entity Instance: 01h Record ID: 63 Record Type: 11h Device Name: AC Pwr Cage FRU Device Type: 10h Device Type Modifier: 00h FRU Entity ID: 15h FRU Entity Instance: 01h Record ID: 64 Record Type: 11h Device Name: Pwr Supply 1 FRU Device Type: 10h Device Type Modifier: 00h FRU Entity ID: 0Ah FRU Entity Instance: 01h Record ID: 65 Record Type: 11h Device Name: DIMM 1B SPD Device Type: 10h Device Type Modifier: 01h FRU Entity ID: 20h FRU Entity Instance: 01h Record ID: 66 Record Type: 11h Device Name: DIMM 1A SPD Device Type: 10h Device Type Modifier: 01h FRU Entity ID: 20h FRU Entity Instance: 02h Record ID: 67 Record Type: 11h Device Name: DIMM 2B SPD Device Type: 10h Device Type Modifier: 01h FRU Entity ID: 20h FRU Entity Instance: 03h Record ID: 68 Record Type: 11h Device Name: DIMM 2A SPD Device Type: 10h Device Type Modifier: 01h FRU Entity ID: 20h FRU Entity Instance: 04h Record ID: 69 Record Type: 11h Device Name: DIMM 3B SPD Device Type: 10h Device Type Modifier: 01h FRU Entity ID: 20h FRU Entity Instance: 05h Record ID: 70 Record Type: 11h Device Name: DIMM 3A SPD Device Type: 10h Device Type Modifier: 01h FRU Entity ID: 20h FRU Entity Instance: 06h Record ID: 71 Record Type: 12h Device Name: Basbrd Mgmt Ctlr Entity ID: 07h Entity Instance: 01h Record ID: 72 Record Type: 12h Device Name: Hot Swap Ctlr Entity ID: 0Fh Entity Instance: 03h Record ID: 73 Record Type: 12h Device Name: Chs Bridge Ctlr Entity ID: 07h Entity Instance: 01h Record ID: 74 Record Type: C0h Sensor Name: NONE Manufacturer ID: 157h OEM Data: 02 02 00 00 70 Record ID: 75 Record Type: C0h Sensor Name: NONE Manufacturer ID: 157h OEM Data: 03 FC FC FC Record ID: 76 Record Type: C0h Sensor Name: NONE Manufacturer ID: 157h OEM Data: 07 00 FC FC FC 01 01 00 98 01 01 0A 3E 00 99 01 01 0A 3E 00 32 00 00 10 00 12 15 13 16 15 17 18 18 1D 19 20 1A 24 1B 2A 1C 2E 1D 34 1E 39 1F 41 20 48 21 50 22 59 23 64 Record ID: 77 Record Type: C0h Sensor Name: NONE Manufacturer ID: 157h OEM Data: 06 01 Record ID: 78 Record Type: C0h Sensor Name: NONE Manufacturer ID: 157h OEM Data: 53 44 52 20 50 61 63 6B 61 67 65 20 35 2E 36 2E 42 Record ID: 79 Record Type: C0h Sensor Name: NONE Manufacturer ID: 157h OEM Data: 53 44 52 20 46 69 6C 65 20 30 2E 43 www:~# |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
BMC provides a centralized, non-volatile System Event Log and logs system events and certain system configuration information to this device. You can perform a postmortem analysis on a system even when a the processor(s) are disabled because of a failure. ipmi-sel utility helps you view and manage system event log.
| 11.1 command-line arguments | Command-line arguments. | |
| 11.2 ipmi-sel sample output |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
www:~# ipmi-sel 4:11-Dec-2005 07:03:43:Event Logging Disabled #9:Log Area Reset/Cleared 24:11-Dec-2005 07:49:05:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 44:11-Dec-2005 07:50:02:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 64:11-Dec-2005 07:52:33:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 84:11-Dec-2005 07:57:04:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 104:11-Dec-2005 07:57:07:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 26h 124:11-Dec-2005 07:57:07:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 1Dh 144:31-Dec-1969 16:00:02:Power Unit #1:AC lost 164:31-Dec-1969 16:00:13:Power Supply #112:Presence detected 184:31-Dec-1969 16:00:15:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 26h 204:31-Dec-1969 16:00:15:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 1Dh 224:31-Dec-1969 16:00:44:System Event #131:Timestamp Clock Synch 244:11-Dec-2005 07:59:03:System Event #131:Timestamp Clock Synch 264:11-Dec-2005 07:59:59:System Event #131:OEM System Boot Event 284:11-Dec-2005 08:09:46:Platform Chassis Intrusion #5:General Chassis Intrusion 304:11-Dec-2005 08:27:06:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 26h 324:11-Dec-2005 08:27:06:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 1Dh 344:11-Dec-2005 08:27:39:System Event #131:Timestamp Clock Synch 364:11-Dec-2005 08:27:41:System Event #131:Timestamp Clock Synch 384:11-Dec-2005 08:28:02:Platform Chassis Intrusion #5:General Chassis Intrusion 404:11-Dec-2005 08:31:36:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 26h 424:11-Dec-2005 08:31:36:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 1Dh 444:11-Dec-2005 08:32:10:System Event #131:Timestamp Clock Synch 464:11-Dec-2005 08:32:10:System Event #131:Timestamp Clock Synch 484:11-Dec-2005 08:32:45:System Event #131:OEM System Boot Event 504:11-Dec-2005 08:36:10:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 26h 524:11-Dec-2005 08:36:10:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 1Dh 544:11-Dec-2005 08:36:32:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 26h 564:11-Dec-2005 08:36:32:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 1Dh 584:11-Dec-2005 08:36:54:System Event #131:System Reconfigured:OEM code = 01h 604:11-Dec-2005 08:37:09:System Event #131:Timestamp Clock Synch 624:12-Dec-2005 08:37:13:System Event #131:Timestamp Clock Synch 644:12-Dec-2005 08:40:28:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 26h 664:12-Dec-2005 08:40:28:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 1Dh 684:12-Dec-2005 08:41:05:System Event #131:Timestamp Clock Synch 704:12-Dec-2005 08:41:06:System Event #131:Timestamp Clock Synch 724:12-Dec-2005 08:42:20:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 26h 744:12-Dec-2005 08:42:20:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 1Dh 764:12-Dec-2005 08:42:56:System Event #131:Timestamp Clock Synch 784:12-Dec-2005 08:42:56:System Event #131:Timestamp Clock Synch 804:12-Dec-2005 08:43:33:System Event #131:OEM System Boot Event 824:12-Dec-2005 08:50:58:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 26h 844:12-Dec-2005 08:50:58:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 1Dh 864:12-Dec-2005 08:51:18:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 884:12-Dec-2005 08:51:35:System Event #131:Timestamp Clock Synch 904:12-Dec-2005 08:51:41:System Event #131:Timestamp Clock Synch 924:12-Dec-2005 08:51:43:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 944:12-Dec-2005 08:51:46:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 26h 964:12-Dec-2005 08:51:46:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 1Dh 984:12-Dec-2005 08:52:18:System Event #131:Timestamp Clock Synch 1004:12-Dec-2005 08:52:18:System Event #131:Timestamp Clock Synch 1024:12-Dec-2005 08:52:29:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 1044:12-Dec-2005 08:54:00:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 1064:12-Dec-2005 08:54:03:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 26h 1084:12-Dec-2005 08:54:03:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 1Dh 1104:12-Dec-2005 08:54:39:System Event #131:Timestamp Clock Synch 1124:12-Dec-2005 08:54:39:System Event #131:Timestamp Clock Synch 1144:12-Dec-2005 08:55:17:System Event #131:OEM System Boot Event 1164:12-Dec-2005 09:13:59:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 26h 1184:12-Dec-2005 09:13:59:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 1Dh 1204:12-Dec-2005 09:14:35:System Event #131:Timestamp Clock Synch 1224:12-Dec-2005 09:14:36:System Event #131:Timestamp Clock Synch 1244:12-Dec-2005 09:15:14:System Event #131:OEM System Boot Event 1264:31-Dec-1969 16:00:08:Power Supply #112:Presence detected 1284:31-Dec-1969 16:00:10:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 26h 1304:31-Dec-1969 16:00:10:Fan #68:Fan:Trigger reading = 00h:Trigger reading = 1Dh 1324:31-Dec-1969 16:01:32:Platform Chassis Intrusion #5:General Chassis Intrusion 1344:31-Dec-1969 16:00:08:Platform Chassis Intrusion #5:General Chassis Intrusion 1364:31-Dec-1969 16:00:08:Power Supply #112:Presence detected 1384:31-Dec-1969 16:00:07:Platform Chassis Intrusion #5:General Chassis Intrusion 1404:31-Dec-1969 16:00:08:Power Supply #112:Presence detected 1424:31-Dec-1969 16:00:02:Power Unit #1:AC lost 1444:31-Dec-1969 16:00:13:Power Supply #112:Presence detected 1464:31-Dec-1969 16:00:51:System Event #131:Timestamp Clock Synch 1484:12-Dec-2005 09:26:13:System Event #131:Timestamp Clock Synch 1504:12-Dec-2005 09:27:12:System Event #131:OEM System Boot Event 1524:12-Dec-2005 10:06:36:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 1544:12-Dec-2005 10:06:58:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 1564:12-Dec-2005 10:10:00:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 1584:12-Dec-2005 10:10:07:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 1604:13-Dec-2005 06:50:05:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 1624:14-Dec-2005 11:16:23:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 1644:15-Dec-2005 07:35:40:System Event #131:Timestamp Clock Synch 1664:15-Dec-2005 07:35:37:System Event #131:Timestamp Clock Synch 1684:15-Dec-2005 07:36:11:System Event #131:OEM System Boot Event 1704:18-Dec-2005 12:41:53:System Event #131:Timestamp Clock Synch 1724:18-Dec-2005 12:41:50:System Event #131:Timestamp Clock Synch 1744:18-Dec-2005 12:42:23:System Event #131:OEM System Boot Event 1764:19-Dec-2005 04:50:50:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 1784:19-Dec-2005 04:50:51:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 1804:25-Dec-2005 13:33:22:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 1824:25-Dec-2005 13:33:23:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 1844:26-Dec-2005 14:36:16:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 1864:26-Dec-2005 14:36:55:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 1884:26-Dec-2005 14:42:33:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 1904:26-Dec-2005 14:42:36:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 1924:27-Dec-2005 02:20:51:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 1944:27-Dec-2005 02:20:59:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 1964:27-Dec-2005 04:16:11:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 1984:27-Dec-2005 04:16:21:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 2004:27-Dec-2005 05:06:46:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 2024:27-Dec-2005 05:06:55:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 2044:28-Dec-2005 08:30:42:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 2064:28-Dec-2005 08:31:03:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 2084:28-Dec-2005 08:32:39:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 2104:28-Dec-2005 08:33:20:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 2124:28-Dec-2005 08:42:29:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 2144:28-Dec-2005 08:43:28:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 2164:03-Jan-2006 16:40:37:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 2184:03-Jan-2006 16:40:45:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 2204:03-Jan-2006 16:40:58:Platform Chassis Intrusion #5:LAN Leash Lost (system is unplugged from LAN):Network controller #15 www:~# |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
bmc-watchdog is a daemon and configuration utility for BMC
watchdog timer. When run as a daemon, it periodically resets the timer
so that, should the system lock up, the BMC can perform an appropriate
emergency recovery action.
The bmc-watchdog tool typically executes as a cronjob or daemon to manage the watchdog timer. A user must be root in order to run bmc-watchdog.
| 12.1 BMC Watchdog Theory | ||
| 12.2 command-line arguments | Command-line arguments. | |
| 12.3 bmc-watchdog example | bmc-watchdog example.
| |
| 12.4 bmc-watchdog known issues | Known issues with the bmc-watchdog.
|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
A BMC watchdog timer is part of the Intelligent Platform Management Interface (IPMI) specification and is only available to BMCs that are compliant with IPMI. When a BMC watchdog timer is started, it begins counting down to zero from some positive number of seconds. When the timer hits zero, the timer will execute a pre-configured pre-timeout interrupt and/or timeout action.
In order to stop the pre-timeout interrupt or timeout action from being generated, the watchdog timer must be periodically reset back to its initial beginning value.
The BMC watchdog timer automatically stops itself when the machine is rebooted. Therefore, when a machine is brought up, the BMC watchdog timer must be setup again before it can be used.
Typically, a BMC watchdog timer is used to automatically reset a machine that has crashed. When the operating system first starts up, the BMC timer is set to its initial countdown value. At periodic intervals, when the operating system is functioning properly, the watchdog timer can be reset by the OS or a userspace program. Thus, the timer never counts down to zero. When the system crashes, the timer cannot be reset by the OS or userspace program. Eventually, the timer will countdown to zero and reset the machine.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| 12.2.1 bmc-watchdog general options | General command-line arguments. | |
| 12.2.2 bmc-watchdog command options | Command command-line arguments. | |
| 12.2.3 bmc-watchdog set options | Set command-line arguments. | |
| 12.2.4 bmc-watchdog start options | Start command-line arguments. | |
| 12.2.5 bmc-watchdog daemon options | Daemon command-line arguments. |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The following commands are available to bmc-watchdog.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The following commands are available to bmc-watchdog.
bmc-watchdog as a daemon. Configurable BMC
watchdog timer options are listed below under bmc-watchdog daemon options.
The configuration values are set once, then the daemon will reset the
timer at specified periodic intervals. Every time the BMC watchdog
timer is reset, a log entry will be generated in the
`bmc-watchdog' log. The default log is stored at
`/var/log/freeipmi/bmc-watchdog.log'. The daemon can be stopped
using the `--stop' command, `--clear' command, or by setting
the `stop_timer' flag on the `--set' command.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The following options can be used by the set command to set or clear various BMC watchdog configuration parameters.
`1' = BIOS FRB2
`2' = BIOS POST
`3' = OS_LOAD
`4' = SMS OS
`5' = OEM
|
`0' = No action
`1' = Hard Reset
`2' = Power Down
`3' = Power Cycle
|
`0' = None
`1' = SMI
`2' = NMI
`3' = Messaging Interrupt
|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The following options can be used by the start command.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The following options can be used by the daemon command to set the initial BMC watchdog configuration parameters.
`1' = BIOS FRB2
`2' = BIOS POST
`3' = OS_LOAD
`4' = SMS OS
`5' = OEM
|
`0' = No action
`1' = Hard Reset
`2' = Power Down
`3' = Power Cycle
|
`0' = None
`1' = SMI
`2' = NMI
`3' = Messaging Interrupt
|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Setup a bmc-watchdog daemon that resets the machine after `15 minutes' (900 seconds) if the OS has crashed. (1)
debian-ia64:~# bmc-watchdog -d -u 4 -p 0 -a 1 -i 900 debian-ia64:~# ps -C bmc-watchdog PID TTY TIME CMD 1035 ? 00:00:00 bmc-watchdog debian-ia64:~# |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
bmc-watchdog may fail to reset the watchdog timer if it is
not scheduled properly. It is always recommended that bmc-watchdog
be executed with a high scheduling priority.
On some machines, the hardware based SMI Handler may disable a processor after a watchdog timer timeout if the timer use is set to something other than SMS/OS.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Remote out-of-band chassis control utility to perform power-up, power-down, power-cycle, hard-reset, pulse-diagnostics-interrupt and OS soft shutdown operations.
PowerMan http://www.llnl.gov/linux/powerman/ now supports
ipmipower as a remote power control device.
Whenever a power command (`--on', `--off',
`--cycle', `--reset', `--stat', `--pulse',
or `--soft') is specified on the command-line,
ipmipower will run in non-interactive mode.
ipmipower will attempt to run the power command on all
hostnames listed on the command line then exit.
If no power commands are specified on the command line,
ipmipower will run in interactive mode. Interactive mode
gives the user a command-line interface to enter various commands.
Details of the interactive command line interface can be found under
ipmipower basic options section.
| 13.1 Command-line arguments | ||
| 13.2 ipmipower configuration file | Configuration file. | |
| 13.3 ipmipower interactive commands | Interactive commands. | |
| 13.4 Host ranges | Host range specificaiton. | |
| 13.5 ipmipower example | ||
| 13.6 Use with powerman | PowerMan integration. | |
| 13.7 Known issues with the ipmipower command | Known issues. |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| 13.1.1 ipmipower basic options | Basic options. | |
| 13.1.2 ipmipower advanced options | Advanced options. | |
| 13.1.3 ipmipower network options | Network options. |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The following options are basic options for ipmipower.
ipmipower. The hostnames must resolve to the IP address of
the NIC connected to the remote host BMC. If hostnames do not resolve
to proper BMC IP addresses, RMCP ping messages will not discover the
remote host or power commands will time out. This option is required
if a power command (`--on', `--off', `--cycle',
`--reset', or `--stat', `--pulse',
`--soft') is specified on the command-line. Hostnames may be
specified in a range format; see Host ranges section.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The following advanced options are used to change the behavior of ipmipower.
ipmipower.
The currently available authentication types are:
`none'
`straight_passwd_key' => (default)
`md2'
`md5'
|
cycle or
reset commands to turn on a machine that is currently
powered off. This option will force ipmipower to issue a
power on command instead of a power cycle or hard reset command if the
remote machine's power is currently off.
ipmipower. The
currently available output types are:
`none'
`newline' => (default)
`hostlist'
|
Hostlist output can be used to shorten output if the number of nodes in your cluster is quite large. However, hostlist output will only output after the slowest node has completed its power control operation.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The following options are used to change the behavior of the actual
ipmipower network protocol used.
ipmipower
uses the time-out value to determine when to give up on a power
command. If not specified, a default time-out of 20000
milliseconds (20 seconds) is used.
ipmipower will retry sending that packet. If not specified,
packet retransmissions will occur after `400' milliseconds (0.4
seconds). The value ms must be less than the time out length
specified with `--timeout'. Packet retransmissions can be
disabled by setting the retry-timeout length to `0'.
Note how this option differs from the `--timeout' option above. The `--timeout' option refers to the entire amount of time the IPMI protocol has to complete a power control operation. The `--retry' option refers to the amount of time any individual packet within the IPMI protocol has to complete.
ipmipower will increase the retry-timeout length by
another factor for the duration of the current power control
operation. This is done to reduce network traffic and allow BMC
buffers to empty. If not specified, retry-backoff-count is
`8'. Retransmission backoff can be disabled by setting the retry
backoff count to `0'.
ipmipower will send RMCP ping discovery messages every
ping-interval milliseconds to discover all remote hosts and
confirm its support of IPMI. Power commands cannot be sent to a host
until it is discovered. If a remote host does not respond within
ping-timeout milliseconds, a host will be considered
undiscovered and power commands will not be sent to it. If not
specified, ping-interval is `5000' milliseconds (5 seconds)
and ping-timeout is `30000' milliseconds (30 seconds).
Ping discovery requests can be disabled by setting the ping interval
to `0'. If ping discovery messages are disabled, power commands
will be attempted without knowledge of the host's existence or its
support of IPMI. The value of ping-interval must be less than
the ping-timeout length. RMCP ping discovery messages are
automatically disabled in non-interactive mode.
ipmipower will monitor ping packets
in ping-packet-count chunks. If ipmipower does not
receive a response to greater than ping-percent of those
packets, ipmipower will assume the link to this node is bad
and will not send power control operations to that node until the
connection is determined to be reliable. If not specified,
ping-packet-count is `10' and ping-percent is
`50'. This heuristic can be disabled by setting either
ping-packet-count or ping-percent to `0'. This
feature is not used if ping-interval is set to `0'. Note
that the `--ping-percent' option takes an integer as an
argument, not a decimal.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The ipmipower configuration file can be used to set default
values to ipmipower when values aren't set on the command line. This
allows users to avoid typing in a long list of command line options
everytime ipmipower is executed. It can also be used to hide
usernames and passwords from the ps command. See
Known issues with the ipmipower command for details.
By default, the configuration file is stored at `/etc/ipmipower.conf'. But users may select a different configuration file at the command line through the `--config' option.
The user can still override the configuration file values by specifying the options on the command line. The configuration file does not stop a user from specifying certain options.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The following are a list of configuration options that can be specified in the configuration file. Each configuration option must be listed on a separate line. Arguments for an option are separated by any amount of whitespace. Multiple arguments are also separated by whitespace. Comments can be marked by using the pound sign ("#") character, and lines can be continued on the next using backslash ("\").
Note that it is possible to list the username and password in the con- figuration file. If this data is stored in a configuration file, sys- tem administrators should limit access to this file.
Specify the default hostnames. Multiple hostnames or hostname ranges can be specified by separating each range by whitespace. See Host ranges for information on hostname ranges. For example, any of the following configuration listings would be acceptable:
hostnames host1 host2 host3 foo1 bar1 hostnames host1,host2,host3,foo1,bar1 hostnames host[1-3] foo1 bar1 hostnames host[1-3] foo1,bar1 |
At most 64 hostnames or hostname ranges can be separted by whitespace.
ipmipower
currently supports the following authentication types:
`straight_passwd_key'
`md2'
`md5'
|
ipmipower
currently supports the following output types:
`none'
`newline' => (default)
`hostlist'
|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
ipmipower provides the following interactive commands at the
`ipmipower>' prompt. Before any power commands (`on',
`off', `cycle', `reset', `stat', `pulse', or
`soft') can be used, hostnames must be configured into ipmipower,
either through the command prompt or the hostnames command below.
`none'
`straight_passwd_key'
`md2'
`md5'
|
`none'
`newline'
`hostlist'
|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
As noted above, ipmipower accepts a range of hostnames in the general form: prefix[n-m,l-k,...], where n < m and l < k, etc., as an alternative to explicit comma separated lists of hosts. This form should not be confused with regular expression character classes (also denoted by []). For example, foo[19] does not represent foo1 or foo9, but rather represents a degenerate range: foo19.
This range syntax is meant only as a convenience on clusters with a prefixNN naming convention and specification of ranges should not be considered necessary - the list foo1,foo9 could be specified as such, or by the range foo[1,9].
Some examples of range usage follow:
foo[01-05] instead of foo01,foo02,foo03,foo04,foo05
foo[7,9-10] instead of foo7,foo9,foo10
foo[0-3] instead of foo0,foo1,foo2,foo3
|
As a reminder to the reader, some shells will interpret brackets ([ and ]) for pattern matching. Depending on your shell, it may be necessary to enclose ranged lists within quotes.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Determine the power status of foo[0-2] with null username and password.
ipmipower -h foo[0-2] --stat |
Determine the power status of foo[0-2] with non-null username and password.
ipmipower -h foo[0-2] -u foo -p bar --stat |
Hard reset nodes foo[0-2] with non-null username and password.
ipmipower -h foo[0-2] -u foo -p bar --reset |
Hard reset the nodes configured in a configuration file.
ipmipower -C /etc/powerctrl.conf --reset |
Example ipmipower session:
debian-sid:~# ipmipower --hostnames debian-ia64 --password "rea1secret" --stat debian-ia64: on debian-sid:~# ipmipower --hostnames debian-ia64 --password "rea1secret" --off debian-ia64: ok debian-sid:~# ipmipower --hostnames debian-ia64 --password "rea1secret" --stat debian-ia64: off debian-sid:~# ipmipower --hostnames debian-ia64 --password "rea1secret" --on debian-ia64: ok debian-sid:~# |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The powerman device configuration file `ipmipower.dev'
supplied with powerman 1.0.20 and beyond can be used to
control one or more instances of ipmipower in coprocess
mode.
Due to deficiencies within powerman, the power control
operations `--on', `--off', `--cycle',
`--reset' will be reported as successful, despite any errors
that may occur. The user should use the `--query' option to
ensure that all remote hosts were successfully powered on or off.
It is recommend that the `--on-if-off' option be used with
ipmipower when it is used in conjunction with powerman. This
will ensure ipmipower behaves similarly to other
powerman devices.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
In order to prevent brute force attacks, some BMCs will lock up after a number of username, password, or privilege errors. There is no known way to cleanly deal with a locked up BMC. The best option is to simply wait awhile.
On certain operating systems, if you input your username and password
on the command line, the username and password may be discovered by
other users when using the ps command or looking in the
`/proc' file system. The most secure solution is to enter the
username and password while in interactive mode. If administrators do
not wish to type in their username and password at the interactive
prompt, they can be listed in a configuration file, in which the
access to this file can be limited.
IPMI specifications do not require BMCs to perform a power control operation before returning a completion code to the caller. Therefore, it is possible for ipmipower power status queries to initially return information other than what you are expecting. For example, if a `power off' operation is performed, a BMC may return a successful completion-code to ipmipower before the `power off' operation is actually performed. Subsequent power status queries may return `on' for several seconds, until the BMC actually performs the `power off' operation.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
IPMI discovery and reachability test tool.
ipmiping uses the IPMI Get Authentication
Capabilities request datagram to elicit an IPMI Get
Authentication Capabilities response from a remote host. The utility
can be used to verify if a remote host supports IPMI.
Returns `0' to the environment if it receives at least `1' response from the remote host. Otherwise, it exists with a value of `1'.
| 14.1 command-line arguments | Command-line arguments. | |
| 14.2 ipmiping example | ipmiping example.
| |
| 14.3 ipmiping known issues | Known issues with the ipmi-ping
|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
ipmiping [OPTIONS] destination
The following options are available
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Example: Test the BMC reachability of host `debian-ia64' using IPMI protocol.
debian-sid:~# ipmiping debian-ia64 ipmiping debian-ia64 (192.168.1.60) response received from 192.168.1.60: rq_seq=0 response received from 192.168.1.60: rq_seq=1 response received from 192.168.1.60: rq_seq=2 response received from 192.168.1.60: rq_seq=3 response received from 192.168.1.60: rq_seq=4 response received from 192.168.1.60: rq_seq=5 --- ipmiping debian-ia64 statistics --- 6 requests transmitted, 6 responses received in time, 0.0% packet loss |
Example: Test the BMC reachability of host `debian-ia64' in verbose mode.
debian-sid:~# ipmiping -v debian-ia64 ipmiping debian-ia64 (192.168.1.60) response received from 192.168.1.60: rq_seq=0, auth: none=set md2=set md5=set passwd=set oem=clear permsg=clear user=set response received from 192.168.1.60: rq_seq=1, auth: none=set md2=set md5=set passwd=set oem=clear permsg=clear user=set response received from 192.168.1.60: rq_seq=2, auth: none=set md2=set md5=set passwd=set oem=clear permsg=clear user=set response received from 192.168.1.60: rq_seq=3, auth: none=set md2=set md5=set passwd=set oem=clear permsg=clear user=set response received from 192.168.1.60: rq_seq=4, auth: none=set md2=set md5=set passwd=set oem=clear permsg=clear user=set --- ipmiping debian-ia64 statistics --- 5 requests transmitted, 5 responses received in time, 0.0% packet loss |
Example: Test the BMC reachability of host `debian-ia64' by sending exactly 2 packets.
debian-sid:~# ipmiping -c 2 debian-ia64 ipmiping debian-ia64 (192.168.1.60) response received from 192.168.1.60: rq_seq=0 response received from 192.168.1.60: rq_seq=1 --- ipmiping debian-ia64 statistics --- 2 requests transmitted, 2 responses received in time, 0.0% packet loss debian-sid:~# |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
It has been observed that some remote BMCs can get confused and
delay packet responses if duplicate packets are sent in succession
very quickly. For example, this could happen if the user repeatedly
executes ipmiping -c 1 destination very quickly. There is
no known way to cleanly deal with a confused BMC. The best
option is to simply wait awhile.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
RMCP/IPMI discovery and reachability test tool.
rmcpping uses the RMCP ping request datagram to elicit an
RMCP pong response from a remote host. The utility can be used to
verify if a remote host supports RMCP or IPMI.
Returns 0 to the environment if it receives at least `1' response from the remote host. Otherwise, it exits with a value of `1'.
| 15.1 Command-line arguments | ||
| 15.2 rmcpping example | rmcpping example.
| |
| 15.3 rmcpping known issues | Known issues with the rmcpping.
|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
rmcpping [OPTIONS] destination
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Example: Test the BMC reachability of host `debian-ia64' using RMCP protocol.
debian-sid:~# rmcpping debian-ia64 rmcpping debian-ia64 (192.168.1.60) pong received from 192.168.1.60: msg_tag=0 pong received from 192.168.1.60: msg_tag=1 pong received from 192.168.1.60: msg_tag=2 pong received from 192.168.1.60: msg_tag=3 pong received from 192.168.1.60: msg_tag=4 pong received from 192.168.1.60: msg_tag=5 pong received from 192.168.1.60: msg_tag=6 pong received from 192.168.1.60: msg_tag=7 pong received from 192.168.1.60: msg_tag=8 --- rmcpping debian-ia64 statistics --- 9 pings transmitted, 9 pongs received in time, 0.0% packet loss |
Example: Test the BMC reachability of host `debian-ia64' in verbose mode.
debian-sid:~# rmcpping -v debian-ia64 rmcpping debian-ia64 (192.168.1.60) pong received from 192.168.1.60: msg_tag=0, ipmi supported pong received from 192.168.1.60: msg_tag=1, ipmi supported pong received from 192.168.1.60: msg_tag=2, ipmi supported pong received from 192.168.1.60: msg_tag=3, ipmi supported pong received from 192.168.1.60: msg_tag=4, ipmi supported --- rmcpping debian-ia64 statistics --- 5 pings transmitted, 5 pongs received in time, 0.0% packet loss |
Example: Test the BMC reachability of host `debian-ia64' by sending exactly 2 packets.
debian-sid:~# rmcpping -c 2 debian-ia64 rmcpping debian-ia64 (192.168.1.60) pong received from 192.168.1.60: msg_tag=0 pong received from 192.168.1.60: msg_tag=1 --- rmcpping debian-ia64 statistics --- 2 pings transmitted, 2 pongs received in time, 0.0% packet loss debian-sid:~# |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
It has been observed that some remote BMCs can get confused and
delay packet responses if duplicate packets are sent in succession
very quickly. For example, this could happen if the user repeatedly
executes rmcpping -c 1 destination very quickly. There is
no known way to cleanly deal with a confused BMC. The best
option is to simply wait awhile.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
"garpd" daemon broadcasts request based gratuitous ARP packets with IP and MAC Address mappings from a configuration file. GARPD is particularly useful for IPMI BMCs (mBMC) which do not support Gartuitous ARP. How ever there are other uses for GARP like IP address conflicts, IP address take over, ARP updates in a clustered environment, NIC link status updates.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Gratuitous ARP: Usually ARP works as follows. Host A sends out an ARP request for the hardware address of an IP address on host B. Host B sees the request and sends an ARP reply containing the hardware address for the interface with the IP address in question. Host A then records the hardware address in its ARP cache so it doesn't have to do an ARP request and wait for a reply each time it wants to send a packet. Entries in an ARP cache typically expire after about two minutes. For more information on ARP, please see RFC 826.
Request Based Gratuitous ARP: A gratuitous ARP request packet where the source and destination IP are both set to the IP of the machine issuing the packet and the destination MAC is the broadcast address ff:ff:ff:ff:ff:ff. Ordinarily, no reply packet will occur. And all hosts on the LAN will refresh their ARP caches using the source hardware address of this request.
Response Based Gratuitous ARP: A gratuitous ARP reply packet without any ARP request where the ARP reply is addressed to the broadcast hardware address. All hosts on the LAN will receive the ARP reply and refresh their ARP cache accordingly.
| 16.2 Command-line arguments | ||
| 16.3 garpd configuration file | Example configuration file. |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
garpd [OPTIONS...]
The following options are available
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Example "garpd" configuration file.
# /usr/etc/garpd.conf: garpd configuration file. # Set default interface to eth0. default iface [eth0] # Send broadcasts every 500 milli seconds. batch-delay 500 # Delay 200 milli seconds between every broadcast. interval-delay 200 # host and MAC mappings to be broadcasted as Gratuitous ARP. host = node2 mac=aa:bb:cc:33:13:c2 iface=eth1 host = 1.2.3.4 mac= aa:1b:cc:33:13:c2 iface=[eth2 eth3 eth4] host = 5.6.7.8 mac= aa:1b:cc:33:13:c2 iface = [ eth4 ] # Use default iface. host = 9.10.11.12 mac =aa:1b:cc:33:13:c2 |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| 17.1 Fencing IPMI IP ports | ||
| 17.2 "Cat ate the fish" exception | Cat ate the fish exception. | |
| 17.3 Non-unique IPC key |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Append the following to /etc/services: # BMC IPMI/RMCP services rmcp 623/udp # Aux Bus Shunt (Primary RMCP Port) rmcps 664/udp # Secure Aux Bus (Secondary RMCP Port) |
BMC internally (at hardware level) uses the above mentioned ports for sending RMCP/IPMI packets . To avoid any conflit with the BMC, Operating System should make sure no other applications or services uses these ports for communication. One easy way to do this is to start a simple daemon at the boot time that opens these ports but never uses them.
Most common victims to this issue are Remote-shell (rsh) and NIS services. You will notice "time out" errors under heavy load, when these services run over the BMC reserved ports.
Secure connections to BMC port 664 is not enabled on most BMC implementations by default.
Thanks to Anand Manian (GE Power Systems) for reporting this problem.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
fish throws exception if it encounters any error in its
extension system. Most of the times, You will get a clear indicative
message from the exception dump.
In this example, Fish throws an exception message, when a built-in
primitive is misspelt as fi-set-promt! instead of
fi-set-prompt!. Unbound-variable `tag' and `throw
args' gives you the clue.
root@gnu:~/work/freeipmi# fish >>--:> >>--:> >>--:> >>--:> ~ ~ Cat ate the fish!! ~ ~ >>--:> >>--:> >>--:> >>--:> Fish Exception (gh_standard_handler dump): tag : unbound-variable throw args : (#f Unbound variable: ~S (fi-set-promt!) #f) data : [/usr/etc/fish/fish.scm] No backtrace available. FreeIPMI Shell [fish-0.1.0] Copyright (C) 2003-2004 FreeIPMI Core Team This program is free software; you may redistribute it under the terms of the GNU General Public License. This program has absolutely no warranty. fish> |
;; file: /usr/etc/fish/fish.scm (fish startup file)
(fi-set-promt! "fish# ")
^---<< Typo, Spell correctly as "fi-set-prompt!"
|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Drivers internally use the inode number of
`/var/lib/freeipmi/ipckey' to obtain a system wide unique IPC key
for locking and synchronization through ftok call. It is
extremely rare (but possible) for more than one application to
conflict with this IPC key, because ftok doesn't absolutely
guarantee system wide uniqueness.
To regenerate a new system wide unique IPC key, you have to recreate `/var/lib/freeipmi/ipckey' with a new inode number.
Example: Recreating `/var/lib/freeipmi/ipckey' file.
debian-ia64:~# touch -f /var/lib/freeipmi/ipckey.new debian-ia64:~# ls --inode /var/lib/freeipmi/ipckey 2289282 /var/lib/freeipmi/ipckey debian-ia64:~# ls --inode /var/lib/freeipmi/ipckey.new 2289284 /var/lib/freeipmi/ipckey.new debian-ia64:~# mv -f /var/lib/freeipmi/ipckey.new /var/lib/freeipmi/ipckey debian-ia64:~# ls --inode /var/lib/freeipmi/ipckey 2289284 /var/lib/freeipmi/ipckey debian-ia64:~# |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Contact Anand Babu ab@gnu.org.in
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
1. | Albert Chu | |
2. | Anand Babu | |
3. | Balamurugan | |
4. | Ian Zimmerman | |
5. | Jim Garlick |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
1. | Anand Babu |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
1. | Albert Chu | RedHat GNU/Linux | |
2. | Ian Zimmerman | Debian GNU/Linux |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
1. | Anand Babu |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| 20.1 GNU FreeIPMI license | ||
| 20.2 GNU FreeIPMI documentation license |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Version 2, June 1991
Copyright © 1989, 1991 Free Software Foundation, Inc. 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.
Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and modification follow.
Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.
You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.
In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.
If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
one line to give the program's name and a brief idea of what it does. Copyright (C) yyyy name of author This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. |
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) 19yy name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. |
The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. signature of Ty Coon, 1 April 1989 Ty Coon, President of Vice |
This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Version 1.2, November 2002
Copyright © 2000,2001,2002 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. |
The purpose of this License is to make a manual, textbook, or other functional and useful document free in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.
This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.
We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.
This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.
A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.
The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.
A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.
A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.
The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.
You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and you may publicly display copies.
If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.
If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.
You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:
If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.
You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.
You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.
You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.
The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.
In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements."
You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.
A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.
Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.
If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.
You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:
Copyright (C) year your name. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled ``GNU Free Documentation License''. |
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the "with...Texts." line with this:
with the Invariant Sections being list their titles, with
the Front-Cover Texts being list, and with the Back-Cover Texts
being list.
|
If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.
If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
BMC | [B]aseboard [M]anagement [C]ontroller. |
FISH | [F]ree[I]PMI [SH]ell. |
GNU | [G]NU's [N]ot [U]nix. |
GPL | GNU [G]eneral [P]ublic [L]icense. |
IP | [I]nternet [P]rotocol. |
IPMI | [I]ntelligent [P]latform [M]anagement [I]nterface |
NIS | [N]etwork [I]nformation [S]ervice. Also humerously known as [N]etwork [I]ntrusion [S]ervice :) . |
RMCP | [R]empote [M]anagement [C]ontrol [P]rotocol. |
RSH | [R]emote [SH]ell. |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| Jump to: | .
/
B C E F G I P R S T |
|---|
| Jump to: | .
/
B C E F G I P R S T |
|---|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| Jump to: | B F I L P R |
|---|
| Jump to: | B F I L P R |
|---|
| [Top] | [Contents] | [Index] | [ ? ] |
see default bmc-watchdog rc script
`/etc/init.d/bmc-watchdog' a more complete example.
| [Top] | [Contents] | [Index] | [ ? ] |
| [Top] | [Contents] | [Index] | [ ? ] |
| [Top] | [Contents] | [Index] | [ ? ] |
This document was generated by root on February, 10 2006 using texi2html 1.76.
The buttons in the navigation panels have the following meaning:
| Button | Name | Go to | From 1.2.3 go to |
|---|---|---|---|
| [ < ] | Back | previous section in reading order | 1.2.2 |
| [ > ] | Forward | next section in reading order | 1.2.4 |
| [ << ] | FastBack | beginning of this chapter or previous chapter | 1 |
| [ Up ] | Up | up section | 1.2 |
| [ >> ] | FastForward | next chapter | 2 |
| [Top] | Top | cover (top) of document | |
| [Contents] | Contents | table of contents | |
| [Index] | Index | index | |
| [ ? ] | About | about (help) |
where the Example assumes that the current position is at Subsubsection One-Two-Three of a document of the following structure:
This document was generated by root on February, 10 2006 using texi2html 1.76.