PTN MPLS-TP

Adil Nadeem
Project Manager
Pakistan Customer Services
 Content
Evolution of MPLS-TP

Introduction to MPLS-TP

IP Planning MPLS-TP

Network Management System

FiberHome PTN in Pakistan

Common Configurations

Common Troubleshooting Techniques

 Agenda
Evolution of MPLS-TP

Introduction to MPLS-TP

IP Planning MPLS-TP

Network Management System

FiberHome PTN in Pakistan

Common Configurations

Common Troubleshooting Techniques

 Evolution of MPLS-TP
Design Case: The SDH based MSTP technology provided all the
packet interfaces to overcome the needs of Packet Traffic over SDH but
Core was still TDM.
Disadvantages: Application requirement of Packet based Services.

Solution: PTN was considered as Solution to the Service

Requirement of Packet based Services providing carrier class OAM.
It was a Layer Set Between the Service Layer and Optical Transport
Layer. (i-e IP as Core and Ethernet as User manifestation)
 Evolution of MPLS-TP
Advantages: As a transport technology, PTN MPLS-TP Possess

I. Lowest cost per transmitted bit,

II. Definable QoS (Quality of Service),

III. Strong OAM Mechanism

IV. High Reliability,

V. Network Management Capabilities

 Agenda
Evolution of MPLS-TP

Introduction to MPLS-TP

IP Planning MPLS-TP

Network Management System

FiberHome PTN in Pakistan

Common Configurations

Common Troubleshooting Techniques

 Introduction to MPLS-TP
PTN MPLS-TP Network Technology Can be divided into two Main
Modules.

1. MPLS

2. TP(Transport Profile)
 Introduction to MPLS-TP
MPLS : Multiprotocol Label Switching

Working Principle: MPLS normally prefix each packet with MPLS

Header also known as Stack.

Each Stack contains four Entries as shown:

Label (20 Bits) EXP (3Bits) S(1 Bit) TTL (8 Bits)

A 20-bit label value.

A 3-bit Traffic Class field for QoS (quality of service) priority
(experimental)
A 1-bit bottom of stack flag. If this is set, it signifies that the current
label is the last in the stack.
An 8-bit TTL (time to live) field.
 Introduction to MPLS-TP
1. MPLS-TP Frame Structure:

DA-Destination SA-Source TPID TMP TMC Payload CRC

Address(6 Bytes) Address(6 Bytes) (0x8847) (4 Bytes) (4 Bytes) (4 Bytes)
2Bytes

TMP Label (20 Bits) EXP (3Bits) S(1 Bit) TTL (8 Bits)

TMP: TMPLS-Path
TMC Label (20 Bits) EXP (3Bits) S(1 Bit) TTL (8 Bits)
TMC: TMPLS-Channel
 Introduction to MPLS-TP
2. MPLS-TP L2VPN

MPLS-TP supports multiple types of Ethernet services and provides

comprehensive L2VPN (Layer 2 Virtual Private Network) solutions
such as:
I. Ethernet private line service, i.e., E-Line service

II. Ethernet private network service, i.e., E-LAN service

III. Ethernet convergence service, i.e., E-Tree service

 Introduction to MPLS-TP
I. Ethernet Private Line Service (E-Line)

Providing Point to point Connection to the client data.

Depending on whether the service at the network side UNI port is

multiplexed, the E-Line services can be further divided into the
following two categories:
EP-Line Ethernet private line service: not allow for service multiplexing.

EVP-Line Ethernet private line service: allows for service multiplexing.

 Introduction to MPLS-TP
I. Ethernet Private Line Service (E-Line)

EP Line Service Model

 Introduction to MPLS-TP
I. Ethernet Virtual Private Line Service (E-Line)

EVP Line Service Model

 Introduction to MPLS-TP
II. Ethernet Private Network Service (E-LAN)

Providing a multipoint to multipoint connection of the client data.

Depending on whether the service at the network side UNI port is

multiplexed, the E-LAN services can be further divided into the
following two categories:
EP-LAN Ethernet private network service: not allow for service multiplexing.

EVP-LAN Ethernet private network service: allows for service multiplexing.

 Introduction to MPLS-TP
II. Ethernet Private Network Service (E-LAN)

EP-LAN Service Model

 Introduction to MPLS-TP
II. Ethernet Private Network Service (E-LAN)

EVP-LAN Service Model

 Introduction to MPLS-TP
III. Ethernet Convergence Service (E-Tree)

Providing a multipoint-to-point connection of the client data.

E-Tree services can be applied in ISP connection and provide basic

networks for multicast services such as IPTV.

Depending on whether the service at the network side UNI port is

multiplexed, the E-Tree services can be further divided into the
following two categories:
EP-Tree Ethernet convergence service: not allow for service multiplexing.

EVP-Tree Ethernet convergence service: allows for service multiplexing.

 Introduction to MPLS-TP
III. Ethernet Convergence Service (E-Tree)

EP-Tree Service Model

 Introduction to MPLS-TP
III. Ethernet Convergence Service (E-Tree)

EVP-Tree Service Model

 Introduction to MPLS-TP
3. MPLS-TP CES (Circuit Emulation Service)
CES (Circuit Emulation Service) technology helps to transmitted the circuit switched data
transparently in the packet transport network as shown:
 Introduction to MPLS-TP
3. MPLS-TP CES (Circuit Emulation Service)

MPLS-TP based emulation of Circuit switched data can be classified

into two types

I. Structured Emulation Mode

II. Non-Structured Emulation Mode

 Introduction to MPLS-TP
I. Structured Emulation Mode (RFC 5086)

Can identify the frame structure of the CES service.

It does not transmit idle timeslot channels and only extracts useful
timeslots of E1 traffic stream and then encapsulates them into PW
packets for transmission.

It can identify and transmit CAS(Channel associated Signaling) and

CCS(Common Channel Signaling) in E1 traffic streams.
 Introduction to MPLS-TP
I. Non-Structured Emulation Mode (RFC 4553)

It transparently transmits CES traffic data and synchronous timing

information.

It completely disregards any structure, and doesn't interpret the CES

data or to participate in the CES signaling.

Is a simple way for transparent transmission of PDH bit-streams in

the CES.
 Introduction to MPLS-TP
4. QoS (Quality of Service)

PTN MPLS-TP provides hierarchical end-to-end QoS (Quality of

Service) management.

Its QoS supports:

Traffic classification, traffic monitoring, congestion management, queue scheduling
and traffic shaping.
 Introduction to MPLS-TP
TP: Transport Profile

Transport part contains:

1. OAM

2. Protection Mechanism

3. Clock Synchronization
 Introduction to MPLS-TP
1. OAM

Function Type Description

CC Continuity and Connectivity Check

AIS Alarm Indication Signal

RDI Remote Defect Indication

Failure
Management
LB Loopback

LCK Lock

CSF Client Signal Fail

LM Frame Loss Measurement

Performance
Monitor
DM Frame Delay Measurement
Ethernet Service OAM ITU-T Y.1731
APS Automatic Protection Switching
PTN Network OAM
GAch+ITU-T Y.1731 Others MCC Management Communication Channel
(LSP/PW/Section)
Access Link OAM IEEE 802.3ah SSM Synchronization Status Message
 Introduction to MPLS-TP
2. Protection
I. LSP 1:1 Protection (50ms)
Working-LSP

Node A Node B

Protection-LSP
Normal State
Protection Domain
Working-LSP

Node A Node B

Temporary Bridge Temporary Switch

Protection-LSP

Working -LSP Fails

Protection Domain
 Introduction to MPLS-TP
II. Wrapping Protection(50ms)

Node Node Node Node Node Node

A B C A B C

Node Node Node Node Node Node

F E D F E D

Working-Section Working-Section
Connection Q Connection Q
Protection-Section Protection-Section
 Introduction to MPLS-TP
III. Clock Synchronization
 Agenda
Evolution of MPLS-TP

Introduction to MPLS-TP

IP Planning MPLS-TP

Network Management System

FiberHome PTN in Pakistan

Common Configurations

Common Troubleshooting Techniques

 IP Planning MPLS-TP
Basic Concepts and Rules
Area: It is equivalent to the concept of AREA defined in routing protocol OSPF. OSPF
network is divided into the following two levels: backbone area or area 0 and non-backbone
areas. One OSPF area may contain only one backbone area and more than one non-backbone
areas. The area number of the backbone area is 0. The non-backbone areas can not exchange
information with each other, they can be connected to backbone areas and exchange
information with each other through backbone areas. The router connecting non-backbone
areas and backbone areas is named as ABR (Area Border Router) and only the ABR records
all the routing lists of each area.
 IP Planning MPLS-TP
Basic Concepts and Rules:
Backbone area and local area: if a network is logically divided, the backbone areas are
at the core, while the local area are at the margin of the network. Usually, when a
network is divided into different areas, the backbone areas and local areas fall into
different levels of the network.
Area ID: in a network, different domains have different IDs. The ID of a backbone area is
0.0.0.0.
Area address and mask: an attribute of area, it is consistent with area ID.
External routing capability: Corresponding to the type of the area. If the value is set as
TRUE, it has external routing capability and it is a TRANSIT area; if it is set as FALSE, it
has no external routing capability and it is a STUB area.
Gateway NE: a function used by the equipment that communicates with a network
administrator through external DCN network. Gateway NE is at the junction between the
equipment network and DCN network.
Default gateway: the gateway NE at the margin of the DCN network must be set as
default gateway. This default gateway is an IP address in DCN network.
 IP Planning MPLS-TP
Principles of IP Planning:
In the same network, two NEs with the same IP address can not coexist.
In one network, two different areas must have different area IDs.
In a network that is divided into different areas and levels, the NE IP address of the
backbone area shall be set as per the following rules: if the IP address of the NE is
W.X.Y.Z, different NEs can be differentiated with X in the IP address W.X.Y.Z, while the Y
in the IP address is usually the maximum effective value 254.
The NE IP address of a local area shall be set as per the following rules: if the address of a
area is W.X.0.0, the IP address of this NE must be set as W.X.Y.X. The Y is used for
differentiating different NEs in this local area.
Considering that old MSTP network usually uses 10.X.Y.Z address, the address field
assigned to PTN equipment is W.X.Y.Z (W>10) so that the old network and new network
may be integrated later.
 IP Planning MPLS-TP
Principles of IP Planning:
In the same area, the area attributes of all NEs shall be completely consistent, including
area ID, area address, area mask and external routing capability. The external routing
capability of the backbone area must be set as TRUE, thats to say,. the area type of the
backbone area must be TRANSIT.

When a network is divided into different areas and different levels and the network is
under the management of DCN network, the gateway NE can only be assigned to the
backbone area, rather than the local area.

Except for the gateway NE, the subnet mask of all the other NEs shall be set as
255.255.255.0.
 IP Planning MPLS-TP
OSPF Protocol:
OSPF allows areas to be divided in an autonomous
system.
Adjacent networks and their connecting routers
constitute an Area.
Each area has its own topological database which
is invisible to external areas. The link status
information database for routers in each area
actually contains only the link status information
of this area.
The routers in the same area have the same
topological database.
A router connected to multiple areas has the link
status information databases of multiple areas. The
method for dividing areas downsizes the link
status information database and greatly reduces
the amount of the status information exchanged
between routers;
 IP Planning MPLS-TP
Principles of Area Division:
If the network is not very large (with less than 50 NE nodes) and not very likely to
expand later and the network levels are not very clear, the single-area planning
method is applied.

In a network that is divided into different areas, the number of the NEs in the area is
preferably controlled within 80.

In the same network, any area must be continuous and can not be divided.
 IP Planning MPLS-TP
Precautions for IP Subnet:

When NEs are connected

through Ethernet, IP
addresses of NEs within the
same Ethernet must belong
to the same IP subnet;

When NEs are connected

through DCC, their IP
address must belong to
different IP subnets.
 IP Planning MPLS-TP
Precautions for IP Subnet:
The subnet address shall not be repeated in the same network.

Take the following figure as example, the subnet mask of all NEs in the figure is
255.255.255.0.

In the example shown in the picture below, although IP addresses of elements directly
connected with each other are not in the same subnet, IP addresses of NE1 and NE5
belong to the same subnet, and such configuration method is not allowed in the same
network.
 IP Planning MPLS-TP
Concept for GNE:
In this case, Workstation and equipment
are separated by DCN network (public
network), and each equipment network
connecting to DCN network respectively
corresponds to one gateway NE.

In this case, if IP configuration of

Workstation and each NE are correct,
ping only connects to gateway network
by entering command "ping NE IP
address" in DOS command window, and
ping doesnt connect to other NEs. If GNE
ping tools are used on workstation, ping
connects to all NEs.
 Agenda
Evolution of MPLS-TP

Introduction to MPLS-TP

IP Planning MPLS-TP

Network Management System

FiberHome PTN in Pakistan

Common Configurations

Common Troubleshooting Techniques

 Network Management System
OTNM2000 is the network Management System for Optical
Transport products in Pakistan
 Agenda
Evolution of MPLS-TP

Introduction to MPLS-TP

IP Planning MPLS-TP

Network Management System

FiberHome PTN in Pakistan

Common Configurations

Common Troubleshooting Techniques

 FiberHome PTN in Pakistan
CITRANS640 Backplane

For efficient Operations, Administration and Maintenance, Operator

must have the knowledge of FiberHome Equipment and its Backplane.
 FiberHome PTN
CITRANS660 Backplane
 Agenda
Evolution of MPLS-TP

Introduction to MPLS-TP

IP Planning MPLS-TP

Network Management System

FiberHome PTN in Pakistan

Common Configurations

Common Troubleshooting Techniques

 Common Configurations
Clock Configuration
In Case of Internal Clock
Click on XCU card of Source, configuration tab on the right pane.
 Common Configurations
Clock Configuration
Go to CLK-Work-Mode and Set it to Free

Click Clock-Priority-Sort and Set as None

 Common Configurations
Clock Configuration
Click on XCU card of Local NE, configuration tab on the right pane.
 Common Configurations
Clock Configuration
Go to CLK-Work-Mode and Set it to Lock

Click Clock-Priority-Sort and Set as Line Port as per connectivity

 Common Configurations
Clock Configuration
 Agenda
Evolution of MPLS-TP

Introduction to MPLS-TP

IP Planning MPLS-TP

Network Management System

FiberHome PTN in Pakistan

Common Configurations

Common Troubleshooting Techniques

Common Troubleshooting Techniques
Problem:1
Some Point to Point, or Point to Multi Point Service is not working!
Solution:
Service used to multiplexed through PW via tunnel so we need to
check the continuity first.
If channel Performance check of the PW is displaying discontinuity,
then all sections of the line need to be checked if every section is OK
and connected?
If channel Performance check shows continuity, then it means that
sections of the used line is fine and need to check on Add/Drop
Interface of Source/Destination.
Common Troubleshooting Techniques
Solution(Cont.): To check the Channel Performance, we need to
enable the CV Frames against the PW showing discontinuity as These
Test Frames used to be disabled by Default.

CV Frames Send Cycle can be

Set to Different values:
3.33ms
10ms
Common Troubleshooting Techniques
Solution(Cont.):
After Setting the Frames to Enable Mode, VC_LOC alarm used to
be appeared on Each side.

If continuity is OK then VC_LOC alarm will disappear. Alarm will

persist in case of Discontinuity.
Common Troubleshooting Techniques
Problem:2
Configuration Mismatch found at VPWS or PW Layer!
Reason:
These two kinds of alarms are caused by wrong configurations,
therefore inspection shall be mainly conducted on whether the
labels, PW labels, VLAN ID, LSP-ID and PW-ID being used are
repeated.
Solution:
Find the VPWS/VPLS Mismatch ID and locate the tunnel by Tunnel ID
Common Troubleshooting Techniques
Solution:
Find the VPWS/VPLS Mismatch ID.

Locate the tunnel by Tunnel ID and Re-deliver the Tunnel.

Check the working mode of ports.

Check the DCN Media as fluctuating Media also play important Role
in Configuration Mismatch if some site can not delivered
completely.
Common Troubleshooting Techniques
Problem:3
Client Service not found i-e Not working!
Solution:
Find the VPWS/VPLS Mismatch ID and locate the tunnel by Tunnel
ID

If there is no Mismatch alarm found on both of the cards

(source/destination), card configuration mapping shall be inspected,
mainly including items such as interface mode, correlation
configuration, VPWS configuration, PW configuration and TUNNEL
instrument configuration as shown:
Common Troubleshooting Techniques
Solution: