Design a network using Cisco ONP
A network design using Cisco ONP is a network architecture planning process that
-
allows users to create a new design manually or import an existing design,
-
supports integration with various sources and tools, 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.
Manually design a network using Cisco ONP
|
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. |
|
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. |
|
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:
|
|
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. |
|
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:
|
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
|
Step 1 |
Choose . |
||||||||||
|
Step 2 |
In the Create New Network dialog box, choose the required options to create a network.
|
||||||||||
|
Step 3 |
Click the Drawing Tool icon (pencil and ruler crossed), and add sites and other network elements. |
||||||||||
|
Step 4 |
Choose . |
Create shared risk link group
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
|
Step 1 |
Open the network where you want to create the SRLGs. |
|
Step 2 |
Click the network tree panel. |
|
Step 3 |
Expand Fibers, and check the check box next to each fiber that should be in the same SRLG. |
|
Step 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.
|
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. |
|
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:
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.
![]() Note |
Transponders are not supported as part of Export or Import Excel. When you export an existing network with transponder card forced, the exported Excel sheet will have the Traffic type set to Pluggable Card in DWDMChannels or MediaChannels tab. Edit the exported Excel sheet before you import it into Cisco ONP. |
Before you begin
Log in to the Cisco ONP web interface.Procedure
|
Step 1 |
Choose . 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. |
|
Step 2 |
Fill the network details in the template file or edit the current network file, and save the file. |
|
Step 3 |
Choose , and select the Import Type .
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. |
|
Step 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. |
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 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.
| 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 |
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
.mpzfiles, -
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 Optical Sources, and Supported Cards and Pluggables.
-
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 and 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
|
Step 1 |
Choose . The Import File (mpz) dialog box appears.
|
||
|
Step 2 |
Choose or to make any changes on the imported network.
|
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
Procedure
|
Step 1 |
Open the network whose design file that you want to export. The network opens.
|
||
|
Step 2 |
Choose . |
||
|
Step 3 |
Inside the Export .cpz file dialog box: |
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
|
Step 1 |
Choose . |
|
Step 2 |
In the Import .cpz file dialog box: |
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 networks with NCS 2000 nodes and NCS 1010 nodes within NCS 1010 and NCS 1014 shelves, and
-
allows you to view comprehensive deployed network details after import.
|
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. |
|
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. |
From Release 25.1.1, you can import a live network through Cisco ONC.
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.
-
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
Procedure
|
Step 1 |
Choose . |
||
|
Step 2 |
In the Import Live Network dialog box: |
||
|
Step 3 |
View the status of the LNI operation: |
||
|
Step 4 |
After the completion of the LNI operation, choose . The format of the LNI imported network filename is LNI_<Date>_<Time>. |
||
|
Step 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.
|
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.
|
Platform |
Chassis |
Card type |
Card |
Configurations |
|---|---|---|---|---|
|
|
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 |
|
Add/Drop |
NCS2K-16-AD-CCOFS |
|||
|
Amplifiers |
NCS2K-OPT-EDFA-17= NCS2K-OPT-EDFA-24= NCS2K-OPT-EDFA-35= 15454-M-RAMAN-CTP= 15454-M-RAMAN-COP= |
|||
|
Transponders |
NCS2K-400GXP-L-K9 NCS2K-200G-CK-LIC NCS2K-200G-CK-LIC+ 15454-M-10X10G-LC |
|||
|
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 and NCS1K4-QXP-K9​ |
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
LNI does not support these configurations and hardware:
-
NCS 1001 network import
-
NCS 2000 configurations that are either colored or colorless
-
NCS 1014 transponders used with NCS 2000 systems
-
EDRA-1, EDRA-2, OPT-EDFA-17, and OPT-EDFA-24 amplifiers
-
All NCS 2000 transponders except for 400G-XP-LC, 200G-CK-C, and 200G-CK-C+10x10G-LC
-
400G-XP-LC modules with various client and trunk combinations and remote TXP configurations
-
NCS 1010 Omni configurations and NCS 1010 C+L configurations
-
Regeneration circuits
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, Non-Contentionless configurations.
-
Importing a network with a mix of NCS 2000 and NCS 1010 nodes from Cisco ONC is not supported.
Workaround: Add either NCS 2000 nodes or NCS 1010 nodes into Cisco ONC and perform the Live Network Import for the selected node type.
-
When importing an NCS2000 network, only these transponder cards are successfully imported: 400G-XP-LC, 200G-CK-C, and 200G-CK-C+ 10x01G-LC.
-
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.
Feedback