JUNIPER-SCU-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › JUNIPER-SCU-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2003-07-18

Category: Vendor: Juniper

Description: Juniper Networks MIB for monitoring Source Class Usage (SCU) statistics for traffic classification accounting on Juniper routers.

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-SCU-MIB?

JUNIPER-SCU-MIB is Juniper Networks' enterprise-specific MIB for Source Class Usage (SCU), a traffic-classification accounting feature used to tally traffic volumes matched against configured source-class policies, commonly used for peering/transit traffic accounting or billing. It exposes traffic counters broken out by source class rather than general device health data. Its monitoring role falls in the performance-counter category: byte and packet counts per source class reveal traffic volume trends and can flag unexpected shifts in traffic mix or a misconfigured classification policy rather than any physical hardware condition. It complements Juniper's policy/firewall-filter configuration and relies on standard interface indexing conventions akin to IF-MIB when associating counters with a physical interface. It is deployed on Juniper M/MX/T-series routers used in service-provider peering and transit environments where per-source-class traffic accounting matters. Engineers can download the JUNIPER-SCU-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in JUNIPER-SCU-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 Networks router (M/MX/T series)

Monitoring Examples

No sample objects were provided for this module, so a concrete polling scenario with real object names cannot be constructed; consistent with its stated purpose, monitoring would involve polling per-source-class byte/packet counters on relevant interfaces to detect a sudden shift in traffic volume attributable to a particular classified source, useful for capacity planning or billing verification.

What Can Be Monitored

  • source class traffic byte counters
  • source class packet counters
  • per-interface source class accounting
Imported Objects

From IF-MIB

InterfaceIndex

From JUNIPER-SMI

jnxMibsOBJECT-IDENTITY

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-SMI

Counter64
MODULE-IDENTITY
OBJECT-TYPE

How to Use in IPNetwork Monitor

Example using jnxScuStatsPackets OID:

Select a Juniper Networks router, M/MX/T series (Source Class Usage 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 jnxScuStatsPackets 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 sent out of jnxScuStatsDstIfIndex that match the source class (jnxScuStatsClassName) and match the address type (jnxScuStatsAddrFamily) defined for this table entry. 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

RFC description

Juniper Networks Source Class Usage (SCU) statistics and traffic metrics for tracking egress interface packet and byte counts.

Start monitoring Juniper Networks router, M/MX/T series (Source Class Usage 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-SCU-MIB