1350OMS-PKT R 9 - 1 - 1 Operation

1350OMS-PKT R 9.1.
1 Operation - Page 1
All Rights Reserved Alcatel-Lucent 2010
1350OMS
1350OMS-PKT R 9.1.1 Operation
STUDENT GUIDE
TOS63013-R.9.1.1-SG1-SEN-I1.0 Issue 1.00
All rights reserved Alcatel-Lucent 2010
Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent
1350OMS-PKT R 9.1.1 Operation - Page 2
1350OMS
2
Empty page
Switch to notes view!
This page is left blank intentionally
1350OMS
3
Terms of Use and Legal Notices
1. Safety Warning
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-Lucents 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
written consent of Alcatel-Lucent.
All rights reserved Alcatel-Lucent 2010
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.
1350OMS
4
Blank Page
1350OMS
5
Course Outline
About This Course
Course outline
Technical support
Course objectives
1. Topic/Section is Positioned Here
Xxx
Xxx
Xxx
Section 1. Product Overview
Module 1. Product Overview
Section 2. Graphical Interfaces
Module 1. How to Logon
Module 2. Network Topology
Section 3. System Operation
Module 1. Transport link Provisioning
Module 2. Traffic descriptor Provisioning
Module 3. Ethernet Service Provisioning
Module 4. Bridge Provisioning
Module 5. T-MPLS Provisioning
Module 6. End to end provisioning
Module 7. Network utilities
Section 4. Maintenance Applications
Module 1. Alarm Management
Module 2. Performance monitoring
1350OMS
6
Course Outline [cont.]
1350OMS
7
Course Objectives
Welcome to 1350OMS-PKT R 9.1.1 Operation
Upon completion of this course, you should be able to:
Operate with the 1350OMS PKT system
1350OMS
8
Course Objectives [cont.]
1350OMS
9
About this Student Guide
Conventions used in this guide
Where you can get further information
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
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.
1350OMS
10
About this Student Guide [cont.]
1350OMS
11
Self-assessment of Objectives
At the end of each section you will be asked to fill this questionnaire
Please, return this sheet to the trainer at the end of the training
Instructional objectives
Yes (or
globally
yes)
No (or
globally
no)
Comments
1350OMS-PKT Overview
Describe the 1350OMS PKT functions and the
system architecture

How to Logon
Get started on 1350OMS PKT functions

Network Topology
Create and modify a network topology made
of Service Nodes, NEs and ENEs

Transport Link Provisioning
Create and modify a Link over TDM, a Link
over Cable; define the transport link
characteristics

Traffic Descriptor Provisioning
Manage a Traffic Classifier, a VLAN Type, a
Color Profile
Manage the Traffic Descriptors for Ethernet
segment

Ethernet Service Provisioning
Manage the End to End Ethernet Services
provisioning

Bridge Provisioning
Manage the Bridge network provisioning

T-MPLS Provisioning
Manage a T-MPLS service provisioning

END TO END Provisioning
Create an END TO END Service

Network utilities
Detect, by means of Audit, the misalignment
between the NE and 1350OMS PKT dB
Fix the misalignment by executing a download
into the NE

Contract number :
Course title :
Client (Company, Center) :
Language : 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

1350OMS
12
Self-assessment of Objectives [cont.]
Instructional objectives
Yes (or
Globally
yes)
No (or
globally
no)
Comments
Alarm management
Manage the elementary alarms affecting
1350OMS PKT managed resources

Performance Monitoring
activate and deactivate Performance
Monitoring
display the results
export PM information
compare the NMLs PM DB with the EMLs PM
dB

Thank you for your answers to this questionnaire
Other comments

Section 1 Module 1 Page 1
3JK Issue 1.00
Do not delete this graphic elements in here:
11
Module 1
Product Overview
3JK Issue 1.00
Section 1
Product Overview
1350OMS
3JK Issue 1.00
1350OMS 1350OMS-PKT R 9.1.1 Operation
Product Overview Product Overview
1 1 2
Blank Page
First edition Buono Giovanni 2010-02-26 01
Remarks Author Date Edition
Document History
3JK Issue 1.00
1 1 3
Module Objectives
Upon completion of this module, you should be able to:
Describe the 1350OMS PKT functions and the system architecture
3JK Issue 1.00
1 1 4
Module Objectives [cont.]
3JK Issue 1.00
1 1 5
Table of Contents
Page
1 1350OMS product and its applications 7
2 1350OMS-PKT Ethernet functions overview 11
3JK Issue 1.00
1 1 6
Table of Contents [cont.]
3JK Issue 1.00
1 1 7
1 1350OMS product and its applications
3JK Issue 1.00
1 1 8
Alcatel-Lucent
Network
(ETSI, Ethernet, WDM and SONET
Alcatel-Lucent
Network
Common GUI
& maps
Common
desktop, login
and security
Common HW
platform
HP Server and
Linux PC
Open Interfaces
ASCII, TMF MTNM MTOSI
NETWORK MANAGEMENT
ELEMENT MANAGEMENT
SERVICE MANAGEMENT
WDM
SDH SONET
PACKET
Common Fault
Management
Common PM
All technologies
TMN description
1350OMS 9.1 integrates the current products into a single operational framework, keeping network
features on a subnetwork basis, whilst setting a first set of common platform-wide functions.
The 1350OMS is decomposed into a set of "applications", each of which is license controlled and
separately purchasable. The applications are:
- 1350OMS-EML
- 1350OMS-SDH
- 1350OMS-PKT
- 1350OMS-SONET
- 1350OMS-WDM
This architecture then decomposes the applications into "subsystems".
3JK Issue 1.00
1 1 9
1350OMS
-eOMS
1350OMS-EML
1350OMS
-WDM
Element Mng
SDH/PDH
Services
1350OMS
-PKT
1350OMS
-SDH
1350OMS
-SONET
WDM
Ntw.Mng
TDM
Ntw.Mng
PKT
ETH, TMPLS
Ntw.Mng
ETH
Services
SONET/PDH
Services
WDM
Services
Sub-network
management
Client/Server
Relationship
1350OMS
-High Availability
1350OMS
-Open Interfaces
Standard & Classic
Alcatel-Lucent
Network
Alcatel-Lucent
Network
Subsystems description
Subsystems description:
1350OMS-EML provides the element layer management capabilities for both Alcatel-Lucent ANSI and
ETSI NEs.
1350OMS-SDH provides the SDH and WDM network management layer along with provisioning, alarm
correlation, and PM correlation capabilities. The 1350 OMS SDH functions as a client for the 1350 OMS
WDM application and as a server for the 1350 OMS PKT application.
1350OMS-PKT application provides Ethernet network management layer support, along with
provisioning, alarm correlation, and historical PM data services.
The 1350 OMS WDM application provides Wavelength Division Multiplexing (WDM) and Dense
Wavelength Division Multiplexing (DWDM) support, along with provisioning, alarm correlation, and
historical PM correlation capabilities.
The 1350 OMS SONET application provides direct Synchronous Optical Network support, along with
provisioning, alarm correlation, and historical PM data capabilities. The 1350 OMS SONET functions as a
client for the 1350 OMS WDM application and as a server for the 1350 OMS PKT application.
1350OMS-eOMS provides:
the element layer and the SDH, SONET, WDM, Ethernet network layer for former Lucent NEs
the SONET and WDM network layer for ANSI TSS NEs
3JK Issue 1.00
1 1 10
Blank Page
3JK Issue 1.00
1 1 11
2 1350OMS-PKT Ethernet functions
overview
3JK Issue 1.00
1 1 12
2 1350OMS-PKT Ethernet functions overview
1350OMS PKT functions
1350 OMS PKT manages Ethernet Networks functionalities in term of
service, provisioning, maintenance, and performance monitoring:
Network discovery and synchronization.
Connectivity routing and provisioning.
Fault management and performance monitoring.
Network audit, alignment, and recovery.
PKT application support the Ethernet technologies:
Packet Ring,
Connection-oriented,
Bridging,
Transport-Multi-Protocol Label Switching (T-MPLS).
The whole network is viewed as a set of sub-Networks each one based on one specific technology with
several specificities. The PKT offers the ability to manage the whole Network in order to implement
End to End Ethernet Services. SLA and QoS characteristics associated to these Services are applied on
each crossed sub Networks according to configurable profiles.
3JK Issue 1.00
1 1 13
Telecommunication Network overview
Metro Core
T-MPLS
Metro
Edge GFP
over SDH
Metro
Edge GFP
over WDM
The picture summarizes the Network architecture supporting Ethernet Service.
3JK Issue 1.00
1 1 14
Telecommunication Network overview [cont.]
Ethernet
Data
GFP
Ethernet
Data
SDH
Ethernet
Data
P2P T-MPLS
OMSN including
ISA unit
supporting GFP
NE supporting
T-MPLS
Ethernet
Data
T-MPLS
T-MPLS
Ethernet
Ethernet
Data
T-MPLS
T-MPLS
Ethernet
Ethernet
Data
T-MPLS
T-MPLS
SDH
An Ethernet End to End service can use all the defined transport server layers: transparent SDH, then
cross an T-MPLS network, to reach the final destination port.
Here above is depicted a traffic flow received through a physical Ethernet port and getting through
different transport layers, including a sub-network implementing a T-MPLS infrastructure; it is getting
out through an aggregate port with the identification of the initial traffic flow provided through a T-
MPLS label added by the edge NE.
3JK Issue 1.00
1 1 15
Network construction and Ethernet service provisioning
The Alcatel 1350OMS PKT provides Ethernet connectivity
services; the main management areas are:
Network construction (Constructor)
Sub-network management
NE and ENE management
Transport Links management
T-MPLS management (T-Mpls)
Transport link management
Tunnel management
PseudoWire management
QoS management
Traffic management (Services)
Customer / Ethernet service management
EVC / Ethernet segment management
VLAN management
Policy control
SDH / WDM network
GFP & T-MPLS
Ethernet service
1350OMS
PKT
3JK Issue 1.00
1 1 16
Network maintenance and PKT administration
Network Maintenance & Utility
Alarm records management
Fault localization
Audit and alignment
PKT administration
Operators management
Process monitoring
Application backup / restore
Fast Ethernet
3JK Issue 1.00
1 1 17
End of Module
Product Overview
3JK Issue 1.00
21
Module 1
How to Logon
3JK Issue 1.00
Section 2
Graphical Interfaces
1350OMS
3JK Issue 1.00
Graphical Interfaces How to Logon
2 1 2
Blank Page
Document History
3JK Issue 1.00
2 1 3
Module Objectives
get started on 1350OMS PKT functions
3JK Issue 1.00
2 1 4
3JK Issue 1.00
2 1 5
Table of Contents
Page
1 Access to PKT application 7
3JK Issue 1.00
2 1 6
3JK Issue 1.00
2 1 7
1 Access to PKT application
3JK Issue 1.00
2 1 8
1 Access to PKT applications
MS-GUI main menu
Functions are grouped under the main
menu and, for the more complex ones, the
menu items give access to specific
submenus, organized in hierarchical tree.
The user accesses the system functions both from the main menu and from the
pop-up menu available from the list, for single or multiple selected items.
3JK Issue 1.00
2 1 9
Search menu
By the Search menu the user can retrieve lists of PKT DB network objects.
N.B: MPLS and OAM CC applications are not supported in current release
3JK Issue 1.00
2 1 10
Enable/Disable filter
The operator can enable or disable the filter for the Search operation, in case
of enabled, the object list is displayed according to the filter condition.
1. Click on the icon
to Enable/Disable
the filter
2. Set the Filter
conditions
3. Click on OK
3JK Issue 1.00
2 1 11
Actions menu
By the Actions menu the user can perform tasks on PKT DB network objects
(create, delete, synchronize, .), get and modify object properties, etc.
N.B: MPLS and OAM CC applications are not supported in current release
3JK Issue 1.00
2 1 12
End of Module
How to Logon
3JK Issue 1.00
22
Module 2
Network Topology
3JK Issue 1.00
Section 2
Graphical Interfaces
1350OMS
3JK Issue 1.00
Graphical Interfaces Network Topology
2 2 2
Blank Page
Document History
3JK Issue 1.00
2 2 3
Module Objectives
Create and modify a network topology made of Service Nodes, NEs and ENEs
3JK Issue 1.00
2 2 4
3JK Issue 1.00
2 2 5
Table of Contents
Page
1 Network Elements and Nodes management 7
2 External Network Element management 35
3 Link Aggregation (LAG) management 45
3JK Issue 1.00
2 2 6
3JK Issue 1.00
2 2 7
1 Network Elements and Nodes
management
3JK Issue 1.00
2 2 8
1 Network Elements and Nodes management
Definitions
Domain: a distributed infrastructure, managing object like NE,
Transport Link, etc.), in order to supply a Connection-oriented, Bridge,
Circuit Emulation or a T-MPLS infrastructure.
Domain are managed by Construction environment and used by Service
environment according to the Domain type (ETS, Bridge, CES, T-MPLS)
Each Domain is a Routing Domain in sense that will contain only object
fully connectable one each other
N.B. specific default domains are already configured for connection-oriented,
Bridge and for T-MPLS infrastructure
Network Element definition
NEs are characterized, in the scope of the Construction domain, by a set of
resources which are:
Ethernet physical ports (local ports)
TDM terminations (remote ports)
External Network Element definition :
ENE management allows to define inside 1350OMS PKT NEs, or networks, or
Customer Edge not directly administrated by the PKT
3JK Issue 1.00
2 2 9
Definitions [cont.]
Transport Link definition:
Provides a description of the infrastructure of the Ethernet; Transport Link
can be:
Link Over TDM (using SDH or SONET technologies)
Link Over Cable
Link Over WDM
Link Over MPLS/T-MPLS
Link Over RPR, to manage ISA PR
Service Nodes definition :
gathering of defined NEs having the same OMSN User label & Location name
implicitly created and updated at the NE definition
3JK Issue 1.00
2 2 10
Construction application and related components
Management overview
Add ENE to a Domain
Configure
TDM Link
Add TDM Link to a Domain
Upload TDM terminations
Create Domain
Display
available NE
Add NE
Upload Ethernet
physical ports
Add physical port
to a Domain
Configure Ethernet
physical ports
Create ENE
Create ETP
Create NE
Add NE to a Domain
3JK Issue 1.00
2 2 11
Domain list
To display the Domain list :
1) Search Packet Construction Domains
A Domain is a distributed infrastructure made of NE, ENE, Transport Links and Edge Ports managed
together in order to supply an Connection-oriented or a Connection-Less or a T-MPLS infrastructure.
The attributes displayed for each Domain are :
User label
Domain Type
Bridge type
STP Type
Comment
The Domains ETS, Indirect, Provide Bridge and TMPLS are created by default and cannot be deleted
3JK Issue 1.00
2 2 12
Domain creation
To create a new Domain:
1) Actions Packet Construction Create Domain
To create a domain:
Enter a User Label
Enter a comment (optional)
Choose the Domain Type (ETS, Bridge, T-MPLS, Circuit Emulation, Packet Ring)
Choose the Bridge Type: only Provider Bridge is supported in this release
Choose the STP Type (STP, RSTP, MSTP, PVSTP, DISABLED), according to Bridge type
Choose the Ring Type (Closed, Open, Single NE), (only for Packet Ring Domain)
Click on OK
The Domain List is updated
3JK Issue 1.00
2 2 13
Domain properties, modification and deletion
To get the Domain Properties:
1) Select a Domain in list
2) Actions (or right mouse button) Properties
To modify the Domain Parameters:
2) Actions (or right mouse button) Modify
To delete a Domain :
2) Actions Domain Delete
It is possible to modify:
Domain User Label
Comment
The Domain List is updated
3JK Issue 1.00
2 2 14
Network Element list
To display the Network Elements list :
1) Search Packet Construction Network Elements Defined NEs
Defined NE are the NEs already present in the 1350OMS PKT database
The attributes displayed for each NE are :
Node User Label (only in case of OMSN provided with ISA board)
User label
NE Type
Software version
Bridge Type
Operational state
Local Access Control (LAC) state
Working state
Consistency state
Location Name
NE IP Address
Access Module type
Comment
Synchro State
Working Mode
Bridge Type
3JK Issue 1.00
2 2 15
Network Element discovery
To discover the Available Network Elements :
1) Search Packet Construction Network Elements Available NEs
This function consists in displaying all NEs suitable to be added to the 1350OMS PKT management.
The attributes displayed for each NE are :
Operator Label
Location Name
NE Type
Software Version
IP address
Operational State
LAC State
3JK Issue 1.00
2 2 16
Network Element creation
To add a Network Element in the PKT management:
Actions Packet Construction Define Network Element
1. Click here to display
the available NE list
The NE can be added in the PKT environment if:
The Operational state of the NE is Enabled
The LAC state of the NE is Denied
3JK Issue 1.00
2 2 17
Network Element creation [cont.]
3. Click here to confirm
the selection
5. Click on Apply
4. Set the related
options
2. Select a NE in the
list
The User Label is automatically assigned
Select a Working Mode: it is used to define which mix of transport technologies are enabled on NE.
According to the NE Type, only the possible combinations are shown
In case of Bridge Working Mode, select an STP Type
Enter a Comment (optional)
Click on OK
All resources of the NE are uploaded :
TDM terminations
Ethernet ports
Ethernet links over SDH terminated on this NE
The NE is defined into the PKT application with the following states :
Working status = normal
NE consistency state = consistent
All other states (operational state, LAC state, Inhibited Alarm state) are updated
The NE is removed from the Available Network Element list
3JK Issue 1.00
2 2 18
Working Mode
The Working mode is used to define which mix of transport
technologies are enabled on NE.
The possible combinations, with the corresponding managed
domains, are:
Virtual Bridge + EPTL Virtual bridge; ETS
Provider Bridge + EPTL Provider bridge; ETS
TMPLS + EPTL ETS; TMPLS
TMPLS + Provider Bridge + EPTL Provider bridge; ETS; TMPLS
ETS + Virtual Bridge + EPTL Virtual bridge; ETS
ETS + Provider Bridge + EPTL Provider bridge; ETS
EPTL ETS
ETS + EPTL ETS
ETS + MPLS + EPTL ETS; MPLS
Flexible Bridge + EPTL MAC, Virtual, Provider bridge; ETS
Indirect
3JK Issue 1.00
2 2 19
Network Element properties, modification and deletion
To get the Network Element Properties:
1) Select a Network Element in list
To modify the Network Element Parameters:
To delete a Network Element :
2) Actions Network Element Delete
It is possible to modify:
NE User Label
Comment
A NE can be deleted if not assigned to a Domain
The Network Element list is updated
3JK Issue 1.00
2 2 20
Add NE to a Domain
It is mandatory to add the NE, or its Ports, to a Domain, in
order to manage it in the Services environment
To add a Network Element in a Domain:
2) Actions Network Element Assign Network Element to Domain
the Domain list
3. Click on Apply
2. Select a Domain in
the list, and confirm
with the icon
Assignment of a NE to a Domain results in a global assignment of all resources to the Domain. (I.e.
assigning a NE to a bridge domain will set all local and remote ports with the Client Type attribute as
ETS_P)
N.B: the operator can also assign a single resource to a Domain (Ports, Links). in this case all the other
resources will not be modified as assignment. (Refer next pages for details)
N.B. The Domain selected for the assignment must be consistent with the Working Mode of the NE,
with regards also to the STP type attribute
3JK Issue 1.00
2 2 21
Ethernet physical port upload and display
To upload the Ethernet physical ports :
1) Select a NE in the NE list
2) Actions Network Element Upload Ethernet Physical Ports
To display the Ethernet physical ports :
2) Search Network Element Ethernet Physical Ports
Upload: this function consists in uploading the Ethernet physical port of the selected NE and is used,
manually by the operator, to solve a misalignment between the PKT DB and the NE.
For uploading or displaying, selected NE must be in Consistency state = Consistent
3JK Issue 1.00
2 2 22
Ethernet physical port configuration
To configure one Ethernet physical port :
1) Select a port into the Ethernet
physical port list
2) Actions Physical Ports
Configure
3) Set the related parameters
4) Click Ok to confirm
This function consists in defining some parameters for the Ethernet physical port:
- Auto Negotiation State: None/Enable/Disable/Not Supported
- Actual Interface Rate, when not fixed
- Traffic Type: Ethernet / MPLS/None (depending if the port is MPLS port or not)
- Duplex Mode: Full, Half
- Flexible port assignment (if supported) : Demarc Role: None/Customer Interface/Network Interface
- Pause Frame: Disabled/Symmetric/Asymmetric/Symmetric & Asymmetric
3JK Issue 1.00
2 2 23
Ethernet physical port modification
To modify one Ethernet physical port:
1) Select a port in the list
2) Actions Physical Ports Modify
Ethernet Physical Port
3) Modify the Manager Control
4) Click Ok to confirm
N.B: The Manager Control of the port can
be modified only after having assigned
the port to a Domain
The Manager Control is a PKT application local state of the port:
When Enabled the port is under the control of the Ethernet Service Traffic Management, that can
use it as Ethernet segment extremity. Its usage state is NotMeaningful in the Construction domain,
but is managed in a significant way by Ethernet traffic management.
The state of this attribute is automatically set to Enabled when the port is assigned to a Domain.
When Disabled the port is fully controlled by Construction domain that can use it as Extremity of
an internal Link over Cable (Ethernet or MPLS or T-MPLS as Supported Layer). Its usage state is
managed in the Constructor domain.
Disabled is the default attribute when the NE or the ENE is created.
3JK Issue 1.00
2 2 24
Assign port to a Domain
Each Ethernet physical port (not involved in a intra-domain link) can be
assigned to a Domain
To assign a specific port to a Domain :
1) Select a port into the Ethernet physical port list
2) Actions Physical ports Assign Resources to Domain
the Domain list
with the icon
The assignment to domain is not done on NE base: the granularity is per-port, taking into account the
limitation of some NE types to have all ports assigned to a domain type in one domain instance only
(I.e. 1850TSS)
The assignment of a port to a Domain make the port available, as Edge Port, in the Service
environment
The check to allow to move a port from one domain to another domain is based on the bandwidth
allocated for service
3JK Issue 1.00
2 2 25
Egress Shaping rate configuration
The egress shaping rate is the maximum bandwidth limiting the peak
rate of the egressing traffic
The operator is allowed to limit the egress throughput of one active
Physical interface, by tuning the egress shaping rate
To configure a specific Egress rate
on a port: :
1) Select a port into the Ethernet
physical port list
2) Actions Physical ports
Configure Egress Shaping rate
Assign the specific value
and click on Apply
The egress shaping is applied to the port when it is used as UNI port in case of Provider Bridge or T-MPLS
UNI interface.
It is possible to modify the Egress Shaping for activated or not activated ports.
3JK Issue 1.00
2 2 26
Ethernet physical port properties
To get the Ethernet physical port properties :
1) Select a port in Ethernet physical port list
2) Actions Properties
3JK Issue 1.00
2 2 27
TDM Termination upload and display
To upload the TDM Terminations:
2) Actions Network Element Upload TDM Terminations
To display the TDM Terminations :
2) Search Search from Network Element TDM Termination list
This function consists in uploading the SDH terminations of the selected NE and is used, manually by the
operator, to solve a misalignment between the 1350OMS PKT DB and the 1354RM, concerning a given
NE.
Selected NE must be in Consistency state = Consistent
The SDH terminations are automatically uploaded at the NE definition
3JK Issue 1.00
2 2 28
TDM Termination properties
To get the TDM Terminations properties :
1) Select a TDM Termination in the list
If the list of TDM terminations of the NE in the PKT is aligned with the SDH, the NE Working State is set to
Normal
3JK Issue 1.00
2 2 29
LAC state acknowledgement
LAC state is Post-granted due to :
Possible misalignment between
PKT DB and NE
Possible NE MIB modification
from 1320 CT, authorized by
the EML
The operator can acknowledge
at any time
Misalignment ?
OMSN with ISA board
EML
TDM PKT
NE
MIB
1320 CT
As the EML can authorize the NE access from the 1320CT, the data stored in the PKT could be different.
For this, after the Granted access and OS access back, the LAC state of the NE is modified in Post-
Granted
In this state the operator can acknowledge the possible misalignment between the PKT and the NE due
to a possible modification from the 1320CT.
3JK Issue 1.00
2 2 30
LAC state acknowledgement [cont.]
To acknowledge LAC state :
1) Select one or several NE in the NE list
2) Actions Network Element Acknowledge
3) Confirm accordingly
The NE LAC State must be Post-Granted
After confirmation the LAC state of the concerned NEs is set to Denied and the NE list is updated
3JK Issue 1.00
2 2 31
Node list
A Node is a gathering of defined NEs, with the characteristic of having
the same OMSN User Label and the same Location Name
To display the Node list :
1) Search Packet Construction Nodes
3JK Issue 1.00
2 2 32
Node Inventory list
To display the Node inventory list :
1) Select one or several Node in the list
2) Search Node Network Element List
It opens the NE list with the NE belonging to the selected service node.
3JK Issue 1.00
2 2 33
Exercise
Create a set of Domains
Create a set of NEs
For a given NE, display the properties
For a given NE, upload the Ethernet physical ports and the TDM
terminations
Assign some Ethernet physical port to a new Domain
Delete several NEs
3JK Issue 1.00
2 2 34
Blank Page
3JK Issue 1.00
2 2 35
2 External Network Element
management
3JK Issue 1.00
2 2 36
2 External Network Element management
ENE Definition
An External Network Element represents:
a Customer Edge Equipment (Customer Edge) (Customer Edge)
an Equipment into the network visible but not managed by the PKT (Inner (Inner
Equipment) Equipment)
An External Operator Network connected through IWI (Inter Working
Interface) (PVLAN Network) (PVLAN Network)
Customer Customer Edge Edge
PVLAN Network PVLAN Network
Inner Inner Equipment Equipment
The External Network Element management allows to define inside PKT, NEs or Networks or Customer
Edges in order to allow the operator to have a complete network view.
In a topology, some ENEs can be added to represent a NE or a set of NEs, which are internal to the
managed network but not directly administrated by the PKT: this is the role of the Inner Equipment,
connected through NNI interfaces.
An ENE can be used to represent Customer Edge Device; this object is included only in order to improve
the USM representation: this is the role of the Customer Edge, connected through UNI interfaces.
An ENE can be added to represent different Operator Networks: this is the role of the PVLAN Network,
connected through IWI Interfaces.
The Inner and the PVLAN External Network Elements can be used as Edge Node of the Ethernet Service,
while a Customer External Network Element is always outside of the Ethernet Service management.
3JK Issue 1.00
2 2 37
Broadcast TV ENE Definition
A Broadcast TV Broadcast TV External Network Element represents the SDH
broadcasting ring in a Broadcast TV application
Broadcast TV
VIDEO
SERVER
The External Network Element Broadcast TV allows the management of the BTV services by using SDH
broadcast path.
N.B: this feature is not available in current release
3JK Issue 1.00
2 2 38
External Network Element list
To display the External Network Element list :
1) Search Packet Construction Network Elements External
Network Element
3JK Issue 1.00
2 2 39
External Network Element creation
To create an External Network Element :
1) Actions Packet Construction Create External Network
Element
Insert a User Label
Choose a Role
An Inner ENE, or a PVLAN ENE, is a subset of NEs not managed by the PKT because not handled. The
connection between the managed network and the ENE is a Link over Cable to a NE.
A Customer ENE is an equipment outside the scope of the network management mainly located at
customer premises. It is connected via an external Link over Cable to a NE.
Resource assignment: the ENE does not support NE base Domain assignment: only specific resources
(ETP) can be assigned to a Domain
N.B:Role Broadcast TV is a specific function to be used for Broadcast TV application; see related
session for details
3JK Issue 1.00
2 2 40
ENE properties, modification and deletion
To get the ENE Properties:
1) Select a ENE in list
To modify the ENE Parameters:
To delete a ENE :
2) Actions External Network Element Delete
3JK Issue 1.00
2 2 41
External Termination Ports list
To get the External Termination Ports list:
1) Select one ENE in the list
2) Search External Network Element ETPs
All External Network Element are created with Manager Control attribute Disabled, that is suitable to
use it as extremity of a Link Over cable.
3JK Issue 1.00
2 2 42
External Termination Ports creation and deletion
To create an External Termination
Port:
1) From an opened ENE list, select an ENE
2) Actions External Network Element
Create ETP
To delete the External Termination
Ports:
1) Select one or several ETPs in the list
2) Actions External TP Delete
Number of ETP to
be added
Identifier to be
assigned to the first
added ETP
- 1st ETP to create = numerical value corresponding to the 1st ETP number to use
- Number ETP to create = numerical value between 1 and the maximum number of ETPs which can be
created on a ENE
3JK Issue 1.00
2 2 43
Assign ETP to a Domain
Each single external termination can be assigned to a Domain
To assign a specific ETP to a Domain :
1) Select an ETP into the ETP list
2) Actions External TP Assign Resources to Domain
the Domain list
with the icon
The assignment to domain is done on ETP base.
The assignment of an ETP to a Domain make the termination available, as Edge Port, in the Service
environment
The check to allow to move a port from one domain to another domain is based on the bandwidth
allocated for service
3JK Issue 1.00
2 2 44
Exercise
Create a set of ENEs with different role
For a given ENE, create a set of ETPs
For this ENE, open the ETPs list
Delete several ETPs and several ENEs
3JK Issue 1.00
2 2 45
3 Link Aggregation (LAG) management
3JK Issue 1.00
2 2 46
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)
MAC
Client
L
A
G
Physical
MAC 2
Physical
MAC 3
Physical
MAC 1
Physical
MAC 2
Physical
MAC 3
Physical
MAC 1
L
A
G
MAC
Client
Aggregation Link
Aggregation
Ports
Aggregation
Ports
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.
Actor and Partner ports (local and far sides) must be of the same type.
3JK Issue 1.00
2 2 47
LAG main target
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)
3JK Issue 1.00
2 2 48
Link Aggregation Control Protocol (LACP)
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.
L
A
G
Physical
MAC 2
Physical
MAC 3
Physical
MAC 1
Physical
MAC 2
Physical
MAC 3
Physical
MAC 1
L
A
G
LACPDU
LACPDU
3JK Issue 1.00
2 2 49
Frame distribution (Hash Key)
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.
The packets distribution over the constituting links is based upon
classification of the following masks:
1. <MAC Destination Address, MAC Source Address>
2. <MAC (DA), MAC (SA)> + MPLS Labels
3. <MAC (DA), MAC (SA)> + MPLS Labels + <C-VID, S-VID>
4. <MAC (DA), MAC (SA)> + MPLS Labels + <C-VID, S-VID>] + <IP SA, IP DA>
5. <MAC (DA), MAC (SA)> + MPLS Labels + <C-VID, S-VID>] + <IP SA, IP DA> +
<Destination Port Number, Source Port Number>
3JK Issue 1.00
2 2 50
Example
LAG size = 2 out of all the aggregated links, two are active and the rest are
stand-by
active
UNI
stand-by
NE A
1
2
3
PR=1
PR=2
PR=3
4
LAG#1
NE B
1
2
3
PR=1
PR=2
PR=3
4
LAG#2
Aggregate Link
UNI
UNI
NNI
UNI
UNI
active
UNI
NNI
Port Priority = 1,2,3
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.
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.
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.
3JK Issue 1.00
2 2 51
Enter the LAG size
Enter the Client Type
(ETS, ETB)
Enable (True) or Disable
(False) the LACP
Enter the Hash Key
Set the Port Priority
Select the NE and the load ports to
assign members to the LAG
Link Aggregation Group creation
LAG size: is the number of physical Ports that belong to the LAG Port. It is possible to add a number of
ports different from the LAG size:
If number of ports is less than the lag size: the LAG is in a degraded state.
If number of ports is greater than the lag size: the exceeding ports are in a stand-by status. They
provide protection to the working ports according to port priority.
Client Type: ETS or ETB
LACP: can be set at creation only
Hash Key: frame distribution can be modified even when LAG is active
Port Priority: priority is used to select active/stand-by physical ports.
3JK Issue 1.00
2 2 52
The Aggregated Logical Ports is suitable for any operation involving
Ethernet physical port: Link Over Cable, EVC, etc.
Aggregated Logical port
GUI impact
The Egress Shaping of a link Aggregation Group is the Rate of one Physical Interface multiplied by the
LAG size (corresponding to the number of aggregated links).
The Client Type of Link Aggregation Group can be ETS, ETS_P or ETB
3JK Issue 1.00
2 2 53
1. Select the LAG port in the list
2. Click twice on LAG port row; a +(expand ) mark will appear on the left
area in correspondence to the LAG port. Select +(expand ); you will
get the LAG port detail.
Display ports member of a LAG
3JK Issue 1.00
2 2 54
This function is used to modify LAG
port attributes, or to add/remove
a physical port member of the
LAG:
1. Select the LAG port in the list
2. Actions Physical Ports Modify
LAG Port
Modify a LAG port
Add o Remove a port in order to
increase or decrease the number of
port members a the LAG
Click here to add
Click here to
remove
The operator can modify:
the LAG Size
The LACP setting
The LAG frame distribution (Hash Key)
The number of physical ports members of the LAG port
The priority of the physical ports members of the LAG port
3JK Issue 1.00
2 2 55
Exercise
On a Network Element, create a LAG port with following attributes:
LAG size = 2
Number of ports = 3
3JK Issue 1.00
2 2 56
End of Module
Network Topology
3JK Issue 1.00
31
Module 1
Transport link Provisioning
3JK Issue 1.00
Section 3
System Operation
1350OMS
3JK Issue 1.00
System Operation Transport link Provisioning
3 1 2
Blank Page
Document History
3JK Issue 1.00
3 1 3
Module Objectives
create and modify a Link over TDM, a Link over Cable; define the
transport link characteristics.
3JK Issue 1.00
3 1 4
3JK Issue 1.00
3 1 5
Table of Contents
Page
1 Transport Link Overview 7
2 Link over TDM management 11
3 Link over Cable management 23
4 Inter-GUIs navigation 31
3JK Issue 1.00
3 1 6
3JK Issue 1.00
3 1 7
1 Transport Link Overview
3JK Issue 1.00
3 1 8
1 Transport Links overview
Transport links and Network Layering _ Operation
MPLS/T-MPLS
SDH, SONET, WDM, CABLE
Ethernet
Network
Layering
Network
Operation
Model
Customer
Service
Segment
EVC
MPLS/T-MPLS
layer
Transport
Per Traffic
flow Routing
WDM, SDH, GFP,
Ethernet /
Martini cables
Customer
Administrative
mgt
Topology
(EPL,EVPL,EPTL,
EVPLAN, .)
Extremities,
BW SLA &
traffic classif.
MPLS/T-MPLS layer
for flow ident.
Transport Link = infrastructure
(TDM or WDM or Cable) used by
MPLS/T-MPLS or Ethernet layers
The three main concepts are:
Ethernet Services:
An Ethernet service connect two or more PEs, each associated to a CE
It belongs to a given Customer; it is composed of one or more Ethernet Virtual Connections
The Ethernet services are implemented directly over SDH or SONET network layer (GFP or LAPS) or
over an intermediate MPLS or T_MPLS network layer or over an intermediate RPR like ring or
directly over a cable. An Ethernet service can use every type of combination of these network
support layers.
Ethernet Virtual Connections:
An Ethernet Virtual Connection (EVC) is an Ethernet end to end connection having a specified
topology (point to point, point to multi-point and multi-point to multi-point) and a packet
forwarding rules (unicast, multicast, broadcast).
One or more Ethernet Virtual Connection (EVC) form an Ethernet service.
Each unidirectional end to end connection belonging to an EVC is called Ethernet Segment: a point
to point EVC is formed by two unidirectional Ethernet segments. This is the elementary connection
managed by 1354 BM Ethernet.
Ethernet segments:
An Ethernet segment has associated a quality of service value (Guaranteed, Best Effort,
Regulated), the bandwidth and the forwarding rules based on VLAN management.
3JK Issue 1.00
3 1 9
Transport links and related applications
Link over Cable
Ethernet layer
Link over WDM
Ethernet layer
Link over TDM
MPLS/T-MPLS layer
Link over TDM
Ethernet (GFP) layer
Link over Cable
MPLS / T-MPLS layer
Transport Link for Ethernet Service can be:
- Link Over TDM, using SDH or SONET technologies, with or without interworking T_MPLS layer
- Link over Cables, with or without interworking layer such as MPLS or T_MPLS
- Link Over WDM, managed by external applications
3JK Issue 1.00
3 1 10
Link over Cable
Ethernet
layer
Transport Link types and related menu
Customer
Ethernet
Service
Construction
Services
Network
NEs
Link over TDM
or WDM
Ethernet layer
MPLS
PW
T-MPLStunnel
Link over Cable/TDM
with supported
T-MPLS layer
VC LSP
Link over Cable
with supported
MPLS layer
ENEs
ENEs
VC LSP LSP tunnel
Link over TDM
with supported
MPLS layer
3JK Issue 1.00
3 1 11
2 Link over TDM management
3JK Issue 1.00
3 1 12
1350OMS SDH/SONET and Packet interaction
Application 1350OMS Packet : Construction
Link between 2 TDM Terminations in Packet =
Link between 2 NAPs in SDH / SONET
SDH Packet
EML layer
OMSN NEs - ISA NEs - 1850TSS
Nodes & NAPs NE Terminations
CDN Z A Z A
Customer
Service
Segment
EVC
MPLS/T-MPLS
layer
Transport
3JK Issue 1.00
3 1 13
Link over TDM list
To display the Link Over TDM list :
1) Search Packet Construction Transport Links
Link Over TDM (Sdh/Sonet)
Customer
Service
Segment
EVC
MPLS/T-MPLS
layer
Transport
3JK Issue 1.00
3 1 14
Reminder 1/4 : 10 100 Mb Rate adaptive path
Select Ethernet for
service Type
Select Transport rate:
TU12/TU3/AU4/TU12-nV/TU3-nV
Select 10-100 Rate
Adaptive
Auto-negotiation:
automatic (enabled) 10Mb
manual (disabled) 10Mb
automatic (enabled) 100Mb
manual (disabled) 100Mb
Select the total
concatenation level
Click on Next
The Auto-Negotiation setting can be changed further.
3JK Issue 1.00
3 1 15
Select the Extremities
of the Path
Click on Next
3JK Issue 1.00
3 1 16
Complete the configuration
(refer to 1350OMS-SDH
User Guide for details)
Click on Apply
to confirm
3JK Issue 1.00
3 1 17
Reminder 4/4 : 1Gb/10Gb Rate adaptive path
Select Ethernet for
service Type
Select 1G or 10G
Rate Adaptive
Auto-negotiation:
(only available for 1Gb)
Automatic (enabled)
Manual (disabled)
Click on Next and proceed
in the configuration
Select Transport rate:
(see Notes)
Select the total
concatenation level
The Auto-Negotiation setting can be changed further.
Allowed Transport Rate:
1G Rate Adaptive: Au4-nv, TU3-nv, TU12-nv
10G Rate Adaptive: Au4-nv, TU3-nv
3JK Issue 1.00
3 1 18
Link over TDM configuration
To configure a Link over TDM:
1) From Link Over TDM List,
select a Link
2) Action Link Over SDH Configure
3) According to the boards, can be set:
Supported Layer
Protocol Type
This option is used when the operator needs to modify the Supported layer (Ethernet or MPLS) or the
Protocol Type.
Supported layer :
MPLS, (for ES16, PR-EA)
Ethernet
The Supported layer must be set to MPLS if the operator wants to make it available for MPLS environment
(not available in current release)
Protocol Type :
LAPS (Ethernet)
GFP (Ethernet)
HDLC (MPLS)
3JK Issue 1.00
3 1 19
Assign Link to a Domain
A Link over TDM must be assigned to a Domain, in order to use it as allocation constraint
To assign a specific Link to a Domain :
1) Select a Link into the Link Over TDM list
2) Action Link Over SDH Assign Resources to Domain
the Domain list
with the icon
The assignment to Domain is mandatory in order to make such resource fully available for Connection
Less or Connection Oriented Services
The Link must be associated to a T-MPLS Domain if the operator wants to make it available for T-MPLS
purpose
The assignment of Link to a domain automatically assign the specific NNI ports to a domain
N.B: the assignment of the Link to a Domain is not required if the Link is the boundary of different
technological domains: in this case each IWI interface shall be managed exploiting all the UNI
capabilities according to the specific domain
3JK Issue 1.00
3 1 20
Link over TDM deletion
Link Over TDM must be deleted by SDH/SONET layer of 1350OMS.
1. Open Path list:
Search SDH (SONET) Paths
Select a path
2. manage the Path life cycle steps as follow:
- Uncommission
- Deimplement
- Deallocate
- Remove
3JK Issue 1.00
3 1 21
Link over TDM properties and modification
To get the Link Over TDM Properties:
1) Select a Link in list
2) Action (or right mouse button) Properties
To modify the Link Over TDM Parameters:
2) Action (or right mouse button) Modify
(only User Label and Comment can be modified)
3JK Issue 1.00
3 1 22
Exercise
Between two NEs managed by the SDH, according to the Classroom
setup:
create an SDH path with an Ethernet supported layer
3JK Issue 1.00
3 1 23
3 Link over Cable management
3JK Issue 1.00
3 1 24
Link over Cable list
Application 1350 PKT Construction:
a Link over cable is a way to connect two NE, or
one NE and one ENE, using Ethernet Physical
Ports
To display the Link Over Cable list :
1) Search Packet Construction Transport Links
Link Over Cable
Customer
Service
Segment
EVC
MPLS/T-MPLS
layer
Transport
3JK Issue 1.00
3 1 25
Link over Cable creation
To create a Link Over Cable :
Actions Packet Construction Create Link Over cable
the available NE list
1. Enter User Label
and Comment
After the creation, the Link over Cable has the following attribute:
Available status is set to Normal
The Supported Layer is MPLS or Ethernet, (only Ethernet for VLAN Network), the Manager Control of
the Transport Link and of the Ethernet physical port of the NE must is Disabled
The Interface Type is NNI
3JK Issue 1.00
3 1 26
Link over Cable creation [cont.]
4. Click here to confirm
the selection
5. Click here and select
a Port in the list
3. Select a NE in the
list
6. Assign the second
extremity of the Link
3JK Issue 1.00
3 1 27
Assign Link over Cable to a Domain
A Link over Cable must be assigned to a Domain, in order to use it as allocation
constraint
To assign a specific Link to a Domain :
1) Select a Link into the Link Over cable list
2) Action Link Over Cable Assign resources to domain
the Domain list
with the icon
The assignment to Domain is mandatory in order to make such resource fully available for Connection
Less or Connection Oriented Services
The Link must be associated to a T-MPLS Domain if the operator wants to make it available for T-MPLS
purpose
The assignment of Link to a domain automatically assign the specific NNI ports to a domain
After the assignment, the Link over Cable has the following attribute:
Available status is set to Normal, in Failure or Degraded, depending on alarm presence on the port
The Manager Control of the Transport Link (not physical port) is set to Enabled
N.B: the assignment of the Link to a Domain is not required if the Link is the boundary of different
technological domains: in this case each IWI interface shall be managed exploiting all the UNI
capabilities according to the specific domain
3JK Issue 1.00
3 1 28
Link over Cable properties, modification and deletion
To get the Link Over Cable Properties:
To modify the Link Over Cable Parameters:
(only User Label and Comment can be modified)
To delete the Links over Cable :
1) Select one or several Links over Cable in List
2) Action Link Over Cable Delete
(see Notes Page for details)
Modification:
at the beginning of the operation, the working state is set to Modifying
If the User label is modified, the corresponding transport segment (in Services domain) or transmission
path (in MPLS domain) is modified too
Deletion:
After the deletion confirmation, the working state is set to Removing
If the manager control is disable, the deletion is authorized; If the manager control is enabled, the
usage of the corresponding transport segment (in Ethernet management domain) or transport link (in T-
MPLS domain) is checked. If some Ethernet segment or Tunnel are carried by it, the deletion is
refused. In other case, the corresponding transport segment or T-MPLS transport link must be deleted
before the Link over Cable.
Then the Links over Cable can be removed. After deletion, the port usage state is set to Idle.
3JK Issue 1.00
3 1 29
Exercise
Between two NE managed by PKT:
Create a Link over Cable and assign it to a Provider Bridge Domain
Create a Link over cable interconnecting two LAG ports
Between one NE managed by the PKT and one ENE :
Create a Link over Cable and assign it to a ETS Domain
3JK Issue 1.00
3 1 30
Blank Page
3JK Issue 1.00
3 1 31
4 Inter-GUIs navigation
3JK Issue 1.00
3 1 32
Services USM
Construction USM
The operator can navigate from Construction environment to the
Services environment in order to display the available constraints for
the services:
1) Select a Transport Link in the relative list (i.e: Link over Cable, Link over T-MPLS, ...)
2) Search Link over ..... Show <entity denomination> (i.e. ETS Transport
Link)
Navigation towards Services environment
Example:
Selecting, in the Construction USM, a Link belonging to an ETS domain, the option opens the ETS
Transport Link list in Ethernet Management USM
Depending on the selected Link, it is allowed navigation towards:
ETS Transport Link
Bridge Transport link
MPLS Section
T-MPLS Section
3JK Issue 1.00
3 1 33
Construction USM
T-MPLS USM
1) Select a Transport Link in the relative list (i.e: Link over Cable, ...)
2) Search Link over ..... Show <entity denomination> (i.e. T-MPLS
Section)
Navigation towards T-MPLS environment
Example:
Selecting, in the Construction USM, a Link belonging to a T-MPLS domain, the option opens the T-MPLS
section list in T-MPLS Management USM
3JK Issue 1.00
3 1 34
Exercise
Practice the navigation from the previously created
links :
Over TDM or Cable ETS or Bridge or T-MPLS layers
3JK Issue 1.00
3 1 35
End of Module
Transport link Provisioning
3JK Issue 1.00
32
Module 2
Traffic descriptor Provisioning
3JK Issue 1.00
Section 3
System Operation
1350OMS
3JK Issue 1.00
System Operation Traffic descriptor Provisioning
3 2 2
Blank Page
Document History
3JK Issue 1.00
3 2 3
Module Objectives
manage a Traffic Classifier, a VLAN Type, a Color Profile
manage the Traffic Descriptors for Ethernet segment
3JK Issue 1.00
3 2 4
3JK Issue 1.00
3 2 5
Table of Contents
Page
1 Traffic classifier management 7
2 VLAN Types management 23
3 Color profile management 31
4 Ethernet Traffic descriptor management 41
3JK Issue 1.00
3 2 6
3JK Issue 1.00
3 2 7
1 Traffic classifier management
3JK Issue 1.00
3 2 8
Ethernet frame IEEE 802.3 _ Reminder
Preamble
Destination
MAC
Address
6 8
Source
MAC
Address
6
Data
-
FCS
4
Type or
Length
2
Number of bytes
The common fields are:
Preamble - Used to synchronise the receivers
MAC addresses - Destination and Source MAC @ such as: 00 20 60 12 34 56
Type - Type of protocol used in the DATA field of the frame
Length - Length of the data field (from 46 to 1500 bytes)
Data - Client Data
FCS - Frame Check Sequence also called CRC taking into
account the fields from Destination MAC @ to Data
Ethernet frames
O OO O
The main characteristics of a MAC address are:
assigned individually to each node by the manufacturer,
located into the network interface card,
manage by the layer 2 (Data) of the related protocol stacks,
made of 48 bits usually written in hexadecimal form,
the OUI (first 24 bits) is assigned to an organisation by the IEEE-SA
OUI Organisationally Unique Identifier
002032 Alcatel Taisel
002060 Alcatel Italia S.P.A.
008021 Alcatel Canada Inc. (was Newbridge Networks Corporation)
008039 Alcatel stc Australia
00C0BE Alcatel - Sel
00089A Alcatel Microelectron
00118B Alcatel-Lucent Calabasas CA (USA)
0017CC Alcatel-Lucent Piano TX (USA)
001C8E Alcatel-Lucent Mountain View CA
IEEE-SA IEEE Standard Association
3 types of MAC addresses:
All bits=1 for Broadcast
Low order bit of the first byte = 1 for multicast
Others for unicast
OUI Node identifier
OO 20 60 00 0A 9F

3JK Issue 1.00
3 2 9
VLAN definition _ Reminder
Role of Switch and
Routers in VLANs
Router
Switch
Switch
Switch
Access control
between VLANs
VLAN
Group #1
VLAN
Group #2
VLAN Tagged
Ethernet frames
O OO O
A VLAN consists of a single broadcast domain and solves the scalability problems of large flat networks by
breaking a single broadcast domain into several smaller domains or VLANs.
LAN switches can be used to segment networks into logically defined virtual workgroups. This logical
segmentation is commonly referred as VLAN communication. Switches can be used as the core device
that controls individual VLANs.
Routers can provide inter VLAN communication and / or VLAN access to shared resources such as servers
and hosts.
3JK Issue 1.00
3 2 10
Tagged Ethernet frames IEEE 802.1P / Q _ Reminder
Preamble
Destination
MAC
Address
6 8
Source
MAC
Address
6
Data
-
FCS
4
Type
or
Length
2
The IEEE 802.1p is an extension of the IEEE 802.1Q (VLAN tagging)
standard and they work in tandem. The 802.1p defines the prioritization
field
The added fields are :
1Q- 802.1Q field (a constant fixed value)
TCI - Tag Control Information
O 3 bits: user priority 802.1P (8 levels: from 0 to 7)
O 1 bit: CFI (Canonical Field Identifier)
O 12 bits: VLAN identifier 802.1Q (0 to 4095)
1Q
2
TCI
2
Q- Tagged
Ethernet frames
O OO O
Number of bytes
Hereafter, an example giving the relation between the priority levels and the customer applications:
Reserved - less than best-effort
Traffic Type
Best Effort
Excellent Effort
Controlled Load
Video, < 100ms Latency and Jitter
Voice, < 10ms Latency and Jitter
Network Control
Background
Priority
1
2
3
4
5
6
7
0
Class
High
Low
3JK Issue 1.00
3 2 11
Differentiated Service _ Reminder
The Differentiated Service is a coarse-grained, Class-based mechanism
for traffic management.
It operates on the principle of traffic classification, where each data packet
is placed into a limited number of traffic classes; each router of the network
is configured to differentiate traffic based on its class. Each traffic can be
managed differently, ensuring preferential treatment for higher-priority
traffic on the network
Time
Data Packet Stream
Time
Time
Fixed link speed
Voice Packet Stream
3JK Issue 1.00
3 2 12
DSCP_Reminder
DSCP (Differentiated Service Code Point) is a field inside the IPv4
packet, that specifies a particular per-hop behaviour (PHB) applied to
the packet
Different Class of Service are assigned to the traffic: routers at the edge of
the network classify packets and mark them with DSCP value in a DiffServ
network. This in order to provide the appropriate QoS treatment.
DSCP is mapped in the six most significant bit of the DiffServ field
0 1 2 3 4 5 6 7
DSCP
CU
Ipv4 header fragment
DSCP = Differentiated Service Code Point
CU = Currently Unused
3JK Issue 1.00
3 2 13
IP DSCP management
IP routers, in charge of managing the frontier between IP and
Ethernet, should translate the IP Diff-Service Code point (DSCP) field
into Ethernet priority bits. However, since some routers dont perform
that kind of translation, the NE functionalities have been extended to
IP DSCP management
Router
Access control
between VLANs
Therefore, an operator managing an Ethernet network may offer differentiated services also when IP
routers are not able to write the PRI bits of the transmitted Ethernet frames. In fact, the NE inspects
the code-point of the IPv4 header, representing PHB and pushes at the NNI a VLAN tag whose PRI bits
value encodes that PHB information.
3JK Issue 1.00
3 2 14
O OO OFrames are switched
depending on priority
Traffic Classifier definition
Role of the Traffic Classifier :
Core Network
Edge Edge
O OO OFrames are Identified
(by port / VLAN/EtherType)
O OO Oare Classified by
priority level
O OO Oare Tagged according
classification criteria
Traffic frames
Traffic frames
Customer
Service
Segment
EVC
MPLS/T-MPLS
layer
Transport
Traffic Classifier: It works as filter matching the incoming frame types to be transported up to the far
end through the SDH network.
Policy Control
The policy control is an application to configure the edge nodes with QoS parameters, IEEE 802.1p, or
as alternative, DSCP classification (by port).
At the edge of the network, frames (identified by port/VLAN/EtherType) are classified in a set of
priority levels and tagged according to classification criteria. In the core of the network, frames are
switched using different queues, based on their priority tag.
The Ethernet priority bits or the IP DSCP are used together with the VLAN id (forming just single
values) to individuate an Ethernet traffic flow. A traffic type (Guaranteed, Regulated or Best Effort)
and a bandwidth are associated to this flow is. When ISA PR EA or ISA ES16 or 4G NE is the edge node,
these information (traffic type and bandwidth) will be mapped on PIR/CIR (and CBS / PBS), then
classified in term of priority (green, yellow or red frames) and then mapped on MPLS layer or on SDH
VC. In case of ISA E/FE/GE board (Q3 board) these bits are transparently transported.
The ingressing Ethernet frames can be managed by a policy colour blind (the incoming
classification is not used) or colour aware where the priority bits or the IP DSCP are taken into
account by the NE.
N.B: the NE manages the IPv4 DSCP translation only at UNI/IWI interface, while at NNI handle only
the classification based on PRI bits
3JK Issue 1.00
3 2 15
Traffic Classifier location
SDH Matrix
ES Unit
Ethernet
Port
OMSN
Link over SDH
SDH Path
SDH
upper
layers
NAP
SDH Term.
SD
H
SD
H
CIR
PIR
Header
=
Ports
?
+
=
Forwarding Policer Classifier Scheduler
Mapping
De-mapping
Control processing unit
The Traffic classifier is located at the Edge input of the Ethernet port. It works as filter matching the
incoming frame types to be transported up to the far end through the SDH network.
3JK Issue 1.00
3 2 16
Traffic Classifier criteria
Customer traffic Classification criteria:
The following classification criteria are applicable to the Ethernet flow:
Physical Port
VLAN tag
Priority bits
IP DSCP
Ether Type
The global way to manage incoming Ethernet frames allows definition of
several Classification combinations.
3JK Issue 1.00
3 2 17
Traffic Classifier management chain
Application 1350OMS Packet Services :
Traffic classifier management chain:
Modify Traffic
Classifier
Associate to
Ethernet segment
Create Traffic
Classifier
Delete Traffic
Classifier
Disassociate from
Ethernet segment
Customer
Service
Segment
EVC
MPLS/T-MPLS
layer
Transport
3JK Issue 1.00
3 2 18
Traffic Classifier list
To display the Traffic Classifier list:
Search Packet Services Traffic Classifiers
Three Traffic Classifier (_FixedClassifier_1,2,3), with VLAN Id = Dont Care (4097) and Priority Id =
Dont Care, are created by default during the 1354BM installation
3JK Issue 1.00
3 2 19
Traffic Classifier creation
To create a Traffic classifier :
1) Actions Packet Services
Create Traffic Classifier
2) Enter :
User label
Classification Type
Priority Id
VLAN Id
IP DSCP
Priority Max
VLAN Max
IP DSCP Max
EtherType
3) Click on Ok
Classification Type specify a criteria allowing several Classification combination:
Default
Untagged + NO IP
VLAN + NO IP
Untagged
Untagged + EtherType
Untagged + NO IP + EtherType
VLAN + NO IP + EtherType
Untagged +DSCP + IP
VLAN + DSCP + EtherType
VLAN
VLAN + EtherType
- Default specifies a Dont care criteria for all values
- NO IP means that only no IP packet are admitted (IP DSCP = 64)
- IP means that only IP packets are admitted (EtherType = 0x800)
When a combination containing DSCP is selected, the EtherType value is automatically set to IP
(0x0800)
Priority max, VLAN max and DSCP max represent the maximum value of priority range, VLAN range and
DSCP range. (0 if a range is not used)
3JK Issue 1.00
3 2 20
Traffic Classifier modification
To modify a Traffic classifier :
1) Select a Traffic classifier in the
list :
2) Actions Modify
3) Modification are possible for:
User label
Priority Id
VLAN Id
IP DSCP
Priority Max
VLAN Max
IP DSCP Max
EtherType
4) Click on Ok
3JK Issue 1.00
3 2 21
Traffic Classifier properties and deletion
To get the Traffic Classifier properties:
1) Select a Traffic Classifier in the list
To delete the Traffic Classifiers :
1) Select one or several Traffic Classifiers in the list
2) Actions Traffic Classifier Delete
3) Confirm
3JK Issue 1.00
3 2 22
Exercise
Create a set of Traffic Classifiers, using different classification criteria
Modify at least one Traffic Classifier
Delete several Traffic Classifiers
3JK Issue 1.00
3 2 23
2 VLAN Types management
3JK Issue 1.00
3 2 24
2 VLAN types management
Customer / Provider VLAN _ Frame formats
DA
(6 Byte)
Type (8100)
(2 Byte)
Q-VLAN Tag
(2 Byte)
Length/Type
(2 Byte)
Data
(< 1500 Byte)
FCS
(4 Byte)
Untagged Frame
DA
(6 Byte)
SA
(6 Byte)
Length/Type
(2 Byte)
Q-tagged Frame
SA
(6 Byte)
Data
(< 1500 Byte)
FCS
(4 Byte)
Type (88a8)
(2 Byte)
S-VLAN Tag
(2 Byte)
DA
(6 Byte)
SA
(6 Byte)
Length/Type
(2 Byte)
S-tagged Frame
Data
(< 1500 Byte)
FCS
(4 Byte)
Type (88a8)
(2 Byte)
S-VLAN Tag
(2 Byte)
DA
(6 Byte)
SA
(6 Byte)
Length/Type
(2 Byte)
Double tagged Frame
Data
(< 1500 Byte)
FCS
(4 Byte)
Type (8100)
(2 Byte)
Q-VLAN Tag
(2 Byte)
The VLAN type entity models the VLAN Tag Protocol Type allowing the operator to give a name (user
label) to a specific VLAN Tag Protocol Type (either standard or not) in order to ease its subsequent
usage in the scope of VLAN management.
The standard Type for Q-VLAN Tag Protocol is defined 8100.
The standard Type for S-VLAN Tag Protocol is defined 88a8.
It can be associated to :
a Provider network
an Ethernet edge port before the creation of a related Ethernet segment (described in this chapter).
an Ethernet segment (described in the End to end Ethernet provisioning management Ethernet
segment management section ) . In this case, the association with the related Edge ports will be
made during the segment life cycle management.
3JK Issue 1.00
3 2 25
VLAN Types management chain
VLAN type management chain:
Modify VLAN
type
Ethernet edge port
association
Create VLAN
type
Delete VLAN
type
Ethernet edge port
disassociation
Customer
Service
Segment
EVC
MPLS/T-MPLS
layer
Transport
3JK Issue 1.00
3 2 26
VLAN Types list
To display the VLAN types List :
Search Packet Services VLANs
3JK Issue 1.00
3 2 27
VLAN Type creation
To create a VLAN Type :
1. Actions Packet Services
Create VLAN Type
2. Enter :
User label
VLAN Tag Protocol Type
3. Click on Ok
A VLAN Protocol type value could be duplicated according to its usage.
If the Protocol Type is equal to 8100 (hex), Role attribute is set to Customer, otherwise Role is set to
Provider.
3JK Issue 1.00
3 2 28
VLAN Type modification, properties, deletion
To modify a VLAN Type :
1) Select a VLAN type in the list
2) Actions Modify
User label
VLAN type
4) Click on Ok
To get the VLAN Type properties:
1) Select a VLAN in the list
To delete the VLAN types :
1) Select one or more VLAN Types in
the list
2) Actions VLAN Delete
A VLAN Type can be modified or deleted when it is not associated to a Provider network, an Ethernet
edge port or an Ethernet segment
3JK Issue 1.00
3 2 29
Ethernet Edge Port and VLAN Type association
To display the Ethernet Edge Port and VLAN Type association :
Search Packet Services Connection Oriented
(ConnectionLess, T-Mpls) ETS (Bridge, T-MPLS) Edge Ports
The Ethernet Edge physical ports represent the border of the network managed by the 1350OMS-PKT.
They are the extremities of Ethernet services, EVCs and Ethernet segments.
An Ethernet Edge Physical port is the image, on the Ethernet Domain, of either an Ethernet Physical Port
or an External Termination Port of the Construction Domain
It cannot be explicitly created or deleted by the operator: it is automatically created when a proper PPT
(ETH Physical Port) or ETP (External Termination Point) is assigned to the Domain and it is
automatically deleted when it is de-assigned.
Whenever a new edge physical port is created, it comes with an Activation State down and will be Up
when the service to which the edge port belongs is implemented. If the edge port is ETP, then is
created with Activation State Up and the VLAN Type is the default one (I.e. 8100).
3JK Issue 1.00
3 2 30
Create a set of VLAN types
Modify an Ethernet Edge port in order to take into
account a created VLAN type.
Exercise
3JK Issue 1.00
3 2 31
3 Color profile management
3JK Issue 1.00
3 2 32
Color Profile definition _ Reminder
A color profile allows the operator to define a priority in
accepting or rejecting incoming frames at the network
boundary ( INFLOW of ES unit).
A color profile is a customized table making a relation
between Customer priority and the Priority queue in the
switch.
Example:
Red
Provider priority
Color profile
Yellow
Yellow
Yellow
Green
Green
Green
Red
User priority
VLAN (802.1p)
1
2
3
4
5
6
7
0
Customer
Service
Segment
EVC
MPLS/T-MPLS
layer
Transport
After its creation, a color profile has to be associated to a Color aware Ethernet segment to be taken
into account. Moreover, a traffic classifier and a traffic descriptor will have also to be associated to
this Ethernet segment.
A given color profile will be downloaded as an ES unit configuration during the related Ethernet segment
implementation.
3JK Issue 1.00
3 2 33
Color Profile definition _ Reminder [cont.]
SDH Matrix
ES Unit
Ethernet
Port
OMSN
Link over SDH
SDH Path
SDH
upper
layers
NAP
SDH Term.
SD
H
SD
H
CIR
PIR
Header
=
Ports
?
+
=
Forwarding Policer Classifier Scheduler
Mapping
De-mapping
Control processing unit
According to the traffic contract, to the policing mode, and to the available bandwidth, the priority of a
data flow into the Provider network is assigned by the traffic scheduler of the system.
Considering an ES unit as an Ethernet switch, 3 queues, corresponding to green, yellow and red will be
managed for a given port.
3JK Issue 1.00
3 2 34
Color Profile definition _ Reminder [cont.]
Unit configuration :
Traffic Descriptor, Policing Mode and Color Profile for INFLOW resource
As assigned by the
ColorProfile and
Policing effect
Bound (3) color-aware
GREEN or YELLOW
or RED
Unbound color-blind
GREEN or YELLOW
Unbound disabled REGULATED
GREEN or RED
color-blind
GREEN
Unbound disabled GUARANTEED
YELLOW or RED
color-blind
YELLOW
Unbound disabled BEST EFFORT
Provider-Colouring
(2)
Color Profile (1) Policing Mode Traffic
Descriptor
For a given INFLOW, the coloring of the Provider VLAN is managed as follow:
The scheduler of an Ethernet data flow can be indicated on the 3 user priority bits (802.1p) of the
Tagged Ethernet frame or on the 6 DSCP bits of the IP packet.
A Color Profile mode has been introduced in order to define if the Color Profile has been built
in order to manage color for NOT IP packets or for IP Packets.
The provider traffic can be coloured if the S-VLAN mode is enable :
green for frames to be passed in any case;
yellow for frames to be passed if the band is available;
red for frames to be discarded.
(1) Unbound means that NoProfile is associated to the ColorProfile field; Bound means that
a Color Profile has been assigned.
(2): in cases different from Color Aware, the colouring is performed by the scheduler, depending on
the traffic condition.
(3): in this case the Priority value of the Classifier associated to this InFlow must be different from
untagged or dont care.
3JK Issue 1.00
3 2 35
Color Profile management chain
Color Profile management chain:
Modify Color
profile
Ethernet segment
assignment
Create Color
Profile
Delete Color
Profile
Ethernet segment
de-assignment
Customer
Service
Segment
EVC
MPLS/T-MPLS
layer
Transport
3JK Issue 1.00
3 2 36
Color Profile list
To display the Color Profile List :
Search Packet Services Color Profiles
The list is displayed, where only the Color Profile Mode is shown; details about the color assignment can
be get from the properties option
3JK Issue 1.00
3 2 37
Color Profile creation
To create a Color Profile:
Create Color Profile
2) Enter :
User label
3) Select a Color Profile Mode: the
menu below will be set
accordingly: select a color for
each priority
3) Click on Ok
In case of Priority mode, the operator can assign a color to 8 different User Priority (0. 7)
In case of DSCP mode, a color can be assigned to 64 different Code Point (0 .. 63)
3JK Issue 1.00
3 2 38
Color Profile modification, properties, deletion
To modify a Color Profile:
1) Select a Color Profile in the list
2) Actions Modify
User label
Color Profile Mode
and/or
the Color assignment
4) Click on Ok
To get the Color Profile properties:
1) Select a Color Profile in the list
2) Actions (or right mouse button)
Properties
To delete the Color Profile:
1) Select one or more Color Profiles
in the list
2) Actions Color Profile
Delete
3) Confirm
A Color profile can be modified or deleted when:
- it is not associated to a segment
- it is associated to a Defined segment
3JK Issue 1.00
3 2 39
Exercise
Create a set of Color Profiles with different Color Priority Mode and
different assignments
Modify and delete a Color Profile
3JK Issue 1.00
3 2 40
Blank Page
3JK Issue 1.00
3 2 41
4 Ethernet Traffic descriptor
management
3JK Issue 1.00
3 2 42
4 Ethernet Traffic descriptor management
Traffic descriptor definition _ Reminder
The Traffic descriptor allows to describe the characteristics of
an Ethernet segment in term of Class of Service (CoS) and
bandwidth.
End to End
ETHERNET SERVICE
Customer Customer
Customer
Service
Segment
EVC
MPLS/T-MPLS
layer
Transport
3JK Issue 1.00
3 2 43
Traffic descriptor definition _ Reminder [cont.]
CIR=0
Bandwidth
CIR
CIR=PIR PIR
PIR
GA
BE
Best Effort Regulated Guaranteed
Ethernet
Best Effort Assured Expedited
T-MPLS
TDM VC-nv
Best Effort
Guaranteed
Guaranteed bandwidth
Reserved and always available
Unavailable to other traffic types
Regulated bandwidth
CIR defines committed delivery
PIR allows bursting
Best Effort bandwidth
NO Commitment, uses whatever bandwidth is left over
BE bandwidth pool can be dimensioned
Peak Information Rate
It is the maximum rate at which packets are allowed to burst above the CIR.
Committed Information Rate
The CIR is the minimum guaranteed rate that the network will deliver for an Ethernet
Transport Service (ETS) flow under normal operating conditions.
Peak Burst Size
It specifies the maximum amount of buffering allocated for an Ethernet Transport Service (ETS)
flow. The incoming traffic offered over the PIR is buffered up to the specified PBS. Once all
buffers are depleted, all excess traffic is typically dropped. PBS buffers are allocated to absorb
the burst when the traffic is continuously received at the line rate.
Committed Burst Size
The CBS is associated with the CIR and specifies the amount of buffering allocated for Ethernet
packets to be en-queued when the Ethernet Transport Service (ETS) flow is continuously
received.
3JK Issue 1.00
3 2 44
Traffic descriptor management chain
Traffic descriptor management chain:
Modify Traffic
Descriptor
Associate to
Ethernet segment
Create Traffic
Descriptor
Delete Traffic
Descriptor
Disassociate from
Ethernet segment
3JK Issue 1.00
3 2 45
Traffic descriptor list
To display the Traffic Descriptor List :
Search Packet Services Traffic Descriptors
Four Traffic descriptor are created by default during the PKT installation
The attribute displayed for each Traffic descriptor are:
User Label
Class of Service (Guaranteed, Regulated, Best Effort, Guaranteed2, Regulated1, Regulated3,
Regulated4, Background)
CIR (Committed Information Rate)
PIR (Peak Information Rate)
CBS (Committed Burst Size)
PBS (Peak Burst Size)
3JK Issue 1.00
3 2 46
Traffic Descriptor Creation
To create a Traffic Descriptor:
Create Traffic Descriptor
2) Enter :
User label
Class of Service
Traffic parameter, according to
the CoS
3) Click on Ok
Class of Service (Guaranteed, Regulated, Best Effort, Guaranteed2, Regulated1, Regulated3,
Regulated4, Background)
- CIR = Committed information rate : in Kb/s
- PIR = Peak information rate : in Kb/s
- CBS = Committed burst size : in bytes
- PBS = Peak burst size : in bytes
(PBS > CBS) & (PBS 0) (PBS = CBS) & (PBS > 0) > 0 PBS
(PIR CIR ) & (PIR > 0) (PIR = CIR) & (PIR > 0) > 0 PIR
(CBS 0) & (CBS PBS)
If (CBS > 0), (CIR > 0)
If (CBS = 0), (CIR = 0)
(CBS = PBS) & (CBS > 0) 0 CBS
(CIR PIR ) & (CIR 0)
If (CIR > 0), (CBS > 0)
If (CIR = 0), (CBS = 0)
(CIR = PIR) & (CIR > 0) 0 CIR
REGULATED GUARANTEED BE Values
3JK Issue 1.00
3 2 47
Traffic descriptor modification, properties, deletion
To modify a Traffic descriptor:
1) Select a Traffic Descriptor in the
list
Modify
User label
Class of Service
Traffic parameters
4) Click on Ok
To get the Traffic Descriptor
properties:
1) Select a Traffic Descriptor in the
list
Properties
To delete the Traffic descriptor:
1) Select one or more Traffic
Descriptors in the list
2) Actions Traffic Descriptor
Delete
3) Confirm
3JK Issue 1.00
3 2 48
Exercise
Create a set of Traffic descriptors
Modify at least one Traffic descriptor
Delete several Traffic descriptors
3JK Issue 1.00
3 2 49
End of Module
Traffic descriptor Provisioning
3JK Issue 1.00
33
Module 3
3JK Issue 1.00
Section 3
System Operation
1350OMS
3JK Issue 1.00
System Operation Ethernet Service Provisioning
3 3 2
Blank Page
Document History
3JK Issue 1.00
3 3 3
Module Objectives
Manage the End to End Ethernet Services provisioning
3JK Issue 1.00
3 3 4
3JK Issue 1.00
3 3 5
Table of Contents
Page
1 End to End Ethernet service concept 7
2 Customer management 17
3 Ethernet Service management 21
4 Ethernet Service type 25
5 Ethernet Virtual Connection management 33
6 Ethernet Segment management 47
7 Ethernet segment life cycle 65
3JK Issue 1.00
3 3 6
Page
3JK Issue 1.00
3 3 7
1 End to End Ethernet service concept
3JK Issue 1.00
3 3 8
Global definition & provisioning steps
End to End concept is spread over 4
levels :
Customer
Ethernet Service user
CPE equipment connected to the Network Ethernet Edge
physical port
Ethernet Service
Description of a service belonging to a given customer.
It is defined by a SLA (Service Level Agreement)
Ethernet Virtual Connections (EVC)
Described in term of association of two or more
Ethernet Edge Points and in terms of the specific
topology realized. It is associated to the Ethernet
Segments
Ethernet Segment
Unidirectional connection between Ethernet
Edge Ports, associated to Traffic descriptor
and Traffic classifier
EVC EVC EVC
Ethernet
Segments
Ethernet
Segments
Ethernet
Segments
Ethernet Service
Customer
Customer
Service
Segment
EVC
VC LSP
LSP Tunnel
Transport
3JK Issue 1.00
3 3 9
Customer definition
A Customer is the owner of one or more Equipment
and is the final user of the Ethernet services defined
across the boundaries of the managed network
A contract is established between :
a Customer and
an Operator
to define an Ethernet Service
Customer Operator
Ethernet
Service
Customer
Service
Segment
EVC
VC LSP
LSP Tunnel
Transport
3JK Issue 1.00
3 3 10
Ethernet Service definition
An Ethernet Service defines the service offered by a
network operator to its customer, in order to
formalise network connection (EVC) satisfying a
specific telecommunication requirements
An Ethernet Service is implemented :
Directly on a TDM or WDM Network layer
On a MPLS/T-MPLS intermediate Network layer
Directly over a cable
An Ethernet Service can use a combination of these
Network layers
Customer
Service
Segment
EVC
VC LSP
LSP Tunnel
Transport
3JK Issue 1.00
3 3 11
Ethernet Virtual Connection (EVC) definition
An Ethernet Virtual Connection (EVC) is an association of
two or more Ethernet End points (UNI)
EVC has :
A specified Service Type, which define the specific topology supported:
Point-to Point
Rooted MultiPoint
Any to Any
A specified Ethernet packet forwarding rule :
Unicast
Multicast
In Connection-oriented cases, an EVC contains a specific
set of Unidirectional Ethernet Segments; while in the
Connection-less cases it is the association of 2 or more EVC
Terminations belonging to the same bridge domain
Customer
Service
Segment
EVC
VC LSP
LSP Tunnel
Transport
3JK Issue 1.00
3 3 12
Ethernet Segment definition
An Ethernet Segment is an unidirectional connection
between two Ethernet Edge physical ports,
associated to :
Quality of Service QoS :
Guaranteed
Best Effort
Regulated
Bandwidth
Traffic descriptor containing QoS information
Traffic classifier containing forwarding rule information
Color Profile, (when required)
Customer
Service
Segment
EVC
VC LSP
LSP Tunnel
Transport
3JK Issue 1.00
3 3 13
Telecommunication Network overview
OMSN - A OMSN - Z OMSN - B
Transport
Link
Transport
Link
Ethernet
Edge
Port
Ethernet
Edge
Port
Ethernet
Edge
Port
Ethernet
Edge
Port
VLAN - A VLAN - B
A B
Z1
Segment A Z1
Z2
Segment Z2 B
Segment Z1 A Segment B Z2
Ethernet Service = Server Z VLANs - A & B over a Point to Point topology
3JK Issue 1.00
3 3 14
Procedure to configure a Conn-Oriented Service
The following procedure describes all the steps necessary to create a
Connection Oriented Service:
1. Create a Customer (see Customer management session)
2. Create an Ethernet Service (see Ethernet Service management
session)
3. Create a Connection Oriented EVC (see Ethernet Virtual
Connection management)
4. Eventually Add Terminations to the EVC (see Ethernet Virtual
Connection management)
5. Create an Ethernet segment (see Ethernet Segment management)
3JK Issue 1.00
3 3 15
Procedure to configure a Conn-Oriented Service [cont.]
6. Associate a Classifier (see Ethernet Segment management)
7. Add Constraints (see Ethernet Segment management)
8. Allocate and Implement the Service (see Ethernet Segment life
cycle)
3JK Issue 1.00
3 3 16
Blank Page
3JK Issue 1.00
3 3 17
2 Customer management
3JK Issue 1.00
3 3 18
Customer list
To display the Customer List, from the MS_GUI:
Search Packet Services Customers
Customer
Service
Segment
EVC
VC LSP
LSP Tunnel
Transport
3JK Issue 1.00
3 3 19
Customer creation
To create a new Customer:
Create Customer
or
1) Display the Customer list
2) Actions Create Customer
To Create a customer:
Enter a User label
Enter a Address (optional)
Enter a Company (optional)
3JK Issue 1.00
3 3 20
Customer properties, modification and deletion
To get the Customer Properties:
1) Select a Customer in list
2) Actions ( or right mouse button) Properties
To modify the Customer Parameters:
2) Actions ( or right mouse button) Modify
To delete an Customer :
2) Actions Customer Delete
N.B: A Customer can be deleted if no more Service are related to.
3JK Issue 1.00
3 3 21
3 Ethernet Service management
3JK Issue 1.00
3 3 22
Ethernet Service list
To display the Ethernet Servicer List, from the
MS_GUI:
Search Packet Services Services
Customer
Service
Segment
EVC
VC LSP
LSP Tunnel
Transport
Service State is set to In Service when all associated EVCs are In Service
3JK Issue 1.00
3 3 23
Ethernet Service creation
Condition to be able to create an
Ethernet Service :
At least, one Customer must be
created
(Default Customer can be
used)
To create an Ethernet Service:
Create Ethernet Service
To Create an Ethernet Service:
Enter a User label
Select a Customer (this field is automatically filled if the window is requested from the Customer List)
Enter a Reference SLA (optional). Any string is possible
3JK Issue 1.00
3 3 24
Ethernet Service properties, modification and deletion
To get the Service Properties:
1) Select a Service in list
To modify the Service Parameters:
To delete a Service :
2) Actions Service Delete
N.B: A Service can be deleted if no more EVC are related to.
3JK Issue 1.00
3 3 25
4 Ethernet Service type
3JK Issue 1.00
3 3 26
Definition
Different types of Ethernet Services are defined :
EVPL Ethernet Virtual Private Line :
Point-to-Point communication between 2 Edge equipment of the same Customer; it is
possible to define a service without restriction. It is a Virtual Service
EPTL Ethernet Private Transparent Line :
Point-to-Point communication between 2 Edge equipment in a transparent mode: it is a
Private Service
EPL Ethernet Private Line :
A Point-to-point communication between 2 edge equipment using shared bandwidth: it is a
Private Service
EVPLAN Ethernet Virtual Private LAN :
It allows any edge node to send/receive information to/from several other edges nodes; it is
possible to define a service without restriction. It is a Virtual Service
HSI High Speed Internet :
It is a Rooted-Multipoint connection, planned for Internet traffic, that allows connecting a
main site with some remote sites belong to one customer (back-hauling) and viceversa
BTV Broadcast TV:
It is a Rooted-Multipoint connection, planned for broadcasting TV, that allows connecting a
main site with many remote sites or one remote site with a main site
BROADCAST :
It is a Rooted-Multipoint connection, planned for broadcasting TV, that allows connecting a
main sites with many remote sites
3JK Issue 1.00
3 3 27
Definition [cont.]
Services Type and EVCs connection type relationships
EVPL
EPTL
EPL
EVC Point to Point
(support Unicast
traffics)
EVPLAN
EVC Any to Any
(support Unicast
traffics)
BTV
Broadcast
EVC Rooted Multi-
Points (support
Multicast traffics)
HSI
EVC Rooted Multi-
Points (support
Unicast traffics)
The Ethernet services are based on EVC: the service is like a container of one or more EVCs, a specific
type of service introduces some restriction on the EVC types to be used for that service.
An EVC is composed of a set of unidirectional point to point connections called Ethernet segment .
1350OMS PKT subsystem manages three types of EVC:
Point to Point
Rooted Multipoint (Point to Multi-point): an EVC termination has the role of root and the other
the role of leaf
Any to Any (Multi-point to Multi-point): it is a bus like topology in which each EVC termination can
communicate with the others
3JK Issue 1.00
3 3 28
EVPL/EPTL/EPL service
Point to point_EVC
CE
A
CE
B
Ethernet
Customer
Edge
Ethernet
Provider
Edge
Server transport layer: SDH / DWDM / RPR or MPLS
OMSN supporting
Ethernet service
and T- MPLS
OMSN supporting
Ethernet Service
An EPL (Ethernet Private Line) is a point to point connection between two CEs :
Support Unicast Service
Private UNIs must be used (see Resource reservation for details)
Only one EVC is allowed with this type of Service
It can be based on connection-oriented network or on a connection-less (Provider) network or on a
T-MPLS network
An EPTL (Ethernet Private Transparent Line) is a point to point connection between two CEs:
Transparent Service (no Bandwidth Profile)
Private UNIs and Private Links must be used (see Resource reservation for details)
Only one EVC is allowed with this type of Service
It can be only based on connection-oriented network
An EVPL (Ethernet Virtual Private Line) is a point to point connection between two CEs :
All possible resource sharing combinations are permitted (see Resource reservation for
details)
One or more EVC are allowed with this type of Service
It can be based on connection-oriented network or on a connection-less (Provider/Virtual) network
or on T-MPLS network
3JK Issue 1.00
3 3 29
EVPLAN service
Full Meshed EVPLAN
OMSN supporting
Ethernet Service
OMSN supporting
Ethernet service
and T- MPLS
CE
A3
CE
A1
CE
A0
CE
F
CE
C
CE
B
CE
D
CE
E
CE
A2
Server transport layer: SDH / DWDM / RPR or MPLS
A number of any single CE sites are connected to each other via Layer 2 switches.
An EVPLAN (Ethernet Virtual Private LAN) is a Multi-point to Multi-point connection :
All possible resource sharing combinations are permitted (see Resource reservation for details)
One or more EVC are allowed whit this type of Service
It can be based on connection-oriented network or on a connection-less (Provider/Virtual) network or
on T-MPLS network
3JK Issue 1.00
3 3 30
HSI/BTV/BROADCAST service
HUB & Spoke
CE
A
CE
F
CE
C
CE
B
CE
D
CE
E
Server transport layer: SDH / DWDM / RPR or MPLS/T-MPLS
Main
Site
ISP
OMSN supporting
Ethernet service
and T- MPLS
OMSN supporting
Ethernet Service
An HSI (High Speed Internet) is a Rooted-Multi-point connection, intended as a set of bidirectional
connection between the main site and any remote site:
Full resource sharing can be used (see Resource reservation for details)
It could be based on connection-oriented network or on a connection-less (Provider/Virtual) network
or on T-MPLS network, but due to the restriction of NE, at the moment connection-less mode can
not guarantee isolation between remote sites
A BTV (Broadcast TV) is a Rooted-Multi-point connection, intended as a broadcast forwarding from the
main site towards the remote sites, with the possibility of a backward channel (unicast) from any
remote sites towards the root
Support Multicast Service
Full resource sharing can be used (see Resource reservation for details)
It can be based both on connection-oriented network or on a connection-less (Provider) network; on
connection-less mode, IGMP can be used to enable or disable forwarding to some specific host
A BROADCAST is a Rooted-Multi-point connection, intended as a broadcast forwarding from the main
site towards the remote sites
It is based on connection-oriented mode, using SDH broadcast network
Support Multicast service (broadcasting is realized by the SDH network)
Private UNIs or Full resource sharing can be used (see Resource reservation for details)
3JK Issue 1.00
3 3 31
Resource Reservation concept
The Resource Sharing attribute at EVC level can assume following
value:
Private UNI : the EVC service must use Private UNI, i.e. UNI uniquely used
by that EVC Service
Private Link : the EVC service must use Private Links, i.e. Transport Links
uniquely used by that EVC Service
Private UNI and LINK : the EVC Service must use Private UNI and Private
Links, i.e. chosen Transport Links and UNIs are uniquely used by that EVC
Service
Full : the EVC Service can use every kind of resource without any restriction
A
Transport Link
UNI UNI
A
3JK Issue 1.00
3 3 32
Resource Reservation combination

ETS ETS Broadcast
ETS
Provider Bridge
T-MPLS
BTV
ETS
Bridge
T-MPLS
HSI
ETS
Bridge
T-MPLS
ETS
Bridge
T-MPLS
ETS
Bridge
T-MPLS
ETS
Bridge
T-MPLS
EVPLAN
ETS
Provider Bridge
T-MPLS
EPL
ETS
EPTL
ETS
Bridge
T-MPLS
ETS
Bridge
T-MPLS
ETS
Bridge
T-MPLS
ETS
Bridge
T-MPLS
EVPL
Private UNI
and Link
Private
Link
Private UNI Full
Resource Sharing
S
e
r
v
i
c
e

T
y
p
e
The table above reports the possible chooses of Resource Sharing respect to the Service Type and respect
to crossed technological domain
3JK Issue 1.00
3 3 33
5 Ethernet Virtual Connection
management
3JK Issue 1.00
3 3 34
5 Ethernet Virtual Connection management
Definition
Ethernet Virtual Connection EVC specifies the
connectivity between :
Two or more Ethernet End points (UNI) of the same
Ethernet Network
An EVC have a specified topology :
Point-to-Point (PtoP) :
Connection between 2 points bi-directional / unicast
traffic only
Rooted-to-MultiPoint (PtoMP) :
Connection between 1 or more points (Root) and each
of the other points (Leaf) /if unicast traffic then bi-
directional / for multicast traffic, unidirectional
Any to Any (MPtoMP) :
Connection between 2 or more points / unicast traffic
bi-directional only
Customer
Service
Segment
EVC
VC LSP
LSP Tunnel
Transport
3JK Issue 1.00
3 3 35
Definition [cont.]
EVCs and Ethernet End Points relationships
In PtoP (green),
bi-directional topology :
B,E=Peer (Root+Leaf)
In PtoMP (red),
unidir. / bidir. topology
A=Root
B,C,D=Leaf
In MPtoMP (blue),
bidirectional topology
C,D,E= Peer (Root+Leaf)
A
B
C
D
E
Peer
Root
Peer
Leaf
Leaf
Leaf
Peer
Peer
Peer
PtoMP
PtoP
MPtoMP
Every EVC is terminated by Edge port.
The same Edge Port can be used by different EVCs, or not, according to the Resource Sharing attribute
Depending on the EVC topology, every Edge port used by a given EVC will assume a specific Role:
in PtoP topology, the two port will assume the Peer role;
in Rooted Multipoint topology, one port will assume the Root role while all the others will assume
the Leaf role;
in Any to Any topology, all ports will assume the Peer role;
3JK Issue 1.00
3 3 36
Connection-Oriented EVC list
To display the Connection Oriented EVC List, from the MS_GUI:
Search Packet Services Connection Oriented ETS EVCs
3JK Issue 1.00
3 3 37
Connection Oriented EVC creation: Specific tab
To create an EVC:
1) Actions Packet
Services Connection
Oriented Create EVC
or
1) Select one EVC in the list
2) Action ETS EVC
Create EVC
To create a new EVC:
In the Specific part:
enter an EVC User Label
select a Service Type from the list
Ethernet Service: choose an Ethernet service by clicking in the box. This field is automatically filled if
the window is requested from the Service List
Domain: choose Domain by clicking in the box: only Connection-oriented domains are listed
Topology (Point to point, Rooted Multipoint, Any to any) is automatically filled, as consequence of
chosen Service
Traffic Type (Unicast, Multicast) is automatically filled, as consequence of Type field
select a Resource sharing attribute, if not already assigned
3JK Issue 1.00
3 3 38
Connection Oriented EVC creation: Detail tab
Details panel:
In the Details part:
Directionality: choose Unidirectional or Bidirectional, if not automatically filled;
Port Service Type, Other or Port to Port: configure this attribute (Port to Port) only for the NE
that support it; in such case the crossed NNI port must be configured as Port-to-Port and must be
not used by an other service, and UNI ports must be not used by an other service
Failure Propagatiion (meaningful only for EPTL Service): enable or disable the CSF insertion and
configure the Ethernet Port for laser shutdown
Select a VLAN Type, or choose True to set the standard (8100)
Unicast/Multicast/Broadcast Service Frame Delivery: defines the policies to be applied to the
incoming Unicast/Multicast/Broadcast frames on the EVC:
Deliver Conditionally = MAC learning based
Deliver Unconditionally = VLAN based
3JK Issue 1.00
3 3 39
Connection Oriented EVC creation: PM tab
PM panel:
Set True to enable PM.
(Refer to specific session
for details)
3JK Issue 1.00
3 3 40
Connection Oriented EVC creation: Miscellaneus tab
Miscellaneus panel:
Click on Next to continue
In the Miscellaneous part:
select a Service Level (Premium, Gold, Silver, Bronze) (N.B. no effect on real traffic)
C-VLAN Preservation: when True selected, it ensure that each packet exiting the EVC (at some egress
UNI) has the same VLAN id information that it had when it entered the EVC (at some ingress UNI).
C-Vlan Cos Preservation: when True selected, it ensure that each packet exiting the EVC (at some
egress UNI) has the same Priority Bits information that it had when it entered the EVC (at some ingress
UNI).
select a NAD value by clicking in the box
External mark: (optional) it can be used to identify external systems having some relation with the EVC
(for example an ownership.
Comment & Text: (optional)
3JK Issue 1.00
3 3 41
Termination selection for Point to Point service
Choose NE and Edge
ports as terminations
For Point to Point topology a window to insert
two edge ports is open
N.B: Edge port are listed if previously assigned to a Connection Oriented domain
3JK Issue 1.00
3 3 42
Termination selection for Multi-Point service
Choose NE and Edge
ports as terminations
For Rooted Multipoint or Any to Any topology a
window to insert multiple edge ports is open
The operator must select the physical edge port and assign a termination role (Peer or Root or
Leaf).
3JK Issue 1.00
3 3 43
Connection Oriented EVC creation: Segment creation
Select True and fill
consequentely to create
Ethernet segments with
current wizard.
Go to specific chapter 6 Ethernet Segment
management to complete the procedure
By setting Create Ethernet Segment = True two segments, one for each direction, are automatically
created, with label <EVC User label>_esg_i
Required parameters:
choose a Traffic Descriptor. IN CASE OF Regulated CoS, the operator can assign a Color Profile in
order to configure the policy mode as Color Aware. If the Color Profile field is left empty, the Color
Blind mode is automatically set.
select the Classification Mode (Priority, DSCP)
3JK Issue 1.00
3 3 44
EVC properties, modification and deletion
To get the EVC Properties:
1) Select an EVC in list
To modify the EVC Parameters:
To delete an EVC :
2) Actions ETS EVC Delete
N.B: An EVC can be deleted if the provisioning state is Defined
3JK Issue 1.00
3 3 45
EVC Configuration : Traffic descriptor assignment
The configuration of an EVC consists
in associating a Traffic Descriptor to
the EVC
To configure an EVC :
1) Select an EVC in the list
2) Actions ETS EVC Configure EVC
3) Select a Traffic Descriptor
It is possible to dynamically change
(increment/decrement) the
bandwidth on active (i.e.
implemented) Ethernet connectivity.
(See notes below for details)
Changing a Traffic Descriptor on implemented or allocated EVC level, the bandwidth change is
propagated to all contained Ethernet segments.
The bandwidth change is only admitted in the scope of the same QoS (e.g. change from BE to Guaranteed
is not allowed as well as other mixed possibilities).
3JK Issue 1.00
3 3 46
EVC Commission / Decommission
To commission the EVC:
1) Select one or several implemented EVC in the list
2) Actions ETS EVC Commission
To decommission the EVC:
1) Select one or several commissioned EVC in the list
2) Actions ETS EVC Decommission
Commissioning is an operative operation, has no effect on Nes.
It allows to notify the availability of the Service to be used to carry Ethernet Traffic
After commission, the Service State of the EVC change from Not in service to In service
3JK Issue 1.00
3 3 47
EVC Terminations list
The EVC Termination List window presents all the termination of the
selected EVC and their attribute
To display the EVC Terminations list:
1) Select one EVC in the list:
2) Search ETS EVC EVC Terminations
3JK Issue 1.00
3 3 48
Add EVC Termination
To add a new Termination in
the EVC:
1) Select one EVC in the list:
2) Actions ETS EVC Add
EVC Termination
Adding a new EVC Termination is possible if compatible with the Ethernet Service Topology
The operator must select the physical edge port and assign a termination role (Peer or Root or
Leaf).
3JK Issue 1.00
3 3 49
EVC Termination properties and deletion
To get the EVC Terminations properties:
1) Select an EVC Termination in the list
To delete an EVC Termination:
1) Select an EVC Termination in thelist
2) Actions EVC Termination Delete
N.B: An EVC Termination can be deleted if no segment are associated.
3JK Issue 1.00
3 3 50
Blank Page
3JK Issue 1.00
3 3 51
6 Ethernet Segment management
3JK Issue 1.00
3 3 52
Ethernet Segment definition
An Ethernet Segment is an Unidirectional connection
between two Ethernet Edge ports.
Enter in and Exit from traffic ports
Associated to:
Bandwidth
Traffic descriptor containing
QoS information
Traffic Classifier
containing forwarding rule
information
Color Profile, in case of Color
Aware Policy mode
Ethernet
segments
T
r
a
n
s
p
o
r
t

L
i
n
k
Guaranteed
Regulated
Best Effort
Ethernet
Port
Ethernet Segment
Ethernet
Port
Customer
Service
Segment
EVC
VC LSP
LSP Tunnel
Transport
Every Ethernet segment is terminated by means of two Ethernet Edge ports which represent the
terminations in the Provider Edges (where the Ethernet traffic enter in/exit from the managed
network.
An Ethernet Edge physical port can support many different Ethernet traffics
3JK Issue 1.00
3 3 53
Ethernet Segment list
To display the Ethernet Segment List, from the MS_GUI:
Search Packet Services Connection Oriented Ethernet
Segments
3JK Issue 1.00
3 3 54
Ethernet Segment creation: General
To create an Ethernet Segment:
Connection Oriented
Create Ethernet Segment
or
2) Action ETS EVC Create
Ethernet Segment
Select the classification
mode (Priority / DSCP)
Set the related options
The Edge Physical Port can be in use by another Ethernet segment provided that it belongs to the same
Ethernet service.
To create an Ethernet Segment:
enter a segment User Label
enter the EVC the Ethernet Segment belongs to. (This field is automatically filled if the window is
requested from the EVC List)
choose the EVC Terminations on side A and on side Z.
choose a Traffic Descriptor. IN CASE OF Regulated CoS, a Policy mode Color Aware can be choose
select a Policy mode (Color Blind, Color Aware, Disabled)
if Color Aware is chosen, select a Color Profile
The direction in the traffic delivering is from A-EvcPort_label to Z-EvcPort_label
3JK Issue 1.00
3 3 55
Vlan Push/Pop at UNI management
The Vlan Push/Pop at UNI interface is provided for inter-working
purposes, this meaning that only the following operations can be
performed:
VLAN Push on the edge port of the Z-end of an Ethernet Segment
VLAN Pop on the edge port of the A-end of an Ethernet Segment
VLAN Push on an interface of a NE that, in respect of the direction of the
Ethernet Segment, is followed by an ENE
VLAN Pop on an interface of a NE that, in respect of the direction of the
Ethernet Segment, is preceded by an ENE
VLAN Pop
VLAN Push
Eth. Segment
Eth. Segment
Z
A
Z
A
A
Z
Z
A
3JK Issue 1.00
3 3 56
Vlan Pop configuration (A-End)
To pop a VLAN on a Ethernet
Segment:
1) During Segment Creation,
select Pop window
2) insert one or more Classifier
that will be applied on the
subsequent NEs
Click here to add a
Classifier
VLAN Pop
Classifier Classifier
To enable the Pop operation, the operator must :
- specify, by choosing in the list, a list of Traffic Classifier that will be used by the subsequent NEs
after the Pop execution
3JK Issue 1.00
3 3 57
Vlan Push configuration (Z-End)
To Push a VLAN on a Ethernet
Segment:
1) During Segment creation,
select Push window
2) Enter required parameters
Set False to enable
Vlan Push
To enable the Push operation, the operator must set clear all fields = False;
then
- enter the VLAN to be pushed
- select the Policy Mode (Color Blind, Color Aware)
- if Policy Mode is Color Blind, choose the Green Priority value (priority of all the packets after the
push
- if Policy Mode is color Aware, choose Green Priority and Yellow Priority values for all green and
yellow outgoing packets
3JK Issue 1.00
3 3 58
Ethernet Segment properties and extremities
To get the Ethernet Segment properties:
1) Select an Ethernet Segment in list
To get the Ethernet Segment extremities:
2) Actions Ethernet Segment Extremities
3JK Issue 1.00
3 3 59
Ethernet Segment modification and deletion
To modify the Ethernet Segment parameters:
2) Actions Modify
To delete an Ethernet Segment :
2) Actions Ethernet Segment Delete
In order to modify Segment attributes or to delete the segment, the Provisioning State must be Defined
or Allocated
3JK Issue 1.00
3 3 60
Associate/Disassociate a Traffic Classifier
To associate a Traffic Classifier to an Ethernet Segment: :
1) Select an Ethernet Segment in the list
2) Actions Ethernet Segment Associate Traffic Classifier
To disassociate a Traffic Classifier from an Ethernet Segment:
1) Select an Ethernet Segment in
the list
2) Actions Ethernet Segment Disassociate Traffic Classifier
Click here to add a
Classifier
Click here to remove
a Classifier
The Ethernet segment provisioning state can be Defined, Allocated or Implemented
More than one Traffic Classifier could be associated to an Ethernet segment
3JK Issue 1.00
3 3 61
Adding Constraints to an Ethernet Segment
Adding a constraint to an Ethernet Segment defines the route
constraints for the Segment and gives the possibility to extend to
Connection-oriented domain the Vlan Push/Pop mechanism:
The Vlan Push/Pop at NNI is provided in order to encapsulate untagged
or C-Vlan Tagged Ethernet frames, with a Provider Vlan Tag (having the
only meaning to route the traffic in segregated way, for example when
untagged signals must be transported through the same transport link)
Eth Seg#2
Eth Seg#1
VLAN Push
VLAN Pop
The function consists in adding an allocation constraint to an Ethernet segment
To add a constraint, the Ethernet segment Provisioning state must be Defined
3JK Issue 1.00
3 3 62
Adding Constraints to an Eth. Segment
To add a constraint to an Ethernet
Segment:
1) Select an Ethernet Segment in the
list
2) Actions Ethernet Segment
Add Constraint to an Ethernet
Segment
3) Select a Transport Link
Click here to display
Transport Link list
Use this option to add VLAN
Pop/Push action on NNI
port of the Transport Link
3JK Issue 1.00
3 3 63
Adding Vlan Pop/Vlan Push on an Ethernet Segment
Set False to enable
Vlan Push
In case of Vlan Pop
management:
click here to display Traffic
Classifier list
To enable the Pop operation, the operator must :
- specify a list of Traffic Classifier that will be applied on the subsequent NEs after the pop
execution
To enable the Push operation, the operator must :
- set False in the Clear All fields
- enter the Vlan to be pushed
- if Policy Mode is Color Blind, choose the Green Priority value (priority of all the packets after
the push
- if Policy Mode is color Aware, choose Green Priority and Yellow Priority values for all green
and yellow outgoing packets
3JK Issue 1.00
3 3 64
Ethernet Segment Constraints list
To display the Ethernet Segment Constraints list :
1) Select an Ethernet Segment in the list
2) Search Ethernet Segment Constraints
3JK Issue 1.00
3 3 65
Ethernet Segment Constraint modification
Constraint modification allows, for a Defined Ethernet Segment, to apply a
VLAN POP and PUSH policy on NNI ports belonging to the Transport Link:
1) Select an Ethernet Segment Constraint in the list
2) Actions Modify
3) Configure accordingly
3JK Issue 1.00
3 3 66
Ethernet Segment Constraints properties and deletion
To get the Ethernet Segment Constraint properties:
1) Select a Constraint in list
To delete an Ethernet Segment Constraint:
1) Select a Constraint in list
2) Actions Constraint Pkt_POP_deleteConstraint_label
To be able to delete a given constraint, the related Ethernet segment must be in Defined provisioning
state.
3JK Issue 1.00
3 3 67
Ethernet Segment Configuration : Traffic Descriptor
To configure an Ethernet Segment :
1) Select an Ethernet segment in the list
2) Actions Ethernet Segment Configure
Ethernet Segment
3) Select a Traffic Descriptor (see Notes for
details)
The configuration of an Ethernet Segment consists in assigning a
Traffic Descriptor to the Segment, when the segment provisioning
state is Implemented or Partially Implemented
Click here to display the
available TD list
N.B: The bandwidth change is only admitted in the scope of the same QoS (e.g. change from BE to
Guaranteed is not allowed as well as other mixed possibilities).
3JK Issue 1.00
3 3 68
Exercise
Create a set of EVC with different Service types
Add a set of Ethernet edge ports to EVCs, where possible, with
different Edge port roles
Create a set of Ethernet segments having different QoS
Create an Ethernet segment with VLAN POP at UNI interface
Delete some Ethernet segments
Add a Constraint to an Ethernet segment with VLAN PUSH at NNI
interface
3JK Issue 1.00
3 3 69
7 Ethernet segment life cycle
3JK Issue 1.00
3 3 70
7 Ethernet Segment life cycle
Definition
Ethernet Segment life cycle :
Defined state
Associate Traffic
classifier
Associate
Constraints
Allocate
Implement
Customer
Service
Segment
EVC
VC LSP
LSP Tunnel
Transport
The allocation of the Ethernet segment will find a route between the related edge ports.
The existing constraints (if any) will be taken into account at this moment.
The provisioning state of the related EVC is updated in allocated or Partially Allocated.
The bandwidth load parameters and the usage state of all the involved transport links is updated
accordingly after the allocation / de-allocation.
The implementation establishes an Ethernet flow over an Ethernet segment creating relevant cross-
connections into the matrixes of the equipment.
The Ethernet segment provisioning state must be Allocated or at least Partially Implemented.
The provisioning state of the related EVC is updated in Implemented or Partially Implemented.
3JK Issue 1.00
3 3 71
7 Ethernet Segment life cycle
Ethernet Segment Allocation and Implementation
To Allocate/Deallocate the Ethernet Segments :
1) Select one or several Ethernet Segments in the list
2) Actions Ethernet Segment Allocate/Deallocate
To Implement/Deimplement the Ethernet Segments :
1) Select one or several Ethernet Segments in the list
2) Actions Ethernet Segment Implement/Deimplement
The Allocation consists in finding a route between the end physical ports of the Ethernet segment.
To be able to allocate an Ethernet segment:
- the Ethernet segment Provisioning state must be Defined
- a list of constraint containing all transport links used is associated to the Ethernet segment
- traffic profile, traffic descriptor and traffic classifier must be associated to the Ethernet segment.
The 1350OMS PKT check the validation of the transport links to be used in term of traffic type,
bandwidth and continuity of the chosen transport links.
The Implementation activates an Ethernet flow over an Ethernet segment
3JK Issue 1.00
3 3 72
Exercise n.1
Create an Ethernet Services, connecting Customer A, having the
following characteristic :
Type of service: EPL
Bidirectional
Policy Mode : Color Blind
QoS: Guaranteed 2 (PIR=CIR=500K; CBS=PBS=1574)
Classifier: VLANid = 10; Priority = 5
Link over SDH
A A
3JK Issue 1.00
3 3 73
Exercise n.2
Create an Ethernet Services for two customers, A and B, with the following
characteristic :
Private UNI, shared Transport link
Customer A: untagged Eth. Frame; QoS: Guaranteed (PIR=500K, PBS=1574);
Customer B: untagged Eth. Frame; QoS: Best Effort (PIR=200K, PBS=1600);
Reminder: use VLAN PUSH/POP at NNI interface to segregate traffic
B B
A A
Link over SDH
Customer
A B
3JK Issue 1.00
3 3 74
End of Module
3JK Issue 1.00
34
Module 4
Bridge Provisioning
3JK Issue 1.00
Section 3
System Operation
1350OMS
3JK Issue 1.00
System Operation Bridge Provisioning
3 4 2
Blank Page
Document History
3JK Issue 1.00
3 4 3
Module Objectives
Manage the Bridge network provisioning
3JK Issue 1.00
3 4 4
3JK Issue 1.00
3 4 5
Table of Contents
Page
1 Bridge Network concept 7
2 Network Constructor and Bridge Infrastructure management 17
3 Ethernet service management 29
4 Connection-Less Ethernet Virtual Connection 35
5 Spanning Tree Instance management 61
6 Ethernet Virtual Connection life cycle 63
3JK Issue 1.00
3 4 6
Page
3JK Issue 1.00
3 4 7
1 Bridge Network concept
3JK Issue 1.00
3 4 8
1 Bridge network concept
Global definition
Bridge network management is based on the following
functional areas:
1. Network constructor
Domain management
NE, Edge Port management
2. Bridge Infrastructure management
Transport Link assignment
3. Bridge traffic management (EVC)
EVC association to a bridge infrastructure
EVC Termination addition
Manual or automatic VLAN distribution inside Packet resources
STP parameter set-up
QoS management
3JK Issue 1.00
3 4 9
Network Constructor
For Connection-Less Service , the Network Construction consists of the
topology definition with the following main elements:
Domain
Nes and ENEs
Ethernet physical ports
Transport links
ENE
NNI
Interface
UNI
Interface
UNI
Interface
UNI
Interface
NNI
Interface
Bridge Domain
3JK Issue 1.00
3 4 10
Bridge Infrastructure management
The Transport Link assignment to the specific Bridge Domain is in the
scope of bridge infrastructure management.
The assignment of the Transport Link to a Bridge Domain forces the
extremities to be configured as ETB
ENE
Provider Bridge
Domain
ETB
ETS_P
ETB
ETS_P
ETB
ETB
3JK Issue 1.00
3 4 11
Bridge Traffic management
Bridge traffic management deals with set-up of data traffic toward the
customer edge, STP tuning and VLAN distribution inside and at the edge
of the domain.
One function of bridge traffic management is the EVC association to
bridge infrastructure and EVC Termination addition:
A set of edge ports, assigned to a bridge domain, are included in the EVC.
EVC association to domain is automatic when the edge ports are specified at
EVC creation-time and when the Transport Link are assigned to the same
domain: the terminations of one EVC correspond to edge ports belonging to
the same bridge domain.
In case of Virtual or Provider domain, one EVC is optionally characterized by
one VLAN bundle, I.e. a group of VLAN
3JK Issue 1.00
3 4 12
OMSN - A
ISA - A
OMSN - B
ISA - B
Transport
Link
Ethernet
Edge
Port
Ethernet
Edge
Port
VLAN - A VLAN - B
A B
L2 switching
layer
Bridge Network overview (MAC and Virtual)
L2 switching
layer
In Connection-less case, no Ethernet Segment are used; the route between two end termination depends
on the current active topology;
the usage of traffic descriptor/classifier is allowed only with Provider bridge.
3JK Issue 1.00
3 4 13
Bridge Network overview (Provider)
OMSN
ISA
Ethernet
Edge
Port
Transport
Link
VLAN - A
A
S-Vlan
PUSH
Virtual Port
Classification,
Policing,
Metering
L2 switching
layer
In case of Provider Bridge termination, one Traffic descriptor, one Color Profile and many Traffic
Classifiers may be optionally associated to each EVC Termination.
The S-VLAN (pre-IEEE 802.1ad) allows the service provider to stack another VLAN tag on the frames
coming on the UNI such that traffic from different customers is put on different S-VID and thus
segregated.
3JK Issue 1.00
3 4 14
Procedure to configure a Bridge Network
The following procedure describes all the steps necessary to create a
Bridge network:
1. Create a Bridge Domain (see Network Elements and Node
managements session S2-M2)
2. Assign Nes, or specific physical Ports, to the Bridge Domain (see
Network Elements and Node managements session S2-M2)
3. Assign Transport Link to the Bridge Domain (See Transport link
management S3-M1)
4. Create a Customer (see Customer management session S3-M4)
5. Create an Ethernet Service (see Ethernet Service management
session)
3JK Issue 1.00
3 4 15
Procedure to configure a Bridge Network
6. Create a Connection Less EVC (see Ethernet Virtual Connection
management session )
7. Configure Ingress Flow and Egress Flow for the Terminations (see
Ethernet Virtual Connection management session)
8. Eventually Add Terminations to the EVC (see Ethernet Virtual
Connection management session)
9. Create Ingress Flow and Egress Flow for the added Terminations
(see Ethernet Virtual Connection management session)
10.Allocate, Implement and Commission the Connection-Less EVC
(see Ethernet Virtual Connection life cycle session)
3JK Issue 1.00
3 4 16
Blank Page
3JK Issue 1.00
3 4 17
2 Network Constructor and Bridge
Infrastructure management
3JK Issue 1.00
3 4 18
2 Network Constructor and Bridge infrastructure management
Ethernet physical port assignment
The assignment of the Ethernet Physical port to a Domain forces the
port to be configured as ETS_P (Provider) or ETB (Virtual) and makes
the port available, as Bridge Edge Port, in the Service environment
1) Select a Physical port in the list
2) Actions Physical Ports Assign Resources to Domain
3) Select the target Domain
4) Click on Ok
The port will set its Client Type attribute as ETS_P or ETB
Even if the Port has been previously assigned to a domain, the operator can change it by assigning to a
different domain, on condition that the port is not busy
3JK Issue 1.00
3 4 19
Bridge Edge Ports list
The Bridge Edge Ports list display all the UNI or IWI ports defined in a
bridge domain, that can be associated to an EVC.
To display the Bridge Edge Ports List, from the MS_GUI:
Search Packet Services Connection Less Bridge Edge Ports
3JK Issue 1.00
3 4 20
Edge Port configuration
To configure an Edge Port:
1) From Bridge Edge Port list: select a
Port
2) Actions Bridge Edge Port
Configure Edge Port
This function permits to configure VLAN parameters of Bridge Edge
port:
The Edge port attributes that can be modified are depending on the specific domain where the port
belong to; (I.e in case of Provider bridge only VLAN Type can be set)
According to the boards, in the General window, can be set:
Acceptable frame type (All/Only VLAN tagged)
PVID (Port VLAN Identifier)
Enable/Disable Ingress filtering:
when enabled (True) it discards all the frames having VLANID that do not have this port on their
relevant MemberSet.
When Disabled (False) it accepts all incoming Ethernet frames.
Define a Priority bit mapping, for Regenerating function: type in sequence the Priority to assign for
each incoming value, from 7 to 0
Default User Priority: that is assigned to the Untagged frames (0-7)
VLAN type (for Provider bridge only) : click on the box to display available VLAN Type and choose one
or set True in the Set Standard VLAN Type field (for VLAN Type = 8100)
3JK Issue 1.00
3 4 21
Edge Port activation/deactivation
To activate (deactivate) an Edge Port:
1) From Bridge Edge Port list: select a Port
2) Actions Bridge Edge Port Activate (Deactivate)
The Activation State Attribute is set to UP (DOWN)
This function activate (deactivate) edge port (set up/down) even if
not used in a Service.
3JK Issue 1.00
3 4 22
Transport Link assignment
The assignment of the Transport Link to a Domain forces the Link to
be configured as ETB and makes it available, as Bridge Transport
Link, in the Service environment:
1) Select a Link over TDM (Cable, .) in the list
2) Actions Link Over TDM (Cable, ) Assign Resources to Domain
3) Select the target Domain
4) Click on Ok
The extremities of the link will set its Client Type attribute as ETB
3JK Issue 1.00
3 4 23
Bridge Transport Links list
The Bridge Transport Links list display all the Transport Links defined
in a bridge domain, that can be associated to a bridge Infrastructure
management.
To display the Bridge Transport Links List, from the MS_GUI:
Search Packet Services Connection Less Bridge Transport
Links
3JK Issue 1.00
3 4 24
Transport Link configuration
To configure a Transport Link:
1) From Bridge Transport Link list:
select a Link
2) Actions Bridge Transport Link
Configure Transport Link
This function permits to configure VLAN parameters of transport link
extremities
According to the boards, can be set:
Acceptable frame type (All/Only VLAN tagged)
PVID (Port VLAN Identifier)
Enable/Disable Ingress filtering:
when enabled (True) it discards all the frames having VLANID that do not have this port on their
relevant MemberSet.
When Disabled (False) it accepts all incoming Ethernet frames.
Define a Priority bit mapping, for Regenerating function: type in sequence the Priority to assign for
each incoming value, from 7 to 0
Default User Priority: that is assigned to the Untagged frames (0-7)
PCP (Priority Code Point) Table profile (for Provider bridge only) : choose an operating mode for the
Interface. (See next slides for details)
VLAN type (for Provider bridge only) : click on the box to display available VLAN Type and choose one
or set True in the Set Standard VLAN Type field (for VLAN Type = 8100)
3JK Issue 1.00
3 4 25
Priority Code Point Table Profile
By PCP Table Profile, on Port basis, the operator can define a way of
mapping each CoS to a specific output queue at the egress port.
The notation 5P3D, 6P2D, 7P1D and 8P0D have the following meaning:
the first number (i.e. 5P) identifies the number of CoS classes
managed for that profile while the second notation (i.e.3D) identifies
how many CoS classes encompass a Dropping Precedence rule (i.e.
classes with Green and Yellow packets)
This operation is possible only in case of Provider Bridge NE, and when the Transport Link termination
Ports play the role of ETB (NNI/IWI)
Only for NEs that support PCP table profile configuration on port basis
N.B: As Container is the default value on Port Basis, mirroring the value defined on Node basis
3JK Issue 1.00
3 4 26
Priority Code Point Table Profile [cont.]
001 (1) 001 (1) 001 (1) Not Supp. Background
000 (0) 000 (0) 000 (0) 001 (1) green
000 (0) yellow
Best Effort
010 (2) 010 (2) 011 (3) green
010 (2) yellow
011 (3) green
010 (2) yellow
Regulated(4)
011 (3) 011 (3) Not Supp. Not Supp. Regulated(3)
100 (4) 101 (5) green
100 (4) yellow
101 (5) green
100 (4) yellow
101 (5) green
100 (4) yellow
Regulated
101 (5) Not Supp. Not Supp. Not Supp. Regulated(1)
110 (6) 110 (6) 110 (6) 110 (6) Guaranteed(2)
111 (7) 111 (7) 111 (7) 111 (7) Guaranteed
8P0D 7P1D 6P2D 5P3D Class
Operation Mode
The table reports the Encoding rules of PHB into PCP bits at the egress port, for the different operation
mode.
3JK Issue 1.00
3 4 27
Transport Link activation/deactivation
To activate (deactivate) the Transport Link extremities:
1) From Transport Link list: select a Port
2) Actions Bridge Transport Link Activate (Deactivate)
The Configuration State Attribute is set to Configured (Partially
Configured)
This function activate (deactivate) the extremities (set up/down) of
a transport link, even if is already assigned to a domain.
3JK Issue 1.00
3 4 28
Transport Link properties and extremities getting
To get the Transport Link Properties :
1) Select a Link in the Bridge Transport Link list
To get the Transport Link Extremities:
1) Select a Link in the Bridge Transport Link list
2) Actions Bridge Transport Link Extremities
Transport Link Properties:
this function consists in easily getting information about a Bridge Transport Link
Transport Link Extremities:
this function consists in easily getting information about extremities of a Bridge Transport Link
3JK Issue 1.00
3 4 29
3 Ethernet service management
3JK Issue 1.00
3 4 30
Ethernet Service list
To display the Ethernet Service List configured in any
Domain, from the MS_GUI:
Search Packet Services Services
Customer
Service
EVC
VC LSP
LSP Tunnel
Transport
3JK Issue 1.00
3 4 31
Ethernet Service creation
To create an Ethernet Service:
Create Ethernet Service
or,
1) Select a Customer in the
Customers list
2) Actions Customer Create
Ethernet Service
Condition to be able to create an Ethernet Service :
At least, one Customer must exist
- Enter :
User Label
Reference SLA (a string); optional
Comment (optional)
- Customer: Click on the box to display available Customer and choose one
3JK Issue 1.00
3 4 32
Ethernet Service properties, modification and deletion
To get the Ethernet Service Properties:
To modify the Ethernet Service Parameters:
To delete an Ethernet Service:
2) Actions Services Delete
3JK Issue 1.00
3 4 33
Exercise
Create a set of Ethernet Services
Display the Ethernet service properties
Delete some Ethernet services
3JK Issue 1.00
3 4 34
Blank Page
3JK Issue 1.00
3 4 35
4 Connection-Less Ethernet Virtual
Connection
3JK Issue 1.00
3 4 36
4 Connection-less Ethernet Virtual Connection
Definitions
Connection-Less EVC specifies the connectivity between a set of edge
ports (EVC Termination) in a specified Bridge Domain
MAC Bridge: in this case there exist only one EVC for the Domain
VIRTUAL / PROVIDER Bridge: many EVC may insist on the same Domain
EVC Termination: it is conceptually associated to:
One Ethernet interface (either local or remote) in case of MAC Bridge
One set of ETB virtual port insisting on the same Ethernet interface in
case of Virtual Bridge: it is the set of ETB virtual ports corresponding to
the C-VLAN of the EVC (there is one ETB virtual port for each C-VLAN)
One ETS_P flow or set of ETS_P flow in case of Provider Bridge: it is the
flow or set of flow referenced by the Traffic Classifier associated with
the C-VLAN of the EVC
3JK Issue 1.00
3 4 37
Connection Less EVC list
To display the EVC List configured in a Bridge Domain,
from the MS_GUI:
Search Packet Services Connection Less
Bridge EVCs
Customer
Service
EVC
VC LSP
LSP Tunnel
Transport
3JK Issue 1.00
3 4 38
Provider Bridge EVC creation: General
To create a Provider Bridge
EVC:
1) Actions Packet
Services Connection Less
Create Bridge EVC
or
1) Select one EVC in the list
2) Actions Bridge EVC
Create Bridge EVC
Select the Network Element
and the edge port to add
EVC terminations
Assign Peer as Role
To create a new Provider bridge EVC:
In the General part:
enter an EVC User Label
select a Service Type from the list.
Ethernet Service: choose an Ethernet service by clicking in the box. This field is automatically filled if
the window is requested from the Service List
Domain: choose a Provider Domain by clicking in the box
Type (Point to point, Any to any) is automatically filled, as consequence of chosen Service
Traffic Type (Unicast, Multicast) is automatically filled, as consequence of Service Type field
select a Resource sharing attribute, if not already assigned
Comment is optional
Termination: the operator must select the physical edge port and assign a termination role (Peer for
Provider bridge).
N.B: Edge port are listed if previously assigned to a Bridge Domain
3JK Issue 1.00
3 4 39
Provider Bridge EVC creation: Detail
Details panel:
S-VLAN assigned to the Service
In the Details part:
select a VLAN Distribution: Full mesh, Not full mesh (see below)
enter S-VLAN Id
enter a VLAN Bundle
select a VLAN type (by clicking in the box) or set the Set Standard VLAN Type to True
Unicast/Multicast/Broadcast Service Frame Delivery: defines the policies to be applied to the incoming
Unicast/Multicast/Broadcast frames on the EVC:
Deliver Conditionally = MAC learning based
Deliver Unconditionally = VLAN based
Enable or Disable IGMP Snooping state
n.b: this field is available only for Provider Bridge Service (EVPLAN, BTV)
N.B. In case of full-mesh the system automatically distributes the VLAN in PKT-MIB to all transport links
(I.e. NNI ports) in the Domain; in case of not full-mesh the operator must assign the specific NNI ports
by manually adding/removing a set of transport links to the allocated EVC
3JK Issue 1.00
3 4 40
Provider Bridge EVC creation: L2 Control Protocol
In the Layer 2 Control Protocol part the operator can select which control protocol must be tunnelled
or discarded.
In this panel the configuration is propagated to all EVC terminations (this in order to ensure that all EVC
terminations uses the same Tunnelling criteria)
Possible values: Not Meaningful, Tunnel (set Default in the top field), Discard (set Free in the top
field)
3JK Issue 1.00
3 4 41
Provider Bridge EVC creation: PM
Set True to enable PM.
(Refer to specific session
for details)
3JK Issue 1.00
3 4 42
Provider Bridge EVC creation: Miscellaneus
Miscellaneus panel:
with the Terminations
Settings window
In the Miscellaneous part:
select a Service Level (Premium, Gold, Silver, Bronze) (N.B. no effect on real traffic)
C-VLAN Preservation: when True selected, it ensure that each packet exiting the EVC (at some egress
UNI) has the same VLAN id information that it had when it entered the EVC (at some ingress UNI).
C-Vlan Cos Preservation: when True selected, it ensure that each packet exiting the EVC (at some
egress UNI) has the same Priority Bits information that it had when it entered the EVC (at some ingress
UNI).
select a NAD value by clicking in the box
External Mark: (optional) it can be used to identify external systems having some relation with the EVC
(for example an ownership).
Comment: optional
Text: optional
3JK Issue 1.00
3 4 43
Provider Bridge Ingress/Egress Flows: definition
Ingress
Flow
PROVIDER
OUTFLOW
CLASSI
FIER
S-VID
POP
Egress
Flow
PROVIDER
INFLOW
TD &
Pol.
TD0
ETS_P
Port
LAN
or
SDH
ETS_P
Port
LAN
or
SDH
ES card
L2 switching layer
S-VID
PUSH
At least one Ingress Flow or at least one Egress Flow should be defined, in order to cover the following
cases:
To define someSource EVC termination point in Broadcasting topologies, only Ingress Flows are
defined
To define some Sink EVC termination point in Broadcasting topologies, only Egress Flows are
defined
To define some Bidirectional EVC termination point in P2P, Rooted MP, MP2MP topologies, Ingress
Flows and Egress Flows are defined; such points can be either balanced (that is having equal I/O
characteristics) or unbalanced (that is having Ingress characteristics different from Egress
characteristics in term of Classification, bandwidth, QoS and so on.
3JK Issue 1.00
3 4 44
Terminations Settings Ingress Flow
By clicking on Next the operator has access to the configuration of
the Ingress Flow and Egress Flow configuration window:
1. Click here to
select the port
3. Select an Ingress Flow
in the list, and confirm
with the icon
2. Specify
Ingress Flow
parameters
The operator has to configure at least an Ingress flow or at least an Egress flow for
each EVC termination
For each Ingress Flow:
choose a Traffic Descriptor. If Policy Mode is Color Aware, the Traffic Descriptor must be necessarily
Regulated.
select a Policy Mode (Color Blind, Color Aware, Disabled)
if Color Aware is chosen, select a Color Profile
VLAN Pop Enabled: set to True if a VLAN pop is required at the Ingress side (see next slides)
3JK Issue 1.00
3 4 45
Terminations Settings Ingress Flow: add Classifier
4. Open the classifier list and
confirm with the icon
Traffic Classifier panel:
More than one Traffic Classifier could be associated to an Ingress Flow
N.B. the Traffic Classifier must be compatible with the Classification Mode selected
3JK Issue 1.00
3 4 46
Terminations Settings Egress Flow
1. Click here to
select the port
2. Select an Egress Flow
in the list, and confirm
with the icon
4. Enable (False) or
disable (True)
push operation at
the egress side
3. Assign a CoS
(see Notes)
For each Egress Flow:
Class Of Service: assign the same CoS that the packets had when entered the EVC
Push:
set Clear all fields to True to disable push operation at the egress side; set False to enable push
operation: in this case the related fields must be filled (see next slides)
3JK Issue 1.00
3 4 47
Vlan Push/Pop at UNI interface
The Vlan Push/Pop at UNI interface of a bridge domain is provided for
inter-working purposes, this meaning that only the following
operations can be performed:
VLAN Push on the Egress Flow of an EVC Termination
VLAN Pop on the Ingress Flow of an EVC Termination
VLAN Push
VLAN Pop
EgressFlow
IngressFlow
3JK Issue 1.00
3 4 48
Vlan Push on Egress Flow
The Vlan Push on Egress Flow allows to encapsulate untagged or C-
Vlan tagged Ethernet frames with a Provider V-Lan Tag, for
interworking purpose
VLAN Push
EgressFlow
To enable the Push operation, the operator must set Clear all fields to False:
- enter the Vlan to be pushed
- if Policy Mode is Color Blind, choose the Green Priority value (priority of all the packets after the
push)
- if Policy Mode is color Aware, choose Green Priority and Yellow Priority values for all green and
yellow outgoing packets
3JK Issue 1.00
3 4 49
Vlan Pop on Ingress Flow
The Vlan Pop defines a POP operation to be performed on Ethernet
traffic ingressing in the Provider Bridge Domain
VLAN Pop
IngressFlow
To enable the Pop operation, the operator must set VLAN Pop Enabled to True
3JK Issue 1.00
3 4 50
EVC Terminations list
The EVC Termination List window presents all the termination of the
selected EVC and their attribute
To display the EVC Terminations list:
2) Search Bridge EVC EVC Terminations
From this list is possible to display the EVC Termination properties, to modify or to delete it
3JK Issue 1.00
3 4 51
Add EVC Termination
This function consists in adding a
new termination to an existing
Connection Less EVC
To add an EVC Termination:
1) Select an Ethernet Service:
2) Actions Bridge EVC Add
Connection Less EVC Termination
Select the termination to be
added
EVC Termination role must be
congruent with EVC Topology
3JK Issue 1.00
3 4 52
Add Provider Bridge Ingress Flow
This window permits to configure
the parameters at the input
direction on a specific edge port
in case of Provider Bridge
To add an Ingress Flow:
1) Select an EVC Termination:
2) Actions EVC Termination
Add Provider Bridge Ingress Flow
Ingress
Flow
CLASSI
FIER
TD &
Pol.
ETS_P
Port
In the general Part:
Traffic Descriptor: select a Traffic Descriptor previously defined
if chosen traffic descriptor is Regulated, is possible to choose Color Aware as Policy Mode and a
Color Profile, using next box (cpl_label)
Select a Classification Mode (Priority or DSCP) for the Ingress flow;
VLAN Pop Enabled: set True to enable or False to disable the VLAN POP operation at the edge port
(see previous slides for details)
Select one or more Traffic Classifier, previously defined (click on the icon to display the
Traffic Classifier list)
N.B. the Traffic Classifier must be compatible with the
Classification Mode selected
In the Layer 2 Control Protocol part choose a BPDU filtering criteria, at termination level
Click on OK to finish the operation
3JK Issue 1.00
3 4 53
Add Provider Bridge Egress Flow
This window permits to create
the output flow and enable the
PUSH operation on a specific
edge port in case of Provider
Bridge
To add an Egress Flow:
1) Select an EVC Termination:
2) Actions EVC Termination
Add Provider Bridge Egress
Flow
Egress
Flow
ETS_P
Port
In the Add Provider Bridge Egress Flow window, the operator can enable the PUSH operation on a
specific edge port:
Clear all fields = True : Push operation is disabled
Clear all fields= False : Push operation is enabled
(see previous slides for details)
It is possible to choose a specific Class of Service for the outgoing flow, or maintain the same as the
ingress flow
Click on OK to finish the operation
3JK Issue 1.00
3 4 54
Provider Bridge Egress / Ingress Flow list
To display the Provider Bridge
Ingress or Egress Flows List
configured in an EVC, from the
MS_GUI:
2) Action Bridge EVC
Provider Bridge Flows
N.B: It is possible to display the Ingress flow or Egress flow of an EVC Termination, if the list is requested
from the specific termination
3JK Issue 1.00
3 4 55
Provider Bridge EVC Termination Egress / Ingress Flow list
It is possible to display the Ingress flow or Egress flow of an EVC
Termination, if the list is requested from the specific termination :
1) Select an EVC Termination the list
2) Search EVC Termination List Provider Bridge Egress / Ingress
Flow
From this list is possible to display the EVC Termination properties, to modify or to delete it
3JK Issue 1.00
3 4 56
EVC modification
To modify an EVC :
The provisioning state of the EVC must be Defined
In the General part is possible to modify::
User Label
Ethernet service
Comment (optional)
In the Details part is possible to modify:
VLAN distribution
S-VLAN Id (for Provider Bridge only)
VLAN Bundle
Vlan Type
Unicast/Multicast/Broadcast Service Frame Delivery criteria
IGMP Snooping (for Provider Bridge only)
In the Layer 2 Control Protocol part is possible to modify the BPDU filtering criteria, at termination
level (for Provider Bridge only)
In the OAM part is possible to enable/disable the OAM feature and assign the priority to C.C packets
In the Miscellaneous part is possible to modify:
C-VLAN Preservation
C-VLAN CoS Preservation
NAD value
External Mark (optional)
Comment and text
3JK Issue 1.00
3 4 57
EVC configuration
The configuration of an EVC consists in associating a Traffic
Descriptor and a VLAN Bundle to the EVC.
To configure an EVC :
2) Actions (or right mouse button) Bridge EVC Configure EVC
It is possible to dynamically change
(increment/decrement) the
bandwidth on active (i.e.
implemented) Ethernet
connectivity. (See notes below for
details)
The provisioning state of the EVC can be Defined, Allocated or Implemented
Changing a Traffic Descriptor on implemented or allocated EVC level, the bandwidth change is
propagated to all Nes involved in the service.
The bandwidth change is only admitted in the scope of the same QoS (e.g. change from BE to Guaranteed
is not allowed as well as other mixed possibilities).
3JK Issue 1.00
3 4 58
EVC properties and deletion
To get the EVC Properties:
To delete an EVC:
2) Actions (or right mouse button) Bridge EVC Delete
In deleting an EVC the provisioning state of the EVC must be Defined
3JK Issue 1.00
3 4 59
EVC Termination Properties and deletion
To get the EVC Termination Properties:
To delete an EVC Termination:
2) Actions (or right mouse button) EVC Termination Delete
3JK Issue 1.00
3 4 60
Blank Page
3JK Issue 1.00
3 4 61
5 Spanning Tree Instance management
3JK Issue 1.00
3 4 62
5 Spanning Tree Instance management
Spanning Tree Instance List
To display the Spanning Tree Instance List configured in a Bridge
Domain, from the MS_GUI:
Search Packet Services Connection Less Spanning Tree
Instance
3JK Issue 1.00
3 4 63
6 Ethernet Virtual Connection life cycle
3JK Issue 1.00
3 4 64
Definition
EVC life cycle :
Defined state
Allocate
Commission
Implement
EVC allocation means to associate the selected Spanning Tree Instance to the set of VLAN characterizing
the EVC.
EVC Implementation establishes an Ethernet flow inside the Bridges
Commissioning of the EVC is made in order to give in charge administrative management to a related
customer; the Service state of the EVC and the parent Ethernet Service is update to In Service
3JK Issue 1.00
3 4 65
EVC life cycle: commands
To allocate/deallocate the EVC:
1) Select one or several EVC in the list
2) Actions Bridge EVC Allocate/Deallocate
3) Select a Spanning Tree Instance and click on Apply
To implement/deimplement the EVC:
2) Actions Bridge EVC Implement/Deimplement
To commission/decommission the EVC:
2) Actions Bridge EVC Commission/Decommission
Commissioning is an operative operation, has no effect on Nes.
It allows to notify the availability of the Service to be used to carry Ethernet Traffic
After commission, the Service State of the EVC change from Not in service to In service
3JK Issue 1.00
3 4 66
Exercise
According to the Classroom setup, configure a Provider-bridge Network,
including two different customers and different Transport Link typology
interconnecting Nes.
Example of exercise set-up:
B
B
A
A
Customer
B
Link over Cable
A
Link over SDH
3JK Issue 1.00
3 4 67
End of Module
Bridge Provisioning
All Rights Reserved 2007, Alcatel-Lucent
3JK Edition 1.00
37
Module 7
Network utilities
3JK Edition 1.00
Section 3
System Operation
3JK Edition 1.00
System Operation Network utilities
3 7 2
Blank Page
Document History
3JK Edition 1.00
3 7 3
Module Objectives
Detect, by means of Audit, the misalignment between the NE and 1350OMS
PKT dB
Fix the misalignment by executing a download into the NE
3JK Edition 1.00
3 7 4
3JK Edition 1.00
3 7 5
Table of Contents
Page
1 NE Audit tool 7
2 NE Reserve tool 13
3 NE Alignment tool 15
4 NE Force Alignment tool 17
5 PKT vs SDH synchronization 21
3JK Edition 1.00
3 7 6
3JK Edition 1.00
3 7 7
1 NE Audit tool
3JK Edition 1.00
3 7 8
1 NE Audit tool
Introduction
The Audit feature provides the operator with a means to detect if a
misalignment exists between the 1350OMS PKT and NEs.
The operation consists in comparing the content of the NE MIB with the
content of the PKT database; after the comparison the differences are
classified as follow:
Data existing in the NE and missing in the PKT
Data existing in the PKT and missing in the NE
Different data using the same resources in NE and PKT
On the basis of the audit file information the operator may proceed
with one of the following operation:
Reserve, in order to insert in the PKT the resources discovered in the NE MIB
not present in the PKT database
(not available in current release)
Align, in order to insert in the NE MIB the resources discovered in the PKT
not present in the NE
Force Align, in order to full re-align NE MIB to the PKT database
3JK Edition 1.00
3 7 9
1 NE Audit tool
Perform an Audit
The AAR Procedure must be start prior to doing Audit, Alignment,
Reservation operations:
Actions Packet Audit Align Reservation Start AAR Procedure
To display the list of the Nes available for the Audit:
Search Packet Audit Align Reservation NEs for Audit
To request an Audit:
1) Select one or several NEs from the Auditable NE list
2) Actions Auditable Ne Start NE Audit
This function consists in starting an audit on the selected NE.
When an audit is started on a NE, this NE is locked to avoid any modification of its MIB during the
procedure life time. At the end of procedure, the NE is unlocked.
3JK Edition 1.00
3 7 10
1 NE Audit tool
Display the Audited NE list
To display the Audited NE :
Search Packet Audit Align Reservation Audited NEs
The Audited NEs are locked
3JK Edition 1.00
3 7 11
1 NE Audit tool
Display the Audit File
To display the Audit file :
1) Select one or several NEs
from the Audited NEs List:
2) Actions Audited Ne
Display NE Audit File
The audit result is displayed according the three domains compared, Construction Domain, MPLS Domain,
Ethernet Domain, T-MPLS Domain and for each domain a list of concerned entities and their compared
attributes are shown.
3JK Edition 1.00
3 7 12
1 NE Audit tool
End of procedure
After executed the alignment, the end of procedure is necessary in
order to have all NEs again available for the common operations the
user:
Actions Packet Audit Align Reservation Stop AAR Procedure
At any time of the audit / alignment / reserve session the operator can close the session. An unlock of
the locked NEs will be done.
3JK Edition 1.00
3 7 13
2 NE Reserve tool
3JK Edition 1.00
3 7 14
2 NE Reserve tool
Perform a reservation on an NE
To start a Reservation operation:
1) Select one or several NEs from the Audited NEs List:
2) Actions Audited Ne NE Resource Reservation
N.B. Not yet implemented in the scope of 1350OMS PKT rel9.1.1
This function consists in starting the reservation on the selected NE.
The reservation operation inserts in the PKT database the resources discovered in the NE MIB and not
present in the PKT database, such as:
- Traffic descriptor
- traffic classifier
- color profiles
- Ethernet connections
- MPLS connections
3JK Edition 1.00
3 7 15
3 NE Alignment tool
3JK Edition 1.00
3 7 16
3 NE Alignment tool
Perform an alignment on an NE
To start an Alignment operation:
2) Actions Audited Ne NE Align Down
The Alignment State of the
NE is set to Done
This function consists in starting the alignment on the selected NE.
The alignment operation inserts in the NE MIB the resources discovered in the PKT database and not
present in the NE.
3JK Edition 1.00
3 7 17
4 NE Force Alignment tool
3JK Edition 1.00
3 7 18
Introduction
The Force Alignment operation allows to force the image of the
Network (as it is known to PKT) on the NEs
This operation is splitted in two parts:
Preparation in order to build all the elementary operations needed to
realize the re-alignment
Force Align Down in order to execute the operations following the provided
sequence
3JK Edition 1.00
3 7 19
Perform a Preparation on an NE
To create an Alignment file:
Select one or several NEs from the Audited NEs List:
1. Actions Audited Ne NE Force Align Down Preparation
The operator can display the Preparation file:
1. Select one or several NEs from the Audited NEs List:
2. Actions Audited Ne Display NE Preparation File
3JK Edition 1.00
3 7 20
Perform a Force Align Down on an NE
To start a Force Alignment operation:
2) Actions Audited Ne NE Force Align Down Execution
This function consists in starting the alignment on the selected NE.
The alignment operation inserts in the NE MIB the resources discovered in the PKT database and not
present in the NE.
3JK Edition 1.00
3 7 21
5 PKT vs SDH synchronization
3JK Edition 1.00
3 7 22
5 PKT vs SDH synchronization
Manual synchronization
At startup, the 1350 OMS PKT synchronizes the TDM terminations and
Links Over TDM tables with 1350 OMS SDH APS and SDH paths.
In case of possible misalignment between the two layers, the operator can
start a manual synchronization:
Actions Packet Construction Synchronization Manual
Resynchronize
1350
PKT
1350
SDH
Manual Resynchronize
TDM Terminations and
Link over TDM uploading
The synchronization status can be checked at any time, by:
Action Packet Construction Synchronization Check Synchronization Status
3JK Edition 1.00
3 7 23
End of Module
Network utilities
3JK Issue 1.00
41
Module 1
Alarm Management
3JK Issue 1.00
Section 4
Maintenance Applications
1350OMS
3JK Issue 1.00
Maintenance Applications Alarm Management
4 1 2
Blank Page
Document History
3JK Issue 1.00
4 1 3
Module Objectives
Manage the elementary alarms affecting 1350OMS PKT managed resources.
3JK Issue 1.00
4 1 4
3JK Issue 1.00
4 1 5
Table of Contents
Page
1 Alarm display 7
2 Fault management 13
3JK Issue 1.00
4 1 6
3JK Issue 1.00
4 1 7
1 Alarm display
3JK Issue 1.00
4 1 8
1 Alarms display
Alarms propagation
Alarm Propagation & Analysis Engine
Ethernet
Segment
Link over
WDM
TDM
Termination
Path
Ethernet
Port
Link
over Cable
Link
over T-MPLS
Link over
TDM
(SDH/Sonet)
GFP
AS
AS
AS
AS
Alarm Sources
NE
(reachability)
NE
(isolation)
AS
Customer
Service
Segment
EVC
Tunnel
Transport
PW
AS
3JK Issue 1.00
4 1 9
1 Alarms display
Routing display alarm propagation
Customer
Service
Segment
EVC
PW
Transport
Tunnel
Alarmed
object
3JK Issue 1.00
4 1 10
1 Alarms display
Fault localization
To display the Fault localization list :
Select an entity with Availability status Degraded or In Failure
1) Search <entity denomination> (i.e. Link Over Cable)
Fault Localization
The fault localization allows the operator to determine the list of elementary alarms affecting a Packet
managed resource as Ethernet Segment, Transport Links, LSP tunnel, PseudoWire, ....
The data displayed are not automatically refreshed; the Reload data button is available.
3JK Issue 1.00
4 1 11
1 Alarms display
Alarm Surveillance
To start Fault Management GUI:
Select the Alarms (PKT 1-9.1.0) icon in the Alarms application of the
Web Portal:
Actions Launch application or
Right mouse button Start or
Double click on the icon
From the current alarm sublist the operator can display the Fault Localization list:
from the AS CUSM_PKT Alarm Sublist:
1) select an alarm
2) Windows External Application Fault_Localization
From the current alarm sublist the operator can navigate to the historical alarm window.
(refer to the 1350OMS EML Student Guide for description)
3JK Issue 1.00
4 1 12
Blank Page
3JK Issue 1.00
4 1 13
2 Fault management
3JK Issue 1.00
4 1 14
2 Fault management
Manual Alarms Synchronization
The operator can resynchronize, on NE basis, all alarms currently
existing on a given NE;
the new Alarm situation is read directly from selected NE and propagated to
AS and internally (Construction, Services, MPLS, T-MPLS)
Select a Network Element in the list
1) Action Network Element Alarm Synchronization
1350
PKT DCN
Alarm Updating
Alarm Synchronization
3JK Issue 1.00
4 1 15
2 Fault management
Exercise
From Web Portal, open the AS Current USM
If possible, create a failure into the TDM network, then:
check it in the Fault Localization window
Check the previous alarm in the AS window, and navigate to Fault
Localization
Perform an Alarm Synchronization
3JK Issue 1.00
4 1 16
End of Module
Alarm Management
xx Issue 01
42
Module 2
Performance monitoring
xx Issue 01
Section 4
Maintenance Applications
1350OMS
xx Issue 01
Maintenance Applications Performance monitoring
4 2 2
Blank Page
Buono Giovanni 2010-02-26 01
Document History
xx Issue 01
4 2 3
Module Objectives
activate and deactivate Performance Monitoring
display the results
export PM information
compare the NMLs PM DB with the EMLs PM DB
xx Issue 01
4 2 4
xx Issue 01
4 2 5
Table of Contents
Page
1 PM from 1350OMS-PKT point of view 7
2 PM on Ethernet Service 12
3 T-MPLS PM management 29
4 PM advanced operation 42
xx Issue 01
4 2 6
xx Issue 01
4 2 7
1 PM from 1350OMS-PKT point of view
xx Issue 01
4 2 8
Objectives
Received
packets
Received
packets
Discarded
Packets
Discarded
Packets
Transmitted
packets
Transmitted
packets
Performance Monitoring tools allow to analyze traffic behavior on a specific
Ethernet interface.
Incoming and Outgoing traffic is analyzed, as well as data traffic lost, or
discarded.
Graphic or tabular reports are generated
Port 1 Port 2
Port 3 Port 4
xx Issue 01
4 2 9
PM objects
Measure
PM transport
PM TP
PM domain
Report
Profile
Archive
session
DB Administration
Report Profile periodically
copies the PM data to .csv files.
Archive Session is an
administration issue that is
used to archive PM data on a
file in order to free space on
the PM database.
Measures are defined on 1350OMS-ETH transport entities (EVC, Tunnel, PseudoWire) and requested on
NEs Termination Points (TPs).
For each transport entity a PM transport is created. For each TP a PM TP is created.
1350OMS-ETH requests 1350OMS-EML to start the counters on NEs whose TPs have to be monitored.
xx Issue 01
4 2 10
PM Domain
Measure
PM Transport
Procedure
1. Select the transport entity (EVC, Tunnel, PW) and Start PM:
Measure, PM Transport, and PM TPs are automatically created
2. Open the PM Domain
3. Locate and retrieve the measure
4. Retrieve the PM Transport
5. Retrieve the PM TPs:
they provide the PM results
6. To stop the PM, select the transport entity and Stop PM
7. Delete the Measure
PM TP
PM TP
Measure
PM Transport
PM TP
PM TP
Each Measure contains
one PM Transport that
contains the PM TPs
PM TP
Measure: it defines the objective, the time granularity and other parameters of the PM.
xx Issue 01
4 2 11
Measure lifecycle
Start PM yields an
activated Measure
remove
transport object
deimplement
transport object
ACTIVATED
Measure
Start PM Stop PM
remove
transport object
implement
transport object
Deimplement
transport object
implement
transport object
Delete
Measure
Delete
Measure
Delete
Measure
STANDBY
Measure
TERMINATED
Measure
STOPPED
Measure
Measure:
Activated: TP counters are started, hence PM results and PM alarms can be inspected.
Stopped: TP counters are stopped. Only former PM results can be inspected.
Standby: the monitoring activities are interrupted temporarily because the PM Transport is
deimplemented.
Terminated: the monitoring activities are interrupted forever because the PM Transport has been
removed. This state can be seen because the Measures attribute Auto Purge is set to False.
xx Issue 01
4 2 12
Blank Page
xx Issue 01
4 2 13
2 PM on Ethernet Service
xx Issue 01
Section 3 - Module 6 - Page 14
4 2 14
Performance Monitoring overview
The system support Ethernet Aggregated octet/frame counters and also
octet/frame counters on per flow (service) basis.
Monitored object:
IN
FLOW
OUT
FLOW
REMOTE
Eth. Port
S
D
H

