6.3.0r10 Release Notes - Juniper Networks
6.3.0r10 Release Notes - Juniper Networks
6.3.0r10 Release Notes - Juniper Networks
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
ScreenOS 6.3.0 <strong>Release</strong> <strong>Notes</strong><br />
38<br />
• 500495—With antispam enabled, e-mail with attachments greater than 3 to 4 MB<br />
sometimes dropped due to out of memory error.<br />
• 500843—Output of SNMP walk sometimes displayed incorrect interface for ARP table<br />
entries.<br />
• 501256—The Translated Dest column was empty when the traffic logs were saved<br />
using WebUI.<br />
• 501343—Even though there was no incoming traffic, alarm traffic for policy increased,<br />
because the self traffic was denied by the deny policy.<br />
• 502419—Traffic shaping statistics were not displayed on the NSRP VSI interfaces on<br />
the firewall.<br />
• 504084—The track IP failed sometimes when the interface was inactive.<br />
• 505456—Event log displayed "system temperature severely high" message even when<br />
the temperature of the device was appropriate and the hardware was in good condition.<br />
• 505554—Traffic log for large PING over MTU size was displayed as close-ageout<br />
instead of close-resp.<br />
• 506473—Radius server was not reachable when the source interface was not the<br />
Virtual Security Interface (VSI).<br />
• 506543—Parsing a folder with the name "quit" abruptly closed the FTP session.<br />
• 509166—SSG5 wireless device was not able to locate the best channel under certain<br />
conditions.<br />
• 510473—Typo in infranet enforcer mode test command resulted in syntax error after<br />
reboot.<br />
• 511026—The implementation of IKEv2 DoS attack prevention was incorrect.<br />
• 511812—When a BGP neighbor was configured and an outgoing route map was applied,<br />
the firewall did not apply the local preference correctly as specified in the policy terms.<br />
• 512752—In certain conditions, failure of the infranet controller connection caused high<br />
CPU condition on the device.<br />
• 515064—In certain conditions, it was possible to define a custom service object for<br />
protocol 0.<br />
• 520662—Under certain conditions, the get alg pptp xlat command sometimes caused<br />
the device to reboot unexpectedly.<br />
Copyright © 2012, <strong>Juniper</strong> <strong>Networks</strong>, Inc.