Allied Telesis X900-12XT/S, x908 manual Some protocols also use filters, so use some of the length

Page 21

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:

CPU CPU protection is enabled by default. It controls the rate at which packets reach the CPU, protection and uses filters to ensure that ARP and unregistered multicast packets get prioritised

appropriately.

It matches on:

Ethertype—2 bytes to check for ARP, and

VLAN tagging—2 bytes to check for tagged ARPs, and

destination MAC address—6 bytes to check for unregistered multicasts (01-00-5E-00-00-xx),

or

destination IP address—4 bytes to check for unregistered multicasts (224.0.0.x).

CPU protection automatically changes from using the destination MAC address to the destination IP address if you configure a filter that uses destination IP address (as long as no other filter already uses destination MAC address). This minimises the impact CPU protection has on the number of filters available. However, it still uses 8-10 bytes of width.

If you are sure your network will not have an excessive rate of broadcast and multicast traffic, you can turn off CPU protection by using the command no platform cpuprotection.

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

USA Headquarters 19800 North Creek Parkway Suite 200 Bothell WA 98011 USA T: +1 800 424 4284 F: +1 425 481 3895

European Headquarters Via Motta 24 6830 Chiasso Switzerland T: +41 91 69769.00 F: +41 91 69769.11

Asia-Pacific Headquarters 11 Tai Seng Link Singapore 534182 T: +65 6383 3832 F: +65 6383 3830

www.alliedtelesis.com

© 2007 Allied Telesis, Inc. All rights reserved. Information in this document is subject to change without notice. Allied Telesis is a trademark or registered trademark of Allied Telesis, Inc. in the United States and other countries.

All company names, logos, and product designs that are trademarks or registered trademarks are the property of their respective owners.

C613-16119-00 REV A

Page 20 Page 21
Image 21
Page 20 Page 21
Contents AlliedWare PlusTM OS Which products and software version does this Note apply to? Creating IP hardware ACLs Creating hardware ACLsDestination-ip-address TCP and UDP You can filter TCP and UDP packets on the basis Creating MAC address hardware ACLs Effects of the action keywords in ACLsACLs Making filters by applying hardware ACLs to portsMaking filters by using QoS class-maps Specifying what the class-map will match on Creating a class-mapMatching on inner keywords for nested VLANs Matching on TCP flag So will the following single match commandApplying the class-maps to a policy-map Applying the policy-map to portsMatching on eth-format and protocol Combining interface ACLs and QoS class-maps Logic of the operation of the hardware filtersBlocking all multicast traffic ExamplesMirroring Http and Smtp traffic Blocking all multicast traffic except one addressMirroring ARP packets This example uses two QoS class-maps Blocking TCP sessions in one direction Filter rules table How many filters can you create?Profile mask Are there enough bytes for your set of filters? Some protocols also use filters, so use some of the length
Related manuals
Manual 8 pages 39.31 Kb Manual 52 pages 56.44 Kb
Top Page Image Contents