MPLS Applications
■
No point-to-multipoint LSPs are reported when the
show mpls lsp p2mp
command
is issued. As a workaround, execute the
show mpls lsp
command before you
execute the
show mpls lsp p2mp
command. [PR/266343: This issue has been
resolved.]
■
Constrained Shortest Path First (CSPF) fails to calculate a P2MP LSP reroute path
merging upon a user configuration change. [PR/454692: This issue has been
resolved.]
■
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 traffic engineered label-switched path that is down might not get re-signaled.
[PR/478375: This issue has been resolved.]
■
While performing an MPLS LDP traceroute in a tunneled MPLS LDP environment,
all hops except the second hop show 127.0.0.1 as the router hop. [PR/486999:
This issue has been resolved.]
■
The NGEN-MVPN multicast traffic might be dropped at the ingress router if a
point-to-multipoint LSP reoptimization is performed. [PR/491533: 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.]
■
Under some circumstances where LDP is enabled, a memory leak might occur
where the routing protocol process does not free up memory. [PR/493885: This
issue has been resolved.]
■
An incorrectly changed LDP session authentication key causes the LDP session
to fail, and the LDP/IGP syncronization feature stops working. The IGP continues
to advertise the link at normal metric values. [PR/499226: 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
show route table mpls.0 label-switched-path
lspname
command may cause
the routing protocol process to core if no route is found. [PR/507239: This issue
has been resolved.]
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
■
87
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
