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

Configuration Guide - Virtualization

CloudEngine 12800 and 12800E V200R002C50

This document describes the configurations of virtualization, including stack and VS.

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 Resources for a VS

Configuring Resources for a VS

Context

After creating a VS, the PS administrator needs to assign both physical resources and logical resources to the VS.
  • Physical resources: Only physical Ethernet interfaces on interface cards can be allocated. By default, all interfaces on an interface card belong to the Admin-VS.

  • Logical resources: Allocatable logical resources include unicast routing entries, multicast routing entries, VLANs, and other resources. By default, a new VS has the default logical resource specifications. For details, see Default Settings for VSs. You can use a logical resource template to modify specifications of logical resources in batches or modify specifications of a specified resource item for a VS.

NOTE:
  • Only the PS administrator can allocate physical interfaces to VSs.

  • Only physical interfaces on interface cards can be assigned to VSs. However, the CSS and Eth-Trunk member interfaces cannot be assigned to VSs. After an interface is allocated to a VS, original configurations on the interface are deleted.

  • In port mode, all interfaces on an interface card can be allocated to any VS; in group mode, all interfaces on the same group must be allocated to the same VS.

  • There is no binding between a logical resource template and a VS. After a logical resource template is loaded on a VS, modifying the logical resource template does not affect the VS. The modified logical resource template takes effect only after it is loaded to the VS again.

Procedure

  • Assign physical interface resources.
    1. Run system-view

      The system view is displayed.

    2. Run admin

      The admin view is displayed.

    3. Run virtual-system vs-name

      The VS management view is displayed.

    4. Run assign interface interface-type interface-number1 [ to interface-number2 ]

      Physical interfaces are assigned to the VS.

      When assigning physical interfaces to a VS in group mode, view interface groups on cards according to Licensing Requirements and Limitations for VSs to determine which interfaces will be assigned to this VS.

    5. Run commit

      The configuration is committed.

  • (Optional) Assign logical resources.
    1. Run system-view

      The system view is displayed.

    2. Run admin

      The admin view is displayed.

    3. Run virtual-system vs-name

      The VS management view is displayed.

    4. Set logical resource specifications.

      • Use a logical resource template to allocate logical resources to the VS.

        Run assign resource-template template-name

        A logical resource template is loaded on the VS.

        NOTE:
        • A user can run the port-mode { group | port } [ resource-template template-name ] command to specify a logical resource template for a VS when configuring the interface assignment mode or run the assign resource-template template-name command to specify a logical resource template for the VS.

        • Skip this step if a logical resource template has been specified for the VS in the port-mode { group | port } [ resource-template template-name ] command.

      • Set specifications of specified resource items.

        • Run resource { u4route | m4route | u6route | m6route | vlan | vpn-instance } upper-limit resource-limit

          The specifications of the routing entry, VLAN, or VPN instance are set.

        • Run resource { cpu weight weight | memory ratio-threshold ratio-threshold | disk ratio-threshold disk-ratio-threshold }

          The maximum CPU usage, storage space, and memory usage are set.

        • Run resource { mpls | trill | mcast } enable

          MPLS, TRILL, or multicast is enabled.

    5. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-03-21

Document ID: EDOC1000166610

Views: 43598

Downloads: 130

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next