You are on page 1of 176

Table of Contents

STMS overview
STMS Alarms
NMS LightSoft Introduction
NMS Elements & Groups
NMS Topology Links
NMS Optical Trails
TCI -Trail Consistency Indicator
TR10_4 Configuration
TR100 Configuration
CMR40 Configuration
AoC10 Card Configuration
CMR100 Configuration
Theory of ASON Technology
ASON Technology Implementation in Apollo
DNI Configuration
DRI Configuration

3
19
27
39
47
53
71
79
87
97
105
117
131
145
161
169

ECI Telecom Ltd.

Global Professional Services

This page is intentionally blank

ECI Training Services

STMS Integrated
ShadeTree Management Suite

Global Services Division


ECI Training Department
1/30

STMS Overview

Content








Introduction
STMS architecture and platforms
STMS client
Configuration features
Faults
PM Performance Monitoring
DB Backup

2/30

STMS Overview

Introduction
 STMS (ShadeTree Management Suite) is the element
management (EMS), service provisioning and
monitoring solution for the Apollo (OPT9600) products
family:
 OPT9624H & OPT9624L
 OPT9608
 OPT9603

 STMS provides FCAPS:


1.
2.
3.
4.
5.

Fault
Configuration
Accounting
Performance
Security

3/30

STMS Overview

TMN Architecture
Business/Service
Management

Northbound OSS: MTNM

Network
Management
Third-party NMS

LightSoft NMS

NMS client

Java RMI

CORBA/MTNM (TMF-814)

Element
Management
STMS Client

JDBC

Java
RMI

Oracle
Database

STMS
SNMP

CORBA over SSL

Network
Element

OPT9603

OPT9608

4/30

OPT9624
STMS Overview

LightSoft or NMS/OSS Integration


 STMS is fully integrated with LightSoft to support:







Inventory management
Alarm management
PMs
Topology links/Optical trails configuration
ODU XC Configuration
GUI cut-through

 STMS can integrate with existing OSS applications via


the Northbound Application Programming Interface
(NB-API) that supports Java RMI
LightSoft/NMS
CORBA/MTNM (TMF-814)
Java RMI NorthBound API

STMS
5/30

STMS Overview

STMS Platforms
 Carrier grade three tier architecture
 Server:
Sun Solaris 9, 10
RedHat Linux RHEL 3, RHEL 4
 Database:
Oracle 9i, 10g
 Thin client Java GUI:
Windows XP, 2000, 7
Solaris
Linux

6/30

STMS Overview

STMS Client
 STMS Client is a Java-based GUI from which operators
can manage STMS server
 The STMS Client can run as a standalone application
on Windows, Linux, Solaris or any other platform that
supports Java
 Client must resolve the host-name of the STMS server
 Configure DNS server
 Or edit hosts file

7/30

STMS Overview

Entering STMS
1. In NMS LightSoft, go to the Physical (EMS) layer
2. Right click the STMS and Open

8/30

STMS Overview

Navigating STMS

Network Element work table


Network Explorer
Alarms, Events & Log tabs

9/30

STMS Overview

Navigating STMS
 Network Explorer
 Displays a representation of the network in the form of a tree
hierarchy

10/30

STMS Overview

Creating a Group

Creation of sub-groups is possible by creating a new folder under an existing


one, or by dragging a folder below another one
Uploading an NE into a group can be done by the Discover NE option on
each folder you can also drag and move NEs between folders (NOT service
11/30
STMS Overview
affecting)

Navigating STMS
 Customer Explorer
 Displays all of the services and XS assigned to a specific customer

12/30

STMS Overview

Inventory View
 Graphical representation of the chassis

13/30

STMS Overview

Slot Assignment

14/30

STMS Overview

Installed Modules
 The Show Actual checkbox shows which modules are
physically
installed in
the chassis

15/30

STMS Overview

Assigned Vs. Actual


Actual card (yellow
background) is OA_ML
Assigned card (gray
background) is OA_ML

Actual card (yellow


background) is OA_ML
Assigned card (gray
background) is TR10_4

16/30

Actual card (yellow


background) is empty slot
Assigned card (gray
background) is ROADM

STMS Overview

10

Physical Port Configuration

17/30

STMS Overview

Fiber Connectivity

18/30

STMS Overview

11

Cross Connections

19/30

STMS Overview

Creating Users in STMS


2
1
 In the Server Preferences tab, click the Users tab
 Click Create User.. 3

2
3

20/30

STMS Overview

12

Fault Management
 Alarm management





Multiple alarm levels


Displays only active alarms
Correlates alarms into a single notification
Uploaded as they are into LightSoft

21/30

STMS Overview

Fault Management
Displays Network events

Displays STMS messages that


indicate system events, exceptions,
or conditions

Displays STMS Client messages that


indicate non-error system events or
conditions, such as network elements
being discovered

Displays STMS Client messages of


system exceptions or conditions
22/30

STMS Overview

13

PM

23/30

STMS Overview

PM

24/30

STMS Overview

14

NE DB Backup
1) Tools -> Configuration Manager

2) Enter username and password


for STMS users in the STMS zone and select the
communication protocol

25/30

STMS Overview

NE DB Backup
 To create an immediate one time backup, click on Create

 Enter a label, select the NEs to be backed up. And click


on OK.

26/30

STMS Overview

15

NE DB Backup
 The backup file is created and listed in the Backup
Manager tab.

27/30

STMS Overview

Backup Scheduler
 Go to Backup Scheduler tab and Click on Create,

 Enter the Schedule attributes and click on OK.

28/30

STMS Overview

16

Restore DB
 Right click on the DB file from the Backup Manager list
and select Restore

29/30

STMS Overview

Summary
 Introduction
 EMS for Apollo products family

 STMS Architecture and Platforms


 Integrated into LightSoft

 STMS Client
 STMS can work as standalone

 Configuration Features
 Ports, Fiber Connectivity, Cross-Conections

 Faults
 Alarms, Logs and Events

 PM
 DB Backup
30/30

STMS Overview

17

ECI Telecom Ltd.

Global Professional Services

This page is intentionally blank

18

ECI Training Services

STMS Alarms

Global Services Division


ECI Training Department
1/16

STMS Alarms

Content








Alarm Hierarchy
Alarm Types
Alarm Window
Historical Alarms
Alarm Details
Managing Alarms
Alarm Preferences

2/16

STMS Alarms

19

Alarm Hierarchy
 In the STMS, alarm indications are propagated through
the object hierarchy and are displayed up to the highest
level

NE
Card

Alarm

Port
Unit
3/16

STMS Alarms

Alarm Types
 Alarms conditions are classified according to severity
levels and are visually reflected in the STMS Client
window using the following colors and indications:
Severity

Color

Indicator

Minor

Yellow

Indicates problem conditions that do not


have a serious effect on service to
customers or are not essential to
network element operations.

Major

Orange

Indicates a serious disruption of service


or the malfunctioning or failure of
important components or functions.

Critical

Red

Indicates a severe, service-affecting


condition and that immediate corrective
action is imperative.

Clear

White/Green

None

4/16

20

Description

Indicates that an alarm condition no


longer exists.
STMS Alarms

Alarm Window
 Table view (the default view) displays alarms in a simple
table format
 Each alarm is displayed as a separate row in the table
 In table view, double-clicking a row opens the property sheet for
the object associated with the alarm

5/16

STMS Alarms

Alarm Window
Severity

Description

Ack

Whether the alarm has been acknowledged. If the


alarm has been acknowledged, a check mark will appear in the box

Time

The time of the Alarm

Clear Time

The time an associated clear alarm was received

Source

The host name or IP address of the network element associated


with the alarm

Name

The object (i.e., subinterface, logical interface, etc.) associated with


the alarm

Severity

The severity of the Alarm

Type

The type of the Alarm

SA

Whether the alarm is Service Affecting

Description

A short description of the alarm

6/16

STMS Alarms

21

Historical Alarms
 By default, the STMS does not maintain nor display
information about historical alarms, only active alarms

If order to retain historical


alarm information, this
feature must be enabled
7/16

STMS Alarms

Historical Alarms
 Viewing historical alarms

8/16

STMS Alarms

22

Alarm Details
Right Click

9/16

STMS Alarms

Alarm Details
Column
Time

10/16

Description
The time of the Alarm

Element Name

The object (i.e., subinterface, logical interface, etc.)

Source NE

The host name or IP address of the network element

Trap Name

The trap name for the alarm

Severity

Minor, Major, Critical

Service Affecting

Whether the alarm is service affecting (SA)

Acknowledged

Whether the alarm has been acknowledged

Acknowledged by

Displays the STMS user name of the user who


acknowledged the alarm

Acknowledged at

Displays the date and the time that the alarm was
acknowledged

Annotation

Any notes about the alarm

Short Description

A short description of the alarm

Detailed Description

A detailed description of the alarm


STMS Alarms

23

Managing Alarms
 Acknowledging Alarms

Right Click

11/16

STMS Alarms

Clearing Inactive Alarms


 Auto-Clearing
 STMS automatically correlates clear alarms with active
alarms
 By default, when a clear alarm is received, the associated active
alarm is automatically cleared and removed from the list of
active alarms in the STMS

12/16

STMS Alarms

24

Clearing Inactive Alarms


 Clearing manually

13/16

STMS Alarms

Alarm Preferences

14/16

STMS Alarms

25

Alarm Preferences

15/16

STMS Alarms

Summary
 Alarm Hierarchy
 Alarm indications are propagated through the object hierarchy and
are displayed up to the highest level

 Alarm Types
 Minor, Major, Critical, Clear

 Alarm Window
 Displays alarms in a simple table format

 Historical Alarms
 Disabled by default

 Alarm Details
 Displays information regarding selected alarm

 Managing Alarms
 Acknowledge, Clearing

 Alarm Preferences
 Notification parameters

16/16

STMS Alarms

26

NMS LightSoft V6
Introduction

Global Services Division


ECI Training Department
1.21

LightSoft GUI

Management Architecture
OSS

TMF-MTNM Corba I/F


Network
Management
Layer

Element
Management
Layer

LightSoft

TMF-MTNM Corba I/F


EMSEMS-XDM

EMSEMS-BGF

Other EMSs

Managed
Equipment
BG line

XDM line
2.21

Other
equipment
LightSoft GUI

27

Tabs No More Menus


 NMS LightSoft has a modern look and feel

ECI Button

Tabs no menus

3.21

LightSoft GUI

ECI Button
 ECI button contains the Help and About LightSoft
options
 The ECI Button menu cannot be customized

4.21

LightSoft GUI

28

LightSoft Ribbon
 The LightSoft ribbon is maximized or minimized

Minimized

Maximized

 To maximize or minimize:
 Double click a tab
 Ctrl + F1
 View tab
click on Ribbon
5.21

LightSoft GUI

Quick Access Area

Technology
Layers

Consistency
Indicators

Alarm
Counters

 Above the ribbon


 Static (always visible to user)
 Displays:
 Technology layers
 Consistency indicators
 Alarm counters

6.21

LightSoft GUI

29

Technology Layers
 LightSoft has traffic from
different technology types
 You can see the elements
processing the different traffic types:
 Optical (WDM, OTN)
 SDH
 Ethernet & MPLS

 Example:
If you go to the ETH/MPLS layer, you see where in your
topology you have Ethernet or MPLS cards & traffic
7.21

LightSoft GUI

Topology Layer Types









Physical (Site)
Physical (EMS)
SDH/SONET
Optical (OTN)
OCH
Ethernet/MPLS Physical
(EMS)

Physical
(Site)

SDH/
SONET

Optical
(OTN)
Ethernet/MPLS

8.21

LightSoft GUI

30

Example of Layers
 Physical (Site):
This layer shows your
whole network, including
3rd party equipment
(technology transparent)

 ETH/MPLS
This layer shows your
Ethernet and MPLS
switches in your
network
9.21

LightSoft GUI

Elements
 ME/NE: Managed/Network Element

 UME: Unmanaged Element

 Groups

10.21

LightSoft GUI

31

Topology Links
 Represent the physical connections between elements
 Must be created before provisioning traffic

11.21

LightSoft GUI

Provisioned Traffic
 Trail List shows the trails in the network

12.21

LightSoft GUI

32

Inserting an Element

After

Before

13.21

LightSoft GUI

Consistency Indicators

 Show the inconsistencies between the NMS LightSoft


DB, and the EMS databases

Client
(GUI)

Server
(Database)

EMS XDM
DB

EMS
BG DB

BroadGate

XDM
14.21

33

Other
EMS DB

Other
transport
equipment

LightSoft GUI

Alarm Counters

 A general picture of all the alarms in the system


Alarm Color

Alarm types

Red

Severe and Major alarms

Yellow

Minor and Warning alarms

15.21

LightSoft GUI

Context Sensitive Tabs


 CST an accepted industry standard
 This tab contains only relevant commands for selected
elements (Nodes, Groups and Links)

16.21

LightSoft GUI

34

Hot Keys
 Pressing Alt toggles hot key tips
 Once the are tips displayed, type the letter to open that
tab level 1

17.21

LightSoft GUI

Hot Keys continued


 When you go to that tab, you see the hot keys for that
tab level 2

 If there is more than one letter in the key, pressing the


keys should be sequential and not simultaneous
i.e. for FC, press F, then C
18.21

LightSoft GUI

35

Tree Seeing the Network


 View

Tree

The Tree shows all


MEs in the topology

19.21

LightSoft GUI

View Functions
 Zoom & Navigation
Seeing all, or different parts of the topology
 Move moving elements on the screen and
saving/not saving changes
 Map working with groups of elements
(Expanding or collapsing groups)

Map
20.21

Move

Zoom & Navigation

36

LightSoft GUI

Summary
 Tabs No More Menus
 ECI Button
 LightSoft Ribbon
 Minimizing/Maximizing
 Categories in each tab

 Quick Access Area


 Technology layers
 Consistency indicators
 Alarm Counters

 Context Sensitive Tabs


 Hot Keys
 Tree, and View menu
21.21

LightSoft GUI

37

ECI Telecom Ltd.

Global Professional Services

This page is intentionally blank

38

ECI Training Services

Elements & Groups in NMS


NMS LightSoft

Global Services Division


ECI Training Department
1.15

Elements

Content





Creating a Managed Element (ME)


Creating a Logical Element (LE)
Creating and Modifying an Unmanaged Element (UME)
Creating and Modifying Groups

2.15

Elements

39

Topology Layer Types









Physical (Site)
Physical (EMS)
SDH/SONET
Optical (OTN)
OCH
Ethernet/MPLS Physical
(EMS)

Physical
(Site)

SDH/
SONET

Optical
(OTN)
Ethernet/MPLS

3.15

Elements

Creating an ME
2

1
1. Switch to Physical (EMS) layer
2. Right click on the relevant EMS

3. A Create ME window opens.


Fill in the required fields
4. OK
5. The ME appears in
the physical (site) layer

4.15

Elements

40

Logical Elements (LE)


 An element in a technological layer is referred to as an
LE
 LEs are created automatically when an ME is added to
network on the Physical Layer
 An LE represents the capabilities of the ME and type of traffic it
can carry
 LEs can be broken down into more granular LEs (e.g taking a
card from an element and making it a separate LE)
 LEs can be moved, grouped or deleted

5.15

Elements

Creating an LE
1

Select resource(s) to
be part of the LE

4
4. Click to place the LE on
the map
6.15

3. Apply & Close

Elements

41

Unmanaged Elements (UME)


 UME an element of another operator or vendor,
managed by a different managing system
 Extremely useful for:
 Giving a better view of the network structure
 Allowing to handle traffic by trails (and not XC)

 Created in the Physical (Site) layer


 UMEs are not managed by the NMS

7.15

Elements

Creating a UME
1

3
4. Click to place the UME
on the map

8.15

3. Apply & Close


Elements

42

Changing a UMEs Configuration


2

1
Switch to Physical (Site) layer

3,4
3. Change configuration
4. Apply

9.15

Elements

Groups
 Groups allow you to organize the network hierarchically:
 According to Physical location rack, site, city
 According to Technological topology chain, ring

 Can be created in any layer (physical/ technological)


 Members can be added/removed from the group at any
time
 You can also create groups of groups

10.15

Elements

43

Creating a Group
2

1
Select elements to include in
the group

4,5

11.15

Elements

Removing Elements from a Group


1

!
The element is no longer
part of the group

12.15

Elements

44

Adding Elements to a Group


1
Select the elements to
add to the group

3. Select the group that is


being added to
4. Apply

!
See that the element is
now part of the group

13.15

Elements

Map Operations

Expand

Expands the members of a specific group


(Available when a group is selected)

Expand in new Expands the members of a specific group in a new window


(Available when a group is selected)
Expand all

Expands the members of all the groups


(Available when at least one group is collapsed)

Collapse

Collapses a specific group


(Available when a member of a group is selected)

Collapse all

Collapses the members of a specific group


(Always available)

14.15

Elements

45

Summary
 Managed Elements(ME)
 Logical Elements(LE)
 Why theyre used
 Mostly used in DWDM and Data

 Unmanaged Elements(UME)
 Creating and deleting
 Editing UMEs

 Groups
 Creating and deleting
 Adding and removing group members
15.15

Elements

46

Working with Topology


Links
NMS LightSoft

Global Services Division


ECI Training Department
1.12

Topology Links

Topology Links
 A topology link represents the physical connection (fiber
or copper) between network elements
 A topology link connects two ports of different objects
(MEs, LEs, and UMEs)
 Traffic trails can only be defined over topology links

2.12

Topology Links

47

Creating a Topology Link


2
1
Select 2 elements to connect

3.12

Topology Links

Create Topology Link Window


1
Select rate

2
Select 2 endpoints
*Only resources that
support the rate
selection are available

3
4.12

Topology Links

48

Create Topology Link Attributes

5.12

Topology Links

Create Topology Link Attributes


Field

Explanation

Technology Layer

Technology layer of the link. Read only according to the port


type

Media Type

Media type of the selected ports: Electrical, Fiber, or Virtual.


(Read only)

Media Subtype

Selection of media subtypes from the list, according to the


media type. You can also enter your own text.

Length (km/mile)

The length of the link in kilometers or miles

Protection

Type of link protection, for example, MS-SPRing, MS,


external protection, or unprotected. If external protection is
used, specify the type.

SRLG (Ducts)

Shared Risk Link Group. Scrollable entry fields allow you to


specify the shared resources for the link.

Ring Name

Name of the ring associated with this link

6.12

Topology Links

49

Create Topology Link Attributes


Field

Explanation

Assigned Cost
(1-1000)

Enter a value for the cost based on your local evaluations of


cost on a nondenominational scale of 1-1000. A low
number indicates a less expensive link..

Quality
(Best 1..5 Worst)

Select the quality of the link, from 1 (best quality) to 5


(worst quality)

Dispersion
(ps*nm/km)

Dispersion rate in ps/nm. User-entered value, not


calculated

Span Loss (dB)

Span loss in decibels. User-entered value, not calculated

Path Trace
Configuration
button

Enables you to set the J0 values of endpoints of a physical


connection
(Opens a new window)

7.12

Topology Links

A Topology Link in LightSoft


 A topology link appears in the physical (site) layer and in
the relevant technology layer

8.12

Topology Links

50

Topology Links Color-Coding


 Color-coding for operational links:





Red
Orange
Yellow
Green

critical or major alarm


minor alarm
warning
clear (no alarms)

 Color-coding for non-operational links:


 Light blue
 Dark blue
 Dark grey
 White

the link is connected and not uploaded


(an intermediate state)
the link is being uploaded
(intermediate, longer state)
the link is disconnected
inconsistent link

9.12

Topology Links

Internal Links
 Internal link A link between two ports of one element
 When an arrow appears next to the ME- it indicates that
an internal link exists in the element

Internal link indication

10.12

Topology Links

51

Viewing Internal Link Details


1

11.12

Topology Links

Summary
 Topology Links
 Between elements
 Internal links

12.12

Topology Links

52

Optical Trails
NMS LightSoft

Global Services Division


ECI Training Department
1.13

Optical Trails

Content





Creating Logical Elements


Creating UMEs for clients
Topology links
Optical Trails

2.13

Optical Trails

53

Optical Links & Trails Hierarchy

Src

TR/CMR/AoC

M
U
X

Optical Links >


Optical Trails >

OPS-1

D
M
U
X

OFA

OTM

OTM

TRP/CMR/AoC

Snk

OPS-1

OMS

OCH
LP

3.13

Optical Trails

DWDM & OTN Trails Hierarchy

4.13

Optical Trails

54

Creating a Logical Element

5.13

Optical Trails

Creating UMEs For Clients


3

6.13

Optical Trails

55

Creating OPS-1 Links

3
2

7.13

Optical Trails

Creating OTM links

8.13

Optical Trails

56

Creating Clients Capacity Links

9.13

Optical Trails

Creating OMS Trails

10.13

Optical Trails

57

Creating OCH Trails

2
3

11.13

Optical Trails

Creating LP Trails

12.13

Optical Trails

58

Content
 Creating Logical Elements
 Creating UMEs for clients
 Topology links
 OPS-1
 OTM

 Optical Trails





OMS
OCH
ODU
LP

13.13

Optical Trails

59

NMS LightSoft
Optical Trails

Global Services Division


ECI Training Department
1.20

Optical Trails

LightSoft Optical Layer Benefits


 LE Enhancements
 GCT to single-card LEs - opens card instead of shelf views or
PM window from Port in tree
 New LE type - Combiners
 Directional LEs & Groups LEs will have four directions, each
a different LE type
 Parent ME properties from LE - From LE Properties window
user can open the ME Properties window

 UME Enhancements
 New types - Transponder, Regenerator

2.20

Optical Trails

60

LightSoft Optical Layer Benefits


 New SDH-like workflow for optical trail acquisition replaces
TCI
 SRLG support - SRLG can be assigned to OMS and OPS_1
links
 Enhanced Availability Table shows used, available and
blocked channels. Details available for selected channel
 Show Ring - enable the user to enter the ring name for all
SDH and OTN layers.
 Add link name - support for virtual links
3.20

Optical Trails

Optical Layer Display


 The Optical Layer simplifies the network by displaying
only optical ports.
 View all of the sites and connections along an optical
link Simple and effective navigation within the network
 View all of the components in each direction of the link
Thorough and complete view of the complete optical link

4.20

Optical Trails

61

Optical Network Creating Process


 On EMS:
 Create NE in EMS
 Make slot assignments
 Configure all internal parameters of optical cards
 On NMS (optical layer)
 Create and configure LEs for all relevant components
(optional)
 Create and configure relevant UMEs ( OTN)
 Create OTM links
 Create OPS_1 Links
 Create client Links ( SDH, GbE, DSR)
 Discover Optical Trails
5.20

Optical Trails

Create Optical Layer LEs


 LEs can be created manually or automatically

6.20

Optical Trails

62

Creating and Configuring Optical UME


 Select UME type in OTN and configure accordingly

7.20

Optical Trails

Create Optical Topology Link

8.20

Optical Trails

63

Types of Topology Link


 Self Link - a link between two ports housed on the same
Optical Element
 Topology Link - a link between two ports housed on
different Optical Elements
 OTM (Optical Terminal Multiplexer) links
 A link that could contain several channels connected to an
optical MUX/DEMUX

 OPS_1- topology physical connection for one channel


(SIO/TRP/CMBR)

9.20

Optical Trails

Simple Optical Link Characteristics

Src

SIO/TRP

SIO/TRP

M
U
X

OPS_1

OFA

OTM

OTM

Snk

D
M
U
X

OPS_1

OMS

OCH
LP

10.20

Optical Trails

64

When Creating Optical Trails


 Terminology
 OTM - topology physical connection (link) that contains more
than 1 channel (OFA, MUX/DEMUX, SV, OADM)
 OMS_OTN - logical trail of the OTM link (like an optical Server
Trail)
 OPS_1 - topology physical connection (link) for 1 channel (TRP)
 OCH_OTN - logical trail of the OCH link (1 optical channel from
end-to-end)
 LP_SDH - logical trail from UME or SDH connected to client
side of the TRP
 LP_GbE - logical trail from UME (defined as GbE PORTS)
connected to client side of the TRP

11.20

Optical Trails

When Creating Optical Trails


 Note
 Optical Trails are bidirectional
 Optical trails are created from Topology Links using the
Discover Optical Trails function

12.20

Optical Trails

65

Show discovered optical trail


 Optical Trails Discovery on selected resources
 Optical Trails of all Rates will be created on selected
links:





OMS
OCH
LP
High Order ( VC-4 or EoS)

 Discovered Optical Trails are bidirectional

13.20

Optical Trails

Show Discovered Optical Trail

14.20

Optical Trails

66

Optical Trails after Discovery

15.20

Optical Trails

Predefined Filter Data over WDM

16.20

Optical Trails

67

Wavelength Utilization Tables


 Quickly and effectively view which channels are:
 Free for use
 In-Use
 Blocked from being used

 Utilization can be seen per single or multiple OMS


segments.

17.20

Optical Trails

Wavelength Utilization Table

Select any channel


and view the optical
trail and the service
18.20

Optical Trails

68

Optical Availability Functions

19.20

Optical Trails

Basic Network Configuration


1

TRP1

OADMG

TRP2

M
U
X

D
M
U
X

add

OFA1

OFA2

OFA1
drop
TRP

OFA2

Single card

drop

Node A

2
2

D
M
U
X

TRP1

TRP2

TRP

add

OFA2

Node C

Node B

Single card

add

OFA1

OFA2

drop

Single
card
OADMG

20.20

OFA1

Single
card

M
U
X

TRP2

TRP1

Optical Trails

69

ECI Telecom Ltd.

Global Professional Services

This page is intentionally blank

70

ECI Training Services

TCI -Trail Consistency


Indicator
Light Soft

Global Services Division


ECI Training Department
1.16

TCI in Lightsoft

Content
 EMS NMS Hierarchy
 Inconsistency Types
 NMS info is partial- yellow flag
 EMS info is partial- red flag

 TCI Window
 Tool bar
 Parameters (auto actions)

 Trail Synchronization Window- Color Indication


 Additional Windows

2.16

TCI in Lightsoft

71

EMS NMS Hierarchy

Client
(GUI)

Server
(Database)

EMS
XDM

XDM

EMS
BG

Broad Gate

Other
EMS

Other
transport
equipment

3.16

TCI in Lightsoft

Inconsistencies
Inconsistencies between the LightSoft database and EMS
databases can develop over time for a number of reasons
such as:
 XCs were defined or changed on the EMS or craft
terminal level
 XCs were accidently deleted from the EMS
 Trails were deleted from the NMS while performing
maintenance operations

4.16

TCI in Lightsoft

72

Inconsistency Types
Red flag

Yellow flag

Network (EMS)
info is:
Database (NMS)
info is:
Completing the
partial info is:

Partial

Full

Full

Partial

Traffic affecting

Non traffic affecting

Required mode:

Master

Monitor

Two types of inconsistencies depending on where the


information is partial- EMS or NMS
5.16

TCI in Lightsoft

TCI Counters

The TCI counter in the NMS main window toolbar shows:


 Number of inconsistencies in all trails
OR
 Number of inconsistencies in SDH trails only

 Clicking the counter icon swaps between total and SDH


 The color of the flag indicates the type of the worst
inconsistency
 No inconsistency
6.16

TCI in Lightsoft

73

TCI Window
To open TCI window click the Trail Consistency icon

Tool bar

Parameters

7.16

TCI in Lightsoft

TCI Window Tool Bar


Start Process
Stop Process- The operation continues on the trails
processed up to that point
Abort- The entire operation stops at once and no results
are provided
Show Selected Objects- Opens Selected Trails pane that
lists the trails selected when the TCI window was
opened
Close Show Selected Objects- closes the pane

8.16

TCI in Lightsoft

74

Inconsistency Types
When a trail exists in one window but not in the other:
 If the network trail is missing, the DB trail should be
imposed on the network (network = EMS DB)
 If the DB trail is missing, the network trail should be
admitted to the DB (DB = NMS DB)

9.16

TCI in Lightsoft

TCI Window - Parameters

Monitor mode:
 Monitor modeactions only on the DB are
available
 Master modeactions on the Network are
available too

Use connectivity only:


 Process the XCs to trails
according to the links found
in the network
 Process the XCs to trails
according to NMSs trail ID

Dropdown list:
Choose level of TCI to
process
10.16

Recommended to check
TCI in Lightsoft

75

TCI Window - Parameters

Auto impose to network:


 Classified- automatically
impose P2P trails from
Database to Network

Auto admit to database:


 Classified- automatically
admit P2P trails from
the Network to the
Database
 Flex- automatically admit
Flex trails from the
Network to the Database
11.16

TCI in Lightsoft

Trail Synchronization Window- Colors


 Trails in the DB window may have counterparts in the
network window that are:
 Exactly matching
 Partially matching
 Overlapping

 When you select a trail in one window the


corresponding trail in the other window is highlighted
with a color that indicates the relation between the trails
 Different treatment is required according to the condition
implied by the color
12.16

TCI in Lightsoft

76

Trail Synchronization Window- Colors


Green

Corresponding
in Grey
Yellow

Blue

13.16

TCI in Lightsoft

Trail Synchronization Window- Colors


Green

Yellow

Blue

Condition

MatchingThe DB and
Network trails
are exactly
equivalent

Partially
MatchingThe DB trail has
more XCs than
the Network trail

Overlapping1. Some of the XCs are


configured differently in the
DB and the Network
OR
2. The Network trail has
more XCs than the DB trail

Action
needed

none

Impose DB trail
to the Network

1. The user must determine


which version of
the trail is preferred
2. Admit Network trail to the
DB

14.16

TCI in Lightsoft

77

Additional Windows
 Queue WindowDisplays the selected trail (admitted or imposed)
After activating displays the action status (success or
failure)
 Imposed and Admitted Trails WindowsDisplays the trails that were automatically
admitted/imposed
 Event List WindowDisplays information about problems that may occur in
the synchronization process
15.16

TCI in Lightsoft

Summary






EMS NMS Hierarchy


Inconsistency Types
TCI icon & window
Trail Synchronization Window- Color Indication
Additional Windows

16.16

TCI in Lightsoft

78

TR10_4 Configuration
Apollo

Global Services Division


ECI Training Department
1.16

TR10_4 Configuration

TR10_4 Card Configuration


2
1

2.16

TR10_4 Configuration

79

TR10_4 Port Configuration


Manual
Client > Line
Y - Protection

OTU2/2e

(0)Client -> Line (1)


(2)Client -> Line (3)
Configuration

3.16

Y-Protection
(0)Client -> Line (1 + 2)
Configuration

TR10_4 Configuration

TR10_4 Ports Configuration

4.16

TR10_4 Configuration

80

Verifying Port Properties

3
2

5.16

TR10_4 Configuration

Y Protection
 Only the first Client port - 0 can be in Y Protection

6.16

TR10_4 Configuration

81

IOP Protection Configuration


 IOP protection group:
 U5 & U7

 Choose one of the cards from the IOP Group:


 IOP protection configuration is done via the ports

7.16

TR10_4 Configuration

IOP Protection Configuration


 Right click on the client port
 Note: Client ports belonging to the same IOP Protection Group
must be configured similarly with the same parameters!

1
2

3
8.16

TR10_4 Configuration

82

Deleting IOP Protection


 Each port is deleted separately Only via the main port

9.16

TR10_4 Configuration

FEC & EFEC Configuration


 From the optical port, move to the OTU Attributes:

 Scroll down:

10.16

TR10_4 Configuration

83

FEC & EFEC Configuration


 FEC & EFEC

 FEC is supported between Apollo and XDM


 EFEC is not supported between Apollo and XDM
 SD-FEC Soft Decision FEC
For Testing of 100Gb Rate

 FEC Ignore Disable = RX (receiver side) expects to get


FEC or EFEC from the other side
 FEC Ignore Enable = RX (receiver) doesnt expect FEC
or EFEC from the other side
11.16

TR10_4 Configuration

GCC Mode
 From the optical port, move to the OTU Attributes:

2
12.16

TR10_4 Configuration

84

Loopbacks
 Client & Line ports supports Remote or Local loopbacks
 Remote = Facility (Far End)
 Local = Terminal (Near End)

13.16

TR10_4 Configuration

Port Performance Monitoring


1

14.16

TR10_4 Configuration

85

Port Alarms

3
2

15.16

TR10_4 Configuration

TR10_4 Optical Parameters

16.16

TR10_4 Configuration

86

TR100 Configuration
Apollo V4.1

Global Services Division


ECI Training Department
1.20

TR100 Configuration

Content
 Assignment
 Modes: Transponder, Regenerator & IOP Protection
 Line (LFF) Port Configuration
 Client (CFP) Port Configuration
 IOP Protection Configuration

2.20

TR100 Configuration

87

Configuration of TR100
 Slot Assignment
 actual & expected type of the card is TR100

 Two modes are supported: Transponder & Regenerator

3.20

TR100 Configuration

Assignment Rules for OPT9624


 Transponder mode:
 0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22

 Pair slots for the Regenerator:


 0&2; 4&6; 12&14; 16&18; 20&22
 Exception:
regenerator mode, cannot

be assigned in slots 8 and 10

 Pair slots for IOP Protection:


 0&2; 4&6; 8&10; 12&14;
 16&18; 20&22

4.20

TR100 Configuration

88

Assignment Rules for OPT9608/03


 OPT9608
 Transponder mode:
 0, 2, 4, 6

 Pair slots for IOP Protection:


 0&2; 4&6

 Regenerator mode is not supported in OPT9608


 OPT9603
 Transponder mode:
 0

5.20

TR100 Configuration

Line (LFF) Port Configuration


 Line - OTU4
 Line needs wavelength definition:

2
3

6.20

TR100 Configuration

89

Line (LFF) Port Configuration


 Loopback of LINE side
 From the Line Port:
Remote

Client

100GbE
CFP

Line

Remote

OTU4
LFF

Local

7.20

TR100 Configuration

Line (LFF) Port Configuration


 Laser Attributes

8.20

TR100 Configuration

90

Line (LFF) Port Configuration


 Basic & TTI Attributes

 Basic Attributes:

 TTI Attributes:

9.20

TR100 Configuration

Line (LFF) Port Configuration


 FEC Attributes:

 GCC Attributes:

 CD Attributes:

10.20

TR100 Configuration

91

Line (LFF) Port Configuration


 Optical & ONCP Parameters

 Optical Parameters:

 ONCP Parameters:

11.20

TR100 Configuration

Client (CFP) Port Configuration


 Three types of CFP client ports:
 OTR100_SR10
 OTR100_LR10
 OTR100_LR4

 All types support 100GbE

12.20

TR100 Configuration

92

Client (CFP) Port Configuration


 Basic Info:

 Laser Info:

13.20

TR100 Configuration

Client (CFP) Port Configuration


 Maintenance Operation:
 Loopback

 Test Mode

14.20

TR100 Configuration

93

Client (CFP) Port Configuration


 Laser Attributes

15.20

TR100 Configuration

Client (CFP) Port Configuration


 CSF/TSF Action Type:

 LF/RF Mode:

 PCS Status:

16.20

TR100 Configuration

94

IOP Protection Configuration


 Example of two TR100 Cards
 Slots U20 & U22

 Choose left-handed card from the IOP Group:


 U20

 IOP Protection configuration done via the Client port

17.20

TR100 Configuration

IOP Protection Configuration


 Right click on the client port
 Note: Client ports belonging to the same IOP Protection Group
must be configured similarly with the same parameters!

18.20

TR100 Configuration

95

Deleting IOP Protection


 Deleting only via the main port:

19.20

TR100 Configuration

Summary
 Assignment
 Modes: Transponder, Regenerator & IOP Protection
 Line (LFF) Port Configuration
 Client (CFP) Port Configuration
 IOP Protection Configuration

20.20

TR100 Configuration

96

CMR40
Configuration
Apollo

Global Services Division


ECI Training Department
1/16

CMR40 Configuration

Content
 CMR40 Configuration via STMS
 Base card configuration
 Port configurations
Client ports
Fixed line port

 Alarms
 PM
 Maintenance

2/16

CMR40 Configuration

97

CMR40 Configuration
1

3/16

CMR40 Configuration

Ports Configuration
1

4/16

CMR40 Configuration

98

Ports Configuration
4

5/16

CMR40 Configuration

Ports Configuration

6/16

CMR40 Configuration

99

Performance Monitoring
1

7/16

CMR40 Configuration

Alarms
1
3

8/16

CMR40 Configuration

100

Temperature

9/16

CMR40 Configuration

Client Port Properties


1

10/16

CMR40 Configuration

101

Client Port Properties Main

11/16

CMR40 Configuration

Client Port Properties Transceiver

12/16

CMR40 Configuration

102

Client Port Properties ETY Attributes

13/16

CMR40 Configuration

Line Port Properties Main

14/16

CMR40 Configuration

103

Line Port Properties OTU Attributes

15/16

CMR40 Configuration

Line Port Properties


 Optical Parameters

16/16

CMR40 Configuration

104

AoC10 Card
Configuration
Apollo

Global Services Division


ECI Training Department
1.22

AOC10 Configuration

Content
 Slot assignment
 Card status verification
 Port configuration
 Fiber connectivity
 Maintenance

2.22

AOC10 Configuration

105

Slot Assignment
 The element is empty and therefore the slot assignment
begins

3.22

AOC10 Configuration

View after Assignment


 Two AoC cards
 Two ROADMs

 Two amplifiers

OA-PA
ROADM

AoC

OA-PA

ROADM

AoC
4.22

AOC10 Configuration

106

Card Status Verification


 Following assignment all cards should be working
 Right Click on Apollo shelf >> Element Status

5.22

AOC10 Configuration

Port Configuration
 Right click on the card

6.22

AOC10 Configuration

107

AoC Port Configuration

7.22

AOC10 Configuration

Fiber Connectivity
 Right click on the Apollo shelves >> Show Fiber
Connectivities

8.22

AOC10 Configuration

108

Create Fiber Connectivity


 Click on the Create button on the bottom right side:

9.22

AOC10 Configuration

Fiber Connectivity
Fiber connectivity = Internal

When connecting between cards in the same


Apollo

Fiber connectivity = External

When connecting between elements

10.22

AOC10 Configuration

109

Fiber Connectivity Verification


 Clockwise - CW

11.22

AOC10 Configuration

Fiber Connectivity Verification


 Counter clockwise - CCW

12.22

AOC10 Configuration

110

Edit Fiber Connectivity


 Fiber connectivity can be edited when required

13.22

AOC10 Configuration

Remote and Local Loopbacks


 Remote and Local loopbacks are supported on any
client/line port
Remote loopback

Signal is turned back towards the Line.


The received signal is transmitted to the line and
continues the original path

Local loopback

Signal is turned back towards the Card.


The loopback is transparent and loop-timed

 Each loopback should be loop and continue


 Only one loopback at a time
14.22

AOC10 Configuration

111

Remote and Local Loopbacks


 Remote Loopback - Signal is turned back towards the
line
 received signal is transmitted to the line and continues along the
original path

 Local Loopback - Signal is turned back towards the


card

15.22

AOC10 Configuration

AoC ALS
 Disconnect on the Receiver (Rx) side shuts down the
laser toward the Transmit (Tx) side

16.22

AOC10 Configuration

112

ALS Configuration
 From the card, choose the required port:

 From the Main button scroll down till Laser Info:

17.22

AOC10 Configuration

AoC CSF
 CSF Client Signal Failure

18.22

AOC10 Configuration

113

AoC TSF
 TSF Traffic Signal Failure

19.22

AOC10 Configuration

AoC Drop and Continue

20.22

AOC10 Configuration

114

AoC East / West Protection

21.22

AOC10 Configuration

AoC Full Client Protection

22.22

AOC10 Configuration

115

ECI Telecom Ltd.

Global Professional Services

This page is intentionally blank

116

ECI Training Services

CMR100 Configuration
Apollo

Global Services Division


ECI Training Department
1.41

Interfaces & Protocols

Content
 CMR100 assignment
 Assignment rules for OPT9624/08/03
 Line (LFF) port configuration
 Client port configuration
 IOP protection configuration

2.41

Interfaces & Protocols

117

CMR100 Configuration via STMS


 Slot Assignment
 Actual & Expected type of the card is CMR100

3.41

Interfaces & Protocols

Assignment Rules for OPT9624


 Muxponder Expected Mode:
 0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22

 Paired slots for IOP Protection:


 0&2; 4&6; 8&10; 12&14;
 16&18; 20&22

4.41

Interfaces & Protocols

118

Assignment Rules for OPT9608/03


 OPT9608
 Expected Muxponder mode:
 0, 2, 4, 6

 Pair slots for IOP Protection:


 0&2; 4&6

 OPT9603
 Expected Muxponder mode:
 0

5.41

Interfaces & Protocols

Line (LFF) Port Configuration


 Line Transceiver defined by default

 Line Port Port 0


 Client Ports: 1 to 10
6.41

Interfaces & Protocols

119

Line (LFF) Port Configuration


 Tx Wavelength definition:

 From the Main window


 Scroll down to the right bottom corner:

7.41

Interfaces & Protocols

Line (LFF) Port Configuration


 Loopbacks
 Type: Local or Remote

100Gb Remote Client


E
Local
CFP

Line Remote

OTU4
LFF

Loop and Continue

 From the Main window


 Scroll down to the left bottom corner:

8.41

Interfaces & Protocols

120

Line (LFF) Port Configuration


 Laser Info:
 AlS State
Disable (Default)
Enable

 Tx Enable:
Enable (Default)
Disable

9.41

Interfaces & Protocols

Line (LFF) Port Configuration


 Transceiver Laser Attributes:

10.41

Interfaces & Protocols

121

Line (LFF) Port Configuration


 OTU Attributes:

 Basic Attributes:

 TTI Attributes:

11.41

Interfaces & Protocols

Line (LFF) Port Configuration


 OTU Attributes
 FEC Attributes: FEC Ignore Disable (By Default)

 GCC Attributes: GCC Termination Disable (By Default)

 CD Attributes:
12.41

Interfaces & Protocols

122

Line (LFF) Port Configuration


 Optical Parameters

 Input & Output Parameters

 Refresh in:
 Default 1 min
13.41

Interfaces & Protocols

Line (LFF) Port Configuration


 At the end, return to the Main window
and click on Apply

14.41

Interfaces & Protocols

123

Client Port Configuration


 First Option: Example with ETY100GOC

1


Example with OTU2e

15.41

Interfaces & Protocols

Client Port Configuration


 Second Option:

 Scroll down toward the bottom right corner:

 If transceiver type is color:

16.41

Interfaces & Protocols

124

Client Port Configuration


 Port Basic Info

 Operational Info, Alarm Master Mask & PM Monitor


 Actual Tx Status: Must be On

17.41

Interfaces & Protocols

Client Port Configuration


 Laser Info
 ALS State Disable by Default
 Tx Enable Enable by Default

 Maintenance Info
 Loopback: Local or Remote (Default No Loopback)
Loop and Continue

18.41

Interfaces & Protocols

125

Client Port Configuration


 Transceiver Laser Attributes:

19.41

Interfaces & Protocols

Client Port Configuration


 OTU Attributes

 Basic Attributes:

 TTI Attributes:

20.41

Interfaces & Protocols

126

Client Port Configuration


 OTU Attributes
 FEC Attributes: FEC Ignore Disable (By Default)

 GCC Attributes: GCC Termination Disable (By Default)

 CD Attributes:

21.41

Interfaces & Protocols

Client Port Configuration


 Optical Parameters

 Input & Output Parameters

 Refresh in:
 Default 1 min
22.41

Interfaces & Protocols

127

Client Port Configuration


 At the end, back to the Main window
and perform Apply

23.41

Interfaces & Protocols

IOP Protection Configuration


 The characteristics of IOP protection scheme are:
 1+1
 Non-Revertive or Revertive
 Uni-directional
 Each port will switch independently

24.41

Interfaces & Protocols

128

IOP Protection Configuration


 Example of two CMR100 Cards

 Choose left-handed card from


the IOP Group:
 U20

 IOP Protection configuration done


via the Client port
25.41

Interfaces & Protocols

IOP Protection Configuration


 Right click on the client port
 Note: Client ports belonging to the same IOP Protection Group,
must be configured similarly with the same parameters!

 Port 1 in the both cards defined same: OTU2e


 Port 2 in the both cards defined same: STM64
 Port 3 in the both cards defined same: FC1200

26.41

Interfaces & Protocols

129

IOP Protection Configuration


 Note: Fiber Connectivity must be done before IOP
Protection

27.41

Interfaces & Protocols

Deleting IOP Protection


 Deleting only via the main port:

28.41

Interfaces & Protocols

130

Theory of
ASON Technology
Apollo

Global Services Division


ECI Training Department
1.26

ASON Technology

Content
 ASON overview & general description
 GMPLS overview & working mode
 ASON framework
 Control plane basic functions
 ASON protection & restoration
 ASON recovery types
2.26

ASON Technology

131

ASON Overview
 ASON Automatically Switched Optical Network
 ASON functionality creates a network of NEs that
recognize one another
 If traffic fails somewhere in the network, a protection
path is automatically found to reroute the traffic
 When the main path is repaired, the traffic is
automatically reverted back by the system
 The restoration path resources are released

3.26

ASON Technology

ASON Overview
 Suitable for sub lambda services and low capacity trails
 Less complicated (no need to consider optical
impairments)
 Signal is terminated in each ODU-XC
 Restoration is based on (SD) PM
 Restoration modes could be recovered in second and
less
4.26

ASON Technology

132

ASON General Description


 ASON uses a control plane & restoration based on
GMPLS at the ODU_XC level
 Enables automatic delivery, protection and restoration of
transport ODUk services:
 ODUk: ODU0, ODU1, ODU2

 Supported by Apollo OPT9624-H


 Available only when the automatic package optional
feature is enabled

5.26

ASON Technology

GMPLS Overview
 GMPLS - Generalized Multi-Protocol Label Switching
 GMPLS Protocol:
 Supports and manages multiple types of switching technologies
other than packet interfaces & switching
 Technologies such as TDM & L2 switching - Wavelength &
Fiber (port) switch
 Enables ODUk and Lambda service provisioning
 Multiple protection and restoration options

6.26

ASON Technology

133

How does GMPLS Work?


 Based on generalized labels
 Composed of three main protocols:
 Signaling protocol - Resource Reservation Protocol with
Traffic Engineering extensions (RSVP-TE)
 Routing protocol - Open Shortest Path First with Traffic
Engineering extensions (OSPF-TE)
 Link Management Protocol (LMP)

7.26

ASON Technology

ASON Framework ITU-T G.8080


 Architecture for the automatically switched optical
network

Management Plane

I-NNI

8.26