p
o
r
t

A
A
U
4
S
D
H

X
C
E
T
S

X
C
LOCAL Eth.
Port
Transmitted frames
Received frames
Received frames
Transmitted frames
xx Issue 01
4 2 15
Aggregated Counters
IN
FLOW
OUT
FLOW
S
D
H

p
o
r
t

A
A
U
4
Transmitted frames
Received frames
Received frames
Transmitted frames
Aggregate counters on
Received Frames:
TRCF
TRCF Broadcast
TRCF Multicast
TRCF Unicast
TRCO
TRDF
TRSEF
Aggregate counters on
Transmitted Frames:
TTDF
TTF
TTF Broadcast
TTF Multicast
TTF Unicast
TTO
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
xx Issue 01
4 2 16
Per Flow Counters
IN
FLOW
OUT
FLOW
S
D
H

p
o
r
t

A
A
U
4
Transmitted frames Received frames
Ingress Flow counters:
TRCF
g
TRCF
y
TRCO
g
TRCO
y
Egress Flow counters:
TTFg
TTFy
TTOg
TTOy
TRCF
g
: number of Total Received Correct green Frames
TRCF
y
: number of Total Received Correct yellow Frames
TRCO
g
: number of Total Received Correct green Ethernet Octets
TRCO
y
: number of Total Received Correct yellow Ethernet Octets
TTF
g
: number of Total Transmitted green Ethernet Frames
TTF
y
: number of Total Transmitted yellow Ethernet Frames
TTO
g
: number of Total Transmitted green Ethernet Octets
TTO
Y
: number of Total Transmitted yellow Ethernet Octets
xx Issue 01
4 2 17
PM activation during the EVC creation
Choose True and set
the parameters
Granularity: is the monitoring frequency, i.e. the frequency of historical data counters grouping. The
operator can select:
- 24 hours . Data are grouped per day.
15 minutes. Data are grouped per quarter of hour.
Involved TPs: choose the TPs involved in the measurement ( No Points, only End Points, only
Intermediate Points, All Points)
CSV Reporting: define the periodicity of the CSV file creation as report: 2 Hours or 24 Hours in case of 15
min granularity; 24 Hours in case of 1 day granularity
Policy: which deals on maintaining PM data:
- Keep: data are maintained
- Purge on stop: data are purged at the measure termination
- Purge on delete: data are purged at the measure deletion
- Not meaningful
xx Issue 01
4 2 18
PM activation for an already created service
1. To Create and Start PM:
1. select the EVC
2. (right mouse button):
Actions PM Start
PM
N.B: the EVC must be Implemented
xx Issue 01
4 2 19
PM activation for an already created service [cont.]
2. Set the specific
parameters
3. Click on Apply
Granularity: is the monitoring frequency, i.e. the frequency of historical data counters grouping. The
operator can select:
- 24 hours . Data are grouped per day.
15 minutes. Data are grouped per quarter of hour.
Involved TPs: choose the TPs involved in the measurement ( No Points, only End Points, only
Intermediate Points, All Points)
CSV Reporting: define the periodicity of the CSV file creation as report: 2 Hours or 24 Hours in case of 15
min granularity; 24 Hours in case of 1 day granularity
Policy: which deals on maintaining PM data:
- Keep: data are maintained
- Purge on stop: data are purged at the measure termination
- Purge on delete: data are purged at the measure deletion
- Not meaningful
xx Issue 01
4 2 20
PM result
1. Search PM PM
Domains on NML
2. Select ETH: Search
PM Measure
xx Issue 01
4 2 21
PM result [cont.]
3. Select the measure:
Search PM Transports
4. Select the transport:
Search PM TPs
xx Issue 01
4 2 22
TP list
I.e:
The list of the available TP is displayed
1 81
65B 64B
1 80
End Point
End Point
Intermediate Point
Intermediate Point
xx Issue 01
4 2 23
Generate report
1. Select the PM TP
Actions Generate
2. Choose From Time
and End Time
PM results are retrieved from NE by
1350OMS every 2 hours (for the 15min)
or every 24 hours (for the 24h).
The list of available TPs is displayed; it s possible to retrieve measurements for:
Aggregated Ports, UNI or NNI (Type = ETHINTERFACE)
per flow basis (Type = FLOW)
xx Issue 01
4 2 24
Report examples
Tabular
Line chart
Bar chart
xx Issue 01
4 2 25
How to deactivate PM
To stop the PM counters on an EVC:
1. select the EVC
2. (right mouse button): Actions
PM Stop PM
3. Select the Granularity of
the counter to be stopped
and click on Apply
xx Issue 01
4 2 26
PM synchronization
To align the PM set to the EVC set:
1. select the EVC
2. (right mouse button): Actions
PM Synchro PM
This operation is executed when the operator wants to align PM setting
to EOT setting
3. Select the Granularity of the
counter to be synchronized
and click on Apply
xx Issue 01
4 2 27
Operation from Measure: Delete, Consist
Delete Measure
Consist Measure: must be run
whenever Consistency is
Not Consistent
Tick the box and
click on Apply
In order to delete a measure, the State must be different from Activated
xx Issue 01
4 2 28
Operation from Measure: Modify
Click on the field to
modify the
attributes, then
click on Apply
It is possible to modify the following attributes:
User Label
Start Time
End Time
Auto Purge (False, True)
Security Label
Purge (At Termination, At Stop)
Collect Counter (true, false)
xx Issue 01
4 2 29
Navigation from Transport to PM Transport
From PM Transport to Transport:
Look for the PM Transports User
Label (its equal to the
Transports User Label) in the
Transport list by applying a
filtered search:
Search NAV TO PKT ..
From Transport to PM
Transport:
Select the Transport:
Search Show PM
Navigation from Transport to PM Transport: without opening the PM Domain and the Measures list, its
possible to get the PM Transport directly from the Transport.
xx Issue 01
4 2 30
Blank Page
xx Issue 01
4 2 31
3 T-MPLS PM management
xx Issue 01
4 2 32
Performance Monitoring on T-MPLS object
The following TMPLS Objects can be monitored from PM point of view:
TMPLS Tunnel;
TMPLS Pseudo Wire;
(PE) (PE) (P)
PW
MPLS
Tunnel
PM on
End Point
PM on
End Point
PM on
End Point
PM on
End Point
PM on
Intermediate
Points
PM on
Intermediate
Points
PM on
Intermediate
Points
PM on
Intermediate
Points
xx Issue 01
4 2 33
PM activation on End Points
The Performance Monitoring tool allows to activate counters on T-MPLS
ports, collecting and displaying performance data associated with the
Pseudowire and the T-MPLS tunnel end points
Monitored object:
PWSEG (Bid)
PW Bid
TUSEG#x
(Bid)
Incoming packet
Outgoing packet
Eth local port
xx Issue 01
4 2 34
How to activate counters on End Points
1. Select a Tunnel (or PW):
Actions Start PM
2. Specify the
Granularity and
click on Apply
PM Granularity: choose 15 minutes or 24 hours
xx Issue 01
4 2 35
PM activation on Intermediate Points
The Performance Monitoring tool allows to activate counters on T-MPLS
ports, collecting and displaying performance data associated with the
transit Pseudowire and the transit T-MPLS tunnel
I.e: Transit Tunnel Intermediate points
PW Bid
TUSEG#x
(Bid)
Incoming packet
Outgoing packet
xx Issue 01
4 2 36
How to activate counters on Intermediate Points
1. Open the Tunnel (or
PW) Routing Display
2. Select one intermediate
tunnel segment: Actions
Configure
3. Specify the Granularity
and click on Apply
PM Granularity: choose 15 minutes or 24 hours
N.B: PM measure on intermediate points can be activated only if Under PM is true for the Tunnel (or
PW), that is only if previously the PM have been started on the Tunnel (or PW). (See previous slides)
xx Issue 01
4 2 37
PM result
1. Search PM PM
Domains on NML
2. Select ETH: Search
PM Measure
xx Issue 01
4 2 38
PM result [cont.]
3. Select the measure:
Search PM Transports
4. Select the transport
(i.e: Tunnel):
Search PM TPs
xx Issue 01
4 2 39
TP list
6 1 1 1
C322 C323 C321
(i.e:
The list of the available TP is displayed
End Point
End Point
Intermediate Point
Intermediate Point
The list of available TPs is displayed; it s possible to retrieve measurements for:
End Points
Intermediate Points
xx Issue 01
4 2 40
Generate report
1. Select the PM TP
Actions Generate
2. Choose From Time
and End Time
PM results are retrieved from NE by
1350OMS every 2 hours (for the 15min)
or every 24 hours (for the 24h).
xx Issue 01
4 2 41
Report examples
Tabular
Line chart
Bar chart
xx Issue 01
4 2 42
How to deactivate PM
To stop the PM counters on T-MPLS ports:
1. select the Tunnel (or PW)
2. (right mouse button): Actions Stop PM
3. Confirm
xx Issue 01
4 2 43
Exercise
Activate PM counters on a T-MPLS EVC and a T-MPLS Tunnel
Check the PM Transport and the PM TPs.
Retrieve the result.
xx Issue 01
4 2 44
Blank Page
xx Issue 01
4 2 45
4 PM advanced operation
xx Issue 01
4 2 46
Report Profile: creation
To look for the available profiles: select the
ETH PM Domain Search Report Profiles
To create a profile: select the ETH PM
Domain Actions Create Report Profiles
Report Profile holds the
rules for creating files
that record the PM results
(TRCF, TRCO, TRSEF,).
Files are generated every
window time.
The CSV format can be exported to Microsoft Excel.
Destination Type:
files: a single report file is created at the chosen frequency (window) for all the measures correlated
to the report. For example, by correlating 4 different 15min measures to a report having a window of
1 hour, only 24 files are created in a day: i.e. every hour a single file is created with the results of all
the measures. The files name is: _Reports User Label_window_x_N00000.csv
(_My_Report_15MIN_8_N00000.csv).
file: a report file is produced at the chosen frequency (window) for each measure correlated to the
report. For example, by correlating 4 different 15min measures to a report having a window of 1
hour, 24x4 = 96 files are created in a day: i.e. every hour a file is created for each measure. The
files name is: _Transports User Label_window_x_co.csv (_MyPath_auto_0_15MIN_8_co.csv).
Window: it must be suitable for the granularity:
granularity = 15min window = 15min, 1h, 2h, 24h.
granularity = 24h window = 24h, 1week, 1month, 2months, 1year.
xx Issue 01
4 2 47
Report Profile: correlation
1. To associate the profile to
the measure: select the
Measure: Actions
Correlate with Report Profile
To disassociate the profile from
the measure: select the Measure:
Actions Uncorrelate with
Report Profile
2. Choose the profile
To delete a Report Profile:
it must not be correlated to any measures.
open the Report Profile list select the Report Profile Actions Delete Report Profiles.
xx Issue 01
4 2 48
Manual exports
To export the PM TPs list to a CSV file:
select the ETH PM Domain Actions Export TPs to To CSV file
enter the location / files name of the file
To export the results of a given measure over a period to a CSV file:
select the Measure Actions Generate Report To CSV File
enter: From Time, End Time, output file location
(the files name will be: <file_name>CPM_NM_CSV_EXPORT_Date_Time)
To export the results of a given PM TP over a period to a CSV file:
select the PM TP Actions Generate Report To CSV File
choose: From Time, End Time, Granularity, output file location
(the files name will be: <file_name>CPM_NM_CSV_EXPORT_Date_Time)
xx Issue 01
4 2 49
NMLs
PM Database
EMLs
PM Database
PM Audit
The user can carry out a comparison between the EMLs PM DB and the
NMLs PM DB to discover the TPs with different PM configuration.
PM Transport
Measure
Monitored NE
Monitored TPs
PM NE (NML NE)
PM TPs (*)
Audit on
PM TP basis
Audit on
PM NE basis
NEs
MIB
TPs
Supposed
to be
aligned
(*) PM TPs can be retrieved
from PM Transport
PM NE is available if at least one of its PM TPs is required for a PM Transport.
xx Issue 01
4 2 50
PM Audit [cont.]
Audit on PM NE basis:
1. select ETH in PM Domains on NML:
Search NML NEs
2. Select a PM NE
Actions Audit NE
Audit on PM TP basis:
1. Select a PM TP Actions
Audit TP
Click on Apply
xx Issue 01
4 2 51
PM Audit: result
In case of PM Audit on PM TP basis, just one row is prompted
xx Issue 01
4 2 52
Exercise
Create a Report Profile and correlate it to a measure.
Export the PM TP list.
Export the results of a given measure.
Export the results of a given PM TP.
xx Issue 01
4 2 53
End of Module
Performance monitoring
@@COURSENAME - Page 1
All Rights Reserved Alcatel-Lucent @@YEAR
@@COURSENAME
@@PRODUCT
1
Last But One Page
@@COURSENAME - Page 2
All rights reserved Alcatel-Lucent @@YEAR
Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent

1350OMS-PKT R 9 - 1 - 1 Operation

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

1350OMS-PKT R 9 - 1 - 1 Operation

Încărcat de

Drepturi de autor:

Formate disponibile

1350OMS-PKT R 9.1.

S-ar putea să vă placă și