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

PDF

Upgrade NCS 2000 nodes hosting SVO line cards

Want to summarize with AI?

Log in

Overview

Use this procedure to upgrade NCS 2000 nodes from R11.x to R25.1.1 to host SVO line cards, enable required OSPF and UDC settings, deploy Cisco Optical Site Manager, and onboard the nodes for management through the WebUI, including geo HA configurations.

Use this task to upgrade NCS 2000 nodes from R11.x to R25.1.1 so the nodes can host SVO line cards and be managed through Cisco Optical Site Manager WebUI.

  • Upgrade the NCS 2000 node software and validate post-upgrade access in CTC.

  • Enable required OSPF and UDC settings for SVO line card deployments, including geo HA.

Table 1. Feature History Table

Feature Name

Release Information

Feature Description

SSH upgrade

Release R25.1.1

When you upgrade to R25.1.1, the SSH and SSL libraries upgrade to the latest revisions that provide better security, addressing vulnerabilities.

New versions Cisco Optical Site Manager supports after upgrade (25.x)

CISCOSSL: 1.1.1y.7.3.377 (6/6/2024)

CISCOSSH: 1.14.55

Use this task to upgrade the NCS 2000 nodes that will install a fresh R25.1.1 SVO line cards from R11.x to R25.1.1.

Note

If SVO line cards are present in the NCS 2000 nodes in the geo HA configuration, repeat this task on both NCS 2000 nodes.

Before you begin

Before you begin, ensure that you have access to the target NCS 2000 nodes and the required software packages, and that you can access Cisco Optical Site Manager Admin Plane and WebUI.

  • Obtain the NCS2K-S-package for R25.1.1.

  • Ensure that you can access the node using CTC and that you have the required credentials for node and SVO line card onboarding.

  • For geo HA deployments, ensure that both adjacent NCS 2000 nodes are available for configuration.

Procedure

1.

Upgrade the NCS 2000 nodes to R25.1.1.

After upgrade, reopen CTC and clear cached data because this is a major release upgrade.

  1. Download and activate the NCS2K-S-package for R25.1.1.

    For more information on the software activation, refer to Cisco NCS 2000 Series Upgrade Guide.

    Note

    While the NCS 2000 nodes upgrade to R25.1.1, both Active and Standby controller cards perform an additional boot during the upgrade.

  2. Reopen CTC in the R25.1.1 node.

  3. Delete the cache option on the login window.

    Note

    The CTC R25.1.1 will now have some panels disabled as some node management will be performed via the Cisco Optical Site Manager WebUI.

2.

In CTC, configure required OSPF and UDC settings.

  1. Enable OSPF on LAN.

    This setting is required on the NCS 2000 node that is hosting the SVO line card irrespective of any HA configuration. The LAN Port Area ID value is the same as the ospf-area-id value in the network configuration YAML file that is used to install the SVO line card.

    1. In Tab View, go to Provisioning > Network > OSPF.

    2. In the OSPF on LAN pane, enable the OSPF active on LAN check box.

  2. Enable UDC on the controller card that connects to the other NCS 2000 node.

    The SVO line cards in geo HA configuration use the UDC ports. Enable UDC on both adjacent NCS 2000 nodes.

    1. In Tab View, go to Provisioning > UDC/VOIP.

    2. In the UDC/VOIP pane, select UDC for the available Service Type.

3.

Install the SVO line card. See Install the SVO line card.

  1. Plug in the first SVO line card into the NCS 2000 node with proper cabling.

  2. Install the second SVO line card in high availability configuration.

Note

For the geo HA configuration, install the SVO line cards in two different NCS 2000 nodes.

Two NCS 2000 nodes are upgraded with two SVO line card ready to configure the Cisco Optical Site Manager application.

The CTC view of the SVO line card will be a double slot line card with the name reported.

4.

Connect to Cisco Optical Site Manager Admin Plane WebUI. For more information, refer to Cisco Optical Site Manager Admin Plane.

Note

In the geo HA configuration, there are two SVO line cards. Each SVO instance has its own IP address. You can connect to one of the two instances for the initial Cisco Optical Site Manager application setup.

5.

Create a Cisco Optical Site Manager instance using the Admin Plane WebUI. For more information, refer to Cisco Optical Site Manager Instances.

Cisco Optical Site Manager application runs in a container environment via docker. This step requires settings used by the virtual environment.

