Cisco Optical Network Planner Configuration Guide, Releases 26.x.x

PDF

Cisco ONP network designs

Updated: March 10, 2026

Want to summarize with AI?

Log in

Overview

Describes the functionality of network designs. Explains the benefits of this feature and how it contributes to efficient and robust network planning.

A Cisco ONP network design is a network architecture planning approach that

  • allows you to create a new design manually or import an existing design,

  • supports integration with various sources and tools such as Excel sheets, live network import, Cisco Transport Planner, or other Cisco ONPA instances, and

  • provides flexibility in how network models are created and managed.

You can design a network in one of these ways:

  • Manual design: Create a network design using the design palette.

  • Import design: Import a network design from an Excel sheet, live network import, Cisco Transport Planner, or another instance of Cisco ONP.

This dual approach enables network architects to choose the method that best fits their workflow, making Cisco ONPA adaptable to various project requirements and existing data sources.

Manually design a network using Cisco ONP

Table 1. Feature History

Feature Name

Release Information

Feature Description

Database Operations Optimization

Cisco ONP Release 5.2

Cisco ONP now provides an option to run some operations in the background involving database interaction, such as Save As, Import CPZ, and Export CPZ. You can continue to use the Cisco ONP interface for other operations when these operations are running in the background.
Table 2. Feature History

Feature Name

Release Information

Feature Description

4K-2K SSON Network Creation Support

Cisco ONP Release 5.2

Now you can include the 4K-2K nodes in both SSON and non-SSON networks while designing the network. This helps you to validate 4K-2K nodes in the SSON design which has higher line rates.
Table 3. Feature History

Feature Name

Release Information

Feature Description

NCS 1010 C+L Network Design

Cisco ONP Release 5.1

Cisco ONP now supports the C+L-band networks that help you plan NCS 1010 networks using the OLT-L and ILA-L line cards to increase your network’s bandwidth capacity. Enhanced with L-band related properties, the UI enables you to design a C+L-band network for your ever-increasing channel demands. These L-band types are introduced to suit your design needs:

  • C+L: This band type adds more channels to your network, increasing its traffic carrying capacity.

  • C+L Futuristic: This band type creates a network with C-band edges and future provisions for L-band edges that you can cost-effectively upgrade after exhausting the C-band capacity.
Table 4. Feature History

Feature Name

Release Information

Feature Description

Greenfield NCS 1010 Network Design

Cisco ONP Release 5.0

You can design and validate NCS1010 optical line system. This feature helps to create OLT-C, OLT-R-C, ILA-C, ILA-R-C, and ILA-2R-C based NCS 1010 networks using fixed grid add/drop MD-32-ODD, MD-32-EVEN and flex grid add/drop BRK-24, BRK-16, and BRK-8 passive modules.
Table 5. Feature History

Feature Name

Release Information

Feature Description
Multi-Layer Platform (MLP) Greenfield Design with NCS 4k-1k-2k

Cisco ONP Release 4.1

This feature allows you to:

  • Support NCS 4K-1K-2K multiplatforms

  • Visualize new layout for Txp and SVO for NCS 2000 node

  • Support different OTN service types with protection

  • Edit layout for NCS 4000 and NCS 1004 nodes

Use this procedure to create a network in the Cisco ONP.

You can create any of these network designs:

  • Spectrum Switched Optical Network (SSON) that uses flexible spectrum allocation, where the required minimum spectral resources are allocated adaptively based on traffic demand and network conditions.

  • Non-SSON network that allocates single spectrum (fixed spectrum) irrespective of the traffic demand and network conditions.

  • NCS 1010 network

  • NCS 1001 network

  • NCS 1014 network

Before you begin

.

Procedure

1.

Choose File > New.
2.

In the Create New Network dialog box, choose the required options to create a network.

  1. From the L0 Network Platform drop-down list:

