1350OMS-PKT R 9_1_1 Operation

December 19, 2017 | Author: Alejandro Flores | Category: Wavelength Division Multiplexing, Network Topology, Computer Network, Ethernet, Data Transmission
Share Embed Donate


Short Description

Download 1350OMS-PKT R 9_1_1 Operation...

Description

1350OMS 1350OMS-PKT R 9.1.1 Operation TOS63013-R.9.1.1-SG1-SEN-I1.0 Issue 1.00

STUDENT GUIDE

All Rights Reserved © Alcatel-Lucent 2010

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

All Rights Reserved © Alcatel-Lucent 2010 1350OMS-PKT R 9.1.1 Operation - Page 1

Empty page Switch to notes view!

2

All Rights Reserved © Alcatel-Lucent 2010

1350OMS 1350OMS-PKT R 9.1.1 Operation

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 1350OMS-PKT R 9.1.1 Operation - Page 2

Terms of Use and Legal Notices 1. Safetyto Warning Switch notes view! Both lethal and dangerous voltages may be present within the products used herein. The user is strongly advised not to wear conductive jewelry while working on the products. Always observe all safety precautions and do not work on the equipment alone. The equipment used during this course may be electrostatic sensitive. Please observe correct anti-static precautions.

2. Trade Marks Alcatel-Lucent and MainStreet are trademarks of Alcatel-Lucent. All other trademarks, service marks and logos (“Marks”) are the property of their respective holders, including AlcatelLucent. Users are not permitted to use these Marks without the prior consent of Alcatel-Lucent or such third party owning the Mark. The absence of a Mark identifier is not a representation that a particular product or service name is not a Mark. Alcatel-Lucent assumes no responsibility for the accuracy of the information presented herein, which may be subject to change without notice.

3. Copyright This document contains information that is proprietary to Alcatel-Lucent and may be used for training purposes only. No other use or transmission of all or any part of this document is permitted without Alcatel-Lucent’s written permission, and must include all copyright and other proprietary notices. No other use or transmission of all or any part of its contents may be used, copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from Alcatel-Lucent. Use or transmission of all or any part of this document in violation of any applicable legislation is hereby expressly prohibited. User obtains no rights in the information or in any product, process, technology or trademark which it includes or describes, and is expressly prohibited from modifying the information or creating derivative works without the express All Rights Reserved © Alcatel-Lucent 2010 3written consent of Alcatel-Lucent. 1350OMS 1350OMS-PKT R 9.1.1 Operation

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 AlcatelLucent 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. AlcatelLucent 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.

All Rights Reserved © Alcatel-Lucent 2010 1350OMS-PKT R 9.1.1 Operation - Page 3

Blank Page Switch to notes view!

4

All Rights Reserved © Alcatel-Lucent 2010

1350OMS 1350OMS-PKT R 9.1.1 Operation

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 1350OMS-PKT R 9.1.1 Operation - Page 4

Course Outline Section Product Overview About This1.Course

4. Topic/Section is Positioned Here

Course outline Module 1. Product Overview Technical support Interfaces Section 2. Graphical Course objectives

5. Topic/Section is Positioned Here

Module 1. How to Logon

Moduleis2.Positioned Network Topology 1. Topic/Section Here

6. Topic/Section is Positioned Here

Section 3. System Operation Xxx Xxx Module 1. Transport link Provisioning 7. Topic/Section is Positioned Here Xxx Module 2. Traffic descriptor Provisioning Module 3. Ethernet Service Provisioning

2. Topic/Section is Positioned Here

Module 4. Bridge Provisioning

Module 5. T-MPLS Provisioning 3. Topic/Section is Positioned Here Module 6. End to end provisioning Module 7. Network utilities Section 4. Maintenance Applications Module 1. Alarm Management Module 2. Performance monitoring

5

All Rights Reserved © Alcatel-Lucent 2010

1350OMS 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 1350OMS-PKT R 9.1.1 Operation - Page 5

Course Outline [cont.] Switch to notes view!

6 1350OMS 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 1350OMS-PKT R 9.1.1 Operation - Page 6

Course Objectives Switch to notes view!

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

7

All Rights Reserved © Alcatel-Lucent 2010

1350OMS 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 1350OMS-PKT R 9.1.1 Operation - Page 7

Course Objectives [cont.] Switch to notes view!

8 1350OMS 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 1350OMS-PKT R 9.1.1 Operation - Page 8

About this Student Guide 

Conventions used in this guide Switch to notes view! Note Provides you with additional information about the topic being discussed. Although this information is not required knowledge, you might find it useful or interesting.

Technical Reference (1) 24.348.98 – Points you to the exact section of Alcatel-Lucent Technical Practices where you can find more information on the topic being discussed.

Warning Alerts you to instances where non-compliance could result in equipment damage or personal injury.

9

All Rights Reserved © Alcatel-Lucent 2010

Where you can get further information

1350OMS 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 1350OMS-PKT R 9.1.1 Operation - Page 9

About this Student Guide [cont.] 

Switch to notes view!

10 1350OMS 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 1350OMS-PKT R 9.1.1 Operation - Page 10

Self-assessment of Objectives Contract number :

 At the end of each Course title :  Please, return this Client (Company, Center) : Language : Switch

section you will be asked to fill this questionnaire sheet to the trainer at the end of the training Dates from :

to notes view!

Number of trainees :

to :

Location :

Surname, First name : Did you meet the following objectives ? Tick the corresponding box Please, return this sheet to the trainer at the end of the training Yes (or globally yes)

Instructional objectives

No (or globally no)

1350OMS-PKT Overview • Describe the 1350OMS PKT functions and the system architecture How to Logon • 11 Get started on 1350OMS PKT functions

All Rights Reserved © Alcatel-Lucent 2010

1350OMS 1350OMS-PKT R 9.1.1 Operation

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 All Rights Reserved © Alcatel-Lucent 2010 1350OMS-PKT R 9.1.1 Operation - Page 11

Comments

Self-assessment of Objectives [cont.] Switch to notes view! Yes (or Globally yes)

Instructional objectives

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 NML’s PM DB with the EML’s PM dB

12

All Rights Reserved © Alcatel-Lucent 2010

1350OMS 1350OMS-PKT R 9.1.1 Operation

Other comments



Thank you for your answers to this questionnaire

All Rights Reserved © Alcatel-Lucent 2010 1350OMS-PKT R 9.1.1 Operation - Page 12

Do not delete this graphic elements in here:

1—1

Section 1 Product Overview Module 1 Product Overview 3JK Issue 1.00

1350OMS 1350OMS-PKT R 9.1.1 Operation TOS63013-R.9.1.1-SG1-SEN-I1.0 Issue 1.00

All Rights Reserved © Alcatel-Lucent 2010

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 1 — Module 1 — Page 1

Blank Page

1—1—2

All Rights Reserved © Alcatel-Lucent 2010

Product Overview — Product Overview 1350OMS — 1350OMS-PKT R 9.1.1 Operation

This page is left blank intentionally

Document History Edition

Date

Author

Remarks

01

2010-02-26

Buono Giovanni

First edition

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 1 — Module 1 — Page 2

Module Objectives Upon completion of this module, you should be able to:  Describe the 1350OMS PKT functions and the system architecture

1—1—3

All Rights Reserved © Alcatel-Lucent 2010

Product Overview — Product Overview 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 1 — Module 1 — Page 3

Module Objectives [cont.]

1—1—4 Product Overview — Product Overview 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 1 — Module 1 — Page 4

Table of Contents Page

Switch to notes view! 1 1350OMS product and its applications 2 1350OMS-PKT Ethernet functions overview

1—1—5

All Rights Reserved © Alcatel-Lucent 2010

Product Overview — Product Overview 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 1 — Module 1 — Page 5

7 11

Table of Contents [cont.] Switch to notes view!

1—1—6 Product Overview — Product Overview 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 1 — Module 1 — Page 6

1 1350OMS product and its applications

1—1—7

All Rights Reserved © Alcatel-Lucent 2010

Product Overview — Product Overview 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 1 — Module 1 — Page 7

1 1350OMS product and its applications

TMN description

Open Interfaces ASCII, TMF MTNM MTOSI

Common HW platform HP Server and Linux PC Common desktop, login and security

Common GUI & maps

Common Fault Management

Common PM

All technologies

SERVICE MANAGEMENT

PACKET NETWORK MANAGEMENT

SDH

SONET WDM

ELEMENT MANAGEMENT

