OID reference

chasPowerSupplyRedundancyReserve

1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.25

Description

When chasPowerSupplyRedundancyReserve is enabled, N+1 power supply redundancy reserve holds the wattage of one power supply in reserve such that the user cannot insert NIs or configure power over Ethernet (POE) that will use the reserved power from that supply. There are two main advantages to enabling chasPowerSupply…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1 (chasChassisEntry)
Node code
25
Node name
chasPowerSupplyRedundancyReserve
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.25
URN notation
urn:oid:1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.25
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 6486 801 1 1 1 3 1 1 3 1 25}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alcatel(6486) alcatelIND1BaseMIB(801) alcatelIND1Management(1) managementIND1Hardware(1) hardwareIND1Entities(1) hardentIND1Chassis(3) alcatelIND1ChassisMIB(1) alcatelIND1ChassisMIBObjects(1) chasChassisTable(3) chasChassisEntry(1) chasPowerSupplyRedundancyReserve(25)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ale(6486) alcatelIND1BaseMIB(801) alcatelIND1Management(1) managementIND1Hardware(1) hardwareIND1Entities(1) hardentIND1Chassis(3) alcatelIND1ChassisMIB(1) alcatelIND1ChassisMIBObjects(1) chasChassisTable(3) chasChassisEntry(1) chasPowerSupplyRedundancyReserve(25)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) alcatel(6486) alcatelIND1BaseMIB(801) alcatelIND1Management(1) managementIND1Hardware(1) hardwareIND1Entities(1) hardentIND1Chassis(3) alcatelIND1ChassisMIB(1) alcatelIND1ChassisMIBObjects(1) chasChassisTable(3) chasChassisEntry(1) chasPowerSupplyRedundancyReserve(25)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ale(6486) alcatelIND1BaseMIB(801) alcatelIND1Management(1) managementIND1Hardware(1) hardwareIND1Entities(1) hardentIND1Chassis(3) alcatelIND1ChassisMIB(1) alcatelIND1ChassisMIBObjects(1) chasChassisTable(3) chasChassisEntry(1) chasPowerSupplyRedundancyReserve(25)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) alcatel(6486) alcatelIND1BaseMIB(801) alcatelIND1Management(1) managementIND1Hardware(1) hardwareIND1Entities(1) hardentIND1Chassis(3) alcatelIND1ChassisMIB(1) alcatelIND1ChassisMIBObjects(1) chasChassisTable(3) chasChassisEntry(1) chasPowerSupplyRedundancyReserve(25)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ale(6486) alcatelIND1BaseMIB(801) alcatelIND1Management(1) managementIND1Hardware(1) hardwareIND1Entities(1) hardentIND1Chassis(3) alcatelIND1ChassisMIB(1) alcatelIND1ChassisMIBObjects(1) chasChassisTable(3) chasChassisEntry(1) chasPowerSupplyRedundancyReserve(25)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) alcatel(6486) alcatelIND1BaseMIB(801) alcatelIND1Management(1) managementIND1Hardware(1) hardwareIND1Entities(1) hardentIND1Chassis(3) alcatelIND1ChassisMIB(1) alcatelIND1ChassisMIBObjects(1) chasChassisTable(3) chasChassisEntry(1) chasPowerSupplyRedundancyReserve(25)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ale(6486) alcatelIND1BaseMIB(801) alcatelIND1Management(1) managementIND1Hardware(1) hardwareIND1Entities(1) hardentIND1Chassis(3) alcatelIND1ChassisMIB(1) alcatelIND1ChassisMIBObjects(1) chasChassisTable(3) chasChassisEntry(1) chasPowerSupplyRedundancyReserve(25)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) alcatel(6486) alcatelIND1BaseMIB(801) alcatelIND1Management(1) managementIND1Hardware(1) hardwareIND1Entities(1) hardentIND1Chassis(3) alcatelIND1ChassisMIB(1) alcatelIND1ChassisMIBObjects(1) chasChassisTable(3) chasChassisEntry(1) chasPowerSupplyRedundancyReserve(25)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) ale(6486) alcatelIND1BaseMIB(801) alcatelIND1Management(1) managementIND1Hardware(1) hardwareIND1Entities(1) hardentIND1Chassis(3) alcatelIND1ChassisMIB(1) alcatelIND1ChassisMIBObjects(1) chasChassisTable(3) chasChassisEntry(1) chasPowerSupplyRedundancyReserve(25)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) alcatel(6486) alcatelIND1BaseMIB(801) alcatelIND1Management(1) managementIND1Hardware(1) hardwareIND1Entities(1) hardentIND1Chassis(3) alcatelIND1ChassisMIB(1) alcatelIND1ChassisMIBObjects(1) chasChassisTable(3) chasChassisEntry(1) chasPowerSupplyRedundancyReserve(25)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) ale(6486) alcatelIND1BaseMIB(801) alcatelIND1Management(1) managementIND1Hardware(1) hardwareIND1Entities(1) hardentIND1Chassis(3) alcatelIND1ChassisMIB(1) alcatelIND1ChassisMIBObjects(1) chasChassisTable(3) chasChassisEntry(1) chasPowerSupplyRedundancyReserve(25)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) alcatel(6486) alcatelIND1BaseMIB(801) alcatelIND1Management(1) managementIND1Hardware(1) hardwareIND1Entities(1) hardentIND1Chassis(3) alcatelIND1ChassisMIB(1) alcatelIND1ChassisMIBObjects(1) chasChassisTable(3) chasChassisEntry(1) chasPowerSupplyRedundancyReserve(25)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) ale(6486) alcatelIND1BaseMIB(801) alcatelIND1Management(1) managementIND1Hardware(1) hardwareIND1Entities(1) hardentIND1Chassis(3) alcatelIND1ChassisMIB(1) alcatelIND1ChassisMIBObjects(1) chasChassisTable(3) chasChassisEntry(1) chasPowerSupplyRedundancyReserve(25)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) alcatel(6486) alcatelIND1BaseMIB(801) alcatelIND1Management(1) managementIND1Hardware(1) hardwareIND1Entities(1) hardentIND1Chassis(3) alcatelIND1ChassisMIB(1) alcatelIND1ChassisMIBObjects(1) chasChassisTable(3) chasChassisEntry(1) chasPowerSupplyRedundancyReserve(25)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) ale(6486) alcatelIND1BaseMIB(801) alcatelIND1Management(1) managementIND1Hardware(1) hardwareIND1Entities(1) hardentIND1Chassis(3) alcatelIND1ChassisMIB(1) alcatelIND1ChassisMIBObjects(1) chasChassisTable(3) chasChassisEntry(1) chasPowerSupplyRedundancyReserve(25)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/6486/801/1/1/1/3/1/1/3/1/25
  • /ISO/Identified-Organization/6/1/4/1/6486/801/1/1/1/3/1/1/3/1/25
  • /ISO/3/6/1/4/1/6486/801/1/1/1/3/1/1/3/1/25
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/alcatel/alcatelIND1BaseMIB/alcatelIND1Management/managementIND1Hardware/hardwareIND1Entities/hardentIND1Chassis/alcatelIND1ChassisMIB/alcatelIND1ChassisMIBObjects/chasChassisTable/chasChassisEntry/chasPowerSupplyRedundancyReserve
  • /iso/identified-organization/dod/internet/private/enterprise/ale/alcatelIND1BaseMIB/alcatelIND1Management/managementIND1Hardware/hardwareIND1Entities/hardentIND1Chassis/alcatelIND1ChassisMIB/alcatelIND1ChassisMIBObjects/chasChassisTable/chasChassisEntry/chasPowerSupplyRedundancyReserve
  • /iso/identified-organization/dod/internet/private/enterprises/alcatel/alcatelIND1BaseMIB/alcatelIND1Management/managementIND1Hardware/hardwareIND1Entities/hardentIND1Chassis/alcatelIND1ChassisMIB/alcatelIND1ChassisMIBObjects/chasChassisTable/chasChassisEntry/chasPowerSupplyRedundancyReserve
  • /iso/identified-organization/dod/internet/private/enterprises/ale/alcatelIND1BaseMIB/alcatelIND1Management/managementIND1Hardware/hardwareIND1Entities/hardentIND1Chassis/alcatelIND1ChassisMIB/alcatelIND1ChassisMIBObjects/chasChassisTable/chasChassisEntry/chasPowerSupplyRedundancyReserve
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/alcatel/alcatelIND1BaseMIB/alcatelIND1Management/managementIND1Hardware/hardwareIND1Entities/hardentIND1Chassis/alcatelIND1ChassisMIB/alcatelIND1ChassisMIBObjects/chasChassisTable/chasChassisEntry/chasPowerSupplyRedundancyReserve
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/ale/alcatelIND1BaseMIB/alcatelIND1Management/managementIND1Hardware/hardwareIND1Entities/hardentIND1Chassis/alcatelIND1ChassisMIB/alcatelIND1ChassisMIBObjects/chasChassisTable/chasChassisEntry/chasPowerSupplyRedundancyReserve
  • /iso/identified-organization/dod/internet/private/vendor-objects/alcatel/alcatelIND1BaseMIB/alcatelIND1Management/managementIND1Hardware/hardwareIND1Entities/hardentIND1Chassis/alcatelIND1ChassisMIB/alcatelIND1ChassisMIBObjects/chasChassisTable/chasChassisEntry/chasPowerSupplyRedundancyReserve
  • /iso/identified-organization/dod/internet/private/vendor-objects/ale/alcatelIND1BaseMIB/alcatelIND1Management/managementIND1Hardware/hardwareIND1Entities/hardentIND1Chassis/alcatelIND1ChassisMIB/alcatelIND1ChassisMIBObjects/chasChassisTable/chasChassisEntry/chasPowerSupplyRedundancyReserve
  • /iso/org/dod/internet/private/enterprise/alcatel/alcatelIND1BaseMIB/alcatelIND1Management/managementIND1Hardware/hardwareIND1Entities/hardentIND1Chassis/alcatelIND1ChassisMIB/alcatelIND1ChassisMIBObjects/chasChassisTable/chasChassisEntry/chasPowerSupplyRedundancyReserve
  • /iso/org/dod/internet/private/enterprise/ale/alcatelIND1BaseMIB/alcatelIND1Management/managementIND1Hardware/hardwareIND1Entities/hardentIND1Chassis/alcatelIND1ChassisMIB/alcatelIND1ChassisMIBObjects/chasChassisTable/chasChassisEntry/chasPowerSupplyRedundancyReserve
  • /iso/org/dod/internet/private/enterprises/alcatel/alcatelIND1BaseMIB/alcatelIND1Management/managementIND1Hardware/hardwareIND1Entities/hardentIND1Chassis/alcatelIND1ChassisMIB/alcatelIND1ChassisMIBObjects/chasChassisTable/chasChassisEntry/chasPowerSupplyRedundancyReserve
  • /iso/org/dod/internet/private/enterprises/ale/alcatelIND1BaseMIB/alcatelIND1Management/managementIND1Hardware/hardwareIND1Entities/hardentIND1Chassis/alcatelIND1ChassisMIB/alcatelIND1ChassisMIBObjects/chasChassisTable/chasChassisEntry/chasPowerSupplyRedundancyReserve
  • /iso/org/dod/internet/private/ldap-enterprise/alcatel/alcatelIND1BaseMIB/alcatelIND1Management/managementIND1Hardware/hardwareIND1Entities/hardentIND1Chassis/alcatelIND1ChassisMIB/alcatelIND1ChassisMIBObjects/chasChassisTable/chasChassisEntry/chasPowerSupplyRedundancyReserve
  • /iso/org/dod/internet/private/ldap-enterprise/ale/alcatelIND1BaseMIB/alcatelIND1Management/managementIND1Hardware/hardwareIND1Entities/hardentIND1Chassis/alcatelIND1ChassisMIB/alcatelIND1ChassisMIBObjects/chasChassisTable/chasChassisEntry/chasPowerSupplyRedundancyReserve
  • /iso/org/dod/internet/private/vendor-objects/alcatel/alcatelIND1BaseMIB/alcatelIND1Management/managementIND1Hardware/hardwareIND1Entities/hardentIND1Chassis/alcatelIND1ChassisMIB/alcatelIND1ChassisMIBObjects/chasChassisTable/chasChassisEntry/chasPowerSupplyRedundancyReserve
  • /iso/org/dod/internet/private/vendor-objects/ale/alcatelIND1BaseMIB/alcatelIND1Management/managementIND1Hardware/hardwareIND1Entities/hardentIND1Chassis/alcatelIND1ChassisMIB/alcatelIND1ChassisMIBObjects/chasChassisTable/chasChassisEntry/chasPowerSupplyRedundancyReserve
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
on