Choose To create...
NCS 2000 a non-SSON network that contains NCS 2000 and NCS 4000 nodes, or an SSON network including NCS 2000, NCS 1004, and NCS 4000 nodes
NCS1010 a network that contains only NCS 1010 nodes
NCS1001 a network that contains only NCS 1001 nodes
NCS 1014 a network that contains only NCS 1014 nodes

  1. If you want to create an SSON network, check the SSON Network check box. Otherwise, do not check the check box..

    This option is not for the NCS 1010 network.

  2. Choose NCS (4K_1K_2K) or NCS (4K_2K) from the Traffic Type drop-down list.

    You can view the Traffic Type drop-down list, if you choose to create an SSON network in the previous step.

    Note

    Once the network is created, you cannot change the Traffic type from 4K_1K_2K to 4K_2K, or the reverse. Export the network to an Excel sheet, make the required modifications, and import it as a new network.

  3. Choose the System Release for NCS 2K or NCS 1010 from the drop-down list.

    You cannot change the system releases that are available for NCS 4K and NCS 1K.

    The Band Type drop-down list appears for NCS 1010 networks from Release 7.9.1.

  4. From the Band Type drop-down list for NCS 1010, choose:

    • C-Band: Only C-band edges are created and ANS is generated based on C-band. For L-band upgrade, ANS unlock is required.

    • C+L Futuristic: Only C-band edges are created and ANS is generated based on C-band and L-band. For L-band upgrade, ANS unlock is not required.

    • C+L: Both C-band and L-band edges are created and ANS is generated based on C-band and L-band.

    Note

    After the creation of a NCS 1010 R7.9.1 network, if required, you can change the network band type under the Network Application Configuration section in the Network Properties.

  5. From the Profile drop-down list, select either the Default profile, which provides the default properties set by Cisco ONP, or a user-defined profile. For more details on profiles, see Predefined user profiles.

  6. Click Create.

    The application displays a map and the design palette. For details, refer to Design Palette options.
3.

Click the Drawing Tool icon (pencil and ruler crossed), and add sites and other network elements.

  1. Add sites to the map using the drawing tool.

    Zoom in on the map to the desired level. Click any of the site icons (ROADM, OLA, or Traffic(4K-1K-2K)), and drag it to the sites on the map. Drag or click the map where a site has to be placed, when the cursor changes to the site icon.

    Note

    • SRLG is not supported in the SSON networks.

      Traffic node is not supported on the NCS 1010 network.

  2. Click the Fiber icon and drag it to connect from one site to another site. Continue this for all sites.

    Note

    By default, the fiber length is set as 1 kilometer for all the fibers. To update the length automatically based on the x and y coordinates, enable the Use Coordinates Distance property in network properties.

  3. Create services between the sites (only for SSON and non-SSON networks).

    Cisco ONP provides only OTN service.

  4. Click OTN Service (green) and add the service between the existing Traffic sites on the map.

  5. Click Circuit (purple), Media channel (purple), or Waves (red), and add media channel, or waves between the existing sites on the map.

    In the left pane, you can view a network tree panel with a default network name. The network elements added are displayed in the tree panel.
4.

Choose File > Save As.

  1. In the Give a Network Name dialog box, enter a network name and click Save.

  2. If you want this operation to run in the background, click the Run in Background check box.

    A notification pops-up after the background operation is completed. Go to Job Monitor to view the progress of the operation running in the background.

Use this procedure to create Shared Risk Link Group (SRLG) using the Cisco ONP GUI. The SRLG feature enables routing of protected services.

Note

SRLG is supported only for non-SSON networks that include traffic nodes.

Before you begin

Log in to the Cisco ONP web interface.

Procedure

1.

Open the network where you want to create the SRLGs.
2.

Click the network tree panel.
3.

Expand Fibers, and check the check box next to each fiber that should be in the same SRLG.

4.

After selecting all fibers, right-click and choose Create SRLG.

Cisco ONP creates an SRLG with a unique name, which you can subsequently rename.

Import a network using an Excel sheet

Use this procedure to import a network into Cisco ONP, using an Excel sheet.

Before you begin

.
Table 6. Feature History

Feature Name

Release Information

Feature Description

CX Unified Planning Tool Network Import

Cisco ONP Release 5.0

The integration between CX Unified Planning Tool (UPT) and Cisco ONP enables you to import the networks created and analyzed in CX UPT into Cisco ONP. This helps you avoid recreating the networks that are already created in UPT. This feature allows you to import networks having NCS 1010 and NCS 2000 nodes into Cisco ONP.
Table 7. Feature History

Feature Name

Release Information

Feature Description

Export and Import of Network Topology in Excel Format

Cisco ONP Release 5.1

It is now possible to export the topology data of an existing network into an Excel file. You can easily modify the exported data in Excel and import it back into Cisco ONP to create a new network or modify an existing network.

These are the supported Excel formats:

  • xlsx—Standard Excel with multiple sheets, each corresponding to a network element such as Network, Sites, Circuits, Spans, OTNdemands, and so on.

  • xlsm—Macros-enabled Excel file that can filter out and display only the applicable network element sheets based on the platform selected in the Network sheet.

Cisco ONP has the built-in intelligence to automatically calculate the shortest path between a source and a destination, even if only a partial fiber path is mentioned in the imported Excel file.

Follow these steps to import a network into Cisco ONP, using an Excel sheet.

Note

By default, the system release of the Excel-imported network is 11.0

Note

