Microsoft Azure Training - [7] Azure Virtual Networks - Part 1 (Exam 70-533) Video Lecture | Microsoft Azure: A-Z Guide - Database Management

hi everyone this is Sean ismo from cloud
Ranger and you are viewing the Microsoft
Azure training today we are going to
talk about the is your virtual networks
and this is the part one of several
parts that are going to be in a zero
virtual networks sessions I have divided
this in multiple parts initially I
thought that we could cram a lot
together but then I thought that we are
going to make this in several parts
because of the amount of information
that we have to cover for the 7533 exam
so this is taken directly from the 7533
exam requirements that as you can see
it's quite a bit to cover there is
configure a virtual network session
section there is a modify a network
configuration and design and implement a
multi-site or hybrid network session my
goal is to go through each of these
requirements and provide a demonstration
as we do this so a couple of things will
happen one we will definitely cover as
much as possible from this for example
int of view and by providing a
demonstration and talking about it you
will also be ready to do similar things
in your lab or in a production
environment after careful planning so
I'm not going to just make this session
based on just exams so we might do
comply steps more than required for the
exam just to make sure that everything
fits in together so let's get it started
as there is a lot to cover the first
thing we will talk about is the building
blocks of is your infrastructure as a
service we have talked about this before
the three building blocks for a zero
infrastructure as a service is compute
networking and it storage we have talked
to brief about compute and today we are
going to actually deep dive into real
exam requirements about networking and
in the future we'll be talking about
storage as well
these sessions this session for
networking sort of assumes certain
periods and certain knowledge that you
should already have so I'm not going to
go into basic what is the network or how
networking components come together to
make a network I'm not going to talk
about virtual a virtualization virtual
networks I'll assume that you already
know a little bit about all this and we
will continue from there so the first
thing we want to talk about is what is a
virtual network or infinite and this is
with respect and context too as your
virtual networking and VIN it
Microsoft's explanation and definition
for this is that it's a it's a customer
managed secure isolated virtual network
or it's a network overlay that can be
configured in a zero the virtual network
in a zero is not too different from the
virtual network you're probably
accustomed to in hyper-v or VMware or
whatever on-premise virtual
virtualization technology you are
currently using so if you know a little
bit about virtual networks and how
virtual networks work it is similar to
how it works in the cloud on the 0 from
our point of view here in this course so
let's talk about a little bit in details
about the a zero virtual network so when
you create a virtual network on a 0
certain things happen the services and
the virtual machines that part of the
same Vinit or virtual network
I'll keep interchanging v-net and
virtual network but they essentially
mean the same thing so the services and
the VMS that a part of the same v-net
can access each other so what I have
over here let me get me get my pointer
this is a virtual network this is how
Visio would do for as your virtual
networks and we have two virtual
machines in this virtual network and
it's for the subnet 192 168 dot one dot
0 with a 24 bit mask or two
fifty-five 255 255 dot zero what
services and VMs that apart of same VM
can access each other means is that this
virtual machine can access this virtual
machine virtual machine over here can
access this one but when they're not
part of this virtual network for example
VM one and bm2 cannot access VM three
and vice versa
you'll notice right away that this is
sort of stuff you're used to already
with virtual virtual networks on your
hyper-v or VMware it's similar
that's the similar concept in a zero as
well that you can create multiple
virtual networks and anything in within
the virtual network is isolated so they
can only talk to each other let's talk
about certain standard details about
virtual networks in Azure subscription
one is that subscription can have as
many as 100 virtual networks and by
default to give you ten you need any
more than ten ten virtual networks and
you might need so under many
circumstances you'll have to actually
call up Microsoft and ask them to
increase it and each subscription can
have up to 100 v-net having said that
this can also obviously change Microsoft
keeps changing and building more and
Azir so this number might not be
accurate in another couple of years
dividing add more or you know they might
remove some of this second each v-net
can have as many subnets so each of this
virtual network so for example this
virtual network over here in this
example has one subnet but you could
have as many subjects as possible based
on different combinations that we will
demonstrate we'll get into when we go
into a demonstration but you can have as
many subnets as you would the virtual
networks are limited to a single region
we have talked about in our previous
sessions that Microsoft has various
reads regions across the world
right they have data centers and any
virtual network that you will create
will have to be associated to a single
region obviously you can create multiple
virtual networks and you can assign them
to several
different regions so you may have a
region where you create a virtual
network which is east USA and you can
also have one for example in Singapore
or somewhere in Hong Kong and that
subnet will be located there or on the
systems there but anytime you create one
subnet all the machines will have to be
associated to one region means all the
virtual machines will be in one region
as well so for example this virtual
network over here if it was in East USA
that means this two virtual machines
when they're associated with this
virtual network will also be located in
the same region and Microsoft Azure
calls this regional vennett's or
regional virtual networks so then the
other thing we have to notice is that
Microsoft currently is not supporting
ipv6 on this virtual networks and you
have to think that this actually might
change in future as the need arises but
for now there's no ipv6 support and the
last thing I want to talk about is that
all services deployed within a v-net can
access internet so this virtual network
when it's created and you create two
virtual machines in here by default they
have access to the Internet you do not
have to do any specific inter v-net
routing or access control or anything to
access the Internet and for you guys who
work with virtualization you would
realize that when we create a separate
virtual network on hyper-v it by default
does not have access to the Internet
unless you associate an NIC or a port
that's already connected to internet so
this might be a little tricky for some
people so for example you have your
hyper-v and you have tried to create a
production now you are trying to create
a development or multiple development
environment or hyper-v you might
eventually have issues associating them
to an echo report which has access to
the internet because of various reasons
right
you might have to act make it access to
the Internet wanting to find out that
you are taking this day of environment
that you're exposing it to production as
well and you're losing that isolation
and this has been a typical problem with
virtualization on premises but as you
can see on 0 this is not a problem you
can create as many virtual network you
want they're already connected with
isolation to the Internet and you don't
have to do any tricky DNS stuff for them
to access internet so now moving on to
the next slide we want to talk about a
couple of things the first thing we want
to talk about is cloud one link v-net so
technically there are three
configurations or three solutions you
may possibly have for your cloud service
you may have a solution where you will
not have a beam it at all
there will be no virtual networks
because you just don't need any you may
have a situation where you will only
need a cloud one leaving it and we'll
talk about in details what a cloud one
leaving it is in a bit or you could have
a cross-purposes virtual network which
we'll get into a lot of details in this
session as well as in the subsequent
sessions that weren't there are to come
so by not having any video it is very
simple you want creative cloud service
put a virtual machine in there and you
are not connecting to any local virtual
network they are directly connected to
the Internet and you can do whatever you
want from there and then there will be
time when you need a cloud when leaving
it and let's talk about what cloud well
even it's our first so a cloud only
v-net is created when a minute is
created in a 0 so if right now we go and
create a virtual network it will be
called a cloud one the virtual network
clouds and virtual machines are accessed
through endpoints on a cloud only
virtual led so by default any virtual
machine that we will have on a virtual
network will only be accessed
from outside through endpoints and in
our previous session when we went on a
brief demo on how to create a virtual
machine we have seen that we were
downloading the RDP file and we were
accessing that virtual machine through a
public IP address to get into the RDP
just because when we are creating the
virtual machine we were creating an
endpoint for RDP which is toward 3:00 at
9:00 so the other thing we have to
remember is that when we create a cloud
only virtual network we do not have to
have many considerations such as the
on-premise Network addressing so think
about this you have a network on your
cloud and you have your own premise data
center or your server room or your lab
whatever and you want to make both of
them talk if you have ever created a
site-to-site network then you know that
you can't have two addresses space
overlap each other so if I have one
92168 1.0 and the site I'm trying to
connect to is 192 168 1.0 address space
as well this boat will not work because
they overlap each other so similar to
cloud when you connect when you create
an cloud multi virtual network you're
basically saying that I'm not connecting
this to anybody on premises or another
site so you will not have to make any
considerations or plants around it so
it's very simple and just because we are
not going to do any site-to-site on a
cloud one the virtual network
there's no VPN devices required no
configuration or anything as such
required for that and which makes cloud
only virtual network very simple to
configure because there's not a whole
lot to think about our plan before you
create those but our main interest after
the cloud volley virtual network will be
the cross premises virtual network or
the hybrid networks and you will keep
hearing about this a lot when we talk
about Microsoft Azure or even you'll get
into this a lot when you are drink
production
work just because this is where most
organizations will go and what I mean by
this is that if you look at the slide
what cross premises virtual networks do
is it's a connection of on-premise
network with cloud virtual network so
you are basically connecting from your
data center to the cloud directly
through a tunnel
it's site-to-site tunnel it's very
simple but this is how most
organizations will do it so for example
today you are in a data center and this
is your on-premise network you are
basically creating something on the
cloud and what you are doing is creating
a site-to-site connection so you can
access internally from your on-premise
to your cloud services here on a 0 this
is when this is this is the basic
building essence or the basic
fundamentals of cloud that it's going to
be an extension from your on-premise to
the cloud environment and this is how
actually it works and that's why I
mentioned that you will hear about this
a lot because chances are you probably
are on-premise today and you want to
take advantage of cloud as an extension
of this environment so you have three
web servers here you probably want to
add two more on demand when you need it
and you have to make sure that they talk
to inside for example other database or
mail or exchange servers here and these
virtual machines will talk side to side
as if they're currently just on your
network over here the typical benefits
or advantages of site-to-site internal
extension of your land so that's what
cross premises means that it will cross
your own premises and go to the cloud
and that's how it will work and it
requires a VPN service obviously because
you will need a VPN device here and you
will need a VPN conversation a
configuration here and they both will
talk to each other and create those
tunnels for you it's pretty simple once
we actually go through a demonstration
of how this all works
so now the next thing we have to go into
now that we talked about the cloud world
virtual network and cross premises
network is the virtual network address
spaces and the subnets and this is
actually quite important when we try to
make a virtual network when you create a
virtual network we will have to
obviously specify the topology to 0
saying that how the network is going to
be and part of that is actually having
an address and a subnet so what we are
going to do is provide an address of
space saying that this is the address
and this is where the subjects will be
created from so just like any internal
network or a private network like your
lab there will be a private address or
space and this is basically the range
the virtual machines and services can
use so if you have a public address
space 192 168 dot one dot 0 with the 24
bit mask then you know that this private
space is where all your virtual machines
and services will be getting their IPS
from private addresses and this is basic
networking there non-routable so
obviously the public network cannot
access your private address space that
means that unless you have your virtual
network created and those IP addresses
that you have are not going to be
routable outside it is this basic
networking stuff guys and one thing is
your is that all network and the
locations are in classless inter-domain
routing notation the cedar notation
that's what we call them and this is
basically a combination of your your IP
address and the subnet mask so for
example you know a slash 8 is just a 255
or it's less 16 would be 255 255 0 0
subnet mask and that's how your privacy
dressing is going to be as well so the 3
address of space that is your provides
to you for your in
private land or virtual network however
you call it a 10.0.0.0 forward slash
eight or 172 1600 slash 12 and 192 168 0
0 slash 16 this is usually more than
enough address that you'll ever need for
your internal networking and you might
be using something similar to this
already on your own premise for example
10 dot whatever or once every 2 16 or
192 168 the thing that you have to
remember here is and that's what we
talked about in the last slide is that
when you are doing across premise means
you are doing an extension of your
current network to cloud you have to
make sure when you do that side to site
that you are not going to overlap if you
are going to do something in the lab
today and you don't have to worry about
on-premises things yet that this is
nothing you have to worry about you can
just pick up one of these ranges and you
can create your subnets in there and go
your merry way but if you are going to
do this in production and for example
you have a 192 168 0 0 16 addresses
based on your on-premise you just have
to make sure when you're planning on
your as your commercial networks you
don't have same range does they go to
overlap and you will not be able to
successfully establish a site-to-site
connection and this is no different from
side to side you do this if you have a
bunch of tunnels for your branch offices
or your head offices you already know
this ok so the next thing after we have
discussed with the address spaces is the
subnets so as we know about subjects is
that it basically breaks up your network
for more manageable sections so you
could have bunch of subnets on your same
private space for different things all
services can be accessed across subnets
this is something we are going to
demonstrate when we get there but what
this means is that if you have a web
service somewhere and you have a bunch
of other
service consuming virtual machines
you'll have to remember that they can
access each other and by this I do not
mean that they can ping each other I
just mean that if there are other
services like FTP services web services
and they have endpoints they'll be able
to access each other
internally and there is a lot of
isolation even though around it and we
will talk about it when we go through
the illustration and make it a little
bit more clear there are features that
Microsoft recently came out with called
network security groups which can be
utilized to implement access control
lists so you can have two subnets
and they can talk to each other but you
can have access control lists that can
prevent from certain services be
accessed outside the subnet or the
virtual machine if you configure the
access control list to do so so what I
mean by that you can have multiple
subnets and how can they be beneficial
so I have two examples here I have
subnet one which is 192 168 1.0 with a
24 bit mask and the subnet 2 with the 24
bit mask here with a 192 168 2.0 so
these web servers will not be on the
same subnet as the FTP server so there
is an isolation here but if this FTP
servers would like to access the web
servers for some reason they will be
able to do that that's what it means by
all services can be accessed across
subjects and unless you put an ACL on
this subnet they all will be able to
access each other and will not talk
about the ACL of the network security
groups in the session today but we will
show how the subnets can access the
services that cross each other
ok so the next thing right now I want to
do is actually jump into a demo we have
talked enough about virtual networks to
get it started and we will create a
couple of virtual networks and put some
virtual machines in there and we will
see what we can do
let's go to our machine real quick here
I have already brought up my
subscription here it was just by going
to manage the Windows Azure comm and
logging in and we are logging in with my
account cloud ranger blog at hotmail.com
obviously you are going to use your
account to get in right now under all
items you can see besides default
directory I do not have everything and
that's where you ideally want to be at
this point so if you have anything else
that you have created go ahead and
delete them if it's a lab environment
and let's go and get into creating a
virtual network so that we you create a
virtual network from the management
portal here is if you go down to
networks here currently I do not have
any networks you go to new and you will
see that it will already bring us to
network services virtual network and
these are the various options we have so
the two options that we are going to
work on today is the quick rate and the
custom create so I'm going to go through
a quick create and create a virtual
network so the first thing you need to
do is give a name to your virtual
network so the first one we are going to
do is cloud Ranger I'm going to call it
prod for production for example you can
name this anything as long as its unique
it will work so you can put whatever you
want this is the private address spaces
we had talked about there's 10 and there
is 172 16 and 192 16 and for our
purposes we'll put 192 168 and I'm going
to just choose 192 168 0 0 so the subnet
mask will be a 16-bit cedar notation or
255 255 0 0 that's what this really
means and you know what if you don't
understand cedar notations right now
because you have not got into networking
go and Bing this or Google this and read
a little bit about it because you need
to have certain knowledge of subnetting
for getting this to work or plan this
properly maybe not necessarily just
getting this to work you could probably
guess here and get away with this
but eventually to plan any network
sooner or later you have to understand
how subnetting works
Microsoft does a pretty good job over
here to actually you know not make you
do all this big level math or binary
math to figure this all out so what it
means by one eighty to one six eight
zero zero with the 16-bit mask is you
basically get a range from 192 168 0 0
to 192 168 255 255 this is a lot and
like we mentioned that your virtual
network will have to be associated with
the region or a location so for my
purposes I'll pick East us two you can
pick whatever you want to I know that
this is the region I want the DNS server
we'll discuss this later for now I am
going to go click on create a virtual
network and that is just going to go and
create a virtual network called cloud
Ranger prod and that's really what there
is to it this is where you come and
create your virtual network we will be
creating two separate networks so I will
create another one here as well but once
this completes but what we are going to
do is we're not going to do a quick
create on there we are going to go into
a regular creating a virtual network
just to demonstrate and show you the
differences between a quick create and a
regular creation of virtual network so
we do that by coming here as well
go to new virtual network and we'll do a
custom create and this is a little bit
different it brings up that little
wizard for your custom two right now so
like this one will be cloud Ranger let's
call it develop so dev as usual I will
pick East us to actually you know what
just for the sake of demonstration I'll
go to me I'm going to make this West us
and let's go to next you can see that
it's asking for a DNS server we are not
going to provide one we're going to keep
this empty and it's also giving a
certain options saying that do you want
to point to site connectivity or side to
side connectivity it's important to note
here is that if eventually you want
this virtual network that we created
which is the cloud Ranger dev tool your
on premise which was which which is
going to be a site-to-site connectivity
you have to do this now you cannot do
this later suddenly thinking that hey
you know I am going to connect to my own
premises if you already have created a
virtual network and that's not created
with this box checked you can't do that
afterwards so there's a little bit of a
planning that in that's involved before
you do this so for our session today we
are not going to do any connection to
on-premises so I'm going to just leave
this alone and go ahead and here you can
see that it's giving you options for
choosing your subnet and it's a little
bit different from the previous one
because on the previous one we were not
giving so many options of creating the
subnets but here we are this is the
address of space so I'm going to get
that your suspense 192.168.0.0 I'm going
to keep this 16 as well for this virtual
network my subnet over here is going to
be for example let's name it subnet dev
and actually let's make this subnet web
so my all web servers will go here I'm
going to have this subnet s10 and for me
I'm going to choose a 24-bit so I know
that the range for this subject is going
to be 192 168 1 dot 0 2 1 dot 255 and
I'm going to create a second subnet you
can create as many subjects as you want
in your address the space I'm going to
call this subnet I don't know FTP and
the range for this is going to be 2.0
this will be 25 as well so as you can
see these are already isolated networks
this is 1 0 to 1 255 this 191 6 8 to 0
to 255 so this is again basic networking
and subnetting we know that these are
isolated and what we are going to do is
we are going to
okay so we have basically in this
subscription right now to virtual
networks one is for our production work
for example and one is for development
work this one we did a quick create and
this one we did a custom create with a
little bit more options for the
granularity and you can see the location
over here is West USA that's the region
this dev network isn't and this one is
on East USA - obviously you are going to
create whatever is closest to you I'm
just doing this both to just demonstrate
that you could pick up your network
based on whatever region you want to and
let's now wait for this cloud Ranger dev
to create meanwhile we are going to go
and explore the cloud ranger production
network as you can see there's not a
whole lot that happened here when we did
a custom create I mean a quick raid here
it went and created this with this
diversity location there's a
subscription virtual network ID the
status isn't created let's go to
configure tab here you can see that it
did not ask us for this subnet but this
quick create went ahead and created this
anyways however in configuration it is
giving you the capability of doing
something about your subject so you can
create over here and come over here and
give it a slip right name for example
like prod or whatever and you can create
this do I don't know I'm going to call
this 1.0 changes subnet as well so it
went and guest couple of things for you
click on save just resolve the completed
over here so the quick create gives you
assumes couple of things for you and I
usually use custom create because once
you know how and what custom create can
do I rather have it all configured
before I even go and provision it so
I have done by planning and did all of
that and this is where most people who
go for doing their work rather than
custom creating this but as you can see
after custom creating you can actually
add more subnets here if you wanted to
induce some things as well so
essentially their settings there's no
DNS server here and on a dev Network I
want to show you the difference is if
you come to configure right now you can
see that it already has those two
Network subjects for us in this address
space so there's no different really
okay so that's that's all there is to
creating virtual networks but these
virtual networks really don't make any
sense if you don't go and do something
with it right so let's try to do
something with this the first thing I
want to do is show you what we can do
without a virtual network so you
remember those three barriers you have
one with no V Nets one with the cloud
one live in it which is this two and one
is the cross premise V net which we will
demonstrate in future sessions I mean a
different part of the station but for
now this is the cloud only virtual
network I'm going to show you something
that we can do within novanet so for
example let's assume that we did not we
do not have or we are not going to use
these two networks what happens so if
you remember my previous session where
we created virtual network we never
really created any but we create a
virtual machine we never really created
any virtual network but it was still
accessible and it was doing everything
else so I'm going to do something
similar right now I would go create a
virtual machine I'm going to do a quick
create I'm going to call this a cloud
Ranger VM 5000 just something random I'm
going to create any two VM put my
username put my password and as you can
see over here for the region I will just
pick East us to this is how we created a
virtual machine in quick create
last time having said that let's go to
the gallery as well and I'm going to
show you over here how we create a
virtual machine this just basically
gives you a little bit more information
so this will be a cloud Ranger vm 5000
there's a reason I'm showing this to you
right now 5 and 15 something happened
over here ok Ranger 50 and I'm going to
pick up a virtual machine but whatever
put in my password over here as you can
see over here when we are creating this
virtual machine under the region
affinity group and virtual network we
can pick up any regions but at the same
time these two options are added as well
so to create a virtual machine to be
part of your network this is where you
would come and rather than choosing this
regions you choose this virtual network
and you already know that this virtual
networks that are associated with one of
these regions so right away when you
create a virtual custom virtual machine
it gives you that option to put them on
the network right away if we did not
have any network created this tool would
not show up here and you basically pick
any one over here and there's a reason
you want to come and do the virtual
network here and not these regions once
you have created the virtual network and
I'll get into that in the demo so for
now let's actually go back to our custom
create and create one without a network
so clout Ranger VM 500 or 50 and it's a
data center and I'm going to pick up
something over here I will do a sure
password from all of that
and you can see over here it's not
giving you that option to pick
Network because just because this is a
quick create they're assuming you're not
good do all of that so I'm not going to
pick up any network this is something we
have done in the last session and that's
exactly what we are doing right now
create a virtual machine I'm going to
pause the video and come back when the
virtual machine is created and I'm going
to show you certain things when a
virtual machine is created without the
network and then we are going to create
a network I mean we created all the
network will create a virtual machine
which is going to use one of these
networks and show you the difference so
I'll be right back ok our virtual
machine is created by region 50 so I'm
going to demonstrate right now what
happens when you create a virtual
machine and it is not part of one of
your minutes so let's go to the virtual
machine here and we go to dashboard you
can see that when you created this
virtual machine it went and this is the
public IP address the public virtual IP
so it's 104 to 9 1 29 29 and this is the
DNS name so if you RDP to this or if you
have a service whatever and this is the
public dns name you will be able to
access the services and this would be
the IP address for the Public DNS and
this is the internal IP address I want
you to notice this actually this is what
I'm trying to show this is to the D IP
or dip that's what it's called it's the
internal IP address that's associated
with your virtual machine and there are
a couple of ways you can actually see
what this can do this is given to you by
a0 itself as 0 DHCP we have not
obviously created in DHCP or anything
but as your provides this to you because
you have not created a virtual network
and associated that virtual network with
this VM so this is what I wanted to show
for this virtual machine which was
created without in virtual net assigned
to it and what I'm going to do right now
is create a virtual machine
and this time I'm going to pick a
network that we have created so I'm
going to call this Ranger VM 100 just go
through in for a course whatever you can
pick based on your requirements I know
we haven't gone through creating virtual
machine in details and we have future
sessions on that but you can just follow
through and create a virtual machine and
get used to this process is not ready
overly complicated it's going to go and
pick up a cloud service leave this all
as default here we are go to this time
choose a virtual network and I'm going
to choose the dev environment if you
recall dev environment we created two
subnets
and it's actually offering you those two
subjects right now as soon as you choose
the dev network the subject that we are
going to choose over here is 1.0 so
which is the subnet web and I'm going to
leave everything here default okay so
this if you're following through you can
pause and you can pretty much put your
stuff over here and that's the VM I
would create and let's go ahead and
create this virtual machine I'm going to
create two virtual machines within this
network to add in both subnets to
demonstrate a couple of interesting
things so let's go ahead and create
another one it's going to be similar I'm
going to call this one Ranger VM 200 for
example and similar in everything else
and this is really so simple if you have
followed the session once you'll be able
to do this without any issue at all as
you can see everything is fine I'm going
to choose a virtual network and we are
using this virtual network that we had
created cloud ranger depth
and this time for the subnet I'm going
to pick this range 1 9 2 1 6 8 2.0 and
it would be subnet FTP and let's just
interesting something here I want to
show you that how subnets can
communicate between services remember
that ACL we had talked about so I will
create an endpoint over here for HTTP so
we will know that it's going to open the
port 80 for you besides support RDP 4 3
3 8 so this tool will take a little
while it takes few minutes to actually
create this virtual machines if you
click on the details you can see that
they do a bunch of stuff to create these
virtual machines so I'll be right back
once all these virtual machines are
created just remember that we created
this two virtual machines they both are
part of the cloud range and the cloud
Ranger dev Network virtual network and
they both are on separate subnets so
let's pause this and come back when they
are all created already those two
machines are made and we are back again
so this is going to get really
interesting right now so I want to show
you this let's go to Ranger VM 100 and
go to the dashboard here when we did a
quick create and we did not choose a
virtual network it went and picked up an
address right if we go to cloud Ranger
50 go to dashboard we can see it was
random address that was picked up for
the internal IP address this is the
address that the virtual machine has
right now let's go to Ranger VM 100 and
let's look at that as real quick here
guess what he picked up the address from
the subnet that we had created so our
subnet which is under the cloud ranger
dev a virtual network was 192 168 1.0 so
the VM when it was being created went
and picked up one of the addresses from
that range
you might have a quick question that who
did provide this address to the virtual
machine because we do not have a DHCP
server here we did not configure one
well as zero does that for you it goes
and it notices that it you have a
specified evident and it goes and picks
up an address from that v-net and uses
DHCP methods to provide that to the
virtual machine when it's created so
this was one night to one 61.0 subnet
right so let's go ahead and go to Ranger
VM 200 here and see which address did it
pick up well as you can see it's 192 168
2.4 because this was the subject which
was 192 168 - so if we go back to our
networks here - just briefly refresh our
mind you can see the dev virtual network
actually had two subjects one was
wanders arrow this is where Ranger VM
100 is and one was 2.0 this is where
Ranger VM 200 is and guess what once you
come back here and go under the cloud
Ranger dev right now it actually shows
you under the resources that's these two
VMs which have these IDs and these are
the subnets they're using are using this
virtual network so it's a very quick way
to come to your virtual networks here
and see which VMs are using that
obviously cloud Ranger prod we have
nothing here under the dashboard as you
can see because we do not have any
virtual machine that's created with this
virtual network in mind so what I try to
demonstrate here right now is that if
you create quick create a virtual net
virtual machine and do not provide a V
net Microsoft Azure just picks up a
random address and puts it in there for
the internal IP address and you can see
just randomly picked up whatever and if
you actually provide one then it picks
up from that range for you and gives you
the DHCP address which the virtual
machine obviously picked up when it was
starting now let's connect to these
virtual machines and have some fun so
let's open the Ranger VM 100 and as you
can see that it's already connecting to
Ranger VM 100 cloud app net means
there's a Public DNS already as your
created for you and that's what we are
connected to with the RDP here and we
are going to do the same thing with the
Ranger VM 200 let you click on connect
here it's going to bring that RDP file
you can save it for my purpose I'm just
connecting to it directly and as you can
see this is Ranger VM 200 cloud wrapped
up in it
that's the public endpoint that is your
crepes for you and the DNS entry as well
so let's go to 100 here takes a little
time to start up again everything
meanwhile while this virtual machines
are starting I would go and run my
Microsoft Azure PowerShell because I
have promised you that everything we do
I'm going to show you as much as
possible on partial as well so the way
we'll do it is we're going to add the
zero account press enter we are on cloud
ranger blog that's our account they're
going to obviously put 0 here we're
connecting to the subscription it's
going to redirect us for credentials so
put my information here do not forget to
do this hopefully by now this is
becoming a practice for you to always
connect and find out the wording shows
up here to find out which subscription
you're connected to we are on free trial
so I know that whatever I'm doing I
would do it in the right place let's see
if my machines are up
okay they're coming up slowly okay
problems let's go to my ranger VM 100
here there is the thing I want to show
you here the local server I always want
to turn off something here so when I go
to my internet explorer I'm not going to
go crazy so I'm going to connect this to
off put this here
let's open up my partial window here as
you can see the internal IP are as
you're called this the D IP or dip our
internal IP is 192.168.0.1
and this is given to you by a zero this
is one that we got from the virtual
network the V net and this was the 1.0
subnet we picked up the 1.4 address so
when we come over here to an IP config
we can see it's given that address its
DHCP and we know this is DHCP because we
come over here and we are going to check
over here we're going to find that the
adapter that was created here does not
have any IP address so it's picked up
directly you do not need a DHCP server
here in your virtual networks in Azure
because as your utilizes its own DHCP
server to go connect to your subnet and
give you that information let's move to
our let here from a local server the
first thing I want to do here let's turn
this to off and off update this open
over here as you can see this one the
internal IP address 192 168 2.4 so if I
do IP config
time you can see it's 192 168 2.4 so I'm
going to do something really interesting
right now I know that these two belongs
to the same virtual network right so if
we go to network here here I know that
they are part of the same virtual
network but they are different subnets
one is subject web one is subnet FTB one
is with the range 1 8 1 6 8 1 0 and 1 is
2.0 so if I come over here and I try to
ping 192 168 dot-to-dot for this is
Ranger VM 100 I'm basically trying to
ping Ranger VM 200 from my range of RAM
100
let's see if I can reply uh-huh as you
can see my this VM from this subnet
cannot ping my other VM on the other
subnet
this is what isolation is all about this
subnet is isolated even though they are
part of the same virtual network they're
isolated from each other so they cannot
communicate with each other within this
two subnets but if you remember we did
talk about one thing which is that they
can access services from another one
house and that's two endpoints so let's
look at this real quick what are the
endpoints of this virtual machines so if
I go to my virtual machines here I go to
Ranger VM 100 my endpoints are for my
partial and my remote desktop and for my
Ranger VM 200 my endpoints are well I
added one more which was port 80 and
I'll show you why I added this endpoint
so Ranger VM 200 has port 80 as one of
the endpoints we just have to remember
that let's go to Ranger VM 200
I will go to server manager I am going
to go
and I'll show you how easy this is and
this is what makes Clark so interesting
is I'm going to go ahead and I'm going
to install I is so basically I'm
installing a web server on my ranger VM
200 some of you already might have
guessed what I'm trying to do here so
let's let this install here one rate
your VM 200 I'm going to go to arrange
your VM 100 here bring up the internet
explorer ask you later
so I moderate your beam 200 so this is
what we have done we have tried to ping
101 62.4 which is ranger vm 200 we were
not able to but on Ranger vm 200 I'm
going to install that web service and
let's see what happens okay it's
installing ok
I had paused the video and that
scalation is complete on ranger vm 200
so this is what I'm going to do if the
web server installed correctly on ranger
vm 200 I'm going to ring your VM 100
notice this this range of him 100 the
address for this is 101 success 1.4 I'm
going to go HTTP to one six eight dot
two dot for this is the Ranger VM to
hundreds web server guess what we can
come to the we can access the web
service or the web server and access the
web site from Ranger VM 200 from Ranger
VM 100 even though we were not able to
ping it they cannot communicate with
each other but they can talk to the
services from each other this is what
I'm trying to demonstrate so we were
able to connect access
service across the suburbs and these
services only come through the endpoints
so if this endpoint was not created here
we were we wouldn't have been able to
connect to the web service as you know
it uses parading so this is one of the
interesting demonstrations that wanted
to show you after creating this so there
are separate subnets cannot pay each
other but they can access the website
okay
now let's go back here I have opened up
my as your here what can we do so the
first thing I want to do over here is
one command that is gate as your V net
convict let's enter that command you can
see that it actually went and got an XML
configuration we can reveal that right
now so I looked you this so we can see
that it basically throws an XML file for
our entire configuration so you can see
that our address the space was 191 six
lips 0 0 but we had two subnets one was
subnet web one was subnet FTP this is a
very interesting information you can see
how things are there's not a whole lot
of command with virtual Nets but you can
do that so this is something you pick up
from here you go to cloud Ranger 100 and
compute - code
the wrong spot here network here you
create this network so this is the cloud
ranger depth so the one that we were
seeing over here is everything so let's
go and do this export button so we are
in the network's right now and click on
export free trial you see that it's
actually exporting out an XML file save
this file and open this file you'll see
that this is the same information that
we have got from here this to a similar
so you can export this XML file and
there's a lot that can be done with this
XML file so for example if you delete
this network you can actually import
this virtual network to that XML file
our next session is going to be how you
can get this XML file how you can import
this XML file as your backup of your
virtual network as well as how you can
edit this XML file and create virtual
networks through PowerShell by importing
those but I'm just showing you the
feature that you can get from there at
this point the other thing I wanted to
show you over here is as well let's do
it get as your VM and the way you get
this is a service name I know my service
name for Ranger VM 100 is range of VM
100 I'm going to put a name of my VM
here which is Ranger we have 101 again
and let's see what we can get so I want
all the information on Ranger VM 100 as
you can see the IP address over here is
192 168 1.4 so I know if I went that
data 200 here and it had its own cloud
service when we created it we'll see
that this one's
addresses one 92168 2.4 so these are
similar informations that you can get
from the management portal as well when
you go to convert your machines and
click those virtual machines and go
there does the interesting information
okay so we have ping this I have showed
you how they can access services so I
installed I is on Ranger VM 200 and Brad
your VM 100 was able to access that and
I created multiple nets over here so we
pretty much covered what we wanted to on
this first session creating networks is
the US and West us here so these are the
various things we have done ok so let's
go back to the slides and conclude this
session real quick so it's it became
almost an hour session because they were
just so much to cover and I wanted to
provide that demonstration though we
went quite a bit in hurry but feel free
to pause this video and make sure that
you go through each and every one of
those steps yourself then you will be
very comfortable in creating virtual
networks and editing them as well as
making several addresses spaces with
several virtual networks and subnets and
talk to each other obviously I've showed
you a single scenario where we created a
production network as well as the
development network this is something
similar to what you are probably doing
on your own premises virtualizations
environment that you created you create
one for your production you create one
for your development or multiple
development and it's similar in issuer
there are several differences and there
are some significant differences and as
the sessions pass through we will go
over that I do want to come back to this
little flow chart here that's taken
directly from Microsoft as yours website
the three solutions that we have talked
about that you could have in no virtual
network scenario you could have a cloud
only virtual net stereo like the one we
showed in the demonstration right now as
well as cross Prime
virtual network this flow chart here
shows you that do you even need a
virtual network and what kind of virtual
network do you need this could be
important for several reasons you
remember in the demonstration the first
virtual machine that we created it did
not even have a virtual network
associated with it and as your took care
of everything
so for example you wanted to run a web
server on there you could have just run
a web server and as far as your your
end-users were concerned they could just
go to the public DNS and they could
accesses a web server so that's a
scenario where you would not need a
virtual network create it for you but
that's very rare I mean how many people
these days have a website which is all
static web pages and not talking to any
in the databases or any back-end server
it's it's almost quite rare these days
so chances are you will probably always
create a virtual network and it's always
a good practice because it provides you
more control on the virtual network that
you'll create the IP addresses as you
have seen as you're went and got those
DHCP addresses from the virtual networks
that you have created so it's important
that those are created but however feel
free to look into this and see how it
can help you decide when you need a
virtual network or not and it's
important somewhat in your planning even
when you're working in your production
not just your exam point of view that
you look into something like this and
then plan out how your networks are
designed and before we conclude this
it's I just want to reiterate the
planning is so important while this
seemed to like it was very easy and it's
it almost makes you
I don't know lack of terms it almost
makes you trigger-happy to just go and
create as many virtual networks as you
want and whatever way you want it but do
not forget that several considerations
come in for your planning point of view
when you are going to connect this to
your own premises or you want go to
learn a large organization with a lot of
networks and a lot of isolations are
required there will be a significant
amount of planning that has
be done before you go and start creating
those but for your lab environment go
crazy play with as many virtual networks
you can create them create virtual
machines on these networks ping each
other create web services or other
services and see how they talk to each
other and how isolation works and that
pretty much concludes our dispersed part
like I said there's going to be multiple
parts to virtual Windows Azure virtual
networking and we will be going through
all those scenarios on the first light
that we had shown to go through the exam
details all right
so as usual our training site URL is
that cloud ranger net /a zero training
our YouTube channel is at forward slash
cloud Ranger Network we are also on
Twitter at the cloud Ranger blog there's
a Google+ site as well you can email me
at Shawn at cloud Ranger net if you have
any specific question but however as
usual I would appreciate it if you have
any questions
you put that on comments on the site or
as well as the youtube comment section
because that's good for everybody else
as well because they might have similar
questions feel free to like this video
on youtube do subscribe to the channel
as well this helps a lot and it provides
as an encouragement and thank you for
viewing and I'll be seeing you in the
next sessions