Enumerated values

ValueName
1on
2off

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.

Published row index: entPhysicalIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.25

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

chasPowerSupplyRedundancyReserve       OBJECT-TYPE
    SYNTAX INTEGER
    {
       on(1),
       off(2)
    }
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "When chasPowerSupplyRedundancyReserve is enabled, N+1 power supply 
         redundancy reserve holds the wattage of one power supply in reserve 
         such that the user cannot insert NIs or configure power over Ethernet (POE)
         that will use the reserved power from that supply. There are two main advantages 
         to enabling chasPowerSupplyRedundancyReserve. The first advantage is that 
         it provides resiliency to avoid POE drawing power from the four main power supplies
         in the OS9900 chassis to the extent that POE sinks much more wattage than 
         the CMM, CFM, and NI board logic combined. (Note: The power management functions 
         on the OS9900 are complicated by the presence of the controllers on the GNI-P48 boards. 
         Unlike other chassis supporting POE, like OS6860, there is no separate power supply 
         for the POE front-panel ports.) This is not to be confused with chasPowerSupplyRedundancy 
         which switches off unneeded power supplies - on the OS9900, all inserted power supplies
         are always switched on and enabled. The second advantage of enabling 
         chasPowerSupplyRedundancyReserve is to avoid 'brown-outs'. 
         (A brown-out may happen when a system running at full POE capacity without the N+1 redundancy reserve
         enabled suffers a power supply failure causing the POE hardware to immediately
         disable power over Ethernet on the basis of port priority as soon as it detects the failure.
         Then, if there is still insufficient power available to run the logic and fan trays,
         the power supplies will 'crowbar' and the system will be power cycled. The software can 
         do little in this scenario since there is insufficient power to keep the CPU chips running.
         When the system reboots the chassis supervisor will only power-up NI slots based 
         upon the power available from the remaining power supplies.)"
    DEFVAL   { on }
