You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/learning-paths/servers-and-cloud-computing/openbmc-rdv3/4_openbmc_communicate.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,8 +8,8 @@ layout: learningpathall
8
8
9
9
## Access the Host Console via OpenBMC SOL
10
10
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 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.
13
13
14
14
### Step 1: Connect the BMC and Host Consoles
15
15
@@ -19,13 +19,13 @@ Run the following command on your development Linux machine (where the simulatio
19
19
socat -x tcp:localhost:5005 tcp:localhost:5067
20
20
```
21
21
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.
23
23
24
24
{{% notice Note %}}
25
25
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:
27
27
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:
29
29
terminal_3: Listening for serial connection on port 5067
30
30
{{% /notice %}}
31
31
@@ -56,15 +56,15 @@ This updates the BMC’s internal host state, allowing UEFI to begin execution.
56
56
{{% notice Note %}}
57
57
As a reminder, the first character of the password is the number ***0***, not a capital ***O***.
58
58
{{% /notice %}}
59
-
After login, you'll see the Web UI dashboard:
59
+
After login, you should see the Web UI dashboard:
60
60
61
61
- From the Overview page, click the `SOL Console` button.
- 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.
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.
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.
68
68
69
69
This confirms that OpenBMC is fully managing host power and console access in your simulated environment.
0 commit comments