Dell VEP/VMWare Edge/Velo Cloud SD-WAN/VeraCloud VEP1400/VEP1400-X firewall units

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

stangri

New Member
Jul 12, 2024
21
0
1
I have 2 640s running 9-20 and 1 680 running 9-22. All ports work as expected regardless of OS. I've been trying to avoid getting sucked in, but I will attempt to update a 640 and post my boot messages.
Is there a way for me to downgrade to 9-20?
 

nmpu

Active Member
Sep 22, 2023
253
125
43
Bradenton, Florida, USA
Is there a way for me to downgrade to 9-20?
Yes, you could downgrade, but I don't think there's a magical BIOS version. Here's the prior release.

Here's the terminal output from reset to Proxmox prompt on my 640.

My devices work and I'm not going to try to break them to match yours. :oops:

I just pulled a 640 off my shelf. It already had the latest DiagOS, CPLD, and PIC. I only updated the BIOS.

My device had Wi-Fi which I removed and replaced with a 1TB NVMe. I had to disable part of the POST via NVRAM to keep DXE from complaining about the missing Wi-Fi module. I've also upgraded the SATA drive to 1TB. None of these changes should affect the network ports.

You'll notice there are 2 boot partitions on the eMMC. There are likely settings which affect the boot process. I suppose you could try deleting those partitions and see if they are recreated. I suspect they are protected.

There are also 2 little pushbuttons inside. Others have claimed magical results. There are 2 BIOS images. I think those buttons just select the image. If you boot the older BIOS, it might trigger a data reset.

It seems most people don't have these issues. I know I managed to break my devices worst that yours. There was a time when some of my ports did not work. I see 3 different BIOS versions in my DiagOS root folder. I kept fiddling. At some point, the DXE messages appeared and everything worked.
 
Last edited:

stangri

New Member
Jul 12, 2024
21
0
1
Here's the terminal output from reset to Proxmox prompt on my 640.
And I'm guessing the `lspci -nn | grep -i ethernet` in proxmox shows all ethernet devices properly?

What about when in BIOS, do you see all ethernet device/ports listed or just two 10GB and two 1GB?

I see 3 different BIOS versions in my /root folder. I kept fiddling. At some point, the DXE messages appeared and everything worked.
So your ethernet ports weren't working and you kept flashing different BIOSes and at some point they started working? What are the 3 versions you've fiddled with?
 

nmpu

Active Member
Sep 22, 2023
253
125
43
Bradenton, Florida, USA
And I'm guessing the `lspci -nn | grep -i ethernet` in proxmox shows all ethernet devices properly?

What about when in BIOS, do you see all ethernet device/ports listed or just two 10GB and two 1GB?

So your ethernet ports weren't working and you kept flashing different BIOSes and at some point they started working? What are the 3 versions you've fiddled with?
Code:
root@fw:~# lspci -nn | grep -i ethernet
02:00.0 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01)
02:00.1 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01)
02:00.2 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01)
02:00.3 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01)
05:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection X553 10 GbE SFP+ [8086:15c4] (rev 11)
05:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Connection X553 10 GbE SFP+ [8086:15c4] (rev 11)
07:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection X553 1GbE [8086:15e4] (rev 11)
07:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Connection X553 1GbE [8086:15e4] (rev 11)
Edge 640 Ports.png

I see the 2.4 and 2.5 BIOS update files in DiagOS. I might have tried others. I suspect it was ultimately the internal pushbuttons that made the difference. Like I said, I'm not pushing those again.
 
  • Like
Reactions: stangri

stangri

New Member
Jul 12, 2024
21
0
1
Thanks. The I350 don’t show up for me in BIOS either. Is there a documentation for location/functionality of the push-buttons inside?
 

nmpu

Active Member
Sep 22, 2023
253
125
43
Bradenton, Florida, USA
Thanks. The I350 don’t show up for me in BIOS either. Is there a documentation for location/functionality of the push-buttons inside?
The buttons are top layer between the Ethernet jacks and the power input. Remove 4 screws from the bottom corners and slide off the top. There are no tabs or anything attached to the cover. I would press and hold one and see what happens. You're not going to make anything worse. There is no formal documentation. Multiple theories in this thread.
 

stangri

New Member
Jul 12, 2024
21
0
1
The buttons are top layer between the Ethernet jacks and the power input.
Silly me, they are described within a first page of this thread with the suggestion to play with them to enable ethernet ports.

Thanks, while it took 5-6 attempts with one unit, with the other one, pressing S1 and S2 together for about 10-15 seconds and then booting into BIOS (which took forever) after everything is reset brought the missing I350 interfaces into BIOS and all non-Dell OSes.
 

stangri

New Member
Jul 12, 2024
21
0
1
Got proxmox with openwrt running on 640. The fan noise is driving me nuts. Are there (much) quieter fans? Should I just take apart existing ones and drop some oil onto bearings? Any specific BIOS setting to control thermal profile/fan RPMs?
 

nmpu

Active Member
Sep 22, 2023
253
125
43
Bradenton, Florida, USA
Got proxmox with openwrt running on 640. The fan noise is driving me nuts. Are there (much) quieter fans? Should I just take apart existing ones and drop some oil onto bearings? Any specific BIOS setting to control thermal profile/fan RPMs?
There's no easy (safe) way to adjust the fan speed. That's another project on my to-do list. The device does have a temperature sensor and the fan(s) are connected to a proper controller IC which can vary the speed. The programming is via I2C. I've posted the addresses and data sheets. It's also possible to control the RGB LED (normally white) as well as override the Ethernet jack LEDs.
 
Last edited:

nmpu

Active Member
Sep 22, 2023
253
125
43
Bradenton, Florida, USA
Thanks, while it took 5-6 attempts with one unit, with the other one, pressing S1 and S2 together for about 10-15 seconds and then booting into BIOS (which took forever) after everything is reset brought the missing I350 interfaces into BIOS and all non-Dell OSes.
There can be a long delay during boot when you change BIOS. I assume the BIOS has to rebuild internal data when deemed incompatible. That's exactly what we wanted. Do you now see the DXE messages and stray numbers during boot? I assume your 'Factory Reset' message has gone away?
 

stangri

New Member
Jul 12, 2024
21
0
1
Do you now see the DXE messages and stray numbers during boot?
I don't know which exact DXE messages you're referring to, there were (and I think still are) some DXE messages even after the NICs were fixed.
I assume your 'Factory Reset' message has gone away?
Yes, I think you're correct a boot into DiagOS fixed that.

I've been away from the world of PCs far too long. Are the Dell's fans somewhat of a standard size? I've tried to look at and even take a photo of the fans labels while I was cleaning and lubricating them, but I can't read that fine of a print at my advanced age. Are there reputable/better fans to replace the worn out ones with? Cleaning/lubing helped, but as there are two fans which spin faster, they are still noisier than a single fan of 620, so I wonder if I can (relatively inexpensively) replace the fans to reduce noise.
 

stangri

New Member
Jul 12, 2024
21
0
1
The fan controller is TC654 at address 0x1B on i2c-0. The temperature sensor is LM75A at address 0x4A on i2c-0.
I can also read from Debian (Proxmox), but I can't set/control anything. :( Is there anything that can be done to reduce the speed/noise from fans of 640? I love the extra hardware, but it's definitely more noticeable than 620.
 

nmpu

Active Member
Sep 22, 2023
253
125
43
Bradenton, Florida, USA
I can also read from Debian (Proxmox), but I can't set/control anything. :( Is there anything that can be done to reduce the speed/noise from fans of 640? I love the extra hardware, but it's definitely more noticeable than 620.
Do you get an actual error? As a test, can you at least change the LED color?
 

cwellman

New Member
Jul 26, 2025
4
2
3
Michigan
www.quartz.systems
I have a Edge 3400/VEP4600 with Proxmox installed on it, has anyone been able to control the fans on the VEP4600s? If so, what are the commands, I'm unsure if the i2c addresses are the same on the VEP4600s as they are on the VEP1400s. Thanks.
 

nmpu

Active Member
Sep 22, 2023
253
125
43
Bradenton, Florida, USA
I have a Edge 3400/VEP4600 with Proxmox installed on it, has anyone been able to control the fans on the VEP4600s? If so, what are the commands, I'm unsure if the i2c addresses are the same on the VEP4600s as they are on the VEP1400s. Thanks.
Is there an equivalent DiagOS like on the 6x0 models? I found the i2c addresses in /etc/dn/diag.
 
  • Like
Reactions: blunden

nmpu

Active Member
Sep 22, 2023
253
125
43
Bradenton, Florida, USA
Yes, found it, does this look correct, thanks.

<device>
<device-id>2</device-id>
<device-name>emc2305 fan controller</device-name>
<bus>/dev/ipmi-1</bus>
<address>0x9a</address>
<reg>0x20</reg>
<count>1</count>
</device>
I found the following in default_fan_list.xml:
Code:
        <descr>
            <id>0</id>
            <name>fan1</name>
            <device>TC654</device>
            <driver>/dev/i2c-1</driver>
            <addr>0x1B</addr>
            <device_index>0</device_index>
            <container>fan 1</container>
            <speedres>50</speedres>
            <speedpol>2</speedpol>
        </descr>
        <descr>
            <id>1</id>
            <name>fan2</name>
            <device>TC654</device>
            <driver>/dev/i2c-1</driver>
            <addr>0x1B</addr>
            <device_index>1</device_index>
            <container>fan 2</container>
            <speedres>50</speedres>
            <speedpol>2</speedpol>
        </descr>
Different addresses and probably different controller IC. You need to identify your controller IC either from the support files or inspection of the PCB.
 

sic0048

Active Member
Dec 24, 2018
235
169
43
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.