Control Plane
E-NNI

MNI

UNI

CCI

Transport Plane
Interfaces
UNI: User-Network Interface
NNI: Network-Network Interface
MNI: Management-Node Interface
CCI: Connection Control Interface -between the control plane and the transport ASON
plane
Technology

134

ASON Framework ITU-T G.8080


 Management Plane
 The plane that controls and monitors the data plane
(Operations, Administration, Maintenance and provisioning)

 Control Plane
 Middle plane that enables intelligent optical networking - adds
dynamic monitoring & control
 Consists of individual processors (control plane instances)
within each Apollo NE
 A dedicated MNI is used between the control plane and
NMS (Management Plane)

 Transport Plane
 Responsible for transporting services between endpoints using
the switching equipment
9.26

ASON Technology

Control Plane Basic Functions


 Network Auto Discovery ( using OSPF)
 Mechanisms for Neighbor Discovery & Topology Discovery
 Cards, intra-node connectivity

 Routing/Topology Advertisement using OSPF


 Topology flooding information
 Network topology discovery
 Route computation

 Connection Management Signaling using GMPLS +


RSVP-TE
 Automated provisioning and failure recovery
 Automatic add and remove connections

10.26

ASON Technology

135

Network Auto Discovery


 Neighbor Discovery Each node builds a network

topology using the neighbor discovery function


 Topology Discovery by NMS Builds the topology using:
 Topology Maps
 Consistency Check

 Auto Discovery includes discovery of:


remote network element and remote port of the OTUk link

11.26

ASON Technology

Routing/Topology using OSPF


 Routing OSPF TE :
 Responsible for automatic network topology discovery
 Automatic resource discovery
 Automatic route computation
 Maintains a local topology database on each control plane
instance
LightSoft

OSPF

12.26

ASON Technology

136

Connection Signaling using RSVP


 Provides the underlying mechanism for dynamic call
and connection management
 Handles connection requests, such as:
 Connection creation or restoration

 RSVP TE - Resource Reservation Protocol


 Transport Layer protocol designed to reserve resources across
a network for an integrated services

13.26

ASON Technology

Service Provisioning
 GMPLS RSVP-TE path
LightSoft

OSPF

PATH

PATH

Discovery
14.26

Routing

Signaling
ASON Technology

137

Protection against Failures


 ASON protects a network against:
 Multiple data-link failures
 Equipment failure associated directly with the data-link
 ODU failures when trails are SNCP protected

15.26

ASON Technology

ASON Protection & Restoration


 ASON enables automatic protection and restoration of
transport ODUk services:
 Protection

Executed by the two end NEs


Capacity is configured across the network and NEs
No sharing backup resources
Less than 50msec protection switching time

 Restoration
No pre-allocated capacity
Network automatically calculates a new route based on available
resources
Services with low priority can be used on the capacity used for
restoration
Performed in more than 50msec
16.26

ASON Technology

138

Restoration Benefits
 Restoration increases the capacity in the network
 Increases network reliability by providing recovery for
multiple failures
 Providing different quality of service for different
services

17.26

ASON Technology

Example Restoration Modes

1+1
Unprotected
Service

Dynamic
Path restoration

18.26

ASON Technology

139

ASON - Recovery Types


 ASON supports assignment of any of the following
recovery types for any trail:
 SNCP Protected (1+1)
 Restoration Protected (1+R)
 One Time SNCP and Restoration Protected (1+1+R)
 SNCP and Restoration Protected Forever (1++)

19.26

ASON Technology

SNCP Protected (1+1)


 Trail recovers within 50 ms of the first failure
 Trail does not recover if it suffers from an additional
failure
 This is called Current Layer protection in LightSoft
terms

20.26

ASON Technology

140

Restoration Protected (1+R)


 Trail recovers within less than one second for any failure
as long as the route is found from head-end to tail end
 In SDH terms this is an unprotected trail with ASON

21.26

ASON Technology

One Time SNCP & Restoration Protected (1+1+R)


 Trail recovers within less than 50 ms for the first failure
and less than one second for any consequent failure as
long as a route is found from the head-end to the tailend

22.26

ASON Technology

141

1+1+R Protection Scheme

LightSoft

M-Working

P-Restoration

P-Working

50 msec protection guarantee for multiple failures


23.26

ASON Technology

SNCP & Restoration Protected (1++)


 SNCP & Restoration Protected Forever
 Trail recovers within less than 50 ms for any failure as
long as a route is found from the head-end to the tailend

24.26

ASON Technology

142

Apollo ASON Restoration Modes


Service Level

Highest
Protection
Scheme

Protected
Forever

Lowest
Protected and
Restored

Protected

Restoration

Unprotected

Protection
Method

1++

1+1+R

1+1

Dynamic path
Restoration

Non

Protection Time

< 50msec

<50msec
(1st failure)
>50msec 2nd
onwards

< 50msec

1 sec

N/A

Capacity
Consumed

Highest

Higher

Lower

Lowest

Applications

High Priority
Customers

Voice, Voice
mobile, fix
enterprise

Telemetry,
Internal data
network

Cheap and dirty

25.26

ASON Technology

ASON Summary
 ASON Components:





Planes
Interfaces
Protocols
Links

26.26

ASON Technology

143

ECI Telecom Ltd.

Global Professional Services

This page is intentionally blank

144

ECI Training Services

ASON Technology
Implementation
in Apollo
NMS LightSoft & STMS
Global Services Division
ECI Training Department
1.32

Implementing ASON Technology

Content







License for the ASON technology


FIO cards parameters STMS
Creating links NMS
Creating OCH trails NMS
Creating ODU* trails NMS
Creating restoration of the LP NMS
 1+R
 1+1+R
 1++

 Maintenance operations
 Useful CLI commands
2.32

Implementing ASON Technology

145

ASON Configuration
 What do we need to do to build an ASON Network?
 NMS License (V10 and higher) - Level Package 2
 STMS License (V5.1 and higher) - Per Port
 OPT9624H shelves
 FIO cards
 Create a Topology link
 Create OCH Trails (Build ASON Data Link)
 ODU XC * ( depends on the LP Service)
 Create a light path - LP: 1+R; 1+1+R; 1++
3.32

Implementing ASON Technology

ASON License in NMS & STMS


 To be able to implement ASON check the licenses in:
 NMS Level Package 2

STMS per port

STMS
NMS

4.32

Implementing ASON Technology

146

STMS

5.32

Implementing ASON Technology

Shelf Mode with FM1000-Fabric


 Today only OPT9624H shelf support ASON Technology
 For FIO cards assignment this configuration mode must
be done:
 Go to the Properties of the shelf

 And check Shelf Mode:

6.32

Implementing ASON Technology

147

Control Plane Attributes


 From the properties of the shelf go to the
 Control Plane Attrs (Attributes)

 ASTN Type should be:


 ASON

7.32

Implementing ASON Technology

ASTN Parameters on the FIO Module


 Open the FIO card and choose the proper port

 Right click on the port and go to the Properties:

 Go to the ASTN Parameters and define:


 Network Interface type:
NNI

8.32

Implementing ASON Technology

148

NMS

9.32

Implementing ASON Technology

Creating Links in the Optical Layer


 Supports all types of FIO & Photonic (DWDM) cards
 The ASON end points should be FIO cards
 FIOMR_16/16B, FIO10_5/10_5B, FIO40, FIO100

 FIO Cards represented by LEs

10.32

Implementing ASON Technology

149

Creating OCH Trails


 Before OCH trail creation:
 Choose rate: OCH
 Protection Types: Unprotected, Current, etc

 Advanced Protection
 Build ASON Data Link

11.32

Implementing ASON Technology

OCH Layer
 After OCH trail creation move to the OCH layer
 If A is White OCH trail is Inconsistent or
Pending
 If A is Yellow OCH trail: Active

12.32

Implementing ASON Technology

150

Checking Link Availability


 Shown on the Optical technology layer and on the OCH
technology layer
 For the ODU trails and the LP

13.32

