summaryrefslogtreecommitdiffstats
path: root/console.md
blob: 2b83d8dc00a2aea66d44fe19ea33cc0ae4b3ba20 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
OpenBMC host console support
============================

This document describes how to connect to the host UART console from an OpenBMC
management system.

The console infrastructure allows multiple shared connections to a single host
UART. UART data from the host is output to all connections, and input from any
connection is sent to the host.

Remote console connections
--------------------------

To connect to an OpenBMC console session remotely, just ssh to your BMC on port
2200. Use the same login credentials you would for a normal ssh session:

    $ ssh -p 2200 [user]@[bmc-hostname]


Local console connections
-------------------------

If you're already logged into an OpenBMC machine, you can start a console
session directly, using:

    $ obmc-console-client

To exit from a console, type:

    return ~ .

Note that if you're on an ssh connection, you'll need to 'escape' the ~
character, by entering it twice.

Logging
-------

Console logs are kept in:

    /var/log/obmc-console.log

This log is limited in size, and will wrap after hitting that limit (currently
set at 16kB).
OpenPOWER on IntegriCloud