NetApp HCI, Руководство пользователя

Страница: 37 / 363

IP address range Description
10.255.0.0/16 Docker swarm ingress network
169.254.100.1/22 Docker bridge network
169.254.104.0/22 Docker bridge network
Find more information
• NetApp HCI Resources page
• NetApp Element Plug-in for vCenter Server
Network configuration
Network configuration
NetApp HCI can utilize multiple different network cabling and VLAN configurations. It is
important to plan your network configuration to ensure a successful deployment.
Required network segments
NetApp HCI requires a minimum of three network segments: management, storage, and virtualization traffic
(which includes virtual machines and VMware vMotion traffic). You can also separate virtual machine and
vMotion traffic. These network segments usually exist as logically separated VLANs in the NetApp HCI network
infrastructure.
How compute and storage nodes connect to these networks depends on how you design the network and
cable the nodes. The sample network illustrations in this guide assume the following networks:
Network name VLAN ID
Management 100
Storage 105
vMotion 107
Virtual machines 200, 201
For automatic discovery and configuration of your NetApp HCI nodes in the NetApp Deployment Engine, you
must have a network segment that is available as an untagged or native VLAN on all switch ports that are used
for the SFP+/SFP28 interfaces on the nodes. This will provide layer 2 communication between all nodes for
discovery and deployment. Without a native VLAN, you must configure the SFP+/SFP28 interfaces of all nodes
manually with a VLAN and IPv4 address to be discoverable. In the network configuration examples in this
document, the management network (VLAN ID 100) is used for this purpose.
The NetApp Deployment Engine enables you to quickly configure networks for compute and storage nodes
during the initial deployment. You can place certain built-in management components such as vCenter and the
management node on their own network segment. These network segments require routing to allow vCenter
and the management node to communicate with storage and compute management networks. In most
deployments those components use the same management network (VLAN ID 100 in this example).