■
The local protocol MTU on an interface with PPP encapsulation might become
higher than the configured media MTU after the PPP negotiation when the remote
end has a higher media MTU configured. [PR/514079: This issue has been
resolved.]
■
The monitor traffic interface (tcpdump) does not produce an outbound output
with matching option when used with the encapsulation
flexibile-ethernet-services. [PR/514247: This issue has been resolved.]
Layer 2 Ethernet Services
■
The DHCPv6 clients do not bind when routing-options access-internal is
configured. [PR/495358: This issue has been resolved.]
■
On MX960 routers, i2c messages related to the fan such as the following are
displayed:
Jan 26 13:32:22 rocky-re0 /kernel: PCF8584(WR): target ack failure on byte 0
Jan 26 13:32:22 rocky-re0 /kernel: PCF8584(WR): (i2c_s1=0x08, group=0xe,
device=0x54)
This is a cosmetic issue and has no impact on the router. [PR/500824: This issue
has been resolved.]
■
The SIP domain names encoded in the DHCPv6 attributes do not conform to
RFC 3319. [PR/512073: This issue has been resolved.]
■
The JUNOS Software drops SOLICIT messages, including the rapid commit option,
instead of ignoring that option and processing the remainder of the message.
[PR/512092: This issue has been resolved.]
MPLS Applications
■
When an RSVP LSP is configured with the no-install-to-address option and is not
associated with CCC connection flaps, the routing protocol process will crash
when the LSP comes up again. To avoid the problem, make sure that the LSP is
either a transmit LSP for a CCC connection or that the install option is also
configured on the LSP. [PR/471339: This issue has been resolved.]
■
A rare condition between the MVPN and RSVP P2MP signaling leads to the
creation of stale flood next hops. [PR/491586: This issue has been resolved.]
■
An incorrectly changed LDP session authentication key causes the LDP session
to fail, which results in the LDP/IGP syncronization feature not working. The IGP
continues to advertise the link at normal metric values. [PR/499226: This issue
has been resolved.]
■
In cases where the secondary Routing Engines contain no label-switched paths
in the up state due to the lack of NSR support, such label-switched paths might
not come up even after a switchover. [PR/501969: This issue has been resolved.]
■
LDP might not handle certain error conditions gracefully when NSR is enabled.
This might cause the LDP replication state to be stuck in the "In Progress" state
forever. [PR/505043: This issue has been resolved.]
■
The name of the bypass label-switched path supports only 32 characters instead
of 64. [PR/515244: This issue has been resolved.]
76
■
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
JUNOS 10.1 Software Release Notes
