Supermicro L2 User manual

L2 / L3 Switches
Access Control Lists (ACL)
Configuration Guide
Revision 1.0

ACL Configuration Guide
Supermicro L2/L3 Switches Configuration Guide
2
The information in this USER’S M NU L has been carefully reviewed and is believed to be accurate. The vendor
assumes no responsibility for any inaccuracies that may be contained in this document, makes no commitment to
update or to keep current the information in this manual, or to notify any person or organization of the updates.
Please Note: For the most up-to-date version of this manual, please see our web site at www.supermicro.com.
Super Micro Computer, Inc. (“Supermicro”) reserves the right to make changes to the product described in this
manual at any time and without notice. This product, including software, if any, and documentation may not, in
whole or in part, be copied, photocopied, reproduced, translated or reduced to any medium or machine without
prior written consent.
IN NO EVENT WILL SUPERMICRO BE LI BLE FOR DIRECT, INDIRECT, SPECI L, INCIDENT L, SPECUL TIVE OR
CONSEQUENTI L D M GES RISING FROM THE USE OR IN BILITY TO USE THIS PRODUCT OR DOCUMENT TION,
EVEN IF DVISED OF THE POSSIBILITY OF SUCH D M GES. IN P RTICUL R, SUPERMICRO SH LL NOT H VE
LI BILITY FOR NY H RDW RE, SOFTW RE, OR D T STORED OR USED WITH THE PRODUCT, INCLUDING THE
COSTS OF REP IRING, REPL CING, INTEGR TING, INST LLING OR RECOVERING SUCH H RDW RE, SOFTW RE, OR
D T .
ny disputes arising between manufacturer and customer shall be governed by the laws of Santa Clara County in
the State of California, US . The State of California, County of Santa Clara shall be the exclusive venue for the
resolution of any such disputes. Super Micro's total liability for all claims will not exceed the price paid for the
hardware product.
FCC Statement: This equipment has been tested and found to comply with the limits for a Class digital device
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful
interference when the equipment is operated in a commercial environment. This equipment generates, uses, and
can radiate radio frequency energy and, if not installed and used in accordance with the manufacturer’s instruction
manual, may cause harmful interference with radio communications. Operation of this equipment in a residential
area is likely to cause harmful interference, in which case you will be required to correct the interference at your
own expense.
California Best Management Practices Regulations for Perchlorate Materials: This Perchlorate warning applies only
to products containing CR (Manganese Dioxide) Lithium coin cells. Perchlorate Material-special handling may
apply. See http://www.dtsc.ca.gov/hazardouswaste/perchlorate/ for further details.
Manual Revison 1.0
Release Date: December 18, 2012
Unless you request and receive written permission from Super Micro Computer, Inc., you may not copy any part of
this document.
Information in this document is subject to change without notice. Other products and companies referred to
herein are trademarks or registered trademarks of their respective companies or mark holders.
Copyright © 2012 by Super Micro Computer, Inc.
ll rights reserved.
Printed in the United States of merica

ACL Configuration Guide
Supermicro L2/L3 Switches Configuration Guide
3
Contents
1 CL Configuration Guide ....................................................................................................................... 4
1.1 What is CL ................................................................................................................................... 5
1.2 How CL works in Hardware SIC ................................................................................................ 5
1.3 Types of CL .................................................................................................................................. 5
1.3.1 M C Extended CL................................................................................................................ 6
1.3.2 IP Standard CL ..................................................................................................................... 6
1.3.3 IP Extended CL .................................................................................................................... 6
1.4 M C Extended CL ....................................................................................................................... 7
1.4.1 Creating M C Extended CL ................................................................................................. 7
1.4.2 Modifying M C Extended CL ............................................................................................ 10
1.4.3 Removing M C Extended CL............................................................................................. 10
1.4.4 pplying M C Extended CL to Interfaces ......................................................................... 11
1.4.5 Displaying M C Extended CL ............................................................................................ 12
1.4.6 M C Extended CL Configuration Example 1 ..................................................................... 13
1.5 IP Standard CL ........................................................................................................................... 14
1.5.1 Creating IP Standard CL .................................................................................................... 15
1.5.2 Modifying IP Standard CL .................................................................................................. 16
1.5.3 Removing IP Standard CL .................................................................................................. 17
1.5.4 pplying IP CL to Interfaces .............................................................................................. 17
1.5.5 Displaying IP Standard CL ................................................................................................. 19
1.5.6 IP Standard CL Configuration Example 1 .......................................................................... 20
1.6 IP Extended CL .......................................................................................................................... 21
1.6.1 Creating IP Extended CL for IP Traffic ............................................................................... 22
1.6.2 Creating IP Extended CL for TCP Traffic ............................................................................ 23
1.6.3 Creating IP Extended CL for UDP Traffic ........................................................................... 25
1.6.4 Creating IP Extended CL for ICMP Traffic ......................................................................... 27
1.6.5 Modifying IP Extended CL ................................................................................................. 29
1.6.6 Removing IP Extended CL ................................................................................................. 29
1.6.7 pplying IP Extended CL to Interfaces .............................................................................. 30
1.6.8 Displaying IP Extended CL ................................................................................................. 30
1.6.9 IP Extended CL Configuration Example 1 .......................................................................... 33

