Chelsio Communications Terminator 6, Инструкция по установке и эксплуатации, Страница: 289 / 432

Chapter XX. Classification and Filtering
Chelsio Unified Wire for Linux 289
Choosing filterMode and filterMask
As mentioned earlier filterMask tuples can be subset of or equal to filterMode tuples. Following
are examples of how you can select filterMode and filterMask and create a Hash filter based on
those values:
•
When all tuples from filterMode are enabled in filterMask
i. Select a filterMode from supported filterMode table based on your requirement. E.g.,
filterMode = fragmentation, mpshittype, protocol, vlan, port, fcoe
ii. Select a filterMask so that it is a subset of or equal to filterMode based on application. E.g.;
filterMask = fragmentation, mpshittype, protocol, vlan, port, fcoe
Here, we have selected fragmentation, mpshittype, protocol, vlan, port, fcoe in filterMask so it is
mandatory to create a filter based on all of those tuples mentioned in filterMask. Otherwise, filter
rule will not honour.
iii. Now, to create a hash filter based on the filterMode and filterMask values selected above:
[root@host~]# cxgbtool eth18 filter 100 action drop lip 120.10.10.100 fip
120.10.10.200 lport 5001 fport 51549 proto 6 frag 0 matchtype 0 ivlan 10
iport 0 fcoe 0 hitcnts 1 cap maskless
Hash-Filter Index = 303760
•
When all tuples from filterMode are not enabled in filterMask:
In case if you don’t want to create filter rule based on any particular tuple from filterMode, don’t
select i
t in filterMask. For example, if you don’t want to create a filter based on VLAN value, then
don’t select it from filterMode to filterMask.
i. Select a filterMode from supported filterMode table based on your requirement. E.g.,
filterMode = fragmentation, mpshittype, protocol, vlan, port, fcoe
In case of Hash/DDR filters, source_ip, destination_ip, source_port and
destination_port are mandatory, since the filters don't support masks and hence,
4-tuple must always be supplied. Proto is also a mandatory parameter.
Note