Layer 2 Ethernet Services
■
DHCP packets may not be processed on an auto-sensed VLAN interface if the
DHCP configuration for the interface is performed after the auto-sensed VLAN
interface is instantiated. As a workaround, clear the auto-sensed VLAN interface(s)
after the DHCP configuration is made for the interface(s). [PR/417958]
■
The
bpdu-block-on-edge
configuration may not work properly when the interface
is configured as 'edge' under the
[edit protocols vstp vlan
vlan-id
interface
interface-name
]
hierarchy level. [PR/522198]
MPLS Applications
■
The
rt
column in the output of the
show mpls lsp
command and the
active route
counter in the output of the
show mpls lsp extensive
command are incorrect
when the per-packet load balancing is configured. [PR/22376]
■
For point-to-multipoint label-switched paths configured for VPLS, the
ping mpls
command reports a 100 percent packet loss even though the VPLS connection
is active. [PR/287990]
■
A targeted LDP neighbor may remain up with an old IP address that was
previously in use with the loopback address on the remote neighbor. This may
happen when either of the following is performed on the remote neighbor:
■
A secondary loopback (lower than the current primary) address is added
and no primary keyword is associated with either of these addresses.
■
A second loopback address is added with the primary keyword.
This results in the targeted LDP neighbor being up with both IP addresses. The
neighbor with the old address may continue to remain up even after the old
loopback address is deleted on the remote neighbor. This neighborship with the
old address eventually times out when the router-id is changed to reflect the new
loopback address on the remote neighbor. [PR/518102]
Platform and Infrastructure
■
On T Series routers, a Layer 2 maximum transmission unit (MTU) check is not
supported for MPLS packets exiting the routing platform. [PR/46238]
■
When you configure a source class usage (SCU) name with an integer (for
example, 100) and use this source class as a firewall filter match condition, the
class identifier might be misinterpreted as an integer, which might cause the
filter to disregard the match. [PR/50247]
■
If you configure 11 or more logical interfaces in a single VPLS instance, VPLS
statistics might not be reported correctly. [PR/65496]
■
When a large number of kernel system log messages are generated, the log
information might become garbled and the severity level could change. This
behavior has no operational impact. [PR/71427]
■
In the situation where a Link Services (LS) interface to a CE router appears in
the VPN routing and forwarding table (VRF table) and a fragmentation is required,
58
■
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
JUNOS 10.1 Software Release Notes
