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

CLI-based Configuration Guide - Virtualization

AR500, AR510, AR531, AR550, AR1500, and AR2500 V200R009

This document provides the basic concepts, configuration procedures, and configuration examples in different application scenarios of the virtualization feature supported by the device.

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).
Configuring Communication Among the Routing System, HostOS, and VMs

Configuring Communication Among the Routing System, HostOS, and VMs

Context

Virtual systems on a device include the routing system, VMs, and HostOS. The virtual systems must communicate with each other before communicating with the external network through the routing system. The virtual systems communicate through a vSwitch.

Procedure

  • Configuring communication through a vSwitch
    1. Run system-view

      The system view is displayed.

    2. Run virtual-environment ip-address

      Enter the virtual-environment view.

      The parameter ip-address indicates the IP address of the virtual interface br0.

    3. Run veth vport-name

      A virtual interface is created for the HostOS.

      By default, the system creates HostOS virtual interfaces veth1 and br0.

    4. Run link veth vport-name to veth vport-name

      A virtual link between a VM and the HostOS or between two VMs is configured.

      NOTE:

      If a VM needs to directly communicate with another VM, configure a virtual link between the two VMs; otherwise, you do not need to configure a virtual link between them.

    5. Run ovs bridge bridge-name

      A vSwitch is created and the vSwitch view is displayed, or an existing vSwitch view is displayed.

      By default, the system creates the vSwitch br0.

    6. Run port vport-name link-type { access | trunk }

      Virtual interfaces are added to the vSwitch.

      These virtual interfaces include all HostOS virtual interfaces created in step 3.

    7. (Optional) Run port vport-name default vlan vlan-id

      The default VLAN for virtual interfaces is configured and the virtual interfaces are added to the VLAN.

      By default, VLAN 1 is the default VLAN of all virtual interfaces.

    8. (Optional) Run port trunk allow-pass vlan { all | vlan-id &<1-10> | vlan-id1 to vlan-id2 }

      The VLAN to which virtual trunk interfaces are added is configured.

  • Configuring direct communication through virtual links
    1. Run system-view

      The system view is displayed.

    2. Run virtual-environment

      The virtual-environment view is displayed.

    3. Run link veth vport-name to interface interface-type interface-number

      A virtual link between the routing system and a VM is created.

    4. Run link veth vport-name to veth vport-name

      A virtual link between two VMs is created.

Translation
Download
Updated: 2019-05-06

Document ID: EDOC1000177806

Views: 8943

Downloads: 38

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next