Specifications

interfaces xe-2/0/0 terse Interface Admin Link Proto Local Remote xe-2/0/0 up up
xe-2/0/0.0 up up aenet --> ae102.0 xe-2/0/0.32767 up up aenet --> ae102.32767 This
issue would be seen when associated aggregated Ethernet bundle is configured for
vlan-tagging. To clear this condition, the affected interface should be deactivated and
activated using CLI commands. user@node# deactivate interfaces xe-2/0/0
user@node# commit user@node# activate interfaces xe-2/0/0 user@node# commit
PR998246
•
In the Ethernet ring protection switching (ERPS) environment, once graceful Routing
Engine switchover (GRES) happens on the ring protection links (RPLs) owner node,
there will be a ~30s Ring automatic protection switching (R-APS) message storm in
the ring, which in turn causes some VPLS instance flapping. PR1004066
•
In BGP-VPLS scenarios with GRES activated, rpd process might crash in cycles after
manually restarting rpd. PR1011165
MPLS
•
In the MPLS environment with no-cspf and strict ERO configuration. In race condition,
if a PATH message with routing loop error is received before standby Routing Engine
has resolved the correct PATH message with no loop, some of LSP are not replicated
on standby Routing Engine. If Routing Engine switchover occurs, the forwarding traffic
might be affected. PR986714
Network Management and Monitoring
•
The Packet Forwarding Engine local protocol statistics are 32-bit counters. If there is
a rollover (typical candidates are arp/lacp), those counters start from zero. mib2d will
add all counters again if one of the pfe statistics traffic counter is less then the previous
collected counter, causing the multiplication affect. PR986712
•
Alarm management daemon runs on master and backup Routing Engines on dual
Routing Engine systems. There is a 80 megabyte alarm.db file that is copied over from
master Routing Engine to backup Routing Engine when the alarm-management daemon
has come up on both the Routing Engines. The basic issue is that alarm-management
daemon is trying to copy the alarm.db file over and over again in an infinite loop on the
system, causing CPU utilization shooting up after every 20 seconds or so. PR988969
Platform and Infrastructure
•
The error message 'unlink(): failed to delete .perm file: No such file or directory' was
logged when disconnecting from a Telnet session to the router. PR876508
•
The cprod commands essentially allow "root" access to FPCs. Therefore, access to
those commands should be highly restricted. The issue here is any user with "shell"
permission will be allowed to use cprod command. We should add restrictions to cprod
to only "root" permission users. PR924574
•
The continuous executing of CLI mib walk command might cause user being unable
to issue show commands and enter configure mode with error "Little memory remains.
Command not stored in history." PR949735
•
On MX Series platform, MPC might crash and reboot when a non-template filter gets
deleted (but does not get completely cleaned up) and the same filter index gets
107Copyright © 2015, Juniper Networks, Inc.
Resolved Issues