JUNIPER-DCU-MIB

All MIBs › JUNIPER-DCU-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2003-07-18

Category: Quality of Service, Technology: QoS, Vendor: Juniper

Description: Provides management objects for Destination Class Usage (DCU) accounting and traffic classification on Juniper Networks routing platforms.

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 JUNIPER-DCU-MIB?

JUNIPER-DCU-MIB is a Juniper Networks enterprise MIB implementing Destination Class Usage (DCU) accounting, a traffic-classification feature that tallies traffic volumes destined to particular route/class groupings, commonly used for billing or traffic-engineering analysis. It exposes counters of packets/bytes per destination class as configured on the router, giving visibility into how outbound traffic is distributed across classified destinations. Its monitoring role is performance/traffic-accounting rather than hardware health: administrators use it to track bandwidth consumption per class for capacity planning or billing verification rather than checking device sensors. It is a Juniper-specific enterprise MIB with no dependency on standard interface MIBs beyond referencing the classification configured via Juniper's routing policy language. Typical deployment is service-provider or large enterprise routers where per-destination traffic accounting is required for billing or capacity analysis, and administrators can inspect its object tree using a JUNIPER-DCU-MIB MIB Browser before deployment.

IPNetwork Monitor allows you to monitor SNMP objects defined in JUNIPER-DCU-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

Juniper router (DCU-capable routing platform)

Monitoring Examples

An administrator would poll the per-destination-class byte/packet counters to detect a class whose traffic volume has spiked unexpectedly, which could indicate a routing policy misconfiguration or a billing anomaly. No sample objects were extracted for this module, so exact table/column names are unconfirmed, but the module description confirms its scope is destination-class traffic counters. This MIB is primarily a traffic-accounting tool rather than a fault or hardware-status MIB.

What Can Be Monitored

destination class traffic bytes
destination class packet counts
traffic distribution per class
billing/accounting counters

Imported Objects

From IF-MIB

InterfaceIndex

From JUNIPER-SMI

jnxMibs

OBJECT-IDENTITY

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-SMI

Counter64
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString

How to Use in IPNetwork Monitor

Example using jnxDcuStatsPackets OID:

Select a Juniper Networks router (Destination Class Usage traffic accounting) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type jnxDcuStatsPackets into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of packets received on this interface, belonging to this address family that match this Destination Class. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter64-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
jnxDCUs	1.3.6.1.4.1.2636.3.6			This is Juniper Networks' implementation of enterprise specific MIB for Destination Class Usage (DCU)
jnxDCUsTable	1.3.6.1.4.1.2636.3.6.1		not-accessible	A list of DCUs entries.
jnxDCUsEntry	1.3.6.1.4.1.2636.3.6.1.1		not-accessible	An entry of DCUs table.
NUM jnxDCUSrcIfIndex	1.3.6.1.4.1.2636.3.6.1.1.1	InterfaceIndex	read-only	The source interface index. This is the ifIndex that the traffic is coming from and the statistics is counted for the specified DCU entry.
STR jnxDCUDstClassName	1.3.6.1.4.1.2636.3.6.1.1.2	DisplayString	read-only	The name of the destination class. This is the name of a valid configuration group defining a set of IP addresses and/or prefixes.
C64 jnxDCUPackets	1.3.6.1.4.1.2636.3.6.1.1.3	Counter64	read-only	The number of packets being counted pertaining to the specified DCU entry.
C64 jnxDCUBytes	1.3.6.1.4.1.2636.3.6.1.1.4	Counter64	read-only	The number of bytes being counted pertaining to the specified DCU entry.
jnxDcuStatsTable	1.3.6.1.4.1.2636.3.6.2		not-accessible	This table contains statistics for traffic that satisfies the rules in each configured Destination Class. A separate set of statistics are kept for each Destination Class on each interface and address family on which this feature is enabled.
jnxDcuStatsEntry	1.3.6.1.4.1.2636.3.6.2.1		not-accessible	Each entry in this table contains a set of statistics for all traffic received on a specific interface and belonging to a specific address family that matches a specific Destination Class.
NUM jnxDcuStatsSrcIfIndex	1.3.6.1.4.1.2636.3.6.2.1.1	InterfaceIndex	not-accessible	The ifIndex of the ingress interface for traffic counted in this entry.
INT jnxDcuStatsAddrFamily	1.3.6.1.4.1.2636.3.6.2.1.2	INTEGER	not-accessible	The address family of this entry's traffic.
STR jnxDcuStatsClassName	1.3.6.1.4.1.2636.3.6.2.1.3	SnmpAdminString	not-accessible	The name of the destination class.
C64 jnxDcuStatsPacketsEx	1.3.6.1.4.1.2636.3.6.2.1.4	Counter64	read-only	The number of packets received on this interface, belonging to this address family that match this Destination Class.
C64 jnxDcuStatsBytes	1.3.6.1.4.1.2636.3.6.2.1.5	Counter64	read-only	The number of bytes received on this interface, belonging to this address family that match this Destination Class.
STR jnxDcuStatsClName	1.3.6.1.4.1.2636.3.6.2.1.6	SnmpAdminString	read-only	The name of the destination class. This object is a duplicate of jnxDcuStatsClassName and is included to satisfy those NM applications that can't extract the name from the instance portion of the OID.

RFC description

Juniper Destination Class Usage (DCU) MIB for monitoring per-interface and per-address-family traffic statistics by destination class.

Start monitoring Juniper Networks router (Destination Class Usage traffic accounting) 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 JUNIPER-DCU-MIB