ACL Configuration Guide
Supermicro L2/L3 Switches Configuration Guide
4
1ACL Configuration Guide
This document describes the ccess Control Lists ( CL) feature supported in Supermicro Layer 2 / Layer
3 switch products.
ccess Control List configurations with examples are explained in this document in detail.
This document covers the CL configurations for the below listed Supermicro switch products.
The majority of this document is applicable to all the above listed Supermicro switch products. However,
the contents in any particular subsection might vary across these switch product models. In those
sections, the differences are clearly identified with reference to particular switch product models. If any
particular switch product model is not referenced, the reader can safely assume that the content is
applicable for all the listed Supermicro switch product models.
In this entire document, the common term “switch” refers to any of the above listed
Supermicro switch product models unless another switch product model is named.
CLs are widely used to provide security and Quality of Service (QoS). This document focuses on CL
configurations only. To learn how to use CLs for QoS, refer to the QoS Configuration Guide.
Top of Rack Switches
• SSE-G24-TG4
• SSE-G48-TG4
• SSE-X24S
• SSE-X3348S
• SSE-X3348T
Blade Switches
• SBM-GEM-X2C
• SBM-GEM-X2C+
• SBM-GEM-X3S+
• SBM-XEM-X10SM

ACL Configuration Guide
Supermicro L2/L3 Switches Configuration Guide
5
1.1What is ACL
CL is used to filter or redirect any particular traffic flow on the switch.
CLs can be configured to match packets based on Layer 2 M C, Layer 3 IP or Layer 4 TCP/UDP
parameters.
Every packet entering the switch is checked for the configured CLs. If any packet contents match any of
the configured CL , that packet will be handled according to the matched CL configured action.
CL configuration provides the following actions that can be applied on matched traffic flow.
1.2How ACL works in Hardware ASIC
Supermicro switches implement CL in hardware SIC ( pplication Specific Integrated Circuit) to provide
line rate CL processing for all incoming traffic.
User configured CL rules are programmed in an CL table in SIC. Layer 2 M C extended CL and
Layer 3 IP CL are implemented in two separate hardware tables, which are TC M tables in SIC.
SIC analyzes the first 128 bytes of every received packet and extracts the packet contents for key fields
in the Layer 2, Layer 3 and Layer 4 headers. SIC looks up the CL tables to find a matching CL rule for
the extracted content of the packet. SIC compares the values of the configured fields only and it treats
all other fields as “do not care”. Once a matching CL is found, SIC stops looking in that CL table.
SIC applies the configured action of the matching CL rule to the matched packet. This could result in it
dropping that packet, redirecting it to any particular port or simply allowing the packet to be forwarded
through the switch.
lookup on Layer 2 CL table and Layer 3 CL table happens simultaneously. If any packet matches the
CL rules of both Layer 2 and Layer 3 CL tables, the actions configured on both CL rules will be
applied. In this case, conflicting actions configured on Layer 2 and Layer 3 CL tables for the same traffic
could lead to unpredictable behavior. Hence it is suggested to avoid such CL use cases.
1.3Types of ACLs
Supermicro switches support the following three different types of CLs.
•The switch drops all packets matching this ACL
Deny
•The switch redirects all packets matching this ACL to any
configured redirect port
Redirect
•The switch permits all packets matching this ACL
Permit

