All MIBs › Juniper-COPS-MIB
Organization: Juniper Networks, Inc.
Last Updated: 2002-09-16
Category: Vendor: Juniper
Description: Provides managed objects for COPS protocol sessions and policy management on Juniper Networks E-series broadband 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-COPS-MIB?
Juniper-COPS-MIB is a Juniper Networks MIB module for the Common Open Policy Service (COPS) protocol, used for centralized policy management on Juniper's E-series broadband routers (formerly Unisphere/Erx platforms). It exposes both cumulative protocol performance counters (sessions created/deleted, bytes and packets sent/received, keepalives sent/received) and a per-session table describing individual COPS client sessions. Its monitoring value lies in software/protocol performance and session-status tracking: administrators can watch session churn, current active session counts, and keepalive activity to detect a failing or flapping connection to the COPS policy server, which would otherwise silently degrade policy-based QoS or subscriber management. It is built on the IETF COPS protocol standard (RFC 2748) as its functional basis. It is deployed on Juniper E-series broadband edge routers used by service providers for policy-controlled subscriber and QoS management. Engineers can download the Juniper-COPS-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in Juniper-COPS-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 E-series broadband router
Monitoring Examples
An administrator would poll juniCopsProtocolCurrentSessions alongside juniCopsProtocolSessionsCreated and juniCopsProtocolSessionsDeleted to see whether COPS sessions are churning excessively rather than remaining stable. Walking juniCopsProtocolSessionTable/juniCopsProtocolSessionEntry and checking juniCopsProtocolSessionClientType per session identifies which policy client types are connected. A drop in juniCopsProtocolKeepAlivesReceived relative to juniCopsProtocolKeepAlivesSent, combined with rising juniCopsProtocolSessionsDeleted, would reveal a failing or unresponsive COPS policy server connection.
What Can Be Monitored
- current COPS sessions
- COPS sessions created/deleted
- COPS bytes/packets sent and received
- COPS keepalives sent/received
- per-session client type
Imported Objects
From Juniper-MIBs
| juniMibs | MODULE-IDENTITY |
From Juniper-TC
| JuniName |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Counter32 | |
| Integer32 | |
| IpAddress | |
| MODULE-IDENTITY | |
| OBJECT-TYPE |
How to Use in IPNetwork Monitor
Example using juniCopsProtocolSessionsCreated OID:
OIDs
RFC description
Manages Common Open Policy Service protocol sessions and statistics on Juniper Networks routers.
Start monitoring Juniper Networks E-series broadband router (COPS policy sessions) 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.