Configure Prefiltering

For prefiltering the traffic, GigaVUE‑FM enables you to create a prefiltering policy template and apply it to a Monitoring Session,

Considerations

  • You can create and reuse a policy template across multiple monitoring sessions.

  • Each monitoring session supports up to 16 prefiltering rules.

  • You can edit the policy template during monitoring session configuration to customize rules and filter values.

  • GigaVUE‑FM does not save changes made to the template during monitoring session edits. These changes apply only to that specific session.

Rules and Notes

■   Prefiltering is supported on UCT-V for Windows systems and Linux systems running Kernel version 4.18 or later.
■   Prefiltering is supported for both Linux and Windows UCT-Vs .
■   For single monitoring session only one prefiltering policy is applicable. All UCT-Vs in that monitoring sessions are configured with respective prefiltering policy .
■   For multiple monitoring session using the same agent to acquire the traffic, if a monitoring session uses a prefilter and the other monitoring session does not use a prefilter, then you cannot apply the prefiltering policy. The policy is set to PassAll and prefiltering is not performed.

Create Prefiltering Policy Template

GigaVUE‑FM allows you to create a prefiltering policy template with one or more rules. You can configure a rule with one or more filters. A single monitoring session supports a maximum of 16 rules.

To create a prefiltering policy template,

1. Go to Traffic > Resources > Prefiltering and select UCT-V.

2. Select New.

3. In the Template Name field, enter the name of the template,

4. In the Rule Name field, enter the name of a rule.

5. Select one of the following options:

■   Pass: Allows the traffic.
■   Drop: Blocks the traffic..

Note:  If no prefilter rules are defined, traffic is implicitly allowed. When rules are defined, an implicit drop rule applies. Traffic that does not match any specified rule is dropped.

6. Select one of the following options:

■   Bi-Directional: Allows the traffic in both directions of the flow. A single Bi-direction rule requires 1 Ingress and 1 Egress rule.
■   Ingress: Filters incoming traffic.
■   Egress: Filters outgoing traffic.

Note:  When using loopback interface in Linux UCT-V, you can use only Bi-directional.

7. Select a priority value from 1-8.

  • 1: Select the value as 1 to pass or drop a rule in top priority.

  • 2-8 Select the value as 2, 3, 4 to 8, where 8 indicates a rule with the least priority.

    Drop rules are added first based on the priority and then pass rules are added.

8. Select one of the following options as Filter Type:

■   L3
■   L4

9. Select one of the following options Filter Name:

■   ip4Src
■   ip4Dst
■   ip6Src
■   ip6Dst
■   Proto: Applies toboth ipv4 and ipv6.

10. Select one of the following options for Filter Relation:

■   Not Equal to
■   Equal to

11. In the Value field, enter the source or destination port.

12. Select Save.

Note:  Select + to add more rules or filters or select - to remove a rule or a filter.

To enable prefiltering for a Monitoring Session, refer to Configure Monitoring Session Options (AWS)Configure Monitoring Session Options (Azure)