1350 Oms SDH R 9.1.1 MNT4 - Top63052 - V1.0

1350OMS
1350OMS-SDH R 9.1.1 MNT4

Operation
TOP63052R.9.1.1MNT4-SG1-SEN-I2.0 Issue 1.00
STUDENT GUIDE
All Rights Reserved © Alcatel-Lucent @@YEAR
All rights reserved © Alcatel-Lucent @@YEAR

Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent

1350OMS-SDH R 9.1.1 MNT4 Operation - Page 1
Empty page
Switch to notes view!
2 All Rights Reserved © Alcatel-Lucent @@YEAR

1350OMS
1350OMS-SDH R 9.1.1 MNT4 Operation
This page is left blank intentionally

Terms of Use and Legal Notices
1. Safetyto
Switch Warning
notes view!
Both lethal and dangerous voltages may be present within the products used herein. The user is strongly advised not to
wear conductive jewelry while working on the products. Always observe all safety precautions and do not work on the
equipment alone.
The equipment used during this course may be electrostatic sensitive. Please observe correct anti-static precautions.
2. Trade Marks
Alcatel-Lucent and MainStreet are trademarks of Alcatel-Lucent.
All other trademarks, service marks and logos (“Marks”) are the property of their respective holders, including Alcatel-
Lucent. Users are not permitted to use these Marks without the prior consent of Alcatel-Lucent or such third party owning
the Mark. The absence of a Mark identifier is not a representation that a particular product or service name is not a Mark.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented herein, which may be subject to
change without notice.
3. Copyright
This document contains information that is proprietary to Alcatel-Lucent and may be used for training purposes only. No
other use or transmission of all or any part of this document is permitted without Alcatel-Lucent’s written permission, and
must include all copyright and other proprietary notices. No other use or transmission of all or any part of its contents may
be used, copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from
Alcatel-Lucent.
Use or transmission of all or any part of this document in violation of any applicable legislation is hereby expressly
prohibited.
User obtains no rights in the information or in any product, process, technology or trademark which it includes or
describes, and is expressly prohibited from modifying the information or creating derivative works without the express
3written consent of Alcatel-Lucent. All Rights Reserved © Alcatel-Lucent @@YEAR
1350OMS
4. Disclaimer
In no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential damages, including
lost profits, lost business or lost data, resulting from the use of or reliance upon the information, whether or not Alcatel-
Lucent has been advised of the possibility of such damages.
Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes neither an
endorsement, nor a recommendation.
This course is intended to train the student about the overall look, feel, and use of Alcatel-Lucent products. The
information contained herein is representational only. In the interest of file size, simplicity, and compatibility and, in some
cases, due to contractual limitations, certain compromises have been made and therefore some features are not entirely
accurate.
Please refer to technical practices supplied by Alcatel-Lucent for current information concerning Alcatel-Lucent equipment
and its operation, or contact your nearest Alcatel-Lucent representative for more information.
The Alcatel-Lucent products described or used herein are presented for demonstration and training purposes only. Alcatel-
Lucent disclaims any warranties in connection with the products as used and described in the courses or the related
documentation, whether express, implied, or statutory. Alcatel-Lucent specifically disclaims all implied warranties,
including warranties of merchantability, non-infringement and fitness for a particular purpose, or arising from a course of
dealing, usage or trade practice.
Alcatel-Lucent is not responsible for any failures caused by: server errors, misdirected or redirected transmissions, failed
internet connections, interruptions, any computer virus or any other technical defect, whether human or technical in
nature
5. Governing Law
The products, documentation and information contained herein, as well as these Terms of Use and Legal Notices are
governed by the laws of France, excluding its conflict of law rules. If any provision of these Terms of Use and Legal
Notices, or the application thereof to any person or circumstances, is held invalid for any reason, unenforceable including,
but not limited to, the warranty disclaimers and liability limitations, then such provision shall be deemed superseded by a
valid, enforceable provision that matches, as closely as possible, the original provision, and the other provisions of these
Terms of Use and Legal Notices shall remain in full force and effect.

Blank Page

1350OMS

Course Outline
Section
About This1.Course
Product Overview
4. Topic/Section is Positioned Here
Module 1. Product Overview
Course outline
Technical support Operation
Section 2. System 5. Topic/Section is Positioned Here
Course objectives
Module 1. How to log on
Moduleis2.Positioned
1. Topic/Section Network topology
Here 6. Topic/Section is Positioned Here
Xxx Module 3. HO Trail management
Xxx Module 4. Path management 7. Topic/Section is Positioned Here
Xxx
Module 5. SNCP and DC SNCP management
Module 6. 2F-MS-SPRING management
Module 7. Advanced operation
Module 8. Network resources availability
Module 9. Topology modification
Module 10. Batch files
Section 3. Maintenance Applications
Module 1. Troubleshooting tools
Module 2. Alarm Management
Module 3. Performance management
Module 4. Consistency and isolation
5
1350OMS
Section 4. Appendix All Rights Reserved © Alcatel-Lucent @@YEAR

Module 1. Routing Algorithm

Course Outline [cont.]

1350OMS

Course Objectives
Welcome to 1350OMS-SDH R 9.1.1 MNT4 Operation
Upon completion of this course, you should be able to:
manage a network using 1350OMS SDH

1350OMS

Course Objectives [cont.]

1350OMS

About this Student Guide

Conventions
Switch used
to notes in this guide
view!
Note
Provides you with additional information about the topic being discussed.
Although this information is not required knowledge, you might find it useful
or interesting.
Technical Reference
(1) 24.348.98 – Points you to the exact section of Alcatel-Lucent Technical
Practices where you can find more information on the topic being discussed.
Warning
Alerts you to instances where non-compliance could result in equipment
damage or personal injury.
Where you can get further information

1350OMS
If you want further information you can refer to the following:

Technical Practices for the specific product
Technical support page on the Alcatel website: http://www.alcatel-lucent.com

About this Student Guide [cont.]

1350OMS

Self-assessment of Objectives
Contract number :
At the end of each section you will be asked to fill this questionnaire
Course title :
Please, return this sheet to the trainer at the end of the training
Client (Company, Center) :
Language :
Switch to notes view! Dates from : to :
Number of trainees : Location :
Surname, First name :
Did you meet the following objectives ?

Tick the corresponding box
Please, return this sheet to the trainer at the end of the training
Yes (or No (or
Instructional objectives globally globally Comments
yes) no)
1350OMS-SDH overview
• Describe the composition of 1350OMS
• List the purposes of 1350OMS-SDH
• Identify the objects implemented by
1350OMS-SDH to fulfil its purposes
How to logon
• 11Login and start the 1350OMS application All Rights Reserved © Alcatel-Lucent @@YEAR
• 1350OMS
Navigate the Web
Portal
Network topology
• Manage the Sub-Networks
• Create the Physical Connections either
manually or automatically
• Recognize the SDH objects provided by the
Physical Connections
• Create the External Networks
• Manage the Network Protection Architecture
(NPA)
HO-Trail
• Create one-hop HO-Trails by configuring the
payload
• Create one-hop and multi-hop HO-Trails by
means of the relevant wizard
• Manage the HO-Trails
Path
• Set up PDH Paths
• Set up Ethernet Paths and manage their
attributes: routing, LCAS, bandwidth, flow
control
• Set up DVB Paths
• Set up ATM Paths
• Create Paths between a real NE and an
External Network
SNCP and D&C SNCP
• Set up and manage SNCP protection
• Move to the spare way the HO traffic of a
Physical Connection
• Set up and manage D&C SNCP protection

Self-assessment of Objectives [cont.]
Yes (or No (or
Instructional objectives Globally globally Comments
Switch to notes view! yes) no)
2F MS-SPRing
• Understand the 2F MS-SPRing behaviour
• Analyse the protection status
• Apply user commands
Advanced operation
• Manage Path and HO-Trail Constraints
• Disable/Enable the Node Download status
• Reroute Path and HO-Trail
• Add/Remove legs for broadcast Path
• Upload the Paths/Trails from the NEs
• Set up and manage X and Y Paths
Network resources availability
• retrieve the information about the resources
available/not available for creating Paths and
Trails
Topology modification
• Remove/add a Node from/to the network by
applying the join/split procedures
• Replace a Node in the network by applying
the “move port” procedure
• Get the Map more consistent with the
deployed network in case of External
Networks
• Manage the Planned Ports
Batch files
1350OMS
• 1350OMS-SDH
operateR the Batch
9.1.1 MNT4 Files that may be used to
Operation
modify the 1350OMS-SDH objects

Troubleshooting tools
• Locate a faulty network section by means of
loopbacks
• Forward a traffic to test ports connected to
an external instrument for monitoring
purposes
Alarms
• Localize and analyse a network fault
• Configure the framed/unframed/PRA modes
on 2Mb/s paths
• Use the Path Overhead Monitoring (POM)
• Manage the Trace Identifier for Path, HO-
Trail, Physical Connection
Performance Monitoring
• Start and stop Performance Monitoring
• Display the PM results
• Export PM information
• Compare the NML’s PM DB with the EML’s PM DB
Consistency and isolation
• check and fix the misalignment between the
1350OMS-SDH’s DB and the NE’s MIB
• operate the network in case of communication
problems between the NEs and 1350OMS
Routing algorithm
• Be aware on how the 1350OMS-SDH selects the
route for a Path/Trail
Other comments

Thank you for your answers to this questionnaire

Do not delete this graphic elements in here:
@@SECTI
Section 1
Product Overview
Module 1
Product Overview
3JK Issue 03
1350OMS

3JK Issue 03
Section 1 Module 1 Page 1
Blank Page

Product Overview Product Overview
1350OMS 1350OMS-SDH R 9.1.1 MNT4 Operation
Document History
Edition Date Author Remarks
01 2011-04-29 Pirola Paolo

3JK Issue 03
Module Objectives
Upon completion of this module, you should be able to:
Describe the composition of 1350OMS

List the purposes of 1350OMS-SDH
Identify the objects implemented by 1350OMS-SDH to fulfil its purposes


3JK Issue 03
Module Objectives [cont.]

1350OMS 1350OMS-SDH R 9.1.1 MNT4 Operation This page is left blank intentionally

3JK Issue 03
Page
1 1350OMS product and its applications 7

2 1350OMS-SDH purposes 11
3 1350OMS-SDH objects 15

3JK Issue 03

3JK Issue 03
1 1350OMS product and its applications


3JK Issue 03
TMN description
A Telecommunication Management Network (TMN) is a structured

network featuring management functions for a Telecommunication
Network.
The TMN is structured in layers
EML: Element Management Layer
To manage the network element configuration, alarms and performance
NML: Network Management Layer
To manage network connectivity, routing and protections in various topologies and
across different regions
SML: Service Management Layer
To manage services offered to the customer: order handling, service handling,
billing, service development, planning
BML: Business Management Layer
To manage the overall sales activity: e.g. return on investment, system decision
support, market analysis


3JK Issue 03
Open Interfaces
System Functional Overview Standard & Classic
Common HW
platform
HP Server
Common
desktop, login Common GUI Common Fault
& maps Management Common PM
and security
PACKET
NETWORK MANAGEMENT SDH SONET
WDM
ELEMENT MANAGEMENT
ANSI Alcatel-Lucent
ANSIAlcatel
Alcatel Alcatel-Lucent Legacy
Network
Network
Network
Network LegacyLucent
Lucent
(ETSI, Network
Network
(ETSI, Ethernet,WDM
Ethernet, WDMand
andSONET
SONET

The 1350OMS focuses on the Element Management and on the Network Management layers of the TMN.
These management layer functions are accomplished by a set of different “applications”.
The Element Management Layer is implemented by:

1350OMS-EML application
The Network Management Layer is implemented by:

1350OMS-SDH application
1350OMS-PKT application
1350OMS-SONET application
1350OMS-WDM application
Each of them is dedicated to a different network transport technology.
Common functionalities are bundled into components. Components are generic and not specialized for
the technology supported by the applications. They are:
Common desktop, login and security application
Common GUI (Graphical User Interface) and Maps application
Common Fault Management application
Common Performance Management application

3JK Issue 03
Applications and Subsystems 1350OMS
-Open Interfaces
Standard & Classic
Common HW
PKT
1350OMS
ETH platform
ETH, TMPLS Services
-PKT HP Server
Ntw. Mng
TDM SONET/PDH
Ntw. Mng SDH/PDH
1350OMS Services 1350OMS Services 1350OMS
-SONET -SDH -eOMS
WDM WDM
1350OMS
Ntw. Mng Services
-WDM
Element Mng
1350OMS-EML
Sub-network
management
Client/Server
Relationship
ANSI Alcatel-Lucent
ANSIAlcatel
Alcatel Alcatel-Lucent Legacy
Network
Network
Network
Network LegacyLucent
Lucent
(ETSI, Network
Network
(ETSI, Ethernet,WDM
Ethernet, WDMand
andSONET
SONET
1 1 10 All Rights Reserved © Alcatel-Lucent @@YEAR

The 1350OMS is decomposed into a set of “applications”, each of which is license controlled and
separately purchasable. These applications are:
1350OMS-EML, to manage Element Layer functions such as NE creation, SW download, NE data
backup/restore, NE alarms, PM data collection.
The Network Physical Resource (NPR) module is also part of the 1350OMS-EML application. It
manages network construction and inventory on physical resource (i.e. NE, boards and ports). It
provides support for manual/automatic physical link creation.
1350OMS-SDH, to manage provisioning, assurance (alarm correlation, fault localization), fulfillment
(performance monitoring) for the SDH technology and for the former WDM Alcatel equipment.
1350OMS-PKT, to manage: provisioning, assurance, fulfillment for the Ethernet/MPLS/CES/Packet
Ring technologies.
1350OMS-SONET, to manage: provisioning, assurance, fulfillment for the SONET technology.
1350OMS-WDM, to manage: provisioning, assurance, fulfillment for the WDM technology.
Moreover, the optional subsystem eOMS is integrated into 1350OMS Rel. 9.1 architecture to indirectly
manage the former Lucent legacy network. eOMS:
It is integrated with the 1350OMS GUI for single login and common GUI navigation.
It relies on the Common Fault Management component to display alarms.
It is integrated with EML, SDH, WDM and SONET applications for sub-network management.

3JK Issue 03
2 1350OMS-SDH purposes


3JK Issue 03
Service provisioning
In the most simple case, the user has just to select the two end-nodes.
1350OMS-SDH chooses the suitable end-points and route. However, the
user can also specify the desired end-points and route.
Protection configuration: SNCP, D&C, 2F/4F MS-SPRing, MSP
Service modification:
protection can be added/removed
service’s route can be modified
further end-points can be added
…


3JK Issue 03
Fault Management
The objects’ color depend

on the alarm severity
Alarm surveillance
Network
1350OMS-SDH
The elementary alarms are processed by 1350OMS-SDH in order to detect the impacted NML entities:
Physical Connections, Trails, Paths.

3JK Issue 03
Performance Management report
Tabular, Bar and Line reports are provided

PM data displayed in 15-minute or 24-hour granularities.

PM data archiving, backup.
Export of PM data to external systems.

3JK Issue 03
3 1350OMS-SDH objects


3JK Issue 03
Sub-Networks
Link: it represents all the

between two nodes
ROOT
Italy
63B 165B
Venice
Rome 53B
Colosseo

Sub-Networks feature the Nodes and the links between the Nodes. The link is a summary of all the
Physical Connections between two Nodes.

3JK Issue 03
SDH objects
xN x1
STM-N AUG AU4 VC4 C4 140 Mb/s
x3 34 Mb/s
x1 VC3 C3 OR
TUG3 TU3
45 Mb/s
x7
x3 VC12
TUG2 TU12 2 Mb/s
SDH Multiplexing Structure C12
= Overhead
VC4 payloaded as TU12,TU3,TU3 = Pointer
TUG3 #1 = Mapping
TUG2 #1 TUG2 #2 TUG2 #7 = Alignment
= Multiplexing
TU12 (03/1/1.1) TU12 (03/1/2.1) TU12 (03/1/7.1)
… TU12 (03/1/7.2)
AU4 #03
VC4 #03
TU12 (03/1/1.2) TU12 (03/1/2.2)

TU12 (03/1/1.3) TU12 (03/1/2.3) TU12 (03/1/7.3) Payload types:
TU3,TU3,TU3
TUG3 #2 AU4 TU3,TU3,TU12
TUG3 TUG2 TU12 TU3,TU12,TU3
TU3 (03/2) TU3,TU12,TU12
TUG3 #3 TU12,TU3,TU3
Objects numbering TU12,TU12,TU3
TU3 (03/3) TU12,TU3,TU12
in 1350OMS-SDH TU12,TU12,TU12
AU4 TUG3
The Multiplexing Structure is the basis of the SDH technology. It represents all the functions needed to
introduce a PDH signal into an SDH one.
SDH transmission is based on standard functional entities, used to transport a characteristic information
through a connection between two Termination Points in the network.
The SDH entities are:
Cn = Container of order n: this is the information structure carrying a synchronous payload.
VCn = Virtual Container of order n: this is the information structure formed by Cn+Path Overhead
(POH).
TUn = Tributary Unit of order n: information structure formed by VCn+Pointer.
TU12 is identified by (k,l,m) with: k= TUG3# (1...3); l=TUG2# (1...7); m=TU12# (1...3).
AU4 = Administrative Unit of order 4: information structure which provides for adaptation
(synchronization) between the Virtual Containers (VCn) and the multiplexing plane (= STM-N); it is
formed by VC4+Pointer.
Pointer = Indicator of off-set for VCn (it indicates the start position of VCn inside the payload).
TUG/AUG = Tributary Unit Group/Administrative Unit Group: a set of n x TU / n x AU.

3JK Issue 03
NE objects Vs 1350OMS-SDH objects: 2/34/45 Mb/s Path
LO Path
LO Link Connection
1350OMS-SDH
HO Trail (2 hops)
objects
HO Link Connection HO Link Connection

MS Trail MS Trail
Physical Physical
Connection Connection
L H M P P M H H M P P M H L
PDH NA
O C O S o o S O O S o o S O C O N PDH
A
Port P A r r r r A
C P C T t t T C C T t t T C P C P Port
T T T T T T T T T T
P P P P P P P P P P
MSOH
MSOH
MSOH
MSOH
RSOH
RSOH
RSOH
RSOH
STM-N STM-N
TUn
TUn
AU4
AU4
AU4
AU4
VC4
VC4
VCn
VCn
PPI
Pm
Pm
PPI
SPI
SPI
SPI
SPI
… …
Ei
Ei
X X X X X
NE 1 NE 2 NE 3
HO: Higher Order Higher Order
LO: Lower Order Ei: i=1 for 2Mb/s; i=3 for 34Mb/s
pass-through Pm: m=12 for 2Mb/s; m=31 for 34Mb/s
NAP: Network Access Point VCn-TUn: n=12 for 2Mb/s; n=3 for 34Mb/s
CTP: Connection Termination Point
PPI: PDH Physical Interface
CAP: Client Access Point (also said HO TTP)
MSOH: Multiplex Section Over-Head
TTP: Trail Termination Point
RSOH: Regenerator Section Over-Head
: Connection in Topology
SPI: SDH Physical Interface
Ei and Pm are PDH layer functions. Some NEs explicitly report and allow to configure both of them (e.g.
OMSN), whereas other NEs provide just Ei (e.g. 1850TSS-100). For example, E1 and P12 concern the
“Framed” and “Unframed” format of 2Mb/s PDH signals.
RSOH. The name of the object that manages the RSOH depends on the NE type. For example, in OMSN it
is said RST (Regeneration Section Termination); in 1850TSS it is said Section.
MSOH. The name of the object that manages the MSOH depends on the NE type. For example, in OMSN
it is said MST (Multiplex Section Termination); in 1850TSS it is said Line.
In case of 45Mb/s Path: instead of Ei, there’s DS3. Pm: m=41. VCn-TUn: n=3.
Physical Connection connects two STM-N ports. It is created by the user or auto-discovered by 1350OMS.
MS Trail & HO Link Connections: they are automatically created by 1350OMS-SDH at the Physical
Connection implementation. One HO LC is created for each couple of HO CTPs (AU4s).
HO Trail connects two CAPs/HO TTPs (VC4s). The user can create:
one-hop HO Trail whose extremities belong to adjacent NEs.
multi-hop HO Trail whose extremities belong to not adjacent NEs.
LO Link Connection is created by 1350OMS-SDH:
when setting up the payload of the HO Trail.
at the physical connection creation, if the user chooses to have some AU4s structured at Lower Order.
each time the payload configuration needs to be automatically modified in order to implement a new
Path.
Path is created by the user. It’s the end-to-end service with NAPs as terminations.
Higher Order pass-through in NE 2 accomplishes a transit at AU4 level. Thus, no drop/insert is allowed
in NE 2 for the services carried by the HO Trail.

3JK Issue 03
NE objects Vs 1350OMS-SDH objects: 2/34/45 Mb/s Path
LO Path
LO Link Connection LO Link Connection
1350OMS-SDH
HO Trail (1 hop) HO Trail (1 hop)

objects

MS Trail MS Trail
Phys. Phys.
Conn. Conn.
L H M P P M H L L H M P P M H L
PDH NA
O C O S o o S O C O O C O S o o S O C O N PDH
A
Port P A r r A A r r A
C P C T t t T C P C C P C T t t T C P C P Port
T T T T T T T T T T T T
P P P P P P P P P P P P
MSOH
MSOH
MSOH
MSOH
RSOH
RSOH
RSOH
RSOH
TUn
TUn
TUn
AU4
TUn
AU4
AU4
AU4
VC4
VCn
VC4
VC4
VC4
VCn
Pm
PPI
PPI
Pm
SPI
SPI
SPI
SPI
… … … …
Ei
Ei
X X X X X X X
NE 1 NE 2 NE 3
HO: Higher Order Lower Order
LO: Lower Order Ei: i=1 for 2Mb/s; i=3 for 34Mb/s
By means of Lower Order pass-through, each HO Trail’s LO Link Connection can be treated separately.
In the intermediate NE, some LO CTPs can be put in transit whereas others can be exploited for
drop/insert services.

3JK Issue 03
NE objects Vs 1350OMS-SDH objects: 140 Mb/s Path
HO Path
1350OMS-SDH

objects
MS Trail MS Trail
Physical Physical
H M P P M H H M P P M H
PDH N O S o o S O O S o o S O N PDH
A r r r r A
Port P C T t t T C C T t t T C P Port
T T T T T T T T
P P P P P P P P
MSOH
MSOH
MSOH
MSOH
RSOH
RSOH
RSOH
RSOH
STM-N STM-N
AU4
AU4
AU4
AU4
VC4
VC4
PPI
PPI
SPI
SPI
SPI
SPI
P4
P4
E4
E4
X X X
NE 1 NE 2 NE 3
Higher Order
HO: Higher Order pass-through
LO: Lower Order
NAP: Network Access Point PPI: PDH Physical Interface
CTP: Connection Termination Point MSOH: Multiplex Section Over-Head
TTP: Trail Termination Point RSOH: Regenerator Section Over-Head
: Connection in Topology SPI: SDH Physical Interface
No HO Trail and subtended LO objects are required. 140Mb/s Path makes directly use of HO Link
Connections.

3JK Issue 03
Hierarchy of transport objects for PDH Paths
STM-N Physical Connection
(example: N=4)
MS Trail
(one per Physical Connection)
HO Link Connection
(N per MS Trail)
HO Trail
(one per HO LC)
LO Link Connection
(the quantity and type depend on
the payload type)
TU3,TU3,TU3
TU3,TU3,TU12
TU3,TU12,TU3
TU3,TU12,TU12
TU12,TU3,TU3
HO Path LO Path TU12,TU12,TU3
(one per HO LC) TU12,TU3,TU12
(one per LO LC) TU12,TU12,TU12

3JK Issue 03
NE objects Vs 1350OMS-SDH objects: Data Path
Ethernet Path Not concatenated
LO/HO Link Connection Ethernet Path
For Server
layers refer to Eth NA
N Eth
A
1350OMS-SDH
the previous CTP CTP
Port P SDH P Port objects
slides
Network NE
MAU
MAU
VCn
VCn
TU/AU TU/AU
objects
Ethernet Path
Ethernet Server Link Connection Concatenated
Ethernet Server Trail (channel#1)
Ethernet Path
Ethernet Server Trail (channel#2) (example: VCx-2V)
LO/HO Link Connection
CAP #1 CTP CTP CAP #1

Eth N N Eth 1350OMS-SDH
A CTP CTP A
Port P P Port objects
CAP #2 CTP SDH CTP CAP #2
VCx #1 TU/AU Network TU/AU VCx #1

TU/AU
TU/AU
MAU
MAU
VCG
VCG
NE
-2V
-2V
VCx #2 TU/AU TU/AU VCx #2 objects

MAU: Medium Attachment Unit.

VCG: Virtual Concatenation Group (e.g. VC12-5V, VC4-7V).
From 1350OMS-SDH point of view, there’s little difference between Data Paths and PDH Paths. Both
Data and PDH signals are mapped into SDH Virtual Containers that are routed over the SDH network.
Data Paths can rely or not on virtual concatenation. If virtual concatenation is implemented, the
Path consists on several Server Trails, one per Virtual Container.

3JK Issue 03
Hierarchy of transport objects for Data Paths
4 Concatenated Data Path (3 x VC4)

T M-
S
Concatenated
Data Path
(3 x VC3)
ST
M-
4
MS Trail
(one per Physical HO Trail
Connection) (one per HO LC)
HO Link Connection LO Link

(N per MS Trail) Connection
The Virtual Containers of the Virtual Concatenation Group can use different routes over the SDH
network. In the picture, the Paths rely on two STM-4 Physical Connections.

3JK Issue 03
Objects creation sequence
1. Network Elements [dealt in 1350OMS-EML training]

the Nodes are automatically created upon NE creation
2. Sub-Networks [mainly dealt in 1350OMS-EML training]
3. Physical Connections [mainly dealt in 1350OMS-EML training]

MS Trails and HO Link Connections are automatically created
4. NPA (Network Protection Architecture)

just in case of protection handling: SNCP (optional), MSP, 2F/4F MS-SPRing
5. HO Trails
necessary for Paths with VC12 or VC3 granularity
LO Link Connections are automatically created
6. Paths

Sub-Networks are not mandatory. Physical Connections, NPA, HO Trails, Paths can be created even
without configuring any Sub-Networks.
NPA is not mandatory in case of SNCP. It’s mandatory for MSP and 2F/4F MS-SPRing.

3JK Issue 03
Node View
Working state NA reachability Craft Terminal Access status

NE consistency phase Alarms aligned
Alarms alignment
EML Domain
EML Domain alignment Download status
Paths Client Ports
Starting/Ending NAPs
Paths Alarmed objects
TTPs/CAPs
Starting/Ending Not aligned objects
HO Trails HO CTPs
Not aligned objects
Physical (traffic impacting)
SDH ports
connections

“Node View” is a summary window that allows to retrieve the 1350OMS-SDH objects as far as a Node is
concerned.
1350OMS-SDH has a Node for each NE.
To get the Node View, select a Node and ...
... Search OTN Node View
or click the shortcut
NA reachability. NA stands for Network Adapter and corresponds to the EML-IM (Element Management
Layer – Information Manager) in charge of managing the Network Element (e.g. EMLIMQ3 for OMSN,
EMLIMSNA for 1850TSS).
NE consistency phase: it concerns the alignment between the Node used by 1350OMS-SDH and the
Network Element in terms of CTPs, NAPs, CAPs, ports, ...
Download status: if enabled, the configurations performed by means of 1350OMS-SDH are downloaded
to the Network Element; if disabled, the configurations are just kept in the 1350OMS-SDH’s database.
EML Domain. It’s the EML-IM. By synchronizing it, 1350OMS-SDH uploads the Nodes and the ports (SDH
and Client ports) from the Network Elements that are managed by that EML-IM.

3JK Issue 03
Answer the Questions
1. How many MS Trails are there in an STM-16 Physical Connection?
2. What are the HO Link Connection’s extremities?
3. How many HO Link Connections are there in an STM-16?
4. How many HO CTPs are involved in an STM-16 Physical Connection?
5. What are the HO Trail’s extremities?
6. Is HO Trail necessary for every type of Path?
7. What are the Path’s extremities?
8. How many 2M Paths can an HO Trail with payload TU12,TU3,TU3 bear?


3JK Issue 03
Blank Page


3JK Issue 03
End of Module
Product Overview


3JK Issue 03
@@SECTI
Section 2
System Operation
Module 1
How to log on
xx Issue 03
1350OMS

xx Issue 03
Blank Page

System Operation How to log on
Document History

xx Issue 03
Module Objectives
Login and start the 1350OMS application

Navigate the Web Portal


xx Issue 03


xx Issue 03
Page
1 Login windows 7
2 Web Portal Overview 11

xx Issue 03

xx Issue 03
1 Login windows


xx Issue 03
1 Login windows
Preliminary setting
1. Select the following folder:

C : \ WINNT \ system32 \ drivers \ etc
2. Open the file “hosts”
4. Save the file

and exit
3. Insert the IP address and
hostname of the Server
To gain full access to the Graphical User Interfaces (GUIs), the PC must be configured so that HP-UX
server can be reached using its machine hostname. If the Domain Name Server (DNS) is configured on
the PC, it should be configured so that HP-UX server hostname is managed.
If such a configuration is not feasible, the HP-UX server hostname IP address association must be
manually inserted in the following file:
C:\WINxxx\system32\drivers\etc\hosts in case the PC runs the Windows® Operating System
/etc/hosts in case PC runs the PC-Linux Operating System

xx Issue 03
1 Login windows
Web Browser
1. Open a Web Browser and type

the Server’s IP address as Address

Java 1.6 is required.

The system can be invoked from any web browser.

xx Issue 03
1 Login windows
Web Desktop
2. Insert User
and Password
and then Login
1. Click
here

On the first log in, the user will be asked to change the password:
it must contain at least a digit, a special char, an uppercase letter.
It must not contain the User string.

xx Issue 03
2 Web Portal Overview


xx Issue 03
Web Portal
Web Portal is a Java application that is started when the user logs in
from the Web Desktop
Toolbar
Main View Area

Tree Area
Message Area
Status Bar

The web Portal provides the user with a view of all the 1350OMS applications and manages GUI
navigation among the sub-system components.
The Tree Area is a navigational panel which is organized with a hierarchical tree that lists the
1350OMS applications. Applications are displayed grouped by their logical functions, which are
Operation (Management, Alarm, Network Tools) and Administration (System, Data Management,
Security Administration). When a logical function is selected from the Tree Area, the application’s
icons are displayed in the Main View Area.
In the Main View Area the application’s icons can be selected to open the application. When the user
selects a logical function from the Tree Area, the icons representing the 1350OMS applications
related to the logical function are displayed in the Main View Area. To start an application, double
click an icon or right click the icon to display a Start button.
The Message Area displays application and Web Portal messages.
The Status Bar displays the last application or Web Portal message.

xx Issue 03
Web Portal Applications Navigation
Administration
Operation

Common system applications are grouped by their logical function as follows:

Operation: it includes applications for Network Provisioning and Inventory, Alarms and “IP over
OSI” Tunnel GUI.
Administration: it includes system administration tools, such as System Monitor, Task Scheduler,
Data Backup/Restore, Security Administration.

xx Issue 03
Operation applications: Management
Network Management provides the Multi Service Graphical User
Interface (MS-GUI) that allows to manage all the applications (EML,
SDH, WDM, PKT) for service provisioning and Performance Monitoring.
As far as EML and SDH are concerned, MS-GUI manages NEs, Nodes,
Sub-Networks, Physical Connections, Trails, Paths.
Right click and

choose “Start”
or double click
the icon to
start the MS-GUI


xx Issue 03
Operation applications: Management [cont.]
Physical
OTN


xx Issue 03
Operation applications: Alarms
Alarms application is the single common fault management environment
which provides the GUIs for the alarms of all managed NEs and networks.
The alarm GUIs present a dynamic view of the current alarms and the
historical alarms.
Global Alarm GUI consolidates the alarms of all the applications: EML, SDH,
WDM, PKT. Single-application GUIs are available, too.
Global
SDH
EML


xx Issue 03
System Monitor
If green, all the application’s

processes are OK


xx Issue 03
End of Module
How to log on


xx Issue 03
@@SECTI
Section 2
System Operation
Module 2
Network topology
ss Issue 03
1350OMS

ss Issue 03
Blank Page

System Operation Network topology
Document History

ss Issue 03
Module Objectives
manage the Sub-Networks

create the Physical Connections either manually or automatically
recognize the SDH objects provided by the Physical Connections
create the External Networks
manage the Network Protection Architecture (NPA)


ss Issue 03


ss Issue 03
Page
1 Sub-Networks 7
2 Physical Connections 9
2.1 Introduction on Physical Connections 11
2.2 Manually creating Physical Connections 15
2.3 Automatic upload of Physical Connections 23
3 External Networks 35
4 NPA 39
4.1 Introduction on NPA 41
4.2 SNCP NPA 47
4.3 MSP 1+1 NPA 57
4.4 MSP 1:n NPA 65
4.5 2F MS-SPRing NPA 73
4.6 Upload Protection Schema 77

ss Issue 03
Page

ss Issue 03
1 Sub-Networks


ss Issue 03
1 Sub-Networks
Summary about operation on Sub-Networks
1. To manage the Sub-Networks: select
a Sub-Network right click
• Modify: just to change the name and comments
Map: to get the Map

•
view
• Sub-Networks: to get the list
of the subtended Sub-
Networks
• Delete: to delete the Sub-Network. Its Nodes
are not deleted from the database and can
be assigned to another Sub-Network
• Create: to create a new child Sub-
Network. Meanwhile, it’s possible to
assign Nodes, too.
• Modify: to add/remove Nodes and to
change the parent Sub-Network
The Sub-Network management is dealt in 1350OMS-EML training. Here just a summary.

ROOT is always configured by default as the root network under which all the managed Sub-Networks
must be created, based on the desired hierarchy.
ROOT cannot directly contain any Node.
When a Network Element (NE) is created in EML, a correspondent object, called Node, is automatically
created too.
A Node is the logical representation of the NE and contains the objects used by the network managers
for modeling the transmission network: ports, NAPs, CAPs, …
Besides Nodes, it’s possible to assign other Sub-networks to a given Sub-Network.
A Node involved in Physical Connections, Trails, and Paths and initially assigned to a Sub-Network, can
be then assigned to another Sub-Network. Two methods are available:
by means of commands
remove the Node from the current Sub-Network: select the Node Actions MAP Remove Node
From Sub-Network
assign the Node to another Sub-Network: select the other Sub-Network Actions Modify Sub-
Network
by means of drag&drop
open the Maps of both the source Sub-Network and the destination Sub-Network
arrange the two Maps so that they can be seen at the same time in the main panel
drag&drop the Node

ss Issue 03
2 Physical Connections


ss Issue 03
Blank Page


ss Issue 03
2.1 Introduction on Physical Connections


ss Issue 03
Objects involved in Physical Connection
1350OMS-SDH HO Link Connection

MS Trail
objects
Physical
Connection
Node 1 L H M
P P
M H Node 2
O O S S O
o o
PDH N C C C T r r T C
A T A T T t t T T
Port P P P P P P P
MSOH
MSOH
RSOH
RSOH
STM-N
TUn
AU4
AU4
VCn
VC4
PPI
Pm
SPI
SPI
…
Ei
X X
NE 1 NE 2 HO: Higher Order

LO: Lower Order
NE Node
PPI: PDH Physical Interface NAP: Network Access Point
MSOH: Multiplex Section Over-Head CTP: Connection Termination Point
RSOH: Regenerator Section Over-Head CAP: Client Access Point (also said HO TTP)
SPI: SDH Physical Interface TTP: Trail Termination Point


ss Issue 03
Physical Connection lifecycle
PC “Implementation State”:
Issue the command Defined, Implemented, Deimplemented
“Synchronize NE” on the Nodes
Nodes are available Also Ports are available in the

in the 1350OMS’s DB 1350OMS’s DB. STM-N ports’
Assignment State is “Observed”.
C Create PC Remove PC
v eP blu
mo PC is DEFINED e
Re
Ports’ Assignment State is “Assigned”
Implement PC
PC is DEIMPLEMENTED PC is IMPLEMENTED
HO-CTPs, HO-LCs, MS-TTPs, MS-Trails are It’s the normal working condition
available in the 1350OMS’s database but
the provisioning is limited (see note) HO-CTPs, HO-LCs, MS-TTPs, and MS-Trails
are available in the 1350OMS’s DB and can
ma be used to provision HO-Trails and Paths.
gen
ta Deimplement PC gre
User can put the PC “In service”. en

DB: database
PC: Physical Connection
When the Physical Connection is deimplemented:

if the user creates HO-Trails by means of the wizard, the HO-Trails can not be allocated.
it’s possible to create and implement HO-Trails by means of “payload configuration”.
it’s not possible to allocate Paths.
The Physical Connection deimplementation:

is possible even if the PC contains one-hop HO-Trails (also implemented), even with Lower Order
payload.
is not possible if the PC contains allocated, implemented or commissioned Paths.
is not possible if the PC belongs to an implemented NPA (Network Protection Architecture).
The Physical Connection’s default “Service State” is “Not In Service”. The user can set “Service State”
to “In Service”. It’s useful from alarm management point of view. 1350OMS-SDH’s Alarm Surveillance
handles two different alarm sub-lists for PC: the “Physical Link In Service” sub-list and the “All Physical
Links” sub-list.

ss Issue 03
Two ways to create Physical Connections
First of all, 1350OMS-SDH must be aware of the Nodes’ Ports.

To retrieve the Ports from the NE:
Node Actions Physical Synchronize Synchronize NE
To verify that the Ports have been uploaded:
Node Search Physical Ports
Once the Ports are available, it’s possible to create the Physical
Connections.
Two different procedures for creating STM-N Physical Connections:

1. Manual procedure
The user manually creates the PC between the Nodes, based on the information he
has about the network connectivity.
2. Automatic upload procedure
The Physical Connections are auto-discovered by means of the Trace Identifier
contained in the J0 byte of the STM-N frames.

The Physical Connection’s Trace Identifier can be configured either by means of the automatic
procedure or manually by the user.
The manually configured TI is not overwritten by the automatic procedure.
The TI configured by the automatic procedure is overwritten by the manual configuration.

ss Issue 03
2.2 Manually creating Physical
Connections


ss Issue 03
2.2 Manually creating Physical Connections
Procedure
1. Select the two end-Nodes of the Physical Connection (optional)

2. Issue “Actions Physical Create Physical Connection”
The “Create Physical Connection” Wizard is opened
3. Assign a User Label to the Physical Connection
4. Select “Connection Type” (SDH, WDM, Ethernet, …) and other
relevant parameters of the PC to be created. Set the “Implement
Rule”
5. Click “Next”
6. Based on the “Connection Type” chosen at point 4, select the “STM
Type” or “WDM Type” etc.
7. Select the “A Node”, “Z Node”, “A Port” and “Z port”
8. Click “Apply” to start the Physical Connection creation
In the following, an example is given for the creation of an SDH

Physical Connection

Step 1: if the user selects the two Nodes before issuing the creation command, the two Nodes will be
shown in the creation wizard. Otherwise, the user will have to select the Nodes from the creation
wizard.

ss Issue 03
Example
2. Actions Physical
Create Physical
Connection
1. Select the two end-Nodes

of the Physical Connection
(optional)

ss Issue 03
Example [cont.]
3. Assign a User Label to the

Physical Connection
4. Select “Connection
Type” and other
relevant parameters
5. Next
Transport Alarm Enabling Rule:

values: On Definition, On Implementation, On Set in-service, Manual
the user can decide the Physical Connection’s state at which the PC’s alarms must be enabled. In
case of Manual, the alarm enabling is up to the user.
Implement Rule:
if set to “Automatic”, 1350OMS-SDH implements the Physical Connection, so that all the objects (HO-
CTPs, HO-Links, MS-TTPs, MS-Trails) necessary for the management of the Physical Connection at
network layer are created.
if set to User, the Physical Connection’s “Implementation State” will be Defined. The
implementation is up to the user.
Allocation cost: it’s taken into account by the routing algorithm to choose the route for HO-Trails and
Paths. The lower the “Allocation cost”, the more the PC is likely to be used.
Show created Physical Connection: if set to Yes, the “Physical Connection structure” window is
automatically opened at the end of the creation.

ss Issue 03
Example [cont.]
6. select the
“Rate”
7. Select “A Node”, “Z Node”, “A Port and “Z port”. To

get the Node or Port selection window, click the
nearby icon or anywhere on the “Node” or “Port” box.
Click “More Log” for 8. Apply

details

● Physical Connection Rate: STM0, STM1, STM4, STM16, STM64, STM256.

● A and Z: information used by 1350OMS-SDH to provide the graphical views. For example, “A Node” is put
in the left-hand side of the Physical Connection Structure; “Z Node” in the right-hand side.
● Port Specification Mode:
From List: a port of the Node that corresponds to a real card of the equipment.
Create Planned Port: to create in the Node a Port that does not exist in the equipment. It is dealt in
the “Topology Modification” module.
● Used For Test: port to be connected to a test instrument. It’s dealt in the “Troubleshooting Tools”
module.
● Preserve Au4 Concatenation: to keep the concatenation already configured in the equipment.
● Initial Number of Au4 at LO: for creating and payloading HO-Trails between the two Nodes.
● Saturation Profile: it’s taken into account by the routing algorithm to choose the route for HO-Trails and
Paths. 1350OMS-SDH aims at distributing HO-Trails and Paths among the available Physical Connections
instead of assigning HO-Trails and Paths to just one Physical Connection till it is full.
● Fragmentation Profile: it’s taken into account by the routing algorithm to choose the route for HO-Trails
and Paths. 1350OMS-SDH aims at keeping free higher layers resources (AU4,...) by using the lower layer
resources (TU12,...) of already and partially engaged higher layers resources.

ss Issue 03
Physical Connection Structure
HO-Link Connection
MS-Trail
PC
Node HO CTP MS TTP Port Port MS TTP HO CTP

STM-N
SPI SPI
NE AU4 MSOH MSOH AU4
RSOH RSOH
Node Physical Connection

(Implemented)
STM-N Port
HO-Link Connection
MS-Trail
MS-Trail and HO-Link Connections are NOT available if the PC is “Defined”


ss Issue 03
Manage the Physical Connection life cycle
1. Retrieve a PC list. There are several ways to do it: Node’s Ports
- From Main menu bar, Sub-Network or Node: create remove
Search Physical Physical Connections ov e
rem DEFINED
- From a link on the map: Search List Physical deimplement implement
Connections DEIMPLEMENTED IMPLEMENTED
Implementation State
2. Commands for managing

the life cycle

In the Physical Connection creation wizard there’s the parameter “Implement Rule”; it can be set to
Automatic or User.
Automatic: the Physical Connection is created and automatically implemented.
User: the Physical Connection is created and left to Defined. Then the user will implement it.
Service State is meaningful for alarm management.

ss Issue 03
Preserve AU4 concatenation
1. Go to the Step 2 of
Physical Connection
creation wizard
Missing HO Link Connections
4c: HO LC that corresponds

to a Contiguous
concatenation of four AU4s
2. Set it
If “Preserve Au4 Concatenation” is set to “True”,
PC takes into account the equipment configuration

By setting “Preserve Au4 Concatenation” to True, 1350OMS-SDH checks the AU4 organization of the
equipment’s ports involved in the Physical Connection creation.
The contiguous concatenated AU4s previously created by the 1350OMS-EML user or by the Craft
Terminal user will yield contiguous concatenated HO Link Connections on implementing the Physical
Connection.
If the equipment’s ports have contiguous concatenated AU4s, but “Preserve Au4 Concatenation” is set
to False, 1350OMS-SDH will turn the concatenated AU4s into single AU4s.
If just one of the two ports has contiguous concatenated AU4s and “Preserve Au4 Concatenation” is set
to True, 1350OMS-SDH will turn the concatenated AU4s into single AU4s.

ss Issue 03
2.3 Automatic upload of Physical
Connections


ss Issue 03
2.3 Automatic upload of Physical Connections
Procedure – Part 1: Trace Identifier
1. Select the Nodes involved in the creation of the physical connectivity

2. Issue “Actions Physical Discover Physical Topology”
The “Discover Physical Topology” wizard is opened
3. Put “Action Selection = Automatic Generation of Trace Identifier”
4. Click on “Next”
5. Check that the selected Nodes appear in the “Node” section,
otherwise right-click the Node and issue “Send To Discover
Physical Topology Node”
6. Click on “Apply”. Don’t close the wizard.
7. To see the details about the Trace Identifier setting:
in the wizard: More Log
in the MS-GUI: Logs tab


ss Issue 03
Procedure – Part 2: Upload Physical Connections
8. Click on “Back” in the wizard.

9. Put “Action Selection = Physical Connectivity from J0”
10. Click on “Next”
11. The Nodes reappear in the “Node” section
12. Set “Implement” as you prefer: False or True
13. Click on “Apply”
14. To see the details about the Physical Connection upload:
in the wizard: More Log
in the MS-GUI: Logs tab


ss Issue 03
Example
2. Discover Physical
Topology
1. Select
the
Nodes


ss Issue 03
Example [cont.]
3. Automatic Generation of Trace Identifier
4. Next

ss Issue 03
Example [cont.]
5. “Send To” can 6. Apply

be used as well


ss Issue 03
Example [cont.]
To close the Log
8. Back
7. More Log

ss Issue 03
Example [cont.]
9. Physical Connectivity from
J0
10. Next

ss Issue 03
Example [cont.]
11. Nodes still

available
12. Implement:
False or True
13. Apply
Implement:
if set to True, 1350OMS-SDH implements the Physical Connection, so that all the objects (HO-CTPs,
HO-Links, MS-TTPs, MS-Trails) necessary for the management of the Physical Connection at network
layer are created along with the Physical Connection creation.
if set to False, the user will have to implement manually each Physical Connection.

ss Issue 03
Example [cont.]
14. Logs in MS-GUI


ss Issue 03
Example [cont.]
Properties

The User Label of the discovered Physical Connections is set by 1350OMS by appending the Port
Identifiers to the suffix AutoDisc.

ss Issue 03
Exercise
Based on the network available for the training:

create a suitable sub-network hierarchy
create the Physical Connections by using both the manual and the automatic
upload procedures


ss Issue 03
3 External Networks


ss Issue 03
3 External Networks
Creation
• External Network represents a Network whose NEs are not managed
by 1350OMS-SDH.
• External Networks are treated by 1350OMS-SDH as Nodes.
• It’s possible to create Physical Connections, HO-Trails and Paths
involving both NEs managed by 1350OMS-SDH and External Networks.
1. To create an External
Network: Actions Physical 3. The External Network creation
Create External Network provides a Node but not an NE. The
Node can be put in the Sub-Network
2. Just “User Label” and

“Location Name” are
required.
This window is the one used to add
objects to the Sub-Network
To add an External Network to a Sub-network, use the same procedure as for Nodes: select the
destination Sub-Network right click Actions Modify Sub-Network.
It’s possible to create Physical Connections, HO-Trails and Paths also between:
an NE managed by 1350OMS-SDH and External Network
two External Networks

ss Issue 03
3 External Networks
Physical Connection with External Networks
Step#2 of Physical Connection creation
Node that corresponds to a
NE managed by 1350OMS-SDH External Network
1. Choose “Create Port”

2. Specify a name for the External Network’s
port. The port is automatically created.
3. “Used For Test”=“True”: in case the

External Network is a test instrument

“Used For Test”=“True” is meant for monitoring and troubleshooting purposes by connecting a test
instrument (External Network) to the “Real” NE (63B). Any signals transiting through any ports of the
“Real” NE can be forwarded to the test instrument, too.

ss Issue 03
Exercise
Create an External Network

Create a Physical Connection between the External Network and a Node
Check the Physical Connection Structure


ss Issue 03
4 NPA


ss Issue 03
Blank Page


ss Issue 03
4.1 Introduction on NPA


ss Issue 03
Definition
The NPA (Network Protection Architecture) object is used to manage

the protection schemes.
An NPA is a set of Physical Connections accomplishing a dedicated

protection scheme or grouped together to establish path layer
protections.
NPA types are:

SNCP
MSP (1+1, 1:n)
2F MS-SPRing
4F MS-SPRing
ASON (*)
FAST-Restoration (*)
(*) not dealt in the standard 1350OMS-SDH Operation training

ASON: Automatically Switched Optical Network.

SNCP, 2F MS-SPRing and 4F MS-SPRing rings in all the configurations supported by the NEs. This includes
stacked or collapsed rings and multiple rings per NE.
NPA allows to manage the protection schemes, including:

Construction/set-up and modification of protected network architectures.
Maintenance: visualization of current protection state, handling of switch events and user commands.
An integrated path provisioning including D&C and flexibility in specifying the protections providing
automatic “acceptable” solutions in most of the supported and installed network configurations.
The 1350OMS-SDH user builds the network defining:

Sub-Network hierarchy.
The assignment of the Nodes to the Sub-Networks.
Physical Connections between the Nodes.
As a further, independent step, the user can build the NPA.

ss Issue 03
NE – Topology - NPA
Sub-net 3
NPA deals with Physical Connections
• One or more NPAs per NE

SNCP
NPA • NPA can encompass Physical Connections
between Nodes of different Sub-Networks
Sub-net 2
2F MS-
SNCP
NPA SPRing NPA
MSP
NPA
Sub-net 1
2F MS-SPRing
2F MS-SPRing NPA
Sub-net 4 NPA

It’s possible to configure in the network multiple SNCP, 2F MS-SPRing and 4F MS-SPRing rings crossing
the same NE.

ss Issue 03
Benefits
Is NPA necessary?
For MSP, 2F MS-SPRing, and 4F MS-SPRing the NPA configuration is mandatory.

Should NPA not be configured, the protection scheme is not established.
For SNCP the NPA is not mandatory, but NPA eases the constraint
management.
Example: the Link Connection (Tu12) of a Physical Connection assigned as constraint
to a Path, is engaged in all the ring’s Physical Connections.
NPA & Routing Algorithm:

The user can set two costs relevant to NPA. These costs are taken into
account by the Routing Algorithm in allocating Paths/Trails and have the
target to make it costly to enter and to exit in/from an NPA (costs are not
feasible for MSP):
NPA Usage Cost: it is an extra cost to pay for crossing the NPA.
NPA Reduction Cost Factor: it enables a percentage cost reduction for the Physical
Connections belonging to the NPA.

ss Issue 03
Physical Connection and NPAs
An SDH Physical Connection can belong to only one NPA with the
following exception:
SNCP/MSP
ASON Internal/Linear MSP (*)
ASON Interworking/any other NPA (*)
FAST-Restoration Internal/MSP
An SDH Physical Connection is present in 1350OMS also when supported

by a WDM network. The server OTS or OPS physical connections are not
part of a NPA.
(*) ASON is not dealt in the standard 1350OMS-SDH Operation training


ss Issue 03
Blank Page


ss Issue 03
4.2 SNCP NPA


ss Issue 03
4.2 SNCP NPA
Creation: Step 1
The Physical Connections
must have the same rate
1. Actions OTN Create NPA
Select SNCP
Time Slot
Interchange
Finally, do Next
See next slide

NPA Reduction Cost Factor:

It is taken into account by the Routing algorithm.
It enables a cost reduction for the Physical Connections belonging to the NPA. This cost reduction has
the target to make more attractive the routing inside an NPA than an external one.
It works together with the NPA Usage Cost making more attractive long routes in an NPA.
If equal to 0 it has no effect.
The bigger it is set, the more the cost of NPA internal route is reduced.
It is a percentage value and can be set from 0% to 100%. Default value is 20%.
NPA Usage Cost:

It is taken into account by the Routing algorithm.
It is an extra cost to pay for the usage of an NPA. It has the target to make costly to enter and to exit
in/from an NPA.
The bigger this attribute is set, the more the routing inside a single NPA will be preferred compared
to a routing involving more than one NPA.
If set to 0, the routing is done not considering the NPA.
Its value can be set from 0 to 100. Default value is 20.

ss Issue 03
4.2 SNCP NPA
Time Slot Interchange
When a Path/Trail is allocated, it is not said that the same time slot
(i.e. AU4, TU3, TU12) is used over all the involved Physical
Connections. The “Time Slot Interchange” attribute allows to inhibit or
not this changing for SNCP and 2F MS-SPRing.
The “Time Slot Interchange” attribute can be set to:

Allowed: Paths/Trails are allocated allowing the interchanging of the time
slot.
Preferable Avoided: the time slot interchange is still allowed, but

Paths/Trails are allocated keeping the same time slot in the NPA, if possible.
Forbidden: the time slot interchange is not allowed, that is Paths/Trails are
allocated keeping the same time slot in the NPA, if possible; if not possible,
the allocation fails.

HO-Trail: even if Time Slot Interchange is set to Allowed, the routing algorithm implements the
“Preferable avoided” approach.
Examples for LO Path when Time Slot Interchange is set to Forbidden:

A Path can not be allocated over two single-hop HO-Trails that use two different AU4s (Trail#1
uses AU4#1 whereas Trail#2 uses AU4#2).
A Path can be allocated over a two-hop HO-Trail that uses different AU4s (AU4#1 and AU4#2).
For 2F MS-SPRing rings Time Slot Interchange is meaningful only at Lower Order.

ss Issue 03
4.2 SNCP NPA
Creation: Step 2
To remove Physical
Connections
1. Click this icon to open the Physical
Connection list and select the
Physical Connections for the NPA
2. Do Apply to create the NPA. NPA is

created in the Defined state. It must be
implemented, too. See next slide.


ss Issue 03
4.2 SNCP NPA
Implementation
1. Verify that the
Physical
Connections are
implemented
2. To retrieve the NPA
list: Search OTN
NPAs
NPA list NPA is Defined
3. Implement the NPA

create remove
DEFINED
implement deimplement
IMPLEMENTED

Implemented:
the NPA costs and the Time Slot Interchange attribute are taken into account by the routing
algorithm.
in case of MSP and MS-SPRing NPAs, the relevant protection is configured in the equipment according
to the NPA settings.

ss Issue 03
4.2 SNCP NPA
NPA indication
NPA icon is also put in
the routing display of
the HO-Trails and Paths
1. Select SDH as over the Physical
Technology Connections of NPA
NPA
icons
Map
PC
Structure


ss Issue 03
4.2 SNCP NPA
Search for NPA’s items
NPA list
1. NPA View
See next
slide


ss Issue 03
4.2 SNCP NPA
NPA view
NPA View
Search Search
Nodes Physical Connections


ss Issue 03
4.2 SNCP NPA
Modify
NPA list
Modify
• User label, Costs,
Time slot Interchange
• allowed even for
Implemented NPA
Modify NPA
• “NPA creation” like:
attribute modification,
add/remove PCs
• allowed only for Defined NPA
Time Slot Interchange:

Its value is meaningful only for Paths/Trails to be allocated, that is new or to be rerouted
Paths/Trails. No modification is applied to the Paths/Trails already allocated.
It can be modified from any value to any value even if the NPA is already crossed by Paths/Trails.

ss Issue 03
Blank Page


ss Issue 03
4.3 MSP 1+1 NPA


ss Issue 03
4.3 MSP 1+1 NPA
General concept
(MSP 1+1) = (Linear plus)

(Single ended) = (Unidirectional)
Normal condition
NE 1
(Dual ended) = (Bidirectional)
Normal condition
NE 1
NE 2
One-way failure condition

NE 1
NE 2
One-way failure condition
NE 1
NE 2
NE 2

In single ended mode the protection is accomplished by switching only the side affected by the
failure.
In dual ended mode the protection is accomplished by switching both the sides, the one affected and
the one unaffected.
1+1 linear APS (single ended/dual ended MSP) is meant for STM-N line protection.
Switching criteria are: LOS, LOF, MS-AIS, Excessive BER (B2), Signal Degrade (B2), or card failure.
Note that each STM-1 electrical stream can be protected by an optical stream and vice versa.
Switching signaling (in dual ended) is carried over the APS channel (K1 and K2 bytes), using the K-
byte protocol.
Only NON REVERTIVE mode is supported.

ss Issue 03
4.3 MSP 1+1 NPA
Creation: Step 1
1. Actions OTN Create NPA 2. Insert the NPA
User Label
3. Select the NPA
Type: Linear-plus
4. Choose the
Protection
switch mode
6. Plus APS Mode

5. The mode of operation noAPS: Unidir
is “nonRevertive”
generic: Unidir/Bidir
optimized: Bidir
7. Next
Bidirectional = Dual Ended

Unidirectional = Single Ended
Some NEs support just the “Unidirectional” type.

ss Issue 03
4.3 MSP 1+1 NPA
Creation: Step 2
2. Choose the SPARE

1. Choose the MAIN Physical Connection
Physical Connection
3. Apply


ss Issue 03
4.3 MSP 1+1 NPA
Implementation
Checks are performed during the implementation to verify that no HO-
Trail/Path is present on the Spare Physical Connection.
By implementing the NPA, the protection is configured in the NEs.
1. NPA Implementation can be done from

several views. For example from the
Physical Connection Structure. 2. Implement
PC structure


ss Issue 03
4.3 MSP 1+1 NPA
NPA View
The NPA view can be got by selecting the NPA in any views (NPA
list, Physical Connection structure, …) and then “Search NPA
View”
MS Protection Block’s Protection

Switch Mode =
Configuration State = Active
NPA Bidirectional
Magenta: Spare
MS
Blue: Main
Protection
Block Protection Unit
Condition
- Standby
STM Port - Active
Priority Protection Unit

Status
- H: High MS-Trail
- L: Low Physical Connection - nr: no request
Protection Unit Status: Protection Unit Condition:
= no request ● = active
= lockout (only possible on Spare) ● = standby
= forced
● = unknown
= manual
Priority (meaningful only for MSP 1:n)

= do not revert ● H: High
● L: Low
= “auto switch” or “auto switch pending”
= remote indication

ss Issue 03
4.3 MSP 1+1 NPA
Synchronize
2. Select the Protection Block
3. Synchronize
1. To align the information …


ss Issue 03
4.3 MSP 1+1 NPA
Protection status
NPA
View
Protection Unit Status:
remote indication - auto switch
Alarm on
the Main
PC
NPA list

In this example, “Protection Switch Mode” is bidirectional; thus, the active line is the Spare one for
both the NEs.
Possible values for the attributes
Switch status
SwitchOff
SwitchOn
Unknown
Operator Command
Not Present
Present
Unknown
Traffic position
onWorking
onProtecting
Unknown

ss Issue 03
4.4 MSP 1:n NPA


ss Issue 03
4.4 MSP 1:n NPA
General concept
(MSP 1:n) = (Linear colon)

Normal condition
(Dual ended) = (Bidirectional)
Failure condition
NE 1 NE 2
NE 1 NE 2

1:n (n=15 max) linear protection without extra traffic for STM-N interfaces.
One section is used as spare resource to protect one of the main sections when in failure.
Switching criteria are: LOS, LOF, MS-AIS, Excessive BER (B2), Signal Degrade (B2) or card failure.
Note that each STM-1 electrical stream can be protected by an optical stream and vice versa.
Only dual ended (bidirectional) mode is supported.
Switching signaling is carried over the APS channel (K1 and K2 bytes), using the K-byte protocol.
Only REVERTIVE mode is supported: the WTR value is selected in the range from 1 minute to 15
minutes (step = 1minute).
WTR: wait to restore time.

ss Issue 03
4.4 MSP 1:n NPA
Creation
1. Choose 2. Choose
Linear-colon Bidirectional
3. Next

ss Issue 03
4.4 MSP 1:n NPA
Creation [cont.]
4. Choose the MAIN

5. Choose the SPARE

Physical Connection
6. Apply
7. Implement the NPA: the SPARE Physical

Connection must have no HO-Trail/Path
The priority of all the channels is automatically set to High. The user can change it to Low onwards.
See next slides.

ss Issue 03
4.4 MSP 1:n NPA
NPA View
The NPA view can be got by selecting the NPA in any views (NPA
list, Physical Connection structure, …) and then “Search NPA
View”
NPA Revertive MS Prot. Block

Configuration Protection
State = Active Switch Mode =
MS
Bidirectional
Protection
Block
Magenta: SPARE
Blue: MAIN
STM Port
Protection
Unit Condition
Protection
Priority MS-Trail Unit Status
Physical Connection
Possible Protection Unit Status: Possible Protection Unit Condition:
= no request ● = active
= lockout (only possible on Spare) ● = standby
= forced ● = unknown
= manual
Priority (meaningful only for MSP 1:n)
● H: High
= “auto switch” or “auto switch pending”
● L: Low
= remote indication
= wtr running

ss Issue 03
4.4 MSP 1:n NPA
Priority – WTR - Synchronize
To modify WTR and Synchronize:
1. Select protection block
2. Actions …
1...15min
To modify the priority:

1. NPA must be implemented
2. Select a MAIN physical
connection
3. Actions Change SDH Priority
4. High or Low
Priority
- H: High
- L: Low
Priority:
The user can specify a priority for the Main physical connections. The allowed values are High and
Low. The default priority, set at NPA creation time, is equal to High.
In case of concurrent alarms of the same type, such as Signal failure or Signal Degraded, on two Main
physical connections, the protection will apply to the one with higher priority.
The feature is applicable only if it is supported by both the NEs involved in the protection scheme.
The priority can be modified only if the NPA is “Implemented”.
WTR (wait to restore time):

It ranges from 1 minute to 15 minutes (step = 1minute).

ss Issue 03
4.4 MSP 1:n NPA
Modify
Modify NPA:
• for Defined NPA (the protection is NOT
operational)
• to change unidirectional/bidirectional
• to add/remove/change Physical Connections
“Add Physical Connections” and “Remove Physical Connections”:

• for Implemented NPA (the protection is operational)


ss Issue 03
4.4 MSP 1:n NPA
Add physical connections to an implemented NPA
1. NPA must be
Implemented
2. Select the NPA

Actions Modify
Add Physical
Connections
3. Select further
Additional MAIN physical
connections
Current

To launch this window, it’s possible to right click a Physical Connection Actions NPA Add to NPA

ss Issue 03
4.5 2F MS-SPRing NPA


ss Issue 03
Creation
4. Select the Physical

1. Actions Connections
SDH
Create NPA
2. 2F-MS-SPRing
5. Apply
3. Next

When a LO Path is allocated into a 2F MS-SPRing by 1350OMS-SDH, it is not said that the same time slot
(TU3 or TU12) is used over all the chosen route. The “Time Slot Interchange” attribute allows to inhibit
or not this changing of time slot into the NPA.
The Time Slot Interchange attribute can be characterized as:

Allowed: Paths/Trails are allocated allowing the interchanging of time slot in their routes.
Preferable avoided: the time slot interchange is still allowed, but Paths/Trails are allocated keeping
the same time slot, if possible.
Forbidden: the time slot interchange is not allowed, that is Paths/Trails are allocated keeping the
same time slot in the NPA, if possible; if not possible, the allocation fails.
N.B.: at HO level the time slot interchange in a 2F MS-SPRing NPA is always forbidden.

ss Issue 03
Implementation
Checks are performed during the implementation to verify that no
HO-Trail/Path is present on the Physical Connections.
NPA list By implementing the NPA, the protection is configured in the NEs.
1. To retrieve the NPA
list: Search OTN
NPAs
4. To align the info:

select the node
NPA View Actions Manage
2. To implement the Switch Synchronize
NPA: select the NPA
Actions Ring’s nodes
Configuration
Implement
3. Select the NPA

Search NPA View

The 2F MS-SPRing protection is dealt in detail in “2F MS-SPRing” module.

ss Issue 03
NPA indication
NPA icon is also put in
the routing display of
the HO-Trails and Paths
1. Select SDH as over the Physical
Technology Connections of NPA
NPA
icons
Map PC
Structure


ss Issue 03
4.6 Upload Protection Schema


ss Issue 03
Rationale
MSP and 2F MS-SPRing protection schemes can be completely managed

by 1350OMS-SDH using the NPA feature.
Two situations may exist related to their management:
Protection scheme configured and managed by means of 1350OMS-SDH

See previous slides.
Protection scheme already configured in the equipment (by means of

1350OMS-EML or Craft Terminal) and afterwards managed by means of
1350OMS-SDH
the involved resources (Nodes, Physical Connections,…) are not yet taken in charge
by 1350OMS-SDH.
the Protection schema was configured on the NEs by means of 1350OMS-EML.
Take in charge the involved resources (Nodes, Physical Connections,…) by means of
1350OMS-SDH.
Upload the Protection scheme. The relevant NPA is created.


ss Issue 03
Operation
1. Implement all the Physical

Connections involved in
the Protection scheme
2. Select: Actions OTN

Upload Protection Schema
3. Choose the NPA
Type
4. Put here the Nodes:
- drag/drop the Nodes from the
Node list
OR
- right click the Node Send To
Upload Protection Schema
Nodes
The discovered NPA is automatically assigned a User Label: AutoDisc…


ss Issue 03
Answer the Questions
1. Which is the scope of NPA?
2. Which are the objects that characterize an NPA?
3. Is the NPA to be defined during the Sub-Network creation, physical

connection creation or later?
4. Is it possible that a Node be involved in more than one NPA?


ss Issue 03
Exercise
SNCP:
Create an homogeneous ring
Create an SNCP NPA
MSP 1+1:
Create a pair of homogeneous Physical Connections
Create a “Linear plus” NPA
Open the NPA View and investigate the protection status
Select an already created NPA and:

Open the NPA View
List the Physical Connections belonging to the NPA
List the Nodes associated to the NPA


ss Issue 03
End of Module
Network topology


ss Issue 03
@@SECTI
Section 2
System Operation
Module 3
HO Trail management
3JK Issue 03
1350OMS

3JK Issue 03
Blank Page

System Operation HO Trail management
Document History

3JK Issue 03
Module Objectives
Create one-hop HO-Trails by configuring the payload

Create one-hop and multi-hop HO-Trails by means of the relevant wizard
Manage the HO-Trails


3JK Issue 03


3JK Issue 03
Page
1 Introduction on HO-Trail 7
2 HO-Trail by Payload Configuration 11
3 HO-Trail creation wizard 15
4 Operation with HO-Trail 21

3JK Issue 03

3JK Issue 03
1 Introduction on HO-Trail


3JK Issue 03
HO-Trail life cycle
Network resources are available
in the 1350OMS’s database
User sets the trail’s Create Remove
attributes: end-nodes,
user label, protection, … DEFINED blu
Only 1350OMS’s DB is concerned e
User can check the trail’s attributes
User can assign Constraints (optional)
Route selection over the Allocate Deallocate
resources in 1350OMS’s DB
ALLOCATED
Only 1350OMS’s DB is concerned ma
gen
The Trail’s route is available ta
User can inspect the selected resources:

Nodes, Physical Connections, HO LCs
The configuration in Implement Deimplement
the 1350OMS’s DB is IMPLEMENTED
downloaded to NEs.
HO cross-connections are effective in NEs
if the LO payload has been specified gre
en
User can set/modify the payload
User can put the trail “In service”
Defined: the HO-Trail’s attributes (end-nodes, CAPs, user label, protection,…) are set. The user can
assign Constraints to the Defined HO-Trail, that is the resources (HO CTPs, Physical Connections, Nodes,
…) the HO-Trail is to use. If the user has specified HO CTPs in the creation wizard, the HO CTPs are
reserved for the addressed HO-Trail; these HO-CTPs are not available for the creation of further HO-
Trails.
Allocated: the resources accomplishing a route crossing the SDH Network are selected for the HO-Trail
into the 1350OMS’s database (for example Physical Connections, HO CTPs, HO Link Connections) and the
suitable Connections in Topology (SNC - Sub Network Connections) are provided. If the user has not
specified any constraints, 1350OMS-SDH automatically chooses the suitable resources. The HO-Trail’s
route can be inspected.
Implemented: all the information is sent to the NEs. If the LO payload has been specified, the HO cross-
connections are set-up in the NEs where required. HO-Trail is operational. The HO-Trail’s “Service
State” can be set to “In service”; it’s useful from alarm management point of view. 1350OMS-SDH’s
Alarm Surveillance handles two different alarm sub-lists: a sub-list “LO-HO Trail In Service” and a sub-
list “All LO-HO Trails”.
Instead of applying step-by-step the above flowchart, the HO-Trail’s Configuration State can be
modified also as follow:
An allocated HO-Trail can be directly removed.
An implemented HO-Trail can be directly removed unless it contains allocated, implemented or
commissioned Paths.
To deimplement an HO-Trail, it must be payloaded as AU4 first.
Implementation: the NE’s database is concerned unless the node’s attribute “Configure Download
Status” is set to “Disabled”.
3JK Issue 03
Highlight on HO-Trail objects
LO Path
LO Link Connection
HO Trail (2 hops)
MS Trail MS Trail
Payloa Physical Physical Payloa
d Connection Connection d
L H M P P M H H M P P M H L
PDH N O C O S o o S O O S o o S O C O N PDH
A A r r r r A A
Port P C P C T t t T C C T t t T C P C P Port
T T T T T T T T T T
P P P P P P P P P P
MSOH
MSOH
MSOH
MSOH
RSOH
RSOH
RSOH
RSOH
STM-N STM-N
TUn
TUn
AU4
AU4
AU4
AU4
VC4
VC4
VCn
VCn
PPI
Pm
Pm
PPI
SPI
SPI
SPI
SPI
… …
Ei
Ei
X X X X X
NE 1 NE 2 NE 3
HO: Higher Order Higher Order Ei: i=1 for 2Mb/s; i=3 for 34Mb/s
LO: Lower Order Pm: m=12 for 2Mb/s; m=31 for 34Mb/s
pass-through VCn-TUn: n=12 for 2Mb/s; n=3 for 34Mb/s
NAP: Network Access Point
CTP: Connection Termination Point PPI: PDH Physical Interface
CAP: Client Access Point (also said HO TTP) MSOH: Multiplex Section Over-Head
TTP: Trail Termination Point RSOH: Regenerator Section Over-Head
: Connection in Topology SPI: SDH Physical Interface

3JK Issue 03
Two methods for creating HO-Trails
Payload configuration: (only for HO-Trails between adjacent nodes)
During Physical connection manual creation: in this case the user can specify how
many AU4s will be used at lower order level. During Physical connection
implementation the HO-Trail(s) will be configured by default as TU3/TU3/TU3.
From HO Link Connection: by defining the HO LC’s payload, AU4 by AU4. In this case
the 1350OMS-SDH automatically creates the HO-Trail over the HO LC and provides the
chosen payload configuration.
HO-Trail creation wizard:

The user selects the two end-nodes and optionally the HO CTPs. Some parameters must
be defined. The user can assign constraints for the route.

Payload configuration:
These two methods allow to create only one-hop HO-Trails, that is HO-Trails between adjacent nodes.
The HO-Trail’s label is automatically created by the system taking into account the NEs’ location
names inserted at the NE creation. The default payload type can be modified later on, for example to
TU12/TU12/TU3.
Manual creation of HO-Trails by means of the wizard:

Constraints can be attached by the user to a Defined HO-Trail in order to use specific network
resources (e.g.: nodes, physical connections, AU4#…). These constraints will be taken into account by
the routing algorithm.
N.B.: after the first configuration of the HO-Trail’s payload (at Lower or Higher Order), 1350OMS-SDH
will automatically manage the payload configuration of the HO-Trail (Dynamic Payload). In this way,
each time a new Path requires a specific transport rate (TU12 or TU3), 1350OMS-SDH automatically sets
the correct payload creating or modifying the HO-Trail’s payload. For example, by implementing a
2Mb/s Path over a trail whose payload is AU4, the trail is automatically payloaded as TU12/TU12/TU12.
The dynamic payload can be enabled/disabled by means of an environment parameter (ask the system
administrator). In particular:
if disabled, all payload changes must be done explicitly by the user.
if enabled, a payload change can be performed either automatically on a Path allocation or manually
by the user; anyway, the payload manually changed, can be again automatically changed when
necessary.

3JK Issue 03
2 HO-Trail by Payload Configuration


3JK Issue 03
From HO Link connection
1. Open the Physical

Connection Structure
2. Select the HO Link

Connection (au4)
Ho Cfg
Lo Cfg
This procedure can be used to:

• create and payload an HO-Trail 3. Actions Payload Structure
Modification Ho Cfg or Lo Cfg
• modify the payload of an
already created HO-Trail The HO-Trail is implemented and payloaded
An HO LC payloaded at LO level can be put in HO rate by choosing AU4 in the Lo Cfg options.
The payload modification is accomplished only if the new payload is not going to impact
allocated/implemented/commissioned Paths.
Contiguous concatenation
AU4-4C, AU4-16C, AU4-64C
Example: an STM16 frame containing one AU4-4C (AU4#1 to #4 concatenated) and 12 normal AU4s
(AU4#5 to #16).
As far as Alcatel-Lucent NEs are concerned:
It is available, for example, in some OMSN, ION and 1850TSS pieces of equipment.
To check whether it is supported by the NE: select the HO LC open its properties check the
attribute “conc. AU4 supported”.
It is used to transport IP or ATM signals (to set up concatenated paths).
The AU4s are concatenated following fixed grouping rules:
AU4-4C is made of four adjacent AU4s, the first being #1, #5, #9, #13, …. For issuing the
concatenation command, the user is free to choose any AU4 among the four that will be
concatenated.
AU4-16C is made of sixteen adjacent AU4s, the first being #1, #17, #33, #49. For issuing the
concatenation command, the user is free to choose any AU4 among the sixteen that will be
concatenated.
AU4-64C is made of sixty-four adjacent AU4s, the first being #1. For issuing the concatenation
command, the user is free to choose any AU4s among the sixty-four that will be concatenated.
If the setting of a concatenated payload fails, select the MS-Trail right click Actions
Configuration “Synchronize AU4-nC Support”.
3JK Issue 03
Trail Structure
Payload: tu12-1tu12-tu3
Node
HO-
Trail Vc4 (CAP)
Hops
Protection indication
(none: not protected)
Working state
tu12 LO Link Connection 1. To get the Trail

05/2/1.3 Structure:
Select the trail Search
AU4/TUG3/TUG2.tu12
Trail Structure
The HO-Trail’s User Label is set automatically by the system by appending the two terminal NEs’
Location Names and the suffix VC4Sx. Example:
NE A’s Location Name = Florence
NE B’s Location Name = Milan
x: the HO-Trail being created is the xth HO-Trail created by means of the “During the Physical
Connection manual creation” or “From HO Link connection” procedures on any Physical Connections
between the two Nodes.
HO-Trail’s User Label = Florence-Milan VC4S7

3JK Issue 03
During the Physical Connection manual creation
Step 2 of Physical Connection manual creation procedure
PC
Structure
HO Link Connection
HO-Trail
Payload
1. “Preserve Au4
Concatenation”
must be False
When the PC is
implemented, the HO-
Trails are created, 2. Set “Initial Number of Au4 at LO”
implemented, and equal to the quantity of Au4s to
payloaded structure as Tu3/Tu3/Tu3.
The Au4s payloaded at LO start from the Au4#1, up to the chosen Au4 number. For example, if the
chosen number is 2, the Au4s payloaded at LO are the Au4#1 and the Au4#2.
The default payload is Tu3/Tu3/Tu3.
The Au4’s payload can then be changed manually by the user or automatically by the dynamic payload
algorithm.

3JK Issue 03
3 HO-Trail creation wizard


3JK Issue 03
Start the wizard
1. Start the wizard. There are several ways to do it:

• From map: select at least a node Actions OTN
Create Create Trail
• From the top bar menu: Actions OTN Create Trail
HO-Trail to create


3JK Issue 03
Configuration
1. Set the User Label

2. It refers to manual (no) or
automatic (yes) allocation
and implementation.
• yes:
• no constraint can be given
prior to allocating the trail
• payload must be defined
• No:
• constraint can be given
• payload must be defined
later on
3. Quantity: number of HO-

Trails to create. It can be
set if no CTP is specified.


3JK Issue 03
Configuration [cont.]
4. Choose the Nodes
5.CTP selection
• it is possible if Quantity=1
• it’s optional
• it allows to specify the
port/CTP
• if the user doesn’t specify
any CTPs, the first free CTP
is taken

If you are creating a one-hop trail and you want to specify the CTPs, the two CTPs must have the same
position (AU4’s number).

3JK Issue 03
Protection - PM
Meaningful only for Trails crossing

4F MS-SPRing topologies “with alarms” enables the
AU4-AIS visualization
Automatic PM Creation (true, false): if set to true,

a 24h QoS PM measure is automatically created
and activated over the trail on its implementation.
Automatic PM Purge (true, false): if set to true, the created PM

is automatically purged when the trail is removed. Its setting is
available only if “Automatic PM Creation” is set to true.
MS Protection usage profile:

normal: to be selected for Trails not crossing 4F MS-SPRing or for Trails crossing a 4F MS-SPRing that
must be allocated using High Priority resources.
protecting preferred: applicable to Trails crossing a 4F MS-SPRing interconnected with an SNCP ring.
Low Priority resources are used during allocation in 4F MS-SPRing.
protecting only: applicable to Trails allocated inside 4F MS-SPRing only: only Low Priority resources
must be used.
Routing:
NPA Main & Spare Factor:
During the Spare route calculation, the “NPA Usage Cost” is reduced by this factor.
It indicates how strongly Main & Spare have to be forced to use the same NPA.
The bigger it is set the more the cost of the routes internal to the NPA used by the Main is
decreased, so attracting the Spare.
It is a percentage value and can be set from 0% to 100%. Default value is 100%. If 0 it has no effect.
MS-SPRing D&C Factor:
Meaningful for SNCP or D&C SNCP HO-Trails traversing MS-SPRing.
It is used to encourage the routing of the Spare to be the most overlapped as possible with the Main
inside MS-SPRing.
If the Spare goes on the Physical Connection in the same direction as the Main, the Physical
Connection’s cost is decreased by 0.85*MS-SPRing D&C Factor.
The Physical Connection’s cost where the Spare overlaps the Main is reduced to zero.
If the MS-SPRing D&C Factor is equal to 0 it has no effect.
CP Restoration: it concerns ASON.
3JK Issue 03
Blank Page


3JK Issue 03
4 Operation with HO-Trail


3JK Issue 03
Routing Display
1. To get the HO-Trail’s Routing Display: Defined Trail
Select the trail Search Routing Display
Performance Monitoring
HO Trail Hops
Implemented Trail
HO CTP (Au4)
CAP (VC4)
Green Line: Connection In Topology
Node
The blue Line is the HO Link Connection. It’s name is given by
MS-Trail & Au4’s number Bidirectional
point

When the HO-Trail is Defined, the network’s resources (HO Link Connections, …) are not yet assigned.
The user can just check if the Nodes, Ports, CAPs are the desired ones.
When the HO-Trail is Allocated:
the network’s resources (HO Link Connections, …) are assigned.
the payload is AU4.
the color of the “Connection In Topology” line is magenta.
Performance Monitoring icon:
“24Q” stands for Granularity = “24 hours” and Objective = “Quality of service”.
The border of the CAPs (VC4s) is purple because the Performance Monitoring is active.

3JK Issue 03
Object’s properties
Right click an object

(i.e. CAP) Properties


3JK Issue 03
Trail allocation and implementation
1. Several ways to retrieve the trail list. Three of those are:

- From Physical Connection: Search HO Trails
- From end-node: Search OTN Starting/Ending Trails
- From Sub-Network: Search OTN Trails
Trail list
Configuration State
2. If the trail is just

Defined, it must be first
Allocated and …
LYFE CYCLE
DEFINED
ALLOCATED
3. … then Implemented
IMPLEMENTED


3JK Issue 03
Payload
1. Note that if the trail is
manually allocated and
implemented, the
payload is AU4.
2. The user must

specify the payload
LYFE CYCLE
DEFINED
ALLOCATED
IMPLEMENTED
payload definition


3JK Issue 03
In Service
1. To set the HO-Trail’s “Service state” to
“In Service”: select the implemented LYFE CYCLE
trail Actions Set Service State
DEFINED
ALLOCATED
2. Configure the IMPLEMENTED

Service State
Set in Service

The HO-Trail’s “Service State” can be set to “In Service”; it’s useful from alarm management point of
view. 1350OMS-SDH’s Alarm Surveillance handles two different alarm sub-lists: a sub-list “LO-HO Trails
In Service” and a sub-list “All LO-HO Trails”.
By deimplementing an HO-Trail whose “Service State” is “In Service”, the HO-Trail gets “Allocated”
with “Service State” equal to “Not In Service”.

3JK Issue 03
Trail deimplementation, deallocation and removal
Step-by-step procedure Fast removal
LYFE CYCLE LYFE CYCLE

No trail No trail
Remove 4
DEFINED DEFINED Remove
Deallocate 3
ALLOCATED ALLOCATED Remove
Deimplement 2
IMPLEMENTED IMPLEMENTED Remove
Without Paths
With or without payload.
Restore the Without Paths.
1
Payload to
AU4

• To deimplement an HO-Trail, its payload must be set to AU4 first: select the trail Actions Lo Cfg
AU4. If the HO-Trail contains allocated, implemented or commissioned Paths, it’s not possible to set the
payload to AU4.
• HO-Trail can be removed when:

- it’s defined or allocated
- it’s implemented: in this case it must not contain allocated, implemented or commissioned Paths.

3JK Issue 03
Exercise 1: HO-Trail creation
1. Create an STM-N Physical Connection directly structuring one Au4 at

Lower Order.
2. Open a Physical Connection Structure and do the following payload
configuration:
STM-1: 21xTU12, 2xTU3
STM-4: 42xTU12, 1xTU3; 3xAU4
3. Create an unprotected HO-Trail between two nodes setting the
“Allocate, implement and payload” parameter to “no”. Allocate and
implement the trail. Structure the trail to TU3/TU3/TU12.
4. Create an unprotected HO-Trail between two nodes setting the
“Allocate, implement and payload” parameter to “yes” and “Payload
Structure” parameter to TU3/TU3/TU12.


3JK Issue 03
Exercise 2: Physical Connection Structure
Referring to the picture, where are …

Trails
Payload
Physical connection


3JK Issue 03
End of Module
HO Trail management


3JK Issue 03
@@SECTI
Section 2
System Operation
Module 4
Path management
3JK Issue 03
1350OMS

3JK Issue 03
Blank Page

System Operation Path management
Document History

3JK Issue 03
Module Objectives
Set up PDH Paths

Set up Ethernet Paths and manage their attributes: routing, LCAS, bandwidth,
flow control
Set up DVB Paths
Set up ATM Paths
Create Paths between a real NE and an External Network


3JK Issue 03


3JK Issue 03
Page
1 Introduction on Path 7
2 PDH Path 15
3 Ethernet Path 33
3.1 Ethernet Path’s objects and routing 35
3.2 Prior to creating the Path 41
3.3 10-100Mb, 1Gb, 10Gb Rate Adaptive Paths 47
3.4 EVPL Path for 1678MCC 59
3.5 Bandwidth modification 71
3.6 LCAS Management 81
3.7 Flow control 85
4 DVB Path 87
5 ATM Path 95
6 Not Terminated Path 107

3JK Issue 03
Page

3JK Issue 03
1 Introduction on Path


3JK Issue 03
Types of Path
Path: it’s the service provided to the customer. The Path is usually
established across the network between two or more NEs to which the
customer’s equipment is connected.
1350OMS-SDH permits to set up different types of Path:

PDH (2Mb/s, 34Mb/s, 45Mb/s, 140Mb/s)
SDH (AU4, AU4-xC)
ATM (over PDH or SDH signals)
Ethernet (10Mb/s, 100 Mb/s, 1Gb/s, 10Gb/s over SDH signals)
Data (FDDI, Digital Video, ESCON, Fiber Channel, … over SDH signals)
These Paths are suitable for dedicated hardware. For example:

PDH boards in OMSN for PDH Paths
ATM boards in OMSN for ATM Paths
Ethernet boards in 1850TSS for Ethernet Paths
4XANY board in OMSN for DATA Paths
SDH Path is between two External Networks and is accomplished by HO-pass-through connections in
all the traversed NEs. HO means AU4, AU4-4C, AU4-16C, AU4-64C. The suitable AU4 contiguous
concatenation is automatically configured by 1350OMS-SDH in the NEs.
OMSN: 1642EM, 1660SM, ...

1850TSS: 1850TSS320, 1850TSS100, ...

3JK Issue 03
PDH LO Path’s objects
LO Path
MS Trail MS Trail
Phys. Phys.
Conn. Conn.
PDH NA
A
MSOH
MSOH
MSOH
MSOH
RSOH
RSOH
RSOH
RSOH
TUn
TUn
TUn
AU4
TUn
AU4
AU4
AU4
VC4
VCn
VC4
VC4
VC4
VCn
Pm
PPI
PPI
Pm
SPI
SPI
SPI
SPI
… … … …
Ei
Ei
X X X X X X X
NE 1 NE 2 NE 3
HO: Higher Order
Lower Order Ei: i=1 for 2Mb/s; i=3 for 34Mb/s
LO: Lower Order
This slide features a LO PDH Path across three Nodes.

The end-points of the Path are said NAPs. NAPs reside in the boards to which the customer’s equipment
is connected.
LO Path (VC12) needs the LO Link Connections (TU12) of HO-Trails (VC4).

3JK Issue 03
Available NAPs
1. First of all, verify that the NAPs
are available. To open the NAPs NAPs are the
list, select a Node and then: Path’s end-points
• Search OTN NAPs
Not
• or click the icon Connected:
the NAP is
involved in a
defined Path
Busy: the NAP is

involved in an
allocated,
implemented or
commissioned Path
Idle: the NAP is

free for creating a
new Path
2. If the NAPs are not available in the 1350OMS-SDH’s database, they

must be retrieved from the NEs.
Select the Node Actions OTN Configuration Upload NAPs
NAPs are the start/end-points of Paths. A NAP (Network Access Point) is the logical representation in
the 1350OMS-SDH of:
VC12, VC3, or VC4 for PDH or ATM traffic.
g-MAU or VCG (Virtual Concatenation Group) for Ethernet or data traffic.

3JK Issue 03
Terminated and Not Terminated Paths
Terminated Path: both end-points (NAPs) belong to
NEs that are managed by 1350OMS-SDH.
Path
Network managed
NE
by 1350OMS-SDH
External Network
Boundary NE Ext. Ext.

Net. Net.
HO-Trail
Not Terminated Path: at least one end-point

(NAP) belongs to an External Network that stands Ext.
Net.
for a NE that is not managed by 1350OMS-SDH.
Not Terminated Path enters/exits the network made of NEs managed by
1350OMS-SDH through “Boundary NEs”. Boundary NE is not specified by Physical
Connections; for example, in case of LO Path, the Boundary NE is the NE that
contains the end-point of the HO-Trail starting in the External Network.
Boundary NE:
it is not specified by Physical Connections; that is the Boundary NE is not always the NE that shares
the Physical Connection with the External Network.
it contains the last LO CTP (in case of LO Path) or the last HO CTP (in case of HO Path) close to the
External Network.

3JK Issue 03
Path life cycle
Network resources are available in

the 1350OMS’s database
User sets the Path’s attributes:
end-nodes, rate, NAPs, user Create Remove
label, protection, … DEFINED
1350OMS’s DB is concerned.
blu
User can check the Path’s attributes. e
User can assign Constraints (optional).
Route selection over the
resources in 1350OMS’s DB Allocate Deallocate
ALLOCATED ma
The cross-connections 1350OMS’s DB is concerned. gen
ta
that accomplish the Path User can inspect the selected resources:
are downloaded from the Nodes, HO-Trails, LO LCs,…
NEs’ cross-
1350OMS’s DB to the NEs
Implement Deimplement connections
are deleted
Partially IMPLEMENTED IMPLEMENTED gre
• For protected Paths when the Cross-connections are effective in NEs en
Main is implemented whereas the
Spare is allocated Commission Uncommission
• For concatenated Data Paths COMMISSIONED
when all the Server trails are not ligh
active Some Path’s configurations can not be modified. tg
r ee
Path’s “Service State” is set to “In service”. n

The Path’s “Configuration State” can be: defined, allocated, implemented, commissioned.
Defined: the Path’s attributes (NAPs, user label, protection, rate,…) are set. The user can assign
Constraints to the Path, that is the resources (LO CTPs, Physical Connections, Nodes, …) the Path is
to use. The end-points (usually the end-points are NAPs; for not-terminated Paths, the end-points
can be CTPs) are reserved for the addressed Path and so they are not available for the creation of
further Paths. The NAP’s “Idle Indicator” is equal to “Not Connected”. In case of some Data Paths
(e.g. 1Gb/s Rate Adaptive Path for PP10MS in 1850TSS-320), the VCG ports are configured in the
NEs.
Allocated: the resources accomplishing a route across the SDH Network are selected for the Path
into the 1350OMS’s database (for example Physical Connections, LO Link Connections, HO-Trails)
and the suitable Connections in Topology (SNC-Sub Network Connections) are provided but not
configured in the NEs. If the user has not specified any constraints, 1350OMS-SDH automatically
chooses a set of suitable resources. The Path’s route can be inspected.
Implemented: all the information is sent to NEs in order to set up the NEs’ internal Cross-
Connections. The Path is operational. This Configuration State is meant for testing the Path.
Commissioned: this Configuration State is meant for giving the service to the customer. The Path’s
“Service State” is set to “In service”; it’s useful from alarm management point of view. 1350OMS-
SDH’s Alarm Surveillance handles two different alarm sub-lists: a sub-list “Path In Service” and a
sub-list “All Paths”. Some operations are forbidden; for example: “add protection”, loopbacks,
“trace identifier configuration”.
Instead of applying step-by-step the above flowchart, the Path’s Configuration State can be modified
also as follow:
An allocated or implemented Path can be directly removed whereas a commissioned Path can not
be removed.
Implementation: the NE’s MIB is concerned unless the Node’s attribute “Configure Download Status”
is set to “Disabled”.

3JK Issue 03
“Create Path” wizard Step 1: full window
If the Path has to use LO resources, To start the Path creation:

first create the HO-Trails • from Nodes Actions OTN
Create Create Path
• from main tool-bar: Actions
OTN Create Path
See next
slide
Optional


3JK Issue 03
“Create Path” wizard Step 1: Upper part of the window
Service Type
Service Protection
Path Type Sncp Type
Rate (PDH)

MS Protection usage profile:

normal: to be selected for:
Paths not crossing 4F MS-SPRing.
Paths crossing a 4F MS-SPRing that must be allocated using High Priority resources.
protection preferred: applicable to Paths crossing a 4F MS-SPRing interconnected with an SNCP
ring. Low Priority resources are used during allocation in 4F MS-SPRing.
protection only: applicable to Paths allocated inside 4F MS-SPRing only: only Low Priority resources
must be used.
SNCP/I: Sub Network Connection Protection Inherent

SNCP/N: Sub Network Connection Protection Not-intrusive
SNCP Type: SNCP/I with or without AIS alarm visualization (AU-AIS or TU-AIS according to the service
rate) or SNCP/N where supported. SNCP/N is degraded to SNCP/I where not supported.
D&C: Drop & Continue. It’s a protection that is suitable for Paths that cross two rings.
In Rings: a switch that accomplishes a protected cross-connection is created in every Node that is an
exit or an entrance of a ring along the Path’s route. In the parts of the Path’s route that
interconnect the rings the protection is not established. “In Rings” behavior requires that the ring be
set as SNCP NPA (Network Protection Architecture).

3JK Issue 03
2 PDH Path


3JK Issue 03
2 PDH Path
Test bench
Path to create:
between the Nodes 164B and 165B
passing through 63B
trail_63-164 trail_63-165
PDH 2Mb/s
HO level HO-Trails required
bidirectional (no matter Sink and
Source)
Path_164-165 terminated Path
Source and Sink Nodes contain the
NAPs

Source and Sink:

In case of Unidirectional Path, the Source Node is the entrance for the client’s signal from the SDH
network point of view, whereas the Sink Node is the exit for the client’s signal.
In case of Bidirectional Paths, no matter which Node of the two end-Nodes is selected as Source
and which one as Sink.
Source and Sink are two possible values of the NAP’s “Used Direction” attribute.

3JK Issue 03
2 PDH Path
“Create Path” wizard Step 2
“Backup”: for X 1. End Point inside SDH: set “Yes” because
and Y Paths we are creating a Terminated Path
2. Choose the
Sink and the
Source Nodes
3. It is not mandatory to select the NAPs.

If the NAP is not selected by the user,
1350OMS-SDH uses the first idle NAP. 4. Next
Multiple Path creation: by setting it to Yes, Paths in number of Quantity are created. The Paths are
automatically given a name composed of the Path’s User Label followed by an incremental number
that depends on “Starting Suffix”.
Example:
User Label=MyClient
Quantity=3
Starting Suffix=11
Specify Multiple Path Naming=Append number
So:
First Path’s user label= MyClient11
Second Path’s user label= MyClient12
Third Path’s user label= MyClient13
Backup: it’s suitable for X and Y Paths. These Paths have respectively four and three end-points. X
and Y Paths are SNCP Paths with respectively one and two end-points not belonging to the NEs
managed by 1350OMS-SDH.

3JK Issue 03
2 PDH Path
“Create Path” wizard Step 3: Configuration
Configuration

Allocation Rule:
User: the Path is created and left as Defined.
Automatic: the Path is created and promoted to Allocated.
Implement Rule:
User: the Path is promoted from Allocated to Implemented upon user command.
Automatic: the Path is promoted from Allocated to Implemented as soon as it is Allocated.
Allocation resources: it refers to the objects used during allocation (all objects, not alarmed
objects).
Automatic PM Creation: to enable the Performance Monitoring QoS 24 hour-measure creation and
activation at Path implementation (default = False).
Automatic PM Purge: its configuration is available only if “Automatic PM Creation” is set to True. If
“Automatic PM Purge” is set to True, the created measure is automatically purged on Path removal.
Show created Path(s): if set to Yes, the Paths’ routing displays are automatically opened.

3JK Issue 03
2 PDH Path
“Create Path” wizard Step 3: Alarm
Alarm

Alarm tab: its parameters are dealt deeper in “Alarms” module.

Propagation Rule: the user can select the Path status in which the NE’s alarms are delivered to
1350OMS.
Client/Transport alarm enabling rule: the user can select the Path status in which the
client/transport NE’s alarms are enabled or enable them manually.
If the user keeps the default settings, the Path’s alarms are enabled in the NE and are delivered to
1350OMS on Path implementation.

3JK Issue 03
2 PDH Path
“Create Path” wizard Step 3: Routing, LCAS, CP Restoration
Routing
Parameters taken into account

by the Routing algorithm
LCAS
LCAS is suitable for Virtual
concatenation that is for some
kinds of Path (Ethernet, MPLS,…)
CP Restoration
It concerns ASON
Do Apply
NPA Main & Spare Factor:

During the Spare route calculation, the “NPA Usage Cost” is reduced by this factor.
It indicates how strongly Main & Spare have to be forced to use the same NPA.
The bigger it is set the more the cost of the routes internal to the NPA used by the Main is
decreased, so attracting the Spare.
MS-SPRing D&C Factor:

Meaningful for SNCP or D&C SNCP HO Paths traversing MS-SPRing.
It is used to encourage the routing of the Spare to be the most overlapped as possible with the
Main inside MS-SPRing.
If the Spare goes on the Physical Connection in the same direction as the Main, the Physical
Connection’s cost is decreased by 0.85*MS-SPRing D&C Factor.
The Physical Connection’s cost where the Spare overlaps the Main is reduced to zero.
LCAS (Link Capacity Adjustment Scheme) is a standard protocol that improves Virtual Concatenation.
LCAS allows to:
hitless increase/decrease the quantity of concatenated Virtual Containers.
temporarily remove the Virtual Containers affected by a failure: these Virtual Containers are then
hitless added again after failure recovery.
ASON: Automatically Switched Optical Network
3JK Issue 03
2 PDH Path
Path list retrieval
from Main tool-bar from Sub-Network
from Physical Connection
see next slides

for details
from Node
see next slide

for details
from HO-Trail
Defined Paths are retrieved from Node and Main tool-bar

From main tool-bar: Paths with test port

“test port” is used to monitor the traffic by means of a test instrument. It’s dealt in the
“Troubleshooting tools” module.

3JK Issue 03
2 PDH Path
Path list retrieval [cont.]
from Node


3JK Issue 03
2 PDH Path
Path list retrieval [cont.]
from Physical Connection SNCP protected Path
No failure condition
from a PC along the Spare route
from a PC along the Main route

“Active Path role” concerns ASON.

3JK Issue 03
2 PDH Path
Defined Path
1. Retrieve the Path list: 2. Retrieve the Path The Path is Defined
e.g. from Node 164B routing display: Select because in the
the Path Search creation wizard
Routing Display “Allocation Rule” was
set to “User”
Path
Path_164-165
NAP
(VC12)
PDH
port Port/NAP’s name
Map

When the Path is Defined, the network’s resources (HO-Trails, CTPs,…) are not yet assigned. The user
can just check if the end-Nodes, end-Ports, NAPs and the parameters chosen in the Path creation
wizard are the desired ones.

3JK Issue 03
2 PDH Path
Path life cycle management
To manage the Path life cycle,

choose the suitable commands:
• Allocate / Deallocate DEFINED
• Implement / Deimplement
LIFE CYCLE
• Commission / Uncommission ALLOCATED
IMPLEMENTED
COMMISSIONED
It’s possible to Remove a Path if it is

Implemented, Allocated or Defined. It’s not
possible to remove a Commissioned Path.

Each “Configuration State” has a different color:

Defined blue
Allocated magenta
Implemented green
Commissioned light green

3JK Issue 03
2 PDH Path
Routing Display of an implemented Path
Path’s
alarm
Working State
Double arrow:
Path Bidirectional Path
Straight line: No Path_164-165
protection
Green Line:
Connection
Blue Line:
In Topology
LO LC
Position:
02 / 1 / 1 . 1
PDH NAP LO CTP Au4 Tug3 Tug2 Tu12
port (VC12) (TU12)
Alarms are available for Implemented and Commissioned Paths.

3JK Issue 03
2 PDH Path
Path over 2-hop HO-Trail
HO-Trail
Path

If the Path is using a multi-hop HO-Trail, the icon is placed over the Link Connection. From this
icon, it’s possible to retrieve the HO-Trail’s routing display.

3JK Issue 03
2 PDH Path
Path indication in the Trail Structure
Trail_63-164
tu12
1/1.1
Path_164-
165
Path_164-165

The Path is not shown in the Trail Structure if the Path is Defined.
The Path is shown in all the traversed HO-Trails.

3JK Issue 03
Answer the Questions 1
What are the actions and states in a Path life cycle?
Action: Action:
..................
Action: Action:
..................
Action: Action:
....................
Action: Action:
....................


3JK Issue 03
Fill in the callouts with the kind of the indicated object


3JK Issue 03
Exercise 1: LO-Path creation with NAP selection
Working on any topology made of NEs having 2, 34 or 45Mb/s ports
1. Create an HO-Trail, having the required payload, between the involved

nodes.
2. Create a LO-Path, between two specific NAPs, with the following
parameters:
Protection: None
Allocation Rule: Automatic
Implement Rule: Automatic
3. Commission the Path.
4. Get information to verify that the Path is properly created.
5. Question: what are the involved network resources (Nodes, HO-Trails and
TU12s)?


3JK Issue 03
Exercise 2: HO-Path creation with node selection
Working on any topology made of NEs having 140Mb/s ports or made of

External Networks:
1. Create a 140Mb/s Path between two nodes with the following parameters:
Protection: None
Allocation Rule: User
Implement Rule: User
2. Allocate, implement and commission the Path.
Question 1: what are the involved network resources (NAPs, Nodes and
Au4s)?
Question 2: is it possible to remove a commissioned Path?
3. Remove the Path.


3JK Issue 03
3 Ethernet Path


3JK Issue 03
Blank Page


3JK Issue 03
3.1 Ethernet Path’s objects and routing


3JK Issue 03
NE objects Vs 1350OMS-SDH objects: Data Path
Ethernet Path Not concatenated
LO/HO Link Connection Ethernet Path
Eth NA
N Eth
A
1350OMS-SDH
CTP CTP
Port P SDH P Port objects
Network NE
MAU
MAU
VCn
VCn
TU/AU TU/AU
objects
Ethernet Path
Ethernet Server Link Connection Concatenated
Ethernet Server Trail (channel#1)
Ethernet Path
Ethernet Server Trail (channel#2) (example: VCx-2V)
CAP #1 CTP CTP CAP #1

Eth N N Eth 1350OMS-SDH
A CTP CTP A
Port P P Port objects
CAP #2 CTP SDH CTP CAP #2
VCx #1 TU/AU Network TU/AU VCx #1

TU/AU
TU/AU
MAU
MAU
VCG
VCG
NE
-2V
-2V
VCx #2 TU/AU TU/AU VCx #2 objects

MAU: Medium Attachment Unit.

VCG: Virtual Concatenation Group (e.g. VC12-5V, VC4-7V).
From 1350OMS-SDH point of view, there’s little difference between Data Paths and PDH Paths. Both
Data and PDH signals are mapped into SDH Virtual Containers that are routed over the SDH network.
Data Paths can rely or not on virtual concatenation. If virtual concatenation is implemented, the Path
consists on several Server Trails, one per Virtual Container.

3JK Issue 03
Server Trails: uniform vs diverse routing
NE3 Example for VC12-5V concatenation
#1 #2
Ethernet
Ethernet
#3 #4
10Mb/s
10Mb/s
#5 Uniform
C C C C C Ethernet Path C C C C C routing
N N
NE4
NE1 NE2 “Ethernet Path” with
NE3
TU12-nV transport rate
#1 is accomplished by “n”
#3
Ethernet
Ethernet
Server Trails
10Mb/s
10Mb/s
#5
C C C Ethernet Path C C C
N N
C C NE4 C C
Diverse
NE1 #4 NE2 routing
#2
N NAP (Transport Rate = TU12-nV) C CAP (VC12)
N N Ethernet Path (Transport Rate = TU12-nV) C C Server Trail

STM-N Physical Connection LO Link Connection
Diverse Routing mechanism makes the Server Trails have different routes:
If two routes with enough free bandwidth are available, and whatever their cost is, the 50% of the
Server Trails are put on a route and the other 50% on the other route.
If more than two routes are available and more than two Server Trails are required, the routing
algorithm is likely to apply the 50-50 over two routes approach.
In this way, a fault (e.g. fiber cut) might impact only one route; the rest of the routes provide
anyway a minimum functionality level if LCAS is enabled.
If the network resources are not enough to fulfill the Diverse Routing (for example there’s just one
Physical Connection), the Server Trails could have the same route even if the user enables the
Diverse Routing.
If the network resources are not enough to fulfill the Uniform Routing (for example there’s just one
free TU12 per Physical Connection), the Server Trails could have different routes even if the user
enables the Uniform Routing.
Regardless of the enabled Server Trails Routing (Uniform or Diverse), the user can force the routing
of each Server Trail by means of Constraints. Constraints override the Server Trails Routing
configuration.
The Constraints for the Server Trails must be defined at Path level specifying the “Channel Number”
attribute; “Channel Number” refers to the Server Trail number.

3JK Issue 03
Server Trails: uniform vs diverse routing [cont.]
NE3 Example for VC4-3V concatenation
#1
#2
Ethernet
#3
Ethernet
Uniform
1Gb/s
1Gb/s
C C C Ethernet Path C C C routing
N N
NE4
NE1 NE2 “Ethernet Path” with
NE3 AU4-nV transport rate
#1 is accomplished by “n”
Server Trails
Ethernet
Ethernet
#3
1Gb/s
1Gb/s
C C Ethernet Path C C
N N Diverse
C NE4 C routing
NE1 #2 NE2
N NAP (Transport Rate = AU4-nV) C CAP (VC4)
N N Ethernet Path (Transport Rate = AU4-nV) C C Server Trail

STM-N Physical Connection HO Link Connection

3JK Issue 03
Diverse Routing & LCAS
LCAS (Link Capacity Adjustment Scheme) is a standard protocol that improves
Virtual Concatenation, allowing to:
• hitless increase/decrease the quantity of Server Trails.
• temporarily remove the Server Trails affected by a failure: these trails are then
hitless added again after failure recovery.
Diverse routing; LCAS disabled

#1
Ethernet
Ethernet
#3
“Diverse Routing” + LCAS:
C C C C
NE3
The Path benefits from both “hitless N N
C C NE2
bandwidth modification” and “failure Ethernet Path
NE1 Path is
tolerance” provided by LCAS. #2 down
“Uniform Routing” + LCAS:
Diverse routing; LCAS enabled
The Path benefits mainly from just Ethernet #1
Ethernet
“Hitless bandwidth modification” #3
provided by LCAS. C C C C
NE3
N N
C C NE2
Ethernet Path
NE1 Path and Server
#2
trail are active
Some boards that support LCAS:

GETH-MB (available from 1650SMC/1660SM Rel 4.2, 1670SM Rel 4.3, 1662SMC Rel 2.1)
ES1, ES4, ES16 (available from 1650SMC/1660SM Rel 4.3, 1662SMC Rel 2.1, 1642EMUX Rel 2.1,
1642EMC Rel 1.1)
BCE-ETH (available from 1650SMC/1660SM Rel 4.5, 1662SMC Rel 2.6)
ES64 (available from 1678MCC Rel 4.3)
P4GE, P8GE, P16GE (available from 1678MCC Rel 3.1B)
P2XGE, P4XGE (available from 1678MCC Rel 4.2)
PIMMS (1850TSS-320 Rel 1.4)
PP10MS (1850TSS-320/160 Rel 3.x)
PP10G (1850TSS-100 Rel 3.x)
LCAS can be enabled only if it is supported by the NAPs.

3JK Issue 03
Blank Page


3JK Issue 03
3.2 Prior to creating the Path


3JK Issue 03
Things to know
1. Given a pair of boards between which a Path is to be created, check

first their NAP properties:
NAP Rate
Supported concatenation:
concatenation type
max supported concatenation level
LCAS control
2. Once the NAP properties are known, find out the suitable Paths:
Service Rate
Transport Rate


3JK Issue 03
NAP properties
Concatenation Type:
NAP Rate
• Virtual conc. with LCAS
• LO Packet conc.
• HO Virtual-LO Packet conc.
• HO Virtual conc.
• not supported
2. Select an Ethernet
NAP and retrieve its
properties
Max supported
Concatenation
1. To retrieve the
LCAS Control: NAP list: select the
• Not Available Node Search
• Enabled OTN NAPs
• Disabled (example for 1850TSS-320)
• Fixed Enabled
If the NAPs are not available: select the Node Actions OTN Configuration Upload NAPs.
LCAS Fixed Enabled: only for BCE-ETH.
Examples of LO concatenation:
Concatenation level
Board Details Concatenation type
vc12-nV vc3-nV
ES1 Rel 1.2 on 1…50 1…2 Virtual
Rel 1.2 on, as SMII 1…50 1…2
ES4 Virtual
Rel 1.2 on, as GMII 1…63 1…12
ES16 1…63 1…12 Virtual
ETH-MB + ETH-ATX 1…8 1…2 Packet
ISA-PREA 1…8 1…2 Packet
BCE-ETH 1…4 Not Available Virtual
PP10MS (1850TSS-160 & 320) 1...63 1...24 Virtual
PP10G (1850TSS-100) 1...63 1...24 Virtual
Examples of HO concatenation:
Concatenation
Board Details vc4-nV Concatenation level
type
ES4 Rel 1.2 on, as GMII 1…4 Virtual
in any slot of 1660SM Rel 5.x 1…16
in any slot of 1662SMC and in 1…8
ES16 Virtual
enhanced slots of 1660SM Rel 4.x
else 1…4
GETH-MB 1…7 Virtual
ISA-PREA 1 Virtual
ETH-MB + GETH-AG 1 Virtual
1678MCC [P4GE, P8GE, P16GE] 1…7 Virtual
1678MCC [P2XGE, P4XGE, ES64] 1…64 Virtual
PP10MS (1850TSS-160 & 320) 1…64 Virtual
PP10G (1850TSS-100) 1...64 Virtual

3JK Issue 03
Rate Adaptive Paths
Get it from the
Path’s Service Rate that can be chosen in
NAP properties
the Create Path wizard
Examples of 10-100 Mb 1 Gb 10 Gb EVPL
NAP Rate
board/equipment RA RA RA RA
10-100Mb ES1-8FE in 1660SM
OK - - -
RA ES4-8FE in 1660SM
isa-prea ES16 in 1660SM OK OK OK OK
1Gb P4GE in 1678MCC
- OK OK OK
RA GETH-MB in 1660SM
PP10MS in TSS-320
10Gb MultiService OK OK OK OK
PP10G in TSS-100
(1Gb and 10Gb
ES64, P2XGE, P4GE - OK OK OK
1678MCC’s NAPs)
In creating the Path, Path’s Service Rate Allowed Transport Rates

choose a Service Rate 10-100 Mb RA au4, tu3, tu12, au4-nv, tu3-nv, tu12-nv
that fits the desired
1 Gb RA au4-nv, tu3-nv, tu12-nv
Transport Rate
(concatenation type) and 10 Gb RA au4-nv, tu3-nv
the NAP Rate EVPL RA au4-nv, tu3-nv

RA: Rate Adaptive.

In Path creation wizard, when the user selects “Ethernet” as “Service Type”, the user must then specify
the “Service Rate” and then the “Transport Rate”.
Once the Path has been created, its Service Rate may differ from the one chosen in the Create Path
wizard. The final Service Rate depends on the NAP Rate and is set by 1350OMS.
Some boards provide a NAP belonging to Ethernet physical interfaces (e.g. SFP, RJ45,...) whereas other
boards provide a NAP belonging to an “SDH like” Ethernet logical port (remote port, VCG) that mediates
between the Ethernet physical interfaces and the SDH ports. In the former case, the Ethernet Path
accomplishes the end-to-end Ethernet service. In the latter case, the Ethernet service is to be
completed by means of 1350OMS-PKT or 1350OMS-EML.
“Not concatenated” 10-100 Mb Rate Adaptive Paths are feasible for: ETH-MB, ISA-PREA, ES1, ES4, ES4E,
and ES16 of OMSN.
“EVPL Rate Adaptive” Paths support the “Filtering plus External VLAN Termination” feature. This
feature is accomplished if at least a NAP belongs to P2XGE or P4XGE boards of 1678MCC. The other NAP
can belong to P2XGE or P4XGE boards as well, or to the boards that are suitable for the “1 Gb Rate
Adaptive” or “10 Gb Rate Adaptive” Paths.

3JK Issue 03
Paths other than Rate Adaptive Paths
Service Rate Transport Rate Equipment Board (see Note1)

1670SM GBETH-MM, GBETH-SM
1 Gb
AU4-8V (fixed) 1696MS,1696MSC
Transparent 4xANY
1660SM, 1662SMC
100 Mb 1696MS, 1696MSC
AU4 4xANY
Transparent 1660SM, 1662SMC
TU12, TU3,
1650SMC, 1662SMC, ISA-PREA
MPLS TU12-nV, TU3-nV,
1660SM ES16
AU4, AU4-nV
1642EMUX (up to Rel
Feb6 10-100Mb TU12, TU3 FEB6
2.3)
1 Gb 1696MS, 1692MSE,
AU4-7V (fixed) 2x1GE
GFP Transparent 1626LM
1 Gb 1626LM ETHC1000
WDM grooming
Ethernet Vlan MUX 1696MS/C 8xGE
Just the Rate Adaptive Paths are analyzed in the Student Guide. About the rest:
1 Gb and 100 Mb Transparent Paths are more simple than Rate Adaptive Paths
MPLS Paths are almost equal to Rate Adaptive Paths.
“1 Gb GFP Transparent” and “1 Gb Ethernet Vlan MUX” Paths concern WDM equipment
that is not part of this training.
Note1:
“Transport Rate” & “Board”: as far as a row is concerned, not all the values of “Transport Rate” are
supported by all the boards reported in the relevant “Board” column. By reading the properties of the
board’s NAP you can get the details. For example, the “... Max Supported Concatenation Level”.
Some boards provide a NAP belonging to Ethernet physical interfaces (e.g. SFP, RJ45,...) whereas other
boards provide a NAP belonging to an “SDH like” Ethernet logical port (remote port, VCG) that mediates
between the Ethernet physical interfaces and the SDH ports. In the former case, the Ethernet Path
accomplishes the end-to-end Ethernet service. In the latter case, the Ethernet service is to be
completed by means of 1350OMS-PKT or 1350OMS-EML.
MPLS Paths:
ISA-PREA supports concatenation from Rel 4.2.
ISA-PREA’s packet concatenation is not compatible with ES16’s virtual concatenation.

3JK Issue 03
Blank Page


3JK Issue 03
3.3 10-100Mb, 1Gb, 10Gb Rate Adaptive
Paths


3JK Issue 03
3.3 10-100Mb, 1Gb, 10Gb Rate Adaptive Paths
Test bench for HO concatenation
Path to create:
between the Nodes C176 (1850TSS-
100C with PP10G board) and C321
(1850TSS-320 with PP10MS board)
3 x Server Trails
#2 1Gb/s Rate Adaptive Path
au4-3V 3 Server Trails
C C
C #3 C
NAP NAP HO level HO-Trails not required
C #1 C
diverse routing
LCAS enable
Path: au4-3V
bidirectional (no matter Sink and
Source)
C CAP (VC4)
terminated Path
C C Server Trail
Source and Sink Nodes contain the
HO Link Connection NAPs

Diverse routing: the Server Trails #1 and #3 are assigned the lowest cost route; the Server Trail #2 is
assigned a route different from the one used by the other two Server Trails.
Node C660 fulfills an HO pass-through.
Source and Sink:
In case of Unidirectional Path, the Source Node is the entrance for the client’s signal from the SDH
network point of view, whereas the Sink Node is the exit for the client’s signal.
In case of Bidirectional Paths, no matter which Node of the two end-Nodes is selected as Source
and which one as Sink.
Source and Sink are two possible values of the NAP’s “Used Direction” attribute.

3JK Issue 03
1. Service Type:
Ethernet
2. Service Rate:
1Gb Rate Adaptive
3. Transport
Rate:
AU4-nV
4. Auto-Negotiation is meaningful
only for the Q3 managed boards.
• automatic 10Mb
• manual 10Mb
5. Total Concatenation • automatic 100Mb
Level: 3 • manual 100Mb
Automatic: to enable auto-negot.
6. User Label
7. Next Manual: to disable auto-negotiation
Two Ethernet boards managed via Q3 (that is not IP) are:

ETH-MB in OMSN
P16GE in 1678MCC

3JK Issue 03
1. Primary
2. Yes
3. Choose the NAPs (optional)
4. Next Example: NAP Rate is

“eth/10Gb MultiService”

Primary and Backup: backup is necessary in case of X and Y Paths. They are dealt in the “Advanced
Operation” module.
End Point inside SDH: select “no” if the NAP belongs to an External Network.

3JK Issue 03
Configuration

Allocation Rule:
Implement Rule:
User: the Path is promoted from Allocated to Implemented on user command.
Automatic: the Path is promoted from Allocated to Implemented as soon as it is Allocated.
Allocation resources: it refers to the objects used during allocation (all objects, not alarmed objects).
Show created Path(s): if set to Yes, the Paths’ routing displays are automatically opened.

3JK Issue 03
Alarm
LCAS
“LCAS Control” and “Server Trails Routing” can’t be

set in Create Path wizard if at least one of the NAPs
doesn’t support LCAS or if the user has selected two
real Nodes without specifying the NAPs.
Finally, do Apply
“Alarm” tab: it is dealt in the “Alarms” module.

“Routing” tab: it is dealt in the “Routing Algorithm” appendix.
“CP Restoration” tab: it concerns ASON. ASON is not dealt in this training.

3JK Issue 03
Path life cycle management
1. Retrieve the Path list: e.g. The Path is Defined because
Node Search OTN Paths “Allocation Rule” was set to “User”
in the Create Path wizard
DEFINED
Path life cycle

ALLOCATED
IMPLEMENTED
COMMISSIONED
To manage the Path life cycle,

apply the suitable commands:
• Allocate / Deallocate
• Implement / Deimplement
• Commission / Uncommission
Service Rate: it may be different from the one chosen by the user in the Create Path wizard. It is set by
the system according to the NAP Rate.
It’s possible to Remove a Path if it is Implemented, Allocated or Defined. It’s not possible to remove a
Commissioned Path.
Server Trails’ life cycle (in case of concatenated Path):

By allocating the Path, the Server Trails are created, allocated and set to “idle”. By deallocating the
Path, the Server Trails’ are deleted.
By implementing the Path, the Server Trails are implemented and activated. By deimplementing the
Path, the Server Trails are deimplemented and deactivated.
For details on the Server Trails’ life cycle, refer to the “Bandwidth Modification” chapter further on.
During the Path implementation, the Path’s “Configuration State” may be “Partially Implemented” for
a while. It means that some of the Server Trails have not been yet implemented.

3JK Issue 03
Path and Server Trails: HO
Physical Connection
Structure
#2
C
#3 C
C Server Server
C
NAP C #1 C NAP Trail #1 Trail #3
3 x Server Trails
Path: au4-3V The Server Trails are not available if the Path is Defined

In case of “1 Gb Transparent” Path, there are 8 Server Trails.

3JK Issue 03
Path and Server Trails: HO [cont.]
Path Routing Display
Connection Link Connection

In Topology (AU4-nv) Retrieve the Server
Trail list from this icon
or from the LC
(see next slide)
Remote NAP #2
port (AU4-nv) CTP (AU4-nv)
(VCG) C C
C #3 C
NAP C #1 C NAP
The Path Routing Display is useful mainly to
check the end-points (NAPs). The routing across 3 x Server Trails
the network concerns the Server Trails. Path: au4-3V
Server Trail list can be retrieved from:

the Link Connection
the icon along the Link Connection
the Path

3JK Issue 03
Path and Server Trails: HO [cont.]
Server Trail list
#2
C C
C #3 C
NAP C #1 C NAP
3 x Server Trails
Path Suffix
user Path: au4-3V
label Routing Display of Server Trail #2
CTP (AU4) CAP (VC4)

Server Link Connection
Trail Position-AU4 (AU4)
Connection In Topology
The Server Trail is assigned a “Channel Number”. It’s useful in managing the constraints of the
concatenated Path.
The Server Trail User Label is set by the system by appending: “Path User Label” - “rate” _ “Channel
Number”.
rate: VC4, VC3, VC12

3JK Issue 03
LO concatenation
HO-Trails are required for Ethernet Paths

with LO virtual concatenation
Path list
Search Server Trails

Server Trails list


3JK Issue 03
LO concatenation [cont.]
Routing display of Path
Remote port (VCG)
NAP (TU12-nv) #2
C C
C #3 C
NAP C #1 C NAP
3 x Server Trails
Path: tu12-3V
Server Trail CTP (TU12) CAP (VC12)

Link Connection
Routing Display of
Position- (TU12)
Server Trail #2
TU12
Connection In Topology

3JK Issue 03
3.4 EVPL Path for 1678MCC


3JK Issue 03
Introduction
Log Logical port Vlan: Tag 2
Vlan: Tag 3 MAC Vlan Rest of

Vlan: Tag 1 12 Tag 2frame 12
Real#1
Log
12
PL Path
EV
of
MAC Vlan Rest of Real#1
A C Rest e 12 P2XGE
12 Tag 1 frame 12 M am P4XGE
Log 12 fr
MAC Vlan Rest of Log 1678MCC
3 Tag 3 frame 3 EVPL
MAC R Path 3
MAC Vlan Rest of est of
P2XGE 3 fra
3 Tag 3 frame 3 me 3 MAC V
Port#1
P4XGE la
3 Ta n Rest of
Eth
g ? fra
me 3
Real#2
EPL Path 4 (1G

or 10G Rate Ad
aptive)
Port#2
MAC Vlan Rest of
Eth
4 Tag 4 frame 4 MAC Vlan Rest of
4 Tag 4 frame 4
1678MCC Any
compatible
SDH Network equipment
EVPL (Ethernet Virtual Private Line) service bears multiple Ethernet traffics on a single Ethernet port.
The “all EVPL” is supported by 1678MCC (Rel 4.1 on) by the P2XGE and P4XGE boards.
For each EVPL port, the following rules apply:
The maximum number of “EVPL Rate Adaptive” Paths is 99 (99 VLANs with VLAN-ID in the range
1...4095).
The maximum capacity is 64 AU4s.
Logical port:
During the Node uploading phase (Synchronize NE and Upload NAPs), only the Real port (Ethernet
interface) and its single associated NAP are loaded into the 1350OMS-SDH database.
Upon an EVPL Path creation, a Logical port is created along with its NAP starting from the Real port.
The EVPL Paths that share the same Real port must use different VLAN-ID.
P2XGE and P4XGE boards allow the “Filtering plus External VLAN Termination” tag processing:
From client to SDH network: the complete tag (VLAN-ID, priority, Ethernet type) of the frames is
removed if the tag matches the Logical port configuration.
From SDH to client network: the complete tag configured on the Logical port is added to the frame.
“Filtering plus External VLAN Termination” can be supported by both the NAPs involved in the EVPL
Path or just by one of them. In the latter case, the action on the Ethernet frame performed by the NAP
not-supporting “Filtering plus External VLAN Termination” depends on the NAP configuration that may
be carried out by other means than 1350OMS-SDH.
P2XGE and P4XGE boards support EPL (Ethernet Private Line) service, too. In this case the port is
transparent from Ethernet frame point of view. EPL service is accomplished by the 1G or 10G Rate
Adaptive Paths.
A Real port used for an EPL Path can not be used for EVPL Paths at the same time.

3JK Issue 03
Compatibility for EVPL Rate Adaptive Path
These boards don’t support the “Filtering plus External VLAN Termination”
P2XGE P2XGE PIMMS
P4XGE P4XGE P4GE ES4-GMII ETH-MB +
PP10G ISA- Ext.
P8GE ES16 GETH-MB
(EVPL (EVPL PP10MS ES4E GETH-AG PREA Net.
P16GE
enabled) disabled) ES64
P2XGE
P4XGE
64 64 7 64 8 4 1 7 1 64
(EVPL
enabled)
1650SMC, 1662SMC, 1660SM ETH-MB+GETH-AG, GETH-MB, ISA-PREA, ES4-GMII, ES16

1642EM ES4E
1850TSS-320/160 Rel 3.x PP10MS
1850TSS-100 Rel 3.x PP10G
1678MCC P4GE, P8GE, P16GE, P2XGE, P4XGE, ES64

The table features the highest AU4 concatenation level supported by the EVPL Rate Adaptive Path. For
some boards (e.g. ES16, GETH-MB), the real maximum concatenation level depends on the NE’s slot the
board is occupying. Check the NAP properties.

3JK Issue 03
1. Service Type:
Ethernet
2. Service Rate:
3. Transport Rate: EVPL Rate Adaptive
AU4-nV
4. Concatenation:
choose the
quantity of AU4s
5. User Label


3JK Issue 03
This section is
shown by
selecting a
NAP that
supports EVPL

NAPs:
Both the two end-point NAPs (A and Z) must be specified.
It is mandatory to select at least a NAP with the “EVPL Supported” attribute equal to “EVPL
Terminate External Vlan”. These kinds of NAPs are those of P2XGE and P4XGE boards for 1678MCC.
NAP that supports EVPL: the one that corresponds to the Real port must be selected.
VLAN Identifier, Priority and Ethernet type are used for the “Filtering plus External VLAN Termination”:
External VLAN Identifier: 1-4095.
External VLAN priority: 0-7.
External VLAN Ethernet Type: “Customer Tag” or “Service Tag”.
Suffix Port Name: the Logical port’s “Port Name” attribute is obtained by appending the “Suffix Port
Name” to the Real port’s “Port Name”. If this field is left empty, 1350OMS-SDH will automatically set a
value.
3JK Issue 03
Configuration

Allocation Rule:
Implement Rule:
User: the Path is promoted from Allocated to Implemented on user command.
Automatic: the Path is promoted from Allocated to Implemented as soon as it is allocated.
Allocation resources: it refers to the objects used during allocation (all objects, not alarmed objects).
Show created Path(s): if set to Yes, the Path routing display is automatically opened.

3JK Issue 03
“Create Path” wizard Step 3 [cont.]
LCAS

“Alarm” tab: it is dealt in the “Alarms” module.

“Routing” tab: it is dealt in the “Routing Algorithm” appendix.
“CP Restoration” tab: it concerns ASON. ASON is not dealt in this training.

3JK Issue 03
Path routing display
Path routing
display
Link Connection
(AU4-nv)
NAP
(AU4-nv)
Port list
Logical port CTP (AU4-nv)
Server Trail list
“Suffix Port Logical Real port

Name” port
Suffix
Server Trails can be retrieved from:

the Link Connection
the icon along the Link Connection
the Path
The Server Trail is assigned a “Channel Number”. It’s useful in managing the constraints of the
concatenated Path.
The Server Trail User Label is set by the system by appending: “Path User Label” – VC4 _ “Channel
Number”.

3JK Issue 03
Server Trail routing display
Map
Server Trail #1 routing display
Link Connection (AU4)
CTP (AU4) CAP (VC4)


3JK Issue 03
VLAN modification
Path list
1. Double click the

Path to get the NAPs
2. Select a NAP
Modify
NAP modifiable
properties
3. It’s possible
to modify
the VLAN
parameters

The VLAN parameters defined upon Path creation can be modified onwards.

3JK Issue 03
Exercise
Create a concatenated Ethernet Path between a couple of available

boards.
Retrieve the Server Trails and check their routing.

Is it Uniform or Diverse routing?


3JK Issue 03
Blank Page


3JK Issue 03
3.5 Bandwidth modification


3JK Issue 03
Suitable Paths
The user can increase/decrease the quantity of the Server Trails. After
the increasing, the Server Trails have to be activated.
Bandwidth modification can apply to the following Paths:

10-100 Mb Rate Adaptive
1 Gb Rate Adaptive DEFINED
10 Gb Rate Adaptive
Server Trail life cycle

EVPL Rate Adaptive
ALLOCATED
MPLS
Digital Video Broadcasting
IMPLEMENTED
- idle -
IMPLEMENTED
- active -

Active Server Trail: it participates to the traffic relaying.

Idle (not active) Server Trail: it doesn’t participate to the traffic relaying.
By implementing the Path, its Server Trails are implemented and activated as well. Afterwards, the
Server Trails can be deactivated.
To go through all the Server Trail Configuration States, the “Modify Bandwidth” wizard is to be used.
A Server Trail can be activated/deactivated if it is implemented.
A Path can bear traffic only if at least one of its Server Trails is active.
A Path is implemented when at least one of its Server Trails is active.
By deactivating all the Server Trails, the Path evolves from “Implemented” to “Partially
Implemented” state.

3JK Issue 03
Path attributes
First of all, check Path

the Path
concatenation
properties
Path properties Total Concatenation Level

It’s defined in the Create Path wizard
Active Concatenation Level

Number of active Server Trails
Max supported Concatenation Level

e.g. au4-nV n=1...64
Min required Concatenation Level

see next slide
Total concatenation level: total number of Server Trails (active + idle).

Max supported concatenation level: max number of configurable Server Trails; it depends on the
board/equipment type.

3JK Issue 03
Path attributes [cont.]
Select the Path Modify
Two methods to
change them
Select the Path Actions
Ethernet and Virtual Concatenation
Lock management
If “Check Min Req. Conc. Level”=“True”, then

“Active Conc. Level” < “Min Req. Conc. level” is forbidden
If “Check Min Required Concatenation Level”=“True”, then the system forbids to set “Active
Concatenation Level” to a value lower than “Min Required Concatenation level”.
“Min Required Concatenation Level”: it makes sense if the Ethernet Path is used by 1350OMS-PKT (Data
Manager). The Path may be in charge of relaying a Guaranteed Ethernet service, so that a minimum
granted bandwidth is required. In this case, the following operations
Path removal
Path deimplementation
Server Trail removal
Server Trail deactivation
are inhibited if they are in contrast with the value of the minimum required bandwidth.

3JK Issue 03
Modification commands
Select the Path Actions Ethernet and Virtual Concatenation

Modify Bandwidth
Max supported Concatenation Level
Total Concatenation Level
Active Concatenation Level

By means of “Modify Bandwidth” wizard, the user cannot specify the Server Trails on which the
commands are to be applied.
“Activate Trail” applies to the Server Trails with lower channel number.
“Decrease Bandwidth” and “Deactivate Trail” apply to the Server Trails with higher channel
number.

3JK Issue 03
Increase Bandwidth
2. Specify how many trails must be

DEFINED
added. Don’t exceed “Max
supported concatenation level” ALLOCATED
IMPLEMENTED
- idle -
IMPLEMENTED
- active -
1. Increase Bandwidth
4. If needed, specify 3. Specify the

the protection of the final status of
added trails the added trails
“Increase Bandwidth” with “Operation on trail”=“Activate” is allowed for any LCAS configuration,
both enable and disable, and any alarm state of the new Server Trails. If LCAS is disable and the new
Server Trails are alarmed, the Path becomes unavailable.

3JK Issue 03
Decrease Bandwidth
3. Specify how many
trails must be removed
1. Decrease Bandwidth
2. True or False. If “True”,

it allows the removal
also of active trails: at
least a trail must be
kept.
“Number of Trail” can be specified if:

“Remove activated Trails”=“True”
OR
“Remove activated Trails”=“False” AND any Server Trail is “idle”

3JK Issue 03
Deactivate Trail

DEFINED
2. Specify how many trails
must be deactivated ALLOCATED
IMPLEMENTED
- idle -
IMPLEMENTED
1. Deactivate Trail - active -
3. Specify the final

status of the
deactivated trails
If LCAS is enable, it’s possible to deactivate a Server Trail also in this way: select the Server Trail
Actions Ethernet Deactivate trail.
Modify Bandwidth wizard allows to deactivate the Server Trails of Paths with LCAS enable or disable.

3JK Issue 03
Activate Trail
1. Activate Trail
2. Specify how many trails

must be activated
3. “Force the operation” must be set to True if:

- LCAS is disable on the Path
AND
- the Path is not alarmed
AND
- the Server Trail being activated is alarmed
Force the operation: it must be set to True to activate an alarmed Server Trail that gets the Path to
be unavailable. It’s the case of LCAS disable. If LCAS is enable, the Path doesn’t become completely
unavailable by adding an alarmed Server Trail.
“Activate Trail” in Modify Bandwidth wizard applies to the Server Trails with higher channel number.
If LCAS is enable, it’s possible to activate a Server Trail also in this way: select any Server Trail
Actions Ethernet Activate trail.
Modify Bandwidth wizard allows to activate the Server Trails of Paths with LCAS enable or disable.

3JK Issue 03
Blank Page


3JK Issue 03
3.6 LCAS Management


3JK Issue 03
3.6 LCAS Management
LCAS in Create Path wizard
NAP list
1. Prior to creating a
Path, check the “LCAS
Control” attribute of
the NAPs. The NAPs
may not support LCAS
(Not Available).
2. “LCAS Control” and “Server

Trails Routing” can’t be set in
Create Path wizard Path Creation wizard if at least
one of the NAPs doesn’t
support LCAS or if the user has
selected two real Nodes
without specifying the NAPs.
LCAS Control:
Disabled: LCAS is supported by the NAP but has not been activated. It can be activated during Path
creation or later on by means of the LCAS Management wizard (see next slide).
Enabled: LCAS is supported by the NAP and has been activated.
Not Available: LCAS is not supported by the NAP.
Fixed Enabled: it’s the ISA BCE-ETH case.

3JK Issue 03
3.6 LCAS Management
LCAS management wizard
Select the Path Actions Ethernet and Virtual Concatenation
LCAS management…
If all the Server Trails are idle,

both “LCAS Control” and
“Server Trails Routing” can be
modified.
“LCAS Control” and “Server
Trails Routing” can not be
modified if at least a Server
Trail is active.
LCAS Control:
Enabled, Disabled, Fixed Enabled
Server Trails Routing:
Uniform Routing, Diverse Routing

The user can modify the Server Trails Routing attribute of a Defined, Allocated or Implemented Path.
The new provided value will be taken into account for the allocation of the new Server Trails; the
already allocated Server Trails are not affected by the new setting.

3JK Issue 03
Exercise
Create a concatenated Ethernet Path between a couple of available

boards.
Increase the bandwidth of the Path by adding two Server Trails. Check
their routing.


3JK Issue 03
3.7 Flow control


3JK Issue 03
3.7 Flow control
Configuration
Suitable for 1 Gb and 10 Gb Rate Adaptive NAPs of 1678MCC Rel 4.1 on.
On the other NEs the flow control is always disabled.
1. Select the NAP

Modify
“Modify”
window for
the NAP
2. Set the Flow Control


3JK Issue 03
4 DVB Path


3JK Issue 03
4 DVB Path
ISA DVB ASI Board capabilities
As represented in the following figure, ISA DVB ASI board accomplishes

the Network adapter function.
The ISA DVB ASI maps the Digital Video Broadcasting stream on:
VC12-nV (n = 1…63)
VC3-nV (n = 1…3)
Up to 4 “user to network” streams +

Up to 4 “network to user” streams

Digital Video Broadcasting signal is managed, in Transport Networks based on Alcatel-Lucent OMSN,
by the board named ISA DVB ASI. It is available starting from OMSN Rel 4.5.
Prior to entering into the transport network, the television broadcast signal is compressed using an
MPEG-2 encoder. The single MPEG-2 stream generated by the encoder may be combined with other
MPEG-2 streams in a multiplexer, then a network adapter (ISA DVB ASI) maps the resulting MPEG-2
stream into a single or a group of VC12 or VC3 containers, suitable to be borne in the SDH transport
network.
At the receiving ends of the link, a network adapter extracts the required data stream from the
network. If a multiplex of programs was created at the input to the network, the adapted data
stream is presented to a de-multiplexer to extract the individual MPEG-2 stream.
These are then passed to an MPEG-2 decoder for conversion into television broadcast signals.
In ISA DVB ASI:

the mapping protocol used for encapsulating the Data traffic into SDH virtual containers is fixed; it
is the GFP Framed Null Extension header without FCS as specified in Standard G.7041.
LCAS is not supported.
the traffic is not bidirectional; as a matter of fact each board is capable to manage independently:
4 traffic flows in “from user to network” direction (Source NAPs)
4 traffic flows in “from network to user” direction (Sink NAPs)
that is for a given interface the trails in the Sink direction and in the Source direction can be
different both in terms of route and/or in terms of bandwidth (i.e. VC type and/or concatenation
level).

3JK Issue 03
4 DVB Path
Test bench
Example:
Sink[1]
• broadcast Path
• two Sink end-points
Sink
• TU12-2V
• not protected
Source No HO-Trail
NAP list
The board provides 8 NAPs:

• 4 NAPs can be used as Source
• 4 NAPs can be used as Sink

The Physical Connections between 63B and 165B don’t afford any HO-Trail; thus, they are not used by
the Path.

3JK Issue 03
4 DVB Path
1. DATA 2. Digital Video
Broadcasting
Concatenation:
• 1 to 63 for TU12-nV
• 1 to 3 for TU3-nV
Protection: can be
enabled or disabled
Sncp Type: it must be set to
“SNCP/N preferred” regardless
“Protection” is enabled or not
Path Type:
unidirectional: point-to-point
broadcast: point-to-multipoint
Total Concatenation Level can be modified when the Path is established by means of the Modify
Bandwidth wizard: select the Path Actions Ethernet and Virtual Concatenation Modify
Bandwidth
ISA DVB ASI doesn’t support LCAS

3JK Issue 03
4 DVB Path
If broadcast, click to add

further Sinks (Sink[1])
When choosing the NAPs, pay attention
to their “Direction” attribute: whether
they can be used as Source or Sink

3JK Issue 03
4 DVB Path
Path
Sink Sink[1] Broadcast
Link Connection
(TU12-nV)
Sink
Source
Leg # Source CTP

Source NAP Sink CTP (TU12-nV)
(TU12-nV) (TU12-nV)
Source CTP
The Path Routing Display is (TU12-nV)
useful mainly to check the
end-points (NAPs). The
routing across the network
concerns the Server Trails.
Sink[1]

3JK Issue 03
4 DVB Path
Server Trails
Sink NAP Sink[1] NAP
Ch#1 Link CAP#1 CAP#2 CAP#1 CAP#2
Link
Source NAP
Involved
resources CAP#1
CAP#2
Link Link
Ch#2 Connection Connection
Ch#1-leg#1
Ch#1-leg#2 Sink NAP Sink[1] NAP
CAP#1 CAP#2 CAP#1 CAP#2
Routing Link Link
Display Connection Connection
Source NAP
provided by CAP#1
1350OMS-SDH
CAP#2
Link Link
Ch#2-leg#2
Pt-to-MPt
Ch#2-leg#1 Cross-connection
In this example, the two legs of a channel share the same Link Connection over a span. In different
network topologies, the legs may result completely disjoined.

3JK Issue 03
4 DVB Path
Server Trails [cont.]
Server Trail – Channel #1
Only one
TU12
Sink CAP Ch#1-leg#1

(VC12)
Ch#1-leg#2
Source CAP – Source CTP

Sink CTP Source CTP Sink CAP
gMAU#1 (VC12) (TU12)
(TU12) (TU12) (VC12)
Sink CTP
(TU12)

164B fulfills a point-to-multipoint cross-connection for each Server Trail: the Source CTP is connected
to both Sink CAP and Sink CTP.
The Routing of the “Server Trail – Channel #2” is similar to the “Server Trail – Channel #1”’s one:
instead of “Source CAP-gMAU#1”, the “Source CAP-gMAU#2” is used (a different VC12).
instead of “Sink CTP-.../1/1.1”, the “Sink CTP-.../1/1.2” is used.
instead of “Sink CAP-gMAU#1”, the “Sink CAP-gMAU#2” is used (a different VC12).

3JK Issue 03
5 ATM Path


3JK Issue 03
5 ATM Path
ATM over SDH example
ATM over E3
TU3
TU3
TU3
(20Mb/s)
1 20
FREE
1
FREE
30
20
30
20
NE with ATM
M A
ATM over E1 AT ver board
o v TM
(1Mb/s) o DH SD er A TM
S H over
SDH
ATM over E3 STM-N network
(20Mb/s)
NE with ATM
board HO or LO pass-through
ATM over E3
(30Mb/s)
ATM board can aggregate

several ATM signals into a
single Virtual Container The ATM traffic can be mapped into:
• SDH Virtual Containers: VC12, VC3, VC4, VC4-4C
• PDH signals: E1 (PDH 2M), E3 (PDH 34M), DS3 (PDH 45M)
Metro OMSN has integrated ATM Virtual Path and ATM Virtual Channel switching capabilities available
through optional ATM switch boards.
Such functionalities are particularly useful in urban and local access ring to consolidate data traffic
from different users onto the same SDH Virtual Container, thereby optimizing the utilization of
transmission bandwidth.
1350OMS-SDH permits to create the SDH connections involving ATM boards. ATM connections must be
done via Craft Terminal or 1350OMS-EML.
VC4-4C: contiguous concatenation of four VC4s.
In the picture, the VC4 is payloaded at LO (TU3, TU3, TU3). The aggregate ATM traffic (71Mb/s) can
be borne by two TU3s; these two TU3s can be later filled in with further ATM traffic. The third TU3 is
free: it can be used for any kind of traffic (ATM, PDH,...).

3JK Issue 03
5 ATM Path
Example for UMTS application
OMSN
RNC
board
STM-N
ATM port
(*) -VC4- (External Network)
SDH network
VC4 AU4 VC4
NAP AU4 NAP
ATM port ATM Path at
-PDH 2M- 140Mb-HO
NAP VC12
ATM
board
ATM Path at 2Mb-LO
NAP
VC12 2Mb/s
board
2Mb/s port
(*) This ATM connection can be

carried out by means of Craft
ATM over E1 Terminal or 1350OMS-EML
UMTS: Universal Mobile Telecommunications System

RNC: Radio Network Controller
To map the ATM traffic carried by a 2Mb/s signal (E1) into an STM-N signal, it’s necessary to create
two ATM Paths:
ATM Path at 2Mb-LO: to let the ATM board exchange the ATM traffic with the 2Mb/s board.
ATM Path at 140Mb-HO:
in the starting node, to let the ATM board exchange the ATM traffic with the STM-N board.
to enable the transit of the VC4 carrying ATM traffic in the nodes across the SDH network.
The ATM Path can be terminated on ATM switches; they are represented by External Networks.

3JK Issue 03
5 ATM Path
ATM port configuration by 1350OMS-EML
First of all, configure the ATM ports by 1350OMS-EML
1. From the
“Configuration”
menu, choose “ISA
Port Configuration”
2. Select a row,
that is a port
3. Select the
signal type
4. Create/Change


3JK Issue 03
5 ATM Path
ATM ports/NAPs in 1350OMS-SDH

VC4-C: contiguous concatenation of four VC4s.

3JK Issue 03
5 ATM Path
ATM ports/NAPs in 1350OMS-SDH [cont.]
1. Prior to creating the ATM

Path:
- Perform a “Synchronize
NE” in order to upload the
ATM ports.
- NAPs are automatically
provided.
SDH VC4 “Signal”
PDH 2M “Signal”
SDH VC4-C “Signal”

PDH 34M “Signal”

“Signal” refers to the window in 1350OMS-EML.

3JK Issue 03
5 ATM Path
ATM Path at 2Mb-LO
Create Path wizard – step#1
1. Service Type:
ATM
2. Service Rate:
2Mb-LO
ATM port type in Craft Path type in

Terminal or 1350OMS-EML 1350OMS-SDH
PDH 2M, SDH VC12 2Mb-LO
PDH 34M, SDH VC3 34Mb-LO
PDH 45M 45Mb-LO
SDH VC4 140Mb-HO
SDH VC4-C AU4-4C

3JK Issue 03
5 ATM Path
ATM Path at 2Mb-LO [cont.]
Source and Sink belong to the same

node. Both NAPs’ rate is VC12.
ATM board’s NAP; its attribute 2M board’s NAP; its attribute

“Port Technology” is ATM “Port Technology” is PDH


3JK Issue 03
5 ATM Path
ATM Path at 2Mb-LO [cont.]
In this example, the

2Mb-LO ATM Path
between the ATM port
and the PDH port
involves one Node
OMSN
ATM NAP PDH NAP
ATM port (VC12) (VC12)
VC4
ATM port 2M ATM port 2M PDH port

VC12 ATM
board
VC12 Path
2M port
Connection
PDH board
In Topology


3JK Issue 03
5 ATM Path
Concatenated ATM Path
1350OMS-EML
VC4-C: contiguous
concatenation of four VC4s
1. Configure the ATM

Create Path wizard – step#1 port as “SDH VC4-C”
by using 1350OMS-EML
2. Service Type:
ATM
3. Service Rate:
AU4-4C

To terminate a concatenated Path on an NE, it is necessary to:

configure in the NE an ATM8x8 board.
configure an ATM port as VC4-C; it provides the concatenated NAP for the Path.
The Physical Connections must be STM-N (N>=4) and must afford contiguous concatenated AU4s. The
concatenation is automatically created by 1350OMS-SDH upon Path implementation or can be
configured by the user (select an AU4 and issue “Payload Structure Modification Ho Cfg AU4-
4C”).

3JK Issue 03
5 ATM Path
Concatenated ATM Path [cont.]
ATM NAP rate = C4-

4C
CTP
ATM NAP (AU4-4C)
(C4-4C)
ATM port
(C4-4C)


3JK Issue 03
5 ATM Path
Concatenated ATM Path [cont.]
Physical Connection Structure
These 3 LCs have been replaced by

the concatenated one
ATM Path
The grouping of four AU4s
Concatenated Link Connection (AU4-4C):
into one AU4-4C on the STM
AU4#1 + AU4#2 + AU4#3 + AU4#4 ports is automatic
Removing the concatenated ATM Path, the AU4-4C is not disassembled into AU4s. To recover the four
AU4s: select the 4C Link Connection Actions Payload Structure Modification Ho Cfg AU4.

3JK Issue 03
6 Not Terminated Path


3JK Issue 03
Example
boundary CTP properties
“Not terminated Path” has one or both the
end-points belonging to External Networks
Example: create a 2Mb/s Path between a real

Node (164B) and an External Network (EN1)
Path’s end-nodes
(A and Z nodes) Boundary LO CTP (TU12) 01/1/2.3
on board#3 3– port#1
Path Routing Display
External
Network
HO-Trail HO-Trail
NAP

Not terminated Paths have one or both the end-points not belonging to a NE managed by 1350OMS-
SDH, so that they must be terminated into External Networks.
Should 164B be selected as A node, Z node can be either 165B (it contains the boundary CTP) or EN1.
In this example, let’s select 165B as Z node.

3JK Issue 03
Example [cont.]
board#33 – port#1
LO CTP (TU12) 01/1/2.3 2. Select the
boundary NE
1. Set “End Point inside SDH” to “No” (or the
External
Network)
3. Select the
STM port
4. Select the
boundary CTP
5. Set Z Port Name


3JK Issue 03
Exercise
Create an External Network

Create a Physical Connection between the External Network and a Node
Create an HO-Trail over that Physical Connection
Create a Path between the External Network and another Node,
different from the adjacent one:
first, by selecting the External Network as Sink Z Node
then, by selecting the Node adjacent to the External Network as Sink Z Node


3JK Issue 03
Blank Page


3JK Issue 03
End of Module
Path management


3JK Issue 03
@@SECTI
Section 2
System Operation
Module 5
SNCP and DC SNCP management
xx Issue 03
1350OMS

xx Issue 03
Blank Page

System Operation SNCP and DC SNCP management
Document History

xx Issue 03
Module Objectives
Set up and manage SNCP protection

Move to the spare way the protected HO traffic of a Physical Connection
Set up and manage D&C SNCP protection


xx Issue 03


xx Issue 03
Page
1 SNCP management 7
TableofContents
2 Handling of X and Y Paths
2.1 X and Y Paths introduction
2.2 X Path setup
27
29
35
2.3 Y Path setup 39
2.4 Add/Remove Path ends 43
3 Drop & Continue SNCP 53
3.1 Drop & Continue Generalities 55
3.2 D&C Path/Trail Creation and Management 61
Switchtonotesview!
255 AllRightsReserved©Alcatel-Lucent@@YEAR
SystemOperationSNCPandDCSNCPmanagement
1350OMS1350OMS-SDHR9.1.1MNT4Operation

xx Issue 03
TableofContents[cont.]
SystemOperationSNCPandDCSNCPmanagement

xx Issue 03
1 SNCP management


xx Issue 03
1 SNCP management
General concepts
Sub-Network Connection Protection can be used on SDH network

topologies that provide at least two routes (Main and Spare): ring or
mesh networks.
SNCP applies to: VC12, VC3, VC4, VC4-xc (x = 4, 16, 64)
SNCP can be used to protect the full end-to-end Path/Trail or a portion

of Path/Trail.
SNCP can be “not revertive” or “revertive”. In the latter case, the Main
takes over again after 5 minutes (WTR: wait time to restore).

VC4-xc: contiguous concatenation of x VC4s

xx Issue 03
1 SNCP management
General concepts [cont.]
Two different SNCP mechanisms are supported for Path/Trail: SNCP/I

and SNCP/N.
SNCP/I (Inherent) with or without alarm visualization:

switching criteria: AIS and LOP.
with alarm visualization:
AIS detection is enabled on the switches’ CTPs (HO or LO) that belong to the main
and spare routes.
should AIS be detected either on the main or on the spare route, the Path/Trail
“Degraded Protection” alarm is raised.
SNCP/N (Not intrusive):

switching criteria: AIS, LOP, SSF, SD, TIM, Excessive BER, Unequipped.
POM functionality is automatically enabled by 1350OMS-SDH on the switches’
CTPs (HO or LO) that belong to the main and spare routes.

LOP: Loss Of Pointer

SD: Signal Degrade
TIM: Trace Identifier Mismatch
BER: Bit Error Rate
OH: OverHead
POM (Path Overhead Monitoring):

it allows a server layer to read the OH of its client layer (e.g. POM enabled on AU4 monitors the OH
of VC4).
it is just a monitoring, thus the OH is read from the VCn inside the incoming AU4/TUn without
being modified.
For SNCP/N, the “Ingressing” POM is required. “Ingressing” POM is also said “Before Matrix” POM.

xx Issue 03
1 SNCP management
Protection strategies
Two types of SNCP protection strategy can be applied.
Unprotected HO-Trails containing protected LO-Paths

The bridge/switch operates at TU12/TU3 level
Protected HO-Trails containing unprotected LO-Paths

The bridge/switch operates at AU4 level


xx Issue 03
1 SNCP management
Protection strategies [cont.]
Unprotected HO-Trails containing protected LO-Paths
NODE 2
trail 1 trail 2
NODE NODE
1 3
TU TU
bridge bridge
switch switch
TU TU
NODE 5 NODE 4
tr
l5
ai
Protected
ai
l3
trail 4
tr
Path Protected
Path
Protected Path: main route
Protected Path: spare route Unprotected Trails
Bridge/switch
it is at TUn level.
for bidirectional Path, it’s actually bridge & switch in both the end-nodes.
for unidirectional Path, there’s a bridge in one end-node and a switch in the other end-node.
Unprotected HO-Trails contain protected and/or unprotected LO-Paths.
Only the protected Paths are protected in case of failure.

xx Issue 03
1 SNCP management
Protection strategies [cont.]
Protected HO-Trails containing unprotected LO-Paths
NODE 2
NODE NODE
1 AU4 AU4 3
bridge bridge
switch switch
AU4 AU4
NODE 5 NODE 4
Unprotected
Paths Unprotected
Paths
Protected HO-Trail: main route
Protected HO-Trail: spare route
Bridge/switch
it is at AU4 level.
for bidirectional Path, it’s actually bridge & switch in both the end-nodes.
for unidirectional Path, there’s a bridge in one end-node and a switch in the other end-node.
Protected HO-Trails contain unprotected LO-Paths.
All the LO-Paths are protected in case of failure.

xx Issue 03
1 SNCP management
Protection enabling
During Path/Trail creation:

In the “Create Path” and “Create Trail” wizards.
Later on. Three methods are available:

method 1: use the command “Modification Add Protection Spare” for
defined/allocated/implemented Path/Trail.
method 2: use the Path/Trail Modification Tool for
defined/allocated/implemented Path/Trail.
method 3: modify the properties of the Path/Trail for defined Path/Trail.
“Create...” wizards, method 1 and method 3 are meant for end-to-end

protection.
Method 2 is meant for segment protection.

the user must specify the extremities along the Path/Trail between which the
protection has to be established.

The SNCP protection for Paths and HO-Trails can be enabled during their creation or later on.
Later on: SNCP protection can be added to a Path/Trail already created without protection.
In Rings:
just the rings configured as SNCP NPA along the Path’s route afford the protection. The rest of the
route’s segments are not protected.
Both the end-to-end and the segment protections are accomplished by a best-effort approach.
End-to-end protection: 1350OMS-SDH looks for main and spare resources between the end-points of
the Path/Trail. If the available resources don’t accomplish the end-to-end protection, the
protection may be established just for a part of the Path/Trail, leaving some segments
unprotected.
Segment protection: 1350OMS-SDH looks for main and spare resources between the extremities
chosen by the user. If the available resources don’t accomplish the complete protection of that
segment, the protection may be established just for a part of the segment, leaving some parts
unprotected.

xx Issue 03
1 SNCP management
End-to-end protection: Path/Trail creation
Protection For HO-Trail

Protection
Sncp Type
For Path
Protection

SNCP/I (Inherent)
with alarms:
AIS detection is enabled on the switches’ CTPs (HO or LO) that belong to the main and spare
routes.
the Path/Trail “Degraded Protection” alarm is generated in case of spare route’s failure; it’s
warning (blue).
In Rings:
available only for Paths.
not available for virtual concatenated Paths.
In Rings: just the rings configured as SNCP NPA along the Path’s route afford the protection. The
rest of the route’s segments are not protected.

xx Issue 03
1 SNCP management
Routing display of an SNCP protected Path
CIT: Connection
In Topology
SNCP
symbol Blue “Link Connection”:
Main route
Search Selected side:

Connection M: Main
Details
S: Spare
CTP CTP
Magenta “Link Connection”: CTP “involved”

NAP in SNCP
Spare route
CIT: it’s a protected cross-connection in case of SNCP bridge/switch.

To check whether a CTP belongs to a protected cross-connection: open its properties window look
for the SNCP section SNCP attribute is “involved”.

xx Issue 03
1 SNCP management
Synchronize and Revertive/Not revertive
Synchronize (for implemented and commissioned Path/Trail):

To synchronize both the Path/Trail’s switches:
Select the Path/Trail Actions SNCP Management Synchronize Switch Position
To synchronize a single switch:
Select the CIT Actions SNCP Management Synchronize
Revertive/Not revertive (for implemented Path/Trail):
To set the Operation Mode of both the Path/Trail’s switches:
Select the Path/Trail Actions SNCP Management Operation mode Choose
between “Revertive” and “Not revertive”
To set the Operation Mode of a single switch:
Select the CIT Actions SNCP Management Operation mode Choose
between “Set revertive” and “Set not revertive”
Blue arrow: revertive
Question mark: unknown status

“Synchronize” retrieves the actual switch status from the equipment. It’s necessary when the
switch’s status is unknown.
The default Operation Mode is “not revertive”.
CIT: Connection In Topology.

xx Issue 03
1 SNCP management
SNCP type and Hold off time
To modify the SNCP type

the Path/Trail must not be “commissioned”
select the Path/Trail Actions SNCP Management Modify SNCP Type
SNCP/I preferred with alarms
SNCP/I preferred no alarms
SNCP/N preferred
To set the Hold Off Time
the Path/Trail must not be “defined”
select the CIT Actions Hold Off Time Set Hold Off Time
0, 30, 50, 70, 100, 300, 500, 700 ms
1, 3, 5, 10 s

Hold Off Time: in case of failure, the protection is triggered after this time and not immediately. It is
meaningful when other protections (MSP, ...) are enable at the same time.

xx Issue 03
1 SNCP management
User commands
The commands can be issued on Path/Trail or on CIT.

On Path/Trail:
The command affects both the switches
Select the Path/Trail Actions SNCP Management Commands
On CIT:
The command affects only the selected switch
Select the CIT Actions SNCP Management Commands
CIT
Path properties
F: force command
is active
CIT (Connection In Topology): cross-connection.
Release clears the previously issued lockout/force/manual command.

Lockout locks (forces) the switch on the main route. The Path/Trail remains on the main route even
in case of failure.
Force main forces the Path/Trail on the main route. The Path/Trail remains on the main route even
in case of failure. The switch is rejected in case of a previously issued Lockout command is active.
Force spare forces the Path/Trail on the spare route. The Path/Trail remains on the spare route even
Manual main switches the Path/Trail to the main route. The switch is rejected in case of failure or a
previously issued Force/Lockout command is active.
Manual spare switches the Path/Trail to the spare route. The switch is rejected in case of failure or a
Some commands are not supported by some equipment types.

xx Issue 03
1 SNCP management
SNCP/I preferred with alarms
“Degraded Protection” alarm: it’s warning
CTP with AIS
Fiber cut
HO-Trail
SNCP/I (Inherent)
with alarms:
AIS detection is enabled on the switches’ CTPs (HO or LO) that belong to the main and spare
routes.
should AIS be detected either on the main or on the spare, the Path/Trail’s “Degraded
Protection” alarm is generated.
for more details, see the Student Guide’s “Alarm” module.

xx Issue 03
1 SNCP management
End-to-end protection: Add protection Spare
2. Choose between:
• Spare: to get an SNCP protection
• Service: to get a D&C SNCP protection
(only Allocation): the spare/service is not implemented
automatically even if the Path/Trail main is implemented
1. Select the Path/Trail Actions
Modification Add Protection …
D&C SNCP is dealt onwards in this module.

xx Issue 03
1 SNCP management
End-to-end protection: remove
2. Choose between:
• Keeping main: the Spare is removed if the Main is not faulty
• Keeping spare: the Main is removed if the Spare is not faulty
(no check): the removal is executed regardless the failure
condition
1. Select the Path/Trail Actions

Modification Remove Protection …
The protection is removed for the whole Path/Trail, end-to-end. No segment is kept protected.

xx Issue 03
1 SNCP management
Segment protection: Path/Trail Modification Tool
protection to add (spare)
current route (main)
Termination Points (TPs)

at the extremities of the
segment to protect
HO-Trail routing display

If the segment encompasses an end-node, the TP to select in the end-node is the CAP (VCx) and not the
CTP (AU4, TUn).

xx Issue 03
1 SNCP management
Segment protection: Path/Trail Modification Tool [cont.]
1. Select the Path/Trail
Actions Modification
Path/Trail Modification Tool
2. Add Protection
3. Only Allocation:
No: the spare is implemented
Yes: the spare is allocated
4. Apply

As “A Tp” can be selected either the one of the Node on the left or the one of the Node on the right. As
“Z Tp” as well.
Only Allocation
it’s prompted only if the Path/Trail is implemented.
if No:
the spare route is created, allocated and implemented.
if Yes:
the spare route is created and allocated.
the Path/Trail gets “Partially Implemented” as a whole; it’s grey.
to implement the spare route, the user must implement the Path/Trail.

xx Issue 03
1 SNCP management
Segment protection: Path/Trail Modification Tool [cont.]
Outcome
Protected segment
Protected CIT Protected CIT


xx Issue 03
1 SNCP management
Segment protection: Remove
Termination Points (TPs)

at the extremities of the
segment
Protected segment Protected segment

NOT to remove to remove


xx Issue 03
1 SNCP management
Segment protection: Remove [cont.]
1. Remove Protection
2. Choose the extremities.

The TPs may be the ones indicated
in the previous slide. However, also
other TPs of the switch are suitable.
3. Check on SNCP Switch
Yes: the removal is not executed if
the leg to remove (Main or Spare) is
currently operational
4. Keeping. Choose the leg 5. Apply

NOT to delete: Main or
Spare

xx Issue 03
1 SNCP management
Segment protection: adding additional Spares
The protection segments can be
disjoint or nested
added to Main or Spare
Main
Protected
CITs
Original
Spare
Further
Spare


xx Issue 03
1 SNCP management
Not protected LO-Path over protected HO-Trail
LO-Path
routing display
HO-Trail
routing display
HO-Trail


xx Issue 03
Exercise
Working on NEs with LO Ports or on External Networks:

1. On a given AU4#, create HO-Trails in order to carry LO-Paths.
2. Configure the payload of these HO-Trails according to the type of NAPs.
3. On a given TU12#, create a protected LO-Path crossing the HO-Trails
previously created. Select “SNCP/I preferred no alarm”.
4. Get information
1. Localize the main and the spare routes.
2. Identify the current status of the switches.
5. Check the protection
1. Create a failure on the active side.
2. Verify the new status of the switches.
6. Remove the Path’s protection keeping the main side.
7. Remove the free HO-Trail(s).
8. Add the protection to an HO-Trail.


xx Issue 03
Blank Page


xx Issue 03
2 Force switch on HO-Paths/Trails
crossing a Physical Connection


xx Issue 03
2 Force switch on HO-Paths/Trails crossing a Physical Connection
Rationale
The user has the possibility to move away the active routes of all the
protected HO-Paths and HO-Trails from a Physical Connection by means
of the “Maintenance” wizard.
The “Maintenance State” of the selected Physical Connection is set to
“In Maintenance”.
The traffic of each protected HO-Path/Trail is moved away by means of
a “force” command on their switches.
By means of the same tool, the user can recover to “Normal” the
Maintenance State of the selected Physical Connection. As a
consequence, the “force” commands are released. If SNCP is “not
revertive”, the user can re-activate the routes on the original Physical
Connection by using the SNCP commands.
N.B.: only the traffic of HO-Paths and HO-Trails is switched. Therefore,

protected LO-Paths over not-protected HO-Trails are not moved away
from the Physical Connection to be put in maintenance.

The feature is not applicable to:

not protected, broadcast and protected D&C Paths/Trails.
Physical Connection inside ASON/Fast Restoration domain.

xx Issue 03
Test bench
trail-3:
-It’s protected
-It contains Path-3
trail-2:
-It’s protected
-It contains Path-2
trail-1:
-It’s NOT protected
-It contains Path-1
Addressed Physical Connection

PC
properties
Log
Maintenance State:
it is “normal” as default.
it changes to “In Maintenance” after the execution of the switch command.
Routing Administrative State:

it’s default value is Enabled.
if Disabled, the Physical Connection is not used for allocating Paths/Trails.
it can be set by means of “Modify” for the Physical Connection.
it can be modified from Enabled to Disabled during this procedure.
Trail-1
it’s not addressed by the switch command because it is not protected.
Trail-2
its main route crosses the addressed Physical Connection. Hence the switch command consists in a
Force on the spare.
Trail-3
its spare route crosses the addressed Physical Connection. Hence the switch command consists in a
Force on the main (Lockout).

xx Issue 03
Operation
Select the Physical Connection

Actions Path/HO Trail
management SNCP maintenance

Set in maintenance with no check: the force command is invoked for a Path/Trail only if:
the route which the traffic has to be moved to doesn’t cross Physical Connections with
“Maintenance State” equal to “In Maintenance”.
no force commands have been performed by the user.
Set in maintenance with check: the force command is invoked for a Path/Trail only if:
same conditions as for “no check”.
the switch succeeds if the route to which the traffic has to be moved to is not alarmed (it means
that the HO-Trail or HO-Path must be in SNCP-N protection).
Remove from maintenance: the force command is released for a Path/Trail only if:
the routes (main and spare) of the Path/Trail don’t cross other Physical Connections with
“Maintenance State” equal to “In Maintenance”.
N.B. Force commands performed by the user are not released.
Modify Routing Administrative State: if the user checks this option, the execution of the switch
command changes the Physical Connection’s “Routing Administrative State” attribute from Enabled
to Disabled.

xx Issue 03
Exercise
Consider a ring.
Create some protected HO-Trails and some not protected HO-Trails.
Choose a ring’s Physical Connection that bears some HO-Trail’s active
sides.
Set that Physical Connection in “Maintenance”.


xx Issue 03
Blank Page


xx Issue 03
3 Drop & Continue SNCP


xx Issue 03
Blank Page


xx Issue 03
3.1 Drop & Continue generalities


xx Issue 03
Schemes
D&C protection refers to rings interconnection. It permits to support

one failure per ring.
Three types of interconnection between two rings:
Single Node interconnection with 1 NE
Dual Node interconnection with 2 NEs


xx Issue 03
Single Node interconnection with 1 NE
“No failure”
route
First failure
SNCP ring Switched
SNCP ring Second

failure
Switched

xx Issue 03
“No failure”
route
First failure
SNCP Ring Switched
SNCP Ring
Second
failure
Switched

xx Issue 03
“No failure”
route
First failure
Switched
SNCP Ring
SNCP Ring
Second
failure
Switched

xx Issue 03
Blank Page


xx Issue 03
3.2 D&C SNCP Path/Trail creation and
management


xx Issue 03
3.2 D&C Path/Trail creation and management
Routing roles
SNCP = Main + Spare

Service
D&C SNCP = Main + Spare + Services
Main Spare
Service


xx Issue 03
Reminder about SNCP NPA
NPA
icon NPA
icon
SNCP
NPA
SNCP
NPA


xx Issue 03
Creation methods
D&C SNCP Path/Trail can be set up in three different ways:
Method 1: by selecting “D&C SNCP” as “Protection” in the Create wizard

Method 2: by using the “Actions Modification Add Protection
Service” command on an SNCP protected Path/Trail
Method 3: by means of “Path/Trail Modification Tool” on an SNCP Path/Trail
For methods 1 and 2:

SNCP NPA must have been previously set up in the involved rings, except in
case of “Single Node interconnection with 1 NE”.
the Service segment is created only for the ring/s for which the NPA has been
defined.
For method 3:
only one or both the Service segments can be created.

Method 2: besides “Add Protection Service”, “Add Protection Service(only Allocation)” is

available: the Service segments are only allocated to permit the user to check the routing. The
Path/Trail status gets to “partially implemented”. To configure the Service segments into the NEs,
the Path/Trail must be implemented again.

xx Issue 03
Method 1: Path/Trail creation
Trail
Path


xx Issue 03
Method 2: “Add protection” to SNCP Path/Trail
SNCP
Select the Path/Trail

Actions Modification
Add Protection Service
OR Service (only Allocation)


xx Issue 03
Method 3: Path/Trail modification tool
Select the Path/Trail Actions Modification

Path/Trail Modification Tool


xx Issue 03
Method 3: Dual Node – 4 NEs, TP naming
HO-Trail
D&C D&C
A tp on Z tp on
main route main route
Main
Service
Service
Spare
D&C D&C
A tp on Z tp on spare
spare route route
As “A TPs” can be selected either the ones of the Node on the left or the ones of the Node on the right.
As “Z TPs” as well.

xx Issue 03
Method 3: Dual Node – 4 NEs, configuration


xx Issue 03
Method 3: Dual Node – 2 NEs, TP naming
D&C
HO-Trail
A tp on
main route D&C
Z tp on
main route
Main
Service
Service
Spare
D&C D&C
A tp on Z tp on spare
spare route route

xx Issue 03
Method 3: Dual Node – 2 NEs, configuration


xx Issue 03
Synchronize switches and Revertive/Not revertive
To align the Routing Display information with the real status of the NEs,
it may be necessary to “Synchronize” the switches’ position:
To align all the Path/Trail’s switches: select the Path/Trail Actions

SNCP Management Synchronize Switch Position
To align just a switch: select the Connection In Topology Actions SNCP
Management Synchronize
To change the Operation Mode:
To configure all the Path/Trail’s switches: select the Path/Trail Actions

SNCP Management Operation mode Revertive/Not revertive
To configure just a switch: select the Connection In Topology Actions
SNCP Management Operation mode Set revertive/Set not revertive
revertive


xx Issue 03
“Dual Node interconnection with 4 NEs”: routing display
M
M M
C C
S
Main Main Main
Service
M Service Spare
Spare Spare
S
Details in
next slide
C C
S S

HO-Trail with D&C SNCP

M, C, S icons in the Routing Display indicate the active side:
M: Main
S: Spare
C: Service

xx Issue 03
“Dual Node interconnection with 4 NEs”: details
Z
Y
X
C
S
Search Z X
Connection Details
Y
Z Y
Z Y
X
Protected
Search cross-connection
X HO CTP
Connection Details

xx Issue 03
“Dual Node interconnection with 2 NEs”: routing display
Main Main Main
Service Service
Spare Spare
Spare
Details in
next slide


xx Issue 03
“Dual Node interconnection with 2 NEs”: details
X W
Y
Z W X
Search
Connection
Details Z
Y Y
W
Z X
Y W
X Z
Protected Protected
cross- cross-
Z connection Y connection

xx Issue 03
User commands
To issue a user command:
For all the Path/Trail’s switches: select the Path/Trail Actions SNCP
Management Commands …
For just a switch: select the Connection In Topology Actions SNCP
Management Commands …

Release clears the previously issued lockout/force/manual command.

Lockout locks (forces) the switch on the main route. The Path/Trail remains on the main route even
in case of failure.
Force main forces the Path/Trail on the main route. The Path/Trail remains on the main route even
Force spare forces the Path/Trail on the spare route. The Path/Trail remains on the spare route even
Manual main switches the Path/Trail to the main route. The switch is rejected in case of failure or a
Manual spare switches the Path/Trail to the spare route. The switch is rejected in case of failure or a

xx Issue 03
Remove the Service segments
Method 1: Select the Path/Trail Actions Modification Remove

Protection Service/Service(no check)
it removes all the Service segments
Service: the removal fails if the Service segments are currently part of the
Path/Trail’s active route.
Service(no check): the removal is executed regardless of the Service
segments usage.
Method 2: Path/Trail modification tool

the user selects the TPs of the Service segments to remove: only one Service
or both.
“Check on SNCP Switch”=Yes: the removal fails if the Service segments are
currently part of the Path/Trail’s active route.
By removing both the Service segments of a D&C SNCP Path/Trail, its

protection becomes SNCP.


xx Issue 03
Exercise
Set up a D&C SNCP protected Path

Analyze the routing display


xx Issue 03
End of Module
SNCP and DC SNCP management


xx Issue 03
@@SECTI
Section 2
System Operation
Module 6
2F-MS-SPRING management
3JK Issue 03
1350OMS

3JK Issue 03
Blank Page

System Operation 2F-MS-SPRING management
Document History

3JK Issue 03
Module Objectives
understand the 2F MS-SPRing behaviour

analyze the protection status
apply user commands


3JK Issue 03


3JK Issue 03
Page
1 Introduction on 2F MS-SPRing 7
TableofContents
2 2F MS-SPRing analysis
3 2F MS-SPRing user commands
13
19
Switchtonotesview!
SystemOperation2F-MS-SPRINGmanagement

3JK Issue 03
Switchtonotesview!
SystemOperation2F-MS-SPRINGmanagement

3JK Issue 03
1 Introduction on 2F MS-SPRing


3JK Issue 03
Principles
Overview of the ring Node A Node B

(max 16 nodes)
Node D Node C
Detailed view of one span

Node A Node B
Section overhead
Working channels
STM-16 fiber: Protection channels
Working channels: AU4 #1-8
Protection channels: AU4 #9-16
Section overhead
Working channels
STM-64 fiber:
Protection channels
Working channels: AU4 #1-32
Protection channels: AU4 #33-64

A 2F MS-SPRing consists of a set (2 to 16) of Network Elements forming an STM-N ring.

The capacity of the Ring can be STM-16 or STM-64.
NEs are connected by means of two optical fibers, one for the clockwise direction (East output to West
input) and the other for the counter-clockwise direction (West output to East input).
The pair of connections between two adjacent NEs is called SPAN.
It is possible to fully describe the topology of the ring by the ordered list (in clockwise order) of the
Position identifiers of the NEs that compose the ring itself.
Principles on STM-16 level (similar on STM-64 level):

The bandwidth of a 2F MS-SPRing is split into “working” (AU4#1 to AU4# 8) and “protection” (AU4#9
to AU4#16) channels.
AU4#1 is protected by AU4#9; AU4#2 by AU4#10; till AU4#8 that is protected by AU4#16.
The “working” capacity is used to carry the traffic in normal condition, while the “protection”
capacity is used in case of failure.
A single NE can be involved in more 2F MS-SPRing protection architectures, through different ports.

3JK Issue 03
Failure study
LOS
LOF
PROTECTED
SIGNAL Switch Bridge Switch MS-AIS
MS-ExBER
MS-DS
E W E W
Bridge
1 2 3
W E
request
intermediate
E W
W E W E
6 5 4
WORKING CHANNELS 1 fiber carries both

PROTECTED
PROTECTION CHANNELS types of channels SIGNAL
All protecting AU4s are put in pass-through in the 1st, 4th, 5th and 6th NE
In case of Multiplex Section (MS) alarm the APS for 2F MS-SPRing uses a synchronized sequence of
“bridge” and “switch” operations that modify the internal connections of the two NEs adjacent to the
failure and permit the “high priority” traffic to be restored.
The dialogue between the Nodes of a ring can take place if each NE knows the “Node ID” of the others.
Knowing the Node ID means to be acquainted with the Ring Map, that is the sequence of the NEs in the
ring (ring position).
Only the NEs adjacent to the failure are interested to the “switch” and “bridge” functions while for all
other NEs the final configuration is a “pass-through” of all “protection” AU4s.
Each Node of a ring can be in one of the following status:
No Request:
The protection is not activated.
Intermediate:
The protection is activated but the Node is not adjacent to the failed span. The AU4s of the
protection capacity and the bytes K1-K2 are put in pass-through.
Request:
The protection is activated and the Node is adjacent to the failed span.
Switching criteria:
Signal Fail: LOS, LOF, MS-AIS, MS-ExBER
Degraded Signal: MS-DS
The Node that detects the failure is called Tail-end.

The other Node adjacent to the failure is called Head-end.

3JK Issue 03
Squelching
PORT 3 PORT 1 PORT 2 PORT 4

AU4#1 AU4#1 AU4#1 AU4#1
BRIDGE SF/SD SF/SD SWITCH
Side W Side E
Isolated BRIDGE
SWITCH E W E W
Side W Node Side E
1 2 3
W E
AIS on AIS on
AU4#9 AU4#9
E W
AIS ON AIS ON AIS ON

AU4#9 AU4#9 AU4#9
Pass-Through W E Pass-Through W E Pass-Through
6 5 4
WORKING CHANNELS 1 fiber carries both

PROTECTION CHANNELS types of channels

The Squelching function is triggered when a Node that carries Drop/Insert streams remains isolated
because of a double failure.
In order to avoid misconnection, squelching function inserts an AIS signal, instead of the user signal,
on protection channels transmitted by the Nodes adjacent to the isolated one. These AU4s are said
to be “squelched”.
Description of the example:

Before Node 2 isolation because of the double failure, the following connections were active using
the AU4#1:
Stream between Port 3 and Port 1
Stream between Port 2 and Port 4
After a second failure, the Nodes adjacent to the isolated Node 2 send AIS on the protection
channel AU4#9 (or Au4#33 in case of STM-64 ring) by means of the squelching function.
This avoids misconnection between Port 3 and Port 4.
To insert the AIS correctly, the algorithm which handles this protection must be provided with
routing information. This information is supplied by means of squelching tables. 1350OMS-SDH
compiles the squelching tables for all the ports of the ring’s NEs.

3JK Issue 03
SNCP vs 2F MS-SPRing: bandwidth
2F MS-SPRing SNCP
AU4#1 AU4#1
1 2 1 2
AU4#1 AU4#1 AU4#1 AU4#1
AU4#1 AU4#1
4 3 4 3
• 4 x bidirectional Drop/Insert • 1 x bidirectional Drop/Insert

• Implicit protection provided by 2F MS-SPRing • Protection route configured by user
Either cases: 4 x AU4 used bandwidth

2F MS-SPRing is a shared protection since each AU4 of the working capacity can be dropped and
inserted in each span of the ring, but the relevant AU4 of the protection capacity can protect one
connection at a time.
2F MS-SPRing exploits the ring bandwidth better than SNCP does:
In 2F MS-SPRing a connection between two ports reserves resources (AU4s) just on one side of the
ring.
instead SNCP reserves resources on both sides of the ring.

3JK Issue 03
Blank Page


3JK Issue 03
2 2F MS-SPRing configuration and
analysis


3JK Issue 03
2 2F MS-SPRing configuration and analysis
NPA creation
1. Actions OTN Create NPA 2F-MS-SPRing


3JK Issue 03
NPA creation [cont.]
Choose the ring’s

PCs
Implement
NPA list NPA
Search

OTN

NPAs

3JK Issue 03
NPA view
NPA view
Select the NPA
Search NPA
View Protection blocks
Properties of Node 171B’s
protection block
W E W E W E
Node Pos. = 0 Node Pos. = 1 Node Pos. = 2
W E
E W
W E

1350OMS-SDH automatically creates the Ring Map in each Node. The Ring Map puts in relation the
Nodes’ Position in the ring with the Nodes’ identifier. So that each Node knows where the other Nodes
are.
1350OMS-SDH elects the first Node (Node Position=0) and assigns his ports the East or West role. The
second node (Node Position=1) is the Node connected to the first Node’s East side. And so on.

3JK Issue 03
Protection Block view
Select a protection block Search
MS Protection Blocks View
MS-Trail
Reliable
MS-TTP
(R)
MS-Trail Protection
Unreliable block
MS-TTP
(U)
Port
W E
Physical Connection
A Physical Connection has usually one MS-Trail that manages all the AU4s. The MS-Trail is said
Unreliable. The MS-Trail’s user label is obtained by appending the PC’s user label and the letter “U”
(Unreliable).
A Physical Connection involved in 2F MS-Spring supports two MS-Trails with half AU4s: one Unreliable
and the other one Reliable.

3JK Issue 03
Protection Block list
Select the NPA Search 2f MS Protection blocks
Protection block list


3JK Issue 03
Span failure
171B
W E
E W
W E
Media
In the NPA list, check the “Switch Failure
status” attribute: it’s “switchOn”
LOS E
alarm: Switch Active W
alarm: Media Failure

In the protection block list, check
171B 172B 170B
the “Switch Position” attribute:
W E W E W E
• 171B: Bridge&Switch West
B&S B&S • 172B: Bridge&Switch East
W E PT
• 170B: Pass-Through

The Paths and the HO-Trails crossing the alarmed span are re-routed, therefore they are not alarmed.
In the routing display anyway the new route is not represented.

3JK Issue 03
Node isolation
Node 171B is isolated
alarm: Switch Active
alarms: Media Failure
171B 172B 170B

W E W E W E
B&S B&S
End E W
W E
Exclamation mark
E W Protection block list
W E
In the NPA list, check the “Switch

status” attribute: it’s “switchOn”

As effect of the squelching tables set by 1350OMS-SDH upon HO-Trail definition, the AU4s that
enter/exit the ring from the isolated node are squelched, that is they carry AU4-AIS. Thus, the Paths
and the HO-Trails that make use of the squelched AU4s are alarmed: “Transport failure” on Path/Trail;
“SSF” on NAPs and CAPs.

3JK Issue 03


3JK Issue 03
Available commands
• Manual E / Manual W
• Forced E / Forced W
• Lockout protection E / Lockout protection W
• Lockout working E / Lockout working W
and the corresponding release commands
Select a Protection Block Actions

Manage Switch …

The priorities are (starting from the lowest):

Manual
Failure
Force
Lockout
The user commands are used for maintenance activity.
Moreover, the user can release the Wait to Restore time (WTR) West and East.
to modify WTR: select a protection block Actions wait to restore time Change WTR. Set the
same value in every Node.
default WTR=5 minutes.
When two commands are performed one after the other, the one with higher priority cancels the effect
of the previous one.

3JK Issue 03
Manual
“Manual East” brings the same
Manual East Bridge&Switch and Pass-through operations
W E as a failure on the East side does
E W Protection block list
W E
alarm: Switch Active
Manual East
171B 172B 170B
W E W E W E In the NPA list, check that:
• “Switch status” is “switchOn”
B&S B&S • “Operator Command” is “Present”
W E PT

Manual East and Force East simulate a failure on the E side: the NE this command is applied to performs
a Bridge&Switch on the West side.
Manual West and Force West simulate a failure on the W side: the NE this command is applied to
performs a Bridge&Switch on the East side.
The manual command performed in a span influences the whole ring. A failure occurring in another
span removes the effect of the Manual command because of the priority.

3JK Issue 03
Lockout protection
“Lockout Protection” issued on an interface prevents the protection

channels of the span the interface belongs to from carrying traffic
Span C Lockout
protection E
In case of a failure in Span C: 171B
W E
• Paths 1 and Path 2 are lost;
Span A
they can not use Span A as
protection.
P P
• Path 3 is not affected by the a a
t Path 2 t
failure. E h h W
1 3
170B 172B
W E
Span B
Interface with
blocked switch

Lockout Protection:
it disables the protection channels along the span where the command is issued.
If you have a lockout protection command and a ring failure:
the ring protection is served if this ring failure occurs along the same span.
the ring protection is not served if the ring failure occurs in another span.

3JK Issue 03
Lockout protection [cont.]
171B 172B 170B
W E W E W E
Lockout
End End PT
protection E
Protection block list
Lockout
protection E
W E
In the NPA list, check that:
E W
• “Operator Command” is “Present”
W E


3JK Issue 03
Lockout working
“Lockout Working” issued on an interface prevents the protection mechanism
from being triggered for the failures detected by the interface itself
Lockout Working E
on 171B
Span C
+
Span A
W 171B E Lockout Working W
on 172B
P P
a a
t Path 2 t
E h h W In case of a failure in Span A:
1 3 • Paths 2 and Path 3 are lost.
170B 172B • Path 1 is not affected by the
failure.
W E
Span B
Interface with
blocked switch

The node that detects the failure is called Tail-end.

The other node adjacent to the failure is called Head-end.
Lockout Working:
If the node is Tail-end, the lockout working command disables the protection mechanism.
if the node is Head-end, the protection is triggered (protection not disable).
If the lockout working command and a ring failure occur along different spans, the ring protection is
served (protection not disable).
If you want to completely disable the ring protection, also in case of failure on both directions, it’ s
necessary to command a lockout working on both the span’s extremities.

3JK Issue 03
Lockout working [cont.]
Lockout Lockout Without failure

Working E Working W
W E W E W E
Protection block list Lockout

Working E
Lockout
Working W
W E
In the NPA list, check that: E W

• “Switch status” is “switchOff”
• “Operator Command” is “Present” W E


3JK Issue 03
Lockout working [cont.]
With failure
Lockout
Lockout Working W
Working E
W E W E W E
End End PT
Lockout
Working E
Lockout
Working W
W E
Protection block list In the NPA list, check that: E W
• “Operator Command” is “Present” W E


3JK Issue 03
Exercise
Create a 2F MS-SPRing NPA

Check the NPA View
Generate failures on the Physical Connections
Apply user commands


3JK Issue 03
End of Module
2F-MS-SPRING management


3JK Issue 03
@@SECTI
Section 2
System Operation
Module 7
Advanced operation
3JK Issue 03
1350OMS

3JK Issue 03
Blank Page

System Operation Advanced operation
Document History

3JK Issue 03
Module Objectives
Manage Path and HO-Trail constraints

Disable/Enable the Node Download status
Reroute Path and HO-Trail
Add/Remove legs for broadcast Path
Upload the Paths/Trails from the NEs
Set up and manage X and Y Paths


3JK Issue 03


3JK Issue 03
Page
1 Constraints for Path and HO-Trail 7

TableofContents
2
3
4
Path/Trail Rerouting
Download Enabled/Disabled
Split/join
19
23
27
5 Trace Identifier 45
5.1 Trace Identifier for Path and HO-Trail 47
5.2 Trace Identifier for Physical Connection 53
6 Add/Remove legs for broadcast Path 59
7 Loopback Management 69
Switchtonotesview!
8 Path/Trail take-over 73
SystemOperationAdvancedoperation

3JK Issue 03
Page
SystemOperationAdvancedoperation

3JK Issue 03
1 Constraints for Path and HO-Trail


3JK Issue 03
General concepts
The user can force Paths and HO-Trails to follow a desired route in the
Network by adding Constraints.
Many types of objects can be used as constraint: NPA, Node, Physical

Connection, MS-Trail, HO/LO Link Connection, HO/LO CTP, HO-Trail,
Paths, Port.
For each constraint the user must specify: “Use” as “Main”, “Use” as
“Spare”, “Do not use” or …
Though constraints can be assigned whatever the Path/Trail’s

configuration state is (defined, allocated, implemented,
commissioned), constraints are taken into account just during the
ALLOCATION phase, that is when the route is calculated.

The allocation of a Path/Trail with constraints returns “The action is terminated with some
warnings” as Operation Status. It just means that some constraints have been taken into account.

3JK Issue 03
Allowed constraint objects for HO-Trail/HO-Path
NPA:
Inside an NPA (SNCP or 2F MS-SPRing), the user can select the HO-Link
Connection (AU4) to be used over all the engaged Physical Connections.
Node
Physical Connection
MS-Trail
Other HO-Trails/HO-Paths
HO-CTP:
Only for Real HO-CTP: select it and issue “Send To”
For Real and Potential HO-CTPs: select the STM-N port and issue “Send To”.
Edit the Position attribute in the Constraints wizard.
HO-Link Connection:
Only for Real HO-LC: select it and issue “Send To”
For Real and Potential HO-LCs: select the MS-Trail and issue “Send To”. Edit
the Position attribute in the Constraints wizard.

To specify an HO-Link Connection (Au4), the user must write the Au4 number as “Position” attribute.
Example: to select the 2nd Au4 the user must write 02
NPA (Network Protection Architecture). Example for a ring that supports SNCP protected HO
Trails/Paths.
to use the same AU4 on each link of the ring, both on main and spare legs
configure an SNCP NPA
it must encompass all the Physical Connections that constitute the ring
all the Physical Connections must have the same rate, e.g. STM16
set “Time Slot Interchange” to “Forbidden”
assign the NPA to the Trail/Path as constraint
the desired AU4 number (e.g. 03) as “Position”
“main” as “Constraint Section”

3JK Issue 03
Allowed constraint objects for LO-Path
NPA:
Inside an NPA (SNCP or 2F MS-SPRing), the user can select the LO-Link
Connection (TU3, TU12) to be used over all the engaged Physical Connections
Node
Physical Connection
HO-Trail
Other LO-Paths
LO-CTP:
Only for Real LO-CTP: select it and issue “Send To”
For Real and Potential LO-CTPs: select the STM-N port and issue “Send To”.
Edit the Position attribute in the Constraints wizard.
LO-Link Connection:
Only for Real LO-LC: select it and issue “Send To”
For Real and Potential LO-LCs: select the HO-Trail and issue “Send To”. Edit
the Position attribute in the Constraints wizard.

Besides “Send To”, that is available from any window types (Lists and Graphical), from some windows
it’s possible to drag/drop an object.
To specify a LO-Link Connection (TU3, TU12), the user must write the LO-LC number as “Position”
attribute. The format is as follows.
In case of TU3, the notation is: AU4/tu3
For example, in order to select the position
AU4#4; tu3#1
the user must write: 04/1
In case of TU12, the notation is: AU4/K/L.M, where:
K = TUG3#(1…3)
L = TUG2#(1…7)
M = TU12#(1…3)
For example, in order to select the position
AU4#4; TUG3#2; TUG2#5; TU12#1
the user must write: 04/2/5.1
Real and Potential resources. Example: when allocating a 2Mb/s Path over an HO-Trail payloaded as
(TU3,TU3,TU12), the routing algorithm selects the potential TU12(1,1,1) even if the first TUG3 is
structured as TU3 and not as TU12s. The following Path implementation will modify the payload into
(TU12,TU3,TU12); TU12(1,1,1) becomes real. That’s possible if the Dynamic Payload configuration is
enabled (see the module that deals with the HO-Trail configuration).

3JK Issue 03
Assigning constraints starting from Path/Trail creation
Procedure for adding constraints to HO-Trail:

1. Create the HO-Trail setting the “Allocate, implement and payload”
parameter to “no” in order to only define the HO-Trail.
2. Add a Constraint (for example an HO-Link Connection: AU4#05) by means of
the Constraints Wizard.
3. Life cycle management: allocate and implement the HO-Trail.
4. Carry out the Payload configuration.
Procedure for adding constraints to Path:

1. Create the Path setting “Allocation Rule” to “User” in order to only define
the Path.
2. Add a Constraint (for example a LO-Link Connection: TU12#05/1/2.3) by
means of the Constraints Wizard.
3. Life cycle management: allocate and implement the Path.


3JK Issue 03
Assigning constraints: example for Path
Objective of the example: create a

Path between 63B and 165B passing
through 164B.
164B can be chosen as constraint.
In Path Creation, set

“Allocation Rule” to “User”

If “Allocation Rule” is set to User and “Implementation Rule” is set to Automatic, the issuing of
Allocate command on the defined Path allocates and implements the Path as well.
The Path/Trail properties tells the “Active Constraint Set”. Look for the “Constraint Set” attribute in
the Routing section. If no constraint has been associated, “Constraint Set” is equal to “initial”.

3JK Issue 03
Assigning constraints: example for Path [cont.]
1. To open the Constraints wizard: select the Path
Actions Constraints Edit Constraints
2. Drag/drop the Node or use the option “Send To…”
4. “Use”
3. “main”
5. Apply
Leg Number: for broadcast Paths Channel Number: for concatenated Paths
A Constraint Set is made of one or more constraint items collected in the Constraint List.
About Constraint Set:
It’s defined over a specific Path/Trail.
It’s possible to define more Constraint Sets for a Path/Trail.
A constraint belonging to a Constraint Set can belong also to another Constraint Set.
Only a Constraint Set can represent the working constraints over the Path/Trail.
In other words, the user is allowed to store more Constraint Sets to a single Path/Trail, activating
them from time to time, but just one of them can be activated at a time.
The Active Constraint Set will be taken into account in the next Path/Trail allocation (rerouting, add
protection, add leg,…).
The user has to type the name of one of the available “Constraint Sets” into the “Active Constraint
Set” field in order to get it operational. If what is written in the “Active Constraint Set” field doesn’t
match any “Constraint Sets”, no constraint will be taken into account in allocating the Path/Trail.
Channel Number:
it concerns Path with virtual concatenation.
it specifies the Server Trail to which the constraint is to be applied.
the Constraint Set must be assigned to the concatenated Path and not to the single Server Trail.
For details about the Constraints Management wizard, see the Notes page of the next slide.

3JK Issue 03
De-assigning constraints
1. Select the constraint

The new constraints (no
2. Click the red cross constraint) are applied
to the Path just during
3. Apply the ALLOCATION phase
Constraint Constraint Note

Section Type
Main Use The constraint object has to be used in the main route.
Spare Use The constraint object has to be used in the spare route.
Main dontUse The constraint object has NOT to be used in the main route.
Spare dontUse The constraint object has NOT to be used in the spare route.
Service Use The constraint object has to be used as Service for a D&C protected trail/path.
Service dontUse The constraint object has NOT to be used as Service for a D&C protected
trail/path.
Common Overlap Applicable for path/trail. The trail must use the same physical connections used
by the trail given as constraint. The path must use the same physical
connections and trails used by the path given as constraint. The main route
must overlap with the main route of the trail/path given as constraint; the spare
route must overlap with the spare route of the trail/path given as constraint.
Common Extended Applicable for LO path. The path must use the same physical connections and,
Overlap if available, the same trails used by the path given as constraint; if the same
trails are not available, the path can use equivalent trails. The main route
overlaps with the main route of the trail/path given as constraint; the spare
route overlaps with the spare route of the trail/path given as constraint.
Common Disjoint Applicable when the constraint object is a trail or a path. The main and spare
route must be disjoint from the trail/path given as constraint.
“Use As Sink” and “Use As Source” apply to CTPs.

3JK Issue 03
Constraint Set management
A Constraint Set can contain several constraints (e.g. all the Nodes to
traverse)
The default Constraint Set is “initial”
as default it is empty
the user can add constraints to it
Further Constraint Sets can be created. One at a time can be active.
Path properties


3JK Issue 03
Constraint Set creation
3. If the new set is to be 2. Edit the name for

the active one, edit also the Constraint Set
here its name;
otherwise leave “initial”
1. Click
this icon
4. Apply
The new Constraints Set, if declared
as Active, is taken into account just
during the ALLOCATION phase

3JK Issue 03
Constraint Set deletion
2. Select all the

constraints and ...
3. ... delete them
1. Select the Constraints Set to 4. Apply

delete in the drop down list

By deleting the “Constraint Set” that is currently the “Active Constraint Set”, “Active Constraint Set”
still shows the deleted one. In this case, “Active Constraint Set” is not effective and no constraint is
taken into account by the next allocation.

3JK Issue 03
Copy and Paste constraints between Paths/Trails
1. Let’s apply the constraints of First_Path to Second_Path, too.
2. Select First_Path Actions Constraints Copy

Path list
3. Select Second_Path Actions Constraints Paste

Path list

Port/Trail constraints with the payload position specified cannot be copied.

Example for LO-Path:
if the constraint of First_Path specifies the TU12 (e.g. --/1/2.3), the Paste over Second_Path
fails.
Example for HO-Trail:
if the constraint of First_Trail specifies the AU4 (e.g. 03), the Paste over Second_Trail fails.

3JK Issue 03
Exercise 1: constraints for LO-Path
1. Create an unprotected LO-Path, between two adjacent Nodes.
2. Set a previously created HO-Trail as constraint.
3. Get information to verify that the Path is properly created through

the specific HO-Trail.
Question: which is the involved TU12#?
4. Replace the previous constraint by a specific TU12#.

Question: is it taken into account immediately?
5. If necessary, manage the life cycle of the Path to take the constraint
into account.
6. Get information to verify that the new constraint is taken into

account.


3JK Issue 03
Exercise 2: Broadcast Path creation with constraints
1. Create a broadcast LO-Path with al least two legs
2. Assign different routing constraints to the different legs


3JK Issue 03
2 Download Enabled/Disabled


3JK Issue 03
Rationale
Two ways of operating by 1350OMS-SDH are provided to the user: the

Node can be set into “Download Enabled” or “Download Disabled”.
Node in Download Enabled:

it’s the default and the normal mode.
when operating on Node from “Physical” or “OTN” environment, the NE’s MIB
is modified according to the requests issued by 1350OMS-SDH.
Node in Download Disabled:

the Node configurations issued by 1350OMS-SDH are not sent to the NE but
are buffered in the 1350OMS-SDH’s database. The “consistency status” of the
addressed TPs is set to “not aligned”.
when the Node is set back to Download Enabled and the NE is reachable, the
“not aligned” configurations are automatically sent to the NE.
used for testing the outcome of a new configuration before implementing it
in the NEs and for special procedures like consistency operations.

Example:
The user implements a Path involving Nodes in Download Disabled.
The Path gets implemented in 1350OMS-SDH’s database but the NE’s MIB is not configured
accordingly.
By enabling the Node’s download, the new connections are created in the involved NEs as well.
Consistency operations: comparison between the 1350OMS-SDH’s database and the NE’s MIB.
MIB: Management Information Base (database)

TP: Termination Point (NAP, CTP, ...)

3JK Issue 03
How to change the Download status
1. Let’s use the Node View: select the With green flag:
Node Search OTN Node View Download Enabled
Without green flag:

Download Disabled
In the Map, too

(Technology: SDH)
2. Just click the icon

OR
Select the Node
Actions Configure
Download Enable
or Disable

The “Configure Download Status” icon is available in several graphical windows, such as Map and
Routing display.

3JK Issue 03
Blank Page


3JK Issue 03
3 Path/Trail rerouting


3JK Issue 03
Generalities
An existing and already allocated/implemented Path/Trail can be

rerouted based on:
a newly configured and activated Constraint Set
the Path/Trail original routing saved as Constraint Set
The rerouting can be performed:

End-to-end
the new route may engage resources different from the ones used for the current
route between the two end-Nodes.
On a specific segment
the new route may engage resources different from the ones used for the current
route, but only between two points defined by the user. The rest of the resources
are kept.
Between two Physical Connections
all the traffic on a Physical Connection is moved to another Physical Connection.

As usual, the rerouting implies the routing algorithm. The routing algorithm:
takes into account the constraints provided by the customer
computes a new route on cost and free resources basis
For example, end-to-end rerouting means that the new route computed by the routing algorithm may
have some resources in common with the ones used by the current route because of resource
shortage.
Server Trails rerouting:

in case of concatenated Path, the Constraint Set must be assigned to the Path specifying the Server
Trail number as Channel Number.
by issuing the Reroute command on the Path, 1350OMS-SDH tries to reroute all the Server Trails,
but the rerouting succeeds only for the ones for which a constraint has been specified.
by issuing the Reroute command on the Server Trail, 1350OMS-SDH reroutes only that Server Trail.

3JK Issue 03
Saving the current routing as a Constraint Set
board#34 board#36
port#1 port#1
1. Select the Path/Trail Actions Other

Route Copy Save as Constraint Set
2. Open the Constraints

wizard. The “LastRoute”
Constraint Set describes
the routing of the
Path/Trail.

It is possible to save as a Constraint Set the current routing of an allocated, implemented, or

commissioned Path/Trail. The automatically created Constraint Set is named “LastRoute” and is
constituted by some constraints that describe the current routing.
LastRoute Constraint Set:
can be invoked to restore the original route after a rerouting: “Revert to Saved”. It’s not necessary
to set it as “Active Constraint Set”.
can be deleted: “Delete Saved”.
When the LastRoute Constraint Set is created, the Path/Trail properties reports “Saved” in the
“Route” Routing attribute.

3JK Issue 03
Blank Page


3JK Issue 03
3.1 End-to-end Path/Trail rerouting


3JK Issue 03
Procedure
For sake of safety, save the current Path/Trail route

Select the Path/Trail Actions Other Route Copy Save as Constraint
Set
Configure the Active Constraint Set in the Constraints wizard
Perform the rerouting
Select the Path/Trail Actions Modification Reroute
Choose among:
Allow traffic impacts
Allow traffic impacts (only allocation)
Avoid traffic impacts
Avoid traffic impacts (only allocation)
Avoid traffic impacts rerouting types are suitable for:

allocated Path/Trail
idle Server Trail of concatenated Paths
ASON NPA
To reapply the original route, if necessary
Actions Other Route Copy Revert to Saved

Commands with “Only allocation”

the Path/Trail becomes Partially Implemented.
After rerouting, the user has to implement the Path/Trail.
Commands without “Only allocation”
the rerouted Path/Trail is implemented
Avoid traffic impacts rerouting types for idle Server Trails of concatenated Path:
the Constraint Set must be assigned to the Path specifying the Server Trail number as Channel
Number.
the Reroute command must be issued on the Server Trail.
Revert to Saved: it can be applied only if the Path/Trail is implemented.

3JK Issue 03
Example
Map
Constraint to apply:
use Node 165B
Current HO-Trail routing display
Constraints wizard
1. Save the
current
route

3JK Issue 03
Example [cont.]
2. Activate a
Constraint Set
3. Reroute Constraints wizard
Rerouted HO-Trail routing display
Map


3JK Issue 03
Undo
If required, it’s possible to issue “Undo”. It’s available when the

Path/Trail is Partially Implemented because of:
“Only allocation” rerouting
rerouting failures

Undo is available both for end-to-end and segment rerouting.

3JK Issue 03
Blank Page


3JK Issue 03
3.2 Path/Trail segment rerouting


3JK Issue 03
Procedure
1. For sake of safety, save the current Path/Trail route

Select the Path/Trail Actions Other Route Copy Save as Constraint
Set
2. Configure the Active Constraint Set in the Constraints wizard
3. Perform the rerouting

Select the Path/Trail Actions Modification Path/Trail Modification
Tool
select the two points of the current route between which a new piece of route must
be computed
4. To reapply the original route, if necessary

Actions Other Route Copy Revert to Saved


3JK Issue 03
Example
Map
An HO-Trail between 63B and C322
passes through 164B
Objective: make the HO-Trail pass
through 165B as far as the right segment
is concerned
To keep
To modify passing 165B For HO-Trails, also

through 165B
the CAP changes
(current route)
To keep To modify passing

through 165B
For HO-Trails, also the CAP changes when the end-point of the HO-Trail is selected as rerouting point.
It changes because the CAP corresponds to the STM-N port. In case of Path, if the NAP is selected as
rerouting point, the NAP doesn’t change.

3JK Issue 03
Example [cont.]
1. Select the
Path/Trail
Actions
2. Reroute
Modification
Path/Trail
Modification 3. Choose the
Tool segment
end-points
4. Yes/No
5. Yes/No
6. Apply
(current route)
To modify passing
To keep through 165B

Only allocation:
the “to keep” segment is kept implemented
the “to modify” segment is just allocated
the Path/Trail becomes Partially Implemented
the user has to implement the Path/Trail to implement the allocated segment, too

3JK Issue 03
Procedure

(before rerouting)

(after rerouting)


3JK Issue 03
Exercise: Path rerouting
1. Create, allocate and implement a Path
2. Create a new set of constraint
3. Reroute the whole Path on the new set of constraint
4. Reroute a specific segment of the Path


3JK Issue 03
3.3 Path/Trail rerouting between two


3JK Issue 03
3.3 Path/Trail rerouting between two Physical Connections
Rationale
This feature allows the user to move the HO-Paths, the HO-Trails (with
all their supported LO-Paths), and the HO-Server Trails crossing a
Physical Connection to another one.
The two Physical Connections must be between the same two Nodes.
A purpose of this feature is to allow the substitution of the two boards

of a link between two NEs with two new boards with an higher rate.

Such a feature is also called “link capacity upgrade”; i.e. the traffic can be moved to an
infrastructure having an higher capacity with respect to the original one. The traffic moving can be
done also between two Physical Connections that are already in use.

3JK Issue 03
Example
ST
Physical Connection Structure M
-4
STM-4
HO-Trail
Path
AU4-2V
STM-16
HO-Trail
ST
M
Move HO -1
6
objects
STM-4
STM-16
HO-Trail
HO-Trail
Path AU4-2V
The destination Physical Connection already supports an HO-Trail in position #1.

3JK Issue 03
Procedure
1. Select the PC stm4

Actions Path / HO
Trail management
Reroute paths
2. Select the PC stm16

3. In this example,
choose Compact
Payload Position
4. Yes/No
5. Yes/No
It refers to stm4
6. Apply

Reroute Operation Type:

Preserve Payload Position: in the destination Physical Connection, the Paths/Trails are allocated
keeping the same payload position (AU4) as in the source Physical Connection, if possible. The
rerouting succeeds for the Paths/Trails for which the position is free; whereas it fails for the
Paths/Trails for which the position is already occupied.
Compact Payload Position: in the destination Physical Connection, the Paths/Trails are allocated
applying the usual allocation criteria.
In this example:
Preserve Payload Position manages to allocate just the objects in position #2 and #3, because the
position #1 is already engaged in stm16.
Compact Payload Position manages to allocate all the three objects.
Disable Routing Administrative State: if set to Yes, the source Physical Connection will not be used to
allocate new Paths/Trails. (It can be modified also in this way: select the Physical Connection
Modify).
If some user constraints are associated to the Paths/Trails, they are not taken into account in the
rerouting.
In case of broadcast or other complex Paths, the reroute is not guaranteed.
Rerouting is performed in best effort policy. In other words, 1350OMS-SDH tries to move all
Paths/Trails from the source to the destination Physical Connection and in the end informs the user
whether all or some Paths/Trails have been moved.
Rerouting causes traffic loss for the not protected Paths/Trails. The user has to be aware about this
risk. For this reason, before the action is started, a warning message informs him. The warning
message is displayed as dialog box; the user has to accept the risk.
Also commissioned Paths can be rerouted.

3JK Issue 03
Specific application for clustering operation
As a specific application, the Reroute Physical Connection wizard can be used

in situation like the one depicted in the following picture, where some NEs are
clustered into one:
After the clustering operation the Physical Connections linking the clustered NEs (i.e.
A2-B2, A3-C3 and B3-C2) are not useful, but cannot be removed because they carry
traffic.
The Reroute Physical Connection wizard can be used to remove the Paths/Trails from
the Physical connections in “loopback”, cross-connecting them into the clustered Node
between the proper CTPs.


3JK Issue 03
Specific application for clustering operation [cont.]
For example, after the clustering operation, a Path could be routed as in the
left part of the following picture, that is
A1 A2 B2 B1
By using the Reroute Physical Connection wizard, this Path is rerouted as in the
right part of the picture, that is:
A1 B1
After having moved all the Paths from the A2-B2 Physical Connection, it can be
manually removed.
In the wizard, select the source Physical Connection and do Apply. Don’t select
any destination Physical Connections.


3JK Issue 03
Exercise: move traffic from/to Physical Connection
1. Create, allocate and implement Trails and Paths between two

adjacent Nodes
2. Create and implement a new Physical Connection between the two

Nodes
3. Move all the Trails and Paths created at point 1 between the two
Nodes on the new Physical Connection


3JK Issue 03
Blank Page


3JK Issue 03
4 Add/Remove legs for broadcast Path


3JK Issue 03
Generalities
A broadcast unidirectional Path can be created in two ways:

by creating a broadcast Path.
by adding new legs to a unidirectional point-to-point Path.
The user can add/remove legs to/from a unidirectional Path by

choosing the sink end-points.
The current Path status must differ from “Commissioned”.
The new leg can be SNCP protected.


3JK Issue 03
Unidirectional Path
Source Sink Sink NAP (current) Path list double
NAP NAP to add click
HO-Trail HO-Trail
Map
Current Path
Leg to add
Sink
NAP
Source
NAP
Current Path

To create a unidirectional Path:

in step 1 of the wizard, choose “Unidirectional” as “Path Type”.
in step 2 of the wizard, take care about which is the Source Node and which is the Sink Node.
To get the Path’s NAPs in the Path list, double click the Path.

3JK Issue 03
Add leg
1. To add an end-point: select the Path

Actions Modification 2. Choose
Modify End Points “Add Leg”
3. Choose the desired

state and protection
4. Next

3JK Issue 03
Add leg [cont.]
5. End Point inside SDH

No: an External Network is involved in the leg
Yes: otherwise
6. Select
the Node
7. Select the NAP

(optional)
8. Apply


3JK Issue 03
New leg
Path list
Broadcast Path
New NAP
164B fulfils a Point-to-Multipoint

The two legs share this LO cross-connection
Link Connection
New
leg


3JK Issue 03
Remove Leg keeping NAP
1. Select the
operation
2. Next
3. Select the
sink NAP 4. Apply
to remove

By issuing “Remove Leg keeping NAP”, the addressed leg is not completely deleted, but gets a state
similar to the one of a Defined Path: the routing (LO Link Connections, ...) is not provided and the
Sink NAP is “Not Connected”. Therefore, the Sink NAP can not be used to create other Paths. The
Source NAP is still used by the other legs.
By issuing “Remove Leg”, the leg is completely deleted: also the Sink NAP is released (Idle).
“Remove Ends” and “Add Ends” are suitable for X and Y Path types. They are dealt onwards in this
module.

3JK Issue 03
Remove Leg keeping NAP [cont.]
The NAP that belongs

to the removed leg is
“Not Connected”.
It can not be used to
create other Paths.
Removed leg After “Remove Leg

keeping NAP”, apply
“Remove Leg” to
release the Sink NAP

Even if one leg out of the two has been removed, the Path is still Broadcast. To completely delete
the removed leg and release its Sink NAP, the user must apply “Remove Leg” for the already
removed leg.

3JK Issue 03
Exercise
1. Create a broadcast Path with two sink end-points.
2. Check the legs’ routing: do the legs share any network resource?
3. Add a leg to the broadcast Path.
4. Remove a leg (not the added one).


3JK Issue 03
Blank Page


3JK Issue 03
5 Path/Trail take-over


3JK Issue 03
Generalities
Path/Trail take-over allows to automatically create Paths/Trails in

1350OMS-SDH by uploading the cross-connections from the NEs’ MIB.
Take-over looks for the Paths/Trails that make use of the objects
specified by the user. The objects can be:
NAP, CAP, LO/HO-CTP, LO/HO-LC, PDH/SDH port, Physical Connection, Node
Take-over is suitable for Point-to-Point and SNCP Paths/Trails.
Ethernet/Data TPs are not taken into account by the take-over

procedure.

MIB (Management Information Base): NE’s database

3JK Issue 03
Operation
2. To add an object, use

1. To open the wizard: “Send To” or drag/drop
Actions OTN
Discover Connection
3. Choose the desired final state
for the discovered
Paths/Trails
4. Apply

By choosing any “Object type” and setting “Required Configuration State” to “Implemented”, both
HO-Trails and Paths are uploaded.
In order to first upload HO-Trails, and then Paths, it’s possible to apply the following procedure:
discovery with “Object type” = “Node” and “Required Configuration State” = “Allocated”: HO-
Trails are discovered and allocated.
Implement the HO-Trails leaving the payload AU4.
discovery with “Object type” = “HO-CTP” (you can select just the ones with “used direction” =
“bidirectional”) and “Required Configuration State” = “Implemented”: the HO-Trails’ payload is
uploaded.
discovery with “Object type” = “NAP” and “Required Configuration State” = “Implemented”: Paths
are discovered and implemented.

3JK Issue 03
Outcome
Uploaded
Path
Path
HO-Trail HO-Trail
Uploaded
HO-Trails

The discovered Path/Trail has the following characteristics:

the user label is automatically calculated by 1350OMS-SDH.
the ASAP profile is not uploaded, but is set according to the 1350OMS-SDH rules.
the Performance Monitoring are not uploaded, but are started according to the 1350OMS-SDH rules.

3JK Issue 03
6 Handling of X and Y Paths


3JK Issue 03
Blank Page


3JK Issue 03


3JK Issue 03
End-points
Traditional “I” Paths, even if SNCP protected, have only primary end-
points:
a point-to-point “I” Path has a single source NAP or CTP and a single sink NAP
or CTP.
a point-to-multipoint “I” Path has a single source NAP or CTP and several sink
NAPs or CTPs; all of them are primary.
“Y” and “X” Paths have instead, respectively, one or two additional
backup end-points.
Primary end Primary end
Primary end Primary end
“I” path
Primary end Primary end Backup end

“Y” path
Backup end Backup end
“X” path NAP or CTP

The Path end-point is a CTP in case of Not Terminated Paths.
The X configuration is not available for concatenated Paths.
The Y configuration is available also for:

Digital Video Broadcast Paths, concatenated or not.
Broadcast 1GbE Rate Adaptive Paths (broadcast virtual concatenated Paths with 2 source TPs).
Both of these cases are also known as “broadcast Paths with Y legs”.

3JK Issue 03
End-points [cont.]
Primary Primary Backup Backup
OR OR
Sink Source NE 3 Source Sink
Spare Route
NE 4
Ma
NE 2 in Y path
R ou
Backup Spar te
e Ro
Source ute
Network in NE 5
External 1350OMS
NE-A Domain Primary
X path Sink
Primary OR
Source Primary
NE 1
Mai Source
n Ro u
te NE 6
Backup
NE 7 Sink
Primary External NE-B
Sink
X Path:
has two source end-points (primary and backup) and two sink end-points (primary and backup).
is seen as SNCP protected Path having the main route connecting the primary source-sink pair
and the spare route connecting the backup source-sink pair.
Y Path:
has two source end-points (primary and backup) and one sink end-point (primary), or
one source end-point (primary) and two sink end-points (primary and backup).
is seen as SNCP protected Path having the main route connecting the primary source with the
primary sink and the spare route connecting the backup (or primary) source with the primary (or
backup) sink.
The primary and the backup end-points can belong to the same or to different Nodes.

3JK Issue 03
Applications: Path protected outside the 1350OMS domain
Deployed network Main Route

CTP CTP
Network in NE 2
1350OMS domain
NE 1
CTP CTP
Spare Route
NE 3
1350OMS-SDH representation
CTP CTP CTP NAP
CTP
Network in External Network 2
NAP
1350OMS domain
NAP CTP
External Network 1 CTP CTP CTP NAP

External Network 3
X Path

X Path management allows the user to represent in an easy way a scenario like the one depicted in
the figure above:
a protected Path crosses the 1350OMS domain and is terminated in some NEs outside the managed
network. The Path’s route is known only in the managed network and in the boundary interfaces,
but is not known outside the managed network.
The user simply defines the Path by specifying all the boundary CTPs or new NAPs on the External
Networks as end-points. In this way it is not necessary to know the Path’s route outside the managed
network. Yet, if the Path is defined as X Path, the two legs are seen as a main-spare pair.

3JK Issue 03
Applications: Add/Remove path ends
Backup and primary end-points can be added or removed.

In this way, performing a combination of add/remove main or spare and
add/remove Path ends it is possible to perform modifications like this:
Transform an “I” Path

into a new one with a
different Z-end Add Z-backup
Remove Z-primary


3JK Issue 03
Blank Page


3JK Issue 03
6.2 X Path setup


3JK Issue 03
6.2 X Path setup
Create Path wizard
1. In Step 1, choose SNCP or
D&C SNCP as “Protection” 3. Select “No” for each
one of the four end-points
2. Select “Yes” for both because they belong to
Source and Sink External Networks
Primary
Main Route Sink
Primary
Source
Backup
Sink
Backup
4. Configure Primary and Backup Source
for both Source and Sink Spare Route
The Node, Port and Time Slot selection is equal to the one for not terminated Paths.

3JK Issue 03
6.2 X Path setup
Protection e
out
R
in
Ma
Primary Primary
Source Sink
e
Backup out Backup
Source R Sink
a re
Sp

Like in classical SNCP scenario, in case of resource shortage (for example, there’s no Physical
Connection between 165B and 172B) the Main route and the Spare route may result partially
overlapping.

3JK Issue 03
Blank Page


3JK Issue 03
6.3 Y Path setup


3JK Issue 03
6.3 Y Path setup
Create Path wizard
1. In Step 1, choose SNCP or 3. Choose the two source
D&C SNCP as “Protection” end-points (Primary and
Backup). To enable the
2. Choose the source backup end-point
end-point (Primary) selection, choose Yes.
Main
Primary Route
Source
Primary
Sink
Spare Backup
Route Sink

This example features the one-source/two-sink scenario. Y Path can be two-source/one-sink as

well.
The Node, Port and Time Slot selection is equal to the one for not terminated Paths.

3JK Issue 03
6.3 Y Path setup
Main
Primary Route
Source
Primary
Sink
Spare Backup
Route Sink
e
Protection ut
Ro
in
Ma
Primary
Sink
e Backup
ut Sink
Primary Ro
e
Source ar
Sp


3JK Issue 03
Exercise
Using Nodes and External Networks, create an X Path with the following
characteristics:
Primary and backup Source end-points “not inside SDH”
Primary and backup Source end-points in the same External Network
Primary Sink end-point “inside SDH”
Backup Sink end-point “not inside SDH”
Primary route has to use different Physical Connections from the Backup
route’s ones


3JK Issue 03
6.4 Add/Remove Path ends


3JK Issue 03
Generalities
The user can modify the Path type (I, Y, X) by means of the “Modify
End Points” wizard that allows to add/remove end-points:
X = I + two ends
X = Y + one end
Y= I + one end
Y = X – one end
I = X – two ends
I = Y – one end
The end-points to be added can be selected by specifying:

Nodes
NAPs
CTPs
The end-points to be removed (NAPs) must be chosen in a list which is

automatically proposed by the system.


3JK Issue 03
Generalities [cont.]
In the Path to be modified, the added end-points can be:

Simply defined, without cross-connecting them with other resources
In this case, the end-point is “not connected” and its Node is shown in the Path
routing display without links to any other node.
Allocated in a spare route
In this case, the end-point is “connected” and is part of the Path spare route.
So, the user is given two possibilities:

Add end-points simply by defining them (not connected) and then provide the
spare route by means of the “Add protection” command.
Add end-points by allocating them (connected), so automatically allocating
also a spare route and setting an SNCP protection over the Path.
Possible constraints are taken into account in allocating the spare

route, either adding allocated end-points or adding protection after
having defined a not connected end-point.

The following considerations must be taken into account for adding and removing end-points:
if an X or Y Path is at least allocated, the A and Z mains have to be always connected while the
A and Z spares can be not connected.
one or two NAPs (A and Z spare) can exist associated to the Path but not connected.
if a Y Path has the A and Z main connected and the A spare not connected, any main end-point
cannot be removed.
the add protection command over an X Path with the A spare and Z spare not connected
calculates the spare route between A spare and Z spare.
the add protection command on an Y Path with the A (Z) spare not connected calculates the
spare route between A spare (A main) and Z main (Z spare).
the result of the remove protection keeping main on an X Path is still an X Path with the A spare
and Z spare not connected.
the result of the remove protection keeping spare on an X Path is still an X Path where the NAPs
that initially were spare become main and the NAPs that initially were main become spare not
connected.
the result of the remove protection keeping main on an Y Path is still an Y Path with the A spare
(Z spare) not connected.
the result of the remove protection keeping spare on an Y Path is still an Y Path where the A
spare (Z spare) becomes A main (Z main) and the A main (Z main) becomes A spare (Z spare) not
connected.

3JK Issue 03
Add Ends
“I” path “Y” path with two sink ends
add backup
sink end-point
1. Select the Path Actions

Modification Modify End Points
2. Add Ends
3. Choose the final state
4. Next

Example:
add a backup sink end-point to an “I” Path to obtain a “Y” Path with one source end-point
(primary) and two sink end-points (primary and backup).
State of the added end-point:
if the starting Path is implemented, all the three states (Allocated, Defined, Implemented) are
allowed.
if the starting Path is allocated, just Allocated and Defined are allowed.
if the starting Path is defined, just Defined is allowed.

3JK Issue 03
Add Ends [cont.]
1. Select the Sink

Backup node to add
2. Select the NAP

(optional)
3. Apply

3JK Issue 03
Add Ends [cont.]
Primary
Sink
New end-point
Primary Backup Sink
Source
A: source; Z: sink

Path_Y00: it’s the port name of the added end-point. It’s been set by the system because in the
wizard no name has been specified.
If the starting Path was implemented and “Allocated” is chosen as end-point’s state, the Path
becomes “Partially implemented”. Implement the Path.
If “Defined” is chosen as end-point’s state, the Spare route is not computed.
The end-point and its Node are shown, whereas the Spare route is not. The end-point is “not
connected”.
To allocate the Spare route: select the Path Actions Modification Add Protection
“Spare” or “Spare (only allocation)”.

3JK Issue 03
Remove Ends
1. The Path must not be “commissioned”
2. In the first step of “Modify End Points”

wizard, select “Remove Ends”
3. Select the end-point to

remove
4. Apply
Connected end-points (their route is allocated or implemented) can also be removed in
two steps:
1) Remove the protection keeping main (or spare), based on the end-point(s) to be
removed: the spare (or the main) route is deallocated and the relevant end-point
becomes “not connected”.
2) Remove the “not connected” end-point(s) by the “Modify End Points” wizard.
Example above: remove the end-point that has been added in the previous example.
After having removed NAPs, the Path must have at least one NAP A (source) and one NAP Z (sink).
Either Main NAPs or Spare NAPs can be removed.
If the Path is Partially implemented (the Main route is implemented, whereas the Spare route is
allocated) it’s not possible to remove the Spare route’s end-points. To enable the removal, first
remove the Spare route by issuing “Remove protection” “Keeping main” or implement the Spare
route.
It’s possible to remove end-points even if the Spare route is “Implemented”.
It’s possible to remove also end-points whose state is “not connected”, that is their route is not
allocated.

3JK Issue 03
NE Restrictions
The NE doesn’t support protected cross-connections (SNCP) where the NAP is

involved as shown in figure 1. Anyway, 1350OMS-SDH allows to allocate such
kinds of Path, as they can represent a temporary configuration when the user
wants to change the NAPs of a Path.
Here are the steps the user must perform to change a NAP of a Path, using
another NAP of the same Node:
step 1: the Node containing the involved NAPs has to be put in Download Disabled.
step 2: the Link Connections already used by the main route have to be specified as
constraints for the spare one; then issue the Add Ends command with implementation.
step 3: the Remove Ends operation of the main NAP has to be performed.
step 4: the involved Node has to be put in Download Enabled. Just now, to the NE are
sent the removal of the old cross-connection and the creation of the new one (no
request to create protected cross-connection is sent to the NE).
step 1
step 2
step 3
case 2
case 1
NAP primary
figure 1 NAP backup
CTP

3JK Issue 03
Exercise: add/remove Path ends
Create an “I” Path.

Transform the “I” Path into an “X” Path by adding two allocated end-
points.
Transform the “X” Path into a “Y” Path by using only the “Modify End
Points” wizard.
Rebuild the previously created “X” Path.
Transform it into a “Y” Path by:
Removing the protection (comment the Path end-point status in the routing
display)
Removing end-point
Adding protection


3JK Issue 03
End of Module
Advanced operation


3JK Issue 03
@@SECTI
Section 2
System Operation
Module 8
xx Issue 01
1350OMS

xx Issue 01
Blank Page

System Operation Network resources availability
Document History

xx Issue 01
Module Objectives
retrieve the information about the resources available/not available for

creating Paths and Trails


xx Issue 01


xx Issue 01
Page
1 Statistics Tables 7
TableofContents
2 Payload Configuration Summary 11
Switchtonotesview!
SystemOperationNetworkresourcesavailability

xx Issue 01
Switchtonotesview!
SystemOperationNetworkresourcesavailability

xx Issue 01
1 Statistics tables


xx Issue 01
1 Statistics tables
How to get the statistics tables
2. Search OTN SDH CTPs statistics

Search OTN NAPs statistics
OR
Use the shortcuts
1. Select a SDH CTPs NAPs
node statistics statistics


xx Issue 01
1 Statistics tables
NAPs and CTPs statistics tables
ST 6
b3 -4
M
M-
b3
0
ST
1
HO-Trail HO-Trail
TU12,TU3,TU3 TU12,TU3,TU3
2M Path
2M Path

The NAPs are grouped based on the value of certain attributes.

Specifically, the first column (Total#) gives the total number of NAPs having the same value for the
following attributes:
Idle Indicator:
Busy, if the NAP supports an Allocated, Implemented or Commissioned Path.
Not Connected, if the NAP supports a Defined Path.
Idle, if the NAP is not used for any Paths.
NAP Rate: gives the rate of the NAPs (VC12, VC3, …).
The SDH CTPs are grouped based on the value of certain attributes.
Specifically, the first column (Total#) gives the total number of SDH CTPs having the same value for the
following attributes:
Path/trail Indicator: tells whether the CTP (Potential or Real) supports a Path, a Trail or whether it is
Idle (i.e. available).
CTP Rate: gives the rate of the CTPs (Au4, Tu3, Tu12, …).
Port Name: is the name of the SDH Port the CTPs belong to.
Example about Real and Potential resources: when allocating a 2Mb/s Path over an HO Trail payloaded
as (TU3,TU3,TU12), the routing algorithm selects the potential TU12(1,1,1) even if the first TUG3 is
structured as TU3 and not as TU12s. The later Path implementation will modify the payload into
(TU12,TU3,TU12); TU12(1,1,1) becomes real. That’s possible if the Dynamic Payload configuration is
enabled.

xx Issue 01
Blank Page


xx Issue 01
2 Payload Configuration Summary


xx Issue 01
Generalities
For Path/Trail allocation, the resources to be chosen are:

LO/HO Link Connections (TU12, TU3, AU4)
As explained in the module that deals with HO-Trails, 1350OMS-SDH can

automatically manage the payload configuration of the Trail (Dynamic
Payload). In this way, each time a new Path requires a specific
transport rate, 1350OMS-SDH automatically sets the correct payload by
creating or modifying the HO-Trails (and related Link Connections).
Therefore the Routing Algorithm must have knowledge not only of the
configured resources (Au4-4C, Au4, Tu12,...) that are the “Real” ones,
but also of “Potential” resources, such as Link Connections that can be
made available after possible modifications of the current payload
configuration.

A Link Connection (HO or LO) puts in connection a pair of CTPs (HO or LO).
Configuring the payload of an HO-Trail means to structure the AU4 into LO-CTPs (TU3, TU12) and
connecting them by means of LO-Link Connections.
Configuring the payload at Higher Order means to structure the MS-Trail into groups of HO-CTPs
(AU4, AU4-nC) and connecting them by means of HO-Link Connections.

xx Issue 01
Potential Resources
Potential Higher Order resources of an MS-Trail (STM-N) are

combinations of:
Up to N x Au4
Up to N/4 x Au4-4C
Up to N/16 x Au4-16C
Up to N/64 x Au4-64C
Potential Lower Order resources of an HO-Trail are combinations of:

Up to 3 x Tu3
Up to 63 x Tu12
A “Potential” resource is present in the 1350OMS-SDH’s database, but is

not implemented in the NE’s MIB. By implementing a potential
resource, it becomes a “Real” resource.

MIB: Management Information Base

xx Issue 01
Busy, Available and overlapped Resources
A payload resource, no matter if Real or Potential, can be:

Busy, if used by any Path/Trail (e.g. a Tu12 used by a 2Mb/s Path).
Available, if it is not used by any Path/Trail and all of its overlapped
resources are not used by any Path/Trail, too.
Not available, if it is not used by any Path/Trail at the current rate but at
least one of its overlapped resources is used by any Path/Trail.
Two resources are said to be overlapped if one of them contains as

potential the other one, i.e.:
At HO level, an Au4-64C is overlapped with all the Au4-16C, the Au4-4C and
the Au4 potentially contained in it.
At LO level, a Tu3 is overlapped with all the Tu12 potentially contained in it.
In the following, some examples are given in order to better clarify the
concept of Potential, Busy, (not)Available and overlapped resources.


xx Issue 01
Busy, Available and overlapped Resources – Examples 1 and 2
Example 1
Au4
Real HO Supported LO
Posi Path status HO Resources status
Resources Paths Resources
tion
1 Au4 Au4 available N.A.
2 Au4 140M Path Implemented Au4-4C Au4 Busy N.A.
3 Au4 not available Au4 available N.A.
4 Au4 Au4 available N.A.
Example 2
Au4
Real HO Supported LO
Posi Path status HO Resources status
Resources Paths Resources
tion
1 Au4 available N.A.
2 140M Path Allocated Au4-4C Au4 Busy N.A.
Au4-4C
3 not available Au4 available N.A.
4 Au4 available N.A.

Example 1:
The Au4-4C Link Connection is:
potential because it is not the current payload of the MS-Trail.
overlapped to the 4 Au4s.
Not available because a Path is using a resource overlapped to it (the 2nd Au4).
4 Au4s are:
real because it is the current payload of the MS-Trail.
overlapped to the Au4-4C, because they are part of it.
Au4 #1, #3 and #4 are available because no Path is using a resource overlapped to them (the Au4-
4C).
Au4 #2 is busy because it is carrying a Path.
N.B.: The payload must be consistent with the implemented Path.
Example 2:
The Au4-4C Link Connection is real because it is the current payload of the MS-Trail.
The payload must not be necessarily consistent with the carried non-implemented Path, so it is
allowed to allocate a 140M Path over a potential Au4 making part of a real Au4-4C Trail.
The 4 Au4s are:
potential because the current payload is Au4-4C.
overlapped to the Au4-4C, because they are part of it.
3 of them are available because no traffic is using a resource overlapped to them (the Au4-4C).
1 of them is busy because it is carrying an allocated Path.

xx Issue 01
Busy, Available and overlapped Resources – Example 3
Example 3
Au4 HO
HO- Real Supported
Posi Path status Resource LO Resources status
Trail Resources Paths
tion s status
21 x Tu12
Tu3 34M Path Allocated Tu3 Busy
not available
2M Path 1st Tu12 Busy
Tu3 not
Tu3 (position Allocated 2nd to 21st Tu12
1 yes N.A. available
/2/1.1) available
2M Path 1st Tu12 Busy
Tu3 not
Tu12 (position Implemented 2nd to 21st Tu12
available
/3/1.1) available
Au4
2 no Au4
available
Au4
3 no Au4
available
Au4
4 no Au4
available

Example 3:
The Tu3/Tu3/Tu12 Link Connections are real because they are the current payload of the first Au4.
The payload must not be necessarily consistent with the carried non-implemented Path, so it is
allowed to allocate a 2M Path over a potential Tu12 making part of a real Tu3.
The 1
st Tu3 (real) is:
busy because it is carrying a 34M Path.

overlapped with the 21 potential Tu12s making part of it.

These Tu12s are:

potential because not currently payloaded.

Not available because they overlap to a busy Tu3.
The 2
nd Tu3 (real) is:
Not available because one of its potential Tu12s is carrying an allocated 2M Path.

overlapped to the 21 potential Tu12s making part of it.

The 1st potential Tu12 is busy because it is carrying an allocated 2M Path.

The other 20 Tu12s are:


available because they do not overlap to a busy Tu3.
The 3
rd Tu3 is:

Not available because one of its real Tu12s is carrying an implemented 2M Path.

overlapped to the 21 real Tu12s making part of it.

The 1st Tu12 (real) is busy because it is carrying an implemented 2M Path.

The other 20 Tu12s are:

real because currently payloaded.

available because they do not overlap to a busy Tu3.
xx Issue 01
Case study: an HO-Trail
Two 2M Paths The two Tu12s are Potential and Busy
Tu3 with 2x2M Paths

Tu3 is Real and
Not Available
Nineteen Tu12s with no Path
They are Potential and Available
Tu3 with 34M Path
Tu3 is Real and Busy
Twenty-one Tu12s with no Path

They are Potential and Not Available
Tu12 with 2M Path
Tu12 is Real and Busy
Twenty Tu12s with no Path
Tu3 Potential and They are Real and Available
Not Available

xx Issue 01
Case study: a Physical Connection
The AU4-4c that overlaps Au4#1, Au4#2, Au4#3, and Au4#4 is Potential and Not Available
The AU4-4c that overlaps Au4#5, Au4#6, Au4#7, and Au4#8 is Potential and Available
Seven Au4s with no HO-Trail

Au4 with HO-Trail They are Real and
(the one in the Available
previous slide) It
is Real and Busy
Au4-4c empty It is
Real and Available
Au4 with HO-Trail It is Potential and Busy.

Au4-4c with HO-Trail It Its three Tu3s are Potential and Available. Its
is Real and Not Available sity-three Tu12s are Potential and Available.
Seven Au4s with no HO-Trail They are Potential and Available


xx Issue 01
Retrieval
Payload Configuration Summary is available for

HO-Trail
Physical Connection
Payload Configuration summary can be retrieved:

as a list in GUI
as a file to be managed by a web-based interface


xx Issue 01
Retrieval: as a list in GUI
1. Select the Physical Connection/Trail

2. Search Payload Configuration Summary
OR
current available
Use the shortcut current busy
current total
potential available
current on total band
fill up
max on total
fragmentation
current overlapped
potential busy
potential overlapped
potential total

xx Issue 01
Retrieval: as a file
1. Actions OTN Payload Configuration Summary

Create (onwards, View)
2. “Drag and Drop” or

“Send to...” the
Trail/Physical
Connection
3. File name
4. Apply


xx Issue 01
Retrieval: as a file [cont.]
1. Actions OTN
Payload Configuration
Summary View
2. By clicking
“View HTML”
3. See next
slide


xx Issue 01


xx Issue 01
By clicking “View”


xx Issue 01
Blank Page


xx Issue 01
End of Module


xx Issue 01
@@SECTI
Section 2
System Operation
Module 9
zz Issue 1.0
1350OMS

zz Issue 1.0
Blank Page

System Operation Topology modification
Document History

zz Issue 1.0
Module Objectives
Remove/add a Node from/to the network by applying the join/split

procedures
Replace a Node in the network by applying the “move port” procedure
Get the Map more consistent with the deployed network in case of External
Networks
Manage the Planned Ports


zz Issue 1.0


zz Issue 1.0
Page
1 Name of Level 1 7
TableofContents
1.1 Name of Level 2
1.1.1 Name of Level 3
1.1.1.1 Name of Level 4
8
9
10
No Level 11
Text Boxes 13
Symbols (mentioned in Front-Matter Part of Course) 14
Tables 15
Numbered Lists 16
Switchtonotesview!
Unnumbered List
Presentation of Animation Settings on Slide Master
17
18
Animation Sequence Complete 19
Text and Graphic 20
Annotations 21
Oversized Screen Snapshots 22
(1) Detail 1 23
(2) Detail 2 24
Notes Page only (Standard Notes Text Field Extended) 25
Notes Page only (Active X Word Text Field) 26
Main Colors 27
Splash Pictures (Samples) 28
How to Do It 29
Discover 30
Exercise 32
Summary 33
Self-Assessment on the Objectives 34
Abbreviations and Acronyms 35
Glossary 37
References 39
End of Module 40
SystemOperationTopologymodification

zz Issue 1.0
Switchtonotesview!
SystemOperationTopologymodification

zz Issue 1.0
1 Split/join


zz Issue 1.0
1 Split/join
Split/join Physical Connections
MSOH
MSOH
MSOH
MSOH
STM-N STM-N
RSOH
RSOH
RSOH
RSOH
TUn
AU4
AU4
TUn
AU4
AU4
VCn
VC4
VC4
VCn
PPI
PPI
Pm
Pm
SPI
SPI
SPI
SPI
… …
Ei
Ei
X X X X X
NE 1 NE 2 NE 3
HO LCs with the
LO HO HO PC same position PC HO
LC Trail LC LC
LO
Path
Split PC
Join PC
LO HO HO PC
LC Trail LC
LO
Path
MSOH
MSOH
RSOH
RSOH
TUn
TUn
AU4
AU4
VCn
VC4
VC4
VCn
PPI
PPI
Pm
Pm
SPI
SPI
… …
Ei
Ei
X X X X
STM-N
NE 1 NE 3
JOIN
A purpose of “Join Physical Connections” is to remove a Node.
Two Physical Connections terminated on a Node are replaced by one Physical Connection that
excludes that Node.
It’s possible to join two Physical Connections if:
they do not bear HO-Trails/Paths terminated in the Node to exclude.
the HO transits that accomplish HO-Trails in the Node to exclude involve HO CTPs with the same
position on the two Physical Connections.
they belong to the same NPA (in case of NPA).
If the two Physical Connections belong to an NPA (SNCP or 2F MS-SPRing), the NPA is updated
accordingly.
SPLIT
“Split Physical Connection” creates HO pass-through cross-connections in the Node-to-insert for the
supported HO-Trails; each HO transit involves two HO CTPs with the same position (time-slot).
Onwards, the user can split the HO-Trails in the inserted Node in order to terminate the Paths in it.
If the Physical Connection belongs to an NPA (SNCP or 2F MS-SPRing), the NPA is updated accordingly.

zz Issue 1.0
1 Split/join
Join Physical Connections
Node to HO-Trail
exclude HO
transit
HO-Trail
+
LO-Path
<Same time-slot!>
Path
Join PCs
PCs to join
HO-Trail + LO-Path
HO-Trail
Joined PC
Excluded
Node
Path doesn’t change.

A purpose of “Join Physical Connections” is to remove a Node.
Two Physical Connections terminated on a Node are replaced by one Physical Connection that excludes
that Node.
It’s possible to join two Physical Connections if:
they do not bear HO-Trails/Paths terminated in the Node to exclude.
the HO transits that accomplish HO-Trails in the Node to exclude involve HO CTPs with the same
position on the two Physical Connections.
they belong to the same NPA (in case of NPA).
If the two Physical Connections belong to an NPA (SNCP or 2F MS-SPRing), the NPA is updated
accordingly.

zz Issue 1.0
1 Split/join
Join Physical Connections [cont.]
1. Open the Physical 2. Select the two Physical Connections

Connection list Actions Topology Modification
Join Physical Connection
3. Insert the name of the

new Physical Connection
4. Apply

Prior to starting the join operation, it is advisable to set the Node’s “Download Status” to “Disabled”:
select the Node Actions OTN Configure Download Disable.

zz Issue 1.0
1 Split/join
Split a Physical Connection
HO-Trail
HO-Trail + LO-Path
Board#37 Board#34
Path
Node to
Split PC
insert
HO-Trail Inserted HO-Trail

+ Node HO
LO-Path transit
Board#37 Board#34
Board#37 Board#28
<Same time-slot!>
“Split Physical Connection” creates HO pass-through cross-connections in the Node-to-insert for the
supported HO-Trails; each HO transit involves two HO CTPs with the same position (time-slot).
Onwards, the user can split the HO-Trails in the inserted Node in order to terminate Paths in it.
If the Physical Connection belongs to an NPA (SNCP or 2F MS-SPRing), the NPA is updated accordingly.

zz Issue 1.0
1 Split/join
Split a Physical Connection [cont.]
1. Select the Physical Connection Actions Topology Modification

Split Physical Connection
2. Select the Node to insert
3. Next

Prior to starting the split operation, it is advisable to set the Node’s “Download Status” to “Disabled”:

zz Issue 1.0
1 Split/join
Split a Physical Connection [cont.]
4. Select the Node-

to-insert’s ports
One of One of
the two the two
new PCs new PCs
5. Insert the names of

the two new
6. Apply
Board#37 Board#34
Board#37 Board#28


zz Issue 1.0
1 Split/join
Split/join HO-Trails
PDH N O C O S o o S O C O O C O S o o S O C O N PDH
A A r r A A r r A A
Port P C P C T t t T C P C C P C T t t T C P C P Port
MSOH
MSOH
MSOH
MSOH
RSOH
RSOH
RSOH
RSOH
TUn
TUn
AU4
AU4
TUn
TUn
AU4
AU4
VCn
VCn
VC4
VC4
VC4
VC4
PPI
PPI
Pm
Pm
SPI
SPI
SPI
SPI
… … … …
Ei
Ei
X X X X X X X
NE 1 NE 2 NE 3
HO HO HO
LO HO LC PC LO LCs with the same position PC LC Trail LO
LC Trail LC
LO
Split HO-Trail
Path
Join HO-Trail
LO HO HO PC HO PC
LC Trail LC LC
LO
Path
MSOH
MSOH
MSOH
MSOH
RSOH
RSOH
RSOH
RS0H
TUn
AU4
AU4
AU4
TUn
AU4
VC4
VC4
VCn
VCn
PPI
Pm
Pm
PPI
SPI
SPI
SPI
SPI
… …
Ei
Ei
X X X X X
NE 1 NE 2 NE 3
SPLIT
A given HO-Trail crossing at HO layer a Node can be split. This enables the usage of LO resources in
the splitting Node.
A protected HO-Trail can’t be split.

As a consequence of the splitting: the current HO-Trail is deleted and two new HO-Trails are created.
The LO-Paths “crossing” the splitting Node are modified by adding LO pass-through cross-
connections.
JOIN
Two HO-Trails with one end-point in the same Node (“join” Node) can be joined in that Node in order
to reduce the LO resources usage in that Node.
It’s possible to join two HO-Trails if:
They have the same payload structure.
All the LO-Paths that are contained in the two current HO-Trails and are accomplished by a LO pass-
through cross-connection in the “join” Node must be using the same LO time-slot in both the HO-
Trails (in case of 2Mb/s Path, the same TU12).
They must not contain Paths terminated in the “join” Node.
The “join” Node must afford HO cross-connections.
They are not protected.
As a consequence of the joining:
The two current HO-Trails are deleted and the new one is created. That is, the LO-Paths “crossing”
the two current HO-Trails are modified by replacing the LO pass-through cross-connections with an
HO pass-through cross-connection in the “join” Node.
Modifications to cross-connections and payload structure are applied only to the “join/split” Node.

zz Issue 1.0
1 Split/join
Split/join HO-Trails: before the split/after the join
Long HO-Trail
in
HO-CTP HO-CTP /jo HO-CTP HO-CTP
HO-TTP lit e
Sp Nod HO-TTP
HO transit
Long Then “First Label” HO-Trail Then “Second Label” HO-Trail

HO-Trail
LO Link Conn. of
Long HO-Trail
Path over
the HO-Trail

SPLIT
A given HO-Trail crossing at HO layer a Node can be split. This enables the usage of LO resources in
the splitting Node.
A protected HO-Trail can’t be split.

As a consequence of the splitting:
The current HO-Trail is deleted.
Two new HO-Trails are created.
The LO-Paths “crossing” the splitting Node are modified by adding LO pass-through cross-
connections.
Modifications to cross-connections and payload structure are applied only to the splitting Node.
The splitting operation reduces the impact on the existing traffic. The LO-Paths carried by the HO-
Trail are disconnected only for the time necessary to perform the operation.

zz Issue 1.0
1 Split/join
Split/join HO-Trails: after the split/before the join
“Second Label” HO-Trail
Split/join
Node
“First Label” HO-Trail HO-CTP HO-CTP
HO-TTP
HO-CTP HO-CTP
HO-TTP
Further HO-TTPs
Split/join Path
LO Link Conn. of LO Link Conn. of
“First Label” trail
Node “Second Label” trail
LO transit
<Same time-slot!>
JOIN
Two HO-Trails with one end-point in the same Node (“join” Node) can be joined in that Node in order
to reduce the LO resources usage in that Node.
It’s possible to join two HO-Trails if:

They have the same payload structure.
All the LO-Paths that are contained in the two current HO-Trails and are accomplished by a LO pass-
through cross-connection in the “join” Node must be using the same LO time-slot in both the HO-
Trails (in case of 2Mb/s path, the same TU12).
They must not contain Paths terminated in the “join” Node.
The “join” Node must afford HO cross-connections.
They are not protected.
As a consequence of the joining:

The two current HO-Trails are deleted and the new one is created. That is, the LO-Paths “crossing”
the two current HO-Trails are modified by replacing the LO pass-through cross-connections with an
HO pass-through cross-connection in the “join” Node.
Modifications to cross-connections and payload structure are applied only to the “join” Node.

zz Issue 1.0
1 Split/join
Split an HO-Trail
1. Select the HO-

Trail Actions
Modification
Split Trail

the two new trails
3. Next
4. Select the
“split” Node
5. Apply

1350OMS-SDH checks in which Nodes traversed by the HO-Trail it can be split (i.e. Nodes where LO
capability is available, Nodes not belonging to protected parts of the HO-Trail,...) and prompts to the
user the list of these Nodes.

zz Issue 1.0
1 Split/join
Join HO-Trails
1. Select the two

current HO-Trails
Actions
Modification
Join Trails
2. Set the name for

the new trail
4. Choose 3. Next
the Node
5. Apply


zz Issue 1.0
1 Split/join
Split/join Paths
PPI PPI
VCn VCn
TUn X
TUn X
MSOH
MSOH
MSOH
MSOH
RSOH
RSOH
RSOH
RSOH
TUn
TUn
AU4
AU4
AU4
AU4
VCn
VCn
VC4
VC4
VC4
VC4
PPI
PPI
Pm
Pm
SPI
SPI
SPI
SPI
… … … …
Ei
Ei
X X X X X X
NE 1 NE 2 NE 3
LO LO
HO
LO HO LC PC Path Path
LC Trail
Split LO Path
Join LO Path
LO
Path
MSOH
MSOH
MSOH
MSOH
RSOH
RSOH
RSOH
RSOH
TUn
AU4
AU4
TUn
TUn
AU4
AU4
TUn
VCn
VCn
VC4
VC4
VC4
VC4
PPI
PPI
Pm
Pm
SPI
SPI
SPI
SPI
… … … …
Ei
Ei
X X X X X X X
NE 1 NE 2 NE 3
SPLIT
A Path may be accomplished by a LO pass-through in a given Node (“split” Node). The user can split
the Path into two Paths by replacing the LO pass-through with two drop/insert cross-connections in
the “split” Node. In the “split” Node two ports/NAPs are required: one port/NAP for a Path, another
port/NAP for the other Path.
JOIN
Two Paths terminated in a given Node can be joined: the two LO drop/insert cross-connections are
replaced by a LO pass-through. Hence the two ports/NAPs in the “join” Node are released and got
available for other Paths.

zz Issue 1.0
1 Split/join
Split/join Paths: before/after – join/split
Then “First Label” Path Then “Second Label” Path Before split
/ after join
Split/join Node
NAP and
LO-CTP LO-CTP LO transit LO-CTP LO-CTP Port
NAP and
Port
Long Path
Split/join NAP and

Node Port
“First Label” Path LO-CTP LO-CTP
drop/insert
LO-CTP LO-CTP
“Second Label” Path

Further NAPs
NAP and drop/insert and Ports After split /
Port before join

zz Issue 1.0
1 Split/join
Split a Path
1. Select the Path

Actions
Modification
Split Path

the two new Paths
3. Next
4. Select the
“split”
Node
5. Apply
1350OMS-SDH checks in which Nodes traversed by the Path it can be split (i.e. Nodes where LO
capability is available, Nodes not belonging to protected parts of the Path,...) and prompts to the user
the list of these Nodes.

zz Issue 1.0
1 Split/join
Join Paths
1. Select the two

Paths Actions
Modification
Join Paths
2. Insert the name of

the new Path
4. Select the
“split” 3. Next
Node
5. Apply

zz Issue 1.0
Exercise: Join/Split HO-Trails
Join
1. Get two HO-Trails created with constraints and ending in a common Node.
2. Join these HO-Trails.
3. Get information to verify the result.
4. Question: what do you notice about constraints applied on the resulting HO-
Trail?
Split
1. Split the HO-Trail mentioned above in order to get the previous
configuration.
3. Rename the HO-Trails in order to get their previous user label.


zz Issue 1.0
Exercise: Join/Split LO-Paths
Split
1. Get a LO-Path crossing at least two HO-Trails.
2. Split this LO-Path.
4. Rename the resulting Paths.
5. Identify the involved NAPs.
Join
1. Get the Paths resulting from the “Split”.
2. Join these Paths in order to get the previous configuration.


zz Issue 1.0
2 Routing Domains


zz Issue 1.0
2 Routing Domains
Routing Domain definition
Client Ports SDH Ports Routing Domain = Ports that are

or can be cross-connected
Routing Domain #1
Routing Domain #2
Node
Allowed cross-connection
Not allowed cross-connection
A Routing Domain groups the Ports of the Node whose client TPs are on can be cross-connected. Once
the Routing Domain has been enabled, it is taken into account by the Path/Trail routing algorithm to
set up new cross-connections.
In the example, some allowed and not allowed cross-connections inside a Node are shown, based on
the assignment of the Ports to different Routing Domains.
A Routing Domain is an object pertaining to a specific Node. So, the same Routing Domain cannot
own ports of different Nodes.

zz Issue 1.0
2 Routing Domains
Routing Domain purposes
Used alone
to force Paths/Trails to use the Ports belonging to the same domain, Node by
Node
Used as support for

Move Ports
the Routing Domain’s Ports of one Node can be migrated to another Node
the supported Paths/Trails are moved, too
it’s useful to
replace a Node
split an External Network (EN)
External Network (EN) partitioning

to rearrange the route of Paths/Trails according to new routing domains
it’s a preliminary step for splitting an EN, too


zz Issue 1.0
2 Routing Domains
Routing Domain state diagram
Set/Modify routing domain only for the
ports without routing domain
The Routing Enabled for

Domain of the r Migration
le fo
ports is Enab tion
a
disregarded by Migr
the routing le
Disab
algorithm
Enable for
Disabled Enable for
Partitioning
Migration
Disab
le
•Routing Domain
check/calculation
•Set/Modify/Delete Enabled for
routing domain on ports Enable for Partitioning Only
Partitioning for EN
•Routing Domain check/calculation

•Set/Modify/Delete routing domain on ports
Routing Domain “Disabled”

In this state the routing domains defined for the ports of Node are not taken into account by the
routing algorithm for the Path/Trail set up. In this state the user can:
Set/Modify/Delete the value of the Routing Domain attribute for all or a set of the ports of the
Node.
Request for the automatic assignment of the routing domain by 1350OMS. The same routing domain
label is assigned to the ports:
involved in the same cross-connection.
involved in the same protection scheme (Linear MSP, SNCP or 2F MS-SPRing).
at the end of the same WDM-SDH interworking Physical Connection.
Routing Domain “Enabled for Migration”

In this state the Routing Domain is taken into account by the routing algorithm for the new
Path/Trail set up. Cross-connections can be set-up only among the ports that belong to same
Routing Domain.
This state can be got only if the ports involved in the same cross-connection, involved in the same
protection scheme (Linear MSP, SNCP or 2F MS-SPRing) and at the end of the same WDM-SDH
interworking Physical Connection have the same Routing Domain and the Routing Domain is
different from the default one (null value).
In this state 1350OMS is able to migrate sets of ports (and all the supported TPs, cross-connections,
POM, Protection Blocks, Link Connections, Paths, Trails) from a Node to another one.
In this state the user can change the Routing Domain only for the ports that have the default
Routing Domain (null value).
Routing Domain “Enabled for Partitioning”: see next slide

zz Issue 1.0
2 Routing Domains
Commands to use
Select the Node Actions OTN Modification ...

Routing Domain “Enabled for Partitioning”: from previous slide

This state is applicable only to External Network (EN). In this state the Routing Domain is used for
partitioning the EN for routing purposes and is taken into account by the routing algorithm for the
new Path/Trail set up. The user can:
Set/Modify/Delete the value of the Routing Domain attribute for all or a set of the ports of the
Node.
carry out a procedure, as an off-line tool, that checks and notifies the Paths/Trails not routed
according to the Routing Domains and then a procedure that re-arranges those Paths/Trails.

zz Issue 1.0
2 Routing Domains
Routing Domain information
Node list Port list
Hereafter, the following procedures for modifying the topology are

explained:
Move Ports from a Real NE to another Real NE
Split of External Network
This procedure includes the EN partitioning


zz Issue 1.0
3 Move Ports between real NEs


zz Issue 1.0
Example
From... ...to...
Board#25 Board#25 Board#4

Port#1 Port#1 Port#6
Source
Node
Board#34 Board#34 Board#18

Destination
Port#1 Node Port#1 Port#15

Node 165B must be replaced with Node 170B, hence the two STM-N Ports connecting 165B to the
other Nodes of the network must be moved to 170B.
Moving Ports means moving also all the cross-connections involving the HO/LO TPs belonging to those
Ports. Consequently, also all the Paths/Trails (i.e. traffic) are moved along with the Ports through
which they are routed.

zz Issue 1.0
Procedure
1. The destination Node must be available in 1350OMS

Create NE, upload Ports (Synchronize NE)
2. Set “Download Status”=Disabled on the source and destination Nodes
3. Manually assign the Routing Domain on the source Node

Assign to the Routing Domain the Ports to be moved. The Routing Domain
must encompass all the Ports among which there are cross-connections.
4. Move the Ports from the source Node to the destination Node
Set “Routing Domain Status”=“Enable for Migration” on the source Node
Move the Ports using the “NE Migration wizard”
5. Set “Download Status”=Enabled on the source and destination Nodes

The involved Nodes can be either in Download Status=Enabled or Disabled. In both cases the
procedure is traffic impacting. But, operating in Download Status=Disabled, the impact is lower. The
user can prepare the 1350OMS database and move the cables only when he decides to change the
status from Disabled to Enabled. In this way, the traffic impact is limited to the time required by the
Consistency Download procedure to complete.
This feature is suitable only for the SDH Ports.

zz Issue 1.0
Step 2-3: Download Status=Disabled and Routing Domains
1. Set Download Status=Disabled on the two Nodes
2. Select the source Node
Actions OTN Modification
Routing Domain Assign
3. On Selected
Port
4. Choose the
Ports to move
Only the ports to
be moved must be
5. Edit a name for the assigned to
Routing Domain Routing Domains.
Only SDH Ports can
be moved.
6. Apply
Select where set(modify) the Routing Domain Name

All Ports: all of the Node’s Ports are assigned the Routing Domain whose name has to be specified in
“Or new Routing Domain Name” box. By leaving it empty, all the Node’s Routing Domains are
deleted.
Automatic: 1350OMS-SDH creates a Routing Domain for each group of suitable Ports.
Only SDH Ports and not Client Ports can be moved between real NEs. Hence, the procedure forbids to
move SDH Ports supporting Paths that are terminated in the source Node.

zz Issue 1.0
Step 4: “Enabled for migration” and “Move ports”
“Enabled For Migration”
Select the source Node Actions OTN Modification

Routing Domain Enabled For Migration
it fails if the Routing Domain configuration is not correct. Examples:

consider a group of Ports among which there are cross-connections. Some of those
Ports have been assigned to a Routing Domain, whereas others to another Routing
Domain.
the Ports to move belong to different NPAs (linear MSP, SNCP, 2f MS-SPRing).
Move ports
1. Select the source Node Actions OTN Modification
Move Ports


zz Issue 1.0
Step 4: Move ports
2. Use “Send To” to place

here the destination Node
3.
Nex
t


zz Issue 1.0
Step 4: Move ports [cont.]
4. Select a source Port select the

destination Port click “Create
ports correlation”
Do it for each Port to move, that is
every Port of the Routing Domain
5. Apply

Just the destination Node’s Ports that match the type of the source Node’s Ports are prompted.
Client Ports (C12, C3, etc)
cannot be assigned to any real destination Port
cannot be moved
must not belong to the Routing Domain
A Port can be moved only if associated with a destination Port. All the Routing Domain’s Ports must
have a correlation with a destination Port.

zz Issue 1.0
Procedure outcome
Example: HO-Trail between 63B and 164B
Before
Board#25 Board#4
Port#1 Port#6
Board#34 Board#18
Port#1 Port#15
After


zz Issue 1.0
Step 5: Download Status=Enabled
Download Status=Enabled
If the outcome of the procedure is successful:
Set Download Status=Enabled on the two Nodes
and
move the cables
The Consistency Download is triggered:
1350OMS downloads the new configuration to the two Nodes
the cross-connections in the source Node are deleted
the cross-connections in the destination Node are created
it’s traffic impacting, hence it’s convenient to move the cables
To restore the default Node status:

Select the source Node Actions OTN
Modification Routing Domain Disable


zz Issue 1.0
Blank Page


zz Issue 1.0
4 Split of External Network


zz Issue 1.0
Rationale
Deployed network
Eq4 Eq1
Eq5
Eq1, Eq2, Eq3, Eq4: managed by 1350OMS
Eq5, Eq6: not managed by 1350OMS

Eq6
Eq3 Eq2
Current map “To be” map

in 1350OMS in 1350OMS
Node4 Node1 Node4 Node1
EN-A EN-A
Split EN
EN-B
Node3 Node2 Node3 Node2
EN-A stands for EN-A stands for Eq5
Eq5 and Eq6 EN-B stands for Eq6
An EN normally represents more than one piece of equipment, sometimes even a whole network.
EN splitting is useful to get the Map be compliant with the deployed network.

zz Issue 1.0
Path/Trail concerns: Partitioning
Deployed network
An EN may represent more than one Eq4 Eq1

Eq5
piece of equipment.
The cross-connections in EN should
involve ports that correspond to the Eq6
same equipment.
Eq3 Eq2
Node4 Node1 Node4 Node1 Node4 Node1

EN-A Partition EN-A Split EN-A
EN EN
EN-B
Node3 Node2 Node3 Node2 Node3 Node2

EN partitioning and splitting make use of Routing Domains. Their purpose is to partition the whole set of
ports available in the EN into disjoint sets of ports, each one representing one piece of equipment.

zz Issue 1.0
Procedure
1. Routing Domain assignment on EN-A

a. create two domains: one for each piece of equipment
2. Partitioning of EN-A
a. Set Routing Domain status = “Enabled for Partitioning”
b. Find and fix the already allocated/implemented/commissioned Paths/Trails
which have a wrong route by means of off-line commands
3. Split: move the Ports of one of the two domains from EN-A to EN-B
a. Set Routing Domain status = “Enabled for Migration” on EN-A
b. Move the ports using the “NE Migration wizard”
4 EN-A 1 Partition 4 EN-A 1 Split 4 EN-A 1

EN EN
3 2 3 2 3 EN-B 2
step 1 step 2 step 3


zz Issue 1.0
Current Map/Path


zz Issue 1.0
Step 1: Routing Domains – automatic assignment
1. Select EN1 Actions OTN

Modification Routing Domain
Assign
2. Automatic
3. Apply
Port list
Outcome of
automatic
assignment

By doing the automatic assignment, the Routing Domain creation is based on the current cross-
connections in EN1: the Port “looking to” Node 62B and the Port “looking to” Node 164B have been
given the same domain, whereas the other two Ports another domain.

zz Issue 1.0
Step 1: Routing Domains – manual assignment
Deployed network
Eq4 Eq1
Eq5
Eq6
Eq3 Eq2
Create a domain for the

Ports corresponding to Eq5

To get a map compliant with the deployed network, the Routing Domains must encompass the Ports
of one piece of equipment. So, the user has to carry out the manual assignment.
N.B.: even if the Routing Domain concerns a single Node, the same Routing Domain name cannot be
used at the same time for different Nodes.

zz Issue 1.0
Step 1: Routing Domains – manual assignment [cont.]
Deployed network
Eq4 Eq1
Eq5
Eq6
Eq3 Eq2
Create a domain for the

Ports corresponding to Eq6


zz Issue 1.0
Step 1: Routing Domains – manual assignment [cont.]
automatic assignment
The Routing Domains

are compliant with the
deployed network, but
the cross-connections
in EN1 are still the
original ones.
Partitioning is
required.
manual assignment

zz Issue 1.0
Step 2: Partitioning
a. Set Routing Domain status = “Enabled for Partitioning”
Select EN1 Actions OTN Modification

Routing Domain Enabled For Partitioning
b. Find and fix the already allocated/implemented/commissioned

Paths/Trails which have a wrong route by means of off-line commands
The off-line commands are Unix commands. The user must have
administrator rights.
Commands:
1. findWrongPath
2. fixWrongPath


zz Issue 1.0
Step 2b: Partitioning – find wrong Path
Output file name (user defined). The file is
containing the list of the badly routed paths/trails
findWrongPath EN1 id
EN1
properties
Execution Notification


zz Issue 1.0
Step 2b: Partitioning – fix wrong Path
The file created by “findWrongPath”
fixWrongPath
Execution Notification
“Fix” has been
executed on this
Path that was
found wrong

If the fixing procedure suggests any corrective actions, execute them on the relevant Path/Trails (i.e.
Remove Spare followed by Add Spare, or others).
If the fixing procedure doesn’t suggest any corrective actions, it is advisable to run again the “Find
wrong Paths” command for checking purpose.

zz Issue 1.0
Step 2: Partitioning – outcome


zz Issue 1.0
Step 3: split EN1
1. Set EN1 “Enabled for migration”
2. Move the ports of Routing Domain “Below” from EN1 to EN2
move ports
164B EN1 63B 62B EN2 165B

The “Move port” procedure is dealt in the previous chapter.

The Path is rearranged accordingly.

zz Issue 1.0
Partitioning restriction
N.B.: The “FixWrongPath” procedure can cross-connect only the TPs already used by the
Path/Trail to be rerouted. The cross-connections inside the Node are rearranged
according to the configured routing domains but they can be set-up only between TPs
already used by the Path/Trail to be fixed: see the following two examples.
Path
endpoint A
2 1
Current
Example 1: suitable Path
In the “Current” and in the “To
be” topologies, the involved TPs 3 4
are the same: 1, 2, 3, 4. Path
endpoint Z
The procedure has to modify just
the cross-connections: cross-
connections 1-3 and 2-4 are Path
replaced by the cross- 2 1 endpoint
To be
connections 1-2 and 3-4 A
3 4
Path
endpoint Z


zz Issue 1.0
Partitioning restriction [cont.]
Example 2: not suitable Path

“Fix wrong Path” fails because Path
the “To be” topology shall 1 endpoint A
involve the TP 3 that is not used
Current
in the “Current” topology.
2 3
Path
endpoint Z
Path
endpoint A
To be 1
2 3
Path
endpoint Z


zz Issue 1.0
Exercise: split External Network
Using the NEs provided for the training:

1. Set up a topology made of Real NEs and at least one EN. Plan to modify the
topology splitting in two the ENs.
2. Set up Trails or Paths misrouted as regard to the final topology.
3. Configure Routing Domains, then find and fix the wrongly routed
Paths/Trails
Check the route of the fixed Paths/Trails
4. Split the EN.


zz Issue 1.0
Blank Page


zz Issue 1.0
5 Port conversion and Planned Ports


zz Issue 1.0
Overview
STM-N Planned Ports can be configured on a Node when the relevant

hardware, that is the board and/or port (Real Port), has not yet been
plugged in.
Planned Ports can be configured at one or both the extremities of the

Physical Connection. That Physical Connection can be used for
provisioning.
Once the hardware has been plugged in and the NE has been properly
configured (board/port declaration in Equipment View), the Planned
Ports can be converted into Real Ports.


zz Issue 1.0
Operation with Planned Ports
Convert Port (on the same Node)

Planned Port Real Port
Real Port Planned Port
Real Port Real Port (too)
Move Port (from Node A to Node B)

Planned Port Real Port
Real Port Planned Port


zz Issue 1.0
Conversion Planned Real: procedure
Initial configuration
1. Create a Physical Connection (PC) with a Planned Port.
2. That PC can be used for provisioning: create Paths/Trails.
Conversion
3. Plug in the hardware in the equipment.
4. Declare the hardware in Equipment View.
5. Check whether the Node has recognized the new hardware (Real Port). If
not, do “Synchronize NE”.
6. Set the Download Status of the Node with the Planned Port to “Disabled”.
7. Do convert by means of the “Conversion Real/Planned Ports” wizard.
8. If everything is successful, set the Download Status of the Node to
“Enabled”.
Onwards, Step 1 and Step 7 are addressed

The conversion can be applied with the Node either in Download Enabled mode or in Download Disabled
mode. In both cases the conversion is traffic impacting. But, operating in Download Disabled mode, the
user can prepare the 1350OMS database and move the cables only when he decides to change the status
from Download Disabled to Download Enabled. In this way, the traffic impact is limited to the period of
time required by Consistency Download procedure to complete.

zz Issue 1.0
Step 1: create a Physical Connection with a Planned Port
1. For Real
Port: From 2. For Planned Port:
List Create Planned
Port
The Planned Port’s “Resource State” is
“Planned”
(for a real Port, it’s “Installed”)
The Planned Port’s user label will be
164B/Planned_to_63
Real Planned “Node’s User Label” / “Z Port Name”
Port Port

zz Issue 1.0
Step 7: “Conversion Planned/Real Ports” wizard
4. Select the Real Port

3. From List (destination is Real)
2. Select the Planned Port
5. Create ports 1. Select the Node with the
correlation planned port Actions OTN
Modification Move
6. Apply Convert planned/real port

zz Issue 1.0
Exercise: convert Planned Ports into Real Ports
Using the NEs provided for the training:

1. Set up a Physical Connection using at least a Planned Port as end-point
2. Convert the Planned Ports into real ones using the proper procedure


zz Issue 1.0
End of Module


zz Issue 1.0
@@SECTI
Section 2
System Operation
Module 10
Batch files
xx Issue 01
1350OMS

xx Issue 01
Blank Page

System Operation Batch files
Document History

xx Issue 01
Module Objectives
operate the Batch Files that may be used to modify the 1350OMS-SDH
objects.


xx Issue 01


xx Issue 01
Page
1 Introduction 7
TableofContents
2 Procedure: Example for modifying the Path end points
3 Example: Increase bandwidth with new board in the same slot
13
23
Switchtonotesview!
SystemOperationBatchfiles

xx Issue 01
Switchtonotesview!
SystemOperationBatchfiles

xx Issue 01
1 Introduction


xx Issue 01
1 Introduction
Rationale for Batch Files
The user can create Batch Files for Path, Trail, Node, NPA, Shared Risk
Group, eml Domain, Physical Connection.
Batch File stores the configuration parameters of the addressed

objects.
By executing a Batch File, the addressed objects are created.
Thus, Batch Files are useful when an object has to be deleted and then
recreated as it was or modified.
Prior to executing a Batch File, the user can modify its content in order to
get a modified object (i.e. the recreated Path is to use a TU12 different from
the one used by the original Path).
Batch file must be created before deleting the objects.

Shared Risk Group: it concerns ASON.

xx Issue 01
1 Introduction
Rationale for Batch Files [cont.]
So, Batch Files are also a means to modify the parameters of an object.
In some cases, the same object modification may be accomplished by a

command/wizard available in 1350OMS-SDH.
The user may find easier the Batch File implementation than the
command/wizard one.
Examples:
in order to modify a part or the complete routing of a Path:
1350OMS-SDH provides the “Reroute” command
Batch File allows to edit the new STM-N Ports/TU12s
in order to modify the NAPs of a Path:
1350OMS-SDH provides the “Modify End Points” wizard
Batch File allows to edit the new NAPs


xx Issue 01
1 Introduction
Batch File example for a 2Mb/s Path
NAPs


xx Issue 01
1 Introduction
Batch File example for a 2Mb/s Path [cont.]
Path_68-160
68B 69B 160B
01/1/1.1 01/1/2.3
b36p01 b30p01
b20p01 b34p01 b28p01 b21p19
b03p04 b03p01
01/2/2.2 01/3/3.3
b08p01 b09p02
57B

xx Issue 01
Blank Page


xx Issue 01
2 Procedure: Example for modifying the
Path end points


xx Issue 01
Steps
1. Create the Batch File for the Path to modify.
2. Modify the Batch File.
3. Set the “Download Status” of the Nodes traversed by the Path to “Disabled”.
The 1350OMS-SDH operation will not affect the NEs.
4. Remove the Path.
5. Execute the Batch File.

Since the Nodes have “Download Status” = “Disabled”, the Path with the new settings
is created in the 1350OMS-SDH database but not in the NEs.
6. Inspect the new Path.
7. Set back the “Download Status” of the Nodes to “Enabled”.

The new Path is implemented in the NEs.


xx Issue 01
Modification to apply
Original
Path
Port#2 Port#1
Port#3 Port#2
Modified
Path


xx Issue 01
Step 1: create the Batch file
1. Preliminary step:
Actions OTN Command Line
Interface Dump Preparation
2. Put here the Path:

use “Send To”
3. Insert a name for

the Dump file
4. Apply


xx Issue 01
Step 1: create the Batch file [cont.]
1. Actions OTN
Command Line Interface
Batch Commands
Back
Type and User Label of

the addressed object
2. Create
batch
The Dump file just created file

xx Issue 01
Step 1: create the Batch file [cont.]
Batch File
creation log
The Batch File

just created
1. Back
2. To modify the Batch

File do “Edit”.
See next slide.


xx Issue 01
Step 2: modify the Batch file
Modified
Path
1. Edit the
new Original
NAPs Path
[*]
2. (Optional) By removing these 3 lines, the

constraints taken into account by the Batch File
(see [*]) will be reported in the Constraint Wizard.
3. Save

About the three lines:

CONSTRpath
userLabel "Path_68-69"
END
If you execute the Batch File containing the three lines, that is without deleting them, the
constraints wizard for the addressed Path/Trail will be empty. If you remove these lines prior to
executing the Batch File, you’ll see the constraints from the file [*] in the constraints wizard. The
constraints given by user are removed/overwritten anyway.

xx Issue 01
Steps 3-4-5: Download – Remove Path – Run Batch file
3. Set the “Download Status” of the Nodes traversed by the Path to

“Disabled”: select the Node Actions Configure Download
Disable. So, the 1350OMS-SDH operations will not affect the NEs.
4. Remove the Path.
5. Execute the Batch File by doing “Run”. Since the Nodes have
“Download Status” = “Disabled”, the Path with the new settings is
created in the 1350OMS-SDH database but not in the NEs.


xx Issue 01
Steps 6-7: Inspection - Download
Warning: not aligned

6. Inspect the new Path objects because the Node
is in Download disabled
New NAPs
7. Set back the “Download Status” of the Nodes to “Enabled”. The new
Path is implemented in the NEs.


xx Issue 01
Blank Page


xx Issue 01
3 Example: Increase bandwidth with
new board in the same slot


xx Issue 01
Introduction
A B
before: sl28 sl34
STM-4
STM-4
STM-4
A B
sl28 sl34
after:
STM-16
STM-16
STM-16

xx Issue 01
Preconditions
The board to replace must be empty:
the board is not involved in

MSP protection
LAPD protocol
Synchronization
EPS protection
on the board there are no

PM-TPs
Overhead Cross Connections
Loopbacks


xx Issue 01
Procedure
All Paths/HO-Trails passing the Physical Connection to change have to

be removed later, therefore save the configuration of the Paths/HO-
Trails:
1. Create the Batch files for all Paths/HO-Trails passing the Physical
Connection to change
To minimize traffic impacts the following preparation in 1350OMS-EML

and 1350OMS-SDH is done without communication to the affected NEs.
For NE A and NE B the simulator is used:
2. Perform a MIB backup of NE A and NE B
3. Disable Download for all the Nodes used by Paths/HO-Trails passing the
Physical Connection to change except for Node A and Node B
4. Stop Supervision of NE A and NE B
5. Increase the number of possible simulators in the system from “1” to “2”
6. Start the simulator for NE A and NE B


xx Issue 01
Procedure [cont.]
Remove the Physical Connection between the boards to replace from

1350OMS-SDH:
7. Remove all Paths/HO-Trails passing the Physical Connection to change
8. Deimplement and remove the Physical Connection
Create a new Physical Connection between the new boards in

1350OMS-SDH:
9. Configure the new boards ( only in the simulator)
10. Create the new Physical Connection
Create again the HO-Trails and Paths removed before; they now use
the new Physical Connection:
11. Execute the Batch files for all HO-Trails
12. Execute the Batch files for all Paths


xx Issue 01
Procedure [cont.]
Check the correct execution of the preparation:

13. Perform a mark audit for all Nodes except Node A and Node B and check
the result
14. Enable Download for all Nodes
Replace the boards:

15. Disable Download for Node A and Node B
16. Stop the simulator for NE A and NE B
17. Replace the board physically
from now on the traffic is interrupted
18. Start supervision for NE A and NE B
19. Simulator align down and activation of MIBs in NE A and NE B
from now on the traffic is back


xx Issue 01
Procedure [cont.]
Check the correct execution of the operation:

20. Perform a mark audit for Node A and Node B and check the result
( Download is still disabled from step 15)
21. Enable Download for Node A and Node B
Set back the system configuration:

22. Decrease the number of possible simulators in the system from “2” to
“1”


xx Issue 01
Step 1: create Batch files
a. First, create a Dump for all of the HO-Trails and a Dump for all of the
Paths. Use the window that opens by means of:
Actions OTN Command Line Interface Dump Preparation
b. Then, create the two relevant Batch files. Use the window that opens
by means of:
Actions OTN Command Line Interface Batch Commands
c. Finally, edit and save the HO-Trails Batch file. Seven lines must be
deleted:
includeAnyColorId 1
excludeAnyColorId 2
creationRule notMeaningful
pm24QoS false
published false
includeAnyColorName "NoColor"
excludeAnyColorName "AllColors"


xx Issue 01
Step 2: MIB backup for NE A and NE B
operation 1350OMS-SDH
DB
NO
is download
enabled for
A and B?
YES
1350OMS-EML
are A Simulator
and B NO is Sim YES
supervised? started?
A B
NO
YES
NE A NE B
To align the simulator MIB to the NE MIB:

the NE must be Supervised
issue Align Up in the Equipment View
Default settings:
Download enabled for all the Nodes
All the NEs are supervised
The simulators are stopped
1350OMS-EML
Simulator
simulator
MIB
Simulator
Align up Simulator
Align down
Q3
NE active Not active
MIB MIB
activate

xx Issue 01
Steps 3-4-5: Disable download - Stop supervision - Simulators
3. Disable download for all Nodes involved in Paths/HO-Trails passing the

Physical Connection to change except for Node A and Node B:
select the Node Actions Configure Download Disable
4. Stop Supervision of NE A and B:

select the NE Actions Supervision Stop Supervision
5. Increase the number of simulators (ask the system administrator):

folder: /usr/Systems/EML_1/simulator/simcon/data
file: param.cfg
parameter to modify: MAX_NUMBER_OF_INSTANCIABLE_SIMULATORS
After this action it is necessary to restart the 1350OMS process “simcon”


xx Issue 01
Step 6: start simulator for NE A and NE B
DB
NO
is download
enabled for
A and B?
YES 1350OMS-EML
are A
4 6
NO is Sim YES
Simulator
and B
supervised? started? A B
NO
YES
From now on the 1350OMS-SDH

operation for NE A and NE B is
performed in the simulator MIB and
not in the NE MIB NE A NE B

To start the simulator:

the NE must not be supervised. The supervision has been stopped at Step 4.
issue Start in the Equipment View that is empty.
NE A and NE B are not supervised and their simulator is started. Hence, the configurations carried out
by means of 1350OMS-SDH concern the simulator MIB and not the NE MIB. Thus, the traffic is not
affected.

xx Issue 01
Steps 7 through 12: transports deletion and recreation
7. Remove all Path/HO-Tails passing the Physical Connection to change

Remember: All nodes are in Download Disabled Mode - nothing happens with
traffic!
8. Deimplement and remove the Physical Connection
9. Configure the new boards in the simulator of NE A and NE B
10. Create the new Physical Connection

the slots are the same as before. Instead the Port Type is different.
11. Execute the Batch files for all HO-Trails
12. Execute the Batch files for all Paths
Nodes are still in Download Disabled mode; after executing the Batch files we
have the same situation in 1350OMS-SDH DB as in the NE themselves.


xx Issue 01
Step 13: Mark Audit
The result of the audit should be “No Difference”


xx Issue 01
Steps 14-15-16-17: download – simulator - board
14. Enable the Download for the Nodes
for which it was disabled in Step 3. DB
The 1350OMS-SDH operation affects all
the NEs of the network except NE A NO 15
and NE B that are not supervised. All is download
enabled for
Paths are still running; for the traffic A and B?
nothing has changed up to now, no
error should have occurred.
YES 1350OMS-EML
4
15. Disable Download for Node A and are A
NO Simulator
and B is Sim YES
Node B. started?
supervised? A B
16 NO
16. Stop the simulator for NE A and B. YES
The Nodes now appear isolated.
17. Replace the boards physically:

From now on we have traffic interruption!
NE A NE B


xx Issue 01
Steps 18-19: supervision - simulator
18.Start Supervision for NE A and
NE B. DB
NO 15
19.Perform a simulator align down is download
enabled for
and activation. A and B?
YES 1350OMS-EML
are A Simulator
and B NO is Sim YES
16 NO
YES
18 19
19
NE A NE B


xx Issue 01
Steps 20-21-22: audit - download
20.Perform a Consistency Audit: Mark
Audit for Node A and Node B and DB
check the results.
This is for safety reasons to verify NO
is download
that NE MIB and 1350OMS-SDH DB enabled for
A and B?
are aligned.
YES 21
1350OMS-EML
21.Enable the Download for Node A
are A Simulator
and Node B. and B NO is Sim YES
22.Decrease the number of NO
YES
simulators.
NE A NE B


xx Issue 01
End of Module
Batch files


xx Issue 01
@@SECTI
Section 3
Maintenance Applications
Module 1
aa Issue 1.0
1350OMS

aa Issue 1.0
Blank Page

Maintenance Applications Troubleshooting tools
Document History

aa Issue 1.0
Module Objectives
Locate a faulty network section by means of loopbacks

Forward a traffic to test ports connected to an external instrument for
monitoring purposes


aa Issue 1.0


aa Issue 1.0
Page
1 PM from 1350OMS-SDH point of view 7

TableofContents
2
3
4
PM
PM
PM
basic operation
result
advanced operation
13
23
29
Switchtonotesview!
MaintenanceApplicationsTroubleshootingtools

aa Issue 1.0
Switchtonotesview!
MaintenanceApplicationsTroubleshootingtools

aa Issue 1.0
1 Loopback Management


aa Issue 1.0
Activation from NAP or from Port
Path Routing
Display
Loopback indication
NAP
Port
1. Select a NAP or
a Port
Actions
Manage
loopback …
Path
properties
Port
properties
The Path must not be “Commissioned”.

According to the equipment and the point types, some loopback types are available, whereas others
not.
“No Loop”: to remove the active loopback.

aa Issue 1.0
Loopback on CTP
Path Routing
Display
Loopback indications
Path properties
The CIT between NAP

and CTP is replaced
by the loopback
1. Select a CTP Actions

Matrix Loopback …

CTP must be involved in a bidirectional point-to-point connection.

In case of HO-Trail, the HO CTP connected to the CAP doesn’t support loopback.

aa Issue 1.0
Exercise
On a Path:
Activate a loopback on a NAP
Deactivate it
Activate a loopback on a CTP
Deactivate it


aa Issue 1.0
2 Test Port


aa Issue 1.0
2 Test Port
Rationale
Monitor cross-connections
Node
Phys. Phys.
Conn. STM-N STM-N Conn.
A B
SDH SDH
Path#1
Network Path#2 Network
Path#3
Tes Tes
t STM-N 2M t
Port C D Port
Phys. Cable
Conn.
Test
Instrument

For monitoring and troubleshooting purposes, the user can check the signal of a Path in an intermediate
Port by means of a test instrument.
1350OMS-SDH allows the user to create monitor cross-connections along the route of the Path.
The monitor cross-connection is unidirectional and connects a CTP of the Path to a Test Port. The Test
Port is to be connected to the Test Instrument.
The Test Port can be PDH or SDH. In the latter case, signals coming from different Paths can be
multiplexed on the same SDH Port.
The Path can be bidirectional, unidirectional point-to-point or broadcast.
Even if the example shows the Test Port implementation in a transit Node, the operation can be done
also on the end Nodes, that is where the Path is terminated.

aa Issue 1.0
2 Test Port
Bidirectional monitoring
Monitor cross-connections
Node
Phys. Phys.
Conn. STM-N STM-N Conn.
A B
SDH SDH
Network Path Network
Test
Port/s
Port/s
Test
Instrument

To monitor both the Path’s directions, two monitor cross-connections are necessary, one per direction.
The Path’s CTPs on the STM-N Ports concern the incoming direction, from the SDH network to the Node.

aa Issue 1.0
2 Test Port
PDH Port as Test Port
Example
Two Paths transiting in the Node are STM-N Ports
monitored using two different PDH Ports.
Only one direction of the Paths is
monitored: Network 1 Network 2.
Path#1 CTP1 CTP3
SDH SDH
Network 1 CTP4 Network 2
Operation Path#2 CTP2 NAP Cable
The test instrument must be physically
connected to the Node via a cable per Test
PDH Port. NAP Instrument
The Test Port is identified by its NAP. Cable
The monitored direction depends on the
selected CTP: PDH Test Ports
CTP1 and CTP2 for Network 1 Network 2
(CTP3 and CTP4 for Network 2 Network 1)


aa Issue 1.0
2 Test Port
SDH Port as Test Port
Example
Two Paths transiting in the Node are STM-N Ports
monitored using one SDH Port.
Only one direction of the Paths is
monitored: Network 1 Network 2.
Path#1 CTP1 CTP3
SDH SDH
Network 1 CTP2 CTP4 Network 2
Operation Path#2
The test instrument must be physically
connected to the Node via a cable. CTP5 Test
CTP6 Instrument
Physical
Connection
The user must create a Physical
Connection between the SDH Test Port
and an EN that stands for the test
instrument.
SDH Test
The Test Port uses a CTP per monitored
Port
Path.
The monitored direction depends on the
selected CTP:
CTP1 and CTP2 for Network 1 Network 2
(CTP3 and CTP4 for Network 2 Network 1)

aa Issue 1.0
2 Test Port
Operation: SDH Test Port and Physical Connection creation
STM-N Port used

as SDH Test Port
Used For Test = True Create an HO-Trail

in case of LO-Path
In the STM-N Test Port properties the “Used For Test” attribute is equal to “True” (Miscellaneous
section).

aa Issue 1.0
2 Test Port
Operation
1. To monitor the way 63B 165B in 164B:

• select this CTP
• Actions Test Port Add Test Port
2Mb/s Path
between 63B
and 165B
Path routing
display
CTPs CTPs

aa Issue 1.0
2 Test Port
Operation [cont.]
2. Select the SDH Test

Port or the PDH
Test Port (NAP)
3. In case of SDH Test

Port, choose one of
its CTPs
PDH Test
Ports (NAPs)
SDH Test
Port


aa Issue 1.0
2 Test Port
Operation [cont.]
click this
Connection
icon
Details
CTP
Unidirectional To retrieve the list of

cross-connection
the monitored Paths:
CTP of SDH Test Port main tool bar
OR Search OTN
NAP of PDH Test Port Paths with test port
Besides the “Connection Details” of the Test Port cross-connection, the “Connection Details” of the
Path cross-connection is provided.

aa Issue 1.0
End of Module


aa Issue 1.0
@@SECTI
Section 3
Module 2
Alarm Management
3JK Issue 03
1350OMS

3JK Issue 03
Blank Page

Maintenance Applications Alarm Management
Document History

3JK Issue 03
Module Objectives
Localize and analyze a network fault

Configure the framed/unframed/PRA modes on 2Mb/s Paths
Use the Path Overhead Monitoring (POM)
Manage the Trace Identifier for Path, HO-Trail, Physical Connection


3JK Issue 03


3JK Issue 03
Page
1 Alarm Management 7
TableofContents
1.1 Alarms correlation in 1350OMS-SDH
1.2 Alarms scenarios
1.2.1 Fiber cut in linear network
9
17
19
1.2.2 Client failure 27
1.2.3 SNCP 31
1.2.4 MSP 37
1.3 Node alarms 43
1.4 ASAP Management 47
Switchtonotesview!
1.5 Alarms Enabling/Disabling
1.6 PDH alarm monitoring
53
63
2 Path Overhead Monitoring (POM) 67
2.1 Generalities on POM 69
2.2 POM Configuration and Alarms 73
MaintenanceApplicationsAlarmManagement

3JK Issue 03
MaintenanceApplicationsAlarmManagement

3JK Issue 03
1 Alarm Management


3JK Issue 03
Blank Page


3JK Issue 03


3JK Issue 03
Introduction
The “Elementary alarms” are the alarms detected by the equipment

and collected by 1350OMS-EML: LOS, AIS, SSF, …
1350OMS-SDH correlates the Elementary alarms to the transport

objects, that are Physical Connections, Trails, and Paths, in order to
provide the transport’s alarms.
For example:
LOS on STM-N port causes a failure on Physical Connection
SSF on VC4 causes a failure on HO-Trail
SSF on VC12 causes a failure on Path

SSF: Server Signal Failure

3JK Issue 03
Physical connection and MS Trail
Just some alarms are reported as far as Q3 NEs are concerned
Network Correlated Alarm Default Elementary 1350OMS- Elementary Alarm Probable Cause
Layer Probable Cause severity SDH’s object for Q3 NEs
Physical Equipment Failure Major SDH port Underlying Resource Unavailable
Connection
Media Failure Major SDH port Loss Of Signal
Loss Of frame
Transmitter Failure
Transmitter Degraded
Trace Identifier Mismatch
Server Signal failure
Server Media Failure Major ETH port Loss Of Signal
Underlying Resource Unavailable
MS Trail RS Failure Major MS-TP MS AIS
Remote Defect Indication
Excessive BER Major MS-TP Excessive BER
Degraded Signal Warning MS-TP Degraded Signal


3JK Issue 03
HO-Trail
Network Layer Correlated Alarm Default Elementary 1350OMS- Elementary Alarm Probable Cause for Q3 NEs
Probable Cause severity SDH’s object
HO-Trail Transport Failure Major CAP URU, SSF, U, TIM, PTM, SLM, UAT, LOMF,
Sequence Mismatch
Boundary CTP RDI Ingres and Egres, UAT Ingres and Egres
Excessive BER Major CAP EBER
Degraded Signal Warning CAP DS
Degraded Protection Warning Not Boundary CTP; SSF, U, TIM, EBER, DS, AIS : Ingres types;
SNCP enabled AIS, LOP
Quality Threshold Minor CAP Threshold Crossing Alarm
Crossed 15m or 24h CTP+boundary CTP
Transport Incoming Major Boundary CTP SSF, U, TIM, EBER, DS, UAT: Ingres types
Failure
Transport Outgoing Major Boundary CTP SSF, U, TIM, EBER, DS, UAT: Egres types
Failure

URU: Underlying Resource Unavailable

SSF: server Signal Failure
U: Unequipped
PTM: Payload Type Mismatch
SLM: Signal Label Mismatch
UAT: Unavailable Time
RDI: Remote Defect Indication
LOMF: Loss Of Multiframe
EBER: Excessive Bit Error Rate
DS: Degraded Signal
AIS: Alarm Indication Signal

3JK Issue 03
Path
Network Correlated Alarm Probable Default Elementary 1350OMS- Elementary Alarm Probable Cause for Q3 NEs
Layer Cause severity SDH’s object
Path Transport Failure Major NAP URU, SSF, U, TIM, PTM, SLM, UAT
Boundary CTP RDI Ingres and Egres, UAT Ingres and Egres
Data port SSF
Data NAP Total Loss of Capacity TX or RX
Excessive BER Major NAP EBER
Degraded Signal Warning NAP DS
Degraded Protection Warning CTP; SNCP enabled SSF, U, TIM, EBER, DS: Ingres types;
AIS, LOP
Quality Threshold Crossed 15m Minor NAP Threshold Crossing Alarm
or 24h CTP+boundary CTP
Transport Incoming Failure Major Boundary CTP SSF, U, TIM, EBER, DS, UAT: Ingres types
Transport Outgoing Failure Major Boundary CTP SSF, U, TIM, EBER, DS, UAT: Egres types
Data NAP AIS, Cient Signal Failure
Client failure Warning PDH port LOS, URU, SSF, EBER, DS, AIS, LOF, RDI
ATM port SSF, U, TIM, DS, LOMF, RDI
NAP (PDH part) SSF, DS, AIS, LOF, RDI, AUXP, RNTE
Data port URU, LOS, LOF, AIS, Queue Size Exceeded

URU: Underline Resource Unavailable

SSF: server Signal Failure
U: Unequipped
PTM: Payload Type Mismatch
SLM: Signal Label Mismatch
UAT: Unavailable Time
RDI: Remote Defect Indication
LOF: Loss Of Frame
LOMF: Loss Of Multiframe
EBER: Excessive Bit Error Rate
DS: Degraded Signal
AIS: Alarm Indication Signal
AUXP: Auxiliary Pattern
RNTE: Remote Node Transmission Error

3JK Issue 03
Alarms from graphical views
PC structure
1. Click the alarm icon

beside the object
(eg HO-Trail)
OR
“Search”


3JK Issue 03
Alarm Surveillance
1. Select “Alarms”
1350OMS-SDH’s
Alarm Surveillance
2. Start
“Alarms (SDH 1-9.1.0)”


3JK Issue 03
Alarm Surveillance [cont.]
Probable Cause
In Service
All

In Service:
Once Implemented, HO-Trails and Physical Connections can be put “In Service”.
The Path is automatically put “In Service” on commissioning.

3JK Issue 03
1.2 Alarms scenarios


3JK Issue 03
Blank Page


3JK Issue 03


3JK Issue 03
Scenario
Path
“Laser Forced ON”
HO-Trail
One-way on STM-N port
fiber cut
Elementary MS-RDI on LOS on SSF on SSF on

alarm on TP MS-CAP STM-N port CAP NAP
Correlated RS Failure on Media Failure on Transport Failure on Transport Failure on
alarm MS-Trail Physical Connection HO-Trail Path

Aim: verify that AIS is disabled and SSF is enabled by 1350OMS-SDH.

AIS is enabled just in case of “SNCP/I preferred with alarms” (see onwards).
HO-Trails and Path:
two HO-Trails: trail_68B-69B and trail_69B-160B.
one Path: from 68B-160B.
Failure:
one way cut on the STM-N optical link from 68B to 69B. The laser of STM-N card of 69B is “Forced
ON” in order to check the RDI alarms sent in the backward direction and detected by 68B.
AIS alarms:
AIS on HO CTP of 69B is disabled by alarm profile and hidden by higher priority alarm (LOS) as well.
AIS on LO CTP of 69B is disabled by alarm profile and hidden by higher priority alarm (LOS) as well.
AIS on LO CTP of 160B is disabled by alarm profile.
RDI alarms:
RDI on MS TTP of 68B is enabled by alarm profile.
RDI on CAP of 68B is disabled by alarm profile.
RDI on NAP of 68B is disabled by alarm profile.

3JK Issue 03
Physical Connection and MS-Trail alarms
PC
Port
MS-Trail

3JK Issue 03
HO-Trail alarms
HO-
Trail
HO-
Trail
routing
display
Search
Active Alarms
This is the HO-Trail on
CAP
the faulty Physical
Connection. The other
HO-Trail is not alarmed.


3JK Issue 03
Path alarms
Path
Search
Active Alarms
NAP


3JK Issue 03
Alarmed Transport Objects at Server Layer
Select an object
and do “Alarmed
Transport Objects
at Server Layer”
For Path
For HO-Trail


3JK Issue 03
1.2.2 Client failure


3JK Issue 03
Scenario
2Mb/s
Path cable cut
AIS on LOS on
Elementary alarm on TP
NAP 2Mb/s port
Client Failure on Client Failure on
Correlated alarm
Path Path

Aim: alarms generated in case of 2Mb/s signal disconnection.

HO-Trails and Path:
One 2-hop HO-Trail or two 1-hop HO-Trails (it doesn’t matter).
one Path: 68B-160B.
Failure:
2Mb/s signal disconnection on 160B.
Alarms:
LOS on the client 2Mb/s port where there is the disconnection (160B).
AIS (PDH type) on NAP belonging to the opposite client’s site 2Mb/s port (68B). NAP is made by two
parts: VC12, that monitors the SDH alarms, and P12, that monitors the PDH alarms; AIS is detected
by P12.

3JK Issue 03
Path alarms
Path
NAP Port


3JK Issue 03
Blank Page


3JK Issue 03
1.2.3 SNCP


3JK Issue 03
1.2.3 SNCP
SNCP types
SNCP/I (Inherent) with or without alarm visualization

switching criteria: AIS and LOP
no alarms
alarm setting equivalent to “not protected” Path/Trail
AIS disabled
dealt
with alarms (default) hereafter
AIS enabled on the switches’ CTPs
AIS detection “Degraded Protection” alarm on Path/Trail
SNCP/N (Not intrusive)

switching criteria: AIS, LOP, SSF, SD, TIM, Excessive BER, Unequipped
POM before matrix (ingressing) enabled on switches’ CTPs dealt
alarm detection “Degraded Protection” alarm on Path/Trail onwards in
this module

Two different SNCP mechanisms are supported for Path/Trail: SNCP/I and SNCP/N.
SNCP/I (Inherent) with or without alarm visualization:
without alarm visualization:
with alarm visualization:
AIS detection is enabled on the switches’ CTPs (HO or LO) that belong to the main and spare routes.
should AIS be detected either on the main or on the spare route, the Path/Trail “Degraded Protection”
alarm is raised.
SNCP/N (Not intrusive):
switching criteria: AIS, LOP, SSF, SD, TIM, Excessive BER, Unequipped.
POM functionality is automatically enabled by 1350OMS-SDH on the switches’ CTPs (HO or LO) that belong to
the main and spare routes.
POM (Path Overhead Monitoring):

it allows a server layer to read the OH of its client layer (e.g. POM enabled on AU4 monitors the OH of VC4).
it is just a monitoring, thus the OH is read from the VCn inside the incoming AU4/TUn without being modified.
For SNCP/N, the “Ingressing” POM is required. “Ingressing” POM is also said “Before Matrix” POM.

SD: Signal Degrade
BER: Bit Error Rate
OH: OverHead

3JK Issue 03
1.2.3 SNCP
SNCP/I preferred with alarms: Scenario
Elementary
Correlated alarm
alarm on TP
Transport Failure on
SSF on CAPs
HO-Trail
LOS on STM Media Failure on
ports Physical Connection
Degraded Protection on
AIS on LO CTP
Path
Fiber
cut Main
Spare
Protected Path
HO-Trails
Aim: verify that in case of “SNCP/I preferred with alarms”, a failure on a multi-hop route (either the
Main or the Spare) yields an alarm on the protected transport (in this example, a Path).
HO-Trails and Path:
three Not protected HO-Trails: trail_68B-69B, trail_69B-160B, trail_68B-160B.
one protected Path between 68B and 160B.
main way (multi-hop): 68B-69B-160B.
spare way (single-hop): 68B-160B.
Failure:
link cut along the Main way between 68B and 69B.
AIS alarms:
AIS on Main LO CTP of 160B is raised because the CTP is part of the bridge/switch. AIS is enabled by
“SNCP/I preferred with alarms” and is not hidden by any higher priority alarm.
AIS on LO CTPs of 69B is not enabled because the CTPs are not part of the bridge/switch.

3JK Issue 03
1.2.3 SNCP
SNCP/I preferred with alarms: PC and HO-Trail
Physical
Connection
HO-Trail


3JK Issue 03
1.2.3 SNCP
SNCP/I preferred with alarms: Path
Path
Main
CTP
Spare

3JK Issue 03
Blank Page


3JK Issue 03
1.2.4 MSP


3JK Issue 03
1.2.4 MSP
Case study
Main
Spare
Switch status: Traffic position:

NPA list switchOn onProtecting
NPA’s
PCs
Main
(Working) is
alarmed

MSP 1+1 protection between 63B and 165B.

Failure: main link cut.

3JK Issue 03
1.2.4 MSP
Faulty Physical Connection structure
Port
Main Physical Connection LOS is Minor
because of the
protection
Physical
Connection

Elementary alarms:
LOS on the two ports connected by the main link.
Correlated alarms:
“Media Failure” on the faulty Physical Connection.
Trails and Paths have no alarm because of MSP protection.

3JK Issue 03
1.2.4 MSP
NPA view
The Spare link

(magenta) is “Active”
auto: the protection

is active because of
failure condition
The Main link (blue) is The Main link (blue)

alarmed (Media Failure) is “Stand-by”

3JK Issue 03
1.2.4 MSP
User commands: example for Forced
The Spare unit, that is

frc = forced not the one selected to
issue “Forced”, is Active
2. Forced
1. Select the Main unit that is currently the Active

one Actions Manage Linear Switch …
Lockout must be issued selecting the protecting unit. Lockout gets/keeps the main unit to/in
active status.
Forced and Manual get active the unit that is not selected to issue the command:
if the selected unit is “active”, it is set to standby and the other unit is set active with Forced or
Manual status (the units are switched).
if the selected unit is already “standby”, it still remains standby and the other unit is set active
with Forced or Manual status (the units aren’t switched).
Release removes the last issued command. It must be issued selecting the unit which the last
command has been issued on that is the current standby unit.
Clear WTR must be issued on the unit that has Protection unit status equal to “wtr running”.
Commands’ priorities:
Lockout disables the usage of the protecting unit, even in case of failure. Lockout is not alarm
sensitive:
it can be issued in case of active alarm.
it remains issued in case of future alarm.
Forced is rejected in case of a previously issued Lockout command is active. Forced is not alarm
sensitive:
it can be issued in case of active alarm.
it remains issued in case of future alarm.
Manual is rejected in case of a previously issued Lockout or Forced command is active. Manual is
alarm sensitive:
it can’t be issued in case of active alarm.
it is deleted in case of future alarm.
Clear WTR stops the WTR, so the equipment doesn’t wait the entire 5 minute period to update
the protection status.
3JK Issue 03
1.2.4 MSP
User commands: example for Release
1. Select again the unit for which you issued the previous command
(example: Forced on the Main unit). It is currently in Standby status.
2. Issue the command “Release Forced”
The Spare
unit is still
Active
because the
protection is
Not Revertive
dnrv (do not revert)


3JK Issue 03
1.3 Node alarms


3JK Issue 03
1.3 Node alarms
Node alarms - NE alarms – Map alarms
Alarm Status refers to the Node Alarm Synthesis refers to the NE alarms:
alarms: Port, CAP, NAP, … Equipment, Board, Port, VC4, VC12, …
To get the Node alarms: On the map, the colors

refer to the NE alarms
select the Node Search OTN (Alarm Synthesis)
Alarmed Objects

3JK Issue 03
1.3 Node alarms
Active Alarms on Node
STM-N Port
2Mb/s Port
To get the details

(Elementary alarms) on an
object, select it Search
Active Alarms


3JK Issue 03
Blank Page


3JK Issue 03
1.4 ASAP Management


3JK Issue 03
1.4 ASAP Management
Default ASAP
Alarm’s severity depends on the ASAP (Alarm Severity Assignment

Profile) correlated to the alarmed transport.
As far as 1350OMS-SDH is concerned, ASAP is managed for Physical

Connections, MS-Trails, HO-Trails, Paths.
To check the default ASAP, do Search Physical Alarm Profiles


3JK Issue 03
1.4 ASAP Management
Objects correlated to the ASAP


3JK Issue 03
1.4 ASAP Management
ASAP correlated to an object
Select a transport
Search
Alarm Profile


3JK Issue 03
1.4 ASAP Management
Severity modification
1. Select the default ASAP Modify
2. It’s possible to
change the severity

It’s possible to modify the default ASAP as required. The new severity will apply only for new
incoming alarms.
The same procedure can be applied to modify a user created ASAP.

3JK Issue 03
1.4 ASAP Management
ASAP creation
1. Actions Physical Create Alarm Profile
2. Assign a
User Label
3. Modify the
severity


3JK Issue 03


3JK Issue 03
Three rules
Transport alarm enabling rule and Client alarm enabling rule enable/disable the TPs’ alarms:
• These rules can be set to manual; in this case the alarms’ en/disabling is up to the user.
• These rules can be related to the transport’s “Configuration state” which determines the
alarms’ en/disabling: Path (On implementation, On commissioning); Trail (On
implementation); Physical Connection (On definition, On implementation, On set-in-service).
Degradation Elementary Alarms on TPs

Failure Physical
NE
Are yes LO-Path: Connection:
alarms HO-Trail:
enabled •client TPs (PDH) •transport TPs (VC4) •transport TPs
on TPs? •transport TPs (VCn) (Port, RSOH)
Propagation Rule
1350OMS
enables the propagation Is propagation
on the “Configuration enabled?
state” of the Path: yes
•When Defined Alarms for:
•When Allocated • Paths (Client Alarms, Transport Alarms)
•When Implemented • Trails (Transport Alarms)
• Physical Connection (Transport Alarms)
•When Commissioned
TP (Termination Point): E1, VC12, VC4, RSOH, …

If “Client alarms”/“Transport alarms” are disabled, the relevant NE’s Termination Points are assigned
a “No alarm” like NE ASAP, thus their alarms are inhibited.
In order to receive the alarm indication on the 1350OMS:
the alarms must be enabled in the NE (Transport alarm enabling rule, Client alarm enabling rule).
for Path, the propagation must be enabled, too (Propagation rule).

3JK Issue 03
Default rules
Physical Connection
default Properties
Trail default
Properties
NE Path default
Elementary Properties
? Alarms
1350OMS ?
Alarms for:
• Paths (Client Alarms, Transport Alarms)
• Trails (Transport Alarms)
• Physical Connections (Transport Alarms)
Propagation rule: for Path, it defines when the alarms are propagated to the 1350OMS’s transport
objects.
Client alarm enabling rule: it is possible to decide when the Client elementary alarms in the NE have
to be enabled.
Transport alarm enabling rule: it is possible to decide when the Transport elementary alarms in the
NE have to be enabled.
Alarms can be shown if:
For Path:
Propagation rule’s hierarchical level is lower or equal to the Path’s Configuration State (Example:
“Propagation Rule” is “When Implemented” and the Path is Implemented or Commissioned).
Client alarms: the “Client alarms” attribute is Enabled. Besides the manual case, it’s Enabled if
“Client alarm enabling rule” hierarchical level is lower or equal to the Path’s Configuration State
(Example: “Client alarm enabling rule” is “On Implementation” and the Path is Implemented or
Commissioned).
Transport alarms: the “Transport alarms” attribute is Enabled. Besides the manual case, it’s
Enabled if “Transport alarm enabling rule” hierarchical level is lower or equal to the Path’s
Configuration State (Example: “Transport alarm enabling rule” is “On Implementation” and the
Path is Implemented or Commissioned).
For Trail: the “Transport alarms” attribute is Enabled. Besides the manual case, it’s Enabled if
“Transport alarm enabling rule” hierarchical level is lower or equal to the Trail’s Configuration
State (Example: “Transport alarm enabling rule” is “On Implementation” and the Trail is
Implemented or Commissioned).
For Physical Connection: the “Transport Alarm enabling state” attribute is Enabled. Besides the
manual case, it’s Enabled if “Transport alarm enabling rule” hierarchical level is lower or equal to
the PC’s Configuration State (Example: “Transport alarm enabling rule” is “On Definition” and the
PC is Defined or Implemented).
3JK Issue 03
Physical Connection

Actions Alarms Manage Alarms

The “Transport Alarm enabling rule” can be set also at Physical Connection creation.
The setting of “Transport Alarm enabling state” is meaningful only in case of “Transport Alarm
enabling rule” is set to “manual”.
Alarms can be shown if the “Transport Alarm enabling state” attribute is Enabled. Besides the manual
case, it’s Enabled if “Transport alarm enabling rule” hierarchical level is lower or equal to the PC’s
Configuration State (Example: “Transport alarm enabling rule” is “On Definition” and the PC is
Defined or Implemented).

3JK Issue 03
Path/Trail
Elementary
NE
? Alarms
1350OMS ? 2a. Set Propagation (only for Path)

Alarms for:
2b. Set Client Enabling

(only for Path)
1. Select the Path/Trail

Actions Alarms 2c. Set Transport Enabling
Alarm Rules … (for Path and Trail)

If “manual” is selected, as default the Elementary alarm detection is disabled. It’s up to the user to
enable it later on.
For Path, the “manual” option can be selected to avoid client alarms in case the PDH signal is not
connected yet and no hardware loops are put on the Path’s end-points.
The “Propagation Rule”, “Client alarm enabling rule” and “Transport alarm enabling rule” can be set
also at Path creation.
Alarms can be shown if:

Propagation rule’s hierarchical level is lower or equal to the Path’s Configuration State (Example:
“Propagation Rule” is “When Implemented” and the Path is Implemented or Commissioned).
Client alarms: the “Client alarms” attribute is Enabled. Besides the manual case, it’s Enabled if
“Client alarm enabling rule” hierarchical level is lower or equal to the Path’s Configuration State
(Example: “Client alarm enabling rule” is “On Implementation” and the Path is Implemented or
Commissioned).
Transport alarms: the “Transport alarms” attribute is Enabled. Besides the manual case, it’s
Enabled if “Transport alarm enabling rule” hierarchical level is lower or equal to the Path’s
Configuration State (Example: “Transport alarm enabling rule” is “On Implementation” and the
Path is Implemented or Commissioned).

3JK Issue 03
“Manual” for Path/Trail
Select the Path/Trail

Actions Alarms …
Manual enable and Manual disable

refer to the Transport alarms Only for
Path
On client refers to the Client alarms
Example: by issuing
Manual disable On client
Elementary
NE ? Alarms
Path
1350OMS ? properties
Alarms for:


3JK Issue 03
Auto Mode
By default, the “Auto Mode” Path/Physical Connection’s attribute is

equal to “Disabled”. It means that the Ports involved in Paths or
Physical Connections behave according to the correlated ASAP as far as
the alarm detection is concerned. Thus, if the cable (copper or fiber)
has not been yet connected, the Ports provide the suitable alarms.
By setting “Auto Mode” to “Enabled”, the Ports are prevented from

arising any alarms even if there is a correlated ASAP. Thus, if the cable
(copper or fiber) has not been yet connected, the Ports provide no
alarm. The Ports start to take into account their ASAP as soon as they
detect a signal for the first time.


3JK Issue 03
Auto Mode: example for Physical Connection
Actions Alarms Manage Alarms
Auto Mode: it reflects the user’s configuration
Current Monitoring State:

- WaitingForSignalDetection: the Port has not detected any signals since its “Auto Mode”
was set to Enabled. The Port is not able to show any alarms.
- accordingToAsap: the Port has detected a signal since its “Auto Mode” was set to Enabled.


3JK Issue 03
Exercise
Get an alarmed Path with a PDH failure: «Loss Of Signal».

Set the Path’s configuration state equal to «implemented».
Verify that «Propagation rule» is set to «When implemented».
Question: what is the status of «Client Alarm» (Enabled or Disabled)?
Open the equipment view of the involved Node and display the involved
port’s ASAP.
Display the ASAP details in order to identify the related severity.


3JK Issue 03
Blank Page


3JK Issue 03


3JK Issue 03
Introduction
PDH alarm monitoring can be enabled for 2Mb/s Paths.

Possible monitoring types:
unframed (default): only AIS can be detected.
framed: AIS, LOF, RDI, DS can be detected.
ISDN-PRA (Integrated Services Digital Network - Primary Rate Access):
this option is allowed for bidirectional Paths only.
only one of the two ports must be marked as NT (Network Termination), the one
connected to the TE (Terminal Equipment) at the User’s Premises.
on the NT port the PRA functionality is enabled (it can detect the AUXP alarm, too).
on the non-NT port the “framed” behavior is activated.
Leased line PRA:
this option is allowed for bidirectional Paths only.
one or both ports can be marked as NT.
on the NT ports a non-standard PDH monitoring is activated (it can detect the RNTE
alarm, too).
on the non-NT port the “framed” behavior is activated.

AUXP (Auxiliary Pattern) is a sequence 01010101…

RNTE (Remote Node Transmission Error)

3JK Issue 03
How to proceed
1. Select the 2M Path Actions Path properties

Alarms PDH Alarm Monitoring
The Path status can be defined,
allocated or implemented.
2. Choose the
monitoring type
3. Set the port(s) as NT

(PRA cases)


3JK Issue 03
Blank Page


3JK Issue 03
2 Path Overhead Monitoring (POM)


3JK Issue 03
Blank Page


3JK Issue 03
2.1 Generalities on POM


3JK Issue 03
POM: Path Overhead Monitoring
In the NEs that fulfill AU4/TUn pass-through, the VCn is not terminated.
The VCn is terminated in the NEs with the HO-Trail’s or Path’s end-
points (CAP and NAP).
However, it is possible to read the VCn’s OH inside the AU4/TUn by
applying the HPOM/LPOM.
POM is just a monitoring, thus the OH is read from the VCn inside the
incoming AU4/TUn and is rewritten without any modification in the VCn
of the outgoing AU4/TUn.
POM is used to monitor alarms and to implement Performance
Monitoring on the boundary CTPs.
By default, POM is enabled:
in case of Paths and HO/LO-Trails ending on an external network, on the
boundary CTPs.
in case of SNCP/N protection, on the CTPs of the nodes where the path/trail
enters and exits the ring, that is on the “Involved” CTPs.

HPOM: Higher order POM. It acts on AU4/VC4.

LPOM: Lower order POM. It acts on TU12/VC12 or TU3/VC3.

3JK Issue 03
POM for HO-Trail
HO-Trail
NE A W X NE B Y E NE C
HPOM HPOM
before after
HO CTP MATRIX HO CTP

CxC
X Y
HPOM HPOM
after before
HO CTP X:
HPOM Before Matrix monitors the signal in the direction from NE A to NE C
HPOM After Matrix monitors the signal in the direction from NE C to NE A
HO CTP Y:
HPOM Before Matrix monitors the signal in the direction from NE C to NE A
HPOM After Matrix monitors the signal in the direction from NE A to NE C

There is a HO-Trail between NE A and NE C passing through NE B.

NE A and NE C terminate the HO-Trail: NE A and NE C have both HO CTP and CAP.
NE B is a transit node where the AU4 is put in pass-through: it has only HO CTPs.
POM can be enabled on HO CTPs of NE A and NE C as well, but it isn’t useful because the same
information is available on CAPs.

3JK Issue 03
POM for Path
Path
HO-Trail HO-Trail
NE A NE C
W X NE B Y E
PDH PDH
LPOM LPOM
before after
LO CTP MATRIX LO CTP

X CxC Y
LPOM LPOM
after before
LO CTP X:
LPOM Before Matrix monitors the signal in the direction from NE A to NE C
LPOM After Matrix monitors the signal in the direction from NE C to NE A
LO CTP Y:
LPOM Before Matrix monitors the signal in the direction from NE C to NE A
LPOM After Matrix monitors the signal in the direction from NE A to NE C

There is a HO-Trail between NE A and NE B and a HO-Trail between NE B and NE C.

There is a Path between NE A and NE C passing through NE B.
NE A and NE C terminate the Path: NE A and NE C have both LO CTP and NAP.
NE B is a transit node where the TUn is put in pass-through: it has only LO CTPs.
POM can be enabled on LO CTPs of NE A and NE C as well, but it isn’t useful because the same
information is available on NAPs.

3JK Issue 03
2.2 POM Configuration and Alarms


3JK Issue 03
Case study: Path routing display
Without POM LO CTPs are
Alarmed
NOT alarmed
NAP
Attenuation

To enable POM After matrix (egressing) and POM Before matrix (ingressing) on
all the LO CTPs traversed by the Path: select the Path Actions Other
Intermediate CTP monitoring Enable
With POM LO CTPs are

Alarmed
alarmed
NAP
Attenuation


There is a Path between 68B and 160B that makes use of two 1-hop HO-Trails.
The Path has Degraded Signal alarm due to Degraded Signal alarm on 160B’s NAP.
It means that the attenuation occurs in the direction from 68B to 160B.
To find out whether the attenuation occurs in the 68B-69B Physical Connection or in the 69B-160B
one, let’s enable POM on the Path.
POM can be enabled/disabled on all the LO CTPs of a Path.
By means of POM, Degraded Signal alarm is raised on LO CTPs, too.

3JK Issue 03
Alarmed TPs
Path
After matrix: Egressing

Before matrix: Ingressing
Attenuation

LO CTP
LO CTP NAP

Since the 69B’s LO CTPs are alarmed, the attenuation occurs in the 68B-69B Physical Connection.
LO CTPs’ alarms are not correlated to the Path. The Path’s alarm is due to the NAP’s alarm. The
CTP’s alarms are correlated to the transport just in case of boundary CTP.

3JK Issue 03
Object properties
CTP properties
Path properties
CTP with
POM
enabled
none
CTP with
POM
disabled
all

For most of the NE types, by enabling the POM the POM alarms are enabled, too. The “POM
Egressing/Ingressing Disabled Alarms” attributes are set to “none”.

3JK Issue 03
Boundary CTP – case study
Boundary HO CTP Boundary LO CTP
External
Network AU4-AIS
HO-Trail
Path
POM is automatically configured on the boundary CTPs.

The boundary CTPs are:
• HO CTP toward EN1 in 68B
• LO CTP in 160B

This subnetwork is made of 3 real NEs and an External Network.

Failure: “AU4-AIS” coming from EN.

3JK Issue 03
Boundary CTP – Properties
Boundary
CTP
Properties
For example, AIS is

disabled on the CTP
FERF = RDI
“All Alarms” like ASAP is

set on the POM Ingressing
AIS is not detected by the

CTP itself, but by the POM
on the CTP

FERF: Far End Remote Failure.

RDI: Remote Defect Indication.
In the addressed case study, no FERF/RDI is detected because its detection is disabled on the POM
Egressing.

3JK Issue 03
Boundary CTP of HO-Trail
HO-Trail

The alarms raised by boundary CTPs are correlated to the transport objects, that is to Paths and HO-
Trails.

3JK Issue 03
Boundary CTP of Path
Path

The alarms raised by boundary CTPs are correlated to the transport objects, that is to Paths and HO-
Trails.
In this example, “Client Failure” is not due to the AU4-AIS coming from EN, but is due to a failure on
the 2Mb/s port.

3JK Issue 03
3 Trace Identifier


3JK Issue 03
3 Trace Identifier
Transports that support TI
Trace Identifier is supported by:
J0 in RSOH of STM-N frame
HO-Trails/HO-Paths
J1 in VC4 POH
LO-Paths
J1 in VC3 POH
J2 in VC4 POH


3JK Issue 03
3.1 Trace Identifier for Physical Connection


3JK Issue 03
Scenario
Trace Identifier J0
Regenerator Transmitted Florence
ce
Port 2
Port 1
NE1 NE2
ren
o
TX RX
Fl TX RX
Port A
Port Z
ce e
ni RX om
Ve TX R
STM-N
Trace Identifier J0 Trace Identifier J0

Expected Rome Expected Florence
Received Rome Received Florence
Transmitted Venice Transmitted Rome
Should Received be different from Expected:

• TIM (Trace Identifier Mismatch) alarm is raised by the Ports
• Media Failure alarm is raised by the Physical Connection
TIM affects the Physical Connection itself and all the Trails/Paths over the Physical Connection.

3JK Issue 03
Configuration
Example with no
regenerator 1. Select the Physical Connection
Actions Configuration
Manage Trace Identifier
2. Choose Set
3. Next
The Physical Connection’s Trace Identifier can be configured either by means of the automatic
procedure or manually by the user.
The manually configured TI can not be overwritten by the automatic procedure.
The TI configured by the automatic procedure can be overwritten by the manual configuration.
Automatic procedure: Actions Physical Discover Physical Topology; Automatic Generation of
Trace Identifier.

3JK Issue 03
1. Edit the Sent Trace Identifiers
2. To enable the
TI analysis, set
“Expected…”
to True
4. Apply
3. In case of Regenerator, set
Yes and then set the beneath
“Expected Trace Identifier”
It’s possible to set “Expected Trace Identifier Enabling” to True on A only if “Sent Trace Identifier Z”
has been set. And vice versa.
“Please specify the Expected...” must be set to “yes” in case of regenerator. If it is set to “False”
for A-end, that is the link from Port Z to Port A has no regenerators, the value set in “Sent Trace
Identifier” for Z is automatically assigned to “Expected Trace Identifier” for A. And vice versa.
In order not to have any burst of alarm during the setting of Trace Identifier, it’s advisable to do it in
two phases:
first, set the “Sent Trace Identifier” and leave “Expected Trace Identifier Enabling” to False.
then, enable the comparison between the Expected and the Received values by setting “Expected
Trace Identifier Enabling” to True.
In order not to have any burst of alarm during the removing of Trace Identifier, it’s advisable to do it
in two phases:
first, disable the comparison between the Expected and the Received values by setting “Expected
Trace Identifier Enabling” to False.
then, set the “Sent Trace Identifier” to blank (empty field).

3JK Issue 03
TI on the STM-N Port
1. Open the properties of a

Physical Connection’s Port


3JK Issue 03
Exercise
Take a Physical Connection and check the TI of its ports. Their TI may
be already configured by the “Automatic Generation of Trace
Identifier” procedure.
Configure manually the TI for the Physical Connection.
Read the TI of the Physical Connection.
Check the TI of the ports.
Disable the TI.


3JK Issue 03
3.2 Trace Identifier for Path and HO-Trail


3JK Issue 03
Points
Should Received be different from Expected:
Equipment • TIM (Trace Identifier Mismatch) alarm is raised by the NAP/CAP/CTP
• Transport Failure is raised by the Path/Trail
Trace Identifier J1/J2
Received Ingressing TI
Provider 3 Expected Berlin
Expected Ingressing TI
Hamburg Received Berlin
Transmitted Hamburg NODE
LO CTP / HO CTP
Provider 2 TI Expected
TI Received X STM-N
Provider 1 TI Sent NAP / CAP

Berlin Trace Identifier J1/J2
Expected Hamburg Received Egressing TI
Received Hamburg Expected Egressing TI
Equipment
Transmitted Berlin Equipment

The mechanism of Trace Identifier bytes J1/J2 is used to control the Trail/Path continuity.
Trace Identifier consists of up to 16 bytes: 15 data bytes (user definable) + 1 byte (checksum).
Trace Identifier is available for the following levels:

J0: Regenerator Section (RSOH)
J1: VC4 HO Path, VC3 LO Path (34/45Mb/s)
J2: VC12 LO Path (2Mb/s)
Trace Identifier operates in the same way in every level: it is set on the transmit side (TX) which
assigns a name. This name is then compared on the receive side (RX) of the remote Node with the
expected Trace Identifier.
TI is suitable for HO-Trails and for the Paths that concern VCx NAPs, such as PDH Paths, Server Trails
of Ethernet concatenated Paths, ...
TI monitoring can be enabled on CTPs only if “Intermediate CTP monitoring” (POM: Path overhead
Monitoring) has been activated.
TI can be enabled also if one of the two NEs is an External Network.
J1/J2 Trace Identifier can be set up on allocated/implemented Path/Trail.
TIM is a transport failure.

TIM on HO-Trail: TIM affects the HO-Trail itself and all the Paths over the HO-Trail.
TIM on Path: TIM affects the Path itself.
3JK Issue 03
Configuration
1. Select the Path/Trail Actions Other

Trace Identifier Management
2. Next


3JK Issue 03
4. Set the Sent TI for

the two NAPs/CAPs
(max 15 characters)
3. Enable TI on the
two NAPs/CAPs
5. Do Apply. The
enabling takes
a while.

1350OMS-SDH configures the NEs in this way:

first, it enables the transmission of TI
then, it enables the reading and the comparison between the Received and the Expected values
so that there’s no transient alarm.
To remove the TI configuration, repeat the setting procedure setting to “no” both “Enable Trace
Identifier A” and “Enable Trace Identifier Z”.
Example: if “Enable Trace Identifier Z” is set to “no”, the Z-end doesn’t transmit any Trace Identifier
and the “Expected Trace Identifier” on A-end is disabled. Thus, TIM alarm can be detected just by Z-
end.

3JK Issue 03
Trace Identifier analysis on end-points
NAP Properties
Path Properties
Select the NAP/CAP Actions

Trace Identifier… Read

3JK Issue 03
Trace Identifier analysis on intermediate points
CTP
TI
ad
Ingressing
TI
TI
Re
sent: A-Venezia
Egressing sent: Z-Roma
1. Enable POM on CTPs:

select the Path/Trail
Actions Other
Intermediate CTP
monitoring Enable
2. Read the TI on CTP:
select the CTP Actions
Trace Identifier…
Read
By issuing “Intermediate CTP monitoring” on the Path/Trail, POM (Path Overhead Monitoring) is
enabled on the CTPs along the Path/Trail.
The Trace Identifier reading on CTP yields four values:

expectedETraceId
expectedITraceId
receivedITraceId
receivedETraceId
“E” stands for Egressing: in the way from the NE’s matrix to the STM port the CTP belongs to.
“I” stands for Ingressing: in the way from the STM port the CTP belongs to the NE’s matrix.

3JK Issue 03
Exercise
Set the TI for a Path/HO-Trail

Read the TI
Disable the TI


3JK Issue 03
End of Module
Alarm Management


3JK Issue 03
@@SECTI
Section 3
Module 3
Performance management
xxx Issue 03
1350OMS

xxx Issue 03
Blank Page

Maintenance Applications Performance management
Document History

xxx Issue 03
Module Objectives
start and stop Performance Monitoring

display the PM results
export PM information
compare the NML’s PM DB with the EML’s PM DB


xxx Issue 03


xxx Issue 03
Page
1 PM from 1350OMS-SDH point of view 7

TableofContents
2
3
4
PM
PM
PM
basic operation
result
advanced operation
13
23
29
Switchtonotesview!
MaintenanceApplicationsPerformancemanagement

xxx Issue 03
Switchtonotesview!
MaintenanceApplicationsPerformancemanagement

xxx Issue 03
1 PM from 1350OMS-SDH point of view


xxx Issue 03
Objectives
NE (Near End)
Node 1 SDH network Node 2
FE (Far End)
FE counters NE counters
NE counters FE counters Objective

Quality of Service
Maintenance
(QoS)
ES (NE/FE)
X X
- Errored Second -
BBE (NE/FE)
X X
- Background Block Error -
Counters SES (NE/FE)
X X
- Severely Errored Second -
UAS unidirectional
bidirectional
- Unavailable Second - (NE/FE)
15 minutes Not Available X
Time
granularity Available for some
24 hours X
equipment types
Let’s take the two end-nodes of a Physical Connection, Trail or Path.

One node is the node where you are located, this is the near end node. The node at the other end is
the far end node.
Bit errors and defects detected locally at the receiver:
are used for local near end performance monitoring (PM).
their quantity is transmitted to the far end over SDH overhead bytes (i.e. REI and RDI) for far end
PM at the far end.
REI and RDI received locally are used for local far end PM.

xxx Issue 03
“PM TPs” and “PM Transports” for SDH
LO Path
MS Trail MS Trail
Phys. Phys.
Conn. Conn.
PDH NA
A
TUn
TUn
MST
MST
TUn
AU4
TUn
AU4
MST
MST
AU4
AU4
VC4
VCn
VC4
VC4
VC4
VCn
RST
RST
RST
RST
Pm
PPI
PPI
Pm
SPI
SPI
SPI
SPI
… … … …
Ei
Ei
X X X X X X X
NE1 (+) (+) NE2 (+) (+) (*) (*) External Network
default PM TP with intermediate PM TP
PM Transport default PM TP
External Network (*) (optional) (+)
LO/HO Path NAP Boundary LO/HO CTP LO/HO CTP
HO-Trail CAP Boundary HO CTP HO CTP
MS-Trail MS TTP - -

TP: Termination Point
PM Transport and its PM TPs are automatically created when a measure is created on a transport (Path/
Trail).
Automatically monitored points:

For Path:
unidirectional Path: the sink NAP. NE counters.
bidirectional Path: the two NAPs. NE and FE counters.
broadcast (unidirectional) Paths: the sink NAPs. NE counters.
For HO-Trails: the two CAPs. NE and FE counters.
For HO-LO Paths and HO-Trails ending on External Network: the boundary CTPs. NE and FE counters.
For MS-Trail: the two MS TTPs. NE and FE counters.
Optional monitored points: the user can activate PM on the intermediate TPs on TP basis.
For HO-LO Paths and HO-Trails: the CTP selected by the user or all of the Path/Trail’s CTPs. NE and
FE counters.
Performance Monitoring on RST and on CTPs (pointer justification) are managed by 1350OMS-EML.

xxx Issue 03
PM objects
PM domain
DB Administration
Report Archive
Measure
Profile session
• Report Profile periodically

PM transport copies the PM data to .csv files
•Archive Session is an
administration issue that is
used to archive PM data on a
file in order to free space on
PM TP the PM database (it’s not dealt
in this training)

Measures are defined on 1350OMS-SDH’s transport entities (Path and Trail) and requested on NE’s
Termination Points (TPs).
For each transport entity a PM transport is created. For each TP a PM TP is created.
1350OMS-SDH requests 1350OMS-EML to start the counters on NEs whose TPs have to be monitored.

xxx Issue 03
Procedure
1. Select a Path/Trail and “Create and Start” PM:

Measure, PM Transport, and PM TPs are automatically created
2. Open the PM Domain
3. Locate and retrieve the measure
4. Retrieve the PM Transport
5. Retrieve the PM TPs:
they provide the PM results
6. To stop the PM, select the Path/Trail and “Stop” PM
7. Delete the Measure
PM Domain
Measure Measure
PM Transport PM Transport Each Measure contains
one PM Transport that
PM TP PM TP PM TP
contains the PM TPs
PM TP
PM TP

Measure: it defines the objective, the time granularity and other parameters of the PM.

xxx Issue 03
Measure lifecycle
deimplement
PM “Create and path/trail
ACTIVATED STANDBY
Start” yields an
“activated” Measure Measure Measure
implement
path/trail Delete
Measure
remove
Start PM Stop PM path/trail
remove
STOPPED path/trail TERMINATED
Measure Measure
implement
deimplement/
path/trail Delete Delete
deallocate
Measure path/trail Measure

Measure:
Activated: TP counters are started, hence PM results and PM alarms can be inspected.
Stopped: TP counters are stopped. Only former PM results can be inspected.
Standby: the monitoring activities are interrupted temporarily because the PM Transport is
deimplemented.
Terminated: the monitoring activities are interrupted forever because the Transport has been
removed. This state can be seen if the Measure’s attribute “Auto Purge” is set to “False”.

xxx Issue 03
2 PM basic operation


xxx Issue 03
PM creation for an already created transport
Path list
1. Select the
Path/Trail
Actions PM ...

The Stop commands and the commands for the Intermediate TPs are available only if a PM is active.

xxx Issue 03
PM indication in routing display
Measure’s
granularity
Purple border for the TPs with active PM


xxx Issue 03
PM creation during the transport creation
Create Trail
Create Path

For HO-Trail and Path, PM can be created also during their creation:
set the “Automatic PM Creation” attribute to True.
“Automatic Purge of the Measure”: if set to True, the measure is deleted when it is Terminated, that
is when the Path/Trail is removed.
the Measure is 24h QoS.

xxx Issue 03
PM Domain and Measures retrieval
1. To retrieve the PM
domains: Search PM
PM Domains on NML
2. To retrieve the
Measures: select SDH
Search PM Measures
PM Domain
Measure Measure
PM Transport PM Transport
PM TP PM TP PM TP
PM TP PM TP


xxx Issue 03
Measure
Measures list
Measure User Label (eg: first PM on the path)=

“Path User Label”_path_auto_0
Measure
properties

Consistency: a measure is said consistent if its PM TPs provide the expected data to the measure.
Layer: network layers of the monitored objects.
All Layers
HO for VC4 and AU4
LO for VC12 and VC3
DATA for ATM Path, 4xAny, ISA-ESx and PREA
CBR for WDM Path
MS for Multiplex Section
“Auto Purge” and “Purge”: if “Auto Purge” is set to True, the measure is automatically removed when
it is in the status said by “Purge”. Default values: “Auto Purge”= false; “Purge”= “At Termination”.
Security Label: not operational.
Collect Counter: if True, the collection of the performance counters is provided for all the enabled TPs.
Automatic: True if the measure has been automatically created and activated on a Path/Trail
implementation.
Default TCA: True if the measure uses the default TCA (Threshold Crossing Alarm). TCA is not
operational in this release.

xxx Issue 03
PM Transport and PM TPs
Measure
To get the PM Transport:
PM Transport
PM TP
• double click the Measure or
PM TP
• select the Measure Search PM Transports or
• select the Path/Trail Search PM Transport
To get the PM TPs:

• double click the PM Transport or
• select the PM Transport Search PM TPs

There are two PM TPs because this PM Transport corresponds to a Path between real NEs (there are no
boundary TPs) and the monitoring on intermediate TPs has not been activated.

xxx Issue 03
Operation from Measure
... Report Profile:

see onwards
Delete Measure
Consist Measure: it
must be run
whenever
Generate ...: see “Consistency” is “Not
onwards Consistent”

xxx Issue 03
Navigation: from Transport to PM Transport
Select the Transport

Search PM Transport

Navigation from Transport to PM Transport: without opening the PM Domain and the Measures list, it’s
possible to get the PM Transport directly from the Transport.

xxx Issue 03
Navigation: from PM objects to SDH objects
From “PM Transport” to

“Transport”
From “PM TP” to “TP”


xxx Issue 03
3 PM result


xxx Issue 03
3 PM result
Get the result
Select the object

Actions Generate …
PM TP
Measure
PM Transport

Since for each Measure there’s only one PM Transport, the report from Measure is equivalent to the
report from PM Transport.
The Measure and the PM Transport reports provide the counters of all the PM TPs.

xxx Issue 03
3 PM result
Get the result [cont.]
PM results are
retrieved from NE
by 1350OMS every
2 hours (for the
15min) or every 24
hours (for the 24h)
Choose “Start
Time” and
“End Time”

1350OMS-EML performs the periodic collection of the PM results and stores them in a specific PM
database.
1350OMS-SDH accesses the PM database and correlates the PM results with the PM TPs and PM
Transports.

xxx Issue 03
3 PM result
Get the result [cont.]
Tabular
Line chart
Bar chart

xxx Issue 03
Exercise
Create and Start PM on a Path and on a HO-Trail.

Check the PM Transport and the PM TPs.
Retrieve the result.


xxx Issue 03
Blank Page


xxx Issue 03
4 PM advanced operation


xxx Issue 03
PM on Path/Trail terminated on External Network
Sink
(POM Ingressing) Path between a real NE
CTP Matrix CTP and an External Network.
Source Two one-hop HO-Trails.
(POM Egressing)
Boundary
CTP
External
Network

POM: Path Overhead Monitoring.

POM Ingressing is also said POM Before Matrix.
POM Egressing is also said POM After Matrix.
The LO CTP of board02/port01 of 68B is a boundary CTP because it is the first LO CTP from the External
Network side. On the boundary CTP, POM is activated automatically. By creating PM on the Path/Trail,
PM is automatically activated on POM, too.
Both Near End and Far End counters are activated on both CTP Source and CTP Sink.

xxx Issue 03
PM on intermediate TP
First, PM must be activated on Path/Trail

PM is activated on the default TPs
Then, PM can be managed for intermediate PM TPs

from the Path/Trail
Actions PM Add Intermediate PM TP
Actions PM Remove Intermediate PM TP
PM is activated on all the CTPs
from a CTP
Actions Add Intermediate PM TP
Actions Remove Intermediate PM TP
PM is activated only on that CTP


xxx Issue 03
PM on intermediate TP [cont.]
Sink
(POM Ingressing)
CTP Matrix CTP
Source
(POM Egressing)

POM: Path Overhead Monitoring.

POM Ingressing is also said POM Before Matrix.
POM Egressing is also said POM After Matrix.
Both Near End and Far End counters are activated on both CTP Source and CTP Sink.

xxx Issue 03
Report Profile: available profiles
Report Profile holds the rules for creating the files that record the PM results
(BBE, ES, SES, UAS).The files are generated every “window” time.
To look for the available profiles:

select the SDH PM Domain Search Report
Profiles
To look for the Measures correlated to a profiles:

select the Report Profile Search PM Measures


xxx Issue 03
Report Profile: creation
To create a profile:
select the SDH PM Domain Actions Create Report
Profiles
• files: one file with the results of all the measures
• file: a file per measure

The CSV format can be exported to Microsoft Excel.
Destination Type:
files: a single report file is created at the chosen frequency (window) for all the measures correlated
to the report. For example, by correlating 4 different 15min measures to a report having a window of
1 hour, 24 files are created in a day: i.e. every hour a single file is created with the results of all the
measures. The file’s name is: _Report’s User Label_window_x_N00000.csv (example:
_My_Report_15MIN_8_N00000.csv).
file: a report file is created at the chosen frequency (window) for each measure correlated to the
report. For example, by correlating 4 different 15min measures to a report having a window of 1
hour, 24x4 = 96 files are created in a day: i.e. every hour a file is created for each measure. The
file’s name is: _Transport’s User Label_window_x_co.csv (example:
_MyPath_auto_0_15MIN_8_co.csv).
x: number of the report.
Window: it must be suitable for the granularity:

granularity = 15min window = 15min, 1h, 2h, 24h.
granularity = 24h window = 24h, 1week, 1month, 1year.

xxx Issue 03
Report Profile: un/correlation from/to a Measure
2. Choose the profile
1. To associate the profile to 3. To disassociate the profile

the measure: select the from the measure: select the
Measure Actions Measure Actions
Correlate with Report Profile Uncorrelate with Report Profile
To delete a Report Profile:

it must not be correlated to any measures.
open the Report Profile list select the Report Profile Actions Delete Report Profiles.

xxx Issue 03
Manual exports
Server as destination
Export the PM TPs list to a CSV file
Export the results of a given measure over a period to a CSV file
Export the results of a given PM TP over a period to a CSV file
PC as destination
Export any list to a CSV file
See the next slides


xxx Issue 03
Manual exports: PM TPs list
To export the PM TPs list to a CSV file on the Server:
select the SDH PM Domain Actions Export TPs to To CSV file
edit the path the file is to be saved to in the server (/tmp/ as default) and do
Apply.
the file name is: TPList.csv
It’s possible to specify also the file name: e.g. /tmp/myfile
Example of TP:
SDH@SDH_1-9.1.0/Path_68-160_path_auto_0/Path_68-160/68B/r01s1b20p001c1(Sink)
measure PM transport Node TP


xxx Issue 03
Manual exports: results of a given measure
To export the results of a given measure over a period to a CSV file on

the Server:
select the Measure Actions Generate CSV Report
choose
Start Time, End Time
Granularity
the path the file is to be saved to in the server (/tmp/ as default)
and do Apply.
the file name is: CPM_NM_CSV_EXPORT_2011-04-25-14-04-10.csv
date time
It’s possible to modify the file name by appending a string:

Example: by setting /tmp/myfile as path, the file name will be
myfileCPM_NM_CSV_EXPORT_2011-04-25-14-04-10.csv


xxx Issue 03
Manual exports: results of a given PM TP
To export the results of a given PM TP over a period to a CSV file on the

Server:
select the PM TP Actions Generate CSV Report on NML TP
choose
Start Time, End Time
Granularity
the path the file is to be saved to in the server (/tmp/ as default)
and do Apply.
the file name is: CPM_NM_CSV_EXPORT_2011-04-25-14-04-10.csv
date time
It’s possible to modify the file name by appending a string:

Example: by setting /tmp/myfile as path, the file name will be
myfileCPM_NM_CSV_EXPORT_2011-04-25-14-04-10.csv


xxx Issue 03
Manual exports: any list
Export any list to a CSV file on the PC

open the list
click the “Export data” icon
to get a better data visualization in the CSV file

in Windows Excel, select the first column
then, use “Data” “Text to columns”

The CSV file is not easy to read, because the values of a GUI row are gathered in one single cell of the
first column of the CSV file. Once the CSV file has been created, it’s possible to arrange its content to
get a better result visualization, that is a data per cell.

xxx Issue 03
PM Audit
The user can carry out a comparison between the EML’s PM DB and the
NML’s PM DB to discover the TPs with different PM configuration.
NML’s
PM Database
PM Transport
EML’s
PM Database Measure
NE’s
MIB Supposed Monitored NE PM NE (NML NE)
TPs to be Monitored TPs Audit on
PM TP basis PM TPs (*)
aligned
Audit on
PM NE basis
(*) PM TPs can be retrieved

from PM Transport
PM NE is available if at least one of its PM TPs is required for a PM Transport.

xxx Issue 03
PM Audit [cont.]
Audit on PM NE basis:
1. Open the PM NE list: select SDH in “PM Domains on NML”
Search NML NEs
2. Select a PM NE Actions
Generate Audit for NE
Audit on PM TP basis:
1. Select a PM TP Actions
Audit TP


xxx Issue 03
PM Audit [cont.]
In case of “PM Audit on PM TP basis”, just one row is prompted
…-PMNETR15: Near End 15min In case of Maintenance measure, both NE and FE

Monitored TPs are configured in the EML’s PM DB,
…-PMFETR15: Far End 15min but just the NE PM TP is issued in the NML’s PM DB.
…-PMFE1d: Far End 24h
However, the measure provides both the NE and FE
…-PM1d: 24h QoS counters.


xxx Issue 03
Exercise
Create a Report Profile and correlate it to a measure.

Export the PM TP list.
Export the results of a given measure.
Export the results of a given PM TP.


xxx Issue 03
Blank Page


xxx Issue 03
End of Module
Performance management


xxx Issue 03
@@SECTI
Section 3
Module 4
xx Issue 01
1350OMS

xx Issue 01
Blank Page

Maintenance Applications Consistency and isolation
Document History

xx Issue 01
Module Objectives
check and fix the misalignment between the 1350OMS-SDH’s DB and the NE’s
MIB
operate the network in case of communication problems between the NEs
and 1350OMS


xx Issue 01


xx Issue 01
Page
1 Consistency audit and download procedures 7

TableofContents
2 NE isolation and recovery 19
Switchtonotesview!
MaintenanceApplicationsConsistencyandisolation

xx Issue 01
Switchtonotesview!
MaintenanceApplicationsConsistencyandisolation

xx Issue 01
1 Consistency audit and download
procedures


xx Issue 01
1 Consistency audit and download procedures
DB misalignment
The 1350OMS-SDH’s DB may differ from the NE’s MIB.
The user can execute:

Consistency Audit, to compare the two DBs and eventually fix the
differences.
Global Download, to completely download the configuration stored in the
1350OMS-SDH’s DB to the NE’s MIB.
Among the others, here some Elementary objects addressed by these

procedures:
NE
Protection : linear protection (MSP), msProt2F, msProt4F
SDH TP : msTP, hoCTP, loCTP, CAP, NAP, pmTP, tct, tcm, …
Port : sdh, client, wdm, wdm client, xdsl, …
WDM TP : oms CTP, CAP, client TTP, CTP, MS, ...
Cointo : ho, lo, wdm client, wdm OCH, otu, odu2, odu3, ...
OTU/ODU TP: otu CTP, odu3 CTP, odu2 CTP, odu1 CTP, ...

Cointo: Connection In Topology
Consistency Audit and Global Download act on the objects known by 1350OMS-SDH.
Example:
Scenario: in the NE’s MIB there are an HO cross-connection (AU4-VC4) and a LO cross-connection
(TU12-VC12) that accomplish an add/drop between a 2Mb/s and an STM signals. But 1350OMS has
no Physical Connection that involves that STM Port. So, 1350OMS-SDH doesn’t have that STM Port
and the following termination points: the HO-CTP (AU4), the CAP (VC4), and the LO-CTP (TU12).
Consistency Audit and Global Download can act on the LO cross-connection (the NAP is available
in 1350OMS-SDH) but not on the HO cross-connection (both AU4 and VC4 are not available in
1350OMS-SDH).

xx Issue 01
Consistency audit
It verifies the alignment between the 1350OMS-SDH’s DB and the NE’s

MIB.
It concerns only the Elementary objects of the 1350OMS-SDH’s DB which

correspond to the ones of the NE’s MIB (ports, single TPs, …).
It can be done if the NE is reachable and in Download Disabled mode.
While it’s ongoing, the user can work on the system.
All current operation on the NE must be completed before the

transition from the Download Disabled to Download Enabled mode and
vice versa.
Two types of Audit can be done according to the need: Mark Audit and
Notify Audit.


xx Issue 01
Consistency audit [cont.]
MARK Audit - check and fix the differences

The system provides the differences between the SDH’s DB and the NE’s MIB.
When the command “Download Enable” is performed these differences are
downloaded to the NE’s MIB.
In the end all the objects are aligned.
NOTIFY Audit - check the differences

The system provides the differences between the SDH’s DB and the NE’s MIB.
When the command “Download Enable” is performed these differences are
NOT downloaded to the NE’s MIB.
To realign the SDH’s DB and the NE’s MIB, it is necessary to perform a “Global
Download” on the NE (see afterwards).


xx Issue 01
Consistency audit: how to proceed
1. Set the Node to Download Disabled: Select the Node

Actions OTN Configure Download Disable
2. Select the Node Actions OTN Consistency Audit
“Mark Audit” or “Notify Audit”
Download
Disabled
“All layers
During the operation the
processed”
Align activity in Node View displays
progress = Audit instead of

xx Issue 01
Consistency audit result
The user has several options to display
the misaligned objects:
1. Display all the not aligned objects
In the Node View, select this

icon Search Not aligned
objects


xx Issue 01
Consistency audit result [cont.]
2. Display only the not aligned

objects that are traffic impacting
In the Node View, select this icon

Search Not aligned objects
(traffic impacting)


xx Issue 01
Consistency audit result [cont.]
3. Display only the not aligned TPs and Cross Connections
In the Node View, select the Node

Search OTN Not aligned TPs
and Cross Connections


xx Issue 01
Global download
It performs the alignment between the SDH’s DB and the NE’s MIB by
downloading the configuration of all the Elementary objects to the NE.
It can be done independently from the Audit procedures.
It is available when:
the NE is not isolated
the Node is in Download Enabled mode
the system is in “full functionality” run level (check it in PMC)

Global Download aligns the NE’s MIB to the SDH’s DB taking into account the objects known by
SDH.
Example:
Scenario: in the NE’s MIB there are an HO cross-connection (AU4-VC4) and a LO cross-
connection (TU12-VC12) that accomplish an add/drop between a 2Mb/s and an STM signals. But
1350OMS has no Physical Connection that involves that STM Port. So, 1350OMS-SDH doesn’t
have that STM Port and the following termination points: the HO-CTP (AU4), the CAP (VC4),
and the LO-CTP (TU12).
The Global Download executed on this NE deletes the LO cross-connection (1350OMS-SDH has
the NAP/VC12) but doesn’t delete the HO cross-connection.

xx Issue 01
Global download [cont.]
1. Select a Node Actions OTN Consistency Download

Global Download
Download
Enabled
“All layers
During the operation the processed”
Align activity in progress = Node View displays
Download instead of
N.B. While Global Download is ongoing, any further NE’s MIB modification
issued by the user is not accomplished. For example, the implementation
of a Path does not succeed whereas the Path allocation does.

xx Issue 01
Exercise
Set Download Disabled on all the NEs involved in a Path.

Remove the Path (uncommission, deimplement, deallocate and
remove): it concerns just the 1350OMS-SDH’s DB.
Perform the Notify Audit on the Nodes.
Check the “not aligned objects (traffic impacting)” to see the
misaligned NAPs and CTPs.
Set Download Enabled on all the Nodes.
Verify that the misalignment is still present.
Fix the situation aligning the NEs’ MIB to the 1350OMS-SDH’s DB.


xx Issue 01
Blank Page


xx Issue 01
2 NE isolation and recovery


xx Issue 01
NE isolation
From 1350OMS-SDH point of view, an NE becomes isolated because of:
case 1 – NE unreachable
1350OMS’s software problems: the EMLIM on the EML instance is stopped.
the access state is granted to the Craft Terminal.
DCN or NE problems.
case 2 – FEP down

1350OMS’s software problems: the FEP on the SDH instance is stopped.
1350OMS
Process Monitoring
SDH SDH
and Control
FEP
FEPs
EML
EMLIM EML
Emlims
NE
FEP: Front End Processor

EMLIM: EML Information Manager
“Unreachable” states:
Node’s attributes NE’s attributes

NE Communication Communication NE Communication
NA Reachability
Problems State reachability State
EMLIM stopped Unreachable NE unreachable Unreachable
Access granted to CT NE unreachable
DCN or NE problems NE unreachable Unreachable Unreachable Unreachable
FEP down Unreachable
NA: Network Adapter

“NA Reachability” specifies whether 1350OMS-SDH can communicate with EMLIM.
NE Communication Problems = NE unreachable: it is shown when a configuration of the NE (e.g.
Path creation, Path deimplementation,...) fails because the NE cannot be configured. For
example, when the EMLIM is stopped or the Craft Terminal has the access.
Communication State: it concerns the basic network reachability of the NE, that is the ping of the
NE from 1350OMS-EML is successful.
NE reachability: it concerns the communication between the EMLIM and the NE.

xx Issue 01
Case 1 – NE unreachable
An NE is unreachable as a consequence of:

1350OMS’s software problems: the EMLIM on the EML instance is stopped.
the access state is granted to the Craft Terminal.
DCN or NE problems.
When the Node is in Download Enabled and the NE is unreachable:

no information is exchanged between 1350OMS-SDH and the NE.
all the changes performed by the user are buffered in the 1350OMS’s DB.
the modified objects’ consistency status is set equal to “Not Aligned”.
i.e. by implementing a Path, the Path gets “Implemented”, but the NAP belonging to
the unreachable NE gets “Not Aligned”.
Recovery from isolation:

1350OMS-SDH carries out a slow polling on the “isolated” NE.
When an isolated NE comes reachable, the download is automatically started.
Any other further change requested by the user will be executed at the end
of the download procedure.


xx Issue 01
Case 1 – NE unreachable [cont.]
Stopping the EMLIM
NA Reachability =
Unreachable
NE Communication
Problems = NE
unreachable
EML Domain Alignment = Failed

Giving the access to the Craft Terminal
NE Communication
Problems = NE
unreachable
Local Access Control =

Granted
NA: Network Adapter

“NA Reachability” specifies whether 1350OMS-SDH can communicate with EMLIM.
NE Communication Problems = NE unreachable: it is shown when a configuration of the NE (e.g.

Path creation, Path deimplementation,...) fails because the NE cannot be configured. For
example, when the EMLIM is stopped or the Craft Terminal has the access.
In case of DCN or NE problems, the Node View issues:

NE Communication Problems = NE unreachable.
NE’s critical alarm because the supervision is lost.

xx Issue 01
Case 2 – FEP down
From 1350OMS-SDH point of view, an NE becomes isolated because of:

1350OMS’s software problems: the FEP on the 1350OMS-SDH is stopped.
even if the problem is at 1350OMS-SDH side, the relevant NEs are seen as “isolated”.
When the Node is in Download Enabled and the FEP is down:

all the NE configurations performed by the user fail.
the changes are not buffered anywhere.
e.g. the Path creation and allocation are successful; the Path implementation fails.
Recovery from isolation:

As the FEP gets operational and the NE reachable, the user must repeat the
operations that failed during the isolation.
i.e. the Path implementation.


xx Issue 01
Case 2 – FEP down [cont.]
NA Reachability
= Unreachable
EML Domain Alignment

= Failed

When the FEP is down:

the Path/Trail implementation fails. Path/Trail gets “Partially implemented”.
in the window “EML Domains” that opens by issuing “Search Physical EML Domains” all the
EMLIMs have the “NA Reachability” attribute equal to “Unreachable”.
the FEP processes are red in the “Process Monitoring and Control” window.

xx Issue 01
Exercise 1: EMLIM down
From PMC: stop the controller and an EMLIM.

From SDH: define, allocate and implement a Path involving at least one
NE managed by the stopped EMLIM.
Check the Path’s routing display.
From PMC restart the EMLIM.
Verify that the missing connections are automatically sent to the NEs
when they are reachable again.


xx Issue 01
Exercise 2: FEP down
From PMC: stop the controller and the FEP.

From SDH: define, allocate and implement a Path involving at least a
NE managed by the FEP.
Check the Path’s routing display.
Verify that the Path implementation fails.
Restart the controller and the FEP.
Verify that the missing connections are NOT sent automatically to the
NEs when they are reachable again (the Path is not implemented).
Implement again the Path.


xx Issue 01
Blank Page


xx Issue 01
End of Module


xx Issue 01
@@SECTI
Section 4
Appendix
Module 1
Routing Algorithm
xx Issue 03
1350OMS

xx Issue 03
Blank Page

Appendix Routing Algorithm
Document History

xx Issue 03
Module Objectives
be aware on how 1350OMS-SDH selects the route for a Path/Trail


xx Issue 03


xx Issue 03
Page
1 Introduction on Routing Algorithm 7

TableofContents
2 Costs
2.1 Physical Connection attributes for the Routing Algorithm
2.2 NPA and Path/Trail attributes for the Routing Algorithm
9
11
23
Switchtonotesview!
AppendixRoutingAlgorithm

xx Issue 03
Switchtonotesview!
AppendixRoutingAlgorithm

xx Issue 03
1 Introduction on Routing Algorithm


xx Issue 03
1 Introduction on Routing Algorithm
Criteria
Routing Algorithm takes into account the following rules ordered by

decreasing priority:
Constraints to be always satisfied:
NE constraints
Protection constraints (e.g. 2F MS-SPRing doesn’t allow time-slot interchange)
User defined constraints
Costs:
Physical Connection and NPA costs (see the following chapter)
First free time-slot:
This allows a more ordered usage of the time-slots. An exception to this rule are the
protecting fibers inside 4F MS-SPRing, where the allocation of time-slots starts from
the last free one.
Routing Algorithm takes into account not only the “Real” resources, but
also the “Potential” resources, such as Link Connections that can be
made available by modifying the actual payload configuration.

Real and Potential resources:

for a detailed description, see the “Network resources availability” module.
example: when allocating a 2Mb/s Path over a HO-Trail payloaded as (TU3,TU3,TU12), the
routing algorithm selects the potential TU12(1,1,1) even if the first TUG3 is structured as TU3
and not as TU12s. The later Path implementation will modify the payload into (TU12,TU3,TU12);
TU12(1,1,1) becomes real. That’s possible if the Dynamic Payload configuration is enabled (see
the “HO-Trail” module).

xx Issue 03
2 Costs


xx Issue 03
2 Costs
Attributes and cost computation
Routing Algorithm chooses the least cost route for Path/Trail
allocation.
The route cost computation is based on the costs of Physical
Connections and of NPAs. They depend on the following attributes.
The Attribute… …belongs to… …and impacts the…
Allocation Cost (AC) Physical Connection Physical Connection cost
Saturation Profile Physical Connection Physical Connection cost
Fragmentation Profile Physical Connection Physical Connection cost
NPA Usage Cost NPA NPA cost
NPA Reduction Cost Factor (RCF) NPA Physical Connection cost
NPA Main&Spare Factor path/trail NPA cost
MS-SPRing D&C Factor path/trail Physical Connection cost
PCbasic = AC*(1 + UsageExtraCost + FragmentationExtraCost)

PCtot = PCbasic*(1–NPA RCF)*(1-0.85*MS-SPRing D&C Factor)
NPAcost = NPA Usage Cost*(1-NPA Main&Spare Factor)
PCbasic: Physical Connection cost taking into account just the Physical Connection attributes.
PCtot is the total Physical Connection cost that is evaluated by means of PCbasic and the
Path/Trail/NPA attributes.
If the Path is going to use… (to simplify, NPA is not considered)

…a series of one-hop HO-Trails, the route cost is the sum of the single Physical Connections costs.
…a multi-hop HO-Trail, the route cost is evaluated by means of the following formula:
[max(Ci) + ΣCi]/2; where Ci is the PCtot of the Physical Connection “i”.
Should more than one Physical Connection – the rate doesn’t matter – with the same cost be
available, the one with the lowest Identifier is preferred.

xx Issue 03
2.1 Physical Connection attributes for
the Routing Algorithm


xx Issue 03
Physical Connection properties
Saturation Profile dependent Fragmentation Profile dependent

Physical Connection properties
Routing Administrative State:

if “Disabled”, the Physical Connection
is prevented from being used by the
Allocation Cost (AC): Routing Algorithm unless a user
defined constraint is used
0 - 100
Default
values

Both UsageExtraCost and FragmentationExtraCost contribute to the basic Physical Connection cost.
Onwards they are treated separately.

xx Issue 03
Saturation: Profiles and Usage Costs
Example for a Physical Connection whose bandwidth is used at 80%:
PCbasic = 20*(1+75%) = 20+15 = 35
Saturation Profile noExtraCost (default) predefinedExtraCost
mediumThreshold 75% 75%
highThreshold 88% 88%
lowUsageExtraCost 0% 0%
mediumUsageExtraCost 0% 75%
highUsageExtraCost 0% 175%
Medium High
Threshold Threshold
Physical
connection
cost Values of the
Medium Usage High Usage
Extra Cost “predefinedExtraCost”
Low Usage Extra Cost profile
Allocation Extra Cost 0% 75% 175%
cost
75% 88% 100% Used bandwidth

The FragmentationExtraCost provided by the fragmentation profile is supposed to be equal to 0.

The Routing Algorithm prevents the saturation of the available resources of a Physical Connection.
This is realized by increasing by “Usage Extra Cost” factors the cost of the Physical Connection
when its usage exceeds some predefined thresholds. Extra costs are defined in the “Saturation
Profile”.
Specifically, two thresholds are defined: Medium Threshold and High Threshold.
These two thresholds split the Physical Connection capacity into three bands: Low usage, Medium
Usage, High usage.
A specific “Usage Extra Cost” is then associated to each of these three bands:
low Usage Extra Cost
medium Usage Extra Cost
high usage Extra Cost
Two Saturation Profiles are automatically defined by the system:

“noExtraCost” (default): saturation is disregarded
“predefinedExtraCost”
The user can define additional Saturation Profiles to be applied to the desired Physical
Connections.

xx Issue 03
Saturation: Examples
By associating the predefinedExtraCost profile to the Physical

Connections of the network, the Routing Algorithm will route a new
Path/Trail as follows:
L
L L L L
1 2
M M M
M
M M M M
3 4
H H H
L
L L L L
5 6
H H
L = Low usage; M = Medium usage; H = High usage; Bold line = Chosen route
In the examples above:

the FragmentationExtraCost provided by the fragmentation profile is supposed to be equal to
0.
the default Allocation Cost (20) is used.
the predefinedExtraCost profile is used.
1. “M” cost = 20*(1+75%) = 20+15 = 35
“L” cost = 20 +20 = 40
“M” cost < “L” cost
2. “M” cost = 2*20*(1+75%) = 2*(20+15) = 70
“L” cost = 20 +20 +20 = 60
“M” cost > “L” cost
3. “H” cost = 20*(1+175%) = 20+35 = 55
“M” cost = 2*20*(1+75%) = 2*(20+15) = 70
“H” cost > “M” cost
4. “H” cost = 2*20*(1+175%) = 2*(20+35) = 110
“M” cost = 3*20*(1+75%) = 3*(20+15) = 105
“H” cost > “M” cost
5. “H” cost = 20*(1+175%) = 20+35 = 55
“L” cost = 20 +20 = 40
“H” cost > “L” cost
6. “H” cost = 20*(1+175%) = 20+35 = 55
“L” cost = 20 +20 +20 = 60
“H” cost < “L” cost
xx Issue 03
Saturation: Operation
1. Select: Actions OTN Create Saturation Profile
2. Set the
parameters
(Comment 1,
too) and then
do OK
3. To modify a created profile:

• Retrieve the list of the profiles:
Search OTN Saturation
Profiles
• “Modify” the profile

xx Issue 03
Saturation: Operation [cont.]
1. Two ways to assign a
Saturation Profile to a
Physical Connection…
2b. by issuing “Modify” for

an already created
Physical Connection (edit
the profile name)
2a. during the Physical

Connection creation

xx Issue 03
Fragmentation: introduction
A Physical Connection or a HO-Trail is said fragmented if the busy time-

slots are not rationally organized and impede the allocation of higher
order transports.
The Routing Algorithm chooses the best route for a Path/Trail avoiding
the fragmentation of the Trails/Physical Connections.
For example, two 2M Paths allocated over TU12s belonging to two different
TUG3s prevent the possibility to use the TUG3#2 as a TU3.
Fragmented allocation NOT Fragmented allocation
TUG3#1 TUG3#2 TUG3#3 TUG3#1 TUG3#2 TUG3#3
2M 2M 2M 2M
Free
TU3 for
then
34/45M
Path


xx Issue 03
Fragmentation: Profiles and Extra Costs
The Physical Connection basic cost is incremented by a percentage
(Fragmentation Extra Cost) to take into account the high rate
bandwidth that is becoming unusable.
The Fragmentation Extra Costs are defined in the Fragmentation

Profiles. Two of them are automatically defined by the system (the
user can create new ones):
noExtraCost: fragmentation is disregarded
predefinedExtraCost (default): fragmentation is considered
noExtraCost predefinedExtraCost
Fragmentation
Tu3 Extra Cost 0% 5%

Au4 Extra Cost 0% 5%
profile
Au4-4C Extra Cost 0% 5%

For example, an empty STM-1 is preferred to an empty STM-16 to
allocate a HO-Trail.

The following Fragmentation Extra Costs are taken into account. They are expressed in percentage
of the Allocation Cost.
tu3 Extra Cost: extra cost to use resources available for Tu3 paths.
Au4 Extra Cost: extra cost to use resources available for Au4 paths.
Au4-4C Extra Cost: extra cost to use resources available for Au4-4C paths.
tu3ExtraCost is taken into account for LO Path allocation.
For HO-Trail and HO-Path allocation…

…au4-4c, au4-16c, and au4-64c ExtraCosts are taken into account in case of STM-64.
…au4-4c, and au4-16c ExtraCosts are taken into account in case of STM-16.
…au4-4c ExtraCost is taken into account in case of STM-1.

xx Issue 03
Fragmentation: Example for STM-16 Physical Connection
#1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14 #15 #16 Cost

Case 1 22
Case 2 20
Case 3 21
Case 4 20
Busy AU4 Next AU4 that is likely to be used
the usage of AU4-4c on the first AU4 group and AU4-16c is PCbasic=
Case 1
prevented 20*(1+5%+5%)=22
the usage of AU4-4c on the first AU4 group and AU4-16c is
Case 2 PCbasic=20
already prevented by AU4#1
the usage of AU4-4c on the second AU4 group is prevented; PCbasic=
Case 3
AU4-16c is already prevented by the other AU4s 20*(1+5%)=21
the usage of AU4-4c on the first AU4 group and AU4-16c is
Case 4 PCbasic=20
already prevented by the other AU4s
In the example above:

the UsageExtraCost provided by the saturation profile is supposed to be equal to 0.
the default Allocation Cost (20) is used.
the predefinedExtraCost profile is used.
If an STM-16 Physical Connection is filled up by HO-Trails or HO Paths starting from AU4#1 up to

AU4#16, its cost is…
22 for AU4#1
21 for AU4#5, AU4#9, AU4#13
20 for (AU4#2,3,4) (AU4#6,7,8) (AU4#10,11,12) (AU4#14,15,16)
If an STM-4 Physical Connection is filled up by HO-Trails or HO-Paths starting from AU4#1 up to

AU4#4, its cost is…
21 for AU4#1
20 for AU4#2, AU4#3, AU4#4
For the LO-Path allocation just tu3ExtraCost is suitable.

xx Issue 03
Fragmentation: Operation
1. To create a Fragmentation Profile: Actions

OTN Create Fragmentation Profile
2. Set the parameters

(Comment 1, too)
and then do OK
To modify a created profile:

• Search OTN Fragmentation Profiles
• “Modify” the profile
To assign a profile to a Physical Connection:
• during the Physical Connection creation (select one from the list) or
• by “Modify” on an already created Physical Connection (edit the
profile name)

xx Issue 03
Enable/Disable the Pass-through in the Node
The user has the possibility to prevent the creation of pass-through

connections in a specific Node.
This is useful when the Node is a CPE, so it must be avoided to involve
it in the routing of Paths/Trails having end-points in other Nodes of the
network (see the figures in the notes as example).
Open the “Modify” window of the Node. By setting
to “False” the “PassThrough Enabled” attribute,
pass-through connections at LO and HO are
forbidden into the Node (default value is “True”)

CPE: Customer Premise Equipment
A
CPE2
Z
Protection
If in the CPE1 the pass-through is disabled,

CPE1 the routing algorithm doesn’t use the CPE1
for routing purpose even if the cost of the
route crossing the CPE1 is the lowest.
CPE2 A
Z
Protection
CPE1

xx Issue 03
Blank Page


xx Issue 03
2.2 NPA and Path/Trail attributes for
the Routing Algorithm


xx Issue 03
Attributes

NPA properties
Path/Trail
properties
Default
values

RCF: Reduction Cost Factor.

PCbasic: Physical Connection cost taking into account just the Physical Connection attributes.
PCtot: Physical Connection cost taking into account both the Physical Connection attributes and the
Path/Trail/NPA attributes.
NPAcost: NPA contribution to the route cost.

xx Issue 03
NPA route allocation rules: Rule#1
Stacked Rings require the Main route be routed in only one ring.
This is strongly required in case of 2F MS-SPRing (see next slide).
In case of SNCP rings there is no impact on reliability level, but the following
advantages are produced by applying the rule:
A well-ordered network
An easier algorithm for adding protection


xx Issue 03
NPA route allocation rules: Rule#1 [cont.]
2 x 2F MS-SPRing rings
DASHED path is
impacted when Node
2 fails.
In this case the path
is terminated in Node
2 and, in order to
avoid misconnections,
Node 2 each path’s section in
the two rings is
squelched (AIS is
transmitted over the
Node 1 path).
SOLID path is not impacted by Node 2 failure.

Node 3
This is because Node 2 is an intermediate Node
and the squelching mechanism is not initiated.

2F MS-SPRing: an AU4 is squelched when the destination node of the AU4 itself is not reachable.
In this example:
The dashed path crosses two rings and therefore uses two independent AU4 paths, one for each
ring. The two AU4 paths are terminated by Node 2 that is one of their source/destination nodes.
The solid path uses just one AU4 path in one ring. The source/destination nodes for this path are
Node 1 and Node 3. Node 2 is not the destination node and when it fails no squelch is initialized.

xx Issue 03
In stacked SNCP rings, the Spare routing should stay in the same ring
used by the Main one.
Applying this rule:
Encourages to avoid dangerous routing of the Spare (as it is shown in the
figure)
Keeps the network well-ordered
Allows 1350OMS-SDH to use an easier algorithm for adding protection
Dangerous routing: Ring#1: SNCP

If the Spare route is Ring#2: SNCP
allocated in a ring
Spare
different from the one
used for the Main route,
the two routes may have
the same points of failure
Main


xx Issue 03
When the Main branch of a HO-Trail uses a given 2F MS-SPRing ring, the
Spare branch should use the same ring and should be routed the more
overlapped as possible with the Main one, taking into account the
inherent MS-SPRing protection (instead of two separated routings in
different or in the same ring, as should be in classical SNCP).
The resulting configuration increases the resilience to external multiple

faults (see examples in the next slide).


xx Issue 03
NPA route allocation rules: Rule#3 [cont.]
2
With two
separated routings
in the same ring 2x
the trail is lost
with an external “2F MS-SPRing”
1
double fault (1+2)
By using the same

ring and by routing
1
the Spare the most
overlapped as
possible with the 2x
Main, the trail is 2
saved even with “2F MS-SPRing”
an external double Protected
fault (1+2) CxC
Main
Spare
The assertion “…the most overlapped as possible…” means that the Main and Spare try to share the
same AU4s where feasible.

xx Issue 03
Routing Algorithm attributes
The 1350OMS-SDH Routing Algorithm translates all the previously listed

rules into costs.
By increasing or decreasing the costs it’s possible to make a route more

attractive than others.
These costs need to be tuned and, for this reason, they are “driven” by
“attributes” whose values are modifiable by the user.
Attributes:
NPA Usage Cost (NPA Attribute)
NPA Reduction Cost Factor (NPA attribute)
NPA Main&Spare Factor (Path/Trail attribute)
MS-SPRing D&C Factor (Path/Trail attribute)

xx Issue 03
NPA Usage Cost
It is an extra cost to pay for the usage of a NPA. It has the target to
make costly to enter and to exit from a NPA.
The bigger this attribute is set, the more the routing inside a single NPA
will be preferred compared to a routing involving more than one NPA.
If set to 0, the routing is done not considering the NPA.
Its value can be set from 0 to 100. Default value is 20.


xx Issue 03
NPA Reduction Cost Factor
It is a NPA attribute that enables a percentage cost reduction for the

Physical Connections belonging to the NPA. This cost reduction has the
target to make more attractive the routing inside a NPA compared to an
external one.
It works together with the NPA Usage Cost making more attractive long
routes in a NPA.
The bigger it is set, the more the cost of NPA internal route is reduced.
It is a percentage value and can be set from 0% to 100%. Default value

is 20%.

xx Issue 03
Routing Computation: Example 1
“NPA Usage Cost” and “NPA Reduction Cost Factor” make the Routing
Algorithm apply the Rule#1, that is:
Stacked Rings require the main route to stay in the same ring.
Path 1 stays into Ring 1.
Path 2 (dotted)
Path 2 jumps from Ring 1 to Ring 2.
Outcome of the 2 3
Routing Algorithm: 4 Path 1 (solid)
Cost of Path 1 = 140
Cost of Path 2 = 144
1 6
5
7
8
NPA Usage Cost = 20

NPA Reduction Cost Factor = 20%
Allocation Cost = 20 Ring 2
Ring 1
It is supposed that the Fragmentation profile and the Saturation profile don’t contribute.
Thus PCbasic = Allocation Cost *(1 + UsageExtraCost + FragmentationExtraCost) = Allocation Cost =
20 [default]
The Path route computation is based on the following calculations:
Cost of Path 1 = Cost of Physical Connection (1,2,3,4,6,7,8) + Ring 1 NPA Usage Cost
Cost of Physical Connection (1,8) = 20

Cost of Physical Connection (2,3,4,6,7) = 20*(1 - NPA Reduction Cost Factor) = 20*(1-0.2) = 16
Ring 1 NPA Usage Cost = 20
Cost of Path 1 = 2*20 + 5*16 + 20 = 140
Cost of Path 2 = Cost of Physical Connection (1,2,3,4,5,8) + Ring 1 NPA Usage Cost + Ring 2 NPA
Usage Cost

Cost of Physical Connection (2,3,4,5) = 20*(1 - NPA Reduction Cost Factor) = 20*(1-0.2) = 16
Ring 1 NPA Usage Cost = Ring 2 NPA Usage Cost = 20
Cost of Path 2 = 2*20 + 4*16 + 2*20 = 144

xx Issue 03
NPA Main & Spare Factor
During the Spare route calculation, the “NPA Usage Cost” is reduced by
this factor.
It indicates how strongly Main & Spare have to be forced to use the
same NPA.
The bigger it is set the more the cost of the routes internal to the NPA
used by the Main is decreased, so attracting the Spare.
It makes the Routing Algorithm to apply Rule#2 and part of the Rule#3,
that is: in SNCP and 2F MS-SPRing stacked rings, the Spare routing
should stay in the same ring as the Main one.

is 100%. PCtot = PCbasic*(1–NPA RCF)*(1-0.85*MS-SPRing D&C Factor)

xx Issue 03
“NPA Main & Spare Factor” makes the Routing Algorithm apply the
Rule#2 and part of the Rule#3, that is:
in SNCP and 2F MS-SPRings stacked rings, the spare routing should stay in the
same ring as the main.
The “Spare 1” path stays into the same NPA (Ring1) used by the Main Main
The “Spare 2” path uses the NPA (Ring 2) not used by the Main Spare 1
Outcome of the Spare 2
Routing Algorithm:
Cost of Spare 1 = 72
Cost of Spare 2 = 92
1
6
NPA Usage Cost = 20 4 5
NPA Reduction Cost Factor = 20% Ring 2
Allocation Cost = 20
NPA Main&Spare Factor = 100% 2 3 Ring 1
Thus PCbasic = Allocation Cost *(1 + UsageExtraCost + FragmentationExtraCost)= Allocation Cost =
20 [default]
The Path route computation is based on the following calculations:
Cost of “Spare 1” path = Cost of Physical Connection (1,2,3,6)+ Ring 1 NPA Usage Cost

Cost of Physical Connection (2,3) = 20 * (1 - NPA Reduction Cost Factor) = 20*(1-0.2) = 16
Ring 1 NPA Usage Cost = 20*(1 - NPA Main&Spare Factor) = 20*(1-1) = 0
Cost of “Spare 1” path = 2*20 + 2*16 + 0 = 72
Cost of “Spare 2” path = Cost of Physical Connection (1,4,5,6) + Ring 2 NPA Usage Cost

Cost of Physical Connection (4,5) = 20*(1 - NPA Reduction Cost Factor) = 20*(1-0.2) = 16
Ring 2 NPA Usage Cost = 20
Cost of “Spare 2” path = 2*20 + 2*16 + 20 = 92

xx Issue 03
MS-SPRing D&C Factor
Meaningful for SNCP or D&C SNCP trails traversing MS-SPRing.
It is used to encourage the routing of the Spare to be the most

overlapped as possible with the Main inside MS-SPRing.
If the Spare goes on the Physical Connection in the same direction as

the Main, the Physical Connection cost is decreased by 0.85*MS-SPRing
D&C Factor.
The Physical Connection cost where the Spare overlaps the Main is
reduced to zero.

is 80%.

xx Issue 03
MS-SPRing D&C Factor makes the Routing Algorithm apply the Rule#3:
When the Main branch of a trail uses a given 2F MS-SPRing, the Spare should
use the same ring and should be routed as more overlapped as possible with
the Main, taking into account the inherent 2F MS-SPRing protection.
- The “Spare 1” trail is the more overlapped as possible with the Main
main and makes use of the MS-SPRing protection on Ring 1 NPA. Spare 1
- The “Spare 2” stays completely separated from the Main. Spare 2
Outcome of the 5 6 7
Routing Algorithm: Ring 1
Cost of Spare 1 = 55.36 Ring 2
Cost of Spare 2 = 72 8
4
NPA Usage Cost = 20 10
1 9
NPA Reduction Cost Factor = 20%
Allocation Cost = 20
NPA Main&Spare Factor = 100% 2 3 Protected
MS-SPRing D&C Factor = 80% CxC

Thus PCbasic = Allocation Cost *(1 + UsageExtraCost + FragmentationExtraCost)= Allocation Cost = 20
[default]
The Path route is computed by 1350OMS-SDH based on the following calculations:
Cost of the “Spare 1” trail = Cost of Physical Connection (1,4,5,6,7,8,9,10)+ Ring 1 NPA Usage Cost

Cost of Physical Connection (4,8,9) = 20 * (1 - Reduction Cost Factor)*(1-0.85*0.8) = 20*(1-
0.2)*0.32 = 5.12
Cost of Physical Connection (5,6,7) = 0
Ring1 NPA Usage Cost = 20 * (1 - NPA Main&Spare Factor) = 20*(1-1) = 0
Cost of the “Spare 1” trail = 2*20 + 3*5.12 = 55.36
Cost of the “Spare 2” trail = Cost of Physical Connection (1,2,3,10) + Ring 1 NPA Usage Cost

Cost of Physical Connection (2,3) = 20 * (1 - NPA Reduction Cost Factor) = 20*(1-0.2) = 16
Ring1 NPA Usage Cost = 20 * (1 - NPA Main&Spare Factor) = 20*(1-1) = 0
Cost of the “Spare 2” trail = 2*20 + 2*16 = 72

xx Issue 03
Exercise: Routing cost computation
In the network drawn below, calculate the routing cost of the trails:
Main
Spare a NPA Usage Cost = 20
Spare b NPA Reduction Cost Factor = 20%
Physical Link Cost = 20
NPA Main&Spare Factor = 100%
MS-SPRing D&C Factor = 80%
Main
Ring 1 Ring 2 Spare a

(2F MS-SPRing) (2F MS-SPRing) Spare b


xx Issue 03
Blank Page


xx Issue 03
End of Module
Routing Algorithm


xx Issue 03
Last But One Page

@@PRODUCT
@@COURSENAME

@@COURSENAME - Page 1
Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent
@@COURSENAME - Page 2

1350 Oms SDH R 9.1.1 MNT4 - Top63052 - V1.0

Uploaded by

Copyright:

Available Formats

1350 Oms SDH R 9.1.1 MNT4 - Top63052 - V1.0

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1350 Oms SDH R 9.1.1 MNT4 - Top63052 - V1.0

Uploaded by

Copyright:

Available Formats

1350OMS

1350OMS-SDH R 9.1.1 MNT4

All Rights Reserved © Alcatel-Lucent @@YEAR

All rights reserved © Alcatel-Lucent @@YEAR

All Rights Reserved © Alcatel-Lucent @@YEAR

Switch to notes view!

2 All Rights Reserved © Alcatel-Lucent @@YEAR

All Rights Reserved © Alcatel-Lucent @@YEAR

All rights reserved © Alcatel-Lucent @@YEAR

All Rights Reserved © Alcatel-Lucent @@YEAR

Switch to notes view!

4 All Rights Reserved © Alcatel-Lucent @@YEAR

All Rights Reserved © Alcatel-Lucent @@YEAR

1350OMS-SDH R 9.1.1 MNT4 Operation

All Rights Reserved © Alcatel-Lucent @@YEAR

Switch to notes view!

6 All Rights Reserved © Alcatel-Lucent @@YEAR

All Rights Reserved © Alcatel-Lucent @@YEAR

Switch to notes view!

Welcome to 1350OMS-SDH R 9.1.1 MNT4 Operation

Upon completion of this course, you should be able to:

manage a network using 1350OMS SDH

7 All Rights Reserved © Alcatel-Lucent @@YEAR

All Rights Reserved © Alcatel-Lucent @@YEAR

Switch to notes view!

8 All Rights Reserved © Alcatel-Lucent @@YEAR

All Rights Reserved © Alcatel-Lucent @@YEAR

9 All Rights Reserved © Alcatel-Lucent @@YEAR

Where you can get further information

If you want further information you can refer to the following:

All Rights Reserved © Alcatel-Lucent @@YEAR

Switch to notes view!

10 All Rights Reserved © Alcatel-Lucent @@YEAR

All Rights Reserved © Alcatel-Lucent @@YEAR

Did you meet the following objectives ?

All Rights Reserved © Alcatel-Lucent @@YEAR

modify the 1350OMS-SDH objects

Thank you for your answers to this questionnaire

All Rights Reserved © Alcatel-Lucent @@YEAR

All Rights Reserved © Alcatel-Lucent @@YEAR

112 All Rights Reserved © Alcatel-Lucent @@YEAR

Edition Date Author Remarks

01 2011-04-29 Pirola Paolo

All Rights Reserved © Alcatel-Lucent @@YEAR

Upon completion of this module, you should be able to:

Describe the composition of 1350OMS

113 All Rights Reserved © Alcatel-Lucent @@YEAR

All Rights Reserved © Alcatel-Lucent @@YEAR

114 All Rights Reserved © Alcatel-Lucent @@YEAR

All Rights Reserved © Alcatel-Lucent @@YEAR

1 1350OMS product and its applications 7

All Rights Reserved © Alcatel-Lucent @@YEAR

All Rights Reserved © Alcatel-Lucent @@YEAR

117 All Rights Reserved © Alcatel-Lucent @@YEAR

All Rights Reserved © Alcatel-Lucent @@YEAR

A Telecommunication Management Network (TMN) is a structured

118 All Rights Reserved © Alcatel-Lucent @@YEAR

All Rights Reserved © Alcatel-Lucent @@YEAR

112 All Rights Reserved © Alcatel-Lucent @@YEAR

113 All Rights Reserved © Alcatel-Lucent @@YEAR

114 All Rights Reserved © Alcatel-Lucent @@YEAR

117 All Rights Reserved © Alcatel-Lucent @@YEAR

118 All Rights Reserved © Alcatel-Lucent @@YEAR

119 All Rights Reserved © Alcatel-Lucent @@YEAR

1 1 10 All Rights Reserved © Alcatel-Lucent @@YEAR

1 1 11 All Rights Reserved © Alcatel-Lucent @@YEAR

1 1 12 All Rights Reserved © Alcatel-Lucent @@YEAR

1 1 15 All Rights Reserved © Alcatel-Lucent @@YEAR

1 1 16 All Rights Reserved © Alcatel-Lucent @@YEAR

1 1 22 All Rights Reserved © Alcatel-Lucent @@YEAR

1 1 24 All Rights Reserved © Alcatel-Lucent @@YEAR

1 1 25 All Rights Reserved © Alcatel-Lucent @@YEAR

1 1 26 All Rights Reserved © Alcatel-Lucent @@YEAR

1 1 27 All Rights Reserved © Alcatel-Lucent @@YEAR

1 1 28 All Rights Reserved © Alcatel-Lucent @@YEAR

212 All Rights Reserved © Alcatel-Lucent @@YEAR