cygnet_adrs_usermanual_v1_4.pdf

v User Manual for CygNet ADRS/NMSWorks/IBM/Bharti Airtel/v.1.4

Confidential and Proprietary

User Manual for CygNet ADRS

PREPARED FOR

Bharti Airtel Limited

Version 1.4

PREPARED BY

NMSWorks Software Pvt. Ltd.



NMSWorks Project User Manual

Statement of Confidentiality

This document contains information confidential to NMSWorks and the Buyer, which are provided for the sole purpose of permitting the Buyer to use CygNet OTNMS. Transmission or translation in any form or by any method, electronic, manual, mechanical, optical or otherwise or unauthorized circulation is strictly prohibited. This document shall be treated at all times as a confidential and proprietary document for internal use only. If you are not authorized to have access to this document or have received it by mistake, or by deliberation through unauthorized sources, please return it immediately or inform us at the address given below to arrange for its collection: NMSWorks Software Private Limited #C3, 6th floor IIT Madras Research Park Taramani Chennai- 600113



Revision History

Sl No Version Date Status Author Reason for Change

1

1.2

First

Release

Baskaran N

&

Manikandan M

Initial version

2

1.3

Revised

Baskaran N

&

Abhishek Goel

Updated Reconciliation

&

Added Workflow chapter

3

1.4

Revised

Baskaran N

&

Abhishek Goel

Added report chapter &

modified suggested changes

Approvals

Sl No Name Role

1 A. Manickavasagam Operations Head



Table of Contents

1. Introduction .................................................................................................................... 7 1.1 Background ................................................................................................................ 7 1.2 Purpose of Document and Intended Audience ......................................................... 7 1.3 Terminology Used In This Document ........................................................................ 7 1.4 Abbreviation Used in this Document ........................................................................ 8 1.5 An Overview of this Document .................................................................................. 8

2. A Brief System Overview .............................................................................................. 10 2.1 CygNet OTNMS ........................................................................................................ 10 2.2 CygNet OTNMS Architecture ................................................................................... 10 2.3 Security .................................................................................................................... 11

3. Getting Started .............................................................................................................. 14 3.1.1 Starting the CygNet Client ............................................................ 14 3.1.2 Standard Toolbar......................................................................... 15

4. Network Discovery ........................................................................................................ 18 4.1 Introduction .............................................................................................................. 18 4.2 Adding a Transport EMS.......................................................................................... 18 4.3 Discovery Profile Manager. ..................................................................................... 20

4.3.1 Add a Profile ................................................................................... 22 4.3.2 Modify Profile .................................................................................. 24 4.3.3 View Profile .................................................................................... 26 4.3.4 Delete Profile .................................................................................. 27

4.4 Discovery Process Manager .................................................................................... 28 4.4.1 Profile activation .............................................................................. 29 4.4.2 Starting a profile .............................................................................. 30 4.4.3 Suspending a profile ......................................................................... 31 4.4.4 Resuming a profile............................................................................ 32 4.4.5 Stopping a profile ............................................................................. 33 4.4.6 Viewing process history ...................................................................... 34

4.5 On Demand Discovery ............................................................................................. 35 4.5.1 Guidelines for doing On-demand discovery ............................................... 36

4.5.2 Viewing on Demand Discovery process history .................................................. 37 4.6 Deleting Network Elements ..................................................................................... 38

4.6.1 Delete Symbol ................................................................................ 38 4.7 EMS, NE and Link Properties .................................................................................. 40

4.7.1 EMS Property.................................................................................. 40 4.7.2 ME Property pages ........................................................................... 43 4.7.3 Link Property .................................................................................. 58

4.8 Import and Export .................................................................................................... 65 4.8.1 Multiple NE Export ............................................................................ 65

4.9 Circuit Discovery ..................................................................................................... 68 4.9.1 Discover Circuit from Database ............................................................. 68 4.9.2 Discover All Circuits........................................................................... 70

4.10 Ring Discovery ....................................................................................................... 71 4.10.1 Topology Manager .......................................................................... 71 4.10.1.1 Create Topology .......................................................................... 72 4.10.1.1.1 Create topology using Using Design design type ................................ 72 4.10.1.1.2 Create topology using Ring Name Design design type ......................... 81 4.10.1.1.3 View Topology .......................................................................... 82 4.10.1.1.4 Approach used .......................................................................... 89

4.11 General ................................................................................................................... 91 4.11.1 Custom Map Creation ...................................................................... 91 4.11.2 Search Elements ............................................................................ 95 4.11.3 Topological Link Addition ................................................................... 95 4.11.4 Topological Link Deletion ................................................................... 97 4.11.5 Addition of VNE/Virtual Network .......................................................... 98 4.11.5.1 VNE / Virtual Network addition ......................................................... 98 4.11.5.2 Inventory Addition .......................................................................100

User Manual for CygNet ADRS/NMSWorks/IBM/Bharti Airtel/v.1.2


4.11.5.3 Addition of Cross Connection...........................................................102 4.12 Inventory Search .................................................................................................. 105 4.13 Network Metrics ................................................................................................... 107

5. Reconciliation .............................................................................................................. 110 6. Workflow ...................................................................................................................... 115

6.1 Introduction ............................................................................................................ 115 6.2. Update Network Element discrepancy in M6 NRMS ............................................ 117

6.2.1 Update Network Element Only In Network discrepancy in M6 NRMS..............117 6.2.2 Update Network Element Changed discrepancy in M6 NRMS ......................121 6.2.3 Update Network Element Only in M6 discrepancy in M6 NRMS ....................125

6.3 Update Card discrepancy in M6 NRMS ................................................................. 127 6.3.1 Update Card Only In Network discrepancy in M6 NRMS .............................127 6.3.2 Update Card Changed discrepancy in M6 NRMS ......................................130 6.3.3 Update Card Only In M6 discrepancy in M6 NRMS ...................................133

6.4 Update Link discrepancy in M6 NRMS .................................................................. 136 6.5.1 Update Link Only In Network discrepancy in M6 NRMS..............................136 6.5.2 Update Link Changed discrepancy in M6 NRMS ......................................138 6.5.3 Update Link Only In M6 discrepancy in M6 NRMS ....................................141

6.5 Update Circuit discrepancy in M6 NRMS .............................................................. 144 6.5.1 Update Circuit Changed discrepancy in M6 NRMS ....................................144 6.5.1.1 Update Circuit Valid resource discrepancy in M6 NRMS ...........................144 6.5.1.2 Update Circuit Link Channel Rate Mismatch in M6 NRMS .........................148 6.5.1.3 Update bulk circuits in M6 NRMS........................................................151

6.6 Ignore Task............................................................................................................. 156 7. Reports ........................................................................................................................ 159

7.1 Introduction ............................................................................................................ 159 7.2 OnDemand Reports ...........................................................................159 7.2.1 Generate OnDemand Reports .............................................................160 7. 2.2 Progress OnDemand Report ..............................................................167 7. 2.3 Download OnDemand Report .............................................................168


Confidential and Proprietary - 6 -

Chapter 1

Introduction



1. Introduction

1.1 Background

CygNet OTNMS developed by NMSWorks enables discovery & reconciliation of the Transport network at Bharti Airtel Limited. The transport network at Bharti Airtel consists of network devices running on SDH, EoS, MOT/PTN, ASON, OTN and WDM technology.

1.2 Purpose of Document and Intended Audience

As network administrators are primarily responsible for managing enterprise and service provider infrastructure, this User Manual helps you in configuring CygNet OTNMS to suit your

organizational requirements. The administrative tasks are eased by CygNet OTNMS by providing easy-to-use graphical user interfaces which enables you to perform all administrative tasks quickly. This user manual provides the basic understanding about functioning of the CygNet OTNMS and procedures to perform the basic tasks and work flows using it. Users can use this document for reference.

1.3 Terminology Used In This Document

Customer refers to Bharti Airtel Limited

System refers to the software system that is to be developed and deployed based on this

document to cater to the needs of this project. The terminologies CygNet OTNMS and System are interchangeably used to refer the same External IMS refers to the Inventory management system that is deployed in the Customer

environment which is to be reconciled. In this case the External IMS refers to M6 NRMS Equipment refers to the card inserted in the slots of the NE

Un-Managed links refers to the connectivity that are not managed by any of underlying

NMS/EMS such as links between NEs managed by different management systems Circuit refers to the customer circuits, internal VC4 pipes, Ethernet services, MoT trails, lambda

trails, ODU, OMS trails Reconcilable Object refers to any that is considered for reconciliation with M6 NRMS Ex:

Network Element, Cards, Links, and Circuits Link refers to the connectivity between the two neighboring network elements Intra NMS/EMS Links refers to links between NEs that are managed by a same management

system (NMS/EMS) Inter NMS/EMS Links refers to links between NEs that are managed by a different management

system (NMS/EMS)



Discovery refers to the module or process responsible for building the network inventory by

fetching the resource, topology and circuit related from the underlying NMS/EMS Reconciliation refers to the module or process, which is part of the system to be deployed,

responsible for reconciling the network discovered inventory with the inventory of M6 NRMS for identified reconcilable objects

1.4 Abbreviation Used in this Document

Acronym Expansion

ADRS Activation Discovery Reconciliation System

CTP Connection Termination Point

DWDM Dense Wavelength Division Multiplexing

EMS Element Management System

GUI Graphical User Interface

HO Higher Order(SDH Container)

IMS Inventory Management System

ME Managed Element

MLSN Multilayer Sub-Network

MSP Multiplex Section Protection

MSSP Multiplex Section Shared Protection

NBI North Bound Interface

NE Network Element

NMS Network Management System

OSS Operations Support System

PDH Plesiochronous Digital Hierarchy

PGP Protection Group

PTP Physical Termination Point

SDH Synchronous Digital Hierarchy

SNC Sub-Network Connection

STM Synchronous Transport Module

TL Topological Link

VC Virtual Container

VNE Virtual Network Element

WDM Wavelength Division Multiplexing

1.5 An Overview of this Document

Chapter 1 Introduction Chapter 2 A Brief System Overview Chapter 3 Getting started Chapter 4 Network Discovery Chapter 5 Reconciliation Chapter 6 Workflow Chapter 7 Reports



Chapter 2

Overview of the System



2. A Brief System Overview

2.1 CygNet OTNMS

CygNet OTNMS caters to the transport network of Bharti Airtel Limited. This system comprises of adapters for the various Transmission Network Equipment deployments in Bharti Airtel Limited consisting of multiple models from the following vendors

ECI

Tellabs Nortel

Huawei

Alcatel

Ciena

Siemens

Tejas The system will discover networks including identification of the network elements, circuits etc based on user configured parameters. The system also considers the circuits passing through the clouds and virtual concatenation groups.

2.2 CygNet OTNMS Architecture

The below diagram shows the high level software architecture of CygNet OTNMS solution, It includes the top level functional blocks and its internal modules along with their interactions with other modules.



2.3 Security

Security is the assurance of legitimate use, maintenance of confidentiality, data integrity, and the ability to audit the network management operations. It involves identifying the assets, threats, and vulnerabilities of the system, and taking protective measures that, if not done, might lead to unintended use of the system. The Security Administration module enables you to manage CygNet Discovery Server security information.



Chapter 3

Getting Started



3. Getting Started

This chapter demonstrates how to start operating the CygNet OTNMS. 3.1.1 Starting the CygNet Client

To start the CygNet client from Windows, go to the CygNetClient_Home/bin and execute (double click) startclient.bat. A login screen appears in which you can enter your CygNet Username and Password as seen in the figure. Enter the CygNet Server IP in the Server Host field, and Windows System IP in Systems IP field.

Click Connect button, then you will get a loading frame as shown below.

Once you have logged in, by default the map opens up on your desktop with various menus, which are discussed in the later sections. Each of these menus seen in the next figure has drop-down sub-menus under them.



For ease of use CygNet is designed with twin frames, the one on the left displays a tree menu with its leaf nodes listing various modules. Selecting a node in the left frame will display the details relevant to the selection on the right frame. 3.1.2 Standard Toolbar

The standard toolbar present in the Network Manger, all the NMS Maps and Custom Maps has the following buttons

Functions of the buttons in the Tool bar is specified below.

Symbols Symbol Name Description

Save Configuration Button

