Specifications

Software Installation and Upgrade
•
Routing Engine could be brought to DB mode when rebooting after interrupted
downgrade. PR966462
•
By upgrade-with-config, user can specify a configuration to be applied on upgrade,
but the configuration file will not be loaded post upgrading. As a result, router will bring
up with old configuration. PR983291
Subscriber Access Management
•
In early Release 13.3 code, if NSR and 64-bit rpd are used, there is a chance that the
Routing Engine may lose the primary floating IP address assigned to both Routing
Engine after a couple of GRES Routing Engine switchovers. This issue had been
corrected in later Release 13.3 branch codes. PR973278
User Interface and Configuration
•
When load large scale configuration, due to the ddl object not being freed properly
after it's accessed, load configuration failed with error: Out of object identifiers.
PR985324
VPNs
•
Upon withdraw /inject bgp routes in the serving PEs for two different
route-groups,member/regular sites receive traffic from both serving sites for 60
seconds. PR973623
•
Route group member site and regular site may receive data from two serving sites of
two groups for the same (S,G). This only happens when in one RG there are no receivers.
PR974245
•
In Rosen MVPN environment, if there a two multihomed ingress PEs, when the route
to multicast source flaps, the receiver router might keep switching between sender
Data MDTs, which resulting in traffic loss. PR974914
•
In the Rosen MVPN environment, setting the TOS IP control packet bit can avoid the
possibility of data-mdt TLV messages being dropped in the core during congestion.
But in this case, the TOS field to indicate its IP control packet (0xc0) is not set. This
might lead to traffic loss. PR981523
•
The S-PMSI tunnel might fail to be originated from ingress PE after flapping the routes
to customer multicast source. PR983410
•
In MVPN scenario, a multihomed ingress PE might fail to advertise type-4 after losing
routes to local sources. PR984946
•
In AT route-group scenario, source route is flapped on preferred serving site. After that
the member site fails to originate type-4 even though it has type-5 and type-3 from
non-preferred serving sites. PR994687
125Copyright © 2015, Juniper Networks, Inc.
Resolved Issues