ESXi 7.0 Mid-August Update

Since my last post, there have been some developments. Booting from USB went from being inconsistent to being a non-starter. So, back to the old faithful hard drive boot. I have four internal 300GB SAS drives in a RAID-5 configuration. Since I have my VMs on the Synology NAS using iSCSI, the internal drive array was never used for much. Sometimes I would have a specific VM that wanted to make sure would be up in the event that the NAS went down such as the UniFi controller. I realised that isn’t a real worry. Along with having backups on both NASes I have an offline backup where the configurations of pfSense, Unifi and ESXi are kept.

ESXi backups are important as noted in previous posts. For quick reference (maybe mine!) the instructions are provided by VMware in the KB article How to back up ESXi host configuration. More steps are needed than pfSense of UniFi but it is something I do on at least a monthly basis or before and after I make any major configuration changes.

I’m not sure if booting ESXi from USB is an issue with my DL360p Gen8 server, the USB thumb drive (and I tried several) or ESXi 7.x. I do know that booting from the internal drive array does work and I’ll stick with that.

I also updated to the most current patch level of ESXi after the change to booting from the internal drive array. The update to ESXi 7.0.2 (build number 17867351) went flawlessly – although as slow as always. A great resource (especially if you do not use vSphere) is VMware Front Experience‘s VMware ESXi Patch Tracker. Great resource – including step-by-step instructions in a pop-up.

Posted in Uncategorized | Leave a comment

ESXi 7.0 Upgrade to Update 2 and iSCSI

I realized last night that in my efforts to get ESXi up and running, I had installed the original release of ESXi 7.0. Since I had taken Friday off work to take care of a few things that needed to be done during the weekdays I decided to upgrade ESXi to Update 2. It also allowed me to test my theory from my previous post.

The update worked as planned (and boy-oh-boy are updates slow!) but was successful. As I expected the iSCSI share did not show up in ESXi. Let’s check the NAS and see if the targets are still there and if the ESXi server is connected. Yep, ESXi is shown as a host in DSM.

Okay, ssh into the ESXi box. Can I ping the NAS? Yes, working fine.

Log into the ESXi console (again, I’m not using vSphere). The software iSCSI sees the host and the target. But, no iSCSI devices are showing up under storage devices and obviously the datastores are not present.

Let’s try my theory from the last post. Try esxcfg-volume -l and get the UUIDs. Well now, iSCSI volumes are not showing up. Let’s try a few more pings to the NAS, rescan the devices. Nope, not working.

Time for some deep thinking. No panic this time as I know that the VMs are still in the iSCSI LUNs and I just have to get them mounted. And I have good backups!

Some more Googling and the first result from Reddit (vSphere 7.0 U2 iSCSI not working with older HP Lefthand SAN) seems to have the answer. It seems that the issue is around the IQN and how ESXi is handling this. I deleted the ESXi host on the NAS and re-created it. A rescan of the storage devices showed the iSCSI LUNs. I then did the esxcfg-volume -l and mounted, using esxcfg-volume -M UUID (with the “M” rather than the “m” option), the two UUIDs. Bang, the datastores reappears. While the article is for upgrades and not reboots, my gut is that this problem will persist until the bug is squashed. I haven’t tested a reboot because this is a pain in the arse and I have other things I have to do.

From the Reddit post, there is now a KB article from VMware on this issue (iSCSI adapter IQN may change during the upgrade of ESXi 7.0 U1 (84339)). I didn’t see the workaround (I’ll try it if a patch not available and I have to shutdown the ESXi or NAS) but here is that workaround example from the article:

To work around the issue:
Prior to the upgrade, use the esxcli get and set commands to set the generated iSCSI adapter IQN explicitly. As the IQN is a user setting it won’t change after the upgrade.
Get the IQN details:
$ esxcli iscsi adapter get -A vmhba67

vmhba67
   Name: iqn.1998-01.com.vmware:w1-hs3-n2503.eng.vmware.com:452738760:67


Set the IQN details:
$ esxcli iscsi adapter set -A vmhba67 -n iqn.1998-01.com.vmware:w1-hs3-n2503.eng.vmware.com:452738760:67


EDIT

I couldn’t wait for the next time that I needed to reboot the ESXi server. That is probably a good idea given that I probably don’t want to have a number of things going on at the same time. I applied the VMware KB work around and then shutdown the VMs and rebooted the server.

SUCCESS! The iSCSI datastores automatically came up. A gin and tonic with lots of ice may be in order!

Posted in Uncategorized | Leave a comment

Importance of Backups and Wednesday Trials and Tribulations

On Sunday, I upgraded my Synology DS216+II to DSM 7.0. I followed the DSM 7.0 reviews by Robert (Robbie) Andrews on NAS Compares and made the plunge starting with the DS216 – my backup NAS. Things went well so on Wednesday evening my main NAS, the RS1221+ was upgraded. As my VMware ESXi 7.0 has its VMs on the RS1221 using iSCSI, I shut down the ESXi server because past experience has shown me that the remote datastores “disappear” when the NAS shuts down and won’t reappear until the ESXi box is rebooted. (More on that later, I may have found a workaround.)

Anyway, the RS1221 DSM 7.0 upgrade went well. For both the DS216 (which is technically underspeced as it only has 512 MB of RAM and 1 GB is recommended but it is on the Synology compatibility list) and the RS1221 the new interface is really snappy. Login is much, much faster. So far, so good.

After about a half-hour – enough time for the RS1221 to “settle in” – I powered on the ESXi server. And discovered that my iSCSI datastores were no longer there. First thing to check was the RS1221 to make sure that iSCSI was running and the LUNs with the VMs was still there. Ok, everything fine there. I could see the ESXi host connected on the RS1221.

Back to the ESXi server. Under storage I could see that the Software iSCSI adapter was there. So were the iSCSI targets. But no datastores… Ok, rescan. No dice, still no datastores. Time to reboot.

And… ESXi would not come up. It could not find the internal USB thumb boot drive. A moment of panic until I remembered I had (not recently but recent enough) backed up the ESXi configuration (twice – once to the DS216 and once to the RS1221). As I do not use vCenter, I had to backup the configuration from the ESXi shell. This will save a lot of time and effort instead of starting the configuration from scratch. That information can be found in the VMware Knowledge Base: How to back up ESXi host configuration. Time to grab a couple of new USB thumb drives (one for the installer, one as the destination) and make a new boot drive.

And… I could not get the new installation (not the installer) to boot. I could boot from the installer thumb drive and the installer could see the destination thumb drive and install ESXi. But there was no way that the server would boot ESXi after installation. Manually selecting the thumb drive didn’t work either. By now it was getting late and I had to work in the morning. Off to bed.

Thursday evening, and after a lot of trial and error I remembered that the three thumb drives I was using as targets have been used as FreeNAS/TrueNAS installers. Now, TrueNAS uses FreeBSD as its base and that seems to do some strange things to the signatures on the drive. Even with deleting the partitions and formatting the drive as FAT32 didn’t help. Weird. Finally, I also recalled that when I was first installing FreeNAS I had a similar problem with disk signatures. Solution: remove the disk signature on the target thumb drive and all was well – ESXi would boot. Since I had the backup of the ESXi box’s configuration, I applied the backup and the configuration returned.

But… the iSCSI datastores were still not there. It was getting late again and I had to work Friday. Off to bed for a not-so-restful night.

After a lot of Googling I found an article on VirtualizationHowto.com by Brandon Lee titled VMware ESXi 6.5 Can’t Add Existing iSCSI LUN (from back in December 2016 for ESXi 6.5!) that was most helpful. It is great for troubleshooting. Anyway, the high level solution (details in the article) was to:

esxcfg-volume -l
esxcfg-volume -m UUID

