CC Configuration
Except on the first page, right running head:
Heading1 or Heading1NewPage text (automatic)
479
Alcatel-Lucent
Beta Beta
OmniAccess 5740 Unified Services Gateway CLI Configuration Guide
TO CONFIGURE A MATCH-LIST
EXAMPLE
ALU(config)# match-list test
ALU(config-match-list-test)#
RULES WITHIN MATCH-LISTS
Rules are the main classification component, and are constructed using a specific
syntax that may reference other elements and/or lists as part of the rule. A single
rule roughly corresponds to one line of an match-list without the permit/deny
action. Rules indicate specific fields of packets that must match in order for the
rule itself to match. A group of rules is termed as a ruleset, which forms a
match-list.
Rulesets are the collection of rules that are grouped into a single classification
and become the objects that different features refer when binding classification to
their parameters. Apart from this, these rules are applied for all flows irrespective
of the interfaces. Each rule is differentiated by a line number.
In general, the following have to be considered before configuring a rule:
• The Source / Destination (from / to) order of the fields must configure a rule.
• The fields specified in the rule must all match for the rule to be matched, so the
components of the rule can be considered to have a boolean AND function
applied.
Note: A match-list matches if any of the rule matches.
• In the situation where a list is used, any of the members of the list may match, but
at least one must match before that field is considered a match for that rule.
• The “service” keyword in TCP and UDP protocols refer to the destination port.
Currently, the ‘service’ keyword in TCP or UDP can have only the following
values:
ftp-data|ftp|ssh|telnet|smtp|dns|tftp|http|pop2|pop3|imap|
snmp|snmptrap|bgp
Command (in CM) Description
match-list <name> This command is used to configure a
match-list.
This enters Match-list Configuration
Mode.
To Next Page
Loading...
