Skip to content

Commit fadee85

Browse files
authored
Update 4_openbmc_communicate.md
1 parent e8b08de commit fadee85

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

content/learning-paths/servers-and-cloud-computing/openbmc-rdv3/4_openbmc_communicate.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,8 @@ layout: learningpathall
88

99
## Access the Host Console via OpenBMC SOL
1010

11-
The OpenBMC platform provides `Serial over LAN` (SOL), allowing you to access the host console (RD-V3 FVP) remotely through the BMCwithout needing a physical serial cable.
12-
In this module, you’ll use `socat` to create a virtual UART bridge, verify port mappings, and access the host console via the BMC Web UI.
11+
The OpenBMC platform provides `Serial over LAN` (SOL), allowing you to access the host console (RD-V3 FVP) remotely through the BMC, without needing a physical serial cable.
12+
In this section, you will use `socat` to create a virtual UART bridge, verify port mappings, and access the host console via the BMC Web UI.
1313

1414
### Step 1: Connect the BMC and Host Consoles
1515

@@ -19,13 +19,13 @@ Run the following command on your development Linux machine (where the simulatio
1919
socat -x tcp:localhost:5005 tcp:localhost:5067
2020
```
2121

22-
This command connects the host-side UART port (5005) to the BMC-side port (5067), allowing bidirectional serial communication.
22+
This command connects the host-side UART port (5005) to the BMC-side port (5067), allowing bi-directional serial communication.
2323

2424
{{% notice Note %}}
2525
If you see a Connection refused error, check the FVP logs to verify the port numbers:
26-
* In fvp_boot.log, look for a line like:
26+
* In `fvp_boot.log`, look for a line like:
2727
terminal_ns_uart0: Listening for serial connection on port 5005
28-
* In obmc_boot.log, confirm the corresponding line:
28+
* In `obmc_boot.log`, confirm the corresponding line:
2929
terminal_3: Listening for serial connection on port 5067
3030
{{% /notice %}}
3131

@@ -56,15 +56,15 @@ This updates the BMC’s internal host state, allowing UEFI to begin execution.
5656
{{% notice Note %}}
5757
As a reminder, the first character of the password is the number ***0***, not a capital ***O***.
5858
{{% /notice %}}
59-
After login, you'll see the Web UI dashboard:
59+
After login, you should see the Web UI dashboard:
6060

6161
- From the Overview page, click the `SOL Console` button.
6262
![img4 alt-text#center](openbmc_webui_overview.jpg "WebUI Overview")
6363

6464
- The SOL terminal in the Web UI will display the host console output (UEFI shell or Linux login). You can type commands directly as if you were connected over a physical serial line.
6565
![img5 alt-text#center](openbmc_webui_sol.jpg "WebUI SOL")
6666

67-
Once connected to the SOL terminal, you can monitor the UEFI boot sequence, interact with the host shell, and run diagnostic or recovery workflowsjust as if you were connected to a physical serial port.
67+
Once connected to the SOL terminal, you can monitor the UEFI boot sequence, interact with the host shell, and run diagnostic or recovery workflows, just as if you were connected to a physical serial port.
6868

6969
This confirms that OpenBMC is fully managing host power and console access in your simulated environment.
7070

0 commit comments

Comments
 (0)