Skip to content

Commit 70ea42e

Browse files
committed
copy edit
1 parent b74f54d commit 70ea42e

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

articles/private-5g-core/data-plane-packet-capture.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,10 +55,11 @@ To perform packet capture using the command line, you must:
5555
1. Return to the **Packet Capture** view.
5656
1. Select **Start packet capture**.
5757
1. Fill in the details on the **Start packet capture** pane and select **Create**.
58-
1. The page will refresh every few seconds until the packet capture has completed. You can also use the **Refresh** button to refresh the page. If you want to stop the packet capture early, select **Stop packet capture**.
5958

6059
The **Maximum bytes per session** limit is applied per node. In highly available (HA) deployments, it's likely that the packet capture will reach this limit and complete on one node before the other, so a packet capture will still be running when the first has completed. You should stop any running packet captures before starting a new one.
6160

61+
1. The page will refresh every few seconds until the packet capture has completed. You can also use the **Refresh** button to refresh the page. If you want to stop the packet capture early, select **Stop packet capture**.
62+
6263
1. Once the packet capture has completed, the AP5GC online service will save the output at the provided storage account URL.
6364

6465
In HA deployments, two packet capture files will be uploaded, one for each node. The files will be labelled with a `0` or a `1`, corresponding to the `core-mec-dp-0` or `core-mec-dp-1` pod. If one packet capture fails, the status page will show an error, but the successful capture results will upload as normal.

0 commit comments

Comments
 (0)