A VPC vRouter is a dedicated VM instance that provides
multiple network services.
Characteristics
A VPC vRouter can be used to provide network services such as virtual IP
address, elastic IP address, IPsec tunnel, port forwarding, load balancing,
DHCP, and Shared Bandwidth.
You can set multicast routing for VPC vRouters.
You can attach or detach a VPC network or public network to or from a VPC
vRouter as needed.
VPC vRouters have higher priorities to use resources than VM instances. If
the resource utilization of the host is so high that the resource
distribution must be prioritized, the resources are distributed first to VPC
vRouters, then to VM instances with High priorities, and then to VM
instances with Normal priorities. For example, if VPC vRouters and VM
instances are competing for CPU resources, the CPU resources are distributed
first to VPC vRouters.
Notice
Before you create a VPC vRouter, you need to create a public network,
management network, and VPC vRouter image required for a vRouter
offering.
A VPC vRouter is created from a vRouter offering with a public network and a
management network. The public network and management network defined in a
vRouter offering cannot be detached.
We recommend that a VPC vRouter has no more than 23 VPC networks and public
networks in total associated. Too many networks might lower the VPC vRouter
performance and affect the quality of related network services.
All network services in this Cloud share the bandwidth of the physical NIC.
Therefore, too many VIPs on a VPC vRouter might cause network performance
bottlenecks. We recommend that you reasonably plan the number of VIPs based
on actual bandwidth requirements.
Create a VPC vRouter
Log in to ZCF, switch to the corresponding region, and then on the main menu, choose Resource Center > Network Resource > vRouter > VPC vRouter. On the VPC vRouter page, click Create
VPC vRouter. Then, the Create VPC vRouter page is
displayed.
On the displayed page, set the following parameters:
Name: Enter a name for the VPC vRouter.
Description: Optional. Enter a description for the VPC
vRouter.
vRouter Offering: Select a vRouter offering you created
before.
Note: A VPC vRouter created from a vRouter offering has a public
network and a management network.
Enable SR-IOV: Optional. Choose whether to use
SR-IOV to pass through a VF NIC to the VPC vRouter as a default public
network NIC.
Note:
By default, SR-IOV is disabled and a vNIC is attached to the
VPC vRouter as a public network NIC.
If the hardware requirements are satisfied, you can enable
SR-IOV to attach a VF NIC to the VPC vRouter as a public
network NIC.
To enable SR-IOV, ensure the following points:
The public network and the management network of the
VPC vRouter are deployed separately.
The vRouter offering uses an openEuler image.
There are available VF NICs based on the physical
NICs corresponding to the public network.
Cluster: Optional. Specify a cluster for the host on
which the VPC vRouter is to be started.
Storage Allocation Policy: Specify how the Cloud
allocates a primary storage. The following two policies are supported:
System Allocation: The
Cloud allocates a primary storage according to the preconfigured
policy.
Custom: Select a primary storage as needed.
Primary
Storage: Select a primary storage for the VPC
vRouter.
Host: Optional. Select a host on which the VPC vRouter is
started.
Default IPv4/IPv6 Address: Optional. Specify a default IP
address for the VPC vRouter. If not specified, the Cloud allocates one
automatically.
Assign Management Network IP: Optional. Assign a
management network IP to the VPC vRouter.
Note: To assign a management network
IP, make sure that the management network used by the VPC vRouter is
separated from the public network the VPC vRouter uses. If the VPC vRouter
uses a same network both as its management network and public network, you
cannot assign a management network IP.
DNS: Optional. Set the DNS service for the VPC vRouter.
If not specified, 223.5.5.5 will be used.
Note:
You can set an IPv4 DNS or IPv6 DNS as needed. For example, you can
set the IPv4 DNS to 223.5.5.5 or IPv6 DNS to 240C::6644.
Services in the VPC vRouter can access the public network services
via DNS. You can also specify the other DNS address if
necessary.
For VM instances created by using a VPC network, the DNS is the
gateway of the VPC network. The VM traffics are forwarded by a VPC
vRouter.
CPU Pinning: Associate the
virtual CPUs (vCPUs) of a VPC vRouter with host pCPUs stringently and allow you
to allocate specific pCPUs for the VPC vRouter, thus improving VPC vRouter performances.
Note:
Pinning Format
In the left input box, set a vCPU range. In the right input
box, set a pCPU range. Range format: integer, hyphen(-), and
caret (^). Use commas to separate them.
The vCPU range depends on the vRouter offering attached to
the VPC vRouter.
The pCPU range depends on the pCPU quantity of the selected
cluster or host.
Example: In the left input box, enter 1. In the right input box,
enter 0-3,^2. This example indicates that vCPU 1 is stringently
associated with pCPU 0, pCPU 1, and pCPU 3, while ^ represents that
vCPU 2 is excluded.
Figure 1. Create VPC vRouter
Considerations
When you use a VPC vRouter, note the following:
VPC networks under different VPC vRouters are isolated from each other by
default at Layer 2.
The IP address segments of different VPC networks under the same VPC vRouter
cannot overlap. In addition, the gateways of any two VPC networks cannot be
the same.
Before an ordinary account can create a VPC vRouter, the admin needs to
share the vRouter offering. Otherwise, the ordinary account could not create
a VPC vRouter or VPC network.
Before you use a VPC vRouter to provide network services, make sure that the
VPC vRouter is in the running or connected state. If the VPC vRouter is in
other states, check whether exceptions occur on the related resources.
If a VM instance is using a VPC network, the VPC network could not be
detached from the VPC vRouter.
You can login to a VPC vRouter by using a password or SSH key:
SSH login using password:
By default, SSH login by using a password is disabled. To
enable this login method, you can go to Global Setting and
enable SSH Login with Password. After enabling,
reconnect the VPC vRouter to make the modification take
effect.
After enabling SSH Login with Password, you can log in to the VPC vRouter with
the default account and password. To modify the
password, you can go to Global Setting and set
VPC vRouter SSH Login Password. After the
modification, reconnect the VPC vRouter to make the new
password take effect.
VyOS 1.1.7 VPC vRouters:
Default SSH Account: vyos
Default SSH Password: vrouter12#
openEuler 22.03 VPC vRouter:
Default SSH Account: zstack
Default SSH Password: vrouter12#
SSH login using key: The SSH key is stored in the path:
$ZSTACK_HOME/WEB-INF/classes/ansible/rsaKeys/id_rsa.
Manage a VPC vRouter
Log in to ZCF, switch to the corresponding region, and then on the main menu, choose Resource Center > Network Resource > vRouter > VPC vRouter. Then, the VPC vRouter page appears.
The following table lists the actions that you can perform on a VPC vRouter.
Action
Description
Edit VPC vRouter
Edit the name and description of a VPC
vRouter.
Create VPC vRouter
Create a VPC vRouter.
Start VPC vRouter
Start a stopped VPC vRouter.
Stop VPC vRouter
Stop a running VPC vRouter.
Note: Stopping a VPC
vRouter also stops all network services of this VPC vRouter.
Proceed with caution.
Reboot VPC vRouter
Reboot a VPC vRouter.
Reconnect VPC vRouter
Reconnect a VPC vRouter.
Note: A VPC vRouter
automatically upgrades after the management node is upgraded and
rebooted.
Change Host
Migrate a VPC vRouter to another host, and hot
migration is supported.
This action changes only the host where the VPC vRouter runs
and does not change the primary storage.
In the LocalStorage scenarios, before you can hot migrate a
VPC vRouter, go to the Global Setting and set Change Host
Online on Local Storage to true.
We recommend that you perform this action during off-peak
hours.
Change Host and Primary Storage
Migrate a VPC vRouter to another host and primary
storage. After you change the primary storage, the host where the
VPC vRouter resides is changed based on the system policy.
You can hot migrate a VPC vRouter across different types of
primary storage, including LocalStorage↔SharedBlock,
LocalStorage↔NFS, and SharedBlock↔NFS.
You can hot migrate a VPC vRouter across primary storage of
the same type, including SharedBlock↔SharedBlock.
After you change the primary storage of a running VPC
vRouter, the snapshot of the VPC vRouter are not saved.
The network configurations of the cluster to which the
destination primary storage is attached need to satisfy the
network requirements of the VPC vRouter.
Before you hot migrate a VPC vRouter, detach all VF NICs
from the VPC vRouter.
Launch Console
Access a VPC vRouter through terminals.
Set Console Password
If the console already has a password and you modify this
password, the new password takes effect immediately after
modification.
If you add a new password or remove the console password,
restart the VPC vRouter(s) for the modification to take
effect.
Set Instance-Cluster Binding
Select whether to bind the VPC vRouter to the
current cluster.
You can enable/disable Instance-Cluster Binding for the VPC
vRouter individually. If not set individually, it is
consistent with the cluster setting Instance-Cluster
Binding.
If enabled, the VPC vRouter is bound to the current cluster
according to the cluster setting Instance Binding
Policy.
Hard: The VPC vRouter must always start in the
current cluster. If the cluster has no available
host, it fails to start. In addition, manual
cross-cluster migrations are not allowed.
Soft: The VPC vRouter is always prioritized to start
in the current cluster. If the cluster has no
available host, it may start in another cluster. In
addition, manual cross-cluster migrations are
allowed.
If disabled, the VPC vRouter is not bound to the current
cluster. It may start in any eligible clusters.
Change System
Change the operating system of the VPC vRouter.
Note:
Stop the VPC vRouter before you can change the system.
The new system takes effect after you restart the VPC
vRouter.
You can only change a VyOS 1.1.7 system to an openEuler
22.03 system.
Delete VPC vRouter
Delete a VPC vRouter.
Note: Deleting VPC vRouters
will cause the network services of relevant VM instances
unavailable. To resume the network service, you must re-create a
VPC vRouter, attach the VPC network used by the VM instances,
and then reboot the VM instances. Proceed with
caution.
Multicast Routing
Multicast Routing: VPC vRouters receive multicast information sent
by multicast sources and forward the information to V instances to realize
one-to-many connections on senders and receivers.
ZStack Cloud allows you to use VM instances as the
multicast information receivers, and to use VPC vRouters as multicast
routers to participate in the multicast routing message exchanges.
VPC vRouters support the PIM-SM/PIM-SSM protocol. In the PIM-SM protocol, RP
routers are the key devices in the PIM-SM domain. You can either manually
configure RP addresses or dynamically elect or assign RP addresses according
to the BSR mechanism.
Typical scenario of multicast routing: Assume that the user has a VPC environment on
ZStack Cloud, and demands that VM instances using the VPC
vRouter to communicate can receive multicast data from the public network. To do so,
the user needs to set relevant configuration of the VPC vRouter on ZStack Cloud.
Figure 2. Multicast Routing Topology
To use multicast routing, follow these steps:
Prepare multicast source.
Configure multicast routing.
Test whether multicast routing works.
The following tables list the assumed environment configurations.
Public Network
Public Network
Configuration
NIC
em01
VLAN ID
No VLAN
IP Range
10.108.10.100~10.108.10.200
Netmask
255.0.0.0
Gateway
10.0.0.1
DHCP IP
10.108.10.101
Management Network
Management
Network
Configuration
NIC
em02
VLAN ID
No VLAN
IP Range
192.168.29.10~192.168.29.20
Netmask
255.255.255.0
Gateway
192.168.29.1
Note:
For security and stability reasons, we recommend that you deploy
an independent management network and separate it from the
public networks.
The management network we mentioned here is the same as that in
ZStack Private
Cloud. That is,
the management network is the network used to manage hosts,
primary storages, and backup storages. If a management network
was created before, you can use it directly.
VPC Network
Private Network
Configuration
NIC
em01
VLAN ID
2800
IP CIDR
192.168.1.0/24
DHCP IP
192.168.1.2
The following section describes the detailed steps of how to use a multicast
routing.
Prepare multicast source.
Configure the VM instance as the multicast source according to the following
requirements:
Create a VM instance from the public network according to the
planned configuration. Set the VM name as VM-sender and use the
yum install -y socat command to install socat.
This way, the VM-sender can be used as the source to send multicast
messages.
Make sure that the multicast feature of the switch is enabled.
Configure multicast routing.
Create a VPC vRouter on ZStack Cloud based on the
planned network configuration. You can refer to the Basic
Deployment chapter.
Public Network: 10.108.10.100 to 10.108.10.200.
Make sure that the public network is on the same gateway with
the traditional physical network to ensure network
interconnection.
VPC vRouter: VPC vRouter-1.
On the Multicast Routing tab of the details page of
the VPC vRouter, click Enable to enable the
multicast routing feature. On the Multicast Routing
tab, click Actions > Add to add a static RP Configuration. On the displayed
Add Static RP Configuration dialogue box, set
the following parameters:
RP Address: Enter a RP address, for
example, 10.108.10.125.
Note: You can either manually
configure RP addresses or dynamically elect or assign RP
addresses according to the BSR mechanism. The RP address
must be a stable public IP address.
Group: Set an IP multicast group address
to which multicast messages are sent, for example,
239.1.1.1/32.
Note:
An IP multicast group is a collection of receivers
identified by IP multicast addresses. VPC vRouters
join the IP multicast group as its members so that
they can receive the multicast data sent to the
group.
Enter the IP multicast group address in the format
of a CIDR block.
Figure 3. Add Static RP Configuration
Create a VPC network using the VPC vRouter, and create a VM instance
from the VPC network, for example, VM-receiver. Use the yum
install -y socat command to install socat so that the
VM-receiver can receive multicast messages.
Note: VM instances need to
correctly configure the firewall to receive multicast messages, for
example, enabling IGMP protocol and receiving multicast
data.
Test whether the multicast routing works.
Launch the console of VM-sender and run the following command to
send an UDP data packets to the address whose multicast group
address is 239.1.1.1 and port is 54321 and set the TTL
of the multicast group data as
10.
[root@localhost~]# for i in {1..100} ;do echo hi+$i | socat - udp4-sendto:239.1.1.1:54321,sp=54321,ip-multicast-ttl=10 ;done
Figure 4. Send Multicast Message
Launch the console of VM-receiver and run the following command,
which indicates that specifying the NIC (em01) to add to the
multicast group (239.1.1.1) and receiving the UDP data
packets from port
54321.
As described above, the VM-receiver receives the multicast messages
from VM-sender, which indicates that the multicast routing takes effect.
So far, we have introduced how to use multicast routing.
Basic Deployment
ZStack Cloud VPC network supports both IPv4 and IPv6 protocols and
users can choose to use IPv4, IPv6, or IPv4+IPv6 dual-stack networks as needed. This
chapter introduces the basic deployment of IPv4 and IPv6 VPC networks in detail.
Distributed Routing
Distributed routing: After distributed routing feature is enabled, the Cloud will
optimize east-west network traffic to improve I/O performance and reduce the network
latency. Distributed routing also strengthens the reliability of communication among
VM instances and the intranet traffic across three layers will not fail due to
vRouter failures.
Typical distributed routing scenarios:
Assume that the user has three hosts. VM-1 and VM-2 are on different hosts,
and on vxlan1: 192.168.1.0/24 and vxlan2: 192.168.2.0/24,
respectively. Since the L2 and L3 networks of the two VM instances are
different, the traffic that flows between VM-1 and VM-2 needs to be routed
through a VPC vRouter on the third host.
After the distributed routing is enabled, messages sent by VM-1 will be sent
to a VPC vRouter through the traditional path. The network proxy of the VPC
vRouter sends an optimization instruction through ZSNP protocol to that of
the compute node. Then, messages of VM-1 will be directly sent to VM-2
without passing through a VPC vRouter.
Note: ZSNP protocol: Based on IP
protocol, it is used to solve the problem that the router proxy cannot
know the information of compute node where the VM instance
resides.
This scenario mainly introduces how to use distributed routing with VXLAN network as
an example.
Create a VPC vRouter.
Create a VXLAN pool.
Create L2 private networks (L2-VXLAN1 and L2-VXLAN2) and attach them to the
corresponding cluster. These L2 private networks are used to create L3 VPC
networks.
Specify a VPC vRouter to create L3 VPC networks (VPC Netowrk-1 and VPC
Network-2).
Use VPC Network-1 to create VM-1 on Host-1 and use VPC Network-2 to create
VM-2 on Host-2.
Enable distributed routing, test the network connectivity between VPC
Network-1 and VPC Network-2, and monitor traffic flow direction.
Note: Note that all private network range must not overlap.
The following tables list the assumed environment configurations.
Public Network
Public Network
Configuration
NIC
em01
VLAN ID
No VLAN
IP Range
10.108.10.100~10.108.10.200
Netmask
255.0.0.0
Gateway
10.0.0.1
DHCP IP
10.108.10.101
Management Network
Management
Network
Configuration
NIC
em02
VLAN ID
No VLAN
IP Range
192.168.29.10~192.168.29.20
Netmask
255.255.255.0
Gateway
192.168.29.1
Note:
For security and stability reasons, we recommend that you deploy
an independent management network and separate it from the
public networks.
The management network we mentioned here is the same as that in
ZStack Private
Cloud. That is,
the management network is the network used to manage hosts,
primary storages, and backup storages. If a management network
was created before, you can use it directly.
VPC Network-1
Private Network
Configuration
NIC
em01
VLAN ID
2800
IP CIDR
192.168.1.0/24
DHCP IP
192.168.1.2
VPC Network-2
Private Network
Configuration
NIC
em01
VLAN ID
2900
IP CIDR
192.168.2.0/24
DHCP IP
192.168.2.2
The following section describes the detailed steps of how to use distributed
routing.
Create a VPC vRouter.
Create a VPC vRouter according to the planned network configuration. For more
information, see Basic Deployment.
Public Network: 10.108.10.100 to 10.108.10.200. Make
sure that the public network is on the same gateway with the
traditional physical network to ensure network interconnection.
VPC vRouter: VPC vRouter-1.
Create a VXLAN Pool.
Log in to ZCF, switch to the corresponding region, and then on the main menu, choose Resource Center > Network Resource > L2 Network Resources > VXLAN Pool. On the VXLAN Pool page, click
Create VXLAN Pool. Then, the Create
VXLAN Pool page is displayed. On the displayed page, set the
following parameters:
Zone: By default, the current zone is
displayed.
Name: Enter a name for the VXLAN pool.
Description: Optional. Enter a description
for the VXLAN pool.
SDN Type: Select
Software.
VNI Range: Enter the start ID and end ID of
VXLAN networks, for example, 1 to 1000.
Note:
You can enter an ID that ranges from 1 to 16777214.
The end ID must be equal to or greater than the start
ID.
The two VNI IDs 16777215 and 16777216 are reserved by
the system of this cloud platform.
Cluster: Optional. Attach the VXLAN pool to a cluster.
Note:
You can attach a VXLAN pool to a cluster when you create
the VXLAN pool or after the VXLAN pool is created.
When you attach the VXLAN pool to a cluster, IP
addresses of the compute nodes must be available in the
cluster that correspond to the VTEP CIDR block.
VTEP CIDR: Enter the corresponding VTEP CIDR
block.
Figure 6. Create VXLAN Pool
Create L2 private networks and attach them to the corresponding cluster. These
L2 private networks are used to create L3 VPC networks.
Log in to ZCF, switch to the corresponding region, and then on the main menu, choose Resource Center > Network Resource > L2 Network Resources > L2 Network. On the L2 Network page, click
Create L2 Network. Then, the Create L2
Network page is displayed. On the displayed page, set the
following parameters:
Zone: By default, the
current zone is displayed.
Name: Enter a name for the L2 network, for
example, L2-VXLAN1.
Description: Optional. Enter a description
for the L2 network.
Switch Type: Select Linux
Bridge.
Network Type: Select
VxlanNetwork.
VXLAN Pool: Select a VXLAN pool of the
software SDN type.
VNI: Optional. Enter a specified VNI in the
VXLAN pool. If not specified, the Cloud allocates a VNI
randomly.
Figure 7. Create L2VxlanNetwork
Similarly, create another L2 private network named as L2-VXLAN2.
Specify a VPC vRouter to create L3 VPC networks.
Log in to ZCF, switch to the corresponding region, and then on the main menu, choose Resource Center > Network Resource > L3 Network Resources > VPC Network. On the VPC Network page, click
Create VPC Network. The Create VPC
Network page appears. On the displayed page, set the
following parameters:
Name: Enter a name for the VPC network, for
example, VPC Network-1.
Description: Optional. Enter a description
for the VPC network.
L2 Network: Select
L2-VXLAN1.
VPC vRouter: Optional. You can specify a VPC
vRouter when you create a VPC network or attach a VPC vRouter after
you create the VPC network.
Network Address Type: Select
IPv4.
Network Range Method: Select
CIDR.
CIDR: Set a CIDR block for the VPC network,
for example, 192.168.1.0/24.
Gateway: Optional. Set a gateway for the VPC
network.
DHCP Service: Choose
whether to enable the DHCP service.
Note:
The DHCP service is a built-in distributed service
of the Cloud, which assigns IP addresses only to
resources in the Cloud and does not conflict with
your existing DHCP server.
By default, the DHCP service is enabled so that the
NICs using this L3 network acquire IP addresses in a
DHCP mode. You can customize a DHCP IP or use the
DHCP IP that the system assigned according to the IP
allocation policy.
If you disable this option, NICs using this L3
network acquire IP address in a Static mode. The
Cloud does not assign IP addresses to NICs
automatically. If the NICs need IP addresses, you
need to configure IP addresses for them manually. In
addition, you cannot specify a DHCP IP. Neither can
the system allocate one.
IP Allocation Policy: Optional.
If the DHCP service enabled, IP addresses can be
assigned according to the following three allocation
policies:
Random: The system
randomly assigns IP addresses from the network
range.
Allocate in Order:
The system assigns all available IP addresses
from the network range in ascending order.
Released IP addresses are assigned in the next
allocation.
Example: Assume that the network range is
192.168.0.101～192.168.0.120, within
which 192.168.0.101～192.168.0.108
are allocated. If 192.168.0.106 is
released, it will be assigned first in the next
allocation.
Allocate in Cycle:
The system assigns available IP addresses to
VM instances from the network range in ascending
order. Released IP addresses are assigned when
currently available IP addresses are used up.
Example: Assume that the network range is
192.168.0.101～192.168.0.120, within
which 192.168.0.101～192.168.0.108
are allocated. If 192.168.0.106 is
released, it will be assigned after
192.168.0.120 is used.
DHCP IP:
Optional. Set an IP address for the DHCP server, for
example, 172.20.108.10.
Note:
A DHCP IP is an IP address used by the DHCP
service to assign IP addresses to resources that
use this L3 network.
If you create an L3 network for the first time
with the DHCP service enabled, or if you add the
first network range to an L3 network with the DHCP
service enabled, you can customize the DHCP
IP.
If the L3 network has a DHCP IP, you cannot
customize the DHCP IP when you add a network
range.
The DHCP IP can be in or outside the added IP
range, but it must be an unoccupied IP address in
the CIDR block of the added IP range
The IP range determined by the start IP and
end IP cannot contain the link-local address
169.254.0.0/16.
If you select random as the IP allocation
policy and this field is left blank, the system
randomly assigns IP addresses from the added
network range.
If you select allocate in order/allocate in
cycle as the IP allocation policy and this field
is left blank, the system uses the start IP
address in the network range as the DHCP IP.
DNS: Optional. Provide DNS services for an L3
network.
Figure 8. Create VPC Network
Similarly, use L2-VXLAN2 to create another VPC network named as VPC
Network-2.
Use VPC Network-1 to create VM-1 on Host-1 and use VPC Network-2 to create VM-2
on Host-2.
Figure 9. Use VPC Network to Create VM Instance
Test the network connectivity between VPC Network-1 and VPC Network-2, and
monitor traffic flow direction.
Log in to VM-1, test whether VM-1 can successfully
ping VM-2.Figure 10. VM-1 Ping VM-2
Log in to VM-2, test whether VM-2 can successfully
ping VM-1.Figure 11. VM-2 Ping VM-1
Log in to ZCF, switch to the corresponding region, and then on the main menu, choose Resource Center > Network Resource > vRouter > VPC vRouter. On the VPC vRouter page, locate the
VPC vRouter and enter its details page. On the details page, you can
view the NIC monitoring data.Figure 12. NIC Monitoring Data
As described above, VM-1 and VM-2 can communicate with each other. Traffic
flows through the VPC vRouter and can be continuously monitored on the NIC
monitoring card.
Enable distributed routing, test the network connectivity between VPC Network-1
and VPC Network-2, and monitor traffic flow direction.
Log in to ZCF, switch to the corresponding region, and then on the main menu, choose Resource Center > Network Resource > vRouter > VPC vRouter. On the VPC vRouter page, locate the
VPC vRouter and enter its details page. On the details page, turn on the
Distributed Routing switch.Figure 13. Enable Distributed Routing
Log in to VM-1, test whether VM-1 can successfully
ping VM-2.Figure 14. VM-1 Ping VM-2
Log in to VM-2, test whether VM-2 can successfully
ping VM-1.Figure 15. VM-2 Ping VM-1
Log in to the management node and run the following API to view the
distributed routing
status.
Figure 16. Enable Distributed Routing As described above, the distributed routing is successfully
enabled and the Cloud begins to optimize east-west network traffic.
Log in to ZCF, switch to the corresponding region, and then on the main menu, choose Resource Center > Network Resource > vRouter > VPC vRouter. On the VPC vRouter page, locate the
existing VPC vRouter and enter its details page. On the details page,
view the NIC monitoring data.Figure 17. NIC Monitoring Data
As described above, after the traffic between VM-1 and VM-2 is first
connected through the VPC vRouter, the subsequent traffic will be directly sent
between VM-1 and VM-2. The NIC monitor does not detect traffic flows as
expected, indicating that the distributed routing successfully takes
effect.
So far, we have introduced how to use a distributed
routing.
Note: A VPC vRouter created from a vRouter offering has a public
network and a management network.