Alcatel-Lucent Alcatel-Lucent Network Network (ETSI, Ethernet, (ETSI, Ethernet,WDM WDMand andSONET SONET 1—1—8

All Rights Reserved © Alcatel-Lucent 2010

Product Overview — Product Overview 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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".

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 1 — Module 1 — Page 8

1 1350OMS product and its applications

Subsystems description

PKT ETH, TMPLS Ntw.Mng TDM Ntw.Mng

WDM Ntw.Mng Element Mng

1350OMS -Open Interfaces Standard & Classic

ETH Services

1350OMS -PKT

1350OMS -SONET

SONET/PDH Services

1350OMS -WDM

1350OMS -High Availability 1350OMS -SDH

SDH/PDH Services

1350OMS -eOMS

WDM Services

1350OMS-EML Sub-network management Client/Server Relationship

Alcatel-Lucent Alcatel-Lucent Network Network (ETSI, Ethernet, (ETSI, Ethernet,WDM WDMand andSONET SONET 1—1—9

All Rights Reserved © Alcatel-Lucent 2010

Product Overview — Product Overview 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 1 — Module 1 — Page 9

Blank Page

1 — 1 — 10

All Rights Reserved © Alcatel-Lucent 2010

Product Overview — Product Overview 1350OMS — 1350OMS-PKT R 9.1.1 Operation

This All page Rights is Reserved left blank © Alcatel-Lucent intentionally 2010 3JK Issue 1.00 Section 1 — Module 1 — Page 10

2 1350OMS-PKT Ethernet functions overview

1 — 1 — 11

All Rights Reserved © Alcatel-Lucent 2010

Product Overview — Product Overview 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 1 — Module 1 — Page 11

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).

1 — 1 — 12

All Rights Reserved © Alcatel-Lucent 2010

Product Overview — Product Overview 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 1 — Module 1 — Page 12

2 1350OMS-PKT Ethernet functions overview

Telecommunication Network overview

Metro Core T-MPLS Metro Edge GFP over SDH

1 — 1 — 13

Metro Edge GFP over WDM

All Rights Reserved © Alcatel-Lucent 2010

Product Overview — Product Overview 1350OMS — 1350OMS-PKT R 9.1.1 Operation

The picture summarizes the Network architecture supporting Ethernet Service.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 1 — Module 1 — Page 13

2 1350OMS-PKT Ethernet functions overview

Telecommunication Network overview [cont.] T-MPLS

P2P

Data

Data

Data

Data

Data

Data

Ethernet

Ethernet

Ethernet

Ethernet

Ethernet

Ethernet

GFP

T-MPLS

T-MPLS

T-MPLS

SDH

T-MPLS

T-MPLS

T-MPLS

Ethernet

Ethernet

SDH

OMSN including ISA unit supporting GFP

1 — 1 — 14

NE supporting T-MPLS All Rights Reserved © Alcatel-Lucent 2010

Product Overview — Product Overview 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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 TMPLS label added by the edge NE.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 1 — Module 1 — Page 14

2 1350OMS-PKT Ethernet functions overview

Network construction and Ethernet service provisioning 

The Alcatel 1350OMS PKT provides Ethernet connectivity services; the main management areas are: 

Network construction (Constructor)   



1350OMS PKT

T-MPLS management (T-Mpls)    



Sub-network management NE and ENE management Transport Links management Transport link management Tunnel management PseudoWire management QoS management

Traffic management (Services)    

Customer / Ethernet service management EVC / Ethernet segment management VLAN management Policy control

1 — 1 — 15

All Rights Reserved © Alcatel-Lucent 2010

Product Overview — Product Overview 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 1 — Module 1 — Page 15

Ethernet service GFP & T-MPLS SDH / WDM network

2 1350OMS-PKT Ethernet functions overview

Network maintenance and PKT administration



Network Maintenance & Utility  Alarm records management  Fault localization  Audit and alignment



Fast Ethernet

PKT administration  Operators management  Process monitoring

 Application backup / restore 1 — 1 — 16

All Rights Reserved © Alcatel-Lucent 2010

Product Overview — Product Overview 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 1 — Module 1 — Page 16

End of Module Product Overview

1 — 1 — 17

All Rights Reserved © Alcatel-Lucent 2010

Product Overview — Product Overview 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 1 — Module 1 — Page 17

Do not delete this graphic elements in here:

2—1

Section 2 Graphical Interfaces Module 1 How to Logon 3JK Issue 1.00

1350OMS 1350OMS-PKT R 9.1.1 Operation TOS63013-R.9.1.1-SG1-SEN-I1.0 Issue 1.00

All Rights Reserved © Alcatel-Lucent 2010

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 1 — Page 1

Blank Page

2—1—2

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — How to Logon 1350OMS — 1350OMS-PKT R 9.1.1 Operation

This page is left blank intentionally

Document History Edition

Date

Author

Remarks

01

2010-02-26

Buono Giovanni

First edition

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 1 — Page 2

Module Objectives Upon completion of this module, you should be able to:  get started on 1350OMS PKT functions

2—1—3

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — How to Logon 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 1 — Page 3

Module Objectives [cont.]

2—1—4 Graphical Interfaces — How to Logon 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 1 — Page 4

Table of Contents Page

Switch to notes view! 1 Access to PKT application

2—1—5

7

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — How to Logon 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 1 — Page 5

Table of Contents [cont.] Switch to notes view!

2—1—6 Graphical Interfaces — How to Logon 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 1 — Page 6

1 Access to PKT application

2—1—7

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — How to Logon 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 1 — Page 7

1 Access to PKT applications

MS-GUI main menu 

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. 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.

2—1—8

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — How to Logon 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 1 — Page 8

1 Access to PKT applications

Search menu 

By the Search menu the user can retrieve lists of PKT DB network objects.

2—1—9

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — How to Logon 1350OMS — 1350OMS-PKT R 9.1.1 Operation

N.B: MPLS and OAM CC applications are not supported in current release

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 1 — Page 9

1 Access to PKT applications

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 3. Click on “OK” 2. Set the Filter conditions

2 — 1 — 10

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — How to Logon 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 1 — Page 10

1 Access to PKT applications

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.

2 — 1 — 11

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — How to Logon 1350OMS — 1350OMS-PKT R 9.1.1 Operation

N.B: MPLS and OAM CC applications are not supported in current release

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 1 — Page 11

End of Module How to Logon

2 — 1 — 12

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — How to Logon 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 1 — Page 12

Do not delete this graphic elements in here:

2—2

Section 2 Graphical Interfaces Module 2 Network Topology 3JK Issue 1.00

1350OMS 1350OMS-PKT R 9.1.1 Operation TOS63013-R.9.1.1-SG1-SEN-I1.0 Issue 1.00

All Rights Reserved © Alcatel-Lucent 2010

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 1

Blank Page

2—2—2

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

This page is left blank intentionally

Document History Edition

Date

Author

Remarks

01

2010-02-26

Buono Giovanni

First edition

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 2

Module Objectives Upon completion of this module, you should be able to:  Create and modify a network topology made of Service Nodes, NEs and ENEs

2—2—3

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 3

Module Objectives [cont.]

2—2—4 Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 4

Table of Contents Page

Switch to notes view! 1 Network Elements and Nodes management 2 External Network Element management 3 Link Aggregation (LAG) management

2—2—5

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 5

7 35 45

Table of Contents [cont.] Switch to notes view!

2—2—6 Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 6

1 Network Elements and Nodes management

2—2—7

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 7

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

2—2—8

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 8

1 Network Elements and Nodes management

Definitions [cont.] 

Transport Link definition:  Provides a description of the infrastructure of the Ethernet; Transport Link can be:     



Link Link Link Link Link

Over Over Over Over Over

TDM (using SDH or SONET technologies) Cable WDM MPLS/T-MPLS 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

2—2—9

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 9

1 Network Elements and Nodes management

Construction application and related components 

Management overview Display available NE

Create Domain

Add NE Create ENE Add ENE to a Domain Create ETP

Create NE

Add NE to a Domain

Upload Ethernet physical ports

Configure Ethernet physical ports

Add physical port to a Domain

Configure TDM Link

Upload TDM terminations Add TDM Link to a Domain

2 — 2 — 10

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 10

1 Network Elements and Nodes management

Domain list 

To display the Domain list : 1) Search  Packet  Construction  Domains

2 — 2 — 11

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 11

1 Network Elements and Nodes management

Domain creation 

To create a new Domain: 1) Actions  Packet  Construction  Create Domain

2 — 2 — 12

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 12

1 Network Elements and Nodes management

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: 1) Select a Domain in list 2) Actions (or right mouse button)  Modify



To delete a Domain : 1) Select a Domain in list 2) Actions  Domain  Delete

2 — 2 — 13

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

It is possible to modify: 

Domain User Label



Comment

The Domain List is updated

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 13

1 Network Elements and Nodes management

Network Element list 

To display the Network Elements list : 1) Search  Packet  Construction  Network Elements  Defined NEs

2 — 2 — 14

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

“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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 14

1 Network Elements and Nodes management

Network Element discovery 

To discover the Available Network Elements : 1) Search  Packet  Construction  Network Elements  Available NEs

2 — 2 — 15

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 15

1 Network Elements and Nodes management

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

2 — 2 — 16

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 16

1 Network Elements and Nodes management

Network Element creation [cont.] 2. Select a NE in the list

4. Set the related options

3. Click here to confirm the selection

5. Click on Apply

2 — 2 — 17

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation



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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 17

1 Network Elements and Nodes management

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

2 — 2 — 18

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 18

1 Network Elements and Nodes management

Network Element properties, modification and deletion 

To get the Network Element Properties: 1) Select a Network Element in list 2) Actions (or right mouse button)  Properties



To modify the Network Element Parameters: 1) Select a Network Element in list 2) Actions (or right mouse button)  Modify



To delete a Network Element : 1) Select a Network Element in list 2) Actions  Network Element  Delete

2 — 2 — 19

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 19

1 Network Elements and Nodes management

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: 1) Select a Network Element in list 2) Actions  Network Element  Assign Network Element to Domain 2. Select a Domain in the list, and confirm with the icon

1. Click here to display the Domain list

3. Click on Apply 2 — 2 — 20

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 20

1 Network Elements and Nodes management

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 : 1) Select a NE in the NE list 2) Search  Network Element  Ethernet Physical Ports

2 — 2 — 21

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 21

1 Network Elements and Nodes management

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

2 — 2 — 22

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 22

1 Network Elements and Nodes management

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

2 — 2 — 23

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 23

1 Network Elements and Nodes management

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 1. Click here to display the Domain list

2. Select a Domain in the list, and confirm with the icon

2 — 2 — 24

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 24

1 Network Elements and Nodes management

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”

2 — 2 — 25

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 25

1 Network Elements and Nodes management

Ethernet physical port properties 

To get the Ethernet physical port properties : 1) Select a port in Ethernet physical port list 2) Actions  Properties

2 — 2 — 26

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 26

1 Network Elements and Nodes management

TDM Termination upload and display 

To upload the TDM Terminations: 1) Select a NE in the NE list 2) Actions  Network Element  Upload TDM Terminations



To display the TDM Terminations : 1) Select a NE in the NE list 2) Search  Search from Network Element  TDM Termination list

2 — 2 — 27

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 27

1 Network Elements and Nodes management

TDM Termination properties 

To get the TDM Terminations properties : 1) Select a TDM Termination in the list 2) Actions  Properties

2 — 2 — 28

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 28

1 Network Elements and Nodes management

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



Misalignment ?

TDM

PKT EML

The operator can acknowledge at any time

NE MIB

OMSN with ISA board 2 — 2 — 29

1320 CT

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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 PostGranted In this state the operator can “acknowledge” the possible misalignment between the PKT and the NE due to a possible modification from the 1320CT.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 29

1 Network Elements and Nodes management

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

2 — 2 — 30

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 30

1 Network Elements and Nodes management

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

2 — 2 — 31

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 31

1 Network Elements and Nodes management

Node Inventory list 

To display the Node inventory list : 1) Select one or several Node in the list 2) Search  Node  Network Element List

2 — 2 — 32

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

It opens the NE list with the NE belonging to the selected service node.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 32

1 Network Elements and Nodes management

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

2 — 2 — 33

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 33

Blank Page

2 — 2 — 34

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

This All page Rights is Reserved left blank © Alcatel-Lucent intentionally 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 34

2 External Network Element management

2 — 2 — 35

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 35

2 External Network Element management

ENE Definition 

An External Network Element represents:  a Customer Edge Equipment (Customer Edge)  an Equipment into the network visible but not managed by the PKT (Inner Equipment)  An External Operator Network connected through IWI (Inter Working Interface) (PVLAN Network)

PVLAN Network

Inner Equipment

Customer Edge

2 — 2 — 36

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 36

2 External Network Element management

Broadcast TV ENE Definition 

A Broadcast TV External Network Element represents the SDH broadcasting ring in a Broadcast TV application

Broadcast TV

VIDEO SERVER

2 — 2 — 37

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 37

2 External Network Element management

External Network Element list 

To display the External Network Element list : 1) Search  Packet  Construction  Network Elements  External Network Element

2 — 2 — 38

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 38

2 External Network Element management

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

2 — 2 — 39

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 39

2 External Network Element management

ENE properties, modification and deletion 

To get the ENE Properties: 1) Select a ENE in list 2) Actions (or right mouse button)  Properties



To modify the ENE Parameters: 1) Select a ENE in list 2) Actions (or right mouse button)  Modify



To delete a ENE : 1) Select a ENE in list 2) Actions External Network Element  Delete

2 — 2 — 40

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 40

2 External Network Element management

External Termination Ports list 

To get the External Termination Ports list: 1) Select one ENE in the list 2) Search  External Network Element  ETPs

2 — 2 — 41

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All External Network Element are created with Manager Control attribute “Disabled”, that is suitable to use it as extremity of a Link Over cable.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 41

2 External Network Element management

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 Identifier to be assigned to the first added ETP Number of ETP to be added

2 — 2 — 42

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

- 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 ETP’s which can be created on a ENE

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 42

2 External Network Element management

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

1. Click here to display the Domain list

2. Select a Domain in the list, and confirm with the icon

2 — 2 — 43

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 43

2 External Network Element management

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

2 — 2 — 44

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 44

3 Link Aggregation (LAG) management

2 — 2 — 45

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 45

3 Link Aggregation (LAG) management

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) Aggregation Link

MAC Client

L A G

Physical MAC 1

Physical MAC 1

Physical MAC 2

Physical MAC 2

Physical MAC 3

Physical MAC 3

Aggregation Ports

2 — 2 — 46

L A G

MAC Client

Aggregation Ports

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation



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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 46

3 Link Aggregation (LAG) management

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)

2 — 2 — 47

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 47

3 Link Aggregation (LAG) management

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. LACPDU

L A G

Physical MAC 1

Physical MAC 1

Physical MAC 2

Physical MAC 2

Physical MAC 3

Physical MAC 3

LACPDU 2 — 2 — 48

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 48

L A G

3 Link Aggregation (LAG) management

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. 2. 3. 4. 5.

+ MPLS Labels + MPLS Labels + + MPLS Labels + ] + + MPLS Labels + ] + +

2 — 2 — 49

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 49

3 Link Aggregation (LAG) management

Example LAG size = 2  out of all the aggregated links, two are active and the rest are stand-by LAG#1

PR=1 1 NNI

4

PR=2

2

PR=3 3

LAG#2

Aggregate Link

UNI

UNI active

UNI

UNI active

UNI

UNI stand-by

NE A

1 PR=1 NNI

2

PR=2

4

3 PR=3 NE B

Port Priority = 1,2,3

2 — 2 — 50

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation



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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 50

3 Link Aggregation (LAG) management

Link Aggregation Group creation Enter the LAG size Enter the Client Type (ETS, ETB)

Enable (True) or Disable (False) the LACP

Enter the Hash Key

Select the NE and the load ports to assign members to the LAG

Set the Port Priority 2 — 2 — 51

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 51

3 Link Aggregation (LAG) management

GUI impact 

The Aggregated Logical Ports is suitable for any operation involving Ethernet physical port: Link Over Cable, EVC, etc.

Aggregated Logical port

2 — 2 — 52

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 52

3 Link Aggregation (LAG) management

Display ports member of a LAG 1. 2.

Select the LAG port in the list 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.

2 — 2 — 53

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 53

3 Link Aggregation (LAG) management

Modify a LAG port 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

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

2 — 2 — 54

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 54

3 Link Aggregation (LAG) management

Exercise 

On a Network Element, create a LAG port with following attributes:  LAG size = 2  Number of ports = 3

2 — 2 — 55

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 55

End of Module Network Topology

2 — 2 — 56

All Rights Reserved © Alcatel-Lucent 2010

Graphical Interfaces — Network Topology 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 2 — Module 2 — Page 56

Do not delete this graphic elements in here:

3—1

Section 3 System Operation Module 1 Transport link Provisioning 3JK Issue 1.00

1350OMS 1350OMS-PKT R 9.1.1 Operation TOS63013-R.9.1.1-SG1-SEN-I1.0 Issue 1.00

All Rights Reserved © Alcatel-Lucent 2010

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 1

Blank Page

3—1—2

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

This page is left blank intentionally

Document History Edition

Date

Author

Remarks

01

2010-02-26

Buono Giovanni

First edition

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 2

Module Objectives Upon completion of this module, you should be able to:  create and modify a Link over TDM, a Link over Cable; define the transport link characteristics.

3—1—3

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 3

Module Objectives [cont.]

3—1—4 System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 4

Table of Contents Page

Switch to notes view! 1 2 3 4

Transport Link Overview Link over TDM management Link over Cable management Inter-GUIs navigation

3—1—5

7 11 23 31

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 5

Table of Contents [cont.] Switch to notes view!

3—1—6 System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 6

1 Transport Link Overview

3—1—7

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 7

1 Transport Links overview

Transport links and Network Layering _ Operation 

Transport Link = infrastructure (TDM or WDM or Cable) used by MPLS/T-MPLS or Ethernet layers Network Layering

Customer Administrative mgt

Network Operation Model

Topology (EPL,EVPL,EPTL, EVPLAN, ….) Extremities, BW SLA & traffic classif.

Customer Ethernet

Service EVC

Per Traffic flow Routing

MPLS/T-MPLS

Segment SDH, SONET, WDM, CABLE

MPLS/T-MPLS layer

MPLS/T-MPLS layer for flow ident.

Transport

WDM, SDH, GFP, Ethernet / Martini cables

3—1—8

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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





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. 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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 8

1 Transport Links overview

Transport links and related applications

Link over WDM Ethernet layer

Link over Cable MPLS / T-MPLS layer Link over Cable Ethernet layer

Link over TDM Ethernet (GFP) layer

3—1—9

Link over TDM MPLS/T-MPLS layer All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 9

1 Transport Links overview

Transport Link types and related menu Link over TDM or WDM Ethernet layer

ENE’s

Link over Cable Ethernet layer

Network NE’s

Link over TDM with supported MPLS layer

LSP tunnel

Link over Cable with supported MPLS layer

VC LSP

Customer Ethernet Service

VC LSP

ENE’s Link over Cable/TDM with supported T-MPLS layer

MPLS T-MPLStunnel

Services

Construction 3 — 1 — 10

PW

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 10

2 Link over TDM management

3 — 1 — 11

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 11

2 Link over TDM management

1350OMS SDH/SONET and Packet interaction  

Application 1350OMS Packet : “Construction” Link between 2 TDM Terminations in Packet = Link between 2 NAPs in SDH / SONET

Customer Service EVC Segment

Nodes & NAPs A Z

SDH

EML layer

CDN

NE Terminations A Z

Packet

OMSN NEs - ISA NEs - 1850TSS

3 — 1 — 12

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 12

MPLS/T-MPLS layer

Transport

2 Link over TDM management

Link over TDM list 

To display the Link Over TDM list : 1) Search  Packet  Construction  Transport Links  Link Over TDM (Sdh/Sonet)

Customer Service EVC Segment MPLS/T-MPLS layer

Transport

3 — 1 — 13

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 13

2 Link over TDM management

Reminder 1/4 : 10 – 100 Mb Rate adaptive path Select Ethernet for service Type

Select 10-100 Rate Adaptive Select Transport rate: TU12/TU3/AU4/TU12-nV/TU3-nV Auto-negotiation: automatic (enabled) 10Mb manual (disabled) 10Mb automatic (enabled) 100Mb manual (disabled) 100Mb

Select the total concatenation level

Click on Next

3 — 1 — 14

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

The Auto-Negotiation setting can be changed further.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 14

2 Link over TDM management

Reminder 2/4 : 10 – 100 Mb Rate adaptive path

Select the Extremities of the Path

Click on Next

3 — 1 — 15

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 15

2 Link over TDM management

Reminder 3/4 : 10 – 100 Mb Rate adaptive path

Complete the configuration (refer to 1350OMS-SDH User Guide for details)

Click on Apply to confirm

3 — 1 — 16

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 16

2 Link over TDM management

Reminder 4/4 : 1Gb/10Gb Rate adaptive path Select Ethernet for service Type

Select 1G or 10G Rate Adaptive Select Transport rate: (see Notes)

Auto-negotiation: (only available for 1Gb) Automatic (enabled) Manual (disabled)

Select the total concatenation level Click on Next and proceed in the configuration

3 — 1 — 17

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 17

2 Link over TDM management

Link over TDM configuration 

To configure a Link over TDM: 1) 2) 3)

From Link Over TDM List, select a Link Action  Link Over SDH  Configure According to the boards, can be set: Supported Layer Protocol Type

3 — 1 — 18

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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)

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 18

2 Link over TDM management

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

1. Click here to display the Domain list

2. Select a Domain in the list, and confirm with the icon

3 — 1 — 19

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 19

2 Link over TDM management

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

3 — 1 — 20

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 20

2 Link over TDM management

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: 1) Select a Link in list 2) Action (or right mouse button)  Modify (only “User Label” and “Comment” can be modified)

3 — 1 — 21

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 21

2 Link over TDM management

Exercise 

Between two NEs managed by the SDH, according to the Classroom setup:  create an SDH path with an Ethernet supported layer

3 — 1 — 22

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 22

3 Link over Cable management

3 — 1 — 23

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 23

3 Link over Cable management

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

3 — 1 — 24

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 24

Customer Service EVC Segment MPLS/T-MPLS layer

Transport

3 Link over Cable management

Link over Cable creation 

To create a Link Over Cable : Actions  Packet  Construction  Create Link Over cable 1. Enter “User Label” and “Comment” 2. Click here to display the available NE list

3 — 1 — 25

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 25

3 Link over Cable management

Link over Cable creation [cont.] 3. Select a NE in the list

6. Assign the second extremity of the Link

4. Click here to confirm the selection

5. Click here and select a Port in the list

3 — 1 — 26

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 26

3 Link over Cable management

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

1. Click here to display the Domain list

2. Select a Domain in the list, and confirm with the icon

3 — 1 — 27

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 27

3 Link over Cable management

Link over Cable properties, modification and deletion 

To get the Link Over Cable Properties: 1) Select a Link in list 2) Actions (or right mouse button)  Properties



To modify the Link Over Cable Parameters: 1) Select a Link in list 2) Actions (or right mouse button)  Modify (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)

3 — 1 — 28

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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 TMPLS 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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 28

3 Link over Cable management

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

3 — 1 — 29

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 29

Blank Page

3 — 1 — 30

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

This All page Rights is Reserved left blank © Alcatel-Lucent intentionally 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 30

4 Inter-GUIs navigation

3 — 1 — 31

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 31

4 Inter-GUIs navigation

Navigation towards Services environment 

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  (i.e. ETS Transport Link)

Construction USM

Example:

Services USM

3 — 1 — 32

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 32

4 Inter-GUIs navigation

Navigation towards T-MPLS environment 1) Select a Transport Link in the relative list (i.e: Link over Cable, ...) 2) Search  Link over .....  Show  (i.e. T-MPLS Section)

Construction USM

Example:

T-MPLS USM

3 — 1 — 33

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 33

4 Inter-GUIs navigation

Exercise 

Practice the navigation from the previously created links :  Over TDM or Cable  ETS or Bridge or T-MPLS layers

3 — 1 — 34

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 34

End of Module Transport link Provisioning

3 — 1 — 35

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Transport link Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 1 — Page 35

Do not delete this graphic elements in here:

3—2

Section 3 System Operation Module 2 Traffic descriptor Provisioning 3JK Issue 1.00

1350OMS 1350OMS-PKT R 9.1.1 Operation TOS63013-R.9.1.1-SG1-SEN-I1.0 Issue 1.00

All Rights Reserved © Alcatel-Lucent 2010

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 1

Blank Page

3—2—2

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

This page is left blank intentionally

Document History Edition

Date

Author

Remarks

01

2010-02-26

Buono Giovanni

First edition

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 2

Module Objectives Upon completion of this module, you should be able to:  manage a Traffic Classifier, a VLAN Type, a Color Profile  manage the Traffic Descriptors for Ethernet segment

3—2—3

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 3

Module Objectives [cont.]

3—2—4 System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 4

Table of Contents Page

Switch to notes view! 1 2 3 4

Traffic classifier management VLAN Types management Color profile management Ethernet Traffic descriptor management

3—2—5

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 5

7 23 31 41

Table of Contents [cont.] Switch to notes view!

3—2—6 System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 6

1 Traffic classifier management

3—2—7

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 7

1 Traffic classifier management

Ethernet frame IEEE 802.3 _ Reminder Ethernet frames Preamble

Destination MAC Address

Source MAC Address

8

6

6

Type or Data FCS Length 2

-

4

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

3—2—8

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

OO

OUI 20

OUI

60

00

Node identifier 0A

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 All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 8

9F



1 Traffic classifier management

VLAN definition _ Reminder VLAN Tagged Ethernet frames



Role of Switch and Routers in VLANs

Router

VLAN Group #1

VLAN Group #2

Switch

Switch

Access control between VLANs Switch

3—2—9

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 9

1 Traffic classifier management

“Tagged” Ethernet frames IEEE 802.1P / Q _ Reminder Q- Tagged Ethernet frames





Preamble

Destination MAC Address

Source MAC Address

1Q

TCI

8

6

6

2

2



Type or Data FCS Length 2

-

4

Number of bytes

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   

3 bits: user priority 802.1P (8 levels: from 0 to 7) 1 bit: CFI (Canonical Field Identifier) 12 bits: VLAN identifier 802.1Q (0 to 4095)

3 — 2 — 10

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

Hereafter, an example giving the relation between the priority levels and the customer applications:

Priority

Class

Traffic Type

7

High

Network Control

6

“Voice”, < 10ms Latency and Jitter

5

“Video”, < 100ms Latency and Jitter

4

Controlled Load

3

Excellent Effort

2

Best Effort

1

Reserved - less than best-effort

0

Low

Background

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 10

1 Traffic classifier management

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 Voice Packet Stream

Time Fixed link speed

Time Data Packet Stream 3 — 2 — 11

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 11

1 Traffic classifier management

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

DSCP Ipv4 header fragment

3 — 2 — 12

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

DSCP = Differentiated Service Code Point CU = Currently Unused

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 12

7 CU

1 Traffic classifier management

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 don’t perform that kind of translation, the NE functionalities have been extended to IP DSCP management

Router

Access control between VLANs

3 — 2 — 13

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 13

1 Traffic classifier management

Traffic Classifier definition 

Customer

Role of the Traffic Classifier :

Service

Core Network

EVC Segment

Edge

Edge

MPLS/T-MPLS layer

Transport

Traffic frames

Traffic frames

 Frames are Identified (by port / VLAN/EtherType)

 are

 Frames are switched depending on priority

Classified by priority level

are Tagged according classification criteria 3 — 2 — 14

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 14

1 Traffic classifier management

Traffic Classifier location OMSN SDH Matrix ES Unit

Link over SDH SDH Path

Classifier

Policer Forwarding Scheduler Mapping

Header

CIR

Ports ?

PIR

+

=

SDH upper layers

SD SD HH

De-mapping =

