No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

CX11x, CX31x, CX710 (Earlier Than V6.03), and CX91x Series Switch Modules V100R001C10 Configuration Guide 13

The documents describe the configuration of various services supported by the CX11x&CX31x&CX91x series switch modules The description covers configuration examples and function configurations.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Virtualization Perception Solution

Virtualization Perception Solution

Related Concepts

The following roles are required to implement server virtualization on a network:

  • Virtual center (vCenter): serves as an integrated management tool. It manages virtualization devices, such as virtual machines (VMs) and virtual switches (vSwitches).

  • Network center (nCenter): automatically collects information about physical and virtual networks and dynamically allocates predefined network resources based on VM access. A network administrator only needs to configure VMs. When an nCenter detects VMs, it delivers the configurations of the VMs to network devices. nCenter deployment improves service deployment efficiency, simplifies device management, and reduces the configuration error ratio.

Introduction

Figure 10-59 shows Huawei's virtualization perception solution. An nCenter is deployed on a remote network device. A vCenter is deployed on one of the server integrated with VMs or on a remote network device. A network administrator implements virtualization perception and service deployment based on information exchanged between the nCenter and vCenter, and between the nCenter and the Switch.

Figure 10-59 Virtualization perception solution

The nCenter communicates with the vCenter using an application process interface (API) of the vCenter. Therefore, this solution is also known as an API-based virtualization detection solution.

The API-based virtualization solution has the following functions:
  • VM login: After the vCenter starts a VM, the nCenter and Switch detect that the VM goes online.

  • Topology detection: After a VM goes online, the nCenter obtains the topologies of the physical and virtual networks.

  • Policy deployment: The requirements on access control lists (ACLs) and quality of service (QoS) policies vary according to services. ACLs and QoS policies can be deployed on the Switch and VMs to meet these requirements.

  • VM logout: After a VM goes offline, the nCenter and Switch detect the VM logout and delete the policies that apply to the VM.

  • VM migration: When VM resources of a server are insufficient and VMs of the server need to be migrated to another server, the policies and resources of the VMs need to be migrated too.

API-based Virtualization Perception Solution

A network center (nCenter) uses an application process interface (API) of a virtual center (vCenter) to detect virtual machine (VM) login and migration. When the nCenter detects VM login or migration, it notifies a switch. VM login and migration are detected by an nCenter, but not by protocols or devices exchanging messages. Therefore, the API-based virtualization perception solution is also known as an nCenter out-band virtualization perception solution.

VM Login

On a network in which the API-based virtual perception solution is used, after an nCenter uses an API of a vCenter to detect VM login, the nCenter notifies the Switch, as shown in Figure 10-60.

Figure 10-60 Network diagram for VM login

The VM login process is divided into VM pre-login and VM login, as shown in Figure 10-61.

Figure 10-61 VM login procedure

Topology Detection

On a network in which the virtualization perception is used, a neighbor discovery protocol reports neighbor relationships on physical and virtual networks to an nCenter. The nCenter draws the network topology based on neighbor relationships. The nCenter can manage the end-to-end (E2E) data center network and E2E network of VMs, and dynamically adjust network configurations.

Figure 10-62 shows how to detect network topologies.

Figure 10-62 Network diagram for topology detection
  • The Link Layer Discovery Protocol (LLDP) or Cisco Discovery Protocol (CDP) discovers the neighbor relationships between a switch and a physical server, and between a switch and a virtual switch (vSwitch).

  • The topology from a vSwitch to a VM is detected using an API provided by a vCenter. An nCenter uses API messages to identify connections between a VM and a vSwitch, and between a vSwitch and a physical server.

  • The nCenter uses the neighbor relationships discovered above to draw the data center network topology.

Policy Deployment

Server virtualization and cloud computing bring new challenges to network configuration and service classification.
  • Traditional network-oriented manual configuration cannot meet server virtualization requirements. For example, the virtual local area network (VLAN) technology has been widely used as Layer 2 network isolation technology on networks in which server virtualization is not used. On networks in which server virtualization is used, the efficiency for configuring VLAN technology is low and the possibility of VLAN configuration errors is high. Therefore, manual VLAN configuration does not meet the automation requirements of cloud computing.

  • Service types and tenant traffic policies, such as access control lists (ACLs) and quality of service (QoS) policies, vary according to VMs.

  • The Dynamic Host Configuration Protocol (DHCP) snooping-based security policy is an important means for enhancing Layer 2 network security. When a VM is moved from a physical server to another physical server, the security policy that applies to the VM also changes.

In the automatic network policy deployment solution, an nCenter applies policy profiles by service type and tenant classification, and maintains VM information and policy profiles. A network administrator must configure policy profiles on the nCenter before VM startup. Figure 10-63 shows policy deployment.

Figure 10-63 Policy deployment procedure

VM Logout

When a VM goes offline, the nCenter detects VM logout and notifies the Switch. The Switch deletes all information about the VM. Figure 10-64 shows how a VM goes offline.

Figure 10-64 Network diagram for VM logout

VM Migration

After a VM of a server is started, the VM may be migrated to another server due to server resource limitations, such as high CPU usage and insufficient memory resources. Figure 10-65 shows how a VM is migrated. The network policy and configuration of the VM remain unchanged during VM migration, which prevents service interruption.

Figure 10-65 Network diagram for VM migration

A VM migration process consists of the logout of the original VM and the login of a new VM. Figure 10-66 shows how a VM is migrated from one server to another server.

Figure 10-66 VM migration procedure
Translation
Download
Updated: 2019-12-13

Document ID: EDOC1000041694

Views: 60636

Downloads: 3623

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next