ALU 1350OMS PKT with T-MPLS

8/19/2019 ALU 1350OMS PKT with T-MPLS

1/659

Copyright © 2013 Alcatel-Lucent. All Rights Reserved.

COPYRIGHT ©ALCATEL-LUCENT 2013. ALL RIGHTS RESERVED.

1350 OMS PKTR 9.6 Operation and Maintenance withoutMPLS-TPT-MPLSSTUDENT GUIDETOP63071_V1.1-SG Edition 1

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


2/659


R 9.6 Operation and Maintenance without MPLS-TPT-MPLS1350 OMS PKT2

COPYRIGHT © ALCATEL-LUCENT 2013. ALL RIGHTS RESERVED.

Terms of use and legal notices

Switch to notes view!TERMS OF USE AND LEGAL NOTICE Alcatel-Lucent provides this training course to you subject to these Terms of Use and Legal Notice. Your use of this trainingcourse and/or this site constitutes your acceptance of and agreement to these Terms of Use and Legal Notice. These Termsof Use and Legal Notice, as well as the contents of this training course, may be updated or amended by Alcatel-Lucent fromtime to time without prior notice to you. Your use of the Alcatel-Lucent training materials after such update or amendmentconstitutes your acceptance of and agreement to said updated or amended Terms of Use and Legal Notice.

SAFETY WARNING Alcatel-Lucent training materials can be for products or refer to products that have both lethal and dangerous voltagespresent. Always observe all safety precautions and do not work on the equipment alone. The user is strongly advised not towear conductive jewelry while working on the products. Equipment referred to or used during this course may beelectrostatic sensitive. Please observe correct anti-static precautions.

PERMISSION TO USE CONTENTThe information, communications, scripts, photos, text, video, graphics, music, sounds, images and other materials providedin this training course (collectively the "Content"), is intended for the lawful use of employees of Alcatel-Lucent and otherauthorized participants in this Alcatel-Lucent training course. You are hereby granted a non-exclusive, non-transferablepermission to access and use the Content solely for your personal training and non-commercial use. This permission may beterminated by Alcatel-Lucent at any time for any reason or no reason, with or without notice. You must immediately ceaseuse of the Content upon such termination.

COPYRIGHTS AND TRADEMARKSThe unauthorized copying, displaying or other use of any Content from this training course is a violation of the law and

Alcatel-Lucent’s corporate policies. The Content is protected in France, the U.S. and other countries by a variety of laws,including but not limited to, copyright laws and treaty provisions, trademark laws, patent laws and other proprietary rightslaws (collectively, "IP Rights"). In addition to Alcatel-Lucent’s IP Rights in the Content, in part and in whole, Alcatel-Lucent,and any of the third parties who have licensed and/or contributed to the Content, owns a copyright in the formatting andpresentation of the Content.

Alcatel-Lucent does not grant you any permission to use the Content other than the permission expressly stated in theseTerms of Use and Legal Notice. All other use of Content from this training course, including, but not limited to, modification,publication, transmission, participation in the transfer or sale of, copying, reproduction, republishing, creation of derivativeworks from, distribution, performance, display, incorporation into another training course or presentation, or in any other wayexploiting any of the Content, in whole or in part, for uses other than those expressly permitted herein is strictly prohibitedand shall not be made without Alcatel-Lucent’s prior written consent. All characters appearing in this training course arefictitious. Any resemblance to real persons, living or dead, is purely coincidental.There may be a number of proprietary logos, marks, trademarks, slogans and product designations found in theContent. Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logos are trademarks of Alcatel-Lucent. All other trademarks

are the property of their respective owners. Alcatel-Lucent does not grant you a license to use any of the foregoing logos,marks, trademarks, slogans and product designations in any fashion. Granting of the right to access and use the Content fortraining purposes does not confer upon you any license under any of Alcatel-Lucent’s or any third party's IP Rights.

DISCLAIMER ALCATEL-LUCENT DISCLAIMS ALL WARRANTIES REGARDING THE TRAINING COURSES OR THE CONTENT, EXPRESS ORIMPLIED, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR APARTICULAR PURPOSE. THE ALCATEL-LUCENT WILL NOT BE RESPONSIBLE OR LIABLE FOR ANY INJURY, LOSS, CLAIM,DAMAGE, OR ANY SPECIAL, EXEMPLARY, PUNITIVE, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES OF ANY KIND(INCLUDING WITHOUT LIMITATION LOSS PROFITS OR LOSS SAVINGS), WHETHER BASED IN CONTRACT, TORT, STRICTLIABILITY OR OTHERWISE, THAT ARISES OUT OF OR IS IN ANY WAY CONNECTED WITH (A) ANY USE OR MISUSE OF THECONTENT OR THE TRAINING COURSES BY YOU, OR (B) ANY FAILURE OR DELAY BY ALCATEL-LUCENT, ITS OFFICERS,DIRECTORS, AGENTS OR EMPLOYEES IN CONNECTION WITH THE CONTENT OR THE TRAINING COURSES (INCLUDING,WITHOUT LIMITATION, THE USE OF OR INABILITY TO USE ANY COMPONENT OF THE CONTENT OR TRAINING BY

YOU). SOME JURISDICTIONS LIMIT OR PROHIBIT SUCH EXCLUSION OF WARRANTIES OR LIMITATION OF LIABILITIES AND SO THE FOREGOING EXCLUSION OF WARRANTIES OR LIMITATION OF LIABILITY MAY NOT APPLY TO YOU.

GOVERNING LAWThese Terms of Use and Legal Notice are governed by the laws of France. The operation and use of the training course isgoverned by the laws of the country that governs your employment contract, if applicable. If any provision of these Terms ofUse and Legal Notice, or the application thereto to a person or circumstance, is held invalid or unenforceable by law, statuteor a court of competent jurisdiction, for any reason, then such provision shall be modified and/or superseded by a provisionthat reflects the intent of the original provision as closely as possible. All other provisions of these Terms of Use and LegalNotice shall remain in full force and effect. You may not assign these Terms of Use or any permission granted hereunderwithout Alcatel-Lucent’s prior written consent. Nothing herein shall be deemed an employment agreement or an offer ofemployment or an alteration in any way of a user’s terms of employment with or within Alcatel-Lucent.Copyright © 2011 Alcatel-Lucent. All Rights Reserved


