Design and Analyze Networks

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

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. The following 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 perform the following:

  • Support NCS 4K-1K-2K multi-platforms

  • 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

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

Log in to Cisco ONP web interface.

Procedure

Step 1

Choose File > New.

Step 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 one of the following:

    • NCS 2000—To create 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—To create a network that contains only NCS 1010 nodes

    • NCS1001—To create a network that contains only NCS 1001 nodes

  2. If you want to create an SSON network, check the SSON Network check box, else leave it unchecked.

    This option is not for the NCS 1010 network.

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

    If you had chosen to create an SSON Network in the previous step, you can view the Traffic Type drop-down list.

    Note

     

    Once the network is created you cannot change the Traffic type from 4K_1K_2K to 4K_2K or vice versa. Hence, we recommend you export the network into an Excel sheet, do the required modification and then import it as a new network.

  4. 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.

  5. From the Band Type drop-down list for NCS 1010, choose one of the following:

    • 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.

  6. Click Create.

    You can view a map and the design palette. For more information, see Design Palette.

Step 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 into 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 updated as 1 km for all the fibers. If you want the length to be auto updated based on the x, y coordinates, then enable the Use Coordinates Distance property under the 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 in color) and add the service between the existing Traffic sites on the map.

  5. Click Circuit (purple in color), Media channel (purple in color), or Waves (red in color), 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.

Step 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 progression of the operation running in the background.

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

Log in to Cisco ONP web interface.

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

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 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.

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.

The following 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 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

Log in to Cisco ONP web interface.

Procedure

Step 1

Choose Export > Excel .

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

  2. Choose the File Type as xlsx or xlsm (Macro 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 includes mandatory tabs with respective fields to be filled in the Excel sheet. See 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 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. The network must be on 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 of 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 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.

Note

 

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 ), Traffic Type, NCS1010 Line Card, NCS1010 Band Type, Chassis Type, and System Release

Sites

Cisco Transport Planner network import support

You can import networks created and analyzed in Cisco Transport Planner into Cisco ONP. This avoids the need to recreate existing networks. Networks from Cisco Transport Planner are imported as .mpz files and must meet specific criteria:

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

  • Only networks from Release 11.0 or later are supported.

Supported hardware

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 MPZ Design File

Follow these steps to import .mpz file from Cisco Transport Planner to 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 Manage > Optical Source and Manage > Optical Source options. For more information, refer Manage Alien, and Manage Layout .

  • Delete the parameters that are not supported by Cisco ONP from the .mpz file. For example, importing of mpz networks with P-Ring and A2A demands is not supported. We recommend deleting these demands in Cisco Transport Planner, reanalyzing the networks in Cisco Transport Planner and importing the mpz into Cisco ONP.

Procedure

Step 1

Choose Import > MPZ.

The Import File (.mpz) dialog box appears.

  1. Browse to the .mpz file stored in your local system.

  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 had chosen 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.

Step 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 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

Log in to Cisco ONP web interface

Procedure

Step 1

Open the network.

  1. Choose File > Open.

  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.

    Note

     

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

Step 2

Choose Export > CPZ.

Step 3

In the Export .cpz file dialog box:

  1. If required, rename the file.

  2. If you want this operation to run in 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 progression of the operation running in the background.

  3. Click Export and save the file in your local system.

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

Log in to Cisco ONP web interface.

Procedure

Step 1

Choose Import > CPZ.

Step 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.

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

  3. Click Import.

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

    Note

     

    The error message "Network already exists in the system with another user. New network will be created" is just an information. You do not need to perform any action. Cisco ONP automatically imports as a new network specific to the user. There is no impact on the already existing network.

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

    If you leave the check box unchecked, 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.

Live Network Import

Table 9. 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 Live Network Import (LNI) feature enables you to import deployed networks containing NCS 1004, NCS 2000, and NCS 4000 nodes into Cisco ONP in real-time. 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, OTN service, and media channel properties through the Network Tree and the Entity Editor.

Perform Live Network Import

Use this task to perform live import of a network:

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.

  • Configure all the mandatory parameters on the circuit.

  • Make sure that the following Cisco IOS XR Software Maintenance Updates (SMUs) are loaded on the NCS 4000 devices on top of Cisco IOS XR Release 6.5.28:

    • ncs4k-6.5.28.CSCvu93045.tar

    • ncs4k-sysadmin-6.5.28.CSCvt67465.tar

    • ncs4k-6.5.28.CSCvv79518.tar

  • Make sure that there is a provision for opening three TL1 sessions per NCS 2000 device for Live data collection. NCS 2000 devices should not be overloaded with too many TL1 sessions.

  • Make sure that the fibers are configured with the same channel numbers (Spectral Density, ex: 91.0/82.0) on both source and destination ends.

  • 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

  • You must install Microsoft Excel in the Client Machine from where the browser is launched to open Cisco ONP application.

  • Log in to Cisco ONP web interface

.
Procedure

Step 1

Choose Export > Download LNI Import Template, and download the template which is in the form of an Excel sheet.

Step 2

Fill the template with the details of all the nodes belonging to the network to be imported and save the file.

The following fields are mandatory:

  • Node IP

  • User Name

  • Password

  • Connectivity Type―TL1 for NCS 2000 nodes and NETCONF for NCS 1004 and NCS 4000 nodes

  • Connectivity port―830 for NCS 4000 and NCS 2000 nodes

Note

 

Enter a value in the range of 60–180 in the Connectivity Timeout field or leave the field empty.

Step 3

Choose Import > Live Import.

  1. Browse and choose the saved file.

  2. If you want to clean the existing LNI database of the nodes and perform a fresh import, check the Fresh Import (Cleanup LNI Database) check box.

    Note

     

    We recommend fresh import of the live network.

    Leave this check box unchecked, if you want to import the details of only few of the nodes which had issues during the previous import.

    Note

     

    LNI import is not user-specific. When you perform a fresh import, Cisco ONP overwrites all the LNI data that are imported by the other users.

  3. Click Import.

  4. In the Device Onboarding dialog box, click OK.

    Note

     

    If you try to import a network of unsupported version, the device collection does not happen, and an error message "device collection failed" appears. See Supported Hardware and Software for LNI.

Step 4

View the status of the LNI operation:

  1. Click Job Monitor, and click Check Progress for the IMPORT_LIVE_NETWORK task, to view the status of the LNI operation in the LNI Progress dialog box. 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.

Step 5

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

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

Step 6

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

The aggregated node including NCS 1004, NCS 2000, and NCS 4000 is indicated in purple color, and the aggregated node including NCS1004 and NCS 2000 is indicated in orange color in the network tree. You can view the tag Imported from Network in the top-right corner.

Note

 

  • Even If some errors occur during the LNI operation, the LNI operation is not canceled. In such case, when you open the imported network, a warning message is displayed.

  • You can view the errors under the Elements > Messages tab.

    • Device collection failure is listed under critical messages.

    • The reason for failure is listed under noncritical messages.

  • 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.

  • Service path for the restored circuits is displayed as:

    • Primary Path: Working path before restoration

    • Secondary path: Protected path

    • Restoration path: Current work path after restoration

    Note

     

    If the circuit is not in the restored state, the restoration path is not shown.

  • SSON circuits carrying protected OTN services are merged as Client 1+1 protected Media Channel. Due to this, you may see difference in total number of SSON circuits between the imported network in Cisco ONP and the actual network.

  • If LNI is not installed properly, you may encounter the errors such as LNI failure or LNI not able to purge the data. In such cases, we recommend starting and stopping the LNI services in the server where Cisco ONP and LNI are installed using the following commands:

    • Stop the LNI services.

      root:~/$ONP_HOME# cd LNI
      root:~/$ONP_HOME/LNI# bash ciscolniinstaller.sh -o stop -t update -m offlinemode

    • Start the LNI services.

       root:~/$ONP_HOME/LNI# bash ciscolniinstaller.sh -o start -t update -m offlinemode

Note

 

Wait for a minimum of five minutes after starting the services, for the LNI services to resume before triggering a new live network import. You can

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. You can check the properties of the network using the Entity Editor.

Ports Used in LNI

LNI application uses the following ports. If any port is shut down due to any failure, then the service is restarted by the Docker system.

Port

Service

Usage

8761

Eureka Service

Registration and discovery service, which holds the information about all microservice applications

8080

API Gateway

Receives all the incoming requests, and then delegates the requests to internal microservices like LNI Broker

8080

Collector Service

Collects metrics and operation data from the devices

8080

Device Manager

Responsible for device onboarding process

8080

Inventory Service

Provides inventory data

9888

TL1 plug-in Service

South bound interface plug-ins for TL1 protocol-based NCS 2000 devices

8888

NCS 2K Inventory Adapter Service

Adapter module to transform NCS 2000 device response from collector to Cisco ONP NCMS schema-based POJO

8888

NCS 4K Inventory Adapter Service

Adapter module to transform NCS 4000 device response from collector to Cisco ONP NCMS schema-based POJO

8888

NCS 1K Inventory Adapter Service

Adapter module to transform NCS 1004 device response from collector to Cisco ONP NCMS schema-based POJO

9976

NETCONF plug-in Service

South bound interface plug-ins for NETCONF based 1K/4K devices

8888

LNI Broker Service

Provides interfaces for Cisco ONP BE service to trigger live network import

8085

Topology Service

 Provides network topology data

8090

Circuit Service

Provides network circuit data

8024

NETCONF Adapter Service

Common adapter for Topology and Circuit services

8888

Model Aggregator Service

Aggregates inventory, topology, and circuit details under NCMS schema-based networks

8092

TL1 Adapter Service

Common adapter for Topology and Circuit Service

5601

Kibana

Data visualization and exploration tool that is used for log and time-series analytics, application monitoring, and operational intelligence use cases

Note

 

The default Edge browser on Windows OS is not supported for viewing the Kibana logs. Cisco recommends using Firefox or Chrome browser for viewing the Kibana logs.

2181

Zookeeper

Keeps track of status of the Kafka cluster nodes, and also keeps track of Kafka topics, partitions publish-subscribe messaging system that enables inter service communication

9092

Kafka

Publish-subscribe messaging system that enables inter-service communication

5432

Postgres

Database to persist services data

Supported Hardware and Software for LNI

The following table describes the software versions and hardware requirements of the network imported through LNI.

Table 10.

Property

Values

Network

Network Type

SSON

Platform

ETSI

System Release

NCS 2000: R11.1, and R11.1.1.2

NCS 1004: XR 7.0.1

NCS 4000: XR 6.5.2.8

Site/Node

Site Type

4K-1K-2K: ADD/DROP, 1K-2K;Regen, 2K:ROADM/OLA

ROADM

SMR-20, SMR-9-17FS, SMR-9-34FS, SMR-9-24FS

Amplifier

RAMAN-CTP, RAMAN-COP, EDFA35-24, EDFA35-35

Degree Mesh Type

DEG-5/UPG-4

Chassis Type

4K: NCS4016, 2K:NCS2006, 1K:NCS1004

Power Supply

4K-DC, 1K-DC, 2K-DC40

ECU

ECU-S

Controller Card

TNCS-2, TNCS-2O

Channel Rule

82

Line Cards

NCS1K4-1.2T-K9=, NCS4K-4H-OPW-QC2

Evolved Mesh

ON and OFF

Node Protection

2K: Separated shelves, 4K: Single shelf

Mpo16Lc

MPO-16LC Unit

Mpo16ToMpo08

MPO16TO2MPO8Cable

Cascaded SMR

Yes

Enable NCS

Yes

Use Payg

No

Connection Verification

Yes, No

MF Unit

MF-6RU, MF6-10RU, or MF-1RU

