mpls deployment chapter 1 - basic1

7/29/2019 MPLS Deployment Chapter 1 - Basic1

1/80

Muhammad Syarifuddin, CCNA, CCNP, NRS-1

http://id.linkedin.com/in/syarifuddin
http://id.linkedin.com/in/syarifuddinhttp://id.linkedin.com/in/syarifuddinhttp://id.linkedin.com/in/syarifuddin


2/80

Chapter 1 Basic :http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-1-basic1Chapter 2 Services :http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-2-services1

Chapter 3 Optimization :http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-3-optimization
http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-1-basic1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-2-services1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-2-services1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-2-services1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-2-services1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-3-optimizationhttp://www.slideshare.net/ariefcakep/mpls-deployment-chapter-3-optimizationhttp://www.slideshare.net/ariefcakep/mpls-deployment-chapter-3-optimizationhttp://www.slideshare.net/ariefcakep/mpls-deployment-chapter-3-optimizationhttp://www.slideshare.net/ariefcakep/mpls-deployment-chapter-3-optimizationhttp://www.slideshare.net/ariefcakep/mpls-deployment-chapter-3-optimizationhttp://www.slideshare.net/ariefcakep/mpls-deployment-chapter-3-optimizationhttp://www.slideshare.net/ariefcakep/mpls-deployment-chapter-3-optimizationhttp://www.slideshare.net/ariefcakep/mpls-deployment-chapter-3-optimizationhttp://www.slideshare.net/ariefcakep/mpls-deployment-chapter-3-optimizationhttp://www.slideshare.net/ariefcakep/mpls-deployment-chapter-3-optimizationhttp://www.slideshare.net/ariefcakep/mpls-deployment-chapter-2-services1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-2-services1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-2-services1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-2-services1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-2-services1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-2-services1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-2-services1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-2-services1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-2-services1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-1-basic1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-1-basic1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-1-basic1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-1-basic1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-1-basic1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-1-basic1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-1-basic1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-1-basic1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-1-basic1http://www.slideshare.net/ariefcakep/mpls-deployment-chapter-1-basic1


3/80

Multiprotocol Label Switching (MPLS) is amechanism in high-performancetelecommunications networks that directs datafrom one network node to the next based on

short path labels rather than long networkaddresses, avoiding complex lookups in arouting table. The labels identify virtual links(paths) between distant nodes rather thanendpoints. MPLS can encapsulate packets of

various network protocols. MPLS supports arange of access technologies, including T1/E1,ATM, Frame Relay, and DSL.


4/80

In 1996 a group from Ipsilon Networks proposed a"flow management protocol". Their "IP Switching"technology, which was defined only to work over ATM,did not achieve market dominance. Cisco Systems

introduced a related proposal, not restricted to ATMtransmission, called "Tag Switching". It was a Ciscoproprietary proposal, and was renamed "LabelSwitching". It was handed over to the InternetEngineering Task Force (IETF) for openstandardization. The IETF work involved proposals

from other vendors, and development of a consensusprotocol that combined features from several vendors'work.


5/80

MPLS brings the following benefits to IP networks: Improved up-time By providing alternative network paths Improved bandwidth utilization By allowing for multiple traffic

types to traverse the network Reduced network congestion By utilizing optional paths for

traffic to avoid congestion Improved end user experience By allowing multiple Classes of

Service to different types of traffic such as VOIP Traffic engineering - the ability to set the path that traffic will

take through the network and the ability to set performancecharacteristics for a class of traffic.

Layer 2 transport - new standards allow service providers to carryLayer 2 services including Ethernet, Frame Relay and ATM over an

IP/MPLS core


6/80

Beside of its benefits, MPLS have several

issues : The carrier has to play a role in configuration

of the overall network. MPLS network does not offer any inherent data

protection and improper implementation canopen your network to vulnerabilities.

Possibilities to peek up end user traffic fromService Provider Network


7/80

Label switching through label path

PE PEP

P

P

P

Label Path

P router digunakan di sisi backbone,

PE router digunakan di sisi ujung (edge) yang

memberikan service ke CE,

CE adalah end user. CE dapat berupa router, server

telco equipment (bsc, rnc, msc/mgw, bts, radio), dll.

CE

CE

CE


8/80

LABEL SWITCHING

IP IP label

PE PE

Label swapping networking technology that forwards packetsover multiple, underlying layer 2 media.

Integrates layer 2 switching and layer 3 routing by linking the layer 2

infrastructure with layer 3 routing characteristics.

PP

IP label IP label IP

Label Path

Layer 3 routing occurs only at the edge of the network, and layer 2

switching takes over in the MPLS core.

