Engineering Papers⌕ Search

DOE OSTI · 1104721

Intelligent Platform Management Interface (IPMI)

Abstract

Intelligent Platform Management Interface (IPMI) is a set of specifications that defines interfaces between components of the same system, most notably in servers; these interfaces provide information on the status of environmental variables such as voltage, temperature, and fan status. IPMI, which has grown significantly within the past five years, is generally used in computers to keep the system in check. However, the Controls Department at the SLAC National Accelerator Laboratory wants to find a way to implement IPMI in its standalone chassis. First, it is imperative to study how IPMI is used in a computer before actually going about designing a system that implements IPMI. Next, the proper parts of the system must be determined before research can be conducted on finding these parts. In addition to finding the right chips, figuring out the proper connections between these parts is just as important. While the system wasn’t constructed during the course of the project, the general process of designing the system from scratch is outlined.

Explore related subjects

Keep this discovery

Explore connections, maps & timelines

BibTeXRIS

Wung, Derek S.. 2009-08-14. Intelligent Platform Management Interface (IPMI). https://doi.org/10.2172/1104721

Cite the original work for its findings. Save a collection to share your selection of sources.

KEEP EXPLORING

Related reports

Uncertain quantum computing futures and potential energy and physical resource impacts at scale

Considerable attention has recently focused on the vast energy and water demands of supercomputing, namely large-scale data centers that underpin artificial intelligence (AI), one of the great disruptors of contemporary society. Looking ahead some years from now, quantum computing is poised to disrupt established computing paradigms once again. Scientists and engineers are now working intensely to bring this century-old dream of physicists to fruition. Yet, as quantum computers begin to be integrated with classical supercomputing architectures, the implications for energy and physical resource use also need to be understood, especially how they compare to today’s AI data centers. These impacts have not yet been quantified by the research community – a notable gap in the literature, even if commercial-scale deployment of Quantum-Accelerated Computing Infrastructure (QuACI) is not expected for a few more years. This study is the first to conduct such an assessment. Using publicly available information from academic sources and private industry, we characterize multiple configurations of superconducting qubit-based, fault-tolerant quantum computers (FTQC) that could plausibly be deployed at scale in the 2030s and into the 2040s. By parameterizing these FTQC systems at a process level, we conduct a prospective scenario analysis to quantify their energy and physical resource needs. While these estimates are uncertain, given the current state of quantum technologies and their unknown future trajectories, important insights can already be drawn. One key finding is that while the electricity needs for a fleet of FTQCs are within the bounds of previous modeling studies that have explored high electricity demand futures, the needs for certain physical resources, namely water and helium-3, could pose bottlenecks to QuACI scale-up.

Computing↗

EPICS for small-scale laboratories with Python soft IOCs

While the Experimental Physics and Industrial Control System (EPICS) is widely used at large laboratories for slow controls and instrumentation, the deployment of a full EPICS installation can be difficult, with a steep learning curve to new users. Taking advantage of the pythonSoftIOC module, we developed an EPICS slow controls implementation for Jefferson Lab's Hall B cryotarget written entirely in Python and based on software IOCs that communicate with instruments over Ethernet. Here, this system ran successfully, interfacing with Jefferson Lab's full EPICS network, and we offer it as an example of the capabilities of pythonSoftIOC to build lightweight, yet robust and flexible instrumentation platforms that would be easily adapted for use at a small-scale laboratory. University groups can use these examples to build complete slow controls systems, from device communication to data archiving and display, using open-source, mature EPICS tools and student-friendly Python as an alternative to expensive and proprietary systems such as LabVIEW.

Computing↗