Skip to content

Commit a90c579

Browse files
authored
Merge pull request #60654 from dfitzmau/OCPBUGS-8745
OCPBUGS#8745: Removed part of the Dell iDRAC note
2 parents 6f18cf1 + 436eefb commit a90c579

File tree

1 file changed

+13
-12
lines changed

1 file changed

+13
-12
lines changed

modules/ipi-install-bmc-addressing-for-dell-idrac.adoc

Lines changed: 13 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,11 @@ See the following sections for additional details.
4646

4747
For Redfish virtual media on Dell servers, use `idrac-virtualmedia://` in the `address` setting. Using `redfish-virtualmedia://` will not work.
4848

49+
[NOTE]
50+
====
51+
Use `idrac-virtualmedia://` as the protocol for Redfish virtual media. Using `redfish-virtualmedia://` will not work on Dell hardware, because the `idrac-virtualmedia://` protocol corresponds to the `idrac` hardware type and the Redfish protocol in Ironic. Dell's `idrac-virtualmedia://` protocol uses the Redfish standard with Dell's OEM extensions. Ironic also supports the `idrac` type with the WSMAN protocol. Therefore, you must specify `idrac-virtualmedia://` to avoid unexpected behavior when electing to use Redfish with virtual media on Dell hardware.
52+
====
53+
4954
The following example demonstrates using iDRAC virtual media within the `install-config.yaml` file.
5055

5156
[source,yaml]
@@ -61,7 +66,14 @@ platform:
6166
password: <password>
6267
----
6368

64-
While it is recommended to have a certificate of authority for the out-of-band management addresses, you must include `disableCertificateVerification: True` in the `bmc` configuration if using self-signed certificates. The following example demonstrates a Redfish configuration using the `disableCertificateVerification: True` configuration parameter within the `install-config.yaml` file.
69+
While it is recommended to have a certificate of authority for the out-of-band management addresses, you must include `disableCertificateVerification: True` in the `bmc` configuration if using self-signed certificates.
70+
71+
[NOTE]
72+
====
73+
Ensure the {product-title} cluster nodes have *AutoAttach* enabled through the iDRAC console. The menu path is: *Configuration* -> *Virtual Media* -> *Attach Mode* -> *AutoAttach*.
74+
====
75+
76+
The following example demonstrates a Redfish configuration using the `disableCertificateVerification: True` configuration parameter within the `install-config.yaml` file.
6577

6678
[source,yaml]
6779
----
@@ -77,17 +89,6 @@ platform:
7789
disableCertificateVerification: True
7890
----
7991

80-
81-
[NOTE]
82-
====
83-
There is a known issue on Dell iDRAC 9 with firmware version `04.40.00.00` or later for installer-provisioned installations on bare metal deployments. The Virtual Console plugin defaults to eHTML5, an enhanced version of HTML5, which causes problems with the *InsertVirtualMedia* workflow. Set the plugin to use HTML5 to avoid this issue. The menu path is *Configuration* -> *Virtual console* -> *Plug-in Type* -> *HTML5* .
84-
85-
Ensure the {product-title} cluster nodes have *AutoAttach* enabled through the iDRAC console. The menu path is: *Configuration* -> *Virtual Media* -> *Attach Mode* -> *AutoAttach* .
86-
87-
Use `idrac-virtualmedia://` as the protocol for Redfish virtual media. Using `redfish-virtualmedia://` will not work on Dell hardware, because the `idrac-virtualmedia://` protocol corresponds to the `idrac` hardware type and the Redfish protocol in Ironic. Dell's `idrac-virtualmedia://` protocol uses the Redfish standard with Dell's OEM extensions. Ironic also supports the `idrac` type with the WSMAN protocol. Therefore, you must specify `idrac-virtualmedia://` to avoid unexpected behavior when electing to use Redfish with virtual media on Dell hardware.
88-
====
89-
90-
9192
[discrete]
9293
== Redfish network boot for iDRAC
9394

0 commit comments

Comments
 (0)