GigaSMART Rules and Tips

Use on Any GigaSMART-Enabled Node

Maps including GigaSMART operations can be bound to any network port on a GigaSMART-enabled node:

o

Standalone GigaVUE‑HC3 with SMT-HC3-C05 module.

o

Standalone GigaVUE‑HC2 with front or rear GigaSMART-HC0 module.

o

Standalone GigaVUE‑HC1 nodes.

o

Any GigaVUE H Series node operating in a cluster with one of these node types.

Clustered nodes can use maps with GigaSMART operations so long as there is at least one node available in the cluster with GigaSMART capabilities. The GigaSMART group used to power the GigaSMART operation does not need to reside on the same physical chassis as the network or tool ports for the map. Refer to GigaSMART Operations in Clusters for some illustrations of how this works.

Use in Maps with Standard Rule Criteria

Combine GSOPs with map rules carefully to ensure selective application. For example, headers in an IPv4 packet end at a different offset than those in an IPv6 traffic. You can create maps for the following:

o

Identify IPv4 traffic, slice it at a 64-byte offset and forward the results to tool port 5.

o

Identify IPv6 traffic, slice it at an 82-byte offset and forward the results to tool port 6.

GSOPs are applied to all packets matching any rule in the map in which the GSOP is included.

Editing Maps and GSOPs

Maps containing GigaSMART operations (GSOPs) should not be edited. Also GSOPs should not be edited once they are associated with maps.

Note: In Gen3 platform, if there are multiple maps with GSOPs sourcing from the same network ports, when you edit, delete, or reconfigure a map, traffic drop from one map to another maps GSOP will be observed.

Rules for Tunneling Operations

The rules for tunneling operations are as follows:

o

A map including a GigaSMART operation with a tunnel decapsulation component (tunnel-decap) cannot also include a collector rule. The system prevents situations that would violate this rule.

o

GigaSMART operations with a tunnel decapsulation component can only be assigned to GigaSMART groups consisting of a single GigaSMART port.

o

IP interfaces cannot be shared with map-passalls, tool-mirrors, port-pairs, or other regular maps.

o

For devices involved in tunneling using GMIP. the recommendation is that they run the same software version on both sides of the tunnel (encapsulating/decapsulating).

Combine Multiple Components in a Single Operation

You can combine multiple GigaSMART components into a single operation. For example, you could set up a single GigaSMART operation that masks a packet, strips its VLAN header, and applies a trailer.

Note: With the exception of slicing and masking, most GigaSMART components can be combined in a single operation. Slicing and masking can be combined with other components but not with each other. Refer to How to Combine GigaSMART Operations for details on the combinations of GigaSMART operations.

Note: The [trailer <remove>] argument cannot combined with others – it must be used by itself. Refer to Remove GigaSMART Trailers for details.

Note: NetFlow can only be combined with de-duplication and with APF (using second level maps).

GigaVUE‑HC3 Nodes with Multiple GigaSMART Modules

The GigaVUE‑HC3 chassis supports up to four GigaSMART SMT-HC3-C05 modules. Each module has two GigaSMART engine ports. Each GigaSMART engine port can process packets at up to 100Gb.