Hide Navigation Pane
Show Navigation Pane
Download
SHA1
Monitoring the Status of the Router During Unified ISSU
Purpose
Display information about the current status of the router relative to a unified in-service software upgrade and of the upgrade itself.
Action
To display the current unified ISSU state and identify the active and armed releases in brief:
host1#show issu brief
ISSU state: initializing ISSU description: ISSU initialize is in-progress, 5% complete criteria met: No, upgrade error(s) found running release: release1.rel armed release: release2.rel
To the information displayed by show issu brief, the show issu command adds a summary table of unified ISSU verification criteria:
host1# show issu ISSU state: idle ISSU description: ISSU is currently idle criteria met: No, upgrade error(s) found running release: release1.rel armed release: release2.rel # ISSU Activation Criteria Summary Met -- ----------------------------------------------------- ----------- 1 In-Service Software Upgrade ready? Yes 2 High-Availability ready? No 3 Line modules ready? Conditional 4 Configuration conversion support ready? Yes 5 CLI sessions ready? Yes 6 Routing applications ready? Yes 7 Protocol timers ready? Yes
To the information displayed by show issu, the show issu detail command adds a detailed table of unified ISSU verification criteria that lists mandatory and conditional criteria that have not been met, the impact of this status, and the remedy as reported by router applications and system components that participate in the in-service software upgrade:
host1# show issu detail
ISSU state: idle
ISSU description: ISSU is currently idle
criteria met: No, upgrade error(s) found
running release: release1.rel
armed release: release2.rel
# ISSU Activation Criteria Summary Met
-- ------------------------------------------------------ -----------
1 In-Service Software Upgrade ready? Yes
2 High-Availability ready? No
3 Line modules ready? Conditional
4 Configuration conversion support ready? Yes
5 CLI sessions ready? Yes
6 Routing applications ready? Yes
7 Protocol timers ready? Yes
# ISSU Criterion Detail Met
-- ------------------------------------------------------ -----------
1 In-Service Software Upgrade ready? Yes
2 High-Availability ready? No
-> Problem: The standby SRP must not be running the same release No
Reporting Slot: 6
Impact: ISSU cannot be performed
Remedy: boot a release compatible with ISSU on the standby SRP
3 Line modules ready? Conditional
-> Problem: Card does not support required memory configuration Conditional
: Slot 1, OC3/OC12/DS3-ATM, requires at least 256 MB
Reporting Slot: 6
Impact: If you continue, the card will immediately be reset
and then cold started when ISSU Upgrade completes
Remedy: data unavailable
-> Problem: Card does not support required memory configuration Conditional
: Slot 8, CT3-12, requires at least 256 MB
Reporting Slot: 6
Impact: If you continue, the card will immediately be reset
and then cold started when ISSU Upgrade completes
Remedy: data unavailable
-> Problem: Card does not support required memory configuration Conditional
: Slot 9, CT3-12, requires at least 256 MB
Reporting Slot: 6
Impact: If you continue, the card will immediately be reset
and then cold started when ISSU Upgrade completes
Remedy: data unavailable
-> Problem: Card does not support required memory configuration Conditional
: Slot 10, CT3-12, requires at least 256 MB
Reporting Slot: 6
Impact: If you continue, the card will immediately be reset
and then cold started when ISSU Upgrade completes
Remedy: data unavailable
-> Problem: Card not disabled or not online: Slot 1, OC3/OC12/D Conditional
S3-ATM, 0/0
Reporting Slot: 6
Impact: If you continue, the card will immediately be reset
and then cold started when ISSU Upgrade completes
Remedy: If not standby, Wait for card to come online before
proceeding
-> Problem: Card not disabled or not online: Slot 8, CT3-12, 0/ Conditional
0
Reporting Slot: 6
Impact: If you continue, the card will immediately be reset
and then cold started when ISSU Upgrade completes
Remedy: If not standby, Wait for card to come online before
proceeding
4 Configuration conversion support ready? Yes
5 CLI sessions ready? Yes
6 Routing applications ready? Yes
7 Protocol timers ready? Yes
The following example displays the sample output when an attempt to start the initialization phase of the unified ISSU process fails, because of the upgrade being attempted from JunosE releases that do not contain the design changes for CSR FPGA functionality (earlier than Release 11.3.0) to JunosE releases that contain the enhanced CSR FPGA design (Release 11.3.0 and later releases).
host1# show issu
ISSU state: idle
ISSU description: ISSU is currently idle
criteria met: No, upgrade error(s) found
running release: release1.rel
armed release: release2.rel
# ISSU Activation Criteria Summary Met
-- ----------------------------------------------------- -----------
1 In-Service Software Upgrade ready? No
ISSU is tried over an Incompatible release No
Impact: ISSU cannot proceed
Remedy: ISSU is not supported in selected releases
(PSN-2010-11-986)
Reporting slot: 6
2 High-Availability ready? No
3 Line modules ready? Conditional
4 Configuration conversion support ready? Yes
5 CLI sessions ready? Yes
6 Routing applications ready? Yes
7 Protocol timers ready? Yes
Meaning
Table 23 lists the show issu command output fields.
Table 23: show issu Output Fields
Field Name | Field Description |
|---|---|
ISSU state | State of the upgrade process, idle, initializing, initialized, or upgrading |
ISSU description | State of the upgrade, including percent complete |
criteria met | Whether prerequisites for the upgrade have been met and, generally, what errors occurred |
running release | Filename of JunosE Software release that is currently running on the SRP modules |
armed release | Filename of JunosE Software release that is armed to become the next running release when the router reboots |
ISSU Activation Criteria Summary | Summarizes the criteria for unified ISSU activation. |
In-Service Software Upgrade ready? | Criteria required for unified ISSU activation. Possible values: Yes, No, Conditional. Note: All criteria must be “yes” for unified ISSU to be active. |
ISSU is tried over an Incompatible release | Criteria required for unified ISSU activation. Possible values: Yes, No, Conditional. Note: All criteria must be “yes” for unified ISSU to be active. |
High-Availability ready? | Criteria required for unified ISSU activation. Possible values: Yes, No, Conditional. Note: All criteria must be “yes” for unified ISSU to be active. |
Line Modules ready? | Criteria required for unified ISSU activation. Possible values: Yes, No, Conditional. Note: All criteria must be “yes” for unified ISSU to be active. |
Configuration conversion support ready? | Criteria required for unified ISSU activation. Possible values: Yes, No, Conditional. Note: All criteria must be “yes” for unified ISSU to be active. |
CLI sessions ready? | Criteria required for unified ISSU activation. Possible values: Yes, No, Conditional. Note: All criteria must be “yes” for unified ISSU to be active. |
Routing applications ready? | Criteria required for unified ISSU activation. Possible values: Yes, No, Conditional. Note: All criteria must be “yes” for unified ISSU to be active. |
Protocol Timers ready? | Criteria required for unified ISSU activation. Possible values: Yes, No, Conditional. Note: All criteria must be “yes” for unified ISSU to be active. |
ISSU Criterion Detail | Detailed information on why the criteria required for unified ISSU activation was not met or was conditional. |
Problem | The reason why the criteria for unified ISSU activation is not met. |
Reporting Slot | Slot where the issue occurred. |
Impact | What happens if you continue with the upgrade. |
Remedy | What you can do to fix the Problem. |
