Juniper Networks 204, 5200, 208, 500, 5XT, 5400 manual Known Issues in ScreenOS 5.0.0r9-FIPS

Juniper Networks NetScreen Release Notes

Juniper NetScreen-5000 series only: Before you upgrade a Juniper Networks security appliance to ScreenOS 5.0.0, we recommend that you verify the amount of memory on the device using the get system CLI command. You need 1 gigabyte of memory for Juniper NetScreen-5000. If you start upgrading the device and run into memory problems, you might see the following messages: “insufficient memory, call TAC” or “see release notes for upgrade instructions”.

To avoid network downtime while upgrading devices in an NSRP configuration, refer to the Upgrading Devices in an NSRP Configuration without Downtime document. You can download this document from the location on the CSO where the revision image resides.

NSM does not support the NSRP Configuration without Downtime feature.

5.3 Known Issues in ScreenOS 5.0.0

The following are known deficiencies in features at the time of this release. Whenever possible, a work-around is suggested following the description of the problem. Workaround information starts with “W/A:” If there is no subsection for a particular ScreenOS release, no new known issues were identified for that release.

5.3.1 Known Issues in ScreenOS 5.0.0r9-FIPS

•04960 – A burst of logs sent from a device running ScreenOS to the Security Manager server sometimes creates memory corruption, causing the device to fail.

•03773 – The device drops some IPSec AH packets because of authentication failures, slowing the transfer of packets over an FTP session and sometimes causing large FTP data transfer sessions to fail.

ScreenOS 5.0.0r9-FIPS P/N 093-1638-000, Rev. A Page 32 of 42