http://en.wikipedia.org/wiki/Desktop_Management_Interface

Desktop Management Interface

From Wikipedia, the free encyclopedia
 
 
Not to be confused with SMBIOS.

The Desktop Management Interface (DMI) generates a standard framework for managing and tracking components in a desktop, notebook or server computer, by abstracting these components from the software that manages them. The development of DMI marked the first move by the Distributed Management Task Force (DMTF) into desktop-management standards.[1] Before the introduction of DMI, no standardized source of information could provide details about components in a personal computer.

Due to the rapid development of DMTF technologies, such as Common Information Model (CIM), the DMTF defined an "End of Life" process for DMI, which ended on March 31, 2005.

From 1999, Microsoft required OEMs and BIOS vendors to support the DMI interface/data-set in order to have Microsoft certification.[citation needed]

DMI and SMBIOS[edit]

DMI exposes system data (including the System Management BIOS (SMBIOS) data) to management software, but the two specifications function independently.

DMI is commonly confused with SMBIOS, which was actually called DMIBIOS in its first revisions.

Optional additional services: MIF data and MIF routines[edit]

When software queries a memory-resident agent that resides in the background, it responds by sending data in MIFs (Management Information Format) or activating MIF routines. Static data in a MIF would contain items such as model ID, serial number, memory- and port-addresses. A MIF routine could read memory and report its contents.

DMI and SNMP[edit]

DMI can co-exist with SNMP and other management protocols. For example, when an SNMP query arrives, DMI can fill out the SNMP MIB with data from its MIF. A single workstation or server can serve as a proxy agent that would contain the SNMP module and service an entire LAN segment of DMI-capable machines.

See also[edit]

http://en.wikipedia.org/wiki/SMBIOS

System Management BIOS

From Wikipedia, the free encyclopedia
  (Redirected from SMBIOS)
 
Not to be confused with DMI.

In computing, the System Management BIOS (SMBIOS) specification defines data structures (and access methods) that can be used to read information stored in the BIOS of a computer. Circa 1999, it became part of the domain of the Distributed Management Task Force (DMTF). Before this integration, SMBIOS functionality had the name DMIBIOS, since it interacted with Desktop Management Interface(DMI). At approximately the same time Microsoft started to require that OEMs and BIOS vendors support the interface/data-set in order to have Microsoft certification.

The DMTF released the current version of the specification, version 2.8.0, on April 3, 2013.

Structure types[edit]

As of version 2.7.1, the SMBIOS specification defines these structure types:

Type Description
0 BIOS Information
1 System Information
2 Baseboard (or Module) Information
3 System Enclosure or Chassis
4 Processor Information
5 Memory Controller Information (Obsolete)
6 Memory Module Information (Obsolete)
7 Cache Information
8 Port Connector Information
9 System Slots
10 On Board Devices Information
11 OEM Strings
12 System Configuration Options
13 BIOS Language Information
14 Group Associations
15 System Event Log
16 Physical Memory Array
17 Memory Device
18 32-Bit Memory Error Information
19 Memory Array Mapped Address
20 Memory Device Mapped Address
21 Built-in Pointing Device
22 Portable Battery
23 System Reset
24 Hardware Security
25 System Power Controls
26 Voltage Probe
27 Cooling Device
28 Temperature Probe
29 Electrical Current Probe
30 Out-of-Band Remote Access
31 Boot Integrity Services (BIS) Entry Point
32 System Boot Information
33 64-Bit Memory Error Information
34 Management Device
35 Management Device Component
36 Management Device Threshold Data
37 Memory Channel
38 IPMI Device Information
39 System Power Supply
40 Additional Information
41 Onboard Devices Extended Information
42 Management Controller Host Interface
126 Inactive
127 End-of-Table
128–255 Available for system- and OEM- specific information

Accessing SMBIOS data[edit]

From Linux[edit]

The Linux kernel contains an SMBIOS decoder, allowing systems administrators to inspect system hardware configuration and enable or disable certain workarounds for problems with specific systems, based on the provided SMBIOS information.

The userspace command-line utility dmidecode(8) can be used to inspect this data. Information provided by this utility typically includes system manufacturer, model name, serial number, BIOS version and asset tag, as well as a lot of other details of varying level of interest and reliability — depending on the system manufacturer. The information often includes usage status for the CPU sockets, expansion slots (including AGP, PCI and ISA) and memory module slots, and the list of I/O ports (including serial, parallel and USB).[1][2]

From Windows[edit]

WMI is the preferred mechanism for accessing SMBIOS information from Windows.[3]

On Windows systems that support it (XP and later), some SMBIOS information can be viewed with either the WMIC utility with 'BIOS'/'MEMORYCHIP'/'BASEBOARD' and similar parameters, or by looking in the Windows Registry under HKLM\HARDWARE\DESCRIPTION\System

