Dell Technologies VEP4600 BIOS/Firmware Upgrade
Thu, 25 Aug 2022 17:11:09 -0000|
Read Time: 0 minutes
This document discusses how to use Dell Unified Firmware upgrade (UFW) utility to upgrade VEP4600 BIOS and other firmware.
1. Download UFW (Unified Firmware Upgrader) from Dell support portal and search VEP4600, as shown in the following image:
2. Select Dell Networking VEP4600 16-Core or any other VEP4600 models from the dropdown list (UFW works the same on all VEP4600 models).
3. Click the Drivers & Downloads tab.
4. Scroll down and select the following UFW file.
5. Expand Dell EMC Unified Firmware Updater V3.5 for VEP 4600 Switch as shown in the following image:
6. Select View full driver details and open the hyperlink
7. Click Download for both file formats to download the release notes and UFW zip file
8. Download the rn_vep4600.pdf to open the UFW release notes.
9. Open and download the VEP4600_ufw_3.5_External.zip file.
10. Save and unzip the file to a new folder, right click the filename to pop up the file process menu, select Extract All… from the drop down list.
13. Right click the VEP4600_ufw_3.5.zip file name and repeat the extraction process to generate a new subfolder.
14. These are the actual VEP4600 UFW file and md5 hash signature of the file. There are three options to run UFW to upgrade BIOS firmware in VEP4600:
- Run UFW through a bootable USB with diagOS
- Run UFW natively in Linux Operating Systems (Ubuntu, Red Hat, CentOS, and Dell diagOS based on Debian)
- Run UFW remotely through BMC/IPMI network
See the release notes (filename rn_vep4600.pdf, page 15) for more details about running UFW on VEP4600 system.
Related Blog Posts
Dell Enterprise SONiC Flexible and Robust VLAN QinQ, VXLAN, and VLAN Translation Solutions
Wed, 24 May 2023 17:24:24 -0000|
Read Time: 0 minutes
As a corporate business grows through mergers, acquisitions, and expansions, it must add or extend new business branches in many different locations. The network infrastructure must evolve to accommodate these new locations. Compute and network virtualization have also brought strong demand and requirements to transport local VLAN over WAN (Wide Area Network), Telco (Telecommunication), and many other network infrastructures.
Figure 1. Transport VLAN network through WAN network
In Figure 1, Laptop 1 is connected to the corporate network in San Francisco. Soon after, Laptop 2 was added to the same corporate network in New York. The users of these two laptops are in the same corporate business unit (BU), such as engineering, finance, or HR. Corporate IT wants to apply the same set of policies for network access, security, and service to these laptops. These policies are implemented through VLAN IDs, subnets, and other network provision parameters. Therefore, IT must transport the VLAN ID over WAN and its network infrastructures. Often, on corporate networks, endpoints must be on the same VLAN. These endpoints can be laptops, VMs, applications, and Virtual Network Function (VNF) entities, to name a few.
To help customers meet these network transport requirements, Dell Enterprise SONiC has built the new IEEE 802.1ad VLAN QinQ feature. This feature adds another VLAN tag in the original dot1q frame, creating a double-tagged VLAN frame.
The figures below demonstrate how the outer tag is used to identify the Telco provider’s traffic, while the inner tag is still the local dot1q VLAN ID. This process allows endpoints to use the same VLAN ID while traveling through Telco network infrastructures.
Figure 2. VLAN QinQ frame
Figure 3. Transport local dot1q VLAN over VLAN QinQ enables switches
Dell Enterprise SONiC VXLAN (Virtual Extensible LAN) solution is designed to transport VLANs in Layer 4, the User Datagram Protocol (UDP) transport layer, which is defined in the Open Systems Interconnection (OSI) model. Packets that VXLAN encapsulates are not aware of the underlay networking protocols.
The figures below demonstrate how the VXLAN IP/UDP header is created in a VXLAN tunnel endpoint (VTEP) ingress tunnel server and decapsulated in the egress VTEP server.
Figure 4. VXLAN header to encapsulate dot1q VLAN frame
Figure 5. Transport dot1q VLAN frame over VXLAN enabled network infrastructure
Network infrastructures in Telco, Communication Service Provider (CSP), data center, and cloud providers often consist of different types of VLAN transportation technologies like QinQ, VXLAN, and dot1q. To transport VLAN frames over a mix of VLAN protocol networks, Dell Enterprise SONiC introduces the VLAN translation feature with the following options:
- Dynamically modify the tag in a single tag VLAN frame
- Dynamically modify one tag and remove the other in a double tag VLAN frame
Figure 6. VLAN translation to modify VLAN tags
Figure 7. Illustration of Dell SONiC VLAN translation, QinQ, and VXLAN sample scenarios
Network service providers constantly face technical challenges and stringent requirements. For example, one common challenge is determining how to scale bandwidth up and out to address fast and spontaneous traffic growth. Other challenge include protecting and securing the networks through user and tenant isolations, or improving network efficiency.
Open source-based SONiC network software provides rapid feature development and a broad selection of network orchestration tools through a vibrant ecosystem and community. On top of that, Dell Enterprise SONiC has added special features and verifications, such as world class technical support for Dell networking hardware. This support can improve network security and flexibility, as well as increase network provisioning and monitoring capabilities.
Contact a Dell SONiC sales representative for additional information about Dell Enterprise SONiC solutions and technologies.
Contact Dell SONiC Sales representatives
To learn more about Dell Enterprise SONiC features, see the Enterprise SONiC Spec Sheet.
To learn more about Enterprise SONiC Distribution by Dell Technologies, see Enterprise SONiC Networking Solutions, Enterprise SONiC Distribution By Dell Technologies, and Dell SONiC Solution Overview.
For more information about specific steps and commands, see the Dell SONiC User’s Guide available on the Dell Digital Library.
uCPE Hypervisor Network Functions Virtualization Sizing Guideline
Tue, 06 Sep 2022 17:56:43 -0000|
Read Time: 0 minutes
This document describes how to make proper NFV sizing estimate and choose a right VEP model.
VEP4600 powered by Intel Xeon D CPU, hyperthreading function can be enabled or disabled in BIOS settings. The following screenshot shows the BIOS hyperthreading enable configuration.
If hyperthreading is enabled in VEP4600 BIOS settings, ESXi web UI displays that the logical processor count is 16, which is the double of physical CPU core count.
If hyperthreading is disabled, ESXi displays that the logical core count is the same as CPU core count.
Hypervisor undersubscription and oversubscription
Size of VM/NFV
Here is a sample profile of VMware SD-WAN Edge running as a VM in ESXi.
It takes two CPU cores from the total logical core/processor count in ESXi. If the total core count is larger than the ESXi core count, for example, in our previous VEP4600 eight core ESXi model, with hyperthreading enabled, the total core count is 16. If total VM/NFV core count is bigger than 16, then the ESXi hypervisor is running in oversubscription mode, meaning the hypervisor has to multiplexer among these NFVs, suspend one of them from time to time. If the total core count is less than 16, ESXi is running in undersubscription mode, no multiplexer is required, all NFVs can run simultaneously in ESXi hypervisor.
Use ESXi monitor feature to display graphical view of CPU/core performance.
VEP1405 Atom/Denverton CPU
In VEP1405 platform, Intel Deverton CPU does not support hyperthreading, the logical core count is always the same as physical CPU core count.
In VEP4600 platform, make sure to enable hyperthreading in BIOS to double the core count. Check every NFV/VM profile running in ESXi to make sure the total core count is not larger than the ESXi core count, so that it can run ESXi in undersubscription mode. It is still possible to run ESXi in over subscription mode if some of the VMs are not required to constantly hug CPU resource, for example if a VM is a DNS server, then most likely it is not constantly processing DNS client queries.