JUNIPER-POWER-SUPPLY-UNIT-MIB
Updated Oct 27, 2010The JUNIPER-POWER-SUPPLY-UNIT-MIB enables SNMP-based monitoring and management of power supply unit status, voltage levels, current draw, and temperature metrics on Juniper Networks devices. It facilitates the detection of power failures, redundant unit status, and environmental thresholds to ensure hardware reliability and availability.
Imported Objects
Objects
42 total| Object Name |
|---|
jnxPsuMIBThe Juniper Supply Unit MIB definitions for enabling
power monitoring and management of a juniper device. MODULE-IDENTITY .1.3.6.1.4.1.2636.3.58.1 |
jnxPsuNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.58.1.1 |
jnxPsuObjects OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.58.1.2 |
jnxPsuScalars OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.58.1.2.1 |
jnxPsuAvailableDeviceCountGives the number of PSU units available online in the System.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.1.1 |
jnxPsuAvailableAveragePowerSupplyGives the total average power that the System can supply from the
available online units in Watts.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.1.2 |
jnxPsuAvailableMaxPowerSupplyGives the total maximum power that the System can supply from the
available online units in Watts.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.1.3 |
jnxPsuRedundancyPSU power redundancy configuration.ro Enumeration .1.3.6.1.4.1.2636.3.58.1.2.1.4 |
jnxPsuChassisPowerReservedPower reserved for Chassis in Watts.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.1.5 |
jnxPsuChassisPowerAllocatedTotal power allocated for chassis and all the FPCs in Watts.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.1.6 |
jnxPsuRedundantPowerAvailablePower(in Watts) that is still available for allocation
even while supporting redundancy with the present usage.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.1.7 |
jnxPsuTotalPowerAvailablePower(in Watts) which could be made available for further
allocation without supporting any redundancy with the present usage.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.1.8 |
jnxPsuChassisPowerConsumedTotal power consumed by the entire system rounded to the nearest integer.
This is calculated using the PowerFactor, Current and Voltage values
of each PSU that is online and connected to the System.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.1.9 |
jnxPsuTemperatureInflowAverage inflow temperature calculated from all
the available input sensors on the master RE.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.1.10 |
jnxPsuTemperatureOutflowAverage outflow temperature calculated from all
the available output sensors on the master RE.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.1.11 |
jnxPsuTemperatureInflowSamplesThe number of samples being taken while calculating
jnxPsuTemperatureInflow.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.1.12 |
jnxPsuTemperatureOutflowSamplesThe number of samples being taken while calculating
jnxPsuTemperatureOutflow.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.1.13 |
jnxPsuTableA list of power entries for each PSU component. SEQUENCE OF JnxPsuEntry .1.3.6.1.4.1.2636.3.58.1.2.2 |
jnxPsuEntryDefines an entry in jnxPsuTable. JnxPsuEntry .1.3.6.1.4.1.2636.3.58.1.2.2.1 |
jnxPsuAvgPowerBuffer that contains the average power used, in Watts
for each component.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.2.1.1 |
jnxPsuMaxPowerBuffer that contains the max power available, in Watts
for each component.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.2.1.2 |
jnxPsuModeMode for each PSU component.ro Enumeration .1.3.6.1.4.1.2636.3.58.1.2.2.1.3 |
jnxPsuOutletCountThe number of outlets (regardless of their current state)
present on this psu component, default is 0.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.2.1.4 |
jnxPsuEnvironmentTableA list of PSU Environment entries. SEQUENCE OF JnxPsuEnvironmentEntry .1.3.6.1.4.1.2636.3.58.1.2.3 |
jnxPsuEnvironmentEntryDefines an entry in jnxPsuEnvironmentTable. JnxPsuEnvironmentEntry .1.3.6.1.4.1.2636.3.58.1.2.3.1 |
jnxPsuThermalValueTemparature at each component in degrees Celsius rounded to
the nearest integer.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.3.1.1 |
jnxPsuHumidityValueHumidity at each component in percentage.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.3.1.2 |
jnxPsuOutletTableGives details of each Power outlet`s state,
capacity to supply power, and other details. SEQUENCE OF JnxPsuOutletEntry .1.3.6.1.4.1.2636.3.58.1.2.4 |
jnxPsuOutletEntryA value contained within the OutletEntry JnxPsuOutletEntry .1.3.6.1.4.1.2636.3.58.1.2.4.1 |
jnxPsuOutletNameOutlet name associated to the power supply unit for
each PSU Component.ro DisplayString .1.3.6.1.4.1.2636.3.58.1.2.4.1.1 |
jnxPsuOutletDescriptionOutlet description associated to the power supply unit for
each PSU Component.ro DisplayString .1.3.6.1.4.1.2636.3.58.1.2.4.1.2 |
jnxPsuOutletAvgPowerBuffer that contains the average power used, in Watts for each component.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.4.1.3 |
jnxPsuOutletMaxPowerBuffer that contains the maximum power available, in Watts for each component.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.4.1.4 |
jnxPsuOutletCurrentPSU output current in milliamps rounded to the nearest
integer.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.4.1.5 |
jnxPsuOutletStatusThe value of the operational status for the given outlet.
This can also be used to set the outlet statero Enumeration .1.3.6.1.4.1.2636.3.58.1.2.4.1.8 |
jnxPsuOutletVoltageOutput voltage in Volts rounded to the nearest integer.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.4.1.9 |
jnxPsuOutletPowerFactorValuePower factor percentage of each PSU (2k/3k).
Algorithm for calculation of Power Factor is below.
For PowerOut values that fall in between 618.93W and 915.24W,
say 700W, the appropriate PF ranges from 0.910191 &
0.917994. Following linear equation could help deduce a
fairly accurate input power value.
Linear equation y = mx + b (where m is the slope and b is
the Y intercept)
Slope m = (y2 - y1) / (x2 - x1)
Y intercept b = y - mx
Plugging it all together for our example:
m = (915.24 - 618.93) / (0.917994 - 0.910191) = 37973.86
b = 915.24 - (37973.86 * 0.917994) = -33944.5
for 700W (y), our efficiency (x) would then be:
x = (700 - (-33944.5)) / 37973.86 = 0.912326 = 91%
PowerIn = 700W /0.912326 = 767.26Wro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.4.1.10 |
jnxPsuOutletPowerConsumedPower Consumed by each outlet units in Watts.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.4.1.11 |
jnxPsuFpcPowerTableA list of entries for each FPC(Flexible PIC Concentrator)
giving it's assigned priority and power being allocated.
More information on FPCs can be found in JUNIPER-MIB. SEQUENCE OF JnxPsuFpcPowerEntry .1.3.6.1.4.1.2636.3.58.1.2.5 |
jnxPsuFpcPowerEntryA value contained within the FpcPowerEntry JnxPsuFpcPowerEntry .1.3.6.1.4.1.2636.3.58.1.2.5.1 |
jnxPsuFpcPowerPriorityThe Power budget priority assigned to the FPC.
Lower number means higher priority.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.5.1.1 |
jnxPsuFpcPowerAllocatedThe Power allocated to the FPC in Watts.ro INTEGER .1.3.6.1.4.1.2636.3.58.1.2.5.1.2 |
More MIBs from Juniper Networks
Browse all Juniper NetworksMIBs →The JUNIPER-CHASSIS-DEFINES-MIB establishes the foundational Object Identifier (OID) namespace and data type definitions required to map and identify specific Juniper chassis hardware platforms and their internal physical components. This module serves as the structural prerequisite for the JUNIPER-CHASSIS-MIB, enabling the retrieval of inventory data, component status, and hardware topology details for Juniper MX, PTX, and EX series devices.
The JUNIPER-MOBILE-GATEWAY-GTP-MIB provides SNMP objects for monitoring GTP (GPRS Tunneling Protocol) session states, tunnel endpoints, and protocol counters on Juniper mobile gateway platforms. It enables administrators to track GTP-C and GTP-U traffic statistics, error conditions, and active tunnel metrics essential for validating mobile core network connectivity.
SNMP MIB module
SNMP MIB module
The JUNIPER-MOBILE-GATEWAY-SGW-GTP-MIB module enables monitoring of GTP (GPRS Tunneling Protocol) session states and traffic counters on Juniper Mobile Gateway Serving Gateways (SGW). It provides specific objects for tracking GTP-C and GTP-U tunnel establishment, teardown, and packet throughput metrics essential for validating mobile core network connectivity.
The JUNIPER-IPSEC-FLOW-MON-MIB monitors Juniper Networks IPsec VPN infrastructure by exposing tables for IKE tunnels, IPSec tunnels, and IPSec security associations to track tunnel states, association parameters, and flow statistics. This module facilitates the management of IPsec security policies and the operational status of encrypted traffic flows within the device's security architecture.