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

DHCP
Enhanced Switching
Flow and Processing
Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers
Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers
On SRX210 and SRX240 devices, when autoinstallation is configured to run on
a particular interface and the default static route is set with options discard,
retain and no-advertise, then 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 of the TFTP
server being 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 options: Discard, Retain, and
No-advertise from the configuration.
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]
On J Series devices, even when forwarding options are set to drop packets for
the ISO protocol family, the device forms End System-to-Intermediate System
(ES-IS) adjacencies and transmits packets because ES-IS packets are Layer 2
terminating packets. [PR/252957]
On SRX Series devices, the
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 SRX Series devices, when traffic matches a deny policy, sessions will not be
created successfully. However, sessions are still consumed, and the
and
unicast-sessions sessions-in-use
summary command will reflect this. [PR/284299] [PR/397300]
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
in traces that are not related to the configured filter. As a workaround, use the
flow trace flag basic with the command
[PR/304083]
On SRX210, SRX240, and SRX650 devices, after the device fragments packets,
the FTP over a GRE link might not perform properly because of packet
serialization. [PR/412055]
show security flow session
fields shown by the
set security flow traceoptions flag
command currently does
show security flow session
flag might result
all
.
147