Manage Map Rule Resources

The resources available on a GigaVUE HC Series line card or node changes depending on the combination of criteria in place on the line card or node as a whole. In general, adding or removing MAC address, UDA pattern match, or IPv6 criteria in the map rules bound to a line card or node changes the type of filter template used on the line card or node. This can result in a brief interruption of traffic as the new template is applied.

Template Groups

The template groups are listed sequentially from least resource-intensive to most resource-intensive:

■

IPv4 Only – This is the default filter template, including all IPv4 arguments without any MAC addresses, UDA data patterns, or IPv6 arguments. This template can support the IPv4 and related filter criteria, including VLAN tags, source leader in a bidirectional clock relationship (formerly master)/destination ports, protocol criteria, and so on.

■

IPv4 and MAC Addresses – This template combines MAC address criteria with the standard IPv4-related criteria. When MAC address criteria are in use, map rule resources are decreased.

■

IPv4 and Single UDA Data Pattern – This template combines one of the two available UDA data patterns with the standard IPv4-related criteria. Using a single UDA criteria does not affect the total number of drop map rules available, but it does decrease the number of pass map rules available.

■

Both UDA Data Patterns – This template uses both UDA data patterns but removes the ipv4 argument. Drop map rule availability is not affected by adding a second UDA data pattern, but pass map rules are decreased again from what was available when only a single UDA was used.

■

IPv6 Arguments – This template adds the use of the IPv6 argument. IPv6 criteria are resource-intensive, significantly decreasing both drop and pass map rule capacity, as shown in the following table. Note also the changes in available criteria and available resources.

The map rule criteria available in each filter template (or “group”) is shown in the following table.

Table 1: Map Rule Criteria for Default Templates

Rules - Pass and Drop	IPv4	IPv4 + MAC	IPv4 + UDA	UDA	IPv6
IPv4	ü	ü	ü		ü
IPv6					ü
MAC		ü
UDA1			ü	ü
UDA2				ü
VLAN	ü	ü	ü	ü	ü
Inner VLAN	ü	ü	ü	ü	ü
L4 Port dst and src	ü	ü	ü	ü	ü
Ethertype		ü	ü
IP Ver	ü	ü	ü	ü	ü
Protocol	ü	ü	ü	ü	ü
DSCP	ü	ü	ü	ü	ü
ToS	ü	ü	ü	ü	ü
TCP Ctl	ü	ü	ü	ü	ü
IP Frag	ü	ü	ü	ü	ü
TTL	ü	ü	ü	ü	ü
IPv6 Flow Label		ü	ü

The number of rule entries in a cluster is shown in the following table.

Table 2: Rule Entries

# Rule Entries	IPv4	IPv4 + MAC	IPv4 + UDA	UDA	IPv6
GigaVUE‑HC3	4096(1024 per slot)	4096(1024 per slot)	4096(1024 per slot)	4096(1024 per slot)	4096(1024 per slot)
GigaVUE‑HC2 CCv1 Node	4096	2048	2048	2048	2048
GigaVUE‑HC2 CCv2 Node	16384	8192	8192	8192	8192
GigaVUE‑HC1 Node	16384	8192	8192	8192	8192
GigaVUE-TA10/TA40 Node	2048	1024	1024	512	512
GigaVUE-TA100 Node	1024	1024	1024	1024	1024
GigaVUE-TA200 Node	1024	1024	1024	1024	1024
GigaVUE‑TA25	3072	3072	3072	3072	3072

Note:  In addition, you can use flexible filter templates on GigaVUE‑HC3 to support up to 6K rules per slot. On GigaVUE-TA100 and GigaVUE-TA200 they support up to 6K rules per pseudo-slot, or 24K rules per node. GigaVUE‑TA25 supports up to 18K rules per node. Refer to Flexible Filter Templates for details.

Note:  The above table lists the values for the Default template with license.