This MIB module defines a set of objects for monitoring batteries of networked devices and of their components. Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this MIB module is part of RFC 7577; see the RFC itself for full legal notices. |
entPhysicalIndex | ENTITY-MIB |
SnmpAdminString | SNMP-FRAMEWORK-MIB |
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP | SNMPv2-CONF |
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, Integer32, Unsigned32 | SNMPv2-SMI |
DateAndTime | SNMPv2-TC |
![]() | .1.3.6.1.2.1.233 | |
![]() | .1.3.6.1.2.1.233.0 | |
![]() | .1.3.6.1.2.1.233.1 | |
![]() | .1.3.6.1.2.1.233.1.1 | |
![]() | .1.3.6.1.2.1.233.1.1.1 | |
![]() | .1.3.6.1.2.1.233.1.1.1.1 | |
![]() | .1.3.6.1.2.1.233.1.1.1.10 | |
![]() | .1.3.6.1.2.1.233.1.1.1.11 | |
![]() | .1.3.6.1.2.1.233.1.1.1.12 | |
![]() | .1.3.6.1.2.1.233.1.1.1.13 | |
![]() | .1.3.6.1.2.1.233.1.1.1.14 | |
![]() | .1.3.6.1.2.1.233.1.1.1.15 | |
![]() | .1.3.6.1.2.1.233.1.1.1.16 | |
![]() | .1.3.6.1.2.1.233.1.1.1.17 | |
![]() | .1.3.6.1.2.1.233.1.1.1.18 | |
![]() | .1.3.6.1.2.1.233.1.1.1.19 | |
![]() | .1.3.6.1.2.1.233.1.1.1.2 | |
![]() | .1.3.6.1.2.1.233.1.1.1.20 | |
![]() | .1.3.6.1.2.1.233.1.1.1.21 | |
![]() | .1.3.6.1.2.1.233.1.1.1.22 | |
![]() | .1.3.6.1.2.1.233.1.1.1.23 | |
![]() | .1.3.6.1.2.1.233.1.1.1.24 | |
![]() | .1.3.6.1.2.1.233.1.1.1.25 | |
![]() | .1.3.6.1.2.1.233.1.1.1.3 | |
![]() | .1.3.6.1.2.1.233.1.1.1.4 | |
![]() | .1.3.6.1.2.1.233.1.1.1.5 | |
![]() | .1.3.6.1.2.1.233.1.1.1.6 | |
![]() | .1.3.6.1.2.1.233.1.1.1.7 | |
![]() | .1.3.6.1.2.1.233.1.1.1.8 | |
![]() | .1.3.6.1.2.1.233.1.1.1.9 | |
![]() | .1.3.6.1.2.1.233.2 | |
![]() | .1.3.6.1.2.1.233.2.1 | |
![]() | .1.3.6.1.2.1.233.2.2 |
Name | OID | Description |
---|---|---|
.1.3.6.1.2.1.233.0.1 | ication can be generated when a charging state of the battery (indicated by the value of object batteryChargingOperState) is triggered by an event other than a write action to object batteryChargingAdminState. Such an event may, for example, be triggered by a local battery controller. | |
.1.3.6.1.2.1.233.0.2 | ication can be generated when the current charge (batteryActualCharge) or the current voltage (batteryActualVoltage) of the battery falls below a threshold defined by object batteryAlarmLowCharge or object batteryAlarmLowVoltage, respectively. Note that, typically, this notification is generated in a state where the battery is still sufficiently charged to keep the device(s) that it powers operational for some time. If the charging state of the battery has become critical, i.e., the device(s) powered by the battery must go to a 'sleep' or 'off' state, then the batteryCriticalNotification should be used instead. If the low charge or voltage has been detected for a single cell or a set of cells of the battery and not for the entire battery, then object batteryCellIdentifier should be set to a value that identifies the cell or set of cells. Otherwise, the value of object batteryCellIdentifier should be set to the empty string when this notification is generated. The notification should not be sent again for the same battery or cell before either (a) the current voltage or the current charge, respectively, has become higher than the corresponding threshold through charging or (b) an indication of a maintenance action has been detected, such as a battery disconnection event or a reinitialization of the battery monitoring system. This notification should not be sent when the battery is in a charging mode, i.e., the value of object batteryChargingOperState is charging(2). | |
.1.3.6.1.2.1.233.0.3 | ication can be generated when the current charge of the battery falls so low that it cannot provide a sufficient power supply function for regular operation of the powered device(s). The battery needs to be charged before it can be used for regular power supply again. The battery may still provide sufficient power for a 'sleep' mode of a powered device(s) or for a transition into an 'off' mode. If the critical state is caused by a single cell or a set of cells of the battery, then object batteryCellIdentifier should be set to a value that identifies the cell or set of cells. Otherwise, the value of object batteryCellIdentifier should be set to the empty string when this notification is generated. The notification should not be sent again for the same battery before either the battery charge has increased through charging to a non-critical value or an indication of a maintenance action has been detected, such as a battery disconnection event or a reinitialization of the battery monitoring system. This notification should not be sent when the battery is in a charging mode, i.e., the value of object batteryChargingOperState is charging(2). | |
.1.3.6.1.2.1.233.0.4 | ication can be generated when the measured temperature (batteryTemperature) rises above the threshold defined by object batteryAlarmHighTemperature or falls below the threshold defined by object batteryAlarmLowTemperature. If the low or high temperature has been detected for a single cell or a set of cells of the battery and not for the entire battery, then object batteryCellIdentifier should be set to a value that identifies the cell or set of cells. Otherwise, the value of object batteryCellIdentifier should be set to the empty string when this notification is generated. It may occur that the temperature alternates between values slightly below and slightly above a threshold. For limiting the notification rate in such a case, this notification should not be sent again for the same battery or cell, respectively, within a time interval of 10 minutes. An exception to the rate limitations occurs immediately after the reinitialization of the battery monitoring system. At this point in time, if the battery temperature is above the threshold defined by object batteryAlarmHighTemperature or below the threshold defined by object batteryAlarmLowTemperature, respectively, then this notification should be sent, independent of the time at which previous notifications for the same battery or cell, respectively, had been sent. | |
.1.3.6.1.2.1.233.0.5 | ication can be generated when the actual capacity (batteryActualCapacity) falls below a threshold defined by object batteryAlarmLowCapacity or when the charging cycle count of the battery (batteryChargingCycleCount) exceeds the threshold defined by object batteryAlarmHighCycleCount. If the aging has been detected for a single cell or a set of cells of the battery and not for the entire battery, then object batteryCellIdentifier should be set to a value that identifies the cell or set of cells. Otherwise, the value of object batteryCellIdentifier should be set to the empty string when this notification is generated. This notification should not be sent again for the same battery or cell, respectively, before an indication of a maintenance action has been detected, such as a battery disconnection event or a reinitialization of the battery monitoring system. | |
.1.3.6.1.2.1.233.0.6 | ication can be generated when it has been detected that a battery has been connected. The battery can be identified by the value of object batteryIdentifier as well as by the value of index entPhysicalIndex that is contained in the OID of object batteryIdentifier. | |
.1.3.6.1.2.1.233.0.7 | ication can be generated when it has been detected that one or more batteries have been disconnected. |