Design a network using Cisco ONP
You can design a network in one of these ways:
-
Manual Design―Create a network design using a design palette.
-
Import Design―Import a network design from an Excel sheet, Live Network Import or from an existing network from CTP, 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. The following 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 perform the following:
|
You can create any of the following 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
Perform the following steps to create a network in the Cisco ONP:
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
You can use the Shared Risk Link Group (SRLG) feature for routing protected services. You can create SRLGs through the Excel import file SRLG tab or through the Cisco ONP GUI using the following procedure:
![]() Note |
SRLG is supported only for the non-SSON network including the traffic nodes. |
Before you begin
Procedure
Step 1 |
Click the network tree panel in the left. |
Step 2 |
Expand Fibers, and check the check box next to each fiber in the same SRLG. |
Step 3 |
After all fibers are checked, right-click, and select Create SRLG. SRLG is created with a unique name. You can rename the SRLG. |
Import network using 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 Cisco 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. The following 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. |
![]() 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 CX UPT via Cisco ONP Import Excel option. CX 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 also export the entire network design data of an existing network in the form of the 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/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/MediaChannels tab. Make necessary changes in the exported Excel sheet before you import it into Cisco ONP. |
Before you begin
Procedure
Step 1 |
Choose .The template has the following mandatory tabs, and the respective fields to be filled in the Excel sheet.
|
||||||||||||||||||||||||||||
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 importing the network data. The View Data check box remains checked by default. Uncheck it of you do not want to view the imported data. |
||||||||||||||||||||||||||||
Step 4 |
Browse, select the saved file, and click Import. During the import for the Existing network, if the state is Locked, Cisco ONP does not consider the data, if the state is Unlocked, Cisco ONP changes the existing parameter, provided the network is in upgrade mode, and if the state is New, the parameters in the Excel is added as a new entry into the network. During new network import, new network design is created irrespective of the State.
|
Cisco Transport Planner network import support
You can import the networks that are created and analyzed from Cisco Transport Planner (CTP) to Cisco ONP, to avoid recreating the networks that are already created in CTP. The CTP network files are in .mpz format. You can, release upgrade, the imported networks.
![]() Note |
|
Supported Hardware
-
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 changes as a ROADM node when you unlock the site after the release upgrade.
-
ROADM-SMR-9 and SMR-20
-
All flex supported amplifiers, controller cards, and chassis types
Import MPZ Design File
Use this task to import .mpz file from CTP to Cisco ONP.
![]() Note |
Importing of mpz networks with P-Ring and A2A demands is not supported. Hence, we recommend you to delete these demands in CTP, reanalyze the networks in CTP and import the mpz into Cisco ONP. |
Before you begin
Log in to 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 Manage Alien and Manage Layout .
Delete the parameters that are not supported by Cisco ONP from the .mpz file and then import the .mpz file to Cisco ONP.
Procedure
Step 1 |
Choose .The Import File (.mpz) dialog box appears. |
||
Step 2 |
Browse to the .mpz file stored in your local system. |
||
Step 3 |
Choose 4K_1K_2K or 4K_2K from the Traffic Type drop-down list. If you had chosen an SSON MPZ file, you can view the Traffic Type drop-down list. |
||
Step 4 |
Click Import. The .mpz file gets imported to Cisco ONP.
|
||
Step 5 |
Choose or to make any changes on the imported network.
|
Export the CPZ File
Cisco ONP stores the network design file as .cpz file in its database. You can export the design file into your local system.
-
In design mode, the .cpz file includes the design file, layout template, and optical source details.
-
In analyze mode, the .cpz file contains 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 |
Choose . |
||
Step 2 |
In the Select Network To Open dialog box , click the network that you want to export, from the list of networks. The network opens.
|
||
Step 3 |
Choose . |
||
Step 4 |
In the Export .cpz file dialog box: |
Import CPZ File
You can 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
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. |
The Live Network Import (LNI) feature allows you to import deployed networks into Cisco ONP in real-time. This includes networks containing NCS 2000 nodes and NCS 1010 nodes contained within NCS 1010 and NCS 1014 shelves. To perform the LNI operation, you must have a Network Management role. Once the import is complete, you can view the entire deployed network details within Cisco ONP. 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.
Perform Live Network Import
Use this task 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 the following 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 top-right corner.
|
What to do next
![]() 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. You can check the properties of the network using the Entity Editor.
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.
Limitations of LNI
The LNI feature has these limitations:
-
You cannot perform multiple LNI at the same time.
-
Scheduled LNI is not supported.
-
LNI does not support:
-
Non-SSON Network import
-
Non-Contentionless configuration import
-
Import of NCS1001, NCS1004 and NCS4000 devices
-
-
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 the 400G-XP-LC, 200G-CK-C, and 200G-CK-C+ 10x01G-LC transponder cards are successfully imported.
-
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 any, present in inventory, and show as N/A PID in the Cisco ONP BOM.
-
Duplicate media channel label is not supported. If there are multiple media channels with same label present in the network, only one media channel is imported and the rest of them are discarded.
-
Fiber name, source, and destination names may not match between the first and the second import. Source and destination site names may interchange for bidirectional fibers.
-
Fibers may not be associated with correct optical subnet if the fibers are not configured with the same channel number at both source and destination ends. Due to this amplifier output power may not be within valid range. Hence, you either correct channel number at both source and destination nodes and re-import the network, or associate the fiber with correct optical subnet after network upgrade in Cisco ONP.