Structure

Line, Multidegree, Terminal

Scalable upto degree

4, 8, 12

Power redundancy

Yes

IP Address

IPv4

Fiber

OSC Frame Type

Auto

DCN Extension

Yes

ENE/GNE

Yes

Length

Yes

Loss

Yes

Measurement Unit

KM

Length based Loss

No

Raman Amplified

Yes

Fiber Type

G652-SMF-28E

Connector Loss A

Yes

Connector Loss B

Yes

Cross OSC and Parallel OSC

Yes

Media Channel

Traffic Type

NCS1004_SP_16QAM_16QAM_300G_27%SDFEC_60GBd

Protection

Unprotected, and 1+R

Path

Actual Path

Regen

Regen site

Multicarrier

No

Contentionless

Yes

Circuit State

Restored, Unrestored

Service

Service Type

100GE, 10GE, STM-64

Protection

1+1, Unprotected, 1+R, 1+1+R, 1+1+R+R

Path

Actual Path

Client Type (1K)

OTU4

Interface Type (1K)

BH

Trunk Mode (1K)

200G, 300G

Baud Rate (1K)

60 and 69 GBd

Client Pluggable

ONS-QSFP28-LR4=, QSFP-100G-SR4-S=,ONS-QSFP-4X10-MLR=

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, circuits with NCS 2000 Transponder or Muxponder cards, or NCS1001, NCS1004, and NCS4000 devices.

  • The chassis position in the layout may not be accurate in the live imported network. NCS 2000, NCS 1004, and NCS 4000 chassis are placed in separate racks to provide a clearer layout view.

    Workaround: You can edit the layout after network upgrade and analysis.

  • 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.

  • The Scalable upto degree parameter is not imported from the real device. Cisco ONP chooses the maximum scalable up to degree based on the number of line sides and contentionless sides present on the node.

    Workaround: Unlock the node after upgrading and change the scalable upto degree. After unlocking the site, use the layout template to rearrange the layout.

  • 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.

  • If the regenerated demand is in restored state, the restored path is shown as working or protected path, and service protection is shown as 1+R in Cisco ONP. Restoration details will not be available. Service protection type is shown as 1+1+R or 1+1+R+R only if restoration path is available. Otherwise, it is shown as 1+1.

    Preprovisioned cards are not listed in the Cisco ONP BOM and are populated only after a successful upgrade and analysis of the LNI network. Ensure that the cards are equipped to retrieve the PID details.

Create optical subnet for Non-SSON networks

An optical subnet is a collection of spans with certain associated properties. When you create a new network, Cisco ONP automatically creates an optical subnet that is associated to the network. At least one optical subnet must exist for each network.


Note

Check the Current Subnet check box in the properties window below the network tree, to make the subnet you created as the current subnet. You cannot uncheck the Current Subnet check box.

Use this procedure to create an optical subnet for Non-SSON networks:

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Open the network:

  1. Choose File > Open.

  2. In the Select Network To Open dialog box, select the non-SSON network in which you want to create a subnet.

    The network opens.

Step 2

Expand Subnet in the network tree panel.

Step 3

Click the Ellipsis icon available in the right side of Optical Subnet.

  1. In the Create Optical Subnet dialog box, choose the C-band design rules for the new optical subnet that you want to create, from the Cband Rules drop-down list, then click Save.

A new optical subnet with the design properties you selected is created and placed in the network tree panel under OpticalSubnet.

Step 4

After the new optical subnet is created:

If you want to...

Then...

select a new spectral density

select a new spectral density from the Spectral Density drop-down list in the properties window displayed under the network tree.

add a fiber to a subnet

add a fiber to a subnet from the Fiber links drop-down list in the properties window.

The fiber now appears in the Fiber links field. When you select the optical subnet, its corresponding fiber is highlighted in the map.

add a fiber to a subnet from the network tree panel

  • Click the Ellipsis icon available in the right side of the required optical subnet and select Edit Fibers.

    In the Info dialog box, click OK.

    The UI freezes, and you can select a fiber only from the map.

  • Select the required fiber and click the Done button appearing near the zoom icon.

Note

 

When a fiber is added to one of the subnets, it is automatically removed from the other subnets. Only one subnet rule is associated with one fiber.

Create optical Subnet for SSON networks

The following procedure creates an optical subnet for SSON networks:

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Open the network:

  1. Choose File > Open.

  2. In the Select Network To Open dialog box, select the SSON network in which you want to create a subnet.

    The network opens.

Step 2

Expnad Subnet in the network tree panel.

Step 3

Click the Ellipsis icon available in the right side of Optical Subnet, and select Create Optical Subnet.

  1. In the Create Optical Subnet, choose the spectral density for the new optical subnet that you want to create from the Spectral Density drop-down list.

    The Name, CBand Rules, and Maximum Number of Channels the you see in the Create Optical Subnet dialog box, are set based on the spectral density that you have selected.

  2. Click Save.

A new optical subnet with the design properties you selected is created and placed in the network tree panel under OpticalSubnet.

Step 4

After the new optical subnet is created:

If you want to...

Then...

select a new spectral density

select a new spectral density from the Spectral Density drop-down list in the properties window displayed under the network tree.

add a fiber to a subnet

add a fiber to a subnet from the Fiber links drop-down list in the properties window.

The fiber now appears in the Fiber links field. When you select the optical subnet, its corresponding fiber is highlighted in the map.

add a fiber to a subnet from the network tree panel

  • Click the Ellipsis icon available in the right side of the required optical subnet and select Edit Fibers.

    In the Info dialog box, click OK.

    The UI freezes, and you can select a fiber only from the map.

  • Select the required fiber and click the Done button appearing near the zoom icon.

Note

 

When a fiber is added to one of the subnets, it is automatically removed from the other subnets. Only one subnet rule is associated with one fiber.

Create optical subnet for NCS 1010 networks


Note

From Release 7.9.1, both C-Band and L-Band optical subnets appear by default for the NCS 1010 networks.

For C-Band and C+L Futuristic networks, the L-Band optical subnet contains no fiber links. To add fiber links for the L-Band optical subnet, you must upgrade the existing network to a C+L-Band network or add an L-Band edge for each C-Band edge.

The following procedure creates an optical subnet for SSON networks:

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Open the network:

  1. Choose File > Open.

  2. In the Select Network To Open dialog box, select the NCS 1010 network in which you want to create a subnet.

    The network opens.

Step 2

Expand Subnet in the network tree panel.

Step 3

Click the Ellipsis icon available in the right side of Optical Subnet, and select Create Optical Subnet.

Step 4

In the Create Optical Subnet dialog box:

  1. Choose either C-Band or L-Band from the Band Type drop-down list.

    Note

     
    From R7.9.1, Band Type drop-down list is available when creating an optical subnet for NCS 1010.

  2. From the Spectral Density drop-down list, choose the spectral density for the new optical subnet that you want to create.

    From Release 5.2, the range of spectral density has increased (ranges 30–100).

    The Name, CBand Rules or LBand Rules, and Maximum Number of Channels values that appear in the Create Optical Subnet dialog box are set based on the spectral density that you have selected.

  3. Click Save.

A new optical subnet with the design properties you selected is created and placed in the network tree panel under OpticalSubnet.

Step 5

After the new optical subnet is created:

If you want to...

Then...

select a new spectral density

select a new spectral density from the Spectral Density drop-down list in the properties window displayed under the network tree.

add a fiber to a subnet

add a fiber to a subnet from the Fiber links drop-down list in the properties window.

The fiber now appears in the Fiber links field. When you select the optical subnet, its corresponding fiber is highlighted in the map.

add a fiber to a subnet from the network tree panel

  • Click the Ellipsis icon available in the right side of the required optical subnet and select Edit Fibers.

  • In the Info dialog box, click OK.

    The UI will freeze to allow fiber selection from the map.

  • Select the required fiber and click the Done button appearing near the zoom icon.

Note

 

When a fiber is added to one of the subnets, it is automatically removed from the other subnets. Only one subnet rule is associated with one fiber.

Convert a non-SSON network to SSON network

The following procedure converts non-SSON networks to SSON networks:


Note

You cannot convert a non-SSON network with Traffic Sites to SSON.

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Open the network:

  1. Choose File > Open.

  2. In the Select Network To Open dialog box, select the non-SSON network you wish to convert.

    Ensure that the network is in Design Mode. If the network is in Analyze mode, upgrade or release upgrade the analyzed network, then unlock all the channels, and force CFP-2 optical source.

Step 2

Convert to SSON:

  1. Choose Network > SSON Convert and click Ok.

  2. If you see the error message "Network cannot be converted to SSON due to following errors : [Network contains waves with invalid traffic types: [100G-SD-FEC, 200G-SD-FEC]]", follow these steps to resolve it:

    • Choose Network > Entity Editor > Services.

    • Expand Waves and navigate to trail, and click a trail.

    • From the Src Card Type drop-down list, choose any CFP-2optical source

    • Click Update, then choose File > Save.

    • Choose Network > SSON Convert again.

Step 3

In the Warning pop-up window, choose 4K-2K or 4K-1K-2K from the Traffic Type drop-down list, and click Ok. Note that 4K-1K-2K is the default option. After the network is converted, you cannot switch the site types between 4K-2K and 4K-1K-2K.

The non-SSON gets converted as SSON network.

Step 4

After the network is converted to SSON, select SSON optical source from the Traffic Type drop-down list in the properties window displayed under the network tree and click Update.

Convert NCS 2000 network to NCS 1010 network

Use the following task to convert an NCS 2000 network (both SSON and non-SSON) into to NCS 1010 network:

Table 11. 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 Cisco ONP web interface.

Procedure

Step 1

Open the network:

  1. Choose File > Open.

  2. In the Select Network To Open dialog box, select the non-SSON network that you wish to convert.

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

Step 2

Choose Network > NCS 1010 Convert, then click Ok.

The network does not get 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.

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

Step 3

Choose File > Save.

The following parameters are automatically updated after the conversion:

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

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

Share a network

Use these steps to share a network with one or more users or user groups:

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Open the network:

  1. Choose File > Open.

  2. In the Select Network To Open dialog box, select the network that you want to share.

    The network opens.

Step 2

Choose File > Share.

Step 3

In the Share Network dialog box, select one or more users or user groups, then click Share.

You can share the network with selected users or user groups in read-only mode.

Access a shared network

Use these steps to access a network shared by another user:

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Open a shared network:

  1. Choose File > Open Shared.

  2. In the Select Network To Open dialog box that lists the networks that are shared by other users, select a network.

    The shared network opens in read-only mode.

Step 2

Choose File > Save As.

Step 3

Enter the name in the Give a network name dialog box, and click Save.

A copy of the shared network is saved.

Note

 
You can work on this copy of the network, depending on the privileges of your user role. For example, if your user role is Designer, you can change the design of the saved copy of the shared network, but you cannot analyze the shared network.

Step 4

If you want, share the updated network with other users.

Unshare a network

Use these steps to unshare a network with one or more users or user groups:

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Open the network:

  1. Choose File > Open.

  2. In the Select Network To Open dialog box, select the network you want to share.

    The network opens.

Step 2

Choose File > Share.

Step 3

In the Share Network dialog box, remove the name of one or more users or user groups from the list, then click Share.

The shared network is no longer available to the users or user groups that are removed.

Analyze the network

Table 12. Feature History

Feature Name

Release Information

Description

Detailed Tooltip for Sites on the Map View

Cisco ONP Release 5.1

The See More Details option has been introduced in the tooltip displayed on hovering over Sites on the Map view of an analyzed network. This option shows the Amplifier data and PSD (Power Spectral Density) profile graph. The See More Details option avoids navigating to the Entity Editor to view these details.

