I just wanted to say Thank You for all the people that have contributed to this thread. I recently purchased a 620 and got the firmware updated and installed OPNsense on it by following the information in this thread. I could not have done it without everyone that took the time to write about their experiences.
Dell VEP/VMWare Edge/Velo Cloud SD-WAN/VeraCloud VEP1400/VEP1400-X firewall units
- Thread starter j_h_o
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
On a whim I picked up a Edge 640 with power supply for $75.
My plan is ro update to the firmware 2.6 bundle and attempt to install the ESXi 7.0 update 3 dell customized hypervisor, create two virtual machines and pass through the network interfaces and sata disk to run Opnsense in one VM and TrueNAS in the other.
Considering removal of the WiFi module (don't need it, less power) and installation of a larger Sata SSD.
Is this a reasonable plan? What roadblocks will I face?
Tips/advice welcome.
My plan is ro update to the firmware 2.6 bundle and attempt to install the ESXi 7.0 update 3 dell customized hypervisor, create two virtual machines and pass through the network interfaces and sata disk to run Opnsense in one VM and TrueNAS in the other.
Considering removal of the WiFi module (don't need it, less power) and installation of a larger Sata SSD.
Is this a reasonable plan? What roadblocks will I face?
Tips/advice welcome.
I still have the Dell ESXi 7.0 running on a 640. I think the BIOS on that device is a few points older than current. Can you still get a license key? I remember running into some passthrough limitations with the free ESXi. I can't remember if it was the whole interface or just SR-IOV. At this point, I think Proxmox is a better choice.
The SATA drive is on the bottom of the PCB and will require removing the fans and CPU heatsink. That means you will want to repaste. My units had full-height posts for 2240 and 2280. That means you'll need a 2240 drive, a single-sided 2280, a carrier board, or carefully drilling down the 2240 post that's in the way.
Removing the Wi-Fi module is easy, but I'd wait until after the BIOS has been updated. My devices have undergone extensive experimentation and multiple factory resets. These devices now fail POST and reboot without the Wi-Fi module present. I had to disable POST in NVRAM. I haven't seen anyone else mention this check/workaround.
I haven't personally tried the permutation, but if you only need one large drive, I'd remove the SATA completely. Remove the mini-PCIe Wi-Fi and replace with NVMe using either of the following adapters. This way you'll have easier access to the drive. Large NVMe is also easier to source.
Attachments
Thank you! I still have an ESXi 7 perpetual license, so no worries there. One follow up question: When you say you disabled POST in NVRAM, was this through a BIOS setting, or was another method used?
There's an NVRAM tool included with the bundled DiagOS utilities. There's also a list of addresses and values. The documentation is minimal.
Hello
Maybe the below is useful. Note- Not tested!
I too have several of these Edge units. All updated to 9-2x.
They are running various workloads at the moment. I will re-purpose them at sometime soon and was looking for information about how to install a NVME drive in place of the WiFi card.
I came across this Chinese website with some information of how to disable the POST check on these devices.
www.vvave.net
I attempted to create a direct link - but if that fails, please copy and paste.
From the translation.
Modify the hardware self-test policy
If you don't need a wireless network card to remove and install an additional hard drive, it should be noted that the default BIOS will verify the hardware information, if the hard disk or network card needs to be manually modified to modify the self-test policy:
nvramtool --write --reg=0x56 --val=0x0
nvramtool --write --reg=0x55 --val=0xf
If you want to skip the POST self-test entirely, you can set the bit to .0x540
POST Control=0xEA000F03
I have not attempted to use these commands yet! - Proceed at your own risk.
I hope this helps.
RedX1
Maybe the below is useful. Note- Not tested!
I too have several of these Edge units. All updated to 9-2x.
They are running various workloads at the moment. I will re-purpose them at sometime soon and was looking for information about how to install a NVME drive in place of the WiFi card.
I came across this Chinese website with some information of how to disable the POST check on these devices.
VMware Edge 620 SD-WAN 改造和使用 - VVavE
机缘巧合下，在某鱼上买到了二手的 Edge 620，这款机器实际上是 VMware 定制的 SD-WAN 设备，原设备带看门狗，只能安装特定的系统和软件。
I attempted to create a direct link - but if that fails, please copy and paste.
From the translation.
Modify the hardware self-test policy
If you don't need a wireless network card to remove and install an additional hard drive, it should be noted that the default BIOS will verify the hardware information, if the hard disk or network card needs to be manually modified to modify the self-test policy:
nvramtool --write --reg=0x56 --val=0x0
nvramtool --write --reg=0x55 --val=0xf
If you want to skip the POST self-test entirely, you can set the bit to .0x540
POST Control=0xEA000F03
I have not attempted to use these commands yet! - Proceed at your own risk.
I hope this helps.
RedX1
I only remember changing a single value. Maybe the above settings provide more granularity. My POST checks the memory and skips everything else. I thought I was the only one who ever encountered the POST issue when removing the Wi-Fi module. The original behavior was to boot 3 times from the primary BIOS and then fall back to the secondary BIOS (which at this point is much older).
That recent blog actually references this thread, so it's becoming circular. I just revisited NVRAM locations 0x54, 0x55, and 0x56. Here's what I found:
1) Don't ever enable [6 POST Extended Upper DRAM test] or [5 POST Extended Lower DRAM test]. You'll be waiting a very long time.
2) You can enable extended tests and verbose messages, but 0x54 is always reset to 0x01 after boot.
3) Address 0x55 appears to always retain its value.
The following values allow all tests to be reported without halting the boot (when the Wi-Fi module has been removed). I've never tested totally removing the SATA drive. However, I've used 3 alternate 512GB/1TB SATA drives without any warnings during boot.
Code:
nvramtool --write --reg=0x54 --val=0x01
nvramtool --write --reg=0x55 --val=0x09
nvramtool --write --reg=0x56 --val=0x00Here's what my complete boot sequence looks like. You can see that the POST technically fails because the Wi-Fi module is missing, but the process continues. I have no explanation for all the seemingly random characters. They're mostly numbers separated by commas, so it's not transmission noise.
Code:
BIOS Boot Selector for VEP1400-X
Version 3.50.0.9-21
POST Configuration
CPU Signature 506F1
CPU FamilyID=6, Model=5F, SteppingId=1, Processor=0
Microcode Revision 3E
Platform ID: 0x0
PMG_CST_CFG_CTL: 0x37
Misc EN: 0x840089
Gen PM ConA: 0xA0800200
Therm Status: 0x8000000
POST Control=0xEA000901, Status=0xE604CF10
BIOS initializations...
CPGC Memtest Channel 0 ...................... PASS
CPGC Memtest Channel 1 ...................... PASS
POST:
RTC Battery OK at last cold boot
RTC date 8/22/2025 7:06:34
POST SPD test ............................... PASS
POST Lower DRAM Memory test ............. START
POST ECC Test ............................... PASS
.... Perf cnt (curr,fixed): 0x5C012A3D0,0xFD033432C
POST Lower DRAM Memory test ................. PASS
POST Lower DRAM ECC check ................... PASS
37, 00068003, 4F, 3B, 00068002, 60, DXE_CORE_STARTED (03041000)
61, 9A, 02020000, 62, 78, 68, 69, 00068005, 6A, 70, 00068008, 71, 79, 03058001, 90,
DXE_BDS_STARTED (03041001), 92,
PciBusStart(02010000): 93, 94, 02011000, 93, 94, 02011000, 93, 94, 02011000, 94, 02011000, 94, 02011000, 94, 02011000, 95, 96, 91, 92,
PciBusStart(02010000): 97,
98, 98, 9D, 9D, 02020004, 9C, 9C, 02020003, 92, 92,
PciBusStart(02010000): A0, A0, A0, A0,
AhciBusStart (02080000), A2, A2, AHCI port 5 reset 1 pass
SATA ConfigureDevice Port 5: Device SATA CVB-8D1024 Pass
AMI Code Label: 0ACHI055
RC Version : 0.149.4.66
SPS Version : 0B:4.0.4.830
CPLD: 0.42
Current BOOT from Primary BIOS
DxE POST
POST Upper DRAM Memory test
Short memory cell test
POST Upper DRAM Memory test ................. PASS
HDD Device check ............................ PASS
Temperature test ............................ PASS
FAN controller test ......................... PASS
EEPROM test ................................. PASS
WIFI [168C:003C] not found, expect:3d: 4: 0 ... FAIL
POST PCI test ..................................... FAIL
POST NVRAM check ............................ PASS
POST overall test results ......................... FAIL
NVRAM: 10 CF 04 E6 01 09 00 EA 05 00 00 __ 00 0F 00 F7 FF
Version 2.19.1266. Copyright (C) 2024 American Megatrends, Inc.
BIOS Date: 09/19/2024 12:41:27 Ver: 0ACHI055
Press <DEL> or <F2> to enter setup.AD, Welcome to GRUB!
error: no suitable video mode found.
GNU GRUB version 2.06-13+pmx7
/----------------------------------------------------------------------------\
|*Proxmox VE GNU/Linux |
| Advanced options for Proxmox VE GNU/Linux |
| Memory test (memtest86+x64.efi) |
| Memory test (memtest86+x64.efi, serial console) |
| UEFI Firmware Settings |
| |
| |
| |
| |
| |
| |
| |
\----------------------------------------------------------------------------/
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, `e' to edit the commands
before booting or `c' for a command-line. ESC to return previous
menu.
The highlighted entry will be executed automatically in 5s. + The highlighted entry will be executed automatically in 0s.
Booting `Proxmox VE GNU/Linux'
Loading Linux 6.8.12-13-pve ...
Loading initial ramdisk ...
error: no suitable video mode found.
Booting in blind mode
AF,
DXE_EXIT_BOOT_SERVICES(03101019)
B B
Ugh! So I got my 640; set up serial link, forced a factory reset, and booted from the DiagOS recovery image on USB. Here is the problem: I cannot install DiagOS on either the sMMC or SSD, the watchdog timer kicks in and the system reboots. I tried hitting Ctrl-C when at the menu of the DiagOS installer program, but it will not drop me in the shell. How can I disable the watchdog timer and install DiagOS so I can update the firmware?
So, your device reboots while installing DiagOS? I've personally never encountered that problem working with 2 640s and 1 680. What's the current BIOS version?
Figured it out - now device is fully updated and ESXi is installed.
The problem was a bad USB thumb drive for the DiagOS installer image. Apparently it was so slow (retries? just a cheap device?) that the watchdog caught the install. With a different thumb drive the DiagOS install completes in a matter of seconds - long before the watchdog hits.
The problem was a bad USB thumb drive for the DiagOS installer image. Apparently it was so slow (retries? just a cheap device?) that the watchdog caught the install. With a different thumb drive the DiagOS install completes in a matter of seconds - long before the watchdog hits.
Last edited:
@rory What are you going to be running under ESXi? Whatever instructions I originally followed for Home Assistant produced a VM that ends up with a corrupt disk every time there's a power failure.
looking to run two vms:
1) opnsense with network adapters passed through
2) truenas with network adapter and NVMe passed through
BTW - there was a firmware update for the SSDs related to corruption after power loss.. Can't remember where I saw that.
1) opnsense with network adapters passed through
2) truenas with network adapter and NVMe passed through
BTW - there was a firmware update for the SSDs related to corruption after power loss.. Can't remember where I saw that.
Last edited:
That was probably on the Dell website. I swapped the original 240GB SATA for 512GB and then 1TB. Sometimes eBay deals take a really long time to surface.
All-in-all I am very happy with the 640. I have SR-IOV enabled on the SFP+ and am passing all the network interfaces through to the VMs under ESXi 7.0u3. Very impressed with the build quality and routing performance is fine for my 1G internet connection. For grins I pulled the power while both TruNAS and OPNSensne VMs were running - upon re-applying power ESXi rebooted and the VMs auto started fine.
Hi everyone,
I recently got a VeloCloud Edge 540 (looks very similar to the Dell VEP1400/1405 series) and I’m trying to repurpose it to run pfSense or OPNsense.
However, I’m having trouble with the BIOS access and I can’t find a working BIOS file that allows normal USB boot.
Here’s what I know so far:
* The unit boots into VeloCloud OS and shows SN:VC05400011xxx on the console.
* BIOS access seems restricted (ESC key shows “Enter username”), and I can’t get into setup.
* I’ve read that some users flashed the VEP1400_UFW2.5 or 3.48.0.9-19 BIOS to unlock full features and disable watchdog, but I can’t find a trusted download source.
* I’m not sure whether the Edge 540 is closer to the VEP1400 or VEP1405 hardware.
What I need help with:
1. Which BIOS version is safe and confirmed working for VeloCloud Edge 540?
2. How exactly do you flash the BIOS (via USB, SPI programmer, or from within the existing OS)?
3. Does flashing the Dell VEP BIOS disable the watchdog automatically, or is there an extra step?
Any pointers, confirmed BIOS dumps, or guides from your experience would be greatly appreciated.
If anyone has a working modded BIOS or SPI image that boots pfSense/OPNsense cleanly, please let me know.
Thank you in advance for your help!
I recently got a VeloCloud Edge 540 (looks very similar to the Dell VEP1400/1405 series) and I’m trying to repurpose it to run pfSense or OPNsense.
However, I’m having trouble with the BIOS access and I can’t find a working BIOS file that allows normal USB boot.
Here’s what I know so far:
* The unit boots into VeloCloud OS and shows SN:VC05400011xxx on the console.
* BIOS access seems restricted (ESC key shows “Enter username”), and I can’t get into setup.
* I’ve read that some users flashed the VEP1400_UFW2.5 or 3.48.0.9-19 BIOS to unlock full features and disable watchdog, but I can’t find a trusted download source.
* I’m not sure whether the Edge 540 is closer to the VEP1400 or VEP1405 hardware.
What I need help with:
1. Which BIOS version is safe and confirmed working for VeloCloud Edge 540?
2. How exactly do you flash the BIOS (via USB, SPI programmer, or from within the existing OS)?
3. Does flashing the Dell VEP BIOS disable the watchdog automatically, or is there an extra step?
Any pointers, confirmed BIOS dumps, or guides from your experience would be greatly appreciated.
If anyone has a working modded BIOS or SPI image that boots pfSense/OPNsense cleanly, please let me know.
Thank you in advance for your help!
Edit: does not apply to 5x0 since those aren't Denverton!
The watchdog is programmed into the PIC, not the BIOS. The BIOS (or, UEFI) can talk to the PIC, but generally this doesn't matter: the PIC in default mode doesn't start the watchdog and it only gets turned on if the OS switches it on (once), and then it stays on until switched off or reset to defaults.
The firmware packages are almost always deployed for Dell DiagOS. First things first: which hardware does it report to be in software? During power-on it should display "BIOS Boot Selector for VEPxxxx" on the serial console. Maybe copy-and-paste the entire bootup serial log here.
The watchdog is programmed into the PIC, not the BIOS. The BIOS (or, UEFI) can talk to the PIC, but generally this doesn't matter: the PIC in default mode doesn't start the watchdog and it only gets turned on if the OS switches it on (once), and then it stays on until switched off or reset to defaults.
The firmware packages are almost always deployed for Dell DiagOS. First things first: which hardware does it report to be in software? During power-on it should display "BIOS Boot Selector for VEPxxxx" on the serial console. Maybe copy-and-paste the entire bootup serial log here.
Last edited:
I hate to be the bearer of bad news, but I'm pretty sure the only people with success in this thread have a 620, 640, or 680. The support files for those models are still freely available on the Dell website.
Last edited:
Hello
VeloCloud Edge 5x0
The VeloCloud Edge 5x0 units use the Intel C2000 series CPU. Sometimes they can be found for very low cost. I have no experience with the 510 unit.
Nothing from the Dell EDGE VEP 600 series is applicable to this unit.
Some useful information is available here.
VeloCloud 520 (5×0) to Opensource (WIP) | MODLOG
For OpenWRT - the link on the webpage still is working today. This image will allow all the ports to work, but it is based on a very old version of OpenWRT.
More here.
PFsense on a Velocloud Edge 510 (watchdog)
What is this board??? Help!
The original Coreboot Bios image - Jul 29 2015 does not invoke the watchdog and allows installation of PFsense, OPNsense, Ubuntu etc. If you use this method only the SFP ports will work.
The 3 units I have are not affected by the AVR54 bug.
Here is the Dashboard from the OpenWRT image provided by Kristian at ModLog
The Bios Chip on these units is a Winbond W25Q64JVSIQ.
It is Not Soldered to the motherboard and is easily accessible, in a small receptacle with lids.
I hope this helps.
RedX1
VeloCloud Edge 5x0
The VeloCloud Edge 5x0 units use the Intel C2000 series CPU. Sometimes they can be found for very low cost. I have no experience with the 510 unit.
Nothing from the Dell EDGE VEP 600 series is applicable to this unit.
Some useful information is available here.
VeloCloud 520 (5×0) to Opensource (WIP) | MODLOG
For OpenWRT - the link on the webpage still is working today. This image will allow all the ports to work, but it is based on a very old version of OpenWRT.
More here.
PFsense on a Velocloud Edge 510 (watchdog)
What is this board??? Help!
The original Coreboot Bios image - Jul 29 2015 does not invoke the watchdog and allows installation of PFsense, OPNsense, Ubuntu etc. If you use this method only the SFP ports will work.
The 3 units I have are not affected by the AVR54 bug.
Here is the Dashboard from the OpenWRT image provided by Kristian at ModLog
The Bios Chip on these units is a Winbond W25Q64JVSIQ.
It is Not Soldered to the motherboard and is easily accessible, in a small receptacle with lids.
I hope this helps.
RedX1
Last edited:
Since these run coreboot you'll need the coreboot utils to configure the CBFS; but it's also running SageBIOS so you can run BSD (and thus OPNSense) on it just fine. You can't select a different boot device at startup so you'll have to re-write the storage offline (outside of the device).
As for the WDT; I have a 5x0 image and it's still sending the WDT over I2C so that would still work (you'd put it in rc.local). As for the ports; those need configuration before they work; either MDIO or some in-band L2 frames. Usually that's done with a dtb but as long as you can find the addresses you can do that from BSD just fine.
As for the WDT; I have a 5x0 image and it's still sending the WDT over I2C so that would still work (you'd put it in rc.local). As for the ports; those need configuration before they work; either MDIO or some in-band L2 frames. Usually that's done with a dtb but as long as you can find the addresses you can do that from BSD just fine.