JUNIPER-DFC-MIB :: jnxDfcCSControlProtocolAddRequests

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsJUNIPER-DFC-MIBjnxDfcCSControlProtocolAddRequests

jnxDfcCSControlProtocolAddRequests

Module: JUNIPER-DFC-MIB

OID (symbolic): JUNIPER-DFC-MIB::jnxDfcCSControlProtocolAddRequests

OID (numeric): 1.3.6.1.4.1.2636.3.33.1.1.3

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: Total number of Control protocol Add requests received. The add request specifies a new filter criteria to be merged with the existing tasking list for a given Control Source and Content Destination.

What is jnxDfcCSControlProtocolAddRequests?

Counts total Control-protocol Add requests received from a Dynamic Flow Capture (DFC) Control Source, each specifying new filter criteria to merge into that source's tasking list for a given Content Destination. Admins watch this alongside jnxDfcCSCriteriaAdded and jnxDfcCSCriteriaAdditionFailed to see how many add attempts a control source is issuing and how many succeed.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2636.3.33.1.1.3
snmpwalk -v2c -c public <target> JUNIPER-DFC-MIB::jnxDfcCSControlProtocolAddRequests

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2636.3.33.1.1.3.1
snmpget -v2c -c public <target> JUNIPER-DFC-MIB::jnxDfcCSControlProtocolAddRequests.1

Start monitoring Juniper Networks router (Dynamic Flow Capture, lawful intercept/forensics) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the JUNIPER-DFC-MIB::jnxDfcCSControlProtocolAddRequests OID value, configure state conditions and alerts, and monitor any Juniper Networks router (Dynamic Flow Capture, lawful intercept/forensics) from a single console.

How to Use in IPNetwork Monitor

Select a Juniper Networks router (Dynamic Flow Capture, lawful intercept/forensics) 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 jnxDfcCSControlProtocolAddRequests 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. It reports the total number of Control protocol Add requests received. 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.

OID Breakdown

Upper-level ancestors (8 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.2636juniperMIBJUNIPER-SMI
1.3.6.1.4.1.2636.3jnxMibsJUNIPER-SMI
Numeric OIDNameModule
1.3.6.1.4.1.2636.3.33jnxDfcJUNIPER-DFC-MIB
1.3.6.1.4.1.2636.3.33.1jnxDfcCSTableJUNIPER-DFC-MIB
1.3.6.1.4.1.2636.3.33.1.1jnxDfcCSEntryJUNIPER-DFC-MIB
1.3.6.1.4.1.2636.3.33.1.1.3jnxDfcCSControlProtocolAddRequestsJUNIPER-DFC-MIB