Compatibility Verification Using Cisco Feature Navigator - Cisco Catalyst 4500 Series Software Configuration Manual

In-Service Software Upgrade (ISSU) on a VSS
•
To display the compatibility matrix data between two software versions on a given system, enter the
show issu comp-matrix stored command.
This command is useful only for verification purposes because it is available only after the ISSU process
Note
has started. You might want to check the compatibility matrix prior to starting ISSU. Use the Feature
Navigator to obtain the needed information:
http://tools.cisco.com/ITDIT/CFN/jsp/index.jsp

Compatibility Verification Using Cisco Feature Navigator

The ISSU application on Cisco Feature Navigator allows you to:
•
•
•
•
•
How to Perform the ISSU Process
Unlike SSO, which is a mode of operation for the device and a prerequisite for performing ISSU, the
ISSU process is a series of steps performed while the switch is in operation. The steps result in an
upgrade to new or modified Cisco IOS XE software, and have a minimal impact to traffic.
For an illustration of the process flow for ISSU, refer to
Note
This section includes the following topics:
•
•
•
•
•
•
•
•
Catalyst 4500 Series Switch, Cisco IOS Software Configuration Guide - Cisco IOS XE 3.9.xE and IOS 15.2(5)Ex
5-64
possible. The matrix entry designates the images to be incompatible (I). The system operates in RPR
mode during the upgrade process when the versions of Cisco IOS XE at the active and standby
supervisor engines are incompatible.
Cisco IOS XE determines the compatibility between the active and the standby IOS XE software
dynamically during Standby boot up. The matrix is represented by "x".
Select a specific software bundle.
Identify which software images are compatible with the selected software image.
Compare two IOS XE software images and understand the compatibility level of the software
images (that is, compatible, base-level compatible, and incompatible), or dynamically determined.
Compare two software images and see the client compatibility for each ISSU client.
Provide links to release notes for the software image.
Verifying the ISSU Software Installation, page 5-65
Verifying Redundancy Mode Before Beginning the ISSU Process, page 5-65
Verifying the ISSU State Before Beginning the ISSU Process, page 5-67
ISSU using the Four-command Sequence: Step 1 (loadversion), page 5-68
ISSU using the Four-command Sequence: Step 2 (runversion), page 5-70
ISSU using the Four Command Sequence: Step 3 (acceptversion), page 5-72
ISSU using the Four Command Sequence: Step 4 (commitversion), page 5-72
Using changeversion to Automate an ISSU Upgrade, page 5-73
Chapter 5 Configuring Virtual Switching Systems
Figure 5-11.