Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell VxRail Network Planning Guide

PDF

Identify switch ports to be configured for LAG

Enabling load-balancing for the non-management VxRail networks requires peering the pair of ports on each VxRail node with a pair of ports on the ToR switches.

Figure 1. Plug into equivalent switch ports for LAG. Plug into equivalent switch ports for LAG.
Plugging into equivalent switch ports for link aggregation

If you are enabling LAG across a pair of switches, and you have matching open ports on both switches, the best practice is to plug the cables into equivalent port numbers on both switches. Create a table to map each VxRail node port to a corresponding switch port. Identify which ports on each VxRail to be enabled for LAG.

For example, if you want to deploy a VxRail cluster with four nodes, and reserve and use two ports on the NDC or OCP and two ports on a PCIe adapter card for the VxRail cluster, and use the first eight ports on a pair of ToR switches for connecting the cables, you could use the resulting table to identify the switch ports to be configured for LAG.

Figure 2. Sample port mapping. Sample port mapping
Sample port-mapping table

Assuming that you are using the second port on the NDC or OCP and PCIe adapter card for the non-management VxRail networks, you can identify the switch port pairs, as shown in the columns shaded green, to be configured for LAG. Create a table mapping the VxRail ports to the switch ports as part of the planning and design phase.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\