Raw SMBIOS data can be retrieved using various utilities, such as "smbiosw"[4] and "SMBIOS Peek".[5]

From UEFI[edit]

In UEFI, the "SmbiosView" shell application can be used to view the SMBIOS data.

See also[edit]

Desktop Management Interface & System Management BIOS的更多相关文章

  1. Operating system management of address-translation-related data structures and hardware lookasides

    An approach is provided in a hypervised computer system where a page table request is at an operatin ...

  2. Flexible implementation of a system management mode (SMM) in a processor

    A system management mode (SMM) of operating a processor includes only a basic set of hardwired hooks ...

  3. IPMI (Intelligent Platform Management Interface)

    4.3. ipmitool - utility for controlling IPMI-enabled devices 4.3.1. ipmitool 4.3.1.1. ubuntu 确定硬件是否支 ...

  4. C# 学习笔记(三)----- 设备监视 ( System.Management )

    实例:串口监视 using System; using System.Collections.Generic; using System.Linq; using System.Text; using ...

  5. HP管理工具System Management Homepage安装配置

    如果用HP的启动光盘进行系统安装时,HP SMH 及相关组件会自动安装完成,但如果是用操作系统光盘进行系统安装,则HP SMH相关组件需要手动进行安装及相关设置!HP SMH由三部分组成:HP Sys ...

  6. 快速找出System.Management.Automation.dll,c#调用powershell

    public static void InvokeSystemPS(string cmd) { List<string> ps = new List<string>(); ps ...

  7. FAQ – Automatic Undo Management (AUM) / System Managed Undo (SMU) (Doc ID 461480.1)

    FAQ – Automatic Undo Management (AUM) / System Managed Undo (SMU) (Doc ID 461480.1) APPLIES TO: Orac ...

  8. Can't access RabbitMQ web management interface after fresh install

    http://stackoverflow.com/questions/22850546/cant-access-rabbitmq-web-management-interface-after-fres ...

  9. Cisco IOS basic system management command reference

    absolute : to specify an absolute time for a time-range (in time-range configuration mode) no absolu ...

随机推荐

  1. cookie小结(转)

    原文地址:http://www.cnblogs.com/xianyulaodi/p/6476991.html#_label0 作者:咸鱼老弟   阅读目录 什么是cookie       官方定义:N ...

  2. android 之 ListView相关

    ListView是一种列表视图,其将ListAdapter所提供的各个控件显示在一个垂直且可滚动的列表中.需要注意的为创建适配器并将其设置给ListView. 1.ArrayAdapter Array ...

  3. 自己项目使用了ARC,项目中使用第三方库继续引用ARC

    Objective-C引入ARC(Automatic Reference Counting)后,我们经常会面对这样一种困境:自己的项目使用了ARC,却发现要使用的第三方类库是non-ARC的:又或者自 ...

  4. 使用pipework将Docker容器桥接到本地网络环境中

    在使用Docker的过程中,有时候我们会有将Docker容器配置到和主机同一网段的需求.要实现这个需求,我们只要将Docker容器和主机的网卡桥接起来,再给Docker容器配上IP就可以了.pipew ...

  5. Sequence Models

    Sequence Models This is the fifth and final course of the deep learning specialization at Coursera w ...

  6. 【转】OPC远程访问相关配置信息

    原文:http://blog.gkong.com/kking_25653.ashx 对于远程访问OPC服务器,需要在客户和服务器计算机上都进行DCOM设置,本文提供一些具体配置方法.(by Kevin ...

  7. spring中quartz的使用。【转http://www.cnblogs.com/kay/archive/2007/11/02/947372.html】

    注:从spring3到spring4改变 org.springframework.scheduling.quartz.CronTriggerBean org.springframework.sched ...

  8. KVM 网络虚拟化基础

    网络虚拟化是虚拟化技术中最复杂的部分,学习难度最大. 但因为网络是虚拟化中非常重要的资源,所以再硬的骨头也必须要把它啃下来. 为了让大家对虚拟化网络的复杂程度有一个直观的认识,请看下图 这是 Open ...

  9. 关于内存 转载自http://blog.csdn.net/xluren/article/details/8150723

    首先感谢下原作者,写的真的非常明白,非常详细 1.预备知识—程序的内存分配 一个由C/C++编译的程序占用的内存分为以下几个部分 1.栈区(stack)— 由编译器自动分配释放 ,存放函数的参数值,局 ...

  10. ci框架——修改分页的显示样式

    修改ci框架分页的显示样式 用过ci框架的都知道,ci框架自带的分页样式是1,2下一页,在最开始刷新页面现实的时候如果页面不够多的话,那么首页和末页是不显的,这是ci框架的一个缺点, 这个时候需要我们 ...