From Release 5.0, Cisco ONP supports import of networks created using UPT via Cisco ONP Import Excel option. UPT does not populate the DWDMChannel Type and Add/Drop Type values in the Excel sheet. If the values are not found in the Excel sheet, then Cisco ONP picks the default options. By default, DWDMChannel Type is NCS1004_QPSK_SP_16QAM_200G_27%SDFEC_60GBd and Add/Drop Type is Colored. We recommend you to check the DWDMChannel Type and Add/Drop Type values before importing the Excel sheet into Cisco ONP to avoid any discrepancies.

From Release 5.1, in addition to exporting the template, you can export the entire network design data of an existing network as an Excel sheet. Modify the network properties available in the Excel sheet and reimport. The network can be exported in all modes and reimported on Design mode, Upgrade mode, and Release Upgrade mode.

Before you begin

Log in to the Cisco ONP web interface.

Procedure

1.

Choose Export > Excel .

  1. Choose the Network Type as Template or Current Network.

  2. Choose the File Type as xlsx or xlsm (Macros-enabled)

    The Macros-enabled Excel sheet automatically customizes the tabs on the Excel sheet based on the platform that you choose. It provides functionalities such as selection of fibers in the path selection, wavelength count validation in case of regen selection.

  3. Click Download.

The template has tabs and fields that you must fill in the Excel sheet. For details about these tabs and fields, refer to Tabs available in the Excel sheet template.
2.

Fill the network details in the template file or edit the current network file, and save the file.
3.

Choose Import > Excel , and select the Import Type .

  • New: Choose this option if you want to create a new network using the design data available in the Excel sheet.

  • Existing: Choose this option if you want to update an existing network with the data available in the Excel sheet. Open the network before you import the Excel sheet. Ensure the network is in Design mode, Upgrade mode, or Release Upgrade mode.

You can view the data available in the Excel sheet before you import the network data. The View Data check box remains checked by default. Uncheck it if you do not want to view the imported data.
4.

Browse for the file, select it, and click Import.

During the import for the existing network, If the network is locked, Cisco ONP does not import the data. If the network is unlocked and in upgrade mode, Cisco ONP updates the parameter. If the state is New, Cisco ONP adds parameters from the Excel file as a new entry.

During a new network import, the system creates a new network design regardless of the state.
5.

(Optional) After you successfully import the network design through Excel, choose a profile:

  1. Choose Network > Entity Editor.

  2. Click the network name and select the required user profile from the Profile drop-down-list.

    Note

    Values specified in Excel take precedence over the profile. For properties not available in Excel and set to Auto, they are updated according to the profile.
The selected network is imported.

If there are errors in the imported data, a pop-up error message is shown in case of new import, and the errors are available under the Elements > Messages tabs in case of updating the existing network.

Tabs available in the Excel sheet template

This table lists the various tabs available in the Excel sheet template used to import a network.

Table 8. Tabs available in the Excel sheet template
Tabs Description
Network

Label (name of the network), Platform (NCS2000(NON SSON), NCS2000 (SSON), NCS1010, NCS 1001 , NCS 1014), Traffic Type, NCS1010 Line Card, NCS1010 Band Type, Chassis Type, and System Release

Network Property

This is applicable for NCS 1010 network alone.

State (New, Locked, and Unlocked), NCS 1010 Line Card, NCS 1010 Band Type, and Chassis Type
Sites

Site Label, Type, X coordinates, Y coordinates,X_Rearranged, Y_Rearranged, Pre Equip Degree, Grooming Site, CLLI code, and Site Address, Degree (Scalable upto degree), NCS1010 Line Card, NCS1010 Band Type, Chassis Type, and State.

Spans

Span label, A (Source site name), Z (Destination site name), Kms (Distance), Loss, Type, A_Edge, Z_Edge, AZ_Loss, ZA_Loss, AZ_Kms , ZA_Kms, NCS1010 Band Type, Ageing loss, and State.

OTNDemands-4K-2K

Demand Label, A (Source), Z (Destination), Y (Tertiary Source), B (Tertiary Destination), Type, Quantity, Protection, Primary Path, Secondary Path, and State.

Note: Y and B can be used with Unprotected Disjoint Service.

OTNDemands-4K-1K-2K

 Demand Name, Source, Destination, Service Group, Type, A/D Type, Protection, Primary Wavelength, Secondary Wavelength, Primary Path, Secondary Path, First Restoration path, Second Restoration Path, Primary ODU Timeslot, Secondary ODU Timeslot, Primary Regen, Secondary Regen, Trunk Mode, Baud Rate, and State.

MediaChannels

 Channel Label, Source, Destination, Primary Wavelength, Secondary Wavelength, Protection, Traffic Type, Card Type, A/D Type, Primary Path, Secondary Path, Primary Regen, Secondary Regen, and State.

ServiceGroup

 ServiceGroup Name, Demand Types, 4K Exclusive LC Usage, 4K Symmetric Aggregation, 1K Exclusive LC Usage, 1K Symmetric AggregationChannel Label, and State.