IP ForwardingIP Forwarding

CE CE


9/80

Ethernet PPP

Shim Label(s)

Label Exp. S TTL

Label: Label Value, 20 bits (0-15 reserved)

Exp.: Experimental, 3 bits (Class of Service)

S: Bottom of Stack, 1 bit (1 = last entry in label stack)

TTL: Time to Live, 8 bits

Layer 2 Header

(eg. PPP, 802.3)

Network Layer Header

and Packet (eg. IP)

4 Octets

MPLS Shim Headers (1-n)

1n

Label Stack

Entry Format

Packet-based encoding


10/80

Push

Push the first label on the packet or

Push a label on existing label stack

For IP packets, set the TTL value of the label to the valuein the IP packet

Pop

Remove the top label from the packet

Copy the TTL value of the label to the TTL value of the IPPacket

Swap (applies to LSR only)

Combination of POP and PUSH operation

Copy the TTL value from incoming label to new label afterdecrementing it


11/80

FEC = A subset of packets that are all treated the same way by a router

The concept of FECs provides for a great deal of flexibility and scalability

In conventional routing, a packet is assigned to a FEC at each hop (i.e. L3

look-up), in MPLS it is only done once at the network ingress.

Packets are destined for different address prefixes, but can be

mapped to common path

LSRLSRLER LER

LSP

IP1

IP2

IP1

IP2

IP1 #L1

IP2 #L1

IP1 #L2

IP2 #L2

IP1 #L3

IP2 #L3

IP1 #L2

IP2 #L2

IP1 #L3

IP2 #L3

IP1 IP1


12/80

Label protocols in MPLS were divided in threeitems: LSP (Label Switched Patch)

Is static label distribution that need to be createdmanually in P & PE Routers.

LDP (Label Distribution Protocol)

Dynamic protocol that automatically generates labelpath between Routers

RSVP (Resource Reservation Protocols)

Provide better reroute time failure


13/80

All Routers are configured manually with labels No signaling is required

12

3 4

5

47.1

123

DestLabel

Out

47.1 123

Int

In

-

Int

Out

2

123

456

456

DestLabel

In

47.1 123

Int

In

3

Int

Out

4

Label

Out

456

Dest

47.1 4565 -

Label

In

Int

In

Int

Out


14/80

ESR

or

Core Router

ESR

ESR

ESR

ESR

ESR

ESR

ESR

LSP Primary

Path

LSP Secondary

Path (Non-Fate

Sharing )

Secondary Path LSPs can be:

Standby (preconfigured)

Signaled and set up upon failure of the primary LSP

Hello REQ

Hello ACK

PATH

Refresh

RESV

Refresh


15/80

ESR

or

Core Router

ESR

ESR

ESR

ESR

ESRESR

ESR

LSP Primary

Path

LSP Secondary

Path (Non-Fate

Sharing )

When Primary Path Fails The first secondary path becomes active

Attempts are made to restore primary path (retry timer)

Software will revert back to primary when it recovers

RESV

ERR

PATH

ERR

Hello REQ

Hello REQ


16/80

Difficult to quickly restore connectivity usingtraditional IP protocols because:

Failures are not detecting quickly

Takes time to compute an alternate routeTakes time to signal an alternate LSP and update

forwarding tables


17/80

Protected

LSP

R1

R2

R3

R4

R5R6 R7

R8

R9

Protected LSP: R1>R2>R3>R4>R5

R1s backup: R1>R6>R7>R8>R3

R2s backup: R2>R7>R8>R4

R3s backup: R3>R8>R9>R5

R4s backup: R4>R9>R5


18/80

R1

R2

R3

R4

R5

R8

R6

R7

R9

Protected LSP 1: R1>R2>R3>R4>R5

Protected LSP 2: R8>R2>R3>R4

Protected LSP 3: R2>R3>R4>R9

Bypass LSP Tunnel: R2>R6>R7>R4


19/80

One of several standardised label distributionprotocol draft-ietf-mpls-ldp-09.txt

A set of procedures and messages to distributemappings between labels and FECs

Two LSRs which use LDP to exchangelabel/FEC mapping information are known as"LDP Peers"

Peers exchange LDP messages

Uses TLV encoded message structure


20/80

Discovery messages Used to discover and maintain the presence of new peers Hello packets (UDP) sent to all-routers-in-subnet multicast

address Once neighbor is discovered, the LDP session is established

over TCP Runs over UDP port number 646

Session messages Establish, maintain and terminate LDP sessions Runs over TCP port number 646

Advertisement messages Create, modify, delete label mappings

Notification messages Error signalling


21/80

NTW NTW NTW NTWNTW NTW

RTM

Route x use 1.1.1.2

Form an Adjacency Form an Adjacency Form an Adjacency

Maintain LDP session Maintain LDP sessionMaintain LDP session

Use label 1 to reach x Use label 7 to reach x Use label 9 to reach x

RTM

Route x use label 1

RTM

Route x use label 7

RTM

Route x use label 9

1

2

3

SR-A SR-B SR-C SR-D

NTW Network Link RTM = route mapping

Alternative to MPLS /RSVP-TE signaling to obtain routing labels.


22/80

RSVP uses two message types for resource reservation

Sender sends PATH message towards receiver indicating characteristics of the traffic

Each Router along the path makes note of the traffic type

Receiver sends RESV message back towards sender

Each Router reserves the resources requested (if available) for the micro-flow

Path Refresh and RESV Refresh messages are sent periodically

1

2

3 4

5 ResV: 10.10.10.1

Path Refresh

Resv Conf

ResV Refresh

Path Tear

Resv Error

ResV Tear

Path Error

Path: 30.30.30.1

ResV: 10.10.10.1

Path: 30.30.30.1

ILER

ELER


23/80

RSVP-TE has extensions to support operation with MPLS:

Provide the mechanism to setup an explicitly routed LSP that coulddiffer from the normal path calculated by the IGP.

Perform downstream on demand label allocation, distribution, andbinding among LSRs in the path, thus establishing path state innetwork nodes.

Optionally provide resource reservations (bandwidth) along the path tomeet the requirements of the traffic flow.

Provide users information about the actual path traversed by the LSP.

LSP preemption based on administrative policy control.

Loop detection and avoidance during the initial LSP set-up andrerouting an existing LSP.

Monitor and maintain the state of an explicitly routed LSP


24/80

RSVP Refresh Reduction

PATH Refresh and RESV Refresh are sent out for eachLSP

Multiple messages are bundled into a singlemessage to reduce network overhead

Each bundled message contains Multiple Message-ids of the associated PATH and RESV messages forwhich the state needs to be refreshed


25/80

ESR

or

Core Router

ESR

ESR

ESR

ESR

ESRESR

ESR

Primary LSP

Secondary LSP Hot Standby Detour

Hello REQ

Hello ACK

RSVP Failure Detection Hello Message exchanged between neighbors

Enables failure detection in milliseconds


26/80

Study Case, General Requirement : Customer requested to use Cisco Router as the platform. To keep compatibility with non-Cisco devices,routing

protocol that will be used is OSPF. Label Protocol = LDP. Every region has different OSPF area to keep ospf

calculation locally. Area 0 for backbone PR, area 1 forjakarta, area 2 for east java, and area 3 for borneo. Ring topology will be used for P router. From jakarta1

jakarta2 - surabaya1 - banjarmasin1 jakarta1. To keep redundancy, there will be 2 P router in jakarta that

will serve as master & backup.


27/80

2 P routers in jakarta were connected to 5 PE (2jakarta, 1 bekasi, 1 bogor, 1 tangerang), 1 Psurabaya connected to 3 PE (1 surabaya, 1malang, 1 madiun), 1 P banjarmasin connectedwith 1 PE in the same place.

Due to services that will be delivered fromPEJKTKPI01 & PEJKTKPI02 were critical, to provideredundancy, PEJKTKPI01 have direct link toPEJKTKPI02

PRJKTKPI01, PRJKTKPI02, PEJKTKPI01, PEJKTKPI02were placed in same room


28/80

East Java Area were designed to use ringtopology with distribution point to P surabaya.P surabaya PE surabaya PE malang PEmadiun P surabaya.

For Borneo area, there is only 1 P & 1 PE. Wecreate 2 interface point to point forredundancy


29/80

Loopback IP is used to stabilize

OSPF, BGP, MPLS LDP,

and many router processes

Device Ip Loopback

PRJKTKPI01 10.0.0.1/32

PRJKTKPI02 10.0.0.2/32

PEJKTKPI01 10.0.0.3/32

PEJKTKPI02 10.0.0.4/32

PEBTNTGR01 10.0.0.5/32PEJBRBKS01 10.0.0.6/32

PEJBRBGR01 10.0.0.7/32

PRJTMSBY01 10.0.0.8/32

PEJTMSBY01 10.0.0.9/32

PEJTBMLG01 10.0.0.10/32

PEJTMMDN01 10.0.0.11/32PRKALBJM01 10.0.0.12/32

PEKALBJM01 10.0.0.13/32

Loopback IP Design


30/80

Area 3 Kalimantan

Area 2 Jatim

Area 1 Jakarta

Area 0 CORE

10.10.10.1/3010.10.10.2/30 10.1

0.10.5/3

0

10.10.1

0.6/30

10.10.10.9/30

10.10.10.10/30

10.10.10

.13/30

10.10.10.14/30

PRJKTKPI02

10.0.0.2/32

PRJKTKPI01

10.0.0.1/32

PEBTNTGR01

10.0.0.5/32 PEJBRBGR01

10.0.0.7/32

PEJBRBKS01

10.0.0.6/32

PRJTMSBY0110.0.0.8/32

PEJTMSBY01

10.0.0.9/32

PEJTMMDN01

10.0.0.11/32

PEJTMMLG01

10.0.0.10/32

10.10.20.2/30

10.10.20.1/30

10.10.20.6/30

10.10.20.5/30

10.10.20.10/3010.10.20.9/30

10.10.20.14/3010.10.20.13/30

10.10.20.18/30

10.10.20.17/30

10.10.20.21/30

10.10.20.22/30

10.10.30.2/30

10.10.30.1/30

10.10.30.6/30

10.10.30.5/30

10.10.30.13/30

10.10.30.14/30

10.10.30.9/30

10.10.30.10/30

10.10.40.1/30

10.10.40.2/30

Tangerang

Jakarta

Bogor Bekasi

Jakarta

Jakarta

Jakarta

Banjarmasin

Banjarmasin

Surabaya

Surabaya

Madiun

Malang

Design by : Muhammad SyarifuddinRevision : 4

Project : MPLS Core Network

PEJKTKPI01

10.0.0.3/32PEJKTKPI02

10.0.0.4/32

10.10.20.26/30

10.10.20.25/30

PRKALBJM01

10.0.0.12/32

PEKALBJM01

10.0.0.13/32

10.10.40.5/30

10.10.40.6/30


31/80

Area 0 CORE

10.10.10.1/30

10.10.10.2/3010.1

0.10.5/3

0

10.10.10

.6/30

10.10.10.9/30

10.10.10.10/30

10.10.10

.13/30

10.10.10.14/30

PRJKTKPI02

10.0.0.2/32

PRJKTKPI01

10.0.0.1/32

PRJTMSBY01

10.0.0.8/32

PRKALBJM01

10.0.0.12/32

Jakarta

Jakarta

Banjarmasin

Surabaya


32/80

Area 1 Jakarta

10.10.10.1/3010.10.10.2/30

PRJKTKPI02

10.0.0.2/32

PRJKTKPI01

10.0.0.1/32

PEBTNTGR01

10.0.0.5/32 PEJBRBGR01

10.0.0.7/32

PEJBRBKS01

10.0.0.6/32

10.10.20.2/30

10.10.20.1/30

10.10.20.6/30

10.10.20.5/30

10.10.20.10/3010.10.20.9/30

10.10.20.14/3010.10.20.13/30

10.10.20.18/30

10.10.20.17/30

10.10.20.21/30

10.10.20.22/30

Tangerang

Jakarta

Bogor Bekasi

Jakarta

Jakarta

Jakarta

PEJKTKPI0110.0.0.3/32

PEJKTKPI02

10.0.0.4/32

10.10.20.26/30

10.10.20.25/30


33/80

Area 2 JatimPRJTMSBY01

10.0.0.8/32

PEJTMSBY01

10.0.0.9/32

PEJTMMDN01

10.0.0.11/32

PEJTMMLG0110.0.0.10/32

10.10.30.2/30

10.10.30.1/30

10.10.30.6/30

10.10.30.5/30

10.10.30.13/30

10.10.30.14/30

10.10.30.9/30

10.10.30.10/30

Surabaya

Surabaya

Madiun

Malang


34/80

Area 3 Kalimantan

10.10.40.1/30

10.10.40.2/30

Banjarmasin

Banjarmasin

PRKALBJM01

10.0.0.12/32

PEKALBJM01

10.0.0.13/32

10.10.40.5/30

10.10.40.6/30


35/80

PRJKTKPI01

Loopback0 10.0.0.1/32

Fa1/0 To PRJKTKPI02 Fa1/0 10.10.10.1/30 PRJKTKPI02 Fa1/0 10.10.10.2/30

Fa1/1 To PRKALBJM01 Fa1/3 10.10.10.14/30 PRKALBJM01 Fa1/3 10.10.10.13/30

Fa1/2 To PEJKTKPI01 Fa1/1 10.10.20.1/30 PEJKTKPI01 Fa1/1 10.10.20.2/30

Fa1/3 To PEBTNTGR01 Fa1/0 10.10.20.5/30 PEBTNTGR01 Fa1/0 10.10.20.6/30

PRJKTKPI02 Loopback0 10.0.0.2/32


Fa1/1 To PRJTMSBY01 Fa1/3 10.10.10.5/30 PRJTMSBY01 Fa1/3 10.10.10.6/30


Fa1/3 To PEJBRBKS01 Fa1/0 10.10.20.18/30 PEJBRBKS01 Fa1/0 10.10.20.17/30

PEJKTKPI01

Loopback0 10.0.0.3/32



PEJKTKPI02

Loopback0 10.0.0.4/32




36/80

PEBTNTGR01

Loopback0 10.0.0.5/32


Fa1/1 To PEJBRBGR01 Fa1/1 10.10.20.9/30 PEJBRBGR01 Fa1/1 10.10.20.10/30

PEJBRBKS01

Loopback0 10.0.0.6/32


Fa1/1 To PEJBRBGR01 Fa1/0 10.10.20.14/30 PEJBRBGR01 Fa1/0 10.10.20.13/30

PEJBRBGR01

Loopback0 10.0.0.7/32

Fa1/0 To PEJBRBKS01 Fa1/1 10.10.20.13/30 PEJBRBKS01 Fa1/1 10.10.20.14/30

Fa1/1 To PEBTNTGR01 Fa1/1 10.10.20.10/30 PEBTNTGR01 Fa1/1 10.10.20.9/30


37/80

Surabaya

PRJTMSBY01

Loopback0 10.0.0.8/32



Fa1/2 To PEJTMSBY01 Fa1/0 10.10.30.1/30 PEJTMSBY01 Fa1/0 10.10.30.2/30

Fa1/3 To PEJTMMDN01 Fa1/0 10.10.30.14/30 PEJTMMDN01 Fa1/0 10.10.30.13/30

PEJTMSBY01

Loopback0 10.0.0.9/32Fa1/0 To PRJTMSBY01 Fa1/2 10.10.30.2/30 PRJTMSBY01 Fa1/2 10.10.30.1/30

Fa1/1 To PEJTMMLG01 Fa1/0 10.10.30.5/30 PEJTMMLG01 Fa1/0 10.10.30.6/30

Malang

PEJTMMLG01 Loopback0 10.0.0.10/32

Fa1/0 To PEJTMSBY01 Fa1/1 10.10.30.6/30 PEJTMSBY01 Fa1/1 10.10.30.5/30

Fa1/1 To PEJTMMDN01 Fa1/1 10.10.30.9/30 PEJTMMDN01 Fa1/1 10.10.30.10/30

Madiun

PEJTMMDN01

Loopback0 10.0.0.11/32


Fa1/1 To PEJTMMLG01 Fa1/1 10.10.30.10/30 PEJTMMLG01 Fa1/1 10.10.30.19/30


38/80

Banjarmasin

PRKALBJM01

Loopback0 10.0.0.12/32



Fa1/2 To PEKALBJM01 Fa1/0 10.10.40.1/30 PEKALBJM01 Fa1/0 10.10.40.2/30

Fa1/3 To PEKALBJM01 Fa1/1 10.10.40.5/30 PEKALBJM01 Fa1/1 10.10.40.6/30

PEKALBJM01 Loopback0 10.0.0.13/32




39/80

For implementation, we will use GNS3 tosimulate Cisco MPLS Router. And then we candeploy from the Simulator to Real Devices.

Step by step GNS3 Installation: Download GNS3 windows version atwww.gns3.net, choose all in one package.

Install GNS3

Attach IOS in GNS3, from menu - edit IOSimages & hypervisor. *we will use Cisco Router 2691 version
http://www.gns3.net/http://www.gns3.net/http://www.gns3.net/


40/80

Point browser to : www.gns3.net
http://www.gns3.net/http://www.gns3.net/


41/80

Install GNS3, use default parameter and followthe installshield wizard.


42/80

There are 2 steps that needs to be donebefore you can use GNS3 :

1. Configure and test dynamips, emulationsoftware that will run cisco IOS

2. Add IOS to the GNS3 directory


43/80

Usually if we usethe all-in-onepackage, there isno need toconfigure

dynamips, butjust in case if weinstall thestandalonepackage, then we

can setup frommenu edit -preferences


44/80

Second step is add IOS images to GNS3, can

be accessed from Menu Edit IOS imagesand hypervisors.

Click image file, and then point it to your IOSimages, set the platform, model, and RAM.


45/80

One of the problem when using GNS3 is, ourPC/Laptop will be forced to run many routersat a time. In fact, our PC/Laptop doesnt have

resources to provide the router feature andspecification. But in this case, GNS3 hasprovide idle-pc feature that can barely reduceprocessor load when running router

simulation..


46/80

After you create GNS3 topology based ondesign, try to run one of the Router, by usingright click, and then click Start.


47/80

After the router is running, the routerinterface color will changed to green. The nextstep, right click, choose Idle PC.


48/80

And then GNS3 will calculate the best idle-pcthat fits for you. After calculation finish,choose one of the dropdown list. Choose thebest value, marked by star sign (*), if no star

sign exist, try one by one until you find goodone. And the task manager processes will beso much reduced.


49/80

After you finish setup idle-pc, re-checkprocessor utilization by opening the task-manager.

Before and After


50/80


51/80

VPCS is virtual PC simulator that emulates pc inthe GNS3, with VPCS we can save lot of resourcesthan using router/vm-ware based virtual pc.

With VPCS, we can do standard troubleshootinglike ping, and traceroute.

VPCS can be downloaded at :http://sourceforge.net/projects/vpcs/

Simple VPCS tutorial can be found at :http://rednectar.net/gns3-workbench/vpcs-

tutorial/
http://sourceforge.net/projects/vpcs/http://sourceforge.net/projects/vpcs/http://rednectar.net/gns3-workbench/vpcs-tutorial/http://rednectar.net/gns3-workbench/vpcs-tutorial/http://rednectar.net/gns3-workbench/vpcs-tutorial/http://rednectar.net/gns3-workbench/vpcs-tutorial/http://rednectar.net/gns3-workbench/vpcs-tutorial/http://rednectar.net/gns3-workbench/vpcs-tutorial/http://rednectar.net/gns3-workbench/vpcs-tutorial/http://rednectar.net/gns3-workbench/vpcs-tutorial/http://sourceforge.net/projects/vpcs/


52/80

After you download VPCS, put it on thed:\vpcs folder to make it easy to access thefile.


53/80

To connect VPCS to GNS3, you need to createnew symbol through menu-edit-SymbolManager


54/80

On the left pane, click computer, and thenclick right arrow, on the right top field, fill PCon the name, and choose Cloud for the type.Click Apply and OK.

12

3

4


55/80

Drag the new PC icon to the topology, right

click, and choose configure


56/80

On the NIO UDP tab, fill the local port and

remote port, leave the remote host to default127.0.0.1, and then click add.


57/80

Each NIO UDP local port/remote port representthe VPCS number.

VPCS can support 9 virtual PCs to accomodateyour needs

Please note below numbering :

30000 -> vpcs number 1 30001 -> vpcs number 2 30002 -> vpcs number 3 --- 30009 -> vpcs number 9


58/80


59/80

You can open command prompt, point to the

vpcs folder, and run vpcs program. Becausewe use nio udp 30000, we should press 1(one) in vpcs to enter virtual pc number 1

Press ? to see all available commands.


60/80

Its time to configure our routers, by right clickon the router, click console.


61/80

Type enable to enter privileged mode, andthen configure terminal to enter globalconfiguration mode.

Every router has different configuration, and

dont forget to setup the loopback IP Address


62/80

PRJKTKPI01:

hostname PRJKTKPI01

interface Loopback0ip address 10.0.0.1 255.255.255.255

!

interface FastEthernet0/0

description to PRJKTKPI02 f0/0

ip address 10.10.10.1 255.255.255.252

speed 100

full-duplex

!


description to PRKALBJM01 f0/1ip address 10.10.10.14 255.255.255.252

speed 100

full-duplex

!


description to PEJKTKPI01 f0/1

no switchport

ip address 10.10.20.1 255.255.255.252

duplex full

speed 100

!interface FastEthernet1/1

description to PEBTNTGR01 f0/0

no switchport

ip address 10.10.20.5 255.255.255.252

duplex full

speed 100

!

PRJKTKPI02:

hostname PRJKTKPI02


!



ip address 10.10.10.2 255.255.255.252

speed 100

full-duplex

!


description to PRJTMSBY01 f0/1ip address 10.10.10.5 255.255.255.252

speed 100

full-duplex

!



no switchport

ip address 10.10.20.22 255.255.255.252

duplex full

speed 100

!interface FastEthernet1/1

description PEJBRBKS01 f0/0

no switchport

ip address 10.10.20.18 255.255.255.252

duplex full

speed 100

!

PEJKTKPI01:

hostname PEJKTKPI01


!



ip address 10.10.20.25 255.255.255.252

speed 100

full-duplex

!


description to PRJKTKPI01 f1/0ip address 10.10.20.2 255.255.255.252

speed 100

full-duplex

PEJKTKPI02:

hostname PEJKTKPI02

interface Loopback0

ip address 10.0.0.4 255.255.255.255

!


description PEJKTKPI01 f0/0ip address 10.10.20.26 255.255.255.252

speed 100

full-duplex

!


description PRJKTKPI02 f1/0

ip address 10.10.20.21 255.255.255.252

speed 100

full-duplex


63/80

PEBTNTGR01:

hostname PEBTNTGR01

interface Loopback0

ip address 10.0.0.5 255.255.255.255

!



ip address 10.10.20.6 255.255.255.252

speed 100

full-duplex!


description to PEJBRBGR01 f0/1

ip address 10.10.20.9 255.255.255.252

speed 100

full-duplex

!

PEJBRBGR01:

hostname PEJBRBGR01

interface Loopback0

ip address 10.0.0.7 255.255.255.255

!


description to PEJBRBKS01 f0/1

ip address 10.10.20.13 255.255.255.252

speed 100

full-duplex!


description to PEBTNTGR01 f0/1

ip address 10.10.20.10 255.255.255.252

speed 100

full-duplex

!

PEJBRBKS01:

hostname PEJBRBKS01

interface Loopback0

ip address 10.0.0.6 255.255.255.255

!



ip address 10.10.20.17 255.255.255.252

speed 100

full-duplex!


description to PEJBRBGR01 f0/0

ip address 10.10.20.14 255.255.255.252

speed 100

full-duplex

!


64/80

PRJTMSBY01:hostname PRJTMSBY01

interface Loopback0

ip address 10.0.0.8 255.255.255.255

!


description to PRKALBJM01 f0/0

ip address 10.10.10.9 255.255.255.252

speed 100

full-duplex

!



ip address 10.10.10.6 255.255.255.252

speed 100

full-duplex

!


description to PEJTMSBY01 f0/0

no switchport

ip address 10.10.30.1 255.255.255.252

duplex fullspeed 100

!


description to PEJTMMDN01 f0/0

no switchport

ip address 10.10.30.14 255.255.255.252

duplex full

speed 100

!

PEJTMSBY01:hostname PEJTMSBY01

interface Loopback0

ip address 10.0.0.9 255.255.255.255

!


description to PRJTMSBY01 f1/0

ip address 10.10.30.2 255.255.255.252

speed 100

full-duplex

!


description to PEJTMMLG01 f0/0

ip address 10.10.30.5 255.255.255.252

speed 100

full-duplex

!


65/80

PEJTMMLG01:

hostname PEJTMMLG01interface Loopback0

ip address 10.0.0.10 255.255.255.255

!


description to PEJTMSBY01 f0/1

ip address 10.10.30.6 255.255.255.252

speed 100

full-duplex

!

interface FastEthernet0/1description to PEJTMMDN01 f0/1

ip address 10.10.30.9 255.255.255.252

speed 100

full-duplex

PEJTMMDN01:

hostname PEJTMMDN01interface Loopback0

ip address 10.0.0.11 255.255.255.255

!



ip address 10.10.30.13 255.255.255.252

speed 100

full-duplex

!

interface FastEthernet0/1description to PEJTMMLG01 f0/1

ip address 10.10.30.10 255.255.255.252

speed 100

full-duplex

!


66/80

PRKALBJM01:

hostname PRKALBJM01

interface Loopback0

ip address 10.0.0.12 255.255.255.255

!



ip address 10.10.10.10 255.255.255.252

speed 100

full-duplex

!

interface FastEthernet0/1description to PRJKTKPI01 f0/1

ip address 10.10.10.13 255.255.255.252

speed 100

full-duplex

!


description to PEKALBJM01 f0/0

no switchport

ip address 10.10.40.1 255.255.255.252

duplex full

speed 100!


description to PEKALBJM01 f0/1

no switchport

ip address 10.10.40.5 255.255.255.252

duplex full

speed 100

PEKALBJM01:

hostname PEKALBJM01

interface Loopback0

ip address 10.0.0.13 255.255.255.255

!


description to PRKALBJM01 f1/0

ip address 10.10.40.2 255.255.255.252

speed 100

full-duplex

!

interface FastEthernet0/1description to PRKALBJM01 f1/1

ip address 10.10.40.6 255.255.255.252

speed 100

full-duplex


67/80

OK, after finishing interface configurationsetup. Dont forget to save it by typing: copyrunning-config startup-config. And then doverification on each router, following below

procedure. This verification step is a MUST,otherwise the next step will be failed. Such asOSPF, MPLS, and MPLS VPN.


68/80

Configuration verification : from privilegedmode, type show run check within interface,make sure configuration were enteredcorrectly.


69/80

Interface verification: from privileged mode,type show ip interface brief, or showinterface, make sure we already setup the IPAddress, and UP, whether by status or

protocol.


70/80

