Issues In Junos Os Release 10.4 For Srx Series Services Gateways And J Series Services Routers; Outstanding Issues In Junos Os Release 10.4 For Srx Series Services Gateways And J Series Services Routers - Juniper JUNOS OS 10.4 - RELEASE NOTES Release Note

Issues in Junos OS Release 10.4 for SRX Series Services Gateways and J Series Services Routers

Copyright © 2010, Juniper Networks, Inc.
Issues in Junos OS Release 10.4 for SRX Series Services Gateways and J Series Services Routers
Outstanding Issues In Junos OS Release 10.4 for SRX Series Services Gateways and J
Series Services Routers on page 143
Resolved Issues in Junos OS Release 10.4 for SRX Series Services Gateways and J
Series Services Routers on page 161
Outstanding Issues In Junos OS Release 10.4 for SRX Series Services Gateways
and J Series Services Routers
The following problems currently exist in SRX Series and J Series devices. The identifier
following the description is the tracking number in our bug database.
Application Layer Gateways (ALGs)
On SRX5600 devices, if you run the
doing a bulk call generation, it might bring down the SPU with a flowd core file error.
[PR/292956]
On SRX Series devices, SIP server protection does not work. The
application-screen protect deny
On J4350 devices in a NAT-PT environment, when the client is in an IPv6 environment
and the DNS server is in an IPv4 environment, the DNS server will have only the IPv4
address record. When the client looks up the IPv6 address of the record in the DNS
server, DUT performs NAT-PT on the DNS ALG. When the client executes the lookup
action several times, a core file error is returned. As a workaround, do not perform the
lookup action when the DNS server has only an IPv4 address record. [PR/533345]
Authentication
On J Series devices, after the user is authenticated, if the
changed and an entry exists in the firewall authentication table, then an authentication
entry created as a result of
for that entry. Otherwise, the
This behavior will not cause a security breach. [PR/309534]
AX411 Access Point
On SRX210 PoE devices, the access point reboots when 100 clients are associated
simultaneously and each one is transmitting 512-byte packets at 100 pps. [PR/469418]
On SRX650 devices, when an access point is part of the default cluster and you change
the default cluster after the access point is connected to it, the changes might not be
reflected. As a workaround, restart the wireless LAN service. [PR/497752]
Chassis Cluster
On J Series devices in a chassis cluster, a high load of SIP ALG traffic might result in
some call leaks in active resource manager groups and gates on the backup router.
[PR/268613]
On SRX3400, SRX3600, SRX5600, and SRX5800 devices, 8-queue configurations
are not reflected on the chassis cluster interface. [PR/389451]
show security alg sip counters
command does not work. [PR/512202]
will be deleted only if a traffic flow session exists
webauth
entry will not get deleted and will only age out.
webauth
command while
set security alg sip
webauth-policy is deleted or
143