DWDMChannels Primary Wavelength and Secondary Wavelength (Work and Protect Wavelength for NCS2000 non-SSON waves), Primary Path and Secondary Path (Work and Protect Path for NCS2000 Wave/Media Channel and NCS1010 circuit), A/D Type (Colored/Colorless/Contentionless), Traffic Type, Primary Regen Secondary Regen State, Channel label, A, Z, Wavelength, Protection, and Type.

Services-1K

Service Name, Source, Destination, Type, Protection, Primary Wavelength, Primary Path, Primary Regen, Card Type, Trunk Mode, A/D Type, Band Type, and State.

Circuits

Circuit Label, Source, Destination, Primary Wavelength, Protection, Traffic Type, Card Type, A/D Type, Primary Path, Primary Regen, Band Type, and State.

Flex Optical Source

Flex Optical Source Name.

SRLG

 SRLG Label, Spans, and State.

Network imports from Cisco Transport Planner

The Cisco Transport Planner network import is a compatibility feature that

  • allows you to import networks created and analyzed in Cisco Transport Planner into Cisco ONP, as .mpz files,

  • prevents the need to recreate existing networks, and

  • supports only networks from Release 11.0 or later for compatibility.

Supported hardware for CTP network import

Cisco ONP supports these hardware as part of CTP network import.

  • Optical source files and transponders

    See Supported Cards and Pluggables and Supported Optical Sources.

  • Contentionless, colorless, and colored point-to-point demands

  • Flex network

  • Gain Equalizer

    Note

    The Gain Equalizer node converts to a ROADM node when you unlock the site after a release upgrade.

  • ROADM-SMR-9 and SMR-20

  • All flex supported amplifiers, controller cards, and chassis types

Import an mpz design file from Cisco Transport Planner

Use this procedure to import an mpz file from Cisco Transport Planner to Cisco ONP.

Before you begin

  • Log in to the Cisco ONP web interface as a user with network creation permission.

  • Import the required optical source files and layout template using Manage > Optical Source and Manage > Optical Source options. For more information, refer to Manage Alien, and Manage Layout .

  • Delete the unsupported parameters for Cisco ONP from the mpz file. For example, mpz networks with P-Ring and A2A demands are not supported for import. Delete these demands in Cisco Transport Planner, reanalyze the networks in Cisco Transport Planner, and import the mpz file into Cisco ONP.

The network must be in design-analyzed or upgrade-analyzed mode.

Procedure

1.

Choose Import > MPZ.

The Import File (mpz) dialog box appears.

  1. Browse to the mpz file stored on your computer.

  2. From the Traffic Type drop-down list, choose 4K_1K_2K or 4K_2K.

    You can view this drop-down list only if you select an SSON MPZ file.

  3. Click Import.

    The mpz file is imported to Cisco ONP.

Note

If you view a blank screen when you click waves in the network tree, refresh the browser.
2.

Choose Network > Upgrade or Network > Release Upgrade to make any changes on the imported network.

Note

  • You cannot go back to design mode on the imported mpz network.

  • The wave label of imported mpz network in Cisco ONP is the service name present in the Cisco Transport Planner properties window.

Export the CPZ file

Cisco ONP saves the network design file as a .cpz file in its database. Use this process to export the design file to your computer.

The contents of the .cpz file depend on the network mode:

  • In design mode, the .cpz file includes the design file, layout template, and optical source details.

  • In analyze mode, the .cpz file contains several items: a design file, analyze file, ANS file, per-side ANS file, BOM, error messages, trace files, layout template, mpz, and report.

  • For networks in upgraded mode, you can only export the last child in the parent-child hierarchy.

Note

You can export only one network at a time.

Before you begin

Log in to the Cisco ONP web interface

Procedure

1.

Open the network whose design file that you want to export.

The network opens.

Note

If a blank screen appears when you open a network, refresh the browser or log in to Cisco ONP again.
2.

Choose Export > CPZ.
3.

Inside the Export .cpz file dialog box:

  1. Rename the file if necessary.

  2. If you want this operation to run in background, click the Run in Background check box.

    A notification appears after the background operation is completed. Go to Job Monitor to view the progression of the operation running in the background.

  3. Click Export.

The design file is stored on your computer. Starting with Release 26.1.1, the LUT version, and the user profile utilized in the current network will be included during the export of the network CPZ file.

Import the CPZ file

Use this procedure to import the cpz network design files that are exported from another Cisco ONP instance.

Note

You can import only the networks that are exported from the current release.

Before you begin

.

Procedure

1.

Choose Import > CPZ.
2.

