NMS Configurations MPLS TP

MPLS-TP
NMS Provisioning
Tejas Networks Limited 2021. All rights reserved.

Contents
MPLS-TP Configuration and features o Parameters which can be edited after tunnel/service
creation
o Creating TL using MPLS-TP nodes and Ports
- Editing Customer name
o Tunnel creation
- Adding protected tunnel to an unprotected
o -Creating unprotected tunnels tunnel group
o -Creation of protected tunnel - Enabling OAM on tunnel.
o LED indication on tunnel - Edit the tunnel on which the service is
o LED indication on service provisioned (Pseudowire migration)
o MPLS-TP Service creation
o SRLG
o OAM on tunnel and service
o 3G/4G Network
o Ping/Trace route on Service
o Full mesh
o External commands on Tunnel/pseudowire
o Hub and Spoke
o Viewing underlying Tunnel path from service created
o Dual home
o Node Augmentation
Tejas Networks Limited 2021. All rights reserved. 2

Enabling MPLS-TP feature on Ports & TL creation
After adding Nodes which support MPLS-TP, next step is to create Topological link.
Please create the Topological link (TL) first after the physical connection using fiber is done.
It can be done after topology view is launched. Select the nodes And then Click on Create TL , and then
select the ports and capacities.

Tunnel creation
For all MPLS-TP provision, tunnels have to be created first and then psuedowire on top of tunnels.
Service Tunnel

Tunnel creation
To begin with we create tunnel group (TG), every tunnel group can have work and protect tunnel
depending on the protection mode selected.
If protection mode is selected as ‘none’, tunnel group will only contain work tunnel (i.e unprotected TG).
If protection mode is selected as 1:1, tunnel group will contain both work and protect (i.e Protected TG).

Creating unprotected tunnels
Go to Configuration  L2  Complete tunnels
Click on add tunnel icon and select MPLS-TP.

Creating unprotected tunnels contd…
Enter a unique name for the tunnel.

Shared tunnel: if the box is checked, this tunnel will be visible to all customers while creating service
If the box is unchecked, customer name has to be entered. In this case tunnel will be visible only to one particular
customer whose name is mentioned during tunnel creation.
Protection mode has to be none since we are creating unprotected tunnel.
Path selection:
Plan manually – user can select the link on which tunnel has to be created.
Auto discover- NMS will select the link automatically.7
As of now, Domain is kept as all domain. QoS related configuration is covered in the later section.
To check the status of the tunnel, OAM can be enabled. Check the box.
Mention the MD level from the drop down and specify a name to the Maintenance domain.
Support adding protection: if checked, there is an option of adding protection tunnel later to the tunnel group.
Click on next.
Click on add.
Select two end nodes(starting and ending point of the tunnel).

Click on next, Topology view will open, select the link.
Click on add work and then done.
Click on next .
CCM interval can be set.
There is an option to enable Y1731 from the NMS which
can be used for loss and delay measurement.
Finally click on create and activate and then finish.

(NOTE: If only create is selected, tunnel will be created only in NMS and not in the node)

Creation of protected tunnel
Links Tunnel Group Work Tunnel Protect Tunnel Service
All the steps remain same as creating unprotected tunnel.

Only change would be to select Protection mode as 1:1 and
OAM must be enable while creating protected tunnel.
Mention Maintenance Domain information by clicking on
After adding Maintenance domain, select the created one
from the drop down.
Tunnel can be made revertive by checking the box.
Reversion policy has to be Revert to Work.
LED indication on tunnel
LED is ‘White’ for Tunnels in Pending/Partial/Conflict/Orphan state.

LED is ‘Green’ for no alarms.
LED is ‘Red’ for following alarms –
1. Loss of Signal
2. Auto-Negotiation Failed
3. Forced down-Link Integrity
4. Connectivity Check Failed on MEP
Tejas Networks Limited 2021. All rights reserved. 12 12

LED indication on service
LED is ‘White’ for Services in Pending/Partial/Conflict/Orphan state.

LED is ‘Green’ for no alarms.
LED is ‘Red’ for Eline services if following alarms are present on UNI/NNI ports –
1. Loss of Signal
5. Pseudowire Down
LED is ‘Grey’ for Elan services if following alarms are present on UNI/NNI ports –
1. Loss of Signal
5. Pseudowire Down

MPLS-TP Service creation
Go to ConfigurationL2  Services  Complete services.
Click on add service icon and select .1q/.1ad-MPLS-TP

MPLS-TP Service creation
Service Name: Give a unique name to the service.
Customer name: Customer name can be created and can attached with the
Service(eg:- Tejas). If the shared path box is not checked then only tunnels created with
the customer name Tejas will be shown.
Technologies: Select technology as MPLS-TP
Service type as Eline for simple point to point service.
Domain: All Domain
Enable PSC: This provides external commands to be issued on the psuedowire.
OAM can be enabled to check the health of the pseudowire.
Uncheck the SRLG disjoint box. This feature can be used once its application is
known( please refer to following slides)
Click on next.

MPLS-TP Service creation contd…
Click on Add, select the end points of the service. Select the switch ,select the UNI ports and enter Vlan, If All box is
checked, Port will allow all vlans, Click on Add uni

Add the other end point as well, after adding you can check the summary of the switch and UNI ports added.
If this box is checked, NMS will automatically select one tunnel after clicking on find path.
• If this box is unchecked, user can select the tunnel manually after clicking on
Manual path.

Topology view showing the nodes and tunnels between them is opened.
Select the desired tunnel and click on Add work and then Done.
Finally click on create and activate and then finish.
If create is selected, service will be created only in NMS and not
in the node.

MPLS-TP ELAN Service creation
Service Name: Give a unique name to the service.
Customer name: Customer name can be created and can attached with the
Service(eg:- Tejas). If the shared path box is not checked then only tunnels created with
the customer name Tejas will be shown.
Technologies: Select technology as MPLS-TP
Service type as ELAN for point to multi-point service.
Domain: All Domain
Enable PSC: This provides external commands to be issued on the psuedowire.
OAM can be enabled to check the health of the pseudowire.
Uncheck the SRLG disjoint box. This feature can be used once its application is
known( please refer to following slides)
Click on next.

In the case of Hub and Spoke or Full Mesh ELAN services. Make sure all the underlying tunnels are created first.
Add the Hub node its UNI and then add the Spoke nodes and UNI and add all the UNI ports in case of Full
Mesh ELAN Service.

In the case of Hub and Spoke or Full Mesh ELAN services.
Make sure all the underlying tunnels are created first on all the multiple NNI ports where traffic needs to flow.
All the other steps remains same as ELINE service as mentioned in slides 14 to 17.
In case of the protection scenarios make sure there are already multiple paths and tunnels availabilities.
The service switches to the protect path of the underlying tunnels using Hierarchical protection.
Create the ELAN service.
Once Activated the ELAN service is also pushed to the respective nodes.

OAM on tunnel and service
To check the health of the tunnel, Ping and trace route can be performed.
Double click on the tunnel, click on icon.
Message type: Ping or Trace route can be selected.
Path type: Ping/trace route can be performed either on
Work or on protect tunnel, which has to be mentioned here.
Source MEP: select any one of the end node.
TTL: Time to leave, can be 255.
Number of packets: Number of ping packets user wish
to send for verifying the path.(Max 50).
Payload side: Frame size of the ping packets.
Interval: Time between two ping packets
Click on create.
Check the refresh box on the top right corner.

OAM on tunnel and service contd…
Ping result will be displayed in the same page after few seconds. If the link is fine, Rx packets will be equal to Tx packets.

To perform trace route, again click on Icon.
Select message type as LSP trace route.
Path type: Ping/trace route can be performed either on
Work or on protect tunnel, which has to be mentioned here.
Source MEP: select any one of the end node.
Click on create.
Check the refresh box on the top right corner.

Click on Show Trace route path. If the tunnel is fine, the link is shown in blue colour, if there is a fault on the tunnel it is
shown in red.
a. Path with no failures

b. Path with failures
Ping/Trace route on Service
To check the health of service, Ping and trace route can be performed.
Double click on the tunnel, click on icon.
Steps remain same as performing ping/trace route on tunnel.

External commands on Tunnel/pseudowire
Get inside the tunnel/service, click on trigger external command icon, select the command from the dropdown and
click on Go.
After giving the command, status can be checked by clicking on view .

Viewing underlying Tunnel path from service created
From the created service user can check tunnel the service is taking and also there is an option to see the ethernet
links involved in the tunnel creation.
Double click on the service created.
Click on pseudowire tab, check show tunnel path box.
Point to the link, Port number of the link are shown.

Up MEP Support for MPLS-TP Services
MEPs are used to check connectivity, UP MEP is used to check end to end connectivity of the service path. UP MEP
are configured on UNI ports of the end nodes.
MPLS-TP cloud
UNI UNI
A B C
UP MEP monitors end to end service path
If the UNI port is down on the other end, Remote MEP interface down alarm is raised on the local end in the service.

How to configure?
Steps are similar to normal service creation, extra thing which needs to be done is check Enable CFM
box.
Select the end points and then select the path.

How to configure?
Under CFM configuration all the port in the service path will be shown. Select the UNI ports of the service one by one
and click on Add MEP. MEP creation window is opened, click on the PLUS icon and create a maintenance Domain.

How to configure?
Consider two nodes setup for creating UP MEP, Select the maintenance domain from drop down.
192.168.106.52 192.168.106.72
MEP ID: 1(local) MEP ID: 2

Remote MEP ID: 2 Remote MEP ID: 1
MEP Direction should be UP.

Primary VID: Mention one VLAN for CCMs to flow.( Ex: If vlan range in the service is 501-510, one vlan can be used
for UP MEP, Same vlan can be used for data as well.)
MEP ID: Two MEP IDs are needed local and remote MEP IDs as shown in the figure but from NMS only Local MEP
will be given on both sides. At 52 node MEP ID is 1 and at 72 node MEP ID is 2. Remote MEP ID are taken
automatically.
Repeat this for other UNI port and click and create and activate.

Parameters that can be edited
after tunnel/service creation

1.Editing Customer name
Go to Configuration L2  Tunnels  Complete tunnels. Double click on the tunnel.
Click on edit option, user can edit customer name.
This is useful when tunnel is not a shared tunnel, if the user wants to create services of new customer on the existing
tunnel, user can make unshared tunnel as shared tunnel or can edit the customer name.

2. Adding protected tunnel to an unprotected tunnel group
Consider an example, Where there is a single link between two nodes in the network, there is no extra link to provide
tunnel protection.
User has no option but to create unprotected tunnel. In future if in case extra link is added between the nodes, user can
add protection to the existing tunnel without deleting the tunnel and services on them.
This is possible by checking the support adding protection box while creating tunnel.

How to add protect tunnel?
Goto Configuration  L2  Tunnels  Complete tunnels.
Double click on the tunnel, Click on add protection to tunnel icon.
Note: OAM has to enabled on the tunnel for the add protection option to
be seen tunnel. Refer next slide on how to enable OAM
Select the protect tunnel path from the topology and activate the tunnel .

3.Enabling OAM on tunnel
If the OAM is not enabled for, while creating a tunnel, there is an option to enable it later.
Double click on the tunnel, click on Enable OAM option.

4. Edit the tunnel on which the service is provisioned
(Pseudowire migration)
Go to Configuration  L2  Services  Complete services.
Double click on the service, click on edit, select the pseudowire.
Remove the link/tunnel on which the service is provisioned, and add the new link.

SRLG
In Real time networks, bunch of fibers will be carried from one location to other. Here fiber ducts are used to carry
bunch of fibers. In case of Fiber cut scenarios, there is a high chance of the entire duct getting damaged. Which means
all the fiber pairs are affected. We have protection mechanism to compensate these fiber cuts. Where we can select
protection path. What if the protection path fiber is also taken over the same duct?
In that case, providing protection is of no use. In order to overcome this situation we have SRLG feature which helps to
monitor fibers which are going on the same duct.
Same IDs will be given to all the fibers, which are going over the same duct.
While selecting protection path if SRGL disjoint is selected, NMS the will not let you select the protection path on the
same duct.
Work path
1
1
1
Fiber duct
2
2
2
Links/fiber
Protect path

How to provision SRLG?
First step would be creating SRLG IDs.
Second step would be attaching these IDs to links (Ports).
To create IDs, Go to Topology  SRLG  Create SRLG
Enter IDs and description and click on create

How to provision SRLG? Contd…
To attach the IDs to the links (ports), Goto TopologySRLGManage SRLG
Select the ID which you have created from drop down.
Type the IP of the node and click on search, it will list out the links, select the required links and click on
Apply.


Consider the setup: 3 links are assigned same ID which is 1.
Other one link is assigned with a ID 2.
Consider a scenario where tunnel level protection has to be provisioned,
Create a protected tunnel group, while creating tunnel make sure
SRLG Disjoint box is checked.

Work tunnel is created on links which has SRLG ID 1(3 links has ID 1 and 1 link has ID 2).
As soon as work path is selected, links with ID 1 are not shown. Link with different SRLG IDs are shown for the protect
tunnel.
a. SRLG disabled b. SRLG enabled

Where Full Mesh, Hub and spoke
and Dual home services are
used??
3G/4G Network
Dual home
Hub and Spoke
Full Mesh service

How to provision Full mesh?
Tunnels have to be created between all the nodes involved. Tunnels can be protected or unprotected.
Goto configuration  L2 complete services.
2
Make sure Service type is ELAN and Full Mesh is selected from the drop down. 1
7 8
Select the end points(nodes) and UNI ports and provide a VLAN. 9
NMS will list out the number of pseudowires which has to be created after adding end points. 10 3
5
In this example, 10 end points have been added. Hence, 10 pseudowire has to be selected. 6
4

How to provision Hub and Spoke?
Tunnels have to be created between hub and every spoke.

Go to configuration  L2  Complete services.
Make sure Service type is ELAN and Hub and Spoke is selected from the drop down.

Hub and Spoke contd…
Add a Hub node first and then add spokes and add UNI ports on them.
Click on Next. Pseudowires will be listed out.

If 2 spokes are added for example, then select the pseudowire one by one (one for Hub <-> Spoke-1 and
another for Hub <-> Spoke-2) and select the path from the topology view.
Then click on Create and Activate

Hub and Spoke contd…

How to provision Dual home?
Tunnels have to be created between primary node and end node, backup node and end node.
Primary node
Ethernet link between primary node and backup node.
Go to Configuration L2  Complete services.
Ethernet
Make sure Service type is Eline and check the dual home box. end node link
Backup node
Tunnels
Note:
1.Service type is ELine to create a dual home-
eline service. To create a dual home-elan sevice
type is Elan and Mesh type is Hub and Spoke.
2. OAM has to be enabled on the dual home
service.

Dual home contd…
Select the primary node 1st and check on the dual home on the right top corner and then the end node.

Dual home contd…
Later backup node has to be selected.
Click on Add link and select the L2 link between primary and backup node.

Dual home contd…
Note: OAM has to be enabled on the dual home service.

Work pseudowire will be between primary node and end node.
Protect pseudowire will be between backup node and end node.

Node Augmentation
Node Augmentation is the process of adding a new midpoint between two already existing end nodes with
end to end tunnels between them
Few things to be taken care while doing node augmentation are:
1. Node augmentation is done to add only midpoint. Not applicable for end nodes
2. This midpoint node can have only pass through tunnels. No end tunnels should be configured on it
3. LLDP should be disabled on the links connecting the original two nodes

How to configure?
To do node augmentation, go to Topology view  Network view (Nodes)
Select the link between the two end nodes and click on icon as shown
(NOTE: For protected tunnels it is always preferred to switch the traffic to protect tunnel before doing node augmentation on
work and vice-versa)

Node Augmentation contd…
Now enter the node name or select the check box next to IP and enter the IP address (Router ID for a non GNE) of the
node to be added/augmented. Click on icon
Select the two ports together (using CTRL button) which would be connected to both the end nodes and click on Select
pair. Then click on Augment Node. The first port selected will always connect to the west node port

This can be verified by checking the tunnels for the midpoint node
Go to Topology view  Network view (Switches)
Select the midpoint and then click on icon. Select Tunnels from the drop down and click OK

Tunnels for the selected switch (midpoint node here) will be displayed as shown below

Other Additional features

Boundary Nodes Display in Switch View
NMS shows terminal switches of an inter partition TL in both the partitions.

NMS distinguishes boundary nodes with the help of their display color.
Boundary nodes are shown in pink color in switch view.

‘Creation timestamp’ in service, tunnel & node
NMS displays the time(creation timestamp) when tunnels, services are created.

Create Service/tunnel from topology view using
selected partitions
NMS support creation of tunnels/services by selecting partition from topology view.
Goto Topology view  Network view(switches)
Select partitions between which tunnels/services have to be created.
Right click and select the required option.

Creation of tunnels using already existing tunnels
This option is useful when one more tunnel has to be created which takes the same path as the tunnel which is already
present in the NMS.
User don’t have to search again for end points and links from topology view.
Click on select the tunnel, right click on the selected tunnel, select create tunnel using select tunnels

Creation of tunnels contd…
While selecting end nodes, click on ADD, Only two nodes will be shown( this information is taken from
already existing tunnel).

Creation of tunnels contd…
While selecting the path for tunnel, NMS will show the path taken by the already existing tunnel.

Creation of services using already existing services
This option is useful when one more service has to be created which takes the same path as the service
which is already present in the NMS.
User don’t have to search again for end points and links from topology view.
Click on select the service, right click on the selected service, select create service using select
services.

Tagged MPLS
Tagged MPLS is used when intermediate node doesn’t support MPLS but supports only .q or .ad services or if you have
third party cloud. In this case to pass tunnels seamlessly through this node which doesn’t support MPLS-TP we make
use of tagged MPLS.
MPLS-TP MPLS-TP
enabled enabled
.q .q
port port
A B C
Ingress vlan: 100 Create Service Ingress vlan: 101

Egress vlan : 101 which includes 100 Egress vlan : 100
and 101 tags
This is achieved by giving Ingress and Egress vlans on node A and C, match ingress and egress vlans like how it is
shown in the figure.
At B node, create an Eline service which includes both 100 and 101 tags.

How to configure?
From the figure above, third party cloud is placed between node TJ1400_52_R1 and TJ1400P_72_R1.
Steps to create tunnels remain same but one addition step would be mentioning the vlan tags(ingress and Egress vlan)
in the Path Details step.

Acronyms
EMS- Element Management System ERPS- Ethernet Ring Protection Switching
NMS- Network Management System MPLS-TP – Multi Protocol Label Switching - Transport
Profile
SRLG- Shared Risk Link Group
OAM- Operation Administration & Maintenance
LLDP- Link Layer Discovery Protocol
QoS- Quality of Service
VLAN- Virtual LAN
CoS- Class of service
ELINE- Ethernet Virtual Private Line (EVPL)
ELAN- Ethernet Virtual Private LAN (EVP-LAN)
UNI- User Network Interface
NNI- Network Node Interface
CVLAN- Customer VLAN
SVLAN- Service Provider VLAN
PVID- Port VLAN ID
LAG- Link Aggregation Group
LACP- Link Aggregation Control Protocol
Thank you!
Contact Us:
[email protected]

NMS Configurations MPLS TP

Uploaded by

Copyright:

Available Formats

NMS Configurations MPLS TP

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NMS Configurations MPLS TP

Uploaded by

Copyright:

Available Formats

MPLS-TP

Tejas Networks Limited 2021. All rights reserved.

Tejas Networks Limited 2021. All rights reserved. 2

Tejas Networks Limited 2021. All rights reserved. 3

Tejas Networks Limited 2021. All rights reserved. 4

Tejas Networks Limited 2021. All rights reserved. 5

Tejas Networks Limited 2021. All rights reserved. 6

Enter a unique name for the tunnel.

Tejas Networks Limited 2021. All rights reserved. 9

Finally click on create and activate and then finish.

Tejas Networks Limited 2021. All rights reserved. 10

Links Tunnel Group Work Tunnel Protect Tunnel Service

All the steps remain same as creating unprotected tunnel.

LED is ‘White’ for Tunnels in Pending/Partial/Conflict/Orphan state.

Tejas Networks Limited 2021. All rights reserved. 12 12

LED is ‘White’ for Services in Pending/Partial/Conflict/Orphan state.

Tejas Networks Limited 2021. All rights reserved. 13

Tejas Networks Limited 2021. All rights reserved. 14

Tejas Networks Limited 2021. All rights reserved. 15

Tejas Networks Limited 2021. All rights reserved. 16

Tejas Networks Limited 2021. All rights reserved. 17

Tejas Networks Limited 2021. All rights reserved. 18

Tejas Networks Limited 2021. All rights reserved. 19

Tejas Networks Limited 2021. All rights reserved. 20

In the case of Hub and Spoke or Full Mesh ELAN services.

Tejas Networks Limited 2021. All rights reserved. 21

Tejas Networks Limited 2021. All rights reserved. 22

Tejas Networks Limited 2021. All rights reserved. 23

Tejas Networks Limited 2021. All rights reserved. 24

a. Path with no failures

Tejas Networks Limited 2021. All rights reserved. 26

After giving the command, status can be checked by clicking on view .

Tejas Networks Limited 2021. All rights reserved. 28

UP MEP monitors end to end service path

Tejas Networks Limited 2021. All rights reserved. 29

Tejas Networks Limited 2021. All rights reserved. 30

Tejas Networks Limited 2021. All rights reserved. 31

MEP ID: 1(local) MEP ID: 2

MEP Direction should be UP.

Tejas Networks Limited 2021. All rights reserved. 32

Tejas Networks Limited 2021. All rights reserved.

Tejas Networks Limited 2021. All rights reserved. 34

Tejas Networks Limited 2021. All rights reserved. 35

Tejas Networks Limited 2021. All rights reserved. 36

Tejas Networks Limited 2021. All rights reserved. 37

Tejas Networks Limited 2021. All rights reserved. 38

Tejas Networks Limited 2021. All rights reserved. 39

Tejas Networks Limited 2021. All rights reserved. 40

Tejas Networks Limited 2021. All rights reserved. 41

Tejas Networks Limited 2021. All rights reserved. 42

Tejas Networks Limited 2021. All rights reserved. 43

a. SRLG disabled b. SRLG enabled

Hub and Spoke

Full Mesh service

Tejas Networks Limited 2021. All rights reserved. 46

Tejas Networks Limited 2021. All rights reserved. 47

Tunnels have to be created between hub and every spoke.

Tejas Networks Limited 2021. All rights reserved. 48

Click on Next. Pseudowires will be listed out.