Juniper Networks 5400, 5200, 208, 204, 500, 5XT manual Juniper Networks NetScreen Release Notes

Juniper Networks NetScreen Release Notes

•02867 – If the DHCP relay server is set with an IP address, the device incorrectly attempted to resolve the IP address with the host name even though there was no hostname.

•02861 – IP swapping issues occurred on the Juniper NetScreen-5000 Series systems sometimes because of invalid cache.

•02845 – In an NSRP active-passive configuration, improper MAC table entries prevented the backup device from being managed.In some instances, you could not manage a backup device in an NSRP active-passive configuration.

•02810 – A policy with the negate option did not free memory on the device properly, creating a memory leak, degrading performance on the device.

•02798 – The Juniper NetScreen-5000 Series systems sometimes had a redundant buffer when receiving out-of-order fragmented VPN packets.

•02787/03020 – A memory leak caused by a failed DNS query on a Juniper NetScreen-5200 in an HA pair caused the primary system to fail.

•02774 – Multiple trace routes occurred after you created a BGP neighbor to a device in an HA pair, disabled HA synchronization, and then attempted to redistribute routes from the primary device to the backup device.

•02768 – When the primary device attempted to synchronize with the backup device and sent it a new DIP session, the backup device could still have the existing DIP session and could not perform the synchronization.

•02762 – If you attempted to display 100 logs per page in the WebUI Traffic Log, the WebUI displayed no logs.

•02725 – In an NSRP device pair, the primary device generated a log that indicated that multiple failovers occurred, but the backup device only generated one log, indicating only one failover.

•02710 – The Unknown Protocol SCREEN option did not work on the Juniper NetScreen-5000 Series systems.

•02656 – The WebUI home page did not display the status for Layer 2 interfaces.

•02620 – Issuing the debug command for the WebSense server, caused the device to fail.

•02604 – When a device exported routes from a Vsys to a root virtual router, the exported routes were not tagged with the correct Vsys ID.

•02602 – Attempts to establish Telnet, WebUI, and SSH, sessions to the interface, where management was enabled, failed, when a route from the correct interface was not provided or the route pointed to a different gateway.

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