3/659




Course outline

4. Topic/Section is Positioned Here




Section 1. Product OverviewModule 1. 1350 OMS PKT in 1350 OMSModule 2. Services environment

Section 2. System OperationModule 1. 1350 OMS GUIModule 2. Construction environmentModule 3. Client traffic parametersModule 4. Connection-oriented EVCsModule 5. Connection-less EVCsModule 6. 9500MPR

Module 7. Aggregate objectsModule 8. Network utilities

Section 3. Maintenance ApplicationModule 1. Alarm managementModule 2. Performance MonitoringModule 3. OAMModule 4. Link Pass Throu h

Welcome to 1350 OMS PKT

R 9.6 Operation and Maintenance without MPLS-TPT-MPLS

Section 1. Product Overview

Module 1. 1350 OMS PKT in 1350 OMS

Module 2. Services environment

Section 2. System Operation

Module 1. 1350 OMS GUI

Module 2. Construction environment

Module 3. Client traffic parametersModule 4. Connection-oriented EVCs

Module 5. Connection-less EVCs

Module 6. 9500MPR

Module 7. Aggregate objects

Module 8. Network utilities

Section 3. Maintenance Application

Module 1. Alarm management

Module 2. Performance Monitoring

Module 3. OAM

Module 4. Link Pass Through

Section 4. Abbreviations and Acronyms

Module 1. Abbreviations and Acronyms


4/659




Course objectives

Upon completion of this course, you should be able to:

describe the 1350 OMS functions and architecture;enable the required technologies (Ethernet; CES) over the Network Elements' ports;create connection-oriented and connection-less Ethernet services;create Circuit Emulation Services (CES);configure the service parameters; such as bandwidth thresholds and filtering criteria;handle the Alarm Surveillance application for monitoring the current and historical alarms;manage the transmission quality records;carry out troubleshooting by means of Ethernet OAM;keep align the Network configuration to the 1350 OMS PKT database.

Welcome to 1350 OMS PKT

R 9.6 Operation and Maintenance without MPLS-TPT-MPLS

Upon completion of this course, you should be able to:

describe the 1350 OMS functions and architecture;enable the required technologies (Ethernet; CES) over the Network Elements' ports;create connection-oriented and connection-less Ethernet services;create Circuit Emulation Services (CES);configure the service parameters; such as bandwidth thresholds and filtering criteria;handle the Alarm Surveillance application for monitoring the current and historical alarms;manage the transmission quality records;carry out troubleshooting by means of Ethernet OAM;keep align the Network configuration to the 1350 OMS PKT database.

Your feedback is appreciated!Please feel free to Email your comments to:

[email protected]

Please include the following training reference in your email:TOP63071_V1.1-SG Edition 1

Thank you!


5/659

All Rights Reserved © Alcatel-Lucent 2013TOP63071_V1.1-SG-R 9.6-Ed1 Module 1.1 Issue 1

Section 1 · Module 1 · Page 1

Do not delete this graphic elements in here:

@@SECAll Rights Reserved © Alcatel-Lucent 2013Module 1

1350 OMS PKT in 1350 OMSTOP63071_V1.1-SG-R 9.6-Ed1 Module 1.1 Issue 1

Section 1Product Overview

1350 OMS PKTR 9.6 Operation and Maintenance without MPLS-TPT-MPLS

TOP63071_V1.1-SG Issue 1


6/659



All Rights Reserved © Alcatel-Lucent 2013

1350 OMS PKT · R 9.6 Operation and Maintenance without MPLS-TPT-MPLSProduct Overview ·1350 OMS PKT in 1350 OMS1 · 1 · 2

Blank Page

This page is left blank intentionally

Document History

Edition Date Author Remarks

01 2011-12-23 Pirola Paolo cILT


03 2013-02-12 Pirola Paolo vILT


7/659





Module Objectives

Upon completion of this module, you should be able to:

Describe the 1350OMS architectureList the main purposes of 1350OMS-PKT


8/659





Module Objectives [cont.]



9/659





Table of contents

Switch to notes view! Page

1 1350OMS Product and its Applications 7TMN description 8

Applications and Common Components 9 Applications’ purposes 10Example of service provisioning: Ethernet over SDH over WDM 112 1350OMS-PKT overview 12Packet networks and services 13Network maintenance 14Three main provisioning environments 15Three main provisioning environments: Construction 16Three main provisioning environments: MPLS-TP and T-MPLS 17Three main provisioning environments: Services 18Three main provisioning environments: summary 19End of Module 20


10/659





Switch to notes view!



11/659




1350 OMS PKT · R 9.6 Operation and Maintenance without MPLS-TPT-MPLSProduct Overview ·1350 OMS PKT in 1350 OMS1 ·1 · 7

1 1350OMS Product and its Applications


12/659






TMN description

A Telecommunication Management Network (TMN) is a structurednetwork featuring management functions for a TelecommunicationNetwork (TN).The TMN is structured in layers

EML: Element Management LayerTo manage the network element configuration, alarms and performance

NML: Network Management LayerTo manage network connectivity, routing and protections in various topologies andacross different regions

SML: Service Management LayerTo manage services offered to the customer: order handling, service handling, billing,service development, planning

BML: Business Management LayerTo manage the overall sales activity: e.g. return on investment, system decisionsupport, market analysis


13/659




1350 OMS PKT · R 9.6 Operation and Maintenance without MPLS-TPT-MPLSProduct Overview · 1350 OMS PKT in 1350 OMS1 ·1 · 9


Applications and Common Components

1350OMS-PKT

1350OMS-eOMS

1350OMS-WDM

GUI &mapsLogin andSecurityFaultManagement PerformanceMonitoring

Network

1350OMSHardwarePlatform

CraftTerminal

1350OMS-SDH 1350OMS-SONET

1350OMS-EML

NMLlayer

EMLlayer

