Flow Mapping® FAQ
This section answers frequently asked questions by users migrating to the Flow Mapping® model.
How Many Map Rules are Supported?
The maximum number of map rules supported per line card or standalone node are shown in Maximum Number of Nodes and Map Rules Supported in a Cluster.
|
Node Type |
Maximum Combined Rules for Default Template Without a License |
Maximum with Flexible Filter Templates Without a License |
Maximum with Advanced Features License for Flexible Filter Templates |
|
GigaVUE-HCT Node |
6k (6142) |
6k (6142) |
N/A |
|
GigaVUE-HCT Module |
3k (3071) |
3k (3071) |
N/A |
|
GigaVUE‑HC1-Plus Node |
6k (6142) |
36k (36862) |
N/A |
|
GigaVUE‑HC3 Node |
4K (4096) |
24K (24576) |
N/A |
| GigaVUE‑HC3 Module | 1K (1024) | 6K (6144) | N/A |
|
GigaVUE‑HC1 |
16K (16383) |
16K (16383) |
N/A |
|
GigaVUE TA Series |
256 |
The Flexible Filter Templates are available only for GigaVUE-TA100 and GigaVUE-TA200 nodes. |
The Advanced Features License is available only for the GigaVUE-TA Series. The extended max rule limit varies based on the GigaVUE-TA Series node. |
|
GigaVUE‑TA25 |
256 |
256 |
18k (18431) rules per node |
|
GigaVUE‑TA25E |
256 |
256 |
36k (36862) rules per node |
|
GigaVUE-TA100 |
256 |
256 |
6K (6144) per pseudo-slot with Flexible Filter Template and Advanced Feature License. 1K (1024) per pseudo-slot with only Advanced Feature License. |
|
GigaVUE‑TA200 |
256 |
256 |
6K (6144) per pseudo-slot with Flexible Filter Template and Advanced Feature License. 1K (1024) per pseudo-slot with only Advanced Feature License. |
|
GigaVUE‑TA200E |
256 |
256 |
6K (6144) per pseudo-slot with Flexible Filter Template and Advanced Feature License. 1K (1024) per pseudo-slot with only Advanced Feature License. |
|
GigaVUE‑TA400 |
256 |
256 |
88K (22528) per pseudo-slot with Flexible Filter Template and Advanced Feature License. 40K (10299) per pseudo-slot with only Advanced Feature License. |
The limit for GigaVUE TA Series standalone nodes is 256 combined pass/drop rules but is up to 2048 with the Advanced Features License installed.
Refer to Manage Map Rule Resources for managing map rules.
The maximum number of nodes and map rules supported when in a cluster is as follows:
The maximum number of map rules supported in a cluster apply to all nodes in the cluster including GigaVUE HC Series nodes: GigaVUE‑HC3, GigaVUE‑HC1, GigaVUE‑HC1-Plus, GigaVUE-HCT and GigaVUE TA Series nodes: GigaVUE‑TA25, GigaVUE‑TA25E, GigaVUE-TA100, GigaVUE‑TA200, GigaVUE‑TA200E, and GigaVUE‑TA400 including Certified Traffic Aggregation White Box (white box).
How Many Rules Can Each Map Have?
The maximum number of rules per map is 4K (4096), except on products that only support a total of 2K map rules. GigaVUE‑HC3 supports 6K rules per map. Refer to Rules Per Map.
|
Node Type |
Rules per map |
|
GigaVUE-HCT Node |
4K |
|
GigaVUE-HCT Module |
4K |
|
GigaVUE‑HC1-Plus Node |
4K |
|
GigaVUE‑HC1-Plus Module |
4K |
|
GigaVUE‑HC3 Node |
6K |
| GigaVUE‑HC3 Module | 6K |
|
GigaVUE‑HC1 |
4K |
|
GigaVUE TA Series |
4K |
|
GigaVUE‑TA25 |
4K |
|
GigaVUE‑TA25E |
4K |
|
GigaVUE-TA100 |
4K |
|
GigaVUE‑TA200 |
4K |
|
GigaVUE‑TA200E |
4K |
|
GigaVUE‑TA400 |
4K |
How Many Maps Can Run at Once?
The maximum number of maps that can run is only limited by the total number of rules used by the maps.
What Criteria can be Filtered in Q-in-Q Packets?
Maps on GigaVUE nodes can match Layer 3/Layer 4 criteria in packets using Q-in-Q with up to two tags. For more information refer to How to Handle Q-in-Q Packets in Maps.
How Many Maps Can Share a Network Port?
There is no limit to the number of maps that can share a network port.
How Many Network Ports and Tool Ports Can Be in a Map?
If the ports are not in a GigaStream, the number of individual map ports in the Source or Destination field of a map is limited to 64 on all GigaVUE HC Series nodes. The individual ports can be any of the following port types: network or tool.
On GigaVUE‑HC3, if the ports are in a GigaStream, the limit is 95.
Are Port-Filters Supported?
Yes.
Egress port-filters (tool, hybrid, circuit, and inline network), are less efficient and scalable than flow maps, but they do provide a convenient way to narrow down the traffic seen by the tools/GigaVUE® HC Series nodes without having to change an entire map. Refer to Port Filters for details.
Each GigaVUE‑HC3 module, or GigaVUE-HB1 node supports 100 combined egress port-filters. A single filter applied to multiple tool ports counts multiple times against the 100-filter limit.
In the the GigaVUE‑HC1 or GigaVUE‑HC3 node, the limit is 400 filters.
The GigaVUE TA Series can only support 20 egress port-filters. When the GigaVUE-TA100 or GigaVUE-TA200 , GigaVUE‑TA200E are in a cluster, they can support 400 filters. GigaVUE-TA25, GigaVUE‑TA25E supports 20 port filters by default and up to 100 port filters with advanced feature license.
Does Flow Mapping® Support Passalls?
Yes.
Flow Mapping® supports passalls with the following:
| The map Subtype Pass All option for network to tool port passalls. |
| A tool-mirror connection between to tool ports. The Tool Mirrors page replaces the tool-to-tool port passalls. To create a Tool Mirror, select Ports > Tool Mirrors to go to the Tool Mirror page shown in 4. |
| 4 | Tool Mirror Page |
Does Flow Mapping® Support port-pairs?
Yes.
Select Ports > Port Pairs to go to the Port Pairs page shown in 5. For more information about port pairs and details on configuring two ports as an inline TAP, refer to Port Pairs.
| 5 | Creating Port Pairs |
Does Flow Mapping® Support UDA Pattern Matches?
Yes.
Pattern match rules are still supported in map rules. They can be used in both pass rules and drop rules. Refer to Work with User-Defined Pattern Match Rules for details.
Are Maps Supported Across Nodes in a Cluster?
Yes.
Clusters of GigaVUE nodes operate as a unified fabric. Use the standard box ID/slot ID/port ID syntax to create packet distribution, just as on a standalone node. Maps can have network ports and tool ports on different physical nodes within the cluster.
Similarly, a map does not need to keep its network and tool ports on the same physical node in order to take advantage of GigaSMART operations – a GigaVUE TA Series node in a cluster can take advantage of the GigaSMART processing available on a GigaVUE‑HC3 module, or GigaVUE‑HC1 node elsewhere in the same cluster.
Can a GigaStream Act as a Shared Collector?
Yes.
Multiple individual ports for a Shared Collector can be setup or a GigaStream tool group. Refer to About Shared Collectors for details.
What Are the GigaStream Maximums?
The number of GigaStream per line card, module, or node varies by product. Refer to GigaStream Rules and Maximums for the details.
DoesGigaVUE‑FM Provide the Same Features as the GigaVUE‑OS CLI?
The GigaVUE‑FM provides all of the mapping features of the CLI in an intuitive and highly-usable setting. The map creation wizard speeds map creation.
What order are the map rules displayed in "show running config"?
You can view the rules within a map, displayed in the order created.
