Unified Issu Considerations For Mx Series Routers; Unified Issu Considerations For Ptx Series Routers - Juniper EX9200 Features Manual

Unified ISSU Considerations for MX Series Routers

Unified ISSU Considerations for PTX Series Routers

Copyright © 2017, Juniper Networks, Inc.
Unified ISSU has the following caveats for MX Series routers:
On MX Series 3D Universal Edge Routers (with Modular Port Concentrator/Modular
Interface Card (MPC/MIC) interfaces), unified ISSU is supported starting with Junos OS
Release 11.2.
On MX Series 3D Universal Edge Routers with MPC3E and MPC4E interfaces, unified
ISSU is supported starting with Junos OS Release 13.3.
Unified ISSU for MX Series routers does not support the IEEE 802.1ag OAM and IEEE
802.3ah protocols.
Unified ISSU is not supported when clock synchronization is configured for Synchronous
Ethernet, Precision Time Protocol (PTP), and hybrid mode on the MICs and MPCEs on
MX240, MX480, and MX960 routers. If clock synchronization is configured, the unified
ISSU process aborts.
On MX Series routers with MPC/MIC interfaces, the policers for transit traffic and
statistics are disabled temporarily during the unified ISSU process.
On MX Series MPCs, interface-specific and firewall filter statistics are preserved across
a unified ISSU. During the unified ISSU, counter and policer operations are disabled.
To preserve statistics across a unified ISSU on MX Series routers with MPC/MIC
interfaces, the router stores the statistics data as binary large objects. The router
collects the statistics before the unified ISSU is initialized, and restores the statistics
after the unified ISSU completes. No statistics are collected during the unified ISSU
process.
After a unified ISSU operation is completed, an MPC reboot is required for MACsec to
work. If you upgrade a router from an earlier Junos OS release to Release 14.2R2 or
Release 15.1R1 using unified ISSU and MACsec is configured on that router, you must
reboot the MPC for MACsec to function properly.
When there is a large number of subscribers configured, the Layer 2 scheduler can
become oversubscribed. The unified ISSU process might abort when the system runs
out of schedulers. The system generates log messages with ISSU failures and CRC
errors on the control plane. If you encounter this issue, please contact JTAC for
assistance in eliminating the Layer 2 scheduler oversubscription in your configuration.
Unified ISSU has the following caveats for PTX Series routers:
Starting with Junos OS Release 13.2, unified ISSU is supported on the PTX5000 and
PTX 3000 with the FPC-PTX-P1-A FPC. However, you can perform unified ISSU only
from Junos OS Release 13.2 to 13.3 and from Junos OS Release 14.1 to a later release.
You must not perform unified ISSU from Junos OS Release 13.2 or 13.3 to 14.1 and later
releases.
Link Aggregation Control Protocol (LACP) is not supported during unified ISSU on PTX
Series routers. You must disable the
Chapter 16: Unified ISSU System Requirements
statement at the
lacp [edit interfaces interface-name
163