Specifications
•
Micro BFD sessions are used to monitor the status of individual LAG member links.
When micro BFD configurations are added after the LAG bundle configuration in
separate commit, the micro BFD sessions for all the member links might remain in
"Down" state. PR1006809
•
On TX Matrix Plus routers or TX Matrix Plus routers with 3D SIBs, all the incoming
interfaces on an FPC are deactivated when none of the fabric planes are functional.
By default, the interfaces remain activated. You can enable the deactivation of
interfaces by using the fpc-restart configuration statement at the edit chassis fabric
degraded hierarchy level. PR1008726
•
If rate-limit has been configured in scheduler for MX-VC VCP ports, unified ISSU might
fail. PR1009590
•
MPLS traffic going through the ingress pre-classifier logic may not determine mpls
payload correctly classifying mpls packet into control queue versus non-control queue
and expose possible packet re-order. PR1010604
•
The fix was committed for this PR# but it also needs DDOS configuration additional
to this fix and it is as below: 1) check the "show ddos-protection protocols statistics
terse" 2) For each of the Control plane protocols on the system like ospf/vrrp/pvstp,
it is recommended to configure 2X of the rate as give below example along with
increasing DDOS rate for virtual-chassis control. Example, ######## set system
ddos-protection protocols virtual-chassis control-high bandwidth 20000 set system
ddos-protection protocols virtual-chassis control-high burst 20000 set system
ddos-protection protocols ospf aggregate bandwidth 1000 set system ddos-protection
protocols ospf aggregate burst 1000 set system ddos-protection protocols vrrp
aggregate bandwidth 100 set system ddos-protection protocols vrrp aggregate burst
100. PR1017640
•
For MX Series platform with inline Network Address Translation (NAT) service, when
using "source-prefix" or "destination-prefix" in a NAT translation rule, a pool is implicitly
created, appending "_jinpool_" with the rule name and term name with a form :
_jinpool_{rule_name}_{term_name}. The name might be cropped due to the maximum
length limitation (64 characters). If that happens, both pools might get the same name
and result in the indeterminate behavior (statistic issue, drop or incorrect translation).
PR1020033
•
Problemscenario: The error logs "CHASSISD_FCHIP_CONFIG_MD_ERROR" will appear
during FPC normal boot up time and also during FPC restart time for each plane and
for each gimlet FPC. Problem statement: Ths Error logs
"CHASSISD_FCHIP_CONFIG_MD_ERROR" are observed only in M320 chassis containing
FPCs based on Gimlet chipsets. Due to this error logs the rate limit for the fabric port
connecting the PFE 1 will be set to the default values. PR1020551
•
On MX Series based line card, if normal BFD sessions (e.g. BFD for OSPF) and micro
BFD sessions are configured over LAG, it might be seen that only micro BFD sessions
come up and other normal BFD sessions keep in down state. PR1021584
•
On MX Series based platform, with igmp-snooping enabled and a multicast route with
integrated routing and bridging (IRB) as a downstream interface, a multicast composite
nexthop is created with a list of L3 and corresponding L2 nexthops. In a rare corner
97Copyright © 2015, Juniper Networks, Inc.
Resolved Issues