Specifications

Software Installation and Upgrade
•
Filesystem corruption might lead to routing engine boot up failure. This problem is
observed when directory structure on hard disk (or SSD) is inconsistent. Such a failure
should not result in boot up problem normally, but due to the software bug the affected
Junos OS releases mount /var filesystem incorrectly. The affected platforms are
M/T/MX/TX. PR905214
User Interface and Configuration
•
Selecting the Monitor port for any port in the Chassis Viewer page takes the user to
the common Port Monitoring page instead of the corresponding Monitoring page of
the selected port. PR446890
•
User needs to wait until the page is completely loaded before navigating away from
the current page. PR567756
•
Using the Internet Explorer 7 browser, while deleting a user from the Configure > System
Properties > User Management > Users page on the J-Web interface, the system is not
showing warning message, whereas in the Firefox browser error messages are shown.
PR595932
•
If you access the J-Web interface using the Microsoft Internet Web browser version 7,
on the BGP Configuration page (Configure > Routing > BGP), all flags might be shown
in the Configured Flags list (in the Edit Global Settings window, on the Trace Options
tab) even though the flags are not configured. As a workaround, use the Mozilla Firefox
Web browser. PR603669
•
On the J-Web interface, next hop column in Monitor > Routing > Route Information
displays only the interface address and the corresponding IP address is missing. The
title of the first column displays "static route address" instead of "Destination Address."
PR684552
VPNs
•
When you modify the frame-relay-tcc statement at the [edit interfaces interface-name
unit logical-unit-number] hierarchy level of a Layer 2 VPN, the connection for the
second logical interface might not come up. As a workaround, restart the chassis
process (chassisd) or reboot the router. PR32763
•
BGP community 0xFF04 (65284) is a well known community (NOPEER), but it is
incorrectly displayed as "mvpn-mcast-rpt" in the cli command "show route". This is a
show command issue only. No operational mis-behavior will be observed on the
router/network. PR479156
•
In the Rosen MVPN environment, the RP-PE is an assert loser, another PE is sending
traffic over the data-mdt. If a new receiver PE with higher rate comes up, because
internal workflow processes wrong, the receiver PE might reset data-mdt. This leads
to traffic loss. PR999760
•
In NG-MVPN scenario with multiple source PEs for a same group, if an inactive source
PE has local receivers, the routing protocol process (rpd) on this PE might cause
multicast traffic loss and continuous IFF-MISMATCH error. PR1009215
79Copyright © 2015, Juniper Networks, Inc.
Known Issues