0% found this document useful (0 votes)

69 views408 pages

Title Page 1350 Optical Management Syste PDF

Uploaded by

Brwa Luqman

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

69 views408 pages

Title Page 1350 Optical Management Syste PDF

Uploaded by

Brwa Luqman

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 408

Title page

1350
Optical Management System
(OMS)
Release 14.0

Automatically Switched
Optical Networks (ASON) Guide

8DG43185XAAA

Issue 2
October 2016
Legal notice

Legal notice

Nokia is a registered trademark of Nokia Corporation. Other products and company names mentioned herein may be trademarks or tradenames of their
respective owners.

The information presented is subject to change without notice. No responsibility is assumed for inaccuracies contained herein.
© 2016 Nokia.

Notice

Every effort was made to ensure that the information in this document was complete and accurate at the time of printing. However, information is subject to
change.

Warranty

Nokia provides a limited warranty for this product. For more information, consult your local Alcatel-Lucent customer support team.

Ordering information

The ordering number for this document is 8DG43185CAAA. To order 1350 OMS information products, contact your local Nokia customer support team.

Technical support

For technical support, contact your local customer service support team. You can reach them through the Web at the Nokia Customer Support web site
(http://www. alcatel-lucent.com/support) or the customer support telephone number listed at the Nokia Contact Us web site (http://www.alcatel-
lucent.com/contact).

Information product support

For questions or concerns about this or any other Nokia information product, please contact us at one of the following numbers: (888) 727 3615 (for the
continental United States); +1 (630) 713 5000 (for all countries).
Contents

About this document

Purpose ........................................................................................................................................................................................... xix
xix

What's new .................................................................................................................................................................................... xix

xix

Safety information ..................................................................................................................................................................... xix

xix

Intended audience ...................................................................................................................................................................... xix

xix

Document parts ............................................................................................................................................................................ xx

Conceptual and task content .................................................................................................................................................... xx

Format of task content ............................................................................................................................................................... xx

Technical content ........................................................................................................................................................................ xxi

xxi

Treatment of terms ..................................................................................................................................................................... xxi

xxi

Document formats ................................................................................................................................................................... xxiii

xxiii

On-line help ............................................................................................................................................................................... xxiii

xxiii

Ordering information ............................................................................................................................................................. xxiii

xxiii

How to comment ..................................................................................................................................................................... xxiii

xxiii

Part I: Understanding the Product and Concepts

1 ASON Concepts

Overview ...................................................................................................................................................................................... 1-1

1-1

ASON ............................................................................................................................................................................................ 1-2

1-2

ASON/GMPLS Control Plane ............................................................................................................................................ 1-7

1-7

GMPLS Routing Engine ...................................................................................................................................................... 1-15

1-15

ASON Architecture Concepts ............................................................................................................................................ 1-17

1-17

ASON Features and Supporting Functionalities ......................................................................................................... 1-19

1-19

Overview ...................................................................................................................................................................................... 2-1

2-1

ASON Overview in 1350 OMS ........................................................................................................................................... 2-2

2-2

ASON Concepts applied in 1350 OMS ............................................................................................................................ 2-3

2-3

ASON Connection Setup ..................................................................................................................................................... 2-12

2-12

ASON Protection and Restoration ................................................................................................................................... 2-14

2-14

Network Backbone Setup ................................................................................................................................................... 2-18

2-18

3 ASON Configuration

Overview ...................................................................................................................................................................................... 3-1

3-1

ASON Configuration Flow ................................................................................................................................................... 3-2

3-2

Macro-steps for ASON Configuration .............................................................................................................................. 3-5

3-5

Network Construction ............................................................................................................................................................. 3-8

3-8

Bundling rule ............................................................................................................................................................................ 3-11

3-11

High Level Provisioning Flow for Layer 0 GMRE ................................................................................................... 3-12

3-12

High Level Provisioning Flow for Layer 1 GMRE ................................................................................................... 3-18

3-18

4 1350 OMS ASON Provisioning

Overview ...................................................................................................................................................................................... 4-1

4-1

Connections

Connection Definition, Creation, and Categorization ................................................................................................. 4-3

4-3

Connection Auto Discovery and User Creation of Connections ............................................................................. 4-7

4-7

Infrastructure Connections and Services ....................................................................................................................... 4-10

4-10

Client/Server Relationships ............................................................................................................................................... 4-15

4-15

Create an OTN Physical Connection .............................................................................................................................. 4-16

4-16

Modify the Allocation Cost of a Physical Connection ............................................................................................. 4-38

4-38

Modify the Parameters of an Infrastructure Connection or Service .................................................................... 4-40

4-40

Single Step Provisioning ..................................................................................................................................................... 4-42

4-42

Modify the Route (Reroute) of a Connection .............................................................................................................. 4-45

4-45

Auto Payload ............................................................................................................................................................................ 4-51

4-51

Auto Creation of Edge Connections ................................................................................................................................ 4-56

4-56

Unterminated OTUk/ODUk Infrastructures without Virtual Termination Management ............................. 4-58

4-58

Y-Cable Protection for Services ........................................................................................................................................ 4-64

4-64

SNC Protection for 1830 PSS OCS NEs ....................................................................................................................... 4-69

4-69

OPSB Protection ..................................................................................................................................................................... 4-72

4-72

Nodes and Network Elements

Add a Node/NE ....................................................................................................................................................................... 4-75

4-75

Synchronize Nodes and NEs .............................................................................................................................................. 4-88

4-88

Part II: Working with 1350 OMS ASON WebUI

5 1350 OMS ASON WebUI

Overview ...................................................................................................................................................................................... 5-1

5-1

Navigate to ASON ................................................................................................................................................................... 5-2

5-2

NPA and SNC: Icons ............................................................................................................................................................... 5-3

5-3

NPA and SNC: Tabs ................................................................................................................................................................. 5-8

5-8

3R Tab ........................................................................................................................................................................................... 5-9

5-9

ASON SNCs tab of ASON NPA ....................................................................................................................................... 5-10

5-10

Alarms tab ................................................................................................................................................................................. 5-13

5-13

Control Planes tab of ASON NPA .................................................................................................................................... 5-15

5-15

End Points Tab of ASON SNCs ........................................................................................................................................ 5-19

5-19

Links tab of ASON NPA ...................................................................................................................................................... 5-22

5-22

Nodes tab of ASON NPA .................................................................................................................................................... 5-26

5-26

Nominal Route Problems Tab ............................................................................................................................................ 5-29

5-29

Routes tab of ASON SNCs ................................................................................................................................................. 5-33

5-33

SNCP tab of ASOn SNCs .................................................................................................................................................... 5-35

5-35

TE Links tab of ASON NPA .............................................................................................................................................. 5-36

5-36

Save and Reset Table Preferences .................................................................................................................................... 5-40

5-40

Export a Data Table to a .CSV File .................................................................................................................................. 5-43

5-43

6 1350 OMS WebUI – Working in ASON

Overview ...................................................................................................................................................................................... 6-1

6-1

Design - Service/Infrastructure Template

Overview ...................................................................................................................................................................................... 6-4

6-4

Network Configuration window .......................................................................................................................................... 6-5

6-5

Connection Template Types .................................................................................................................................................. 6-6

6-6

Deploy – New OTN Physical Connection

Overview ...................................................................................................................................................................................... 6-7

6-7

Deploy a Template to Make a Connection ....................................................................................................................... 6-8

6-8

Create an OTN Physical Connection ............................................................................................................................... 6-11

6-11

View 96 OCH Channel Support in Different Windows of OTN WebUI ........................................................... 6-12
6-12

Operate Phase - ASON

Overview ................................................................................................................................................................................... 6-21

6-21

View the list of NPAs ............................................................................................................................................................ 6-23

6-23

Create an NPA ......................................................................................................................................................................... 6-27

6-27

Add and Remove Links in ASON .................................................................................................................................... 6-29

6-29

Implement/Deimplement an NPA .................................................................................................................................... 6-36

6-36

Access and View the Misalignment Report for a Link ............................................................................................. 6-39
6-39

Activate/Deactivate Auto Restoration of the Control Plane for an NPA ............................................................ 6-40
6-40

Assign an ASON I-NNI Link to a TE Link and/or an SRG .................................................................................... 6-43

6-43

Change ASON WTR ............................................................................................................................................................. 6-50

6-50

Perform Link Maintenance ................................................................................................................................................. 6-53

6-53

Correlate an ASAP with an NPA ...................................................................................................................................... 6-58

6-58

Enable/Disable Fast Photonic Restoration of the Control Plane for an NPA ................................................... 6-62
6-62

Manage 3Rs .............................................................................................................................................................................. 6-63

6-63

Enable or Disable Auto Restoration of Links .............................................................................................................. 6-70

6-70

Manage Jobs in ASON ......................................................................................................................................................... 6-72

6-72

Modify TE-Links .................................................................................................................................................................... 6-76

6-76

Remove an NPA ...................................................................................................................................................................... 6-79

6-79

View the ASON SNCs .......................................................................................................................................................... 6-80

6-80

View an SNC on the Network Map ................................................................................................................................. 6-85

6-85

View a Misalignment Report for an SNC ...................................................................................................................... 6-89

6-89

View the Inherited Priorities of an SNC ........................................................................................................................ 6-92

6-92

Correlate an ASAP with SNC ............................................................................................................................................ 6-94

6-94

Enable/Disable TCM for an SNC ..................................................................................................................................... 6-99

6-99

Enable/Disable the Test Mode for an SNC ................................................................................................................. 6-102

6-102

Explore an SNC on the Routing Display .................................................................................................................... 6-104

6-104

Manage SNCP in ASON SNC ........................................................................................................................................ 6-106

6-106

Manage SNC Restoration Constraints .......................................................................................................................... 6-107

6-107

Modify the Attributes of an SNC .................................................................................................................................... 6-111

6-111

Switch SNC Routes ............................................................................................................................................................. 6-114

6-114

Operate - Network Profiles - Shared Risk Group

Overview ................................................................................................................................................................................. 6-117

6-117

View the Shared Risk Groups .......................................................................................................................................... 6-118

6-118

Create an SRG ....................................................................................................................................................................... 6-120

6-120

Correlate an SRG with a Physical Connection ......................................................................................................... 6-123

6-123
....................................................................................................................................................................................................................................
Nokia 1350 OMS vii
8DG43185XAAA Release 14.0
Issue 2 October 2016
Contents

Control the Deployment of the Physical Connections Associated with a Shared Risk Group ................ 6-129
6-129

Manage the ASON Links Assigned to a Shared Risk Group ............................................................................... 6-131
6-131

Manage the TE Links Assigned to a Shared Risk Group ...................................................................................... 6-132

6-132

Remove a Shared Risk Group ......................................................................................................................................... 6-133

6-133

Operate - Network Profiles – Color Profiles

Overview ................................................................................................................................................................................. 6-134

6-134

View a List of Color Profiles ........................................................................................................................................... 6-135

6-135

Create a Color Profile ......................................................................................................................................................... 6-140

6-140

Associate a Color Link over an Existing ASON Domain ..................................................................................... 6-143

6-143

Manage ASON Links Assigned to a Color Profile .................................................................................................. 6-145

6-145

Manage ASON SNCs Assigned to a Color Profile .................................................................................................. 6-146

6-146

Manage TE Links Assigned to a Color Profile ......................................................................................................... 6-148

6-148

Delete an Existing Color Profile .................................................................................................................................... 6-149

6-149

Operate – Network Profiles – Alarm Profiles

Overview ................................................................................................................................................................................. 6-150

6-150

View Alarm Profiles ............................................................................................................................................................ 6-151

6-151

Create an Alarm Profile ..................................................................................................................................................... 6-154

6-154

Determine the Network Alarm Profile Assigned to a Connection ..................................................................... 6-156

6-156

Modify an Alarm Profile ................................................................................................................................................... 6-157

6-157

Remove an Alarm Profile .................................................................................................................................................. 6-159

6-159

Operate - Wavelength Usage Report

Overview ................................................................................................................................................................................. 6-160

6-160

Wavelength Usage Report ................................................................................................................................................ 6-161

6-161

Generate Wavelength Usage Report ............................................................................................................................. 6-162

6-162

A ASON Alarm and Correlation

Overview ..................................................................................................................................................................................... A-1

A-1

ASON SNC ................................................................................................................................................................................ A-2

A-2

ASON NPA ................................................................................................................................................................................ A-4

A-4

GMRE .......................................................................................................................................................................................... A-5

A-5

ASON SNC Alarms Correlation ........................................................................................................................................ A-7

A-7

B List of Abbreviations

Abbreviations ............................................................................................................................................................................ B-1

B-1

Index

4-1 Modify Connections for Infrastructure Connections and Services ....................................................... 4-46

5-1 NPA Icons ..................................................................................................................................................................... 5-3

5-3

5-2 SNC Icons .................................................................................................................................................................... 5-7

5-7

6-1 Wavelength Report : Parameters ..................................................................................................................... 6-164

A-1 ASON SNC ................................................................................................................................................................. A-2

A-2

A-2 ASON NPA Correlated Probable Cause ........................................................................................................... A-4

A-3 GMRE Probable Cause .......................................................................................................................................... A-5

A-4 ASON SNC Correlated Alarms ........................................................................................................................... A-7

1-1 ASON as a Smart Network .................................................................................................................................... 1-2

1-2 Operating planes for an optical transport network ........................................................................................ 1-3

1-3 GMPLS/ASON key features - 1 ........................................................................................................................... 1-8

1-4 GMPLS/ASON key features - 2 ........................................................................................................................... 1-8

1-5 Mapping between GMPLS/ASON resource models .................................................................................. 1-11

1-6 ASON control processes and components ..................................................................................................... 1-12

1-7 Functional interaction between network nodes within a set of planes ................................................ 1-13

1-8 GMRE top-level architecture .............................................................................................................................. 1-15

1-9 ASON Architecture Requirements .................................................................................................................... 1-17

1-10 Key ASON Architecture ....................................................................................................................................... 1-18

1-11 Network Configuration ......................................................................................................................................... 1-22

1-12 3 260SCX2 (100G Mode) with OPSB – 96 OCH Channels ................................................................... 1-22

1-13 11QPA4 Cascading 130SNX10 with Y-cable – 96 OCH Channels ...................................................... 1-23

1-14 5 11DPM12 Cascading 130SNX10 with Y-cable – 96 OCH Channels .............................................. 1-23

1-15 Figure 6 12P120 Cascading 130SNX10 with Y-cable – 96 OCH Channels ..................................... 1-23

1-16 260SCX2 with OPSB Client Protection with L0 GMPLS – 100GbE Client .................................... 1-24

2-1 Work Split between OMS and Control Plane .................................................................................................. 2-3

2-2 ASON: Network Reference Points and Connection Types ........................................................................ 2-7

2-3 Multi-Region Network ............................................................................................................................................ 2-9

2-9

2-4 ASON - ASON Nominal Route and Current Route - 1 ............................................................................ 2-12

2-5 ASON Nominal Route and Current Route - 2 .............................................................................................. 2-13

2-6 Network resource optimization .......................................................................................................................... 2-13

2-7 ASON – GMPLS Unprotected Service ........................................................................................................... 2-14

2-9 Guaranteed Restoration ......................................................................................................................................... 2-15

2-15

2-10 ASON – GMPLS Protection and Restoration Combined ......................................................................... 2-16

2-11 ASON SRGs ............................................................................................................................................................. 2-19

2-19

2-12 Shared Risk Group .................................................................................................................................................. 2-20

2-20

3-1 ASON configuration flow ...................................................................................................................................... 3-3

3-2 Create subnetwork menu ........................................................................................................................................ 3-8

3-3 Create subnetwork window ................................................................................................................................... 3-9

3-4 High level provisioning flow for Layer 0 GMRE ....................................................................................... 3-15

3-5 Provisioning the Control Plane ODUK connection .................................................................................... 3-17

4-1 Link Connection Example ...................................................................................................................................... 4-5

4-2 Physical Connections – Physical Connection Creation Window – Default ....................................... 4-17

4-3 Physical Connections – Physical Connection Creation Window – Unidirectional ......................... 4-18

4-4 Physical Connections – Physical Connection Creation Window – Default ....................................... 4-20

4-5 Physical Connections – Physical Connection Creation Window – Double-Simple (uni) ............ 4-21

4-6 Physical Connections – Physical Connection Creation Window – Default ....................................... 4-24

4-7 Physical Connections – Physical Connection Creation Window – Bidirectional ............................ 4-25

4-8 Physical Connections – Physical Connection Creation Window – Default ....................................... 4-29

4-9 Physical Connections – Physical Connection Creation Window – E-Sncp ....................................... 4-30

4-10 Physical Connections – Physical Connection Creation Window – Default ....................................... 4-32

4-11 Physical Connections – Physical Connection Creation Window – Y-Cable ..................................... 4-33

4-12 Physical Connections – Physical Connection Creation Window – Default ....................................... 4-35

4-13 Physical Connections – Physical Connection Creation Window – OPS Uplink ............................. 4-36

4-14 DSR Service Creation between Two 1830 PSS-64 OCS NEs Passing Through a 1830 PSS
Photonic Core ........................................................................................................................................................ 4-53
4-53

4-15 DSR Service Creation between One 1830 PSS-64 OCS NE and One 1830 PSS-4 Photonic NE
............................................................................................................................................................................ 4-544-54
4-54

4-16 DSR Service Creation between Four 1830 PSS-64 OCS NEs ............................................................... 4-55
....................................................................................................................................................................................................................................
xiv Nokia 1350 OMS
8DG43185XAAA Release 14.0
Issue 2 October 2016
List of figures

4-18 Nodes – Add Node/NE – Default Window .................................................................................................... 4-76

4-19 Nodes – Add Node/NE – 1830 PSS PHN User Label Tab ...................................................................... 4-78

4-20 Nodes – Add Node/NE – 1830 OCS User Label Tab ................................................................................ 4-79

4-21 Nodes – Add Node/NE – TDMX Tab .............................................................................................................. 4-79

4-22 Nodes – Add Node/NE – TDMXC Tab .......................................................................................................... 4-79

5-1 3R tab ............................................................................................................................................................................. 5-9

5-9

5-2 ASON SNCs tab ...................................................................................................................................................... 5-10

5-10

5-3 ASON SNCs tab: additional attributes ............................................................................................................ 5-11

5-4 ASON SNCs tab: right-click operations ......................................................................................................... 5-12

5-5 Alarms tab of ASON NPA ................................................................................................................................... 5-13

5-6 Alarms tab of ASON SNC ................................................................................................................................... 5-13

5-7 Control Planes tab of ASON ............................................................................................................................... 5-15

5-8 Control Planes tab: additional attributes ......................................................................................................... 5-17

5-9 Control Planes: right-click actions .................................................................................................................... 5-18

5-10 End Points tab ........................................................................................................................................................... 5-19

5-19

5-11 End Points tab: additional attributes ................................................................................................................ 5-20

5-12 Links tab of ASON NPA ...................................................................................................................................... 5-22

5-13 Links tab: additional attributes ........................................................................................................................... 5-24

5-14 Links tab: right-click operations ........................................................................................................................ 5-25

5-15 Node tab of ASON NPA ....................................................................................................................................... 5-26

5-16 Nominal Route Problems tab .............................................................................................................................. 5-29

5-17 Properties tab: ASON NPA .................................................................................................................................. 5-31

5-18 Properties tab: ASON SNCs ............................................................................................................................... 5-32

5-19 Routes tab .................................................................................................................................................................. 5-34

5-34

5-20 SNCP tab .................................................................................................................................................................... 5-35

5-35

5-21 TE Links tab .............................................................................................................................................................. 5-36

5-36
....................................................................................................................................................................................................................................
Nokia 1350 OMS xv
8DG43185XAAA Release 14.0
Issue 2 October 2016
List of figures

5-23 TE Links tab: right-click operations ................................................................................................................ 5-39

5-24 Save Table Preferences window ........................................................................................................................ 5-41

6-1 Network Configuration window .......................................................................................................................... 6-5

6-2 Deploy > New Service/Infrastructure Connection window ....................................................................... 6-9

6-3 Create Connection window ................................................................................................................................. 6-10

6-4 96 channels: Routing Constraints tab .............................................................................................................. 6-13

6-5 96 Channels and the Frequencies: Routing Constraints tab .................................................................... 6-14

6-6 Ingress Power window - 96 channels .............................................................................................................. 6-16

6-7 96 channels: Link Connections tab ................................................................................................................... 6-18

6-8 96 channels: Wave Key Assignments .............................................................................................................. 6-19

6-9 View 96 channels in Client ASON SNCs tab ............................................................................................... 6-20

6-10 List of ASON NPAs ............................................................................................................................................... 6-23

6-11 Additional attributes of ASON NPAs .............................................................................................................. 6-24

6-12 Data table sorting .................................................................................................................................................... 6-25

6-25

6-13 NPA right-click operations ................................................................................................................................... 6-25

6-14 Add Links to ASON option ................................................................................................................................. 6-30

6-15 Add Links to ASON window .............................................................................................................................. 6-30

6-16 ASON Available Objects (INNI) window ...................................................................................................... 6-32

6-17 I-NNI Links panel ................................................................................................................................................... 6-32

6-32

6-18 ASON Available Objects (Drop/UNI) ............................................................................................................. 6-33

6-19 Remove Links from ASON option ................................................................................................................... 6-35

6-20 Auto Restoration option ........................................................................................................................................ 6-41

6-21 Control Planes tab: Automatic Restoration window .................................................................................. 6-41

6-22 TE-Link Assignment window ............................................................................................................................. 6-45

6-23 Set the Administrative State: Right-click options ....................................................................................... 6-48

6-24 Set the Administrative State: Administrative State icon ........................................................................... 6-48

6-26 Link Maintenance window .................................................................................................................................. 6-54

6-27 Link Maintenance window - Attribute icon ................................................................................................... 6-55

6-28 Client ASON SNCs tab ......................................................................................................................................... 6-56

6-29 Server Physical Connection tab ......................................................................................................................... 6-57

6-30 Correlate ASAP option .......................................................................................................................................... 6-58

6-31 Correlate ASAP window ...................................................................................................................................... 6-59

6-32 Npas window ............................................................................................................................................................ 6-60

6-60

6-33 3R Creation window .............................................................................................................................................. 6-64

6-64

6-34 3R Creation window: Add node ........................................................................................................................ 6-65

6-35 3R Creation window: Add NNI Line ports .................................................................................................... 6-66

6-36 3R functions .............................................................................................................................................................. 6-67

6-67

6-37 Auto Restoration > Enable/Disable .................................................................................................................. 6-71

6-38 NPA Job window ..................................................................................................................................................... 6-72

6-72

6-39 Modify TE-Link window ..................................................................................................................................... 6-77

6-40 List of ASON SNCs ............................................................................................................................................... 6-80

6-41 Additional attributes of ASON SNCs .............................................................................................................. 6-81

6-42 ASON SNC sorting ................................................................................................................................................ 6-82

6-43 SNC right-click operations .................................................................................................................................. 6-83

6-44 Display Route on Map option ............................................................................................................................. 6-86

6-45 ASON SNC - Network Map ............................................................................................................................... 6-87

6-46 ASON SNC - Current Route ............................................................................................................................... 6-88

6-47 Misalignment Report option in ASON SNC ................................................................................................. 6-90

6-48 Misalignment Report window - SNC .............................................................................................................. 6-91

6-49 Correlate ASON option in ASON ..................................................................................................................... 6-95

6-50 Correlate ASAP window in SNC ...................................................................................................................... 6-96

6-51 Trails window ........................................................................................................................................................... 6-97

6-97
....................................................................................................................................................................................................................................
Nokia 1350 OMS xvii
8DG43185XAAA Release 14.0
Issue 2 October 2016
List of figures

6-53 TCM Level window ............................................................................................................................................. 6-100

6-54 SNC Test Modes ................................................................................................................................................... 6-103

6-103

6-55 Routing Display of ODU ASON 14_DR4_1350OMS_OTNESMGuide_i1link .......................... 6-105

6-56 SNC Restoration Constraints window .......................................................................................................... 6-108

6-57 TE Links window ................................................................................................................................................. 6-109

6-58 Subnetwork Connections window .................................................................................................................. 6-110

6-59 Modify Trail Parameters window ................................................................................................................... 6-112

6-60 Switch Routes - SNC ........................................................................................................................................... 6-115

6-61 SRG Creation window ........................................................................................................................................ 6-121

6-62 Correlate SRG window ....................................................................................................................................... 6-124

6-63 Physical Links window ...................................................................................................................................... 6-125

6-64 SRG window .......................................................................................................................................................... 6-126

6-126

6-65 List of Color Profiles ........................................................................................................................................... 6-136

6-66 Color Profile additional attributes .................................................................................................................. 6-137

6-67 Right-click actions on ASON links tab of Color Profiles ...................................................................... 6-138

6-68 Right-click actions on TE links tab of Color Profiles ............................................................................. 6-139

6-69 Color Profile window .......................................................................................................................................... 6-141

6-70 Available Colors window .................................................................................................................................. 6-142

6-71 Alarm Profile Identification window ............................................................................................................ 6-155

6-72 Properties tab .......................................................................................................................................................... 6-158

6-158

6-73 Wavelength Usage Report ................................................................................................................................. 6-162

6-74 Exported format of Wavelength Usage Report .......................................................................................... 6-163

6-75 ..................................................................................................................................................................................... 6-163

6-163

Purpose
This preface provides information about how to use this document, which is the
Automatically Switched Optical Networks (ASON) Guide.
The purpose of Automatically Switched Optical Networks (ASON) Guide is to describe
and explain the ASON management in the 1350 OMS as a quick reference.

What's new
This document has been issued to work on the ASON part of the OTN application in the
1350 OMS.

Safety information
This document does not contain any safety information (cautions or warnings) because
the 1350 OMS is a software product.
Important! When working with any hardware that is associated with any piece of
software, always refer to the safety information that the hardware manufacturer provides
for that particular piece of hardware. For example, when working with an server, refer to
safety information that is provided in the documentation for that server. When working
with any Nokia network element, refer to safety information that is provided in the Nokia
documentation for that particular NE.

Intended audience
The Automatically Switched Optical Networks (ASON) Guide is written primarily for
network planners, engineers, administrators, and provisioning operators. This document
can be used by anyone who needs specific administration or connection provisioning
information about the features, applications, and operations of the 1350 OMS in ASON
environment. These people are you, its users.

Conceptual and task content

In the broadest sense, the Automatically Switched Optical Networks (ASON) Guide
contains the following:
• Conceptual information, which is specific data related to the tasks
• Task information, which includes user tasks (that is, step-by-step instructions)
The conceptual information complements and enhances the step-by-step instructions that
are found in each task. Use the conceptual information to broaden your general
knowledge of the network management system. It is best if you read all conceptual
information and have a good understanding of the concepts being presented before
undertaking the step-by-step instructions given in any task.
This type of Guide is aimed to deepen an argument and to give the informations at a high
level of managing in the 1350 OMS, for the detailed task information the user is invited
to read the component specific documentation.
A term that is presented in the text of this document, along with any used abbreviation for
the term, is typically defined where the term is initially introduced. Many of the more
generic terms that are defined in this document, along with the terms that are defined in
other documents in this documentation set, are also defined in the Glossary, which is part
of the Getting Started Guide. We encourage our readers to rely on the Glossary for a
comprehensive set of terms and any abbreviations of the terms.
This document can be used in its on-line versions (HTML/PDF) or in paper version (print
PDF). The on-line HTML document version has a search capability, a full table of
contents in the front matter of the document, a partial table of contents in each chapter, an
index for each document, and an index for the entire documentation set. Use all of these
tools to help find information quickly. However, be aware that the index for each
document and the index for the entire documentation set are the preferred search tools.

Format of task content

Each task consists of sections that are called When to use, Related information, Before
you begin, and Task. The intent of these sections is self-explanatory—they explain when
you should use the task, any related information that you would need to know while doing
the task, and what you need to consider or do before you start the task.

Technical content
In general, the technical content in this document is augmented by technical content that
is provided in other documents in this documentation set and/or in the document set of the
particular network element (NE ) or piece of hardware in the network configuration. It is
the user's responsibility to read all pertinent material in all documentation sets in order to
understand a particular concept or procedure and/or to implement the procedure in his or
her working environment.
This document contains information on the complete line of NEs that the 1350 OMS
supports. Each release of the 1350 OMS and its applications supports certain NEs within
the Nokia family of optical NEs. Mention of NEs or specific NE features in the text of
this document, or any document in the 1350 OMS documentation set, that are not
supported in this particular product release can apply to prior or future product releases.
Such material may not be currently visible or operable on the GUI and/or the server and
has been added only as a convenience for our customers. This material is subject to
change. For a list of NEs that are supported in the 1350 OMS Release 14.0, contact your
Nokia local customer service support team.

Treatment of terms
A term that is presented in the text of this document, along with any used abbreviation for
the term, is typically defined where the term is initially introduced.

Related documentation
The following documents support the Nokia 1350 OMS Release 14.0 :
1. The Getting Started Guide (8DG43185AAAA) explains the application that includes
the alarm, network and administration functions for the 1350 OMS user. This
document contains a complete explanation of the 1350 OMS information product set
and a glossary of terms that is applicable to the documentation set.
The document explains also the look-and-feel of the 1350 OMS user and
administration GUIs to new users. This document contains a complete explanation of
the 1350 OMS graphical interface applications
2. The Administration Guide explains how to administer and maintain the element
management layer, network management layer, and service management layer of the
1350 OMS.
This document consists of the following volumes:
• The Administration Guide: System Maintenance and Troubleshooting
(8DG43185LAAA) explains how to administer and maintain the common tools
and processes that are associated with the 1350 OMS and with its applications.
• The Administration Guide: Common Functions (8DG43185MAAA) explains how
to administer and maintain the common administration GUIs that are associated
with the 1350 OMS and with its applications.
3. The Platform Guide (8DG43185BAAA) explains how to provision the 1350 OMS
Platform application of the 1350 OMS, which is the element management layer of the
1350 OMS.
4. The OTN Guide (8DG43185QAAA) explains how to provision the 1350 OMS OTN,
which provides theWavelength Division Multiplexing (WDM) and DenseWavelength
Division Multiplexing (DWDM) network management layer for the 1350 OMS. The
1350 OMS OTN Guide includes EML and Service Assurance information for the
1350 OMS OTN application. In addition, the 1350 OMS OTN Guide explains how to
use the OTNWebUI user interface. The 1350 OMS OTN Guide is the companion
document to the 1350 OMS OTN Guide
5. The PKT Guide (8DG43185DAAA) explains how to provision the Packet (PKT)
application of the 1350 OMS, which provides Ethernet network management layer
support for all Alcatel-Lucent NEs, except for the 1830 PSS NEs which are supported
by the 1350 OMS OTN application.
6. The Service Assurance Guide (8DG43185FAAA) explains fault management and
performance monitoring for the entire 1350 OMS and its applications.

Document formats
This document is available for use in HTML format and PDF.
The on-line HTML version of the document has a search capability, a table of contents in
the front matter of the document, a partial table of contents in each chapter, and an index.
The PDF version can be viewed on-line; or it, or portions of it, can be printed locally at
the user's discretion.

On-line help
The 1350 OMS help systems are designed to consider the task that the user is performing
and to help the user complete the task.
Contact sensitive help, which defines many GUI fields, is available; and other types of
help can be accessed from the GUI menu.

Ordering information
The ordering number for this particular document is 8DG43185CAAA. Contact your
local Nokia local customer service support team for details.
In addition, to order the 1350 OMS and/or any of its applications, add-on features or
upgrades, contact your local Nokia local customer service support team.

How to comment
To comment on this document, go to the Online Comment Form (http://infodoc.alcatel-
lucent.com/comments/) or e-mail your comments to the Comments Hotline
(comments@nokia.com).

Overview
Purpose
Part I of the document explains the concepts involved in the ASON management. This
part also explains the configuration of ASON in 1350 OMS

Contents

Chapter 1, ASON Concepts 1-1

Chapter 2, ASON and the 1350 OMS 2-1
Chapter 3, ASON Configuration 3-1
Chapter 4, 1350 OMS ASON Provisioning 4-1

Overview
Purpose
The purpose of this chapter is to introduce the fundamentals of ASON and GMPLS.

Contents

ASON 1-2
ASON/GMPLS Control Plane 1-7
GMPLS Routing Engine 1-15
ASON Architecture Concepts 1-17
ASON Features and Supporting Functionalities 1-19

ASON
Introduction
The Automatic Switched Optical Network (ASON) is both a framework and a technology.
As a framework, ASON depicts a control and management architecture for an automatic
switched optical transport network. As a technology, ASON refers to routing and
signaling protocols applied to an optical network which enable dynamic connection
creation and life cycle management.

Figure 1-1 ASON as a Smart Network

Traditional networks consist of two operating planes: the management plane and the
transport or the data plane. In this architecture, the data plane carries the user data. The
data plane consists of various network equipment, such as interface cards, switching
equipment, and the fiber plant. Network operating information is managed by the
management plane consisting of the Element Management System (EMS), the Network
Management System (NMS), and the Operation Support System (OSS). With the advent
of optical networks, a third operating plane was added. The optical control plane is
located between the management plane and the data plane and helps to move some
network intelligence down to the Network Elements (NE). As a result of adding the
optical control plane, the NEs have access to the overall topology of the network and the
available resources allowing the NEs to participate in the planning, establishment, and
maintaining network services for the end user.

Figure 1-2 Operating planes for an optical transport network

The Control Plane supports the following benefits

• provides much faster and less labor intensive service provisioning.
• provides efficient and cost-effective network restoration.
• Supports new dynamic service provisioning: Reduces time from a Service request to
Service Delivery.
• Network efficiency and resilience – supports mesh topologies and dynamic service
restoration: Network processing and Distribution of restoration improves
Time-To-Repair.
• Reduces OPEX cost - decreasing operator workload, reducing service turn-up fallout,
and supporting multi-vendor inter-operability.

Network
An ASON is an intelligent optical network that can automatically manage the signaling
and routing through the network. Traditionally, it was necessary to configure
cross-connections in the Network Elements (such as an optical switch) to create a new
traffic connection for a customer.
In ASON, this process can be automated. The customer defines a new connection by its
start and end point, the bandwidth needed, the Quality of Service and so on. The Network
Elements have the necessary processing functions built in to configure the new traffic
connection. The connection itself is not specified by the customer. The ASON network
creates a light connection through the network for this customer. This traffic connection is
changed if the network is changed.
ASON uses the Generalized MPLS (GMPLS) signaling protocol to set up and monitor
edge-to-edge transport connections. ASON concentrates on the optical backbone network.
The related ASTN is used in the access networks and metropolitan area networks, so
called city rings.

Control Plane Applications

Most optical control plane applications focus mainly on the services that perform
connection management for the transport plane for both the packet-based services and
connection-based services. The main functions of a control plane are:
• Routing control
• Resources discovery
• Connection management
• Connection restoration
ROUTING CONTROL
The routing control function is responsible for selecting the combination of links to be
used for a given connection, based on the network topology and routing criteria that is
provided. Common route selection criteria are shortest path, lowest cost, fewest hops, and
least congested. This function is triggered by a connection management function request
and utilizes the network topology populated by resource discovery function.
RESOURCE DISCOVERY
The resource discovery function keeps track of the system resource availability such as
bandwidth, multiplexing capability, and ports. It is responsible for the discovery of
neighboring nodes and the links connecting them, and the communication of this
information to all relevant elements. It maintains the neighbor and link information and
updates this in real time. This information enables all the elements of the control plane to
have an accurate topology map of the network to be used for connection management and
routing control functions.

Control Plane Standards

When intelligent optical networks first arrived on the market, every implementation
utilized different control plane architectures, to support varying functions, using
proprietary protocols. Due to the fact that network operators typically included equipment
from multiple suppliers (either by design or acquisition) and suppliers wanted to sell
standards based products globally, work was started to standardize the optical control
plane. There were parallel efforts in multiple standards development organizations and
forums, but the International Telecommunication Union Telecommunications Sector
(ITU-T) first defined a clear architecture and a standardized set of functions for an optical
network.
The optical network with an active control plane between was labeled an Automatically
Switched Optical Network (ASON) and the ASON architecture was defined in ITU-T
Recommendation G.8080/Y.1304 (referred to as G.ASON when it was a draft).

ASON/GMPLS Control Plane

GMPLS is the protocol defined to support a control plane based on the ASON
architecture. Specific capabilities that fit under the ASON architecture are defined for
GMPLS. The fundamental service provided by an ASON/GMPLS control plane is
dynamic end-to-end connection provisioning. The operators need only to specify the
connection parameters and send them to the ingress node. The network control plane can
then determine the best optical connections across the network according to the
parameters and signal the adjacent nodes to establish the connection. ASON/GMPLS will
also function well in today multi- layers optical networks. It can be used for traffic
grooming on edge nodes when applied across a two-layer network.
For example, consider an optical wavelength routed in an optical network and an
optoelectronic multiplexed layer over it. When a transparent light connects in the optical
layer (operating strictly at wavelength granularity) two physically adjacent or distant
nodes, these nodes will seem adjacent to the multiplexing layer. The multiplexing layer
can then multiplex the different traffic streams into a single wavelength-based light
connection. It can also de-multiplex different traffic streams from a single light path. At a
multiplexing node, some of the de-multiplexed traffic can also be re-multiplexed into
different light paths using a GMPLS-based control plane.
GMPLS includes the definition of several forms of labels the generalized labels suitable
to be used with wavelength-based optical networks. These objects include the generalized
label request, the generalized label, the explicit label control, and the protection flag. The
generalized label can be used to represent time slots, wavelengths, wave bands, or
space-division multiplexed positions. In order to set up a light path, GMPLS uses a
signaling protocol to exchange control information among the nodes in the network, to
distribute labels, and to reserve resources along the connection. Signaling protocol to be
used for the GMPLS control plane includes Resource Reservation Protocol (RSVP).
RSVP can be used to reserve a single wavelength for a light path if the wavelength is
known in advance. Open Shortest Path First (OSPF) can be used over GMPLS as a
routing protocol to keep track of link states and select link as requested by users,
management plane, or triggered by control plane functions. GMPLS also uses the Link
Management Protocol (LMP) to communicate proper cross-connect information between
the network elements. LMP runs between adjacent systems for link provisioning and fault
isolation.
In addition to the service-related advantages of using a control plane, the most important
function of a control plane is to provide efficient and cost effective restoration for optical
networks. In view of the current implementation of 40G and 100G systems, restoration
become even most critical for future optical networks. The efficient ASON/GMPLS based
control plane incorporated with the management plane will not only provide new and
better network functions but will also help the carriers explore new revenue streams as
well as save network and operations costs.

Figure 1-3 GMPLS/ASON key features - 1

Figure 1-4 GMPLS/ASON key features - 2

The key features of GMPLS are

• Network and Resource Discovery: Eases the installation and commissioning process
• Dynamic Provisioning: Supports bandwidth-on-demand services & end-to-end
provisioning: Connection set-up triggered through the NMS (soft permanent
connections)

Routing protocols
In general, routing protocols (OSPF-TE with GMPLS extensions) are used to exchange
topology and reachability information between GMRE nodes to allow each node to build
its own topology map of the entire network or subnetwork. A topology map basically
consists of node-related information and link-related information which is then stored in a
topology database.
Each node periodically disseminates node-related information describing the node itself
(local state information). Furthermore, it disseminates link state information describing its
local links (leading to one of its adjacent neighbors). The routing information, a node
periodically receives from each of its neighbors, is used to update its local topology
database, and is further advertised to all other adjacent neighbors. This mechanism
implemented in routing protocols ensures, that each node in the network repeatedly
obtains information describing all the nodes and links in the network so that it is able to
build its own topology map of the entire network or subnetwork.
In the path establishment process, the GMRE node uses this information to calculate a
route from a given source to a given destination or to determine the “next hop” leading
into the direction of the given destination.

Signaling protocols
Signaling protocols (RSVP-TE with GMPLS extensions) are used to exchange
information between neighboring nodes mainly for the purpose of establishing or
releasing a path across the network or subnetwork. Thus, when a new path is being
established, the signaling messages have to be processed in every node along that path.
....................................................................................................................................................................................................................................
Nokia 1350 OMS 1-9
8DG43185XAAA Release 14.0
Issue 2 October 2016
ASON Concepts ASON/GMPLS Control Plane

Link Management Protocol

The Link Management Protocol (LMP) extends between the neighbor NEs and is used to
manage the TE links. Furthermore it supports the supervision of control channel
connectivity and verification of the physical connectivity of the transmission links.

Control Plane Architecture

GMPLS makes no assumptions regarding the control plane architecture. It implicitly
assumes the existence of the routing (OSPF, ISIS), the signaling (RSVP, CR-LDP), and
the LMP controllers. These communicate with their peers and exchange the particular
protocol information performing the tasks of connection control, call/connection control,
and resource discovery. Network state information is contained in MIBs. This information
is partially configured from the management system or updated as a result of automatic
actions performed in the control plane. The architecture of a GMPLS control plane is
inherently protocol-specific. On the other hand, the ASON control plane architecture is
specified in a protocol neutral way. Control Plane functions are modeled by control
components with generic functional interfaces organized in federations. Components can
be configured and monitored, and their behavior can be changed by applying policies.
ASON specifications introduce a set of control components responsible for call control,
connection control, and resource discovery.

Figure 1-5 Mapping between GMPLS/ASON resource models

In addition, the ASON architecture includes specific protocol controller (PC) components
responsible for translating functional primitives defined on the generic interfaces of
control components, into protocol messages of a suitable protocol implementation.
Protocol messages are transported in the control network over the control plane
interfaces.
The ASON protocol neutral control plane architecture enables a generic approach for
defining and understanding requirements and for validating potential solutions. However,
the aim of ITU-T is not to define some new protocols but to incorporate the GMPLS
protocols and other valid candidates in the ASON framework retaining the visibility of
the generic requirements. GMPLS protocols are represented within the protocol control
components as outlined in the Figure 1-6, “ASON control processes and components”
(p. 1-12)..

Figure 1-6 ASON control processes and components

Functional Components and Planes

There are many functional components in the network nodes. This makes it possible to
build a more coherent architectural model, but also makes it easy to understand the roles
that particular networks nodes play and how they communicate.
For example, one functional component has the responsibility for managing network
nodes, and another provides the management support within a network device such as a
router. These components would possibly be positioned at remote sites within the network
(the Network Management Station and the router itself) and communicate with each other
across the network.
When a network is seen partitioned into these functional components, messages and
information move around the network between components with the same, or related,
functional responsibilities. The example of communications between management
components cited in the previous paragraph is one illustration. Similarly, the
data-switching components of network nodes process data and distribute it among
themselves. If we follow up this idea, we see that the network may be sliced into sets of
functional components that communicate with each other and all of which have related
responsibilities. These slices are called planes.

Figure 1-7 Functional interaction between network nodes within a set of planes

Figure 1-7, “Functional interaction between network nodes within a set of planes”
(p. 1-13) depicts simple network divided into the four planes. Data is moved between the
devices within the data plane, so the connectivity in this plane is a direct representation of
the physical data links in the network. The management plane is responsible for all
management activity, such as configuration requests, statistics gathering, diagnostics, and
so forth. The signaling plane and the routing plane are sometimes grouped together and
referred to as control plane. The routing protocols are dynamically distribute connectivity
and reachability information, and the TE resource attributes, operate in the routing plane,
whereas the signaling path exist.
The data plane is also sometimes referred to as the user plane or the transport plane,
because it carries user traffic. Also, some people like to add another plane to their view of
the network. The application plane facilitates communication between applications.
Figure 1-7, “Functional interaction between network nodes within a set of planes”
(p. 1-13) illustrates how a set of five network nodes is connected together in different
ways in each plane. The vertical lines represent the presence of each network node across
all the planes. The dotted lines represent the communication relationship within each
plane. In the data plane, the communication services map to the actual physical

GMPLS Routing Engine

Introduction
Each transport NE (TNE) is equipped with a controller called GMRE which runs the
GMPLS protocols. The GMRE is a software package which can be activated on the basic
NE software on the Controller card ( First-Level Controller (FLC) in case of 1830 OCS,
Equipment Controller (EC) in case of 1830 WDM). No additional hardware is required
for the implementation of the GMRE.

Figure 1-8 GMRE top-level architecture

GMRE Architecture
The basic elements of the ASON networks are the GMRE nodes. The GMRE nodes are
designed to implement the GMPLS architecture.
In the GMRE nodes reside a set of processes implementing the control plane (Signaling,
Routing, link and path management). Those processes interact with the NE MIB trough a
specific interface and with the Management Plane through a dedicated interface. The
Management Plane is represented by the NMS or a simple user command line interface
(CLI).
GMRE is capable of establishing as soft-permanent connections (SPCs) between TTPs.
For more information on GMRE architecture, see 1830 PSS GMPLS/GMRE Guide.

ASON Architecture Concepts

ITU Key ASON Architecture Requirements
The ITU ASON requirements can be summarized :
• Supports heterogeneous network topologies, technologies, and applications.
• Supports control plane-based or management plane-based subnetworks.
• Provides boundaries of policy and information sharing.
• Supports varying trust relationships among users and providers.
• Provides functional independence between control plane, data plane, and the
management plane.

Figure 1-9 ASON Architecture Requirements

Key ASON Architecture Concepts

• Call/connection control: The call is a service activation mechanism in control plane
and may be associated with 0, 1 or more connections in the transport plane. It states
the level of service required (for example, QoS, protection, and so on). Calls does not
provision any network resources to carry data for the service. The connection(s) carry
the requested services in the transport plane.
• Networks are partitioned into domains by network operator policies.
• Service demarcation and reference points are defined within and between the
domains, and between a provider network and a user/client.
• A control channel (CC) is a communication connection in a DCN supporting
exchange of control plane protocol messages.

Figure 1-10 Key ASON Architecture

ASON Features and Supporting Functionalities

1830 PSS-24Xcard support
The 1830 PSS-24x is capable to receive, evaluate, execute, and acknowledge all
operations and status retrievals by the main shelf’s system controller. 1830 PSS-24x
provides alarm and performance monitoring data on status change spontaneously and
allows maintenance operation either remotely from the main shelf or locally at related
connectors for debug console access.
1830 PSS-24x is a new shelf of PSS-PHN (PSS32/16 NE type) with OTN switching
features. The 1830 PSS-24X can be included in compound 1830 PSS PHN/1830 PSS
OCS node configuration. GMRE supports interworking L1 with Uplink in PSS24X shelf
and MUX in PSS32 main shelf in case of single NE.There is no internal protocol between
PSS24X and PSS32 as for OCS-PHN compound.
The service types can be (unprotected, SBR, GR (Guaranteed) , PRC, SNCP)
The direct OPS connection in uplinks card between 2UC400 or 4UC400 logical links get
auto generated and these logical links are added to ASON domain or NPA.
2UC400 card support
2UC400 is a PSS-24X 100G/200G Two Port Uplink card with single slot and full height
supporting Uplink card configurable for 100G QPSK/SPQPSK or 200G 8QAM/16QAM
modes.
2UC400 is supported for managed-plane and L1 GMPLS. The card can be used as drop
port for L1 GMPLS domain. In such scenarios, if 2UC400 is used at 200G mode (if IW
with a 260SCX2/D5X500), both ODU4 transported by OTU4x2 must be managed as
drop ports.
User has to add L1 Logical links 1 and 2 to ASON independently each time. When both
the logical links are added to ASON, they are (as usual) bundled in the same TE-Link
based on the same Costs and SRGs. Set up a L1 ODU Infrastructure. If it is ASON routed
involving the board, ASON SNCs are created on top of L1 Logical Links.
4UC400 card support
4UC400 is an Uplink card for the PSS-24X shelf that is introduced in PSS R9.0. It is a
100G four Port Uplink card, with single slot and full height, supporting Uplink card
configurable for 100G QPSK mode
4UC400 is four times the 130SCUP - one OCH, one OTU one ODU4. The board is
managed as 130SCUP. The board supports both SDFEC-G2 and AFEC.

D5X500 card support

The D5X500 has to be supported in Managed plane and L0 Control Plane (PSS-8, PSS
16, PSS32) configurations. The D5X500 is used as a transponder.
The L0 mode is supported by GMRE for D5X500 in 200G mode.
Both L0 and MRN modes are supported by GMRE for 100G modes.
ASON is able to route SNC originated on D5X500 with 62.5GHz width (8QAM and
SP-QPSK encoding) across flex-grid Nodes and to terminate on flex-grid add/drop
Nodes.

OPSA Protection
OPSA protection is managed by GMRE and 1350 OMS as a PRC configuration.
The user must verify the management of OPSA protection inside L0 GMPLS network.
• supports PRC protection or restoration provisioning for all supported network
scenarios.
• supports PRC protection schema with/without more of one 3R in the same
connection.
• supports the allocation via automatic routing or via manual routing. With automatic
routing, the 3R has to be used only if there are not alternative paths without 3R.
• Define and specify 3R

96 optical OCH channel support

A4PSWG and ASWG packs supports 96 optical OCH channels in CDC-F configuration,
as compared to the 88 optical channels.
The OMS supports the DWDM networks formed by the PSS-32 NEs with 96 optical
channels per OTS line. The configurations are CDC-F (ROADM, ILA and DGEs) with
100G optical channels, add/drop via 260SCX2 or 130SNX10 OTs. The 130SNX10 OT
can cascade 11QPA4, 11DPM12, or 12P120 to support 10G client unprotected or
protected (Y-Cable, ESNCP) service. The HO-OTU4 DWDM line management is under
Layer 0 Control Plane.
For more details, see “View 96 OCH Channel Support in Different Windows of OTN
WebUI” (p. 6-12).
The following scenarios are supports 96 optical channels per OTS line:

Figure 1-11 Network Configuration

Figure 1-12 3 260SCX2 (100G Mode) with OPSB – 96 OCH Channels

Figure 1-14 5 11DPM12 Cascading 130SNX10 with Y-cable – 96 OCH Channels

Figure 1-15 Figure 6 12P120 Cascading 130SNX10 with Y-cable – 96 OCH Channels

Overview
Purpose
This chapter provides an overview of ASON and technologies associated to ASON.

Contents

ASON Overview in 1350 OMS 2-2

ASON Concepts applied in 1350 OMS 2-3
ASON Connection Setup 2-12
ASON Protection and Restoration 2-14
Network Backbone Setup 2-18

ASON Overview in 1350 OMS

ASON, which is an Automatically Switched Optical Network, is a network that can
automatically manage the signalling and routing of a connection through an optical (for a
GMRE Level 0 Control Plane) or electrical (for a GMRE Level 1 Control Plane) network
without input from a user or a management system, which is an important function if a
failure occurs within the network. If a failure does occur within the network, service is
quickly restored by using the spare capacity that is already available in the network;
therefore, minimizing the amount of protection capacity that is needed in the network.
ASON relies on Generalized Multiprotocol Label Switching, or the GMPLS protocol, to
reroute traffic dynamically around a failure. Once the failure in the network is repaired,
the connection is returned to its original route automatically or upon demand depending
on the connection settings.
If the equipped is with a Generic MPLS (Multi-Protocol Label Switching) Routing Engine
(GMRE) module, the 1830 PSS NEs have the necessary processing functions to
acknowledge the GMPLS protocols for the signalling, path management and the link
management that are needed to create ASON.
The 1350 OMS is able to manage distributed restoration network defining a network
protection architecture (NPA) of type ASON, the NE available with control plane (CP)
are 1678Mcc, 1830 PSS 32, 1626LM R6.x, and 1830 PSS-64/36. All the NEs are not
managed in the same way.
The Control Plane is discovered during the NE upload and a specific object, with a
specific icon, is associated to the node. The status of reachability, management of control
plane alarms, visible attributes in the proprieties, the navigation towards the Control Plane
and the CLI are the salient features of ASON.

ASON Concepts applied in 1350 OMS

Control Plane
ASON GMRE supports photonic switching (L0) and electrical (L1) switching. In 1350
OMS ASON domain is represented by the NPA.

Figure 2-1 Work Split between OMS and Control Plane

These physical links represent in 1350 OMS the links of inter-working between the two
managers for the ASON SNC routed in ASON domain. The port at the end of the drop
link and I-NNI link and belonging to the shared NE represents the shared port.
The TPs on a shared port can either be completely managed by the 1350 OMS or
managed by both the 1350 OMS and the GMRE, according to the routing of the ASON
SNC involving the TP.
Both managers operates on the TP: 1350 OMS is in charge of all the normal operations on
the TP, apart from the set up of the cross-connection, set up by GMREs, and dynamically
changed according to GMRE's restoration strategies.
Physical links and the NEs of the ASON network are represented in the 1350 OMS as
ASON links and the nodes.

....................................................................................................................................................................................................................................
For the user provisioning of a GMRE L0 WDM/photonic connection or a GMRE L1
OCS/electrical switching connection in an 1830 PSS network, the 1350 OMS supports the
following plane domains:
• The Control Plane is the operating plane in which pure ASON connections enable the
network to reroute connections if a failure occurs, provided the NE has the necessary
processing functions to acknowledge the GMPLS protocols for signalling, connection
management, and link management.
With the 1350 OMS, the Control Plane is a generalized term that is used to represent
the portion of the network or a connection that uses ASON/GMPLS. The Pure Control
Plane connections are infrastructure connections that originate and terminate in
ASON.
For GMRE L0 Control Plane provisioning on the 1830 PSS WDM/photonic NEs, the
OTUk is provisioned in parallel by the network when the ODUk provisioning is done.
For GMRE L1 Control Plane provisioning on the 1830 PSS OCS NEs, the base
network is build up until the connectivity between the 1830 PSS OCS network is
established at a rate that supports the ODUk Control Plane layer rate. Any optical
connectivity that is present in the network via 1830 PSS WDM/photonic NEs is
established first to provide connectivity between the 1830 PSS OCS NEs.
For both GMRE L0 and GMRE L1, the overall process of establishing connections
follow the G.709 standard. Each layer rate is established in the network starting with
the physical network. Both ASON layers cannot be active in the network at the same
time; the network is designed to have either GMRE L0 or GMRE L1 active at any
given time. Once the 1350 OMS network is provisioned, connections can be rerouted
depending upon the occurrence of different failure conditions.
The role of 1350 OMS for ASON Networks are as follows:
– Network Setup and Topology configuration (NPA, TE-Links, SRGs).
– Network Configuration : Path Computation and deployment of SPC for the
following:
Connections terminating within the domain (I-NNI links)
Interworking with non-Control Plane networks and seamless management
MRN (Mixed L0/L1) Control plane Connection
– Manage life-cycle of SPC for Operation Maintenance and Bandwidth
Management
Modification of Nominal Route, Switching, and Reversion to Nominal Route
Move traffic
– Planning and Maintenance of Network via Graphical and 360 degree Display of
SPC

Figure 2-2 ASON: Network Reference Points and Connection Types

ASON Domain
A ASON domain represents the set of instances of (distributed) GMPLS Control Planes
(GMREs) working together to automate the resource and connection management,
including the rerouting in case of failure.
An ASON domain is composed of the following:
• Control plane instances (1 GMRE per NE, Two CPs in each PSS Node PHN+OCS)
• Links and aggregation of links = TE-LINKS (see later for details)
• Soft permanent Connectivity (SPC)(ASON SNC part of the e2e connection)

ASON NPA
NPA, which is Network Protection Architecture, is a set of NEs, protections blocks, and
physical links that work together to create a dedicated protection mechanism or are
grouped together to establish service layer protection
The 1350 OMS uses NPA to associate resources that are part of the same protecting
structure. By creating and implementing NPA, users can specify the role of a physical link
and they can assign a reduction cost factor and a usage cost factor to the physical link.

ASON Link
An ASON link represents the connectivity between the NEs that can be used for ASON
routing. In an optical L0 ASON network, the ASON link is equivalent to the OMS layer
rate. In an electrical L1 ASON network, the ASON link represents the OTU layer rate.
The following guidelines apply to ASON links:
• ASON links are established in the OTN and cannot be deleted or rearranged.
• ASON links and link connections of ASON links are not available for use by manual
or automatic routing in OTN.
Users can view ASON links in the Connection list within the OTN Manager by filtering
the Category Column for ASON Links.

Multi-Region Network
Multi-Region/Multi-Layer Network (MRN/MLN) control plane maximizes multi layer
awareness and resource optimization of WDM and ODU layers
Multi-Region Network (MRN) simplifies and harmonizes operations on multiple layers,
providing cross-layer visibility and end-to-end service view across network layers. MRN
increases the service availability by maintaining dis-jointness of primary and spare
resources in multiple layers. MRN recovers quickly by coordinating response to failures,
without mandating hold-off timers for layer de-coupling. MRN avoids traffic hits through
a coordinated sequenced reversion strategy.

Figure 2-3 Multi-Region Network

Connection setup
When the 1350 OMS user sets up a connection crossing (or terminating) in the ASON
domain, the subnetwork connection at the ASON NPA level is created along with the
related cross-connection inside the Nodes.
These cross-connections are marked in such a way that the 1350 OMS does not directly
forward the cross-connection implementation to the NE, but they are provided to the
GMRE with the provisioning of the SPC nominal route (the provisioning of the single
cross-connections to the NE is in charge of GMRE).

Control Plane Domain Object

The controlPlaneDomain class represents the GMRE, that is. the Control Plane instance
contained in the Network Element.
Some important attributes are:
• reachable: indicates the Control Plane communication status.
• userLabel: indicates the user label of the Control Plane
• operationalState, alarmStatus, ...
• emsFactoryAddress: indicates the GMRE Factory IOR for addressing the
GMRE/Control Plane using NMI Corba (not visible on the User Interface)

Control Plane Tandem Connection

A Control Plane Tandem Connection is a connection that appears in the Control Plane
Tandem Connection list. Control Plane Tandem Connections cannot be deleted or
rearranged in OTN. You cannot terminate a Control Plane Tandem Connection, if it is also
a service or trail connection that appear in both the Control Plane Tandem Connection
List and the Service/Trail List in OTN. In the Service/Trail List, the connection has a
category of control plane. Discovered connections/Trail connections cannot be deleted or
rearranged in OTN. An unterminated Control Plane Tandem Connection can be extended
in OTN to create a mixed plane connection. When extended, the connection appears in
both the Control Plane Tandem Connection List and the Service/ Trail List. In the
Service/Trail List, the connection has a category of mixed plane if any NEs in the
extended connection are in the managed domain. If none of the NEs in the extended
connection are in the managed plane, the connection will have a category of control
plane. Two-ended, three-ended, and four-ended control plane tandem connections are
supported. For connections with category of Control Plane, two-ended, three-ended and
four-ended control plane tandem connections are supported. For connections with
category of Mixed Plane, only two ended control plane tandem connections are currently
supported. Therefore, for protected Mixed Plane connections two control plane tandem
connections are chosen, one for the working side and a second for the protection side.

Subnetwork Connection
Some important attributes are:
• userLabel
• sncActiveSt: specifies if the subnetwork Connection has been implemented on the
NEs by the GMRE (not visible on the User Interface).
• rerouting: specifies if the rerouting by the Control Plane is allowed or not.

Network Element
The following attributes are added to the Network Element:
• controlPlaneDomId: it is the Identifier of the Control Plane Domain (not visible on
the User Interface)
• controlPlaneStatus: it identifies the Control Plane status.

Port
The following attributes are added to the port class:
linkType: it identifies the port type inside 1350 OMS. Allowed values:
• 1350 OMS-internal: it is a port of an NE not involved in an ASON NPA (default
value).
• drop: it is a port (without signaling) of an NE belonging to an ASON NPA, connected
to a port of a client device.
• uni-n: it is a port (with signaling) of an NE belonging to an ASON NPA, connected to
a port of a client device.
• i-nni: it is a port of an NE belonging to an ASON NPA, connected to an NNI port of a
neighboring NE belonging to the same ASON NPA.
• e-nni: it is a port of an NE belonging to an ASON NPA, connected to an NNI port of a
neighboring NE belonging to a different ASON NPA.
portNativeName: it identifies the port inside the Control Plane.
remotePort: it identifies the native name of the far-end port.

ASON Connection Setup

Connection setup using the nominal, optimal, and current routes
The initial set up of a connection in ASON involves the establishment of the nominal
route, which is the initial route though the network. For optical connections, the user sets
up the nominal route in conjunction with the Engineering and Planning Tool (EPT) to
establish an optimal route through the network. The nominal route information is sent to
the GMRE module on the 1830 PSS NE for implementation in the network.
The route that a connection takes through the network is known as the current route. In
most cases, the current route and the nominal route are the same. If a failure occurs,
ASON reroutes traffic around the failure automatically and restores service. The current
route follow a path that differs from the nominal route. Once the failure is repaired, the
traffic can be switched back to the nominal route to ensure optimal routing through the
network. The 1350 OMS system stores the details of the nominal route and retrieves the
current route upon demand when needed.
The following figures illustrates how the traffic is rerouted.

Figure 2-4 ASON - ASON Nominal Route and Current Route - 1

Note: The users can rearrange the nominal route of a Control Plane connection in ASON.
When a control plane connection is rearranged, a service disruption on the connection
might occur as cross connects are being taken down and are being re-established, which
causes alarms to occur on both the given connection and the client connections.

Figure 2-6 Network resource optimization

The Nominal Route and Reversion concepts keeps control over the ASON network.

ASON Protection and Restoration

ASON generally uses fewer network resources than ring or other one-to-one protection
schemes or it can be combined with ring protection methods to provide more robust
protection if network survivability is critical to a site. The combine protection method
provides fast recovery through ring protection and also restores the failed portion of the
ring through ASON.
GMPLS protection services that can be established through ASON include unprotected
service, SBR (upon failure), and PRC (through SNCP inside ASON for GMRE L1;
through O-SNCP outside ASON in GMRE L0), and precalculated.

Unprotected Service
With unprotected service, traffic is lost if a fail occurs.

Figure 2-7 ASON – GMPLS Unprotected Service

Source based restoration

With SBR, or Source Base Restoration, the Control Plane protects the traffic if a failure
occurs by calculating a new route.
The following figure illustrates GMPLS SBR.

Figure 2-8 GMPLS Source Based Restoration

In Provisioning, the Nominal Route is computed by NMS.

Guaranteed Restoration
In Guaranteed Restoration (guaranteed restoration), the restoration route is calculated in
the same time of implementation of nominal route.
With Guaranteed Restoration, protection and restoration are used together to optimize
recovery time and to maximize service quality. The Control Plane calculates a restored
route as an alternative to the nominal route (main).

Figure 2-9 Guaranteed Restoration

In provisioning, the Nominal Route is computed by NMS. The backup path that is
calculated and reserved is shared among several active nominal routes.
In restoration, the Backup path is implemented upon failure detection. The backup path is
reserved subsequently.

Protection and Restoration Combined

With PRC, or Protection and Restoration Combined, protection and restoration are used
together to optimize recovery time and to maximize service quality. The Control Plane
calculates a restored route as an alternative to the nominal route (main).
The following figure illustrates GMPLS PRC in an optical network. Note that after the
first failure, an Optical-Subnetwork Connection Protection (O-SNCP) switch occurs in
less than 50ms. The network then calculates a restored route as an alternative to the
nominal route.

Figure 2-10 ASON – GMPLS Protection and Restoration Combined

In Provisioning, the Nominal Route and fully-diverse backup path is computed by the
NMS.
For restoration, the following functionalities are supported:
• on first failure detection, backup path becomes active (tail-end path selection)
• A new, diverse backup path is then computed and activated
• After subsequent failure(s), new services are computed and activated
• Applies to failures on either/both active and backup services
• When available, original nominal route and/or backup path is reinstated by means of
bridge and roll.

Sub Network Connection

Sub Network Connection (SNC) specifies if the subnetwork Connection has been
implemented on the NEs by the GMRE
During provisioning, Nominal Route and fully-diverse backup path is computed by NMS.

During restoration, following functions are available:

• On failure detection, backup path becomes active (via tail-end path selection)
• Reversion to original nominal route upon failure resolution
• Backup path remains implemented and active

Network Backbone Setup

Overview
To reroute traffic successfully if a failure occurs, the network needs additional
information that is supplied by the establishment of Shared Risk Groups (SRGs) and a
Network Protection Architecture (NPA) for the network.
An SRG is a user-defined group of associated physical links and, in some cases, logical
links that represent a common failure point, such as a conduit.
The establishment of proper SRGs in a network is important because a primary and
backup connection is not set up through the same failure points, even though they may be
using different fibers. (A failure point can be a shared conduit or other such physical
structure.) If multiple fibers share the same conduit, they can all share a common failure
point and they can also all be affected if the conduit is damaged or destroyed. Because an
SRG contains the physical connections that use the same physical plan, ASON uses SRG
information to reroute traffic to ensure that the rerouted traffic avoids the failure point.
Example:
If two fibers pass through the same conduit, they would be grouped in the same SRG. If a
failure occurs on the conduit, all the traffic is rerouted around the fibers that are assigned
to that SRG.
The following figure illustrates a physical depiction of a network on the left and a logical
depiction of a network on the right. With the physical network (left), rerouting procedures
require the knowledge of the physical aspects of the network to avoid shared risks and
localized faults. The physical links share the same pipe. With the logical network (on the
right), the network management system requires a logical view of the network to route
traffic. If the pipe is broken, both the physical connections are down. Both the physical
and logical networks share the same SRG.

Figure 2-11 ASON SRGs

ASON also relies on the information supplied by the NPA. The NPA is a set of NEs,
protections blocks, and physical connections that work together to create a dedicated
protection mechanism or are grouped together to establish path layer protection. The
NPAs are used by the 1350 OMS to associate resources that are part of the same
protecting structure. By creating and implementing an ASON NPA, the users can specify
the role of the physical connection and they can assign a reduction cost factor and a usage
cost factor to the physical connection.

Shared Risk Group (SRG)

Shared Risk Group (SRG) is a group of elements that share a common risk, and whose
failure can cause the failure of all the elements in the group. The purpose of SRG is to
provide a redundant route through the network for an existing route avoiding that the
same problem, for example a link failure, disturbs both the routes.
SRGs are identified by means of SRG values that need to be unique within a GMRE
domain One or more SRG identifiers have to be assigned to the TE links in the GMRE
domain network that share at least one risk. An SRG attribute can be empty, can comprise
a single SRG identifier, or comprises a list of multiple SRG identifiers in case the entity is
vulnerable to a number of different failures. Two or more connections are fully SRG
diverse, if the intersection of their SRG attributes is empty, that is, if the respective
connections do not have any SRG values in common.
A single Optical Physical link may belong to several SRGs in different sections. Routing
algorithms for nominal and pre-planned restoration avoids common risks between main,
spare, or planned backup.
....................................................................................................................................................................................................................................
Nokia 1350 OMS 2-19
8DG43185XAAA Release 14.0
Issue 2 October 2016
ASON and the 1350 OMS Network Backbone Setup

Figure 2-12 Shared Risk Group

Latency
Latency is a configurable attribute for constraint-based routing.
Latency must be configured manually and is not measured automatically.
End-to-end latency threshold
The source node of a control plane service maintains a configurable latency constraint per
service, which specifies an end-to-end latency threshold in microseconds that is not
exceeded by any of the actual path(s) of the service and, in case of a GR service, is not
exceeded by the backup path. An end-to-end latency threshold of 0 means that the latency
is not used for constraint-based routing.
TE link latency
The TE link latency is a configurable attribute that specifies the latency costs in
microseconds associated to a TE link.
Access link latency
If an end-to-end latency threshold is specified, then the source node of a control plane
service maintains an access link latency value in microseconds representing the latency
caused by the drop ports at the source and destination node.
Calculated latency
The source node of a control plane service maintains a calculated latency per actual path,
which is the sum of the TE link latency plus the access link latency of the service.

Color
The color values associated to a logical I-NNI link are the union of a propagated set of
color values and a user-defined set of color values.
....................................................................................................................................................................................................................................
2-20 Nokia 1350 OMS
8DG43185XAAA Release 14.0
Issue 2 October 2016
ASON and the 1350 OMS Network Backbone Setup

Cost
The cost value of a logical I-NNI link is propagated (inherited) from the underlying
physical I-NNI links as the sum of all cost values of the underlying physical I-NNI links
minus 1, according to the actual route of the LSP.
In addition, there are the following configuration options
• The propagated cost value can be overwritten by a manually provisioned value. The
manually provisioned value is valid for the link irrespective of any route changes
occurring on the underlying tunnel service.
• A manually provisioned cost value can be invalidated. Then, the propagated value
becomes valid and is updated based on any route changes occurring on the underlying
tunnel service.

Overview
Purpose
This chapter describes the ASON configuration in 1350 OMS.

Contents

ASON Configuration Flow 3-2

Macro-steps for ASON Configuration 3-5
Network Construction 3-8
Bundling rule 3-11
High Level Provisioning Flow for Layer 0 GMRE 3-12
High Level Provisioning Flow for Layer 1 GMRE 3-18

ASON Configuration Flow

ASON has been represented in electrical or Photonic environment as a specific Network
Protection Architecture that offers GMPLS restoration.
In traditional networks, services are provided connecting a chain of subnetwork
connections. In ASON, the control over OTN is signal-based. Signal is distributed
through a distributed Control Plane.

Figure 3-1 ASON configuration flow

Macro-steps for ASON Configuration

When to use
Use this task to configure ASON.

Related information
To manage a restoration network, the NPA has to be defined and the links of GMPLS
domain have to be assigned to the NPA so that the NEs are inserted in the GMPLS
domain in an automatic way. The NEs and the links have been uploaded automatically by
NPR module and the commissioning has been done on the NE (for only WDM NE). The
NPA can be defined or implemented. During the implementation phase, the TE-Link,
data-bearers, SRGs, and costs are automatically created on the NE.
The TE-Links are the links in the GMPLS domain, In a electrical restoration network, the
TE-Link represents one or more physical links with the same extremities and same rate;
whereas in photonic GMPLS the TE-Link is in relation with the OMS trail (ASON link).
The SRG defines the risk linked to the connectivity. The 1350 OMS provides a specific
wizard to create or remove the SRG and different types of SRGs are managed by the
system.
Using the modification wizard of the TE-Link, the SRG and cost can be assigned to
TE-Link. The SRG and cost are needed to do the routing.
After the NPA implementation, the TE-Links are in Locked state. In this state, the links
cannot be used by the GMRE and the traffic does not flow in Locked state. To activate all
the links in the NPA, all the TE-Links have to be changed to Unlocked state. The Lock
state can be used for maintenance purpose.

See Chapter 5, “1350 OMS ASON WebUI ”.

Task
Complete the following steps to configure ASON.
...................................................................................................................................................................................................

1 Network construction. Create the physical network in 1350 OMS System:

• Create the Network Elements.
• Synchronize EML domains to upload ports.
• Create, upload, and implement drop link and I-NNI physical connections.
• Modify the allocation cost of the physical connections.
See “Network Construction” (p. 3-8).
...................................................................................................................................................................................................

2 Shared Risk Groups (SRGs) management. Assign dependencies relevant for routing in
1350 OMS:
• Create SRGs.
• Correlate physical connections to SRGs.
For Shared Risk Groups (SRGs) management, see “Operate - Network Profiles - Shared
Risk Group” (p. 6-117).
...................................................................................................................................................................................................

3 ASON NPA (Network Protection Architecture) management. Define the ASON NPA.
Implement ASON NPA:
• Create and implement ASON NPA.
• TE-Links are automatically created.
To create and implement ASON NPA,
• see “Create an NPA” (p. 6-27)
• see “Add and Remove Links in ASON” (p. 6-29).
• see “Change ASON WTR” (p. 6-50).
• “Assign an ASON I-NNI Link to a TE Link and/or an SRG” (p. 6-43).
...................................................................................................................................................................................................

4 Physical connection management. Make the physical connections usable for GMRE:
• Unlock drop link and I-NNI physical connections
Afterwards connections crossing the ASON can be created from 1350 OMS

Network Construction
When to use
Use this task to create all network topological objects.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”.

Before you begin

This task does not have any preconditions.

Task
Complete the following steps to create all network topological objects.
...................................................................................................................................................................................................

1 From the 1350 OMS OTN WebUI main menu bar, select Operate > Network Map.
Result: The system displays the OTN Network Map window.
...................................................................................................................................................................................................

2 Select the root map in the left tree, right-click, and select Create Subnetwork.

Figure 3-2 Create subnetwork menu

3 In the Subnetwork Name field, enter the value and click OK.

Figure 3-3 Create subnetwork window

...................................................................................................................................................................................................

4 Create all the required NEs. From the 1350 OMS OTN WebUI menu, follow the path
Operate > Nodes.
Result: The system displays a data table that lists all of the nodes.
...................................................................................................................................................................................................

5 Mouse over the icons on the top right and click the Add Node icon.
Result: The Add Node/NE window is displayed.
...................................................................................................................................................................................................

6 Enter the relevant attributes and click the Create button.

...................................................................................................................................................................................................

7 To assign the NE to the Subnetwork from the Subnetwork issue, select Operate >
Network Map.
...................................................................................................................................................................................................

8 Open the subnetwork to which you want to add the node or NE.
In the Staging Area of the Network Map, identify the node or NE that you add to the
opened subnetwork and drag the node or NE into the subnetwork.
Result: The node or NE is added to the subnetwork.
...................................................................................................................................................................................................

9 From the WebUI menu bar, follow the path Operate > Physical Connection.

10 Mouse over the icons on the top right and click the Create icon.
...................................................................................................................................................................................................

11 Create a OTN physical connection and Deploy.

E...................................................................................................................................................................................................
N D O F S T E P S

Bundling rule
Bundling rule definition
When an ASON NPA is built, the related TE-Links are automatically created in the 1350
OMS and in the involved GMREs.
The creation of the TE-Links is based on the following:
• Defined SRGs
• Bundling rule with the same risks and cost: The physical connections having the same
type, cost, protection, and belonging to the same Shared Risk Groups are grouped in
the same TE-Link.
The user labels of the TE-Links are automatically created by 1350 OMS and forwarded to
the GMREs.

High Level Provisioning Flow for Layer 0 GMRE

Layer 0 GMRE Provisioning Flow
The Layer 0 GMRE is a Control Plane network at the ODUk layer rate supported by the
1830 PSS WDM/photonic NEs. The overall process of establishing connections follows
the G.709 standard. Each layer rate is established in the network starting with the physical
network
Prerequisite
The high-level provisioning flow for Level 0 GMRE is as follows
• Physical connection creation occurs within the optical network.
All required external or internal OTS or OS physical connections are typically auto
discovered by the system. If they are not auto discovered, they can be created by the
user. The physical connections are both external (between NEs) and internal (within
an NE). Typically, both are automatically discovered through notifications from the
NE or when a synchronization is initiated with the NE.
• The OMS layer is created.
The OMS layer Rate is automatically discovered by the system.
Once the physical connections are created, the OTN Manager automatically discovers
the OMS layer rate and makes this connection layer available to the ASON Manager.
For L0 optical connections, the ASON Manager uses the OMS layer rate to provision
the OTU or ODU Control Plane connections.
• ASON Manager takes control of the OMS layer rate
The ASON Manager takes control of the OMS layer rate when the user assigns the
OMS to an NPA. The ASON Manager creates a separate connection, called an ASON
link, once the NPA assignment is made. The ASON links carry the ASON
connections.
User provisioning includes the following steps
– Users must assign the OMS connection to the NPA in the ASON Manager.
For optical provisioning, the OMS layer rate is shared with the ASON Manger so
that the ASON Manager has knowledge of the connectivity between the NEs.
When the user assigns the OMS to an NPA, the ASON Manager notifies the OTN
Manager so that the OMS layer is not used to support Managed Plane
connections, which reserves the OMS for Control Plane connections. In the OTN
Manager, the connection is changed to a category of ASON link, indicating that it
is in use by the ASON Manager.
– Users must make SRG assignments and associate connections with TE links
within the ASON Manager.

....................................................................................................................................................................................................................................
An SRG represents a group of connections that all pass through the same physical
failure points in the network. The establishment of proper SRGs in the network is
important so that a primary and backup connection are not set up through the same
failure points, even though they may be utilizing different fibers. A failure point
may be a shared conduit or other such physical structure.
• Provisioning the Control Plane ODUk connection
Users can provision the ODUk nominal route through the network using the ASON
links (OMS layer rate) as servers. When implemented in the network, the ODUk and
the OTUk connections are set up in tandem. The OTN Manager tracks the OTUk
nominal route.
When the ODUk is provisioned, GMRE automatically creates OTUk connections. (As
the ODUk is created in the ASON network, the OTUk servers are created in parallel.
Both layer rates are therefore created at the same time.) The ASON Manager
establishes a nominal route in the network. The OTN Manager maintains the OTUk
nominal route information and provides access to the current route on demand.
This nominal route through the 1830 PSS OCS NE network can contain one of the
following ODUk connection types:
– For an HO-ODUk terminated connection, an HO-ODUk connection is created and
the DSR client of the connection is automatically discovered and inventoried in
the OTN Manager.
– For a LO-ODUk terminated connection, an LO-ODUk connection is created and
the ODUk is terminated within the Control Plane (entirely in the ASON domain).
The three connections that are generated, which are LO-ODUk, HOODUk, and
OTUk, are all shared with and inventoried by the OTN Manager
– For a LO-ODUk un-terminated connection, an LO-ODUk connection is created
and is it not terminated; meaning, it extends beyond the Control Plane into the
Managed Plane. If the extension is to an NE that is managed by the 1350 OMS,
the OTN Manager then extends the connection to the next managed object. This
connection is then classified as a mixed plane connection and is locked so the
ASON Manager cannot delete the connection until the connection is free. When
the LO-ODUk mixed plane connection is created, the system automatically
discovers the DSR client on the LO-ODUk
Because the OTN Manager maintains the OTUk nominal route information, the
OTUk/ODUk connections are now visible to the user on the OTN connection list,
which they can access via the OTN path. In addition, the OTUk/ODUk
connections are now visible to the user on the Control Plane Tandem Connections
list.
• The Managed Plane connection is established
When the DSR connection is discovered, users can then use the OTN path to make
any needed changes to the LO-ODUk/DSR path connection in the Managed Plane
using the optical ODUk Control Plane connection.
....................................................................................................................................................................................................................................
Nokia 1350 OMS 3-13
8DG43185XAAA Release 14.0
Issue 2 October 2016
ASON Configuration High Level Provisioning Flow for Layer 0 GMRE

Figure 3-4 High level provisioning flow for Layer 0 GMRE

High Level Provisioning Flow for Layer 1 GMRE

Layer 1 GMRE Provisioning Flow
The Layer 1 GMRE is a Control Plane network at the ODUk layer rate that is supported
by the 1830 PSS OCS NEs. The overall process of establishing connections follows the
G.709 standard. Each layer rate is established in the network starting with the physical
connectivity. The base network is build up until the connectivity between the 1830 PSS
OCS network is established at a rate that supports the ODUk Control Plane layer rate. The
optical network connectivity, if it is present in the network via 1830 PSS WDM/photonic
NEs, is also established first to provide connectivity between the 1830 PSS OCS NEs.
The high-level provisioning flow for Level 1 GMRE is as follows:
1. Physical connection creation occurs within the optical network
All required OTS or OS physical connections are typically discovered by the 1350
OMS;. If they are not discovered, they can be created by the user. The physical
connections are both external (between NEs) and internal (within an NE). Typically,
both are automatically discovered through notifications from the NE or when a
synchronization is initiated with the NE.
All internal and external physical connections are established in the system
2. The OMS layer is created
The OMS layer rate is automatically discovered by the system
Once the physical connections are created, the OTN Manager automatically discovers
the OMS layer rate and makes this connection layer available to the ASON Manager.
3. ODU L-OPC is provisioned in case of server photonic network between OCS.
4. L-OPC assignments are made to the NPA and SRG.
User provisioning includes the following steps:
• The L-OPC connection can be assigned to the ASON Manager for use to perform
ASON connections, which is done by assigning the connection to an NPA within
the ASON Manager. The ASON Manager creates a separate connection, called an
ASON link after the NPA assignment is made. The ASON link carries the ASON
connections.
Once a connection has been assigned to an NPA, the ASON Manager notifies the
OTN Manager that the connection supports Control Plane traffic and can no
longer be used to support Managed Plane connections. The OTN Manager tracks
and lists the connections that are being used by the ASON Manager by labeling
them as ASON logical links.

Overview
Purpose
This chapter contains the information that the users need to understand to provision the
1350 OMS ASON application of the 1350 OMS.

Contents

Connections 4-3
Connection Definition, Creation, and Categorization 4-3
Connection Auto Discovery and User Creation of Connections 4-7
Infrastructure Connections and Services 4-10
Client/Server Relationships 4-15
Create an OTN Physical Connection 4-16
Modify the Allocation Cost of a Physical Connection 4-38
Modify the Parameters of an Infrastructure Connection or Service 4-40
Connections Features 4-42
Single Step Provisioning 4-42
Modify the Route (Reroute) of a Connection 4-45
Auto Payload 4-51
Auto Creation of Edge Connections 4-56
Unterminated OTUk/ODUk Infrastructures without Virtual Termination 4-58
Management
Y-Cable Protection for Services 4-64
SNC Protection for 1830 PSS OCS NEs 4-69
OPSB Protection 4-72

Nodes and Network Elements 4-75

Add a Node/NE 4-75
Synchronize Nodes and NEs 4-88

Connections

Connection Definition, Creation, and Categorization

Connection Definition
Connection is a generic term that is used to define any electrical or optical connectivity
between the NEs.

Methods of Connection Creation in the System

Connections can be created in, or added to, the management system in the following
ways, depending on the nature of the connection:
• Without any user intervention, the management system can automatically add
connections to the system during certain system events; these connections are said to
be automatically added or discovered.
• Users can provision certain connections in the management system on the GUI; these
connections are said to be manually provisioned; and the parameters that describe
these connections are said to be user-defined.
See “Connection Categorization” (p. 4-3).

Connection Categorization
Connections in the 1350 OMS OTN environment can be categorized as the following,
depending on the user or system interaction:
• Physical connections are connections that use wires, cables, or optical fibers to
connect two physical ports in a network. Physical connections are automatically
discovered or user-defined connections that users can manually provision. See
“Physical Connections” (p. 4-3) for details.
• Logical connections are client connections that ride on any other server, including
physical connections. See “Logical Connections” (p. 4-4) for details.
• Link connections are connections that the system automatically adds or deletes during
certain system events. See “Link Connections” (p. 4-5) for details.
• Tandem connections are partial connections that are initially built in one application
and are completed in another application. See “Tandem Connections” (p. 4-5) for
details.

Physical Connections
A physical connection is a connection that uses wires, cables, or optical fibers to connect
two physical ports in a network.

Logical Connections
Logical connections are client connections that ride on any other server, including the
physical connections.
A logical connection is typically created between the photonic NEs. It spans more than
one photonic NE that is carrying one or more (that is, Mux OTs) client signals that are
converted into a single wavelength (or frequency) or multiple wavelengths, with each
carrying one or more client signals. These logical connections, which are also referred to
as optical logical layers, are established logically by the receipt and the acknowledgment
of commands to the optical devices to connect the ports internally.
Logical connections, which can be automatically discovered connections or user-defined
connections, are either infrastructure connections or services.
User-defined paths and trails
A service is a connection between the boundary ports of a service provider network that
provides service to an end-user or the customer of the network. A path connects the
logical ports that are entirely used to carry a unique service, which is specified by the
Service Rate Type and Service Rate connection parameters.
A trail is a connection between the interior ports of a network that is used as a server
connection for other connections (either path connections or other trails.) A trail connects
logical ports that are adapted connections with one or more types of link connections.
Services and trails have most of the same characteristics, except for supported service rate
types, service rates, and connection rates.
In addition, services and trails differ regarding the client and server connections. A client
is an object that uses a service of another object; whereas a server is an object that
provides a service to another object. Services do not have client connections. Trails can
create client link connections, that is, they can carry clients.
The users can create and modify the parameters of services and trails; The users can also
view the attributes of services and trails.

Figure 4-1 Link Connection Example

Link connections are automatically added to the management system when a service
connection or a physical connection moves to the commissioned order step. When either
of the event occurs, a link connection is automatically created and added to the database
without any user intervention. Users cannot manually add any link connections.
During the add link connections process, only link connection states of Available and
Connected are displayed if the Show All Link Connections option is set to No.
Link connections are automatically deleted from the management system when their
server connection is deleted. When this event occurs, the management system
automatically deletes the link connection and deletes it from the database without any
user intervention. Users cannot manually delete any link connection.

Tandem Connections
Tandem connections are partial connections that are initially built in one application and
are completed in another application.
Example:
....................................................................................................................................................................................................................................
Nokia 1350 OMS 4-5
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS ASON Provisioning Connection Definition, Creation, and Categorization
Connections
....................................................................................................................................................................................................................................
A mixed plane connection has a control plane portion that is established in the ASON
manager and a managed plane portion that is managed by OTN Manager. Both the ASON
Manager and the OTN Manager are responsible for notifying and discovering necessary
connections, providing routes, and sharing the list information.
The ASON Manager creates the Level 1 GMRE connection first and makes it available to
the OTN Manager as a control plane tandem connection. The OTN Manager then extends
the connection to an end-to-end mixed plane connection. For examples of provisioning
flows involving tandem connections, see “Control Plane Tandem Connection ” (p. 2-10).

Connections linked by client and server relationships

The transmission network is layered, and connections are linked to each other through
client/server relationships. A client is an object that uses a service of another object. A
server is an object that provides a service to another object.
The client/server relationships of the various connection types are as follows:
• Trails can have other trails or services as clients, and trails can have other trails or
physical connections as servers.
When the users access a trail (either from a Connection list or from other windows,
such as the Routing Display), the system provides users with the access to the
following:
– To the list of trail server connections; that is, the connections that are serving this
connection (trails or physical connections depending on the selected trail position
in the hierarchy.)
– To the list of clients that are served by the trail (trails and paths).
– To the list of service that are served by the trail (both direct clients and indirect
clients).
• Services can never have clients, but have servers.
When accessing a path, the system provides users with the access to the servers of the
selected path, which are its trails.
• Physical connections can never have servers; they can only have clients.
When accessing a physical network connection, the system provides the users with
the access to the clients of the selected connection, which are its trails.

Connection Auto Discovery and User Creation of Connections

Physical connection types that are automatically discovered
The 1350 OMS automatically discovers two types of external physical connections during
its subnetwork discovery process. Users cannot manually provision these connections
through the GUI.
The following types of physical connections are automatically discovered:
• An External Optical Section (OS) is a physical connection that involves two different
NEs.
External OS connections are one of the following types:
– Type A is a physical connection between the TDM NE OC-n port and the 1350
OMS OTN OM/OD port.
– Type B is a physical connection between the TDM NE OC-n port and the 1350
OMS OTN OT client side port.
– Type C is a physical connection between the TDM NE OC-n port and the 1350
OMS OTN OT OP1P1 client side port.
• An External Optical Transmission Section (OTS), or an OTS, is a physical fiber
bidirectional connection between the two high speed lines of photonic NEs, which
consists of two unidirectional fibers making up a bidirectional connection.

Physical connections that are automatically discovered or user defined

An internal link is a physical fiber connection that is provisioned within the NE and is
established as a bidirectional connection either automatically by the NE when it detects a
valid signal, or explicitly through a TL1 command.
These internal links either can be discovered or they can be user-defined; meaning, if they
are not automatically discovered, users can explicitly provision them or create them
during OTU trail connection provisioning.
Internal links are one of the following:
• Internal OS, Type A is a physical connection between the line side port of an OT and
an OM/OD circuit pack. Internal OS, Type A connections are discovered through a
database synchronization or are automatically provisioned during OCH connection
provisioning. OS Type A connections can be manually provisioned.
• Internal OS, Type B is a physical connection between the line side port of an OP1P1
(protection) circuit pack and the client side of an OT.

Automatic discovery of connections

The automatic discovery of physical connections occurs during the subnetwork discovery
process.

Automatic discovery of clients

The system automatically attempts to discover client connections whenever a new OS rate
physical connection is provisioned in the system. When an OS connection is successfully
provisioned, the system automatically attempts to discover if that connection completes
any new OCH, OTUk, and/or ODUk rate connections. If the system successfully
discovers a new valid connection at any of these rates, it adds it to the database.

Automatic discovery of OS connections and OPSB protection

When a DSR or ODUk path connection is created with OPSB protection, the system
automatically creates the OS connections between the following:
• The working ports on the OPSB circuit packs and the OTU client ports.
• The OS connections between the Protected Ports on the OPSB circuit packs and the
OTU client ports.
The DSR or the ODUk connections remains in the Defined order step until all OS
connections reach the commissioned order step.
Note: Digital Service Rate (DSR) is a term that is used generically to represent the
service rate of a connection that is being provisioned. When provisioning the service path,
users must select the actual Service Rate of the connection in order for the connection to
be implemented.

Automatic discovery of LO-ODUk and DSR connections

Whenever a HO-ODUk connection is successfully provisioned and in the Implemented
state, the system automatically discovers any LO-ODUk and DSR connections if
LO-ODUk cross connections exist between a client port on an I/O card on the 1830
PSS-32S shelf and the virtual plane. If the system successfully creates a new valid
connection at the ODUk or DSR rate, that connection is automatically added to the
database.

Infrastructure Connections and Services

Infrastructure connections
An infrastructure is a connection that acts as a hierarchical server layer to carry customer
services. Infrastructure connections, which can be unterminated or terminated
connections, are categorized on the OTNWebUI (and are also known) as trails and logical
links.
Provisioning Note: During template-based infrastructure provisioning, users must
specify whether the infrastructure connection is a trail or a logical link.

Infrastructure services — trails

An infrastructure trail is a terminated entity that can multiplex or demultiplex client
signals. An infrastructure trail connects the interior, logical network ports that are adapted
connections with one or more types of link connections.
An infrastructure trail can consist of a hierarchy of trails according to the OTN layered
model per ITU-T G.709 standard. It is used as a server connection for other connections
(either service paths or other infrastructure trails).

Infrastructure services — logical links

A logical link is an unterminated entity that provides contiguous, fixed connectivity to the
far end, which can be terminated or unterminated. services

Services
Services are also known as paths. A service is a connection between the boundary ports of
a service provider network that provides service to an end-user/customer of the network.
A service is an end-to-end connection that carries the customer's service as a container in
low order (LO) or high order (HO) trail. A service connects the logical ports that are
entirely used to carry a unique service.
The following parameters apply to the creation of a service:

Service Service Rate

Rate
Type
Ethernet 100 GbE, 40 GbE, 10 GbE (the default), 1 GbE, or Fast Ethernet
Optical ODU1, ODU2 (the default), ODU2E, ODU3, ODU4, OCH, or OMS.
SDH STM-256, STM-64 (the default), STM-64MS, STM-16, STM-16MS, STM-4, or STM-1
SONET OC-768, OC-192 (the default), OC-48, OC-12, or OC-3
CBR CBR 2G5

Service Service Rate

Rate
Type
Data FC 100 (the default), FC 200, FC 400, FC 800, FC 1200, HDSDI, SDSDI, DVBASI,
DDR, or 3GSDI

During the creation of a service, the 1350 OMS OTN application uses the service rate
value as follows:
• For DSR connection rates, the service rate value is the initial value of the signal type
in the Transmission Parameters panel.
• The particular service rate value is used to filter the list of ports that are displayed in
the From/To... fields in the Service Definition panel. Only ports that have a signal
type that is equal to the service rate or ports that are unassigned and can be assigned
with the signal type that is equal to the service rate are displayed for selection in the
From/To... fields in the Service Definition panel.
For a service, the 1350 OMS OTN application automatically assigns a service type based
on the connection rate and a service rate.

Connection Rate Service Rate Service Type

ODUk, OCH, Not applicable Undetermined
OC-nRS, STM-nRS
DSR 100 GbE, 40 GbE, 10 GbE (the Ethernet
default), 1 GbE, or Fast Ethernet
DSR Any value except 100 GbE, 40 Undetermined
GbE, 10 GbE (the default), 1 GbE,
or Fast Ethernet

The Category of a connection

When the users create or modify a connection, the system automatically determines and
names the Category of the connection based on the route of the connection. The route of
a connection is determined by the user selection in the ASON Routed field in the Service
Definition of the connection. The Category of a connection is not user-selectable;
meaning, it does not appear on any template. The Category field appears on the data table
for an infrastructure connection or service.

....................................................................................................................................................................................................................................
Nokia 1350 OMS 4-11
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS ASON Provisioning Infrastructure Connections and Services
Connections
....................................................................................................................................................................................................................................
The system-assigned Category of a connection can be one of the following:
• A Managed Plane connection is a connection in which the user has not checked the
ASON Routed field and the connection is not a logical drop link connection. Managed
Plane connections can be infrastructure connections or services.
• A Control Plane connection is an infrastructure connection in which the user has
checked the ASON Routed field, has unchecked the MRN Tunnel box, and the entire
route of the connection is in the Control Plane.
Note: A Drop Link, which is an external OS connection that is assigned to a Network
Protection Architecture (NPA) in ASON, is the link between the Managed Plane and
the Control Plane.
• A Mixed Plane connection is a connection in which the user has checked the ASON
Routed field and the route of the connection is in both the Managed Plane and the
Control Plane. Mixed Plane connections can be infrastructure connections or services.
• A ASON Logical Edge Drop Link is an ODUk connection with at least one connection
endpoint on an ODUPOOL where the ODUPOOL is in the Control Plane and the
route of the connection contains at least one link connection that belongs to an
external OS connection that is a Drop Link. For these connections, the HO-ODUk
cross-connection in the NE in the Control Plane must be created via the ASON
manager. Therefore, if the HO-ODUk cross- connection in the NE in the Control
Plane does not already exists when the Logical Drop Link connection is created, the
HO- ODUk cross connection must be created as part of the order for the Logical Drop
Link. Logical Drop Links can only be deleted if all the Control Plane clients are
deleted. (Note: when all Control Plane clients are deleted, the HO-ODUk cross
connection in the NE in the Control Plane is deleted via ASON manager.)
• An ASON Link is a managed plane infrastructure connection or a managed plane link
connection that is created in OTN and is assigned to an NPA in ASON. These
connections, which are reserved by the ASON manager, are locked in OTN and
cannot be modified, deleted, or rearranged. ASON Links and link connections of
ASON Links are not available for use by routing when ASON Routed is not selected
for the connection. When the users select ASON Routed for the connection and the
connection is a Control Plane or Mixed Plane connection, the ASON Links and link
connections of ASON links are not available to be used in any portion of the
connection in the Managed Plane. These connections can only be used in the portion
of the connection in the Control Plane.
• An ASON Implicit Server is the server of another ASON connection. An ASON
Implicit Server is automatically created by the GMRE and OTN. ASON Implicit
Server cannot be modified, deleted, or rearranged in OTN. ASON Implicit Servers
and link connections of ASON Implicit Servers are not available for use by routing
when ASON routing is not selected for the connection. When the users select ASON
Routed for the connection and the connection is a Control Plane or Mixed Plane

How infrastructures and services differ

Services and infrastructures have many of the same characteristics; but when the users
view the infrastructure connections or services in their respective data tables, some
differing characteristics become apparent. The following table summarizes these different
characteristics.

Infrastructure Connections and Services — Different Characteristics

Characteristic Infrastructures Services
Category ASON Implicit Server Managed Plane
ASON Logical Edge Drop Mixed Plane
Link
ASON Logical Link
ASON MRN Unterminated
Tunnel
ASON MRN Terminated
Tunnel
Control Plane
Managed Plane
Mixed Plane
Clients* — ✓

Infrastructure Connections and Services — Different Characteristics

Characteristic Infrastructures Services
Created by N/A —
SDH/GMRE
System
System Notify
User
Deploy Type Add Add
Delete Discover
Discover
Implementation State Commissioned Commissioned
Defined Defined
Implemented Implemented
Partially Allocated
Protection OMSP Protected
Protected Segment Protected
Unprotected Unprotected
Provisionable Wave Key Keyed Keyed
N/A N/A
Unkeyed
Servers* ✓ ✓
* A client is an object that uses a service of another object; whereas a server is an object that
provides a service to another object. Services do not have client connections. Infrastructure trails
can create client link connections; that is they can carry clients.

Client/Server Relationships
Connections linked by client/server relationships
A transmission network is layered; and, as such, the connections within a transmission
network are linked to one another through client/server relationships.
A client is an object that uses a service of another object.
A server is an object that provides a service to another object
See “Client/Server Relationships ” (p. 4-15) for details.

Client/Server relationship of various connection types

The client/server relationship of the various connection types is as follows:
• Infrastructure trails can have other infrastructure trails or services (paths) as clients.
The infrastructure trails can have other infrastructure trails or physical connections as
servers.
When the users access an infrastructure trail (either from a Connection list or from
other windows, such as the Routing Display), the system provides the users with
access to the following:
– To the list of infrastructure trail server connections; that is, the connections that
are serving this connection (infrastructure trails or physical connections depending
on the selected infrastructure trail position in the hierarchy.)
– To the list of clients that are served by the infrastructure trail (infrastructure trails
and services).
– To the list of services that are served by the infrastructure trail (both direct clients
and indirect clients).
• Services can never have clients. Services always have servers.
When accessing a service, the system provides users with access to the servers of the
selected service, which are its infrastructure trails.
• Physical connections can never have servers; they can only have clients.
When accessing a physical network connection, the system provides users with access
to the clients of the selected connection, which are its infrastructure trails.

Create an OTN Physical Connection

When to use
Use this task to create an OTN physical connection.

Related information
See the following topic in this document:
• “Physical Connections” (p. 4-3)

Before you begin

The OTN physical connection to be created can be one of several types of connections.
See the following tasks for detailed steps:
• “Task: Create an OTN OPS Unidirectional Physical Connection” (p. 4-16)
• “Task: Create an OTN Double-Simple (uni) Physical Connection” (p. 4-19)
• “Task: Create an OTN OTS or OPS Bidirectional Physical Connection” (p. 4-23)
• “Task: Create an OTN E-SNCP Physical Connection” (p. 4-28)
• “Task: Create an OTN Y-Cable Physical Connection” (p. 4-31)
• “Task: Create an OTN OPS Uplink Physical Connection” (p. 4-34)
You can also access the Physical Connection Creation window from the following areas
on the WebUI:
• By navigating to Deploy > New OTN Physical Connection.
• On the Link Maintenance Window.
• From the Physical Connections tab of the Shared Risk Group data table.

Task: Create an OTN OPS Unidirectional Physical Connection

Complete the following steps to create a unidirectional (one-way) physical connection.
...................................................................................................................................................................................................

1 From the OTN WebUI, follow this navigation path:

Operate > Physical Connections
Result: The system displays a data table that lists the OTN physical connections.
...................................................................................................................................................................................................

2 Mouse over the icons on the top right and click on the Create icon.

Figure 4-2 Physical Connections – Physical Connection Creation Window – Default

...................................................................................................................................................................................................

3 In the User Label field, enter a name to identify the connection.

Provisioning Note: You can enter a maximum of 92 characters for the User Label field.
The valid characters that you can enter for the User Label are the following:
Alphanumeric characters 0-9, a-z, and A-Z along with these special characters:
space, !, @, #, $, %, &, *, ( ), -, _, +, =, { }, [ ], :, ;, < >, ,, ., /, and ?.
...................................................................................................................................................................................................

4 In the Connection Type field, select Unidirectional from the drop-down list.

Figure 4-3 Physical Connections – Physical Connection Creation Window –

Unidirectional

...................................................................................................................................................................................................

5 Optional: In the SRGs panel, do one of the following to assign the physical connection to
a Shared Risk Group:
• Mouse over the icons and select Select items from List, which is the magnifying glass
icon. When the Shared Risk Group list is displayed, select the SRG or SRGs to be
correlated with the physical connection and click Add.
• If SRGs have not been created or to create a new SRG, mouse over the icons and select
the plus sign icon. When the SRG Creation window is displayed, enter the required fields
and click Deploy.
...................................................................................................................................................................................................

6 Optional: In the Enhanced Information panel, select the Allocation Cost from the
drop-down menu. The values range from 0 to 100. The default is 20.

7 Optional: In the Enhanced Information panel, select the Ultra Long Span from the
drop-down menu. The values are True or False (the default).
...................................................................................................................................................................................................

8 In the End Points panel, complete the following required A/Z End Points. Adjust the
Network Map to view the connection that you are creating.
• In the A End Points section, click the map or click the icon to the right to display the list
of available nodes and ports.
• In the Z End Points section, click the map or click the icon to the right to display the list
of available nodes and ports.
Result: The system displays the selected Node or Port List.
...................................................................................................................................................................................................

9 From the selected list that is displayed, do the following to select nodes and ports:
• Select a node and a port from the list for the A End Points and click Select.
• For a bidirectional connection, click on a node and a port from the list for the Z End
Points and click Select.
Result: The system adds the names of the A and Z nodes and ports that you selected
to the A End Points and Z End Points areas of the window.
...................................................................................................................................................................................................

10 In the Direction field, select the A End Points to be Sink or Source end points.
...................................................................................................................................................................................................

11 Click Deploy.
Result: The physical connection is created.
E...................................................................................................................................................................................................
N D O F S T E P S

Task: Create an OTN Double-Simple (uni) Physical Connection

Complete the following steps to create an double-simple (uni) physical connection.
...................................................................................................................................................................................................

1 From the WebUI, follow this navigation path:

Operate > Physical Connections

2 Mouse over the icons on the top right and click on the Create icon.
Result: The system displays the Physical Connection Creation window, which
defaults to an OTS physical connection.

Figure 4-4 Physical Connections – Physical Connection Creation Window – Default

...................................................................................................................................................................................................

3 In the User Label field, enter a name to identify the connection.

Provisioning Note: You can enter a maximum of 92 characters for the User Label field.
The valid characters that you can enter for the User Label are the following:
Alphanumeric characters 0-9, a-z, and A-Z along with these special characters:
space, !, @, #, $, %, &, *, ( ), -, _ , +, =, { }, [ ], :, ;, < >, ,, ., /, and ?.
...................................................................................................................................................................................................

4 In the Connection Type field, select Double-simple (uni) from the drop-down list.

Figure 4-5 Physical Connections – Physical Connection Creation Window –

Double-Simple (uni)

...................................................................................................................................................................................................

5 In the Interworking Tech field, select none, SDH, SONET, or ETH from the drop-down
list.
...................................................................................................................................................................................................

6 Do one of the following:

• If you selected none as the Interworking Tech, go to Step 7.
• If you selected SDH as the Interworking Tech, go to Step 8.
• If you selected SONET as the Interworking Tech, go to Step 9.
• If you selected ETH as the Interworking Tech, go to Step 10.

7 If the Interworking Tech is None, do the following:

• In the Specific Information panel, select the WDM connection Type from the
drop-down list to be OTS (the default) or OPS.
See Step 11.
...................................................................................................................................................................................................

8 If the Interworking Tech is SDH, do the following:

• In the Specific Information panel, select the Client Signal Type from the drop-down list
to be STM-256 (the default), STM-64, STM-16, STM-4, or STM-1.
See Step 11.
...................................................................................................................................................................................................

9 If the Interworking Tech is SONET, do the following:

• In the Specific Information panel, select the Client Signal Type from the drop-down list
to be OC-768 (the default), OC-768, OC-192, OC-48, OC-12, or OC-1.
• Go to Step 11.
...................................................................................................................................................................................................

10 If the Interworking Tech is ETH, do the following:

• In the Specific Information panel, select a Client Signal Type from the drop-down list.
• Go to Step 11.
...................................................................................................................................................................................................

11 Optional: In the SRGs panel, do one of the following to assign the physical connection to
a Shared Risk Group:
• Mouse over the icons and select Select items from List, which is the magnifying glass
icon. When the Shared Risk Group list is displayed, select the SRG or SRGs to be
correlated with the physical connection and click Add.
• If SRGs have not been created or to create a new SRG, mouse over the icons and select
the plus sign icon. When the SRG Creation window is displayed, enter the required fields
and click Deploy.
...................................................................................................................................................................................................

12 Optional: In the Enhanced Information panel, select the Allocation Cost from the
drop-down menu. The values range from 0 to 100. The default is 20.
...................................................................................................................................................................................................

13 In the End Points panel, complete the following required A/Z End Points. Adjust the
Network Map to better view the connection that you are creating.
....................................................................................................................................................................................................................................
4-22 Nokia 1350 OMS
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS ASON Provisioning Create an OTN Physical Connection
Connections
....................................................................................................................................................................................................................................
• In the A End Points section, click on the map or click on the icon to the right to display
the list of available Nodes and the available ports for your Interworking Tech selection.
• In the Z End Points section, click on the map or click on the icon to the right to display
the list of available ports for your Interworking Tech selection.
Result: The system displays the selected Node and selected port lists.
...................................................................................................................................................................................................

14 From the selected list that is displayed for your Interworking Tech selection, do the
following to make selections:
• Click on a node and a port(s) from the displayed lists for the A End Points and click
Add.
• Click on a node, and a source and sink port from the displayed lists for the Z End
Points, and click Add.
Result: The system adds the names of the A and Z nodes and ports that you selected
to the A End Points and Z End Points areas of the window.
...................................................................................................................................................................................................

15 Click Deploy.
Result: The physical connection is created.
E...................................................................................................................................................................................................
N D O F S T E P S

Task: Create an OTN OTS or OPS Bidirectional Physical Connection

Complete the following steps to create an OTS or OPS bidirectional physical connection.
...................................................................................................................................................................................................

1 From the WebUI, follow this navigation path:

2 Mouse over the icons on the top right and click on the Create icon.

Figure 4-6 Physical Connections – Physical Connection Creation Window – Default

...................................................................................................................................................................................................

3 In the User Label field, enter a name to identify the connection.

Provisioning Note: You can enter a maximum of 92 characters for the User Label field.
The valid characters that you can enter for the User Label are the following:
Alphanumeric characters 0-9, a-z, and A-Z along with these special characters:
space, !, @, #, $, %, &, *, ( ), -, _ , +, =, { }, [ ], :, ;, < >, ,, ., /, and ?.
...................................................................................................................................................................................................

4 In the Connection Type field, select Bidirectional from the drop-down list.

Figure 4-7 Physical Connections – Physical Connection Creation Window –

Bidirectional

...................................................................................................................................................................................................

6 Do one of the following:

• If you selected none as the Interworking Tech, go to Step 7.
• If you selected SDH as the Interworking Tech, go to Step 12.
• If you selected SONET as the Interworking Tech, go to Step 13.
• If you selected ETH as the Interworking Tech, go to Step 14.

7 If the Interworking Tech is None, do the following:

• In the Specific Information panel, select the WDM connection Type from the
drop-down list to be OTS (the default) or OPS.
Result: The system activates the appropriate fields depending on your selection.
...................................................................................................................................................................................................

8 If the WDM connection Type is OPS, go to Step 9.

If the WDM connection Type is OTS, go to Step 15.
...................................................................................................................................................................................................

9 In the Interface Type, select - (the default, which is not applicable or unknown), NNI,
UNI_SDH, UNI_SONET, UNI-Ethernet, or UNI-miscellanea.
Result: The system activates the appropriate Client Signal Type depending on your
selection.
...................................................................................................................................................................................................

10 In the Client Signal Type field, select - (the default, which is not applicable or unknown)
or the specific signal type for your installation:
• NNI client interface types include various OTUx/OTULx client signal types.
• UNI_SDH client interface types include various STMx client signal types.
• UNI_SONET client interface types include various OCx client signal types.
• UNI-Ethernet client interface types include various E, FE, GbE, or GB E Ethernet client
signal types.
• UNI-miscellanea client interface types include various FCx, CBRx, GFCE, DVBASI,
SHDSI, HDSI, FICON, DV_SDI, or DV-ASI client signal types.
...................................................................................................................................................................................................

11 In the OCS-Photonic Interworking Type field, do the following:

• Select - (the default, which is not applicable or unknown), OVERLAY, or DROP.
• Go to Step 15.
...................................................................................................................................................................................................

12 If the Interworking Tech is SDH, do the following:

• In the Specific Information panel, select the Client Signal Type from the drop-down list
to be STM-256 (the default), STM-64, STM-16, STM-4, or STM-1.
• Go to Step 15.

13 If the Interworking Tech is SONET, do the following:

• In the Specific Information panel, select the Client Signal Type from the drop-down list
to be OC-768 (the default), OC-768, OC-192, OC-48, OC-12, or OC-1.
• Go to Step 15.
...................................................................................................................................................................................................

14 If the Interworking Tech is ETH, do the following:

• In the Specific Information panel, select one of the Client Signal Type from the
drop-down list.
• Go to Step 15.
...................................................................................................................................................................................................

15 Optional: In the SRGs panel, do one of the following to assign the physical connection to
a Shared Risk Group:
• Mouse over the icons and select Select items from List, which is the magnifying glass
icon. When the Shared Risk Group list is displayed, select the SRG or SRGs to be
correlated with the physical connection and click Add.
• If SRGs have not been created or to create a new SRG, mouse over the icons and select
the plus sign icon. When the SRG Creation window is displayed, enter the required fields
and click Deploy.
...................................................................................................................................................................................................

16 Optional: In the Enhanced Information panel, select the Allocation Cost from the
drop-down menu. The values range from 0 to 100. The default is 20.
...................................................................................................................................................................................................

17 In the End Points panel, complete the following required A/Z End Points. Adjust the
Network Map to better view the connection that you are creating.
• In the A End Points section, click on the map or click on the icon to the right to display
the list of available Nodes and the available ports for your Interworking Tech selection.
• In the Z End Points section, click on the map or click on the icon to the right to display
the list of available ports for your Interworking Tech selection.
Result: The system displays the selected Node and selected port lists.
...................................................................................................................................................................................................

18 From the selected list that is displayed for your Interworking Tech selection, do the
following to make selections:
• Click on a node and a port(s) from the displayed lists for the A End Points and click
Add.
....................................................................................................................................................................................................................................
Nokia 1350 OMS 4-27
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS ASON Provisioning Create an OTN Physical Connection
Connections
....................................................................................................................................................................................................................................
• Click on a node, and a source and sink port from the displayed lists for the Z End
Points, and click Add.
Result: The system adds the names of the A and Z nodes and ports that you selected
to the A End Points and Z End Points areas of the window.
...................................................................................................................................................................................................

19 Click Deploy.
Result: The physical connection is created.
E...................................................................................................................................................................................................
N D O F S T E P S

Task: Create an OTN E-SNCP Physical Connection

Complete the following steps to create an E-SNCP physical connection.
...................................................................................................................................................................................................

1 From the WebUI, follow this navigation path:

2 Mouse over the icons on the top right and click on the Create icon.

Figure 4-8 Physical Connections – Physical Connection Creation Window – Default

...................................................................................................................................................................................................

3 In the User Label field, enter a name to identify the connection.

Provisioning Note: You can enter a maximum of 92 characters for the User Label field.
The valid characters that you can enter for the User Label are the following:
Alphanumeric characters 0-9, a-z, and A-Z along with these special characters:
space, !, @, #, $, %, &, *, ( ), -, _ , +, =, { }, [ ], :, ;, < >, ,, ., /, and ?.
...................................................................................................................................................................................................

4 In the Connection Type field, select E-Sncp from the drop-down list.

Figure 4-9 Physical Connections – Physical Connection Creation Window – E-Sncp

...................................................................................................................................................................................................

5 In the Client Signal Type field, select one of the Ethernet signal types for your
installation.
...................................................................................................................................................................................................

6 Optional: In the SRGs panel, do one of the following to assign the physical connection to
a Shared Risk Group:
• Mouse over the icons and select Select items from List, which is the magnifying glass
icon. When the Shared Risk Group list is displayed, select the SRG or SRGs to be
correlated with the physical connection and click Add.

7 Optional: In the Enhanced Information panel, select the Allocation Cost from the
drop-down menu. The values range from 0 to 100. The default is 20.
...................................................................................................................................................................................................

8 In the End Points panel, complete the following required A/Z End Points. Adjust the
Network Map to better view the connection that you are creating.
• In the A End Points section, click on the map or click on the icon to the right to display
the list of available nodes and ports.
• In the Z End Points section, click on the map or click on the icon to the right to display
the list of available nodes and ports.
Result: The system displays the selected Node or Port list.
...................................................................................................................................................................................................

9 From the selected list that is displayed, do the following to make selections:
• Select a node and then a port from the displayed lists for the A End Points and click
Add.
• Select a node and then a port from the displayed lists for the Z End Points and click
Add.
Result: The system adds the names of the A and Z nodes and ports that you selected
to the A End Points and Z End Points areas of the window.
...................................................................................................................................................................................................

10 Click Deploy.
Result: The physical connection is created.
E...................................................................................................................................................................................................
N D O F S T E P S

Task: Create an OTN Y-Cable Physical Connection

Complete the following steps to create a Y-Cable physical connection.
...................................................................................................................................................................................................

1 From the WebUI, follow this navigation path:

Operate > Physical Connections

2 Mouse over the icons on the top right and click on the Create icon.
Result: The system displays the Physical Connection Creation window, which
defaults to an OTS physical connection.

Figure 4-10 Physical Connections – Physical Connection Creation Window – Default

...................................................................................................................................................................................................

3 In the User Label field, enter a name to identify the connection.

Provisioning Note: You can enter a maximum of 92 characters for the User Label field.
The valid characters that you can enter for the User Label are the following:
Alphanumeric characters 0-9, a-z, and A-Z along with these special characters:
space, !, @, #, $, %, &, *, ( ), -, _ , +, =, { }, [ ], :, ;, < >, ,, ., /, and ?.
...................................................................................................................................................................................................

4 In the Connection Type field, select Y-Cable from the drop-down list.

Figure 4-11 Physical Connections – Physical Connection Creation Window – Y-Cable

...................................................................................................................................................................................................

8 In the End Points panel, complete the following required A/Z End Points. Adjust the
Network Map to better view the connection that you are creating.
• In the A End Points section, click on the map or click on the icon to the right to display
the list of available nodes and ports.
• In the Z End Points section, click on the map or click on the icon to the right to display
the list of available nodes and main and spare ports.
Result: The system displays the selected Node or Port list.
...................................................................................................................................................................................................

9 From the selected list that is displayed, do the following to make selections:
• Select a node and then a port from the displayed lists for the A End Points and click
Add.
• Select a node and then a main and a spare port from the displayed lists for the Z End
Points and click Add.
Result: The system adds the names of the A and Z nodes and ports that you selected
to the A End Points and Z End Points areas of the window.
...................................................................................................................................................................................................

Task: Create an OTN OPS Uplink Physical Connection

Complete the following steps to create an OPS uplink physical connection.
...................................................................................................................................................................................................

1 From the WebUI, follow this navigation path:

Operate > Physical Connections

2 Mouse over the icons on the top right and click on the Create icon.
Result: The system displays the Physical Connection Creation window, which
defaults to an OTS physical connection.

Figure 4-12 Physical Connections – Physical Connection Creation Window – Default

...................................................................................................................................................................................................

3 In the User Label field, enter a name to identify the connection.

Provisioning Note: You can enter a maximum of 92 characters for the User Label field.
The valid characters that you can enter for the User Label are the following:
Alphanumeric characters 0-9, a-z, and A-Z along with these special characters:
space, !, @, #, $, %, &, *, ( ), -, _ , +, =, { }, [ ], :, ;, < >, ,, ., /, and ?.
...................................................................................................................................................................................................

4 In the Connection Type field, select OPS uplink from the drop-down list.

Figure 4-13 Physical Connections – Physical Connection Creation Window – OPS

Uplink

...................................................................................................................................................................................................

6 Optional: In the Enhanced Information panel, select the Allocation Cost from the
drop-down menu. The values range from 0 to 100. The default is 20.

7 In the End Points panel, click on the map or click on the icon to the right to display the
list of available nodes and ports. Adjust the Network Map to better view the connection
that you are creating.
Result: The system displays the selected Node or Port list.
...................................................................................................................................................................................................

8 From the selected list that is displayed, do the following to make selections:
• Select a node and click Add.
• Select an uplink port and a Mux client port from the displayed lists and click Add.
Result: The system adds the names of the node and ports that you selected in the End
Points 1830 PSS Compound Node portion of the window.
...................................................................................................................................................................................................

9 Click Deploy.
Result: The physical connection is created.
E...................................................................................................................................................................................................
N D O F S T E P S

Modify the Allocation Cost of a Physical Connection

When to use
Use this task to modify the allocation cost of a physical connection.

Related Information
See the following topics:
• “Infrastructure Connections and Services” (p. 4-10)

Before you begin

When you modify the parameters of a connection, you are modifying the template from
which the connection was created. The system determines the parameters that are to be
modified.

Task
Complete the following steps to modify the allocation cost of a physical connection.
...................................................................................................................................................................................................

1 From the WebUI, follow the navigation path:

Operate > Physical Connections
Result: The system displays a data table that lists all of the physical connections.
...................................................................................................................................................................................................

2 Highlight and select the physical connection for which you want to modify the allocation
cost and do the following:
• Select the Properties tab in the lower part of the window.
Result: The system displays the properties of the selected physical connection.
...................................................................................................................................................................................................

3 Click he Routing tab.

Result: The system displays the Routing parameters
...................................................................................................................................................................................................

4 Change the value of the Allocation Cost.

Important! The system determines if the parameter can be modified, depending on the
state and correlation of the connection.
...................................................................................................................................................................................................

5 Click the Save icon to save the changes.

Modify the Parameters of an Infrastructure Connection or

Service
When to use
Use this task to modify the parameters of an infrastructure connection or service.

Related Information
See the following topics:
• “Infrastructure Connections and Services” (p. 4-10)

Before you begin

When you modify the parameters of a connection, you are modifying the template from
which the connection was created. The system determines which parameters can be
modified.

Task
Complete the following steps to modify the parameters of an infrastructure connection or
service.
...................................................................................................................................................................................................

1 From the WebUI, follow one of these navigation paths:

Operate > Infrastructure Connections
Operate > Services
Result: Depending on your selection, the system displays a data table that lists all of
the infrastructure connections or services.
...................................................................................................................................................................................................

2 Highlight and select the infrastructure connection or service for which you want to
modify parameters and do one of the following:
• Mouse over the icons on the top right and click on the Modify Parameters icon.
• Right click and follow this path: Modify Parameters.
Result: The system displays the Modify Connection window, which is the template
from which the connection was created.
...................................................................................................................................................................................................

3 Make the necessary changes to suit your installation.

4 Click Deploy.
Result: The system makes the requested changes and displays a message window.
...................................................................................................................................................................................................

5 Optional: To view the connection details for the connection that you just modified in data
table, click Show Connection.
E...................................................................................................................................................................................................
N D O F S T E P S

Connections Features

Single Step Provisioning

Single Step Provisioning definition
Single Step Provisioning is a method of connection provisioning in which the user creates
one particular type of connection and the system automatically creates the appropriate
server connection. In addition, when the users modify the route of the connection, the
system automatically modifies the route of the server connection.

Single Step Provisioning and LO-ODUk/DSR connections

When users create a DSR service, the system automatically creates the LO-ODUk server
connection. Transmission parameters can be set for the DSR service that the user has
created and the ODUk server connection that the system has created. One order is created
for each connection and both the orders transition through the steps in tandem.
Users can modify only the DSR connection that they have created. When the users
modify the route of the DSR service, the system automatically modifies the route of the
LO-ODUk server connection.
Connection type, group name, and group order
All automatically created servers have the connection type of Managed Plane Implicit
Server.
When the servers are automatically created, the primary connection (the DSR connection)
and the automatically created servers have an automatically assigned group name, which
has the format:
g-[connection name]
Where: The connection name is the name of the primary connection.
When the servers are automatically created, the primary connection (the DSR connection)
and the automatically created servers have a group order status that reflects the status of
all the connections in the group. If any connection is in a failed state, the group order
status is failed.
Supported 1830 PSS and 1830 PSS-4 circuit packs
For 1830 PSS and 1830 PSS-4, the following circuit packs support DSR connections that
have supported server layers at the ODUk rate:
• 11DPM12
• 11DPM8
• 11DPM4M
....................................................................................................................................................................................................................................
4-42 Nokia 1350 OMS
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS ASON Provisioning Single Step Provisioning
Connections Features
....................................................................................................................................................................................................................................
• 112SDX11
• 4QPA8
• 11OPE8
• 11QCE12X
• 20P200
Restrictions
Restrictions include the following:
• Users can continue to create the immediate LO-ODUk connection; however, the DSR
and LO-ODUk connections is not linked.
• For DSR connections on 11DPM12 packs with OPTSG container type, the system
does not automatically create the ODU1 server connection when the first DSR
connection is created.
• When a DSR service has two or more LO-ODUk server connections, the system only
creates the immediate LO-ODUk server connection. Users must create the second
LO-ODUk.

Single Step Provisioning and HO-ODUk/OTUk connections

When the users create a HO-ODUk infrastructure connection (trail) or service, the system
automatically creates the OTUk server connection. Users cannot create OTUk
connections directly. One order is created for each connection and both the orders
transition through the order steps in tandem.
Transmission parameters can be set for the HO-ODUk connection that the user creates
and the OTUk server connection that the system has created.
Wave Key parameters can be set for the OTUk server connection that the system has
created.
The users can modify only the HO-ODUk connection that they have created.
When the users modify the route of the HO-ODUk infrastructure connection (trail) or
service, the system automatically modifies the route of the respective LO-ODUk server
connection. One order is created for each connection and both orders transition through
the order steps in tandem.
When the users delete or database delete an HO-ODUk connection, the system
automatically deletes the OTUk server connections.

Modify the Route (Reroute) of a Connection

When to use
Use this task to modify the route of a Connection.

Related Information
You can modify the route of the following types of connections by using the steps that are
provided in this task
• Infrastructure connections, including infrastructures (trails) and logical links
• Service connections
• Client and server connections of a selected infrastructure connection
• Server connections of a selected service
• PM enabled points of a selected service or infrastructure connection
• Impacted connections of a selected service or infrastructure connection
Impacted connections are those infrastructure and service connections that are
associated with a selected node and its current operational and alarm state.
• Used ports of a selected service or infrastructure connection
Used ports are those infrastructure and service connections that are assigned to a port
address on a selected node.

Table 4-1 Modify Connections for Infrastructure Connections and Services

Modify Connection
Option Explanation
Modify Route When modifying a route, some part of the route must be common between
the old and new routes.
• Reroute deletes the connection using a route that needs to be released,
and recreates the connection using the new route.
• Reinstate is used to rollback a Reroute with a reinstate order to its
original route. Reinstate is available for a commissioned reroute with a
reinstate order. With a Reinstate of the original route, traffic disruption
might occur.
• Reroute with Reinstate deletes the connection using a route that needs to
be released, and recreates the connection using the new route, but stores
the layout of the older connection so it can be rolled back using a
Reinstate. During the Reinstate, the original (older) route might cause
traffic disruptions. The older route is purged and the saved time slots are
released.
• Regenerator ports are displayed in the Routing Constraints panel when
you create an infrastructure connection or modify the route of an
infrastructure connection if the connection rate is ODUK and ASON
Routed is selected and if the connection rate is ODUK and the Auto Server
Creation field is selected. When you modify the route of an infrastructure
connection, you can view the regenerator ports in the Routing Constraints
table, but you cannot add or remove the regenerator ports as routing
constraints.
Soft Reinstate* A Soft Reinstate is a non-traffic affecting reinstatement of the connection.
Soft Reinstate, which is the default, is executed as a best effort by the
system.
Hard Reinstate* A Hard Reinstate is a traffic affecting Reinstate.
*The system enables you to select a Soft or a Hard Reinstate in the Modify Route window. The
system makes a best effort to comply with your preferences; that is, the system performs a Soft
Rearrange if the impacted connection supports that capability. If the impacted connection does
not support the capability, the system performs a Hard Rearrange.

Task
Complete the following steps to modify the route of an infrastructure connection or a
service.
...................................................................................................................................................................................................

1 From the WebUI, follow one of these navigation Connections:

2 Do one of the following:

• Right click on a connection, select Modify Connection, and select Reroute....
• Click on a connection, mouse over the icons on the top right, locate Modify Connection,
click the right side of the icon, and select and select Reroute....

...................................................................................................................................................................................................

3 In the Routing Constraints panel, configure the following parameters:

• In the Rearrange field, select Hard or Soft from the drop-down list.
If no connection endpoints are changed on the Service Definition panel, the default is
Soft. If one or more connection endpoints are changed on the Service Definition
panel, the default is Hard. If the connection rate is OTUk or if the connection category
is a terminated ASON MRN tunnel, the default and only option is Hard.

• To delete a routing constraint from the data table in the Routing Constraints panel,
select the constraint to be deleted and click the Delete icon. The system deletes the
routing constraint from the data table.
...................................................................................................................................................................................................

4 Modify or set the parameters in the Service Definition panel, Connection Control Panel,
Transmission Parameters panel, SNC Protection panel, and Assurance panel.
...................................................................................................................................................................................................

5 Click the Deploy button.

Auto Payload
Auto Payload definition
Auto Payload is a 1350 OMS OTN provisioning feature that enables an HO-ODUk
infrastructure trail, along with a LO-ODUk infrastructure trail, to be provisioned in a
single step when users provision a DSR service.

Auto Payload functional description

When the users provision DSR services, the system automatically creates all
point-to-point HO-ODUk trails along with any accompanying LO-ODUk trails. However,
for any HO-ODUk trails that involve pass-through HO cross connections or protected
HO-ODUk trails, users must provision these connections in separate steps.

Auto Payload Routing Mode considerations

The Auto Payload feature supports the provisioning of DSR services and LO-ODUk
infrastructure connections in the Automatic and Manual routing modes.
When users specify the Automatic routing mode during the creation of a DSR service or
a LO-ODUk infrastructure connection (trail), the system automatically determines the
route of the connection. When the LO-ODUk infrastructure trails are implemented, the
system creates the HO-ODUk infrastructure trails and makes the appropriate cross
connections to the NEs.
During the provisioning of LO-ODUk infrastructure trails in the Manual routing mode,
users can select the LO-ODUk link connections from the HO-ODUk trails as well as the
appropriate OTUk trails. When users select the OTUk trails, the system uses those link
connections to create the HO-ODUk trails and it makes the appropriate cross connections
to the NEs during implementation of the LO-ODUk.

Auto Payload supported configurations

The Auto Payload feature relies on the system's automatic creation of virtual servers,
which are ODU2 pool ports on the 1830 PSS OCS NEs that are used for internal routing.
Virtual servers are not visible to our users; the system uses the virtual servers internally
for routing.
The system creates a virtual server at the HO-ODUk layer during the following events:
• When a logical link is created between two 1UD200 I/O ports of two photonic NEs.
• When a logical link is created between two 1830 PSS OCS I/O ports that have a
photonic core in the middle.
• When a logical link is created between two 1830 PSS OCS uplink ports that have a
photonic core in the middle.

Auto Payload configuration examples

The first configuration example consists of two 1830 PSS-64 OCS NEs that pass
through a photonic core of 1830 PSS-32 NEs. In a single step, users create a DSR and
LO-ODUk connection that connects the two 1830 PSS-64 OCS NEs. The system
automatically creates the HO-ODUk infrastructure connection (trail) and virtual servers
on the 1830 PSS-64 OCS NEs, the endpoints of which are ODUPOOL ports. The
remaining L-OPC and OTUk connections are then automatically created among the 1830
PSS-64 OCS and 1830 PSS-32 NEs.

Figure 4-14 DSR Service Creation between Two 1830 PSS-64 OCS NEs Passing
Through a 1830 PSS Photonic Core

The second configuration example consists of an 1830 PSS-64 OCS NE asymmetrically

connected to an 1830 PSS-4 Photonic NE that is configured with an 11DPM12 pack. In a
single step, users create a DSR and LO-ODUk connection that connects the OCS and
photonic NEs. The system automatically creates the HO-ODUk infrastructure connection
(trail) and a virtual server on the 1830 PSS-64 OCS NE, the endpoint of which is an
ODUPOOL port. The remaining OTUk connection is then automatically created between
the 1830 PSS-64 OCS and 1830 PSS-4 Photonic NE.

Figure 4-15 DSR Service Creation between One 1830 PSS-64 OCS NE and One 1830
PSS-4 Photonic NE

The third configuration example consists of the connection of four 1830 PSS-64 OCS
NEs. In a single step, users create a DSR and LO-ODUk connection that connects the
four 1830 PSS-64 OCS NEs. The system automatically creates the HO-ODUk
infrastructure connections (trails) and virtual servers on the 1830 PSS OCS NEs, the
endpoints of which are ODUPOOL ports. The remaining OTUk connections are then
automatically created among the four 1830 PSS OCS NEs.

Figure 4-16 DSR Service Creation between Four 1830 PSS-64 OCS NEs

Auto Payload and Delete/DB Delete

Whenever users delete or DB delete HO-ODUk infrastructure connections (trails) that
uses the link connection of an L-OPC or link connections from an OTUk trail that is
between two 1830 PSS OCS NEs, the system recreates the ODUPOOL ports that are
between the two ends of 1830 PSS OCS NEs or are on the L-OPC.
When the users delete or DB delete DSR services, the system automatically deletes the
corresponding LO-ODUk infrastructure connection (trail). The system also deletes the
HO-ODUk if the LO-ODUk is the only client of the HO-ODUk infrastructure connection
(trail).

Auto Creation of Edge Connections

Auto Creation of Edge HO ODUk connections
When the users create an asymmetric service connection with one end point on a black
box and the other end point on a managed NE, the system automatically creates an edge
HO ODUk connection between the black box and the adjacent managed NE when the
connection is required. The edge HO ODUk server connection is created as part of the
service connection order.
Example:
If one connection end point is a 10GbE client port on a 10X10ANYG card and the second
end point is a black box connected to an OTU4 port on a 1XAN100G card, an HO ODU4
connection must exist or must be created between the black box and the OTU4 port.

Auto Creation of Edge HO Trail connections

If the users create a DSR or LO-ODUj connection and if the connection is the first
connection using a channelized endpoint, the system automatically creates an edge HO
infrastructure trail connection. If the DSR or LO-ODUj connection has multiple
channelized endpoints, the system automatically creates an edge HO infrastructure trail
connection for each channelized endpoint.
The system automatically provisions these edge HO trail connections for DSR or
LO-ODUj connections that are created using automatic, trail based, and link connection
based routing. In addition, the system automatically provisions these edge HO trail
connections regardless of the users selecting Auto Server Creation.
After the users submit the DSR/LO-ODUj connection request, the system determines if
one or more edge HO trail connections need to be created:
• If one or more edge HO trails need to be created, the system creates an order for each
edge HO trail connection.
• If an edge HO trail connection exists without an associated order, the system create an
order for the edge HO trail connection.
• If an edge HO trail connection order exists and the order is not in Commissioned
state, the system moves the state to Commissioned .
In each instance, the system creates an order for each connection and all orders transition
through the order steps in tandem. If any order fails, the group state for the connections is
Failed. If the auto-creation of the edge HO trails connection is successful, the system
names the connection (ENNI:[PTP Name]:[rate]<num>) and the system generates link
connections.

Unterminated OTUk/ODUk Infrastructures without Virtual

Termination Management
Terminated/Unterminated and channelized/unchannelized connections
In a Multi-Regional Network, (MRN), connections can be labeled as forward
adjacency-terminated (FA_TERM) and forward adjacency-untermated (UNTERM).
• FA_TERM: Connection where the start and the end point is an OCS NE.
• FA-UNTERM: Connection where the start and the end point may or may not be an
OCS NE.
A terminated connection is a connection that occurs when a particular layer comes to a
logical end and a client (technology) layer payload is mapped or several clients of the
same layer are multiplexed, and overhead bytes are inserted or removed. A terminated
connection can be asymmetric; meaning, one end of the connection can be terminated and
the other end can be unterminated.
An unterminated connection is a connection that occurs when a transmission frame passes
through a particular connection end point (TP) and overhead is not inserted or not
removed. The management system does not have any knowledge of the internal payload
structure. Both logical links and ODUk paths are unterminated.
A channelized connection occurs when, at the edge of the network, the hand-off port is
unterminated at a layer higher (lower bit rate) than the hand-off layer. The hand-off layer
is then referred to as channelized, because it multiplexes several unterminated lower order
connections and leaves the managed domain as a singular entity.
For a channelized endpoint, an HO-ODU cross connection is required between the ODUk
CTP of the edge port and a TTP on the ODUPOOL. The route of the edge HO trail
consists of the HO ODU cross connection. The edge HO trail has x number of link
connections at the ODUj rate.
An unchannelized connection is a connection that is unterminated on one end and is
carrying an invisible payload (no multiplexing, only one-to-one mapping). When a
connection is unchannalized on both ends, it is typically referred to as a path.
Control Plane connections can be terminated or unterminated:
• The terminated ASON connections are those that are terminated on a UNI port.
• The unterminated ASON connections are those that have the endpoints on an NNI
port.

Figure 4-17 Connections for Channelized and/or Unterminated Endpoints

Unterminated OTUk/ODUk Infrastructures without Virtual Termination

To support both terminated and unterminated connections, the 1350 OMS OTN manages
unterminated ODUk connections in the Managed Plane, Control Plane, and Mixed Plane
environments without having to create an external topological link and an edge NE
(ENE). Users can continue to create unterminated ODUk connections using topological
links and ENEs; and, within the network, users can create unterminated connections that
do not use topological links and endpoint NEs (ENEs) along with other unterminated
connections that use topological links and ENEs.

Supported connection types

The following connection types are supported:
• Channelized and unchannelized ODUk service connections are supported.
• Channelized connections with one or more endpoints on an ENE are supported.
• Configurations that require three-ended HO-ODU cross connections and subsequent
three-ended edge HO trails are supported.
• Both HO-ODUk and LO-ODU (at the point where each exists the network)
connections are supported.
• Connections in which all connection endpoints have the same signal type (symmetric)
and connections in which the endpoints have different, but compatible, signal types
(asymmetric) are supported.
• DSR service connections in which the DSR LO-ODU connections are created in a
single step using Auto Server Creation are supported.
• DSR connections are supported in which one connection endpoint is an NNI port, the
other connection endpoint is a UNI port, and the rate of the NNI port is equivalent to
the container rate of the UNI port is asymmetric and is not channelized at either
connection endpoint.
Example:
One connection endpoint is an OTU2 port and the second endpoint is a 10GbE port
and the connection rate is a 10GbE DSR.
Example – Asymmetric DSR Connection Not Channelized at Either End

• An ODUk service connection can be asymmetric and channelized at one or both

connection endpoints.
Examples:
A channelized connection at one endpoint is one in which one connection endpoint is
an OTU4 port, the second endpoint is an OTU2 port, and the connection rate is
ODU2.
A channelized connection at both endpoints is one in which one connection endpoint
is an OTU4 port, the second endpoint is an OTU3 port, and the connection rate is
ODU2.
....................................................................................................................................................................................................................................
Nokia 1350 OMS 4-61
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS ASON Provisioning Unterminated OTUk/ODUk Infrastructures without Virtual
Connections Features Termination Management
....................................................................................................................................................................................................................................
• Channelized configurations in which the aggregation is at the end node of the
connection are supported with two step provisioning. In the first step, the user creates
the HO ODU logical link and OTUk connection. In the second step, the user creates
the service connection and LO ODUj connection.
The following figure illustrates an asymmetric DSR connection that is channelized at
one end.
Example – Asymmetric DSR Connection Channelized at One End

• A service connection in which an endpoint is channelized and the aggregation of the

connection is in the non-managed portion of the network is supported; however, users
must complete an additional step when creating the service connection.
For this configuration, a single HO ODU cross connection is on a node that contains a
channelized endpoint. To create this type of service connection, users must first create
the OTS connection(s); then they must create the HO ODU logical link. For the
additional step, users must create the HO ODU trail. One endpoint is on an ODUPTF
on the ODUPOOL (the left hand node in the following figure) and the other endpoint
is the edge port. Lastly, users must create DSR/ODUj connection.
Example – Asymmetric DSR Connection Channelized Multi Hop at Edge

Channelized ports
For HO ODU service connections, connection termination points (CTPs) on ports
(including black box ports) with a Signal Type of OTUK are supported on 1830 PSS OCS
I/O cards and uplink cards.
Channelized LO ODU CPTs on unassigned and assigned ports are supported on 1830 PSS
OCS I/O cards and uplink cards. Channelized LO ODU CTPs on black boxes are also
supported.

Y-Cable Protection for Services

Y-Cable definition
A Y-cable, also called a splitter or signal splitter, is a type of cable that contains three
ends. One end of the cable is common; the other end splits into two leads.

Best Practice templates for Y-Cable Protection

The Y-Cable Protection feature is available for SONET and SDH service connections.
Users can provision Y-cable service connections when they select one of the following
Best Practice templates:
• Service, SONET, Y-Cable Protected, OC-N, which is known as the SONET Y-Cable
Protected template
• Service, SDH, Y-Cable Protected, STM-N, which is known as the SDH Y-Cable
Protected template

Y-Cable general provisioning guidelines for the SDH and SONET Best Practice templates
The following general provisioning guidelines apply to using the SONET Y-Cable
Protected and SDH Y-Cable Protected Best Practice templates:
• If connection shape is bidirectional, users can specify the Switch Mode to be
Unidirectional (the default) or Bidirectional. For switch modes that are
Bidirectional, users can optionally enable or disable Revertive Mode. If the
Revertive Mode is enabled, users can then specify the Wait to Restore Time (min).
• If the values of Switch Mode, Revertive Mode, or Wait to Restore Time (min) are
different for the A End and Z End of a 2 Ended Bi (I) connection, the values from the
A End connection are set for the connection. A discrepancy is not reported for the
connection. The Network Elements Cross Connection list displays the values of all
three fields for each protection group.
• All Y-Cable ports must be on the same type of circuit pack.
The From OT Working Port, From OT Protection Port, To OT Working Port, and To
OT Protection Port must all be on the same type of circuit pack. Note that the
11STAR1 and 11STAR1A are considered the same type of circuit pack.
• All Y-Cable ports must use the same port number.
When selecting ports for To OT Working Port, From OT Protection Port, and To OT
Protection Port, the port must be the same port number on the same type of circuit
pack as that of the From OT Working Port.
• All Y-Cable ports must have a signal type that matches the service rate of the
connection.

Y-Cable Protection for 11DPE12 and 11DPE12E circuit packs

The following Y-cable protection guidelines apply to both 11DPE12 and 11DPE12E
circuit packs:
• Only the 1830 PSS-4 supports Y-cable protection for 11DPE12 and 11DPE12E circuit
packs.
• The packs containing the From OT Working Port, From OT Protection Port, To
OTWorking Port, and To OT Protection Port must all have the same Ethernet
Operational mode (Full Rate, Sub Rate, or QinQ mode).

Y-Cable provisioning for the 11DPM12 circuit pack

The following Y-Cable provisioning guidelines apply to the 11DPM12 circuit pack:
• The CTP on the From OT Working Port, From OT Protection Port, To OT Working
Port, and To OT Protection Port must be cross connected to a CTP on the Line Port 1
of the OT; they cannot be cross connected to a CTP on the Line Port 2 of the OT. If
not, the system displays the following message:
Y-cable protection only allowed with Line Port 1 of OT.
Example: The 11DPM12-[shelf]- [slot]-L1-1-8 can be cross connected to the From
OT Working Port, but the 11DPM12-[shelf]-[slot]-L2-1-8 cannot.
• The CTP on the Line Port that is cross connected to the From OT Working Port must
be the same CTP on the Line Port that is cross connected to the From OT Protection
Port; and the CTP on the Line Port that is cross connected to the To OT Working Port
must be the same CTP on the Line Port that is cross connected to the To OT
Protection Port. If not, the system displays the following message:

OS connections automatically created

When creating a DSR or ODUk service with Y-cable protection, the system automatically
creates the OS connections between the following:
• The working ports on the Y-cable circuit packs and the OTU client ports.
• The protected ports on the Y-cable circuit packs and the OTU client ports.
If the Connection Shape is 2 Ended Bi (I), these four OS connections are automatically
created:
• An OS connection is created between the Working Port on the A End Y-cable circuit
pack and the OTU client port that the user selects as the A End Working Port.
• An OS connection is created between the Protection Port on the A End Y-cable circuit
pack and the OTU client port that the user selects as the A End Protection Port.
• An OS connection is created between the Working Port on the Z End Y-cable circuit
pack and the OTU client port that the user selects as the Z End Working Port.
• An OS connection is created between the Protection Port on the Z End Y-cable circuit
pack and the OTU client port that the user selects as the Z End Protection Port.
If the Connection Shape is 3 Ended A Bi (Y), these two OS connections are automatically
created:
• An OS connection is created between the Working Port on the Z End Y-cable circuit
pack and the OTU client port that the user selects as the Z End Working Port.
• An OS connection is created between the Protection Port on the Z End Y-cable circuit
pack and the OTU client port that the user selects as the Z End Protection Port.
If the Connection Shape is 3 Ended Z Bi (Y), these two OS connections are automatically
created:
• An OS connection is created between the Working Port on the A End Y-cable circuit
pack and the OTU client port that the user selects as the A End Working Port.
• An OS connection is created between the Protection Port on the A End Y-cable circuit
pack and the OTU client port that the user selects as the A End Protection Port.
Note: If the From OT Working Port, From OT Protection Port, To OT Working Port, and
To OT Protection Port are on 11DPE12 or 11DPE12E circuit packs with the mode of
SubRate or QinQ, all of these automatically created OS connections are created except
that OS connections are only created for the first DSR connection that uses an OTU client
port.

Y-Cable modifications
For modifications of Y-Cable parameters, the following apply:
• If the connection shape is bidirectional, the Switch Mode displays the values of
Unidirectional and Bidirectional.
• If the Switch Mode is Bidirectional, the Revertive Mode is displayed and its default
value is the current value of the connection. If the connection does not have a current
value, the default is Disabled.
• If the Protection Type is Revertive, the Wait to Restore Time (min) is displayed
and its default value is the current value of the connection. If the connection does not
have a current value, the default is 5.

SNC Protection for 1830 PSS OCS NEs

SNC Protection defined
SNC Protection is a level of subnetwork connection protection (SNCP) that can be
specified for infrastructure connections (trails) or services to create protected cross
connections on 1830 PSS OCS NEs.

Best Practice templates for SNC Protection

SNC Protection provisioning

Users can provision SNC Protected connections for 1830 PSS OCS NEs. when they select
one of the following Best Practice templates:
• Infrastructure Trail, SNC-I Protected Uplink ODUk with L0 Restoration
• Infrastructure Trail, SNC-I Protected Uplink ODUk with L0 Restoration
• Infrastructure Trail, SNC-N Protected Uplink ODUk with L0 Restoration
• Infrastructure Trail, SNC-N Protected Uplink ODUk
• Service, SONET, SNC-NC Protected, OC-N with external 1+1 APS Protection
• Service, SDH, SNC-NC Protected, STM-N with external 1+1 MSP Protection
Thus users can specify and subsequently modify SNC Protection provisioning for service
and infrastructure connection parameters on the SNC Protection panel during connection
provisioning for 1830 PSS OCS NEs.
The users can specify SNC parameters for the following types of infrastructure
connections (trails) and services:
• For infrastructure connections (trails) and services in which the Connection Shape is
2 Ended Bi (I), 4 Ended Bi (X), 3 Ended A Bi (Y), or 3 Ended Z Bi (Y).
• For infrastructure connections (trails) and services in which the Routing field is set to
Automatic and the Protection Type field is set to Protected; or the Routing field is
set to Manual.

SNC Protection parameters

To implement SNC Protection during provisioning, users must specify whether the Client
Protection Type is to be one of the following:
• SNC-N, which is SNC protection for network ports.
• SNC-Nc, which is SNC Protection for network client ports.
• SNC-I, which is SNC protection with inherent monitoring.
• None, the default, which is no SNC protection.
For both service and infrastructure connections, the users can specify the following
optional parameters to further define SNC Protection for network ports:
• Client Hold Off Time (msec), which ranges from 0 to 10,000 in 20 msec increments
up to 100, and 100 msec increments thereafter until 10,000 msec, providing that the
Connection Shape specified is one of the supported Y or X connection shapes, which
are 3 Ended A Bi (Y), 3 Ended Z bi (Y), and 4 Ended Bi (X).
• Client Protected Protection Method, which can be specified as ODU Path NIM
protection or ODUk Path Adaptation, providing that the Connection Shape
specified is one of the supported Y or X connection shapes, which are 3 Ended A Bi
(Y), 3 Ended Z bi (Y), and 4 Ended Bi (X).
• Client Protecting Protection Method, which can be specified as ODU Path NIM
protection or ODUk Path Adaptation, providing that the Connection Shape
specified is one of the supported Y or X connection shapes, which are 3 Ended A Bi
(Y), 3 Ended Z bi (Y), and 4 Ended Bi (X).
• Client Signal Degrade for Protection Switching, which can be specified as Enable
or Disable, providing that the Connection Shape specified is one of the supported Y
or X connection shapes, which are 3 Ended A Bi (Y), 3 Ended Z bi (Y), and 4 Ended
Bi (X).
• Client Revertive Mode, which can be specified as Enable or Disable if the value of
the Client Protection Type is SNC-N or SNC-I.
• Client Wait to Restore Time (min), which can be specified as 1 to 15 minutes if the
value of the Client Protection Type is SNC-N or SNC-I.
• Network Protection Type, which can be SNC-N, SNC-I, or None, the default.
• Network Hold Off Time (msec), which ranges from 0 to 10,000 in 20 msec
increments up to 100, and 100 msec increments thereafter to 10,000 msec.
• Network Protected Protection Method, which can be specified as ODU Path NIM
protection or ODUk Path Adaptation.
• Network Protecting Protection Method, which can be specified as ODU Path NIM
protection or ODUk Path Adaptation.
....................................................................................................................................................................................................................................
4-70 Nokia 1350 OMS
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS ASON Provisioning SNC Protection for 1830 PSS OCS NEs
Connections Features
....................................................................................................................................................................................................................................
• Network Signal Degrade for Protection Switching, which can be specified as
Enable or Disable.
• Network Revertive Mode, which can be specified as Enable or Disable.
• Network Wait to Restore Time (min), which can be specified as 1 to 15 minutes.
Note the following guidelines for parameter activation:
• If the Client Protection Type parameter and/or the Network Protection Type
parameter is set to None, no other parameters are displayed either protection type.
• If the Client Protection Type is SNC-N or SNC-Nc, only the ODU Path NIM
protection parameter is displayed for the Client Protected Protection Method and
the Client Protecting Protection Method fields.
And, if the Network Protection Type is SNC-N, only the ODU Path NIM protection
parameter is displayed for the Network Protected Protection Method and the
Network Protecting Protection Method fields.
• If the Client Protection Type is SNC-I, only the ODU Path Adaptation parameter is
displayed for the Client Protected Protection Method and the Client Protecting
Protection Method fields.
And, if the Network Protection Type is SNC-I, only the ODU Path Adaptation
parameter is displayed for the Network Protected Protection Method and the
Network Protecting Protection Method fields.

SNC Protection and special 1830 PSS considerations

If at least one connection endpoint is on an 1830 PSS OCS NE and at least one
connection endpoint is on an 11DPM12 or 11QPA4 circuit pack on an 1830 PSS/PSS-4
NE, users must specify the Network Protection Type to be None or SNC-N.

SNC Protection panel display for rerouted connections

The SNC Protection panel is displayed for the reroute of WDM connections if the
Reroute type is Add Protection or Modify route and if the connection rate is ODUk.

OPSB Protection
Description
OPSB Protection is a type of protection that is afforded by an Optical Protection Switch
Board (OPSB), which is an 1830 PSS NE circuit pack that has a non-latching switch.
Users can create OPSB Protected service connections when they select one of the
following Best Practice templates
Service, SONET, OPSB Protected, OPSB Protected OC-N
Service, SDH, OPSB Protected, OPSB Protected STM-N

Supported circuit packs

The users can specify the from/to working and protection ports. The OTU circuit packs
that support OPSB protection are the following:
• 1QPA4
• 11STAR1
• 11STAR1A
• 11STMM10
In general, the NE allows OPSB Protection if the OPSB circuit pack, the OT working
port, and OT protection port are all on different shelves, or if all are on the same shelf, or
if two of the three packs are on the same shelf, but the third pack is on a different shelf.
However, since the OPSB is a non-latching switch, when power is removed, the default
switch position is the B port regardless if the B port is designated the working or
protection port. To prevent a single shelf failure, the OT port connected to the B port must
be a pack that is in a different shelf from the OPSB pack
Therefore, when one OT is in the same shelf as the OPSB pack and one OT is in a
different shelf from the OPSB pack, users must adhere to the following supported
configurations:
• The OPSB pack and the OT working port on the same shelf and the OT protection
port on a different shelf configuration is supported if the user specifies the OPSB A
port as the working port.
• The OPSB pack and the OT protection port on the same shelf and the OT working
port on a different shelf configuration is supported if the user specifies the OPSB B
port as the working port.

OT client ports and OPSB Protection

• The OT client ports that are connected to the OPSB A and B ports must have the same
frequency.
• The frequency for the OT client ports that are connected to the OPSB A and B ports
must be 1310 nm or 1500 nm.
• The OT client ports that are connected to the OPSB A and B ports must have the same
pluggable module type.

OPSB protection on OT client ports with client NNI in L0 Control Plane

• ASON manages the proper TP chain on the internal link
• The user can add links between OPSA and OTs to ASON NPA. See “Add and
Remove Links in ASON” (p. 6-29)
• The user sets up protected ODU infrastructure having two ASON SNCs on the main
and spare legs originated from the OPSB. ASON SNCs are terminated by ODU on
client side OT ports.

Nodes and Network Elements

Add a Node/NE
When to use
Use this task to add a node/NE.

Related information
See the following topic in this document:
• The OTN Guide for details on the NEs, Subnetworks, Nodes, Ports, and Cross
Connections.

Before you begin

You can also add/create a node/NE from the Operate > Network Map navigation path.
This task enables you to do the following:
• Add managed or external nodes/NEs.
• Add managed 1830 PSS PHN or 1830 PSS OCS nodes/NEs.
• Partner managed 1830 PSS PHN and 1830 PSS OCS nodes/NEs with other managed
1830 PSS PHN and 1830 PSS OCS nodes/NEs.
• For 1830 PSS PHN nodes, make Simple Network Management Protocol (SNMP)
communication and privacy assignments.
• Add 1830 TDM Extender (TDMX) and 1830 TDM Extender Compact (TMDXC)
information for a managed 1830 PSS PHN and/or 1830 PSS OCS node configuration.
This task includes the following parts:
• “Task: Add General Node Information” (p. 4-76)
• “Task: Add 1830 PSS PHN Node/NE Information” (p. 4-80)
• “Task: Add 1830 PSS OCS Node/NE Information” (p. 4-82)
• “Task: Add 1830 PSS-4, 1830 PSS-1AHP, 1830 PSS-1MDH4H, 1830 PSS-1MSAH,
and Generic Node/NE Information” (p. 4-84)
• “Task: Add 1830-TMDX, 1830-TDMXC, and 1626-LM Node/NE Information”
(p. 4-85)
• “Task: Add 1830 TDM Extender (TDMX) and TDM Extender Compact (TMDXC)
Information” (p. 4-86)
• “Task: Finish Creating the Node/NE or Create Another Node/NE” (p. 4-87)

1 From the WebUI, follow this navigation path:

Operate > Nodes
Result: The system displays a data table that lists all of the nodes.
...................................................................................................................................................................................................

2 Mouse over the icons on the top right and click on the Add Node icon.
Result: The system displays the Add Node/NE window, which defaults to Managed
Node.

Figure 4-18 Nodes – Add Node/NE – Default Window

...................................................................................................................................................................................................

3 In the Node Type field, click on the button for Managed Node or External Node.
Result: The system displays the appropriate general information for node/NE type for
your selection.
...................................................................................................................................................................................................

4 If you have selected Managed Node, go to Step 5.

If you have selected External Node, enter the User Label (the node/NE name); enter the
geographic Location of the node/NE; and go to the “Task: Finish Creating the Node/NE
or Create Another Node/NE” (p. 4-87) task.

5 If you selected Managed Node in the Type field, select the 1830 PSS NE that you want to
add. Options are 1830 PSS, 1830 PSS-4, 1830 PSS-1-AHP, 1830 PSS-1GBEH, 1830
PSS-1MD4H, 1830 PSS-1MSAH, 1830 PSS-TDMX, 1830 PSS-TDMXC, 1630-LM, or
GenericNE.
...................................................................................................................................................................................................

6 In the Release field, select the appropriate release number of the Node/NE that you want
to add from the drop-down list. The node/NE Type and Release defaults are as follows:
• 1830 PSS is 8.0.
• 1830 PSS-4 is 8.0.
• 1830 PSS-1-AHP is 1.0.
• 1830 PSS-1GBEH is 2.7.
• 1830 PSS-1MD4H is 1.9.
• 1830 PSS-1MSAH is 1.9.
• 1830 PSS-TDMX is 2.3.
• 1830 PSS-TDMXC is 2.3.
• 1636-LM is 7.6.
• Generic NE is 1621SLE-2.1.
...................................................................................................................................................................................................

7 In the EML field, select EML_1, which is the default domain.

Provisioning Note: The Element Management Level defaults to the EML_1 domain to
force the assignment of the NE that is being added to this domain. By forcing the
assignment of the node/NE into a particular domain, the system ensures that the domain
only contains NEs of a certain Type and Release.
...................................................................................................................................................................................................

8 In the EMLIM field, select 100 (TCPNA) or 101 (tcplan3).

Note: EMLIMs are Network Adapter (NA) processes, or protocol adapters, that enable
the Element Management Level to be established and summarize the communication state
that operates with different management interfaces and DCN protocols that run in the NEs
such as: Q3, SNMP, TL1, 4G-EMLIM, SNA.
...................................................................................................................................................................................................

9 In the ACD (Access Control Domain) field, select unknown, which is the default.
...................................................................................................................................................................................................

10 In the User Label field, enter a string of characters to identify the node/NE.
....................................................................................................................................................................................................................................
Nokia 1350 OMS 4-77
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS ASON Provisioning Add a Node/NE
Nodes and Network Elements
....................................................................................................................................................................................................................................
Provisioning Note: The string of characters can be a combination of alphanumeric and
special characters. The system checks the maximum length of the User Label and
prevents duplication. For TL1 NEs, the system manages a specific User Label length (in
accordance with the TID) and character set. The 1830 PSS OCS and 1830 PSS PHN NEs
support a maximum of 20 characters in the User Label.
...................................................................................................................................................................................................

11 In the Location field, enter a string of characters that identifies the geographic location
where the node/NE resides.
...................................................................................................................................................................................................

12 For 1830 PSS nodes/NEs only, check the PHN (photonic) and/or OCS (Optical Core
Switching) fields to specify whether the node/NE is a photonic or Optical Core Switching
node/NE.
Result: The system displays the appropriate PHN and/or OCS User Label tab along
with the appropriate number of UserLabel#TDx and UserLabel#TCx tabs.

Figure 4-19 Nodes – Add Node/NE – 1830 PSS PHN User Label Tab

...................................................................................................................................................................................................

13 In the TDMX and TDMXC fields, use the drop-down list to specify the number of TDM
Extenders (TDMX) and TDM Extender Compacts (TDMXC) in the configuration to be 0,
1, 2, 3, or 4.
Result: The system displays the appropriate number of UserLabel#TDx and
UserLabel#TCx tabs.

Figure 4-21 Nodes – Add Node/NE – TDMX Tab

Figure 4-22 Nodes – Add Node/NE – TDMXC Tab

...................................................................................................................................................................................................

14 In the Comments field, enter any information that can further identify or clarify the
node/NE that you are adding.

15 For 1830 PSS nodes/NEs only, if you checked the PHN to add an 1830 PSS photonic
node/NE, go to the “Task: Add 1830 PSS PHN Node/NE Information” (p. 4-80) and/or
the “Task: Add 1830 TDM Extender (TDMX) and TDM Extender Compact (TMDXC)
Information” (p. 4-86) task.
For 1830 PSS nodes/NEs only, if you checked OCS to add an 1830 PSS Optical Core
Switching node/NE, go to the “Task: Add 1830 PSS OCS Node/NE Information”
(p. 4-82) and/or the “Task: Add 1830 TDM Extender (TDMX) and TDM Extender
Compact (TMDXC) Information” (p. 4-86) task.
For 1830-TMDX, 1830-TDMXC, and 1626-LM nodes, go to the “Task: Add
1830-TMDX, 1830-TDMXC, and 1626-LM Node/NE Information” (p. 4-85) task.
For 1830 PSS-4, 1830 PSS-1AHP, 1830 PSS-1MDH4H, 1830 PSS-1MSAH, go to the
“Task: Add 1830 PSS-4, 1830 PSS-1AHP, 1830 PSS-1MDH4H, 1830 PSS-1MSAH, and
Generic Node/NE Information” (p. 4-84) task.
For TDM Extenders (TDMXs) and TDM Extender Compacts (TMDXCs), go to the
“Task: Add 1830 TDM Extender (TDMX) and TDM Extender Compact (TMDXC)
Information” (p. 4-86) task.
E...................................................................................................................................................................................................
N D O F S T E P S

Task: Add 1830 PSS PHN Node/NE Information

Complete the following steps to add 1830 PSS PHN node/NE information.
...................................................................................................................................................................................................

1 From the WebUI, follow this navigation path:

2 For 1830 PSS nodes/NEs only, check or uncheck the Shared User Name field, which
specifies whether node/NE will require a user name and password for access.
Result: If you check the Shared User Name field, the system activates the User
Name and Password fields.
...................................................................................................................................................................................................

3 For 1830 PSS nodes/NEs only, if you checked the Shared User Name field, enter a User
Name and Password for access to the node/NE.

4 In the Release field, enter the release of the 1830 PSS PHN node/NE. The 1830 PSS
defaults to 8.0.
...................................................................................................................................................................................................

5 In the Address field, enter an address for the 1830 PSS PHN node/NE.
...................................................................................................................................................................................................

6 In the Partner Address field, enter the address of the node/NE that is partnered with the
1830 PSS PHN node/NE that you are adding.
...................................................................................................................................................................................................

7 In the User Name field, enter a name to be used to access the node/NE.
...................................................................................................................................................................................................

8 In the Password field, enter the password to be used to access the node/NE.
...................................................................................................................................................................................................

9 In the SNMP Version field, select the SNMP version from the drop-down list. Options are
V3 or V2C (the default).
Result: The system activates the appropriate fields depending on your selection.
...................................................................................................................................................................................................

10 If the SNMP Version is V2C, in the Read Community and Write Community, enter the
appropriate private information by typing over the security dots and go to Step 17.
...................................................................................................................................................................................................

11 If the SNMP Version is V3, in the Security Level field, AuthorizationPrivacy

(communication with authentication and privacy), which is the default.
...................................................................................................................................................................................................

12 If the SNMP Version is V3, in the USM user field, select v3DefaultUser, which is the
default.
Explanation: The USM user (User-based Security Model) provides authentication and
privacy (encryption) functions and operates at the message level.
...................................................................................................................................................................................................

13 If the SNMP Version is V3, in the USM Authentication Password field, enter the
appropriate private information by typing over the security dots.
...................................................................................................................................................................................................

14 If the SNMP Version is V3, in the USM Privacy Password field, enter the appropriate
private information by typing over the security dots.

15 If the SNMP Version is V3, in the Authentication Method field, select a method from the
drop-down list. Options are HMAC-MD5 (the default) or HMAC-SHA.
Explanation: HMAC is a keyed-hash message authentication code. MD5 and SHA are
cryptographic hash functions that can be used to calculate an HMAC; the MAC algorithm
is called HMAC-MD5 or HMAC-SHA.
...................................................................................................................................................................................................

16 If the SNMP Version is V3, in the Privacy Method field, select a method from the
drop-down list. Options are DES (Data Encryption Standard, the default) or AES-128
(Advanced Encryption Standard-123).
Explanation: DES and AES-128 are encryption support files.
...................................................................................................................................................................................................

17 Do one of the following:

• If want to add an 1830 PSS OCS NE, go to the “Task: Add 1830 PSS OCS Node/NE
Information” (p. 4-82) task to complete the remaining steps.
• If want to add 1830 TDM Extender (TDMX) and/or TDM Extender Compact
(TMDXC) Information, go to the “Task: Add 1830 TDM Extender (TDMX) and TDM
Extender Compact (TMDXC) Information” (p. 4-86) task to complete the remaining
steps.
• If you are finished, go to the “Task: Finish Creating the Node/NE or Create Another
Node/NE” (p. 4-87) task to complete the remaining steps.
E...................................................................................................................................................................................................
N D O F S T E P S

Task: Add 1830 PSS OCS Node/NE Information

Complete the following steps to add 1830 PSS OCS node/NE information.
...................................................................................................................................................................................................

1 From the WebUI, follow this navigation path:

2 For 1830 PSS nodes/NEs only, check or uncheck the Shared User Name field, which
specifies whether node/NE will require a user name and password for access.

3 For 1830 PSS nodes/NEs only, if you checked the Shared User Name field, enter a User
Name and Password for access to the node/NE.
...................................................................................................................................................................................................

4 In the Release field, enter the release of the 1830 PSS OCS node/NE. The 1830 PSS
defaults to 8.0.
...................................................................................................................................................................................................

5 In the Target Identifier (TID) field, specify the TID for the node/NE being added.
...................................................................................................................................................................................................

6 In the Address field, enter an address for the 1830 PSS OCS node/NE.
...................................................................................................................................................................................................

7 In the Partner Address field, enter the address of the node/NE that is partnered with the
1830 PSS OCS node/NE that you are adding.
...................................................................................................................................................................................................

8 In the User Name field, enter a name to be used to access the partnered node/NE.
...................................................................................................................................................................................................

9 In the Password field, enter the password to be used to access the partnered node/NE.
...................................................................................................................................................................................................

10 In the Secure Communication (TL1) field, select None or SSH2 from the drop-down list.
Explanation: Secure Shell (SSH) is a cryptographic network protocol for secure data
communication, remote command-line login, remote command execution, and other
secure network services between two networked devices. SSH-2, which is an updated
SSH protocol features both security and feature improvements.
Result: If Secure Communication (TL1) is SSH2, the system activates the Public Key
field.
...................................................................................................................................................................................................

11 If Secure Communication (TL1) is SSH2, in the Public Key File field, select DEFAULT,
which is the default, from the drop-down list.
...................................................................................................................................................................................................

12 Do one of the following:

• If want to add an 1830 PSS PSS NE, go to the “Task: Add 1830 PSS PHN Node/NE
Information” (p. 4-80) task to complete the remaining steps.
....................................................................................................................................................................................................................................
Nokia 1350 OMS 4-83
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS ASON Provisioning Add a Node/NE
Nodes and Network Elements
....................................................................................................................................................................................................................................
• If want to add 1830 TDM Extender (TDMX) and/or TDM Extender Compact
(TMDXC) Information, go to the “Task: Add 1830 TDM Extender (TDMX) and TDM
Extender Compact (TMDXC) Information” (p. 4-86) task to complete the remaining
steps.
• If you are finished, go to the “Task: Finish Creating the Node/NE or Create Another
Node/NE” (p. 4-87) task to complete the remaining steps.
E...................................................................................................................................................................................................
N D O F S T E P S

Task: Add 1830 PSS-4, 1830 PSS-1AHP, 1830 PSS-1MDH4H, 1830 PSS-1MSAH, and Generic Node/NE
Information
Complete the following steps to add 1830 PSS-4, 1830 PSS-1AHP, 1830 PSS-1MDH4H,
1830 PSS-1MSAH, and Generic node/NE information.
...................................................................................................................................................................................................

1 In the Address field, enter an address for the node/NE.

...................................................................................................................................................................................................

2 In the SNMP Version field, select the SNMP version from the drop-down list. Options are
V3, VC1, V2C (the default).
Result: The system activates the appropriate fields depending on your selection.
...................................................................................................................................................................................................

3 In the User Name field, enter a name to be used to access the node/NE.
...................................................................................................................................................................................................

4 In the Password field, enter the password to be used to access the node/NE.
...................................................................................................................................................................................................

5 If the SNMP Version is VC1 or V2C, in the Read Community and Write Community,
enter the appropriate private information by typing over the security dots and go to Step
12.
...................................................................................................................................................................................................

6 If the SNMP Version is V3, in the Security Level field, AuthorizationPrivacy

7 If the SNMP Version is V3, in the USM User field, select v3DefaultUser, which is the
default.
Explanation: The USM user (User-based Security Model) provides authentication and
privacy (encryption) functions and operates at the message level.
....................................................................................................................................................................................................................................
4-84 Nokia 1350 OMS
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS ASON Provisioning Add a Node/NE
Nodes and Network Elements
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

8 If the SNMP Version is V3, in the USM Authentication Password field, enter the
appropriate private information by typing over the security dots.
...................................................................................................................................................................................................

9 If the SNMP Version is V3, in the USM Privacy Password field, enter the appropriate
private information by typing over the security dots.
...................................................................................................................................................................................................

10 If the SNMP Version is V3, in the Authentication Method field, select a method from the
drop-down list. For 1830 PSS-4 NEs, options are HMAC-MD5 (the default) or HMAC-SHA.
For all other NEs, the default and only option is HMAC-MD5.
Explanation: HMAC is a keyed-hash message authentication code. MD5 and SHA are
cryptographic hash functions that can be used to calculate an HMAC; the MAC algorithm
is called HMAC-MD5 or HMAC-SHA.
...................................................................................................................................................................................................

11 If the SNMP Version is V3, in the Privacy Method field, select a method from the
drop-down list. For 1830 PSS-4 NEs, options are DES (Data Encryption Standard, the
default) or AES-128 (Advanced Encryption Standard-123). For all other NEs, the default
and only option is AES-128.
Explanation: DES and AES-128 are encryption support files.
...................................................................................................................................................................................................

12 If you are finished, go to the “Task: Finish Creating the Node/NE or Create Another
Node/NE” (p. 4-87) task to complete the remaining steps.
E...................................................................................................................................................................................................
N D O F S T E P S

Task: Add 1830-TMDX, 1830-TDMXC, and 1626-LM Node/NE Information

Complete the following steps to add 1830 PSS-TDMX, 1830 PSS-TDMXC, or 1630-LM
node/NE information.
...................................................................................................................................................................................................

1 In the Target Identifier (TID) field, specify the TID for the node/NE that is being added.
...................................................................................................................................................................................................

2 In the Address field, enter an address for the node/NE that is being added
...................................................................................................................................................................................................

3 In the User Name field, enter a name to be used to access the node/NE that is being
added.
....................................................................................................................................................................................................................................
Nokia 1350 OMS 4-85
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS ASON Provisioning Add a Node/NE
Nodes and Network Elements
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

4 In the Password field, enter the password to be used to access the node/NE that is being
added.
...................................................................................................................................................................................................

5 If you are finished, go to the “Task: Finish Creating the Node/NE or Create Another
Node/NE” (p. 4-87) task to complete the remaining steps.
E...................................................................................................................................................................................................
N D O F S T E P S

Task: Add 1830 TDM Extender (TDMX) and TDM Extender Compact (TMDXC) Information
Complete the following steps to add 1830 PSS TDM Extender (TDMX) and 1830 PSS
TDM Extender Compact (TMDXC) information for 1830 PSS PHN and 1830 PSS OCS
Nodes/NEs. Depending on how many TDMXs and TMDXCs you add, the system opens
the appropriate number of tabs and names the Target Identifier (TID) field for the TDMX
and TMDXC as TDx and TCx, respectively; where: x is the number of TDMXs or
TMDXCs you have specified.
...................................................................................................................................................................................................

1 In the User Name field, specify a name for the TDMX and/or TMDXC that is being
added.
...................................................................................................................................................................................................

2 Skip the Release field; the system defaults the release to 2.3.
...................................................................................................................................................................................................

3 In the Address field, enter an address to be used to access TDMX and/or TMDXC that is
being added.
...................................................................................................................................................................................................

4 In the Password field, enter the password to be used to access TDMX and/or TMDXC
that is being added.
...................................................................................................................................................................................................

5 If you are finished, go to the “Task: Finish Creating the Node/NE or Create Another
Node/NE” (p. 4-87) task to complete the remaining steps.

1 Optional: To create another node/NE, click the Create Another button and reuse the
steps in any of the previous tasks.
...................................................................................................................................................................................................

2 Click the Create button.

Result: The system creates the node; and after the Nodes list is refreshed, the new
node/NE is displayed on the Nodes list.
...................................................................................................................................................................................................

3 Optional: To view the newly created node, refresh the nodes list.
Result: The newly created node is displayed on the Nodes list.
E...................................................................................................................................................................................................
N D O F S T E P S

Synchronize Nodes and NEs

Synchronize Nodes and NEs with its Associated Objects
Starting from the nodes or NEs list, te associated objects that can be synchronized are
reachable doing one of the following
• Right-click on the node and follow one of these paths:
Synchronize > NE Parameters, Equipments, Ports, Alarms, Internal Links, Protection
Groups, Cross Connections, Subnetwork Connections, Paths * , Transmission
Parameters * , ASAPs * , Ethernet Ports , Full * , Synchronization Failure Report
• Select the node. Mouse over the icons on the top right, locate and click on the
Synchronize icon, and follow one of these paths:
NE Parameters, Equipments. Ports, Alarms, Internal Links, Protection Groups, Cross
Connections, Subnetwork Connections, Paths (OTN) *, Transmission Parameters *,
ASAPs (OTN) *, Ethernet Ports, Full *,
* Important!
The ability to synchronize certain node/NE objects depends on the setting of the Network
Master Elementary View (EA.NTW_MASTER_ELE_VIEW) installation parameter,
which enables the network master elementary view for listen only cross-connect based
systems. When this installation parameter is enabled (ON), the Paths, Transmission
Parameters, and ASAPs are disabled. In addition, when this installation parameter is
enabled (ON), the Full synchronization excludes the synchronization of the Paths,
Transmission Parameters, and ASAPs objects.
The Status column in the Logs list shows the status of Executing... When the
synchronization completes successfully, the information bar on the bottom of the window
displays the following output: The action is successfully terminated. The Logs list
displays the status of Successful in the Status column.
You can also synchronize a selected node/NE with its associated objects from the
Network Map.

Overview
Purpose
Part II of the document explains the working of ASON in 1350 OMS.

Contents

Chapter 5, 1350 OMS ASON WebUI 5-1

Chapter 6, 1350 OMS WebUI – Working in ASON 6-1

Overview
Purpose
This chapter provides an overview of ASON navigation and ASON UI.

Contents

Navigate to ASON 5-2

NPA and SNC: Icons 5-3
NPA and SNC: Tabs 5-8
3R Tab 5-9
ASON SNCs tab of ASON NPA 5-10
Alarms tab 5-13
Control Planes tab of ASON NPA 5-15
End Points Tab of ASON SNCs 5-19
Links tab of ASON NPA 5-22
Nodes tab of ASON NPA 5-26
Nominal Route Problems Tab 5-29
Properties Tab of ASON NPA 5-31
Routes tab of ASON SNCs 5-33
SNCP tab of ASOn SNCs 5-35
TE Links tab of ASON NPA 5-36
Save and Reset Table Preferences 5-40
Export a Data Table to a .CSV File 5-43

Navigate to ASON
When to use
Use this task to navigate to ASON part of the 1350 OMS application.

Related information
This task does not have any related information.

Before you begin

This task does not have any preconditions.

Task
Complete the following steps to navigate to ASON part of the 1350 OMS application.
...................................................................................................................................................................................................

1 From the OTN WebUI, follow the navigation path:

Operate > ASON >NPAs
Operate > ASON > SNCs
Result: Based on the navigation, the system displays the list of NPAs or SNCs.
NPA, which is Network Protection Architecture, is a set of NEs, protections blocks,
and physical links that work together to create a dedicated protection mechanism or
are grouped together to establish a service layer protection.
SNC, which is a Subnetwork Connection, is a WDM ODU0, ODU1, or ODU4 layer
that connects user-selected primary and spare endpoints. An SNC is further defined by
its connection shape, its support of Tandem Connection Monitoring (TCM), and its
sets of Control Plane restoration parameters and color parameter.
...................................................................................................................................................................................................

2 To perform any user functions in the NPA or SNC record, click any one of the icons.
When the users click on any icon, the system navigates them to the function that the icon
performs for the selected object.
...................................................................................................................................................................................................

3 To view the specific details, such as Alarms, TE Links, and so on, click each tab of the
NPA or SNC page.
E...................................................................................................................................................................................................
N D O F S T E P S

NPA and SNC: Icons

The icons that are displayed on the 1350 OMS OTN WebUI represent the user functions.
When the user clicks on any icon, the system navigates them to the function that the icon
performs for the selected object. Some icons drop-down to the right of the icon. When the
user clicks on the list, there is an option to perform additional operations. The icons are
displayed on the right side top corner of the upper panel and lower panel. This section
lists the icons that are displayed along with a data table and those icons that are displayed
outside of a data table.

Table 5-1 NPA Icons

Icons Icon Names Description

Create Creates an NPA
In the Node tab of ASON
NPA, this icon depicts
creating a new node.
Implement Enabled when the
Configuration State of NPA
is in Deimplement state. This
operation cannot be
performed if the
Administrative State of NPA
is in Locked state.
Deimplement Enabled when the
Configuration State of NPA
is in Implement state. This
operation cannot be
performed if the link
associated to it is in Locked
state
Add Links to ASON Adds UNI and I-NNI links in
the ASON domain. Enabled
for NPAs that are in the
Implemented or Partially
Implemented Configuration
State.
This icon is available in
ASON NPA main page, and
also on the Links tab of
ASON NPA.

Icons Icon Names Description

Jobs Displays the current NPA jobs
that are run.
This icon is available in
ASON NPA main page,
Control Planes, Links, TE
Links, ASON SNCs tabs and
pages.
Remove Removes the NPA from the
system.
The user can remove an NPA
if all the links that are added
to the NPA are unassigned
from the NPA. Else, the
system displays an error.
Save Table Preferences Saves all the changes that has
been set in the table.
This icon is available in the
ASON NPA page and in all
the individual tabs.
Reset Table Preferences to Resets the changes that the
Default user would have set in the
table, that is, resets the data
table preferences to the
defaults and instantly
refreshes the table with the
defaults.
This icon is available in the
ASON NPA page and in all
the individual tabs.
Export to csv Exports the csv file to a
location in the user local
system
Start/Stop Autorefresh Based on the selection,
enables or disables auto
refresh of the records.

Icons Icon Names Description

Refresh Refreshes the records
This icon is available in the
ASON NPA page and in all
the individual tabs.
Start/Stop Autorefresh This icon is available in
Alarms tab of ASON NPA.
Based on the selection,
enables or disables auto
refresh of the records.
Synchronize This icon is available in the
Nodes tab of the ASON NPA
Provides the synchronization
options for the following:
• NE Parameters
• Equipments
• Ports
• Alarms
• Internal Links
• Protection Groups
• Cross Connections
• Subnetwork connections
• Paths
• Transmission Parameters
Discover External Physical Discovers external physical
Links links that are available.
This icon is available in the
Nodes tab of ASON NPA.
Modify Node Modifies the node
This icon is available in the
Nodes tab of the ASON NPA.
Supervision Starts or stops the supervision
of the node.
This icon is available in the
Nodes tab of ASOn NPA.

Icons Icon Names Description

Configure This icon is available in the
Nodes tab of ASON NPA
Configures the following:
• Global Remote Inventory
• Ping Nodes(s)
• Configure SSH and
SNMP
• MIB Backup
• Download Disable
NEs Synchronization Synchronizes the NE
This icon is available in the
Nodes tab of ASON NPA.
Administrative This icon is available in the
Links tab of ASON NPA
Sets the Administrative state
• to Unlocked
• to Shutting Down
• To Soft Shutting Down
• To Locked
• Synchronize
Remove Links from ASON Removes links from ASON
This icon is available in the
Links tab of ASON NPA

Configure Configures the following in

the 3R tab of ASON NPA
• Implement
• Add to Npa
• Remove Links from
ASON
Save Saves the property settings.
This icon is available in the
Properties tab of NPA.
Help Enables the user to access the
information related to a
particular window.

Table 5-2 SNC Icons

Icons Icon Names Description

Jobs Displays the current SNC jobs
that are run

Save Table Preferences Saves all the changes that has

been set in the table.

Reset Table Preferences to Resets the changes that the

Default user would have set in the
table, that is, resets the data
table preferences to the
defaults and instantly
refreshes the table with the
defaults.
Export to CSV file Saves the Log history in your
local system.

Refresh Refreshes the records

Start/Stop Autorefresh Based on the selection,

enables or disables auto
refresh of the records.
Help Enable to access the
information related to a
particular window.

NPA and SNC: Tabs

Overview
Tabs provides all of the information that is related to a particular network management
object. Tab, when selected, can navigate the users to additional information related to a
particular network management object.
In most instances, tabbed topics are located directly below the data table of the selected
network management object. In some other instances, tabbed topics are located directly to
the left of the data table of the selected network management object.

Tabbed topics and hyperlinks in the data tables

When the users click on an object in a data table in any other column other than the
hyperlink name for the object, the system activates the tabbed topics for the selected
object in the same browser window, directly below the original data table. When the users
click or double-click an object that has hyperlink in the data table, the system displays the
tabbed topic information that is particular to the selected object in a new browser window.
The users can return to the original browser window by clicking the back arrow.

Tabbed topics and the Expand and collapse icons

When the users click the Expand icon, which is two up arrows that are located to the
upper right of the tabbed topics, they can view the tabbed topics in a full window. Once
the tabbed topics are expanded in a new window, users can then click on the collapse
icon, which is two down arrows that are located to the upper right of the tabbed topics, to
return to the original split window.

3R Tab
What is a 3R tab
A 3R is a user-selected optical regeneration group that consists of a node and two NNI
transponder line ports that reshape, retime, and retransmit a signal; hence, the name 3R.

3R tab display
For information on the operations of the icons, see “NPA and SNC: Icons” (p. 5-3).
Click the plus icon on the right side corner of the data table to customize the columns. See
“ Save and Reset Table Preferences” (p. 5-40).

Figure 5-1 3R tab

The user can perform the following operations when you select and right-click an object
in the 3R tab:
• Create a 3R
• Implement or Deimplement an existing 3R
• Add a 3R to an existing NPA
• Add or remove links for ASON
• Remove a 3R from an existing NPA.
For more details on all the operations, see “Manage 3Rs” (p. 6-63).

ASON SNCs tab of ASON NPA

What is ASON SNC tab
An ASON SNC can be a WDM ODU0, ODU1, or ODU4 layer that connects
user-selected primary and spare endpoints. An ASON SNC can be further defined by its
connection shape, its support of Tandem Connection Monitoring (TCM), and its sets of
Control Plane restoration parameters and Color parameters

ASON SNCs display

Navigate to the data table for ASON SNCs directly from the Operate > ASON > SNCs
navigation path. The user can perform the same icon and right click functions and actions
from the ASON SNCs tab in the Infrastructure Connections and Network Profiles tabs.

Figure 5-2 ASON SNCs tab

For information on the operations of the icons, see Chapter 5, “1350 OMS ASON WebUI
”.
Click the plus icon on the right side corner of the data table to customize the columns.
Click the Attribute icon to view the additional attributes of an object.

Figure 5-3 ASON SNCs tab: additional attributes

ASON SNC tab icon and/or right click actions

Right-click the selected object in the data table of ASON SNC tab.
The system displays the following operations:
• Explore. See “Explore an SNC on the Routing Display” (p. 6-104).
• Display Route on Map. See “View an SNC on the Network Map” (p. 6-85).
• Convert Current to Nominal. See “Switch SNC Routes” (p. 6-114).
• Enable Test Mode. See “Enable/Disable the Test Mode for an SNC” (p. 6-102).
• Disable Test Mode. See “Enable/Disable the Test Mode for an SNC” (p. 6-102)
• Switch to Nominal. See “Switch SNC Routes” (p. 6-114).
• Switch to Backup. See “Switch SNC Routes” (p. 6-114).
• Modify Attributes. See “ Modify the Attributes of an SNC” (p. 6-111).

Figure 5-4 ASON SNCs tab: right-click operations

Alarms tab
What is an Alarm
An Alarm is an visual and/or audible indication to the user from the equipment that a
Critical, Major, Minor, or Warning event has occurred.
For information on ASON related alarms correlation and rules, see Appendix A, “ASON
Alarm and Correlation ”.

Alarms tab display

The Alarms tab of the ASON NPA and ASON SNC enables the user to view the list of
alarms and alarmed connections in the 1350 OMS OTN ASON NPA and ASON SNC
applications.

Figure 5-5 Alarms tab of ASON NPA

Figure 5-6 Alarms tab of ASON SNC

For information on the operations of the icons, see “NPA and SNC: Icons” (p. 5-3).
....................................................................................................................................................................................................................................
Nokia 1350 OMS 5-13
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS ASON WebUI Alarms tab

The Control Planes tab displays the following columns:

• Name
• Severity
• Alarm Time
• Object Label
• Service Affecting
• ID
• Acknowledge Status
• Acknowledge Time
• Acknowledge UserName
• Correlated Object Type
• Parent ID

Control Planes tab of ASON NPA

The Control Plane is a generalized term that is used to represent the portion of the
network or a connection that uses ASON GMPLS. In case of a failure, the Control Plane
is the operating plane in which pure ASON connections enable the network to reroute
connections.

Control Planes tab display

The Control Planes helps to manage the Control Planes for a selected NPA.
Note: Fast photonic restoration is only available for 1830 PSS PHN nodes. It is not
available for 1830 PSS OCS nodes. The Control Planes tab provides the same actions
and functions as the Control Planes tab that is displayed for Nodes. This task
redirects the user to the same tasks that are documented for Operate > Nodes.

Figure 5-7 Control Planes tab of ASON

Figure 5-8 Control Planes tab: additional attributes

Control Planes tab icon and/or right click actions

Right-click any selected record in the data table. The system provides the users an option
to activate the automatic restoration of the Control Plane and to view the job list.

Figure 5-9 Control Planes: right-click actions

To activate or deactivate auto restoration, selectAuto Restoration > Activate or Auto

Restoration > Deactivate. For more information, see “Activate/Deactivate Auto
Restoration of the Control Plane for an NPA” (p. 6-40).
To view the job list, select Jobs. For more information, see “Manage Jobs in ASON”
(p. 6-72).

End Points Tab of ASON SNCs

What is a End Points
The end points displays the end points that are required for the provisioning.

End Points tab display

The End Points tab displays the end point type, that is, A or Z end point type.

Figure 5-10 End Points tab

For information on the operations of the icons, see Chapter 5, “1350 OMS ASON WebUI
”.
Click the plus icon on the right side corner of the data table to customize the columns.

Figure 5-11 End Points tab: additional attributes

Click the hyperlink in the Node User Label field in the data table to navigate to NPAs TE
Links page.

The End Points tab displays the following fields:

• endType
• Resource Type
• Node UserLabel

Links tab of ASON NPA

What is Links tab
The Links tab helps to access the Link Maintenance window and to view the Link
Maintenance data table and its tabbed topics.

Links tab display

The Links tab enables the user to view NPA related link information in data table format.

Figure 5-12 Links tab of ASON NPA

The Links tab displays the following columns:

• Alarm Status
• Operational State
• Name
• Administrative State
• Link Type
• Category
• 3R Resource
• TE Link Name
• SRG Present
• From NE/Port #1
....................................................................................................................................................................................................................................
5-22 Nokia 1350 OMS
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS ASON WebUI Links tab of ASON NPA

Figure 5-13 Links tab: additional attributes

Links tab icon and/or right click actions

Right-click the selected object in the data table of the Links tab.

Figure 5-14 Links tab: right-click operations

The following options are displayed:

• Administrative State: Set to Unlocked, Set to Shutting Down, Set to Soft Shutting
Down, Set to Locked, Synchronize.
• Link Maintenance Window
See “Perform Link Maintenance” (p. 6-53).
• Change ASON WTR
• Auto Restoration
See “Change ASON WTR” (p. 6-50).
• Remove Links from ASON
See “Add and Remove Links in ASON” (p. 6-29).
• TE Link Assignment
See “Assign an ASON I-NNI Link to a TE Link and/or an SRG” (p. 6-43).
• Misalignment Reports
See “Access and View the Misalignment Report for a Link” (p. 6-39).
• Jobs
See “Manage Jobs in ASON” (p. 6-72).

Nodes tab of ASON NPA

A node is a single NE or two NEs that are linked together and are treated as a single unit.
The user can also access the information related to nodes in the Operate > Nodes page of
1350 OMS OTN application.

Nodes tab display

Depending on the node that is selected and its current state, the Nodes tab has icons and
right-clicks for the actions or functions.

Figure 5-15 Node tab of ASON NPA

Nodes tab icon and/or right click actions

Right-click the selected object in the data table of Nodes tab.
The system displays the following operations:
• Synchronize
• Discover External Physical Links
• Modify Node
• Delete Node
• Supervision
• Global Remote Inventory
• Ping Nodes(s)
• Configure SSH and SNMP
....................................................................................................................................................................................................................................
Nokia 1350 OMS 5-27
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS ASON WebUI Nodes tab of ASON NPA

For information on the Nodes tab, refer to 1350 OMS OTN Guide.

Nominal Route Problems Tab

What is a nominal route
A nominal route is the initial route of a connection through the Automatic Switched
Optical Network (Control Plane, G.7718). For optical connections, the user would set up
the nominal route in conjunction with the Engineering and Planning Tool (EPT) to
establish an optimal route through the network. The route that a connection takes through
the network is known as the current route. In most cases, the current route and the
nominal route are the same. If a failure occurs, ASON reroutes traffic around the failure
automatically and restores the service.
So, a nominal route problem is a problem (an alarm severity type) that the system has
detected on an Implemented ASON subnetwork connection (SNC) that is in the Nominal
Route.

Nominal Route Problems tab display

The Nominal Route Problems tab is displayed for the Dashboard and SNC objects
The navigation paths for this tab are as follows
Operate > ASON > SNCs > Nominal Route Problems (tab) Nominal Route.

Figure 5-16 Nominal Route Problems tab

Nominal Route Problems tab icon and/or right click table actions
Depending on the type of connection that is selected and its current state, the Nominal
Route Problems tab only displays the common set of OTNWebUI icons. The right-click
actions are not allowed.
For information on the operations of the icons, see Chapter 5, “1350 OMS ASON WebUI
”.

Properties Tab of ASON NPA

What is a Properties tab
The Properties tab enables the users to set or modify the required parameter settings
depending on the needs.

Properties tab display

Expand each of the fields in the Properties tab to view and edit the fields and set a new
option.
For information on the operations of the icons, see Chapter 5, “1350 OMS ASON WebUI
”,

Figure 5-17 Properties tab: ASON NPA

Click the right arrow to the left of the panel name to expand the panel. click the down
arrow next to the field name and select a new option.
To save your modifications, click the Save icon, which is located in the upper right corner
of the window. The system displays a success message at the bottom of the window.

Routes tab of ASON SNCs

What is a Route
Route is the way that the connection takes in a network.
The initial set up of a connection in ASON involves the establishment of the nominal
route, which is the initial route though the network.
The route that a connection takes through the network is known as the current route. In
most cases, the current route and the nominal route are the same.
If a failure occurs, ASON reroutes traffic around the failure automatically and restores the
service. The current route follows a path that differs from the nominal route. Once the
failure is repaired, the traffic can be switched back to the nominal route to ensure optimal
routing through the network. The 1350 OMS system stores the details of the nominal
route and retrieves the current route upon demand when needed.

Routes tab display

The Routes tab displays a split screen for the Nominal Route and Current Route data
tables.

Figure 5-19 Routes tab

Select the hyperlink in the Nominal Route fields to display the details of the nominal
route
For information on the operations of the icons, see Chapter 5, “1350 OMS ASON WebUI
”.
Click the plus icon on the right side corner of the data table to customize the columns.
Click the plus icon on the right side corner of the data table to customize the columns. See
“ Save and Reset Table Preferences” (p. 5-40).
To export to .csv file, see “Export a Data Table to a .CSV File” (p. 5-43).

SNCP tab of ASOn SNCs

What is a SNCP
The Simple Network Management Protocol (SNCP) is a protection switching for a
protected connection.

SNCP tab display

The SNCP tab displays the SNC-related information either directly below the data table
for the SNC or in a new browser window. The SNCP tab is displayed if the Protection is
set to SNCP and the Configuration State is Implemented.

Figure 5-20 SNCP tab

TE Links tab of ASON NPA

What is a TE Link
A Traffic Engineered link, or a TE Link, is a unique application entity that is configured
through grouping the component links. The groupings can be based on different attributes
such as SRGs, link metrics, or latency parameters

TE Links tab display

The entities are displayed in the TE Links tabs if the NPAs are in Implemented state.

Figure 5-21 TE Links tab

For information on the operations of the icons, see Chapter 5, “1350 OMS ASON WebUI
”.
Click the plus icon on the right side corner of the data table to customize the columns. See
“ Save and Reset Table Preferences” (p. 5-40).
To export to .csv file, see “Export a Data Table to a .CSV File” (p. 5-43).
The TE-Links tab displays the following columns:
• Name
• Link Metric
....................................................................................................................................................................................................................................
5-36 Nokia 1350 OMS
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS ASON WebUI TE Links tab of ASON NPA

Figure 5-22 TE Links tab: additional attributes

Click the hyperlink in the Name field in the data table to navigate to NPAs TE links page.

Figure 5-23 TE Links tab: right-click operations

Save and Reset Table Preferences

When to use
Use these tasks to save data table preferences and to reset the data tables to its default
display.

Related information
See

Before you begin

This task does not have any preconditions.

Task: Save Table Preferences

Complete the following steps to save the table preferences.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow one of these navigation paths

Operate > ASON > NPAs
Operate > ASON > SNCs
...................................................................................................................................................................................................

2 From the data table, click the Save Table Preferences icon that is located in the upper
right corner of the page.

Figure 5-24 Save Table Preferences window

...................................................................................................................................................................................................

3 Use any column filters to customize each column.

...................................................................................................................................................................................................

4 Click OK.
Result: The system displays a success message that the table configuration is
successfully saved.
E...................................................................................................................................................................................................
N D O F S T E P S

Task: Reset Table Preferences

1 From the OTNWebUI, follow one of these navigation paths

2 From the data table, click the Reset Table Preferences to Default icon that is located in
the upper right corner of the page.
Result: The system displays a confirmation message.
...................................................................................................................................................................................................

3 Click OK.
Result: The system displays a success message. The system also resets the data table
preferences to the defaults and instantly refreshes the table with the defaults
E...................................................................................................................................................................................................
N D O F S T E P S

Export a Data Table to a .CSV File

When to use
Use this task to export a data table to a .CSV File.

Related information
This task does not have any related information.

Before you begin

This task does not have any preconditions.

Task
Complete the following task to export a data table to a .CSV file.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path:

Operate > ASON > NPAs
Operate > ASON > SNCs
Result: The system displays the data table.
...................................................................................................................................................................................................

2 From any data table that has the Export to CSV icon; for example, Alarms tab; mouse
over the icons on the top right and select the Export to CSV icon.
Result: The system displays the pop-up window displayed with a confirmation to be
saved in the local system.

...................................................................................................................................................................................................

3 To save the .csv file, select Save or Save As. Select Cancel to cancel the operation.
• If you select Save, the file is saved to your Downloads directory in your local system.
• If you select Save As, you can (optionally) rename the file and save it to a directory of
your choice in your local system.

4 If you want to view the .CSV file now, do one of the following:
• Select Save and then click Open.
• Select Save As . Then select Open folder, and double-click the .CSV file that is
highlighted.
If you want to view the .CSV file at a later date, do one of the following
• If you have selected Save, navigate to the Downloads folder and double-click the
.CSV file that was downloaded.
• If you have selected Save As, navigate to the folder in which you have saved the .CSV
file and double- click to open.
Result: The .CSV file is opened.
E...................................................................................................................................................................................................
N D O F S T E P S

Overview
Purpose
This chapter provides the end-to-end working of ASON in 1350 OMS Web UI.

Contents

Design - Service/Infrastructure Template 6-4

Network Configuration window 6-5
Connection Template Types 6-6
Deploy – New OTN Physical Connection 6-7
Deploy a Template to Make a Connection 6-8
Create an OTN Physical Connection 6-11
View 96 OCH Channel Support in Different Windows of OTN WebUI 6-12
Operate Phase - ASON 6-21
View the list of NPAs 6-23
Create an NPA 6-27
Add and Remove Links in ASON 6-29
Implement/Deimplement an NPA 6-36
Access and View the Misalignment Report for a Link 6-39
Activate/Deactivate Auto Restoration of the Control Plane for an NPA 6-40
Assign an ASON I-NNI Link to a TE Link and/or an SRG 6-43
Set the Administrative State of Links 6-47
Change ASON WTR 6-50
Perform Link Maintenance 6-53
Correlate an ASAP with an NPA 6-58

Enable/Disable Fast Photonic Restoration of the Control Plane for an NPA 6-62
Manage 3Rs 6-63
Enable or Disable Auto Restoration of Links 6-70
Manage Jobs in ASON 6-72
Modify TE-Links 6-76
Remove an NPA 6-79
View the ASON SNCs 6-80
View an SNC on the Network Map 6-85
View a Misalignment Report for an SNC 6-89
View the Inherited Priorities of an SNC 6-92
Correlate an ASAP with SNC 6-94
Enable/Disable TCM for an SNC 6-99
Enable/Disable the Test Mode for an SNC 6-102
Explore an SNC on the Routing Display 6-104
Manage SNCP in ASON SNC 6-106
Manage SNC Restoration Constraints 6-107
Modify the Attributes of an SNC 6-111
Switch SNC Routes 6-114
Operate - Network Profiles - Shared Risk Group 6-117
View the Shared Risk Groups 6-118
Create an SRG 6-120
Correlate an SRG with a Physical Connection 6-123
Change or Assign the TE Link to an SRG 6-127
Control the Deployment of the Physical Connections Associated with a Shared 6-129
Risk Group
Manage the ASON Links Assigned to a Shared Risk Group 6-131
Manage the TE Links Assigned to a Shared Risk Group 6-132
Remove a Shared Risk Group 6-133
Operate - Network Profiles – Color Profiles 6-134
View a List of Color Profiles 6-135
Create a Color Profile 6-140
Associate a Color Link over an Existing ASON Domain 6-143
Manage ASON Links Assigned to a Color Profile 6-145

Manage ASON SNCs Assigned to a Color Profile 6-146

Manage TE Links Assigned to a Color Profile 6-148
Delete an Existing Color Profile 6-149
Operate – Network Profiles – Alarm Profiles 6-150
View Alarm Profiles 6-151
Create an Alarm Profile 6-154
Determine the Network Alarm Profile Assigned to a Connection 6-156
Modify an Alarm Profile 6-157
Remove an Alarm Profile 6-159
Operate - Wavelength Usage Report 6-160
Wavelength Usage Report 6-161
Generate Wavelength Usage Report 6-162

Design - Service/Infrastructure Template

Overview
Purpose
This section provides an overview of the Best Practices Templates and the Connection
Template Location and Types.

Contents

Network Configuration window 6-5

Connection Template Types 6-6

Network Configuration window

The Network Configuration window is initially displayed. The Network Configuration
window contains a Tree of connection templates on the left and a data table on the right.
Upon the initial opening of the Network Configuration window, the data table displays
the templates that were most recently accessed and modified. When users subsequently
click on any folder in the Tree, the connection templates that reside in that folder are
displayed in the data table

Figure 6-1 Network Configuration window

Connection Template Types

Best Practices templates
In the 1350 OMS OTN application, a predefined, factory supplied set of Best Practices
templates is provided to users for the provisioning of the logical connections that a given
1350 OMS OTN release supports. These logical connections include infrastructure
connection templates for trails and logical links and service templates. Each Best
Practices template is technology and connection type specific, and each template provides
a proven combination of the parameters that are needed to create a working service. Best
Practices templates are system owned templates; therefore, they cannot be unpublished or
modified; but, they can be saved to another name.

My Templates
the 1350 OMS OTN application also provides users with the ability to create, save, and
share their own templates in the My Templates folder from the Design > navigation path.
With this customization ability, users do not have to sacrifice the ease-of-use and speed
that templates afford.
The templates that reside in the My Templates folder are user owned templates; therefore,
if they are not published, they can be modified

Deploy – New OTN Physical Connection

Overview
Purpose
This section provides an overview of deploy phase and the creation of physical
connection.

Contents

Deploy a Template to Make a Connection 6-8

Create an OTN Physical Connection 6-11
View 96 OCH Channel Support in Different Windows of OTN WebUI 6-12

Deploy a Template to Make a Connection

When to use
Use this task to deploy a template to make an infrastructure connection or service
connection.

Related information
This task does not have any related information.

Before you begin

Before you deploy any template to create a connection, provision a 1350 OMS OTN
Network to determine if you are ready to deploy a template.
This is a generic task; therefore, the template to be deployed can be any template that
resides in the available folders, which can include the Best Practices, My Templates, or
Published folders.

Task
Complete the following steps to deploy a template to make an infrastructure connection
or service connection.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path

Deploy > New Service/Infrastructure Connection.

Figure 6-2 Deploy > New Service/Infrastructure Connection window

...................................................................................................................................................................................................

2 Click the plus signs to expand the tree and drill down to locate the particular template in
the folder
...................................................................................................................................................................................................

3 In the tree, click on the particular template that you want modify
...................................................................................................................................................................................................

4 In the data table, right click on the particular template that you want deploy and select
Deploy.

Figure 6-3 Create Connection window

...................................................................................................................................................................................................

5 Configure the required parameters.

...................................................................................................................................................................................................

6 Click Deploy or Save as Template.

Create an OTN Physical Connection

When to use
Use this task to create an OTN physical connection

Related information
This task does not have any related information.

Before you begin

You can also access the Physical Connection Creation window from the following areas
on OTNWebUI
• By navigating to Operate > Physical Connection > Add.
• From the Physical Connections tab of the Shared Risk Group data table.
• From the Link Maintenance window.

Task
Complete the following steps to create an OTN physical connections.
...................................................................................................................................................................................................

1 From the OTN WebUI, follow this navigation path:

2 To access more information on the creation of OTN physical connections, see “Create an
OTN Physical Connection” (p. 4-16).
E...................................................................................................................................................................................................
N D O F S T E P S

View 96 OCH Channel Support in Different Windows of OTN

WebUI
When to use
Use this task to view 96 OCH channels that are supported in OMS per OTS line in
different windows or pages of 1350 OMS OTN WebUI.

Related information
A4PSWG and ASWG packs supports 96 optical OCH channels in CDC-F configuration,
as compared to the 88 optical channels.
For each degree of OTS optical line, OMS links displays the 96 channels support.
See “96 optical OCH channel support” (p. 1-21).

Before you begin

This task does not have any preconditions.

Task: View the 96 Channels in the Deploy Window

Complete the following steps to view 96 OCH channels in the Routing Constraints tab of
Deploy window.
...................................................................................................................................................................................................

1 From the OTN WebUI, follow this navigation path:

Deploy > New Service / Infrastructure Connection
Result: The system displays a data table that lists the OTN physical connections.
...................................................................................................................................................................................................

2 Select a connection and click the Deploy icon.

...................................................................................................................................................................................................

3 Click the Routing Constraints tab.

...................................................................................................................................................................................................

4 On the right panel of the window, navigate to Advanced Settings > Connection
Controls.
...................................................................................................................................................................................................

5 In the Routing field, select Manual from the drop-down list.

...................................................................................................................................................................................................

6 In the Current Node field on the left panel of the window, enter an appropriate node.
....................................................................................................................................................................................................................................
6-12 Nokia 1350 OMS
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS WebUI – Working in ASON View 96 OCH Channel Support in Different Windows of OTN
Deploy – New OTN Physical Connection WebUI
....................................................................................................................................................................................................................................
Result: The system displays the Link Connections panel with a filter for 96 channels.
The # column in the Link Connection field displays all the 96 channels that are
supported for that OTS link.

Figure 6-4 96 channels: Routing Constraints tab

1 From the OTN WebUI, follow this navigation path:

2 Right-click a physical connection, select Optical Power, and select any one of the
following options:
• Ingress Power at A End
• Ingress Power at Z End
• Egress Power at A End
• Egress Power at Z End
Result: Based on your selection, the system displays the Ingress Power or the Egress
Power window.
...................................................................................................................................................................................................

3 Click the Details tab.

Figure 6-6 Ingress Power window - 96 channels

Task: View the 96 Channels in the Links Connection Tab

Complete the following steps to view the 96 channels in the Link Connection tab of
Physical Connections window.
...................................................................................................................................................................................................

1 From the OTN WebUI, follow this navigation path:

2 Select a physical connection and click a Links tab in the lower panel.

3 In the Links tab, select the hyperlink in the In Use Connection column.
Result: The system navigates to a new window for that particular connection.
...................................................................................................................................................................................................

4 Click the Links Connection tab and check the number of entries in the # column.
In the lower right column, the number of entries per window is set to 25 by default.
Change the number of entries to 100.

Figure 6-7 96 channels: Link Connections tab

View the 96 Channel Through Wave Key Assignments

1 From the OTN WebUI, follow this navigation path:

Operate > Wave Key Assignements
Result: The system displays a Wave Key Assignments window.
...................................................................................................................................................................................................

2 Click OK.
Result: The system displays the OTS links that are assigned to this particular channel
with the selected frequency.

Figure 6-8 96 channels: Wave Key Assignments

1 From the OTN WebUI, follow this navigation path:

Operate > ASON > SNCs.
Result: The system displays a the list of ASON SNCs.
...................................................................................................................................................................................................

2 In the Route tab, select a Current Route or a Nominal Route.

Result: The system navigates to a new window.
...................................................................................................................................................................................................

3 In the lower panel, click Client ASON SNCs tab.

Result: The system displays the number of OCH channels as 96.

Figure 6-9 View 96 channels in Client ASON SNCs tab

Operate Phase - ASON

Overview
Purpose
This section provides the functionalities of ASON NPAs and ASON SNCs.

Contents

View the list of NPAs 6-23

Create an NPA 6-27
Add and Remove Links in ASON 6-29
Implement/Deimplement an NPA 6-36
Access and View the Misalignment Report for a Link 6-39
Activate/Deactivate Auto Restoration of the Control Plane for an NPA 6-40
Assign an ASON I-NNI Link to a TE Link and/or an SRG 6-43
Set the Administrative State of Links 6-47
Change ASON WTR 6-50
Perform Link Maintenance 6-53
Correlate an ASAP with an NPA 6-58
Enable/Disable Fast Photonic Restoration of the Control Plane for an NPA 6-62
Manage 3Rs 6-63
Enable or Disable Auto Restoration of Links 6-70
Manage Jobs in ASON 6-72
Modify TE-Links 6-76
Remove an NPA 6-79
View the ASON SNCs 6-80
View an SNC on the Network Map 6-85
View a Misalignment Report for an SNC 6-89
View the Inherited Priorities of an SNC 6-92
Correlate an ASAP with SNC 6-94
Enable/Disable TCM for an SNC 6-99
Enable/Disable the Test Mode for an SNC 6-102

Explore an SNC on the Routing Display 6-104

Manage SNCP in ASON SNC 6-106
Manage SNC Restoration Constraints 6-107
Modify the Attributes of an SNC 6-111
Switch SNC Routes 6-114

View the list of NPAs

When to use
Use this task to view the list of NPAs.

Related information
NPA, which is Network Protection Architecture, is a set of NEs, protections blocks, and
physical links that work together to create a dedicated protection.

Before you begin

This task does not have any preconditions.

Task
Complete the following steps to view the list of NPAs.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path

Operate > ASON > NPAs
Result: The system displays the list of NPAs in the data table.

Figure 6-10 List of ASON NPAs

...................................................................................................................................................................................................

2 Select an NPA and click the Attributes icon.

Figure 6-11 Additional attributes of ASON NPAs

...................................................................................................................................................................................................

3 Select an NPA and click any of the icons that is available in the right corder of the data
table.
For information on the operations of the icons, see “NPA and SNC: Icons” (p. 5-3).
...................................................................................................................................................................................................

4 Select the Sorting icon to sort the data in the column in ascending or descending order.

Figure 6-12 Data table sorting

...................................................................................................................................................................................................

5 Select an NPA and right-click.

Result: The system displays a list of operations that can be performed on the selected
NPA.

Figure 6-13 NPA right-click operations

...................................................................................................................................................................................................

6 To implement or deimplement an NPA, see “Implement/Deimplement an NPA” (p. 6-36).

...................................................................................................................................................................................................

7 To add links to ASON or remove links from ASON, see “Add and Remove Links in
ASON” (p. 6-29).

8 To correlate ASAP, see “Correlate an ASAP with an NPA” (p. 6-58).

...................................................................................................................................................................................................

9 To manage jobs, see “Manage Jobs in ASON” (p. 6-72).

Create an NPA
When to use
Use this task to create an Network Protection Architecture (NPA).

Related information
This task does not have any related information.

Before you begin

Ensure that the equipment in the network is properly set, according to the deployed
network.

Task
Complete the following steps to create an NPA for ASON.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path:

Operate > ASON > NPAs.
Result: The system displays the list of NPAs in a data table.
...................................................................................................................................................................................................

2 Click the Create icon from the data table.

...................................................................................................................................................................................................

3 In the Name field, enter a name to identify the NPA.

...................................................................................................................................................................................................

4 Optional: In the Comment 1 field, enter any relevant comment.

...................................................................................................................................................................................................

5 Optional: In the Comment 2 field, enter any additional relevant comments.

...................................................................................................................................................................................................

6 Click the Deploy button

Result: The system creates the NPA and displays a success message.
The configuration state is set to Defined.
E...................................................................................................................................................................................................
N D O F S T E P S

Add and Remove Links in ASON

When to use
Use this task to add and remove links in ASON.

Related information
This task provides the main navigation method in which you can add links to or remove
links from ASON and from different starting locations on the OTNWebUI.
“NPA and SNC: Icons” (p. 5-3).

Before you begin

The NPA must already be created
The NPA must be listed in the NPA data table in the Implemented or Partially
Implemented configuration state.

Task: Add Links to ASON

Complete the following steps to add links to ASON and/or remove links from ASON.
...................................................................................................................................................................................................

1 From the OTN WebUI, follow the navigation path

Operate > ASON > NPAs
Operate > ASON > NPAs > Links tab
Result: The system displays the lists of NPAs in a data table.
...................................................................................................................................................................................................

2 Click on the NPA or link to which you want to add links and do one of the following:
• Right-click the NPA and select Add Links to ASON.
• Select the Add Links to ASON icon.

Figure 6-14 Add Links to ASON option

Result: The system displays the Add Links to ASON window.

Figure 6-15 Add Links to ASON window

3 In the ASON Domain panel, the User Label field is populated by default.
...................................................................................................................................................................................................

4 In the Link Parameters field, configure the parameters for I-NNI links
• In the Latency (microsec) and Cost/Metric fields, enter the value by clicking the up
and the down arrow buttons.
• In the ASON WTR field, select the value from the drop-down list.
• In the Color Profile, click the Select icon. The system displays the Color Profile
Available Object window.

• In the SRGs panel, mouse over and click the Select items from list icon.
...................................................................................................................................................................................................

5 In the I-NNI links panel, click the Search icon. The system displays the ASON Available
Objects (INNI) window. Select the I-NNI link and click the Select button.

Figure 6-16 ASON Available Objects (INNI) window

Result: The I-NNI links are added

Figure 6-17 I-NNI Links panel

6 To add the UNI links, click the Search icon in the Drop/UNI panel.
The system displays the ASON Available Objects (Drop/UNI) window. Select the link and
click the Search button.

Figure 6-18 ASON Available Objects (Drop/UNI)

...................................................................................................................................................................................................

7 Click the Deploy button.

Result: The system adds the parameter specifications to the NPA and outputs a
Success message at the bottom of the window
E...................................................................................................................................................................................................
N D O F S T E P S

Task:Remove Links from ASON

Complete the following steps to remove links from ASON.
...................................................................................................................................................................................................

1 From the OTN WebUI, follow one of these navigation paths:

Operate > ASON > NPAs
Operate > ASON > NPAs > Links tab
...................................................................................................................................................................................................

2 Click the NPA or link from which you want to remove its links to ASON and click the
Links tab.
Result: The system activates the Links tab and the Links data table is displayed.
...................................................................................................................................................................................................

3 In the Links data table, locate the link to be removed and one of the following
• Right click on the link, and follow this path: Remove Links from ASON
• Click the link, mouse over the icons on the top right, and click on the Remove Links
from ASON icon
....................................................................................................................................................................................................................................
6-34 Nokia 1350 OMS
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS WebUI – Working in ASON Add and Remove Links in ASON
Operate Phase - ASON
....................................................................................................................................................................................................................................

Figure 6-19 Remove Links from ASON option

Result: The system displays a confirmation message.

...................................................................................................................................................................................................

4 Click OK.
Result: The system removes the selected link from ASON.
E...................................................................................................................................................................................................
N D O F S T E P S

Implement/Deimplement an NPA
When to use
Use this task to implemented or deimplement a selected NPA.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”.

Before you begin

Ensure that the NPAs are created.
The NPA must be listed in the NPA data table in the Defined or Partially Implemented
Configuration State. If an NPA is listed as Partially Implemented, some process failed
while attempting to implement the NPA.

Task: Implement an NPA

Complete the following procedure to implement an NPA.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path:

Operate > ASON > NPAs
Result: The list of NPAs are listed in the data table.
...................................................................................................................................................................................................

2 To implement an NPA, do one of the following steps

• Right-click the NPA that you want to implement and follow the path: Implement
• Click the NPA that you want to implement, mouse over the icons on the top right, and
click the Implement icon.
Result: The system displays a confirmation message whether you want to implement
the particular NPA.
...................................................................................................................................................................................................

3 Click OK
Result: The Configuration State changes to Implemented on the NPA data table and
the system displays a message at the bottom left of the window:
Implement <NPA Name> ✓ Success

Deimplement an NPA
Complete the following steps to deimplement an NPA
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path:

Operate > ASON > NPAs
Result: The system displays the list of NPAs in the data table.
Ensure all the links from NPA are removed prior to deimplementing an NPA.
...................................................................................................................................................................................................

2 To deimplement an NPA, do one of the following steps

• Right-click on the NPA that you want to implement and follow the path:
Deimplement .
• Click the NPA that you want to implement, mouse over the icons on the top right, and
click the Deimplement icon.

Result: The system displays a confirmation message. .

...................................................................................................................................................................................................

3 Click OK
Result: The Configuration State changes to Deimplemented on the NPA data table
and the system displays the following message at the bottom left of the window:
Deimplement <NPA name> ✓ Success.
E...................................................................................................................................................................................................
N D O F S T E P S

Access and View the Misalignment Report for a Link

When to use
Use this task to access and view the Misalignment Report for a link for an ASON or a TE
link.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”.

Before you begin

Ensure that the links are created.

Task
Complete the following steps to access and view the Misalignment Report for an ASON
or a TE link.
...................................................................................................................................................................................................

1 From the OTN WebUI, follow one of the navigation paths

Operate > ASON > NPA.
Result: The system displays the list of NPAs in the data table.
...................................................................................................................................................................................................

2 Click the Links tab and select a link.

...................................................................................................................................................................................................

3 Right-click the selected link and select Misalignment Report.

OR
Click on the link, mouse over the icons on the top right, select the Misalignment Report.
(to be discussed)
Result: The system displays the Misalignment Report for the selected link.
E...................................................................................................................................................................................................
N D O F S T E P S

Activate/Deactivate Auto Restoration of the Control Plane for

an NPA
When to use
Use this task to activate or deactivate auto restoration of the Control Plane for ASON
NPA.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”.

Before you begin

Ensure that the NPAs are created.

Task
Complete the following steps to activate the Auto Restoration of the Control Plane.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path

2 Click the Control Planes tab.

Result: The system displays the list of Control Planes.
...................................................................................................................................................................................................

3 Select a control plane you want to activate, right-click, and select Activate.

Figure 6-20 Auto Restoration option

Result: The system displays the Automatic Restoration window.

Figure 6-21 Control Planes tab: Automatic Restoration window

4 In the Automatic Restoration window, configure the following parameters:

• the User Label is auto-populated by default
• In the Priority field, select a number from 1 to 5 from the drop-down list. The default
is 1.
.
...................................................................................................................................................................................................

5 Click Deploy.
Result: The system displays a success message.
Deactivate Auto restoration : To deactivate, select the Control Plane, right-click and
select Deactivate. The system displays a confirmation message. Click OK. The
system displays a success message.
E...................................................................................................................................................................................................
N D O F S T E P S

Assign an ASON I-NNI Link to a TE Link and/or an SRG

When to use
Use this task to assign an ASON I-NNI link that is associated with a selected ASON NPA
to a TE link and/or an SRG.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”.

Before you begin

Ensure that the NPAs that are created is in Implemented state.

Task
Complete the following steps to assign an ASON I-NNI link that is associated with a
selected ASON NPA to a TE link and/or an SRG.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow one of these navigation paths:

Operate > ASON > NPAs
Result: The system displays the list of NPAs in the data table.
...................................................................................................................................................................................................

2 Select Links tab.

Result: The system displays the list of links available.
...................................................................................................................................................................................................

3 Select an I-NNI link, right-click and select TE-Link Assignment option.

Figure 6-22 TE-Link Assignment window

4 If you have selected New in the Final TELink, field, the system displays the following
fields:
• In the TE-Link parameters pane, configure the following parameters:
– Costs/Metric: Use the Up and the Down button to select a value.
– Latency (microsec): Use the Up and the Down button to select a value.
– Color Profile: Click the Search icon to select the Color Profile from the Color
Profile Available Objects window.
• In the SRGs panel, click the Search icon. The system displays the SRGs window. Select
an SRG and the same is populated in the SRG panel.
...................................................................................................................................................................................................

5 If you have selected Existing in the Final TE-Link field, click the Search icon to add the
Final Telink Name in the TE-Link parameters pane. You can add the Assigned TE links
from the Assignable TE-Link list window.
...................................................................................................................................................................................................

6 Click Deploy
Result: The ASON link is updated.
E...................................................................................................................................................................................................
N D O F S T E P S

Set the Administrative State of Links

When to use
Use this task to set the Administrative State of links.

Related information
See “View the list of NPAs” (p. 6-23).

Before you begin

Ensure that the NPAs are created.
You can also change the administrative state of the links that are assigned to an NPA or
color profile from the Link Maintenance Window.
The Color Profile data table has tabs for Used In and Matched By. These tabs have a
subtab for ASON Links. The ASON Links subtab and Links tab, which is displayed for
ASON NPAs, provide the same actions and functions for links

Task
Complete the following steps to set the Administrative State of the links.
...................................................................................................................................................................................................

1 From the OTN WebUI, follow one of these navigation paths

2 Click the Links tab in the lower panel

Result: The system displays the list of links.
...................................................................................................................................................................................................

3 Select a link and do one of the following options:

• Right-click and select Administrative State
• Select the Administrative State icon on the right side of the lower panel
...................................................................................................................................................................................................

4 Set one of the following options as per your need for the configuration
• set to Unlock
• set to Shutting Down
• set to Soft Shutting Down

Figure 6-23 Set the Administrative State: Right-click options

Figure 6-24 Set the Administrative State: Administrative State icon

...................................................................................................................................................................................................

5 If the Administrative State selected is one of the following; set to Unlock, set to
Shutting Down, set to Soft Shutting Down, or Synchronize; the system performs the
requested operation and outputs a Success message at the bottom left of the window.

6 If the Administrative State selected is Set to Locked, the system displays a warning
message:

...................................................................................................................................................................................................

7 Click OK.
Result: The system performs the Lock operation and outputs a success message at the
bottom left of the window
E...................................................................................................................................................................................................
N D O F S T E P S

Change ASON WTR

When to use
Use this task to change Wait Time to Restore (WTR) of a physical connection and/or a
logical link.

Related information
The Wait Time to Restore (WTR) defines the time to wait before the traffic is moved back
to the Main path, starting from the Main path restoration. When a failure occurs in ASON,
the failed path is switched to an alternative path, called a Spare, to guarantee the traffic.
Once the Main path is restored, the traffic is switched from the Spare back to the Main.
See

Before you begin

Ensure that the physical connections and the logical links belongs to ASON.

Task
Complete the following steps to change the WTR of a physical connection or a link
...................................................................................................................................................................................................

1 From the OTN WebUI, follow the navigation path:

2 Click the Links tab.

Result: The system displays the links for that NPA.
...................................................................................................................................................................................................

3 Select a link, right-click, and select Change ASON WTR.

Figure 6-25 Change ASON WTR window

...................................................................................................................................................................................................

4
• The Name field is auto populated by default.
• In the ASON WTR (*) field, select the value from the drop-down list.
...................................................................................................................................................................................................

5 Click Deploy.
Result: The system is updated with the new value.
E...................................................................................................................................................................................................
N D O F S T E P S

Perform Link Maintenance

When to use
Use this task to access and perform the link maintenance.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”.

Before you begin

Ensure that the NPAs are available and are in Implemented state.

Task
Complete the following steps to access the Link Maintenance Window:
...................................................................................................................................................................................................

1 From the OTN WebUI, follow the navigation path:

Operate > ASON > NPA.
Result: The system displays the NPAs in the data table.
...................................................................................................................................................................................................

2 Click the Links tab.

...................................................................................................................................................................................................

3 Select the link, right-click, and select Link Maintenance Window.

Figure 6-26 Link Maintenance window

...................................................................................................................................................................................................

4 To view the additional attributes of the selected link, click the attribute icon.

Figure 6-27 Link Maintenance window - Attribute icon

...................................................................................................................................................................................................

5 Perform the following operations from the Link Maintenance Window:

• Set the Administrative State. “Set the Administrative State of Links” (p. 6-47).
• Access Link Management Window
• Change ASON WTR. See “Change ASON WTR” (p. 6-50).
• Add and Remove Links from ASON. See “Add and Remove Links in ASON”
(p. 6-29).
• Enable or Disable Auto Restoration of Links. See “Enable or Disable Auto
Restoration of Links” (p. 6-70).

6 To view the tabbed topics for a particular link in the same browser window, select a link
in any column except for the Name column, scroll down to the bottom of the window, and
click on one of the following tabs: SRGs, Client ASON SNCs, Server SRGs, or Server
Physical Connections.
Result: The system displays a detailed information for the selected item.
For example, the following figure depicts the Client ASON SNCs.

Figure 6-28 Client ASON SNCs tab

...................................................................................................................................................................................................

7 Click the hyperlink in the Name field.

Result: The system navigates to the link-related information page in a new browser
window.
...................................................................................................................................................................................................

8 Click the hyperlink in the TE Link Name field.

Result: The system navigates to TE Links page in a new browser window.
You can also perform the following operations:
• Create and delete a Shared Risk Group from the Link Maintenance Window.
• Create a Server Shared Risk Group from the Link Maintenance Window
• Create and remove a Physical Connection from the Link Maintenance Window.
• Implement/Deimplement a Physical Connection from the Link Maintenance Window
• Configure the Service State of a Physical Connection from the Link Maintenance
Window.

Correlate an ASAP with an NPA

When to use
Use this task to correlate an Alarm Severity Assignment Profile (ASAP) with an NPA.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”.

Before you begin

Ensure that the NPAs are created.

Task
Complete the following steps to correlate an ASAP with an NPA.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path:

Operate > ASON > NPAs.
Result: The system displays the list of NPAs in the data table.
...................................................................................................................................................................................................

2 Select an NPA that you want to correlate, right-click, and select Correlate ASAP.

Figure 6-30 Correlate ASAP option

Result: The system displays the Correlate ASAP window.

Figure 6-31 Correlate ASAP window

...................................................................................................................................................................................................

3 To add the NPA, click the Search icon.

Figure 6-32 Npas window

Choose an NPA and click the Select button. The NPA is added to the Correlate ASAP
window.
...................................................................................................................................................................................................

4 In the ASAP Profile panel, click the Search icon and select the alarm profiles from the
Alarm Profile window.

...................................................................................................................................................................................................

5 Click Deploy

Enable/Disable Fast Photonic Restoration of the Control Plane

for an NPA
When to use
Use this task to enable or disable Fast Photonic Restoration of the Control Plane for an
NPA.

Related information
see

Before you begin

Fast photonic restoration is only available for 1830 PSS PHN nodes. It is not available for
1830 PSS OCS nodes.

Task
Complete the following steps to enable or disable the fast photonic restoration of the
Control Plane for an NPA
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path

2 To enable the fast photonic restoration of the Control Plane, select Fast Photonic
Restoration > Enable.
Result: The system displays a success or a failure message.
...................................................................................................................................................................................................

3 To disable the fast photonic restoration of the Control Plane, select Fast Photonic
Restoration > Disable.
Result: The system displays a success or a failure message.
E...................................................................................................................................................................................................
N D O F S T E P S

Manage 3Rs
When to use
Use this task to manage 3Rs for an existing NPA.

Related information
A 3R is a user-selected optical regeneration group that consists of a node and two NNI
transponder line ports that reshape, retime, and retransmit a signal. Managing 3Rs for an
NPA includes the creation of the 3R, the addition of the 3R to an existing NPA, the
implementation or deimplementation of an existing 3R, and the removal of a 3R from an
existing NPA.

Before you begin

Ensure that the NPA is created.
When you add a 3R to an NPA or remove a 3R, the NPA must be listed in the NPA data
table in the Implemented or Partially Implemented configuration state.
Note: The system supports the allocation by means of automatic routing or via
manual routing. With automatic routing, the 3R has to be used only if there are no
alternative paths without 3R.

Task: Create a 3R
Complete the following steps to create a 3R.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path:

2 Click the 3R tab and select the Create icon.

Figure 6-33 3R Creation window

...................................................................................................................................................................................................

3 In the 3R Node panel, configure the following parameters:

• In the Npa field, the value is auto populated by default.
• In the Node field, select the Search icon. The system displays the Node List window.
Select a node and click the Select button. The node is added to the 3R window.

Figure 6-34 3R Creation window: Add node

...................................................................................................................................................................................................

4 In the 3R Transponder panel. configure the following fields

• In the NNI Line port filed, click the search icon to open the NNI port details window.
Select a port and add to the 3R Transponder panel.
• In the Second NNI Line port filed, click the search icon to open the port details
window. Select a port and add to the 3R Transponder panel.

Figure 6-35 3R Creation window: Add NNI Line ports

...................................................................................................................................................................................................

5 Click Deploy.
Result: The system adds the selected node and transponder ports to create a 3R.
E...................................................................................................................................................................................................
N D O F S T E P S

Task: Add a 3R to an Existing NPA

Complete the following steps to add a 3R to an existing NPA
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path:

Operate > ASON > NPAs.

2 Select an NPA that you want to add a 3R and click on the 3R tab.
...................................................................................................................................................................................................

3 In the 3R tab, do one of the following:

• Right-click on the particular 3R that you want to add to the NPA and follow the path:
Configuration > Add to NPA.
• Click the particular 3R to be add to the NPA, mouse over, and select Add to NPA from
the Configuration icon drop-down.

Figure 6-36 3R functions

Result: The 3R is added to the selected NPA.

Task: Remove Links from ASON

1 From the OTNWebUI, follow this navigation path:

Operate > ASON > NPAs.

2 Select an NPA from which you want to remove the link and click on the 3R tab.
...................................................................................................................................................................................................

3 In the 3R tab, do one of the following:

• Right-click on the particular 3R from which you want to remove the link and follow
the path: Configuration > Remove Links from ASON.
• Click the particular 3R 3R from which you want to remove the link, mouse over, and
select Remove Links from ASON from the Configuration icon drop-down.
Result: The links are removed from ASON.
See Figure 6-36, “3R functions” (p. 6-67)
E...................................................................................................................................................................................................
N D O F S T E P S

Task: Implement/Deimplement an Existing 3R

Complete the following steps to implement or deimplement an existing 3R.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path:

2 Click the 3R tab.

Result: The 3R tab is activated and the 3R data table is displayed.
...................................................................................................................................................................................................

3 To implement a 3R, do one of the following

• Right-click the 3R that you want to implement and follow the path: Configuration >
Implement.
• Select a 3R to be implemented, mouse over, and select Implement option from the
Configuration icon drop-down list.
Result: The Configuration State changes to Implemented in the 3Rs data table.
See Figure 6-36, “3R functions” (p. 6-67).

4 To deimplement a 3R, do one of the following:

• Right-click on the particular 3R that you want to deimplement and follow the path:
Configuration > Deimplement.
• Select a 3R to be deimplemented, mouse over, and select Deimplement option from
the Configuration option drop-down list.
Result: The Configuration State changes to Deimplemented in the 3R data table.
E...................................................................................................................................................................................................
N D O F S T E P S

Remove a 3R from an Existing NPA

Complete the following steps to remove a 3R from an existing NPA.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path:

Operate > ASON > NPAs
Result: The system displays a list of NPAs in a data table.
...................................................................................................................................................................................................

2 Click a particular NPA that you want to remove a 3R and click on the 3R tab.
Result: The system displays the 3R tab with details.
...................................................................................................................................................................................................

3 In the data table of the 3R tab, do one of the following:

• Right-click the particular 3R that you want to remove from the NPA and follow the
path: Remove.
• Click the particular 3R that you want remove from the NPA, mouse over the icons and
select Remove.
See Figure 6-36, “3R functions” (p. 6-67)

Enable or Disable Auto Restoration of Links

When to use
Use tis task to enable or disable the auto restoration of the links.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”.

Before you begin

Ensure that the NEs are reachable and the NPAs are in Implemented state.

Task
Complete the following steps to enable or disable the automatic restoration of links
...................................................................................................................................................................................................

1 From the OTNWebUI, follow the navigation path:

Operate > ASON > NPA
Result: The system displays the list of NPAs in the data table.
...................................................................................................................................................................................................

2 Select the Links tab.

...................................................................................................................................................................................................

3 Select a link, right-click, and select Auto Restoration > Enable or Auto Restoration >
Disable. The selection depends on the current restoration state of the link.

Figure 6-37 Auto Restoration > Enable/Disable

Result: Depending on the configuration state of the link and the selection, the system
displays a success message.
E...................................................................................................................................................................................................
N D O F S T E P S

Manage Jobs in ASON

When to use
Use this task to manage jobs for an NPA.

Related information
This task does not have any related information.

Before you begin

This task does not have any prerequisites.

Task
Complete the following steps to view the jobs for an NPA
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path

2 Select an NPA, right-click and select Jobs.

OR
Select an NPA and select the Job icon.
Result: The system displays the job history in a new browser window.

Figure 6-38 NPA Job window

3 To reschedule job, click the Reschedule Job icon.

...................................................................................................................................................................................................

4 To view the details, click the Run History icon.

Result: The system displays the Results Details window.

...................................................................................................................................................................................................

5 To delete a job, select a job and click the Delete icon.

...................................................................................................................................................................................................

6 To view the details, click the Details tab in the lower panel.

7 To view the job inventory, click the Job Inventory tab in the lower panel.
E...................................................................................................................................................................................................
N D O F S T E P S

Modify TE-Links
When to use
Use this task to modify a traffic engineering (TE) link that is assigned to an NPA, color
profile, or SRG.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”.

Before you begin

Ensure that the NPAs are in Implemented state.

Task
Complete the following steps to modify a traffic engineering (TE) link that is assigned to
an NPA, color profile, or SRG.
...................................................................................................................................................................................................

1 From the OTN WebUI, follow the navigation path:

2 Select the TE Links tab.

Result: The system displays the TE Links in the lower panel.
...................................................................................................................................................................................................

3 Select a TE Link, right-click, and select Modify TE Link.

Figure 6-39 Modify TE-Link window

...................................................................................................................................................................................................

4 In the TE Link panel, configure the following parameters:

• The Name field is auto populated.
• In the Cost/Metric field, use the up and down arrow to select the value.
• In the Latency (microsec) field, use the up and down arrow to specify a valid time
for latency.
• In the Color Profile field, click the Search icon. The Color Profile Available Objects
window is displayed, where you select the color profile. Click the Select button. The
Color Profile is added.

5 In the SRGs field, click the Search icon. The SRGs window is displayed. Select the SRG
and click the Select button.
...................................................................................................................................................................................................

6 Click Deploy
Result: The system modifies the TE link.
E...................................................................................................................................................................................................
N D O F S T E P S

Remove an NPA
When to use
Use this task to remove an NPA.

Related information
This task does not have any related information.

Before you begin

Ensure that the NPAs are in Defined state.
If the NPA to be removed (deleted) is currently in the Implemented state, it must first be
moved to Deimplemented.

Task
Complete the following steps to remove an NPA that has been created and is listed on the
NPA data table.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path

2 Do one of the following:

• Right-click the NPA to be deleted select: Remove
• Mouse over the icons and click the Remove icon.
Result: The system displays a confirmation message.
...................................................................................................................................................................................................

3 Click OK.
Result: The system removes the selected NPA from the NPA data table.
E...................................................................................................................................................................................................
N D O F S T E P S

View the ASON SNCs

When to use
Use this task to view the list of SNC in the data table.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”.

Before you begin

This task does not have any preconditions.

Task
Complete the following steps to view the details of the ASON SNCs.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path:

Operate > ASON > SNCs.
Result: The system displays the list of SNCs in a data table.

Figure 6-40 List of ASON SNCs

...................................................................................................................................................................................................

2 Select an SNC and click the Attributes icon.

Figure 6-41 Additional attributes of ASON SNCs

...................................................................................................................................................................................................

3 Select an SNC and click any of the icons that is available in the right corder of the data
table.
For information on the operations of the icons, see “NPA and SNC: Icons” (p. 5-3).
...................................................................................................................................................................................................

4 To sort the data in the column in ascending or descending order, select the Sorting icon on
the right side of the field.

Figure 6-42 ASON SNC sorting

...................................................................................................................................................................................................

5 Select an SNC and right-click.

Figure 6-43 SNC right-click operations

...................................................................................................................................................................................................

6 Refer the following procedures for the right-click actions:

• To enable or disable TCM, see “Enable/Disable TCM for an SNC” (p. 6-99).
• To view the misalignment report for a given SNC, see “View a Misalignment Report
for an SNC” (p. 6-89)
• To enable or disable test mode, see “Enable/Disable the Test Mode for an SNC”
(p. 6-102).
• To modify the SNC attributes, see “ Modify the Attributes of an SNC” (p. 6-111).
• To manage SNCP attributes, see “Manage SNCP in ASON SNC” (p. 6-106).
• To explore the Routing Display, see “Explore an SNC on the Routing Display”
(p. 6-104).
• To manage SNC constraints, see “Manage SNC Restoration Constraints” (p. 6-107).
• To correlate ASAP in ASON SNC, see “Correlate an ASAP with SNC” (p. 6-94).
....................................................................................................................................................................................................................................
Nokia 1350 OMS 6-83
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS WebUI – Working in ASON View the ASON SNCs
Operate Phase - ASON
....................................................................................................................................................................................................................................
• To view the inherited priorities, see “View the Inherited Priorities of an SNC”
(p. 6-92).
• To view the network map, see “View an SNC on the Network Map” (p. 6-85).
• To switch SNC routes, see “Switch SNC Routes” (p. 6-114).

View an SNC on the Network Map

When to use
Use this task to view an SNC on the Network Map.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”.

Before you begin

Ensure that the SNCs are created and displayed in the data table.

Task
Complete the following steps to view an SNC on the Network Map.
...................................................................................................................................................................................................

1 From the OTN WebUI, follow one of these navigation paths:

Operate > ASON > SNCs
Operate > ASON > NPAs > ASON SNCs (tab)
Note: You can also access the SNCs tab from the Color Profiles page.
Result: The system displays the ASON SNCs in a data table.
...................................................................................................................................................................................................

2 Select an SNC for which you want to switch the route, right-click, and select: Display
Route on Map.....

Figure 6-44 Display Route on Map option

Figure 6-45 ASON SNC - Network Map

...................................................................................................................................................................................................

3 [Optional] To view the current route of the SNC on the Network Map, click the Current
button, which is located at the bottom right of the window.
...................................................................................................................................................................................................

4 [Optional] To return to the nominal route of the SNC on the Network Map, click the
Nominal button, which is also located at the bottom right of the window

Figure 6-46 ASON SNC - Current Route

View a Misalignment Report for an SNC

When to use
Use this task to view the misalignment report for an SNC.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”

Before you begin

Ensure that the SNCs are available in the data table.

Task
Complete the following task to view the misalignment report for an SNC.
...................................................................................................................................................................................................

1 From the OTN WebUI, follow one of these navigation path

Operate > ASON > SNCs.
Operate > ASON > NPAs > ASON SNCs (tab).
The ASON SNCs tab is also available in the Color Profile window.
...................................................................................................................................................................................................

2 Right-click the selected SNC and select Misalignment Report.

Figure 6-47 Misalignment Report option in ASON SNC

Figure 6-48 Misalignment Report window - SNC

To save and reset data table, see “ Save and Reset Table Preferences” (p. 5-40).
To export to .csv file, see “Export a Data Table to a .CSV File” (p. 5-43).
...................................................................................................................................................................................................

3 To view the additional attributes, click the Attribute icon.

View the Inherited Priorities of an SNC

When to use
Use this task to view the inherited properties of an SNC.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”.

Before you begin

Ensure that the SNCs are available in the data table.

Task
Complete the following steps to view the inherited properties of an SNC.
...................................................................................................................................................................................................

1 From the OTN WebUI, follow one of these navigation paths:

Operate > ASON > SNCs
Operate > ASON > NPAs > ASON SNCs (tab)
You can access the ASON SNCs tab from the Color Profiles window.
...................................................................................................................................................................................................

2 Right-click the selected SNC and select Inherited Properties.

Correlate an ASAP with SNC

When to use
Use this task to correlate an SNC with an ASAP.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”.

Before you begin

Ensure that the SNCs are listed in the data table.

Task
Complete the following steps to correlate an SNC with an Alarm Severity Assignment
Profile (ASAP).
...................................................................................................................................................................................................

1 From the OTN WebUI, follow one of these navigation paths:

Operate > ASON > SNCs
Operate > ASON > NPAs > ASON SNCs (tab)
You can also view the ASON SNCs tab in the Color Profiles window.
...................................................................................................................................................................................................

2 Right-click a selected SNC and select Correlate ASAP.

Figure 6-49 Correlate ASON option in ASON

Figure 6-50 Correlate ASAP window in SNC

...................................................................................................................................................................................................

3 To select and populate the entity in the Objects panel, click the Search icon.

Figure 6-51 Trails window

...................................................................................................................................................................................................

4 To select the alarm profiles and populate in the ASAProfile panel, click the Search icon.

Figure 6-52 Alarm Profiles window

...................................................................................................................................................................................................

5 Click Deploy.
Result: The selected ASAP and SNC are now correlated.
E...................................................................................................................................................................................................
N D O F S T E P S

Enable/Disable TCM for an SNC

When to use
Use this task to enable or disable a Tandem Connection Monitoring (TCM) level for an
SNC.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”.

Before you begin

Ensure that the SNCs are available in the data table.

Task: Enable TCM

Complete the following steps to enable a TCM level for an SNC
...................................................................................................................................................................................................

1 From the OTN WebUI, follow one of these navigation paths:

Operate > ASON > SNCs
Operate > ASON > NPAs > ASON SNCs (tab)
You can also view the ASON SNC tab from the Color Profiles window.
...................................................................................................................................................................................................

2 Right-click the selected SNC and select Enable TCM.

Figure 6-53 TCM Level window

...................................................................................................................................................................................................

3 In the Level field of the TCM Level window, slide the scale to the appropriate numbered
level.
...................................................................................................................................................................................................

4 Click Deploy.
Result: The system applies the TCM level to the selected SNC.
E...................................................................................................................................................................................................
N D O F S T E P S

Task: Disable TCM

Complete the following steps to disable a TCM level for an SNC
...................................................................................................................................................................................................

1 From the OTN WebUI, follow one of these navigation paths:

Operate > ASON > SNCs
Operate > ASON > NPAs > ASON SNCs (tab)
....................................................................................................................................................................................................................................
6-100 Nokia 1350 OMS
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS WebUI – Working in ASON Enable/Disable TCM for an SNC
Operate Phase - ASON
....................................................................................................................................................................................................................................
You can also view the ASON SNC tab from the Color Profiles window.
...................................................................................................................................................................................................

2 Right-click the selected SNC and select Disable TCM.

Result: The system disables the TCM for the selected SNC.
E...................................................................................................................................................................................................
N D O F S T E P S

Enable/Disable the Test Mode for an SNC

When to use
Use this task to enable or disable the Test Mode for an SNC.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”.
The enabling or disabling of the test mode for an SNC deals with modifying the Working
State of the attributes of the SNC. Only an SNC that has the Working State of Normal
can have the test mode enabled. Only an SNC that has the Working State of Failed to
Modify SNC Attributes can have the test mode disabled.
Depending on the success or the failure of the test mode, the system changes the Working
State from Normal to Modifying SNC Attributes or Failed to Modify SNC Attributes; or,
conversely, the system changes the Working State from Failed to Modify SNC Attributes
to Normal.

Before you begin

Ensure that the SNCs are available in the data table.

Task: Enable Test Mode

Complete the following steps to enable the Test Mode for an SNC.
...................................................................................................................................................................................................

1 From the OTN WebUI, follow one of these navigation paths:

2 Right-click the selected SNC and select Enable Test Mode.

Figure 6-54 SNC Test Modes

Task: Disable Test Mode

Complete the following steps to disable the Test Mode for an SNC.
...................................................................................................................................................................................................

1 From the OTN WebUI, follow one of these navigation paths:

2 Right-click the selected SNC and select Disable Test Mode.

Result: The system changes the Working State from Failed to Modify SNC
Attributes to Normal.

Explore an SNC on the Routing Display

When to use
Use this task to explore an SNC on the Routing Display.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”.

Before you begin

Ensure that the SNCs are available in the data table.

Task
Complete the following steps to explore an SNC on the Routing Display.
...................................................................................................................................................................................................

1 From the OTN WebUI, follow one of these navigation paths:

2 Right-click a selected SNC and select Explore.

Result: The system accesses the MS-GUI, and the Routing Display for the selected
SNC is displayed.
Note: If the PKT component is not installed in the server, then the system does not
display the Routing Display of the SNC in the 1350 OMS MS-GUI. This means that
OTNE needs to be present for the Routing Display to open in MS-GUI.
If the user wants to view the routing display of ODU ASON link, go to Operate >
Infrastructure Connections. Select and right-click an object from the list and select
Routing Display.

Figure 6-55 Routing Display of ODU ASON 14_DR4_1350OMS_OTNESMGuide_i1link

Manage SNCP in ASON SNC

When to use
Use this task to Manage SNCP in ASON SNC.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”.

Before you begin

Ensure that the ASON SNCs are available in the data table.
To identify the SNCP command status for each SNC that is listed in the SNC data table,
click the plus sign that is located in the upper right corner of the data table and check the
SNCP command status column.

Task
Complete the following steps to manage SNCP in ASON SNC.
...................................................................................................................................................................................................

1 From the OTN WebUI, follow one of these navigation paths:

Operate > ASON > SNCs.
Operate > ASON > NPAs > ASON SNCs (tab).
You can also view the ASON SNC tab from the Color Profiles window.
Result: The system displays the list of SNCs in the data table.
...................................................................................................................................................................................................

2 Right-click the SNC to which you want to manage SNCP and, depending on the current
state of the SNC, follow one of these paths:
• SNCP Management > Synchronize Switch Position
• SNCP Management> Force main
• SNCP Management> Force spare
• SNCP Management> Manual main
• SNCP Management> Manual spare
• SNCP Management> Release
Result: The system displays a success or failure message at the bottom of the window
and changes the SNCP command status in the SNC data table to reflect your request.
E...................................................................................................................................................................................................
N D O F S T E P S

Manage SNC Restoration Constraints

When to use
Use this task to manage SNC restoration constraints.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”.

Before you begin

Ensure that the SNCs are available in the data table.

Task
Complete the following steps to manage SNC restoration constraints.
...................................................................................................................................................................................................

1 From the OTN WebUI, follow one of these navigation paths:

2 Right-click the selected SNC and select SNC Restoration Constraints option.

Figure 6-56 SNC Restoration Constraints window

...................................................................................................................................................................................................

3 In the ASON SNC panel, the User Label field is automatically populated.
...................................................................................................................................................................................................

4 In the Must avoid TE-LINKS panel, click the search icon to select the TE Links from the
TE Links window.

Figure 6-57 TE Links window

...................................................................................................................................................................................................

5 In the Must avoid ASON SNC's panel, click the Search icon to select the subnetwork
connections from the Subnetwork Connections window.

Figure 6-58 Subnetwork Connections window

...................................................................................................................................................................................................

6 Click Deploy.
Result: The selected TE Links and/or ASON SNCs that are to be avoided are added to
the restoration constraints.
E...................................................................................................................................................................................................
N D O F S T E P S

Modify the Attributes of an SNC

When to use
Use this task to modify the attributes of SNC.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”.

Before you begin

Ensure that the SNCs are listed in the data table.

Task
Complete the following steps to modify the attributes of the SNC.
...................................................................................................................................................................................................

1 From the OTN WebUI, follow one of these navigation paths:

Operate > ASON > SNCs
Operate > ASON > NPAs > ASON SNCs (tab)
You can also view the ASON SNC tab from the Color Profiles window.
Result: The system displays the list of SNCs in a data table.
...................................................................................................................................................................................................

2 Right-click a selected NE and select Modify Attributes.

Figure 6-59 Modify Trail Parameters window

...................................................................................................................................................................................................

3 In the ASON SNC panel, the values in the User Label field is auto populated.

4 In the Routing & Restoration parameters field, configure the following parameters:
• In the Restoration Mode field, select one of the following options:
– No Restoration: the traffic is lost if a failure occurs.
– Source-Based Restoration: the Control Plane protects the traffic if a failure
occurs by calculating a new route.
– Guaranteed Restoration: protection and restoration are used together to optimize
recovery time and to maximize service quality. The Control Plane calculates a
restored route as an alternative to the nominal route (main).
• In the Priority field, slide the scale to the appropriate numbered priority with 1 being
High and 5 being Low.
• In the Setup Priority field, slide the scale to the appropriate numbered priority with 1
being High and 5 being Low.
• In the ASON Revertive field, select Manual or Automatic.
• In the Max Latency (microsec.) field, select the number of microseconds from 0 to
2147483647 from the drop-down list.
• In the Wait For Server Restoration field, select No or Yes.
...................................................................................................................................................................................................

5 Click Deploy.
Result: The system makes the parameter changes for the selected SNC.
E...................................................................................................................................................................................................
N D O F S T E P S

Switch SNC Routes

When to use
Use this task to switch routes for an SNC.

Related information
See Chapter 5, “1350 OMS ASON WebUI ”.

Before you begin

Ensure that the SNCs are listed in the data table.

Taskl
Complete the following steps to switch the route to Nominal
...................................................................................................................................................................................................

1 From the OTN WebUI, follow one of these navigation paths:

Operate > ASON > SNCs
Operate > ASON > NPAs > ASON SNCs (tab)
You can also view the ASON SNC tab from the Color Profiles window.
Result: The system displays the list of SNCs in the data table.
...................................................................................................................................................................................................

2 To switch the route to Nominal, right click the SNC for which you want to switch the
route and select Switch to Nominal.

Figure 6-60 Switch Routes - SNC

...................................................................................................................................................................................................

3 To convert the route, right click the SNC for which you want to convert the route and
select Convert current to Nominal.
...................................................................................................................................................................................................

4 To switch the route to backup, right-click the SNC you want to switch the route of backup
and select Switch to Backup.
...................................................................................................................................................................................................

5 When you switch to any of the three states, the system displays the message stating that
the operation could be traffic impacting.

6 Click OK
Result: The system displays a success or failure message.
E...................................................................................................................................................................................................
N D O F S T E P S

Operate - Network Profiles - Shared Risk Group

Overview
Purpose
This section provides an overview of the functionalities of Shared Risk Groups with
regard to ASON.

Contents

View the Shared Risk Groups 6-118

Create an SRG 6-120
Correlate an SRG with a Physical Connection 6-123
Change or Assign the TE Link to an SRG 6-127
Control the Deployment of the Physical Connections Associated with a Shared 6-129
Risk Group
Manage the ASON Links Assigned to a Shared Risk Group 6-131
Manage the TE Links Assigned to a Shared Risk Group 6-132
Remove a Shared Risk Group 6-133

View the Shared Risk Groups

When to use
Use this task to view a list of Shared Risk Groups (SRGs).

Related information
This task does not have any related information.

Before you begin

Ensure that the SRGs are created.

Task
Complete the following step to view a list of SRGs.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path:

Operate > Network Profiles > Shared Risk Groups.
Result: The system displays a list of SRGs.

2 To view the additional attributes, click the Attribute icon.

...................................................................................................................................................................................................

3 To create an SRG, click the Create icon. See “Create an SRG” (p. 6-120).
...................................................................................................................................................................................................

4 To delete an SRG, click the Remove icon or select an SRG, right-click and select
Remove option.
E...................................................................................................................................................................................................
N D O F S T E P S

Create an SRG
When to use
Use this task to create an Shared Risk Group (SRG).

Related information
This task does not have any related information.

Before you begin

You can also create SRGs from the Link Maintenance window.

Task
Complete the following step to create an SRG.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path:

Operate > Network Profiles > Shared Risk Groups.
Result: The system displays the list of Shared Risk Groups in a data table.
...................................................................................................................................................................................................

2 Select the Create icon.

Figure 6-61 SRG Creation window

...................................................................................................................................................................................................

3 In the Label field, enter a name to identify the SRG that you are creating.
...................................................................................................................................................................................................

4 In the Risk Type field, select one of the following from the drop-down list:
• Other
• Node
• Right of Way
• Physical Connection
....................................................................................................................................................................................................................................
Nokia 1350 OMS 6-121
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS WebUI – Working in ASON Create an SRG
Operate - Network Profiles - Shared Risk Group
....................................................................................................................................................................................................................................
• Conduit (the default)
• Cable
...................................................................................................................................................................................................

5 In the Probability field, select undefined [0]], very low [10], low [100], medium [1000],
high [10000] (the default), or very high [100000] from the drop down list.
...................................................................................................................................................................................................

6 Optional: Click the Additional Information panel. In the Comment field, enter any notes
to further identify or clarify the SRG that you are creating.
...................................................................................................................................................................................................

7 Optional: Click the Additional Information panel. In the A-Site and Z-Site fields, enter
the appropriate user labels for both sites.
...................................................................................................................................................................................................

8 Click Deploy
Result: The system creates the SRG and is added to the Shared Risk Groups data
table.
E...................................................................................................................................................................................................
N D O F S T E P S

Correlate an SRG with a Physical Connection

When to use
Use this task to correlate a Shared Risk Group (SRG) with a physical connection.
When you correlate an SRG with a particular physical connection, assign that physical
connection to the SRG.

Related information
See “Create an OTN Physical Connection” (p. 4-16).

Before you begin

The SRG must already be created.
The physical connection must belong to a Defined NPA. If the NPA is in the
Implemented state, the operation is available on a TE-Link and is applied to all the
physical connections inside the TE link.
The physical connection or TE-Link that you correlate to one SRG can be correlated to
another SRG; meaning, one physical link or one TE-Link can be correlated to multiple
SRGs.
You an also correlate an SRG with a physical connection from the Physical Connections
data table.

Task
Complete the following steps to correlate a SRG.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path:

Operate > Network Profiles > Shared Risk Groups.
Result: The system displays a list of SRGs in the data table.
...................................................................................................................................................................................................

2 Select the SRG you want to correlate.

...................................................................................................................................................................................................

3 Click the Physical Connections tab and select the Correlate SRG icon.

Figure 6-62 Correlate SRG window

...................................................................................................................................................................................................

4 In the Physical Link panel, click the Search icon and select the Physical link from the
Physical Links window.

Figure 6-63 Physical Links window

...................................................................................................................................................................................................

5 In the SRGs panel, click the Search icon and select the SRG from the SRGs window.

Figure 6-64 SRG window

...................................................................................................................................................................................................

6 Click Deploy.
Result: The system displays a success message.
E...................................................................................................................................................................................................
N D O F S T E P S

Remove the Correlation of a Physical Connection to a Shared Risk Group

From the Shared Risk Groups list that is displayed, select the SRG from which you want
to remove its physical connection correlation. In the Physical Connections tab of the
window, do one of the following:
• Click the Remove icon.
• Mouse over the icons, click on the SRG Correlate icon. In the SRG Correlation
window, click the Delete icon and click Deploy.

Change or Assign the TE Link to an SRG

When to use
Use this task to assign or change the assignment of a Shared Risk Group to a traffic
engineering (TE) link.

Related information
This task does not have any related information.

Before you begin

Ensure that the equipment in the network has been properly set, according to the deployed
network.
Ensure that the NPAs are created and implemented.
The SRG must be created and the physical connection must be created. The SRG and the
physical connection must be correlated. The SRG then propagates to all of the physical
connections that are bundles in TE link.
For GMRE L0, one TE Link has been automatically created for each OMS trail. In turn,
each OMS trail has been automatically created for each OTS physical connection.
For GMRE L1, the relationship of the TE link - OTU trail is 1:n based on the bundling
rules.

Task
Complete the following steps to assign or change the assignment of a Shared Risk Group
to a traffic engineering (TE) link.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path

Operate > Network Profiles > Shared Risk Groups
Result: The system displays the SRGs in the data table.
...................................................................................................................................................................................................

2 Click the TE Link tab.

Result: The system displays the list of TE links.
...................................................................................................................................................................................................

3 Select a link, right-click and select Modify TE-Link.

4 In the TE Link panel, configure the following parameters:

• The Name field is auto populated.
• In the Cost/Metric field, select a value.
• In the Latency (microsec), select a value from the scroll buttons
• To select a color profile, click the Search icon and select the color profile from the
Color Profile Available Objects window.
...................................................................................................................................................................................................

5 In the SRGs panel, click the Search icon and select SRG from the SRGs window.
...................................................................................................................................................................................................

6 Click Deploy.
Result: The TE link is updated with your selections and applied to all links (physical
connections) that belong to TE link.
E...................................................................................................................................................................................................
N D O F S T E P S

Control the Deployment of the Physical Connections

Associated with a Shared Risk Group
When to use
Use this task to control the deployment of the physical connections that are associated
with an SRG.

Related information
This task does not have any related information.

Before you begin

This task enables you to change the service state and the implementation state of the
physical connection that is associated with an SRG.
The SRG must already be created and the physical connections must be correlated with
the SRG.

Task
Complete the following steps to control the deployment of the physical connections that
are associated with an SRG
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path:

Operate > Network Profiles > Shared Risk Groups
Result: The system display the SRGs in the data table.
...................................................................................................................................................................................................

2 To implement a physical connection that is Defined (not yet implemented)

In the Physical Connections tab of the window, select the connection to be implemented,
and do one of the following:
• Right-click the physical connection and follow this path: Deployment Control >
Implement.
• Click the physical connection, mouse over the icons, select Deployment Control,
click on the down arrow, and select Implement.
Result: The implementation state of the physical connection is first changed to
Partially Implemented and then to Implemented.
...................................................................................................................................................................................................

3 To deimplement a physical connection that is already implemented

4 To deimplement the deployment, click OK.

Result: The implementation state of the physical connection is first changed to
Partially Implemented and then to Defined.
...................................................................................................................................................................................................

5 To set the service state of an not-in-service physical connection to in service

In the Physical Connections tab of the window, select the connection to be put into
service, and do one of the following:
• Right-click the physical connection and follow this path: Deployment Control > Set
Service State (in service).
• Click the physical connection, mouse over the icons, select Deployment Control,
click on the down arrow, and select Set Service State (in service)
Result: The system displays a success message.
...................................................................................................................................................................................................

6 To set the service state of an in-service physical connection to not-in-service

In the Physical Connections tab of the window, select the connection to be put
out-of-service, and do one of the following
• Right-click the physical connection and follow this path: Deployment Control > Set
Service State (not in service).
• Click the physical connection, mouse over the icons, select Deployment Control,
click on the down arrow, and select Set Service State (not in service)
Result: The system displays a success message.
E...................................................................................................................................................................................................
N D O F S T E P S

Manage the ASON Links Assigned to a Shared Risk Group

When to use
Use this task to manage the ASON links (Links) that are assigned to an SRG.

Related information
This task does not have any related information.

Before you begin

The ASON Links tab provides the same actions and functions as the Links tab that is
displayed for ASON NPAs. This task redirects you to the same task that is documented
for Operate > ASON > NPAs.

Task
...................................................................................................................................................................................................

1 To set the administrative state, see “Set the Administrative State of Links” (p. 6-47)
...................................................................................................................................................................................................

2 To change the add or remove links, see “Add and Remove Links in ASON” (p. 6-29).
...................................................................................................................................................................................................

3 For Link Maintenance Window. see “Perform Link Maintenance” (p. 6-53).
...................................................................................................................................................................................................

4 For Change ASON WTR (wait time to restore), see “Change ASON WTR” (p. 6-50).
...................................................................................................................................................................................................

5 For automatic restoration, see “Enable or Disable Auto Restoration of Links” (p. 6-70).
...................................................................................................................................................................................................

6 For Misalignment Report, see “Access and View the Misalignment Report for a Link”
(p. 6-39).
E...................................................................................................................................................................................................
N D O F S T E P S

Manage the TE Links Assigned to a Shared Risk Group

When to use
Use this task to manage the TE links that are assigned to a color profile.

Related information
This task does not have any related information.

Before you begin

The TE Links tab provides the same actions and functions as the TE Links tab that is
displayed for ASON NPAs. This task redirects you to the same task that is documented
for Operate > ASON > NPAs.

Task
Complete the following steps to manage the TE links that are assigned to a SRG.
...................................................................................................................................................................................................

1 To Modify TE links, see “Modify TE-Links” (p. 6-76).

...................................................................................................................................................................................................

2 For Misalignment Report, see “Access and View the Misalignment Report for a Link”
(p. 6-39).
E...................................................................................................................................................................................................
N D O F S T E P S

Remove a Shared Risk Group

When to use
Use this task to delete an SRG.

Related information
See “Create an SRG” (p. 6-120).

Before you begin

The SRG must already be created and it cannot be correlated to any physical connection.
Complete the following step to delete an SRG.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path

2 Find the SRG that you want to remove and do one of the following
• Right-click the SRG and follow the path: Remove.
• Click the SRG, and select the Remove icon.
Result: The system displays a confirmation window.
E...................................................................................................................................................................................................
N D O F S T E P S

Operate - Network Profiles – Color Profiles

Overview
Purpose
This section provides an overview of the functionalities of color profiles with regard to
ASON.

Contents

View a List of Color Profiles 6-135

Create a Color Profile 6-140
Associate a Color Link over an Existing ASON Domain 6-143
Manage ASON Links Assigned to a Color Profile 6-145
Manage ASON SNCs Assigned to a Color Profile 6-146
Manage TE Links Assigned to a Color Profile 6-148
Delete an Existing Color Profile 6-149

View a List of Color Profiles

When to use
Use this task to view the list of color profiles in the data table.

Related information
This task does not have any related information.

Before you begin

This task does not have any preconditions

Task
Complete the following steps to view the list of color profiles in the data table.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow one of these navigation paths:

Operate > Network Profiles
Result: The system displays the list of color profiles in the data table.
...................................................................................................................................................................................................

2 Click the Color Profiles tab.

Figure 6-65 List of Color Profiles

...................................................................................................................................................................................................

3 To view the additional attributes, click the Attribute icon.

Figure 6-66 Color Profile additional attributes

...................................................................................................................................................................................................

4 In the lower panel, click the ASON Links tab.

The Color Profile data table has tabs for Used In and Matched By. These tabs have a
subtab for ASON Links. The ASON Links sub tab, TE Links and ASON SNC sub tab.
These tabs provide the same actions and functions as it is for ASON NPAs and ASON
SNCs.

Figure 6-67 Right-click actions on ASON links tab of Color Profiles

To set the administrative state, see “Set the Administrative State of Links” (p. 6-47).
To view the Link Maintenance window, see “Perform Link Maintenance” (p. 6-53).
To change ASON WTR, see “Change ASON WTR” (p. 6-50).
To enable or disable auto restoration of ASON links, see “Enable or Disable Auto
Restoration of Links” (p. 6-70).
To add or remove links from ASON, see “Add and Remove Links in ASON”
(p. 6-29).
To assign TE links, see “Assign an ASON I-NNI Link to a TE Link and/or an SRG”
(p. 6-43).

5 In the lower panel, click the TE Links tab.

Result: The system displays the TE links. Right-click an object and for more
information on the right-click navigations, see the following:

Figure 6-68 Right-click actions on TE links tab of Color Profiles

Create a Color Profile

When to use
Use this task to create a new color profile.

Related information
This task does not have any preconditions.

Before you begin

This task enables the users to add the color components that are needed to create a New
Color Profile. To create a New Color Profile, users must select more than one existing
color profile.

Task
Complete the following steps to create a new color profile.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow one of these navigation paths:

Operate > Network Profiles.
...................................................................................................................................................................................................

2 Click the Color Profiles tab.

Result: The system displays the list of color profiles in the data table.
...................................................................................................................................................................................................

3 Click the Create icon.

Figure 6-69 Color Profile window

...................................................................................................................................................................................................

4 In the Color Components panel, click the Search icon to add the colors to the panel from
the Available Colors window.

Figure 6-70 Available Colors window

Note: Ensure that at least two color profiles are added.

...................................................................................................................................................................................................

5 In the Properties panel, enter the name and comment in the User Label and Comment
fields respectively.
...................................................................................................................................................................................................

6 Click Deploy.
Result: The New Color Profile is created and is added to the Color Profile list.
E...................................................................................................................................................................................................
N D O F S T E P S

Associate a Color Link over an Existing ASON Domain

When to use
Use this task to associate a Color Link over an existing ASON Domain.

Related information
This task does not have any related information.

Before you begin

Add color links and traffic to set up a well identified, valid path for the traffic type to
which the selected color refers.

Task
Complete the following steps to associate a colored link with a physical connection and
NPA over an existing ASON domain.
...................................................................................................................................................................................................

1 If a physical connection has not already been created, create the physical connection. See
“Create an OTN Physical Connection” (p. 4-16).
...................................................................................................................................................................................................

2 If an NPA has not already been created, create an NPA.“Create an NPA” (p. 6-27).
...................................................................................................................................................................................................

3 From the OTNWebUI, follow this path:

Operate > Network Profiles > Color Profiles
...................................................................................................................................................................................................

4 From the lower panel, click Add links to ASON.

Result: The system displays the Add Links to ASON window.
...................................................................................................................................................................................................

5 From the Add Links to ASON window, associate a link to ASON NPA.
...................................................................................................................................................................................................

6 In the ASON Domain panel, click the Add button to select the ASON domain to which the
colored link must be included.
...................................................................................................................................................................................................

7 Click Deploy

Manage ASON Links Assigned to a Color Profile

When to use
Use this task to manage ASON Links assigned to a Color Profile.

Related information
This task does not have any related information.

Before you begin

The Color Profile data table has tabs for Used In and Matched By. These tabs have a
sub-tab for ASON Links. The ASON Links sub-tab and Links tab, which is displayed for
ASON NPAs, provide the same actions and functions for links. This task redirects you to
the appropriate task that is documented for Operate > ASON > NPAs.
...................................................................................................................................................................................................

1 To set the administrative state, see “Set the Administrative State of Links” (p. 6-47).
...................................................................................................................................................................................................

3 For Link Maintenance Window, see “Perform Link Maintenance” (p. 6-53).
...................................................................................................................................................................................................

Manage ASON SNCs Assigned to a Color Profile

When to use
Use this task to manage the ASON SNCs that are assigned to a color profile.

Related information
This task does not have any related information.

Before you begin

The Color Profile data table has tabs for Used In and Matched By. These tabs have a
subtab for ASON SNCs. The ASON SNCs sub-tab and ASON SNCs tab, which is displayed
for ASON NPAs, provide the same actions and functions for SNCs. This task redirects you
to the appropriate task that is documented for Operate > ASON > SNCs.

Task
Complete the following steps to manage the ASON links that are assigned to a color
profile.
...................................................................................................................................................................................................

1 To explore, see “Explore an SNC on the Routing Display” (p. 6-104).

...................................................................................................................................................................................................

2 For Display Route on Map, see “Manage SNCP in ASON SNC” (p. 6-106)
...................................................................................................................................................................................................

3 To enable and disable test mode, see “Enable/Disable the Test Mode for an SNC”
(p. 6-102).
...................................................................................................................................................................................................

4 For Convert current to nominal, Switch to Nominal, and Switch to Backup, see “Switch
SNC Routes” (p. 6-114).
...................................................................................................................................................................................................

5 For Modify Attributes, see “ Modify the Attributes of an SNC” (p. 6-111).
...................................................................................................................................................................................................

6 For SNC Contraints Management, see “Manage SNC Restoration Constraints” (p. 6-107).
...................................................................................................................................................................................................

7 For Enable or Disable TCM, see “Enable/Disable TCM for an SNC” (p. 6-99).
...................................................................................................................................................................................................

8 For Inherited Priorities, see “View the Inherited Priorities of an SNC” (p. 6-92)
....................................................................................................................................................................................................................................
6-146 Nokia 1350 OMS
8DG43185XAAA Release 14.0
Issue 2 October 2016
1350 OMS WebUI – Working in ASON Manage ASON SNCs Assigned to a Color Profile
Operate - Network Profiles – Color Profiles
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

9 For Correlate ASAP see “Correlate an ASAP with SNC” (p. 6-94).
...................................................................................................................................................................................................

10 For Misalignment report, see “View a Misalignment Report for an SNC” (p. 6-89).
E...................................................................................................................................................................................................
N D O F S T E P S

Manage TE Links Assigned to a Color Profile

When to use
Use this task to manage the TE links that are assigned to a color profile.

Related information
This task does not have any related information.

Before you begin

The Color Profile data table has tabs for Used In and Matched By. These tabs have a
sub-tab for TE Links. The TE Links sub-tab and TE Links tab, which is displayed for
ASON NPAs, provide the same actions and functions for links. This task redirects you to
the appropriate task that is documented for Operate > ASON > NPAs.

Task
Complete the following steps to manage the TE links that are assigned to a color profile.
...................................................................................................................................................................................................

1 To Modify TE links, see “Modify TE-Links” (p. 6-76).

...................................................................................................................................................................................................

Delete an Existing Color Profile

When to use
Use this task to delete an existing color profile.

Related information
This task does not have any related information.

Before you begin

The color profile to be deleted must be listed in the Color Profiles list.

Task
Complete the following step to delete an existing color profile.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow one of these navigation paths:

Operate > Network Profiles
Result: The system displays the color profiles in a data table.
...................................................................................................................................................................................................

2 Click the Color Profile tab.

Result: The system displays the Color Profiles in a data table.
...................................................................................................................................................................................................

3 Select the Color Profile and click the Remove icon.

Result: The system displays a success message at the bottom of the window and
removes the selected color profile from the data table.
E...................................................................................................................................................................................................
N D O F S T E P S

Operate – Network Profiles – Alarm Profiles

Overview
Purpose
This section provides an overview of the functionalities of Alarm Profiles with regard to
ASON.

Contents

View Alarm Profiles 6-151

Create an Alarm Profile 6-154
Determine the Network Alarm Profile Assigned to a Connection 6-156
Modify an Alarm Profile 6-157
Remove an Alarm Profile 6-159

View Alarm Profiles

When to use
Use this task to view a list of alarm profiles.

Related information
This task does not have any related information.

Before you begin

If alarm profiles have not been created, the only alarm profile that is displayed on the data
table list is that of the default ASAP.

Task
Complete the following step to view a list of alarm profiles
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path:

2 Click the Alarm Profiles tab.

...................................................................................................................................................................................................

3 Click the attribute icon to view the additional attributes.

...................................................................................................................................................................................................

4 Select the alarm profile and right-click

Result: The system displays the following options:
Remove
Correlate Connection Rate Asap

Create an Alarm Profile

When to use
Use this task to create an alarm profile.

Related information
This task does not have any related information.

Before you begin

If the alarm profiles have not been created, the only alarm profile that is displayed on the
data table list is that of the default ASAP.

Task
Complete the following step this task to create an alarm profile
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path:

2 Click the Alarm Profiles tab.

Result: The system displays the Alarm Profiles data table.
...................................................................................................................................................................................................

3 Click the Create icon.

Figure 6-71 Alarm Profile Identification window

...................................................................................................................................................................................................

4 In the Name field, enter a name to identify the alarm profile that you are creating.
Result: The system displays a success message.
E...................................................................................................................................................................................................
N D O F S T E P S

Determine the Network Alarm Profile Assigned to a

Connection
When to use
Use this task to determine the network alarm profile that is assigned to a connection.

Related information
This task does not have related information.

Before you begin

By default, the default ASAP is assigned to all the OTN connections. By accessing the
data table for a physical connection, an infrastructure connection, or a service; this task
enables you to determine if an ASAP, other than the default ASAP, is assigned to a
selected connection.

Task
Complete the following step this task to determine the network alarm profile that is
assigned to a connection.
...................................................................................................................................................................................................

1 Do one of the following

• Operate > Physical Connections
• Operate > Infrastructure Connections
• Operate > Services
Result: The system displays the data table for the selected object.
...................................................................................................................................................................................................

2 Locate the connection or connections and do one or both of the following

• For physical connections, click the plus sign that is located in the upper right corner of
the data table (which is used to customize the columns that are displayed in the data
table) and check the ASAP Name.
• For infrastructure connections and services, click the plus sign that is located in the
upper right corner of the data table (which is used to customize the columns that are
displayed in the data table) and check NML ASAP.
Result: The system displays the NML ASAP column in the visible portion of the data
table.
E...................................................................................................................................................................................................
N D O F S T E P S

Modify an Alarm Profile

When to use
Use this task to modify an existing alarm profile.

Related information
This task does not have any related information.

Before you begin

If alarm profiles have not been created, the only alarm profile that is displayed on the data
table list is that of the default ASAP.

Task
Complete the following step this task to modify an existing alarm profile
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path:

Operate > Network Profiles
...................................................................................................................................................................................................

2 Click the Alarm Profiles tab.

Result: The system displays the alarm profiles in the data table.
...................................................................................................................................................................................................

3 In the Alarm Profile data table, select the existing alarm profile that you want to modify,
then click on the Properties tab.
Result: The system displays the panels of the Properties tab.
...................................................................................................................................................................................................

4 Depending on the needs of your installation, expand each of the panel, and modify the
parameters

Figure 6-72 Properties tab

...................................................................................................................................................................................................

5 To save the modifications, click the Save icon.

Result: The system displays a success message.
E...................................................................................................................................................................................................
N D O F S T E P S

Remove an Alarm Profile

When to use
Use this task to remove an alarm profile from the data table.

Related information
This task does not have any related information.

Before you begin

If alarm profiles have not been created, the only alarm profile that is displayed on the data
table list is that of the default ASAP. The default ASAP cannot be removed or deleted.
You cannot delete any user-created alarm profile that is correlated to existing connection
or connections.
If you delete an alarm profile that is associated with a connection, the system then
correlates the connection, by default, to the default ASAP. The correlated alarms that
existing on the connection are cleared and re-raised with the severities that are defined in
the default ASAP.

Task
Complete the following step this task to remove an alarm profile from the data table.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path:

2 Click the Alarm Profiles tab.

Result: The system displays the Alarm Profiles in the data table.
...................................................................................................................................................................................................

3 Select the alarm and click the Remove icon.

OR
Select the alarm, right-click, and select Remove.
E...................................................................................................................................................................................................
N D O F S T E P S

Operate - Wavelength Usage Report

Overview
Purpose
This section describes about the user generated report that lists all the Optical
Transmission Sections (OTSs) in the network.

Contents

Wavelength Usage Report 6-161

Generate Wavelength Usage Report 6-162

Wavelength Usage Report

Description
The Wavelength Usage Report feature provides the users with the option to generate a
report of the available wavelengths on a route between the source and the destination,
where a new service needs to be deployed. This feature reports the available wavelengths
prior to service provisioning.
The Wavelength Usage Report is a generated in .CSV format. The report can be opened
immediately or saved to the local system.
To generate Wavelength Usage Report, see “Generate Wavelength Usage Report”
(p. 6-162).

Usages of the Wavelength Usage Report

The following scenarios explain the typical usages of the Wavelength Usage Report:
• When a service must be deployed between two sites
To determine to set fiber transponders prior to service turn up, users must have a view
of the available frequencies on the end-to-end route between the sites.
• When performing maintenance on a link or node or temporary reroute traffic around a
failure:
The users must first determine the available wavelengths or blocks of spectrum on
alternative routes between the source and the destination. Then reroute or re-provision
existing wavelength services through alternative routes and put them on available
wavelengths according to Wavelength Usage Report.

Generate Wavelength Usage Report

When to use
Use this task to generate Wavelength Usage Report.

Related information
This feature supports the scenario where there is no planning tool for allocating
wavelengths in the network.
See “Wavelength Usage Report” (p. 6-161).

Before you begin

Ensure that OTS connections are available in the Physical Connections page. If an OTS
connection is not available, create an OTS connection from the Operate > Physical
Connections page.
This feature support 44 or 88 OTS channels.

Task
Complete the following steps to generate a Wavelength Usage Report for an OTS
connection.
...................................................................................................................................................................................................

1 From the OTNWebUI, follow this navigation path

Operate > Wavelength Usage Report.
Result: The system displays a Wavelength Usage Report window.

Figure 6-73 Wavelength Usage Report

By default, the Network Wide radio button remains selected, that is, the report is
generated for all the OTS connections available in the complete network.

2 Click Generate Report.

Result: The system generates the report in .csv format.

Figure 6-74 Exported format of Wavelength Usage Report

The system also prompts the user to open the file or save the file to your local system:

Figure 6-75

Table 6-1 Wavelength Report : Parameters

Parameter Description
OTS Name Name of the OTS connection
From Node From Node end port of OTS
To Node To Node end point of OTS
ASON NPA For Control Plane links, ASON NPA field is
auto-populated with the name, L0_GMRE
that specifies the ASON NPA that the OTS
or OMS belongs to. If the link is a managed
plane link, the values are not populated in
the field.
Number of Channels Specifies the number of channels based on
the link connections of the OTS channels.
9170, 9175 (Frequencies) Displays the frequencies that are supported.
First to eight channels are not applicable.

The available and used wavelengths are depicted as follows:

• x: wavelength used by managed plane infrastructure optical channel
• n: wavelength used by nominal route of ASON connection
• u: uncorrelated cross connection present
• n/a: Frequencies not applicable
• Empty cell : Frequency is available

Overview
Purpose
Part III of the document provides the appendices of 1350 OMS ASON.

Contents

Appendix A, ASON Alarm and Correlation A-1

Appendix B, List of Abbreviations B-1

Overview
Purpose
This section provides the rules that the Automatic Switched Optical Network (ASON)
Manager uses to correlate the elementary alarms that are sourced by L0/L1 control plane
and that are raised in order to transport the object correlated alarms.

Contents

ASON SNC A-2

ASON NPA A-4
GMRE A-5
ASON SNC Alarms Correlation A-7

ASON SNC

Table A-1 ASON SNC

OTN WEB GUI Object Correlated Alarm Probable Operational L1/L0

Cause Status
ASON SNC SNC Rerouted Enabled
ASON SNC Nominal Unavailable – TP blocked Enabled
ASON SNC Nominal Unavailable – Communication Enabled
Problem
ASON SNC Nominal Unavailable – Transmission Enabled
Problem
ASON SNC Nominal Unavailable - Indeterminate Enabled
Problem
ASON SNC Nominal Unavailable – Configuration Enabled
Problem
ASON SNC Nominal Unavailable – Reversion preempt Enabled
ASON SNC Active Failed – Transmission Problem Disabled
ASON SNC Active Failed – Unprotected Disabled
ASON SNC Active Failed – APE failed Disabled L0 only
ASON SNC Active Failed – Cross Connection Problem Disabled
ASON SNC Active Failed – Preemption Disabled
ASON SNC Active Failed – End Point Failure Disabled L0 only
ASON SNC Reroute Not possible Disabled
ASON SNC Ready To Revert Enabled
ASON SNC SNC in Automatic Restoration Disabled Enabled
ASON SNC Test Mode enabled Enabled
ASON SNC SNC Backup Unavailable Enabled
ASON SNC APE In Progress Enabled L0 only
ASON SNC TCA Channel Margin Enabled L0 only
ASON SNC Optical Feasibility Violation Enabled L0 only
ASON SNC SRG Violation Enabled
ASON SNC Link Diversity Violation Enabled
ASON SNC Channel Assignment Violation Enabled L0 only

OTN WEB GUI Object Correlated Alarm Probable Operational L1/L0

Cause Status
ASON SNC Latency Violation Enabled
ASON SNC Color Violation Enabled
ASON SNC SNC SNCP Degraded (L1 only; PRC not in Enabled
LO CP)
ASON SNC Nominal Link Violation Enabled
ASON SNC Tandem Connection Failure (L1 only; TCM Disabled
not yet managed in L0)
ASON SNC Tandem Connection Locked (L1 only; Enabled
TCM not yet managed in L0)
ASON SNC Tandem Connection Degraded (L1 only; Enabled
TCM not yet managed in L0)
ASON SNC Transport Failure Disabled
ASON SNC Transport Locked Enabled
ASON SNC Degraded Signal Enabled
ASON SNC SNC Failure (L0 CP only since TCM not Disabled
yet managed)
ASON SNC Transport Incoming Failure (L0 CP only Enabled
since TCM not yet managed)
ASON SNC Transport Outgoing Failure (L0 CP only Enabled
since TCM not yet managed)
ASON SNC Transport Locked Ingress (L0 CP only Enabled
since TCM not yet managed)
ASON SNC Transport Locked Egress (L0 CP only since Enabled
TCM not yet managed)

ASON NPA

Table A-2 ASON NPA Correlated Probable Cause

OTN WEB GUI Object Correlated Alarm Probable Cause

ASON NPA GMRE Degraded
ASON NPA GMRE In Migration
ASON NPA CP Communication Interface Problem
ASON NPA GMRE Automatic Restoration Disabled
ASON NPA GMRE halted
ASON NPA Fast Photonic Restoration Mode Mismatch

GMRE

Table A-3 GMRE Probable Cause

Elementary Alarm Probable Cause Elementary L1/L0 Comment

Object
SNC Rerouted SNC
Nominal Unavailable – TP blocked SNC LO CP only
Nominal Unavailable – Communication SNC
Problem
Nominal Unavailable – Transmission SNC
Problem
Nominal Unavailable - Indeterminate SNC
Problem
Nominal Unavailable – Configuration SNC L0 CP only New alarm
Problem
Nominal Unavailable – Reversion preempt SNC
Active Failed – Transmission Problem SNC
Active Failed – Unprotected SNC
Active Failed – APE failed SNC
Active Failed – Cross Connection Problem SNC
Active Failed – Preemption SNC
Active Failed – End Point Failure SNC
Reroute Not possible SNC
Ready To Revert SNC
SNC in Automatic Restoration Disabled SNC
Test Mode enabled SNC
SNC Backup Unavailable SNC
APE In Progress SNC
TCA Channel Margin SNC
Optical Feasibility Violation SNC
SRG Violation SNC
Link Diversity Violation SNC
Channel Assignment Violation SNC

Elementary Alarm Probable Cause Elementary L1/L0 Comment

Object
Latency Violation SNC
Nomainal Link Violation SNC
Color Violation SNC
SNC SNCP Degraded SNC

NE not reachable by Control Plane Control Plane

GMRE degraded Control Plane
GMRE in migration Control Plane
RSVP Down Control Plane
RSVP Degraded Control Plane
DPR Down Control Plane
DPR Degraded Control Plane

GMRE Automatic Restoration disabled Control Plane

RSVP Network Version Mismatch Control Plane
DPR Network Version Mismatch Control Plane
GMRE halted Control Plane
Fast Photonic Restoration Mode Mismatch Control Plane

ASON SNC Alarms Correlation

Table A-4 ASON SNC Correlated Alarms

Elementary alarm on SNC (by GMRE) Correlated alarm on ASON SNC

SNC Rerouted SNC Rerouted
Nominal Unavailable – TP blocked Nominal Unavailable – TP blocked
Nominal Unavailable – Communication Nominal Unavailable – Communication
Problem Problem
Nominal Unavailable – Transmission Problem Nominal Unavailable – Transmission Problem
Nominal Unavailable - Indeterminate Problem Nominal Unavailable - Indeterminate Problem
Nominal Unavailable – Configuration Problem Nominal Unavailable – Configuration Problem
Nominal Unavailable – Reversion preempt Nominal Unavailable – Reversion preempt
Active Failed – Transmission Problem Active Failed – Transmission Problem
Active Failed – Unprotected Active Failed – Unprotected
Active Failed – APE failed Active Failed – APE failed
Active Failed – Cross Connection Problem Active Failed – Cross Connection Problem
Active Failed – Preemption Active Failed – Preemption
Active Failed – End Point Failure Active Failed – End Point Failure
Reroute Not possible Reroute Not possible
Ready To Revert Ready To Revert
SNC in Automatic Restoration Disabled SNC in Automatic Restoration Disabled
Test Mode enabled Test Mode enabled
SNC Backup Unavailable SNC Backup Unavailable
APE In Progress APE In Progress
TCA Channel Margin TCA Channel Margin
Optical Feasibility Violation Optical Feasibility Violation
SRG Violation SRG Violation
Link Diversity Violation Link Diversity Violation
Channel Assignment Violation Channel Assignment Violation
Latency Violation Latency Violation
Nomainal Link Violation Nominal Link Violation
Color Violation Color Violation

Elementary alarm on SNC (by GMRE) Correlated alarm on ASON SNC

SNC SNCP Degraded SNC SNCP Degraded (L1 only; PRC not in
LO CP)

Elementary alarm on CP (by GMRE) Correlated alarm on ASON NPA

NE not reachable by Control Plane GMRE Degraded
GMRE degraded GMRE Degraded
GMRE in migration GMRE in migration
RSVP Down CP Communication Interface Problem
RSVP Degraded CP Communication Interface Problem
DPR Down CP Communication Interface Problem
DPR Degraded CP Communication Interface Problem
RSVP Network Version Mismatch CP Communication Interface Problem
DPR Network Version Mismatch CP Communication Interface Problem
GMRE Automatic Restoration disabled GMRE Automatic Restoration disabled
GMRE halted GMRE halted
Fast Photonic Restoration Mode Mismatch Fast Photonic Restoration Mode Mismatch

Abbreviations
Abbreviations and Meanings

Abbreviation Meaning
ASON Automatically Switched Optical Network
CC control channel
CLI command line interface
CP Control Plane
DSR Digital Service Rate
EC Equipment Controller
E-NNI External Network-Network Interface
EPT Engineering and Planning Tool
FLC First-Level Controller
FSC Fiber Switching Capability
FA_TERM forward adjacency-terminated
FA-UNTERM forward adjacency-unterminated
GMPLS Generalized Multi protocol Label Switching
GMRE Generic MPLS Routing Engine
GR Guaranteed Restoration
I-NNI Internal Network-Network Interface
ISC Interface Switching Capability
LSC Lambda Switching Capability
LMP Link Management Protocol
MRN Multi-Region Network

Abbreviation Meaning
MLN Multi-Layer Network
MA Maintenance Association
MAC Media Access Control
MC-LAG Multi-Chassis Link Aggregation Group
MEP Maintenance End Point
MIB Management Information Base
MPLS Multiprotocol Label Switching
MPLS-TP Multiprotocol Label Switching-Transport Bridging
NE Network Element
NML Network Management Layer
NPA Network Protection Architecture
OCH Optical Channel
OCS Optical Core Switching
ODU Optical Data Unit
OI Open Interfaces
OMS Optical Management System
OPS Optical Physical Section
OSPF Open Shortest Path First
OTN Optical Transport Network
O-SNCP Optical-Subnetwork Connection Protection
PC Protocol Controller
PM Performance Monitoring
PSC Protection Switch Control
PSN Packet Switched Network
PSS Photonic Service Switch
PRC Protection and Restoration Combined
RH Route Handler
SNC Subnetwork Connection
SNCP Simple Network Management Protocol
SPC soft-permanent connections
SRG Shared Risk Groups
TDM Time Division Multiplexed Switching
....................................................................................................................................................................................................................................
B-2 Nokia 1350 OMS
8DG43185XAAA Release 14.0
Issue 2 October 2016
List of Abbreviations Abbreviations

Abbreviation Meaning
TE-Link Traffic Engineered link
UNI User Network Interface
VPN Virtual Private Network
WDM Wavelength Division Multiplexing
WTR Wait to Restore

Numerics 3R Tab, 5-9 Disable Test Mode, 6-103

11DPE12 circuit pack, 4-65 Add Links to ASON, 6-29 Display Route on Map, 6-85
11DPE12E circuit pack, 4-65 Auto Restoration Enable TCM, 6-99
11DPM12 circuit pack, 4-66 Enable/Disable, 6-70
Enable Test Mode, 6-102
3R Change ASON WTR, 6-50
End Points tab, 5-19
Add to NPA, 6-66, 6-67 Deimplement, 6-37
Explore - Routing Display,
Create a 3R, 6-63 Fast Photonic Restoration, 6-104
6-62
Implement and Deimplement, Inherited Priorities, 6-92
6-68 Implement, 6-36
Manage SNCP, 6-106
Remove 3R, 6-69 ASOn NPA
Misalignment Report, 6-89
............................................................. Implement, 6-36
Modify attributes, 6-111
ASON NPA
A ASON, 4-6 Nominal Route Problems, 5-29
Jobs, 6-72
Create SRG, 6-120 SNC Restoration Constraints,
Link Maintenance, 6-53 6-107
NPA, 6-23
Links tab, 5-22 Switch to Backup, 6-115
NPA icons, 5-3
Modify TE-Links, 6-76 Switch to Nominal, 6-114
Reset Table Preferences, 5-40
Nodes tab, 5-26 Tandem Connection
Save Table Preferences, 5-40
Monitoring, 6-99
Remove NPA, 6-79
Shared Risk Group, 6-118
Test Mode, 6-102
TE Links tab, 5-36
SNC, 6-80
Audience intended for this
TE-Link Assignment, 6-43
SNC icons, 5-3 document, xix
ASON NPA Links
ASON Control Plane Auto discovery
Administrative State, 6-47
Auto Restoration, 6-40 of clients, 4-8
ASON SNC
Automatic Restoration of physical connections, 4-7
window, 6-41 Convert current to Nominal,
Auto Discovery
6-115
ASON NPA
Y-Cable Protection and, 4-67
Disable TCM, 6-100
3R, 6-63

definition, 4-51 terminated connection, 4-58 I Icons

delete and DB delete and, 4-55 trails, 4-4, 4-6 Export to csv, 5-43
functional description, 4-51 unterminated connection, 4-58 Internal OS connections
routing mode considerations, unterminated OTUk/ODUk type A connection definition,
4-51 infrastructures without virtual 4-7
termination, 4-59
supported configurations, 4-51 type B connection definition,
user-defined, 4-3 4-7
Auto Restoration
Cross connections .............................................................
Activate, 6-40
SNC Protection and, 4-69
Deactivate, 6-42 L Link connections
.............................................................
Automatic Switched Optical definition, 4-5
Network (ASON), 4-6 D Definitions, 2-18 external link connection
............................................................. Auto Payload, 4-51 definition, 4-5

C Circuit packs client, 4-6 internal link connection

definition, 4-5
11DPE12, 4-65, 4-65 connection, 4-3
Logical connections
11DPM12, 4-66 external link connections, 4-5
definition, 4-4
Clients external OS connection, 4-7
L-OPCs
auto discovery of, 4-8 external OTS connection, 4-7
definition, 4-4
definition, 4-6 internal link connections, 4-5
.............................................................
Color Profile internal links, 4-7
M MRN
Associate ASON Domain, internal OS, type A connection,
6-143 4-7 forward adjacency-terminated
(FA_TERM) connection,
Configuration State internal OS, type B connection,
4-58
4-7
Deimplemented, 6-37
forward adjacency-untermated
link connections, 4-5
Implemented, 6-36 (UNTERM) connection, 4-58
server, 4-6
Connections .............................................................
terminated connection, 4-58
automatically added, 4-3 N NEs
unterminated connection, 4-58
client/server relationships and, add a node/NE, 4-75
4-6 Documentation
Network Profile
discovered, 4-3 list of related customer
documentation, xxiii Modify Alarm Profile, 6-157
link, 4-3
............................................................. Network Profiles
logical, 4-3, 4-4
Alarm Profile, 6-154
manually provisioned, 4-3 F Features
Color Profile, 6-140
paths, 4-4, 4-6, 4-10 Auto Payload, 4-51
NIM, 4-70, 4-70, 4-70, 4-70, 4-71
physical, 4-3, 4-3, 4-6
....................................................................................................................................................................................................................................
IN-2 Nokia 1350 OMS
8DG43185XAAA Release 14.0
Issue 2 October 2016
Index

add a node/NE, 4-75 Protection Y Y-Cable Protection

NPA SNC Protection, 4-69 11DPM12 circuit pack and,
Correlate ASAP, 6-58 ............................................................. 4-66

............................................................. provisioning 11DPE12 and

S Safety information, xix
11DPE12E circuit packs,
O OCH Servers 4-65
96 channels, 6-12 definition, 4-6 provisioning guidelines for,
4-64
operate Shared Risk Group
Y-cable definition, 4-64
Wavelength Usage Report, Remove SRG, 6-133
6-160
TE Link, 6-127
Operate
Shared Risk Groups
Wavelength Usage Report,
TE Links, 6-132
6-161
SNC Protection
OPSB
NIM, 4-70
parameter in SNC Protection
provisioning, 4-70 provisioning of, 4-69

OS connections rerouted connections and, 4-71

definition of external OS SNC-I, 4-70

connection, 4-7 SNC-N, 4-70
definition of internal links, 4-7
SNC-Nc, 4-70
OTS special 1830 PSS
Generate Wavelength Usage considerations, 4-71
Report, 6-162 SRG
OTS connections
Correlate SRG, 6-123
definition of OS internal link, Link Maintenance, 6-120
4-7
SRGs
.............................................................
definition, 2-18
P Paths
Subnetwork Connection Protection
client/server relationship and, See: SNC Protection
4-6
.............................................................
definition, 4-4
T Tandem connections, 4-6
Physical connections
Trails
add, 4-16
client/server relationship and,
automatic discovery of, 4-7
4-6
client/server relationship and, definition, 4-4
4-6
....................................................................................................................................................................................................................................
Nokia 1350 OMS IN-3
8DG43185XAAA Release 14.0
Issue 2 October 2016
Index

Worksheet Class Xii Ip 2023-24
No ratings yet
Worksheet Class Xii Ip 2023-24
143 pages
Arduino LCD Tutorial - How To Connect An LCD To Arduino
No ratings yet
Arduino LCD Tutorial - How To Connect An LCD To Arduino
27 pages
The Subtle Art of Not Giving a F*ck: A Counterintuitive Approach to Living a Good Life
From Everand
The Subtle Art of Not Giving a F*ck: A Counterintuitive Approach to Living a Good Life
Mark Manson
4/5 (6458)
FBC Lab Manual - 4361603-1
No ratings yet
FBC Lab Manual - 4361603-1
48 pages
Ahmad Javaid - Software Engineer
No ratings yet
Ahmad Javaid - Software Engineer
1 page
Interactive Map
No ratings yet
Interactive Map
2 pages
Chapter 6 Part1 Hands-On Exercies With Answers
No ratings yet
Chapter 6 Part1 Hands-On Exercies With Answers
8 pages
101521-Report On The Physical Count of Property, Plant - Equipment-RPCPPE
No ratings yet
101521-Report On The Physical Count of Property, Plant - Equipment-RPCPPE
4 pages
Principles: Life and Work
From Everand
Principles: Life and Work
Ray Dalio
4/5 (648)
Anomaly-Based IDS To Detect Attack Using Various...
No ratings yet
Anomaly-Based IDS To Detect Attack Using Various...
5 pages
Chapter 1 How The Web Works
No ratings yet
Chapter 1 How The Web Works
81 pages
Never Split the Difference: Negotiating As If Your Life Depended On It
From Everand
Never Split the Difference: Negotiating As If Your Life Depended On It
Chris Voss
4.5/5 (1005)
Multimedia DLL
No ratings yet
Multimedia DLL
5 pages
Grit: The Power of Passion and Perseverance
From Everand
Grit: The Power of Passion and Perseverance
Angela Duckworth
4/5 (650)
Basic ITK Customization Concept Part-01
No ratings yet
Basic ITK Customization Concept Part-01
1 page
Schneider Electric Altivar Machine ATV320 DTM Library V1.7.7 ReleaseNotes
No ratings yet
Schneider Electric Altivar Machine ATV320 DTM Library V1.7.7 ReleaseNotes
8 pages
The Gifts of Imperfection: Let Go of Who You Think You're Supposed to Be and Embrace Who You Are
From Everand
The Gifts of Imperfection: Let Go of Who You Think You're Supposed to Be and Embrace Who You Are
Brené Brown
4/5 (1175)
The Little Book of Hygge: Danish Secrets to Happy Living
From Everand
The Little Book of Hygge: Danish Secrets to Happy Living
Meik Wiking
3.5/5 (464)
The Glass Castle: A Memoir
From Everand
The Glass Castle: A Memoir
Jeannette Walls
4.5/5 (1856)
Computer Organization-Chapter 9
No ratings yet
Computer Organization-Chapter 9
9 pages
Mark 7 Arterion Injection System Brochure (PP-M-MARK-US-0076-1) - 0
No ratings yet
Mark 7 Arterion Injection System Brochure (PP-M-MARK-US-0076-1) - 0
9 pages
A Man Called Ove: A Novel
From Everand
A Man Called Ove: A Novel
Fredrik Backman
4.5/5 (5181)
FD1104SN-R1 Datasheet V1.0
100% (1)
FD1104SN-R1 Datasheet V1.0
2 pages
Sing, Unburied, Sing: A Novel
From Everand
Sing, Unburied, Sing: A Novel
Jesmyn Ward
4/5 (1267)
Motion UI
No ratings yet
Motion UI
3 pages
PRELIM LAB QUIZ 1 - Attempt Reviewadadawasd
No ratings yet
PRELIM LAB QUIZ 1 - Attempt Reviewadadawasd
4 pages
More About Spreadsheet Errors and Fixes
100% (1)
More About Spreadsheet Errors and Fixes
3 pages
The Hard Thing About Hard Things: Building a Business When There Are No Easy Answers
From Everand
The Hard Thing About Hard Things: Building a Business When There Are No Easy Answers
Ben Horowitz
4.5/5 (361)
Hidden Figures: The American Dream and the Untold Story of the Black Women Mathematicians Who Helped Win the Space Race
From Everand
Hidden Figures: The American Dream and the Untold Story of the Black Women Mathematicians Who Helped Win the Space Race
Margot Lee Shetterly
4/5 (1022)
Shoe Dog: A Memoir by the Creator of Nike
From Everand
Shoe Dog: A Memoir by the Creator of Nike
Phil Knight
4.5/5 (629)
Elon Musk: Tesla, SpaceX, and the Quest for a Fantastic Future
From Everand
Elon Musk: Tesla, SpaceX, and the Quest for a Fantastic Future
Ashlee Vance
4.5/5 (582)
Her Body and Other Parties: Stories
From Everand
Her Body and Other Parties: Stories
Carmen Maria Machado
4/5 (903)
The Sympathizer: A Novel (Pulitzer Prize for Fiction)
From Everand
The Sympathizer: A Novel (Pulitzer Prize for Fiction)
Viet Thanh Nguyen
4.5/5 (141)
The Emperor of All Maladies: A Biography of Cancer
From Everand
The Emperor of All Maladies: A Biography of Cancer
Siddhartha Mukherjee
4.5/5 (298)
The Perks of Being a Wallflower
From Everand
The Perks of Being a Wallflower
Stephen Chbosky
4.5/5 (4103)
Steve Jobs
From Everand
Steve Jobs
Walter Isaacson
4.5/5 (1139)
Digital Marketing
No ratings yet
Digital Marketing
41 pages
P170SM Service Manual: Downloaded From Manuals Search Engine
No ratings yet
P170SM Service Manual: Downloaded From Manuals Search Engine
126 pages
Structure of The ISO/IEC 15504-5:2012 Model
No ratings yet
Structure of The ISO/IEC 15504-5:2012 Model
11 pages
Quamet MSC530M G02 3T 2020-2021 - Part IV
No ratings yet
Quamet MSC530M G02 3T 2020-2021 - Part IV
2 pages
The World Is Flat 3.0: A Brief History of the Twenty-first Century
From Everand
The World Is Flat 3.0: A Brief History of the Twenty-first Century
Thomas L. Friedman
3.5/5 (2289)
Angela's Ashes: A Memoir
From Everand
Angela's Ashes: A Memoir
Frank McCourt
4.5/5 (943)
A Study On Social Media and Its Impact On Youth
No ratings yet
A Study On Social Media and Its Impact On Youth
10 pages
Cprcs It Kerala
No ratings yet
Cprcs It Kerala
17 pages
The Yellow House: A Memoir (2019 National Book Award Winner)
From Everand
The Yellow House: A Memoir (2019 National Book Award Winner)
Sarah M. Broom
4/5 (100)
Yes Please
From Everand
Yes Please
Amy Poehler
4/5 (2016)
Brooklyn: A Novel
From Everand
Brooklyn: A Novel
Colm Toibín
3.5/5 (2141)
The Woman in Cabin 10
From Everand
The Woman in Cabin 10
Ruth Ware
3.5/5 (2814)
Bad Feminist: Essays
From Everand
Bad Feminist: Essays
Roxane Gay
4/5 (1090)
ManualOperacion CJ1 CS1-ETN PDF
No ratings yet
ManualOperacion CJ1 CS1-ETN PDF
314 pages
EOS IT Support Service L1 & L2
No ratings yet
EOS IT Support Service L1 & L2
82 pages
Devil in the Grove: Thurgood Marshall, the Groveland Boys, and the Dawn of a New America
From Everand
Devil in the Grove: Thurgood Marshall, the Groveland Boys, and the Dawn of a New America
Gilbert King
4.5/5 (280)
The Art of Racing in the Rain: A Novel
From Everand
The Art of Racing in the Rain: A Novel
Garth Stein
4/5 (4372)
A Tree Grows in Brooklyn
From Everand
A Tree Grows in Brooklyn
Betty Smith
4.5/5 (2033)
Oracle 1z0-960 v2018-03-23 q61
No ratings yet
Oracle 1z0-960 v2018-03-23 q61
21 pages
A Heartbreaking Work Of Staggering Genius: A Memoir Based on a True Story
From Everand
A Heartbreaking Work Of Staggering Genius: A Memoir Based on a True Story
Dave Eggers
3.5/5 (233)
AFT Impulse 8 Data Sheet
No ratings yet
AFT Impulse 8 Data Sheet
2 pages
AMVER Introduction
100% (1)
AMVER Introduction
14 pages
Wolf Hall: A Novel
From Everand
Wolf Hall: A Novel
Hilary Mantel
4/5 (4135)
Rise of ISIS: A Threat We Can't Ignore
From Everand
Rise of ISIS: A Threat We Can't Ignore
Jay Sekulow
3.5/5 (144)
The Outsider: A Novel
From Everand
The Outsider: A Novel
Stephen King
4/5 (2886)
Install Shield User Guide
No ratings yet
Install Shield User Guide
2,504 pages
Fear: Trump in the White House
From Everand
Fear: Trump in the White House
Bob Woodward
3.5/5 (836)
On Fire: The (Burning) Case for a Green New Deal
From Everand
On Fire: The (Burning) Case for a Green New Deal
Naomi Klein
4/5 (78)
Team of Rivals: The Political Genius of Abraham Lincoln
From Everand
Team of Rivals: The Political Genius of Abraham Lincoln
Doris Kearns Goodwin
4.5/5 (244)
Manhattan Beach: A Novel
From Everand
Manhattan Beach: A Novel
Jennifer Egan
3.5/5 (919)
The Light Between Oceans: A Novel
From Everand
The Light Between Oceans: A Novel
M.L. Stedman
4.5/5 (815)
The Unwinding: An Inner History of the New America
From Everand
The Unwinding: An Inner History of the New America
George Packer
4/5 (45)
John Adams
From Everand
John Adams
David McCullough
4.5/5 (2546)
The Constant Gardener: A Novel
From Everand
The Constant Gardener: A Novel
John le Carré
4/5 (278)
Little Women
From Everand
Little Women
Louisa May Alcott
4.5/5 (2369)

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.

Title Page 1350 Optical Management Syste PDF

Uploaded by

Title Page 1350 Optical Management Syste PDF

Uploaded by

Title page

Information product support

About this document

What's new .................................................................................................................................................................................... xix

Safety information ..................................................................................................................................................................... xix

Intended audience ...................................................................................................................................................................... xix

Document parts ............................................................................................................................................................................ xx

Conceptual and task content .................................................................................................................................................... xx

Format of task content ............................................................................................................................................................... xx

Technical content ........................................................................................................................................................................ xxi

Treatment of terms ..................................................................................................................................................................... xxi

Related documentation ........................................................................................................................................................... xxii

Document formats ................................................................................................................................................................... xxiii

On-line help ............................................................................................................................................................................... xxiii

Ordering information ............................................................................................................................................................. xxiii

How to comment ..................................................................................................................................................................... xxiii

Part I: Understanding the Product and Concepts

Overview ...................................................................................................................................................................................... 1-1

ASON ............................................................................................................................................................................................ 1-2

ASON/GMPLS Control Plane ............................................................................................................................................ 1-7

GMPLS Routing Engine ...................................................................................................................................................... 1-15

ASON Architecture Concepts ............................................................................................................................................ 1-17

ASON Features and Supporting Functionalities ......................................................................................................... 1-19

Overview ...................................................................................................................................................................................... 2-1

ASON Overview in 1350 OMS ........................................................................................................................................... 2-2

ASON Concepts applied in 1350 OMS ............................................................................................................................ 2-3

ASON Connection Setup ..................................................................................................................................................... 2-12

ASON Protection and Restoration ................................................................................................................................... 2-14

Network Backbone Setup ................................................................................................................................................... 2-18

Overview ...................................................................................................................................................................................... 3-1

ASON Configuration Flow ................................................................................................................................................... 3-2

Macro-steps for ASON Configuration .............................................................................................................................. 3-5

Network Construction ............................................................................................................................................................. 3-8

Bundling rule ............................................................................................................................................................................ 3-11

High Level Provisioning Flow for Layer 0 GMRE ................................................................................................... 3-12

High Level Provisioning Flow for Layer 1 GMRE ................................................................................................... 3-18

4 1350 OMS ASON Provisioning

Overview ...................................................................................................................................................................................... 4-1

Connection Definition, Creation, and Categorization ................................................................................................. 4-3

Connection Auto Discovery and User Creation of Connections ............................................................................. 4-7

Infrastructure Connections and Services ....................................................................................................................... 4-10

Client/Server Relationships ............................................................................................................................................... 4-15

Create an OTN Physical Connection .............................................................................................................................. 4-16

Modify the Allocation Cost of a Physical Connection ............................................................................................. 4-38

Modify the Parameters of an Infrastructure Connection or Service .................................................................... 4-40

Single Step Provisioning ..................................................................................................................................................... 4-42

Modify the Route (Reroute) of a Connection .............................................................................................................. 4-45

Auto Payload ............................................................................................................................................................................ 4-51

Auto Creation of Edge Connections ................................................................................................................................ 4-56

Unterminated OTUk/ODUk Infrastructures without Virtual Termination Management ............................. 4-58

Y-Cable Protection for Services ........................................................................................................................................ 4-64

SNC Protection for 1830 PSS OCS NEs ....................................................................................................................... 4-69

OPSB Protection ..................................................................................................................................................................... 4-72

Nodes and Network Elements

Add a Node/NE ....................................................................................................................................................................... 4-75

Synchronize Nodes and NEs .............................................................................................................................................. 4-88

Part II: Working with 1350 OMS ASON WebUI

5 1350 OMS ASON WebUI

Overview ...................................................................................................................................................................................... 5-1

Navigate to ASON ................................................................................................................................................................... 5-2

NPA and SNC: Icons ............................................................................................................................................................... 5-3

NPA and SNC: Tabs ................................................................................................................................................................. 5-8

3R Tab ........................................................................................................................................................................................... 5-9

ASON SNCs tab of ASON NPA ....................................................................................................................................... 5-10

Alarms tab ................................................................................................................................................................................. 5-13

Control Planes tab of ASON NPA .................................................................................................................................... 5-15

End Points Tab of ASON SNCs ........................................................................................................................................ 5-19

Links tab of ASON NPA ...................................................................................................................................................... 5-22

Nodes tab of ASON NPA .................................................................................................................................................... 5-26

Nominal Route Problems Tab ............................................................................................................................................ 5-29

Routes tab of ASON SNCs ................................................................................................................................................. 5-33

SNCP tab of ASOn SNCs .................................................................................................................................................... 5-35

TE Links tab of ASON NPA .............................................................................................................................................. 5-36

Save and Reset Table Preferences .................................................................................................................................... 5-40

Export a Data Table to a .CSV File .................................................................................................................................. 5-43

6 1350 OMS WebUI – Working in ASON