.TH "ipmitool" "1" "" "Duncan Laurie" "" .SH "NAME" ipmitool \- utility for controlling IPMI\-enabled devices .SH "SYNOPSIS" ipmitool [\fB\-c\fR|\fB\-h\fR|\fB\-d \fIN\fP\fR|\fB\-v\fR|\fB\-V\fR] \fB\-I\fR \fIopen\fP <\fIcommand\fP> ipmitool [\fB\-c\fR|\fB\-h\fR|\fB\-v\fR|\fB\-V\fR] \fB\-I\fR \fIlan\fP \fB\-H\fR <\fIhostname\fP> [\fB\-p\fR <\fIport\fP>] [\fB\-U\fR <\fIusername\fP>] [\fB\-A\fR <\fIauthtype\fP>] [\fB\-L\fR <\fIprivlvl\fP>] [\fB\-a\fR|\fB\-E\fR|\fB\-P\fR|\fB\-f\fR <\fIpassword\fP>] [\fB\-o\fR <\fIoemtype\fP>] [\fB\-O\fR <\fIsel oem\fP>] [\fB\-e\fR <\fIesc_char\fP>] <\fIcommand\fP> ipmitool [\fB\-c\fR|\fB\-h\fR|\fB\-v\fR|\fB\-V\fR] \fB\-I\fR \fIlanplus\fP \fB\-H\fR <\fIhostname\fP> [\fB\-p\fR <\fIport\fP>] [\fB\-U\fR <\fIusername\fP>] [\fB\-L\fR <\fIprivlvl\fP>] [\fB\-a\fR|\fB\-E\fR|\fB\-P\fR|\fB\-f\fR <\fIpassword\fP>] [\fB\-o\fR <\fIoemtype\fP>] [\fB\-O\fR <\fIsel oem\fP>] [\fB\-C\fR <\fIciphersuite\fP>] [\fB\-k\fR <\fIkg_key\fP>] [\fB\-e\fR <\fIesc_char\fP>] <\fIcommand\fP> .SH "DESCRIPTION" This program lets you manage Intelligent Platform Management Interface (IPMI) functions of either the local system, via a kernel device driver, or a remote system, using IPMI V1.5 and IPMI v2.0. These functions include printing FRU information, LAN configuration, sensor readings, and remote chassis power control. IPMI management of a local system interface requires a compatible IPMI kernel driver to be installed and configured. On Linux this driver is called \fIOpenIPMI\fP and it is included in standard distributions. On Solaris this driver is called \fIBMC\fP and is inclued in Solaris 10. Management of a remote station requires the IPMI\-over\-LAN interface to be enabled and configured. Depending on the particular requirements of each system it may be possible to enable the LAN interface using ipmitool over the system interface. .SH "OPTIONS" .TP \fB\-a\fR Prompt for the remote server password. .TP \fB\-A\fR <\fIauthtype\fP> Specify an authentication type to use during IPMIv1.5 \fIlan\fP session activation. Supported types are NONE, PASSWORD, MD2, MD5, or OEM. .TP \fB\-c\fR Present output in CSV (comma separated variable) format. This is not available with all commands. .TP \fB\-e\fR <\fIsol_escape_char\fP> Use supplied character for SOL session escape character. The default is to use \fI~\fP but this can conflict with ssh sessions. .TP \fB\-k\fR <\fIkey\fP> Use supplied Kg key for IPMIv2 authentication. The default is not to use any Kg key. .TP \fB\-C\fR <\fIciphersuite\fP> The remote server authentication, integrity, and encryption algorithms to use for IPMIv2 \fIlanplus\fP connections. See table 22\-19 in the IPMIv2 specification. The default is 3 which specifies RAKP\-HMAC\-SHA1 authentication, HMAC\-SHA1\-96 integrity, and AES\-CBC\-128 encryption algorightms. .TP \fB\-E\fR The remote server password is specified by the environment variable \fIIPMI_PASSWORD\fP. .TP \fB\-f\fR <\fIpassword_file\fP> Specifies a file containing the remote server password. If this option is absent, or if password_file is empty, the password will default to NULL. .TP \fB\-h\fR Get basic usage help from the command line. .TP \fB\-H\fR <\fIaddress\fP> Remote server address, can be IP address or hostname. This option is required for \fIlan\fP and \fIlanplus\fP interfaces. .TP \fB\-I\fR <\fIinterface\fP> Selects IPMI interface to use. Supported interfaces that are compiled in are visible in the usage help output. .TP \fB\-L\fR <\fIprivlvl\fP> Force session privilege level. Can be CALLBACK, USER, OPERATOR, ADMINISTRATOR. Default is ADMINISTRATOR. .TP \fB\-m\fR <\fIlocal_address\fP> Set the local IPMB address. The default is 0x20 and there should be no need to change it for normal operation. .TP \fB\-o\fR <\fIoemtype\fP> Select OEM type to support. This usually involves minor hacks in place in the code to work around quirks in various BMCs from various manufacturers. Use \fI\-o list\fP to see a list of current supported OEM types. .TP \fB\-O\fR <\fIsel oem\fP> Open selected file and read OEM SEL event descriptions to be used during SEL listings. See examples in contrib dir for file format. .TP \fB\-p\fR <\fIport\fP> Remote server UDP port to connect to. Default is 623. .TP \fB\-P\fR <\fIpassword\fP> Remote server password is specified on the command line. If supported it will be obscured in the process list. \fBNote!\fR Specifying the password as a command line option is not recommended. .TP \fB\-S\fR <\fIsdr_cache_file\fP> Use local file for remote SDR cache. Using a local SDR cache can drastically increase performance for commands that require knowledge of the entire SDR to perform their function. Local SDR cache from a remote system can be created with the \fIsdr dump\fP command. .TP \fB\-t\fR <\fItarget_address\fP> Bridge IPMI requests to the remote target address. .TP \fB\-U\fR <\fIusername\fP> Remote server username, default is NULL user. .TP \fB\-d \fIN\fP\fR Use device number N to specify the /dev/ipmiN (or /dev/ipmi/N or /dev/ipmidev/N) device to use for in-band BMC communication. Used to target a specific BMC on a multi-node, multi-BMC system through the ipmi device driver interface. Default is 0. .TP \fB\-v\fR Increase verbose output level. This option may be specified multiple times to increase the level of debug output. If given three times you will get hexdumps of all incoming and outgoing packets. .TP \fB\-V\fR Display version information. .LP If no password method is specified then ipmitool will prompt the user for a password. If no password is entered at the prompt, the remote server password will default to NULL. .SH "SECURITY" There are several security issues be be considered before enabling the IPMI LAN interface. A remote station has the ability to control a system's power state as well as being able to gather certain platform information. To reduce vulnerability it is strongly advised that the IPMI LAN interface only be enabled in 'trusted' environments where system security is not an issue or where there is a dedicated secure 'management network'. Further it is strongly advised that you should not enable IPMI for remote access without setting a password, and that that password should not be the same as any other password on that system. When an IPMI password is changed on a remote machine with the IPMIv1.5 \fIlan\fP interface the new password is sent across the network as clear text. This could be observed and then used to attack the remote system. It is thus recommended that IPMI password management only be done over IPMIv2.0 \fIlanplus\fP interface or the system interface on the local station. For IPMI v1.5, the maximum password length is 16 characters. Passwords longer than 16 characters will be truncated. For IPMI v2.0, the maximum password length is 20 characters; longer passwords are truncated. .SH "COMMANDS" .TP \fIhelp\fP This can be used to get command\-line help on ipmitool commands. It may also be placed at the end of commands to get option usage help. ipmitool help .br Commands: raw Send a RAW IPMI request and print response lan Configure LAN Channels chassis Get chassis status and set power state event Send events to MC mc Management Controller status and global enables sdr Print Sensor Data Repository entries and readings sensor Print detailed sensor information fru Print built\-in FRU and scan for FRU locators sel Print System Event Log (SEL) pef Configure Platform Event Filtering (PEF) sol Configure and connect IPMIv2.0 Serial\-over\-LAN tsol Configure and connect Tyan IPMIv1.5 Serial\-over\-LAN isol Configure and connect Intel IPMIv1.5 Serial\-over\-LAN user Configure Management Controller users channel Configure Management Controller channels session Print session information sunoem Manage Sun OEM Extensions exec Run list of commands from file set Set runtime variable for shell and exec ipmitool chassis help .br Chassis Commands: status, power, identify, policy, restart_cause, poh, bootdev ipmitool chassis power help .br chassis power Commands: status, on, off, cycle, reset, diag, soft .TP \fIbmc|mc\fP .RS .TP \fIreset\fP <\fBwarm\fR|\fBcold\fR> .br Instructs the BMC to perform a warm or cold reset. .TP \fIguid\fP Display the Management Controller Globally Unique IDentifier. .TP \fIinfo\fP .br Displays information about the BMC hardware, including device revision, firmware revision, IPMI version supported, manufacturer ID, and information on additional device support. .TP \fIgetenables\fP .br Displays a list of the currently enabled options for the BMC. .br .TP \fIsetenables\fP <\fBoption\fR>=[\fBon\fR|\fBoff\fR] .br Enables or disables the given \fIoption\fR. This command is only supported over the system interface according to the IPMI specification. Currently supported values for \fIoption\fR include: .RS .TP \fIrecv_msg_intr\fP .br Receive Message Queue Interrupt .TP \fIevent_msg_intr\fP .br Event Message Buffer Full Interrupt .TP \fIevent_msg\fP .br Event Message Buffer .TP \fIsystem_event_log\fP .br System Event Logging .TP \fIoem0\fP .br OEM\-Defined option #0 .TP \fIoem1\fP .br OEM\-Defined option #1 .TP \fIoem2\fP .br OEM\-Defined option #2 .RE .RE .TP \fIchannel\fP .RS .TP \fIauthcap\fP <\fBchannel number\fR> <\fBmax priv\fR> Displays information about the authentication capabilities of the selected channel at the specified privilege level. .RS .TP Possible privilege levels are: .br \fI1\fP Callback level .br \fI2\fP User level .br \fI3\fP Operator level .br \fI4\fP Administrator level .br \fI5\fP OEM Proprietary level .RE .TP \fIinfo\fP [\fBchannel number\fR] Displays information about the selected channel. If no channel is given it will display information about the currently used channel: .RS .PP > ipmitool channel info .br Channel 0xf info: .br Channel Medium Type : System Interface .br Channel Protocol Type : KCS .br Session Support : session\-less .br Active Session Count : 0 .br Protocol Vendor ID : 7154 .RE .TP \fIgetaccess\fP <\fBchannel number\fR> [<\fBuserid\fR>] .br Configure the given userid as the default on the given channel number. When the given channel is subsequently used, the user is identified implicitly by the given userid. .TP \fIsetaccess\fP <\fBchannel number\fR> <\fBuserid\fR> [<\fBcallin\fR=\fBon\fR|\fBoff\fR>] [<\fBipmi\fR=\fBon\fR|\fBoff\fR>] [<\fBlink\fR=\fBon\fR|\fBoff\fR>] [<\fBprivilege\fR=\fBlevel\fR>] .br Configure user access information on the given channel for the given userid. .TP \fIgetciphers\fP <\fBipmi\fR|\fBsol\fR> [<\fBchannel\fR>] .br Displays the list of cipher suites supported for the given application (ipmi or sol) on the given channel. .RE .TP \fIchassis\fP .RS .TP \fIstatus\fP .br Displays information regarding the high\-level status of the system chassis and main power subsystem. .TP \fIpoh\fP .br This command will return the Power\-On Hours counter. .TP \fIidentify\fP <\fBinterval\fR> Control the front panel identify light. Default is 15. Use 0 to turn off. .TP \fIrestart_cause\fP .br Query the chassis for the cause of the last system restart. .TP \fIpolicy\fP .br Set the chassis power policy in the event power failure. .RS .TP \fIlist\fP .br Return supported policies. .TP \fIalways\-on\fP .br Turn on when power is restored. .TP \fIprevious\fP .br Returned to previous state when power is restored. .TP \fIalways\-off\fP .br Stay off after power is restored. .RE .TP \fIpower\fP .br Performs a chassis control command to view and change the power state. .RS .TP \fIstatus\fP .br Show current chassis power status. .TP \fIon\fP .br Power up chassis. .TP \fIoff\fP .br Power down chassis into soft off (S4/S5 state). \fBWARNING\fR: This command does not initiate a clean shutdown of the operating system prior to powering down the system. .TP \fIcycle\fP .br Provides a power off interval of at least 1 second. No action should occur if chassis power is in S4/S5 state, but it is recommended to check power state first and only issue a power cycle command if the system power is on or in lower sleep state than S4/S5. .TP \fIreset\fP .br This command will perform a hard reset. .TP \fIdiag\fP .br Pulse a diagnostic interrupt (NMI) directly to the processor(s). .TP \fIsoft\fP .br Initiate a soft\-shutdown of OS via ACPI. This can be done in a number of ways, commonly by simulating an overtemperture or by simulating a power button press. It is necessary for there to be Operating System support for ACPI and some sort of daemon watching for events for this soft power to work. .RE .TP \fIbootdev\fP <\fBdevice\fR> [<\fBclear\-cmos\fR=\fByes\fR|\fBno\fR>] .br Request the system to boot from an alternate boot device on next reboot. The \fIclear\-cmos\fP option, if supplied, will instruct the BIOS to clear its CMOS on the next reboot. .RS .TP Currently supported values for are: .TP \fInone\fP .br Do not change boot device .TP \fIpxe\fP .br Force PXE boot .TP \fIdisk\fP .br Force boot from BIOS default boot device .TP \fIsafe\fP .br Force boot from BIOS default boot device, request Safe Mode .TP \fIdiag\fP .br Force boot from diagnostic partition .TP \fIcdrom\fP .br Force boot from CD/DVD .TP \fIbios\fP .br Force boot into BIOS setup .RE .RE .TP \fIevent\fP .RS .TP <\fBpredefined event number\fR> .br Send a pre\-defined event to the System Event Log. The following events are included as a means to test the functionality of the System Event Log component of the BMC (an entry will be added each time the event \fIn\fP command is executed). Currently supported values for \fIn\fR are: .br \fI1\fP Temperature: Upper Critical: Going High .br \fI2\fP Voltage Threshold: Lower Critical: Going Low .br \fI3\fP Memory: Correctable ECC Error Detected .br \fBNOTE\fR: These pre\-defined events will likely not produce "accurate" SEL records for a particular system because they will not be correctly tied to a valid sensor number, but they are sufficient to verify correct operation of the SEL. .TP \fIfile\fP <\fBfilename\fR> .br Event log records specified in \fIfilename\fR will be added to the System Event Log. The format of each line in the file is as follows: <{\fIEvM Revision\fP} {\fISensor Type\fP} {\fISensor Num\fP} {\fIEvent Dir/Type\fP} {\fIEvent Data 0\fP} {\fIEvent Data 1\fP} {\fIEvent Data 2\fP}>[\fI# COMMENT\fP] Note: The Event Dir/Type field is encoded with the event direction as the high bit (bit 7) and the event type as the low 7 bits. e.g.: .br 0x4 0x2 0x60 0x1 0x52 0x0 0x0 # Voltage threshold: Lower Critical: Going Low .TP <\fBsensorid\fR> <\fBstate\fR> [<\fBeventdir\fR>] Generate a custom event based on existing sensor information. The optional event direction can be either \fIassert\fP or \fIdeassert\fP and defaults to assert. To get a list of possible states for a sensor supply a state of \fBlist\fR on the command line. Each sensor may be different but some states will have pre\-defined shortcuts. For example: .RS .PP > ipmitool \-I open event p0.t_core .br Finding sensor p0.t_core... ok .br Sensor States: .br lnr : Lower Non\-Recoverable .br lcr : Lower Critical .br lnc : Lower Non\-Critical .br unc : Upper Non\-Critical .br ucr : Upper Critical .br unr : Upper Non\-Recoverable .RE .RS .PP > ipmitool \-I open event ps0.prsnt .br Finding sensor ps0.prsnt... ok .br Sensor States: .br Device Absent .br Device Present .br State State Shortcuts: .br present absent .br assert deassert .br limit nolimit .br fail nofail .br yes no .br on off .br up down .br .RE .RE .TP \fIexec\fP <\fBfilename\fR> .RS Execute ipmitool commands from \fIfilename\fR. Each line is a complete command. The syntax of the commands are defined by the COMMANDS section in this manpage. Each line may have an optional comment at the end of the line, delimited with a `#' symbol. e.g., a command file with two lines: sdr list # get a list of sdr records .br sel list # get a list of sel records .RE .TP \fIfru\fP .RS .TP \fIedit\fP <\fBfru id\fR> [<\fBoem\fR> <\fBrecord\fR> <\fBformat\fR>] [<\fBargs\fR>] .br This command edits the data found in the multirecord area. Support for OEM specific records is limited. .TP \fIprint\fP .br This command will read all Field Replaceable Unit (FRU) inventory data and extract such information as serial number, part number, asset tags, and short strings describing the chassis, board, or product. .RE .TP \fIi2c\fP <\fBi2caddr\fR> <\fBread bytes\fR> [<\fBwrite data\fR>] .br This will allow you to execute raw I2C commands with the Master Write\-Read IPMI command. .TP \fIisol\fP .RS .TP \fIinfo\fP .br Retrieve information about the Intel IPMI v1.5 Serial\-Over\-LAN configuration. .TP \fIset\fP <\fBparameter\fR> <\fBvalue\fR> .br Configure parameters for Intel IPMI v1.5 Serial\-over\-LAN. .RS .TP Valid parameters and values are: .br .TP \fIenabled\fP true, false. .TP \fIprivilege\-level\fP user, operator, admin, oem. .TP \fIbit\-rate\fP 9.6, 19.2, 38.4, 57.6, 115.2. .RE .TP \fIactivate\fP .br Causes ipmitool to enter Intel IPMI v1.5 Serial Over LAN mode. An RMCP+ connection is made to the BMC, the terminal is set to raw mode, and user input is sent to the serial console on the remote server. On exit, the the SOL payload mode is deactivated and the terminal is reset to its original settings. .RS Special escape sequences are provided to control the SOL session: .RS .TP \fI~.\fP Terminate connection .TP \fI~^Z\fP Suspend ipmitool .TP \fI~^X\fP Suspend ipmitool, but don't restore tty on restart .TP \fI~B\fP Send break .TP \fI~~\fP Send the escape character by typing it twice .TP \fI~?\fP Print the supported escape sequences .RE Note that escapes are only recognized immediately after newline. .RE .RE .TP \fIlan\fP .RS These commands will allow you to configure IPMI LAN channels with network information so they can be used with the ipmitool \fIlan\fP and \fIlanplus\fP interfaces. \fINOTE\fR: To determine on which channel the LAN interface is located, issue the `channel info \fInumber\fR' command until you come across a valid 802.3 LAN channel. For example: .br > ipmitool \-I open channel info 1 .br Channel 0x1 info: .br Channel Medium Type : 802.3 LAN Channel Protocol Type : IPMB\-1.0 Session Support : session\-based Active Session Count : 8 Protocol Vendor ID : 7154 .TP \fIprint\fP <\fBchannel\fR> .br Print the current configuration for the given channel. .TP \fIset\fP <\fBchannel\fR> <\fBparameter\fR> .br Set the given parameter on the given channel. Valid parameters are: .RS .TP \fIipaddr\fP <\fBx.x.x.x\fR> .br Set the IP address for this channel. .TP \fInetmask\fP <\fBx.x.x.x\fR> .br Set the netmask for this channel. .TP \fImacaddr\fP <\fBxx:xx:xx:xx:xx:xx\fR> .br Set the MAC address for this channel. .TP \fIdefgw ipaddr\fP <\fBx.x.x.x\fR> .br Set the default gateway IP address. .TP \fIdefgw macaddr\fP <\fBxx:xx:xx:xx:xx:xx\fR> .br Set the default gateway MAC address. .TP \fIbakgw ipaddr\fP <\fBx.x.x.x\fR> .br Set the backup gateway IP address. .TP \fIbakgw macaddr\fP <\fBxx:xx:xx:xx:xx:xx\fR> .br Set the backup gateway MAC address. .TP \fIpassword\fP <\fBpass\fR> .br Set the null user password. .TP \fIsnmp\fP <\fBcommunity string\fR> .br Set the SNMP community string. .TP \fIuser\fP .br Enable user access mode for userid 1 (issue the `user' command to display information about userids for a given channel). .TP \fIaccess\fP <\fBon|off\fR> .br Set LAN channel access mode. .TP \fIipsrc\fP <\fBsource\fR> .br Set the IP address source: .br \fInone\fP unspecified .br \fIstatic\fP manually configured static IP address .br \fIdhcp\fP address obtained by BMC running DHCP .br \fIbios\fP address loaded by BIOS or system software .TP \fIarp respond\fP <\fBon\fR|\fBoff\fR> .br Set BMC generated ARP responses. .TP \fIarp generate\fP <\fBon\fR|\fBoff\fR> .br Set BMC generated gratuitous ARPs. .TP \fIarp interval\fP <\fBseconds\fR> .br Set BMC generated gratuitous ARP interval. .TP \fIvlan id\fP <\fBoff\fR|\fBid\fR> .br Disable VLAN operation or enable VLAN and set the ID. .br ID: value of the virtual lan identifier between 1 and 4094 inclusive. .TP \fIvlan priority\fP <\fBpriority\fR> .br Set the priority associated with VLAN frames. .br ID: priority of the virtual lan frames between 0 and 7 inclusive. .TP \fIauth\fP <\fBlevel\fR,\fB...\fR> <\fBtype\fR,\fB...\fR> .br Set the valid authtypes for a given auth level. .br Levels: callback, user, operator, admin .br Types: none, md2, md5, password, oem .TP \fIcipher_privs\fP <\fBprivlist\fR> .br Correlates cipher suite numbers with the maximum privilege level that is allowed to use it. In this way, cipher suites can restricted to users with a given privilege level, so that, for example, administrators are required to use a stronger cipher suite than normal users. The format of \fIprivlist\fR is as follows. Each character represents a privilege level and the character position identifies the cipher suite number. For example, the first character represents cipher suite 1 (cipher suite 0 is reserved), the second represents cipher suite 2, and so on. \fIprivlist\fR must be 15 characters in length. Characters used in \fIprivlist\fR and their associated privilege levels are: \fIX\fP Cipher Suite Unused .br \fIc\fP CALLBACK .br \fIu\fP USER .br \fIo\fP OPERATOR .br \fIa\fP ADMIN .br \fIO\fP OEM .br So, to set the maximum privilege for cipher suite 1 to USER and suite 2 to ADMIN, issue the following command: > ipmitool \-I \fIinterface\fR lan set \fIchannel\fR cipher_privs uaXXXXXXXXXXXXX .RE .RE .TP \fIpef\fP .RS .TP \fIinfo\fP .br This command will query the BMC and print information about the PEF supported features. .TP \fIstatus\fP .br This command prints the current PEF status (the last SEL entry processed by the BMC, etc). .TP \fIpolicy\fP .br This command lists the PEF policy table entries. Each policy entry describes an alert destination. A policy set is a collection of table entries. PEF alert actions reference policy sets. .TP \fIlist\fP .br This command lists the PEF table entries. Each PEF entry relates a sensor event to an action. When PEF is active, each platform event causes the BMC to scan this table for entries matching the event, and possible actions to be taken. Actions are performed in priority order (higher criticality first). .RE .TP \fIraw\fP <\fBnetfn\fR> <\fBcmd\fR> [<\fBdata\fR>] .br This will allow you to execute raw IPMI commands. For example to query the POH counter with a raw command: > ipmitool \-v raw 0x0 0xf .br RAW REQ (netfn=0x0 cmd=0xf data_len=0) .br RAW RSP (5 bytes) .br 3c 72 0c 00 00 .TP \fIsdr\fP .RS .TP \fIget\fP <\fBid\fR> ... [<\fBid\fR>] .br Prints information for sensor data records specified by sensor id. .TP \fIinfo\fP .br This command will query the BMC for SDR information. .TP \fItype\fP <\fBsensor type\fP> This command will display all records from the SDR of a specific type. Run with type \fIlist\fP to see the list of available types. For example to query for all Temperature sensors: > ipmitool sdr type Temperature .br Baseboard Temp | 30h | ok | 7.1 | 28 degrees C .br FntPnl Amb Temp | 32h | ok | 12.1 | 24 degrees C .br Processor1 Temp | 98h | ok | 3.1 | 57 degrees C .br Processor2 Temp | 99h | ok | 3.2 | 53 degrees C .TP \fIlist\fP | \fIelist\fP [<\fBall\fR|\fBfull\fR|\fBcompact\fR|\fBevent\fR|\fBmcloc\fR|\fBfru\fR|\fBgeneric\fR>] .br This command will read the Sensor Data Records (SDR) and extract sensor information of a given type, then query each sensor and print its name, reading, and status. If invoked as \fIelist\fP then it will also print sensor number, entity id and instance, and asserted discrete states. The default output will only display \fIfull\fP and \fIcompact\fP sensor types, to see all sensors use the \fIall\fP type with this command. .RS .TP Valid types are: .RS .TP \fIall\fP .br All SDR records (Sensor and Locator) .TP \fIfull\fP .br Full Sensor Record .TP \fIcompact\fP .br Compact Sensor Record .TP \fIevent\fP .br Event\-Only Sensor Record .TP \fImcloc\fP .br Management Controller Locator Record .TP \fIfru\fP .br FRU Locator Record .TP \fIgeneric\fP .br Generic SDR records .RE .RE .TP \fIentity\fP <\fBid\fR>[.<\fBinstance\fR>] .br Displays all sensors associated with an entity. Get a list of valid entity ids on the target system by issuing the \fIsdr elist\fP command. A list of all entity ids can be found in the IPMI specifications. .TP \fIdump\fP <\fBfile\fR> .br Dumps raw SDR data to a file. This data file can then be used as a local SDR cache of the remote managed system with the \fI\-S \fP option on the ipmitool command line. This can greatly improve performance over system interface or remote LAN. .RE .TP \fIsel\fP .br NOTE: SEL entry\-times are displayed as `Pre\-Init Time\-stamp' if the SEL clock needs to be set. Ensure that the SEL clock is accurate by invoking the \fIsel time get\fP and \fIsel time set