6.

Log in to the Cisco Optical Site Manager WebUI. For more information, refer to Log into Cisco Optical Site Manager.

Note

Use the Username and Password that you configured in Step 5 for Cisco Optical Site Manager instance creation.

The Cisco Optical Site Manager WebUI opens in Node Functional View.

7.

Create a Cisco Optical Site Manager Authorization Group for SVO line cards and NCS 2000 nodes.

The Authorization Group defines the username and password that Cisco Optical Site Manager uses to connect to the SVO line card, NCS 2000 node, or remote device.

  1. Choose Devices > Authorization Group.

    1. For the SVO line card, Cisco Optical Site Manager creates the Authorization Group automatically. Edit the password field to enter the password of the added SVO line card.

      Note

      The SVO line card password is the password that you created during the SVO line card installation.

      Note

      SVO line card is considered as a separate device for the Cisco Optical Site Manager node although it is physically a line card plugged into the NCS 2000 node.

      In HA mode, both line cards are added to the Authorization Group.

    2. For the NCS 2000 node, refer to Manage Authorization Groups.

      Note

      After creating the Authorization Group, Cisco Optical Site Manager manages only one NCS 2000 node.

After you create the Authorization Group, all the SVO line cards, NCS 2000 nodes, and remote nodes appear in a list.

8.

(Optional) Set the NTP server for Cisco Optical Site Manager WebUI.

Cisco Optical Site Manager requires its own NTP server settings.

  1. Click the settings icon and then click NTP.

    You can either maintain the NTP settings on NCS 2000 device or remove them depending on your network choice.

    If you decide to

    then

    maintain the NCS 2000 NTP settings

    the Cisco Optical Site Manager node NTP setting affects only the Cisco Optical Site Manager application.

    remove the NCS 2000 NTP settings

    the Cisco Optical Site Manager application pushes the time information to the NCS 2000 node.

  2. Click Edit and update the NTP server settings.

9.

Onboard the NCS 2000 node to Cisco Optical Site Manager WebUI.

  1. Choose Devices > Devices and click the + icon to add a device.

    In Cisco Optical Site Manager, a subtended network element (NCS 2000) is referred to as a device.

    The Add Device dialog box opens.

  2. Enter the device information.

    Fields

    Actions

    Device Type

    Select ncs2000 from the drop-down list.

    Device Flavor

    any-config is the default option.

    Device Name

    Enter a name to identify the device in Cisco Optical Site Manager.

    First Active Chassis UID

    Leave this field blank for the first NCS2K device that you add to the Cisco Optical Site Manager node.

    IP Address

    Enter the IP address of the NCS2K node.

    Auth Group

    Select the Authorization Group that contains credentials for the NCS2K node.

    Note

    Device Name and Device Flavor cannot be changed afterwards unless you delete and re-add the device.

  3. Click Add.

    Device onboarding may take a few minutes.

10.

Verify that the NCS 2000 device Sync Status is sync completed, alarm-synchronized.

If Sync Status has a different message, refer to the troubleshooting upgrades.

The NCS 2000 node is upgraded to R25.1.1 and managed by its Cisco Optical Site Manager application accessible via WebUI. Cisco Optical Site Manager represents the new view of the node as the Cisco Optical Site Manager node. The Cisco Optical Site Manager node is reachable via its IP address in the DCN planned for Cisco Optical Site Manager management. The Cisco Optical Site Manager node is ready to be imported into CONC.

What to do next

Upgrade the remaining NCS 2000 nodes in the network.


Upgrade the remaining NCS 2000 nodes

Use this task to upgrade NCS 2000 nodes that do not host SVO line cards, to release R25.1.1 and enable management through Cisco Optical Site Manager WebUI.

  • Download and activate the NCS2K-S-package.

  • Create and access a Cisco Optical Site Manager instance.

  • Onboard and manage the upgraded nodes through the Cisco Optical Site Manager WebUI.

Table 2. Feature History Table

Feature Name

Release Information

Feature Description

SSH upgrade

Release R25.1.1

When you upgrade to R25.1.1, the SSH and SSL libraries upgrade to the latest revisions that provide better security, addressing vulnerabilities.

New versions Cisco Optical Site Manager supports after upgrade (25.x)

CISCOSSL: 1.1.1y.7.3.377 (6/6/2024)

CISCOSSH: 1.14.55