Magic – the datastores reappeared. (I had to do it twice – once for each of the iSCSI targets. I think the next time using a “-M” to make it permanent over reboots. I’ll get around to that.) This might also fix the need to reboot the ESXi box when I have to reboot the NAS or have to reboot the switch when I upgrade the firmware.

Now, on backups:

Synology has a free application called Active Backup for Business. You have to register when you install it, but it is still free. Active Backup for Business lets you backup your VMs even if they are live. If you do not have vCenter (I don’t), you need to enable ssh and ESXi Shell for Active Backup to work. (An aside: After enabling ssh and ESXi Shell the settings did not stay set after reboot. I think that was a warning that the original USB thumb drive was starting to fail.) You also need to enable Changed Block Tracking (CBT) on the ESXi host to reduce the transferred data size and time for backup because CBT backs up only the blocks that are changed since the previous backup. Synology (and VMware) has a nice article on how to do this in the KB article How to enable CBT manually for a virtual machine. Unfortunately, I have not found how to automatically backup the ESXi configuration yet. This is a great solution for Synology users.

The other thing is that I am, one could say, religious on backing up configurations. The pfSense configuration is backed up pre and post changes and upgrades as is the UniFi configuration. I back them up to three locations: the DS216, RS1221 and on my “work” laptop. I also keep previous firmware available so I can rollback if needed (or available – the DSM upgrade can’t be rolled back). Backups are a good thing!

Posted in Uncategorized | Leave a comment

Final Upgrades Completed – Only Tweaks Left

As it finally started warming up I noticed that our electric bill was not going down as expected. We use electic heat (for hot water as well and we have a heat pump) so one would expect that as temperatures increased the power bill would go down. After some thought, I realized that I had two things in the rack that while helping keep the office warm during winter were not helping at all during the summer.

The lesser of the “problem” children was the HP DL360 Gen7. I used it only for testing – and that utility was greatly reduced when VMware ESXi 7.0 was no longer supported on its architecture – and it was only on for brief periods (it had not been on for over 45 days). While it was powered off, there was still power usage as it was not truely off but in standby mode.

The biggest problem was my Supermicro TrueNAS (FreeNAS) server. That server is a beast with old technology. The specs were:

  • Chassis: Supermicro SuperChassis 825TQ-R740LPB 2U 8 x 3.5″ Drive Bays
  • Power Supply: 2 x 740 Watt PWS-741P-1R Power Supply Platinum
  • Backplane: Supermicro BPN-SAS-825TQ 8-port 2U TQ (W/ AMI 9072)
  • Motherboard: Supermicro X9DR3-LN4F+
  • CPU: 2 x Intel Xeon E5-2630 V1 Hex (6) Core 2.3GHz
  • RAM: 32GB DDR3 ECC (8 x 4GB – DDR3 – REG)
  • Storage Controller: LSI 9210-8i 6 GB/S
  • Boot Pool: 2 x Kingston A400 120 GB SSD Mirrored (using motherboard SATA 6 GB/s)
  • Pool_1: 5 x WD Red 3 TB RAIDZ2 (CIFS and PROD VMware VMs)
  • Small_n_Slow Pool: 1 x Western Digital Blue WD3200AAKS 320GB and 2 x Seagate Barracuda 7200.10 300 GB (DEV VMware VMs)

I did not need dual Xeons running at up to 95W each. The dual 740W power supplies were not helping either. (Yes, I know that they don’t always draw 740W)

I really love TrueNAS. It has amazing flexibilty and stability. The first plan of attack was to see about swapping out components but even on the used market this would have been costly because, well, it is a server – you can’t easiy swap out the motherboard and put in a single processor with lower power requirements. And that doesn’t address the issue of the dual 740W power supplies. Even the RAM is relatively power hungry compared to modern components. So, that would not work.

I briefly thought about going to an iXsystems TrueNAS Mini but that was not inexpensive either and there is no rackmount model (yes, a little “vanity” on my part). The rackmount TrueNAS systems ain’t cheap either.

After additional thought, I started considering Synology (again). About 10 years ago, I purchased a Synology DS211j. A nice little unit that intoduced me to DSM. Over time, the ability to transcode was degraded by the march of technology. I then purchased a QNAP TS-219P II just to server as a media server. With newer releases of DSM, the perfomance of the 211j became painful. I then upgraded to a DS216+ II and retired the DS211j. Over time, the 1TB drives were upgraded to 2TB drives and then 3TB drives with the older drives being handed down to the older NASes.

Finally, the limitation of the two bays became evident as I increased the number of VMs I had. I had started using iSCSI to increase my storage space between the ESXi server(s) and the NASes. I was then on the quest to upgrade to something that was four-plus drive bays and was rack mountable. I looked at Synology but the four-bay unit was overpriced (in my opinion – yes, I know that rack mount adds about 25% or more for the price as the cooling requirements in a rack has implications and, well, they always seems to charge more for rack gear because they can…). After doing my research, particularly from information from Tom Lawrence of Lawrence Technology Solutions I decided on FreeNAS. After looking at price (including shipping) I ended up with the aforementioned Supermicro server. (Which came with rails. <rant>Why do used server vendors charge for rails? Average $100? What do they do with the ones they can’t sell? Argggg!!!</rant)>

So, I was back at what to replace the TrueNAS server with? Well, I’m back to Synology. A RS1221+ to be exact. It is a nice little box:

  • AMD Ryzen V1500B (64-bit, 4-core 2.2 GHz)
  • 4 GB DDR4 ECC SODIMM expandable to 32 GB (16 GB x 2)
  • 4x RJ-45 1GbE LAN Port
  • 1 x eSATA which I can use for the 4-bay RX418 expansion unit if needed
  • 1 x Gen3 x8 PCIe slot (x4 link)

The RX1221+ is not perfect. At this price level:

  • It should have 10GbE ports by now
  • It only has eSATA expansion for four additional drives – why no SAS or InfiniBand?
  • Only one PCIe slot – it has room for two
  • DSM’s approach to VLANs definately needs work. There is a command line hack to allow multiple VLANs to an interface but the GUI does not easily let you know which is which. Obviously , if you can do it on the command line it can be done in the GUI. This is Linux-based after all. I have a feature request in for that
  • NFS cannot be bound to a specific NIC (or subnet/VLAN). I had my TrueNAS NFS shares split off on a different interface to segregate it from the rest of the network traffic. I like the flexibility of NFS but I am now back to iSCSI. Some say that iSCSI is a little bit faster but it is nice to be able to go directly to the share without having to set up an iSCSI initiator on another device
  • No rails included (see previous rant)

I also added five new Seagate IronWolf 4TB drives. I’m not happy with the shenanigans Western Digital got up to with their Red line. Three of the old WD Red 3TB drives are moved from the old TrueNAS server to the RS1221+ as another pool (SHR2 for the 4TB pool, SRH for te 3TB pool) for backups, additional capacity if needed. The remaining two 3TB drives went to the RS216+ II. That leaves two spare 2TB WD Red drives. I’ll have to figure out what to do with them. Maybe I’ll sell them with the Supermicro server.

The second part of my upgrades was the start to redudancy. While we’ll likely be going back to the office (or maybe not) and classroom by the fall, work/learn-from-home is likely going to stay. And if you are at home you need to ensure that you have connectivity. I added a UniFi SW24 G2 switch as the new core switch leaving the old SW24 as a backup. I still need to figure out what to have as a redundacy for the pfSense firewall. I’d like something rack mounted (with the same number and type of NICs so that I can simply restore the configuration). These are items you can’t just drop down to BestBuy and pick up here.

Anyway, here is what the rack looks like now (all cleaned up):

Posted in Uncategorized | Leave a comment

OMG – Pelleys.com Was 20 in October

I just realized the I registered pelleys.com back on October 2, 2000….

Posted in Uncategorized | Leave a comment

New Camera for wx.pelleys.com

Back in August, August 23rd to be exact, the camera for wx.pelleys.com died in the afternoon. It was a nice warm day. The camera, a Panasonic TK-C750C, was about 10 years old. That’s a pretty good age given it is outside in an enclosure. The enclosure, actually the second one, has a heater and a fan for cooling, but in this environment (wind blown sea air) I’m not surprised failed. It looks like the sensor broke. The sea air actually croaded the chromed thumbscrews on the lens! The arrows point to the former silver thumbscrews.

binary comment

I started my search but I couldn’t decide on whether to get another analog camera or go with a higher definition IP-based camera. As noted in my previous post, my dad got ill in September and then passed away in October.

Finally, I got around to replacing the camera. The weather had to be decent (which we haven’t had for the past two week – rain, drizzle, fog and lots of wind) to replace it. I decided to cheap it out and went for another analog used camera. This time a Panasonic WV-CP484 with a 2.8-12mm lens. This lens has a slightly higher zoom than the old camera.

If I can get another 5 years out of this camera, I’ll be pleased.

Anyway wx.pelleys.com’s web cam is back up.

Posted in Uncategorized | Leave a comment

Home Lab All Done – For Now

Back in August I posted on my latest updates to the home lab. At that time, I had added a new HP DL360p Gen8 to replace the old G7 for ESXi, added a UniFi Flex Mini for the office and replaced some of the old CAT5e “thick” cable with the Monoprice Cat6A SlimRun patch cables. I was planning some additional upgrades/replacement when my father fell ill in September and then passed away in October. Since dad died my sister and I have been quite consumed with being executors of his estate.

Since then, I have been able to make a few upgrades and replacements:

  • I replaced the second UniFi UAP-AC-Lite upstairs with a Unifi UAP-FlexHD. That is a nice AP even though it looks like someone painted a Red Bull can white 🙂 That said, it is very unobtrusive and works really, really well.
  • The UAP-AC-Lite was moved to my shed. The placement of the APs in the house coupled with the number of walls (some concrete) and the metal garage door led to terrible WiFi performance.
  • I really disliked the “wall warts” for the UniFi US-8 switches and the PoE injectors took up space in the rack (they were mounted on a board at the top of the router). Since I now had six devices that could be powered via PoE, I went with the UniFi US-8-150W switch.
  • Since I was at it – and wanted to free up some ports on the UniFi US-24-G1 – I added a couple of UniFi Fiber Multi-Mode SFP 1Gbit/s modules with a 10Gtek LC to LC OM3 10Gb/Gigabit Multi-Mode Fiber Optic cable. Thinking back, I may have been better off (no real cost difference) with using a DAC cable instead. Maybe later, but I think that it “kinda kool” to have fibre in my rack even if it is pointless…
  • I added a Detroit Packing CAT6a patch panel. This has female-to-female keystone jacks since I didn’t want to punch down/crimp cables and I wanted to keep using the SlimRun patch cables.
  • I continued to replace any of the thick cables where possible with the SlimRun cables.
  • Cable labels – where needed I added labels especially from the ESXi boxes and the TrueNAS box.
  • Wire Management: I have some small zip ties used for the ESXi/TrueNAS (more below) cable bundles. However, for other bundling, I have used hook-and-loop (a/k/a Velcro) wraps.
  • Speaking of which:
    • FreeNAS is dead, long live TrueNAS. iXsystems has merged FreeNAS with TrueNAS creating TrueNAS Core. A nice few updates, etc. As of this post, I’m running TrueNAS-12.0-U3.
    • pfSense is now running 2.5.1-RELEASE; there was that awful mess (to be very kind) with 2.5.0 and WireGuard if 2.0…
  • I added the old door Information Systems sign (when our group changed names in my first job over 25 years ago!). Why? Why not?

