TN-ENTITY-SENSOR-MIB
The TN-ENTITY-SENSOR-MIB provides SNMP-based monitoring of physical power supply units and cooling fan modules within TN equipment, exposing operational status, health states, and sensor telemetry for these critical infrastructure components.
Imported Objects
Objects
23 total| Object Name |
|---|
tnEntitySensorMIBThe mib module for managing all powersupply and fan modules. MODULE-IDENTITY .1.3.6.1.4.1.868.2.5.6 |
tnEntitySensorMIBNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.6.0 |
tnEntSensorThresholdNotificationThe sensor value crossed the threshold listed in tnEntSensorThresholdTable. This notification is generated once each time the sensor value crosses the threshold. The agent implementation guarantees prompt, timely evaluation of threshold and generation of this notification. NOTIFICATION-TYPE .1.3.6.1.4.1.868.2.5.6.0.1 |
tnEntitySensorMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.6.1 |
tnEntSensorValues OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.6.1.1 |
tnEntSensorExtTableThis table is an private extension of the public ENTITY-SENSOR-MIB entPhySensorTable. SEQUENCE OF TnEntSensorExtEntry .1.3.6.1.4.1.868.2.5.6.1.1.1 |
tnEntSensorExtEntryThe entries list the unique properties of the ION Power supply module. TnEntSensorExtEntry .1.3.6.1.4.1.868.2.5.6.1.1.1.1 |
tnEntSensorExtRelayInstalledThis variable indicates if the relay contact is installed on the power supply module or not.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.6.1.1.1.1.1 |
tnEntSensorExtRelayEnabledThis variable enables or disables the relay contact if it is installed (tnEntSensorExtRelayInstalled) in the power supply. This relay contact is used to trigger an event to the user by attaching an external indicator.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.6.1.1.1.1.2 |
tnEntSensorExtModuleTypeThis variable indicates if the power supply is AC or DC module.ro Enumeration .1.3.6.1.4.1.868.2.5.6.1.1.1.1.3 |
tnEntSensorExtOperModeThis variable indicates operational mode of the power supply when redundant modules exists.ro Enumeration .1.3.6.1.4.1.868.2.5.6.1.1.1.1.4 |
tnEntSensorThresholds OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.6.1.2 |
tnEntSensorThresholdTableThis table lists the threshold severity, relation, and comparison value, for a sensor listed in the Entity-MIB EntPhysicalTable. SEQUENCE OF TnEntSensorThresholdEntry .1.3.6.1.4.1.868.2.5.6.1.2.1 |
tnEntSensorThresholdEntryAn tnEntSensorThresholdTable Entry describes the thresholds for a sensor: the threshold severity, the threshold value, the relation, and the evaluation of the threshold. Only Entities of type sensor(8) are listed in this table. Only pre-configured thresholds are listed in this table. Users can create sensor-value monitoring instrumionEnts in differionEnt ways, such as RMON alarms, Expression-MIB, etc. Entries are created by the agionEnt at system startup and FRU insertion. Entries are deleted by the agionEnt at FRU removal. TnEntSensorThresholdEntry .1.3.6.1.4.1.868.2.5.6.1.2.1.1 |
tnEntSensorThresholdIndexAn index that uniquely identifies an entry in the tnEntSensorThresholdTable. This index permits the same sensor to have several different thresholds. Integer32 .1.3.6.1.4.1.868.2.5.6.1.2.1.1.1 |
tnEntSensorThresholdSeverityThis variable indicates the severity of this threshold.rw TnSensorThresholdSeverity .1.3.6.1.4.1.868.2.5.6.1.2.1.1.2 |
tnEntSensorThresholdRelationThis variable indicates the relation between sensor value (entSensorValue) and threshold value (tnEntSensorThresholdValue), required to trigger the alarm. when evaluating the relation, entSensorValue is on the left of tnEntSensorThresholdRelation, tnEntSensorThresholdValue is on the right. in pseudo-code, the evaluation-alarm mechanism is: ... if (entSensorStatus == ok) then if (evaluate(entSensorValue, tnEntSensorThresholdRelation, tnEntSensorThresholdValue)) then if (tnEntSensorThresholdNotificationEnable == true)) then raise_alarm(sensor's entPhysicalIndex); endif endif endif ...rw TnSensorThresholdRelation .1.3.6.1.4.1.868.2.5.6.1.2.1.1.3 |
tnEntSensorThresholdValueThis variable indicates the value of the threshold. To correctly display or interpret this variable's value, you must also know entSensorType, entSensorScale, and entSensorPrecision. However, you can directly compare entSensorValue with the threshold values given in tnEntSensorThresholdTable without any semantic knowledge.rw EntitySensorValue (ENTITY-SENSOR-MIB) .1.3.6.1.4.1.868.2.5.6.1.2.1.1.4 |
tnEntSensorThresholdEvaluationThis variable indicates the result of the most recent evaluation of the threshold. If the threshold condition is true, tnEntSensorThresholdEvaluation is true(1). If the threshold condition is false, tnEntSensorThresholdEvaluation is false(2). Thresholds are evaluated at the rate indicated by entSensorValueUpdateRate.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.6.1.2.1.1.5 |
tnEntSensorThresholdNotificationEnableThis variable controls generation of tnEntSensorThresholdNotification for this threshold. When this variable is 'true', generation of tnEntSensorThresholdNotification is enabled for this threshold. When this variable is 'false', generation of tnEntSensorThresholdNotification is disabled for this threshold.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.6.1.2.1.1.6 |
tnEntSensorGlobalObjects OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.6.1.3 |
tnEntSensorThreshNotifGlobalEnableThis variable enables the generation of tnEntSensorThresholdNotification globally on the device. If this object value is 'false', then no tnEntSensorThresholdNotification will be generated on this device. If this object value is 'true', then whether a tnEntSensorThresholdNotification for a threshold will be generated or not depends on the instance value of tnEntSensorThresholdNotificationEnable for that threshold.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.6.1.3.1 |
tnEntitySensorMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.6.2 |
More MIBs from Transition
Browse all TransitionMIBs →SNMP MIB module
The TN-MPLS-MIB module enables the monitoring and configuration of Multiprotocol Label Switching (MPLS) parameters, including label bindings, forwarding equivalence classes, and tunnel states, on Nokia (formerly Alcatel-Lucent) Service Router and IP/MPLS network devices.
Standard SNMP MIB module defining data structures for TNI-MIB.
The TN-CES-MIB module enables monitoring and management of Circuit Emulation Service (CES) sessions on network equipment, specifically tracking performance metrics such as session status, packet loss, jitter, and synchronization errors for T1/E1 circuit emulation over packet-switched networks.
The TN-LLDP-MIB module enables monitoring and management of Link Layer Discovery Protocol (LLDP) neighbor discovery data, including system identification, port descriptions, and TLV (Type-Length-Value) attributes, on Trellix (formerly McAfee) network infrastructure devices. This private MIB extension facilitates the collection of LLDP session states and neighbor topology information for network inventory and connectivity verification.
The TN-DHCP-SERVER-MIB enables monitoring and management of Dynamic Host Configuration Protocol server configurations, lease states, and address pool utilization on Tanaza network infrastructure devices. This module provides visibility into DHCP scope assignments, client binding tables, and server operational status to facilitate network address administration.