RegistryStore
更新时间： 2026/06/26
在Gitcode上查看源码ResourceDefinition
uris
/redfish/v1/RegistryStore/Messages/en/{file_id}
properties
| 名称 | 类型 | 是否只读 | 取值范围/枚举值 | 说明 |
|---|---|---|---|---|
| @odata.type | string | true | - | 注册文件资源类型 |
| Id | string | true | - | 注册文件资源ID |
| Name | string | true | - | 注册文件的名称 |
| Language | string | true | - | 注册文件的语言 |
| Description | string | true | - | 注册文件的描述信息 |
| RegistryPrefix | string | true | - | 注册文件名称前缀 |
| RegistryVersion | string | true | - | 注册文件版本 |
| OwningEntity | string | true | - | 注册文件所属公司 |
| Messages | object | true | - | |
| Messages.MessageId | string | true | - | 事件ID |
| Messages.Description | string | true | - | 事件对象的描述信息 |
| Messages.Message | string | true | - | 事件描述 |
| Messages.Severity | string | true | OK,Warning,Critical | 严重性级别 ● OK ● Warning ● Critical |
| Messages.NumberOfArgs | number | true | - | 事件描述参数个数 |
| Messages.ParamTypes | array | true | - | 参数类型列表 |
| Messages.Resolution | string | true | - | 事件处理建议 |
| Messages.Oem | object | true | - | 自定义属性 |
| Messages.Oem.Public | object | true | - | 自定义属性 |
| Messages.Oem.Public.@odata.type | string | true | - | 事件资源类型 |
| Messages.Oem.Public.EventId | string | true | - | 事件码 |
| Messages.Oem.Public.EventName | string | true | - | 事件名 |
| Messages.Oem.Public.EventEffect | string | true | - | 事件影响 |
| Messages.Oem.Public.EventCause | string | true | - | 事件原因 |
supported_methods
- GET
HTTP methods
GET
命令功能
查询归档的 BMC 事件上报注册文件资源
命令格式
URL: https://device_ip/redfish/v1/RegistryStore/Messages/en/file_id
请求头:
X-Auth-Token: 123456789***********************请求消息体: 无
参数说明
| 参数 | 参数说明 | 取值 |
|---|---|---|
| device_ip | 登录设备的IP地址 | IPv4或IPv6地址 |
| file_id | BMC事件上报注册文件名 | 可通过单个归档资源查询接口：redfish/v1/Registries/registries_id查询BMCEvents时获得 |
| auth_value | 执行该GET请求时，必须在"Headers"中携带"X-Auth-Token"值用于鉴权 | 可通过/redfish/v1/SessionService/Sessions创建会话时获得 |
使用指南
无
使用实例
请求样例：
http
GET https://device_ip/redfish/v1/RegistryStore/Messages/en/iBMCEvents.v2_8_3.json请求头：
X-Auth-Token: 123456789***********************响应样例：
json
{
"@odata.type": "#Message.v1_0_0.Message",
"Id": "iBMCEvents.2.8.3",
"Name": "iBMC Event Registry",
"Language": "en",
"Description": "This registry defines the events for Redfish",
"RegistryPrefix": "iBMCEvents",
"RegistryVersion": "2.8.3",
"OwningEntity": "",
"Messages": {
"ResourceUpdated": {
"Description": "Resource updated.",
"Message": "Resource updated.",
"Severity": "OK",
"NumberOfArgs": 0,
"ParamTypes": [],
"Resolution": null,
"Oem": {
"Public": {
"@odata.type": "#HwBMCEvent.v1_0_0.HwBMCEvent",
"EventId": null,
"EventName": null,
"EventEffect": null,
"EventCause": null
}
}
},
"BMCNTPSynchronizeFailed": {
"Description": null,
"Message": "iBMC failed to synchronize time with the NTP server.",
"Severity": "OK",
"NumberOfArgs": 0,
"ParamTypes": [],
"Resolution": "1. Check whether the NTP server is configured correctly. 2. Check communication between the iBMC and the NTP server. 3. Restart the NTP service on the iBMC.",
"Oem": {
"Public": {
"@odata.type": "#HwBMCEvent.v1_0_0.HwBMCEvent",
"EventId": "0x1A00002B",
"EventName": "BMCNTPSynchronizeFailed",
"EventEffect": null,
"EventCause": null
}
}
},
"ChassisInletOverTempMajor": {
"Description": null,
"Message": "The air inlet temperature (%1 degrees C) exceeds the overtemperature threshold (%2 degrees C).",
"Severity": "Warning",
"NumberOfArgs": 2,
"ParamTypes": [
"string",
"string"
],
"Resolution": "1. Check the equipment room temperature. 2. Check for air inlet blockage. 3. Check for vacant slots and missing air baffles. Install filler panels in vacant slots and air baffles.",
"Oem": {
"Public": {
"@odata.type": "#HwBMCEvent.v1_0_0.HwBMCEvent",
"EventId": "0x12000003",
"EventName": "ChassisInletOverTempMajor",
"EventEffect": "The system stability is affected.",
"EventCause": "1. The ambient temperature is too high. 2. The air inlet is blocked. 3. The server has empty slots or spaces. 4. The component holding the air inlet sensor is faulty."
}
}
}
}
}响应码：200