FusionCompute V100R005C10 Network Management Guide 01
FusionCompute V100R005C10 Network Management Guide 01
V100R005C10
Issue 01
Date 2015-11-11
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://e.huawei.com
Purpose
This document describes how to create, adjust, and reclaim network resources, such as
distributed virtual switches (DVSs), upstream links, and port groups, on the FusionCompute.
Intended Audience
This document is intended for:
l Technical support engineers
l Maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows:
Symbol Description
Symbol Description
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Issue 01 (2015-11-11)
This issue is the first official release.
Contents
5 Network Configuration.............................................................................................................. 52
5.1 Configuring the MAC Address Segment......................................................................................................................53
5.2 Enabling or Disabling IPv6 Forwarding.......................................................................................................................54
A Appendix......................................................................................................................................56
A.1 Parameter Reference.................................................................................................................................................... 57
A.1.1 DVS Parameters........................................................................................................................................................57
Summary
FusionCompute resources include host and cluster resources, network resources, and storage
resources. Network management involves the following operations for the FusionCompute:
create network resources, such as a distributed virtual switch (DVS) or a port group, and
adjust network resource configurations.
VM
Port group
DVS
Virtual
resources Uplink
Physical
resources
Physical network
Port group A port group is a virtual logical port similar to a template with
network attributes. A port group is used to define VM NIC attributes
and uses a DVS to connect to the network:
l Subnet: FusionCompute automatically allocates an IP address in
the subnet IP address pool to each NIC on VMs that use the port
group.
l VLAN: Users must manually assign IP addresses to VM NICs.
VMs connect to the VLAN defined by the port group.
Dual-stack is defined in RFC 4213. Both IPv4 and IPv6 protocols run on the both terminal
devices and network nodes, thereby implementing communication between IPv4 and IPv6
nodes. Nodes that have both IPv4 and IPv6 stacks deployed are named dual-stack nodes. They
can receive and send both IPv4 and IPv6 packets, and can communicate with IPv4 nodes over
the IPv4 network and communicate with IPv6 nodes over the IPv6 network.
The port on a dual-stack device can have only one IPv4 or IPv6 address configured, or have
both IPv4 and IPv6 addresses configured.
To assign an IPv6 address to a VM, you can deploy a third-party DHCPv6 server, use a
hardware gateway to implement stateless automatic assignment, or uses static IP address
injection.
In the FusionSphere system, both common NICs (HW_X_NET) and high-performance NICs
(HW_V_NET) support IPv6. The following functions also support IPv6:
l NIC bounding
l Traffic shaping
l Port mirroring
l Trunk port
The following functions does not support IPv6:
l IP-MAC binding
Add an uplink.
Associate the storage
No resource with hosts.
Is a Huawei SAN
device or an FC
SAN device (Optional) Add a VLAN
used? pool.
Scan storage devices.
Yes
Change the multiple (Optional) Add a subnet.
storage path.
Add a data store.
(Optional) Configuring a
Is the host VTEP Network.
connected to the No Create a disk.
storage device
using ISCSI.
Create a port group.
Yes
Add a storage port to the
host.
Procedure
Table 1-2 describes the creation procedure.
Prerequisites
Conditions
l You have logged in to FusionCompute.
l The host has been added to a cluster.
Procedure
If the DVS type is set to Standard, the Internet Group Management Protocol (IGMP) snooping
function is available by default. If the DVS type is set to VMDq-enabled or SR-IOV-enabled, the
option for this function is unavailable.
To run multicast services, IGMP snooping must be enabled on the DVS, and switch IGMP
listening and the device querier must be enabled for the multicast tunnel. These functions for the
multicast tunnel can be enabled in the switch shell. For details, see the switch configuration guide.
VXLAN packets on underlying virtual switches do not support IGMP snooping.
IGMP Snooping in the system of the current version supports only IGMPv2 multicast packets.
4 Determine whether to select Add uplink, Add VLAN pool, or both.
– If yes, go to 7.
– If no, go to 5.
5 Click Next.
The system displays a message indicating that the DVS is created.
6 Click OK.
The DVS creation task is complete.
No further action is required.
7 Select Add uplink or Add VLAN pool, or both, and click Next.
NOTICE
– In all load sharing modes, aggregation must be configured on the switch to which
network ports are connected, that is, the ports to be bound must be configured on the
same Eth-trunk port on the switch. Otherwise, network exception may occur.
– In the Link Aggregation Control Protocol (LACP) mode, create an Eth-trunk in
LACP mode on the switch to which network ports are connected, configure ports to
be bound on the same Eth-trunk, and enable the bridge protocol data unit (BPTU)
protocol packet forwarding function on the Eth-trunk. For example, if the switch is
Huawei S5300, run the following commands:
<S5352_01>sys
[S5352_01]interface Eth-Trunk x
[S5352_01-Eth-Trunkx]mode lacp-static
[S5352_01-Eth-Trunkx]bpdu enable
For details about how to configure port aggregation on a switch, see the switch user
guide.
In the middle of the page, set Name and Binding Mode for the network ports.
The following binding modes are available for common network interface cards (NICs):
– Active-backup: applies to scenarios where two network ports are to be bound. This
mode provides high reliability. The bandwidth of the bound port in this mode equals
to that of a member port.
– Round-robin: applies to scenarios where two or more network ports are to be
bound. The bandwidth of the bound port in this mode is higher than that of a
member port, because the member ports share workloads in sequence.
This mode may result in data packet disorder because traffic is evenly sent to each
port. Therefore, MAC address based load balancing prevails over Polling in load
sharing modes.
– IP address and port-based load balancing: applies to scenarios where two or
more network ports are to be bound. The bandwidth of the bound port in this mode
is higher than that of a member port, because the member ports share workloads
based on the source-destination-port-based load sharing algorithm.
higher than that of a member port, because the member ports share workloads based
on the IP address of the source port.
– Destination IP address-based load balancing: applies to scenarios where two or
more network ports are to be bound. The bandwidth of the bound port in this mode
is higher than that of a member port, because the member ports share workloads
based on the IP address of the destination port.
This mode is recommended when most network traffic is on the layer 3 network.
This mode allows network traffic to be evenly distributed based on the destination
IP addresses.
12 Click Bind.
An information dialog box is displayed.
13 Click OK.
The Bind Network Port page is displayed.
14 Click OK.
The Add uplink page is displayed.
15 Check whether to configure virtual tunnel end point (VTEP) for the VXLAN used on
FusionManager.
– If yes, go to 16.
NOTE
When you configure the VXLAN function, allocate the IP address from the VTEP network to the
software router, so that the software router can communicate with VTEPs on hosts. For details,
see the VXLAN chapter in the FusionManager V100R005C10 Administrator Guide.
– If no, go to 19.
16 Locate the row that contains the host and click Configure VTEP.
The Configure VTEP page is displayed.
17 Configure VTEP information.
– IP: specifies the IP address planned for the VTEP.
NOTE
The following conditions must be met when you configure the IP address of the VTEP.
n The IP address of the VTEP cannot be in the same network segment as that of other
system interfaces on the same host.
n The IP address of the VTEP cannot be in the same network segment as that of other
VTEPs on the same host.
n The IP address of the VTEP must be unique.
– Subnet mask: specifies the subnet mask of the VTEP.
– Gateway: specifies the gateway address of the VTEP.
– Outer VLAN: specifies the VLAN to be used by the VTEP. The VLAN must be
different from the VLANs used by the management, storage, and service planes.
– LLDP: specifies the LLDP service. If this service is enabled, the host topology can
be reported to the switch using the LLDP protocol.
18 Click OK.
The Add uplink page is displayed.
19 Select the uplink ports or the bound uplink port on the host, as shown in Figure 2-2.
23 Enter the start VLAN ID and the end VLAN ID of the VLAN pool.
24 Click OK.
25 Click Next.
The Confirm page is displayed.
26 Click Create.
The system displays a message indicating that the DVS is created.
27 Click OK.
----End
Prerequisites
Conditions
You have logged in to FusionCompute.
Data
You have obtained the name of the DVS to be queried.
Procedure
Query information about all the distributed virtual switches (DVSs).
1 On FusionCompute, click Network Pool.
The Network Pool page is displayed.
2 Click the DVS tab and view the information about all the DVSs, including the DVS
name, DVS type, description, port groups, and whether Internet Group Management
Protocol (IGMP) snooping is enabled, as shown in Figure 2-4.
NOTE
If the DVS type is Standard, information about whether the IGMP snooping function is enabled is
available. If the DVS type is VMDq-enabled or SR-IOV-enabled, the IGMP snooping function is
unavailable.
– If yes, go to 3.
– If no, no further action is required.
Query the detailed information about a DVS.
----End
Scenarios
On FusionCompute, delete an unwanted distributed virtual switch (DVS).
Prerequisites
Conditions
l You have logged in to FusionCompute.
l The DVS to be deleted does not contain any port group.
Procedure
Step 1 On FusionCompute, click Network Pool.
The Network Pool page is displayed.
Step 2 In the navigation tree on the left, select the target DVS, right-click the DVS to be deleted, and
choose Delete.
An information dialog box is displayed, asking you whether to delete the DVS.
Step 3 Click OK.
An information dialog box is displayed, indicating that the DVS is deleted.
Step 4 Click OK.
The DVS is deleted.
----End
Prerequisites
Conditions
Procedure
4 Enter the start VLAN ID and the end VLAN ID of the VLAN pool.
5 Click OK.
An information dialog box is displayed.
6 Click OK.
The VLAN pool is added on the DVS.
Follow-up Procedure
Create port groups. For details, see Creating a Port Group.
----End
Prerequisites
Conditions
Procedure
Step 1 On FusionCompute, click Network Pool.
The Network Pool page is displayed.
Step 2 In the navigation tree on the left, expand Network Pool and select the DVS.
The Getting Started page is displayed.
Step 3 On the VLAN Pool page, locate the row that contains the VLAN pool, click Delete VLAN
Segment.
A dialog box is displayed, as shown in Figure 2-6.
Step 4 Set the start VLAN ID and the end VLAN ID of the VLAN pool to be deleted.
----End
Prerequisites
Conditions
You have logged in to FusionCompute.
You have configured the DHCP relay on the switch. For details, see Example of Configuring
Switch.
Procedure
3 Set the following subnet parameters: Name, Description, Subnet, Subnet mask,
Gateway, Reserved IP segment, Domain name, Preferred DNS server/Alternate
DNS server, Preferred WINS server/Alternate WINS server, and VLAN ID.
Note the configuration requirements for the following parameters:
– Subnet: specifies the network segment for the subnet, for example, 192.168.80.0.
– Reserved IP segment: specifies the reserved IP address segment in which the IP
addresses are not allocated to the VMs that use this port group. The system supports
a maximum of three reserved IP address segments.
– Domain name: specifies the domain name for the subnet. The value is a string of
225 characters that consist of case-insensitive letters, digits, and hyphens (-). The
value cannot start or end with a hyphen (-).
Prerequisites
Conditions
l You have logged in to FusionCompute.
l The VMs using this subnet are stopped.
Procedure
Step 1 On FusionCompute, click Network Pool.
The Network Pool page is displayed.
Step 2 Click the Subnet tab, and select the target subnet.
Step 5 Set the following subnet parameters: Name, Description, Subnet, Subnet mask, Gateway,
Reserved IP segment, Domain name, Preferred DNS server/Alternate DNS server,
Preferred WINS server/Alternate WINS server, and VLAN ID.
Note the configuration requirements for the following parameters:
l Subnet: specifies the network segment for the subnet, for example, 192.168.80.0.
l Reserved IP segment: specifies the reserved IP address segment in which the IP
addresses are not allocated to the VMs that use this port group. The system supports a
maximum of three reserved IP address segments.
l Domain name: specifies the domain name for the subnet. The value is a string of 225
characters that consist of case-insensitive letters, digits, and hyphens (-). The value
cannot start or end with a hyphen (-).
l Preferred DNS server/Alternate DNS server: specifies the IP addresses of the active
and standby DNS server.
l Preferred WINS server/Alternate WINS server: specifies the IP addresses of the
active and standby WINS server.
l VLAN ID: specifies the ID of the VLAN with which the subnet is associated.
----End
Prerequisites
Conditions
l You have logged in to FusionCompute.
l The subnet to be deleted is not used by any port group.
Procedure
Step 1 On FusionCompute, click Network Pool.
The Network Pool page is displayed.
Step 2 Click the Subnet tab, and select the target subnet.
----End
Scenarios
On FusionCompute, create a port mirroring session. The port mirroring session can mirror
packets from a source port to a destination port so that the system can monitor traffic on the
source port from the destination port for data analysis and network fault diagnosis.
NOTE
Declaration: This feature is a high-risk feature. Using this feature complies with industry practices. However,
end user data may be required for implementing the feature. Exercise caution and obtain end user's consent
when using this feature.
Port mirroring allows you to obtain data packets received and sent by the user VM NICs. If the end user data
is involved, obtain end user's consent before you create the port mirroring session.
When you configure a port mirroring session, do not select VRM VM NICs. Otherwise, VRM
communication is adversely affected, and an active/standby switchover may be triggered. After a port
mirroring session is configured, resource consumption in the system is increased, thereby degrading VM
network performance.
In a port mirroring session, a port can only be a source port or a destination port.
A port mirroring session cannot be created on a DVS type is set to VMDq-enabled or SR-
IOV-enabled.
The two physical switch ports connected to two uplinks used by port groups of the VMs
providing the source and destination ports can communicate with each other using the
dedicated VLAN.
NOTE
After the local port mirroring session function is enabled on a DVS port, the port is prone to data leakage
risks. Therefore, exercise caution when enabling this function on a port.
Prerequisites
Conditions
You have logged in to FusionCompute.
Procedure
Determine the type of the port mirroring session to be created.
1 Perform the required operation based on the port mirroring session type.
– To create a distributed port mirroring session, go to 2.
– To create a remote port mirroring session, go to 16.
Create a distributed port mirroring session.
2 On FusionCompute, click Network Pool.
The Network Pool page is displayed.
3 In the navigation tree on the left, expand Network Pool and select the DVS.
The Getting Started page is displayed.
4 Click Create Port Mirroring Session.
The Basic Information page is displayed, as shown in Figure 2-9.
– Ingress: indicates that the traffic transmitted through the source port to the DVS.
– Egress: indicates that the traffic transmitted through the source port from the DVS.
– Ingress/Egress: indicates that the traffic transmitted through the source port to and
from the DVS.
10 Click Next.
The Select Destination Port page is displayed.
11 Click Add.
The Select Port dialog box is displayed.
12 Select destination ports and click Save.
Destination ports are identified based on MAC addresses. You can select a maximum of
four destination ports for a port mirroring session.
13 Click Next.
The Verify Information page is displayed.
14 Confirm the information and click Create.
A dialog box is displayed.
15 Click OK.
The distributed port mirroring session is successfully created.
Create a remote source port mirroring session.
Before creating a remote port mirroring session, log in to the physical switch, disable the
MAC address learning function on the dedicated VLAN of the ports, and clear up all dynamic
MAC address entries that map the VLAN. For example, if the switch is HUAWEI Quidway
S5352, run the mac-address learning disable command on the VLAN interface and run the
undo mac-address dynamic vlan Dedicated VLAN ID command in the system view.
16 On FusionCompute, click Network Pool.
The Network Pool page is displayed.
17 In the navigation tree on the left, expand Network Pool and click the DVS that provides
the source ports.
The Getting Started page is displayed.
18 Click Create Port Mirroring Session.
The Basic Information page is displayed.
19 Enter the following information about the port mirroring session:
– Name
– Status: specifies the start status of the port mirroring session.
– Mirroring Session Type: Set to Remote mirroring source.
– Encapsulation VLAN ID: specifies the ID of the dedicated VLAN for the
mirroring data.
– Preserve original VLAN: If this parameter is select, the mirroring packets contain
two VLANs (inner VLAN and out VLAN). The inner VLAN is the original VLAN,
and the outer VLAN is the dedicated VLAN.
– Mirrored packet length (Bytes): specifies the length of the mirrored packets. This
parameter puts a limit on the size of mirrored packets. If this parameter is selected,
all mirrored packets are truncated to the specified length.
– Description
NOTE
If Preserve original VLAN is selected and Mirrored packet length (Bytes) is deselected,
mirroring packets received by the destination ports may be incomplete because mirroring packets
with more than 1514 bytes will be truncated to 1514 bytes.
20 Click Next.
The Select Source Port page is displayed.
21 Click Add.
The Select Port dialog box is displayed.
22 Select source ports and click Save.
Source ports are identified based on MAC addresses. You can select a maximum of four
source ports for a port mirroring session.
23 To change the direction of traffic for creating a port mirroring session, select the source
ports and select Ingress, Egress, or Ingress/Egress.
The default value is Ingress/Egress.
– Ingress: indicates that the traffic transmitted through the source port to the DVS.
– Egress: indicates that the traffic transmitted through the source port from the DVS.
– Ingress/Egress: indicates that the traffic transmitted through the source port to and
from the DVS.
24 Click Next.
The Select Destination Port page is displayed.
25 Click Next.
The Verify Information page is displayed.
26 Confirm the information and click Create.
A dialog box is displayed.
27 Click OK.
The remote source port mirroring session is successfully created.
Create a remote destination port mirroring session.
Before you create a remote port mirroring session, ensure that source ports for the remote port
mirroring session have been created in the system.
28 On FusionCompute, click Network Pool.
The Network Pool page is displayed.
29 In the navigation tree on the left, expand Network Pool and click the DVS that provides
the destination ports.
The Getting Started page is displayed.
30 Click Create Port Mirroring Session.
The Basic Information page is displayed.
31 Enter the following information about the port mirroring session:
– Name
– Status: specifies the start status of the port mirroring session.
– Mirroring Session Type: Set to Remote mirroring destination.
– Normal I/O on destination ports: specifies whether normal traffic is allowed to
pass through destination ports. If this parameter is set to Not allowed, only traffic
for creating a port mirroring session is allowed to pass through destination ports.
– Description
32 Click Next.
The Select Source Port page is displayed.
33 Select VLAN IDs.
34 Click Next.
The Select Destination Port page is displayed.
35 Click Add.
The Select Port dialog box is displayed.
36 Select destination ports and click Save.
Destination ports are identified based on MAC addresses. You can select a maximum of
four destination ports for a port mirroring session.
37 Click Next.
The Verify Information page is displayed.
38 Confirm the information and click Create.
A dialog box is displayed.
39 Click OK.
The remote destination port mirroring session is successfully created.
----End
Scenarios
On FusionCompute, modify the parameters of a port mirroring session.
Note the following limitations on port mirroring session modification:
l To enable a distributed port mirroring session, you must ensure that the VMs providing
the source and destination ports run on the same host.
l In a port mirroring session, a port can only be a source port or a destination port.
l During modification, the source port and destination port in the same mirroring session
cannot be exchanged. To exchange them, delete the mirroring session and create a new
session.
NOTE
When you configure a port mirroring session, do not select VRM VM NICs. Otherwise, VRM
communication is adversely affected, and an active/standby switchover may be triggered. After a port
mirroring session is configured, resource consumption in the system is increased, thereby degrading VM
network performance.
Prerequisites
Conditions
You have logged in to FusionCompute.
Procedure
Modify parameters of a distributed port mirroring session.
25 Click Next.
The Select Destination Port page is displayed.
26 Click Next.
The Verify Information page is displayed.
27 Confirm the information and click Modify.
A dialog box is displayed.
28 Click OK.
The remote source port mirroring session is successfully modified.
Modify parameters of a remote destination port mirroring session.
29 On FusionCompute, click Network Pool.
The Network Pool page is displayed.
30 In the navigation tree on the left, expand Network Pool and click the DVS that provides
the destination ports.
The Getting Started page is displayed.
31 Choose Port > Port Mirroring.
All the port mirroring sessions of the DVS are displayed.
32 Locate the row that contains the port mirroring session, click Modify.
The Basic Information page is displayed.
33 Enter the following information about the port mirroring session:
– Name
– Status: specifies the start status of the port mirroring session.
– Normal I/O on destination ports: specifies whether normal traffic is allowed to
pass through destination ports. If this parameter is set to Not allowed, only traffic
for creating a port mirroring session is allowed to pass through destination ports.
– Description
34 Click Next.
The Select Source Port page is displayed.
35 Click Add.
The Add VLAN ID dialog box is displayed.
36 Enter the VLAN IDs of the source ports and click OK.
You can enter a maximum of four VLANs for a port mirroring session.
37 Click Next.
The Select Destination Port page is displayed.
38 Click Add.
The Select Port dialog box is displayed.
39 Select destination ports and click Save.
Destination ports are identified based on MAC addresses. You can select a maximum of
four destination ports for a port mirroring session.
40 Click Next.
The Verify Information page is displayed.
41 Confirm the information and click Modify.
A dialog box is displayed.
42 Click OK.
The remote destination port mirroring session is successfully created.
----End
Scenarios
On FusionCompute, query and view information about a port mirroring session.
Prerequisites
Conditions
You have logged in to FusionCompute.
Procedure
5 Click the Source ports or Destination ports tab to view the source ports or destination
ports in the port mirroring session.
----End
Scenarios
On FusionCompute, delete a port mirroring session.
Prerequisites
Conditions
You have logged in to FusionCompute.
Procedure
Scenarios
On FusionCompute, add an uplink to a distributed virtual switch (DVS) to provide network
resources for VMs.
The uplink can be composed of an independent uplink port on a host or a bound uplink port
on the host.
Prerequisites
Conditions
l You have logged in to FusionCompute.
l The host has been added to a cluster.
l The DVS has been created.
Procedure
Step 1 On FusionCompute, click Network Pool.
The Network Pool page is displayed.
Step 2 In the navigation tree on the left, expand Network Pool and select the DVS.
The Getting Started page is displayed.
Step 4 Determine whether to bind the uplink ports on the host to improve network reliability.
NOTE
If the host uses intelligent network interface cards (iNICs), bind the uplink network ports on the host together.
Otherwise, the broadcast suppression function of the port group may be adversely affected.
l If yes, go to Step 5.
l If no, go to Step 11.
Step 5 Locate the row containing the target host and click Bind Network Port.
The Bind Network Port page is displayed, as shown in Figure 3-2.
Step 6 In the Network Port list, select the physical network ports to be bound.
Step 7
NOTICE
l In all load sharing modes, aggregation must be configured on the switch to which network
ports are connected, that is, the ports to be bound must be configured on the same Eth-
trunk port on the switch. Otherwise, network exception may occur.
l In the Link Aggregation Control Protocol (LACP) mode, create an Eth-trunk in LACP
mode on the switch to which network ports are connected, configure ports to be bound on
the same Eth-trunk, and enable the bridge protocol data unit (BPTU) protocol packet
forwarding function on the Eth-trunk. For example, if the switch is Huawei S5300, run the
following commands:
<S5352_01>sys
[S5352_01]interface Eth-Trunk x
[S5352_01-Eth-Trunkx]mode lacp-static
[S5352_01-Eth-Trunkx]bpdu enable
For details about how to configure port aggregation on a switch, see the switch user guide.
In the middle of the page, set Name and Binding Mode for the network ports.
The following binding modes are available for common network interface cards (NICs):
l Active-backup: applies to scenarios where two network ports are to be bound. This
mode provides high reliability. The bandwidth of the bound port in this mode equals to
that of a member port.
l Round-robin: applies to scenarios where two or more network ports are to be bound.
The bandwidth of the bound port in this mode is higher than that of a member port,
because the member ports share workloads in sequence.
This mode may result in data packet disorder because traffic is evenly sent to each port.
Therefore, MAC address based load balancing prevails over Polling in load sharing
modes.
l IP address and port-based load balancing: applies to scenarios where two or more
network ports are to be bound. The bandwidth of the bound port in this mode is higher
than that of a member port, because the member ports share workloads based on the
source-destination-port-based load sharing algorithm.
than that of a member port, because the member ports share workloads based on the IP
address of the destination port.
This mode is recommended when most network traffic is on the layer 3 network. This
mode allows network traffic to be evenly distributed based on the destination IP
addresses.
Step 8 Click Bind.
An information dialog box is displayed.
Step 9 Click OK.
The Bind Network Port page is displayed.
Step 10 Click OK.
The Add uplink page is displayed.
Step 11 Check whether to configure virtual tunnel end point (VTEP) for the VXLAN used on
FusionManager.
l If yes, go to Step 12.
NOTE
The VTEP network assigns IP addresses to software firewalls. With the IP address, the software
firewall can communicate with the the VTEP on the host. For details, see VXLAN in the
FusionManager V100R005C10 Administrator Guide.
l If no, go to Step 15.
Step 12 Locate the row that contains the host and click Configure VTEP.
The Configure VTEP page is displayed.
Step 13 Configure VTEP information.
l IP: specifies the IP address planned for the VTEP.
NOTE
The following conditions must be met when you configure the IP address of the VTEP.
– The IP address of the VTEP cannot be in the same network segment as that of other system
interfaces on the same host.
– The IP address of the VTEP cannot be in the same network segment as that of other VTEPs on
the same host.
– The IP address of the VTEP must be unique.
l Subnet mask: specifies the subnet mask of the VTEP.
l Gateway: specifies the gateway address of the VTEP.
l Outer VLAN: specifies the VLAN to be used by the VTEP. The VLAN must be
different from the VLANs used by the management, storage, and service planes.
l LLDP: specifies the LLDP service. If this service is enabled, the host topology can be
reported to the switch using the LLDP protocol.
Step 14 Click OK.
The Add uplink page is displayed.
Step 15 Click Refresh in the upper right corner, select an uplink port or bound uplink port on the host,
and click OK.
An information dialog box is displayed.
Step 16 click OK.
----End
Prerequisites
Conditions
You have logged in to FusionCompute.
Data
You have obtained the name of the uplink to be queried.
Procedure
9 In the navigation tree on the left, expand Network Pool, select the DVS, and click
Uplink Group.
The Getting Started page is displayed.
10 Query the information about the host that uses the uplink on the Host page.
No further action is required.
----End
Scenarios
On FusionCompute, delete an uplink from a virtual distributed switch (DVS).
Prerequisites
Conditions
l You have logged in to FusionCompute.
l The VMs on the host that uses the uplink has been deleted or migrated.
Procedure
Step 1 On FusionCompute, click Network Pool.
The Network Pool page is displayed.
Step 2 In the navigation tree on the left, expand Network Pool, select the DVS, and click Uplink
Group.
Step 4 Locate the row that contains the uplink to be deleted, click Remove from DVS.
A confirmation dialog box is displayed.
----End
If FusionCompute has been connected to FusionManager and VTEP networks have been
configured on FusionCompute, update the hypervisor information on FusionManager so that
the VTEP networks can be used on FusionManager.
Prerequisites
Conditions
l You have logged in to FusionCompute.
l The network segment to be used by VTEP networks has been planned and is different
than the network segments used by the management, storage, and service planes.
l The virtual local area network (VLAN) to be used by VTEP networks has been planned
and is different than the VLANs used by the management, storage, and service planes.
l The host network interface cards (NICs) are not intelligent NICs (iNICs), because iNICs
do not support VXLAN.
Procedure
Determine method of configuring VTEP networks.
NOTE
The following conditions must be met when you configure the IP address of the VTEP.
n The IP address of the VTEP cannot be in the same network segment as that of other
system interfaces on the same host.
n The IP address of the VTEP cannot be in the same network segment as that of other
VTEPs on the same host.
n The IP address of the VTEP must be unique.
– VTEP Subnet Mask: specifies the subnet mask of the VTEP network.
– VTEP Gateway IP Address: specifies the gateway address of the VTEP network.
– VTEP Outer VLAN ID: specifies the VLAN planned for the VTEP. The VLAN
must be different from the VLANs used by the management, storage, and service
planes.
– LLDP: specifies the Link Layer Discovery Protocol (LLDP) service. If this service
is enabled, the host topology can be reported to the switch using the LLDP protocol.
For details about the parameters, see the help sheet in the template.
9 After information about all VTEP networks is configured, save and close the template
file.
10 On the Add VXLAN VTEP in Batches page, click Browse on the right of Import
template file.
A dialog box is displayed.
11 Select the configured template file and click Open.
12 Click OK.
An information dialog box is displayed.
13 Click OK.
The VTEP networks are configured.
No further action is required.
Configure a VTEP network one by one.
14 On FusionCompute, click Network Pool.
The Network Pool page is displayed.
15 In the navigation tree on the left, expand Network Pool, select the DVS, and click
Uplink Group.
The Getting Started page is displayed.
16 On the Network Port page, locate the row that contains the uplink to be configured,
click Configure VTEP.
A dialog box is displayed.
17 Configure VTEP information.
– IP: specifies the IP address planned for the VTEP.
NOTE
The following conditions must be met when you configure the IP address of the VTEP.
n The IP address of the VTEP cannot be in the same network segment as that of other
system interfaces on the same host.
n The IP address of the VTEP cannot be in the same network segment as that of other
VTEPs on the same host.
n The IP address of the VTEP must be unique.
NOTE
In the FusionSphere solution, if both FusionCompute and FusionManager are in use, and FusionManager is
used to provision VMS, no port group on the DVS on the service plane is required.
Prerequisites
Conditions
l A VLAN pool or subnet has been added.
l You have logged in to FusionCompute.
Procedure
Step 1 On FusionCompute, click Network Pool.
The Network Pool page is displayed.
Step 2 In the navigation tree on the left, expand Network Pool and select the DVS.
The Getting Started page is displayed.
Step 3 Click Create Port Group.
The Basic Information page is displayed, as shown in Figure 4-1.
Step 4 Specify the following basic information about the port group:
NOTE
To use the broadcast suppression function, the uplink network ports on the host that uses intelligent network
interface cards (iNICs) must be bound together. For details, see System Port Management > Binding
Network Ports in the FusionCompute V100R005C10 Host and Cluster Management Guide.
To add management VM ports to the port group, set the average send and receive bandwidths, peak send and
receive bandwidths, and burst send and receive sizes to values greater than or equal to 1000 or do not limit
these rates.
l Name
l Description
l Port type: specifies the type of the port to be added to the port group. An access port can
be added to only one VLAN, and a trunk port can be added to multiple VLANs. Set the
port type to Access for a common VM. If the NIC of a common VM uses a VLAN
tagging device, ensure to set the port type for the VM to Trunk.
If the ports added to a port group are set to trunk mode on a Linux VM, multiple VLAN
tagging devices can be created on the VM to transmit data packets from different
VLANs over one virtual NIC, exempting the VM from using multiple virtual NICs.
l Outbound Traffic Shaping
– Average send bandwidth (Mbit/s): specifies the average number of bits per second
to allow across a port during a certain period of time.
If a common NIC is used, the port traffic remains close to the configured average
bandwidth when no burst of traffic occurs. If an iNIC is used, the average
bandwidth is equal to the minimum bandwidth when no congestion occurs on the
network. If the burst send size is set to a too small value, the network bandwidth
decreases.
– Peak send bandwidth (Mbit/s): specifies the maximum number of bits per second
to allow across a port when it is sending a burst of traffic.
The peak send bandwidth must be greater than or equal to the average send
bandwidth. A proper peak send bandwidth set for a service prevents network
congestion on other VM networks when the traffic of this service is too large. When
an iNIC is used, the peak send bandwidth is equal to the maximum bandwidth after
the burst of traffic disappears, and in the idle period, the bandwidth remains around
the peak send bandwidth.
– Burst send size (Mbits): specifies the maximum number of bytes to allow in a
burst.
– Priority: specifies the priority of a system port or virtual switch port (VSP) for
using the bandwidth on a physical network traffic when network congestion occurs.
A port with a higher priority is able to gain more bandwidths.
The bandwidth range varies in different scenarios. If the number of bits allowed
across a physical port per second is greater than the sum of average bandwidths of
system ports and VSPs on a server and less than the sum of their peak bandwidths,
the traffic on each VM created on the server is greater than the average bandwidth
but no more than the peak bandwidth of the system ports and VSPs. If the number
of bits allowed across a physical port per second is less than the sum of average
bandwidths of system ports and VSPs on the server, the minimum traffic of each
VM may be less than the average bandwidth and the maximum traffic is less than
the peak bandwidth of system ports and VSPs.
l Inbound Traffic Shaping
– Average receive bandwidth (Mbit/s): specifies the average number of bits per
second to allow across a port during a certain period of time.
If a common NIC is used, the port traffic remains close to the configured average
bandwidth when no burst of traffic occurs. If an iNIC is used, the average
bandwidth is equal to the minimum bandwidth when no congestion occurs on the
network. If the burst send size is set to a too small value, the network bandwidth
decreases.
– Peak receive bandwidth (Mbit/s): specifies the maximum number of bits per
second to allow across a port when it is receiving a burst of traffic.
The peak receive bandwidth must be greater than or equal to the average receive
bandwidth. When an iNIC is used, the peak receive bandwidth is equal to the
maximum receive bandwidth after the burst of traffic disappears, and in the idle
period, the bandwidth remains around the peak receive bandwidth.
– Burst receive size (Mbits): specifies the maximum number of bytes to allow in a
burst.
l ARP broadcast suppression (Kbit/s): specifies the allowed transmission bandwidth for
Address Resolution Protocol (ARP) broadcast packets. ARP broadcast suppression limits
the number of ARP broadcast packets that can be sent by VMs, preventing ARP
broadcast packet attacks.
l IP broadcast suppression (Kbit/s): specifies the allowed transmission bandwidth for IP
broadcast packets. IP broadcast suppression limits the number of IP broadcast packets
that can be sent by VMs, preventing IP broadcast packet attacks.
l DHCP quarantine: specifies whether to forbid users from enabling the DHCP server
service for a VM. If this parameter is selected, users are not allowed to enable the DHCP
Server service whenever unintentionally or maliciously. Otherwise, VM IP address
allocation is affected.
NOTE
Declaration: This feature is a secure feature. It enhances end user data security.
l IP-MAC binding: binds the IP address and MAC address of the VM that uses the port
group. This function enhances VM network security because it prevents users from
initiating IP address or MAC address spoofing attacks after changing the IP address or
MAC address of the VM NIC. This parameter is valid only when Port type is set to
Access. Do not enable this function if a VM NIC is configured with multiple IP
addresses, because this function may cause communication exceptions for some IP
addresses of this NIC.
NOTE
Declaration: This feature is a secure feature. It enhances end user data security.
l TCP checksum calculation: this enables FusionCompute to automatically calculate the
TCP checksum when VMs in this port group receive packets. Enable this function only
when the checksum accuracy is high priority as it may impact VM network receive
performance.
Step 5 Click Next.
The Network Connection page is displayed.
Step 6 Perform the required operation based on the selected port type.
l If Access is selected, go to Step 8.
l If Trunk is selected, go to Step 7.
Step 7 Enter the allowed VLAN range in the VLAN text box and go to Step 16.
Note the following requirements for specifying the VLAN parameter:
l VLANs length 1-2047.
l Enter single VLAN IDs or VLAN ID ranges.
l VLAN IDs can range in value from 1 to 4094, VLAN IDs can range in the VLAN pool
of the DVS.
l When entering a VLAN ID range, use the format A-B, where the value of A less than the
value of B.
l When entering multiple VLAN IDs or VLAN ID ranges, use commas (,) to separate the
IDs or ranges.
Step 8 Set Connection mode for the port group.
Step 9 Perform the required operation based on the selected connection mode.
l If the selected connection mode is subnet, go to Step 11.
l If VLAN is selected, go to Step 10.
Step 10 Set VLAN ID, and go to Step 16.
NOTE
The specified VLAN ID must be contained in the VLAN pool of the distributed virtual switch that
provides the port group.
Step 11 Check whether a subnet resource for the port group is available in the subnet list.
Step 13 Set the following subnet parameters: Name, Description, Subnet, Subnet mask, Gateway,
Reserved IP segment, Domain name, Preferred DNS server/Alternate DNS server,
Preferred WINS server/Alternate WINS server, and VLAN ID.
Note the configuration requirements for the following parameters:
l Domain name: Enter the domain name of the server used by the subnet.
l Preferred DNS server: Enter the DNS address used by the subnet.
l Preferred WINS server: Enter the Windows Internet Name Service (WINS) server
address used by the subnet.
l VLAN ID: Enter the VLAN ID configured for the port group. The specified VLAN ID
must be contained in the VLAN pool of the DVS that provides the port group.
Step 15 In the subnet list on the left, select the subnet configured for the port group.
----End
Prerequisites
Conditions
You have logged in to FusionCompute.
Data
You have obtained the name of the port group to be queried.
Procedure
----End
The VLAN of the management port group, that is, the port group used by Virtualization
Resource Management (VRM) VMs, cannot be changed using the method provided in this
section. For details about how to change the management plane VLAN, see Changing the
Management Plane VLAN in the FusionCompute V100R005C10 Configuration
Management Guide.
Advanced settings of a port group, such as quality of service (QoS), traffic shaping, Address
Resolution Protocol (ARP) broadcast suppression, Dynamic Host Configuration Protocol
(DHCP) isolation, and IP-MAC binding, are available to a VM only after Tools is installed on
the VM.
Prerequisites
Conditions
Procedure
Query the port group attributes.
1 On FusionCompute, click Network Pool.
The Network Pool page is displayed.
2 In the navigation tree on the left, choose Network Pool, and click the target DVS.
The Getting Started page is displayed.
3 On the Port Group page, set the search criteria and click Search.
The port groups that meet the search criteria are displayed.
Search criteria can be Port Group Name, VLAN, and VXLAN.
Modify the attributes of the port group.
4 In the port group list, click the name of the port group.
The Getting Started page is displayed.
5 Click Network Settings.
The Network Settings dialog box is displayed, as shown in Figure 4-3.
NOTE
To add management VM ports to the port group, set the average send and receive bandwidths,
peak send and receive bandwidths, and burst send and receive sizes to values greater than or equal
to 1000 or do not limit these rates.
– Port type: specifies the type of the port to be added to the port group. An access
port can be added to only one VLAN, and a trunk port can be added to multiple
VLANs. Set the port type to Access for a common VM. If the NIC of a common
VM uses a VLAN tagging device, ensure to set the port type for the VM to Trunk.
If the ports added to a port group are set to trunk mode on a Linux VM, multiple
VLAN tagging devices can be created on the VM to transmit data packets from
different VLANs over one virtual NIC, exempting the VM from using multiple
virtual NICs.
– VLAN ID: specifies the VLAN ID configured for the port group.
– Outbound Traffic Shaping
n Average send bandwidth (Mbit/s): specifies the average number of bits per
second to allow across a port during a certain period of time.
If a common NIC is used, the port traffic remains close to the configured
average bandwidth when no burst of traffic occurs. If an iNIC is used, the
average bandwidth is equal to the minimum bandwidth when no congestion
occurs on the network. If the burst send size is set to a too small value, the
network bandwidth decreases.
n Peak send bandwidth (Mbit/s): specifies the maximum number of bits per
second to allow across a port when it is sending a burst of traffic.
The peak send bandwidth must be greater than or equal to the average send
bandwidth. A proper peak send bandwidth set for a service prevents network
congestion on other VM networks when the traffic of this service is too large.
When an iNIC is used, the peak send bandwidth is equal to the maximum
bandwidth after the burst of traffic disappears, and in the idle period, the
bandwidth remains around the peak send bandwidth.
n Burst send size (Mbits): specifies the maximum number of bytes to allow in a
burst.
n Priority: specifies the priority of a system port or virtual switch port (VSP) for
using the bandwidth on a physical network traffic when network congestion
occurs. A port with a higher priority is able to gain more bandwidths.
The bandwidth range varies in different scenarios. If the number of bits
allowed across a physical port per second is greater than the sum of average
bandwidths of system ports and VSPs on a server and less than the sum of
their peak bandwidths, the traffic on each VM created on the server is greater
than the average bandwidth but no more than the peak bandwidth of the
system ports and VSPs. If the number of bits allowed across a physical port
per second is less than the sum of average bandwidths of system ports and
VSPs on the server, the minimum traffic of each VM may be less than the
average bandwidth and the maximum traffic is less than the peak bandwidth of
system ports and VSPs.
– Inbound Traffic Shaping
n Average receive bandwidth (Mbit/s): specifies the average number of bits
per second to allow across a port during a certain period of time.
If a common NIC is used, the port traffic remains close to the configured
average bandwidth when no burst of traffic occurs. If an iNIC is used, the
average bandwidth is equal to the minimum bandwidth when no congestion
occurs on the network. If the burst send size is set to a too small value, the
network bandwidth decreases.
n Peak receive bandwidth (Mbit/s): specifies the maximum number of bits per
second to allow across a port when it is receiving a burst of traffic.
The peak receive bandwidth must be greater than or equal to the average
receive bandwidth. When an iNIC is used, the peak receive bandwidth is equal
to the maximum receive bandwidth after the burst of traffic disappears, and in
the idle period, the bandwidth remains around the peak receive bandwidth.
n Burst receive size (Mbits): specifies the maximum number of bytes to allow
in a burst.
– ARP broadcast suppression (Kbit/s): specifies the allowed transmission
bandwidth for Address Resolution Protocol (ARP) broadcast packets. ARP
broadcast suppression limits the number of ARP broadcast packets that can be sent
by VMs, preventing ARP broadcast packet attacks.
– IP broadcast suppression (Kbit/s): specifies the allowed transmission bandwidth
for IP broadcast packets. IP broadcast suppression limits the number of IP broadcast
packets that can be sent by VMs, preventing IP broadcast packet attacks.
– DHCP quarantine: specifies whether to forbid users from enabling the DHCP
server service for a VM. If this parameter is selected, users are not allowed to
enable the DHCP Server service whenever unintentionally or maliciously.
Otherwise, VM IP address allocation is affected.
NOTE
Declaration: This feature is a secure feature. It enhances end user data security.
– IP-MAC binding: binds the IP address and MAC address of the VM that uses the
port group. This function enhances VM network security because it prevents users
from initiating IP address or MAC address spoofing attacks after changing the IP
address or MAC address of the VM NIC. This parameter is valid only when Port
type is set to Access. Do not enable this function if a VM NIC is configured with
multiple IP addresses, because this function may cause communication exceptions
for some IP addresses of this NIC.
NOTE
Declaration: This feature is a secure feature. It enhances end user data security.
– TCP checksum calculation: this enables FusionCompute to automatically
calculate the TCP checksum when VMs in this port group receive packets. Enable
this function only when the checksum accuracy is high priority as it may impact
VM network receive performance.
NOTE
The specified VLAN ID must be contained in the VLAN pool of the DVS that provides the port
group.
7 Click OK.
A dialog box is displayed.
8 Click OK.
The port group attribute modification task is complete. You can view the task progress
on the Task Tracing page.
----End
Prerequisites
Conditions
l You have logged in to FusionCompute.
l The port group to be deleted is not being used by a VM.
Procedure
Step 1 On FusionCompute, click Network Pool.
The Network Pool page is displayed.
Step 2 In the navigation tree on the left, click Network Pool, select the target DVS and then the port
group.
Step 3 Right-click the port group and choose Delete.
A dialog box is displayed.
Step 4 Click OK.
An information dialog box is displayed.
Step 5 Click OK.
The port group is deleted.
----End
5 Network Configuration
Scenarios
On the FusionCompute, configure MAC address segments for VMs. Each VM must be
assigned a unique MAC address. The newly configured MAC address applies only to the
newly created VM.
The FusionCompute provides 100,000 MAC addresses for users, ranging from
28:6E:D4:88:B2:A1 to 28:6E:D4:8A:39:40. In this segment, the first 5000 MAC addresses
(from 28:6E:D4:88:B2:A1 to 28:6E:D4:88:C6:28) are reserved for Virtualization Resource
Management (VRM) VMs.
A maximum of five MAC address segments can be configured. You can change the MAC
address segment configured by default or add new MAC address segments. The MAC address
segments cannot overlap.
Prerequisites
Conditions
You have logged in to the FusionCompute.
Data
The MAC address segments for user VMs have been planned.
NOTE
The MAC segments to be configured cannot contain any of the reserved 5000 MAC addresses.
Procedure
----End
Before you enable IPv6 addresses for VMs, enable the IPv6 forwarding function on the
physical network. The detailed requirements are as follows:
IPv6-based network functions, including gateway, routing, virtual private network (VPN),
access control list (ACL), network address translation (NAT), load balancing, and Dynamic
Host Configuration Protocol v6 (DHCPv6), are all provided by hardware devices, including
switches, firewalls, load balancers, or external DHCPv6 servers.
Configure the required settings based on the configuration requirements in the following three
scenarios. For detailed configuration procedures, see the configuration guide to the supported
hardware device.
l VMs have static IPv6 addresses configured.
– Enable the IPv6 forwarding function on the physical switch and firewall.
– Configure the gateway IPv6 address on the gateway device, such as the aggregation
switch or the firewall.
l VMs are automatically assigned IPv6 addresses using the stateless address
autoconfiguration (SLAAC) function.
– Enable the IPv6 forwarding function on the physical switch and firewall.
– Configure the gateway IPv6 address on the gateway device, such as the aggregation
switch or the firewall.
– On the aggregation switch or firewall, configure the IPv6 RA packet prefix and the
A-Flag and O-Flag bits, and enable the SLAAC IPv6 address assignment function.
Prerequisites
You have logged in to the FusionCompute.
Procedure
A Appendix
Name Specifies the name of the bound uplink port on the Yes band01
host.
This parameter is valid only when Add uplink
and Bind Network Port are selected.
This parameter is mandatory.
Binding Specifies the mode for binding the uplink ports on Yes Active/
Mode the host. Standby
This parameter is valid only when Add uplink
and Bind Network Port are selected.
The following binding modes are available for
common network interface cards (NICs):
l Active-backup: applies to scenarios where
two network ports are to be bound. This mode
provides high reliability. The bandwidth of the
bound port in this mode equals to that of a
member port.
l Round-robin: applies to scenarios where two
or more network ports are to be bound. The
bandwidth of the bound port in this mode is
higher than that of a member port, because the
member ports share workloads in sequence.
This mode may result in data packet disorder
because traffic is evenly sent to each port.
Therefore, MAC address based load
balancing prevails over Polling in load
sharing modes.
l IP address and port-based load balancing:
applies to scenarios where two or more
network ports are to be bound. The bandwidth
of the bound port in this mode is higher than
that of a member port, because the member
ports share workloads based on the source-
destination-port-based load sharing algorithm.
Source-destination-port-based load
balancing algorithm: When the packets
contain IP addresses and ports, the member
ports share loads based on the source and
destination IP addresses, ports, and MAC
addresses. When the packets contain IP
addresses, the member ports share loads based
on the IP addresses and MAC addresses. When
the packets contain only MAC addresses, the
member ports share loads based on the MAC
addresses.
This mode is recommended when the virtual
extensible LAN (VXLAN) function is enabled.
This mode allows network traffic to be evenly
distributed based on the source and destination
port information in the packets.
l MAC address-based load balancing: applies
to scenarios where two or more network ports
Subnet Specifies the network segment for the subnet. Yes 192.168.8
This parameter is mandatory. 0.0
Domain Specifies the domain name for the subnet. Yes www.hua
name The value is a string of 225 characters that wei.com
consist of case-insensitive letters, digits, and
hyphens (-). The value cannot start or end with a
hyphen (-).
This parameter is optional.
Source Port Specifies the port from which the traffic is Yes N/A
transmitted for creating a port mirroring
session. You can select a maximum of four
source ports for a port mirroring session.
This parameter is mandatory.
Table A-5 Parameter description for a source port in a remote port mirroring session
Parameter Description Modifiable Example
Value
Source Port Specifies the port from which the traffic is Yes N/A
transmitted for creating a port mirroring
session. You can select a maximum of four
source ports for a port mirroring session.
This parameter is mandatory.
Table A-6 Parameter description for a destination port in a remote port mirroring session
Parameter Description Modifiable Example
Value
Source Port You can enter a maximum of four VLANs Yes N/A
VLAN ID for a port mirroring session.
This parameter is mandatory.
destination-port-based
load sharing algorithm.
Source-destination-
port-based load
balancing algorithm:
When the packets
contain IP addresses and
ports, the member ports
share loads based on the
source and destination
IP addresses, ports, and
MAC addresses. When
the packets contain IP
addresses, the member
ports share loads based
on the IP addresses and
MAC addresses. When
the packets contain only
MAC addresses, the
member ports share
loads based on the
MAC addresses.
This mode is
recommended when the
virtual extensible LAN
(VXLAN) function is
enabled. This mode
allows network traffic to
be evenly distributed
based on the source and
destination port
information in the
packets.
l MAC address-based
load balancing: applies
to scenarios where two
or more network ports
are to be bound. The
bandwidth of the bound
port in this mode is
higher than that of a
member port, because
the member ports share
workloads based on the
MAC addresses of the
source and destination
ports.
This mode is
recommended when
most network traffic is
on the layer 2 network.
This mode allows
network traffic to be
evenly distributed based
on the MAC addresses.
l MAC address-based
LACP: This mode is
developed based on the
MAC address based
load balancing mode.
In MAC address-based
LACP mode, the bound
port can automatically
detect faults on the link
layer and trigger a
switchover if a link fails
using the LACP
protocol.
l IP address-based
LACP: applies to
scenarios where two or
more network ports are
to be bound. The
bandwidth of the bound
port in this mode is
higher than that of a
member port, because
the member ports share
workloads based on the
source-destination-IP-
address-based load
sharing algorithm.
When the packets
contain IP addresses,
the member ports share
loads based on the IP
addresses and MAC
addresses. When the
packets contain only
MAC addresses, the
member ports share
loads based on the
MAC addresses. In this
mode, the bound port
can also automatically
This parameter is
mandatory.
Port type Specifies the type of the port to be added to Yes Access
the port group.
Value:
l Access: An access port can be added to
only one VLAN.
l Trunk: A trunk port can be added to
multiple VLANs.
Set the port type to access for a common
VM. If the NIC of a common VM uses a
VLAN tagging device, ensure to set the port
type for the VM to trunk.
This parameter is mandatory.
Outbound Specifies the send traffic on the port group. Yes N/A
Traffic Values:
Shaping
l Average send bandwidth (Mbit/s): 1 to
10000
l Peak send bandwidth (Mbit/s):
Average send bandwidth to 10000
l Burst send size (Mbits): Peak send
bandwidth value to 10000
l Priority: Low, Medium, or High
This parameter is optional.