Juniper JUNOS 10.1 - RELEASE NOTES REV 4 Release Note page 160

JUNOS 10.1 Software Release Notes
Unified Access Control (UAC)
Unified Threat Management (UTM)
USB Modem
160
Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers
On J Series devices, MAC address-based authentication does not work when the
router is configured as a UAC Layer 2 Enforcer. [PR/431595]
On SRX210 High Memory devices, content filtering provides the ability to block
protocol commands. In some cases, blocking these commands interferes with
protocol continuity, causing the session to hang. For instance, blocking the
command for the IMAP protocol causes the client to hang without receiving any
response. [PR/303584]
On SRX210 High Memory devices, when the content filtering message type is
set to , customized messages appear in the log file. [PR/403602]
protocol-only
On SRX210 High Memory devices, the express antivirus feature does not send
a replacement block message for HTTP upload (POST) transactions if the current
antivirus status is engine-not-ready
An empty file is generated on the HTTP server without any
contained within it. [PR/412632]
On SRX240, SRX650, and J Series devices, Outlook Express is sending infected
mail (with an EICAR test file) to the mail server (directly, not through DUT).
Eudora 7 uses the IMAP protocol to download this mail (through DUT). Mail
retrieval is slow, and the EICAR test file is not detected. [PR/424797]
On SRX650 devices operating under stress conditions, the UTM subsystem file
partition might fill up faster than UTM can process and clean up existing
temporary files. In that case, the user might see error messages. As a workaround,
reboot the system [PR/435124]
On SRX240 High Memory devices, FTP download for>4 MB files does not work
in a two-device topology. [PR/435366]
On SRX210, SRX240, and SRX650 devices, the Websense server stops taking
new connections after HTTP stress. All new sessions get blocked. As a
workaround, reboot the Websense server. [PR/435425]
On SRX240 devices, if the device is under UTM stress traffic for several hours,
users might get the following error while using a UTM command:
the utmd subsystem is not responding to management requests
As a workaround, restart the
On SRX210, SRX100, SRX240, and SRX650 devices, when you restart fwdd at
the dial-out side, the umd interface goes down and the call never gets connected.
As a workaround, disable the dialer interface and restart the forwarding daemon.
Enable the dialer interface when the forwarding daemon is up and running. As
a result, the dial-out side reconnects with the dial-in side successfully.
Perform the following steps:
and the fallback setting for this state is
utmd process. [PR/436029]
FETCH
block .
message
block
.