NPT MPLS Basic.pdf

L2 DATA FUNCTIONS

Ethernet Switch Global Services Division ECI Training Department

CONTENT 

L2 concept



L2 functions

2

OPEN SYSTEM INTERCONNECTION: OSI Application

Application

Presentation

Presentation

Session

Session

Transport

Transport

Network

Network

Data Link

Data Link

Physical

Physical

3

DATA LAYER 2 - CONCEPT SDH Card

Data Card

L2 ETY GbE/FE

VSI/Flow

L1

SDH Card

EoS

EoS

STM-x

Data Card

L1

L2 ETY

GbE/FE

VSI/Flow

4

XDM ETHERNET L2 APPLICATION

5

ETHERNET L2 FUNCTIONS 

  

  

  

 

Bridge/Switch Ethernet Frame FDB – Forwarding Data Base FDB Quota VLAN – Virtual LAN QinQ – Double Tagging QoS – Quality of Service Policing BSC – Broadcast Storm Control WRED – Weighted Random Early Discard RSTP – Rapid Spanning Tree Protocol PVID – Port Based Vlan ID 6

BRIDGE / SWITCH 

A bridge is a LAN interconnection device which operates at the data link layer (layer 2)



A Switch is a Multi-Port Bridge.



Divide LAN into segments



IEEE 802.1D –MAC Bridge Standard

7

ETHERNET FRAME

S Destination O Preamble F address

Separates Between frames

Source address

Length/ Type

802.2 header and data

• MAC Address • 48 bits

• Worldwide unique • Assigned at manufacturing • No correlation between addresses and location in network

FCS

Frame Checksum Sequence (CRC)

8

FDB- FORWARDING DATABASE 

A Switch separates the sections by Learning and Filtering



Flooding - Transmits (floods) the frame on all switch interfaces (except the sending port itself)



Forwarding - Sends the frame toward its destination



Aging - Time that an entry remains in the FDB DA

SA

PC2

PC1 Dest. : PC2

I’m PC2 !!! DA PC1 PC 1

1

SA PC2

PC 2

Forwarding Table 2

MAC

Port

PC1

Port 1

PC2

Port 2

9

FDB QUOTA





Protection from MAC address storm effect from one VPN as a result of: 

Malicious users



Incorrect configuration

Solution - Defines the address resources for VPN by setting the FDB quota per S-VLAN

10

VLAN

Ethernet Switch

Ethernet Switch

Ethernet Switch



Separates different users within a network.



Separates broadcast domains.



IEEE 802.1Q –VLAN Tagging Standard 11

VLAN TAG FRAME - CLIENT Destination address

Source address

EtherType 16 bits

802.1q Header

Priority 3 bits

Length/ Type

CFI 1 bit

DATA

FCS

VLAN ID 12 bits



EtherType - 802.1Q Tag Type (0x8100)



Priority - 8 priority levels are defined



CFI – Canonical format Indicator (0 for Ethernet Switch)

12

VLAN TAG FRAME – NETWORK Destination address

Source address

EtherType 16 bits

  

QinQ Tag

CoS 3 bits

C-VLAN header

Length/ Type

DEI 1 bit

DATA

CRC

VLAN ID 12 bits

EtherType - 802.1QinQ Tag Type (0x9100) CoS - 8 priority levels are defined DEI (Drop eligible indicator, Green/Yellow) 

for early congestion avoidance



In 802.1ad (PB), the CFI was changed to DEI 13

QINQ CONCEPT

SDH Transmission Network

Service 1

Service 1

Service 2

Service 2

Service 3

Service 3

Tagged frame - in

Double tagged frame

Tagged frame - out

DA (MAC)

DA (MAC)

DA (MAC)

SA (MAC)

SA (MAC)

SA (MAC)

PBits

CVLAN

IP Packet

CoS

SVLAN

PBits

CVLAN

PBits

CVLAN

IP Packet

IP Packet

14

ETHERNET FRAMES

15

QOS – QUALITY OF SERVICE 

Different applications require different priorities to guarantee a certain level of performance



Packets are classified and marked according to the type of service



These priorities are mapped to 8 levels of QoS (CoS)



CoS levels: 0 (lowest) to 7 (Highest)



High priority traffic will have 

Smaller Packet loss ratio



Smaller Delay



Smaller Delay Variation 16

QOS PRINCIPLES

Classifier

Policer

Forwarding Engine

Congestion Avoidance (WRED)

Congestion Management (Schedule & Queue)

Shaper

17

QOS – TRAFFIC MANAGEMENT 

Classifier - recognizes and distinguishes between different traffic streams



Packets are classified and marked according to the type of service: 

L2 - 802.1p in the VLAN tag



L3 - DSCP or IP Precedence bits in the ToS field of IP header

Classifier

Policer

Forwarding Engine

Congestion Avoidance (WRED)

Congestion Management (Schedule & Queue)

Shaper

18

TRAFFIC CLASSIFICATIONS L3 - DiffServ Code Point (DSCP) Name

CS0

Space 000000

CS1

001000

CS2

010000

CS3

011000

CS4

100000

CS5

101000

CS6 CS7 AF11

110000 111000 001010

AF12 AF13 AF21

001100 001110 010010

AF22

010100

AF23

010110

AF31 AF32 AF33 AF41

011010 011100 011110 100010

AF42

100100

AF43 EF PHB

100110 101110

L2 – 802.1p/ VLAN Tag 802.1Q

Transport CoS

Reference

RFC 2474

Priority bits

Space

0

000

1

001

2

Name

Space

CoS 0

000

CoS 1

001

010

CoS 2

010

3

011

CoS 3

011

4

100

CoS 4

100

5

101

CoS 5

101

6

110

CoS 6

110

7

111

CoS 7

111

RFC 2597

RFC 3246

19

POLICING 

A way to limit bandwidth on a shared media network



Customer traffic is policed on the ingress port



Policing is done per VLAN and per QoS on each port

Classifier

Policer

Forwarding Engine

Congestion Avoidance (WRED)

Congestion Management (Schedule & Queue)

Shaper

20

POLICING 

The client is forced to comply with bandwidth profiles defined by the service provider including: 

CIR - Committed Information Rate



CBS - Committed Burst Size



EIR - Excess Information Rate



EBS - Excess Burst Size

Single Rate Policer

Drop Zone

Red/Dropped

EIR

Yellow

CIR

Green

Link Rate

Two Rate Policer

Single Rate - Suitable policer for EIS cards in XDM and MESW/ESW in BG 21

COLORING PRINCIPLES U

Switch buffer per port

WRED

P T Rx Buffer Tx Buffer

Classifier

F I B

Policer CIR

C B S

E B S

F F

F F

COS6 COS5

EIR

F

COS7

F i L t e r

COS4 COS3 COS2

S C H E D U L E R

S H A P E R

COS1 COS0

UNI/E-NNI (Client)

NNI/MoT (Network)

22

MEF BW PROFILE PARAMETERS 

Policer profile is extended according to MEF5, also includes CM and CF parameters



Color Mode (CM):







Color Blind



Color Aware

Coupling Flag (CF): 

Uncoupled



Coupled

When working in Color Blind mode, Coupling Flag is Uncoupled and disabled

23

BW PROFILE - BY TOKEN BUCKET CF =0: Two token “Green” Tokens

Committed Information Rate (CIR)

buffers operate independently

CF =1: Unused tokens from the C-bucket added to the E-bucket

Overflow

Committed Burst Size (CBS)

C-Bucket CF = 0: “Yellow” Tokens CF = 1: “Green” + “Yellow” Tokens

Excess Information Rate (EIR)

Overflow

Excess Burst Size (EBS)

E-Bucket 24

Data Rate [Kbps]

POLICER RATES

EBS

EIR

CBS

CIR

time 25

QOS – TRAFFIC MANAGEMENT Congestion Avoidance 

Tail Drop



RED – Random Early Detection



WRED – Weight Random Early Detection

1 Drop Probability



Yellow

0 MinY

Classifier

Policer

Forwarding Engine

Average Queue size

Green

MaxY MinG

Congestion Avoidance (WRED)

MaxG

Congestion Management (Schedule & Queue)

Shaper

26

RED – RANDOM EARLY DISCARD 

Oversubscription – more frames are coming in than going out



With RED, frames start to be dropped before the buffer overflows



Frames are dropped statistically thus only few of the TCP-IP sessions are affected Drop Probability Dropped

RED Start RED Stop

RED Start + REDQRange

Drop probability is defined by the CoS and Buffer size allowed for the port

Queue Size

27

WRED YELLOW/GREEN CURVES

Drop probability 1

Policer CIR=0, EIR=100M CoS 0..7 to 0

Drop probability

Max p

Min y

Yellow Green Max y Min g Max g Average queue size

100 M Utilization

100M Utilization

Policer CIR=100M, EIS= 10M CoS 0..7 to 0

V S I

V S I

All Yellow Packets of CoS 0

All Green Packets of CoS 0

Green Packets due to better Curve

SUMMARY - HOW THE TRAFFIC FLOWS… CIR = 10Mb, CBS = 10KB WAN Port

LAN Port F

100M

Rx Buffer

CMP

F

Policer

Rx Buffer

CoS 6

F

Tx Buffer

Tx Buffer

CoS 7

F

CoS 5

CoS 4

100M

Rx Buffer

CMP

Policer

RED

CoS 3

Random Early Discard

CoS 2

WAN Port

Tx Buffer Rx Buffer CoS 1

Tx Buffer CoS 0 Shared Buffer

SWITCH

29.26

EoS L1 & L2

29

QOS – TRAFFIC MANAGEMENT Congestion management 



Scheduling: 

Fair Queuing – based on statistical multiplexing to allow several data flows to fairly share the link capacity



Priority Queuing - packets belonging to one priority class of traffic are sent before all lower priority traffic to ensure timely delivery of those packets

Shaper - regulates the outgoing traffic flow to a configured bit rate by queuing excess traffic in to a smooth outburst

Classifier

Policer

Forwarding Engine

Congestion Avoidance (WRED)

Congestion Management (Schedule & Queue)

Shaper

30

QOS – TRAFFIC MANAGEMENT 

QoS main implementations: 

Strict Priority – Higher CoS will be served first



WRR – Weighted Round Robin 

Higher CoS (default Cos 6, 7) - Strict Priority