In the Import .cpz file dialog box:

  1. Click Choose file, and select a cpz network design file that you want to import into Cisco ONP, from your local system.

  2. If you want this operation to run in background, click the Run in Background check box.

    After the background operation completes, you receive a notification. You can view the progress in Job Monitor.

  3. Click Import.

    If the names of the optical source and layout template files in the database and the imported network file match, Cisco ONP prompts you to confirm whether you want to overwrite the existing file.

    Note

    The message "Network already exists in the system with another user. New network will be created", you do not need to take any action. Cisco ONP automatically imports the network as a new network for you without changing the existing network.

  4. If you want to overwrite the existing file, check the Overwrite Network check box.

    If you do not check the box, Cisco ONP saves the imported network as a new network.

  5. Choose the optical source files and layout template that you want to replace.

    If you do not choose the optical source or the layout template file, the files will not be imported.

  6. Click Confirm.

The imported network is saved in the Cisco ONP database.
3.

(Optional) After you successfully import the CPZ network, choose a profile:

Note

If you had imported a CPZ network that was exported from Release 26.1.1, the user profile associated with that network is included and remains active. Apply a profile only if you have imported a CPZ network from earlier releases without an attached profile.

  1. Choose Network > Entity Editor.

  2. Click the network name and select the required user profile from the Profile drop-down-list.

    The applied profile affects only entities added to the network after the import. Existing entities remain unchanged.

Live Network Import

The Live Network Import (LNI) feature is a network import capability that

  • enables real-time import of deployed networks into Cisco ONP,

  • supports import of networks and nodes with NCS 2000, NCS 1010, NCS 1001, NCS 1004, NCS 1014 shelves and cards, and

  • allows you to view comprehensive deployed network details after import.

Table 9. Feature History

Feature Name

Release Information

Feature Description

Live network import enhancements

 Cisco ONP Release 26.1.1

The live network import feature now offers the following enhancements:

  • Supports the NCS 1001 platform.

  • Includes all NCS 1004, and NCS 1014 native transponders (except NCS1K14-2.4T-A-K9 and NCS1K-OTN-XP) for NCS 2000, NCS1010, and NCS1001 platforms.

  • Imports network with mixed nodes by grouping NCS2000, NCS1010, and NCS1001 nodes into separate, platform-specific Cisco ONP networks.

These improvements enhance network planning, boost automation, and ensure consistent, error-free network upgrades and configurations.
Table 10. Feature History

Feature Name

Release Information

Feature Description

Live network import from Cisco ONC

 Cisco ONP Release 25.1.1

Cisco ONP now directly communicates with Cisco ONC to perform a live network import, eliminating the need for Cisco ONP to be directly connected to a device or network. In addition to the previously supported NCS 2000, networks that include NCS 1010 nodes contained within NCS 1010 and NCS 1014 shelves can also be imported.
Table 11. Feature History

Feature Name

Release Information

Feature Description

Live Network Import

Cisco ONP Release 4.1

This feature allows you to import a live deployed network having NCS 1004, NCS 2000, and NCS 4000 nodes into Cisco ONP, using the LNI (Live Network Import) import template. This feature also allows you to view network topology, BOM, and layout report.

The Map displays the network topology, and you can check the node, fiber, service, and circuit properties through the Network Tree and the Entity Editor.

From Release 25.1.1, you can import a live network through Cisco ONC.

From Release 26.1.1, Cisco ONP supports these for all OLS platforms:

  • NCS 1001 platform is supported.

  • Upgrade and Release-upgrade are available for the imported network.

  • Netconf generation and ANS are available after upgrading the imported network.

  • LNI is supported for all NCS 1004, and NCS 1014 native transponders (except NCS1K14-2.4T-A-K9 and NCS1K-OTN-XP) for NCS 2000, NCS1010, and NCS1001 platforms

  • Mixed platform import:

    Mixed platform import allows nodes from different OLS platforms to be imported. Cisco ONP groups nodes from the NCS2000, NCS1010, and NCS1001 platforms into separate, platform-specific networks, because mixed-platform nodes cannot coexist in a single network.

    Each imported network uses a unique name in the format LNI__, which ensures clear distinction between platforms.

For more details on all hardware supported, see Configurations and hardware supported by LNI.

Perform live network import

Use this procedure to perform live import of a network from Cisco ONC.

