This feature is not supported, and the user cannot obtain or configure any value
under these filter options. [PR/460244]
■
On SRX100, SRX210, SRX240, SRX650, and J Series devices, in the J-Web
interface, the Traceoptions tab in the Edit Global Settings window of the OSPF
Configuration page (Configuration>Routing>OSPF Configuration) does not
display the available flags (tracing parameters). As a workaround, use the CLI to
view the available flags. [PR/475313]
■
On SRX100, SRX210, SRX240, SRX650, and J Series devices, when you have a
large number of static routes configured, and if you have navigated to pages
other than to page 1 in the Route Information table in the J-Web interface
(Monitor>Routing>Route Information), changing the Route Table to query other
routes refreshes the page but does not return you to page 1. For example, if you
run the query from page 3 and the new query returns very few results, the Route
Information table continues to display page 3 with no results. As a workaround,
navigate to page 1 manually to view the results. [PR/476338]
■
On SRX210 Low Memory, SRX210 High Memory, and SRX210 PoE devices, in
the J-Web interface, Configuration>Routing>Static Routing does not display
the IPv4 static route configured in rib inet.0. [PR/487597]
■
On SRX100 (low memory and high memory), SRX210 (low memory, high
memory, and PoE), SRX240 (low memory and high memory), SRX650, J2350,
J4350, and J6350 devices, CoS feature commits occur without validation
messages, even if you have not made any changes. [PR/495603]
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
residual.nfs
files under the
/var/tmp
directory,
which can occupy the disk space for a very long time. As a workaround, run the
request sys storage 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
image. [PR/425419]
■
On SRX650 devices, continuous messages are displayed from
syslogd
when ports
are in switching mode. [PR/426815]
■
On SRX240 devices, if a timeout occurs during the TFTP installation, booting the
existing kernel using the boot command might crash the kernel. As a workaround,
use 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
Scheduler Oinker
messages are seen on the console at
various instances with various Mini-PIM combinations. These messages are seen
during bootup, restarting fwdd, restarting chassisd, and configuration commits.
[PR/437553]
Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers
■
157
Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers
