

Since I already have these ESXi hosts connected to another SAN on the same network I should just need to add the FreeNAS storage interface's IP to the Dynamic Discovery list, right? I've added additional hosts to the existing old SAN - set up the virtual switches, done the network port binding, etc. I set an Ethernet interface to the 172.16.1.0/24 LAN for management, and one to the 17.31.0.0/24 LAN for storage, and connect them to the correct switches. There's a bunch, they're all basically the same, and I hit the same problem no matter what I do: the hosts do not find the zvol datastore when I scan. I followed the guides I found online for connecting ESXi hosts to iSCSI shares on ZFS. We have other solutions in place for things that need fast disk. This will be a production environment, but of non-critical systems that A: should be backed up to the old SAN and B: can be rebuilt from templates with unfortunate but acceptable downtime.

(There is a frankly terrifying lack of backups right now.) It doesn't have to be fast, it needs to be big and reasonably resilient. The new SAN is intended to take over for the old one so that it can be safely "reconditioned" and put back into service as a backup datastore. Non-critical VMs run mostly on the old SAN or on HDD local datastores on older hosts. (Probably not the "best" config, but there's a reason for it based on my admittedly limited understanding of ZFS.)Ĭritical VMs run on local datastores in specific hosts with RAID'd SSD drives. The new SAN is a Dell PowerEdge R510 with 128GB RAM and 12x 3TB 7200 disks in RAID-z2 running FreeNAS 11.2-U6. Everything runs via 1Gb/s Ethernet - the SAN and the hosts mostly run 4 cables each to this switch. (yay) This is set up on its own switch which is a pair of stacked Dell Force10 S25 (stacking cables in the back) on a 172.31.0.0/24 storage network. We also have an aging Dell EqualLogic with about 17TB in RAID 6 with a dead drive. We have over a dozen ESXi hosts that are (thanks to me) now centrally-managed across two sites with a pair of linked vCenters with SSO and all the trimmings. (Hence "JackAlltrades".) Put it this way - I own my own hardhat and I'm not afraid of Linux.
#Best to use nas or san for vm esxi 6.5 software#
I know VMware decently well and know my way around most tools ranging from software to hammer drills. I'm figuring most of this out as I go along.

Basically no one documented anything useful and so no one really knew how anything work and just duct-taped and baling-wired stuff on top of existing systems. there are so many things on fire.īasic background - I show up to solve problems because this company has suffered high turnover in system/network admins for the past few years.
