Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Unified ISSU System Requirements

SUMMARY Unified in-service software upgrade (ISSU) requires you to meet the device and configuration requirements listed below.

The unified in-service software upgrade (ISSU) feature enables you to upgrade your device between two different Junos OS releases with no disruption on the control plane and with minimal disruption of traffic. Unified ISSU is supported only on dual Routing Engine platforms. In addition, the graceful Routing Engine switchover (GRES) and nonstop active routing (NSR) features must be enabled.

To access an interactive tool for verifying hardware support for unified ISSU, see the Juniper Networks Feature Explorer.

This section contains the following topics:

General Unified ISSU Considerations for All Platforms

Unified ISSU has the following caveats:

  • To upgrade to Junos OS Releases 21.2R1 or 22.1R1, you need to include the no-validate option when issuing the in-service-upgrade command. The syntax for this command is request system software in-service-upgrade /var/tmp/package-name.tgz no-validate

    Junos OS releases prior to 20.4R2 do not support the no-validate option with unified ISSU. In order to upgrade from an older release to Junos OS Releases 21.2R1 or 22.1R1 with unified ISSU, you must first upgrade to a release that supports the no-validate option for unified ISSU, such as 20.4R2.

  • We recommend that you not use unified ISSU to upgrade from an earlier Junos OS release to Junos OS Release 14.2.R1 or 15.1.R1. ISSU is not supported in Junos OS Release 14.2. For more information about Junos OS Release 14.2, see the Release Notes for Junos OS Release 14.2. For more information about Junos OS Release 15.1, see the Release Notes for Junos OS Release 15.1.

  • Using unified ISSU to upgrade from an earlier Junos OS release to Junos OS Release 17.1R1 or later does not work if VPLS dynamic profiles are configured and enhanced subscriber management is not configured.

  • The primary Routing Engine and backup Routing Engine must be running the same software version before you can perform a unified ISSU.

  • The unified ISSU process is terminated and a message is displayed if the Junos OS version specified for installation is a version earlier than the one currently running on the device.

  • The unified ISSU process is terminated if the specified upgrade has conflicts with the current configuration, components supported, and so forth.

  • You cannot take PICs offline or bring them online during a unified ISSU.

  • User-initiated GRES is blocked when the device is undergoing a unified ISSU.

  • Unified ISSU does not support extension application packages developed with the Junos SDK.

  • To downgrade from a unified ISSU-capable release to a previous software release (unified ISSU-capable or not), use the request system software add package-name command. Unlike an upgrade using the unified ISSU process, a downgrade using the request system software add package-name command can cause network disruptions and loss of data. For more information about the use of the request system software add package-name command, see the Junos OS Software Installation and Upgrade Guide.

  • Unicast reverse-path-forwarding (RPF)-related statistics are not saved across a unified ISSU, and the unicast RPF counters are reset to zero during a unified ISSU.

  • BGP session uptime and downtime statistics are not synchronized between the primary and backup Routing Engines during a unified ISSU. The backup Routing Engine maintains its own session uptime based on the time when the backup first becomes aware of the established sessions. For example, if the backup Routing Engine is rebooted (or if you run restart routing on the backup Routing Engine), the backup Routing Engine uptime is a short duration, because the backup has just learned about the established sessions. If the backup is operating when the BGP sessions first come up on the primary, the uptime on the primary and the uptime on the backup are almost the same duration. After a Routing Engine switchover, the new primary continues from the time left on the backup Routing Engine.

  • If proxy ARP is enabled on your device, you must delete the unconditional-src-learn statement from the [edit interfaces interface-name unit 0 family inet] hierarchy level before the unified ISSU process begins and include it after the unified ISSU process is complete. Note that the unconditional-src-learn statement is not included by default.