Before you begin

  • Perform LNI only when the Cisco ONC is in a stable or running state. Do not perform LNI during the maintenance period for software upgrade.

  • Ensure that the release version of Cisco ONC you are using for the network import is 25.1.1 or above.

  • Cisco ONP removes any card that is not properly connected via IPC in Cisco Optical Site Manager during LNI. To retain equipment, ensure that each card has at least one valid IPC connection in Cisco Optical Site Manager.

  • Configure all the mandatory parameters on the circuit.

  • Check the card label set for these NCS 2000 cards and update it if they are not aligned.

    PID

    Card label

    NCS2K-16-AD-CCOFS

    AD-16-FS

    NCS2K-20-SMRFS

    SMR20-FS-CV

    NCS2K-20-SMRFS-L

    SMR20-FS

    NCS2K-9-SMR17FS

    SMR9-17-FS

    NCS2K-9-SMR24FS

    SMR9-24-FS

    NCS2K-9-SMR34FS

    SMR9-34-FS

    NCS2K-9-SMR34FS-L

    SMR9-34-FS

    15454-M-RAMAN-COP=

    OPT-RAMP-COP

    15454-M-RAMAN-CTP=

    OPT-RAMP-CTP

    NCS2K-OPT-EDFA-35

    OPT-EDFA-35

  • Log in to the Cisco ONP web interface

.

Procedure

1.

Choose Import > Live Import.
2.

In the Import Live Network dialog box:

  1. Enter CONC Server IP, Username, and Password.

  2. Click Import.

    The Import button will be enabled only when all the values entered are valid.
3.

View the status of the LNI operation:

  1. Click Job Monitor, to view the status of the IMPORT_LIVE_NETWORK task. Click Refresh to see the updated status.

    After LNI is completed, the job is removed from the Job Monitor page.

  2. Click Logs to view the list of events that are related to the LNI operation, as logs.

4.

After the completion of the LNI operation, choose File > Open.

The format of the LNI imported network filename is LNI_<Date>_<Time>.

5.

Click the imported network name to view the network under the Map tab and its corresponding network tree in the left panel.

You can view the tag Imported from Network in the interface.

Note

  • During the live import of a network with an optical source, if the configuration code of the optical source does not match, it will default to NCS1004_SP_16QAM_300G_27%SDFEC_69GBd. You can update the optical source in upgrade mode while the network is in a locked state.

  • The configurations that are supported by Cisco ONC can only be imported into Cisco ONP. See Configurations and hardware supported by LNI.

  • Even if errors occur during the LNI operation, the operation is not canceled. In this case, when you open the imported network, a warning message appears.

  • You can view the errors under the Elements > Messages tab. See both critical and noncritical messages.

    If you find unconnected equipment in the Messages tab, upgrade the imported LNI network and make the necessary adjustments to reintegrate the removed equipment into Cisco ONP. However, note that the newly created equipment UID may not match the one in Cisco Optical Site Manager. You can utilize the UID edit feature to align the UIDs between Cisco ONP and Cisco Optical Site Manager. Refer to Edit the Unique ID of the chassis

  • Each user is permitted to initiate only one LNI process at a time. If a user tries to start an additional concurrent LNI process, the system will terminate the new request and display an error message indicating the restriction. This limitation is applied on a per-user basis, allowing multiple users to run their own LNI processes simultaneously on the same CONC server, as long as each user adheres to the rule of having only one active process.

  • If both NCS and Non-NCS PIDS are present in the inventory, Cisco ONP enables the Enable NCS option. You can edit this option during upgrade after unlocking the site, if necessary.

What to do next

Click the BOM tab to view the BOM details of the network.
Note

The PIDs of prototype cards are shown as "NA" in the BOM details of the LNI network.

You can export the CPZ, import the CPZ, and share the imported network. Use the Entity Editor to view network properties.

Configurations and hardware supported by LNI

The live network import from Cisco ONC supports the configurations and hardware listed in this table.

Table 12. Configurations and hardware supported by LNI

Platform

Chassis

Card type

Card

Configurations
NCS 2000 1

NCS 2015

NCS 2006

NCS 2002

ROADM

NCS2K-20-SMRFS-L

NCS2K-20-SMRFS=

NCS2K-20-SMRFS-CV=

NCS2K-9-SMR17FS=

NCS2K-9-SMR34FS=

NCS2K-9-SMR24FS-L=

NCS2K-9-SMR34FS-L=

Contentionless

Unprotected circuits

Mixed configurations

Colored configurations

Colorless configurations

Add/Drop

NCS2K-16-AD-CCOFS

NCS1K-MD-64-C

15216-MD-48-ODD, and 15216-MD-48-EVEN Mux/Demux

MF-MPO-16-LC

MF-MPO-8LC

MF-6AD-CFS

Amplifiers

NCS2K-OPT-EDFA-17=

NCS2K-OPT-EDFA-24=

NCS2K-OPT-EDFA-35=

15454-M-RAMAN-CTP=

15454-M-RAMAN-COP=

NCS2K-EDRA2-XX

NCS2K-EDRA1-XX

Transponders

NCS2K-400GXP-L-K9

400G-CK-LC

200G-CK-C

200G-CK-C+10x10G-LC

NCS2K-200G-CK-LIC

NCS2K-200G-CK-LIC+ 15454-M-10X10G-LC