So, what’s next? I’m not quite sure. I was thinking about replacing the the Supermicro TrueNAS server with a HP DL380 Gen8. I like the HP BMC as it uses a HTML5 remote console instead of Java like the Supermicro. But, given that work-from-home/school-from-home enviornment that is likely to continue for some time, I’m thinking about redundancy. This is especially the case for the pfSense box. I can get away for a period of time replacing the Switch 24 (not without pain) but pfSense is another matter. I thinking about buying anothe box just like the one I have. If I buy a UniFi Switch 24 G2 and another pfSense box I’ll have perfect components for my home lab – moving PROD away from DEV 🙂

Posted in Uncategorized | Leave a comment

Another Aide-mémoire – Renaming Files Based on Modification Time

I have a bunch of weather station time lapse daily web cam files (found here: Historical 24-hour WX Timelapse Videos) where the date of the web page index is the day after. This has bugged me for the past three years, but it was one of those things to “get around to”.

I finally got “around to it” (after getting tired of experimenting with pfSense haproxy for now). So that I will remember how I did it, my code is:

#!/bin/bash
# Rename the file based on the modified date
#
# go through the list of .mp4 files
for file in *.mp4 ; do
# Part 1 - for each file get the modification date and put it in a string. $file needs double quotes 
# due to spaces in the original
        part1="$(stat -c %Y "$file")"
# Part 2 - for each file add the destination location, format the new filename based on creation time (YYYY-MONTH-DD) and add the ".mp4" extension  
        part2="fixed/$(echo "$part1" | awk '{ print strftime("%Y-%B-%d", $1)".mp4" }')"
# Uncomment this to test first :-)
#       echo $file " is now" $part2
# This is the actual move of the original file (double quotes due to the spaces in the filename) to 
# the new directory. Use --preserve so the modification date doesn't change
        cp --preserve "$file" $part2
# All done
done

It may not be the prettiest, most efficient code, but it works.

Posted in Uncategorized | Leave a comment

Server/Network Upgrade – Almost at the End… For Now

