Microsoft Azure Training - [10] Azure Virtual Networks - Part 4 - VIP;DIP & PIP (Exam 70-533) Video Lecture | Microsoft Azure: A-Z Guide - Database Management

hi everyone this is Shauna spawn from
the cloud Ranger and you are viewing the
Microsoft Azure training so today is
going to be the part 4 of as your
virtual networks and we are going to
talk about VIP VIP and p IP or the VIP
dip and pip these are the different IP
addresses that are available to you from
your Microsoft Azure for different
reasons that we'll get into in details
some of this you have already looked at
but we have not yet gone into too many
too much details of this but we'll be
doing that right now in this session ok
so the first one is the VIP or the
virtual IP address so traditionally that
addressing that we are familiar with on
premise is something like this if you
have a public domain name for example
cloud range of date that's my domain
name that would have a public DNS entry
for a public IP address so for example
something like this 61 195 120 495 that
would be the public IP address so cloud
range of net would trance could
translate or could resolve to this
public IP address and this public
address would be somewhere assigned to
the outside interface of your firewall
and your firewall is going to do some
sort of a netting network address
translation and forward it to your web
server for example in my example here is
web app 100 which has also a private IP
address this private IP address is
assigned to your virtual machine or your
server and that is your public IP
address so moving on the way this works
in Azure and this is what we have been
doing so far is that every time we
create a virtual machine if you remember
from the previous sessions we mentioned
that it creates a cloud service or it
should be in a contained in a cloud
service and this cloud service could
have multiple virtual
jeans in there not just one to one but
it should be a one-to-many relationship
here so what happens is every cloud
service that is created does have a
public IP address so something like 61
195 120 495 would be assigned to this
cloud service and when the user will go
to for example in the cloud range at net
Microsoft Azure will provide the cloud
services DNS which would be something
like this web app service 100 just
because that was the cloud service named
cloud app net so anytime you see that
address you you will know that this
address will actually be resolving to a
public address that is assigned to a
cloud service so how people access this
is that they go to this public DNS and
it takes you to the cloud service the
cloud service will know the endpoints on
this virtual machine and let you through
based on the port numbers so there will
be a pad or port address translation for
from the cloud service to the virtual
machine so that's how the addressing has
been taking place so far in all our
sessions whenever we created a virtual
machine and we try to connect through it
too with RDP so we'll RDP to this
address with a specific port number
which will hit the cloud service and
take you to the virtual machine so
that's basically the fit bar fit would
be the IP address the public IP address
that's assigned to the cloud the thing
to remember here for both exam and for
your production work is that your VIP is
not assigned to a virtual machine the
VIP or the virtual IP the public IP
address is always assigned to the cloud
service so let's talk about VIP a little
bit so VIP is a public IP address VIP is
created when the cloud service is
created and resources are allocated to
it so every time you create a cloud
service it's not going to create a bit
for you what it will what it will do is
create a v for you when you
signe resources or allocate resources to
it means you create a cloud service that
you connected vm in it and that's when
this cloud service will end up getting a
public IP address this is something
that's provided by Microsoft this public
IP addresses and it's randomly picked
based on the region you're creating the
cloud service at so if you create a
cloud service in West USA you will have
a different range of IP addresses that
as your will provide to you if you
create one in East that would be a
different IP address range it will go
through that as well
the VM see the cloud service can be
configured to be accepted by the VIPs
and assigned port numbers so for example
when we are already paying to the
virtual machine we are already paying to
the cloud rep net service named cloud at
that net that is your public IP address
of the VIP and it's followed by a port
number to specifically go to a certain
machine so if you have five virtual
machines in one cloud service you will
still use the same DNS your service name
clarinet but you change the port number
so there will be a port translation that
will take you to the specific virtual
machines so this is what will happen in
this scenario in this diagram you can
see there's only one cloud service but
with two virtual machines so still the
user would be connecting to web app
service 100 cloud app net however it
will have a different port sign to each
of these virtual machines and based on
that port here if the cloud service will
know which virtual machine to send you
to obviously you can have one-to-one
relationship so instead of having one
cloud service containing those both
virtual machines you can have a cloud
service and a virtual machine a cloud
service and a virtual machine and you'd
basically have different addresses to
correct at that time so let's talk about
the default behavior of a verb if it is
lost when a VM is stopped or Delocated
so we know when a vapers created that's
when the cloud service is created
however this VIP will be lost if the
virtual machine has been shut down
from the azure portal the other time
this vape is lost is also when the cloud
service is deleted so if you go and
delete a cloud service since the vape is
associated to a cloud service you can
just delete it
this is exactly what that makes web
address very unpredictable so what does
that mean it means that if you have a
public IP address assigned to a cloud
and for some reason if it's a lab or if
it is just an environment that you do
not care about and you just want to get
rid of it what it will do is you'll lose
that IP address that was assigned to you
by US Europe for the VIP and this may
have firewall implications for example
if you have a virtual machine that
connects to another organization
automated connection or whatever to
upload a file or anything else
maybe that organization only allows a
certain IP public IP to connect and they
have firewall rules to actually only
allow certain IP addresses to connect to
their systems as a security precaution
so if you have a lab or if you have a
system that only has a VIP but only
turns on it at a specific time or it's a
lab environment so you don't care and
you create the virtual machine as many
times and you want to connect to that
other organization they will only
remember the first time you give them
the VIP they will not be going in and
changing their firewall rules with the
public IP address you keep giving them
so there are implications of having a
VIP address which is not set static to
the cloud service so the other thing
that will be affecting with a regular
VIP is that the DNS so Microsoft gives
you your service named cloud app named
cloud wrap net at the NS name Public DNS
name for you when it creates the VIP so
you can use that DNS cloud F net DNS to
connect to your services and do whatever
however for many organizations that's
not going to work they will want their
own DNS
to collect or to go to their services
for example their website you want your
domain net or domain calm rather than
Microsoft service named cloud up that
net so ideally what you do have you do
is have an e record - in your DNS to
point to that IP address however you
cannot do an a record in this case
because since your IP address changes
every time you stop or shut down or
recreate the virtual machine what you'll
have to do is not create an e record but
a cname to your service cloud rep net to
make sure that that stays consistent
rather than putting on a record that
keeps changing so what is the solution
of all these problems of this default
behavior reserved there so you reserve
the public IP address that's assigned to
a cloud
so rather than Microsoft assigning
random ones you make sure the Microsoft
still assigns them but it's two signs
the same verb every time you create or
you turn on that virtual machine which
is associated with them so what we are
going to do is talk about reserved IP
right now the way you do that is that a
reserved VAP or reserved IP will be
associated to a cloud service so you put
a static address to the cloud service
and it removes all the limitations of
the VIP but however it has its own
limitations as well
the first reservation have been a issue
that it has is that the existing VAP
cannot be converted to a reserved them
so if you have had already a virtual
machine that's up and running and
there's a VAP associated with it you
will not be able to make that IP address
aesthetic and the next one is that that
the VMS must be created with the Viv's
reserved first so once again if you
already have a VIP and it already has a
everything set up you cannot go and just
create I mean just assign the VIP to a
new VIP - or a static VIP to the virtual
machine the only way you can create a
static VIP is actually
create it and assign it while you create
the virtual machine so if you already
have a virtual machine you cannot assign
a static zip to it and this may make
sense
you cannot allocate more than one
reserved verb to a cloud service so you
cannot have like five different IP
addresses that are all pointing to cloud
services for most people this will not
be an issue but I've heard that there
are times when one single service is
required to have multiple IP address for
whatever reasons and of course you
cannot do this from the management
portal you have to use the PowerShell to
do this so when you create the virtual
machine it has to be created through
PowerShell and this is what brings me to
a tricky place right now because we have
not really gone into a session where we
talked about creating virtual machines
so so far all the virtual machines that
we have created
we're just created to demonstrate other
concepts but in this session we will
talk about creating virtual machines
with PowerShell I do not want you to get
completely boggled by you know the
details of how the virtual machine is
going to be created I'm just going to
show the specific parts of a script
which actually reflects setting a static
fit so when in the future sessions you
learned about completely creating
virtual machines with scripts and
commandlets and stuff like that you may
be able to revisit the script and look
at it I will have this script actually
for you to download on the blog website
and on the youtube description i will
have a link directly to go to that
script the next limitation of reserved
VIP is that every subscription can have
up to 20 reserved verbs and it might
work for most people once again
different organizations have different
requirements so they might require one
subscription have more than 20 all you
have to do is call up as your support
it's free to get more than 20 you can
just ask them they'll probably just ask
for an explanation why you need more IP
addresses and that will be it so these
are the two commandlets that we will be
using to connect to the reserved verb or
to create the reserved verb so I'm not
going to spend so much time on this like
right now I'm going to go to the
demonstration and show you a couple of
things and we'll come back to the slides
okay so we are on my client computer
which is already connecting to my
subscription and I actually do have a
virtual machine already created here to
save some time this is just a basic
virtual machine there's no Venus or
anything created I created this through
a quick create so which is by basically
going to new compute virtual machines
and do a quick create and put in all the
information here so that's how this
virtual machine was created so let's go
and this is up and running right now so
let's go ahead and click on this virtual
machine see range your VM 100 I want to
scroll down over here and show you the
VIP or the virtual IP address and this
is the IP address that as you're
assigned to the cloud service it's
called the public virtual IP or web
address and you can see this is the
public address this internal IP address
it does not look like the private IP
ranges the standard IP ranges like 192
168 or 172 or 10 dot whatever but this
is one created by given by Azure as well
for the internal IP address of the VM
you have to understand like I mentioned
that this public IP address web is not
assigned to the virtual machine even
though we are coming into the virtual
machine and looking at this address this
is actually assigned to the cloud
service that was created while this
virtual machine was created so as we
know that the VIP is actually the cloud
services IP address and if you go to the
cloud services details over here you can
actually see that it does not directly
give you the IP address for it I mean it
does give you the data the IP address
for it over here but it also shows you
the endpoints this cloud services allows
on the virtual machine which is this one
so this is one there's a couple of spots
you can actually go and see the VIP or
the virtual IP address so there's a nice
little document that you can find online
the wire you can actually go and look at
all the ranges of all public IP
addresses that are there for different
location or region so for example my
location is East us two and you can go
to this URL
over here so you can pause the video and
copy this up for yourself so what this
will do if you go to this link is that
it will give you a like a XML document
which you can download and look at all
the IP ranges so I have already done
that
I have create I have downloaded the XML
file here so if you go and look at this
open up this file in notepad you will
see that it gives the region name or the
location name and all the ranges of
public IP addresses and their subnet
that are available on this IP range on
this region so for example if we go to
our virtual machine we are in East us
too
so if you look at the east us - region
you will see that this is where the IP
address is taken from so for example
this one thirty seven one one six so
let's go to East us - we are looking for
the range one thirty seven one one six
so it's one thirty seven one one six you
can see these are the two ones 82 so it
probably took from one of the ranges
over here based on the subnetting you
should be able to find out which one it
went to one three zero one one six
eighty two thirty thirty six so you can
obviously go to your region wherever you
are located and you can find out where
the range you took that from so this is
a neat little document to have handy and
microsoft obviously keeps changing that
as they add more stuff or remove stuff
from there so this is where you can
check that and what I'm going to
introduce you to today is also look at
information of the azure VM directly
from PowerShell so the way you do that
is pass this command gate as your VM so
in your subscription if you do get as
your VM and you press Enter
it will actually show you the virtual
machine that is running so this is the
service name the cloud service name and
this is the name of the virtual machine
which is named and says that's already
grown so the way you get information for
this a specific virtual machine is to
actually write the switch of
here see Ranger VM 100 that's my service
name and then the name is si Ranger VM
100 or whatever virtual machine name you
put in there and if you just do this
much I press ENTER it will give you all
the details of the virtual machine you
can see the details like the name of the
virtual machine the IP address this is
the local IP address that's assigned to
your virtual machine however you look
over here the public IP addresses is
empty and this actually should make
sense because there's no public IP
address directly attached to this VM it
gets its IP public IP address from the
cloud service so you cannot look at the
VAP information but just passing this
command line you have to add something
else to it so what we are going to do is
we would take this command and type it
to get as your input you remember the
endpoints the way we get the endpoints
is come to the VM and go to the
endpoints here and we should see that by
default two endpoints are created here
so what do we do over here is get as
your endpoint and press Enter
so here we can see that these are the
two our endpoints we had 5 9 8 6 so 5 9
8 6 here and over here we have six to
nine oh eight six to nine oh eight which
is actually taking to the local port
3389
this is the one we use for remote
desktop this is the one we used for a
partial however looking at this
information you can actually see the VIP
which is obviously same for this two
ports because they're the same virtual
machine coming to the same cloud service
so this is one way to also locate the
bit I usually just go over here
depending on what I'm trying to do and
just click on this and look at the VIP
that's assigned to me so technically it
should be the same so and this all
information are going to be the same
dessert various ways actually to locate
the VIP so let's go ahead and we know
now that this VIP address is a temporary
one and let's actually start to look if
we can actually do a demonstration of
that so we know that this is our vamp
one thirty seven one one six dark thirty
six so I'm going to show the limitation
of event what I'm going to do is I'm
going to turn off this virtual machine
from here then shut it down and
deallocate it and based on our based on
our limitations of it the next time I
turn on this virtual machine it will not
have the same web and the web would
actually change your your DNS name which
is C range your VM 100 dot cloud app
dotnet which is actually your cloud
service address will still remain the
same it just that the DNS entry to the
IP address will change so let's go ahead
and shut down this virtual machine and
when you do that it actually tells you
that if you continue the IP addresses
that were assigned to this virtual
machine will be released so this is for
both the VIP and the internal IP address
as well so as you're basically just goes
and releases all those IP addresses to
their IP pool so we'll click YES on this
one and I'm going to pause the video
till this virtual machine completely
stops okay so the VM completely stopped
now you can look at the status is
stopped and de-allocated means all the
IP addresses have been de located so
we're going to go ahead and turn on this
virtual machine once again if you come
inside you look that all this
information is no longer there because
as you're went ahead and completely
de-allocated this virtual machine
everything else is in there though so
let's go ahead and start the virtual
machine okay so the virtual machine has
started and by the way I do pause this
videos for all this activities to take
place in the background a virtual
machine could sometimes think okay even
I've seen 10 minutes to start so if
you're following along you might have to
wait for the virtual machine to really
start and get into a running State so
anyway so what we were trying to prove
here is that the last time this was
running the VIP was 137 one-one 680 236
let's look at this and this is going to
prove the concept of the limitations is
that if you see it's 137 168
d12 55 so obviously the web address has
changed from what it was previously
right after the virtual machine was
restarted after it was stopped in a
de-allocated mode so that's one thing I
wanted to demonstrate and obviously when
you go to see range of 100 cloud Abnett
so if we come over here for example and
do something like this ping si Ranger VM
103rd cloud Abnett you can see that it's
not going to be able to ping but it will
resolve to that IP address over here so
Microsoft does this DNS Public DNS bit
for you already when you create the
cloud service and put a virtual machine
in there ok so let's go ahead and talk
about reserving a VIP a virtual IP the
way we do this is let's clear the screen
first you have to reserve or you have to
create the reserved vamp
you cannot just assign VIP to a already
created virtual machine so we will not
be able to create a I'm going to assign
a VIP to the virtual machine that's
already running we'll have to create a
new virtual machine with the VIP that we
will create over here now the command
link that you will do so let's actually
see if we actually have any
reserved VIP right now or you know what
maybe I'll just create one first and
then we'll check that so the way you
create this the command let is new as
your reserved IP you have to give it a
name like everything else - in in Europe
so if there will have to be a reserved
name uh I don't know I'll just call it
my reserved IP and ok and the day it has
to have a label so we'll put a label in
there so we'll do a reserved label it's
just another identifier for this IP
address the location
you have to always and you have to
always like provide a location so
Microsoft Azure knows where to go and
pull that public IP address from like I
mentioned when I was opening the file
that you know all the locations up
separate ranges so my range over here
will be us east - that's the command
that you have to put in there for
reserving an IP address and I need to
mention this right now that you do not
provide the public IP address all you do
is provide the location Microsoft goes
and picks one public IP address based on
the location and the ranges it has in
the location so let's hit enter on that
one took about ten seconds for this to
get it so we have a reserved IP right
now it's not doing anything but it just
went to reserved that IP so the way to
actually look at which IP address was
reserved is to is to run the command let
get a zero if I can type yet is your
reserved IP very simple to remember if
you click enter on that you can see that
this was the reserved IP name my
reserved IP name and that's the address
that's what as your winter picked up
based on the region that you had on the
location you provided is it in use false
means this is just an IP that was
reserved but right now it's not assigned
to anything and that's all there is to
as reserve an IP address so what what do
you do at this point is take this IP
address and create a virtual machine
through PowerShell and you would
actually point to the my reserved IP to
do that so I'm not going to use this
reserved IP we're just going to leave it
alone I actually do have a script it's
it's quite a long script so what this
does is that it will go and it will it
will go and it will create a new
reserved write the address and it will
also create the virtual machine week
that reserved IP address so we'll be not
using the one we have
creator Audrey it's going to be new one
so I'm not going to go through all the
details of how this virtual machine is
created because you really don't need to
at this point just a couple of things
the variables are right here you need to
make sure that for your environment you
change them like whatever the virtual
machine name you want and things like
that
um I'm creating a store where the
virtual machine will be stored this is
my cloud service name so essentially
this will become web app service 100
cloud app net my virtual machines name
is just web app 100 credentials
everything over here so just like my
previous command that we hereby reserved
IP name over here was my reserved IP so
I'm not going to call this my reserved
IP I'll just call this my new reserved
IP just keep it consistent here and what
it will do is that it will take this and
it is going to put that in this command
over here this new as your reserved IP
and you can see that this command list
will look familiar right now with this
one over here except that we are using
variables to pass that along so that's
all the script is doing it's creating a
reserved IP first for you as well and
here if you look at the new as your VM
so this is how you actually create a
virtual machine in PowerShell don't
worry about what we are doing with this
command live here all I want to say is
that when you are going to use a
reserved IP you're going to just provide
a switch - reserved IP name with the
reserved IP name variable over here
which is the one that we had created
earlier at this location and that's all
there is to it so I'm going to run this
a script and it takes some time because
obviously it's going to run the script
to create the virtual machine and it
will do all of that so it will take some
time to do that so let's go ahead and
run that
I'm going to just I think it's good do I
think I messed up over here I just went
to read that single line command read
the whole script so just be right back
anyway so I went offline and create and
just cleared all the messes I have
created with running that script that
way so the way you would run the entire
script would be this button over here
brought a script rather than the run
selection so let's go ahead and run the
script it's a quite a verbal script so
it actually tells you what it is doing
it when it's done so I'm going to run
this entire script and lake let
everything be created for us and come
back what everything is created
okay that took about I don't know about
eleven minutes for the entire script to
run and it created a new virtual machine
web app 100 so if you can go over here
we can see that it created these new
virtual machine and it used the static
IP address to actually create the
virtual machine so let's go ahead and
run the command get as your reserved IP
and we should see at this point that
there are two one was the my reserved IP
which we created earlier but look now it
has the my new reserved IP it has a new
IP address obviously and looks like it's
assigned to a service named web app
service and the deployment which is the
VM and it's in use it's true so it's
actually created the whole thing here
and it is 153 dot 171 so what we can do
is we can go over here and we can check
that
that's the IP address so how do we know
that this is going to be static well the
first thing we can run this command late
and we can see that it is going to be
associated with this web service and
it's a static IP address because it's
reserved so let's go back over here and
we're going to prove this that's a
static so if you remember the limitation
that if we turn off this virtual machine
it is supposed to lose that IP address
so we're going to come back after
stopping this and restarting this
virtual machine so I'm going to go
offline and stop this and again go start
this and we'll come back and see that it
still has the reserved IP address okay
the VMs is stopped and now let's go
ahead and start it again
okay the virtual machine is running
right now so let's go ahead and get into
the virtual machine here and what I want
to show is the VIP so here the VIP is 23
1 1 153 171 and you can see over here 23
101 153 171 so even if the virtual
machine was reallocated and it stayed
there and we turn it back on just
because it was associated with the
reserved IP it went and got that IP
address and not a new one this
immediately kind of get rids get gets
rid of all the limitations if it
actually has so the last thing we want
to do over here is how to remove an
event so we will try to remove the one
we had created earlier and the command
late for that is remove as your reserved
IP and I press tab usually to do the
auto completion so what do you need over
here is the reserved IP name so we take
this and that's all we put over there
and technically that all we should have
to do it confirms let it delete
all right it does take like about few
seconds for that to happen so let's do
get as you're typing somewhere else get
this your reserved IP we should just see
one entry in there which is the new
reserved IPS we went ahead and removed
this one okay so let's go back to our
slides that's all I had for demo for now
so going to our slides these are the two
commandlets
we were using so far new as your
reserved IP and we put reserved them and
they label the location and that's what
will reserve the IP for you and while
creating the VM just remember and return
it once again that you only can have a
VM associate itself with a reserved VIP
is when it's being created when you're
creating the new virtual machine you
have to make sure that you have the
reserved IP name switch with the
reserved IP name for this to happen okay
so that's there as far as the VIP is
concerned or the virtual public IP
address and next we are going to move
into dip or the internal IP address and
this is a little bit easier from the VIP
because dip is the IP address which we
all are aware of it's nothing but the
internal IP ID is your virtual machine
gets so this one is not that bad of a
deal because we have looked into this
many times before on-premise so let's
get started
this is the same diagram we had earlier
when we are talking about VIP but we dip
we are talking about this part of this
diagram where the private address that's
associated with the virtual machine so
let's talk about dip a little bit more
in details so we know the dip is a
private IP address for a virtual machine
so anytime you turn on a virtual machine
it gets a private IP address it is sort
of automatically provided by a0 so
anytime you spin a virtual machine with
a quick create or whatsoever you'll see
that the virtual machine already has an
internal IP address
so the contrast between this and an on
premise would be that on premise if you
spin up a virtual machine there would be
a DHCP virtual machine or any server
let's talk about any server you it would
turn itself on and it will go and it
will go and look for a DHCP server and
get an IP address from a scope in your
DHCP server in vmm or VMware now you
have that option where you don't have to
have a DHCP server but your virtual
machine manager will provide you an IP
address from an IP pool and that's what
exactly is happening in Azure
except the fact that you do not have any
control over it so Microsoft will give
you a random IP address it thinks it is
it is free and give it to your virtual
machine as an internal IP address and
you do not have to do any specific
configuration for this you can do a
quick great VM and you'll get now the
next thing is if you actually have a
virtual network and you are creating a
virtual machine and you are specifying
the virtual network as your will go and
get an IP address from the v-net range
so it's not going to give you a random
internal IP address since you have
mentioned that you want to use this
vennett it will actually assign an IP
address from that Vinit and we'll go
through that in our demonstration to
show that the next thing next thing is
just like VIP dip can also save the
static like this is no different from
our on premise physical server where you
know you can not configure anything and
it will get from your DHCP server or
from the IP pool full pull from the VM M
or you can assign a static IP address
and internal like 192 168 1 dot 100 for
example you can put a static IP address
and the same is possible with dip as
well ok so let's go in our
computer a little bit and go through a
little bit of a demonstration of what
I'm actually talking about so back to
our client computer as you can see I
already have two virtual machines made
over here Syrian JVM 100 and C Ranger VM
200 the difference between these two is
that this one C Ranger VM 100 was
created as a quick grade of a virtual
machine so I did not specify anything
except the name the username password
and the location which is east us 2 and
C Ranger VM 200 I actually created this
with a virtual network specified so next
look at the virtual network here you can
see it's called Ranger net and if I go
into details and I go to configure you
can actually see the subnet over here
that's created 192 168 1 0 so the
difference between these two is if we go
to C Ranger VM 100 we can see that
there's an internal IP address this is
the dip d IP which is provided by s0
it's a random IP address 10.2 38 108 not
104 it's internal to the virtual machine
so if you do an IP config this is the
address you are going to see
however in C Ranger VM 200 this one was
the one where we have specified the
v-net so having provided the Vinit
information while creating this you can
see that the IP address is a little
different it's 192 168 1 dot 4 so what
happened is as your figured out that
since I specified the Vinit it's going
to take the IP range from the V Nets IP
range so that's the two difference
between these two virtual machines one
is provided by zero one is providing
internally in a production environment
depending on how your requirements are
most of the time you will probably
create a virtual machine and specify a
virtual network to it
it keeps things more organized it keeps
the subnet consistent so you understand
by looking at the subnet or the IP
address which virtual network your IP or
your virtual machine belongs to so
chances are this is the option you will
take most likely and we have that we
have done this many many times
so we go to a from gallery and what we
did was just to show you once again is
that you would create a random virtual
machine I'm just putting a name over
here I'm not good really create it so
this is the information you definitely
need to put properly and what you do
over here is this is where in the region
infinity over here virtual network this
is how you specify that you need the
virtual machine to go out with the
vinner and you have done many many times
this already in this series for virtual
networks so I'm assuming that you
already know how to do this quite
properly so those are the two things I
wanted to demonstrate over here for now
the other thing I want to show you over
here is that we we will connect one of
these virtual machines here and I'm
going to show how you see from the
virtual machine the IP address and how
it's consistent okay so we have our two
paid into the server so as soon as you
can see over here at the BG info it
shows the internal IP address 192 168
1.4 so that is your dip so that is the
information that we had over here 192
168 1.4 here so you can see that in the
internal IP address over here at the
public IP address you can see 23 101 148
25 that's actually the VIP so if you go
and open up a console here and do IP
config you will see that 192 168 1.4
shows up over here that's also your
internal IP address so so far so good
now the limitation of this similar to
VIP if you have a virtual machine and it
has an internal IP address if you shut
this down from the total and you go and
restart it the internal IP address will
change so this is like DHCP it can go
and pick up any IP address that's
available to you from your V net or
which as Europe provides to you so you
have to remember that
because there are times when you want
your virtual machine to always have a
static IP address and not totally depend
on a dhcp in fact when we were doing on
premises of stuff I've rarely seen it
server even have a DHCP address it's
always a static IP address now this is a
little tricky when Microsoft initially
came up with a 0 they did not have a way
to put internal IP address to be static
for your virtual machines what the
instead did was they said that as long
as you do not shut down and completely
shut down and deallocate your virtual
machine it will have an infinite lease
from your DHCP as your DHCP so what will
that do if you go and shutdown the
virtual machine from here rather than
shutting the this down completely and
deallocating from here as long as the
virtual machine was shut down and
restarted that way you would always have
the same IP address given back to you so
it almost simulates a static IP address
because you're getting an infinite lease
and you're getting that but you have to
remember that as your is an usage based
billing service so what happens is that
if you just go and turn off your virtual
machine from here you are still going to
have all the resources associated with
that connected to that virtual machine
and you will still be charged the only
way you can actually have a virtual
machine sit over here and not be charged
for it is go to shutdown and make sure
that you stop and deallocate this
virtual machine however you lose all
your IP addresses not only your VIP but
also your dip which is your internal IP
and it actually mentions this over here
so what did that do well infinitely it
was fine but I do not want to get
charged for this when I'm at home at
night and this is my lab environment so
most likely out go and shut it down from
here but when I turn them back on
I lose the IP address so what happens if
the
the domain controller what happens if
this is like a bunch of virtual machines
where there were applications being run
on that that dependent that were
dependent on IP addresses you'll totally
get messed up so what you'd have to do
is that shut down from here so there is
not much compute bill but still for the
IP addresses for everything else
you'll be billed for and they'll still
be certain charges so this did not fly
very well and it also created a couple
of confusions so the best practice for
example a domain controller or DNS
server is making sure the server has a
static IP address and a lot of people
had a little bit confusion they were
like well infinities but it still it's a
lease what happens to my domain
controller so this is actually a little
funny because we would go to as yours
documentation on MSDN and they would
clearly mention that hey we know that
the best practice is to have a static IP
address but don't worry about it
just put your regular just just do what
you're doing in azure and as long as you
have infinite leas you'll be fine so
when Microsoft changed that and added
the capability of putting a static IP
address on this virtual machine what
they ended up doing is they went and
updated the document and said oh no
don't worry about it you should always
follow the best practices and make sure
your turbine controller gets a static IP
address so that's going to be the next
part of this where I show you how to add
a static IP address to your already
created virtual machine unlike VIP where
you have to create a virtual machine
with a static VIP on a dip or internal
IP address you can assign a static IP
address while the virtual machine has
already been created so since we already
created this virtual machine we will not
recreate that now you might say that hey
Sean you know what that's almost natural
I already have a virtual machine all I'm
going to do is come over here go to open
network settings go to my adapter change
adapter settings right click on this
properties now this is what we naturally
do I will come over here use the
following IP address and I'll create
that static IP address over here
no no that's not how you set an static
IP address to a virtual machine in a
zero in a zero what you'll have to do is
assign a static IP address just like
that and then create the relationship
between your virtual machine and that
static IP address outside of this
virtual machine so at no point in as
your and remember this carefully at no
point in as your ever you'll have to
come over here and use this option to
put IP addresses doesn't matter it's
DHCP or not or static or not you do not
do this over here so you will be doing
that in like you might have guests in
PowerShell that's the only way to do
that and the way you do that I do have
the command layers but I do have to show
you something first
which is let's get information on my
virtual machines so get as your VM now I
have two virtual machines so I have to
be afterwards show you the one that we
are kind of using right now so we know
that that's going to be the service name
first see Ranger VM 200 that's the one I
want to show you and then the name of
the VM which is just name and is the
same for my case so as you know that
your service name and your VM name can
be separate so that's why it requires
you to mention both but in our case it's
the same let's press ENTER so we will
see our eternal IP address here 192 168
1.4 this is how you'll see that so how
do you in on-premise these days you guys
assign a static IP address you know what
the first thing I do is out just go do a
ping 192 168 1 dot whatever and you know
what you can still do that from here
let's go to the virtual machine 192 ping
192 168 dot one dot 100 I would see if
this IP is being used or not and that's
fine you know what it cannot reach there
because it's because I've not assigned
it to anything else so that's one quick
dirty way of finding out if you have
that IP address set as static or not as
your takes it to the next level
so it actually has a command to check if
you have a static IP address assigned to
a virtual machine on
so the way you do that is test as your
static v-net IP video - IP here means
the eternal IP and then you put the V
net name and I think our name was C
Ranger net that's the name of your V net
and you check for the IP address so you
put IP address new to 192 168 1 dot 100
let me check if this IP address has been
given to anywhere else or not and I just
found out
that's not my V net name I think it's
ranger net let's try that again
so now a 0 is going and seeing through
our V net that if this was assigned to
everybody else or not as as you can see
it says is available true means this has
not been assigned to anybody else so we
know now that we can assign this address
to somebody else so how do you do that
well like before let's go get the
virtual machine so we know gate as your
VM service name we'll get the virtual
machine here put a pipe to that and do
set as your static v-net IP and put the
IP address here so the IP address will
be 192 168 dot one dot 100 that's the
one we want and we are also going to
pipe this to the update sorry the update
is your VM over here as well so what
this will do is it finds the virtual
machine which is in our case is 200 and
we know the 200 of internal IP address
was 192 168 1.4 so we are changing that
to a static V net right now a static IP
address with 192 168 1 dot 100 let's go
ahead and press Enter on this and as you
know this will take a little bit of time
because the update as your VM actually
restarts the virtual machine so yes it
will restart the virtual machine while
the static IP is being said ok so let's
enter a hit enter on that
okay and that succeeded so update as
your VM and you can see it has succeeded
obviously my RDP session has crashed
here because it was restarting that so
I've closed that let's go ahead and RDP
to it again and you can see that it's
still starting and it has not completed
even though the command has completed
and it went and did the update VM
okay so we are logging into the virtual
machine
and we can see the internal IP has been
changed to 192 168 1 . 100 so if we go
over here and do an IP config we can see
it's changed to 192 168 1 . 100 and
similarly if we come over here and go
click on this one we'll see that this is
192 168 1 . 100 so if you come over here
run this command the partial command to
get the information on this will see
that it's 192 168 1 . 100 okay now this
is the thing you might look at and this
is what I was curious about what happens
we know that we created this as an
aesthetic IP address just because we did
this partial command figure but where is
this as a static IP address if you come
over here and you click on this
properties you'll find out that there is
nothing said over here so you cannot go
to a virtual machine and look at the
virtual machine and see if it's an
static IP address or not because the way
as your works is a lot of configuration
is provided to a virtual machine when it
starts up so just because we have
provided this command over here we have
ran this command over here as your knows
that anytime this virtual machine is
turned on it needs to apply a static IP
address externally to the virtual
machine and that's how it has got that
so that's the way you put or that's the
way you add a dip on an internal IP
address to a virtual machine in s0 and
the way you remove this IP address a
static IP address and make it go to DHCP
is same as adding the same as adding the
virtual Medinah static IP address to the
virtual machine but the command this
time is going to be remove as your
static v-net IP that's it and you do
update as your p.m.
that would remove the static IP address
from this virtual machine and when it
restarts using the updated sir VM it
will actually go to a DHCP mode and it
will pick up the IP address randomly
from the virtual network and as you will
do that for you
so as you can see there was no DHCP
involved in this and Azure does that
DHCP portion for you we do not have any
DHCP server we did not even configure it
anywhere so it's a very nice thing to
have so back to our slides what we have
done here is like we checked first if an
internal IP address or tip was available
to the test as your static vennett IP
command let then we added we got a
virtual machine and added a static IP
address which set as your static v-net
IP address and we went and remove that
with removed a zero static Vinit IP so
just like VIP dip also has limitations
and that limitation is taken care of
with this static IP addressing it's a
very important part of the exam as well
as well as for production it's important
that we do things as close to one
premises for the various microsoft
product best practices okay so that
concludes our tip and the last one so we
did dip dip and dip now we are going to
go and do pic which is the instance
level public IP address so pip instance
level public IP address I have no idea
how Microsoft came up with this VIP dip
and pip because as you can see Pape is
instance level public IP address so I
don't know pip for whatever reason so
looking at our diagram here you can see
that's so far we have talked about the
public IP address called VIP which is
associated with the cloud service and we
talked about dip which is the internal
IP address so what exactly is PIP and
why do we even need it so this is
actually an IP address a public IP
address that can be assigned to a
virtual machine so so far we have been
accessing a virtual machine with the
clouds IP address but now for whatever
reason and let's get into the reasons a
little bit later you might need
public IP address associated directly to
a virtual machine you have to remember
the PIP does not take place a VIP it's
an additional IP address so you still
have the same requirements you still
need to make a virtual machine in a
cloud service so you'll already have the
VIP and you'll already have the dip but
people be an additional IP address
that's associated so now you will have
three IP addresses that are associated
with the virtual machine each
subscription can have to have can have
up to five pips and if for some reason
you need more you have to call Microsoft
and using pip allows external traffic to
hit virtual machine on any port so this
is very important for both production
and exam point of view you have to
remember that if virtual IP address
which was the VIP is a cloud IPS and the
way you are getting into that virtual
machine was by specifying a specific
port in the endpoint so when you created
a virtual machine those two endpoints
were created for you
one was for RDP one was for PowerShell
so if your virtual machine was going to
be a web server you would add port 80 or
for HTTP or port 443 for HTTPS or
whatever you have to add that endpoint
to the virtual machine for the cloud
service to get in there with the PIP
you don't need that you have all the
ports open so directly somebody can just
connect or go to your virtual machine
without providing the port or even
creating the endpoint because your
virtual machine will just allow pip to
hit the virtual machine directly and
this can be important and I'll
demonstrate that later because you might
have noticed by now that you know fib
does everything for you you can go HTTP
with the web as long as you have
endpoint it's fine but I'll show you a
place where it's not actually fine when
you go to a virtual machine you know
that when you go to the network or on
the Internet other computers or services
or whatever we'll see the public IP
address so that's basic networking
nobody sees your internal IP address
everybody sees the public
the address so so far all the virtual
machines that we have created actually
go out with the clouds IP address right
so if we were let's go back to our
diagram here if we were here the way
this is set up right now this virtual
machine will go out to this user and
this user will see the VIP address so it
will think that this is the address this
server came from or whatever but we take
pip what will happen is that as soon as
you assign a pip to the virtual machine
it's no longer the VIP even though the
VAP is there the virtual machine will
know that I have a pip address and what
I'm going to do is I'm going to show
this address to the user so I will show
you how that works as well so let's go
ahead and get into hands-on demo over
here so I can explain these concepts to
you from there so I have these two
virtual machines created from our
previous dip information I'm in a part
when we are talking about that so let's
show you something here if you go to if
you go to the if you go RDP to the
server there's a couple of things I want
to do here to make things easier for us
I do want to turn off the enhanced ie
security configuration I would not do
this in production because I do not
browse internet a lot from my servers
but I'm just going to do this to make
things a little bit easier here so
Internet Explorer does not keep nagging
let's fire up the internet explorer okay
SP later I'm going to go to this webpage
called HTTP what's my IP net so this is
a website which will show you the IP
address people on the internet see you
when you come from this server a
computer so you can see you are now
going out as 23 1 1 1 48 25 what is this
IP address this is actually the VIP so
if you minimize this let's go in there
you'll see that we are going out from 23
1 1 1 48 25 this is exactly what people
are seeing you as when you go to the
Internet and this website is created in
such a way it picks that and it displays
that for you so that's the public IP
address you're going out with and this
is the VIP when we create a pip address
you'll have to remember that it will no
longer pick the VIP or the virtual IP it
will actually take the instance level
public IP and show that to the outside
users which is important the next thing
I want to show there is and I will
demonstrate this part once again when we
do the PIP part so the next thing I
would show over here is that this is
very interesting and I found this in
totally accidentally was if you go to my
client computer here this is my regular
client computer on premise right let's
see let's clear the screen here if I do
ping www.microsoft.com/mechanics Ofcom
website this is actually applying bad
with this okay now watch this if i go to
the virtual machine on a zero and i do
it ping www.microsoft.com/mechanics
but the echo reply is not coming back in
so maybe the ICMP traffic is not allowed
through that and maybe we need endpoints
or something like that
turns out no Microsoft by default will
not allow you to send and receive ICMP
traffic on your virtual machine when you
are using a web address to go out the
only time this is going to work is if
you actually have an instance level
public IP address or a pipe assigned to
your server
is that an important thing for you 90%
of the time no because I do not care if
my server is not getting and receiving
ICMP packets from the internet it's okay
but we were working on a project where
we were using a piece of application or
piece of software that was using public
ping or ICMP to monitor external servers
and we were totally dumbfounded that
okay why is this not working and we
found out because of this phenomenon
over here it does not work so the way to
solve that was to assign a pip and of
course if the PIP address is allowed to
go out and do that and receive things
directly so do not need you don't need
to bother trying to get ICMP ports and
put it on endpoints to let the VIP go
and do all that stuff because it doesn't
work we have tried maybe Microsoft will
change this behavior in an update in the
future but so far it has not Microsoft
has done so how do you go ahead and
assign it pip well same as previously
will first get the virtual machine and I
want to present over here now I want to
show you that this is the internal IP
address we created one night once except
100 look at the public IP address over
here this has always been empty in my
previous sessions when we showed this
the reason was because a public IP
address is not assigned to this virtual
machine the VAP is actually a cloud IP
address for the cloud service so
obviously this was empty but a pip and
this is what the PIP is a pip is an IP
address a public IP address assigned
directly to the virtual machine so let's
go ahead and do that so we get the
virtual machine and we type this to set
as your oops sip
it's your
public IP and then you have to give a
public IP name because we like it like
just like dip or the internal I mean
like just like vape we do not pick our
public IP this is given by Azure so all
we have to do here is give a name so
we'll just call this local public local
the end public IP Sub Pop IP or
something like that and of course we are
also going to do update as your VM the
reason we need to do this update as your
VM bigs is because it has to restart or
it has to refresh the the virtual
machine configuration to apply this
configuration so any configuration that
happens to a virtual machine from
outside will be applied during restart
so let's go ahead and do that
we'll hit enter okay
task took about I don't know 15 seconds
to complete so it has has succeeded and
this was the previous output and you can
see the public IP address was not there
so we would run the same command this
time we are going to see a public IP
address has been assigned to this
virtual machine and it's called
local VM Pub IP the one we had provided
here and as your wind and randomly
picked a public IP address for you so
this is this IP address is not the VIP
it's significantly different
unfortunately there's no way to see that
directly from here so that just remember
there so what we can do is let's go to
the virtual machine here and previously
when we went we saw the VIP address was
over here 23 101 148 25 just want to
show you that the VIP addresses are
still here 23 101 148 25 however now
that you go outside let's refresh this
web page and you can see it changed to
23 166 dot 61 which is
23 166 dot 61 as you can see it went out
now publicly with a different IP address
which is the PIP so anytime you have a
paper signed to a virtual machine that's
how it's going to go up and of course as
promised I wanted to demonstrate one
last thing to you which was now if you
come to the server and do a ping
www.microsoft.com/mechanics to the
virtual replies back to the virtual
machine so it's able to ping outside we
have not created any endpoints for this
virtual machine so if you go over here
to endpoints as you can see I have not
done anything else except the remote
desktop and the ports over here now the
last thing I want to talk about with the
VIP and the PIP distinction over here is
that how do you connect to this virtual
machine now if you go and connect this
with this connect button over here it
will download the RDP file for you right
so let's go ahead and save that so I'm
going to save this on my desktop so you
and your VM 200 and I'm not going to
connect before connecting now to show
you something here let's go ahead and
edit that you can see that it's still
connecting with C Ranger VM 200 cloud
rap dotnet with a port number so it's
still using the VIP address how do you
check that that is using the VIP address
to connect well simple right go ping C
Ranger VM 200
dot cloud app net and you can directly
see that it's using the 23 101 148 25
which was the VIP of the server right
over here and it's using the end point
for weaker that was created for us which
is port 62 0 1 7 that translates to 3 3
8 9 so you have to connect to this with
six two zero one seven port with the VAP
to go out ok but we do that we created a
we created an IP address and assigned it
directly to the virtual machine so what
if we go here
take that IP address because as York
does not provide a DNA DNS name for you
with this IP address and what if I do
this will disconnect well absolutely
because now you have a public IP address
directly assigned to the virtual machine
and it will just allow you through you
do not even have to assign the port
number and this is what I was talking
about in the slides that this IP address
will allow any port to be connected
directly to this virtual machine and by
default RDP uses port 3 3 8 9 so 3 3 8 9
is loud so it's allowing you through and
for the DNS well you can have any DNS
you can just call this my VM dot for
example cloud Ranger net so you go to
your cloud Ranger net or your domains
DNS and have this as an a record because
you know that this is static and it will
stay on this virtual machine only ok so
that brings us to the end of this
session and so far this is the stuff we
talked about to add a pip the command
late is set as your public IP and I have
not gone through this command late but
what we are doing is removing the pip
from the VM the command lip is remove as
your public IP and it will go and
directly find which was the public IP
assigned to the VM directly and it will
take that away ok so that concludes this
session unfortunately this was a little
bit more than an hour and I know these
days it's very hard to keep
concentration so you can pause video and
digest as much as possible and the
reason my this was an important topic
both for example of view as well as real
life networking there are a lot of
implications and planning that goes into
doing all this thing so it took a little
bit more time to go to a decision
it took different more than an hour I
try to keep it less than an hour so you
can digest more information but
unfortunately that's what it is and like
I mentioned always that might this is
not a regular training for you I'm
trying to do this hands-on because
obviously we cannot be in a lab together
just because how things are but it gives
you an opportunity to have your own
subscription and go and do exactly what
I'm doing and have a success doing what
you are trying to do if you just follow
the way I'm doing create your virtual
machines getting to your subscription do
your thing you will be able to master
this and hopefully take this skill and
use it in your lab or in your production
ok so as usual in conclusion our
training site is at www.weiu.net /as
your get - training my youtube youtube
channel for this is cloud ranger network
Twitter handle is at cloud Ranger blog
please follow we have Google Plus and my
email address is Shawn at cloud ranger
net if you want to reach me personally
for something any questions or anything
you can do so I know a lot of you have
already done this but please you know do
not ask me questions personally that
could benefit others if there's no
personal information in there that you
do not want to provide use the use that
YouTube's commenting or use the blog
sites commenting so when I answer you
other people who might have this
question get answer - and it's almost
now now that the channel is getting a
little bit busier there are more views
obviously and more people are watching
these videos I've already received like
about 12 to 13 emails on just one video
asking some question and I did clarify
and some of them had same question and I
was like I wish they just commented on
YouTube video and I would have answered
there and would be fine so please do
that and thank you for viewing and I
will be seeing you in the next session
of as your virtual networks thank you