JUNIPER-DFC-MIB
Updated Jul 8, 2005This is Juniper Networks' implementation of enterprise specific MIB for Dynamic Flow Capture (DFC)
Main OID:
jnxDfc.1.3.6.1.4.1.2636.3.33
78
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
78 total| Object Name |
|---|
jnxDfcThis is Juniper Networks' implementation of enterprise
specific MIB for Dynamic Flow Capture (DFC) MODULE-IDENTITY .1.3.6.1.4.1.2636.3.33 |
jnxDfcCSTableStatistics information for Control Source. SEQUENCE OF JnxDfcCSEntry .1.3.6.1.4.1.2636.3.33.1 |
jnxDfcCSEntryAn entry of DFC Control Source table. JnxDfcCSEntry .1.3.6.1.4.1.2636.3.33.1.1 |
jnxDfcGrpNameThe name assigned to a DFC group. A DFC group defines a set of DFC
PICs that share same static/dynamic
configuration. DisplayString .1.3.6.1.4.1.2636.3.33.1.1.1 |
jnxDfcCSIdControl Source identifier. Control Source identifies Juniper router
with one unique Control IP address. There can be multiple IP
addresses from which a Control Source can send Control protocol
request to Juniper router. DisplayString .1.3.6.1.4.1.2636.3.33.1.1.2 |
jnxDfcCSControlProtocolAddRequestsTotal 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.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.3 |
jnxDfcCSCriteriaAddedTotal number of filter criteria added successfully by the Control
Source.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.4 |
jnxDfcCSCriteriaAdditionFailedTotal number of filter criteria addition failed.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.5 |
jnxDfcCSControlProtocolDeleteRequestsTotal number of Control protocol delete requests received. The
delete request removes a particular filter criterion.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.6 |
jnxDfcCSCriteriaDeletedTotal number of filter criteria deleted successfully as requested
by Control Source.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.7 |
jnxDfcCSCriteriaDeletionFailedTotal number of filter criteria deletion failed.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.8 |
jnxDfcCSCriteriaDeletedTimeoutIdleTotal number of criteria deleted by timeout idle.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.9 |
jnxDfcCSCriteriaDeletedTimeoutTotalTotal number of criteria deleted by timeout total.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.10 |
jnxDfcCSCriteriaDeletedPacketsTotal number of criteria deleted by packets.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.11 |
jnxDfcCSCriteriaDeletedBytesTotal number of criteria deleted by bytes.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.12 |
jnxDfcCSControlProtocolRefreshRequestsTotal number of Control protocol Refresh requests received. The
refresh request updates the timeout for a particular filter
criterion or set of filter criteria for the particular Control
Source to a particular Content Destination.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.13 |
jnxDfcCSCriteriaRefreshedTotal number of filter criteria refreshed successfully as requested
by Control Source.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.14 |
jnxDfcCSCriteriaRefreshFailedTotal number of filter criteria refresh request failed.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.15 |
jnxDfcCSControlProtocolListRequestsTotal number of Control protocol List requests received. The List
request returns a list of all criteria that a particular Control
Source has added and are currently active.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.16 |
jnxDfcCSListSuccessTotal number of list commands processed successfully as requested
by Control Source.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.17 |
jnxDfcCSListFailedTotal number of list commands that could not be processed
successfully.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.18 |
jnxDfcCSControlProtocolNoopRequestsTotal number of Control protocol Noop requests received. The purpose
of this request is to verify the end-to-end connectivity between
Control Source and DFC PIC.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.19 |
jnxDfcCSNoopSuccessTotal number of Noop requests processed successfully as requested by
Control Source.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.20 |
jnxDfcCSNoopFailedTotal number of Noop requests that could not be processed
successfully.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.21 |
jnxDfcCSDynamicCriteriaActiveTotal number of active dynamic filter criteria.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.22 |
jnxDfcCSStaticCriteriaActiveTotal number of active static filter criteria.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.23 |
jnxDfcCSBadRequestTotal number of Bad requests received.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.24 |
jnxDfcCSResponseSuccessfulTotal number of successful response(s) corresponding to the
requests (add, delete, refresh, list and noop) sent out to the
Control Source.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.25 |
jnxDfcCSResponseImproperCriteriaTotal number of response(s) generated because of improper filter
criterion specification in the add request.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.26 |
jnxDfcCSResponseUnknownContentDestTotal number of response(s) generated because of unknown Content
Destination specified in the add, delete, refresh and list
request.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.27 |
jnxDfcCSResponseUnknownCriteriaIdTotal number of response(s) generated because of unknown Criteria
Identifier specified in the delete, refresh and list request.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.28 |
jnxDfcCSResponseImproperTimeoutTotal number of response(s) generated because of improper timeout
specified in the add and refresh request.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.29 |
jnxDfcCSResponseInvalidAuthenticationTotal number of response(s) generated because of invalid
authentication specified in the add, delete, refresh, list and
noop request.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.30 |
jnxDfcCSResponseInvalidSequenceNumberTotal number of response(s) generated because of invalid Sequence
Number specified in the add, delete, refresh, list and noop
request.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.31 |
jnxDfcCSResponseInternalErrorTotal number of response(s) generated because of internal error at
the DFC PIC in processing a request.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.32 |
jnxDfcCSNotificationRestartTotal number of Restart notifications sent to configured
notification-recipients. This notification will be generated when
the system experiences a failure such that all the DFC filter
criteria are lost.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.33 |
jnxDfcCSNotificationRolloverTotal number of Rollover notifications sent to configured
notification-recipients. This notification will be generated when
the DFC PIC experiences a sequence number rollover.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.34 |
jnxDfcCSNotificationNoopTotal number of Noop notifications sent to configured
notification-recipents. This notification will be generated when
the DFC PIC receives a Noop message with the SendAsync parameter
present.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.35 |
jnxDfcCSNotificationTimeoutTotal number of Timeout notifications sent to configured
notification-recipents. This notification will be generated when
the DFC PIC times out a filter criterion on any one of its
configured timeout parameters and the criterion contains a
SendTimeoutAsync parameter.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.36 |
jnxDfcCSNotificationCongestionTotal number of Congestion notifications sent to configured
notification-recipents. This notification will be generated when
the 10-second average packet forwarding rate (in bits/second)
summed over all active filter criteria to a configured Content
Destination exceeds the configured soft limit for that destination.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.37 |
jnxDfcCSNotificationCongestionDeleteTotal number of Congestion Delete notifications sent to configured
notification-recipents. This notification will be generated when
the total 10-second average packet forwarding rate (in bits/second)
summed over all active filter criteria to a configured Content
Destination exceeds the configured hard limit for that
destination.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.38 |
jnxDfcCSNotificationDuplicatesDroppedTotal number of Duplicates Dropped notifications sent to configured
notification-recipents. This notification will be generated when
the configurable Maximum Duplicates parameter has been exceeded in
such a way as to cause packets matching criteria added by the
corresponding Control Source to be dropped.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.39 |
jnxDfcCSAddRequestRateThe request processing rate (requests processed/second).ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.40 |
jnxDfcCSAddRequestPeakRateThe peak request processing rate (requests processed/second).ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.41 |
jnxDfcCSAggrCriteriaBandwidthBandwidth in bits/second.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.42 |
jnxDfcCSSequenceNumberProtocol sequence number.ro Counter64 .1.3.6.1.4.1.2636.3.33.1.1.43 |
jnxDfcCDTableStatistics information for content destination. SEQUENCE OF JnxDfcCDEntry .1.3.6.1.4.1.2636.3.33.2 |
jnxDfcCDEntryAn entry of DFC Content-Destination table. JnxDfcCDEntry .1.3.6.1.4.1.2636.3.33.2.1 |
jnxDfcCDIdContent Destination identifier. A Content Destination is the
recipient of the extracted data, once it is forwarded by the
Server. DisplayString .1.3.6.1.4.1.2636.3.33.2.1.1 |
jnxDfcCDCriteriaTotal number of filter criteria configured for the Content
Destination.ro Counter64 .1.3.6.1.4.1.2636.3.33.2.1.2 |
jnxDfcCDByteRateAverage data rate (in bytes/second) summed over all active
filter criteria to a configured Content Destination.ro Counter64 .1.3.6.1.4.1.2636.3.33.2.1.3 |
jnxDfcCDMatchedPacketsTotal number of packets matching the filter criteria configured for
the Content Destination.ro Counter64 .1.3.6.1.4.1.2636.3.33.2.1.4 |
jnxDfcCDMatchedBytesTotal number of bytes matching the filter criteria configured for
the Content Destination.ro Counter64 .1.3.6.1.4.1.2636.3.33.2.1.5 |
jnxDfcCDCongestionNotificationTotal number of Congestion Notifications sent to a configured
notification-recipient.ro Counter64 .1.3.6.1.4.1.2636.3.33.2.1.6 |
jnxDfcNotifyVarsNotification object definitions. OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.33.3 |
jnxDfcInterfaceNameThe textual name of the DFC interface.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.2636.3.33.3.1 |
jnxDfcInputPktRatedata packet rate (in packets per second).ro Unsigned32 .1.3.6.1.4.1.2636.3.33.3.2 |
jnxDfcPpsSoftOverloadLowWatermarkConfigured lowest value for data packet rate (in packets
per second).ro Unsigned32 .1.3.6.1.4.1.2636.3.33.3.3 |
jnxDfcPpsSoftOverloadHighWatermarkConfigured highest value for data packet rate (in packets
per second).ro Unsigned32 .1.3.6.1.4.1.2636.3.33.3.4 |
jnxDfcPpsHardOverloadLowWatermarkRecommended lowest value for data packet rate (in packets
per second).ro Unsigned32 .1.3.6.1.4.1.2636.3.33.3.5 |
jnxDfcPpsHardOverloadHighWatermarkRecommended highest value for data packet rate (in packets
per second).ro Unsigned32 .1.3.6.1.4.1.2636.3.33.3.6 |
jnxDfcFlowsUsage% usage of total number of flows in system.ro Unsigned32 UNITS "percent" .1.3.6.1.4.1.2636.3.33.3.7 |
jnxDfcCriteriaUsage% usage of matching criteria for all filters.ro Unsigned32 UNITS "percent" .1.3.6.1.4.1.2636.3.33.3.8 |
jnxDfcMemSoftOverloadLowWatermarkConfigured lowest watermark percent for memory load.ro Unsigned32 UNITS "percent" .1.3.6.1.4.1.2636.3.33.3.9 |
jnxDfcMemSoftOverloadHighWatermarkConfigured highest watermark percent for memory load.ro Unsigned32 UNITS "percent" .1.3.6.1.4.1.2636.3.33.3.10 |
jnxDfcFlowLowWatermarkRecommended lowest value for number of flows allowed in
the system.ro Unsigned32 .1.3.6.1.4.1.2636.3.33.3.11 |
jnxDfcFlowHighWatermarkRecommended highest value for number of flows allowed in
the system.ro Unsigned32 .1.3.6.1.4.1.2636.3.33.3.12 |
jnxDfcCriteriaLowWatermarkRecommended lowest value for number of criterias allowed
in the system.ro Unsigned32 .1.3.6.1.4.1.2636.3.33.3.13 |
jnxDfcCriteriaHighWatermarkRecommended highest value for number of criterias allowed
in the system.ro Unsigned32 .1.3.6.1.4.1.2636.3.33.3.14 |
jnxDfcNotificationPrefixAll DFC notifications are registered under this branch. OBJECT IDENTIFIER .1.3.6.1.4.1.2636.4.11.0 |
jnxDfcSoftPpsThresholdExceededNotification of input packet rate (in packet per second)
going beyond the configured limit. NOTIFICATION-TYPE .1.3.6.1.4.1.2636.4.11.0.1 |
jnxDfcSoftPpsUnderThresholdNotification of input packet rate (in packet per second)
dropping back to below the configured limit. NOTIFICATION-TYPE .1.3.6.1.4.1.2636.4.11.0.2 |
jnxDfcHardPpsThresholdExceededNotification of input packet rate (in packet per second)
going beyond the recommended limit. NOTIFICATION-TYPE .1.3.6.1.4.1.2636.4.11.0.3 |
jnxDfcHardPpsUnderThresholdNotification of input packet rate (in packet per second)
dropping back to below the recommended limit. NOTIFICATION-TYPE .1.3.6.1.4.1.2636.4.11.0.4 |
jnxDfcSoftMemThresholdExceededNotification of memory overload condition i.e memory usage
is going beyond the configured limit. NOTIFICATION-TYPE .1.3.6.1.4.1.2636.4.11.0.5 |
jnxDfcSoftMemUnderThresholdNotification of memory usage dropping back to below the
configured limit. NOTIFICATION-TYPE .1.3.6.1.4.1.2636.4.11.0.6 |
jnxDfcHardMemThresholdExceededNotification of memory overload condition i.e memory usage
is going beyond the recommended limit. NOTIFICATION-TYPE .1.3.6.1.4.1.2636.4.11.0.7 |
jnxDfcHardMemUnderThresholdNotification of memory usage dropping back to below the
recommended limit. NOTIFICATION-TYPE .1.3.6.1.4.1.2636.4.11.0.8 |
More MIBs from Juniper Networks
Browse all Juniper NetworksMIBs →JUNIPER-CHASSIS-DEFINES-MIB
The JUNIPER-CHASSIS-DEFINES-MIB establishes the foundational Object Identifier (OID) namespace and data type definitions required to map and identify specific Juniper chassis hardware platforms and their internal physical components. This module serves as the structural prerequisite for the JUNIPER-CHASSIS-MIB, enabling the retrieval of inventory data, component status, and hardware topology details for Juniper MX, PTX, and EX series devices.
5187 objects→
JUNIPER-MOBILE-GATEWAY-GTP-MIB
The JUNIPER-MOBILE-GATEWAY-GTP-MIB provides SNMP objects for monitoring GTP (GPRS Tunneling Protocol) session states, tunnel endpoints, and protocol counters on Juniper mobile gateway platforms. It enables administrators to track GTP-C and GTP-U traffic statistics, error conditions, and active tunnel metrics essential for validating mobile core network connectivity.
1616 objects→
GGSN-MIB
SNMP MIB module
789 objects→
JUNIPER-IFOPTICS-MIB
SNMP MIB module
754 objects→
JUNIPER-MOBILE-GATEWAY-SGW-GTP-MIB
The JUNIPER-MOBILE-GATEWAY-SGW-GTP-MIB module enables monitoring of GTP (GPRS Tunneling Protocol) session states and traffic counters on Juniper Mobile Gateway Serving Gateways (SGW). It provides specific objects for tracking GTP-C and GTP-U tunnel establishment, teardown, and packet throughput metrics essential for validating mobile core network connectivity.
683 objects→
JUNIPER-IPSEC-FLOW-MON-MIB
The JUNIPER-IPSEC-FLOW-MON-MIB monitors Juniper Networks IPsec VPN infrastructure by exposing tables for IKE tunnels, IPSec tunnels, and IPSec security associations to track tunnel states, association parameters, and flow statistics. This module facilitates the management of IPsec security policies and the operational status of encrypted traffic flows within the device's security architecture.
453 objects→