Well, I’m almost at the end of the server/network upgrade for now. Since the last update, here’s where we are from the last update:

  1. I rebuilt the network configuration (about 85% of it).
    1. I had a weird problem with DHCP requests. The DHCP address a client requested (except for the two WiFi VLANs/subnets) would not get an address assigned to the subnet. It seems through the evolution of my network I had assigned a subnet to a physical interface and a VLAN on the pfSense firewall. Since I’m not a network engineer by any sense of the term (with my day job I feel like I’m 1 mm deep and 1 km wide) so there may be some reason why you would do this. Anyway, I removed the VLAN and made that subnet my default “core” network.
    2. I think that, for some reason (maybe the issue above), the two UniFi Switch 8s (non-PoE) were funky with DHCP requests, VLAN assignments and connections between the switches (e.g., Switch 8 in my son’s gaming room to the Switch 8 in the TV room to the Switch 24 in the rack). Google University and the forums didn’t give me much help outside of the the suggestion that the configurations for the Switch 8s might be corrupt. I reset both the Switch 8s to factory configuration and deleted them from the UniFi controller. Once I did that I re-adopted the two Switch 8s into the UniFi controller and reconfigured the VLANs on the ports everything works just fine. Plus, the Switch 8 in my TV room could power the Switch 8 in the gaming room. (The Switch 8’s can be powered by PoE and one port can provide PoE. That was a nice bonus.)
    3. I added a UniFi Switch Flex Mini for the desk in the office. I can put VLANs on that small switch for testing, etc.
    4. The move to the Monoprice Cat6A SlimRun patch cables is almost completed in the rack. I only need to buy another pack of 1 foot (or 2 foot) patch cables. I ordered some 6 inch patch cables and only one was long enough to use. Dunh! I have 10 foot cables for the servers: yellow for FreeNAS (eventually to be TrueNAS), red for the HP DL360 G7 and orange for the DL360p Gen8 (more about that below). I bundled the servers patch cables into umbilicals. Connections to non-network/non-server devices are purple SlimRun patch cords (some more still need to replace a few older runs). White will be used in the rack for in-rack networking (e.g., those 6 inch ones).
  2. I bought an HP DL360p Gen8 with 2 x Xeon E5-2650 2.0Ghz 8-Core CPUs, 128 GB of HP SmartMemory (8 x 16GB) PC3-12800R (DDR3-1600) Registered ECC Memory, 4 x HP Enterprise 300 GB 6G SAS 15K SFF Hot Plug Hard Drives, HP Embedded Smart Array P420i/1GB FBWC RAID Controller and 2 HP power supplies. I also have iLO 4 Enhanced which allows for HTML5 remote console. The DL360 G7 only supports, now anyway, remote console under Windows with the HP iLO Integrated Remote Console application. I messed around a little bit with trying to get the Remote Console application to work under Mint with wine, but couldn’t get it to work. I didn’t mess around with it for too long, but that is a sign that remote management is on its way out. (The Supermicro Java iKVM app only works with Firefox and IcedTea – for now…).
  3. I installed VMware ESXi 7.0 on the Gen8 and moved the VMs over. The VMs are stored on the FreeNAS server using NFS. I’d advise using NFS rather than iSCSI as you can easily share the storage between endpoints (ESXi or mounting them from a workstation). The G7 is running ESXi 6.7 – a fresh install from the ESXi 6.0 install. The G7 is now used for testing and experimentation. When I’m not doing anything I turn it off.
  4. I had one 300 GB SATA drive in the FreeNAS box but remembered I had two more 320 GB SATA drives in the old QNAP 2-bay NAS. I deleted the 300 GB pool (the first one that added to the FreeNAS box when I was first setting it up) and added the two 320 GB drives (all 8 bays are now filled) and created a 600 GB “small and slow” RAID-5 pool for the G7 to run test VMs on. Given that it is only 600 GB it might actually force me to delete old VMs. 🙂
  5. I added another UPS, an APC BackUPS 1500. The older BackUPS XS 1300 was a little taxed with everything on it. The server power supplies are split between the two UPSes and the network gear is on the 1500.
  6. Finally, for aesthetics I added 1U filler plates. After looking at the price of the metal filler plates on Amazon and eBay (what $20/each!?!?!) I made some out of some backing board I had left over from the homemade rack. I learned that even with a circular saw I couldn’t cut a good straight line so I borrowed my neighbor’s table saw (Thanks, Phil!) and re-cut them. I still need to paint them black (at some time – I hate painting as I always make a mess…). Here’s what it looks like now (The two chassis on the bottom might be used for some additional SAS storage in the future but I mounted them to get them out of the way. They don’t look too bad there.):
Front of Rack
Back of Rack
Posted in Uncategorized | 1 Comment

UniFi Adoption with Devices on Separate Subnet from UniFi Controller

This is, as always, is maybe more of an aide-mémoire for me, but may be helpful if someone else is searching for a solution…

Here is the scenario: My UniFi devices are on a separate subnet from my UniFi Controller. The problem, if you will, with this configuration is that when a UniFi device looks for the UniFi Controller is that is cannot find the Controller on a different subnet.

There are a number of ways that this can be resolved (other than putting the Controller on the same subnet) as documented in UniFi – Device Adoption Methods for Remote UniFi Controllers. The option that I took, or maybe it is two options, is:

  1. I configured my DNS server with an alias that allows unifi to resolve to the UniFi Controller. That way when a device restarts (such as after a reboot, power loss) it can find the controller when it boots and executes the set-inform http://unifi:8080/inform. The hostname unifi will resolve to my UniFi Controller.
  2. In my DHCP configuration (on pfSense), I added DHCP Option 43. You have to add 01:04 to the hex version of the IP address of your UniFi Controller. Browserling has a page to convert the IP address to hex: Convert IP Address to Hex Format.

One important thing to remember: If you statically set the IP addresses of your UniFi devices you will not get the DHCP Option 43 provided to the devices.

Posted in Uncategorized | Leave a comment