-

-

-

-

-

-

Scanning ATEN-IPMI-MIB::sensorTable with filter: not connected FAN sensors (Value = 0)

Filter:

- {#SNMPVALUE} MATCHESREGEX [1-9]+

- {#SENSORDESCR} MATCHES_REGEX FAN.*

Scanning ATEN-IPMI-MIB::sensorTable with filter: not connected temp sensors (Value = 0)

Filter:

- {#SNMPVALUE} MATCHESREGEX [1-9]+

- {#SENSORDESCR} MATCHES_REGEX .*Temp.*

MIB: ATEN-IPMI-MIB

A textual string containing information about the interface.

This string should include the name of the manufacturer, the product name and the version of the interface hardware/software.

The item is used to collect all SNMP traps unmatched by other snmptrap items

MIB: SNMPv2-MIB

The physical location of this node (e.g., `telephone closet, 3rd floor'). If the location is unknown, the value is the zero-length string.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 12h

MIB: SNMPv2-MIB

The textual identification of the contact person for this managed node, together with information on how to contact this person. If no contact information is known, the value is the zero-length string.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 12h

MIB: SNMPv2-MIB

The vendor's authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determiningwhat kind of box' is being managed. For example, if vendorFlintstones, Inc.' was assigned the subtree1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 12h

MIB: SNMPv2-MIB

An administratively-assigned name for this managed node.By convention, this is the node's fully-qualified domain name. If the name is unknown, the value is the zero-length string.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 12h

MIB: SNMPv2-MIB

A textual description of the entity. This value should

include the full name and version identification of the system's hardware type, software operating-system, and

networking software.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 12h

MIB: SNMPv2-MIB

The time (in hundredths of a second) since the network management portion of the system was last re-initialized.

Preprocessing:

- MULTIPLIER: 0.01

MIB: HOST-RESOURCES-MIB

The amount of time since this host was last initialized. Note that this is different from sysUpTime in the SNMPv2-MIB [RFC1907] because sysUpTime is the uptime of the network management portion of the system.

Preprocessing:

- CHECKNOTSUPPORTED

⛔️ON_FAIL: CUSTOM_VALUE -> 0

- MULTIPLIER: 0.01

Availability of SNMP checks on the host. The value of this item corresponds to availability icons in the host list.

Possible value:

0 - not available

1 - available

2 - unknown

-

-

-

MIB: ATEN-IPMI-MIB

A textual string containing information about the interface.

This string should include the name of the manufacturer, the product name and the version of the interface hardware/software.

System name has changed. Ack to close.

Manual close: YES

Uptime is less than 10 minutes.

Manual close: YES

Depends on:

- No SNMP data collection

SNMP is not available for polling. Please check device connectivity and SNMP settings.

Depends on:

- Unavailable by ICMP ping

Last three attempts returned timeout. Please check device connectivity.

-

Depends on:

- Unavailable by ICMP ping

-

Depends on:

- High ICMP ping loss

- Unavailable by ICMP ping

This trigger uses temperature sensor values as well as temperature sensor status if available

Recovery expression:

Depends on:

- {#SENSOR_DESCR}: Temperature is above critical threshold

This trigger uses temperature sensor values as well as temperature sensor status if available

Recovery expression:

-

Recovery expression:

-

-

-

-

-

-

-

-

-

-

-

-

Depends on:

- Power

-

Depends on:

- Power

- System Fan 2 Critical [{ITEM.VALUE}]

-

Depends on:

- Power

-

Depends on:

- Power

- System Fan 3 Critical [{ITEM.VALUE}]

-

Depends on:

- Power

-

Depends on:

- Baseboard Temp Critical [{ITEM.VALUE}]

- Power

-

Depends on:

- Power

-

Depends on:

- Front Panel Temp Critical [{ITEM.VALUE}]

- Power

-

Depends on:

- Power

-

Depends on:

- BB +1.05V PCH Critical [{ITEM.VALUE}]

- Power

-

Depends on:

- Power

-

Depends on:

- BB +1.1V P1 Vccp Critical [{ITEM.VALUE}]

- Power

-

Depends on:

- Power

-

Depends on:

- BB +1.5V P1 DDR3 Critical [{ITEM.VALUE}]

- Power

-

Depends on:

- Power

-

Depends on:

- BB +3.3V Critical [{ITEM.VALUE}]

- Power

-

-

Depends on:

- BB +3.3V STBY Critical [{ITEM.VALUE}]

-

Depends on:

- Power

-

Depends on:

- BB +5.0V Critical [{ITEM.VALUE}]

- Power

-

-

-

-

-

-

-

-

-

-

-

Depends on:

- BB Ambient Temp Critical [{ITEM.VALUE}]

-

Depends on:

- Power

-

Depends on:

- BB +1.8V SM Critical [{ITEM.VALUE}]

- Power

-

Depends on:

- Power

-

Depends on:

- BB +3.3V Critical [{ITEM.VALUE}]

- Power

-

-

Depends on:

- BB +3.3V STBY Critical [{ITEM.VALUE}]

-

Depends on:

- Power

-

Depends on:

- BB +5.0V Critical [{ITEM.VALUE}]

- Power

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

IMM-MIB::fanDescr

-

IMM-MIB::powerFruName

Scanning IMM-MIB::tempTable

Filter:

- {#SNMPVALUE} MATCHESREGEX `(DIMM

Scanning IMM-MIB::tempTable with Ambient filter

Filter:

- {#SNMPVALUE} MATCHESREGEX Ambient.*

Scanning IMM-MIB::tempTable with CPU filter

Filter:

- {#SNMPVALUE} MATCHESREGEX CPU [0-9]* Temp

MIB: IMM-MIB

A description of the fan component status.

MIB: IMM-MIB

Fan speed expressed in percent(%) of maximum RPM.

An octet string expressed as 'ddd% of maximum' where:d is a decimal digit or blank space for a leading zero.

If the fan is determined not to be running or the fan speed cannot be determined, the string will indicate 'Offline'.

Preprocessing:

- REGEX: (\d{1,3}) *%( of maximum)? \1

The item is used to collect all SNMP traps unmatched by other snmptrap items

MIB: SNMPv2-MIB

The physical location of this node (e.g., `telephone closet, 3rd floor'). If the location is unknown, the value is the zero-length string.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 12h

MIB: SNMPv2-MIB

The textual identification of the contact person for this managed node, together with information on how to contact this person. If no contact information is known, the value is the zero-length string.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 12h

MIB: SNMPv2-MIB

The vendor's authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determiningwhat kind of box' is being managed. For example, if vendorFlintstones, Inc.' was assigned the subtree1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 12h

MIB: SNMPv2-MIB

An administratively-assigned name for this managed node.By convention, this is the node's fully-qualified domain name. If the name is unknown, the value is the zero-length string.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 12h

MIB: SNMPv2-MIB

A textual description of the entity. This value should

include the full name and version identification of the system's hardware type, software operating-system, and

networking software.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 12h

MIB: IMM-MIB

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 1d

MIB: IMM-MIB

Machine serial number VPD information

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 1d

MIB: IMM-MIB

MIB: IMM-MIB

disk module FRU name.

MIB: IMM-MIB

A description of the power module status.

MIB: IMM-MIB

Indicates status of system health for the system in which the IMM resides. Value of 'nonRecoverable' indicates a severe error has occurred and the system may not be functioning. A value of 'critical' indicates that a error has occurred but the system is currently functioning properly. A value of 'nonCritical' indicates that a condition has occurred that may change the state of the system in the future but currently the system is working properly. A value of 'normal' indicates that the system is operating normally.

MIB: SNMPv2-MIB

The time (in hundredths of a second) since the network management portion of the system was last re-initialized.

Preprocessing:

- MULTIPLIER: 0.01

MIB: HOST-RESOURCES-MIB

The amount of time since this host was last initialized. Note that this is different from sysUpTime in the SNMPv2-MIB [RFC1907] because sysUpTime is the uptime of the network management portion of the system.

Preprocessing:

- CHECKNOTSUPPORTED

⛔️ON_FAIL: CUSTOM_VALUE -> 0

- MULTIPLIER: 0.01

Availability of SNMP checks on the host. The value of this item corresponds to availability icons in the host list.

Possible value:

0 - not available

1 - available

2 - unknown

-

-

-

MIB: IMM-MIB

Temperature readings of testpoint: {#SNMPVALUE}

MIB: IMM-MIB

Temperature readings of testpoint: Ambient

MIB: IMM-MIB

Temperature readings of testpoint: CPU

Please check the fan unit

System name has changed. Ack to close.

Manual close: YES

Device serial number has changed. Ack to close

Manual close: YES

Please check physical disk for warnings or errors

Please check the power supply unit for errors

Please check the device for faults

Please check the device for errors

Depends on:

- System is in unrecoverable state!

Please check the device for warnings

Depends on:

- System is in unrecoverable state!

- System status is in critical state

Uptime is less than 10 minutes.

Manual close: YES

Depends on:

- No SNMP data collection

SNMP is not available for polling. Please check device connectivity and SNMP settings.

Depends on:

- Unavailable by ICMP ping

Last three attempts returned timeout. Please check device connectivity.

-

Depends on:

- Unavailable by ICMP ping

-

Depends on:

- High ICMP ping loss

- Unavailable by ICMP ping

This trigger uses temperature sensor values as well as temperature sensor status if available

Recovery expression:

Depends on:

- {#SNMPVALUE}: Temperature is above critical threshold

This trigger uses temperature sensor values as well as temperature sensor status if available

Recovery expression:

-

Recovery expression:

This trigger uses temperature sensor values as well as temperature sensor status if available

Recovery expression:

Depends on:

- Ambient: Temperature is above critical threshold

This trigger uses temperature sensor values as well as temperature sensor status if available

Recovery expression:

-

Recovery expression:

This trigger uses temperature sensor values as well as temperature sensor status if available

Recovery expression:

Depends on:

- CPU: Temperature is above critical threshold

This trigger uses temperature sensor values as well as temperature sensor status if available

Recovery expression:

-

Recovery expression:

Specify password for API.

The API port.

The API scheme (http/https).

Specify user name for API.

Response timeout for API.

A list of the appliance bays in the enclosure.

Preprocessing:

- JSONPATH: $.members.[0].applianceBays

- DISCARDUNCHANGEDHEARTBEAT: 6h

SDX cross fabric module connects to all computing devices installed in the system enclosure and brings in the capability of hard partitioning. Crossbar details are relevant only for enclosures with type "SDX".

Preprocessing:

- JSONPATH: $.members.[0].crossBars

- DISCARDUNCHANGEDHEARTBEAT: 6h

A list of the datacenters.

Preprocessing:

- JSONPATH: $.members

- DISCARDUNCHANGEDHEARTBEAT: 6h

A list of device bays in the enclosure.

Preprocessing:

- JSONPATH: $.members.[0].deviceBays

- DISCARDUNCHANGEDHEARTBEAT: 6h

A list of enclosures resources.

Preprocessing:

- JSONPATH: $.members

- DISCARDUNCHANGEDHEARTBEAT: 6h

A list of the ethernet networks.

Preprocessing:

- JSONPATH: $.members

- DISCARDUNCHANGEDHEARTBEAT: 6h

A list of the fabrics.

Preprocessing:

- JSONPATH: $.members

- DISCARDUNCHANGEDHEARTBEAT: 6h

A list of the fan bays in the enclosure.

Preprocessing:

- JSONPATH: $.members.[0].fanBays

- DISCARDUNCHANGEDHEARTBEAT: 6h

A list of the FC networks.

Preprocessing:

- JSONPATH: $.members

- DISCARDUNCHANGEDHEARTBEAT: 6h

A list of the hypervisor managers.

Preprocessing:

- JSONPATH: $.members

- DISCARDUNCHANGEDHEARTBEAT: 6h

Interconnects are centrally managed by their containing logical interconnect. The interconnect provides a physical view of a detailed downlink and uplink port state and configuration, including the current link state, speed, port role (uplink, downlink, or stacking), current pluggable media, power state, and immediate connected neighbor.

Preprocessing:

- JSONPATH: $.members

- DISCARDUNCHANGEDHEARTBEAT: 6h

A list of the logical enclosures.

- DISCARDUNCHANGED_HEARTBEAT: 6h

A list of the Synergy Frame Link Module bays.

Preprocessing:

- JSONPATH: $.members.[0].managerBays

- DISCARDUNCHANGEDHEARTBEAT: 6h

Electrically isolated hardware partition (nPar). Partition details are relevant only for enclosures with type "SDX".

Preprocessing:

- JSONPATH: $.members.[0].partitions

- DISCARDUNCHANGEDHEARTBEAT: 6h

List of power supply bays in the enclosure.

Preprocessing:

- JSONPATH: $.members.[0].powerSupplyBays

- DISCARDUNCHANGEDHEARTBEAT: 6h

A list of the racks.

Preprocessing:

- JSONPATH: $.members

- DISCARDUNCHANGEDHEARTBEAT: 6h

The server hardware resource is a representation of a physical server.

- DISCARDUNCHANGED_HEARTBEAT: 6h

A list of the storage pools.

- DISCARDUNCHANGED_HEARTBEAT: 6h

A list of the storage systems.

- DISCARDUNCHANGED_HEARTBEAT: 6h

A list of the storage volumes.

- DISCARDUNCHANGED_HEARTBEAT: 6h

A list of the uplink sets.

- DISCARDUNCHANGED_HEARTBEAT: 6h

The JSON with the result from requests to API.

Expression:

A list of errors from API requests.

Preprocessing:

- JSONPATH: $.errors

- DISCARDUNCHANGEDHEARTBEAT: 1h

A list of enclosures.

Preprocessing:

- JSONPATH: $.enclosures

⛔️ON_FAIL: DISCARD_VALUE ->

Data of the datacenters.

Preprocessing:

- JSONPATH: $.datacenters

⛔️ON_FAIL: DISCARD_VALUE ->

Data of the ethernet networks.

⛔️ONFAIL: DISCARD_VALUE ->

Data of the fabrics.

Preprocessing:

- JSONPATH: $.fabrics

⛔️ON_FAIL: DISCARD_VALUE ->

Data of the FC networks.

⛔️ONFAIL: DISCARD_VALUE ->

Data of the hypervisor managers.

⛔️ONFAIL: DISCARD_VALUE ->

Data of the interconnects.

Preprocessing:

- JSONPATH: $.interconnects

⛔️ON_FAIL: DISCARD_VALUE ->

Data of the logical enclosures.

⛔️ONFAIL: DISCARD_VALUE ->

Data of the racks.

Preprocessing:

- JSONPATH: $.racks

⛔️ON_FAIL: DISCARD_VALUE ->

Data of the server hardware.

⛔️ONFAIL: DISCARD_VALUE ->

Data of the storage pools.

⛔️ONFAIL: DISCARD_VALUE ->

Data of the storage systems.

⛔️ONFAIL: DISCARD_VALUE ->

Data of the storage volumes.

⛔️ONFAIL: DISCARD_VALUE ->

Data of the uplink sets.

⛔️ONFAIL: DISCARD_VALUE ->

Checks if the service is running and accepting the TCP connections.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 10m

Data of the appliance bay [{#ENCLOSURENAME}:{#BAYNUMBER}].

Preprocessing:

- JSONPATH: $.members[?(@.name == "{#ENCLOSURE_NAME}")].applianceBays[?(@.bayNumber == "{#BAY_NUMBER}")].first()

The model name of the appliance.

Preprocessing:

- JSONPATH: $.model

- DISCARDUNCHANGEDHEARTBEAT: 1d

The part number of the appliance.

- DISCARDUNCHANGED_HEARTBEAT: 1d

Yes, if the appliance is powered on; false, otherwise.

- BOOLTODECIMAL

- DISCARDUNCHANGED_HEARTBEAT: 1h

The power state of the appliance bay.

EFuse - the power state of the bay - it has been EFused.

Reset - the power state of the bay - it has been reset.

SoftReset - the power state of the bay - it has been softly reset.

Unknown - the power state of the bay is unknown.

Preprocessing:

- JSONPATH: $.bayPowerState

- STRREPLACE: EFuse 0

- STRREPLACE: SoftReset 1

- STRREPLACE: Reset 2

- STRREPLACE: Unknown 3

- INRANGE: 0 3

⛔️ONFAIL: CUSTOM_VALUE -> 3

Indicates whether an appliance is present in the bay:

Absent - the device slot is empty;

PresenceNoOp - the device slot is uninitialized;

PresenceUnknown - the device presence is unknown;

Present - the device slot has a device in it;

Subsumed - the device slot is configured to be part of another device slot. Not applicable for the fan or power supply bays.

Preprocessing:

- JSONPATH: $.devicePresence

- STRREPLACE: Absent 0

- STRREPLACE: PresenceNoOp 1

- STRREPLACE: PresenceUnknown 2

- STRREPLACE: Present 3

- STRREPLACE: Subsumed 4

- INRANGE: 0 4

⛔️ONFAIL: CUSTOM_VALUE -> 2

- DISCARDUNCHANGED_HEARTBEAT: 1h

The serial number of the appliance.

- DISCARDUNCHANGED_HEARTBEAT: 1d

The spare part number of the appliance.

Preprocessing:

- JSONPATH: $.sparePartNumber

- DISCARDUNCHANGEDHEARTBEAT: 1d

The hardware status of the appliance:

Critical - requires immediate attention;

Disabled - the resource is currently not operational;

OK - indicates normal/informational behavior;

Unknown - the health status is not yet known or cannot be determined;

Warning - requires attention soon.

Preprocessing:

- JSONPATH: $.status

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ON_FAIL: CUSTOM_VALUE -> 3

Crossbar [{#ENCLOSURENAME}:{#BAYNUMBER}] data

Preprocessing:

- JSONPATH: $.members[?(@.name == "{#ENCLOSURE_NAME}")].crossbars[?(@.bayNumber == "{#BAY_NUMBER}")].first()

The hardware version.

- DISCARDUNCHANGED_HEARTBEAT: 1d

The part number provided by the manufacturer.

- DISCARDUNCHANGED_HEARTBEAT: 1d

The presence in a bay:

Absent - the device slot is empty;

PresenceNoOp - the device slot is uninitialized;

PresenceUnknown - the device presence is unknown;

Present - the device slot has a device in it;

Subsumed - the device slot is configured to be part of another device slot. Not applicable for the fan or power supply bays.

Preprocessing:

- JSONPATH: $.presence

- STRREPLACE: Absent 0

- STRREPLACE: PresenceNoOp 1

- STRREPLACE: PresenceUnknown 2

- STRREPLACE: Present 3

- STRREPLACE: Subsumed 4

- INRANGE: 0 4

⛔️ONFAIL: CUSTOM_VALUE -> 2

- DISCARDUNCHANGED_HEARTBEAT: 1h

A serial number.

- DISCARDUNCHANGED_HEARTBEAT: 1d

The overall health status of the crossbar:

Critical - requires immediate attention;

Disabled - the resource is currently not operational;

OK - indicates normal/informational behavior;

Unknown - the health status is not yet known or cannot be determined;

Warning - requires attention soon.

Preprocessing:

- JSONPATH: $.status

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ON_FAIL: CUSTOM_VALUE -> 3

Data of the datacenter [{#NAME}].

Preprocessing:

- JSONPATH: $.members[?(@.name == "{#NAME}")].first()

The current state of the resource. The valid values include Adding, AddError, Configured, CredentialError, Refreshing, RefreshError, Removing, RemoveError, and Unmanaged.

Preprocessing:

- JSONPATH: $.state

- STRREPLACE: Adding 0

- STRREPLACE: AddError 1

- STRREPLACE: Configured 2

- STRREPLACE: CredentialError 3

- STRREPLACE: Refreshing 4

- STRREPLACE: RefreshError 5

- STRREPLACE: Removing 6

- STRREPLACE: RemoveError 7

- STRREPLACE: Unmanaged 8

- INRANGE: 0 8

⛔️ON_FAIL: CUSTOM_VALUE -> 9

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that a resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing:

- JSONPATH: $.status

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ON_FAIL: CUSTOM_VALUE -> 3

Data of the device [{#ENCLOSURENAME}:{#BAYNUMBER}].

Preprocessing:

- JSONPATH: $.members[?(@.name == "{#ENCLOSURE_NAME}")].deviceBays[?(@.bayNumber == "{#BAY_NUMBER}")].first()

The model name of an unsupported device occupying the bay if available.

Preprocessing:

- JSONPATH: $.model

- DISCARDUNCHANGEDHEARTBEAT: 1d

The power allocated for the enclosed blade.

- DISCARDUNCHANGED_HEARTBEAT: 1h

Indicates whether a device is present:

Absent - the device slot is empty;

PresenceNoOp - the device slot is uninitialized;

PresenceUnknown - the device presence is unknown;

Present - the device slot has a device in it;

Subsumed - the device slot is configured to be part of another device slot. Not applicable for the fan or power supply bays.

Preprocessing:

- JSONPATH: $.devicePresence

- STRREPLACE: Absent 0

- STRREPLACE: PresenceNoOp 1

- STRREPLACE: PresenceUnknown 2

- STRREPLACE: Present 3

- STRREPLACE: Subsumed 4

- INRANGE: 0 4

⛔️ONFAIL: CUSTOM_VALUE -> 2

- DISCARDUNCHANGED_HEARTBEAT: 1h

If available, the serial number of any device occupying the bay.

⛔️ONFAIL: DISCARD_VALUE ->

- DISCARDUNCHANGEDHEARTBEAT: 1d

Data of the enclosure [{#NAME}].

Preprocessing:

- JSONPATH: $.members[?(@.name == "{#NAME}")].first()

The number of the appliance bays in the enclosure.

Preprocessing:

- JSONPATH: $.applianceBayCount

- DISCARDUNCHANGEDHEARTBEAT: 1h

The number of the device bays in the enclosure.

Preprocessing:

- JSONPATH: $.deviceBayCount

- DISCARDUNCHANGEDHEARTBEAT: 1h

The amount of power allocated for the blades in the enclosure.

Preprocessing:

- JSONPATH: $.deviceBayWatts

The number of the fan bays in the enclosure.

Preprocessing:

- JSONPATH: $.fanBayCount

- DISCARDUNCHANGEDHEARTBEAT: 1h

The name of the current firmware baseline.

Preprocessing:

- JSONPATH: $.fwBaselineName

- DISCARDUNCHANGEDHEARTBEAT: 1d

The number of the interconnect bays in the enclosure.

Preprocessing:

- JSONPATH: $.interconnectBayCount

- DISCARDUNCHANGEDHEARTBEAT: 1h

The amount of power allocated for the interconnects in the enclosure.

Preprocessing:

- JSONPATH: $.interconnectBayWatts

The minimum number of the power supplies needed.

- DISCARDUNCHANGED_HEARTBEAT: 1d

The minimum number of the power supplies needed to fulfill the redundant line feed power mode.

Preprocessing:

- JSONPATH: $.minimumPowerSuppliesForRedundantPowerFeed

- DISCARDUNCHANGEDHEARTBEAT: 1d

The enclosure model name, for example, "BladeSystem c7000 Enclosure G2.

Preprocessing:

- JSONPATH: $.enclosureModel

- DISCARDUNCHANGEDHEARTBEAT: 1d

The part number of the enclosure.

- DISCARDUNCHANGED_HEARTBEAT: 1d

The amount of the power allocated for the fans and management devices of the enclosure.

Preprocessing:

- JSONPATH: $.fansAndManagementDevicesWatts

The power capacity based on power mode.

Preprocessing:

- JSONPATH: $.powerCapacityWatts

The number of the power supply bays in the enclosure.

Preprocessing:

- JSONPATH: $.powerSupplyBayCount

- DISCARDUNCHANGEDHEARTBEAT: 1h

The serial number of the enclosure.

- DISCARDUNCHANGED_HEARTBEAT: 1d

The current resource state of the enclosure:

Adding - the enclosure is being added;

Configured - the enclosure is configured and is a part of the logical enclosure. This is the usual state for an enclosure under full management;

Configuring - a transient state while the enclosure is being configured for a logical enclosure;

Interrupted - the previous operation on the enclosure did not complete. The operation should be re-attempted;

Monitored - the enclosure is being monitored. It is not a part of the logical enclosure and only hardware-control operations are available;

Pending - there are pending operations on the enclosure. Additional operations are denied;

RemoveFailed - the previous operation to remove the enclosure did not succeed. The operation should be re-attempted;

Removing - the enclosure is being removed;

Unmanaged - the enclosure has been discovered, but has not yet been added for the management or monitoring;

Unsupported - the enclosure model or version is not currently supported by HPE OneView. It cannot be configured or monitored.

Preprocessing:

- JSONPATH: $.state

- STRREPLACE: Adding 0

- STRREPLACE: Configured 1

- STRREPLACE: Configuring 2

- STRREPLACE: Interrupted 3

- STRREPLACE: Monitored 4

- STRREPLACE: Pending 5

- STRREPLACE: RemoveFailed 6

- STRREPLACE: Removing 7

- STRREPLACE: Unmanaged 8

- STRREPLACE: Unsupported 9

- INRANGE: 0 9

⛔️ONFAIL: CUSTOM_VALUE -> 10

Indicates the reason why the resource in its current state:

Missing - the enclosure is no longer connected into the frame link topology;

None - no reason is available, or none applies;

NotAdded - the enclosure has not been added;

NotOwner - the enclosure reports being managed by something other than this HPE OneView;

OperationFailed - a prior operation was interrupted;

Unowned - the enclosure reports are not being under the management;

UnsupportedFirmware - the firmware version of the enclosure is not supported by this version of HPE OneView;

UpdatingFirmware - a firmware update is in progress.

- STRREPLACE: Missing 0

- STRREPLACE: None 1

- STRREPLACE: NotAdded 2

- STRREPLACE: NotOwner 3

- STRREPLACE: OperationFailed 4

- STRREPLACE: Unowned 5

- STRREPLACE: UnsupportedFirmware 6

- STRREPLACE: UpdatingFirmware 7

- INRANGE: 0 7

⛔️ON_FAIL: CUSTOM_VALUE -> 8

The overall health status of the enclosure.

The enclosure status reflects the hardware health of the enclosure, all the bays, and the enclosure components (e.g. the enclosure mid-plane, fans, power supplies, Synergy Frame Link Modules, and Synergy Composers). It explicitly does not include the status of the other HPE OneView resources such as the blades (server hardware), the interconnects, and the drive enclosures.

Critical - requires immediate attention.

Disabled - the resource is currently not operational.

OK - indicates normal/informational behavior.

Unknown - the health status is not yet known or cannot be determined.

Warning - requires attention soon.

Preprocessing:

- JSONPATH: $.status

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ON_FAIL: CUSTOM_VALUE -> 3

The total amount of the power allocated in the enclosure.

Preprocessing:

- JSONPATH: $.powerAllocatedWatts

The amount of the unallocated power in the enclosure.

Preprocessing:

- JSONPATH: $.powerAvailableWatts

The type of the enclosure, for example, "C7000" or "SY12000" or "SDX".

Preprocessing:

- JSONPATH: $.enclosureType

- DISCARDUNCHANGEDHEARTBEAT: 6h

Data of the ethernet network [{#NAME}].

Preprocessing:

- JSONPATH: $.members[?(@.name == "{#NAME}")].first()

The current state of the resource.

Preprocessing:

- JSONPATH: $.state

- DISCARDUNCHANGEDHEARTBEAT: 1h

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing:

- JSONPATH: $.status

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ON_FAIL: CUSTOM_VALUE -> 3

Data of the fabric [{#NAME}].

Preprocessing:

- JSONPATH: $.members[?(@.name == "{#NAME}")].first()

The current state of the resource.

Preprocessing:

- JSONPATH: $.state

- DISCARDUNCHANGEDHEARTBEAT: 1h

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing:

- JSONPATH: $.status

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ON_FAIL: CUSTOM_VALUE -> 3

Data of the fan [{#ENCLOSURENAME}:{#BAYNUMBER}].

Preprocessing:

- JSONPATH: $.members[?(@.name == "{#ENCLOSURE_NAME}")].fanBays[?(@.bayNumber == "{#BAY_NUMBER}")].first()

The common descriptive model of the fan.

Preprocessing:

- JSONPATH: $.model

- DISCARDUNCHANGEDHEARTBEAT: 1d

The part number of the fan.

- DISCARDUNCHANGED_HEARTBEAT: 1d

Indicates whether a fan is present:

Absent - the device slot is empty;

PresenceNoOp - the device slot is uninitialized;

PresenceUnknown - the device presence is unknown;

Present - the device slot has a device in it;

Subsumed - the device slot is configured to be part of another device slot. Not applicable for the fan or power supply bays.

Preprocessing:

- JSONPATH: $.devicePresence

- STRREPLACE: Absent 0

- STRREPLACE: PresenceNoOp 1

- STRREPLACE: PresenceUnknown 2

- STRREPLACE: Present 3

- STRREPLACE: Subsumed 4

- INRANGE: 0 4

⛔️ONFAIL: CUSTOM_VALUE -> 2

- DISCARDUNCHANGED_HEARTBEAT: 1h

Indicates whether the enclosure configuration requires a fan to be present in the bay.

Preprocessing:

- JSONPATH: $.deviceRequired

- BOOLTODECIMAL

- DISCARDUNCHANGEDHEARTBEAT: 1h

The serial number of the fan.

- DISCARDUNCHANGED_HEARTBEAT: 1d

The spare part number to be used when ordering an additional or replacement fan of this type.

Preprocessing:

- JSONPATH: $.sparePartNumber

- DISCARDUNCHANGEDHEARTBEAT: 1d

The current state of the fan:

Degraded - a fan is degraded;

Failed - a fan has failed;

Misplaced - a fan is present, but not required in this bay, and the overall fan configuration is not compliant with the enclosure fan placement rules;

Missing - a fan is required, but is not present;

OK - a fan bay has no issues;

Unknown - the state of a fan is unknown.

Preprocessing:

- JSONPATH: $.state

⛔️ONFAIL: CUSTOM_VALUE -> 5

- STRREPLACE: Degraded 0

- STRREPLACE: Failed 1

- STRREPLACE: Misplaced 2

- STRREPLACE: Missing 3

- STRREPLACE: OK 4

- INRANGE: 0 4

⛔️ONFAIL: CUSTOM_VALUE -> 5

The overall health status of the fan:

Critical - requires immediate attention;

Disabled - the resource is currently not operational;

OK - indicates normal/informational behavior;

Unknown - the health status is not yet known or cannot be determined;

Warning - requires attention soon.

Preprocessing:

- JSONPATH: $.status

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ON_FAIL: CUSTOM_VALUE -> 3

Data of the FC network [{#NAME}].

Preprocessing:

- JSONPATH: $.members[?(@.name == "{#NAME}")].first()

The current state of the resource.

Preprocessing:

- JSONPATH: $.state

- DISCARDUNCHANGEDHEARTBEAT: 1h

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing:

- JSONPATH: $.status

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ON_FAIL: CUSTOM_VALUE -> 3

Data of the hypervisor manager [{#NAME}].

Preprocessing:

- JSONPATH: $.members[?(@.displayName == "{#NAME}")].first()

The current state of the resource. The valid values include Connected, Disconnected, Configuring and Error.

- STRREPLACE: Connected 0

- STRREPLACE: Disconnected 1

- STRREPLACE: Configuring 2

- STRREPLACE: Error 3

- INRANGE: 0 3

⛔️ON_FAIL: CUSTOM_VALUE -> 4

Indicates the reason why the resource is in its current state.

Preprocessing:

- JSONPATH: $.stateReason

- DISCARDUNCHANGEDHEARTBEAT: 1h

The current status of this resource:

Critical - requires immediate attention;

Disabled - the resource is currently not operational;

OK - indicates normal/informational behavior;

Unknown - the health status is not yet known or cannot be determined;

Warning - requires attention soon.

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ONFAIL: CUSTOM_VALUE -> 3

Data of the interconnect [{#NAME}].

Preprocessing:

- JSONPATH: $.members[?(@.name == "{#NAME}")].first()

The health status of the interconnect hardware.

Preprocessing:

- JSONPATH: $.interconnectHardwareHealth

- DISCARDUNCHANGEDHEARTBEAT: 1h

The interconnect model.

Preprocessing:

- JSONPATH: $.model

- DISCARDUNCHANGEDHEARTBEAT: 1d

The part number of the interconnect.

- DISCARDUNCHANGED_HEARTBEAT: 1d

The number of ports on the interconnect.

- DISCARDUNCHANGED_HEARTBEAT: 1h

The serial number of the interconnect.

- DISCARDUNCHANGED_HEARTBEAT: 1d

The spare part number of the interconnect.

Preprocessing:

- JSONPATH: $.sparePartNumber

- DISCARDUNCHANGEDHEARTBEAT: 1d

The current state of the resource.

Preprocessing:

- JSONPATH: $.state

- DISCARDUNCHANGEDHEARTBEAT: 1h

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing:

- JSONPATH: $.status

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ON_FAIL: CUSTOM_VALUE -> 3

Data of the logical enclosure [{#NAME}].

Preprocessing:

- JSONPATH: $.members[?(@.name == "{#NAME}")].first()

The current resource state of the logical enclosure:

Consistent - this is the expected state of the logical enclosure. The logical enclosure configuration is consistent with the enclosure group, and the configuration of the hardware resources is consistent with the logical enclosure configuration;

Creating - the logical enclosure is being created;

DeleteFailed - the prior attempt to delete the logical enclosure failed. Retry the delete operation potentially with the force option. No other logical enclosure operations are allowed in this state;

Deleting - the logical enclosure is being deleted;

Inconsistent - the configuration of the logical enclosure differs from that of the enclosure group, or the configuration of the hardware resources is inconsistent with the logical enclosure configuration. Perform an Update from group, Reapply configuration, or Update firmware action as an appropriate to bring the configuration back into consistency;

Updating - configuration changes are being applied to the hardware configuration.

- STRREPLACE: Inconsistent 0

- STRREPLACE: Creating 1

- STRREPLACE: DeleteFailed 2

- STRREPLACE: Deleting 3

- STRREPLACE: Consistent 4

- STRREPLACE: Updating 5

- INRANGE: 0 5

⛔️ON_FAIL: CUSTOM_VALUE -> 6

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ONFAIL: CUSTOM_VALUE -> 3

Data of the partition [{#ENCLOSURENAME}:{#PARTITIONID}].

Preprocessing:

- JSONPATH: $.members[?(@.name == "{#ENCLOSURE_NAME}")].partitions[?(@.partitionID == "{#PARTITION_ID}")].first()

The number of blades in the partition.

- DISCARDUNCHANGED_HEARTBEAT: 10m

Indicates the health of the partition and the health of its owned resources (blades and IO bays) as reported by the firmware. If a problem is detected with one of the resources, the health of the partition is reported as Degraded. If all the resources in the partition are operating correctly, the health of the partition is reported as OK.

NparDegrade - one or more resources in the partition are unhealthy.

NparHealthInvalid - a partition health is invalid.

NparHealthMax - a delimiter defined by the firmware.

NparOk - all the resources in the partition are healthy.

Preprocessing:

- JSONPATH: $.partitionHealth

- STRREPLACE: NparDegrade 0

- STRREPLACE: NparHealthInvalid 1

- STRREPLACE: NparHealthMax 2

- STRREPLACE: NparOk 3

- INRANGE: 0 3

⛔️ONFAIL: CUSTOM_VALUE -> 4

The total memory of the partition.

Preprocessing:

- JSONPATH: $.memoryMb

- MULTIPLIER: 1048576

- DISCARDUNCHANGEDHEARTBEAT: 1h

The number of processors in the partition.

- DISCARDUNCHANGED_HEARTBEAT: 10m

Indicates whether the partition has been booted and also indicates its current power state:

ParStatusActive - a partition is active when a 'poweron' operation is initiated on the partition and the firmware boot process is started;

ParStatusInactive - a partition is in an inactive state after it has been created or shut down;

ParStatusInvalid - a partition status is invalid;

ParStatusManualRepair - a partition under manual repair;

ParStatusMax - a delimiter defined by the OA firmware;

ParStatusUndefined - partition status is undefined;

ParStatusUnknown - a partition might report an Unknown state after an OA restart. This state is possible when the firmware is not able to identify the correct partition state due to the internal firmware errors at an OA startup. The state is persistent and can only be cleared by force powering off of the partition from the OA. A partition in this state will not accept any partition operation except parstatus and force poweroff. Any active OS instances continue to run unhindered even when the partition is in an unknown state.

Preprocessing:

- JSONPATH: $.partitionStatus

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: ParStatusActive 0

- STRREPLACE: ParStatusInactive 1

- STRREPLACE: ParStatusInvalid 2

- STRREPLACE: ParStatusManualRepair 3

- STRREPLACE: ParStatusMax 4

- STRREPLACE: ParStatusUndefined 5

- STRREPLACE: ParStatusUnknown 6

- INRANGE: 0 6

⛔️ON_FAIL: CUSTOM_VALUE -> 6

Data of the power Supply [{#ENCLOSURENAME}:{#BAYNUMBER}].

Preprocessing:

- JSONPATH: $.members[?(@.name == "{#ENCLOSURE_NAME}")].powerSupplyBays[?(@.bayNumber == "{#BAY_NUMBER}")].first()

The common descriptive model of the power supply.

- DISCARDUNCHANGED_HEARTBEAT: 1d

The output capacity of the power supply.

Preprocessing:

- JSONPATH: $.outputCapacityWatts

- DISCARDUNCHANGEDHEARTBEAT: 1h

The part number of the power supply.

Preprocessing:

- JSONPATH: $.partNumber

- DISCARDUNCHANGEDHEARTBEAT: 1d

Indicates whether a power supply is present:

Absent - the device slot is empty;

PresenceNoOp - the device slot is uninitialized;

PresenceUnknown - the device presence is unknown;

Present - the device slot has a device in it;

Subsumed - the device slot is configured to be part of another device slot. Not applicable for the fan or power supply bays.

- STRREPLACE: Absent 0

- STRREPLACE: PresenceNoOp 1

- STRREPLACE: PresenceUnknown 2

- STRREPLACE: Present 3

- STRREPLACE: Subsumed 4

- INRANGE: 0 4

⛔️ONFAIL: CUSTOM_VALUE -> 2

- DISCARDUNCHANGEDHEARTBEAT: 1h

The unique serial number of the power supply.

Preprocessing:

- JSONPATH: $.serialNumber

- DISCARDUNCHANGEDHEARTBEAT: 1d

The spare part number to be used when ordering an additional or replacement power supply of this type.

- DISCARDUNCHANGED_HEARTBEAT: 1d

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ONFAIL: CUSTOM_VALUE -> 3

Data of the rack [{#NAME}].

Preprocessing:

- JSONPATH: $.members[?(@.name == "{#NAME}")].first()

The current state of the resource. the valid values include Adding, AddError, Configured, CredentialError, Refreshing, RefreshError, Removing, RemoveError, and Unmanaged.

Preprocessing:

- JSONPATH: $.state

- STRREPLACE: Adding 0

- STRREPLACE: AddError 1

- STRREPLACE: Configured 2

- STRREPLACE: CredentialError 3

- STRREPLACE: Refreshing 4

- STRREPLACE: RefreshError 5

- STRREPLACE: Removing 6

- STRREPLACE: RemoveError 7

- STRREPLACE: Unmanaged 8

- INRANGE: 0 8

⛔️ON_FAIL: CUSTOM_VALUE -> 9

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing:

- JSONPATH: $.status

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ON_FAIL: CUSTOM_VALUE -> 3

Data of the server [{#SERVER_NAME}:{#LOCATION}].

Preprocessing:

- JSONPATH: $.members[?(@.name == "{#LOCATION}")].first()

The maintenance flag of the Server Hardware - disruptive maintenance operations, such as firmware update, can cause many server hardware alerts to be generated in a short period of time. Example: network connectivity is lost or the server reset is detected. When this field is set, predefined alerts for this particular device are suppressed. This field is set only when firmware update is ongoing. The alerts are processed normally once firmware update operation completes. Possible values are Maintenance and Normal.

Preprocessing:

- JSONPATH: $.maintenanceState

⛔️ONFAIL: DISCARD_VALUE ->

- STRREPLACE: Maintenance 0

- STRREPLACE: Normal 1

- INRANGE: 0 1

⛔️ON_FAIL: CUSTOM_VALUE -> 2

This field is set to Firmware update when the server is put under maintenance.

⛔️ONFAIL: DISCARD_VALUE ->

- DISCARDUNCHANGEDHEARTBEAT: 1h

The amount of memory installed on this server hardware.

- DISCARDUNCHANGED_HEARTBEAT: 1h

The state of an ongoing virtual connect manager (VCM) migration:

Migrating - the enclosure is in the process of migrating from VCM;

NotApplicable - the enclosure did not require or has already completed the migration;

Unknown - the migration state is unknown.

Preprocessing:

- JSONPATH: $.migrationState

⛔️ONFAIL: DISCARD_VALUE ->

- STRREPLACE: Migrating 0

- STRREPLACE: NotApplicable 1

- STRREPLACE: Unknown 2

- INRANGE: 0 2

⛔️ONFAIL: CUSTOM_VALUE -> 2

The model string of the full server hardware.

- DISCARDUNCHANGED_HEARTBEAT: 1d

The part number for this server hardware.

Preprocessing:

- JSONPATH: $.partNumber

- DISCARDUNCHANGEDHEARTBEAT: 1d

The current power state of the server hardware. The values are Unknown, On, Off, PoweringOn, PoweringOff or Resetting.

Preprocessing:

- JSONPATH: $.powerState

- STRREPLACE: PoweringOff 0

- STRREPLACE: PoweringOn 1

- STRREPLACE: Resetting 2

- STRREPLACE: Unknown 3

- STRREPLACE: Off 4

- STRREPLACE: On 5

- INRANGE: 0 5

⛔️ONFAIL: CUSTOM_VALUE -> 3

The number of cores available per processor.

Preprocessing:

- JSONPATH: $.processorCoreCount

- DISCARDUNCHANGEDHEARTBEAT: 1h

The number of processors installed on this server hardware.

- DISCARDUNCHANGED_HEARTBEAT: 1h

The speed of the CPUs.

- DISCARDUNCHANGED_HEARTBEAT: 1h

The type of the CPU installed on this server hardware.

- DISCARDUNCHANGED_HEARTBEAT: 1d

The serial number of the server hardware.

Preprocessing:

- JSONPATH: $.serialNumber

- DISCARDUNCHANGEDHEARTBEAT: 1d

The current resource state of the server hardware. The allowable values are:

Unknown - not initialized;

Adding - a server is being added;

NoProfileApplied - a server successfully added;

Monitored - a server is being monitored;

Unmanaged - a discovered and supported server;

Removing - a server is being removed;

RemoveFailed - an unsuccessful server removal;

Removed - a server is successfully removed;

ApplyingProfile - a server is successfully removed;

ProfileApplied - a profile is successfully applied;

RemovingProfile - a profile is being removed;

ProfileError - an Unsuccessful profile is applied or removed;

Unsupported - a server model or version is not currently supported by the appliance;

UpdatingFirmware - a server firmware update is in progress.

- STRREPLACE: Unknown 0

- STRREPLACE: Adding 1

- STRREPLACE: NoProfileApplied 2

- STRREPLACE: Monitored 3

- STRREPLACE: Unmanaged 4

- STRREPLACE: Removing 5

- STRREPLACE: RemoveFailed 6

- STRREPLACE: Removed 7

- STRREPLACE: ApplyingProfile 8

- STRREPLACE: ProfileApplied 9

- STRREPLACE: RemovingProfile 10

- STRREPLACE: ProfileError 11

- STRREPLACE: Unsupported 12

- STRREPLACE: UpdatingFirmware 13

- INRANGE: 0 13

⛔️ON_FAIL: CUSTOM_VALUE -> 0

The reason for the current resource state of the server hardware. This only applies if the state is Unmanaged, otherwise it is set to NotApplicable. The allowable values are:

Unsupported - a server model or version is not currently supported by the appliance;

UpdatingFirmware - a server firmware update is in progress;

NotApplicable - when PhysicalServerState is anything besides Unmanaged;

NotOwner - no claim on the server;

Inventory - a server is added by the PDU;

Unconfigured - the discovery data is incomplete or an iLO configuration has failed;

UnsupportedFirmware - an iLO firmware version is below the minimum support level;

Interrupted - when PhysicalServerState is a result of an operation that was terminated before completing;

CommunicationError - an appliance cannot communicate with an iLO or an OA.

Preprocessing:

- JSONPATH: $.stateReason

- DISCARDUNCHANGEDHEARTBEAT: 1h

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ONFAIL: CUSTOM_VALUE -> 3

Data of the storage pool [{#NAME}].

Preprocessing:

- JSONPATH: $.members[?(@.name == "{#NAME}")].first()

The capacity allocated from the storage pool in bytes.

Preprocessing:

- JSONPATH: $.allocatedCapacity

The free capacity available from the storage pool in bytes.

Preprocessing:

- JSONPATH: $.freeCapacity

The pool capacity allocated to the snapshots in bytes.

Preprocessing:

- JSONPATH: $.deviceSpecificAttributes.allocatedCapacity.snapshotAllocatedCapacity

The current state of the resource:

AddFailed - an attempt to add the resource failed;

Adding - the resource is in the process of being added;

Configured - the resource is configured;

Connected - the appliance has connected to the resource;

Copying - the resource is in the process of being copied;

CreateFailed - an attempt to create the resource failed;

Creating - the resource is in the process of being created;

DeleteFailed - an attempt to delete the resource failed;

Deleting - the resource is in the process of being deleted;

Discovered - the resource has been discovered by the appliance, but it is not managed by the appliance;

Managed - the resource is managed by the appliance;

Normal - the resource is in a normal state;

UpdateFailed - an attempt to update the resource failed;

Updating - the resource is in the process of being updated.

Preprocessing:

- JSONPATH: $.state

- STRREPLACE: AddFailed 0

- STRREPLACE: Adding 1

- STRREPLACE: Configured 2

- STRREPLACE: Connected 3

- STRREPLACE: Copying 4

- STRREPLACE: CreateFailed 5

- STRREPLACE: Creating 6

- STRREPLACE: DeleteFailed 7

- STRREPLACE: Deleting 8

- STRREPLACE: Discovered 9

- STRREPLACE: Managed 10

- STRREPLACE: Normal 11

- STRREPLACE: UpdateFailed 12

- STRREPLACE: Updating 13

- INRANGE: 0 13

⛔️ONFAIL: CUSTOM_VALUE -> 14

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing:

- JSONPATH: $.status

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ON_FAIL: CUSTOM_VALUE -> 3

The total capacity of the storage pool in bytes.

Preprocessing:

- JSONPATH: $.totalCapacity

Data of the storage system [{#NAME}].

Preprocessing:

- JSONPATH: $.members[?(@.name == "{#NAME}")].first()

The capacity allocated in bytes.

Preprocessing:

- JSONPATH: $.allocatedCapacity

The free capacity of the storage system in bytes.

Preprocessing:

- JSONPATH: $.freeCapacity

The current state of the resource:

AddFailed - an attempt to add the resource failed;

Adding - the resource is in the process of being added;

Configured - the resource is configured;

Connected - the appliance has connected to the resource;

Copying - the resource is in the process of being copied;

CreateFailed - an attempt to create the resource failed;

Creating - the resource is in the process of being created;

DeleteFailed - an attempt to delete the resource failed;

Deleting - the resource is in the process of being deleted;

Discovered - the resource has been discovered by the appliance, but it is not managed by the appliance;

Managed - the resource is managed by the appliance;

Normal - the resource is in a normal state;

UpdateFailed - an attempt to update the resource failed;

Updating - the resource is in the process of being updated.

Preprocessing:

- JSONPATH: $.state

- STRREPLACE: AddFailed 0

- STRREPLACE: Adding 1

- STRREPLACE: Configured 2

- STRREPLACE: Connected 3

- STRREPLACE: Copying 4

- STRREPLACE: CreateFailed 5

- STRREPLACE: Creating 6

- STRREPLACE: DeleteFailed 7

- STRREPLACE: Deleting 8

- STRREPLACE: Discovered 9

- STRREPLACE: Managed 10

- STRREPLACE: Normal 11

- STRREPLACE: UpdateFailed 12

- STRREPLACE: Updating 13

- INRANGE: 0 13

⛔️ONFAIL: CUSTOM_VALUE -> 14

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing:

- JSONPATH: $.status

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ON_FAIL: CUSTOM_VALUE -> 3

The total capacity of the storage system in bytes.

Preprocessing:

- JSONPATH: $.totalCapacity

Data of the storage volume [{#NAME}].

Preprocessing:

- JSONPATH: $.members[?(@.name == "{#NAME}")].first()

The capacity allocated in bytes.

Preprocessing:

- JSONPATH: $.allocatedCapacity

The total provisioned capacity of the volume in bytes.

Preprocessing:

- JSONPATH: $.provisionedCapacity

The current state of the resource:

AddFailed - an attempt to add the resource failed;

Adding - the resource is in the process of being added;

Configured - the resource is configured;

Connected - the appliance has connected to the resource;

Copying - the resource is in the process of being copied;

CreateFailed - an attempt to create the resource failed;

Creating - the resource is in the process of being created;

DeleteFailed - an attempt to delete the resource failed;

Deleting - the resource is in the process of being deleted;

Discovered - the resource has been discovered by the appliance, but it is not managed by the appliance;

Managed - the resource is managed by the appliance;

Normal - the resource is in a normal state;

UpdateFailed - an attempt to update the resource failed;

Updating - the resource is in the process of being updated.

Preprocessing:

- JSONPATH: $.state

- STRREPLACE: AddFailed 0

- STRREPLACE: Adding 1

- STRREPLACE: Configured 2

- STRREPLACE: Connected 3

- STRREPLACE: Copying 4

- STRREPLACE: CreateFailed 5

- STRREPLACE: Creating 6

- STRREPLACE: DeleteFailed 7

- STRREPLACE: Deleting 8

- STRREPLACE: Discovered 9

- STRREPLACE: Managed 10

- STRREPLACE: Normal 11

- STRREPLACE: UpdateFailed 12

- STRREPLACE: Updating 13

- INRANGE: 0 13

⛔️ONFAIL: CUSTOM_VALUE -> 14

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing:

- JSONPATH: $.status

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ON_FAIL: CUSTOM_VALUE -> 3

Data of the manager [{#ENCLOSURENAME}:{#BAYNUMBER}].

Preprocessing:

- JSONPATH: $.members[?(@.name == "{#ENCLOSURE_NAME}")].managerBays[?(@.bayNumber == "{#BAY_NUMBER}")].first()

The firmware version of the manager.

- DISCARDUNCHANGED_HEARTBEAT: 1d

The state of the LINK port:

Disabled - the port is disabled;

Linked - the port is linked;

Unlinked - the port is unlinked.

Preprocessing:

- JSONPATH: $.linkPortState

- STRREPLACE: Disabled 0

- STRREPLACE: Linked 1

- STRREPLACE: Unlinked 2

- INRANGE: 0 2

⛔️ONFAIL: CUSTOM_VALUE -> 3

- DISCARDUNCHANGED_HEARTBEAT: 10m

The status of the LINK port:

Critical - requires immediate attention;

Disabled - the resource is currently not operational;

OK - indicates normal/informational behavior;

Unknown - the health status is not yet known or cannot be determined;

Warning - requires attention soon.

Preprocessing:

- JSONPATH: $.linkPortStatus

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ON_FAIL: CUSTOM_VALUE -> 3

The state of the MGMT port:

Active - the port is in active mode;

Disabled - the port is in disabled mode;

I3s - the port is configured for the deployment of an OS network traffic.

Other - the port is in other mode;

Standby - the port is in standby mode;

Unknown - the mode of the port is not known.

Preprocessing:

- JSONPATH: $.mgmtPortState

- STRREPLACE: Active 0

- STRREPLACE: Disabled 1

- STRREPLACE: I3s 2

- STRREPLACE: Other 3

- STRREPLACE: Standby 4

- STRREPLACE: Unknown 5

- INRANGE: 0 5

⛔️ONFAIL: CUSTOM_VALUE -> 5

- DISCARDUNCHANGEDHEARTBEAT: 10m

The status of the MGMT port:

Critical - requires immediate attention;

Disabled - the resource is currently not operational;

OK - indicates normal/informational behavior;

Unknown - the health status is not yet known or cannot be determined;

Warning - requires attention soon.

Preprocessing:

- JSONPATH: $.mgmtPortStatus

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ON_FAIL: CUSTOM_VALUE -> 3

The model of the link module.

Preprocessing:

- JSONPATH: $.model

- DISCARDUNCHANGEDHEARTBEAT: 1d

The part number of the link module.

- DISCARDUNCHANGED_HEARTBEAT: 1d

Indicates whether a manager is present in the bay:

Absent - the device slot is empty;

PresenceNoOp - the device slot is uninitialized;

PresenceUnknown - the device presence is unknown;

Present - the device slot has a device in it;

Subsumed - the device slot is configured to be part of another device slot. Not applicable for the fan or power supply bays.

Preprocessing:

- JSONPATH: $.devicePresence

- STRREPLACE: Absent 0

- STRREPLACE: PresenceNoOp 1

- STRREPLACE: PresenceUnknown 2

- STRREPLACE: Present 3

- STRREPLACE: Subsumed 4

- INRANGE: 0 4

⛔️ONFAIL: CUSTOM_VALUE -> 2

- DISCARDUNCHANGED_HEARTBEAT: 1h

The serial number of the link module.

- DISCARDUNCHANGED_HEARTBEAT: 1d

The spare part number of the link module.

Preprocessing:

- JSONPATH: $.sparePartNumber

- DISCARDUNCHANGEDHEARTBEAT: 1d

The health status of the link module:

Critical - requires immediate attention;

Disabled - the resource is currently not operational;

OK - indicates normal/informational behavior;

Unknown - the health status is not yet known or cannot be determined;

Warning - requires attention soon.

Preprocessing:

- JSONPATH: $.status

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ON_FAIL: CUSTOM_VALUE -> 3

Data of the uplink set [{#NAME}].

Preprocessing:

- JSONPATH: $.members[?(@.name == "{#NAME}")].first()

The current state of the resource.

- DISCARDUNCHANGED_HEARTBEAT: 1h

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

- DISCARDUNCHANGEDHEARTBEAT: 10m

- STRREPLACE: Critical 0

- STRREPLACE: Disabled 1

- STRREPLACE: OK 2

- STRREPLACE: Unknown 3

- STRREPLACE: Warning 4

- INRANGE: 0 4

⛔️ONFAIL: CUSTOM_VALUE -> 3

Zabbix has received errors from API.

Depends on:

- HPE Synergy: Service is unavailable

-

Manual close: YES

The appliance [{#ENCLOSURENAME}:{#BAYNUMBER}] status is critical. Needs immediate attention.

The appliance [{#ENCLOSURENAME}:{#BAYNUMBER}] status is warning. Needs attention soon.

The appliance [{#ENCLOSURENAME}:{#BAYNUMBER}] is currently not operational

The device slot is configured to be part of another device slot.

The crossbar [{#ENCLOSURENAME}:{#BAYNUMBER}] status is critical. Needs immediate attention.

The crossbar [{#ENCLOSURENAME}:{#BAYNUMBER}] status is warning. Needs attention soon.

The crossbar [{#ENCLOSURENAME}:{#BAYNUMBER}] currently not operational.

The adding of the datacenter [{#NAME}] has failed.

The datacenter [{#NAME}] has a credential error.

The datacenter [{#NAME}] has a refresh error.

The datacenter [{#NAME}] has a remove error.

The datacenter [{#NAME}] status is critical. Needs immediate attention.

The datacenter [{#NAME}] status is warning. Needs attention soon.

the datacenter [{#NAME}] currently not operational.

The device slot is configured to be part of another device slot.

The previous operation on the enclosure did not complete. The operation should be re-attempted.

The enclosure model or version is not currently supported by HPE OneView. It cannot be configured or monitored.

The previous operation to remove the enclosure did not succeed. The operation should be re-attempted.

The enclosure is no longer connected into the frame link topology.

The enclosure reports are not being under the management.

The status of the enclosure [{#NAME}] is critical. Needs immediate attention.

The status of the enclosure [{#NAME}] is warning. Needs attention soon.

The enclosure [{#NAME}] is currently not operational.

The ethernet network [{#NAME}] status is critical. Needs immediate attention.

The ethernet network [{#NAME}] status is warning. Needs attention soon.

The ethernet network [{#NAME}] is currently not operational.

The status of the fabric [{#NAME}] is critical. Needs immediate attention.

The status of the fabric [{#NAME}] is warning. Needs attention soon.

The status of the fabric [{#NAME}] is currently not operational.

The fan [{#ENCLOSURENAME}:{#BAYNUMBER}] is in degraded state.

The fan [{#ENCLOSURENAME}:{#BAYNUMBER}] is in failed state.

The fan [{#ENCLOSURENAME}:{#BAYNUMBER}] is misplaced.

The fan [{#ENCLOSURENAME}:{#BAYNUMBER}] is missing.

The fan [{#ENCLOSURENAME}:{#BAYNUMBER}] status is critical. Needs immediate attention.

The fan [{#ENCLOSURENAME}:{#BAYNUMBER}] status is warning. Needs attention soon.

The fan [{#ENCLOSURENAME}:{#BAYNUMBER}] is currently not operational.

The FC network [{#NAME}] status is critical. Needs immediate attention.

The FC network [{#NAME}] status is warning. Needs attention soon.

The FC network [{#NAME}] is currently not operational.

The hypervisor manager [{#NAME}] has an error.

The hypervisor manager [{#NAME}] status is critical. Needs immediate attention.

The hypervisor manager [{#NAME}] status is warning. Needs attention soon.

The hypervisor manager [{#NAME}] is currently not operational.

The interconnect [{#NAME}] status is critical. Needs immediate attention.

The interconnect [{#NAME}] status is warning. Needs attention soon.

The interconnect [{#NAME}] is currently not operational.

Indicator that the deletion of a logical enclosure failed.

The configuration of the logical enclosure differs from that of the enclosure group, or the configuration of the hardware resources is inconsistent with the logical enclosure configuration. Perform an Update from group, Reapply configuration, or Update firmware action as an appropriate to bring the configuration back into consistency.

The status of the logical enclosure [{#NAME}] is critical. Needs immediate attention.

The status of the logical enclosure [{#NAME}] is warning. Needs attention soon.

The logical enclosure [{#NAME}] is currently not operational.

The partition health is invalid.

One or more resources in the partition are unhealthy.

The partition status is invalid.

The status of the power supply [{#ENCLOSURENAME}:{#BAYNUMBER}] is critical. Needs immediate attention.

The status of the power supply [{#ENCLOSURENAME}:{#BAYNUMBER}] is warning. Needs attention soon.

The status of Power Supply [{#ENCLOSURENAME}:{#BAYNUMBER}] is currently not operational.

Adding the rack [{#NAME}] failed.

The rack [{#NAME}] has credential error.

The rack [{#NAME}] has refresh error.

The rack [{#NAME}] has remove error.

The rack [{#NAME}] status is critical. Needs immediate attention.

The rack [{#NAME}] status is warning. Needs attention soon.

The rack [{#NAME}] is currently not operational.

The disruptive maintenance operations like firmware update can cause many server hardware alerts to be generated in a short period of time. Example: Network connectivity is lost or the server reset is detected.

The unsuccessful profile application or removal.

The server is not initialized.

The server model or version is not currently supported by the appliance.

The previous operation to remove the server hardware did not succeed. The operation should be re-attempted.

Discovered a supported server.

The status of the server [{#SERVER_NAME}:{#LOCATION}] is critical. Needs immediate attention.

The status of the server [{#SERVER_NAME}:{#LOCATION}] is warning. Needs attention soon.

The server [{#SERVER_NAME}:{#LOCATION}] is currently not operational.

Adding of the storage pool [{#NAME}] failed.

Creating of the storage pool [{#NAME}] failed.

Deletion of the storage pool [{#NAME}] failed.

Updating of the storage pool [{#NAME}] failed.

The status of the storage pool [{#NAME}] is critical. Needs immediate attention.

The status of the storage pool [{#NAME}] is warning. Needs attention soon.

The storage pool [{#NAME}] is currently not operational.

Adding the storage system [{#NAME}] failed.

Creating of the storage system [{#NAME}] failed.

Deletion of the storage system [{#NAME}] failed.

Updating of the storage system [{#NAME}] failed.

The status of the storage system [{#NAME}] is critical. Needs immediate attention.

The status of the storage system [{#NAME}] is warning. Needs attention soon.

The storage system [{#NAME}] is currently not operational.

Adding the storage volume [{#NAME}] failed.

Creating of the storage volume [{#NAME}] failed.

Deletion of the storage volume [{#NAME}] failed.

Updating of the storage volume [{#NAME}] failed.

The status of the storage volume [{#NAME}] is critical. Needs immediate attention.

The status of the storage volume [{#NAME}] is warning. Needs attention soon.

The storage volume [{#NAME}] is currently not operational.

The link port status of the manager [{#ENCLOSURENAME}:{#BAYNUMBER}] is critical. Needs immediate attention.

The link port status of the manager [{#ENCLOSURENAME}:{#BAYNUMBER}] is warning. Needs attention soon.

The link port of the manager [{#ENCLOSURENAME}:{#BAYNUMBER}] is currently not operational.

The MGMT port status of the manager [{#ENCLOSURENAME}:{#BAYNUMBER}] is critical. Needs immediate attention.

The MGMT port status of the manager [{#ENCLOSURENAME}:{#BAYNUMBER}] is warning. Needs attention soon.

The MGMT port of the manager [{#ENCLOSURENAME}:{#BAYNUMBER}] is currently not operational.

The device slot is configured to be part of another device slot.

The status of the manager [{#ENCLOSURENAME}:{#BAYNUMBER}] is critical. Needs immediate attention.

The status of the manager [{#ENCLOSURENAME}:{#BAYNUMBER}] is warning. Needs attention soon.

The manager [{#ENCLOSURENAME}:{#BAYNUMBER}] is currently not operational.

The status of the uplink set [{#NAME}] is critical. Needs immediate attention.

The status of the uplink set [{#NAME}] is warning. Needs attention soon.

The uplink set [{#NAME}] is currently not operational.

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

Scanning table of Array controllers: CPQIDA-MIB::cpqDaAccelTable

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

Scanning table of Array controllers: CPQIDA-MIB::cpqDaCntlrTable

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

CPQHLTH-MIB::cpqHeFltTolFanCondition

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

Scanning table of physical drive entries CPQIDA-MIB::cpqDaPhyDrvTable.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

CPQHLTH-MIB::cpqHeFltTolPowerSupplyStatus

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

Scanning table of Temperature Sensor Entries: CPQHLTH-MIB::cpqHeTemperatureTable

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

Filter:

- {#SENSORLOCALE} MATCHES_REGEX `(4

Scanning table of Temperature Sensor Entries: CPQHLTH-MIB::cpqHeTemperatureTable with ambient(11) and 0.1 index filter

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

Filter:

- {#SNMPINDEX} MATCHESREGEX 0\.1

- {#SENSORLOCALE} MATCHESREGEX 11

Scanning table of Temperature Sensor Entries: CPQHLTH-MIB::cpqHeTemperatureTable with cpu(6) filter

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

Filter:

- {#SENSORLOCALE} MATCHES_REGEX 6

Scanning table of Temperature Sensor Entries: CPQHLTH-MIB::cpqHeTemperatureTable with ioBoard(5) filter

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

Filter:

- {#SENSORLOCALE} MATCHES_REGEX 5

Scanning table of Temperature Sensor Entries: CPQHLTH-MIB::cpqHeTemperatureTable with memory(7) filter

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

Filter:

- {#SENSORLOCALE} MATCHES_REGEX 7

Scanning table of Temperature Sensor Entries: CPQHLTH-MIB::cpqHeTemperatureTable with powerSupply(10) filter

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

Filter:

- {#SENSORLOCALE} MATCHES_REGEX 10

Scanning table of Temperature Sensor Entries: CPQHLTH-MIB::cpqHeTemperatureTable with system(3) filter

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

Filter:

- {#SENSORLOCALE} MATCHES_REGEX 3

CPQIDA-MIB::cpqDaLogDrvTable

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQIDA-MIB

This value represents the overall condition of this controller,

and any associated logical drives,physical drives, and array accelerators.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQIDA-MIB

Array Controller Model. The type of controller card.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQIDA-MIB

Cache Module/Operations Status. This describes the status of the cache module and/or cache operations.

Note that for some controller models, a cache module board that physically attaches to the controller or chipset may not be an available option.

The status can be:

Other (1)

Indicates that the instrument agent does not recognize the status of the cache module. You may need to upgrade the instrument agent.

Invalid (2)

Indicates that a cache module board has not been installed in this system or is present but not configured.

Enabled (3)

Indicates that cache operations are currently configured and enabled for at least one logical drive.

Temporarily Disabled (4)

Indicates that cache operations have been temporarily disabled. View the cache module board error code object to determine why the write cache operations have been temporarily disabled.

Permanently Disabled (5)

Indicates that cache operations have been permanently disabled. View the cache module board error code object to determine why the write cache operations have been disabled.

Cache Module Flash Memory Not Attached (6)

Indicates that the flash memory component of the flash backed cache module is not attached. This status will be set when the flash memory is not attached and the Supercap is attached. This value is only used on flash backed cache modules that support removable flash memory.

Cache Module Degraded Failsafe Speed (7)

Indicates that the cache module board is currently degraded and operating at a failsafe speed. View variables cpqDaCacheMemoryDataWidth and cpqDaCacheMemoryTransferRate to obtain the cache module board`s current memory data width and memory transfer rate.

Cache Module Critical Failure (8)

Indicates that the cache module board has encountered a critical failure. The controller is currently operating in Zero Memory Raid mode.

Read Cache Could Not Be Mapped (9)

Indicates that the read cache memory in a split cache configuration could not be mapped by the operating system and as a result is not available. This status may be caused by virtual space limitations in certain operating systems and is only applicable to B-Series controllers.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQIDA-MIB

Cache Module Board Backup Power Status. This monitors the status of each backup power source on the board.

The backup power source can only recharge when the system has power applied. The type of backup power source used is indicated by cpqDaAccelBackupPowerSource.

The following values are valid:

Other (1) Indicates that the instrument agent does not recognize backup power status. You may need to update your software.

Ok (2) The backup power source is fully charged.

Recharging (3) The array controller has one or more cache module backup power sources that are recharging.

Cache module operations such as Battery/Flash Backed Write Cache, Expansion, Extension and Migration are temporarily suspended until the backup power source is fully charged.

Cache module operations will automatically resume when charging is complete.

Failed (4) The battery pack is below the sufficient voltage level and has not recharged in 36 hours.

Your Cache Module board needs to be serviced.

Degraded (5) The battery is still operating, however, one of the batteries in the pack has failed to recharge properly.

Your Cache Module board should be serviced as soon as possible.

NotPresent (6) A backup power source is not present on the cache module board. Some controllers do not have backup power sources.

Capacitor Failed (7) The flash backed cache module capacitor is below the sufficient voltage level and has not recharged in 10 minutes. Your Cache Module board needs to be serviced.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQHLTH-MIB

The condition of the fan.

This value will be one of the following:

other(1) Fan status detection is not supported by this system or driver.

ok(2) The fan is operating properly.

degraded(2) A redundant fan is not operating properly.

failed(4) A non-redundant fan is not operating properly.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

The item is used to collect all SNMP traps unmatched by other snmptrap items

MIB: SNMPv2-MIB

The physical location of this node (e.g., `telephone closet, 3rd floor'). If the location is unknown, the value is the zero-length string.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 12h

MIB: SNMPv2-MIB

The textual identification of the contact person for this managed node, together with information on how to contact this person. If no contact information is known, the value is the zero-length string.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 12h

MIB: SNMPv2-MIB

The vendor's authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determiningwhat kind of box' is being managed. For example, if vendorFlintstones, Inc.' was assigned the subtree1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 12h

MIB: SNMPv2-MIB

An administratively-assigned name for this managed node.By convention, this is the node's fully-qualified domain name. If the name is unknown, the value is the zero-length string.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 12h

MIB: SNMPv2-MIB

A textual description of the entity. This value should

include the full name and version identification of the system's hardware type, software operating-system, and

networking software.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 12h

MIB: CPQSINFO-MIB

The machine product name.The name of the machine used in this system.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQSINFO-MIB

The serial number of the physical system unit. The string will be empty if the system does not report the serial number function.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQIDA-MIB

Physical Drive Status. This shows the status of the physical drive. The following values are valid for the physical drive status:

other (1) Indicates that the instrument agent does not recognize the drive.

You may need to upgrade your instrument agent and/or driver software.

ok (2) Indicates the drive is functioning properly.

failed (3) Indicates that the drive is no longer operating and should be replaced.

predictiveFailure(4) Indicates that the drive has a predictive failure error and should be replaced.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQIDA-MIB

Physical Drive S.M.A.R.T Status.The following values are defined:

other(1) The agent is unable to determine if the status of S.M.A.R.T predictive failure monitoring for this drive.

ok(2) Indicates the drive is functioning properly.

replaceDrive(3) Indicates that the drive has a S.M.A.R.T predictive failure error and should be replaced.

- DISCARDUNCHANGED_HEARTBEAT: 6h

MIB: CPQIDA-MIB

Physical Drive Serial Number.

This is the serial number assigned to the physical drive.

This value is based upon the serial number as returned by the SCSI inquiry command

but may have been modified due to space limitations. This can be used for identification purposes.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQIDA-MIB

Physical Drive Model.This is a text description of the physical drive.

The text that appears depends upon who manufactured the drive and the drive type.

If a drive fails, note the model to identify the type of drive necessary for replacement.

If a model number is not present, you may not have properly initialized the drive array to which the physical drive is attached for monitoring.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQIDA-MIB

Drive Array Physical Drive Media Type.The following values are defined:

other(1) The instrument agent is unable to determine the physical drive's media type.

rotatingPlatters(2) The physical drive media is composed of rotating platters.

solidState(3) The physical drive media is composed of solid state electronics.

- DISCARDUNCHANGED_HEARTBEAT: 6h

MIB: CPQIDA-MIB

Physical Drive Size in MB.

This is the size of the physical drive in megabytes.

This value is calculated using the value 1,048,576 (2^20) as a megabyte.

Drive manufacturers sometimes use the number 1,000,000 as a megabyte when giving drive capacities so this value may differ

from the advertised size of a drive. This field is only applicable for controllers which support SCSI drives,

and therefore is not supported by the IDA or IDA-2 controllers. The field will contain 0xFFFFFFFF if the drive capacity cannot be calculated

or if the controller does not support SCSI drives.

Preprocessing:

- MULTIPLIER: 1048576

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQHLTH-MIB

The condition of the power supply. This value will be one of the following:

other(1) The status could not be determined or not present.

ok(2) The power supply is operating normally.

degraded(3) A temperature sensor, fan or other power supply component is outside of normal operating range.

failed(4) A power supply component detects a condition that could permanently damage the system.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQHLTH-MIB

The overall condition. This object represents the overall status of the server information represented by this MIB.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: SNMPv2-MIB

The time (in hundredths of a second) since the network management portion of the system was last re-initialized.

Preprocessing:

- MULTIPLIER: 0.01

MIB: HOST-RESOURCES-MIB

The amount of time since this host was last initialized. Note that this is different from sysUpTime in the SNMPv2-MIB [RFC1907] because sysUpTime is the uptime of the network management portion of the system.

Preprocessing:

- CHECKNOTSUPPORTED

⛔️ON_FAIL: CUSTOM_VALUE -> 0

- MULTIPLIER: 0.01

Availability of SNMP checks on the host. The value of this item corresponds to availability icons in the host list.

Possible value:

0 - not available

1 - available

2 - unknown

-

-

-

MIB: CPQHLTH-MIB

This value specifies the overall condition of the system's thermal environment.

This value will be one of the following:

other(1) Temperature could not be determined.

ok(2) The temperature sensor is within normal operating range.

degraded(3) The temperature sensor is outside of normal operating range.

failed(4) The temperature sensor detects a condition that could permanently damage the system.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQHLTH-MIB

Temperature readings of testpoint: {#SNMPINDEX}

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQHLTH-MIB

This specifies the location of the temperature sensor present in the system.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQHLTH-MIB

The Temperature sensor condition.

This value will be one of the following:

other(1)

Temperature could not be determined.

ok(2)

The temperature sensor is within normal operating range.

degraded(3)

The temperature sensor is outside of normal operating range.

failed(4)

The temperature sensor detects a condition that could

permanently damage the system.

The system will automatically shutdown if the failed(4) condition results, so it is unlikely that this value will ever be returned by the agent. If the cpqHeThermalDegradedAction is set to shutdown(3) the system will be shutdown if the degraded(3) condition occurs.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQHLTH-MIB

Temperature readings of testpoint: Ambient

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQHLTH-MIB

The Temperature sensor condition.

This value will be one of the following:

other(1)

Temperature could not be determined.

ok(2)

The temperature sensor is within normal operating range.

degraded(3)

The temperature sensor is outside of normal operating range.

failed(4)

The temperature sensor detects a condition that could

permanently damage the system.

The system will automatically shutdown if the failed(4) condition results, so it is unlikely that this value will ever be returned by the agent. If the cpqHeThermalDegradedAction is set to shutdown(3) the system will be shutdown if the degraded(3) condition occurs.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQHLTH-MIB

Temperature readings of testpoint: CPU-{#SNMPINDEX}

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQHLTH-MIB

The Temperature sensor condition.

This value will be one of the following:

other(1)

Temperature could not be determined.

ok(2)

The temperature sensor is within normal operating range.

degraded(3)

The temperature sensor is outside of normal operating range.

failed(4)

The temperature sensor detects a condition that could

permanently damage the system.

The system will automatically shutdown if the failed(4) condition results, so it is unlikely that this value will ever be returned by the agent. If the cpqHeThermalDegradedAction is set to shutdown(3) the system will be shutdown if the degraded(3) condition occurs.

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQHLTH-MIB

Temperature readings of testpoint: Memory-{#SNMPINDEX}

Preprocessing:

- DISCARDUNCHANGEDHEARTBEAT: 6h

MIB: CPQHLTH-MIB

The Temperature sensor condition.

This value will be one of the following:

other(1)

Temperature could not be determined.

ok(2)

The temperature sensor is within normal operating range.

degraded(3)

The temperature sensor is outside of normal operating range.

failed(4)

The temperature sensor detects a condition that could

permanently damage the system.

The system will automatically shutdown if the failed(4) condition results, so it is unlikely that this value will ever be returned by the agent. If the cpqHeThermalDegradedAction is set to shutdown(3) the system will be shutdown if the degraded(3) condition occurs.

Preprocessing: