NPT MPLS Basic.pdf

L2 DATA FUNCTIONS

Ethernet Switch

Global Services Division ECI Training Department

CONTENT

 L2 concept

OPEN SYSTEM INTERCONNECTION: OSI

DATA LAYER 2 - CONCEPT

STM-x

SDH Card _{SDH Card Data Card}

Data Card

GbE/FE _GbE/FE

L1 L1

VSI/Flow VSI/Flow

ETY EoS EoS ETY

L2

L2

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

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

ETHERNET FRAME

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

MAC Port Forwarding Table 1 2 PC 1 PC 2 I’m PC2 !!! Dest. : PC2 MAC Port PC1 Port 1 MAC Port PC1 Port 1 PC2 Port 2 PC1 PC2 SA DA PC2 PC1 SA DA

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

VLAN

 Separates different users within a network.

 Separates broadcast domains.

 IEEE 802.1Q –VLAN Tagging Standard

Ethernet Switch Ethernet Switch

VLAN TAG FRAME - CLIENT

 EtherType - 802.1Q Tag Type (0x8100)

 Priority - 8 priority levels are defined Destination address Source address Length/ Type DATA FCS Priority 3 bits CFI 1 bit VLAN ID 12 bits EtherType 16 bits 802.1q Header

VLAN TAG FRAME – NETWORK

 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

CoS 3 bits DEI 1 bit VLAN ID 12 bits EtherType 16 bits Destination address Source

QINQ CONCEPT

SDH Transmission

Network

Double tagged frame

CVLAN

IP Packet

PBits

SA (MAC) DA (MAC)

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

QOS PRINCIPLES

Classifier Policer Forwarding

Engine Congestion Avoidance (WRED) Congestion Management (Schedule & Queue) Shaper

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

Congestion Avoidance

Congestion Management

TRAFFIC CLASSIFICATIONS

Name Space Reference CS0 000000 RFC 2474 CS1 001000 CS2 010000 CS3 011000 CS4 100000 CS5 101000 CS6 110000 CS7 111000 AF11 001010 RFC 2597 AF12 001100 AF13 001110 AF21 010010 AF22 010100 AF23 010110 AF31 011010 AF32 011100 AF33 011110 AF41 100010 AF42 100100 AF43 100110 EF PHB 101110 RFC 3246

Priority bits Space

0 000 1 001 2 010 3 011 4 100 5 101 6 110 7 111 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

L3 - DiffServ Code Point (DSCP)

L2 – 802.1p/ VLAN Tag 802.1Q

Transport CoS

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

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

CIR EIR Drop Zone

Link Rate

Green

Yellow

Red/Dropped

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

Rate Policer

Two Rate Policer

COLORING PRINCIPLES

Switch buffer per port

T P U Rx Buffer Tx Buffer Classifier Policer F F C B S CIR E B S EIR F F F F I B F i L t e r COS0 COS3 COS6 COS7 COS4 COS5 COS1 COS2 WRED S C H E D U L E R S H A P E R

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}

BW PROFILE - BY TOKEN BUCKET

C-Bucket

“Green” Tokens

CF = 0: “Yellow” Tokens

CF = 1: “Green” + “Yellow” Tokens Overflow Overflow Committed Information Rate (CIR) Excess Information Rate (EIR) Committed Burst Size (CBS) Excess





from the C-bucket added to the E-bucket

POLICER RATES

QOS – TRAFFIC MANAGEMENT

 Congestion Avoidance  Tail Drop

 RED – Random Early Detection

 WRED – Weight Random Early Detection

Forwarding Congestion Congestion Management D rop Probability

Average Queue size

MinY _{MaxY MinG MaxG} Yellow _Green

1

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 Queue Size Dropped RED Start RED Stop RED Start + REDQRange

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

WRED YELLOW/GREEN CURVES

Average queue size

Ming Maxg Yellow Green V S I V S I Policer CIR=0, EIR=100M CoS 0..7 to 0

All Yellow Packets of CoS 0

All Green Packets of CoS 0

100 M Utilization

100M Utilization

Green Packets due to better Curve

SUMMARY -

HOW THE TRAFFIC FLOWS…

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

Congestion Management

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

BSC – BROADCAST STORM CONTROL

 Protection from an excessive number of broadcast packets

RSTP

 Rapid Spanning Tree Protocol

 RSTP is a loop resolution protocol

 IEEE 802.1W

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

SUMMARY

 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

MPLS

INTRODUCTION

AND

FUNCTIONALITY

CONTENT

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

IP ATM, FR, Ethernet, PPP IP ATM, FR, Ethernet, PPP MPLS L2 L3

MPLS MOTIVATION

 MPLS LSP – Label Switched Path  LSP - Tunnel

 Tunnel creation across a network

 Bandwidth Allocation across the network San

Francisco

New York

LABEL SWITCHING ROUTERS

 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

San Francisco New York LSP LER LSR LSR LER

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:

Label Header

PPP Header Layer 3 Header

PPP Header (Packet over SONET/SDH)

Frame Relay Label Header Layer 3 Header

MPLS LABEL STRUCTURE

 Label (20bits)

 Carries the actual value of the label  2^20=1M entries in a routing table  Exp (3bits):Experimental bits

 Used for Priority or QoS

 S (1bits):Bottom of Stack flag

 Can stack multiple labels  TTL (8bits):Time to Live

 Counter for Loop prevention

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

MPLS LABELS

VC Label MAC Header Data

Tunnel Label

MAC Header

Link layer Address, Can be:

(1) Ethernet

(2) PPP

(3) Frame Relay

In Port Out Port

LABEL SWITCHING

 MPLS is connection-oriented protocol

 Provisioning labels to tunnels – done by Signaling/NMS  Data packets can be transferred over the tunnel

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

CE

Source PE P Dest PE

CE

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, where packet replication occurs at branching points along the tree

PE 1 P 1 PE 2 PE 4 CE CE PE 5 CE PE 3 CE

VPWS APPLICATION

 VPWS - Virtual Private Wire Service  P2P connectivity over MPLS

 Pseudo-Wire (PW) - shares the same tunnel

VPLS APPLICATION

 VPLS - Virtual Private LAN Service  _{Multipoint connectivity over MPLS}

 Fully-meshed LSP tunnels are needed

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

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)

MTU MTU PE PE MTU MTU MTU MTU MTU PE PE

MTU = Multi-Tenant Unit

Spoke VCs Hub VCs MTU PE PE PE PE MTU MTU MTU MTU VLANs, Stacked VLANs or VC Labels MTU MTU 18

HUB & SPOKES APPLICATION

Hub & Spoke (Partial Mesh) Pseudo-wires Tunnels Customer B CE (Spoke) MCS-PE MCS-PE MCS-PE

ROOTEDMP APPLICATION (E-TREE)

 RootedMP (Multi Point) Multicast Service  IGMP snooping  MPLS TE enforcement  VC label (VPN) configured by NMS Customer s Customer s IPTV/BTV Head-end Router

Hub and Spoke Pseudo-wires Customer s P2MP Multicast Tunnel (Tree) IGMP Snooping MCS-PE MCS-P

MCS-PE MCS-PE MCS-PE

DSLAM DSLAM DSLAM Ethernet

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

VSI Ethernet Switch

VSI A VCG (WAN) port 1 MPLS Switch VSI B Mapper Ethernet Port 4 Ethernet Port 3 Ethernet Port 2 Ethernet Port 1 VCG (WAN) port 2 Ethernet VC T Ethernet Ethernet VC T Ethernet Port N-1 Ethernet Ethernet Ethernet

ETHERNET-ACCESS AND VPLS

 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

Customer A PB (Tellabs) Network ETH based MPLS-TP Network MPLS Based Network PB Network Customer B Customer B Customer A Customer B PB: Provider Bridge MPLS I-NNI ETH UNI ETH I-NNI ETH E-NNI MCS-PE MCS-PE BG-9300 MCS LightSoft UME: ETX MoE

MPLS TERMS

 VSI COS == Tunnel COS  Connection Types

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

NPT-1020

V.4

Global Services Division ECI Training Department

CONTENT

Main features

Product layout

