CIENA-CES-DATAPLANE-MIB :: cienaCesDpQosFlowIngressMeterPolicy

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCIENA-CES-DATAPLANE-MIBcienaCesDpQosFlowIngressMeterPolicy

cienaCesDpQosFlowIngressMeterPolicy

Module: CIENA-CES-DATAPLANE-MIB

OID (symbolic): CIENA-CES-DATAPLANE-MIB::cienaCesDpQosFlowIngressMeterPolicy

OID (numeric): 1.3.6.1.4.1.1271.2.1.7.1.9.1.1.8

Node type: OBJECT-TYPE

Type: DpIngressMeterPolicy

Access: read-only

Description: This object specifies the ingress meter policy.

The ingress meter policy has no effect when there is no meter profile

attached to this QoS flow..

- Non-Hierarchical: Denotes that frames which classify to the Meter

instantiated via an attached Meter Profile will be Metered according

to the bandwidth parameters of the attached Meter Profile.

The resultant colour of the frame will be determined by the

single meter instance of the logical interface. The frame is

processed by a single ingress meter. Resultant Red frames

are dropped.

- Hierarchical: Denotes that frames which classify to the Meter

instantiated via an attached Meter Profile will first be Metered

according to the bandwidth parameters of the attached Meter Profile,

then subsequently those frames will be Metered according to the

bandwidth parameters of the first parent logical interface (identifie d

by the object cienaCesDpQosFlowParentIfType) that has a

Meter Profile attached. If no parent logical interface

has an attached ingress meter profile, the behavior for frames

which classify to the logical interface is the same as the

Non-Hierarchical policy. The resultant colour of frames that

are metered by the attached meter profile are fed into the parent

meter. If the resultant color of a frame is Red after being

processed by a meter at any hierarchical level, the frame is

dropped and not fed into a parent meter.

What is cienaCesDpQosFlowIngressMeterPolicy?

This DpIngressMeterPolicy decides whether this QoS flow's metering is independent or draws hierarchically from a shared parent budget. It matters when several QoS flows carved out of the same sub-port, for example separate flows for signaling versus bulk data, need to collectively respect one overall CIR ceiling rather than each getting a fully independent allowance. Setting a hierarchical policy, for example, lets a signaling flow and a bulk-data flow on the same customer's sub-port share one parent CIR pool rather than each drawing an independent full allocation.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1271.2.1.7.1.9.1.1.8
snmpwalk -v2c -c public <target> CIENA-CES-DATAPLANE-MIB::cienaCesDpQosFlowIngressMeterPolicy

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1271.2.1.7.1.9.1.1.8.1
snmpget -v2c -c public <target> CIENA-CES-DATAPLANE-MIB::cienaCesDpQosFlowIngressMeterPolicy.1

Start monitoring Ciena CN5410 Carrier Ethernet Switch with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CIENA-CES-DATAPLANE-MIB::cienaCesDpQosFlowIngressMeterPolicy OID value, configure state conditions and alerts, and monitor any Ciena CN5410 Carrier Ethernet Switch from a single console.

OID Breakdown

Upper-level ancestors (9 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.1271cienaCIENA-SMI
1.3.6.1.4.1.1271.2cienaCesCIENA-SMI
1.3.6.1.4.1.1271.2.1cienaCesConfigCIENA-SMI
Numeric OIDNameModule
1.3.6.1.4.1.1271.2.1.7cienaCesDataplaneMIBCIENA-CES-DATAPLANE-MIB
1.3.6.1.4.1.1271.2.1.7.1cienaCesDpMIBObjectsCIENA-CES-DATAPLANE-MIB
1.3.6.1.4.1.1271.2.1.7.1.9cienaCesDpQosFlowCIENA-CES-DATAPLANE-MIB
1.3.6.1.4.1.1271.2.1.7.1.9.1cienaCesDpQosFlowTableCIENA-CES-DATAPLANE-MIB
1.3.6.1.4.1.1271.2.1.7.1.9.1.1cienaCesDpQosFlowEntryCIENA-CES-DATAPLANE-MIB
1.3.6.1.4.1.1271.2.1.7.1.9.1.1.8cienaCesDpQosFlowIngressMeterPolicyCIENA-CES-DATAPLANE-MIB