Connectivity verification, do ping to directlyconnected neighbor. And make sure all weregiving reply.


71/80

IP routing verification, final step, make sureloopback IP, and neighbor IP were shown inrouting table. The C sign indicate directconnection to neighbor interface and loopback

interface.


72/80

Format ospf routing can be described below: Router>enable Router#configure terminal Router(config)#router ospf x x is the ospf process number Router(config-router)#network A.B.C.D W.X.Y.Z area y

ABCD= network address, WXYZ= wildcard mask,y = area Router(config-router)#

Insert all network interfaces IP Address that will beprocessed in OSPF process, including the Loopback IPAddress.


73/80

PRJKTKPI01:router ospf 10

log-adjacency-changes

network 10.0.0.1 0.0.0.0 area 0

network 10.10.10.0 0.0.0.3 area 0

network 10.10.10.12 0.0.0.3 area 0

network 10.10.20.0 0.0.0.3 area 1

network 10.10.20.4 0.0.0.3 area 1

!

PRJKTKPI02:

router ospf 10

log-adjacency-changesnetwork 10.0.0.2 0.0.0.0 area 0

network 10.10.10.0 0.0.0.3 area 0

network 10.10.10.4 0.0.0.3 area 0

network 10.10.20.20 0.0.0.3 area 1

network 10.10.20.16 0.0.0.3 area 1

!

PEJKTKPI01:

router ospf 10


network 10.0.0.3 0.0.0.0 area 1network 10.10.20.0 0.0.0.3 area 1

network 10.10.20.24 0.0.0.3 area 1

!

PEJKTKPI02:router ospf 10


network 10.0.0.4 0.0.0.0 area 1

network 10.10.20.20 0.0.0.3 area 1

network 10.10.20.24 0.0.0.3 area 1

!

PEBTNTGR01:

router ospf 10


network 10.0.0.5 0.0.0.0 area 1


!

PEJBRBGR01:

router ospf 10


network 10.0.0.7 0.0.0.0 area 1

network 10.10.20.8 0.0.0.3 area 1

network 10.10.20.12 0.0.0.3 area 1

!

PEJBRBKS01:router ospf 10


network 10.0.0.6 0.0.0.0 area 1

network 10.10.20.12 0.0.0.3 area 1

network 10.10.20.16 0.0.0.3 area 1

!

PRJTMSBY01:

router ospf 10


network 10.0.0.8 0.0.0.0 area 0


network 10.10.30.0 0.0.0.3 area 2

network 10.10.30.12 0.0.0.3 area 2

!

PEJTMSBY01:

router ospf 10


network 10.0.0.9 0.0.0.0 area 2

network 10.10.30.0 0.0.0.3 area 2

network 10.10.30.4 0.0.0.3 area 2!


74/80

PEJTMMLG01:

router ospf 10


network 10.0.0.10 0.0.0.0 area 2

network 10.10.30.4 0.0.0.3 area 2

network 10.10.30.8 0.0.0.3 area 2

!

PEJTMMDN01:

router ospf 10

log-adjacency-changesnetwork 10.0.0.11 0.0.0.0 area 2

network 10.10.30.8 0.0.0.3 area 2

network 10.10.30.12 0.0.0.3 area 2

!

PRKALBJM01:

router ospf 10


network 10.0.0.12 0.0.0.0 area 0

network 10.10.10.8 0.0.0.3 area 0

network 10.10.10.12 0.0.0.3 area 0

network 10.10.40.0 0.0.0.3 area 3

network 10.10.40.4 0.0.0.3 area 3

!

PEKALBJM01:router ospf 10


network 10.0.0.13 0.0.0.0 area 3

network 10.10.40.0 0.0.0.3 area 3

network 10.10.40.4 0.0.0.3 area 3

!


75/80

Dont forget to save the configuration : copyrunning-config startup-config. Also dontforget to do verification on each router. Thisverification step is very important.


76/80

First verification is neighbor establishment,this step is used to check whether the ospfsession between neighbor router alreadyestablished or not. Can be done by typing

show ip ospf neighbor. Make sure all state isFULL


77/80

The second step is show ip ospf interface, toverify interface status towards neighbor, fromhere we can check the detail status of ospfprocess, hello timer, dead timer, wait timer,

process id, and router id from ospf routingprotocol.


78/80

Next type show ip ospf database, from herewe can see the link id detail, advertisedrouters, sequence, detail of each area,summary, and so on.


79/80

Last one,

command show iproute in bogorrouter(PEJBRBGR01) wereused to see path

that available fromospf process.


80/80

Next, Chapter 2.

MPLS VPN Services

mpls deployment chapter 1 - basic1

Documents