 So networking on ZenServer. Now the purpose of this video is to show you how the networking works on this ZenServer, but I'm not going to get into the V-switch controller. I'm going to do a separate video for that because that's going to be a little bit extensive. And V-switch controller takes this to another level allowing a virtual network to be created across multiple ZenServers to create virtual switching fabric. So this video is going to be limited to what you can do with a single ZenServer with the built-in virtual networking options on there. And just giving an overview of how the networking works on Zen. Alright, so the network settings at the top are the networks available to the ZenServers, the VMs themselves. So that shows up here at the top. At the bottom is the networks available to the Zen machine, the physical layer, and how you have that map. So one of them is storage because that's how it attaches to the storage drive and we're going to show you these real quick. One is the storage network. This connects to the storage sides, the iSCSI in this case on the FreeNAS box. And this is the management interface. I could make these both attached to the physical, what I call the dot two NIC, because it's on a network that ends in dot two and a dot three NIC. So you can control this. And if you had more network interfaces, you'll have more options in here. But this is only affects the ZenServer in the physical layer of the Zen hardware. And these network settings do not reflect the network settings for the virtual machines. Matter of fact, the virtual machines, you don't assign the network settings here, you just create the available network form. So I've got this one called Tom's Land of Zen. I'll show you how I created that. You can see the properties of it. And this land only exists on this Zen two server. And I spelled server wrong. Let me fix that. Nice thing is, even though I've had this assigned, because of the way it uses UUIDs on the underlying, whatever fun creative name I come up with for the Zen server land that I created, it automatically will fix all the virtual machines it's attached to, and my typo will be fixed. Now, this is where the NIC options come when you set these up. Internal means phantom internal NIC, as in it doesn't physically exist, but it does exist between the virtual machines. So here's that internal NIC and automatically add this network to new virtual machines. I don't want it automatically added. You can. That's just a preference. When you create a machine, it just automatically gets added. You can always change it later and I'll show you how that works. Now, when we want to add another network, we can even say a single server private network, create a network that does not leave your Zen server. That's why I did to create this. And I'll show you was create another one. Second. Can type today. Virtual network, the net. And add a description on the same thing. And it's done. We've created a second one. Don't really need a second one for purposes of this, so we'll go ahead and remove it. Now, a couple of quick options to show you what else is in here. External network. You can create a new network and we'll call this VLAN 2. Because you can create attached to one of the physical network cards, but then give it a VLAN ID of another one. That way you could create across your switching fabric a specific route to a virtual machine only across another VLAN. So those are the other options that you do have in here is to use the VLAN options. We're not going to do that today, but it's pretty straightforward. If you know how to use VLANs, you just create one and then it creates a nick for a specific virtual machine VLAN. So that way it attaches directly to that for other advanced use. Another option in here is bonded network. So if you have a couple network cards in here and you want to bond it, you can create this, check the boxes. I'm not going to do it right now because it'll screw some things up. But you could set this up to be bonded and then create what is a single network to the virtual machine, but it's actually a multiple of bonded networks here. But back to the virtual private one. So this LAN only exists on this Zen server too. Tom's LAN of Zen and how we attach it to the virtual machines is really simple. Go over here. I got them started up and I'm in networking right here. So we're going to go to properties and you can see it's attached to the dot three network like that. But before I go there, let me show you what the IP address is. So we have 192.168.3.148 because there's a DHCP server on the dot three network as I call it. And that's the address the case. So without restarting the virtual machine, you can do this on the fly because the way it works is not changing out the network card. So it doesn't have to do anything to the virtual machine. It's kind of like changing where it's plugged in into the server. So we're gonna go ahead and go to properties. We're gonna go to Tom's LAN of Zen. It's gonna take a second. Go back over to the council and now we have another network address. 192.168.1. You're probably asking how you got there. No problem. My usual answer, I spun up PF cents and gave it two network cards. The first network card pulls from the dot three network, hence by the PF cents, which was XN0. XN0 is the first network card. Network card zero. Network card one. Tom's LAN of Zen. Going to council here. XN1. That's how free NAS names are inside here is assigned this address and has DHCP running. So it's a standard PF cent, something special loaded on here. Actually, I didn't, you know, it does have something I seen was spilling up that it seems to detect it's on Zen. I named it Zen PF cents. But now I have all the functionality of PF cents to put in front of any servers that I attach to this network. So they have full access to the PF cents. And this network only exists on here. So if you want to create your own testing environments and things like that. So you create your own PF cents and then create a series of virtual machines that you want to set behind PF cents as a firewall. And I'm just using this example. You can really learn any firewall you want that would run in here. But it's that easy to do that. And that same thing works for Windows 10. So actually what IP address it has now. So this is also on the dot three network. So this is my Windows 10 box. Go to here networking, you see it's on the dot net three network and go here properties. Tom's land of Zen. Hit okay. It's going to take a second. And it's got a new address. It's now on 192 168 11 network 100. And it's a sign in of course, because this is on PF cents, I can even log into if I want the PF cents box now because I'm on the inside of that network. And I have all the controls. Now this is really good if you want to do testing. And let's say you want to you create a virtual network, you want to create a virtual machine, you want to do all the full monitoring and PF cents and have it on a nice quiet network with only one thing attached for monitoring. Easy way to do it. Now the other cool thing about the way this works is you can create more than one you can actually create a series of networks on here and go as deep as you want to go you could actually layer this in different layers because you create one and have it pass through to another one and pass through another one. There's not I mean, there's probably some limit to how many virtual networks you can create in here. But if I wanted to add another private network, it's as easy as going here and adding another one. And you can then tie them together using PF cents. So I create a series of virtual lands, and then tie it to PF cents and give it multiple network interfaces. So I can actually have multiple private server networks on one physical machine without adding a bunch of network art. So it's really great for a lab environment, where you want to do a lot of testing and lock things down and put things behind their own firewalls and work them that way. So pretty cool system for doing this. It's really not that difficult. I like the way it handles the networking pretty straightforward to do. Hopefully this is helpful. I'm going to do a deeper video on the whole Zen v switch system, which is a virtual machine you load in the Zen that allows you to create these private networks across multiple Zen servers. And then you can actually create the private network on one Zen server attached to other devices across another one and you get a lot of features for that. So if you want to build a larger lab environment with virtual switching, that's something you could do on there. It's pretty novel. I haven't tried it yet. It's something I'm playing with. They don't have a good use case for it at the moment. None of my clients, my clients who are running Zen server just running Zen server running multiple Zen servers at the moment, but I'm going to be building multiple ones here just so I can do all those testing and finish my lab environment and some stuff I'm working on here for some more videos. So if you like the count in here, like and subscribe if you have other questions or suggestions for my Zen server videos. Let me know. I know someone asked about hardware video. I will be doing one of those and talking about some of the hardware for it. But hopefully that is helpful on the networking. And once again, thanks for watching.