Unified ISSU Considerations for MX Series Routers

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 is supported with Junos OS Release 17.4R1 for MX Series routers with MPC-3D-16XGE-SFPP, MPC-3D-NG, MPC-3D-16XGE-SFPP-R-B, MPC-SEPTUM-S, MPC2E-3D-NG, MPC2E-3D-NG-IR-B, MPC2E-3D-NG-Q, MPC2E-3D-NG-Q-IR-B, MPC2E-3D-NG-Q-R-B, MPC2E-3D-NG-R-B, MPC3E-3D-NG, MPC3E-3D-NG-IR-B, MPC3E-3D-NG-Q, MPC3E-3D-NG-Q-IR-B, MPC3E-3D-NG-Q-R-B, MPC3E-3D-NG-R-B, MPC4E-3D-2CGE-8XGE, MPC4E-3D-2CGE8XGE-IR-B, MPC4E-3D-2CGE8XGE-R-B, MPC4E-3D-32XGE-IR-B, MPC4E-3D-32XGE-R-B, MPC4E-3D-32XGE-SFPP, MPC5E-100G10G, MPC5E-100G10G-IRB, MPC5E-100G10G-RB, MPC5E-40G10G, MPC5E-40G10G-IRB, MPC5E-40G10G-RB, MPC5EQ-100G10G, MPC5EQ-100G10G-IRB, MPC5EQ-100G10G-RB, MPC5EQ-40G10G, MPC5EQ-40G10G-IRB, MPC5EQ-40G10G-RB, MPC7E-10G, MPC7E-10G-IRB, MPC7E-10G-RB, MPC7E-MRATE, MPC7E-MRATE-IRB, MPC7E, MRATE-RB, MPC7EQ-10G-B, MPC7EQ-10G-IRB, MPC7EQ-10G-RB, MPC7EQ-MRATE-B, MPC7EQ-MRATE-IRB, MPC7EQ-MRATE-RB Flexible Port Concentrators (FPCs). If you perform a unified ISSU on a MX Series router with these FPCs installed, the FPCs need to be rebooted in order to complete the unified ISSU process.

  • 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 terminates.

    Note:

    For Junos OS Releases 22.1R1 and above, you can use the request system software in-service-upgrade command with the handle-incompatible-config option to automatically deactivate/activate clock synchronization for PTP and Synchronous Ethernet on the MX960, MX10003, MX10008, MX10016, MX2010, and MX2020 routers.

  • 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 terminate 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.

  • MX Series routers support Link Aggregation Control Protocol (LACP) with fast hellos during unified ISSU. This support is disabled by default. You must enable the fast-hello-issu option on the main router and on the peer routers before starting unified ISSU. Note that the peer router must also be an MX Series router for this functionality to work.

Unified ISSU Considerations for PTX Series Routers

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 PTX3000 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 lacp statement at the [edit interfaces interface-name aggregated-ether-options] hierarchy level before the unified ISSU process begins and enable it after the unified ISSU process is complete.

Unified ISSU Considerations for T Series Routers

Unified ISSU has the following caveats for T Series devices:

  • During the unified ISSU process on a routing matrix with TX Matrix Plus routers with 3D SIBs, only 75 percent of the traffic remains uninterrupted.

  • The scale supported on T640-FPC2-E, T640-FPC2-E2, T640-FPC3-E, and T640-FPC3-E2 Flexible Port Concentrators (FPCs) is less than that supported on T640-FPC1-ES, T640-FPC2-ES, T640-FPC3-ES, T1600-FPC4-ES, and T640-FPC4-1P-ES FPCs because of differences in hardware configuration. Therefore, when a unified ISSU is performed, if the configured scale on any of the FPCs is more than what is supported on that FPC, field-replaceable unit (FRU) upgrade of that FPC fails. To check the current hardware configuration of an FPC, use the show chassis fpc operational command.

  • The PD-4XGE-XFP PIC goes offline during a unified ISSU if the PIC is installed in a T-1600-FPC4-ES with part number 710-013037 revision 12 or earlier.

  • In the FPCs on T4000 routers, 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 T4000 routers with FPC/PIC 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.

  • To verify that statistics are preserved across the unified ISSU, you can issue CLI operational commands such as show interfaces statistics after the unified ISSU completes.

  • When you configure the unified ISSU feature on the T4000 Core Router, you can also configure LACP. However, LACP periodic fast mode is not supported. If you configure LACP periodic transmission, set it to slow mode at both sides before initiating a unified ISSU. If fast mode is configured, the configuration can be committed without any commit or system log error messages, but you might notice that a larger than expected amount of traffic drops because of the LACP links going down during a unified ISSU.

Unified ISSU Considerations for EX Series Switches

Unified ISSU has the following caveats for EX Series devices:

  • EX9204, EX9208, EX9214, and EX9251, and EX9253 switches do not support LACP fast timer configuration starting with Junos OS Release 17.4. If the LACP fast timer is configured, there will be LAG interface flaps traffic loss during ISSU. We recommend moving to LACP slow before beginning ISSU on these devices.

Unified ISSU Platform Support

Table 1 lists the platforms that support unified ISSU when dual Routing Engines are installed and the first Junos OS release that supports unified ISSU on those platforms. In addition to verifying that your platform supports unified ISSU, you need to verify that the field-replaceable unit, such as PICs, that are installed also support unified ISSU.

