Curso MPLS

Basic MPLS
2202 1358_06_2000_c2 2000, Cisco Cisco Systems, Inc. Inc. CQFE rev17 Russ Davis 1999, Systems,
Agenda
Multi Protocol Label Switching
MPLS Concepts LSRs and labels Label assignment and distribution Label Switch Paths ATM LSRs Loop detection/prevention LDP concepts Configurations
CQFE rev14 Russ Davis
1999, Cisco Systems, Inc.
www.Cisco.com
Distributed Fast Switching

RSP
Available with intelligent IPs
Distributed cache
IP VIP
First Packet Subsequent Packets
www.Cisco.com
Cisco Express Forwarding
Main components
Forwarding Information Base (FIB)
Adjacency table
No process switching of packets
www.Cisco.com
Forwarding Information Base
Adjacency Database
www.Cisco.com
FIB Table
Shadow copy of the IP routing table Classless Routing protocol independent One for each route in IP routing table Each entry has one or more path Each path has nexthop IP address and nexthop interface Each path points to an adjacency
www.Cisco.com
Adjacency Table
Maintains IP address to Mac-rewrite mapping
Populated by ARP table, Frame Relay map table and ATM map table, etc. Mac-rewrite of the nexthop is all thats required to switch packet
www.Cisco.com

Routing Table ARP/Map Table
FIB Table
Adjacency Table
www.Cisco.com
8
CEF Operation
FIB entry created when routes are added to IP routing table
If connected, new FIB entry points to the corresponding adjacency

Ready to switch packets
Non-connected prefix requires more work

www.Cisco.com
MPLS Concepts
Separation of routing and forwarding

Forwarding is done independently
Integrates the control of IP routing with simplicity of layer 2 switching

Helps in deployment of complicated routing services
www.Cisco.com
10
MPLS Concepts
Separation of control and forwarding

Control is build by standard routing protocols (OSPF,ISIS,BGP)
Forwarding is build by LDP independent of routing protocols
www.Cisco.com
11
MPLS Concepts
Forwarding Equivalence Class(FEC)

Group of IP packets forwarded with same treatment over the same path irrespective of the final destination Packet is assigned to FEC based on its network layer destination address
www.Cisco.com
12
MPLS Concepts
Label
Label is a short fixed length, locally significant used to identify a FEC
Label is assigned on the network layer address but it is not encoding of the network layer address Label has local significance between LSRs
www.Cisco.com
13
MPLS Concepts
Labeled Packet
Packet into which a label has been encoded
Label could reside inside network or data link layer (ATM)
www.Cisco.com
14
MPLS Concepts
Upstream
Where the packet source is
Downstream
Towards the destination
www.Cisco.com
15
Upstream and Downstream LSRs

171.68.10/24 171.68.40/24 Rtr-A Rtr-B RtrC
Rtr-C is the downstream neighbour of RtrB for destination 171.68.10/24

Rtr-B is the downstream neighbour of RtrA for destination 171.68.10/24 LSRs know their downstream neighbours through the IP routing protocol
Next-hop address is the downstream neighbour
www.Cisco.com
16
MPLS Concepts
Label Assignment
Assignment is done by the LSR down stream
Downstream LSR informs the upstream LSR of the binding
www.Cisco.com
17
MPLS Concepts
Label Distribution Protocols (LDP)

Set of procedures by which one LSR informs other about the label for a certain FEC LSR that distribute label information between each other are known as Label Distribution Peers
www.Cisco.com
18
MPLS Concepts
MPLS architecture does not assume a single protocol

Existing protocols have been extended (MP-BGP), (MPLS-RSVP) New protocols have also been defined (MPLS-LDP), (MPLS-CR-LDP)
www.Cisco.com
19
MPLS Concepts
MPLS allows:
Packet classification only where the packet enters the network The packet classification is encoded as a label In the core, packets are forwarded without having to re-classify them No further packet analysis Label swapping
www.Cisco.com
20
MPLS concepts
Packet forwarding: FEC and Next-Hop
MPLS make use of FECs

MPLS nodes assign a label to each FEC Packet classification (into a FEC) is done where the packet enters the core No sub-sequent packet classification in the MPLS network
www.Cisco.com
22
MPLS concepts
Address Prefix and mask
Next-Hop
Interface Serial1
171.68.10/24
...
171.68.9.1
...
...
0
IP packet D=171.68.10.23 IP packet D=171.68.10.12
171.68.10/24
Rtr-A
Router-A forwards packets with different destination addresses using the same route, same next-hop and same interface
www.Cisco.com
23
MPLS concepts
Packets are classified into FECs
For each FEC the next-hop is calculated

In IP routing each hop:
re-classify the packet into one FEC recalculate the next-hop of the FEC
www.Cisco.com
24
MPLS concepts
In I/F In Lab Address Prefix Out I/F Out Lab In I/F In Lab Address Prefix Out I/F Out Lab
4 ...
x 171.68.10 3 ...
Next-Hop ... ...
5 ...
5 171.68.10 1
...
...
Next-Hop ... ...
...
3
4 Rtr-B
Label = 5 IP packet D=171.68.10.12
0 Rtr-A
1
171.68.10/24
IP packet D=171.68.10.12 Router-B classify the IP packet into a FEC and assign the corresponding label.
Router-A forwards labelled packets by looking at the label value against the label table. No packet classification into FEC is done.
www.Cisco.com
25
MPLS concepts
MPLS forwarding
MPLS forwarding is performed in the same way in ATM switches and routers. However,
ATM queuing is given by the label value (VCI) Router queuing may be given by EXP bits in label header
ATM switches do not have capabilities to analyse layer 3 headers Labels may be distributed by different protocols
LDP, RSVP, PIM, BGP, ...
www.Cisco.com
26
MPLS concepts
Label Switch Routers
LSR: Label Switch Router Can be an ATM switch or a router Edge-LSRs do label imposition and label removal
Label imposition where the packet enters the MPLS network
Label removal where the packet leaves the MPLS network
All LSRs use existing IP routing protocols to exchange routing information All LSRs use a label distribution protocol
Not necessarily the same in all LSRs www.Cisco.com
27
MPLS concepts ATM-LSR

In order to exchange labels, ATM-LSRs need to run an IP routing protocol
ATM-LSRs will act as routers in terms of IP control plane ATM-LSRs will act as ATM switches in terms of data plane ATM-LSRs will NOT route packets based on routing table Packet forwarding is based on label information Control VC is used to exchange labels
ATM switches use input port,VPI,VCI values and map them to output port,VPI,VCI values
Label is encoded in same fields
VPI/VCI field used to carry label information Existing software can work for label swapping
www.Cisco.com
28
MPLS concepts
Labels
Label format and length depends on encapsulation
Has to be negotiated between peers over ATM interfaces

More than one label is allowed
Label stack: ordered set of labels
MPLS LSRs always forward packets based on the value of the label at the top of the stack
www.Cisco.com
29
MPLS concepts
Labels
ATM Cell Header
GFC VPI VCI PTI CLP HEC DATA
Label
www.Cisco.com
30
Upstream and Downstream LSRs
LSRs assign a label to each FEC Label distribution may be upstream or downstream driven Most implementations use downstream with two variants
Unsolicited Downstream
Downstream on demand no need for upstream allocation
www.Cisco.com
32
Unsolicited Downstream distribution

Use label 5 for destination 171.68.10/24 171.68.40/24 Use label 7 for destination 171.68.10/24 171.68.10/24
Rtr-A
In I/F In Lab Address Prefix Out Out I/F Lab In I/F
Rtr-B
In Lab Address Prefix Out Out I/F Lab
RtrC
In I/F In Lab Address Prefix Out Out I/F Lab
171.68.10
... ...
Next-Hop ... ...
5 ...
5 171.68.10
... ...
Next-Hop ... ...
7 ...
7 171.68.10
... ...
IGP derived routes
Next-Hop ... ...
...
LSRs assign a label to each FEC LSRs distribute labels to the upstream neighbours
www.Cisco.com
33
Downstream on demand distribution

Use label 5 for destination 171.68.10/24 Use label 7 for destination 171.68.10/24
171.68.10/24
171.68.40/24 Rtr-A
Rtr-B
RtrC
Request label for destination 171.68.10/24
Request label for destination 171.68.10/24
LSRs assign a label to each FEC Upstream LSRs request labels to downstream neighbours Downstream LSRs distribute labels upon request
www.Cisco.com
34
Downstream on demand and VC-Merge
VC-Merge allows correct packet reassembling

Sequencing of cells by buffering Receiving (downstream) ATM-LSR can securely re-assemble cells into packets
Even cells of different packets use same VPI/VCI value
Save label space on ATM-LSRs

www.Cisco.com
35
Downstream on Demand and ATM
In In Address I/F Lab Prefix 1 2 ... 5 IP Packet

AT M cell
Out Out I/F Lab 0 0 ... 3 3 ...
5 8 ...
171.68 171.68 ...
Downstream LSR do not know how to reassemble correctly cells into packets. VPI/VCI values are identical for all cells
5
AT M cell
3 IP Packet 8
AT M cell
3
AT M cell
3
AT M cell
3
AT M cell
3
AT M cell
171.68
8
AT M cell
8
AT M cell
AT M cell
www.Cisco.com
36
Downstream on Demand and ATM

AT M cell
Out Out I/F Lab 0 0 ... 3 4 ...
5 8 ...
171.68 171.68 ...
ATM-LSR requested additional label for same FEC in order to distinguish between incoming interfaces (Downstream on Demand)
5
AT M cell
4 IP Packet 8
AT M cell
3
AT M cell
4
AT M cell
3
AT M cell
4
AT M cell
171.68
8
AT M cell
8
AT M cell
AT M cell
www.Cisco.com
37
ATM-LSRs and VC-Merge

AT M cell
Out Out I/F Lab 0 0 ... 3 3 ...
5 8 ...
171.68 171.68 ...
ATM-LSR transmitted cells in sequence in order for the downstream LSR to re-assembling correctly the cells into packets
5
AT M cell
3 IP Packet 8
AT M cell
3
AT M cell
3
AT M cell
3
AT M cell
3
AT M cell
171.68
8
AT M cell
8
AT M cell
AT M cell
www.Cisco.com
38
Label retention modes

Liberal retention mode
LSR retains labels from all neighbours
Improve convergence time, when next-hop is again available after IP convergence
Require more memory and label space

May be a problem in ATM-LSRs since a label is a VC
Conservative retention mode (*)

LSR retains labels only from next-hops neighbours LSR discards all labels for FECs without next-hop
Free memory and label space

www.Cisco.com
39
Label Distribution Ordered vs. Independent

Ordered LSP control
LSR only binds and advertise a label for a particular FEC if: it is the egress LSR for that FEC or it has already received a label binding from its next-hop
Independent LSP control

LSR binds a label to a FEC independently from the label it has to receive from its next-hop
Similar to link-state IP routing (flooding): each router build routing table independently
An LSR may label forward packet to a next-hop that does not have yet label information for that FEC
www.Cisco.com
40
Label Distribution Protocols

Several protocols for label exchange
LDP Maps unicast IP destinations into labels RSVP, CR-LDP Used for traffic engineering and resource reservation PIM For multicast states label mapping BGP External labels (VPN)
www.Cisco.com
41
Label retention modes

Liberal retention mode
LSR retains labels from all neighbours
Improve convergence time, when next-hop is again available after IP convergence
Require more memory and label space

May be a problem in ATM-LSRs since a label is a VC
Conservative retention mode

LSR retains labels only from next-hops neighbours LSR discards all labels for FECs without next-hop
Free memory and label space

www.Cisco.com
42
Label Distribution Ordered vs. Independent

Ordered LSP control
LSR only binds and advertise a label for a particular FEC if: it is the egress LSR for that FEC or it has already received a label binding from its next-hop
Independent LSP control

LSR binds a label to a FEC independently from the label it has to receive from its next-hop
Similar to link-state IP routing (flooding): each router build routing table independently
An LSR may label forward packet to a next-hop that does not have yet label information for that FEC
www.Cisco.com
43
The Label Stack

Each packet/cell may have more than one label
Label stack is the ordered list of labels ATM cells?
Label format is negotiated between peers VPI/VCI fields may contain different labels
Label stack is copied in the payload of the FIRST cell of the packet
LSR nodes label switch packets based ONLY on the label at the top of the stack
www.Cisco.com
44
The Label Stack

In I/F In Lab Address Prefix Out Out I/F Lab
5 171.68.10
... ...
Next-Hop ... ...
...
171.68.10/24
Label = 5
Rtr-A
Label = 7
Label = 21
IP packet D=171.68.10.12
Rtr-A forwards the labelled packet based on the label at the top of the label stack
www.Cisco.com
45
Label space
LSRs must be able to distinguish between labelled packets
A label corresponds to a particular FEC
LSR can distribute the same label/FEC mapping to different neighbours
Same label can be assigned to different FECs if and only if the LSR can distinguish the interface from which the packet will arrive
i.e: the LSR can identify who us the upstream neighbour who insert the label
www.Cisco.com
46
Label space
Per interface label space
Label are unique in a per interface base
Used over ATM interfaces

Label = VCs With interface label space an LSR will accept labelled packets form upstream neighbours only if the labels have been previously advertised to those neighbours. No label spoofing Useful when interconnecting MPLS domains
www.Cisco.com
47
Label space
Label = 5 IP packet D=171.68.10.15 In I/F In Lab Address Prefix Out Out I/F Lab
0 1
5 171.68.10
7 8
Next-Hop 2 5 171.68.10
1
0 Rtr-A
171.68.10/24
Same label for FEC 171.168.10 is advertised to different upstream neighbours

www.Cisco.com
48
Label space
In I/F 0 1 4 In Lab 5 5 5 Address Prefix 171.68.10 Out I/F 2 Out Lab 7 8 9
Next-Hop2 171.68.10
171.68.40 3
1 0 Label = 5 IP packet D=171.68.10.12 4 2
Label = 7 IP packet D=171.68.10. 12
171.68.10/24
Label = 9 Label = 5 IP packet D=171.68.40.33 IP packet D=171.68.40.33 171.68.40/24
Same label is assigned to different FECs if LSR is able to distinguish the upstream neighbour who sent the packet
www.Cisco.com
49
Label space
In I/F 0 1 ... In Lab 5 6 ... Address Prefix 171.68.10 Out I/F 2 Out Lab 7 8 ...
Next-Hop2 171.68.10
... ...
1 0 2 Label = 8 IP packet D=171.68.10.15 171.68.10/24
Label = 6
IP packet D=171.68.10.12
Packet is using a label NOT previously advertised by the downstream neighbour
Label not being previously advertised to that neighbour. The packet is dropped
www.Cisco.com
50
Label Switch Path (LSP)

Each labelled packet
enters the MPLS network in the ingress LSR
exits the MPLS network in the egress LSR
LSP is the sequence of LSRs through which the labelled packets have to go through in order to reach the egress LSR
www.Cisco.com
51
Label Switch Path (LSP)
IngressLSR Egress-LSR
IGP domain with a label distribution protocol
LSR-ingress to LSR-egress path is the same for packets of the same FEC
LSPs are unidirectional
Return traffic takes another LSP
www.Cisco.com
52
Penultimate Hop Popping

The label at the top of the stack is removed (popped) by the upstream neighbor of the egress LSR The egress LSR requests the popping through the label distribution protocol
Egress LSR advertises implicit-null label
The egress LSR will not have to do a lookup and remove itself the label
One lookup is saved in the egress LSR
www.Cisco.com
53
Penultimate Hop Popping

In In Address I/F Lab Prefix 0 171.68/16 ... ... Out Out I/F Lab 1 4 ... Summary route for 171.68/16 1 0 1 In I/F 0 ... In Lab 4 ... Address Prefix 171.68/16 Out Out I/F Lab 2 pop ... Summary route for 171.68/16 Address Next-Hop Interface Prefix and mask 171.68.10/24 171.68.9.1
Serial1
Serial2 Null
Next-Hop ... ...
Next-Hop ... ...
171.68.44/24 171.68.12.1 171.68/16 ...
Use label 4 for FEC 171.68/16
Use label implicit-null for FEC 171.68/16 171.68.44/24
Summary route is propagate through the IGP and label is assigned by each LSR
Egress LSR summarises more specific routes and advertises a label for the new FEC
171.68.10/24
Egress LSR needs to do an IP lookup for finding more specific route Egress LSR need NOT to receive a labelled packet
labelled will have to be popped anyway www.Cisco.com

54
Aggregation and layer 3 summarisation
The LSR which does summarisation will be the end node LSR of all LSPs related to the summary address
Aggregation point
The LSR will have to examine the second level label of each packet
If no second label, the LSR has to examine the IP header No summarisation in ATM-LSRs
www.Cisco.com
55
Aggregation and layer 3 summarisation

In I/F In In Address I/F Lab Prefix 0 171.68/16 ... ... Out Out I/F Lab 1 4 ... Summary route for 171.68/16 1 0 1 0 In Lab Address Prefix Out Out I/F Lab Null 1 7 Pop 171.68/16 171.68.10/24 Address Next-Hop Interface Prefix and mask 171.68.10/24 171.68.9.1 Serial1
Next-Hop ... ...
171.68.44/24
8
Specific routes 171.68.10/24 171.68.44/24
171.68.44/24 171.68.33.3 Serial4
0
1
Use label implicit-null for FEC 171.68/16
Label mappings for 171.68.10/24 171.68.44/24
Area Border router summarises and advertises a single label for the summary route
Egress LSR advertises more specific routes label mappings
171.68.10/24
Aggregating LSR need to do an IP lookup for finding more specific route

!!!! Do not aggregate in ATM-LSRs !!!!
www.Cisco.com
56
Route Selection Hop by Hop Routing
At each hop the LSR selects the LSP where to forward the packet Similar to IP routing where each hop makes its own route selection
www.Cisco.com
57
Route Selection Explicit Routing

The ingress LSR has the knowledge of the complete path (LSP) for the FEC
The ingress LSR specifies all LSR nodes that are in the path The LSP can be set statically by configuration The LSP can be set dynamically using link-state topology information Traffic Engineering makes use of explicit routed LSPs
www.Cisco.com
58
Route Selection Explicit Routing

LSR-1 LSR-2 Use label 25 for LSR-5 LSR3 Ingress
Use label 39 for LSR-5
Need labels for LSP-1 going through LSR-1 LSR-2 LSR-4 LSR-5
LSR-6 Pop label for LSR-5
LSR-4
LSR-5
Egress
LSR-1 request an explicit LSP to LSR-5: LSR1, LSR-2, LSR-4, LSR-5 The request travels hop-by-hop and when it reaches the egress point labels are advertised back to the ingress LSR
www.Cisco.com
59
Route Selection Explicit Routing and label stack

LSR-1 LSR-2 Use label 25 for LSR-5 LSR3 Ingress
Use label 39 for LSR-5 Pop label for LSR-5 LSR-6
LSR-5 advertises mappings to LSR-1 as LSR-1 was an adjacent neighbor
Use label 9 for LSR-6 Use label 3 for LSR-6 LSR-4 LSR-5
Egress
LSR-1 and LSR-5 are non-adjacent peers for label exchange
www.Cisco.com
60
Route Selection Explicit Routing and label stack

LSR-1 LSR-2 LSR3
Label = Ingress 25 Label = 3

IP packet Label = 39 Label = 3 IP packet
LSR-5 --> 25 LSR-6 --> 3
LSR-6
Label = 3 LSR-4 IP packet LSR-5
Label = 9 IP packet Egress
39 <-- LSR-5 --> Pop 3 <-- LSR-6 --> 9
www.Cisco.com
61
ATM LSRs Label Encoding
Label information is carried in VPI/VCI field with different techniques to encode labels
www.Cisco.com
62
Loops and TTL In IP networks TTL is used to prevent packets to travel indefinitely in the network
MPLS may use same mechanism but not on all encapsulations
TTL is present in the label header for PPP and LAN headers
www.Cisco.com
63
Loops and TTL
When a packet enters into the MPLS network

The Ingress LSR does a copy of the layer 3 TTL into the Label TTL
Each hop decrements TTL

If TTL = 0 packet is discarded The Egress LSR does a copy of the label TTL into the layer 3 TTL when the packet leaves the MPLS network
www.Cisco.com
64
Loops and TTL

