docs/designs/multihost-ipmi-design.md

1 # Multi-host IPMI design
12 The current version of OpenBMC does not support multi-host implementation in
13 IPMI commands handling. We have a multi-host system and proposing the design to
14 support multi-host.
27 IPMI and IPMB System architecture:
30  +------------------------------------+
32  | +-----------+       +------------+ |      +--------+
34  | |           |       |            |-|------| Host-1 |
36  | |           |       |            | |      +--------+
39  | |           | D-Bus |            | |      +--------+
40  | | ipmid     |-------| ipmbbridged| | IPMB2|        |
41  | |           |       |            |-|------| Host-2 |
43  | |           |       |            | |      +--------+
46  | |           |       |            | |      +--------+
48  | |           |       |            |-|------| Host-N |
50  | +-----------+       +------------+ |      +--------+
51  +------------------------------------+
56 requests are routed from ipmid or any service by D-Bus interface and The
61 The current version of OpenBMC does not support multi-host implementation in
62 IPMI commands handling. We have a multi-host system and proposing the design to
63 support multi-host.
68 ipmbbridged and ipmid. To address out-of-band IPMI command from the network,the
79 will send '"devIndex": 0' as optional parameter(options) in D-Bus interface to
91     "slave-path": "/dev/ipmb-1",
92     "bmc-addr": 32,
93     "remote-addr": 64,
98     "slave-path": "/dev/ipmb-2",
99     "bmc-addr": 32,
100     "remote-addr": 64,
105     "slave-path": "/dev/ipmb-3",
106     "bmc-addr": 32,
107     "remote-addr": 64,
112     "slave-path": "/dev/ipmb-4",
113     "bmc-addr": 32,
114     "remote-addr": 64,
139 multiple approaches to handle multi-host.Some of the approaches are listed down
142 1. Virtual Ethernet interfaces - One virtual interface per host.
143 2. Different port numbers - Can have different port numbers for each host.
144 3. VLAN Ids- VLAN IDs can be used to support multi host. The netipmid shall have
149 {"Host":1, "Interface-1":"eth0", "Interface-2":"eth1", "Interface-3":"veth4",
150 "Interface-4":"veth5" }, {"Host":2, "Interface-1":"eth2", "Interface-2":"eth3",
151 "Interface-3":"veth1", "Interface-4":"veth2" },
156 +--------------------------------------------+
158 | +--------+       +-----------+   +------+  |      +--------+
159 | |        | D-Bus |           |   |      |  |      |        |
160 | |        |-------| netipmid1 |---|veth1 |---------| Host-1 |
162 | |        |       +-----------+   +------+  |      +--------+
164 | |        |       +-----------+   +------+  |      +--------+
165 | | ipmid  | D-Bus |           |   |      |  |      |        |
166 | |        |-------| netipmid2 |---|veth2 |---------| Host-2 |
168 | |        |       +-----------+   +------+  |      +--------+
170 | |        |       +-----------+   +------+  |      +--------+
171 | |        | D-Bus |           |   |      |  |      |        |
172 | |        |-------| netipmidN |---|vethN |---------| Host-N |
174 | +--------+       +-----------+   +------+  |      +--------+
175 +--------------------------------------------+
184 ## Approach1:ipmbbridged to send host-id in the payload
192 This is a multi service appoach,one instance of ipmid service shall be spawned