Common modules

Matrices

I/O modules

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)

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

NPT BUILDING BLOCKS



Packet Switching:



New Centralized Packet TDM Switch –CPTS



MPLS-TP Functionality:



Support for bidirectional tunnel service



MPLS-TP tunnel OAM



_{Synchronization:}

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

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

CPTS

Centralized Packet and TDM Switch (CPTS) TDM Matrix Packet Switch TDM TDM Packet Packet Packet Packet

A new Centralized hybrid matrix for supporting

any-to-any data cards connectivity in addition to the TDM

switching capacity

Enables the option for

any-to-any data cards

connectivity in addition

to the TDM switching

capacity

PACKET VS. TDM

PACKET VS. TDM

MPLS-TP/ Eth. Packet Switch

TDM Matrix

TDM TDM_EoS Ethernet Ethernet_CES

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

TSLOT MODULES – PDH

PME1_21

PM345_3

• 21 balanced E1s

• Unbalanced mode is Supported

via an xDDF-21 converter

3 E3/DS3 ports, configurable

independently

PME1_63

TSLOT MODULES – SDH

SMD1B

Dual STM1, SFP based

SMS4

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 CARDS

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

MSC_2_8

Multi service card supports

up to 16 x E1 for CES services

MSE1_16

TSLOT MODULES – DATA – PURE PACKET

DHGE_4E

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

SUMMARY

_{Main Features}

Product Layout

_{Common Modules}

Matrices

_{I/O Modules}

NPT-1200

V.4

Global Services Division ECI Training Department

CONTENT

_{Main features}

Product layout

_{Common modules}

Matrices

_{I/O Modules}

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

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

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

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

CPTS - CENTRALIZED PACKET & TDM

SWITCH

TDM & Packet

CPTS - CENTRALIZED PACKET & TDM SWITCH

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

PACKET VS. TDM

PACKET VS. TDM

MPLS-TP/ Eth. Packet Switch

TDM Matrix

TDM TDM_EoS Ethernet Ethernet_CES

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

CPTS 100

Centralized Packet and TDM Switch (CPTS) TDM Matrix Packet Switch TDM TDM Packet Packet Packet Packet

A new Centralized hybrid matrix for supporting

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

CPTS100 622M/ 2GE OHA 100G Packet Switch 40G TDM Matrix Tslot 1# Tslot 2# Tslot 3# Tslot 4# Tslot 5# Tslot 6# Tslot 7# Controller AUX TMN LS LCT EMS G.703 V.11 NPT-1200 Eslot 1# Eslot 2# Eslot 3# 2.5G/20G 2.5G 2 Mbps STN-n E1 1588 V2 Synchronization 2.5G/20G 2.5G/20G 2.5G/20G 2.5G/20G 2.5G/20G 622M/ 2GE 622M/ 2GE EXT-2U

NPT-1200 – 100G ARCHITECTURE

CPS - CENTRALIZED PACKET SWITCH

CPS - CENTRALIZED PACKET SWITCH

Packet

Central 320G Packet switching with 4 x 10GE

TDM BASED MATRIX



XIO64



Redundant matrix and TMU



STM-64 XFP housing

TDM BASED MATRIX



XIO16_4



Redundant matrix and TMU



Four STM1/4/16 independently configured ports

TS3 FCU-50 TS5 TS6 TS7 TS4 CPTS100 CPTS100

NPT-1200

EXT-2U

THE NPT-1200 – BW ALLOCATION

2U

2U

TSLOT MODULES – PDH

PME1_21

PM345_3

• 21 balanced E1s

• Unbalanced mode is supported

via an xDDF-21 converter

3 E3/DS3 ports, configurable

independently

PME1_63

TSLOT MODULES – SDH

SMS16

SMQ1&4

Quad STM1/4, SFP based

SMQ1

TSLOT MODULES – DATA – LAYER 1

DMFE_4_L1

Quad FE L1 Ethernet card

DMFX_4_L1

Quad FX L1 Ethernet card

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)

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

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

• Double-slot card

• Up to 2 cards supported in

a NPT-1200 shelf

• 2 COMBO ports supporting Optical

GbE / Electrical 1000/100/10 Mbit

TSLOT MODULES – DATA – LAYER 2

• 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

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

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

TSLOT MODULES – DATA – PURE PACKET

DHGE_4E

DHGE_8

• Packet card supports up

to 8 x 100/1000 Base-X with 4 CSFP

DHGE_16E

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

TSLOT MODULES – DATA – PURE PACKET

• Supports up to 4 x 10GE ports with connection to

the packet switching matrix

CES CARDS

SME1_16

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

• Multi service card supports

CES CARDS

MSC_2_8

• New Multi Service combo card supports

SUMMARY

_{Main features}

Product layout

_{Common modules}

INF, FCU, MCP

Matrices



CPTS, CPS, XIO64 and XIO16_4



I/O Modules

LCT-APT

NPT-1200 NE

CONTENT

LCT – Main window

Operation mode

_{Basic Attributes}

Timing

_{IP Setting}

Slot Assignment



_{Port configuration example}

DCC XC

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

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

LCT – MAIN WINDOW

Working Area is divided by Tabs – each tab represents

OPERATION MODE



By default the LCT mode is in Monitor mode

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

BASIC ATTRIBUTES

1. Select the NPT icon 2. Go to “NE Setting” tab 3. Press the refresh button

4. Give the NE Name/Location etc.

1

NE TIME OF DAY

1. Press the refresh button

2. Press on the calendar icon to set the date for today

IP SETTING

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

REASSIGNMENT



Reassignment is changing the expected equipment

type to a new but compatible type, logically in a slot

SLOT ASSIGNMENT



Get Logical Card – view the logically assigned cards

(expected)



Get Physical Card – view the actual cards

TIMING CONFIGURATION

1

2 1. Expand the Control and Physical object and select the TMU option

2. Select the Timing Setting tab

3. Remove the v from the internal timing checkbox

CARD CONFIGURATION EXAMPLE

1

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. Set the SFP type and the

application code according the used SFP

1

2 3

DCC CROSS CONNECTS

1. Select the element

2. Select “Services” as the work mode

3. Go to the “DCC XC List” tab and click on the Upload icon

for uploading the XC to the LCT DB

1

2 3

DCC CROSS CONNECTS

Click on the Upload button to view the XC

Overwrite – update the DB according the uploaded

DCC CROSS CONNECTS

1

2

3

1. Select the optical port for the requested DCC XC

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

LICENSE UPGRADE



Set the connection to the EMS server:

3

4

Server IP – the IP address of the EMS server

Port – logical port to use for delivering the license

SUMMARY

LCT – Main window

Operation mode

_{Basic Attributes}

Timing

_{IP Setting}

Slot Assignment

_{DCC XC}

LCT License

APT INTRODUCTION

Global Services Division ECI Training Department

CONTENTS



LCT-APT



EMS-APT

APT FCAPS



FCAPS- Fault, Configuration, Administration,

Performance and Security

Fault-Recognizes, isolates,

corrects and logs the faults

Configuration-Simplifies

gathering and storing device

configurations

APT

Administration - Establishing

users, passwords and

permissions/rights

APT FCAPS

Performance

–

Monitoring performance data to

determine the health and efficiency of

the current network

Security- Controlling access to assets

in the network

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

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,

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}

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)

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

SUMMARY

 LCT-APT and licensing

 EMS-APT

 Integration of the EMS-APT with LightSoft

 NE management

NMS LIGHTSOFT

Introduction

Global Services Division ECI Training Department

MANAGEMENT ARCHITECTURE

EMS-XDM EMS-BGF Other EMSs

TMF-MTNM Corba I/F

TABS – NO MORE MENUS



_{NMS LightSoft has a modern look and feel}

ECI BUTTON



_{ECI button contains the Help and About LightSoft}

options

LIGHTSOFT RIBBON



The LightSoft ribbon is maximized or minimized



To maximize or minimize:

 Ctrl + F1

 View tab click on Ribbon

QUICK ACCESS AREA



Above the ribbon



Static (always visible to user)



Displays:

Technology layers

Consistency indicators

TECHNOLOGY LAYERS



