Specifications

changing gigether-options of core router facing interface multiple times continuously,
the Flexible PIC Concentrator (FPC) CPU utilization might increase to 100%, and then
FPC might crash. PR961473
•
On an MX Series router with dynamic vlan scenario, when improper sort order data is
sent to dynamic vlan on the Packet Forwarding Engine, the Modular Port Concentrator
(MPC) might crash and generate core files. PR961645
•
For MXVC platform, the pfe reconnect timer extends from the default 15s to 60s
temporarily. This will be reversed once Packet Forwarding Engine connection issues
resolved. PR963576
•
Display issue only. "show route cumulative vpn-family" command is using "inet.6" for
vpnv6 routes instead of inet6.0. PR966828
•
Destination alarms are cleared after fabric event even though destination errors are
present in the system. PR967013
•
NH tracing provides a lightweight mechanism to capture NH chains traversed by packets
of interest for further examination. PR967450
High Availability (HA) and Resiliency
•
/var/log/messages is getting filled up with following GRES related messages. These
are harmless and due to the log level(info). *** messages *** Dec 1 22:46:49.201 re0
/kernel: update_slave_peer_gres_status: vksid 0 is_slave_peer_gres_ready 1
is_local_slave_peer_gres_ready 0 Dec 1 22:46:49.201 re0 /kernel: vks[0] 1 vks[1] 0 Dec
1 22:46:49.201 re0 /kernel: PFE-MASTER - vks[0] 1 vks[1] 0 Dec 1 22:46:49.201 re0
/kernel: Slave is ready for GRES for vksid 0 Dec 1 22:46:49.201 re0 /kernel:
update_slave_peer_gres_status: vksid 0 is_slave_peer_gres_ready 1
is_local_slave_peer_gres_ready 0 Dec 1 22:46:49.201 re0 /kernel: vks[0] 1 vks[1] 0 Dec
1 22:46:49.201 re0 /kernel: PFE-MASTER - vks[0] 1 vks[1] 0 Dec 1 22:46:49.201 re0
/kernel: Slave is ready for GRES for vksid 0 Dec 1 22:46:49.401 re0 /kernel:
update_slave_peer_gres_status: vksid 0 is_slave_peer_gres_ready 1
is_local_slave_peer_gres_ready 0 Dec 1 22:46:49.401 re0 /kernel: vks[0] 1 vks[1] 0 Dec
1 22:46:49.401 re0 /kernel: PFE-MASTER - vks[0] 1 vks[1] 0 Dec 1 22:46:49.401 re0
/kernel: Slave is ready for GRES for vksid 0 Dec 1 22:46:53.000 re0 /kernel:
update_slave_peer_gres_status: vksid 0 is_slave_peer_gres_ready 1
is_local_slave_peer_gres_ready 0 Dec 1 22:46:53.000 re0 /kernel: vks[0] 1 vks[1] 0 Dec
1 22:46:53.000 re0 /kernel: PFE-MASTER - vks[0] 1 vks[1] 0 Dec 1 22:46:53.000 re0
/kernel: Slave is ready for GRES for vksid 0 PR918075
•
When performing a unified in-service software upgrade (ISSU) validate against a router
with ISSU unsupported hardware equipped, the unsupported hardware is being taken
offline, as if an actual ISSU is being performed. In addition, the unsupported hardware
is still offline after the ISSU validate is completed. The workaround is rebooting or
executing CLI commands to bring the offline hardware back online. PR949882
Copyright © 2015, Juniper Networks, Inc.128
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series