EasyManua.ls Logo

Juniper JUNOS OS 10.4 - RELEASE NOTES - Page 146

Juniper JUNOS OS 10.4 - RELEASE NOTES
197 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Dynamic Host Configuration Protocol (DHCP)
On SRX210 and SRX240 devices, when autoinstallation is configured to run on a
particular interface and the default static route is set with the options discard, retain,
and no-advertise, the DHCP client running on the interface tries fetching the
configuration files from the TFTP server. During this process, the UDP data port on the
TFTP server might be unreachable. Because the TFTP server is unreachable, the
autoinstallation process might remain in the configuration acquisition state. When
autoinstallation is disabled, the TFTP might fail. In this case, you should manually fetch
the file from the server or the client through the relay.
As a workaround, remove the static route discard, retain, and no-advertise options
from the configuration. [PR/454189]
Enhanced Switching
On J Series devices, if the access port is tagged with the same VLAN that is configured
at the port, the access port accepts tagged packets and determines the MAC.
[PR/302635]
Flow and Processing
On SRX Series devices, the show security flow session command currently does not
display aggregate session information. Instead, it displays sessions on a per-SPU basis.
[PR/264439]
On J Series devices, OSPF over a multipoint interface connected as a hub-and-spoke
network does not restart when a new path is found to the same destination.
[PR/280771]
On J Series devices, outbound filters will be applied twice for host-generated IPv4
traffic. [PR/301199]
On SRX Series devices, configuring the flow filter with the all flag might result in traces
that are not related to the configured filter. As a workaround, use the flow trace flag
basic with the command set security flow traceoptions flag.
NOTE: Be sure to disable flow traceoptions after debugging has been
completed. Flow traceoptions might cause high CPU utilization in the
Routing Engine.
[PR/304083]
On SRX240 devices, traffic flooding occurs when multiple multicast (MC) IP group
addresses are mapped to the same 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
Copyright © 2010, Juniper Networks, Inc.146
JUNOS OS 10.4 Release Notes

Table of Contents

Related product manuals