HUAWEI-OLC-MIB

All MIBs › HUAWEI-OLC-MIB

Organization: Huawei Technologies Co.,Ltd.

Last Updated: 2012-06-27

Category: Domain: Optical Transport, Technology: Optical Transport, Vendor: Huawei

Description: Huawei OLC (Optical Line Controller) MIB for managing optical amplifier and line controller parameters in WDM systems.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is HUAWEI-OLC-MIB?

Despite its short description referencing an optical line controller, the module's own DESCRIPTION text indicates HUAWEI-OLC-MIB actually covers CPU Overload Control (OLC), a system-protection feature that maps traffic queues to priorities and applies leaky-bucket rate limiting to prevent management/control-plane traffic from overloading the device's CPU. It exposes configuration data for the queue-to-priority mapping and the leaky-bucket rate parameters used to throttle excess traffic. Its monitoring value is protective software/hardware status: verifying overload-control settings are correctly tuned indirectly safeguards CPU health, and any exposed drop/throttle counters would reveal active protection kicking in during a traffic burst. It is a standalone Huawei feature MIB not tied to an external standard. It is deployed on Huawei routers and switches where protecting the CPU from control-plane floods or management overload is a priority. Network engineers evaluating or troubleshooting this functionality can download the HUAWEI-OLC-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in HUAWEI-OLC-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Huawei routers
Huawei switches (CPU/control-plane protection feature)

Monitoring Examples

No sample object names were provided for this module. Based on the module's actual description (CPU overload control, not optical line control), an administrator would monitor the per-queue priority mapping and leaky-bucket rate/threshold configuration to verify overload protection is correctly limiting bursts of management or control traffic, and would check any exposed drop counters for signs of active throttling during high CPU load.

What Can Be Monitored

queue-to-priority mapping
leaky bucket rate limit configuration
CPU overload protection thresholds
queue drop/throttling activity

Imported Objects

From HUAWEI-MIB

huaweiUtility

OBJECT-IDENTITY

From SNMPv2-SMI

Counter32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

OIDs

