JUNIPER-JS-SCREENING-MIB :: jnxJsScreenMonTearDrop

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsJUNIPER-JS-SCREENING-MIBjnxJsScreenMonTearDrop

jnxJsScreenMonTearDrop

Module: JUNIPER-JS-SCREENING-MIB

OID (symbolic): JUNIPER-JS-SCREENING-MIB::jnxJsScreenMonTearDrop

OID (numeric): 1.3.6.1.4.1.2636.3.39.1.8.1.1.1.1.4

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: Teardrop attacks exploit the reassembly of fragmented IP packets. In the IP header, one of the fields is the fragment offset field, which indicates one of the fields is the fragment offset field. It indicates the starting position of the data contained in a fragmented packet relative to the data of the original unfragmented packet. When the sum of the offset and size of one fragmented packet differ from that of the next fragmented packet, the packets overlap. The server attempting to reassemble the packet can crash, especially if it is running an older operating system that has this vulnerability.

When this option is enabled, the security device detects this discrepancy in a fragmented packet and drops it and this attribute counts the number of packets dropped.

What is jnxJsScreenMonTearDrop?

This read-only counter tallies Teardrop attack packets dropped in this zone, where a fragmented IP packet's offset and size fields deliberately overlap in a way that can crash an older OS's reassembly code. An admin sees this counter rise when a legacy-OS-targeting fragmentation exploit is being attempted against hosts in the zone.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2636.3.39.1.8.1.1.1.1.4
snmpwalk -v2c -c public <target> JUNIPER-JS-SCREENING-MIB::jnxJsScreenMonTearDrop

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2636.3.39.1.8.1.1.1.1.4.1
snmpget -v2c -c public <target> JUNIPER-JS-SCREENING-MIB::jnxJsScreenMonTearDrop.1

Start monitoring Juniper SRX/J-series security appliance (DoS/DDoS screen defenses) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the JUNIPER-JS-SCREENING-MIB::jnxJsScreenMonTearDrop OID value, configure state conditions and alerts, and monitor any Juniper SRX/J-series security appliance (DoS/DDoS screen defenses) from a single console.

OID Breakdown

Upper-level ancestors (11 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
1.3.6.1.4.1.2636.3.39jnxJsMibRootJUNIPER-SMI
1.3.6.1.4.1.2636.3.39.1jnxJsSecurityJUNIPER-JS-SMI
1.3.6.1.4.1.2636.3.39.1.8jnxJsScreeningJUNIPER-JS-SMI
Numeric OIDNameModule
1.3.6.1.4.1.2636.3.39.1.8.1jnxJsScreenMIBJUNIPER-JS-SCREENING-MIB
1.3.6.1.4.1.2636.3.39.1.8.1.1jnxJsScreenObjectsJUNIPER-JS-SCREENING-MIB
1.3.6.1.4.1.2636.3.39.1.8.1.1.1jnxJsScreenMonTableJUNIPER-JS-SCREENING-MIB
1.3.6.1.4.1.2636.3.39.1.8.1.1.1.1jnxJsScreenMonEntryJUNIPER-JS-SCREENING-MIB
1.3.6.1.4.1.2636.3.39.1.8.1.1.1.1.4jnxJsScreenMonTearDropJUNIPER-JS-SCREENING-MIB