Experience case of reclaiming deployed mapping rules due to modifying interface or device level binding relationships under VLAN-VXLAN/QinQ mapping in ADDC scenario

1. On the VLAN-VXLAN/QinQ mapping interface, modify the binding relationship at the interface or device level, such as adding an interface binding operation in the mapping rule. After the modification is completed, clicking Apply will disrupt all services associated with this mapping rule, and relevant service configurations will be reclaimed.

1. The related operations are for normal business expansion or modification, with correct steps, adding or adjusting mapping configurations in the relevant mapping settings.

2. After modifying the click application, it was found that the VLAN-VXLAN mapping rule range changed to 0. Click to view existing mapping rules have disappeared.

3. Check the controller (CTL) operation log. At the corresponding time point, there was an update operation for VLAN-VXLAN mapping. The log details show that the operation was to update the mapping table, with the table name being addc7.1. However, the VLAN-VXLAN mappings parameter is empty, which corresponds to the empty range in the mapping rule interface.

Updated VLAN-VXLAN mapping table: ID: [4231341d-212a-4dff-8d03-e3a1ef21f36f] Name:[addc7.1] Description:[null] Origin:[null] applyScope:[interface] dataSource:[DEFAULT] VLAN-VXLAN mappings: [ ]

4. This issue is a problem with the controller (CTL) software product.On the VLAN-VXLAN/QinQ mapping list page, selecting apply to device or apply to interface and clicking the apply or acknowledge button will trigger a request to modify the mapping scope. The data source for the mapping scope depends on the return value of the GET /nem/v1.0/vlan_domains?id={uuid} interface. In specific scenarios such as high network latency or slow browser speed, when clicking the apply or acknowledge button, the aforementioned GET request may not return in time, resulting in an empty submitted mapping scope. This causes the mapping table to be deleted, the vsi and ac configuration on the device to be reclaimed, and impacts services. For details, refer to the technical bulletinTechnical Bulletin on the Impact of Low-Probability Deletion of VLAN-VXLAN or QinQ Mapping Rules Triggered by VCFC & SeerEngine-DC Configuration Device or Interface Binding. If the first three steps in the case analysis process are met, it is considered that the relevant technical bulletin has been triggered.

1. If the mistakenly deleted mapping rules are known, reconfigure the lost mapping rules on the controller (CTL) after the failure to urgently recovery the service.

2. If the mistakenly deleted mapping rules are unknown, use the device configuration and controller (CTL) configuration from when the service was normal to perform a configuration rollback for urgent recovery of the service.

3. For related workarounds and solutions, refer to the technical bulletin: Technical Bulletin on VCFC & SeerEngine-DC Configuration Device or Interface Binding VLAN-VXLAN or QinQ Mapping Table Low Probability Deletion of Mapping Rules Causing Service Impact