Upgrading a multichassis IRF fabric

Performing a compatible upgrade

For a compatible upgrade on a multichassis IRF fabric, upgrade a subordinate member first. Then, upgrade the master and the other subordinate members.

To perform a compatible upgrade:

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. (Optional.) Set the automatic rollback timer.

issu rollback-timer minutes

By default, the automatic rollback timer is set to 45 minutes.

This timer starts when you execute the issu run switchover command. If you do not execute the issu accept or issu commit command before this timer expires, the system automatically rolls back to the original software images.

3. Return to user view.

quit

N/A

4. Load the upgrade images as main startup software images on subordinate members.

  • Use .bin files: issu load file { boot filename | system filename | feature filename&<1-30> } * slot slot-number&<1-9>

  • Use an .ipe file: issu load file ipe ipe-filename slot slot-number&<1-9>

Specify the member ID of a subordinate member for the slot-number argument.

5. Perform a master/subordinate switchover.

issu run switchover

N/A

6. (Optional.) Accept the upgrade and delete the automatic rollback timer.

issu accept

N/A

7. Upgrade the remaining members to complete the ISSU.

issu commit chassis chassis-number


[IMPORTANT: ]

IMPORTANT:

After executing the command for one member, you must wait for the member to restart and join the IRF fabric before you execute the command for another member.


Repeat the issu commit command to upgrade the remaining members one by one, including the original master.

To manually roll back to the original software images during this ISSU process, use the issu rollback command.

For more information about rollback, see Fundamentals Command Reference.

Performing an incompatible upgrade

For an incompatible upgrade on a multichassis IRF fabric, upgrade one or more subordinate members first. As a best practice, upgrade half of the subordinate members first. Then, upgrade the master and the other subordinate members.

Perform this task in user view.

Step

Command

Remarks

1. Load the upgrade images as main startup software images on subordinate members.

  • Use .bin files: issu load file { boot filename | system filename | feature filename&<1-30> } * slot slot-number&<1-9>

  • Use an .ipe file: issu load file ipe ipe-filename slot slot-number&<1-9>

Specify the member ID of a subordinate member for the slot-number argument.

As a best practice on a ring-topology IRF fabric, specify half of the subordinate members for this command to reduce service interruption. Make sure the specified subordinate members are physically connected.

2. Perform a master/subordinate switchover to complete the ISSU process.

issu run switchover

To roll back to the original software images during this ISSU process, use the issu rollback command.

This ISSU process does not support automatic rollback.

For more information about rollback, see Fundamentals Command Reference.

3. Verify that the ISSU is finished.

display issu state

If the ISSU state field displays Init, the ISSU is finished.