Introduction

You can delete an unused traffic mirroring policy to release resources such as the mirror source and mirror destination. This operation applies to scenarios such as service decommissioning or changes in mirroring requirements, preventing unused policies from consuming system resources.

Constraints and Restrictions

• If the mirror source or mirror destination of a traffic mirroring policy is currently used by other services (such as running VMs or edge-connected interfaces carrying business traffic), the policy can be deleted without affecting the services.

• Traffic mirroring policies associated with VM migration tasks can be deleted only after the associated tasks are terminated or complete.

• If the mirror source and mirror destination of a traffic mirroring policy belong to different resource pools, ensure that the resource pools are not associated with data sync tasks before deleting the traffic mirroring policy.

• Traffic mirroring policies that are in use (for example, when the mirror destination is receiving traffic and is associated with an auditing task) cannot be deleted. Terminate the associated tasks before deletion.

Prerequisites

• You have logged in to SCP using the admin account.

• The target traffic mirroring policy exists and is in Disabled status. (Disabling the policy before deletion to avoid unexpected traffic interruption.)

• The target traffic mirroring policy is not associated with any ongoing tasks (such as VM migration and traffic auditing tasks).

• Confirm that no services rely on traffic mirrored based on the policy to be deleted for auditing, monitoring, or troubleshooting.

Precautions

• Before you delete a policy, back up the policy configuration (by taking screenshots or recording parameters) in case policy recreation is needed later.

• If the policy is used to mirror critical business traffic, notify relevant O&M personnel before deletion to avoid impacts on auditing or monitoring activities.

• After a cross-resource pool traffic mirroring policy is deleted, check whether other policies within the communication domain are normal to prevent cascading effects.

• A deleted policy cannot be restored. If the policy is deleted by mistake, you need to recreate it. Therefore, double-check the policy name and use before deletion.

Steps

Step 1.Log in to SCP and go to Networking > Traffic Mirroring.

Step 2.(Optional) If the target policy is in Enabled status, click Edit in the Operation column. In the Edit Traffic Monitoring Policy pop-up window, deselect Enabled for Status and click OK to save the change.

Step 3.Find the target policy in the policy list and click Delete (or choose More > Delete) in the Operation column.

Step 4.Confirm the name of the policy to be deleted and click OK in the confirmation pop-up window.

Step 5.The system will automatically delete the policy. If the policy no longer appears in the list after the page is refreshed, the deletion is successful.

Step 6.(Optional) If a traffic mirroring policy between physical interfaces is deleted, you can clear related isolation configuration on the physical switch to release network resources.