•
On SRX210 High Memory devices, J-Web did not work with IE8 (Japanese version) as
the behavior of J-Web was undefined when launched from any browsers based on
languages other than English. [PR/544801: This issue has been resolved.]
•
On SRX100, SRX210, SRX240, and SRX650 devices, J-Web login and page navigation
were slow. [PR/546502: This issue has been resolved.]
Network Address Translation (NAT)
•
On SRX240 High Memory devices in a chassis cluster, the secondary node could go to
DB> mode when there were many policies configured and when TCP, UDP, and ICMP
traffic matches the policies. [PR/493095: This issue has been resolved.]
•
On SRX5800 NAT enabled devices, show security nat source pool command output
displayed negative value in translation hits counter. [PR/509329: This issue has been
resolved.]
•
On SRX3400 and SRX3600 devices, if you changed the configuration from source
pool NAT to static NAT when there were entries in the incoming table, those entries
would contain unrecognized characters. [PR/517500: This issue has been resolved.]
•
in source NAT mode, RTSP control session was not closed in time (route mode under
Ixload rtsp testing) and IP mistranslated in RTSP header. [PR/521555: This issue has
been resolved.]
•
On SRX3400 and SRX3600 devices, if a SIP proxy with a nonstandard SIP source port
(5060) was located outside the firewall, the inbound call might experience a delay of
several seconds in all source NAT modes. [PR/526808: This issue has been resolved.]
•
On SRX650 devices, source-address option for J-Flow did not stay persistent.
[PR/530620: This issue has been resolved.]
Screens
•
On SRX3400, SRX3600, SRX5600, and SRX5800 devices, screen names with 24
characters were not functioning properly. [PR/520299: This issue has been resolved.]
SNMP
•
On SRX650 devices, the SNMP MIB walk to the jnxFru table displayed only one fan.
[PR/533112: This issue has been resolved.]
VPNs
•
On SRX240 High Memory devices, IPsec VPNs went down if the /var/log/ partition
was 100 percent full and trace options were enabled. [PR/513567: This issue has been
resolved.]
•
On SRX650 devices, KMD did not respond to management requests, which prevented
the administrator from determining SA status. [PR/519274: This issue has been
resolved.]
•
On SRX210 High Memory devices, when using an IKE preshared key of more than 41
ASCII characters for dynamic VPN, the IKE phase 1 connection failed to establish.
[PR/523231: This issue has been resolved.]
165Copyright © 2010, Juniper Networks, Inc.
Issues in Junos OS Release 10.4 for SRX Series Services Gateways and J Series Services Routers
To Next Page
Loading...