Juniper Networks 208, 5200 The NetScreen device was unable to complete the upgrade of the loader

Juniper Networks NetScreen Release Notes

•03358 – A very long URL entry when you attempt to perform URL filtering sometimes caused the device to fail.

•03356 – The Phase 2 rekey sometimes failed after the Phase 1 expired when you used Kbytes as the criteria to trigger a Phase 2 rekey operation.

•03355 – Track IP packets were sent out at the wrong interval, increasing failed counts (decreasing success rates) even though pings worked correctly.

•03353 – When you configured a policy using the multiple service feature including more than 49 services, the Move checkbox of the policy disappeared from the WebUI and the WebUI displayed some field strings incorrectly.

•03351 – When the Juniper NetScreen-5XP successfully upgraded to ScreenOS 5.0.X, the device incorrectly displayed the following message:

The NetScreen device was unable to complete the upgrade of the file system.

The NetScreen device was unable to complete the upgrade of the loader.

•03346 – The Juniper NetScreen-5200 sometimes failed when you set up IKE gateways in a Vsys on the Juniper NetScreen-5200.

•03340 – Security Manager did not send the correct Action code when generating a traffic log.

•03338 – The component blocking feature that forces a packet to be dropped did not work properly.

•03311 – When the VIP server detection was set to the Manual setting, the VIP server status detection still displayed the same status when the server detection parameter was set to Automatic.

•03308 – When you attempted to change a username in the WebUI, the system added a new user instead of changing the name of the existing user.

•03295 – When you issued a get interface command or similar commands, ScreenOS truncated interface names that had too many characters.

•03294 – When you issued the command get log traffic inc on a Juniper NetScreen-5200, the system failed.

•03281 – When you performed an incremental SPF (Shortest Path First) operation for an OSPF virtual routing instance, the device failed.

•03278 – When updating a dynamic VPN tunnel’s peer gateway IP, a new route lookup was not performed for the updated peer gateway IP. If the updated peer gateway IP was not reachable via the old route used for the previous peer gateway IP entry, the VPN would fail.

•03273 – After you saved the value in the policy counter in the WebUI, the value was different from the actual policy count.

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