Alcatel-Lucent OmniSwitch 6850-48 Network Configuration Manual page 922

Creating Policies
The keywords used with these commands are similar to the keywords used for the
command. The keyword should be relevant to the type of traffic as listed in the table here:
show policy classify l2
source port
destination port
source mac
destination mac
source vlan
To test a theoretical condition against the set of pending policies, enter the command and the relevant
keyword and value. The switch will display information about the potential traffic and attempt to match it
to a policy (pending policies only). For example:
-> show policy classify l2 destination mac 08:00:20:d1:6e:51
Packet headers:
L2:
*Port
*IfType
*MAC
*VLAN
*802.1p
L3/L4:
*IP
*TOS/DSCP
Using pending l2 policies
Classify L2 Destination:
*Matches rule 'yuba': action pri3 (accept)
Classify L2 Source:
*No rule matched: (accept)
The display shows Layer 2 or Layer 3 information, depending on what kind of traffic you are attempting to
classify. In this example, the display indicates that the switch found a rule, yuba, to classify destination
traffic with the specified Layer 2 information.
To test a theoretical condition against the set of applied policies, enter the command with the applied
keyword. The switch will display information about the potential traffic and attempt to match it to a policy
(applied policies only). For example:
-> show policy classify l3 applied source ip 143.209.92.131 destination ip
198.60.82.5
Packet headers:
L2:
*Port
*IfType
*MAC
*VLAN
*802.1p
L3/L4:
*IP
*TOS/DSCP
page 40-40
show policy classify l3
source port
destination port
source ip
source ipv6
destination ip
destination ipv6
ip protocol
ipv6
nh
flow-label
source ip port
destination ip port
tos
dscp
: 0/0
: any
: 000000:000000
:
: 0
: 0.0.0.0
: 0/0
: 0/0
: any
: 000000:000000
:
: 0
: 143.209.92.131
: 0/0
OmniSwitch AOS Release 6 Network Configuration Guide
destination port
destination mac
destination vlan (multicast only)
destination ip
-> 0/0
-> any
-> 080020:D1E51
0 -> 0
-> 0.0.0.0
-> 0/0
-> any
-> 000000:000000
0 -> 0
-> 198.60.82.5
Configuring QoS
policy condition
September 2009