|
|
Post by josephreynolds1 on Jan 20, 2020 23:00:44 GMT
OpenBMC has a feature called serial-over-lan (SoL) which provides access to the host's UART serial console. (This provides the same function as IPMI SOL.)
The function is implemented as a SSH connection to port 2200, so network users connect via SSH to the BMC's port 2200, authenticate to the BMC, and then get access to the host's serial console. We may want for the BMC administrator to disable this access, and be able to re-enable it as needed for host debug scenarios. This request is to add a property for SOLSSH to the ManagerNetworkProtocol.
|
|
|
|
Post by josephreynolds1 on Apr 3, 2020 15:24:04 GMT
The OpenBMC project now has at least one implementation where the BMC provides SSH access to more than one console. For example, the BMC has access to two host consoles, and it provides access to console A via `ssh -p 2200 user@bmc` and access to console B via `ssh -p 2201 user@bmc`.
I am not sure how to model this situation in Redfish.
|
|
|
|
Post by jautor on Apr 5, 2020 0:06:01 GMT
What's the purpose of two consoles? Are they providing different functionality, or just two console instances? SSH implementations should support multiple sessions without having to specify multiple ports.
|
|
|
|
Post by radsquirrel on Apr 17, 2020 19:46:21 GMT
What's the purpose of two consoles? Are they providing different functionality, or just two console instances? The former - multiple consoles are useful on devices like this:
It is 4 "systems" all managed by a single BMC. Each system console can be accessed on a different ssh port.
IBM also has system designs with multiple consoles that provide different functions.
I hope this helps!
-brad
|
|
