Juniper Networks | NetScreen Release Notes |
|
|
discrepancy, you had to read the text description of the trap type to identify it. Now you can refer to the trap type value to identify it. For example, the traditional SNMP trap type value for a Cold Start event is 0. Please check the ScreenOS Messages Guide for the correct values in ScreenOS 5.0.0.
•02062 – Under certain circumstances,
•02059 – When you changed an IKE gateway from Static IP to Dynamic IP using the WebUI, the procedure automatically changed the setting from Main Mode to Aggressive mode.
•02057 – Multiple custom addresses or service groups in a policy sometimes caused a Juniper Networks security appliance to fail during restart.
•02050 – Configuring an address group from an Apple computer using Internet Explorer sometimes caused a Juniper Networks security appliance to fail.
•02047 – When the device received a packet with Ethernet type 0x8888, the device failed.
•02045 – Under certain circumstances, the device incorrectly flagged and dropped
•02044 – An operation using SSH version 1 to access the device failed when using Radius for administration authentication.
•02035 – The device did not allow URL filtered traffic when the URL queue was full and the URL queue size was too small to process heavy traffic.
•02034 – In transparent mode, when selecting the WebAuth option in the WebUI for the
•02019 – You could not use the WebUI to remove the key id and preshared key of the primary NTP server.
•02018 – The Juniper Networks security appliance failed when applying debug commands, for example, the set ffilter command.
•02001 – If a dynamically added route and a static route on a device both used the same interface default gateway as the next hop, when the dynamic route’s interface default gateway changed, the static route’s gateway did not change with it as expected.
•01993 – You could not modify management services on interfaces configured in the WebUI environment to obtain addresses using DHCP.
•01986 – In an NSRP environment, the primary device sometimes had more active XAuth users than the backup device because the garbage collection mechanism for IPSec SA removed XAuth users from the backup device at a more accelerated rate than it did from the primary device.
ScreenOS | P/N | Page 26 of 42 |
