0% found this document useful (0 votes)

230 views82 pages

FusionCompute V100R005C10 Network Management Guide 01

Uploaded by

Alex

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

230 views82 pages

FusionCompute V100R005C10 Network Management Guide 01

Uploaded by

Alex

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 82

FusionCompute

V100R005C10

Network Management Guide

Issue 01
Date 2015-11-11

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

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.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China

Website: http://e.huawei.com

Issue 01 (2015-11-11) Huawei Proprietary and Confidential i

About This Document

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

Indicates an imminently hazardous situation which, if

not avoided, will result in death or serious injury.
DANGER

Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.
WARNING

Indicates a potentially hazardous situation which, if not

avoided, may result in minor or moderate injury.
CAUTION

Indicates a potentially hazardous situation which, if not

avoided, could result in equipment damage, data loss,
NOTICE
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to
personal injury.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential ii

Symbol Description

NOTE Calls attention to important information, best practices

and tips.
NOTE is used to address information not related to
personal injury, equipment damage, and environment
deterioration.

GUI Image Conventions

The GUI images that may be found in this document are for reference only. See the product
GUI in practice.

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential iii

Contents

About This Document.....................................................................................................................ii

1 Overview of Network Management.......................................................................................... 1
2 Distributed Virtual Switch Management................................................................................. 5
2.1 Creating a DVS...............................................................................................................................................................6
2.2 Querying DVS Information.......................................................................................................................................... 12
2.3 Deleting a DVS.............................................................................................................................................................13
2.4 Adding a VLAN Pool................................................................................................................................................... 13
2.5 Deleting a VLAN Pool................................................................................................................................................. 14
2.6 Adding a Subnet........................................................................................................................................................... 15
2.7 Modifying a Subnet...................................................................................................................................................... 17
2.8 Deleting a Subnet..........................................................................................................................................................19
2.9 Creating a Port Mirroring Session................................................................................................................................ 19
2.10 Modifying a Port Mirroring Session...........................................................................................................................24
2.11 Querying a Port Mirroring Session.............................................................................................................................28
2.12 Deleting a Port Mirroring Session.............................................................................................................................. 28

3 Upstream Link Group Management........................................................................................30

3.1 Adding an Uplink......................................................................................................................................................... 31
3.2 Querying Uplink Information....................................................................................................................................... 35
3.3 Deleting an Uplink........................................................................................................................................................36
3.4 Configuring VTEP Networks....................................................................................................................................... 36

4 Port Group Management............................................................................................................40

4.1 Creating a Port Group...................................................................................................................................................41
4.2 Querying Port Group Information................................................................................................................................ 46
4.3 Modifying Attributes of a Port Group.......................................................................................................................... 47
4.4 Deleting a Port Group...................................................................................................................................................51

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

Issue 01 (2015-11-11) Huawei Proprietary and Confidential iv

A.1.2 VLAN Pool Parameters............................................................................................................................................ 61

A.1.3 Subnet Parameters.................................................................................................................................................... 61
A.1.4 Port Mirroring Session Parameters........................................................................................................................... 63
A.1.5 Uplink Parameters.................................................................................................................................................... 67
A.1.6 VTEP Parameters......................................................................................................................................................73
A.1.7 Port Group Parameters..............................................................................................................................................74

Issue 01 (2015-11-11) Huawei Proprietary and Confidential v

1 Overview of Network Management

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.

Principles of VM Network Access

A virtual NIC of a VM communicates with an external network by connecting to the DVS
through the port group, then by connecting to the physical NIC of a host through the DVS
uplink. These connections are shown in the following figure, as shown in Figure 1-1.

Figure 1-1 Working principles of VM network access

Host 1 Host 2

Port group

DVS
Virtual
resources Uplink

Physical
resources

Physical network

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 1

Table 1-1 describes the concepts in the preceding figure.

Table 1-1 Concepts in VM network access

Network Element Description
(NE)

DVS A DVS is similar to a switch used for communications on the layer

2 network. A DVS links the port group to the VM and connects to
the physical network through the uplink.

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.

Uplink An uplink connects the DVS to the physical network. An uplink is

used for VM upstream data transmission.

FusionCompute Support for IPv6

The system allows service VMs to communicate with each other over IPv6 networks. The
VMs supports both single-stack (IPv6 or IPv4) and dual-stack (IPv4 and IPv6) networks.

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

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 2

l Dynamic Host Configuration Protocol (DHCP) quarantine

l Broadcast Suppression
l IGMP Snooping
A DVS that uses iNICs or the VXLAN network does not support IPv6 neither.
The system supports only IPv6 gateways, virtual private networks (VPNs), access control lists
(ACLs), and load balancers provided by external physical switches and firewalls. To use IPv6
networks, the external physical devices (including switches, firewalls, and load balancers)
must be upgraded to support both IPv4 and IPv6 stacks.

Resource creation process

Figure 1-2 shows the process for creating a network resource.

Figure 1-2 Creation process

Host and cluster
Storage management Network management
management
Local or raw
device mapping
Create a cluster. What is the FC SAN Yes
storage resource Is a DVS available?
type?

Add hosts to the cluster. IP SAN NAS No

FusionStorage
Create a DVS.
Adding storage resources Configure the FC SAN
Set host clock to the site. initiator.
synchronization.

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 3

Table 1-2 Procedure

Resource Procedure Description

Network 1. Creating a DVS To modify network

resources 2. Adding an Uplink resource configurations,
see the following sections:
3. If the connection mode of a port group is
virtual local area network (VLAN), perform l Modifying a Subnet
operations provided in Adding a VLAN l Modifying Attributes
Pool. of a Port Group
4. If the connection mode of a port group is
subnet, perform operations provided in
Adding a Subnet.
5. If the virtual extensible local area network
(VXLAN) is required on the
FusionManager, perform operations
provided in Configuring VTEP Networks.
6. Creating a Port Group

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 4

2 Distributed Virtual Switch Management

About This Chapter

2.1 Creating a DVS

2.2 Querying DVS Information
2.3 Deleting a DVS
2.4 Adding a VLAN Pool
2.5 Deleting a VLAN Pool
2.6 Adding a Subnet
2.7 Modifying a Subnet
2.8 Deleting a Subnet
2.9 Creating a Port Mirroring Session
2.10 Modifying a Port Mirroring Session
2.11 Querying a Port Mirroring Session
2.12 Deleting a Port Mirroring Session

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 5

2.1 Creating a DVS

Scenarios
the FusionCompute, create a distributed virtual switch (DVS) to provide network resources
for VMs.
A DVS functions as a physical switch that connects to hosts. In the downstream direction, the
DVS connects to VMs through virtual ports. In the upstream direction, it connects to network
interface cards (NICs) on hosts that provide the VM resources. Therefore, the host network
can communicate with the VM network. In addition, a DVS allows the network
configurations of VMs to retain unchanged when the VMs are migrated across hosts.