Lower CoS (default CoS 0 -5) - WRR

Classifier

Policer

Forwarding Engine

Congestion Avoidance (WRED)

Congestion Management (Schedule & Queue)

Shaper

31

BSC – BROADCAST STORM CONTROL



Protection from an excessive number of broadcast packets



BSC policer drops broadcast packets exceeding the BSC rate

32

RSTP 

Rapid Spanning Tree Protocol



RSTP is a loop resolution protocol



IEEE 802.1W



BPDU – Bridge Protocol Data Unit

33

PVID 

Port based VLAN ID: untagged traffic can be forwarded with VLAN tag (regular switch operation)



User can also define the C-VLAN priority bits Untagged

Tagged

10 Tagged

10

PVID

34

SUMMARY 

L2 concept



L2 functions 

Ethernet Frame



FDB – Forwarding Data Base



FDB Quota



VLAN – Virtual LAN



QinQ – Double Tagging



QoS – Quality of Service



Policing



BSC – Broadcast Storm Control



WRED – Weighted Random Early Discard



RSTP – Rapid Spanning Tree Protocol



PVID – Port Based VLAN ID

35

MPLS INTRODUCTION AND FUNCTIONALITY LightSoft Global Services Division ECI Training Department

CONTENT 

What is MPLS?



MPLS Terms



Label Structure



Tunnels Types



MPLS Services

2

WHAT IS MPLS ? 

MPLS – Multiprotocol Label Switching 

Carries many kinds of traffic (IP, ATM, Ethernet etc.)



Layer 2.5 – Lies between layer 2 and layer 3



Provides a connection-oriented service



Packet switching network

L3

IP

IP MPLS

L2

L1

ATM, FR, Ethernet, PPP

ATM, FR, Ethernet, PPP

SDH, WDM

SDH, WDM

3

DYNAMIC MPLS VS. STATIC MPLS

4

MPLS MOTIVATION New York San Francisco

LSP



MPLS LSP – Label Switched Path 

LSP - Tunnel



Tunnel creation across a network



Bandwidth Allocation across the network



Tunnel with relevant CoS



Tunnel is Unidirectional 5

LABEL SWITCHING ROUTERS LER LER San Francisco

New York LSR

LSR

LSP



Label-Edge Router (LER) - PE 





Assign Initial Label to a FEC in Ingress Remove Label at Egress and return the original packet

Label-Switch Router (LSR) - P  



Forwards MPLS packets using label-switching Capable of forwarding native IP/ETH packets Executes one or more IP routing protocols 6

MPLS – TECHNICAL SIGNIFICANCES 

TE – Traffic Engineering



Service Provider (SP) can guarantee QoS



VPN - Provides Layer 2 Virtual Private Network



When traffic traverse the network it can have the following encapsulation:

Frame Relay Label Header PPP Header (Packet over SONET/SDH) LAN MAC Label Header

Frame Relay

Label Header

PPP Header

Label Header

Layer 3 Header

Label Header

Layer 3 Header

MAC Header

Layer 3 Header

7

MPLS LABEL STRUCTURE Label







Carries the actual value of the label



2^20=1M entries in a routing table

Data

Exp (3bits):Experimental bits Used for Priority or QoS

S (1bits):Bottom of Stack flag 



TTL

Label (20bits)





Exp S

Can stack multiple labels

TTL (8bits):Time to Live 

Counter for Loop prevention

8

MPLS CONTROL PLANE VS. DATA PLANE Control Plane 

Path (Tunnel) Selection Connection-Oriented Vs. Connection-Less



Label Distribution Methods 

Determine labels to nodes by management



Distribute label by signaling RSVP-TE/LDP

Data/Forwarding Plane 

FEC – Forwarding Equivalency Class



Looking up a label in the table



Label Pushing, Swapping and Popping



TTL decreasing and checking 9

MPLS LABELS Ethernet

MPLS Label

MPLS Ethernet

Original packet (e.g. Ethernet)

VPN ID (Label)

MAC Header Tunnel Label

Ethernet

VC Label

MAC Header

Data

Link layer Address, Can be: (1) Ethernet (2) PPP (3) Frame Relay

10

ETHERNET/MPLS TRAFFIC FLOW – MOT

11

LABEL SWITCHING 

MPLS is connection-oriented protocol



Provisioning labels to tunnels – done by Signaling/NMS



Data packets can be transferred over the tunnel

In Port

Out Port

12

LABELS 

Tunnel Label – the outer MPLS label – represents the tunnel to which the packet is mapped to



VC Label – the inner MPLS label - which represents the pseudo wire (PW) to which the packet belongs, serves as an edge-to-edge pseudo wire (PWE3), it allows aggregating multiple services into a single tunnel

ETH

T V ETH

T V ETH

ETH

CE

CE Source PE

T

Tunnel Label

V

P VC Label

ETH

Dest PE Payload

13

TUNNEL TYPES 

P2P tunnel - originates at the source PE, traverses through Transit Ps, and terminates at the destination PE



P2MP Tunnel - originates at the source PE and terminates at multiple destination PEs. It is a tree-and-branch structure, CE where packet replication occurs at branching points along the tree CE PE 4

PE 2

CE PE 1

PE 5

P1

CE PE 3

14

VPWS APPLICATION 

VPWS - Virtual Private Wire Service



P2P connectivity over MPLS



Pseudo-Wire (PW) - shares the same tunnel



No MAC Learning

15

VPLS APPLICATION 

VPLS - Virtual Private LAN Service



Multipoint connectivity over MPLS



Fully-meshed LSP tunnels are needed



Learning and Aging MAC addresses on a per LSP basis

16

VPLS ISSUES 



Fully Meshed Architecture 

A core architecture of 10 nodes, requires 90 unidirectional tunnels



A network of 60 nodes requires 3540 unidirectional tunnels (n2 – n tunnels)



Each unknown packet has to go through n-1 pseudo-wires

Solutions 

Use Advanced Ethernet Package to scale Ethernet domains beyond standard Ethernet, and keep MPLS core network manageable



Use H-VPLS (Hierarchical VPLS) to scale the MPLS network 

Hub and Spoke architecture

17

H-VPLS 

Eliminates the need for full mesh to include spokes



Reduces signaling overhead (fewer VC-LSPs)



Simplifies discovery (a spoke is only aware of upstream PE)



Scalable inter-metro VPLS using SHG (Split Horizon Group) VLANs, Stacked VLANs or VC Labels

MTU = Multi-Tenant Unit MTU

MTU

MTU

PE

MTU PE

Spoke VCs MTU

PE

MTU PE

PE

MTU

PE MTU

MTU

PE

MTU

PE

MTU

MTU MTU

Hub VCs MTU

18

18

HUB & SPOKES APPLICATION Hub & Spoke (Partial Mesh) Pseudo-wires CE (Spoke)

CE (Hub) Customer B

MCS-PE

MCS-PE Tunnels

Customer B

CE (Spoke) Customer B MCS-PE

19

ROOTEDMP APPLICATION (E-TREE) 

RootedMP (Multi Point) Multicast Service 

IGMP snooping

TV Channels Source



MPLS TE enforcement



VC label (VPN) configured by NMS

IPTV/BTV Head-end Router P2MP Multicast

MCS-PE

Tunnel (Tree)

Hub and Spoke

Pseudo-wires MCS-P

IGMP Snooping

MCS-PE

MCS-PE

MCS-PE

Ethernet DSLAM

Customer s

DSLAM

Customer s

DSLAM

Customer s 20

VSI 

VSI – (Ethernet) Virtual Switch Instance 

Regular Ethernet switch will flood traffic to all ports when a new MAC needs to be learned



With VSI in the ports, traffic attached to the VSI will be flooded

Ethernet

VSI Ethernet Switch

Ethernet Port 1

VCG (WAN) port 1

T VC Ethernet

VCG (WAN) port 2

T VC Ethernet

VSI A Ethernet

Ethernet Port 2 Ethernet

VSI B

Ethernet Port 3

MPLS Switch

Ethernet

Ethernet Port 4

Mapper

Ethernet Port N-1 VSI N Ethernet Port N

VCG (WAN) port N

21

ETHERNET-ACCESS AND VPLS PB: Provider Bridge Customer

A

UME: ETX

ETH I-NNI MCS

PB Network

BG-9300

LightSoft

MCS-PE

MPLS Based Network

MoE

ETH E-NNI Customer

A

ETH UNI B

B

ETH based MPLS-TP Network

MCS-PE

Customer

Customer

MPLS I-NNI

PB (Tellabs) Network Customer

B



End-to-End Ethernet Service Provisioning Across MPLS and PB network 

MPLS Network (PE – Provider Edge)



Ethernet Network (PB – Provider Bridge)



MPLS & PB (ETH-VPLS)



UME Access devices 22

MPLS TERMS 





Tunnel Types



NE Types



P2P



P (Transit)



P2MP



PE (Ingress / Egress) 

Service Types 

PE ID

Label Types



P2P



MP2MP



Tunnel Label



Rooted MP



VC Label



P2MP





Port Types 

MOT Port



MOE Port

CoS Mapping



VSI COS == Tunnel COS

Connection Types 

UNI



NNI 23

SUMMARY 

Technical differences between MPLS and Ethernet



MPLS Encapsulation



MPLS Terms: 

LSP - Tunnels



LER and LSR



Control Plane and Data Plane



Label Switching



MPLS applications



VSI

24

NPT-1020

Global Services Division ECI Training Department

V.4

CONTENT

 Main

features  Product layout  Common modules  Matrices  I/O modules

2

NPT-1020 MAIN FEATURES  1U,

front access connectors

 10 G / 60G packet capacity 

Packet processing up to 10G (GE based configuration) 



Built in central 10G switching NPU

Packet processing up to 60G (10GE based configuration) 

By Tslot unique central switching card (CPS50)

 2.5G TDM matrix  From

64Kbps up to 10 Gbps (10GE)  CES and native TDM support

3

NPT-1020 MAIN FEATURES

 From

64Kbps up to 10 Gbps (STM-64 and n x10GE)  CES and native TDM support  Built in Power over Ethernet support (PoE+)  Expansion options 

Add-on expansion unit – EXT-2U

 SNCP,

MSP 1+1

4

NPT BUILDING BLOCKS

 Packet 

Switching:

