@@ -36,13 +36,18 @@ MachineName=tiogapass
36
36
37
37
2 . Transfer the generated BMC image to the BMC via one of the following methods:
38
38
39
- - Method 1: Via scp: Copy the generated BMC image to the ` /tmp/images/ `
39
+ - Method 1: Via Redfish Upload:
40
+ https://github.com/openbmc/docs/blob/master/REDFISH-cheatsheet.md#firmware-update .
41
+ If using this method skip ahead to step 5!
42
+ - Method 2: Via scp: Copy the generated BMC image to the ` /tmp/images/ `
40
43
directory on the BMC.
41
- - Method 2 : Via REST Upload:
44
+ - Method 3 : Via REST Upload:
42
45
https://github.com/openbmc/docs/blob/master/rest-api.md#uploading-images
43
- - Method 3 : Via TFTP: Perform a POST request to call the ` DownloadViaTFTP `
46
+ - Method 4 : Via TFTP: Perform a POST request to call the ` DownloadViaTFTP `
44
47
method of ` /xyz/openbmc_project/software ` .
45
48
49
+ Methods 3 and 4 require additional options in bmcweb to be enabled.
50
+
46
51
3 . Note the version id generated for that image file. The version id is a hash
47
52
value of 8 hexadecimal numbers, generated by SHA-512 hashing the version
48
53
string contained in the image and taking the first 8 characters. Get the
@@ -104,15 +109,22 @@ MachineName=tiogapass
104
109
the activation progress and is not present once the activation is completed
105
110
via one of the following:
106
111
107
- - Method 1: From the BMC command line:
112
+ - Method 1: From Redfish: A task is returned from the Redfish upload. The task
113
+ can be used to monitor the progress.
114
+
115
+ ```
116
+ curl -k https://${bmc}/redfish/v1/TaskService/Tasks/0
117
+ ```
118
+
119
+ - Method 2: From the BMC command line:
108
120
109
121
```
110
122
busctl get-property xyz.openbmc_project.Software.BMC.Updater \
111
123
/xyz/openbmc_project/software/<id> \
112
124
xyz.openbmc_project.Software.ActivationProgress Progress
113
125
```
114
126
115
- - Method 2 : Using the REST API:
127
+ - Method 3 : Using the REST API:
116
128
117
129
```
118
130
curl -b cjar -k https://${bmc}/xyz/openbmc_project/software/<id>/attr/Progress
@@ -121,29 +133,41 @@ MachineName=tiogapass
121
133
6 . Check that the activation is complete by verifying the "Activation" property
122
134
is set to "Active" via one of the following methods:
123
135
124
- - Method 1: From the BMC command line:
136
+ - Method 1: From Redfish: Check the task returned from the Redfish upload.
137
+
138
+ ```
139
+ curl -k https://${bmc}/redfish/v1/TaskService/Tasks/0
140
+ ```
141
+
142
+ - Method 2: From the BMC command line:
125
143
126
144
```
127
145
busctl get-property xyz.openbmc_project.Software.BMC.Updater \
128
146
/xyz/openbmc_project/software/<id> \
129
147
xyz.openbmc_project.Software.Activation Activation
130
148
```
131
149
132
- - Method 2 : Using the REST API:
150
+ - Method 3 : Using the REST API:
133
151
134
152
```
135
153
curl -b cjar -k https://${bmc}/xyz/openbmc_project/software/<id>
136
154
```
137
155
138
156
7 . Reboot the BMC for the image to take effect.
139
157
140
- - Method 1: From the BMC command line:
158
+ - Method 1: From Redfish: If ApplyTime was set to "Immediate", the BMC will
159
+ automatically reboot:
160
+ https://github.com/openbmc/docs/blob/master/REDFISH-cheatsheet.md#firmware-applytime .
161
+ To reboot the BMC manually see:
162
+ https://github.com/openbmc/docs/blob/master/REDFISH-cheatsheet.md#bmc-reboot .
163
+
164
+ - Method 2: From the BMC command line:
141
165
142
166
```
143
167
reboot
144
168
```
145
169
146
- - Method 2 : Using the REST API:
170
+ - Method 3 : Using the REST API:
147
171
148
172
```
149
173
curl -c cjar -b cjar -k -H "Content-Type: application/json" -X PUT \
0 commit comments