ACL Configuration Guide
Supermicro L2/L3 Switches Configuration Guide
6
1.3.1 AC Extended ACL
M C Extended CL allows users to control the traffic based on fields in Ethernet M C and VL N
headers.
Users can configure the traffic flow based on source M C address, destination M C address or Ethernet
type field value. Users can also use VL N identifiers to configure the traffic flow.
Users can choose to deny, redirect or permit the configured traffic flow using a M C Extended CL.
1.3.2 IP Standard ACL
n IP Standard CL allows users to control the traffic based on the fields in an IP header.
Users can configure the traffic flow based on source IP address and destination IP address.
Users can choose to deny, redirect or permit the configured traffic flow using an IP Standard CL.
1.3.3 IP Extended ACL
n IP Extended CL allows users to control the traffic based on fields in an IP header, ICMP header, TCP
header and UDP header.
Users can configure the traffic flow based on source IP address, destination IP address, protocol field in
IP header, TOS field in IP header or by using a DSCP priority in an IP header.
Users can also configure the traffic flow based on ICMP message type, ICMP message code, TCP port
number or UDP port number.
Users can choose to deny, redirect or permit the configured traffic flow using an IP Extended CL.
Three
types
of CL
M C Extended CL
IP Standard CL
IP Extended CL

ACL Configuration Guide
Supermicro L2/L3 Switches Configuration Guide
7
1.4 AC Extended ACL
Supermicro switches support up to 128 M C Extended CLs.
Users can define a M C Extended CL with a deny, permit or redirect action rule. M C Extended CL
can be defined only with one rule. To implement multiple rule CLs, configure multiple M C Extended
CLs.
There is no implied deny all rule in Supermicro switch CLs. By default
,
all packets not
matching a configured CL rule will be forwarded automatically. For any traffic to be denied,
it has to be configured with an explicit deny rule.
The permit rule is widely used for QoS applications. In some cases permit rules are useful when all traffic
is denied by a rule and a few specific hosts are to be permitted. In this case, permit rules have to be
created before deny rules to make sure switch hardware processes permit rules first.
M C Extended CLs allow users to configure the traffic flow with the following fields.
Source M C ddress
Destination M C ddress
Non-IP Protocol
Ethernet type field in an Ethernet Header
VL N Identifier
M C Extended CL rules can be created and identified either a with an CL number such as 1,2,3 or with
a name string. n CL identifier number can be any number from 1 to 65535. n CL identifier name
can be any string length not exceeding 32 characters.
1.4.1 Creating AC Extended ACLs
Follow the steps below to create a M C Extended CL.
Step Command escription
Step 1
configure terminal
Enter the configuration mode
Step 2
mac access
-
list extended
{ <
access-list-number
>
| <access-list-name> }
Create
s
a M C Extended CL using
the
mac-access-list extended command.
access-list-number – can be any
number from 1 to 65535
access-list-name – any name string up
to 32 characters.
Step 3
deny { any | host <src-mac-address>}
{
any | host <dest-mac-address> } [aarp
|
amber | dec-spanning | decnet-iv
|
Configure
s
a deny CL rule
,
a
permit
CL rule or a redirect CL rule.

ACL Configuration Guide
Supermicro L2/L3 Switches Configuration Guide
8
diagnostic | dsm | etype-6000 | etype-8042
| lat | lavc-sca | mop-console | mop-dump
| msdos | mumps | netbios | vines-echo
| vines-ip | xns-id | <protocol (0-65535)>
]
[ encaptype <value (1-65535)>]
[Vlan <vlan-id (1-4069)>] [priority <value
(1-255)>]
or
permit { any | host <src-mac-address
>}{
any | host <dest-mac-address> } [aarp
|
amber | dec-spanning | decnet-iv
|
diagnostic | dsm | etype-6000 |etype-8042
|
lat | lavc-sca | mop-console | mop-dump
|
msdos | mumps | netbios | vines-echo
|
vines-ip | xns-id | <protocol (0-65535
)>] [
encaptype <value (1-65535)>][ Vlan <vlan-id
(1-4069)>] [priority <value (1-255)>]
or
redirect <interface-type> <interface-id
> {
any | host <src-mac-address>}{ any
|
host <dest-mac-address> } [aarp | amber
| dec-spanning | decnet-iv | diagnostic
|
dsm | etype-6000 | etype-8042 | lat | lavc-
sca | mop-console | mop-dump | msdos
|
mumps | netbios | vines-echo | vines-ip
|
xns-id | <protocol (0-65535)>] [ encaptype
<value (1-65535)>][ Vlan <vlan-id (1-
4069)>] [priority <value (1-255)>]
The source and destination M C
addresses are provided with the
keyword host. The keyword any is used
to refer any M C addresses. If a source
or destination M C address is
configured as any, the switch will not
check that source or destination M C
address to match the packets for this
CL.
User can configure any of the following
non-IP protocols to match for this rule.
aarp | amber | dec-spanning
|
decnet-iv | diagnostic | dsm
|
etype-6000 | etype-8042 | lat
|
lavc-sca | mop-console | mop-
dump | msdos | mumps
|
netbios | vines-echo | vines-ip
|
xns-id
lternatively, users can configure the
protocol number to be matched for this
CL rule.
This Non-IP protocol or protocol type is
an optional parameter. If not provided,
switch will not check the Non-IP
protocol field while matching packets
for this CL.
The encaptype keyword can be used to
configure the Ethernet header Encap
Type field to be matched to apply this
CL rule.
This encaptype is an optional
parameter. If not provided, switch will
not check this field while matching
packets for this CL.
If this CL rule is to be applied only to a
particular VL N, user can configure
VL N number using Vlan keyword.
This Vlan is an optional parameter. If
not provided, switch will not check
VL N while matching packets for this
CL.
The priority keyword lets user assign a

