Allied Telesis x900-24 series manual Some protocols also use filters, so use some of the length

Page 11

How many filters can you create?

Okay length For example, this set of filters would work:

source MAC address source UDP port

destination IP address + destination TCP port

The total number of bytes for the switch to check in a packet would be:

source MAC address + IP protocol type + source TCP/UDP port + destination IP address + destination TCP/UDP port =

6 + 1 + 2 + 4 + 2 = 15 bytes

Too long But this set of filters would not work:

source MAC address destination MAC address

destination IP address + destination TCP port

The total number of bytes for the switch to check in a packet would be:

source MAC address + destination MAC address + IP protocol type + destination IP address + destination TCP/UDP port =

6 + 6 + 1 + 4 + 2 = 19 bytes

Some protocols also use filters, so use some of the length

The following protocols use filters, and therefore use up some of the available profile length and filter entries:

EPSR EPSR matches on VLAN ID, which uses 2 bytes. EPSR is disabled by default.

IGMP IGMP snooping matches on the IP protocol type field (to identify IGMP packets and send snooping them to the CPU). This uses 1 byte. IGMP snooping is enabled by default.

DHCP DHCP snooping matches on the IP protocol type field (1 byte) and the source and snooping destination UDP ports (2 bytes each). Therefore, it uses 5 bytes in total. DHCP snooping is

disabled by default.

MLD MLD snooping matches on the IPv6 router alert option and its value (2 bytes). MLD snooping snooping is enabled by default. If you are not using IPv6, you can turn off MLD snooping with the

command disable mldsnooping.

Page 11 AlliedWare™ OS How To Note: Hardware Filters

Page 10 Page 12
Image 11
Page 10 Page 12
Contents Introduction AlliedWareTM OSThis document contains the following What information will you find in this document?Creating dedicated hardware filters Configuring packet classification1st tag Configuring inner parameters for nested VLANsCore port 1st tag 2nd tag Nested VLANs disabled Customer portFor example, imagine you have the following set of filters Then, enter the following commandCreating hardware filters Effects of the action parameters Logic of the operation of the hardware filtersFilter rules table Combining hardware filters and QoSHow many filters can you create? Rule Empty Rule table Extra rules used when combining QoS and hardware filtersRule Profile maskFollowing figure shows the copies of these rules Are there enough bytes for your set of filters? Okay length For example, this set of filters would work Disabled by defaultSome protocols also use filters, so use some of the length How to see the current filter resource usage on the switch 07D0 in hexadecimal Appendix a How to use the layer 4 mask in classifiersDefault mask BinaryPoints to remember Example 1 portsNow it is really easy to write the classifiers Example 2 portsExample 3 ports 024 128256 51265536 Following table shows the port ranges for the largest blocksC613-16058-00 REV C
Top Page Image Contents