To save the configurations done in the CygNet OTNMS

Re-lay out Button To reset the layout of the maps

Find Button To find any managed object added in the maps

To open in a new window with all the links between the selected nodes in the maps



To open in a new window with selected links between the selected nodes in the maps

To open in a new window with all the links of the selected nodes maps



Chapter 4

Network Discovery



4. Network Discovery

4.1 Introduction

The CygNet OTNMS provides an enhanced discovery utility that allows the user to perform scheduled discovery and rediscovery, with a wide range of discovery options to choose from.

Before starting the Network discovery process, Transport EMS should be added. The next section discusses on addition of Transport EMS.

4.2 Adding a Transport EMS

This section describes how to add a Transport EMS

Using the Add sub-menu, you can add the Transport EMS. Click Elements sub-menu in the Edit menu, select Add Transport EMS and a window opens up as seen below.



The user should key in the EMS Name, Username and Password (The default values for Username is username and password is password). The transport EMS will be added and represented with a suitable icon on the map as seen below. In General this will be done by Administrator.



Discovery can be initiated in two ways,

Profile based discovery

o Discovery Profile Manager

o Discovery Process Manager

On demand discovery

4.3 Discovery Profile Manager.

This is used to create a many profiles based on number of EMS/NMS available in the network and to define the discovery scope, schedule and re-discovery schedule etc.

The Discovery Profile Manager a sub menu in the Discovery menu should be used to

configure scheduled discovery.



On invocation of Discovery Profile Manager the frame as shown below comes up. The home

tab is displayed with the configured profile(s).



Discovery Profile Manager enables

Addition of a new Profile

Modify a Profile

View a created Profile Delete a Profile

Each of this is described in the sections below. 4.3.1 Add a Profile

To create a new profile,

Click New button

The add profile frame as seen below comes up.

In the Add Profile frame, perform the steps given below

Enter the profile name in Profile Name field. Enter the description of the profile in Description field.

Choose the Profile Type as EMS.

On clicking the Next button the next step in Discovery Configuration comes up as shown below.



In this step,

Choose Access Details. (If any authentication is required to access the NMS. In general this will be required to access the NEs and for others we can left blank)

The various discovery options can be selected by the user namely ME info, PTP, Hardware inventory, Matrix Flow Domain, Cross Connect, Protection Group, Sub Network, Flow Domain, Flow Domain Fragment, SNC, TL (Topological Link), Supporting Equipments, and For logical discovery, there is only one option to be

selected based on the support in EMS/NMS

o SNC or

o Cross Connect.

Both SNC and Cross Connect should not be selected.

On clicking the Next button the next step in Discovery Configuration comes up as shown below.



The Discovery Schedule section allows you to schedule the discovery and the rediscovery

intervals.

We can schedule the discovery by selecting Schedule check box.

Automatic Rediscovery can be enabled by selecting Rediscover check box.

Blackout

Click Save button to finish the new profile addition.

4.3.2 Modify Profile

The Discovery Profile manager provides an option to modify a profile; the user can select a created profile and modify it. To modify a profile the state of the profile should be inactive; more on this will be discussed in the section Discovery Process Manager.

To modify the profile, follow the steps given below.

Click the Discovery Profile Manager submenu from the Discovery menu.

Select a profile name and click Modify button.

Perform the modification and click save button to finish the modification.



4.3.3 View Profile

A created profile can also be viewed by using the View profile option in the Discovery Profile Manager.

To view the profile, follow the steps given below.


Select a profile name and click View button



4.3.4 Delete Profile

A configured profile can be deleted in the Home screen. To delete a profile the state of the profile should be inactive; more on inactivating a profile will be discussed in the section 4.4 on Discovery Process Manager

Steps to delete a profile,


Select a profile name and click Delete button to delete the profile.

Note: Active Profiles cannot be deleted



4.4 Discovery Process Manager

This feature will help to activate the newly added profiles. This page will provide current state of profiles, when profiles are scheduled, start, stop, suspend and resume the profiles.

The Discovery Process Manager a sub menu in the Discovery menu is used to monitor and

control the status of Discovery Profiles created in the previous section.



On invocation of the menu the Discovery Process Manager comes up.

The Discovery Process Manager displays the following.

List of profiles created through Discovery Profile Manager

Current Status of the profiles (Default is InActive).

Process Status of the profile.

Extraction state of the profile.

Recon State of the profile.

Next Schedule of the profile.

A newly created profile will be in the inactive state and can be activated to start the discovery

process as shown below.

4.4.1 Profile activation

From this User Interface (which would be mentioned as UI hereafter),

The user can select the required discovery profile and can activate it by clicking the Activate button.

On activation the status of the profile changes to Active state.

The Process, Extraction & Recon State changes to Not Running.

The Next Schedule column will be updated with the configured schedule time mentioned in the profile, indicating the time at which discovery will begin.



4.4.2 Starting a profile

On clicking the StartNow button user can start the profile.

On clicking the StartNow button the Process state changes to Running.

The other possible process states are suspended and Interrupted

When we Suspend the process the Process State changes to Suspended

When the process is Interrupted the Process State changes to Interrupted.



4.4.3 Suspending a profile

The Running process can be suspended by selecting the process and clicking on the Suspend button.



4.4.4 Resuming a profile

A suspended process can be resumed by clicking on the Resume button.



4.4.5 Stopping a profile

A suspended process can be stopped completely by clicking on the Stop button.



4.4.6 Viewing process history

The Process History button will indicate the progress of a running discovery.

Click on the Process History button to view the process history for a specified period.

Select any process and Click On Show Details button.

A sample snapshot of the process history details including start and end time.



4.5 On Demand Discovery

Alternative to the Scheduled Discovery we can use the On Demand Discovery (Manual Discovery). The Manual Discovery can be invoked by a right click on the EMS/ME level as shown

in the snapshot below.

At the EMS level the following options are available

Discover MEs: Discovers all the MEs available in the EMS/NMS

Discover Supporting Equipments: Discover Flow domains:

Discover Sub networks:

Discover Links and Trails : Discover all the Topological links and Trails available in the

EMS/NMS

SNC Discovery by ME: Discover SNCs ME Wise



At the ME level the following options are available

Discover PTPs: Discovers all the PTPs available in the ME.

Discover Equipments: Discovers all the Equipments available in the ME.

Discover Cross Connects: Discovers all the Cross Connects available in the ME

Discover PGPs: Discover all the PGPs available in the ME. Note: On-demand manual discovery can be used when properties for a specific ME have to be

discovered in the sequence listed above. Discovery through the Discovery Profile Manager option is recommended for a complete discovery.

4.5.1 Guidelines for doing On-demand discovery

On demand discovery is generally used to immediately see the specific changes done in a network element. On demand discovery is not recommended while the circuit discovery, inventory export and circuit export is in progress. Its only recommended while the inventory discovery is in progress. Its basically recommended to do at the Node level. EMS level discovery is a time consuming one. The user has to follow the hierarchy before doing the discovery. The hierarchy is same as the one described in Process Manager. For example we cant discover the Protection Groups unless the PTPs are discovered. First the PTPs have to be discovered and then the PGPs have to be discovered.



EMS level On-demand discovery options: Note:

On-demand discovery on EMS level is a timing consuming one.

EMS Level options Recommended Remarks

Discover ME YES Duration of discovery depends on the number of MEs present in the EMS/NMS.

Discover Links and Trails YES Duration of discovery depends on the number of Topological Links present in the EMS /NMS, time consuming.

ME level options:

ME Level options Recommended Remarks

Discover PTP YES Duration of discovery depends on the number of PTPs present in the ME

Discover Equipment YES Duration of discovery depends on the size of the inventory

Discover PGPs YES Duration of discovery depends on the size of the inventory

4.5.2 Viewing on Demand Discovery process history

This option is available in the Discovery Ondemand Discovery Process Manager menu

The Process History button will indicate the progress of a running discovery.

Click on the Process History button to view the process history for a specified period.



4.6 Deleting Network Elements

4.6.1 Delete Symbol

This option is available in the Edit - Element menu

It should be exercised to remove the Network element from the Custom map.

Navigate to the Custom map, select the network element and invoke the Delete Symbol menu, a frame as shown below appears.



On confirmation from the user and successful deletion a pop up appears indicating successful deletion.



4.7 EMS, NE and Link Properties

The CygNet OTNMS offers information on the various element details in a single frame. The properties of EMS, ME, Circuits and Links can be seen using this feature.

4.7.1 EMS Property

Right click on the EMS and invoke the Properties page as shown below.

On invocation of the Property page the frame as shown below comes up,

EMS property frame contains General, EMS Details, NE List, Additional Info and User Data tabs.

EMS Details tab shows the EMS Label, Native EMS name, SW version and Type of the EMS

Two buttons are available in NE List tab namely Export and Element Properties.

Export button used for export the NE Details in CSV format.

Element Properties button used to view the properties of the selected NE from the table.

Additional Info tab shows the NMS IP address

User Data tab shows EMS label, IPs and Network Group.



EMS Details Tab:

NE List Tab:



EMS Additional Info Tab:

EMS User Data Tab:



4.7.2 ME Property pages

Click on EMS in left tree to view all ME/VNE on map.

Right click on the ME/VNE and invoke the Properties menu. The ME property frame comes up.



This page will provides the in depth details of the Network Element like

General

Element Details

Hardware Inventory

Port Inventory Tree

Port Utilization

Cross Connection

Protection Groups

Topological Links

Circuit

CTP Usage

Map List

Additional Info

Port Details

Involved Topology

User Data

Bridges

Services

VSI Mapping



Click on the Element Details tab to view the details of the selected element. The Element details

like EMS label, address, software version can be seen in the Element details tab

Element Details Tab:

Update button is used to update the remarks field value

Open Chassis View This will provide the unified chassis view of the element with card holder, cards and ports.



A snapshot of the Hardware Inventory tab details is shown below. The view displays the

Equipment native name, version and hardware details of the ME. Hardware Inventory tab:

Export button is used to export the CTP Usage data in CSV, HTML format.



Click the Port Inventory Tree Tab this brings up the Port Inventory details.

Select the object in the left tree the corresponding card, port and ctp details are shown on the right. Port Inventory Tree tab:

Open Link button is used to view the link properties associated with the selected port

Click CTP Tree View in the Port Inventory tree. The CTP connection states, namely

connected, terminated and free will be shown in the view.

CTP Matrix View button is used to view CTP view in the form of Matrix



CTP Tree View:

CTP Matrix View:



Click on the Port Utilization tab to view the Equipped ports, Used ports, Free ports and

Percentage of Utilization of ports in the NE.

Port Utilization tab:

Export button is used to export the port utilization details in CSV and HTML format.



Click on the cross connection tab to view the Cross Connections in the NE.

The cross connection information with Rate, Direction, AEnd, ZEnd information etc will be shown in this view.

Export button is used to export the Cross Connection details in CSV and HTML format.

Cross Connection tab:

Export button is used to export the port utilization details in CSV and HTML format.



Click on the Protection Group tab to view the list of protection group in the NE

The Protection Group tab will show the information like PG Type, Rate, Worker Ports, Protecting Ports, Reversion mode and PG Parameters etc.

Protection Group tab:

Export button is used to export PG details in CSV and HTML format



Topological Links present in the NE can be seen in the Topological Links tab

Topological Links Tab:

Open Link Properties button is used to view the Link properties.

Export button is used to export the link details in CSV and HTML format.

Delete button is used to delete a Topological Link



Circuit information can be seen in the Circuit tab. This tab shows the layer rate, customer name,

circuit id, Directionality etc

Circuit Tab:

Open Service Properties button is used to view the properties of the selected service.

Export button is used to export the service details in CSV and HTML format.



CTP usage status can be seen in the CTP usage tab. This tab shows the Port, CTP and its

usage status.

CTP Usage Tab:

Export button is used to export the service details in CSV and HTML formats.



Click on Map List tab to view the list of maps in which the NE is located. The tab shows the

Symbol name and Map Name.

Map List Tab:



Additional info tab shows the additional information of the ME exposed in the NBI

Additional Info Tab:



Click on the Port Details tab to view the Physical Port the details like Rate, Type, Interface Type,

Usage state etc.

Port Details Tab:

Open Properties button is used to view the Port details



4.7.3 Link Property

This page helps to provide the details to see the link details like, AEND and ZEND Details, whether link is protected or not with discrepancy details, Role of the links with Additional info details exposed from.

NBI Topological Link properties can be viewed in the following ways.

From the Map Right Click the Link and invoke Properties

In the ME property page go to Topological Links tab select a link and click Open Properties

In the Inventory Search Link can be searched based on Name, Label and LayerRate

Link Property from Map:



The Link Details tab shows the Link Rate, Type, Direction and Protection Role, A end & Z end

NE and their port details.

The Protection info tab displays AEnd protection details, Z End Protection details, Protection

Complement ports and Protection Results.



Protection Result box will also show the if there is any PGP discrepancy in the selected Link as shown below

The Protection Complement Links tab displays Associated Topological link details.

Open Link button is used to view the properties of the selected link



The link utilization summary is displayed in the link utilization tab. The link utilization summary

can be generated for

Actual cross connection distribution

After VC-4 level Optimization or

After link level Optimization

The Export button is used to export the utilization data in CSV format

Show Channel Matrix Panel button is used to View the Channel Matrix View of the Port.

Link Utilization Tab with Current Cross Connection:



Link Utilization Tab after VC-4 Level Optimization:

Link Utilization Tab after Link Level Optimization:



Channel Matrix View tab:

The Circuit tab displays the list of circuits in the selected link; it also shows the circuit details like

Circuit Name, Layer rate, Directionality etc.

Open Service button is used to view the properties of the selected service.

Export button is used to export the circuit details in CSV and HTML format.



Additional info tab shows the additional information of the Link exposed in the NBI

Additional Info Tab:



4.8 Import and Export

The CygNet OTNMS Import/Export feature facilitates to export various reports for the selected set of network elements. The Import/Export has the following menus

Multiple NE Export

Each of this is explained in the following sections.

4.8.1 Multiple NE Export

Multiple NE Export is used to export various reports for the selected NEs. Invoke the Multiple NE Export menu from the Import/Export menu. A GUI as shown below comes up.



In the Multiple NE Export frame the user can search the NE using the Property as Label, ME Name and Address.

List of NE's matching the search Value will be listed in the left side frame.

User can select the NE's using the SelectAll / DeselectAll button and can add it to the Right side frame to generate the report.

Reports of the selected NE will be saved in the user specified location

Report type can be generated is shown below.

Reports can be generated in csv or html format



4.9 Circuit Discovery

4.9.1 Discover Circuit from Database

The CygNet OTNMS offers a utility to trace the end to end service from CTP point from the CygNet.

The Discover circuit (from DB) option can be invoked from the Service Management menu as seen below to discover the circuit from the Database.

On invocation of the menu the following frame comes up. Select the CTP and click on the Trace Circuit button

The traced circuit will be generated. A sample snapshot is shown below.



There are two icons available in the frame.

- On clicking this icon, the user can save the circuit as an Image.

- On clicking this icon, the users can change the circuit visibility settings.

A sample hanging circuit is shown in the snapshot below.



4.9.2 Discover All Circuits

Using the Discover All Circuits option, we will be able to build all the possible circuits

based on the discovered inventory across various vendor NEs.

Click Discover All Circuits from Service Management Menu

The following window will appears. Then click Discover All Circuits button to initiate the complete circuit discovery.

Discover All Circuits should not be run frequently and it should be initiated by Administrator only.



Once the Discover All Circuits" option is chosen the status of Circuit Discovery will change from Not Running to Running state.

4.10 Ring Discovery

4.10.1 Topology Manager

The CygNet OTNMS offers a utility that discovers (manually & semi auto) the topology from the CygNet Database

The Topology Manager option can be invoked from the Topology Designer menu as seen below to discover the topology from the Database.

On invocation of the menu the following frame comes up



Create menu is used to create a Topology

View menu is used to view the stored Topology

Delete menu is used to delete the stored Topology

4.10.1.1 Create Topology

Using create topology we will be able to discover the MSSP and SNCP Rings

4.10.1.1.1 Create topology using Using Design design type

For MSSP Ring Select Topology Type as TWO_FIBER_BLSR

MSSP Ring Discovery can be in done in two ways

Manually selecting Single Port

Automatically discovering all 2F BLSR topologies in the given list of EMS

Manually creating topology using Single Port

Select EMS Name it will load all the Element Names which are having 2F BLSR PGP's

Drill down to select the port it will highlight the rack, shelf, slot and port.

Once the port of given Protection Group is selected, start Button will be enabled to start the discovery process.

If Given 2F BLSR Links are proper it will be saved as Topology.



Manual MSSP Ring Discovery:

Auto 2F BLSR topology discovery

Select EMS Names

System will find all the Protection Group ports of 2F BLSR Type of selected EMS's and saved as topology

Auto 2F BLSR topology discovery:



For SNCP Ring Select Topology Type as RING

SNCP Ring Discovery can be in done in two ways Manual and Semi - Auto



Manual Ring Computation:

Right click on the empty graph and select "Start Topology Design" menu to design. It will invoke a new frame for adding NE.

Add the NE and Click OK. It will display all the links in the NE.

Using the menus Show Links, Select Link, Backtrack, user can trace the Ring.

Use Backtrack menu for a NE and use Show Links menu to show links of all available layer rate.

The trace is continued in the layer rate of the selected source NE.

Then the ring topology is automatically formed by tracing the link connected to each NE till the destination port is reached.

The trace will be stopped with a NE which has no further links and the user is given a message (No further links available for this NE).

Ring must end in the starting NE to save it as a proper topology.

If save button is clicked in midway of design, before the ring is complete, the user is given a message (Graph design is not yet completed) and the topology is not saved.



Addition of NE:

Selecting a Link in Manual Discovery:



Displaying Links:

Show Links:



SNCPRing:

Semi-Automatic Computation:

Right click on the empty graph and select "Start Topology Design" menu to design. It will invoke a new Ring Design Details frame.

Add the NE and Click OK. It will display all the links in the NE.

Select start and destination ports using Ring Design Dialog window. Topology label is optional

Selecting an aggregate node makes automatic ring trace easier.

Ring must end in the starting NE to save it as a proper topology.

If save button is clicked in midway of design, before the ring is complete, the user is given a message (Graph design is not yet completed) and the topology is not saved.

Ring Design Details:



Addition of NE:

Selecting Source Port and Destination Port:



Discovered Toology:



4.10.1.1.2 Create topology using Ring Name Design design type

EMS/NMS Ring Name Design parameter is used during the discovery of topology

Select Design Type as Ring Name Design

Select EMS/NMS from dropdown to discover topology in respective EMS/NMS.

Select check box to discover topology.

Click on Discovery Topology button to discover topology

Click on save button to save topology

Note: This is applicable only for EMS/NMS which supports Ring Name Design parameter.



Discovered Topology:

4.10.1.1.3 View Topology

In Topology Manager option, View Topology can be invoked from the Topology Designer menu to view the topology.

Click on View menu and View Topology submenu to view the topology.

Choose View, Type and source of topology

Click on Find Topology button to find the topologies with given criteria.

Click on Export button to export topology details

Click on cancel button to cancel the result.



Search Topology:

Search Result:



Select any topology and Click on Open Topology button to view topology below details.

Topology details

Graphical View

Involved Topology Elements

Topology Utilization

Circuit

Traffic Metrics

NE Wise Drop Traffic

Topology Drop Traffic

Graphical View:

Graphical View tab display the node connectivity in graphical fashion.

Click on Save button to save topology in graphical view.



Involved Topology Elements:

Involving topology list out the NE and Topological details involved in the topology.

Topology Utilization:

Topology utilization tab list out the utilization of topological links involved in the topology.

Click on below mentioned tabs to view utilization

Topologica Links

Currently working circuits

Provisionable currently

Provisinable after defragmentation

Utilization

Ring Utilization Computation:

For computing the utilization of SNCP/MSSP rings, the system is considering the maximum utilized links utilization as the ring utilization

Note: For MSSP rings, system is considering only the half of the ring bandwidth.



Click on Export button to export topology utilization



Circuit:

Circuit tab list all the circuits passing through the topology.

Click on Open Properties button to see circuit properties.

Click on Export button to export circuits.

Traffic Metrics:

Traffic Metrics tab list out the traffic summary of the topology.

Click on Export to export the metrics.



NE Wise Drop Traffic:

NE Wise Drop Traffic list out the drop traffic count.

Click on Export button to export NE Wise Drop Traffic details

Topology Drop Traffic:

Topology Drop Traffic list out the drop traffic count.

Click on Export button to export Topology Drop Traffic details



4.10.1.1.4 Approach used

Line Protected Topologies

Physical Connections involved in SDH Line Protection schemes (MSP and MSSP) will be derived

based on protection group configuration discovered from the network. The topology types derived

using this approach are listed below

1. MSP 1+1

2. MSP 1:N

3. MSSP

The above topologies will be discovered based on the MSP / MSSP configurations discovered from the network. No extra rules / business logic will be used to derive these topologies. These will be derived purely based on the SDH inherent line protection schemes and related configuration information.

User-Defined Topologies

The topologies that are not involved in any line protection scheme will be derived based on

standard operational practices followed in the Bharti network and related business logic. The

topology types derived using this approach are listed below

1. SNCP-Ring

2. SNCP-Dual Homing

3. SNCP-Linear Chain

4. SNCP-Mesh

Logic behind deriving the User-Defined Topologies only. This does not apply to the Line

Protected Topologies discussed in the previous section.

Criteria

These topologies will be derived based on the following three criteria. All the following criteria

together will be used to identify the distinct topologies

1. Ring Name obtained for the link ( This attribute is discovered as an attribute of Physical Link )

2. Rate of the Link

3. All links in a topology should be connected

Criteria 1: Ring Name

All the links discovered will be examined to derive its ring name. This value will be taken directly

from an attribute of the discovered link or by applying business logic on an attribute of the

discovered link. On identifying the ring name, all such links will be narrowed to be a single group,



which will be further scrutinized with the remaining two criteria listed above. The following table

summarizes the logic for deriving the value of ring name for various vendors across TNG/ANG.\

Vendor TNG ANG

ECI Type : Actual Attribute

Value for Ring Name

Object : TopologicalLink

Attribute =

LSNExt_LinkRingName

Type : Actual Attribute

Value for Ring Name


Attribute = UserLabel

Tejas Not applicable


Value for Ring Name



Alcatel

Type : Attribute &

Business Logic



Logic : First 10

characters of User Label

to be used as Ring name.

As confirmed by

business.

Not Applicable

(Rings are not available

in ANG)

Tellabs No SNCP Rings available Not Applicable

Huawei No SNCP Rings


Value for Ring Name



Ciena Not Applicable TBD



Criteria 2: Categorization based on Link Rate

On applying Criteria 1, all links that have a same ring name will be narrowed to be a single group.

Such a group will be further split into various sub-groups based on the rate of the links in that

group. This will ensure that all the links in each such split sub-group will all have a same ring

name and will be of the same rate (STM-n).

Criteria 3: Connected Links in a Topology

On applying Criteria 1 & 2, all links that have a same ring name and that have a same rate (STM-

n) will be narrowed to be a single sub-group. Now, there is a possibility that the links in a sub-

group may form one or more sets of topologies in such a way, that the links and nodes in each

set is completely connected, whereas there will not be any continuity between the nodes of those

sub-groups. In such a case, each such set which has a complete connectivity will be formed as a

topology.

4.11 General

4.11.1 Custom Map Creation

Select Create Custom Map from Edit menu.

The following frame will appears.

Enter the Name in Name field.

Parent Map Name can be Changed

Select Assign Privilege

.



Select the Criteria and Click ADD, The following frame will appears.

Create Rules by selecting the Field, Condition and Value

More than one rules can also be merged to form a group

Select Group Name and Press Submit

Click on Create Map button to finish the custom map creation



Adding Rule for Custom Map Creation:

Adding Group for Custom Map Creation:



Tab Showing Custom Map Criteria:

Custom Map Creation Notification:



4.11.2 Search Elements

Select the Find symbol in the Toolbar of the Map

A search frame will appears.

Enter the Label and Click Find

NEs matching the search will be listed. Select a NE from the list Selected NE will be highlighted in the MAP as shown below

4.11.3 Topological Link Addition

Go to Edit Elements Add Topological Link

Add Topological Link frame will appears.



Provide the details like Link label, Link type, Link layer and directionality.

Select source and destination port.

The users cannot select the port, if the link is already present on that port.

Layer rate of the source and destination port should be same.

Click Add Link button to finish the Topological Link addition

4.11.4 Topological Link Deletion

Select the Topological Link form the NE property page

Click Delete Button.

Delete Traces window will open

All the circuits passing through the selected link will be shown in the Service tab of the Delete Traces window

Click yes to delete the link

Deleting the link will also delete the dependant services of the Link



4.11.5 Addition of VNE/Virtual Network

4.11.5.1 VNE / Virtual Network addition

Go to Edit Elements Add VNE / Virtual Network menu.

Create VNE / Virtual Network frame will appears.



Provide the Name, Location, Remarks in the corresponding fields.

Choose the Type as Element or Network.

Follow the steps given in 9.5.2 to add the inventory.



4.11.5.2 Inventory Addition

Follow the below steps to add the inventory,

Select Virtual NEs in left panel.

Right Click on the created Virtual NE in the right side frame and Select Properties and choose inventory tab.

In selection area, Choose rack or shelf as object.

Click Add button to add the selected object to the tree and click Add button.

Select the object one by one and click Add button as shown in the below snapshot.

While adding the Ports, the CTP will get added automatically based on the layer rate of the port.

Remove button is used to remove the object from the inventory tree.

Rename button is used to rename the objects name.

Click Create button to finish the inventory addition for the VNE



Inventory Addition:



4.11.5.3 Addition of Cross Connection

Click Virtual NEs Map in the left tree panel.

Right click on the VNE in the sub map and click Properties menu. VNE Properties frame will appears. Choose Add Cross Connection tab. Select the Layer Rate in Select Layer Rate drop down menu. Select AEnd and ZEnd CTPs, then click Set button. Select Working Port/CTP should be selected first. Protecting CTP/Port can be added only after adding the working CTP/Port. Click on Create Cross Connection button to finish the cross connection

creation. Click on Cross Connection tab to view the Cross connections Created. Delete Selected Cross Connection button is used to delete the selected

cross connection Export button is used to export the Cross Connections in CSV format.

Refresh button is used to refresh the Cross Connection list.



Creating Cross Connection:

Creating Cross Connection:



Viewing the Cross Connections:

Deleting Cross Connection:



4.12 Inventory Search

Inventory Search is used for getting the complete details of Inventory available across various maps from a single frame using defined search options.

The search can be performed for the following entities

EMS

ME

VNE (Virtual Network Element)

Virtual Network

Link

Service

Connectionless Service

Topology

To invoke Inventory Search, choose Edit Inventory Search from the Main Menu as shown below.



The user can choose the Search for entity from the drop down list and choose the appropriate search criteria.

The Property drop down list in the criteria section corresponds to the entity type searched.

Click on Add button, to add search criteria. Multiple search criteria with AND/OR condition can be used for search

Click on Search button for viewing the complete details of the resultant inventory.

The search output can be exported to a CSV/Html format as desired using the Export option



4.13 Network Metrics

Click Network Metrics submenu from Import/Export menu.

Network Metrics frame will appears as shown below

Select the type Metric Report from the left panel.

Click select button to view the report.

Users can export the Metrics Report in the form of CSV or HTML by clicking the Export button.

Reports will be saved in the user specified location

Following Metrics Report can be exported

EMS List

EMS Level Metrics

ME Model Report

ME Version Report

PTP Rate Report

Equipment Label Report

Equipment Part Number Report

Topological Link Rate Report

Inter-EMS Topological Link Rate Report

SNC Rate Report

PGP Rate Report

Circuit Rate Report

Customer Count Report

Network Free Slot Count



EMS Level Metrics:



Chapter 5

Reconciliation



5. Reconciliation

CygNet OTNMS Reconciliation process involves the following actions

Discrepancy computation of the Reconcilable objects

Discrepancy correlation of the Reconcilable objects

Updating the identified discrepancies in M6 NRMS which involve creation, deletion or

update of attributes/properties of the object. Update will be done either automatically or

as per the user confirmation through workflow

CygNet OTNMS will do the Discrepancy computation and Correlation for the following

Reconcilable objects.

Network Element

Card

Topological Link

Circuit

After the Discrepancy computation and correlation, system will categorize the identified

discrepancies as follows

Only in CygNet

Objects which is present only in Network and not in M6

Changed

Objects that are exists both in Network and M6, but some of their common

attribute values got changed

Only in Metasolv M6

Objects which is present only in M6 and not in network

Error (CygNet/Metasolv)

Objects which are having configuration issues like same ip for two devices in

M6, so those network and m6 objects will be categorized here



NE Error Bucket:

NE Error bucket is classified based on Error Message as mentioned in the below table.

Error Message Reason

Key Based Error IP conflict in Network / Metasolv

Out of Scope / Metasolv ME

Out of Scope

Not a valid Spec ID available in Metasolv

Root equipment is not associated with that particular NE

Multiple root equipment

configured for the same NE

More than 1 root equipment is associated with that particular NE

Card Error Bucket:

Card Error bucket is classified based on Error Message as mentioned in the below table.


Parent not processed Parent NE/Card not reconciled

Parent Error Its Parents cards/NE in error bucket.

Parent Not In Sync Parent cards having equipment type discrepancy.

Topological Link Error Bucket:

Topological Link Error bucket is classified based on Error Message as mentioned in the below

table.


Parent not processed Corresponding card is not reconciled

Parent Error Its Parents cards/NE in error bucket.

Parent Not In Sync Parent cards having equipment type discrepancy.

OUT_OF_SCOPE Corresponding NE/Card is out of scope.

To View the Reconciliation Summary Invoke the Summary View under Reconciliation menu



On invocation of the Summary View the following frame comes up

Choose Network Group from drop down to view reconciliation summary BU vise.

Click on View button to view reconciliation summary for chosen Network Group.

ObjectType column shows the list of Reconcilable objects.

Click on to export the Reconciliation summary in CSV format.

Reload button is used to refresh the Summary details.

Click on the category to view generated discrepancy.

Select Records per page from Records per page drill down to view set of records.



