SRC Sample Course

IP Networks and Services Fundamentals

1 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

2 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

3 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

4 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

5 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

6 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

7 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

8 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

9 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

10 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

11 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

12 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

13 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

14 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

15 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

16 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course
The service provider can offer simple, transparent layer-2 and layer-3 VPN services to multiple customers over a single
network.

Diagram source: Nokia ION Learning Services course “Nuage Networks Virtualized Cloud Services (VCS) – Advanced Topics”,
Module 1, slide 12. See references [2].

IP Networks and Services Fundamentals

17 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

18 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course
Virtual Private Wire Service
Virtual Private Wire Service (VPWS) is a simple layer-2 service that emulates a single leased line or circuit between two
locations. The customer has no knowledge of the service provider network; the service acts as a simple point-to-point
connection between customer sites. The VPWS can emulate an Ethernet connection (Epipe), a frame relay connection
(Fpipe), an ATM connection (Apipe) or a TDM circuit (Cpipe). Layer-2 frames of customer data are encapsulated in MPLS
labels and tunneled across the service provider network.

Virtual Private LAN Service

Virtual Private LAN Service (VPLS) is a layer-2 multipoint service that can be used to interconnect more than two customer
locations. From the customer’s perspective, VPLS looks as though a simple layer-2 LAN switch exists between different
customer locations. The Ethernet frames of customer data are encapsulated in MPLS labels and tunneled across the
service provider network.

Virtual Private Routed Network

Virtual Private Routed Network (VPRN) is a layer-3 service that makes the service provider network appear as a simple IP
router that connects two or more customer locations. The VPRN allows the CE devices to exchange route information with
the VPRN as if it were an IP router. The IP packets containing customer data are encapsulated in MPLS labels and tunneled
across the service provider network.

Diagram source: Nokia ION Learning Services course “Nuage Networks 210 WBX”, Module 4, slide 5. See references [15].

VPN services are discussed in more detail in the Nokia ION Learning Services course “Nokia Services Architecture”. See
references [16].

IP Networks and Services Fundamentals

19 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course
The example above shows a generic VPN service. The same terminology applies to any type of VPN service.

In a distributed service, there is an IP network in between the routers that provide the VPN service. Tunnels are required to
carry the layer-2 frames or layer-3 packets from one customer site to another, regardless of the routing tables and layer-
2 FDBs of the underlying service provider network.

Source: Nokia ION Learning Services course “Nuage Networks 210 WBX”, Module 4, slide 10. See references [15].

IP Networks and Services Fundamentals

20 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course
VPN services can be combined to create more complex virtual networks.

For instance:
• A VPLS can be bound to a VPRN interface that exists on the same or on a different router. A VPLS attached to a VPRN
interface that exists on the same router is referred to as a routed VPLS or simply rVPLS.
• A VPWS on a given router can be terminated into a VPLS or into a VPRN interface that exists on a different router.

For more details, refer to the Nokia Services Architecture course (#3FL30636AAAAZZZZA).

IP Networks and Services Fundamentals

21 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course
Customer edge devices
A customer edge (CE) device resides on the customer premises. The CE device provides access to the service provider
network over a link to one or more provider edge (PE) routers. The end user typically owns and operates these devices. CE
devices are unaware of tunneling protocols or VPN services provided by the service provider.
Provider edge devices
A provider edge (PE) device has at least one interface directly connected to the CE devices. In addition, a PE device usually
has at least one interface that connects to the service provider core devices, or provider routers. Because the PE device
must be able to connect to different CE devices over different access media, the PE device is usually able to support many
different interface types. The PE device is the customer's gateway to the VPN services offered by the service provider.
Provider router
Provider (P) routers are located in the provider core network. The P router supports the service provider’s bandwidth and
switching requirements over a geographically dispersed area. The P router does not connect directly to the customer
equipment.

IP Networks and Services Fundamentals

22 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course
In order to provide a virtual private network (VPN) service, the service provider must encapsulate the customer data to
traverse the service provider network. Depending on the nature of the VPN service, the encapsulation of the layer-2 and
layer-3 headers may be included. Customer data must be transported without any changes across the service provider
network from one customer site to another customer site. This way, the provider can attach any additional information to
the original packet for forwarding inside the provider network. The provider will remove this information and forward the
packet using the standard layer-2 and layer-3 information at the destination CE.

In order to accomplish this, an additional header is added to customer data for transport across the service provider
network. Instead of routing or switching the data across the service provider’s network using the customer’s layer-2 or
layer-3 headers, the data traverses the network using the header that is added at the edge of the service provider
network. Therefore, customer data is effectively tunneled across the service provider network unchanged.

In this slide, packets from the source CE arrive at the ingress PE and are encapsulated with a tag that allows them to be
forwarded through the provider network along specific paths. The forwarding path is based on this provider-created tag.
The tag is removed before the packet is forwarded to the destination CE so that the original packet arrives at the
destination CE unchanged.

IP Networks and Services Fundamentals

23 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course
All the VPN services described earlier use tunnels to transmit customer data across the service provider network. When
MPLS is used, customer data is encapsulated with two MPLS labels: an outer transport label and an inner service label.

GRE uses an additional IP header as the transport tunnel, but it also requires an MPLS label to identify the service tunnels
inside.

VXLAN, similar to GRE, uses an additional IP header as the transport tunnel, but the VPN service that the customer data
belongs to is identified by means of a VXLAN-specific header that carries what is called the Virtual Network Identifier (VNI).

IP Networks and Services Fundamentals

24 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

25 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

26 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course
The purpose of MPLS is to provide a tunneling service to forward customer packets across the provider network by adding
a special header called a label. The label is simply an additional header added to packets coming into the provider network.
In an MPLS network, routers are categorized as Label Edge Routers (LERs) or Label Switch Routers (LSRs).
The LERs are the endpoints of the MPLS tunnels, known as Label Switched Paths (LSPs), and are normally at the edge of
the network.
The ingress LER (iLER) is the starting point of the LSP, or the start of the tunnel. The egress LER (eLER) is the termination
point of the LSP, or the end of the tunnel.
The LSPs are set up using an MPLS signaling protocol, such as LDP (Label Distribution Protocol) or RSVP-TE (Resource
Reservation Protocol with Traffic Engineering extensions). RSVP and LDP are covered in more detail in the Nokia MPLS
course.
The LSRs are at the core of the network and provide connectivity between the LERs.
The MPLS-enabled routers (LERs and LSRs) use a signaling protocol to distribute labels across the network. These labels
are used to make the forwarding decision for incoming traffic, rather than the IP address. This turns the layer-3 routed
network into a switched network.

IP Networks and Services Fundamentals

27 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course
Diagram source: Nokia ION Learning Services course “Nokia Multiprotocol Label Switching”, Module 2, slide 27. See
references [17].

IP Networks and Services Fundamentals

28 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course
In the context of VPN services, each router only needs to advertise a label for its system IP address. The diagram above
shows the example of R3 advertising a label for its system IP address (SysIP3). By doing that, the router advertises itself as
the eLER or tail-end of an MPLS tunnel.

When RSVP-TE is used as the MPLS signaling protocol, it is possible to signal multiple tunnels with the same head-end and
tail-end. Even in that case, the label for each of the multiple tunnels is typically advertised associated with the system IP
address of the tunnel’s tail end. For more details on RSVP-TE, refer to the Nokia Multiprotocol Label Switching course.

Each router independently selects the label value that it will advertise for a given prefix, even when it is propagating a
prefix originally advertised by another router.

Diagram source: Nokia ION Learning Services course “Nokia Multiprotocol Label Switching”, Module 2, slide 30. See
references [17].

IP Networks and Services Fundamentals

29 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course
As a result of the label binding advertised from the egress router R3, and forwarded by router R2, the label connection is
now complete and the LSP is established from router R1 towards router R3. The routers build a Label Forwarding
Information Base (LFIB) containing the labels advertised by the routers in the path to the destination.

Data forwarding can now take place with the negotiated labels.

Diagram source: Nokia ION Learning Services course “Nokia Multiprotocol Label Switching”, Module 2, slide 33. See
references [17].

IP Networks and Services Fundamentals

30 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course
Before an LSP (Label Switched Path) is established, labels must be distributed using MPLS signaling protocols. LDP and
RSVP-TE are examples of MPLS signaling protocols.
This slide illustrates the forwarding process of an MPLS labeled packet.
A label is added to the “unlabeled” packet by an LER at the ingress to the service provider core network. This is called a
Push operation.
The LSR checks the incoming label against its Label Forwarding Information Base (LFIB) to find the interface and outgoing
label needed to forward the packet to the next-hop. This is called a Swap Operation.
The LER at the egress of the service provider core network strips the incoming label and sends the packet again as
“unlabeled” to the customer network.
Diagram source: Nokia ION Learning Services course “Nokia Multiprotocol Label Switching”, Module 2, slide 33. See
references [17].

IP Networks and Services Fundamentals

31 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course
A Label Switched Path (LSP) can be defined as a sequence of labels and label actions performed on MPLS routers to
forward data packets from point A to point B, using label switching.
A Label Switched Path always starts from an iLER and ends at an eLER. An LSP is thus an end-to-end, unidirectional path
that carries traffic from one router to another.
In the above slide, traffic flows from right-to-left for LSP 1 and traffic flows from left-to-right for LSP 2.
The encapsulation and forwarding of packets using labels is also referred to as tunneling. Therefore, LSPs are often called
tunnels.
Tunnels must be established prior to the arrival of data packets.

IP Networks and Services Fundamentals

32 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

33 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course
RFC 3036, later updated by RFC 5036, defines the Label Distribution Protocol (LDP).

LDP can also be used to signal MPLS label bindings for the service tunnels used by layer-2 VPN services, as will be
explained in the following section. In that case, the established sessions are of type targeted LDP, instead of link LDP.

Diagram source: Nokia ION Learning Services course “Nokia Multiprotocol Label Switching”, Module 3, slide 7. See
references [17].

IP Networks and Services Fundamentals

34 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course
Accepting a label binding and installing it in the LFIB means that the advertising router is included in the path of the tunnel
that goes to the router that originally advertised the prefix. In other words, encapsulated packets whose final destination
is the relevant prefix will be forwarded to the advertising router.

The reason to only accept label bindings received from the neighbor identified as the prefix’s next hop in the routing table
is that tunnels must follow a path to the eLER equal to the shortest path selected by the routing protocol.

IP Networks and Services Fundamentals

35 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course
The end result is a full-mesh of LDP tunnels, from each router to all the other routers. As examples, the diagram above
only shows the tunnels created with R1 and R4 as iLER.

Diagram source: Nokia ION Learning Services course “Nokia Multiprotocol Label Switching”, Module 3, slides 53 and 54.
See references [17].

IP Networks and Services Fundamentals

36 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course
The example above shows the configuration required on router R1. The only required steps are to add to the “configure
router "Base" ldp interface-parameters” context the physical interfaces on which the router should speak LDP
with its neighbors, and to enable IPv4 for each of them.

Similar configuration commands need to be issued on the other routers.

Diagram source: Nokia ION Learning Services course “Nokia Multiprotocol Label Switching”, Module 3, slide 10. See
references [17].

IP Networks and Services Fundamentals

37 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

38 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

39 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

40 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

41 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course
There are always two entries for non-local prefixes, one “Push” and one “Swap,” meaning that this router can be the iLER
(head-end) of a tunnel going to the relevant prefix, but it can also be an intermediate router (LSR) of tunnels that begin on
other upstream routers.

For a “Pop” entry, there is no egress label because the packets will be forwarded without a label once its is removed from
the MPLS tunnel. The ingress label value is the one that, if received, indicates that a labeled packet has arrived at its eLER.

Conversely, for a “Push” entry there is only an egress label because an unlabeled packet will be inserted into the MPLS
tunnel by pushing an MPLS label into it.

For a “Swap” entry there are both an ingress and an egress label. When the specific ingress label value is received in a
packet, the router knows that the packet must continue on inside the same tunnel in which it came. For that, the label
must be swapped into the specific value that the next hop in the tunnel path is expecting.

IP Networks and Services Fundamentals

42 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course
See the Nokia IP Networks and Services Fundamentals v1.0 Lab Guide.

IP Networks and Services Fundamentals

43 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

44 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655
 SRC Sample Course

IP Networks and Services Fundamentals

45 Course Number: TTP3FL30632AAAAZZZZA © 2021 Nokia
Product code: (April) CID201655