Alcatel-Lucent OmniAccess 5740 - Page 509

CC Configuration
Except on the first page, right running head:
Heading1 or Heading1NewPage text (automatic)
483
Alcatel-Lucent
Beta Beta
OmniAccess 5740 Unified Services Gateway CLI Configuration Guide
TO CONFIGURE RULES FOR TCP
E
XAMPLE
Ex 1:
The following example configures a TCP rule with ‘any any’ and service ‘smtp’,
and another TCP rule with ‘any any’ and type ‘normal’:
ALU(config-match-list-test)# tcp any any service smtp
ALU(config-match-list-test)# tcp any any type normal
Ex 2:
This example gives a list of possible rules that can be used in a match-list, with a
comparison of the ‘service’ keyword used in case of “tcp”.
ALU(config-match-list-m1)# ip prefix 10.0.0.0/8 any
ALU(config-match-list-m1)# ip host 10.0.0.0 any
ALU(config-match-list-m1)# ip prefix 192.168.1.0/24 host
10.0.0.0
ALU(config-match-list-m1)# tcp interface GigabitEthernet3/0
interface GigabitEthernet 3/0 service smtp
Ex 3:
The power and flexibility of the rulesets can be best seen when the list references
are used, especially in multiple fields e.g the following configuration:
ALU(config)# list i1 prefix 10.0.0.0/8 prefix 11.0.0.0/8
ALU(config)# list i2 prefix 20.0.0.0/8 prefix 21.0.0.0/8
ALU(config)# match-list m1
ALU(config-match-list-m1)# 1 tcp list i1 list i2 service
telnet
Command (in Match-list CM) Description
[<1-1024>] tcp {any|host <source
ip-address>|interface <name>|list
<name>|prefix <source ip-address/
prefix length>} {any|host
<destination ip-address>|interface
<name>|list <name>|prefix
<destination ip-address/prefix
length>} [ack|dscp {<0-63>|<dscp-
mnemonics>}|established|fin|
fragment|from <1-65536>|ip-
precedence {<0-7>|<precedence-
mnemonics>}|length {<1-1500>
|{eq|ge|gt|le|lt|range <1-1500>}}
|rst|service {<1-65536>|<protocol>}
|syn|urg|tos {<0-15>|<tos-
mnemonics>}|type {ftp|normal
|rpc|rtcp|rtp|sip|tftp}]
This command is used to
configure rules for TCP protocol in
a match-list.