ACL Configuration Guide
Supermicro L2/L3 Switches Configuration Guide
9
priority for this CL rule.
This priority is an optional parameter. It
can be any value from 1 to 255. The
default value is 1.
Redirect CL rule needs additional
<interface-type> <interface-id
>
parameters to define the port to which
the packets matching this CL rule need
to be redirected.
Step 4
show
access
-
lists
D
isplay
s
the configured CL rule
s
Step 5
write startup
-
config
Optional step
–
Save
s
this
CL
configuration to be part of startup
configuration.
Every CL
is
applied
to
all ports by default.
ny CL
that
needs to be applied only
to
particular ports needs to be configured as described in section pplying M C Extended CL
to Interfaces.
The below examples show various ways of creating a M C Extended CL.
Create a deny MAC Extended ACL with ACL number 100 to deny all traffic from MAC 00:25:90:01:02:03
SMIS# configure terminal
SMIS(config)# mac access-list extended 100
SMIS(config-ext-macl)# deny host 00:25:90:01:02:03 any
Create a permit MAC Extended ACL with ACL name acl_cw3 to permit all traffic from MAC
00:25:30:01:02:03
SMIS# configure terminal
SMIS(config)# mac access-list extended acl_cw3
SMIS(config-ext-macl)# permit host 00:25:30:01:02:03 any
Create a redirect MAC Extended ACL to redirect all packets from MAC 00:25:90:01:02:03 going to MAC
00:25:90:01:02:04 to interface gi 0/10.
SMIS# configure terminal
SMIS(config)# mac access-list extended 1
SMIS(config-ext-macl)# redirect gi 0/10 host 00:25:90:01:02:03 host 00:25:90:01:02:04

ACL Configuration Guide
Supermicro L2/L3 Switches Configuration Guide
10
1.4.2 odifying AC Extended ACLs
To modify a configured M C Extended CL, follow the same steps used to create a M C Extended CL.
When users modify an CL with a deny, permit or redirect rule, the previously configured rule and its
parameters for that CL will be completely overwritten with the newly provided rules and parameters.
The below example shows a M C Extended CL rule 50 that is created and later modified with different
parameters.
SMIS# configure terminal
SMIS(config)# mac access-list extended 50
SMIS(config-ext-macl)# deny host 00:25:90:01:02:03 any
SMIS(config-ext-macl)# end
# Modify this CL’s rule 50 to deny traffic destined to a particular host M C instead of any
SMIS# configure terminal
SMIS(config)# mac access-list extended 50
SMIS(config-ext-macl)# deny host 00:25:90:01:02:03 host 00:25:90:01:02:04
1.4.3 Removing AC Extended ACLs
Follow the steps below to remove M C Extended CLs.
Step Command escription
Step 1
configure terminal
Enter
s
the configuration mode
Step 2
no
mac access
-
list
extended
{ <
access-list-
number> | <access-list-name> }
Delete
s
a M C Extended CL using
no
mac-access-list extended command.
access-list-number – the CL number
that needs to be deleted
access-list-name – the name of the
CL that needs to be deleted
Step 3
show access
-
lists
D
isplay
s
the configured CL rule
s
to
make sure the deleted CL is removed
properly
Step 4
write startup
-
config
Optional step
–
Save
s
this CL
configuration to be part of startup
configuration.
The example below shows how to remove a M C Extended CL .
SMIS# configure terminal
SMIS(config)# no mac access-list extended 50