LSR-1 LSR-2 Use label 25 for LSR-6 Hops=4 Use label 39 for LSR-6 Hops=3 LSR-6 Use label 21 for LSR-6 Hops=2 LSR-4 LSR3
Ingress
LSR-5
Pop label for LSR-6 Hops=1
Egress
LSRs exchange label mappings with hop-count information

www.Cisco.com
65
Loops and Path Vector (LDP)
Each LSR inserts (append) its ID into label mappings messages LSR receiving an LDP message will check the ID list If its own ID is found the loop is detected
.
www.Cisco.com
66
Concepts LDP Messages Peers exchange LDP messages
Discovery messages
Used to discover and maintain the presence of new peers Hello packets (UDP) sent to all-routers-insubnet multicast address
Once neighbour is discovered, the LDP session is established over TCP

www.Cisco.com
67
Concepts LDP Messages
Session messages
Establish, maintain and terminate LDP sessions
Advertisement messages
Create, modify, delete label mappings
Notification messages
Error signalling
www.Cisco.com
68
Configuration
CEF should be running
Tag switching you need to configure it in interface mode

tag-switching ip mpls ip
www.Cisco.com
69
Configuration
To enable to type of label distribution protocol you want to run, this is done per interface basis
mpls label-protocol [ tdp ldp both]
www.Cisco.com
70
Configuring TTL
By default ip ttl is copied into mpls packet To disable you need the following command
no tag-switching ip propagate-ttl no mpls ip prapagate-ttl
TTL propagation if disabled has to be done on both ingress and egress LSR
www.Cisco.com
71

Curso MPLS

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Curso MPLS

Hochgeladen von

Copyright:

Verfügbare Formate

Basic MPLS

Distributed Fast Switching

Available with intelligent IPs

CQFE rev14 Russ Davis

1999, Cisco Systems, Inc.

Cisco Express Forwarding

No process switching of packets

CQFE rev14 Russ Davis

1999, Cisco Systems, Inc.

Cisco Express Forwarding

Forwarding Information Base

CQFE rev14 Russ Davis

1999, Cisco Systems, Inc.

1999, Cisco Systems, Inc.

Cisco Express Forwarding

FIB entry created when routes are added to IP routing table

If connected, new FIB entry points to the corresponding adjacency

Non-connected prefix requires more work

1999, Cisco Systems, Inc.

Separation of routing and forwarding

Integrates the control of IP routing with simplicity of layer 2 switching

CQFE rev14 Russ Davis

1999, Cisco Systems, Inc.

Separation of control and forwarding

CQFE rev14 Russ Davis

1999, Cisco Systems, Inc.

Forwarding Equivalence Class(FEC)

CQFE rev14 Russ Davis

1999, Cisco Systems, Inc.

CQFE rev14 Russ Davis

1999, Cisco Systems, Inc.

CQFE rev14 Russ Davis

1999, Cisco Systems, Inc.

CQFE rev14 Russ Davis

1999, Cisco Systems, Inc.

Upstream and Downstream LSRs

Rtr-C is the downstream neighbour of RtrB for destination 171.68.10/24

1999, Cisco Systems, Inc.

CQFE rev14 Russ Davis

1999, Cisco Systems, Inc.

Label Distribution Protocols (LDP)

CQFE rev14 Russ Davis

1999, Cisco Systems, Inc.

MPLS architecture does not assume a single protocol

CQFE rev14 Russ Davis

1999, Cisco Systems, Inc.

MPLS make use of FECs

CQFE rev14 Russ Davis

1999, Cisco Systems, Inc.

Address Prefix and mask

CQFE rev14 Russ Davis

1999, Cisco Systems, Inc.

Packets are classified into FECs

For each FEC the next-hop is calculated

Next-Hop ... ...

CQFE rev14 Russ Davis

1999, Cisco Systems, Inc.

Label removal where the packet leaves the MPLS network

Not necessarily the same in all LSRs www.Cisco.com

MPLS concepts ATM-LSR

Has to be negotiated between peers over ATM interfaces

CQFE rev14 Russ Davis

1999, Cisco Systems, Inc.