Control processing unit NAP SDH Term.

Ethernet Port 3 — 2 — 15

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 15

1 Traffic classifier management

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.

3 — 2 — 16

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 16

1 Traffic classifier management

Traffic Classifier management chain 

Customer

Application 1350OMS Packet Services :

Service

 Traffic classifier management chain:

EVC Segment MPLS/T-MPLS layer

Create Traffic Classifier

Delete Traffic Classifier

Modify Traffic Classifier

Associate to Ethernet segment

3 — 2 — 17

Disassociate from Ethernet segment

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 17

Transport

1 Traffic classifier management

Traffic Classifier list 

To display the Traffic Classifier list: Search Packet Services Traffic Classifiers

3 — 2 — 18

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

Three Traffic Classifier (……_FixedClassifier_1,2,3), with VLAN Id = Don’t Care (4097) and Priority Id = Don’t Care, are created by default during the 1354BM installation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 18

1 Traffic classifier management

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

3 — 2 — 19

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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 “Don’t 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)

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 19

1 Traffic classifier management

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

3 — 2 — 20

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 20

1 Traffic classifier management

Traffic Classifier properties and deletion To

get the Traffic Classifier properties:

1) Select a Traffic Classifier in the list 2) Actions Properties To

delete the Traffic Classifiers :

1) Select one or several Traffic Classifiers in the list 2) Actions Traffic Classifier Delete 3) Confirm

3 — 2 — 21

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 21

1 Traffic classifier management

Exercise   

Create a set of Traffic Classifiers, using different classification criteria Modify at least one Traffic Classifier Delete several Traffic Classifiers

3 — 2 — 22

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 22

2 VLAN Types management

3 — 2 — 23

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 23

2 VLAN types management

Customer / Provider VLAN _ Frame formats Untagged Frame DA

SA

Length/Type

Data

FCS

(6 Byte)

(6 Byte)

(2 Byte)

(< 1500 Byte)

(4 Byte)

Q-tagged Frame DA

SA

Type (8100)

Q-VLAN Tag

Length/Type

Data

FCS

(6 Byte)

(6 Byte)

(2 Byte)

(2 Byte)

(2 Byte)

(< 1500 Byte)

(4 Byte)

S-tagged Frame DA

SA

Type (88a8)

S-VLAN Tag

Length/Type

Data

FCS

(6 Byte)

(6 Byte)

(2 Byte)

(2 Byte)

(2 Byte)

(< 1500 Byte)

(4 Byte)

Double tagged Frame DA

SA

Type (88a8)

S-VLAN Tag

Type (8100)

Q-VLAN Tag

Length/Type

Data

FCS

(6 Byte)

(6 Byte)

(2 Byte)

(2 Byte)

(2 Byte)

(2 Byte)

(2 Byte)

(< 1500 Byte)

(4 Byte)

3 — 2 — 24

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 24

2 VLAN types management

VLAN Types management chain 

Customer

Application 1350OMS Packet Services :

Service

 VLAN type management chain:

EVC Segment MPLS/T-MPLS layer

Create VLAN type

Delete VLAN type

Modify VLAN type

Ethernet edge port association 3 — 2 — 25

Ethernet edge port disassociation All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 25

Transport

2 VLAN types management

VLAN Types list 

To display the VLAN types List : Search Packet Services VLANs

3 — 2 — 26

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 26

2 VLAN types management

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

3 — 2 — 27

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 27

2 VLAN types management

VLAN Type modification, properties, deletion To

modify a VLAN Type :

To

1) Select a VLAN type in the list 2) Actions Modify 3) Modification are possible for: User label VLAN type 4) Click on Ok

To

delete the VLAN types :

1) Select one or more VLAN Types in the list 2) Actions VLAN Delete 3) Confirm accordingly

get the VLAN Type properties:

1) Select a VLAN in the list 2) Actions Properties

3 — 2 — 28

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 28

2 VLAN types management

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

3 — 2 — 29

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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).

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 29

2 VLAN types management

Exercise  

Create a set of VLAN types Modify an Ethernet Edge port in order to take into account a created VLAN type.

3 — 2 — 30

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 30

3 Color profile management

3 — 2 — 31

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 31

3 Color profile management

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:

Service EVC Segment MPLS/T-MPLS layer

Transport

User priority VLAN (802.1p)

Provider priority “Color profile”

7

Green

6

Green

3 — 2 — 32

Customer

5

Green

4

Yellow

3

Yellow

2

Yellow

1

Red

0

Red All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 32

3 Color profile management

Color Profile definition _ Reminder [cont.] OMSN SDH Matrix ES Unit

Link over SDH SDH Path

Classifier

Policer Forwarding Scheduler Mapping

Header

CIR

Ports ?

PIR

+

=

SDH upper layers

SD SD HH

De-mapping =

Control processing unit NAP SDH Term.

Ethernet Port 3 — 2 — 33

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 33

3 Color profile management

Color Profile definition _ Reminder [cont.] Traffic Descriptor BEST EFFORT

Policing Mode

Color Profile (1) Provider-Colouring (2)

“disabled”

“Unbound”

YELLOW or RED

“color-blind” GUARANTEED

“disabled”

“Unbound”

GREEN GREEN or RED

“color-blind” REGULATED

YELLOW

“disabled”

“Unbound”

GREEN or YELLOW

“color-blind”

“Unbound”

“color-aware”

“Bound” (3)

GREEN or YELLOW or RED As assigned by the “ColorProfile and Policing effect

Unit configuration : Traffic Descriptor, Policing Mode and Color Profile for « INFLOW » resource 3 — 2 — 34

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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 “don’t care”.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 34

3 Color profile management

Color Profile management chain 

Customer

Application 1350OMS Packet Services :

Service

 Color Profile management chain:

EVC Segment MPLS/T-MPLS layer

Create Color Profile

Delete Color Profile

Modify Color profile

Ethernet segment “assignment” 3 — 2 — 35

Ethernet segment “de-assignment” All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 35

Transport

3 Color profile management

Color Profile list 

To display the Color Profile List : Search Packet Services Color Profiles

3 — 2 — 36

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

The list is displayed, where only the Color Profile Mode is shown; details about the color assignment can be get from the “properties” option

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 36

3 Color profile management

Color Profile creation To

create a Color Profile: 1) Actions Packet Services

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

3 — 2 — 37

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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)

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 37

3 Color profile management

Color Profile modification, properties, deletion To

modify a Color Profile:

To

1) Select a Color Profile in the list 2) Actions Modify 3) Modification are possible for: User label Color Profile Mode and/or the Color assignment 4) Click on Ok

To

delete the Color Profile:

1) Select one or more Color Profiles in the list 2) Actions Color Profile Delete 3) Confirm

get the Color Profile properties:

1) Select a Color Profile in the list 2) Actions (or right mouse button) Properties

3 — 2 — 38

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

A Color profile can be modified or deleted when: - it is not associated to a segment - it is associated to a Defined segment

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 38

3 Color profile management

Exercise  

Create a set of Color Profiles with different Color Priority Mode and different assignments Modify and delete a Color Profile

3 — 2 — 39

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 39

Blank Page

3 — 2 — 40

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

This All page Rights is Reserved left blank © Alcatel-Lucent intentionally 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 40

4 Ethernet Traffic descriptor management

3 — 2 — 41

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 41

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.

Customer Service EVC Segment MPLS/T-MPLS layer

Transport

End to End ETHERNET SERVICE

Customer 3 — 2 — 42

Customer All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 42

4 Ethernet Traffic descriptor management

Traffic descriptor definition _ Reminder [cont.] Bandwidth PIR

PIR

CIR=PIR

BE CIR CIR=0

Ethernet T-MPLS

GA

Best Effort

Guaranteed

Regulated

Best Effort

Expedited

Assured

Best Effort

TDM VC-nv Guaranteed

3 — 2 — 43

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 43

4 Ethernet Traffic descriptor management

Traffic descriptor management chain 

Application 1350OMS Packet Services :  Traffic descriptor management chain:

Create Traffic Descriptor

Delete Traffic Descriptor

Modify Traffic Descriptor

Associate to Ethernet segment

3 — 2 — 44

Disassociate from Ethernet segment

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 44

4 Ethernet Traffic descriptor management

Traffic descriptor list 

To display the Traffic Descriptor List : Search Packet Services Traffic Descriptors

3 — 2 — 45

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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)

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 45

4 Ethernet Traffic descriptor management

Traffic Descriptor Creation To

create a Traffic Descriptor: 1) Actions Packet Services

Create Traffic Descriptor 2) Enter : User label Class of Service Traffic parameter, according to the CoS 3) Click on Ok

3 — 2 — 46

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

Values

BE

GUARANTEED

REGULATED

CIR

0

(CIR = PIR) & (CIR > 0)

(CIR ≤ PIR ) & (CIR ≥ 0) If (CIR > 0), (CBS > 0) If (CIR = 0), (CBS = 0)

CBS

0

(CBS = PBS) & (CBS > 0)

(CBS ≥ 0) & (CBS ≤ PBS) If (CBS > 0), (CIR > 0) If (CBS = 0), (CIR = 0)

PIR

>0

(PIR = CIR) & (PIR > 0)

(PIR ≥ CIR ) & (PIR > 0)

PBS

>0

(PBS = CBS) & (PBS > 0)

(PBS > CBS) & (PBS ≥ 0)

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 46

4 Ethernet Traffic descriptor management

Traffic descriptor modification, properties, deletion 

To modify a Traffic descriptor: 1) Select a Traffic Descriptor in the list 2) Actions (or right mouse button) Modify 3) Modification are possible for: User label Class of Service Traffic parameters 4) Click on Ok



To

delete the Traffic descriptor:

1) Select one or more Traffic Descriptors in the list 2) Actions Traffic Descriptor Delete 3) Confirm

To get the Traffic Descriptor properties: 1) Select a Traffic Descriptor in the list 2) Actions (or right mouse button) Properties

3 — 2 — 47

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 47

4 Ethernet Traffic descriptor management

Exercise   

Create a set of Traffic descriptors Modify at least one Traffic descriptor Delete several Traffic descriptors

3 — 2 — 48

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 48

End of Module Traffic descriptor Provisioning

3 — 2 — 49

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Traffic descriptor Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 2 — Page 49

Do not delete this graphic elements in here:

3—3

Section 3 System Operation Module 3 Ethernet Service Provisioning 3JK Issue 1.00

1350OMS 1350OMS-PKT R 9.1.1 Operation TOS63013-R.9.1.1-SG1-SEN-I1.0 Issue 1.00

All Rights Reserved © Alcatel-Lucent 2010

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 1

Blank Page

3—3—2

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

This page is left blank intentionally

Document History Edition

Date

Author

Remarks

01

2010-02-26

Buono Giovanni

First edition

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 2

Module Objectives Upon completion of this module, you should be able to:  Manage the End to End Ethernet Services provisioning

3—3—3

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 3

Module Objectives [cont.]

3—3—4 System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 4

Table of Contents Page

Switch to notes view! 1 2 3 4 5 6 7

End to End Ethernet service concept Customer management Ethernet Service management Ethernet Service type Ethernet Virtual Connection management Ethernet Segment management Ethernet segment life cycle

3—3—5

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 5

7 17 21 25 33 47 65

Table of Contents [cont.] Page

Switch to notes view!

3—3—6

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 6

1 End to End Ethernet service concept

3—3—7

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 7

1 End to End Ethernet service concept

Global definition & provisioning steps  End

to End concept is spread over 4 levels :



Customer Service

Customer

Customer

EVC Segment

 Ethernet Service user  CPE equipment connected to the Network Ethernet Edge physical port



VC LSP LSP Tunnel

Ethernet Service

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



EVC

EVC

EVC

Ethernet Segment  Unidirectional connection between Ethernet Edge Ports, associated to Traffic descriptor and Traffic classifier

3—3—8

Ethernet Segments

Ethernet Segments

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 8

Ethernet Segments

Transport

1 End to End Ethernet service concept

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

Service EVC Segment

A contract is established between :

VC LSP

 a Customer and  an Operator

LSP Tunnel Transport

 to define an Ethernet Service

Customer

Operator

Ethernet Service

3—3—9

Customer

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 9

1 End to End Ethernet service concept

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

Customer Service EVC Segment VC LSP



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

3 — 3 — 10

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 10

LSP Tunnel Transport

1 End to End Ethernet service concept

Ethernet Virtual Connection (EVC) definition 

An Ethernet Virtual Connection (EVC) is an association of two or more Ethernet End points (UNI)

Customer Service EVC



Segment

EVC has :  A specified Service Type, which define the specific topology supported:

LSP Tunnel

 Point-to Point  Rooted MultiPoint  Any to Any

Transport

 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

3 — 3 — 11

VC LSP

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 11

1 End to End Ethernet service concept

Ethernet Segment definition 

An Ethernet Segment is an unidirectional connection between two Ethernet Edge physical ports, associated to :

Customer Service EVC Segment

 Quality of Service QoS :   

   

VC LSP

Guaranteed Best Effort Regulated

LSP Tunnel Transport

Bandwidth Traffic descriptor containing QoS information Traffic classifier containing forwarding rule information Color Profile, (when required)

3 — 3 — 12

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 12

1 End to End Ethernet service concept

Telecommunication Network overview OMSN - A

Segment A Z1 Segment Z2 B

Transport Link

Ethernet Edge Port A

OMSN - B

OMSN - Z

Ethernet Edge Port

Segment Z1 A

Transport Link

Ethernet Edge Port

Ethernet Edge Port

Z1

Z2 Z2 Segment B

VLAN - A

B

VLAN - B

Ethernet Service = Server Z  VLANs - A & B over a Point to Point topology 3 — 3 — 13

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 13

1 End to End Ethernet service concept

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)

3 — 3 — 14

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 14

1 End to End Ethernet service concept

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)

3 — 3 — 15

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 15

Blank Page

3 — 3 — 16

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

This All page Rights is Reserved left blank © Alcatel-Lucent intentionally 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 16

2 Customer management

3 — 3 — 17

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 17

2 Customer management

Customer list 

To display the Customer List, from the MS_GUI: Search  Packet  Services  Customers

Customer Service EVC Segment VC LSP LSP Tunnel Transport

3 — 3 — 18

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 18

2 Customer management

Customer creation 

To create a new Customer: 1) Actions  Packet  Services  Create Customer or 1) Display the Customer list 2) Actions  Create Customer

3 — 3 — 19

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

To Create a customer: Enter a User label Enter a Address (optional) Enter a Company (optional) Enter a Comment (optional)

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 19

2 Customer management

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: 1) Select a Customer in list 2) Actions ( or right mouse button)  Modify



To delete an Customer : 1) Select a Customer in list 2) Actions  Customer  Delete

3 — 3 — 20

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

N.B: A Customer can be deleted if no more Service are related to.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 20

3 Ethernet Service management

3 — 3 — 21

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 21

3 Ethernet Service management

Ethernet Service list 

To display the Ethernet Servicer List, from the MS_GUI: Search  Packet  Services  Services

Customer Service EVC Segment VC LSP LSP Tunnel Transport

3 — 3 — 22

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

Service State is set to “In Service “ when all associated EVCs are “In Service”

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 22

3 Ethernet Service management

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: 1) Actions  Packet  Services  Create Ethernet Service

3 — 3 — 23

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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 Enter a Comment (optional)

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 23

3 Ethernet Service management

Ethernet Service properties, modification and deletion 

To get the Service Properties: 1) Select a Service in list 2) Actions (or right mouse button)  Properties



To modify the Service Parameters: 1) Select a Service in list 2) Actions (or right mouse button)  Modify



To delete a Service : 1) Select a Service in list 2) Actions  Service  Delete

3 — 3 — 24

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

N.B: A Service can be deleted if no more EVC are related to.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 24

4 Ethernet Service type

3 — 3 — 25

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 25

4 Ethernet Service type

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

3 — 3 — 26

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 26

4 Ethernet Service type

Definition [cont.] 

Services Type and EVCs connection type relationships

EVPL EPTL EPL

EVPLAN

EVC Point to Point (support Unicast traffics)

EVC Any to Any (support Unicast traffics)

3 — 3 — 27

HSI

BTV Broadcast

EVC Rooted MultiPoints (support Unicast traffics)

EVC Rooted MultiPoints (support Multicast traffics)

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 27

4 Ethernet Service type

EVPL/EPTL/EPL service 

Point to point_EVC

Ethernet Customer Edge

B CE

A CE Ethernet Provider Edge OMSN supporting Ethernet Service

3 — 3 — 28

OMSN supporting Ethernet service and T- MPLS

Server transport layer: SDH / DWDM / RPR or MPLS

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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)  Support Unicast Service  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 :  Support Unicast Service  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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 28

4 Ethernet Service type

EVPLAN service 

Full Meshed EVPLAN CE

CE A3

B

CE

C F

A0 CE

CE A2 OMSN supporting Ethernet Service

3 — 3 — 29

A1 CE

CE

E

CE

D

CE

OMSN supporting Ethernet service and T- MPLS

Server transport layer: SDH / DWDM / RPR or MPLS

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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 :  Support Unicast Service  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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 29

4 Ethernet Service type

HSI/BTV/BROADCAST service 

HUB & Spoke

CE B

CE C

Main Site

F CE

A CE

ISP

CE E OMSN supporting Ethernet Service

3 — 3 — 30

CE D

OMSN supporting Ethernet service and T- MPLS

Server transport layer: SDH / DWDM / RPR or MPLS/T-MPLS

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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:  Support Unicast Service  Full resource sharing can be used (see “Resource reservation” for details)  One or more EVC are allowed whit this type of Service  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)  One or more EVC are allowed whit this type of Service  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)  One or more EVC are allowed whit this type of Service

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 30

4 Ethernet Service type

Resource Reservation concept

UNI



A

Transport Link

A

UNI

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

3 — 3 — 31

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 31

4 Ethernet Service type

Resource Reservation combination Resource Sharing Full EVPL

ETS Bridge T-MPLS

Private Link

Private UNI ETS Bridge T-MPLS

ETS Bridge T-MPLS

Service Type

EPTL

HSI BTV Broadcast 3 — 3 — 32

ETS Bridge T-MPLS ETS

ETS Provider Bridge T-MPLS

EPL EVPLAN

Private UNI and Link

ETS Bridge T-MPLS ETS Bridge T-MPLS ETS Provider Bridge T-MPLS

ETS Bridge T-MPLS

ETS

ETS

ETS Bridge T-MPLS

ETS Bridge T-MPLS

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

The table above reports the possible chooses of Resource Sharing respect to the Service Type and respect to crossed technological domain

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 32

5 Ethernet Virtual Connection management

3 — 3 — 33

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 33

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

Customer Service EVC Segment VC LSP



An EVC have a specified topology : 

Point-to-Point (PtoP) : 





Transport

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 bidirectional / for multicast traffic, unidirectional

Any to Any (MPtoMP) : 

Connection between 2 or more points / unicast traffic bi-directional only

3 — 3 — 34

LSP Tunnel

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 34

5 Ethernet Virtual Connection management

Definition [cont.] 

EVCs and Ethernet End Points relationships In PtoP (green), bi-directional topology : B,E=Peer (Root+Leaf)

MPtoMP

PtoMP B

In PtoMP (red), unidir. / bidir. topology A=Root B,C,D=Leaf

Leaf

Peer

Peer

C Root A

In MPtoMP (blue), bidirectional topology C,D,E= Peer (Root+Leaf)

Leaf

Peer

PtoP

3 — 3 — 35

Peer

Peer Leaf E

D

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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;

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 35

5 Ethernet Virtual Connection management

Connection-Oriented EVC list 

To display the Connection Oriented EVC List, from the MS_GUI: Search  Packet  Services  Connection Oriented  ETS EVCs

3 — 3 — 36

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 36

5 Ethernet Virtual Connection management

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

3 — 3 — 37

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 37

5 Ethernet Virtual Connection management

Connection Oriented EVC creation: Detail tab Details panel:



3 — 3 — 38

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 38

5 Ethernet Virtual Connection management

Connection Oriented EVC creation: PM tab 

PM panel:

Set “True” to enable PM. (Refer to specific session for details)

3 — 3 — 39

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 39

5 Ethernet Virtual Connection management

Connection Oriented EVC creation: Miscellaneus tab 

Miscellaneus panel:

Click on Next to continue

3 — 3 — 40

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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)

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 40

5 Ethernet Virtual Connection management

Termination selection for Point to Point service For “Point to Point” topology a window to insert two edge ports is open

Choose NE and Edge ports as terminations

Click on Next to continue

3 — 3 — 41

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

N.B: Edge port are listed if previously assigned to a Connection Oriented domain

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 41

5 Ethernet Virtual Connection management

Termination selection for Multi-Point service For “Rooted Multipoint” or “Any to Any” topology a window to insert multiple edge ports is open

Choose NE and Edge ports as terminations

Click on Next to continue

3 — 3 — 42

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

N.B: Edge port are listed if previously assigned to a Connection Oriented domain The operator must select the physical edge port and assign a termination role (“Peer” or “Root” or “Leaf”).

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 42

5 Ethernet Virtual Connection management

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 3 — 3 — 43

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

By setting “Create Ethernet Segment = True” two segments, one for each direction, are automatically created, with 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)

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 43

5 Ethernet Virtual Connection management

EVC properties, modification and deletion 

To get the EVC Properties: 1) Select an EVC in list 2) Actions (or right mouse button)  Properties



To modify the EVC Parameters: 1) Select an EVC in list 2) Actions (or right mouse button)  Modify



To delete an EVC : 1) Select an EVC in list 2) Actions  ETS EVC  Delete

3 — 3 — 44

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

N.B: An EVC can be deleted if the provisioning state is “Defined”

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 44

5 Ethernet Virtual Connection management

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)

3 — 3 — 45

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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).

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 45

5 Ethernet Virtual Connection management

EVC Commission / Decommission 

To commission the EVC: 1) Select one or several implemented EVC in the list 2) Actions  ETS EVC  Commission 3) Confirm accordingly



To decommission the EVC: 1) Select one or several commissioned EVC in the list 2) Actions ETS EVC  Decommission 3) Confirm accordingly

3 — 3 — 46

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

“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”

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 46

5 Ethernet Virtual Connection management

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

3 — 3 — 47

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 47

5 Ethernet Virtual Connection management

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

3 — 3 — 48

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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”).

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 48

5 Ethernet Virtual Connection management

EVC Termination properties and deletion 

To get the EVC Terminations properties: 1) Select an EVC Termination in the list 2) Actions (or right mouse button)  Properties



To delete an EVC Termination: 1) Select an EVC Termination in thelist 2) Actions  EVC Termination  Delete

3 — 3 — 49

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

N.B: An EVC Termination can be deleted if no segment are associated.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 49

Blank Page

3 — 3 — 50

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

This All page Rights is Reserved left blank © Alcatel-Lucent intentionally 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 50

6 Ethernet Segment management

3 — 3 — 51

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 51

6 Ethernet Segment management

Ethernet Segment definition Customer



An Ethernet Segment is an Unidirectional connection between two Ethernet Edge ports. 

Service EVC

“Enter in” and “Exit from” traffic ports

Ethernet Port

Ethernet Segment

Segment VC LSP

Ethernet Port

LSP Tunnel Transport



Guaranteed

Associated to:

 

Bandwidth Traffic descriptor containing QoS information Ethernet Traffic Classifier segments containing forwarding rule information Color Profile, in case of Color Aware Policy mode

3 — 3 — 52

Regulated

Transport Link

 

Best Effort

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 52

6 Ethernet Segment management

Ethernet Segment list 

To display the Ethernet Segment List, from the MS_GUI: Search  Packet  Services  Connection Oriented  Ethernet Segments

3 — 3 — 53

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 53

6 Ethernet Segment management

Ethernet Segment creation: General 

To create an Ethernet Segment: 1) Actions  Packet  Services  Connection Oriented  Create Ethernet Segment or 1) Select an EVC in the list 2) Action  ETS EVC  Create Ethernet Segment

Set the related options

Select the classification mode (Priority / DSCP)

3 — 3 — 54

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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. N.B: Edge port are listed if previously assigned to a Connection Oriented domain 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 select the Classification Mode (Priority, DSCP) The direction in the traffic delivering is from A-EvcPort_label to Z-EvcPort_label

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 54

6 Ethernet Segment management

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 Eth. Segment

Eth. Segment

AA

AA

Z

VLAN Pop

VLAN Push

3 — 3 — 55

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 55

ZZ

6 Ethernet Segment management

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

Classifier

Classifier

VLAN Pop

Click here to add a Classifier 3 — 3 — 56

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 56

6 Ethernet Segment management

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

3 — 3 — 57

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 57

6 Ethernet Segment management

Ethernet Segment properties and extremities 

To get the Ethernet Segment properties: 1) Select an Ethernet Segment in list 2) Actions  Properties



To get the Ethernet Segment extremities: 1) Select an Ethernet Segment in list 2) Actions  Ethernet Segment  Extremities

3 — 3 — 58

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 58

6 Ethernet Segment management

Ethernet Segment modification and deletion 

To modify the Ethernet Segment parameters: 1) Select an Ethernet Segment in list 2) Actions  Modify



To delete an Ethernet Segment : 1) Select an Ethernet Segment in list 2) Actions  Ethernet Segment  Delete

3 — 3 — 59

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

In order to modify Segment attributes or to delete the segment, the Provisioning State must be Defined or Allocated

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 59

6 Ethernet Segment management

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

3 — 3 — 60

Click here to remove a Classifier

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

The Ethernet segment provisioning state can be Defined, Allocated or Implemented More than one Traffic Classifier could be associated to an Ethernet segment

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 60

6 Ethernet Segment management

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) VLAN Push

VLAN Pop

Eth Seg#1

Eth Seg#2

3 — 3 — 61

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

The function consists in adding an allocation constraint to an Ethernet segment To add a constraint, the Ethernet segment « Provisioning state » must be “Defined”

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 61

6 Ethernet Segment management

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 Use this option to add VLAN Pop/Push action on NNI port of the Transport Link

Click here to display Transport Link list

3 — 3 — 62

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 62

6 Ethernet Segment management

Adding Vlan Pop/Vlan Push on an Ethernet Segment

In case of Vlan Pop management: click here to display Traffic Classifier list

Set “False” to enable Vlan Push

3 — 3 — 63

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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 - 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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 63

6 Ethernet Segment management

Ethernet Segment Constraints list 

To display the Ethernet Segment Constraints list : 1) Select an Ethernet Segment in the list 2) Search  Ethernet Segment  Constraints

3 — 3 — 64

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 64

6 Ethernet Segment management

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

3 — 3 — 65

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 65

6 Ethernet Segment management

Ethernet Segment Constraints properties and deletion 

To get the Ethernet Segment Constraint properties: 1) Select a Constraint in list 2) Actions  Properties



To delete an Ethernet Segment Constraint: 1) Select a Constraint in list 2) Actions  Constraint  Pkt_POP_deleteConstraint_label

3 — 3 — 66

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

To be able to delete a given constraint, the related Ethernet segment must be in Defined provisioning state.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 66

6 Ethernet Segment management

Ethernet Segment Configuration : Traffic Descriptor 

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



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)

Click here to display the available TD list

3 — 3 — 67

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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).

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 67

6 Ethernet Segment management

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

3 — 3 — 68

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 68

7 Ethernet segment life cycle

3 — 3 — 69

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 69

7 Ethernet Segment life cycle

Definition 

Ethernet Segment life cycle :

Customer Service EVC

Defined state

Segment VC LSP

Associate Constraints

Associate Traffic classifier

LSP Tunnel Transport

Allocate Implement

3 — 3 — 70

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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 crossconnections 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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 70

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

3 — 3 — 71

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 71

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

A

A

Link over SDH

3 — 3 — 72

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 72

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

A

A

B

B Link over SDH

A

B

Customer

3 — 3 — 73

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 73

End of Module Ethernet Service Provisioning

3 — 3 — 74

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Ethernet Service Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 3 — Page 74

Do not delete this graphic elements in here:

3—4

Section 3 System Operation Module 4 Bridge Provisioning 3JK Issue 1.00

1350OMS 1350OMS-PKT R 9.1.1 Operation TOS63013-R.9.1.1-SG1-SEN-I1.0 Issue 1.00

All Rights Reserved © Alcatel-Lucent 2010

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 1

Blank Page

3—4—2

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

This page is left blank intentionally

Document History Edition

Date

Author

Remarks

01

2010-02-26

Buono Giovanni

First edition

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 2

Module Objectives Upon completion of this module, you should be able to:  Manage the Bridge network provisioning

3—4—3

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 3

Module Objectives [cont.]

3—4—4 System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 4

Table of Contents Page

Switch to notes view! 1 2 3 4 5 6

Bridge Network concept Network Constructor and Bridge Infrastructure management Ethernet service management Connection-Less Ethernet Virtual Connection Spanning Tree Instance management Ethernet Virtual Connection life cycle

3—4—5

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 5

7 17 29 35 61 63

Table of Contents [cont.] Page

Switch to notes view!

3—4—6

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 6

1 Bridge Network concept

3—4—7

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 7

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

Bridge Infrastructure management

2.



Transport Link assignment

Bridge traffic management (EVC)

3.

    

EVC association to a bridge infrastructure EVC Termination addition Manual or automatic VLAN distribution inside Packet resources STP parameter set-up QoS management

3—4—8

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 8

1 Bridge network concept

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 UNI Interface

NNI Interface

UNI Interface NNI Interface

Bridge Domain ENE UNI Interface

3—4—9

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 9

1 Bridge network concept

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

ETS_P

Provider Bridge Domain

3 — 4 — 10

ETB

ETB

ETB

ETB ENE

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 10

ETS_P

1 Bridge network concept

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

3 — 4 — 11

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 11

1 Bridge network concept

Bridge Network overview (MAC and Virtual) OMSN - A

OMSN - B ISA - B

ISA - A L2 switching layer

Transport Link

L2 switching layer

Ethernet Edge Port

Ethernet Edge Port

A

B

VLAN - A

3 — 4 — 12

VLAN - B

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 12

1 Bridge network concept

Bridge Network overview (Provider) OMSN ISA

Transport Link

L2 switching layer

Ethernet Edge Port A

VLAN - A

3 — 4 — 13

Virtual Port Classification, Policing, Metering

S-Vlan PUSH

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 13

1 Bridge network concept

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)

3 — 4 — 14

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 14

1 Bridge network concept

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)

3 — 4 — 15

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 15

Blank Page

3 — 4 — 16

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

This All page Rights is Reserved left blank © Alcatel-Lucent intentionally 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 16

2 Network Constructor and Bridge Infrastructure management

3 — 4 — 17

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 17

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

3 — 4 — 18

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 18

2 Network Constructor and Bridge infrastructure management

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

3 — 4 — 19

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 19

2 Network Constructor and Bridge infrastructure management

Edge Port configuration 

This function permits to configure VLAN parameters of Bridge Edge port:



To configure an Edge Port: 1) From Bridge Edge Port list: select a Port 2) Actions  Bridge Edge Port  Configure Edge Port

3 — 4 — 20

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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 VLAN–ID 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)

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 20

2 Network Constructor and Bridge infrastructure management

Edge Port activation/deactivation 

This function activate (deactivate) edge port (set up/down) even if not used in a Service.



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”)

3 — 4 — 21

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 21

2 Network Constructor and Bridge infrastructure management

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

3 — 4 — 22

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 22

2 Network Constructor and Bridge infrastructure management

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

3 — 4 — 23

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 23

2 Network Constructor and Bridge infrastructure management

Transport Link configuration 

This function permits to configure VLAN parameters of transport link extremities



To configure a Transport Link: 1) From Bridge Transport Link list: select a Link 2) Actions  Bridge Transport Link  Configure Transport Link

3 — 4 — 24

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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 VLAN–ID 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)

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 24

2 Network Constructor and Bridge infrastructure management

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)

3 — 4 — 25

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 25

2 Network Constructor and Bridge infrastructure management

Priority Code Point Table Profile [cont.]

Operation Mode Class

5P3D

6P2D

7P1D

8P0D

Guaranteed

111 (7)

111 (7)

111 (7)

111 (7)

Guaranteed(2)

110 (6)

110 (6)

110 (6)

110 (6)

Not Supp.

Not Supp.

Not Supp.

101 (5)

101 (5) green 100 (4) yellow

101 (5) green 100 (4) yellow

101 (5) green 100 (4) yellow

100 (4)

Regulated(3)

Not Supp.

Not Supp.

011 (3)

011 (3)

Regulated(4)

011 (3) green 010 (2) yellow

011 (3) green 010 (2) yellow

010 (2)

010 (2)

Best Effort

001 (1) green 000 (0) yellow

000 (0)

000 (0)

000 (0)

Background

Not Supp.

001 (1)

001 (1)

001 (1)

Regulated(1) Regulated

3 — 4 — 26

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

The table reports the Encoding rules of PHB into PCP bits at the egress port, for the different operation mode.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 26

2 Network Constructor and Bridge infrastructure management

Transport Link activation/deactivation 

This function activate (deactivate) the extremities (set up/down) of a transport link, even if is already assigned to a domain.



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”)

3 — 4 — 27

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 27

2 Network Constructor and Bridge infrastructure management

Transport Link properties and extremities getting 

To get the Transport Link Properties : 1) Select a Link in the Bridge Transport Link list 2) Actions (or right mouse button)  Properties



To get the Transport Link Extremities: 1) Select a Link in the Bridge Transport Link list 2) Actions  Bridge Transport Link  Extremities

3 — 4 — 28

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 28

3 Ethernet service management

3 — 4 — 29

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 29

3 Ethernet Service management

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

3 — 4 — 30

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 30

3 Ethernet Service management

Ethernet Service creation 

Condition to be able to create an Ethernet Service : 



At least, one Customer must exist

To create an Ethernet Service: 1) Actions  Packet  Services  Create Ethernet Service

or, 1) Select a Customer in the Customers list 2) Actions  Customer  Create Ethernet Service

3 — 4 — 31

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

-

Enter : User Label Reference SLA (a string); optional Comment (optional)

-

Customer: Click on the box to display available Customer and choose one

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 31

3 Ethernet Service management

Ethernet Service properties, modification and deletion 

To get the Ethernet Service Properties: 1) Select a Service in list 2) Actions (or right mouse button)  Properties



To modify the Ethernet Service Parameters: 1) Select a Service in list 2) Actions (or right mouse button)  Modify



To delete an Ethernet Service: 1) Select a Service in list 2) Actions  Services  Delete

3 — 4 — 32

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 32

3 Ethernet Service management

Exercise   

Create a set of Ethernet Services Display the Ethernet service properties Delete some Ethernet services

3 — 4 — 33

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 33

Blank Page

3 — 4 — 34

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

This All page Rights is Reserved left blank © Alcatel-Lucent intentionally 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 34

4 Connection-Less Ethernet Virtual Connection

3 — 4 — 35

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 35

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

3 — 4 — 36

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 36

4 Connection-less Ethernet Virtual Connection

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

3 — 4 — 37

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 37

4 Connection-less Ethernet Virtual Connection

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

3 — 4 — 38

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 38

4 Connection-less Ethernet Virtual Connection

Provider Bridge EVC creation: Detail 

Details panel:

S-VLAN assigned to the Service

3 — 4 — 39

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 39

4 Connection-less Ethernet Virtual Connection

Provider Bridge EVC creation: L2 Control Protocol

3 — 4 — 40

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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)

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 40

4 Connection-less Ethernet Virtual Connection

Provider Bridge EVC creation: PM

Set “True” to enable PM. (Refer to specific session for details)

3 — 4 — 41

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 41

4 Connection-less Ethernet Virtual Connection

Provider Bridge EVC creation: Miscellaneus 

Miscellaneus panel:

Click on Next to continue with the Terminations Settings window

3 — 4 — 42

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 42

4 Connection-less Ethernet Virtual Connection

Provider Bridge Ingress/Egress Flows: definition

S-VID PUSH

CLASSI FIER

LAN or SDH

ETS_P Port

LAN or SDH

ETS_P Port

ES card

3 — 4 — 43

Ingress Flow TD & Pol.

PROVIDER OUTFLOW L2 switching layer

Egress Flow

TD0 PROVIDER INFLOW

S-VID POP

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

At least one Ingress Flow or at least one Egress Flow should be defined, in order to cover the following cases: 

To define some”Source” 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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 43

4 Connection-less Ethernet Virtual Connection

Terminations Settings Ingress Flow By clicking on Next the operator has access to the configuration of the Ingress Flow and Egress Flow configuration window: 

The operator has to configure at least an Ingress flow or at least an Egress flow for each EVC termination 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 3 — 4 — 44

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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 select the Classification Mode (Priority, DSCP) VLAN Pop Enabled: set to “True” if a VLAN pop is required at the Ingress side (see next slides)

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 44

4 Connection-less Ethernet Virtual Connection

Terminations Settings Ingress Flow: add Classifier 

Traffic Classifier panel: 4. Open the classifier list and confirm with the icon

3 — 4 — 45

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 45

4 Connection-less Ethernet Virtual Connection

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)

3 — 4 — 46

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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)

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 46

4 Connection-less Ethernet Virtual Connection

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

EgressFlow

IngressFlow

VLAN Push

VLAN Pop

3 — 4 — 47

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 47

4 Connection-less Ethernet Virtual Connection

Vlan Push on Egress Flow 

The Vlan Push on Egress Flow allows to encapsulate untagged or CVlan tagged Ethernet frames with a Provider V-Lan Tag, for interworking purpose

EgressFlow

VLAN Push

3 — 4 — 48

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

To enable the Push operation, the operator must set “Clear all fields” to False: - 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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 48

4 Connection-less Ethernet Virtual Connection

Vlan Pop on Ingress Flow 

The Vlan Pop defines a POP operation to be performed on Ethernet traffic ingressing in the Provider Bridge Domain

IngressFlow

VLAN Pop

3 — 4 — 49

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

To enable the Pop operation, the operator must set “VLAN Pop Enabled” to True

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 49

4 Connection-less Ethernet Virtual Connection

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 an EVC in the list 2) Search  Bridge EVC  EVC Terminations

3 — 4 — 50

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

From this list is possible to display the EVC Termination properties, to modify or to delete it

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 50

4 Connection-less Ethernet Virtual Connection

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

3 — 4 — 51

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 51

4 Connection-less Ethernet Virtual Connection

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 CLASSI FIER

ETS_P Port



Ingress Flow TD & Pol.

To add an Ingress Flow: 1) Select an EVC Termination: 2) Actions  EVC Termination  Add Provider Bridge Ingress Flow

3 — 4 — 52

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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 Traffic Classifier list)

to display the

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 52

4 Connection-less Ethernet Virtual Connection

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 ETS_P Port



Egress Flow

To add an Egress Flow: 1) Select an EVC Termination: 2) Actions  EVC Termination  Add Provider Bridge Egress Flow

3 — 4 — 53

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 53

4 Connection-less Ethernet Virtual Connection

Provider Bridge Egress / Ingress Flow list 

To display the Provider Bridge Ingress or Egress Flows List configured in an EVC, from the MS_GUI: 1) Select an EVC in the list 2) Action  Bridge EVC  Provider Bridge Flows

3 — 4 — 54

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 54

4 Connection-less Ethernet Virtual Connection

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

3 — 4 — 55

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

From this list is possible to display the EVC Termination properties, to modify or to delete it

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 55

4 Connection-less Ethernet Virtual Connection

EVC modification 

To modify an EVC : 1) Select an EVC in the list 2) Actions (or right mouse button)  Modify

3 — 4 — 56

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 56

4 Connection-less Ethernet Virtual Connection

EVC configuration 

The configuration of an EVC consists in associating a Traffic Descriptor and a VLAN Bundle to the EVC.



To configure an EVC : 1) Select an EVC in the list 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)

3 — 4 — 57

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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).

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 57

4 Connection-less Ethernet Virtual Connection

EVC properties and deletion 

To get the EVC Properties: 1) Select an EVC in the list 2) Actions (or right mouse button)  Properties



To delete an EVC: 1) Select an EVC in the list 2) Actions (or right mouse button)  Bridge EVC  Delete

3 — 4 — 58

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

In deleting an EVC the provisioning state of the EVC must be “Defined”

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 58

4 Connection-less Ethernet Virtual Connection

EVC Termination Properties and deletion 

To get the EVC Termination Properties: 1) Select an EVC Termination in the list 2) Actions (or right mouse button)  Properties



To delete an EVC Termination: 1) Select an EVC Termination in the list 2) Actions (or right mouse button)  EVC Termination  Delete

3 — 4 — 59

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 59

Blank Page

3 — 4 — 60 System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 60

5 Spanning Tree Instance management

3 — 4 — 61

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 61

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

3 — 4 — 62

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 62

6 Ethernet Virtual Connection life cycle

3 — 4 — 63

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 63

6 Ethernet Virtual Connection life cycle

Definition 

EVC life cycle :

Defined state

Allocate Implement

Commission

3 — 4 — 64

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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”

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 64

6 Ethernet Virtual Connection life cycle

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: 1) Select one or several EVC in the list 2) Actions  Bridge EVC  Implement/Deimplement



To commission/decommission the EVC: 1) Select one or several EVC in the list 2) Actions  Bridge EVC  Commission/Decommission

3 — 4 — 65

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

“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”

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 65

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

A

Link over SDH

Link over Cable

B

A

A

B

Customer

3 — 4 — 66

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 66

End of Module Bridge Provisioning

3 — 4 — 67

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Bridge Provisioning 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 3 — Module 4 — Page 67

Do not delete this graphic elements in here:

3—7

Section 3 System Operation Module 7 Network utilities 3JK Edition 1.00

All Rights Reserved © Alcatel-Lucent 2010

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 1

Blank Page

3—7—2

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

This page is left blank intentionally

Document History Edition

Date

Author

Remarks

01

2009-05-21

Buono Giovanni

First edition

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 2

Module Objectives Upon completion of this module, you should be able to:  Detect, by means of Audit, the misalignment between the NE and 1350OMS PKT dB  Fix the misalignment by executing a download into the NE

3—7—3

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 3

Module Objectives [cont.]

3—7—4 System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 4

Table of Contents Page

Switch to notes view! 1 2 3 4 5

NE Audit tool NE Reserve tool NE Alignment tool NE Force Alignment tool PKT vs SDH synchronization

3—7—5

7 13 15 17 21

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 5

Table of Contents [cont.] Switch to notes view!

3—7—6 System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 6

1 NE Audit tool

3—7—7

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 7

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 3—7—8

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 8

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) 2)

Select one or several NEs from the Auditable NE list Actions  Auditable Ne  Start NE Audit

3—7—9

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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”.

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 9

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

3 — 7 — 10

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 10

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

3 — 7 — 11

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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.

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 11

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

3 — 7 — 12

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

At any time of the audit / alignment / reserve session the operator can close the session. An “unlock” of the locked NEs will be done.

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 12

2 NE Reserve tool

3 — 7 — 13

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 13

2 NE Reserve tool

Perform a reservation on an NE To start a Reservation operation: 1) 2)

Select one or several NEs from the Audited NEs List: Actions  Audited Ne  NE Resource Reservation

N.B. Not yet implemented in the scope of 1350OMS PKT rel9.1.1

3 — 7 — 14

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 14

3 NE Alignment tool

3 — 7 — 15

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 15

3 NE Alignment tool

Perform an alignment on an NE To start an Alignment operation: 1) 2)

Select one or several NEs from the Audited NEs List: Actions  Audited Ne  NE Align Down

The Alignment State of the NE is set to “Done”

3 — 7 — 16

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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.

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 16

4 NE Force Alignment tool

3 — 7 — 17

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 17

4 NE Force Alignment tool

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

3 — 7 — 18

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 18

4 NE Force Alignment tool

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

3 — 7 — 19

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 19

4 NE Force Alignment tool

Perform a Force Align Down on an NE To start a Force Alignment operation: 1) Select one or several NEs from the Audited NEs List: 2) Actions

 Audited Ne  NE Force Align Down Execution

3 — 7 — 20

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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.

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 20

5 PKT vs SDH synchronization

3 — 7 — 21

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 21

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 SDH

Manual Resynchronize

1350 PKT

TDM Terminations and Link over TDM uploading 3 — 7 — 22

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

The synchronization status can be checked at any time, by: Action  Packet  Construction  Synchronization  Check Synchronization Status

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 22

End of Module Network utilities

3 — 7 — 23

All Rights Reserved © Alcatel-Lucent 2010

System Operation — Network utilities 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © 2007, Alcatel-Lucent 3JK Edition 1.00 Section 3 — Module 7 — Page 23

Do not delete this graphic elements in here:

4—1

Section 4 Maintenance Applications Module 1 Alarm Management 3JK Issue 1.00

1350OMS 1350OMS-PKT R 9.1.1 Operation TOS63013-R.9.1.1-SG1-SEN-I1.0 Issue 1.00

All Rights Reserved © Alcatel-Lucent 2010

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 4 — Module 1 — Page 1

Blank Page

4—1—2

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Alarm Management 1350OMS — 1350OMS-PKT R 9.1.1 Operation

This page is left blank intentionally

Document History Edition

Date

Author

Remarks

01

2009-05-21

Buono Giovanni

First edition

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 4 — Module 1 — Page 2

Module Objectives Upon completion of this module, you should be able to: • Manage the elementary alarms affecting 1350OMS PKT managed resources.

4—1—3

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Alarm Management 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 4 — Module 1 — Page 3

Module Objectives [cont.]

4—1—4 Maintenance Applications — Alarm Management 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 4 — Module 1 — Page 4

Table of Contents Page

Switch to notes view! 1 Alarm display 2 Fault management

4—1—5

7 13

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Alarm Management 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 4 — Module 1 — Page 5

Table of Contents [cont.] Switch to notes view!

4—1—6 Maintenance Applications — Alarm Management 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 4 — Module 1 — Page 6

1 Alarm display

4—1—7

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Alarm Management 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 4 — Module 1 — Page 7

1 Alarms display

Alarms propagation Alarm Sources

Alarm Propagation & Analysis Engine

NE (reachability) Ethernet Port

AS NE (isolation)

AS Link over T-MPLS Customer

AS

AS Link over Cable

Service EVC PW Segment

GFP

TDM Termination Path

Ethernet Segment

Link over AS TDM (SDH/Sonet) AS Link over WDM

4—1—8

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Alarm Management 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 4 — Module 1 — Page 8

Tunnel

Transport

1 Alarms display

Routing display alarm propagation

Customer Service EVC Segment

PW Tunnel

Transport

Alarmed object 4—1—9

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Alarm Management 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 4 — Module 1 — Page 9

1 Alarms display

Fault localization 

To display the Fault localization list : Select an entity with Availability status “Degraded” or “In Failure” 1) Search  (i.e. Link Over Cable)  Fault Localization

4 — 1 — 10

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Alarm Management 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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.

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 4 — Module 1 — Page 10

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 Right mouse button  Start Double click on the icon

4 — 1 — 11

or or

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Alarm Management 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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)

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 4 — Module 1 — Page 11

Blank Page

4 — 1 — 12

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Alarm Management 1350OMS — 1350OMS-PKT R 9.1.1 Operation

This All page Rights is Reserved left blank © Alcatel-Lucent intentionally 2010 3JK Issue 1.00 Section 4 — Module 1 — Page 12

2 Fault management

4 — 1 — 13

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Alarm Management 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 4 — Module 1 — Page 13

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 Alarm Synchronization

DCN

1350 PKT

Alarm Updating

4 — 1 — 14

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Alarm Management 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 4 — Module 1 — Page 14

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

4 — 1 — 15

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Alarm Management 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 4 — Module 1 — Page 15

End of Module Alarm Management

4 — 1 — 16

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Alarm Management 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 3JK Issue 1.00 Section 4 — Module 1 — Page 16

Do not delete this graphic elements in here:

4—2

Section 4 Maintenance Applications Module 2 Performance monitoring xx Issue 01

1350OMS 1350OMS-PKT R 9.1.1 Operation TOS63013-R.9.1.1-SG1-SEN-I1.0 Issue 1.00

All Rights Reserved © Alcatel-Lucent 2010

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 1

Blank Page

4—2—2

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

This page is left blank intentionally

Document History Edition

Date

Author

01

2010-02-26

Buono Giovanni

Remarks

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 2

