JUNIPER-JS-POLICY-MIB: View SNMP OID List / Download MIB

VENDOR: JUNIPER


 Home MIB: JUNIPER-JS-POLICY-MIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, SNMPv2-TC, JUNIPER-JS-SMI

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 jnxJsSecPolicyMIB 1.3.6.1.4.1.2636.3.39.1.4.1
This 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.
     jnxJsPolicyNotifications 1.3.6.1.4.1.2636.3.39.1.4.1.0
     jnxJsPolicyObjects 1.3.6.1.4.1.2636.3.39.1.4.1.1
         jnxJsPolicyNumber 1.3.6.1.4.1.2636.3.39.1.4.1.1.1 integer32 read-only
The number of policies (regardless of their current state) present on this system.
         jnxJsPolicyTable 1.3.6.1.4.1.2636.3.39.1.4.1.1.2 no-access
The 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.
             jnxJsPolicyEntry 1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1 no-access
An 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.
                 jnxJsPolicyFromZone 1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1.1 displaystring no-access
The attribute displays the from zone name.
                 jnxJsPolicyToZone 1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1.2 displaystring no-access
The attribute exposes the to-zone name.
                 jnxJsPolicyName 1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1.3 displaystring no-access
The name of the policy defined. It consists of up to 256 ascii characters and uniquely identifies the policy entry.
                 jnxJsPolicySequenceNumber 1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1.4 integer32 read-only
The 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.
                 jnxJsPolicyAction 1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1.5 integer read-only
The attribute indicates the actions performed when the criteria is matched. The action permit, deny and reject are used configured policies. Enumeration: 'deny': 2, 'reject': 3, 'permit': 1.
                 jnxJsPolicyScheduler 1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1.6 displaystring read-only
The name of the schedule attached to this policy. Certain schedule has a specified duration and this may effect the status of the policy.
                 jnxJsPolicyState 1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1.7 integer read-only
The state of this policy: active, inactive, or unavailable. The state can be effected by the scheduler if the scheduler has a specified duration. Enumeration: 'active': 1, 'inactive': 2, 'unavailable': 3.
                 jnxJsPolicyStatsAvailability 1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1.8 integer read-only
The 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. Enumeration: 'available': 1, 'unavailable': 2.
                 jnxJsPolicyPerSecBytesThreshold 1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1.9 integer32 read-only
The attribute indicates the threshold value of bytes per second.
                 jnxJsPolicyPerMinKbytesThreshold 1.3.6.1.4.1.2636.3.39.1.4.1.1.2.1.10 integer32 read-only
The attribute indicates the threshold value of kbyte per min.
         jnxJsPolicyStatsTable 1.3.6.1.4.1.2636.3.39.1.4.1.1.3 no-access
The table exposes the security policy statistics entries. These statistics can be enabled and disabled by configuration on a per policy basis.
             jnxJsPolicyStatsEntry 1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1 no-access
An 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.
                 jnxJsPolicyStatsCreationTime 1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.1 timestamp read-only
The 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.
                 jnxJsPolicyStatsInputBytes 1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.2 counter64 read-only
The number of input bytes enters the FW through this policy.
                 jnxJsPolicyStatsInputByteRate 1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.3 gauge32 read-only
The number of input bytes per second or the rate that enters the FW through this policy.
                 jnxJsPolicyStatsOutputBytes 1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.4 counter64 read-only
The number of output bytes associated with this policy.
                 jnxJsPolicyStatsOutputByteRate 1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.5 gauge32 read-only
The number of output bytes per second or the rate associated with this policy.
                 jnxJsPolicyStatsInputPackets 1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.6 counter32 read-only
The number of input packets enters the FW through this policy.
                 jnxJsPolicyStatsInputPacketRate 1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.7 gauge32 read-only
The number of input packets per second or the input packet rate of the FW through this policy.
                 jnxJsPolicyStatsOutputPackets 1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.8 counter32 read-only
The number of output packets associated with this policy.
                 jnxJsPolicyStatsOutputPacketRate 1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.9 gauge32 read-only
The number of output packets per second or the rate associated with this policy.
                 jnxJsPolicyStatsNumSessions 1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.10 counter32 read-only
The number of sessions associated with this policy.
                 jnxJsPolicyStatsSessionRate 1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.11 gauge32 read-only
The rate of the sessions associated with this policy.
                 jnxJsPolicyStatsSessionDeleted 1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.12 counter32 read-only
The number of sessions associated with this policy.
                 jnxJsPolicyStatsLookups 1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.13 counter32 read-only
The number of policy lookups performed.
                 jnxJsPolicyStatsCountAlarm 1.3.6.1.4.1.2636.3.39.1.4.1.1.3.1.14 counter32 read-only
The number of alarm counted when the traffic exceeds certain threshold configuration.
     jnxJsPolicyTrapVars 1.3.6.1.4.1.2636.3.39.1.4.1.2