Description

The SNMP trap jnxJsScreenAttack belongs to category Routing, but cannot be disabled based on category. This article explains how to filter it in SNMPv3.

Symptoms

 Unable to block  jnxJsScreenAttack via category.

Solution

The trap will not be blocked in SNMPv2; but can only be filtered with SNMPv3. This trap cannot be disabled based on category. This means that the trap jnxJsScreenAttack will be sent out even if routing is not mentioned in the category list.

The SNMP trap jnxJsScreenAttack belongs to category Routing as per link below:

Juniper Networks Enterprise-Specific SNMP Version 2 Traps

However, this trap cannot be disabled based on category. This means that the trap jnxJsScreenAttack will be sent out even if routing is not mentioned in the category list.

The traps filters are supported only in SNMPv3 but are not in the trap-group. This trap can be disabled using SNMPv3, with the command snmp v3 notify-filter in the CLI. SNMPv3 is much more flexible; it supports sending the same trap to multiple NMS systems, and including or excluding specific OIDs.

Related Information