Implementing ASON Technology

ODU Trails
 ODU trails support the following rates:






ODU1
ODU2
ODU2e
ODU3e
ODU4

14.32

Implementing ASON Technology

151

ODU Trails Some Scenarios


 If the OCH trail is done by FIO100
 The ODU4 Trail is mandatory for the all rates of LP
Except 100GbE LP trail

 If OCH trail is done by FIO10_5B


 The ODU2 Trail cannot be created for STM64 or 10GbE or for
the other LPs that has 10Gb rate

15.32

Implementing ASON Technology

NMS supports the following


OTN ASON restoration schemes:
1+R, 1+1+R, 1++

16.32

Implementing ASON Technology

152

LP Trail Creation
 If ASON checkbox is checked, the Protection combo box has the
following list of values:
1+R (Bronze)

1+R (Bronze) & Underlying

1+1+R (Silver)

1+1+R (Silver) & Underlying

1++ (Gold)

1++ (Gold) & Underlying

17.32

Implementing ASON Technology

LP Completion Methods
 Two ways to complete a Light Path
 Auto-complete
 Explicit Selection

18.32

Implementing ASON Technology

153

1+R (Bronze) Restoration


 1+R trail is an ASON trail that has only a Main path and
a P2P topology

19.32

Implementing ASON Technology

1+R (Bronze) Restoration

20.32

Implementing ASON Technology

154

Trail List
 To be able to see the ASON Path State in the Trail List:
 Click on the Configure Columns square
 Click on ASON Path State

21.32

Implementing ASON Technology

1+1+R (Silver) Restoration

22.32

Implementing ASON Technology

155

1+1+R (Silver) Restoration


 1+1+R trail must have Main and Protection paths

23.32

Implementing ASON Technology

1++ (Gold) Restoration


 1++ trails must have Main and Protection paths

24.32

Implementing ASON Technology

156

1++ (Gold) Restoration


 The trail should contain main and protection LSPs
 1++ is a trail with main and protection provisioned paths
that is protected by dynamic restoration

25.32

Implementing ASON Technology

1++ (Gold) Restoration

Purple line shows the Main - blue outline


shows where the actual traffic is

Current traffic

Main
Protection

Light blue line


shows the protection

26.32

Implementing ASON Technology

157

1++ (Gold) Restoration

Purple line shows the Main - blue line in the


middle shows where the actual traffic is

Main

Protection

Current traffic

Light blue line


shows the protection

27.32

Implementing ASON Technology

Showing the Highlighted Trail


 This icon shows us where the active route (active traffic)
is run

28.32

Implementing ASON Technology

158

ASON Trail Maintenance Operations









Revert Manual Main Path


Revert Manual Protection Path
Revert Force Main Path
Revert Force Protection Path
Reroute Manual Main Path
Reroute Manual Protection Path

29.32

Implementing ASON Technology

ASON Trail Export & Import


 All ASON trail features that are supported from the GUI
can be supported through XML files
 ASON trails can be exported to CSV files

30.32

Implementing ASON Technology

159

Alarms, Current PM, PMH


 The list of alarms and probable cause events:
 Restoration Attempt Timeout
 Restoration Admission Control Failure
 Restoration Failure No Route Found
 Faulty Trail
 Trail Degraded
 Restoration event
 Reversion event

31.32

Implementing ASON Technology

Useful CLI Commands


 To check the ASON alarms & status via CLI:
 root@AsonNE1xx# run show mpls interface detail
 root@AsonNE1xx# run show chassis alarms
 root@AsonNE1xx# show trails
 root@AsonNE1xx# show cross-connects
 root@AsonNE1xx# run show protection traffic

32.32

Implementing ASON Technology

160

LP DNI Configuration
NMS LightSoft

Global Services Division


ECI Training Department
1/14

DNI LP Configuration

Content







Topology
Protection Scheme
Prerequisite
DNI LP Trail Configuration
DNI Cross-Connects in STMS
DNI Cross-Connects CLI

2/14

DNI LP Configuration

161

Topology

Apollo-85

Apollo-86

FIO10_5

MUX

FIO10_5

FIO10_5

MUX

MUX

MUX

TR10_4

MUX

Apollo-87

TR10_4

FIO10_5

MUX

MUX

Apollo-88

MUX

Apollo-89

3/14

DNI LP Configuration

Protection Scheme

Apollo-89

Apollo-88

Apollo-85

Apollo-86

Apollo-87

Main
Protection
DNI Bridge

4/14

DNI LP Configuration

162

Prerequisites
1. Slot assignment and ports configuration
2. Topology links
3. OMS and OCH trails

5/14

DNI LP Configuration

Topology in LightSoft

6/14

DNI LP Configuration

163

DNI LP (LightPath) Trail


 Open Create Trail window
 Select the endpoints of the LP trail (In this example:
STM64 port on C1 port of TR10_4 on both sides)

7/14

DNI LP Configuration

DNI LP Trail

Select the protection


mode

Check the DNI box

8/14

DNI LP Configuration

164

DNI LP Trail
 Open the Trail list window
 Select the previously configured LP trail

Number of DNI nodes


within the trail

9/14

DNI LP Configuration

DNI Cross-Connects
 Right click on FIO(DNI node) and select Cross
Connection

10/14

DNI LP Configuration

165

DNI Cross-Connects in STMS


Previously configured LP
trail, on STMS crossconnection window

DNI cross-connects
11/14

DNI LP Configuration

DNI Cross-Connects in STMS

FIO10_5

FIO10_5

FIO10_5

FIO10_5
2
12/14

DNI LP Configuration

166

DNI Cross-Connects in CLI


1
1

FIO10_5

FIO10_5

4
8

FIO10_5

FIO10_5

2
8

13/14

DNI LP Configuration

Summary







Topology
Protection Scheme
Prerequisite
DNI LP Trail Configuration
DNI Cross-Connects in STMS
DNI Cross-Connects CLI

14/14

DNI LP Configuration

167

ECI Telecom Ltd.

Global Professional Services

This page is intentionally blank

168

ECI Training Services

LP DRI Configuration
NMS LightSoft

Global Services Division


ECI Training Department
1/12

DRI LP Configuration

Content





Topology
Protection Scheme
Prerequisite
DRI LP Trail Configuration

2/12

DRI LP Configuration

169

Topology
Apollo-87
FIO10_5

FIO10_5

FIO10_5

Apollo-85

Apollo-86

TR10_4

TR10_4

FIO10_5

Apollo-89

FIO10_5

FIO10_5

FIO10_5

FIO10_5

3/12

DRI LP Configuration

Protection Scheme
Apollo-87

Apollo-86

Apollo-89

Apollo-85

Main
Protection
DRI Bridge
4/12

DRI LP Configuration

170

Prerequisites
1. Slot assignment and ports configuration
2. Topology links
3. OMS and OCH trails

5/12

DRI LP Configuration

Topology in LightSoft

6/12

DRI LP Configuration

171

DRI LP (LightPath) Trail


 Open Create trail window
 Select the endpoints of the LP trail (In this example:
STM64 port on C1 port of TR10_4 on both sides)

7/12

DRI LP Configuration

DRI LP Trail

Select the protection


mode

Select maximum
number of DRI
bridges (up to 16)
Check the DRI box
8/12

DRI LP Configuration

172

DRI LP Trail
 Open the Trail list window
 Select the previously configured LP trail

Number of DRI bridges


within the trail

9/12

DRI LP Configuration

DRI LP Trail

Resource Tree

Bridge 1 - Main

Bridge 1 - Protection

10/12

DRI LP Configuration

173

DRI LP Trail
Apollo-87
FIO10_5

FIO10_5

FIO10_5

3
4

FIO10_5

1
2

1 4

3 2
Apollo-85

FIO10_5

FIO10_5

FIO10_5

FIO10_5

11/12

DRI LP Configuration

Summary





Topology
Protection Scheme
Prerequisite
DRI LP Trail Configuration

12/12

DRI LP Configuration

174

You might also like