HP Systems Insight Manager 7.1 Database Tables

DescriptionData TypeColumn Name
Possible States enumerates the string outputs of the
Sensor (For example, a switch sensor can output the
NVARCHAR(512)PossibleStates
states On or Off. Another implementation of the
Switch can output the states Open and Close.
Another example is a NumericSensor supporting
thresholds. This Sensor can report the states like
Normal, Upper Fatal, Lower non-critical and so on.
A Numeric Sensor that does not publish readings
and threshold but stores this data internally can still
report its states.)
The current air temperature at the exhaust of the
power supply in degrees Celsius
INTCurrentReading
The current air temperature at the intake of the power
supply in degrees Celsius
INTdc_OtherCurrentReading
Code for the units used by the readings (pull from
CIM_NumericSensor)
INTBaseUnit
Type of sensor: ValueMap { "0", "1", "2", "3", "4",
"5", "6", "7", "8", "9", "10", "11", "12" }, Values
SMALLINTSensorType
{ "Unknown", "Other", "Temperature", "Voltage",
"Current", "Tachometer", "Counter", "Switch",
"Lock", "Humidity", "Smoke Detection", "Presence",
"Air Flow" }
CIM_SoftwareElement table
DescriptionData TypeColumn Name
LUID uniquely defining this table rowBIGINTSoftwareElement_LUID
Node partly identifies CIM_SoftwareElementBIGINTNodeID
Snapshot partly identifies CIM_SoftwareElementBIGINTSnapshotID
SoftwareElementID partly identifies
CIM_SoftwareElement (This is an identifier for
NVARCHAR(256)SoftwareElementID
theSoftware Element and is designed to be used in
conjunction with other keys to create a unique
representation of the element.)
SoftwareElementState partly identifies
CIM_SoftwareElement (The SoftwareElementState is
SMALLINTSoftwareElementState
defined in this model to identify various states of a
SoftwareElement life cycle. A SoftwareElement in the
deployable state describes the details necessary to
successfully distribute it and the details (checks and
actions) required to move it to the installable state
(for example, the next state). A SoftwareElement in
the installable state describes the details necessary
to successfully install it and the details (checks and
actions) required to create an element in the
executable state (for example, the next state). A
SoftwareElement in the executable state describes
the details necessary to successfully start it and the
details (checks and actions) required to move it to
the running state for example, the next state). A
SoftwareElement in the running state describes the
details necessary to manage the started element.
CIM_SoftwareElement.SoftwareElementState
enumeration 0 = Deployable, 1 = Installable, 2 =
Executable, 3 = Running)
42 HP SIM database tables