Licensing Requirements and Limitations for VCMP

Involved Network Elements

Other network elements are not required.

Licensing Requirements

VCMP is a basic feature of a switch and is not under license control.

Version Requirements

To know details about software mappings, see Hardware Query Tool.

Feature Limitations

• XGE interfaces connected to the ACU2, ET1D2IPS0S00, ET1D2FW00S00, ET1D2FW00S01, or ET1D2FW00S02 card do not support VCMP.

• VCMP can only help the network administrator synchronize VLAN information but not dynamically assign interfaces to VLANs. VCMP is often used with LNP to simplify user configurations. For details about LNP, see "LNP" in "VLAN Configuration" in the Configuration Guide - Ethernet Switching of the corresponding product version.

• VCMP packets can be only transmitted in VLAN 1. By default, all interfaces join VLAN 1. To prevent loops, deploy a loop prevention protocol such as STP in addition to VCMP. After STP is deployed, blocked interfaces cannot receive or send VCMP packets.

• By default, a switch is a VCMP client. If a switch is upgraded from a version that does not support VCMP to a VCMP-supporting version, the VCMP role is Silent by default. In addition, to ensure that the switch's VCMP role is consistent before and after the upgrade, the switch by default delivers the undo bpdu mac-address 0118-8255-5555 command to process VCMP packets as data packets. To enable VCMP, see "Configuring VCMP" in "VCMP Configuration" in the Configuration Guide – Ethernet Switching Configuration Guide of the corresponding product version.

• VCMP synchronizes only the VLAN ID in the current version.

• One switch can join only one VCMP domain, and only one VCMP server exists in a VCMP domain.

• If the VCMP domain authentication password is set, ensure that the VCMP server and clients use the same VCMP domain authentication password.

• If VLANs created or deleted on the VCMP server are the control VLANs of the Ethernet Ring Protection Switch (ERPS), Rapid Ring Protection Protocol (RRPP), Smart Ethernet Protocol (SEP), or Smart link, or reserved VLANs of stack, a VCMP client does not create or delete the VLANs.

• If the Generic VLAN Registration Protocol (GVRP) has been enabled, the VCMP role can be only the transparent or silent switch. If the VCMP role is set to client or server, do not use GVRP.

• Termination sub-interfaces cannot be configured on a VCMP client. For details on how to configure a termination sub-interface, see "Configuring a Sub-interface" in "Logical Interface Configuration" in the Configuration Guide - Interface Management of the corresponding product version.

• A VCMP client cannot be configured with the VLAN switch function. Before changing a VCMP server configured with the VLAN switch function to a VCMP client, delete the VLAN switch configuration.

• After a VLAN is deleted on the VCMP server, VCMP clients delete the VLAN but do not delete configurations in the VLAN. In addition, the vlan vlan-id configuration command is generated in the configuration file, and the configurations in the deleted VLAN specified by vlan-id are moved to the VLAN configuration view.
• When the device used as a VCMP client that connects to a VCMP server restarts, the VLAN configuration before the restart takes effect. To make the saved VLAN configuration take effect, use one of the following methods to delete the vlan.dat file and then restart the device:
  • Run the vcmp role { server | silent | transparent } command to change the device role to a non-client.
  • Run the startup saved-configuration configuration-file command to configure a new configuration file. Ensure that the name of the new configuration file is different from that of the current configuration file.
  • Run the reset saved-configuration command to clear the saved configuration file. This command will clear all the configuration.

  When the value of Server ID in the display vcmp status command output is not empty, the device used as a VCMP client has been connected to a VCMP server.