JUNIPER-JS-POLICY-MIB
Updated Jul 2, 2013The JUNIPER-JS-POLICY-MIB provides SNMP access to monitor and manage security policy configurations and enforcement actions on Juniper SRX Series firewalls, specifically tracking traffic flow rules defined between network zones, source/destination IP addresses, and scheduled time windows.
Imported Objects
Objects
73 total| Object Name |
|---|
jnxJsSecPolicyMIBThis module defines the mib for policy monitoring.
A security policy, which can be configured from the user
interface controls the traffic flow from one zone to another
zone by defining the kind(s) of traffic permitted from
specified IP sources to specified IP destinations at
scheduled times.
Juniper security device enforce the security policies rules
for the transit traffic in terms of which traffic can pass
through the firewall, and the actions taken on the traffic as
it passes through the firewall. MODULE-IDENTITY .1.3.6.1.4.1.2636.3.39.1.4.1 |
jnxJsPolicyNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.39.1.4.1.0 |
jnxJsPolicyObjects OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.39.1.4.1.1 |
jnxJsPolicyNumberThe number of policies (regardless of their current
state) present on this system.ro Integer32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.1 |
jnxJsPolicyTableThe table exposes the security policy entries. Security
devices/routers provide a network boundary with a single
point of entry and exit point, which allows the screening
and directing of traffic through the implementation of
access policies. The access policies can permit, deny,
encrypt, authenticate, prioirtize, schedule and monitor
the traffic flow through the firewall.
This table lists entries of policy. The number of policies
are given by jnxJsPolicyNumber. SEQUENCE OF JnxJsPolicyEntry .1.3.6.1.4.1.2636.3.39.1.4.1.1.2 |
jnxJsPolicyEntryAn entry contains a security policy.
The security policies are configured under from-zone,
to-zone direction. Under a specific zone direction,
each security policy contains name, match-criteria,
action, and other options. JnxJsPolicyEntry .1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1 |
jnxJsPolicyFromZoneThe attribute displays the from zone name. DisplayString .1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1.1 |
jnxJsPolicyToZoneThe attribute exposes the to-zone name. DisplayString .1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1.2 |
jnxJsPolicyNameThe name of the policy defined. It consists of up to 256 ascii
characters and uniquely identifies the policy entry. DisplayString .1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1.3 |
jnxJsPolicySequenceNumberThe attribute indicates the policy sequence order of the policy
within a specific from-zone and to-zone pair. Policies are matched
in a sequence where the ordering is specified by this number.ro Integer32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1.4 |
jnxJsPolicyActionThe attribute indicates the actions performed when the
criteria is matched.
The action permit, deny and reject are used configured policies.ro Enumeration .1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1.5 |
jnxJsPolicySchedulerThe name of the schedule attached to this policy. Certain schedule
has a specified duration and this may effect the status of the
policy.ro DisplayString .1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1.6 |
jnxJsPolicyStateThe state of this policy: active, inactive, or unavailable.
The state can be effected by the scheduler if the scheduler
has a specified duration.ro Enumeration .1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1.7 |
jnxJsPolicyStatsAvailabilityThe statistics availability of this policy.
The attribute indicates whether the statistics counters are
available and are actively updated. If available, there would
exists a matching jnxJsPolicyStatsEntry for the policy.ro Enumeration .1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1.8 |
jnxJsPolicyPerSecBytesThresholdThe attribute indicates the threshold value of bytes per second.ro Integer32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1.9 |
jnxJsPolicyPerMinKbytesThresholdThe attribute indicates the threshold value of kbyte per min.ro Integer32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1.10 |
jnxJsPolicyStatsTableThe table exposes the security policy statistics entries. These
statistics can be enabled and disabled by configuration on a
per policy basis. SEQUENCE OF JnxJsPolicyStatsEntry .1.3.6.1.4.1.2636.3.39.1.4.1.1.3 |
jnxJsPolicyStatsEntryAn entry contains a security policy.
The security policies are configured under from-zone,
to-zone direction. Under a specific zone direction,
each security policy contains name, match-criteria,
action, and other options. JnxJsPolicyStatsEntry .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1 |
jnxJsPolicyStatsCreationTimeThe creation timestamp of the policy statistics entry. The
timestamp is modified during the creation and deletion of the
policy statistics entry. When the timestamp changes, the policy
entry statistics is assumed to be a new statistics entry and not
associated with previous statistic entry of the same indices.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.1 |
jnxJsPolicyStatsInputBytesThe number of input bytes enters the FW through this policy.ro Counter64 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.2 |
jnxJsPolicyStatsInputByteRateThe number of input bytes per second or the rate that enters the FW
through this policy.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.3 |
jnxJsPolicyStatsOutputBytesThe number of output bytes associated with this policy.ro Counter64 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.4 |
jnxJsPolicyStatsOutputByteRateThe number of output bytes per second or the rate associated
with this policy.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.5 |
jnxJsPolicyStatsInputPacketsThe number of input packets enters the FW through this policy.ro Counter32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.6 |
jnxJsPolicyStatsInputPacketRateThe number of input packets per second or the input packet rate
of the FW through this policy.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.7 |
jnxJsPolicyStatsOutputPacketsThe number of output packets associated with this policy.ro Counter32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.8 |
jnxJsPolicyStatsOutputPacketRateThe number of output packets per second or the rate
associated with this policy.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.9 |
jnxJsPolicyStatsNumSessionsThe number of sessions associated with this policy.ro Counter32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.10 |
jnxJsPolicyStatsSessionRateThe rate of the sessions associated with this policy.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.11 |
jnxJsPolicyStatsSessionDeletedThe number of sessions associated with this policy.ro Counter32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.12 |
jnxJsPolicyStatsLookupsThe number of policy lookups performed.ro Counter32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.13 |
jnxJsPolicyStatsCountAlarmThe number of alarm counted when the traffic exceeds
certain threshold configuration. The node is obsoleted.roobsolete Counter32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.14 |
jnxJsPolicyStatsInBytesInitThe number of input bytes in the session initial direction enters
the FW through this policy.ro Counter64 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.15 |
jnxJsPolicyStatsInBytesRepThe number of input bytes in the session reply direction enters
the FW through this policy.ro Counter64 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.16 |
jnxJsPolicyStatsInByteRtInitThe number of input bytes in the session initial direction
per second or the rate that enters the FW through this policy.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.17 |
jnxJsPolicyStatsInByteRtRepThe number of input bytes in the session reply direction
per second or the rate that enters the FW through this policy.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.18 |
jnxJsPolicyStatsOutBytesInitThe number of output bytes in the session initial direction
associated with this policy.ro Counter64 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.19 |
jnxJsPolicyStatsOutBytesRepThe number of output bytes in the session reply direction
associated with this policy.ro Counter64 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.20 |
jnxJsPolicyStatsOutByteRtInitThe number of output bytes in the session initial direction
per second or the rate associated with this policy.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.21 |
jnxJsPolicyStatsOutByteRtRepThe number of output bytes in the session reply direction per
second or the rate associated with this policy.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.22 |
jnxJsPolicyStatsInPacketsInitThe number of input packets in the session initial direction
enters the FW through this policy.ro Counter32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.23 |
jnxJsPolicyStatsInPacketsRepThe number of input packets in the session reply direction
enters the FW through this policy.ro Counter32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.24 |
jnxJsPolicyStatsInPacketRtInitThe number of input packets in the session initial direction
per second or the input packet rate of the FW through this policy.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.25 |
jnxJsPolicyStatsInPacketRtRepThe number of input packets in the session reply direction
per second or the input packet rate of the FW through this policy.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.26 |
jnxJsPolicyStatsOutPacketsInitThe number of output packets in the session initial direction
associated with this policy.ro Counter32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.27 |
jnxJsPolicyStatsOutPacketsRepThe number of output packets in the session reply direction
associated with this policy.ro Counter32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.28 |
jnxJsPolicyStatsOutPacketRtInitThe number of output packets in the session initial direction
per second or the rate associated with this policy.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.29 |
jnxJsPolicyStatsOutPacketRtRepThe number of output packets in the session reply direction
per second or the rate associated with this policy.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.30 |
jnxJsPolicyTrapVars OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.39.1.4.1.2 |
jnxJsPolicySystemStats OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.39.1.4.1.3 |
jnxJsPolicySystemStatsIPv4 OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.39.1.4.1.3.1 |
jnxJsPolicySystemStatsTotalAllowIPv4PacketsThe number of IPv4 packets allowed by all policies.ro Counter64 .1.3.6.1.4.1.2636.3.39.1.4.1.3.1.1 |
jnxJsPolicySystemStatsTotalAllowIPv4BytesThe number of IPv4 bytes allowed by all policies.ro Counter64 .1.3.6.1.4.1.2636.3.39.1.4.1.3.1.2 |
jnxJsPolicySystemStatsTotalAllowIPv4PacketsRateThe rate of IPv4 packets allowed by all policies.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.3.1.3 |
jnxJsPolicySystemStatsTotalAllowIPv4BytesRateThe rate of IPv4 bytes allowed by all policies.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.3.1.4 |
jnxJsPolicySystemStatsTotalDropIPv4PacketsThe number of IPv4 packets dropped by all policies.ro Counter64 .1.3.6.1.4.1.2636.3.39.1.4.1.3.1.5 |
jnxJsPolicySystemStatsTotalDropIPv4BytesThe number of IPv4 bytes dropped by all policies.ro Counter64 .1.3.6.1.4.1.2636.3.39.1.4.1.3.1.6 |
jnxJsPolicySystemStatsTotalDropIPv4PacketsRateThe rate of IPv4 packets dropped by all policies.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.3.1.7 |
jnxJsPolicySystemStatsTotalDropIPv4BytesRateThe rate of IPv4 bytes dropped by all policies.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.3.1.8 |
jnxJsPolicySystemStatsTotalAllowIPv4FlowsThe number of IPv4 flows allowed by all policies.ro Counter64 .1.3.6.1.4.1.2636.3.39.1.4.1.3.1.9 |
jnxJsPolicySystemStatsTotalAllowIPv4FlowsRateThe rate of IPv4 flows allowed by all policies.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.3.1.10 |
jnxJsPolicySystemStatsIPv6 OBJECT IDENTIFIER .1.3.6.1.4.1.2636.3.39.1.4.1.3.2 |
jnxJsPolicySystemStatsTotalAllowIPv6PacketsThe number of IPv6 packets allowed by all policies.ro Counter64 .1.3.6.1.4.1.2636.3.39.1.4.1.3.2.1 |
jnxJsPolicySystemStatsTotalAllowIPv6BytesThe number of IPv6 bytes allowed by all policies.ro Counter64 .1.3.6.1.4.1.2636.3.39.1.4.1.3.2.2 |
jnxJsPolicySystemStatsTotalAllowIPv6PacketsRateThe rate of IPv6 packets allowed by all policies.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.3.2.3 |
jnxJsPolicySystemStatsTotalAllowIPv6BytesRateThe rate of IPv6 bytes allowed by all policies.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.3.2.4 |
jnxJsPolicySystemStatsTotalDropIPv6PacketsThe number of IPv6 packets dropped by all policies.ro Counter64 .1.3.6.1.4.1.2636.3.39.1.4.1.3.2.5 |
jnxJsPolicySystemStatsTotalDropIPv6BytesThe number of IPv6 bytes dropped by all policies.ro Counter64 .1.3.6.1.4.1.2636.3.39.1.4.1.3.2.6 |
jnxJsPolicySystemStatsTotalDropIPv6PacketsRateThe rate of IPv6 packets dropped by all policies.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.3.2.7 |
jnxJsPolicySystemStatsTotalDropIPv6BytesRateThe rate of IPv6 bytes dropped by all policies.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.3.2.8 |
jnxJsPolicySystemStatsTotalAllowIPv6FlowsThe number of IPv6 flows allowed by all policies.ro Counter64 .1.3.6.1.4.1.2636.3.39.1.4.1.3.2.9 |
jnxJsPolicySystemStatsTotalAllowIPv6FlowsRateThe rate of IPv6 flows allowed by all policies.ro Gauge32 .1.3.6.1.4.1.2636.3.39.1.4.1.3.2.10 |
jnxJsPolicySystemStatsEnabledThe configured status of Policy System Wide Statistic Collection.ro Enumeration .1.3.6.1.4.1.2636.3.39.1.4.1.3.3 |
More MIBs from Juniper Networks
Browse all Juniper NetworksMIBs →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.
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.
SNMP MIB module
SNMP MIB module
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.
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.