Table of Contents
Advertisement
JUNOS OS 10.4 Release Notes
166
Under certain stress conditions, SRX1400 will not be able to reach max supported NAT
sessions. [PR/568660]
Power over Ethernet (PoE)
On SRX240 and SRX210 devices, the output of the PoE operational commands takes
roughly 20 seconds to reflect a new configuration or a change in status of the ports.
[PR/419920]
On SRX210 PoE devices managing AX411 Access Points, the device might not be able
to synchronize time with the configured NTP server. [PR/460111]
On SRX210 devices, the fourth access point connected to the services gateway fails
to boot with the default PoE configuration. As a workaround, configure all the PoE
ports to a maximum power of 12.4 watts. Use the following command to configure the
ports:
root#
set poe interface all maximum-power 12.4
[PR/465307]
On SRX210, SRX220, SRX240, and SRX650 devices with factory default configurations,
the device is not able to manage the AX411 Access Point. This might be because of the
DHCP default gateway is not set. [PR/468090]
On SRX210 PoE devices managing AX411 Access Points, traffic of 64 bytes at a speed
of more than 45 megabits per second (Mbps), might result in loss of keepalives and
reboot of the AX411 Access Point. [PR/471357]
On SRX210 PoE devices, high latencies might be observed for the Internet Control
Message Protocol (ICMP) pings between two wireless clients when 32 virtual access
points (VAPs) are configured. [PR/472131]
On SRX210 PoE devices, when AX411 Access Points managed by the SRX Series devices
reboot, the configuration might not be reflected onto the AX411 Access Points. As a
result, the AX411 Access Points retain the factory default configuration. [PR/476850]
On SRX240 PoE devices, during failover, on the secondary node the ADSL Mini-PIM
restarts and takes about 3 to 4 minutes to come up. [PR/528949]
Security
On SRX3400, SRX3600, SRX5600, and SRX5800 devices, the egress filter-based
forwarding (FBF) feature is not supported. [PR/396849]
On SRX210, SRX3400, SRX3600, SRX5600, and SRX5800 devices in a chassis cluster,
if the Infranet Controller auth table mapping action is configured as
as needed
, UAC terminates the existing sessions after Routing Engine failover. You
might have to initiate new sessions. Existing sessions are not affected after Routing
Engine failover if the Infranet Controller auth table mapping action is configured as
always provision auth table
On SRX3400, SRX3600, SRX5600, and SRX5800 devices, you should not configure
rulebase-DDoS rules that have two different application-DDoS objects to run on one
destination service because the traffic destined to one application server can encounter
more than one rule. Essentially, for each protected application server, you have to
configure a single application-level DDoS rule. [PR/467326]
. [PR/416843]
provision auth table
Copyright © 2011, Juniper Networks, Inc.
Advertisement
Table of Contents