Use this procedure to analyze the network after design completion.

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Open the network:

  1. Choose File > Open.

  2. In the Select Network To Open dialog box, select the network that you want to analyze.

    The network opens.

Step 2

Analyze the network:

  1. Choose Network > Analyze.

    The Cisco ONP analysis progress indicator indicates the analysis status. After successful analysis, the network goes to Analyze Mode.

  2. If you see the “Analysis Failed.” message, navigate to the Elements > Messages tab to see the list of error details in the analyzed network.

    By default, it shows only the key messages when the Critical Only toggle button is enabled. If you want to view the entire network message, disable the Critical Only toggle button.

  3. Resolve the error and analyze the network again. Repeat this step until all errors are resolved.

Note

 

The error message "Unexpected Situation 999" may occur when the optical simulation becomes inconsistent due to incorrect values of properties entered or modified while designing the network. Call Cisco TAC to know the exact cause of the error and modify the suggested property value for the successful analysis of the network.

Step 3

If you want to view the details such as Amplifier Data and PSD Profile graph for a site in an analyzed network, hover the mouse over a site and click See More Details.

The amplifier data includes output power, EOL gain, attenuator in, attenuator out, and Raman gain. The attenuator details are not displayed for the NCS 1010 site. The PSD profile graph is displayed only for the NCS 1010 site.

Bottom-Up Flow

Bottom-up support enables step-by-step creation of a network. Adding all the services and waves on day 0 itself is not mandatory to analyze the network and view reports. Bottom-up flow enables you to build a network over a period.

Day 0: Create a network with only the topology added. Add all sites and add fibers between them. Analyze the network and view the reports without adding any services or waves.

Day 1: Add waves between the sites that are added on Day 0 and newly added sites and fibers. Analyze the network and view the reports.

Day 2: Add services and tag waves that are created on Day 1 and newly added sites and fibers. Analyze the network and view the reports.


Note

After you have created the topology with sites and fibers added, you can add either a service or a wave. You need not follow any specific order.

Bottom-up flow is applicable only for Non-SSON networks. In order to achieve this, you must set A2A mode as A2A_fast in network properties. You can also set the A2A channel type as contentionless, colorless, and colored.

Idle Timeout in the Analyze Mode

If you keep the browser idle for more than 15 minutes, you are logged out of Cisco ONP. The default timeout is set to 15 minutes. The System Admin can disable this feature by changing the enabled option in the configuration file on the server to false. You can change the default time of 15 minutes by editing the duration option in the configuration file.

During a long network analyze cycle, you get logged out due to idle timeout, and the network analysis runs in the background. When you log back, the same network opens in one of the following states:

  • If the analysis is still on, the analysis progress bar is shown, and you cannot perform any other action.

  • If the analysis is complete, the network opens in the Analyze mode.

  • If the analysis has failed, the network opens in the design mode, and you can view the reason for failure on the Elements > Messages page.

The session time out does not redirect you to the login page always; so, reload or enter the URL again.

Upgrade the analyzed network

Table 13. Feature History

Feature Name

Release Information

Description

NCS 1010 Network Upgrade Flexibility

Cisco ONP Release 5.0

After a network is analyzed, all the network elements get locked. With this feature, you can selectively unlock certain network elements to upgrade the network further. This helps in preventing accidental updates to the part of the network that does not need any modification.

Use this procedure to upgrade an existing network that is in analyzed mode. You can change specific properties of a network element while keeping the network layout and design locked.

Upgrade is supported for NCS2K, NCS4K-2K, NCS4K-1K-2K, and NCS1010 networks.

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Open the network that you want to upgrade.

Step 2

Upgrade the network:

  1. Choose Network > Upgrade.

  2. Click Yes .

The message “Network Upgraded Successfully” appears. The network goes into upgrade mode and network elements such as sites, fiber, waves (for non-SSON), media channel (for SSON), and circuits (for NCS 1010) are locked.

Step 3

To modify a network element in the network tree panel, click the Ellipsis icon next to element, and choose Unlock.

Unlock individual elements at the node, side, add/drop card, or amplifier level in the network tree hierarchy.

If you want to change only the add/drop between MD-32-ODD/Even or BRK_24/16/8 in the NCS 1010 network, you can unlock the add/drop without unlocking the network elements that are higher in the hierarchy.

Make these modifications:

  • Edit properties of network elements.

  • Delete elements from the network.

  • Add a new site, wave, service, demand, optical subnet, or fiber into the network map.

Step 4

Choose File > Save.

The newly added elements are automatically displayed in the network tree panel, and by default, remain unlocked.

Note

 

To insert a node in upgrade mode, unlock the fibers connected to that node, then add the node to the network.

Step 5

Choose Network > Analyze.

After the analysis is completed, the newly added elements are locked, and the optical reports and installation parameters of the upgraded network are updated.

When you add services or fibers while upgrading a network with an applied layout template, the template updates to include the new service or fiber. You can export the template, make changes, and reapply it to another network.

Step 6

Choose Network > Design to further upgrade the newly upgraded network design.

Each time you upgrade the network, Cisco ONP saves the new version as a child network and maintains the parent-child relationship.

Upgrade LNI network

Use this procedure to correct errors in your LNI network, modify ,and reanalyze it, and view updated BOM, layout, connections, and optical results.

Table 14. Feature History

Feature Name

Release Information

Feature Description

Upgrade LNI Network

Cisco ONP Release 4.1

This feature allows you to upgrade and modify the imported LNI (Live Network Import) network as required. You can also correct LNI errors, reanalyze the network, and view the updated parameters such as BOM, layout, connections, and optical results.

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Open the network imported through LNI that you want to upgrade.

Step 2

Upgrade the network:

  1. Choose Network > Upgrade.

  2. Click Yes .

    The message “Network Upgraded Successfully” appears. After you upgrade the network, it enters upgrade mode, which locks elements such as sites, fiber, OTN services, and media channels.

Step 3

To modify a network element in the network tree panel, click the Ellipsis icon next to element, and choose Unlock.

Unlock individual elements at the node, side, add/drop card, or amplifier level in the network tree hierarchy.

Make these modifications:

  • Edit the properties of network elements.

  • Delete elements from the network.

  • Add a new site, wave, service, demand, optical subnet, or fiber into the network map.

Step 4

Choose File > Save.

Each time that you upgrade the network, Cisco ONP saves the new version as a child network and maintains the parent-child relationship.

Step 5

Choose Network > Analyze.

Analysis succeeds only if the imported network is consistent and valid. If the analysis fails, perform the listed steps:

  1. Check the reports under Elements Messages for failure reasons.

  2. Resolve the issues by modifying the network manually in Cisco ONP or re-importing the network after correcting the errors.

  3. Reanalyze the network.

Step 6

After analyzing the network:

  1. Click the Layout tab and edit the layout manually to adjust chassis or card position for NCS 4000 and NCS 1004 platforms. See

  2. Click the BOM tab and the Results tab to view the BOM and optical results.

Media channel unlocking scenarios

This table explains the various media channel conditions and the unlocking possibilities.

Table 15. Media channel unlocking scenarios

Conditions

Unlocking possibilities

The channel has OTN services. In 4K-2K cases, the service maps directly to the channel. In 4K-1K-2K, the service maps to the channel through the OTU4 trail.

Cisco ONP throws an error indicating that there are OTN services associated with the media channel. First, unlock the associated OTN services. Then, unlock and delete the media channel. You cannot update or delete the channel before unlocking the associated services.

Channel does not have OTN services going over it. For example, in the case of 4K-1K-2K, the media channel carries empty OTU4s.

Cisco ONP allows you to unlock the channel.When you unlock the channel, the properties of the channel and its child entities like Trail and Section are not cleared automatically, whether you or the system assigned them. You can only unlock the channel automatically if there are no associated OTU4s.

After unlocking the channel, you can delete the channel. You cannot update the properties of the channel or its child entities. When the properties of the media channel or any of its child entities are auto-assigned, the system clears and sets only the wavelength to Auto. All other properties are not cleared.

Channel has neither OTN services nor OTU4(s) going over it. In case of 4K-1K-2K networks, Media Channel does not carry even empty OTUs.

Cisco ONP allows you to unlock the channel and automatically clears auto-assigned properties. After unlocking you can perform these:

  • Update various properties of the channel and its child entities.

  • Delete the channel.

Possible error scenarios and the workarounds

This table provides the workarounds for the errors that are shown under the Elements > Messages tab.

Table 16. Error scenarios and the workarounds

Error message

Workarounds

Device Authentication failure

Check the username and password of the device provided in the LNI input Excel file. Retry the LNI import using valid device credentials.

Device collection failed or Device not reachable.

Check for any connectivity issues in the setup. Fix any identified issues and retry the LNI import.

In Site4.A, output power setting is not supported by the amplifier.

Unlock C-Band amplifiers for side A within Site4 in the Network tree, and set the correct output power. If you are unsure, choose Auto and analyze the result. Cisco ONP chooses the best value based on the configuration.

Cannot Route demand! Did not find any valid Omnidirectional Side.

For protected OTN or SSON services, ensure that at least two contentionless sides are present on both the source and destination sites. Add contentionless sides where necessary, then analyze the network configuration.

  • Demand OTU3 has unrecognized type [OTU3]

  • ServiceGroup does not support the demandType OTU3 for OTU3

Only 100GE, 10GE, and STM-64 service rates are supported. If a different service rate exists in the network, unlock the specific service, change it to a supported service type, update the ODU time slot accordingly, and analyze the changes.

Primary OTN Demand [100GE_Flex] has invalid Timeslot ranges. Allowed ranges are [1-80]

100GE service type must have ODU time slot in the range of 1–80. If any other value is set, update the correct value or leave it blank so that Cisco ONP can set it to the correct value.

Cannot complete mesh connections at Site3.

Unlock the site and reanalyze.

No OTN demand found for NCS4K trunk port - NCS4016-B - OTU40/8/0/1.

No action required. This is an information message to the user.

Fiber between Node1.A and Node2.B has an invalid value in connector loss value

Unlock the corresponding fiber couple and update the connector loss value so that it is greater than zero. The typical value is 0.2.

Fiber between Nod1.C and Node2.C has an invalid value in Tot SOL Loss w/o Connectors.

Unlock the corresponding fiber couple and update the Tot SOL Loss w/o Connectors value so that it is greater than zero.

Span Fiber-2 is forced as Raman but no traffic is present.

Remove Raman forcing on the fiber, or force the path for a service to ensure it travels through a Raman-enabled span.

Couple Fiber-2 has Raman enabled on the duct but corresponding Raman Forcing is missing.

Force RAMAN-CTP or COP on the Fiber-2 connecting node interface, or remove RAMAN forcing on the Fiber-2.

Note

No specific action is required for noncritical messages. These are just information messages to the user.

Upgrade the software release of a network

Table 17. Feature History

Feature Name

Release Information

Feature Description

Release Upgrade

Cisco ONP Release 4.1

This feature allows you to choose the NCS 2000 system release to the desired release (11.1.0, 12.0.1, or 12.1.0), while performing the release upgrade of CTP network, Cisco ONP network, network imported through Excel, and LNI network.

You can upgrade the software version of networks that are imported from CTP, created in Cisco ONP, LNI Network, or imported from Excel to any desired release version. The release upgrade is supported for both SSON and non-SSON networks that have NCS 2000 nodes with ROADM, OLA, Traffic, or Passthrough functionality, and NCS 1010 networks.

Release upgrade is supported starting with NCS 2000 Release 11.1.0.


Note

NCS 2000 supports SVO from the Release 12.1.0.

The table shows the available upgrade releases for each network type.