Module Objectives Upon completion of this module, you should be able to:    

activate and deactivate Performance Monitoring display the results export PM information compare the NML’s PM DB with the EML’s PM DB

4—2—3

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 3

Module Objectives [cont.]

4—2—4 Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 4

Table of Contents Page

Switch to notes view! 1 2 3 4

PM from 1350OMS-PKT point of view PM on Ethernet Service T-MPLS PM management PM advanced operation

4—2—5

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 5

7 12 29 42

Table of Contents [cont.] Switch to notes view!

4—2—6 Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 6

1 PM from 1350OMS-PKT point of view

4—2—7

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 7

1 PM from 1350OMS-PKT point of view

Objectives 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 Received Received packets packets Port 1

Port 3

Port 2

Port 4

Discarded Discarded Packets Packets

4—2—8

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 8

Transmitted Transmitted packets packets

1 PM from 1350OMS-PKT point of view

PM objects PM domain

Measure

PM transport

PM TP

4—2—9

DB Administration

Report Profile

Archive session

• 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.

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation



Measures are defined on 1350OMS-ETH transport entities (EVC, Tunnel, PseudoWire) and requested on NE’s Termination Points (TPs).



For each transport entity a PM transport is created. For each TP a PM TP is created.



1350OMS-ETH requests 1350OMS-EML to start the counters on NEs whose TPs have to be monitored.

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 9

1 PM from 1350OMS-PKT point of view

Procedure Select the transport entity (EVC, Tunnel, PW) and “Start” PM:

1.

Measure, PM Transport, and PM TPs are automatically created



Open the PM Domain Locate and retrieve the measure Retrieve the PM Transport Retrieve the PM TPs:

2. 3. 4. 5.

they provide the PM results

 6. 7.

To stop the PM, select the transport entity and “Stop” PM Delete the Measure PM Domain Measure

Measure

PM Transport

PM Transport

PM TP

PM TP PM TP

4 — 2 — 10

PM TP

Each Measure contains one PM Transport that contains the PM TPs

PM TP

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation



Measure: it defines the objective, the time granularity and other parameters of the PM.

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 10

1 PM from 1350OMS-PKT point of view

Measure lifecycle “Start PM” yields an “activated” Measure

ACTIVATED Measure

Start PM

implement transport object

implement transport object

STOPPED

STANDBY Measure Delete Measure

remove transport object

Stop PM

remove transport object

TERMINATED Measure

Measure Delete Measure

4 — 2 — 11

deimplement transport object

Deimplement transport object

Delete Measure

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation



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 Measure’s attribute “Auto Purge” is set to “False”.

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 11

Blank Page

4 — 2 — 12 Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 12

2 PM on Ethernet Service

4 — 2 — 13

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 13

2 PM on Ethernet Service

Performance Monitoring overview

Received frames IN FLOW

OUT FLOW

SDH port A

Monitored object:

AU4



SDH XC

The system support Ethernet Aggregated octet/frame counters and also octet/frame counters on per flow (service) basis.

ETS XC



Transmitted frames

LOCAL Eth. Port

4 — 2 — 14 Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

REMOTE Eth. Port

All Rights Reserved © Alcatel-Lucent 2010

Section 3 - Module 6 - Page 14

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 14

Transmitted frames Received frames

2 PM on Ethernet Service

Aggregated Counters Aggregate counters on Received Frames: •TRCF •TRCF Broadcast •TRCF Multicast •TRCF Unicast •TRCO •TRDF •TRSEF

Received frames IN FLOW

OUT FLOW

AU4 SDH port A

Aggregate counters on Transmitted Frames: •TTDF •TTF •TTF Broadcast •TTF Multicast •TTF Unicast •TTO

Transmitted frames

Transmitted frames

4 — 2 — 15 Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

Received frames

All Rights Reserved © Alcatel-Lucent 2010

Section 3 - Module 6 - Page 15

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

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 15

2 PM on Ethernet Service

Per Flow Counters

Ingress Flow counters: •TRCFg •TRCFy •TRCOg •TRCOy

IN FLOW

4 — 2 — 16 Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

OUT FLOW

AU4

Received frames

SDH port A

Egress Flow counters: •TTFg •TTFy •TTOg •TTOy

All Rights Reserved © Alcatel-Lucent 2010

Section 3 - Module 6 - Page 16

TRCFg: number of Total Received Correct green Frames TRCFy: number of Total Received Correct yellow Frames TRCOg: number of Total Received Correct green Ethernet Octets TRCOy: number of Total Received Correct yellow Ethernet Octets TTFg: number of Total Transmitted green Ethernet Frames TTFy: number of Total Transmitted yellow Ethernet Frames TTOg: number of Total Transmitted green Ethernet Octets TTOY: number of Total Transmitted yellow Ethernet Octets

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 16

Transmitted frames

2 PM on Ethernet Service

PM activation during the EVC creation

Choose “True” and set the parameters

4 — 2 — 17

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 17

2 PM on Ethernet Service

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

4 — 2 — 18

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

N.B: the EVC must be Implemented

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 18

2 PM on Ethernet Service

PM activation for an already created service [cont.]

2. Set the specific parameters

3. Click on Apply

4 — 2 — 19

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 19

2 PM on Ethernet Service

PM result 1. Search  PM  PM Domains on NML

2. Select ETH: Search  PM Measure

4 — 2 — 20

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 20

2 PM on Ethernet Service

PM result [cont.] 3. Select the measure: Search  PM Transports

4. Select the transport: Search  PM TPs

4 — 2 — 21

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 21

2 PM on Ethernet Service

TP list The list of the available TP is displayed 64B

I.e: End EndPoint Point

4 — 2 — 22

80

65B 1

1

Intermediate IntermediatePoint Point

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 22

81

2 PM on Ethernet Service

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). 4 — 2 — 23

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

The list of available TPs is displayed; it s possible to retrieve measurements for: 

Aggregated Ports, UNI or NNI



per flow basis (Type = FLOW)

(Type = ETHINTERFACE)

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 23

2 PM on Ethernet Service

Report examples

Tabular

Line chart

Bar chart 4 — 2 — 24

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 24

2 PM on Ethernet Service

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”

4 — 2 — 25

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 25

2 PM on Ethernet Service

PM synchronization 

This operation is executed when the operator wants to align PM setting to EOT setting To align the PM set to the EVC set: 1. select the EVC 2. (right mouse button): Actions  PM  Synchro PM

3. Select the Granularity of the counter to be synchronized and click on “Apply”

4 — 2 — 26

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 26

2 PM on Ethernet Service

Operation from Measure: Delete, Consist Tick the box and click on Apply

Delete Measure

Consist Measure: must be run whenever “Consistency” is “Not Consistent” 4 — 2 — 27

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

In order to delete a measure, the State must be different from “Activated”

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 27

2 PM on Ethernet Service

Operation from Measure: Modify

Click on the field to modify the attributes, then click on Apply

4 — 2 — 28

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

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)

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 28

2 PM on Ethernet Service

Navigation from Transport to PM Transport From PM Transport to Transport: Look for the PM Transport’s User Label (it’s equal to the Transport’s 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

4 — 2 — 29

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation



Navigation from Transport to PM Transport: without opening the PM Domain and the Measures list, it’s possible to get the PM Transport directly from the Transport.

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 29

Blank Page

4 — 2 — 30 Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 30

3 T-MPLS PM management

4 — 2 — 31

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 31

3 T-MPLS PM management

Performance Monitoring on T-MPLS object 

The following TMPLS Objects can be monitored from PM point of view:  TMPLS Tunnel;  TMPLS Pseudo Wire; MPLS Tunnel

PW

(PE)

PM PMon on End EndPoint Point

4 — 2 — 32

(P)

PM PMon on Intermediate Intermediate Points Points

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 32

(PE)

PM PMon on End EndPoint Point

3 T-MPLS PM management

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) Eth local port

Outgoing packet PW Bid Incoming packet

TUSEG#x (Bid)

4 — 2 — 33 Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

Section 4 - Module 2 - Page 33

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 33

3 T-MPLS PM management

How to activate counters on End Points

1. Select a Tunnel (or PW): Actions  Start PM

2. Specify the Granularity and click on “Apply” 4 — 2 — 34

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation



PM Granularity: choose 15 minutes or 24 hours

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 34

3 T-MPLS PM management

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

Outgoing packet PW Bid Incoming packet

TUSEG#x (Bid)

4 — 2 — 35 Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

Section 4 - Module 2 - Page 35

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 35

3 T-MPLS PM management

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” 4 — 2 — 36

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation



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)

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 36

3 T-MPLS PM management

PM result 1. Search  PM  PM Domains on NML

2. Select ETH: Search  PM Measure

4 — 2 — 37

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 37

3 T-MPLS PM management

PM result [cont.] 3. Select the measure: Search  PM Transports

4. Select the transport (i.e: Tunnel): Search  PM TPs

4 — 2 — 38

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 38

3 T-MPLS PM management

TP list The list of the available TP is displayed

(i.e:

C321

C322 1

End EndPoint Point

4 — 2 — 39

1

C323 6

1

Intermediate IntermediatePoint Point

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

The list of available TPs is displayed; it s possible to retrieve measurements for: 

End Points



Intermediate Points

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 39

3 T-MPLS PM management

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). 4 — 2 — 40

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 40

3 T-MPLS PM management

Report examples

Tabular

Line chart

Bar chart 4 — 2 — 41

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 41

3 T-MPLS PM management

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

4 — 2 — 42

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 42

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.

4 — 2 — 43

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 43

Blank Page

4 — 2 — 44 Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 44

4 PM advanced operation

4 — 2 — 45

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 45

4 PM advanced operation

Report Profile: creation

To create a profile: select the ETH PM Domain  Actions  Create Report Profiles

To look for the available profiles: select the ETH PM Domain  Search  Report Profiles

Report Profile holds the rules for creating files that record the PM results (TRCF, TRCO, TRSEF,……). Files are generated every “window” time.

4 — 2 — 46

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation



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 file’s name is: _Report’s 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 file’s name is: _Transport’s 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.

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 46

4 PM advanced operation

Report Profile: correlation 1. To associate the profile to the measure: select the Measure:  Actions  Correlate with Report Profile

2. Choose the profile

To disassociate the profile from the measure: select the Measure:  Actions  Uncorrelate with Report Profile 4 — 2 — 47

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation



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.

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 47

4 PM advanced operation

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” / “file’s 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 file’s name will be: 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 file’s name will be: CPM_NM_CSV_EXPORT_”Date”_”Time”)

4 — 2 — 48

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 48

4 PM advanced operation

PM Audit 

The user can carry out a comparison between the EML’s PM DB and the NML’s PM DB to discover the TPs with different PM configuration. NML’s PM Database PM Transport

EML’s PM Database NE’s MIB TPs

Supposed to be aligned

Measure

Monitored NE Monitored TPs

PM NE (NML NE)

Audit on PM TP basis

PM TPs (*)

Audit on PM NE basis

(*) PM TPs can be retrieved from PM Transport 4 — 2 — 49

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation



PM NE is available if at least one of its PM TPs is required for a PM Transport.

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 49

4 PM advanced operation

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

Click on “Apply” Audit on PM TP basis: 1. Select a PM TP  Actions  Audit TP 4 — 2 — 50

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 50

4 PM advanced operation

PM Audit: result

In case of “PM Audit on PM TP basis”, just one row is prompted

4 — 2 — 51

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 51

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.

4 — 2 — 52

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 52

End of Module Performance monitoring

4 — 2 — 53

All Rights Reserved © Alcatel-Lucent 2010

Maintenance Applications — Performance monitoring 1350OMS — 1350OMS-PKT R 9.1.1 Operation

All Rights Reserved © Alcatel-Lucent 2010 xx Issue 01 Section 4 — Module 2 — Page 53

Last But One Page Switch to notes view!

1 @@PRODUCT @@COURSENAME

All Rights Reserved © Alcatel-Lucent @@YEAR

This page is left blank intentionally

All Rights Reserved © Alcatel-Lucent @@YEAR @@COURSENAME - Page 1

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 All Rights Reserved © Alcatel-Lucent @@YEAR @@COURSENAME - Page 2

View more...

Comments

Copyright ©2017 KUPDF Inc.
SUPPORT KUPDF