Demo Video: Infoblox Hybrid Cloud Integration with Azure and AWS

hello today what we are going to cover is to give you a quick overview of Infoblox a cloud integration with AWS and Azure and what you're about to see is a live demo we can record all of this live step by step where we currently have a grid master and a grid member connected on Prem this is really running in our lab in Santa Clara California and this is a fully working lab environment connected directly to the Internet and as a matter of fact we opened these ports the four for three is to connect to the grid Master GUI 1194 UDP is for Open VPN and 2114 UDP is for the key exchange so when we spin up grid members as you'll see shortly in Amazon and ashur these ports need to be open on the grid master so the grid members will connect to the grid master so what we're about to do today is to show you step-by-step how we are going to spin up a grid member in Amazon connected to grid master running on Prem and similarly spin up a great number running an azure to connect it to the grid master or plan this will give you a lot of advantages you'll get centralized visibility so you get basically a single pane of glass of both your on-prem DDI environment as well as your data running in public cloud moreover we'll show you some advanced capabilities such as V discovery which has the ability to discover all the VMS in Amazon as well as a shell and we'll also show you a demo of route 53 integration how certain records that get created an Amazon can then be synchronize down to the grid Master running comp Ram and again it will give you the single pane of glass for both all of your DDR activity is running on Prem as well as a public cloud so what exactly are we going to cover today so the first thing is to give you a quick overview of how the grid master and the grid member are currently configured everything running in a virtual environment under vmware esxi and of course using vCenter and then we're going to spin up a grid member in Azure first and we're gonna connect it to the grid master running on Prem and you will see how that's gonna happen similarly we're gonna spin up a great number running in AWS and we're going to connect it to on Prem then we're going to configure the grid master to accept connections from both Azure and AWS grid members for that we need to configure something called the net group so we configured the net group on the grid master we do some you know we do certain configuration in it and just basically put the master in the mode when it can accept connections from Azure and 80s right the reason for that is because you don't want anybody to simply connect to the grid master you need to know the IP address of your local machine where they're coming from bunch of other information to make sure that only those authorized grid members can connect to the grid master and of course they will do it over a secured connection and this is why we need those ports open using an open VPN so it will be a VPN connection from the azure great member as well as Amazon good number to connect your grid master that's running on plan so once we've done all of that the other thing we need to do is being able to enable DNS service on both Asia and a disputed members and once you've enabled that then we can do V discovery and as I mentioned earlier we discovery is ability to allow you to discover a lot of resources that are running on both agile and AWS so you get the grid century in a single pane of glass wonderful visibility into your cloud environment once we've done all of that then we'll also show you we discover the running on Prem you know for VMware so you can actually discover all the VM running and in VMware environment and we can actually automatically create DNS records for all the records that we automatically discover it's a wonderful functionality as you will see shortly and last but not least we'll show you some advanced pool functionality in terms of how to configure route 53 on the grid member and how it will synchronize with the grid master so a lot of cool stuff again we're going to do this live over the internet and so get sharing all right so now that you have a high-level understanding of what we're trying to do in this demo let's get into the details so the first thing is we're going to log onto the grid master as you can see here we're logged onto the grid master and I'd like to show you on the grid and this will show you how my current topology is currently set up so the grid master is over here as you can see it's running and I also have an on-prem grid member running over here and again both of them running as virtual appliances under vmware okay so it's a super clean environment with a grid master and a grimm member running in our lab in Santa Clara California and again this environment is connected directly to the Internet now a couple of things before we get started going to show you a quick overview of the environment so you can see here the grid master it's an AVM 1414 10 and then the grid member is the a 20 okay now you will also notice the cloud tab as we'll currently is empty this is the cloud tab that will be populated when we run V discovery to show you all the resources available under vmware AWS and azure okay if you go to the grid master you will also notice that I have the DNS service turned on on both the grid master and the grid member and if I go to administration go under Network view you will see that there is only one network view which is called default and this is the default network view that's currently that basically gets configured when you install the grid master later on we're going to be creating multiple network views when we start discovery sources under Azure and eight videos okay and if you go to the other management you will see I have a network right now this network is created and there's really nothing in it just the basically the grid member as you can see remember the IP address of the grid member on the in the lab environment and I also have a domain name already created called my company comm and later on as you will see when we discover resources under vmware all of the records will be automatically populated and become visible in this domain and if you go to dashboard status this will give you a quick overview of our current environment again a super clean environment it's a great master grid member i have the dns service turned on the cloud tab is currently empty have a DNS record created and basically when that were created all right super clean environment we are ready to get started so what I'm going to do right now is I'm going to log on to Azure using my own personal account and I'm going to spin up a grid mentor basically we gonna spin up a great master eventually we will convert it into a great member but so we're going to walk you through the steps of to configure basically spin up an instance of a grid master in Azure and then after that we're going to do the same thing running it in AWS so you can see here this is my asher tab i only have a one grid member right now but it's currently turned off so i'm gonna create a new one shortly and i have a couple of member you know couple of VMs running in native illustrator but again we're gonna create one and run it shortly so let's start with our first so how do we get started the first thing you need to do you need to go to dashboard click on marketplace and type Infoblox okay you've seen you will soon discover that there is only one entry over here you click on it and you click on create and now we're going to go through the process of provisioning an appliance the appliance I wanna pick this and pick an entry level one let's say v8 25 we give it a name so let's call it V a 25 - m14 like member 1 we're gonna give it a password make sure you pick a strong password so it doesn't complain pay as you go a resource group so let's go ahead and create a resource group again this is all other stuff so V 820 m1a ok and you as first you can select the region but for now let's keep it on us quest ok click OK we go to the next page say okay well what version of miles do you want to use for this grid member so we're gonna go with the latest version that's available for algae which is 8 or 3.0 we pick the storage that we need to use which storage account you want to use we'll pick one I already created this ahead of time for the interest of time ok we go to virtual network I already have a virtual network created the subnet we have two interfaces one for the LAN interface and one for management so we select language and we select management click ok then an IP address do you want to give it a public routable IP address yes because I'm going to connect to this instance later on over the internet so I'm gonna give this a name so let's call it IP m14 number one and I wanted I want to give it a public routable static IP address so it doesn't change ok ok and now we're going to give this instance a domain name so you can connect to it via domain name or VIP but in this case we're going to give it a dim name so we call it V 825 m 1 okay and you can see a green check which means is available and this is the domain name that you can connect to and click OK ok and now we wait a couple of seconds for Asher to basically review your settings make sure everything is ok and then the ok button will appear in few seconds so now that it passed the validation we can go ahead and click OK last you will see the smashes in are you sure you agree to the terms of condition because you're going to be built so basically my account will be built for this I'm gonna go ahead and create and now Asher is in the process of creating your virtual machine your novice virtual of the machine I'm just gonna take up to six minutes to be created so let's click on refresh and you'll notice you you will see the progress and again it's gonna take about 6 minutes for the VM to be created IP address to be assigned to be spun off etc etc so we'll come back to it in a few seconds now while we're waiting let's go ahead and create an instance for the AWS version of the great man direct so we're gonna switch over to address click on launch instance and we're gonna do three is similar process but slightly different so the first thing you need to do is come over here to a community MI and type Infoblox you will see lots of models so let's pick the 8.3 dot 0 and let's copy this name this number because we only want to get a list of all the miles zero appliances so you see now we shrink down the list and the one I want to pick as this guy a 3.0 TDI which basically give you the ability to pick which version of Nyos which version of Venus you wanna pick later on when they deploy it in a SS so and the other thing I'd like to do is I'm interested in the entry-level version which is a VA 25 which basically uses the are for large it will use a template as you see shortly so I'm gonna copy that so I'm gonna click on select and you see this is the different flavors or different configuration you want so the best way to do is control f and paste this are for large because it will take you there directly so I don't have to search for it so you select it click on next next is we need to figure out well what subnet I want to give an IP address for for this VM I already created one ahead of time we're gonna select the subnet let's not worry about like IP address we'll do a little bit later I'll show you how to do it and you scroll down and this is extremely important by default there's only one interface that ships with this appliance by AWS so you wanna make sure to add another one remember we need one for language and not one for management so we need to add one and this is a manual process you have to do it otherwise things will not work ok click on next yup magnetic storage is fine click on next we don't care about tag for now click on next security group basically what post you wanna have opened that are available for your appliance I already created the security group ahead of time for the interest of time and I selected commerce and also at the ports that must be opened to get the again to get the configuration to work ok click on next and say yes I don't want to use a city I wanna use the cheaper one the magnetic one click on next and then yep you review the setup looks good everything looks good so let's go ahead and click on launch and yes I acknowledge launch wait few seconds and click on few instances and there you have it so now your answer is going to be created and again this is going to take about for five minutes now while we're waiting for it we need to do a couple of things if you click on this guy you will see information about your VM about your villainous villain and you can see we have is zero and is one which we added shortly a few minutes ago so let's go ahead and click on f1 and let's click on the interface ID of is 1 and this will take us to this segment where we can associate a public routable IP address with this interface so we can connect to it over the internet so we're going to go to actions and we're gonna click on associate address and let's pick a public routable IP address and this one is available if it's not available you can there is an option in advance where you can basically allocate a new IP address to become available but I already allocated it ahead of time again to skip a couple of steps so this is the IP address I'm gonna click on associate and it will associate it with each one and it will make this environment available over the Internet so let's go back to the dashboard and let's go and select our our soon-to-be running instance and you will notice over here ipv4 public IP address this is the IP address that we're going to be reaching the Vanaras appliance over the internet at ok so let's go back to asher now again it's going to take about five minutes so let's go back to Azure and let's see where we are so it's been 4 minutes and 25 seconds it's gonna take a couple more minutes for LG to wrap it up but at this point if you go to virtual machine you are going to see the VA 25 m1 even though it's still creating that but you can see it and if you click on it and you click on networking guess what you will see the internal IP address and the public laudible IP address this is a static public routable IP address where you are going to connect to your other instance app this is exactly similar to AWS remember the ipv4 where I manually had to assign it with Azure I basically told that during provisioning process to give it a public router like the others I could have done the same thing in a SS but I didn't want it to show you the extra step of how you can associate a public route or IP address to the virtual machine alright so while we're waiting for it we need to do a couple of things at the grid master to tell the great master to accept connection from the azure endpoint or from the eyes your grid member and there is a good number so the first thing you need to do before I actually show you the step there's one very important thing you need to do and that is you need to create not groups now why do you need to be in a group now let's talk about that for a second now when you configure when you want to add a an entry here at the grid master to tell it hey I want to accept connections from this remote as an endpoint you need to provide the IP address of the remote input now the IP address of the robot endpoint is this private IP address 10005 but this is private to Azure it is not visible on the Internet now when you create an entry over here you gotta give it the private IP address which is 10005 however well the grid master doesn't know how to talk to 10005 it knows how to talk to the public routable IP address which is this guy so we need to do an extra step to basically enable the grid master to know yep this is the private IP address of the grid mapper but it's coming from this public routable IP address and this is the whole concept of an ad group so we need to create an ad group and it's very simple you see basically select your grade master over here you click on grid properties and you will see an option here called null groups now I went ahead and I created a few ahead of time but it's very simple if you click on plus and you basically give it a name let's say you know X Y Z and it's there but anyway I didn't ahead of time so we don't have to do it one by one so I already created several new groups as you can see here one NAT G as your energy address and you know a few others that we can use later on if I need it so that's it that's all I need to do over here and you will see how we're gonna use it shortly you can so make sure the net groups entries are created ahead of time for the great master so now let's go ahead and create an entry to for a sure so we're going to click on plus and this is a virtual appliance so we're gonna select Venus and we're gonna give it a name so this will be the same as your m1 dot my company comm which is a zone that I already created ahead of time all right click next now we need to give it the internal IP address of the other endpoint which is 10005 so let's go ahead and do that the subnet mask is 255 255 255 0 and the Gateway is basically a good one right this is kind of standard stuff if you don't know what the subnet mask is when you boot up the VM you can login and you can get this info but I already know what it is so I just started I have time click on next click on 7 clothes now you can see here I already added an entry for Asha but we're not done yet we need to let it know the public IP address of as you remember we talked about now group so we need to go to edit we're going to go to networking or to network and we're gonna click on the Advanced tab scroll down and you see over here now you can click on the net group and you select NAT NAT G Asha and here you type in the public routable IP address of asia which is this guy okay again this is you have to do it this way so the glute master knows both the IP address of your private instance as well as where it's coming from alright you do that click on 7 clothes you will get a this message say yes and it will basically take a few seconds to configure it alright so we've done that for the actual end point let's do the same thing for the AWS entry so again same thing plus I will control it AWS m1 dot my company.com click on next and same thing let's give it the private IP address so we're gonna go to is one and it's this guy actually you can click here on copy and let's go ahead and paste it and same thing two five five five five two five five zero and the Gateway ends with dot one all right seven close and just like we did before we added we go back to network we go to Advanced tab and we scroll down to that group and we're now gonna select Neji AWS and we need to public routable IP address and which is over here again we click on copy to clipboard and let's go ahead seven closed and done all right so now the grid master has the two entries needed for it to accept connections from the remote grid members so let's go to Azure the the azure virtual machine should be ready by now you can see here it's running if you go here you will see the deployment has been successful so all of the steps are done so we are ready to connect so one last feature that's available in Azure that is not available in in AWS is this is the ability to connect to the virtual machine via its console so if you click on it and you scroll down you see over here see your console this is basically give the ability to connect directly to the virtual machine and start typing your commands unfortunately AWS doesn't allow you to do this in a TLS you need to know the public routable IP SSH into it and start using it the problem with that approach is if something bad happens to your virtual machine and you cannot for some reason connect to it over the Internet you simply locked out you just can't connect it because there's no console access with this approach on Azure even if you can't connect to the caller to the VM over the internet you can simply come here to the serial console and connect to it as if you're sitting in front of your computer ok so here we go let's type admin and we give it the same password that we did when we configured it for the first time so make sure you remember your password so the first thing I'm gonna do is this I'm going to do a short network to confirm that I get the 1000 IP a 10 1000 5 IP address I'm going to show you that actually I'm connected to the Internet via the public routable IP address if I try to ping the Google DNS IP address you can see it being successful now I can't ping by domain name because I don't have the DNS and the forwarding servers enabled on the grid member and that's okay we don't need it we just need the ability to ping IP addresses on the Internet which is fine the next thing is if you do show licenses this will show you all the licenses that are activated by default when you spin up the grid member ok in this case the grid master alright great well how do i connect to this instance over the Internet remember our public routable IP address so if you go to networking you see this guy so let's go ahead and copy it and let's go ahead and open a new tab and I'm going to HTTP and I get a bit the IP address and lo and behold I can connect to it and now we'll give it a few seconds and then we'll go ahead and type in the username password again make sure to remember your password which is what you said during the provisioning process of your virtual machine under agile now this will take a few seconds to log in and again we are connecting to this appliance over the Internet now this is a real public I mean I'm doing this step-by-step this is not like some recorded this is like real actually happening right now as I'm recording it so I'm connecting over the Internet to this appliance so I'm gonna click on I accept again you gotta wait few more seconds and we are connected to the grid master all right if you click on the grid master you will see and if you move to the side you will see the platform is Asscher and you can see it's the VA 25 appliance all right so I just wanted to show you that you can connect to your instance over the Internet and let's do the same thing for AWS while we're at it so it should be running by now so again let's copy the IP address open a new tab type HTTP actually as a matter of fact not yet because AWS is a bit different because you need to apply temporary licenses when you connect to it so what we need to do is we need to SSH into the appliance so let's go ahead and launch puddi and then basically it's an ssh client and type in the IP address of the AWS member or in this case against the liquid master click open you're gonna see this yep no problem and let's go ahead type admin and the default password is info box all right so if you first think let's do this show network yeah this is my internal IP address and of course you can ping Google cuz I'm just connecting to it over the internet so it's gonna work but what I didn't wanted to show you is when you spin this up and there under it Willis for the first time if you do show licenses there are no licenses set so let's go ahead and enable temporary licenses to get started so set temp license and we're gonna select option number two okay I don't know if you do show licenses again you will see the DDI licenses now we also need to enable the Vinaya license so we do the same things at them and we select option number four you can see here add - license option 4 and you select the model that you want and we're gonna pick the entry level 1 which is the VA 25 and say yes now this is gonna reboot the appliance so you will see shortly that my ssh connection is gonna is going to be gone because again the appliance going to reboot so let's wait for it okay so the appliance rebooted so let's go ahead and log back in admin and again the default password design for blocks and if you do show licenses you can see all the DDI licenses including the newest appliance now it's gonna take again a few more minutes maybe 2 to 3 more minutes for all the services to start and then you'll be able to connect to this virtual appliance over the internet via the public routable IP address now if we go ahead to this tab that we just opened and we do HTTP and we give it the public routable IP address of the instance you know I can just gonna take some time so it's not ready yet because these services are being started so let's give it a couple more minutes and they will be able to connect to the virtual appliance over the internet so now that the services started you can see we got this message click on advanced proceed and now we're connecting to the grid manager again over the Internet running in AWS so I can add man the default password is Infoblox and we are connecting to it we'll go ahead click on I accept so now we're connected to the grid master over the Internet again this is running in AWS if you click on grid just like we did with Asher if you move to the side you can see here the platform is I develop AWS and again is DV a 25-dollar again so this is running in AWS and if you click on this tab this is running in hazard okay so I can measure AWS alright so now let's go back to the grid manager for a second just to give you a quick review of what we've done so far so we've created an entry for a sure we've created an entry for the AWS member we have both Azure and it will escalate masters running the question is well ok how do you connect the grid basically convert the grid master in every list become a grid member so it can connect to the grid master running on plan so for that very simple we simply need to connect now there are two ways you could SSH into this instance just like you did under AWS or you can open the console I prefer to use the console for with Azure you just you know much easier so I come over here and I'll type set membership and it's gonna ask me for the VIP which is the virtual IP address of the grid master which is in our case this guy so - 850 and again this is our on Prem a grid master so we're gonna connect it I already open the write ports and I did all the and all of this stuff just to make it really easy you're connected directly to it now in real life you never do this you don't expose your grid master to the Internet but against I needed to do this I can show you the live demo okay so let's come back to the console and let's go ahead and paste the IP address of the grid master next is the entered the grid name the default is Ophir box I'm using the default so I hit enter and the entered the grid shared secret by default it's called test which are again I'm using the default so I'm gonna call it test and say yes are you sure you wanna connect yes are you sure yes so now the applies going to reboot and one of the beautiful things about the serial console is you can actually see what's actually happening so now we're gonna reboot or restart the services or the grid member and it's going to attempt to connect to the grid master shortly so let's we'll give it a few more seconds while it starts to restart and then we're gonna switch over to the grid master and I'm going to show you that the connection is going to start to occur between the remote member and the grid master so they're gonna start to synchronize your data it's going to reboot couple of times so I'm just gonna take a few minutes for the synchronization to occur so here you go let's do a refresh and you can see it's connecting synchronizing and within a few seconds the appliance gonna restart again so there will be a couple of restarts before it's all done so here we go the system restart you can see so if you go back to the grid master do a refresh you can see offline because again the grid member is going to restart and again that's this couple of times so the first time basically is connecting two to synchronize next time it's gonna apply the configurations and then the last time it will be ready to connect so again a couple of restarts and you'll be ready to to connect so while let's just wait for it because I'd like to make sure the connection went there smoothly before we move on and do the same thing on the idleness so you can see here starting services let's do a refresh again this is gonna take a couple more minutes again you just wait another minute or so and it's gonna be green here we go it's running great so we just connected our grid member running an azure to our home Prem grid master again this is all done live right now as I'm recording this over the Internet great so the first thing I want to do before I forget is I need to go to services and turn on make sure that the basically I'm in this case outline I need to make sure I turn on the DNS service of the azure grid member so I select it and you see here this button click start yes and it will take you know another 30 seconds or so to start the DNS service and you get to see you get to see this message um that's going to take some time click close and let's refresh and there it is so now the DNS service is running on the other end close so I can if you select the azure and port now if you scroll down you will see additional information you will see the shield number which you didn't see before because again now we connected the grid member to the grid master so we have more information about it all right and if you need more information about the other endpoint you come over here you go to edit and again this will see it's a VA 25 you get to see how it's not pro just like we did before so all it's all good all right great so let's do the same thing for AWS now remember with AWS there's no such thing as a console so you have to SSH so we're searching into the grid number running in a SS and you can see the IP address that ends with dot 1 3 9 you can see here 1 3 9 so same thing we're not gonna do a set membership and we're gonna give it the vet of the grid master that's running our plan just like we did with Asher so let's go ahead and copy and paste the sky ok and hit enter again Infoblox again we'll use the default chair key test say yes yes now it's gonna reboot as you can see we lost our SSH connection and again this is where you would we would hope that everything goes smoothly and the grid members in a restart and connect otherwise because if you can't connect to the grid member you really just there's no way around it right you don't have console access this is one nice feature again I like about Asia that AWS unfortunately doesn't have so now I just have to wait it's gonna take probably a couple of minutes for the services to start and same thing it's going the grid member in AWS who's going to connect to the grid master on Prem and synchronize so we just have to wait let's just be patient here now a lot good meaning for this couple things I want to mention things went fairly fast because the grid master and the grid member are using the same version of our DDI appliance which in our case we're using version 8.3 dot 0 if the if the client is using an older version let's say 8.0 or 8.1 it will actually connect to the grid master and it will download the latest version from the grid master and that will take some time it could easily take 5-10 minutes all right so right now you know luckily for us we're using the same version so things go fairly fast but again if you're using an older version of the grid member it would simply download the latest version from the grid master over the Internet apply and rebooted so it'll be more repos going on and eventually it will work so here you go we're connecting we're synchronizing and again there will be a restart so we're gonna lose our connection just like we did on the router so give it some time and as you can see now we're offline basically the appliance is reporting and it's gonna try to connect again in another minute to the grid master and here we go the grid number was able to connect the grid master again this is using the AWS instance as you can see here and again just like we did before let's go to services and let's make sure we enable the DNS service on the AWS grid member then give it a few more seconds and we'll be able to connect and there you have it the DNS service is running and everything looks good all right so before we continue let's just do a quick summary of what we've done so far again I have my grid master initially with the grid basically a grid master running on-prem along with this grid member again running on pram and you can see here the naming I called it you know VA 21 Prem then I went ahead and I spun up an instance under a sure I provisioned it I set membership and I was able to connect my grid man by running energy to my grid master running on Prem I did the same thing for ADA les aspin epic remember running in AWS I was able to connect it to the great master running on RAM so now I can I have beautiful you know centralized visibility into both on Prem and in the cloud you as a user or as an admin you really have no idea what's going on here because the only way you can find that this is running in Azure in a dress you just simply have to come over here and decide the table this is a table scenario which is which is exactly what we intended it to do intended this product to be very seamless very elegant and when you're managing your data infrastructure it really doesn't matter if you're doing it on Prem or in the public cloud alright great so things are looking good wherever we were able to connect all of these remote appliances to the on plan now what what do we do now the first thing you need to do is to run v discovery and v discovery will give you the ability to discover all appliances running in a remote environment so let's start by configuring V discovery for adjure so I click on the cloud tab and I click on V discovery and I click on discovery manager and I click on the plus sign and I give it a name so let's call it either V 1 or V D 1 for the discovery one ok select I select my edger and port which is a n number one click Next and I click on server type which is a sure now I need to provide some sensitive information to how to connect to my as your endpoints so there's a service entry client ID secret client secret you get this information from your as your account and you copy based on mobile here so I'm gonna pause this video copy and paste this information and I'll be right back alright son back I copied and pasted all this sensitive information that are applicable to my account and I'm gonna click on next next is basically you need to decide do you want to use the default view or you want to create your own view now remember earlier in the video I showed you on the grid master there is something called default view which is created by default or you can create a new one that are applicable for a particular domain now the whole point for a network view in a nutshell is if you have overlapping IPs that you want to use at the same time so for example company acquires Company B and both companies have the same exact internal IP address space well with Network view you can solve this issue by saying network view for company another network view for Company B both of them can have the same existing IP address space and no conflict will occur okay so I'm gonna go ahead and say I want to create an automatic network view for agile and this will be automatically created based on the tenant ID that was provided by agile which is really nice way to segment how information you know hey you have data on pram there an azure data data individuals so some time it makes sense to have multiple network views it's really up to you but in this demo I want to use a network view for a sure as well as a network view later on for anybody else okay click on next this is how it's gonna yeah when you do a discovery do you want to merge your existing data with a new data or what you wanna do it so for the interest of time we'll just leave the default and how often do you wanna run we discovered you can run it every few minutes hours days whatever so for now we're gonna run it manually but usually you can run it every few you know every like a couple of hours or so right depending on how think changing your environment will save on close again let's quickly review our setup so if you go to this entry click on edit we started by giving the the job a name we selected the azure member this is the sensitive information you need to copy a page from your account we decide if you want to use a diff view or a new view how you want to do with the data that you discover it and how often you want on your discovery all right so with that we are ready to run to be discovery now it is always recommended to wait like you know another 30 seconds a minute before you run it because again we're doing some stuff behind the scenes so let's go ahead and run it and if it doesn't tell you simply you know run it again so click on start click yes and job started ok good job in progress and it's fairly fast and now this will finish very quickly because I don't have a lot of resources or a lot of VMs running in Azure you can see boom it's done very fast so now if I click on close watch what happens boom there it is the azure platform and apart from becoming visible in the cloud that there was nothing there right and this is the basically the talent ID as you can see you the name and the ID and it told you how many VM is discovered how many networks and so on and so for a lot of cool information now if you drill down if you click on the name you will get to see all the network that it discovered in Azure and if you click on VMs you will see the VMs that are available energy now in my case I don't know I only have like one VM so not much not terribly exciting but at least you'll get to see how things work VPC this is the virtual private cloud and terminology basically and you can see here it discovered to be pcs and you can see detailed information about each of the DPC's okay that works again the network it discovered in Azure VMs what VM so have running in Azure and so on and so forth it's all there ok now if you click on data management you see there's a default view which is what ships with the product but now you have another view which didn't exist before this is the view that could automatically created via V discovery because we told it to create a new view so let's select that and again you will see only the resources that are visible in Azure versus if you go to default you will see the resources that are only available on Prem again this is a nice way I mean that's how I like to do it you could combine both of them become combined everything and if but again to make the demo interesting it makes sense to just have it create a new view that's about a fact if you go to administration you go to Network views you will see here the view that got created and you can see it auto created IV discovery right it's all there okay great so looks good now let's do the same thing for the AWS entry so we're gonna go to the discovery discovery manager plus we're gonna call it AWS v1 I can for be discovered here because it's for anybody else select we select the AWS member one and same thing we coming over here and sort of Ajman will select AWS and again I need to enter some sensitive information for this to work so I'm gonna pause the video enter the information I will come back alright so we're back i entered all of the sensitive information I was talking about earlier just like we did for a sure we click on next same thing you want to use default or in new tenant yep I wanna create a new tenant for this particular demo and yes I'm going to use the default and yes I'm gonna use the default save and close all right again just to review click on edit again we have the name the member we have the endpoint with all the information we basically provided I got this from my AWS account yep I want to create a new network view yes I want to basically use the default policy in terms of how I'm gonna merge my existing data with my discovered data and how often do I wanna run it alright so let's go ahead select that entry and click on start are you sure you wanna start yes do a refresh now this happens sometimes it doesn't start right away this is why I said earlier sometimes it's better to just give it a minute before you start it because it's still doing some stuff behind the scene so that's just wait a few more seconds and we probably have to try it a couple of times before it works so click on start and you can see now it's started and here we go it's running and again it's going to finish fairly quickly because I don't have a lot of resources running in areas and here we go it's done now watch what happens I click on or close you're gonna see the the Amazon management platform up here okay watch this click close and there it is okay so you can see here it discovered the Amazon entries and now if I click on this guy you'll get to see the network's in this case it's showing everything and go to the ends it shows all the VMS on the amazon and again if you go to data management lo and behold it created the entries for Amazon for the views and here we go this is one view the other view doesn't really have anything it's empty but what I'm gonna be using is this guy alright versus this one is for agile like we talked about earlier alright and if you go to administration Network views you can see the net reviews already created all right so now go back to the cloud tab the great we've done this for Amazon we've done this for edger well what about VMware what about the on-prem VMware environment that we have remember this guy the on-prem what this is running on prime this is running on my D receptor can I do the discovery for VMware yes you can we're gonna come here we're gonna go to V discovery and we're gonna do the same thing except now we're gonna call it you know VMware and we're gonna select the on-prem agent or then prime grade number which is the sky and now we're gonna say VMware now for VMware we're gonna give it the IP address or the domain name for vCenter server so vCenter server were basically host all your VMs right so again give me one minute while I gather this information and we'll continue alright I'm back I entered all the information and this is again the IP address of my vCenter server running in my private isolated new lab environment yep I'm using HTTPS and I gave it the username password to connect to my vCenter server all right now do I want to create a network view or when I use the default one I didn't wanna use the default one in this case because again this is my um pram you know environment I'd like use the default one I'm not gonna create a new one so I say default now over here I want to show you one cool feature we've added you know a year or two ago is this for every newly discovered IP address I want you to create a host record so if I create if I discovered a VM with an IP address you know with a specific IP address I can automatically create a DNS host record based on some kind of a policy so this policy I'm gonna use this default policy which is basically the VM name dot my company comm so it will automatically if it discovers the VM it will automatically assign it a name and it will put it a basic one that the my company comm domain name which is really powerful feature as you will see shortly and it will do this automatically for you on the fly for all the hosts that it discovers click on next and save and close and just like before let's just give it 30 seconds to a minute while it's doing its thing behind the scenes and then we can start it and then once it finishes you will see an entry for VMware just like you have for Amazon in AWS and we were able to see all of the resources it discovered not my lab environment is a decent size I have a lot of VMs in it so this is gonna take some time so let's go ahead and start it it's running here you go the job in progress and this is gonna take a while so this could easily take like four or five minutes for it to finish because I have a fairly decent-sized environment it really depends on the size of your environment right I mean if you only have a couple of V ends like I do in antivirus and Asher you know you saw it was very quick like 20 seconds it was over with VMware I have a fairly decent sized lab environment so it's gonna take a while to discover everything I have about like theory VMs or so configured different configurations multiple switches and it's you know it's gonna take some time to discover everything so I let it run and we'll come back alright so we're back it took about four or five minutes for this job to run so click on close and guess what here it is VMware measurement platform appeared and you can see it discovered 29b ends which is exactly what I had in mind and if you click on default you'll get to see all the games so now you understand why it's taking water rights I mean it helped to go and discover all these resources if you click on the next tab you can see more resources click on the next tab more resources try to discover the lot of stuff now great this is the feature that I've been wanting to show you if I click on data management click on DNS and then I need to switch back to default right and you see here my company comm click on my company comm and you get to see all the IP addresses of all the VMS that it discovered but more importantly it created a host record for each of the discovered devices the VMS now the reason why I did that is because of the policy that I configured earlier during we discover you remember let's go back to the discovery configuration just to make sure this concept is clear and let's go to VMware I did that root view the Rumple I told to use the default view which it did and there are a collection consolidation you can see here I told her host and I told it to basically create the VM name and my company so to magically created all of this for you so again if you go back to the air management you can see as it discovered as I discovered the VMS it automatically created the host record for them all right and of course you could do the same thing for a native less energy I just wanted to show it to you on the vmware alright so let's go back to the cloud tab one more time to go to tenants and again you can see amazon vmware we also support OpenStack and very soon we'll also be adding Google Cloud our phone to the list so you'll be able to bring it all together under one umbrella ok and you can see you're on your V PC you can see the Amazon veetc you can see all the configuration here now one other thing I'd like to show you is if you go under VM and you can create some filters so right now I can say show me under cloud management platform equal to let's say Amazon I'll click apply and you can see it will filter it down to the Amazon DMS or only show me a sure the ends click apply and you can see after I mean show me VMware and of course you're gonna get a lot all right so you get the idea here you can do filtering and you can do filtering on all sorts of information um it's very flexible in terms of how you filter and of course one other thing we do is you can actually export all of this data to an Excel spreadsheet so if you click on this button and say export yes and now it's exporting it download and you know you can open it on the excel I don't have Excel format this machine but you get the idea you can open it you get nice fancy table and you get this all of your data over here okay so it's it's totally supported alright now one other feature i'd like to show you which is a specific to AWS and that is the integration that we have with round 53 so wrap to 53 is basically amazon's way of doing dns or it's their method of doing dns and what i want to show you is if I create a DNS record in route 53 other Amazon I would like to synchronize it to bring it down to the grid master so that way I still have the centralized visibility for DNS records created by of course by our TDI appliance as well as DNS records I've got created by around 53 and again this is part of the unified view of both up Gramm and the cloud bringing everything together on the grid massive very powerful capability alright so how do you do it well let's go to administration and let's go to users we're gonna create a user account for route 53 so let's call it route 53 ok the user and we give it a password and we need to select the cloud API only account all right just remember this this users route 53 and then the password click Save on clause so that's the first thing we need to do next we need to go to the cloud tab and we need to enter a bunch of information now again this information are sensitive to your account that we need to copy and paste here so all right I'm back so I entered this information that are specific to my account select the novice user remember we created route 53 that's why you needed to need this account save our Clause okay so that's the second step third step we need to come here to the grid Amazon and we need to create the entry to do the synchronization with about 53 so we're gonna call it synchronization Group 1 we select the member which is AWS member we're gonna select the username password for the account we created in the earlier step and we're going to say use the default all right now click on plus we get it a name as t1 for sync task 1 and how often you wanna do the discovery let's say every five minutes and yep I wanted to both public hostesses and private houses on this is in AWS stuff click on add save and close all right and now we come here using details and let's go ahead and run it now before I run it I need to show you what I'm talking about so I'm gonna go to the error management I'm gonna go to DNS I want to make sure I'm in my default view and you can see here there is something called my company comm now let's go to the AWS account and let's go to route 53 so let me go to route 53 and under my route 53 account I have two zones to host his own so if I click on hosted zone you will see there's something called Tessa's on and there's something called public zone so if you go sorry private zone so if you go to private zone you will see I have a bunch of records created over here okay and tested zone I only have like you know couple few records so what I'm going to do right now when I run this task is going to connect to this section in route 53 and download both the both of the zones along with the old a host records I bring it into the grid master I'm just going to do it you know elegantly very fast all right so let's go to the grid master again let's go back to grid come back here and we're gonna go ahead and run it run task now and assuming I've entered my credentials correctly here you go it should take a few seconds to run horses on successfully fetched I can give it a few more seconds completed now again we were running it manually but in real life you know it runs every five minutes because that's the policy but for the interest of this demo I don't need 90 but it runs okay click close now let's go to data management and lo and behold what do you see private zones and tests on so if you go inside the private zone you can see all the records that are there and if you go to the test soil you can see all the records are there all right so let's test it one more time let's go to that 53 go to private zone and I'm gonna create a zone a create a create a record so let's call it demo one and since this is demo let's call it four four four okay so again then we want a profit zone and this is the IP address click create and where is it today's demo on so now let's go to the grid master again go to the private zone it's not gonna be there yet because we haven't run the synchronization you have to five minutes or we can write manually so let's go ahead and run it manually so let's go to the grid come back here you do the same thing run it and here we go give it a few seconds to run clothes go back to the other management and there you have done one got downloaded okay so that's the beauty of configuring route 53 I can go back to the single pane of glass bringing all this data from A to B less you bring it down to your grid master you have a beautiful visibility into your environment that's all that summarize everything we've done I know we've covered quite a bit so over here we started the demo by showing you the grid master at the grid number on pram we spun up a grid member running in Azure we spun up another grid member running in AWS we connected to each of these great masters over the internet then we changed the entry basically table set membership to make sure the grid members connect to the grid master on plan for both Asia and AWS we started the DNS service we did we discovery for a sure that we discovered for AWS that we discovered for VMware we show you all of the centralized visibility for all both on Prem in the cloud then we showed you how to configure and run route 53 integration which basically bring down the records from Amazon into the on primaried master with that I hope that you found this video useful again we only touched upon the essential features and functionality of our cloud offering there is much more to it than what I just showed you today but hopefully give this gives you a very good idea what Infoblox is doing in the public cloud arena and the integrated smooth integration that you saw today how we can actually make it seamless from an administrator perspective to bring in the data from your public cloud integrated with aam Prime and you have centralized visibility of all of your DD idea with that thank you very much and if you have any questions please contact your roblox sales rep

Channel: Infoblox Community

Views: 2,455

Keywords: Hybrid Cloud Azure AWS Route 53 Infoblox DDI vDisocvery

Id: lcH1iEXj_CU

Length: 58min 3sec (3483 seconds)

Published: Wed Jan 16 2019