Prerequisites
Conditions
l You have logged in to FusionCompute.
l The host has been added to a cluster.

Procedure

1 On FusionCompute, click Network Pool.

The Network Pool page is displayed.
2 Click Create DVS.
The Create DVS page is displayed, as shown in Figure 2-1.

Figure 2-1 Create DVS

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 6

3 Set Name, Description, DVS type, and IGMP Snooping.

The value of DVS type can be:
– Standard: The host physical NIC that associates with the uplink is a common NIC.
– VMDq-enabled: The host physical NIC that associates with the uplink is an
intelligent NIC (iNIC).
– SR-IOV-enabled: The host physical NIC that associates with the uplink is a SR-
IOV-enabled NIC.
NOTE
Pay attention to the following restrictions when using the SR-IOV-enabled NICs:
n SR-IOV can be enabled for Intel 82599, MZ510, and MZ512 NICs. If SR-IOV is
enabled, a network port of the Intel 82599 NIC supports a maximum of 63 virtual
network ports and a network port of the MZ510 or MZ512 NIC supports a maximum of
28 virtual network ports.
n To create port groups on the SR-IOV-enabled DVS, the port type can only be set to
Access.
n All network ports on the MZ510 or MZ512 NICs can either use the SR-IOV-enabled or
Standard mode.
n If a VM uses the SR-IOV-enabled NICs, the following functions become unavailable to
the VM: VM hibernation, VM waking up, VM live migration, VM migration as a whole,
memory snapshot, consistency snapshot, memory hot add, NIC hot add and delete,
VXLAN, security group, port mirroring, IP-MAC address binding, and ACL.
n If SR-IOV is enabled for NICs of a host, memory overcommitment becomes unavailable
to the host.
n If the SR-IOV-enabled NICs are used, the VMs can run only the Windows 7 64–bit
operating system.
– IGMP Snooping (Internet Group Management Protocol Snooping): It is an
advanced function for switches. It allows a switch to listen to IGMP network traffic
to control the flow of multicast packets from the switch ports, managing and
controlling multicast packet forwarding.
NOTE

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 7

A DVS without any uplinks cannot be used to create VMs.

8 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.
– If yes, go to 9.
– If no, go to 15.
9 Locate the row containing the target host and click Bind Network Port.
The Bind Network Port page is displayed.
10 In the Network Port list, select the physical network ports to be bound.
11

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 8

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.
– 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.
– 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.
– 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 detect faults on the link layer and trigger a switchover if a link fails
using the LACP protocol.
This mode is recommended when most network traffic goes across layer 2 and layer
3 networks.
The following binding modes are available for intelligent network interface cards
(iNICs):
– 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.
– Source 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 address of the source port.
– Destination 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 address of the destination port.
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.
– Source 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

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 9

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

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 10

Figure 2-2 Add Uplink

20 Check whether Add VLAN pool is selected.

– If yes, go to 21.
– If no, go to 25.
21 Click Next.
The Add VLAN Pool page is displayed.
22 Click Add.
A dialog box is displayed, as shown in Figure 2-3.

Figure 2-3 Add VLAN Pool

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 11

The DVS creation task is complete.

Follow-up Procedure
Add a host uplink on the DVS. For details, see Adding an Uplink.
Add a VLAN pool or subnet on the DVS. For details, see Adding a VLAN Pool and Adding
a Subnet.

----End

2.2 Querying DVS Information

Scenarios
On FusionCompute, query the information about a distributed virtual switch (DVS).

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.

Figure 2-4 DVS information

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.

Determine whether to query the detailed information about a DVS.

– If yes, go to 3.
– If no, no further action is required.
Query the detailed information about a DVS.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 12

3 Click the name of the target DVS in the Name column.

The Getting Started page is displayed.
4 View the corresponding information about the DVS by clicking the Summary,
Configuration, VM, Host, Port, VLAN Pool, VXLAN Pool, or Port Group tab.
NOTE
The Configuration tab displays information about the IGMP Snooping function and whether this
function is enabled. This tab is displayed only when the DVS type is Standard.

----End

2.3 Deleting a DVS

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

2.4 Adding a VLAN Pool

Scenarios
On FusionCompute, add a virtual local area network (VLAN) pool on a distributed virtual
switch (DVS) based on the data plan to provide VLAN resources for port groups.

Prerequisites
Conditions

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 13

l A DVS has been created.

l You have logged in to FusionCompute.

Procedure

1 On FusionCompute, click Network Pool.

The Network Pool page is displayed.
2 In the navigation tree on the left, expand Network Pool and select the DVS.
The Getting Started page is displayed.
3 Click Add VLAN Pool on the VLAN Pool page.
A dialog box is displayed, as shown in Figure 2-5.

Figure 2-5 Add VLAN Pool

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

2.5 Deleting a VLAN Pool

Scenarios
On FusionCompute, delete an unwanted virtual local area network (VLAN) pool from a
distributed virtual switch (DVS).
After a VLAN pool is deleted, all the VLANs in the pool will be deleted.

Prerequisites
Conditions

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 14

l You have logged in to FusionCompute.

l The VLANs in the VLAN pool to be deleted are not used by 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, 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.

Figure 2-6 Deleting a VLAN pool

Step 4 Set the start VLAN ID and the end VLAN ID of the VLAN pool to be deleted.

Step 5 Click OK.

An information dialog box is displayed.
Step 6 Click OK.
The VLAN pool is deleted from the DVS.

----End

2.6 Adding a Subnet

Scenarios
On FusionCompute, add a subnet with a specified IP address pool. If the connection mode of
a port group is set to subnet, the VRM node automatically assigns IP addresses in the
specified IP address pool to VMs that use this port group.

Prerequisites
Conditions
You have logged in to FusionCompute.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 15

You have configured the DHCP relay on the switch. For details, see Example of Configuring
Switch.

Procedure

1 On FusionCompute, click Network Pool.

The Network Pool page is displayed.
2 Click Add Subnet.
The Add Subnet page is displayed, as shown in Figure 2-7.

Figure 2-7 Add Subnet

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 (-).

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 16

– Preferred DNS server/Alternate DNS server: specifies the IP addresses of the

active and standby DNS server.
– Preferred WINS server/Alternate WINS server: specifies the IP addresses of the
active and standby WINS server.
– VLAN ID: specifies the ID of the VLAN with which the subnet is associated.
4 Click OK.
An information dialog box is displayed.
5 Click OK.
The subnet is added.
Follow-up Procedure
Create port groups. For details, see Creating a Port Group.
----End

2.7 Modifying a Subnet

Scenarios
On FusionCompute, modify the attributes of a subnet. Then the system assigns IP addresses
for VMs based on the new subnet configurations.

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 3 Click Modify.

An information dialog box is displayed.
Step 4 Click OK.
The Modify Subnet page is displayed, as shown in Figure 2-8.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 17

