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

Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers
On SRX210 devices, the fourth access point connected to the services gateway
fails to boot with the default Power over Ethernet (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 SRX100, SRX210, SRX240, and SRX650 devices, with factory default
configurations the device is not able to manage the AX411 Acess Point. This
might be due to the DHCP default gateway not being set. [PR/468090]
On SRX210 PoE devices managing AX411 Access Points, traffic of 64 bytes at
speed 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]
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
, UAC terminates the existing sessions after Routing
provision auth table as needed
Engine failover. You might have to initiate new sessions. Existing sessions will
not get affected after Routing Engine failover if the Infranet Controller auth table
mapping action is configured as always provision auth table . [PR/416843]
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]
159
Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers