>> Global VNet Peering enables you to connect
Azure Virtual Network seamlessly with
a private low latency high bandwidth connection.
This is done using Microsoft's backbone infrastructure to avoid
network bandwidth limitations that are
common to most VPN gateways.
Anavi Nahar is here to show us how easy it is
to set up Global VNet Peering today on Azure Friday.
[MUSIC]
>> Hey, everyone, Donovan Brown here with
another episode of Azure Friday.
I'm here with Anavi and she's going to teach us
about Global VNet Peering.
Tell me what is that?
>> In Azure today to ensure you have private isolated networks,
you have VNets or virtual networks.
In order to connect virtual networks,
there are multiple ways you can do it through VPN gateways,
you can do it through VNet Peering.
Up until recently, we only had
VNet Peering for within the same region.
So let's say you're in California,
so you could only connect VNets in California.
But we expanded that and we said hey,
why stop there, right?
We have this vast Microsoft infrastructure,
let our customers use it.
So what we released about a year ago now was
Global VNet Peering where you're able
to connect virtual networks in different regions.
So let's say if you have a VNet in,
pick your favorite Azure region because obviously we all have one,
East US for example is mine.
I can take a VNet in East US and connect it to
West US all literally with a click of a button.
>> The reason that I want to do this is just
for performance or there are other benefits to it?
>> Performance is definitely one but
the real world applications of
Global VNet Peering are I think data replication.
You're a large organization,
you have a lot of data.
You want to transfer it to
your second location so that it's easy to access low latency.
Also database fail over.
A region fails, you want to
fail over to another database or even another region as
a whole and those are the key scenarios that this would cater to.
>> All right. Perfect. So you have some where
to show me how cool this stuff is?
>> Yeah, exactly. So this is just the Azure portal and
I got slightly creative with my resource groups.
That's my going global resource group.
I have two VNets here,
East US, West US.
>> Okay.
>> Within them, I have two virtual machines.
Now the VMs I decided to use are the standard DB2 15s
and so if you see here on our documentation we have
the max expected network bandwidth at 25 Gbps.
Perfect, good to know.
>> Yes.
>> Another data point I want you to know
is California to Virginia.
It's East US to West US, right?
So that's about 2,700 miles according to Bing.
>> Okay.
>> All right. Let's go to my East US VNet.
Of course, I've already peered it to
West US which is why you see it's
connected here and my peer is the West US VNet.
>> Okay. Did you just do that by clicking the "Add" button?
>> Yeah, exactly. So let me just show you how I did it.
So all I did was add,
put the name of the peering from East to
West and then similarly from West to East.
Now actually, Donovan, we recently revamped this experience.
So first of all, obviously,
it's a bidirectional connection.
So you have to connect from a to b and then b
to a where a and b are your VNets, right?
But what we found based on
just data analysis and customers and creating peerings
and learning to do this data is that
customers would just create one link and say, "Oh, it's done."
So it's stuck in this initiated state.
So what we did is, at least,
in the portal we just made it easy to
just one click and you're able to literally connect VNets.
>> Right. Since they have to be bidirectional,
I shouldn't have to tell you.
If I told you one direction you
should be able to figure out the other direction.
>> Yes, exactly.
>> Clearly, as a human, don't do that and I'm messing stuff up.
So we just set the machine to do that.
>> Exactly, and so that's exactly what we did.
>> Okay.
>> All right. So let's go to now my specific VM.
So East US VM,
I just want to show you this in my private IP address which is
10.1.0.4 and then on the West US VM, it's 10.2.0.4.
Something to know is that your VNet address spaces
have to be nonoverlapping for us to be able to connect.
>> Makes sense. Otherwise, you have IP collisions.
>> Exactly. All right.
Sweet. So let's actually go into these two VMs that I have here.
I did a simple IP config and you can see I have 10.1.0.4 here,
that was the default gateway.
So my IPv4 address is.4 and on this side over here,
if I do an IP config,
I see that it's 10.2.0.4.
>> Yeah. So 1.0.4 to 2.0.4.
>> Exactly.
>> Got it.
>> Then previously I also just did a quick ping
because what's a network demo without a ping really.
So just for that checkbox,
I went ahead and did that and as you can see
it's connecting to a private IP.
There's no public IP involved which is really important to
our customers because if you're doing
the database replication scenario,
you don't want any public IP endpoint
even close to your data, right?
>> For sure. So its completely
private on the Microsoft backbone isolated.
So what I have here is
a simple receiver and
a listener that I have set up and I'll set it up.
Basically, we'll see how much data I can push through
these DS15 V2s and really test out if I
can actually push it to their maximum. All right.
So here I'm going to go ahead and do just a simple NTttcp.
This is my receiver.
I'm sending it to 10.1.0.4.
That's my receiver address.
Same as the one we had here.
On my other VM over here, same thing.
I have it set up so NTttcp knows that this is the sender,
how much data it's sending,
and then to what address.
It was the 10.1.0.4. Perfect. All right.
So let's have our receiver receive.
>> One more in there, there you go.
>> Then let's have our sender send.
>> One more, there you go.
>> Perfect. Now while it's happening
obviously it's going to ramp up but
we'll be able to see really this picking up, right?
So it starts off.
It started around 10, picking up
11 and basically we'll see this go up, up,
up, and up as sending more data and receiving as much data.
>> Got you.
>> So really just to think of how you can
just connect to East of US,
Virginia to California and just keep pushing
this data all with a simple click, private IPs,
and you keep pushing and look I have it almost up
to 19-20 gigs and in the last time,
I did this this was 25 gigs.
>> So there's a little variability
in there but the performance that you're going to be able
to get is far
greater than anything you would get
without this type of feature enabling that.
>> Exactly and we just have it there at 28 even,
which is really crazy.
>> Yes, for being able to go from one side of the world or
one side of the United States to the other is very impressive.
This is all GA, ready to rock and roll.
>> This is all GA.
It's been GA for awhile.
When we GA'd it, we had
a few constraints like for example there was
no Global VNet Peering with gateway transit.
So you being able to use a central gateway to go
on-premises and still having
multiple gateways in the event that you
have to go on premises, right?
>> Got you.
>> But since then we've GA'd all of that functionality.
So totally GA, you can use it all,
all data portal, PowerShell,
CLI, pick your favorite.
>> Perfect. The UI has now been improved such that there's
a lot less clicks to get going and
you're not going to make that same mistake that a lot of us do,
do one-half and not the other and
then you're wondering why it's not working.
>> Exactly, just one single click.
You can go global with one click.
>> That's awesome. Thank you so much.
So we're learning all about
Global VNet Peering here on Azure Friday.
[MUSIC]