EASY

VIRTUAL
NETWORK
EVN: EASY VIRTUAL NETWORK

VNET TRUNK
VRF A VRFAA
VRF

VRF B VF BBB
VRF
VRF

Summary by Vicens Ferran

#StillLearning /vicens-ferran-rabassa 2
 EVN (EASY VIRTUAL NETWORK)

INDEX
Page 5 – Introduction.
Page 6 – Description of the course on EVN by Mr. Arash Deljoo.
Page 7 - Virtual Networking Concept.
Page 7 - Benefits of Network Virtualization.
Page 8 - Summary table of Network Virtualization techniques.
Page 9 - How EVN helps us?.
Page 9 - But, What is EVN?.
Page 10 - EVN in more detail.
Page 11 - Some concepts used in EVN: Vnet TAG, Vnet Trunk, Show-derived-config.
Page 12 - Comparing Configuration Procedures (I): VRF Lite.
Page 13 - Comparing Configuration Procedures (I): EVN.
Page 14 - How does EVN works?.
Page 15 - Troubleshooting and Monitoring.
Page 16 - EVN with Routing Protocols: Rip & EIGRP.
Page 17 - EVN with Routing Protocols: OSPFv2.
Page 18 - EVN with Routing Protocols: BGP.
Page 19 - BGP Route Distinguishers.
Page 20 - Route Targets (RT).
Page 21 - Sharing Routes within VRFs: Route Leaking.
Page 22 - In Summary.

/vicens-ferran-rabassa 3
 EVN (EASY VIRTUAL NETWORK)

INTRODUCTION

This work has been inspired on the course Easy Virtual Network (EVN) by Arash Deljoo in Udemy. I tried to summary it.
I want to agree Mr. Deljoo for it’s clear and practical teaching that makes you get trapped in its courses. In the course of Mr. Deljoo you can
learn more deeply and practically all the concepts about EVN.

Requirements
Minimum Level: CCNA
Have read and understood previously concepts about VRF Lite

It’s a CCNP Enarsi topic

/vicens-ferran-rabassa 4
 EVN (EASY VIRTUAL NETWORK)

DESCRIPTION

“Deliver traffic separation and path isolation capabilities on a shared network infrastructure with Easy Virtual Network (EVN). An IP-based
network virtualization solution, EVN takes advantage of existing Virtual Routing and Forwarding (VRF)-Lite technology to simplify Layer 3
network virtualization, improve support for shared services, and enhance management and troubleshooting. Easy Virtual Network (EVN)
is an IP-based network virtualization solution that helps enable network administrators to provide traffic separation and path isolation
on a shared network infrastructure. EVN uses existing Virtual Route Forwarding (VRF)-Lite technology to: Simplify Layer 3 network
virtualization, Improve shared services support and Enhance management, troubleshooting, and usability
What Problems Does It Help Solve?
EVN reduces network virtualization configuration significantly across the entire network infrastructure with the Virtual Network Trunk.
The traditional VRF-Lite solution requires creating one sub interface per VRF on all switches and routers involved in the data path,
creating a lot of burden in configuration management.
EVN removes the need of per VRF sub interface by using “vnet trunk” command. This helps reduce the amount provisioning across the
network infrastructure
EVN enhances network virtualization troubleshooting by making VRF-Lite easier to deploy, operate, and scale. A routing context
command mode allows network operators to perform troubleshooting issues that pertain specifically within a VRF without specifying the
VRF name in every command.”

This is Mr. Arash Deljoo description on his course on EVN in Udemy.

/vicens-ferran-rabassa 5
 EVN (EASY VIRTUAL NETWORK)

Virtual Networking
But let’s remember something. We are talking about Layer 3 Virtual Networks.
What does it mean? Means that we are communicating with other devices
through different logical networks with different or same Ipv4 subnets (we
can overlap subnets), and all of this through the same cable and links. Each
logical network remains separate from the others in the routers, devices, links
and cables. General or global Context RIB
In each router coexist a separated RIB (Routing Information Base in control
plane) and FIB (Forwarding Information Base in Data Plane) for each VRF. And
the General Context Router with it’s normal or default RIB and FIB.
A single IP infrastructure can be virtualized to provide up to 32 virtual
VRF A RIB
networks end-to-end.

Benefits of network virtualization VRF B RIB

Path Isolation:
-Maintain traffic partitioned over Layer 3 infrastructure.
-Transport traffic over isolated Layer 3 partitions. In Summary
-Map Layer 3 isolated path to Vlans in access and Services Edge. - Device virtualization in Control Plane, Data Plane and
Services virtualization.
At Services Edge:
- Provides access to services (Shared or Dedicated). - Data path virtualization:
-Can be applied policies per partition. • Hop-by-Hop -> VRF Lite end to end
-Isolate application environments if necessary. • Multi-Hop → VRF Lite+GRE+MPLS-VPN

/vicens-ferran-rabassa 6
 EVN (EASY VIRTUAL NETWORK)

The table above resumes some of Network Virtualization techniques. We are Here
Transport Layer Technique

Layer 3 VRF-Lite (Campus networks)

Ethernet
Easy Virtual Network (EVN)

AToM (EoMPLS)
Layer 2
VPLS
MPLS
Layer 3 MPLS VPN
OTV
Layer 2
VPLSoGRE
IP
VRF-Lite over mGRE
Layer 3
MPLS-VPN over mGRE
NOTE: This table has been extracted from a document created by Radek Boch CCIE#7095 for a Cisco Expo in the year 2.011. Maybe there are new technologies not listed here,
but this is a General View on Network Virtualization Techniques.

/vicens-ferran-rabassa 7
 EVN (EASY VIRTUAL NETWORK)

How EVN helps us? The main goal.

Now, let’s figure out that we have to configure an scenario with for example 100 VRF’s.
• Configuring VRF Lite, we should need a minimum of 27 configuration commands Per Router and Per VRF. Let’s say a total of 2.700
configuration commands.
• Configuring VRF Lite with EVN, we should need a minimum of 22 commands Per Router and Per VRF. This totalizes 2.200 configuration
commands.
• The main goal is that we have a savings of 500 commands. Easier, right?
But, What is EVN?.
EVN it’s an Ip-based virtualization technology. It’s compatible back guards with VRF Lite, an extends it a little more beyond. As we have
seen in VRF Lite summary, EVN uses the same network infrastructure to maintain multiple virtual networks , each one with its logical
routing and forwarding tables, granting the path isolation between them. This virtualization is end to end over layer 3 networks with
another main goal that is securing each one network.
To achieve network path isolation without these virtualization technologies:
- We can separate paths using dedicated routers.
- We can use ACLs (Control Access Lists).
Why is better to use that virtualization techniques?
- ACLs don’t support unique RIB and FIB. Its management gives less tolerance for errors and produces excess administrative work.
- Separating paths with dedicated routers is more expensive.
In general, these two ways of separating routes increase the complexity of management and maintenance, and this increase the
resources dedicated by the company and therefore its financial expense.

/vicens-ferran-rabassa 8
 EVN (EASY VIRTUAL NETWORK)

EVN in more detail.

Prerequisites
- A single Ip infrastructure is required.
- You must have a functioning campus design in place before adding virtualization to a network.
- You should understand virtual routing and forwarding (VRF) instances and how they are used to maintain traffic separation across the
network.
Characteristics and Restrictions
- An EVN trunk is allowed on any interface that supports 802.1q encapsulation, such as Fast Ethernet, Gigabit Ethernet, and port channels.
- There are additional platform and line-card restrictions for an EVN trunk. Check Cisco Feature Navigator, www.cisco.com/​go/​cfn for
supported platforms and line cards.
- A single IP infrastructure can be virtualized to provide up to 32 virtual networks end-to-end.
- If an EVN trunk is configured on an interface, you cannot configure VRF-Lite on the same interface.
- The following are not supported by EVN: IS-IS, RIPv1, Route replication is not supported with BGP, Certain SNMP set operations, OSPFv3
is not supported; OSPFv2 is supported.
- The following are not supported on an EVN trunk: Access control lists (ACLs), BGP interface commands are not inherited, IPv6, except
on vnet global, Network address translation (NAT), NetFlow, Web Cache Communication Protocol (WCCP).

/vicens-ferran-rabassa 9
 EVN (EASY VIRTUAL NETWORK)

Some concepts used in EVN

Here we are going to define some topics that we will need to understand this technology..
Vnet Tag (VN).:
The Vnet Tag is a number between a range from 2 to 4096. It’s configured by the administrator. It’s used to identify each VRF, and when is
applied the EVN Vnet Trunk command, it’s used as a dot1q tag in the Layer 3 trunk created automatically by EVN.
Vnet Trunk.:
This command create automatic hidden dot1q sub-interfaces. Vnet trunks use the Vnet Tags configured in VRF Definition as a dot1q tag.
Each of interfaces created by the Vnet Trunk are separated and isolated between them. The sub-interface inherits ip address from the
main interface . Vnet Trunk command is allowed on any physical port interface that is compliant with dot1q, also is allowed on Port-
channels. But, when using Vnet Trunk command is not supported to create manually sub-interfaces.
Show derived-config.:
Configuration commands can be applied to an interface from sources such as static templates, dynamic templates bound by resource
pooling, dialer interfaces, AAA per-user attributes and the configuration of the physical interface. The show derived-config command
displays all the commands that apply to an interface.
The output for the show derived-config command is nearly identical to that of the show running-config command. It differs when the
configuration for an interface is derived from a template, a dialer interface, or some per-user configuration. In those cases, the
commands derived from the template, dialer interface, and so on, will be displayed for the affected interface.
In practice. If we use the command show vrf [VRF_NAME] you will see listed all the interfaces and sub interfaces assigned to the VRFs. But
if you type the show run command, you won’t see listed the sub interfaces. They are hidden. So here comes this command to help us: show
derived-config. Typing this command is listed a “copy” of the show run, but with configurations hidden.
The automatic creation of the sub interfaces by EVN has more preference that the commands we type as administrators, and creates
DERIVED configurations that can remain hidden of our own configurations.

/vicens-ferran-rabassa 10
 EVN (EASY VIRTUAL NETWORK)

COMPARING CONFIGURATION PROCEDURES (I)

Let’s compare how to configure VRF Lite vs EVN. Let’s begin with Gi0/0
VRF Lite Configuration. We need a total of 54 commands. Gi0/1 Gi0/1
VRF A VRF A

Defining the VRF on R1, R2 Gi0/2 Gi0/2

VRF B VRF B
R1(config)#vrf definition A
R1(config-vrf)#[description]
R1(config-vrf)#address-family ipv4 unicast
R1(config-vrf)#exit Configuring Sub Interfaces (R1,R2)

R1(config)#vrf definition B R1(config)#int Gi0/0

R1(config-vrf)#[description] R1(config-if)#no shutdown
R1(config-vrf)#address-family ipv4 unicast R1(config-if)#int gi0/0.1
R1(config-vrf)#exit R1(config-subif)#vrf forwarding A
R1(config-subif)#encapsulation dot1q 2
R1(config)#int Gi0/1 R1(config-subif)#ip address 10.1.2.1 255.255.255.0
R1(config-if)#vrf forwarding A
R1(config-if)#ip address 10.1.0.1 255.255.255.0 R1(config)#int Gi0/0
R1(config-if)#no sh R1(config-if)#no shutdown
R1(config-if)#int gi0/0.2
R1(config)#int Gi0/2 R1(config-subif)#vrf forwarding B
R1(config-if)#vrf forwarding B R1(config-subif)#encapsulation dot1q 3
R1(config-if)#ip address 10.1.0.1 255.255.255.0 R1(config-subif)#ip address 10.1.2.1 255.255.255.0
R1(config-if)#no sh
*Same configuration in Router 2
*Same configuration in Router 2

/vicens-ferran-rabassa 11
 EVN (EASY VIRTUAL NETWORK)

COMPARING CONFIGURATION PROCEDURES (II)

Now it’s turn on EVN Configuration. We need a total of 44 commands. We are reducing the configurations on 10 commands. EVN will take the
job of doing it for us taking into account the Vnet Tags defined in each VRF and creating a virtual Trunk Link, tagging each frame with 802.1Q
with the Vnet Tag defined in the VRF, only typing the Vnet Trunk Command.

Defining the VRF on R1, R2 For creating the VRFs with EVN it’s mandatory to use the new method of VRF
definition.
R1(config)#vrf definition A
R1(config-vrf)#[description] Gi0/0
R1(config-vrf)#vnet tag 2 Gi0/1
Gi0/1 VRF A
R1(config-vrf)#address-family ipv4 unicast VRF A
R1(config-vrf)#exit

R1(config)#vrf definition B Gi0/2

Gi0/2
R1(config-vrf)#[description]
VRF B VRF B
R1(config-vrf)#vnet tag 2
R1(config-vrf)#address-family ipv4 unicast
R1(config-vrf)#exit

R1(config)#int Gi0/1
R1(config-if)#vrf forwarding A Configuring Sub Interfaces (R1,R2)
R1(config-if)#ip address 10.1.0.1 255.255.255.0
R1(config-if)#no sh
R1(config)#int Gi0/0
R1(config-if)#vnet trunk
R1(config)#int Gi0/2 R1(config-if)#no shutdown
R1(config-if)#vrf forwarding B R1(config-subif)#ip address 10.1.2.1 255.255.255.0
R1(config-if)#ip address 10.1.0.1 255.255.255.0
R1(config-if)#no sh R2(config)#int Gi0/0
R2(config-if)#vnet trunk
*Same configuration in Router 2 R2(config-if)#no shutdown
R2(config-subif)#ip address 10.1.2.2 255.255.255.0

/vicens-ferran-rabassa 12
 EVN (EASY VIRTUAL NETWORK)

How does EVN works? The main goal.

If we take as a basis the most complex network scenario that I posted in my summary on VRF Lite. The first thing we can see is that is a
scenario of tedious configuration because of the quantity of Sub-Interfaces that there are in it. One of the goals of EVN in a Lan, maybe
the most important, is that it help us to reduce this over helm of working in the configuration.
HOW? With the VNET TRUNK. If we compare the scenario below with the other one in VRF Lite Summary, published for me previously, we
can see that the configuration is reduced minimum in 24 Sub-Interfaces between R24 and R26. EVN will take the job of doing it for us
taking into account the Vnet Tags defined in each VRF and creating a virtual Layer 3 Trunk Link, tagging each frame with 802.1Q with the
Vnet Tag defined in VRF. Easier, right?

 Static Routing or Routing Protocol →

Vnet Trunk Vnet Trunk

Vnet Trunk Vnet Trunk

/vicens-ferran-rabassa 13
 EVN (EASY VIRTUAL NETWORK)

Troubleshooting and monitoring.

Take into account that all interfaces that hasn’t been associated with a VRF, they belong to the global RIB, or global Vnet, or Global VRF.
All VRF’s are separated and isolated, so if you use commands to see the Routing Table, have to apply them for the VRF you want to
inspect.:
Show ip route → will show the general context router or default RIB, so you will not see the routes on each VRF.
If you want to inspect the RIB of, for example VRF B you have to type: Show ip route vrf [Vrf Name]
But there is another way to do that.

You can enter into the VRF context, and the operate inside it:
router#routing –context vrf [VRF_NAME]
router%VRF_NAME# show ip route
router%VRF_NAME# ping A.B.C.D
router%VRF_NAME# telnet A.B.C.D
router%VRF_NAME# traceroute A.B.C.D
router%VRF_NAME# exit

To display VRF configuration info, you can use router#show run vrf [VRF_NAME]
It displays VRF Definitions, Interfaces in VRFs and protocol configurations for Multi-VRF.

/vicens-ferran-rabassa 14
 EVN (EASY VIRTUAL NETWORK)

EVN With Routing Protocols

For configuring Routing Protocols with EVN, we will have to use, in general, the Address Families format in RIP and in EIGRP, except in OSPF.
One thing to take into account is that, in VRF Lite, we can use IS-IS, but not in EVN because IS-IS is not compatible with Vnet Trunk.
> RIPv2 and EIGRP
Once configured Ip addressing, VRF definitions, assigned interfaces to VRFs, and configured the Vnet Trunks as per diagram, we can
configure the routing protocols.
The configurations in both protocols are very similar.

RIPv2 EIGRP

R1(config)#router rip R1(config)#router eigrp [AS Number / Named mode]

R1(config-router)#version 2 R1(config-router)#address-family ipv4 unicast vrf [VRF-NAME] [AS
R1(config-router)#address-family ipv4 unicast vrf [VRF-NAME] Number]
R1(config-router-af)#network A.B.C.D R1(config-router-af)#network A.B.C.D WildCard Mask
R1(config-router-af)#no auto-summary R1(config-router-af)#exit
R1(config-router-af)#exit

Every network commands and configurations are done under the VRF address- Each Eigrp configuration must be done under the VRF Address-Family declaration.
family environment. Every VRF (Address-Family) can be configured with the same or different AS-Number.

/vicens-ferran-rabassa 15
 EVN (EASY VIRTUAL NETWORK)

EVN With Routing Protocols

> OSPFv2
Once configured Ip addressing, VRF definitions, assigned interfaces to VRFs, and configured the Vnet Trunks as per diagram, we can
configure the routing protocols. In this case OSPFv2.
OSPFv2 is not compatible with Address-Families definition. IETF has been kept updating OSPFv3, and this feature is introduced in the
protocol since RFC 5838.
This means that, as OSPFv3 is not supported by EVN, we have to use OSPFv2. As OSPFv2 is not compatible with Address-Family definitions,
we have to use a different instance of OSPF for each VRF. So, if there are many VRFs, this can overwhelm the router resources, and this
have to be taken it into account.

OSPFv2

R1(config)#router ospf [PID] [VRF-NAME]

R1(config-router)#router-id A.B.C.D
R1(config-router-af)#network A.B.C.D [Wildcard Mask] [Area]
R1(config-router-af)#no auto-summary
R1(config-router-af)#exit

For every VRF we will use an OSPFv2 process, and network commands and configurations are done
under the OSPF PID VRF-NAME environment.

/vicens-ferran-rabassa 16
 EVN (EASY VIRTUAL NETWORK)

EVN With Routing Protocols

When configuring EVN with the Address Families, we can configure a path in the global Vnet or global VRF (without using Address-
Families) and then configure each VRF on a different Address-Family. So it means that we can have a path configured in the global RIB and
FIB with the same, or different routing protocol.
> BGP
Once configured Ip addressing, VRF definitions, assigned interfaces to VRFs, and configured the Vnet Trunks as per diagram, we can
configure BGP.
Also, we can configure Address-family with VRF definition using eBGP or iBGP.

- One consideration on BGP configuration. BGP

RD (Route Distinguisher). If you try to configure an Address-Family R1(config)#router bgp [AS_NUMBER]
VRF in BGP directly, you will see an error message in the cli: “vrf R1(config-router)#neighbor A.B.C.D remote-as [AS_NUMBER]
[VRF_NAME] does not have an RD configured”. Configuring Global RIB
We need to configure an RD (Route Distinguisher) previously in the R1(config-router)#address-family ipv4 unicast
VRF Definition. R1(config-router-af)#network A.B.C.D mask [MASK]
R1(config-router-af)#exit
In next page I will talk about Route Distinguishers. Configuring for concrete VRF
R1(config-router)#address-family ipv4 unicast [VRF_NAME]
R1(config-router-af)#network A.B.C.D mask [MASK]
R1(config-router-af)#exit

/vicens-ferran-rabassa 17
 EVN (EASY VIRTUAL NETWORK)

BGP Route Distinguishers (RD).

VRF Lite and EVN do not need the configuration of RD. It’s a feature used in MPLS with some types of VPN. So, it’s an extended
feature for VRF and EVN not used in VRF Lite, only if we are using BGP. So, here we will see only the basics on this topic.
What Route Distinguishers?
Let’s figure out that we are connecting some of our corporate networks trough Internet, or we are working in an ISP, and we have
multiple customers that connect their Lans to the Internet through us. Surely that we will have multiple Lans using the same subnet
addressing, for example 192,168,1,0/24. Also, maybe in the corporate networks, and surely in the ISP, we have created VRFs and
assigned it to each different network, to securely separate the routing domain.
Here comes the question.: How do we know which subnet belongs to each customer? In other words, if the majority of subnets use
the same addressing, How do we differentiate them?
We need a type of tag or a number assigned to each VRF that help us to make the differentiation. That’s is the RD or Route
Distinguisher. It’s a 64 bit identifier prepended to the path, it’s required if we are using BGP.
So, the purpose of RDs is to distinguish two identical subnetworks, or Ip Prefixes. In other words, make a prefix unique over the
network. The details of RDs are defined in the RFC 4364.
RDs have different types and formats,
Declaring an RD in the VRF definition
but this is beyond the scope of this document.
R1(config)#ip vrf A
We will see it in upcoming documents. R1(config-vrf)#rd 65120:100 or 1:1 or 100:10 (They are different examples)

----------------------------
As example, RD is declared in the VRF in this way:
R1(config)#vrf definition A
Route-target-both as a macro to add both R1(config-vrf)#rd 65120:100

Commands (import and export) simultaneously.

/vicens-ferran-rabassa 18
 EVN (EASY VIRTUAL NETWORK)

Route Targets (RT).

Let’s figure out an scenario where there are some VRFs, and we have to share some services or files between them, but granting
that the VRFs will continue isolated, in other words, granting the security. Here we have RT (Route Targets) to help us in that work.
What Route Targets?
Route Distinguishers (RD) are used to maintain that identical routes in different VRFs are UNIQUE. On the other hands, RT (Route
Targets) are used or can be used to share routes between different VRFs. We apply RT to VRFs to control the import and export of
routes between them.
In case of VRF Lite RT configuration is not mandatory, unlike RD is mandatory if we use BGP.
Route target is used mostly in MPLS with MP-BGP, and is a 64 bit identifier, used as part of BGP Attribute (extended community) to
identify which route should be exported or imported to specific VPN. It may be the same across multiple VPNs specially if are used
Shared Services.
There are two types of RT: Export Route Target and Import Route Target. We can configure each VRF with one or more Route Targets
depending on the import and export
policies between VRFs. This allows greater Declaring an RD in the VRF definition
Flexibility. RTs can be used locally (on our Lan) or R1(config)#ip vrf A
Prepended with MP-BGP as Extended R1(config-vrf)#route target export 65120:100 or 1:1 or 100:10

Communities. And the format can be the same R1(config-vrf)#route target import 65120:100 or 1:1 or 100:10
----------------------------
as defined for RDs. There is a shortcut command
R1(config)#vrf definition A
R1(config-vrf)#route target export 65120:100 or 1:1 or 100:10
R1(config-vrf)#route target import 65120:100 or 1:1 or 100:10

/vicens-ferran-rabassa 19
 EVN (EASY VIRTUAL NETWORK)

IN SUMMARY.
Easy Virtual Network (EVN) is an IP-based virtualization technology that provides end-to-end virtualization of two or more
Layer-3 networks. You can use a single IP infrastructure to provide separate virtual networks whose traffic paths remain
isolated from each other.
EVN builds on the existing IP-based virtualization mechanism known as VRF-Lite. EVN provides enhancements in path isolation,
simplified configuration and management, and improved shared service support. EVN is backward compatible with VRF-Lite to
enable seamless network migration from VRF-Lite to EVN.
EVN supports IPv4, static routes, Open Shortest Path First version 2 (OSPFv2), and Enhanced Interior Gateway Routing Protocol
(EIGRP) for unicast routing, and Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP) for IPv4
Multicast routing. EVN also supports Cisco Express Forwarding (CEF) and Simple Network Management Protocol (SNMP).
This two technologies VRF Lite and EVN are important for secured virtualizing networks in a single path IP infrastructure
environment. Maybe, there are few scenarios where to apply them on our Lan environments. But certainly, they are the basis to
understand what's going on in ISPs. This technologies permits to extend our Lans beyond of the scope of itself, and going also
through Internet, because they permit secured virtualization of different paths from one end to the other, in a secured way,
running with MPLS, some types of VPN, BGP, and more technologies.
In case someone wants to expand their knowledge about EVN or read a little more about this technology, here I leave some links
on the Cisco web:
Easy Virtual Network Configuration Guide, Cisco IOS XE Release 3S
Simplify Layer 3 Network Virtualization
Easy Virtual Network Configuration Example
Easy Virtual Network Management and Troubleshooting

/vicens-ferran-rabassa 20
 EVN (EASY VIRTUAL NETWORK)

Sharing routes within VRFs (Route Leaking)

In some kind of scenario, perhaps, you will need to share some kind of routes within VRFs. For example, in
the case that you have a Guest Wifi in one VRF and the normal Corporate Lan in another VRF for security.
But let’s figure out that the Gateway of the both networks is the same.
In this case, inevitably, you would have to inject the Gateway Route to the Guest Wifi Network.
This is Sharing Routes within VRFs or ROUTE LEAKING.

We will talk about this topic on the next summary that will be coming soon.

/vicens-ferran-rabassa 21
Thanks for watching.
I’m always #StillLearning

If you want to see more of my

content, follow me on LinkedIn.

/vicens-ferran-rabassa