修订记录

openUBMC版本号	修订日期	修订人	修订内容
25.06	2025/06/26	pengqiang-gs	初稿，新增命令详情

基本信息

功能说明

立即发送事件到指定目的地。 This command is used to send an alert to the destination specified by the destination selector.

权限

ReadOnly

命令信息

请求信息

字节顺序	域取值说明
1	Channel number. (This value is required to select which configuration parameters are to be used to send the Alert.) [7:4] - reserved [3:0] - Channel number. Note: BMC stores the ‘Alert immediate status’ for each channel that can send alert.
2	Destination Selector/ Operation [7:6] - Operation 00b = Initiate alert 01b = Get Alert Immediate status 10b = Clear Alert Immediate status (sets status to 00h) 11b = reserved [5:4] - Reserved [3:0] - destination selector. Selects which alert destination should go to. 0h = use volatile destination info. 1h-Fh = non-volatile destination. Note: If Operation is ‘Get Alert Immediate status’ or ‘Clear Alert Immediate Status’ bits [3:0] are reserved.
3	Alert String Selector Selects which Alert String, if any, to use with the alert. [7] 0b = don’t send an Alert String 1b = send Alert String identified by following string selector. [6:0] - string selector. 000_0000b = use volatile Alert String. 01h-7Fh = non-volatile string selector.
(4:11)	The following “Platform Event Parameters” ( bytes 4:11) can be used to fill in the corresponding event data fields of a Platform Event Trap. When supported, all bytes (4:11) must be supplied. Implementation of this capability is OPTIONAL but highly recommended for IPMI v2.0 implementations. See Event Request Message Fields, for specification of the individual fields. Byte4 = Generator ID Byte5 = EvMRev Byte6 = Sensor Type Byte7 = Sensor # Byte8 = Event Dir

响应信息

字节顺序	域取值说明
1	Completion Code. Generic codes, plus following command-specific completion codes: 81h = Alert Immediate rejected due to alert already in progress. 82h = Alert Immediate rejected due to IPMI messaging session active on this channel. 83h = Platform Event Parameters (4:11) not supported.
2	Following byte is only returned when Operation in request is set to “Get Alert Immediate status” Alert Immediate Status SMS can poll this status to determine present state of the immediate alert. 00h = No status. >Note: A BMC implementation is allowed (but not required) to abort the Alert Immediate command due to a channel parameter configuration, power, or reset state changes that occur while the Alert Immediate command is being processed. In which case the BMC will return the ‘no status’ state. 01h = Alert was Normal End. This will also be returned if one or more attempts failed, but the last attempt was successful. 02h = “Call Retry” (Dial connection) retries failed. 03h = Alert failed due to timeouts waiting for acknowledge on all retries. FFh = Alert by this command is in progress. Status pending

字节顺序

域取值说明

Completion Code. Generic codes, plus following command-specific completion codes:
81h = Alert Immediate rejected due to alert already in progress.
82h = Alert Immediate rejected due to IPMI messaging session active on this channel.
83h = Platform Event Parameters (4:11) not supported.

Following byte is only returned when Operation in request is set to “Get Alert Immediate status”

Alert Immediate Status
SMS can poll this status to determine present state of the immediate alert.
00h = No status.
>Note: A BMC implementation is allowed (but not required) to abort the Alert Immediate command due to a channel parameter configuration, power, or reset state changes that occur while the Alert Immediate command is being processed. In which case the BMC will return the ‘no status’ state.

01h = Alert was Normal End. This will also be returned if one or more attempts failed, but the last attempt was successful.

02h = “Call Retry” (Dial connection) retries failed.

03h = Alert failed due to timeouts waiting for acknowledge on all retries.

FFh = Alert by this command is in progress. Status pending

命令样例

样例1：

请求：
响应：

修订记录 ​

基本信息 ​

功能说明 ​

权限 ​

命令信息 ​

请求信息 ​

响应信息 ​

命令样例 ​

样例1： ​

返回到索引 ​