Martin Pool's blog

snippet

kate dumpfru% make dumpfru&&sudo ./dumpfru
gcc -o dumpfru -Wall -g dumpfru.c -lezbmc  -lm
FRU 0000/0000
     8  1  1  9  d 1c  0  0
        FRU common header checksum OK :-)
chassis info at offset 72
    20  1  4 17 cb  0  0  0  |  0  0  0  0  0  0  0  0
    cc 53 47 33 33 33 32 30  | 36 31 31  0  0 c1  0  0
    32 bytes of chassis data
chassis info length 32
chassis type 0x17
chassis part number: ""
chassis serial number: "SG33320611"
board info at offset 104
128 bytes of board info:
    80  1  f  0  0  0  0 ca  | 68 70  0  0  0  0  0  0
     0  0 e0 77 6f 72 6b 73  | 74 61 74 69 6f 6e 20 7a
    78 36 30 30 30 20 73 79  | 73 74 65 6d 20 62 6f 61
    72 64  0 d0 34 30 43 54  | 4c 56 4e 30 33 54  0  0
     0  0  0  0 cb 41 37 32  | 33 31 2d 36 36 35 31 30
    41 11 c8 64  8 44  0  0  |  0  0  0 c4 34 33 32 31
    c2 44  0 10  1 17  0  0  |  0  0  0  0  0  0  0  0
     0  0  0  0 c1  0  0  0  | 23  1 10  0 c2 68 70 e0
board manf: "hp"
board product: "workstation zx6000 system board"
board serial number: "40CTLVN03T"
board part nr: "A7231-66510"
board FRU file ID: 6bit: 1@,9

CMPI - WBEM Common Management Provider Interface

CMPI is a C programming interface for writing "provider modules" that plug in to a WBEM management server. It's kind of analogous to the Apache module interface in scope and content. You might use this to write a provider module that can issue management information about SMART disk drives. The module can do either a polled mode, reporting on the drives in response to a request, or interrupt mode, where it generates an "indication" message when something happens.

This interface is meant to be standardized across all providers and managers allowing for them to evolve separately.

WBEM is technically pretty good but the documentation can be hard to get a grip on. DMTF's determined efforts to make sure it remains obscure (e.g. requiring registration to read documentation) are not helping. I think I should add more links here.

SBLIM - Standards Based Linux Instrumentation for Manageability

SBLM pronounced "sublime" and is an acronym for Standards Based Linux Instrumentation for Manageability. The goal of this project is to provide a complete Open Source implementation of the CIM Schema for Linux Systems. SBLIM is a project maintained by the IBM Linux Technology Center and is licensed under the CPL.

Why is it needed?

Today, looking at GNU/Linux systems (and others) reveals a rather fragmented and incoherent picture regarding Systems Management and Manageability. There are basically two reasons:

  1. Proprietary format and locations: Information about system resources are spread all over the place and have their unique format. This includes files in the /etc directory tree, entries the /proc filesystem and so forth.
  2. Lack of common concepts: It is virtually impossible for a Systems Management application to manage system resources without knowing implementation details. Example needed? How about configuring a device in need of special run-time options.

This needs less enterprise-speek if it's going to be adopted, but I think the core idea may be good.

Archives 2008: Apr Feb 2007: Jul May Feb Jan 2006: Dec Nov Oct Sep Aug Jul Jun Jan 2005: Sep Aug Jul Jun May Apr Mar Feb Jan 2004: Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan 2003: Dec Nov Oct Sep Aug Jul Jun May