H3C-RDDC-MIB
The H3C-RDDC-MIB module monitors and manages Redundancy Group (RDDC) states within H3C IRF (Intelligent Resilient Framework) environments to track node failover status and ensure control plane continuity during group-node failures. It provides specific objects for verifying the operational state of active and standby IRF members to confirm minimal service interruption during redundancy transitions.
Imported Objects
Objects
27 total| Object Name |
|---|
h3cRddcRedundancy group is concerned with ensuring minimal disruption to data and control planes in case of a failover. If one of the group-node in an IRF fails, the other group-node in the IRF takes over the function of the failed group-node with minimal service interruption. This module defines the objects pertaining to redundancy group(RDDC). MODULE-IDENTITY .1.3.6.1.4.1.2011.10.2.151 |
h3cRddcNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.151.0 |
h3cRddcSwitchoverTrapNotification to signal switchover/failover. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.151.0.1 |
h3cRddcFailIfRecoverTrapNotification to signal the failed interface recovered. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.151.0.2 |
h3cRddcFailIfGenerateTrapNotification to signal the failed interface generated. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.151.0.3 |
h3cRddcObjects OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.151.1 |
h3cRddcInfo OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.151.1.1 |
h3cRddcTableThis table describes the current status of redundancy groups. SEQUENCE OF H3cRddcEntry .1.3.6.1.4.1.2011.10.2.151.1.1.1 |
h3cRddcEntryThe entry of h3cRddcEntry. H3cRddcEntry .1.3.6.1.4.1.2011.10.2.151.1.1.1.1 |
h3cRddcGroupIdxUnique identifier of this redundancy group. 0 is an invalid value.ro Unsigned32 .1.3.6.1.4.1.2011.10.2.151.1.1.1.1.1 |
h3cRddcGroupNameUnique identifier of this redundancy group.ro OCTET STRING .1.3.6.1.4.1.2011.10.2.151.1.1.1.1.2 |
h3cRddcPreempTimeRemainThe redundancy group should not switch back immediately when a failover is recovered. The preempt delay timer is started for waiting the failover became believable. This object contains the current preempt delay time remained when a failover is recovered.ro Unsigned32 UNITS "minutes" .1.3.6.1.4.1.2011.10.2.151.1.1.1.1.3 |
h3cRddcPreempTimeConfigThe current preempt delay time.ro Unsigned32 UNITS "minutes" .1.3.6.1.4.1.2011.10.2.151.1.1.1.1.4 |
h3cRddcHoldTimeRemainTo prevent frequent switchovers of the redundancy group, the hold-down timer started to keeping in a state for a fixed time. This object contains the current remained hold-down time when a switchover or a failover recovery occurred.ro Unsigned32 UNITS "seconds" .1.3.6.1.4.1.2011.10.2.151.1.1.1.1.5 |
h3cRddcHoldTimeConfigThe current hold-down time.ro Unsigned32 UNITS "seconds" .1.3.6.1.4.1.2011.10.2.151.1.1.1.1.6 |
h3cRddcNodeTableThis table describes the current status of a redundancy group node. SEQUENCE OF H3cRddcNodeEntry .1.3.6.1.4.1.2011.10.2.151.1.1.2 |
h3cRddcNodeEntryThe entry of h3cRddcNodeEntry. H3cRddcNodeEntry .1.3.6.1.4.1.2011.10.2.151.1.1.2.1 |
h3cRddcNodeGroupIdxUnique identifier of this redundancy group. 0 is an invalid value. Unsigned32 .1.3.6.1.4.1.2011.10.2.151.1.1.2.1.1 |
h3cRddcNodeIdUnique identifier of this redundancy group node. 0 is an invalid value. Unsigned32 .1.3.6.1.4.1.2011.10.2.151.1.1.2.1.2 |
h3cRddcNodeBindTypeThe bind type of this redundancy group node. The current version only supports binding chassis of an IRF device.ro Enumeration .1.3.6.1.4.1.2011.10.2.151.1.1.2.1.3 |
h3cRddcNodeBindInfoThe bind information of this redundancy group node. The current version only supports binding chassis of an IRF device. If the value of h3cRddcNodeBindType is invalid, the value of h3cRddcNodeBindInfo is 65535.ro Unsigned32 .1.3.6.1.4.1.2011.10.2.151.1.1.2.1.4 |
h3cRddcNodePriorityThe priority of this redundancy group node. The higher the value, the greater the priority.ro Unsigned32 .1.3.6.1.4.1.2011.10.2.151.1.1.2.1.5 |
h3cRddcNodeWeightThe current weight of this redundancy group node. The max value is 255.ro Integer32 .1.3.6.1.4.1.2011.10.2.151.1.1.2.1.6 |
h3cRddcNodeStatusThe current status of this redundancy group node.ro Enumeration .1.3.6.1.4.1.2011.10.2.151.1.1.2.1.7 |
h3cRddcTrapObjects OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.151.1.2 |
h3cRddcNodeInfoThis object contains node identification information where the switchover occurred.ro DisplayString .1.3.6.1.4.1.2011.10.2.151.1.2.1 |
h3cRddcSwitchReasonThis object contains the cause for switchover.ro DisplayString .1.3.6.1.4.1.2011.10.2.151.1.2.2 |
More MIBs from Huawei
Browse all HuaweiMIBs →The HUAWEI-MIB module provides a unified namespace for monitoring and managing generic system resources, interface statistics, and hardware telemetry across Huawei network devices. It serves as the foundational OID repository for retrieving standard operational data, including CPU utilization, memory usage, interface counters, and device status, required for comprehensive network management via SNMP.
Standard SNMP MIB module defining data structures for HUAWEI-SERVER-IBMC-MIB.
The HUAWEI-XPON-MIB module enables Network Management Systems to monitor and configure GPON and EPON optical line terminals and optical network units, specifically tracking PON port status, optical power levels, bandwidth allocation, and subscriber session states.
SNMP MIB module
The HUAWEI-WLAN-CONFIGURATION-MIB facilitates the configuration and monitoring of Huawei Wireless LAN access point parameters, specifically managing AP port link profiles and broadcast suppression settings. This module enables administrators to enforce traffic control policies and optimize wireless network performance by adjusting switch profile associations and limiting broadcast traffic on specific ports.
The HUAWEI-XQoS-MIB enables configuration and real-time monitoring of Class Based QoS parameters on Huawei network devices, specifically tracking traffic classification rules, queue states, and policy enforcement metrics. This module facilitates granular control over bandwidth allocation and packet prioritization by exposing objects for policy definitions, interface queue depths, and dropped packet counters associated with QoS classes.