Skip to content

Commit 3880a51

Browse files
committed
Update Blog “automate-boot-from-san-target-configurations-using-redfish”
1 parent d62b2a6 commit 3880a51

File tree

1 file changed

+3
-11
lines changed

1 file changed

+3
-11
lines changed

content/blog/automate-boot-from-san-target-configurations-using-redfish.md

Lines changed: 3 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -61,8 +61,6 @@ ilorest commit
6161
ilorest reboot
6262
```
6363

64-
65-
6664
**Note**:
6765

6866
After restarting the server, remember to logout/login again to the server using ilorest tool to retrieve the updated settings from the server directly, rather than the cache. You can also update the ilorest cache contents with the following command
@@ -166,18 +164,12 @@ The above values can help you ascertain that you have the right card, and its de
166164

167165
Before you can change the boot from SAN configurations on an FC card, you will have to set `RedfishConfiguration` key to "Enabled" for the specific adapter, if not already done.
168166

169-
The current value of this variable can be viewed by querying the adapter.
167+
The current value of this key can be viewed by querying the adapter.
170168

171169
```markdown
172170
ilorest rawget /redfish/v1/Chassis/1/NetworkAdapters/DE083000
173171
```
174172

175-
Towards the end of the generated output from the above command, please check for an entry.
176-
177-
```markdown
178-
"RedfishConfiguration": "Enabled"
179-
```
180-
181173
If the value is not set, please perform the following:
182174

183175
1. Create a file named enable-redfish.txt with the following contents
@@ -313,12 +305,12 @@ To modify the value of this property,
313305
```markdown
314306
ilorest rawpost <file path>\flushtonvm.txt
315307
```
316-
4. Reboot the server
308+
4. Restart the server
317309

318310
```markdown
319311
ilorest reboot
320312
```
321-
5. Once the server has reset, you can view the boot order to verify that the new entry for the SAN boot target has been created.
313+
5. Once the server has restarted, you can view the boot order to verify that the new entry for the SAN boot target has been created.
322314

323315
```markdown
324316
ilorest bootorder

0 commit comments

Comments
 (0)