Figure 2-8 Modify 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.

Step 6 Click OK.

An information dialog box is displayed.

Step 7 Click OK.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 18

The subnet is modified.

----End

2.8 Deleting a Subnet

Scenarios
On FusionCompute, delete an unwanted subnet. After the subnet is deleted, IP addresses in
the subnet cannot be assigned to VMs.

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.

Step 3 Click Delete.

A dialog box is displayed.
Step 4 Click OK.
An information dialog box is displayed.
Step 5 Click OK.
The subnet is deleted.

----End

2.9 Creating a Port Mirroring Session

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 19

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.

A distributed virtual switch (DVS) allows a maximum of 64 port mirroring sessions to be

created and eight port mirroring sessions to be enabled. You can create three types of port
mirroring sessions: distributed port mirroring session, remote source port mirroring session,
and remote destination port mirroring session.
l If the source and destination port mirroring VMs are on the same host, use the distributed
port mirroring session. VMs providing the source and destination ports must run on the
same host. If the VMs are migrated to different hosts, the configured port mirroring
function becomes invalid.
l If the source and destination port mirroring VMs are on different hosts, use the remote
source port mirroring session or remote destination port mirroring session. The mirroring
data is broadcasted on a dedicated virtual local area network (VLAN). VMs providing
the source and destination ports must run on different hosts. If the VMs are migrated to
the same host, the configured port mirroring function becomes invalid.

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 20

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.

Figure 2-9 Basic Information

5 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 Distributed port mirroring.
– 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.
– 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
6 Click Next.
The Select Source Port page is displayed.
7 Click Add.
The Select Port dialog box is displayed.
8 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.
9 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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 21

– 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

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 22

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 23

– 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

2.10 Modifying a Port Mirroring Session

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 24

1 Select Network Pool.

The Network Pool page is displayed.
2 In the navigation tree on the left, expand Network Pool and select the DVS.
The Getting Started page is displayed.
3 Choose Port > Port Mirroring.
All the port mirroring sessions of the distributed virtual switch (DVS) are displayed.
4 Locate the row that contains the port mirroring session to be modified, click Modify.
The Basic Information page is displayed.
5 Modify 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.
– 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
6 Click Next.
The Select Source Port page is displayed.
7 Click Add.
The Select Destination Port dialog box is displayed.
8 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.
9 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.
10 Click Next.
The Select Destination Port page is displayed.
11 Click Add.
The Select Destination 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 Modify.
A dialog box is displayed.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 25

The distributed port mirroring session parameters are modified.

15 Click OK.
The distributed port mirroring session is successfully modified.
Modify parameters of 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 Choose Port > Port Mirroring.
All the port mirroring sessions of the DVS are displayed.
19 Locate the row that contains the port mirroring session, click Modify.
The Basic Information page is displayed.
20 Enter the following information about the port mirroring session:
– Name
– Status: specifies the start status of the port mirroring session.
– 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
21 Click Next.
The Select Source Port page is displayed.
22 Click Add.
The Select Port dialog box is displayed.
23 Select source ports and click OK.
Source ports are identified based on MAC addresses. You can select a maximum of four
source ports for a port mirroring session.
24 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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 26

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 27

42 Click OK.
The remote destination port mirroring session is successfully created.
----End

2.11 Querying a Port Mirroring Session

Scenarios
On FusionCompute, query and view information about a port mirroring session.

Prerequisites
Conditions
You have logged in to FusionCompute.

Procedure

1 On FusionCompute, click Network Pool.

The Network Pool page is displayed.
2 In the navigation tree on the left, expand Network Pool and select the DVS.
The Getting Started page is displayed.
3 Choose Port > Port Mirroring.
All the port mirroring sessions of the DVS are displayed.
4 Click the name of the port mirroring session to be queried.
Information about the port mirroring session is displayed at the lower part.

Figure 2-10 Basic Information

5 Click the Source ports or Destination ports tab to view the source ports or destination
ports in the port mirroring session.
----End

2.12 Deleting a Port Mirroring Session

Scenarios
On FusionCompute, delete a port mirroring session.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 28

Prerequisites
Conditions
You have logged in to FusionCompute.

Procedure

1 On FusionCompute, click Network Pool.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 29

3 Upstream Link Group Management

About This Chapter

3.1 Adding an Uplink

3.2 Querying Uplink Information
3.3 Deleting an Uplink
3.4 Configuring VTEP Networks

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 30

3.1 Adding an Uplink

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 3 Click Add Uplink.

The Add Uplink page is displayed, as shown in Figure 3-1.

Figure 3-1 Add Uplink

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 31

Figure 3-2 Bind Network Port

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 32

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 detect faults on the link
layer and trigger a switchover if a link fails using the LACP protocol.
This mode is recommended when most network traffic goes across layer 2 and layer 3
networks.
The following binding modes are available for intelligent network interface cards (iNICs):
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 Source 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 address of the source port.
l Destination 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 address of the destination port.
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 Source 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 source port.
l 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

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 33

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 34

The uplink is added to the DVS.

----End

3.2 Querying Uplink Information

Scenarios
On FusionCompute, query the information about an uplink.

Prerequisites
Conditions
You have logged in to FusionCompute.
Data
You have obtained the name of the uplink to be queried.

Procedure

1 Perform the following operations based on the information to be queried:

– To query the general information about the uplink, go to 2.
– To query the information about network ports on the uplink, go to 5.
– To query the information about the host that uses the uplink, go to 8.
To query the general information about the uplink.
2 On FusionCompute, click Network Pool.
The Network Pool page is displayed.
3 In the navigation tree on the left, expand Network Pool, select the distributed virtual
switch (DVS), and click Uplink Group.
The Getting Started page is displayed.
4 Query the general information about the uplink on the Summary page.
No further action is required.
To query the information about network ports on the uplink.
5 On FusionCompute, click Network Pool.
The Network Pool page is displayed.
6 In the navigation tree on the left, expand Network Pool, select the DVS, and click
Uplink Group.
The Getting Started page is displayed.
7 Query the information about network ports on the uplink on the Network Port page.
No further action is required.
Query the information about the host that uses the uplink.
8 On FusionCompute, click Network Pool.
The Network Pool page is displayed.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 35

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

3.3 Deleting an Uplink

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 3 Click Network Port.

All the available uplinks on the DVS are displayed.

Step 4 Locate the row that contains the uplink to be deleted, click Remove from DVS.
A confirmation dialog box is displayed.

Step 5 Click OK.

An information dialog box is displayed, indicating that the uplink is deleted.

Step 6 Click OK.

The uplink deletion task is complete.

----End

3.4 Configuring VTEP Networks

Scenarios
On FusionCompute, configure VXLAN Tunnel End Point (VTEP) networks for uplinks
created on a Distributed Virtual Switch (DVS) so that the Virtual Extensible LAN (VXLAN)
can be used.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 36

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.

1 Determine method of configuring VTEP networks.

– To configure VTEP networks in batches, go to 2.
This method is recommended when the system has a large number of hosts.
– To configure the VTEP network one by one, go to 14.
This method is recommended when the system has a small number of hosts.
Configure VTEP networks in batches.

2 On FusionCompute, click Computing Pool.

The Computing Pool page is displayed.
3 In the navigation tree on the left, select the site.
4 Click Operation and select Add VXLAN VTEP in Batches.
The Add PLAN VTEP in Batches page is displayed.
5 Click Download Template.
The page for downloading templates is displayed.
6 Save the template on the local PC.
The default name of the template for configuring VTEP networks in batches is
VTEPHHMMSSXXX.xls.
7 Open the template file, click the Host_VTEP sheet, locate the row that contains the
information about host to be configured based on the host IP address and port number,
and copy the information to the Config sheet.
The information to be copied includes Host IP Address, Host ID, Network Port Name,
and Network Port ID.
8 Set VTEP information in the Config sheet.
– VTEP IP Address: specifies the IP address planned for the VTEP network.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 37

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

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 38

– 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.
----End

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 39

4 Port Group Management

About This Chapter

4.1 Creating a Port Group

4.2 Querying Port Group Information
4.3 Modifying Attributes of a Port Group
4.4 Deleting a Port Group

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 40

4.1 Creating a Port Group

Scenarios
On FusionCompute, create a port group on a distributed virtual switch (DVS) to provide
network resources for VMs.
A port group is also considered a mechanism for setting some policies for managing the
network connected to the port group. A DVS can contain multiple port groups. If VMs
connect to the same port group of a DVS through their network interface cards (NICs), these
VMs are working on the same network even if they are carried on different physical servers.
The VM NICs connected to the same port group share the same network attributes, such as
virtual local area network (VLAN), subnet, quality of service (QoS) requirements, and
security attributes. This function improves network security, network segmentation, running,
availability, and traffic management performance of the system.
Advanced settings of a port group, such as 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.

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 41

Figure 4-1 Basic Information

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 42

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 43

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 44

l If yes, go to Step 15.

l If no, go to Step 12.

Step 12 Click Add Subnet.

A dialog box is displayed, as shown in Figure 4-2.

Figure 4-2 Add Subnet

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 14 Click OK.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 45

Step 15 In the subnet list on the left, select the subnet configured for the port group.

Step 16 Click Next.

The Confirm page is displayed.
Step 17 Confirm the information and click Create.
The system displays a message indicating that the port group is created.
Step 18 Click OK.
The port group creation task is complete.

----End

4.2 Querying Port Group Information

Scenarios
On FusionCompute, query the information about a port group.

Prerequisites
Conditions
You have logged in to FusionCompute.
Data
You have obtained the name of the port group to be queried.

Procedure

1 Perform the following operations based on the information to be queried:

– To query the general information about the port group, go to 2.
– To query the information about VMs connected to the port group, go to 5.
– To query the information about ports in the port group, go to 8.
Query the general information about the port group.
2 On FusionCompute, click Network Pool.
The Network Pool page is displayed.
3 In the navigation tree on the left, click Network Pool, select the target DVS and then the
port group.
The Getting Started page is displayed.
4 Query the general information about the port group on the Summary page.
No further action is required.
Query the information about VMs connected to the port group.
5 On FusionCompute, click Network Pool.
The Network Pool page is displayed.
6 In the navigation tree on the left, click Network Pool, select the target DVS and then the
port group.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 46

The Getting Started page is displayed.

7 Query the information about VMs connected to the port group on the VM page.
No further action is required.
Query the information about ports in the port group.
8 On FusionCompute, click Network Pool.
The Network Pool page is displayed.
9 In the navigation tree on the left, click Network Pool, select the target DVS and then the
port group.
The Getting Started page is displayed.
10 Query the information about ports in the port group on the Port page.
No further action is required.

----End

4.3 Modifying Attributes of a Port Group

Scenarios
On FusionCompute, query and modify the attributes of a port group created on a distributed
virtual switch (DVS). If the Connection mode of the port group is set to VLAN, the
following attributes of the port group can be modified: Port Type, VLAN ID, Outbound
Traffic Shaping, Inbound Traffic Shaping, ARP broadcast suppression (Kbps), IP
broadcast suppression (Kbps), DHCP quarantine, and IP-MAC binding. If the
Connection mode of the port group is set to Subnet, the VLAN ID of the port group cannot
be modified.

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.

Impact on the System

l After the VLAN is changed, the system reassigns IP addresses for the VMs based on the
new VLAN if the VMs connected to the port group obtain IP addresses automatically.
l Before changing the VLAN, ensure that the IP addresses of the VMs are contained in the
new VLAN if the VMs connected to the port group use manually-configured IP
addresses, Otherwise, VM may fail to communicate with the DVS.

Prerequisites
Conditions

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 47

l You have logged in to FusionCompute.

l The IP addresses of the VMs are contained in the new VLAN if the VMs connected to
the port group use manually-configured IP addresses.

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.

Figure 4-3 Network Settings

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 48

6 Modify the following port group attributes as required:

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 49

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 50

The port group attribute modification task is complete. You can view the task progress
on the Task Tracing page.
----End

4.4 Deleting a Port Group

Scenarios
On FusionCompute, delete a port group from a distributed virtual switch (DVS).

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

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 51

5 Network Configuration

About This Chapter

5.1 Configuring the MAC Address Segment

5.2 Enabling or Disabling IPv6 Forwarding

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 52

5.1 Configuring the MAC Address Segment

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

1 On the FusionCompute, choose Network Pool > MAC Address Pool.

The MAC Address Pool page is displayed.
2 Click Add.
A dialog box is displayed, as shown in Figure 5-1.

Figure 5-1 Add MAC Address

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 53

3 Specify the start and end MAC addresses.

4 Click OK.
An information dialog box is displayed.
5 Click OK.
The MAC address segment is configured.
6 Check whether to add other MAC address segments.
– If yes, go to 7.
– If no, no further action is required.
7 Click Add.
A dialog box is displayed.
8 Repeat 3 to 5 to add MAC address segments.
To modify or delete an MAC address segment, locate the row that contains the target
MAC address segment, click Modify or Delete.

----End

5.2 Enabling or Disabling IPv6 Forwarding

Scenarios
On FusionCompute, enable or disable the IPv6 forwarding function, which enables or disables
IPv6 addresses for VMs, and enables or disables the IPv6 forwarding function for distributed
virtual switches (DVSs). This function is disabled by default.

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 54

l VMs are assigned IPv6 addresses using DHCPv6.

– 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 A-Flag and O-
Flag bits and enable the DHCPv6 IPv6 address assignment function.
– (Optional) Configure the DHCPv6 relay function on the aggregation switch or
firewall.

Impact on the System

Disabling IPv6 forwarding interrupts communications for VMs that use IPv6 in the system.

Prerequisites
You have logged in to the FusionCompute.

Procedure

1 On FusionCompute, choose Network Pool > IPv6 forwarding settings.

The IPv6 forwarding settings page is displayed.
2 Enable or disable the IPv6 function for all hosts.
– If Enable is selected, go to 4.
– If Disable is selected, go to 4.
3 Click OK.
A confirmation dialog box is displayed.
4 Click OK.
An information dialog box is displayed.
5 Click OK.
The task is complete.
----End

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 55

A Appendix

A.1 Parameter Reference

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 56

A.1 Parameter Reference

A.1.1 DVS Parameters

Table A-1 Parameter description
Paramete Description Modifiabl Exampl
r e e

Name Specifies the name of the distributed virtual Yes LANswi

switch (DVS). tch01
This parameter is mandatory.

Switching Specifies the data exchanging mode of the DVS. No Commo

type Value: n mode
l Standard: The host physical NIC that
associates with the uplink is a common NIC.
l VMDq-enabled: The host physical NIC that
associates the uplink is an intellectual NIC
(iNIC).
l SR-IOV-enabled: The host physical NIC that
associates with the uplink is a SR-IOV-enabled
NIC.
This parameter is mandatory.

Descriptio Provides supplementary information about the Yes N/A

n DVS.
This parameter is optional.

Add uplink Specifies whether to add an upstream link on the No N/A

DVS.
A DVS with no upstream link added cannot be
used to create VMs.
This parameter is optional.

Add Specifies whether to add a virtual local area No N/A

VLAN network (VLAN) pool.
pool This parameter is optional.

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 57

Paramete Description Modifiabl Exampl

r e e

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

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 58

Paramete Description Modifiabl Exampl

r e e

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
detect faults on the link layer and trigger a
switchover if a link fails using the LACP
protocol.
This mode is recommended when most
network traffic goes across layer 2 and layer 3
networks.
The following binding modes are available for
intelligent network interface cards (iNICs):
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 Source 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

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 59

Paramete Description Modifiabl Exampl

r e e

ports share workloads based on the MAC

address of the source port.
l Destination 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 address of the destination port.
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 Source 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 source port.
l 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.
This parameter is mandatory.

IP Specifies the IP address to be used by virtual Yes 192.168.

tunnel end point (VTEP). 0.23
This parameter is mandatory.

Subnet Specifies the subnet mask of the VTEP. Yes 255.255.

mask This parameter is mandatory. 255.0

Gateway Specifies the gateway address of the VTEP. Yes 192.168.

This parameter is mandatory. 0.1

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 60

Paramete Description Modifiabl Exampl

r e e

Outer Specifies the VLAN to be used by the VTEP. The Yes 2

VLAN VLAN is different from the VLANs used by the
management, storage, and service planes.
This parameter is mandatory.

Start Specifies the start VLAN ID of the VLAN pool. No 2

VLAN ID This parameter is valid only when Add VLAN
pool is selected.
Value range: 1 to 4094
This parameter is mandatory.

End Specifies the end VLAN ID of the VLAN pool. No 100

VLAN ID This parameter is valid only when Add VLAN
pool is selected.
Value range: 1 to 4094
This parameter is mandatory.

A.1.2 VLAN Pool Parameters

Table A-2 Parameter description
Parameter Description Modifiable Example

Start Specifies the start VLAN ID No 2

VLAN ID of the VLAN pool.
Value range: 1 to 4094
This parameter is mandatory.

End VLAN Specifies the end VLAN ID No 100

ID of the VLAN pool.
Value range: 1 to 4094
This parameter is mandatory.

A.1.3 Subnet Parameters

Table A-3 Parameter description
Paramete Description Modifiable Example
r Value

Name Specifies the name of the subnet. Yes subnet01

This parameter is mandatory.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 61

Paramete Description Modifiable Example

r Value

Descriptio Provides supplementary information about the Yes N/A

n subnet.
This parameter is optional.

Subnet Specifies the network segment for the subnet. Yes 192.168.8
This parameter is mandatory. 0.0

Subnet Specifies the subnet mask. Yes 255.255.2

mask This parameter is mandatory. 55.0

Gateway Specifies the gateway address of the subnet. Yes 192.168.8

This parameter is optional. 0.1

Reserved Specifies the reserved IP address segment in Yes 192.168.8

IP segment which the IP addresses are not allocated to the 0.1 to
VMs that use this port group. The system 192.168.8
supports a maximum of three reserved IP 0.10
address segments.
This parameter is optional.

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.

Preferred Specifies the IP address of the active or standby Yes 192.168.6

DNS domain name server (DNS). 0.100/192.
server/ This parameter is optional. 168.60.10
Alternate 1
DNS
server

Preferred Specifies the IP address of the active or standby Yes 192.168.6

WINS Windows Internet Name Service (WINS) server. 0.110/192.
server/ This parameter is optional. 168.60.11
Alternate 1
WINS
server

VLAN ID Specifies the ID of the virtual local area network Yes 98

(VLAN) with which the subnet is associated.
This parameter is mandatory.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 62

A.1.4 Port Mirroring Session Parameters

Table A-4 Parameter description for a distributed port mirroring session
Parameter Description Modifiable Example
Value

Name Specifies the name of the port mirroring Yes Mirr01

session.
This parameter is mandatory.

Status Specifies the start status of the port Yes N/A

mirroring session.
This parameter is mandatory.

Mirroring Specifies the type of the port mirroring No N/A

Session session.
Type This parameter is mandatory.

Normal I/O Specifies whether normal traffic is allowed Yes N/A

on to be switched to destination ports.
destination If this parameter is set to Not allowed, only
ports traffic for creating a port mirroring session
is allowed to pass through destination ports.
This parameter is mandatory.

Mirrored Specifies the length of the mirrored Yes 60

packet packets. This parameter puts a limit on the
length size of mirrored packets. If this parameter is
(Bytes) selected, all mirrored packets are truncated
to the specified length.
Value range: an integer ranging from 60 to
1514.
This parameter is mandatory.

Description Provides supplementary information about Yes N/A

the port mirroring session.
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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 63

Parameter Description Modifiable Example

Value

Traffic Specifies the direction of traffic transmitted Yes Ingress/

Direction through the source port. Egress
Values:
l Ingress: indicates that the traffic
transmitted through the source port to
the distributed virtual switch (DVS).
l Egress: indicates that the traffic
transmitted through the source port from
the DVS.
l Ingress/Egress: indicates that the traffic
transmitted through the source port to
and from the DVS.
This parameter is optional.

Destination Specifies the port to which the traffic is Yes N/A

Port transmitted for creating a port mirroring
session. You can select a maximum of four
destination 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

Name Specifies the name of the port mirroring Yes Mirr01

session.
This parameter is mandatory.

Status Specifies the start status of the port Yes N/A

mirroring session.
This parameter is mandatory.

Mirroring Specifies the type of the port mirroring No N/A

Session session.
Type This parameter is mandatory.

Encapsulati Specifies the ID of the dedicated virtual Yes N/A

on VLAN local area network (VLAN) for the
ID mirroring data.
This parameter is mandatory.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 64

Parameter Description Modifiable Example

Value

Preserve Specifies whether to reserve the original Yes N/A

original VLAN. If this parameter is select, the
VLAN 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.
This parameter is optional.

Mirrored Specifies the length of the mirrored packets. Yes 60

packet This parameter puts a limit on the size of
length mirrored packets. If this parameter is
(Bytes) selected, all mirrored packets are truncated
to the specified length.
Value range: an integer ranging from 60 to
1514.
This parameter is mandatory.

Description Provides supplementary information about Yes N/A

the port mirroring session.
This parameter is optional.

Traffic Specifies the direction of traffic transmitted Yes Ingress/

Direction through the source port. Egress
Values:
l Ingress: indicates that the traffic
transmitted through the source port to
the DVS.
l Egress: indicates that the traffic
transmitted through the source port from
the DVS.
l Ingress/Egress: indicates that the traffic
transmitted through the source port to
and from the DVS.
This parameter is optional.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 65

Table A-6 Parameter description for a destination port in a remote port mirroring session
Parameter Description Modifiable Example
Value

Name Specifies the name of the port mirroring Yes Mirr01

session.
This parameter is mandatory.

Status Specifies the start status of the port Yes N/A

mirroring session.
This parameter is mandatory.

Mirroring Specifies the type of the port mirroring No N/A

Session session.
Type This parameter is mandatory.

Normal I/O Specifies whether normal traffic is allowed Yes N/A

Description Provides supplementary information about Yes N/A

the port mirroring session.
This parameter is optional.

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 Specifies the port to which the traffic is Yes N/A

Port transmitted for creating a port mirroring
session. You can select a maximum of four
destination ports for a port mirroring
session.
This parameter is mandatory.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 66

A.1.5 Uplink Parameters

Table A-7 Parameter description
Parameter Description Modifiable Example
Value

Bound Name Specifies the name of the Yes band01

port bound uplink port on the
parameter host.
s This parameter is
mandatory.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 67

Parameter Description Modifiable Example

Value

Binding Specifies the mode for Yes Active/

Mode binding the uplink ports on Standby
the host.
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-

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 68

Parameter Description Modifiable Example

Value

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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 69

Parameter Description Modifiable Example

Value

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

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 70

Parameter Description Modifiable Example

Value

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 71

Parameter Description Modifiable Example

Value

workloads based on the

MAC address of the
destination port.
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 Source 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 source port.
l 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.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 72

Parameter Description Modifiable Example

Value

This parameter is
mandatory.

Virtual IP Specifies the IP address to Yes 192.168.0.23

tunnel end be used by the VTEP.
point This parameter is
(VTEP) mandatory.
parameter
s Subnet Specifies the subnet mask Yes 255.255.255.0
mask of the VTEP.
This parameter is
mandatory.

Gateway Specifies the gateway Yes 192.168.0.1

address of the VTEP.
This parameter is
mandatory.

Outer Specifies the VLAN to be Yes 2

VLAN used by the VTEP. The
VLAN is different from the
VLANs used by the
management, storage, and
service planes.
This parameter is
mandatory.

LLDP Specifies the LLDP Yes N/A

service. If this service is
enabled, the host topology
can be reported to the
switch using the LLDP
protocol.
This parameter is optional.

A.1.6 VTEP Parameters

Table A-8 Parameter description
Parameter Description Modifiable Example
Value

IP Specifies the IP address to be Yes 192.168.0.2

used by virtual tunnel end 3
point (VTEP).
This parameter is mandatory.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 73

Parameter Description Modifiable Example

Value

Subnet Specifies the subnet mask of Yes 255.255.25

mask the VTEP. 5.0
This parameter is mandatory.

Gateway Specifies the gateway address Yes 192.168.0.1

of the VTEP.
This parameter is mandatory.

Outer Specifies the VLAN to be Yes 2

virtual used by the VTEP. The
local area VLAN is different from the
network VLANs used by the
(VLAN) management, storage, and
service planes.
This parameter is mandatory.

LLDP Specifies the LLDP service. Yes N/A

If this service is enabled, the
host topology can be reported
to the switch using the LLDP
protocol.
This parameter is optional.

A.1.7 Port Group Parameters

Table A-9 Parameter description
Paramet Description Modifiabl Example
er e Value

Name Specifies the name of the port group. Yes portgroup01

This parameter is mandatory.

Descripti Provides supplementary information about Yes Port group for

on the port group. the storage plane
This parameter is optional.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 74

Paramet Description Modifiabl Example

er e Value

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.

Inbound Specifies the receive traffic on the port Yes N/A

Traffic group.
Shaping Values:
l Average receive bandwidth (Mbit/s): 1
to 10000
l Peak receive bandwidth (Mbit/s):
Average receive bandwidth to 10000
l Burst receive size (Mbits): Peak receive
bandwidth value to 10000
This parameter is optional.

ARP Specifies the allowed transmission Yes 2

broadcast bandwidth for Address Resolution Protocol
suppressi (ARP) broadcast packets. ARP broadcast
on suppression limits the number of ARP
(Kbit/s) broadcast packets that can be sent by VMs,
preventing ARP broadcast packet attacks.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 75

Paramet Description Modifiabl Example

er e Value

IP Specifies the allowed transmission Yes 10

broadcast bandwidth for IP broadcast packets. IP
suppressi broadcast suppression limits the number of
on IP broadcast packets that can be sent by
(Kbit/s) VMs, preventing IP broadcast packet
attacks.

DHCP Specifies whether to forbid users from Yes N/A

quarantin enabling the DHCP server service for a VM.
e 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.
This parameter is optional.

IP-MAC Binds the IP address and MAC address of Yes N/A

binding the VM using 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.
This parameter is optional.

Connecti Specifies the mode in which the port group No VLAN

on mode connects to the network.
Value:
l Subnet: In this mode, the system
automatically assigns IP addresses in the
IP address pool configured for the subnet
to VM NICs that communicate with this
port group.
l VLAN: In this mode, the system does
not assign IP addresses to VM NICs that
communicate with this port group. Users
need to configure IP addresses for the
NICs after creating the port group.
This parameter is valid only when Port type
is set to Access.
This parameter is mandatory.

Issue 01 (2015-11-11) Huawei Proprietary and Confidential 76

NE40E-F V800R011C10 Configuration Guide - Interface and Data Link 02
No ratings yet
NE40E-F V800R011C10 Configuration Guide - Interface and Data Link 02
54 pages
HCIA Cloud Computing V4.0 Lab Guide PDF
No ratings yet
HCIA Cloud Computing V4.0 Lab Guide PDF
133 pages
A10 Thunder Vlan Bridging + VRRP
No ratings yet
A10 Thunder Vlan Bridging + VRRP
328 pages
NetEngine 8000 X V800R012C00SPC300 Configuration Guide - System Monitor 04
No ratings yet
NetEngine 8000 X V800R012C00SPC300 Configuration Guide - System Monitor 04
513 pages
ZXHN F670L V9.0 Datasheet
50% (2)
ZXHN F670L V9.0 Datasheet
2 pages
A10 4.1.4-P1 Net PDF
No ratings yet
A10 4.1.4-P1 Net PDF
358 pages
A Questionnaire For Examining The Impact
78% (18)
A Questionnaire For Examining The Impact
12 pages
16 FusionSphare OpenStack OM Services Operation
No ratings yet
16 FusionSphare OpenStack OM Services Operation
37 pages
Huawei E9000 Server Network Technology White Paper
No ratings yet
Huawei E9000 Server Network Technology White Paper
120 pages
Huawei FusionCube Technical White Paper
0% (1)
Huawei FusionCube Technical White Paper
119 pages
FusionSphere V100R005C00 Quick User Guide 01
No ratings yet
FusionSphere V100R005C00 Quick User Guide 01
64 pages
NCE V100R018C10 Configuration Guide (IP+Optical Services) 01-C PDF
100% (2)
NCE V100R018C10 Configuration Guide (IP+Optical Services) 01-C PDF
140 pages
FusionCompute V100R005C10 Quick Start 01
No ratings yet
FusionCompute V100R005C10 Quick Start 01
48 pages
Edge-Core Switch CLI Reference Guide
No ratings yet
Edge-Core Switch CLI Reference Guide
720 pages
Huawei FM1000A40 V200R003C00 IT Maintenance Guide
No ratings yet
Huawei FM1000A40 V200R003C00 IT Maintenance Guide
179 pages
FusionModule800 Smart Small Data Center V100R001C20 User Manual (NetCol5000-A013)
No ratings yet
FusionModule800 Smart Small Data Center V100R001C20 User Manual (NetCol5000-A013)
629 pages
CL02 FusionCompute Product Introduction
No ratings yet
CL02 FusionCompute Product Introduction
41 pages
Useful FusionCompute V100R005C10 Initial Configuration Guide 01
No ratings yet
Useful FusionCompute V100R005C10 Initial Configuration Guide 01
132 pages
FusionModule800 Smart Small Data Center V100R021C00 User Manual
No ratings yet
FusionModule800 Smart Small Data Center V100R021C00 User Manual
508 pages
FusionCompute V100R005C00 Installation and Configuration PDF
No ratings yet
FusionCompute V100R005C00 Installation and Configuration PDF
39 pages
FusionHub User Manual and Installation Guide PDF
No ratings yet
FusionHub User Manual and Installation Guide PDF
116 pages
Operation Manual 2.1
No ratings yet
Operation Manual 2.1
56 pages
FusionCompute V100R005C10 Storage Management Guide 01
No ratings yet
FusionCompute V100R005C10 Storage Management Guide 01
154 pages
FusionCompute V100R005C10 Host and Cluster Management Guide 01
No ratings yet
FusionCompute V100R005C10 Host and Cluster Management Guide 01
137 pages
FusionCompute V100R005C10 Product Description 01
No ratings yet
FusionCompute V100R005C10 Product Description 01
61 pages
ACOS 4.1.1-P11 Network Configuration Guide: For A10 Thunder Series and AX™ Series 29 May 2019
No ratings yet
ACOS 4.1.1-P11 Network Configuration Guide: For A10 Thunder Series and AX™ Series 29 May 2019
378 pages
FusionSphere6.5.0 Installation and Configuration
No ratings yet
FusionSphere6.5.0 Installation and Configuration
41 pages
NE9000 V800R022C00 Configuration Guide 04 Interface and Data Link
No ratings yet
NE9000 V800R022C00 Configuration Guide 04 Interface and Data Link
122 pages
Mz710 Nic v100r001 User Guide 06
No ratings yet
Mz710 Nic v100r001 User Guide 06
25 pages
FusionCloud Desktop Solution Engineering Installation Preparation Guide For Customer
No ratings yet
FusionCloud Desktop Solution Engineering Installation Preparation Guide For Customer
71 pages
FusionAccess V100R006C00 Release Notes
No ratings yet
FusionAccess V100R006C00 Release Notes
18 pages
Experiment No.10 AIM: Configuring TCP/IP On Windows Operating Systems Theory
No ratings yet
Experiment No.10 AIM: Configuring TCP/IP On Windows Operating Systems Theory
5 pages
Day One: Inside Segment Routing
No ratings yet
Day One: Inside Segment Routing
183 pages
HUAWEI NE40E-F1 Series Universal Service Router Configuration Guide - Interface and Data Link
No ratings yet
HUAWEI NE40E-F1 Series Universal Service Router Configuration Guide - Interface and Data Link
2 pages
IP Traffic Monitoring Configuration: About This Chapter
No ratings yet
IP Traffic Monitoring Configuration: About This Chapter
2 pages
FusionSphere PCS 6.5.1.1 Operation Guide (HCS Xen To KVM) 01
No ratings yet
FusionSphere PCS 6.5.1.1 Operation Guide (HCS Xen To KVM) 01
142 pages
Huawei FusionSphere Virtualization Suite 6.3.1 Product Description
No ratings yet
Huawei FusionSphere Virtualization Suite 6.3.1 Product Description
96 pages
01 Data Communication Network Basis
No ratings yet
01 Data Communication Network Basis
35 pages
ASR9000/XR - BNG Deployment Guide
No ratings yet
ASR9000/XR - BNG Deployment Guide
53 pages
NetEngine 8000 M14, M8 and M4 V800R023C00SPC500 Configuration Guide 04 Interface and Data Link
No ratings yet
NetEngine 8000 M14, M8 and M4 V800R023C00SPC500 Configuration Guide 04 Interface and Data Link
207 pages
FusionServer Pro Rack Server iBMC (V290 To V299) User Guide 27
No ratings yet
FusionServer Pro Rack Server iBMC (V290 To V299) User Guide 27
525 pages
IYC05 FusionCompute Routine Maintenance
No ratings yet
IYC05 FusionCompute Routine Maintenance
36 pages
B Cisco N1KV For KVM Interface Config 5x
No ratings yet
B Cisco N1KV For KVM Interface Config 5x
26 pages
SMCGS10P-Smart MG
No ratings yet
SMCGS10P-Smart MG
288 pages
NetEngine 8000 F1A V800R022C10 Product Description
No ratings yet
NetEngine 8000 F1A V800R022C10 Product Description
21 pages
01-16 Network Management and Monitoring Commands
No ratings yet
01-16 Network Management and Monitoring Commands
671 pages
FusionServer Pro Rack Server IBMC (V250 To V259) User Guide 31
No ratings yet
FusionServer Pro Rack Server IBMC (V250 To V259) User Guide 31
499 pages
List of Materials With Out COE As USA
No ratings yet
List of Materials With Out COE As USA
77 pages
Operations Troubleshooting Guide: Verify and Identify The Issue
100% (1)
Operations Troubleshooting Guide: Verify and Identify The Issue
2 pages
FusionDC1000A40 Prefabricated All-in-One Data Center Quick Guide (2021, Zambia, ZESCO)
No ratings yet
FusionDC1000A40 Prefabricated All-in-One Data Center Quick Guide (2021, Zambia, ZESCO)
30 pages
FusionStorage 8.0.1 Block Storage HyperMetro Feature Guide 05
No ratings yet
FusionStorage 8.0.1 Block Storage HyperMetro Feature Guide 05
176 pages
Ecs4810 12M Cli R05 - 20160929
No ratings yet
Ecs4810 12M Cli R05 - 20160929
893 pages
6.2.1 Packet Tracer - Configure IPv4 and IPv6 Static and Default Routes - ILM
No ratings yet
6.2.1 Packet Tracer - Configure IPv4 and IPv6 Static and Default Routes - ILM
4 pages
100-101 Icnd1
No ratings yet
100-101 Icnd1
18 pages
NE9000 V800R023C00SPC500 Configuration Guide 18 System Monitor
No ratings yet
NE9000 V800R023C00SPC500 Configuration Guide 18 System Monitor
687 pages
NE9000 V800R023C00SPC500 Configuration Guide 12 Application Awareness
No ratings yet
NE9000 V800R023C00SPC500 Configuration Guide 12 Application Awareness
54 pages
FusionServer Pro Rack Server Deployment Guide 06
No ratings yet
FusionServer Pro Rack Server Deployment Guide 06
119 pages
CCNA Lab M4 5.5.1
No ratings yet
CCNA Lab M4 5.5.1
6 pages
Case Study On Computer Networks PDF
No ratings yet
Case Study On Computer Networks PDF
2 pages
FusionStorage 8.0.0 Block Storage HyperMetro Feature Guide 07
No ratings yet
FusionStorage 8.0.0 Block Storage HyperMetro Feature Guide 07
165 pages
Star Network Setup
No ratings yet
Star Network Setup
3 pages
MCQ Question (Latest)
No ratings yet
MCQ Question (Latest)
13 pages
Bras Commands
No ratings yet
Bras Commands
8 pages
IP Addressing: Introductory Material
No ratings yet
IP Addressing: Introductory Material
30 pages
Intro To MPLS Slides
No ratings yet
Intro To MPLS Slides
66 pages
ITN Practice Skills Assessment - Packet Tracer
No ratings yet
ITN Practice Skills Assessment - Packet Tracer
3 pages
Dell Solution For Microsoft Azure Stack HCI Networking Concepts and Implementation Participant Guide
No ratings yet
Dell Solution For Microsoft Azure Stack HCI Networking Concepts and Implementation Participant Guide
84 pages
Chapters 1-2 Advanced Network
No ratings yet
Chapters 1-2 Advanced Network
97 pages
Chapter 1 8.1 L (1-2)
No ratings yet
Chapter 1 8.1 L (1-2)
87 pages
A6V10366162 - BACnet Router For BACnet - IP BACnet - LonTalk BACne - en
No ratings yet
A6V10366162 - BACnet Router For BACnet - IP BACnet - LonTalk BACne - en
10 pages
CloudVPNGuide UsingCloudVPNwithPaloAltoNetworksPA 3020
No ratings yet
CloudVPNGuide UsingCloudVPNwithPaloAltoNetworksPA 3020
28 pages
07 Huawei Virtualization Platform
No ratings yet
07 Huawei Virtualization Platform
29 pages
Week13 Lec1-VLANS
No ratings yet
Week13 Lec1-VLANS
22 pages
Comparison DataSheet of Routing Protocols RIP EIGRP OSPF
No ratings yet
Comparison DataSheet of Routing Protocols RIP EIGRP OSPF
1 page
An Ethernet Hub
No ratings yet
An Ethernet Hub
1 page
08 Huawei Virtualization Platform Management and Usage
No ratings yet
08 Huawei Virtualization Platform Management and Usage
70 pages
Itnet 2 - Routing Vlan Reviewer
No ratings yet
Itnet 2 - Routing Vlan Reviewer
3 pages
FusionAccess V100R005C20SPC102 Upgrade Guide
No ratings yet
FusionAccess V100R005C20SPC102 Upgrade Guide
91 pages
FusionCloud Desktop V100R005C20 Solution Description 03
No ratings yet
FusionCloud Desktop V100R005C20 Solution Description 03
136 pages
A10 Control Admin Guide: March, 2025
No ratings yet
A10 Control Admin Guide: March, 2025
2,099 pages
Diaz Updated Resume
No ratings yet
Diaz Updated Resume
3 pages
07 Lab Guide-Student
No ratings yet
07 Lab Guide-Student
45 pages
Ilovekaylaxx - Profile Page
No ratings yet
Ilovekaylaxx - Profile Page
1 page
Networks and Security Lecture Notes 1
No ratings yet
Networks and Security Lecture Notes 1
131 pages
NetEngine 8000 M14K, M14, M8K, M8, M4, 8000E M14 M8, 8100 M14 M8 V800R022C00SPC600 Configuration Guide 17 System Monitor
No ratings yet
NetEngine 8000 M14K, M14, M8K, M8, M4, 8000E M14 M8, 8100 M14 M8 V800R022C00SPC600 Configuration Guide 17 System Monitor
1,105 pages
Networks 511
No ratings yet
Networks 511
7 pages
Implementing VMware Dynamic Environment Manager: Manage, Administer and Control VMware DEM, Dynamic Desktop, User Policies and Complete Troubleshooting
From Everand
Implementing VMware Dynamic Environment Manager: Manage, Administer and Control VMware DEM, Dynamic Desktop, User Policies and Complete Troubleshooting
Peter von Oven
No ratings yet
IT Survival Guide !!!: Avoid Disaster, Cut Cost, Protect Your Sh*t!
From Everand
IT Survival Guide !!!: Avoid Disaster, Cut Cost, Protect Your Sh*t!
Alp Ertunga Isin
No ratings yet
Computer Networking: Beginners Guide to Network Security & Network Troubleshooting Fundamentals
From Everand
Computer Networking: Beginners Guide to Network Security & Network Troubleshooting Fundamentals
Richie Miller
No ratings yet
CompTIA Security+ SY0-601 Exam Practice Tests
From Everand
CompTIA Security+ SY0-601 Exam Practice Tests
CertSquad Professional Trainers
No ratings yet