NCS1K14-2.4T-K9

NCS1K14-2.4T-X-K9

NCS1K4-QXP-K9​

NCS1K14-2.4TL-K9, ​

NCS1K4-2-QDD-C-K9​

NCS1K4-1.2T-K9

NCS1K4-1.2TL-K9

NCS 1010

NCS 1010

NCS 1014

ROADM

All OLT variants with Standard and Enhanced faceplate

Colored

Colorless

Unprotected Circuits​

Add/Drop

CCMD16-C

MD-32-ODD

MD-32-EVEN

BRK-24

BRK-8

Direct LC

Amplifiers

All ILA variants

Transponders

NCS1K14-2.4T-K9

NCS1K14-2.4T-X-K9

NCS1K4-QXP-K9​

NCS1K14-2.4TL-K9, ​

NCS1K4-2-QDD-C-K9​

NCS1K4-1.2T-K9

NCS1K4-1.2TL-K9
NCS 1001 NCS 1001 (Only terminal nodes)

Amplifiers

NCS1K-EDFA

NCS1K-PSM

Add/Drop

NCS1K-MD-32E-CE and NCS1K-MD-32O-CE

15216-FLD-4-XX.X

Transponders

NCS1K14-2.4T-K9

NCS1K14-2.4T-X-K9

NCS1K4-QXP-K9​

NCS1K14-2.4TL-K9, ​

NCS1K4-2-QDD-C-K9​

NCS1K4-1.2T-K9

NCS1K4-1.2TL-K9
1

Optical source interface import is not supported in NCS2000. By default, it is set to NCS1004_SP_16QAM_300G_27%SDFEC_69GBd. You can manually edit the optical source interface to the correct one during an upgrade, without unlocking the circuit.

Configurations and hardware unsupported by LNI

This section outlines the configurations and hardware that are not supported by the Live Network Import from Cisco ONC.

LNI does not support these configurations and hardware

  • NCS1K4-OTN-XP card

  • These transponder modes are not supported: 50G, 150G, 250G, 350G, 450G, and 550G

  • Configurations with Inline amplifiers

  • Regeneration and Protection circuits

  • NCS 1014 as a platform and NCS1K14-EDFA2 card

  • OTN cross-connects on the 400G-XP-LC module and OTN-XP card

  • NCS 1010 Omni configurations and NCS 1010 C+L configurations

  • Different Add/drop functionalities (Colored, Colorless, or Contentionless) at Source and Destination.

Limitations of LNI

These are the limitations, unsupported features, and known constraints of LNI, and scenarios where LNI may not function as expected and the available workarounds.

  • Simultaneous import of multiple live networks and scheduled import are not supported. LNI does not support importing Non-SSON networks.

  • If X, Y coordinates are not configured in the devices, nodes are overlapped in the Cisco ONP map.

    Workaround: Configure X, Y coordinates before importing the network for a better view of the topology in Cisco ONP map; otherwise, you can drag and drop the nodes in the Cisco ONP map and adjust the node position after importing.

  • Cisco ONP imports the proto-PID, if present in the inventory, and show as N/A PID in the Cisco ONP BOM. Duplicate media channel labels are not supported. If multiple media channels with the same label exist in the network, only one is imported; the rest are discarded.

  • Fiber name, source, and destination names may not match between imports; source and destination site names may interchange for bidirectional fibers. Fibers may not associate with the correct optical subnet if channel numbers differ at source and destination, causing amplifier output power issues. Workaround: Correct channel numbers at both ends and re-import or associate fibers with the correct optical subnet after upgrade.

  • Transponder cards that are not utilized for any circuits will be removed in Cisco ONP.

  • The NCS1000 BoM is not included for networks imported with NCS2000 and NCS1004/NCS1014. The NCS1000 BoM is populated following an upgrade analysis.

  • A combination of BRK-8 and BRK-24 on the same node is not supported.

Predefined user profiles

A predefined user profile is a user configuration template that

  • saves all settings across both network and all entities such as sites, fibers, , services, and circuits into a unified profile file,

  • is stored securely in the Cisco ONP database and can be modified or exported as needed, and

  • can be imported into the Cisco ONP environment to instantly apply the same configuration settings to designs.

Table 13. Feature History

Feature Name

Release Information

Feature Description

Reusable predefined user profiles

Cisco ONP Release 26.1.1

Now you can save all network and site-level settings into a reusable profile file, in the CONP database. You can use this profile during network designing ensuring consistent configurations across different designs and teams. This feature eliminates repetitive manual setup, reduces errors, and streamlines configuration sharing and management within an organization.

