RunBMC – BMC interface specification for OCP Baseboard Management Controllers (BMC) perform a range of functions on servers; like checking temperature ranges; voltage; current; power management; and other kinds of health checks. Admins typically monitor these statistics through IPMI; issuing commands through a network topology that’s separate and insulated from the communication between the server’s CPU; firmware; and operating system. There’s a proliferation of hardware devices and SKUs in contemporary data centers; all with different BMCs. Last summer’s controversies over potential hardware vulnerabilities built into server networks have people paying close attention to the BMC subsystem. Having a standardized BMC interface will enable companies to “lock down” their BMC subsystem. Having a design that’s more stable; that rolls at a slower cadence than compute platforms; lets you harden your BMC. It’s really difficult in that environment to control everything and guard against vulnerabilities like man in the middle attacks. By focusing security efforts on a single BMC card; system designers can standardize their own software management stack. The RunBMC specification daughter board card design for use with Open Compute Project motherboards. This specification defines the interface between the Baseboard Management Controller (BMC) subsystem and OCP hardware platforms; such as network or compute motherboards. The daughter board interfaces with hardware platforms through a 260 pin SODIMM DDR4 connector; which is intended for mounting into a mating SODIMM DDR4 socket. The specification defines the IO which should cover the majority of platform BMC requirements.