1850 TSS 320 1850 TSS 160 R 4 1 Ce

1850 TSS-320 & 1850 TSS-160
1850 TSS-320 & 1850 TSS-160 R

4.1 O&M
TOP63058_V2.0-SG-R4.1 Issue 01
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

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M - Page 1
Empty page
Switch to notes view!
2 All Rights Reserved © Alcatel-Lucent @@YEAR

1850 TSS-320 & 1850 TSS-160
1850 TSS-320 & 1850 TSS-160 R 4.1 O&M
This page is left blank intentionally

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M - Page 2
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
1850 TSS-320 & 1850 TSS-160
1850 TSS-320 & 1850 TSS-160 R 4.1 O&M
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.

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M - Page 3
Blank Page

1850 TSS-320 & 1850 TSS-160
1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M - Page 4
Course Outline
Section
About This1.Course
Product Overview
4. Topic/Section is Positioned Here
Module 1. Introduction
Course outline
Technical support
Module 2. Architecture 5. Topic/Section is Positioned Here
Course objectives
Section 2. Functional Description
Moduleis1.Positioned
1. Topic/Section Hardware Description-Common
Here 6. Topic/Section is Positioned Here
Xxx Module 2. Hardware Description-SDH
Xxx Module 3. Hardware Description-CWDM 7.FOADM
Topic/Section is Positioned Here
Optical amplifiers
Xxx
Module 4. Hardware Description-Data
Module 5. Hardware Description-1662 Drop Shelf
Section 3. NE Operation
Module 1. Operator Interface-NE
Module 2. Operator Interface-SDH WDM features
Module 3. Operator Interface-Ethernet Bridge features
Module 4. Operator Interface-T-MPLS & MPLS-TP features
Module 5. Operator Interface-ATM features
Module 6. Operator Interface-CES features
Module 7. Alarm Management
Module 8. Monitoring
5 Section 4. Maintenance
1850 TSS-320 & 1850 TSS-160
1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

Module 1. Backup & Restore
Module 2. Software Download
Module 3. User Management
Module 4. EC substitution

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M - Page 5
Course Outline [cont.]

1850 TSS-320 & 1850 TSS-160
1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M - Page 6
Course Objectives
Welcome to 1850 TSS-320 & 1850 TSS-160 R 4.1 O&M
Upon completion of this course, you should be able to:
Operate the 1850 TSS-320 and/or 1850 TSS-160 by means of Craft Terminal

1850 TSS-320 & 1850 TSS-160
1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M - Page 7
Blank Page

1850 TSS-320 & 1850 TSS-160
1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M - Page 8
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

1850 TSS-320 & 1850 TSS-160
1850 TSS-320 & 1850 TSS-160 R 4.1 O&M
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

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M - Page 9
About this Student Guide [cont.]

1850 TSS-320 & 1850 TSS-160
1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M - Page 10
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 Comments
globally no)
yes)
1 Describe the basic concept of 1850TSS
Family
Describe the basic concept of 1850TSS320/160
2 Describe the insertion of the equipment in the network
Describe the SDH and Data networks configuration
Describe the switching capacity sub-systems
11 3 Describe the common HW parts of theAll1850TSS-320
Rights Reserved © Alcatel-Lucent @@YEAR
and
1850 TSS-320 & 1850 TSS-160
1850TSS-160
1850 TSS-320 & 1850 TSS-160 R 4.1 O&M
4 Describe the SDH boards of the 1850TSS-320 /160
5 Describe the DWDM and CWDM boards of the 1850TSS-320/160
6 Describe the Data boards of the 1850TSS-320 and 1850TSS-160
7 Describe how to configure the NE with CT port

Describe how to log on the NE
Describe how to configure the Communication parameters
Explain how to configure ALS, J0, TP threshold, Restart NE and
Alarm LIst
Describe how to configure subrack & boards
Describe how to configure and manage the Equipment
Protections
8 Explain how to create cross connections & protected cross
connections
Describe the APS protection
Explain how to Manage the loopbacks
Explain how to perform the NE synchronization

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M - Page 11
Self-assessment of Objectives [cont.]
Yes (or No (or

Switch to notes Instructional
view! objectives globally globally Comments
yes) no)
9 Create point-to-point Ethernet services
Create Flow based CXC
Create virtual and provider bridge services
Implement the Link Aggregation on the Ethernet Port
Configure and understand x-STP protocol
Manage OAM functionality
Implement the In Band management for remote NE
supervision
Configure LPT functionality
Configure AIS Ethernet functionality
Configure Delay Measurement and Synthetic Loss
Measurement
Configure Ethernet Loopback
Configure the transparent clock
10 Create a T-MPLS Ethernet Virtual Private Line service
Create a T-MPLS Virtual Private LAN Service
Manage the Quality of Service in for the T-MPLS network
Configure a T-MPLS tunnel 1:1 protection
Configure T-MPLS / MPLS TP OAM
Configure MAC Flushing propagation
11 Create ATM to ATM CXC
Configure the ATM Cell Concatenation
Create ATM over PW CXC
12 Describe how to handle the AS application for current
alarms
1850 TSS-320 & 1850 TSS-160
13 Describe the theory of Performance Monitoring
1850 TSS-320 & 1850 TSS-160 R 4.1 O&M
Explain the Performance Monitoring Operation
14 Explain to create a backup of the NE database

Describe the restore on available backup
15 Describe the NE software download
16 Describe how to change the user password

Describe how to create and delete user
Describe how to define and assign user privileges
(permission)
Describe how to configure the security parameters
17 Substitute the EC320 board
Other comments
Thank you for your answers to this questionnaire


1850 TSS-320 & 1850 TSS-160 R 4.1 O&M - Page 12
Do not delete this graphic elements in here:
11
Section 1
Product Overview
Module 1
Introduction
Issue 01
1850 TSS-320 & 1850 TSS-160

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

Issue 01
Section 1 Module 1 Page 1
Blank Page

Product Overview Introduction
1850 TSS-320 & 1850 TSS-160 1850 TSS-320 & 1850 TSS-160 R 4.1 O&M
Document History
Edition Date Author Remarks
01 2011-12-15 Grecchi Ilario

Issue 01
Objectives
Describe the basic concept of 1850TSS family

Describe the basic concept of 1850TSS-320/160


Issue 01
Blank Page


Issue 01
Table of Contents
Switch to notes view! Page
1 Introduction 7


Issue 01
Blank Page


Issue 01
1 Introduction


Issue 01
1 Introduction
4G equipment
The Alcatel-Lucent 1850 Transport Service Switch (TSS) is a new class of

multiservice transport platform that supports any mix of traffic, from
all-circuit to all-packet, with carrier class levels of reliability and fault
tolerance.
Their unique Universal Matrix switches packets or circuits in their
native format seamlessly; it is able to integrate several network
(matrix) layers (i.e. from ODU to SDH to packets) into a single chip.
Thus businesses can begin with circuit-based transport and, over time,
gradually ramp up packet transport with only simple changes of line
cards. Hence the 1850 TSS supports current traffic requirements while
eliminating the scalability issues encountered when traditional
multiservice provisioning platforms are confronted with packet-based
traffic increases.


Issue 01
1 Introduction
4G equipment [cont.]
The 1850 TSS offers the flexibility to split increasing traffic demands
among any combination of carrier Ethernet switching, WDM, optical
data unit (ODU), ATM and TDM transport technologies, using a simple
point-and-click interface. It offers a powerful cross-layer network
management and a unified control plane that simplify operations and
reduce the total cost of ownership.
This solution is made possible by the following key architectural
concepts, which enable the signal processing associated with different
network layers to be distributed among different boards:
Payload matrix or matrices do not perform traffic processing, only cross
connection
Traffic processing inside a layer is performed on Port Cards specific to that
layer and directly connected to the portion of the Universal Matrix belonging
to the layer
Optional Adapter Cards or Modules are used to interconnect different layers
(matrices) either integrated or external to the Universal Matrix. These cards
are equipped with the termination and adaptation functions required by a
layered approach.


Issue 01
1 Introduction
Main benefits of cost-effectiveness and scalability of the 1850 TSS-320

and 160:
packets and circuits are switched in their native formats, in any combination
system complexity is handled by the port cards (working inside a layer) and
the adapter cards or modules (working between different layers)
system capacity is directly proportional to the port cards and adapter cards
actually equipped
allows easy progression from 100% circuit to 100% packet and any ratio in
between
the overall matrix capacity is shared among different layers and the amount
of bandwidth per layer is dynamically changed on "slot" basis
the Optical Packet Transport fulfils the roles of the traditional multiservice
provisioning platform/multiservice transport platform (MSPP/MSTP) up to full
Packet Transport Node (PTN), plus aggregation, grooming and metro & long-
haul WDM and 8-degrees ROADM capabilities (not supported in this rel,
already available in rel. 2.0).
1 1 10 All Rights Reserved © Alcatel-Lucent @@YEAR


Issue 01
1 Introduction
ATM, , ATM


Issue 01
1 Introduction


Issue 01
1 Introduction
A smooth evolution from a legacy transport network (mainly based on

Sonet/SDH and PDH) towards an integrated network solution coping
with optical, TDM and Data services calls for platforms capable to
manage several technologies at the same time.
Alcatel-Lucent devised the 4G equipment to meet the convergence
issue.
1850 TSS-5C
1850 TSS-5R
1850 TSS-10
1850 TSS-100/100C
1850 TSS-160
1850 TSS-320
Switching capacity in Gbps

Transport Service Switch

Issue 01
1 Introduction
Alcatel-Lucent Optics Portfolio
Multiservice Transport Service Switches Cross-Connects Photonics 1626
LM
Provisioning Platforms 1850
TSS-320/160
1696
1660 TSS-100 MS
λ @ 10/40G SM
Lambda 1692
Unite MSE
WDM λ @ 10G 1678
MCC
λ @ 2.5G
TSS-10
STM-256 (40G) 1662
SMC
TSS-5
1642 1643
STM-64 (10G) EM AM/S 1650
EMC AMC SMC
STM-16 (2.5G)
SDH STM-4
STM-1
PDH
SAN
10GE
GE
DATA
E/FE
MPLS/T-MPLS
ATM
SHDSL

The picture shows the Alcatel-Lucent Optics Portfolio of network elements (NE)
Multiservice Provisioning Platforms (MSPP)
1642 EM/C
1643 AM/S, AMC
1650 SMC
1662 SMC
1660 SM
Transport Service Switches (TSS)

1850 TSS-5C
1850 TSS-5R
1850 TSS 10
1850 TSS-100/100C
1850 TSS-160/320
Cross Connects
Lambda Unite
1678 MCC
Photonics (WDM: Wavelength Division Multiplexer)

1692 MSE: Metro Span Edge
1696 MS: Metro Span
1626 LM: Light Manager
Issue 01
1 Introduction
1850TSS-320 vs 1850TSS-160
Main differences between the two equipments are:
TSS-320 provides double traffic slots (32 slots) with respect the TSS-160 (16
slots)
TSS-160 does not support CWDM.
TSS-320 provides double switch capacity respect to TSS-160
The TSS-320 matrix is able to provide:
320G (2048 VC4 equivalent) of multiservice (TDM, packets) multi-rate cross-
connect capability, by means of the higher order matrix
40G (16128 VC12 equivalent) of TDM cross-connect capability, in the lower
order matrix, by means of up to six 10G LOA adapters (two groups 1:2
protected).
The TSS-160 matrix is able to provide:
160G (1024 VC4 equivalent) of multi-service (TDM, packets) multi-rate cross-
connect capability, by means of the higher order matrix
20G (8064 VC12 equivalent) of TDM cross-connect capability, in the lower
order matrix, by means of up to three 10G LOA adapters (1:2 protected)
In the note area, are included two tables concerning to the switching
capacity

Because switching time is the same for HO SDH/SONET, OTN and packet based traffic, the values in the
table refer to the maximum switching capacity that can be obtained with no technology mixing.
For LO SDH/SONET, LO switching is performed in a dedicated device. In this case, the management of
OTN traffic and/or packets in the same equipment has no impact on the LO switching capacity.

Issue 01
1 Introduction
1850TSS-320 vs 1850TSS-160


Issue 01
1 Introduction
Advantage of 1850TSS-320/160
By combining multiservice data switching and aggregation capabilities

in one NE, 1850TSS-320/160 allows network operators to easily
increment functionality and performances of their network leveraging
on current infrastructures.
Optical Packet Backbone Optical Packet Backbone

Triple play: voice, data, video

Issue 01
End of Module
Introduction


Issue 01
12
Section 1
Product Overview
Module 2
Architecture
Issue 01
1850 TSS-320 & 1850 TSS-160

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

Issue 01
Blank Page

Product Overview Architecture
Document History

Issue 01
Objectives
Describe the insertion of the equipment in the network

Describe the SDH, WDM and Data networks configuration
Describe the switching capacity sub-systems


Issue 01
Blank Page


Issue 01
Table of Contents
Page
1 Insertion of the equipment in the network 7
2 SDH network implementation 9
3 WDM network implementation 11
4 Data network implementation 23
5 Controller Sub-system 57
6 Protection Sub-system 61
7 Synchronization architecture 81
8 Power distribution architecture 93
9 Network Management 101


Issue 01
Blank Page


Issue 01
1 Insertion of the equipment in the
network


Issue 01
1 Insertion of the equipment in the network
Application of 1850TSS-320/160
The 1850TSS-320/160 can be utilized in metropolitan networks

configured for SDH, WDM and Data

1850TSS-320/160 can be suitably employed on linear, ring and meshed networks with protected or
unprotected line links

Issue 01
2 SDH and PDH network implementation


Issue 01
2 SDH and PDH network implementation
Example of network topologies
Client Signals
1850TSS-320
LINEAR
STM-N
Client Signals 1850TSS-320 RING 1850TSS-320 1850TSS-320 1850TSS-320
STM-1 STM-1
Client Signals Client Signals
1850TSS-320
STM-N
POINT 1850TSS-320
STM-N STM-N
TO POINT
STM-N
Client Signals 1850TSS-320 1850TSS-320 1850TSS-320 Client Signals
STM-N MESHED
STM-N 1850TSS-320 STM-N
Client Signals

The 1850 TSS supports linear, ring and hub networks and on protected or unprotected line links.

Issue 01
3 WDM network implementation


Issue 01
Introduction
Both CWDM and DWDM technologies are supported by WDM systems. In

the following pages, these different types of technologies will be
described.

The CWDM system supports the 8possible channels according to the ITU-T G.694.2 Rec. The operating
wavelength is determined by the CWDM SFP module, plugged on line side. Eight different CWDM SFP
are available, to cover the 8 CWDM wavelengths of the C-band. The table gives the nominal
frequencies allocation plan, based on the 20 nm wavelength grid.
TDM and DATA boards (STM64 and 10GE, respectively) can be equipped with CWDM SFPs.

Issue 01
Section 1 - Module 2 - Page 12
Introduction [cont.]

The DWDM system is based on the 100 GHz channel spacing in the C-band, according to the ITU-T G.694.1
Rec. In current release, the 16 channels of the L1 and L2 bands are supported. The optical spectrum is
shown in the Table. It is anchored to the 193.1 THz reference.
The operating wavelength is determined by the DWDM XFP module. 16 different DWDM XFP are available
in current release, to cover the 16 DWDM wavelengths.

Issue 01
CWDM Configurations
Line Terminal (LT)

Optical Add and Drop Multiplexer (OADM)

TRIB stands for tributary board and indicates an optical channel. This functionality can be provided by
CWLA3 board, each one equipping two CWDM optical channels/transponders
SDH/DATA units equipped with multirate CWDM SFPs, each one providing a colored wavelength in
the C-band (they don't belong to the WDM system). These units provide CWDM wavelengths with 100
Mbps to 10 Gbps bit rate range. Moreover, the transponders perform an Optical-Electrical Optical
conversion and they are optically connected to both the client and the mux/demux;
CMDX stands for Channel Mux/DemuX. It supports CWDM applications and it is used in Line Terminal
configurations. 1 channel, 2 channel and 8 channel mux/demux are available•
CADM stands for Channel Add/Drop Multiplexer. It supports CWDM applications and it is used in OADM
configurations. 1 channel, 2 channel and 4 channel OADM are available.
Multi-rate client signals: the system can be equipped with multi rate transponders (TPD), which support
client signals from 100 Mbps to 2.67Gbps.
Optical interfaces: SFP (up to 2.67Gbps) and XFP (10Gbps)
Unidirectional transmission on a single fiber: it means that all the channels/wavelengths are transmitted
in one direction (one fiber for direction).

Issue 01
CWDM Line Terminal (LT)
In Line Terminal configuration, the equipment connects up to

8 CWDM tributary optical signals (100 Mbps to 10 Gbps) to an optical fiber
WDM line.
In Line Terminal configuration, the equipment takes places at both
ends of point to point links.
It is made up of
CWDM transponders and/or SDH, DATA boards (TRIB), providing the optical
channels (wavelengths)
A CMDX-n (n channel mux/demux with n=1,2 or 8).

The equipment takes place at both ends of the point-to-point link.

Issue 01
CWDM Optical Add and Drop Multiplexer (OADM)
Out of the n channels of the line, x channels are added/dropped and n-

x channels (express channels) are put in pass-through.
The OADM is made up of:
CWDM transponders and/or SDH, DATA boards (TRIB), providing the optical
One CADM board (equipped with two mux/demux, one per direction).

The OADM takes place as linear add/drop multiplexer in point-to-point links and ring networks. This
configuration allows the Sub-Network Connection Protection (SNCP) of the added/dropped channels.
The Optical Add and Drop Multiplexer is able to add and drop a part of the traffic (wavelengths)
to/from the WDM aggregate signal, in both directions (East/West). It is based on a mux/demux pair
in back-to-back configuration.
In CWDM applications, 1/2/4 channels/wavelengths can be added and dropped by each OADM board
(CADM).
All the channels that are not extracted are in pass-through, without any regeneration (express
channels).
If n is the number of WDM channels (line signal) and x the added/dropped channels, n-x is the
number of the channels in pass-through (express channels).
The OADM takes place as linear add and drop multiplexer in point to point links and ring networks.

Issue 01
Fixed DWDM (FOADM) configurations
The FOADM system of the 1850 TSS, allows the following basic
configurations:
Line Terminal (LT)
In Line Amplifier (ILA).
FOADM operates on a 100 GHz grid.

In the following figures:

TRIB stands for tributary board and indicates an optical channel. This functionality can be provided by
DWLA 10X unit; it is a 1 channel DWDM transponder
SDH/DATA units equipped with DWDM XFPs, each one providing a colored wavelength in the C-band
(they don't be long to the WDM system)
These units provide DWDM wavelengths at 10Gbps.
Moreover, the transponders perform an Optical Electrical Optical conversion and they are optically
connected to both the client and the mux/demux;
OMDX stands for Optical Mux/Demux supporting the 100 GHz grid. Each OMDX supports 8 wavelengths
multiplexing and demultiplexing. It is used in Line Terminal and OADM configurations. In current
release, the 8 channel muxes/demuxes in L1 and L2 bands are available, allowing the equipment to
mux/demux up to 16 channels/wavelengths, via mux cascading

Issue 01
DWDM Line Terminal (LT)
Line Terminal
In Line Terminal configuration
The 1850 TSS320 connects up to 16 DWDM tributary optical signals at 10 Gbps
to an optical fiber WDM line.
The 1850 TSS160 connects up to 12 DWDM tributary optical signals at 10 Gbps
(only 12 units can be hosted, because of it has less room than TSS320) to an
optical fiber WDM line.
In Line Terminal configuration, the equipment takes places at both
ends of point to point links. It is made up of
DWDM transponders and/or SDH, DATA boards (TRIB), providing the optical
One or two OMDX 8100 (8 channel mux/demux): one board is required for the
8 channel configuration, two boards are required for the 16 channel
configuration
One line amplifier (LOFA, optional unit).


Issue 01
DWDM Line Terminal (LT) [cont.]


Issue 01
The Optical Add and Drop Multiplexer is able to add and drop a part of
the traffic (wavelengths) to/from the WDM aggregate signal, in both
directions (East/West). It is based on one (or two) mux/demux pair in
back to back configuration.
In the TSS-320 aIl the 16 channels of the L1 and L2 bands, can be added
and dropped by the OMDX units.
In the TSS-160 (having half room than TSS-320):
In case of two OMDX are equipped (L1 or L2) up to 6 channels can be added
and dropped for direction
In case of four OMDX are equipped (L1 and L2) up to 4 channels can be added
and dropped for direction.
All the channels that are not extracted are in pass-through, without any
regeneration (express channels).
The OADM is made up of:
DWDM transponders and/or SDH, DATA boards (TRIB), providing the optical
Two or four OMDX 8100 boards (8 channel mux/demux): one board for
direction in 8 channel configuration, two boards for direction in 16 channel
configuration.
The OADM takes place as linear add and drop multiplexer in point to point links and ring networks.
If n is the number of WDM channels (line signal) and x the added/dropped channels, n-x is the number of
the channels in pass-through (express channels).

Issue 01
Optical Add and Drop Multiplexer (OADM) [cont.]
OADM configuration in FOADM systems


Issue 01
In Line Amplifier (ILA)
In Line Amplifier (ILA)

In Line Amplifier (ILA) is a WDM amplifier, without transponders and
Mux/Demux.
It consists of optical double stage in–line amplifiers (LOFA) providing a
bidirectional wide band amplification in order to boost the optical
power of the aggregate DWDM signal, avoiding any optical to electrical
conversion.
ILA configuration in Fixed DWDM (FOADM) systems

LOFA stands for Line Optical Fiber Amplifier. It is a C-Band, dual stage, EDFA (Erbium Doped Fiber
Amplifier) aggregate amplifier, providing +17 dBm output power and +12 dBm first stage output power.
It is used in vertical/bidirectional configuration. A floating VOA is available on the front panel.

Issue 01
4 Data network implementation


Issue 01
Introduction
The 1850 TSS-320/160 DATA system is designed for METRO and

Backbone networks applications with integrated Optical Transport
(xWDM, OTH, SONET/SDH).
The maximum throughput for data packets is:
as regard 1850 TSS-320: 320 Gbps for a mixed Data/SONET/SDH/WDM
configuration, as a maximum of 16 data boards each with maximum access
capacity up to 20Gbps can be equipped. This means a local connectivity
capacity of maximum 320 GE or 32 x 10GE interfaces
as regard 1850 TSS-160: 160 Gbps for a mixed Data/SONET/SDH/WDM
configuration, as a maximum of 8 data boards each with maximum access
capacity of 20Gbps can be equipped. This means a local connectivity capacity
of maximum 160 GE or 16 x 10GE interfaces.


Issue 01
The data packets are cross-connected by the Universal Matrix of the
equipment to Local and Remote Ports.
The local Ethernet interfaces operate at 100 Mbps (el. And opt.), 1
Gbps (el. and opt.) and 10 Gbps Optical rates.
Data units are listed in the following:
10 x Gigabit Ethernet Packet Module, with SFP optics
20 x Gigabit Ethernet Packet Module, with SFP optics
1 x 10 Gigabit Ethernet Packet Module, with XFP optic
2 x 10 Gigabit Ethernet Packet Module, with XFP optic
Multi-service Packet over SONET/SDH (PoS) Packet Module (portless)
ATM gateway Packet Module (portless)
Universal Gateway portless Packet Module (CES)


Issue 01
These units perform enhanced QoS and traffic management with the
DiffServ approach, providing:
8 forwarding classes (CoS) mapped onto 8 queues: Guaranteed classes (only
green packet) associated to real time applications which requires very low
delay, jitter and loss; Regulated and Best Effort classes (green and yellow
packet) associated to not real time applications and managed through 2
levels of frame drop probability
Queue scheduling discipline based on Strict Priority (the 2 highest queues)
and Weighted Fair Queuing (the 6 lowest queues) methods
3 scheduling priority levels: High, Medium and Low priority
3-tier QOS: per service (Virtual Transport logical path), per class, per Port
(hierarchical shaping).
The 1850TSS-320/160’s Data sub-system accomplishes the following
functionalities:
Ethernet cross-connection between two Ethernet ports
Ethernet per-flow cross-connection
Ethernet bridging


Issue 01
Ethernet main features:

Ethernet protocol (802.3)
Ethernet media access control (MAC) auto-learning and aging
Ethernet MAC static configuration
VLAN push, pop, swap (service delimiting)
Ethernet virtual bridging (802.1 q)
Ethernet provider bridging (802.1 ad)
RSTP, MSTP Spanning tree Protocols
Link aggregation (LAG) on local port
Jumbo frame management
Y.1731/802.1ag Ethernet OAM (CC with RDI, LT, LB, AIS, Two-way Eth DM
proactive / on demand, on demand one-way Eth DM, proactive Eth SLM),
8 QoS Classes, associated with 8 different queues with a strict (on the first
two queues) plus a Weighted Deficit Round robin (the other six) scheduling
practice
Three levels Shaping
ETH flow, RGY counters


Issue 01
MAC “black-hole” forwarding prevention, in both “Dual node” and “Single

node” topology
MAC table retrieval, MAC access control list management
LPT (Link Pass-Through), LLCF (Link Loss Carry Forward)
T-MPLS / MPLS-TP main features:

Data Plane (T-MPLS / MPLS-TP)
Tunnel setup
T-MPLS / MPLS-TP OAM: CV / CCM (with RDI flag), APS, FDI / AIS, two-way DM
(proactive / on demand), Dual-End Synthetic LM (proactive)
T-MPLS Protection (bidirectional 1:1 linear trail protection or tunnel
protection)
E-Line, E-LAN.


Issue 01
ATM (Asynchronous Transfer Mode) gateway functionalities

ATM over STM-1 (VC4)/OC-3 (STS1) un-channelize data ingress side
RFC 4717 ATM VCCs/VPCs N:1 PWE3 mapping
RFC 4717 N:1 cell concatenation: 1 to 32 ATM cell mapped into one T-
MPLS/MPLS-TP packet
VPI/VCI translation, to perform VPI/VCI swapping at NE edge points of a T-
MPLS/MPLS-TP network
ATM OAM (F4,F5), ATM QoS <-> PWE3 QoS, OAM
ATM UNI-UNI cross-connection (XC of ATM cells of two UNI ports in the same
NE)


Issue 01
Example of implementations
1850 TSS-320 #1 1850 TSS-320 #2
ETH ETH ETH ETH ETH
ETH
ETH
ETH
STM
STM
ETH
ETH ETH
ETH
BRIDGE BRIDGE
STM
STM
ETH
ETH
STM
STM WDM ETH STM ETH WDM
STM STM
ETH
ETH
ETH
ETH
WDM ETH
BRIDGE
WDM
Ethernet
STM ETH ETH ETH
cross-connection
1850 TSS-320 #3

Issue 01
Data + TDM + WDM configuration
The 1850TSS-320’s Data sub-system manages data streams transported

over:
“local” 1GbE or 10GbE ports
“remote” Ethernet ports interfacing the Sonet network. The Ethernet packets
are mapped over Sonet by means of GFP.
WDM networks, using “colored” Ethernet interfaces or “transponder”

The universal/agnostic matrix is assigned the switching function. It combines both TDM and data
switching capabilities.
The SDH cards, WDM cards and Data cards are assigned the payload specific processing functions.

Issue 01
Pure Data Switching
Agnostic
Matrix
320Gbps
PHY Backplane
Packet Traffic
Ethernet MAC frame
Proc. Manager
formatter Data
port
Queuing (Virtual
MAC termination Output Queuing) “Agnostic” format adaptation
•1GbE /10GbE •Output queues •Frame assembling in fixed
•auto-negotiation Classification •WRED on each queue length packets
•Full/half duplex •Port Scheduling •Pacer for central Fabric
•Eth preamble •VLAN •Strict priority •Management of fabric packets
•MAU cross-over (elect. eth) Policing •WDRR delivery
PHY Backplane
Packet Traffic
Ethernet MAC frame
Proc. Manager
formatter Data
port

Both pure packet based traffic and TDM/packets inter-working are managed.
The Packet Processor card is foreseen to manage the data traffic. This card can host several
interfaces, thus reaching the best performances in terms of flexibility and modularity.
Policing: IETF compliant (CIR/PIR/CBS/PBS)
WRED: Weighted Random Early Discard

WDRR: Weight Deficit Round Robin

Issue 01
Data over SDH
Agnostic
STM-n Matrix
Line HO VC
STM-N Line
Resync. Mon. 320Gbps
Termin.
SDH port
EOS Layer adaptation PP MS

•GFP-F •One PP MS is able to serve several data Packet traffic from
•VCG, LCAS line cards (up to 10Gbps of data over Sonet other Data ports
•HO VC termination mapping). It implements the Ethernet
remote ports.
Data port
EOS
Adapt
Data port
Backplane
PHY Packet Traffic
Ethernet frame
MAC Proc. Manager
formatter

The Universal Matrix provides the functionalities of the standard HPC connection function, too.
GFP-F: Generic Framing Procedure-Frame

VCG: Virtual Container Group
LCAS: Link Capacity Adjustment Scheme

Issue 01
Data over WDM
The interconnections with the WDM sub-system are accomplished by

means of external optical fibers using transponders or colored interfaces
Agnostic
Matrix
WDM Line WDM Line 320Gbps
WDM MUX/DEMUX or OADM
Data
Backplane
port
PHY Packet Traffic
frame
MAC Proc. Manager
formatter
Colored
interface
Backplane
PHY Packet Traffic
Ethernet frame
MAC Proc. Manager
formatter
Data
port

Issue 01
T-MPLS introduction
T-MPLS is a network layer technology that uses a subset of the existing

MPLS standards and is designed specifically for application in (packet)
transport networks. It is a connection-oriented packet-switched (CO-PS)
technology, well suited to support Ethernet services. It offers a simpler
implementation by removing features that are not relevant to CO-PS
applications and adding mechanisms that provide support of critical
transport functionality (T-MPLS = MPLS - IP + OAM).
More precisely T-MPLS creates an application profile for the use of
MPLS frame format (MPLS header), MPLS forwarding paradigm (e.g.
label swapping and stacking) and the client to MPLS mapping in
transport networks (PWE3).
T-MPLS uses the same architectural principles of layered networking
that are used in other technologies like SDH and OTN and provides a
reliable packet-based technology that is familiar and aligned with
circuit-based transport networking. It can run on any physical layer.
T-MPLS is a transport optimized technology that provides QoS, end-to-
end OAM and protection switching


Issue 01
T-MPLS introduction [cont.]
The implementation of Ethernet services with T-MPLS benefit from

Transport MPLS of being both
a packet technology (i.e. better fitting the nature of packet services like
Ethernet)
a transport technology (i.e. a carrier-grade technology supporting OAM,
protection switching and restoration, management).
In a T-MPLS connection-oriented domain, a stream of data client (any
L2) always traverses a common, predetermined path via the
establishment of a label switched path (LSP). At the ingress switch,
each packet is assigned a label and is transmitted downstream. At each
switch along the path, the label is used to forward the packet to the
next hop.
T-MPLS uses a differentiated services architecture to manage traffic: all
packets crossing a link and requiring the same forwarding behavior are
said to constitute a behavior aggregate. At the ingress node, the
packets are classified and marked with a code point that corresponds to
their behavior aggregate (based on the service configuration policy).


Issue 01
T-MPLS introduction [cont.]
At each transit node, the code point is used to identify the per hop
behavior that determines the appropriate scheduling and buffer
management treatment and, in some cases, the drop probability for
each packet.
With its linear/ring protection and restoration schema, differentiated
service capabilities and flexible, configurable on-demand OAM tools, T-
MPLS carrier-class packet transport network technology enables service
providers to provide a wide range of service levels to users.
Transport MPLS networks are able to provide the following services:
Point-to-point EPL/EVPL based on MEF E-Line (point-to-point EVC)
Multipoint EVPLAN (Ethernet Virtual Private LAN) based on MEF E-LAN
(multipoint EVC)


Issue 01
T-MPLS network layering model


Issue 01
T-MPLS over Ethernet and T-MPLS over TDM
In Figure the path of a packet entering the 1850 TSS from a UNI
interface is depicted

The packet enters in the example from a Gigabit interface on the 10x1 Gigabit (only four interfaces have
been configured) in the left side. It first goes through the Packet processor (PP), where the packet is
classified.
The packet (let's suppose n Ethernet packet) is then switched based on rule for that port or packet.
If the rule states that packet has to be PW encapsulated, the proper PW label is applied and then the
proper T-MPLS tunnel label may be stacked on it before determining the proper destination
card/interface. The packet is then forwarded to the TM.
It is switched through the matrix at Packet level and then it may enter on the right side:
the ETH Card (e.g. 1x10Gbps or 10x1Gbps Packet Module), if the packet has to be kept and
forwarded at ETH link layer
the EoS card (e.g. 10G Portless EoS Packet Module), if the packet has to be encapsulated in a TDM
timeslot. In this second case it must first pass through the EoS card. It is processed as explained by
TM and PP before being mapped with GFP on the proper VCG (also with LCAS capability if enabled).
Before exiting the system, the Universal Matrix needs to be crossed again. The switch is done at this
layer and the packet finally can exit from the TDM card towards the NNI.

Issue 01
Link Aggregation Group (LAG)
Link Aggregation is supported at the Ethernet side, as specified in IEEE-

802.3ad rec.; it is a technique to aggregate many data streams into a
single logical link. The resulting aggregate link will be treated by the
system (with regard to instances about STP, IGMP, network protections,
etc.), as a single link. It permits to overcome the bandwidth limitation
of the single ethernet interfaces, or to protect the traffic.
1Gbps, 10Gbps,100 Mbps and VCG ports may be aggregated. The max
number of ports (LAG-size) to be aggregated is 16. Links may be
anytime added or removed to/from the bundle.
Ports to be aggregated can be either located on the same board and
also on different boards.
Its management in the network is based upon the communication,
between the aggregate partner equipments, of LACP messages (Link
Aggregation Control Protocol). The LACP packets transport information
about set-up, aggregation capability, links failures, automatic
reconfiguration after failure, etc.


Issue 01
Link Aggregation Group (LAG) [cont.]
In addition to default of MAC SA/DA field, the enhanced LAG key shall
be based on the following fields of the composite Ethernet frame :
MPLS labels (up to 3) (3* 20) bits
VLAN tags (Outer VID +Inner VID) (12+12) bits
IP SA/DA (32 +32) bits
L4 Source/Destination port number (16+16) bits
All packets belonging to the same conversation (i.e. same MAC-DA/SA)
are transported over the same link. The packets cannot be fragmented,
i.e. a packet is transmitted entirely on the same link.
More conversations (i.e. different MAC SA/DA) can be transported on
the same link.
The benefits of Link Aggregation feature are:
Bandwidth limitation overcoming
Load balancing (the traffic is distributed over the constituting links);
Reliability increasing (in case that a link of the aggregate fails, its traffic will
be automatically distributed over the other links of the aggregate).


Issue 01
Link Aggregation Group (LAG) [cont.]
The conditions for Link Aggregation option are the followings:

All involved ports must work at the same rate
All involved ports must have the same configurations, regarding
AutoNegotiation and FlowControl
All aggregated links must be point-to-point (Multicast is not allowed)
All involved interfaces must work in full-duplex modality
All involved ports must be Local or Remote
Actor and Partner ports (local and far sides) must be of the same type.


Issue 01
Link Aggregation Group on VCG port
The Alcatel-Lucent 1850 Transport Service Switch (TSS-320/160)

supports the capability to apply the Link Aggregation method over a
Virtual Concatenated Group (VCG), in order to allow the connectivity of
the system itself, through the SDH matrix, towards remote access
interfaces located both on one or more boards of the same or different
equipment.
The VCG must be of the same type (VC12,VC3,VC4)
The bandwidth of the LAG is defined by the “minimum” number of
members among the different VCGs multiplied by the number of legs.
This allows the operator to increase the bandwidth of the LAG,
increasing one by one the number of members of the different VCG


Issue 01
Link Aggregation Group (LAG): example
In this example, a 5Gbps packets stream, is transported on an incoming

segment over a 10Gbps link, and the outgoing segment is implemented
by means of the Link Aggegation feature, using 7 Ports at 1 Gbps, of
which 2 are used for protection (Stand-By links). In case of failure, the
traffic of failed link is switched to the stand-by port having higher
priority.

Each port (p1 to p7) is associated by the operator to a priority, in which lower value means higher
priority.
Exaple of Port-Priority association:
p1: prior 6
p2: prior 5 (highest priority)
p3: prior 12
p4: prior 87
p5: prior 21
p6: prior 252 (lowest priority)
p7: prior 251
With these values of priorities, having a LagSize=5 and PortRate=1Gbps, the ports p6 and p7 are set, by
the system, to"StandBy" state. In case of failure on a port, the traffic will be switched to port p7, that
has priority higher than p6. In case the priorities between the two connected equipments do not
match properly, then the Master system can change the priorities of the peer system.

Issue 01
ATM: introduction
ATM Gateway aggregates ATM (ATM/VC-4/STM-1) traffic coming from

legacy ATM networks via STM-1 unchannellized ports, while leveraging
installed base (e.g. ISA-ATM into 1660SM) that aggregates mobile traffic
collected from Node-Bs and Base Stations via E1 (ATM) / nxE1 (ATM
IMA).
ATM cell relay service provides a VCC or VPC equivalent connection
over a PTN with either multiple or single ATM connection deployment
models (as per RFC 7417):
Binding multiple VCC/VPC to a single pseudowire allows a more efficient use
of the PW header space and makes easier the VCC/VPC service provisioning
The provision of a single VCC/VPC to a pseudowire allows to better satisfy the
QoS and restoration requirements.
The application scenario is shown in the next page


Issue 01
ATM: introduction [con’t]
The system supports the following main features:

ATM cells mapped only in STM1 (VC4) at the ingress side
The system is requested to support the N to one mapping method, where one
or more ATM connections (VCCs or VPCs) are mapped to one PW; ATM header
is copied unaltered in the T-MPLS packet


Issue 01
The system is requested to support both single and multiple connection

deployment models. The single connection deployment model is
implemented using the N-to-one encapsulation method, with N = 1.
cell concatenation mode, as per RFC 4717, where up to 32 ATM cells can be
mapped into one T-MPLS packet. The maximum number of ATM concatenated
cells into one T-MPLS packets is configurable per concatenated ATM flow in
the range [1,32] (1: no concatenation, 32: PW size = 1676 bytes), see Figure
below. The maximum number of concatenated cells per 5G Multi-Service ATM
card is 32 K.


Issue 01
The same ATM PW can carry both concatenated and not concatenated
ATM flow. Moreover, the following conditions shall be applied:
Concatenated cells , carried by the PW, can belong to more than one ATM
flow, with upper limit of 4K
In case of cell concatenation when an ATM OAM packet (e-to-e/segment F4
and F5) is received, the previously already enqueued cells for that PW are
sent in a TMPLS packet. The OAM cell is sent in the subsequent packet.
ATM flows included in a concatenated group should have the same ATC
(ATM Traffic Contract profile). This ATC is translated in the
corresponding T-MPLS PHB of the concatenated packet.
The timeout for the generation of T-MPLS concatenated packet is
configurable:
Per concatenated ATM flow
In the range [0.1ms -10ms],with step of 0.1ms
The CLP(Cell Loss Priority) bit changing in the ATM cells used as trigger for the
generation of the MPLS packet containing concatenated ATM cells is
configurable per concatenated ATM flow

The system is requested to implement the VPC/VCC mapping to PW per port, that is VPC/VCC from
different ATM ports are not mapped in the same PW.

Issue 01
The figure shows examples of CoS handling in a concatenated packet:


Issue 01
ATM internal p2p connection
It is an ATM internal (inside the NE) connection, between an ATM

attachment circuit and another ATM attachment circuit, referring to
ATM ports on the same ATM card or on different ATM cards.
The feature is based on the supported ETS cross-connection in TMPLS
context when UNI to UNI connection is provided without assigning any
label (PW or tunnel).
The VPI/VCI translation can be performed either at the ingress or at
egress point


Issue 01
ATM N-to-one cell mode mapping
4 bytes
Tunnel Header
PW Header
OPTIONAL
ATM Control Word
12 bits 16 bits 3 bits 1 bits
ATM Service Payload VPI VCI PTI CLP
ATM header
(4 bytes ATM header
+ 48 byte ATM payload)
52 bytes
one or more ATM concatenated cells
… length = m x 52 byte + 4 byte (Control Word)

min 56 bytes


Issue 01
ATM Services interworking
In case of ATM over PW, 9500 MPR delivers to TSS320 a VLAN tag in
front of a PW header for one-to-one mapping. Optionally Tunnel label is
used between PW and VLAN. The following processing are required on
TSS320:
Classification at ingress port on VLAN/PW basis (optionally tunnel)
Removal of VLAN (pop operation) towards T-MPLS network
Addition of VLAN (push operation) towards MPR network
The signal exchanged between MPR and TSS320 carries PHB QoS
information in the PW/Tunnel EXP bits (Class Of Service).


Issue 01
CES: introduction
The UGW card shall support CES (Circuit Emulation Service) capability
for DATA application, where a TDM client (TDM E1 only in this release)
is mapped into an upper server layer , that can be :
TMPLS server layer (TDM over Packet), performing SAToP function (“Structure
Agnostic over Packets”), as per RFC 4553;
Ethernet server layer (CES over Ethernet: CESoETH), as per MEF-8 Note. (not
available in this release)
The UGW can be placed into the general transport architecture of
TMPLS network, where:
TMPLS interworks directly with TDM network at its edges (via SAToP): in the
TDM-to-MPLS direction, the continuous TDM stream is segmented and
encapsulated into an MPLS packet by the interworking function (IWF). For the
MPLS-to-TDM direction, the TDM segments are extracted from the MPLS
packets and the continuous TDM stream is reassembled.
TDM network is mapped over Ethernet (via MEF-8) before entering the TMPLS
core network: TDM stream is segmented and encapsulated into Ethernet
packets using MEF-8 IWF, before entering TMPLS transport network (which
provides PW and Tunnel labels). At the remote end , Ethernet packets are
extracted from MPLS and the reverse MEF-8 IWF is performed for TDM stream
reassembly. (not available in this release)

Issue 01
CES: introduction [con’t]
The UGW card shall support the following CES capabilities:

Up to 1008 bidirectional E1 CES sessions.
E1 SAToP over PW (RFC4553)
E1 structure agnostic (MEF-8) over MPLS PW for a T-MPLS node (interworking
function).


Issue 01
CES: SAToP
The system shall support Structure-Agnostic Time Division Multiplexing

(TDM) over Packet (SAToP) encapsulation method (RFC4553) for
structured or unstructured PDH signals, disregarding any structure that
may possibly be imposed on these signals.
Only E1 PDH signals shall be supported in current release.
Structure-Agnostic encapsulation method allows for transport of
unstructured TDM, or of structured TDM when the structure is
completely disregarded by the transport mechanism. This mechanism
maintains the precise bit sequence of data and any structure overhead
that may be present. The encapsulation provides no mechanisms for the
location or utilization of a frame alignment.
TDM signals are treated as bit-streams and carried across the PSN in
their entirety; this includes TDM framing and the associated control
information (if present), as well as the payload.


Issue 01
CES: SAToP [con’t]
The general application scenario for SAToP is shown below:
The system supports SAToP packets encapsulation over T-MPLS

interface with MPLS label stack provided by Tunnel and PW labels


Issue 01
5 Controller Sub-system


Issue 01
Control sub-system

With the extensive introduction of SONET/SDH and WDM in the transport network, centralized and
integrated network management is mandatory for Network Operators to realize the potential cost
saving and required Quality of service.
The ZIC (Zero-Installation Craft terminal) is a project in charge of the local management of single
network elements from different Alcatel-Lucent SDH and WDM products, providing ITU compliant
Information Model Interface to the Network Element.
The ZIC uses a state-of-the-art platform for providing an advanced and integrated Management.
The 1850 TSS-320 control sub–system is based on a two level model :
Equipment Controller (EC) implemented by the EC320 card.
Shelf Controller (SC) implemented as part of the MATRIX card.
Local Data Controller (LDC) located on Data traffic cards.
The Matrix provides the HW resources (physical interface, the M interface), while EC provides the SW
functionalities (protocol stack) and the management agent (TL1, SNMP, CLI) required for the
communication between NE and Management system (OS, craft terminal, etc)
EC performs as well all the SW functions related to the control and management activities like info–
model processing, event reporting and logging, equipment data base management, SW downloading
and management, etc. It can be provided in 1+1 configuration.
The following buses belong to the internal control sub-system:
• HW Control bus that allows:
– Connection between SC and the µProcessor of the traffic ports for provisioning and control
– Remote inventory data acquisition
– Data collection (alarms) and commands handling (ex. loops)
• SW Control bus, used for communication among the Equipment Controller, Shelf Controllers and the
Local Data Controllers, located on Data traffic cards.
Issue 01
Controllers
First Level Controller

• HW resources and SW functions for the communication
between the NE and the managing system
• MIB management
FLC
• SW download, Performance Monitoring, Alarms
LAN
Second Level Controller
• SDH/WDM functionalities
SLC SLC • Provisioning
• Alarm & performance monitoring
ISPB
Termination • Protections management
HW Config
Bus • FPGA download, update and configuration
• Reporting to FLC all of collected info
LDC
SPI
Board Local Data Controller
• Only on Data boards
• Same functionalities exploited by SLC, but for data
• Reporting to both FLC and SLC

FLC:
It is implemented by the Equipment Controller card
Its functions are:
HW resources and SW functions required for the communication between the NE and the
management system (OS/CT).
All the agents (Q3,SNMP,CLI,…) that are requested for the management of the NE
Management of the NE database, resident on Hard Disk.
Management of Housekeeping I/O, Remote Alarms and Rack Lamps via dedicated HW and SW.
SLC:
It is implemented by the Matrix card
Its function is the control and management of the machine for the part concerning SDH/WDM
functionalities only.
SLC application SW is loaded and started by bootstrap procedure.
Bus:
ISPB (Intra Shelf Parallel Bus):
Configuration and access to any kind of component
SDH alarms and PM
LAN:
Communication among microprocessors
Data alarms and PM
SPI (Serial Peripheral & Inventory): WDM boards management
HW Configuration: Download of FPGA

Issue 01
Internal and External LAN
Equipment Controller
board
1000 1000
Boards
10/100
10/100/1000 10/100/1000
1000
ETH ETH 1000
Drop 10/100 10/100 Drop
Shelf GE Q3 Q3 GE Shelf
switch switch
Drop switch Q3 Q3 switch Drop
Shelf spare spare Shelf
10/100 10/100
10/100
Debug 10/100
SLC SLC 10/100 Debug
interface IPL interface
Matrix board A Matrix board B

IPL (Inter Processor Link): it brings the traffic meant to support the standby functionality.

Issue 01
6 Protection Sub-system

Product Overview Architecture Section 1 Module 2 Page 61

Issue 01
Supported protections
The 1850TSS-320 supports the following protections:
Equipment Protection
MT320 (matrix): 1+1 protection;
EC320 (FLC): 1+1 protection
LOA (Lower Order Adapter): 1+N (N=1 or 2) protection
PP10ATM (5G ATM gateway portless packet processor): 1+1 protection
Network Protection
SDH protections:
1+1 Linear APS (MSP, Multiplex Section Protection), single/dual ended
(STM1/4/16/64)
SNCP/I, SNCP/N (Subnetwork Connection Protection), (VC12/VC3/VC4)
2F MS-SPRING (2 Fibers Multiple Section Shared Protection) (STM16/64)
Drop & Continue
DATA protections:
bidirectional 1:1 linear trail protection (Tunnel level), as for ITU-T G.8131; only
one way is working, in case of failure on the working path, the protecting one is
selected (APS protocol)
Link Aggregation Group (LAG) on UNIs, is able to group a set of Ethernet interfaces
into one logical interface with greater capacity and reliability, providing link
protection
Rapid Spanning Tree Protocol (RSTP) (802.1D)
Multiple Spanning Tree Protocol (MSTP) (802.1Q).

Product Overview Architecture Section 1 - Module 2 - Page 62
EPS: Equipment Protection Switching

SNCP/I: Sub Network Connection Protection / Inherent
SNCP/N: Sub Network Connection Protection / Non intrusive
Power Supply Units don't use a working/protection scheme but work in load sharing. When one of the two
modules is not ever able to supply Power, the other one takes 100% of the load, whatever is the Logical
state of the two boards.

Issue 01
EPS
The hardware failures causing automatic EPS protection switch can be

grouped as:
failures causing the internal equipment link loss as powering KO, Clock loss,
card missing
failures causing traffic loss (the internal link is preserved) as for instance
unlocked oscillator, electrical interface defective and so on.
failures not causing traffic loss nor internal link loss but causing loss of
management as internal bus failures.
The EPS is available for the following card:


Issue 01
SNCP introduction
SNCP (Subnetwork Network Connection Protection) in SDH networks are

used to protect a path (e.g. that portion where two separate path
segments are available) or the full end-to-end path, i.e. HO/LO Path
layer for SDH.
The traffic is recovered through a ‘dedicated’ mechanism, where one
‘protection’ resource is used for protecting one ‘working’ resource (i.e.
1+1). As a consequence the traffic is bridged to both resources.
In SDH technology, two possible types of SNCP are considered:
SNCP/I (Inherent monitoring) protecting the traffic against failures that
affects the ‘server’ layer; it switches on SSF criteria (AU-AIS and AU-LOP).
SNCP/N (Non-intrusive monitoring) protecting traffic against failures that
affects the ‘server’ layer and failures affecting the ‘client’ layer; POH is
monitored by the POM enable before the matrix. The switches criteria are
SSF and one or more of ExBER, TIM, UNEQ, SD;

The Tx signal reaches destination through two different paths thus enabling the node receiving it to
select the best one (switch).

Issue 01
SNCP introduction [cont.]
Each transmitting signal node is permanently connected (bridge) in the

main traffic direction (clockwise) and in the protected traffic direction
(counter clockwise).
Two operating modes can be selected:
revertive:
the signal is switched back to the main channel, after the recovery of the fault
the “Wait time to restore” (WTR) is fixed at 5 minutes
not revertive


Issue 01
SNCP introduction [cont.]

On ZIC, the following terminology is used:

Pass-Through= Bidirectional Connection
Drop/Ins Prot.= Bidirectional Protected Connection

Issue 01
Failure examples in SNCP ring


Issue 01
Failure examples in SNCP ring [cont.]


Issue 01
1+1 Linear MSP Protection Switching
The system supports 1+1 linear Multiplex Section Protection (MSP) for
STM-1, STM-4, STM-16 and STM-64 signals. In 1+1 Linear MSP, the head-
end signal is permanently bridged to both the working facility and the
protect facility. At the tail end, both the working facility and the
protect facility are monitored independently for failures. The receiving
NE normally selects the working facility. In the event of failure, the
protect facility is automatically selected. 1+1 Linear MSP is a local
action that involves no changes elsewhere in the network.
Features:
Revertive or non-revertive switching
Revertive—Service is switched back to the working facility after the condition that
caused the automatic switch clears and the Wait to Restore (WTR) time has
expired.
Non-revertive—Service is switched back to the working facility only when the
protect facility becomes unavailable or when a manual protection switch command
is received.
The switching criteria are: Loss of Signal, Loss of frame, MS-AIS/AIS-L,
Excessive BER/Line BER and (user provisionable) Signal Degrade.

Issue 01
1+1 Linear MSP Protection Switching [cont.]
This feature permits a 1+1 protection in a linear link, where a path signal
is protected by another dedicated path which carries the same signal.
The protection can be set both in single and in dual ended mode.
In single ended mode (unidirectional) the protection is accomplished by
switching only the signal affected by the failure.
In dual ended mode (bidirectional) the protection is accomplished by
switching both the affected and the unaffected signals.
The switching signalling is carried over the APS channel (K1 and K2
bytes), using the K-byte protocol.
Protected and Protecting ports cannot be on the same card!

Each STM stream can be protected by an electrical or optical stream of another port.

Issue 01
1+1 Linear MSP Protection Switching (single ended)
The picture shows an example of linear single ended 1+1 protection,
and the case of signal switching after an unidirectional failure on the
main link (APS= Automatic Protection Switching).


Issue 01
1+1 Linear MSP Protection Switching (dual ended)
The picture shows an example of linear dual ended 1+1 protection, and
the case of signal switching after an unidirectional failure on the main
link.


Issue 01
1:N Linear MSP Dual-Ended protection
The Linear protection switching scheme is a method for traffic recovery

applicable to 'point to point‘ (i.e. linear) network topology.
It is a shared mechanism, in this case one 'protection‘ resource is used
for protecting the traffics carried by one or more 'working‘ resource
(i.e. 1:N, with N=1 to 14). It applies to STM-n synchronous interfaces.
In this mechanism the priority can be assigned to the main resource so
that in case of double failure the high priority traffic is restored.
The switching criteria are:
Loss of Signal,
Loss of frame,
MS-AIS,
Excessive BER,
Signal Degrade.


Issue 01
1:N Linear MSP Dual-Ended protection
The picture shows an example of linear dual ended 1:N protection, and
the case of signal switching after an unidirectional failure on one of the
main link.


Issue 01
1:N Linear MSP Dual-Ended protection [cont.]


Issue 01
2F MS-SPRing
The following MS-SPRing protections are supported:

2 fiber MS-SPRing at STM-16 (VC4 level)
2 fiber MS-SPRing at STM-64 (VC4 level)
The MS-SPRing (Multiple Section Shared Protection Ring) protection is
realized in the Matrix card.
A 2 fiber MS-SPRing consists of a set of NEs each equipped with a two
bidirectional ports, one for the clockwise and the other for the counter-
clockwise. The MS-SPRing is said “two fiber” because each pair of
adjacent NEs is linked by two fibers, one for each direction.
The MS-SPRing protection is an alternative with respect to SNCP. While
MS-SPRing allows the connection at the same time on the clockwise and
on the counter-clockwise direction on the same AU4 that can be
inserted and extracted in each span, on the contrary the SNCP
connection engages the same AU4 on both sides for the whole link.


Issue 01
2F MS-SPRing: Failure study
PROTECTED Switch Bridge Switch

SIGNAL
SF/SD
B A B A
Bridge
1 2 3
A B
B A
A B A B
6 5 4
WORKING CHANNELS 1 fiber carries both PROTECTED

PROTECTING CHANNELS type of channels SIGNAL
In case of failure, all protecting AU-4s are put in pass through in the 1st, 6th, 5th and 4th NE
The 2F MS-SPRing algorithm starts as a consequence of the following Signal Failure (SF) or Signal
Degrade (SD) alarms:
LOS
LOF
MS AIS
Signal degrade (B2)
In case of Multiplex Section 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 permits the ”high priority” traffic to be restored.
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” (low priority) AU4s.
The max number of NEs in a ring with MS-SPRing is 16, due to the limitation of K1, K2 protocol.

Issue 01
T-MPLS protection at Tunnel level
T-MPLS protection switching is based on a specific APS (Automatic

Protection Switch) protocol, defined in G.8131 (linear protection) and
under definition in G.8132 (ring protection). APS information is
exchanged using a OAM communication channel as defined in ITU-T
G.8114/Y.1373.
T-MPLS protection switching is analogue to the existing schemes for
other transport technologies (e.g. SDH).
T-MPLS supports bidirectional 1:1 linear trail protection for Tunnel (see
next page for details)
1-phase APS protocol is supported, revertive switch only is
implemented.
In 1:1 architecture a protection connection is dedicated to each
working connection.
The normal traffic is transported either on the working transport entity
(tunnel) or on the protection transport entity using a selector bridge at
the source of the protected domain.
At the sink of the protected domain the entity that carries the normal
traffic is selected.


Issue 01
T-MPLS protection at Tunnel level [cont.]
In case of failure, protection switching is performed by the selective

bridge at the source of the protection domain: both directions of the
connection are switched to protection. The APS protocol coordinates
source and sink bridge. The service always returns to (or remain on) the
working connection as soon as the switch requests are ended.
Sum of the main features of the T-MPLS Trail protection: end-to-end
protection architecture:
1-phase APS protocol: the communication between the two ends of the
protected domain, e.g. A and Z, is only in one phase, from Z to A or A to Z
Bi-directional switching type: both directions of the connection are switched
to protection. APS protocol is required to coordinate the two endpoints
Revertive: service will always return to the working connection if the switch
request is terminated.
Switching criteria:
Connectivity Verification (CV) function, with periodicity of 3.33 ms
Forward Defect Indication (FDI) detection.


Issue 01
T-MPLS protection at Tunnel level [cont.]
Bidirectional 1:1 linear trail protection for Tunnel


Issue 01
7 Synchronization architecture

Product Overview Architecture Section 1 Module 2 Page 81

Issue 01
Synchronization main processes
The equipment Clock Reference Generator (CRG) function is located in

a daughter board mounted on the matrix card (MT320 or MT160).
The board also hosts second level controller.
The main processes by which the clock reference function is made up,
are summarized in the following picture

The characteristics of the timing function are in accordance with ITU-T G.813 Option 1 (networks
optimized for the 2048Kbit/s hierarchy) and ETSI prETS 300 462-5 are the references for internal and
external clock generation.
ETSI prETS 300 417-6 and ITU-T G.781 are the reference for the basic building blocks and algorithms
determining the timing function behaviors (sync interfaces configuration, SSM management, external
commands etc.).
All the boards present in the system included data boards, UNIVERSAL MATRIX and LO matrix are slave
with respect to the clock and sync pulses distributed by matrix card and therefore every card must
receive those signals.

Issue 01
Shelf synchronization
The equipment Clock Reference Generator (CRG) function includes an

internal oscillator and two synchronous timing generators one for the
internal clock (T0) and another one for the station output clock
(T4/T5).
The active CRG, for instance CRG A, provides the internal equipment
master clock (T0) to every card in the system as output of T0 filtering
process (Phase Locked Loop) which can be phase locked to different
synchronization sources as determined by T0 selection process; when
no valid sync inputs are available the CRG will run in free-running or
holdover mode.
The selectors SEL_A and SEL_B controlling the synchronization sources
for the equipment internal clock (T0) and for the generated output
reference clock (T4/T5) are controlled by processes fully independent.
The equipment supports handling of synchronization signal derived from
Etnernet interfaces, as per ITU-TG.8262 (June 2007), and used for clock
distribution and network synchronization.


Issue 01
Shelf synchronization [cont.]
ITU-T G.8262 is mainly reflecting G.813 “Timing characteristics of SDH

equipments slave clocks” while Jitter/wander requirements for
Ethernet come from IEEE 802.3, so that SDH and Synchronous Ethernet
(SyncE in the following) equipments can interwork in the same
synchronization network.
The output Ethernet interfaces can be locked to the local CRU (default
configuration).
SyncE is supported by dedicated Packet Modules, listed in the following:
PP1GESY (10 x GE interfaces) with 1000 Base-X interfaces (optical SFPs)
PP1GEX20 (20 x GE interfaces) with 1000 Base-X interfaces (optical SFPs)
PP10GESY (1 x 10GE interface) with 10G Base-LAN interface (optical XFP).
PP10GEX2 (2 x 10GE interface) with 10G Base-LAN interface (optical XFPs).
SyncE is not supported by 100/1000 Base-T electrical interface/SFP
(working in 802.3az mode).
SyncE interfaces provide a reference clock signal (TE), used as Clock
Reference Generator (CRG).


Issue 01
Up to 6 recovered 2048Mhz clock signals (TE IN) can be supplied to CRG

by SyncE interfaces (from any traffic ports/slots). This reference timing
is used as source for T0 internal clock as well as the external reference
output interfaces T4/T5. TE can be delivered according to the following
options (EEC Options) as per ITU-T G.8262:
EEC Option 1: for SDH equipments only, in compliance with ITU-T G.813
Option 1 and ETSI prETS300462-5 (for external clock generation). T0 internal
clock is based on SEC quality level SSM quality indicator is coded as 1011
(G.813)
The system supports handling of SSM indicator for reference timing
Quality Level from SyncE signals, by providing periodic transmission of
ESMC messages carrying Quality Level indicator, as per ITU-T G.8264 (in
cooperation with IEEE).
LOESM alarm is raised when ESMC timeout is reached, to trigger cutoff
of the reference clock used as timing synchronization source for T0,
thus either entering the “holdover” state, or selecting a different
reference timing, priority based.


Issue 01
SyncE SSM management is supported via ESMC messages, providing two

types of message:
Heartbit (every 1 sec.), carrying ESMC information
Event (immediate), providing accuracy state change (e.g. Quality Level)
This behaviour is similar to SDH SSM management.
For the cards implementing SyncE interfaces, it is possible to enable
forwarding ESMC received messages to LDC per each physical interface
(sink function). Sink enabled port must also be source enabled (e.g.
transmitting ESMC messages).
The system supports “Transparent Clock” (TC) functionality to allow
the transport of ToD (Time of Day) protocol across data networks, as
per IEEE 1588v2 standard.
IEEE 1588 v.2 is also known as PTP (Precision Time Protocol). PTP is a
message based protocol, and it is designed to synchronize clocks across
packet based network. PTP allows for synchronization of distributed
clocks to sub-microsecond accuracy with devices that may have
different precision, resolution, and stability.
ESMC message provides timing info only for the SyncE reference, without extension to phase information.
Currently up to six ports can be enabled for SSM management, with further extension to all the Ethernet
ports, where the extended phase info shall be applied.

Issue 01
Standard Ethernet switches introduce a variable delay to packets that
inhibits path delay measurements. Transparent clock have been
introduced to measure and adjust the packet delay, thus removing the
negative effects that these variations cause.
IEEE 1588v.2 Synchronous Ethernet is supported by the following Packet
Modules:
20xGE Packet Module with 1000 Base-X interfaces (optical SFPs)
2x10GE Packet Module with 10G Base-LAN interface (optical XFPs).
The system supports the Fiber Asymmetry configuration for IEEE 1588v2
Transparent Clocks (TC), in order to compensate different delay
contribution in case of asymmetric fiber length.
The IEEE 1588 differs from SyncE in 2 fundamental ways:
In addition to frequency synchronization, it achieves time-of-day (ToD)
synchronization (an accurate value of the current absolute time) to achieve
phase alignment which is required for multi-channel communications.
It is a purely packet-based solution, with the actual clock values being
passed inside the payloads of special packets dedicated to that task.


Issue 01
CRG functional view
In any operation mode (i.e. locked, holdover and free-running) the

stand-by CRG, for instance CRG B, is phase locked to same
synchronization source selected by the active one (CRG A in the
example); both CRG receive the same reference sources and in
particular in non locked condition, the stand-by CRG is synchronized
with the local oscillator of the working copy.


Issue 01
Synchronization sources
The T0 clock selector SEL_B selects one reference synchronization

source from a number of signals derived from SDH signals and/or from
external reference (station) synchronization signals:
For SDH network 2 external 2Mhz (T3) or 2Mbit/s (T6) input clocks from
POW320 or PSF320 units (one from copy A and one from copy B) are
supported
Up to 6 recovered clock from traffic interfaces (T1). Each optical or
electrical interface of any SDH port card can be provisioned to gain access to
a 6 wires clock bus.
T1: STM-N transport signals carry (in addition to the payload) reference timing
information and the indication of the quality level of the source generating this
timing information, via S1 byte as defined in Rec ITU-T G.707
Local and remote oscillators (OSC) clocks.


Issue 01
Output clock generation
One redundant external station output reference clock is provided by

each POW320 or PSF320 units; these signals can be set either as 2Mhz
without SSM information (T4) or 2Mbit/s with SSM information (T5)
output references.
The T4/T5 clock selector (SEL_A) will receive the same references
defined for T0 generation with the exception of the remote T0 clock;
this distribution is in line with ITU-T G.781
There is not any restriction about the number of signals taken from
each board. The only constraint is that the six T1 timing sources are
shared between T0 and T4/T5 selection processes: so the 2 selections
for T0 and T4/T5, even if fully independent, have to be done inside the
same group of six T1 signals.


Issue 01
Characteristics and operating mode
The SETG (Synchronous Equipment Timing Generator) function filters

the selected timing reference to ensure that the generated clock (T0) is
according to the relevant ITU-T (SDH) recommendations. Furthermore
SETG function must filter the step changes in frequency caused by
(hitless) changes in the reference source.
Three modes of operation of SETG function are provided:
Free running mode: it is a temporary operating mode entered when the
clock has never acquired the lock to external timing reference, or has not
access to the stored data acquired during previous lock state. The SETG
output timing is totally internally controlled and determined by the internal
oscillator.


Issue 01
Characteristics and operating mode [cont.]
Locked mode (steady state): the SETG generated clock signal is controlled
by the selected external timing reference determined by the T0 selection
process; the output clock is traceable to the selected input frequency over
long term and the phase difference between the input and output is
bounded. The “holdover memory” is acquired and periodically updated
(acquiring holdover memory is a temporary mode entered when coming from
free running state).
Holdover mode (steady state): the SETG has lost its controlling external
timing reference, and is using stored data, acquired while it is in locked
mode, to control its output. The stored “holdover value” is an average
figure obtained over a certain period of time in order to reduce the effects
of any short-term variations that might occur in the locked reference
frequency during normal operations. The internal oscillator signal is then
phase corrected according to the stored data, and used as timing reference
by SETG in holdover mode.


Issue 01
8 Power distribution architecture


Issue 01
GENTRU
Each rack accepts redundant independent battery power plants

providing
-38.4 VDC to -72 VDC for ETSI markets with diversely routed dual bus.
At the top of each rack that hosts a 1850 TSS-320 and/or a 1850 TSS-
160 is located a mini subrack named GENTRU (Top Rack Unit). It
provides power distribution to each shelf and related fans within the
rack and can host up to 6 modules (2 - for protection purposes - for
each of the 3 allowed shelves in a rack).
Each module can be either a STEP-UP (requested up-to 3.5 kW power
feeding) or a BY-PASS (for equipments requiring lower power supply).
Each module is connected to a Power Unit in the shelf. In case less than
3 shelves are hosted in the rack, the unused TRU slots are covered with
dummy covers. The GENTRU include front panel controls to
apply/remove power from each shelf individually.

The GENTRU performs the following functions:

Delivers power to the housed equipment by means of a DC/DC converter called “STEPUP”. The power
output is as follows:
The distributed voltage is:
58 VDC for ANSI standard/market.
65 VDC for ETSI standard/market.
The selection is done by means of the switch on the back of the STEPUP converter
The distributed voltage can be either 48V or 60V by means of the Bypass or Extension Bypass.
Delivers the service battery (VSERV+ and VSERV-) to the housed equipment (for future release)
Collects commands received from the equipment and then generates optical indications and
transmits remote alarms as necessary
Connects the assemblies equipment to the supervisory network through connectors within the GEN-
TRU.
In addition to the main voltage rails (-48V/-60V), each POW unit shall provide two service voltages:
3.6 V distributed to all slots of the equipment
5.3 V specific for legacy WDM cards management
The GENTRU can be equipped with:

LAMP GROUP:
The LAMP GROUP manages the alarms of the installed system.

Issue 01
GENTRU [cont.]
The GENTRU has the main function to (re)generate, from each one of
the up to three incoming battery power inputs, a set of (A+B
redounded) Battery cables for feeding each shelf in the Rack through
the plugged PSF boards (one PSF for Battery A access and one PSF for
Battery B access): the power supply to the other boards inside the shelf
and to the two FAN trays is then distributed through the Back Panel.
The GENTRU provides fuse-protection between the multiple battery
cable from plant (available through the rack framework) and the
shelves mounted within that rack.
The Maximum Power available from each step-up device output is 3.5
kW.
The NE triggers a major alarm when a power sequence fault, an under-
voltage fault, an over-voltage fault, or an over-current fault is detected
on either of the power supplies.The NE triggers a minor alarm when a
fuse is blown or a breaker tripped.

Each rack that hosts a 1850TSS 320 shall have a device named Top Rack Unit that has the main function
to (re)generate, from each one of the (maximum) three incoming (plant) battery power inputs, a set of
(A+B redunded) Battery cables for feeding the Shelves contained in the Rack through the plugged PSF
boards (one PSF for Battery A access and one PSF for Battery B access): the power supply to the other
Boards inside the Shelf and to the related two FAN trays is then distributed through the Back Panel.
The TRU shall provide fuse-protection between the multiple battery feeders cable from plant
(available through the rack framework) and the shelves mounted within that rack. The TRU shall
accept up to 3 independent inputs from the rack framework at nominal -48Vdc, with -38.4Vdc to -
60Vdc range or -38.4Vdc to -57Vdc range

Issue 01
GENTRU [cont.]
The Step-Up converter placed in the GENTRU has a low and high input
voltage shutdown feature:
In accordance with ETS 300 132-2 (ETSI). The low input voltage shutdown
shall occur when the input voltage measured at the input side is -35V to -
37Vdc. The restart shall happen automatically when the input voltage
measured at the input side of the step-up is -40.5V ±0.5V. The system shall
return to normal operations without manual intervention
DC/DC power supplies operate in redundant configuration (duplex, load
shared, etc.) such that a single power supply failure does not affect the
system.
The NE is not damaged from an input voltage between 0.0Vdc and its
minimum operating voltage of -37.5Vdc.

Each DC to DC converter shall have a low input voltage shutdown feature. The low input voltage
shutdown shall occur when the input voltage measured at the input terminals of the equipment is -39.5
to -37.5 VDC for more than 100 ms. DC-DC Converter operating shutdown feature shall be
implemented inside Step-up device
The Network Element shall restart automatically after a low input voltage shutdown. The restart shall
occur when the voltage measured at the NE unit input terminals is -43+/- 1.0 VDC. The system shall
return to normal operations without manual intervention.

Issue 01
GENTRU [cont.]
Feeding: the
Maximum Power
available from each
By-Pass output is 1
kW.
The battery return
of each feeder input
and frame ground is
isolated from the
battery returns of
the other feeder
inputs.

STEP-UP 3500W
The 3.5 kW STEPUP is a DC/DC converter. It behaves as follows depending on whether ANSI or ETSI
standard is selected:
ANSI standard: regulates the output voltage at 58 VDC with the input voltage in the range between
38.4 VDC and 58VDC. When input voltage is greater than 58 VDC and less (or equal) than 72VDC, the
device works like a pass through (the internal switching circuit turns off and the output wires are
connected directly with the input side).
ETSI standard: when the input voltage is between 38.4 VDC and 65 VDC, it is able to adjust the
output voltage at 65 VDC (the internal switching circuit works as a step-up converter to generate the
65 V at the output side). When the input voltage is greater than 65 VDC and less (or equal) than 72
VDC, the device works like a pass through (the internal switching circuit turns off work and the
output wires are connected directly with the input side);
EXTENSION BYPASS
The Extension Bypass works like a pass through in the range from 38.4 V to 72 V but with two breaker
fuses, not one, installed inside the group. The two distributed lines are protected by two fuse-breaker
that have a maximum capacity of 40 A.The power delivered at the output side is 3.5 kW and the stand-
by state (output side) is available when the output is not connected to the load.

Issue 01
Power Consumption (TSS-160/320)


Issue 01
Power Consumption (TSS-160/320) [cont.]


Issue 01
Blank Page


Issue 01
9 Network Management


Issue 01
Introduction
Introduction to network management system (NMS)

The Alcatel-Lucent 1850 TSS-320 and Alcatel-Lucent 1850 TSS-160 are
managed by a set of NMS (ZIC, EML, NMS) and a set of User Language
Interfaces (CLI, TL1). They are briefly described in the following:
ZIC: web based browser application running on NE Equipment Controller. It
allows to control both local connected NEs and remote connected NEs. It
provides basic management functions (support to turn-up, equipment
provisioning, service set-up, alarm surveillance, performance monitoring,
etc)
EML: application hosted on server/PC system, it allows to control single NEs
and also a set network of NEs. It provides basic management functions
(equipment provisioning, service set-up, alarm surveillance, performance
monitoring, SW download, Alarm Surveillance and network maps, etc)
PKT/SDH-SONET (NMS): applications hosted on servers, they allow to set-up,
monitor and control, respectively, for DATA / TDM end-to-end services
through the network
CLI: Common Language Interface, it is a string/command based interface
which allows to provision and monitor DATA (mainly ETHERNET)
functionalities at NE level

Issue 01
TL1: Telecommunication Language Interface, it is a TELCORDIA standard
ASCII string based command interface which allows to provision and monitor
TDM and DATA (mainly T-MPLS) functionalities at NE level
The network architecture is in general described by means of the OSI
(Open System Interconnection) Reference Model, which defines the
following seven layers: Application, Presentation, Session, Transport,
Network, Data-Link, and Physical Layers


Issue 01
Physical layer
The physical layer defines the communication medium used to
transport the management stack.
Alcatel-Lucent networks offer different solutions for the physical layer.
With respect to the relation of the physical layer of the management
plane of the actual transport layer, the following types of management
may be distinguished:
in-fiber or out-of-fiber, depending of the necessity of additional cabling (e.g.
LAN)
in-Band or out-of-Band, depending on the usage of the transport bandwidth.


Issue 01
Typically GNE are reachable via out-of-fiber/out-of-band connectivity

while RNE are reachable via in-fiber connectivity. The in-band/out-of-
band solution depends strongly on the Transport technology available,
i.e: for traditional SDH/SONET networks out-of-band is used based on
DCC, while for packet networks in-band solution is used based on
Ethernet or T-MPLS.
In case of in-fiber/in-band management over Ethernet, a dedicated S-
VLAN is allocated to the management flow which is threated with the
highest priority.
In case of in-fiber/in-band management over T-MPLS, a dedicated
Tunnel label is allocated to the management flow which is threated
with the highest priority.


Issue 01
Example
The figure provide an overview of the possible combinations of in/out-

fiber/band management options in connection with the new optics
equipment


Issue 01
Routing protocols
The equipment supports integrated IS-IS according to ITU-T Rec.

G.7712/RFC 1195 as general routing protocol for both OSI and IP
domains. This allows the usage of a common routing protocol in a
mixed environment. OSPF may be used in addition in the access DCN
area.
Static routes
Although from reliability stand point, dynamic routing is the preferred
option, the NE offers as well the possibility to set up static routes
which define in a fixed way the reliability path for a couple of end
points /NE, i.e. NE vs NMS systems.
Tunneling
While the equipment can support both OSI and IP stacks in a native way
in more complex networks, they can be located between clouds of NEs
supporting OSI-only or IP-only stacked way. In these cases the tunneling
functionality can be effectively exploited by TSS systems.


Issue 01
Routing protocols
The TSS-320/160 support the following tunnels:

IP-over-OSI tunnel, which is bypassing an OSI domain between 2 IP domains
(possibly reduced to a single NE)
OSI-over-IP tunnel, which is bypassing an IP domain between 2 OSI domains
(possibly reduced to a single NE)


Issue 01
Blank Page


Issue 01
End of Module
Architecture


Issue 01
21
Section 2
Functional Description
Module 1
Hardware Description-Common
Issue 01
1850 TSS-320 & 1850 TSS-160

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

Issue 01
Blank Page

Functional Description Hardware Description-Common
Document History

Issue 01
Objectives
Describe the common HW parts of the 1850TSS-320

and 1850TSS-160


Issue 01
Blank Page


Issue 01
Table of Contents
Page
1 Hardware Description - common 7


Issue 01
Blank Page


Issue 01
1 Hardware Description - common


Issue 01
1 Hardware Description – Common
1850 TSS ETSI Rack and composition


Issue 01
EC
1850 TSS-320 Shelf
MATRIX spare
MATRIX main
EC
42 T-BUS 43 T-BUS

The main features of 1850TSS-320 shelf are:

it provides 43 slots, allocated as follows:
16 full slots @20Gbps / 32 half slots @10Gbps for traffic cards (any card anywhere)
2 slots for redundant Controllers, Matrices and Power supply
1 slot for service unit
2 specific horizontal slots for Fans and 2 specific slots for Termination bus.
An 1850 TSS-320 node may contain one main/universal shelf, hosting any mix of traffic cards (CWDM,
FOADM, Data, SDH/SONET)

Issue 01
1850 TSS-320 Shelf [cont.]
Housekeeping
Rack Lamps
Remote alarms Auxiliary Channels

Shelf Identifier
Step-Up
alarms
inventory

Four output (CPO) and 8 input (CPI) contacts for housekeeping alarms or commands are physically available
on connectors placed at the top of the subrack backpanel

Issue 01
1850 TSS-160 Shelf
Wheels to set the Shelf Identifier
39
EC main EC spare
MATRIX spare
MATRIX main

The main features of 1850TSS-160 shelf are:

it provides 25 slots, allocated as follows:
8 full slots @20Gbps / 16 half slots @10Gbps for
traffic cards (any card anywhere)
2 slots for redundant Controllers, Matrices and
Power supply
1 slot for service unit
2 specific horizontal slots for Fans and 2 specific
slots for Termination bus.
It hosts FOADM, Data, TDM cards (it doesn’t support
CWDM cards). Only the single shelf configuration is
allowed
N.B.: To guarantee the correct airflow it is necessary
to assemble, above and below of the subrack, two
air deflectors.
The air deflector is made of two parts bracket and
plate, both are included in kit code 8DG87321AA*.
The upper air deflector installation to the subrack is
made by the two screws already present on the
subrack.
The lower air deflector installation to the subrack is
made by two bolts, see figure below

Issue 01
1850 TSS-160 Shelf [cont.]
(1) RJ45 8-pin connector for Step-Up “A” Alarms and Remote Inventory
(2) RJ45 8-pin connector for Step-Up “B” Alarms and Remote Inventory
(3) 9-pin male connector for Rack lamps (RL)
(4) 15-pin female connector for remote alarms (RA)
(5) 25-pin female connector for housekeeping (HK)
(6) 15-pins male connector for heaters and fans control and the thermocouples
Four output (CPO) and 8 input (CPI) contacts for housekeeping alarms or commands are physically available
on connectors placed at the top of the subrack backpanel

Issue 01
GENTRU unit
The TSS Rack may be equipped with the GENTRU Unit.

The GENTRU receives from the station:
the Station Battery power supplies (BATT)
the Service power supply (VSERV) (for future release in ANSI market)The
VSERV is delivered from GENTRU to the housed assemblies.

The Rack Lamps unit on the GENTRU Unit generates optical indications (rack lamps) and transmits remote
alarms to external sources by summing up the commands received from other NEs in the system.
The GENTRU unit provides 1+1 protection to the shelf via the following pre-mounted backup power supply
units:
GENTRU Extension Bypass
DC/DC Converter 3.5 kW Step-Up
The GENTRU Extension Bypass units work like a pass through in the range 38.4V to 58.0V for ANSI, 38.4V to
72.0V for ETSI.

Issue 01
EMI filter unit

An installation kit box is supplied. An additional external filter for ETSI 3.5 KW EMI is compliant. It is
mounted on the top of the GENTRU. One filter is needed for each couple of step-ups. Rack occupation is
about 20 cm in height. The filter can be mounted on either of the following:
• Inside the ETSI rack, between the top of the rack and the GENTRU.
• Above the ETSI rack, using the GENTRU EMI filter Rack Extension, so increasing the overall rack height
from 2.2 m to 2.6 m.

Issue 01
3.5 KW STEPUP unit
Output Voltage Test Point (-58/-65 VDC)
Red LED: ON in presence

of an unit alarm
Green LED: ON in Normal
Output Voltage condition
ON/OFF manual switch

It is important to note that the STEPUP unit always works in pairs (one powered from battery A and the
other one powered from battery B); it is not possible to have only one STEPUP unit.
The power is supplied to the unit by means of a Manual ON/OFF Switch when the lever is high.
Input circuits protect against reverse voltage, under voltage, and over voltage (reversible type).
A fuse on the negative input protects against overload protection.
The 3.5 kW STEPUP is a DC/DC converter. It behaves as follows depending on whether ANSI or ETSI standard
is used:
ANSI standard: regulates the output voltage at 58 VDC with the input voltage in the range between 38.4
VDC and 58VDC. When input voltage is greater than 58 VDC and less (or equal) than 72VDC, the device
works like a pass through (the internal switching circuit turns off and the output wires are connected
directly with the input side).
ETSI standard: when the input voltage is between 38.4 VDC and 65 VDC, it is able to adjust the output
voltage at 65 VDC (the internal switching circuit works as a step-up converter to generate the 65 V at
the output side). When the input voltage is greater than 65 VDC and less (or equal) than 72 VDC, the
device works like a pass through (the internal switching circuit turns off work and the output wires are
connected directly with the input side);
LEDs on the STEPUP unit are as follows:
Green LED ON in normal output voltage condition
Red LED ON when the unit is in alarm
The STEPUP unit is equipped with an internal fan for air flow from the front to top of the unit.
The following unit alarms are detected and reported by the SETUP unit:
FANOFF = detection of faulty fan. Both green and red LEDs are ON.
UNDERVOLTAGE OUTPUT ALARM = detection of output voltage. This is referred to Vnom and is from -
10% to -20% less than the expected voltage. This alarm is not active when the input undervoltage alarm
is present. Green LED is off; red LED is ON.
INTERNAL ALARM = detection of an overvoltage or overtemperature. Green LED is off; red LED is ON.
INPUT UNDERVOLTAGE ALARM = detection of an undervoltage threshold of the incoming voltage that is
incompliant with European and American standards. Green LED is off; red LED is ON.
Issue 01
BYPASS unit
(1) Manual Switch ON/OFF Fusebreaker

(2) Fusebreaker Switch OFF access
(3) Turned OFF symbol
(4) Turned ON symbol

The Extension-Bypass works like a pass through in the range from 38.4 V to 72 V but with two breaker fuses,
not one, installed inside the group. The two distributed lines are protected by two fuse-breaker that have
a maximum capacity of 40 A.
The power delivered at the output side is about 1.2 kW.
It is important to note that the extension bypass always works in pairs (one powered from battery A and the
other from battery B); it is not possible to have only one extension bypass.
The following are the components and symbols found on the front cover panel:
Two manual vertical lever type ON/OFF fuse breakers located on the negative line. The switch is ON
when the switch lever is up.
A DC/DC symbol in the top right corner –An ON/OFF symbol near the switches
Two connectors on the upper cover panel deliver the main power supply voltage (48V/60V) to the housed
assemblies/equipment.

Issue 01
Rack lamp unit
RJ45 connector for Extension Remote Alarm

Turned OFF symbol
ON/OFF manual switch – Fusebreaker
Turned ON symbol
Green LED - BUZ: indicates the presence of the

Service Call or Service Battery
Red LED - URG: indicates the presence of an
Urgent Alarm
yellow LED - MEM: indicates the storing of an
alarm
Red LED - NURG: indicates the presence of an
Non Urgent Alarm
The LAMP GROUP manages the alarms of the installed system.

This unit can be considered an interface between signals coming from the apparatus in the bayframe/rack
and the LED lighting/outgoing alarms.
The following are the components and symbols that are visible on the front cover panel of the 1850 TSS:
a) One green LED that indicates the presence of the service call or service battery
b) One red LED that indicates the presence of an urgent alarm (Major)
c) One red LED that indicates the presence of a not urgent alarm (Minor)
d) One yellow LED that indicates the storing of an alarm
e) A manual vertical lever type ON/OFF fuse-breaker located on the negative input. The switch is ON
when the lever is on.
f) An Interface connector for extension alarm.
g) An ON/OFF symbol near the switch.

Issue 01
Subrack ID connector (TSS-320 only)
It is necessary to plug the module onto the backplane subrack ID

connector.
Adjust the rotary switches according the equipment hierarchy, as
referred in the following table


Issue 01
Subrack ID connector (TSS-160 only)
These connections are made using a rotary switches for Shelf identifier
Adjust the rotary switches according the equipment hierarchy, as
referred in the following table
Rotary Switches


Issue 01
Equipment front view (TSS-320)
10 11
POW/PSF
FLC + HDD
Mat + SLC + CRU (copy A)
Mat + SLC + CRU (copy B)

Empty slot
Empty slot
POW/PSF
42 T-BUS 43 T-BUS


Issue 01
Equipment front view (TSS-160)
39


Issue 01
Termination Bus
ACRONYM SLOT AID
TBUS320 (x2), TBUS160 (x1) 42-43 TBUS
1850TSS-160 TSS-160
42/43
T-BUS
1850TSS-320
42 43 TSS-320
The T-BUS provides electrical termination to buses routed on the backplane of the rear-access shelf.
The TBUS provides the LCI interface
The TBUS terminates the following signal buses of the rear-access 1850 TSS-100 shelf backplane:
ISPBA / ISPBC
HWCFGA / HWCFGB
SYT1T2
Termination is required at each end for all buses; two TBUSs are required in a shelf to provide this double
termination. In addition, an LCI interface is supported. The LCI interface is the serial link between the
EC100 and a serial non-volatile memory (EEPROM) where the equipment local configuration and the MAC
address data are stored
T-BUS plugs into the rear of the backplane, just above the Common Part Interface (CPI)
In the TSS-100 are presents two T-BUS for shelf and both are mandatory

Issue 01
1 Hardware Architecture
Card size (TSS-320)

The 43 slots in a 1850 TSS-320 shelf are made up as follows:

32 are Port slots
2 are Matrix slots
5 are common part and control slots
2 are FANs and 2 are Bus Termination (hidden)

Issue 01
1 Hardware Architecture
Card size (TSS-160)
Half slot (½) card for SDH

Full slot card for Data and and D-WDM application
D-WDM application

The 25 slots in a 1850 TSS-160 shelf are made up as follows:

16 are Port slots
2 are Matrix slots
5 are common part and control slots
2 are FANs and 2 are Bus Termination (hidden)

Issue 01
Equipment controller
ACRONYM SLOTS EPS

• 1+1
EC320 1, 20 • not revertive
Reset
command key
10/100 Eth debug
RJ45 connector
RS232 on mUSB
DEBUG connector
1850TSS-320
1850TSS-160
1 M 20 S
1
M
20 USB interface
S for external
memory device
Alarm cut–off key
Lamp test key

The EC320 provides the following functionalities:

Physical layer interface for the different serial communication channels supported by the EC function
Station alarm signaling interfaces (Rack Lamp, Remote Alarms and Housekeeping)
Mass storage device for NE database
Board and system identification number
Unit’s power supply
Multi HDLC controller for ECC termination (DCC)
Remote inventory function
Microprocessor (CPU)
System memory (Boot Flash EPROM, RAM)

Issue 01
Matrix (TSS-320)
ACRONYM SLOTS EPS
• 1+1
MT320 • not revertive
10 , 11
MT320LO
SLC restart
command key
mUSB and RJ45
DEBUG connectors
HO
LO: 40Gb/s
CxC
1850TSS-320
Q3
S Acronym Slots
M MT320
10,11 I/F for CT (fixed IP: 10.0.0.1)
MT320LO
10 11
Internal LAN (Drop Shelf)
HO & LO Internal LAN (Drop Shelf)

CxC

The Universal Matrix unit provides SONET/SDH and agnostic data flows switching capabilities on the 1850
TSS-320 equipments.. The unit performs the following functionalities:
Shelf Controller (SLC)
Payload Performance Monitoring
Sub-Network Connection Protection (SNCP)
Automatic Protection Switching
Central scheduler for data switch management
Synchronous clock unit (CRU)
HO Matrix
LO Matrix
The switching capacity is:
MT320 supports 320 Gbps HO switching capabilities
MT320LO supports 320 Gbps HO and 40 Gbps LO switching capabilities

Issue 01
Matrix (TSS-160)
ACRONYM SLOTS
EPS
MT160 • 1+1
10 , 11 • not revertive
MT160LO
SLC restart
command key
mUSB and RJ45
DEBUG connectors
HO
CxC
LO: 20Gb/s 1850TSS-160
Q3
Acronym Slots
MT160 I/F for CT (fixed IP: 10.0.0.1)
11 10,11
S MT160LO
10 M
Internal LAN (Drop Shelf)
HO & LO Internal LAN (Drop Shelf)

CxC

The Universal Matrix unit provides SONET/SDH and agnostic data flows switching capabilities on the 1850
TSS-320 equipments.. The unit performs the following functionalities:
Shelf Controller (SLC)
Payload Performance Monitoring
Sub-Network Connection Protection (SNCP)
Automatic Protection Switching
Central scheduler for data switch management
Synchronous clock unit (CRU)
HO Matrix
LO Matrix
MT160 supports 160 Gbps HO switching capabilities
MT160LO supports 160 Gbps HO and 20 Gbps LO switching capabilities

Issue 01
10G lower Order Adapter board
ACRONYM SLOTS
From 21, 22, 24 (320 only)
LOA10G
From 33, 35, 36
EPS
• 2:1
• revertive
1850TSS-320
LO traffic
Protection Protection
group group MT320LO: 40Gb/s
M S S M
LOA: 10Gb/s
M M 4 x LOA
1850TSS-160
LO traffic
M M
MT160LO: 20Gb/s
S
LOA: 10Gb/s
Protection
group 2 x LOA

Functional Description Hardware Description-Common Section 2 - Module 1 - Page 28
Lower Order Adapter (LOA) card is needed to enable LO processing capabilities and for hosting LOA
processing parts
In the TSS-320 it adapts 10 G of HO switching to 10 G of LO switching (it provides access to 10 G of LO
switching in the Matrix). 4 working LOA (40G) may be deployed. Two hot standby spares may also be
deployed to provide 2 x 1+2 protection groups. Slot 24 protects slots 21, 22, slot 33 protects slots 35, 36.
In the TSS-160 it adapts 10 G of HO switching to 10 G of LO switching (it provides access to 10 G of LO
switching in the Matrix). 2 working LOA (20G) may be deployed. One hot standby spares may also be
deployed to provide one 1+2 protection group. Slot 33 protects slots 35, 36.

Issue 01
Power Supply (TSS-320/160)
ACRONYM SLOTS
PSF320 37 , 39
1850TSS-320
1850TSS-160

For POW320 and PSF320, that doesn't support a working/protection scheme but works in load sharing, if one
of the two available modules is not ever able to supply Power, the other one shall take 100% of the load,
whatever is the logical state of the same two boards.
This unit can be considered an interface between the input battery coming from the TOP RACK UNIT
(GENTRU) and the backplane to supply power to all the boards in the subrack.
Besides it supplies two “Auxiliary voltages”: 3.6V and 5.3V.
Each line foresees a fuse (over-voltage and over-current protection) both on positive and negative line.
Besides each line is able to monitor its own fuses and the relative alarm.
The main board of the sub-unit power supply (PSF320) performs the following fuctions:
Input filter: The EMI filter is a low pass filter on the power line that performs the following functions:
Prevents the entry of high frequency interference carried by the DC power line into the equipment
Prevents the exit of interference energy generated within the protected equipment into the DC
power line
Battery distribution and presence sensors: The main board distributes battery input to the back panel
and all the boards. Each line goes to a fuse on both the positive and the negative lines.
Battery alarms (battery missing and failure of batteries [And])
Card missing
By-pass for Access battery
Power monitoring
Timing interface: Two external reference signals are provided at 2.048 MHz or 2.048 Mb/s.

Issue 01
Power Supply (TSS-320 only)
ACRONYM SLOTS
POW320 37 , 39
1850TSS-320

Function performed:
the unit can receives up to one 2 MHz clock (T3) or up to one 2 Mbit/s signals (T6) that could be used
to synchronize the NE. The unit provide software programmability to switch between the two mode.
the unit provides up to one 2 MHz clock (T4) or up to one 2 Mbit/s signals (T5) that can be used by
another NE. for timing purpose. The unit provide software programmability to switch between the
two mode.
The correspondent physical interfaces are located on the front panel of the PSF320_A and PSF320_B
units, guaranteeing in this way the required redundancy of this functionality(T3a, T3b or T6a, T6b /
T4a,T4b or T5a,T5b).
The physical accesses and terminations of the synchronization signals are implemented on the
PSF320_A and PSF320_B units, while the frame processing (significant in case of E1) with SSM
management is realized on the Matrix units (MT320, MT160).
Spider
The daughter board of the sub-unit power supply (PSF320) performs the following fuctions:
Input power stage for DC/DC converters
DC/DC converters
Step-down

Issue 01
Fan (TSS-320)
ACRONYM SLOTS
FAN320 40 , 41
1850TSS-320
40
Dust
filter
41

In the 1850TSS-320 equipment two FAN units are mandatory.

The unit can be simply plugged into the backpanel as any other board of the 1850TSS-320, in one of the two
slots present for the purpose, at the top and the bottom of the shelf.
Fan speeds are monitored and an alarm is raised when fans revolve below 30% of their maximum speed
allowed.

Issue 01
Fan (TSS-160)
ACRONYM SLOTS
FAN160 40 , 41
40
1850TSS-160
41

In the 1850TSS-160 equipment two FAN units are

mandatory.
The 1850 TSS-160 equipment must have two FAN units
installed. As with other 1850 TSS-160 boards, this
unit can be plugged into the back panel in one of the
two designated slots, located at the top-left and at
the bottom-left of the shelf.
The FAN160 are managed and monitored by a local
microcontroller and by the Shelf Controller, via
SPIDER controlled by SC via SPI bus.
The local microcontroller provides the following
functionalities:
manages and monitors the speed of each of them
raises an alarm when the fans revolve below 30% of
their maximum allowed speed
monitors the power supplies presence (DC/DC
output voltage), the current absorption and the
ambient temperature.

Issue 01
Mechanical adapters
Board Adapter
1P10GSO (STM-64) HSLAD
4P2G5SO (STM-16) HSLAD Special mechanical parts called
8PSO (STM-1/4) HSLAD
“Adapters” are used to separate a Full
slot into Half or Normal ones.
LOA10G (LO adapter) HSLAD
1POTU2 (DWDM line card) HSLAD
10XANY (Data/TDM concentrator) HSLAD Three types of mechanical adapters
DWLA10X (Transponder 10G) HSLAD
exist:
CMDX8 (8 ch mux) SSLAD HSLAD (Half SLot ADapter) enables
CMDX8S (8 ch mux) SSLAD
to use Half boards (SDH boards)
CMDX2S (2 ch mux) SSLAD
CMDX1S (1 ch mux) SSLAD SSLAD (Single SLot ADapter) (320
CADM4 (4 ch oadm) DSLAD only) enables to use Normal boards
CADM4S (4 ch oadm) DSLAD
(WDM boards except CADM4)
CADM2 (2 ch oadm) SSLAD
CADM2S (2 ch oadm) SSLAD DSLAD (Double SLot ADapter) (320
CADM1 (1 ch oadm) SSLAD only) enables to use Normal
CADM1S (1 ch oadm) SSLAD Double boards (CADM4 boards)
CWLA3OP (transponder) SSLAD
CWLA3 (transponder) SSLAD


Issue 01
Mechanical adapters [cont.]
ACRONYM SLOTS ACRONYM SLOTS

6 , 7 , 8 , 9, 6+7
SSLAD
12 , 13 ,14 , 15 8+9
DSLAD
12+13
14+15
ACRONYM SLOTS
HSLAD All slots


Issue 01
Blank Page


Issue 01
End of Module
Hardware Description-Common


Issue 01
22
Section 2
Module 2
Hardware Description-SDH
Edition 01
All Rights Reserved © 2007, Alcatel-Lucent

Edition 01
Blank Page

Functional Description Hardware Description-SDH
Document History

Edition 01
Objectives
Describe the SDH boards of the 1850TSS-320 /160


Edition 01
Blank Page


This page is leftEdition
blank01intentionally
Table of Contents
Page
1 Hardware Description - SDH 7
2 Examples of shelf configuration: SDH 19


Edition 01
Blank Page


This page is leftEdition
blank01intentionally
1 Hardware Description - SDH

Functional Description Hardware Description-SDH Section 2 Module 2 Page 7

Edition 01
1 Hardware Description – SDH
1 x 10Gbps board
ACRONYM SLOTS
Max interfaces
From 2 to 9 (320 only) 1850TSS-320: 32 x 1 = 32
From 12 to 19 1850TSS-160: 16 x 1 = 16
1P10GSO
From 21 to 28 (320 only)
From 29 to 36
1850TSS-320
1850TSS-160 1 x XFP

Functional Description Hardware Description-SDH Section 2 - Module 2 - Page 8
1P10GSO board provides bi-directional processing of one STM-64 signal.

1P10GSO board is an Half slot unit.
On the front panel are available:
An embedded slot for XFP optical transceiver
A multicolor LED as visual card status indicator (card failure, in service,….)
A push button for Manual Laser Restart
Unit is able to provide Optical Safety support by means of an Automatic Laser Shutdown (ALS) procedure.
XL-642C is the acronym of the DWDM modules. For each channel is foreseen a different module.
Channels of the L1 band:
Wavelength central frequency
channel
(nm) (GHz)
1553.33 30 193.0
1552.52 31 193.1
1551.72 32 193.2
1550.92 33 193.3
1549.32 35 193.5
1548.51 36 193.6
1547.72 37 193.7
1546.92 38 193.8

Edition 01
4 x 2.5Gbps board
ACRONYM SLOTS Max interfaces

1850TSS-320: 32 x 4 = 128
1850TSS-160: 16 x 4 = 64
From 12 to 19
4P2G5SO
From 29 to 36
1850TSS-320 4 x SFP
1850TSS-160

4P2G5SO board provides bi-directional processing of (up to) four STM-16 signals.
4P2G5SO board is an Half slot unit.
Four embedded slots for optical line access via SFP optical transceivers
The unit will be used in conjunction with four SFP optical Transceivers as an Optical Line Interface Card at
STM-4 level.
This unit is able to provide Optical Safety support by means of an Automatic Laser Shutdown (ALS)
procedure.
SS-161AR is the multirate module able to support the bit rates from 100Mbps through 2700Mbps.
SS-162C and SL-162C are the acronyms of the CWDM modules. For each channel is foreseen a different
module.
Wavelength
channel
(nm)
1471 47
1491 49
1511 51
1531 53
1551 55
1571 57
1591 59
1611 61
Edition 01
8 x 155/622 Mbps board

1850TSS-320: 32 x 8 = 256
From 2 to 9 (320 only) 1850TSS-160: 16 x 8 = 128
From 12 to 19
8PSO
From 29 to 36
1850TSS-320
1850TSS-160 8 x SFP

8PSO board provides bi-directional processing of (up to) eight STM-1 or STM-4 signals.
8PSO board is an Half slot unit.
Eight embedded slots for optical line access via SFP optical transceivers
The unit will be used in conjunction with eight SFP optical Transceivers as an Optical Line Interface Card at
STM1/4 level.
Unit is able to provide Optical Safety support by means of an Automatic Laser Shutdown (ALS) procedure

Edition 01
8x155/622M, 4x2.5G Multirate Synch optical unit

1850TSS-320: 32 x 8 = 256
From 2 to 9 (320 only) 1850TSS-160: 16 x 8 = 128
From 12 to 19
MRSOE
From 29 to 36
1850TSS-320
1850TSS-160 8 x SFP

MRSOE unit provides bi-directional processing of:

Up to eight OC-3/STM-1 or OC-12/STM-4 signals
Up to four OC-48/STM-16 signals
The traffic configuration couldn’t exceed the maximum backplane throughput per port that is 10Gb/s
MRSOE board is an Half slot unit.
The unit provides Optical Safety support by means of an Automatic Laser Shutdown (ALS) procedure

Edition 01
8x155/622M, 4x2.5G Multirate Synch optical unit [cont]
Each board can manage the following maximum quantities of client

signals (SFPs):
Up to 8xSTM-1, STM-4
Up to 4 STM-16
Mixed configurations are allowed.

Other equipping rules:

STM-16 SFPs can be equipped only in positions 0, 2, 4, 6
STM-1, STM-4 SFPs can be equipped in any position
If STM-16 is provisioned in module n. X, the module X+1 must be empty and is not provisionable

Edition 01
1xOTU-2 PORT SLIM board
Max interfaces
ACRONYM SLOTS
1850TSS-320: 32 x 1 = 32
From 2 to 9 (320 only) 1850TSS-160: 16 x 1 = 16
1POTU2 From 12 to 19
1POTU2BX From 21 to 28 (320 only)
From 29 to 36
1850TSS-320
1850TSS-160
1. Multicolor LED
2. Duplex LC-type adapter
3. XFP module
The OTU-2 card is a 10 Gbps bidirectional unit that supports one DWDM optical interface (one optical
channel) in the 1529 nm –> 1563 nm range on a 100 GHz grid, per G.709 requirements .
The Client interface is a bidirectional back panel electrical interface on a black and white wavelength,
providing the connection to the client unit (i.e. 10xANY) via a Matrix cross-connection. The supported bit
rate is 9.95320 Gbps in UNI mode (STM–64, OC–192, 10 GB Ethernet WAN).
1xOTU2 Port provides bi-directional processing of one OTU2 signal, such as:
FEC coding/decoding
OTU2 and ODU2 overhead insertion/extraction–mapping/demapping of an OC-192/STM64 client signal
into/from an OTU2 frame structure
bi-directional processing of the OC-192/STM64 client signal, such as:
regenerator and multiplex section transport overhead insertion/extraction
payload assembly/de-assembly at STS-3c SPE/VC4 level
Loopback testing capability
1xOTU2 Port card is connected to two Matrix boards (1+1 configuration) for cross connection (HPC)
processing.
The unit provides Optical Safety support by means of a protection procedure, which is based on the trigger
signals when alarms/defects are detected and when the Automatic Laser Shutdown (ALS) command is
issued.

Edition 01
10XANY board
From 2 to 9 (320 only) 1850TSS-320: 32 x 8 = 256
From 12 to 19 1850TSS-160: 16 x 8 = 128
10XANY
From 29 to 36
1850TSS-320
1850TSS-160

The 10xANY unit is a Data/TDM concentrator which aggregates up to ten client signals (FE, GE, STM-1/4/16
SDH) into a VC4-nv (n= 1 .. 64) electrical frame, supporting VCAT/LCAS. The client signals on the front
panel (GE, STMn) can be mapped to VCAT groups or extracted to single VC4 and cross-connected to other
TDM units (e.g. OTU-2, 1P10GSO). The client signals on the same 10xANY can be cross-connected to
multiple TDM units via Matrix.
The board performs an optical to electrical conversion. The optical interfaces are the client interfaces and
the electrical interface is the back panel aggregate/multiplexed interface to the WDM unit (i.e. OTU-2)
via the Matrix, by means a cross-connection.
ll the client interfaces are external SFP pluggable modules (0 to 9 on the front plate).
Each Client interface (0 to 9 on the front plate) provides the connection to the clients by up to ten SFPs.
SFPs are optical transceivers enabling the building of a unit with a client-oriented User Interface.
The following SFP optical modules are supported on the client side:
B&W GbE–SX, GbE–LX, GbE–ZX, supporting 1.25Gbps bit rate at 850nm, 1310nm, 1550nm
B&W 100Base-Fx: 125Mbps, 2 Km reach, operating wavelength is 1310 nm
B&W S-1.1/L-1.1/L-1.2: OC-3/STM–1 (155Mbps) Short/Long reach at 1310nm and (L-1.2) 1550nm
B&W S-4.1/L-4.1/L-4.2: OC-12/STM–4 (622Mbps) Short/Long reach at 1310nm and (L-4.2) 1550nm
B&W I–16.1/S–16.1: OC-48/STM–16 (2.488Gbps) Inter–office/Short reach at 1310nm
B&W L–16.1/L–16.2: OC-48/STM–16 Long reach at 1310nm and 1550nm
B&W S-16.1: multirate/multiformat i/f (100 to 2700Mbps), 15 Km reach, 1310 nmGbE
ITU-T G.695 C8S1-1D2: multirate CWDM (2M - 2.7G), PIN detector, 40 Km, short haul, 1470 to 1610nm
ITU-T G.695 C8L1-1D2: multirate CWDM (2M - 2.7G), APD detector, 80 Km, long haul, 1470 to 1610nm
SFP electrical modules are also be supported. The client interfaces/ports are LC/PC connectors.

Edition 01
10XANY board [cont]
Mixed configurations are allowed, but with the following restrictions:

only two types of clients can be installed in each group of four clients
(0 -> 3, 4 -> 8 on the front plate). This means only SDH and GbE or GbE
and FC can be plugged in each group, but not SDH and GbE and FC
together.
STM-16 STM-1 STM-4
STM-1 STM-4
STM-16 STM-1 STM-4
STM-1 STM-4
STM-16
STM-16 STM-1 STM-4
STM-1 STM-4
STM-16 STM-1 STM-4
STM-1 STM-4

Each board can manage the following maximum quantities of client signals (SFPs):
up to 8 x (STM-1/4)
Up to 10 x 100 Base FX / GbE
up to 4 STM-16
The ten clients (SFPs) can be both electrical and optical, with the following rule:
max 4 electrical SFP modules for each 10xANY
no restrictions on optical SFP modules (up to 10 for each 10xANY, according to the bit rate)
STM-16 SFPs can be equipped only on positions 0, 2, 4, 6
STM-1, STM-4 SFPs can be equipped only on positions n. 0, 1, 2, 3, 4, 5, 6, 7
if STM-16 is provisioned in module n. X, the module X+1 must be empty and is not provisionable
GE interfaces can be hosted on any module from 0 to 9, with a max. number of 8 SFPs;
any SDH/GBE module always use N VC-4 from the 8 VC-4 dedicated to its module
GE subslots 0, 1, ...7 use only the last N VC-4 of the 8 VC-4 dedicated to its subslot
GE subslot 8 uses only the latest 7 VC-4 of the 8 VC-4 dedicated for subslot 6
GE subslot 9 uses only the latest 7 VC-4 of the 8 VC-4 dedicated for subslot 7
if subslot 6 is equipped with GE, subslot 8 cannot be provisioned with GE (and viceversa)
if subslot 7 is equipped with GE, subslot 9 cannot be provisioned with GE (and viceversa)
if subslot 6 is equipped with STM-16, then subslot 8 and 9 cannot be equipped
subslot 6 (7) can be equipped with STM-1; if equipped it uses the first 3 STS1 dedicated to subslot 6 (7).

Edition 01
XFP Modules

1850 TSS-320 & 1850 TSS-160 1850 TSS-320 & 1850 TSS-160 R 4.1 O&M Section 2 - Module 2 - Page 16
10Gbps transponder, with XFP optics on client and Line sides.

Client side, both SDH (I-64.n, S-64.nb, P1L1-2D2) and Data (10GE Base S/L/E) B&W i/f are supported, at
9.95Gbps (SDH/WAN) and 10.31Gbps (10GE LAN). Line side 10.709 Gbps and 11.096 Gbps bit rates are
supported.
Line side, the XFP-E adapter is required

Edition 01
SFP Modules: dual fiber (unidirectional) SFP module


Edition 01
SFP Modules: single fiber (bidirectional) SFP module


Edition 01
2 Examples of shelf configuration - SDH

Functional Description Hardware Description-SDH Section 2 Module 2 Page 19

Edition 01
Shelf equipped with STM-n boards (TSS-320)


Edition 01
Shelf equipped with STM-n and LOA boards (TSS-320)


Edition 01
Shelf equipped with STM-n boards (TSS-160)
MT160 copy B
MT160 copy A


Edition 01
Shelf equipped with STM-n and LOA boards (TSS-160)
MT160 copy B
MT160 copy A


Edition 01
End of Module
Hardware Description-SDH


Edition 01
23
Section 2
Module 3
Hardware Description-CWDM FOADM Optical amplifiers
Issue 01
1850 TSS-320 & 1850 TSS-160

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

Issue 01
Blank Page

Functional Description Hardware Description-CWDM FOADM Optical amplifiers
Document History

Issue 01
Objectives
Describe the DWDM and CWDM boards of the 1850TSS-320/160


Issue 01
Blank Page


Issue 01
Table of Contents
Page
1 Hardware Description - FOADM 7
2 Examples of shelf configuration - FOADM 13
3 Hardware Description - CWDM (320 only) 19
4 Examples of shelf configuration - CWDM (320 only) 35
5 Hardware Description – Optical Amplifiers 39
6 Examples of shelf configuration - Optical Amplifiers 45


Issue 01
Blank Page


Issue 01
1 Hardware Description - FOADM

1850 TSS-320 & 1850 TSS-160 1850 TSS-320 & 1850 TSS-160 R 4.1 O&M Section 2 Module 3 Page 7

Issue 01
1 Hardware Description – FOADM
8 channel DWDM Mux/Demux (L1 & L2) - OADM
LEDs
ACRONYM SLOTS 1
2
6 to 9,
OMDX8100 3
12 to 15
Out MUX monitor
In DEMUX monitor
Ch#38 (193.8THz)
Ch#37 (193.7THz)
IN Ch#36 (193.6THz)
Ch#35 (193.5THz)
Ch#33 (193.3THz)
1) MSF yellow LED: ON indicates signal failure at one or Ch#32 (193.2THz)
more of the MUX inputs Ch#31 (193.1THz)
2) DSF yellow LED: ON indicates signal failure at the Ch#30 (193.0THz)
DEMUX input (line side) OUT
Extra Port
3) Board Status multicolor LED: Line
• OFF: card plugged but not declared
• GREEN: card in service without failures
• RED: card fail, card misconfigured or card mismatch

The OMDX8100_XX is a bi-directional unit used, in ingress direction, for multiplexing on a single output port
to obtain the aggregate signal to be sent to the line. The reverse operation (demultiplexing) is provided in
egress direction.
In the ingress direction, the input signals can be:
the 8 channels of the related band (L1 or L2)
an Extra Band connected to the Extra port input (according to the configuration, it can be another
band, i.e. L2 Band, allowing MUX cascading, or the express/pass-through channels)
The unit is used in Line Terminal and OADM configurations.
When provides Line Terminal, the extra port input (MUX input, access side) is usually used to provide Mux
cascading; thus it is connected to the multiplexed output of a cascaded MUX (and viceversa).
When provides OADM, the extra port input of the MUX can be connected to the extra port output of the
DEMUX on the opposite transmission direction, and viceversa, thus allowing to pass-through the traffic
that is not added and dropped.
This unit contains a 9:1 multiplexer, @ 100GHz grid and a 1:9 demultiplexer, @ 100GHz grid.
In transmit direction, the 9:1 MUX is used to multiplex
8 optical channels, coming from eight transmitters (transponders)
the Extra Band multiplexed signal, coming from the multiplexed output of a cascaded Mux (Line
Terminal/Back to Back) or the extra output of the opposite Demux (OADM) into a single output WDM
signal to be sent to the line.
In receive direction, the 1:9 DEMUX is used to demultiplex the WDM signal into
8 optical channels outputs, further sent to the eight relative transmitters (transponders)
the Extra Band multiplexed signal, further sent to the Line/multiplexed input of a cascaded Demux
(Line-Terminal/Back to Back) or the extra input of the opposite Mux (OADM).

Issue 01
Single port 11G Pluggable OT
ACRONYM SLOTS
2 to 9 (320 only), 12 to 19
DWLA10X
21 to 28 (320 only), 29 to 36

The DWLA10X unit is a bidirectional transponder, compliant with the G.709 Rec., with one client B&W
optical interface and one colored (DWDM) optical interface, in C-Band (1546.92 nm to 1561.42 nm,
covering the L1 and L2 bands, in current release), on the 100 GHz grid.
It provides both User to Network Interface (UNI) and Network Node Interface (NNI), client side.
The main function of this board is to convert the User (B&W) optical signal into a DWDM optical signal and
viceversa. It also performs 3R and PM functions of the optical signal, for SDH/SONET and 10GE signals.
The two optical interfaces/transceivers are XFP pluggable modules so that they can be alternated according
to the different applications
The Line optical interface is the connection to the network and it is accomplished by a single coloured
wave-length on the DWDM module. Each wavelength on the line interface is then multiplexed into a single
fiber and sent to the WDM network.
The Line interface can be an XFP (using and XFP-E adapter) or an Extended XFP, APD type, tuned on a
DWDM wavelength in C-Band, @100 GHz. It supports the following interface/standard
ITU-T G.698.2 DW100U-2AXC: DWDM with APD detector, 80 km reach, operating in 3rd window.
The following bit rates are supported at the WDM Line interface (NNI):
10.709225 Gbps (OTU-2), for the 9.9532 Gbps (STM-64/OC-192/10GE WAN) client signal
11.095728 Gbps (proprietary over clocked OTU-2, to encapsulate 10 GE LAN), for the 10.3125 Gbps
(10GE LAN) client signal.
The optical receiver performs an optical-to-electrical conversion and viceversa the optical transmitter.

Issue 01
Single port 11G Pluggable OT [cont.]

The User/Client interface performs the connection to the client of the network. It is provided by an
external XFP (using XFP Adapter) or XFP-E.
XFPs are optical transceivers enabling the building of a transponder with a client oriented User Interface.
The optical receiver performs an optical-to-electrical conversion and viceversa the optical transmitter.
In accordance with the XFP plugged, the Client optical interface complies with the following standards:
ITU-T G.691 I-64.1 and G.693 VSR 2000-2R1 / GR-253-CORE SR-1 OC-192; 2 Km reach, up to 4 dB link
budget, intraoffice, operating wavelength is 1310 nm
ITU-T G.691 S-64.2b / GR-253-CORE IR-2 OC-192; 40 km reach, short haul, operating at 1565 nm
ITU-T G.959.1 P1L1-2D2 / GR-253-CORE LR2 OC-192; 80 km reach, long haul, 1565 nm
IEEE 802.3 10GBASE–S; 300 m reach, very short haul, operating wavelength is 850 nm
IEEE 802.3 10GBASE-L; 10Km reach, intraoffice, up to 9.4 dB link budget, operating at 1310nm
IEEE 802.3 10GBASE–E; 40 km reach, short haul, operating wavelength is 1565 nm.
These applications support 10 Gbps optical tributary signals.
Herebelow are listed the supported client bit rates:
9.95328 Gbps (STM-64, OC-192, 10 Gigabit Ethernet WAN) in UNI mode
10.3125 Gbps (10 GE LAN) in UNI mode
10.709 Gbps (OTU-2 - G.709) in NNI mode
11.095728 Gbps (proprietary over clocked OTU-2, to encapsulate 10 GE LAN) in NNI mode according to
the XFP plugged on client side.
NNI will be available in a coming release.

Issue 01
XFP Modules for DWLA10X
XS-642
XP1L12D2 (L-64.2)
ACRONYM Type
10GB
XI-641
B&W
XS-642
XP1L12D2
XL-642C DWDM
OR
10GB
XI-641
XS-642
XL-642C


Client side, both SDH (I-64.1, S-64.2b, P1L1-2D2) and Data (10GE Base S/L/E) B&W i/f are supported, at
supported.

Issue 01
Blank Page


Issue 01
2 Examples of shelf configuration -
FOADM


Issue 01
4 Examples of shelf configuration - FOADM
16 DWDM channels in Line Terminal configuration (TSS-320)
FOADM: 16 - channel Line Terminal

The following example is built up on two 8-channel mux/demux (OMDX8100_L1 and L2), to which can be
connected the following tributaries:
9 x DWLA10X plus 2 x P10GSO (STM-64/OC-192) with DWDM optics (XFP) plus 3 x 1POTU2 (OTU-2) plus 2
x PP10GE (10GE Packet Processor) with DWDM optics (XFP). B&W units (i.e.10xANY) can be used to
transport B&W client traffic.

Issue 01
7 channel OADM (TSS-320)
FOADM: 7 - channel OADM

The following example is built up on two 8-channel mux/demux (OMDX8100) and two optional Line
Amplifiers (LOFA111), to which can be connected the following tributaries:
x PP10GE (10GE Packet Processor) with DWDM optics (XFP), West side
x PP10GE (10GE Packet Processor) with DWDM optics (XFP), East side

Issue 01
8 channel Line Terminal (TSS-160)
FOADM: 8 - channel Line terminal


Issue 01
7 channel OADM (TSS-160)
FOADM: 6 - channel OADM

x PP10GE (10GE Packet Processor) with DWDM optics (XFP), West side

Issue 01
Blank Page


Issue 01
3 Hardware Description – CWDM (320
only)


Issue 01
3 Hardware Description – CWDM (320 only)
8 channel CWDM Mux/Demux
ACRONYM SLOTS
1
6,7,8,9,
CMDX8
12,13,14,15
Empty
Line
IN Ch#47 (1471nm)
Ch#49 (1491nm)
Ch#51 (1511nm)
Ch#53 (1531nm)
Ch#55 (1551nm)
OUT Ch#57 (1571nm)
Ch#59 (1591nm)
1) Board Status multicolor LED: Ch#61 (1611nm)

This board performs both the multiplexing and demultiplexing of 8 channels/wavelengths, 20nm spaced,
to/from a fiber, in the unidirectional application (one fiber for direction).
In TX direction, 8 input ports (CH1 IN CH8 IN) and 1 output port (LINE TX OUT) for the multiplexer, are
provided.
In RX direction, 1 input port (LINE RX OUT) and 8 output ports (CH1 OUT CH8 OUT) for the demultiplexer,
are provided.
5% of the input signal (LINE RX IN) is extracted via a 95:5 SM coupler and sent to a photodiode. It is then
amplified and compared with LOS-threshold, to perform LOS detection wavelength.

Issue 01
8 channel CWDM Mux/Demux with 1310nm channel
ACRONYM SLOTS
1
6,7,8,9,
CMDX8S
12,13,14,15
1310nm
Line
IN Ch#47 (1471nm)
Ch#49 (1491nm)
Ch#51 (1511nm)
Ch#53 (1531nm)
Ch#55 (1551nm)
OUT Ch#57 (1571nm)
Ch#59 (1591nm)
1) Board Status multicolor LED: Ch#61 (1611nm)

This board performs both the multiplexing and demultiplexing of 8 channels/wavelengths , 20 nm spaced,
to/from a fiber, in the unidirectional application (one fiber for direction). It also provides the insertion
and extraction of the 1310nm supervisory signal (OSC) or a 1310nm SDH signal.
provided.
are provided.
amplified and compared with LOS-threshold, to perform LOS detection.

Issue 01
ACRONYM SLOTS
1 Ch#1 47 51 55 59
6,7,8,9,
CMDX2S Ch#2 49 53 57 61
12,13,14,15
IN
1310nm
Line
Ch#1 (1xx1nm)
Ch#2 (1yy1nm)
OUT
1) Board Status multicolor LED:


This board performs both the multiplexing and demultiplexing of 2 channels/wavelengths, 20nm spaced,
There are four types of CMDX2S boards, each one multiplexing and demultiplexing a pair of channels. They
have the same front panel, apart from the silk-printings indicating the multiplexed/demultiplexed
channels. The CMDX2S boards are: 47 & 49 ; 51 & 53 ; 55 & 57 ; 59 & 61.
provided.
are provided.
The 1310 nm OSC (or SDH) wavelength is available on the 1310 nm IN (added signal) and 1310 nm OUT
(dropped signal) connectors.

Issue 01
47
ACRONYM SLOTS 51
1
6,7,8,9, 55
CMDX1S 59
12,13,14,15 Ch#1
49
IN 53
1310nm
57
Line
61
Ch#1 (1xx1nm)
Empty
OUT


This board performs both the multiplexing and demultiplexing of 1 channel/wavelength, 20nm spaced,
In TX direction, 1 input ports (CH1 IN) and 1 output port (LINE TX OUT) for the multiplexer, are provided
In RX direction, 1 input port (LINE RX OUT) and 1 output port (CH1 OUT) for the demultiplexer, are
provided.
The 1310 nm OSC (or SDH) wavelength is available on the 1310 nm IN (added signal) and 1310 nm OUT
(dropped signal) connectors.

Issue 01
4 channel CWDM OADM
ACRONYM SLOTS Ch#1 47 55

1
6+7; 8+9 Ch#2 49 57
CADM4
12+13; 14+15
Ch#3 51 59
Empty Ch#4 53 61
IN Empty
East Line West Line
East Ch#1 West Ch#1
East Ch#2 West Ch#2
East Ch#3 West Ch#3
East Ch#4 West Ch#4
OUT
East extra port West extra port


This board performs both the adding and the dropping of 4 channels/wavelengths for each direction (east
and west), 20nm spaced, to/from fiber, in the unidirectional application (one fiber for direction).
The added/dropped channels are to/from the transponders/colored boards. The other channels are passed
through by the board (express channels).
It is used in OADM configuration.
There are two types of CADM4 boards: one board adds and drops the four lower channels, the other one
adds and drops the four higher channels. They have the same front panel, apart from the silk-printings
indicating the added/dropped channels (47 to 53 for the lower channels board, and 55 to 61 for the
higher channels board):
47 & 49 & 51 & 53
55 & 57 & 59 & 61

Issue 01
4 channel CWDM OADM with 1310 nm channel
ACRONYM SLOTS Ch#1 47 55

1
6+7; 8+9 Ch#2 49 57
CADM4S
12+13; 14+15
Ch#3 51 59
East 1310nm Ch#4 53 61

West 1310nm
IN
East Line West Line
East Ch#1 West Ch#1
East Ch#2 West Ch#2
East Ch#3 West Ch#3
East Ch#4 West Ch#4
OUT East extra port West extra port


This board performs both the adding and dropping of 4 channels/ wavelengths for each direction (east and
west), 20nm spaced, to/from fiber, in the unidirectional application (one fiber for direction).
through by a CADM4S board (express channels).
It also provides the insertion and extraction of the 1310nm supervisory signal (OSC) or 1310nm SDH signal on
both directions (east and west).
There are two types of CADM4S boards: one board adds and drops the four lower channels, the other one
adds and drops the four higher channels. They have the same front panel, apart from the silk-printings
indicating the added/dropped channels (47 to 53 for the lower channels board, and 55 to 61 for the
higher channels board):
47 & 49 & 51 & 53
55 & 57 & 59 & 61

Issue 01
2 channel CWDM OADM
ACRONYM SLOTS
1 Ch#1 47 51 55 59
6,7,8,9,
CADM2
12,13,14,15 Ch#2 49 53 57 61
Empty
Empty
IN East Line
East Ch#1
East CH#2
East Extra Port
West Line
OUT West Ch#1
West CH#2
1) Board Status multicolor LED: West Extra Port

through by a CADM2 board (express channels).
amplified and compared with LOS-threshold, to perform LOS detection
There are four types of CADM2 boards, each one adding and dropping a pair of channels. They have the
same front panel, apart from the silk-printings indicating the added/dropped channels.
According to the board P/N, the following channels are added/dropped by each CADM2:
47 & 49
51 & 53
55 & 57
59 & 61

Issue 01
2 channel CWDM OADM with 1310nm channel
ACRONYM SLOTS
1 Ch#1 47 51 55 59
6,7,8,9,
CADM2S
12,13,14,15 Ch#2 49 53 57 61
East 1310nm
West 1310nm
IN East Line
East Ch#1
East CH#2
East Extra Port
West Line
OUT West Ch#1
West CH#2
1) Board Status multicolor LED: West Extra Port

It also provides the insertion and extraction of the 1310nm supervisory signal (OSC) or 1310nm SDH signal on
both directions (east and west).
amplified and compared with LOS-threshold, to perform LOS detection
There are four types of CADM2S boards, each one adding and dropping a pair of channels. They have the
same front panel, apart from the silk-printings indicating the added/dropped channels.
According to the board P/N, the following channels are added/dropped by each CADM2S:
47 & 49
51 & 53
55 & 57
59 & 61

Issue 01
1 channel CWDM OADM
47
ACRONYM SLOTS
51
1
6,7,8,9, 55
CADM1
12,13,14,15 59
Ch#1
49
53
Empty 57
Empty 61
IN East Line
East Ch#1
East Extra Port
West Line
West Ch#1
OUT West Extra Port


This board performs both the adding and dropping of 1 channel/wavelength per direction (east and west),
20nm spaced, to/from a fibre, in the unidirectional application (one fibre pe direction).
The added/dropped channel is to/from the colored board. The other channels are passed through by the
CADM1 board (express channels).
There are eight types of CADM1 boards, each one adding and dropping one channel. They have the same
front panel, apart from the silk-printings indicating the added/dropped channel.

Issue 01
1 channel CWDM OADM with 1310nm channel
47
ACRONYM SLOTS 51
1
6,7,8,9, 55
CADM1S 59
12,13,14,15 Ch#1
49
53
East 1310nm 57
IN West 1310nm 61
East Line
East Ch#1
East Extra Port
West Line
OUT West Ch#1
West Extra Port


This board performs both the adding and the dropping of 1 channel/wavelength for each direction (east and
west), 20nm spaced, to/from fiber, in the unidirectional application (one fiber for direction).
The added/dropped channel is to/from the transponders/colored boards. The other channels are passed
It also provides the insertion and the extraction of the 1310 nm supervisory signal (OSC) or 1310nm SDH
signal on both directions (east and west).
There are eight types of CADM1S boards, each one adding and dropping one channel. They have the same
front panel, apart from the silk-printings indicating the added/dropped channel.

Issue 01
Transponder CWLA3
LEDs
ACRONYM SLOTS 1
2
6,7,8,9,
CWLA3 3
12,13,14,15
4
5
1) Power LED:
• GREEN: the card is properly working
• RED: one of the local power supplies is in failure WDM Ch#2
2) OOS LED: ON (Yellow) when the unit is plugged but
not configured by software WDM Ch#1
3) CH1 LED: ON (Yellow) means problem on channel#1
User Ch#2
4) CH2 LED: ON (Yellow) means problem on channel#2
5) Board Status multicolor LED: User Ch#1
• GREEN: card in service
• YELLOW BLINK: firmware download state
The CWLA3 (wavelength adapter) is equipped with two multi-rate (125Mbps 2.67Gbps) transponders
supporting two CWDM optical channels (wavelengths), in the 1470nm/1610nm range, 20nm spaced.
The main function of this board is to convert (for each one of the two channels) the User B&W optical signal
into a CWDM colored optical signal and vice versa. Moreover it performs 3R function for both B&W and
CWDM sides, E-SNCP protection and performance monitoring for the 4 arms of the optical signal
simultaneously, for SDH and GbE signals.
The two B&W transceivers and the two CWDM transceivers are SFP pluggable modules so that they can be
alternated according to the different applications (100Mbps 2.67Gbps).
N.B.1: Never unplug the board when it is in firmware download state (hardware failure led is yellow
blinking). Should this occur, the board will not restart and may have to be returned for factory repair.
N.B.2: Make sure fibers are disconnected when plugging/unplugging the card.

Issue 01
Transponder CWLA3: E-SNCP
E-SNCP is not supported in current release

The E-SNCP protection is based on the “parallel transmit and best one receive” strategy at electrical level.
At the transmit side, the signal is broadcasted to the two arms of the ring and the available signal is
selected at the receive side, according to the failure conditions of the two signals. The routing is done
electrically in the 8x8 matrix.

Issue 01
SFP Modules for transponders
ACRONYM Type
STM-1: SI-11; SS-11; SL-11; SL-12
STM-4: SS-41; SL-41; SL-42
STM-16: SI-161; SS-161; SS-162; SL-161; SL-162 B&W
SS-161AR (multirate)
GbE: 1000B (SX/LX/ZX)
STM-16: SS-162C (PIN CWDM)
CWDM
SL-162C (APD CWDM)
SFP Module
Output
Input
Optical Cables

APD: Avalanche Photo Detector (photodiode technology)

Issue 01
4 Examples of shelf configuration – CWDM (320 only)
4 Examples of shelf configuration –

CWDM (320 only)


Issue 01
CWDM Line Terminal

The example is built up on the 8-channel mux/demux (CMDX8), to which are connected the following
tributaries:
1 x SDH (STM-16) board with CWDM optics plus 1 x SDH (STM-16) board with B&W optics
2 x CWLA3(OP) with CWDM optics, providing 4 CWDM transponders/channels

Issue 01
CWDM back-to-back

The example is built up on the 8-channel mux/demux (CMDX8, two boards), to which are connected the
following tributaries:
East side
1 x SDH (STM-16) board with CWDM optics
1 x SDH (STM-16) board with B&W optics
2 x CWLA3(OP) with CWDM optics
West side
1 x SDH (STM-16) board with CWDM optics
1 x SDH (STM-16) board with B&W optics
2 x CWLA3(OP) with CWDM optics

Issue 01
CWDM 4-channel OADM
west
east
The example is built up on the 4-channel OADM board (CADM4, one board), to which are connected the
following tributaries:
1 x SDH (STM-16) board with CWDM optics plus 1 x SDH (STM-16) board with B&W optics, East side
1 x SDH (STM-16) board with CWDM optics plus 1 x SDH (STM-16) board with B&W optics, West side
The SDH boards equipped with optical modules can be replaced by transponders. In this case, the MATRIX is
not involved.

Issue 01
5 Hardware Description – Optical
Amplifiers


Issue 01
5 Hardware Description – Optical Amplifiers
Line Optical Fiber Amplifier 22/9 (17 dB)
LEDs
ACRONYM SLOTS
1
6 to 9 (320 only),
LOFA1111 2
12 to 15
3
4
1) Power ON LED:
5
2) 1st stage abnormal LED :
•Input signal level below the IN signal LOS1 threshold
•Output signal level below the OUT signal LOS1 threshold IN
3) 2nd stage abnormal LED:
•Input signal level below the IN signal LOS2 threshold
•Output signal level below the OUT signal LOS2 threshold
4) SHUT DOWN indicator LED:
VOA
•Turned ON it means one or both stages shut down VOA
5) HW FAILURE LED:
•LED OFF means the board is plugged but not configured OUT
•GREEN LED means that the board is ok
•RED LED means failure due to hardware failure
•YELLOW LED means that a firmware download is being
performed. The board must not be extracted
LOFA1111 is a C-band, dual-stage, erbium doped fiber amplifier. The first stage output power is +12 dBm
max. Each unit provides up to +17 dBm second stage output power in C-band.
At the optical 1st stage input, is located a 1510 nm DEMUX, able to separate the 1510 nm supervisory
information (OSC, not provided in current release) from the aggregate/line signal to be amplified. At its
optical 2nd stage output, is located a 1510 nm MUX, able to add the 1510 nm supervisory information
(OSC, not provided in current release) to the aggregate/line signal sent to the line.
LOFA1111 have two possible configurations: Unidirectional (also named horizontal mode) or Bidirectional
(also named vertical mode). In current release, only the Bidirectional configuration is supported.
This unit contains an internal tunable attenuator (VOA) in order to optimize the gain flatness during the life
of the system and to avoid Non-linear effects in DCF that can fill the interstage. This is true if the
LOFA1111 is in Unidirectional configuration, not in the case of Bidirectional configuration. Because in
Bidirectional configuration the floating VOA is before the first stage for maintain the loss variation of the
span fiber during the life (ageing).This VOA is floating: it is accessed via front panel and can be used or
not, depending on the system configuration.
LOFA1111 units are capable:
to tune automatically the VOA and the 1st stage output power. The dedicated mechanisms are
embedded inside the FPGA.
to tune automatically the 1st stage and the 2nd stage output powers by keeping the gain of each stage
constant; this tuning mode is supported when the amplifier operates in unidirectional configuration as
well as in bidirectional configuration. The floating VOA is tuned by the SW, not by the unit itself
LOFA amplifiers are tunable. In fact some parameters are provisionable by the operator as output powers
(1st stage, 2nd stage...), ILOS1, OLOS1 and 2 alarms, VOA and APSD parameters
LOFA1111 is a 22/9 amplifier. This means that when the interstage is filled with 9 dB insertion losses, the
nominal gain of this EDFA unit is 22 dB.

Issue 01
Optical Amplifier 22/9 (17 dB) [cont.]

LOFA1111 can work in horizontal configuration (unidirectional) as well as in vertical configuration

(bidirectional). In this latter, it complies with the following requirements:
Bidirectional amplifier is supported in a Line Terminal or in an OADM, not in a Line Repeater
there is up to one bidirectional amplifier per side of a NE
the 1st stage receives from the line and the second one emits to the line.
By default, LOFA1111 is Bidirectional. The Unidirectional configuration is obtained by creation of the inter-
stage cable.
The VOA can be configured in two ways:
Manual mode: the operator directly provisions the VOA attenuation; the range is from 1.0 dB to 15.0 dB
in step of 0.25dB, the default value is 9dB
SAC (Span Attenuation Control) mode: the VOA attenuation is provisioned automatically by the
software.
LOFA1111 supports “Dynamic Channel Equalization”. It is the capability to provide per wavelength dynamic
power equalization when wavelengths are added, dropped, or passed thru a node, without disruption of
existing channels.
LOFA1111 in vertical configuration, can work in two modalities:
Manual mode, the output power of the first and of the second stage of the amplifier are tuned by the
operator directly configuring them
Gain (Automatic Gain Control) mode: the power of the 1° and 2° stage are regulated automatically
through algorithms controlled by software. In AGC mode, the output power of the 1° and of the 2°
stage (OP1 and OP2) is regulated keeping the gain as constant; this means that the power associated to
each transmitted lambda doesn't change respect to the number of the transmitted lambdas.

Issue 01
Booster + 10 dBm LC CH34
ACRONYM SLOTS
2 to 9 (320 only), 12 to 19
BOOST10G
21 to 28 (320 only), 29 to 36
OUT
(1) multi-color LED indicating Unit Status:

GREEN: Card provisioned and properly working
RED: Card fail
ORANGE: FPGA download, the unit has being configured
IN
(2) yellow LED indicating Laser Status:
OFF: Laser ON (OK)
YELLOW: Laser OFF (Laser shutdown)
(3) optical output signal (amplified TX signal), LC connector
(4) optical input signal (RX signal), LC connector

The BOOST10G unit provides optical amplification for one channel (CH 34, 193.400 THz) for Ultra Long Haul
applications (used in conjunction with the Preamplifier, as shown herebelow). It is connected to the
transmit side of any 10 Gbps Transponder or SDH/Data unit, to get longer span by increasing link budget.
This unit provides +10 dBm optical output power.The optical signal received from the 1850 TSS unit, is
amplified and then transmitted to the line. The interconnection between the transponder/port and the
booster, is performed on the front panel connectors (LC type) via optical cables.
The Booster can be used toghether with the Pre-amplifier, as shown herebelow, so providing Ultra Long
Links with the following main features:
Span Budget : 33 dB to 44 dB, Max Link Length: 160 km
Max Chromatic Dispersion: 3200 ps/nm
Max Chromatic Dispersion @ 1550.116 nm: 18.3 ps/nm.

Issue 01
Preamplifier 10GB/s LC CH34
ACRONYM SLOTS
2 to 9 (320 only), 12 to 19
PRE10G
21 to 28 (320 only), 29 to 36
OUT
(1) multi-color LED indicating Unit Status:

GREEN: Card provisioned and properly working
RED: Card fail
ORANGE: FPGA download, the unit has being configured
IN
(2) yellow LED indicating Laser Status:
OFF: Laser ON (OK)
YELLOW: Laser OFF (Laser shutdown)
(3) optical output signal (amplified TX signal), LC connector
(4) optical input signal (RX signal), LC connector

The PRE10G unit provides optical amplification for one channel (CH 34, 193.400 THz) for:
Ultra Long Haul applications, if used in conjunction with the Booster
Very Long Haul applications, if used without the Booster.
It is connected to the receive side of any 10 Gbps Transponder or SDH/Data unit, to get longer span by
increasing link budget.
This unit provides -7 dBm optical output power.
The optical signal received from the line/Mux/Demux, is amplified and then transmitted to the 1850 TSS
unit.The interconnection between the transponder/port and the preamplifier, is performed on the front
panel connectors (LC type) via optical cables.
The Preamplifier can be used toghether with the Booster, so providing Ultra Long Links with the following
main features:
The Preamplifier can also be used without the Booster, so providing Very Long Links with the following main
features (according to ITUT-G.691):
Min Chromatic Dispersion @ 1550.116 nm: 18.3 ps/nm.

Issue 01
Blank Page


Issue 01
6 Examples of shelf configuration –
Optical Amplifiers


Issue 01
6 Examples of shelf configuration – Optical Amplifiers
7- channel OADM (TSS320)

4 x DWLA10X plus 1 x P10GSO (STM-64) with DWDM optics (XFP) plus 1 x 1POTU2 (OTU-2) plus 1 x
PP10GE (10GE Packet Processor) with DWDM optics (XFP), West side

Issue 01
6 Examples of shelf configuration – Optical Amplifiers
8- channel Line Terminal (TSS160)

The following example is built up on the 8-channel mux/demux (OMDX8100) and one optional Line Amplifier
(LOFA111), to which can be connected the following tributaries:
4 x DWLA10X plus 1 x P10GSO (STM-64) with DWDM optics (XFP) plus 1 x 1POTU2 (OTU-2) plus 2 x
PP10GE (10GE Packet Processor) with DWDM optics (XFP).

Issue 01
End of Module
Hardware Description-CWDM FOADM Optical amplifiers


Issue 01
24
Section 2
Module 4
Hardware Description-Data
Issue 01
1850 TSS-320 & 1850 TSS-160

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

Issue 01
Blank Page

Functional Description Hardware Description-Data
Document History

Issue 01
Objectives
Describe the Data boards of the 1850TSS-320 and 1850TSS-160


Issue 01
Blank Page


Issue 01
Table of Contents
Page
1 Hardware Description - DATA 7
2 Examples of shelf configuration: Data 19


Issue 01
Blank Page


Issue 01
1 Hardware Description - DATA

Functional Description Hardware Description-Data Section 2 Module 4 Page 7

Issue 01
1 Hardware Description – DATA
1 x 10 Gbe board
ACRONYM SLOTS PP10GE PP10GEX2
PP10GE PP10GESY
2,3,4,5,6,7,8,9 (320 only)
PP10GESY
12,13,14,15,16,17,18,19
PP10GEX2
PP10GEx2 Packet Module cards provides the following additional

capability respect to PP10GE and PP10GESY data boards:
•Ethernet loopback facility (with both options of line and
internal loopback);
•Unidirectional line management;
•100FX SFP support;
•Port Mirroring;
•1588v2 Transparent Clock implementation on MAC level;
Port Mirroring is supported for the HW part only (not actually
SW implementation)

Functional Description Hardware Description-Data Section 2 - Module 4 - Page 8
The PP10GE unit is a Layer 2 Packet Processor, able to collect & switch packets coming from one 10 GE XFP-
Extended module or XFP module with special adapter placed on the front panel. It supports Ethernet
service emulation over a T-MPLS transport network (PWE3 encapsulation) and enhanced QoS (8 CoS
mapped onto 8 queues..).
The total processing power is 10 Gbps. The over subscribed bandwidth is discarded.
The unit provides the following main features:
supporting of L2 Ethernet services (EPL, EVPL and EPVLAN service delivery model) over T-MPLS
packet processing, performed via:
Classification (MAC address/VLAN/Prio, MPLS Stack entries)
Metering, Policing and Marking (IETF and MEF compliant)
Encapsulation (IEEE 802.1Q, IEEE 802.1ad, MPLS label push/pop/swap)
traffic management, able to support:
Queue scheduling discipline based on Strict Priority and Weighted Fair Queuing methods
8 forwarding classes mapped onto 8 queues: Guaranteed classes associated to real time applications
which requires very low delay, jitter and loss; Regulated and Best Effort classes associated to not real
time applications and managed through 2 levels of frame drop probability
management of 10 Gb/s data traffic, full duplex, Flow control and MAC learning
supported protocols: Ethernet, MPLS.
The unit performs an optical to electrical conversion; it is provided with an electrical back panel interface
and an optical interface towards the client/line.

Issue 01
1 x 10 Gbe board [cont.]

The Client/line interface is a bidirectional optical interface and provides the connection to the
client/network. The unit supports one B&W or WDM 10GE LAN or 10GE WAN interface; it is provided by an
external XFP (using XFP Adapter) or XFP-E.
XFPs are optical transceivers enabling the building of a unit with a client-oriented optical interface.The
optical receiver performs an optical-to-electrical conversion and vice versa the optical transmitter.
According to the XFP plugged, the following interfaces/standards are supported:
IEEE 802.3 10GBASE-S; 300 m reach, very short haul, operating wavelength is 850 nm
IEEE 802.3 10GBASE-L; 10Km reach, intraoffice, up to 9.4 dB link budget, operating at 1310nm
IEEE 802.3 10GBASE-E; 40 km reach, short haul, operating wavelength is 1565 nm
ITU-T G.959.1 P1L1-2D2 / GR-253-Core LR2 OC192; 80 km reach, long haul, at 1565 nm
ITU-T G.698.2 DW100U-2AXC: DWDM with APD detector, 80 km reach, operating in 3rd window.

Issue 01
10 x 1 Gbe board
PP1GE PP1GESY PP1GEX20
ACRONYM SLOTS
PP1GE
2,3,4,5,6,7,8,9 (320 only)
PP1GESY
12,13,14,15,16,17,18,19
PP1GEX20
PP1GEx20 Packet Module cards provides the following

additional capability respect to PP1GE and PP1GESY data
boards:
•Ethernet loopback facility (with both options of line and
internal loopback);
•Unidirectional line management;
•100FX SFP support;
•Port Mirroring;
•1588v2 Transparent Clock implementation on MAC level;
Port Mirroring is supported for the HW part only (not
actually SW implementation)

The PP1GE unit is a Layer 2 Packet Processor, able to collect & switch packets coming from 10 x 1GE SFP
modules. It supports Ethernet service emulation over a T-MPLS transport network (PWE3 encapsulation)
and enhanced QoS (8 CoS mapped onto 8 queues..). The total processing power is 10 Gbps.
supporting of L2 Ethernet services (EPL, EVPL and EPVLAN service delivery model) over T-MPLS
management of 10 Gb/s data traffic, full duplex, Flow control and MAC learning
The unit performs an optical to electrical conversion; it is provided with an electrical back panel interface
and an optical interface towards the client/line.

Issue 01
10 x 1 Gbe board [cont.]

The Client/line interface is a bidirectional optical interface and provides the connection to the
client/network. The unit supports ten FE or GE interfaces; they are provided by external SFP modules.
SFPs are optical transceivers enabling the building of a unit with a client-oriented optical interface.
The optical receiver performs an optical-to-electrical conversion and vice versa the optical transmitter.
According to the SFP plugged, the following interfaces/standards are supported:
IEEE 802.3 1000Base-T: 1.25Gbps, m reach, haul, nm
IEEE 802.3 1000Base-S: 1.25Gbps, 550m (50/125µm) or 275m (62.5/125µm) reach, short haul, 850 nm
IEEE 802.3 1000Base-L: 1.25Gbps, 10 Km reach, long haul, 1310 nm
IEEE 802.3 1000Base-Z: 1.25Gbps, 80 Km reach, long haul, 1550 nm
S-16.1 (G.957) / IR-1 OC48 (GR-253-Core) multirate (100 to 2700Mbps), 15 Km reach, 1310 nm
ITU-T G.695 C8S1-1D2: multirate CWDM (2M - 2.7G), PIN detector, 40 Km, short haul, 1470 to 1610nm
ITU-T G.695 C8L1-1D2: multirate CWDM (2M - 2.7G), APD detector, 80 Km, long haul, 1470 to 1610nm

Issue 01
Multiservice EOS portless board
ACRONYM SLOTS
2,3,4,5,6,7,8,9 (320 only)
PP10MS
12,13,14,15,16,17,18,19

The Unit acts as an "edge" between TDM traffic domain and packet-based domain, allowing to transport
packet data services over SDH/SONET physical layer, supporting TDM service emulation over T-MPLS
(PWE3 encapsulation) (future release). So it performs:
data packet processing and management
the mapping of Ethernet frames over SDH/SONET via VCAT, LCAS, GFP-F (EoS), to exchange Ethernet
frames between the Ethernet Network Processor of this unit and the Universal Matrix.
It allows the “remotization” of Ethernet flows, transporting them through the SDH network, to reach
remote Ethernet equipments. Its maximum throughput is 10Gbps (STM-64).
Neither SDH nor Ethernet physical interface (electrical or optical) is equipped on the front panel. As local
access is not provided, other SDH/Ethernet cards provide data flow via matrix cross-connections, passing
through back-panel connectors.
Each unit processes up to 10 Gbps data throughput.
supporting of L2 Ethernet services (EPL, EVPL and EPVLAN service delivery model) and ATM
encapsulation over T-MPLS (future release)
supporting of VCAT, LCAS and GFP-F (as encapsulation method) for Packet/TDM mapping

Issue 01
Multiservice EOS portless board [cont.]

management of 10 Gbps data traffic, full duplex, Flow control and MAC learning

Issue 01
5G ATM gateway portless board
ACRONYM SLOTS
2,3,4,5,6,7,8,9 (320 only)
PP10GATM
12,13,14,15,16,17,18,19

The Unit acts as an "edge" between TDM traffic domain and packet-based domain, allowing to convert ATM
services over SDH/SONET physical layer, into ATM services over PWE3.
No physical interface are equipped on the front panel, other cards provide data flow via matrix cross-
connections, passing through back-panel connectors.
Each unit processes up to 5 Gbps data throughput
The “MULTISERVICE ATM” Unit address the following functional requirements, subdivided between ATM to
T-MPLS direction and viceversa:
• ATM to T-MPLS direction (from MAPPER to TRAFFIC MANAGER)
SDH termination
up to 32 ATM ports (32 VC-4 carrying ATM) supported per card; no mix of EoPW and ATMoPW
VPC/VCC to pseudo-wire mapping per port (up to 2k VPC/VCC per card)
ATM Transmission Convergence (TC) Sk functions (cell delineation)
ATM classification and forwarding
encapsulation N-to-one, no cell concatenation
queuing and QoS managed by T-MPLS layer
input policing can be performed on PW
allocation of one tunnel per physical port guarantee traffic fairness in case of congestion
VP-AIS/VC-AIS cells generation
• T-MPLS to ATM direction (from Traffic Manager to MAPPER)
scheduling at MPLS level
VP-AIS/VC-AIS cells generation for TMPLS server failure
decapsulation N-to-one, no cell concatenation, from PW
ATM Transmission Convergence (TC) So functions (rate adaptation)
Issue 01
5G ATM gateway portless board [cont.]

The unit performs traffic management, via:

Three scheduling priority levels: High, Medium and Low priority
Queue scheduling discipline based on Strict Priority (2 queues) and Weighted Fair Queuing (6 queues)
methods
Eight forwarding classes mapped onto eight queues:
1 queue Guaranteed (SP1)
1 queue Guaranteed (SP2)
6 queues Regulated and Best Effort (WFQ3 to WFQ8)
PP10GATM cards can be 1+1 EPS protected. The protection is triggered by the detected card failures, or can
be forced via manual command. The positions of the main and the spare units are:
TSS-320 working slots: 2-9, 12-18
TSS-320 protection slots: 3-9, 12-19
TSS-160 working slots: 12-18
TSS-160 protection slots:13-19
The protection/spare unit has to be plugged in an higher slot number with respect the working/main one.
So, if the working unit is inserted in slot 2, the protection/spare unit is provisioned in any slot among 3
and 19.

Issue 01
2.5G UGW portless board
ACRONYM SLOTS
2,3,4,5,6,7,8,9 (320 only)
PP2G5UGW
12,13,14,15,16,17,18,19

This multiservice card supports interworking between legacy protocols (E1 PDH) and Ethernet/T
MPLS/MPLS-TP. It can exploit up to 2.5 Gbps of matrix switching capability to process the TDM CES
protocol. No optical interfaces are available and the unit is cross-connected via Matrix with another DATA
unit, to launch the signal to the line.

Issue 01
2.5G UGW portless board [cont.]
RJ45 debug connector
µUSB RS232 debug connector


Issue 01
XFP Modules for PP10GE, PP10GESY, PP10GEX2


Client side, both SDH (I-64.1, S-64.2b, P1L1-2D2) and Data (10GE Base S/L/E) B&W i/f are supported, at
supported.

Issue 01
SFP Dual fiber for PP1GE, PP1GESY, PP1GEX20


Issue 01
SFP Single fiber for PP1GE, PP1GESY, PP1GEX20


Issue 01
2 Examples of shelf configuration - Data

Functional Description Hardware Description-Data Section 2 Module 4 Page 21

Issue 01
Shelf equipped with data (TSS-320)


Issue 01
Shelf equipped with data and SDH boards (TSS-160)
MT160 copy B
MT160 copy A


Issue 01
End of Module
Hardware Description-Data


Issue 01
25
Section 2
Module 5
Hardware Description-1662 Drop Shelf
Issue 01
1850 TSS-320 & 1850 TSS-160

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

Issue 01
Blank Page

Functional Description Hardware Description-1662 Drop Shelf
Document History

Issue 01
Objectives
Describe the 1662SMC shelf as drop shelf of TSS-320 R.4.1,

in order to have integrated PDH access available on TSS-320,
in particular for UGW (Universal Gateway) access.


Issue 01
Blank Page


Issue 01
Table of Contents
Page
1 1662SMC as Drop Shelf of TSS 160/320 7


Issue 01
Blank Page


Issue 01
1 1662SMC as Drop Shelf of TSS 160/320

Functional Description Hardware Description-1662 Drop Shelf Section 2 Module 4 Page 7

Issue 01
Introduction
The system supports management of the compound node, composed by

1850 TSS-320 or 1850 TSS-160 equipment provided with 1662SMC as
drop shelf in order to have integrated PDH access available on the main
shelf (1850 TSS-320 and TSS-160). The whole equipment (multi–shelf
configuration) is managed as a single NE, so that a single SW download
and a single alarm list is provided for the compound node.
The main target of this feature is to provide E1 physical access for UGW
CES functionalities. This requires a full inter-work between 1662SMC E1
and UGW E1. Only E1 as PDH access is supported in current release.
1662SMC shall not be visible as external network element but as
integrated shelf.
We have a single SW download, Backup&Restore, alarm list and log.
Only single 1662SMC drop shelf is managed by 1850TSS-320
The fully non−blocking matrix allows CXC of up to 96 x 96 STM−1
equivalent at High Order level and up to 64 x 64 STM−1 equivalent at
Low Order level between all traffic ports.

Functional Description Hardware Description-1662 Drop Shelf Section 2 - Module 4 - Page 8

Issue 01
The 1662SMC is equipped with the following cards:

2 x CONGISL (both mandatory), providing power supply interfaces (thus
assuring dual power, working in power sharing), and the external LAN
interface (two I/F per unit); a Shelf Identifier is plugged on the CONGISL in
slot 20 (Q2 interface)
2 x Compact ADM-4 (SYNTH-4 V2) (both mandatory), each one equipped with
2 x STM-4 SFP. SYNTH- 4 performs the following main functions: Equipment
Controller, CRU and SDH Matrix. The full non blocking matrix allows cross-
connections at HO and LO level
Up to 8 x port cards, each one providing 63 x E1 ports, organized in two fixed
3:1 EPS groups.
Up to 6 x access cards (75Ω or 120Ω), providing the line Interface;
Up to 2 x protection access cards (EPS protection)
Termination Bus; It is mandatory and is located behind the SYNTH-4 V2
A separate FAN shelf (mandatory) is mounted at the bottom of each 1662 SMC
shelf for cooling. It includes two FAN drawers and one anti-dust filter.
No plug & play available for cards equipped in the drop shelf.


Issue 01
The following figure describes how the drop shelf is connected to the
main shelf and which hardware components are involved.
The connection between 1850TSS-320 main shelf and 1662SMC drop
shelf is provided with STM-4 lines. Standard 8xSTM-1/4 card is equipped
in the main shelf without a fixed position in order to carry E1/VC-12
from 1662SMC access to TSS-320 central matrix. The STM-4 access to
the Main Shelf is also supported by a proper Port inside a 10XANY card
or inside a MultiRate card.
Slot 15
Slot 6
Slot 11 Slot 10 Slot 1 Slot 20


Issue 01
The System Synchronization is part of the 1850 TSS-160/320 Main Shelf

1662 SMC synchronization is done without special clock cable through
standard SDH interfaces by using SSM signalling.
The drop shelf can handle the Priority and Quality (SSM)
synchronization algorithms termination functionality. The
synchronization between Drop and Main shelf is done via STM-4 links
These links are MSP protected


Issue 01
1662 protection
1662SMC integrated into the compound node supports the following

protection types:
1+1 MSP (Multiplex Section Protection), single/dual-ended. 1662SMC supports
1+1 MSP as network protection. This protection is used for STM-N synchronous
interfaces only.
COMPACT ADM card protection:

Slot 6: COMPACT ADM main
Slot 15: COMPACT ADM spare.
The COMPACT ADM EPS protection is automatically presented when the
SPARE COMPACT ADM is created.
EPS for SYNTH card and MSP 1+1 are supported by the same SYNTH-4
V2: an equipment failure of SYNTH-4 V2 card shall cause both EPS
switch and MSP switch for STM-4 ports.
Operator commands work independently on those protection schemas:
for example an EPS Manual Swtich command on SYNTH card shall not
cause switch of STM4 ports.


Issue 01
1662 protection [cont.]
Low Speed (LS) port protection:
63 x 2Mb/s ports: N:1 protection (N=3), 2 fixed schemes
EPS scheme 1
Slot 2 hosts the 63xE1 access card protection/spare unit (LSPROT)
Slot 3, 4, 5host the 63xE1 access cards working units (A63E1A/B)
Slot 7 hosts the 63xE1 port card protection/spare unit (P63E1)
Slot 8, 9, 10 host the 63xE1 port cards working units (P63E1)
EPS scheme 2
slot11, 12, 13 host the 63xE1 port cards working units (P63E1)
slot 14 hosts the 63xE1 port card protection/spare unit (P63E1)
Slot 16, 17, 18 host the 63xE1 access cards working units (A63E1A/B)
slot19hoststhe63xE1accesscardprotection/spareunit (LSPROT)


Issue 01
1662 Equipping rules
The connection between 1850TSS-320 main shelf and 1662SMC drop
shelf is provided with STM-4 lines. Connection capability inside Drop
shelf is fixed, and is activated on Equipment provisioning basis. The
STM-4 #1 housed in the Synth main (slot 6) manages the 2 Mb/s traffic
card in the slots 8,9 and 10 while the STM-4 #2 housed in the Synth
main (slot 6) manages the 2 Mb/s traffic card in the slots 11, 12 and 13.
So, only the first three AU-4 of the STM-4, are used.
The CXC between the 2 Mb/s card and the STM-4 module is fixed by the
system, and also the relationship is fixed: i.e. physical port 1 of the slot
3 is associated with the TU-12 1-1-1 of the AU-4 #1 presents in the STM-
4 #1 and so on


Issue 01
1662 Equipping rules [cont.]


Issue 01
LAN management connection
The 1662SMC shelf is connected to 1850TSS-320 shelf with an internal
LAN in order to provide management access from main shelf to drop
shelf. No DCC access is provided for 1662SMC drop shelf.
No specific IP address is provided for 1662SMC drop shelf.
The matrix in the slot 10

provides the sw to the
Synth4-V2 in slot 6
while the matrix in the
slot 11 provides the
software to the Synth4-
V2 in the slot 15
In current release,
the Drop Shelf
(DS) connector #1
can not be used

Issue 01
STM-4 link connection

2 Mb/s PDH traffic is mapped into VC-12 and then multiplexed into STM-4 streams by the SYNTH-4 V2 unit.
SYNTH-4 V2 are the 1662SMC link boards (STM-4 I/O boards). They are connected with fibers to up to four
optical ports of the STM-4 I/O boards (8PSO, MRSOE, 10xANY) in the main shelf.

Issue 01
Relationship between access cards and traffic cards


Issue 01
1662 Shelf


Issue 01
Termination bus
ACRONYM SLOTS
TBUS 21,22


Issue 01
New Compact ADM 4
ACRONYM SLOTS 1662SMC

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
SYNTH4V2 6,15
1. not used
2. reset command key
3. lamp test push button
4. alarm storing push button 23
5. channel #1 - STM-4 SFP optical module
6. channel #2 - STM-4 SFP optical module.
7. Red LED - Urgent alarm (Critical or Major)
8. Red LED - Not Urgent alarm (Minor)
9. Yellow LED - Alarm storing (Attended)
10. Yellow LED - Abnormal condition
11. Yellow LED - Indicative alarm (Warning)
12. EPS LED: Green: unit is active; Orange: unit is standby
13. Status LED: Red: local unit alarm; Green: in service unit

SYNTH-4 V2 unit supports 2xSTM-4 line interfaces in one board.

Line interfaces are provided by two optical SFP modules.
The unit supports different types of SFP modules, but in this application, short haul (S-4.1) interfaces are
foreseen. The unit provides bidirectional processing of 2xSTM-4 signals.
The Equipment Controller function is only available on the SYNTH-4 V2 board in slot 1. The EC functionality
is therefore unprotected. If the board is faulty, plugged out or unreachable, communication within the
1662SMC shelf is lost. The traffic is not affected.

Issue 01
CONtrol and General I/F
1. power supply
2. housekeeping connector (FAN alarms), used ACRONYM SLOTS
only on CONGSL in slot 1
3. not used CONGISL 1,20
4. not used
5. not used
6. RJ 45 for Q3 10Base-T
7. Status LED: Red: local unit alarm; Green: in
service unit
1662SMC
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
23

1662SMC equipment can house two CONGISL, referred as CONGISL A main (slot1) and CONGISL B (slot 20).
They are not intended as main and spare: each board provides a set of functions. Both boards are
necessary to provide the complete set. CONGISL A can be used as standalone but in this case only a subset
of interfaces can be used. Next table reports the interfaces present on each board (top to bottom).

Issue 01
2 Mb/s traffic card
ACRONYM SLOTS
P63E1 7 (SP),8,9,10,11,12,13,14 (SP)
1662SMC
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
23

Up to 8 LS ports can be housed in the subrack.

The P63E1 is a bidirectional board which interfaces 63 plesiochronous 2048 kb/s signals and the STM-4
signal.

Issue 01
63 x 2 MB/s 75 Ohm and 63 x 2 MB/s 120 Ohm
ACRONYM SLOTS
A63E1A
3,4,5,16,17,18
A63E1B
1662SMC
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
23

The 63x2 Mb/s access card provides the connections from back-panel to the external line and viceversa for
63 PDH signals. According to the type of line impedance and electrical characteristics, different types of
access board are available:
A63E1A provides 75 Ohm line impedance.
A63E1B provides 120 Ohm line impedance.

Issue 01
Low speed PROTection
ACRONYM SLOTS
LPROT 2,19
1662SMC
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
23

This unit is used to do EPS protection for low speed (E1) ports. It makes the connection between the port
card and the LS protection bus if protection is requested. The LSPROT card receives the signals coming
from the port card via back-panel.

Issue 01
FAN Shelf
ACRONYM SLOTS
SRFANV2 23
1662SMC
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
1. Multicolor LED
Red: local unit alarm
Orange: temperature major than 55°C
Green: in service unit
23 2. Battery A connector
3. Battery B connector
4. Not used
5. Alarms connector (to CONGISL in slot 1)
6. Not used
The FANs shelf is composed by a mechanical structure and a back-plane. The FAN Shelf is used to prevent
high temperature inside the 1662SMC equipment. Up to four FAN units and two Metallic FAN grids can be
equipped in one FAN shelf. For the current application, only two FAN units and one metallic grid are
required.

Issue 01
SFP Dual fiber for SYNTH4-V2


Issue 01
2 Drop Shelf creation


Issue 01
Shelf creation
To create a drop shelf, select the RACK icon, and then click on Create
Shelf
1. Select the Rack
2. Click on Create Shelf
See next slide

In the “create a new Shelf” window, you have the following parameters:
Access Identifier: by means three comboboxes is possible to select the label (with associated icon) and
the number inside the rack that will be presented in the tree. The available choices are:
SHELF: This is the Alcatel-Lucent 1850 TSS-320/160 subrack and is shown in the tree area
the label will be set at SHELF-x-x
This second combobox sets the first number presented in the tree; i.e. SHELF-1-x as for the picture. It
can range from 1 to 7.
The third choice sets the second number presented in the tree; i.e. SHELF-1-1 as for the picture. It can
range from 1 to 9.
Provisioned Type: it is the type of the shelf actually provisioned. The allowable choices are:
UNVRSL320: 320 Type Shelf
UNVRSL160: 160 type Shelf
UNVRSL160C: 19” 160 type shelf
PDHACCSSHLF: ETSI 1662 - based 75 Ohm – E1 drop shelf
PDHACCSSHLF120: ETSI 1662 - based 120 Ohm - E1 drop shelf
Automatic In Service Mode: it specifies the Automatic in service mode to which the equipment is set.
The allowable choices are:
NOWAIT: a condition notifies the module is unplugged
AINS: No condition is sent due to module unplugged
Primary State: it specifies the primary state to which the equipment is set. The allowable choices are:
IS: In Service
OOS: Out Of Service

Issue 01
Shelf creation [cont.]
To work properly, Alcatel-Lucent 1662SMC shelf ID must be=2
3. Set this field = 2
4. Configure the correct Provisioned Type:

PDHACCSSHLF for 75 Ohm – E1 drop shelf
PDHACCSSHLF120 for 120 Ohm E1 drop shelf
5. Choose Shelf ID = 2
6. Choose Shelf Role = No MAIN

7. Do Save

SHELF ID: This parameter specifies, for the Shelf Types = UNVRLS320/160, a value that is equal to the
one set by the HW tool mounted on the Shelf and to set the ID of the Shelf. The allowable choices are in
the 0 to 31 range.
SHELF Role: Specifies the provisioned shelf role for UNVRLS320/160 shelf types. The allowable choices
are :
MAIN: Main Shelf of the NE
NOMAIN: Extension Shelf of the NE

Issue 01
8. Click on here to refresh the current window
The new shelf appears

in the window


Issue 01
3 1662 Equipment view


Issue 01
Equipment view


Issue 01
EPS configuration
1. Select: Protection Equipment
Protection to open the command menu
The protection scheme is automatically

created when the spare card and
This is the area relevant to 2 Mbit/s protection access card are inserted
EPS protection and declared in the NE


Issue 01
EPS commands
1. Select: Protection Equipment
Protection to open the command menu
2. Select the card where you want

applied the EPS command


Issue 01
EPS commands [cont.]
Click on Switch to Protection or Switching to

Working to perform the EPS switch
“Inhibit Switch” correspond to Lockout command
Click here to refresh the page. This command

permit you to update the EPS status


Issue 01
Blank Page


Issue 01
End of Module
Hardware Description-1662 Drop Shelf


Issue 01
31
Section 3
NE Operation
Module 1
Operator Interface-NE
Issue 01
1850 TSS-320 & 1850 TSS-160

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

Issue 01
Blank Page

NE Operation Operator Interface-NE
Document History
01 2011-12-15 Grecchi, Ilario First edition

Issue 01
Module Objectives
Upon completion of this module, you should be able to:
Describe how to configure the NE with CT port

Describe how to log on the NE
Describe how to configure the Communication parameters
Explain how to configure ALS, J0, TP threshold, Restart NE and Alarm LIst
Describe how to configure subrack & boards
Describe how to configure and manage the Equipment Protections


Issue 01
Module Objectives [cont.]


Issue 01
Table of Contents
Page
1 NE Start-up 7
2 How to log on 19
3 Xcom menu 39
3.1 NE discovery 40
3.2 DCC configuration 43
3.3 DCN Physical interface 53
3.4 IP tunnel configuration 59
3.5 NE autodiscovery 63
3.6 OSPF Area 65
3.7 Network Domain 67
3.8 TARP Management 75
3.9 NTP configuration 79
4 Configurations: ALS, AINS mode, J0, TP threshold, J1, Restart NE,
Alarm List, Housekeeping, Optical Intrusion 87
5 Configurations: shelf declaration 113
6 Configurations: boards declaration 117
7 Equipment Protections (EPS) 145


Issue 01
Table of Contents [cont.]

NE Operation Operator Interface-NE This page is left blank intentionally

Issue 01
1 NE Start-up

NE Operation Operator Interface-NE Section 3 Module 1 Page 7

Issue 01
1 NE Start-up
NE management port
Connect the LAN port of the CT to the LAN connector, as shown in

Figure, located on the MT320 or MT160 board respectively (SLC,
plugged in slot 10).

NE Operation Operator Interface-NE Section 3 - Module 1 - Page 8

Issue 01
1 NE Start-up
TL1 management
Connect the LAN port of the CT to the LAN connector, as shown in

Figure, located on the MT320 or MT160 board respectively (SLC,
plugged in slot 10).
Open Tera-Term console
1. Insert the IP address of the LAN interface
2. Select Telnet
3. Choose the 3083 TCP port
4. Click on Ok


Issue 01
1 NE Start-up
TL1 management [cont.]
5. Digit the following command:
act-user::ALCATEL:::PWD;
It’s the password of the ALCATEL user


Issue 01
1 NE Start-up
NE Login
Open a browser and enter the IP address of the TSS-320/160 ZIC Craft
Terminal (ZIC) port (10.0.0.1 and click on ENTER key). The
Authentication dialog box will be displayed on the screen. To access
the NE, the operator has to be logged to the NE. Enter User and
Password, then click on Login button.
1. Insert the IP address in the Address bar
2. Insert User and Password

and tag the Local Time box
3. Click on Login

Open the IE browser and login as:

User: admin
Password: Root1850
Local Time: if selected, enable the UTC time zone. The UTC time zone depend of the windows time setting

Issue 01
1 NE Start-up
Root Password
Root Password
1. Insert the Old password and

then the new password
2. Click on Save

Important! After the first login it is necessary to change the Password entry
This procedure allows to change the password.
1.Follow the Security User Account Change Password menu path. The Modify Password Identifier panel
will be displayed, where is shown the current User Identifier.
2.In the Old Password ID: field, enter the current password.
3.In the New Password ID: field, enter the desired password.
4.Click on Save.

Issue 01
1 NE Start-up
NE Parameter Management
NE Parameter Management
1. Insert the Region=ETSI and

the Provisioning Mode
2. Click on Save

Region : ETSI
Provisoning mode: field the type of provisoning.
– when the AUTOEQ-AUTOFC mode is selected, both the boards and facilties are automatically referred in
the three area.
– when the MANEQ-AUTOFC mode is selected, the boards can be manually selected only and the facilities
are automatically referred after the manual provisioning of the board.
After to saved you will be automatically disconnected

Issue 01
1 NE Start-up
Set Site Identifier
1. Select System Management -> DB Management -> Set Side Identifier
SET SIDE IDENTIFIER
2. Insert the New Site Identifier
3. Do Save

This option is used to set the Site Identifier (SID) code that is compared to any Target Identifier (TID) value
entered in a text field.
If lower-case characters are entered for the SID, they are converted to an upper-case character string and
stored as the SID value.
If a quoted string is entered for the SID, no case conversion is applied.
Upon completion of the option the new site identification is displayed in the response message.
The Set Site Identifier panel allows to change the Site identifier name; it contains:
Old Site Identifier: It shows the actual identifier..
New Site Identifier: It allows to entry the name of the identifier that you need to change. The Double
Quotes hyperlink allows to set the characters within enclosing double quotes. Empty double quotes (i.e.
“”) indicate a NULL string.

Issue 01
1 NE Start-up
Shelf Creation
Before to start to configure the Master shelf we have to be sure the

rotary switch is correctly inserted in the back panel port ; the setting
value for the rotary switch must be 8 1.
1. Select the Rack

3. Configure the proper equipment: UNVRSL320
for TSS-320 or UNVRSL160 for TSS-160
4. Do Save


Issue 01
1 NE Start-up
LAN Configuration
LAN address
It allows to modify the LAN address.
1.Follow the Xcom DCN Phys If LAN manag. menu path. The Customer LAN
Management panel will be displayed.
2.Enter the desired IP address in the IP address of NE: field, and the Subnet
Mask (if any). In the panel there are some other fields:
OSI Protocol (determines if the OSI Protocol will be run on the customer LAN or not),
Internet Protocol (determines if the Internet Protocol will be run on the customer
LAN or not)
OSI Area (it is possible to enter as to which OSI Area the Customer LAN belongs to)
Integrated ISIS (determines if the Integrated IS-IS Protocol will be run on the
customer LAN or not)
Proxy Address Resolution Protocol (determines if it is enabled or not)
Channel user by (determines if the customer LAN is not used or if it is used by
management plane or by control plane).
3.Click on Save.


Issue 01
1 NE Start-up
LAN Configuration [cont.]
1. Set “Y” this parameters 2. Configure the IP parameters
3. Choose “MNGPLANE”
4. Do Save

The Customer LAN Management tab displays the Customer LAN Management panel that contains the following
parameters:
OSI Protocol: Determines if the OSI Protocol will be run on the customer LAN or not. The values are:
N (OSI Protocol is disabled on the Customer LAN); Y (OSI Protocol is enabled on the Customer LAN)
Internet Protocol: Determines if the Internet Protocol will be run on the customer LAN. The values are:
N (Internet Protocol is disabled on the Customer LAN); Y (Internet Protocol is enabled on the Customer
LAN)
OSI Area: This is possible to enter as to which OSI Area the Customer LAN belongs to (“1”, if OSI was disabled
previously, previously existing value, otherwise)
Integrated ISIS: Determines if the Integrated IS-IS Protocol will be run on the customer LAN or not. The values
are:
N (Integrated IS-IS Protocol is disabled on the customer LAN), Y (Integrated IS-IS Protocol is enabled on the
customer LAN)
Proxy Address Resolution Protocol: ARP functionality works on management LAN interface of the Gateway
NE; in the IP address plane of the DCN, Remote NEs belong to same subnet of the Gateway NE, this means
that Management System sees RNEs as belonging to same lan of the Gateway. ARP requests have been sent by
Management System for IP-MAC resolution of RNE. Proxy ARP functionality shall be enabled on LAN interface
of the GNE in order to "intercept" such ARP requests destinated to RNE, answering with MAC address of
Management LAN interface.
Channel used by: determines if the customer LAN is not used or if it is used by management plane or by
control plane
IP address of NE: The IP address of the Network Element
Subnet Mask: The subnet mask of the Network Element
Gateway address: The gateway address of the Network Element
MAC address: The Media Access Control address of the Network Element
Issue 01
Blank Page


Issue 01
2 How to log on


Issue 01
2 How to log on
ZIC window opening
Enter the IP address of the shelf in the Address field (in the example
151.98.55.186) and press the “Enter” key and the “Authentication
dialog box” appears

The computer configuration to be used consists of:

CPU Pentium IV 1.7 GHz (2.8 Ghz suggested)
RAM 1 Gb, (2 Gb suggested)
HDD free space 400 Mb
MONITOR 15" (20" suggested)
RESOLUTION 1024 x 768 pixel (1280 x 1024 suggested)
CD-Rom drive
The following software items are required as alternative:

Internet Explorer 6.0 / 7.0
Mozilla Firefox 3.0
Operating System (Windows XP)
In order to manage multiple Tabs in Internet Explorer 7, it is necessary to increase the number of files that
the user can download, at one time it is 8.
The following steps are required to be performed:
Start Registry Editor (Windows)
Locate the following key in the registry
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet settings
In the Edit menu, click New, click DWORD value, and add the followin gregistry values:
Value name - MaxConnectionsPer1_0Server
Value data-8
Base – Decimal
Value name – Max Connections Per Server
Base – 8
Exit registry editor

Issue 01
2 How to log on
NES window opening
1. Insert the User and password
2. Click on Login

The Authentication dialog box contains the following fields:

User Identifier specifies a unique user ID. According to the specification. It is a sequence from 5 to 12
case-sensitive alphanumeric characters, where the first character must always be an alphabetic
character. The following special characters are also accepted as valid characters and will be part of
the User Identifier: % (percent sign), + (plussign), # (pound sign), and _ (under score).
Password specifies the user's login password. According to the specification, it is a sequence from 8
to 12 case-sensitive alphanumeric characters. The Password must contain at least 1 upper alphabetic
character, at least 1 lower alphabetic character and at least 1 numeric character. The following
special characters are also accepted as valid characters and can be part of the Password: % (percent
sign), + (plus sign), # (pound sign), and _ (under score). The first character of the Password can be an
alphabetic, numeric, or a valid special character.
Language is one of available languages of the manager.
The default Login and Password are the following:

Issue 01
2 How to log on
General Introduction
The browser window opening at the start up of a ZIC application

includes three main object:
The menu toolbar in the upper side of the window
The tree view of the equipment, at the left hand side of the window
The main page with all the controls for the management of the system
The alarm section at the bottom of the main page, listing the current
reported alarms present in the system


Issue 01
2 How to log on
General Introduction [cont.]
Menu bar
Client area
Tree area
Alarm counter
The “menu toolbar” provide with a set of tools needed to configure the system
This is the page where the configuration controls are located
The Client area is the area in which you work, i.e. select from combobox and act on hyperlink.
A tree area is generally a part of a page that enables the operator to consult and select items from an
existing list.

Issue 01
2 How to log on
Symbols and icons
The tree presents some icons in order to resume the associated functions.
Symbol/Icon Description
Node
This icon is usually provided with a ball icon which identifies the
status (red, yellow or green) and the node ID name. The browser
“Equipment”tab allows to show also the composition
LAG (Link Aggregation Group)
Icon for logical data resources. Greyed icon means not provided.


Issue 01
2 How to log on
Symbols and icons [cont.]
Rack
This icon represents the rack that is identified by a number
(e.g., “1”). It can houses one or more shelf (more than one rack
is possible). The browser “Equipment” tab allows to show also
the composition
Shelf
This icon represents the shelf; it is identified by the rack number
the relevant shelf number and the type of configuration (e.g.
“SHELF-1-1-SWTCH”, “SHELF-1-1”). The browser “Equipment”
tab allows to show also the composition
Module
Usually associated to the SFP/XFP, a symbol which identify the
carried signal. Greyed icon means not provisioned


Issue 01
2 How to log on
Symbols and icons [cont.]
Unit/card/pack
Each unit/card/pack is identified by a label that identifies the
type of unit/card/pack (e.g., “EC320”) and a number associated
to the rack and shelf (e.g., “-1-1-1”).
If a slot is free the label is “MDL-1-1-3” (MoDuLe-rack-1, shelf-1,
position-3).
The color identifies the relevant status
green provisioned and in-service.
red and grey provisioned and out-of-service or equipment
mismatch (MEA in the secondary state)
grey not provisioned.
Ethernet interface
The symbol identifies the ETS (blue colour) and ETB (orange
color) physical interface (e.g., DATA-1-1-7-2-1). Greyed icon
means not provisioned

This icon means that the object

is decleared but not present

is decleared and present

is not properly decleared

Issue 01
2 How to log on
Tree area
This view presents in a hierarchical view the objects a system is

composed of the following items:
The node
The rack
The shelf
The boards
The modules (if any)
The ports

At the left hand side of any of the objects above, if lower level objects are present in the hierarchical
view, a squared “+” is present, to expand the view to the lower level.
This view is automatically refreshed in case of modifications

Issue 01
2 How to log on
Tree area [cont.]
Selecting one of the objects in the tree area, its detailed configuration
information is displayed.


Issue 01
2 How to log on
NE configuration page
This option displays all VCG

resources types

The Restart panel resets the specified equipment entity by means of the following fields:
Access Identifier: It specifies the equipment entity.
Phase: It allows to select the type of restart. The allowable values are:
COLD: reload of dynamic and static data (db and sw). It is supported by MT320, EC320, IOC. It is used
with AID = ALL for normal full reset of the NE (cold restart of EC320 followed by cold restart of
MT320).
POWER-ON: full restart (as if unplugged and plugged), including processor restart and reloading sw
and db. It is supported by MT320. It is used with AID=ALL for power-on full reset of the NE (cold
restart of EC320, power-on restart of MT320, cold restart of IOCs).
Command Mode: It allows to select the Command Execution Mode. The allowable values is:
FRCD Forced, the command is completed even if the result of its execution is service-affecting.
The panel has the Save hyperlink which restart the selected item.

Issue 01
2 How to log on
Rack view

The Rack x tab displays the Rack-x panel and a table that contains the following parameters. The table
displays the following details relevant to the rack:
Shelf: This column lists all the available shelf/shelves of the rack.
Resource. In this column is specified the access identifier of the shelf/shelves (type and position). It is
also shown in the tree. The values are:
UNVRSL320/UNVRSL160
PST: Specifies the primary state of the shelf.
Provisioned: Specifies the name of the shelf. It is also shown in the tree.
Actual: Specifies the physically equipped shelf type.

Issue 01
2 How to log on
Shelf view

In the Shelf configuration page, the upper part is similar to the three previous one, but the resource list is
more detailed, as it includes all the boards (not the modules, as the latter are two levels lower than the
subrack) of the subrack
In the upper part of the page there are some tabs (alarms, equipment and Shelf x-x). Clicking on the
equipment tab the client area shows the actual shelf layout.
If a board is not declared, the selection of the “provision” option leads to the releated configuration page
The UP Rack x Shelf x panel resumes the shelf info and displays the following read-only fields:
Access Identifier: Specifies the equipment entity.
Current Provisioned Type: It specifies the equipment entity.
Actual Type: It specifies the physically equipped entity type (see Current Provisioned Type).
Primary/secondary state: It specifies the primary and secondary service state.
Shelf ID: Specifies, for the Shelf Types (UNVRL320/UNVRL160), the provisioned shelf identification
value. It can range from 1-31.
Shelf Role. Specifies, for the Shelf Types (UNVRL320/UNVRL160), the provisioned shelf role. The value
can be:
MAIN (main shelf of the NE)
NOMAIN (extension shelf of the NE).
Shelf WDM Role: It specifies, for the Shelf Types (SWTCH, ROADM, UROADM, ILA and UILA), the
provisioned shelf WDM role. The value can be: WDMMASTER (master shelf of the WDM set of shelves in
NE) or WDMSLAVE (slave shelf of the WDM set of shelves in NE).

Issue 01
2 How to log on
Shelf view [cont.]
This option displays the total and

free VC4 resources

The Restart panel resets the specified equipment entity and displays the following fields:
Phase: Allows to select the type of restart. The values are:
COLD: Reload of dynamic and static data (db and sw). It is supported by MT320, EC320, IOC. It is used
with AID = ALL for normal full reset of the NE (cold restart of EC320 followed by cold restart of
MT320).
Command Mode: Allows to select the Command Execution Mode. The values are:
NORM: Normal, the command is denied if the result of its execution is service-affecting.
FRCD: Forced, the command is completed even if the result of its execution is service-affecting.
The Alarms panel displays the list of alarms associated with the shelf.
The Conditions panel displays the list of alarms associated with the shelf.
The Lower Order Pool Information panel displays the Lower Order Pool Access Identifier.
The table contains the details relevant to the shelf:–Board This column lists all the shelf slots. –Resource In
this column is specified the access identifier of the shelf/shelves (type and position). It is also shown in
the tree.

Issue 01
2 How to log on
Shelf view: graphical view
1. Select the equipment tab


Issue 01
2 How to log on
Shelf view: graphical view (options)
1. Select the equipment tab
2. Select the port

2. Select the board
Port selection
Board selection


Issue 01
2 How to log on
Shelf view: graphical view (options in the SFP)
Used to modify the SFP parameters
Used to set Out Of service the SFP
Used to retrieve the SFP information
Used to retrieve DDM information


Issue 01
2 How to log on
Shelf view: graphical view (options in the board: matrix)
Used to modify the matrix type
Used to retrieve the

Matrix information
Used to retrieve the Link Matrix Status
Used to reset the Shelf Controller


Issue 01
2 How to log on
Network Element menu
1. Select System Management -> DB Management -> Remote File -> Network Element

The Network element panel contains a table which resumes:

Access Identifier: It identifies the entity for which the output data are retrieved. Possible values are:
ACTSW (The active software generic on the NE)
STBYSW (The standby software generic on the NE).
Matrix Size: It identifies the maximum matrix size in terms of bandwidth switching capacity in Gb/s
(i.e. 320 for 1850 TSS-320).
Node Type: It identifies the role of the NE. Possible values are: UNVRSL320 or UNVRSL160
Provisioning Mode: Specifies the provisioning mode
Region: Specifies the region
Release Date: It identifies the date of the system software release in the format of <YY>-<MM>-<DD>.
Release Identification: It identifies the release ID of the system software. Possible value combination
are {E, F, R, P}{00-99}.{00-99}.{00-99}
System Restart Process Status: It identifies the status of any system restart process. Possible values
are:
COMPLETE
IN-PROGRESS
System Type: It identifies the system type (i.e. 1850 TSS-320)

Issue 01
Blank Page


Issue 01
3 Communication menu


Issue 01
3.1 NE discovery


Issue 01
3.1 NE discovery
Local address window
This option is used to retrieve the system's output response (site)

header. Normally, the output response header consists of the site
identifier (SID) and the current date and time. Using the PC option, it is
available to assist in discovery of the TIDs of Remote NEs connected to
a Gateway NE via OSI over DCC.
Select the Communication -> NE Gen. Config -> NE discovery option
1. Choose the filter criteria
2. Click on Search

The page contains the SITE HEADER panel:

PC: The combobox to determine the PC flag (1301 for autodiscovery); it also returns the NE type.
TID: It shows the target network element for this command. 40 hexadecimal character NSAP address
may be used to address an NE with unknown TID. Clicking on SEARCH hyperlink a second SITE HEADER
panel shows the following information:
Site ID: the site identifier.
Date: It shows the current date in the <year>-<month>-<day> format.
Time: It shows the current time in the <hour>-<minute>-<second> format.
Type: It shows the current NE type
Release Num: It shows the current NE version

Issue 01
3.1 Local address
Local address configuration
PC option in the filter set to PC
PC option in the filter set to blank alternative


Issue 01
3.2 DCC configuration


Issue 01
3.2 DCC Configuration
LAPD
Line
Section Section
DCC
TSS-320 REG TSS-320
DCC
Section = USER Section = NETWORK
Section = NETWORK Section = USER

Example 1
Line = NETWORK Line = USER
The CT communicates with remote NEs through the DCC (Data Communication Channels) that support Qecc
protocol.
Two groups of DCC can be configured:
D1-D3: DCC in Section OH
D4-D12: DCC in Line OH
The DCC functional tab is made up of the NETWORK Interface panel which allows to create a network inter-
face on a specified DCC channel on an optical port for data communication purposes. The network
interface can be provisioned on the line or section DCC of the specific OCn facility.
Maximum number of DCC is 4RS+4MS channels for each slot.
Total maximum number of DDC for shelf is 32RS +32MS channels

Issue 01
LAPD [cont.]
Line
Section
DCC
TSS-320 1660SM
DCC
Section = NETWORK Section = NETWORK

Example 2
Line = NETWORK Line = NETWORK


Issue 01
LAPD [cont.]
This option allows the operator to modify the various network interface
parameters on a specified DCC channel on an optical port for data
communication purposes.
Select the Communication -> DCC -> Network IF option
1. Click on Create SEL
2. Choose the AID

(SDH board)
3. Click on Search

It allows the operator to modify the various network interface parameters on a specified DCC channel on an
optical port for data communication purposes.
The network interface must be first provisioned on the line or section DCC of the specific STMn facility.
The DCC is identified as STMn and the DCCCHNL parameter.

Issue 01
LAPD [cont.]
4. Select the SDH board and then click on Apply & Exit
7. Configure the IP protocol: set Y 6. Set the Channel: LINE =

if you connect the TSS 320 with MST, SECTION = RST
another TSS 320 or 100
5. Set OSI = “Y”
Set MNGPLANE to activate the supervision

8. Click on Save & Continue or Save
If you connect the TSS-320 with a omsn equimpemnt, the Layer 2
(role) must be the same (user – user or network – network)
The DCC tab displays a list of the facility with DCC capability previously provided. The list is basically
made up of a radio button, an AID column and a DCCHNL column.
Click on one of the available radio button the NE Interface Details panel change the fields according to
the selection.
The Delete hyperlink allow to remove the selected item from the list.
The NE Interface Details panel contains the following parameters:
Access Identifier: Specifies the Access Identifier of the facility
DCC Channel: Specifies whether the referred DCC is a Line DCC or a Section DCC. The values are:
LINE (MST) or SECTION (RST)
Lower Layer Mode: Specifies the protocol used for the Layer 2 over the specified DCC. The values
are: LAPD (LAPD Protocol to be supported on the Layer 2) or PPP (Point-to-Point Protocol to be
supported on the Layer 2)
Layer2: specifies the role of the interface. The values are: USER User Side (DTE) shall be assigned;
NETWORK Network Side (DCE) shall be assigned
OSI Protocol: Determines if the OSI Protocol will be run on the addressed DCC or not. The values are:
N (OSI Protocol is disabled on the addressed DCC) or Y (OSI Protocol is enabled on the addressed DCC)
Internet Protocol: Determines if the Internet Protocol will be run on the addressed DCC or not. The
values are: N (Internet Protocol is disabled on the addressed DCC) or Y (Internet Protocol is enabled
on the addressed DCC)
Layer 3 Quality of Service: specifies the quality of service used when establishing a Layer 2
connection: AITS (Acknowledged information Transfer Service) or UITS (Unacknowledged information
Transfer Service)
Integrated ISIS: Specifies if the Integrated IS protocol is running on the addressed DCC or not. The
values are: ENABLE or DISABLE (the IP must be set = Y)
Channel used by: The default value is MNGPLANE

Issue 01
LAPD [cont.]
Select the AID and then click on Delete to delete the LAPD
This panel is used to modify some LAPD parameters


Issue 01
OSI ULC Report
It allows to modify OSI upper layers stack parameters which are

common to all the stack interfaces of the NE (i. e., all the Line and
Section DCC interfaces and the Customer LAN).
To display the OSI ULC report, select: Communication DCC OSI
ULC Report
Configure the parameters and then click on Save

The DCC - OSI ULC Report page contains OSI Upper Layers Common Parameters table which contains:
Layer 3 IS Level: It the IS level provisioning. Possible values are:
1 It is a Level 1 IS.
2 It is a Level 2 IS

Issue 01
XC Overhead
Use this procedure to create overhead channel cross-connection. DCC

cross-connection provides DCC transparency functionality..
To create the XC overhead, select: Communication DCC XC
overhead
1. Click on Create


Issue 01
XC Overhead [cont.]
2. Choose the “DCC channel”
3. Click on “Select” relevant

to “From” channel
4. Choose the “From” DCC and

then click on “Select”

The parameters are:

DCC CHNL: specifies the reference of the DCC Channel. The values are:
LINE: Line / MS Control Channels D4 - D12
SECTION: Section / RS Control Channels D1 - D3
From: From Access Identifier determines the entity Access Identifier (AID) of either end of a cross-
connection for 2 WAY cross-connections. The cross-connection is bidirectional.
To: To Access Identifier determines the entity access identifier of the other end of a cross-connection
with respect to the identifier specified by the From parameter.

Issue 01
XC Overhead [cont.]
5. Click on “Select” relevant

to “To” channel
6. Choose the “To” DCC and

then click on “Select”
7. Click on “Save”
The XC overhead appears in the window


Issue 01
3.3 DCN Physical interface


Issue 01
3.3 DCN Physical Interface
IP Address
Configure the IP address of

the remote TSS 320 (#2)
DCC with IP and

OSI enabled
In this example, is not necessary the tunnel IP over OSI for the management of the remote
TSS 320. In fact, the DCCs of the TSS-320 transport the IP and OSI protocol. To open the
supervision of the remote TSS, it’s mandatory insert the IP address of the node and not the
IP address of the LAN (like in the TSS 320 (#1)


Issue 01
IP Address [cont.]
It retrieves TCP/IP stack parameters.

To display/set the IP address parameters, select: Communication
DCN Phys If IP Address
NE MAC Address
Configure the IP address, the subnet mask and then click on Save

The NE Configuration page contains the IP Address Management panel:

MAC ADDRESS: (Medium Access Control address), it is the MAC address assigned to the card. Note that
this parameter can only be read and cannot be modified.
IP Address: (Internet Protocol address), it is the IP address of the NE. The entry box allows to digit the
IP address of the NE (value range [1-99, 101-126,128-223] - [0-255] - [0-255] - [0-254]).
Subnet mask: it is the entry box for subnet mask of the network the NE is connected to (value range
[128-255] - [0-255] - [0-255] - [0-255]). The mask, in binary representation, must contain a contiguous
string of 1s (the network portion) and a contiguous string of 0s (the host portion).

Issue 01
LAN Management
It allows the operator to modify the various network interface

parameters associated with the customer LAN.
To display the LAN parameters, select: Communication DCN Phys If
LAN Manag
N.B.: the Channel must be set to MNGPLANE

1. Set “Y” this parameters To enable the supervision from ZIC
2. Configure the LAN parameters
4. Click on Save 3. Configure the Negotiation mode

The Customer LAN Management tab displays the Customer LAN Management panel that contains the
following parameters:
OSI Protocol: Determines if the OSI Protocol will be run on the customer LAN or not. The values are:
N (OSI Protocol is disabled on the Customer LAN); Y (OSI Protocol is enabled on the Customer LAN)
Internet Protocol: Determines if the Internet Protocol will be run on the customer LAN. The values are:
N (Internet Protocol is disabled on the Customer LAN); Y (Internet Protocol is enabled on the
Customer LAN)
OSI Area: This is possible to enter as to which OSI Area the Customer LAN belongs to (“1”, if OSI was
disabled previously, previously existing value, otherwise).
Integrated ISIS: Determines if the Integrated IS-IS Protocol will be run on the customer LAN or not. The
values are:
N (Integrated IS-IS Protocol is disabled on the customer LAN); Y (Integrated IS-IS Protocol is enabled
on the customer LAN)
Proxy Address Resolution Protocol: The values are:
Y Proxy Address Resolution Protocol is enabled on the customer LAN; N Proxy Address Resolution
Protocol is disabled on the customer LAN
Channel used by: The values are:
MNGPLANE, NONE
IP address of NE: The IP address of the Network Element
Subnet Mask: The subnet mask of the Network Element
Gateway address: The gateway address of the Network Element
MAC address: The Media Access Control address of the Network Element
OSPF: Specifies the Open Shortest Possible Path. The values are Y or N
OSPF Area: A mechanism that specifies the backbone area of the NE. The valid range is from 1 to 3
Issue 01
ARP Cache Management
It allows the operator to get all the entries contained in the ARP
(Address Resolution Protocol) cache on the customer LAN interface.
To display the ARP parameters, select: Communication DCN Phys If
ARPCACHE Mng
Click on Delete ARPCACHE to delete ARPCACHE

The page contains a table where:

# Progressive number for the ARP cache that are populated automatically as a result of ARP protocol's
functionalities.
IP ADDRESS It is the IP address (in dotted-quad format) of the entry in the ARP cache.
MAC ADDRESS It is the MAC (Medium Access Control) Address of the entry in the ARP cache.

Issue 01
Blank Page


Issue 01
3.4 IP tunnel configuration


Issue 01
3.4 IP tunnel Configuration
IP over OSI tunnel Configuration
In this example, the bidirectional IP over OSI tunnel it’s necessary for the TSS
320 management from the 1660SM. In fact, the DCCs of the 1660 don’t transport
the IP protocol, but only the OSI


Issue 01
3.4 IP tunnel Configuration
IP over OSI tunnel Configuration [cont.]
It allows the operator to manage an IP tunnel instance on the NE. The

IP tunnel that has to be created is specified by its AID. If the AID
specified matches any of the ID for existing IP tunnels, an error
message will be returned in response. The supported encapsulation of
the IP tunnel is the Alcatel-Lucent proprietary type: both Standard
(RFC3147: GRE over CLNS network) and CISCO proprietary
encapsulation protocol types are not supported.
To configure the IP tunnel, select: Communication IP Tunnel
1. Click on Create
2. insert an identifier
Remember to add F0
at the end the NSAP
3. Click on Save
The IP Tunnel Configuration tab displays the following:

AID: Refers about the access identifier of the LSP tunnel for the network connection. It is assigned by
system at connection creation. Format is as follows: <Source Node ID> or <Destination Node ID>: <Four
dot separated numeric string> <Tunnel ID> or <Tunnel Instance>: <One numeric string> in the 0 to 255
range for each numeric string.
Remote NSAP: Specifies the Network Service Access Point for the IP Tunnel
Encapsulation Type: Specifies the Encapsulation Type required for the Tunnel configuration: ALU
(Alcatel-Lucent Proprietary protocol) or GRE (Generic Routing Encapsulation)

Issue 01
Blank Page


Issue 01
3.5 NE Autodiscovery


Issue 01
3.5 NE Autodiscovery
NE autodiscovery Configuration
The NE implements the NE Autodiscovery mechanism for automatic

discovering by Network management system of the NE presence in the
network.
To enable the NE autodiscovery, select: Communication NE
Autodiscovery
1. Set Y
2. Click on Save

The NE Auto Discovery tab displays the Autodiscovery panel that contains the following parameters:
ENABLED: To enable or disable the NE Autodiscovery. The values are:
Y: To enable the NE Auto Discovery
N: To disable the NE Auto Discovery
STATE: Displays the current status of the NE. The default value is IDLE

Issue 01
3.6 OSPF Area


Issue 01
3.6 OSPF Area
OSPF Area creation
Thi smenu permits to configure an OSPF Area.
To create a new OSPF Area or to delete an existing OSPF Area, select:
Communication OSPF Area
1. Click on Create
Backbone
2. Click on Save


Issue 01
3.7 Network domain


Issue 01
3.7 Network domain
IP Route
It allows the operator to enter (add) a new static IP route in the IP
routing table, by ZIC. If the AID specifies a STM-n then the NEXTHOP
parameter should not be specified. If the AID specifies the LAN, then
the NEXTHOP parameter must be specified.
To open the Ip Route select: Communication Network Domain IP
Route
1. Click on “Create” to prepare a new static route

The IP Routing Configuration tab displays the following:

Access Identifier: Specifies the Access Identifier for the IP route
DESTADDR: Specifies the destination IP address for the IP route
IP MASK: Specifies the subnet mask for the IP route
NEXTHOP: Specifies the IP address of the next hop
DCCCHNL: Specifies the DDC channel information
METRIC: Specifies the metric value for the IP route
METRICTYPE: Specifies the metric type for the IP route
STATUS: Specifies the IP route status
ADVERTISE: Specifies whether the IP route is leaked into IP routing protocols ( Integrated IS-IS). The
values are: N (route is only known on the local NE) or Y (route is leaked into integrated IS-IS)

Issue 01
3.7 Network domain
IP Route [cont.]
2. Click on Select
4. Insert the static route
3. Choose the AID and click on Send

5. Click on Save or Save & Exit


Issue 01
3.7 Network domain
IP Route [cont.]
IP address of the NE LAN
NE IP Address
IP static route
IP route discovered by means of integrated IS-IS protocol
IP route discovered by adjacent host

Example: in the selected row, the next hop represents the IP LAN Address while the Destination Address
represents the IP Address of the node (NE)

Issue 01
3.7 Network domain
NSAP report
This option instructs the NE to provide routing database information

that is supported by Layer 3 (network layer) of the OSI Data
Communication Network (DCN).
To open the NSAP Report menu select: Communication Network
Domain NSAP report 1. Choose the type
2. Click on Search to display the parameters

The NSAP Report page contains the Network Service Access Point panel, where:
TID: The entry field allows to digit the network node TID for the command. Possible values are:•<1-20
VALID TID CHARACTERS> (e.g. VIMERCATE)
Lookup Type: By means of this combobox it is possible to specify the type of lookup function that will be
performed to retrieve neighboring NEs. Possible values are:
DRCT It retrieves the NSAPs and the TIDs of all the directly reachable (1 hop away) Level 1 and Level 2
Intermediate Systems (ISs), to which an adjacency is formed.
L1ROU It retrieves the NSAPs of all the reachable Level 1 ISs within all the areas, the NE is part of,
including NEs and Gateway NEs.
L1ROUTID It retrieves the NSAPs and the TIDs of all the reachable Level 1 ISs within all the areas, the
NE is part of, including NEs and Gateway NEs.
L2ROU It retrieves the area addresses of all the reachable Level 2 ISs, including NEs and Gateway NEs.

Issue 01
3.7 Network domain
OSI Address
It retrieves the parameters of a configured OSIAREA that the NE is part
of.
To open the OSI Address menu select: Communication Network
Domain Osi Mng OSI NE Area
1. Insert the address
2. Click on Save
3. Click on Yes
The OSI page contains the OSI AREA panel:

OSI AREA: Combobox to determine an access Identifier for an OSI area.
Level 3 Initial Domain Part: Assigns the initial domain part of the manual area address (8 hexadecimal
characters)
Level 3 Domain Format Identifier: Assigns the domain format identifier field of the manual area address
(2 hexadecimal characters)
Level 3 Organization: Assigns the organization field of the manual area address (8 hexadecimal
characters):
Level 3 Reserved: Assigns the reserved field of the manual area address (4 hexadecimal characters):
Level 3 Routing: Assigns the routing domain and routing area within the routing domain of the manual
area address (8 hexadecimal characters)
Level 3 System Identifier: This is the system identifier assigned to the card (12 hexadecimal characters)

Issue 01
3.7 Network domain
OSI Tunnel [cont.]
OSI over IP tunnel
In this example, the bidirectional OSI over IP tunnel between the pc and the TSS-320 it’s
necessary for the management of the 1660SM. In fact, the 1660 management uses OSI
protocol and then it’s necessary create the OSI over IP tunnel up to the TSS-320.A this
point the OSI is transported by means of DCC up to the 1660SM. The tunnel OSI over IP
from pc to TSS-320 is realized by means of a specific configuration of the Lower Layer
(“Sub-network Type” = IP tunnel )


Issue 01
3.7 Network domain
OSI Tunnel
This function is used to create a new OSI over IP tunnel.

To open the OSI Tunnel menu select: Communication Network
Domain Osi Mng OSI Tunnel
1. Click on Create to create a

new OSI over IP tunnel
2. Insert the Access Identifier

and the IP address of the
target NE
3. Click on Save

Issue 01
3.8 TARP Management


Issue 01
3.8 TARP Management
TARP Report
This menu allows the user to retrieve the TL1 Address resolution
Protocol (TARP) parameters.
To open the TARP Report select: Communication TARP Mng TARP
Report

The TL1 ADDRESS RESOLUTION PROTOCOL PARAMETERS panel displays the following fields:
Type 1 Timer: Waiting forr esponse to TARP Type 1 request PDU
Type 2 Timer Waiting for response to TARP Type 2 request PDU
Loop Detection Buffer Flush Entry Timer: The default value is 5 minutes
Loop Detection Buffer Entry Timer: The default value is 300 seconds
TARP Lifetime: The default value is 100 hops
TARP Origination Flag: Allows to enable/disable TARP origination flag
TARP Sequence Number: Specifies current sequence number in use by TARP processor
TARP Data Cache processing: The values are either Y or N

Issue 01
3.8 TARP Management
TARP Cache
This function retrieve all of the current TARP Data Cache entries.
The 1850 TSS 320/160C maintains a TARP Data Cache of at least 240
entries. The cache contains the most recently used TID/SAP translations
that allows faster TID/SAP translation. This cache is cleared once the
system reboots or on a specific user request. The maintenance and
update of this cache is automatic without user intervention.
TL1 uses the TID to define the destination of a command, but the
connectionless network protocol (CLNP) uses the NSAP address to
define the destination of a TL1 message. In order to send a TL1
message in a network using CLNP at layer 3, the TID must be converted
into the appropriate NSAP address. The TID addresses are mapped to
NSAP addresses through automatic network provisioning (TARP feature).
For TID routing translation, TIDs and NSAPs are associated in pairs and
are cached in the TARP CACHE. This command removes all the TID-
NSAP entries that were stored in the TARP cache due to the TARP
function.


Issue 01
3.8 TARP Management
TARP Cache [cont.]
The TARP CACHE is essentially the TID-NSAP look-up table. The TARP
cache gets repopulated automatically as a result of TARP protocol's
functionalities.
To open the TARP cache select: Communication TARP Mng TARP
Cache


Issue 01
3.8 TARP Management
TARP LDB
This menu retrieves the TARP Loop Detection Buffer (LDB). The 1850
TSS320/160C supports a circular (First In First Out) TARP Loop
Detection Buffer (LDB) in order to perform the loop detection
procedure. The LDB is used by Intermediate Systems to verify the
received TARP PDU for loop detection. Each entry in the TARP LDB
contains a sequence number and the protocol address of the originator.
Note that in this implementation the protocol used will be CLNP, so the
protocol address will be the NSAP address of the network layer entity.
To open the TARP LDB menu select: Communication TARP Mng
TARP LDB


Issue 01
Blank Page


Issue 01
3.9 NTP configuration


Issue 01
NTP server configuration
This procedure allows to set the Time and Network Time Protocol
(NTP).
1. Follow the System Management Network Time Protocol menu
path.
A window with Time and Date and Network Time Protocol panels will be
displayed.
The Time and Date panel allows to manually set the system date and time by means of
six combo-boxes Year, Month, Day, Hour, Minute and Sec.
The Network Time Protocol panel shows the current values and allows to ENABLE or
DISABLE the time synchronization from the NTP server. When the NTP protocol is
enabled and no NTP server is in service or reachable, then the time of day clock
will keep it's current value and synchronize with the NE internal clock frequency.
2. If you want the time synchronization from the NTP server select the
ENABLE option in the NTP Server Synchronization: field. By means of
the New Offset three combo-boxes (+/-, HH and MM) it is possible to
apply at the NTP server the UTC (Universal Time Clock) time, for all
events and time stamps reported by this NE. Factory default is +00-00.
3. Click on Save.
Up to 10 NTP servers can be provisioned. An NTP server can be designated as a preferred server among
equally usable and qualified servers. In the case where more than one server is determined to be the
optimum server, the server with the preferred attribute is selected.

Issue 01
NTP server configuration [cont.]
1. Open System Management Network Time Protocol
When the NE is supervised

from the EML, the NTP is
automatically set to
enable and the server
appears in the window
2. Click on Create

The page contains the following two panels:

The Time and Date panel allows to manually set the system date and time by means of six combo-boxes
Year, Month, Day, Hour, Minute and Sec. This command is not allowed if NTP is enabled.
The panel has the Save hyperlink in order to save the settings.
The Network Time Protocol panel shows the following information:
Current NTP Server Synchronization: The time synchronization from the NTP server; The value are
Enabled or Disabled. Factory default is Disabled
Current Offset: By means of the New Offset three combo-boxes (+/-, HH and MM) it is possible to
apply at the NTP server the UTC (Universal Time Clock) time, for all events and time stamps reported
by this NE. Factory default is +00-00.
Current Operating Mode: The current operating mode of the NTP service. The values are:
FREE-RUNNING NTP is not enabled, and the NE is not synchronized to an NTP server and is instead
using its own internal clock as a source
HOLDOVER NTP is enabled but the NE has lost NTP server connectivity, and is using the last known
clock update to synchronize its clock
NTPSYNC NTP is enabled, and the NE is using the NTP protocol to synchronize to an NTP server

Issue 01
NTP server configuration [cont.]
2. Insert the IP server address
3. Click on Save
4. Set ENABLE
5. Click on Save The NTP server appears in the window
N.B.: to create the spare NTP server, repeat the steps 1, 2, 3

This option edits the Network Time Protocol parameters. Changes take place immediately.
Note: If no NTP server has been entered, and the NTP protocol is enabled, the time-of-day clock will
synchronize with the last known internal clock frequency.
Changing the date and time of the system could result in partial or incomplete PM data.

Issue 01
NE time
To set the NE time: System Management Network Time Protocol
1. Insert the date/time parametrs
2. Click on Save
N.B.: the NTP protocol must be disable


Issue 01
Blank Page


Issue 01
4 Configurations: ALS, AINS mode, J0, TP threshold,
J1, Restart NE, Alarm List, Housekeeping,
Optical Intrusion


Issue 01
4 Configurations: ALS, AINS mode, J0, TP threshold, J1, Restart NE, Alarm List, Housekeeping, Optical Intrusion
Physical media parameters: ALS
ALS Enable, determines if the laser will be shut down on the

occurrence of an LOS defect on the receive side. If a shutdown occurs,
the IO module will periodically transmit pulses to attempt to restart
the circuit. When ALS is disabled, the laser will remain on. If the ALS
state is changed from enable to disable while the laser is shut down,
laser power will be unconditionally restored. The commands are:
Y: ALS Enable
N: ALS Disable, Laser forced on, no condition is raised on the affected STM-
n
N_ON: ALS Disable, Laser forced on, ABNORMAL condition is raised on the
affected STM-n
N_OFF: ALS Disable, Laser forced off, ABNORMAL condition is raised on the
affected STM-n
Restriction: the parameter is applicable for the following port types:

NORMALSO (Normal Synch. Optical)


Issue 01
Physical media parameters: ALS [cont.]
2. Select STM
1. Select the
optical port
4. Configure the WTR Time

(Time of Laser off): 3. Configure the ALS mode
from 60s to 300s
5. Configure the Time of Laser

On: from 2s up to 10 s
6. Click on Save

Issue 01
Physical media parameters: Automatic Laser ShutOff
2. Select STM tab
1. Select the
optical port
3. Click here to retrieve

the laser state
4. Click on “Operate Automatic Laser ShutOff”

to activate the RESTART or TEST laser mode
For RESTART mode, a pulse of normal duration ALS TX seconds is immediately applied. If this does not
result in a restoration of the circuit, then after ALS WTR seconds normal ALS automatic restart pulsing is
resumed.
For TEST mode and immediate pulse is applied and lasts 90 seconds. The laser is unconditionally shutdown
at the end of the 90 seconds. Circuit restoration is not tested during this period, so even if a failure
clears the circuit will not be restored. Following the end of the TEST pulse, regular automatic ALS pulsing
resumes after ALS WTR seconds

Issue 01
TP Configuration: J0
2. Select STM
1. Select the
optical port
3. Configure the TX pathtrace

4. Click on Save See next page

Only the Path trace in the Section layer can be configured. The received Path trace is also displayed
Path Trace: it is made of 16 bytes: 15 bytes written by the operator and 1 byte handled by the system for
CRC7 error checking.
Received field is read only
The “SSBits” permits to transport the SONET frame over SDH network or SDH frame over SONET network
without generation of the LOP alarm.
The “TRC. Id. mism. Monitor” permits to enable/disable the TIM (trace identifier mismatch) alarm

Issue 01
TP Configuration: J0 [cont.]
To insert the path trace in TEXT format.

To set the format of the Trace Identifier Choose to convert it in HEX format
To insert the path trace in HEX format. To enable/disable the path trace monitoring
Choose to convert it in TEXT format


Issue 01
J0 analysis
1. Select STM
2. Select SectionTrace Info panel
3. Click on Retrieve section Trace
Retrieve Section Trace permits to retrieve

the actual Rx section trace


Issue 01
Automatic In-Service threshold
Automatic In-Service Threshold, specifies how long an input signal must

be present on the facility without a failure condition before the system
transitions the facility into the In-Service state.
2. Select STM
3. Configure the HHH and MM HHH MM
1. Select the
optical port
4. Click on Save
See next page

Automatic In-Service Threshold:

Allows to set how long an input signal must be present on the facility without a failure condition before
the system transitions the facility into the In-Service state, in HHH-MM format, where value HHH
indicates the time duration in hours and value MM indicates the time duration in minutes. The default
value is 008-00.
This parameter sets also the value of AINSTH for the ODU2 entity.
This parameter applies to the client side only.

Issue 01
Automatic In-Service threshold [cont.]
This parameter works only when “Port

Mode” = “AUTO”:
• LOS: hide LOS alarm, during the To have the automatic In Service timer
“Automatic in Service Threshold” period updated to 000-00 and then the board in
service state, the alarm selected in the
• ALL: hide all alarms, during the Automatic In-Service Fault Criteria, must
“Automatic in Service Threshold” period not be present

PMODE (Port Mode), determines if the conditions for the facility are reported or not. The criteria for
leaving the AUTO state autonomously depends on the current value of the parameter AINSCRIT.
In addition the set of conditions which are considered for the alarm correlation with PMODE depends on the
current value of the parameter PST Correlation. The values are:
AUTO: the conditions as defined by PST Correlation are not reported and transition to MON if condition
as defined by AINSCRIT (determines the fault criteria to leave the PMODE/SST state value AUTO/AINS) is
cleared and AINSTIMER has expired.
NMON: the conditions as defined by PST Correlation are not reported.
MON: conditions are reported according the specified ASAP.

Issue 01
TP Threshold Configuration (MST) and SS bits
2. Select STM
1. Select the
optical port
3. Configure the thresholds

5. Click on Save
4. Configure the SS bits

TP Thresholds Configuration allows the operator to set the DS and Signal fail alarms’ thresholds for the
selected Termination Point. It’s available for Line section (MST).
The system enables the configuration of the Signal fail threshold (from 10E-3 to 10E-5) and of the Signal
Degrade threshold (from 10E-5 to 10E-9)
It is possible to select the Defect distribution:
Poisson enables the configuration of the ExBER threshold (from 10E-3 to 10E-5) and of the Signal
Bursty enables the configuration of the Signal Degrade.
Threshold: quantity of errored frames (Threshold can be set to 1, 10, 100, 1000)
Consecutive Bad Seconds: quantity of consecutive seconds where each second contains at least a
quantity of errored frames equal to the value written in the Threshold box (Consecutive Bad
Seconds ranges from 2 to 10)
The “SSBits” permits to transport the SONET frame over SDH network or SDH frame over SONET network
without generation of the LOP alarm.

Issue 01
TP Threshold Config., RDI byte and J1 in the VC4
1. Select the
optical port
2. Select AU List
3. Select an AU
See next page


Issue 01
TP Threshold Config., RDI byte and J1 in the VC4 [cont.]
4. Select AU Configuration
5. SET Y the POM INGRESS and/or EGRESS

6. Configure the error distribution
7. Configure J1
8. Click on Save
TP Thresholds Configuration allows the operator to set the DS and Signal fail alarms’ thresholds for the
selected Termination Point. It’s available for Channel section (VC4)
The system enables the configuration of the Signal fail threshold (from 10E-3 to 10E-5) and of the Signal
It is possible to select the Defect distribution:
Poisson enables the configuration of the ExBER threshold (from 10E-3 to 10E-5) and of the Signal
Bursty enables the configuration of the Signal Degrade.
Threshold: quantity of errored frames (Threshold can be set to 1, 10, 100, 1000)
Consecutive Bad Seconds: quantity of consecutive seconds where each second contains at least a
quantity of errored frames equal to the value written in the Threshold box (Consecutive Bad
Seconds ranges from 2 to 10)
The J1 Path Trace presents the same parameters of J0
The C2 Signal Label presents the following parameters:
Received and Expected fields are read only; they can display the following numbers (decimal code),
according to G.707 ITU-T recommendation:
0: Unequipped
1: Equipped non-specific
2: TUG structure
3: Locked TU-n
4: Asynchronous 34/45Mbit/s
18: Asynchronous 140Mbit/s
19: ATM
20: MAN, DQDB
21: FDDI All Rights Reserved © Alcatel-Lucent @@YEAR
Issue 01
J1 analysis
1. Select AU List tab
2. Select AU Configuration tab
3. Select Retrieve Path Trace panel
4. Choose the direction
5. Click on Search
RCV side TRANS side


Issue 01
Restart NE
1. Select NE, Shelf or a board according to

the table present in the next page
2. Choose the Phase
3. Choose the Command Mode

4. Click on Save

The Restart panel resets the specified equipment entity and displays the following fields:
Phase: Allows to select the type of restart. The values are:
WARM: microprocessor is restarted and reload of dynamic data only (DataBase in RAM) is executed
COLD: microprocessor is restarted and reload of dynamic and static data (SW and DataBase if present)
is executed
POWER-ON: the board is powered-off/on (as if unplugged and plugged), microprocessor is restarted
and reload of dynamic and static data (SW and DataBase) is executed
Command Mode: Allows to select the Command Execution Mode. The values are:
NORM: Normal, the command is denied if the result of its execution is service affecting. (warm)
FRCD: Forced, the command is completed even if the result of its execution is service-affecting.
(warm, cold, power-on)
If a plug&play module is inserted in a slot which cannot be provisioned with that entity, the provisioning
attempt fails and its state moves to OOS-MA, UAS. No data is provisioned for the inserted module.
After a full restart of the NE, all the modules are automatically autoprovisioned.
After a cold restart of the active SC in unprotected configuration (non-active SC not present), SC
downloads DB from EC and autoprovisions only the modules that have no provisioned data in the DB.
After a power-on restart of the active SC in unprotected configuration, SC autoprovisions all modules
except ECs.
It is also supported manual restart at NE level (both COLD and POWER-ON) which have the effort of
restarting EC320 and MT320/MT160.

Issue 01
Restart NE [cont.]
Restart allowed for each Board.
x x

It is supported manual restart at NE level (both COLD and POWER-ON) which have the effort of restarting
EC320 and Matrix cards.

Issue 01
Alarm list
The alarms list displays the current status of any existing, standing,
housekeeping conditions in the system (alarmed, not alarmed, or not
reported). For each event, an alarm is reported. If multiple conditions
exist, a line of output is provided for each condition in ascending order
by date and time of occurrence, and it is possible refresh the table.
4. Click on alarms tab


Issue 01
Housekeeping (introduction)
The NE shall be able to receive and process eight (8) separate

customer-defined inputs for fault conditions arising externally to the
NE. The fault conditions shall be processed and reported as for
internally detected fault conditions. It shall be possible to disable the
reporting from any input if not used.
The inputs shall be capable of interfacing to a dry relay contact, i.e. an
input shall comprise two wire interface capable of detecting an open or
closed circuit condition between the two connections.
Each user alarm input shall be separately configurable to accept either
a closed circuit or open circuit state as the active alarm condition. The
inputs from the dry contacts are normally used for ”site specific”
alarms such as open door, high temperature, high water level, etc.
The polarity of an external input control determines the relationship
between the declaration of an environmental condition and the
physical signal.


Issue 01
Housekeeping (introduction) [con’t]
The NE shall drive 4 separate output station controls for customer

defined site specific facilities external to the NE, such as air
conditioning, generators, etc.
Operating an external control means that a relay is activated to control
some external device. Releasing an external control means deactivating
the relay.
The polarity of an external output control determines the relationship
between the control state (CONTSTATE) value and the physical signal.
Housekeeping functionality is provided by the active FLC board.
Customer access to the HKP connections shall be via 25 pin D-Sub
connector on the NE Front-top of the Main Shelf.

The states of the control relays shall be persistent through an EC320 restart or protection switch. That is, at
the completion of the restart or protection switch, the state of the outputs shall be the same as before
the restart or protection switch
During the time that an EC320 restarts or switch activity is in process, if the control relay states cannot be
maintained, then they shall be (default) to the open contact state.
The AIDs of the input and output points shall always be associated with the EC320 in slot 1 regardless of the
actual location of the working EC320
The AIDs respectively shall be CPO-1-1-1-{1-4} and CPI-1-1-1-{1-8}.

Issue 01
Housekeeping: input configuration
1. Open Alarms Housekeeping Input Points
2. Click on Continue
Click on View to
check the Alarm or
Condition status
3. Click on Set to configure the input point


Issue 01
Housekeeping: input configuration [con’t]
4. Fill in the parameters
5. Click on Save

It shall be possible to configure user labels for each alarm input and control output to be used for TL1
command and message purposes on all user interfaces (via the local terminal and element manager). The
labels shall consist of free (ASCII) text fields of up to 30 characters. It shall be possible to reconfigure
each label at any time. Provisioning of housekeeping alarms and controls shall be persistent
Input Alarm sensors shall have the following characteristics:
Single ended with a common reference
Alarm sensor inputs shall indicate a LOW state when the customer driving circuitry has an impedance less
than 470 ohms. Driver applied voltage if any must be greater than -4v. Driver circuit must be able to
supply at lease 2ma minimum. A closed relay contact shall sufficient to cause a Low indication by the HKP
alarms sensors.
Alarm sensor inputs shall indicate a HIGH state when the customer driving circuitry has an impedance
greater than 100K ohms. An open relay contact shall sufficient to cause a HIGH indication by the HKP
alarms sensors. Driver applied voltage, if any must be in the range -6v<Vin<-220V

Issue 01
Housekeeping: output configuration
1. Open Alarms Housekeeping Output Points
Click on Operate or Release

to activate/deactivate the
External Control output point
3. Click on Set to configure the output point

The control outputs shall have the following characteristics:

Floating pairs, (no common reference)
Maximum blocking voltage 350V
Open contact resistance > 50 Mohm
Closed contact resistance < 20 ohm
Maximum load current 120ma

Issue 01
Housekeeping: output configuration [con’t]
4. Fill in the parameters
5. Click on Save

In Automatic mode, the related contact is driven Operating when the associated standing ConditionType is
active; the contact is Released when the associated standing ConditionType is cleared.

Issue 01
Optical Intrusion
Optical intrusion management is the capability to detect intrusion on

an optical line by unauthorized users and to provide consequent alarm
raise by the NE. Optical intrusion concept relies in the monitoring of
the receiving power in the STM-64 line modules, with an alert raised in
case of Rx power falling below or raising above a configured threshold.
Optical Intrusion Threshold, represents the maximum acceptable
difference among two measurements of received power, [PRx(tn)-
PRx(tn+1)], in absolute value; if the calculated value is higher than this
value, then an alarm indication shall be triggered by the port. Unit of
measure is dB, fixed granularity is 0.1db. Optical Intrusion can be
detected either by an increase or by a decrease of the measured
optical power.


Issue 01
Optical Intrusion [con’t]
Rx power is retrieved by the XFP termination supporting DDM. This

mechanism applies to UNI and NNI interfaces to detect a 1 dB change in
optical power level on all outside fiber spans (using DDM enhanced
accuracy). This is reported as an alarm, in near real time (no more than
15 mins after the event). Optical intrusion is supported for 1P10GS
interfaces only.
The allowed values are:
DISABLED: the optical intrusion detection is disabled
ENABLED: the optical intrusion detection is enabled
RAISED: an optical intrusion event has been detected
The parameter is applicable for the ports supported by hardware items
implementing Enjanced DDM function.
The XFPs P/N 1AB217280004 (40 Km reach) and 1AB217280003 (80
Km reach) support Enhanced DDM. This allows to provide Rx power
reading precision with ±1 dB accuracy, in order to detect intrusion
in optical line by unauthorized users.


Issue 01
Optical Intrusion [con’t]
1. Select the STM-64 port 2. Select AU List tab
3. Select the configuration: Enabled or Disabled only
4. Choose the threshold from

+1.0 dB up to +48.2 dB
5. Click on Save


Issue 01
Blank Page


Issue 01
5 Configurations: shelf declaration


Issue 01
5 Configurations: shelf declaration
Shelf creation
To create a new shelf, select the RACK icon, and then click on Create
Shelf
1. Select the Rack

3. Configure the proper equipment: UNVRSL320
for TSS-320 or UNVRSL160 for TSS-160
4. Do Save

In the “create a new Shelf” window, you have the following parameters:
Access Identifier: by means three comboboxes is possible to select the label (with associated icon) and
the number inside the rack that will be presented in the tree. The available choises are:
SHELF: This is the Alcatel-Lucent 1850 TSS-320/160 subrack and is shown in the tree area
the label will be set at SHELF-x-x
This second combobox sets the first number presented in the tree; i.e. SHELF-1-x as for the picture. It
can range from 1 to 7.
The third choice sets the second number presented in the tree; i.e. SHELF-1-1 as for the picture. It can
range from 1 to 9.
Provisioned Type: it is the type of the shelf actually provisioned. The allowable choices are:
UNVRSL320
UNVRSL160
Automatic In Service Mode: it specifies the Automatic in service mode to which the equipment is set.
The allowable choices are:
Primary State: it specifies the primary state to which the equipment is set. The allowable choices are:
IS: In Service
OOS: Out Of Service

Issue 01
5 Configurations: shelf declarations

SHELF ID: This parameter specifies, for the Shelf Types = UNVRLS320/160, a value that is equal to the
one set by the HW tool mounted on the Shelf and to set the ID of the Shelf. The allowable choices are in
the 0 to 31 range.
SHELF Role: Specifies the provisioned shelf role for UNVRLS320/160 shelf types. The allowable choices
are :
MAIN: Main Shelf of the NE
NOMAIN: Extension Shelf of the NE

Issue 01
5 Configurations: shelf declarations
Refresh Tree
It allows to update the left part of the browser page when some
changes are occurred.
To refresh the tree, click on the following icon
Click on here to refresh the current window


Issue 01
6 Configurations: boards declaration


Issue 01
6 Configurations: subrack & boards declaration
Introduction
The NE hierarchy is organized in the following way:

Node rack shelf board module (if any) port
The navigation through different levels of the NE hierarchy is performed by
double clicking on the objects in the tree area.
Clicking on the “Equipment” tab, the client area shows the actual shelf
layout as depicted in the following


Issue 01
Clicking on one of the slot (both the vertical one and the horizontal
one, such as FAN and TBUS), it is possible
On a empty slot to “provision” or “retrieve” information about an object
On a busy slot to retrieve information about the card and the relevant ports
(if present)
EMPTY SLOT

Selecting one empty slot the Provision... message popups and it is possible to start the provisioning
procedure.

Issue 01
BUSY SLOT

Selecting one board the Details message popups and it is possible to accessing the physical resource

Issue 01
Board Configuration: General procedure
1.Configuration of a New board (This procedure is valid when Auto-
Provisioning field had been set as MANEQ – AUTOFC (refer to pg.13)):
Select a empty slot (grey color) in the tree area or in the “Equipment” tab of
the shelf view (see previous slide) Select Provision… (shelf view only)
Click on “Save” to configure the board and the present modules
2.Remove a board:
Select a port
Check the presence of Cross Connection, DCC, Loopback, VCG port, Synch
source, PM
Select a Board
Click on “Remove” option (Causes the specified facility client/line to be
placed in an out-of-service (OOS-MA or OOS-AUMA) state for maintenance
purposes).
Select a Board once again
Click on “Delete” option (the facility is removed from the tree view)
In case of LOA card, remember that:
the two matrix must be set both to “MT320LO”
Before configuring the LOA spare (slot 24, 33) it’s mandatory to configure at least
one LOA main (slot 21 or/and 22 for slot 24 and slot 35 or/and 36 for slot 33).
It is possible to undeclared a port only if no channels and no connections are active on it

Issue 01
Examples of Configuration: 4P2G5SO
When the “Equipment actual”

1. Select a slot appears, it means that the board
is present in the equipment
2. Choose Provisioned Type = Actual Type
3. Click on Save
Configuration of a 4P2G5SO:
Select the empty slot
Set Provisioned Type = 4P2G5SO The board, the
Click on “Save” modules and the
Configure the modules ports appear in
Configure the port the tree view
In the window appears the following parameters:

Access Identifier: It specifies the Equipment Access Identifier, identifies the equipment entity access
identifier
Actual Type: Specifies the Physically equipped module type (see Current Provisioned Type).
Provisioned Type: It specifies the Provisioned module type. It is also shown in the tree.
Primary State: To change the primary state to which the unit is set. The choices are:
IS (In Service): The module is providing service.
OOS-AU (Out of Service, Autonomous): The module is out of service due to an autonomous event.
OOS-MA (Out of Service, Management): The module is out of service due to management action.
OOS-AUMA (Out of Service, Autonomous and Management): The module is out of service both due to
an autonomous event and management action.
Automatic In Service Mode: the combobox allows to change the Automatic in service mode to which the
unit is set. The allowable choices are:

Issue 01
Port View window: 4P2G5SO
Port View window displays five functional tabs.

This window is opened by clicking on the port symbol in the tree view.
Functional tabs are:
STM
PROTECTION
STM PM
AU Select
AU LIst


Issue 01
Port View window: 4P2G5SO [cont.]


Issue 01
SFP View window: STM-16
DDM information


Issue 01
1POTU2/1POTU2XB board view
1POTU2
1POTU2XB

Issue 01
1POTU2/1POTU2XB port view: line


Issue 01
1POTU2/1POTU2XB port view: client


Issue 01
LOFA board view
This parameters are used

only when APT mode
and VOA mode aren’t
set to manual

The VOA can be configured in two ways:

Manual mode: the operator directly provisions the VOA attenuation; the range is from 1.0 dB to 15.0 dB
in step of 0.25dB, the default value is 9dB
SAC (Span Attenuation Control) mode: the VOA attenuation is provisioned automatically by the
software.
LOFA1111 supports “Dynamic Channel Equalization”. It is the capability to provide per wavelength dynamic
power equalization when wavelengths are added, dropped, or passed thru a node, without disruption of
existing channels.
LOFA1111 in vertical configuration, can work in two modalities:
Manual mode, the output power of the first and of the second stage of the amplifier are tuned by the
operator directly configuring them
Gain (Automatic Gain Control) mode: the power of the 1° and 2° stage are regulated automatically
through algorithms controlled by software. In AGC mode, the output power of the 1° and of the 2°
stage (OP1 and OP2) is regulated keeping the gain as constant; this means that the power associated to
each transmitted lambda doesn't change respect to the number of the transmitted lambdas.

Issue 01
LOFA: OTN management view
1. Select the LOFA card
2. Scroll the window up to the bottom,

select the WDM selection panel and
click on Continue


Issue 01
OMDX8100 board view


Issue 01
OMDX8100: OTN management view
1. Select the OMDX8100 card

select the WDMselection panel and
click on Continue


Issue 01
OMDX8100: OTN management view [cont.]
Management panels

In the OMDX8100 card, the following entities are managed

OTS: the OTS is automatically provisioned when an OMDX module or LOFA module is provisioned. The
OTS on an OMDX is automatically deleted and disabled if/when an optical connection is provisioned
between the OMSOTSPORT and the LOFA. Conversely, if an optical connection between OMSOTSPORT
and LOFA is deleted, the OTS on LOFA is deleted and disabled and entered/enabled on the OMDX
OMS: the OMS is automatically provisioned when an OMDX module is provisioned. In case of a cascade
configuration, the OMS on the secondary OMDX is deleted and disabled.
OMSBAND: the OMS BAND is automatically provisioned when an optical connection is established
between two OMSBANDPORTs on separate OMDXs representing a pass-through band of channels
OMSOCH: eight OMSOCH facilities are automatically provisioned when an OMDX module is provisioned.
In case of a cascade configuration, the OMSOCHs on the secondary OMDX is automatically deleted and
recreated as a child of the master OMS.
OMSOCHIF: an OMSOCHIF facility is automatically provisioned when an OMSOCHPORT is connected via
optical connection to a transponder OCHPORT or to an EXTERNAL entity. The OMSOCHIF represents the
optical port of an OMSOCH.
OCONN: the OCONN tab is used to create an optical connectionwith the OMDX8100 card

Issue 01
DWLA10X board: line and client configuration
2. Choose the colored XFP module
4. Click on Save 3. Choose the channel

1. Select the MDL 1 (Line side)
or MDL 2 (client side)
5. Choose the XFP module

according to the client type
6.Choose the client type
7. Click on Save
In current release only XL-642C is available

Issue 01
DWLA10X board view
The module 2 is the client side
The module 1 is the line side


Issue 01
DWLA10X line view
1. Select the Module 1 of

the DWLA10X card
2. Scroll the window up to the

bottom, select the DWDM
Line Selector panel and
click on Select Line


Issue 01
DWLA10X client view
1. Select the Module 2

of the DWLA10X card

Rate Selector panel and
click on Modify


Issue 01
Removing a board: example 1
1. Select a Board
2.Click on Remove
3.Click on YES to confirm the choice

Warning for Remove function: there are five main reasons for which Remove, Modify, Set commands are
refused:
A PM measurement is active on a TP in the board;
The Board contains a TP used as clock source;
The board contains a TP with cross-connection
The board contains LAP-D
The board contains loopback
The PP10AD has any configured port
In all these cases Remove request is refused

Issue 01
Removing a board: example 1 [cont.]
4. Select a Board once again
5. Click on Delete


Issue 01
Removing a board: example [cont.]
The slot becomes empty with EQPT

alarm (minor)


Issue 01
Removing a board: example 2
1. Select a Board
2.Click on Remove
3.Choose the command mode

Warning for Remove function: there are five main reasons for which Remove, Modify, Set commands are
refused:
A PM measurement is active on a TP in the board;
The Board contains a TP used as clock source;
The board contains a TP with cross-connection
The board contains LAP-D
The board contains loopback
The PP10AD has any configured port
In all these cases Remove request is refused

Issue 01
Removing a board: example 2 [cont.]
4. Select a Board once again 5. Click on Delete
The slot becomes empty with EQPT

alarm (minor)


Issue 01
Remote Inventory
To display the remote inventory data of the selected board:
1. Select a board: click on

with the mouse pointer.
2. Select Remote Inventory


Issue 01
Global inventory storage
To display the global remote inventory data:
1. Select a Shelf 2. Click on “Remote

Inventory”


Issue 01
7 Equipment Protections (EPS)


Issue 01
EPS Introduction
The hardware failures causing automatic EPS protection switch can be

grouped as:
failures causing the internal equipment link loss as powering KO, Clock loss,
card missing
failures causing traffic loss (the internal link is preserved) as for instance
unlocked oscillator, electrical interface defective and so on.
failures not causing traffic loss nor internal link loss but causing loss of
management as internal bus failures.
Moreover some failures can cause equipment malfunctioning (as remote

inventory fault, laser degrade, loss of DC/DC synchronism). These
hardware faults are signaled to the management system and do not
provoke an automatic switch.


Issue 01
EPS Introduction [cont.]
EC is designed to permit 1:1 protection.

SC is designed to permit 1:1 protection.
PP10GATM is designed to permit 1:1 protection: the protection group
should be created before.
LOA10G is designed to permit 1:2 protection in SDH applications: two
LOA10G protection group are supported in the TSS-320 Shelf System and
one only in the TSS-160 Shelf System.
General characteristics of the EPS protection mode are:
Switching criteria: card-missing, card-fail
Switching time: max 50ms
Operation mode:
1+1 EPS always non revertive
N+1 EPS revertive / not revertive ; WTR configurable from 1min to 15min (LOA)
External commands to control the switch position: Manual, Lockout,

Release
The Matrix, the equipment controller and LOA EPS are automatically
provisioned.
Any single failure in a protected module shall be detected and switch to the redundant copy within 60 ms
(normally 10 ms for detection, 50 ms for switching).
The NE is designed with a single control bus that connects the two MT320 (MT160 in TSS-160 shelf) and all
the others boards. No control bus switch is possible.
No MT320 (MT160), EC320, LOA10G or PP10GATM switch is done as a consequence of a bus failure.

Issue 01
Protected cards and board position
Equipment Controller EC320 :

EPS protection 1+1 (not REVERTIVE)
MATRIX MT 160/320:
PP10GATM (PP10AD):
Lower Order Adapter (LOA):

EPS protection 1:N with N=1 or 2 (REVERTIVE)

Removing or reinserting an EC module shall not cause a traffic interruption.

The loss of a first level controller, or the loss of availability of the local NE database shall not cause a
traffic interruption, whether the controller is protected or not.
Lower order adapter cards can be 1:N (N=2 max) EPS protected; up to two working LOA10G share one
protecting LOA10G.
As regard the PP10GATM protection Group for a one for one redundancy (duplex), both the equipment card
that are the group components should be specified: the protection slot is the one that has the higher AID
position.
The EPS protection has the following characteristics:
Architecture: 1:N (N=2)
Switch type: UNIDIRECTIONAL Operation type: Revertive
Switching time: <50ms
Triggers: Equipment failures
WTR (Wait To Restore): 5min

Issue 01
EPS information
Select Protection
EQPS in the menu item: the list of the already
configured EQPS protection is displayed

The EQPS tab displays one table for each 1:1 protection that are in the node. Each table contains the
following parameters:
Protected Equipment: Specifies the Primary and Spare units that are 1:1 protected
Protecting Equipment: Specifies the type of units that is 1:1 protected. Each one is identified by <unit
acronym> - <rack> - <shelf> - <slot> where is housed (e.g., MT320-1-1-10)
Active Equipment: Specifies the name of the equipment that is currently active and in use.
Active Switch Command: Specifies the switch command that is used if the second level controller

Issue 01
EPS information [cont.]
Role and Status are displayed in the window


Issue 01
Equipment Controller EPS
Selecting the Equipment Controller protection, there are no parameters

that can be configured, as this type of protection is always a non-
revertive protection. It is anyway possible to force a protection switch
State of EPS protection: Active (role: worker)
Click on status to open the command menu

The Equipment Condition Type RAIDSYNC associated to the Standby EC320 should arise the SST to PSI on
both the EC320, in order to allow the prevention of any Switching during a RAIDSYNC Condition.
If the EC320 stand-by slot is provisioned, any restart of any of the two EC320s causes a full realignment
between the two hard-disks and this takes about 30 minutes during which the RAIDSYNC Condition Type is
up; the same full realignment also happens when an EC320 in slot 20 is created
If the RAID mirroring fails after the RAIDSYNC phase is ended, the remote hard disk is un-mounted and the
EC320 stand-by will no-more be available for EQPS

Issue 01
Equipment Controller EPS command
1. Select the Command Mode
2. Click on “Manual Switch” to execute the command

The panel shows the following field:

Access Identifier specifies in the <unit acronym> - <rack> - <shelf> - <slot> format.
Primary/Secondary State
Command Mode combobox allows to change the status of the unit. The values are:
NORM (normal)
FRCD (forced)
The panel has the following hyperlinks:
Cancel hyperlink is used to delete the operation in the page and came back to the previous page.
Manual Switch hyperlink is used to manually switch the real status shown in the associated table.
The table contains the following columns:
Slot specifies the slots where the protected and protecting units are housed.
Role specifies the real role of the unit. This column is related to the next column. The values are:
Protecting
Working
Equipment Protection Status specifies the real status of the unit. This column is related to the
previous column. The values are:
Standby
Active

Issue 01
Matrix EPS
Selecting the Matrix protection, there are no parameters that can be

configured, as this type of protection is always a non-revertive
protection. It is anyway possible to force a protection switch
Click on status to open

the command menu State of EPS protection: Active (role: worker)


Issue 01
Matrix EPS command
Click on Manual Switch to perform the EPS switch


NORM (normal)
FRCD (forced)
Protecting
Working
Equipment Protection Status specifies the real status of the unit. This column is related to the previous
column. The values are:
Standby
Active

Issue 01
PP10GATM EPS
PP10GATM card can be 1+1 EPS protected. The protection is triggered

by the detected card failures, or can be forced via manual command
The protection/spare unit has to be
plugged in an higher slot number
with respect the working/main one.
1. Select the working

board (board with
lower slot number) 2. Click on Create EQPS
3. Click on Select to
choose the spare unit

The positions of the main and the spare units are:

and 19.

Issue 01
PP10GATM EPS [con’t]
4. Choose the spare unit and then click on Apply & Exit
5. Click on Save
Clock on Delete EQPS to delete the EQPS protection scheme


Issue 01
PP10GATM EPS command
Click on Equipment Protection status

to open the command menu


Issue 01
PP2G5UGW EPS
PP2G5UGW card can be 1+1 EPS protected. The protection is triggered

by the detected card failures, or can be forced via manual command
The protection/spare unit has to be
plugged in an higher slot number
with respect the working/main one.
1. Select the working

board (board with
lower slot number) 2. Click on Create EQPS
choose the spare unit

The positions of the main and the spare units are:

and 19.

Issue 01
PP2G5UGW EPS [con’t]
4. Choose the spare unit and then click on Apply & Exit
5. Click on Save
Click on Delete EQPS to delete the EQPS protection scheme


Issue 01
PP2G5UGW EPS deletion
1. Click on Equipment Protection status

2. Click on Delete EQPS to delete the EQPS protection scheme


Issue 01
PP2G5UGW EPS command
Click on Equipment Protection status



Issue 01
LOA EPS
Selecting the LOA protection, there are no parameters that can be

configured; as this type of protection is always a revertive protection.
It is anyway possible to force a protection switch. To open the menu,
select: Protection Equipment Protection
1. Open: Protection Equipment Protection


Issue 01
LOA EPS command
1. Select one card
“Inhibit Switch” correspond to

Lockout command
2. Select “Switch to Protection” or “Switch to

Working” according to the card role

NORM (normal)
FRCD (forced)
Protecting
Working
Equipment Protection Status specifies the real status of the unit. This column is related to the
previous column. The values are:
Standby
Active

Issue 01
LOA EPS deletion
Before deleting the last working card,

1. Select the protecting board it’s necessary enable the “Inhibit
Switch” command on the protecting
card, remove this card and then
remove the last working card
2. click on “Inhibit Switch”


Issue 01
LOA EPS deletion [cont.]
Check the presence of PSI
state in the secondary
state of protecting board
3. Select the protecting board once again
4. Click on “Remove” 5. Click on “Delete”


Issue 01
End of Module
Operator Interface-NE


Issue 01
32
Section 3
NE Operation
Module 2
Operator Interface-SDH WDM features
Issue 01
1850 TSS-320 & 1850 TSS-160

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

Issue 01
Blank Page

NE Operation Operator Interface-SDH WDM features
Document History

Issue 01
Module Objectives
Explain how to create cross connections & protected cross connections

Describe the APS protection
Explain how to Manage the loopbacks
Explain how to perform the NE synchronization


Issue 01


Issue 01
Table of Contents
Page
1 Cross Connections 7
1.1 Introduction 8
1.2 Creation & Mgmt 15
1.3 Example 1: HO pass through (AU4-AU4) 23
1.4 Example 2: LO pass through (TU12-TU12) 29
1.5 Example 3: EoS connection (AU4-VCG port) 51
2 SNCP Protection 57
3 Optical connection 69
4 Linear MSP Protection 101
5 Loopback 113
6 Synchronization 133
7 OTN management 175


Issue 01
Page


Issue 01
1 Cross Connections

NE Operation Operator Interface-SDH WDM features Section 3 Module 2 Page 7

Issue 01
1.1 Introduction


Issue 01
1.1 Introduction
Matrix role
A not-blocking matrix can interconnect all the afferent SDH with any other
SDH.
All ports are connected to the matrix in the same way, without any difference
between the port types.
Connections are always performed by the matrix: no direct connection between

two ports is allowed.
There is no constraint for the timeslot change for each cross-connection (e.g.
AU-4#n of an SDH port can be cross-connected to AU-4#m of another SDH port,
with “n” and “m” generic)
Several types of connections may be established, such as: Unidirectional Point

to Point, Bidirectional Point to Point, Protected.
AU4-4c, AU4-16c and AU4-64c concatenated signals can also be cross connected
between any STM-4, STM-16 and STM-64 ports.


Issue 01
1.1 Introduction
SDH-ETSI Multiplexing Structure
xN x1
STM-N AUG AU-4 VC-4 C-4 140 Mbit/s
x3 34 Mbit/s
x1
TUG-3 TU-3 VC-3 C-3 OR
45 Mbit/s
x7
x1
TUG-2 TU-12 VC-12 C-12 2 Mbit/s
PDH + STUFFING BITS
SIGNAL LEVEL-n x JUSTIFICATION
C-n
VCn-POH C-n
= POINTER
TU-n
POINTER
VC-n = MAPPING
= ALIGNMENT
TU-n = MULTIPLEXING

The Mapping Scheme is the basis of the SDH. It represents all functions needed to introduce a PDH signal
into an SDH Network.
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:
C-n = Container of order n : this is the information structure carrying a synchronous payload.
VC-n = Virtual Container of order n: this is the information structure formed by C-n+ Path Over Head
(POH)
TU-n = Tributary Unit of order n: information structure formed by VC-n + Pointer
AU-4 = Administrative Unit of order 4: information structure which provides for adaptation
(synchronization) between the Virtual Containers (VC-n) and the multiplexing plane (= STM-N); it is
formed by VC-4 + Pointer
POINTER = Indicator of off-set for VC-n ( it indicates the start position of VC-n inside the payload)
TUG/AUG = Tributary Unit Group / Administrative Unit Group = a set of n x TU / n x AU
TU12 is identified by (k,l,m) with: k= TUG3# (1...3); l=TUG2# (1...7); m=TU12# (1...3)

Issue 01
1.1 Introduction
Termination points to cross-connect
SDH Network
SDH SDH SDH

port port Client
port port SDH
Network
Termination Points: Termination Points:

AU4 AU4 VC4 AU4
Pass-through AU4-nc AU4-nc (n=4,16,64) VC3 TU3 Drop-insert
TU3 TU3 VC12 TU12
TU12 TU12
Client
port
SDH
Client Network
port Client port:
• PP10MS remote port
Termination Points:
VC4 VC4
VC
VC3 VC3
connection
VC12 VC12


Issue 01
1.1 Introduction
Termination points to cross-connect
HO Matrix LO Matrix
VC4
STM-N
STM-N AU4 AU4-AU4 TU-VC VC12
CXC PP10MS
PP10MS
Port
Port CXC
VC3
TU-TU VC-VC PP10MS
AU4-VC4 PP10MS
CXC CXC
CXC
STM-N
STM-N AU4 VC4
VC4-VC4 PP10MS
PP10MS
Port
Port
CXC
Matrix can cross-connect:

• Lower Order (LO) termination points: VC12, VC3, TU12, TU3
• Higher Order (HO) termination points: VC4, AU4, AU4-nc
A not-blocking matrix can interconnect all the afferent SDH signals with any other SDH or Data (PP10MS)
port.
All ports are connected to the matrix in the same way, without any difference between the port types.
Connections are always performed by the matrix: no direct connection between two ports is allowed.
There is no constraint for the timeslot change for each cross-connection (e.g. AU-4#n of an SDH port can be
cross-connected to AU-4#m of another SDH port, with “n” and “m” generic)
Several types of connections may be established, such as: Unidirectional Point to Point, Unidirectional Point
to Multipoint, Bidirectional Point to Point, Protected.
AU4-4c and AU4-16c concatenated signals can also be cross connected between STM-16 and STM-64 ports.

Issue 01
1.1 Introduction
1850 TSS-320 / TSS-160 switch capacity
TSS-320
TSS-320
TSS-160
TSS-160


Issue 01
Blank Page


Issue 01
1.2 Creation & Mgmt


Issue 01
1.2 Creation & Mgmt
TDM connection view (Search)
This menu allows to manage (provisioning, service type etc.) the

client/line traffic.
TDM Search-Allows to set the SDH service
TDM Create-Allows to configure the SDH service
Once the search is performed, selecting the “Search” option, the list of
all the connections matching the defined criteria is displayed.
1. Choose the search criteria
2. Click on Search
NE Operation Operator Interface-SDH WDM features Section 3 - Module 2 - Page 16
The Search tab displays the Search Cross-Connections panel that contains the following:
Search: Allows to select XConnection or Protection legs:
Using Specific VC Type Commands (RTRV-CRS-[LO]VCn and RTRV-CRSPROT-<rate>) for a searching
identified by the STSn specific type declared in the next STS Type combo-box.
Using Circuit Identifier (RTRV-CKTID) for a searching identified by the circuit identifier (TID).
Using Generic STM Commands (RTRV-CRS) for a searching identified by the generic type of the STMn.
Its selection arranges the panel accordingly.
VC Type: The combo-box allows to select one of the items VC4, VC44C, VC416C, VC464C in order to
chose the hierarchical level of the signal.
Retrieve Command: Specifies the TL1 Command used for the searching procedure set in the Search
Type field.
VC Access Identifier: The entry box allows to select one of the available STMn. For the information
relevant to the procedure.

Issue 01
1.2 Creation & Mgmt
TDM connection view (Search) [cont.]
The list of TDM CXC appears in the window


Issue 01
1.2 Creation & Mgmt
TDM connection view (Search) [cont.]
From the connection TDM view it is possible to delete the cross-
connection, to create a new one or to modify (split, join and protect)
the connection by selecting it.


Issue 01
1.2 Creation & Mgmt
TDM connection creation
Can be created four different types of connections:

Unidirectional (1WAY) (this option is also used in case of broadcast
connection, where you create many unidirectional (1WAY) connections with
the same “from” and different “to”)
Unidirectional Protected (1WAYSNCP)
Bi-directional (2WAY)
Bi-directional Protected (2WAYSNCP)
1. Open Connection TDM Create menu
2. Select the CCT-Type
3. Choose the VC Type

and the direction
4. Click on Continue to continue


Issue 01
1.2 Creation & Mgmt
TDM connection creation [cont.]
Selecting the type of TDM connection required, some of the pieces of

information can be hidden.
7. Click on Set to continue
6. Click on ADD to submit the choice

5. The user must specify the complete AID of
the end point (i.e: STM1AU4-1-1-23-2-1)


Issue 01
1.2 Creation & Mgmt
8. Click on Select to specify the
second point of the connection

the end point (i.e: STM1AU4-1-1-23-6-1) 10. Click on ADD to submit the choice


Issue 01
1.2 Creation & Mgmt
12. Choose the cross Connection

Type: 1WAY or 2WAY
13. Click on Create
The XC appears in the window


Issue 01
1.3 Example 1: HO pass through (AU4-
AU4)


Issue 01
1.3 Example 1: HO pass through (AU4-AU4)
XC HO configuration
To create the cross connection, open: Connection TDM Create
1. Configure the cross connection

parameters as reported in the picture


Issue 01
XC HO configuration [cont.]



Issue 01

the end point (i.e: STM1AU4-1-1-23-6-1) 8. Click on ADD to submit the choice


Issue 01
10. Choose 2WAY CC Type
11. Click on Create
The XC appears in the window


Issue 01
Blank Page


Issue 01
1.4 Example 2: LO pass through (TU12-
TU12)


Issue 01
1.4 Example 2: LO pass through (TU12-TU12)
XC LO configuration steps
To create LO pass-through cross connection, are necessary four steps:

1) HO cross connection between STM-1 (sl12-p1) card and LOA card (sl.21);
2) HO cross connection between STM-1 (sl12-p2) card and LOA card (sl.21);
3) Define the structure of the MVC4s
4) LO cross connection in LOA card.
LOA
Slot 21
STM-1 MT320LO
STM-1
Slot 12-p1 AU4#1 AU4#1 Slot 12-p2
Slot 10
TU12#1 TU12#1

LOA is used to process LO tributaries of HO payload: it consists of assembly/disassembly

Each LOA provides a pool of 64 MVC4 that are determined according an incremental rule from 1 to 64.
If more MVC4 are needed, the second LOA card provides another pool of 64 MVC4, numbered from 65 to
128.
Each LOA can support 10G of traffic (totally 40G).

Issue 01
HO XC between STM-1 (sl12-p1) and LOA (sl.21)



Issue 01
HO XC between STM-1 (sl12-p1) and LOA (sl.21) [cont.]
Slot Port AU-4

Slot Port AU-4


Issue 01
7. Select the LOPOOL (1-1-1) 8. Click on ADD to submit the choice


Issue 01
11. Click on Create
We cross connect the STM-1 board with

the LOPOOL. You have to select always
LOPOOL-1-1-1 and the system recognize
dynamically the first available free slot
(In this case MVC4-1-1-21-1).

We cross connect the STM-1 board with the LOPOOL. You have to select always LOPOOL-1-1-1 and the
system recognize dynamically the first available free slot (In this case MVC4-1-1-21-1).

Issue 01
HO XC between STM-1 (sl12-p2) and LOA (sl.21)



Issue 01



Issue 01

7. Select the LOPOOL (1-1-1) 8. Click on ADD to submit the choice


Issue 01

11. Click on Create
We cross connect the STM-1 board with

the LOPOOL. You have to select always
LOPOOL-1-1-1 and the system recognize
dynamically the first available free slot
(In this case MVC4-1-1-21-2).


Issue 01
Low Order structure
Since the system will provision as default the MVC4 like TU#3, and we
want a VC12 cross connection, we will have to terminate ALL the MVC4
involved :
1. Select LOA in the slot 21

2. go down the window and
select MVC4-1-1-21-1


Issue 01
Low Order structure [cont.]
In the new window modify Low Order structure:
4. Click on Modify


Issue 01
5. In our example we modify the first
VC3 of the MVC4-1-1-21-1 as VC12.
6. Click on save


Issue 01
The new structure

7. Click on save

Issue 01
The same thing must be done for the MVC4-1-1-21-2. In our example
We modify the first VC3 as VC12.
1. Select LOA in the slot 21
2. go down the window and

select MVC4-1-1-21-2


Issue 01
In the new window modify Low Order structure:
4. Click on Modify


Issue 01
5. In our example we modify the first VC3 of the MVC4-1-1-21-2 as VC12.
6. Click on save


Issue 01
The new structure

7. Click on save

Issue 01
LO XC between MVC4-1-1-21-1 and MVC4-1-1-21-2
Now we can cross connect the VC12 elements.



Issue 01
LO XC between MVC4-1-1-21-1 and MVC4-1-1-21-2 [cont.]
TUG-3 TUG-2 TU-12
3. The user must specify the complete AID of the

end point (i.e: MVC4TU12-1-1-21-1-1-1-1)


Issue 01

7. Select the MVC4TU12-1-1-21-2-1-1-1) 8. Click on ADD to submit the choice


Issue 01

11. Click on Create
The list of TDM CXC appears in the window


Issue 01
1.5 Example 3: EoS connection (AU4-
VCG port)


Issue 01
1.5 Example 3: EoS connection (AU4-VCG port)
Select the VCG port
This option allows to create the cross-connection between the VC4s belonging to
the logical VCGroup and the TDM containers
Open the VCGroup window:
1. Select PTF
2. Select the specific VC4 to

3. Click on Continue be cross-connected

The operator must configure the option for all members belonging to the logical VCGroup

Issue 01
PTF connection window
It is suggested to modify the Threshold

parameter (to “00.00”) in order to set
immediately In Service the facility
4. Select PTF
Connection


Issue 01
Select the AU-4




Issue 01
Create the TDM XC
10.Click on Create


Issue 01
Blank Page


Issue 01
2 SNCP Protection


Issue 01
2 SNCP protection
SNCP Introduction
The system supports Sub-Network Connection Protection (SNCP) node

configurations for path protection. SNCP is available on all line rates.
One SNCP node is formed by using two STM-n modules in adjacent slots
of the NE.
Data is transmitted simultaneously along the working and protection
lines of the ring. The traffic for each line is transmitted in the
clockwise and counterclockwise directions and is received by both
facilities of each SNCP node. A path selector is provisioned in each two-
way protection group and selects the best signal. If a fiber cut occurs,
the received signals at the protection and working lines of the node are
interrupted causing the path selectors at each node to select the
alternate facility in order to automatically restore traffic. See figure in
the next page


Issue 01
2 SNCP protection
SNCP scheme
NE 3
Side B Side A
PASS-THROUGH
Bridge Side A Side B
NE 2 PASS-THROUGH NE 4
Side B Side A
Switch
Side A Side B
SWITCH
NE 5
NE 1 PASS-THROUGH
Side B
Side A
BRIDGE


Issue 01
2 SNCP protection
SNCP Configuration
To configure the SNCP I/N protection, it is enough create a protected

XC.
To create the cross connection, open: Connection TDM Create



Issue 01
2 SNCP protection
SNCP Configuration [cont.]

main end point (i.e: STM1AU4-1-1-23-2-1)


Issue 01
2 SNCP protection

spare end point of the connection

spare end point (i.e: STM1AU4-1-1-23-6-1) 8. Click on ADD to submit the choice


Issue 01
2 SNCP protection
10. Click on Select to specify the To

end point of the connection

the spare end point (i.e: STM1AU4-1-1-23-7-1) 12. Click on ADD to submit the choice


Issue 01
2 SNCP protection
14. Choose the CCT: 1WAYSNCP or 2WAYSNCP
15. Configure the Revert Mode (Y or N) and

the protection Type (SNCI or SNCN)
16. Click on Create
In the other fields of the Provision Connection Path Protected panel select the default values clickin on the
Default hyperlink:
Revertive Mode: = Possible values:
N (it indicates whether or not to make revert to protected once the protected comes into service and
the traffic is on protecting).
Y (Yes revert to protected / FROMPED)
Revert Delay Time [min]: = 5 (wait to restore time, if Revertive Mode =Y in minutes. If Revertive
Mode=N it does not have any effect at the NE behaviour.). Possible values: in the 0 to 15 range.
Hold Off Time [millisec]: = 0 (time for automatic switching. The values are in milliseconds). Possible
values: 0, 30, 50, 70, 100, 300, 500, 700, 1000, 3000, 5000, 10000 milliseconds.
Protection Type: = SNCI (SubNetwork Connection Protection with Inherent monitoring) or SNCN
(SubNetwork Connection Protection with Non-intrusive monitoring).

Issue 01
2 SNCP protection
Close the command result window
The SNCP appears in the window

Current Active Protection: it displays always the current SNCP status of the Cross Connection.
NR No SNCP Switch, working VCn path is OK

Auto An automatic SNCP Switch was performed because of a failure condition
MAN / FRCD SNCP Switch because of an operator command
Lockout No SNCP Switch is possible any more because of an operator command
Currently requested: Indicates the kind of signal error.
SF / SD: Signal Failure (alarm was detected) / Signal Degrade (many bit errors)

Issue 01
2 SNCP protection
SNCP Protection commands
1. To operate a command, select the protected Xc and
then click on Operate Path Protected
2. Choose the command and

the direction
3. Click on Create
The command resalt appears in the window

Manual Switch has lower priority than the automatic switch; you can use Manual Switch command to
avoid problems with the traffic in case of failure.
“Force to” has higher priority than the Automatic Switch; “Force to” is used for Maintenance.
Lockout has higher priority than Force, and inhibits the protection also in case of failure.
Release: it removes the previous command.

Issue 01
2 SNCP protection
SNCP Protection deletion
1. To delete the SNCP protection, select the protected

Xc and then click on Delete Path Protected
2. Choose the CCT: 1WAYSNCP

or 2WAYSNCP
3. Click on YES to confirm the operation


Issue 01
Blank Page


Issue 01
3 Optical connection


Issue 01
Introduction
The optical connections are related to the management of cabling

connections between the following DWDM hardware items:
LOFA (In Line Optical Amplifier)
MUX/DEMUX 8 channels
1POTU2/1POTU2XB
DWLA10GX (XFP Transponder 10Gb/s)
External Tributary Card
The optical connections are classified into four classes, based on the
possible DWDM configurations on the node. All Optical Connections are
Bidirectional (i.e. 2WAY); they represent two physical fibers and logical
connections between bidirectional optical ports.
The four configurations are:
Line: this connection establishes if the DWDM line is amplified or not in the
Node itself; it indicates an optical connection between a MUX and the Line
amplifier. If the line is not amplified, this optical connection is not present.


Issue 01
Pass-through: this connection configures the pass-through between MUX

channels. This optical connection is not supported in the line terminal
configuration.
Cascade: this connection configures the cascade of MUX/DMUX devices.
Cascade has to be configured when the DWDM system operates with channels
supported not only by a single type of MUX
ADDROP: this connection configures the channel added/dropped in/from
DWDM system. Logically the optical connection moves from MUX Channel to
line port of a Transponder or other tributary card.


Issue 01
Optical Cross-connect ports
The optical cross-connection represents a cable between two specific

ports, which are available on each DWDM Hardware item.
Line Amplifier card (i. e. LOFA1111) supports the ports:

LOFOTSPORT, port of DWDM line (Sink and Source);
LOFOSCPORT-IN, Sink port of Supervisory channel signal;
LOFOSCPORT-OUT, Source port of Supervisory channel signal;
LOFVOAPORT, port for accessing VOA device (Sink and Source);
LOFOMSPORT, port for connecting LOFA with MUX/DEMUX card (Sink and
Source).
MUX/DEMUX card (i. e. OMDX8100) supports the ports:
OMDOMSPORT, port for connecting MUX/DEMUX card to LOFA card (Sink and
Source);
OMDBANDPORT, port of Bundle signal (Sink and Source);
OMDOCHPORT, port of single channel signal (Sink and Source) to be
added/dropped or to be clear channel pass-through.


Issue 01
Optical Cross-connect ports [cont.]
Transponder card (i. e. DWLA10X) supports the ports:

OTPORT-L1, port for connecting single channel added/dropped from
MUX/DEMUX card (Sink and Source);
OTPORT-C1, port of client signal (Sink and Source).
OTU2 Tributary card (i. e. 1POTU2TDM) supports the port:
OTPORT-L1, port for connecting single channel added/dropped from
MUX/DEMUX card (Sink and Source).
Optical Connections uses a subset of the ports above listed.

The ports involved in the optical connections are:
LOFOMSPORT,
OMDOMSPORT,
OMDBANDPORT,
OMDOCHPORT
OTPORT.


Issue 01
Optical Cross-connect ports [cont.]

The tables indicates which denies shall be implemented if the connection set up attempt is impossible or
inappropriate:
"N. A.“: not allowed
"Deny": it's not possible to set up a connection, where from and to belongs to the same port type (not
only port instance); for example I can not set up a connections among to omdoms ports; the only
exception is constituted by the omdband port for the bundle pass-through.
"If Freq Match“: the frequency of channel in pass-through or added/dropped shall be the same.
"If not PC (L2)" indicates a check which avoids a cascade connection, if any other optical connection has
been already set up on MUX on band L2. This check is not related to bundle pass-through connection of
MUX on band L1, which is covered by the general one: port already involved in another optical
connection. The check covers all optical connections set up on MUX L2 other than omdoms port.

Issue 01
Optical connections: example 1
Pass-through O-CONN
ADD/DROP O-CONN


Issue 01
Optical connections: example 2
Cascade O-CONN
Line O-CONN


Issue 01
Line optical connection
In order to define ots facility, the configuration of LOFA card is not

enough; it's also needed to which MUX device the LOFA card is
associated. This association is provided by optical connection with
optical class equal to LINE; note that line connection actually
correspond to a cable connection that operator must set up between
LOFAOMSPORT of LOFA card and the OMDOTSPORT of the MUX card.
If a line connection is configured, this implies ots facility defined on
LOFA, with DOWN pointer pointing to oms defined on MUX card.
Otherwise ots facility is defined on MUX card itself and DOWN pointer
points to oms as well.


Issue 01
Line optical connection: creation
1. Open Connection Connection menu
2. Click on Create
3. Click on Select to choose the From

direction: LOFOMSPORT for
amplifier and OMDOMSPORT for
OMD8100 card
4. Select LOFA card

5. Select the LOFOMSPORT port

Issue 01
Line optical connection: creation [cont.]
6. Click on Select to choose the To

direction: LOFOMSPORT for amplifier
and OMDOMSPORT for OMD8100 card
7. Select the OMDX8100 card
8. Select the OMDOMSPORT port


Issue 01
Line optical connection: creation [cont.]
9. Click on Save
The display the created optical connection,

open Open Connection Connection menu
and then click on Search


Issue 01
Line optical connection: deletion
2. Click on Search
3. To delete a Service, tick the box and click on Delete


Issue 01
Pass-Through connection
In DWDM system a MUX device can be used as line terminal, where the
channels are only added/dropped, or as drop&continue, where the
channels are added/dropped and passedthrough. In the first
configuration, MUX operates as stand alone and there isn' t any optical
connection to be set-up among different MUX. This configuration is
represented, in transmission point of view, by DOWN pointers of
omsband and of omsoch facilities, which are not added/dropped,
pointing to NULL. In the second configuration, MUX operates in
tandem with another MUX on the opposite side and there are optical
connections to be set-up among them. Bundle connectivity can be set-
up for passing-thorugh all channels which are outside the working
spectrum of the MUX, this is configured by a cable connection among
OMDBANDPORT of MUX on west side and OMDBANDPORT on East side.
Single channel connectivity can be set-up for passing-thorugh specific
channel which is inside the working spectrum of the MUX, this is
configured by a cable connection among OMDOCHPORT on MUX on West
side and OMDOCHPORT of MUX on East side.


Issue 01
Pass-Through connection [cont.]
Pass-through configuration is represented, in transmission point of

view, by DOWN pointers of omsband and of omsoch facilities, which
are not added/dropped, pointing to the omologous facilities
instantiated by the MUX of the opposite side.

Line amplifier connected to MUX port of the West side of pass-through configuration;
MUX card of the East side doens't have any line amplifier;
2 channels of L1 band are in pass-thorugh;
2 channels of L1 band of West side are add/dropped towards two DWLA10X cards;
2 channels of L1 band of East side are add/dropped towards respectively DWLA10X and OTU2TMD card;
Bundle channels (i.e. all channels other in L1 band) are in pass-through.

Issue 01
Pass-Through connection: creation
2. Click on Create
3. Click on Select to choose

the From direction:
OCHPORT for channel
pass-through and
OMDBAND port for
external bandwidth
4. Select the first OMDX8 card 5. Select the OMDOCHPORT and the channel

Issue 01
Pass-Through connection: creation [cont.]
6. Click on Select to choose the To direction:
OCHPORT for channel pass-through and
OMDBAND port for external bandwidth
7. Select the second OMDX8100 card (the

OMDX card used for the To direction
can’t the same of the From direction)
8. Select the OMDOCHPORT and

the channel (the channel
must be the same of the
From direction)

Issue 01
Pass-Through connection: creation [cont.]
9. Click on Save



Issue 01
Pass-Through connection: deletion
2. Click on Search


Issue 01
ADD/DROP connection
Independently if the MUX is line terminal or in pass-through, channels

can be added and dropped in the DWDM line. For the adding/dropping
of a single channel, a cable connection can be set-up among
OMDOCHPORT of MUX and OTPORT of the tributary Card. The
configuration of add/drop connection determines the creation of
omsochif facility associated to MUX adding/dropping the channel;
omsochif points with UP pointer the connectable port omsoch facility
and viceversa omsoch points with DOWN pointer to omsochif. This last
one points with DOWN pointer to och faciliity defined on Tributary Card
and viceversa och points with UP pointer omsochif.


Issue 01
ADD/DROP connection [cont.]

2 channels of L1 band of West side are add/dropped towards two DWLA10X cards;
2 channels of L1 band of East side are add/dropped towards respectively DWLA10X and OTU2TMD card;

Issue 01
ADD/DROP connection: creation
2. Click on Create

the From direction
4. Select the OMDX8 card 5. Select the OMDOCHPORT and the channel

Issue 01
ADD/DROP connection: creation [cont.]

the To direction
7. Select the transponder card
8. Select the OTPORT (Line)


Issue 01
ADD/DROP connection: creation [cont.]
9. Click on Save



Issue 01
ADD/DROP connection: deletion
2. Click on Search


Issue 01
Cascade connection
Two MUX cascaded shall be represented, in terms of facilities, as a

single one with doubled channels. Cascade connection allows the
distinction between one oms and 8 omsoch facilities for each MUX, and
one oms and 16 omsoch facilities associated to the first MUX of the
cascade. In TSS320 DWDM system, the first OMDX8100 to be cascaded is
the one operating in L1 band, and the second one is operating in L2
band. When MUX L1 is cascaded, it has to instantiate 1 oms and 16
omsoch facilities, while the MUX L2 has not to instantiate any facility.
Only once cascade connection is configured between MUX L1 and MUX
L2, the system is able to instantiate facilities properly.
It’s required that no other optical connections have been configured on
MUX L2.


Issue 01
Cascade connection [cont.]
L2 band
L1 band

The above figure reports an exemplified equipment view of the configuration:

Line amplifier connected to L1 MUX port of the cascade configuration;
MUX card of L1 band has been cascaded to MUX card of L2 band;
2 channels of L1 band are add/dropped towards two DWLA10X cards;
3 channels of L2 band are add/dropped towards the corresponding DWLA10X cards;
Bundle channels (i.e. all channels other in L1 band) are not in pass-through.

Issue 01
Cascade connection: creation
2. Click on Create
3. Click on Select to choose the From direction:

OMDBANDPORT for OMD8100 in L1 band and
OMDOMSPORT for OMD8100 in L2 band
5. Select the OMDBANDPORT
4. Select the OMDX8 L1 band card


Issue 01
6. Click on Select to choose the To direction:
OMDBANDPORT for OMD8100 in L1 band and
OMDOMSPORT for OMD8100 in L2 band
7. Select the OMDX8 L2 band card
8. Select the OMDOMSPORT


Issue 01
9. Click on Save



Issue 01
Cascade connection: deletion
2. Click on Search


Issue 01
Blank Page


Issue 01
4 Linear MSP Protection


Issue 01
4 LINEAR protection
Introduction
The system supports 1+1 Linear Automatic Protection Switching (APS)

for STM-1, STM-4, STM-16, and STM-64 facilities. In 1+1 LINEAR, the
head-end signal is permanently bridged to both the working facility and
the protect facility. At the tail end, both the working facility and the
protect facility are monitored independently for failures. The receiving
NE normally selects the working facility. In the event of failure, the
protect facility is automatically selected. 1+1 LINEAR is a local action
that involves no changes elsewhere in the network.
Features:
Revertive or non-revertive switching
Revertive—Service is switched back to the working facility after the condition that
caused the automatic switch clears and the Wait to Restore (WTR) time has
expired.
Non-revertive—Service is switched back to the working facility only when the
protect facility becomes unavailable or when a manual protection switch command
is received.
Unidirectional operation—The tail-end signal switches only at the near-end
NE that detects the failure. Refer to figure 4-11. The bold lines indicate the
active traffic path.

Linear protection switching scheme is a method for traffic recovery applicable to ‘point-to-point’ (i.e.
linear) network topology.
It is a ‘dedicated’ mechanism where one ‘protection’ resource is used for protecting one ‘working’ resource
(i.e. 1+1). It applies to STM-N synchronous interfaces.
Switching might be caused by line failure or hardware faulty on another system connected to the one being
considered.
The switching criteria are: Loss of Signal, Loss of frame, MS-AIS/AIS-L, Excessive BER/Line BER and (user
provisionable) Signal Degrade.
This feature permits a 1+1 protection in a linear link, where a path signal is protected by another dedicated
path which carries the same signal. The protection can be set both in single and in dual ended mode.
In single ended (UNI) mode (unidirectional) the protection is accomplished by switching only the signal
affected by the failure.
In dual ended (BI) mode (bidirectional) the protection is accomplished by switching both the affected and
the unaffected signals. The switching signalling is carried over the APS channel (K1 and K2 bytes), using
the K-byte protocol.

Issue 01
4 LINEAR protection
LINEAR MSP Scheme
Figure 4-11.


Issue 01
4 LINEAR protection
LINEAR MSP Configuration
The LINEAR protection involves only SDH facilities. If no LINEAR

protections are active, the “Create” option allows for the creation of a
new protection group.
To open the LINEAR menu: Protection LINEAR MSP
1. Click on Create


Issue 01
4 LINEAR protection
LINEAR MSP Configuration [cont.]
Once the “Create” option has been selected, the working and the
protecting facilities must be provided
2. Choose the Revertive Mode: Y or N
3. Choose the Revert Delay

Time: 0 to 15 minutes (WTR)
4. Click on “Select” to
configure the protected card
5. Select the protected card

If the protection is configured as “Revertive”, the revertive time must be provided too.
In order to have the configuration stored on the system, the “Save & exit” or the “Save & Continue” option
must be selected.
The parameters involved in the configuration are:
FFP Access Identifier: Specifies the Access Identifier for Fast Facility Protection
Protection Type: Specifies the type of protection. The default values is Linear
Revertive Mode: The values are Y or N
Revertive Time (sec): The valid range is from 0-15 seconds
Protected Access Identifier: Specifies the Access Identifier for the protected resource
Protecting Access Identifier: Specifies the Access Identifier for the protecting resource
Protection Switching Direction: Specifies the switching direction. The values are UNI or BI

Issue 01
4 LINEAR protection
6. Click on “Select” to configure

the protecting card
7. Select the protecting card


Issue 01
4 LINEAR protection
8. Choose the Protection

Switching: UNI or BI
9. Click on Save


Issue 01
4 LINEAR protection
10. The protection scheme appears in the window


Issue 01
4 LINEAR protection
LINEAR MSP Protection command
To open the protection commands, select the APS scheme and click on
the FFP Access Identifier
1. Select the Linear MSP scheme
2. Choose the command

3. Click on Operate Switch

From the list under details it is possible change “Execute command”:

Lockout (lockout of protection) prevents the working channel from switching to the protection line.If
the working channel is already on the protection line, it is switched back to its working line.This is only
applicable to 1+1 system.
Forced PROTN: to switch from protected (main resource) to protecting unit (Spare resource). This
command is Y if no failure is present on protecting unit (BI only);
Forced WKG: switches the working channel back from the protection entity to working unless a request
of equal or higher priority is in effect.

Issue 01
4 LINEAR protection
LINEAR MSP Protection: modify option
This option permits to modify the revertive mode (Y or N) and the

Revert Delay Time. Open Protection Linear MSP menu and click on
“Search” button. Select the Linear MSP protection
1. Modify the revert mode and the WTR
2. Click on Save


Issue 01
4 LINEAR protection
LINEAR MSP Protection deletion
This option permits to delete the protection scheme. Open Protection

Linear MSP menu and click on “Search” button. Select the Linear
MSP protection scheme and then click on Delete
2. Click on Delete
1. Select the Linear MSP scheme


Issue 01
Blank Page


Issue 01
5 Loopback


Issue 01
5 Loopback
Loopback Introduction
Loopback definition
A loopback is a troubleshooting test in which a signal is transmitted
through a port unit to a set destination and then returned to the
originating port unit. The transmitted and received signals are
measured and evaluated by the user to ensure that the received signal
is accurate and complete when compared to the originating signal.
Loopback types
The system supports the following software-initiated loopback types at
the near end. Loopbacks at the far end are not supported.
Facility: loopback where the signal received at the port (port ingress
direction) is connected to the transmit side of the port (in ETSI region it
means LINE).
Terminal: loopback where the signal that is about to be transmitted (port
egress direction) is connected to the receive side of the port.
Loopbacks can be initiated, released and retrieved. A port under
loopback operation is not provisionable. Only one loopback can be
active on a facility.

Facility and terminal loopbacks may be initiated independently on the East and West STM-n ports of a MS-
SPRING (SPRING), a Sub-Network Connection Protection (SNCP) and Linear MSP.

Issue 01
5 Loopback
How to set a loopback
1. In the Tree Structure, select the board and expand it until the
available SFP/XFP modules is displayed ( )
2. Select the involved module and click on it. In the client area some
panels (according to the type of rate) appear
3. Scroll down the client area until the Loopback panel is shown
4. In the panel, by means the Loopback Type combo-box, it is possible to
choice (according the resource type):
FACILITY = loopback at the receive side (from the network) to the transmit
side (to the network) of the specified facility
TERMINAL = loopback where the signal that is about to be transmitted is
connected to the associated incoming receiver. The default value is
FACILITY
5. After the choice, click on Operate Loopback hyperlink that allows to
establish a near-end facility or terminal loopback on the specified
resource facility.


Issue 01
5 Loopback
How to disable a loopback
1. In the Tree Structure, select the board and expand it until the
available SFP/XFP modules is displayed ( )
2. Select the involved module and click on it. In the client area some
panels (according to the type of rate) appear
3. Scroll down the client area until the Loopback panel is shown
4. The panel refers about the actual loopback
5. Click on Release Loopback hyperlink that allows to release a near-end
facility or terminal loopback on the specified resource facility


Issue 01
5 Loopback
Facility Loopback
Facility loopbacks
The Facility loopback, specifies a loopback where the signal received at
the port (port ingress direction) is connected to the transmit side of the
port.
Facility loopbacks are supported for STM-1, STM-4, STM-16, STM-64
facilities.

The specified STM-n port must have a PST of OOS-AUMA or OOS-MA and not have an SST of LPBK (i.e. it is
not already in a loopback).

Issue 01
5 Loopback
Facility Loopback [cont.]
The operation to configure an a facility loopback are:

Select the port
Select STM tab
Set “Port Mode” = NMON or MON
Set “Primary state” = OOS
Scroll down the client area until the Loopback panel is shown
In the panel, by means the Loopback Type combo-box, choose FACILITY
click on Operate Loopback
1. Select the port
2. Select STM tab


Issue 01
5 Loopback
3. Set “Port Mode” = NMON or MON
4. Click on Save

Issue 01
5 Loopback
5. Set “Primary state” = OOS
6. Click on Save
7. Set “Loopback Type” = FACILITY
8. Click on Operate Loopback

The Loopback panel displays the following parameters:

Access Identifier: Identifies the entity access identifier in the <rack>-<shelf>-<slot>-<side> format.
Location: Allows to set the location in which the loopback is performed. The value is NEND Near End.
Loopback Type: Allows to set the type of loopback. The choices are:
FACILITY Loopback at the receive side (from the client equipment or a DWDM line) to the transmit
side (toward the client equipment or DWDM line) of the specified facility.
TERMINAL Loopback where the signal that is about to be transmitted toward the client is transmitted
back toward a DWDM domain. The default value is FACILITY.
Consequent Action: Specifies the consequent action. The values are Y or N.
When the loopback is done, the link changes in Release Loopback so to perform the reverse operation. The
Operate Loopback link allows the user to execute the loopback for the selected port.

Issue 01
5 Loopback
The loopback appear in the window
N.B. to delete the loopback, click on “Release loopback”


Issue 01
5 Loopback
Terminal Loopback
Terminal loopbacks
The Terminal loopback, specifies a loopback where the signal that is
about to be transmitted (port egress direction) is connected to the
receive side of the port.
Terminal loopbacks are supported for STM-1, STM-4, STM-16, STM-64
facilities.


Issue 01
5 Loopback
Terminal Loopback [cont.]
The operation to configure an a terminal loopback are:
Select the port
Select STM tab
Set “Port Mode” = NMON or MON
Set “Primary state” = OOS
Scroll down the client area until the Loopback panel is shown
In the panel, by means the Loopback Type combo-box, choose TERMINAL
click on Operate Loopback
1. Select the port
2. Select STM tab


Issue 01
5 Loopback
4. Click on Save

Issue 01
5 Loopback
6. Click on Save
7. Set “Loopback Type” = TERMINAL



Issue 01
5 Loopback
The loopback appear in the window
N.B. to delete the loopback, click on “Release loopback”


Issue 01
5 Loopback
DWDM Loopback
The system manages

Line (terminal) Loopback for the following DWDM cards:
OTU2 colored card (1POTU2 and 1POTU2XB)
DWDM10G Transponder (DWLA10X)
Client Loopback for the following DWDM cards
DWDM10G Transponder (DWLA10X).


Issue 01
5 Loopback
1POTU2/1POTU2XB: loopback configuration (line side)
1. Select 1POTU2 port
2. Scroll the window up to

the bottom, select the
payload carries panel
and click on Select Line
3. Select ODU2 LINE tab
4. Choose the Loopback type
The primary state of

the ODU2 must be
equal to IS


Issue 01
5 Loopback
1POTU2/1POTU2XB: loopback configuration (client side)
1. Select 1POTU2 port
2. Scroll the window up to

the bottom, select the
payload carries panel
and click on Select Client
3. Select STM tab
5. Scroll the Synchronous

Transport Signal Modify
tab up to the bottom and
Click on Save

Issue 01
5 Loopback
1POTU2/1POTU2XB: loopback configuration (client side) [cont.]
6. Click on Save
7. Set “Loopback Type” = TERMINAL



Issue 01
5 Loopback
DWLA10X: loopback configuration (line side)

3. Select ODU2 LINE tab bottom, select the DWDM
Line Selector panel and click
on Select Line
4. Choose the Loopback type
The primary state of

the ODU2 must be
equal to IS


Issue 01
Blank Page


Issue 01
6 Synchronization


Issue 01
6 Synchronization
Hierarchical structure
PRC: Primary Reference Clock
SSU: Synchronization Supply Unit
SEC: SDH Equipment Clock
PRC
PRC PRC
level
Max. 10
SSU
SSU SSU level
SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC
Max. 20 SEC
level
Max. 60
The Network Elements (NE) within SDH networks have to be synchronized to a central clock.
A hierarchical structure of clock generators with different qualities is used to distribute the clock
reference signal through the entire network:
PRC
The high precision Primary Reference Clock (PRC), according to ITU-T recommendation G.811,
builds up the highest level of the synchronization hierarchy and provides clock reference signals for
the NEs within the network.
It should be redundant in the synchronization network.
SSU
The second level is represented by the Synchronization Supply Unit (SSU), according to ITU-T
recommendation G.812. It filters the incoming clock reference signal and provides the network
with a high quality clock reference signal in case of a loss of the PRC reference.
The SSU can be a separate equipment or part of a SDH NE.
Max. 10 SSU are allowed in a chain.
SEC
The third and last level of synchronization is realized by the SDH Equipment Clock (SEC) according
to ITU-T recommendation G.813.
It is normally part of the NE and provides the NE with an holdover capability for at least 24 hours.
Max. 20 SEC are allowed one after the other and max 60 SEC in a chain between two SSU or after a
PRC.

Issue 01
6 Synchronization
Quality and Priority
Order Priority Quality
Level Code
(within S1
byte)
Highest 1 G.811 (PRC) 0010
2 G.812T (SSU transit) 0100
3 G.812L (SSU local) 1000
4 G.813 (SEC) 1011
Lowest 5 Do not use1) 1111
0 Quality unknown 0000

1)
This signal should not be used for synchronization. It is automatically
transmitted in the backward direction of the port, which is selected as clock
reference. This is done to prevent synchronization loops.

To select the clock reference signal with the highest quality available, the NE is using quality information
and/or a priority value.
Quality information is either delivered within the traffic signal used for synchronization transmitted
in the Synchronization Status Message (SSM) or provided manually by the operator; the binary code
representing the SSM is inserted in the S1 byte of the MSOH within the STM-N signal or the timeslot
zero of the 2Mbps PCM frame.
Priority values have to be provided manually by the operator: values from 1 to 5.
Frequency drift
G.811:
Cesium: 10-13 / day
GPS / Rubidium: 10-11 / day (1 slip in 145 days)
G812:
G.812T 10-9/ day
G.812L 2 x 10-8 / day
G.813 (Internal Oscillator) 10-8/ day (1 slip in 3,46 h)

Issue 01
6 Synchronization
SSM algorithm
SSM: Synchronization Status Message
YES NO
Is the SSM
managed ?
Does only
one source has the NO
highest quality
criterion? Selection of the clocks
with the highest Analysis of the
YES quality criterion priorities table
Selection of the source

with the best quality Selection of the clock
criterion with the highest priority
Locking phase to external

clock reference signal

The SSM (Synchronization Status Message) Algorithm is used by the NE to select the clock reference signal
with the highest quality available by using quality information and/or a priority value.
3 operation modes are available in the NE (see next page):

Locked mode:
SETG output is fully controlled by the external timing references (T1 and T3/T6)
Holdover mode:
The external timing reference is malfunctioning.
The SETG during normal operation (locked mode) stores regularly the value of the external timing
reference: in the case of Holdover mode the SETG output is controlled by this memorized value.
Free running mode:
This is not a normal operating mode.
The external timing reference and the memorized timing reference are malfunctioning.
In this case the SETG output is controlled by the internal clock source.

Issue 01
6 Synchronization
SETS function
SETS: Synchronous Equipment Timing Source
Selector Squelch Selector

A T4/T5
A C
External
Clock
Squelch
3 B
T1
2 Selector
SETG
T3/T6 B T0
Internal
Clock
osc SETS

The Synchronous Equipment Timing Source (SETS) function performs different tasks to ensure
synchronization.
SETG: Synchronous Equipment Timing Generator
generates the internal system clock T0
T0: internal clock reference signal (38,88 MHz on the backpanel)
has 3 operation modes: Locked / Holdover / Free running (explanation see previous page)
The SETS function receives clock reference signals which can be extracted from different types of
sources:
T1: clock reference input signal extracted from STM-N traffic signal
T3: 2 MHz clock reference input signal received from an external synch. equipment
T6: 2 Mbps clock reference input signal carrying no traffic but containing the SSM
OSC: An internal oscillator enables a holdover state if the external clock references fail
The SETS function provides external clock reference signals which can be used to synchronize other NEs:
T4: 2 MHz clock reference output signal
T5: 2 Mbps clock reference output signal carrying no traffic but containing the SSM
Selector A / B and C:
Selector A and B: The clock reference sources are selected automatically using quality information
received from the SSM and/or priority criteria. Also a manual selection (by the operator) is possible.
Selector C is used to set/release the external clock signals equal to the internal used clock reference
signal (T0) by operator command.
Squelch functions (A / B) are used to disable the transmission of the external clock signals in case of a
minor quality of the reference clock input signal than the quality defined by the operator.

Issue 01
6 Synchronization
Synchronization: CRG function
The system additionally utilizes Line timing from STM-N ports to

synchronize the system. In this case system is timed to either a
Primary or Secondary Line time reference. Line timing enters via the
STM-N boards the redundant Clock Reference Unit (CRU) on the matrix
boards. The Clock Reference Generator (CRG) function of the CRU
selects the appropriate source and distributes timing.
The Clock Reference Generator (CRG) function of the CRU selects the
appropriate source out of up to two references (2 x BITS or 2 x Line
timing or 1 x BITS and 1 x Line timing) and distributes timing.


Issue 01
6 Synchronization
Timing Loop
A reuse of signal for synchronization purpose must be deeply

investigated since timing loops might be generated through a lot of PDH
and SDH pieces of equipment. Next figure gives an example of timing
loop.
Risk of timing loop No risk of timing loop
SSU SSU SSU SSU

DNU
B B
SEC squelched
SEC SEC SEC SEC
direction of timing
This port must
not be a sync port


Issue 01
6 Synchronization
Synchronization: operational mode
Clock modes
The supported clock modes are as follows:
Locked mode (Normal mode): (steady state) The SETG generated clock
signal is controlled by the selected external timing reference determined by
the T0 selection process; the output clock is traceable to the selected input
frequency over long term and, and the phase difference between the input
and output is bounded. The "holdover memory" is acquired and periodically
updated (acquiring holdover memory is a temporary mode entered when
coming from free run state)
Holdover mode: (steady state) The holdover mode is the operating condition
of a clock that has lost its references and is using data previously acquired
(when it was operating in the normal mode) to control its output signal. In
general, the stored data or "holdover value" used by a clock in the holdover
mode is an average value obtained over some period of time (in order to
reduce the effects of any short-term variations that might occur in the
reference frequency during normal operations).


Issue 01
6 Synchronization
Synchronization: operational mode [cont.]
Free-running mode: (temporary operating mode) The free-running mode of

a clock is its operating condition when the output signal is totally internally
controlled, with no influence of a present or previous reference


Issue 01
6 Synchronization
Synchronization menu
This menu allows the operator to manage the ports dedicated to BITS
(Building Integrated Timing Supply) facilities for clock distribution
purposes. A BITS output reference is a 2 MHz signal. The menu options
are:
BITS: Allows to modify the characteristics (BITS-0 as Primary and BITS-1 as
Secondary) and the outgoing port of reference clock.
Synchronization: Allows to modify the parameters of the synchronization
system.
Synch. Outgoing. Allows to modify the parameters of the synchronization
outgoing.


Issue 01
6 Synchronization
Reference clock configuration (T1)
Extracted reference clock (T1) settings

1. In the menu bar open the Synchronization Synchronization
Search menu path.
2. In the Synchronization panel, select ALL as Access Identifier: and
click on Search hyperlink, selecting one out of the provisionable
LINEREFSYS-x-x-xx in the list and click on Modify hyperlink.
3. In the Modify Synchronization panel set the following items:
Assigned port Access Identifier: one out of the available STM-n ports and
that can be selected by means the Select procedure.
Provisioned Quality Level: It is the provisioned quality level of a timing
reference. Two different methods are supported; i.e. the quality level is
either derived from the incoming SSM value or a fixed quality value is set.
The value AUTO is only allowed for ports supporting SSM. Possible values:
AUTO (quality level value is derived from incoming SSM) or PRC (ETSI
quality level value is fixed to Primary Reference Clock, specified in ITU-T
Rec. G.811) or SSUL (ETSI quality level value is fixed to Synchronization
Supply Unit - Local node, specified in ITU-T Rec. G.812) or SSUT (ETSI


Issue 01
6 Synchronization
Reference clock configuration (T1) [cont.]
quality level value is fixed to Synchronization Supply Unit -Transfer node,

specified in ITU-T Rec. G.812) or SEC (ETSI quality level value is fixed to
SDH Equipment Clock, specified in G.813 option 1). Select one out of the
available items .
Timing Reference Priority: It is the priority of a timing reference for the
system timing selection process. It is possible to provision the same priority
to different timing references in order to support a non-revertive selection
process. When Sync Messaging is disabled, the selection process will be
controlled by signal status and priority. The priority "0" means that the
timing reference is disabled from the selection process. A greater
parameter value means a lower the priority for the selection besides the
value "0". Possible values: 0 (disabled for the system timing selection
process) and from 1 to 8 (enabled for the system timing selection process).
4. Click on Save hyperlink in order to confirm the settings and the client
area shows the updated list.


Issue 01
6 Synchronization
To configure the Internal Synch timing, select:

Synchronization Synchronization Search
1. Open the Search menu
2. Select ALL
3. Click on Search

The Synchronization tab displays the Synchronization panel that contains the following parameters:
Shelf Access Identifier: This is used to change the content of Access Identifier field according to the
selected shelf identifier
Access Identifier: Specifies the Equipment Access Identifier of clock reference unit
Clock Control Status: Indicates whether the related clock entity is the Active or Standby status. The
values are ACTIVE, STANDBY, or NA
Clock Mode: Specifies the clock tracking mode. The values are FREE-RUNNING, HOLDOVER, NORMAL,
NOTRRACKING, and NA
The Search link is used to locate the Selected Shelf and corresponding Access Identifier

Issue 01
6 Synchronization
5. Click on Modify
4. Select one LINEREFSYS-x-x-xx resource in

the list (the resource MUST BE IN SERVICE)

The Sychronization search results are displayed in a set of tables on a per shelf basis. The are two types of
tables:
System Timing Entity
Reference Timing Entity
The System Timing Entity table contains the following parameters:
Select: Contains a check box used to identify the Access Identifier used with Modify, Operate, and
Release
Access Identifier: Specifies timing entity facility
Clock Mode Status: Specifies the currently used operation mode for the system timing. The values are
LOCKED, AUTONOMOUS-HOLDOVER, AUTONOMOUS-FREERUNNING, FORCEDFREERUNNING
Sync Messaging: Determines if the timing reference selection for system timing is using sync messaging.
The values are Y and N
Alarm Profile: Specifies Alarm Severity Assignment Profile (ASAP) name to be used for the system timing
and timing reference entity
Active Reference: Specifies the AID of the currently selected timing reference for the system timing
Reference Switch State: Specifies the currently active switch request state of reference selection for
the system timing. The values are NR, MANUAL, and FORCED
System Timing Quality: Specifies the actual quality value level for the stem timing. The values in SDH
mode are PRC, SSUL, SSUT, SEC, and DUS
The Reference Timing Entities table contains the following parameters:
Select: contains a check box used to identify the Access Identifier used with Modify, Operate, and
Release

Issue 01
6 Synchronization
6. Click on Select to specify

the STM-n or GbE resource
7. The user must specify the complete

AID of the STM-n or GbE resource 8. Click on ADD to submit the choice
(STM1-1-1-23-2 in our example)

Assigned Port Access Identifier: Specifies the Access Identifier of the port
Provisioned Quality level: Specifies the provisioned quality level of a timing reference. The values are
in SDH mode AUTO, PRC, SSL, SSUT, and SEC
Timing Reference Priority: Specifies the priority of a timing reference as forwarded to the system
timing selection process. The values are 0 (disabled for the system timing selection process) and from 1
to 8 (enabled for the system timing selection process)
Outgoing Quality: Specifies the actual quality value level for the timing reference as forwarded to the
system timing selection process. The values are in SDH mode PRC, SSUL, SSUT, SEC, and DUS
Timing Reference Status: Specifies the actual signal status for the timing reference as forwarded to
the system timing and output timing selection process. The values are NORMAL, SF, WTR, and NA
Timing Reference Lockout: Specifies whether a lockout command for the system timing selection is
present for the timing reference. The values are Y and N
Alarm Profile: Specifies Alarm Severity Assignment Profile (ASAP) name to be used for the system
timing and timing reference entity
Primary State: Specifies the new value of primary state. The values are IS and OOS

Issue 01
6 Synchronization
10. Choose the Quality level and the Timing

Reference Priority (0 (highest) - 8 (lowest))
11. Click on Save
12. Click on Close
The Synch. resource appears in the window


Issue 01
6 Synchronization
Reference clock configuration (T3/T6)
External reference clock (T3/T6) settings

1. In the menu bar follow the Synchronization Bits Modify BITS-0 menu
path.
2. In the Select Shelf panel, click on Continue hyperlink.
3. In the Modify BITS panel, set the Signal Format: field as the signal
type for the timing output port (i.e. out-going direction) as referred in
the plat document. This parameter determines the capabilities of the
timing output port in terms of SSM insertion and squelching. Possible
values: 2MHZ (2 MHz signal without SSM support. ITU-T definiton T3)
or 2MBIT-NOSSM (2 Mbit/s framed signal with no SSM support. ITU-T
definiton T6) or 2MBIT-SSM (2 Mbit/s framed signal with SSM support.
ITU-T definiton T6).
4. Repeat the procedure for BITS-1.


Issue 01
6 Synchronization
Reference clock configuration (T3/T6) [cont.]
5. Set the external reference clock from one of the provisionable

incoming signals (i.e. on the PSF320 adapter), selecting one out of the
possible EXTREF-x-x-x in the list and click on Modify hyperlink.
6. In the Modify Synchronization panel set the items by means the
procedure previously mentioned.


Issue 01
6 Synchronization
From “BITS” option of the Synch menu item it is possible to configure,

BITS-0 (primary) and BITS-1 (secondary)
To modify the BITS-0 or BITS-1 parameters, select:
Synchronization BITS Modify BITS-0 or
Synchronization BITS Modify BITS-1


Issue 01
6 Synchronization
2. Configure the parameters
3. Click on Save to confirm the settings
To display the alarms relevant to the BITS
To display the conditions relevant to the BITS

The “Modify BITS-0” and “Modify BITS-1” are the same panel with the two different Access Identifier
values. The panel contains the following fields:
Access identifier: Specifies the access identifier for the selected BITS
Signal Format: Specifies the signal format. The values are 2MHZ, 2MBIT-NOSSM, or 2MBIT-SSM
SA Bit Location: Specifies the SA bit location used to carry the SSM information. The values are SA4,
SA5, SA6, SA7, and SA8. The default menu value is the previous existing value. If the existing value is
empty. The default existing value is SA4.
Alarm Profile: Specifies Alarm Severity Assignment Profile (ASAP) name to use with the facility. The
Select link opens a secondary window to select available Alarm Profiles.
Adapter: Specifies if the adaptor is active or not
Current Primary State: Specifies the retrieved value of primary state. The values are IS-NR, OOS-AU,
and OOS-MA.
Primary State: Specifies the new values of primary state. The values are IS and OOS. The default value
is the previous existing value. If the existing values is empty, the default factory value is IS.
Command Mode: Specifies the command execution mode. The values are NORM or FRCD. The default
menu value is FRCD for SDH mode.
The Save link is used to send the related command to the Network Element. Automatically is loaded the
“Modify BITS-0” or “Modify BITS-1” page to show update data.

Issue 01
6 Synchronization

5. Select ALL
6. Click on Search

The Synchronization tab displays the Synchronization panel that contains the following parameters:
Shelf Access Identifier: This is used to change the content of Access Identifier field according to the
selected shelf identifier
Access Identifier: Specifies the Equipment Access Identifier of clock reference unit
Clock Control Status: Indicates whether the related clock entity is the Active or Standby status. The
values are ACTIVE, STANDBY, or NA
Clock Mode: Specifies the clock tracking mode. The values are FREE-RUNNING, HOLDOVER, NORMAL,
NOTRRACKING, and NA
The Search link is used to locate the Selected Shelf and corresponding Access Identifier

Issue 01
6 Synchronization
8. Click on Modify
7. Select one EXTREF-x-x-x resource in the list

(the resource MUST BE IN SERVICE)

The Sychronization search results are displayed in a set of tables on a per shelf basis. The are two types of
tables:
System Timing Entity
Reference Timing Entity
The System Timing Entity table contains the following parameters:
Select: Contains a check box used to identify the Access Identifier used with Modify, Operate, and
Release
Clock Mode Status: Specifies the currently used operation mode for the system timing. The values are
LOCKED, AUTONOMOUS-HOLDOVER, AUTONOMOUS-FREERUNNING, FORCEDFREERUNNING
Sync Messaging: Determines if the timing reference selection for system timing is using sync messaging.
The values are Y and N
Active Reference: Specifies the AID of the currently selected timing reference for the system timing
Reference Switch State: Specifies the currently active switch request state of reference selection for
the system timing. The values are NR, MANUAL, and FORCED
System Timing Quality: Specifies the actual quality value level for the stem timing. The values in SDH
mode are PRC, SSUL, SSUT, SEC, and DUS
The Reference Timing Entities table contains the following parameters:
Select: contains a check box used to identify the Access Identifier used with Modify, Operate, and
Release

Issue 01
6 Synchronization

the BITS-x resource

the BITS-x resource (i.e: BITS-1-1-0) 11. Click on ADD to submit the choice


Assigned Port Access Identifier: Specifies the Access Identifier of the port
Provisioned Quality level: Specifies the provisioned quality level of a timing reference. The values are
in SDH mode AUTO, PRC, SSL, SSUT, and SEC
Timing Reference Priority: Specifies the priority of a timing reference as forwarded to the system
timing selection process. The values are 0-8
Outgoing Quality: Specifies the actual quality value level for the timing reference as forwarded to the
system timing selection process. The values are in SDH mode PRC, SSUL, SSUT, SEC, and DUS
Timing Reference Status: Specifies the actual signal status for the timing reference as forwarded to
the system timing and output timing selection process. The values are NORMAL, SF, WTR, and NA
Timing Reference Lockout: Specifies whether a lockout command for the system timing selection is
present for the timing reference. The values are Y and N
Primary State: Specifies the new value of primary state. The values are IS and OOS

Issue 01
6 Synchronization
13. Choose the Quality level and the

Timing Reference Priority
14. Click on Save
15. Click on Close


Issue 01
6 Synchronization
Output Synch configuration (T4/T5)
Outgoing reference clock (T4/T5) settings

1. In the menu bar follow the Synchronization Bits Modify BITS-
OUT menu path.
2. In the Select Shelf panel, click on Continue hyperlink.
3. In the Modify BITS-OUT panel set the following items:
Signal Format: signal type for the timing output port (i.e. out-going
direction). The parameter determines the capabilities of the timing output
port in terms of SSM insertion and squelching. Possible values: 2MHZ (2 MHz
signal without SSM support. ITU-T definiton T4) or 2MBIT-NOSSM (2 Mbit/s
framed signal with no SSM support. ITU-T definiton T5) or 2MBIT-SSM (2
Mbit/s framed signal with SSM support. ITU-T definiton T5).
Enable Output: specify the output mode to Y (output is enabled, i.e.
switched on). Other possible value N (output is disabled, i.e. switched off).


Issue 01
6 Synchronization
BITS Configuration (BITS-OUT)
To modify the BITS-OUT parameters, select:

Synchronization BITS Modify BITS-0UT


Issue 01
6 Synchronization
BITS Configuration (BITS-OUT)

The Modify BITS OUT panel contains the following fields:

Access Identifier: Specifies the Access Identifier of the selected BITS.
Signal Format: Specifies the signal time for the timing input port. The values are 2MHZ and 2MBIT-SSM.
If the user selects 2MBIT-SSM, the SA bit location is displayed. The default value is the previous existing
value. If the existing value is empty, the default factory value is 2MHZ for SDH mode.
SA Bit Location: Specifies the SA bit location used to carry the SSM information. The values are SA4,
SA5, SA6, SA7, and SA8. The default menu value is the previous existing value. If the existing value is
empty. The default existing value is SA4.
Transmitted ESF: Specifies if the output signal is the DUS message or is the actual SSM value. The
values are DUS and ACT. The default existing value is DUS
Enable Output: Specifies the output mode to which the facility is set. The values are Y and N. The
default value is N.
AIS Mode: Specifies which signal is inserted for the timing output port if the output signal is squelched.
The parameter is only applicable for port types supporting SSM. The values are AISMODE (AIS signal is
inserted) and QLMODE (DUS is inserted as SSM, output is squelched). The default values is the QLMODE.
Outgoing Signal Quality: Specifies the quality value level for the out-going signal at the timing output
port. The values are PRC, SSUL, SSUT, SEC, and DUS.
SSM Supported: Specifies whether the timing input port supports SSM or not. The values are Y and N.
Adapter 0: Adapter, specifying the type of the external adapter, which has been positioned on the
front panel of power supply board A (on slot 39) for connector of the BITSOUT physical interface: The
values are: NOADAPT: No adaptor, suitable for 2MHz/2MBit or 1.5Mbit signal , WIREWRAP Wire Wrap
adaptor, suitable for 1.5Mbit signal, UNKNOWN If adapter information can not be accessed
Adapter 1: Adapter, specifying the type of the external adapter, which has been positioned on the
front panel of power supply board B (on slot 37) for connector of the BITSOUT physical interface: The
values are: NOADAPT: No adaptor, suitable for 2MHz/2MBit or 1.5Mbit signal , WIREWRAP Wire Wrap
adaptor, suitable for 1.5Mbit signal, UNKNOWN If adapter information can not be accessed
The Default hyperlink allows to recover the previously existing value or the factory default (Actual).
The panel has the Save hyperlink that is used to send the related command to the Network Element.

Issue 01
6 Synchronization
Output Synch configuration (T4/T5) [cont.]

Synchronization Synch. Outgoing Search
5. Select ALL
6. Click on Search

The Synchronization Outgoing tab displays the Synchronization Outgoing panel that contains the following
parameters:
Shelf Access Identifier: This is used to change the content of Access Identifier parameter according to
the selected shelf
Access Identifier: Specifies the access identifier of the synchronization facility
The Search link retrieves the shelf information based on the selection

Issue 01
6 Synchronization
8. Click on Modify
7. Select one LINEREFOUT-1-1-x resource in

the list (the resource MUST BE IN SERVICE)


Issue 01
6 Synchronization

the STM-n resource

the STM-n resource (i.e: BITS-1-1-0) 11. Click on ADD to submit the choice


Issue 01
6 Synchronization
13. Choose the Quality level and the

Timing Reference Priority
14. Click on Save
15. Click on Close


Issue 01
6 Synchronization
SSM for T0 configuration
To configure the SSM for T0, select:

2. Select ALL
3. Click on Search

T0 Configuration
The SSM algorithm implements the choice among the sources of synchronization, according to the
best quality indicated in SSM byte.

The use of SSM algorithm allows also the automatic restoration of the synchronization in a network in
case of failure.
When SSM algorithm is enabled:
SSM is extracted by the incoming signal and used as criteria to select the clock reference.

NE inserts SSM=Don’t use in the opposite direction from where the clock is received (in case of SDH

reference clock).
Internal clock is assumed SSM=G.813; you have the same quality in the Holdover condition.

If one of the following: “ACT, PRC, SSUL, SSUT and SEC” is selected in “S1 byte to be

Transmitted” drop down window from the STM tab of the port view, the system internal T0 clock
quality is transmitted towards the external interface.
The SSM algorithm implements the choice among the synchronization’s sources, according to the best
quality indicated in SSM byte. The use of SSM algorithm allows also the automatic restoration of the
synchronization in a network in case of failure.

Issue 01
6 Synchronization
SSM for T0 configuration [cont.]
5. Click on Modify
4. Select SYNC-1-1-0 resource
6. Click on Y to enable
the SSM algorithm
7. Click on Save

The Transmitted SSM quality for a STM-N port can be set from the “S1 byte to be Transmitted” drop
down window from the STM tab of the port view.

Issue 01
6 Synchronization
T4 configuration
To configure the SSM for T0, select:

Synchronization Synch. Outgoing Search
2. Select ALL
3. Click on Search


Issue 01
6 Synchronization
T4 configuration [cont.]
5. Click on Modify
4. Select SYNC-1-1-0
6. Choose Y To enable SSM for T4/T5 (Sel. A)
7. Configure Output
Selection: OUTTIM
for Sel. A and SETG
for Sel. B
8. Choose the squelch A or B criteria See next slide

Different squelch criteria may be applied:

when T0 is selected to generate T4/T5 (ex T0=T4 command) (use the command “Output selection” =
“SETG”):
T0 may be squelched if all the allowable timing references of Selector B have Quality Level lower

than the programmable threshold.
when an input reference is selected to generate T4/T5 (use the command “Output selection” =
“OUTTIM”):
the output of selector A may be squelched if the Quality Level of selected source is lower than
the programmable threshold or if it becomes unavailable.

Issue 01
6 Synchronization
T4 configuration [cont.]
9. Click on Save

Regenerator Loops mode: Specifies whether output timing is used for timing regenerator loops (ADM
with SSU/SASE). The supported values are:
ENABLE: output timing is used for timing regenerator loop.
DISABLE output timing is not used for timing regenerator loop and is specific to ETSI.
The default value is DISABLE or the previously existing value.

Transparent clock: determines if transport of the Transparent Clock is disabled or not in the node. The
supported values are:
DISABLE. The Transparent clock function is disabled
1588V2: The Transparent clock function is enabled using IEEE 1588 v2 protocol.
The default value is DISABLE or the previously existing value.

Issue 01
6 Synchronization
Information from the window
2MHz or 2 Mbit/s port configured
as clock source: SF (LOS)
Quality
Squelching result: Y means the resource is been squelched
Priority

Issue 01
6 Synchronization
Remove Input/Output Timing Reference
2. Click on Modify 1. Select a synch. resource
3. click on NA
4. click on Save


Issue 01
6 Synchronization
Quality check
The Sync. Message options displays the actual quality value for the
incoming SSM derived from corresponding OH byte value of a timing
reference.
To check the quality, open: Synchronization Synchronization
Sync. message 2. Select ALL
1. Open the Sync.

Message menu 3. Click on Search

The Retrieve Synchronization Message table contains the following columns:

Access Identifier: Specifies the timing entity facility
Incoming SSM Message: Specifies the actual quality value for the incoming SSM derived from
corresponding OH byte value of a timing reference. The values in SDH mode are SSM0, PRC, SSM3,
SSUT, SSM5, SSM6, SSM7, ,SSUL, SSM9, SSM10, SEC, SSM12, SSM13, SSM14, DUS, UNAVAILABLE, NA,
NOT-SUPPORTED

Issue 01
6 Synchronization
Synchronization command (operate)
This function allows to assign the clock reference source that is to be

selected as the system clock synchronization source.
To open the menu, select: 2. Choose the switch
command (i.e. LOCKOUT)
Synchronization Synchronization Operate
Synchronization Synch. Outgoing Operate
1. Open the
Operate menu
3. Choose the reference
4. Click on Operate
It’s also possible to open the Operate / Release command

selecting the resource and clicking on the command

The Synchronization Switch tab displays the Modify Synchronization Switch tab that contains the following
parameters:
Switch Command: Specifies the switch command, that is requested by the user. The values are
LOCKOUT, FRCD and MAN
Shelf Access Identifier: This is used to change the content of Switch To Reference parameter according
to the selected shelf access identifier
Switch To Reference: Specifies the access identifier of the synchronization facility
Invoke Lockout: You cannot invoke lockout on the internal oscillator!

To disable the selected timing source from being considered as possible source of timing for T0 or
T4/T5.
Invoke Force:
To force a switch to the selected timing source.
This operation is independent on the priority or quality of the timing source.
A forced switch to a timing source which is in state “don’t use” or “faulty” leads to holdover mode.
Invoke Manual: You cannot invoke a manual switch on the internal oscillator!
The manual command invokes a manual switch to the selected timing source.
This operation is possible only if the priority or quality of the selected timing source are the same as
for the currently selected timing source.
If this is not the case then the automatic selection overrules the manual selection.

Issue 01
6 Synchronization
Synchronization command (release)
This function allows to release a lockout, manual or forced switch.

To open the menu, select:
Synchronization Synchronization Release
2. Choose the command
Synchronization Synch. Outgoing Release
1. Open the 3. Choose the reference

Release menu
4. Click on Operate

The Synchronization Switch tab displays the Modify Synchronization Switch panel that displays the following
parameters:
Switch Command: Specifies the switch command, that is requested by the user. The values are
CLOCKSWITCH, REFSWITCH
Shelf Access Identifier: This is used to change the content of Access Identifier parameter according to
the selected shelf access identifier
Access Identifier: Specifies the access identifier of the synchronization facility

Issue 01
6 Synchronization
Ethernet quality configuration
1. Select the local port of
PP1GESY or PP10GESY board
2. Select Synchronization tab
4. Click on Save 3. Select the quality


Issue 01
7 OTN management


Issue 01
7 OTN management
Introduction
The aim of the optical transport network (OTN) is to combine the

benefits of SDH technology with the bandwidth expandability of DWDM.
In short, OTNs will apply the operations, administration, maintenance
and provisioning (OAM&P) functionality of SDH, to DWDM optical
networks.
This newly developed OTN is specified in ITU-T G.709 Network Node
Interface for the Optical Transport Network (OTN).
Forward error correction (FEC) adds an additional feature to the OTN
by offering the potential for network operators to reduce the number
of regenerators used leading to reduced network costs.
OTNs present a number of advantages to network operators including:
Protocol transparency
Backward compatibility for existing protocols
Allowance of FEC coding
Reduction in 3Rregeneration (through flexible optical network designs)
The last point is of particular significance as it minimizes network
complexity which leads to reduced costs.


Issue 01
7 OTN management
Several overhead sections are added to the client signal which together
with the FEC form the optical transport unit (OTU). This is then carried
by a single wavelength as an optical channel (OCh). As multiple
wavelengths are transported over the OTN, an overhead must be added
to each to enable the management functionality of the OTN. The
optical multiplexing sections and optical transmission sections are
constructed using the additional OH together with the OCh.


Issue 01
7 OTN management
Client
Digital domain
OH Client OCh Payload Unit (OPUk)

Associated
overhead
OH OPUk OCh Data Unit (ODUk)
OH ODUk FEC OCh Transport Unit (OTUk)

Non-associated overhead
OTUk Optical Channel (OCh)
OH
OCC OCC OCC Optical Channel Carrier (OCC)
Optical domain
OH OMSn OPS0 Optical Multiplex Section

OPSn
OH OTSn Optical Transmission Section
OOS OTM Overhead Signal

OSC
OSC Optical Supervisory Channel
Optical Transport Module
Optical Physical Section

Transport of a client signal in the OTN follows this procedure:

OH is added to the client signal to form the optical channel payload unit (OPU)
OH is then added to the OPU thus forming the optical channel data unit (ODU)
Additional OH plus FEC are added to form the optical channel transport unit (OTU)
Adding further OH creates an OCh which is carried by one color
Additional OH may be added to the OCh to enable the management of multiple colors in the OTN.
The OMS and the OTS are then constructed. The result is an optical channel (OCh) comprising an OH
section, a client signal and a FEC segment

Issue 01
7 OTN management
OTU-frame
3824
3825
4080
15
14
16
17
1
7
8
OTUk
1 Alignm
OH
OPUk OH
2 Client Signal
OTUk
mapped
OPU in
k Payload
3 ODUk FEC
OPUk Payload
OH
4
Client Signal
k indicates the order:
OPUk - Optical Channel Payload Unit 1 2.5G
2 10G
ODUk - Optical Channel Data Unit 3 40G
OTUk - Optical Channel Transport Unit

Frame format identical for all bit rates
Alignment The frame time depends on the bit rate tframe = 122368/bit rate
The frame alignment OH is part of the OTU OH. It is situated in row 1, columns 1 to 6 of the OTU in
which a frame alignment signal (FAS) is defined. As the OTU and ODU frames could span multiple OTU
frames, a multiframed, structured overhead signal is defined.
The multiframe alignment signal (MFAS) is defined in row 1, column 7 of the OTU/ODU overhead.
The value of the MFAS byte is incremented with each OTU/ODU frame.
SM (Section Monitoring) bytes: for details see next page
General communication channel 0 (GCC0) is used as a communication channel between OTU termination
points.
RES bits: These bytes are reserved for future international standardization. All bytes are set to zero and
not in use.

Issue 01
7 OTN management
OTU-frame (Section Monitoring bytes)

The section monitoring OH consists of the following fields:

Trail trace identifier (TTI): the TTI is similar to the J0 byte in SDH. It is used to identify the signal
from the source to the destination within the network. The TTI contains the so called access point
identifiers (API) which are used to specify the source access point identifier (SAPI) and destination
access point identifier (DAPI).
Bit interleaved parity (BIP-8): this is one byte which is used for error detection. The BIP-8 byte
provides a bit interleaved parity 8 code. The BIP-8 is computed over the whole OPU and inserted into
the BIP-8 SM two frames later.
Backward defect indication (BDI): this single bit conveys information regarding signal failure in the
upstream direction.
Backward error indication (BEI) and backward incoming alignment error (BIAE): these signals carry
information on interleaved-bit blocks detected in error in the upstream direction. The IAE (incoming
alignment error) bit allows the ingress point to inform the egress point that an alignment error in the
incoming signal has been detected. IAE is set to “1” when an error occurs, otherwise it is set to “0”.
RES bits: These bytes are reserved for future international standardization. All bytes are set to zero
and not in use.

Issue 01
7 OTN management
OTN layer structure
T M A A M T
T= Transponder
M= MUX/DEMUX
A= Amplifier

Issue 01
7 OTN management
Introduction: FEC
In conjunction with the OCh OH, additional bytes are added. This bytes
are used for FEC. The FEC algorithm enables the correction and
detection of errors in an optical link.
There are several algorithms which can be used to perform the error
correction. The TSS-320/160 supports only two different FEC:
RSFEC: Red-Solomon FEC
EFEC2: Enhanced FEC2 (not allowed on DWLA10X client side)
The RS-FEC implementation defined in the G.709 recommendation uses
the Reed-Solomon code RS(255/239).


Issue 01
7 OTN management
Introduction: FEC [cont.]
Here, an OTU row is split into 16 sub-rows each consisting of 255

bytes. The sub-rows are formed byte interleaved, meaning that the
first sub-row consists of both the first OH byte and the first payload
byte. The first FEC byte is inserted into byte 240 of the first sub-
row. This is valid for all 16 sub-rows

Of these 255 bytes, 239 are used to calculate the FEC parity check, the result of which is transmitted in
bytes 240 to 255 of the same sub-row. The Reed-Solomon code detects 16 bit errors or corrects 8 bit
errors in a sub-row

Issue 01
7 OTN management
Transponder Functional block Diagram
Coloured
STM 64 B&W FEC To/From the
Module
signal WDM line

FEC (Forward Error Correction) is implemented in the Transponders.

A special type of FEC called “Enhanced FEC” (EFEC) is implemented in the “Enhanced” Transponders.
EFEC characteristic, BER vs. Q factor is shown in the above diagram together with other FEC solutions.
Transmit side : FEC encoder performs the following operations:
framing of the input STM-64/OC192 into a FEC frame, compliant with G.709 OTH frame;
insertion of the inter-terminal auxiliary channels into OTH frame,
computation of redundant FEC symbols for error detection and correction at receiver side,
Insertion of the Trail Trace Identifier (TTI) inside OTH frame, into ODU2-OH,
insertion of AIS under fault conditions, into ODU2-OH
The SDH frame is not modified by the FEC encoding to obtain the FEC frame.
Receive side : FEC decoder performs the following operations:
OTH frame alignment to the received signal
line error correction and monitoring of the number of corrected errors for BER calculations,
re-framing of the traffic data into an STM-64/OC192 data output,
detection and insertion of AIS under fault conditions,
auxiliary channels extraction from the frame overhead,
Trail Trace Identifier (TTI) recognition in the frame overhead (to detect mis-routed signals in the
system).

Issue 01
7 OTN management
100
10-2
10-4 BER without correction

Bit-error rate
(BERIN)
10-6
10-8
Standard FEC
RS(255,239)
10-10 Alcatel
Enhanced SFEC NCG=5.8dB
10-12
10-14 NCG=8.6dB
With erasures
10-16
7 8 9 10 11 12 13 14 15 16 17 18
Q2 factor (dB)
The above diagram compares the Enhanced FEC with standard FEC described in G.709 (OTN standard).
The above characteristic allows to guarantee a minimum OSNR=16.2dB/0.1nm at Transponder input, WDM
side.
The basic algorithm adopted in the Enhanced FEC is the classical BCH coding.
A BCH(1020,988)*BCH(1020,988) Pseudo-Product Code FEC algorithm is implemented in the 1626LM .
An additional algorithm is added, called “Erasure Algorithm”, to improve the FEC performance. Erasure
algorithm allows a correct FEC operation, with full error correction, up to an input error rate 4x10E-3.
The total redundancy introduced is 7% (line data rate is 10.709 Gb/s) and the net coding gain achieved
according to simulations is ~8.5 dB at a BER of 10E-13.
A net coding gain of 8.45 dB has been measured at BER=10E-13.
The diagram above shows a comparison of the error correction performance of the EFEC and previous
generations of FEC. The measured EFEC performance lies on top of the simulation result.
Important Note: EFEC is based on the standard OTH frame; but some implementation details are
proprietary. EFEC must be disabled in case of interworking with other manufacturers.

Issue 01
7 OTN management
DWLA10 board: line side
1. Select the DWLA10x board
2. Select the line side XFP
DDM info panel

Line Selector panel and
click on Select Line


Issue 01
7 OTN management
DWLA10 board: line side (ODU2 line)-TTI and FEC configuration

Select the ODU2 LINE tab
To enable/disable the path

trace monitoring
Click on Save to confirm

FEC configuration
the settings
Click on Retrieve Trail Trace

to retrieve TTI informations
(see note page)
Configure the TTI parameters


Issue 01
7 OTN management
DWLA10 board: line side (OCH Line)-ALS management
1. Select OCH LINE tab
AINS configuration
2. Choose the ALS

configuration
3. Click on Save to
confirm the settings


Issue 01
7 OTN management
DWLA10 board: line side (Client)
Select CLIENT tab
This window depends on the

client type chosen in the XFP
client (OUT-2, 10GE or STM-64)


Issue 01
7 OTN management
DWLA10 board: client side
2. Select the client side XFP
DDM info panel

select the DWDM Rate Selector panel
and click on Modify


Issue 01
7 OTN management
DWLA10 board: client side [cont.]
This window depends on the

client type chosen in the XFP
client (OUT-2, 10GE or STM-64)


Issue 01
7 OTN management
1POTU2 board: client side
1. Select the 1POTU2 board
2. Click on Select Client


Issue 01
7 OTN management
1POTU2 board: client side


Issue 01
7 OTN management
1POTU2 board: line side
2. Click on Select Line


Issue 01
7 OTN management
1POTU2 board: line side (ODU2 line)-TTI and FEC configuration
To enable/disable the path

trace monitoring
FEC configuration
Click on Save to confirm
the settings
Click on Retrieve Trail Trace

to retrieve TTI informations
(see note page)
Configure the TTI parameters


Issue 01
7 OTN management
1POTU2 board: line side (OCH Line)-ALS management
1. Select OCH LINE tab
AINS and Channel

configuration
2. Choose the ALS
configuration
3. Click on Save to


Issue 01
7 OTN management
LOFA1111: OTS view
1. Select the LOFA1111 board

select the DWDM selection panel
and click on Continue


Issue 01
7 OTN management
LOFA1111: OTS view [cont.]
OCONN tab is used to

create optical connection
1. Select OTS tab


Issue 01
7 OTN management
OMDX8100 board: OTN management
1. Select the OMDX8100 board

select the DWDM selection panel
and click on Continue


Issue 01
7 OTN management
OMDX8100 board : OTS view
1. Select OTS tab
OCONN tab is used to

create optical connection


Issue 01
7 OTN management
OMDX8100 board : OMS view
1. Select OMS tab


Issue 01
7 OTN management
OMDX8100 board : OMSOCH view
1. Select OMSOCH tab
2. Choose the channel


Issue 01
7 OTN management
OMDX8100 board : OMSOCHIF view
1. Select OMSOCHIF tab
2. Choose the channel


Issue 01
7 OTN management
OMDX8100 board : OMSBAND view
1. Select OMSBAND tab


Issue 01
Blank Page


Issue 01
End of Module
Operator Interface-SDH WDM features


Issue 01
33
Section 3
NE Operation
Module 3
Operator Interface-Ethernet Bridge features
Issue 01
1850 TSS-320 & 1850 TSS-160

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

Issue 01
Blank Page

NE Operation Operator Interface-Ethernet Bridge features
Document History

Issue 01
Module Objectives
• Create point-to-point Ethernet services

• Create Flow based CXC
• Create virtual and provider bridge services
• Implement the Link Aggregation on the Ethernet Port
• Configure and understand x-STP protocol
• Manage OAM functionality
• Implement the In Band management for remote NE supervision
• Configure LPT functionality
• Configure AIS Ethernet functionality
• Configure Delay Measurement and Synthetic Loss Measurement


Issue 01


Issue 01
Table of Contents
Page
1Introduction 7
2Ethernet overview 19
3Point–to-point cross-connection 23
4Flow Based Switching cross-connection 57
5Link Aggregation 89
6Virtual bridge - VLAN registration - RSTP - Filtering DB 105
7Provider bridge 143
8MSTP 191
9OAM 215
9.1 Introduction 216
9.2 EFM (Ethernet in the First Mile) 237
9.3 Standard OAM Management 243
9.4 DM configuration 267
9.5 Synthetic Loss Measurement tool 287
10 In Fiber In Band 303
11 Group Segregation Mng 309
12 Link Pass Through (LPT) 315
13 ETH AIS management 327
14 Ethernet loopback 335
15 Sync. and Transparent Clock Delay 339
16 CSF Configuration
NE Operation Operator Interface-Ethernet Bridge features 345
17 MAC File Collection 353
18 MAC Access Control List 359

Issue 01


Issue 01
1 Introduction

NE Operation Operator Interface-Ethernet Bridge features Section 3 Module 3 Page 7

Issue 01
1 Introduction
Ethernet frame
After a frame has been sent transmitters are required to transmit 12

octets of idle characters before transmitting the next frame. For 10M
this takes 9600 ns, 100M 960 ns, 1000M 96 ns.
Some implementations use larger jumbo frames (jumbo frames are
Ethernet frames with more than 1,500 bytes of payload (MTU).
Conventionally, jumbo frames can carry up to 9,000 bytes of payload,
but variations exist and some care must be taken when using the term).

NE Operation Operator Interface-Ethernet Bridge features Section 3 - Module 3 - Page 8

Issue 01
1 Introduction
Single tag frame and Double tag frame
S-VLAN tagged frame format

The Provider Bridging functionality relies on the definition and the handling of a further VLAN tag to be
added to the customer Ethernet frames ‘ingressing’ the Provider Bridge network.
This new tag is referred to as a ‘Service VLAN’ or ‘S-VLAN’, in order to distinguish it with respect to the
‘Q-VLAN tag’ (in this document referred to as ‘Customer VLAN’ or ‘C-VLAN’), already defined in the
previous 802.1Q std.
Two types of tags are, then, specified by the P802.1ad:
1) Customer VLAN TAG (C-TAG), for general use by VLAN Bridges and a C-VLAN component of Provider
Edge Bridges;
2) Service VLAN TAG (S-TAG), reserved for use by Provider Bridges and the S-VLAN component of
Provider Edge Bridges.
Both tags are based on the same format and are identified by different TPID. Tag Control Information (TCI)
is specific for C-tag and S-tag.
PRI and PCP bits define VLAN priority for C-tagged and S-tagged frames.
In the S-tag, the DEI bit is used for drop precedence, while the CFI bit is related to specific media access
type in C-tag field.
Thus, Ethernet frame transmitted by a Provider Bridge on an S-VLAN results in either “single tag” or
“double tag” format, depending on the presence of the inner C-VLAN

Issue 01
1 Introduction
Single tag frame and Double tag frame [cont.]
VLAN tag format
TPID format


Issue 01
1 Introduction
Single tag frame and Double tag frame [cont.]
C-tag TCI field
S-tag TCI field


Issue 01
1 Introduction
TSS-320 features
The tss_320 can be configured as:
802.1Q (virtual bridge)
802.1 AD (provider bridge)
802.1Q features supported:
P2P xc: connection oriented, no policing, don’t care classifier
ETS xc: connection oriented, policing, classification
Vlan switch: Connection less, MAC+Cvlan learning, CoS
802.1AD features supported:
802.1Q features
ADD xc: connection less, policing, classification, Svlan push
DROP xc: connection less, classification, Svlan pop
Service Delimiting
Protocols:
RSTP/MSTP/LAG/LCAS/GFP
Port Client layers:
ETS (Ethernet switch), ETB (Ethernet bridge), Link aggr.


Issue 01
1 Introduction
Auto Negotiation
The objective of 'auto-negotiation' function is to provide the means to
exchange information between two devices that share a link segment
and to automatically configure both devices in order to take maximum
advantage of their abilities.
Following parameters are exchanged :
Full duplex/half duplex
Asymmetric/Symmetric flow control (for cases existing: none, asymmetric,
symmetric and both)
Port speed rate


Issue 01
1 Introduction
Flow Control
Flow control is applied in two ways:
Asymmetric: in case of “overwhelming” incoming Ethernet traffic leading to
exhaustion of buffers on input queues, it is requested the capability to
transmit PAUSE frames in order to slow down remote peer MAC sub-layer.
Drop silently the pause frames received.
Symmetric: manages the pause frames, and so inhibit transmission of
Ethernet data frames for the specified period of time extracted from
received PAUSE frames.
Note:
Flow control is applicable on P2P/ETS service only


Issue 01
1 Introduction
LCAS and VCAT
LCAS (Link Capacity Adjustment Scheme)
The 1850TSS-320 DATA-system supports (at the SDH side) Virtual
Concatenation and LCAS features.
The Virtual Concatenation consists in the fact that frames not fitting
into a single SDH-container are transported over more individual
containers, indicated with the symbol VCn-Xv (e.g. VC4-3v indicates the
virtual concatenation of 3 VC4), also called VCG (Virtual Concatenated
Group).
The individual containers can follow different paths in the network,
with different delays, and they need to be reassembled at the end
points, taking into account the different path delays. This feature is
compliant to ITU-T G.707 rec


Issue 01
1 Introduction
LCAS and VCAT [cont.]
Limit of VCG configuration:
VC-4: up to 64 instances of VCG per 10G multiservice packet module,
with a minimum membership of 1 and a max. membership of 64
VC-3: up to 24 instances VC3 VCG per 10G multiservice packet module,
with a minimum membership of 1 and a max. membership of 24
VC-12: up to 106 instances of SDH VC12 VCG per 10G multiservice
packet module, with a minimum membership of 1 and a max.
membership of 63


Issue 01
1 Introduction
The LCAS feature (Link Capacity Adjustment Scheme) permits the
operator to “hitless" modify the bandwidth capacity of a virtual
concatenated link (VCG), in order to meet the bandwidth needs of the
service (by adding or removing virtual containers in all the involved
nodes of the network). It can also temporarily remove failed links of
the group, in automatic and hitless mode. In case of failure or addition
of links, the traffic is automatically redistributed over the working
links. Reference: ITU-T G.7042 rec.
Remark:
Hitless bandwidth increase of the virtual path
Hitless bandwidth decrease of the virtual path (starting from the “last”
virtual path*)
LCAS monitoring is available by ZIC


Issue 01
1 Introduction
Example of Vconc and LCAS

generator 1-RX 1gbe traffic on both side
Bandwidth reduced
1Ge 2-Fiber cut
3-Bandwitdh reduced on both side
Remore port
Remore port
TSS_9 Sl6-1
Sl5-1
4vc4 3vc4
STM-16
RING
Fiber Cut
Remore port
Remore port
Remore port
Remore port
TSS_10 TSS_11
Sl14-1 Sl13-1 Sl14-1 Sl13-1
1Ge
Bandwidth reduced
generator

Issue 01
2 Ethernet overview


Issue 01
2 Ethernet overview
Ethernet connections
GBE PP1GE SDH Port
MATRIX SFP
Eth
over
GBE STM-x SDH
Eth –to- “Eth over SDH” connection
VC4-1
PP10AD VC4-2
VCG-1
Remote
Port-1
Eth-to-Eth connection
VC4-1
VC4-2 SDH Port
Local Ports
Eth
SFP over
Remote
Port-2
PP1GE VCG-2 STM-x SDH
VC4-1 VC4-1
“Eth over SDH”–to–
PP10AD “Eth over SDH”
connection SDH Port
Remote
Port-1
VCG-1 Eth
GBE VC4-1
SFP
over
STM-x SDH
VC4-5
PP10AD: 64xVC4 max; 124xVCG max
Optical fibers TDM cross-connection Data cross-connection


Issue 01
2 Ethernet overview
Ethernet port’s service
Before using a port, its service type must be specified
Port-To-Port service:
•The port can accommodate one
bidirectional “Port based” connection ETS ETS
ETS ETS
with another port
Bridge = MAC, Virtual, Provider

Other service: ETB ETB
ETS ETS
Bridge = None
Frames Switching
•The port can accommodate a
number of unidirectional “Flow
based” connections with a number
ETS (one or more) of ports
ETS (Provider bridge)

•The port is ETB
ETS ETS
•The port is ETS for Provider bridge
switching


Issue 01
2 Ethernet overview
Locate the Local and the Remote ports in the tree
PP1GE supports 10
Local Ports
PP10AD supports the

Remote Ports. The
Remote Ports are not
in the tree.
10 x 1 GBE
Local Ports
10 GBE Local
Port


Issue 01
3 Point–to-point cross-connection


Issue 01
Point-to-Point cross-connection’s properties
It provides a transparent transport of the Ethernet signal.

The allowed bandwidth is the physical port’s bandwidth:
a Best Effort traffic descriptor is automatically given to the connection, but it
isn’t implemented because the policing is disabled.
The frames may be tagged or untagged:
a filter on the incoming frames (Classifier) is automatically given to the
connection, but it isn’t implemented.
It’s bidirectional.
Each port can support only one connection.
either local or remote ETS ports support Port-to-Port connection (local-
local, remote-remote, local-remote).


Issue 01
Point-to-point Ethernet over TDM service
Eth. in
VC4
port A
port B
Eth Eth
SDH
SDH
NE-A NE-B
SDH XC
SDH XC
ETS XC
ETS XC
CLASSI CLASSI
FIER FIER
Eth Eth
port A
port B
AU4
AU4
SDH
IN OUT IN OUT
SDH
FLOW FLOW FLOW FLOW
Traff. Traff.
Descr. Descr.
LOCAL Eth. REMOTE REMOTE LOCAL Eth.

Port A Eth. Port A Eth. Port B Port B
(VC4) (VC4)
Port-To-Port connection is bidirectional. The figure shows just one way.


Issue 01
Procedure for one node
Step Action
1 Create, activate and configure the remote port (VCG port)
create the TDM cross-connection between the remote port and the TDM
2
port
3 configure the local port
create the Point-To-Point connection between the local port and the
4
remote port


Issue 01
Step 1: Create the VCG
1. Select the PP10MS board
2. Scroll downwards the window
3. Each PP10MS can support

up to 124 VCGs. Set the
range to retrieve.
4. Click on Search/Refresh


Issue 01
Step 1: Create the VCG [cont.]
VCG#1 (remote port #1) Modify: already

enabled VCG
provision: not
5. To enable a VCG, click “provision” and see next slide
enabled VCG


Issue 01
6. Set the max number of

members that constitute the VCG
7. Choose the VCG type: VC4, LOVC3 or LOVC12
8. Optional. If not set, the “LBL ASAPVCG-SYSDFLT”

9. Click on Save ASAP will be assigned.


Issue 01
These are equal to 0. To

activate the VC4s see the
following steps.
Enable (Y) or disable (N) the LCAS

control for the VCG; if enabled,
configure the related parameters

The current Primary State of the VCG at this point is IS-NR.

In case of LCAS enabled, you have the following parameters:
- Hold Off Time. It specifies the time, in number of 100milliseconds, to wait before considering a
member of the addressed virtual concatenation group in failure condition after a defect has occurred
on that member. Valid only if LCAS is Enabled. A HOLD OFF TIME = 0 means there is no hold off time.
- Re-sequence Acknowledge timeout. This indicates the time, in milliseconds, the LCAS protocol waits
for the re-sequence acknowledge message. Valid only if the LCAS is Enabled.
- Signal Degrade Mode. Indicates if the signal degrade on the constituent member of the VCG
contributes to its fail condition. Valid only when LCAS is Enabled. The values are:
N: No. The signal degrade on the member does not fail that member
Y: Yes. The signal degrade on the member fails that member
If you enable the LCAS Control, at the bottom of the window, appear the following parameters:
- VCG Access Identifier, specifies the selected VCG entity to which the command is directed.
- Working Transmitting Channel Numbers. Indicates the the total number of channels within the
addressed VCG that are transmitting payloads (traffic).
- Working Receiving Channel Numbers. Indicates the the total number of channels within the addressed
VCG that are receiving payloads (traffic).
- MST Reference Channel. The VC channel used for retrieving the MST (Member Status Information).
(VCGVC4-{1-7}-{1-9}-{2-9,12-19}-{1-64}-{1-64} (VC4 within a logical VCG on a Multiservice Packet Card)
Channel used for Differential Delay. VC channel that has the most differential delay. (VCGVC4-{1-7}-{1-
9}-{2-9,12-19}-{1-64}-{1-64} (VC4 within a logical VCG on a Multiservice Packet Card)
- Re-Sequence Acknowledge Bit Transmitted.
- Re-Sequence Acknowledge Bit Received.

Issue 01
LCAS Monitoring

Channel Number. The channel number of the channel whose information is being displayed.
Control Packet Transmitted. Displays the value of the Control Field that is being transmitted. Values
are:
ADD The Channel is about to be added to the VCG.
DNU Do Not Use (the payload). The Sink Node side reported FAIL status for this channel.
EOS End of Sequence indication and Normal transmission. Indicates that this channel is the highest
non-failed active member of the VCG.
FIXED Fixed. This is an indication that this end uses fixed bandwidth (non-LCAS mode).
IDLE This member is not part of the group or os about to be removed
NORMAL Normal transmission
UNKNOWN The channel is experiencing a failure and hence cannot read the control packet.
Control Packet Received. Displays the value of the Control Field that is being received. The values are
the same of the Control packet Transmittes
Sequence Number Transmitted
Sequence Number Received. If there is a failure on the channel, the Sequence number returns
UNKNOWN.
Channel State transmitted. This state is coded in MST field in H4/Z7 byte of path overhead. The values
are:
FAIL: The channel has detected a failure in the receive direction and hence is transmitting FAIL.
OK: The channel has no failure in the receive direction.
Channel State received. This state is coded in MST field in H4/Z7 byte of path overhead. The values are
the same of the Channel state transmitted
Differential delay, calculated with respect to the Virtual Concatenation group Master channel given in
Channel used for Differential Delay parameter, in milliseconds.

Issue 01
Step 1: activate the paths
2. Set ACTIVE
1. Choose how many are to be activated
3. Click on Save
After activation, the indication

in the VCG window is updated
The current Primary State of the VCG at this point is OOS.AU

The current secondary state of the VCG at this point is FAF

Issue 01
Step 1: VCG interface configuration (State)
1. Select PHYSICAL
2. Set up
When the port is “down”, the

3. Click on Save option to change the alarm
profile is available


Issue 01
Step 1: VCG interface configuration (Ethernet port)
These options are available before setting the port up
Speed depends on the active VCs :

i.e. 2xVC4 = 299520 Kb/s
From 1574 to 9242
Choose ets
Click on Save to submit modifications

Alias: indicates the friendly name for the interface that can be set by the user
Maximum Receive Unit (MRU): size of the largest packet which can be received on this interface,
specified in octets.
Promiscous mode = true means that this interface does not have to inspect the packets' MAC address.
Link up/down trap: it indicates whether linkUp/linkDown traps (notification upon the changing of the
node operational state from up to down and vice versa) should be generated for this interface.

Issue 01
Step 1: VCG interface configuration (Ethernet port service)
1. Select PHYSICAL
2. Set port To port
3. Click on Save


Issue 01
Step 1: VCG interface configuration (GFP & Shaping)
These options are available before setting the port up
Specify the GFP parameters (see Notes)
80 Mb/s 10 Mb/s
Data VCG TDM TDM VCG Data

port port port port
Click on Save to submit 2xVC4: 299.520 Mb/s

modifications If Rate Limited Speed=10000
Define the shaping rate at the egress port.

It represents the old rate limiting
function presents in the ISA card and in
the old release of the TSS-320
GFP format:
nullExtHeader (GFP ONLY Null Extension Header((without FCS)): for scenarios where the transport
path (consisting of a single VCG) is dedicated to one GFP client signal.
PropietaryGFP: for scenarios where the transport path (consisting of a single VCG) is dedicated to
different GFP client signals.
Equipment-non-specific SL (Signal Label):
automatic: the transmitted signal label is automatically calculated.
forced: the transmitted signal label is always set equal to the “equipped-non-specific” code.
FCS (Frame Check Sequence) is an optional field of the GFP frame.
Transmit capability:
CSF consequent actions for failure propagations: in front of defect conditions detected over local
interfaces OR network traffic blocked over a local Ethernet Interface (Port-setting Administration
feature)
SSF consequent actions for failure propagations: in front of defect conditions detected over SDH-
based interfaces OR network traffic blocked over a SDH-based Interface (Port-setting Administration
feature);
the processing of received GFP CSF Client Management frames with detection of dCSF defect
(constrained to verification of the same UPI (User Payload Identifier) value supported on
transmission side) and raising of cCSF alarm

Issue 01
Delete a VCG: check the Provisioned Members
Deletion of VCG is possible if

Active Members is equal to 0.
2. Click on view
1. Look for VCG


Issue 01
Delete a VCG: deactivate all the VC4s
1. Select VCG
2. Set Activation State

to “IDLE”
3. Set Number of Paths to ALL



Issue 01
Delete a VCG: set down the interface
1. Select PHYSICAL
2. Set to down
3. Click on Save


Issue 01
Delete a VCG: Delete
1. Select VCG tab
2. Click on Delete

Issue 01
Step 2: Create the TDM XC
This option allows to create the cross-connection between the VC4s belonging to
the logical VCGroup and the TDM containers
Open the VCGroup window:
1. Select PTF
2. Select the specific VC4 to be cross-connected


The operator must configure the option for all members belonging to the logical VCGroup

Issue 01
Step 2: Create the TDM XC [cont.]
It is suggested to modify the Threshold

parameter (to “000.00”) in order to set
immediately In Service the facility
4. Select PTF Connection


Issue 01


7. The user must specify the complete AID
of the end point (i.e: STM16AU4-1-1-9-2-
1) or click on Start Tree Selection


Issue 01
10. Click on Create


Issue 01
Step 3: Local port configuration (State)
2. Select PHYSICAL tab
3. Admin state must be set to

“up” to enable the port
1. Select Local port
Operational state is “up” when

(i.e.) there’s no Loss Of Signal
alarm on the port
4. Click on Save
When the port is “down”, it is

possible to modify the alarm profile
Alarm Profiles:
No alarm
Primary alarms
Path alarms
All alarms

Issue 01
Step 3: Local port configuration (Ethernet port)
1. From 1574 to 9242
2. Select the Client type = ets
Asymmetric Default PAUSE: the Pause frames are

generated and transmitted by the Data port when the
received bit rate is higher than the the throughput of
the cross-connected VCG.
4. Click on Save
320 Mb/s Eth Data TDM
VCG port
Pause frames port
3. Configure the Pause behavior: this
applies in case of AutoNegotiation 1000 Mb/s 2xVC4: 299.520 Mb/s
enabled / disabled)

Speed [b/s]: indicates the actual configured rate

Alias: indicates the friendly name for the interface that can be set by the user
Maximum Receive Unit (MRU): size of the largest packet which can be received on this interface,
specified in octets.
Promiscous mode = true means that this interface does not have to inspect the packets' MAC address.
FCS discard errored frame: it indicates the insertion or removal of GFP-FCS (Frame Check Sequence) field
into the optional field pFCS of the GFP frame. The allowable values are: true or false.
Client Type: indicates the transported layer (ets or Lingaggr)
The Flow Control is used to inform the far-end connected port about the congestion state of the
receiver. If the receiver buffer is full, the transmitter sends a “Pause” frame to the far-end, in order
to stop sending packets
Default PAUSE behavior (It applies only in the case that the AutoNegotiation-AdminStatus is in
“disabled”):
Asymmetric-PAUSE: the interface can generate and transmit to the connected Ethernet device the
Pause Frames
disabled: the interface can NOT generate and transmit to the connected Ethernet device the Pause
Frames

Issue 01
Step 3: Local port configuration (MAU)
1. Specify the CSF and SSF MAU Action (see Notes)
Information given when the auto-

negotiation is enabled
2. These parameters are displayed only if you set Default PAUSE behavior =
asymmetric-PAUSE in the Ethernet port tab (previous page)

In case of Auto-negotiation “Enabled” the capability for the Pause behavior must be set on the dedicated
window:
bfdxPause: Symmetric Pause Frame generation
bfdxAPause: Asimmetric Pause Frame generation
Default Type: the type of physical I/F.

b100baseTXFD for 100 Mbit/s (ETHMR electrical module only)
b1000baseXFD for 1GE (1000Mb/s) (ETHMR and GE (ANY-DATAS) module)
b10GbaseR for 10GE (10,000Mb/s) (GE (ANY-DATAS) module only)
CSF consequent actions for failure propagations: in front of defect conditions detected over local
interfaces OR network traffic blocked over a local Ethernet Interface (Port-setting Administration
feature)
SSF consequent actions for failure propagations in front of defect conditions detected over SDH-based
interfaces OR network traffic blocked over a SDH-based Interface (Port-setting Administration feature);
N.B: Auto-Negotiation can be enable or disable even if the port is “up”.

Issue 01
Step 3: Local port configuration (Shaping)
1. To enable the Egress Shaping rate, click on Enable
3. Click on Save
2. Define the shaping rate at the egress port


Issue 01
3 Point-to-point cross-connection
Step 4: create the Data Point-to-Point XC
This option allows to create a Point to Point cross-connection between
two Ethernet port (Local to Remote (VCG), Local to Local, VCG to VCG)
Select: Connection ETS XC P2P
1. Click on Create
2. Select the port (local

in this example)
3. Select the Local port


Issue 01
Step 4: create the Data Point-to-Point XC
second point of the connection:
remote port in this example
5. Select the remote port
6. Click on “Save & Exit”


Issue 01
Step 4: Data Point-to-Point XC result
The Traffic Descriptor is not taken into account


Issue 01
Check the created objects
Class. XC2
IN OUT
Remote Port
FLOW-1 FLOW-2
1-1-17-1-1
TDM port A
Local Port
TD By opening the Remote port,

VCG
Class.
you can see OUTFLOW-1 and
XC3 INFLOW-2
OUT IN
FLOW-1 FLOW-2
TD


Issue 01
Check Inflow
Click on the InFlow

Link
The Policing is disabled. Thus

the TD is not applied.
The assigned classifier applies no filtering


Issue 01
Check Outflow
Click on the OutFlow Link:

in this way it’s possible to
change the user label
Click on Save to confirm the settings


Issue 01
Delete the Point-to-Point XC
This option allows to delete a Point to Point cross-connection
Select: Connection ETS XC P2P
1. Click on Search
3. Click on Delete: both direction will be delete in one step
2. Tick the box 4. Click on Yes


Issue 01
Blank Page


Issue 01
4 Flow Based Switching connection


Issue 01
Properties
Flow based Switching cross-connection:

connects inflow and outflow for Ethernet services
can be point-to-point or point-to-multipoint
is unidirectional
the operator can specify the parameters for the inflow and outflow: traffic
descriptor, policing, classifier, …
each port can support several connections
is supported by both local and remote ETS ports


Issue 01
Involved objects
Eth. in
VC4
port A
port B
Eth Eth
SDH
SDH
NE-A NE-B
Data XC
Data XC
TDM XC
TDM XC
CLASSI CLASSI
FIER FIER
Eth Eth
port A
port B
IN OUT IN OUT
AU4
Au4
SDH
SDH
FLOW FLOW FLOW FLOW
Traff. Traff.
Descr. Descr.
LOCAL Eth. sl17 REMOTE Eth. REMOTE LOCAL Eth.

module #1 port#1 Port (sl15, VCG Eth. Port B Port B
port #1, (VC4)) (VCG-port1)


Issue 01
Procedure
As far as one equipment is concerned:

Step ...to... Example for equipment A
Create and configure the remote port (VCG port)
1 (remember to set “Service Type=other”; refer VCG port #1 (sl15) as VC4
to pg 35)
create the SDH cross-connection between the
2 VC4 and AU4
remote port and the SDH port
3 configure the local port Sl17, module #1-port#1
Traffic Descriptor: guaranteed,

4 create the traffic descriptor
PIR=50Mbps, PBS=1000 bytes;
Sl17 module #1-port#1 and VCG port #1
create bidirectional ETS connection between the (sl15)
local port and the remote port. Configure the
5 Classifier: Vlan ID from 6 to 10, Vlan
TD, classifier, Color profile, VLAN pop, VLAN
Priority from 4 to 7;
push, and the policing
Enable color-blind policing.
It is supposed that the trainee can perform the steps 1, 2, 3


Issue 01
Step 4: Traffic Descriptor creation
1. Select Data Traffic Descriptor
2. Click on Create
3. Specify the User label

and the Service Type
see next slide

Service Type: Indicates the Traffic codification, according to international standard conversion:
best Effort Service: serves Low priority traffic, which relies on transport layer protocol to recover from
loss and tolerates large delay; e.g. E-mail and file transfer applications. Best Effort denotes BW (PIR >
CIR = 0 in 100kbps increments), which may or may not be available per network operator’s reservation
for Best Effort policy. It may therefore be unavailable under congestion conditions
backGround Service
Regulated Service: serves Medium priority traffic, which relies on transport layer protocol to recover
from occasional loss and requires moderate delay; e.g. client–server applications. Regulated service
denotes BW (PIR > CIR >0 in 100Kbps increments), which may be overbooked per network operator’s
overbooking policy. The portion of bandwidth between CIR and PIR (aka EIR) may therefore be partially
available under congestion conditions.
regulatedService1
regulatedService3
regulatedService4
Guaranteed Service: serves High priority traffic for mission critical applications that require loss–less
delivery and minimal delay. Guaranteed SLA denotes BW (CIR = PIR > 0 in 100Kbps increments), that is
always available regardless of any congestion conditions. Traffic delivered using Guaranteed BW, is
policed to the CIR value with a burst window equal to the CBS.
Guaranteed Service2
CIR -Committed Information Rate [kb/sec]: This is the normal medium rate (expressed in kb/sec) of the
data flow (Effective Bandwidth) and it ranges from 0 to PIR value. It can be set only if the
regulatedService has been selected; in bestEffortService case it is set to 0 by the system; in
guaranteedService case it is set equal to PIR value
PIR - Peak Information Rate [kb/sec]: This is the maximum rate (expressed in kb/sec) up to which the
source can transmit for a short time period and it ranges from 3 to physical-line-rate of the relative Port

Issue 01
Step 4: Traffic Descriptor creation [cont.]
4. Define the Traffic

descriptor parameters
5. Specify the descriptor 6. Specify the descriptor

for Multicast Traffic for unknown MAC traffic
7. Click on Save & ….

CBS - Committed Burst Size [bytes]: This is the committed number of bytes for which the source may
transmit the PIR; it ranges from 0 to 64 MBytes. It can be set only if the regulatedService traffic has
been selected; in besEffortService case it is set to 0 by the system; in guaranteedService case it is set
equal to PBS value. A value greater than MTU (e.g. 2000) is advisable
PBS - Peak Burst Size [bytes]: This is the maximum number of bytes for which the source may transmit
the PIR; it ranges from 1 to 64 MBytes (this max value cannot be greater than the minimum value of 64
MB or 256xCBS. I.e.: if CBS=2000, then PBS< 512 kB). A value greater than MTU (e.g. 2000) is advisable
Multicast / Unknown Traffic: if the field is left empty, the same descriptor of the configured unicasted
traffic is automatically assigned.

Issue 01
Step 4: Traffic Descriptor management
To delete a TD tick the box and click on “Delete”: the TD will

be removed from the list (if no Service is associated to)


Issue 01
Step 4: Traffic Descriptor modification
To modify a Data Traffic Descriptor:
1. Select a TD
3. Modify parameters; click on

Save and then Activate
2. Click on Deactivate

N.B: a traffic descriptor can be modified if no Services are using it

Issue 01
Step 5: create the UNINNI connection
1. Select Connection ETS XC Flow based Switching
2. Click on Create
see next slide


Issue 01
Step 5: create the UNINNI connection [cont.]
This option allows to create the connectivity between the Local port
(UNI interface) and the VCG port (NNI interface)
3. click on Select to choose the

UNI port (sl17 Local port 1)
4. Select the port


Issue 01

NNI port (sl15 VCG port #1)
6. Select the port
7. Insert an User Label

The System shall support the capability to perform, on configuration base, the 'selective' tunneling of
Service BPDU frames (xSTP Provider instances), classifying on MAC DA basis and tunneling across the
network.
MAC DA associated to SBPDU xSTP instances is 01-80-C2-00-00-08.
This feature is intended, ONLY, in order to support the 'CE Dual Homing' interconnection.
Note: If selective tunneling check box is enabled, the traffic descriptor is not displayed.

Issue 01
9. Choose Topology Classifier = PRIO + VLAN
8. Select a TD in the list
Set Classifier values: the displayed parameters

depend on the selected Classification mode

Topology Classifier: according to the selected Topology Classifier, specific parameters must be set:
PRIO+VLAN:VLAN identifier + Priority
VLAN+DSCP/IP: VLAN identifier + DSCP value
Untagged+DSCP/IP: DSCP value (only untagged frame are forwarded)
Default: “Don’t care (all frame are forwarded)
Untagged: untagged frame are forwarded

Issue 01
10. Fill in the classifier parameters, Click on view to check or
according to the classifier topology modify the protocol profile
11. Set Policing mode = color Blind
12. Choose a Color profile in case of color aware selected

Layer 2 control frames: allow to enable or disable the Protocol Frames that can accede the port
Policing Mode:
Disabled: the policing is not performed
Color-blind: the policing is based on the associated TD
colorAware: the policing is based on the associated TD and on the priority colors of the associated
“color Profile” (IETF compliant)
colorAwareNoCoupling: the policing is based on the associated TD and on the priority colors of the
associated “color Profile” (MEF compliant)
colorAwareWithCoupling: the policing is based on the associated TD and on the priority colors of the
associated “color Profile”; Coupling Flag mode is managed (MEF compliant).
Color Profile: specifies the association between incoming EVPL priorities and forwarded frame coloring
VLAN pop: if enabled, it pops out the “Stacked VLAN” field of the incoming Ethernet frame

Issue 01
VLAN push is used to attach a VLAN to

the customer frame.
VLAN pop at UNI interface, is used to
cut the Customer VLAN
VLAN
Push
IN OUT
FLOW FLOW
UNI VCG
13. Click on Save & continue port VLAN port
Pop

Issue 01
Step 5: create the NNIUNI connection
NNI port (sl15 VCG port #1)
15. Select the port



Issue 01
Step 5: create the NNIUNI connection [cont.]
17. Select the port
18. Insert an User Label


Issue 01
20. Choose Topology Classifier = PRIO + VLAN
Set Classifier values: the displayed parameters



Issue 01
21. Fill in the classifier parameters, Click on view to check or
according to the classifier topology modify the protocol profile
22. Set Policing mode = color Blind
23. Choose a Color profile in case of color aware selected


Issue 01
VLAN push is used to attach a VLAN to

the frame for interworking
VLAN pop at NNI interface, is used to
cut the internal VLAN (provider VLAN)
VLAN
Pop
UNINNI
24. Click on Save & exit
OutFlow Inflow
UNI TD VCG
port VLAN port
Push


Issue 01
Check the created objects: InFlow
2. Click on Search
3. Select an InFlow
To delete a Flow based CXC, tick the box and click

on Delete. The XC will be removed from the list

Issue 01
Check the created objects: InFlow [cont.]
Click on the View to display or modify

the Classisfier parameters
Click on the View to display or

modify the TD parameters
Click on Bitmask details to check

or modify the protocol profile
Click here to activate the PM on InFlow


Issue 01
Check the created objects: InFlow [cont.]


Issue 01
Check the created objects: Classifier
2. Click on Search
3. Select an InFlow


Issue 01
Check the created objects: Classifier [cont.]
It allows to set a further classifier: it must be in

the scope of the same Classification mode
4. Click on View 5. Click on Create
Click on Search to display

the configured classifiers
for this InFlow


Issue 01
6. Click on Save & Continue to add

another classifier or Save & Exit to
finish the classifier configuration



Issue 01
Check the created objects: OutFlow
2. Click on Search
3. Select an OutFlow
To delete a Flow based CXC, tick the box and click

on Delete. The XC will be removed from the list

Issue 01
Check the created objects: OutFlow [cont.]
It allows to modify the User Label
Click here to activate the PM on OutFlow


Issue 01
Color Profile and Policing
Are Traffic Descriptor and Color

Policing Color Profile Profile used to classify the frames Note
as green, yellow and red?
Traffic descriptor : no
disabled #No Profile
Color Profile : no
different from #No Traffic descriptor : no Classifier is
disabled necessary
Profile Color Profile : yes
it's not possible to assign Traffic descriptor : yes
color blind
a Color Profile Color Profile : no
color different from #No Traffic descriptor : yes Classifier is
aware Profile Color Profile : yes necessary
Rate
Overall Frame
classification
Red Red Red
PIR
“Color aware" policing and Yellow Yellow Red
“Color Profile" can be CIR
used just with Regulated Green Yellow Red
traffic descriptor type
0
Green Yellow Red Frame classification
according to the Color
Profile

Issue 01
Color Profile and Policing [cont.]
CLASSIFIER
TRAFFIC DESCRIPTOR Vlan=10
Type: Regulated Pri = from 0 to 7
CIR = 20Mbps
My Color Profile PIR = 40Mbps
Prior. 0 red
Prior. 1 red
Prior. 2 red Eth. in
Prior. 3 yellow NE-A VC3 NE-B
Prior. 4 yellow
port A
Prior. 5 yellow
port B
Eth Eth
SDH
SDH
Prior. 6 green X Y
Prior. 7 green Vlan=10; Vlan=10;
Pri=4 Pri=4
X: Overall Frame Y:
Policing
TX bit rate [Mbps] classification RX bit rate [Mbps]
color
15<CIR yellow 15
aware
color
CIR<25<PIR yellow 25
aware
color
45>PIR yellow, red ~40
aware

Issue 01
Color-blind policing
CLASSIFIER
Vlan=from 10 to 11
TRAFFIC DESCRIPTOR Pri = from 4 to 5
Type: Regulated
CIR = 20Mbps
PIR = 40Mbps Eth. in
NE-A VC3 NE-B
Vlan=10; Pri=4, 5, 6
port A
port B
Eth Eth
SDH
SDH
Vlan=11; Pri=4 X Y
Vlan=12; Pri=5
Vlan=10; Pri=4, 5
Vlan=11; Pri=4
X: Frame Y:
Policing
TX bit rate [Mbps] classification RX bit rate [Mbps]
60 disabled Not supported ~48 (limited by VC3)
color
15<CIR green 15
blind
color
CIR<25<PIR green, yellow 25
blind
color green, yellow,
45>PIR ~40
blind red

Issue 01
Push & Pop of VLAN
Data
Data Data
Classifier acts Classifier acts
C-VLAN on S-VLAN
C-VLAN on C-VLAN SDH C-VLAN
S-VLAN
ETH NE-A ETH NE-B ETH
Flow C XC
Flow CXC
SDH XC
SDH XC
CLASSI CLASSI
FIER FIER
Eth Eth
port A
port B
AU4
SDH
IN OUT IN OUT
SDH
AU4
FLOW FLOW FLOW FLOW
VLAN VLAN
Push Pop

C-VLAN is missing in case of untagged frames

If VLAN Pop is enabled on the Inflow of NE A, the C-VLAN is removed from the incoming frames

Issue 01
Push of VLAN
Set to enabled
Priority of the pushed VLAN can be:

• fixed: priority's value is decided by the operator.
"Stack Priority" field contains the priority's value to
be assigned to all the incoming frames.
"Priority Mode" must be "Color Blind“
• color sensitive: priority's value depends on the
VID of the pushed VLAN classification of the incoming frame.
The operator must write the VID's "Stack Priority" field contains the priority's value to
value in the "VLAN Value" field. be assigned to the green frames.
This VID is attached to all the "Stack Priority Yellow" field contains the priority's
incoming frames. value to be assigned to the yellow frames.
"Priority Mode" must be "Color Aware"


Issue 01
5 Link Aggregation


Issue 01
5 Link Aggregation
Introduction
Link Aggregation is a method for aggregating N parallel instances of full

duplex point-to-point links, operating at the same data rate (FE, GBE,
10GBE), into a single logical link. Specifically, a Link Aggregation Group
is defined, such that a MAC client can treat this group as it were a
single link. (max N=16)
Link Aggregation is supported on Local ports and VCG ports.
The main goals of Link Aggregation are:

Increased Link Capacity: the performance is improved because the capacity
of an aggregated link is higher than that one provided by a single physical
link.
High Link Availability: the loss of a link within an aggregation group reduces
the available capacity but the connection is maintained and the data flow is
not interrupted.
Statistical distribution of frames across the links (relying on hashing key)

Constraints:
All involved ports must work at the same rate.
All involved ports must have the same configurations, regarding Auto Negotiation and Flow Control.
All aggregated links must be point-to-point (Multicast is not allowed).
All involved interfaces must work in full-duplex modality.
All involved ports must be Local (Remote ports are not allowed).
Actor and Partner ports (local and far sides) must be of the same type.

Issue 01
5 Link Aggregation
Link Aggregation management in the network is based upon the

communication, between the aggregate partner equipments, of LACP
messages (Link Aggregation Control Protocol). The LACP packets
transport information about set-up, aggregation capability, links
failures, automatic reconfiguration after failure, etc.
The Link Aggregation control messaging is managed by means of special
control frames LACPDU (Link Aggregation Control Protocol Data Unit),
periodically sent, in band, by the nodes using the Link Aggregation
function.
All the packets belonging to the same conversation are transported over
the same link.
More conversations can be transported on the same link.
A fair load-balancing is not guaranteed, since conversations and packets
can not be fragmented.


Issue 01
5 Link Aggregation
The packets distribution over the constituting links is based upon

classification of the following five masks:
Mask0 (Default) - <MAC Destination Address(DA), MAC Source Address(SA)>;
Mask1 - <MAC (DA), MAC (SA)>+ up to 3 MPLS Labels;
Mask2 - [<MAC (DA), MAC (SA)> + up to 3 MPLS Labels] + <C-VID, S-VID>;
Mask3 – [<MAC (DA), MAC (SA)> + up to 3 MPLS Labels + <C-VID, S-VID>] + <IP
SA, IP DA>;
Mask4 – [<MAC (DA), MAC (SA)> + up to 3 MPLS Labels + <C-VID, S-VID>] + <IP
SA, IP DA> + <Destination Port Number, Source Port Number>;


Issue 01
5 Link Aggregation
Example
LAG size = 2 out of all the aggregated links, two are active and the rest are
stand-by
LAG#1 Aggregate Link LAG#2
UNI UNI
PR=1 1 1 PR=1
active
UNI UNI NNI

NNI
4 PR=2 2 2 PR=2 4
active
UNI UNI
PR=3 3 3 PR=3
NE A stand-by NE B
Admitted range Value for NE A Value for NE B

LAG name LAG#1…LAG#123 LAG#1 LAG#2
Actor Admin Key 1… 65535 10 20
Actor System Priority 0… 65535 100 200

A priority value is associated to each port of the bundle; lower values mean higher priority.
A port of the group is classified, by the system, in “Active” or “Stand-by” state, depending from the
port-priority values and from the LAG-size. E.g.: if port-rate=1Gb/s, LAG-size=5, number of ports=7,
then 2 ports (those ones having lower priorities) are classified as “stand-by” by the system.
Each system has a System Identifier that is composed of System Priority value and System MAC Address.
Master system is the one having the lower System Identifier value.
In case that the port priorities between the two connected equipments do not match properly, then the
Master system can change the port priorities of the peer system.
In case of a protected traffic, if a link failure occurs, the traffic of the failed link will be switched to the
stand-by port having a priority value just lower than the failed one.
Both Actor (local) and Partner (far) systems must switch accordingly.
If the traffic is not protected, i.e. no stand-by ports are configured, then the traffic of the failed link
will be redistributed to all ports, if bandwidth is available. In this case frames discarding may occur.
The redistribution of the traffic after failures impacts all the involved links, therefore the transport is
not hitless for all the conversations in operation.
The reconfiguration is triggered by the LOS on aggregate ports.
The reconfiguration is accomplished within 1 second.

Issue 01
5 Link Aggregation
Procedure
Step Action
1 Create the aggregator
2 Configure the aggregator
3 Configure the port as Link Aggregator type
4 Port assignment and configuration


Issue 01
5 Link Aggregation
Step 1: create the aggregator
1. Click LAG Group (Link Aggregation Group) Result
2. Modify the Name: 1…123 3. Actor Admin key: 1…65535

4. Actor System Priority: 0…65535
5. Size: 1…16
7. Click on Save 6. Choose the hashing key for LAG

Name: Allows to set the name of the LAG. The only suffix after “#” can be set by the user, with an
integer in the range 1-123.
Admin State: Administration status. The entry field can be set only after the LAG creation option. The
values are: enable (the LAG is in-service) or disable (the LAG is out-of-service).
Actor Admin Key: Indicates the LAG “Key”, the parameter identifying this LAG; integer in the range 1 -
123.
Type: Indicates the type of port (read only field, fixed by the system to
Size: it specifies the number of port that can be aggregated (max: 16)
User Label: Indicates the LAG name as defined by the user.
Actor System Priority: Indicates the LAG Priority. This parameter, together with the LAG Mac Address,
forms the “System Identifier”. The lowest System Identifier value will be elected as the “Master” of
the link, i.e. the one that will drive the actions in case of events such as failures, switches, etc.
Possible values are integers in the range 0-65535.
Maximum MRU: Specifies the maximum receive units for the LAG.
Hash Input: it defines the packet distribution over the constituting links. Classification is based on:
Mask0 (default) - <MAC Destination Address(DA), MAC Source Address(SA)>;
Mask1 - <MAC (DA), MAC (SA)>+ up to 3 MPLS Labels;
Mask2 - [<MAC (DA), MAC (SA)> + up to 3 MPLS Labels] + <C-VID, S-VID>;
Mask3 – [<MAC (DA), MAC (SA)> + up to 3 MPLS Labels + <C-VID, S-VID>] + <IP SA, IP DA>;
Mask4 – [<MAC (DA), MAC (SA)> + up to 3 MPLS Labels + <C-VID, S-VID>] + <IP SA, IP DA> + <Destination
Port Number, Source Port Number>;
EthClient Type: The entry field can be set only after creation. The values are: ets (for Ethernet
Transparent System) or etb (for Ethernet Bridge System).

Issue 01
5 Link Aggregation
Step 2: configure the aggregator
2. Select the LAG tab
1. Select the LAG
5. Click on Save
& …. 3. Set Admin Status = enable
4. Choose the client type: ets or etb

And then click on Save

The Link Aggregator configuration panel contains the parameters previously described with the following
differences:
Name: As described in the previous section. A read only field.
Admin State: Allows to set the Administration status. Possible values are: enable or disable
Type: As previously described, but read only field
Oper. State: The read-only field indicates the current operational status of the Port, information
about the actual state of the Aggregation Port regarding the traffic; possible values: up (the traffic
on Aggregation Port is active) or down (the traffic on Aggregation Port is inactive).
User Label: Indicates the LAG by means of a name defined by the user
Bandwidth: Indicates the actually used Bandwidth of the LAG, after that Aggregated Ports have been
associated to this LAG. It is the sum of Aggregated Ports rates
Actor Admin Key: Indicates the LAG “Key”, the parameter identifying this LAG; integer in the range
1 -123
Available Band: Indicates the remaining Bandwidth of the LAG, not yet used by Aggregated Ports
Actor System Priority: Indicates the LAG Priority. This parameter, together with the LAG Mac
Address, forms the “System Identifier”. The lowest System Identifier value will be elected as the
“Master” of the link, i.e. the one that will drive the actions in case of events such as failures,
switches, etc. Possible values are integers in the range 0-65535.
Flooding rate: Allows to set the maximum rate of packets having unknown Addresses, for this LAG,
that can be flooded to all ports.
Actor System ID-A read-only field fixed by the system indicates the “System Identifier”, composed of
the LAG Mac Address and the above Actor System Priority. The LAG having the lowest LAG-System
Identifier value will be elected as the “Master” of the LAG link, i.e. the one that will drive the
actions in case of events such as failures, switches, etc.
See next page
Issue 01
5 Link Aggregation
Step 3: configure port’s service as “other”
1. Select PHYSICAL
2. Set other
3. Click on Save


Issue 01
5 Link Aggregation
Step 3: configure the ports as Link Aggregation type
1. Select the UNI port (Local port)
2. Set Client type=Linkagg”
3. Click on Save

LACP Type: Indicates if the Link Aggregation Control Protocol is ON (i.e. lacpOn is active on this
aggregator) or OFF (IacpOff inactive); read only field, fixed by the system.
LACP Enabled: Specifies if the LACP is enabled or disabled.
Actor Op. key: A read-only field fixed by the system indicates the actual operational value of LAG-key
for this LAG.
Maximum MRU: Specifies the maximum receive unit for the LAG
Size: Allows to set the size of the LAG, i.e. number of Aggregated Ports. The values are integers in the
range 0 to 16.
Protocol Profile: Allows to set the protocol profile for the LAG
Asap Name: An entry field displays the name of alarms profile to be associated to the current Port. The
Select hyperlink allows to start the selection procedure. After the selection procedure, the chosen
value will be reported.
MTU: Allows to set the Maximum Transmit Unit (MTU); size of the largest packet which can be sent
on this LAG interface, specified in octets. Allowed values are integers in the range 1574-9216.
Protocol Profile: (allowed only in Provider Bridge case) The entry field indicates the name of the 2-
bytes provider (S-VLAN-Prototypal) contained into the S-Vlan ethernet frames afferent to the current
Port.
Encaps Method: The entry field indicates the method of MAC packets encapsulation inside the
underlying physical layer. Possible options are: ethernetV2 (default mode, set by the system) or
IEEE8023 (not yet operative).
Frame Distribution: Specifies the frame distribution rate for the selected LAG

Issue 01
5 Link Aggregation
Step 4: port assignment and configuration
1. Select the UNI port Scroll the window up to bottom
once again
2. Configure LAG
3. Set to up
4. Select the LAG the port is

to be bound to
6. Click on Save & Exit

5. Actor Port Priority
(1….255)
After “Save & Exit” the “Admin Status” of the UNI port is automatically set to “up”

Issue 01
5 Link Aggregation
Link Aggregator information
1. Select the LAG
2. Scroll the window up to bottom and select

the Link Aggregation configuration panel

Mac Address: (read only field, fixed by the system) indicating the MAC Address assigned to the selected
LAG.
Partner System Id: (read only field, fixed by the system) This parameter is the System Identifier of the
Partner, i.e. the connected remote LAG.
Partner Admin Key: (read only field, fixed by the system) indicating the LAG Key of the Partner LAG as
set by the user.
Partner Operator Key: (read only field, fixed by the system) indicating the actual operational LAG Key of
the Partner LAG as set by the system.
Partner System Priority: (read only field) indicating the LAG priority of the Partner LAG as set by the user
N. Selected Ports: (read only field, fixed by the system), indicating the number of selected ports, that
are potentially aggregable on this Aggregator.
N. Attached Ports: (read only field, fixed by the system) indicating the number of attached ports, that
are actually aggregated on this Aggregator.
Primary Port: (read only field, fixed by the system) indicating the Primary Port, i.e. the one selected
among all aggregated ports, for carrying special traffic (such as Multicast/Broadcast, xSTP-BPDU, IGMP,
unknown addressed packets flooding, etc.). Primary Port is the first one created in the LAG.
Primary Port Position: (read only field, fixed by the system); indicating the position of the Primary Port
on the equipment connectors.

Issue 01
5 Link Aggregation
Delete the LAG
Scroll the window up to bottom
1. Select the UNI port (LAG port)
2. Click on Configure LAG
Unbind all the

ports
3. Select 0 (Unlink port)
4. Save & exit

After unbound the port, the “Admin Status” is automatically set to “down”

Issue 01
5 Link Aggregation
Delete the LAG [cont.]
6. Set Admin Status = disable

5. Select the LAG
7. click on Save & ….
8. Select LAG Group

10. Click on Delete
11. Click on Yes

9. Tick the LAG


Issue 01
5 Link Aggregation
Alarms on the LAG [cont.]
• LAG is not alarmed if the number of active

links is equal to or higher than the LAG size.
• DEG (minor alarm): the number of active links is less

than the LAG size and there is at least one active link.
•LOS (major alarm): there’s no active link.


Issue 01
Blank Page


Issue 01
6 Virtual bridge - VLAN registration -
RSTP - Filtering Database


Issue 01
6 Virtual bridge - VLAN registration - RSTP - Filtering Database
Introduction
A Virtual Local Area Network (VLAN) is an Ethernet Bridged Network

that is logically (not physically) segmented to separate parts of the
network from other parts of that network, even if those parts overlap
physically. This can be used to ensure that Customer A does not see the
data traffic of Customer B or that R&D data traffic does not mix with
HR data traffic. It provides thus an alternative to using layer-3 switches
or routers to separate a LAN that gets too large.
Any port can belong to a VLAN and the frames it unicasts, broadcasts or
multicasts are first flooded then forwarded only to other ports in the
same VLAN. Example: D
VLAN 1 has A and D
VLAN 2 has B and F
D
F
VLAN 3 has C and E
1|D
8
J
VLAN
A D
E
P
0
4
k for
d trun
B S ha r e s 1 , 2 , 3
C VLAN


Issue 01
If we need to segregate traffic of two different customers that are

using the same customer VLAN it is necessary to use a second TAG
(Stacked VLAN) . Provider Bridge (IEEE 802.1AD) implements the
solution.
TSS_320 802.1Q features:
A default VLAN value, PVID=1 is allocated (native VLAN) on all ports.

The Pvid value can be changed but not removed.
The port VLAN ID can be configured to any value (0-4095)
0priority tagged
1native Vlan
A VLAN tag to all incoming “untagged or priority based” frames based
on the port on which the frame was received
A tagged frame is forwarded to a port only if the port belongs to the
VLAN indicated by the VID of the frame

Issue 01
The incoming packets are inqueueing in two queues (CoS), as follows:

from priority bit 0 to 5Low queue
from priority bit 6 to 7High queue
The NE supports the regeneration of priority bits for incoming packets


Issue 01
Virtual bridge
ETS ETS Before using a port (local

or remote), it must be
defined as ETS or ETB
(ETS is the default)
MAC & C-VLAN based

Frames Switching
ETB ETB
ETB
ETB: Ethernet Transport Bridge ETS: Ethernet Transport Service


Issue 01
Scenario
5 ETB port registered for VLAN#5 RSTP
root bridge
5
5 MAC of Bridge A: 00 20 60 2c 28 00
2 1
Designated port
5 5
Designated port
Bridge A
Root port Root port
Alternate port
8 1
1
5 5
5 2 2
designated bridge 5 5
designated bridge
Bridge C Designated port Bridge B
MAC of Bridge C: 00 20 60 71 68 00 MAC of Bridge B: 00 20 60 36 9b 00

This scenario is just an example.

RSTP has been chosen just for simplicity. Also the other spanning tree algorithms can be used.

Issue 01
802.1Q bridge configuration
Bridge A
Step Purpose Example

1 configure the bridge type Virtual, RSTP
2 configure the port as ETB Local port 1, 2 and 5 (Sl-17),
3 set the admin status of the port to Up Local port 1, 2 and 5 (Sl-17),
“Configure Bridge Port" parameters (ingress

4 keep the default configuration
filtering, acceptable frame type)
5 register the port on the VLAN Local port 1, 2 and 5 (Sl-17), on VLAN#5
6 Check the Ether Type Local port 1, 2 and 5 (Sl-17


Issue 01
Step 1: Configure the bridge type
1. Select Data Bridge Configuration
2. Set Bridge Type = Bridge802.1Q (Virtual bridge)
3. Choose RSTP as Spanning tree
4. Click on Save & continue
In order to change the bridge

type, all the etb ports must be Down
The Bridge tab displays the Bridge Configuration panel that contains the following parameters:
Bridge Type - indicates what types of mechanism this bridge performs. The values are:
Bridge802.1Q - Virtual Bridge Type
Bridge802.1ad - Provider Bridge Type
Protocol Type - indicates the Type of Spanning Tree protocol. The values are:
manualDisable - is used to disable the protocol on the root bridge.
RSTP - is used to enable RSTP
MSTP - is used to enable MSTP

Issue 01
Step 2 and 3: configure port’s service as “other”
1. Select PHYSICAL
2. Set other
3. Click on Save


Issue 01
Step 2 and 3: configure the port as ETB and set it up
4. Set Admin status = up
1. Select a Local port
5. click on Save
3. click on Save 2. Choose client type = etb

Ethernet port panel - It allows to change the settings of the resource and displays the following
parameters:
Connector present - indicates if the interface has a physical connector. The values are: true or false
Type - indicates the type of port (fixed to “ethernetCsmacd"). The values fixed: ethernetCsmacd
Speed - indicates the actual configured rate. The values are: 100000 (100 Mb/s) or 1000000 (1 Gb/s)
or 10000000 (10 Gb/s)
Alias - indicates the friendly name for the interface that can be set by the user
Encapsulation mode - indicates the method of MAC packets encapsulation inside the underlying
physical layer. The values are: ethernetV2 (default) or IEEE8023
Maximum MRU - indicates the Maximum Receive Unit size of the largest packet that can be
sent/received on the interface, specified in octets. The value ranges from 1574 to 9216. In case of
Provider Bridge, for ETB ports, the following values are allowed: from 1600to 9242
Promiscuous mode - indicates indicating whether this interface has to inspect the packets' MAC
addresses. The values are: true or false
FCS discard errored frame - indicates the insertion or removal of GFP-FCS (Frame Check Sequence)
field into the optional field pFCS of the GFP frame. The allowable values are: true or false
Client type - indicates the transported layer. The allowable values are: ets (for Ethernet Trans-
parent System), etb (for Ethernet Bridge System) or LinkAgg (for Link Aggregation System).
Underlie layer - indicates the associated layer. The allowable values are: mau (for Ethernet Trans-
parent System), vconc (virtual concatenation to permit the setting of the “virtual-concatenation
granularity" mode) or sdh (to permit the setting of the “Rate-Limiting" mode. NOTE: this value is
given only in the case that the concatenation number for the VC4 is equal to 1)
Link up/down trap - indicates whether linkUp / linkDown traps (notification upon the changing of
the node operational state from up to down and vice versa) should be generated for this interface.
possible options: enabled / disabled the associated layer. The values are: enabled or disabled
Physical address: MAC Address of the port
Issue 01
Step 4: Configure Bridge Port parameters
The port must be Down
Port VLan Identifier: VID used

for the untagged frames: default =1
1. Select an a port and

select “Bridge” tab
Acceptable frame type: this parameters permits
the modification of the ingress filter port
2. When all the parameters modify the bridge parameters
have been configured, do Save


Issue 01
Step 4: Configure Bridge Port parameters [cont.]
Click here to modify the
bridge priority
4. When all the parameters have

been configured, do Save
See step 5 for the VLAN configuration


Issue 01
Detail 1 (Default User priority)
modify the default value
Current default user priority
2. Tick the new value and do Apply
3. Click on Save
Default User Priority: it allows to set the UserPriority to be assigned by default to untagged frames. Note:
its setting is possible only if the ETB port is in “down” status.
Regeneration User Priority: it allows to associate a Regeneration Priority to this ETB port.

Issue 01
Detail 1 (Regeneration User priority)
modify the default value
5. Click on Save
2. Tick the priority to change
3. Choose the new value
4. Click on Apply

Frames with: Bridge Frames with:

• VID = 5 X • VID = 5
Y
• Priority = 2 • Priority = 4
5 5

Issue 01
Step 5: register the port on the VLAN
1. Select Data Virtual LAN Management Virtual LAN
Repeat this steps for all the

others port, for NE A, B and C
2. Select the board, choose the

range and then click on Search
VLAN#1 is the default for untagged frames
3. Write the VLAN ID =5
4. Click on Create see next slide

The virtual LAN management provides reports the registered VLANs associated to the Ethernet interface
existing on the each data card and in specific range. Maximum is 100 in time.
The operator can register/create a new VLAN in range 2-4095.
The VLAN tab reports, in tabular form, the VLAN identifiers, in the specified range, already registered on
the selected Data Board, and, in the same row, the relevant existing Ethernet Ports on which a VLAN is
registered.
In the case of Virtual bridge, all the existing (and activated) ETB ports (and ETB LAGs, in case of “Agg
Group Management”) of the board are tabled. While in the case of Provider Bridge all the existing (and
activated) ETS and ETB ports (and LAGs, in case of “Agg Group Management”) of the board are
presented. The values are:
VLAN#: The VLAN Identifiers (number)
Limit in learning process: Specifies the process that observes the Source Addresses (SA) and VIDs of
received frames, updates the filtering database, conditionally on the port state
Tagged: Specifies that the Port is part of the “Member” of the corresponding VLAN domain (i.e.
frames are accepted, at the relevant ports, if having Priority and VLAN information)
Untagged: Specifies that the Port is part of the “Untagged Set” (i.e. frames are accepted, at the
relevant ports, without Priority and VLAN information) of the corresponding VLAN domain
n.a.: Specifies that the Port does not belong to the corresponding VLAN domain.

Issue 01
Step 5: register the port on the VLAN [cont.]
5. Select the board
6. Consider the “Port Tagged Set”

8. Click on >> to move the
port to the other side
7. Select the port


Issue 01
Step 5: How to modify the VLAN registration
Tick the VLAN, to delete it

2. Click on “tagged” or “untagged”
2. Choose the new configuration: “tagged” “untagged” or “n.a.”


Issue 01
Step 6: How to check the Ether Type
1. Select a port 2. Scroll downwards the window

up to the Flow management
4. click on Save if you wont modify

the VLAN protocol profile
3. Choose the Ether Type

The system is required to support classification of Ethernet input flow at UNI on Ethertype basis, i.e.
providing ETS classifier based on Ethertype value of the Ethernet header, after the tagged field (if
present):
The following Ethertype values can be configured in classification process :

0x0800: IP, Internet Protocol
0x0806: ARP, Address Resolution Protocol
0x8035: DRARP, Dynamic RARP/RARP, Reverse Address Resolution Protocol
0x814C: SNMP, Simple Network Management Protocol
0x86DD: IPv6, Internet Protocol version 6
0x880B: PPP, Point-to-Point Protocol
0x8847: MPLS, Multi-Protocol Label Switching (downstream)
0x8848: MPLS, Multi-Protocol Label Switching (upstream)
0x8863: PPPoE, PPP Over Ethernet (Discovery Stage)
0x8864: PPPoE, PPP Over Ethernet (PPP Session Stage)

Issue 01
Detail 1: How to create or delete a Ethernet Type
1. Select Data VLAN Profile
2. Click on Create
3. Define the User Label

and Ethernet Type
4. Click on Save & ..
Tick the Ethernet Type, to delete it


Issue 01
RSTP analysis
Operation
Check the bridge role
Check the port role
Understand the rest of the provided RSTP parameters


Issue 01
Check the bridge role
2. Select the BRIDGE tab
1. Select an ETB port
3. Do Select for (X)STP Per Bridge

Port VLAN Identifier: it is the PVID parameter, i.e. the VID to assign to “untagged" or “only-priority-
tagged" frames retransmitted by this port. In consequence, this Port is included in the “UntaggedSet"
of this indicated VLAN. Note: its setting is possible only if the ETB port is in “down” status; default
value is 1.
Ingress Filtering: it refers whether the receive frame filter is enabled/disabled. “true” means that the
filter is enabled; it discards all the frames having VLAN-ID that do not have this port on their relevant
“MemberSet". VLAN dependent BPDU frames (such as GMRP) are filtered too. NOTE: VLAN independent
BPDU frames (such as GVRP and STP) are not filtered.
Acceptable Frame Type: Possible values:
admitAll to accept all types of ethernet frames (tagged & untagged)
admitOnlyVlanTagged to accept only VLAN tagged ethernet frames
Default User Priority: it allows to set the Priority to be assigned by default to untagged frames. Note: its
setting is possible only if the ETB port is in “down” status.
Regeneration User Priority: it allows to associate a Regeneration Priority table to this ETB port in order
to change the frame’s VLAN priority. Note: its setting is possible only if the ETB port is in “down”
status.

Issue 01
Check the bridge role [cont.]
Priority: “Priority value” & “Local system ID”
Address: it’s the Bridge Identifier (“Priority

value” & “Local system ID” & “Bridge’s MAC”)
Designated root: it’s the Bridge

Identifier of the root bridge
IF (Address = Designated root) THEN the bridge is the root bridge
The Root bridge is the bridge with the lowest Bridge Identifier (Address box)

Priority: priority of the bridge (to whom this port belongs) to become the root bridge, at start–up or in
case of failure of the actual root bridge; 16–bit decimal value, but only the most significant 4 bits are
settable. This value is used by STP procedure to designate the root bridge.
The possible options are 16 values, settable by means of the associated incrementing/decrementing
keys: (best priority = least numerical value).
Address: (read only, set by the system); bridge identifier of this selected bridge, as specified in
IEEE802.1D, composed of 8 octets, of which the first 4 bits representing a priority parameter (as fixed
in the above item), the next 12 bits are considered as local system ID, the remaining 6 octets represent
the bridge MAC address. The root bridge of the network is the bridge having this parameter with lowest
numerical value.
Designated Root: (read only) representing the bridge Identifier of the bridge assumed to be the boot
bridge for the current Spanning Tree instance.

Issue 01
Check the bridge role [cont.]
Priority box Priority value

Dec Hex Dec
Priority box : 80 00 (Hex)  32768 (Dec) 0 00 00 0 (the best)
4096 10 00 1
Address box : 80 : 00 : 00 : 20 : 60 : 50 : be : 80 8192 20 00 2
12288 30 00 3
16384 40 00 4
Bridge’s MAC address 20480 50 00 5
Priority 24576 60 00 6
28672 70 00 7
Local system ID 32768 80 00 8
36864 90 00 9
40960 A0 00 10
45056 B0 00 11
49152 C0 00 12
53248 D0 00 13
57344 E0 00 14
Bridge Identifier 61440 F0 00 15

Local system ID is always equal to 0 00.

Issue 01
Check the port role
3. Do Select for (X)STP Per Port


Issue 01
Check the port role [cont.]
Port Number as far as the Spanning Tree’s BPDUs

are concerned. It isn’t the module’s number.

Port State: (read only); indicating the current port state as regard the STP process.
Blocking: the frames received by this port will be discarded, thus forcing it out of the active
topology, for preventing frame duplication arising through multiple paths; STP control frames (BPDU)
are not discarded.
Forwarding: the port is participating in the frames relay, STP algorithm computation and MAC
learning procedures, thus it is included in the active topology.
Disabled: all the received frames are discarded; further the Port does not participate in the
operations of the STP or MAC learning processes.
Port Role (read only). See 802.1D:
root: the port offers the lowest cost path from this bridge to the root bridge. It is to be part of the
active topology connecting the Bridge to the Root Bridge.
designated: the port is connecting a LAN, through the current Bridge, to the Root-Bridge
alternate: if the Bridge is not the Designated Bridge for the attached LAN. It offers an alternate
path(in case of failure) in the direction of the Root Bridge to that provided by the root port.
backup: if the Bridge is the Designated Bridge for the attached LAN. Backup Port acts as a backup (in
case of failure) for the path provided by a Designated Port in the direction of the leaves of the
Spanning Tree. Backup Ports exist only where there are two or more connections from a given Bridge
to a given LAN.
disabled: the Port has no role within the operation of Spanning Tree.
Force Port State:
Dynamic: the port is managed by the Spanning Tree Protocol.
Blocked: the frames received by this port will be discarded, thus forcing it out of the active
topology, for preventing frame duplication arising through multiple paths; BPDU frames are not
discarded.
Forwarding: the port is participating in the frames relay, STP algorithm computation and MAC
learning procedures, thus it is included in the active topology.
Issue 01
RSTP parameters: Port Path Cost, …
1. Path Cost: contribution of this port to the path cost of paths towards the root bridge.
2. Designated Bridge: Identifier of the bridge that this port considers to be the designated
bridge for the segment attached to this port.
3. Designated Root: Identifier of the bridge assumed to be the root bridge by the
designated bridge for the segment to which the port is attached.
4. Designated Cost: path cost of the designated port of the segment connected to this
port.
2
1
3
4

Conn type:
edgeport: the port is connected to a LAN that has no other bridges connected to it
pointtopoint: the port is connected to another bridge
nopointtopoint: the port is connected to more other bridges (hub,…)
autopointtopoint: the port automatically realizes the own connection type.
Edgeport and pointtopoint allows a fast STP convergence.
Port path cost Interface’s rate

2000000 10 Mb/s
200000 100 Mb/s
20000 1 Gb/s
2000 10 Gb/s

Issue 01
RSTP parameters: Root Path Cost
Root Path Cost is the cost of the path to the root bridge as seen from
this bridge for this spanning tree instance.
When this bridge is the root bridge this parameter has the value zero.
Otherwise, it is equal to the sum of all the Port Path Costs of the root ports
encountered along the path to reach the root bridge.
1. Open the (X)STP Per Bridge window


Issue 01
RSTP parameters: example
root designated root designated
TSS-320 TSS-320 TSS-320

1 2 3 4 Root bridge
Segment Segment
Bridge C Bridge B Bridge A
BC AB
Bridge parameters
Designated Root A A A
Root Path Cost 17 10 0
Port parameters
Port 1 Port 2 Port 3 Port 4
Port Path Cost 7 19 10 4
Port Designated Bridge B B A A
Port Designated Root A A A A
Port Designated Cost 10 10 0 0

Root Path Cost is the cost of the path to the root bridge as seen from this bridge for this spanning tree
instance.
When this bridge is the root bridge this parameter has the value zero.
Otherwise, it is equal to the sum of all the Port Path Costs of the root ports encountered along the
path to reach the root bridge.
Port Path Cost: contribution of this port to the path cost of paths towards the root bridge.
Port Designed Bridge: Identifier of the bridge that this port considers to be the designated bridge for the
segment attached to this port.
Port Designed Root: Identifier of the bridge assumed to be the root bridge by the designated bridge for
the segment to which the port is attached.
Port Designed Cost: path cost of the designated port of the segment connected to this port.

Issue 01
RSTP parameters: Port Parameters
1. Port priority: priority of this port

2. Port designated pt number: port identifier of the designated port on
the designed bridge for this segment
3. Port designated pt priority: priority of the designated port on the
designated bridge for this segment
1
3

Port Priority
Port Priority box
value
Dec Hex Dec
0 00 0 (the best)
16 10 1
32 20 2
48 30 3
64 40 4
80 50 5
96 60 6
112 70 7
128 80 8
144 90 9
160 A0 10
176 B0 11
192 C0 12
208 D0 13
224 E0 14
240 F0 15

Issue 01
RSTP parameters: Bridge Parameters
Values obtained from the root

bridge and used by this bridge
Values used by all the bridges when

this bridge is the root bridge
Time since change: time (in hundredths of second) since the last time a topology change was detected by
this spanning tree instance.
Topology changes: (read only) total number of topology changes detected by this spanning tree instance
since the management entity was last restarted or initialized.
Hello time: (read only: actual value that this instance is currently using); amount of time between the
transmission of Configuration bridge PDUs by this instance on any port when it is the Root Bridge of the
spanning tree or trying to become so, in units of hundredths of a second (range=1 to 10 sec).
Max age: (read only: actual value that this instance is currently using); maximum age of Spanning Tree
Protocol information learned from the network on any port before it is discarded, in units of
hundredths of a second (range=6 to 40 sec).
Fwd Delay: (read only: actual value that this instance is currently using); this value, measured in units of
hundredths of a second, controls how fast a port changes its spanning state when moving towards the
Forwarding state. The value determines how long the port stays in each of the Listening and Learning
states, which precede the Forwarding state. This value is also used, when a topology change has been
detected and is underway, to age all dynamic entries in the filtering Database (range=4 to 30 sec).
Next best root cost: (only for RSTP); cost of the path to the root through the next best root port as seen
from this bridge for this spanning tree instance.
Next best root port: (only for RSTP); port number of the next port which offers the lowest cost path from
this bridge to the root bridge for this spanning tree instance. The port here indicated will become root
port if the actual root port goes down.
Tx hold count: (only for RSTP); used by the Port Transmit state machine to limit the maximum
transmission rate.

Issue 01
Filtering database
Operation Tool
Create entry for unicast addresses Static Unicast Filtering
Create entry for multicast addresses Static Multicast Filtering
Multicast
i.e.
address Customer BPDU 01 80 C2 00 00 00
0000 0001 1000 0010 ... ... ... ...
This bit is equal to 1


Issue 01
Static Unicast Filtering
WITH FILTER:
WITHOUT FILTER: In order to get bridge A

P1
forward the frames just
Bridge A floods the frames to port 1, configure the
1
generated by P2 because it Static Unicast Filtering
doesn’t know the location of 6 3
00 20 60 12 34 56 Bridge A
P1 5 4
1 8 10 9 P2
6 3 Bridge C Bridge B
Bridge A
5 4 Frames generated by P2:

Dest. Address = 00 20 60 12 34 56
8 10 9 P2
Bridge C Bridge B

Static UF-DB - the connection instances are manually entered by the operator for only towards one Port.

Issue 01
Static Unicast Filtering [cont.]
1. Select Data Virtual LAN Management

DB Filtering Static Unicast Filtering DB
2. Click on Create
3. Click on Search to select the VLAN
4. Tick the VLAN, to change


Issue 01
5. Enter the MAC address (use “:” as separator)
6. select the board



Issue 01
result


Issue 01
Static Multicast Filtering
1. Select Data Virtual LAN Management DB

Filtering Static Multicast Filtering DB
2. Click on Create
3. Click on Search to select the VLAN
4. Tick the VLAN, to change


Issue 01
Static Multicast Filtering [cont.]
5. Enter the multicast MAC address (use “:” as separator)
6. select the board



Issue 01
Static Multicast Filtering [cont.]
result


Issue 01
7 Provider bridge


Issue 01
7 Provider bridge
Provider bridge
Provider Bridge Network Port:
this is the access port to Provider Network (ETH-NNI Interface)
The Ethernet Interface Port Client Type is ETB
Customer Network Port/Provider Edge Port:
this connects the Provider Bridge to customers organizations (UNI interface)
The Ethernet Interface Port Client Type is ETS
Even if the Ethernet Interface Port Client Type is ETS, this port is part of “S-
VLAN Port
The port state is always in forwarding and so auto-learning for ingress
Ethernet frames is always enabled


Issue 01
7 Provider bridge
Provider bridge [cont.]
Provider Bridges add an additional provider tag to customer frames.

Tagging and un-tagging operations follow the IEEE 802.1Q standard
(same ingress and egress rules apply).
A new ether-type is defined for provider bridges, which enables double
tagging.
“802.1Q tagged” or “untagged” frames are processed as untagged by a
provider bridge. 6 bytes 6 bytes
SRC Provider Customer

DST PAYLOAD
TAG TAG
Encapsulated frame
TPID Priority DE VID
Ethertype (802.1AD here)
2 bytes 3 bit 1 bit 12 bits

Remark:
Ethernet type for Provider TAG is 88A8
Ethernet type for Customer TAG is 8100


Issue 01
7 Provider bridge
Provider bridge
6 6 2 2 2 2 42 -1500 4
SVLAN CVLAN
Dest Address Src Address (Type) TAG
8100 TAG
Data FCS
8100/88A8
CVID200
VID200
1 2 1 2
CVID200 VID200
SVID501;CVID200
3 4 3 4
SVID502;CVID200
5 6 5 6
SVLAN 502 SVLAN 501
The Test Example above showes how 802.1AD is used to segregate traffic of two different
customers that are using the same Customer VLAN.


Issue 01
7 Provider bridge
Provider bridge [cont.]
ETS ETS Before using a port (local

or remote), it must be
Provider Bridge
defined as ETS or ETB
(ETS is the default)
MAC & S-VLAN based

Frames Switching
ETB ETB
ETB
ETS
Cross-connection that gets the UNI port participate to the Switching functionality. The
filter on the incoming frames, the Policing, …are configured by the operator and are used.

ETB: Ethernet Transport Bridge

ETS: Ethernet Transport Service

Issue 01
7 Provider bridge
Traffic descriptors for provider bridge
In case of ADD (to bridge) connection, an ETS Inflow is created for the
ETS port.
The ETS Inflow requires two items: Classifier and Traffic Descriptor.
Classifier is a filter on the incoming frames. The frames can be
accepted or discarded according to the filtering criteria chosen by the
operator: VLAN ID, VLAN priority
Traffic Descriptor:
is defined by PIR, CIR, PBS, CBS. Policing can be enabled.
there are 3 types:
CLASS
Traffic Descriptors IFIER
LAN ETS
or ETS
Guaranteed Port INFLOW
SDH
Regulated TD &
Best-Effort Pol.

PIR: Peak Information Rate

CIR: Committed Information Rate
PBS: Peak Burst Size
CBS: Committed Burst Size

Issue 01
7 Provider bridge
802.1ad bridge scheme
ADD (to bridge)

SVID
SVID Push SVID
CLASSI Reg
Reg FIER
LAN ETB LAN
ETS ETS PROVIDER or
or Port Port
SDH INFLOW OUTFLOW SDH
TD &
Frames RP
Pol. PT
SVID
Reg SVID
TD0 Reg
LAN
ETS switching
or ETS PROVIDER ETB LAN
SDH Port OUTLOW INFLOW or
Port
SDH
DROP (from
bridge)
RP
SVID PT
Pop
RP: Regenerated Priority TD: Traffic Descriptor

PT: Protocol Type TD0: Traffic Descriptor "Null"

Issue 01
7 Provider bridge
Test bench
Each port is registered for S-VLAN#5 (S-VID=5) Provider bridge

RSTP
Local port
(sl 17)
ETS
Remote port
5 (VCG port #1
(sl 15)) ETB
TSS-320


Issue 01
7 Provider bridge
Procedure for ingressing ETS

1 configure the bridge type and QoS Provider, RSTP, QoS
set the admin status of the port to Sl17, module #1-port#1 and Remote port (VCG port
2
Up #1 (sl 15))
3 register the port on the S-VLAN S-VLAN#5
create the traffic descriptor and
regulated; PIR=10Mbps; CIR=5Mbps; PBS=5k bytes;
4 color profile (creation, management
and modification) CBS=3k bytes; color profile= default (priority)
Traffic descriptor: choose the created one.

Classifier: C-VLAN ID from 60 to 70
5 create the UNI NNI connection C-VLAN Priority from 4 to 6
Enable the policing (color aware).
Push the S-VLAN#5 (S-VID=5)
Ethernet Inflow and Provider Outflow are automatically created
It is supposed that the trainee can perform the step 2


Issue 01
7 Provider bridge
Step 1: Configure the bridge type and QoS
2. Set Bridge Type = Bridge802.1ad

(Provider bridge)
3. Choose RSTP as Spanning tree
4. Click on Save & continue
In order to change the bridge

type, all the etb ports must be Down

Issue 01
7 Provider bridge
Step 1: Configure the bridge type and QoS [cont.]
Traffic Traffic
Descriptors Descriptors
for 8P0D for 5P3D
Guaranteed Guaranteed
Guaranteed(2) Guaranteed(2)
Regulated(1) -
Regulated Regulated
Regulated(3) -
Regulated(4) Regulated(4)
Best-Effort Best-Effort
Back-Ground -
2. Choose the operation mode
3. Click on Save


Issue 01
7 Provider bridge
Step 3: register the port on the S-VLAN
1. Select Data Virtual LAN Management Virtual LAN
Repeat this steps for all the

others port, for NE A, B and C
2. Select the board, choose the

range and then click on Search
VLAN#1 is the default for untagged frames
3. Write the VLAN ID =5
4. Click on Create see next slide

The virtual LAN management provides reports the registered VLANs associated to the Ethernet interface
existing on the each data card and in specific range. Maximum is 100 in time.
The operator can register/create a new VLAN in range 2-4095.
The VLAN tab reports, in tabular form, the VLAN identifiers, in the specified range, already registered on
the selected Data Board, and, in the same row, the relevant existing Ethernet Ports on which a VLAN is
registered.
In the case of Virtual bridge, all the existing (and activated) ETB ports (and ETB LAGs, in case of “Agg
Group Management”) of the board are tabled. While in the case of Provider Bridge all the existing (and
activated) ETS and ETB ports (and LAGs, in case of “Agg Group Management”) of the board are
presented. The values are:
VLAN#: The VLAN Identifiers (number)
Limit in learning process: Specifies the process that observes the Source Addresses (SA) and VIDs of
received frames, updates the filtering database, conditionally on the port state
Tagged: Specifies that the Port is part of the “Member” of the corresponding VLAN domain (i.e.
frames are accepted, at the relevant ports, if having Priority and VLAN information)
Untagged: Specifies that the Port is part of the “Untagged Set” (i.e. frames are accepted, at the
relevant ports, without Priority and VLAN information) of the corresponding VLAN domain
n.a.: Specifies that the Port does not belong to the corresponding VLAN domain.

Issue 01
7 Provider bridge
ETB port 5. Select the board 15 (VCG port)
6. Consider the “Port Tagged Set”
7. select the remote port #1 in the left

side and then Click on >> to move
the port to the other side


Issue 01
7 Provider bridge
ETS port 9. Select the board 17 (Local port))

10. Consider the “Port Untagged Set”
11. select the Local port #1 in the left

side and then Click on >> to move
the port to the other side

Issue 01
7 Provider bridge
2. Click on Create
3. Specify the User label

see next slide

backGround Service
regulatedService1
regulatedService3
regulatedService4
Guaranteed Service2

Issue 01
7 Provider bridge




Issue 01
7 Provider bridge



Issue 01
7 Provider bridge
1. Select a TD



Issue 01
7 Provider bridge
Step 4: Ethernet Color Profile creation (Priority)
1. Select Data Color Profile
This option allows to create a Color Profile to be

associated in case of “ColorAware” policing mode
2. Specify the Color Profile

Mode: Priority
3. Assign a Label
4. According to the selected mode,

5. Click on Save & …. configure the profile

In case of “Priority” mode, the operator can assign a color to 8 different User Priority (0…. 7)

Issue 01
7 Provider bridge
Step 4: Ethernet Color Profile creation (dscp)
1. Assign a label and Specify

the Color Profile Mode: Dscp
2. For dscp mode, configure

3. Click on Save & …. the code points

In case of “DSCP” mode, a color can be assigned to 64 different Code Point (0 ….. 63)

Issue 01
7 Provider bridge
Step 4: Ethernet Color Profile management
To delete a Color Profile tick the box and click on “Delete”: the Color Profile will be
removed from the list (if no Service is associated to)


Issue 01
7 Provider bridge
Step 4: Ethernet Color Profile modification
To modify a Color profile:
2. Select a Color Profile

N.B: a Color Profile can be modified if no Services are using it

Issue 01
7 Provider bridge
Step 5: create the UNINNI connection
1. Select Connection Provider bridge Service
2. Click on Create
see next slide


Issue 01
7 Provider bridge
This option allows to create the connectivity between the payload
data at UNI interface and the bridge ports (NNI interface)
3. Select Topology = UNI - NNI

5. Select the port


Issue 01
7 Provider bridge
9. write a label
6. click on Select to choose the S-VLAN (5)
10. Configure the 7. Choose the range and

VLAN Swap then Click on Search
8. Choose 5
The system supports the VLAN Swap: a single VLAN Tag Pop operation on a ETS InFlow followed by a
single VLAN Tag Push operation on the associated ETS Out Flow (same direction of the InFlow)
network.

Issue 01
7 Provider bridge
Detail 1: C-VLAN swap in the UNI to NNI Ethernet Service
C-VLAN New C-VLAN
IN OUT
FLOW FLOW
VLAN
Pop
2. configure the new C-

1. Set to enabled VLAN and priority
When the VLAN Swap is set to enabled,

automatically the system set to enabled the
VLAN pop and the VLAN push

Issue 01
7 Provider bridge
12. Choose Topology Classifier

= PRIO + VLAN
13. Set Classifier values: the displayed parameters

PRIO+VLAN:VLAN identifier + Priority

Issue 01
7 Provider bridge
Click on view to check or
modify the protocol profile
14. Set Policing mode =

color Aware
15. Choose a Color profile in

case of color aware selected

Policing Mode:
colorAwareWithCoupling: the policing is based on the associated TD and on the priority colors of the
associated “color Profile”; Coupling Flag mode is managed (MEF compliant).

Issue 01
7 Provider bridge
IN OUT
FLOW FLOW
VLAN push/pop at UNI interface is VLAN

provided for inter-working purposes Pop


Issue 01
7 Provider bridge
Check the created objects for UNI NNI connection
2. Click on search
3. Select an InFlow or an OutFlow

with topology = UNI-NNI
To delete a PB service, tick the box and click on

Delete. The XC will be removed from the list

Issue 01
7 Provider bridge
Check the created objects for UNI NNI connection (TD)

Click on the View to display

the TD parameters



Issue 01
7 Provider bridge
Check the created objects for UNI NNI connection (IF)
It allows to modify the TD (see Notes)

Set Classifier parameters,

then “Save” and “Activate”

Traffic descriptor: it is allowed to modify TD for bandwidth change even if the Service is ON: in this case
the change is only admitted in the scope of the same CoS (e.g. change from BE to Guaranteed is not
allowed as well as other mixed possibilities).
Bitmask details: allows to enable or disable the Protocol frames that can accede the port.Clicking on the
Bitmask detail button is possible to display and set the mask

Issue 01
7 Provider bridge
Check the created objects for UNI NNI connection (IF)[cont.]


Issue 01
7 Provider bridge
Check the created objects: Classifier
2. Click on search
3. Select an InFlow


Issue 01
7 Provider bridge

4. Click on View 5. Click on Create
Click on Search to display

the configured classifiers
for this InFlow


Issue 01
7 Provider bridge
6. Click on Save & Continue to add

another classifier or Save & Exit to
finish the classifier configuration



Issue 01
7 Provider bridge
Check the created objects for UNI NNI connection (OF)


Issue 01
7 Provider bridge
Procedure for egressing ETS

1 configure the bridge type provider, RSTP
2 register the port on the S-VLAN S-VLAN#5
3 NULL traffic descriptor creation Regulated; PIR=CIR=CBS=PBS=0
Traffic descriptor: choose the NULL.
4 create the NNIUNI connection
Pop the S-VLAN#5.
Provider Inflow and Ethernet Outflow are automatically created
It is supposed that the trainee can perform the steps 1, 2


Issue 01
7 Provider bridge
Step 3: create the Ethernet Traffic Descriptor
The operator must create also a Null Traffic Descriptor to be
applied in the NNI-UNI direction of the connection
2. Click on Create
3. Assign value 0 to all

parameters

N.B: The “Null TD” must be in the same CoS of the UNI-NNI TD applied on the remote end point.

Issue 01
7 Provider bridge
Step 4: Create the Ethernet Service: NNI UNI
2. Click on Create
see next slide


Issue 01
7 Provider bridge
Step 4: Create the Ethernet Service: NNI UNI [cont.]
3. Select Topology = NNI - UNI

5. Select the port


Issue 01
7 Provider bridge
6. click on Select to choose

the S-VLAN (5)
9. write a label
7. Choose the range and
then Click on Search
8. Choose 5
network.

Issue 01
7 Provider bridge
10. Select a reg Null TD in the list
S-VID
Pop
11. Click on Save & …. S-VID UNINNI
Reg
ETS Ethernet Provider bridge
Port OutFlow Inflow
Null
TD
VLAN
Push


Issue 01
7 Provider bridge
Check the created objects for NNI UNI connection
2. Click on search
3. Select an InFlow or an OutFlow

with topology = NNI-UNI
To delete a PB service, tick the box and click on

Delete. The XC will be removed from the list

Issue 01
7 Provider bridge
Check the created objects for NNI UNI connection (TD)

Click on the View to display

the TD parameters



Issue 01
7 Provider bridge
Check the created objects for NNI UNI connection (IF)


Issue 01
7 Provider bridge
Check the created objects for NNI UNI connection (OF)


Issue 01
Blank Page


Issue 01
8 MSTP


Issue 01
8 MSTP
Introduction
MSTP enables VLANs to be grouped into a spanning tree instance, each

instance having a spanning tree topology independent of other spanning
tree instances. This architecture provides multiple forwarding paths for
data traffic, enables load balancing, and reduces the number of
spanning tree instances required to support a large number of VLANs.
MSTP provides simple and full connectivity for frames assigned to any
given VLAN throughout a Bridged LAN comprising arbitrarily
interconnected Bridges, each operating MSTP, STP or RSTP.
MSTP allows frames assigned to different VLAN to follow separate
paths, each based on an independent Multiple Spanning Tree Instance
within Multiple Spanning Tree Regions composed of LANs and/or MST
Bridges. These Regions and the other Bridges and LANs are connected
into a single Common Spanning Tree.

NE Operation Operator Interface-Ethernet Bridge features Section 2 - Module 2 -- Page 192

Issue 01
8 MSTP
The following picture shows a common design that features access

Switch A with 1000 VLANs redundantly connected to two distribution
Switches, D1 and D2. In this setup, users connect to Switch A, and the
network administrator typically seeks to achieve load balancing on the
access switch Uplinks based on even or odd VLANs, or any other
appropriate scheme.


Issue 01
8 MSTP
The idea is that several VLANs can be mapped to a reduced number of

spanning tree instances because most networks do not need more than
a few logical topologies. In the topology described in the previous
picture, there are only two different final logical topologies, so only
two spanning tree instances are really necessary. There is no need to
run 1000 instances. If you map half of the 1000 VLANs to a different
spanning tree instance, as shown in this diagram, these statements are
true: The desired load balancing scheme can still be achieved, because
half of the VLANs follow one separate instance.

From an end user's point of view, the main drawbacks associated with a migration to MST are:
The protocol is more complex than the usual spanning tree.
Interaction with legacy bridges can be a challenge.

Issue 01
8 MSTP
Each switch running MST in the network has a single MST configuration.
All the switches sharing exactly the same MST configuration belonging
to the same MST region.
MST
Region
ES1/4 c
ES1/4 c
ES1/4 c
STP/RSTP
switch
MSTP switch

MST configuration parameters:
Alphanumeric configuration name

Configuration revision number
4096-element table: it associates each one of the 4096 VLAN supported to a given instance of the MSTP in
the region
It’s up to the NMS to properly set the configuration on all the switches belonging to the same region

Issue 01
8 MSTP
The “name”, the “revision number” and a “digest of the table” of the
MST region are propagated across the network via BPDU.
Once a MST switch receives the BPDU, it looks up the MST parameters:
if they are equivalent to the ones it has, then it learns they belong to the
same MST region
If the digest is different, the port which the BPDU was received from is at
the boundary of the region
RSTP
MST ES1/4 a ES1/4 b ES1/4 c

Region A
MST
Boundary of Boundary of Region B
MST region A MST region B


Issue 01
8 MSTP
Each MST switch must be able to run: STP/RSTP

one Internal Spanning Tree instance switch
one or more instances of MSTP
MSTP switch
RSTP RSTP
=
MST RSTP MST
Region
= Switch Region

one Internal Spanning Tree instance

The IST is an RSTP instance that extends the outside STP inside the MST region
It allows the MST switch inter-works with the other STP/RSTP switches outside the MST region.
It has the capability to represent the MST region as a virtual RSTP switch to the outside world
It runs inside and outside the MST region
one or more instances of MSTP
They are RSTP instances running only inside the MST region, they never interact outside the MST region.
Each MST instance is associated to a group of VLANs.

Issue 01
8 MSTP
IST and MSTi do not send individual BPDU

Each switch sends just one BPDU format, including all the information
for the IST and all the MST instances
BPDUs generated by the MST switches inside the MST Region can be
seen
as a normal RSTP BPDU for the IST instance
contains M-information record for each one of the M-ST instances running on
the ports
Protocol
MST
BPDU Information For IST RSTP
Region
M-Records
ES1/4 c
ES1/4 c
Protocol Information
ES1/4 c
For MST instances
present on the ports RSTP RSTP


Issue 01
8 MSTP
MST BPDU contains also the MST Configuration Identifier
MST Configuration Identifier contains:

Format Selector (1 byte)
Region’s name (32 bytes)
Revision Level (2 bytes)
Digest (16 bytes): it depends on the mapping between VLANs and MST
instances
The bridges with the same MST Configuration Identifier belong to the
same region.


Issue 01
8 MSTP
Example
All the ports are registered for all the VLANs 802.1Q
MSTP
root bridge
for MSTI=3 CIST root
MSTI instance 3: VLAN 15 Bridge A bridge
VLAN 16
VLAN 25
VLAN 26 8 7 MAC of Bridge A:
00 20 60 50 c3 00
Region 1 (name=region1; revision level=1)
Region 2 (name=region2; revision level=2)
MSTI instance 1: VLAN 15 2 7

VLAN 16
MSTI instance 2: VLAN 25 1 1
VLAN 26
Bridge C Bridge B
MAC of Bridge C: MAC of Bridge B:
root bridge for MSTI=1 and MSTI=2 00 20 60 4d 7e 80
00:20:60:50:be:80
MST BPDU contains also the MST Configuration Identifier.

MST Configuration Identifier contains:
Format Selector (1 byte)
Region’s name (32 bytes)
Revision Level (2 bytes)
Digest (16 bytes): it depends on the mapping between VLANs and MST instances:
max 16 MST instances per region
max 4094 VLANs per instance
The bridges with the same MST Configuration Identifier belong to the same region.

Issue 01
8 MSTP
Procedure

1 configure the bridge type 802.1Q, MSTP
configure the port as ETB and
2 ports# 1(C), 2, 7(A), 8, 7(B), 1(B)
set it up
VLAN registration: create all
3 the VLANs of the region and VLAN#15,16,25,26
register the ports
assign the region’s name and region1; revision level=1
4
revision level region2; revision level=2
for region1: MSTI=3 with VLAN#15,16,25,26
create the MST instances
5 for region2: MSTI=1 with VLAN#15,16
assigning them the VLANs
for region2: MSTI=2 with VLAN#25,26


Issue 01
8 MSTP
Step 4: MST region creation
Example for bridge C
3. Do Select for Region number
It’s enough to configure these parameters

for one port of the bridge


Issue 01
8 MSTP
Step 4: MST region creation [cont.]
4. Insert the Name and Example for bridge C

the Revision Level
5. Click on save & exit


Issue 01
8 MSTP
Step 5: MST instance creation
It’s enough to configure these parameters

for one port of the bridge
3. Do Select for MSTID


Issue 01
8 MSTP
Step 5: MST instance creation [cont.]
4. Select MSTID=1 5. Click on Create
6. Select MSTID=1
once again
7. Click on Assign


Issue 01
8 MSTP
9. Click on Save
8. Select the VLAN 15 and 16


Issue 01
8 MSTP
Scroll downwards the window
10. Click on save & exit
Click here to see the MSTID Details Create also MSTI=2 with VLAN#25,26


Issue 01
8 MSTP
MSTP analysis: CIST topology (bridge)
3. Click on Select to check

the CIST parameters


Issue 01
8 MSTP
MSTP analysis: CIST topology (bridge) [cont.]
Bridge parameters for the CIST
First of all, verify that the bridges in the

same region have the same digest


Issue 01
8 MSTP
MSTP analysis: CIST topology (port)
CIST parameters for the selected port


Issue 01
8 MSTP
MSTP analysis: MSTI topology (bridge)
3. Click on Select to select MSTID =1


Issue 01
8 MSTP
MSTP analysis: MSTI topology (bridge) [cont.]
4. Select an MSTID=1 and then

click on Save & exit
5. Click on Select to check the MSTI Per Bridge parameters


Issue 01
8 MSTP
MSTP analysis: MSTI topology (bridge) [cont.]
Bridge parameters for the MSTI


Issue 01
8 MSTP
MSTP analysis: MSTI topology (port)
MSTI parameters for the

selected port and MSTI =1

Master port:
it provides the connectivity from the region to a CIST root that lies outside the region.
it is the same for all the MSTIs

Issue 01
9 Ethernet OAM


Issue 01
9.1 Introduction


Issue 01
9.1 Introduction
Introduction
Until recently Ethernet lacked OAM functionality like that found in in

SONET/SDH or ATM, and therefore was not characterized as “carrier
class.”
Now it has acquired two types of OAM, one developed by the ITU and
IEEE 802.1, and another by the EFM task force.
The former is a full-featured OAM mechanism that can run end-to-end
and includes all traditional OAM elements such as AIS, RDI and
performance measurement. The latter is limited to continuity
monitoring of a single link and is targeted at access applications.
OAM (Operation, Administration, and Maintenance) describes the
monitoring of network operation by network operators. OAM is a set of
functions used by the user that enables detection of network faults and
measurement of network performance, as well as distribution of fault-
related information


Issue 01
9.1 Introduction
OAM functionality ensures that network operators comply with QoS

guarantees, detect anomalies before they escalate, and isolate and
bypass network defects.
Ethernet originated as a Local Area Network (LAN) technology. Since
LANs usually consist of a relatively small number of stations, all
managed by a single entity, defect detection was manual, and
performance was never really a concern. As Ethernet developed,
physically separated LANs were interconnected but still managed by a
single entity (although now an enterprise). OAM was still not a major
concern, and network defects were handled by manual activation of
simplistic tools such as ping.
Since the introduction of Metro Ethernet Networks and the advent of
“Carrier Class Ethernet” the situation has changed radically. These
networks need to be managed by service providers, and in order to be
truly “carrier class” it is essential for Ethernet MANs to support
automated defect detection and performance measurement. In order to
guarantee SLAs, service layer parameter monitoring is also required.


Issue 01
9.1 Introduction
In order to enable Ethernet service providers to operate and maintain

their networks, there is a need to include OAM on the Ethernet layer.
Two Ethernet OAM protocols have emerged. One has been developed
for “Ethernet in the first mile” (EFM) applications, operating at the
level of the single link, while the other tackles the wider problem of
end-to-end Ethernet connectivity and service guarantees. The link-layer
OAM was developed by the 802.3ah EFM task force in the IEEE 802.3
working group, and thus is often called the “802.3ah” or “EFM” OAM.
Due to their different objectives, Ethernet link-layer OAM and Ethernet
service OAM protocols were not intended to compete with each other,
and can even be complementary. In an access segment based on EFM,
both Ethernet OAM protocols may be running simultaneously, where the
EFM OAM monitors the lower (physical transport) layer, and the service
OAM maintains the higher layer.
Core networks have rich connectivity, with multiple alternative paths
available between any two switches or routers. In contrast, first mile
networks usually have very simple topology, direct point-to-point links

Issue 01
9.1 Introduction
between provider and customer, or point-to-multipoint PONs so that

the provider can broadcast content to many customers. For this reason,
the OAM needed for EFM applications is link-layer OAM.
The capabilities of link-layer OAM are limited, being restricted to
placing the remote device into loopback, setting flags indicating critical
events, and querying the remote device’s configuration. There is no
performance measurement and the information exchanged about the
state of the link being monitored is minimal.
The network model consists of:
Different administrative domains (a.k.a. OAM levels). Each administrative
domain can be independently monitored by its own Ethernet Connectivity
Fault Management (CFM) frames. The scope of OAM frames is limited to the
domain in which the carried information is significant
Two plans: a “vertical plane” (red arrow) that represents the OAM entities
across different administrative domains, and an “horizontal plane” (blue
arrow) that represents the OAM entities within a single administrative
domain.


Issue 01
9.1 Introduction
Ethernet OAM network model


Issue 01
9.1 Introduction
Ethernet OAM entities: vertical plane


Issue 01
9.1 Introduction
Ethernet OAM entities: horizontal plane


Issue 01
9.1 Introduction
Delay Measurement
ETH-DM can be used for on-demand OAM to measure frame delay and
frame delay variation. Frame delay and frame delay variation
measurements are performed by sending periodic frames with ETH-DM
information to the peer MEP and receiving frames with ETH-DM
information from the peer MEP during the diagnostic interval. Each MEP
may perform frame delay and frame delay variation measurement. Only
point-to-point delay measurement shall be supported. Delay
measurement shall be performed between two MEPs of the EVC


Issue 01
9.1 Introduction
Delay Measurement [cont.]
When a MEP is enabled to generate frames with ETH-DM information, it

periodically sends frames with ETH-DM information to its peer MEP in
the same ME. When a MEP is enabled to generate frames with ETH-DM
information, it also expects to receive frames with ETH-DM information
from its peer MEP in the same ME.
A MEP involved in LM measurements, supports the following
parameters:
MEG level
Priority – Identifies the priority of the frames with ETH-DM information. This
information is configurable per operation.
Drop Eligibility – Frames with ETH-DM information are always marked as drop
ineligible. This information is not necessarily configured.
A MIP is transparent to the frames with ETH-DM information and
therefore does not require any information to support ETH-DM
functionality.


Issue 01
9.1 Introduction
DM Tool both for TMPLS and OAM works in the following way:
DMM Frame is sent by “Initiator Node” with “TxTimeStampf” time-stamp.
DMM Frame is received by “Responder Node” and is time-stamped
“RxTimeStampf”
“Responder Node” sends back the DMR Frame with “TxTimeStampb”
“Initiator Node” receives back the DMR Frame and time-stamps it with
“RxTimeStampb”
TxTimeStampf
(1) RxTimeStampf
(2)
(4)
(3)
RxTimeStampb
TxTimeStampb

The following peculiarities apply to DM implementation:

It is possible to launch in parallel for the same Tunnel (or EVC in ETH case) different tools for different
Class Of Services.
It is possible to configure the frame size for the DM tool: in this way it is possible to measure the delay for
the different frame sizes.
It is “on-demand” tool but it is possible to configure toll running for 1000’s of samples and large period
(10min).
Output is provided on Excel format in order to allow further manipulation and calculation.

Issue 01
9.1 Introduction
Populated in initiator Tx
DMM
Populated in the answer (Rx)

DMR
Populated in Initiator Rx

The fields of the DMM PDU format are as follows:

MEG level: a 3 bit field used to choose the meg level from 0 to 7
Version:value is always 0.
OpCode: Value for this PDU type is DMM (47).
Flags: Set to all-ZEROes.
TLV offset: Set to 32.
TxTimeStampf: An 8-octet transmit timestamp field
Reserved: Reserved fields are set to all-ZEROs.
End TLV: An all-ZEROs octet value.
The fields of the DMR PDU format are as follows:

MEG level: A 3-bit field the value of which is copied from the last received DMM PDU.
Version: A 5-bit field the value of which is copied from the last received DMM PDU.
OpCode: Value for this PDU type is DMR (46).
Flags: A 1-octet field the value of which is copied from the last received DMM PDU.
TLV offset: A 1-octet field the value of which is copied from the last received DMM PDU.
TxTimeStampf: An 8-octet field the value of which is copied from last received DMM PDU.
RxTimeStampf: An 8-octet transmit timestamp field.
TxTimeStampb: An 8-octet transmit timestamp field
Reserved: Reserved fields are set to all ZEROs.
End TLV: A 1-octet field the value of which is copied from the DMM PDU.

Issue 01
9.1 Introduction
DM process shall be invoked to calculate the one-way frame delay
counter for each ETH-DM instance as PM primitives which are further
processed in performance monitoring functions
Frame Delay = (RxTimeStampb–TxTimeStampf)–(TxTimeStampb–RxTimeStampf)


Issue 01
9.1 Introduction
Ethernet Synthetic Loss Measurement (LM)
ETH-LM is used to collect counter values applicable for ingress and

egress service frames where the counters maintain a count of
transmitted and received data frames between a pair of MEPs.
ETH-LM is performed by sending frames with ETH-LM information to a
peer MEP and similarly receiving frames with ETH-LM information from
the peer MEP. Each MEP performs frame loss measurements which
contribute to unavailable time. Since a bidirectional service is defined
as unavailable if either of the two directions is declared unavailable,
ETH-LM must facilitate each MEP to perform near-end and far-end
frame loss measurements.
For a MEP, near-end frame loss refers to frame loss associated with
ingress data frames while far-end frame loss refers to frame loss
associated with egress data frames. Both near-end and far-end frame
loss measurements contribute to near-end severely errored seconds
(Near-End SES) and far-end severely errored seconds (Far-End SES)
respectively which together contribute to unavailable time,


Issue 01
9.1 Introduction
Ethernet Loss Measurement (LM)
A MEP maintains the following local counters for each peer MEP:
TxFCl: counter for data OAM CCM frames transmitted towards the peer MEP.
RxFCl: counter for data OAM CCM frames received from the peer MEP
A MEP involved in LM measurements, supports the following
parameters:
MEG Level
transmission period
Priority: identifies the priority of the frames with ETH-LM information. This
information is configurable per operation.
Drop Eligibility – Frames with ETH-LM information are always marked as drop
ineligible. This information is not necessarily configured.
A MIP is transparent to frames with ETH-LM information
TSS-320/160 supports Synthetic measurement. “Synthetic” means
way to measure the packet loss via counting of dedicated packets
(CCM OAM packets): this is different from standard approach where
data traffic packets are counted to calculate packet loss.


Issue 01
9.1 Introduction
OAM in the TSS-320
1850 TSS-320 support OAM for two scopes:
Connectivity fault management: per service/VLAN OAM on a bridge network.

Ethernet continuity check (CCM): MEPs periodically exchange Continuity Check OAM
messages to detect loss of continuity or incorrect network connections. A CCM is
multicast to each MEP in a MA/MEG at each administrative level. A MEP can also
include information on the status (up, down, in loopback, etc.) of its associated port
in CC Messages;
Link trace Message (LTM): MEPs multicast LTMs on a particular MA/MEG to identify
adjacency relationships with remote MEPs and MIPs at the same administrative level.
The message body of a LTM includes the destination MAC address of a target MEP
that terminates the link trace. When a MIP or MEP receives a LTM, it generates a
unicast Linktrace Replay Message (LTR) to the initiating MEP. It also forwards the
LTM to the target MEP destination MAC address. A LTM effectively traces the path to
the target MEP.
Loopback (LBM): MEPs send loopback messages to verify connectivity with another
MEP or MIP for a specific MA/MEG. Loopback is a ping like request / reply function. A
MEP sends a loopback request message to another MEP or MIP, which generates a
subsequent loopback reply message (LRM). LBMs / LRMs are used to verify
bidirectional connectivity. They are typically initiated by operator command.
However a MEP can be provisioned to send LBMs periodically.
Ethernet First Mile: link layer OAM to monitor the link between two ports.

Issue 01
9.1 Introduction
OAM in the TSS-320 [cont.]
Ethernet OAM over VPWS

Ethernet OAM over VPWS provides the following ETH OAM functions:
Connectivity Check Messages (CCM) with periodic refresh of 1 sec.
Loopback Messages (LM)
Link Trace Messages (LTM).
For supporting Ethernet OAM over VPWS a MA is created and associated
via management operations to a PW (identified via PW index). Each
MEP inside the MA is bound to the same PW. Inside MA a MEP is
identified by MA (PW index) and port (UNI).
A TMPLS node supports enabling of Ethernet OAM functions with MEPs
(“UP” MEP) on UNI interfaces (AC port, see next figure). The system
supports both unidir and bidir ETH OAM over VPWS.


Issue 01
9.1 Introduction
VPWS OAM MEPs points location is based upon the management model
used in the VPWS scenario. The final goal is to achieve end-to-end
service and segment monitoring in the network (see next figure).


Issue 01
9.1 Introduction
Ethernet OAM over VPLS
Ethernet OAM over VPLS provides the following ETH OAM functions:
Connectivity Check Messages (CCM) with periodic refresh of 1 sec.
Loopback Messages (LM)
Link Trace Messages (LTM).
For supporting Ethernet OAM over VPLS a MA is created and associated
via management operations to a VPLS Instance (identified via VPN ID).
Each MEP inside MA is bound to the same VPLS Instance. Inside MA a
MEP is identified by MA (VPLS Instance) and port (UNI/NNI).
A VPLS–NE node supports, for each VPLS instance, enabling of Ethernet
OAM functions with MEPs on both UNI and NNI interfaces (see next
slide)
”UP MEP” for UNI VPLS interfaces (AC port)
”DOWN MEP” for NNI VPLS interfaces (PW logical port).
For H-VPLS network “DOWN MEP” refers both on Spoke PW and Core
PW, as shown in next slide.


Issue 01
9.1 Introduction
The system supports both unidir and bidir ETH OAM over VPLS. Ethernet
OAM frames apply at both MEP termination points, within the specific
service layer.


Issue 01
Blank Page


Issue 01
9.2 EFM (Ethernet in the First Mile)


Issue 01
EFM activation
1. Select Data EFM Tool
2. Click on Search
3. select the
Ethernet port
4. Click on “Show”


Issue 01
EFM activation
5. Select Configuration tab
6. Set to “Enabled”
7. Click on Save
TSS-320 TSS320
2 8
C324 C325

Oper Status: (read only field) current operational status of the OAM for this interface. Possible values:
disabled, linkfault, passiveWait, activeSendLocal, sendLocalAndRemote, sendLocalAndRemoteOk,
oamPeeringLocallyRejected, oamPeeringRemotelyRejected, or operational according to the operation
and failure conditions.
Config Revision: (read only field) indicating if configuration changes have occurred which might require
the peer OAM entity to re-evaluate whether the peering is allowed.
Functions Supported: OAM functions supported on this Ethernet like interface. Possible values:
unidirectionalSupport, loopbackSupport, eventSupport, variableSupport.
PDU Size: (read only field) indicating the OAM entities exchange maximum OAMPDU sizes and negotiate
to use the smaller of the two maximum OAMPDU sizes between the peers. This value is determined by
the local implementation
Mode: (read only field)
active mode provides additional capabilities to initiate monitoring activities with the remote OAM peer
entity.
passive mode generally waits for the peer to initiate OAM actions with it.
Information TX Interval: indicating the minimum interval, in terms of 10ms, between two consecutive
Information OAMPDUs. Default value is 100 (1s).
Loopback Command: allows to select the initialization or termination of remote loopback with an OAM
peer. Possible values: noLoopback (no remote loopback),
Loopback Status: (read only field) indicating the loopback status of the OAM entity. Possible values:
noLoopback.

Issue 01
EFM Information (Configuration tab)
TSS-320 can get the remote device execute a loopback.

TSS-320 can not execute a loopback issued by a remote device.
Information Tx: indicating the current count of the number of Information OAMPDUs transmitted on this
interface.
Information Rx: indicating the current count of the number of Information OAMPDUs received on this
interface.
Loopback Control Tx: (not supported in current release) indicating the current count of the number of
Loopback Control OAMPDUs transmitted on this interface.
Loopback Control Rx: (not supported in current release) indicating the current count of the number of
Loopback Control OAMPDUs received on this interface.

Issue 01
EFM Information (Link Monitoring tab)

Unique Event Notification Tx: (not supported in current release) indicating the current count of the
number of unique Event OAMPDUs transmitted on this interface.
Unique Event Notification Rx: (not supported in current release) indicating the current count of the
number of unique Event OAMPDUs received on this interface.
Duplicate Event Notification Tx: (not supported in current release) indicating the current count of the
number of duplicate Event OAMPDUs transmitted on this interface.
Duplicate Event Notification Rx: (not supported in current release) indicating the current count of the
number of duplicate Event OAMPDUs received on this interface.

Issue 01
Blank Page


Issue 01
9.3 Standard OAM Management


Issue 01
Introduction
MD – level Z
Seven levels:
MA – VLAN#X MA – VLAN#Y •0,1,2 for operator Functions supported by
MEP MEP MEP •3,4 for provider TSS-320:
MEP
MEP •5,6,7 for customer
• Loopback (ping)
• Link Trace
MEP of level 7: up
MEP of level 4: down MEP of level 4: down
MEP of level 7: up
MEP of level 1: down
MEP of level 4: down MEP of level 4: up
MEP of level 1: up
1 2 3 4 5 6 7 8 9 10
Bridge A Bridge B Bridge C Bridge D Bridge E
Level 1
Level 4 Level 4
Level 7
MD: Maintenance Domain

MEG: Maintenance Entity Group. It corresponds to MA.
MA: Maintenance Association
MEP: MEG End Point
MIP: MEG Intermediate Point
MEP: it is capable of initiating and terminating OAMPDU frames.

MIP: it is capable to respond to the OAMPDU frames generated by MEP.
“up” and “down” concern the MEP direction:

up: means the OAM messages must traverse the bridge (messages go out from the bridge via other
ports).
down: means OAM messages are directly sent outside the bridge (messages go out from the bridge via
this same port).

Issue 01
Global setting
1. Select Data OAM Management Global setting
2. Configure the Ether Type

and LBM time out (ping)
3. Click on Save


Issue 01
Test bench 1 (loopback)
Example:
• All the ports are ETB (Provider bridge)
• Consider one level: level 7
• Configure MEPs and MIPs
MEP of level 7 MEP of level 7

(Direction=Down) MIP of level 7 (Direction=Down)
C324 c325
MEP ID=10
1 2 8 1
Bridge A MEP ID=11 Bridge B
Level 7


Issue 01
Procedure for Bridge A

configure the card as Virtual bridge or
1 Virtual bridge; RSTP
Provider bridge
2 configure the ports ETB; Admin Status=Up
3 Register the ports on the VLAN VLAN=15
4 Create the Maintenance Domain Name=‘whatever’; level=7

Name=‘whatever’; VLAN=15;
5 Create the Maintenance Association
MIP=“none”
Identifier=‘10’; port#2;
6 Create the MEP
direction=down


Issue 01
Step 4: create the Maintenance Domain
1. Select Data OAM Management OAM Resource Config. MD
2. Do Create


Issue 01
Step 4: create the Maintenance Domain [cont.]
3. Assign a Name 5. Set to up
4. Set Level = 7
6. Click on Save
8. Tick the box and then click on Activate

Format: to define the format for the name of this MD. Possible values:
charString
dnsLikeName
All Bridges belonging to the same MD must have the same format.
The level associated to the OAMPDU is the level that can allow to pass in other MD up to same level ( i.e.
the OAMPDU with level 4 can pass through MD with level 0,1,2,3,4 )

Issue 01
Step 5: create Maintenance Association
1. Select Data OAM Management OAM Resource Config. MA
Click on Search/Refresh to seek existing MA
2. Click on Create

Issue 01
Step 5: create Maintenance Association [cont.]
3. Choose the MD: click on Select
5. Choose the MD Label


Issue 01
6. Assign the Name 7. Leave “…none” because we
need no MIP on bridge A
9. click on Select
11. Click on Save
8. set “vid”
10. Select VLAN = 15

CCM Interval: is the period to send continuity check messages on the line
Type: specifies the application of the MA
Format: to define the format of this MA. Possible values: charString

All Bridges belonging to the same MA must have the same format.
MA Name: to type a name chosen by the user.
MHF Creation: to define the MHF (MIP Half Function) of this MA. Possible values:
defMHFnone: no MIP can be created for this MA.
defMHFdefault: MIPs can be created for this MA on any bridge port (intermediated node)

Issue 01
11. Click on Search


Issue 01
13. Click on details to see the MEP identifier list
14. Assign the remote MEP

identifier (11)
15. Click on Create


Issue 01
Step 6: create the MEP
1. Select Data OAM Management OAM Resource Config. MEP
2. Click on Create Click on Search to seek existing MEP


Issue 01
Step 6: create the MEP
3. click on Select to choose the MA
4. Assign the identifier (integer number)

6. select the direction: down
5. Click on Select to Choose the

interface the MEP is to be created on
9. Click on Save
8. Insert the LTM
priority and the
LBM VLAN priority

Identifier: integer value set by the user, different from 0.
Cci Enabled (not operative): true/false.
Ltm Priority: to associate a VLAN priority (0 to 7) to the Link Trace Message; default is 7.
Status: actual state of this MEP (up/down); i.e. in-service/out-of-service.
Direction: to indicate the direction of OAM messages for this MEP.

“up” means the OAM messages must traverse the bridge (messages go out from the bridge via other
ports).
“down” means OAM messages are directly sent outside the bridge (messages go out from the bridge via
this same port).
Active: (true/false) to activate/deactivate this MEP.

Issue 01
Step 6: create the MEP [cont.]
Created MEP


Issue 01
MEP MAC address
To know the MEP MAC address … 1. Click on Search/Refresh
2. Select the MEP
MEP MAC address

The MAC address of the MEP with direction=down is equal to the MAC address of the Bridge’s port the
MEP belongs to.
The MAC address of the MEP with direction=up is equal to the Bridge’s MAC address.

Issue 01
Ping port#8 (Bridge B) from port#2 (Bridge A)
First of all, configure Bridge B
as you did for Bridge A
1. Open the MEP window
for port#2
3. Click on LoopBack
2. Select the MEP
4. select dest. MEP-ID


Issue 01
Ping port#8 (Bridge B) from port#2 (Bridge A) [cont.]
5. Insert the target MEP ID (11)
7. Result: “Operation completed successfully”
6. Click on Start Test


Issue 01
Test bench 2 (Link Trace)
Example:
• All the ports are ETB (Provider bridge)
• Consider one level: level 7
• Configure MEPs and MIPs

(Direction=down) MIP of level 7 (Direction=down)
C324 C326
C325
2 8 1 1
Bridge A Bridge B Bridge C
Level 7


Issue 01
Enable level 7 MIPs on bridge B
1. Create a level 7 MD
2. Click on Save
3. Create a MA for the level 7 MD


ES1 ES4
ES4
10 20 21 22
Level 7

Issue 01
Enable level 7 MIPs on bridge B [cont.]
4. Click on Save
Mhf Creation:
• None: no MIP is created.
• Default: each bridge port behaves as MIP, too. Any MEP creation on the
port is not necessary.
• Explicit: a bridge port behaves as MIP only if it is configured as MEP for a
lower level (i.e. Port#8 is a MIP for level 7 only if port#8 is configured as MEP
for a level from 0 to 6).

Mhf: MIP Half Function

ES1 ES4
ES4
10 20 21 22
Level 7

Issue 01
Link Trace test
1. Open the MEP window for port#2 (bridge A)
3. Click on LinkTrace
2. Select the MEP
4. Enter the MAC address of the MEP on port#1

(bridge c): (00:20:60:7B:5A:F0)
First of all, issue the loopbacks

from both the MEPs (port#2
5. Click on Start Test and port#1 (bridge c))

Transmit Ltm TTL: max number of bridge nodes this message can traverse before expiring.

Issue 01
Link Trace test [cont.]
Port#2: 00:20:60:6B:CC:6C Port#1: 00:20:60:6E:89:D6 Port#1: 00:20:60:7B:5A:F0
2 8 1 1
Level 7
Port#8: 00:20:60:6E:89:DD Bridge B: 00:20:60:50:C3:00 Bridge C: 00:20:60:46:32:80
6. Do Get Test results
1 2
4 3
B A C B 1(C) 8 1(B)

Issue 01
Blank Page


Issue 01
9.4 DM configuration


Issue 01
9.4 Delay Measurement
Proactive tool: test bench
Test bench is composed by 3 nodes (A,B,C) with

TMPLS Tunnel end-to-end (node A-C)
Eth Service over PW end-to-end (node A-C)
C-UNI: C-UNI:
MD: MD1 MD: MD1
MA: MA1 MA: MA1
LEVEL: 4 LEVEL: 4
MEP: 10 MEP: 11
Tunnel
18/8
16/1
19/1 19/1 7/1 19/1
Node A Node B Node C
C321 C322
TMPLS DM
C323
ETH-DM


Issue 01
Proactive tool: Configuration
1. Select: Data OAM management Proactive

Tool Synthetic Loss Measur Tool
The DM tool can be configured only in the ETS

port of the provider bridge.
The MEP must be set with direction = “up” and
the provider bridge CXC must be created
2. Click on Create


Issue 01
Proactive tool: Configuration [cont.]
3. Click on Select
4. Choose the filter
6. Select the MEP


Issue 01
7. Choose the priority
It is possible to start at the same

time up to 8 tools for each Tunnel
indicating the PHB (Class Of Service)


Issue 01
8. Choose the MEP ID

The interval represents the distance
between two consecutive TMPLS
DMM messages
9. It is possible to specify the “Frame

Length” for the TMPLS DM packet
between 64 to 1500 bytes and
with the option “Random” (in this
case DMM packets are generated
with polynomial generator).
10. Choose the Interval
11. Click on Save to activate the measurements


Issue 01
Proactive tool: Management
To delete a measurement, tick the box and click on

Delete. The measurement will be removed from the list
Click here to modify the SLM

PM threshold profiles.
2. Click on view statistic to view the results

It’s possible to “Select” more instances at the same time.

Issue 01
Proactive tool: proactive DM PM threshold profiles

PM threshold profiles or to
create a new one Click here to modify the interval
Click on Create to create a

new threshold profiles
Click on Search to see the

actual threshold profiles


Issue 01
Proactive tool: proactive DM PM threshold profiles [cont.]
To create a new DM PM profile 3. Configure the values
1. Click on Create
2. Select the counter type
4. Click on Save & Activate


Issue 01
Proactive tool: proactive DM PM threshold profiles [cont.]
Click on profiles to see the details or

to modify the threshold profiles


Issue 01
Proactive tool: Test Results
1. Click on view statistics
2. Select the 2-Way Current Data tab or 1-Way Current Data tab
Click on Delete PM to delete the PM counter
3. Choose the Granularity Period
4. Click on Create PM


Issue 01
Proactive tool: Test Results [cont.]
Click on next to see the other results
Measurement available after PM creation
Click on Reset to reset the PM counters
Click on Refresh to update the results
The polling panel displays the PM

measurement for the elapsed polling periods
5. Click on Start Click on next to see the other results

The system supports the following PM counters associated to Delay and Delay Variation Measurement:
aB_FDCnt Average Round Trip Frame Delay
mB_FDCnt Minimum Round Trip Frame Delay
xB_FDCnt Maximum Round Trip Frame Delay
aN_FDVCnt Average Near End Frame Delay Variation
mN_FDVCnt Minimum Near End Frame Delay Variation
xN_FDVCnt Maximum Near End Frame Delay Variation
aF_FDVCnt Average Far End Frame Delay Variation
mF_FDVCnt Minimum Far End Frame Delay Variation
xF_FDVCnt Maximum Far End Frame Delay Variation

Issue 01
Proactive tool: Test Results [cont.]
Every elapsed CD period is accumulated in 15m or 24h History Data tab


Issue 01
On Demand tool: Configuration
1. Select: Data OAM management On-

Demand Tool Delay Measurement
2. Click on Create


Issue 01
3. Click on Select
6. Select the MEP


Issue 01
8. Choose the MEP ID
9. Choose the Duration

It is possible to indicate the Start and
End Time OR in alternative the
number of samples for the TMPLS
DM measurement.


Issue 01
The interval represents the distance

between two consecutive TMPLS
DMM messages
11. It is possible to specify the “Frame

between 64 to 1500 bytes and with
the option “Random” (in this case
DMM packets are generated with
polynomial generator).
12. Click on Save to activate the measurements


Issue 01
On Demand tool: management
13. tick the box and click on Activate to activate the measurements
14. Right Click on the view statistic icon and select

Open Link in New Window to view the results, or
select Save Link As to save the results
15. Click on OK

Issue 01
On Demand tool: Test Results
Summary of test
input parameters
Round Trip Delay

Number of Successful DM
Number of unsuccessful DM
Elapsed time from test starting
These are the four fields

reported in the TMPLS DMR tool


Issue 01
On Demand tool: Test Results
TxTimeStampf
RxTimeStampf Round Trip Frame Delay =

(RxTimeStampb–TxTimeStampf)–
Round Trip Frame
Delay (TxTimeStampb–RxTimeStampf)
TxTimeStampb
RxTimeStampb
Clock Local end Clock Remote end


Issue 01
9.5 Synthetic Loss Measurement tool


Issue 01
Proactive tool: test bench
Test bench is composed by 3 nodes (A,B,C) with

TMPLS Tunnel end-to-end (node A-C)
Eth Service over PW end-to-end (node A-C)
C-UNI: C-UNI:
MD: MD1 MD: MD1
MA: MA1 MA: MA1
LEVEL: 4 LEVEL: 4
MEP: 10 MEP: 11
Tunnel
18/8
16/1
19/1 19/1 7/1 19/1
Node A Node B Node C
C321 C322
TMPLS DM
C323
ETH-DM


Issue 01
Proactive tool: Configuration
1. Select: Data OAM management Proactive

Tool Synthetic Loss Measur Tool
The SLM tool can be configured only in the ETS

port of the provider bridge.
The MEP must be set with direction = “up” and
the provider bridge CXC must be created
2. Click on Create


Issue 01
3. Click on Select
6. Select the MEP


Issue 01
8.
9. Insert the MP ID
10. Insert the destination

MAC address
12. Insert the Slm identifier

13. Click on Save
to activate the
measurements


Issue 01
Proactive tool: Management
With “Activate” and “deactivate”
button is possible to start (Stop)
the measurement of the tool.
To delete a measurement, Click here to modify the SLM

tick the box and click on PM threshold profiles.
Delete. The measurement
will be removed from the list
1. Right Click on the view statistic icon and select

Open Link in New Window to view the results, or
select Save Link As to save the results


Issue 01
Proactive tool: proactive SLM PM threshold profiles
Click here to modify the interval

PM threshold profiles or to Click on Create to create a
create a new one new threshold profiles
Click on Search to see the

actual threshold profiles


Issue 01
Proactive tool: proactive SLM PM threshold profiles [cont.]
Click on profiles to see the details or

to modify the threshold profiles


Issue 01
Proactive tool: proactive SLM PM threshold profiles [cont.]
To create a new SLM PM profile
2. Select the counter type
1. Click on Create
3. Configure the values
4. Click on Save & Activate


Issue 01
Proactive tool: Test Results (ETH-LM statistics)
1. Click on ETH-LM statistics
2. Select the Current Data tab
3. Choose the Granularity Period


Issue 01
Proactive tool: Test Results (ETH-LM statistics) [cont.]

5. Click on Start

Where:
anFLR Average Near End Frame Lost Ratio
afFLR Average Far End Frame Lost Ratio

Issue 01
Proactive tool: Test Results (ETH-LM statistics) [cont.]


Issue 01
Proactive tool: Test Results (UNI / BIDIR statistics)
1. Click on UNI/BIDIR PM statistics
2. Select the 1-Way Current Data tab

or 2-WAY Current Data tab
3. Choose the Granularity Period. For

2-Way, 24h period only

Issue 01
Proactive tool: Test Results (UNI / BIDIR statistics) [cont.]

5. Click on Start


Issue 01
Proactive tool: Test Results (UNI / BIDIR statistics) [cont.]


Issue 01
Blank Page


Issue 01
10 In Fiber In Band


Issue 01
10 In Fiber In band
In Band Management
The “In Band Management” is used to supervise a remote NE by using data
card.The byte exchanged for the supervision are embedded in the Ethernet
frames.
To identify the supervision packets we’ll provide a label as a tunnel or a Vlan

value. You can have the In band management between two port MPLS (NNI) or
between two port Eth. (UNI).
You can also use the In band management to supervise a different NE i.e. TSS3.
Host ID remote node:
10.10.10.10
Control Channel mapped

with data

CC-TP : Control Channel terminating Point

Issue 01
10 In Fiber In band
Procedure on one node
Step Action
1 Configure the IP address of the NE
2 Configure the LAN management (mandatory only on Gateway)
3 Configure the In Band management on the GEth port
4 Activate
It is supposed that the trainee can perform the

steps 1, 2. (please refer S3-M2 module)

N.B: the IP address of the NE is the address to be used for logon to the remote NE

Issue 01
10 In Fiber In band
Step 3: configure the In Band management on MPLS port
3. Set a label 2. Set a label

1. Select the port
5. Choose “isis” to 4. Set “PPPoE”

6. Click on “Save” to submit enable the
routing protocol

Label: pay attention to set the same label on both end point of the attached Nes
LL mode: specifies the Lower Layer mode for the management plane: choose PPoE in case of MPLS layer

Issue 01
10 In Fiber In band
Step 3: configure the In Band management on Eth port
1. Set a VLAN value
2. Set “ETH”
3. Choose “isis” to
enable the routing
protocol
4. Click on Save
6. Click on Save
5. Insert IP address and

netmask of the remote NE

Label: pay attention to set the same label on both end point of the attached Nes
LL mode: specifies the Lower Layer mode for the management plane: choose ETH in case of Ethernet link

Issue 01
10 In Fiber In band
Step 4: activation
5. Activate

The Status is updated in “Active”

Issue 01
11 Group Segregation Mng


Issue 01
Introduction
This option is to set the segregation state, in order to exclude the Port
from the exchanging of frames with a given list of ports. Only ETB ports
in case of MAC/Virtual Bridge, ETB and ETS ports for Provider Bridge
case.
In case of Virtual or Provider Bridge, the ports to be segregated can
also registered over the same VLAN. In this way a segregated port can
exchange frames only with a non-segregated port.
Segregation is applicable also for Link Aggregation Groups.
An application example is reported in figure below.
p1, p2, p3, p4 are segregated ports.

p5 is a non segregated port.
ports p1, p2, p3, p4 can exchange frames with p5, but not among them

This function is used to save the band and resources on the node and on the ports, and also to improve the
security and the privacy of the transmission.
he System shall support port segregation feature, i.e. the capability to prevent that packet , coming from a
port belonging to a segregation group is forwarded to another port within the same group. Port
segregation is used for security reasons and is applicable both in T-MPLS and bridge node configuration.
The maximum number of segregation groups is requested to be 15.

Issue 01
Group Segregation enabling
1. Select: Data Group Segregation Mng
2. Click on Create to
create a new group
3. Click on Yes


Issue 01
Port registering
4. Select Bind port to add a
port to the group
5. Choose the board
6. Select the board in the left side and then click

on >> to move the port to the other side
The Port Segregation Group parameters displays the selected segregation group service. Select the board
for which the binding is required from the Board Selection drop-down list box.
If the port is configured on the selected board, it displays in the left entry box. To set the port binding,
click >> button to send the available port entry into the right entry box. Use >> button to sent the port
entry back to the left entry box.

Issue 01
Port registering [cont.]
The segregated port is put in the group
Click on Show Ports to see the

associated ports with the group


Issue 01
Blank Page


Issue 01
12 Link Pass-Through


Issue 01
Introduction
LPT is a mechanism that propagates failures detected on (see figure in

the next page):
CIF, e.g. Customer Interface
NIF, e.g. Network Interface.
LPT ensures that a network (e.g. multi-domain PTN) inserted between
two CEs will behave externally as if the CE were directly connected on
a Link. It is used when client native service OAM does not provide
mechanisms to propagate failure conditions (e.g. CE does NOT support
IEEE 802.1ag).
LPT is available only for the following point-to-point port-based
services (over ETH, SDH and T-MPLS):
Port-to-Port
EPL service
EVPL service (point-to-point)
EVC mux (Hub & Spoke); in case of Hub & Spoke, LPT supports the LLCF (Link
Loss Carry Forward) mechanism,


Issue 01
LPT frames are inserted, both at CIF and NIF level, on the same
interface type, that is: FE interface, GE interface, 10 GE interface, LAG
Interface and GFP Interface (“remote port”).


Issue 01
LPT frames may be of the following type, in accordance with the type
of indication reporting the failure (per port, per service):
GFP-CSF (per port, only on "GFP remote port").
ETH-CSF (per service)
ETH-AIS / ETH-RDI (per service)


Issue 01
LLCF (Link Loss Carry Forward)
It is a mechanism that Propagates failures detected:

On the Hub NIF to the far-end NIF on leaf(s)
Within the Network to both NIF, such that CE (at Hub or Leaf) can take
proper action.
It ensures that a network inserted between a Hub and various Leaf CEs
will behave externally as if the CEs were directly connected on a Link
(EVC).
Available only for EVC Mux based services over SDH, ETH and T-MPLS…
The system supports LPT on Hub & Spoke topology (EVC mux, point-to-
point service), applying LLCF mechanism, in case of either:
Upstream direction (Spoke Hub): Ethernet PHY Interface failure at Spoke
CIF (even if forced from Management operator for Maintenance) or failure
detected in the transport network
Down stream direction (Hub Spoke) Ethernet PHY Interface failure at Hub
CIF (even if forced from Management operator for Maintenance).


Issue 01
LLCF (Link Loss Carry Forward) [cont.]
LPT applies the LLCF principle to propagate failures:
Via GFP CSF Point-to-MultiPoint
Via ETH-CSF or ETH-AIS/RDI.
LPT (LLCF) frames are inserted, both at CIF and NIF level, on the same
interface type, that is: FE interface, GE interface, 10 GE interface, LAG
Interface and GFP Interface (“remote port”).


Issue 01
LLCF (Link Loss Carry Forward) [cont.]


Issue 01
Configuration steps
Step Action
1 Create a MEP
2 LPT creation
3 LPT configuration
It is supposed that the trainee can perform the

steps 1. (please refer Chapter 9.3)


Issue 01
Step 2: LPT creation
2. Choose Service basis
1. Select: Data Link Pass-Trough
3. Click on Select
4. Click on Search / Refresh


Issue 01
Step 2: LPT creation [cont.]
5. Select the MEP


Issue 01
Step 3: LPT configuration
7. Configure the CSF
consequent action
10. Click on Save 8. Configure the SSF

9. Configure the LPT consequent action
Send Control
The insertion of LPT frames shall be provided according to below selective Transmit mode capabilities
(provisionable from Management Operator):
Disable (transmit) capability;
Bidirectional CSF (transmit) capability. This enables both LPT consequent actions in case of failure
detected at CIF and remote LPT insertion in case of failures detected at NIF.
Unidirectional CSF (transmit) capability. This enables exclusively LPT consequent actions in case of failure
detected at CIF.

Issue 01
Step 3: LPT configuration [cont.]
The Insertion Control parameters

appear in the window


Issue 01
13 ETH AIS management


Issue 01
Introduction
The system shall be able to generate and detect ETH-AIS on each active
MEP in the following network configuration:
EPL (Ethernet Private Line)
EVPL (Ethernet Virtual Private Line)
E-LAN
The system shall be able to generate and detect ETH-AIS on each active
MEP in Provider Bridge (802.1ad), Provider Backbone Bridge (802.1ah)
and TMPLS contexts (where applicable)
In case of service MEP, ETH-AIS is inserted inside the same MA/MD of
the MEP (so with the VID of the corresponding MEP).
In case of Down MEP at port level, ETH-AIS is inserted for all VID
registered on that port.
In case of multiple MEP level configured in the same node for the same
service, ETH-AIS should be injected only by the “upper level MEP”,
while the other MEP should be triggered to provide the SSF alarm.


Issue 01
The system shall be configured to not generate AIS in scenarios where

Spanning Tree Protocol is enabled.
The system shall be able to propagate AIS to client level in front of
fault detected by MEP. MEP failures can be either detected at the MEP
layer via ETH-OAM tools (e.g. CCM) or detected as Server Signal Fail
condition (e.g. due to failure at physical layer)
Upon reception of an ETH-AIS frame, NE shall check whether there are
one or more MEPs to meet the following conditions:
MD level of the MEP is equal to or higher than the MD level in the received
ETH-AIS frame (if higher the frame is discarded)
VLAN of the MEP is equal to the VID in the received ETH-AIS frame, including
no-VID.
If no qualifying MEPs are found, the ETH-AIS frame shall be forwarded.


Issue 01
ETH-AIS reception/detection capability on MEP shall automatically be

disabled if the spanning tree (STP, RSTP or MSTP) is enabled on the
interface where the MEP resides. The MEP shall respond to received AIS
frames, if no spanning tree is enabled on the interface where the server
MEP resides


Issue 01
Configuration
1. Select: Data OAM management Alarm Indication Signal
2. Click on Create


Issue 01
Configuration [cont.]
3. Click on Select
6. Select the MEP


Issue 01
10. Choose the Priority
9. Set True
8. Choose the Maintenance

Customer VLAN
12. Click on Create
11. Choose the MEG Level (MEL). The client MEL values must be
bigger (or equal) than MD level of the MEP specified


Issue 01
Check the configuration
1. Set the filter = show all
The configuration appears in the window


Issue 01
14 Ethernet Loopback


Issue 01
Introduction
The PP10GEx2 and PP1GEx20 support both “Ethernet line loopback” and
“Ethernet Internal Loopback” at MAC level, in Loop & Continue
operating mode. This facilities can be applied in “point-to-point”
Ethernet application, for testing purposes.
Ethernet line loopback is performed at client side (UNI), looping the
Ethernet signal received from Customer Edge (CE) at “ingress” UNI,
back to the relevant transmission side. When active, the “line
loopback” implies the discarding of packets received, from NNI.
Consequent action is the transmission of CSF packets (GFP mapped) in
the forwarding direction of the server transport (NNI side).
Ethernet Internal loopback is performed at “egress” UNI, looping the
Ethernet signal received from the transport layer back to the relevant
transmission side on the transport layer. When active, the “internal
loopback” implies the discarding of packets received from UNI.
Consequent action is the notification of Ethernet internal loopback to
remote CE, performed at egress UNI (Transmitter shutdown).
PP10GE, PP10GESY, PP1GE and PP1GESY does not support any
Loopback.

Issue 01
Ethernet loopbacks
Ethernet internal loopback: transmitter shutdown as consequent action


Issue 01
Configuration
2. Select the PHYSICAL tab
1. Select the Ethernet port

3. Set up
4. Click on Create line loopback or Create

Internal loopback to activate the loopback
The selected card must be a
PP1GEx20 or PP10GEx2


Issue 01
15 Sync. and Transparent Clock Delay


Issue 01
Introduction
The TSS-320/160 supports the capability to provide Fiber Asymmetry

configuration for IEEE 1588v.2 Transparent Clocks (TC), in order to
compensate different delay contribution in case of asymmetric fiber
length. The system supports “end-to-end” TC role only.
Fiber Asymmetry configuration allows provisioning of a specific Delay
Asymmetry attribute, for Rx and Tx direction, into the correction field
of 1588v.2 synchronization packets entering a transit network.
If no asymmetry is considered, correction field for TC application is
referenced to the calculated mean delay contribution of the transit
network in both direction ,i.e. results from the mean of Rx and Tx path
contributes.
Hence, considering asymmetric path compensation, the single delay
contribute for each clock path direction is obtained in the following
way:
For the ingress path (t ms direction), Delay Asymmetry attribute is added to
the correction field value of received “Sync” message packet from 1588v.2
master clock

Issue 01
For the egress path ( t sm direction), DelayAsymmetry attribute is subtracted

from the correction field value of received “Delay_Req” message packet
from 1588v.2 slave clock

Fiber Asymmetry compensation does not remove offset observed by slave clock due to intervening
protection with different path replacement.
The TSS-320/160 supports the Fiber Asymmetry configuration per span length ,with zero as default value for
Delay Asymmetry attribute.
The suggested values for accuracy and Delay Asymmetry are:
Delay Asymmetry range of +/- 8 µs
Delay Asymmetry accuracy = 1 ns

Issue 01
Input Fiber
Port #N
Input Fiber is longer than Output
Fiber. This difference is L delayAsymmetry Register
associated to Port #N
Output Fiber
In delayAsymmetry Register associated to Port #N the positive value

corresponding to propagation time of light in that fiber calculated for L/2
length has to be written
Input Fiber
Port #N
Output Fiber is longer than
Input Fiber. This difference is L delayAsymmetry Register
associated to Port #N
Output Fiber
In delayAsymmetry Register associated to Port #N the negative value

corresponding to propagation time of light in that fiber calculated for L/2
length has to be written

Issue 01
Configuration
1. Select an Ethernet port
2. Choose the Sync/Clk Delay
3. Configure the Delay value
4. Click on Save


Issue 01
Blank Page


Issue 01
16 CSF configuration


Issue 01
CSF configuration
2. In the VCG Range panel, select the VCG index (in other
word you must choose the number of the already
enabled VCG port) and then click on Search/Refresh
3. Select a already enabled VCG

port and click on Modify


Issue 01
CSF configuration [cont.]
4. Select the GFP panel of the PHYSICAL tab
5. Configure the CSF support
6. Click on Save
These settings allows to enable the CSF insertion. The

Backward types are not supported.

Issue 01
CSF
CSF (Client Signal Fail) alarm is inserted by the remote ports in two
cases:
Failure on local port: CSF is inserted, towards the SDH network, into the GFP
frame, in case of LOS detection on the local Ethernet port.
CSF CSF
LOS detection
NE A insertion NE B
VCG1
Eth VCG1 Eth
SDH
SDH
X X
1
2
Failure on remote port: CSF is inserted, towards the SDH network, into the
GFP frame, in case of one or more of the following alarms: LOF, TSF, PLM.
CSF CSF
NE A insertion detection NE B
VCG1
VCG1
Eth Eth
SDH
SDH
X X
1
2
TSF

Issue 01
CSF [cont.]
CSF enabling is meaningful only for Port-To-Port and ETS Switch

services.
CSF insertion must be enabled. CSF detection is always enable.
Unidir types: only the failures on the local port are the triggering
criteria for the CSF insertion.
Bidir types: either the failures on the local port or the failures on the
remote port are the triggering criteria for the CSF insertion.
CSF is encoded in the GFP frame’s header with the values:

0000 0010, in case of UPI (User Payload Identifier)-LOF selection
0000 0001, otherwise

The “Backward” types are not supported.

Issue 01
CSF + Shutdown
1. Select a local port and then choose MAU

panel on the PHYSICAL tab
2. Choose transmitterShutdown option
3. Click on Save

RemoteClientFail cons. actions:

disabled
transmitterShutdown: If shutdown is selected, then the Tx i/f (towards the Ethernet line) of this Local
Port will be set in shut Down state, in case of Internal LoopBack on this port, or in case of CSF alarm
detection on the remote port connected to this port.

Issue 01
CSF + Shutdown [cont.]
Possible simulation:
• on port VCG1 enable CSF insertion
AND
• on port #1 set Conf. Remote Client=Shutdown
Interface
CSF CSF shutdown
NE A insertion detection NE B
VCG2
VCG1
Eth Eth
SDH
SDH
X X
2
1
Link down
Port#2 shutdown is triggered by CSF

alarm on port #VCG2. Thus the link
between port #2 and the attached
Ethernet device is down.

Issue 01
Blank Page


Issue 01
17 MAC File Collection


Issue 01
Introduction
This command starts the preparation of the MAC File Collection. The
mechanism of MAC File Collection is an efficient way of collecting MAC
addresses of the entire NE in a single file.
After the start, the status of the collection will become INPREP (in
preparation).
A previously prepared file collection will be no longer available.


Issue 01
Configuration
1. Select Data FDB Operations MAC File Collection
See next page


Issue 01
2. choose the parameters
3. Click on Start Collection


Issue 01
Results
5. Wait the READY status and then click on the file
6. Click on Open with
7. Click on Ok
8. Click twice the file


Issue 01
Results
The results appear in the window


Issue 01
18 MAC Access Control List


Issue 01
Introduction
In Provider Bridge configuration, the system supports MAC Access

Control List management at ingress UNI ports, ”on per port basis”, to
allow the selective 'forwarding‘ / 'dropping‘ of all the frames except
those ones matching the values stored in the MAC ACL list.
A single MAC ACL list is supported for each port, so that MAC ACL List is
configured on port basis.
An ACL is an ordered list of “permit” and “deny” statements that
determine whether a particular packet will be forwarded or dropped.
The order of entries (rules) in a ACL is important because the controller
stops testing conditions in the statement after the first match. The
frames that don’t match any rule are discarded.


Issue 01
Configuration
1. Select Data MAC Access Control List
2. Click on Create
3. Write the ACL Name
4. Click on Send
The new ACL appears in the window


Issue 01
5. Select the ACL 6. Click on editACE
7. Click on Create
8. Choose the execution order
9. Click on Send


Issue 01
10. Fill in the fields
11. Click on Save or Save&exit


Issue 01
13. Choose the PHYSICAL tab
12. Select the ETS port

where you want to
assign the ACL profile
14. Click on Select
16. Click on Associate
15. Choose the ACL profile


Issue 01
Disable ACL

where you want to
disable the ACL profile
3. Click on De-ssociate


Issue 01
End of Module
Operator Interface-Ethernet Bridge features


Issue 01
34
Section 3
NE Operation
Module 4
Operator Interface-T-MPLS & MPLS-TP features
Issue 01
1850 TSS-320 & 1850 TSS-160

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

Issue 01
Blank Page

NE Operation Operator Interface-T-MPLS & MPLS-TP features
Document History
01 2011-12-15 Grecchi, Ilario First Edition

Issue 01
Module Objectives
• Create a T-MPLS Ethernet Virtual Private Line service

• Create a T-MPLS Virtual Private LAN Service
• Manage the Quality of Service in for the T-MPLS network
• Configure a T-MPLS tunnel 1:1 protection
• Configure T-MPLS / MPLS TP OAM
• Configure MAC Flushing propagation


Issue 01


Issue 01
Table of Contents
Page
1 T-MPLS / MPLS-TP overview 7
2 Global Network 15
3 Configure Head/Tail Node 17
4 L2 Encapsulation profile 79
5 Virtual Transport management 83
6 T-MPLS Quality of Service 91
7 PW/ELAN – VT Association 101
8 Configure Transit node 105
9 VPLS (Virtual Private LAN Service) 117
10 T-MPLS OAM 143
10.1 T-MPLS / MPLS-TP OAM theory 144
10.2 DM configuration 183
10.3 SLM configuration 197
11 T-MPLS Protection (FFP) 205
12 Single Node Interconnection for ring closure with TSS-40 223
13 MAC Flushing propagation 231
14 MAC File Collection 251
15 MAC Access Control List 257


Issue 01


Issue 01
1 T-MPLS / MPLS-TP overview


Issue 01
T-MPLS Introduction
T-MPLS is a network layer technology that uses a subset of the existing MPLS
standards and is designed specifically for application in packet transport
networks.
It is a Connection-oriented packet switched technology, well suited to support

Ethernet Services.
T-MPLS creates an application profile for the use of MPLS frame format (MPLS
header), MPLS forwarding paradigm (e.g. label swapping and stacking) and the
client to MPLS mapping in transport network (PseudoWire)
MPLS
PW Tunnel
CE
CE
PE
P PE
UNI CE
UNI
TMPLS Network domain


Issue 01
T-MPLS Introduction [cont.]
At the ingress node, the packets are classified and marked with a code
point that corresponds to their behavior aggregate (based on the
service configuration policy).
At each transit node, the code point is used to identify the per hop
behavior that determines the appropriate scheduling and buffer
management treatment and, in some cases, the drop probability for
each packet.


Issue 01
T-MPLS / MPLS-TP migration
The migration from T-MPLS to MPLS-TP can be done without

interruption of the data traffic and without spurious alarms, using the
T-MPLS / MPLS-TP OAM configurability at node and MEP levels.
Setting the parameter (at node level) that allows to receive both T-
MPLS and MPLS-TP OAM packets it is possible to change the OAM packet
generation from T-MPLS to MPLS-TP (node or Tunnel granularity)
without detecting alarms at receiving side.


Issue 01
T-MPLS / MPLS-TP migration [cont.]


Issue 01
T-MPLS / MPLS-TP overview
Label handling (pop, push, swap) in T-MPLS forwarding
In the T-MPLS edge node, client This T-MPLS

layer traffic flows are intermediate node This T-MPLS
encapsulated/decapsulated performs T-MPLS XC at intermediate node
into/from PWs, which are PW layer, after performs T-MPLS XC at
multiplexed /demultiplexed terminating the Tunnel Tunnel layer
into/from Tunnels layer
NE1 NE2 NE3 T- MPLS NE4 NE5

ETH ETH
UNI NNI NNI NNI NNI NNI NNI NNI NNI UNI
Tunnel1 Tunnel1 Tunnel2 Tunnel2
PW1 PW1 PW1 PW1 VLAN
VLAN VLAN VLAN VLAN VLAN
label SWAP for label SWAP for label SWAP for

2 MPLS label PUSH PW
from NE1 to NE2 Tunnel#1 Tunnel#2
2 MPLS label POP Editorial note:

from NE2 to NE1 - the change of the label number in adjacent hops (e.g. Tunnel1,
Tunnel2) means that they are different LSPs (e.g. different Tunnels)
- the change of the label color in adjacent hops, with the same the label
number, means that it is the same LSP with swapped label value


Issue 01
Head/Tail node: bandwidth constraints
Physical port vs T-MPLS Tunnels:

Σ CIRTunnel_ ≤ Bandwidth Phys port
MPLS Tunnel vs Pseudowires:

Σ CIRPW_ ≤ CIRTunnel
Pseudowire vs Service TD:

PIRService ≤ PIRPW Head Tunnel
Σ CIRService ≤ CIRPW Pseudowire
IN OUT
FLOW FLOW


Issue 01
Transit node: bandwidth constraints
Physical port vs Transit Tunnels/Pseudowire:

Σ CIRTunnel_ ≤ Bandwidth Phys port
Σ CIRPW_ ≤ Bandwidth Phys port
MPLS Tunnel vs Transit Pseudowires:

PIRPW_ ≤ PIRTunnel Transit
Tunnel
Σ CIRPW_ ≤ CIRTunnel
Transit PW


Issue 01
2 Global Network


Issue 01
2 Global Network
Global Network menu
The Global Network option allows to manage all the global
network parameters assigned to the T-MPLS/MPLS-TP.
1. Select MPLS-TP/T-MPLS MPLS-TP/T-MPLS Global Network
OAM CV Period: specifies the default values for

CV/CCM period into OAM CV/CCM frames
PHB range: see “T-MPLS Quality

of Service” module for details
OAM Type: specifies the OAM
This parameters are type for the new created MEPs
valid only for the
Click on Save new T-MPLS/MPLS- Proactive LM Mode: specifies the bit
TP configurations
used to insert the SLM Mode indication
OAM CV (Operation And Maintenance Connectivity Verification) Period: see “T-MPLS OAM” module for
details
PHB (Per Hop Behavior) range: see “T-MPLS Quality of Service” module for details
OAM Type: it’s possible to choose the OAM type at node level. If you modify this value, the new default
configuration it’s valid only for the new MEPs
OAM Rx Detection: with this parameter, it’s possible to manage T-MPLS or MPLS-TP OAM (TYPE-SEL
option refer to OAM Type configuration in the previous row) or both (BOTH option). BOTH option it’s
used, typically, in case of migration from T-MPLS towards MPLS-TP technology
Channel Type: fixed to 7FFA in this release
Proactive Lm Mode: this option is used to choose the bit for the Loss Measurement (LM) Mode indication.
The position is configurable. The values are:
0 when SLM functionality is not enabled
1 when SLM functionality is enabled

Issue 01
3 Configure Head/Tail Node


Issue 01
Head/Tail node properties
Head/Tail node represents the edge point of the T-MPLS channel,

where the encapsulation/decapsulation of the Ethernet client signal
into the T-MPLS frame (PW) is performed, according to RFC4448
QoS (Quality of service) allow the operator, on the Head node, to

provide carrier grade service that meet the negotiated SLA (Service
Level Agreement) in terms of network bandwidth, delay, jitter, packet
loss and availability.
Head Head Tunnel

Universal Pseudowire
Matrix
CLASSI
GEth port or FIER
VCG port IN OUT GEth MPLS port
FLOW FLOW or VCG MPLS port
TD
PW label Tunnel
label


Issue 01
T-MPLS label processing
On the Head/Tail node the following operations are performed:

The PW and PSN tunnel labels are “pushed” to an Ethernet packet ingressing
the T-MPLS domain (port UNI)
The PW and PSN tunnel labels are “popped” to an Ethernet packet egressing
the T-MPLS domain (port UNI)
CLASSI
FIER
UNI/IWI port: IN OUT NNI port:
Local or VCG FLOW FLOW Local or VCG
TD Tunnel
PW label
label
Tunnel
PW
VLAN VLAN

PSN = Packet Switched network

Issue 01
Test bench
VLAN: 60 to 60
Priority: 4 to 6
CLASSI
FIER
Local port: IN OUT NNI port:
port
SDH
Port#2, sl17 FLOW FLOW VCG#1, sl15
TD Tunnel
PW label
label
Tunnel
PW
VLAN VLAN
Guaranteed: PIR=CIR=20000 Mb/s

PBS=CBS=5000 bytes


Issue 01
Procedure for Head/Tail Tunnel
Step Action
1 configure the NNI Port (VCG) as MPLS *
2 Activate the MPLS Port (VCG interface)
3 Activate the UNI port
4 create and manage the Ethernet Traffic descriptors and Color Profile
5 create the Head/Tail tunnel
6 configure and manage the Tunnel
7 create the Head/Tail Pseudowire
8 configure and manage the Pseudowire
9 create and manage the Service (NULL TD creation for NNIUNI XC)
* To create the VCG port, refer to session: “S03M03_S3_NE Operation

M3_Operator_Interface_Ethernet_Bridge_features” pg. 27


Issue 01
Step 1: configure the NNI port (VCG) as MPLS
2. Scroll the window up to the bottom, choose

the VCG Index e then click on Search


Issue 01
Step 1: configure the NNI port (VCG) as MPLS [cont.]
3. Scroll the window up to the bottom, choose

the VCG port and than click on Provision
provision: not
enabled VCG


Issue 01
4. Set the max number of members

that constitute the VCG
5. Choose the VCG type:

VC4, LOVC3 or LOVC12
7. Click on Save 6. Optional. If not set, the “LBL-

ASAPVCG-SYSDFLT” ASAP will
be assigned.


Issue 01
These are equal to 0. To activate

the VC4s see the following steps.
8. Enable (Y) or disable (N) the LCAS control for the

VCG; if enabled, configure the related parameters


Issue 01
LCAS Monitoring


Issue 01
10. Set ACTIVE
9. Choose how many are to be activated
11. Click on Save
After activation, the indication

in the VCG window is updated

Issue 01
13. Scroll the window up to the bottom

and click on CREATE MPLSIF-……


Issue 01
Step 1: configure the NNI port (Local port) as MPLS
1. Select the port

The status of the port
must be set to down
2. Scroll the window up to the bottom
A new MPLS
Interface is added
3. Click on CREATE MPLSIF-..


Issue 01
Step 2: Activate the MPLSIF (VCG interface)
Select the VCG port

1. Select (T)MPLS tab
2. Set to UP
3. Click on Save


Issue 01
Step 2: Activate the MPLSIF (Local port)
1. Select the local port
3. Set Up and click on Save


Issue 01
Step 2: Activate the MPLSIF (Local port) [cont.]
1. Select the MPLS port
3. Set to up and click on Save
The color of the symbol is updated


Issue 01
Step 2: Remove MPLSIF (VCG) and deactivate the NNI port
Select the VCG port
2. Set to DOWN
3. Click on Save

N.B: The MPLSIF can be set DOWN if no Tunnel or PW are associated to.

Issue 01
Step 2: Remove MPLSIF (VCG) and deactivate the NNI port
5. Click on DESTROY MPLSIF …


Issue 01
Step 2: Remove MPLSIF (Local) and deactivate the NNI port
1. Select the MPLSIF
3. Set it DOWN and click on Save
4. Select the local NNI port

N.B: The MPLSIF can be set DOWN if no Tunnel or PW are associated to.

Issue 01
Step 2: Remove MPLSIF (Local) and deactivate the NNI port [cont.]
6. Set it DOWN and click on Save


Issue 01
Step 2: Remove MPLSIF (Local) and deactivate the NNI port [cont.]
8. Click on DESTROY MPLSIF …


Issue 01
Step 3: Activate the UNI port
1. Select the UNI
3. Set to up and
click on Save
The color of the symbol

is updated


Issue 01
2. Click on Create
Tick the box to configure ATM

traffic parameters 3. Specify the User label
see next slide

backGround Service
regulatedService1
regulatedService3
regulatedService4
Guaranteed Service2

Issue 01




Issue 01



Issue 01
1. Select a TD



Issue 01
Step 4: Ethernet Color Profile creation (Priority)
This option allows to create a Color Profile to be
associated in case of “ColorAware” policing mode
2. Click on Create
3. Specify the Color Profile

Mode: Priority
4. Assign a Label
5. According to the selected mode,

6. Click on Save & …. configure the profile
In case of “Priority” mode, the operator can assign a color to 8 different User Priority (0…. 7)

Issue 01
Step 4: Ethernet Color Profile creation (dscp)
1. Assign a label and Specify

the Color Profile Mode: Dscp
2. For dscp mode, configure

3. Click on Save & …. the code points

In case of “DSCP” mode, a color can be assigned to 64 different Code Point (0 ….. 63)

Issue 01
Step 4: Ethernet Color Profile management
To delete a Color Profile tick the box and click on “Delete”: the Color Profile will be
removed from the list (if no Service is associated to)


Issue 01
Step 4: Ethernet Color Profile management [cont.]
To modify a Color profile:
2. Select a Color Profile

N.B: a Color Profile can be modified if no Services are using it

Issue 01
Step 5: Create the Head Tunnel
This option allows to create, at the edge

port of the Network, the T-MPLS Tunnel
1. Select MPLS-TP/T-MPLS MPLS-TP/T-MPLS Tunnel
Click on Search to filter the Tunnel details

based on the selected parameter values
2. Click on Create Head/Tail Tunnel

The Tunnel Management tab displays the Filter by panel that contains the following parameters:
Tunnel Location: This specifies where the search must be executed. The values are:
ALL
SHELF 1-1
Tunnel Type: This specifies the type of Tunnel to be filtered. The values are:
LOCAL: No filter applied
CP: All the tunnel related to the Management Plane
ALL: All the tunnel related to the Control Plane
LOST: All the tunnel related to LOST
Route: Specifies the route information for the tunnel. The values are:
ACTUAL
CONFIGURED
COMPUTED
CALCULATE
Tunnel Ranging Filter: Specifies the From and To range with the identifier, Ingress IP, and Egress IP.
Tunnel ID Filter: Enable the check box to enter the tunnel id to be filtered in the text field.
Tunnel AID Filter: Enable the check box to enter the tunnel access identifier to be entered in the
entry field.

Issue 01
Step 5: Create the Head Tunnel [cont.]
5. Expected label for incoming segment 3. Click on Select to choose the MPLS port
4. Insert the user label (optional)
6. Transmitted label for outgoing segment
7. Enable/Disable the DDM protection switch
Configure OAM resources only in

case of maintenance association
The new Tunnel appears in the window

MPLS Port: select the end point of the T-MPLS tunnel

Direction: specify the Tunnel Segment direction (BIDIR, UNIDIRIN, UNIDIROUT)
In Label: specify the expected label for the incoming segment (16 – 131071)
PHB Profile: select the PHB Profile resource (if no fill, the default value is used)
L2 Encapsulation Profile: specify the L2 encapsulation profile to be used in case of MPLS mapped over
Ethernet (if no fill, the default value is used)
User Name: (optional) specify a tunnel User name
Out Label: specify the transmitted label for the outgoing segment (16 – 1048575)
Click on General that displays and allow to modify the general information of a Tunnel.
Click on Path that shows and allow to modify the path of a Tunnel.
Click on PWs that displays the pseudowires related to a Tunnel.
The DDM protection Switch for SD is used to enable the protection switching also when DDM SD is
detected at the Tunnel termination point, where a TSF is generated. The supported values are:
Enable
Disable
Add Group: if you set enable, the tunnel can’t be used for the pseudowire creation

Issue 01
Step 6: Configure and activate the Head Tunnel
1. click on the tunnel
See next page


Issue 01
Step 6: Configure and activate the Head Tunnel
2. Select a VT (or leave the default) Optional
4. Set to ON
3. Assign the TD
parameters
5. Click on Save
The status must be ON

Identifier: (optional) specify a string that will be associated to the Tunnel

VT Head: select, in the list, the Virtual Transport that will be associated to the Tunnel (only active VT
defined on the port are listed). If no fill, the Tunnel is automatically associated to the default VT (=1)
(See next session for details).
CIR, CBS, PIR, PBS : assign a TD profile used by the System for bandwidth checks related to “port bit
rate” or “Virtual Transport port bit rate” on which the Tunnel is defined.

Issue 01
Step 6: Tunnel management and deletion
2. Click on Search to filter the Tunnel details



Issue 01
Step 6: Tunnel management and deletion [cont.]
The Tunnel can be deleted if its Status is OFF
3. To set the Status=OFF,

click on the Tunnel Management options:
General: displays the Tunnel
configuration window
Path: displays the Tunnel
activation window
PWs: displays the list of PWs
transported by the Tunnel
4. Set the Admin Status=OFF

and then click on Save
5. To delete a tunnel, tick the box and click on Delete

N.B: “Status” can be set to OFF if no PW are associated to.

3,4,5 steps for deletion and deactivation only

Issue 01
Step 7: Create the Head Pseudowire
This option allows to create, at the edge port of the Network,
the Pseudowire that encapsulate/decapsulate the Traffic flow
1. Select MPLS-TP/T-MPLS PseudoWire
Click on Search to filter the Pseudowire details

2. Click on Create Head/Tail Pseudowire


Issue 01
3.: click on Selected

TUSEG 4. Click on Search
5. Select the TUSEG-x-x-x
6. Expected label for

incoming PW 7. Insert the user label (optional)
8. Transmitted label for outgoing PW

9. Click on Save
The new PseudoWire appears in the window

Port: select the related Tunnel Segment or (in case of PW directly on physical link) the physical Interface
Control Word: it enable/disable the capability to insertion/stripping of the Control Word, associated to
the PW segment (cfr. IETF RFC 4385)
User Name: (optional) specify a PW User name
Out Label: specify the transmitted label for the outgoing PW (16 – 1048575)
L2 Encapsulation Profile: specify the L2 encapsulation profile to be used in case of PW mapped over
Ethernet (only for PW directly on physical link)

Issue 01
Step 8: Configure and activate the Pseudowire
1. click on the PseudoWire
4. Set to ON
3. Assign the TD parameters

5. Click on Save
The status must be ON

Identifier: (optional) specify a string that will be associated to the PW

VT Head: select, in the list, the Virtual Transport that will be associated to the PW (only active VT
(See next session for details).
rate” or “Virtual Transport port bit rate” on which the PW is defined.

Issue 01
Step 8: Pseudowire management and deletion
2. Click on Search to filter the PseudoWire details



Issue 01
Step 8: Pseudowire management and deletion [cont.]
The PseudoWire can be deleted if its Status is OFF
3. To set the Status=OFF, click on the PseudoWire
4. Set the Admin Status=OFF

and then click on Save
5. To delete a tunnel, tick the box and click on Delete

The PW can be deleted if its Status is OFF;

N.B: “Status” can be set to OFF if no Services are associated to.
3,4,5 steps for deletion and deactivation only

Issue 01
Step 9: Create the Ethernet Service : UNI-NNI
This option allows to create the connectivity between
the payload data at UNI interface and the Pseudowire
1. Select Connection Ethernet Service XC EVPL
2. Click on Create


Issue 01
Step 9: Create the Ethernet Service : UNI-NNI [cont.]
3. Select UNI - NNI

PW used as Transport Link
5. Click on Search
6. Select the PW


Issue 01
Detail 1: C-VLAN swap in the UNI to NNI Ethernet Service
C-VLAN New C-VLAN
IN OUT
FLOW FLOW
VLAN
Pop



Issue 01

the UNI port (sl 17 port 2)
9. Insert the Service

Label (optional)
8. Select the UNI port

Selective tunneling is used for C-BPDU or P-BPDU.

If selective tunneling check box is enabled, the traffic descriptor is not displayed.

Issue 01

= PRIO + VLAN


PRIO+VLAN: VLAN identifier + Priority

Issue 01
13. Set Policing mode

= colorBlind



Issue 01
IN OUT
FLOW FLOW



Issue 01
Step 9: Create the Ethernet Service: NNI-UNI
This option allows to create the connectivity between
the payload data at UNI interface and the Pseudowire
2. Click on Create


Issue 01
Step 9: Create the Ethernet Service: NNI-UNI [cont.]
3. Select NNI - UNI

5. Select the PW


Issue 01

the UNI port (sl 17 port 2)
8. Insert the Service

Label (optional)
7. Select the UNI port


Issue 01
9. Select a “Null” TD in the list:

see next slide for configuration
In case of VLAN push = “enabled”,

enter the required parameters
port
SDH
OUT IN
FLOW FLOW
VLAN
10. Click on Save & …. Push
N.B: The “Null TD” must be in the same CoS of the UNI-NNI TD applied on the remote end point.
network.

Issue 01
The operator must create also a Null Traffic Descriptor to be
applied in the NNI-UNI direction of the connection
2. Click on Create
3. Assign value 0 to
all parameters


Issue 01
Check the created objects for UNI NNI connection
2. Click on search
To delete a Service, tick the box and click on Click on the XC Id to display
Delete (a multiple selection is admitted) the Ethernet Flow window

Issue 01
Check the created objects for UNI NNI connection [cont.]
3. Select a XC UNI-NNI
Click on the InFlow (OutFlow) to display or Click on the TD to display

modify the Ethernet Flow parameters the Descriptor values


Issue 01
Check the created objects for UNI NNI connection (IF)



Bitmask details: allows to enable or disable the Protocol frames that can accede the port. Clicking on
the Bitmask detail button is possible to display and set the mask

Issue 01
Check the created objects for UNI NNI connection (OF)
It allows to modify the

User Label


Issue 01
Check the created objects for NNI UNI connection
1. Select (T)MPLS Ethernet Service XC EVPL
2. Click on search

Issue 01
Check the created objects for NNI UNI connection (TD)
3. Select a XC NNI-UNI
Click on the TD to display

Click on the InFlow (OutFlow) to display or
the Descriptor values
modify the Ethernet Flow parameters


Issue 01
Check the created objects for NNI UNI connection (IF)


Issue 01
Check the created objects for NNI UNI connection (OF)
It allows to modify the

User Label


Issue 01
Blank Page


Issue 01
4 L2 Encapsulation profile


Issue 01
L2 Encapsulation Profile management
• The Layer 2 Encapsulation profile specifies the parameters to be used in case

of mapping of MPLS over Ethernet when a switched network is present.
1. Select MPLS-TP/T-MPLS L2 Encapsulation Profile
Default values
2. To delete a Profile, tick the

box and click on Delete


Issue 01
L2 Encapsulation Profile creation
1. Click on Create
2. Set the parameters
A new L2 Encapsulation Profile is added to the list, with a new generated Access
Identifier, the value is in the range L2ENCAPPROF-{1-32}

MAC Destination Address: specifies the MAC address to be used in case of mapping of MPLS over Ethernet
when a switched network is present
Tagged Flag: specifies the Tagged/Untagged flag
VLAN Identifier: specifies the VLAN to be used in case of switched network (802.1Q)
Priority: specifies the Priority value for tagged Ethernet frame
Drop Eligible: specifies the Drop Eligible indication according to 802.1ad

Issue 01
Blank Page


Issue 01
5 Virtual Transport management


Issue 01
Virtual Transport concept
• VT (Virtual Transport) is a logical entity associated to an output port for

hierarchical shaping level function: it defines an aggregated packet stream
that competes with other aggregates for resource allocation, e.g. bandwidth.
• Applied to both Individual and/or Aggregated (in case of LAG) Egress Ports
• Virtual Transport:
• Default VT: Automatically coupled with whole egress port [for legacy services (Port-
to-Port ..)] at port activation
• “Service-aware VT” associated (via operator) to services (SVLAN, PW, MPLS label,
VPLS..) according to TSS-320 NE configuration
• A set of 8 queues is associated to each Virtual Transport.


Issue 01
Virtual Transport architecture
A Virtual Transport is identified by:
output port associated

Aggregation criteria (SVLAN,
PW, MPLS label, VPLS..)
Shaping Shaping Shaping
VT Committed Rate at Level 2 at Level 1 over Port
[over Virtual [over Virtual
VT Shaping Rate (in case of Transport Transports
Queues (VTQs)] (VTs)]
shaping active) VT shaper
VT3 r1
Strict priority
Tail drop on G
VT 2 r2
q1 s1
…
…
q2 s2 …
Port rate
q3 s3 VT1 rn
…
WRED on Y WFQ,
…
Tail drop on G Wi
…
sm
q8
WFQ,
Wi


Issue 01
Virtual Transport creation
1. Select the port (must be up) and click on “Quality of service” tab
2. Tick off the box
3. Click on Search
The list of available

VT is displayed

“Search” display the Virtual Transport list according to the range indicated in the VT Search window;
“SearchAll” display the whole llist

Issue 01
Virtual Transport creation [cont.]
4. Select a VT
The Virtual Transport Queue

window is open


Issue 01
By selecting each queue, the operator can modify the related parameters
5. Select a queue
6. Modify the queue parameters and click on Save

Queue parameters:
Queue: queue identifier (0 – 7)
Type: the scheduling type associated to the queue (SP or WFQ).It is a read only value.
Committed Rate: the queue committed rate associated to the weight of the scheduler (only for
WFQ)
Shaping: enable (true) or disable (false) the shaper connected to the queue
Peak Rate: the queue peak rate associated to the rate limiting, introduced by the shaper
Committed Queue Size/Excessive Queue size: refer to the CQS and EQS queue size parameters
Queue Profile: it refers to the green and yellow thresholds (see next slides for details)
N.B: the total bandwidth for the WFQ queues, defined by the sum of the committed rate, is limited
by the available (not used by the Stricty Priority queues) bandwidth

Issue 01
After saving, the queue parameters are updated
7. If necessary, modify the VT parameters and

click on Save & Activate

Virtual Transport parameters:

Index: VT identifier (1 – 4096)
Committed Rate: the VT committed rate associated to the weight of the TM scheduler
Shaping: enable (true) or disable (false) the VT shaper
Peak Rate: the VT peak rate associated to the rate limiting, introduced by the shaper
User label: the operator can modify the default label for the VT
Aggregation Criteria: specify the associated service (mplstunnel, mplspw, vpls)
Referenced Number: number of associated entities for the specific service
Status: active / notInService

Issue 01
Blank Page


Issue 01
6 T-MPLS Quality of Service


Issue 01
DiffServ architecture
• The Differentiated Service (DiffServ) Architecture, based on priorization

approach, provides a way to categorize and prioritize network traffic (flow)
aggregates, enabling QoS provisioning rules at the edge of a domain to create
traffic aggregates, and coupling each of these with a specific forwarding path
treatment in the domain, using a “code-point” (value) in the packet header
(Per-Hop Forwarding Behavior, PHB).
• Using DiffServ approach, each node uses the QoS information coded into the
packet header to correctly forward that Class of traffic (CoS), according to its
bandwidth, delay, jitter and loss charactheristic.


Issue 01
PHB Profile concept
• Experimental bits, in the T-MPLS header, identifies the the QoS information
associated to the traffic packet in a DiffServ architecture
Label EXP S TTL
• The scheduling of the MPLS packet depend ONLY on MPLS EXP bits
• Up to 8 MPLS PHB can be encoded in MPLS EXP bits


Issue 01
PHB Profile scheduling class
• In configuring the forwarding behavior applied to the packets on each NE,

inside a DiffServ domain, the user can use the following “data treatments”
(defined as PHB Scheduling Class, PSC):
• EF (Expedited Forwarding): used to give preferential queuing treatment in a Strict

Priority queue
• HIGH2
• AF (Assured forwarding): this defines four independent forwarding classes denoted as
AF1, AF2, AF3, AF4
• DE (Default behavior): identify the existing Best Effort traffic
• LOW2


Issue 01
PHB Profile creation
1. Select MPLS-TP/T-MPLS Quality of Service PHB Profile
2. Choose an operation mode.
3. Assign EXP value to each

PSC, and click on Save


Issue 01
PHB Profile management
This option allows to display or delete PHB profiles
1. Select MPLS-TP/T-MPLS Quality of Service PHB Profile
Profile n°1 and n°2 are created by

default and cannot be deleted
2. To delete a Profile, tick the


The PHB Profile table present the following parameters:

Access Identifier: this specifies the Identifier of the profile stored in the system
EXP Bit I (I = 0-7): reports the user association between the EXP Bit field and the defined PSCs
In Use: specifies if the PHB is referenced by a Tunnel segment or a Pseudowire segment
CoS: specifies the operation mode (5P3D or 8P0D)

Issue 01
Queue Profile management
8 queues (VTQ) are associated to each Virtual Transport:
- 2 strict priority queues (SP VTQ)
- 6 queues in WFQ (WFQ VTQ)


Issue 01
WFQ management
For each Forwarding Queue is requested to define an Egress Dropper behavior
(Queue Profile) in order to to optimize the expected queuing utilization.
The Egress Dropper behavior is attained by configuring the following WRED
profile parameters:
o threshold max green (Max_th_g)
o threshold min green (Min_th_g)
o max discard probability green (Pmax_green)
o threshold max yellow (Max_th_y)
o threshold min yellow (Min_th_y)
o max discard probability yellow (Pmax_yellow)
P(x)
Pmax_yellow
Pmax_green
Low_th_y Up_th_y x
Low_th_g Up_Th_g
WRED = Weighted Random Early Detection

WRED parameters:
UpTh Green Pkts: specifies the percentage (0 to 100) of the buffer utilized after which the drop
probability of Green packets is 100 percent. The default value is 90.
LowTh Green Pkts: specifies the percentage (0 to 100) of the buffer utilized after which the drop
probability of Green packets starts to rise above 0. The default value is 70.
Max Prob of Green Pkts: specifies the drop probability (0 to 100) of Green packets increases steadily
from 0 (at Queue Profile Green Lower Threshold) up to Queue Profile Green Drop Max Probability (at
Queue Profile Green Upper Threshold)
UpTh Yellow Pkts: specifies the percentage (0 to 100) of the buffer utilized after which the drop
probability of Yellow packets is 100 percent. The default value is 60.
LowTh Yellow Pkts: specifies the percentage (0 to 100) of the buffer utilized after which the drop
probability of Yellow packets starts to rise above 0. The default value is 50.
Max Prob of Yellow Pkts: specifies the drop probability (0 to 100) of Yellow packets increases steadily
from 0 (at Queue Profile Yellow Lower Threshold) up to Queue Profile Yellow Drop Max Probability (at
Queue Profile Yellow Upper Threshold)

Issue 01
Queue Profile list
This option allows to display or delete Queue profiles
1. Select MPLS-TP/T-MPLS Quality of Service Queue management
To delete a Profile, tick the box and click on Delete


Issue 01
Queue Profile creation
1. Select MPLS-TP/T-MPLS Quality of Service Queue management
2. Click on Create
3. Assign a name
4. Modify the default

WRED parameters
5. Click on Save to confirm

Issue 01
7 PW/ELAN – VT Association


Issue 01
Virtual Transport Association
• PW-VT Association and ELAN-VT Association enforces Traffic Rate control at the
interconnection points (UNI/IWI). It correlates a VT to the PW (or E-LAN) at the egress
UNI port
• UNI/IWI support any combination of VT aggregation criteria (PW, VPLS, MPLS)
UNI/IWI PW
VT


Issue 01
Virtual Transport Association creation
This option allows to create, on a UNI port, the association
between a Pseudowire (or a E-LAN) and the port
1. Select the port

(must be up)
2. Scroll the window up to bottom
3. Select the VPLS or PW option,

according to the Service Type


Issue 01
Virtual Transport Association creation [cont.]
I.e.: Select the PW and the VT

to be associated


Issue 01
8 Configure Transit node


Issue 01
8 Configure Transit Node
Transit node properties
Transit node perform T-MPLS cross connection at tunnel layer or at PW

layer
According to the cross connection operation, a label swapping at

Tunnel layer or at PW layer is executed
PW label Tunnel
swap label swap
Tunnel Tunnel Tunnel
PW PW PW
VLAN VLAN VLAN


Issue 01
Procedure for VPLS Service
Step Action
1 configure the NNI Port as MPLS
2 Activate the NNI Port and the MPLS Port
3 Create the Transit Tunnel
4 Configure the Transit Tunnel
5 create the Transit Pseudowire
6 Configure the Transit Pseudowire
It is supposed that the trainee can perform the steps 1, 2


Issue 01
Step 3: Create the Transit Tunnel
This option allows to create, on a transit node, the T-MPLS Transit Tunnel
Click on Search to filter the Tunnel details

2. Click on Create Transit Tunnel


Issue 01
Step 3: Create the Transit Tunnel [cont.]
3. Click on Select the choose 4. Click on Select the choose
the MPLS port From 6. Choose the Direction the MPLS port To
5. Insert the Expected label and the

transmitted label for incoming segment
and outgoing segment
8. Click on Save 7. Choose Cross-connection Type=2WAY

MPLS Port: select the two side of the transit tunnel

User Name: (optional) specify a User name for the segment
Ethernet
Cross-connection Type: select 1WAY (unidirectional cross-connection between the selected FROM and TO
segments) or 2WAY ( bidirectional cross-connection between the selected FROM and TO segments).

Issue 01
Step 4: Configure and activate the Transit Tunnel
1. click on the tunnel
See next page


Issue 01
Step 4: Configure and activate the Transit Tunnel [cont.]
2. Select a VT for Head and Tail Optional
(or leave the default)
3. Set to ON
6. click on Save 5. Choose Cross-connection Type=2WAY


VT Head, VT Tail: select, in the list, the Virtual Transport that will be associated to the head segment
(From entity) and to the Tail (To entity) segment (only active VT are listed). If no fill, the Tunnels are
automatically associated to the default VT (=1) (See next session for details).

Issue 01
Step 5: Create the Transit Pseudowire
This option allows to create, on a transit Node, the transit Pseudowire.

2. Click on Create Transit Pseudowire


Issue 01
Step 5: Create the Transit Pseudowire [cont.]
3. Click on Select the choose the 4. Click on Select the choose the
TUSEG or MPLS port “From” TUSEG or MPLS port “To”
6. Set the Direction
8. Click on Save
5. Insert the Expected label and the

transmitted label for incoming segment
and outgoing segment
7. Choose Cross-connection Type=2WAY

MPLS Port: select the two side of the transit pseudowire

Direction: specify the PW Segment direction (BIDIR, UNIDIRIN, UNIDIROUT)
User Name: (optional) specify a User name for the PW segment
Ethernet (for MPLS port only)
Cross-connection Type: select 1WAY (unidirectional cross-connection between the selected FROM and TO
segments) or 2WAY ( bidirectional cross-connection between the selected FROM and TO segments).
If you want to realise the pseudowire transit over TUSEG, it’s mandatory to create before the
pseudowire transit, an a Head/tail Tunnel

Issue 01
Step 6: Configure and activate the Transit Pseudowire
1. click on the PW
See next page


Issue 01
Step 6: Configure and activate the Transit Pseudowire [cont.]
2. Select a VT for Head and Tail
(or leave the default)
Optional
3. Set to ON
5. Choose Cross-connection Type=2WAY

6. click on Save


VT Head, VT Tail: select, in the list, the Virtual Transport that will be associated to the head segment
(From entity) and to the Tail (To entity) segment (only active VT are listed). If no fill, the PWs are
automatically associated to the default VT (=1) (See next session for details).

Issue 01
Blank Page


Issue 01
9 VPLS (Virtual Private LAN Service)


Issue 01
VPLS architecture
The VPLS (Virtual Private LAN Service) architecture allows multiple

sites to be connected in a single emulated bridged domain over a
provider management T-MPLS network. All customer sites in a VPLS
instance (i.e. a VPLS for a particular enterprise) appear as they are on
the same Local Area Network, regardless of their location.
It is based on a full meshed tunnel infrastructure


Issue 01
VPLS architecture
In rel. 3.0 the E-LAN service can be implemented only in a full mesh
configuration. That means every nodes must be linked to every other
nodes , this heavy implementation constrains to use the E-lAN in small
network. This limitation is due to the fact the PWs are able to forward
the traffic received from others PW, only to the UNI port (split horizon )
In rel. 3.1 there is the choice to decide if this traffic received in the PW
(NNI port) must be forward to other PWs (Hub and Spoke) and UNI ports
(in this case you will configure the PW as Spoke) or forward only to UNI
port and spoke PW (in this case you will set the PW as Hub).
It has been also introduced the choice to enable or disable the Mac
learning function (in rel 3.0 was always enabled ).
Example 1: input PW Hub Example 2: input PW Spoke
PW (hub) PW (spoke)
PW (spoke) PW (hub)
UNI PW (hub)
UNI

Issue 01
VPLS architecture
The below scenario shows a E-LAN service in rel 3.0 that is supported only
in a full mesh configuration.
NODE B
NODE A
PW 1
TC2-3
(hub)
PW 1
TC2-1 (hub) PW 2
4-1 STM64 4-1
(hub)
PW 2
(hub)
18-1
6-4
10 GBE
1 GBE
10 GBE
6-4 17-1
18-1
18-1 10 GBE 17-1
6-3 1 GBE 6-3

PW 2 PW 1
TC2-5
(hub) (hub)
NODE D
NODE C


Issue 01
VPLS architecture
The below scenario shows a E-LAN service in rel 3.1 and is not need any
more a full mesh configuration.
NODE B
NODE A
PW 1
TC2-3
(spoke)
PW 1
TC2-1
(hub) PW 2
4-1 STM64 4-1
(spoke)
18-1
6-4
10 GBE
1 GBE
10 GBE
6-4 17-1
18-1
18-1 10 GBE 17-1
6-3 1 GBE 6-3 PW 1

(hub) TC2-5
NODE D
NODE C


Issue 01
VPLS provisioning
In the node both tunnel and PW are initiated at NNI ports. UNI flow and
PWs are attached to the bridge of the associated VPLS instance
etsFlow
PWSEG#x
(Bid)
VPLS Instance
etsFlow
PW Bid
tunnel


Issue 01
Procedure for VPLS service
Step Action
1 Create all T-MPLS tunnel and PWs in the network
2 Activate the UNI ports
3 Create the Ethernet Traffic descriptor
4 Create the VPLS instance
5 Associate UNI ports and PW to the VPLS instance
6 Create the VPLS Service


Issue 01
Step 4: create the VPLS instance
This option allows to create a VPLS instance into the node
1. Select (T)MPLS E-LAN Service Mgnt ELAN Service
2. Specify a range and click on Create
4. Click on Save
3. Assign an Id: (i.e: 1)

“Mac Aging” is fixed to TRUE

Issue 01
Step 5: associate the UNI ports to the VPLS
1. Select UNI Port Binding tab
2. Select the UNI Ports to be

associated and click on >>
3. Click on Save

UNI active ports are available in the list; the operator associates the port by adding it in the right side
window

Issue 01
Step 5: associate the PWs to the VPLS
1. Select PW Binding tab
2. Select the PWs to be associated 3. Choose the role:

Hub or Spoke
4. Click on Save

PW must be previously created; the operator associates the PWs by adding them in the right side
window

Issue 01
Step 6: Create the VPLS Service : UNI-NNI
This option allows to create the connectivity
between the payload data at UNI interfaces
and all PW associated to the VPLS instance
1. Select Connection Ethernet Services XC EVPLAN
2. Click on Create


Issue 01
Step 6: Create the VPLS Service : UNI-NNI [cont.]
3. Select UNI - NNI
4. Click on Select to choose the ELAN
5. Click on Search
choose the UNI port
6. Select the ELAN service
8. Select the UNI ports

Service Label: specifies the name or label for the service

Issue 01
Detail 1: C-VLAN swap in the UNI to NNI VPLS Service
C-VLAN New C-VLAN
IN OUT
FLOW FLOW
VLAN
Pop



Issue 01

= PRIO + VLAN



Issue 01
12. Set Policing mode

= colorBlind


Policing Mode:
colorAwareWithCoupling: the policing is based on the associated TD and on the priority colors of
the associated “color Profile”; Coupling Flag mode is managed (MEF compliant).

Issue 01
IN OUT
FLOW FLOW


Policing Mode:
colorAwareWithCoupling: the policing is based on the associated TD and on the priority colors of
the associated “color Profile”; Coupling Flag mode is managed (MEF compliant).

Issue 01
Step 6: Create the VPLS Service : NNI-UNI
NNI UNI direction 1. Select NNI - UNI
2. Click on Select to chooset the

3. Click on Select to choose the UNI port
4. Select a “Null” TD in the list
OUT IN
In case of VLAN push = “enabled”, FLOW FLOW
enter the required parameters
VLAN
Push
N.B: The “Null TD” must be in the same CoS of the UNI-NNI applied TD.

Issue 01
Ethernet Service management
2. Click on search


Issue 01
Ethernet Service Flow window
3. Select a XC UNI-NNI
Click on the TD to display

Click on the InFlow (OutFlow) to display or the Descriptor values
modify the Ethernet Flow parameters


Issue 01
Ethernet Flow parameters: Inflow




Issue 01
Ethernet Flow parameters: Outflow


Issue 01
Procedure for VPLS service deletion
Step Action
1 Delete the EVPLAN Service
2 Disassociate UNI ports and PW from the VPLS instance
3 Delete the VPLS instance


Issue 01
Step 1: delete the EVPLAN Service
2. To delete a Service, tick the box and click on

Delete (a multiple selection is admitted)


Issue 01
Step 2: disassociate the UNI ports from the VPLS
1. Select UNI Port Binding tab
2. Select the UNI Ports to be

disassociated and click on the
arrow to remove


Issue 01
Step 2: disassociate the PWs from the VPLS
1. Select PW Binding tab
2. Select the PWs to be

disassociated and click on the
arrow to remove


Issue 01
Step 3: delete the VPLS instance
1. Select (T)MPLS E-LAN Service Mgnt ELAN Service
2. Specify a range and click on “View”
3. Tick the box and click on Delete (a multiple selection is admitted)


Issue 01
10 MPLS OAM


Issue 01
10.1 T-MPLS / MPLS-TP OAM theory


Issue 01
Introduction
TSS-320 rel.4.0 supports T-MPLS / MPLS-TP OAM functions at Tunnel

level only.
MEPs only are to be implemented.
The total number of OAM points is up to 4k for each 10G Packet
Processor (4k in a 10G board; 4k for the first Packet Processor + 4k for
the second Packet Processor in a 20G board)
thebandwidthreservedforOAMis50Mbit/sincaseof10Gboards
There are up to 512 T-MPLS / MPLS-TP DM on demand tools available for
each 10G Packet processor (512 DM in a 10G card; 512 DM for the first
Packet Processor + 512 DM for the second Packet Processor in a 20G
card). These resources are shared for on demand and proactive tools.
There are up to 128 SLM Instances (Ethernet + T-MPLS / MPLS-TP) for
each 10 G Packet Processor (128 SLM in a 10G card; 128 SLM for the first
Packet Processor + 128 SLM for the second Packet Processor in a 20G
card). The maximum number of supported SLM instances can be lower if
the period is less than 3.3 ms
The TSS-320/160 supports the Synthetic LM OAM tool only

Issue 01
The TSS-320 rel.4.0 supports T-MPLS and MPLS-TP OAM functions

In this release, the NE supports the selection between T-MPLS and MPLS-
TP OAM tools as default for the new created Tunnels at node level
In this release, the NE supports the selection between the reception and
processing of both T-MPLS and MPLS-TP OAM tools or only the OAM tools
configured for generation at Tunnel level (Global Network configuration)
For each Tunnel Termination Point, MEPs can be optionally configured
and activated, via ZIC or OMS, in order to originate and / or terminate
T-MPLS / MPLS-TP OAM packets.
By default T-MPLS / MPLS-TP OAM at Tunnel level are disabled.


Issue 01
Maintenance Entity (ME): entity between two Maintenance Entity

Group End Points, that requires management. The basic ME in the T-
MPLS network is the path of a point to point LSP. The ME is the MD
object in the TSS-320/160 OAM configuration
ME Group (MEG) (the MEG is the MA object in the TSS-320/160 OAM
configuration): includes different MEs that satisfy the following
conditions:
MEs in a MEG exist in the same administrative boundary
MEs in a MEG operates at the same MEG Level
MEs in a MEG belong to the same point to point T-MPLS connection or to the
same point to multipoint T-MPLS connection. For a point to point T-MPLS LSP,
a MEG contains a single ME. For a point to multipoint T-MPLS LSP containing n
end points, a MEG contains (n-1) MEs.


Issue 01
MEG End Point (MEP): End Point of a T-MPLS MEG; it is capable of

initiating and terminating OAM packets for fault management and
performance monitoring. The OAM packets are inserted in T-MPLS
connection and it is assumed that they are subject to the same
forwarding treatment as the T-MPLS packets being monitored.
MEG Intermediate Point (MIP): intermediate Point in a T-MPLS MEG
that is capable of reacting to some OAM frames (i.e. responding to a
Loopback). A MIP does not initiate an OAM frames.
MEG Level (MEL):in case MEGs are nested, the OAM packets of each
MEG have to be clearly identifiable and separable from the OAM packets
of the other MEGs. In case the OAM packets are not distinguishable by
the T-MPLS layer encapsulation itself, the MEG Level in the OAM packet
distinguishes between the OAM packets of nested MEGs. Eight MEG
Levels (from 0 to 7) are available.
Pro-active OAM: based on periodic OAM packet generation. These OAM
packets are inserted at the ingress of the MEG, and extracted and
processed at the egress of the MEG.


Issue 01
On-demand OAM: based on one shot OAM packet query and response.
These OAM packets are inserted at the ingress of the MEG; they can be
extracted and processed from intermediate and/or egress points of the
MEG.
Two way Packet Delay: Packet Delay can be specified as round trip
delay for a packet, defined as the time elapsed since the start of
transmission of the first bit of the packet by a source node until the
reception of the last bit of the loop backed packet by the same source
node, when the loop back is performed at the packet’s destination
node.
Two way packet delay variation: it is the difference between two
subsequent two way packet delay measurements.
(Dual ended) Synthetic Loss Measurement (SLM): OAM tool derived
from Standard Loss Measurement; counters in the peer MEPs maintain a
count of transmitted and received CV / CCM packets instead of service
packets.


Issue 01
DDM-SD: defect associated to the degraded status of the line; it is

detected monitoring the optical power in the Digital Diagnostic
Monitoring (DDM) capable SFP/XFP. The system provides optionally the
insertion of T-MPLS / MPLS-TP FDI / AIS packets in case of detection of
DDM-SD in an intermediate node and so provides the protection
switching as consequence when FDI is detected at the Tunnel
termination point.
Signal Degrade (DEG): it is detected by MEP on the basis of Synthetic
Loss Measurement tool, so this is a different defect from DDM SD.


Issue 01
T-MPLS frame format


Issue 01
T-MPLS Tunnel OAM packet format
T-MPLS TU header is appended to the OAM PDU. In this T-MPLS header the label
has the same value of the label in the monitored T-MPLS Tunnel header.


Issue 01
T-MPLS OAM PDU format
In the T-MPLS OAM header the fixed label value is "14"; the S bit has the
fixed value "1“
At the creation point, the MEL (MEG level) is set to "0"
The TTL has the fixed value 0x01 because, in rel.4.0, the exchange of
OAM packets is between MEPs; in the future it could have different values
in case of exchange of packets with MIPs.

Issue 01
MPLS-TP frame format


Issue 01
MPLS-TP Tunnel OAM packet format
The TU header is appended to the OAM PDU. In this TU header the label
has the same value of the label in the monitored Tunnel.
In the MPLS-TP GAL the fixed label value is "13"; the TC (Traffic Class)
bits have the fixed value "7".
The S bit has the fixed value "1".
The TTL has the fixed value 0x01 because, in this release, the exchange
of OAM packets is between MEPs only.

Issue 01
MPLS-TP Tunnel OAM packet format [cont.]
In the Associated Channel Header (ACH) the Version bits have the fixed
value "0". The Reserved bits has the fixed value "0". The Channel Type
field is configurable.


Issue 01
Supported OAM in release 4.0
The TSS-320/160 rel.4.1 supports the following T-MPLS / MPLS-TP OAM:
Supported T-MPLS OAM (as per ITU-T Y.1711, ITU-T G.8114):

CV: Connectivity Verification
FDI: Forward Defect Indication
APS: Automatic Protection Switching
Two-way T-MPLS Delay Measurement (DM), both proactive and on demand
Dual-ended proactive T-MPLS Synthetic Loss Measurement (SLM)
Supported MPLS-TP OAM (as per IETF draft bhh MPLS-TP OAM Y1731):
CCM: Continuity Check Message
AIS: Alarm Indication Signal
APS: Automatic Protection Switching
Two-way MPLS-TP Delay Measurement (DM), both proactive and on demand
Dual-ended proactive MPLS-TP Synthetic Loss Measurement (SLM)


Issue 01
CV (Connectivity Verification) and CCM (Continuity Check Message)
It is possible to configure and enable the Connectivity Verification (CV)

(CCM for MPLS-TP) function, in order to detect Loss Of Continuity (LOC)
between pairs of MEPs in a MEG, to detect an unintended connectivity
between two MEGs, an unintended connectivity within the MEG with an
unexpected MEP, and other defect conditions (e.g. Unexpected Period,
etc.)
Moreover, CV packets are used to support Synthetic LM (SLM) tool
When MPLS-TP is supported, CCM packets are used instead of CV.
NE1 T- MPLS NE3 NE2

ETH ETH
T-PW
CV/CCM
ME Tunnel
MEP MEP
MEG

MEG (Maintenance Entity Group): is a group including different Entity to be managed.

MEP (MEG End Point): End Point of a T-MPLS MEG. It is capable of initiating and terminating OAM packets
for fault management and performance monitoring
By default the complete CV / CCM function is disabled.
The NE is able to generate, receive and process version 1 only T-MPLS CV OAM packets. Backwards
compatibility to version 0 is NOT possible.
The bandwidth reserved for OAM is 50 Mbit/s in case of 10G boards, 100 Mbit/s in case of 20G boards.
The total number of OAM points can not exceed 4k points for 10G board; 4k for the first Packet Processor
+ 4k for the second Packet Processor in a 20G board

Issue 01
CV and CCM period values
For each enabled CV / CCM source point, it is possible to configure the

CV Period or the default value can be used.
The CV / CCM packets are transmitted periodically according with the
CV Period parameter, which value is application dependent. Considering
the application supported by this release, for Fault Management, the
configured transmission period should be = 1 s, while for Protection
Switching the configured transmission period is 3.33 ms
For Connectivity Verification the default value should be = 1 s
From this release, specific values (0.5 ms, 0.1 ms and 1 ms) are
supported for CV Period that can be used only when the SLM
functionality is activated
For each created MEP, at Tunnel level, we have the possibility to
optionally activate the capability to detect a Loss Of Continuity alarm.
By default the Loss Of Continuity defect detection capability is disabled.


Issue 01
Unidirectional CV / CCM configuration


Issue 01
Bidirectional CV / CCM configuration


Issue 01
CV OAM format

In the Flags area the following values are inserted:

Bit-8 (RDI)
Bit 7-4 (reserved) = 0. One of these reserved bits is used for the Loss Measurement (LM) Mode
indication. The position is configurable. The value of this bit is:
0 when SLM functionality not enabled
1 when SLM functionality enabled
Bit 3-1 = CV Period (Transmission Period)
The MEP ID value field's length is 16 bits. The NE inserts into this field a 13 bits integer value (MEP ID),
identifying the transmitting MEP. The three MSBs of the first octet are not used and set to 0, so the
range of MEP ID is from 0 to 8191
The NE inserts in the MEG ID value the number used by configuration to identify the MEG to which the
MEP belongs
For backwards compatibility, the NE insert in the last two bytes the BIP-16, calculated over the CV PDU
frame.

Issue 01
CCM OAM format

In the Flags area the following values are inserted:

Bit 8 (RDI)
Bit 7-4 (reserved) = 0. One of these reserved bits is used for the Loss Measurement (LM) Mode
indication. The position is configurable. The value of this bit is:
0 when SLM functionality not enabled
1 when SLM functionality enabled
Bit 3-1= CCM Period (Transmission Period)
The MEP ID value field's length is 16 bits. The NE inserts into this field a 13 bits integer value (MEP ID),
identifying the transmitting MEP. The three MSBs of the first octet are not used and set to 0, so the
range of MEP ID is from 0 to 8191
The NE inserts in the MEG ID value the number used by configuration to identify the MEG to which the
MEP belongs

Issue 01
FDI (Forward Defect Indication) and AIS (Alarm Indication Signal)
Detected failures at link layer trigger FDI packets insertion in all the pass-
through tunnels correspondent to the link where failure is detected
FDI packets are transmitted with the periodicity of 1 s, until the fail
condition is cleared.
Link failure triggers FDI/AIS packets
insertion in Tunnel 1
SDH link 1 NE3 SDH link 2
NE1 NE2
ETH ETH
T- MPLS
Tunnel 1 Tunnel 1
MEP MEP
FDI/AIS Tunnel the receiving MEP extracts the

packets insertion FDI/AIS packets and detect
the FDI/AIS alarm condition

Upon detection of a signal fail condition, the system start the transmission of FDI/AIS packets
periodically with MEG Level set to 0 for T-MPLS and MEG Level set to 7 for MPLS-TP for each pass-
through tunnel that uses that server layer.
The system provides, optionally, the insertion of FDI/AIS packets also in case of DDM-SD, (i.e. when the
degraded status of the line is detected monitoring the optical power at the ingress of SFP/XFP)

Issue 01
FDI OAM format

For backwards compatibility, the system inserts in the last two bytes the BIP-16, calculated over the FDI
PDU frame

Issue 01
AIS OAM format

The system inserts in bit 3-1 of Flags the fixed Period = 0b100, the other bits of Flags are “0”; in the TLV
offset field the fixed value 0d00 is inserted.

Issue 01
APS (Automatic Protection Switching)
APS carries information about the protection architecture, the remote
node condition, the signal that the near end requests to be carried over
the protection path and the signal that is bridged onto the protected
path.
APS packets are inserted periodically every 5 sec in normal conditions;

in case of status change of the protection end point 3 APS packets are
inserted every 3.3 ms


Issue 01
Two-way T-MPLS Delay Measurement
Two-way T-MPLS / MPLS-TP Delay Measurement (DM) provides means to

monitor the network packets delivery performances. It is performed on
LSP tunnels.
Two-way Delay Measurement is performed to monitor packet delay
measurement and packet Delay Variation Measurement between two
active T-MPLS / MPLS-TP MEPs. It is performed by sending periodic DM
packets and receiving DM packets from the peer MEP during the
diagnostic interval.
The system supports both “on demand” and “proactive“ DM
(proprietary solution).
For the On-Demand tool, the two-way function is performed by sending
periodic DMM (Delay Measurement Message) packets and receiving the
corresponding DMR (Delay Measurement Response) packets from the
peer MEP during the diagnostic interval. The system provides as output
a file containing the time stamps and the two-way packet measured
delay

10G cards support up to 512 DM instances, 20G cards support up to 1024 DM instances, shared between
ETH and T-MPLS/MPLS-TP, on Demand and Proactive..

Issue 01
Two-way T-MPLS Delay Measurement [cont.]
For Proactive tool, the DMM and DMR packets are sent periodically if
the tool is enabled; PM counters are provided as output.
When a MEP is enabled to generate DMM packets, it periodically sends
DMM packets to its peer MEP in the same MEG and also expects to
receive DMR packets from its peer MEP in the same MEG.
If the MEP is not enabled to receive that DMR, the packet is dropped.
When the transmission of T-MPLS / MPLS-TP DMM is enabled
automatically also the reception of DMR is enabled.
The maximum tolerated delay between one DMM and its corresponding
DMR is 10 seconds. If the DMR packet is received beyond this interval, it
shall be dropped
It is possible to run one or more (up to 8) on demand delay
measurement tool on each MEP, differentiated by the PHB.
Proactive and On-demand DM tools can coexists on the same MEP, but is
not possible to enable both tools for the same PHB at the same time.


Issue 01
Two-way T-MPLS Delay Measurement [cont.]
The period for the generation of the DMM packets (1sec, 10sec,
1minutes, 10minutes). The default value for period is 1 minute.
The packet length for T-MPLS case is 41 (standard packet, considering
37 bytes for DM PDU + 4 bytes for OAM header) while for MPLS-TP case
is 45 (standard packet, considering 37 bytes for DM PDU + 4 bytes for
ACH + 4 bytes for GAL).
In case of On Demand tool, we have the following parameters:
Start date and time: it has to be later or equal to the current system time.
The default value is the current local time.
End date and time: it has to be greater than start date and time. The default
value is the current local time + 1 min.
Packet number: can be entered as alternative to the start and end time


Issue 01
Two-way T-MPLS Delay Measurement: processing
The system calculates the two-way Round Trip Packet Delay according to
the following definition:
Packet Delay = (Rx Time Stamp b – Tx Time Stamp f) – (Tx Time Stamp
b – Rx Time Stamp f) where:
Tx Time Stamp f = Time stamp at the time of transmitting DMM packet
Rx Time Stamp f = Time stamp at the time of receiving DMM packet
Tx Time Stamp b = Time stamp at the time of transmitting DMR packet
Rx Time Stamp b = Time stamp at the time of receiving DMR packet


Issue 01
Two-way T-MPLS Delay Measurement: processing [cont.]


Issue 01
DMM T-MPLS OAM frame
• The system inserts in the TLV offset field the value 0x20 (the length of
the payload used for time stamps is 32 bytes).
• The system inserts in the TxTimeStamp_f field the time stamp at the
time of transmitting the DMM packet


Issue 01
DMR T-MPLS OAM frame
• The system inserts in the Function Type (FT) field the fixed value 0x2E
(T-MPLS DMR OAM); the other bytes are copied from the DMM received
packet (Version = 0x00, Flag = 0x00, TLV offset = 0x20)
• The system copies in the the TxTimeStamp_f field the TxTimeStamp_f
received in the DMM packet and inserts two additional time stamps: in
the RxTimeStamp_f field the time stamp at the time of receiving the
DMM packet and in the TxTimeStamp_b field the time stamp at the
time of transmitting back the DMR packet.
• In the received DMR packet also the RxTimeStamp_b information is
added defining the time at the reception of DMR packet, before
sending the packet to the microprocessor for the processing.


Issue 01
DMM MPLS-TP OAM frame
• The system inserts in the Flag field the fixed value 0d00 and in the TLV
offset field the value 0d32 (the length of the payload used for time
stamps is 32 bytes).
• The system inserts in the TxTimeStamp_f field the time stamp at the
time of transmitting the DMM packet


Issue 01
DMR MPLS-TP OAM frame
• The system inserts in the OpCode field the fixed value 0d46 (MPLS-TP
DMR OAM); the other bytes are copied from the DMM received packet
(Version = 0d00, Flag = 0d00, TLV offset = 0d32)
• As in the T-MPLS case, the system copies in the the TxTimeStamp_f
field the TxTimeStamp_f received in the DMM packet and inserts two
additional time stamps: in the RxTimeStamp_f field the time stamp at
the time of receiving the DMM packet and in the TxTimeStamp_b field
the time stamp at the time of transmitting back the DMR packet.
• In the received DMR packet also the RxTimeStamp_b information is
added defining the time at the reception of DMR packet, before
sending the packet to the microprocessor for the processing.


Issue 01
Dual-ended proactive T-MPLS Synthetic Loss Measurement (SLM)
T-MPLS / MPLS-TP Synthetic Loss Measurement (SLM) performs packet

loss calculation based on T-MPLS / MPLS-TP OAM packets counters (i.e.
CV / CCM packets). It supports packet loss measurement between peer
MEPs for p2p services (VPWS).
10G cards support up to 128 SLM instances while 20G cards support up
to 256 SLM instances, shared between ETH and T-MPLS / MPLS-TP.
In rel.4.0, the system supports Proactive Dual Ended Synthetic Loss
Measurement only, for PM and fault management purposes (DEG alarm).
Periodic CV / CCM packets are sent by each MEP with SLM configured to
its peer MEP and, upon termination of received packets, near-end and
far-end packet loss measurements are performed at the same time:
Far-end SLM is referred to the remote node (peer MEP) and it is associated
with egress data packets direction of the local node
Near-end SLM is referred to the local node and it is associated with ingress
data packets direction of the local node.
It is possible to run one proactive LM tool on each MEP
The system sets the LM Mode bit in the Flags byte of CV / CCM packet
to “1” when the SLM functionality is enabled

Issue 01
Proactive SLM processing
When in a MEP, the SLM tool is enabled, the system periodically

transmit CV / CCM packets with the following information elements:
TxFCf: Value of the local CV / CCM counter (TxFCl) at the time of
transmission of the CV/CCM frame.
RxFCb: Value of the local CV / CCM counter (RxFCl) at the time of reception
of the last CV / CCM frame from the peer MEP.
TxFCb: Value of TxFCf in the last received CV / CCM frame from the peer
MEP.
When in a MEP the SLM tool is enabled, at the rx side, the system
calculate the near end and far end loss measurements, using the
following values:
Received CV / CCM frame’s TxFCf, RxFCb and TxFCb values and local counter
RxFCl value at time this CV / CCM frame was received. These values are
represented as TxFCf [tc], RxFCb [tc], TxFCb [tc] and RxFCl [tc].


Issue 01
Proactive SLM processing
Previous CCM frame’s TxFCf, RxFCb, and TxFCb values and local counter
RxFCl value at time the previous CCM frame was received. These values are
represented as TxFCf [tp], RxFCb [tp], TxFCb [tp] and RxFCl [tp].
The formulas are:

Far End Frame Loss = (TxFC_b [tc] – TxFC_b [tp]) - (RxFC_b [tc] – RxFC_b [tp])
Near End Frame Loss = (TxFC_f [tc] – TxFC_f [tp]) - (RxFCl [tc] – RxFCl [tp])
where:
Tc is the reception time of the current frame.
Tp is the reception time of the previous frame.


Issue 01
Proactive SLM processing Far End packet loss


Issue 01
Proactive SLM processing: Near End Packet loss


Issue 01
Blank Page


Issue 01


Issue 01
Proactive DM OAM creation
1. Select (T)MPLS Tunnel Management
2. Click on Create Head/Tail Tunnel to activate

the DM OAM in a new tunnel or Search to
activate the DM OAM in an existing tunnel

Issue 01
Proactive DM OAM creation (on existing tunnel)
3. Select a tunnel
5. Fill in the OAM parameters See next page


Issue 01
Proactive DM OAM creation (on a existing tunnel) [cont.]
6. Set to ENABLE 7. Choose T-MPLS or MPLS-TP protocol
8. Insert the MEG 9. Insert the MEP ID

ID (a string)
10. Insert the

expected MEP
12. Set to ENABLE
13. Choose the DM period
14. Click on Save

Operation And Maintenance:

MEP: set to ENABLE
MEG ID: specifies the MEG Identifier (a string)
OAM PHB Profile: specifies the PHB profile for OAM packets
CV Rx: set to ENABLE: it is the capability to detect the Loss of Continuity (LOC) alarm
CV Period: specifies the period of CV packet transmission
MEP ID: specifies the transmitted MEP (0-8191). Must be unique inside MEG ID; must be different from
the EXP MEP ID
CV PHB: specifies the CV packet transmission for PHB profile
CV Tx: it enables the transmission of CV packets
EXP MEP ID: specifies the expected MEP value
Proactive DM period: specifies the period of DM OAM packet transmission
Proactive DM PHB: specifies the PHB profile for DM OAM packets
Proactive DM Payload Length: specifies the length of DM OAM payload

Issue 01
Proactive DM OAM results
From the OAM configuration view
1. Click on PRODM Performance Monitoring


Issue 01
Proactive DM OAM results [cont.]
2. Select PM List tab
3. Set to ON
4. Choose the Location

and the Time Period
5. Click on Save


Issue 01
Proactive DM OAM results [cont.]
6. Select PM Report tab

7. Click on Retrieve


Issue 01
On Demand DM OAM creation


Issue 01
On Demand DM OAM creation (on existing tunnel)
3. Select a tunnel
5. Fill in the OAM parameters
See next page


Issue 01
On Demand DM OAM creation (on a existing tunnel) [cont.]
6. Set to ENABLE 7. Choose T-MPLS or MPLS-TP protocol
8. Insert the MEG 9. Insert the

ID (a string) MEP ID
10. Insert the

expected MEP
11. Set to DISABLE
12. Click on Save


MEP: set to ENABLE
the EXP MEP ID
CV Tx: it enables the transmission of CV packets

Issue 01
13. Select (T)MPLS OAM Management

Delay Measurement Tool
14. Click on Create


Issue 01
16. Click on Search

15. Click on Create
17. Select the tunnel
18. Choose the

Sender type
It is possible to specify the “Frame

between 64 to 1500 bytes and with the
option “Random” (in this case DMM
packets are generated with polynomial
19. Click on Save generator).

Issue 01
On Demand DM OAM activation
2. Tick the box

and click
on Start
Check that the new status indicates ENABLE


Issue 01
On Demand DM OAM results
1. With your mouse select and right click
2. Select Open Link in New Tab
3. Choose Open with option
4. Click on OK
The DM results appear in the window


Issue 01
10.3 SLM configuration


Issue 01
Proactive SLM OAM creation


Issue 01
Proactive SLM OAM creation [cont.]
3. Select a tunnel
See next page

5. Fill in the OAM parameters


Issue 01
Proactive SLM OAM creation [cont.]
7. Choose T-MPLS or MPLS-TP protocol
6. Set to ENABLE
8. Insert the MEG ID 9. Insert the MEP ID

(a string)
10. Insert the
expected MEP
12. Set to ENABLE
11. Set to SLM CV
13. Choose the CV period

15. Set ENABLE to see
the RDI status
16. Click on Save
Only this three values
14. Choose the packet Loss Probability are accepted


Issue 01
Proactive SLM OAM results
From the OAM configuration view
1. Click on PROLM Performance Monitoring


Issue 01
Proactive SLM OAM results [cont.]
2. Select PM List tab
3. Set to ON
4. Choose the Location

and the Time Period
5. Click on Save


Issue 01
Proactive SLM OAM results [cont.]
6. Select PM Report tab
7. Click on Retrieve The new Tunnel appears in the window


Issue 01
Blank Page


Issue 01
11 T-MPLS Protection (FFP)


Issue 01
Protection architecture
In TSS320 rel 4.1 the 1:1 linear trail architecture for Tunnel is
supported
according with ITU-T G.8131:
bidirectional switching is supported
1-phase APS protocol is supported
revertive switch only is implemented


Issue 01
Protection requirements
To implement T-MPLS Tunnel protection it is required to create the Fast Facility
Protection (FFP) Group, constituted by a Protected (Main) Unit and a Protecting (Spare)
Unit.
Up to 4K Protection Groups are supported per node; up to 4K Protection Units are
supported per 10 Gb card.
It is requested that the two tunnels, that assume the role of Main Unit and Spare Unit,
have been already created and activated.
It is required that bidirectional MEPs are created and activated for both tunnels in the
Protection Group.
PWs can be previously mapped only in the Tunnel that becomes the Protected one (no
PWs mapped on the the tunnel that assumes the role of Protecting Unit)
Tunnel 1 (M AIN )
protection group
T-PW T-PW
protected unit
protecting unit
Tunnel 2 (SPAR E)


Issue 01
Procedure for 1 : 1 tunnel protection creation
Step Action
1 Create two T-MPLS tunnels (with OAM)
2 Create the FFP
3 Create the PW and associate it to the “Main”
4 Create the EVPL Service
It is supposed that the trainee can perform the steps 4


Issue 01
Step 1: create T-MPLS main tunnel


Issue 01
Step 1: create T-MPLS main tunnel [cont.]
4. Expected label for incoming segment 5. Transmitted label for outgoing segment
3. Select the NNI MPLS port
6. Configure OAM resources (see Notes)


MPLS Port: select the end point of the T-MPLS main tunnel
Ethernet

MEP: set to ENABLE
the EXP MEP ID
CV Tx: set to ENABLE: it enables the transmission of CV packets

Issue 01
Step 1: create T-MPLS spare tunnel


Issue 01
Step 1: create T-MPLS spare tunnel [cont.]
4. Expected label for incoming segment 5. Transmitted label for outgoing segment
3. Select the NNI MPLS port
6. Configure OAM resources (see Notes)


MPLS Port: select the end point of the T-MPLS spare tunnel
Ethernet

MEP: set to ENABLE
the EXP MEP ID
CV Tx: set to ENABLE: it enables the transmission of CV packets

Issue 01
Step 1: Configure and activate the Tunnels
4. Set to ON
3. Assign the TD
parameters
5. Click on Save


VT Head: select, in the list, the Virtual Transport that will be associated to the Tunnel (only active VT

Issue 01
Step 2: Create FFP (Fast Facility Protection)
This option allows to create the Protection
Group to specify Working and Protecting Tunnels
1. Select Protection 1:1 Tunnel Protection

2. Click on Create


Issue 01
Step 2: Create FFP (Fast Facility Protection) [cont.]
3. Click on Select
5. Click on Apply & Exit
4. Select the Working and the protecting Tunnel

Layer: the value is fixed to TUNNEL

Revert Time: specify the Wait to Restore time after the alarm is cleared (0-12 min.)
Protection Type: the value is fixed to APSBIDIR (bidirectional)
Revertive: the value is fixed to Y
Hold Off Time: is specifies the time, to wait, after failure detection, before activating the protection
(0 – 10000 msec.)
APS PHB: Specifies the APS PHB profile for the FFP group. The values are EF, HIGH2, AF21, AF22, AF41,
AF42, DE-G, and DE-Y

Issue 01
Step 2: Create FFP (Fast Facility Protection) [cont.]
6. Set the protection parameters
7. Click on “Save” to confirm

Layer: the value is fixed to TUNNEL

Revert Time: specify the Wait to Restore time after the alarm is cleared (0-12 min.)
Protection Type: the value is fixed to APSBIDIR (bidirectional)
Revertive: the value is fixed to Y
Hold Off Time: is specifies the time, to wait, after failure detection, before activating the protection
(0 – 10000 msec.)
APS PHB: Specifies the APS PHB profile for the FFP group. The values are EF, HIGH2, AF21, AF22, AF41,
AF42, DE-G, and DE-Y

Issue 01
1. Select (T)MPLS PseudoWire Management
2. Click on Create Head/Tail Pseudowire


Issue 01
Step 3: Create the Head Pseudowire [cont.]
3. Select the main tunnel
4. Expected label for

incoming PW
5. Transmitted label for outgoing PW


Port: select the Tunnel Segment configured as “Main”

Control Word: it enable/disable the capability to insertion/stripping of the Control Word, associated to
the PW segment (cfr. IETF RFC 4385)
User Name: (optional) specify a PW User name
Out Label: specify the transmitted label for the outgoing PW (16 – 1048575)

Issue 01
Step 3: Configure and activate the Pseudowire
1. Select a VT (or leave the default)

Optional
3. Set to ON

4. Click on Save

Identifier: (optional) specify a string that will be associated to the PW

VT Head: select, in the list, the Virtual Transport that will be associated to the PW (only active VT

Issue 01
Protection management
This option allows to get information about the
configured FFP group and the protection status
1. Select Protection 1:1 Tunnel Protection
2. Click on Search
Switch Position:
•WKG Current Request:
•NR: No Request
•PROTN •WTR: Wait To Restore
To delete a FFP, tick the
•SF: Signal failure
•SF-P: Signal failure on protecting
•MAN: Manual command
•FRCD: Forced
•LOCKOUT: Lockout

Issue 01
Protection management [cont.]
3. Select the FFP
4. click here to modify the

protection parameters
5. Click on Save


Issue 01
Protection switch commands
1. Select the FFP

Before performing a new command,
with lower priority, it s necessary to
“release” the previous one
2. Specify the Switch Command
3. Specify the destination (only for Manual command)
4. Click on Operate Protection to activate

FRCD (Forced) :
Force the system to switch to the Protecting channel
Note: Signal Failure (SF) on the protecting section overrules the forced switch.
if there is a SF (i.e. LOS) on the Protecting Port then ‘Force to Protecting’ will not work.

LOCKOUT: highest priority.

Force the system to use the Working channel
MAN (Manual): lowest priority.

switches the channel to the selected section, Working (WKG) or Protection (PROTN) according to
the user selection, unless a failure condition exists on the protection section or an equal or higher
priority switch command is in effect.

Issue 01
12 Single Node Interconnection for ring closure
with TSS-40


Issue 01
12 Single Node Interconnection for ring closure with TSS-40
Introduction
This feature is used to configure the single node interconnection for

ring closure with TSS-40. With this feature you can configure the ring
closure using the same “In Label” for the working tunnel and
protecting tunnel. TSS-320 forwards the incoming traffic towards both
the working and protecting tunnels, while the TSS-40 selects one of the
two ways according to the failure condition


Issue 01
Working and protecting tunnel creation
For the working tunnel creation refer to “Section 3 - Module 4 -

Configure Head/Tail Node” chapter
As regard the protecting tunnel, create the tunnel with the same In
Label of the working tunnel, set Add Group = TRUE (Fig. 1) and
configure the traffic descriptor parameters (PIR, CIR, CBS, PBS) greater
or equal respect to the value inserted in the working tunnel (Fig. 2)
Insert “In Label” of the protecting tunnel

Fig. 1 equal to “In Label” of the working tunnel Set Add Group: TRUE


Issue 01
Working and protecting tunnel creation [cont.]
Fig. 2
The traffic descriptor parameters of the protecting

tunnel must be greater or equal to the working tunnel


Issue 01
Tunnel group configuration
1. Select (T)MPLS Tunnel Group Management
2. Click on Create Tunnel Group
3. Click on select to choose the working tunnel


Issue 01
Tunnel group configuration [cont.]
4. Click on Search All
The two tunnels must have

5. Select the working tunnel the same In Label
The value for the working

tunnel must be = FALSE
6. Click on select to choose the protecting tunnel


Issue 01
Tunnel group configuration [cont.]
7. Click on Search All
8. Select the protecting tunnel
The value for the protecting

tunnel must be = TRUE
9. Click on Save
The new Tunnel Group appears in the window


Issue 01
Tunnel group deletion
1. Select (T)MPLS Tunnel Group Management
2. Click on Search to filter the Tunnel

Group Protection details based on
the selected parameter values
3. To delete a Tunnel group protection,

tick the box and click on Delete


Issue 01
13 MAC Flushing propagation

NE Operation Operator Interface-T-MPLS & MPLS-TP features Section 3 Module 4 Page 231

Issue 01
Introduction
The Alcatel Lucent 1850 TSS-320 and TSS-160 supports MAC “Black-
Hole” function with automatically MAC table flushing. This means
flushing of MAC table entries on a remote NE upon network failure
event thus preventing traffic forwarding through a black hole port until
MAC aging time is expired and a new learning process takes place. MAC
“Black Hole” forwarding prevention applies in all network
configurations where an interconnection function is involved for a ring
closure or a protected access.
Typical application scenarios:
Interconnection with ERP (Ethernet Ring Protection) ring supporting RPS (Ring
Protection Switching) OAM packets
Interconnection with CE supporting 1:1 port protection
The Alcatel Lucent 1850 TSS-320 and TSS-160 supports:
Local MAC @ table flushing upon a LOS has been detected
”MAC flushing indication” generation, upon a LOS has been detected
”MAC flushing indication” forwarding, when receiving a failure detection
from remote node

Issue 01
Local MAC @ table flushing action upon detection (snooping) the ”MAC
flushing indication” coming from remote nodes
This allows to perform, both locally and remotely, are learning that
allows to avoid the “MAC black holing”. The equipment supports ”MAC
flushing propagation indication” associated with TMPLS networks (in
case of both VPLS and HVPLS schemes). The flushing action must be
completed within 250ms.
When the ”MAC flushing indication” is configured and enabled, the
system is able to:
Detect the ”MAC flushing indication” coming from remote nodes (snooping)
Propagate the received ”MAC flushing indication” to other nodes
Generate the ”MAC flushing indication” in front of failures locally detected.
The following optimization applicable to single node scenarios is
supported
”MAC flushing indication” upon a local LOS has been detected, is not sent in
case of single node interconnection, because of there is no need of
reconvergence of the other nodes
”MAC flushing indication” is not forwarded when receiving a failure detection
from remote node.

Issue 01
Dual node interconnection (DNI) with ERP ring
The following picture shows the reference scenario. T-MPLS nodes

deliver traffic in ERP (Ethernet Ring Protection) ring via VPLS instances,
subjected to MAC learning/forwarding process. T-MLS nodes do not
participate in ERP ring, but ERP R-APS packets are tunneled via PW in
the ring closure performed by two T-MPLS nodes.


Issue 01
Dual node interconnection (DNI) with failure in ERP ring
Assuming traffic direction from node A to node B, in case of failure in

the ring (see picture below), the ERP protocol performs, via OAM
packets, automatic flush action on MAC table of the nodes along the
ring, but not on T-MPLS nodes.


Issue 01
Dual node interconnection (DNI) with failure in ERP ring [cont.]
This results in a “black hole” problem (traffic loss) because traffic is

still forwarded on the “old” path from T-MPLS node (1) to T-MPLS node
(2) and not through T-MPLS node (3), since the first equipment is not
aware of the failure (its MAC table is not flushed or updated).
When the “MAC flushing indication” for the specific VPLS instance is
configured for the T-MPLS nodes, the following behavior is expected:
When the ERP redundancy protection mechanism occurs, the ERP node
detecting the failure sends 3 consecutive R-APS packets
T-MPLS nodes outside the ring perform “MAC flushing indication” snooping
action (getting the R-APS packets) and Packet propagation to the other nodes
in the meshed network connected via PW. This allows flushing the MAC table
for the involved virtual switching instance(s).
“MAC flushing indication” is not forwarded towards the user (UI)
interfaces.


Issue 01
Single node interconnection (SNI) with failure in ERP ring
In case of failure detected inside the ring, T-MPLS node has to detect
the “MAC flushing indication” packets (snooping) and to provide “MAC
@ table flushing” on all cards for the MAC @ learned behind that port
from which the “MAC flushing indication” has been received for all
VPLS instances on which the “MAC flushing indication” has been
enabled.
The “MAC flushing indication” is not forwarded towards the user (UI)
interfaces.
The differences respect the DNI are:
The configuration of the tunneling for the APS message to close the ERP ring,
is performed with dedicated VPLS instance, while in case of dual node it is
performed via dedicated PW (P2P)
The “MAC flushing indication” is not sent towards the other nodes in the
meshed network (towards PW).


Issue 01
Example 1: MAC flushing mechanism: Initial phase
MAC@ lists are initially empty. C A

MAC Learning
MAC@ A A -> B ETH MAC Learning
A B transmission
MAC@ A
A starts to send pkts to B. MAC@B is
VSI VSI
unknown and those pkts are flooded
into the E-LAN.
MAC@A is progressively learned
node by node as pkts pass through and
MAC@ lists get filled.
VSI
ETH MAC@ A
MAC Learning
B


Issue 01
Example 1: MAC flushing mechanism: Normal functioning
B A response C A
Now MAC@ lists are filled in MAC@ A ETH
(MAC@A is known). Pkts sent by B MAC@ A
toward A are forwarded as unicast VSI VSI
packets. MAC@ B
MAC@B is also learned MAC Learning
by nodes as pkts pass through
VSI
MAC@ B
MAC Learning ETH MAC@ A
B B -> A


Issue 01
Example 1: MAC flushing mechanism: MAC@ flushing and MAC withdrawal message
LOS occur at port A A

MAC@ learned are locally flushed.
C MAC Flush
ETH MAC Flush
Remote members of the E-LAN are MAC@ A
alerted via MAC@ withdrawal messages. MAC@ A
At the reception of MAC withdrawal VSI VSI
message, each node performs MAC MAC@ B
MAC@
flushing for clearing its MAC@ list. withdrawal
VSI
MAC@ B
ETH MAC@ A
MAC Flush
B


Issue 01
Example 1: MAC flushing mechanism: Forwarding (after LOS) w/o MAC flushing/withdrawal
MAC Learning
C A (new position) C MAC@ C ?
Not performing MAC flushing MAC@ A ETH
C -> A
nodes will hold MAC@ lists than MAC@ A
containing not up to date MAC@ C VSI VSI
information. MAC Learning
MAC@ B
C will send packets to A but
those packets will flow in
unicast mode toward the known
A address. However in the
meanwhile A has silently moved
to another location.
A VSI
MAC@ B ETH MAC@ A

B


Issue 01
Example1: MAC flushing mechanism: Forwarding (after LOS) w/ MAC flushing/withdrawal
C A (new position)
MAC@ lists are empty as a MAC Learning
C MAC@ C
consequence of flushing.
MAC@ A ETH
MAC@C is unknown and those C -> A
pkts are flooded into the E-LAN. MAC@ A
MAC@A is progressively learned MAC@ C VSI VSI
MAC Learning
node by node. MAC@ B
A is now correctly reached.
MAC Learning
MAC@ C
A VSI
MAC@ B ETH MAC@ A

B


Issue 01
MFP topology creation
1. Select Data MAC Flushing Propagation
2. Click on Create
4. Set to Active
3. Insert a label
5. Choose the topology
The parameters of this window

depend on the topology

The window provides the following parameters:

- MFP Topology Label: The MFP Topology Instance User Label. The default is no label.
- Status: Provides the status of the MAC Flushing topology. The supported values are:
Active: Activates a MAC Flushing topology instance previously created.
Not in service: Deactivates a MAC Flushing topology instance by the Administrator.
Note:
1. Activation of the related topology ports entries depends on the Dual Node/Single Node
interconnection options.
2. The default status is active.
- Interconnection mode: The management plane operation for the MAC Flushing topology. The supported
values are:
Dual node interconnection: a topology configuration where two nodes are interconnected to a ring
with a single IC port.
Single node interconnection: a topology configuration where a single node is connected to the ring
with a couple of IC ports.
Remote node interconnection: Ring Automatic Protection Switch: ETH OAM control packets of
ERP(S) protocol triggering automatic MAC table flushing.
Note:
1. This field can not be modified once created.
- Service port #1: Provides the option of having MAC Flushing on a port. Note: This field cannot be
modified once created.

Issue 01
MFP topology creation [cont.]
6. Click on Select
7. Select the port
8. Click on Save to Save the MAC

Flushing topology or Save and
Continue to save the MAC flushing
topology and create a new one


Issue 01
MFP Instance creation
2. Select the MAC flushing Instance criteria

from the drop-down menu if available or
leave the default selection All Instance
3. If the MAC Flushing Criteria is

4. Click on Create selected, enter the VLAN Id.

If the MAC Flushing Criteria is selected, enter the VLAN Id. If the default MAC Flushing Instance criteria is
selected, this field is not editable.

Issue 01
MFP Instance creation [cont.]
4. Select the topology if not already specified
in the previous page (point #2)
5. Insert a label 6. Insert the VLAN Index

the VPLS Instance

The MEP Instance Parameters window, provides the following parameters:

User Label: The User label for the MFP Instance.
VLAN Index: The VLAN Index Id between 1 and 4094.
ERP Protocol Version: The MAC flushing packets (R-APS packets) ERP Protocol version.
The supported ERP protocol versions are:
V1 plus
V2 (default)
R-APS PDU Priority enable: PCP bits of the R-APS PDU flushing packets. The default PCP value is 7
(highest priority).
Ring R-APS PDU MEG Level: The MEB level of the R-APS PDU flushing packets. The supported value
range is 0 to 7 (default)
R-APS PDU Drop enable: DEI bit control of the R-APS PDU flushing packets. The supported values
are:
True: enabled
False: disabled (default)
Asap User Label: The ASAP reference object for a MAC Flushing table Instance.
Enable/Disable MAC Flushing: Enable or disable MAC flushing control of a MAC flushing instance. The
supported values are:
True: enabled
False: disabled (default)
VPLS Instance: Virtual Private Line Service: ELAN service, emulated by T-MPLS nodes. The ELAN
service From and To values are to be specified as search criteria.

Issue 01
MFP Instance deletion
2. Click on Search
3. To delete a MFP Instance, tick the box and click on Delete


Issue 01
MFP topology deletion
2. Select a MFP topology
3. Set to notInService
4. Click on Save


Issue 01
MFP topology deletion [cont.]
5. To delete a MFP topology, tick the box and click on Delete
6. Click on Yes to confirm the operation


Issue 01
Blank Page


Issue 01


Issue 01
Introduction
This command starts the preparation of the MAC File Collection. The
mechanism of MAC File Collection is an efficient way of collecting MAC
addresses of the entire NE in a single file.
After the start, the status of the collection will become INPREP (in
preparation).
A previously prepared file collection will be no longer available.


Issue 01
Configuration
1. Select Data FDB Operations MAC File Collection
See next page


Issue 01
2. choose the parameters
3. Click on Start Collection


Issue 01
Results
5. Wait the READY status and then click on the file
6. Click on Open with
7. Click on Ok
8. Click twice the file


Issue 01
Results
The results appear in the window


Issue 01


Issue 01
Introduction
In T-MPLS or MPLS-TP, the system supports MAC Access Control List

management at ingress UNI ports, ”on per port basis”, to allow the
selective 'forwarding‘ / 'dropping‘ of all the frames except those ones
matching the values stored in the MAC ACL list.
A single MAC ACL list is supported for each port, so that MAC ACL List is
configured on port basis.
An ACL is an ordered list of “permit” and “deny” statements that
determine whether a particular packet will be forwarded or dropped.
The order of entries (rules) in a ACL is important because the controller
stops testing conditions in the statement after the first match. The
frames that don’t match any rule are discarded.


Issue 01
Configuration
1. Select Data MAC Access Control List
2. Click on Create
3. Write the ACL Name
4. Click on Send
The new ACL appears in the window


Issue 01
5. Select the ACL 6. Click on editACE
7. Click on Create
8. Choose the execution order
9. Click on Send


Issue 01
10. Fill in the fields
11. Click on Save or Save&exit


Issue 01

where you want to
assign the ACL profile
14. Click on Select
16. Click on Associate
15. Choose the ACL profile


Issue 01
Disable ACL

where you want to
disable the ACL profile
3. Click on De-ssociate


Issue 01
End of Module
Operator Interface-T-MPLS & MPLS-TP features


Issue 01
35
Section 3
NE Operation
Module 5
Operator Interface-ATM features
Issue 01
1850 TSS-320 & 1850 TSS-160

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

Issue 01
Blank Page

NE Operation Operator Interface-ATM features
Document History

Issue 01
Module Objectives
• Create ATM to ATM CXC

• Configure the ATM Cell Concatenation
• Create ATM over PW CXC


Issue 01


Issue 01
Table of Contents
Page
1 Introduction 7
2 ATM to ATM CXC 15
3 ATM Cell Concatenation 33
4 ATM on PW CXC 41


Issue 01


Issue 01
1 Introduction


Issue 01
1 Introduction
Introduction
ATM flow are classified

on the basis of VPI/VCI ATM
values and mapped on
selected PW
TSS320
T-MPLS
ATM over SDH
ATM on PW
ATM ATM ATM

SDH PW
TU
Eth
ATM on PW ATM
ATM over VC4 VCI/ VPI
VCI/VPI
VCI/ VPI PW/TU
VC4 ETH


Issue 01
1 Introduction
4 bytes
Tunnel Header
PW Header
ATM Control Word

OPTIONAL
12 bits 16 bits 3 bits 1 bits
ATM Service Payload VPI VCI PTI CLP
ATM header
(4 bytes ATM header
+ 48 byte ATM payload)
52 bytes
one or more ATM concatenated cells
… length = m x 52 byte + 4 byte (Control Word)

min 56 bytes


Issue 01
1 Introduction
ATM on PW CXC

VPI/VCI swapping is supported both at the ingress NE and at the egress NE of the T-MPLS network, for
interworking scenarios:
Ingress:
VPI/VCI translation = capability to change either or both the fields VPI and VCI of an ATM packet,
coming from the ATM attachment circuit
VPI/VCI translation has to be applied on <incoming port, ATM flows> basis that is on ATM (=ETS)
flow basis
Egress:
VPI/VCI translation = capability to change either or both the fields VPI and VCI of an ATM packet,
carried by a T-MPLS circuit, while delivering out to the ATM attachment circuitfrom the T-MPLS
network
VPI/VCI translation has to be applied on <PW, VPI/VCI > basis

Issue 01
1 Introduction
ATM on PW CXC [cont.]
The value used in the VPI/VCI classifier can be:

•A single VPI/VCI value
•A range of VPI/VCI values


Issue 01
1 Introduction
PW on ATM CXC [cont.]


Issue 01
1 Introduction
ATM to ATM CXC
ATM to ATM cross connection
The system is required to support a p2p ATM internal (inside NE)

connection, between an ATM attachment circuit, referring to ATM ports
on the same ATM card or different ATM cards. The VPI/VCI translation
can be performed either at the ingress or at egress point
Egress direction
VPI/VCI ATM port

(VC4)


Issue 01
Blank Page


Issue 01
2 ATM to ATM CXC


Issue 01
2 ATM to ATM CXC
Procedure for one node
Step Action
1 Create SDH CXC between ATM port 1 and the SDH port
2 Create SDH CXC between ATM port 2 and the SDH port
3 Create the ATM traffic descriptor

create unidirectional ATM connection between the ATM port 1 and
4
ATM port 2. Configure the TD, ingress VPI/VCI and egress VPI/VCI
It is supposed that the trainee can perform the steps 1, 2.

For the steps 1 and 2, please refer to session: “S03M02_S3_NE Operation
M2_Operator_Interface_SDH features” pg. 15


Issue 01
2 ATM to ATM CXC
Test bench
ATM port 1 Classification ATM port 2

VPI = 1000 on port and VPI = 2000
VCI = 500 ATM VPI/VCI VCI = 500
CLASSI
FIER
port B
ATM XC
port A
IN OUT
AU4
AU4
SDH
SDH
FLOW FLOW
Traff.
SDH XC Descr.
SDH XC
Ingress Traffic Descriptor (CBR):
PIR: 50 Mb/s
CIR: 50 Mb/s
PBS: 1000 bytes
CBS: 1000 bytes

Issue 01
2 ATM to ATM CXC
2. Click on Create
3. Tick the box 4. Specify the ATM Class
see next slide


Issue 01
2 ATM to ATM CXC



Issue 01
2 ATM to ATM CXC



Issue 01
2 ATM to ATM CXC
1. Select a TD
2. Tick the box



Issue 01
2 ATM to ATM CXC
Step 4: Configuration
1. Select Connection ATM P2P XC
2. Click on Create


Issue 01
2 ATM to ATM CXC
Step 4: Configuration [cont.]
ingress port of the connection
4. Select the ATM port


Issue 01
2 ATM to ATM CXC
egress port of the connection


Issue 01
2 ATM to ATM CXC
7. Select the ATM TD


Issue 01
2 ATM to ATM CXC
8. Choose the values

for the swapping
(optional)
VPI and VCI are the values

for the ATM classifier
9. Click on Save


Issue 01
2 ATM to ATM CXC
Traffic Descriptor analisys


Issue 01
2 ATM to ATM CXC
Ingress flow and classifier analisys
1. Select an InFlow
2. Click on View to display or modify

3. Click on Search


Issue 01
2 ATM to ATM CXC
Ingress flow and classifier analisys [cont.]
Click on Create to add

a new Classifier
4. Choose the Classifier
To delete a Classifier, tick the

box and click on Delete.


Issue 01
2 ATM to ATM CXC
ATM Classifier creation
1. Click on Create to add

a new Classifier
2. Insert the VPI/VCi values
1. Click on Save & continue or Save & exit


Issue 01
2 ATM to ATM CXC
Egress Flow analisys
You can modify the configuration and

the values of the swapping

Issue 01
Blank Page


Issue 01
3 ATM Cell Concatenation


Issue 01
Introduction
The system supports the N to one mapping method, where one or more
ATM connections (VCCs or VPCs) are mapped to one PW; ATM header is
copied unaltered in the T-MPLS packet.
The system supports both single and multiple connection deployment
models. The single connection deployment model is implemented using
the N-to-one encapsulation method, with N = 1.
The system maps one cell ATM into one T-MPLS packet, in case of no
cell concatenation mode


Issue 01
The system supports cell concatenation mode, as per RFC 4717, where
up to 32 ATM cells can be mapped into one T-MPLS packet. The
maximum number of ATM concatenated cells into one T-MPLS packets is
configurable per concatenated ATM flow in the range [1,32] (1: no
concatenation, 32: PW size = 1676 bytes). The maximum number of
concatenated cells per 10G Multi-Service ATM card is 32 K
The same ATM PW can carry both concatenated and not concatenated
ATM flow. Moreover, the following conditions shall be applied:
Concatenated cells , carried by the PW, can belong to more than one ATM
flow, with upper limit of 4K
In case of cell concatenation when an ATM OAM packet (e-to-e / segment F4
and F5) is received, the previously already queued cells for that PW are sent
in a T-MPLS packet. The OAM cell is sent in the subsequent packet.
ATM flows included in a concatenated group should have the same ATC
(ATM Traffic Contract profile). This ATC is translated in the
corresponding T-MPLS PHB of the concatenated packet


Issue 01
The timeout for the generation of T-MPLS concatenated packet is

configurable:
Per concatenated ATM flow
In the range [0.1ms -10ms],with step of 0.1ms
The CLP (Cell Loss Priority) bit changing in the ATM cells used as trigger
for the generation of the MPLS packet containing concatenated ATM
cells is configurable per concatenated ATM flow
The figure in the next page shows examples of CoS handling in a
concatenated packet:


Issue 01


Issue 01
For ATM cell concatenation mode (see figure below), each flow where
concatenation is required is associated to a CellConcGroup, whose
characteristics are defined by the CellConcGroupTable.
The following checks are required:
ATM flows components of a cell concatenation group are required to have the
same ATC;
All Inflows associated to a CellConcGroup should be included in the same
PW;.


Issue 01
Configuration
1. Select Data ATM Management Concatenation Group
2. Click on Create


Issue 01
4. Click on Save & exit or Save & continue


Issue 01
4 ATM on PW CXC


Issue 01
4 ATM on PW CXC
Procedure for ATM over PW CXC
Step Action
1 configure the NNI Port (VCG) as MPLS *

2 Activate the MPLS Port (VCG interface)
create the Head/Tail tunnel (In Label = 500, Out Label =
3
600)
4 configure and manage the Tunnel
create the Head/Tail Pseudowire (In Label = 5000, Out
5
Label = 6000)
6 configure and manage the Pseudowire
7 Create the ATM traffic descriptor
create unidirectional ATM connection between the ATM port 1 and
8
PW
It is supposed that the trainee can perform the steps 1, 2, 3,4,5,6,7.

For the steps 1,2,3,4,5,6 refer to session: “S03M04_S3_NE Operation
M4_Operator_Interface_T-MPLS_features” pg. 15


Issue 01
4 ATM on PW CXC
Test bench
ATM port 1 Classification Inside the ATM PP10G, the operator

VPI = 1000 on port and
VCI = 500 ATM VPI/VCI can choose if activating or not the
swapping of the VPI/VCI
CLASSI
FIER
ATM over
port B
MPLS
IN OUT
PW CXC
NNI port:
port
AU4
SDH
FLOW FLOW VCG#2, sl15

Traff.
PW label Tunnel
Descr. label
SDH XC
ATM Ingress Traffic Descriptor (CBR):

PIR: 50 Mb/s
CIR: 50 Mb/s
PBS: 1000 bytes
CBS: 1000 bytes

Issue 01
4 ATM on PW CXC
Step 8: create ATM over PW CXC
1. Select Connection ATM Service XC
2. Click on Create


Issue 01
4 ATM on PW CXC
Step 8: create ATM over PW CXC [cont.]

egress port of the connection
4. Click on Search
5. Select the PW

Issue 01
4 ATM on PW CXC

ingress port of the connection


Issue 01
4 ATM on PW CXC
8. Select the ATM TD


Issue 01
4 ATM on PW CXC
8. Choose the values

for the swapping
(optional)
VPI and VCI are the values

for the ATM classifier
9. Configure the cell

10. Click on Save & exit or concatenation
Save & continue


Issue 01
4 ATM on PW CXC


Issue 01
End of Module
Operator Interface-ATM features


Issue 01
36
Section 3
NE Operation
Module 6
Operator Interface-CES features
Issue 01
1850 TSS-320 & 1850 TSS-160

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

Issue 01
Blank Page

NE Operation Operator Interface-CES features
Document History

Issue 01
Module Objectives
• Create TDM over PW service


Issue 01


Issue 01
Table of Contents
Page
1 Introduction 7
2 CES configurations 13
3 CES over PW: SAToP over MPLS PW 19
4 CES over PW: MEF-8 over MPLS PW 33


Issue 01


Issue 01
1 Introduction


Issue 01
1 Introduction
Introduction
1850 TSS-320/160 supports (via Universal Gateway, UGW unit)

interworking between legacy protocols and Ethernet / T-MPLS / MPLS-
TP and performs gateway functionality between TDM and Packet
domains. It supports CES (Circuit Emulation Service) capability for DATA
application, where a TDM client (E1) is mapped into an upper server
layer, that can be:
T-MPLS / MPLS-TP server layer (TDM over Packet), performing SAToP function
(“Structure Agnostic TDM over Packets”), as per RFC 4553
CES requires an interworking function (IWF) at both ends of the packet
network: the IWF converts the TDM signal into a series of PKTs on
ingress into the PKT network and re-creates the TDM circuit on egress.
The packet network must maintain the bit integrity, the timing
information and any other client specific characteristic of the
transported traffic.


Issue 01
1 Introduction
1662SMC equipment can be used as drop shelf in order to provide the

E1 ports.


Issue 01
1 Introduction
1850 TSS-320/160 supports the following CES capabilities:

Up to 1008 bidirectional E1 CES sessions
E1 SAToP over PW (RFC 4553)
E1 structure agnostic (MEF-8) over MPLS PW for a T-MPLS node (interworking
function).
1850 TSS-320/160 supports:
E1 TDM client (2048 kbps) for CES functionality in framed structure, as per
ITU-T Rec.G.704
CES functionality for the TDM signals transported by SDH frame, according to
E1 PDH signals mapping in SDH VC-12 tributaries.


Issue 01
1 Introduction
Differential Timing Frequency
Differential timing method is recommended when frequency

transparency is required through a PSN. This method requires
synchronous network clock at CES systems. Timing information (the
difference between the common reference clock and the incoming
clock) must be explicitly transferred from the ingress CES system to the
egress CES system.
1850 TSS-320/160 supports differential timing method using RTP
protocol time-stamping mechanism.
In this scenario IWFs share a common clock independent of the TDM
timing. One of the TDM end systems is required to slave its timing
circuitry to that of the other. The relationship between the frequencies
of the master TDM clock and the common clock is encoded in using RTP
timestamp mechanism, and transmitted across the packet network. The
master frequency is regenerated at the remote IWF by modifying the
TDM clock frequency based on the encoded relationship received.

Differential timing with RTP time-stamping

Issue 01
1 Introduction
It is possible that timing restoration in each direction is done

independently on each other.
Differential timing with independent timing in each direction
18500 TSS-320/160 provides the user the ability of configuring the

frequency of RTP protocol time-stamping:
155.53 MHz
77.76 MHz
38.88 MHz
25 MHz (default value)
16.384 MHz

Issue 01
2 CES configurations


Issue 01
Differential Time Frequency
The parameter is per node
1. Select Data CES Management Differential Time Frequency
2. Choose the frequency

3. Click on Save


Issue 01
TDM parameters profile
The parameter is per node
1. Select Data CES Management Generic TDM parameters
2. Click on Create


Issue 01
TDM parameters profile [cont.]

The window, provides the following parameters:

Payload Size: this parameter indicates the E1 payload size
Rtp hdr Used: this option permits to enable the control over CES signal
Jtr Bfr Depth: this parameter permits to set the buffer size
Pkt Filler: works only in case of failure. This is the value inserted in the staffing bits towards the SDH
side
Payload Suppression: this option permits enable/disable the payload suppression: if set to enable, in
case of errored frames, the payload is removed and only the header is transmitted
Pkt replace Policy: works only in case of failure. This is the value inserted in the staffing bits towards
the T-MPLS side
Average Pkt Loss Time Window: this value represents the timeframe in which the parameters at the
right of the window are checked
Stray Pkt Detect: this option permits enable/disable the Stray packet detection.
Excessive packet loss Threshold: shall be detect by computing the number of lost packets over a
configurable amount of time and comparing it with a preconfigured threshold.
Stray packets: shall be detected as a mismatch between the expected SSRC value in the RTP header
and the actually received SSRC field value in the incoming packets. In the UGW this SAToP defect is
equivalent to the Misconnection of CESoETH frames defined in MEF8.
Malformed packets: shall be detected as the mismatch between the expected packet size (taking the
value of the L bit into account) and the actual packet size. When RTP is used, malformed packets shall
also be detected as the mismatch between the PT value and that allocated for this direction of the
PW. In the UGW this SAToP defect is equivalent to the Malformed frames defined in MEF8.
Buffer overrun: shall be detected when the jitter buffer cannot accommodate newly arrived packets.
The system shall use one second time window to calculate the number of packets dropped due to
buffer overrun.

Issue 01
TDM parameters profile [cont.]
3. Click on Save

Buffer underrun: shall be detected when the jitter buffer does not have enough packets to be used for
recovery of PDH data stream.The system shall use one second time window to calculate the number of
times a packet needed to be played out and the jitter buffer did not have enough data
Remote packet loss: shall be detected when the R bit is set in the incoming packets. The system shall
use one second time window to calculate the number of detected packets with R bit set.

Issue 01
Blank Page


Issue 01
3 CES over PW: SAToP over MPLS PW


Issue 01
Test bench (E1 over PW)
SDH Matrix SDH Matrix

PW 1-1-2 Tunnel-1-1-1
PW label: Tunnel label:
- in label: 7000 - in label: 2000
- out label: 8000 - out label: 3000
PDH port SDH port SDH port
STM-4 link
E1 UGW MPLS port
Sl 25/p1
AU-4 #1
UGMVC4 port #1
1662SMC 1850 TSS-320


Issue 01
Procedure for 1850 TSS-320 node
Step Action
1 Create MPLS port
2 Create T-MPLS/MPLS-TP Tunnel
3 Create T-MPLS/MPLS-TP Pseudowire
4 Create TDM Parameters Profile
5 Choose the UGW port and activate the selected E1
6 Create SDH CXC between AU4 & UGMVC4 port
7 Create SAToP Service
It is supposed that the trainee can perform the steps 1, 2, 3 and 4.

For the steps 1, 2 and 3, please refer to session: “S03M04_S3_NE Operation
M4_Operator_Interface_T-MPLS_MPLS-TP_features” from pg. 22 on. For the
step 4 please refer to chapter #2 pg 15


Issue 01
Step 4: choose the UGMVC4 port & activate the selected E1
1. Select the PPUGW board
2. Scroll the window up to the bottom and click on View ALL
3. Click on the UGMVC4 port #1


Issue 01
Step 4: choose the UGMVC4 port & activate the selected E1 [cont.]
4. Select the E1 Select tab
5. Choose the E1 channel

6. click on Continue
7. Select the PHYSICAL tab
8. Set up the PDH port
9. Click on Save

Issue 01
Step 4: E1 configurations
1. Select the E1 Detail tab
2. Configure the E1 parameters: E1

framed ON/OFF and CRC ON/OFF
3. click on Save

Issue 01
Step 5: create SDH CXC between AU4 & UGMVC4 port
1. Select the PTF Connection tab
2. Choose the Direction



Issue 01
Step 5: create SDH CXC between AU4 & UGMVC4 port [cont.]
5. The user must specify the complete AID of the end point
(i.e: STM16AU4-1-1-25-1-1) or click on Start Tree Selection


Issue 01
Step 5: create SDH CXC between AU4 & UGMVC4 port [cont.]
8. Click on Create


Issue 01
Step 6: create SAToP service
1. Select Data CES Management PW Management
Click on Search/Refresh to filter the CES PW

or PDH port details based on the selected
parameter values
2. Click on Create Satop


Issue 01
Step 6: create SAToP service [cont.]
3. Click on Select to specify the PW
4. Click on Search
5. Select the PW-1-1-2


Issue 01
6. Click on Select to specify the PDH port
7. Choose the UGW board 8. Select the E1 channel


Issue 01
9. Click on Select to choose the TDM parameters profile
11. Insert RTP Header SSRC In and Out
12. Insert RTP Payload In and Out
10. Choose the TDM profile
13. Choose the traffic Type: Guaranteed

Service only in this release
14. Click on Save

1850 TSS-320/160 provides the user the ability to configure the follwing RTP parameters when RTP
header is in used:
PT value shall be allocated from the range of dynamic values 96-127 (according to the user
configuration) for each direction of the PW. The same PT value MAY be reused for both directions of
the PW and also reused between different PWs.
SSRC (synchronization source) value in the RTP header is used for detection of misconnections, i.e.,
incorrect interconnection of attachment circuits. The SSRC value is provisioned by user per emulated
service per direction. Value in range 0 - 2^32-1 per service

Issue 01
Step 6: SAToP service management
Click on Search/Refresh to display the CES services
Click on Details to display the CES service parameters
The new CES service appears in the window
To delete a tunnel, tick the box and click on Delete

(a multiple selection is admitted)
Click on Statistics to enable/disable the PM on CES: for details please refer

to session: “S03M07_S3_NE Operation M8_Monitoring” from pg. 107 on


Issue 01
4 CES over PW: MEF-8 over MPLS PW


Issue 01
Test bench (E1 over PW)
SDH Matrix SDH Matrix

PW 1-1-2 Tunnel-1-1-1
PW label: Tunnel label:
- in label: 7000 - in label: 2000
- out label: 8000 - out label: 3000
PDH port SDH port SDH port
STM-4 link
E1 UGW MPLS port
Sl 25/p1
AU-4 #1
UGMVC4 port #1
1662SMC 1850 TSS-320


Issue 01
Procedure for 1850 TSS-320 node
Step Action
1 Create MPLS port
2 Create T-MPLS/MPLS-TP Tunnel
3 Create T-MPLS/MPLS-TP Pseudowire
4 Create TDM Parameters Profile
5 Choose the UGW port and activate the selected E1
6 Create SDH CXC between AU4 & UGMVC4 port
7 Create MEF-8 Service
It is supposed that the trainee can perform the steps 1, 2, 3, 4, 5 and 6

For the steps 1, 2 and 3, please refer to session: “S03M04_S3_NE Operation
M4_Operator_Interface_T-MPLS_MPLS-TP_features” from pg. 22 on. For the
step 4 please refer to chapter #2 pg 15. For the steps 5 and 6 please refer to
chapter #3 pg. 19 on


Issue 01
Step 6: create MEF-8 service
Click on Search/Refresh to filter the CES PW

or PDH port details based on the selected
parameter values
2. Click on Create Mef8


Issue 01
Step 6: create MEF-8 service [cont.]
3. Click on Select to specify the PDH port
5. Select the UGE1 interface

4. Choose the UGW board

The UGE1 represents the image on UGW board of the E1 interface presents in the 1662 DS.

Issue 01
6. Click on Select to choose the TDM parameters profile
8. Insert Rx ECID value 9. Insert Tx ECID value
10. Insert RTP Header SSRC In and Out
11. Insert RTP Payload In and Out
12. Insert the NE MAC Address of the peer node
7. Choose the TDM profile

1850 TSS-320/160 provides the user the ability to configure the follwing RTP parameters when RTP
header is in used:
ECID (Emulated Circuit IDentifier): consists of a single, 20-bit unsigned binary field and identifies the
emulated circuit being carried. This separates the identification of the emulated circuit from the
Ethernet layer. ECID have local significance only, and are associated with a specific MAC address.
Emulated circuit may be given different ECIDs for each direction of the circuit. ECIDs are selected
during the creation of an emulated circuit by operator.
PT value shall be allocated from the range of dynamic values 96-127 (according to the user
configuration) for each direction of the PW. The same PT value MAY be reused for both directions of
the PW and also reused between different PWs.
SSRC (synchronization source) value in the RTP header is used for detection of misconnections, i.e.,
incorrect interconnection of attachment circuits. The SSRC value is provisioned by user per emulated
service per direction. Value in range 0 - 2^32-1 per service

Issue 01
13. Choose the traffic Type: Guaranteed
Service only in this release
14. Click on Select to specify the PW
17. Click on Save

15. Click on Search
16. Select the PW-1-1-2


Issue 01
Step 6: MEF-8 service management
Click on Details to display the CES service parameters
The new CES service appears in the window
To delete a tunnel, tick the box and click on Delete

(a multiple selection is admitted)
Click on Statistics to enable/disable the PM on CES: for details please refer

to session: “S03M07_S3_NE Operation M8_Monitoring” from pg. 107 on


Issue 01
Blank Page


Issue 01
End of Module
Operator Interface-CES features


Issue 01
37
Section 3
NE Operation
Module 7
Alarm Management
Issue 01
1850 TSS-320 & 1850 TSS-160

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

Issue 01
Blank Page

NE Operation Alarm Management
Document History
Editi Date Author Remarks

on

Issue 01
Module Objectives
Describe how to handle the AS application for current alarms


Issue 01


Issue 01
Table of Contents
Page
1 Alarm Management 7
1.1 Presentation 8
1.2 The operative Primary and Secondary state 13
1.3 ASAP Management 19
1.4 Reported alarms 29
1.5 TCA Profile, ALM CUTOFF, ALM Resynch., Condition Log 33
1.6 List of Equipment Condition Types and Facility Condition Types 43


Issue 01
Page


Issue 01
1 Alarm Management

NE Operation Alarm Management Section 3 Module 7 Page 7

Issue 01
1.1 Presentation


Issue 01
1.1 Presentation
Alarm and condition types

The system reports different types of events, which differ in their
potential affect on service and the urgency of clearing the condition.
These event types are:
Alarms with different severities, which require trouble clearing
Not alarmed but reported standing conditions in which the system is in a non-
regular state (for example in a loopback) but which do not require trouble
clearing
Transient conditions which are reported but do not require clearing.

NE Operation Alarm Management Section 3 - Module 7 - Page 9

Issue 01
1.1 Presentation
Alarm and condition severities

The alarm severity is determined by the service affect of a particular
failure. The alarm severity is used to indicate the urgency to repair the
failure.
Alarms and conditions are raised with one of these severities:
Critical
Major
Minor
Non-Alarmed.
Alarms have default severity levels, but new severity levels can be
assigned to each condition type on a per entity basis, whereas entities
include equipment and facilities. Also the impact on service can be
provisioned (service-affecting or non service-affecting). That means
that alarms can be reported with different severity levels and as
service-affecting (SA) or non service-affecting (NSA).


Issue 01
1.1 Presentation
Introduction
Reporting
Alarms and conditions are reported in different ways:
By autonomous reports and logs
Visually by LEDs on the modules in the shelves in different colors which
indicate the severity
As audible alarms.
Alarms and conditions are autonomously reported and logged and they
are retrievable, individually or per type.
Reports and logs include access identifiers, date and time, event type,
event description, severity (applies to alarms only), and service impact.
An alarm hierarchy applies to the alarm reporting. Whenever a higher
level alarm occurs while a lower level alarm exists on the same entity,
the lower level alarm is cleared. For example, when an alarm on a port
is reported and afterward an alarm is raised for the same module, the
port alarm is cleared.

Displaying summary alarms

Summary alarms show that at least one alarm of a certain severity exists in the shelf or in the rack.
They are displayed for the individual shelf on LEDs on the Fan Unit according to their severity
(Critical, Major, Minor).

Issue 01
Blank Page


Issue 01
1.2 The operative Primary and
Secondary state


Issue 01
1.2 The operative Primary and Secondary state
Alarm synthesis screens [cont.]
The possible values allowed for the primary and secondary state are the
following:
Primary state
IS, IS-NR In_Service, Normal: the entity is capable and allowed to provide
its provisioned functions.
OOS-AU Out_Of_Service-Autonomous: the entity is not available for
providing its provisioned functions but the entity is not
intentionally suspended by external management command
(from an OS or craft interface) from performing these functions.
In general, the cause of the incapability is due to an unsolicited
autonomous event detected in the system or in the associated
network (e.g., STM-n LOS detected).
OOS-AUMA Out_Of_Service-Autonomous_and_Management: the entity is not
available for providing its provisioned functions because an OOS-
AU state transition has occurred and the entity is intentionally
suspended by external management command (from an OS or
craft interface) from performing its provisioned functions.

primary service state. Valid for all modules except TBUS (it has only IS and OOS-AU) and Shelf (it has
only IS and OOS-AUMA).

Issue 01
OOS-MA Out_Of_Service-Management: the entity is intentionally
suspended by external management command (from an OS or
craft interface) from performing its provisioned functions, but
the entity may still be operationally capable of performing its
provisioned functions.
Secondary state
ACT Cross Connected

AINS Automatic In-Service: When a facility is in AINS state, no
transmission condition types or PM threshold crossing alerts are
autonomously reported for this facility, but the alarm conditions
are monitored and PM data are collected (if performance data
collection is enabled).
AINS-DEA Automatic In-Service Deactivate
CP Managed By TDM Control Plan
DSBLD Disabled
FAF Facility Failure
LPBK Loopback
MEA Mismatch of Equipment and Attributes - An incompatible module
is physically present in a provisioned slot.
PMD Performance Monitoring Disabled

Issue 01
PMI Performance Monitoring Inhibited

PSI Protection Switching Inhibited, by operator command
SGEO Supporting Entity Outage - reported for an XFP, SFP or PIM
module if the supporting IO card is in a OOS primary state.
SDEE Supported Entities Existing - Reported for IOC, PIM, SFP and XFP
modules that directly supports provisioned Facilities reported
for all the IOCs modules that don't support directly any Facilities
but that hosts provisioned Equipment entities that support
directly provisioned Facilities
STBYC Standby-Cold - the module is to back up another module, but is
not synchronized with the backed-up module. A module with a
cold standby status will not be immediately able to take over
the role of the backed-up module, and will require some
initialization activity
STBYH Standby-Hot - the module is to back-up another entity and is
normally synchronized with the backed-up module. When In-
Service, a module with a hot standby status will be immediately
able to take over the role of the backed-up module without the
need for initialization activity

Issue 01
SWDL Software Download - the module is out of service because it is

in the process of acquiring, loading, and/or initializing its
software
TRM Terminated (only for ModVC4)
VCACT Virtual Concatenation Path is Active. This means the entity is
part of VCG and is allowed to carry traffic (only for VCGMem)
VCIDLE Virtual Concatenation Path is Idle. This means the entity is part
of VCG and is not allowed to carry traffic (only for VCGMem).
UAS Unassigned. No equipment is provisioned in the addressed
position
UEQ Unequipped - there is no module in the addressed position
WRK Working - the module is currently active and if able, providing
service. Mutually exclusive with STBYH or STBYC


Issue 01
Blank Page


Issue 01
1.3 ASAP Management


Issue 01
1.3 ASAP Management
ASAP list (data port)
To display the ASAP list: Data ASAP list

ASAP: Alarm Severity Assignment Profile

For each NE, 4 fixed ASAP are defined by default by the manufacturer and others can be created by the
user. The fixed ASAP are mandatory and can not be modified or deleted but they can be cloned to
create a new ASAP.

Issue 01
1.3 ASAP Management
ASAP details (data port)
1. Select an a profile

The content of the details page are the alarms, the SA (Service Affecting) and NSA (Not Service
Affecting) information

Issue 01
1.3 ASAP Management
ASAP list creation (data port) [cont.]
1. Open Data Asap List
2. Select “Create”
3. Insert the name and

then click on “Create”


Issue 01
1.3 ASAP Management
ASAP list creation (data port) [cont.]
4. Choose the Alarm Type
5. Choose the severity

for SA and NSA case
6. Click on “Save
Asap Label”


Issue 01
1.3 ASAP Management
ASAP list creation (data port)
7. The new ASAP appears in the list


Issue 01
1.3 ASAP Management
ASAP assignment (data port)
2. Select “PHYSICAL” tab
1. Select a data port
3. Set “down” the Admin state
4. Choose the “Change severity profile”
5. Choose the ASAP profile

The new ASAP appears in the profile

Issue 01
1.3 ASAP Management
ASAP list creation
1. Open Alarms ASAP Mng
2. Select “Create ASAPs”
3. Insert the User Label, configure the ASAP

Type, Default and the configuration
4. Click on “Save & exit”

User Label label must be inserted with the following format: name with the extension from -2 to -n
Options for ASAP Type
Options for Default

Issue 01
1.3 ASAP Management
ASAP list display
1. Select ASAP AID = ALL
2. Click on “Search”
The new ASAP appears in the ASAP list

The ASAP Mng tab displays the ASAP FILTER panel that contains the following parameters:
ASAP AID: the associated combo-box lists all the available ID services as the tributary signal. The
default values are:
ALL = all alarms
TIMING
MAU = MAU port profile
BITS = synchronism alarms
SECU = administration security alarms
STMn = STMn (where n = 1, 4, 16 or 64) alarms
GBE = Gigabit Ethernet alarms
OGPORT
VCn = (where n = 4, 44c, 416c, 464c)
TUSEG–10GBE = 10 Gigabit Ethernet alarms
VCG = Virtual Concatenation Group alarms
ODU2 = ODU2 port alarms
User Label: The entry box shows a mnemonic string to address the ASAP. The xxxxxxx-0 and -1 are
factory defined, while xxxxxx-2 to -n can be set by the user. Each single alarm can be classified with a
criterion selected by the operator.

Issue 01
1.3 ASAP Management
ASAP assignement
1. Select a board
2. Click on “Select”
3. Choose the ASAP and

click on “Send” The new ASAP appears in the profile

Issue 01
1.4 Reported alarms


Issue 01
1.4 Reported alarms
Introduction
By means of the “Alarm” option it is possible to display all the alarms
related to the card.
1. Select a board
2. Click on “view”


Issue 01
1.4 Reported alarms
Reported Alarm
1. Select alarm tab
Click here to display alarms & conditions
The reported alarms list appears in the window


Issue 01
Blank Page


Issue 01
1.5 TCA Profile, ALM CUTOFF, ALM Resynch.,
Condition Log


Issue 01
1.5 TCA Profile, ALM CUTOFF, ALM Resynch., Condition Log
TCA Profile configuration
TCA Profile: it allows to configure and display of the active threshold

crossing alarm profile (TCA = Threshold Crossing Alarm).
To open the TCA Profile menu, select: Alarms TCA Profile
1. Select “create”
See next page

The TCA Profile tab contains the Filter panel that contains the following parameters:
Profile Type: the associated combo-box lists all the TCA profile access Identifier. The values are:
Blank = none
ALL = all profiles
STM-n = STM-n (where n = 1, 4, 16, 64)
GBE10 = 10 Gigabit Ethernet profiles
GBE = Gigabit Ethernet profiles
VC4-n = VC4-n (where n = 1, 4C, 16C, 64C) profiles
LOVC3 = LO VC3 profile
TCA – Profile ID: it has three associated combo boxes:

The first combo-box lists all the TCA profile access Identifier with the THP prefix followed by the
Profile Type abbreviation previously described, e.g. THPVC4
The second and third combo-boxes allow to set a number for the profile access Identifier. The range
is from 0 to 256, e.g. THPVC4
User Label: This is an entry field which allows to digit the user label of the profile access Identifier.
This is the TCA-AID with only one of the profile number and precedes by the LBL description

Issue 01
TCA Profile configuration [cont]
2. Select the “Profile Type”
3. Insert the user label
4. Select “Y” or ” N”
See next page

Profile Type: the associated combo-box lists all the TCA profile access Identifier. The values are:
STM-n = STM-n (where n = 1, 4, 16, 64)
GBE10 = 10 Gigabit Ethernet profiles
GBE = Gigabit Ethernet profiles
VC4-n = VC4-n (where n = 1, 4C, 16C, 64C) profiles

Issue 01
6. Open Alarms TCA profile menu
7. Select Profile Type = ALL and then click on Search
8. Click on the new TCA Profile

See next page


Issue 01
1.5 TCA Profile, ALM CUTOFF, ALM Resynch., condition Log
10. Click on “Save” to confirm the settings


Issue 01
TCA Profile assignment
To assign a TCA profile, select an object (i.e. port) and configure the
TCA
1. Click on “Select” and choose the TCA
2. Click on “Send”


Issue 01
ALM CUTOFF
ALM CUTOFF: it allows to silence the office audible alarm indications.

To open the ALM CUTOFF menu, select: Alarms ALM CUTOFF
1. Click on “SEND”

The currently active audible alarm indications will be silenced. The visual alarm indications are not
affected. Future alarm reporting is not be affected and new audible alarm indications will be provided
for any new alarms.
The ACO LED turns on and a new alarm arrives, it is presented to the audible closures and the ACO LED
switches off. Alarms silenced is not presented to the Audible closures even if they are still present

Issue 01
ALM Resynch.
ALM Resynch.: it allows to update the alarm database to the current

alarm situation.
Clicking on Resynchronize functional button a command refresh the
alarms and the relevant information is referred.
To resynchronize the alarms, select: Alarms ALM resynch.
1. Click on “Resynchronize”


Issue 01
Condition Log: history alarm
This function reporting the NE alarm history log
1. Configure the search criteria
2. Click on “Search”

The Alarm Log tab displays the Filter by panel that contains the following parameters:
Domain: Specifies the domain for filtering the alarm. The values are ALL, TDM, and DATA.
Note: If the selected Domain value is DATA, the window displays Severity drop down, the values are:
CRITICAL, MAJOR, MINOR, WARNING, and CLEARED. If the selected Domain value is ALL, the Event
Type and Aid Type parameters are not available.
Event Type: Specifies the event type that triggers alarm. The values are ALM or NOTALM.
Aid Type: Specifies the Access Identifier type. The values are: ALL, BITS, TIMING, EQPT, GBE, VCG,
GBE10, ODU2, OTU2, STM1, STM4, STM16, STM64, VC4, etc…
From Date & Time: Specifies From date & time to apply filter to the alarm
To Date & Time: Specifies To data & time to apply filter to the alarm

Issue 01
Blank Page


Issue 01
1.6 List of Equipment Condition Types and
Facility Condition Types


Issue 01
1.6 List of Equipment Condition Types and Facility Condition Types
Introduction
Equipment Condition Types

This paragraph provides a list of the equipment and facility condition
types used in the product, along with the factory default notification
codes (CRitical, MaJor, MiNor, Not-Alarmed, or Not-Reported) for each
service effect setting (Service Affecting or Non-Service Affecting).
The following pages describes by means of tables list, the relationship
between the standing condition types, the equipment/facility type, and
the factory default notification code for equipment, facility, and
system common condition types.
Detail of informations:
DIRN = Direction (RCV = Received; TRMT = Transmitted)
LOCN = Location (NEND = Near End; FEND = Far End)
NC = Notification Code (MN = Minor; MJ = Major ; CR = Critical; NA = Not
Alarmed ; NR = Not Reported)
SE = Service Effected (NSA = Non-Service Affecting; SA = Service Affecting)
CE = Condition Effected (SC= Standing Condition; TC = Transient Condition)
AE = Affected Entity
The Affected Entity column identifies the type of equipment associated with each condition type. The
factory default service affecting (SA) and non-service affecting (NSA) notification code setting for each
condition type is shown in the Notification Code (NC) columns (a dash indicates that setting does not
apply for that condition type).

Issue 01

The following table shows the facility condition types used in the
system. The Access Identifier column identifies the type of facility
associated with each condition type. The factory default service
affecting (SA) and non-service affecting (NSA) notification code setting
for each condition type is shown in the Notification Code columns (a
dash indicates that setting does not apply for that condition type).
Detail of informations:
DIRN = Direction (RCV = Received; TRMT = Transmitted)
LOCN = Location (NEND = Near End; FEND = Far End)
NC = Notification Code (MN = Minor; MJ = Major; CR = Critical; NA = Not
Alarmed; NR = Not Reported)
SE = Service Affected (NSA = Non-Service Affecting; SA = Service Affecting)
CE = Condition Affected (SC = Standing Condition; TC = Transient Condition)
AE = Affected Entity

The AE and AIDP columns identify the type of facility associated with each condition type. The factory
default service affecting (SA) and non-service affecting (NSA) notification code setting for each
condition type is shown in the Notification Code (NC) columns (a dash indicates that setting does not
apply for that condition type).

Issue 01
Equipment Condition reference


Issue 01
Equipment Condition reference [cont.]


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01
Facility Condition Types [cont.]


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01


Issue 01
Facility Condition Types (snmp)


Issue 01
Facility Condition Types (snmp) [cont.]


Issue 01


Issue 01


Issue 01
End of Module
Alarm Management


Issue 01
38
Section 3
NE Operation
Module 8
Monitoring
Issue 01
1850 TSS-320 & 1850 TSS-160

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

Issue 01
Blank Page

NE Operation Monitoring
Document History

Issue 01
Module Objectives
Describe the theory of Performance Monitoring

Explain the Performance Monitoring Operation


Issue 01


Issue 01
Table of Contents
Page
1 Introduction 7
2 Operation (SDH) 19
3 PM on Ethernet Data 33
4 PM on T-MPLS 65
5 PM on OTN 73
6 PM on ATM 91
7 PM on PDH 99
8 PM on CES 107
9 PM Global File 133


Issue 01


Issue 01
1 Introduction

NE Operation Monitoring Section 3 Module 6 Page 7

Issue 01
1 Introduction
PM Approach: Block definition
A block is a set of consecutive bits associated with a specific path or section.
Each block is monitored by means of the relevant BIP-n code performing n

independent parity checks
A block is assumed to be errored if at least one of the n checks fails

max. number
Error checksum Block size of block errors
per second
B1 (RSOH) STM-N 8.000
B2 (MSOH) 801 bits 192.000 * N

(STM-N)
B3 (HP-POH) VC-4 8.000

VC-3
V5 (LP-POH) VC-12 Multiframe 2.000

Two approaches can be used to estimate the quality of a signal:

BER Approach: uses the BIP code to compute the Bit Error Rate (BER)
This method is the same used in PDH networks
It fits the case of random distribution of errors, but provides very poor indications when burst
distributed errors are present

Errored Block Approach: uses the BIP code to evaluate the errored Block
This method focuses on various portions of the digit stream. It is not interested just in the amount
of errors occurred, but on the amount of errors occurred in a certain portion of the signal.
This approach shows good results for any type of error distribution.
This new approach was adopted for SDH networks and, as a consequence, new quality parameters
based on error block events have been defined.

Performance Monitoring (PM) is used to monitor the signal quality
The performance parameters are based upon the measurement of Blocks:

a set of consecutive bits associated with the path and the section
Each block is monitored by calculating a checksum e.g. Bit Interleaved Parity (BIP).
These block errors can be monitored on several layers inside each NE:
B1: BIP8 for a regeneration section
B2: N*BIP24 for a multiplex section (N= 1, 4, 16, 64)
BIP24 STM-1
BIP96 STM-4
BIP384 STM-16
BIP1536 STM-64
B3: BIP8 for VC-4 or VC-3 path (HP)
V5: 2 bits perform a BIP2 of VC-12 path (LP)

Issue 01
1 Introduction
Principles of data collection
EB: Errored Block
ES: Errored Second Error Monitoring
SES: Severely Errored Second
BBE: Background Block Error
Anomalies Defects
EB ≥ 30 % /s
* Each SES is also

counted as ES
ES * SES
(in case of defects)
errored blocks
BBE
outside SES
Unavailabilty
Counter inhibition ≥ 10 consecutive SESs
The signal quality depends on the occurrence of:

Bit Errors = Anomalies
Alarms = Defects
Errored Block (EB)

Block containing one or more errored bits.
Errored Second (ES)

A one second period with one or more errored blocks or at least one defect.
Severely Errored Second (SES)

A one-second period which contains at least 30% (for path layer) errored blocks or at least one
defect.
SES is a subset of ES.
Background Block Error (BBE)

Errored block (EB) occurring outside a severely errored second (SES).

Issue 01
1 Introduction
Definition of Availability
x t in sec
= 10 sec < 10 sec < 10 sec = 10 sec
UAT (UnAvailable Time) with UAS (UnAvailable Seconds)
Begin of detection: SES End of detection:

ES := ES - 10 ES := ES + x
SES := SES - 10 ES which is not a SES SES := SES
UAS := UAS + 10 Non errored second UAS := UAS - 10
Inhibition of counters:
ES / SES / (BBE)

Unavailable Time (UAT)

A period of unavailable time (UAT) begins at the onset of 10 consecutive SES events.
These 10 seconds are considered to be part of unavailable time.
A new period of available time begins at the onset of 10 consecutive non-SES events.
UAT report = Unavailability Time report.
This report is provided when an unavailability period is detected
Upon detection of the start of the unavailability condition a data/time UAT report is provided
Upon detection of the end of the unavailability condition a data/time report notifying the end of
UAT is supplied
Unavailable Second (UAS)
An unavailable second (UAS) is a second which is part of the Unavailable Time (UAT).
A bi-directional path is in the unavailable state if either one or both directions are in the unavailable
state
In case of bidirectional TP only one UAS performance data is obtained, counting both the Near End and
Far End terminal values.
Each direction of a path or section can be in one of these two states:
Available state
Unavailable state:
Unavailable Second (UAS): number of seconds during an unavailability period
Unavailable Time Report (UAT report):a period of unavailable time begins at the onset of 10
consecutive SES events. When an unavailable period is detected this report is sent.
Near End Unavailable Second (NEUAS/UAS):
An Unavailable Second is a second which is part of the Unavailable Time.

Issue 01
1 Introduction
Test: PM Counter Values
Fill in the counter values for ES, SES and UAS for the following
points of time: 5s, 10s, 15s, ... 70s (start values: 0)
ES --------------------------------------------------------------------------------------
SES --------------------------------------------------------------------------------------
UAS --------------------------------------------------------------------------------------
700 2 4 6 8 10 15 20 25 30 35 40 45 50 55 60 65 70
60
EB (%)
50
40
30
20
10
0
2 4 6 8 10 15 20 25 30 35 40 45 50 55 60 65 70
Time allowed :
time (in seconds)
15 minutes


Issue 01
1 Introduction
Near End/Far End Counters
Network Element 1
STM-N Network Element 2
with errors V5
B1
PDH Port SDH Port B3 SDH Port PDH Port
B2
Vc12 Tu12 Vc4 Au4 MST RST RST MST Au4 Vc4 Tu12 Vc12
V5
G1
M1
MS-REI HP-REI LP-REI
LP-REI HP-REI MS-REI STM-N
with REIs
Far End Counters: Near End Counters:
FEBBE BBE
FEES ES
REI: Remote Error Indication
FESES SES
FEUAS NEUAS

Near End PM:

The performance monitoring parameters are evaluated by means of the Error Detection Code, e.g. B1
Far End PM:

The performance monitoring parameters are evaluated by means of Remote In-Service Indications
Both Near end and Far end counters are supported in receive direction of the signal for all path layers of
SDH, and for the multiplex section layer.
For the regenerator section, no far end information is transmitted and, therefore, only near end
counting is supported.
Near End counters are incremented inside the different TPs if in the received STM-N frame anomalies or
defects have been detected.
Far End counters are incremented inside the different TPs if the transmitted STM-N frame was erroneous
(anomalies or defects)
The Network Element which is transmitting an errored signal, is informed about the errors by receiving
Remote Error Indications (REI)
MS-REI: M1-Byte inside MSOH contains the number of erroneous blocks detected in B2
HP-REI: Inside the G1-Byte (Bits 1 to 4) the number of erroneous blocks detected in B3 is indicated
LP-REI: Inside the V5-Byte (Bit 5) there is the indication if BIP2 errors are detected (<>0)
The transmitting Network Element is informed about the alarms by receiving Remote Defect Indications
(RDI)

Issue 01
1 Introduction
Alarm information process
Two types of alarm information are provided when the performance

limits are reached:
UAT report = Unavailability Time report. This report is provided when an

unavailability period is detected
TCA reports = Threshold Crossing Alarm reports. These reports are provided
when at least one of the error/maintenance events ES, SES, BBE exceeds the
relevant fixed performance threshold


Issue 01
1 Introduction
TCA report: Thresholds
TCA: Threshold Crossing Alarm
Performance Monitoring: 15 minutes Performance Monitoring: 24 hours

TCA (on) TCA (off) TCA (on) TCA (off)
High
threshold threshold
Low
threshold
t1 t2 t3 t4 t5 t1 t2 t3 t4 t5
15min 15min 15min 24h 24h 24h

“Reset register” command "Reset register" command
The TCA is reset when within a The TCA is reset at the begin
15 min period there are no low of every new 24 hour period
thresholds crossed. and after a manual reset.

For quality supervision purposes, the recorded errors through the performance counters (ES, SES, BBE )
can be compared to threshold levels.
TCA: Threshold Crossing Alarm
If a counter value has crossed a threshold level, a TCA is transmitted to the alarm manager.
The threshold values are defined in threshold tables together with a severity and a flag indicating
whether crossing this value should be notified by an alarm and logged or only stored in the current
problem list.
Different thresholds can be assigned for near/far end and for granularity of 15 minutes and 24 hours.
Two thresholds mechanisms are supported:

For 24–hour (implicit clearance) monitoring periods, one threshold value is defined:
if the event count reaches or exceeds the threshold value during the monitoring period, a TCA is
generated: To clear a TCA, the alarm must be manually acknowledged by the user.
The following limitations apply for implicit clearance:
the value of the low threshold is fixed to “0” (only a single threshold is provided by a threshold
table).
An SES threshold crossing is cleared at the end of the interval if no unavailability was detected and
SES had not reached the low threshold (low threshold equal to 0).
Even in case of a suspect interval the TCA is cleared if no unavailability was detected and the low
threshold had not been reached.

For 15–minute (explicit clearance) monitoring periods, two threshold values (low, high) are defined:
a TCA is generated during the monitoring period when the event count reaches or exceeds the set
high threshold value the first time.

This TCA is automatically cleared by the system at the end of the following monitoring period in
which the event count is less than or equal to the low threshold value and there was neither an
unavailable nor a suspect period during this monitoring period.
Additionally an explicit clearance of TCAs for all granularity periods is executed if one of the
following events occurs during the current interval: deletion of the current data instance (TP)
Only for 24h: resetting of counters, increased thresholds (higher than current value of counters)
Issue 01
1 Introduction
PM Storage Registers: 15 minute
The Current 15-minute register shall accumulate the current 15-minute

PM data
At the end of each 15-minute boundary, the contents of the Current 15-
minute register shall be transferred to the Previous 15-minute register.
The current 15-minute registers shall then automatically be initialized
to zero.
The 31 Recent 15-minute registers shall be arranged as a Push-down
stack. At the end of each 15-minute boundary, the content of the
Previous 15-minute register shall be transferred to the top of the stack.
The PM data at the top of the stack shall be pushed down to the next
register and so forth. The data at the bottom of the stack shall be
pushed off and lost. The Recent 15-minute registers stack thus
contains the 31 most recent 15-minute PM data.


Issue 01
1 Introduction
PM Storage Registers: 1 day
The Current 1-Day register shall accumulate the current 1-day PM data.
At the end of each 1-day boundary, the contents of the Current 1-Day
register shall be transferred to the Previous 1-Day register. The current
1-Day registers shall then automatically be initialized to zero.
The 6 Recent 1-day registers shall be arranged as a Push-down stack.
At the end of each 1-day boundary, the content of the Previous 1-day
register shall be transferred to the top of the stack. The PM data at
the top of the stack shall be pushed down to the next register and so
forth. The data at the bottom of the stack shall be pushed off and lost.
The Recent 1-day registers stack thus contains the 6 most recent 1-day
PM data.
When the maximum value of a register is reached, the register shall
remain at the maximum value until it is reset or the value is transferred
or discarded.


Issue 01
1 Introduction
Higher order Path Overhead Monitoring
NE A NE B NE C
E W X Y E W
SDH SDH
AU4 Pass Through

SDH signal SDH signal
Slot # X AU4#n Slot # Y AU4#m

HPOM HPOM
before after
MATRIX
CxC
HPOM HPOM
after before


Issue 01
1 Introduction
Higher order Path Overhead Monitoring [cont.]
In case of AU4 pass through, the TTP is not terminated; however, in

such cases it is possible to read the OH of the VC-4 applying the “Higher
order Path Overhead Monitoring” function (HPOM). This is just a
monitoring, thus the OH is read from the VC-4 inside the incoming AU4
and is rewritten without any modification in the VC-4 of the outgoing
AU4.
The HPOM can be Before Matrix and After Matrix:
in slot #X: HPOM Before Matrix monitors the signal in the direction from A to
C
HPOM After Matrix monitors the signal in the direction from C to A
in slot #Y: HPOM Before Matrix monitors the signal in the direction from C to
A
HPOM After Matrix monitors the signal in the direction from A to C


Issue 01
2 Operation (SDH)


Issue 01
2 Operation (SDH)
PM in the port
To open the Performance Monitoring view, select an a port and then

click on “STM PM” tab. Three sub-functional tabs appears in the
window: 2. Select the “STM PM” tab
PM report
PM Init Register
PM Mode
1. Select the
SDH port

NE Operation Monitoring Section 3 - Module 6 - Page 20

Issue 01
2 Operation (SDH)
PM configuration
The PM Mode sub-functional tab contains two panels:
The Set Performance Monitoring Mode page allows to set the mode of PM
data collection for the specified facility
The Retrieve Performance Monitoring Mode page allows to retrieve the
mode of PM data col-lection for the specified facility
1. Select the “PM Mode” tab
2. Set “PM State” = ON

3. Click on “Save” to save the parameters.

The “Set Performance Monitoring Mode” tab shows the following parameters:
Access Identifier: Specifies the Access Identifier for the selected STMn port.
Location: Specifies the location. The values are NEND, FEND, BIDIR, or ALL. The default value is ALL.
Mode Type: Specifies the mode type requires to be set. The values are ALL, S, L. The default value is
ALL.
Direction: Specifies the direction. The values are RCV (receive Direction) and ALL. The default value is
RCV.
PM State: Specifies the performance monitoring state. The values are:
ON: The PM registers shall be enabled and counting
OFF: The PM registers shall be created/enabled but don’t count. While the PM registers are created
in this state, PM is considered as disabled in the document, because it is not counting.
DISABLED: The PM registers shall be not created for the facility. The default value is DISABLED.
Time period: Specifies the time interval for the which the report is being generated. The values are
15-MIN, 1-DAY, or BOTH. The default value is BOTH.
For performance monitoring purposes, the start of every 1-day period shall start at 00:00 (midnight)
related to UTC.

Issue 01
2 Operation (SDH)
PM configuration [cont.]
Retrieve Performance Monitoring Mode page
Click on “Retrieve”
to retrieve the
Mode result

The page shows the following parameters:

Access Identifier: The entry box specifies the identifier of the unit resource. It is also shown in the
tree.
Location: The combobox allows to specify the PM registers location to be initialized. The allowable
choices are:
NEND: Near End
FEND: Far End
BIDIR: Bidirectional
ALL: All
Clicking on the Default hyperlink it is possible to set the default value ALL.
Direction: The combobox allows to specifiy the direction of the signal being monitored. The allowable
choices are:
ALL
RCV Receive direction
Time Period: The combobox allows to specifies whether the 15-minute or 1-day (24 hour) PM collection
register is to be initialized. The allowable choices are:
15-MIN
1-DAY
Clicking on the Default hyperlink it is possible to set the default value 15-MIN.
Click on Retrieve to recall the Performance Monitoring Mode Result

Issue 01
2 Operation (SDH)
The PM Report sub-functional tab allows to retrieve the current and/or
historical 15-minute and/or 1-day PM data corresponding to the PM data
collection register(s) selected for the specified facility.
For each monitored parameter, the current and/or up to thirty-two (32) 15-
minute historical PM registers, or the current and/or up to seven (7) 1-day
historical PM registers or both 15-minute and 1-day PM registers can be
retrieved.
4. Select the “PM Report” tab
5. Click on “Retrieve” to retrieve the last PM results.


tree.
Monitor Level: The combo-box allows to set the discrimination level of PM parameter values to be
reported for the specified Monitored Parameter Type. The allowable choices are:
1- Down, Only PM data for the specified MONTYPE that is less-than or equal-to ( < ) the value of <
LEVEL> is reported.
1- Down Or Not Complete, Only PM data for the specified MONTYPE that is< the value of <LEVEL> or
that does not have a VLDTY flag of CMPL.
1- Up, Only PM data for the specified MONTYPE that is greater-than or equal-to ( > ) the value of <
LEVEL> is reported.
1- Up Or Not Complete, Only PM data for the specified MONTYPE that is >the value of <LEVEL> or
Clicking on the Default hyperlink it is possible to set the default value 1- UP
Location: The combobox allows to specify whether PM registers for near-end and/or far-end PM
monitoring are to be reported. The allowable choices are:
NEND: Near End
FEND: Far End
BIDIR:
ALL: All
Monitored Parameter Type: The combobox allows to specifies the type of monitored parameter whose
PM data registers are being retrieved. The allowable choices are:
ALL: All monitored types
Issue 01
2 Operation (SDH)

Direction: Direction: The combobox allows to specify the direction of the signal being monitored. The
allowable choices are:
ALL: both directions
RCV: Receive direction
TRMT: Transmit Direction
Time Period: The combobox allows to specifies the accumulation time period for the retrieved
performance monitoring information. The allowable choices are:
15-MIN
1-DAY
BOTH
Number of 15-minute: The combobox allows to set the number of 15-minute historical registers,
specifies the number of previous 15-minute historical PM registers to retrieve in addition to that
specified by Monitor Date and Monitor Time. The register specified by these parameters will be the first
output followed by the Number of 15-minute previous registers. The allowable choices are:
from 0 to 32 previous historical 15-minute PM data registers
ALL: All previous historical 15-minute PM data registers
Clicking on the Default hyperlink it is possible to set the default value 0.
Number of 1-day: The combobox allows to set the number of 1-day historical registers, specifies the
number of previous 1-day historical PM registers to retrieve in addition to that specified by Mon-itor
Date and Monitor Time. The register specified by these parameters will be the first output fol-lowed by
the Number of 1-day previous registers. The allowable choices are:
from 0 to 7 previous historical 1-day PM data registers
ALL: All previous historical 1-day PM data registers
Issue 01
2 Operation (SDH)

Monitor Date: The comboboxes allow to set the starting date of the PM collection period for which PM
data is to be reported. The allowable choices are:
Month from 01 to 12
Day from 01 to 31
Clicking on the Default hyperlink it is possible to set the default value current date.
Monitor Time: The comboboxes allow to set the starting time of the PM collection period for which PM
Hour from 00 to 23
Minute from 00 to 59
Clicking on the Default hyperlink it is possible to set the default value current hour and beginning of
the current 15-minute window.

Issue 01
2 Operation (SDH)
PM Init Register sub-functional tab
The “PM Init Register” sub-functional tab allows to initialize the current
15-Minute or current 1-Day (specified by Time Period) PM collection
reg-sters for the near- or far-end side (specified by Location) pertaining
to the specified port to the value zero.
1. Select the “PM Init

Register” tab
2. Set the parameters (or click on default)
3. Click on “Save” to save parameters


tree.
Monitor Value: The combobox allows to set specifies the value to be set in the register specified by
Location and Time Period. Only the value 0 is supported.
choices are:
NEND: Near End
FEND: Far End
ALL: All
PM data registers are being retrieved. Only the default value ALL (All monitored types) is supported.
Direction: The combobox allows to specifiy the direction of the signal being monitored (receive or
transmit).
15-MIN
1-DAY
The panel has the Save hyperlink by means of which it is possible to store the settings.

Issue 01
2 Operation (SDH)
Path Overhead Monitoring
NE A W X NE B Y E NE C
HPOM HPOM
before after
AU4 MATRIX AU4

CxC
X Y
HPOM HPOM
after before
• AU4 X:
• HPOM Before Matrix monitors the VC4 in the direction from NE A to NE C
• HPOM After Matrix monitors the VC4 in the direction from NE C to NE A
• AU4 Y:
• HPOM Before Matrix monitors the VC4 in the direction from NE C to NE A
• HPOM After Matrix monitors the VC4 in the direction from NE A to NE C

In case of AU4 pass through, the VC4 is not terminated; however, in such cases it is possible to read the
OH of the VC4 applying the “Higher order Path Overhead Monitoring” function (HPOM). This is just a
monitoring, thus the OH is read from the VC4 inside the incoming AU4 and is rewritten without any
modification in the VC4 of the outgoing AU4.
Similarly for Lower Order where the LPOM (Lower order POM) can be enabled:
On TU12, to monitor the OH of VC12
On TU3, to monitor the OH of VC3
On RSCtp of transponder (1660SM) it’s possible to enable POM RS, that is a POM Before Matrix.

Issue 01
2 Operation (SDH)
Path Overhead Monitoring creation
Before activating the PM on AU4, it’s mandatory to enable at least one

HPOM (EGRESS or INGRESS)
2. Select the “AU List” tab
1. Select the
SDH port
See next page


Issue 01
2 Operation (SDH)
Path Overhead Monitoring creation [cont.]
2. Set the Path Overhead Monitor Function

INGRESS and/or EGRESS = “Y”


Issue 01
2 Operation (SDH)
Path Overhead Monitoring creation [cont.]
HPOM configurations
3. Click on “Save” to save the configurations


Issue 01
2 Operation (SDH)
PM on AU4 (HPOM)
To open the AU4 Performance Monitoring view, select an a AU4 and

then click on “AU PM” tab. Three sub-functional tabs appears in the
window:
1. Select the “AU PM” tab
PM report
PM Init Register
PM Mode
2. Starting from this

point, all the steps to
configure the PM in
the AU4, are the same
as for the “STM PM”
explained in the
previous pages


Issue 01
Blank Page


Issue 01
3 PM on Ethernet Data


Issue 01
Objectives
Performance Monitoring function allow to analyze traffic behavior on a
specific Ethernet interface.
Incoming and Outgoing traffic is analyzed, as well as data traffic lost, or
discarded.
Received
Received
packets
packets
Port 1 Port 2
Transmitted
Transmitted
packets
packets
Port 3 Port 4
Discarded
Discarded
Packets
Packets


Issue 01
Performance Monitoring overview
The system support Ethernet Aggregated octet/frame counters and also

octet/frame counters on per flow (service) basis.
Monitored object:
SDH XC
ETS XC
Received frames Transmitted frames
port A
AU4
SDH
IN OUT
FLOW FLOW
Transmitted frames Received frames
LOCAL Eth. REMOTE

Port Eth. Port


Issue 01
Aggregated Counters
Aggregate counters on Aggregate counters on

Received Frames: Transmitted Frames:
•TRCF •TTDF
•TRCF Broadcast •TTF
•TRCF Multicast •TTF Broadcast
•TRCF Unicast •TTF Multicast
•TRCO •TTF Unicast
•TRDF •TTO
•TRSEF
port A
AU4
SDH
IN OUT
FLOW FLOW
Transmitted frames Received frames

TRCF: number of Total Received Correct Frames

TRCF-Broadcast: number of Total Received Correct Frames of Broadcast type
TRCF-Multicast: number of Total Received Correct Frames of Multicast type
TRCF-Unicast: number of Total Received Correct Frames of Unicast type
TRCO: number of Total Received Correct Ethernet Octets
TRDF: number of Total Discarded Frames on Incoming signal
TRSEF: number of Total Received Service Errored Frames
TTDF: number of Total Discarded Frames on outgoing signal

TTF: number of Total Transmitted Ethernet Frames
TTF-Broadcast: number of Total Transmitted Ethernet Frames of Broadcast type
TTF-Multicast: number of Total Transmitted Ethernet Frames of Multicast type
TTF-Unicast: number of Total Transmitted Ethernet Frames of Unicast type
TTO: number of Total Transmitted Ethernet Octets

Issue 01
Per Flow Counters
Ingress Flow counters: Egress Flow counters:

•TRCFg •TTFg
•TRCFy •TTFy
•TRCOg •TTOg
•TRCOy •TTOy
port A
AU4
SDH
IN OUT
FLOW FLOW

TRCFg: number of Total Received Correct green Frames

TRCFy: number of Total Received Correct yellow Frames
TRCOg: number of Total Received Correct green Ethernet Octets
TRCOy: number of Total Received Correct yellow Ethernet Octets
TTFg: number of Total Transmitted green Ethernet Frames

TTFy: number of Total Transmitted yellow Ethernet Frames
TTOg: number of Total Transmitted green Ethernet Octets
TTOY: number of Total Transmitted yellow Ethernet Octets

Issue 01
PM on local port: configuration
2. Select PM DATA
1. Select the Ethernet port
Values collected since Start Time

The application table area contains, for Ethernet Port resources, the following PM data folders:
Maintenance Rx folder:
TRCF-Broad.: number of Total Received Correct Frames of Broadcast type
TRCF-Mult.: number of Total Received Correct Frames of Multicast type
TRCF-Unic.: number of Total Received Correct Frames of Unicast type
Retrieving Time: time of the last PM data refresh

Issue 01
PM on local port: Polling on Maintenance Rx
1. Start the polling
30 x 2 = 60
Values collected every “Polling Period” seconds by doing Start Polling

Polling: the user can carry out a sampling in real time of the PM data (polling), by choosing the "Polling
Period" and the number of samples ("N. Retries" ), and pressing then on the "Start " key. After finishing
the collection of the requested number of samples, the polling is automatically stopped, if not yet
stopped by the user. Reported values are the difference between current and previous monitoring period;
when the mouse is passed on a value, it pops-up the corresponding absolute value.
Maintenance Rx folder:
TRCF-Broad.: number of Total Received Correct Frames of Broadcast type
TRCF-Mult.: number of Total Received Correct Frames of Multicast type
TRCF-Unic.: number of Total Received Correct Frames of Unicast type

Issue 01
PM on local port: Polling on Maintenance Tx
30 x 2 = 60

Maintenance Tx folder:
TTF: number of Total Transmitted Ethernet Frames
TTF-Broad.: number of Total Transmitted Ethernet Frames of Broadcast type
TTF-Mult.: number of Total Transmitted Ethernet Frames of Multicast type
TTF-Unic.: number of Total Transmitted Ethernet Frames of Unicast type
TTO: number of Total Transmitted Ethernet Octets

Issue 01
PM on local port: Current Data
The operator can start or stop the accumulation of PM events
1. The polling period

must be set in advance

for the PM creation
to start counters


Issue 01
PM on local port: Current Data [cont.]
Measurement available
after PM creation
Choose the granularity

for PM polling Click on “Reset” to reset
the PM counters
Choose the direction for the

Click on Start polling measurement


Issue 01
PM on local port: Current Data polling result


Current Data parameters:

Rx direction:
EINF: Ethernet Incoming Number of Frames
EINB: Ethernet Incoming Number of Bytes
EINF Unicast: Ethernet Incoming Number of Frames of Unicast type
EINF Multicast: Ethernet Incoming Number of Frames of Multicast type
EINF Broadcast: Ethernet Incoming Number of Frames of Broadcast type
EIFE: Ethernet Incoming Frames with Errors
TUF:
Tx direction
EONF: Ethernet Outgoing Number of Frames
EONB: Ethernet Outgoing Number of Bytes
EONF Unicast: Ethernet Outgoing Number of Frames of Unicast type
EONF Multicast: Ethernet Outgoing Number of Frames of Multicast type
EONF Broadcast: Ethernet Outgoing Number of Frames of Broadcast type
Start By OS:

Issue 01
PM on local port: History Data

Historical Data parameters:

Rx direction
EINF: Ethernet Incoming Number of Frames
EINB: Ethernet Incoming Number of Bytes
EINF Unicast: Ethernet Incoming Number of Frames of Unicast type
EINF Multicast: Ethernet Incoming Number of Frames of Multicast type
EINF Broadcast: Ethernet Incoming Number of Frames of Broadcast type
EIFE: Ethernet Incoming Frames with Errors
TUF:
Tx direction
EONF: Ethernet Outgoing Number of Frames
EONB: Ethernet Outgoing Number of Bytes
EONF Unicast: Ethernet Outgoing Number of Frames of Unicast type
EONF Multicast: Ethernet Outgoing Number of Frames of Multicast type
EONF Broadcast: Ethernet Outgoing Number of Frames of Broadcast type
Start By OS:

Issue 01
Inflow measurement
1. Select:
• Connection ETS XC Flow based
Switching (or P2P) or
• Connection Provider Bridge Services
2. Click on Search
3. Select an InFlow


Issue 01
Inflow measurement [cont.]


Issue 01
Inflow measurement [cont.]
1. Choose the granularity

for PM polling
to start counters


Issue 01
Inflow measurement: Current Data
after PM creation
2. Set the polling condition

and click on Start
for PM polling
Polling result

Inflow Current Data parameters:

EINFg: Ethernet Incoming Number of Frames marked green
EINBg: Ethernet Incoming Number of Bytes marked green
EINFy: Ethernet Incoming Number of Frames marked yellow
EINFr: Ethernet Incoming Number of Frames marked red (discarded)
EINBy: Ethernet Incoming Number of Bytes marked yellow
EINBr: Ethernet Incoming Number of Bytes marked red (discarded)
N.B: as the service is only Point-to-Point without traffic classification nor Policing, all frames are marked
green
Start By OS:

Issue 01
Inflow measurement: History Data

Inflow History Data parameters:

EINFg: Ethernet Incoming Number of Frames marked green
EINBg: Ethernet Incoming Number of Bytes marked green
EINFy: Ethernet Incoming Number of Frames marked yellow
EINFr: Ethernet Incoming Number of Frames marked red (discarded)
EINBy: Ethernet Incoming Number of Bytes marked yellow
EINBr: Ethernet Incoming Number of Bytes marked red (discarded)
green
Suspect Interval Flag : it is an indication (True) that the data of the corresponding register may be either
incomplete or invalid
Start By OS:

Issue 01
Outflow measurement
1. Select:
• Connection ETS XC Flow based
Switching (or P2P) or
• Provider Bridge Ethernet Service XC
2. Click on Search


Issue 01
Outflow measurement


Issue 01
Outflow measurement

for PM polling
to start counters


Issue 01
Outflow measurement: Current Data
after PM creation
2. Set the polling condition

and click on Start
1. Choose the granularity for PM polling
Polling result

Outflow Current Data parameters:

EONFg: Ethernet Outgoing Number of Frames marked green
EONBg: Ethernet Outgoing Number of Bytes marked green
EONFy: Ethernet Outgoing Number of Frames marked yellow
EONBy: Ethernet Outgoing Number of Bytes marked yellow
green
Start By OS:

Issue 01
Outflow measurement: History Data

Outflow History Data parameters:

EONFg: Ethernet Outgoing Number of Frames marked green
EONBg: Ethernet Outgoing Number of Bytes marked green
EONFy: Ethernet Outgoing Number of Frames marked yellow
EONBy: Ethernet Outgoing Number of Bytes marked yellow
green
Suspect Interval Flag : it is an indication (True) that the data of the corresponding register may be either
incomplete or invalid
Start By OS:

Issue 01
PM on remote port
To open the Performance Monitoring view, select a VCG and then
choose a VCG member: PTF (select a member) PTF PM.
Three sub-functional tabs appears in the window:
PM Report
PM Init Register
PM Mode


Issue 01
PM Mode sub-functional tab
mode of PM data collection for the specified facility
1. Select the PM Mode tab


Issue 01
PM Mode tab (Set Performance Monitoring Mode)
Set Performance Monitoring Mode page


Access Identifier: The entry box specifies the identifier of the unit resource.
Location: The combobox allows to specify the PM registers location to be activated. The allowable
choices are:
NEND: Near End
FEND: Far End
ALL
Direction: (only for OC-192 port) The combobox allows to specifiy the direction of the signal being
monitored. The allowable choices are:
ALL
RCV: Receive direction for remote port
Mode Type: The entry box specifies the PM mode type to be enabled or disabled. The allow-able
choices are:
ALL
P: Path

Issue 01
PM Mode tab (Set Performance Monitoring Mode) [cont.]
Set Performance Monitoring Mode page
2. Set the State to “ON”

PM State: The combobox allows to set whether the PM data collection for the specified mode type is
enabled or disabled. The allowable choices are:
ON: PM for the specified Mode Type is enabled
OFF: PM for the specified Mode Type is disabled
DISABLED: PM for the specified Mode Type is disabled
Clicking on the Default hyperlink it is possible to set the default value ON.
15-MIN
1-DAY
BOTH

Issue 01
PM Mode sub-functional tab
Click on Retrieve to retrieve

the Mode result


tree.
choices are:
NEND: Near End
FEND: Far End
ALL: All
Direction: The combobox allows to specify the direction of the signal being monitored. The allowable
choices are:
ALL
RCV Receive direction for OT port)
15-MIN
1-DAY

Issue 01
PM Report sub-functional tab

historical 15-minute and/or 1-day PM data corresponding to the PM
data collection register(s) selected for the specified facility.
For each monitored parameter, the current and/or up to thirty-two (32)
15-minute historical PM registers, or the current and/or up to seven (7)
1-day historical PM registers or both 15-minute and 1-day PM registers
can be retrieved.
1. Select the PM Report tab
2. Click on Retrieve to retrieve the last PM result


LEVEL> is reported.
LEVEL> is reported.
NEND: Near End
FEND: Far End
ALL: All

Issue 01
PM Report sub-functional tab [cont.]

Direction: The combobox allows to specifies the direction of the signal being monitored (receive or
transmit). Only the value RCV (receive) is supported.
Clicking on the Default hyperlink it is possible to set the default value RCV.
Time Period: The combobox allows to specifies the accumulation time period for the retrieved per-
formance monitoring information. The allowable choices are:
15-MIN
1-DAY
BOTH

Issue 01
PM Report sub-functional tab [cont.]

Month from 01 to 12
Day from 01 to 31
Hour from 00 to 23

Issue 01
PM Result

Validity:
PRTL (Partial): the data corresponding to the specific interval is not completed, as the period is the
current one not yet expired
COMPL (Completed): the data belong to a completed time period

Issue 01
PM Init Register sub-functional tab
The PM Init Register sub-functional tab allows to initialize the current

registers for the near- or far-end side (specified by Location) pertaining
1. Select the PM Init

Register tab
2. Set the parameters (or

3. Click on Save to save click on default)
parameters


choices are:
NEND: Near End
FEND: Far End
ALL: All
transmit). Only the default value RCV (receive) is supported.
15-MIN
1-DAY

Issue 01
4 PM on T-MPLS


Issue 01
4 PM on T-MPLS
Performance Monitoring overview
The Performance Monitoring tool allows to activate, collect and display

performance data associated with the Pseudowire and the T-MPLS
tunnel.
Monitored object:
PWSEG (Bid)
Eth local port
Outgoing packet
PW Bid
Incoming packet
TUSEG#x
(Bid)


Issue 01
4 PM on T-MPLS
PM on PseudoWire (or Tunnel): PM Set
To activate the Performance Monitoring counters, select a Pseudowire (or a
Tunnel) and then click on “Performance Monitoring”
Four sub-functional tabs

appears in the window:
PM Report
PM Initialization
PM Mode
PM Set
1. Select PM Set
2. Set the State to “ON” and

choose the time period


Issue 01
4 PM on T-MPLS
PM on PseudoWire (or Tunnel): PM Report
Display Performance Monitoring result:

4. Select PM Report
5. Set retrieve parameters


LEVEL> is reported.
LEVEL> is reported.
Monitored Counter Type: The combobox allows to specifies the type of monitored counter whose PM
data registers are being retrieved. The allowable choices are:
MINB: Number of Monitored Incoming Bytes
MONB: Number of Monitored Outgoing Bytes
MINP: Number of Monitored Incoming Packets
MONP: Number of Monitored Outgoing Packets

Issue 01
4 PM on T-MPLS
PM on PseudoWire (or Tunnel): PM Report [cont.]
Display Performance Monitoring result:
6. Click on “Retrieve”

Time Period: The combobox allows to specifies the accumulation time period for the retrieved per-
formance monitoring information. The allowable choices are:
15-MIN
1-DAY
BOTH
Number of 15-minute/1-Day Historical Register : The combobox refers to 15 min or 1 day according to
the Time period select. It allows to set the number of 15-minute (1 day) historical registers, specifies
the number of previous 15-minute (1 day) historical PM registers to retrieve in addition to that specified
by Monitor Date and Monitor Time. The register specified by these parameters will be the first output
followed by the Number of 15-minute (1 day) previous registers. The allowable choices are:
From 1 to 7 previous historical 1-day PM data registers
ALL: All previous historical PM data registers
Month from 01 to 12
Day from 01 to 31
Hour from 00 to 23

Issue 01
4 PM on T-MPLS
PM on PseudoWire (or Tunnel): PM Result

Validity:
PRTL (Partial): the data corresponding to the specific interval is not completed, as the period is the
current one not yet expired
COMPL (Completed): the data belong to a completed time period

Issue 01
4 PM on T-MPLS
PM on PseudoWire (or Tunnel): PM Mode
The PM Mode sub-functional tab allows to retrieve the PM Mode values

that are:
Time Period: Specifies the time interval for the which the report is being
generated. The values are 15MIN, 1DAY, or BOTH. The default value is BOTH.
1. Select PM Initialization
2. Select the time period
3. Click on “Retrieve”


Issue 01
4 PM on T-MPLS
PM on PseudoWire (or Tunnel): PM Initialization
The PM Initialization sub-functional tab allows to initialize the current

registers.
1. Select PM Initialization
3. Click on “Save” 2. Select the PM registers to be initialized


Issue 01
5 PM on OTN


Issue 01
5 PM on OTN
Introduction
The following Near-end OTUk Section layer parameters shall be

monitored for OTN interfaces per ITU-T G.709 and G.8201:
Background Block Errors - (BBE-OTU): Count of BIP-8 (SM BIP-8) errors. It is
done for all seconds in which there is no URU-O, URU-S, LOF, LOM, LOS or
AIS.
Errored Seconds - (ES-OTU): Count of seconds with (SM BIP-8) Errors ≥1. The
count is also done when LOF1 True or LOM True or LOS True or AIS=True or
TIM-S=True or URU-O=True or URU-S=True.
Severely Errored Seconds - (SES-OTU)): Count of seconds with (SM BIP-8)
Errors ≥ x². The count is also done when LOF True or LOM=True or LOSTrue
or AIS=True or TIM-S=True or URU-O=True or URU-S=True.
Unavailable Seconds – (UAS-OTU): A second of Unavailability which begins at
the on-set of 10 contiguous SES-OTUs and ends at the on-set of 10 contiguous
seconds with no SES-OTUs.
FEC Corrected Errors – (FECC): Count of FEC Errors Corrected3 and LOS =False
and LOD = False. FECC counter is incremented by the number of FEC errors
corrected in each second in which no LOS or LOF have been detected.


Issue 01
5 PM on OTN
The following Far-end OTUk Section layer parameters shall be

monitored for OTN interfaces per ITU-T G.709 and G.8201.
Background Block Errors - (BBE-OTU): Count of BEI ≥ 1 (SM BEI). It is done for
all seconds in which there is no URU-O, URU-S, LOF, LOM, LOS or AIS
Errored Seconds - (ES-OTU): Count of seconds with BEI ≥ 1 (SM BEI). The
Count is also done when LOF True or LOM True or LOS True or AIS=True or
TIM-S=True or URU-O=True or URU-S=True.
Severely Errored Seconds - (SES-OTU)): Count of seconds with BEI ≥ x² (SM
BEI). The Count is also done when LOF True or LOM =True or LOSTrue or
AIS=True or TIM-S=True or URU-O=True or URU-S=True.
Unavailable Seconds – (UAS-OTU): A second of Unavailability which begins at
the on-set of 10 contiguous SES-OTUs and ends at the on-set of 10 contiguous
seconds with no SES-OTUs.


Issue 01
5 PM on OTN
PM on DWLA10X board
2. Select the line side XFP (Module 1)

select the DWDM Line Selector
panel and click on Select Line
4. Select the OUT PM LINE tab


Issue 01
5 PM on OTN
PM on DWLA10X board: PM configuration


Location: Specifies the location. The values are NEND, FEND, or ALL. The default value is ALL.
Mode Type: Specifies the mode type requires to be set. The values are ALL, S. The default value is
ALL.
RCV.
related to UTC.

Issue 01
5 PM on OTN
PM on DWLA10X board: PM configuration [cont.]
to retrieve the
Mode result


tree.
choices are:
NEND: Near End
FEND: Far End
ALL: All
choices are:
ALL
15-MIN
1-DAY

Issue 01
5 PM on OTN
retrieved.


tree.
LEVEL> is reported.
LEVEL> is reported.
NEND: Near End
FEND: Far End
ALL: All

Issue 01
5 PM on OTN

choices are:
15-MIN
1-DAY
BOTH

Issue 01
5 PM on OTN

Month from 01 to 12
Day from 01 to 31
Hour from 00 to 23

Issue 01
5 PM on OTN
PM on DWLA10X board: PM Init Register sub-functional tab

Register” tab


tree.
choices are:
NEND: Near End
FEND: Far End
ALL: All
transmit).
15-MIN
1-DAY

Issue 01
5 PM on OTN
PM on 1POTU2/1POTU2XB board

select the Payload carries panel
and click on Select Line
3. Select the OUT PM LINE tab


Issue 01
5 PM on OTN
PM on 1POTU2/1POTU2XB board: PM configuration


ALL.
RCV.
related to UTC.

Issue 01
5 PM on OTN
PM on 1POTU2/1POTU2XB board: PM configuration [cont.]
to retrieve the
Mode result


tree.
choices are:
NEND: Near End
FEND: Far End
ALL: All
choices are:
ALL
15-MIN
1-DAY

Issue 01
5 PM on OTN
retrieved.


tree.
LEVEL> is reported.
LEVEL> is reported.
NEND: Near End
FEND: Far End
ALL: All

Issue 01
5 PM on OTN

choices are:
15-MIN
1-DAY
BOTH

Issue 01
5 PM on OTN

Month from 01 to 12
Day from 01 to 31
Hour from 00 to 23

Issue 01
5 PM on OTN
PM on 1POTU2/1POTU2XB board: PM Init Register sub-functional tab

Register” tab


tree.
choices are:
NEND: Near End
FEND: Far End
ALL: All
transmit).
15-MIN
1-DAY

Issue 01
Blank Page


Issue 01
6 PM on ATM


Issue 01
6 PM on ATM
PM on PP10GATM board
select the Path Termination Function
Selection panel and select the ATM port
1. Select the PP10GATM board
3. Click on View ALL or Continue
4. Select the PTF PM tab


Issue 01
6 PM on ATM
PM on PP10GATM board: PM configuration

ALL.
RCV.
related to UTC.

Issue 01
6 PM on ATM
PM on PP10GATM board: PM configuration [cont.]
Click on “Retrieve” to
retrieve the Mode result


tree.
choices are:
NEND: Near End
FEND: Far End
ALL: All
choices are:
ALL
15-MIN
1-DAY

Issue 01
6 PM on ATM
retrieved.


tree.
LEVEL> is reported.
LEVEL> is reported.
NEND: Near End
FEND: Far End
ALL: All

Issue 01
6 PM on ATM

choices are:
15-MIN
1-DAY
BOTH

Issue 01
6 PM on ATM
PM on PP10GATM board : PM configuration [cont.]

Month from 01 to 12
Day from 01 to 31
Hour from 00 to 23

Issue 01
6 PM on ATM
PM on PP10GATM board : PM Init Register sub-functional tab

Register” tab


tree.
choices are:
NEND: Near End
FEND: Far End
ALL: All
transmit).
15-MIN
1-DAY

Issue 01
7 PM on PDH


Issue 01
7 PM on PDH
PM on P63E1 board
1. Select the PDH Access Shelf
2. Scroll the window up to the bottom, select

the PDHLOVC12/E1 Selection panel and
2. Select the P63E1 board Select the VC12


Issue 01
7 PM on PDH
PM on P63E1 board: PM configuration

ALL.
RCV.
related to UTC.

Issue 01
7 PM on PDH
PM on P63E1 board: PM configuration [cont.]
to retrieve the
Mode result


tree.
choices are:
NEND: Near End
FEND: Far End
ALL: All
choices are:
ALL
15-MIN
1-DAY

Issue 01
7 PM on PDH
retrieved.
5. Choose the parameters


tree.
LEVEL> is reported.
LEVEL> is reported.
NEND: Near End
FEND: Far End
BIDIR: both direction
ALL: All
Issue 01
7 PM on PDH

choices are:
TRMT: TX direction
RCV: Rx direction
15-MIN
1-DAY
BOTH
Issue 01
7 PM on PDH

Month from 01 to 12
Day from 01 to 31
Hour from 00 to 23

Issue 01
7 PM on PDH
PM on P63E1 board: PM Init Register sub-functional tab
1. Select the “PM Init Register” tab


tree.
choices are:
NEND: Near End
FEND: Far End
ALL: All
transmit).
15-MIN
1-DAY

Issue 01
8 PM on CES


Issue 01
8 PM on CES
PM on PP2G5UGW board
the Path Termination Function Selection
panel and select the remote port
1. Select the PP2G5UGW board


Issue 01
8 PM on CES
PM on PP2G5UGW board: PM configuration
3. Click on “Save” to save

the parameters.

ALL.
RCV.
related to UTC.

Issue 01
8 PM on CES
PM on PP2G5UGW board: PM configuration [cont.]


tree.
choices are:
NEND: Near End
FEND: Far End
ALL: All
choices are:
ALL
15-MIN
1-DAY

Issue 01
8 PM on CES
retrieved. 4. Select the PM Report tab
5. Choose the parameters


tree.
LEVEL> is reported.
LEVEL> is reported.
NEND: Near End
FEND: Far End
ALL: All

Issue 01
8 PM on CES

choices are:
15-MIN
1-DAY
BOTH

Issue 01
8 PM on CES
PM on PP2G5UGW board : PM configuration [cont.]

Month from 01 to 12
Day from 01 to 31
Hour from 00 to 23

Issue 01
8 PM on CES
PM on PP2G5UGW board : PM Init Register sub-functional tab
1. Select the “PM Init Register” tab


tree.
choices are:
NEND: Near End
FEND: Far End
ALL: All
transmit).
15-MIN
1-DAY

Issue 01
8 PM on CES
PM on PP2G5UGW board: PM on VC-12
4. Select the VC12 Select tab
5. Select the relevant TU12



Issue 01
8 PM on CES
PM on PP2G5UGW board: PM on VC-12 [cont.]
7. Select the VC12 PM tab

ALL.
RCV.
related to UTC.

Issue 01
8 PM on CES

the parameters.

ALL.
RCV.
related to UTC.

Issue 01
8 PM on CES


tree.
choices are:
NEND: Near End
FEND: Far End
ALL: All
choices are:
ALL
15-MIN
1-DAY

Issue 01
8 PM on CES
retrieved. 4. Select the “PM Report” tab
5. Choose the options to

display the results


tree.
LEVEL> is reported.
LEVEL> is reported.
NEND: Near End
FEND: Far End
ALL: All

Issue 01
8 PM on CES
PM on PP2G5UGW board: PM on E1
4. Select the E1 Select tab
6. Click on Continue 5. Select the relevant TU12


Issue 01
8 PM on CES
PM on PP2G5UGW board: PM on E1 [cont.]
7. Select the E1 PM tab

ALL.
RCV.
related to UTC.

Issue 01
8 PM on CES

the parameters.


Issue 01
8 PM on CES


tree.
choices are:
NEND: Near End
FEND: Far End
ALL: All
choices are:
ALL
15-MIN
1-DAY

Issue 01
8 PM on CES
retrieved. 4. Select the “PM Report” tab


tree.
LEVEL> is reported.
LEVEL> is reported.
NEND: Near End
FEND: Far End
ALL: All

Issue 01
8 PM on CES
PM on CES service: introduction
1850 TSS-320/160 provides the user the ability to enable/disable the

performance monitoring functionality per CES session.
The ES counter shall be incremented whenever any of the following
anomalies occurred during the monitored one-second interval:
At least one packet lost
At least one stray packet received
At least one malformed packet received
At least one buffer overrun event occurred
At least one buffer underrun event occurred
The SES (and ES) counters shall be incremented whenever any of the
following defects is detected during the monitored one-second interval:
Packet loss state
Excessive packet loss state
Stray packets
Malformed packets
Buffer overrun
Buffer underrun


Issue 01
8 PM on CES
PM on CES service: introduction [cont.]
The FEES counter shall be incremented whenever following anomaly

occurred during the monitored one-second interval:
At least one remote packet loss indication received
The FESES (and FEES) counters shall be incremented whenever
following defect is detected during the monitored one-second interval:
Remote packet loss


Issue 01
8 PM on CES
PM on CES service
2. Click on Statistics


Issue 01
8 PM on CES
PM on CES service: configuration
1. Select Mainteinance RX tab

30 x 2 = 60

Polling: the user can carry out a sampling in real time of the PM data (polling), by choosing the "Polling
Period" and the number of samples ("N. Retries" ), and pressing then on the "Start " key. After finishing
the collection of the requested number of samples, the polling is automatically stopped, if not yet
stopped by the user. Reported values are the difference between current and previous monitoring period;
when the mouse is passed on a value, it pops-up the corresponding absolute value.
1850 TSS-320/160 supports the following near-end CES PM counters:

Missing packets - Number of missing packets (as detected via control word sequence number gaps).
Packets reorder - Number of packets detected out of sequence (via control word sequence number) but
successfully re-ordered.
Buffer underruns - Number of times a packet needed to be played out and the jitter buffer was empty.
Buffer overruns - Number of times when the jitter buffer could not accommodate newly arrived
packets.
Misorder dropped packets - Number of packets detected out of order (via control word sequence
numbers) that could not be re-ordered.
Malformed packets - Number of packets detected with unexpected size or bad headers' stack.

Issue 01
8 PM on CES
PM on CES service: Current Data
The operator can start or stop
the accumulation of PM events
1. Select Current Data tab
2. The polling period must

be set in advance

for the PM creation
4. Click on Create PM to start counters


Issue 01
8 PM on CES
PM on CES service: Current Data [cont.]
Choose the granularity

for PM polling
Choose the direction for the

Click on Start polling measurement


Issue 01
8 PM on CES
PM on CES service: Current Data polling result
Select the Current Data



Issue 01
8 PM on CES
PM on CES service: History Data

1850 TSS-320/160 supports the following near-end and far-end CES PM counters:
Missing packets - Number of missing packets (as detected via control word sequence number gaps).
Packets reorder - Number of packets detected out of sequence (via control word sequence number) but
successfully re-ordered.
Buffer underruns - Number of times a packet needed to be played out and the jitter buffer was empty.
Buffer overruns - Number of times when the jitter buffer could not accommodate newly arrived
packets.
Misorder dropped packets - Number of packets detected out of order (via control word sequence
numbers) that could not be re-ordered.
Malformed packets - Number of packets detected with unexpected size or bad headers' stack.
FEES - Number of Far-end Errored Seconds.
FESES - Number of Far-end Severily Errored Seconds.
FEUAS - Number of Far-end Unavailable seconds.

Issue 01
9 PM Global File


Issue 01
9 PM Global File
PM global file collection
NE prepares a file set with all PM history data This file set may be
transferred via file transfer to the management system
States of the related state machine will be reported via transient
conditions


Issue 01
9 PM Global File
PM global file collection
1. Select System Management -> PM global File
2. Click on “Start PM Global File”


Issue 01
9 PM Global File
PM global file collection : Perform Copy (backup)
All the history data, referred to a fully equipped configuration, can be

saved in the PM global file which can be transferred to a remote server
for further analysis.
1. Select System Management -> DB Management -> Remote File -> Perform Copy
See next page

Only one of this option can be active on an NE at any given time.

This option initiates the file upload/download operation and returns a complete response once the
operation has been verified as possible and initiated. During the subsequent file transfer, the answers are
generated every 30 seconds (+/- 15 seconds) to indicate the percentage of completion of the file transfer
and the final completion status. During the transfer period, a Cancel Copy option can be used to abort
the operation.
The command is used for data base transfer operations to and from remote devices (RFS) located in an IP-
based DCN (Data Communication Network) via the ftp File Transfer Protocol.

Issue 01
9 PM Global File
PM global file collection : Perform Copy (backup) [cont.]
As already done for the DB backup transfer to remote PC, it is possible

to save the PM global file into a remote PC.
2. Choose From and To taking into account the table present in the note page
See next page

Valid AID / input parameters combinations
The Copy Remote File panel contains:

From: The combobox supports the following input parameters:
Secondary Backup Database (STDBYDB) The system's secondary backup database. It represents the
secondary backup database that has been either created as copy of the primary backup database (by the
Perform DB Backup option), or has been downloaded from RFS (by this option). A secondary backup
database becomes the active database only by being activated via the Restore Database option. There is
one instance of secondary backup database in the system.
Remote File Server Database (RFSDB) A database backup on a Remote File Server. It represents a database
on a Remote File Server. Multiple instances of RFSDB can exist in different locations on an RFS.
Remote File Server Software (RFSSW) A software generic on a remote file server. It represents a software
generic on a Remote File Server. Multiple instances of RFSSW can exist in different locations on an RFS.
Local NE PM Global file collection (LOCPMGLB):
To: The combobox supports the following input parameters:

Database Backup on a Remote File Server (RFSDB) A database backup on a Remote File Server.
Secondary Backup Database (STDBYDB) The system's secondary backup database.
Standby Software Generic (STBYSW) The standby software generic on the NE.
Remote File server PM Global File collection (RFSPMGLB)

Issue 01
9 PM Global File
PM global file collection : Perform Copy (backup) [cont.]
3. Insert the location parameters
4. Do Apply

Location: The following fields indicates the source/destination of the files on an RFS (Remote File Server)
to be transferred. The fields are:
User: The entry box allows to digit the user identifier used for the ftp connection on the RFS.
Password: The entry box allows to digit the user password used for the ftp connection on the RFS.
Host: The entry box allows to digit the IP address of the host (the Remote File Server)
Port: The entry box allows to digit the port number to connect to. Most schemes designate protocols
that have a default port number. The default port number for ftp is 21.
URL Path: The entry box allows to digit the details of how the specified resource (i.e. the directory
where the file(s) reside) can be accessed. It has the following syntax:
[/]<cwd1>/<cwd2>/.../<cwdN>where <cwd1> through <cwdN> are strings that identify directories.
Command Mode: The combobox allows copying an RFS DB to the secondary backup database on the system.
Forced: The operation is performed, regardless of the following:
the BACKUP-DATE and BACKUP-TIME on the RFS DB (represented in the label on the RFS database) is
older/prior to the BACKUP-DATE and BACKUP-TIME on the system
the SID indicated on the RFS DB does not match the SID of the system.
the software release/identifier indicated for RFS DB does not match the software release identifier
indicated for the system.
Normal (default value): The command is denied if there is a mismatch between the SID, the release
identifier, system stream, system type or the backup time stamp of the system and the information
stored in the source database.
The Default hyperlink allows to set Normal automatically.
Overwrite: The combobox allows copying the secondary backup database to an RFS DB. Indicates whether
existing files should be overwritten.
Yes: Overwrite the existing files listed for the TO AID.
No (default value): Do not overwrite the existing files listed for the TO AID.
Issue 01
9 PM Global File
PM global file transfer
Opening with notepad the file, all the PM counters stored in teh FLC
are available to further analysys


Issue 01
9 PM Global File
PM global file transfer [cont.]

PP is the facility and the setting of the PNM on it

ME is the type of error followed by the amount
BL is the block, the timeslot on which the counter recorded the ME. It carries also the info about the
elapsed time.

Issue 01
Blank Page


Issue 01
End of Module
Monitoring


Issue 01
41
Section 4
Maintenance
Module 1
Backup & Restore
Issue 01
1850 TSS-320 & 1850 TSS-160

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

Issue 01
Blank Page

Maintenance Backup & Restore
Document History

Issue 01
Module Objectives
Explain to create a backup of the NE database

Describe the restore on available backup


Issue 01


Issue 01
Table of Contents
Page
1 Backup & Restore 7


Issue 01

Maintenance Backup & Restore This page is left blank intentionally

Issue 01
1 Backup & Restore

Maintenance Backup & Restore Section 4 Module 1 Page 7

Issue 01
1.Backup & restore
MIB definition
Database types
An NE maintains all its configuration in a volatile memory database.
Non-volatile disk backup databases are maintained implicitly by the NE,
and explicitly by operator commands. The NE is able to restore its
memory database from the contents of a disk backup database at
restart time or triggered by an operator command.
The NE provides mechanisms to transfer a locally stored disk database
backup to an RFS and vice versa.
The NE allows operator to reset its memory and primary backup
database to a factory installed default configuration.
The volatile memory database is maintained by the NE and reflects the
NE configuration, its alarm states and conditions. Two non-volatile disk
database types exist for the NE: the primary backup database and the
secondary backup data base .

Maintenance Backup & Restore Section 4 - Module 1 - Page 8
MIB: Management Information Base

Issue 01
1.Backup & restore
MIB definition [cont.]
The primary backup database is maintained implicitly by the NE during

its normal operation. At any time, it reflects the state of the NE's
volatile memory database. Updating the primary backup database
occurs online without interrupting the NE's normal service operation.
The primary backup database can be copied to the secondary backup
database by an operator command (backup). The secondary backup
database can be copied to the primary backup database. After an FLC
restart (or FLC switch) the memory database will be reloaded from the
restored disk database.
The secondary backup database can be copied to/from a remote file
server (RFS) by operator commands (remote backup and remote
restore).
The NE disk is considered to be part of the L1 controller board. In case
of a redundant L1 controller configuration, the system assures
consistency of disk contents between active and standby L1 controller.
It is therefore assumed that all locally stored backup databases are
consistent between the redundant L1 controllers of the NE without
need for specific operator action.
The NE assures that:

- a download of database backups from RFS does not exceed the free disk space on the FLCs‘ disks. The file
transfer command is denied if the free FLC disk space is not sufficient to store the remote database
backup.
The creation of a local database backup on the FLC does not exceed the free disk space on the FLCs‘ disks.
The backup creation command is denied if the free FLC disk space is not sufficient to create a local
database backup.

Issue 01
1.Backup & restore
The system is responsible to replicate any change to disk database on

the active L1 controller to the corresponding disk database on standby
L1 controller (if available).
In particular, the implementation of the operations for creation of a
database backup and download of a database backup to the disk on the
active L1 controller is expected to have the corresponding effects on
the disk of the standby L1 controller.
After a reboot or insertion of a standby FLC, the FLC status LED
indicates a status of Software Download until the standby database
image is synchronized with the primary.
Any failures in updating the database is reported by the NE.
The NE prevents inadvertent restoration of an obsolete, corrupt or
empty database or database from another system. By default the NE
only allows to restore the most recent backup. The system incorporates
timestamp checks, system ID comparisons, etc.., but allow a forced
override by a sufficiently privileged user.


Issue 01
1.Backup & restore
The system restores the memory database from the primary backup
database when initializing the NE.
No more than one backup, restore, or software download operation are
allowed at a time on the NE.
The NE supports the ability to transfer the secondary backup database
to and from a Remote File Server (upload and download).
Information includes the SID, NE type, and release of the NE on which
the backup took place, and the date and time at which the backup
occurred.
The correct file size of a remotely stored disk databases is verified
before downloading the database to the NE.
The file transfer functionality works with any RFS supporting an IP
connection, a standard ftp file server.


Issue 01
1.Backup & restore
L1 CPU
Database Management

Database Types
The following database types are provided for the NE:
ACTV CPU DB: Database in volatile memory (e.g. RAM on the L1 controller). At FLC (re-) start time the
contents of the ACTV DSK DB is copied into the ACTV CPU DB
ACTV DSK DB: Primary backup database on the NE's disk. This database is also used to automatically restore
the ACTV CPU DB on system initialization
STDBY DB: Secondary backup database on the NE's disk. This database is created during a successful backup
operation. It can be copied to the ACTV DSK DB and ACT CPU DB during a successful restoration operation.
The STDBY DB can also be copied to/from the RFS
DFLT DB: Factory default configuration provided for the NE during system installation time. The factory
default configuration is not necessarily a database in the strict sense but may be a fixed set of
configuration values
RFS DB: Remote File Server Database. This database can be copied to the STDBY DB during a successful file
transfer operation

Issue 01
1.Backup & restore
Database operations
DB management menu supports the following operations:
Data Base for Data base management.
Remote File for Data base from Remote File Server management.


Issue 01
1.Backup & restore
Data Base menu
This database menu option is joined with these choices:

Perform DB Backup It backs up the primary backup data base to the
secondary backup data base.
Cancel DB Backup It cancels (aborts) a database backup currently in
progress.
Restore DB It copies the backup database stored on secondary backup
database to the primary backup database and resets the system to activate
the new database.
DB Information It reads the database label of the selected backup database
stored on the NE.


Issue 01
1.Backup & restore
Data Base menu: Perform DB backup
1. Select System Management -> DB Management -> Data Base -> Perform DB Backup
Wait for a while
2. Do Yes

This option backs up the whole NE provisioning and configuration database, excluding Performance
Monitoring History Data, current alarm situation, and event log data; in addition to the database, also
writes the system type, the software release identifier, the site identifier, the backup date and time
stamp to the secondary backup database.
The system also writes a CRC (Cyclic Redundancy Check) to the secondary backup database.
Any database backup currently in-progress can be aborted (cancelled) by the Cancel DB Backup option. If an
in-progress database backup is cancelled, an unsuccessful response message is generated for this option
and the system may mark via the database header the backed-up data on the secondary backup database
as "invalid" (depending on the timing of the cancellation) so that it cannot be inadvertently used for a
subsequent database restoral or remote database backup.
Alarms are not part of the backup, neither alarms active when the backup was started, nor alarms being
raised during the backup is created. Alarms should be cleared before performing database backups. Note:
when a database backup is restored, the NE is will perform an alarm resynchronization to update its
alarm database to the current alarm situation.

Issue 01
1.Backup & restore
Data Base menu: Cancel DB backup
1. Select System Management -> DB Management -> Data Base -> Cancel DB Backup
Wait for a while

2. Do Yes

This option cancels (aborts) a database backup currently in progress.

If an in-progress database backup is cancelled, a message indicates the cancellation is generated for this
action and the system may mark via the database header the backed-up data on the secondary backup
data-base as "invalid" (depending on the timing of the cancellation) so that it cannot be inadvertently
used for a subsequent database restoral or remote database backup.

Issue 01
1.Backup & restore
Data Base menu: Restore DB
1. Select System Management -> DB Management -> Data Base -> Restore DB
2. Choose the command:

Normal
Forced
3. Do Apply

This option copies the backup database stored on secondary backup database to the primary backup data-
base and resets the system to activate the new database.
When this option is executed, provisioning and database effects of TL1 commands issued since the time the
backup was made, until the completion of a database restoral, are lost.
The database restoral operation verifies the System Type, software release identifier, the date and time of
the backup creation, and Site ID (SID) of the system against the corresponding data stored along with the
secondary backup database. A database restoral with a System Type mismatch cannot be performed. A
data-base restoral with a software release identifier or SID mismatch cannot be performed unless the
command mode parameter is set to FRCD. A database restoral with backup creation date and time
different from the most recent backup created on the system cannot be performed unless the command
mode parameter is set to FRCD.
The database restoral operation also verifies the CRC (Cyclic Redundancy Check) calculated for the data-
base from the secondary backup database against the CRC stored for the database. A database restoral
with a CRC mismatch cannot be performed.
The Restore Database panel contains the combobox:
Command Mode: It allows to assign the command mode of the action. The values are:
Forced: The database restoral operation is performed regardless both the BACKUP-DATE, BACKUP-
TIME indicated for the secondary backup database is older/prior to the BACKUP-DATE, BACKUP-TIME
on the system (represented in label of the Active Local Primary Hard disk Data-base) and the SID
indicated on the STBY DB does not match the SID of the system.The software release identifier
indicated for the secondary backup database does not match the software release identifier indicated
for the system.
Normal: The command is denied if there is a mismatch between the SID, the software release
identifier, system type or the backup time stamp of the system and the information stored in the
secondary backup database.Clicking on Default hyperlink the Normal mode is set.

Issue 01
1.Backup & restore
Data Base menu: DB Information
1. Select System Management -> DB Management -> Data Base -> DB Information
2. Choose the access identifier:

Primary Backup DB or
Secondary Backup DB
3. Do Retrieve

This option reads the database label of the selected backup database stored on the NE (primary backup DB
or secondary backup DB).
The successful output response for this action displays one output line per selected database. The output
displays the database AID and the associated database label. The unsuccessful output response for a
RTRV-DB-LABEL command displays a separate line of data.
A value for the calculated CRC is only returned in a successful response if the selected secondary backup
database location contains a valid database.
The DB Information panel contains :
Access Identifier: It allows to identify the database. The values are:
Primary backup database (ACTDSKDB)
Secondary backup database (STDBYDB)

Issue 01
1.Backup & restore
Remote file menu: Remote Database Backup
The NE provides for transfer database files from the local storage area
on the disk to a remote storage area on a RFS and vice-versa. Using this
capability, operators can perform remote database backup and remote
database restore.
The Remote file menu option is joined with these choices:
Perform Copy It copies secondary backup database on the NE from/to
specified locations on a Remote File Server (RFS).
Cancel Copy It interrupts an in-progress file transfer previously intitiated.
File Information It is used to read information related to transferred files on
a Remote File Server.

The remote file transfer process is performed with minimal impact to system performance (e.g., protection
switch times, response times doesn’t impact enough to cause investigation by the casual user).
The remote file transfer functionality works with any RFS supporting an IP connection and the FTP protocol
as defined in RFC-959 and the RSYNC protocol for differential file transfer.
Only one originating remote file transfer is allowed on a system at any given time.
The system reports to the managing system the percentage and remote file transfer status of the file
transfer every 30 seconds after file transfer initiation and during file transfers to/from an RFS.
The NE provides an operator with the capability to interrupt an in-progress file transfer that was previously
initiated.
In case a remote download file transfer is autonomously or manually cancelled, all files already transferred
on the NE are removed.

Issue 01
1.Backup & restore
Remote file menu: Remote Database Backup [cont]
The process of backing up can be split in two different phases:

first, create a backup database on the NE;
second, send this backup database to its remote storage destination.
Figure 2. depicts the general principle for the backup of an NE database
on a Remote File Server:

(1) The OS sends a command to setup the database backup image in the backup partition (i.e. ACT-DB-
BACKUP).
(2) The OS sends a command to the NE to trigger the backup to the RFS (i.e. COPY-RFILE).
(3) The NE sends a message to the RFS initiating the file transfer.
(4) The NE sends a message to the OS, indicating that the file transfer is on its way (COPY-RFILE command
completion).
(5) The NE sends a message to the OS, indicating that the file transfer is on its way (i.e. REPT^COPY^RFILE).
(6) During the transfer process, messages are sent to the OS to keep it informed of the progress (i.e.
REPT^COPY^RFILE).
(7) When the transfer is completed, the NE sends a completion message to the OS (i.e. REPT^COPY^RFILE).
Upon receipt of a Copy Remote File Database Backup Request, an NE validates the file transfer, initiate a
file transfer connection and transfer the database to the remote location (COPY-RFILE TL1 command pro-
vides this functionality with the AIDs FROM=STDBYDB and TO=RFSDB).
In order to check, during the restoration process, if the backup is compatible with the NE on which it is
restored, without first having to do a complete download of the database, the database label information
is stored in a separate descriptor file for each database backup stored on the NE or on the RFS. The
descriptor file is kept in the same path as the database backup.
The system, by default, doesn’t allow the transfer of a database to a remote location where a backup with
the same location/database name already exists.

Issue 01
1.Backup & restore
Remote file menu: Remote Database Restoration
The process of restoring an NE’s working database is two fold:

first, download a backup from a remote location onto a target NE;
second, restart the NE with the downloaded database.

(1) The OS sends a command to the NE to trigger the remote transfer from the RFS (i.e. COPYRFILE).
(2) The NE sends a message to the RFS to retrieve the descriptor file (containing the database label) from
the RFS.
(3) The NE requests the backup from the RFS and begins storing it on the hard disk.
(4) The NE sends a message to the OS, indicating that the file transfer is on its way (COPY-RFILE command
completion).
(5) The NE sends a message to the OS, indicating that the file transfer is on its way (i.e. REPT^COPY^RFILE).
(6) During the transfer process, messages are sent to the OS to keep it informed of the progress (i.e.
REPT^COPY^RFILE).
(7) When the transfer is completed, the NE sends a completion message to the OS (i.e. REPT^COPY^RFILE).
(8) The OS sends commands to the NE to trigger the activation of the restored database (i.e. RESTORE-DB).
The system provides a command to download and restore a previously backed up database from a Remote
File Server to an NE.
Prior to downloading a backup, the restore procedure downloads first the database descriptor file and
perform the following checks:
Validation of the descriptor file itself by an CRC check.
If the system type of the NE is not identical to the one of the RFS database being restored, the transfer
fails.
If the software release of the NE is not identical to the one of the RFS database being restored, the
transfer fails, unless an option is used to force the transfer.
If the SID of the NE is not identical to the one of the RFS database being restored, the transfer fails,
unless an option is used to force the transfer.
If the date/time stamp of the RFSDB is older/prior to the date/time stamp of the primary backup
database on the system, the transfer fails, unless an option is used to force the transfer

Issue 01
1.Backup & restore
Remote file menu: Perform Copy (backup)
See next page

Only one of this option can be active on an NE at any given time.

This option initiates the file upload/download operation and returns a complete response once the
operation has been verified as possible and initiated. During the subsequent file transfer, the answers are
generated every 30 seconds (+/- 15 seconds) to indicate the percentage of completion of the file transfer
and the final completion status. During the transfer period, a Cancel Copy option can be used to abort
the operation.
The command is used for data base transfer operations to and from remote devices (RFS) located in an IP-
based DCN (Data Communication Network) via the ftp File Transfer Protocol.

Issue 01
1.Backup & restore
Remote file menu: Perform Copy (backup) [cont.]
2. Choose From and To taking into account the table present in the note page
See next page

Valid AID / input parameters combinations
The Copy Remote File panel contains:

From: The combobox supports the following input parameters:
Secondary Backup Database (STDBYDB) The system's secondary backup database. It represents the secondary
backup database that has been either created as copy of the primary backup database (by the Perform DB
Backup option), or has been downloaded from RFS (by this option). A secondary backup database becomes
the active database only by being activated via the Restore Database option. There is one instance of
secondary backup database in the system.
Remote File Server Database (RFSDB) A database backup on a Remote File Server. It represents a database on
a Remote File Server. Multiple instances of RFSDB can exist in different locations on an RFS.
Remote File Server Software (RFSSW) A software generic on a remote file server. It represents a software
generic on a Remote File Server. Multiple instances of RFSSW can exist in different locations on an RFS.
Local NE PM Global File collection (LOCPMGLB)
To: The combobox supports the following input parameters:
Database Backup on a Remote File Server (RFSDB) A database backup on a Remote File Server.
Secondary Backup Database (STDBYDB) The system's secondary backup database.
Standby Software Generic (STBYSW) The standby software generic on the NE.
Remote File Server PM Global File Collection (RFSPMGLB)
Issue 01
1.Backup & restore
Remote file menu: Perform Copy (backup) [cont.]
Remember to add “/” for the

default directory of ftp server
3. Insert the location parameters
4. Do Apply

Location: The following fields indicates the source/destination of the files on an RFS (Remote File Server)
to be transferred. The syntax of the url is as follows: "ftp ://[<userid>[:<pass-
word>]@]<ftphost>[:<port>]/<url-path>" with:
Port: The entry box allows to digit the port number to connect to. Most schemes designate protocols
that have a default port number. The default port number for ftp is 21.
Command Mode: The combobox allows copying an RFS DB to the secondary backup database on the system.
Forced: The operation is performed, regardless of the following:
the BACKUP-DATE and BACKUP-TIME on the RFS DB (represented in the label on the RFS database) is
older/prior to the BACKUP-DATE and BACKUP-TIME on the system
the SID indicated on the RFS DB does not match the SID of the system.
the software release/identifier indicated for RFS DB does not match the software release identifier
indicated for the system.
Normal (default value): The command is denied if there is a mismatch between the SID, the release
identifier, system stream, system type or the backup time stamp of the system and the information
stored in the source database.
The Default hyperlink allows to set Normal automatically.
Overwrite: The combobox allows copying the secondary backup database to an RFS DB. Indicates whether
existing files should be overwritten.
Yes: Overwrite the existing files listed for the TO AID.
All Rights
No (default value): Do not overwrite theReserved © Alcatel-Lucent
existing @@YEAR
files listed for the TO AID.
Issue 01
1.Backup & restore
Remote file menu: Perform Copy (restore)
2. Choose:
• From = Database Backup on a
Remote File Server
• To = Secondary Backup database
Remember to add “/” for the

default directory of ftp server
3. Do Apply See next page


Issue 01
1.Backup & restore
Remote file menu: Perform Copy (restore) [cont.]


Issue 01
1.Backup & restore
Remote file menu: Cancel Copy
1. Select System Management -> DB Management -> Remote File -> Cancel Copy
2. Do Apply

This option interrupts an in-progress file transfer previously initiated by the Perform Copy File option. A
sub-sequent activation of this option will start a file transfer from the beginning.
In case a remote upload file transfer is autonomously or manually cancelled, partially transferred files
might exist on the RFS after an upload gets cancelled. The system does not take care of these remote
files. It is the responsibility of the RFS maintainer in this case to do the clean up, or to reuse the same
storage location for future backups by using the overwrite option.
When this option completes successfully, the message indicates that the file transfer initiated by the Copy
Remote File option was not completed successfully.

Issue 01
1.Backup & restore
Remote file menu: File Information
1. Select System Management -> DB Management -> Remote File -> File Information
2. Fill in all the parameters
3. Do Retrieve

The Remote File Information panel contains:

Access Identifier: the combobox supports the following input parameters:
Database Backup on a Remote File Server (RFSDB) (default value) A database backup on a Remote File
Server. It represents a database on a Remote File Server. Multiple instances of RFSDB can exist in
different locations on an RFS. A specific instance is always addressed with this AID, with the addition
of information in the LOCATION parameter in the command.
Secondary Backup Database (STDBYDB) The system's secondary backup database. It represents the
secondary backup database that has been either created as copy of the primary backup database (by
an ACT-DB_BACKUP command), or has been downloaded from RFS (by a COPY-RFILE commend). A
secondary backup database becomes the active database only by being activated via the RESTORE-DB
command.
Standby Software Generic (STBYSW) The standby software generic on the NE. It represents a software
generic that has been downloaded but not yet made active. The STBYSW becomes the system
software after it gets activated.
The Default hyperlink allows to set Database Backup on a Remote File Server (RFSDB) automatically.
Location: The following fields indicates the source/destination of the files on an RFS to be transferred.
The syntax of the url is as follows: "ftp ://[<userid>[:<password>]@]<ftphost>[:<port>]/<url-path>"
with:
Port: The entry box allows to digit the port number to connect to. The default port number for ftp is
21.
Issue 01
Blank Page


Issue 01
End of Module
Backup & Restore


Issue 01
42
Section 4
Maintenance
Module 2
Software Download
Issue 01
1850 TSS-320 & 1850 TSS-160

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

Issue 01
Blank Page

Maintenance Software Download
Document History

Issue 01
Module Objectives
Describe the NE software download


Issue 01


Issue 01
Table of Contents
Page
1 NE Software Download 7


Issue 01

Maintenance Software Download This page is left blank intentionally

Issue 01
1 NE Software Download

Maintenance Software Download Section 4 Module 2 Page 7

Issue 01
1 NE software download
Installation: Computer Hardware Configuration
The computer configuration to be used as a ZIC support consists of :

Main Hardware Configuration
CPU Pentium IV 1.7 GHz (2.8 GHz

suggested)
RAM 1 GB, (2GB suggested)
Monitor 15” (20” suggested)
Resolution 1024x768 pixel

Maintenance Software Download Section 4 - Module 2 - Page 8
Options:
Ethernet port: As an alternative to the CD-ROM drive for Software Download and upgrading (if any). In
alternative to the serial bootstrap, the Ethernet port can be used for LAN based bootstrap
Computer software configuration:
The following software items are required as alternative:
Internet Explorer 6.0 (or higher version)
Mozilla Firefox
Important:
- FTP Server program installed and running is mandatory for software download.
- In case of a firewall is running on PC, it is required to disable it.
- Disable the pop-up blocker, if enabled.
- If a secure http is used (https://…), it is required to have a temporary certification. The customer can get
it, following the browser indications.

Issue 01
Software download operative sequence
In order to execute the SW download you need to start up the FTP

server on your PC using Filezilla server or similar software tools.
Steps for Software download by using ZIC:
1) First operation you have to verify the NE is in the correct status (NOSTAIP)
“System Management Initialize and Upgrade In-Service Upgrade
Upgrade Status”. If you found a different status , please select “System
Management Initialize and Upgrade In-Service Upgrade Remove
Old Upgrade” menu .
2) Open the “System Management DB Management Remote File
Perform Copy” menu in order to specify which operation you want to
perform ( i.e sw download , DB backup , DB restore).
Set the following fields:
“From = Software Generic on a Remote File Server (RFSSW)”
“To = Standby Software Generic on the NE (STBYSW)”
Location fields depend on how you configured the ftp server tool on your PC


Issue 01
Software download operative sequence
3) Check the upgrade status “System Management Initialize and Upgrade

In-Service Upgrade Upgrade Status”. The status must be = “NOSTAIP”
. If you found a different status , please select “System Management
Initialize and Upgrade In-Service Upgrade Remove Old Upgrade”
menu . (identical to the step #1)
4) After the status upgrade check you select the “System Management
Initialize and Upgrade In-Service Upgrade Start Upgrade” menu.
Waiting for the “SUCCES“ event
5) Now , is possible to activate the new software release using the: “System
Management Initialize and Upgrade Initialize System With New
Release”. After that the NE will restart and will be activated the new
software release
6) You can check the sw release downloaded : “Equipment System
Information”


Issue 01
Step #1: check the status
First operation you have to verify the NE is in the correct status

(NOSTAIP).
To check the status, select: “System Management Initialize and
Upgrade In-Service Upgrade Upgrade Status”.
At the start of the procedure, check the status of the NE:

System Management Initialize and Upgrade In-Service Upgrade Upgrade Status.
If the status is not NOSTAIP, select: System Management Initialize and Upgrade In-
Service Upgrade Remove Old Upgrade and click on “Apply” to remove the old release
The panel shows the status of the in-service upgrade. The possible status are:
Download In Progress (DLIP), indicates that a COPY-RFILE command for software package transfer is
ongoing.
Initialize New Completed (INITNC), indicates the INIT-SYS-NEW system initialization process completed
successfully and the system is restarted on the new release.
Initialize New In Progress (INITNIP), indicates the INIT-SYS-NEW system initialization process is in
progress.
Initialize Old Completed (INITOC), indicates the INIT-SYS-OLD system initialization process completed
successfully and the system is restarted on the previous release.
Initialize Old In Progress (INITOIP), indicates the INIT-SYS-OLD system initialization process is in
progress.
No Status In Progress (NOSTAIP), indicates that no generic in-service upgrade procedure is in progress or
has been attempted.
Removal In Progress (RMVIP), indicates the removal of the previous release is in progress.
Status Completed (STAC), indicates that the STA-ISU command completed successfully and is awaiting
the issuance of the INIT-SYS-NEW command.
Status In Progress (STAIP), indicates that an in-service upgrade procedure is in progress.
Stop Completed (STPC), indicates that the STP-ISU command completed successfully.

Issue 01
Step #1: check the status [cont.]
If you found a different status , please select “System Management

Initialize and Upgrade In-Service Upgrade Remove Old
Upgrade” menu .
Click on “Apply” to remove the old release

This option makes the current release software the permanent active software. It effectively prevents
reversion to a previous release once it is determined by the operator that the capability is no longer
required.
After successful completion of this command, all software/database indicators are set to indicate that the
current release is now the permanently active one. The system remains in service on the currently active
release and all system functionality remains operational.

Issue 01
Step #2: perform the software copy
Open the “System Management DB Management Remote File

Perform Copy” menu in order to specify which operation you want to
perform
1. fill in the
location fields
2. Insert the path

where the .DSC
file is located
3. Click on “Apply” to start the copy 4. Click on “Yes”

This option makes the current release software the permanent active software. It effectively prevents
reversion to a previous release once it is determined by the operator that the capability is no longer
required.
After successful completion of this command, all software/database indicators are set to indicate that the
current release is now the permanently active one. The system remains in service on the currently active
release and all system functionality remains operational.

Issue 01
Step #2: perform the software copy
The result must be this one


Issue 01
Step #3: check the upgrade status
To check the upgrade status, select: “System Management

Initialize and Upgrade In-Service Upgrade Upgrade Status”.
The status must be = “NOSTAIP


Issue 01
Step #4: perform the start upgrade
This option start the in-service upgrade procedure

To start the In-service upgrade procedure, select: System Management
Initialize and Upgrade In-service upgrade Start Upgrade
Click on “Apply” to start the procedure
The result must be this one

The system performs a series of consistency checks on the actual configuration to make sure that the
system is in a state that can successfully be upgraded to the new release.
During command execution, the system remains in-service and continues to provide protection switching
and alarm reporting functionality on the current release. To assure that the consistency checks are done
on a consistent NE database, TL1 commands that would alter the NE configuration are rejected during the
ongoing consistency checks.
The performed consistency checks shall assure that the upgrade from the current (old) release to the
specified new release can be done successfully. The performed checks include:
verification that a new release software has been downloaded to the NE;
verification that the downloaded software matches the specified new release build identifier;
verification the the NE configuration of the current release is fully supported by the new release
(anticipating any known incompatibilities between old and new release).

Issue 01
Step #5: New Software release activation
To start the Initialize System with new release procedure, select:

System Management Initialize and Upgrade Initialize System
With new Release

This option starts the background activity on the NE to perform the actual switch over from the current
release to the new release.
This option returns a completion message to the user when the background activity has been successfully
started.
A copy of the primary database is made during its execution and used for database conversion in the
upgrade processing.
This backup is also used to revert to the old release database when the Initialize System With Old Release
option is issued after the system has been upgraded to the new release.
During the switch over process the system performs an FLC switch.
During the switch over process the system will perform an POWER-ON reset on the matrix modules and
download new FPGA images on IO cards and matrix cards if required.
If the activation of the new release fails, the system will revert to the old release and old database.

Issue 01
Step #6: check the new software
To check the new software, select: “Equipment System

Information”
At the end of the procedure, check the status of the NE:

System Management Initialize and Upgrade In-Service Upgrade Upgrade Status.
If the status is not NOSTAIP, select: System Management Initialize and Upgrade In-
Service Upgrade Remove Old Upgrade and click on “Apply” to remove the old release

This option starts the background activity on the NE to perform the actual switch over from the current
release to the new release.
This option returns a completion message to the user when the background activity has been successfully
started.
A copy of the primary database is made during its execution and used for database conversion in the
upgrade processing.
This backup is also used to revert to the old release database when the Initialize System With Old Release
option is issued after the system has been upgraded to the new release.
During the switch over process the system performs an FLC switch.
During the switch over process the system will perform an POWER-ON reset on the matrix modules and
download new FPGA images on IO cards and matrix cards if required.
If the activation of the new release fails, the system will revert to the old release and old database.

Issue 01
Initialize System With Old Release
To start the Initialize System with old release procedure, select:

System Management Initialize and Upgrade Initialize System
With old Release

This option starts the background activity on the NE to switch back from the current release and database
to previous release and database. The previous release and database are those which were active on the
NE before the last Initialize System With New Release option was successfully completed.
During the switch back process the system will perform an POWER-ON reset on the matrix modules and
download previous release software FPGA images on IO cards and matrix cards if required. This may cause
traffic interruption.

Issue 01
Stop Upgrade
This option halts/stops the in-service upgrade procedure

To stop the In-service upgrade procedure, select: System Management
Initialize and Upgrade In-service upgrade Stop Upgrade
Click on “Apply” to stop the procedure

This option halts/stops the in-service upgrade procedure and reverts the system to the state before the
Start Upgrade command was issued. The downloaded new release software is removed from the NE.

Issue 01
Blank Page


Issue 01
End of Module
Software Download


Issue 01
43
Section 4
Maintenance
Module 3
User Management
Issue 01
1850 TSS-320 & 1850 TSS-160

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

Issue 01
Blank Page

Maintenance User Management
Document History

Issue 01
Module Objectives
Describe how to change the user password

Describe how to create and delete user
Describe how to define and assign user privileges (permission)
Describe how to configure the security parameters


Issue 01


Issue 01
Table of Contents
Page
1 User management 7
2 Security 25


Issue 01

Maintenance User Management This page is left blank intentionally

Issue 01
1 User management

Maintenance User Management Section 4 Module 3 Page 7

Issue 01
1. User management
Introduction
The NE supports:
Up to 12 simultaneous TCP connections to either of the L1 ports 3082 and
3083
Up to 32 section DCC and up to 32 line DCC channels, but they can be
derived from up to 32 STM-n (1, 4, 16, 64).
As a gateway network element (GNE), the NE supports DCC
communications up to 240 nodes distributed over 16 separate DCC
channels on 16 rings or APS sub-networks. The 16 rings may be all OSI
over DCC, all IP over DCC, or mixed.
A GNE is able to mediate up to 240 simultaneous TL1 user sessions logged
into remote NEs. Normally, for large networks it is desirable to configure
an additional GE for every 30-40 managed nodes.
Up to 128 as max number of IP tunnels.

Maintenance User Management Section 4 - Module 3 - Page 8

Issue 01
1. User management


Issue 01
1. User management
Password management
To access the system, the user must enter a valid login ID and a
password. The password is a case-sensitive string with 8 to 12
alphanumeric characters with specific requirements.
The 1850TSS-320/160 allows up to 512 login IDs and passwords. The
number of simultaneous active sessions per user ID is limited to 1 per
management interface (ZIC and TL1). Ten concurrent user sessions are
supported.
To change the actual password select: Security User Account
Change password
1. Insert the old and
the new password
The home tab displays the Modify Password Identifier that contains the following parameters:
User Identifier: Specifies a unique user ID
Old Password: Specifies the old user's login password
New Password: Specifies the new user's login password
Confirm New Password ID: Specifies to confirm the newly entered password
The Save button send the command to the agent, then the main page of the manager is displayed

Issue 01
1. User management
Information functionality
This option can be used by the administrator to retrieve the parameters

in use for the security log
1. Select: Security User Account Information

The User Information page displays the following fields:

User Identifier specifies a unique user ID (e.g. admin).
User Access Privileges specifies the User access privilege(s) granted to the user.
User State: shows the new user's login password. The values are: Active and Suspended.
Password Duration [day]: specifies the number of days of validity for the password. The values that can
be displayed are in the 0 - 999 range, 0 (zero) means that Password aging is disabled.
Warning on Password Duration [day]: shows the number of days after the expiration date, which is
allowed for the user to change the password.
Access after Password Duration: shows the number of times that a user can log in after Password
expiration. The 0 (zero) means that the grace extra log-in after password expiration is disabled.
Password Obsolescence Interval [day]: shows the minimum time interval that is required if the User
wishes to use a password that was already used.
Password Expiration date and time: specifies the expiry date and time for the password.
User ID Duration [day]: shows the aging or expiry interval of a particular User Id.
Login Fails Number :specifies the number of unsuccessful authentication (login) attempts since the last
authenticated session.
Last Login Timestamp: shows the last recorded Login time of a user.
Keep Alive Message Interval [min]: shows the time interval, in minutes, after which the NE shall send a
KEEPÂLIVE^MESSAGE on a TCP connection inactivity.
Minimum Interval between Invalid Attempts [min]: shows the minimum interval, in seconds, between
invalid login attempts before an NE shall logout a user and lockout the user channel.
Max Invalid Attempts: shows the maximum number of invalid login attempts before an NE shall logout a
user and lockout the user channel.
Timeout [min]: shows User Session Activity Link TimeOut, specifies the amount of time that the User
Session link is inactive with regards to user TL1 input before a user session link time-out occurs.
Issue 01
1. User management
Accounts: create account
To create a new user, select: Security Administration Accounts

Create Account It’s suggested to create a dedicated user for
the 1350OMS management. For this user, it’s
necessary to assign “No inactivity timeout
(NOTMOUT)” privilege. In this way, the
inactivity timeout is not taken in account for
this user.
1. Fill in all the

parameters
A user with SEC privileges,

must have all this
parameters set to zero

The Create User Account page contains the following fields:

User Identifier: specifies a unique user ID. It is a sequence from 5 to 12 case-sensitive alphanumeric
characters, where the first character must always be an alphabetic character. The following special
characters shall also be valid; % (percent), + (plus sign), # (pound sign), and _ (underscore)
Password Identifier: specifies the user's login password. It is a sequence from 8 to 12 case-sensitive
alphanumeric characters. The Password must contain at least 1 upper alphabetic character, at least 1
lower alphabetic character and at least 1 numeric character. The following special characters shall be
valid: % (percent sign), + (plus sign), # (pound sign), and _ (under score). The first character of the
Password Identifier can be any alphabetic, numeric, or a valid special character. The Password
Identifier shall not have more than 3 consecutive identical characters, e.g. User_00001 shall be denied.
Password Duration [day]: specifies the number of days of validity for the password. The value range is 0
- 999, 0 (zero) means that Password aging is disabled. Default is 30.
Warning on Password Duration [day]: specifies the number of days after the expiration date, which is
allowed for the user to change the password. The value range is 0 - 999, 0 (zero) means that grace
period after password expiration is disabled. Default is 7.
Access after Password Duration: specifies the number of times that a user can log in after Password
expiration.
Password Obsolescence Interval [day]: specifies the minimum time interval that is required if the User
User ID Duration [day]: specifies the aging or expiry interval of a particular User Id. The value range is 0
- 999, 0 (zero) means that User ID aging is disabled. Default is 60.
The page contains also two entry boxes:
Available User Access Privileges: lists all the privileges for the User access.
User Access Privileges: shows the privileges for the User access.
The NE supports a maximum of 512 unique userIDs.

Issue 01
1. User management
Accounts: change or delete an account
To change or delete an account, select: Security Administration

Accounts Change Account
The User Information page displays a
table with all information about all
Users. This window allows to
execute other functionality: i.e.
change the pwd, inhibit a user, etc
This function is used to create a new account
Click on Modify account to modify the account parameters
Click on “Save” to
This function is used to delete an account

The change account page contains the same fields of the “create account” page

Issue 01
1. User management
Accounts: change account [cont.]
To modify a User Account,

1. Click on “Modify Account” 2. Insert the user name,
password and ID
parameters
3. Configure the User

Access Privileges

A Password Identifier shall be a case sensitive string of 8 to 12 alphanumeric characters with at least three
of the following: at least one upper alphabetic character, at least one lower alphabetic character, at
least one numeric character, at least one special character. The following special characters shall be
valid: % (percent sign), + (plus sign), # (pound sign), and _ (under score). The first character of the
Password Identifier can be any alphabetic, numeric, or a valid special character.

Issue 01
1. User management
Accounts: Default Settings
To modify the default settings, select: Security Administration

Account Default Settings
Click on “Save” to accept the new configuration

The Modify Account Default Settings page displays a table with all information about Users:
Password Duration [day]: specifies the number of days of validity for the password. The value range is 0
- 999, 0 (zero) means that Password aging is disabled. Default is 30.
Warning on Password Duration [day]: specifies the number of days after the expiration date, which is
allowed for the user to change the password.
Access after Password Duration: specifies the number of times that a user can log in after Password
expiration.
Password Obsolescence Interval [day]: specifies the minimum time interval that is required if the User
Keep Alive Message Interval [min]: specifies the time interval, in minutes, after which the NE shall send
a KEEPÂLIVE^MESSAGE on a TCP connection inactivity.
Minimum Interval after Invalid Access [min]: specifies the minimum interval, in seconds, between
invalid login attempts before an NE shall logout a user and lockout the user channel.
Max Invalid Attempts: specifies the maximum number of invalid login attempts before an NE shall
logout a user and lockout the user channel.
Timeout [min]: specifies User Session Activity Link TimeOut, specifies the amount of time (in minutes)
that the User Session link is inactive with regards to user TL1 input before a user session link time-out
occurs.
User ID Duration [day]: specifies the aging or expiry interval of a particular User Id.
Max Number of Session: specifies the maximum number of simultaneous sessions allowed on the NE for
any user.
Security Access: specifies the Security access mode
Security Port mode: specifies which are the accepted IP address, inserted in the segregation list
ICMP Protocol: this parameter indicates whether or not ICMP protocol is enabled.
DHCP Protocol: this parameter enables/disables the DHCP protocol on the CT port.
All Rights Reserved ©all
Physical Ports: this parameter enables/disables Alcatel-Lucent
the physical@@YEAR
ports on the NE, except Q and F. This
Issue 01
means that Q and F ports shall be always enabled. Note that F ports is always referenced to as CT port.
1. User management
Current Session
To display the current session, select: Security Administration

Account Current Session
The page displays a table with information about current session.
Click on “Log Off User” to close the session

The columns of the table are :

Action contains the Log Off User hyperlink which allows to close the session.
User Identifier specifies a unique user ID (e.g. admin).
Session specifies by a unique identifier allocated to a client connection that distinguishes that
connection from other connections in the system.
Address specifies the address where the user is connecting from. It is the port/IP address that is being
used for access. If a non IP port is used to connect to the NE, the values DCC, LAN, USB, RS232 are
used.
Last login timestamp specifies by a quoted string the last recorded Login time of a user. This time is
displayed every time a user logs in.

Issue 01
1. User management
Command privileges attributes
The “Command” option show the list of Command whit state (In
Service, Out of Service) and profile. The NE shall support the ability for
a user with sufficient Security Level privileges to change the Command
Security Level assigned to a specified external command.
User privilege attributes

When a user is added to the NE, user privilege attributes, which include
an authorization level and command access privileges, are assigned to
that user for one or more of the functional categories, based on the
type of work the user is doing.
The functional categories are:
READ (Read only)
DEBUG (to initiate non service-affecting test procedures)
PROV (Provisioning): he user may perform non-destructive provisioning of IO
cards, ports and interfaces, initiate test procedures which are not service
affecting and retrieve information about the system


Issue 01
1. User management
Command privileges attributes [cont.]
CONF (Configure): a user may configure the system, including non-

destructive provisioning and testing of all IO cards, ports, interfaces and
circuits. The user may configure all subsystems which do not allow for system
wide affect and the user may initiate test procedures which are not service
affecting and he may retrieve information about the system.
NETADMIN (Network administrator) A network administrator may configure
anything in the system except user accounts.
SEC (Security administrator) A user with the security privilege flag may
create, delete, and modify user accounts. A security user does not need to be
a network administrator (but can create user accounts with network
administrator privilege). The user is able to issue all commands, but is not
able to use debugging and software development tools.
Only the default user ALCATEL has, beside all the security administrator
privileges, the capability of using debug and software development tools, for
debug and maintenance purposes.
NOTMOUT (No inactivity timeout) No inactivity timeout is applied to the
user.


Issue 01
1. User management
To open the DB command access privileges: Security Administration

Commands privileges
1. Select a command


Issue 01
1. User management
2. Choose the permission


Issue 01
1. User management
Network Element Logs
To open the NE Logs: Security Administration Network Element

Logs
2. Click on Search to
see the log file

The Retrieve Audit Log page contains the Retrieve Audit Log panel with the following parameters:
From: Specifies the beginning date and time used to filter the response messages. By means the combo-
boxes it is possible to change data and time
To: Specifies the beginning date and time used to filter the response messages. By means the combo-
boxes it is possible to change data and time
UID: The combo-box allows to select the user identifier:
ALL
admin

Issue 01
1. User management
Network Element Logs [cont.]
2. Click on Ok to
confirm the choice
1. Click on Download to local to
save (or to see) the file in the pc


Issue 01
1. User management
Log settings
This function Displays the Log Attributes panel to modify the Log
attributes. To open the Log settings: Security Administration Log
Settings
1. Choose the new

attributes
Modify Log Attributes panel contains:

Current Log File Max Size [Mbyte]: Specifies the size, in 1 Megabyte blocks, of the Security Log File
system's disk buffer.
New Log File Max Size [Mbyte]: Allows to change the size, in 1 Megabyte blocks, of the Security Log File
system's disk buffer. When the SECULOG has reached its max size, the SECULOG wraps reducing its size
to the 70% of its max size discarding the oldest events (30%). The Default hyperlink allows to set the
relevant value automatically
Current Warning Message: This is the provisioned user-logon warning message is shown
Warning Message: Allows to provision user-logon warning message. The Default hyperlink allows to set
the relevant warning message automatically
New Warning Message: Allows to provision a new user-logon warning message. The Default hyperlink
allows to set the relevant warning message automatically. The Set Empty hyperlink allows to deplete
the entry field.
Current Log Events: Specifies the current log event
Available Log Events: Specifies the list of events that, upon their occurrence, are included in the
security log (i.e., events that are specified for logging, if they occur).
New Log Events: This shows the log events for the command. The entry box has the Default hyperlink
in order to set the User access privileges forecast for the account.

Issue 01
Blank Page


Issue 01
2 Security

Maintenance User Management Section 4 Module 3 Page 25

Issue 01
2 Security
Security parameters: Security Access
When the NE is in SECURE mode, only ports 6084 and 6085 (TL1), 6086
(CLI) and 443 (HTTPS) are opened, the NE shall support SNMPv3 only
and shall use SFTP to transfer files to/from the NE. When the NE is in
unsecure mode only ports 3082 and 3083 (TL1), 1123 (CLI), 22 (debug
port for ROOT access always with SSH), 23 (port for telnet) and 80
(http) shall be opened, and both SNMPv2 and v3 shall be supported on
port 161.
1. Select: Security Administration
Accounts Default Settings
2. Choose the
configuration
Every time you change the Security

Access, the NE forces logout


Issue 01
2 Security
Security parameters: Security Access set to Secure
1. Set Security Access = SECURE
2. Click on Save 3. Click on Ok


Issue 01
2 Security
Security parameters: Security Access set to Secure [cont.]
4. Insert the IP address of NE with

https at the beginning
5. Click on I Understand the Risk


Issue 01
2 Security
7. Click on Confirm Security Exception
6. Click on Add Exception


Issue 01
2 Security
8. insert User ID and Password
9. Click on Login

Issue 01
2 Security
Security parameters: Port Segregation
The aim of the feature “Port Segregation” is to avoid RNE to RNE

communication. The scenario on next figure shows a typical example,
with RNEs (TSS3) of different customers. NM shall be able to
communicate with all TSS3, but TSS3 nodes shall not communicate
between them.


Issue 01
2 Security
Security parameters: Port Segregation [cont.]
The NE supports a configurable list of IP addresses, called “port-

segregation” list, containing the IP addresses of the machines that are
connected to the network and are allowed to communicate with any
other machine’s IP of the network. In practice the IP addresses
configured in the port-segregation list should be the addresses of NMS,
which shall be able to communicate with any NE and RNE of the
network.
Every NE shall discard the IP packets with either Source Address (SA) or
Destination Address (DA) NOT matching with any of the IP addresses in
the port-segregation list.
The Port Segregation feature can be enabled (Security port mode set to
ENABLE in the Account Default Settings menu) only if the Port
Segregation list is not empty. This is because an empty list will make
the NE unreachable when the feature is enabled.


Issue 01
2 Security
Security parameters: Port Segregation [cont.]

Port segregation List
2. Insert the IP address and the network

mask (If the IP address is a host, this
field can be left empty)
At the end of the procedure, the new

IP address appears in the list
3. Click on Add


Issue 01
2 Security
Security parameters: ICMP
The commands also allows to enable/disable ICMP protocol. This

protocol is used for ping operation, which provides an important
security weakness for exposure to DOS attacks, so that the purpose of
ICMP disabling is removing this risk. But ICMP is also used to provide
tunneling features, e.g. OSI over IP. For this reason ICMP is enabled by
default and, when enabled, the max number of allowed ping messages
per session shall be 10 per minute. This will mitigate the possibility of
DOS attacks. 1. Select: Security Administration
2. Choose the
configuration


Issue 01
2 Security
Security parameters: DHCP
This parameter enables/disables the DHCP protocol on the CT port.

2. Choose the
configuration


Issue 01
2 Security
Security parameters: Physical port
This parameter enables/disables all the physical ports on the NE,

except Q and F. This means that Q and F ports shall be always enabled.
Note that F ports is always referenced to as CT port. Ports to be closed
include also the LAN for DEBUG, the LAN used for drop shelves and the
serial debug ports.
2. Choose the
configuration


Issue 01
2 Security
Security parameters: SNMP V3 configuration
1. Select: Security Administration Accounts

Create Account (or Change Account)
2. Click on Create Account or Modify Account


Issue 01
2 Security
Security parameters: SNMP V3 configuration [cont.]
3. Configure the
SNMPv3 parameters

SNMPv3 Privacy Protocol: this parameter allows the configuration of the SNMPv3 privacy protocol and its
disabling.. NOPRIV means that privacy is disabled for this user.
SNMPv3 Authorization Protocol: this parameter allows the configuration of the SNMPv3 authorization
protocol and its disabling.. NOAUTH means that authorization is disabled for this user.

Issue 01
2 Security
Security parameters: SNMP V3 combinations
The NE supports the following SNMPv2c and SNMPv3 combinations:

SNMPv2c: no Authority and no encryption
SNMPv3: (NOPRIV, NOAUTH): like SNMPv2c
SNMPv3: (NOPRIV, HMACMD5): authentication encrypted, messages no
encrypted
SNMPv3: (AES, HMACMD5): authentication encrypted, messages encrypted
SNMPv3: (CBCDES, HMACMD5): authentication encrypted, messages encrypted

SNMP provides for both security versions and security levels. A security version is an authentication strategy
that is set up for a user and the group in which the user resides. A security level is the permitted level of
security within a security version. A combination of a security version and a security level will determine
which security mechanism is employed when handling an SNMP packet. Two security versions are
available: SNMPv2c an SNMPv3.
SNMPv3 supports HMACMD5 (Hash-based Message Authentication Code Message Digest Algorithm number 5)
only for authentication protocol, and CDCDES and CFBAES (for AES128) encryption for privacy protocol.
The authentication protocol and privacy protocol must be specified in SNMPv3 packets or the packet will
be ignored.
When the NE is in SECURE mode, only SNMPv3 shall be supported and only SNMP users with privacy and
authorization enabled shall be supported.
When the NE is in unsecure mode, both SNMPv2 and SNMPv3 shall be supported.

Issue 01
2 Security
Radius server
RADIUS (Remote Authentication Dial In User Service) is a networking

protocol, based on RADIUS servers, that provides centralized
Authentication, Authorization and Accounting (AAA) services. The user
sends a connection request to a Network Access Server (NAS), which
acts as RADIUS client and sends a RADIUS access request to the RADIUS
server. The RADIUS server is provisioned with one or more user
profiles. Based on the user profile and user class definitions, the
RADIUS server accepts or rejects the NAS request. In turn the NAS
accepts or, respectively, rejects the user connection. The following
picture shows the general RADIUS scenario.


Issue 01
2 Security
Radius server [cont.]
In our implementation the NAS role is covered by the NE. The following
Figure shows the messages exchange between the user, the NE and the
RADIUS server, for the three possible cases of authentication and
authorization.


Issue 01
2 Security
Radius server [cont.]
When the RADIUS server receives an access request, it searches a

database of users to find the user whose name matches the request. If
the username is found and the password is correct, the RADIUS server
returns a RADIUS packet, Access-Accept, otherwise an Access-Reject.
The access request contains the user ID, the user password and the NSA
address. The user password shall be encrypted by a shared key
(between the NE and the RADIUS server). This shared key is called
"shared secret".


Issue 01
2 Security
Radius Configuration
This menu is used to configure the RADIUS server parameters:

To open the Configure Authority menu: Security Administration
Management RADIUS Configure RADIUS
2. Configure the RADIUS

parameters and the
Secret Key
1. Click on Create
The parameters involved in the RADIUS server configuration are:

Server Number: This identifies RADIUS server. The acceptable values are RAD1 (First server as "1") and
RAD2 (second server as "2").
Status: indicates the RADIUS server status. The Enabled value can be entered if at least one RADIUS
server is provisioned in the system.
IP Address: This is the IP address of the specified RADIUS server. .The supported value format is {1-99,
101-126, 128-223} - {0-255} - {0-255} - {1-254}.
Port: This is the authentication port of the RADIUS server. The valid value is from 1 to 65000. The
default port value is 1812.
Secret Key: It indicates the shared secret key between the NE and the target RADIUS server. The key is
an ascii string between the value range of 5 to 32. The secret key must be encrypted on the NE using
AES or 3DES protocol.

Issue 01
2 Security
Radius Configuration [cont.]
This menu is used to configure the following RADIUS attributes:

Authority Order
Retries
Timeout
To open the Configure Authority menu: Security Administration
Management RADIUS Configure Authority
1. Choose the Authority

order and the retries
number
The parameters involved in the RADIUS Authority are:

Authority Order:
LOCAL: Authentication is based on the local NE's security database.
RADIUS: Authentication first attempt is however based on the local NE's security database: if the user
ID in not found there, then the authentication is based on the RADIUS server's database. NOTE: this
way the NE can always guarantee NMS access, which is based on a local NE user ID.
Timeout: this is the timeout (in seconds) for the NE to wait for a response from the RADIUS server. The
failure is declared after the timeout is elapsed. The supported value range for timeout is 1 to 1000. The
default value is 5.
Retries: this is the number of attempts that the NE will try to contact the specified RADIUS server that
has failed to respond during the previous requests. If there is no response from the server after the
specified tries then the NE will try to contact the second RADIUS server if one is provisioned (status:
"Enabled"). The retries range is 0 to 100 with default value 3.

Issue 01
Blank Page


Issue 01
End of Module
User Management


Issue 01
44
Section 4
Maintenance
Module 4
EC substitution
Issue 01
1850 TSS-320 & 1850 TSS-160

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

Issue 01
Blank Page

Maintenance EC substitution
Document History

Issue 01
Objectives

Substitute the EC320 board


Issue 01
Blank Page

Maintenance EC substitution This page is left blank intentionally

Issue 01
Table of Contents
Page
1 EC substitution 7


Issue 01
Blank Page

Maintenance EC substitution This page is left blank intentionally

Issue 01
1 EC substitution


Issue 01
1 EC substitution
Dip switch
ON
OFF
Switch#1 Switch#2
Side view of EC320
The insertion of EC320 spare is easy: it is enough insert the board without modify the
switch position and without delete the equipment software, also is different release.
If the board is without sw, it is necessary execute the HDD format and USB key download


Issue 01
1 EC substitution
Procedure (necessary if present one EC320 only)
Set the new unit with: switch#1=OFF, switch#2=ON (reset database)
Insert the new unit
What’s the The needed A wrong
SW of the release release No SW
new unit?
Download the NE Download the NE

relevant SW release with relevant SW release with
Download procedure Loading procedure
Remove and set the new unit with:

switch#1=ON, switch#2=OFF (reset database and upload comm/routing tables)
Insert the new unit again
NO Is the MIB stored in the PC? YES
From OS send the saved MIB From ZIC send the saved MIB
containing the correct configuration containing the correct configuration
By OS activate the sent MIB By ZIC activate the sent MIB

Remove and set the new unit with: switch#1=OFF, switch#2=OFF (normal operating condition)
Insert the new unit again

Issue 01
1 EC substitution
How to read the SW release of the new EC320/160
To check the software releases present in the EC320/160, select:

Equipment System Information


Issue 01
Blank Page


Issue 01
End of Module
EC substitution


Issue 01
DRAFT
@@SECTIONTITLE - @@MODULETITLE @@SECTION - @@MODULE - 1
@@PRODUCT
All Rights Reserved © Alcatel-Lucent 2007
@@COURSENAME This page is left blank intentionally
Copyright © 2007 by Alcatel-Lucent - All rights reserved
Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel

1850 TSS 320 1850 TSS 160 R 4 1 Ce

Uploaded by

Document Information

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

1850 TSS 320 1850 TSS 160 R 4 1 Ce

Uploaded by

Copyright:

Available Formats

1850 TSS-320 & 1850 TSS-160

1850 TSS-320 & 1850 TSS-160 R

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

Switch to notes view!

4 All Rights Reserved © Alcatel-Lucent @@YEAR

All Rights Reserved © Alcatel-Lucent @@YEAR

1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

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 1850 TSS-320 & 1850 TSS-160 R 4.1 O&M

Upon completion of this course, you should be able to:

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 ?

4 Describe the SDH boards of the 1850TSS-320 /160

5 Describe the DWDM and CWDM boards of the 1850TSS-320/160

6 Describe the Data boards of the 1850TSS-320 and 1850TSS-160

7 Describe how to configure the NE with CT port

All Rights Reserved © Alcatel-Lucent @@YEAR

Yes (or No (or

14 Explain to create a backup of the NE database

15 Describe the NE software download

16 Describe how to change the user password

17 Substitute the EC320 board

Thank you for your answers to this questionnaire

All Rights Reserved © Alcatel-Lucent @@YEAR

1850 TSS-320 & 1850 TSS-160

All Rights Reserved © Alcatel-Lucent @@YEAR

All Rights Reserved © Alcatel-Lucent @@YEAR

112 All Rights Reserved © Alcatel-Lucent @@YEAR

This page is left blank intentionally

Edition Date Author Remarks

01 2011-12-15 Grecchi Ilario

All Rights Reserved © Alcatel-Lucent @@YEAR

Describe the basic concept of 1850TSS family

113 All Rights Reserved © Alcatel-Lucent @@YEAR

All Rights Reserved © Alcatel-Lucent @@YEAR

114 All Rights Reserved © Alcatel-Lucent @@YEAR

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent @@YEAR

Switch to notes view! Page

115 All Rights Reserved © Alcatel-Lucent @@YEAR

All Rights Reserved © Alcatel-Lucent @@YEAR

116 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

115 All Rights Reserved © Alcatel-Lucent @@YEAR

116 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 14 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 17 All Rights Reserved © Alcatel-Lucent @@YEAR

1 1 18 All Rights Reserved © Alcatel-Lucent @@YEAR

122 All Rights Reserved © Alcatel-Lucent @@YEAR

123 All Rights Reserved © Alcatel-Lucent @@YEAR

124 All Rights Reserved © Alcatel-Lucent @@YEAR

125 All Rights Reserved © Alcatel-Lucent @@YEAR

126 All Rights Reserved © Alcatel-Lucent @@YEAR

127 All Rights Reserved © Alcatel-Lucent @@YEAR

128 All Rights Reserved © Alcatel-Lucent @@YEAR

129 All Rights Reserved © Alcatel-Lucent @@YEAR

1 2 10 All Rights Reserved © Alcatel-Lucent @@YEAR

1 2 11 All Rights Reserved © Alcatel-Lucent @@YEAR

1 2 12 All Rights Reserved © Alcatel-Lucent @@YEAR

1 2 13 All Rights Reserved © Alcatel-Lucent @@YEAR

1 2 14 All Rights Reserved © Alcatel-Lucent @@YEAR