Aliases – HP Insight Control Software for Linux User Manual
Page 65
The following attributes are recognized in specific formats only.
FORMATS
TYPE
NAME
TAB, text
String
CircuitName
All but XML
String
DeviceName
TAB, text
String
DeviceSubType
TAB, text
Unsigned
enclEndU
TAB, text
Unsigned
EndU
TAB, text
Unsigned
ipmBreakerCapacity
TAB, text
Unsigned
ipmDeratedBreakerCapacity
TAB, text
Unsigned
ipmLineVoltage
TAB, text
String
IPMPoweredBy
TAB, text
String
ipmPowerIdentifier
TAB, text
Unsigned
ipmPowerLimit
TAB, text
Unsigned
ipmPowerOutputs
TAB, text
String
ipmSide
TAB, text
String
managedByDevice
Note that the value of "ipmSide" for a circuit is limited to "A" for primary power or "B" for backup power,
usually used for racks that have redundant power. A circuit with no side specified defaults to "A".
Lines beginning with a # sign are treated as comments. The convention for setting any attribute is
attribute:value.
DatacentreID:Lab5
Objects appear in a hierachy, with the container first, and the members below it indented. Everything related
to a device appears on a single line of the text file separated by commas.
RowNumber:1
RackName:southamerica, PositionRow:8, rackHeight:48
DeviceName:peru, StartU:5, HeightU:2
Circuits don't have such a clear hierarchy, but text output tools do group and indent for readability.
CircuitName:PDU1, DeviceSubType:PDU
CircuitName:PAN1, DeviceSubType:Panel, IPMPoweredBy:PDU1
CircuitName:BRK1, DeviceSubType:Breaker, IPMPoweredBy:PAN1
CircuitName:OUT1, DeviceSubType:Power Strip, IPMPoweredBy:BRK1
CircuitName:PAN2, DeviceSubType:Panel, IPMPoweredBy:PDU1
When a device is powered by multiple circuits, list them all, separated by the & (ampersand) delimiter. See
file /opt/ipm/examples/redundant.txt for complete examples.
DeviceName:alaska, IPMPoweredBy:SIDEA_Outlet & SIDEB_Outlet
ALIASES
The attribute names shown above are the official HPSIM attribute names. However, different sites call these
attributes by different names, sometimes in different languages. By using aliases, IPM allows administrators
to express attributes in their own language. In a special /var/opt/ipm/conf/alias.txt file,
administrators expand on the current examples.
# This is a list of alternate keywords that the IPM tools can
# recognize. Format for any pair is
# alias : HPSIM keyword
# Pairs may be delimited by comma, or newline.
# Comments and leading spaces are ignored.
# Below are examples
Data Center Id : DataCentreID
Lab : DataCentreID
Start: StartU, Height:HeightU
# These aliases are transitive. Use the short form once established.
Altura: Start
ALIASES
65