 Tommy here from Lauren systems and we're going to talk about building an open source slab using xcp and g including how the virtual Networking works inside of it if you all learn more about me and my company head over to Lawrence systems comm There's a hires button right up at the top if you want to support this channel in other ways There is affiliate links well on the side of our website and down below this video to get you deals and discounts on Products and services we talk about on this channel that does include shirts because this question seems to come up a lot in Comments and where do you get the shirts? There's an affiliate link for the shirts over on teespring If you like any of the shirts that we have or ones you've seen us wear that are available on our store you can order them here Shipping is pretty much all over the place. Teespring takes care of all that for us all right xcp and g is the Fully open source hypervisor. I've talked about a lot on his channel But I wanted to give you a getting started video now I have videos that I'll reference that go in depth on other topics But this is the basics of getting you started This is an fully open source product and it does offer paid support if you want it We're going to talk about it from the concept of building your own lab Which means we're going to use the open source unsupported versions of this You can get support from their forums and have discussions They do offer, you know a good community that actually they have quite a big community as they point out here 23 000 forum posts and over 90 000 downloads of this and 3400 forum contributors So they have a very active very healthy online community, which is great if you're looking for basic help So I think this is a great product with a great community to build your system on But it also does work in the production environments of large-scale enterprises And that's also why I want to start with what is zen orchestra? What is the architecture of this and what is zen project? So zen project is the actual hypervisor itself, but not the whole thing zen Orchestra is an orchestrating tool that runs on top of it So you have xo a the zen server, which is over here xcp and g But xo a actually supports both the citrix one and the open source one from here citrix has their own version This is separate from citrix, but citrix does pull Just so you know the same zen server at the core and zen server itself at the core is if you're wondering Just how popular a project it is. This is still the primary hypervisor within amazon and I know amazon uses more than one But this the zen core not xcp and g but the zen core is a big part of the hypervisor system That's used in enterprise things like amazon and xcp and g is used very frequently like I said in large production apartments all right We'll start at the hardware level And picking out a server means well Some you know guesswork sometimes for things they do have A hypervisor hardware compatibility list generally speaking it does work on a very broad range of hardware But will it work? Is it hardware compatibility certified that matters a lot in the enterprise market? And I just chose a del server, but I mean they have a lot more than just del in here And they bring up del because one of the affiliates down below is tech supply directed and they do offer discounts And for example, I just did a video with the del r630 It's 100 compatible with zen server. It's on the list here You can spec one out and I have a separate review. I did have this It's a good server to run this on but obviously if you're building a lab it kind of comes on to whatever you have So even if you don't have a system that matches this hardware compatibility list, it doesn't mean it won't run specifically the lab server We're building here is on an amd fx processor with 24 gigs ram and an ssd and some random motherboard We had I purposely built it one out of spare parts I had two to show that yes, it'll work with things that aren't even on the list But anytime you go off-list with it, there could be Potentially compatibility issues and there's work around for some of those compatibility issues that you can discuss in the forums Now architecture wise this is where sometimes it's a little bit confusing and this is an important part of the video That's I wanted to start with when you're loading xcpng Which we will go through the loading process of xo a zen orchestra the preferred way to control and manage the servers is a vm that runs within it This is different than some other projects and I'll bring up proxmox I don't really use proxmox, but of course i'm familiar with it. They integrate it all into one system And that's just a different architectural design to load it and have the management platform be within it Zen has been done differently for a long time and one of the reasons that is scalability So you can have a single system running xo a one vm wherever that vm lives As a matter of fact, it doesn't have to live inside of a Zen server, but traditionally you do it's one of the servers you would have running on there You can but I could be running it directly even on my computer right here if I wanted to it's a web-based application And there's instructions and we'll get to those and how to build it or you can just download it from them But from one server you can run many many zen servers So from a concept of that you can even and they have options to work remotely I can have a zen server running as an orchestra server running here at my office and vpn into other clients that are remotely and Manage all of their vms with it. So zen orchestra offers a large amount of flexibility and scalability by doing it this way So you can have all these machines deployed and even if they're completely separate pools for example So you pool resources together So you take a series of physical zen servers and you create a resource pool So you can do things like high availability or just easily You know move vms around between those resource pools zen orchestra can connect different pools together And move machines between them And this is really easy for us because we have our main production pool and we have our lab pool And we'll be focusing on the lab pool But I can use one instance of zen orchestra to manage both pools very easily and move vms between them Even though the servers don't have to know each other zen orchestra will handle the introduction So to speak of the server so they can speak to each other and pass vms around between them provided They're all on the same version of xcp ng I do bring that up because there's sometimes these Compatibilities if you have one on a newer one and one on the older one Older will go to newer but newer doesn't always go to older. It couldn't sometimes be compatibilities It's always best when they're on the same But zen orchestra can handle talking to pools that are at different versions So even if some are at older versions, you haven't get it on re-upgrading and some are at newer zen orchestra will communicate with them All right, so first thing is do is download it pretty easy Grab the iso and install it now. I've already physically loaded it on the hardware But what I want to do now is walk you through what it looks like to go through the load and what the options are to choose I want to boot you've got two options standard boot or advance We're going to look at the advanced options and what these are is if you have a certain edge cases Like install or upgrade Alternate kernel options serial console etc. There's a couple different things if you have an edge case And like I said, if you have certain hardware compatibilities, you may want to try one of the other kernels or the install 2g That's for some of the Ryzen systems that there's some working out compatibility issues with and same with some of the epic So let's go back over here And we're just going to go through the standard install go through the boot installer here So press enter and I'll fast forward through this while it boots Once it boots you're presented with, you know, kind of a basic style older as I Have sent around for a while linux style installer Press enter next, you know pretty basic here check for existing products I've loaded this demo before so it's going to find an existing one Now one of the nice things about how this works We're going to perform a clean install, but it also sees backups on here when you do the upgrades You actually will upgrade them when there's full releases the same way you put the drive in and you install over the top And it performs an upgrade, but it keeps a backup This is a great way to do it because whenever you're Doing this you can always go back and just pop the drive in and if it doesn't go well restore from that backup But we're going to go ahead and delete and put a clean installation in here We're not worried about the backup now hardware wise This has got an 80 gig hard drive in this is the demo one the machine the hardware we built it on has 120 gig ssd in it I put two in this particular System to show you that there's an option comes up for software raid So I do have the ability if I wanted to hit software raid and I can raid two systems together Or two drives together to make a raid if I wanted to we're not going to for this demo I just want to show you that was an option there and if you're using enterprise hardware You can also present a single large drive Like with the del raid utility would be an example like I did in my del r630 review to xcp and g and just have it Install there now xcp and g slices a part for the operating system and will take the remaining hard drive Whatever the size that is and leave it for storage for the vms as a local storage There are ways later to add more storage to it or you could start putting all the drives together themselves There's a couple different options you can think about for doing this But you at least want to install it on one drive Itself maybe one smaller ssd that's on the system, but it'll still take the leftover It doesn't use and allow you to use it as local storage Now this is the part where it's going to ask about the local storage essentially We could merge these together and put them both in here in storage for now Which for simplicity we're going to do it as ext because this is going to match the physical hardware when we get there I prefer the ext file base maybe slower, but then provisioning I can't really say and you can go look into forums There's barely any noticeable speed difference between lvm or ext Especially because now the newer versions are using ext4 the previous versions were using ext3 So I don't think there's much of a difference anymore But my preference because i'm more familiar with managing the ext system I'm less familiar with lvm is ext plus it supports the thin provisioning Press okay local media scanning Live dangerous and skip verification of the media Give it a password, but it doesn't really matter because we're going to change it And this is just the demo for install Static is probably your preferred so 192 and 683 dot 102 210 Whatever works for you match it to your network settings when it was free you can work this as dhcp if you want Um, but it's probably easier to find the system if you statically assign it to an unused address Give it a name dns servers, whatever your preference is Choose a time zone We'll skip this for now, but you can put your I think it is it But I don't think that's the right one put a proper time server in there and hit install This will take a little while it's going to go through the installation eject and reboot Depending on speed of your hardware this may take about five to 15 minutes to install Like I said wild variation comes with how fast your hardware is really fast hardware and install faster So now we're going to get out of this and show you what the next step is to forgetting to set up All right, once the system's loaded you go to HTTP 192 168 3 dot 210 the ip address we assigned to the system It says welcome to xcp ng 8.10 now as of 8.1. Like I said, there's no management interface here to actually Manage the system, but it gives you some options for a quick deploy your download before we do either one of those I assasaged into the system. So root at 192 168 3.1 3.2 10 and we're going to do a yum upgrade Okay, no updates on this is actually because I've already done the upgrades on here The first time you log in there's probably going to be some updates depending on when you downloaded What version you downloaded and if there's been any updates But the good news is from the command line And it's better to do it before you load anything just yum upgrade It runs through the upgrade process and then you just can do a shutdown Dash our now and it'll restart So we're also going to pull this up now if you were to plug in directly to the machine that this is running on right now And this is what you would see the status display You know network management, etc. And this interface This is what's actually on the screen right now as far as like if it booted up But you don't really have to do anything with this and pretty much the machine right now is sitting in our lab And is headless. It doesn't have a monitor plugged in at all. So let's go back over here And talk about quick deploy So the two options for management are zen orchestra the older one And I've talked about this in my older videos But I don't really use it at all anymore is xcp and g center As a matter of fact with the 8.1 Please note It makes sure you have the latest version because they just fixed a bunch of bug updates where it was trying to Pull some of the wrong updates for it This is the lesser maintained and lesser featured system and it doesn't have as many features as zen orchestra does So zen orchestra has everything like it's a pretty extensive Everything from backups and continuous replication and all the different bells and whistles including a lot of advanced networking options But of course they have a paid version versus a free version Let's talk about that when you run the deploy it's going to run Right here and we'll put in the password Connect and put an ip address and this is really slick It goes through here. It you can see all the different networks that are on this and we'll get to those in a second It's going to see normally just the main network You put an ip address you want to sign to this and it's going to load and launch the free version of zen orchestra And they have a comparison for what's in your free package and things like that limited support But it does work You don't get all the cool auto patching rolling snapshot full backup features and all the cool reporting features On the starter you do get 15 Days of premium included with it, which is pretty cool. So you can actually use it to play around and see what all the full features are But being that this is a lab The concept is let's build it all from sources now. They have all the details and all the documentation in their Documentation here on how to build up from sources. It's actually really cool And they did a nice job of documentation overall But they also like I said details how to do this or You can go here and this is the zen orchestra Updater zen installer from sources and this is a github script I have full instructions on how to do and use this on my video that i'll leave link to how to build zen orchestra from Sources using zen orchestra install updater. I have people say they can't find the video I don't know how to make it any clear, but I will link it down below Is it's pretty easy to find for how to build it from sources using this update tool works really well It makes it really easy. They also have docker images if you don't want to take the time to compile So let's go over here The first thing you want to do after you have it loaded is get zen orchestra running and that quick deploy is probably an easy way To do it once you have that running you're going to want to build a vm But you're probably asking well, how do I at least get one iso on there so I could build the vm Well, I do recommend doing the quick deploy for it and I'll show you how to set up local isos. This is actually Not my favorite way to put these on here, but if we're talking about a single lab server This will definitely get you started. So this is how you create a local iso repository Now we're going to assume you already loaded the xo a appliance and the xo a appliance system the free one With the quick deploy here completely will let you do this without even activating the trial You can add this local I figured I'd show how this works real quick When you go here to create a repository and we'll walk through the system. So we're going to go new and we'll say new storage Select the host which is the xcp ng lab And we're going to say we want a local iso repository path to directory. Well, we're sshed in over here We'll call it local iso local iso now we're going to go ahead and find something to download And i'm pulling this from the devian page. So we'll just copy this link here We're in the iso folder and we'll just type uh w get to pull it But you could use whatever tool to get this in here What we did is in the root of this system. We've added this particular iso Now the problem you may run into is there's a limited amount of storage in the local system And that limited amount of storage means well You're not going to be able to put too many isos in here and you could cause problems So this is not my favorite way to do it But it is a way at least you can start getting some isos on the system But I wanted to show that this is possible and how this part worked To an ls and pwd. So we're at local iso right here Let's copy that and we see that there's one devian iso in there So where's the path? Local iso we hit create. Well, actually gotta give it a name Call it like local iso here create Oh, please fill out the description There we go Let me look at what drives are in there. There we go pretty much One disc one simple system in there not a big deal If you want to put a few more in there, but like I said, there's a limited amount of storage That's how you would do that and then to create a new vm you go over here to new vm Select the pool select a template and we're going to say Devian 10 because that's what we downloaded in there and then you would select the iso And there's our local iso now. I obviously have a lot more isos in there We're going to talk about the better way to do it. So right here's that devian one If we wanted to go ahead and create it and we could go through the load process and build a vm Not going to do that. We're going to go back over here to storage pools And let's go get rid of the local iso one remove it Oh Gotta disconnect it. Yep Yeah It's stuck because there went something it was stuck because I thought something was using it takes a second and now it's gone All right, so if you go back over here to storages I have this free nas iso the way this got on there pretty simple this is A free nas server with a bunch of isos in it now this can be this is just as smb mount But this can be done in a few different ways. So we're going to go to new storage post storage name Select the value and you have local nfs or smb You put it in the server name now This can be your windows server if you have all your iso files on a windows server And you have an open share or a share with the username password on there You put all fill all this in and create and it will read all those on there It only has to be a read only share because it's just pulling the iso files. So This is another option for getting all the isos in in the better option Especially because I have so much storage on my free nas now. What about adding Other local storage well I'm not going to dive too deep into that because we have some available local storage for things But kind of the same thing when you're adding a new storage So we're going to go ahead and look at the existing storage again And we'll look at this right here. This is my free nas name dozer And mount dozer been left. So let's go ahead and show you how you add one of those. We're going to go new storage again Select host Free nas nfs It's just an nfs share the basic options of nfs share. We'll log in and look at those real quick We'll choose nfs 192.168 Default nfs version Get this little query and look it found all the different ones that are available on there That I have including the lab vm Which is actually not a good idea to add the same one twice that will probably create some problems So i'm not going to do that but this you kind of get an idea That's pretty easy way to do that now What does it look like just really quick and free nas and you can do this with Synology you can do this with really anything that supports nfs And here's the zen lab vm share. We're going to edit Advanced mode check the box that says all directories make sure it has permission to Read write access into that storage. Like I said, whatever you're using for storage that will work a few other options that are inside of the zen server We're going to go back up here It does have and i've covered this before how to set up iscazion there lvm local zfs local So they've built in zfs if you have a bunch of drives you can go to the command line and time to get over zfs I believe you can have a separate video on that lvm or simple ext local So if you just have a device you can just point it at that device and it will create an ext file system Where you can create an ext file system on it and point it at the device after you create it that you've attached So there's plenty of options to dive into and your documentation is pretty good on that so Once those pieces are taken care, let's jump into the networking part Now there's two pieces to the networking It it's sometimes a little bit confusing But let's get break down and explain it by starting over here This is my lab. This is my xcpng lab system running an amd I put the processor because someone will ask it's an fx 83 20 with 24 gigs of ram in a single 120 gig ssd on there So the hypervisor and all the vms live inside of this one physical box The network card in here happens to be an intel x5 20 10 gig card There's a lot of different 10 gig cards that work I like the intel ones because they seem to be very very compatible This is going to my unify switch My unify switch is set up as a trunk port Which means all vlands are passed across here. That's an important thing to remember So all vlands and that is also the native network is the 192 1683.1 network That's native vlan one and I'm bringing this up because we're going to talk about not just how to create a network But also how to create a couple of vlands in there But it is important to know that it's a single physical network connection But we're going to create vlands inside of here and show you how they work And they're already defined either in the unify switch and the pf sense or just the unify switch That's going to vary with some of the switching equipment But at least you should be defining those vlands within there if you want them to work on the ports We're also going to talk about the private networking features that are in here Let's go back over to this And look at kind of the ip layout of what we have set up So my pf sense Manages the 192 683.0 network and the 1272 network. I do have defined but not managed in pf sense It's only defined as vlands in my unify Vlan 20 vlan 100 vlan 200. I just created these so I have some extra vlands for Doing things where I may want something in the physical Side of the server to come out to a physical port. I may do in those later in advanced videos I just want to mention exist, but you do have to have these defined in your switching equipment And that's because we're going to be running pf sense inside of here as our lab Which you've seen me do before if you watch this channel And that's how I get pf sense inside the system to talk to outside systems is by Splitting off these vlands, but physically the lab servers like I said one physical ethernet cable connected at 10 gigs So there's the assignments we have here's the lab server itself the xcp ng And this is a virtual machine running on it the zen orchestra and it's at dot 28 So let's dive into the networking side of things now Please note. I am using the fully compiled version Like I have him reference to my other video of zen orchestra that being said I did compile it with the flags and you can look through the details when you set it up Or use a docker image to say make sure all the plugins are there This is important because if you don't have some of the plugins specifically the plugins related to the sdn controller You wouldn't be able to do some of the steps in this video because the sdn controller has to be turned on So if you did compile it that way great You just have to turn the sdn controller on if you try to create a network without That turned on it prompts you with a link to the instructions of how to turn that on So let's go over to the networking under host And we can see the network interfaces right here This is the one that's assigned the other ones can all be left alone You assign them to the VMs But you don't have to assign anything more than a single IP address within the actual physical xcp ng machine But you notice I can't edit these networks. So that seems kind of odd, right? Well, not really And I ignore the fact that for my lab demo We did set it to tcp instead of static because I wanted pfSense to handle that So if anyone wants to point that out that I said set it to The other way. Yes, you can set it to static But I choose dhcp that way I can manage everything with my pfSense just fyi and you can see it's connected at 10 gig But then we have vlan 20 10 gig storage. Let's go ahead and add another network Now even though I can't edit them here Let's talk about exactly how we add them and where they end up So you go over here to network We select the pool and if we had more than one pool collected It would give me all the options for the other pools You can see which ones are plugged in and eth0 is the one we want to use And we're going to call this vlan 69 Because the vlan tag is it is not the mtu. I'm sorry 69 You can leave the mtu at default if you want to tweak it They do give the option to leave it at default unless you know what you're doing there So we just named this vlan 69 to make it simple. We'll go ahead and create network All right, and we're going to do another new network Select pool It does have bonding options if you were to select multiple interfaces That is an option in case you want to know what that is up there So you can bond them together studio 100 create network And we'll do one last one just so we match what we had in the sheet over there Over here to network Actually 200 copy and paste the wrong thing here 200 200 Now we're going to go to home pools And we edit all the networks from the pool. This is where you can actually change and Set settings on these and use them and rename them to something different if you want and the reason you Edit them in the pool is so all the hosts have matching Network interfaces in that pool and let's show you that in production So if we go over here, we go over to my production pool here And we look at the network interfaces and let's say we have this this is dot three general network Not in use studio 200 lab network. Let's edit this one to say lab network. So we'll put this as lab network And I have in here go to the host You can see that network is now in this host and that network is in the other host as well So what this allows you to do is create it in one location And this automatically gets propagated to the other ones pretty straightforward But if you're even if this is a host of one, it's still the way the practices are of doing that one important thing The network order has to match in order for this to work properly So eth zero is plugged into and trunked all on my main system just like it is on my lab system So both of my servers the xc xcp and g running on the 630 and the other one go over here back to host 720 both have a matching set of network interfaces plugged in the same way for the network It's there's ways to rearrange them. It can get a little tricky But generally if you're putting them in you want eth zero on each computer to be plugged into the same Network that way if you pass any vm between there's not any weird things that happen And same goes for each subsequent network interface the cards can be different types of cards They should just be plugged into the same network interfaces So it's a little side note on when you're building the machines, but it's something that is fairly important to do When you're doing that because you're naming them all in the pool. All right back to the system here So now that we have those networks built, let's talk about building one more network and that's a private one So the private networks are different. So the vlands work fine for When you have the system and we'll go open the system requirements here the vlands are for when you want a Network of course to pass through your network and switching equipment But sometimes maybe you don't necessarily want it to openly pass through there and there's a couple different options So they have vx lands and encrypted g re tunnels I've already got one vx land created on there and you can create one vx land or one g re tunnel And it has an encryption option and you can if there was more than one pool We'd have the add pool option And these are kind of neat because what this allows you to do Is have an extended software to find networking controller and you can find this they have a lot of information on it But one stn controller three different pools Many different hosts that can talk to each other through an encrypted tunnel Now this is an interesting way you can build out a pool and have inter communications between the vms on tied to a back end vx Land that's all encrypted and you're able to pass this data back and forth as if it's kind of a Almost like a vpn, but it's actually at the network layer So everything goes across there and this is sometimes used in data centers But when you're building out something kind of specific for yourself and you want to play with a lab and you say I want this locked down Don't let it leave into my networking equipment, but this particular vm needs to stay behind Whatever firewall we put in front of it and we will demo how to set up pf sense in front of it That's one of the other options they have in here. Um, it's pretty pretty neat I'm not going to dive deep into it other than yes It's pretty easy to create and pretty easy to maintain and the reason you still tie it to An adapter so it knows what adapter to leave and go out through the system when you're setting it up So uh, that is definitely an option in there. All right Let's go over to pf sense now And we're going to say filter none to show all the vms that are on this machine right now And we'll go over here to the pf sense lab setup and let's look at the networking So we have the vlan 69, which let's just change it So we'll have it plugged into 10 gig native, which give is it a 192 1683 dot address on there And then I said studio 100 and studio 200 now the studio 100 200 are not defined in my pf sense They are just vlans defined in my switching equipment And this allows me if I want to put any ports on my switch To trunk it to that particular Vlan tag I can say tag 100 tie it to one of the switchboards And then the pf sense in here will then feed any devices that are outside of my network for my lab testing And this is how we do some of the demo videos that you see in our studio So we'll go ahead and fire this up now as far as getting pf sense on xcp ng They have a tutorial right here right in their blog post about how to do it They have entries in our wiki on how to do it and I will comment on this There's two approaches to setting up vlans and I definitely By far as it says here the easy solution and perhaps the officially supported approach for xcp ng When you do this dom zero hands all the vlan tagging what that means is As we were doing it and creating all those network interfaces Each one of those network interfaces is attached to the main xcp ng system and in it's handling the vlans And pf sense which should be booted up now it is we'll go ahead and log into it It does not see these as vlans, but as actual adapters So by handling it inside of here and we'll log into pf central quick It does not see these as vlans here. So if we look at interface assignments, we go over here to vlans There's no vlan tagging going on here. Everything's treated as an interface So instead of adding more vlans to here even though they are because there's only one physical adapter on our xcp ng machine and everything else is trunked out with the vlans And that's how we're slicing these up to build out the separate networks You don't actually define them here. There is some information on here and ways to do it But it's it's kind of I don't know. It doesn't seem as well supported It's more challenging to do that and I don't think you gain any benefit from it Other than you'd be able to define and play with vlans inside of pf sense here But that like I said kind of a one-off thing I mentioned it But I prefer to do it the way that I have this set up But when was the first interface lan lan to Ignore this this is for another demo, but these are the interfaces that we have attached that we have right here So you can see that the second one down xn2 has the 40 network on pf sense So we should be able to go over here Network and we'll attach it to the studio 100. So now we've attached this to studio 100 and we'll boot up this Debian server Debian on my labs server here And it now is behind the pf sense and should get an ip address once it boots Boot it up. Let's log into it And it has 192 168 40 dot 119 we go over here in a pf sense services dcp server Hey, look there is the Debian lab assigned 192 168 40 dot 119 Pretty easy enough to find there. And what if we wanted to change it? What if we want to put it on the other network? Well, it's actually pretty easy. We go over here to network We'll change it to the studio 200 option And now it has 10 dot 10 dot 11. So that was and we'll just do over here Go back over here to pf sense. You can see That's the other network inside of pf sense the xn2 network adapter that's attached to that pretty straightforward to do Now the only tricky problem I've had and pf sense might get angry if I do this is it. Let's go ahead and change it So let's try that lab vxlan sometimes pf sense Yep, it didn't like that. So let's see if it actually worked Sometimes you do have to change When you change the network it after restart pf sense not all the time but some of the time I've had this happen Yep, it still thinks it's disconnected. So you just have to reboot it. So we'll reboot pf sense real quick and It'll come right back up and running. So we'll just go ahead and reboot it It doesn't like the network adapters on pf sense being changed without a restart I'm not sure what the work around for that is or if there's some driver I'm missing but I did follow the instructions and I do see that happening It does have as you can see and it's stopping right now the zen guest utilities running in the background But that still happens. So we'll let this reboot real quick All right, pf sense is rebooted logged in And now we change the network to this lab vxlan So we're not going to go through the whole demo of extending this vxlan across other pools But just to show you basically if we take and go to the vms here and now this server We're gonna move it over to that vxlan here There we go And we still have the ten address and We should be able to get out And we're on the internet so we can ping things we can get out on the internet things are resolving Networks are really fine now the one other network type that's worth mentioning in here and we can go to the pools Exhibiting lab go to networks is the host internal management network networks On which guests will be assigned a private link local ip which can be used to talk to the zen api These are kind of neat because this is local only to one physical host So you can tie things to this particular adapter, and this will allow you to have communication Only inside of this particular machine So it doesn't have anything else But you can tie this once again to pf sense and then build your networks behind it and everything flows back out of pf sense Now the other question that comes up a lot is what if I want to virtualize my pf sense and run it inside of here Well, if you may have noticed I labeled a couple of these not in use not in use And that's just kind of a general house cleaning I do when I set them up if I don't have and there's nothing plugged into These other network interfaces like eith 1 and eith 2 our system is not in use But what if I wanted to use them and what if I wanted to use it for my cable modem to plug into my virtualized pf Sense so I can have it all virtualized my self I prefer to run pf sense on real hardware that way if i'm ever troubleshooting something I did inside of zen server and it didn't boot for some reason I have easy internet access but if you insist and want to run it this way you could call this cable modem And the reason you might want to call it cable modem a b a b l e modem Is you would take this and assign it to the wan And calling it cable modem would help you Hopefully not accidentally assign it somewhere else. So if we were in here and we seen it and we go to networks And If you if you assigned it cable modem You would go, huh? I'm assigning something a network called cable modem So if you label like that it's a good clear way to let you know where to assign it to and where would you assign it? pf sense pretty straightforward as you go here And you would change the native network and we're using a native network Because this is essentially double-natted as my lab system, but I would change this to cable modem because vfi vif Number zero is right here. It's the first network in it or if you're looking in the council You'll see that it's x and n zero inside of pf sense and assigned here via dhcp Now in case you're wondering can't you assign more than one thing to your cable modem? Yes, and it's essentially the same as when you come out of the cable modem and you plug it into your switch Any type of switch and then plug more systems into it What happens next is really based on the support level you have with whoever your cable writers Or really if you're doing this and you're getting like let's say a fiber handoff that does give you a whole block of ip's Yes, you could assign them all through here or even have xcp and g and have that one port that we label cable modem Attached to multiple pf senses or multiple different things that you have virtualized inside of here Maybe you want to have a server have a direct public address. That's another way to handle it So there are some different use cases that do work if you want it publicly done Just be careful when you're doing that because what you don't want is because obviously it's so easy to go here and Go to the network and swap these two really any network pretty quickly You don't want someone to accidentally do that and accidentally take a server that's supposed to be private For local communication and just throw it out on a public internet But that's pretty much it there for setting up the networking pretty straightforward Now anything else you do from here I've gone and got videos on how to do the backups how to do the config backup restores settings setting up the remotes and There's a lot of other features that are in here that obviously you can play with There's importing vm's importing just a disc and setting up, you know New servers new storage new vm's and I have other ones on how the entire ha process works where we took Several servers tied them together to a single resource pool put it in ha mode and showed how it auto failed Over between them and because this is a self-compiled version. Like I said, it does have any Support if you want to use in production they do have a purchase option And if you decide if you're playing with this in your lab and you want to run this at your business There is paid support for both xcp and g and zen orchestra and support packages available That do help out the developers of this that is the way they monetize is they make money selling support packages for The whole system if you want to use it in production, but it's a pretty awesome system I've been using it for a while. We've got a lot of clients running this in production I'm really happy with it. It's been an excellent project and 100 open source So all the features and I've talked about some of the other ones details before like The v-motion that you see in the esx esxi world does work inside of here They have the zen motion as they call it so I can move and transition live servers between pools and a lot of those other bells and whistles including Doing snapshots and snapshots with memory so you can snapshot something in place and grab live memory for backup So there's so many features I could probably go on another hour But I won't if you look through my videos I have a few more on there and of course they got plenty of documentation You can go through inducing your own reading and they have a very lively community and forum where you can also have discussions as well So a read and thank you. Hopefully this was helpful And thank you for making it to the end of the video If you like this video, please give it a thumbs up If you'd like to see more content from the channel hit the subscribe button and hit the bell icon If you like youtube to notify you when new videos come out If you'd like to hire us head over to laurancesystems.com fill out our contact page And let us know what we can help you with and what projects you'd like us to work together on If you want to carry on the discussion head over to forums.laurancesystems.com Where we can carry on the discussion about this video other videos or other tech topics in general Even suggestions for new videos. They're accepted right there on our forums, which are free Also, if you like to help the channel in other ways head over to our affiliate page We have a lot of great tech offers for you and once again Thanks for watching and see you next time