New Centralized Packet TDM Switch –CPTS

 MPLS-TP

Functionality:



Support for bidirectional tunnel service



MPLS-TP tunnel OAM

 Synchronization: 

supporting for both SyncE and IEEE 1588v2

5

NPT BUILDING BLOCKS  Enhanced   

protection:

FRR for link and node protection PW redundancy supporting dual homing topology MPLS-TP 1:1 linear protection based on BFD OAM

 OAM:  

Service OAM based on Y.1731 Performance monitoring OAM based Y.1731:  

Delay, jitter and packet loss measurement MNS PM reports support

6

CPS – CENTRAL PACKET SWITCH  CPS50    

Up to 50G packet processing for 10GE based configuration Central packet switch card located in T-slot with ports of 4 x 10GE or 2 x 10GE + 4 x GE Ports 1&2: 10GbE SPF+ based Ports 3&4:10GbE SPF+ based or GbE (CSFP or SPF)

1

2

3

4 7

The NPT-1020 – Product Layout

8

CPTS A new Centralized hybrid matrix for supporting any-toany data cards connectivity in addition to the TDM switching capacity Centralized Packet and TDM Switch (CPTS)

Enables the option for any-to-any data cards connectivity in addition to the TDM switching capacity

TDM

TDM Matrix

TDM

Packet

Packet Packet Switch Packet

Native Packet Native TDM

Packet

CES EoS

9

PACKET VS. TDM

Packet

STM16/64

TDM

 Native Eth./MPLS-TP  EoS / MoT NPT

E1 ETH

NPT

NPT

NPT

NPT

TDM  Native TDM  CES

GigE/10GigE Fiber

Ethernet

10

PACKET VS. TDM

Ethernet CES

Ethernet

MPLS-TP/ Eth. Packet Switch

TDM Matrix TDM

TDM EoS

Packet

TDM

From 10 Mbps to 10 Gbps I/F

From E1 to STM-64 I/F

MPLT-TP/Ethernet switch

HO/LO matrix

Packet synchronization

EoS

Circuit emulation (CES)

MPLSoSDH [MoT]

11

TSLOT MODULES – PDH PME1_21

• 21 balanced E1s • Unbalanced mode is Supported via an xDDF-21 converter

PM345_3

3 E3/DS3 ports, configurable independently

PME1_63

• 63 balanced E1s 12

TSLOT MODULES – SDH SMD1B Dual STM1, SFP based

SMS4 Single STM-4 SFP based

CES CARDS

DMCES1_4  CES matrix card supporting circuit emulation interworking function (CES IWF)  TDM interfaces – supporting 4xSTM-1  CES interface – one SFP based GbE port on the front panel

CES port

4 TDM ports 14

CES CARDS MSE1_16

Multi service card supports up to 16 x E1 for CES services

MSC_2_8 COMBO CES with 2 x STM-1/OC-3 and 8 x E1/T1

15

TSLOT MODULES – DATA – PURE PACKET DHGE_4E

• supports up to 4x10/100/1000 Base-T • Supports PoE+

DHGE_8

Packet card supports up to 4 x 100/1000 Base-X (SFP based only)

CPS50- up to 50G packet processing for 10GE based configuration

16

NPT-1020 ARCHITECTURE

NPT-1020 ARCHITECTURE WITH CPS50

18

SUMMARY  Main

Features  Product Layout  Common Modules  Matrices  I/O Modules

19

NPT-1200

Global Services Division ECI Training Department

V.4

CONTENT  Main

features  Product layout  Common modules  Matrices  I/O Modules

2

NPT-1200 MAIN FEATURES 2U, front access connectors  Up to 320G packet capacity  40 Gb/s TDM matrix  From 64Kbps up to 10 Gbps (STM-64 and n x10GE)  CES and native TDM support  Built in Power over Ethernet support (PoE+)  EXT-2U – 2U Expansion unit for additional 3 traffic IO cards ■ Full interoperability with XDM and BG equipment and management 

3

THE NPT-1200 PRODUCT LAYOUT

4

COMMON CARDS

 INF-1200  

550W

DC power feed with input filtering Supports hot insertion and redundancy (2 x INF-1200)

 FCU-1200

Pluggable fan control unit  8 independent fans  3 speed modes controlled by MCP according to temperature and fan failure 

5

COMMON CARDS  MCP1200       

Main control card One MCP1200 card with a dedicated slot Fast Ethernet management/LCT connection Uses 1G CF type replaceable NVM External synchronization interface(T3/T4) Auxiliary connector (SCSI 36) for the ICP_MCP1200 connection panel : V.11, Alarms Out, OW, Debug 32 RS ports, 32 MS ports and 2 DCC clear channel

6

MATRICES The NPT-1200 can operate with different matrix cards:  CPS/CPTS100: Matrix card that provides native packet switching only. With or with or without TDM support.  CPS/CPTS320:

Matrix card that provides native packet switching only. With or with or without TDM support.

 XIO16_4&

XIO64: TDM matrices cards that provide TDM only cross connecting 7

CPTS - CENTRALIZED PACKET & TDM SWITCH

 CPTS 100

TDM & Packet Fully 40G low/high order TDM with 2 x STM-1/4/16 or one STM-64 port & Central 100G Packet switching with 2 x 10GE 8

CPTS - CENTRALIZED PACKET & TDM SWITCH  CPTS 320

TDM & Packet Fully 40G low/high order TDM with 2 x STM-1/4/16 or one STM-64 port & Central 320G Packet switching with 4 x 10GE 9

PACKET VS. TDM

Packet

STM16/64

TDM

 Native Eth./MPLS-TP  EoS / MoT NPT

E1 ETH

NPT

NPT

NPT

NPT

TDM  Native TDM  CES

GigE/10GigE Fiber

Ethernet

10

PACKET VS. TDM

Ethernet CES

Ethernet

MPLS-TP/ Eth. Packet Switch

TDM Matrix TDM

TDM EoS

Packet

TDM

From 10 Mbps to 10 Gbps I/F

From E1 to STM-64 I/F

MPLT-TP/Ethernet switch

HO/LO matrix

Packet synchronization

EoS

Circuit emulation (CES)

MPLSoS

11

CPTS 100 A new Centralized hybrid matrix for supporting any-toany data cards connectivity in addition to the TDM switching capacity Enables the option for any-to-any data cards connectivity in addition to the 40G TDM switching capacity

Centralized Packet and TDM Switch (CPTS) TDM

TDM Matrix

TDM

Packet

Packet Packet Switch

Packet

Native Packet Native TDM

Packet

CES EoS

12

NPT-1200 – 100G ARCHITECTURE OHA AUX TMN LS LCT EMS G.703 V.11

NPT-1200

EXT-2U Controller

2.5G/20G Tslot 1#

CPTS100 2.5G/20G

Tslot 2#

40G TDM Matrix

2.5G/20G

Tslot 3#

Tslot 4#

622M/ 2GE Eslot 1#

622M/ 2GE

2.5G/20G

Eslot 2#

100G Packet Switch

2.5G Tslot 5# 2.5G/20G

622M/ 2GE Eslot 3#

Tslot 6#

Tslot 7#

2.5G/20G

Synchronization

2 Mbps

STN-n SDH

E1

1588 V2

13

CPS - CENTRALIZED PACKET SWITCH  CPS 100

Packet Central 100G Packet switching with 2 x 10GE

14

CPS - CENTRALIZED PACKET SWITCH  CPS 320

Packet Central 320G Packet switching with 4 x 10GE 15

TDM BASED MATRIX

 XIO64 

 

Redundant matrix and TMU STM-64 XFP housing Capacity of 256*VC4 with VC4/VC3/VC12 granularity

16

TDM BASED MATRIX

 XIO16_4   

Redundant matrix and TMU Four STM1/4/16 independently configured ports Capacity of 256*VC4 with VC4/VC3/VC12 granularity

17

THE NPT-1200 – BW ALLOCATION

ES3 INF – E2U

622M / 2 x GEs FCU-E2U

ES2

2U

622M / 2 x GEs INF - E2U

EXT-2U

FCU-50

ES1

622M / 2 x GEs TS5 INF-1200

2.5G

TS6

2.5G/ 20 GE

CPTS100

2U

2.5G/ 20 GE TS4

2 x 10GE + 2 x STM-16 or 1 x STM-64 INF-1200

TS7

CPTS100

TS3

2 x 10GE + 2 x STM-16 or 1 x STM-64

2.5G/ 20 GE

MCP1200

TS1

2.5G/ 20 GE

465mm

NPT-1200

2.5G/ 20 GE FCU1200

FCU-50

TS2

2.5G/ 20 GE

243mm

TSLOT MODULES – PDH PME1_21

PM345_3

• 21 balanced E1s • Unbalanced mode is supported 3 E3/DS3 ports, configurable independently via an xDDF-21 converter PME1_63

• 63 balanced E1s 19

TSLOT MODULES – SDH SMQ1&4

SMQ1

Quad STM1/4, SFP based

Quad STM1o/e, SFP based

SMS16

Single STM-4 or 16 I/O, SFP based

TSLOT MODULES – DATA – LAYER 1 DMFX_4_L1

DMFE_4_L1

Quad FE L1 Ethernet card

Quad FX L1 Ethernet card

DMGE_4_L1

Quad GE L1 Ethernet card

DATA CARDS – LAYER 1

Card

Type

LAN Interface

EoS WAN Interface

DMFE_4_L1

10/100BaseT

4

4 (Up to 4xVC4)

DMFX_4_L1

Optical Fast Ethernet (SFP)

4

4 (Up to 4xVC4)

DMGE_4_L1

Gigabit Ethernet (GbE)

4

4 (Up to 16xVC4)

TSLOT MODULES – DATA – LAYER 2 DMFE_4_L2

Quad FE L2 Ethernet card with MPLS functionality

DMFX_4_L2

Quad FX L2 Ethernet card with MPLS functionality

DMEoP_4

Quad FE- Ethernet Over PDH 23

TSLOT MODULES – DATA – LAYER 2 DMGE_2_L2

Dual GE L2 Ethernet port with MPLS functionality

DMGE_4_L2

Quad GE L2 Ethernet port with MPLS functionality

DMGE_8_L2 • 2 COMBO ports supporting Optical • Double-slot card GbE / Electrical 1000/100/10 Mbit • Up to 2 cards supported in • 6 optical/electrical GbE SFP based ports a NPT-1200 shelf

24

TSLOT MODULES – DATA – LAYER 2 DMXE_48_L2 •

•

Double Tslot (TS1 & TS2 ,TS6 & TS7) Supports up to: • • •

•

96WAN ports (32 x VC-4) Up to 8 x GE ports 4 x 10GE ports

Supports PB (Provider Bridge) and MPLS functionality

DMXE_22_L2 Dual 10GE and GE L2 Ethernet port with MPLS functionality

25

DATA CARDS – LAYER 2

Card

Type

LAN Interfaces

EoS WAN Interfaces

DMFE_4_L2

10/100BaseT

4

8 (Up to 4xVC4)

DMFX_4_L2

Optical Fast Ethernet (SFP)

4

8 (Up to 4xVC4)

*DMEoP_4

10/100BaseT

4

16xEoP (Up to 32xE1)



All Layer 2 cards support MPLS (except DMEoP_4)) 26

DATA CARDS – LAYER 2 Card

Type

LAN Interfaces

EoS WAN Interfaces

DMGE_2_L2

Gigabit Ethernet (GbE)

2

64 (Up to 16xVC4)

DMGE_4_L2

Gigabit Ethernet (GbE)

4

64 (Up to 16xVC4)

DMGE_8_L2

Gigabit Ethernet (GbE)

8

96 (Up to 32xVC4)

DMXE_48_L2

GbE/10GbE

8 x GbE 4 x 10GbE

96 (Up to 32xVC4)

DMXE_22_L2

GbE/10GbE

2 X 10GbE 2 X 1GbE

64 (Up to 16xVC4)

27

TSLOT MODULES – DATA – PURE PACKET DHGE_4E

• supports up to 4x10/100/1000 Base-T • Supports PoE+

DHGE_8

• Packet card supports up to 8 x 100/1000 Base-X with 4 CSFP

DHGE_16E • Double slot card and up to 2 cards supported in a shelf • Packet card supports up to 8 x 10/100/1000 Base-T and up to 8 x 100/1000 Base-X with 4 CSFP 28

TSLOT MODULES – DATA – PURE PACKET DHGE_24 • Double slot card and up to 2 cards supported in a shelf • Packet card supports up to 24 x 1GbE with 12 CSFP or any mixture with regular SPFs

DHXE_2 • Supports up to 2 x 10GE ports with connection to the packet switching matrix

29

TSLOT MODULES – DATA – PURE PACKET

DHXE_4 • Supports up to 4 x 10GE ports with connection to the packet switching matrix

30

CES CARDS DMCES1_4 • CES matrix card supporting circuit emulation interworking function (CES IWF) • TDM interfaces – supporting 4xSTM-1 • CES interface – either from the SFP based GbE port on the front panel or through the backplane to one of the MoE ports

SME1_16 • Multi service card supports up to 16 x E1

31

CES CARDS

MSC_2_8 • New Multi Service combo card supports 2 x STM1/OC3 ports & 8 xE1/T1s

32

SUMMARY  Main

features  Product layout  Common modules 

INF, FCU, MCP

 Matrices 

 I/O 

CPTS, CPS, XIO64 and XIO16_4

Modules I/O Modules – PDH, SDH, DATA and CES

33

LCT-APT NPT-1200 NE CONFIGURATION

Global Services Division ECI Training Department

CONTENT – Main window  Operation mode  Basic Attributes  Timing  IP Setting  Slot Assignment  Port configuration example  DCC XC  LCT License  LCT

2

PREPARING THE PC … SET THE IP ADDRESS  In

the PC Internet Protocol (TCP/IP) properties :

 Change

the IP Address to match your element's Ethernet IP address

3

GETTING STARTED… Double click the LCT icon  The window below opens 

Insert the NE Ethernet IP  Insert the User Name and Password  Check “Fully Upload”  Ping first to check connectivity  Press Login 

4

LCT – MAIN WINDOW

Menu Bar

Working Modes

Objects Tree

Working Area is divided by Tabs – each tab represents the relevant information according to the working mode that is chosen 5

OPERATION MODE  By

default the LCT mode is in Monitor mode

In the main window, go to Advance -> Request to log in as Master

6

BASIC ATTRIBUTES 2

1

1. 2. 3. 4.

Select the NPT icon Go to “NE Setting” tab Press the refresh button Give the NE Name/Location etc.

7

NE TIME OF DAY 1.

Press the refresh button

2.

Press on the calendar icon to set the date for today Apply

3.

8

IP SETTING

In this window we can change the NE connection mode and set the ip

9

SLOT ASSIGNMENT

10

REASSIGNMENT  Reassignment

is changing the expected equipment type to a new but compatible type, logically in a slot

11

SLOT ASSIGNMENT

Get Logical Card – view the logically assigned cards (expected)  Get Physical Card – view the actual cards  Set As Logical- automatically assign the physical cards 

12

TIMING CONFIGURATION 2

1.

2. 3.

1

Expand the Control and Physical object and select the TMU option Select the Timing Setting tab Remove the v from the internal timing checkbox

3

4. Set the priority for the clock reference

13

TIMING CONFIGURATION

14

CARD CONFIGURATION EXAMPLE

2

1

J0 pattern C2 Signal Labe 15

PORT CONFIGURATION EXAMPLE 1. Expand the optical module and click on the optical port 2. in the configuration mode go to the rate setting tab & change the rate if needed, press on “Apply” 3

1

3. Set the SFP type and the application code according the used SFP

2

16

DCC CROSS CONNECTS 2 3 1

1. 2. 3.

Select the element Select “Services” as the work mode Go to the “DCC XC List” tab and click on the Upload icon

for uploading the XC to the LCT DB

17

DCC CROSS CONNECTS Click on the Upload button to view the XC

Overwrite – update the DB according the uploaded XCs from the element

18

DCC CROSS CONNECTS

1

2

3

1. 2. 3.

Select the optical port for the requested DCC XC Under the MCP card, select the COM port Active XC 19

DCC XC LIST

20

LICENSE UPGRADE  When

the 90 days trial of the LCT license expires the following message appears when you try to connect  Connection to the EMS server is required

1

21

LICENSE UPGRADE  Set

the connection to the EMS server: 2

Server IP – the IP address of the EMS server Port – logical port to use for delivering the license

3

4 22

SUMMARY – Main window  Operation mode  Basic Attributes  Timing  IP Setting  Slot Assignment  DCC XC  LCT License  LCT

23

APT INTRODUCTION

Global Services Division ECI Training Department

CONTENTS  LCT-APT  EMS-APT  LightSoft

Integration

2

APT FCAPS  FCAPS-

Fault, Configuration, Administration, Performance and Security

Fault-Recognizes, isolates, corrects and logs the faults APT Configuration-Simplifies gathering and storing device configurations Administration - Establishing users, passwords and permissions/rights 3

APT FCAPS Performance – Monitoring performance data to determine the health and efficiency of the current network

APT

Security- Controlling access to assets in the network

4

LCT-APT LICENSING 

Each LCT requires a license to activate it   

Licenses are controlled from the EMS EMS-APT maintains an LCT license bank, each LCT activation withdraws one license from the bank After installing the LCT, user should connect the LCT host to the EMS. EMS checks the LCT license in the bank and enables the operation



The LCT license is bound with the LCT host ID and activated by EMS-APT



A temporary license (90 days) is provided to allow using the LCT when there is no connection to the EMS-APT 5

EMS-APT  Based

on a Java platform  Supports two working modes  

Standalone Integrated with NMS LightSoft

 Provides

full management of BG networks  Server-Client architecture  Provides a wide range of management functions, including alarms, configuration, inventory, provisioning, and security management 6

EMS-APT  Supports   

multiple operating systems:

Solaris LINUX (client only) WINDOWS

 Supports

up to 30 concurrent users  Up to 3000 NEs  Introduces a user friendly licensing mechanism that eliminates the need of a hardware protection device

7

EMS-APT

8

INTEGRATION WITH LIGHTSOFT  The

EMS-BGF is fully integrated into LightSoft  The following functions are provided:  

BGs and NPTs icons in all LightSoft topology views EMS created/uploaded in LS

 Trail 



management

Uploads all types of trails to LS including EOS, MoT and MoE Creates/deletes all types of trails via LS

 Unified

alarm management  Opens EMS/NE/Shelf/Card/Object via GUI Cut Through (GCT)  GCT supports multi users 9

LIGHTSOFT USER INTERFACE VIEW

NE MANAGEMENT There is more than one way to manage an element:  Ethernet only  Via Ethernet cable, cannot manage additional elements

 Gateway  Via Ethernet cable  DCC IP + Ethernet IP  Can manage remote elements via SDH overhead DCC

 DCC only  DCC IP, cannot manage the element via Ethernet port

 In-Band management via native Ethernet  In band management is an Ethernet based management channel that runs over MoE or Ethernet PB links

NE MANAGEMENT Ethernet Cable Ethernet Only

G.W

EMS-APT

DCC only

Ethernet Cable

DCC only

EMS-APT INSTALLATION SCENARIOS - 1

EMS-APT INSTALLATION SCENARIOS - 2

EMS-APT INSTALLATION SCENARIOS - 3

SUMMARY     

LCT-APT and licensing EMS-APT Integration of the EMS-APT with LightSoft NE management EMS-APT installation scenarios

NMS LIGHTSOFT Introduction

Global Services Division ECI Training Department

MANAGEMENT ARCHITECTURE OSS TMF-MTNM Corba I/F Network Management Layer

Element Management Layer

LightSoft

TMF-MTNM Corba I/F EMS-XDM

EMS-BGF

Other EMSs

Managed Equipment XDM line

BG line

Other equipment 2

TABS – NO MORE MENUS  NMS

LightSoft has a modern look and feel

ECI Button

Tabs – no menus

3

ECI BUTTON  ECI

button contains the Help and About LightSoft options  The ECI Button menu cannot be customized

4

LIGHTSOFT RIBBON 

The LightSoft ribbon is maximized or minimized

Minimized



Maximized

To maximize or minimize:   

Double click a tab Ctrl + F1 View tab click on Ribbon 5

QUICK ACCESS AREA

Technology Layers

Consistency Indicators

Alarm Counters

 Above

the ribbon  Static (always visible to user)  Displays: 

 

Technology layers Consistency indicators Alarm counters 6

TECHNOLOGY LAYERS 

LightSoft has traffic from different technology types



You can see the elements processing the different traffic types:   



Optical (WDM, OTN) SDH Ethernet & MPLS

Example: If you go to the ETH/MPLS layer, you see where in your topology you have Ethernet or MPLS cards & traffic 7

TOPOLOGY LAYER TYPES  Physical

(Site)  Physical (EMS)  SDH/SONET  Optical (OTN)  OCH  Ethernet/MPLS

Physical (EMS)

Physical (Site)

SDH/ SONET

Optical (OTN) Ethernet/MPLS 8

EXAMPLE OF LAYERS Physical

(Site): this layer shows your whole network, including 3rd party equipment (technology transparent)

 ETH/MPLS This layer shows your Ethernet and MPLS switches in your network 9

ELEMENTS  ME/NE:

 UME:

Managed/Network Element

Unmanaged Element

 Groups

10

TOPOLOGY LINKS Represent the physical connections between elements  Must be created before provisioning traffic 

1

2

3

11

PROVISIONED TRAFFIC  Trail

List shows the trails in the network

x

x

12

INSERTING AN ELEMENT

Before

After

13

CONSISTENCY INDICATORS

 Show

the inconsistencies between the NMS LightSoft DB and the EMS databases

Client (GUI)

Server (Database)

EMS XDM DB

XDM

EMS BG DB

BroadGate

Other EMS DB Other transport equipment 14

ALARM COUNTERS

 A general

picture of all the alarms in the system

Alarm Color

Alarm types

Red

Severe and Major alarms

Yellow

Minor and Warning alarms

15

CONTEXT SENSITIVE TABS – an accepted industry standard  This tab contains only relevant commands for selected elements (Nodes, Groups and Links)  CST

16

HOT KEYS  Pressing

Alt toggles hot key tips  Once the are tips displayed, type the letter to open that tab – level 1

17

HOT KEYS CONTINUED  When

you go to that tab, you see the hot keys for that tab – level 2

 If

there is more than one letter in the key, pressing the keys should be sequential and not simultaneous i.e. for FC, press F, then C 18

TREE – SEEING THE NETWORK  View

Tree

The Tree shows all MEs in the topology

19

VIEW FUNCTIONS  Zoom

& Navigation Seeing all, or different parts of the topology – moving elements on the screen and saving/not saving changes

 Move

– working with groups of elements (Expanding or collapsing groups)

 Map

Map

Move

Zoom & Navigation 20

SUMMARY Tabs – No More Menus  ECI Button  LightSoft Ribbon 







Minimizing/Maximizing Categories in each tab

Quick Access Area   

Technology layers Consistency indicators Alarm Counters

Context Sensitive Tabs  Hot Keys  Tree, and View menu 

21

WORKING WITH TOPOLOGY LINKS NMS LightSoft

Global Services Division ECI Training Department

TOPOLOGY LINKS  A topology

link represents the physical connection (fiber or copper) between network elements

 A topology

link connects two ports of different objects (MEs, LEs, and UMEs)

 Traffic

trails can only be defined over topology links

2

CREATING A TOPOLOGY LINK 2 1 Select 2 elements to connect 3

3

CREATE TOPOLOGY LINK WINDOW 1 Select rate

2 Select 2 endpoints *Only resources that support the rate selection are available

3 4

CREATE TOPOLOGY LINK ATTRIBUTES

5

CREATE TOPOLOGY LINK ATTRIBUTES Field

Explanation

Technology Layer

Technology layer of the link. Read only according to the port type

Media Type

Media type of the selected ports: Electrical, Fiber, or Virtual. (Read only)

Media Subtype Selection of media subtypes from the list, according to

the media type. You can also enter your own text. Length (km/mile)

The length of the link in kilometers or miles

Protection

Type of link protection, for example, MS-SPRing, MS, external protection, or unprotected. If external protection is used, specify the type.

SRLG (Ducts)

Shared Risk Link Group. Scrollable entry fields allow you to specify the shared resources for the link.

Ring Name

Name of the ring associated with this link 6

CREATE TOPOLOGY LINK ATTRIBUTES Field

Explanation

Assigned Cost (1-1000)

Enter a value for the cost based on your local evaluations of cost on a nondenominational scale of 11000. A low number indicates a less expensive link..

Quality (Best 1..5 Worst)

Select the quality of the link, from 1 (best quality) to 5 (worst quality)

Dispersion (ps*nm/km)

Dispersion rate in ps/nm. User-entered value, not calculated

Span Loss (dB)

Span loss in decibels. User-entered value, not calculated

Path Trace Configuration button

Enables you to set the J0 values of endpoints of a physical connection (Opens a new window)

7

A TOPOLOGY LINK IN LIGHTSOFT  A topology

link appears in the physical (site) layer and in the relevant technology layer

8

TOPOLOGY LINKS COLOR-CODING  Color-coding   



Red – critical or major alarm Orange – minor alarm Yellow – warning Green – clear (no alarms)

 Color-coding 

Light blue



Dark blue



Dark grey White



for operational links:

for non-operational links: – the link is connected and not uploaded (an intermediate state) – the link is being uploaded (intermediate, longer state) – the link is disconnected – inconsistent link 9

INTERNAL LINKS  Internal

link – A link between two ports of one

element  When

an arrow appears next to the ME- it indicates that an internal link exists in the element

Internal link indication

10

VIEWING INTERNAL LINK DETAILS 1

2

11

SUMMARY  Topology  

Links

Between elements Internal links

12

MoE CONFIGURATION NMS LightSoft

Global Services Division ECI Training Department

AGENDA  Switch

configuration  Port configuration  MoE creation

2

MPLS (MoE) PROCEDURE

3

CHANGING SWITCH MODE  By

default the NPT is configured as PB (Provider Bridge) with only L2 capabilities

 For

MPLS capabilities, change the switch mode to PE (Provider Edge)

 Both

NPT, BG and XDM MPLS cards require a license for card activation as a PE

 Each

PE must have a unique identifier, therefore we need to also set the PE_ID of each data card 4

SWITCH CONFIGURATION – NPT 2

1. Click the Switch 2. Go to “Configuration” 3. Set the switching mode to: “MPLS-PE”* 4. Configure a unique PE_ID

1

3

3

 When changing the switch mode to PE, the card automatically draws a license from the EMS license bank 5

MoE PORT DEFINITION

1

2

3

1. Right click the Card 2.Click Activate/Deactivate port 3.Activate the desired port 4.click the Apply button

4

6

SFP CONFIGURATION  Choose

the Expected SFP Type according to the inserted SFP

7

DEFINE MoE PORT

3 4 1 2

1. 2. 3. 4.

Right click the Card Click Define MoE Port Select the desired port Click the Apply button 8

MoE LINKS IN LIGHTSOFT 

Prerequisites: 

1

Traffic Engineering configuration is according to the plan (can be changed later using the Link list):   

2

EXP Mapping CoS CAC

1.Highlight the elements 2.Under the Topology tab, select the Topology Link option 3.Set the port type according to the previously configured port (can also be All Rates) 4.Select the ports on each side (validate that the system sees it as MoE) 5. Apply the changes

3

4

5 9

MoE LINKS & PORTS Physical Site link

ETH/MPLS layer link

The port is automatically enabled

10

SUMMARY

 Switch  

MPLS-PE Unique ID

 Port 

configuration

configuration

SFP configuration

 MoE

creation

11

TE CONFIGURATION IN NMS

Traffic Engineering ( QoS, CAC & EXP) Global Services Division ECI Training Department

AGENDA 

System preferences



QoS



EXP Mapping



CAC on MPLS tunnels



CAC on MPLS services

2

SYSTEM PREFERENCES 

LightSoft preference settings define how trails, tunnels, and Ethernet services are created in LightSoft



Allows to configure system settings for network-wide features such as general TE, CoS, CAC, and EXP mapping preferences



System preferences can only be set by a system administrator and are applied to all server clients

3

QOS IN NMS 

The System Preferences window CoS workspace is used to configure default CoS values for new PEs created in the MPLS Layer

4

QUALITY OF SERVICE 

Priority:

High

Strict priority, committed traffic with low latency. PIR=CIR= Tunnel BW

Low

Fair queuing, have EIR and can accept drops when applicable, PIR = Port BW



Booking factor - Overbooking ratio allowed to tunnels per CoS on this network. 

1.0: Tunnel BW can reach up to 100% of MoT BW (no overbooking)



2.0: Tunnel BW can reach up to 200% of MoT BW

5

QUALITY OF SERVICE 

A CoS can be set as a BE (Best Effort) CoS, which can be associated with zero BW tunnels in order to save bandwidth over the network for BE CoS services aggregation



BE Protection :

Enabled

The Bypass tunnel protects all assigned tunnels regardless of their bandwidth

Disabled

The bandwidth sum of the tunnels protected is limited by the Bypass tunnel bandwidth

6

QUALITY OF SERVICE BE Protection Enabled

BE Protection Disabled

10M Bypass

10M Bypass

A

A

B

C 10M Main

B

C 10M Main

10M Main 10M Main

7

BE IMPLEMENTATION RULES 





BE CoS Enabled

CoS has zero BW and can be set with only zero BW tunnels.

Disabled

Tunnels must have at least a minimum BW.

CoS can be enabled as BE CoS only if: 

it is Low Priority



there are no tunnels with BW using this CoS

On the other hand, you can disable as BE CoS, 

if no tunnels (with zero BW) exist on it causes it to become Low Priority CoS again.

8

EXP – EXPERIMENTAL BITS 

This workspace is used to configure default EXP mapping values on MoE/MoT ports (EXP profile) for new links that are created in the MPLS layer



The EXP column refers to both inside and outside EXP mapping parameters of the port 9

EXP – EXPERIMENTAL BITS 

EXP mapping values on ports of existing links can be changed as long as no tunnels exist on the port



EXP mappings for 1-8 CoS-color combinations are allowed for a port 



For example, 4 CoS instances with both colors, or 8 with one color

The default mapping determines what CoS will be supported on an E-LSP tunnel thus affecting the CoS that will be supported when configuring a service 10

CAC – CONNECTION ADMISSION CONTROL 

CAC is a part of TE – Traffic Management and ensures effective QoS delivery by MPLS networks

11

CAC – CONNECTION ADMISSION CONTROL 

CAC is a set of actions taken when: 

setting up a new tunnel



changing parameters of an existing tunnel



CAC ensures that each tunnel guarantees the expected bandwidth



For the Global domain Define Res BW and Res Shared BW 

Res Shared BW = FRR traffic



Res BW = Regular traffic

12

CAC EXAMPLE 

Applied to verify that the sum of all tunnels cannot exceed the link rate



If link rate (MOT trail) = 100 Mbps (e.g. 2xVC3) then



Tunnels BW ≤ Link rate (for regular traffic; FRR traffic can be different)

FRR Tunnels ≤ 50Mbps

100Mbps

Traffic Tunnels ≤ 50Mbps

13

CAC BW – PARAMETERS MAP Non-Reservable BW (optional) Unallocated shared BW

Port Rate

FRR Shared BW

Free CoS7

Allocated shared BW CoS2 CoS1 CoS0

Unallocated BW

Free Book1

CoS7

Traffic BW

Tunnel BW Tunnel BW

Allocated shared BW CoS2 CoS1 CoS0

Book2

Tunnel BW Tunnel BW

CAC PER LINK 1 2

4 3

15

CAC PER LINK 222

333

The configuration is shown for both endpoints and done per directionmeaning we see the transmitting port always

16

PROVISIONING AN MPLS NETWORK Example 1: 

Traffic & FRR Tunnels in both directions

A

Traffic & FRR Tunnels in both directions

Traffic & FRR tunnels are configured on both sides of the topology B

CAC Setting per link: 50% for traffic 50% for FRR

Management & VOIP traffic

D

C

HSI traffic

17

PROVISIONING AN MPLS NETWORK Example 2:

FRR Tunnels in the other direction on the ring



All traffic tunnels are configured in one direction of the network



All FRRs are in the other direction

Traffic Tunnels in one direction in the ring, meaning bidirectional traffic from A to D:

A

B

D

C

1. A - D 2. D-C-B-A

18

CAC AVAILABILITY MAP 

ETH/MPLS layer ->Tools->Availability Map 

Shows availability of the tunnels

Unshared=Traffic Shared=FRR

19

CAC AVAILABILITY PER LINK 1. Right click the link -> Availability -> CAC

20

CAC AVAILABILITY – PORT LEVEL 2.

Divided into two parts: 

Port Level



COS Level (Next slide)

Traffic half 

FRR half

Port level shows the port % or BW is used – both for traffic and FRR

COS Level – next slide 21

CAC AVAILABILITY – COS LEVEL 

Shows the traffic divided by COS and its availability

22

CAC ON MPLS SERVICES 

CAC for Ethernet Services ensures that a Tunnel has sufficient bandwidth



The sum of the P2P service CIRs assigned to a specific tunnel cannot exceed the tunnel bandwidth



Service CAC is only performed on:  

P2P services Tunnel with “P2P Service Only” selected

23

SUMMARY 

System preferences



QoS



EXP Mapping



CAC on MPLS tunnels







CAC per Domain



CAC per Link

How much BW do I have according to CAC defaults? 

CAC availability map



CAC availability per port

CAC on MPLS services 24

TUNNEL CREATION NMS LightSoft

Global Services Division ECI Training Department

CONTENT  Topology

Link  Tunnel creation   

P2P P2MP Mesh tunnels

2

CREATING TOPOLOGY LINKS IN LIGHTSOFT 

Prerequisites: 

1

Traffic Engineering configuration is according to the plan (can be changed later using the Link list):   

2

EXP Mapping CoS CAC

1.Highlight the elements 2.Under the Topology tab, select the Topology Link option 3.Set the port type according to the previously configured port (can also be All Rates) 4.Select the ports on each side (validate that the system sees it as MoE) 5. Apply the changes

3

4

5 3

CREATING MoE LINKS & PORTS Physical Site link

ETH/MPLS layer link

The port is automatically enabled

4

CREATING A P2P TUNNEL  Example 

In the diagram below we want to create a P2P tunnel from A to B B A

5

CREATING TUNNELS Create Tunnel window

6

BASIC TUNNEL PARAMETERS Protection Desired  Tunnel Type  Directionality  DiffServ  CoS  BW (Mb/s) 

Tunnels are defined by CoS and BW only services with the same CoS pass through that tunnel 7

ENABLING THE ASYMMETRIC SETTING  Bi-directional

tunnels can have different settings for each direction  When asymmetric setting is enabled A-Z and Z-A tabs appear with settings for each direction

8

ADVANCED PARAMETERS Scrolling down reveals advanced parameters: 

Single Service Only 



P2P Service Only 



When MP2MP and P2MP Services don't run on that tunnel

Used for MC-LAG 



When only one service runs on that tunnel

When working with MC-LAG

User Usage State 

Selecting Active prevents the user from deleting the tunnel 9

SELECTING ENDPOINTS – P2P TUNNEL  Tunnels  

are bidirectional

It means that each endpoint is both head and tail Therefore it's not relevant which endpoint is selected first and which second

1. Select the first endpoint

2. Select the second endpoint

3. Complete &Activate 10

EMS APT VIEW – TUNNEL XC

2 3 1

1. Select the Switch 2. Select “Services” as the working mode 3. Select “BD LSP List” tab 11

EMS MPT VIEW – TUNNEL XC 1

2 3

1. Select the port 2. Select “Connections” tab 3. Select “MPLS XC Connections” tab 12

P2MP TUNNEL  Example 

In the diagram below we want to create a P2MP tunnel from A, to B and C

B

A

C

13

SELECTING ENDPOINTS – P2MP TUNNEL  P2MP  

Tunnels:

Head = First selected endpoint All other endpoints are Tails

14

VIEWING CREATED TUNNELS

15

TUNNEL MESH 

Example: In the diagram below we want to create a Tunnel Mesh between C, D and E  

Create a P2P tunnel for each direction and for each endpoint Total of 6 tunnels

B

A

C 16

TUNNEL MESH

17

TUNNEL PARAMETERS Fill in the Basic Parameters: Protection Desired  LSP Type  CoS 



Can be more than one

DiffServ  BW (Mb/s) 

The tunnel type will be P2P by default 18

CREATING A TUNNEL MESH

1. Select the Endpoints

2. Click on the complete button to start the process 19

CREATING A TUNNEL MESH - RESULT 

A total of 20 tunnels were created:

20

VIEWING THE CREATED TUNNELS

21

SUMMARY  Topology 

MoE, MoT

 Tunnel   

Link

creation

P2P P2MP Mesh tunnels

22

FRR TUNNELS NMS LightSoft

Global Services Division ECI Training Department

CONTENT  Creating

and understanding the following MPLS schemes:     

Link Protection Node Protection Protected tunnel Associating tunnels Upgrading tunnel protection

2

REMEMBER  Important!

Tunnels can be unidirectional or bidirectional  To

protect a bidirectional tunnel, first create a protection tunnel in one direction, then again in the opposite direction A

B Main tunnel

Bypass tunnels

3

FRR – FAST REROUTE PROTECTION  A tunnel

connects the head node to the tail node  A tunnel may have intermediate nodes  An FRR protection protects the tunnels by  

Protecting each one of the intermediate nodes and the links between them Protecting the last link to the tail node

A Head

B

Node Protection

D Tail

C

Node Protection

Link Prot. 4

FRR - LINK PROTECTION  Link 

protection only protects a link

For example: In the diagram below protect the link between A and B (NH -Next Hop) Bypass tunnel from A to B through C and D B

A Main tunnel

D

C Bypass tunnel

5

CREATING LINK PROTECTION 

Create a bypass tunnel with Link Protection

Select Bypass  Select Link Protection  Fill in the tunnel parameters 

6

CREATING LINK PROTECTION  Select

endpoints  Select Protected Link 

Select the data direction

 Complete

and Activate

Bypass

7

FRR - NODE PROTECTION 

Node protection protects a node, and the previous link 

For example: Protect node B by creating a tunnel from A to E (NNH – Next next hop)

B

A

E C

Bypass tunnel

D

8

CREATING NODE PROTECTION 

Create a bypass tunnel with Link Protection

Select Bypass  Select Node Protection  Fill in the tunnel parameters 

9

CREATING NODE PROTECTION Select the endpoints  Select the Protected Node 





Select the data direction

Complete and Activate

Head Tail Bypass

10

CREATING A PROTECTED TUNNEL 

A tunnel and its protecting tunnels can be created simultaneously



When creating a protected tunnel  



LightSoft creates the tunnel LightSoft also creates the necessary bypass tunnels for it, if possible

If LightSoft cannot find or create the bypass tunnels, the main tunnel is still created but without the requested level of protection 

Protection may be partial or none

11

CREATING A PROTECTED TUNNEL 

Create a Protected tunnel

Select Bypass  Select Protected FRR 

12

PROTECTED TUNNEL – ADVANCED PARAMETERS 

Using existing bypass tunnels 



Uses existing bypasses only, LightSoft selects the bypass tunnels that provide the highest available protection

Use existing Guarantee full Protection (Unidirectional only): 

LightSoft provides protection using existing bypass tunnels only. Tunnel creation is only completed if all hops can be protected by existing bypasses

13

PROTECTED TUNNEL – ADVANCED PARAMETERS  Auto-create

- FRR: If a hop is not protected, where possible, create new node or link bypasses

 Auto-create

- eFRR: If a hop is not protected, where possible, create a new eFRR or link bypasses

 Full

FRR protection is not guaranteed because if a bypass cannot be created for one or more hops, tunnel creation is still done

14

CREATING A PROTECTED TUNNEL  Fill

in the tunnel parameters on the left

15

CREATING A PROTECTED TUNNEL  Select

the endpoints in the topology window

16

CREATING A PROTECTED TUNNEL  Complete

& Activate

17

TUNNEL LIST AFTER CREATION Via the tunnel list you can see the tunnels LightSoft created

1

1. The protected tunnel 2. Node protection tunnels 3. One link protection tunnel for the last segment

2

3

18

ASSOCIATING TUNNELS  Association  

is required when

a tunnel was created before the bypass tunnel an unprotected tunnel was created after the bypass tunnel

19

DESIRED AND ACTUAL PROTECTION  Protection

Desired – is the protection requested for

the tunnel  Protection Actual – is the protection actually created for the tunnel  

It may differ from Protection Desired For example, if a bypass tunnel is not currently assigned to the protected tunnel

20

UNPROTECTED TO PROTECTED TUNNEL  If

Bypass = first and Protected = second THEN association is automatic

21

UNPROTECTED TO PROTECTED TUNNEL  Use

existing bypass tunnels: Uses existing bypasses only  Auto-create - FRR: Creates a new node or link bypasses  Auto-create - EFRR: Creates a new eFRR or link bypasses

22

UPDATING FRR PROTECTION 

Update the protected tunnel from A to C



See the Trail List to verify the tunnel is protected, and which are its bypass tunnels 23

UPDATING FRR PROTECTION  Update 

FRR Protection:

From partial protection to full protection

24

TUNNEL LIST FOR TUNNEL DETAILS  To

verify that the tunnel is protected, and its bypasses

25

SUMMARY  Creating

Link Protection  Creating Node Protection  

When is each protection scheme used? Each protection scheme is unidirectional or bidirectional

 Creating 

Protected tunnel

Creating simultaneously a tunnel with protection

 Associating

tunnels  Upgrade tunnel protection  Trail List  

Viewing the protection details Viewing which bypass belongs to each Protected tunnel 26

LINEAR PROTECTION 1:1

Global Services Division ECI Training Department

CONTENT  BFD

Introduction  Linear Protection introduction  BD Tunnels  Linear Protection Configuration  BFD Tunnel Session

2

BFD INTRODUCTION  Failures

in connectivity between 2 IP hosts (routers) can be detected by several mechanisms  Most of them are too slow, unreliable or difficult to implement

3

BFD INTRODUCTION Networks use relatively slow "Hello" mechanisms, to detect failures, usually in routing protocols. The times to detect failures ("Detection Times") available in the existing protocols are no better than a second, which is far too long for some applications and represents a great deal of lost data at gigabit rates.

Routing Protocol

4

BFD INTRODUCTION

Detecting a failure by physical interface state, might be problematic in a switched environment

5

BFD GOALS  Provide

low overhead, and short-time detection of

failures  Faster convergence of routing protocols  Provide a single detection mechanism over any media, for any protocol layer, with a wide range of Detection Times and overhead, to avoid the proliferation of different methods  No changes to existing protocols

6

BFD DESIGN  BFD

- Bidirectional Forwarding Detection  BFD operates on top of any data protocol (network layer, link layer, tunnels, etc.) and it is forwarded between two systems  It is always run in unicast, point-to-point mode  BFD

packets are carried in the payload of whatever encapsulating protocol is appropriate for the medium and network

7

BFD PROTOCOL OVERVIEW  BFD

is a simple Hello protocol

 There

is no discovery mechanism in BFD

 A BFD

session is established based on the requirements of the application using it

8

BFD STATES  Session 

Down

A session remains in Down state until the remote system indicates that it agrees the session is down by sending a BFD Control packet with the State field set to anything other than Up

Local

State: 0) Admin Down 1) Down 2) Init

Remote

Session Down 9

LINEAR PROTECTION CONCEPT

 

The 1:1 switching mode means that a protection LSP is used to replace a working LSP in the event the working LSP fails Working and protection LSPs are selected on the ingress node. 



When the links are working properly , the traffic is relayed to the working LSP through the selector on the ingress

While not selected the protection LSP does not carry the traffic transmitted on the working LSP 10

LINEAR PROTECTION CONCEPT

 



After the egress node detects a failure on the working LSP link, user traffic is switched to the protection LSP The egress node sends PSC packets to the ingress node through the backward path to tell the ingress node to perform the switching After the ingress node receives the PSC packets, it switches the selector to the protection LSP and switches the traffic from the working LSP to the protection LSP 11

CC MESSAGES  Continuity

Check (CC) messages allow fast detection of loss of connectivity

 The

CC messages are sent by all nodes periodically and are monitored for Loss Of Continuity (LOC)

12

PROTECTED TUNNEL

PE – Provider Edge P - Provider

MEP – Maintenance End Point MIP – Maintenance Intermediate Point

PSC - Protection State Coordination Protocol

13

CREATING LINEAR PROTECTION  To

create a tunnel with linear protection in a 3 NE ring topology

14

BASIC TUNNEL PARAMETERS     

Protection Desired Tunnel Type Directionality CoS BW (Mb/s)

Tunnels are defined by CoS and BW only services with the same CoS pass through that tunnel 15

CREATING LINEAR PROTECTION

16

CREATING LINEAR PROTECTION  You

can have a different setting for each direction when creating bidirectional tunnels  It is possible to protect only part of the tunnel

17

CREATING LINEAR PROTECTION

Select the endpoints

18

OAM CONFIGURATION

1 2

3

1. Select OAM tab 2. Configure the general parameters 3. Define the BFD intervals

OAM CONFIGURATION

The lowest value is 3.33

20

CREATING LINEAR PROTECTION  After

Complete you will see the paths

21

TUNNEL LIST  In

the Tunnel List we see that the tunnel is protected with Linear Protection

22

CHECKING XCS IN THE EMS  In

the EMS we can see the XCs that are part of the tunnels

BD-Bidirectional LSP-Label Switched Path

23

CHECKING BFDS IN THE EMS  Select

the specific tunnel and BFD Tunnel Session icon to open its BFD sessions

24

CHECKING BFDS IN THE EMS

25

SUMMARY  BFD

Introduction  Linear Protection introduction  BD Tunnels  Linear Protection Configuration  BFD Tunnel Session

26

MPLS - SERVICES EMS-APT Integrated

Global Services Division ECI Training Department

CONTENT  Concept  Service

Types  Create Service

2

CONCEPT NE_1 L2 ETY GbE/FE

M L1 P L S

NE_2 MoE

MoE Link

Ethernet

MoE

L1 M P L S

L2

ETY GbE/FE

VSI/Flow

VSI/Flow

Tunnel Service 3

MPLS PROCEDURE

4

NETWORK TOPOLOGY NPT1200-23

NPT1200-20

NPT1200-22

NPT1200-21

5

SERVICES TYPES  P2P  P2MP  MP2MP

 Rooted

MP

6

TUNNELS & SERVICES  Tunnel 

Types:

P2P 

Services supported: 

 



P2P P2MP MP2MP

P2MP 

Services supported: 

Rooted MP

7

CREATING A SERVICE – P2P  Example:

In the diagram below we want to create a P2P Service between X and Y  

First create a P2P tunnel for each direction (BiDirectional) Then create the service ETY

X

P2P Tunnel_CoS2_2

Y

P2P Tunnel_CoS2_1 ETY

8

SERVICE CONFIGURATION

9

ADVANCED PARAMETERS  Single

Service Tunnels Only One service is carried on Single Service Tunnels Only with bandwidth specifically configured for this service

 Protected

Tunnels Only Ensures the service can only use protected tunnels

10

CREATING A SERVICE – BASIC PARAMETERS

11

SELECTING ENDPOINTS

12

SERVICE CONFIGURATION  The

service is mapped with the same CoS as the associated tunnel 1. 2. 3.

First, click on the endpoint to configure Define the C-VLANs Map the client Priorities to COS 1

3 2 13

CREATING A SERVICE – COS MAPPING 2 Option 1

Option 2

14

DSCP MAPPING  In

IP Service frames, CoS mapping maps DSCP codes (6 bits) to CoS codes (3 bits) Name CS0 CS1 CS2 CS3 CS4 CS5 CS6 CS7 AF11 AF12 AF13 AF21 AF22 AF23 AF31 AF32 AF33 AF41 AF42 AF43 EF PHB

Space 000000 001000 010000 011000 100000 101000 110000 111000 001010 001100 001110 010010 010100 010110 011010 011100 011110 100010 100100 100110 101110

Reference RFC 2474

RFC 2597

Name

Space

CoS 0

000

CoS 1

001

CoS 2

010

CoS 3

011

CoS 4

100

CoS 5

101

CoS 6

110

CoS 7

111

RFC 3246

15

DSCP MAPPING IN LIGHTSOFT

16

CREATING A SERVICE – POLICERS 3

17

CREATING A SERVICE – CREATING A NEW POLICER 4

New policer

18

CREATING A NEW POLICER  Fill

in the fields according to the configured card

 Color  

mode fields

Color Blind Color Aware

 Coupling  

Flag

BG – Supported XDM- Not Supported 19

BANDWIDTH PROFILE – BY TOKEN BUCKET

“Green” Tokens

Committed Information Rate (CIR)

Committed Burst Size (CBS)

Overflow

C-Bucket CF = 0: “Yellow” Tokens CF = 1: “Green” + “Yellow” Tokens

Excess Information Rate (EIR)

Overflow

Excess Burst Size (EBS)

E-Bucket 20

POLICER PROFILE LIST  Policers

can also be managed directly in LightSoft  Use the “Services” tab  Utilities pane

21

CREATING A SERVICE–SELECTING POLICER PROFILE 5

Assign policer

22

NETWORK CONFIGURATION Tab – Shows the tunnels used to implement the service

 Networks

 The  

appropriate tunnels appear:

P2P tunnels for both directions Same CoS

23

AUTOMATIC TUNNEL CREATOR  If

you have a level 2 LightSoft license, LightSoft can create the tunnel for you  Click Complete and if there are missing tunnels NMS will let you know

24

CREATING A SERVICE – TUNNELS ASSIGNMENT

25

ASSIGNING TUNNELS

26

ACTIVATING THE SERVICE  Complete

& Activate

27

CREATING A SERVICE – MP2MP  Example:

In the diagram below create a MP2MP service between X, Y and Z 

First we create a P2P tunnel for each direction and for each endpoint participating in the service then create the service

Y

ETY

ETY

Z P2P Tunnels CoS3

ETY

X 28

CONFIGURING THE SERVICE  Service

Type – MP2MP

29

CONFIGURING THE ENDPOINTS

30

CREATING A SERVICE – TUNNEL ASSIGNMENT

31

ASSIGNING TUNNELS

32

CONFIGURING THE NETWORK

33

CREATING A SERVICE – P2MP  Example:

In the diagram below create a P2MP service between the ISP and the clients: X,Y & Z 

First create a P2P tunnel for each direction and for each endpoint participating in the service  then create the service ETY

ETY

ISP

Y P2P Tunnels CoS1

X

ETY

ETY

Z

34

CONFIGURING THE SERVICE Type – P2MP  E-Tree Enabled  Service

35

CONFIGURING THE ENDPOINTS

36

NETWORK CONFIGURATION

37

MPLS SERVICES VS. TUNNELS

Services

Tunnels

P2P

P2P (Bi-directional Tunnels)

MP2MP

P2P (Mesh of Bi-directional Tunnels between all nodes)

P2MP (ISP)

P2P (Bi-directional Tunnels from the Hub to each Spoke)

38

SUMMARY  Concept  Service   

types

P2P MP2MP P2MP

39

EMS-APT– INTEGRATED Maintenance

Global Services Division ECI Training Department

CONTENT  NE

List  XC List  ALS  Loopbacks  Force Signals  Export XCs  NEs DB backup  EMS DB Backup

2

NE LIST Create/Edit/Delete elements from this window

Search for a specific NE

3

XC LIST  Two  

type of trails in EMS-BGF

Server Trail (HO XC) Service Trail – equivalent to Client Trail (LO XC) 2 1

4

LASER CONTROL - ALS 1. Select the object

2. Select the Work mode Maintenance

3. Select the ALS mode

Force On – ALS Disabled – laser on Force Off – laser off Automatic Restart- ALS Enabled Manual Restart – By clicking the restart button 5

LOOPBACK TYPES  Terminal

Loopback

Physical Port

 Facility

XC

Loopback

Physical Port

XC

6

LOOPBACKS 1. Working mode- Maintenance 2. Select the card in the object tree 1

3. Select the Loopback tab

3

2

7

FORCED SIGNALS – AIS, RDI – TX port  Downstream – RX port  Upstream

Upstream example

Downstream example 8

EXPORTING XC 1. Click the “Select all” option or select manually the XC to export 2. Export XC to an XML file

9

DB BACKUP OF NES 1. 2. 3.

Mark the NEs Remember the path of the file as written in “File Name” Press on Start

10

EMS DB BACKUP  Two  

options to backup the DB

Set a time to Backup Backup immediately

11

EMS DB BACKUP  Configuration

DB backup  Alarms DB backup 1 2

3

4 12

SUMMARY  NE

List  XC List  ALS  Loopbacks  Force Signals  Export XCs  NEs DB backup  EMS DB Backup

13

CFM: UNDERSTANDING & CONFIGURING LightSoft EMS-APT

Global Services Division ECI Training Department

CONTENT  CFM

overview  CFM Functions  Using CFM functionality

2

WHAT IS CFM?  CFM

– Connectivity Fault Management

 CFM

is an MEF standard aimed at helping service providers monitor their network E2E

 The   

following basic functions are supported

Discovery & Connectivity Fault Verification - Loopback Fault Isolation – Link Trace

3

CFM FUNCTIONAL MODEL  Ethernet

CFM has an hierarchical administrative domain known as the Maintenance Domain (MD)  8 MD Levels are available: 

 

Customer Domain Service Provider Domain Operator Domain NPT

Levels 5, 6, 7 Levels 3, 4 Levels 0, 1, 2

NPT

NPT

Operator Service Provider

Customer 4

CFM ENTITIES – Maintenance End Point  MIP – Maintenance Intermediate Point  MA – Maintenance Association or MEG – Maintenance Entity Group  MEP

NPT

NPT

NPT

MA

MA MEP

MIP

MIP

MIP

MIP

MEP 5

DISCOVERY & CONNECTIVITY  CC

- Continuity Check (by CC Message - CCM)  CC is used for discovery and monitoring   

A multicast packet is sent by each MEP Every MEP builds a connectivity table CCM frequency: 1sec, 10sec, 1min, 10min

NPT

MEP

NPT

MIP

MIP

MEP 6

FAULT VERIFICATION – LOOPBACK Loopback is a ping-like request/reply protocol  MEP sends a unicast Loopback Message (LBM) to MEP or MIP  Remote side responds with Loopback Response (LBR)  LBMs / LBRs are used to verify bidirectional connectivity  They are initiated by operator command 

LBM

LBR NPT

MEP

NPT

MIP

MIP

MEP 7

FAULT ISOLATION – LINK TRACE Link Trace is used to trace the path to the target MEP  MEPs send multicast Link Trace Message (LTM) to identify adjacency relationships with the remote MEPs and MIPs  Each MIP on the way responds with a Link Trace Response (LTR) 

LTM NPT

NPT

LTR 8

CONFIGURING CFM EoS Trail

EoS Trail

ETY#1

EoS#1

EoS#1

EoS#2

EoS#2

MEP

MIP

MIP

MIP

MIP

ETY#1

MEP

9

CFM IN NMS

10

PRE-REQUISITES  EoS  

Server trails VC4 exists Service trails EoS-VC3 or EoS-VC12 exists

 MoT 

network

& MoE networks

Tunnels exists for the service creation

11

WHILE CREATING A SERVICE  Create 

the service, as usual

MP2MP, endpoints with COS, Policers, VLANs

12

CREATING MAs  Click

the CFM tab  Add MA

1

2

13

CREATING MAs

3

4 5 6

 Then

3. MD Level in NMS can only be 1 4. Each CFM session is based on COS 5. Write a name for the MA Label Will be the same on both endpoints 6. CCM Period, sends messages every 1000ms (default)

Complete & Activate the service 14

MEPs & MIPs  After

the service is activated  NMS automatically updates all MEP & MIP objects

15

CFM OPERATIONS

16

MAINTENANCE OPERATIONS Select Loopback, Link Trace, Continuity Check

Select Source and Target MIPs/MEPs

View Results

17

CFM IN EMS-APT

18

SWITCH CONFIGURATION 2

3 4

1

1. 2. 3. 4.

Click the Switch Working mode – Configuration Click the “CFM Domain” tab Click the create icon

19

SWITCH CONFIGURATION

5

5. Fill in the Domain Name - the domain name and level has to be the same in all NEs 6. Select the domain level - in our scenario it is domain level 0

6

The MD appears under the CFM domain and Level

 Repeat

the steps for the other NEs 20

CREATING MIPs 2

3

4

1

1. 2. 3. 4.

Click the EoS port Working mode – Configuration Click the “CFM MIPs” tab Click the create icon

21

CREATING MIPS

5

5. Verify the domain name is the same as the name configured for the switch 6. Click the “Enable” checkbox – to enable the port as an MIP

6

The new configuration appears under the CFM MIPs tab

22

CREATING MIPS Repeat steps 1-6 for the second EoS port and also for the other EoS ports in the service

23

CREATING AN MA

1

2 3

1. Right–click on the service in the VSI list  select “Edit VSI” 2. In the Edit window go to the “CFM MA List” tab 3. Click the create icon

24

CREATING AN MA

25

CREATING AN MA

4. Write a name for the MA. The name must be the same also for the remote endpoint

MEP Direction – the direction of the CFM frame up = towards the network (fixed) Down = to the customer 4

CCM = Continuity Check Message CCM Interval – how often to send CCM information (in msec)

26

CREATING AN MA

5 7

5. Select the Local MEPwhich is the first ETY in our scenario – it appears in the local MEP window below

6. Configure the Local MEP ID and enable the port

7. Select the Remote MEP – which is the remote end point of the service – it appears in the remote MEP window below

6

8

8. Configure the Remote MEP ID

27

CREATING AN MA The MA configuration was added to the CFM MA List. Apply the changes

28

CREATING AN MA  Repeat 1. 2. 3. 4. 5. 6. 7.

the steps for the MA at the other endpoint

Services  Select VSI  Edit VSI CFM MA List tab  Create new Give the MA a name Set CCM interval, Cos  Enable CCM Select local MEP  MEP ID  Enable Select Remote MEP  ETY Port  MEP ID Save & Close

29

CFM MAINTENANCE – Continuity Check Message  Loopback  Link trace  CCM

30

CCM CONFIGURATION

ETY#1

EoS#1

MEP

MIP

EoS#1

MIP

EoS#2

MIP

EoS#2

ETY#1

MIP

MEP 31

CCM CONFIGURATION

2

3 5 4

1

1. 2. 3. 4. 5.

Click the switch Working mode Maintenance Go to the CFM MA List tab Select the MA Click the CCM icon

32

CCM CONFIGURATION 6

7

6. Click the checkbox “Enable CCM” 7. If needed - configure the time interval for sending the CCM frames

33

LOOPBACK CONFIGURATION LBM LBR

ETY# 1

EoS# 1

EoS# 1

EoS# 2

MEP

MIP

MIP

MIP

EoS# 2

ETY# 1

MIP

MEP 34

LOOPBACK CONFIGURATION

2

3 5 4

1

1. 2. 3. 4. 5.

Click the switch Working mode Maintenance Go to the CFM MA List tab Select the MA Click the Loopback & link trace icon

35

LOOPBACK CONFIGURATION 6. Option button – loopback 7. Select the Local MEP 8. Select the Remote MEP

6

7

8

36

LINK TRACE CONFIGURATION

LTM

MIP

MIP

MIP

MIP

ETY#1

ETY#1

LTR MEP

MEP 37

LINK TRACE CONFIGURATION

2

3 5 4

1

1. Click the switch 2. Working mode Maintenance 3. Go to the CFM MA List tab 4. Select the MA 5. Click the Loopback & link trace icon

38

LINK TRACE CONFIGURATION 6

6. Option button Link Trace 7. Select the Local MEP 8. Select the Remote MEP

7

8

39

CFM ALARMS  To

see CFM results enable the report on the fault severity settings  check the CFM alarms in each element

40

CFM RESULTS EXAMPLE  If

the fiber is disconnected the following alarm is triggered – we have a connectivity problem The alarm belongs to the BS:SCIO card on element 217

1 7 200

= VSI ID = MA level = MEP ID

41

CFM RESULTS EXAMPLE  If

the cable from one of the MEPs is disconnected, in this example from 217, the following alarms are triggered

42

SUMMARY 

CFM overview  



CFM Functions 

 



MDs – Maintenance Domains CFM Entities Continuity Check Loopback Link Trace

Configuring CFM functionality 

NMS LightSoft    



Switch configuration Creating MEPs Creating Mas CCM, Loopback and Link Trace

Running CFM 

Alarms

43