Mount an OS Image Through the BMC HTML5 or Java Console
Archived OEM guide to mounting installation media through HTML5 or Java BMC console redirection. Eleven English instructional localizations cover twelve image references; two Oracle official English Java figures cover three references, with differences captioned. Seven original English figures are retained. The source mixes hosts and UI states; it is not proof of a single completed OS installation. No BMC login, media mount, security exception or host operation was performed while preparing this article.
Method for Mounting System Image via IPMI
I. HTML5 console: log in to the intended BMC with an authorized account, then open its console. The dashboard is an archived example with BMC 4.2.0 and BIOS 4.0.4; its online-user IP is a client address, not necessarily the BMC address. The duplicated dashboard starts each alternative workflow.
2. Open Remote Control → Console Redirection (KVM) and choose Launch KVM HTML5 Viewer where the actual firmware supports it. The red rectangle identifies the HTML5 control, not the Java alternative.
3. In the HTML5 viewer, use Browse File in the CD Image area. The first source example shows 0 KB and Start Media, with no selected image yet. A running KVM console is separate from an attached virtual disc.
4. Select the intended verified bootable image. The archived file-picker example highlights CentOS-7-x86_64-DVD-2003; its Chinese personal folder names are translated as English instructional names. They are not changes made to an actual workstation filesystem.
5. After selecting the correct image, choose Start Media and inspect the resulting connection status. The displayed Start Media figure itself still shows 0 KB and comes from a different BMC address, 10.125.236.34; its iCloud Sphere console warnings do not prove media connected or an OS installed successfully. Do not treat the separate source screenshots as one verified uninterrupted session.
6. Use the actual firmware boot-menu key and select the intended virtual CD/DVD entry. The source prose uses F11 and its menu highlights the virtual CDROM; another USB and several network-boot entries are different devices. A boot-device menu alone does not demonstrate a completed installation.
7. Keep the media session available while the actual operation requires it, then choose Stop Media when it is safe to detach. The source screenshot still shows the boot menu and a selected CentOS image with an adjacent 118 KB counter; it does not show installation completion and the counter is not evidence that the whole ISO is only 118 KB. Stop KVM and Stop Media are different controls.
II. Method for Mounting Image via Java
The archived source names jre-8u71-windows-x64.zip as its Java 8u71 Windows x64 example. This is an old package reference, not a current runtime recommendation. Check the server vendor’s supported console/client combination; use its supported HTML5 path when appropriate instead of installing an old Java release solely to match this screenshot.
1. Log in to the intended BMC. This Java workflow is an alternative to the preceding HTML5 workflow, not an additional mandatory stage.
2. Open Remote Control → Console Redirection (KVM) and choose Launch KVM Java Viewer. Here the red rectangle identifies the second, Java button.
3. Download jviewer.jnlp from the intended trusted BMC and use the supported Java Web Start environment. The next source image shows an invalid-certificate warning for https://10.125.236.34:443 with Continue highlighted. That highlight is historical instruction, not certificate validation: confirm the intended host and resolve the trust issue before proceeding; cancel if identity cannot be established.
4. In JViewer, open Media → Virtual Media Wizard, then the CD/DVD image controls and Browse. Select the intended ISO. Some source windows retain an insufficient device-redirection permission message; an open file picker does not mean that message was resolved. Follow the actual vendor/client permission requirements for the required redirection mode.
5. Review the selected image and choose Connect. The source Connect figure still shows a not-connected state; choosing the control and observing a connected state are separate steps.
The next source dialog says the device is redirected in Read Only mode. Review and acknowledge that information as appropriate; it is not an installer-success message.
The following source figure shows Disconnect and a Virtual CD/DVD connection entry. Check the actual console’s connection state and image identity; the pictured physical-device permission footer is still present, so this is not evidence that every redirection mode works.
6. At the appropriate boot prompt, use the actual boot-menu key and choose the virtual CD/DVD entry. The source uses F11 in its instructions. Keep the required media available until the actual operation is finished and detach according to the console workflow. No final installed OS is demonstrated in this article.
III. Common Issues
1. If JViewer cannot launch, inspect the detailed error and the actual client/runtime, application origin and certificate/signature state. The generic Unable to launch the application dialog shown here identifies https://192.168.20.180:443, a different source example. That message alone does not establish that the exception list is the cause or that adding an exception will fix it.
For a vendor-supported, trusted legacy application where a site exception is actually appropriate, find Security → Edit Site List in Java Control Panel. The official English panel below has High selected and an empty list; it does not reproduce the OEM’s pre-existing HTTP entries.
Oracle official English Java 8u20+ Security tab: High is selected and the exception list is empty. The OEM screenshot instead shows three existing HTTP addresses; those addresses are not copied. This figure identifies the controls and does not certify a BMC connection.
Choose Add and enter the exact verified BMC/application origin, represented here as https://<BMC_ADDRESS> . Include the actual port if it is not the default and review the scope before saving. Oracle’s official demonstration figure uses an example HTTP URL; it is not the BMC address to copy. A site exception allows otherwise blocked applications to run and does not repair a certificate or prove the endpoint is trustworthy.
Oracle official English Exception Site List example with Add highlighted and http://www.example.com as a demonstration URL. The OEM screenshot instead enters https://192.168.1.13. Use only the actual verified BMC origin, not the demonstration address; Oracle recommends HTTPS.
If the reviewed configuration is saved, reopen the actual JNLP and confirm the result. The reused official panel below intentionally has no saved BMC entry; the OEM’s final screenshot instead shows https://192.168.1.13. None of these figures proves that Java settings were changed or the application launched while preparing this translation.
The same official English Security-tab figure is reused to identify the final OK control. Its list is empty, unlike the OEM screenshot containing https://192.168.1.13. It is not evidence that an exception was saved, that a certificate is valid or that JViewer successfully launched.
English sources and scope
The OEM QA’s English link leads to the vendor home page; no corresponding English article or complete same-firmware image set was verified. Oracle’s English Java controls are directly relevant to the Java 8 troubleshooting step; their example URLs and empty exception-list state are explicitly distinguished from the OEM screenshots. The other translated figures are instructional illustrations rather than official English console captures.