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

CloudEngine 12800, 12800E, 8800, 7800, 6800, and 5800 Series Switches M-LAG Best Practices

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).
Constraints When M-LAG Is Used with Other Features

Constraints When M-LAG Is Used with Other Features

The service features supported by the M-LAG dual-active system are similar to those supported by the non-M-LAG devices. Table 3-1 lists the constraints when M-LAG is used with other features.

Table 3-1 Constraints when M-LAG is used with other features

Feature

Precaution

VBST

M-LAG and VBST cannot be configured together.

GVRP

M-LAG in the Eth-Trunk interface view cannot be used with GVRP.

DHCP

  • The two devices that constitute an M-LAG cannot be configured with DHCP snooping.
  • The DHCP relay function must be configured on the two devices that constitute an M-LAG.
  • The DHCP server function must be configured on the two devices that constitute an M-LAG, and addresses in the address pools of the two devices cannot overlap.

IP unicast routing

The M-LAG device and connected device cannot establish a routing neighbor relationship through an M-LAG member interface.

IP multicast

  • In V100R005C10 and earlier versions, the two devices that constitute an M-LAG cannot be configured with IPv4 Layer 3 multicast.
  • The two devices that constitute an M-LAG cannot be configured with bidirectional PIM (IPv4). The two devices that constitute an M-LAG cannot be configured with IPv6 multicast.
  • On the two devices that constitute an M-LAG, a physical interface that is configured as a Layer 3 interface using the undo portswitch command does not support Layer 3 multicast.

FCoE

M-LAG cannot be used on the device that is configured with the FSB and FCF or NPV.

IP source guard (IPSG)

The two devices that constitute an M-LAG cannot be configured with IPSG.

VXLAN

M-LAG and a Layer 2 sub-interface with QinQ encapsulation cannot be configured together.

Translation
Download
Updated: 2018-07-02

Document ID: EDOC1000137639

Views: 37023

Downloads: 1487

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