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 8800, 7800, 6800, and 5800 V200R005C10

This document describes the configurations of virtualization, including stack and SVF.
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 a Fabric Port

Configuring a Fabric Port

Context

A parent switch connects to leaf switches using fabric ports. One or more member ports can be added to a fabric port to improve SVF link bandwidth and reliability.

NOTE:
  • A fabric port can have a maximum of eight member ports.

  • After a 10GE port on the CE6850EI, CE6810EI is directly added to a fabric port, the four 10GE ports in the same range of 4N+1 to 4N+4 (N = 0, 1, 2, 3...) are automatically configured as physical stack member ports, but the other three 10GE ports are not added to the fabric port. For example, after you add 10GE1/0/1 to a fabric port, ports 10GE1/0/1 to 10GE1/0/4 are all configured as physical stack member ports, but only 10GE1/0/1 is added to the fabric port.

Procedure

  1. Create a fabric port and bind a leaf ID to it.
    1. Run the system-view command to enter the system view.
    2. Run the interface fabric-port port-id command to create a fabric port.

      By default, no fabric port exists in the system. The value of port-id ranges from 1 to 24.

    3. Run the port bind member member-id command to bind a leaf ID to the fabric port.

      By default, no leaf ID is bound to a fabric port. The value of member-id ranges from 101 to 254.

      Leaf IDs are used to identify and manage leaf switches in an SVF system. Each leaf switch has a unique leaf ID. Leaf IDs are bound to fabric ports. When a leaf switch connects to the parent switch, it obtains its leaf ID from the parent switch.

      NOTE:
      • Each fabric port can have only one leaf ID bound to it, and each leaf ID can be bound to only one fabric port.

      • If you change or delete the leaf ID bound to a fabric port, the leaf switch connected to the fabric port will restart.

    4. (Optional) Run the description description command to configure the description of the fabric port.

      By default, a fabric port does not have a description.

      To facilitate fabric port management and identification, you can configure descriptions for fabric ports. For example, you can describe the ID of a leaf switch that connects to a fabric port.

    5. Run the commit command to commit the configuration.
  2. Add the service ports to the fabric port.

    NOTE:

    The configuration can be performed in the fabric port view or interface view. The two configuration methods obtain the same result.

    Service ports are automatically configured as physical member ports after being added to a fabric port. Alternatively, run the port mode stack interface interface-type { interface-number1 [ to interface-number2 ] } &<1-32> command in the stack management view or run the port mode stack command in the interface view to configure service ports as physical member ports and then add the physical member ports to a fabric port.

    • Configuration in the fabric port view:
      1. Run the system-view command to enter the system view.

      2. Run the interface fabric-port port-id command to enter the fabric port view.

      3. Run the port member-group interface interface-type { interface-number1 [ to interface-number2 ] } &<1-8> command to add member ports to the fabric port.

      4. Run the commit command to commit the configuration.

    • Configuration in the interface view:
      1. Run the system-view command to enter the system view.

      2. Run the interface interface-type interface-number command to enter the interface view.

      3. Run the fabric-port port-id command to add the port to the fabric port.

        To add multiple ports to the fabric port, repeat steps b and c.

      4. Run the commit command to commit the configuration.

  3. (Optional) Configure the working mode for a 40GE port that has a high-speed cable installed.
    1. Run the system-view command to enter the system view.
    2. Run the interface interface-type interface-number command to enter the interface view.
    3. Run the port copper mode { sr4 | cr4 }command to configure the working mode for a 40GE port that has a high-speed cable installed.

      By default,
      • On CE6810-32T16S4Q-LI, CE6850-48T6Q-HI, CE6851-48S6Q-HI, CE6855HI, CE6856HI, CE5855-24T4S2Q-EI, and CE5855-48T4S2Q-EI, the working mode of 40GE ports that have high-speed cables installed is SR4.
      • On CE6810-48S4Q-LI and CE6810-24S2Q-LI, 40GE ports that have high-speed cables installed can auto-negotiate to work in CR4 or SR4 mode.
      • On other switch models, 40GE ports that have high-speed cables installed can auto-negotiate to work in CR4 or SR4 mode. After being added to stack ports, these 40GE ports work in CR4 mode.

      By default, if a CE6810-32T16S4Q-LI, CE6850-48T6Q-HI, CE6851-48S6Q-HI, CE6855HI, CE6856HI, CE5855-24T4S2Q-EI, or CE5855-48T4S2Q-EI sets up a stack or an SVF system with other device model using 40GE ports that have high-speed cables installed, the connected device can enable the 40GE ports on both ends to work in the same mode through auto-negotiation. If the two ports work in different modes, they will become Down. However, auto-negotiation lasts a certain period. To ensure that the two ports can rapidly become Up, you are advised to run this command on the connected device to configure the 40GE port to work in SR4 mode. This configuration ensures that 40GE ports on both ends work in SR4 mode.

    4. Run the commit command to commit the configuration.
  4. (Optional) Disable auto-negotiation on the fabric port.
    1. Run the system-view command to enter the system view.
    2. Run the interface fabric-port port-id command to enter the fabric port view.
    3. Run the leaf negotiation disable command to disable auto-negotiation on the fabric port.

      By default, auto-negotiation is enabled on a fabric port.

      To prevent the switch connected to a fabric port from connecting to the SVF system mistakenly, you can disable auto-negotiation on the fabric port. After auto-negotiation is disabled, the unconfigured switch connected to the fabric port cannot join the SVF system through auto-negotiation. However, the switch configured to work in Leaf mode can still join the SVF system.

    4. Run the commit command to commit the configuration.
  5. (Optional) Configure a load balancing mode for the fabric port.
    1. Run the system-view command to enter the system view.
    2. Run the interface fabric-port port-id command to enter the fabric port view.
    3. Run the load-balance { dst-ip | dst-mac | src-dst-ip | src-dst-mac | src-ip | src-mac | enhanced profile profile-name } command to configure a load balancing mode for the fabric port.

      By default, the load balancing mode for a fabric port is src-dst-ip (load balancing based on the source and destination IP addresses).

      Before specifying the enhanced profile profile-name parameter, you need to run the load-balance profile profile-name command in the system view to create a load balancing profile and run the stack { hash-mode hash-mode-id | universal-id universal-id } * command in the load balancing profile to configure a load balancing mode for the fabric port.

    4. Run the commit command to commit the configuration.
Translation
Download
Updated: 2019-04-03

Document ID: EDOC1100075367

Views: 9784

Downloads: 69

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