1 Rookie
•
3 Posts
0
146
August 15th, 2025 17:21
BMC on Virtual Edge Platform (VEP) 4600
I'm wondering if anyone has used this (either console or network) to do firmware updates on the VEP4600. I have a few dozen of these things that I need to maintain and I have no physical access to the systems (I need to lean on raised floor teams at remote data centers) so if I could leverage the BMC that's be great. The only problem is that the documentation is lacking. It doesn't seem straightforward at all. I inherited this responsibility and the person who originally deployed the first of these didn't bother to connect either of the BMC ports nor did the software vendor (for the platform that runs on these things) recommend using it. If anyone could point me to documentation that's effective (or even a link to a YouTube video or blog that explains it) I'd appreciate it.
DELL-Joey C
Moderator
•
4.2K Posts
•
21K Points
0
August 18th, 2025 01:51
Hi,
For Virtual Edge Platform (VEP), the documentations and the support are limited. The only way of using BMC to update firmware, you will need to setup BMC first. I'm unsure if the BMC has been fully configured, here's the reference: https://www.dell.com/support/manuals/en-my/virtual-edge-platform-4600-16c/vep4600_os_install_pub/configure-bmc-management-address-on-bmc-console?guid=guid-7b0bc17b-8155-4eaa-8e10-3165aa210531&lang=en-us
From there, you will need to use a Linux based server which is on the same network as the VEP BMC to update the firmware, here: https://www.dell.com/support/manuals/en-my/virtual-edge-platform-4600-16c/vep4600_os_install_pub/run-the-unified-firmware-updater-tool-from-a-linux-server?guid=guid-556d049c-9a4f-4784-99f2-8678a8eebed9&lang=en-us
SteveRDavid
1 Rookie
•
3 Posts
0
August 18th, 2025 13:29
@DELL-Joey C
Thanks! I think I already know the answer to this next question but I want to confirm. There's no way to update the system/bios firmware through the BMC GUI, right? Any mention of "firmware" within the BMC Web GUI is related to the firmware for the BMC itself. Is that correct? Also, you say "you will need to use a Linux based server which is on the same network as the VEP BMC to update the firmware" I assume that you're referring to non-BMC firmware (as in firmware for the mb/bios). Is that correct? Lastly, you say "same network". I know that the BMC takes a default gw config and I can access the BMC Web GUI from an offnet device. BMC clearly can communicate offnet. Why does the Linux server need to be on the same network if BMC can talk offnet?
DELL-Chris H
7 Practitioner
•
9.7K Posts
•
48K Points
0
August 18th, 2025 13:54
Your understanding is largely correct, but let me see if I can help clarify the things you asked about.
You're correct, the BMC Web GUI on the VEP4600 does not support updating system firmware such as BIOS, CPLD, or platform firmware.
Any mention of "firmware" within the BMC GUI refers exclusively to the BMC firmware itself. You cannot update BIOS or system firmware through the BMC GUI — only the BMC firmware itself.
As far as the Linux serve Dell documentation or community responses mention, they are referring to non-BMC firmware updates — specifically:
BIOS
CPLD
System firmware packages
These updates are typically performed using tools like:
Dell Diagnostic OS (DIAG OS)
Dell Firmware Update Packages (DUPs)
Redfish API or IPMI tools (e.g., ipmitool, ipmiutil)
So the Linux server is used for updating system-level firmware, not BMC firmware.
Lastly, based on your question on the same network element, the phrase “same network” is often used loosely. Technically if the BMC has a default gateway configured, it can communicate off-subnet.
Therefore, a Linux server does not need to be on the same Layer 2 subnet, as long as routing is properly configured and the BMC can reach the server.
However, Dell documentation recommends “same network” to:
Avoid routing issues
Simplify troubleshooting
Ensure lower latency and direct access during firmware operations
Let me know if this helps answer your questions.