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).
Stack Feature Limitations

Stack Feature Limitations

Stack Setup Precautions

When setting up a stack, pay attention to the following points:
  • Optical or copper modules that are certified for Huawei Ethernet switches must be used. If high-speed cables or AOC cables are used, you must purchase cables from Huawei.

    Optical or copper modules that are not certified for Huawei Ethernet switches or cables that are not purchased from Huawei cannot ensure transmission reliability and may affect service stability. Huawei is not liable for any problem caused by the use of optical or copper modules that are not certified for Huawei Ethernet switches, or cables not purchased from Huawei, and will not fix such problems.

  • When connecting stack members through stack cables, ensure that the stack members are directly connected.

  • It is recommended that you configure DAD for a stack to minimize the impact of a stack split on services.

  • After a stack is set up, you must run the save command to save the stack configuration.

  • When a stack is running stably, do not shut down stack ports and DAD-configured ports. Otherwise, the stack will split and service traffic cannot be forwarded.
  • To ensure high network reliability, it is recommended that a stack connect to upstream and downstream devices using an inter-device Eth-Trunk (dual-homing networking).

  • Before setting up a stack, you are advised to load the same software version and patch version on member switches.

  • It is recommended that you use two or more links to set up a stack. If only one link is used to set up a stack (this method is not recommended), it is recommended that you run the carrier down-hold-time interval command on stack member ports to configure the delay after which the port Down state is reported. This configuration prevents the stack from becoming unstable because of intermittent port disconnection.

  • You are advised to preferentially use the MPU connection mode. This mode separates management links from forwarding links, ensuring high reliability of the stack system.

  • Switches using different board interoperability modes cannot set up a stack. To view the board interoperability mode on a switch, run the display forward capability command.

  • Before the master and standby switches complete batch backup, do not shut down or remove stack links. Otherwise, the standby switch may restart.

    To check the batch backup status between the master and standby switches, run the display switchover state command.

  • Local stack member ports cannot connect to remote common service ports. Otherwise, traffic forwarding may fail or switches restart unexpectedly. Ports on both ends must be configured either as stack member ports or as service ports.

  • To prevent stack packet forwarding from being affected, you are advised not to configure the flow-control command on stack member ports.

  • When traffic control is configured in a stack and traffic is forwarded between member switches in the stack, traffic control does not take effect because stack ports do not support the flow-control command.

  • When you change the system software for a stack that is set up in LPU connection mode and reboot the system, do not close the terminal window before execution of the reboot command is complete. Otherwise, the standby switch in the stack will restart repeatedly.
  • Ports on the CE-FWA/CE-IPSA card cannot be used for stack connections.
  • In V100R006C00 or later versions, after service ports are configured as stack member ports, the port crc-statistics trigger error-down command is automatically configured on these member ports. After a version upgrade to V100R006C00 or later, the port crc-statistics trigger error-down command configuration is automatically added to these member ports.

    In versions earlier than V200R002C50, after stack member ports are restored as common service ports, the port crc-statistics trigger error-down command configuration is not automatically cleared.

    In V200R002C50 and later versions, if the port crc-statistics trigger error-down command is not configured before service ports are configured as stack member ports, this command configuration is automatically cleared after stack member ports are restored as common service ports. If this command has been configured before service ports are configured as stack member ports, this command configuration is not automatically cleared after stack member ports are restored as service ports.

  • When the protocol of a stack member port is Down, the port will not enter the Error-Down state due to CRC error packets.

  • On the CE12800E (equipped with ED-E, EG-E, and EGA-E series cards), only known unicast and multicast packet statistics on stack member ports are collected, and unknown unicast packet statistics are collected as multicast packet statistics.

  • When stack and multiple other services need to be configured together, some services may fail to be delivered because of insufficient ACL resources. For services that can be configured together with stack, see "Using CSS/M-LAG with Other Services" in CloudEngine 12800, 12800E, 8800, 7800, 6800, and 5800 Series Switches ACL Technical Topics.

Stack Upgrade Precautions

When upgrading a stack, pay attention to the following points:
  • Do not remove or reinstall cards, optical modules or power cycle the switch during a software upgrade.

  • Ensure network stability and do not perform other service configurations on the network during a software upgrade.

  • If there are MPUs, LPUs, or SFUs on the switch but these cards are not registered, the fast stack upgrade cannot be performed.
  • During a fast stack upgrade, to shorten traffic interruptions, ensure that upstream and downstream devices are dual-homed to stacked switches using Eth-Trunk.

  • If 40GE high-speed cables are used to connect stack member switches, you cannot fast upgrade switches to V100R003C00 or a later version.

  • When 40GE QSFP+ AOC cables are used for stack connections, the stack cannot be upgraded using fast upgraded to V100R005C10 or a later version.

  • If the current stack connection mode is different from the stack connection mode for the next startup, the stack fast upgrade cannot be performed. Otherwise, a version rollback occurs.

  • In a stack, the current stack configuration must be consistent with the stack configuration for next startup; otherwise, you cannot perform an ISSU. The stack configuration includes the stack domain ID, stack member ID, and stack connection mode.

  • In a stack established in MPU connection mode, if no forwarding link is available, the stack cannot be upgraded fast.

  • During the fast upgrade of a stack, the SFU reset due to heartbeat loss is a normal situation and does not affect services.

  • You are advised to configure a backup IP address for the stack management interface before a fast upgrade. This configuration prevents a failure to manage member switches when the stack fails the fast upgrade and splits.

  • In a stack set up in LPU connection mode, after an upgrade to V200R001C00 or later, installing FD/FD1/FDA/FG/FG1/SD LPUs on the switch will decrease the inter-chip forwarding capability of these LPUs. To restore the inter-chip forwarding capability of these LPUs, replace existing SFUs with SFUFs or SFUGs and then restart the stack.

Feature Support in a Stack

In a stack, support for most features except the following features is the same as support on a standalone switch. Table 1-4 shows the difference in support for some features.
Table 1-4 Feature support in a stack

Feature

Feature Support in a Stack

Mirroring

In a stack system of the following cards, inter-chassis mirroring is not supported: CE-L48GT-EA, CE-L48GT-EC, CE-L48GS-EA, CE-L48GS-EC, CE-L24XS-BA, CE-L24XS-EA, CE-L48XS-BA, CE-L48XS-EA, CE-L24LQ-EA, CE-L48GT-ED, CE-L48GS-ED, CE-L12XS-ED, CE-L24XS-EC, CE-L24XS-ED, CE-L48XT-EC, CE-L48XS-EC, CE-L48XS-ED, CE-L48XS-EF, CE-L02LQ-EC, CE-L06LQ-EC, CE-L12LQ-EF, CE-L24LQ-EC, CE-L24LQ-EC1, CE-L36LQ-EG, CE-L04CF-EC, CE-L04CF-EF, CE-L08CC-EC, and CE-L12CF-EG. If inter-chassis mirroring is configured, mirrored traffic cannot be forwarded.

In a stack system of other series cards, inter-chassis mirroring is supported.

Port split

If a 100GE or 40GE optical port has been configured as a stack member port, it cannot be split.

Layer 2 port isolation

Inter-chassis Layer 2 port isolation in a stack is supported since V100R003C10.

MPLS

MPLS is not supported in a stack.

Translation
Download
Updated: 2019-03-21

Document ID: EDOC1000166610

Views: 44088

Downloads: 131

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next