What is protocol used by MPLS?

TDP or LDP

MPLS works on which layer?

Between L2 & L3

Can we make PE R as a P?
To make PE R as P, i need to remove the BGP config & after that it will not participate with customer
nw.

How loop prevention work in MPLS?

As far as loop mitigation is concerned, MPLS labeled packets may carry a TTL field that operates just
like the IP TTL to enable packets caught in transient loops to be discarded.

what is the diff between P & PE R?

P R doesn't have customer NW routes where in PE R is having customer NW routes.
Another reason is P R doesn't require MP-iBGP but for PE IT IS MUST.

Enables the VPN routing and forwarding (VRF) routing table.

(config)#ip VRF Customer_A

Route distinguisher creates routing and forwarding tables for a VRF

(config-VRF)#RD 100:110

Creates list of import & export RT extended, communities for the specificed VRF.
(config-VRF)#route-targer import 100:1000

Associates a VRF instance with an interface or subinterface

#interface Loopback101
#ip vrf forwarding Customer_A

ip address 200.0.4.1 255.255.255.0

Loopback101 and 102 use the same IP address, 200.0.4.1.
This is allowed because they belong to two
different customers' VRFs.

Which IOS version support MPLS feature?

12.2(6h)

Which is lower end model R does support MPLS PE?

2600 series or higher end 2691, 3640

FIB function?
FIB stand for Forwarding Information Base and it contains information such as interface identifier and
information how to reach the next hop network prefix. basically, it is used to make IP destination
prefix based switching decision.
https://www.rogerperkin.co.uk/featured/route-distinguisher-vs-route-target/
https://www.cisco.com/c/en/us/support/docs/multiprotocol-label-switching-mpls/mpls/4649-mpls-faq-
4649.html

Route Distinguisher.
The route distinguisher has only one purpose, to make IPv4 prefixes globally unique. It is used by the
PE routers to identify which VPN a packet belongs to, e.g to enable a router to distinguish between
10.0.0.1/8 for Customer A and 10.0.0.1/8 for Customer B. The route distinguisher is made up of an 8
octet field prefixed to to the customer IPv4 address, the resulting 12 octect field make a unique
VPNv4 address. For more info on this please refer.

Route Target
which prefixes are exported and imported on the PE routers.
Since RD can't identify participation in more than one VPN, what is required to support complex MPLS
VPN?
Route Target
8 byte field which is a BGP extended Communities Attribute.
Now, if customer A decided to make a new network, 10.0.0.0/24, and Router 1 advertises this to
Router 4, how does Router 4 if it’s meant for VRF CUSTOMER_A or CUSTOMER_B? That’s where
route targets come in. In short, a route target is some extra information, added to an advertised
prefix, to tell the receiving router which VRF to put it in.

Is full control of routing between customer edge (CE) routers is required?

If you absolutely need full control of routing between your sites then IPsec and MPLS/L2TPv3-based
layer-2 VPNs are all possibilities. MPLS Layer-3 (RFC 2547bis/RFC 4364) VPNs are not an option if full
control of routing is important because service provider edge (PE) routers will be involved in your
routing, and you will therefore have some loss of control. This loss of control is often considered
insignificant when compared to the advantages of deploying MPLS layer-3 VPNs, but it’s worth noting.

Are additional managed services such as firewalled internet access/voice services required/desirable?
Service providers can offer a variety of managed services to their customers such as firewalled
Internet access and voice services. These managed services are most easily provided and most often
available via MPLS Layer-3 VPNs.

Do you need to transport multicast traffic over your VPN?

MPLS layer-3 and IPsec VPNs do not natively support multicast. If you need to transport multicast
traffic in an MPLS layer-3 VPN then you’ll need GRE tunnels or support for multicast VPNs (MVPNs). If
you need to transport multicast over an IPsec VPN then you’ll need to use technologies such as GRE
tunnels or Virtual Tunnel Interfaces (VTIs).
Next time, I’ll look at some of the main considerations when selecting a remote access VPN
technology.

Why know as MP-BGP?

It has ability to exchange info about multiple protocols such as IPV4, VPNv4, IPV6 & multicast.

Which App enables MPLS & exchange labels between PE?

LDP enabled MPLS. LDP is used to exchange labels between PE.

Label allocation done by which protocol?

BGP

What platforms and Cisco IOSes support MPLS?

The Cisco Series 2691, 3640, 3660, 3725, 3745, 6400-NRP-1, 6400-NRP-2SV, 6400-NSP.
3600,3700,6400

Basic cmd to enable MPLS on a R?

!--- Customer A commands.

ip vrf Customer_A

!--- Enables the VPN routing and forwarding (VRF) routing table. !--- This command can be used in global or
!--- router configuration mode.

rd 100:110

!--- Route distinguisher creates routing and forwarding !--- tables for a VRF.

route-target export 100:1000

!--- Creates lists of import and export route-target extended !--- communities for the specified VRF.

route-target import 100:1000

(config)#IP CEF
(config-if)#IP MPLS

How does the LSR know which is the top label, bottom label, and a middle
label of the label stack?
The label immediately after the Layer 2 header is the top label, and the
label with the S bit set to 1 is the bottom label. No application requires
LSR to read/identify the middle labels. However, a label will be a middle
label if it is not at the top of the stack and the S bit is set to 0.

What protocol and port numbers do LDP and TDP use to distribute labels
to LDP/TDP peers?
LDP uses TCP port 646, and TDP uses TCP port 711. These ports are
opened on the router interface only when mpls ip is configured on the
interface.
#1: VPN prefix doesn’t have any label in the LFIB on the local PE

Scenario 1 Solution
VPN prefix doesn’t have any label in the LFIB on the local PE,
though BGP now does?
Solution
“clear ip route vrf <vrf> <prefix>”
If the above doesn’t fix, then (soft) reset the
BGP session

#3: Remote PE (PE2) doesn’t get the VPNv4 prefix from PE1
Solution
Validate “route-target import” config on PE2. If not present, then
configure it; Check for import-map as well.

4: Remote PE (PE2) still doesn’t get the VPNv4 prefix from PE1.
Solution
#5: Remote PE2 STILL doesn’t get the VPNv4 prefix from PE1
How does MPLS perform failure recovery?
When a link goes down it is important to reroute all trunks that
were routed over this link. Since the path taken by a trunk is
determined by the LSR at the start of the MPLS path (head end),
rerouting has to be performed by the head end LSR. To perform
rerouting, the head end LSR could rely either on the information
provided by IGP or by RSVP/CR-LDP.