• The 1350OMS focuses on the TMN’s Element Management and Network Management layers.• These management layers’ functions are accomplished by a set of different “applications”.• The Element Management Layer is implemented by the 1350OMS-EML application.• The Network Management Layer is implemented by the 1350OMS-SDH, 1350OMS-PKT, 1350OMS-SONET,

and 1350OMS-WDM applications.• Common functionalities are bundled into components that are shared by the applications:

• by means of a unique login, the user is granted the access to the applications according to the securitysettings.

• the commands of all the applications are available in the same Graphical User Interface (GUI) thatprovides a unique map, too.

• fault management and Performance Monitoring management are common to all the applications. Theuser can retrieve the data collected by a single application, too. Every application renders the alarmsand the PM results according to the own management.

• Craft Terminal is meant for commissioning and for maintenance when the Network Element is notreachable from 1350OMS.


14/659






Applications’ purposes

Legacy LucentNetwork

Legacy LucentNetwork

ElementMng

1350 OMS-PKT

1350 OMS-SDH1350 OMS-SONET

WDM

TDM

DataEthernet,

T-MPLS, CES

1350 OMS-EML

1350 OMS-WDM

1850TSS, 9500MPR, ISA-ES

1850TSS, OMSN

1626LM1830PSS

Client/Server relationship

N e

t w o r k

i n g m a n a g e m

e n

t

1 3 5 0 OM

S -

e OM

S

• Each application is license controlled and separately purchasable.• 1350OMS-EML is for the Element Layer functions such as NE creation, SW download, NE data

backup/restore.• 1350OMS-SDH is for the SDH technology and for the WDM technology in some equipment, e.g. 1626LM.• 1350OMS-PKT is for the data technologies, such as Ethernet, MPLS-TP/T-MPLS, CES (Circuit Emulation

Service).• 1350OMS-SONET is for the SONET technology.• 1350OMS-WDM is for the WDM technology in some equipment, e.g. 1830PSS.• 1350OMS provides the users with the ease of accessing and using the eOMS (embedded Optical

Management System) to provision the former Lucent legacy network. 1350OMS-eOMS accomplishes boththe EML and NML functions.• It is integrated with the 1350OMS GUI for single login and common GUI navigation.• It relies on the Common Fault Management component to display alarms.• It is integrated with EML, SDH, WDM and SONET applications for sub-network management.


15/659






Example of service provisioning: Ethernet over SDH over WDM

1 8 5 0

T S S

GbE

S T M - N

S T M - N

1350OMS-SDH 1350OMS-SDH1350OMS-WDM

1 8 5 0

T S S

1 8 3 0

P S S - 3

2

GbE

1350OMS-PKT1350OMS-PKT

1350OMS-PKT

1350OMS-SDH

1350OMS-WDM

e

n d -

p o

i n t s s e

l e c t i o

n f o r

p r

o v i s i o n i n

g

e f f e

c t o

f p

r o

v i s i o n i n

g

AB C D E

F

1830PSS-32 1350OMS-WDM1850TSS 1350OMS-SDH for SDH; 1350OMS-PKT for Ethernet

• Let’s consider a Gigabit Ethernet service across SDH and WDM networks:• the WDM network is made of 1830PSS-32 equipment.• the Ethernet/SDH network is made of 1850TSS equipment.

• Management:• 1830PSS-32 requires 1350OMS-WDM.• SDH configuration of 1850TSS requires 1350OMS-SDH.• Ethernet configuration of 1850TSS requires 1350OMS-PKT .

• While provisioning the WDM network, the user has to select the end-ports of node C and node D. All theWDM nodes between the two ports are configured.

• While provisioning the SDH network, the user has to select the suitable points of node A and node F. Allthe SDH nodes between the two points are configured.

• While provisioning the Ethernet service, the user has to select the end-ports of node A and node F. TheEthernet configurations are executed on node A and node F.


16/659





2 1350OMS-PKT overview


17/659






Packet networks and services

Networks:

Services:Ethernet services:

connection-orientedconnection-less

Circuit Emulation Services (CES):TDM over packet C

E S

E t h

Ethernet

based networks

(ISA ES, 1850TSS, ...)

Eth

MPLS

based networks

(ISA ES-16)

Eth

MPLS-TP/T-MPLS

based networks

(1850TSS)

Eth

CES

Packet radio

based networks

(9500MPR) Eth

CES

MPLS: Multi Protocol Label SwitchingT-MPLS: Transport MPLSMPLS-TP: MPLS Transport ProfileMPR: Microwave Packet Radio

• ISA-ES boards can be used in OMSN equipment: e.g. 1660SM, 1650SMC, 1662SMC, 1642EM• T-MPLS vs MPLS-TP:

• same operation• different OAM packet format


18/659






Network maintenance

Tabular

Line chart

Bar chart

AlarmSurveillance

PerformanceMonitoring

Performance Monitoring: to analyze the traffic behavior on per-interface and per-flow basis.• transmitted frames• received frames• discarded frames• ...


19/659





Three main provisioning environments

Construction and NNI ports and links that accomplish a technology(Connection-oriented, Bridge, T-MPLS and MPLS-TP, Packet Radio, ...)

MPLS-TP and T-MPLS

Services

1. to enable a specific technology on the network resources

2. only in case of MPLS-TP/T-MPLS based networks

3. to configure the services

Technology: Ethernet Connection-oriented, Ethernet Bridge, T-MPLS and MPLS-TP, Packet Radio, ...



20/659






Three main provisioning environments: Construction

Construction:

NE

ENE (External Network Element)

Transport Links

Domain:a set of ports (UNI and NNI) and links that:

accomplish the same technology - Ethernet Connection-oriented, Ethernet Bridge, T-MPLS andMPLS-TP, Packet Radio, ...

can be used for creating services

1. to enable a specific technology on the network resources


21/659






Three main provisioning environments: MPLS-TP and T-MPLS

T-MPLS and MPLS-TP:

Tunnel

Pseudo-Wire

PW

PWTunnel

2. only in case of MPLS-TP/T-MPLS based networks

NNINNI


22/659






Three main provisioning environments: Services

Services:

Customer

Service:group of EVCs

EVC - Ethernet Virtual Connection:the real end-to-end packet service

CustomerServices

EVCs

3. to configure the services


23/659






Three main provisioning environments: summary

Construction:NE

ENE (External Network Element)Transport LinksDomain

MPLS-TP and T-MPLS:TunnelPseudo-Wire

Services:CustomerEthernet serviceEVC

PW

PWTunnel

Customer

Services

EVCs


24/659





End of Module1350 OMS PKT in 1350 OMS


25/659





Services environmentTOP63071_V1.1-SG-R 9.6-Ed1 Module 1.2 Issue 1

Section 1Product Overview




26/659




1350 OMS PKT · R 9.6 Operation and Maintenance without MPLS-TPT-MPLSProduct Overview · Services environment1 · 2 · 2

Blank Page


Document History






27/659





Module Objectives


Describe the Services environment’s objectsList the EVC topologies along with their parameters


28/659








29/659





Table of contents


1 Ethernet Virtual Connection 71350OMS-PKT’s purpose 8Definitions from Metro Ethernet Forum - MEF 9EVC Types 10Differences among EVC Types 11Resource Sharing attribute of EVC 12Port Service Type 14Resource sharing and Port Service Type in Create EVC wizard 15Port Service Type: “Port to Port” vs “Other” 16EVC Type against Port Service Type 17Traffic Type and Directionality 182 Service environment’s objects 19Basic objects 20Four-level end-to-end provisioning model 21

Summary on EVC 22Segment’s and Ingress Flow’s purpose 23EVC life cycle 24End of Module 25


30/659








31/659




1350 OMS PKT · R 9.6 Operation and Maintenance without MPLS-TPT-MPLSProduct Overview · Services environment1 ·2 · 7

1 Ethernet Virtual Connection


32/659






1350OMS-PKT’s purpose

EVC[Ethernet Virtual Connection]creation and management

CONNECTION-ORIENTED CONNECTION-LESS


33/659






Definitions from Metro Ethernet Forum - MEF

An EVC is an association of two or more UNIs

A given UNI can support more than one EVC

An ingress Service Frame that is mapped to the EVC can be deliveredto one or more of the UNIs in the EVC other than the ingress UNI


34/659






EVC Types

Point-to-Point:EPL - Ethernet Private Line

EPTL - Ethernet Private Transparent LineEVPL - Ethernet Virtual Private Line

PeerPeer

Peer

Any-to-Any:EVPLAN - Ethernet Virtual Private LAN

Rooted Multipoint:HSI - High Speed InternetBTV - Broadcast TelevisionBroadcast

Every EVC is terminated by Edge ports, that usually are the UNI ports.

Depending on the EVC topology, every Edge port assumes a specific Role:• in Point-to-Point topology, the two ports are “Peer”• in Any to Any (Multipoint-to-Multipoint) topology, all of the ports are “Peer”• in Rooted Multipoint (Point-to-Multipoint) topology, one port is “Root” whereas the others are “Leaf”


35/659





Differences among EVC Types

Topology:Point-to-Point, Any-to-Any, Rooted Multipoint

Resources usage:Resource Sharing:

Private UNI, Private Link, Private UNI and Link, FullPort Service Type:

Port to Port, Other

Traffic Type:Unicast, Multicast

Directionality:Unidirectional, Bidirectional



36/659






Resource Sharing attribute of EVC

The network resources (Ports and Transport Links) can be used byseveral EVCs, or not, also according to “Resource Sharing”:

Private UNIthe UNI ports engaged by one EVC cannot be used by other EVCs

Private Linkthe Transport Links engaged by one EVC cannot be used by other EVCs

Private UNI and Linkthe UNI ports and the Transport Links engaged by one EVC cannot be used by otherEVCs

Fullthe UNI ports and the Transport Links engaged by one EVC can be used by other EVCs


37/659






Resource Sharing attribute of EVC [cont.]

Point-to-Point

Any-to-Any

RootedMultipoint

Topology EVC type Resource Sharing

EPL[Ethernet Private Line]

Private UNI

EPTL[Ethernet Private Transparent Line] Private UNI and Link

EVPL[Ethernet Virtual Private Line]

Private UNIPrivate Link

Private UNI and LinkFull

EVPLAN[Ethernet Virtual Private LAN]



HSI[High Speed Internet]

Full

BTV[Broadcast Television]

Full

Broadcast Private UNIFull

Resource Sharing options depend on the EVC type.

Some EVC types have a fixed Resource Sharing value.


38/659





Port Service Type

Can UNIs and Transport Linksbe shared by more EVCs?

ResourceSharing

PortService

Type

Port-based XCFlow-based XC

only forconnection-oriented

EVCs

Port Service Type attribute is visible only for connection-oriented EVCs.

Port Service Type is implicitly equal to “Other” for connection-less EVCs.

Resource Sharing is a PKT’s constraint; it’s not stored in the NEs.

Port Service Type is defined for the EVC and is configured in the NEs’ ports.

In connection-oriented, the ports of some NEs - e.g. ISA ES-16 and 1850TSS-320 - can be configured “Port toPort” or “Other”; the ports of some NEs - e.g. ISA ES-1 and ISA ES-4 - can be configured “Port to Port”only.

Let’s consider for example EVPL connection-oriented:

IF Resource Sharing = Full AND Port Service Type = Port to Port

THEN the resources cannot be shared because the NEs’ ports support just one cross-connection.

IF Resource Sharing = Private UNI and Link AND Port Service Type = Other

THEN the resources cannot be shared because PKT forbids the creation of other EVCs over the sameresources; indeed the NEs could support further cross-connections on their ports.



39/659





Resource sharing and Port Service Type in Create EVC wizard



40/659





Port Service Type: “Port to Port” vs “Other”

ETS ETSETS

ETS

ETS

ETSETS

C-VID=100C-VID=200C-VID=300

C-VID=10010Mb/s

Transport linkETS

ETS

ETS

ETS

ETS

ETS

ETS

ETSTransport link

ETS ETSETS

Transport link

Transport link

