ipmitool(1) ipmitool(1) NAME ipmitool - utility for controlling IPMI-enabled devices SYNOPSIS ipmitool [ ] [ ] := [ | ] Any recognized option is accepted. Conditional options may be ignored or it's usage postponed until shell or exec processes relevant command. := [ -h | -V | -v | -I | -H
| -d | -p | -c | -U | -L | -l | -m | -N | -R | | | ] := [ | | ] Bridging: := -t [ -b | [ -T
| -B ] ] Options used with -I lan: := [ -A ] Options used with -I lanplus: := [ -C | ] Option groups setting same value: := [ -k | -K | -y | -Y ] := [ -f | -a | -P | -E ] := [ -o | -g | -s ] Options used with specific command : := [ -S ] := [ -O ] := [ -e ] 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 OpenIPMI and it is included in standard distributions. On Solaris this driver is called BMC and is included 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. OPTIONS -a Prompt for the remote server password. -A Specify an authentication type to use during IPMIv1.5 lan session activation. Supported types are NONE, PASSWORD, MD2, MD5, or OEM. -b Set destination channel for bridged request. -B Set transit channel for bridged request (dual bridge). -b Set destination channel for bridged request. -B Set transit channel for bridged request. (dual bridge) -c Present output in CSV (comma separated variable) format. This is not available with all commands. -C The remote server authentication, integrity, and encryption algorithms to use for IPMIv2.0 lanplus connections. See table 22-20 in the IPMI v2.0 specification. The default is 17 which specifies RAKP-HMAC-SHA256 authentication, HMAC-SHA256-128 integrity, and AES-CBC-128 encryption algorithms. NOTE: In ipmitool 1.8.18 and earlier the default was 3, which was insecure and was not supported by some more recent BMC implementations. -d N 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. -e Use supplied character for SOL session escape character. The default is to use ~ but this can conflict with ssh sessions. -E The remote server password is specified by the environment variable IPMI_PASSWORD or IPMITOOL_PASSWORD. The IPMITOOL_PASSWORD takes precedence. -f 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. -g Deprecated. Use: -o intelplus -h Get basic usage help from the command line. -H
Remote server address, can be IP address or hostname. This option is required for lan and lanplus interfaces. -I Selects IPMI interface to use. Supported interfaces that are compiled in are visible in the usage help output. -k Use supplied Kg key for IPMIv2.0 authentication. The default is not to use any Kg key. -K Read Kg key from IPMI_KGKEY environment variable. -l Set destination lun for raw commands. -L Force session privilege level. Can be CALLBACK, USER, OPERATOR, ADMINISTRATOR. Default is ADMINISTRATOR. This value is ignored and always set to ADMINISTRATOR when combined with -t target address. -m Set the local IPMB address. The local address defaults to 0x20 or is auto discovered on PICMG platforms when -m is not specified. There should be no need to change the local address for normal operation. -N Specify nr. of seconds between retransmissions of lan/lanplus messages. Defaults are 2 seconds for lan and 1 second for lanplus interfaces. Command raw uses fixed value of 15 seconds. Command sol uses fixed value of 1 second. -o 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 -o list to see a list of current supported OEM types. -O Open selected file and read OEM SEL event descriptions to be used during SEL listings. See examples in contrib dir for file format. -p Remote server UDP port to connect to. Default is 623. -P Remote server password is specified on the command line. If supported it will be obscured in the process list. Note! Specifying the password as a command line option is not recommended. -R Set the number of retries for lan/lanplus interface (default=4). Command raw uses fixed value of one try (no retries). Command hpm uses fixed value of 10 retries. -s Deprecated. Use: -o supermicro -S 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 sdr dump command. -t Bridge IPMI requests to the remote target address. Default is 32. The -L privlvl option is always ignored and value set to ADMINISTRATOR. -T
Set transit address for bridge request (dual bridge). -T Set transit address for bridge request. (dual bridge) -U Remote server username, default is NULL user. -v 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. Using it five times provides details on request and expected reply processing. The hpm commands targetcap compprop abort upgstatus rollback rollbackstatus selftestresult increases the verbosity level -V Display version information. -y Use supplied Kg key for IPMIv2.0 authentication. The key is expected in hexadecimal format and can be used to specify keys with non-printable characters. E.g. '-k PASSWORD' and '-y 50415353574F5244' are equivalent. The default is not to use any Kg key. -Y Prompt for the Kg key for IPMIv2.0 authentication. -z Change Size of Communication Channel. (OEM) 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. 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 lan 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 lanplus interface or the system interface on the local station. For IPMI v1.5, the maximum password length is 16 characters; longer passwords might be truncated or rejected by the server, or rejected by ipmitool. For IPMI v2.0, the maximum password length is 20 characters; longer passwords will be rejected by ipmitool. COMMANDS help 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 Commands: bmc Deprecated. Use mc channel Configure Management Controller channels chassis Get chassis status and set power state dcmi Data Center Management Interface delloem Manage Dell OEM Extensions. echo Used to echo lines to stdout in scripts ekanalyzer run FRU-Ekeying analyzer using FRU files event Send events to MC exec Run list of commands from file firewall Configure Firmware Firewall fru Print built-in FRU and scan for FRU locators fwum Update IPMC using Kontron OEM Firmware Update Manager gendev Read/Write Device associated with Generic Device locators sdr hpm Update HPM components using PICMG HPM.1 file i2c Send an I2C Master Write-Read command and print response ime Upgrade/Query Intel ME firmware isol Configure and connect Intel IPMIv1.5 Serial-over-LAN kontronoem Manage Kontron OEM Extensions lan Configure LAN Channels mc Management Controller status and global enables nm Node Manager pef Configure Platform Event Filtering (PEF) picmg Run a PICMG/ATA extended command power Shortcut to chassis power commands raw Send a RAW IPMI request and print response sdr Print Sensor Data Repository entries and readings sel Print System Event Log (SEL) sensor Print detailed sensor information session Print session information set Set runtime variable for shell and exec shell Launch interactive IPMI shell sol Configure and connect IPMIv2.0 Serial-over-LAN spd Print SPD info from remote I2C device sunoem Manage Sun OEM Extensions tsol Configure and connect Tyan IPMIv1.5 Serial-over-LAN user Configure Management Controller users channel authcap Displays information about the authentication capabilities of the selected channel at the specified privilege level. Possible privilege levels are: 1 Callback level 2 User level 3 Operator level 4 Administrator level 5 OEM Proprietary level 15 No access info [channel number] Displays information about the selected channel. If no channel is given it will display information about the currently used channel. > ipmitool channel info Channel 0xf info: Channel Medium Type : System Interface Channel Protocol Type : KCS Session Support : session-less Active Session Count : 0 Protocol Vendor ID : 7154 getaccess [] 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. setaccess [] [] [] [] Configure user access information on the given channel for the given userid. getciphers [] Displays the list of cipher suites supported for the given application (ipmi or sol) on the given channel. chassis status Status information related to power, buttons, cooling, drives and faults. power status on off cycle reset diag soft identify [|force] Identify interval. Default is 15 seconds. 0 - Off force - To turn on indefinitely policy What to do when power is restored. list Show available options. always-on previous always-off restart_cause Last restart cause. poh Get power on hours. bootdev none Do not change boot device order. pxe Force PXE boot. disk Force boot from default Hard-drive. safe Force boot from default Hard-drive, request Safe Mode. diag Force boot from Diagnostic Partition. cdrom Force boot from CD/DVD. bios Force boot into BIOS Setup. floppy Force boot from Floppy/primary removable media. bootmbox get [text] [block ] Read the Boot Initiator Mailbox in hex dump or in text mode. By default the whole mailbox is read. If block number is specified, that particular block is read. For block 0 or when the whole mailbox is read, the Boot Initiator IANA Enterprise Number and the corresponding enterprise name are printed. bootmbox set text [block ] "" Write the specified or the entire Boot Initiator Mailbox in text mode. It is required to specify a decimal IANA Enterprise Number recognized by the boot initiator on the target system. Refer to your target system manufacturer for details. The rest of the arguments are a text string. When single block write is requested, the total length of may not exceed 13 bytes for block 0, or 16 bytes otherwise. bootmbox set [block ] [ ...] Same as above, but the arguments after IANA PEN are separate data byte values separated by spaces. bootparam get [] Get value of system boot option number . Some boot options (e.g. option 7) can also take an optional numeric parameter. bootparam set bootflag [options=...] Set a boot flag. Valid devices are: force_pxe Force PXE boot force_disk Force boot from default Hard-drive force_safe Force boot from default Hard-drive, request Safe Mode force_diag Force boot from Diagnostic Partition force_cdrom Force boot from CD/DVD force_bios Force boot into BIOS Setup Valid options are: PEF Clear valid bit on reset/power cycle cause by PEF timeout Automatically clear boot flag valid bit on timeout watchdog Clear valid bit on reset/power cycle cause by watchdog reset Clear valid bit on push button reset/soft reset power Clear valid bit on power up via power push button or wake event selftest Get the chassis self-test results dcmi discover This command is used to discover supported capabilities in DCMI. power Platform power limit command options are: reading Get power related readings from the system. get_limit Get the configured power limits. set_limit Set a power limit option. Possible parameters/values are: action Exception Actions are taken as "No Action", "Hard Power Off system and log events to SEL", or "Log event to SEL only". limit Power Limit Requested in Watts. correction Correction Time Limit in milliseconds. sample Statistics Sampling period in seconds. activate Activate the set power limit. deactivate Deactivate the set power limit. sensors Prints the available DCMI sensors. asset_tag Prints the platforms asset tag. set_asset_tag Sets the platforms asset tag get_mc_id_string Get management controller identifier string. set_mc_id_string Set management controller identifier string. The maximum length is 64 bytes including a null terminator. thermalpolicy [] Thermal Limit policy get/set. The commands are: Get Get Thermal Limit values. entityID is the physical entity that a sensor or device is associated with. instanceID is a particular instance of an entity. Entity Instance can be in one of two ranges, system-relative or device-relative. For example, a system with four processors could use an Entity Instance value of "0" to identify the first processor. Set Set Thermal Limit values. entityID is the physical entity that a sensor or device is associated with. instanceID is a particular instance of an entity. Entity Instance can be in one of two ranges, system-relative or device-relative. For example, a system with four processors could use an Entity Instance value of "0" to identify the first processor. get_temp_reading Get Temperature Sensor Readings. get_conf_param Get DCMI Configuration Parameters. set_conf_param Set DCMI Configuration Parameters. The Configuration Parameters are: activate_dhcp Activate/restart DHCP dhcp_config Discover DHCP Configuration. init Set DHCP Initial timeout interval, in seconds. The recommended default is four seconds. timeout Set DHCP Server contact timeout interval, in seconds. The recommended default timeout is two minutes. retry Set DHCP Server contact retry interval, in seconds. The recommended default timeout is sixty-four seconds. oob_discover Ping/Pong Message for DCMI Discovery. delloem The delloem commands provide information on Dell-specific features. setled {b:d.f} {state..} Sets the drive backplane LEDs for a device. {b:d.f} = PCI Address of device (eg. 06:00.0) {state} = one or more of the following: online | present | hotspare | identify | rebuilding | fault | predict | critical | failed lcd set {mode}|{lcdqualifier}|{errordisplay} Allows you to set the LCD mode and user-defined string. lcd set mode {none}|{modelname}|{ipv4address}|{macaddress}| {systemname}|{servicetag}|{ipv6address}| {ambienttemp}|{systemwatt}|{assettag}| {userdefined} Allows you to set the LCD display mode to any of the preceding parameters. lcd set lcdqualifier {watt}|{btuphr}| {celsius}|{fahrenheit} Allows you to set the unit for the system ambient temperature mode. lcd set errordisplay {sel}|{simple} Allows you to set the error display. lcd info Displays the LCD screen information. lcd set vkvm {active}|{inactive} Allows you to set the vKVM status to active or inactive. When it is active and session is in progress, a message appears on LCD. lcd status Displays the LCD status for vKVM display active or inactive and Front Panel access mode (viewandmodify, view-only or disabled). mac Displays the information about the system NICs. mac list Displays the NIC MAC address and status of all NICs. It also displays the DRAC/iDRAC MAC address. mac get Displays the selected NICs MAC address and status. lan Displays the information of Lan. lan set Sets the NIC selection mode (dedicated, shared with lom1, shared with lom2,shared with lom3,shared with lom4,shared with failover lom1,shared with failover lom2,shared with failover lom3,shared with failover lom4,shared with Failover all loms, shared with Failover None). lan get Returns the current NIC selection mode (dedicated, shared with lom1, shared with lom2, shared with lom3, shared with lom4,shared with failover lom1, shared with failover lom2,shared with failover lom3,shared with failover lom4,shared with Failover all loms,shared with Failover None). lan get active Returns the current active NIC (dedicated, LOM1, LOM2, LOM3 or LOM4). powermonitor Displays power tracking statistics. powermonitor clear cumulativepower Reset cumulative power reading. powermonitor clear peakpower Reset peak power reading. powermonitor powerconsumption | Displays the power consumption in watt or btuphr. powermonitor powerconsumptionhistory | Displays the power consumption history in watt or btuphr. powermonitor getpowerbudget | Displays the power cap in watt or btuphr. powermonitor setpowerbudget Allows you to set the power cap in watt, BTU/hr or percentage. powermonitor enablepowercap Enables set power cap. powermonitor disablepowercap Disables set power cap. vFlash info Card Shows Extended SD Card information. echo For echoing lines to stdout in scripts. ekanalyzer [] ... NOTE : This command can support a maximum of 8 files per command line filename1 : binary file that stores FRU data of a Carrier or an AMC module filename2 : binary file that stores FRU data of an AMC module. These binary files can be generated from command: ipmitool fru read filename3 : configuration file used for configuring On-Carrier Device ID or OEM GUID. This file is optional. xx : indicates the type of the file. It can take the following value: oc : On-Carrier device a1 : AMC slot A1 a2 : AMC slot A2 a3 : AMC slot A3 a4 : AMC slot A4 b1 : AMC slot B1 b2 : AMC slot B2 b3 : AMC slot B3 b4 : AMC slot B4 sm : Shelf Manager The available commands for ekanalyzer are: print [] carrier (default) ... Display point to point physical connectivity between carriers and AMC modules. Example: > ipmitool ekanalyzer print carrier oc=fru oc=carrierfru From Carrier file: fru Number of AMC bays supported by Carrier: 2 AMC slot B1 topology: Port 0 =====> On Carrier Device ID 0, Port 16 Port 1 =====> On Carrier Device ID 0, Port 12 Port 2 =====> AMC slot B2, Port 2 AMC slot B2 topology: Port 0 =====> On Carrier Device ID 0, Port 3 Port 2 =====> AMC slot B1, Port 2 *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* From Carrier file: carrierfru On Carrier Device ID 0 topology: Port 0 =====> AMC slot B1, Port 4 Port 1 =====> AMC slot B1, Port 5 Port 2 =====> AMC slot B2, Port 6 Port 3 =====> AMC slot B2, Port 7 AMC slot B1 topology: Port 0 =====> AMC slot B2, Port 0 AMC slot B1 topology: Port 1 =====> AMC slot B2, Port 1 Number of AMC bays supported by Carrier: 2 power ... Display power supply information between carrier and AMC modules. all ... Display both physical connectivity and power supply of each carrier and AMC modules. frushow Convert a binary FRU file into human readable text format. Use -v option to get more display information. summary [] match (default) ... Display only matched results of Ekeying match between an On-Carrier device and an AMC module or between 2 AMC modules. Example: > ipmitool ekanalyzer summary match oc=fru b1=amcB1 a2=amcA2 On-Carrier Device vs AMC slot B1 AMC slot B1 port 0 ==> On-Carrier Device 0 port 16 Matching Result - From On-Carrier Device ID 0 -Channel ID 11 || Lane 0: enable -Link Type: AMC.2 Ethernet -Link Type extension: 1000BASE-BX (SerDES Gigabit) Ethernet link -Link Group ID: 0 || Link Asym. Match: exact match - To AMC slot B1 -Channel ID 0 || Lane 0: enable -Link Type: AMC.2 Ethernet -Link Type extension: 1000BASE-BX (SerDES Gigabit) Ethernet link -Link Group ID: 0 || Link Asym. Match: exact match *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* AMC slot B1 port 1 ==> On-Carrier Device 0 port 12 Matching Result - From On-Carrier Device ID 0 -Channel ID 6 || Lane 0: enable -Link Type: AMC.2 Ethernet -Link Type extension: 1000BASE-BX (SerDES Gigabit) Ethernet link -Link Group ID: 0 || Link Asym. Match: exact match - To AMC slot B1 -Channel ID 1 || Lane 0: enable -Link Type: AMC.2 Ethernet -Link Type extension: 1000BASE-BX (SerDES Gigabit) Ethernet link -Link Group ID: 0 || Link Asym. Match: exact match *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* On-Carrier Device vs AMC slot A2 AMC slot A2 port 0 ==> On-Carrier Device 0 port 3 Matching Result - From On-Carrier Device ID 0 -Channel ID 9 || Lane 0: enable -Link Type: AMC.2 Ethernet -Link Type extension: 1000BASE-BX (SerDES Gigabit) Ethernet link -Link Group ID: 0 || Link Asym. Match: exact match - To AMC slot A2 -Channel ID 0 || Lane 0: enable -Link Type: AMC.2 Ethernet -Link Type extension: 1000BASE-BX (SerDES Gigabit) Ethernet link -Link Group ID: 0 || Link Asym. Match: exact match *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* AMC slot B1 vs AMC slot A2 AMC slot A2 port 2 ==> AMC slot B1 port 2 Matching Result - From AMC slot B1 -Channel ID 2 || Lane 0: enable -Link Type: AMC.3 Storage -Link Type extension: Serial Attached SCSI (SAS/SATA) -Link Group ID: 0 || Link Asym. Match: FC or SAS interface {exact match} - To AMC slot A2 -Channel ID 2 || Lane 0: enable -Link Type: AMC.3 Storage -Link Type extension: Serial Attached SCSI (SAS/SATA) -Link Group ID: 0 || Link Asym. Match: FC or SAS interface {exact match} *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* unmatch ... Display the unmatched results of Ekeying match between an On-Carrier device and an AMC module or between 2 AMC modules all ... Display both matched result and unmatched results of Ekeying match between two cards or two modules. event Send a pre-defined test 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 N command is executed). Currently supported values for N are: 1 Temperature: Upper Critical: Going High 2 Voltage Threshold: Lower Critical: Going Low 3 Memory: Correctable ECC NOTE: 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. file Event log records specified in will be added to the System Event Log. The format of each line in the file is as follows: <{EvM Revision} {Sensor Type} {Sensor Num} {Event Dir/Type} {Event Data 0} {Event Data 1} {Event Data 2}>[# COMMENT] e.g.: 0x4 0x2 0x60 0x1 0x52 0x0 0x0 # Voltage threshold: Lower Critical: Going Low EvM Revision - The "Event Message Revision" is 0x04 for messages that comply with the IPMI 2.0 Specification and 0x03 for messages that comply with the IPMI 1.0 Specification. Sensor Type - Indicates the Event Type or Class. Sensor Num - Represents the 'sensor' within the management controller that generated the Event Message. Event Dir/Type - This field is encoded with the event direction as the high bit (bit 7) and the event type as the low 7 bits. Event direction is 0 for an assertion event and 1 for a deassertion event. See the IPMI 2.0 specification for further details on the definitions for each field. Get a list of all the possible Sensor States and pre- defined Sensor State Shortcuts available for a particular sensor. sensorid is the character string representation of the sensor and must be enclosed in double quotes if it includes white space. Several different commands including ipmitool sensor list may be used to obtain a list that includes the sensorid strings representing the sensors on a given system. > ipmitool -I open event "PS 2T Fan Fault" list Finding sensor PS 2T Fan Fault... ok Sensor States: State Deasserted State Asserted Sensor State Shortcuts: present absent assert deassert limit nolimit fail nofail yes no on off up down [] Generate a custom event based on existing sensor information. The optional event direction can be either assert (the default) or deassert. > ipmitool event "PS 2T Fan Fault" "State Asserted" Finding sensor PS 2T Fan Fault... ok 0 | Pre-Init Time-stamp | Fan PS 2T Fan Fault | State Asserted > ipmitool event "PS 2T Fan Fault" "State Deasserted" Finding sensor PS 2T Fan Fault... ok 0 | Pre-Init Time-stamp | Fan PS 2T Fan Fault | State Desserted exec Execute ipmitool commands from filename. 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 sel list # get a list of sel records firewall This command supports the Firmware Firewall capability. It may be used to add or remove security-based restrictions on certain commands/command sub-functions or to list the current firmware firewall restrictions set on any commands. For each firmware firewall command listed below, parameters may be included to cause the command to be executed with increasing granularity on a specific LUN, for a specific NetFn, for a specific IPMI Command, and finally for a specific command's sub-function (see Appendix H in the IPMI 2.0 Specification for a listing of any sub-function numbers that may be associated with a particular command). Parameter syntax and dependencies are as follows: [] [ [ []]]] Note that if "netfn " is specified, then "lun " must also be specified; if "command " is specified, then "netfn " (and therefore "lun ") must also be specified, and so forth. "channel " is an optional and standalone parameter. If not specified, the requested operation will be performed on the current channel. Note that command support may vary from channel to channel. Firmware firewall commands: info [] List firmware firewall information for the specified LUN, NetFn, and Command (if supplied) on the current or specified channel. Listed information includes the support, configurable, and enabled bits for the specified command or commands. Some usage examples: info [] [] This command will list firmware firewall information for all NetFns for the specified LUN on either the current or the specified channel. info [] [ [ ] This command will print out all command information for a single LUN/NetFn pair. info [] [ [ [] [ [ []]]] Print out information for a specific sub-function. enable [] This command is used to enable commands for a given NetFn/LUN combination on the specified channel. disable [] [force] This command is used to disable commands for a given NetFn/LUN combination on the specified channel. Great care should be taken if using the "force" option so as not to disable the "Set Command Enables" command. reset [] This command may be used to reset the firmware firewall back to a state where all commands and command sub- functions are enabled. fru print 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. read fru id is the digit ID of the FRU (see output of 'fru print'). fru file is the absolute pathname of a file in which to dump the binary FRU data pertaining to the specified FRU entity. write fru id is the digit ID of the FRU (see output of 'fru print'). fru file is the absolute pathname of a file from which to pull the binary FRU data before uploading it to the specified FRU. upgEkey Update a multirecord FRU location. fru id is the digit ID of the FRU (see output of 'fru print'). fru file is the absolute pathname of a file from which to pull the binary FRU data to upload into the specified multirecord FRU entity. edit This command provides interactive editing of some supported records, namely PICMG Carrier Activation Record. fru id is the digit ID of the FRU (see output of 'fru print'); default is 0. edit field
This command may be used to set a field string to a new value. It replaces the FRU data found at index in the specified section with the supplied string. fru id is the digit ID of the FRU (see output of 'fru print').
is a string which refers to FRU Inventory Information Storage Areas and may be refer to: c FRU Inventory Chassis Info Area b FRU Inventory Board Info Area p FRU Inventory Product Info Area specifies the field number. Field numbering starts on the first 'english text' field type. For instance in the info area field '0' is and field '2' is ; see IPMI Platform Management FRU Information Storage Definition v1.0 R1.1 for field locations. must be the same length as the string being replaced and must be 8-bit ASCII (0xCx). edit oem iana [] This command edits the data found in the multirecord area. Support for OEM specific records is limited. fwum Update IPMC using Kontron OEM Firmware Update Manager. info Show information about current firmware. status Show status of each firmware bank present in the hardware. download Download specified firmware. upgrade [filename] Install firmware upgrade. If the filename is specified, the file is downloaded first, otherwise the last firmware downloaded is used. rollback Ask IPMC to rollback to previous version. tracelog Show firmware upgrade log. gendev list List All Generic Device Locators. read Read to file eeprom specify by Generic Device Locators. write Write from file eeprom specify by Generic Device Locators hpm PICMG HPM.1 Upgrade Agent check Check the target information. check Display both the existing target version and image version on the screen. download Download specified firmware. upgrade [all] [component ] [activate] Upgrade the firmware using a valid HPM.1 image file. If no option is specified, the firmware versions are checked first and the firmware is upgraded only if they are different. all Upgrade all components even if the firmware versions are the same (use this only after using "check" command). component Upgrade only given component from the given file. component 0 - BOOT component 1 - RTK activate Activate new firmware right away. activate Activate the newly uploaded firmware. targetcap Get the target upgrade capabilities. compprop