FSC-HPI-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for FSC-HPI-MIB.
606
Objects
Active
Status
3
Dependencies
Imported Objects
Objects
606 total| Object Name |
|---|
sni OBJECT IDENTIFIER .1.3.6.1.4.1.231 |
RFC1155-SMI Unknown .1.3.6.1.4.1.231 |
sniProductMibs OBJECT IDENTIFIER .1.3.6.1.4.1.231.2 |
fscHpi OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.60 |
fscHpiBMIB OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.60.6 |
hpiAdministration OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.60.6.1 |
hpiHpiVersionThe interface version is the version of the actual interface and
not the version of the implementation. It is a 24 bit value where
the most significant 8 bits represent the compatibility level
(with letters represented as the corresponding numbers);
the next 8 bits represent the major version number; and
the least significant 8 bits represent the minor version number.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.1.1 |
hpiAgentVersionThe Agent Implementation Versionro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.1.2 |
hpiSNMPResourceIdThis columnar node provides the Resource Id of the domain the
HPI-MIB SNMP implementation is running on. This is to help prevent
powering down the machine providing the SNMP service.ro Gauge .1.3.6.1.4.1.231.2.60.6.1.3 |
hpiDiscoverThis columnar node forces the discovery of all resources and
associated domains by the underlying management service.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.1.4 |
hpiDiscoveryStatusThe Status of the HPI Resource Discovery.ro Enumeration .1.3.6.1.4.1.231.2.60.6.1.10 |
hpiDiscoveryTimeThe time in seconds needed for Discoveryro Gauge .1.3.6.1.4.1.231.2.60.6.1.11 |
hpiDiscoveryAutoUpdateTimeThe time in seconds between two HPI Resource Discoveries.
A value of 0 means 'no auto discovery'.rw Gauge .1.3.6.1.4.1.231.2.60.6.1.12 |
hpiReconnectrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.1.20 |
hpiDomain OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.60.6.2 |
hpiDomainEntryCountThe number of Domain entries present in the system.ro Counter .1.3.6.1.4.1.231.2.60.6.2.1 |
hpiDomainTableThis table represents the management attributes common to all Domains
within the managed platform. The logical domain ID and the entity ID
are used to address an entity. SEQUENCE OF HpiDomainEntry .1.3.6.1.4.1.231.2.60.6.2.2 |
hpiDomainEntryDomain Info:
This structure is used to store the information regarding the domain
including information regarding the domain reference table (DRT) and
the resource presence table (RPT).
The DomainTag field is an informational value that supplies an
HPI User with naming information for the domain.
NOTE: Regarding timestamps - If the implementation cannot supply an
absolute timestamp, then it may supply a timestamp relative to some
system-defined epoch, such as system boot.
The value SAHPI_TIME_UNSPECIFIED indicates that the time of the
update cannot be determined. Otherwise, If the value is less
than or equal to SAHPI_TIME_MAX_RELATIVE, then it is relative; if it is
greater than SAHPI_TIME_MAX_RELATIVE, then it is absolute.
The GUID is used to uniquely identify a domain. A GUID value of zero
is not valid and indicates that the domain does not have an
associated GUID. HpiDomainEntry .1.3.6.1.4.1.231.2.60.6.2.2.1 |
hpiDomainIdThe SAHPI_UNSPECIFIED_DOMAIN_ID value is used to specify the
default domain.
SAHPI_UNSPECIFIED_DOMAIN_ID 0xFFFFFFFF(4294967295) Gauge .1.3.6.1.4.1.231.2.60.6.2.2.1.1 |
hpiDomainCapabilitiesThis definition defines the capabilities of a given domain.
A domain may support any number of capabilities.
autoinsertReadOnly
Indicates that the domain auto insert timeout value is
read-only and may not be modified using the
hpiHotSwapAutoInsertTimeoutSet columnar object.ro SaHpiDomainCapabilities .1.3.6.1.4.1.231.2.60.6.2.2.1.2 |
hpiDomainIsPeerIndicates that this domain participates in a peer relationship.
true = Domain is peer. false = Domain is not peer.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.2.2.1.3 |
hpiDomainTagTextTypeInformation tag associated with domain.
See Definition for SaHpiTextType for more details.rw SaHpiTextType .1.3.6.1.4.1.231.2.60.6.2.2.1.4 |
hpiDomainTagTextLanguageInformation tag associated with domain.
See Definition for SaHpiTextLanguage for more details.rw SaHpiTextLanguage .1.3.6.1.4.1.231.2.60.6.2.2.1.5 |
hpiDomainTagInformation tag associated with domain.
The type of date is specified
by hpiResourceTagTextType and hpiResourceTagLanguage.rw SaHpiText .1.3.6.1.4.1.231.2.60.6.2.2.1.6 |
hpiDomainReferenceUpdateCountThis count is incremented any time the table is changed.
It rolls over to zero when the maximum value (2^32) is reached.ro Gauge .1.3.6.1.4.1.231.2.60.6.2.2.1.7 |
hpiDomainReferenceUpdateTimestampThis timestamp is set any time the DRT table is changed.
Refer to SaHpiTime for full description.ro SaHpiTime .1.3.6.1.4.1.231.2.60.6.2.2.1.8 |
hpiDomainResourcePresenceUpdateCountThis count is incremented any time the RPT is changed.
It rolls over to zero when the maximum (2^32) value is reachedro Gauge .1.3.6.1.4.1.231.2.60.6.2.2.1.9 |
hpiDomainResourcePresenceUpdateTimestampThis timestamp is set any time the RPT table is changed.
Refer to SaHpiTime for full description.ro SaHpiTime .1.3.6.1.4.1.231.2.60.6.2.2.1.10 |
hpiDomainAlarmUpdateCountThis count is incremented any time the DAT is changed.
It rolls over to zero when the maximum value (2^32) is reachedro Gauge .1.3.6.1.4.1.231.2.60.6.2.2.1.11 |
hpiDomainAlarmUpdateTimestampThis timestamp is set any time the DAT is changed.
Refer to SaHpiTime for full description.ro SaHpiTime .1.3.6.1.4.1.231.2.60.6.2.2.1.12 |
hpiDomainActiveAlarmsCount of active alarms in the DAT.ro Gauge .1.3.6.1.4.1.231.2.60.6.2.2.1.13 |
hpiDomainCriticalAlarmsCount of active critical alarms in the DAT.ro Gauge .1.3.6.1.4.1.231.2.60.6.2.2.1.14 |
hpiDomainMajorAlarmsCount of active major alarms in the DAT.ro Gauge .1.3.6.1.4.1.231.2.60.6.2.2.1.15 |
hpiDomainMinorAlarmsCount of active minor alarms in the DAT.ro Gauge .1.3.6.1.4.1.231.2.60.6.2.2.1.16 |
hpiDomainAlarmUserLimitMaximum User Alarms that can be added to DAT.
0 = no fixed limit.ro Gauge .1.3.6.1.4.1.231.2.60.6.2.2.1.17 |
hpiDomainAlarmOverflowSet to True if there are one or more non-User Alarms
that are missing from the DAT because of space limitations.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.2.2.1.18 |
hpiDomainGuidThe GUID is used to uniquely identify a domain.
A GUID value of zero is not valid and indicates that the domain
does not have an associated GUID.
GUID - Globally Unique Identifier
The format if the ID follows that specified by the Wired for
Management Baseline, Version 2.0 specification. HPI uses
version 1 of the GUID format, with a 3-bit variant field of
10x (where x indicates 'don't care')ro SaHpiGuid .1.3.6.1.4.1.231.2.60.6.2.2.1.19 |
hpiDomainReferenceEntryCountThe number of DRT entries present in the hpiDomainReferenceTable.ro Counter .1.3.6.1.4.1.231.2.60.6.2.3 |
hpiDomainReferenceTableA table, provided by an HPI implementation, of additional domains
related to the current domain. SEQUENCE OF HpiDomainReferenceEntry .1.3.6.1.4.1.231.2.60.6.2.4 |
hpiDomainReferenceEntryThe Domain Reference Table (DRT) which provides information about
other domains associated with the domain. The two hpiDomainId are
used to uniquely identify a domain and a corresponding domain which
can be off peer or tiered domain architecture.
The DRT contains an entry for each associated domain, and HPI MIB
Users may read these entries to discover the presence of additional
domains within a 'System'. The discovered domains can, in turn, be
used to discover additional resources and domains.
The DRT is automatically built and maintained by the HPI
implementation. Domain entries in the DRT may change over time
if the 'System' configuration changes.
There are two types of domain references:
- A peer domain architecture, which consists of two or more domains
that are expected to contain the same resources and domain references.
Each domain in a peer relationship contains an RPT listing all
resources present in each domain.
- A tiered (child) domain architecture is used when all the resources
in a'system' cannot be accessed in a single domain. A 'parent'
domain references one or more 'child' domains in its DRT. The
'child' domains may be simple domains containing only resources,
or they may themselves be a 'parent' to other 'child' domains.
Domains in a tiered relationship are disjointed and do not contain
the same resources.
Note:
When a domain is added to the DRT (SAHPI_DOMAIN_REF_ADDED) and when
a domain is removed from the DRT (SAHPI_DOMAIN_REF_REMOVED) an event
is generated. HpiDomainReferenceEntry .1.3.6.1.4.1.231.2.60.6.2.4.1 |
hpiDomainReferenceDomain Gauge .1.3.6.1.4.1.231.2.60.6.2.4.1.1 |
hpiDomainReferenceIsPeerIndicates that this domain participates in a peer relationship.
true = Domain is peer. false = Domain is not peer (is a child)ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.2.4.1.2 |
hpiDomainAlarmEntryCountThe number of DomainAlarm entries present in the system.ro Counter .1.3.6.1.4.1.231.2.60.6.2.5 |
hpiDomainAlarmTableThis table represents the management attributes common to all Domains
within the managed platform. The logical domain ID and the entity ID
are used to address an entity. SEQUENCE OF HpiDomainAlarmEntry .1.3.6.1.4.1.231.2.60.6.2.6 |
hpiDomainAlarmEntryThis table is used to store alarm information. HpiDomainAlarmEntry .1.3.6.1.4.1.231.2.60.6.2.6.1 |
hpiDomainAlarmIdDomainAlarm Id SaHpiEntryId .1.3.6.1.4.1.231.2.60.6.2.6.1.1 |
hpiDomainAlarmTimestampTime when alarm was added to the DAT table.
Refer to SaHpiTime for full description.ro SaHpiTime .1.3.6.1.4.1.231.2.60.6.2.6.1.2 |
hpiDomainAlarmSeveritySeverity of alarm.
(Only used with DAT and Annunciator functions. This is not a valid
severity for events or alarms)
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.rw SaHpiSeverity .1.3.6.1.4.1.231.2.60.6.2.6.1.3 |
hpiDomainAlarmAcknowledgedAn HPI User acknowledges an alarm to indicate that it is aware of the alarm
and to influence platform-specific alarm annunciation that may be provided
by the implementation. Typically, an implementation ignores acknowledged
alarms when announcing an alarm on annunciation devices such as audible
sirens and dry contact closures. However, alarm annunciation is
implementation-specific.
An acknowledged alarm will have the Acknowledged field in the alarm entry
set to True.
DomainAlarms are acknowledged by one of two ways: a single alarm entry by DomainAlarmId
regardless of severity or as a group of alarm entries by Severity
regardless of DomainAlarmId.
To acknowledge all alarms contained within the DAT, set the Severity
parameter to allSeverities(256), and set the DomainAlarmId parameter to
SAHPI_ENTRY_UNSPECIFIED.
To acknowledge all alarms of a specific severity contained within the DAT,
set the Severity parameter to the appropriate value, and set the DomainAlarmId
parameter to SAHPI_ENTRY_UNSPECIFIED.
To acknowledge a single alarm entry, set the DomainAlarmId parameter to a value
other than SAHPI_ENTRY_UNSPECIFIED. The DomainAlarmId must be a valid identifier
for an alarm entry present in the DAT at the time of the function call.
If an alarm has been previously acknowledged, acknowledging it again has no
effect. However, this is not an error.
If the DomainAlarmId parameter has a value other than SAHPI_ENTRY_UNSPECIFIED,
the Severity parameter is ignored.
If the DomainAlarmId parameter is passed as SAHPI_ENTRY_UNSPECIFIED, and no
alarms are present that meet the requested Severity, this function will
have no effect. However, this is not an error.
SAHPI_ENTRY_UNSPECIFIED is defined as the same value as SAHPI_FIRST_ENTRY,
so using either symbol will have the same effect. However,
SAHPI_ENTRY_UNSPECIFIED should be used with this function for clarity.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.2.6.1.4 |
hpiDomainAlarmCondTypeEnumeration of status condition type.
This is read-only because creation is allowed for user Alarms onlyro SaHpiCondition .1.3.6.1.4.1.231.2.60.6.2.6.1.5 |
hpiDomainAlarmCondEntityPathEntity assoc. with status condition:
If resource manages a FRU, entity path of the FRU.
If resource manages a single entity, entity path of that entity.
If resource manages multiple entities, the entity path
of the 'primary' entity managed by the resource.
Must be set to the same value in every domain which
contains this resource.
This object converts HPI's hpiEntityPathT structure
and an OpenHPI canonical string. The canonical string is
formed by removing the SAHPI_ENT_ prefix from the
HPI types, and creating tuples for the entity types.
Order of significance is inverted to make entity paths
look more like Unix directory structure. It is also assumed
that {ROOT,0} exists implicitly before all of these entries.
For example:
{SYSTEM_CHASSIS,2}{PROCESSOR_BOARD,0}rw SaHpiEntityPath .1.3.6.1.4.1.231.2.60.6.2.6.1.6 |
hpiDomainAlarmCondSensorNumSensor associated with status Only valid if Type is
SAHPI_STATUS_COND_TYPE_SENSOR.
This is read-only because creation is allowed for user Alarms onlyro Gauge .1.3.6.1.4.1.231.2.60.6.2.6.1.7 |
hpiDomainAlarmCondSensorEventStateSensor event state. Only valid if hpiDomainAlarmCondType
is sensor(1).
This is read-only because creation is allowed for user Alarms onlyro SaHpiEventState .1.3.6.1.4.1.231.2.60.6.2.6.1.8 |
hpiDomainAlarmCondNameAIS compatible identifier associated with Status condition.
The Service Availability(TM) Forum Application Interface
Specification standardizes the interface between Service
Availability(TM) Forum compliant High Availability (HA)
middleware and service applications. http://www.saforum.orgrw OCTET STRING .1.3.6.1.4.1.231.2.60.6.2.6.1.9 |
hpiDomainAlarmCondMidManufacturer Id associated with status condition,
required when hpiDomainAlarmCondStatusCondType is oem(3).rw SaHpiManufacturerId .1.3.6.1.4.1.231.2.60.6.2.6.1.10 |
hpiDomainAlarmCondDataTypeOptional data associated with status condition.
For more details, see textual definitionrw SaHpiTextType .1.3.6.1.4.1.231.2.60.6.2.6.1.11 |
hpiDomainAlarmCondDataLanguageOptional data associated with status condition.
For more details, see textual definitionrw SaHpiTextLanguage .1.3.6.1.4.1.231.2.60.6.2.6.1.12 |
hpiDomainAlarmCondDataOptional data associated with status condition.
The type of date is specified by hpiDomainAlarmCondDomainAlarmaTextType and
hpiDomainAlarmCondDomainAlarmaTextLanguage.rw SaHpiText .1.3.6.1.4.1.231.2.60.6.2.6.1.13 |
hpiDomainAlarmInstanceStatusThis columnar node contains the status of the row and also
perform add and delete operations.rw Enumeration .1.3.6.1.4.1.231.2.60.6.2.6.1.14 |
hpiResourceEntryCountThe number of RPT entries present in the system.
This field is used to determine if new resources have been added
or existing removed.ro Counter .1.3.6.1.4.1.231.2.60.6.2.7 |
hpiResourceTableThe logical domain ID and the entity ID are used to address an entity. SEQUENCE OF HpiResourceEntry .1.3.6.1.4.1.231.2.60.6.2.8 |
hpiResourceEntryThis structure is used to store the RPT entry information.
The ResourceCapabilities field definies the capabilities of
the resource. This field must be non-zero for all valid
resources. The ResourceTag field is an informational value
that supplies the caller with naming information for the
resource. This should be set to the user-visible name for a
resource, which can be used to identify the resource in
messages to a human operator. For example, it could be set to
match a physical printed label attached to the primary entity
which the resource manages. See section 5.2.6,
SaHpiResourceTagSet(), on page 33. HpiResourceEntry .1.3.6.1.4.1.231.2.60.6.2.8.1 |
hpiResourceIdResource identifier.
The SAHPI_UNSPECIFIED_RESOURCE_ID value is used to specify the Domain
Event Log and to specify that there is no resource for such things as HPI
User events/alarms.
Note:
SAHPI_UNSPECIFIED_RESOURCE_ID 0xFFFFFFFF Gauge .1.3.6.1.4.1.231.2.60.6.2.8.1.1 |
hpiResourceEntityTypeexperimentalro SaHpiEntityType .1.3.6.1.4.1.231.2.60.6.2.8.1.2 |
hpiResourceEntityPathIf resource manages a FRU, entity path of the FRU.
If resource manages a single entity, entity path of that entity.
If resource manages multiple entities, the entity path
of the 'primary' entity managed by the resource.
Must be set to the same value in every domain which contains this
resource.
This object converts HPI's hpiEntityPathT structure and an OpenHPI
canonical string. The canonical string is formed by removing the
SAHPI_ENT_ prefix from the HPI types, and creating tuples for the
entity types.
Order of significance is inverted to make entity paths
look more like Unix directory structure. It is also assumed
that {ROOT,0} exists implicitly before all of these entries.
For example:
{SYSTEM_CHASSIS,2}{PROCESSOR_BOARD,0}ro SaHpiEntityPath .1.3.6.1.4.1.231.2.60.6.2.8.1.3 |
hpiResourceCapabilitiesResource Capabilities
This definition defines the capabilities of a given resource.
One resource may support any number of capabilities using this
string (each capability is seperated by a delimeter).
Because each entry in an RPT will have the
RESOURCE string, no value is not a valid value for the
capability flag, and is thus used to indicate 'no RPT
entry present' in some function calls.
RESOURCE
EVT_DEASSERTS
Indicates that all sensors on the resource have the property that their
Assertion and Deassertion event enable flags are the same. That is,
for all event states whose assertion triggers an event, it is
guaranteed that the deassertion of that event will also
trigger an event.
Thus, an HPI User may track the state of sensors on the
resource by monitoring events rather than polling for state changes.
AGGREGATE_STATUS
CONFIGURATION
MANAGED_HOTSWAP
Indicates that the resource supports the full managed hot swap model.
Since hot swap only makes sense for field-replaceable units, the
FRU capability string must also be set for this columnar object.
WATCHDOG
CONTROL
FRU
Indicates that the resource is a field-replaceable unit; i.e., it is
capable of being removed and replaced in a live system. If
MANAGED_HOTSWAP is also set, the resource supports
the full hot swap model. If MANAGED_HOTSWAP is not
set, the resource supports the simplified hot swap model.
ANNUNCIATOR
POWER
RESET
INVENTORY_DATA
EVENT_LOG
RDR
Indicates that a resource data record (RDR) repository is supplied
by the resource. Since the existence of an RDR is mandatory for all
management instruments, this capability must be asserted if the
resource contains any sensors, controls, watchdog timers, or inventory
data repositories.
SENSORro SaHpiCapabilities .1.3.6.1.4.1.231.2.60.6.2.8.1.4 |
hpiResourceSeverityIndicates the criticality that should be raised when the resource
is not responding.
Note: The enumerated named have +1 added as opposed to the SA HPI
spec for the same constants.rw SaHpiSeverity .1.3.6.1.4.1.231.2.60.6.2.8.1.6 |
hpiResourceFailedtrue = Resource Not Functional. false = Resource Functionalro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.2.8.1.7 |
hpiResourceInfoResourceRevhpiResourceInfo contains static configuration data
concerning the management controller associated with
the resource, or the resource itself.
Note this information is used to describe the resource;
that is, the piece of infrastructure which manages an
entity (or multiple entities) - NOT the entities for
which the resource probvides management. The purpose of the
hpiResourceInfoT structure is to provide information
that the HPI user may need in order to interact
correctly with the resource (e.g., recognize a
specific management controller which may have defined
OEM fields in sensors, OEM controls, etc.
All of the fields in the following structure may or
may not be used by a given resource.ro Gauge .1.3.6.1.4.1.231.2.60.6.2.8.1.8 |
hpiResourceInfoSpecificVerhpiResourceInfo contains static configuration data
concerning the management controller associated with
the resource, or the resource itself.
Note this information is used to describe the resource;
that is, the piece of infrastructure which manages an
entity (or multiple entities) - NOT the entities for
which the resource provides management. The purpose of the
hpiResourceInfoT structure is to provide information
that the HPI user may need in order to interact
correctly with the resource (e.g., recognize a
specific management controller which may have defined
OEM fields in sensors, OEM controls, etc.
All of the fields in the following structure may or
may not be used by a given resource.ro Gauge .1.3.6.1.4.1.231.2.60.6.2.8.1.9 |
hpiResourceInfoDeviceSupporthpiResourceInfo contains static configuration data
concerning the management controller associated with
the resource, or the resource itself.
Note this information is used to describe the resource;
that is, the piece of infrastructure which manages an
entity (or multiple entities) - NOT the entities for
which the resource provides management. The purpose of the
hpiResourceInfoT structure is to provide information
that the HPI user may need in order to interact
correctly with the resource (e.g., recognize a
specific management controller which may have defined
OEM fields in sensors, OEM controls, etc.
All of the fields in the following structure may or
may not be used by a given resource.ro Gauge .1.3.6.1.4.1.231.2.60.6.2.8.1.10 |
hpiResourceInfoManufacturerIdhpiResourceInfo contains static configuration data
concerning the management controller associated with
the resource, or the resource itself.
Note this information is used to describe the resource;
that is, the piece of infrastructure which manages an
entity (or multiple entities) - NOT the entities for
which the resource provides management. The purpose of the
hpiResourceInfoT structure is to provide information
that the HPI user may need in order to interact
correctly with the resource (e.g., recognize a
specific management controller which may have defined
OEM fields in sensors, OEM controls, etc.
All of the fields in the following structure may or
may not be used by a given resource.ro SaHpiManufacturerId .1.3.6.1.4.1.231.2.60.6.2.8.1.11 |
hpiResourceInfoProductIdhpiResourceInfo contains static configuration data
concerning the management controller associated with
the resource, or the resource itself.
Note this information is used to describe the resource;
that is, the piece of infrastructure which manages an
entity (or multiple entities) - NOT the entities for
which the resource provides management. The purpose of the
hpiResourceInfoT structure is to provide information
that the HPI user may need in order to interact
correctly with the resource (e.g., recognize a
specific management controller which may have defined
OEM fields in sensors, OEM controls, etc.
All of the fields in the following structure may or
may not be used by a given resource.ro Gauge .1.3.6.1.4.1.231.2.60.6.2.8.1.12 |
hpiResourceInfoFirmwareMajorRevhpiResourceInfo contains static configuration data
concerning the management controller associated with
the resource, or the resource itself.
Note this information is used to describe the resource;
that is, the piece of infrastructure which manages an
entity (or multiple entities) - NOT the entities for
which the resource provides management. The purpose of the
hpiResourceInfoT structure is to provide information
that the HPI user may need in order to interact
correctly with the resource (e.g., recognize a
specific management controller which may have defined
OEM fields in sensors, OEM controls, etc.
All of the fields in the following structure may or
may not be used by a given resource.ro Gauge .1.3.6.1.4.1.231.2.60.6.2.8.1.13 |
hpiResourceInfoFirmwareMinorRevhpiResourceInfo contains static configuration data
concerning the management controller associated with
the resource, or the resource itself.
Note this information is used to describe the resource;
that is, the piece of infrastructure which manages an
entity (or multiple entities) - NOT the entities for
which the resource provides management. The purpose of the
hpiResourceInfoT structure is to provide information
that the HPI user may need in order to interact
correctly with the resource (e.g., recognize a
specific management controller which may have defined
OEM fields in sensors, OEM controls, etc.
All of the fields in the following structure may or
may not be used by a given resource.ro Gauge .1.3.6.1.4.1.231.2.60.6.2.8.1.14 |
hpiResourceInfoAuxFirmwareRevhpiResourceInfo contains static configuration data
concerning the management controller associated with
the resource, or the resource itself.
Note this information is used to describe the resource;
that is, the piece of infrastructure which manages an
entity (or multiple entities) - NOT the entities for
which the resource provides management. The purpose of the
hpiResourceInfoT structure is to provide information
That the HPI user may need in order to interact
correctly with the resource (e.g., recognize a
specific management controller which may have defined
OEM fields in sensors, OEM controls, etc.
All of the fields in the following structure may or
may not be used by a given resource.ro Gauge .1.3.6.1.4.1.231.2.60.6.2.8.1.15 |
hpiResourceInfoGuidGUID - Globally Unique Identifier
The format if the ID follows that specified by the Wired for Management
Baseline, Version 2.0 specification. HPI uses version 1 of the GUID
format, with a 3-bit variant field of 10x (where x indicates 'don't care')ro SaHpiGuid .1.3.6.1.4.1.231.2.60.6.2.8.1.16 |
hpiResourceTagTypeSee Definition.rw SaHpiTextType .1.3.6.1.4.1.231.2.60.6.2.8.1.17 |
hpiResourceTagLanguageSee Definition.rw SaHpiTextLanguage .1.3.6.1.4.1.231.2.60.6.2.8.1.18 |
hpiResourceTagResource tag. The type of date is specified
by hpiResourceTagTextType and hpiResourceTagLanguage.rw SaHpiText .1.3.6.1.4.1.231.2.60.6.2.8.1.19 |
hpiResourceTextResource tag. The type of date is specified
by hpiResourceTagTextType and hpiResourceTagLanguage.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.2.8.1.20 |
hpiResourceParamControlThis object allows the user to save and restore parameters
associated with a specific resource. Valid actions for this
function include:
undefined(0) - resource has no concept of configurations.
restoreDefaultParm(1) - Restores the factory default settings
for a specific resource. Factory defaults
include sensor thresholds and configurations,
and resource- specific configuration parameters.
savaParm(2) - Stores the resource configuration parameters in
non-volatile storage. Resource configuration
parameters stored in non-volatile storage will
survive power cycles and resource resets.
restoreParm(3) - Restores resource configuration parameters
from non-volatile storage. Resource
configuration parameters include sensor
thresholds and sensor configurations, as well
as resource-specific.
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.rw Enumeration .1.3.6.1.4.1.231.2.60.6.2.8.1.21 |
hpiResourceResetStateThis function gets the reset state of an entity, allowing the HPI
User to determine if the entity is being held with its reset asserted.
If a resource manages multiple entities, this function will address
the entity which is identified in the RPT entry for the resource.
coldReset(1) and warmReset(2) are pulsed resets, and are not valid
values to be returned in hpiResetAction.
If the entity is not being held in reset (using resetAssert(3)),
the appropriate value is resetDeAssert(4).
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.rw Enumeration .1.3.6.1.4.1.231.2.60.6.2.8.1.22 |
hpiResourcePowerStateThis function gets the power state of an entity, allowing the
HPI User to determine if the entity is currently powered on or
off. If a resource manages multiple entities, this function will
address the entity which is identified in the RPT entry for the
resource.
cycle(3) is a pulsed power operation and is not a valid return
for the power state.
This function controls the hardware power on a FRU entity
regardless of what hot-swap state the resource is in. For
example, it is legal (and may be desirable) to cycle power
on the FRU even while it is in ACTIVE state in order to attempt
to clear a fault condition. Similarly, a resource could be
instructed to power on a FRU even while it is in INACTIVE state,
for example, in order to run off-line diagnostics.
Not all resources supporting hot swap will necessarily support
this function. In particular, resources that use the simplified
hot swap model may not have the ability to control FRU power.
This function may also be supported for non-FRU entities if power
control is available for those entities.
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.rw Enumeration .1.3.6.1.4.1.231.2.60.6.2.8.1.23 |
hpiHotSwap OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.60.6.2.11 |
hpiAutoInsertTableIn support of hpiAutoInsertTimeoutGet(), hpiAutoInsertTimeoutSet() SEQUENCE OF HpiAutoInsertEntry .1.3.6.1.4.1.231.2.60.6.2.11.1 |
hpiAutoInsertEntryTable of domains with a timeout for how long to wait before
the default auto-insertion policy is invoked on a resource within
a specific domain. HpiAutoInsertEntry .1.3.6.1.4.1.231.2.60.6.2.11.1.1 |
hpiAutoInsertTimeoutThis function allows the HPI SNMP Manager to configure a timeout for
how long to wait before the default auto-insertion policy is invoked
on a resource within a specific domain.
This columnar node accepts a parameter instructing each resource to impose
a delay before performing its default hot swap policy for
auto-insertion. The parameter may be set to
SAHPI_TIMEOUT_IMMEDIATE
( see SaHpiTime Textual-Convention for further details)
to direct resources to proceed immediately to auto-insertion, or to
SAHPI_TIMEOUT_BLOCK
( see SaHpiTime Textual-Convention for further details)
to prevent auto-insertion from ever occurring.
If the parameter is set to another value, then it defines the number
of nanoseconds between the time a hot swap event with
hpiHotSwapState == insertionPending(5) is generated, and the time
that the auto-insertion policy will be invoked for that resource.
If, during this time period, a hpiHotSwapPolicyCancel function
call is processed, the timer will be stopped, and the auto-insertion
policy will not be invoked. Each domain maintains a single
auto-insert timeout value and it is applied to all contained resources
upon insertion, which support managed hot swap. Once the auto-insertion
process begins, the HPI SNMP Manager will not be allowed to take control of
the insertion process; hence, the timeout should be set appropriately
to allow for this condition. Note that the timeout period begins
when the hot swap event with hpiHotSwapState == insertionPending(5)
is initially generated.rw SaHpiTime .1.3.6.1.4.1.231.2.60.6.2.11.1.1.1 |
hpiHotSwapEntryCountThe number of HotSwap entries present in the system.ro Counter .1.3.6.1.4.1.231.2.60.6.2.11.2 |
hpiHotSwapTableThis table represents management attributes common to all hot swappable
resources in the managed platform. The entries in this table are
straight from the HPI spec. This table builds upon information present
in the hpiResourceTable. SEQUENCE OF HpiHotSwapEntry .1.3.6.1.4.1.231.2.60.6.2.11.3 |
hpiHotSwapEntryAn entry describing a particular hot swappable entity. HpiHotSwapEntry .1.3.6.1.4.1.231.2.60.6.2.11.3.1 |
hpiHotSwapCapabilitiesro SaHpiHsCapabilities .1.3.6.1.4.1.231.2.60.6.2.11.3.1.1 |
hpiHotSwapIndicatorA FRU associated with a hot-swappable resource may include
a hot swap indicator such as a blue LED. This indicator signifies
that the FRU is ready for removal.
This columnar node allows the HPI SNMP Manager to retrieve and set the
state of this indicator.
When retrieving the values, the valid states are either
hpiHotSwapIndicator == off(1)
or
hpiHotSwapIndicator == on(2).
This columnar node will return information, regardless of
what hot swap state the resource is in.
When setting the values, valid states include
hpiHotSwapIndicator == off(1)
or
hpiHotSwapIndicator == on(2).
This function will set the indicator regardless of what hot swap
state the resource is in, though it is recommended that this
function be used only in conjunction with moving the resource to
the appropriate hot swap state.rw Enumeration .1.3.6.1.4.1.231.2.60.6.2.11.3.1.2 |
hpiHotSwapStateRefer to the textual convention for full details.ro SaHpiHotSwapState .1.3.6.1.4.1.231.2.60.6.2.11.3.1.3 |
hpiHotSwapExtractTimeoutThis function allows the HPI User to configure a timeout for how
long to wait before the default auto-extraction policy is invoked.
This function accepts a parameter instructing the resource to impose
a delay before performing its default hot swap policy for
auto-extraction. The parameter may be set to SAHPI_TIMEOUT_IMMEDIATE
to direct the resource to proceed immediately to auto-extraction, or
to SAHPI_TIMEOUT_BLOCK to prevent auto-extraction from ever occurring
on a resource. If the parameter is set to another value, then it
defines the number of nanoseconds between the time a hot swap event
with hpiHotSwapState = extractionPending(5) is generated and the
time that the auto-extraction policy will be invoked for the
resource. If, during this time period, a hpiHotSwapPolicyCancel
function call is processed, the timer will be stopped, and the
auto-extraction policy will not be invoked.
Once the auto-extraction process begins, the HPI User will not be
allowed to take control of the extraction process; hence, the
timeout should be set appropriately to allow for this condition.
Note that the timeout period begins when the hot swap event with
hpiHotSwapState = extractionPending(4) is initially generated.rw SaHpiTime .1.3.6.1.4.1.231.2.60.6.2.11.3.1.4 |
hpiHotSwapActionRequestA resource supporting hot swap typically requires a physical
action on the associated FRU to invoke an insertion or extraction
process. An insertion process is invoked by physically inserting
the FRU into a chassis. Physically opening an ejector latch or
pressing a button invokes the extraction process.
This columnar node allows the HPI User to invoke an insertion or
extraction process via software.
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.rw Enumeration .1.3.6.1.4.1.231.2.60.6.2.11.3.1.5 |
hpiHotSwapPolicyCancelA resource supporting hot swap typically supports default policies for
insertion and extraction. On insertion, the default policy may be for
the resource to turn the associated FRU~s local power on and to
de-assert reset. On extraction, the default policy may be for the
resource to immediately power off the FRU and turn on a hot swap
indicator. This function allows an HPI User, after receiving a hot
swap event with hpiHotSwapState equal to INSERTION_PENDING or
EXTRACTION_PENDING, to prevent the default policy from being executed.
Once the resource transitions to either the ACTIVE or INACTIVE state,
the default policies will once again execute, unless cancelled using
hpiHotSwapPolicyCancel.
The default policy cannot be canceled once it has begun to execute.
Because a resource that supports the simplified hot swap model will
never transition into INSERTION PENDING or EXTRACTION PENDING states,
this function is not applicable to those resources.
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.rw Enumeration .1.3.6.1.4.1.231.2.60.6.2.11.3.1.6 |
hpiHotSwapResourceRequestDepending on the values, the user can:
- use this function to request a resource to return to the ACTIVE state
from the EXTRACTION PENDING state in order to reject an extraction request.
Because a resource that supports the simplified hot swap model will never
transition into INSERTION PENDING or EXTRACTION PENDING states, this
function is not applicable to those resources.
- use this function to request a resource to return to the INACTIVE state
from the INSERTION PENDING state to abort a hot-swap insertion action.
Because a resource that supports the simplified hot swap model will never
transition into INSERTION PENDING or EXTRACTION PENDING states, this
function is not applicable to those resources.
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.rw Enumeration .1.3.6.1.4.1.231.2.60.6.2.11.3.1.7 |
hpiEvents OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.60.6.3 |
events OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.60.6.3.1 |
hpiEventInfoTable OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.60.6.3.1.1 |
hpiEventEntryCountThe number of events present in this table.
hpiEventCount represents the total of types currently in the
system. hpiDomainEventCount represents the subset of events
that are Domain events. The same relationship exists for
ResourceEvent, SensorEvent, SensorEnableChangeEvent,
HotSwapEvent, WatchdogEvent, HpiSwEvent, OemEvent, UserEvent.ro Counter .1.3.6.1.4.1.231.2.60.6.3.1.3 |
hpiEventTableEvent Master table. SEQUENCE OF HpiEventEntry .1.3.6.1.4.1.231.2.60.6.3.1.4 |
hpiEventEntryThis table presents the list of all events which are present in the
HPI system. The implementation decides how to manipulate the events
as they reach a large number. This table is used as a master event
table which an index that points to the specific sub-table which has
more details on the event.
Each time a new event is surfaced in the HPI system this table
increases by a new row and its respective sub-event table too
(hpiResourceEventTable, hpiOEMEventTable, etc). Futhermore
based on the type of event, an notification is generated as well. HpiEventEntry .1.3.6.1.4.1.231.2.60.6.3.1.4.1 |
hpiEventSeveritySeverity of event.
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.ro Enumeration .1.3.6.1.4.1.231.2.60.6.3.1.4.1.1 |
hpiEventTimeStampRefer to textual convention for SaHpiTime for more details.
The value is Equal to TIME_UNSPECIFIED if time is not available;
Absolute time if greater than TIME_MAX_RELATIVE, Relative time
if less than or equal to TIME_MAX_RELATIVE.ro SaHpiTime .1.3.6.1.4.1.231.2.60.6.3.1.4.1.2 |
hpiEventSourcero Enumeration .1.3.6.1.4.1.231.2.60.6.3.1.4.1.3 |
hpiEventTimeRefer to textual convention for SaHpiTime for more details.
The value is Equal to TIME_UNSPECIFIED if time is not available;
Absolute time if greater than TIME_MAX_RELATIVE, Relative time
if less than or equal to TIME_MAX_RELATIVE.ro OCTET STRING .1.3.6.1.4.1.231.2.60.6.3.1.4.1.4 |
hpiEventTypeEvent type.
Note: The enumerated named have +1 added as opposed to the
SA HPI spec for the same constants.ro Enumeration .1.3.6.1.4.1.231.2.60.6.3.1.4.1.5 |
hpiResourceEventEntryCountThis columnar node represents the subset of events that
are Resource Events.ro Counter .1.3.6.1.4.1.231.2.60.6.3.1.6 |
hpiResourceEventTableEvent table. SEQUENCE OF HpiResourceEventEntry .1.3.6.1.4.1.231.2.60.6.3.1.7 |
hpiResourceEventEntryResource events. HpiResourceEventEntry .1.3.6.1.4.1.231.2.60.6.3.1.7.1 |
hpiResourceEventTypeResource events are sent to indicate the failure or
subsequent restoration of a resource. Resource events can also be
used to announce the addition of a non-FRU resource to the RPT table.
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.ro Enumeration .1.3.6.1.4.1.231.2.60.6.3.1.7.1.1 |
hpiDomainEventEntryCounthpiDomainEventEntryCount represents the subset of events
that are Domain events.ro Counter .1.3.6.1.4.1.231.2.60.6.3.1.9 |
hpiDomainEventTableEvent table. SEQUENCE OF HpiDomainEventEntry .1.3.6.1.4.1.231.2.60.6.3.1.10 |
hpiDomainEventEntryDomain events. HpiDomainEventEntry .1.3.6.1.4.1.231.2.60.6.3.1.10.1 |
hpiDomainEventTypeDomain events are used to announce the addition of domain
references and the removal of domain references to the DRT.ro Enumeration .1.3.6.1.4.1.231.2.60.6.3.1.10.1.1 |
hpiDomainEventDomainDomain Id of domain added to or removed from DRT.ro Gauge .1.3.6.1.4.1.231.2.60.6.3.1.10.1.2 |
hpiSensorEventEntryCountThis columnar node represents the subset of events that
are Sensor Events.ro Counter .1.3.6.1.4.1.231.2.60.6.3.1.12 |
hpiSensorEventTableEvent table. SEQUENCE OF HpiSensorEventEntry .1.3.6.1.4.1.231.2.60.6.3.1.13 |
hpiSensorEventEntrySensor events. HpiSensorEventEntry .1.3.6.1.4.1.231.2.60.6.3.1.13.1 |
hpiSensorEventNumro Gauge .1.3.6.1.4.1.231.2.60.6.3.1.13.1.1 |
hpiSensorEventTypeRefer to the textual convention for more
details.ro SaHpiSensorType .1.3.6.1.4.1.231.2.60.6.3.1.13.1.2 |
hpiSensorEventCategoryEvent category: See TEXTUAL-CONVENTION, SaHpiEventCategory.ro SaHpiEventCategory .1.3.6.1.4.1.231.2.60.6.3.1.13.1.3 |
hpiSensorEventAssertionSensor Events and Sensor Event States:
Each Event State may be asserted or deasserted. The set of Event
States a sensor may support is defined by the sensor's
'Event Category.' A particular sensor, however, does not have to
support all the Event States defined for its event category.
The specific Event States that a particular sensor supports are
indicated in the 'Events' field in the sensor's RDR. A sensor is
not required to support any Event States. If no Event States are
supported by a sensor, the 'Events' field will be 0x0000. A sensor
may not support any Event States that are not defined for its event
category. Each Event State is independent, although in some event
categories the meaning assigned to the Event States will imply that
certain Event States will be mutually exclusive. For example, a
sensor that uses the SAHPI_EC_LIMIT event category should only have
one of the two Event States, SAHPI_ES_LIMIT_NOT_EXCEEDED or
SAHPI_ES_LIMIT_EXCEEDED asserted at any one time. Except where mutual
exclusion is implied, however, sensors may have multiple Event States
asserted simultaneously. For example, the event category
SAHPI_EC_THRESHOLD uses six different event states to report the
relationship between the value currently measured by the sensor and up
to six different 'threshold' values. Each threshold is independently
examined, and each Event State that represents a threshold that has
been 'crossed' will be asserted. Threshold values must be configured
so that 'Minor', 'Major' and 'Critical' thresholds are increasingly
extreme readings, such that when a 'Major' threshold has been crossed,
the corresponding 'Minor' threshold will also have been crossed, and
thus both Event States will be asserted. When a sensor Event State is
asserted or deasserted, an event may be generated by the resource.
The generated event identifies the sensor and the event state
being asserted or deasserted. The HPI implementation may assign event
severity levels for each event state assertion or deassertion on an
individual sensor basis.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.3.1.13.1.4 |
hpiSensorEventStateRefer to the textual convention for more details.ro SaHpiEventState .1.3.6.1.4.1.231.2.60.6.3.1.13.1.5 |
hpiSensorEventOptionalDataro OCTET STRING .1.3.6.1.4.1.231.2.60.6.3.1.13.1.6 |
hpiSensorEventTriggerReadingTypeRefer to the textual convention for more details.ro SaHpiSensorReadingType .1.3.6.1.4.1.231.2.60.6.3.1.13.1.7 |
hpiSensorEventTriggerReadingRefer to the textual convention for more details.ro SaHpiSensorReadingValue .1.3.6.1.4.1.231.2.60.6.3.1.13.1.8 |
hpiSensorEventTriggerThresholdTypeRefer to the textual convention for more details.ro SaHpiSensorReadingType .1.3.6.1.4.1.231.2.60.6.3.1.13.1.9 |
hpiSensorEventTriggerThresholdRefer to the textual convention for more details.ro SaHpiSensorReadingValue .1.3.6.1.4.1.231.2.60.6.3.1.13.1.10 |
hpiSensorEventPreviousStateRefer to the textual convention for more details.ro SaHpiEventState .1.3.6.1.4.1.231.2.60.6.3.1.13.1.11 |
hpiSensorEventCurrentStateRefer to SaHpiEventState textual convention for more details.ro SaHpiEventState .1.3.6.1.4.1.231.2.60.6.3.1.13.1.12 |
hpiSensorEventOemReserved for OEM use.ro Gauge .1.3.6.1.4.1.231.2.60.6.3.1.13.1.13 |
hpiSensorEventSpecificro Gauge .1.3.6.1.4.1.231.2.60.6.3.1.13.1.14 |
hpiSensorEnableChangeEventEntryCountThis columnar node represents the subset of events that
are Sensor Enable ChangeEvents.ro Counter .1.3.6.1.4.1.231.2.60.6.3.1.15 |
hpiSensorEnableChangeEventTableEvent table. SEQUENCE OF HpiSensorEnableChangeEventEntry .1.3.6.1.4.1.231.2.60.6.3.1.16 |
hpiSensorEnableChangeEventEntrySensor Enable Change events. HpiSensorEnableChangeEventEntry .1.3.6.1.4.1.231.2.60.6.3.1.16.1 |
hpiSensorEnableChangeEventNumro Gauge .1.3.6.1.4.1.231.2.60.6.3.1.16.1.1 |
hpiSensorEnableChangeEventTypeRefer to the textual convention for more
details.ro SaHpiSensorType .1.3.6.1.4.1.231.2.60.6.3.1.16.1.2 |
hpiSensorEnableChangeEventCategoryRefer to the textual convention for more details.ro SaHpiEventCategory .1.3.6.1.4.1.231.2.60.6.3.1.16.1.3 |
hpiSensorEnableChangeEventEnabledCurrent sensor enable status.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.3.1.16.1.4 |
hpiSensorEnableChangeEventEventsEnabledCurrent event enable status.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.3.1.16.1.5 |
hpiSensorEnableChangeEventAssertEventsRefer to the textual convention for more details.ro SaHpiEventState .1.3.6.1.4.1.231.2.60.6.3.1.16.1.6 |
hpiSensorEnableChangeEventDeassertEventsRefer to the textual convention for more details.ro SaHpiEventState .1.3.6.1.4.1.231.2.60.6.3.1.16.1.7 |
hpiSensorEnableChangeEventOptionalDataro OCTET STRING .1.3.6.1.4.1.231.2.60.6.3.1.16.1.8 |
hpiSensorEnableChangeEventCurrentStateCurrent set of asserted Event states.ro SaHpiEventState .1.3.6.1.4.1.231.2.60.6.3.1.16.1.9 |
hpiHotSwapEventEntryCountThis columnar node represents the subset of events that
are HotSwap Events.ro Counter .1.3.6.1.4.1.231.2.60.6.3.1.18 |
hpiHotSwapEventTableEvent table. SEQUENCE OF HpiHotSwapEventEntry .1.3.6.1.4.1.231.2.60.6.3.1.19 |
hpiHotSwapEventEntryHot Swap events. HpiHotSwapEventEntry .1.3.6.1.4.1.231.2.60.6.3.1.19.1 |
hpiHotSwapEventStateRefer to the textual convention for full details.ro SaHpiHotSwapState .1.3.6.1.4.1.231.2.60.6.3.1.19.1.1 |
hpiHotSwapEventPreviousStateRefer to the textual convention for full details.ro SaHpiHotSwapState .1.3.6.1.4.1.231.2.60.6.3.1.19.1.2 |
hpiWatchdogEventEntryCountThis columnar node represents the subset of events that
are Watchdog Events.ro Counter .1.3.6.1.4.1.231.2.60.6.3.1.21 |
hpiWatchdogEventTableEvent table. SEQUENCE OF HpiWatchdogEventEntry .1.3.6.1.4.1.231.2.60.6.3.1.22 |
hpiWatchdogEventEntryWatchdog events. HpiWatchdogEventEntry .1.3.6.1.4.1.231.2.60.6.3.1.22.1 |
hpiWatchdogEventNumro Gauge .1.3.6.1.4.1.231.2.60.6.3.1.22.1.1 |
hpiWatchdogEventActionThese enumerations represent the possible actions to be taken
upon watchdog timer timeout and the events that are generated
for watchdog actions.ro Enumeration .1.3.6.1.4.1.231.2.60.6.3.1.22.1.2 |
hpiWatchdogEventPreTimerActionThese enumerations represent the possible types of interrupts that may be
triggered by a watchdog pre-timer event. The actual meaning of these
operations may differ depending on the hardware architecture.ro SaHpiWatchdogPreTimerAction .1.3.6.1.4.1.231.2.60.6.3.1.22.1.3 |
hpiWatchdogEventUseWatchdog Timer Use
These enumerations represent the possible watchdog users that may have caused
the watchdog to expire. For instance, if watchdog is being used during power
on self test (POST), and it expires, the SAHPI_WTU_BIOS_POST expiration type
will be set. Most specific uses for Watchdog timer by users of HPI should
indicate SAHPI_WTU_SMS_OS if the use is to provide an OS-healthy heartbeat,
or SAHPI_WTU_OEM if it is used for some other purpose.ro SaHpiWatchdogTimerUse .1.3.6.1.4.1.231.2.60.6.3.1.22.1.4 |
hpiSoftwareEventEntryCountThis columnar node represents the subset of events that
are Software Events.ro Counter .1.3.6.1.4.1.231.2.60.6.3.1.24 |
hpiSoftwareEventTableEvent table. SEQUENCE OF HpiSoftwareEventEntry .1.3.6.1.4.1.231.2.60.6.3.1.25 |
hpiSoftwareEventEntrySoftware events. HpiSoftwareEventEntry .1.3.6.1.4.1.231.2.60.6.3.1.25.1 |
hpiSoftwareEventManufacturerIdRefer to the textual convention for more details.ro SaHpiManufacturerId .1.3.6.1.4.1.231.2.60.6.3.1.25.1.1 |
hpiSoftwareEventTypeThe following type defines the types of events that can be
reported by the HPI software implementation.
Audit events report a discrepancy in the audit process.
Audits are typically performed by HA software to detect problems.
Audits may look for such things as corrupted data stores,
inconsistent RPT information, or improperly managed queues.
Startup events report a failure to start-up properly, or
inconsistencies in persisted data.
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.ro Enumeration .1.3.6.1.4.1.231.2.60.6.3.1.25.1.2 |
hpiSoftwareEventTextTypeRefer to the textual convention for more details.ro SaHpiTextType .1.3.6.1.4.1.231.2.60.6.3.1.25.1.3 |
hpiSoftwareEventTextLanguageRefer to the textual convention for more details.ro SaHpiTextLanguage .1.3.6.1.4.1.231.2.60.6.3.1.25.1.4 |
hpiSoftwareEventTextRefer to the textual convention for more details.ro SaHpiText .1.3.6.1.4.1.231.2.60.6.3.1.25.1.5 |
hpiOEMEventEntryCountThis columnar node represents the subset of events that
are OEM Events.ro Counter .1.3.6.1.4.1.231.2.60.6.3.1.27 |
hpiOEMEventTableEvent table. SEQUENCE OF HpiOEMEventEntry .1.3.6.1.4.1.231.2.60.6.3.1.28 |
hpiOEMEventEntryOEM events. HpiOEMEventEntry .1.3.6.1.4.1.231.2.60.6.3.1.28.1 |
hpiOEMEventManufacturerIdRefer to the textual convention for more details.ro SaHpiManufacturerId .1.3.6.1.4.1.231.2.60.6.3.1.28.1.1 |
hpiOEMEventTextTypeRefer to the textual convention for more details.ro SaHpiTextType .1.3.6.1.4.1.231.2.60.6.3.1.28.1.2 |
hpiOEMEventTextLanguageRefer to the textual convention for more details.ro SaHpiTextLanguage .1.3.6.1.4.1.231.2.60.6.3.1.28.1.3 |
hpiOEMEventTextRefer to the textual convention for more details.ro SaHpiText .1.3.6.1.4.1.231.2.60.6.3.1.28.1.4 |
hpiUserEventEntryCountThis columnar node represents the subset of events that
are User Events.ro Counter .1.3.6.1.4.1.231.2.60.6.3.1.30 |
hpiUserEventTableEvent table. SEQUENCE OF HpiUserEventEntry .1.3.6.1.4.1.231.2.60.6.3.1.31 |
hpiUserEventEntryUser events. HpiUserEventEntry .1.3.6.1.4.1.231.2.60.6.3.1.31.1 |
hpiUserEventTextTypeRefer to SaHpiTextType for more details.rw SaHpiTextType .1.3.6.1.4.1.231.2.60.6.3.1.31.1.1 |
hpiUserEventTextLanguageRefer to hpiTextLanguage for more details.rw SaHpiTextLanguage .1.3.6.1.4.1.231.2.60.6.3.1.31.1.2 |
hpiUserEventTextRefer to hpiText for more details.rw SaHpiText .1.3.6.1.4.1.231.2.60.6.3.1.31.1.3 |
hpiUserEventRowStatusThis columnar node contains the status of the row and also
perform add and delete operations.
The status column uses four defined values:
- `active(1)', which indicates that the conceptual row is
available for use by the managed device;
- `createAndGo(4)', which is supplied by a management
station wishing to create a new instance of a
conceptual row (but not make it available for use by
the managed device). This function is used to add a
User Alarm to this User Event Table and also to the
to the Domain Alarm Table; When creating this row,
the value of hpiEventSeverity indice must not be one of
these minor(3), major(2), and critical(3). The effect of
creating a new row will also be reflected in the DAT - with
a new row there.
- `destroy(6)', which is supplied by a management station
wishing to delete all of the instances associated with
an existing conceptual row. This function allows the
HPI MIB User to delete a single User Alarm from the
User Event Table and Domain Alarm Table.
Only User Alarms added to the DAT and User Event Table can
be deleted. To delete a single, specific alarm, set the
hpiDomainAlarmId parameter to a value representing an
actual User Alarm in the User Event Table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.3.1.31.1.4 |
hpiAnnouncementEntryCountThe number of announcements present on this system.ro Counter .1.3.6.1.4.1.231.2.60.6.3.1.33 |
hpiAnnouncementTableTable of Announcements. SEQUENCE OF HpiAnnouncementEntry .1.3.6.1.4.1.231.2.60.6.3.1.34 |
hpiAnnouncementEntryThe table of announcements is used to provide
a common interface to varied mechanisms for announcing conditions.
Each announcement in an Annunciator's current set contains a severity level,
details describing the specific condition that is being reported, an
Acknowledged flag, a timestamp indicating when the announcement was added
to the set, and an EntryId that uniquely identifies the particular status
item within the set.
EntryIds are assigned to announcements as they are added to the set as well
as a Timestamp. After an announcement is deleted from the current set, its
EntryId may be reused for a newly added announcement as long as the new
announcement will have a different timestamp than any previously deleted
announcement using the same EntryId. Thus, the EntryId and Timestamp
together will uniquely identify any announcement, which was ever present
in the Annunciator's set.
The actual meaning of the Acknowledged flag is arbitrary, and the actions
taken by the platform when announcements are flagged as 'acknowledged' or
'unacknowledged' are implementation-specific. The intended use of the flag
is to indicate whether a particular announcement in the current set has been
recognized by whomever or whatever is inspecting the LEDs, displays, etc.,
that are being driven by the Annunciator management instrument. Thus, when
announcements are added to the current set, generally the flag should be set
to indicate that the condition is 'unacknowledged'. Later, either as the
result of an HPI User function call, or due to some implementation-dependent
action (such as pressing an 'acknowledge' button on a front-panel display),
the flag can be changed to indicate that the announcement is now 'acknowledged.'
The ability to acknowledge announcements is not controlled by the Annunciator
'mode' setting (Auto, User, or Shared). Any announcement may be acknowledged
by the HPI implementation, or via the hpiAnnunciatorAcknowledge() function
call, regardless of the current mode setting for the Annunciator.
Over time, announcements are added to and deleted from an Annunciator`s
current set of announcements. This may be done automatically by the HPI
implementation to reflect platform fault conditions, or by the HPI User
via the HPI interface. When announcements are added or deleted automatically
by the HPI implementation, it is implementation-specific which announcements
are added or removed. HpiAnnouncementEntry .1.3.6.1.4.1.231.2.60.6.3.1.34.1 |
hpiAnnouncementEntryIdEntry ID for record
Table Related Type Definitions
SAHPI_FIRST_ENTRY 0x00000000
SAHPI_LAST_ENTRY 0xFFFFFFFF SaHpiEntryId .1.3.6.1.4.1.231.2.60.6.3.1.34.1.1 |
hpiAnnouncementTimestampTime when announcement added to set.ro SaHpiTime .1.3.6.1.4.1.231.2.60.6.3.1.34.1.2 |
hpiAnnouncementAddedByUserTrue if added to set by HPI User, False if added
automatically by HPI implementation.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.3.1.34.1.3 |
hpiAnnouncementSeverityOnly used with DAT and Annunciator functions.
This is not a valid severity for events or alarms.rw Enumeration .1.3.6.1.4.1.231.2.60.6.3.1.34.1.4 |
hpiAnnouncementAcknowledgedAcknowledged flag.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.3.1.34.1.5 |
hpiAnnouncementStatusCondTypeStatus Condition Type.rw Enumeration .1.3.6.1.4.1.231.2.60.6.3.1.34.1.6 |
hpiAnnouncementEntityPathEntity assoc. with status condition.
This object converts HPI's hpiEntityPathT structure
and an OpenHPI canonical string. The canonical string is
formed by removing the SAHPI_ENT_ prefix from the
HPI types, and creating tuples for the entity types.
Order of significance is inverted to make entity paths
look more like Unix directory structure. It is also assumed
that {ROOT,0} exists implicitly before all of these entries.
For example:
{SYSTEM_CHASSIS,2}{PROCESSOR_BOARD,0}rw OCTET STRING .1.3.6.1.4.1.231.2.60.6.3.1.34.1.7 |
hpiAnnouncementSensorNumSensor associated with status Only valid
if Type is SAHPI_STATUS_COND_TYPE_SENSOR.rw Gauge .1.3.6.1.4.1.231.2.60.6.3.1.34.1.8 |
hpiAnnouncementEventStateSensor event state. Only valid if Type is
SAHPI_STATUS_COND_TYPE_SENSOR..rw SaHpiEventState .1.3.6.1.4.1.231.2.60.6.3.1.34.1.9 |
hpiAnnouncementNameAIS compatible identifier associated with Status condition.rw OCTET STRING .1.3.6.1.4.1.231.2.60.6.3.1.34.1.10 |
hpiAnnouncementMidManufacturer Id associated with status condition,
required when type is SAHPI_STATUS_COND_TYPE_OEM.rw SaHpiManufacturerId .1.3.6.1.4.1.231.2.60.6.3.1.34.1.11 |
hpiAnnouncementTextTypeField Data.
See Definition for SaHpiTextType for more details.rw SaHpiTextType .1.3.6.1.4.1.231.2.60.6.3.1.34.1.12 |
hpiAnnouncementTextLanguageField Data.
See Definition for SaHpiTextLanguage for more details.rw SaHpiTextLanguage .1.3.6.1.4.1.231.2.60.6.3.1.34.1.13 |
hpiAnnouncementTextField Data.
The type of date is specified
by hpiResourceTagTextType and hpiResourceTagLanguage.rw SaHpiText .1.3.6.1.4.1.231.2.60.6.3.1.34.1.14 |
hpiAnnouncementDeleteThis function allows the HPI User to delete a single
announcement. Announcements may be deleted individually by specifying
a specific index and setting this columnar node to destroy(6).rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.3.1.34.1.15 |
eventLog OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.60.6.3.2 |
hpiEventLogInfoTableA table definining Event Log Information records. SEQUENCE OF HpiEventLogInfoEntry .1.3.6.1.4.1.231.2.60.6.3.2.1 |
hpiEventLogInfoEntryEach resource has a Event Log Information record, which contains
per resource pertient logging information.
Use hpiResourceId = 0 (SAHPI_UNSPECIFIED_RESOURCE_ID)
to address the Domain Event Log. HpiEventLogInfoEntry .1.3.6.1.4.1.231.2.60.6.3.2.1.1 |
hpiEventLogInfoEntriesThe number of active entries contained in the log.ro Gauge .1.3.6.1.4.1.231.2.60.6.3.2.1.1.1 |
hpiEventLogInfoSizeThe total number of entries the log is able to hold.ro Gauge .1.3.6.1.4.1.231.2.60.6.3.2.1.1.2 |
hpiEventLogInfoUserEventMaxSizeThe UserEventMaxSize entry indicates the maximum size of the
text buffer data field in an HPI User event that is supported
by the Event Log implementation. If the implementation does
not enforce a more restrictive data length, it should be set
to SAHPI_MAX_TEXT_BUFFER_LENGTH (255).ro Gauge .1.3.6.1.4.1.231.2.60.6.3.2.1.1.3 |
hpiEventLogInfoUpdateTimestampThe UpdateTimestamp entry denotes the time of the last
update to the Event Log.
Refer to SaHpiTime for full description.ro SaHpiTime .1.3.6.1.4.1.231.2.60.6.3.2.1.1.4 |
hpiEventLogInfoTimeThe Time entry denotes the Event Log's idea of the
current time; i.e the timestamp that would be placed on an
entry if it was added now.
Remarks:
Entries placed in the Event Log after this function is called will
have Event Log timestamps (i.e., the Timestamp field in the
SaHpiEventLogEntryT structure) based on the new time. Setting
the clock does not affect existing Event Log entries. If the time
is set to a relative time, subsequent entries placed in the Event Log
will have an Event Log timestamp expressed as a relative time; if the
time is set to an absolute time, subsequent entries will have an Event
Log timestamp expressed as an absolute time.
This function only sets the Event Log time clock and does not have any
direct bearing on the timestamps placed on events (i.e., the Timestamp
field in the SaHpiEventT structure), or the timestamps placed in the
domain RPT info record. Setting the clocks used to generate timestamps
other than Event Log timestamps is implementation-dependent, and should
be documented by the HPI implementation provider.
Some underlying implementations may not be able to handle the same
relative and absolute time ranges, as those defined in HPI. Such
limitations will be documented in implementation-specific documentation.
When a time value is set in a region that is not supported by the
implementation, an error code of SNMP_GENERROR will be returned.
Refer to SaHpiTime for full description.rw SaHpiTime .1.3.6.1.4.1.231.2.60.6.3.2.1.1.5 |
hpiEventLogInfoEnabledThe Enabled entry indicates whether the log is enabled.
If the event log is 'disabled' no events generated within the
HPI implementation will be added to the event log.
User events may still be added to the event log.
When the event log is 'enabled' events may be automatically
added to the event log as they are generated in a resource
or a domain, however, it is implementation-specific which
events are automatically added to any event log.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.3.2.1.1.6 |
hpiEventLogInfoOverflowFlagThe OverflowFlag entry indicates the log has overflowed.
Events have been dropped or overwritten due to a table overflow.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.3.2.1.1.7 |
hpiEventLogInfoOverflowResetableIndicates if the the overflow falg can be cleared
by calling hpiEventLogInfoOverflowReset.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.3.2.1.1.8 |
hpiEventLogInfoOverflowActionThe OverflowAction entry indicates the behavior of the
event log when an overflow occurs.
drop(1) New entries are dropped when log is full
overwrite(2) Event Log overwrites existing entries when Event Log
is fullro Enumeration .1.3.6.1.4.1.231.2.60.6.3.2.1.1.9 |
hpiEventLogInfoClearLogThis function erases the contents of the specified Event Log.rw Enumeration .1.3.6.1.4.1.231.2.60.6.3.2.1.1.10 |
hpiEventLogEntryCountA table definining Event Log records.ro Counter .1.3.6.1.4.1.231.2.60.6.3.2.4 |
hpiEventLogTableA table definining Event Log records. SEQUENCE OF HpiEventLogEntry .1.3.6.1.4.1.231.2.60.6.3.2.5 |
hpiEventLogEntryThis section defines the types associated with the SEL. HpiEventLogEntry .1.3.6.1.4.1.231.2.60.6.3.2.5.1 |
hpiEventLogSeveritySeverity of event.
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.ro Enumeration .1.3.6.1.4.1.231.2.60.6.3.2.5.1.1 |
hpiEventLogAddedTimestampRefer to SaHpiTime for full description.ro SaHpiTime .1.3.6.1.4.1.231.2.60.6.3.2.5.1.2 |
hpiEventLogSourcero Enumeration .1.3.6.1.4.1.231.2.60.6.3.2.5.1.3 |
hpiEventLogTimeRefer to SaHpiTime for full description.ro OCTET STRING .1.3.6.1.4.1.231.2.60.6.3.2.5.1.4 |
hpiEventLogTypeThe type of event.
Note: The enumerated named have +1 added as opposed to the
SA HPI spec for the same constants.ro Enumeration .1.3.6.1.4.1.231.2.60.6.3.2.5.1.5 |
hpiResourceEventLogEntryCountThis columnar node represents the subset of events that
are Resource Events.ro Counter .1.3.6.1.4.1.231.2.60.6.3.2.6 |
hpiResourceEventLogTableEvent table. SEQUENCE OF HpiResourceEventLogEntry .1.3.6.1.4.1.231.2.60.6.3.2.7 |
hpiResourceEventLogEntryResource events. HpiResourceEventLogEntry .1.3.6.1.4.1.231.2.60.6.3.2.7.1 |
hpiResourceEventLogTypeResource events are sent to indicate the failure or
subsequent restoration of a resource. Resource events can also be
used to announce the addition of a non-FRU resource to the RPT table.
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.ro Enumeration .1.3.6.1.4.1.231.2.60.6.3.2.7.1.1 |
hpiDomainEventLogEntryCounthpiDomainEventEntryCount represents the subset of events
that are Domain events.ro Counter .1.3.6.1.4.1.231.2.60.6.3.2.8 |
hpiDomainEventLogTableEvent table. SEQUENCE OF HpiDomainEventLogEntry .1.3.6.1.4.1.231.2.60.6.3.2.9 |
hpiDomainEventLogEntryDomain events. HpiDomainEventLogEntry .1.3.6.1.4.1.231.2.60.6.3.2.9.1 |
hpiDomainEventLogTypeDomain events are used to announce the addition of domain
references and the removal of domain references to the DRT.ro Enumeration .1.3.6.1.4.1.231.2.60.6.3.2.9.1.1 |
hpiDomainEventLogDomainDomain Id of domain added to or removed from DRT.ro Gauge .1.3.6.1.4.1.231.2.60.6.3.2.9.1.2 |
hpiSensorEventLogEntryCountThis columnar node represents the subset of events that
are Sensor Events.ro Counter .1.3.6.1.4.1.231.2.60.6.3.2.10 |
hpiSensorEventLogTableEvent table. SEQUENCE OF HpiSensorEventLogEntry .1.3.6.1.4.1.231.2.60.6.3.2.11 |
hpiSensorEventLogEntrySensor events. HpiSensorEventLogEntry .1.3.6.1.4.1.231.2.60.6.3.2.11.1 |
hpiSensorEventLogNumro Gauge .1.3.6.1.4.1.231.2.60.6.3.2.11.1.1 |
hpiSensorEventLogTypeRefer to the textual convention for more
details.ro SaHpiSensorType .1.3.6.1.4.1.231.2.60.6.3.2.11.1.2 |
hpiSensorEventLogCategoryEvent category: See TEXTUAL-CONVENTION, SaHpiEventCategory.ro SaHpiEventCategory .1.3.6.1.4.1.231.2.60.6.3.2.11.1.3 |
hpiSensorEventLogAssertionSensor Events and Sensor Event States:
Each Event State may be asserted or deasserted. The set of Event
States a sensor may support is defined by the sensor's
'Event Category.' A particular sensor, however, does not have to
support all the Event States defined for its event category.
The specific Event States that a particular sensor supports are
indicated in the 'Events' field in the sensor's RDR. A sensor is
not required to support any Event States. If no Event States are
supported by a sensor, the 'Events' field will be 0x0000. A sensor
may not support any Event States that are not defined for its event
category. Each Event State is independent, although in some event
categories the meaning assigned to the Event States will imply that
certain Event States will be mutually exclusive. For example, a
sensor that uses the SAHPI_EC_LIMIT event category should only have
one of the two Event States, SAHPI_ES_LIMIT_NOT_EXCEEDED or
SAHPI_ES_LIMIT_EXCEEDED asserted at any one time. Except where mutual
exclusion is implied, however, sensors may have multiple Event States
asserted simultaneously. For example, the event category
SAHPI_EC_THRESHOLD uses six different event states to report the
relationship between the value currently measured by the sensor and up
to six different 'threshold' values. Each threshold is independently
examined, and each Event State that represents a threshold that has
been 'crossed' will be asserted. Threshold values must be configured
so that 'Minor', 'Major' and 'Critical' thresholds are increasingly
extreme readings, such that when a 'Major' threshold has been crossed,
the corresponding 'Minor' threshold will also have been crossed, and
thus both Event States will be asserted. When a sensor Event State is
asserted or deasserted, an event may be generated by the resource.
The generated event identifies the sensor and the event state
being asserted or deasserted. The HPI implementation may assign event
severity levels for each event state assertion or deassertion on an
individual sensor basis.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.3.2.11.1.4 |
hpiSensorEventLogStateRefer to the textual convention for more details.ro SaHpiEventState .1.3.6.1.4.1.231.2.60.6.3.2.11.1.5 |
hpiSensorEventLogOptionalDataro OCTET STRING .1.3.6.1.4.1.231.2.60.6.3.2.11.1.6 |
hpiSensorEventLogTriggerReadingTypeRefer to the textual convention for more details.ro SaHpiSensorReadingType .1.3.6.1.4.1.231.2.60.6.3.2.11.1.7 |
hpiSensorEventLogTriggerReadingRefer to the textual convention for more details.ro SaHpiSensorReadingValue .1.3.6.1.4.1.231.2.60.6.3.2.11.1.8 |
hpiSensorEventLogTriggerThresholdTypeRefer to the textual convention for more details.ro SaHpiSensorReadingType .1.3.6.1.4.1.231.2.60.6.3.2.11.1.9 |
hpiSensorEventLogTriggerThresholdRefer to the textual convention for more details.ro SaHpiSensorReadingValue .1.3.6.1.4.1.231.2.60.6.3.2.11.1.10 |
hpiSensorEventLogPreviousStateRefer to the textual convention for more details.ro SaHpiEventState .1.3.6.1.4.1.231.2.60.6.3.2.11.1.11 |
hpiSensorEventLogCurrentStateRefer to SaHpiEventState textual convention for more details.ro SaHpiEventState .1.3.6.1.4.1.231.2.60.6.3.2.11.1.12 |
hpiSensorEventLogOemReserved for OEM use.ro Gauge .1.3.6.1.4.1.231.2.60.6.3.2.11.1.13 |
hpiSensorEventLogSpecificro Gauge .1.3.6.1.4.1.231.2.60.6.3.2.11.1.14 |
hpiSensorEnableChangeEventLogEntryCountThis columnar node represents the subset of events that
are Sensor Enable ChangeEvents.ro Counter .1.3.6.1.4.1.231.2.60.6.3.2.12 |
hpiSensorEnableChangeEventLogTableEvent table. SEQUENCE OF HpiSensorEnableChangeEventLogEntry .1.3.6.1.4.1.231.2.60.6.3.2.13 |
hpiSensorEnableChangeEventLogEntrySensor Enable Change events. HpiSensorEnableChangeEventLogEntry .1.3.6.1.4.1.231.2.60.6.3.2.13.1 |
hpiSensorEnableChangeEventLogNumro Gauge .1.3.6.1.4.1.231.2.60.6.3.2.13.1.1 |
hpiSensorEnableChangeEventLogTypeRefer to the textual convention for more
details.ro SaHpiSensorType .1.3.6.1.4.1.231.2.60.6.3.2.13.1.2 |
hpiSensorEnableChangeEventLogCategoryRefer to the textual convention for more details.ro SaHpiEventCategory .1.3.6.1.4.1.231.2.60.6.3.2.13.1.3 |
hpiSensorEnableChangeEventLogEnabledCurrent sensor enable status.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.3.2.13.1.4 |
hpiSensorEnableChangeEventLogEventsEnabledCurrent event enable status.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.3.2.13.1.5 |
hpiSensorEnableChangeEventLogAssertEventsRefer to the textual convention for more details.ro SaHpiEventState .1.3.6.1.4.1.231.2.60.6.3.2.13.1.6 |
hpiSensorEnableChangeEventLogDeassertEventsRefer to the textual convention for more details.ro SaHpiEventState .1.3.6.1.4.1.231.2.60.6.3.2.13.1.7 |
hpiSensorEnableChangeEventLogOptionalDataro OCTET STRING .1.3.6.1.4.1.231.2.60.6.3.2.13.1.8 |
hpiSensorEnableChangeEventLogCurrentStateCurrent set of asserted Event states.ro SaHpiEventState .1.3.6.1.4.1.231.2.60.6.3.2.13.1.9 |
hpiHotSwapEventLogEntryCountThis columnar node represents the subset of events that
are HotSwap Events.ro Counter .1.3.6.1.4.1.231.2.60.6.3.2.14 |
hpiHotSwapEventLogTableEvent table. SEQUENCE OF HpiHotSwapEventLogEntry .1.3.6.1.4.1.231.2.60.6.3.2.15 |
hpiHotSwapEventLogEntryHot Swap events. HpiHotSwapEventLogEntry .1.3.6.1.4.1.231.2.60.6.3.2.15.1 |
hpiHotSwapEventLogStateRefer to the textual convention for full details.ro SaHpiHotSwapState .1.3.6.1.4.1.231.2.60.6.3.2.15.1.1 |
hpiHotSwapEventLogPreviousStateRefer to the textual convention for full details.ro SaHpiHotSwapState .1.3.6.1.4.1.231.2.60.6.3.2.15.1.2 |
hpiWatchdogEventLogEntryCountThis columnar node represents the subset of events that
are Watchdog Events.ro Counter .1.3.6.1.4.1.231.2.60.6.3.2.16 |
hpiWatchdogEventLogTableEvent table. SEQUENCE OF HpiWatchdogEventLogEntry .1.3.6.1.4.1.231.2.60.6.3.2.17 |
hpiWatchdogEventLogEntryWatchdog events. HpiWatchdogEventLogEntry .1.3.6.1.4.1.231.2.60.6.3.2.17.1 |
hpiWatchdogEventLogNumro Gauge .1.3.6.1.4.1.231.2.60.6.3.2.17.1.1 |
hpiWatchdogEventLogActionThese enumerations represent the possible actions to be taken
upon watchdog timer timeout and the events that are generated
for watchdog actions.ro Enumeration .1.3.6.1.4.1.231.2.60.6.3.2.17.1.2 |
hpiWatchdogEventLogPreTimerActionThese enumerations represent the possible types of interrupts that may be
triggered by a watchdog pre-timer event. The actual meaning of these
operations may differ depending on the hardware architecture.ro SaHpiWatchdogPreTimerAction .1.3.6.1.4.1.231.2.60.6.3.2.17.1.3 |
hpiWatchdogEventLogUseWatchdog Timer Use
These enumerations represent the possible watchdog users that may have caused
the watchdog to expire. For instance, if watchdog is being used during power
on self test (POST), and it expires, the SAHPI_WTU_BIOS_POST expiration type
will be set. Most specific uses for Watchdog timer by users of HPI should
indicate SAHPI_WTU_SMS_OS if the use is to provide an OS-healthy heartbeat,
or SAHPI_WTU_OEM if it is used for some other purpose.ro SaHpiWatchdogTimerUse .1.3.6.1.4.1.231.2.60.6.3.2.17.1.4 |
hpiSoftwareEventLogEntryCountThis columnar node represents the subset of events that
are Software Events.ro Counter .1.3.6.1.4.1.231.2.60.6.3.2.18 |
hpiSoftwareEventLogTableEvent table. SEQUENCE OF HpiSoftwareEventLogEntry .1.3.6.1.4.1.231.2.60.6.3.2.19 |
hpiSoftwareEventLogEntrySoftware events. HpiSoftwareEventLogEntry .1.3.6.1.4.1.231.2.60.6.3.2.19.1 |
hpiSoftwareEventLogManufacturerIdRefer to the textual convention for more details.ro SaHpiManufacturerId .1.3.6.1.4.1.231.2.60.6.3.2.19.1.1 |
hpiSoftwareEventLogTypeThe following type defines the types of events that can be
reported by the HPI software implementation.
Audit events report a discrepancy in the audit process.
Audits are typically performed by HA software to detect problems.
Audits may look for such things as corrupted data stores,
inconsistent RPT information, or improperly managed queues.
Startup events report a failure to start-up properly, or
inconsistencies in persisted data.
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.ro Enumeration .1.3.6.1.4.1.231.2.60.6.3.2.19.1.2 |
hpiSoftwareEventLogTextTypeRefer to the textual convention for more details.ro SaHpiTextType .1.3.6.1.4.1.231.2.60.6.3.2.19.1.3 |
hpiSoftwareEventLogTextLanguageRefer to the textual convention for more details.ro SaHpiTextLanguage .1.3.6.1.4.1.231.2.60.6.3.2.19.1.4 |
hpiSoftwareEventLogTextRefer to the textual convention for more details.ro SaHpiText .1.3.6.1.4.1.231.2.60.6.3.2.19.1.5 |
hpiOEMEventLogEntryCountThis columnar node represents the subset of events that
are OEM Events.ro Counter .1.3.6.1.4.1.231.2.60.6.3.2.20 |
hpiOEMEventLogTableEvent table. SEQUENCE OF HpiOEMEventLogEntry .1.3.6.1.4.1.231.2.60.6.3.2.21 |
hpiOEMEventLogEntryOEM events. HpiOEMEventLogEntry .1.3.6.1.4.1.231.2.60.6.3.2.21.1 |
hpiOEMEventLogManufacturerIdRefer to the textual convention for more details.ro SaHpiManufacturerId .1.3.6.1.4.1.231.2.60.6.3.2.21.1.1 |
hpiOEMEventLogTextTypeRefer to the textual convention for more details.ro SaHpiTextType .1.3.6.1.4.1.231.2.60.6.3.2.21.1.2 |
hpiOEMEventLogTextLanguageRefer to the textual convention for more details.ro SaHpiTextLanguage .1.3.6.1.4.1.231.2.60.6.3.2.21.1.3 |
hpiOEMEventLogTextRefer to the textual convention for more details.ro SaHpiText .1.3.6.1.4.1.231.2.60.6.3.2.21.1.4 |
hpiUserEventLogEntryCountThis columnar node represents the subset of events that
are User Events.ro Counter .1.3.6.1.4.1.231.2.60.6.3.2.22 |
hpiUserEventLogTableEvent table. SEQUENCE OF HpiUserEventLogEntry .1.3.6.1.4.1.231.2.60.6.3.2.23 |
hpiUserEventLogEntryUser events. HpiUserEventLogEntry .1.3.6.1.4.1.231.2.60.6.3.2.23.1 |
hpiUserEventLogTextTypeRefer to SaHpiTextType for more details.rw SaHpiTextType .1.3.6.1.4.1.231.2.60.6.3.2.23.1.1 |
hpiUserEventLogTextLanguageRefer to hpiTextLanguage for more details.rw SaHpiTextLanguage .1.3.6.1.4.1.231.2.60.6.3.2.23.1.2 |
hpiUserEventLogTextRefer to hpiText for more details.rw SaHpiText .1.3.6.1.4.1.231.2.60.6.3.2.23.1.3 |
hpiUserEventLogRowStatusThis columnar node contains the status of the row and also
perform add and delete operations.
The status column uses four defined values:
- `active(1)', which indicates that the conceptual row is
available for use by the managed device;
- `createAndGo(4)', which is supplied by a management
station wishing to create a new instance of a
conceptual row (but not make it available for use by
the managed device). This function is used to add a
User Alarm to this User Event Table and also to the
to the Domain Alarm Table; When creating this row,
the value of hpiEventSeverity indice must not be one of
these minor(3), major(2), and critical(3). The effect of
creating a new row will also be reflected in the DAT - with
a new row there.
- `destroy(6)', which is supplied by a management station
wishing to delete all of the instances associated with
an existing conceptual row. This function allows the
HPI MIB User to delete a single User Alarm from the
User EventLog Table and Domain Alarm Table.
Only User Alarms added to the DAT and User EventLog Table can
be deleted. To delete a single, specific alarm, set the
hpiDomainAlarmId parameter to a value representing an
actual User Alarm in the User EventLog Table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.3.2.23.1.4 |
hpiResources OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.60.6.4 |
hpiRdrEntryCountNumber of resource data records in this system.ro Counter .1.3.6.1.4.1.231.2.60.6.4.1 |
hpiRdrTableA table definining RDR records. SEQUENCE OF HpiRdrEntry .1.3.6.1.4.1.231.2.60.6.4.2 |
hpiRdrEntryThe following describes the different types of records that exist
within a RDR repository and the RDR super-structure to all of the
specific RDR types (sensor, inventory data, watchdog, etc.). HpiRdrEntry .1.3.6.1.4.1.231.2.60.6.4.2.1 |
hpiRdrTypeType of RDR entry.
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec. Enumeration .1.3.6.1.4.1.231.2.60.6.4.2.1.1 |
hpiRdrIdResource Data Record identifier - the instrumentID.
Together with the hpiRdrType this identifies the RDR within a
resource. Note: this is not the RDR record ID SaHpiInstrumentId .1.3.6.1.4.1.231.2.60.6.4.2.1.2 |
hpiRdrEntityPathIf resource manages a FRU, entity path of the FRU.
If resource manages a single entity, entity path of
that entity.
If resource manages multiple entities, the entity path
of the 'primary' entity managed by the resource.
Must be set to the same value in every domain which
contains this resource.
This object converts HPI's hpiEntityPathT structure
and an OpenHPI canonical string. The canonical string is
formed by removing the SAHPI_ENT_ prefix from the
HPI types, and creating tuples for the entity types.
Order of significance is inverted to make entity paths
look more like Unix directory structure. It is also assumed
that {ROOT,0} exists implicitly before all of these entries.
For example:
{SYSTEM_CHASSIS,2}{PROCESSOR_BOARD,0}ro SaHpiEntityPath .1.3.6.1.4.1.231.2.60.6.4.2.1.3 |
hpiRdrIsFruEntity is a FRU. This field is Only valid if the
Entity path given in the 'Entity' field is different from the Entity
path in the RPT entry for the resource.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.2.1.4 |
hpiRdrIdStringTypeSee definitionro SaHpiTextType .1.3.6.1.4.1.231.2.60.6.4.2.1.5 |
hpiRdrIdStringLanguageSee definitionro SaHpiTextLanguage .1.3.6.1.4.1.231.2.60.6.4.2.1.6 |
hpiRdrIdStringID String of the RDR entry.ro SaHpiText .1.3.6.1.4.1.231.2.60.6.4.2.1.7 |
hpiRdrIdTextID String of the RDR entry in readable form.
(valid only, if type == (text, , ) and language == ?).ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.2.1.8 |
hpiRdrControlsCountNumber of control data records in this system.ro Counter .1.3.6.1.4.1.231.2.60.6.4.3 |
hpiControls OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.60.6.4.4 |
hpiCtrlEntryCountThe number of control resource data records in the system.ro Counter .1.3.6.1.4.1.231.2.60.6.4.4.1 |
hpiCtrlTableA table definining Control Resource Data Records. SEQUENCE OF HpiCtrlEntry .1.3.6.1.4.1.231.2.60.6.4.4.2 |
hpiCtrlEntryDefinition of the control resource data record. HpiCtrlEntry .1.3.6.1.4.1.231.2.60.6.4.4.2.1 |
hpiCtrlOutputTypeThis enumeration defines the what the control's output will be.
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.ro Enumeration .1.3.6.1.4.1.231.2.60.6.4.4.2.1.1 |
hpiCtrlTypeThis enumerated type defines the different types of generic controls.
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.ro Enumeration .1.3.6.1.4.1.231.2.60.6.4.4.2.1.2 |
hpiCtrlDefaultModeThis object describes how the control is managed.
The control may be managed automatically by the implementation
(auto mode). Or it may be managed by the HPI User (manual mode).
Some controls allow their modes to be changed, allowing the HPI User
to determine if they will manage the control, or relinquish the
management to the implementation. But, other controls do not allow
the mode to be changed. These static-mode controls are indicated
with the hpiCtrlReadOnly flag set as part of the default control
mode.
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.rw Enumeration .1.3.6.1.4.1.231.2.60.6.4.4.2.1.3 |
hpiCtrlDefaultModeReadOnlyIndicates if mode is read-onlyro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.4.2.1.4 |
hpiCtrlWriteOnlyIndicates if mode is write-onlyro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.4.2.1.5 |
hpiCtrlOemReserved for OEM usero Gauge .1.3.6.1.4.1.231.2.60.6.4.4.2.1.6 |
hpiCtrlDigitalEntryCountThe number of control resource data records of
type DIGITAL in the system.ro Counter .1.3.6.1.4.1.231.2.60.6.4.4.3 |
hpiCtrlDigitalTableA table definining Control Resource Data Records. SEQUENCE OF HpiCtrlDigitalEntry .1.3.6.1.4.1.231.2.60.6.4.4.4 |
hpiCtrlDigitalEntryDefinition of the control resource data record. HpiCtrlDigitalEntry .1.3.6.1.4.1.231.2.60.6.4.4.4.1 |
hpiCtrlDigitalValuerw Enumeration .1.3.6.1.4.1.231.2.60.6.4.4.4.1.1 |
hpiCtrlDigitalDefaultro Enumeration .1.3.6.1.4.1.231.2.60.6.4.4.4.1.2 |
hpiCtrlDiscreteEntryCountThe number of control resource data records of
type DISCRETE in the system.ro Counter .1.3.6.1.4.1.231.2.60.6.4.4.5 |
hpiCtrlDiscreteTableA table definining Control Resource Data Records. SEQUENCE OF HpiCtrlDiscreteEntry .1.3.6.1.4.1.231.2.60.6.4.4.6 |
hpiCtrlDiscreteEntryDefinition of the control resource data record. HpiCtrlDiscreteEntry .1.3.6.1.4.1.231.2.60.6.4.4.6.1 |
hpiCtrlDiscreteValuerw Gauge .1.3.6.1.4.1.231.2.60.6.4.4.6.1.1 |
hpiCtrlDiscreteDefaultro Gauge .1.3.6.1.4.1.231.2.60.6.4.4.6.1.2 |
hpiCtrlAnalogEntryCountThe number of control resource data records of
type ANALOG in the system.ro Counter .1.3.6.1.4.1.231.2.60.6.4.4.7 |
hpiCtrlAnalogTableA table definining Control Resource Data Records. SEQUENCE OF HpiCtrlAnalogEntry .1.3.6.1.4.1.231.2.60.6.4.4.8 |
hpiCtrlAnalogEntryDefinition of the control resource data record. HpiCtrlAnalogEntry .1.3.6.1.4.1.231.2.60.6.4.4.8.1 |
hpiCtrlAnalogValuerw INTEGER .1.3.6.1.4.1.231.2.60.6.4.4.8.1.1 |
hpiCtrlAnalogMinro INTEGER .1.3.6.1.4.1.231.2.60.6.4.4.8.1.2 |
hpiCtrlAnalogMaxro INTEGER .1.3.6.1.4.1.231.2.60.6.4.4.8.1.3 |
hpiCtrlAnalogDefaultro INTEGER .1.3.6.1.4.1.231.2.60.6.4.4.8.1.4 |
hpiCtrlStreamEntryCountThe number of control resource data records of
type STREAM in the system.ro Counter .1.3.6.1.4.1.231.2.60.6.4.4.9 |
hpiCtrlStreamTableA table definining Control Resource Data Records. SEQUENCE OF HpiCtrlStreamEntry .1.3.6.1.4.1.231.2.60.6.4.4.10 |
hpiCtrlStreamEntryDefinition of the control resource data record. HpiCtrlStreamEntry .1.3.6.1.4.1.231.2.60.6.4.4.10.1 |
hpiCtrlStreamValueRepeatrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.4.10.1.1 |
hpiCtrlStreamValueStreamrw OCTET STRING .1.3.6.1.4.1.231.2.60.6.4.4.10.1.2 |
hpiCtrlStreamDefaultRepeatro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.4.10.1.3 |
hpiCtrlStreamDefaultStreamro OCTET STRING .1.3.6.1.4.1.231.2.60.6.4.4.10.1.4 |
hpiCtrlOemEntryCountThe number of control resource data records of
type OEM in the system.ro Counter .1.3.6.1.4.1.231.2.60.6.4.4.11 |
hpiCtrlOemTableA table definining Control Resource Data Records. SEQUENCE OF HpiCtrlOemEntry .1.3.6.1.4.1.231.2.60.6.4.4.12 |
hpiCtrlOemEntryDefinition of the control resource data record. HpiCtrlOemEntry .1.3.6.1.4.1.231.2.60.6.4.4.12.1 |
hpiCtrlOemValueMIdrw Gauge .1.3.6.1.4.1.231.2.60.6.4.4.12.1.1 |
hpiCtrlOemValueBodyrw OCTET STRING .1.3.6.1.4.1.231.2.60.6.4.4.12.1.2 |
hpiCtrlOemConfigDataro OCTET STRING .1.3.6.1.4.1.231.2.60.6.4.4.12.1.3 |
hpiCtrlOemDefaultMIdro Gauge .1.3.6.1.4.1.231.2.60.6.4.4.12.1.4 |
hpiCtrlOemDefaultBodyro OCTET STRING .1.3.6.1.4.1.231.2.60.6.4.4.12.1.5 |
hpiRdrSensorCountNumber of sensor data records in this system.ro Counter .1.3.6.1.4.1.231.2.60.6.4.5 |
hpiSensor OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.60.6.4.6 |
hpiSensorEntryCountThe number of sensor resource data records in the system.ro Counter .1.3.6.1.4.1.231.2.60.6.4.6.1 |
hpiSensorTableA table definining Sensors records. SEQUENCE OF HpiSensorEntry .1.3.6.1.4.1.231.2.60.6.4.6.2 |
hpiSensorEntryThis is the sensor resource data record which
describes all of the static data associated with a sensor. HpiSensorEntry .1.3.6.1.4.1.231.2.60.6.4.6.2.1 |
hpiSensorTypeRefer to the textual convention for more details.ro SaHpiSensorType .1.3.6.1.4.1.231.2.60.6.4.6.2.1.1 |
hpiSensorCtrlTrue if HPI User can enable or disable sensor via
hpiSensorEnableSet.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.6.2.1.2 |
hpiSensorEnableWhen reading, this object returns the current sensor enable status
for an addressed sensor. When writing this object sets the sensor
enable status for an addressed sensor. If a sensor is disabled,
the rows in hpiSensorReadingCurrent for that sensor will not be
present, and no events will be generated for the sensor.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.6.2.1.3 |
hpiSensorEventIsSupportedThe Bit mask Events is not SAHPI_ES_UNSPECIFIEDro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.6.2.1.4 |
hpiSensorEventCurrStateThe current event state of a sensorro SaHpiEventState .1.3.6.1.4.1.231.2.60.6.4.6.2.1.5 |
hpiSensorEventCatSensors category. Sensor events contain an event category and event
state. Depending on the event category, the event states take on
different meanings for events generated by specific sensors.
The generic(128) category can be used for discrete sensors which
have state meanings other than those identified with other event
categories.ro SaHpiEventCategory .1.3.6.1.4.1.231.2.60.6.4.6.2.1.6 |
hpiSensorEventCtrlperEvent(1) Event message control per event,
or by entire sensor; sensor event enable
Status can be changed, and assert/deassert
masks can be changed.
readOnlyMasks(2): Control for entire sensor only; sensor
event enable status can be changed, but
assert/deassert masks cannot be changed.
readOnly(3): Event control not supported; sensor event
enable status cannot be changed and
ssert/deassert masks cannot be changed.
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.rw Enumeration .1.3.6.1.4.1.231.2.60.6.4.6.2.1.7 |
hpiSensorEventEnableWhen reading, this object returns the current sensor event enable
status for an addressed sensor. When writing this object sets the
sensor event enable status for an addressed sensor. If event
generation for a sensor is disabled, no events will be generated
as a result of the assertion or deassertion of any event state,
regardless of the setting of the assert or deassert event masks
for the sensor. If event generation for a sensor is enabled, events
will be generated when event states are asserted or deasserted,
according to the settings of the assert and deassert event masks
for the sensor. Event states may still be read for a sensor even
if event generation is disabled, by reading the
hpiSensorReadingCurrent table.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.6.2.1.8 |
hpiSensorReadingIsSupportedIndicates if sensor data readings are supported.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.6.2.1.9 |
hpiSensorRangeSupportedDefines which range flags the sensor supports. They
can be MIN, MAX, NOMINAL, NORMAL_MAX, NORMAL_MIN, or
nothing if the sensor does not support any ranges.ro SaHpiSensorRangeFlags .1.3.6.1.4.1.231.2.60.6.4.6.2.1.10 |
hpiSensorThresholdIsAccessiblero TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.6.2.1.11 |
hpiSensorOemReserved for OEM use.ro Gauge .1.3.6.1.4.1.231.2.60.6.4.6.2.1.12 |
hpiSensorReadingCountThe number of sensor resource data records in the system.ro Counter .1.3.6.1.4.1.231.2.60.6.4.6.3 |
hpiSensorReadingTableA table definining Sensors records. SEQUENCE OF HpiSensorReadingEntry .1.3.6.1.4.1.231.2.60.6.4.6.4 |
hpiSensorReadingEntryThis is the sensor resource data record which
describes all of the static data associated with a sensor. HpiSensorReadingEntry .1.3.6.1.4.1.231.2.60.6.4.6.4.1 |
hpiSensorReadingDataTypero SaHpiSensorReadingType .1.3.6.1.4.1.231.2.60.6.4.6.4.1.1 |
hpiSensorReadingBaseUnitsro SaHpiSensorUnits .1.3.6.1.4.1.231.2.60.6.4.6.4.1.2 |
hpiSensorReadingModifierUnitsro SaHpiSensorUnits .1.3.6.1.4.1.231.2.60.6.4.6.4.1.3 |
hpiSensorReadingModifierUsero SaHpiSensorModUnitUse .1.3.6.1.4.1.231.2.60.6.4.6.4.1.4 |
hpiSensorReadingPercentagero TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.6.4.1.5 |
hpiSensorReadingCurrentValuero SaHpiSensorReadingValue .1.3.6.1.4.1.231.2.60.6.4.6.4.1.6 |
hpiSensorReadingAccuracyFactorThe Accuracy Factor is expressed as a floating point percentage
(e.g. 0.05 = 5%) and represents statistically how close the measured
reading is to the actual value. It is an interpreted value that
figures in all sensor accuracies, resolutions, and tolerances.ro Double .1.3.6.1.4.1.231.2.60.6.4.6.4.1.7 |
hpiSensorRangeCountThe number of sensor resource data records in the system.ro Counter .1.3.6.1.4.1.231.2.60.6.4.6.5 |
hpiSensorRangeTableA table definining Sensors records. SEQUENCE OF HpiSensorRangeEntry .1.3.6.1.4.1.231.2.60.6.4.6.6 |
hpiSensorRangeEntryThis is the sensor resource data record which
describes all of the static data associated with a sensor. HpiSensorRangeEntry .1.3.6.1.4.1.231.2.60.6.4.6.6.1 |
hpiSensorRangeFlagsro SaHpiSensorRangeFlags .1.3.6.1.4.1.231.2.60.6.4.6.6.1.1 |
hpiSensorRangeDataTypero SaHpiSensorReadingType .1.3.6.1.4.1.231.2.60.6.4.6.6.1.2 |
hpiSensorRangeMinro SaHpiSensorReadingValue .1.3.6.1.4.1.231.2.60.6.4.6.6.1.3 |
hpiSensorRangeMaxro SaHpiSensorReadingValue .1.3.6.1.4.1.231.2.60.6.4.6.6.1.4 |
hpiSensorRangeNormalMinro SaHpiSensorReadingValue .1.3.6.1.4.1.231.2.60.6.4.6.6.1.5 |
hpiSensorRangeNormalMaxro SaHpiSensorReadingValue .1.3.6.1.4.1.231.2.60.6.4.6.6.1.6 |
hpiSensorRangeNominalro SaHpiSensorReadingValue .1.3.6.1.4.1.231.2.60.6.4.6.6.1.7 |
hpiSensorThresholdCountThe number of sensor resource data records in the system.ro Counter .1.3.6.1.4.1.231.2.60.6.4.6.7 |
hpiSensorThresholdTableA table definining Sensors records. SEQUENCE OF HpiSensorThresholdEntry .1.3.6.1.4.1.231.2.60.6.4.6.8 |
hpiSensorThresholdEntryThis is the sensor resource data record which
describes all of the static data associated with a sensor. HpiSensorThresholdEntry .1.3.6.1.4.1.231.2.60.6.4.6.8.1 |
hpiSensorThresholdReadMaskro SaHpiSensorThdMask .1.3.6.1.4.1.231.2.60.6.4.6.8.1.2 |
hpiSensorThresholdWriteMaskro SaHpiSensorThdMask .1.3.6.1.4.1.231.2.60.6.4.6.8.1.3 |
hpiSensorThresholdNonLinearro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.6.8.1.4 |
hpiSensorThresholdDataTypero SaHpiSensorReadingType .1.3.6.1.4.1.231.2.60.6.4.6.8.1.5 |
hpiSensorThresholdLowMinorro SaHpiSensorReadingValue .1.3.6.1.4.1.231.2.60.6.4.6.8.1.6 |
hpiSensorThresholdLowMajorro SaHpiSensorReadingValue .1.3.6.1.4.1.231.2.60.6.4.6.8.1.7 |
hpiSensorThresholdLowCriticalro SaHpiSensorReadingValue .1.3.6.1.4.1.231.2.60.6.4.6.8.1.8 |
hpiSensorThresholdUpMinorro SaHpiSensorReadingValue .1.3.6.1.4.1.231.2.60.6.4.6.8.1.9 |
hpiSensorThresholdUpMajorro SaHpiSensorReadingValue .1.3.6.1.4.1.231.2.60.6.4.6.8.1.10 |
hpiSensorThresholdUpCriticalro SaHpiSensorReadingValue .1.3.6.1.4.1.231.2.60.6.4.6.8.1.11 |
hpiSensorThresholdPosThdHysteresisro SaHpiSensorReadingValue .1.3.6.1.4.1.231.2.60.6.4.6.8.1.12 |
hpiSensorThresholdNegThdHysteresisro SaHpiSensorReadingValue .1.3.6.1.4.1.231.2.60.6.4.6.8.1.13 |
hpiSensorEvtCat OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.60.6.4.6.10 |
hpiSensorEvtCatThresholdEntryCountro Counter .1.3.6.1.4.1.231.2.60.6.4.6.10.1 |
hpiSensorEvtCatThresholdTable SEQUENCE OF HpiSensorEvtCatThresholdEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.2 |
hpiSensorEvtCatThresholdEntryThis is the sensor resource data record which
describes all of the static data associated with a sensor. HpiSensorEvtCatThresholdEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.2.1 |
hpiSensorEvtCatThresholdCurrentEventsRefer to the textual convention for more details.ro SaHpiThresholdEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.2.1.1 |
hpiSensorEvtCatThresholdSupportedEventsRefer to the textual convention for more details.ro SaHpiThresholdEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.2.1.2 |
hpiSensorEvtCatThresholdAssertEventsRefer to the textual convention for more details.ro SaHpiThresholdEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.2.1.3 |
hpiSensorEvtCatThresholdDeassertEventsRefer to the textual convention for more details.ro SaHpiThresholdEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.2.1.4 |
hpiSensorEvtCatUsageEntryCountro Counter .1.3.6.1.4.1.231.2.60.6.4.6.10.3 |
hpiSensorEvtCatUsageTable SEQUENCE OF HpiSensorEvtCatUsageEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.4 |
hpiSensorEvtCatUsageEntryThis is the sensor resource data record which
describes all of the static data associated with a sensor. HpiSensorEvtCatUsageEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.4.1 |
hpiSensorEvtCatUsageCurrentEventsRefer to the textual convention for more details.ro SaHpiUsageEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.4.1.1 |
hpiSensorEvtCatUsageSupportedEventsRefer to the textual convention for more details.ro SaHpiUsageEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.4.1.2 |
hpiSensorEvtCatUsageAssertEventsRefer to the textual convention for more details.ro SaHpiUsageEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.4.1.3 |
hpiSensorEvtCatUsageDeassertEventsRefer to the textual convention for more details.ro SaHpiUsageEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.4.1.4 |
hpiSensorEvtCatStateEntryCountro Counter .1.3.6.1.4.1.231.2.60.6.4.6.10.5 |
hpiSensorEvtCatStateTable SEQUENCE OF HpiSensorEvtCatStateEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.6 |
hpiSensorEvtCatStateEntryThis is the sensor resource data record which
describes all of the static data associated with a sensor. HpiSensorEvtCatStateEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.6.1 |
hpiSensorEvtCatStateCurrentEventsRefer to the textual convention for more details.ro SaHpiStateEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.6.1.1 |
hpiSensorEvtCatStateSupportedEventsRefer to the textual convention for more details.ro SaHpiStateEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.6.1.2 |
hpiSensorEvtCatStateAssertEventsRefer to the textual convention for more details.ro SaHpiStateEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.6.1.3 |
hpiSensorEvtCatStateDeassertEventsRefer to the textual convention for more details.ro SaHpiStateEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.6.1.4 |
hpiSensorEvtCatPredFailEntryCountro Counter .1.3.6.1.4.1.231.2.60.6.4.6.10.7 |
hpiSensorEvtCatPredFailTable SEQUENCE OF HpiSensorEvtCatPredFailEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.8 |
hpiSensorEvtCatPredFailEntryThis is the sensor resource data record which
describes all of the static data associated with a sensor. HpiSensorEvtCatPredFailEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.8.1 |
hpiSensorEvtCatPredFailCurrentEventsRefer to the textual convention for more details.ro SaHpiPredFailEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.8.1.1 |
hpiSensorEvtCatPredFailSupportedEventsRefer to the textual convention for more details.ro SaHpiPredFailEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.8.1.2 |
hpiSensorEvtCatPredFailAssertEventsRefer to the textual convention for more details.ro SaHpiPredFailEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.8.1.3 |
hpiSensorEvtCatPredFailDeassertEventsRefer to the textual convention for more details.ro SaHpiPredFailEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.8.1.4 |
hpiSensorEvtCatLimitEntryCountro Counter .1.3.6.1.4.1.231.2.60.6.4.6.10.9 |
hpiSensorEvtCatLimitTable SEQUENCE OF HpiSensorEvtCatLimitEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.10 |
hpiSensorEvtCatLimitEntryThis is the sensor resource data record which
describes all of the static data associated with a sensor. HpiSensorEvtCatLimitEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.10.1 |
hpiSensorEvtCatLimitCurrentEventsRefer to the textual convention for more details.ro SaHpiLimitEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.10.1.1 |
hpiSensorEvtCatLimitSupportedEventsRefer to the textual convention for more details.ro SaHpiLimitEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.10.1.2 |
hpiSensorEvtCatLimitAssertEventsRefer to the textual convention for more details.ro SaHpiLimitEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.10.1.3 |
hpiSensorEvtCatLimitDeassertEventsRefer to the textual convention for more details.ro SaHpiLimitEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.10.1.4 |
hpiSensorEvtCatPerformanceEntryCountro Counter .1.3.6.1.4.1.231.2.60.6.4.6.10.11 |
hpiSensorEvtCatPerformanceTable SEQUENCE OF HpiSensorEvtCatPerformanceEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.12 |
hpiSensorEvtCatPerformanceEntryThis is the sensor resource data record which
describes all of the static data associated with a sensor. HpiSensorEvtCatPerformanceEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.12.1 |
hpiSensorEvtCatPerformanceCurrentEventsRefer to the textual convention for more details.ro SaHpiPerformanceEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.12.1.1 |
hpiSensorEvtCatPerformanceSupportedEventsRefer to the textual convention for more details.ro SaHpiPerformanceEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.12.1.2 |
hpiSensorEvtCatPerformanceAssertEventsRefer to the textual convention for more details.ro SaHpiPerformanceEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.12.1.3 |
hpiSensorEvtCatPerformanceDeassertEventsRefer to the textual convention for more details.ro SaHpiPerformanceEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.12.1.4 |
hpiSensorEvtCatSeverityEntryCountro Counter .1.3.6.1.4.1.231.2.60.6.4.6.10.13 |
hpiSensorEvtCatSeverityTable SEQUENCE OF HpiSensorEvtCatSeverityEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.14 |
hpiSensorEvtCatSeverityEntryThis is the sensor resource data record which
describes all of the static data associated with a sensor. HpiSensorEvtCatSeverityEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.14.1 |
hpiSensorEvtCatSeverityCurrentEventsRefer to the textual convention for more details.ro SaHpiSeverityEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.14.1.1 |
hpiSensorEvtCatSeveritySupportedEventsRefer to the textual convention for more details.ro SaHpiSeverityEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.14.1.2 |
hpiSensorEvtCatSeverityAssertEventsRefer to the textual convention for more details.ro SaHpiSeverityEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.14.1.3 |
hpiSensorEvtCatSeverityDeassertEventsRefer to the textual convention for more details.ro SaHpiSeverityEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.14.1.4 |
hpiSensorEvtCatPresenceEntryCountro Counter .1.3.6.1.4.1.231.2.60.6.4.6.10.15 |
hpiSensorEvtCatPresenceTable SEQUENCE OF HpiSensorEvtCatPresenceEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.16 |
hpiSensorEvtCatPresenceEntryThis is the sensor resource data record which
describes all of the static data associated with a sensor. HpiSensorEvtCatPresenceEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.16.1 |
hpiSensorEvtCatPresenceCurrentEventsRefer to the textual convention for more details.ro SaHpiPresenceEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.16.1.1 |
hpiSensorEvtCatPresenceSupportedEventsRefer to the textual convention for more details.ro SaHpiPresenceEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.16.1.2 |
hpiSensorEvtCatPresenceAssertEventsRefer to the textual convention for more details.ro SaHpiPresenceEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.16.1.3 |
hpiSensorEvtCatPresenceDeassertEventsRefer to the textual convention for more details.ro SaHpiPresenceEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.16.1.4 |
hpiSensorEvtCatEnableEntryCountro Counter .1.3.6.1.4.1.231.2.60.6.4.6.10.17 |
hpiSensorEvtCatEnableTable SEQUENCE OF HpiSensorEvtCatEnableEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.18 |
hpiSensorEvtCatEnableEntryThis is the sensor resource data record which
describes all of the static data associated with a sensor. HpiSensorEvtCatEnableEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.18.1 |
hpiSensorEvtCatEnableCurrentEventsRefer to the textual convention for more details.ro SaHpiEnableEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.18.1.1 |
hpiSensorEvtCatEnableSupportedEventsRefer to the textual convention for more details.ro SaHpiEnableEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.18.1.2 |
hpiSensorEvtCatEnableAssertEventsRefer to the textual convention for more details.ro SaHpiEnableEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.18.1.3 |
hpiSensorEvtCatEnableDeassertEventsRefer to the textual convention for more details.ro SaHpiEnableEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.18.1.4 |
hpiSensorEvtCatAvailabilityEntryCountro Counter .1.3.6.1.4.1.231.2.60.6.4.6.10.19 |
hpiSensorEvtCatAvailabilityTable SEQUENCE OF HpiSensorEvtCatAvailabilityEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.20 |
hpiSensorEvtCatAvailabilityEntryThis is the sensor resource data record which
describes all of the static data associated with a sensor. HpiSensorEvtCatAvailabilityEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.20.1 |
hpiSensorEvtCatAvailabilityCurrentEventsRefer to the textual convention for more details.ro SaHpiAvailabilityEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.20.1.1 |
hpiSensorEvtCatAvailabilitySupportedEventsRefer to the textual convention for more details.ro SaHpiAvailabilityEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.20.1.2 |
hpiSensorEvtCatAvailabilityAssertEventsRefer to the textual convention for more details.ro SaHpiAvailabilityEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.20.1.3 |
hpiSensorEvtCatAvailabilityDeassertEventsRefer to the textual convention for more details.ro SaHpiAvailabilityEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.20.1.4 |
hpiSensorEvtCatRedundancyEntryCountro Counter .1.3.6.1.4.1.231.2.60.6.4.6.10.21 |
hpiSensorEvtCatRedundancyTable SEQUENCE OF HpiSensorEvtCatRedundancyEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.22 |
hpiSensorEvtCatRedundancyEntryThis is the sensor resource data record which
describes all of the static data associated with a sensor. HpiSensorEvtCatRedundancyEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.22.1 |
hpiSensorEvtCatRedundancyCurrentEventsRefer to the textual convention for more details.ro SaHpiRedundancyEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.22.1.1 |
hpiSensorEvtCatRedundancySupportedEventsRefer to the textual convention for more details.ro SaHpiRedundancyEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.22.1.2 |
hpiSensorEvtCatRedundancyAssertEventsRefer to the textual convention for more details.ro SaHpiRedundancyEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.22.1.3 |
hpiSensorEvtCatRedundancyDeassertEventsRefer to the textual convention for more details.ro SaHpiRedundancyEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.22.1.4 |
hpiSensorEvtCatGenericEntryCountro Counter .1.3.6.1.4.1.231.2.60.6.4.6.10.23 |
hpiSensorEvtCatGenericTable SEQUENCE OF HpiSensorEvtCatGenericEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.24 |
hpiSensorEvtCatGenericEntryThis is the sensor resource data record which
describes all of the static data associated with a sensor. HpiSensorEvtCatGenericEntry .1.3.6.1.4.1.231.2.60.6.4.6.10.24.1 |
hpiSensorEvtCatGenericCurrentEventsRefer to the textual convention for more details.ro SaHpiGenericEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.24.1.1 |
hpiSensorEvtCatGenericSupportedEventsRefer to the textual convention for more details.ro SaHpiGenericEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.24.1.2 |
hpiSensorEvtCatGenericAssertEventsRefer to the textual convention for more details.ro SaHpiGenericEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.24.1.3 |
hpiSensorEvtCatGenericDeassertEventsRefer to the textual convention for more details.ro SaHpiGenericEvents .1.3.6.1.4.1.231.2.60.6.4.6.10.24.1.4 |
hpiRdrInventoryCountNumber of inventory data records in this system.ro Counter .1.3.6.1.4.1.231.2.60.6.4.7 |
hpiInventory OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.60.6.4.8 |
hpiIdrEntryCountThe number of inventory resource data records present on this system.ro Counter .1.3.6.1.4.1.231.2.60.6.4.8.1 |
hpiIdrTableTable defining entity inventory resource data records. SEQUENCE OF HpiIdrEntry .1.3.6.1.4.1.231.2.60.6.4.8.2 |
hpiIdrEntryThese structures are used to read and write inventory data to entity
inventory repositories within a resource.
All inventory data contained in an inventory data repository (IDR)
must be represented in the RDR repository HpiIdrEntry .1.3.6.1.4.1.231.2.60.6.4.8.2.1 |
hpiIdrPersistentTrue indicates that updates to IDR are automatically and immediately
persisted. False indicates that updates are notimmediately persisted;
but optionally may be persisted via hpiParmControl function, as
defined in implementation documentation.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.8.2.1.1 |
hpiIdrOemOEM value for the Idr record. This is manufacturere'
specific value.ro Gauge .1.3.6.1.4.1.231.2.60.6.4.8.2.1.2 |
hpiIdrUpdateCountThe count is incremented any time the IDR is changed.ro Gauge .1.3.6.1.4.1.231.2.60.6.4.8.2.1.3 |
hpiIdrIsReadOnlyDescribes if the IDR is read-only. If such, all area
headers and fields are flagged as well.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.8.2.1.4 |
hpiIdrNumAreasNumber of area containted in IDRro Gauge .1.3.6.1.4.1.231.2.60.6.4.8.2.1.5 |
hpiIdrAreaEntryCountThe number of inventory resource area data records present on this
system.ro Counter .1.3.6.1.4.1.231.2.60.6.4.8.3 |
hpiIdrAreaTableTable defining inventory data respoitory data area records. SEQUENCE OF HpiIdrAreaEntry .1.3.6.1.4.1.231.2.60.6.4.8.4 |
hpiIdrAreaEntryThese structures are used to read and write inventory data respository
data area records.
The four-tuple index value consits of:
- hpiDomainId, which is the domain of the resource
- hpiResourceId, the id value for the resource
- hpiIdrId, the id value of entity inventory
- hpiAreaId, the id value of inventory data area.
New Area's are Created when 'hpiIdrAreaType' is written with
the appropriate index values's. The 'AreadId' index is ignored.
SAI-HPI-B.01.01, pages 98...100, 104. HpiIdrAreaEntry .1.3.6.1.4.1.231.2.60.6.4.8.4.1 |
hpiIdrAreaIdSee TEXTUAL-CONVENTION 'SaHpiInstrumentId' SaHpiInstrumentId .1.3.6.1.4.1.231.2.60.6.4.8.4.1.1 |
hpiIdrAreaTypeThe type of Area.
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.rw Enumeration .1.3.6.1.4.1.231.2.60.6.4.8.4.1.2 |
hpiIdrAreaIsReadOnlyDescribes if an area is read-only. All area headers in a
read-only IDR are flagged as read-only as well.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.8.4.1.3 |
hpiIdrAreaNumFieldsNumber of Fields contained in Arearo Gauge .1.3.6.1.4.1.231.2.60.6.4.8.4.1.4 |
hpiIdrAreaRowStatusThis columnar node contains the status of the row and also
perform add and delete operations.
The status column uses three defined values:
- `active(1)', which indicates that the conceptual row is
available for use by the managed device;
- `notInService(2)', which indicates that the conceptual
row exists in the agent, but is unavailable for use by
the managed device (see NOTE below); 'notInService' has
no implication regarding the internal consistency of
the row, availability of resources, or consistency with
the current state of the managed device.
- `createAndWait(5)', which is supplied by a management
station wishing to create a new instance of a
conceptual row (but not make it available for use by
the managed device). This function is used to add
an Area to the specified Inventory Data Repository.
The row is created (and changes state to 'active' when
the hpiAreaType has been correctly set) to a
new instance of the conceptual row. The dis-allowed
hpiAreaType value is undefined(0) and unspecified(256)
- `destroy(6)', which is supplied by a management station
wishing to delete all of the instances associated with
an existing conceptual row. This function allows the
HPI MIB User to delete an Inventory Data Area, including
the Area header and all fields contained with the area,
from a particular Inventory Data Repository.
In some implementations, certain Areas are intrinsically
read-only. The hpiAreaIsReadOnly flag, indicates if the
Area is read-only. If the Inventory Data Area is not
read-only, but contains a Field that is read-only, the Area
cannot be deleted. An attempt to delete an Area that
contains a read-only Field will return an error.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.8.4.1.5 |
hpiIdrFieldEntryCountThe number of inventory data repository IdrField records.ro Counter .1.3.6.1.4.1.231.2.60.6.4.8.5 |
hpiIdrFieldTableTable defining inventory data repository IdrField records. SEQUENCE OF HpiIdrFieldEntry .1.3.6.1.4.1.231.2.60.6.4.8.6 |
hpiIdrFieldEntryThese structures are used to read and write inventory data repository
IdrField records. HpiIdrFieldEntry .1.3.6.1.4.1.231.2.60.6.4.8.6.1 |
hpiIdrFieldIdSee TEXTUAL-CONVENTION 'SaHpiInstrumentId' SaHpiInstrumentId .1.3.6.1.4.1.231.2.60.6.4.8.6.1.1 |
hpiIdrFieldTypeInventory Data IdrField type definitions.
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.rw Enumeration .1.3.6.1.4.1.231.2.60.6.4.8.6.1.2 |
hpiIdrFieldIsReadOnlyDescribes if an IdrField is read-only. All IdrField headers in a
read-only IDR are flagged as read-only as well.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.8.6.1.3 |
hpiIdrFieldDataTypeIdrField Data.
See Definition for SaHpiTextType for more details.rw SaHpiTextType .1.3.6.1.4.1.231.2.60.6.4.8.6.1.4 |
hpiIdrFieldDataLanguageIdrField Data.
See Definition for SaHpiTextLanguage for more details.rw SaHpiTextLanguage .1.3.6.1.4.1.231.2.60.6.4.8.6.1.6 |
hpiIdrFieldDataIdrField Data. The type of date is specified
by hpiResourceTagTextType and hpiResourceTagLanguage.rw SaHpiText .1.3.6.1.4.1.231.2.60.6.4.8.6.1.7 |
hpiIdrFieldDataStringIdrField Data. The type of date is specified
by hpiResourceTagTextType and hpiResourceTagLanguage.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.8.6.1.8 |
hpiIdrFieldStatusThis object provides a method to create and delete a
Data Inventory IdrField.
Supported states are:
active(1),
notInService(2),
createAndWait(5),
destroy(6)
The RowStatus textual convention is used to manage the
creation and deletion of conceptual rows, and is used as the
value of the SYNTAX clause for the status column of a
conceptual row (as described in Section 7.7.1 of [2].)
The status column has four defined values:
- `active(1)', which indicates that the conceptual row is
available for use by the managed device. For it to in such
state, the columnar objects: hpiIdrFieldType,
hpiIdrFieldTextType, hpiTextLanguage, and hpiIdrFieldText
must have valid values.
- `notInService(2)', which indicates that the conceptual
row exists in the agent, but is unavailable for use by
the managed device (see NOTE below); 'notInService' has
no implication regarding the internal consistency of
the row, availability of resources, or consistency with
the current state of the managed device.
- `createAndWait(5)', which is supplied by a management
station wishing to create a new instance of a
conceptual row. After setting this value, the management
station is responsible of providing valid values to the
columnar objects: hpiIdrFieldIsReadOnly, hpiIdrFieldType,
hpiIdrFieldTextType, hpiTextLanguage and hpiIdrFieldText.
- `destroy(6)', which is supplied by a management station
wishing to delete all of the instances associated with
an existing conceptual row.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.8.6.1.9 |
hpiRdrWatchdogsCountNumber of watchdogs data records in this system.ro Counter .1.3.6.1.4.1.231.2.60.6.4.9 |
hpiWatchdogs OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.60.6.4.10 |
hpiWatchdogEntryCountThe number of watchdogs present on this system.ro Counter .1.3.6.1.4.1.231.2.60.6.4.10.1 |
hpiWatchdogTableTable of watchdog resource data records. SEQUENCE OF HpiWatchdogEntry .1.3.6.1.4.1.231.2.60.6.4.10.2 |
hpiWatchdogEntryWhen the 'Watchdog' capability is set in a resource, a watchdog with
an identifier of SAHPI_DEFAULT_WATCHDOG_NUM is required. All
watchdogs must be represented in the RDR repository with an
hpiWatchdogRecT, including the watchdog with an identifier of
SAHPI_DEFAULT_WATCHDOG_NUM. HpiWatchdogEntry .1.3.6.1.4.1.231.2.60.6.4.10.2.1 |
hpiWatchdogLogIf you read this object, it means:
Log - indicates whether or not the Watchdog is configured to
issue an event when it next times out. TRUE=event will
be issued on timeout.
If you set this object, it means:
Log - indicates whether or not the Watchdog should issue
an event when it next times out. TRUE=event will be
issued on timeout.
Setting this object will NOT take effect on the Watchdog until the
object SaHpiWatchdogRunning is set to true(1).rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.10.2.1.1 |
hpiWatchdogRunningIf you read this object, it means:
Running - indicates whether or not the Watchdog is currently
running or stopped. TRUE=Watchdog is running.
If you set this object, it means:
Running - indicates whether or not the Watchdog should be
stopped before updating.
TRUE = Watchdog is not stopped. If it is already
stopped, it will remain stopped, but if it is
running, it will continue to run, with the
countdown timer reset to the new InitialCount.
Note that there is a race condition possible
with this setting, so it should be used with
care.
FALSE = Watchdog is stopped. After this object
is set, a subsequent read on this object
is required to start the timer.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.10.2.1.2 |
hpiWatchdogTimerUseIf you read this object, it means:
TimerUse - indicates the current use of the timer; one of five
preset uses which was included on the last
SET object request, or through some
other implementation-dependent means to start the
Watchdog timer.
If you set this object, it means:
TimerUse - indicates the current use of the timer. Will control
which hpiWatchdogTimerUseExpFlags is set if the timer expires
Setting this object will NOT take effect on the Watchdog until the
object SaHpiWatchdogRunning is set to true(1).rw SaHpiWatchdogTimerUse .1.3.6.1.4.1.231.2.60.6.4.10.2.1.3 |
hpiWatchdogTimerActionIndicates what action will be taken when the Watchdog times out.
Setting this object will NOT take effect on the Watchdog until the
object SaHpiWatchdogRunning is set to true(1).
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.rw Enumeration .1.3.6.1.4.1.231.2.60.6.4.10.2.1.4 |
hpiWatchdogPretimerInterruptPretimerInterrupt - indicates which action will be taken
'PreTimeoutInterval' seconds prior to Watchdog timer
expiration.
Setting this object will NOT take effect on the Watchdog until the
object SaHpiWatchdogRunning is set to true(1).rw SaHpiWatchdogPreTimerAction .1.3.6.1.4.1.231.2.60.6.4.10.2.1.5 |
hpiWatchdogPreTimeoutIntervalPreTimeoutInterval indicates how many milliseconds prior to timer
time out the PretimerInterrupt action will be taken. If
'PreTimeoutInterval' = 0, the PretimerInterrupt action
will occur concurrently with 'TimerAction.' HPI
implementations may not be able to support millisecond
resolution and may have a maximum value restriction.
These restrictions should be documented by the
provider of the HPI interface.
Setting this object will NOT take effect on the Watchdog until the
object SaHpiWatchdogRunning is set to true(1).rw Gauge .1.3.6.1.4.1.231.2.60.6.4.10.2.1.6 |
hpiWatchdogTimerUseExpFlagsSet of values seperated by a delimiter.
For each value set, the corresponding Timer Use Expiration Flag will
be CLEARED. Generally, a program should only clear the Timer Use
Expiration Flag corresponding to its own TimerUse, so that other
software, which may have used the timer for another purpose in the
past can still read its TimerUseExpFlag to determine whether or not
the timer expired during that use.
The values are:
EXP_BIOS_FRB2
EXP_BIOS_POST
EXP_OS_LOAD
EXP_SMS_OS
EXP_OEM
Setting this object will NOT take effect on the Watchdog until the
object SaHpiWatchdogRunning is set to true(1).rw OCTET STRING .1.3.6.1.4.1.231.2.60.6.4.10.2.1.7 |
hpiWatchdogTimerInitialCountInitialCount - The time, in milliseconds,
before the timer will time
out after a SaHpiWatchdogTimerReset() function call is
made, or some other implementation-dependent strobe is
sent to the Watchdog. HPI implementations may not be
able to support millisecond resolution and may have a
maximum value restriction. These restrictions should
be documented by the provider of the HPI interface.
Setting this object will NOT take effect on the Watchdog until the
object SaHpiWatchdogRunning is set to true(1).rw Gauge .1.3.6.1.4.1.231.2.60.6.4.10.2.1.8 |
hpiWatchdogTimerPresentCountPresentCount - The remaining time in milliseconds before
the timer will time out unless a SaHpiWatchdogTimerReset()
function call is made, or some other implementation-
dependent strobe is sent to the Watchdog.
HPI implementations may not be able to support
millisecond resolution on watchdog timers, but will
return the number of clock ticks remaining times the
number of milliseconds between each tick.
Setting this object will NOT take effect on the Watchdog until the
object SaHpiWatchdogRunning is set to true(1).rw Gauge .1.3.6.1.4.1.231.2.60.6.4.10.2.1.9 |
hpiWatchdogTimerResetThis object provides a method to start or restart
the watchdog timer from the initial countdown value.
Setting this to true(1) will 'strobe' the counter and reset to
the initial countdown value as specified in
hpiWatchdogTimerInitialCount.
Setting this object will NOT take effect on the Watchdog until the
object SaHpiWatchdogRunning is set to true(1).rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.10.2.1.10 |
hpiWatchdogOemReserved for OEM usero Gauge .1.3.6.1.4.1.231.2.60.6.4.10.2.1.11 |
hpiRdrAnnunciatorsCountNumber of annunciators data records in this system.ro Counter .1.3.6.1.4.1.231.2.60.6.4.11 |
hpiAnnunciators OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.60.6.4.12 |
hpiAnnunciatorEntryCountThe number of annunciators present on this system.ro Counter .1.3.6.1.4.1.231.2.60.6.4.12.1 |
hpiAnnunciatorTableTable of Annunciator resource data records. SEQUENCE OF HpiAnnunciatorEntry .1.3.6.1.4.1.231.2.60.6.4.12.2 |
hpiAnnunciatorEntryThe Annunciator table is used to control the set of annunciators
associated with a resource.
An Annunciator management instrument holds a set of individual
announcements. The function of the Annunciator is to communicate
the contents of its current set via whatever platform-specific
mechanism is associated with that particular Annunciator management
instrument. For example, if announcements are to be communicated
via lighting a set of LEDs on a front-panel display, the Annunciator
management instrument may analyze its current set of announcements
and turn on a single LED reflecting the most severe condition found,
or turn on a 'System Ok' LED if there are currently no items in the
set. A different Annunciator may continuously scroll each
announcement in its set on a text display, as well as turning
on LEDs and setting dry-contact relays to reflect the severity of
conditions present. A third Annunciator may announce items in its
set by sending messages to a proprietary management system, or by
sending emails or pages to a system technician.
The Annunciator provides a common interface to these varied
mechanisms for announcing conditions, so the HPI User is not
burdened by platform-to-platform differences. However, the
current content of any annunciator management instrument is not
defined by the HPI standard in the same way that the contents of
the DAT are defined. Thus, the HPI implementation and HPI Users
can exert more control over what conditions should be announced.
Further, a platform can contain multiple Annunciator management
instruments, each reflecting a different physical announcement
device in the platform. By exposing each separately, HPI Users
and the HPI implementation can control which conditions are handled
by each announcement device.
An Annunciator management instrument may be implemented using other
HPI controls that are in 'auto' mode; for example, digital controls
to turn LEDs on and off, stream controls to sound audible alerts,
and/or text controls to display detailed information. However, A
nnunciators may also operate directly to report conditions using
mechanisms that are not themselves visible directly in the HPI
interface.
Over time, announcements are added to and deleted from an
Annunciator`s current set of announcements. This may be done
automatically by the HPI implementation to reflect platform fault
conditions, or by the HPI User via the HPI interface. When
announcements are added or deleted automatically by the HPI
implementation, it is implementation-specific which announcements
are added or removed. HpiAnnunciatorEntry .1.3.6.1.4.1.231.2.60.6.4.12.2.1 |
hpiAnnunciatorNumUnique Number identifying each annunciator.ro SaHpiInstrumentId .1.3.6.1.4.1.231.2.60.6.4.12.2.1.1 |
hpiAnnunciatorTypeThe following enumerated type defines the possible output types
which can be associated with an Annunciator Management Instrument.
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.ro Enumeration .1.3.6.1.4.1.231.2.60.6.4.12.2.1.2 |
hpiAnnunciatorModeReadOnlyif True, Mode may not be changed by HPI User.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.231.2.60.6.4.12.2.1.3 |
hpiAnnunciatorMaxConditionsmaximum number of conditions that can be held in current
set. 0 means no fixed limit.ro Gauge .1.3.6.1.4.1.231.2.60.6.4.12.2.1.4 |
hpiAnnunciatorModeThe Annunciator management instrument has a current mode that
indicates whether announcements are added and removed automatically
by the HPI implementation, by the HPI User, or both. The mode may
be set to one of three values, with the following meanings:
auto(1) - the HPI implementation automatically adds and deletes
announcements; the HPI User is not permitted to add or delete
announcements.
user(2) - the HPI User may add and delete announcements; the HPI
implementation will not automatically add or delete announcements.
shared(3) - the HPI implementation automatically adds and deletes
announcements and the HPI User may also add and delete announcements.
The initial mode of each Annunciator is implementation-specific.
The HPI User may change the mode of Annunciators with the
hpiAnnunciatorMode object. However, the mode may be configured
to be Read-only, in which case the HPI User will not be able to
change the mode.
When the mode is user(2) or shared(3), HPI Users may add or delete
any types of announcements in the Annunciator's current set - not
just HPI User announcements. This is allowed so that the HPI User
can exert complete control over what conditions are being announced,
if that is required. Note that this is less restrictive than the
similar operations on the DAT. To distinguish between announcements
added to an Annunciator automatically and those added by an HPI User,
an hpiAddedByUser IdrField in the announcement indicates the source
of the announcement in the set.
Note: Enumerated values are increased by one value compared to
SAI-HPI-B spec.rw Enumeration .1.3.6.1.4.1.231.2.60.6.4.12.2.1.5 |
hpiAnnunciatorOemmaximum number of conditions that can be held in current
set. 0 means no fixed limit. if True, Mode may not be
changed by HPI User.ro Gauge .1.3.6.1.4.1.231.2.60.6.4.12.2.1.6 |
hpiAnnunciatorRDRForward pointer to the RDR OID.ro RowPointer .1.3.6.1.4.1.231.2.60.6.4.12.2.1.7 |
hpiNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.60.6.5 |
hpiSvTraps OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.60.6.5.10 |
hpiSvResourceUndefinedResource (RPT) change event notifications. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.1000 |
hpiSvResourceCriticalResource (RPT) change event notifications. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.1001 |
hpiSvResourceMajorResource (RPT) change event notifications. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.1002 |
hpiSvResourceMinorResource (RPT) change event notifications. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.1003 |
hpiSvResourceInformationalResource (RPT) change event notifications. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.1004 |
hpiSvResourceOkResource (RPT) change event notifications. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.1005 |
hpiSvResourceDebugResource (RPT) change event notifications. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.1241 |
hpiSvDomainUndefinedDomain events are used to announce the addition of domain
references and the removal of domain references to the DRT. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.2000 |
hpiSvDomainCriticalDomain events are used to announce the addition of domain
references and the removal of domain references to the DRT. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.2001 |
hpiSvDomainMajorDomain events are used to announce the addition of domain
references and the removal of domain references to the DRT. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.2002 |
hpiSvDomainMinorDomain events are used to announce the addition of domain
references and the removal of domain references to the DRT. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.2003 |
hpiSvDomainInformationalDomain events are used to announce the addition of domain
references and the removal of domain references to the DRT. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.2004 |
hpiSvDomainOkDomain events are used to announce the addition of domain
references and the removal of domain references to the DRT. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.2005 |
hpiSvDomainDebugDomain events are used to announce the addition of domain
references and the removal of domain references to the DRT. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.2241 |
hpiSvSensorUndefinedSensor event notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.3000 |
hpiSvSensorCriticalSensor event notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.3001 |
hpiSvSensorMajorSensor event notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.3002 |
hpiSvSensorMinorSensor event notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.3003 |
hpiSvSensorInformationalSensor event notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.3004 |
hpiSvSensorOkSensor event notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.3005 |
hpiSvSensorDebugSensor event notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.3241 |
hpiSvSensorEnableChangeUndefinedSensor event notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.4000 |
hpiSvSensorEnableChangeCriticalSensor event notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.4001 |
hpiSvSensorEnableChangeMajorSensor event notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.4002 |
hpiSvSensorEnableChangeMinorSensor event notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.4003 |
hpiSvSensorEnableChangeInformationalSensor event notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.4004 |
hpiSvSensorEnableChangeOkSensor event notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.4005 |
hpiSvSensorEnableChangeDebugSensor event notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.4241 |
hpiSvHotSwapUndefinedHot swap notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.5000 |
hpiSvHotSwapCriticalHot swap notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.5001 |
hpiSvHotSwapMajorHot swap notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.5002 |
hpiSvHotSwapMinorHot swap notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.5003 |
hpiSvHotSwapInformationalHot swap notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.5004 |
hpiSvHotSwapOkHot swap notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.5005 |
hpiSvHotSwapDebugHot swap notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.5241 |
hpiSvWatchdogUndefinedWatchdog notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.6000 |
hpiSvWatchdogCriticalWatchdog notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.6001 |
hpiSvWatchdogMajorWatchdog notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.6002 |
hpiSvWatchdogMinorWatchdog notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.6003 |
hpiSvWatchdogInformationalWatchdog notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.6004 |
hpiSvWatchdogOkWatchdog notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.6005 |
hpiSvWatchdogDebugWatchdog notification. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.6241 |
hpiSvSoftwareUndefinedAudit events report a discrepancy in the audit process. Audits are
typically performed by HA software to detect problems. Audits may
look for such things as corrupted data stores, inconsistent RPT
information, or improperly managed queues. Startup events report a
failure to start-up properly, or inconsistencies in persisted data. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.7000 |
hpiSvSoftwareCriticalAudit events report a discrepancy in the audit process. Audits are
typically performed by HA software to detect problems. Audits may
look for such things as corrupted data stores, inconsistent RPT
information, or improperly managed queues. Startup events report a
failure to start-up properly, or inconsistencies in persisted data. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.7001 |
hpiSvSoftwareMajorAudit events report a discrepancy in the audit process. Audits are
typically performed by HA software to detect problems. Audits may
look for such things as corrupted data stores, inconsistent RPT
information, or improperly managed queues. Startup events report a
failure to start-up properly, or inconsistencies in persisted data. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.7002 |
hpiSvSoftwareMinorAudit events report a discrepancy in the audit process. Audits are
typically performed by HA software to detect problems. Audits may
look for such things as corrupted data stores, inconsistent RPT
information, or improperly managed queues. Startup events report a
failure to start-up properly, or inconsistencies in persisted data. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.7003 |
hpiSvSoftwareInformationalAudit events report a discrepancy in the audit process. Audits are
typically performed by HA software to detect problems. Audits may
look for such things as corrupted data stores, inconsistent RPT
information, or improperly managed queues. Startup events report a
failure to start-up properly, or inconsistencies in persisted data. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.7004 |
hpiSvSoftwareOkAudit events report a discrepancy in the audit process. Audits are
typically performed by HA software to detect problems. Audits may
look for such things as corrupted data stores, inconsistent RPT
information, or improperly managed queues. Startup events report a
failure to start-up properly, or inconsistencies in persisted data. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.7005 |
hpiSvSoftwareDebugAudit events report a discrepancy in the audit process. Audits are
typically performed by HA software to detect problems. Audits may
look for such things as corrupted data stores, inconsistent RPT
information, or improperly managed queues. Startup events report a
failure to start-up properly, or inconsistencies in persisted data. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.7241 |
hpiSvOemUndefinedOEM event notifications. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.8000 |
hpiSvOemCriticalOEM event notifications. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.8001 |
hpiSvOemMajorOEM event notifications. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.8002 |
hpiSvOemMinorOEM event notifications. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.8003 |
hpiSvOemInformationalOEM event notifications. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.8004 |
hpiSvOemOkOEM event notifications. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.8005 |
hpiSvOemDebugOEM event notifications. TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.8241 |
hpiSvUserUndefinedUser events may be used for storing custom events created by an HPI
User when injecting events into the Event Log using
hpiEventLogEntryAdd(). TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.9000 |
hpiSvUserCriticalUser events may be used for storing custom events created by an HPI
User when injecting events into the Event Log using
hpiEventLogEntryAdd(). TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.9001 |
hpiSvUserMajorUser events may be used for storing custom events created by an HPI
User when injecting events into the Event Log using
hpiEventLogEntryAdd(). TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.9002 |
hpiSvUserMinorUser events may be used for storing custom events created by an HPI
User when injecting events into the Event Log using
hpiEventLogEntryAdd(). TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.9003 |
hpiSvUserInformationalUser events may be used for storing custom events created by an HPI
User when injecting events into the Event Log using
hpiEventLogEntryAdd(). TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.9004 |
hpiSvUserOkUser events may be used for storing custom events created by an HPI
User when injecting events into the Event Log using
hpiEventLogEntryAdd(). TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.9005 |
hpiSvUserDebugUser events may be used for storing custom events created by an HPI
User when injecting events into the Event Log using
hpiEventLogEntryAdd(). TRAP-TYPE .1.3.6.1.4.1.231.2.60.6.5.10.0.9241 |