::= { chasChassisEntry 25 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

When chasPowerSupplyRedundancyReserve is enabled, N+1 power supply redundancy reserve holds the wattage of one power supply in reserve such that the user cannot insert NIs or configure power over Ethernet (POE) that will use the reserved power from that supply. There are two main advantages to enabling chasPowerSupplyRedundancyReserve. The first advantage is that it provides resiliency to avoid POE drawing power from the four main power supplies in the OS9900 chassis to the extent that POE sinks much more wattage than the CMM, CFM, and NI board logic combined. (Note: The power management functions on the OS9900 are complicated by the presence of the controllers on the GNI-P48 boards. Unlike other chassis supporting POE, like OS6860, there is no separate power supply for the POE front-panel ports.) This is not to be confused with chasPowerSupplyRedundancy which switches off unneeded power supplies - on the OS9900, all inserted power supplies are always switched on and enabled. The second advantage of enabling chasPowerSupplyRedundancyReserve is to avoid 'brown-outs'. (A brown-out may happen when a system running at full POE capacity without the N+1 redundancy reserve enabled suffers a power supply failure causing the POE hardware to immediately disable power over Ethernet on the basis of port priority as soon as it detects the failure. Then, if there is still insufficient power available to run the logic and fan trays, the power supplies will 'crowbar' and the system will be power cycled. The software can do little in this scenario since there is insufficient power to keep the CPU chips running. When the system reboots the chassis supervisor will only power-up NI slots based upon the power available from the remaining power supplies.)

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Alcatel-Lucent Enterprise MIB copies (LibreNMS)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; representative source files are shown for each definition.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Alcatel-Lucent Enterprise MIB copies (LibreNMS)1 record · 3 sources

Description 1

chasPowerSupplyRedundancyReserve · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Alcatel-Lucent Enterprise MIB copies (LibreNMS)3 sources

Status in source: current.

Names: chasPowerSupplyRedundancyReserve

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "chasPowerSupplyRedundancyReserve",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "on",
    "(",
    "1",
    ")",
    ",",
    "off",
    "(",
    "2",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"When chasPowerSupplyRedundancyReserve is enabled, N+1 power supply redundancy reserve holds the wattage of one power supply in reserve such that the user cannot insert NIs or configure power over Ethernet (POE) that will use the reserved power from that supply. There are two main advantages to enabling chasPowerSupplyRedundancyReserve. The first advantage is that it provides resiliency to avoid POE drawing power from the four main power supplies in the OS9900 chassis to the extent that POE sinks much more wattage than the CMM, CFM, and NI board logic combined. (Note: The power management functions on the OS9900 are complicated by the presence of the controllers on the GNI-P48 boards. Unlike other chassis supporting POE, like OS6860, there is no separate power supply for the POE front-panel ports.) This is not to be confused with chasPowerSupplyRedundancy which switches off unneeded power supplies - on the OS9900, all inserted power supplies are always switched on and enabled. The second advantage of enabling chasPowerSupplyRedundancyReserve is to avoid 'brown-outs'. (A brown-out may happen when a system running at full POE capacity without the N+1 redundancy reserve enabled suffers a power supply failure causing the POE hardware to immediately disable power over Ethernet on the basis of port priority as soon as it detects the failure. Then, if there is still insufficient power available to run the logic and fan trays, the power supplies will 'crowbar' and the system will be power cycled. The software can do little in this scenario since there is insufficient power to keep the CPU chips running. When the system reboots the chassis supervisor will only power-up NI slots based upon the power available from the remaining power supplies.)\"",
    "DEFVAL",
    "{",
    "on",
    "}",
    "::=",
    "{",
    "chasChassisEntry",
    "25",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "on",
            1
          ],
          [
            "off",
            2
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "When chasPowerSupplyRedundancyReserve is enabled, N+1 power supply redundancy reserve holds the wattage of one power supply in reserve such that the user cannot insert NIs or configure power over Ethernet (POE) that will use the reserved power from that supply. There are two main advantages to enabling chasPowerSupplyRedundancyReserve. The first advantage is that it provides resiliency to avoid POE drawing power from the four main power supplies in the OS9900 chassis to the extent that POE sinks much more wattage than the CMM, CFM, and NI board logic combined. (Note: The power management functions on the OS9900 are complicated by the presence of the controllers on the GNI-P48 boards. Unlike other chassis supporting POE, like OS6860, there is no separate power supply for the POE front-panel ports.) This is not to be confused with chasPowerSupplyRedundancy which switches off unneeded power supplies - on the OS9900, all inserted power supplies are always switched on and enabled. The second advantage of enabling chasPowerSupplyRedundancyReserve is to avoid 'brown-outs'. (A brown-out may happen when a system running at full POE capacity without the N+1 redundancy reserve enabled suffers a power supply failure causing the POE hardware to immediately disable power over Ethernet on the basis of port priority as soon as it detects the failure. Then, if there is still insufficient power available to run the logic and fan trays, the power supplies will 'crowbar' and the system will be power cycled. The software can do little in this scenario since there is insufficient power to keep the CPU chips running. When the system reboots the chassis supervisor will only power-up NI slots based upon the power available from the remaining power supplies.)"
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "on"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.6486)

Dalton David R.

Siblings (24)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.1 chasFreeSlots00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.2 chasPowerLeft00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.3 chasNumberOfResets00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.4 chasTempRange00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.5 chasTempThreshold00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.6 chasDangerTempThreshold00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.7 chasPrimaryPhysicalIndex00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.8 chasCPMAHardwareBoardTemp00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.9 chasCFMAHardwareBoardTemp00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.10 chasCPMBHardwareBoardTemp00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.11 chasCFMBHardwareBoardTemp00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.12 chasCFMCHardwareBoardTemp00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.13 chasCFMDHardwareBoardTemp00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.14 chasFTAHardwareBoardTemp00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.15 chasFTBHardwareBoardTemp00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.16 chasNI1HardwareBoardTemp00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.17 chasNI2HardwareBoardTemp00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.18 chasNI3HardwareBoardTemp00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.19 chasNI4HardwareBoardTemp00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.20 chasNI5HardwareBoardTemp00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.21 chasNI6HardwareBoardTemp00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.22 chasNI7HardwareBoardTemp00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.23 chasNI8HardwareBoardTemp00
1.3.6.1.4.1.6486.801.1.1.1.3.1.1.3.1.24 chasPowerSupplyRedundancy00