OID symbolic	OID numeric	Type	Access	Description
hwOverLoadControl	1.3.6.1.4.1.2011.6.127			This MIB module provides certain configuration functions for the CPU overload control feature. The functions include the configuration of the mapping relation between the OLC queue and the priority, configuration and query of the attributes in the OLC queue, and configuration and query of the parameters of the system-level leaky bucket. The CPU overload control function is used for preventing the overuse of system resources of the device. This is to ensure that the interruption of all the service and the management failure of the NMS do not occur due to the overuse of CPU or other system resources.
hwOverLoadControlQueue	1.3.6.1.4.1.2011.6.127.1
U32 hwOverLoadControlCosQueueMappingMask	1.3.6.1.4.1.2011.6.127.1.1	Unsigned32	read-write	Indicate how the cos maps to the queue ID. Every four bits indicate the queue ID corresponding to one cos value. The range of the queue ID is from 0 to 7. bit value: bit31 bit0 0000 0000 0000 0000 0000 0000 0000 0000 cos value: cos7 cos6 cos5 cos4 cos3 cos2 cos1 cos0 DEFVAL { 1985229328 }
hwOverLoadControlQueueWeight	1.3.6.1.4.1.2011.6.127.1.2
U32 hwOverLoadControlQueue0Weight	1.3.6.1.4.1.2011.6.127.1.2.1	Unsigned32	read-write	The weight value of the 0th WRR queue. WRR (Weighted Round Robin) DEFVAL { 7 }
U32 hwOverLoadControlQueue1Weight	1.3.6.1.4.1.2011.6.127.1.2.2	Unsigned32	read-write	The weight value of the 1st WRR queue. WRR (Weighted Round Robin) DEFVAL { 8 }
U32 hwOverLoadControlQueue2Weight	1.3.6.1.4.1.2011.6.127.1.2.3	Unsigned32	read-write	The weight value of the 2nd WRR queue. WRR (Weighted Round Robin) DEFVAL { 9 }
U32 hwOverLoadControlQueue3Weight	1.3.6.1.4.1.2011.6.127.1.2.4	Unsigned32	read-write	The weight value of the 3rd WRR queue. WRR (Weighted Round Robin) DEFVAL { 10 }
U32 hwOverLoadControlQueue4Weight	1.3.6.1.4.1.2011.6.127.1.2.5	Unsigned32	read-write	The weight value of the 4th WRR queue. WRR (Weighted Round Robin) DEFVAL { 15 }
U32 hwOverLoadControlQueue5Weight	1.3.6.1.4.1.2011.6.127.1.2.6	Unsigned32	read-write	The weight value of the 5th WRR queue. WRR (Weighted Round Robin) DEFVAL { 16 }
U32 hwOverLoadControlQueue6Weight	1.3.6.1.4.1.2011.6.127.1.2.7	Unsigned32	read-write	The weight value of the 6th WRR queue. WRR (Weighted Round Robin) DEFVAL { 17 }
U32 hwOverLoadControlQueue7Weight	1.3.6.1.4.1.2011.6.127.1.2.8	Unsigned32	read-write	The weight value of the 7th WRR queue. WRR (Weighted Round Robin) DEFVAL { 18 }
hwOverLoadControlQueueParaTable	1.3.6.1.4.1.2011.6.127.1.3		not-accessible	Olc wrr queues parameter table. It is used for configuring and querying the number of messages of 0-7 OLC queues, and the counts of tail drops and queue back pressures. The index of this table is hwOverLoadControlQueueID.
hwOverLoadControlQueueParaEntry	1.3.6.1.4.1.2011.6.127.1.3.1		not-accessible	Olc wrr queues parameter table. It is used for configuring and querying the number of messages of 0-7 OLC queues, and the counts of tail drops and queue back pressures. The index of this entry is hwOverLoadControlQueueID.
U32 hwOverLoadControlQueueID	1.3.6.1.4.1.2011.6.127.1.3.1.1	Unsigned32	not-accessible	Olc wrr queue ID.
U32 hwOverLoadControlQueueMsgNum	1.3.6.1.4.1.2011.6.127.1.3.1.2	Unsigned32	read-only	The number of Olc wrr queue messages, the number of messages currently buffered in the queue.
C32 hwOverLoadControlQueueDiscardCount	1.3.6.1.4.1.2011.6.127.1.3.1.3	Counter32	read-only	Olc wrr queue discard-count, the count of messages discarded because the queue is full.
C32 hwOverLoadControlQueueSuppressCount	1.3.6.1.4.1.2011.6.127.1.3.1.4	Counter32	read-only	Olc queue suppression count, the count of queue suppressed because the system is busy.
hwOverLoadControlPara	1.3.6.1.4.1.2011.6.127.2
U32 hwOverLoadControlThreshold1	1.3.6.1.4.1.2011.6.127.2.1	Unsigned32	read-write	It indicates the level-1 threshold of the system-level leaky bucket. The overload control is implemented through the leak rate reduction, which starts when the CPU usage exceeds the level-1 threshold. DEFVAL { 80 }
U32 hwOverLoadControlThreshold2	1.3.6.1.4.1.2011.6.127.2.2	Unsigned32	read-write	It indicates the level-2 threshold of the system-level leaky bucket. When the CPU usage exceeds the level-2 threshold, the overload control is implemented according to the minimum traffic. The configured level-2 threshold of the system-level leaky bucket must be higher than the level-1 threshold of the system-level leaky bucket. DEFVAL { 90 }
U32 hwOverLoadControlAdjustFactor	1.3.6.1.4.1.2011.6.127.2.3	Unsigned32	read-write	Olc system leakbucket adjust factor, means how long(units:second) can CPU overload be controlled. DEFVAL { 20 }

RFC description

Manages CPU overload control features including queue priorities, weight configuration, and system-level leaky bucket parameters.

Start monitoring Huawei router or switch (CPU overload control/leaky-bucket protection) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download HUAWEI-OLC-MIB

What Is HUAWEI-OLC-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description