the Packet Forwarding Engine does not receive the expected sequence, and the
FPC will crash. [PR/499315: This issue has been resolved.]
■
On IQ2 PICs, when copy-plp is enabled under class of service, the DCU provides
the wrong statistics. [PR/499378: This issue has been resolved.]
■
The MAC address of a configured static NDP entry is overwritten upon receiving
NA from a connected device. [PR/499418: This issue has been resolved.]
■
The static NDP entry remains permanent if the refcount is more than 1, even
after deleting the static configuration. [PR/499441: This issue has been resolved.]
■
The L2RW does not report an error when the required L2_pgm length is longer
than what the hardware can support. [PR/501318: This issue has been resolved.]
■
On an ichip platform, when the downstream multicast member link flaps, the
Packet Forwarding Engine rarely has a chance to fail multicast next-hop handling.
This can cause multicast traffic drops. [PR/501852: This issue has been resolved.]
■
On an MX Series router configured for PPP subscriber access, subscribers will
experience slow login times as the number of subscriber sessions increases.
[PR/502756: This issue has been resolved.]
■
RED drops occur in the SMQCHIP when the 10x10GE OSE and 4x10GE PICs are
swapped multiple times. [PR/506174: This issue has been resolved.]
■
On a TX Matrix Plus router, if one of the two external RJ45 links between a
TXP-CIP and an LCC Control Board is broken, the router does not generate an
alarm. [PR/508219: This issue has been resolved.]
■
On tcpdump or when the
monitor traffic interface
command is used for an lo0
interface with the IP address having its last octet is greater than or equal to 224
(x.x.x.224 or higher), following message is received: "inet class for 0xe1e11955
unknown." [PR/511911: This issue has been resolved.]
Routing Protocols
■
If a static route points to a discard configuration, a failure might occur when the
router attempts to collect the multicast statistic data. [PR/434298: This issue has
been resolved.]
■
Deleting a logical system causes the routing protocol process to be stuck in an
infinite loop. [PR/439000: This issue has been resolved.]
■
The routing protocol process dumps core due to a soft assertion failed:
"rt_notbest_sanity: Path selection failure" in rt_table.c. As a workaround, use
the
bgp path-selection external-router-id
statement or the
bgp path-selection
always-compare-med
statement. [PR/451021: This issue has been resolved.]
■
When a PIC with a PIM-enabled interface is brought online, the router may send
the first PIM hello slightly before the interface comes up. This causes the router
to drop the first PIM hello message towards its neighbor. [PR/482903: This issue
has been resolved.]
■
After a graceful Routing Engine switchover (GRES) event with NSR enabled and
a scaled L3VPN eBGP test, some BGP sessions fail due to an expired hold down
timer if the hold-down timer is lower than the default 30 seconds. To avoid this
issue, set the hold-down timer to the default value of 30 seconds. [PR/501796:
This issue has been resolved.]
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
■
71
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