Table 18. Supported upgrade paths for network system releases

Network

Upgrade Release

CTP network (.mpz)

  • From 11.0.0 to 11.1.0, 12.1.0, 12.2.0, and 12.3.1

  • From 11.1.0 to 12.1.0, 12.2.0, and 12.3.1

Cisco ONP network

  • From 11.0.0 to 11.1.0, 12.1.0, 12.2.0, and 12.3.1

  • From 11.1.0 to 12.1.0, 12.2.0, and 12.3.1

  • From 12.1.0 to 12.2.0, and 12.3.1

Excel imported network

  • From 11.0.0 to 11.1.0, 12.1.0, 12.2.0, and 12.3.1

LNI network

  • 11.1.0 to 12.0.1, 12.1.0, and 12.3.1

  • 11.1.0 to 12.1.0, 12.2.0, and 12.3.1

  • 11.1.0 to 12.0.1, 12.1.0, and 12.3.1, 25.1.1

  • 11.1.0 to 12.1.0, 12.2.0, and 12.3.1, 25.1.1

Note

 

You cannot directly release upgrade an LNI network. Perform the following:

  • Upgrade the LNI network. see )

  • Analyze the network. (see Analyze the network

  • Release upgrade the analyzed LNI network.

NCS 1010 Network

  • 7.7.1 to 7.9.1, 7.10.1, 7.11.1, 24.31

  • 7.9.1 to 7.10.1, 7.11.1, 24.31

  • 7.10.1 to 7.11.1, 24.31

  • 7.11.1 to 24.31

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Open the network in which you want to perform the system release upgrade.

Step 2

Upgrade the software release of the network:

  1. Choose Network > Release Upgrade.

  2. From the New System Release drop-down list, choose the system release of NCS 2000 or NCS 1010, to which you want to upgrade.

  3. Click Submit.

    The upgraded network is saved as a child network.

    The network elements are locked in the network tree after the release upgrade. You can unlock and modify the elements.

    Note

     

    If the PMD coefficient does not get updated with the expected value, update the fiber type first, followed by the PMD value when you edit the fiber properties.

Plan mode

Plan mode is a feature that

  • enables what-if analysis on existing network designs,

  • simulates network behavior under failure scenarios, and

  • determines the ability to reroute services without providing guidance for expanding network infrastructure.

Table 19. Feature History

Feature Name

Release Information

Feature Description

What-if Analysis for OTN Services

Cisco ONP Release 4.1

This feature extends the current implementation of What-if analysis for the OTN Services that are connecting the aggregated nodes. The failure report includes the number of failed services, restored services, and unrestored services. This feature is supported forsworn (4K-1K-2K and 1K-2K) and non-SSON (4K-2K) networks.

Advantages of plan mode

The advantages of the plan mode are:

  • Simulates and analyzes potential network issues and solutions,

  • focuses on rerouting capabilities, and

  • avoids requiring physical changes to network infrastructure.

Supported network elements

Supported network elements in plan mode include:

  • An NCS 2000 aggregated node that includes ROADM, OLA, and passthrough nodes

  • Traffic nodes including1K-2K, 4K-2K, and 4K-1K-2K

  • Nodes created in Cisco ONP

  • Networks imported from Cisco Transport Planner in mpz format

  • Networks imported from LNI

Limitations of plan mode

Plan mode has these limitations:

  • Only users with PLANNER and ADMIN roles can access the Plan mode.

  • Plan mode does not guide you in turning up new wavelengths or adding new network components.

Perform a what-if analysis on an analyzed network in the Plan mode

Use this procedure to perform a what-if analysis of a network and export the failure report in the Plan mode.

Before you begin

Log in to Cisco ONP web interface as a user with admin or planner role.

Procedure

Step 1

Open an analyzed network.

Step 2

Choose Network > Enter Plan Mode.

The network switches to Plan mode. In this mode, you can perform what-if analysis by failing fibers and sites.

Step 3

Fail the sites:

  1. In the network tree panel, expand Sites.

  2. Click the Ellipsis icon available in the right side of the site, and select Fail. Alternatively, right-click a site on the map and select Fail.

  3. To fail multiple sites, check the check box next to each fiber, and then select Fail.

Step 4

Fail the fibers.

  1. In the network tree panel, expand Fibers.

  2. Click the Ellipsis icon next to the fiber, and click Fail. Alternatively, right-click a fiber in the map and select Fail.

  3. To fail multiple fibers, check the check box next to each fiber and then select Fail.

    When a fiber fails, all media channels or waves, OTN services, and demands that pass through the failed fiber also fail. Symbols on the map indicate these failures:

    • Failed channels: Red cross

    • Fibers impacted due to site failure: Yellow cross

    • Restored channels: Green check

  4. To undo the fiber failure, click the Ellipsis icon next to the fiber, and click Undo Fail.

Step 5

If needed, Create a failure set.

Step 6

Restore the failed fibers by clicking Restore.

The restored channels are indicated by a green check mark in the network tree and map.

All media channels or waves, and demands that pass through the restored fiber are also restored. The Path Computation Element (PCE) restores OTN services based on optical feasibility and OTN constraints.

Step 7

After restoring the fibers, export the failure report:

  1. Choose Export > Failure Report to export the failure report as an Excel file. The failure report includes the parameters described in Failure report.

  2. Alternatively, you can click Export in the Failure Report area under the map.

The failure report provides details about unrestored channels and the reasons for restoration failure under the Elements > Messages tab.

Step 8

Exit the Plan mode.

  1. Choose Network > Exit Plan Mode.

Create a failure set

Use this procedure to create and manage failed fibers and sites as a failure set within a failure group. You can simulate or track network outages efficiently in a single action.

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Open a network and enter the Plan mode.

Step 2

Click the Ellipsis icon next to the Failure Groups option in the network tree panel.

Step 3

Click Add Failure Group.

A failure group gets created.

Step 4

Add fibers and sites to the group.

  1. Choose the Fibers and Sites to fail by selecting the check boxes next to them.

  2. Click the Ellipsis icon next to the chosen Fibers and Sites, and click Fail.

Step 5

Click the Ellipsis icon next to the network name and click Add Failure Set.

Step 6

Select the failure group to which the failed fibers or sites must be added.

The system creates the failure set under the failure group and adds the failed fibers or sites to it.

Note

 

If a network has dark fibers that do not carry traffic, the system does not consider those paths for restoration.

Failure report

The failure report shows these parameters:

Report

Description

Failed Fibers

Shows the failed fibers in the network.

Failed Sites

Shows the failed sites in the network.

Impacted Fibers

Shows the fibers that are impacted due to the site failure.

Total Channels

Shows the total number of media channels in the network.

Failed Channels

Shows the total number of media channels that are passing through the failed ducts or sites in the network.

Restored Channels

Shows the total number of media channels that are restored from the failure state.

Unrestored Channels

Shows the total number of media channels that are not restored from the failure state due to the unavailability of alternate paths.

Fiber HotZones

Shows the fibers that have utilized greater than or equal to 80% of the bandwidth. You can modify the threshold by updating the value in the Feature.Properties file.

  • Fiber: Shows the fibers that are listed under fiber hot zones.

  • Utilization Before (%): Shows the percentage of bandwidth that is utilized before the channel restoration.

  • Utilization After (%): Shows the percentage of bandwidth that is utilized after the channel restoration.

Total Services

Shows the total number of services going through the fiber that was failed.

Failed Services

Shows the number of failed services going through the fiber that was failed.

Restored Services

Shows the number of restored services going through the fiber that was restored.

Unrestored Services

Shows the number of unrestored services going through the fiber that was restored.

Automatic suggestion for regeneration sites in Plan mode

Table 20. Feature History

Feature Name

Release Information

Feature Description

Automatic Suggestion for Regeneration Sites

Cisco ONP Release 5.0

Cisco ONP displays feasibility report in the Plan mode. This report automatically suggests regeneration sites for the channels with high and marginal risk of failure. You can incorporate these regeneration sites in the optical network to make the channel optically feasible. This feature avoids multiple iterations required to manually create the regeneration sites and test the optical feasibility of large networks.

Optical network feasibility assessment

Cisco ONP identifies networks that are not optically feasible, focusing on channels with a high or marginal risk of failure. These risks are highlighted in red and orange on the Optical Results page, indicating End of Life (EOL) and Start of Life (SOL) issues.

Regeneration site suggestions

To address optical feasibility issues, the Path Computation Element (PCE) runs a regeneration suggestion algorithm. This algorithm proposes potential regeneration sites. When entering plan mode, Cisco ONP presents these suggested regeneration sites within the Feasibility Report, located at the bottom of the map. You can apply these suggestions to enhance network feasibility.

For channels with pre-existing regeneration, the system provides suggestions at the section level.

The Feasibility Report table encompasses several fields, which are crucial for assessing the optical feasibility of the network.

Table 21. Feasibility Report

Field

Description
Channel Name

Displays the list of channels (trail and sections) that are not optically feasible.

Alarm

Displays the color of alarm (red, orange, or yellow)

Paths

Displays the actual path of the channel as hyperlink. If you click the link, the path is highlighted in the map.

Suggested Regens

Displays the intermediate sites that can be used as regen sites so that the channel becomes optically feasible.

Exporting the Feasibility Report

You have the option to export the Feasibility Report. Click Export.

The Suggested Regen field in the report may display as "NA" for the following reasons:

  • Negligible Loss: Channels with yellow alarms indicate negligible loss, thus not requiring regeneration suggestions.

  • Insufficient Intermediate Sites: When high loss occurs and there are not enough intermediate sites available to mitigate the overall loss.

  • Lack of Contentionless Sides: Intermediate sites without added contentionless sides are not considered viable for regeneration sites.

Support for various network configurations

Auto regeneration site suggestion functionality is available for both SSON and non-SSON networks that includes contentionless channels or waves between NCS2K (ROADM) or 4K-1K-2K (TRAFFIC) sites.

Apply the suggested regen sites

Use this task to apply the suggested regeneration sites to make the network optically feasible.

Before you begin

Log in to Cisco ONP web interface as a user with admin or planner role.

Procedure

Step 1

Open an analyzed network.

Step 2

Enter the plan mode.

Step 3

Apply the suggested regen sites to the network.

  1. Choose Network > Open Feasibility Report.

    The Feasibility Report is displayed at the bottom of the map.

  2. Select the channels for which regeneration has to be applied and click Apply.

  3. In the Suggested Regen Applied dialog box,click Ok .

Step 4

Exit the Plan mode.

  1. Choose Network > Exit Plan Mode.

  2. Click Yes in the Warning dialog box.

The network gets auto upgraded and saved as a new network. The channels with regens applied are unlocked with the Regen Sites property auto updated and noneditable.

Step 5

Analyze the network.

In the Optical Results page, the SOL, and EOL fields become green, and the channels are not displayed in the feasibility report again when you switch to the plan mode.

Import Optical Sources

Table 25. Feature History

Feature Name

Release Information

Feature Description

Create Optical Source using Excel Sheet

Cisco ONP Release 5.0

You can create an optical source by defining the details of interfaces and the corresponding optical classes in an Excel template. This feature provides you with the flexibility to create any required optical source based on existing or new traffic resources.

Optical Source Wavelength is a way to connect a DWDM interface from any external element to a third-party optical network.

Use this procedure to import an optical source:

Before you begin

Log in to Cisco ONP web interface.

If you want to import the optical sources from an Excel sheet, download the template by choosing Export > Optical Source Template. Fill the necessary details in the Interfaces and Optical Classes sheets of the downloaded template and save the file. See Optical Parameters Available in the Excel Sheet for Optical Sources Creation.

The fields in the columns D, E, and F that are not mandatory are hidden by default in the Interfaces sheet of the template. You can expand the columns and fill the details.

Procedure

Step 1

Choose Manage > Optical Source.

The Manage Optical Source dialog box appears. The default optical sources available in the server are:

  • OpticalSources_NCS2K_400GXP-LC_NCS4K-4H-OPW-QC2

  • NCS1004_OpticalSources_V3

  • ONS-CFP2D-400G-C-OpticalSources-V2.mxd

  • QDD-400G-ZRP-S-OpticalSources-V2.mxd

Note

 

By default, all existing optical source files are loaded in the server.

Step 2

To import optical source as .mxd file:

  1. Click Add.

  2. Choose Optical Source (.mxd)

    The Import Optical Source (.mxd) dialog box appears.

  3. Click Choose File and browse to the .mxd file stored in your local system, and click Import.

    After the optical source is imported, a list of related interfaces appears.

Step 3

To import the optical source from an Excel sheet:

  1. Click Add.

  2. Choose Optical Source (.xlsx)

    The Import Optical Source (.xlsx) dialog box appears.

  3. Click Choose File and browse to the .xls file (optical source template) saved in your local system, and click Import.

  4. Choose the Release Version of the NSC2K network.

  5. Select the interface.

    If you want all the interfances, then click Select All.

  6. Click Create.

    After the optical source is imported, a list of related interfaces appears.

Step 4

Choose the interfaces to import by checking the check box next to them. The selected interfaces get added to the Type drop-down list in the properties window of the network tree.

When you create waves, you can use the interfaces in the Type drop-down list.

What to do next

Go to Download Optical Sources to download optical source for Cisco ONC.

Optical Parameters Available in the Excel Sheet for Optical Sources Creation

The following parameters are available in the Excel sheet template for creating optical sources.

Table 26. Optical Parameters for Creating Optical Sources

Parameters

Description

Interface Name

The name of the interface. It should be unique for all the interfaces that are added in the file.

Vendor Name

The name of the vendor.

Vendor IDs

The vendor IDs.

Platform

The name of the platform.

Pluggable PID

The PID of the pluggable.

Name

It is the combination of the Data Rate and Open Config Code. For example: R400G#5000.

FEC

The forward error correction type for the given interface.

Data Rate

The line rate for the given interface.

Mod Format

The modulation format to be used for the interface.

Baud rate

The baud rate for the given interface.

BPS

The speed of data transfer (bits per symbol) for the given interface.

Open Config Code

The unique code assigned to the interface as specified by the Open Industry Standard for optical networks. For example: 5000.

Sub Mode

Enter the sub-mode if there are any associated with the interface. If not, leave it blank.

Trunk Rate

The trunk rate of the transponder.

Nominal Bit Rate

The bit Rate for the interface

BER Target

The post FEC BER Target for the interface

Power Min and Power Max

The minimum and maximum Tx Power for the interface.

Ovl

The overload power limit for the interface

OL Power

The Rx power sensitivity for the interface.

OL OSNR

The Rx OSNR sensitivity for the interface.

PL Power

The extended Rx power sensitivity.

PL OSNR

The Rx OSNR sensitivity at the extended Rx power sensitivity.

Variance

The variance in power in the Txp.

Opt Class

The optical class to which the interface will be mapped.

InBand OSNR

The Tx OSNR contribution due to laser instability inside the Txp.

Out of Band OSNR

The Tx OSNR contribution due to Add/Drop at 80% and 100% channel spectral density.

ONC Release

The Software release of Cisco ONC from which this interface will be supported.

Interface Type

It is the same as the name of the interface.

Min and Max Frequency

The operating frequency range of the interface.
Table 27. Optical Class Parameters

Class Parameters

Description

Interface Type

The name of the interface. Enter the same name of the interface, if you are doing one to one mapping with the interface.

Opt Class

You can create the optical classes for different optical sources. Certain optical parameters are added in the optical class. Based on interface properties, multiple interfaces can be mapped to the same class.

Enter a unique alphanumeric name for the Optical class. While creating new optical classes, we recommend using the name starting with “X” to avoid overlapping in the existing classes.

Bit Rate

The bit rate for the given interface.

Baud Rate

The baud rate for the given interface.

ModGB Coeff

The modulation guard band coefficient.

Modulation OSNR Penalty

The modulation OSNR penalty.

GBf

The filtering GuardBand at different OSNR penalties.

Mux/Demux Filtering Penalty

Enter the mux/demux filtering penalty value, if there are any.

Chromatic Dispersion

The chromatic dispersion limit at different OSNR penalties.

Find Optical Sources Faster

Use these steps to find the optical sources faster.

Before you begin

Log in to Cisco ONP web interface

Procedure

Step 1

Choose Manage > Optical Source.

The Manage Optical Source dialog box appears.

Note

 

By default, all existing optical source files are loaded in the server.

Step 2

To find the customized optical sources:

  1. Check Show only line rate tuner generated sources.

    The dialog box displays only the customized optical sources.

Step 3

To filter the required optical source:

  1. Enter the optical source name in the Search box.

    The dialog box displays the optical sources matching the typed keyword.

Download Optical Sources

Use this procedure to download an optical source:

Procedure

Step 1

Choose Manage > Optical Source.

The Manage Optical Source dialog box appears.

Step 2

Choose an optical source to download.

Step 3

Click Download and select one of the following options to download the optical sources.

  • .mxd—Downloads the selected optical sources as .mxd file.

  • .xlsx—Downloads only the optical sources which were created and added using the Excel template, as .xls file. Others such as the optical sources which were directly added as .mxd file, are not included in the .xsl file.

  • .xml—Downloads the optical source data as a .xml file. This file contains the application codes for circuit provisioning in Cisco ONC, optical parameters of the interfaces, PIDs, and Vendor ID information. You can load the .xml file into Cisco ONC to create circuits with these optical source interfaces. See Alien Import.

    After the import is successful, the optical source will be present under the Application Code tab in the Service Manager screen of the Cisco ONC application. See Service Manager.

Delete Optical Sources

Use this procedure to delete an optical source:

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Choose Manage > Optical Source.

The Manage Optical Source dialog box appears.

Step 2

Choose an optical source to delete.

Step 3

Click Delete to delete the selected optical sources.

Layout Template for NCS 2000 Network

Layout templates are reusable templates that are used to design layout configurations for the NCS 2000 network. When you have an NCS 2000 network with fixed layout rules applicable for multiple nodes, you can use these templates to accurately set up the layout for those nodes. These templates save you time, effort, and they minimize errors.


Note

Layout template is not supported for a mix of TXP and Real card label of transponders.

Export Layout Template

Table 28. Feature History

Feature Name

Release Information

Feature Description

Layout Template Enhancement

Cisco ONP Release 4.1

 This feature allows you to export the layout template for an individual site or for all the sites. The layout template export is possible only if the network is analyzed in Cisco ONP Release 4.1. The export of layout template is supported on 4K, 4K-1K-2K, and 2K nodes.

Use the following procedure to export the layout template of a specific site or all sites:

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Choose File > Open.

The Select Network To Open dialog box appears.

Step 2

Click the network whose network layout template you want to export.

The network opens.

Step 3

Choose Network > Analyze.

Note

 

Network must be successfully analyzed to proceed further.

Step 4

Click the Layout tab.

Step 5

Click the name of a site in the left side panel, for which you want to download the layout template.

Step 6

Hover the mouse pointer over the Export icon and click Layout Template for Current site or All Sites.

The Export Layout Template dialog box appears.

Step 7

Click Export.

Note

 

  • We recommend that you export the layout template only in the analyze mode. Exporting layout templates in the upgrade and release upgrade modes may be inaccurate.

  • You can export the layout template for node of the type 4000 and 1000, but the exported layout template will contain only the layout of NCS 2000 nodes. To export the layout template for the node type NCS4K-1K-2K and NCS1K-2K, perform the following:

    • Right click the site name in the Layout panel, and click Export.

    • Click OK to export the layout template in text format.

  • The NCS 2000 layout template is in XML format.

Import Layout Template for NCS 2000 Network in to Cisco ONP Database

Use the following procedure to import a template for NCS 2000 Network into the Cisco ONP database:

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Choose Manage > Layout Templates.

Step 2

Click Add in the Manage Layout Template dialog box.

Step 3

Click Choose Files and select a template from your local system.

Step 4

Click Import.

The template is imported to the Cisco ONP database.

Download Layout Template for NCS 2000 Network

Use the following procedure to download a template from the Cisco ONP database:

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Choose Manage > Layout Templates.

Step 2

In the Manage Layout Template dialog box, choose the template that you want to download.

You can also choose multiple templates.

Step 3

Click Download.

Save the template into your local system.

Delete Layout Template for NCS 2000 Network

Use the following procedure to delete a NCS 2000 Network template from the Cisco ONP database:

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Choose Manage > Layout Templates.

Step 2

In the Manage Layout Template dialog box, choose the template that you want to download.

You can also choose multiple templates.

Step 3

Click Delete to delete the template from the Cisco ONP database.

Apply NCS 2000 Layout Template into a Site

Use this task to apply the NCS 2000 Layout template into a site. The site can be NCS4K-2K, NCS1K-2K-4K, or NCS1K-2K, but the template will be applied only to the NCS 2000 section of that site.

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Choose File > Open.

The Select Network To Open dialog box appears.

Step 2

Click the network where you want to apply the layout template into an NCS 2000 site.

The network opens.

Step 3

Choose Network > Entity Editor.

Step 4

In the Entity Editor window, expand Sites and choose the site.

Step 5

In the right pane, choose the required template from the Layout Template drop-down list.

Note

 

Make sure that the other properties under Layout section such as Chassis Type, Power Supply, Controller Card, Node Protection, Redundant Controller Card, and MF-Unit are

set to Auto. Otherwise the Layout Template drop-down list remains disabled.

Import NCS 1000 and NCS 4000 Layout Template into NCS1K-2K and NCS4K-1K-2K Sites

Use this task to import NCS 1000 and NCS 4000 layout templates that were exported, into 4K-2K and NCS4K-1K-2K Sites.

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Choose File > Open.

The Select Network To Open dialog box appears.

Step 2

Click the network that has the site to which you want to apply the layout template.

The network opens.

Step 3

Click the Layout tab.

Step 4

Add the required NCS 4000 and/or NCS 1000 chassis, cards, and pluggables to the required slot of the added chassis. See Edit the Layout Manually

Step 5

Click Edit to enter the edit mode.

Step 6

Right click the name of a site on which you want to import the layout template, and click Import.

Step 7

Choose the layout template that you want to import into the site and click OK

The layout template gets applied to the site.

Note

 

When you modify an exported template, ensure to rename the modified template before reapplying it to a site in the upgrade mode so that the changes in the template reflect in the layout view.

Layout Visualization

Table 29. Feature History

Feature Name

Release Information

Feature Description

Layout Visualization and Edit

Cisco ONP Release 4.1

 This feature allows you to view and adjust the position of NCS 4016 and NCS 1004 chassis and cards in the layout. This feature is supported only on 4K-1K-2K and 1K-2K aggregated nodes and not supported on stand-alone NCS 2000 node.

This feature allows you to visualize the layout of a network, designed using Cisco ONP. You can view the arrangement of racks, chassis inside the racks and cards inserted in the chassis. When you click a particular Rack or Chassis or Card in theLayout panel, the corresponding Rack or Chassis or Card gets highlighted in the Layout image. You can zoom in and zoom out the Layout image.

View Network Layout

The procedure to view the network layout is as follows:

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

From the File menu, click Open.

The Select Network To Open dialog box appears.

Step 2

Click the network to open from the list of available networks.

Step 3

Choose Network > Analyze.

Note

 

Network must be successfully analyzed to proceed further.

Step 4

Click the Layout tab.

Step 5

In the Layout panel on the left side, click the site.

Note

 

The OLA sites are highlighted in green color, ROADM sites in blue color and Aggregated nodes in purple color.

Passthrough sites are not listed under layout.

For NCS 1010 network, Aggregated nodes are not available.

Step 6

Click any rack under a site to visualize the rack view of the network under Layout tab.

Step 7

Click any chassis under a rack to visualize the chassis view of the network.

Note

 

When you click the Aggregated node under Layout panel, NCS 1004, NCS 2000 and NCS 4000 series chassis are placed in separate racks.

You can click the screenshot icon to take screenshot of all racks layout of the selected site.

Edit the Layout Manually

The Manual layout edit feature is used to adjust the position of NCS 4016 and NCS 1004 chassis and cards in the layout.

The procedure to edit the layout manually is as follows:

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Choose File > Open.

The Select Network To Open dialog box appears.

Step 2

Click the network to open from the list of available networks.

Choose the network where 4K-1K-2K and 1K-2K aggregated nodes are added. This feature is not supported on NCS 2000 node.

Step 3

Choose Network > Analyze.

Note

 

Network must be successfully analyzed to proceed further.

Step 4

Click the Layout tab.

Step 5

Click Edit to enter the Edit mode.

Step 6

Select the Chassis (4K-1K-2K and 1K-2K) or Card from a particular rack.

Step 7

Drag and drop the selected Chassis or Card from a particular rack to the empty slot in the same or different Chassis or Rack.

Step 8

To add pluggables to a particular card, perform the following steps:

Note

 

Make sure to add the required cards.

  1. Select the Rack.

    The cards available in the Rack are displayed.

  2. Select the card to which you want to add pluggables.

    The ports available in the card are displayed.

  3. Select the pluggable for each port.

    The following pluggables are displayed:

    Card

    Supported Pluggables

    NCS4K-4H-OPW-QC2

    • ONS-QSFP8-LR4=

    • QSFP-110G-SR4-S=

    • ONS-QSFP-4*10-MLR=

    NCS4K-4H-OPW-LO

    • ONS-QSFP8-LR4=

    • QSFP-100G-SR4-S=

    • ONS-QSFP-4*10-MLR=

    NCS1K4-1.2T-K9=

    • ONS-QSFP8-LR4=

    • QSFP-100G-SR4=

    • ONS-QSFP28-LR4-S=

    • QSFP-100G-CWDM4-S=

    • QSFP-100G-SM-SR=

  4. Click the Tick icon.

Step 9

Click Done to save the changes in the Layout.

View the Layout Details Using Tooltip

You can hover over the Racks or Chassis or cards in the Rack and view the details using Tooltip. Click See More Details to view the details of port no. type, pluggables and rates.

Copy the Configurations of a Particular Node to Another Node

The configuration can be copied from one node to another node only for the manual 4K-1K layout movement. It is not supported for NCS1010 layout movement.

The procedure to copy the configurations of a particular node to another node of a different site is as follows:

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Choose File > Open.

The Select Network To Open dialog box appears.

Step 2

Click the network to open from the list of available networks.

Step 3

Choose Network > Analyze.

Note

 

Network must be successfully analyzed to proceed further.

Step 4

Click the Layout tab.

Step 5

Select the Rack, Chassis, or Card of a particular site.

Step 6

Select the site to where you want to copy the configurations to, from the Copy To drop-down list.

Step 7

Click New Rack to add a new rack. The configuration gets copied to the new rack.

Step 8

Click Done to save the changes in the Layout.

Note

 

You can also cut, copy, and delete Racks, Chassis, and Cards in the Chassis from the Layout.

Export Port Usage of LNI Network

Table 30. Feature History

Feature Name

Release Information

Feature Description

Multi-Layer Connections Phase 1

Cisco ONP Release 4.1

This feature provides the connection trace of a service across various interfaces in a network. This feature allows you to export the following:

  • Consolidated port usage report based on network in addition to the internal port details which you can view by hovering the mouse pointer over the tooltip

  • Port usage report based on sites

  • Port usage report only for LNI imported networks

Use the following procedure to export the port usage details of an LNI network:

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Choose File > Open.

The Select Network To Open dialog box appears.

Step 2

Click the LNI network whose port usage you want to export.

The network opens.

Step 3

Choose Network > Analyze.

Note

 

Network must be successfully analyzed to proceed further.

Step 4

Click the Layout tab.

Step 5

Click the name of a site in the left side panel,for which you want to download the port usage.

Step 6

Mouse hover the Export icon and click Port Usage for Current site or All Sites.

The Export Port dialog box appears.

Step 7

Click Continue.

The port usage details are exported in the Excel sheet format.

Note

 

  • If you modify any services in the NCS 4000 node after upgrading the LNI network , the changes will not get updated in the port usage details.

  • The demand labels seen against the trunk ports of NCS4K-DWDM line card in the port mapping report are not logically related to the NCS 4000 trunk ports, but are related to NCS 1004 client ports.

Define multilayer connections for SSON network

Table 31. Feature History

Feature Name

Release Information

Feature Description
NCS4K-1K-2K Multilayer Connection Trace

Cisco ONP Release 4.2

You can define Multilayer Connections (MLC) such as cards and pluggables for NCS 4K-1K-2K and NCS 1K-2K aggregated nodes in an SSON network.

This new tab in the Layout page helps to view end-to-end MLC trace for OTN service starting from NCS4K IN until NCS2K Add/Drop for LNI network. Also, it helps to define new traces for the newly added service and maintain the network design and deployment.

Use this procedure to define the Multilayer Connections (MLC) such as cards and pluggables for 4K-1K-2K and 1K-2K aggregated nodes in an SSON network.

Before you begin

Log in to Cisco ONP web interface

Procedure

Step 1

Open a network:

  1. Choose File > Open.

  2. In the Select Network To Open dialog box, click a network in which you want to define the multilayer connections.

    Make sure that the network is in analyzed mode and 4K, 1K, and cards are defined in the network.

Step 2

Define the MLC:

  1. Click the Layout tab.

  2. In the left pane, click the MLC tab.

    Alternatively, you can navigate to the MLC page by clicking the Ellipsis icon available in the right side of the service name in the network tree and clicking View in MLC

    You can view a table describing the properties of the service, in the right pane. See MLC details.

  3. Click the service name to switch to the layout view.

    You will view the layout and the service details in the right pane.

  4. Select the rack, shelf, card, and ports from the drop-down lists for NCS4K In, NCS4K Out, NCS 1K In, and NCS 1K out, for both Source and Destination sites.

    The details of the NCS 2000 chassis are auto-populated.

    Note

     

    For LNI imported network all the details are auto-populated. If you add any new service, you can change the details of the new service as per your requirement.

  5. Click the Tick icon to save the changes you have done.

    You can click the refresh icon to delete the changes you made after saving.

    The updated details are included in the BOM.

Step 3

If you want to export the MLC details perform these steps:

  1. Click the Table icon to switch to the table view.

  2. Choose Export > MLC Tracesto export all the details available in the MLC table.

  3. Choose Export > LMP/TTI Connections to export the details of Link Management Protocol (LMP) connections which are the connections between NCS 1004 and NCS 2000 cards, and Trail Trace Identifier (TTI) connections which are the connections between NCS 4000 and NCS 1004 cards.

    All these connections get added to the BOM.

Step 4

If you want to filter the services displayed in the left pane, click the Filter icon and choose one of these options:

  • Source Site

  • Destination Site

  • Type of the traffic

  • Trace Origin

    • LNI: Imported through Import Live Network option

    • User Created: Created through Cisco ONP UI

  • Trace Status

    • Completed: User has defined all MLC details.

    • Partial: User has defined only partial MLC details.

    • Empty: User has not defined any MLC details.

Step 5

Click the three vertical dots and select the required options:

  • Enable Multi Select: You can select up to the card level for different OTN.

  • Expand All: Expands the services tree.

  • Collapse All: Collapses the expanded services tree.

  • Show Trace Status: Shows the trace status icon next to the service name.

Step 6

Click the three horizontal dots across the service trace and select the required options:

  • Delete Trace: Deletes the respective trace.

  • Locate in Map: Shows the service in the map view.

Note

 

You can enable the same port number on the primary and secondary NCS4K IN nodes for Client 1+1 and other protection scheme.

MLC details

This table describes various fields available in the MLC tab.

Table 32. MLC details

Properties

Description

Name

Name of the service

Group Name

Name of the group to which the service belongs to

Type

Traffic type

Src Site

Source site

Src NCS4K In

Details of Rack/Slot/Card/Port in the input side of the NCS 4000 chassis in the source site

Src NCS4K Out

Details of Rack/Slot/Card/Port in the output side of the NCS 4000 chassis in the source site

Src NCS1K In

Details of Rack/Slot/Card/Port in the output side of the NCS 1004 chassis in the source site

Src NCS1K Out

Details of Rack/Slot/Card/Port in the output side of the NCS 1004 chassis in the source site

Src NCS2K AddDrop

Add/Drop multiplexer and demultiplexer connected to the NCS 2000 chassis in the source site

Src NCS2K MPO

Media channel between the source and destination sites

Dst NCS4K In

Details of Rack/Slot/Card/Port in the input side of the NCS 4000 chassis in the destination site

Dst NCS4K Out

Details of Rack/Slot/Card/Port in the output side of the NCS 4000 chassis in the destination site

Dst NCS1K In

Details of Rack/Slot/Card/Port in the input side of the NCS 1004 chassis in the destination site

Dst NCS1K Out

Details of Rack/Slot/Card/Port in the output side of the NCS 1004 chassis in the destination site

Dst NCS2K AddDrop

Add/drop multiplexer and demultiplexer that is connected to the NCS 2000 chassis in the destination site

Dst NCS2K MPO

MPO cable connecting the NCS 2000 chassis in the destination site

Media Channel

Media channel between the source and destination sited

Notes

More notes, if any

Trace Origin

Indicates whether the service connections are user-created or imported through LNI.

Spectrum Utilization and Path Finder

Table 33. Feature History

Feature Name

Release Information

Feature Description

Spectrum Utilization and Path Finder

 Cisco ONP Release 24.3.1

The Spectrum Utilization and Path Finder introduces the Minimal Map, a streamlined network visualization tool focusing on essential data points like Sites and Fibers, enhancing usability and performance. General Settings now allow individual customization, including default map views and spectrum utilization colors. The Path Finder/Selector enables interactive path selection with options for manual and custom path finding for multiple routing options. The Spectrum Utilization provides a comprehensive visualization of used spectrum, while the Spectrum Finder helps locate and apply available spectrum across fibers, offering dual-view capabilities and multiple selection methods. These enhancements collectively improve network management, planning, and resource optimization.

Spectrum Utilization and Path Finder introduces

  • Minimal Map: streamlines network visualization tool focusing Sites and Fibers.

  • Path Finder/Selector: enables interactive path selection with options for manual and custom path finding.

  • Spectrum Utilization: provides a comprehensive visualization of used spectrum.

  • Spectrum Finder: helps to locate available spectrum across fibers and apply them on a Circuit or Media Channel.

Find a Custom Path

The Custom Path Finder is accessible exclusively through the Minimal Map. When you choose the custom path finder, the detailed map automatically switches to the Minimal Map.

Limitations

  • Applies to only Circuits (NCS1010/ NCS1001), Waves (NCS2000 NON-SSON), media channel (NCS2000 SSON).

The procedure to customize a fiber path on the map is as follows:

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

In the network tree, select the section of the media channel/circuit that you want to add a new path.

Step 2

Click the Ellipses icon and select Custom Path Finder.

The Custom Path Finder for the selected section opens.

Step 3

In the Visualization area, choose the required map view.

Map View

Result

Complete Map

Shows a complete network map of the selected path with other sites.

Sub Map

Shows only maps with chosen sites and fiber.

Step 4

In the Options area, choose the required parameters to calculate the Path Finder.

Option Description

Minimum Hop

Performs all the routing based on minimum number of hop counts, irrespective of length of fibers

Minimum Length

Performs all the routing based on fiber minimum length, irrespective of hop count

Distinct Fiber Set

Provides Distinct set of fibers. This makes sure the same fiber is not repeated in other paths

Number of Path Count

Calculates the number of paths based on the provided number

Step 5

Click Calculate.

The list of paths calculated based on the chosen parameters displays.

The calculated paths table contains the path parameters.

Table 34. Path Parameters

Parameter

Description

S.No

Displays the serial number

Path

Displays fiber path direction based on chosen Options parameters

Funnel icon

Filters the path based on fiber labels

Hops

Provides the hop count

Total Length

Provides the total length of the fiber path

Step 6

Click Export to export the chosen fiber path.

Step 7

In the Selected Service and Path area, check the service and path information and click Apply Path to apply the selected path.

Select Path Manually

The Manual Path Selector is accessible exclusively through the Minimal Map. When you choose the manual path selection, the detailed map automatically switches to the Minimal Map.

Limitations

  • Available in Design and Upgrade modes where circuits path can be updated.

  • Applies to only Circuits (NCS1010/ NCS1001), Waves (NCS2000 NON-SSON), media channel (NCS2000 SSON).

  • Applies to regen circuits/waves/media channel.

  • Additional options are applicable for Section under Network Tree.

The procedure to select a path manually on the map is as follows:

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

In the network tree, select the section of the media channel that you want to add a new path.

Step 2

Click the Ellipses icon and select Manual Path Selection.

Step 3

In the Search field, enter the site or fiber to focus on it.

Step 4

Select the required the fibers to create a path.

The selected fibers appear on the Operation Modes pop-up pane under Fibers area.

Step 5

Click Apply.

View Spectrum Utilization and Spectrum Finder

The Spectrum Finder is accessible exclusively through the Minimal Map. When you choose the spectrum finder, the detailed map automatically switches to the Minimal Map.

We recommend that you use the Spectrum Finder for the network in Design/Upgrade/Release Upgrade Mode and view the Spectrum Utilization in Analyze Mode.

The procedure to view the spectrum utilization and find a spectrum to apply for a service is as follows:

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

In the network tree, select the section of the media channel that you want to learn the spectrum utilization per fiber.

Step 2

Click the Ellipses icon and select Spectrum Finder.

The Spectrum Finder for the selected section opens.

Step 3

In the Selected Fibers area, click +Add Fiber and choose the required fibers from the drop-down list.

Step 4

In the Visualization area, choose the required map view.

Map View

Result

Complete Map

Shows a complete network map of the selected path with other sites.

Sub Map

Shows only maps with chosen sites and fiber.

Step 5

In the Spectrum Finder area, modify the parameters as required..

Option Description

Tabular View

Similar to Spectrum Utilization View

Detailed View

Displays multiple fibers in a vertical orientation (Y-Axis) and the spectrum on the horizontal axis (X-Axis).

Spectrum Selection

Enable Spectrum Selection to modify the subsequent parameters.

Spacing

Enter the bandwidth (GHz) that is required for the network circuit.

Distinct Fiber Set

Provides Distinct set of fibers. This makes sure the same fiber is not repeated in other paths

Number of Path Count

Calculates the number of paths based on the number provided

Allow Overlap

Allows you to select overlapping wavelengths with selected fibers, when enabled.

Zoom

Zooms in and out of detailed view to granular view. Click Default reset zoom.

View Labels

Displays the labels. Enable to view the labels. You can also view the labels of existing occupied circuits.

Hovered Spectrum

Shows the start, end, and central wavelengths (THz) of the hovered spectrum when moving across the view

Selected Spectrum

Shows the start, end, and central wavelengths (THz) of the selected spectrum when selecting across the view.

C-Band

Toggle to view the C-band spectrum usage.

L-Band

Toggle to view the L-band spectrum usage.

Fiber Utilization Graph

Displays the frequency utilzed in a fiber for each span in continuation in a vertical axis. Each square block is 3.125GHz. The frequency range starts from the left and continues towards the right, increasing 3.125GHz per block for both C- and L-band.

For C-band, the first row has the starting frequency as 191.325 THz. A single row contains 53 blocks, totalling 0.165625 THz ( 53*3.125 GHz). The starting frequency of subsequent rows increment at 0.165625 GHz.

Color tone of the blocks varies in the Fiber Utilization Graph

Dark red

Indicates overlap of same spectrum across multiple waves.

Light red

Indicates less spectrum usage.

Step 6

In the Apply Properties to Existing Service area, check the service parameters and click Apply Wavelength and Apply Path.

Click Apply Wavelength and Apply Path to revert the changes.

Step 7

Select Apply to Service.

Regenerate BoM Automatically

You can view the new Chassis or Card added to the existing layout under the BOM tab. You can also view the regenerated BoM after manual editing of the layout.

Add new Pluggables, Alarm Cables and 100G Client Bandwidth Licenses to BoM

You can add new pluggables, alarm cables and 100G bandwidth licenses of NCS 1004 and NCS 4000 platforms to the existing BoM.

The procedure to add new pluggables, alarm cables and 100G client bandwidth licenses to the existing BoM is as follows.

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Choose File > Open.

The Select Network To Open dialog box appears.

Step 2

Click the network to open from the list of available networks.

Step 3

Choose Network > Analyze.

Note

 

Network must be successfully analyzed to proceed further.

Step 4

Click the BOM tab.

Step 5

Click Add.

The New window opens.

Step 6

Enter the Cisco part number of the pluggable or alarm cable or 100G bandwidth license in the Cisco Part Number field.

Step 7

Choose the Quantity of pluggables or alarm cables or 100G bandwidth licenses to be added.

Step 8

Click Add.

The new pluggables or alarm cables or 100G bandwidth licenses are added to the BoM list.

Export IPC Report

You can export the connections of a current site or all sites to an Excel sheet using the following procedure:

Before you begin

Log in to Cisco ONP web interface

Procedure

Step 1

From the File menu, click Open.

The Select Network To Open dialog box appears.

Step 2

Click the network to open from the list of available networks.

Step 3

Choose Network > Analyze.

Note

 

The network must be successfully analyzed to proceed further.

Step 4

Click the Layout > IPC tabs.

You can view the patches that are listed in the left pane. Click each patch to view the details such as position, card, and port of the source and destination sites.

The patches that you click are highlighted in the rack.

Step 5

Hover over the Export icon, and click Current site or All Sites option.

The Export IPC dialog box appears.

Step 6

Click Continue to export the connections of the current site or all sites.

The cable-type and Cable ID are included in the report only for the NCS 1010 network.

Edit the Layout Manually for NCS 1010 Networks

Table 35. Feature History

Feature Name

Release Information

Feature Description

Layout Edit Support for NCS 1010 Networks

Cisco ONP Release 5.0

Cisco has introduced NCS 1010 as a new optical line system to meet the growing optical network needs. Using Cisco ONP you can visualize and edit layouts for NCS 1010 chassis and patch panels.

The Manual layout edit feature is used to adjust the position of the NCS 1010 chassis and patch panels in the layout.

The procedure to edit the layout manually is as follows:

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Choose File > Open.

The Select Network To Open dialog box appears.

Note

 
You can also create a new NCS 1010 network. For more information, see Manually design a network using Cisco ONP.

Step 2

Click the network to open from the list of available networks.

Choose the NCS 1010 network.

Step 3

Choose Network > Analyze.

Note

 

The network must be successfully analyzed to proceed further.

Step 4

Click the Layout tab.

Step 5

Click Edit to enter the Edit mode.

Step 6

In the left panel, click a site.

Step 7

Select a unit (NCS 1010 chassis or patch panel) using one of the following methods:

  • In the left panel, expand the rack under a site and choose a unit.

  • Or, in the Rack view, click a chassis or patch panel.

Step 8

To adjust the position of the selected units, use one of the following methods:

Note

 

If necessary, click the +New Rack button to create more racks.

  • In the Rack view, drag and drop the selected chassis or panel from a particular rack to the empty slot in the same or different rack.

  • Swap units in the Rack view:

    • Click a transponder or NCS1K14-CCMD-16 card.

      The Swap with button appears.

    • Click Swap with and select a slot to swap from the drop-down list.

    Note

     

    The Swap with button appears only for NCS 1014 and NCS 1020 chassis.

  • Cut and Paste unit in the left panel:

    • Click Cut above the Rack view.

    • Right-click on an empty slot in the same or different rack and click Paste.

      Cisco ONP disables the Paste option if you try to paste the unit in the prohibited slots.

      Cisco ONP disables the Cut option if an existing cut unit is not pasted.

  • Cut and Paste unit in the Rack view:

    • Right-click the selected chassis or panel and click Cut.

    • Right-click on an empty slot in the same or different rack and click Paste.

      Cisco ONP disables the Paste option if you try to paste the unit in the prohibited slots.

      Cisco ONP disables the Cut option if an existing cut unit is not pasted.

  • Move the unit in the left panel:

    • Go to Move to > Site-X > Rack-X above the Rack view to move the chassis to the same or different rack. Or go to Move to > Site-X > + New rack above the Rack view to move the chassis to a new rack.

  • Move the unit in the Rack view:

    • Right-click the selected chassis or panel and go to Move to > Site-X > Rack-X to move the chassis to the same or different rack. Or go to Move to > Site-X > + New rack to move the chassis to a new rack.

Note

 

The Move to option moves the unit automatically to the immediate empty slot. The Cut and Paste option moves the unit to the selected empty slot.

Step 9

Click Done to save the changes in the Layout.

A warning message appears when empty racks are present in the layout.

Step 10

Click OK to remove the empty racks.

View Internal Node Connections of NCS 1010 Network

Table 36. Feature History

Feature Name

Release Information

Feature Description

View Internal Node Connections of NCS 1010 Network

Cisco ONP Release 5.0

The Node diagram tab displays a functional view that includes precise connections and port labeling of each component such as OLT or ILA, NCS1K-BRK-8/16/24, AAWG-32-O, and AAWG-32-E, for each site in an analyzed NCS 1010 network.

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

ChooseFileOpen.

The Select Network To Open dialog box appears.

Step 2

Click the analyzed NCS 1010 network.

The network opens.

Step 3

Choose Network > Analyze.

Note

 

Network must be successfully analyzed to proceed further.

Step 4

Click the Layout > Node Diagram tabs.

Step 5

Click each site in the left panel and select a side to view the functional view of the site.

The functional view includes both the combination of physical and logical connections such as:

  • Degree interconnections between NCS1010 (OLT or ILA) and NCS1K-BRK-8

  • Add/drop connections between NCS1010 and colorless add/drop units (NCS1K-BRK-8, NCS1K-BRK-16, or NCS1K-BRK-24) and colored add/drop units (AAWG-32-O or AAWG-32-E)

Step 6

Hover over the cable to view the details such as name of the ports that are connected and the cable ID.

Designing networks with SVO card

A SVO card is a network hardware component that

  • provides licenses based on functionality for features such as alarm correlation, performance monitoring, connection verification, and OTDR,

  • serves as the primary card for all networks starting from Release 12.1.0, and

  • can be deployed in both ROADM and TRAFFIC nodes as part of network designs.

Features of the SVO card:

The SVO card offers these key features and configuration options:

  • The SVO card occupies two slots.

  • It serves as the primary card for all networks starting from Release 12.1.0.

  • For high availability, a node can be equipped with two SVO cards, but they cannot be in the same chassis.

  • Two 10G SFP+ pluggables can be used to connect two SVO cards within a node.

  • You can connect a Cisco ASR 920 switch to the SVO cards during network design.

  • The SVO can function as either a card or a UCS based solution.

SVO licenses

  • SVO cards require either a Base License or an SVO Full License which covers High Availability, Connection Verification, and Flex Spectrum. If the SVO Full License is not selected, the SVO Base License and High Availability are enabled by default.

  • Types of SVO licenses include:

    • Cisco NMS: Features High Availability, Connection Verification, Flex Spectrum, and OTDR.

    • Third-Party NMS: Includes North Bound Interface (NBI), Alarm Correlation, Performance Monitoring, and Circuit Provisioning.

Chassis licensing:

  • Every chassis added to the network must be licensed from Release 12.1.0 onwards. For networks upgraded to Cisco ONP Release 4.0 or higher, a new chassis license is required after analysis.

  • Chassis licenses come in variants such as 1-chassis, 5-chassis, 10-chassis, 20-chassis, 50-chassis, and others, chosen based on cost optimization.

  • A license is required for each chassis added to the network after the first chassis.

  • Chassis License Flush Out allows you to replace existing chassis licenses with new ones. The current license remains active if the site is unlocked. However, you can use flush out only during network upgrade mode.

  • You can continue using existing licenses with changes to the chassis unless you opt for the Chassis License Flush Out option.

SVO associations

A ROADM node equipped with an SVO card can manage OLA and DGE nodes that do not have an SVO card by associating them with itself. You can manually associate the OLA and DGE nodes with the ROADM node.

Associate OLA or DGE sites with SVO cards

Use this procedure to associate OLAsites with the SVO cards:

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

In the network tree panel, click the Ellipsis icon available next to any ROADM or Traffic site with SVO card.

Step 2

Click Edit SVO Associations.

Step 3

Select the OLA sites on the map to toggle the SVO connections. To confirm your selection, click Done at the top-right corner.

You can open widgets in the map and select the top section to view the association.

Note

 

You can also right-click any ROADM or Traffic site from the map and click Edit SVO Associations. For the DGE sites, the Edit SVO Associations option is not displayed.

During network analysis, the tool automatically associates the sites you do not associate with the SVO card.

Export device NETCONF XML file

Use this procedure to export the NETCONF XML files for all network sites or the entire network from the Cisco ONP GUI. This supports device configuration, automation, and network provisioning using the latest supported parameters.

The network must be in Analyze mode.

Before you begin

Log in to Cisco ONP web interface.
Table 37. Feature History

Feature Name

Release Information

Feature Description

New Parameters Included in NCS 1010 NETCONF XML file

Cisco ONP Release 24.3.1

The NETCONF XML file exported from the NCS 1010 network design now includes these new parameters to support seamless Day-0 provisioning and the setup of a new node added to the network.

  • Optical cross-connects

  • Gain range margin

  • Tone Rates

  • Raman tuning configurations

  • Slot reserve

  • Dmux WSS attenuation

  • Unused CCMD-16 ports shutdown

  • Span baseline-deviation

  • OTDR Thresholds

  • APC Span-loss correction threshold
Table 38. Feature History

Feature Name

Release Information

Feature Description

Export NETCONF File from NCS 1010 network

Cisco ONP Release 5.0

You can export the NETCONF XML files for all the NCS 1010 nodes, and upload them to the NCS 1010 nodes through the YANG suite. This enables automatic bring up of the NCS 1010 nodes using the NETCONF data.

Procedure

Step 1

In the network tree panel, click the three dots.

A pop-up list appears.

Step 2

In the list, click Generate Device NetConf XML.

The Export window appears displaying the network name.

Step 3

Click Export.

The message "Success. Device NetConf exported successfully" appears.

You can download a zip file that contains the NETCONF XML files for individual sites.

Note

 

You can choose the destination folder for saving the downloaded NETCONF XML files of individual sites.

This feature has limited scope in this release.

Note

 

For C+L Network, the partner band configurations are not included in the Cisco ONP-generated XML file. Manually configure the partner bands on the devices while bringing up the NCS 1010 C+L network.

From Release 24.3.1, these new parameters are available in the NETCONF file exported from the NCS 1010 network design:

  • OSC TX Power

  • Optical Cross Connect

  • OTS tone rate

  • OMS tone rate

  • OTS tone pattern expected

  • OTS tone detect OOB

  • OTS tone pattern

  • OTS tone frequency

  • Raman pump configurations

  • Line port attenuation

  • Raman dual safety

These parameters are available only if you enable the Enable Special Settings check box under the Network properties.

  • Raman turnup

  • OTS ports shutdown

  • OTDR autoscan

  • Gain range margin

  • OTDR excess attenuation threshold

  • OTDR end of fiber threshold

  • Slot reserve

  • Dmux WSS attenuation

  • Unused CCMD-16 ports shutdown

  • Span baseline-deviation

  • OTDR Thresholds

  • APC Span-loss correction threshold

Upload NETCONF XML files on SVO web interface

Use this procedure to upload NETCONF XML files on the SVO web interface to configure and provision network nodes using exported configuration data.

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

In the browser URL field, enter the IP address of the SVO line card.

The login page appears.

Step 2

Enter the username and password.

Step 3

Click Login.

Step 4

Click the hamburger icon and select Node Configuration.

Step 5

Click the Node Setup tab.

Step 6

Click Select files .

Step 7

Browse to the NETCONF XML files exported from the Cisco ONP GUI and upload them.

If the passive unit ID in the NETCONF file exceeds the range 1 to 126, SVO displays an error message. Validate the XML file and import it again.

Note

 
If the FEC mode provisioned in the 200G-CK-C line card does not match with the value in the NETCONF XML file, SVO displays an error message. Remove the provisioned FEC settings for this card and reimport the XML file.

Export device NETCONF XML Files for individual sites

Use this procedure to export device NETCONF XML files for individual sites from the Cisco ONP GUI.

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Click the Ellipsis icon next to the site.

Step 2

In the list, click Generate Device NetConf XML.

Export window appears with network name.

Step 3

Click Export.

The message, "Success. Device NetConf exported successfully" appears.

You can download a zip file containing device NETCONF XML files of individual sites.

Upload NETCONF files to NCS 1010 device

Use this procedure to upload the NETCONF files that you downloaded from Cisco ONP, into the NCS 1010 device using a NETCONF client.

Before you begin

Log in to Cisco ONP web interface.

Procedure

Step 1

Log in to the YANG suite that has access to the NCS 1010 device.

Step 2

Connect to the NCS 1010 device.

Step 3

Copy the NETCONF XML file content that is downloaded from Cisco ONP, and paste it into the Protocol NETCONF Run RPC block.

Step 4

Append this commit code at the end of the NETCONF XML file content.

<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="102">
<commit/>
</rpc>

Export Cisco Optical Site Manager NETCONF XML file

Use this procedure to export the Cisco Optical Site Manager NETCONF XML files for all the individual sites in a network, from the Cisco ONP GUI.

This feature has limited scope in this release.

Table 39. Feature History

Feature Name

Release Information

Feature Description

Export Cisco Optical Site Manager (COSM) NETCONF File from NCS 1010 network

Cisco ONP Release 5.2

The new Generate COSM NetConf XML option allows you to export from the Cisco Optical Network Planner, the Cisco Optical Site Manager NETCONF XML files for all the NCS 1010 nodes. You can then upload these files to the NCS 1010 nodes through the Cisco Optical Site Manager, enabling automatic bring-up of the NCS 1010 nodes.

The network must be in Analyze mode.

Procedure

Step 1

In the network tree panel, click the three dots.

A pop-up list appears.

Step 2

In the list, click Generate COSM NetConf XML.

Export window appears with network name.

Step 3

Click Export.

The message "Success. COSM NetConf exported successfully" appears.

Download the zip file that contains the COSM NETCONF XML files of individual sites.

Note

 

You can choose the destination folder to save the downloaded Cisco Optical Site Manager NETCONF XML files of individual sites.

Note

 

  • For the ROADM OLT node, the device name is generated in the Site Name-Side Name format.

  • For the OLA node, the device name is the same as the Site Name.

Ensure that you align the device name in COSM to match the specified format.

If the Site Name contains any special character, the XML file replaces the special character with its ASCII value in the COSM XML device name, providing a seamless experience with the COSM data backup workflow.

Note

 

L-Band Configuration is not certified in Cisco Optical Site Manager for Release 7.11.1. A future release will be considered for the L-Band configuration.

Upload Cisco Optical Site Manager NETCONF XML to NCS 1010 Device via Cisco Optical Site Manager Web Interface

Use this procedure to upload the Cisco Optical Site Manager NETCONF files that you downloaded from Cisco ONP into the NCS 1010 device using the Cisco Optical Site Manager web interface.

Before you begin

Log in to Cisco ONP web interface

Procedure

Step 1

Log in to the Cisco Optical Site Manager UI that has access to the NCS 1010 device.

Step 2

Verify the device name, UID, and card layout position such as Rack ID and RU position with the CONP XML.

Make sure the device name and UID in Cisco Optical Site Manager match those in the CONP XML. If they do not match, delete the device and add it again using the name and UID from the CONP XML.

Step 3

Go to Optical Setup, browse the Cisco ONP-generated XML without optical cross connect (OXC) for that device, and load the file.

Step 4

Click the Select files... button.

The file explorer window appears.

  1. Select the Cisco ONP-generated Cisco Optical Site Manager XML file from your local device.

  2. Click Open, then click Yes in the confirmation message.

  3. Click Upload.

    The COSM XML successfully uploaded message appears.

Step 5

Go to Optical Configuration > ANS parameter and verify whether the respective configurations are complete.

Step 6

After you load the Cisco Optical Site Manager XML file without optical cross connect, load the file with optical cross connect.

Step 7

After adding the Cisco Optical Site Manager XML file with optical cross connect, go to the Optical Cross Connections tab and verify whether the respective configurations are complete.

Export NCS 1010 network planning data for Cisco Optical Network Controller

Use this procedure to export NCS 1010 network-planning data from Cisco ONP as a JSON file. You can upload the exported JSON file to Cisco Optical Network Controller to enable efficient bulk configuration and management of NCS 1010 devices.

Table 40. Feature History

Feature Name

Release Information

Feature Description

Export NCS 1010 Network Planning Data for Cisco Optical Network Controller (Cisco ONC)

Cisco ONP Release 5.0

You can export the planning data of NCS 1010 network, in the form of a JSON file. This JSON file can be uploaded into Cisco ONC to configure the managed devices in bulk.

You can export the planning data of NCS 1010 network only for releases 7.7.1 and 7.9.1.

Procedure

Step 1

In the network tree panel, click the Ellipsis icon next to the network name, and select Generate CONC JSON .

Step 2

In the Export File dialog box, enter the name of the JSON file, and click Export to download the JSON file to your local system.

Upload planning data into Cisco ONC

Use this procedure to upload the network planning data (JSON file) downloaded from Cisco ONP to efficiently transfer network design and configuration information into Cisco ONC.

Procedure

Step 1

Log in to Cisco ONC.

Step 2

Hover over the Import icon in the left panel and click Planning Data Import.

Step 3

Click Import.

Step 4

Browse and select the JSON file you downloaded from Cisco ONP.

You can use the planning data to configure the devices managed by Cisco ONC.