snmp-trap-thresholds
Syntax
snmp-trap-thresholds {
flows high high-threshold | low low-threshold;
nat-address-port high high-threshold | low low-threshold;
}
}
Hierarchy Level
[edit services service-set service-set-name]
Description
Configures SNMP flow thresholds for all flows for a service set or flows for all NAT pools configured for a service set..
Options
The remaining options are described separately.
flows high high-threshold—Configure
the upper limit for all flows on the service set. The limit is expressed
as a percentage of max-flows configured for the service
set. When the number of active flows exceeds this limit, an SNMP trap
is set.
Default: 90 percent of
max-flows
flows low low-threshold—Configure
the lower limit for all flows on the service set . The limit is expressed
as a percentage of max-flows configured for the service
set. When the number of active flows falls below this limit, an SNMP
trap is set.
Default: 70 percent of
max-flows
nat-address-port high high-threshold—Configure the upper limit for flows for all NAT pools
on the service set. The limit is expressed as a percentage of max-flows configured for the service set. When the number of
active flows exceeds this limit, an SNMP trap is set.
Default: 90 percent of
max-flows
nat-address-port low low-threshold—Configure the lower limit for flows. The limit is expressed
as a percentage of max-flows configured for the service
set. When the number of active flows falls below this limit, an SNMP
trap is set.
Default: 80 percent of
max-flows
SNMP traps that are generated when you modify the threshold
value for flows of NAT address pools in a service set (by using the snmp-trap-thresholds nat-address-port (high high-threshold | low low-threshold) statement) are not
effective in the PIC. Only the initial threshold value that is set
is effective on the PIC and subsequent changes to the threshold value
are not reflected on the PIC. As a workaround, for the configuration
changes under the [edit services nat pool nat-pool-name] hierarchy level, you must deactivate and activate the relevant
service-set to enable the updated configuration to become effective.
Otherwise, you must reboot the PIC for the updated threshold value
of to take effect.
Until Junos OS Release 14.1, when the NAT pool utilization exceeded the high threshold value configured, an SNMP trap was sent. However, a similar SNMP trap was not triggered when the NAT pool utilization fell below the configured lower limit or threshold. Because NMS systems are being used to monitor and set alarm for threshold values, the absence of an SNMP trap when the low threshold value was reached caused NMS to retain an active alarm in the alarms list. As a result, starting with Release 14.2R1, an SNMP trap is generated when the NAT pool utilization reaches the lower threshold, thereby causing the alarm in NMS to be reset.
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 13.1.