Port to Port Port-based XC

Other Flow-based XC

Any

Any

C-VID=20020Mb/s

C-VID=30030Mb/s

Any

AnyNO!



41/659




EVC Type Resource Sharing

EPL[Ethernet Private Line]

Private UNI

EPTL[Ethernet Private Transparent Line] Private UNI and Link

EVPL[Ethernet Virtual Private Line]



EVPLAN[Ethernet Virtual Private LAN]



HSI[High Speed Internet]

Full

BTV[Broadcast Television]

Full

Broadcast Private UNIFull

Port toPort Other


EVC Type against Port Service Type



42/659





Traffic Type and Directionality

Topology EVC Traffic TypeDirectionality

(only for connection-oriented EVCs)

Point-to-Point

EPL

Unicast bidirectionalEPTL

EVPL

Any-to-Any EVPLAN Unicast bidirectional

Rooted Multipoint

HSI Unicast bidirectional

BTV Multicast unidirectionalbidirectional

Broadcast Multicast unidirectional

Unicast: the traffic that enters an Edge Port is delivered to just another Edge Port.

Multicast: the traffic that enters an Edge Port can be delivered to a number of other Edge Ports.

Any-to-Any EVPLAN as connection-oriented: each Edge Port is connected to all other Edge Ports by means ofa set of independent per-flow connections; one different per-flow connection for each other Edge Port;each per flow-connection has different traffic filtering parameters.

BTV: unidirectional if the traffic flow is just from Root to Leaf; bidirectional if the traffic flow is from Leafto Root, too.



43/659





2 Service environment’s objects


44/659




A EthernetbridgeB

UNI

NE-1

NNI

DEthernetbridgeC

UNI

NE-2

NNI

EBA FDCUNI

NE-1 NE-2 NE-3

NNI NNI NNI NNI UNI


Basic objects

Segment

Ingress Flow

Egress Flow Ingress Flow

Egress Flow

C o n n e c t i o

n - o r i e n t

e d

C o n n e c t i o

n - l e s s

( P r o v i d e r B

r i d g e )

Ethernet cross-connection



45/659






Four-level end-to-end provisioning model

Segments(connection-oriented)

Customer Choco Company

Data storage Video conf

conn-lessEVPLAN

conn-orientedEVPL-A

Flows(connection-

less)

conn-orientedEVPL-B

Segment#2Data Center Branch B

Segment#2Data Center Branch A

Segment#1Branch A Data Center

Segment#1Branch B Data Center

EthernetServiceEthernetService

EVCEVCEVCEVC

Ingress FlowBranch A

Egress FlowBranch A

Ingress FlowBranch B

Egress FlowBranch B

EthernetService

Customer:

is the final user of the Ethernet services defined across the boundaries of the Provider’s network

his equipment is connected to the Provider’s network

Service:

defines the service offered by the Provider to his customer, in order to formalise the network connection(EVC) satisfying a specific telecommunication requirement

EVC:

is defined by an SLA (Service Level Agreement)

Segment:

Unidirectional connection between Edge Ports

Flow:

can be Ingress or Egress

is associated to the EVC Terminations (UNI)


46/659






Summary on EVC

Among others, EVC specifies:

Connection-oriented Ethernet Segments

Connection-less Ingress Flows and/or Egress Flows

UNIs terminations of packet serviceService Type EPL, EVPL, EVPLAN,BTV, HSI,...

Topology Point-to-Point, Any to Any, Rooted MultiPoint

Traffic Type Unicast, Multicast

Directionality unidirectional, bidirectional

Resource Sharing Private UNI, Private Link, Full, ...

Port Service Type Port to Port, Other


47/659






Segment’s and Ingress Flow’s purpose

Segments and Ingress Flows specify among other parameters:

Class of Service (CoS):GuaranteedBest EffortRegulated...

Bandwidth thresholds

Classification rule:filter on incoming frame’s fields - e.g. C-VLAN

Traffic Descriptor

Traffic Classifier


48/659






EVC life cycle

Deallocate

Decommission

Deimplement

Delete

Defined

Create

EVC terminations: OK PKT’s DB only

Allocated

Allocate

Route: OK PKT’s DB only

Implemented

Service State=Not in service

Implement

EVC configured in the NEs- running traffic - PKT’s DB and NE’s DB

DB: Database

Implemented

Service State=In service

Commission

PKT’s DB only “Service State = In Service”

- it has no effect on the NEs -

Up to R9.6.3: it has no consequences on EVC management;it may be used to indicate that the EVC is carrying traffic.

From R9.6.4: EVC cannot be deimplemented/deleted;it’s possible to add/remove EVC Terminations.

Commission:• to modify Service State from “Not in Service” to “In Service”. The operator can apply this policy:

implement the EVC for carrying out live tests; commission the EVC when it is given to the customer. Byapplying such a policy, “In Service” means that there’s the customer’s traffic.

Partially ... (not in the slide):• Partially Implemented: at least one segment/flow is Implemented, whereas the others are not (they are

Defined or Allocated).• Partially Allocated: no segment/flow is Implemented; at least one segment/flow is Allocated, whereas

the others are Defined.


49/659





End of ModuleServices environment


50/659





1350 OMS GUITOP63071_V1.1-SG-R 9.6-Ed1 Module 2.1 Issue 1

Section 2System Operation




51/659




1350 OMS PKT · R 9.6 Operation and Maintenance without MPLS-TPT-MPLSSystem Operation · 1350 OMS GUI2 · 1 · 2

Blank Page


Document History






52/659





Module Objectives


Locate the 1350OMS-PKT’s commands in MS-GUI


53/659








54/659





Table of contents

Switch to notes view!Page

1 How to get to MS-GUI 7Web Browser 8Web Desktop 9Web Portal 10MS-GUI 112 1350OMS-PKT’s commands in MS-GUI 12MS-GUI main menus 13Search menu 14Enable/Disable filter 15

Actions menu 16End of Module 17


55/659








56/659




1350 OMS PKT · R 9.6 Operation and Maintenance without MPLS-TPT-MPLSSystem Operation · 1350 OMS GUI2 ·1 · 7

1 How to get to MS-GUI


57/659





1. Open a Web Browser (e.g.: Explorer,Mozilla Firefox, ...) and type theServer’s IP address as Address


Web Browser

The system can be invoked from any web browsers.


58/659






Web Desktop

1. Clickanywhere

VERSION: to checkthe 1350OMS’ssoftware

2. Insert User andPassword andthen Login

To check the PCrequirements:

- 2 GB RAM (3 GB RAM isstrongly recommended)

- JAVA 1.6 and patches

The password is subject to the following constraints:• At least 24 hours should last since the last change• The new password should contain at least one digit [0-9]• The new password should contain at least eight characters• The new password should contain at least two special characters• The new password should contain at least one uppercase letter• The new password should not contain the user identifier


59/659






Web Portal

Right click and choose “Start” ordouble click to start the MS-GUI

(Multi Service - Graphical UserInterface)


60/659






MS-GUI

• The Network Management application provides the Multi Service Graphical User Interface ( MS-GUI), tocreate, modify, delete, retrieve and provision the NEs and the SDH, SONET, WDM and PKT networks.

• It provides inventory lists for querying the content of the management applications’ databases.• It also provides a map of the managed network on which various network objects are displayed, such as

Subnetworks, Nodes, Links, etc.• Performance Monitoring is also issued by the MS-GUI.


61/659





2 1350OMS-PKT’s commands in MS-GUI


62/659






MS-GUI main menus

• MPLS: it’s implemented by ISA-ES16 board in OMSN equipment, e.g. 1660SM, 1650SMC, 1662SMC.• T-MPLS and MPLS-TP are implemented by 1850TSS equipment.

• OAM CC: OAM Continuity Check.• ERP: Ethernet Ring Protection. It was meant for 1850TSS-160C and 1850TSS-10 that are no more part of

the ALU products portfolio.• E2E EVC (End-To-End) EVC: aggregate EVC made of several EVCs.


63/659






Search menu

Search menu to retrieve the content of the 1350OMS-PKT database as lists


64/659






Enable/Disable filter

1. Prior to retrieving a list, check this icon

2. Set the filtering criteria

3. Click on “OK”

• This is an example of filtering method. The trainee should have already seen all the available filteringmethods in the 1350OMS-EML training.


65/659






Actions menu


66/659





End of Module1350 OMS GUI


67/659





Construction environmentTOP63071_V1.1-SG-R 9.6-Ed1 Module 2.2 Issue 1

Section 2System Operation




68/659




1350 OMS PKT · R 9.6 Operation and Maintenance without MPLS-TPT-MPLSSystem Operation · Construction environment2 · 2 · 2

Blank Page


Document History






69/659





Module Objectives


Define the NEConfigure the Ethernet portsCreate and configure the Transport LinksSet the required technology for the Ports and LinksManage the External Network ElementManage the Link Aggregation


70/659








71/659





Table of contents


1 Construction workflow 7Construction is one of the 3 main provisioning environments 8Overview 92 NE definition 10Rationale 11

Available NEs list 12Defined NEs list 13Define NE 14

“Defined NE” back to “Available NE” 163 Ethernet ports configuration 17Port types 18Ethernet physical ports: upload and search for 19Ethernet physical ports: configure 20Ethernet physical ports: Egress Shaping 23

TDM Terminations: upload and search for 24TDM Terminations: configuration 254 Transport Links 26Transport Link types 27Link Over Cable: list 28Link Over Cable: two methods for creating it 29Link Over Cable: creation from Construction 30Link Over Cable: creation as Ethernet Physical Connection 32Link over TDM 33Link over TDM: Ethernet Path 34Link over TDM: 2Mb/s Physical Connection 35Link over WDM 36Link over Radio 37Link over T-MPLS 38

5 Domains 39Rationale 40Domain vs Working Mode 41Domain assignment 43Domain list 44Domain creation 45

Assign a Port to a Domain 47 Assign a Transport Link to a Domain 48 Assign an NE to a Domain 496 External Network Element 50ENE definition 51Three methods to get ENE 52ENE list 53ENE’s ports 54ENE creation from PKT 55ENE from Ethernet physical connection 56ENE from Ethernet path 57ENE’s Ports creation and deletion 58Topological view 597 Link Aggregation 607.1 Introduction 61LAG main targets 62Link Aggregation Control Protocol - LACP 63Frame distribution - Hash Key 64Example 65


72/659





Table of contents [cont.]


7.2 LAG Operation 66Create LAG Port 67Display ports member of a LAG 68LAG role reporting 69LAG port modification and deletion 70Create LAG Link Over Cable From Extremities 71LAG Link deletion 72Create LAG Link Over Cable From Links 73Create LAG Link VCG From Links 74End of Module 75


73/659




1350 OMS PKT · R 9.6 Operation and Maintenance without MPLS-TPT-MPLSSystem Operation · Construction environment2 ·2 · 7

1 Construction workflow


74/659






Construction is one of the 3 main provisioning environments

1. Construction:NE

Transport LinksDomain

2. MPLS-TP and T-MPLS:T-MPLS Section (“Link over xxx” assigned to the T-MPLS Domain)TunnelPseudo-Wire

3. Services (T-MPLS EVC):

CustomerServiceEVC

Flows

Customer

Service

EVC

PW

Tunnel

Section

Flows

Transport1

2

3


75/659






Overview

Create and configure the Transport Links• Link over cable, Link over TDM, Link over WDM, ...

Create the Domain and use it to define the port’s technology• Provider bridge, Virtual bridge, ETS, T-MPLS, Packet Radio, ...

Configure the Ethernet ports• Physical Ethernet ports: Rate, Auto-negotation, Pause Frames, Traffic Status, ...• TDM Terminations: Traffic Status, MRU, ...

Define the NE to get it available to 1350 OMS PKT• NE definition: available NE defined NE• NE’s Working Mode selection: "TMPLS + EPTL", "ETS + Provider + EPTL", ...

First off all, create the NEs by means of 1350OMS-EML

Create the External NEs• from Actions, along with Ethernet Physical Connection, along with Ethernet Path

Create LAG• LAG Link over Cable, LAG Link VCG

6

2

3

4

5

see submodule

7

Some steps are optional.


76/659





2 NE definition


77/659




Create NE

EML

Physical

AvailableNE

PKT

NE

Node

2 NE definition

Rationale

DefinedNE

Define NE

Working Mode selection(technologies to be supported)

Virtual Bridge + EPTLProvider Bridge + EPTL

TMPLS + EPTL

TMPLS + Provider Bridge + EPTL

...

PKT can usethe NE



78/659





2 NE definition

Available NEs list

Search Packet Construction Network Elements Available NEs

AvailableNE

DefinedNE

Define NE


79/659





2 NE definition

Defined NEs list

Search Packet Construction Network Elements Defined NEs

AvailableNE

DefinedNE

Define NE


80/659





2 NE definition

Define NE

Actions Packet Construction Define Network Element

1. Click here to displaythe available NE list

2. Select the NEin the list

AvailableNE

DefinedNE

Define NE

Preconditions:

- NE is supervised and its Operational state is Enabled

- LAC (Local Access Control) state of the NE is Denied


81/659





Working Mode

Virtual Bridge + EPTL

Provider Bridge + EPTL

TMPLS + EPTL

TMPLS + Provider Bridge + EPTL

ETS + Virtual Bridge + EPTL

ETS + Provider Bridge + EPTL

EPTL

ETS + EPTL

ETS + MPLS + EPTL

Flexible Bridge + EPTL

Circuit Emulation + Virtual Bridge+ TMPLS

Circuit Emulation + TMPLS

Indirect

2 NE definition

Define NE [cont.]

3. Set the relatedoptions

• The User Label is automatically assigned.• “Working Mode”: it is used to define which mix of transport technologies are enabled on the NE.

According to the NE Type, only the allowed combinations are shown.• STP Type: in case of bridge Working Mode.

• All of the resources of the NE are uploaded:• TDM terminations• Ethernet ports• Transport Links terminated on the 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 NEs list


82/659





2 NE definition

“Defined NE” back to “Available NE”

Prerequisite: the NE’s resources must be free:no Domain assignment

no EVC...

1) Select the NE in the “Defined NEs” list2) Actions Delete

AvailableNE

PKT

DefinedNE

Define NE Delete


83/659





3 Ethernet ports configuration


84/659






Port types

Ethernet physical portsalso said “local ports”

TDM/WDM terminationsalso said “remote ports”


85/659






Ethernet physical ports: upload and search for

Upload - to align the PKT DB with the NE:1) Select the NE in the Defined NEs list

2) Actions

Upload Ethernet Physical Ports

Search:1) Select the NE in the Defined NEs list2) Search Ethernet Physical Ports

Upload: this function uploads the Ethernet physical ports of the selected NE and is used, manually by the

operator, to fix a misalignment between the PKT DB and the NE.

For uploading or displaying, the selected NE must be in “Consistency state” = Consistent.


86/659






Ethernet physical ports: configure

To configure the physical layer of an Ethernet Port:1) Select a port in the list2) Actions Configure Physical Port(s)

1 2

Traffic Disable support by NE:

NE type/release Ethernetlocal port Remote port LAG port

TSS-3 Not supported Not supported Not supportedTSS-5 Not supported Not supported Not supportedTSS-5C Not supported Not supported Not supportedTSS-5R Not supported Not supported Not supported1646SM, 1646 SMC, 1646-P8FES Not supported Not supported Not supportedTSS-100 from R3.1 Not supported Not supported Not supportedTSS-100 from R4.0 Yes Yes YesTSS-320, TSS-160 from R1.4 Yes Yes Yes

TSS-10 from R1.0 Yes Not applicable YesTSS-160C from R1.0 Yes Not applicable YesES-16 from R2.4a1 Yes Not applicable YesES-1/4 from R1.5 to R1.7 Yes Not supported YesES-1/4 from R3.0 Yes Not supported YesES-64 Not supported Not supported Not supported9500 MPR Not supported Not supported Not supported


87/659





(1) Detail 1 1

Administrative Status [Down/Up]

It’s not necessary to modify it because:

- EVC terminations are set automatically to Up upon EVC implementation

- Transport Link’s extremities are set automatically to Up when theTransport Link is assigned a Domain

MRU: Maximum Received Unit [bytes]


NE type MTU/MRU supported values Default value PKT managesTSS-3 from R2.0 1518, 1522, 1536, 1552, 2048, 10240 2048 R/WTSS-5 From R7.0 1518-9216 1518 R/W

TSS-5C R1.0 1574-9242 1574 R/WTSS-5C from R4.0 1574-10240 1574 R/WTSS-5R From R1.0 1574-10240 1574 R/W

1646SM, 1646 SMC from R1.0Local port: 1518-9600

Remote port: 96001522 R/W

1646-P8FES R2.1Local port: 1518-9600

Remote port: 96001522 R/W

TSS-100 from R3.1 1574-9242 1574 R/WTSS-100 from R4.0 1574-9242 ETS: 1574; ETB: 1600; MPLS: 1600 R/W

TSS-320, TSS-160 from R3.0 toR4.1 1574-9242 ETS: 1574; ETB: 1600; MPLS: 1600 R/W

TSS-320, TSS-160 from R5.0 1574-9622 ETS: 1574; ETB: 1600; MPLS: 1600 R/WTSS-10 from R2.0 1518-12000 9600 R/W

TSS-160C from R1.2ETS: 1574-9220PNP: 1574–9242

ETS: 1574; PNP: 1600; Linkagg: 1574 R

TSS-160C from R2.0 1574-9242 ETS: 1574; PNP: 1600; Linkagg: 1574 R/WES-16 R2.1 Fixed to 2000 N.A. R

ES-16 R2.2ETS: 1518-2000; ETB: 1518-2012

MPLS: 1518-2026ETS: 1518; ETB: 1518; MPLS: 1518 R

ES-16 from R2.4a1 1518-9600 2000 R/WES-1/4 from R1.0 to R1.7 1518-2026 2026 RES-1/4 from R3.0 1518-9600 2026 R

ES-64 from R4.3 1574, 1600, 1974, 2000, 2026, 4474,4500, 4526, 9190, 9216, 9242 1574 R/W

9500 MPR up to R3.0 (latestknown) Fixed to 9728 N.A. R


88/659





(2) Detail 2 2

Auto Negotiation: None/Enabled/Disabled

Actual Interface Rate, when not fixed

Supported Layer: Ethernet/MPLS/None (MPLS: to enable MPLS on ISA ES-16)Duplex Mode: Full/Half (if supported)

Demarc Role: None/Customer Interface/Network Interface

Pause Frame: Disabled/Asymmetric/Symmetric/Symmetric & Asymmetric

Auto Negotiation support by NE:


NE type/version Disabled Asymmetric Symmetric Symmetric&Asymmetricchange

supportedES-1/4 up to R1.3 Y Y N N NES-1/4 from R1.5 Y Y N Y YES-16 up to R2.2 Y Y N N NES-16 from R2.4 Y Y N Y YTSS-320/160 up to R1.2 Y Y N N NTSS-320/160 from R1.4 Y Y N N YTSS-100 R1.1, R3.0 Y Y N N NTSS-100/100C R3.1, R3.2 Y Y N Y NTSS-100/100C from R4.0 Y Y N N YTSS-10 R1.0 to R2.0 Y Y N Y YTSS-160C R1.0 to R2.0 Y Y N N YTSS-3 R1.1, R1.2 Y Y N Y YTSS-3 R2.0, R2.1, R2.2 Y N Y N NTSS-5 VLNC42B R7.0 Y N Y N YTSS-5C R4.0 Y N Y N YTSS-5R R1.0 Y N Y N Y1646SMC R1.0 Y Y Y Y Y1646SM R2.0 Y Y Y Y Y1646-P8FES R2.1 Y Y Y Y Y


89/659






Ethernet physical ports: Egress Shaping

Egress Shaping Rate: egressing traffic’s peak rate- e.g. 1GbE port is configured to transmit 800Mbit/s max -

1) Select the port in the list

2) Actions Configure Egress Shaping

Tick and configure

The egress shaping is applied to the port when it is used as UNI port in case of Provider Bridge or T-

MPLS/MPLS-TP UNI interface.It is possible to modify the Egress Shaping for “activated” or “not activated” ports.


90/659






TDM Terminations: upload and search for

Upload - to align the PKT DB with the NE:1) Select the NE in the Defined NEs list2) Actions Upload TDM/WDM Terminations

Search:1) Select the NE in the Defined NEs list2) Search TDM/WDM Terminations

E.g. 1850TSS-320

This function uploads the SDH terminations of the selected NE and is used, manually by the operator, to

fix a misalignment between the 1350OMS-PKT DB and the 1350OMS-SDH DB, concerning a given NE.

The selected NE must be in “Consistency state” = Consistent.

The SDH terminations are automatically uploaded at NE definition.


91/659






TDM Terminations: configuration

Actions Configure TDM/WDMTermination(s)

Actions Configure EgressShaping


92/659





4 Transport Links


93/659





4 Transport Links

Transport Link types

Search Packet Construction Transport Links ...

Link Over Evc is an aggregate object: “T-MPLS EVC” + 2 x “Interworking Transport Links”


94/659





4 Transport Links

Link Over Cable: list

Link Over Cable corresponds to Ethernet Physical connectionits extremities are Ethernet Physical ports

To display the Link Over Cable list:Search Packet Construction Transport Links Links Over

Cable


95/659





4 Transport Links

Link Over Cable: two methods for creating it

From “Construction” environment of 1350OMS-PKT

As Ethernet Physical Connection

Whatever method is used, 1350OMS provides the link/physicalconnection in “Links Over Cable” list and “Physical Connections” list


96/659





4 Transport Links

Link Over Cable: creation from Construction

Actions Packet Construction Create Link Over Cable

2. Click here to displaythe NE list

1. Enter “User Label” and“Comment” (optional)

The Link Over Cable’s extremities are set as NNI.


97/659





4 Transport Links

Link Over Cable: creation from Construction [cont.]

4. Click on OK toconfirm the selection

5. Click here and selecta Port in the list

3. Select an NEin the list

6. Assign the secondextremity of the Link


98/659





4 Transport Links

Link Over Cable: creation as Ethernet Physical Connection

Actions Physical Create Physical Connection


99/659




4 Transport Links

Link over TDM

Two cases:

Ethernet Path

2Mb/s Physical Connection



100/659





“Link over TDM” corresponds to an Ethernet Path

4 Transport Links

Link over TDM: Ethernet Path

Link over TDM1350OMS-PKT

SDH

capable

equip.

Ethernet Path

ETH ETHEthEth SDH

capable

equip.Ethernetover SDH

TDM Termination(remote port)

1350OMS-SDH

The Ethernet Path is uploaded into the 1350OMS-PKT’s DB as “Link Over TDM” Transport Link.

The effective “Bandwidth” of the “Link over TDM” is equal to the “Transport Rate” times “TotalConcatenation Level” of the TDM path: (vc4, vc3, vc12) x (0…63).


101/659





4 Transport Links

Link over TDM: 2Mb/s Physical Connection

“Link over TDM” corresponds to a 2Mb/s Physical Connection

Between 9500MPR and TDM NE or External Network (EN)The EN may represent:

RNC: Remote Network ControllerBSC: Base Station Controller

9500MPR e.g.1850TSS-100

E1 port E1 port

Actions Physical Create Physical Connection


102/659





4 Transport Links

Link over WDM

“Link over WDM” relies on a WDM Path between 1830PSS equipment

ETH ETHLink over WDM

1830PSS

WDM Path

Optical Trail

ETH ETH

Ethcable

Ethcable

1830PSS

1350OMS-PKT

1350OMS-WDM

Link over WDM = [WDM Path] + [2 x “Ethernet/WDM Interworking” physical connections between 1830PSS

and Ethernet equipment]

Documents

ALU 1350OMS PKT with T-MPLS