Juniper Networks 5XT User Manual

Juniper Networks

NetScreen Release Notes

ScreenOS 5.0.0r9-FIPS

P/N  093-1638-000, Rev. A

Page 22 of 42

• 02384 – The device failed if you connected an Ethernet cable to the untrust 

interface in the v1-untrust zone while the device was in transparent mode.

• 02383 – Under some circumstances, the OSPF routing instance could not 

build an adjacency because its memory buffer was not large enough to 
handle large databases.

• 02379 – You could not establish the Phase II portion of a VPN tunnel when 

you referenced a custom service that had spaces in its name with no quote 
marks around the string because ScreenOS did not recognize strings with 
spaces without quotes around the string.

• 02377 – The Juniper NetScreen-200 did not always free up memory after 

VPN tunnels closed, requiring a manual device reboot to recover.

• 02375 – The device was unable to detect and defend against a ping of death 

attack and would fail when these types of packets arrived at the device. 

• 02372 – You could not clear sessions on Juniper NetScreen-50 devices in an 

active-passive environment in instances when the active device stopped 
creating new sessions when the session table was full

.

• 02370 – When you manually created a VPN tunnel in an NSRP environment 

in the WebUI, using an extra comma in the key portion of the set vpn 
command, the primary device failed while the backup device kept the old 
configuration.

• 02368 – ScreenOS removed the quotation marks around the VPN name with 

a space when you configured an NHTB value on an interface.

• 02364 – The device generated an unknown keyword error to the keyword all-

virtual-system when you tried to assign a new admin password to a VSYS.

• 02354 – Occasionally, the ScreenOS logging environment incorrectly 

displayed unusual logs that indicated a hacker attacked the device. A typical 
message that indicated a hacker was the following:

• 02336 – In an NSRP active-active environment, when the customer 

disconnected all the cables from the HA1, HA2, and MGT interfaces on 
either device, and they reconnected cables to the HA1 and HA2 interfaces, 
the device rebooted.

• 02323 – When you ran FTP Put or Get commands to push or obtain data to 

or from the device, the WebUI always indicated the device had a Deny action 
in its policy even when the policy was configured to permit traffic.