LightSoft has traffic from

different technology types



You can see the elements

processing the different traffic types:

 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

TOPOLOGY LAYER TYPES

_{Physical (Site)}

Physical (EMS)

_SDH/SONET

Optical (OTN)

_OCH

Ethernet/MPLS

Physical

(EMS)

SDH/

SONET

Physical

(Site)

Optical

(OTN)

EXAMPLE OF LAYERS



Physical (Site):

this layer shows your

whole network, including

3

party equipment

(technology transparent)

 ETH/MPLS

This layer shows your

Ethernet and MPLS

switches in your

ELEMENTS



_{ME/NE: Managed/Network Element}



UME: Unmanaged Element

TOPOLOGY LINKS



Represent the physical connections between elements



Must be created before provisioning traffic

1

2

PROVISIONED TRAFFIC



_{Trail List shows the trails in the network}

x x

INSERTING AN ELEMENT

CONSISTENCY INDICATORS



_{Show the inconsistencies between the NMS}

LightSoft DB and the EMS databases

Client (GUI) Server (Database) EMS XDM DB EMS BG DB Other EMS DB

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

CONTEXT SENSITIVE TABS



CST – an accepted industry standard



This tab contains only relevant commands for

selected elements (Nodes, Groups and Links)

HOT KEYS



_{Pressing Alt toggles hot key tips}



Once the are tips displayed, type the letter to open

that tab – level 1

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

TREE – SEEING THE NETWORK



_View

_Tree

The Tree shows all MEs in the topology

VIEW FUNCTIONS



_{Zoom & Navigation}

Seeing all, or different parts of the topology



Move

– moving elements on the screen and

saving/not saving changes



_Map

– working with groups of elements

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

WORKING WITH

TOPOLOGY LINKS

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)

CREATING A TOPOLOGY LINK

Select 2 elements to connect

1

2

CREATE TOPOLOGY LINK WINDOW

Select 2 endpoints *Only resources that

support the rate selection are available

Select rate

1

2

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.

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

Enables you to set the J0 values of endpoints of a physical connection

A TOPOLOGY LINK IN LIGHTSOFT



_{A topology link appears in the physical (site) layer}

TOPOLOGY LINKS COLOR-CODING



_{Color-coding for operational links:}



Red

– critical or major alarm



Orange

– minor alarm



Yellow

– warning



Green

– clear (no alarms)



Color-coding for non-operational links:



Light blue

– the link is connected and not uploaded

(an intermediate state)



Dark blue

– the link is being uploaded

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

VIEWING INTERNAL LINK DETAILS

1

SUMMARY



_{Topology Links}



Between elements

MoE CONFIGURATION

NMS LightSoft

AGENDA



_{Switch configuration}

Port configuration

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}

SWITCH CONFIGURATION – NPT

1

3

1. Click the Switch

2. Go to “Configuration” 3. Set the switching

mode to: “MPLS-PE”* 4. Configure a unique

PE_ID

3 2

MoE PORT DEFINITION

1

1. Right click the Card

2.Click Activate/Deactivate port 3.Activate the desired port

4.click the Apply button

4

3 2

SFP CONFIGURATION



_{Choose the Expected SFP Type according to the}

DEFINE MoE PORT

1. Right click the Card 2. Click Define MoE Port 3. Select the desired port 4. Click the Apply button

1

4

3

MoE LINKS IN LIGHTSOFT

Prerequisites:

 Traffic Engineering configuration is

according to the plan (can be changed later using the Link list):

 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

1

4 3

MoE LINKS & PORTS

Physical Site link

ETH/MPLS layer link

The port is

SUMMARY

Switch configuration

MPLS-PE

Unique ID

Port configuration

SFP configuration

_{MoE creation}

TE CONFIGURATION

IN NMS

Traffic Engineering ( QoS, CAC & EXP)

Global Services Division ECI Training Department

AGENDA

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

QOS IN NMS

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

QUALITY OF SERVICE

 Priority:

 _{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

High Strict priority, committed traffic with low latency.

PIR=CIR= Tunnel BW

Low Fair queuing, have EIR and can accept drops when applicable,

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