Configuring Local Flow Mirroring Based on the Option 82 Information of Access Users
This section describes how to configure local flow mirroring based on the Option 82 information of access users, so that user packets that carry specified Option 82 information are copied to the observing port for analysis.
Usage Scenario
When more precise analysis of user traffic is required, you can combine flow mirroring based on the Option 82 information with traffic classification. In this way, only the packets that meet specified filtering conditions are copied to the observing port for analysis, improving analysis efficiency.
No particular sequence is required for configuring an observing port and mirrored port, defining a mirroring traffic policy, and applying the traffic policy globally. All these configurations, however, must be complete before flow mirroring is implemented. If you no longer use flow mirroring, disable it to avoid affecting user services.
- Configuring an Observing Port
- An observing port copies the traffic on the mirroring port to a packet analyzer. To prevent adverse impacts on running services, do not use the observing port as a service port.
- Specifying an Observing Port
- This section describes how to specify an observing port to associate the observing and mirrored ports.
- Defining a Mirroring Traffic Policy and Applying It Globally
- This section describes how to use a traffic classifier to define the traffic to be mirrored, specify flow mirroring for a traffic behavior, define a traffic policy that associates the traffic classifier with the traffic behavior, and apply the traffic policy globally.
- Checking the Configurations
- After local flow mirroring is configured, you can check configurations about the traffic classifier, traffic behavior, traffic policy, and observing port.
- Disabling Flow Mirroring
- Flow mirroring needs to be disabled if it is no longer used; otherwise, user services are affected.