Cisco ONP lets you create reusable settings profiles that capture all configuration details for your planned or deployed networks. These profiles help you consistently apply, share, and manage settings across multiple platforms, including:

  • NCS2000 (Releases 11.1.0, 25.1.1, 26.1.1) with SSON/Non-SSON modes and various traffic types

  • NCS1010 (Releases 7.10.1 to 26.1.1)

  • NCS1001 (Releases 7.10.1, 25.4.1)

  • NCS1014 (Releases 25.1.1, 26.1.1)

By using profiles, you can eliminate repetitive manual configuration and reduce errors. Profiles are stored as JSON files in the Cisco ONP database and include network-level, site-level, fiber, and media channel settings, each with platform and version-specific compatibility.

Cisco ONP supports profiles for all key network entities, including:

  • Networks

  • Sides

  • Sites (ROADM, OLA, TRAFFIC)

  • Fibers

  • Media Channels/Waves/Circuits

Note

Only newly created entities, such as sites and fibers, will be affected after applying the profiles. Existing entities that were created before the profile application will not be impacted.

Create user profile

Use this task to create a user profile that stores configuration properties you can reuse when building new networks. This approach allows your organization to standardize network templates and share configurations easily.

Before you begin

Log in to the Cisco ONP web interface.

Procedure

1.

Choose Manage > Profiles.
2.

Create a new profile.

  1. Click Create New Profile.

  2. Enter the name of the profile.

  3. Select the Profile Details such as platform and the Release number.

  4. Click Fetch Default Properties to load the properties.

  5. Under the Properties pane,select the settings you want to include for future networks. Then click Save.

    Note

    You cannot set optical subnet properties in the profile at this time.

    Note

    Ensure all necessary entity properties are updated before saving. You can navigate between different entities to update properties and then save. Once saved, the profile cannot be modified. If changes are needed, users can clone and edit the profile.
3.

(Optional) Share the profile.

  1. Click Share.

  2. In the Share Profile window, select the groups and users you want to share the profile with and click Share.
4.

(Optional) Export the profile to JSON file format:

  1. Click Export, to download the profile file to your system.

    Exported files can be edited externally, backed up, or shared across Cisco ONP instances.
5.

(Optional) Import a profile.

  1. Click Import, and select the JSON file.

    The profile is imported to database and added to the user profile list.
6.

Delete a profile if you are the owner of that profile:

  1. Click Delete.

    The system prompts an error message if the profile was already in use, else asks for confirmation to delete

  2. Confirm to delete the profile.
7.

(Optional) Set the user profile as a default one:

  1. Click Manage Default Profiles and for each platform choose the Default Profile.

Limitations of user profiles

User profiles are subject to these limitations:

  • User profiles must be finalized before saving, as they cannot be modified afterward. To make changes, update all necessary entity properties while navigating between entities prior to saving. If further adjustments are required later, clone the existing profile and edit the clone.

  • If you import a CPZ network that was exported from Release 26.1.1, the user profile associated with that network is included and remains active. If you import a CPZ network from earlier releases without an attached profile, you can apply a profile using the Profile property at the network level. The applied profile affects only entities added to the network after the import. Existing entities remain unchanged.

  • When you upgrade a network that was designed in releases prior to 26.1.1, where no profile was attached, you can apply a profile, but it will only affect new entities added to the network after the upgrade, not the existing ones.

  • When creating a network using Excel, users can apply the profile. Values specified in Excel take precedence over the profile. For properties not available in Excel and set to Auto, they are updated according to the profile.

Convert NCS 2000 network to NCS 1010 network

Use this procedure to convert an NCS 2000 network (both SSON and non-SSON) into an NCS 1010 network.

Table 14. Feature History

Feature Name

Release Information

Feature Description

Convert NCS 2000 network to NCS 1010 network

Cisco ONP Release 5.1

The newly introduced NCS 1010 Convert option under the Network menu enables you to directly convert an existing NCS 2000 network into an NCS 1010 network. This conversion eliminates the need to build an NCS 1010 network from scratch.

Before you begin

Log in to the Cisco ONP web interface.

Procedure

1.

Open the NCS 2000 network that you want to convert to an NCS 1010 network.

Ensure that the network is in Design Mode, Upgrade Mode or Release Upgrade Mode.

2.

Choose Network > NCS 1010 Convert, then click OK.

The network is not converted and shows an error message if

  • the network contains traffic sites,

  • the fiber type is LS or TWClassic,

  • the network contains OTN services,

  • the Traffic Type property is set to anything other than Optical Source or Pluggable Card, and

  • the Traffic Type is 100G-SD-FEC or 200G-SD-FEC in non-SSON networks.
3.

Choose File > Save.

These parameters are automatically updated after the conversion:

  • Contentionless sides are deleted, and contentionless demands are automatically changed as colorless, and

  • protected channels are converted to two unprotected channels. The path, wavelength, regeneration sites, and cards that are configured are retained.