To access an interactive tool for verifying hardware support for unified ISSU, see the Juniper Networks Feature Explorer (https://pathfinder.juniper.net/feature-explorer/).

Table 1: Unified ISSU Support for Dual Routing Engine Platforms

Platform

Junos OS Release

EX9200 switch

  • 12.3R3 or later

  • 14.2R1 or later on EX9200-32XS, EX9200-4QS, and EX9200-2C-8XS

  • 17.1R1 or later on EX9200-6QS

M10i router

9.5R1

M120 router

9.2R1

M320 router

9.0R1

MX240 router

9.3R1

MX480 router

9.3R1

MX960 router

9.3R1

MX2010 router

13.2R1

MX2020 router

13.2R1

MX104 router

14.1R1

MX Series Virtual Chassis

14.1R1

MX10003 router

18.2R1

PTX5000 router

13.2R1

PTX3000 router

13.2R1

T320 router

9.0R1

T640 router

9.0R1

T1600 router

9.1R1

T4000 router

12.3R1

TX Matrix router

9.3R1

TX Matrix Plus router

12.3R2

TX Matrix Plus routers with 3D SIBs

14.1R1

Unified ISSU Protocol Support for M Series, MX Series, and T Series Routers and EX9200 Switches

To find out which releases support ISSU, please use the ISSU Feature Explorer tool on the Juniper Networks website. The ISSU Feature Explorer tool contains information about the Juniper Networks devices that support ISSU, the releases that support ISSU for each device, and the SKUs that support ISSU for each release.

Note:

To gain access to the ISSU Feature Explorer tool, you need to log in with a customer or partner account on the Juniper Networks website. For more information on setting up a Juniper Networks account, please see the Juniper Networks Guide to Creating a User Account.

Unified ISSU Feature Support

Unified ISSU supports most Junos OS features starting in Junos OS Release 9.0. However, the following constraints apply:

  • Link Aggregation Control Protocol (LACP)—Link changes are not processed until after the unified ISSU is complete.

  • Automatic Protection Switching (APS)—Network changes are not processed until after the unified ISSU is complete.

  • Ethernet Operation, Administration, and Management (OAM) as defined by IEEE 802.3ah and by IEEE 802.1ag—When a Routing Engine switchover occurs, the OAM hello message times out, triggering protocol convergence.

  • Ethernet circuit cross-connect (CCC) encapsulation—Circuit changes are not processed until after the unified ISSU is complete.

  • Logical systems—On devices that have logical systems configured on them, only the primary logical system supports unified ISSU.

    Note:

    Starting with Junos OS Release 16.1R1, while performing a unified ISSU from a FreeBSD 6.1-based Junos OS to an upgraded FreeBSD 10.x-based Junos OS, the configuration must be validated on a remote host or on a Routing Engine. The remote host or the Routing Engine must be running a Junos OS with an upgraded FreeBSD. In addition, only a few selected directories and files are preserved while upgrading from FreeBSD 6.1-based Junos OS to FreeBSD 10.x-based Junos OS. See Upgrading Junos OS with Upgraded FreeBSD.

Unified ISSU PIC Support Considerations

The following sections list the PICs that are supported by unified ISSU.

Note:

For information about ISSU support on individual PICs based on device and release, use the ISSU Feature Explorer tool.
Note:

For information about Flexible PIC Concentrator (FPC) types, FPC/PIC compatibility, and the initial Junos OS release in which a particular PIC is supported on an FPC, see the PIC guide for your platform.

PIC Considerations

Take the following PIC restrictions into consideration before performing a unified ISSU:

  • Unsupported PICs—If a PIC is not supported by unified ISSU, at the beginning of the upgrade, the software issues a warning that the PIC will be taken offline. After the PIC is brought offline and the unified ISSU is complete, the PIC is brought back online with the new firmware.

  • PIC combinations—For some PICs, newer Junos OS services can require significant Internet Processor ASIC memory, and some configuration rules might limit certain combinations of PICs on particular platforms. With a unified ISSU:

    • If a PIC combination is not supported by the software version that the device is being upgraded from, the validation check displays a message and terminates the upgrade.

    • If a PIC combination is not supported by the software version to which the device is being upgraded, the validation check displays a message and terminates the upgrade, even if the PIC combination is supported by the software version from which the device is being upgraded.

  • Interface statistics—Interface statistics might be incorrect because:

    • During bootup of the new microkernel on the Packet Forwarding Engine, host-bound traffic is not handled and might be dropped, causing packet loss.

    • During the hardware update of the Packet Forwarding Engine and its interfaces, traffic is halted and discarded. (The duration of the hardware update depends on the number and type of interfaces and on the device configuration.)

    • During a unified ISSU, periodic statistics collection is halted. If hardware counters saturate or wrap around, the software does not display accurate interface statistics.

  • CIR oversubscription—If oversubscription of the committed information rate (CIR) is configured on logical interfaces:

    • And the sum of the CIR exceeds the physical interface's bandwidth, after a unified ISSU is performed, each logical interface might not be given its original CIR.

    • And the sum of the delay buffer rate configured on logical interfaces exceeds the physical interface's bandwidth, after a unified ISSU is performed, each logical interface might not receive its original delay-buffer-rate calculation.

SONET/SDH PICs

Table 2 lists the SONET/SDH PICs that are supported during a unified ISSU.

Table 2: Unified ISSU PIC Support: SONET/SDH

PIC Type

Number of Ports

Model Number

Device

OC3c/STM1

4

PB-4OC3-SON-MM—(EOL)

PB-4OC3-SON-SMIR—(EOL)

M120 M320, T320, T640, T1600

PE-4OC3-SON-MM—(EOL)

PE-4OC3-SON-SMIR—(EOL)

M10i

2

PE-2OC3-SON-MM—(EOL)

PE-2OC3-SON-SMIR—(EOL)

OC3c/STM1 with SFP

2

PE-2OC3-SON-SFP

M10i

OC3c/STM1, SFP (Multi-Rate)

4 OC3 ports, 4 OC12 ports

PB-4OC3-4OC12-SON-SFP

M120 M320, MX Series, T320, T640, T1600, T4000, TX Matrix Plus, TX Matrix Plus with 3D SIBs

4 OC3 ports, 1 OC12 port

PB-4OC3-1OC12-SON-SFP

PB-4OC3-1OC12-SON2-SFP

PE-4OC3-1OC12-SON-SFP

M10i

OC12c/STM4

1

PE-1OC12-SON-SFP

PE-1OC12-SON-MM—(EOL)

PE-1OC12-SON-SMIR—(EOL)

M10i

PB-1OC12-SON-MM—(EOL)

PB-1OC12-SON-SMIR—(EOL)

M120, M320, T320, T640, T1600, T4000, TX Matrix, TX Matrix Plus with 3D SIBs

4

PB-4OC12-SON-MM

PB-4OC12-SON-SMIR

OC12c/STM4, SFP

1

PB-1OC12-SON-SFP

M120, M320, T320, T640, T1600, TX Matrix, TX Matrix Plus

OC48c/STM16, SFP

1

PB-1OC48-SON-SFP

PB-1OC48-SON-B-SFP

M120, M320, MX Series, T320, T640, T1600, TX Matrix, T4000, TX Matrix Plus, TX Matrix Plus with 3D SIBs

4

PC-4OC48-SON-SFP

OC192/STM64

1

PC-1OC192-SON-VSR

MX Series routers

OC192/STM64, XFP

1

PC-1OC192-SON-LR

PC-1OC192-SON-SR2

PC-1OC192-VSR

M320, T320, T640, T1600, T4000, TX Matrix Plus with 3D SIBs

OC192/STM64, XFP

4

PD-4OC192-SON-XFP

M120, T640, T1600, T4000, TX Matrix Plus with 3D SIBs

1

PC-1OC192-SON-XFP

T4000, MX Series routers, TX Matrix Plus with 3D SIBs

OC768/STM256

1

PD-1OC768-SON-SR

T640, T1600, T4000, TX Matrix Plus, TX Matrix Plus with 3D SIBs

Fast Ethernet and Gigabit Ethernet PICs

Table 3 lists the Fast Ethernet and Gigabit Ethernet PICs that are supported during a unified ISSU.

Note:

Starting with Junos OS Release 9.2, new Ethernet IQ2 PIC features might cause the software to reboot the PIC when a unified ISSU is performed. For information about applicable new Ethernet IQ2 PIC features, refer to the release notes for the specific Junos OS release.

Table 3: Unified ISSU PIC Support: Fast Ethernet and Gigabit Ethernet

PIC Type

Number of Ports

Model Number

Device

Fast Ethernet

4

PB-4FE-TX

M120, M320, T320, T640, T1600, TX Matrix

PE-4FE-TX

M10i

8

PB-8FE-FX

M120, M320

PE-8FE-FX

M10i

12

PB-12FE-TX-MDI

PB-12FE-TX-MDIX

M120, M320, T320

PE-12FE-TX-MDI

PE-12FE-TX-MDIX

M10i

48

PB-48FE-TX-MDI

PB-48FE-TX-MDIX

M120, M320, T320

Gigabit Ethernet, RJ-45

40

EX9200-40T

EX9200

Gigabit Ethernet, SFP

1

PE-1GE-SFP

M10i

PB-1GE-SFP

M120, M320, T320, T640, T1600, T4000, TX Matrix, TX Matrix Plus, TX Matrix Plus with 3D SIBs

2

4

PB-2GE-SFP

PB-4GE-SFP

10

PC-10GE-SFP

40

EX9200-40F

EX9200

Gigabit Ethernet IQ, SFP

1

PE-1GE-SFP-QPP

M10i

PB-1GE-SFP-QPP

M120, M320, T320, T640, T1600, T4000, TX Matrix, TX Matrix Plus, TX Matrix Plus with 3D SIBs

2

PB-2GE-SFP-QPP

Gigabit Ethernet IQ2, SFP

4

PB-4GE-TYPE1-SFP-IQ2

M120, M320, T320, T640, T1600, T4000, TX Matrix, TX Matrix Plus, TX Matrix Plus with 3D SIBs

8

PB-8GE-TYPE2-SFP-IQ2

PC-8GE-TYPE3-SFP-IQ2

Gigabit Ethernet IQ2, XFP

1

PC-1XGE-TYPE3-XFP-IQ2

M120, M320, T320, T640, T1600, TX Matrix, TX Matrix Plus, TX Matrix Plus with 3D SIBs

10-Gigabit Ethernet XFP

4

PD-4XGE-XFP

Note:

This PIC goes offline during a unified ISSU if the PIC is inserted on T-1600-FPC4-ES with part number 710-013037 revision 12 or below.

T640, T1600, T4000, TX Matrix, TX Matrix Plus, TX Matrix Plus with 3D SIBs

10-Gigabit Ethernet SFP+

10

PD-5-10XGE-SFPP

T640, T1600, T4000, TX Matrix Plus, TX Matrix Plus with 3D SIBs

24

P1-PTX-24-10GE-SFPP

EX9200-6QS

PTX5000

EX9200

32

EX9200-32XS

EX9200

10-Gigabit Ethernet, DWDM

1

PC-1XGE-DWDM-CBAND

M120, M320, T320, T640, T1600, TX Matrix, TX Matrix Plus, TX Matrix Plus with 3D SIBs

10-Gigabit Ethernet, DWDM OTN

1

PC-1XGE-DWDM-OTN

T4000, TX Matrix Plus with 3D SIBs

10-Gigabit Ethernet LAN/WAN PIC with SFP+

12

PF-12XGE-SFPP

T4000, TX Matrix Plus with 3D SIBs

24

PF-24XGE-SFPP

T4000, TX Matrix Plus with 3D SIBs

10-Gigabit Ethernet, SFP+

32

14.2R1 or later EX9200-32XS

EX9200

10-Gigabit Ethernet, XENPAK

1

PC-1XGE-XENPAK

M120, M320, T320, T640, T1600, T4000, TX Matrix, TX Matrix Plus, TX Matrix Plus with 3D SIBs

40-Gigabit Ethernet, CFP

2

P1-PTX-2-40GE-CFP

PTX5000

10-Gigabit Ethernet, 40-Gigabit Ethernet, QFSP+

16/4

24/6

14.2R1 or later EX9200-4QS

17.1R1 or later EX9200-6QS

EX9200

48/12

P2-10G-40G-QSFPP

PTX5000

100-Gigabit Ethernet, CFP

1

PF-1CGE-CFP

T4000, TX Matrix Plus with 3D SIBs

2

P1-PTX-2-100GE-CFP

PTX5000

4

P2-100GE-CFP2

PTX5000

100-Gigabit Ethernet CFP/10-Gigabit Ethernet SFP+

2/8

EX9200-2C-8XS

EX9200

100-Gbps DWDM OTN

2

P1-PTX-2-100G-WDM

PTX5000

100-Gbps OTN, CFP2

4

P2-100GE-OTN

PTX5000

Channelized PICs

Table 4 lists the channelized PICs that are supported during a unified ISSU.

Table 4: Unified ISSU PIC Support: Channelized

PIC Type

Number of Ports

Model Number

Platform

Channelized E1 IQ

10

PB-10CHE1-RJ48-QPP

M120, M320, T320, T640, T1600, TX Matrix

PB-10CHE1-RJ48-QPP-N

M120

PE-10CHE1-RJ48-QPP

PE-10CHE1-RJ48-QPP-N

M10i

Channelized T1 IQ

10

PB-10CHT1-RJ48-QPP

M320, T320, T640, T1600

PE-10CHT1-RJ48-QPP

M10i

Channelized OC IQ

1

PB-1CHOC12SMIR-QPP

PB-1CHSTM1-SMIR-QPP

PB-1CHOC3-SMIR-QPP

M120, M320, T320, T640, T1600, TX Matrix, TX Matrix Plus

PE-1CHOC12SMIR-QPP

PE-1CHOC3-SMIR-QPP

M10i

Channelized DS3 to DS0 IQ

4

PB-4CHDS3-QPP

M120, M320, T320, T640, T1600, TX Matrix, TX Matrix Plus

PE-4CHDS3-QPP

M10i

Channelized STM 1

1

PE-1CHSTM1-SMIR-QPP

M10i

Tunnel Services PICs

Table 5 lists the Tunnel Services PICs that are supported during a unified ISSU.

Table 5: Unified ISSU PIC Support: Tunnel Services

PIC Type

Model Number

Platform

1-Gbps Tunnel

PE-TUNNEL

M10i

PB-TUNNEL-1

M120, M320, T320, T640, T1600, TX Matrix, TX Matrix Plus

4-Gbps Tunnel

PB-TUNNEL

10-Gbps Tunnel

PC-TUNNEL

ATM PICs

Table 6 lists the ATM PICs that are supported during a unified ISSU. The table includes support on Enhanced III FPCs.

Table 6: Unified ISSU PIC Support: ATM

PIC Type

Number of Ports

Model Number

Platform

DS3

4

PB-4DS3-ATM2

M120, M320, T320, T640, T1600, TX Matrix

PE-4DS3-ATM2

M10i

E3

4

PB-4E3-ATM2

M120, M320, T320, T640, T1600, TX Matrix, TX Matrix Plus

2

PE-2E3-ATM2

M10i

OC3/STM1

2

PB-2OC3-ATM2-MM

PB-2OC3-ATM2-SMIR

M120, M320, T320, T640, T1600, TX Matrix, TX Matrix Plus

PE-2OC3-ATM2-MM

PE-2OC3-ATM2-SMIR

M10i

OC12/STM4

1

PB-1OC12-ATM2-MM

PB-1OC12-ATM2-SMIR

M120, M320, T320, T640, T1600, TX Matrix, TX Matrix Plus

2

PB-2OC12-ATM2-MM

PB-2OC12-ATM2-SMIR

M120, M320, T320, T640, T1600, T4000, TX Matrix, TX Matrix Plus, TX Matrix Plus with 3D SIBs

1

PE-1OC12-ATM2-MM

PE-1OC12-ATM2-SMIR

M10i

OC48/STM16

1

PB-1OC48-ATM2-SFP

M120, M320, T320, T640, T1600, TX Matrix, TX Matrix Plus

Serial PICs

Unified ISSU supports the following 2-port EIA-530 serial PICs:

  • PB-2EIA530 on M320 routers with Enhanced III FPCs, and on M120 routers

  • PE-2EIA530 on M10i routers

DS3, E1, E3, and T1 PICs

Unified ISSU supports the following PICs on M120, M320, and T320 routers; T640 and T1600 routers; and the TX Matrix router:

  • 4-Port DS3 PIC (PB-4DS3)

  • 4-Port E1 Coaxial PIC (PB-4E1-COAX)

  • 4-Port E1 RJ48 PIC (PB-4E1-RJ48)

  • 4-Port E3 IQ PIC (PB-4E3-QPP)

  • 4-Port T1 PIC (PB-4T1-RJ48)

Note:

Unified ISSU is also supported on the 4-Port DS3 PIC (PB-4DS3) and the 4-Port E3 IQ PIC (PB-4E3-QPP) on the TX Matrix Plus router.

Unified ISSU supports the following PICs on M10i routers:

  • 2-Port DS3 PIC (PE-2DS3)

  • 4-Port DS3 PIC (PE-4DS3)

  • 4-Port E1 PICs (PE-4E1-COAX and PE-4E1-RJ48)

  • 2-Port E3 PIC (PE-2E3)

  • 4-Port T1 PIC (PE-4T1-RJ48)

  • 4-Port E3 IQ PIC (PE-4E3-QPP)

Enhanced IQ PICs

Unified ISSU supports the following PICs on M120 router, M320 router, and on T320 routers; T640 routers, T1600 routers, TX Matrix router, and the TX Matrix Plus router:

  • 1-Port Channelized OC12/STM4 Enhanced IQ PIC (PB-1CHOC12-STM4-IQE-SFP)

  • 1-Port nonchannelized OC12/STM4 Enhanced IQ PIC (PB-1OC12-STM4-IQE-SFP)

  • 4-Port Channelized DS3/E3 Enhanced IQ PIC (PB-4CHDS3-E3-IQE-BNC)

  • 4-Port nonchannelized DS3/E3 Enhanced IQ PIC (PB-4DS3-E3-IQE-BNC)

  • 4-Port nonchannelized SONET/SDH OC48/STM16 Enhanced IQ (IQE) PIC with SFP (PC-4OC48-STM16-IQE-SFP)

Unified ISSU supports 1-port Channelized OC48/STM16 Enhanced IQ (IQE) PIC with SFP (PB-1CHOC48-STM16-IQE-SFP) on MX Series routers.

Enhanced IQ2 Ethernet Services Engine (ESE) PIC

Unified ISSU supports the enhanced IQ2 ESE PICs listed in Table 7.

Table 7: Unified ISSU Support: Enhanced IQ2 Ethernet Services Engine (ESE) PIC

Model Number

Number of Ports

Platform

PC-8GE-TYPE3-SFP-IQ2E

8

M120, M320, T320, T640, T4000 TX Matrix, TX Matrix Plus, TX Matrix Plus with 3D SIBs

PB-8GE-TYPE2-SFP-IQ2E

8

M120, M320, T320, T640, TX Matrix, TX Matrix Plus, TX Matrix Plus with 3D SIBs

PB-4GE-TYPE1-SFP-IQ2E

4

M120, M320, T320, T640

PC-1XGE-TYPE3-XFP-IQ2E

1

M120, M320, T320, T640, T4000, TX Matrix, TX Matrix Plus, TX Matrix Plus with 3D SIBs

PB-1CHOC48-STM16-IQE

1

M120, M320, T320, T640, T4000, TX Matrix, TX Matrix Plus, TX Matrix Plus with 3D SIBs

PE-4GE-TYPE1-SFP-IQ2E

4

M10i

PE-4GE-TYPE1-SFP-IQ2

4

M10i

Unified ISSU FPC Support on T4000 Routers

In the FPCs on T4000 routers, 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 T4000 routers with FPC/PIC 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.

To verify that statistics are preserved across the unified ISSU, you can issue CLI operational commands such as show interfaces statistics after the unified ISSU completes.

Unified ISSU is supported on the following FPCs:

  • T4000 FPC5 (model numbers—T4000-FPC5-3D and T4000-FPC5-LSR)

  • Enhanced Scaling FPC4-1P (model number—T640-FPC4-1P-ES)

  • Enhanced Scaling FPC4 (T1600-FPC4-ES)

  • Enhanced Scaling FPC3 (T640-FPC3-ES)

  • Enhanced Scaling FPC2 (T640-FPC2-ES)

Note:

The aforementioned FPCs are also supported on TX Matrix Plus routers with 3D SIBs.

Unified ISSU Support on MX Series 3D Universal Edge Routers

The following sections list the Dense Port Concentrators (DPCs), Flexible PIC Concentrators (FPCs), Modular Port Concentrators (MPCs), and Modular Interface Cards (MICs) that are supported during a unified ISSU on MX Series routers.

Unified ISSU DPC and FPC Support on MX Series Routers

Unified ISSU supports all DPCs except the Multiservices DPC on MX Series routers. Unified ISSU also supports Type 2 FPC (MX-FPC2) and Type 3 FPC (MX-FPC3) on MX Series routers. For more information about DPCs and FPCs on MX Series routers, go to https://www.juniper.net/documentation/ en_US/release-independent/junos/ information-products/pathway-pages/mx-series/.

Unified ISSU MIC and MPC Support on MX Series Routers

Unified ISSU supports all the Modular Port Concentrators (MPCs) and Modular Interface Cards (MICs) listed in Table 8 and Table 9. Unified ISSU is not supported on MX80 routers.

In the MPCs on MX Series routers, 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.

To verify that statistics are preserved across the unified ISSU, you can issue CLI operational commands such as show interfaces statistics after the unified ISSU completes.

Table 8: Unified ISSU Support: MX Series Router MPCs

MPC Type

Number of Ports

Model Number

Platform

MPC1

—

MX-MPC1-3D

MX Series routers

MPC1E

—

MX-MPC1E-3D

MX Series routers

MPC1 Q

—

MX-MPC1-3D-Q

MX Series routers

MPC1E Q

—

MX-MPC1E-3D-Q

MX Series routers

MPC2

—

MX-MPC2-3D

MX Series routers

MPC2E

—

MX-MPC2E-3D

MX Series routers

MPC2 Q

—

MX-MPC2-3D-Q

MX Series routers

MPC2E Q

—

MX-MPC2E-3D-Q

MX Series routers

MPC2 EQ

—

MX-MPC2-3D-EQ

MX Series routers

MPC2E EQ

—

MX-MPC2E-3D-EQ

MX Series routers

16x10GE MPC

16

MPC-3D-16XGE-SFPP

MX Series routers

MPC3E

—

MX-MPC3E-3D

MX Series routers

32x10GE MPC4E

32

MPC4E-3D-32XGE-SFPP

MX Series routers

2x100GE + 8x10GE MPC4E

10

MPC4E-3D-2CGE-8XGE

MX Series routers

6x40GE + 24x10GE MPC5E

30

MPC5E-40G10G

MX Series routers

6x40GE + 24x10GE MPC5EQ

30

MPC5EQ-40G10G

MX Series routers

2x100GE + 4x10GE MPC5E

6

MPC5E-100G10G

MX Series routers

2x100GE + 4x10GE MPC5EQ

6

MPC5EQ-100G10G

MX Series routers

MPC6E

2

MX2K-MPC6E

MX Series routers

MPC7E (multi-rate)

12

MPC7E-MRATE

MX Series routers

MPC7E 10G

40

MPC7E-10G

MX Series routers

MPC8E

—

MX2K-MPC8E

MX Series routers

MPC9E

—

MX2K-MPC9E

MX Series routers
Table 9: Unified ISSU Support: MX Series Router MICs

MIC Type

Number of Ports

Model Number

Platform

ATM MIC with SFP

8

MIC-3D-8OC3-2OC12-ATM

MX Series routers

Channelized SONET/SDH OC192/STM64 MIC with XFP

4

MIC-3D-1OC192-XFP

MX Series routers

Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP

4

MIC-3D-4COC3-1COC12-CE

MX Series routers

Channelized E1/T1 Circuit Emulation MIC

16

MIC-3D-16CHE1-T1-CE

MX Series routers

Channelized SONET/SDH OC3/STM1 (Multi-Rate) MICs with SFP

4

MIC-3D-4CHOC3-2CHOC12

MX Series routers

Channelized SONET/SDH OC3/STM1 (Multi-Rate) MICs with SFP

8

MIC-3D-4CHOC3-2CHOC12

MX Series routers

Channelized DS3/E3 MIC

8

MIC-3D-8CHDS3-E3-B

MX Series routers

DS3/E3

8

MIC-3D-8DS3-E3

MX Series routers

See MIC MRATE for MIC Type

12

MIC MRATE

MX Series routers

40-Gigabit Ethernet MIC with QSFPP

2

MIC3-3D-2X40GE-QSFPP

MX Series routers

10-Gigabit Ethernet MIC with SFPP

10

MIC3-3D-10XGE-SFPP

MX Series routers

100-Gigabit Ethernet MIC with CXP

1

MIC3-3D-1X100GE-CXP

MX Series routers

100-Gigabit Ethernet MIC with CFP

1

MIC3-3D-1X100GE-CFP

MX Series routers

Gigabit Ethernet MIC with SFP

20

MIC-3D-20GE-SFP

MX Series routers

10-Gigabit Ethernet MIC with SFP+ (24 Ports)

24

MIC6-10G

MX Series routers

10-Gigabit Ethernet DWDM OTN MIC (non-OTN mode only)

24

MIC6-10G-OTN

MX Series routers

100-Gigabit Ethernet MIC with CFP2 (non-OTN mode only)

2

MIC6-100G-CFP2

MX Series routers

100-Gigabit Ethernet MIC with CXP (4 Ports)

4

MIC6-100G-CXP

MX Series routers

10-Gigabit Ethernet MICs with XFP

2

MIC-3D-2XGE-XFP

MX Series routers

10-Gigabit Ethernet MICs with XFP

4

MIC-3D-4XGE-XFP

MX Series routers

SONET/SDH OC3/STM1 (Multi-Rate) MICs with SFP

4

MIC-3D-4OC3OC12-1OC48

MX Series routers

SONET/SDH OC3/STM1 (Multi-Rate) MICs with SFP

8

MIC-3D-8OC3OC12-4OC48

MX Series routers

Tri-Rate Copper Ethernet MIC

40

MIC-3D-40GE-TX

MX Series routers

100-Gigabit DWDM OTn MIC with CFP2-ACO

1

MIC3-100G-DWDM

MX960 routers
Note:

Note that unified ISSU is supported only by the MICs listed in Table 9.

Note:

Consider the following guidelines before performing a unified ISSU on an MX Series router with ATM interfaces at scale:

  • The PPP keepalive interval must be 10 seconds or greater. PPP requires three keepalives to fail before it brings down the session. Thirty seconds (ten seconds multiplied by three) provides a safe margin to maintain PPP sessions across the unified ISSU in case of any traffic loss during the operation. Configure the interval with the keepalives statement at the [edit interfaces at-interface-name] or [edit interfaces at-interface-name unit logical-unit-number] hierarchy level.

  • The OAM F5 loopback cell period must be 20 seconds or greater to maintain ATM connectivity across the unified ISSU. Configure the interval with the oam-period statement at the [edit interfaces at-interface-name unit logical-unit-number] hierarchy level.

Unified ISSU Limitations on MX Series Routers

Unified ISSU is currently not supported when clock synchronization is configured for Synchronous Ethernet, Precision Time Protocol (PTP), and hybrid mode on MX80 routers and on the MICs and MPCEs on MX240, MX480, and MX960 routers.

Note:

For Junos OS Releases 22.1R1 and above, you can use the request system software in-service-upgrade command with the handle-incompatible-config option to automatically deactivate/activate clock synchronization for PTP and Synchronous Ethernet on the MX960, MX10003, MX10008, MX10016, MX2010, and MX2020 routers.

Note:

Before enabling ISSU on MX routers, when upgrading from a Junos OS Release 14.1 or earlier to Junos OS Release 14.2 or later, you must disable IGMP snooping, and PIM snooping, in all protocol hierarchies. This includes the bridge-domain and routing-instances hierarchies.

Note:

On MX Series routers with MPC/MIC interfaces, the policers for transit traffic and statistics are disabled temporarily during the unified ISSU process.

Related Documentation

Change History Table

Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.

Release
Description
17.4
Unified ISSU is supported with Junos OS Release 17.4R1 for MX Series routers
17.4
EX9204, EX9208, EX9214, and EX9251, and EX9253 switches do not support LACP fast timer configuration starting with Junos OS Release 17.4.
16.1R1
Starting with Junos OS Release 16.1R1, while performing a unified ISSU from a FreeBSD 6.1-based Junos OS to an upgraded FreeBSD 10.x-based Junos OS, the configuration must be validated on a remote host or on a Routing Engine.
13.3
On MX Series 3D Universal Edge Routers with MPC3E and MPC4E interfaces, unified ISSU is supported starting with Junos OS Release 13.3.
13.2
Starting with Junos OS Release 13.2, unified ISSU is supported on the PTX5000 and PTX3000 with the FPC-PTX-P1-A FPC.
11.2
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.