For intermittent usage scenarios such as on-demand packet capture and scheduled monitoring, users can flexibly start and stop mirror sessions and are billed only when in use, effectively controlling idle costs.

Instructions

After a mirror session is stopped, traffic replication is immediately interrupted. Applications that rely on the mirrored traffic—such as IDS, audit systems, and packet capture analysis—will stop receiving data. Please confirm before proceeding.

A stopped mirror session still supports modifying attributes such as session name, description, mirror site, mirror target, mirror filter, VNI, and priority. After modification, the session remains in the stopped status.

The suspension status caused by account arrears is independent of the user-initiated stopped status. Once arrears are cleared, the session will automatically return to the started/stopped status set by the user before the arrears.

Start a traffic mirror session

In the left-side navigation pane, select Traffic Mirror > Mirror Session.

Single traffic mirror session

Click Start to the right of the target Traffic Mirror Session.

Click Save to complete the action.

Multiple traffic mirror sessions

Check multiple traffic mirror sessions, then click Batch start.

Click Save to complete the action.

Stop a traffic mirror session

In the left-side navigation pane, select Traffic Mirror > Mirror Session.

Single traffic mirror session

Click Stop to the right of the target Traffic Mirror Session.

Click Save to complete the action.

Multiple traffic mirror sessions

Select multiple Traffic Mirror Sessions and click Batch stop.

Click Save to complete the action.