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

JUNOS 10.1 Software Release Notes
148
Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers
On SRX240 devices, traffic flooding occurs when multiple multicast IP group
addresses are mapped to the same multicast MAC address because multicast
switching is based on the Layer 2 address. [PR/418519]
On SRX650 devices, the input DA errors are not updated when packets are
dropped because of MAC filtering on the following:
SRX240 device
SRX210 device
16-port and 24-port GPIMs
SRX650 front-end port
This is due to MAC filtering implemented in hardware.
[PR/423777]
On SRX650 devices, the uplinks to the CPU can be exhausted and the system
can be limited to 2.5 GB throughput traffic when the device is using similar kinds
of source MAC addresses. [PR/428526]
On SRX5600 and SRX5800 devices, the network processing bundle configuration
CLI does not check if PICs in the bundle are valid. [PR/429780]
On SRX650 devices, packet loss is observed when the device interoperates with
an SSG20 with AMI line encoding. [PR/430475]
On an SRX210 on-board Ethernet port, an IPv6 multicast packet received gets
duplicated at the ingress. This happens only for IPv6 multicast traffic in ingress.
[PR/432834]
On SRX3400 and SRX3600 devices, the ramp rate of session creation is slow at
times for fragmented UDP traffic. [PR/434508]
On SRX5800 devices, when there are nonexistent PICs in the network processing
bundle, the traffic is sent out to the PICs and is lost. [PR/434976]
The SRX5600 and SRX5800 devices create more than the expected number of
flow sessions with NAT traffic. [PR/437481]
On J Series devices, NAT traffic that goes to the WXC ISM 200 and return back
clear (that is, not accelerated by the WXC ISM 200) does not work. [PR/438152]
On SRX3400, SRX3600, SRX5600, and SRX5800 devices, there is missing
information in the jnxJsFwAuthMultipleFailure trap
required to contain the username, IP address, application, and trap name, but
the username is missing. [PR/439314]
On SRX5800 devices, for any network processing bundle configuration change
to take effect, a reboot is needed. Currently there is no message displayed after
a bundle configuration change. [PR/441546]
On SRX5800 devices, the IOC hot swap is not supported with network processing
bundling. If an IOC that has network processing bundling configured gets
unplugged, all traffic to that network processor bundle will be lost. [PR/441961]
On SRX5800 devices with interfaces in a network processing bundle, the ICMP
flood or UDP flood cannot be detected at the threshold rate. However, it can be
message. The trap message is