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

Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
The licenses are not synced between the master and backup Routing Engine
unless the statement is configured.
system license traceoptions file file-name
[PR/501443]
Invalid XML characters such as &#x11 (0x11) or &#20 (0x14) are allowed to be
loaded into the router. As a result, the XML parsers break as the characters are
not XML compliant. [PR/502994]
The xnm service currently does not support logging of remote-host addresses in
system accounting. [PR/535534]
VPNs
When you modify the frame-relay-tcc statement at the [edit interfaces
hierarchy level of a Layer 2 VPN, the
interface-name unit logical-unit-number]
connection for the second logical interface might not come up. As a workaround,
restart the chassis process (chassisd) or reboot the router. [PR/32763]
When you configure inter-AS VPLS with MAC processing at the autonomous
system (AS) boundary router along with multihoming, and if a designated
forwarding AS boundary router fails and then comes back up again, traffic flowing
to the local AS from the other AS's boundary router might be lost. The loss occurs
in the time period (tenths of a second) during which the old designated forwarding
AS boundary router is taking back the role of designated forwarder. [PR/312730]
On a router configured for nonstop active routing (NSR) (the nonstop-routing
statement is included at the hierarchy level), if a nonstop
[edit routing-options]
active routing switchover occurs after the configuration for routing instances
changes in certain ways, the BGP sessions between PE and CE routers might not
be established after the switchover. [PR/399275]
On MX Series, M120, and new EIII FPCs on M320 routers, the ISO/Connectionless
Network Service (CLNS) packets over the translational cross-connect (TCC) are
dropped in the case of Frame Relay, even though the family TCC has been
configured to switch family iso on the Frame Relay interface. [PR/462052]
In , , and modes, untagged
vlan-tagging stacked-vlan-tagging flexible-vlan-tagging
packets or mismatching Tag Protocol ID (TPID) packets may be dropped. These
dropped packets are not accounted for and are not visible in the CLI. This issue
is specific to the 10-port 10-Gigabit Oversubscribed Ethernet (OSE) PICs.
[PR/496190]
Under certain topologies, using NG-MVPN with the RPT-SPT mode can cause
traffic to be discarded from the RPT before the traffic starts flowing from the
SPT when the RPT is switched to SPT. [PR/529518]
If a VRF routing instance contains a static route that is resolved via a route that
was auto-exported from another routing instance, the static route may not be
removed when the physical interface goes down. [PR/531540]
When a CE-facing interface in a VPLS instance is deactivated, the routing protocol
process may get into a loop leading to a high CPU utilization. [PR/531987]
65
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers