use the edit/move button on the Configuration>Security>Policy>IDP Policies page for
editing or prioritizing the rules configured. [PR/503451]
•
On SRX220 devices, you cannot edit the physical properties of a LAN interface in J-Web
without entering the MAC address. As a workaround, edit the properties in the CLI.
[PR/519818]
•
On SRX100, SRX210, SRX220, and SRX240 devices, in J-Web, after a session expires,
a relogin page appears in the wizard window. As a workaround, close the wizard window
when the session expires and log in again. [PR/537475]
•
On SRX100, SRX210, SRX220, and SRX240 devices, in J-Web, a matching destination
port configured in the NAT wizard is not pushed to the CLI configuration. As a
workaround, use the CLI. [PR/547630]
•
On SRX100, SRX210, SRX220, and SRX240 devices, wizards take more time to commit
the configuration setup and to load the page. [PR/548530]
•
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
group global cannot be edited or deleted in the NAT and firewall wizards. [PR/552519]
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,
while restarting fwdd, while restarting chassisd, and during configuration commits.
[PR/437553]
Copyright © 2010, Juniper Networks, Inc.156
JUNOS OS 10.4 Release Notes
To Next Page
Loading...