Click on Previous or next link to view previous or next set of records.

Show Filter feature is used to search an discrepancy from the List based on the field

and Criteria

View button is used view the individual discrepancy details in a separate window

Click on to export the details in XLS format

Click on to view the legends used

Click on Close button to close a window



Chapter 6

Workflow



6. Workflow

6.1 Introduction

Workflow Management feature is used to update generated discrepancies of various objects likes ME, Card, Links & Circuits into M6 NRMS.

Follow the below steps to use Workflow feature.

Click Workflow Management submenu from Reconciliation menu

Work Flow Management window frame will appear as shown below

Select the type of object like Network Element, Card, Link and Circuit from Object Type dropdown.

Select the classification like Only in Network, Only in M6, Changed etc based on the selected Object Type.

To process the task, pick the task by selecting the task and then click on pick button .



Unpick the task by selecting the task and then click on Unpick button .

After picking, task owner has to process a task accordingly.



6.2. Update Network Element discrepancy in M6 NRMS

To update Network Element in M6 NRMS, select object type as Network Element and then classification in left tree accordingly.

6.2.1 Update Network Element Only In Network discrepancy in M6 NRMS

Follow the below procedure to upload NE in M6 NRMS.

Select task and

Pick the task by clicking on Pick button

Click on Update button

Select Proceed to update radio button, Enter Work Log, and click on Next button

Provide required details like Network Systems, Location, Rack & Mounting Positions and click on Update details button

Click on Next and Proceed button to update NE in M6 NRMS

After update message, click on Finish button to finish the task

Select Task:



Pick Task:

Proceed to update:



Input details required:

Provide input details:



Update Details:

View discrepancy details:



Proceed to update discrepancy:

6.2.2 Update Network Element Changed discrepancy in M6 NRMS

Follow the below procedure to update NE attributes in M6 NRMS.

Select task


Select the task, then click on Update button


Click on Proceed button to update discrepancy




List of Tasks:

Pick Tasks:



Task details:

View Discrepancy details:




Status of update discrepancy and finish task:



6.2.3 Update Network Element Only in M6 discrepancy in M6 NRMS

Follow the below procedure to update NE attributes in M6 NRMS.

Select task


Select the task, then click on Update button

Select Proceed to dele radio button, Enter Work Log, and click on Next button

Click on Proceed button to update discrepancy


Pick task:



Proceed to delete:




Proceed to delete:

6.3 Update Card discrepancy in M6 NRMS

To update Card in M6 NRMS, select object type as Card and then classification in left tree accordingly.

6.3.1 Update Card Only In Network discrepancy in M6 NRMS

Follow the below procedure to upload card in M6 NRMS.

Select task




Click on Proceed button to update card in M6 NRMS




Pick Task:

Task details:



6.3.2 Update Card Changed discrepancy in M6 NRMS

Follow the below procedure to upload NE in M6.

Select task




Click on Proceed button to update discrepancy in M6 NRMS





Status of update discrepancy and finish task:



Finish Task:

6.3.3 Update Card Only In M6 discrepancy in M6 NRMS

Follow the below procedure to upload NE in M6.

Select task



Select Proceed to delete radio button, Enter Work Log, and click on Next button

Click on Proceed button to update discrepancy in M6 NRMS




Pick Task:

Task details:




Proceed to delete card:



6.4 Update Link discrepancy in M6 NRMS

To update Link discrepancy in M6 NRMS, select object type as Link and then classification in left tree accordingly.

6.5.1 Update Link Only In Network discrepancy in M6 NRMS


Select the task






Pick Tasks:



Task details:

View task discrepancy:




6.5.2 Update Link Changed discrepancy in M6 NRMS


Select task








Pick Task:

Task details:



Finish Task:

6.5.3 Update Link Only In M6 discrepancy in M6 NRMS


Select task



Select Proceed to delete radio button, Enter Work Log, and click on Next button





Pick Task:

Task Details:




Proceed to delete Link in M6:



6.5 Update Circuit discrepancy in M6 NRMS

To update Circuit discrepancy in M6 NRMS, select object type as Circuit and then classification in left tree accordingly.

6.5.1 Update Circuit Changed discrepancy in M6 NRMS 6.5.1.1 Update Circuit Valid resource discrepancy in M6 NRMS

Follow the below procedure to upload Valid resource discrepancy circuit in M6 NRMS.

Select the task




Click on Proceed button to update circuit discrepancy in M6 NRMS


List of Tasks:



Select Task:

Pick Task and Update:




Upload status:



Finish Task:

Click on Discrepancy Details tab to view the discrepancy.



Click on View Circuit button to view circuit in graphical view & its details.

6.5.1.2 Update Circuit Link Channel Rate Mismatch in M6 NRMS

Follow the below procedure to update Link Channel Rate Mismatch circuit in M6 NRMS.

Select the task




Click on Proceed button to update circuit discrepancy in M6 NRMS




Pick Task:

Task details:




Proceed to update circuit:



6.5.1.3 Update bulk circuits in M6 NRMS

Follow the below procedure to upload bulk circuit in M6 NRMS.

Pick Up tasks

Click on Export/Import Button a popup will be displayed

Click on Export button

Select Export Selected Tasks or Export All Tasks to export tasks details accordingly in Excel file and, save in your local system

After successful export, popup will be displayed to export Exported tasks discrepancies, Click on Yes to export and No to cancel discrepancies export.

Provide corresponding Circuit IDs for selected tasks in excel file (Column - Circuit Label), and save xls file

Note: Tasks that can be uploaded should be available in xls.

Click on Export/Import Button a popup will be displayed

Click on Import button and provide saved xls file

System will validate xls (throw error message if not validated successfully) and build jobs

Provide work log and Click on Proceed button to upload circuit in M6 NRMS


Pick tasks:



Export circuit details:



Export Selected/All tasks circuit details:



Export Circuit discrepancy details:

Provide Circuit Labels in XLS:



Import Circuit details:

Validation of XLS:




6.6 Ignore Task

Follow the below procedure to ignore the task

Select the task


Select the task and then click on Ignore button and provide Work log

Task is successfully ignored



List of Tasks:

Ignore Task:



Chapter 7

Re

cygnet_adrs_usermanual_v1_4.pdf

Documents