Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

The use of VMware vSAN in the Network

2025-01-18 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

Shulou(Shulou.com)06/03 Report--

This article is about the use of VMware vSAN on the Internet. The editor thought it was very practical, so I shared it with you to learn. The following information is about the use of VMware vSAN in the network.

Consider network features that provide availability, security, and bandwidth assurance in a vSAN cluster. Network failover and load balancing vSAN uses the binding and failover policies configured on backup virtual switches that are used only for network redundancy. VSAN does not bind NICs with load balancing.

If you plan to configure network card groups for availability, consider these failover configurations.

Binding algorithm

Failover configuration of adapters in a group active / passive routing based on source virtual port active / active routing based on IP hash, static EtherChannel for standard switches, and LACP port channels for distributed switches active / active routing based on physical network adapter load

VSAN supports IP hash load balancing, but there is no guarantee of improved performance for all configurations. When there are many IP hash users besides vSAN, you can benefit from IP hash. In this case, the IP hash performs load balancing. If vSAN is the only user, you may not see any improvement. This behavior is particularly suitable for 1-GbE environments. For example, if you use four 1-GbE physical adapters with an IP hash set for vSAN, you may actually be able to use no more than 1 Gbps. This behavior also applies to all Nic binding strategies supported by VMware.

VSAN does not support multiple VMkernel adapters on the same subnet. You can use different VMkernel adapters on different subnets, such as other VLAN or separate physical structures. Using multiple VMkernel adapters to provide availability results in configuration costs (including vSphere and network infrastructure). By binding a physical network adapter, you can improve network availability.

Using unicast in vSAN network

In vSAN6.6 and later versions, multicast is not required on physical switches that support vSAN clustering. You can design a simple unicast network for vSAN. Earlier versions of vSAN relied on multicast to enable detection signals and exchange metadata between hosts in the cluster. If some hosts in the vSAN cluster are running earlier versions of the software, a multicast network is still required. For more information about using multicast in vSAN clusters, see earlier versions of "Managing VMware vSAN."

Note: the following configuration is not supported: deploying vCenter Server on a vSAN6.6 cluster that uses an IP address without a reserved DHCP. You can use DHCP reservation because the assigned IP address is bundled to the MAC address of the VMkernel port.

Use Network I Control O Control to allocate bandwidth to vSAN

VSAN traffic can share 10-GbE physical network adapters with other system traffic types, such as vSphere vMotion traffic, vSphere HA traffic, and virtual machine traffic. To ensure the amount of bandwidth required by vSAN, use the

VSphere Network I/O Control .

In vSphere Network I Control O Control, you can configure reservations and shares for vSAN outbound traffic.

1. Set the reservation so that Network I Control O Control guarantees the minimum bandwidth available to the physical adapter of vSAN.

two。 Set the share so that when the physical adapter assigned to vSAN becomes saturated, vSAN still has specific bandwidth available and prevents vSAN

Takes up the full capacity of the physical adapter during rebuild and synchronization operations. For example, when other physical adapters in the group fail and all traffic in the port group is transferred to other adapters in the group, the physical adapter may become saturated.

For example, on 10-GbE physical adapters that handle vSAN, vSphere vMotion, and virtual machine traffic, you can configure specific bandwidth and share.

Table 3-3. Sample Network I _ vSAN O Control configuration of the physical adapter responsible for the

Traffic type reservation, Gbps share vSAN1

one hundred

VSphere vMotion0.5

70 virtual machine

0.5

thirty

If the 10-GbE adapter becomes saturated, the Network I Gbps O Control will allocate 5 Gbps to the vSAN on the physical adapter.

For information about configuring bandwidth allocation for vSAN traffic using vSphere Network Imax O Control, see the vSphere Network connection document.

Mark vSAN traffic

Priority marking is a traffic marking mechanism used to indicate vSAN traffic with high quality of service (Quality of Service, QoS) requirements in connected network devices. You can assign vSAN traffic to a specific class and use a service class (CoS) value (range 0 (low priority)

To 7 (high priority)) tag the traffic accordingly. Priority levels can be configured using vSphere Distributed Switch's traffic filtering and marking policies.

Segment vSAN traffic in VLAN

Consider isolating vSAN traffic in VLAN to enhance security and performance, especially if you share the capacity of backup physical adapters across multiple traffic types.

Giant frame

If you plan to use jumbo frames in vSAN to improve CPU performance, verify that jumbo frames are enabled on all network devices and hosts in the cluster.

By default, the TCP Segmentation cleanup (TSO) and large receive cleanup (LRO) features are enabled on ESXi. Consider whether using jumbo frames will improve performance enough to cover the cost of enabling jumbo frames on all nodes in the network.

Create a static route for a vSAN network connection

You may need to create a static route in a vSAN environment.

In traditional configurations, vSphere uses a single default gateway through which all routed traffic attempts to reach its destination.

However, some vSAN deployments may require static routes. For example, witness deployments on different networks or extended cluster deployments of data sites and witness hosts on different sites.

To configure a static route on an ESXi host, use the esxcli command:

Esxcli network ip route ipv4 add-n remote-network-g gateway-to-use

Remote-network is the remote network that your host must access, and gateway-to-use is the interface to use when sending traffic to the remote network.

On the use of VMware vSAN in the network to share here, I hope that the above content can be of some help to you, can learn more knowledge. If you like this article, you might as well share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report