Table of Contents
Advertisement
Copyright © 2011, Juniper Networks, Inc.
Issues in Junos OS Release 10.4 for SRX Series Services Gateways and J Series Services Routers
On SRX100, SRX210, SRX220, and SRX240 devices, in J-Web, the candidate
configuration should be removed from the CLI configuration when validation or commit
from the wizard fails. [PR/549202]
On SRX100, SRX210, SRX220, and SRX240 devices, in J-Web, policies configured under
cannot be edited or deleted in the NAT and firewall wizards. [PR/552519]
group global
Management and Administration
On SRX3400, SRX3600, SRX5600, and SRX5800 devices, the queue statistics are
not correct after deletion and re-creation of a logical interface (IFL) or creation of a
new IFL. IFL statistics are not cleared for 15 minutes after chassis-control is restarted.
[PR/417947]
On SRX5600 devices, when the system is in an unstable state (for example SPU
reboot), NFS might generate
occupy the disk space for a very long time. As a workaround, run the
cleanup
command to clean up when the system has low disk space. [PR/420553]
On SRX650 devices, the kernel crashes when the link goes down during TFTP
installation of the
srxsme
On SRX650 devices, continuous messages are displayed from
in switching mode. [PR/426815]
On SRX240 devices, if a timeout occurs during the TFTP installation, booting the
existing kernel using the
the
reboot
command from the loader prompt. [PR/431955]
On SRX240 devices, when you configure the system log hostname as 1 or 2, the device
goes to the shell prompt. [PR/435570]
On SRX240 devices, the
instances with various Mini-PIM combinations. These messages are seen during bootup,
while restarting fwdd, while restarting chassisd, and during configuration commits.
[PR/437553]
On SRX5800 devices, rebooting is required for any NP bundle configuration change
to take effect. Currently there is no notification displayed after the bundle configuration
change to notify that a reboot is required for the change to take effect. [PR/441546]
On SRX5600 and SRX5800 devices, data path debug trace messages are dropped
at above 1000 packets per second (pps). [PR/446098]
On J2350, J4350, and J6350 devices, extended bit error rate test (BERT) takes an
additional 3 hours to complete even though a BERT period of 24 hours is set.
[PR/447636]
Network Address Translation (NAT)
On J4350 devices, when you place internal calls, interface-based persistent NAT
displays only one active hairpinning session instead of two, even after the call is
established. [PR/504932]
On SRX5600 devices, only network addresses are allowed in IPv6 NAT configuration
from Junos OS Release 10.3 onward. This is enforced in commit check. [PR/545330]
files under the
residual.nfs
image. [PR/425419]
command might crash the kernel. As a workaround, use
boot
Scheduler Oinker
messages are seen on the console at various
directory, which can
/var/tmp
request sys storage
syslogd
when ports are
165
Advertisement
Table of Contents
