User-Defined Pattern Match Syntax

The user-defined pattern match syntax is as follows:

[uda1-data <16-byte-hex>] [uda1-mask1 <16-byte-hex>][uda1-offset <2~110 bytes>][uda2-data <16-byte-hex>] [uda2-mask2 <16-byte-hex>][uda2-offset <2~110 bytes>]

■   Both the udax-data and udax-mask arguments are specified as 16-byte hexadecimal sequences. Specify the pattern in four 4-byte segments separated by hyphens. For example:

0x01234567-89abcdef-01234567-89abcdef

■   Masks specify which bits in the pattern must match. The mask lets you set certain bits in the pattern as wild cards – any values in the masked bit positions will be accepted.
o   Bits masked with binary 1s must match the specified pattern.
o   Bits masked with binary 0s are ignored.
■   You can set up the two global offsets allowed per GigaVUE H Series line card, module, or node or GigaVUE TA Series node at 4-byte boundaries beginning at frame offset 2 and ending at offset 110. The resulting data range for pattern matches is from byte 3 through byte 126.
o   Multiple offsets must be set either equal to one another, or set beyond the boundaries of each other. For example, if uda1-offset starts at byte 2, the uda2-offset can only start either at byte 2 or at any point beginning with byte 18 (which would be the next 4-byte boundary after the 16-byte pattern used at uda1-offset).
o   Offsets are always frame-relative, not data-relative.
o   In many cases, you will be looking for patterns that do not start exactly on a four-byte boundary. To search in these position, you would set an offset at the nearest four-byte boundary and adjust the pattern and mask accordingly.
■   On GigaVUE-TA400, both UDA1, UDA2 support 8-byte data match from offset 0 to 160 on a 4-byte boundary. UDA1 offset value specifies offset from start of ethertype, UDA2 offset value specifies offset from start of L3 header. UDA1, UDA2 offset overlap is allowed. UDA rule having both GigaVUE-TA400 and non GigaVUE-TA400 source ports in a map is not allowed. The data to be matched must be specified with trailing 8-byte zeros. For example to specify 0x54206874 as a match value, enter 00000000-54206874-00000000-00000000.