Guide For Interworking Between CloudEngine Switches and VMware VRNI
Guide For Interworking Between CloudEngine Switches and VMware VRNI
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: [email protected]
Overview
This document describes the principle and service process of interconnection between
VMware vRNI and Huawei CloudEngine series switches, and provides detailed
interconnection operation guide and verification description.
Intended Audience
This document is intended for:
Product managers
Marketing representatives
Delivery engineers
Maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Change History
Issue Date Description
Contents
2 Networking Planning...................................................................................................................7
3 Procedure.........................................................................................................................................9
3.1 Configuration Roadmap.................................................................................................................................................9
3.2 Configuring a CE Switch................................................................................................................................................9
3.2.1 Configuring SSH.........................................................................................................................................................9
3.2.2 Configuring NetStream.............................................................................................................................................10
3.3 Configuring VMware ESXi..........................................................................................................................................11
3.4 Verification...................................................................................................................................................................17
1 Function Overview
Path Detection
For VMs on the ESXI host, VMware vRNI can explicitly draw a Layer 3 reachable path
between the two VMs. As shown in the following figure, the Layer 3 path of traffic when the
VM at 10.1.2.2 accesses the VM at 11.1.3.2 is drawn on VMware vRNI.
In the topology view, you can query information about all ECMP links, switches where
gateways are located, and next-hop routes.
Traffic Monitoring
VMware vRNI uses NetStream of switches to monitor traffic and obtains the traffic status of
switches based on the sampling packets sent from the switches to VMware vRNI, as shown in
the following figure. The following figure shows the traffic from ubuntu01_22 to
ubuntu01_23. The source IP address is 10.1.2.2, the port number is 22, and the traffic rate is
428.3 kbit/s. A total of 4.3 GB traffic is sent during the period from 08:26 on December 6 to
08:26 on December 7.
1.2 Principle
Path detection: vRNI connects to CE switches through SSH, and then runs commands on the
CE switches to obtain the command outputs. After parsing the command outputs, vRNI
calculates the current networking information and completes path detection.
Traffic monitoring: After NetStream is configured on CE switches, sampling packets are sent
to vRNI. vRNI calculates the current traffic status based on the sampling packets.
Path Detection
VMware vRNI logs in to a CE switch through SSH, sends a query command to the CE
switch, parses the command output from the CE switch to obtain necessary routing
information, and then draws a path topology based on the routing information. The following
table lists the involved commands. In the commands, | no-more indicates that the output
result is not split.
Command Function
display device board | no-more Displays the device type and status,
excluding information about power modules
and fan modules.
display device manufacture-info | no- Displays manufacturing information.
more
display version | no-more Displays the device version.
display interface | no-more Displays the status of and statistics about
interfaces.
display port vlan | no-more Displays information about interfaces of a
VLAN.
display interface Eth-Trunk | no-more Displays the Eth-Trunk status.
display ip vpn-instance | no-more Displays the VPN instance configuration.
display ip vpn-instance interface | no- Displays information about interfaces bound
more to a VPN instance.
display ip routing-table all-routes | no- Displays IPv4 routes of the public network
more and all private networks.
display mac-address | no-more Displays information about MAC address
entries of all types, including the destination
MAC address, VLAN ID of a device,
outbound interface, and MAC address entry
type.
display lldp neighbor brief | no-more Displays brief information about LLDP
neighbors, such as the devices and
interfaces that are connected to the local
device.
display vrrp | no-more Displays the status and configuration of a
VRRP group.
display dfs-group 1 m-lag | no-more Displays information about the M-LAG
with DFS group 1.
VMware vRNI obtains and parses information such as neighbors, interfaces, VLAN IDs,
VPN, and routes based on command outputs returned by CE switches, and generates a path
topology based on a certain logic algorithm.
Traffic Monitoring
CE switches need to be configured with NetStream v9 to send sampling packets to VMware
vRNI (VMware vRNI needs to be configured with a proxy and sampled packets are sent to
the agent for processing). VMware vRNI analyzes the sampling packets.
2 Networking Planning
Figure 1-1 shows typical networking for interconnection between CE switches and VMware
vRNI. ESXI hosts are connected to CE switches through M-LAG, or a single host is
connected to an ESXI host through a single link. An ESXI host is virtualized into multiple
VMs and configured with IP addresses on different network segments.
The IP addresses here are examples. Replace them based on the actual IP address planning.
Figure 1-1 Typical networking for interconnection between CE switches and VMware vRNI
vRNI is installed on ESXI-1. When vRNI is reachable to CE switches at Layer 3 and can log
in to CE switches in SSH mode, vRNI can manage CE switches.
3 Procedure
The interconnection between vRNI and CE switches does not depend on the physical
networking and service configuration of the CE switches. Therefore, the networking is based
on the actual service requirements.
3.1 Configuration Roadmap
3.2 Configuring a CE Switch
3.3 Configuring VMware ESXi
3.4 Verification
<HUAWEI> system-view
[~HUAWEI] user-interface maximum-vty 21
[~HUAWEI] user-interface vty 0 20
[*HUAWEI-hi-vty0-20] idle-timeout 0
[*HUAWEI-ui-vty0-20] authentication-mode aaa
[*HUAWEI-ui-vty0-20] protocol inbound all
[*HUAWEI-ui-vty0-20] commit
[~HUAWEI-ui-vty0-20] quit
----End
<CE6865> system-view
[~CE6865] netstream export ip version 9 //Configure the version
number of exported packets carrying IPv4 original flow statistics
to 9.
[*CE6865] netstream export ip source X.X.X.X //Configure the
source address for the exported packets carrying IPv4 flow
statistics. You can set this parameter to the IP address of
MEth0/0/0 on a CE switch.
[*CE6865] netstream export ip host X.X.X.X 2055 //Configure the
destination IP address and destination UDP port number for the
exported packets carrying IPv4 flow statistics. In this example,
X.X.X.X is the IP address of the proxy server of vRNI and the port
number is 2055.
[*CE6865] netstream timeout ip active 1 //Set the active aging
time of IPv4 original or flexible flows to 1 minute.
[*CE6865] netstream timeout ip inactive 60 //Set the inactive
aging time of IPv4 original or flexible flows to 60 seconds.
[*CE6865] commit
Step 2 Configure the interface on the CE switch that is directly connected to an ESXI host.
[~CE6865] interface 40ge1/0/1
[~CE6865-40GE1/0/1] netstream inbound ip //Enable IPv4 flow
statistics collection on the inbound interface.
[~CE6865-40GE1/0/1] netstream outbound ip //Enable IPv4 flow
statistics collection on the outbound interface.
[*CE6865-40GE1/0/1] netstream sampler random-packets 1024 inbound
//Configure the device to sample incoming traffic on an interface
and set the sampling interval of random packets to 1024.
[*CE6865-40GE1/0/1] netstream sampler random-packets 1024 outbound
//Configure the device to sample outgoing traffic on an interface
and set the sampling interval of random packets to 1024.
[*CE6865-40GE1/0/1] commit
[~CE6865-40GE1/0/1] quit
----End
Step 3 Configure a VLAN ID. The VLAN ID is the ID of the VLAN that a VM in a port group
belongs to, which must be the same as the VLAN ID of the switch interface that is directly
connected to an ESXI host.
Step 4 Add a host to the distributed switch to prepare for migrating VMs on the host.
Step 6 Add the physical network adapter that is directly connected to the CE switch to the uplink
port.
Migrate VMs from the original network to the new port group of the distributed switch for
unified management.
Step 10 Configure LACP. If a LAG is configured on the network, you need to add a LAG interface
and configure the egress network adapter of a server to work in LAG mode.
Step 11 After the configuration is complete, check the networking information, as shown in the
following figure.
----End
3.4 Verification
After the preceding configurations are complete, VMware vRNI automatically manages
switches on the network segment. After CE switches are detected, transmit traffic between
VMs. The VM-VM forwarding path is displayed, as shown in the following figure.