I found a nifty trick with ESXi. If you want to use an NVMe Drive as your main datastore, you can install to it as normal, but the Dell R720 will not boot to it. (at least in my case, using a Kingston A2000 NVMe SSD on an Orico PCIe Adapter card)
The UEFI simply doesnt see it as a drive.
But what you can do is create a 4GB HDD partition on the vFlash SD card, and install ESXi to that.
While smaller than the minimum disk size of 8GB, the installer will run correctly.
You can then reboot the system, and boot off the 4GB vFlash partition.
Somehow ESXi seems to realise what’s going on and switches over to the NVMe drive!
When it boots up, you will find that your datastore resides on the NVMe drive.
I have a 3CX PBX at home I use for a few things, and I also have a Cisco SPA504g that I use with HamShack Hotline.
I have a second extension setup on the SPA504g for my 3CX system, but I figured it might be a good idea to get the 3CX system to register to HH as a trunk as well! That way I can also make and receive HH calls from my phone and the amazing 3CX application.
I applied for a new trunk line via the HH Support Center, and received it the following morning.
They provided me with three pieces of information; User: 30027 – This is the extension number assigned to my trunk (Try calling me!) Password: aprettygoodpasswordwashere IAX Host: hhap.wizworks.net
The IAX Host is the SIP server, and should accept a SIP Register on port 5060 with the authentication info above.
In the 3CX Management Console, I went to Trunks and clicked Add SIP Trunk.
I selected Generic as the country, and Generic VoIP Provider as the provider. The Main Trunk Number should be the extension provided above.
I filled out the info where it needs to go, and set the destination for calls to the main trunk number to go straight to my extension, so Ill get them on my mobile or PC.
This SHOULD be all that’s required! But alas, I am not that lucky today.
The trunk is failing to register. If we switch over to the 3CX Event Log, we can see the failed registration attempt.
Its worth noting here, that while the log shows the user as [email protected], this is merely a graphical confusion, as 10001 is the internal number assigned to the trunk by 3CX, and not the actual user that it attempts to register with. 3CX Uses the SIP User ID we entered above to register, but I am still receiving a 403 Forbidden from the hhap.wizworks.net:5060 (which currently resolves to 126.96.36.199) server.
I thought this may be happening due to the second connection I already have from this address, the Cisco SPA504g handset, so I connected to my Unifi Controller and shutdown the PoE to the port the phone is connected to.
Once the phone went offline I tried registering again through 3CX, and this time it gives an error that the service is not available…
I have reached out to the HHOPS team to see if there is any issues currently with the hhap.wizworks.net server, and will update my post here when I hear back, or if I otherwise resolve the issue.
I heard back from HHOPS!
They gave a few suggestions, and I was able to get things up and running!
Rather than Generic SIP Provider I have used Asterisk as the type, and rather than 5060 for the port, I have used 4569. It is now successfully registered and appears to be working!
To finalise, I have also setup an Outbound Rule for Hamshack Hotline, where calls to numbers with a length of 5 digits get routed out the new Hamshack Hotline trunk.
To my surprise, I cannot find any sort of blanking panel template for laser cutting on the internet. Considering how common laser cutters are becoming, I expected to find at least some… oh well, I have made my own and will share it with you here!
I threw this together in Illustrator and share with you three files, an AI, an SVG and a DXF for cutting or whatever you want.
I have had for the last few years, a growing pile of electronics that I called my homelab. It looked a bit sad.
I decided recently that it really deserved some love, and it’s really very rewarding to put in a bit of effort for something that looks good.
So I started looking into ideas on how to clean it up.
Initially I was planning on getting either a 9u or 12u rack/cabinet, and just leaving it in the same place. But as much as I love my servers and gadgets, I don’t think a black metal box in the living room/ kitchen looks great to guests. So I figured I should try something that looks better.
An IKEA lack was off the table, as it’s much too large for something up against the wall in my opinion, so I browsed the website for a while until I came across the TRYSIL. It’s a chest of r draws, that extends a mere 40cm from front to back. Perfect for up against the wall! And at only $129, it was just $4.05 more expensive than a 9u rack.
So I ordered one and picked it up Friday night. Assembly was pretty straightforward, just follow the pictures as you would expect. But what I didn’t do was install the bottom two draws, I left that section completely open.
I purchased two metal strips for.the hardware for about $0.80 each, and laid the two draw fronts together about the correct spacing apart, and bolted them together using the metal strips.
I then measured out and attached two butt hinfes ($4.95 for the pair) to the new door and cabinet.
I had this wall-mount server rack thing left over from a previous intention to wall mount my servers in the garage, and flipping it on its side gave me a perfect 3u mounting space.
I used M5 bolts and some washers to secure it in place, and it’s not going ANYWHERE.
This fits really well, leaving a bit of space on either side for cable management and other things.
I then test fit a PowerPoint art he back and started on my way to cutting out a hole in the base to mount a pair of 200mm fans for airflow.
In Australia you can’t do mains voltage work without a license, so I called over a sparky friend do wire things up for me.
I went out to my local Jaycar to pickup a few things I would need, and while I was there I found a 4 Port USB outlet for only $15! I grabbed this and a mounting box for it as well, this will be useful for odd things like an esp8266 to monitor temperature and drive LEDs, and the Mi-Light wifi bridge.
Now that sparky mate has installed those for me I went back to working on cutting out my hole for the fans. I probably could have cut it out before assembly but I was in the mood to get things done in one day so I didn’t want to trek out to Robots and Dinosaurs with some wood to cut out using their tools!
I cut a hole on the upper left side for a cable feed hole for ethernet connectivity, but I’m thinking I’ll replace this with a 6 way Keystone plate to keep the cabinet modular. I want to move the nbn cable NTD into the roof, so that rather than an RG-6 cable to deal with I just have CAT6…
I also got an IEC socket installed on the back to be fed from the external UPS which is too large to fit inside, this also means it’s relatively simple to unplug and move should I have to do that.
Once I had the holes cut out to my satisfaction, keeping in mind that they won’t really be seen so I wasn’t too fussed, I used cable ties to hold the two 200mm fans together, and screwed them into the underside of the cabinet over the hole.
Once I had mounted and wired up my fans, it was time to start moving my network hardware over.
I started with the switch as it will serve as the shelf for the other hardware. (don’t worry it’s properly bolted in)
I then installed the power distribution bar, NTD and pfsense router. I blacked out the pfsense because it’s a surprise for another post soon.
I affixed the Mi-Light bridge and zigbee2mqtt devices using command Velcro, and screwed in a fan controller harvested from the same PC the fans came from.
I began to test fit the various power supplies inside, there’s a few because I’m using micro PC’s as servers… I’m considering consolidating the Synology units into a single 150w PSU though.
I test fit and began cabling everything in, I have ordered a brushed 1u panel to clean up the wiring a bit more but it will be a few weeks from china.
Once everything was in, I did a final test to make sure I was happy with the airflow and the path the air seems to be taking through the cabinet, which will improve after I install the brushed plate and a blank panel.
With ally tests done and happy, I hooked up the ups and turned on all the servers one after another. I monitored them as they came back online to ensure all VMs and services started correctly, and so far only Wireguard refuses to start! 🙁
Good enough for me!
And with that the move was virtually complete!
I have since added some lights, and a DHT22 temp/humidity sensor inside to keep track of how it’s going, but temps so far seem very acceptable.
The 120mm fans bolted directly to the cabinet are audible so I would like to replace them with noctuas, mounted via rubber or foam dampeners.
Overall I’m super happy with how it turned out, everything fit perfectly, it was fun to work on and build, it looks so much better than an ominous pile of electronics next to the kitchen and dust will hopefully be a bit less an issue now!
Best of all, it looks nothing like a server cabinet!
My Home Assistant / Hass.io install was an old ResinOS image from the hass.io website running on an Intel NUC.
Occasionally I would have to reboot the machine, as it would loose network connectivity for an unknown reason (The machine was still connected, and the host OS, but Home Assistant could not connect out to the internet? as in, the logs were full of time outs and refused connections due to ‘max retries exceeded’
I wanted to migrate this over to a Ubuntu Docker install so that I had better control over the hardware and could do other tasks on the machine, and to hopefully repair the issue with connectivity.
I took a snapshot of hass.io through the web UI, copied it off as well as manually backed up the files, and then installed Ubuntu 18.04.3 onto the NUC.
I installed Hass.io following the manual install directions on the website, and then the samba addon. Copied the file back into the correct folder and rebooted. Once it was back up, I selected the snapshot and hit restore.
It took about half an hour to complete for some reason, but once it had, it was pretty much exactly how it was before I started.
There was a few things that required attention, for example Node-Red was not connecting. I didn’t do anything to it but restarting and it connected once more. There was also problems with MariaDB that I couldn’t understand, it could not connect, but was listening and running fine? I ended up just removing this addon and reinstalling it, as it was pretty simple.
Once it was all up and running again, It seemed to be working fine. I setup Portainer manually and connected it to the local docker instance, and added my other docker endpoints to it.
All was good.
Until the next day. My alarm didnt go off in the morning, which was the first red flag, I tried opening Home Assistant to adjust my Air Conditioner and it would not load, I checked Portainer and the container was still running, so it should be working? Checking the logs it looks like its running but cannot connect to the internet again. This is similar but not exactly the same messages as previously. I restarted the Home Assistant container and the logs indicated it was having connectivity problems out to the internet, but this should not stop the Local UI from working on https://IP:8123 … yet it was? I had to leave for work at this point so I figured no biggie, ill fix it on lunch over VPN.
(update: the alarm didn’t go off because the MP3 it plays is hosted on the internet, I need to switch it over to a local MP3 to remove this internet dependency)
But heres where the plot thickens.
Just yesterday I was toying with settings on my OpenVPN Server with my buddy Tom while we were trying to figure out why DNS doesnt work for local clients when connected to VPN, and something we touched must have been wrong as now my VPN is playing up and apparently he is having internet troubles too.
The next day:
So it turns out I didn’t break anything, Telstra had messed up my account for some reason and after an hour talking to them they were able to revert their changes and fix it. Now everything’s back to normal!
Almost exactly (give or take a few days) one year ago, I was browsing eBay looking at Nortel 5520 switches, I was upset that in America you could get them for $75US a pop, whereas over here they were almost $500AU each!
Fast forward to a few weeks ago, I learned of two Nortel 5520-48T-POE that were destined to go to an IT recycling company.
I was able to negotiate my hands on these two switches for $25AU each!
I got them home yesterday when I fired them up with my beautiful homemade serial cable (the one I got from Jaycar was crossover whereas the Nortel needs straight through)
I was greeted with an older version 5.0 software version!
This was no good, all versions of the software before 6.3.3 had terrible web interface.
I know many people say you should stick with the CLI, but when im in a hurry to make a change, check the status of a port, or shutdown / turn on ports, I want a simple and fast method of doing this.
So began the journey of upgrading the switch.
It started with an hour or two of research, trying to find firmware files, and documentation on the upgrade process and path.
You cannot skip major versions apparently, So I had to go from 5.0>5.1 and then to 6.3.
I was getting worried that all of the ftp servers I was finding referenced were dead links, until I stumbled upon a reddit users dropbox, which had everything I needed, PDF docs, firmware files for versions 5-6, I was set!
I found a page detailing the update procedure, which was a pretty simple command.
I reset the switch to factory settings, then gave it an IP address,
Then it was just a case of flashing the diag image, and then the main image.
A single command was all that was needed to flash each one:
5520-48T# download address 172.16.0.123 diag 55xx_diag.bin
5520-48T# download address 172.16.0.123 image 55xx_188.8.131.52s.img
These commands aren’t exact, but you get the idea.
After flashing each one the switch rebooted itself and did a pretty light show while flashing / booting.
Once the switch had rebooted, I checked the web interface by navigating to the switch IP address in Google Chrome, and was met with a warning that my browser may not support the page!
Dismissing the warning, the UI loaded, and it was far superior to the old one.
I suddenly have everything I need!
I will be installing this switch in my homelab once I can mod it to be silent, ill replace the fans with Noctua 40mm fans and see what else I can do for it.
So i’ve wanted to try this one for a while, can I install a desktop GPU into a server, and pass it through to a VM for gaming on?
Well my server has 128GB RAM, 4 SSDs RAIDed together, and 16 logical processors, so like, why not add a GPU and play some games on it!?
I picked up a GT740 second hand on a buy sell facebook group, and i’ve spun up a VM running Windows 10 x64 to install steam on.
I test fit the GPU into my Dell R210, and it doesnt really fit with the fan on, so removing the fan so its just a heatsink lets it fit, but im not sure if the airflow inside will be enough to cool it down? hopefully.
Its not going in the R210 anyway, its going in the R610.
Ill power it down shortly and test fit it.
OK, I had to cut the end off one of the PCIE slots as the R610 only had x8 slots, but that wasn’t too hard, just some very careful dremel work then a small file to clean it up.
I also had to cut off the little lock part of the GPU, the part at the end of the connector, as the R610 raiser card has a large component there (intrusion detection switch maybe?)
With those two parts removed it fits in well.
The system is taking a *very* long time to boot… but it is booting.
the video is coming from the onboard graphics though.
WE HAVE ESXi!!!!
Okay it booted and detected the GPU correctly, but looks like getting NVidia pci-e passthrough is a pain in the ass…. Might look into an AMD card at some point instead. Until then Ill mark this as a maybe!
Maybe ill migrate all the VMs from the R210 over to the R610 and then setup the R210 with a desktop OS ? hmm