Juniper IDP OS 5.1R1 - RELEASE NOTES REV 1 Release Note page 14

Juniper Networks Intrusion Detection and Prevention Release Notes
Table 4: Resolved Issues (continued)
PR Description
CPU Utilization
474709 Resolved an issue where we had reported incorrect CPU utilization for single core platforms (IDP600, IDP200,
IDP75). For single core platforms, you can now use the Linux
is reported to SNMP but not to NSM. For multicore platforms, you use the
not the Linux
502048 Resolved an issue where, if the IDP OS services were restarted while the device was processing traffic, the
idp-cpu-utilization
552181 Resolved an issue on IDP8200 where IDP engine CPU load had been incorrectly reported as 0%.
Stability
415604 Resolved an issue where the autorecovery feature had failed to restart an IDP engine in a hung state.
423847 We have changed the timeout for a TCP session marked for flow bypass to 60 seconds (was 5 seconds).
482866 Resolved an issue where the autorecovery process incorrectly considered the IDP engine to be in a hung state
and consequently terminated the IDP engine. This had occurred during "All Attacks" policy push.
494931 Resolved an issue found in stress testing where continuously pushing a policies with APE rules would eventually
result in policy push errors.
496207 Resolved an issue where running
and increase in latency.
497333 Resolved an issue where there had been a decrease in free packets after the auto-recovery process restarted
the IDP engine (IDP1100, IDP600, IDP200 only).
497628 Improved code so that a core dump is generated more often when IDP engine crashes. However, under low
memory conditions, a core dump might not be generated.
506585 Resolved an issue where memory had not been freed after successive policy pushes.
522406 Resolved an issue that had caused a kernel panic after reboot.
540685 Resolved an issue where the command to disable protocol decoding
resulted in the device dropping traffic rather than passing it through as intended.
541187 Resolved an issue that had killed the autorecovery process before recovery was completed.
548261 Resolved a memory issue that had caused a detector engine update to fail when the security policy was large
(IDP75).
560281 Changed implementation to avoid a memory leak issue that had been reported in 5.0r2.
567916 Resolved an issue where time updates from an NTP server stopped working after installing a patch release.
14
command.
top
query returned 0 (an incorrect value).
scio cpu-utilization
top command to query CPU utilization. This value
scio idp-cpu-utilization
command in single core platforms caused a drop in throughput
scio const -d set PROTOCOLNAME 0
Copyright © 2011, Juniper Networks, Inc.
command and
scio
had