System Setup and Software Installation Guide for Cisco Optical Site Manager, IOS XR

PDF

Install a Cisco Optical Site Manager SMU

Updated: March 2, 2026

Want to summarize with AI?

Log in

Overview

Learn how to install a Software Maintenance Upgrade (SMU) to update your Cisco Optical Site Manager with bug fixes and enhancements.

A Software Maintenance Upgrade (SMU) is a package that can be installed on a system to deliver patch fixes or security updates to a released image. A Cisco Optical Site Manager SMU is an updated Cisco Optical Site Manager image bundled as an XR SMU, providing the latest enhancements or fixes for Cisco Optical Site Manager \within the XR environment.

Install a SMU to update your Cisco Optical Site Manager with bug fixes and enhancements. Transfer the installation file, install the SMU, and verify that the new image is active.

In high availability (HA) deployments, install the SMU on the standby node first. Then, install it on the active node.

Warning

Installing a SMU triggers the host device’s controller to reload.

Before you begin

Download the SMU from the Cisco Software Download page.

Follow these steps to install a Cisco Optical Site Manager SMU:

Procedure

1.

Use the scp command to copy the file to the standby node and confirm the md5sum value.

Example:

[root@NCS1k-ZTP smu]# scp /harddisk/cosm/smu/ncs1010-x86_64-25.1.1-CSCwr67302.tgz
cixxx@10.xx.xx.xx:/harddisk:/

[node0_RP0_CPU0:/harddisk:]$md5sum ncs1010-x86_64-25.1.1-CSCwr67302.tgz
c28dcced4e562e329e36baf1d7621ca0  ncs1010-x86_64-25.1.1-CSCwr67302.tgz
2.

Use the install source command to install the SMU.

Example:

RP/0/RP0/CPU0:COSM_OLT-3_214# install source /harddisk:/ncs1010-x86_64-25.1.1-CSCwr67302.tgz
Wait for the installation to complete.
3.

Use the show install request command to verify the status of installation was successful.

Example:

RP/0/RP0/CPU0:COSM_OLT-3_214#show install request 
Mon Oct 27 11:12:05 UTC

User request: install source /harddisk:/ncs1010-x86_64-25.1.1-CSCwr67302.tgz
Operation ID: 33.1
State:        Success since 2025-10-27 11:09:59 UTC
Current activity:    Await user input
Time started:        2025-10-27 11:09:59 UTC
The following actions are available:
    install package add
    install package remove
    install package upgrade
    install package downgrade
    install package replace
    install package rollback
    install replace
    install rollback
    install source
    install commit
    install replace reimage
4.

Use the install commit command to commit the SMU.

Example:

RP/0/RP0/CPU0:COSM_OLT-3_214#install commit
5.

Use the show install fixes committed command to verify that the SMU image is committed.

Example:

The bold text displays the committed SMU CSCwr67302 xr-cosm-25.1.1v1.0.1-1. 
RP/0/RP0/CPU0:ios#show install fixes committed
Mon Dec  8 05:16:35.319 UTC

Committed Fixes (count: 2):
Bug Id      Packages                                                   
----------- -----------------------------------------------------------
CSCwr31650  xr-ncs1010-forwarder-25.1.1v1.0.1-1                       
CSCwr67302  xr-cosm-25.1.1v1.0.1-1
6.

Use the show install fixes active command to verify that the SMU image is active.

Example:

The text in bold in this example displays the active SMU version CSCwr67302 xr-cosm-25.1.1v1.0.1-1. 
RP/0/RP0/CPU0:ios#show install fixes active 
Tue Dec  9 06:51:23.276 UTC

Active Fixes (count: 2):
Bug Id      Packages                                                   
----------- -----------------------------------------------------------
CSCwr31650  xr-ncs1010-forwarder-25.1.1v1.0.1-1
CSCwr67302  xr-cosm-25.1.1v1.0.2-1
RP/0/RP0/CPU0:ios#show cosm status 
Tue Dec  9 06:51:31.549 UTC
COSM state: APP_ACTIVATED
AppMgr app state: ACTIVATED
AppMgr container state: RUNNING
Container status: Up 13 hours
Last error: No error
COSM version: 25.1.1.D0372
7.

Use the show cosm status command to verify that the Cisco Optical Site Manager SMU version is activated.

Example:

The text in bold in this example displays the active Cisco Optical Site Manager version 25.1.1.R0366. 
RP/0/RP0/CPU0:HAN-1#show cosm status 
Thu Oct 30 10:21:25.374 UTC
COSM state: APP_ACTIVATED
AppMgr app state: ACTIVATED
AppMgr container state: RUNNING
Container status: Up 2 days
Last error: No error
COSM version: 25.1.1.R0366
Redundancy role: ACTIVE (NONE)
The status of the standby node appears as NONE in the output of the show cosm status command.
8.

Perform the same installation process on the active node.

After the installation is completed and the controller is reloaded, these redundancy status changes occur:

  • On the active node, during the SMU installation, the redundancy status transitions through UNKNOWN → STARTING → NONE → STANDBY (connected active 1.1.1.1-COSM) after the active node reloads.

  • The redundancy status of the standby node changes to NONE during the SMU installation on the active node and updates to ACTIVE (standby not connected) after the active node completes its reload.

The Cisco Optical Site Manager SMU is installed.

This table explains the redundancy status changes in the output of the show cosm status command on both nodes during the SMU installation.

Table 1. Cisco Optical Site Manager redundancy status transitions during SMU installation
Node Node Operation Redundancy Status Details
Standby Node Install SMU, the reloads Status varies (install / reload in progress) The standby node temporarily disconnects during SMU installation.
Active Node No action / monitoring ACTIVE (standby not connected) The active node displays standby not connected while the SMU installs on the standby node.
Active Node Install SMU, then reloads Transitions: UNKNOWN → STARTING → NONE → STANDBY (connected active 1.1.1.1-COSM) The active node undergoes state transitions while coming back online.
Standby Node (becomes new Active) Monitors while old active reloads NONE → ACTIVE (standby not connected) → ACTIVE (connected active 2.2.2.2-COSM)

  • The standby node initially shows a redundancy status of NONE during the SMU installation on the active node.

  • Once the active node completes its reload, the standby node transitions to ACTIVE (connected active 2.2.2.2-COSM) and remains active thereafter.