Use this task to upgrade the remaining NCS 2000 nodes in the network that do not host the SVO line card.

The NCS 2000 nodes in this task do not have SVO line cards. However, they are connected to NCS 2000 nodes that have an operational SVO line card. Each SVO line card supports up to 15 Cisco Optical Site Manager nodes.

Before you begin

Follow these steps to upgrade the remaining NCS 2000 nodes.

Procedure

1.

Upgrade the NCS 2000 node to release R25.1.1.

For more information about software activation, see the Cisco NCS 2000 Series Upgrade Guide.

During the upgrade to R25.1.1, both Active and Standby controller cards perform an additional boot.

2.

Download and activate the NCS2K-S-package for release R25.1.1.

3.

Reopen CTC on the R25.1.1 node.

4.

Delete the cache from the login window.

This step is required because R25.1.1 is a major release upgrade.

Some CTC panels are disabled in R25.1.1 because node management is performed through the Cisco Optical Site Manager WebUI.

5.

Log in to the Cisco Optical Site Manager Admin Plane WebUI.

For more information, see Cisco Optical Site Manager Admin Plane.

6.

Create a Cisco Optical Site Manager instance.

The Cisco Optical Site Manager application runs in a containerized Docker environment and requires virtual environment configuration settings.

For more information, see Cisco Optical Site Manager Instances.

7.

Log in to the Cisco Optical Site Manager WebUI.

Use the Username and Password configured during Cisco Optical Site Manager instance creation.

For more information, see Log into Cisco Optical Site Manager.

The Cisco Optical Site Manager WebUI opens in Node Functional View.

8.

Create an Authentication Group for the NCS 2000 nodes.

The Authentication Group defines the credentials that Cisco Optical Site Manager uses to connect to the NCS 2000 node.

For more information, see Manage Authorization Groups.

The NCS 2000 nodes appear in the Authorization Group list.

9.

Onboard the NCS 2000 node to the Cisco Optical Site Manager WebUI.

Repeat Steps 8 to 10 in Upgrade NCS 2000 Nodes Hosting SVO Line Cards to complete onboarding.

The NCS 2000 node is upgraded to release R25.1.1 and managed through the Cisco Optical Site Manager WebUI.

The node is represented as a Cisco Optical Site Manager node and is reachable through its IP address in the planned DCN for Cisco Optical Site Manager management.

The node is ready to be imported into Cisco Optical Network Controller.


Add an NCS 2000 remote TXP node to a Cisco Optical Site Manager

Use this task to add an NCS 2000 remote TXP (transponder) node to an existing Cisco Optical Site Manager so that the remote transponder can be managed from the Cisco Optical Site Manager WebUI.

  • Verify prerequisites and required identifiers (UIDs) before adding the device.

  • Add the remote transponder as an ncs2000 device with txp-only flavor in the Cisco Optical Site Manager WebUI.

  • Ensure the device is added with a valid, unused chassis UID and the correct authentication group.

Use this task after the associated ROADM node is already present and managed, and you need to bring the remote transponder under the same Cisco Optical Site Manager node view.

Adding the remote TXP requires selecting the correct device type and flavor, and assigning a chassis UID that does not conflict with existing UIDs in Cisco Optical Site Manager.

  • Verify available UIDs before you start the add-device workflow.

Follow these steps to add an NCS 2000 remote TXP node to a Cisco Optical Site Manager node.

Procedure

1.

Upgrade the NCS 2000 transponder nodes to release R25.1.1.

2.

Log in to the Cisco Optical Site Manager WebUI using the credentials of the required Cisco Optical Site Manager instance.

3.

Go to Devices > Devices > Device Hardware Details and verify the available UIDs.

4.

Add the remote transponder node to the Cisco Optical Site Manager node.

  1. In the Devices tab, click + to add a device.

    The Add Device window opens.

  2. Select Device Type as ncs2000 and Device Flavor as txp-only.

  3. Enter the Device Name, First Active Chassis UID, and IP Address.

    Verify the value of First Active Chassis UID is a not in use. The value must follow the sequence of free UIDs as the chassis UID for the remote transponder. If you enter an incorrect UID, wait for the device addition to complete. Then delete the device and repeat the steps.

  4. Select the required Auth Group and then click Add.

The NCS 2000 remote TXP node is added to the Cisco Optical Site Manager node and is available for management in the Cisco Optical Site Manager WebUI.