HPE FlexNetwork 5510 HI Series User manual
HPE FlexNetwork 5510 HI Switch Series
A
CL and QoS
Configuration Guide
Part number: 5200-0064a
Software version: Release 11xx
Document version: 6W101-20161221
© Copyright 2015, 2016 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
Enterprise products and services are set forth in the express warranty statements accompanying such
products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or
copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s
standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise
website.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the
United States and other countries.
Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries.
Adobe® andAcrobat® are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
i
Contents
Configuring ACLs····························································································1
Overview····························································································································································1
Applications on the switch··························································································································1
ACL categories···········································································································································1
Numbering and naming ACLs····················································································································1
Match order················································································································································2
Rule numbering··········································································································································2
Fragment filtering with ACLs······················································································································3
Configuration task list·········································································································································3
Configuring a basic ACL ····································································································································3
Configuring an IPv4 basic ACL··················································································································4
Configuring an IPv6 basic ACL··················································································································4
Configuring an advanced ACL···························································································································5
Configuring an IPv4 advanced ACL···········································································································5
Configuring an IPv6 advanced ACL···········································································································6
Configuring an Ethernet frame header ACL·······································································································7
Copying an ACL·················································································································································8
Configuring packet filtering with ACLs ···············································································································8
Applying an ACL to an interface for packet filtering···················································································9
Configuring the applicable scope of packet filtering on a VLAN interface··················································9
Setting the interval for generating and outputting packet filtering logs·······················································9
Setting the packet filtering default action ·································································································10
Displaying and maintaining ACLs ····················································································································10
ACL configuration example······························································································································10
Network requirements······························································································································10
Configuration procedure···························································································································11
Verifying the configuration························································································································11
QoS overview································································································13
QoS service models·········································································································································13
Best-effort service model ·························································································································13
IntServ model···········································································································································13
DiffServ model··········································································································································13
QoS techniques overview ································································································································13
Deploying QoS in a network ····························································································································14
Configuring a QoS policy··············································································15
Non-MQC approach·········································································································································15
MQC approach·················································································································································15
Configuration procedure diagram ····················································································································15
Defining a traffic class······································································································································16
Configuration guidelines···························································································································16
Configuration procedure···························································································································16
Defining a traffic behavior ································································································································17
Defining a QoS policy ······································································································································18
Applying the QoS policy···································································································································18
Applying the QoS policy to an interface···································································································18
Applying the QoS policy to a VLAN··········································································································19
Applying the QoS policy globally··············································································································19
Applying the QoS policy to a control plane ······························································································19
Applying the QoS policy to a user profile·································································································20
Displaying and maintaining QoS policies·········································································································21
Configuring priority mapping·········································································22
Overview··························································································································································22
Introduction to priorities····························································································································22
Priority maps············································································································································22
ii
Priority trust mode on a port·····················································································································23
Priority mapping process··························································································································24
Priority mapping configuration tasks················································································································26
Configuring a priority map································································································································27
Configuring an interface to trust packet priority for priority mapping································································27
Changing the port priority of an interface·········································································································28
Displaying and maintaining priority mapping ···································································································28
Priority mapping configuration examples·········································································································28
Priority trust mode configuration example································································································28
Priority mapping table and priority marking configuration example··························································29
Configuring traffic policing, GTS, and rate limit·············································33
Overview··························································································································································33
Traffic evaluation and token buckets········································································································33
Traffic policing··········································································································································34
GTS··························································································································································35
Rate limit··················································································································································36
Configuring traffic policing································································································································37
Configuring GTS ··············································································································································38
Configuring the rate limit··································································································································38
Displaying and maintaining traffic policing, GTS, and rate limit·······································································39
Traffic policing configuration example··············································································································39
Network requirements······························································································································39
Configuration procedure···························································································································40
Configuring congestion management ···························································42
Overview··························································································································································42
SP queuing···············································································································································42
WRR queuing···········································································································································43
WFQ queuing···········································································································································44
SP+WRR queuing····································································································································44
SP+WFQ queuing····································································································································44
Congestion management configuration task list ······························································································45
Configuring queuing·········································································································································45
Configuring SP queuing···························································································································45
Configuring WRR queuing ·······················································································································45
Configuring WFQ queuing························································································································46
Configuring SP+WRR queuing ················································································································47
Configuring SP+WFQ queuing·················································································································48
Displaying and maintaining queuing ········································································································49
Configuring queue scheduling profiles·············································································································50
Configuring a queue scheduling profile····································································································50
Displaying and maintaining queue scheduling profiles ············································································51
Queue scheduling profile configuration example·····················································································51
Configuring congestion avoidance································································53
Overview··························································································································································53
Tail drop···················································································································································53
RED and WRED·······································································································································53
ECN··························································································································································53
Configuring and applying a WRED table ·········································································································54
Configuration procedure···························································································································55
Configuration example·····························································································································55
Displaying and maintaining WRED··················································································································56
Configuring traffic filtering·············································································57
Configuration procedure ··································································································································57
Configuration example·····································································································································58
Network requirements······························································································································58
Configuration procedure···························································································································58
iii
Configuring priority marking··········································································59
Overview··························································································································································59
Color-based priority marking····························································································································59
Packet coloring methods··························································································································59
Configuring color-based priority marking ·································································································59
Configuration procedure ··································································································································60
Priority marking configuration examples··········································································································61
Local precedence marking configuration example···················································································61
Local QoS ID marking configuration example··························································································63
Configuring nesting·······················································································67
Configuration procedure ··································································································································67
Configuration example·····································································································································68
Network requirements······························································································································68
Configuration procedure···························································································································68
Configuring traffic redirecting········································································70
Configuration procedure ··································································································································70
Configuration example·····································································································································71
Network requirements······························································································································71
Configuration procedure···························································································································71
Configuring global CAR ················································································73
Overview··························································································································································73
Aggregate CAR········································································································································73
Hierarchical CAR······································································································································73
Configuring aggregate CAR·····························································································································74
Configuring hierarchical CAR···························································································································74
Displaying and maintaining global CAR···········································································································75
Aggregate CAR configuration example············································································································75
Network requirements······························································································································75
Configuration procedure···························································································································75
Hierarchical CAR configuration examples ·······································································································76
AND-mode hierarchical CAR configuration example···············································································76
OR-mode hierarchical CAR configuration example ·················································································78
Configuring class-based accounting·····························································80
Configuration procedure ··································································································································80
Configuration example·····································································································································81
Network requirements······························································································································81
Configuration procedure···························································································································81
Appendixes···································································································83
Appendix A Default priority maps·····················································································································83
Appendix B Introduction to packet precedences······························································································84
IP precedence and DSCP values·············································································································84
802.1p priority ··········································································································································85
EXP values···············································································································································86
Configuring time ranges················································································87
Configuration procedure ··································································································································87
Displaying and maintaining time ranges ··········································································································87
Time range configuration example···················································································································87
Configuring data buffers················································································89
Configuration task list·······································································································································89
Enabling the Burst feature ·······························································································································90
Configuring data buffers manually ···················································································································90
Setting the total shared-area ratio············································································································90
Setting the maximum shared-area ratio for a queue················································································91
Setting the fixed-area ratio for a queue····································································································91
iv
Applying data buffer configuration············································································································92
Displaying and maintaining data buffers··········································································································92
Document conventions and icons·································································93
Conventions·····················································································································································93
Network topology icons····································································································································94
Support and other resources ········································································95
Accessing Hewlett Packard Enterprise Support ······························································································95
Accessing updates···········································································································································95
Websites ··················································································································································96
Customer self repair·································································································································96
Remote support········································································································································96
Documentation feedback ·························································································································96
Index·············································································································98
1
Configuring ACLs
Overview
An access control list (ACL) is a set of rules (or permit or deny statements) for identifying traffic
based on criteria such as source IP address, destination IP address, and port number.
ACLs are primarily used for packet filtering. "Configuring packet filtering with ACLs" provides an
example. You canuse ACLs in QoS, security, routing, and other feature modules for identifying traffic.
The packet drop or forwarding decisions depend on the modules that use ACLs.
Applications on the switch
An ACL is implemented in hardware or software, depending on the module that uses it.
•If the module is implemented in hardware (for example, the packet filter or QoS module), the
ACL is applied to hardware to process traffic.
•If the module is implemented in software (for example, the routing module or the login
management module), theACL is applied to software to process traffic.
The Telnet and SNMP features in the login management module denies packets that do not match
any ACL. Some modules (QoS for example) ignore the permit or deny action in ACLrules and do not
base their drop or forwarding decisions on the action set in ACL rules. See the specified module for
information about ACL application.
ACL categories
Category ACL number IP version Match criteria
Basic ACLs 2000 to 2999 IPv4 Source IPv4 address.
IPv6 Source IPv6 address.
Advanced ACLs 3000 to 3999
IPv4 Source IPv4 address, destination IPv4
address, packet priority, protocol number, and
other Layer 3 and Layer 4 header fields.
IPv6 Source IPv6 address, destination IPv6
address, packet priority, protocol number, and
other Layer 3 and Layer 4 header fields.
Ethernet frame
header ACLs 4000 to 4999 IPv4 and IPv6 Layer 2 header fields, such as source and
destination MAC addresses, 802.1p priority,
and link layer protocol type.
Numbering and naming ACLs
Each ACL category has a unique range of ACL numbers. When creating an ACL, you must assign it
a number. In addition, you can assign the ACL a name for ease of identification. After creating an
ACL with a name, you cannot rename it or delete its name.
For an IPv4 basic or advanced ACLs, itsACL number and name must be unique in IPv4. For an IPv6
basic or advancedACL, its ACL number and name must be unique in IPv6.
2
Match order
The rules in an ACL are sorted in a specific order. When a packet matches a rule, the device stops
the match process and performs the action defined in the rule. If an ACL contains overlapping or
conflicting rules, the matching result and action to take depend on the rule order.
The followingACL match orders are available:
•config—SortsACL rules in ascending order of rule ID.Arule with a lower ID is matched before
a rule with a higher ID. If you use this method, check the rules and their order carefully.
•auto—SortsACL rules in depth-first order. Depth-first ordering makes sure any subset of a rule
is always matched before the rule. Table 1 lists the sequence of tie breakers that depth-first
ordering uses to sort rules for each type ofACL.
Table 1 Sort ACL rules in depth-first order
ACL category Sequence of tie breakers
IPv4 basic ACL
1. VPN instance.
2. More 0s in the source IPv4 address wildcard (more 0s means a narrower
IPv4 address range).
3. Rule configured earlier.
IPv4 advanced ACL
1. VPN instance.
2. Specific protocol number.
3. More 0s in the source IPv4 address wildcard mask.
4. More 0s in the destination IPv4 address wildcard.
5. Narrower TCP/UDP service port number range.
6. Rule configured earlier.
IPv6 basic ACL
1. VPN instance.
2. Longer prefix for the source IPv6 address (a longer prefix means a
narrower IPv6 address range).
3. Rule configured earlier.
IPv6 advanced ACL
1. VPN instance.
2. Specific protocol number.
3. Longer prefix for the source IPv6 address.
4. Longer prefix for the destination IPv6 address.
5. Narrower TCP/UDP service port number range.
6. Rule configured earlier.
Ethernet frame header ACL
1. More 1s in the source MAC address mask (more 1s means a smaller
MAC address).
2. More 1s in the destination MAC address mask.
3. Rule configured earlier.
A wildcard mask, also called an inverse mask, is a 32-bit binary number represented in dotted
decimal notation. In contrast to a network mask, the 0 bits in a wildcard mask represent "do
care" bits, and the 1 bits represent "don't care" bits. If the "do care" bits in an IP address are
identical to the "do care" bits in an IP address criterion, the IP address matches the criterion. All
"don't care" bits are ignored. The 0s and 1s in a wildcard mask can be noncontiguous. For
example, 0.255.0.255 is a valid wildcard mask.
Rule numbering
ACL rules can be manually numbered or automatically numbered. This section describes how
automatic ACL rule numbering works.
3
Rule numbering step
If you do not assign an ID to the rule you are creating, the system automatically assigns it a rule ID.
The rule numbering step sets the increment by which the system automatically numbers rules. For
example, the default ACLrule numbering step is 5. If you do not assign IDs to rules you are creating,
they are automatically numbered 0, 5, 10, 15, and so on. The wider the numbering step, the more
rules you can insert between two rules.
By introducing a gap between rules rather than contiguously numbering rules, you have the flexibility
of inserting rules in an ACL. This feature is important for a config-order ACL, where ACL rules are
matched in ascending order of rule ID.
Automatic rule numbering and renumbering
The ID automatically assigned to an ACLrule takes the nearest higher multiple of the numbering step
to the current highest rule ID, starting with 0.
For example, if the numbering step is 5 (the default), and there are five ACL rules numbered 0, 5, 9,
10, and 12, the newly defined rule is numbered 15. If the ACL does not contain any rule, the first rule
is numbered 0.
Whenever the step changes, the rules are renumbered, starting from 0. For example, if there are five
rules numbered 5, 10, 13, 15, and 20, changing the step from 5 to 2 causes the rules to be
renumbered 0, 2, 4, 6, and 8.
Fragment filtering with ACLs
Traditional packet filtering matches only first fragments of packets, and allows all subsequent
non-first fragments to pass through.Attackers can fabricate non-first fragments to attack networks.
To avoid the risks, the HPE ACL implementation does the following:
•Filters all fragments by default, including non-first fragments.
•Allows for matching criteria modification for efficiency. For example, you can configure the ACL
to filter only non-first fragments.
Configuration task list
Tasks at a glance
(Required.) Perform at least one of the following tasks:
•Configuring a basic ACL
{Configuring an IPv4 basic ACL
{Configuring an IPv6 basic ACL
•Configuring an advanced ACL
{Configuring an IPv4 advanced ACL
{Configuring an IPv6 advanced ACL
•Configuring an Ethernet frame header ACL
(Optional.) Copying an ACL
(Optional.) Configuring packet filtering with ACLs
Configuring a basic ACL
This section describes procedures for configuring IPv4 and IPv6 basic ACLs.
4
Configuring an IPv4 basic ACL
IPv4 basic ACLs match packets based only on source IP addresses.
To configure an IPv4 basic ACL:
Step Command Remarks
1. Enter system view. system-view N/A
2. Create an IPv4 basic ACL
and enter its view. acl number acl-number [ name
acl-name ] [ match-order { auto |
config } ]
By default, no ACL exists.
IPv4 basic ACLs are numbered in
the range of 2000 to 2999.
You can use the acl name
acl-name command to enter the
view of a named ACL.
3. (Optional.) Configure a
description for the IPv4 basic
ACL. description text By default, an IPv4 basic ACL has
no ACL description.
4. (Optional.) Set the rule
numbering step. step step-value The default setting is 5.
5. Create or edit a rule.
rule [ rule-id ] { deny | permit }
[ counting | fragment |logging |
source {source-address
source-wildcard | any } |
time-range time-range-name |
vpn-instance
vpn-instance-name ] *
By default, an IPv4 basic ACL
does not contain any rule.
The logging keyword takes effect
only when the module (for
example, packet filtering) that
uses the ACL supports logging.
If an ACL is for outbound QoS
traffic classification or outbound
packet filtering, do not specify the
vpn-instance keyword.
6. (Optional.) Add or edit a rule
comment. rule rule-id comment text By default, no rule comments are
configured.
Configuring an IPv6 basic ACL
IPv6 basic ACLs match packets based only on source IP addresses.
To configure an IPv6 basic ACL:
Step Command Remarks
1. Enter system view. system-view N/A
2. Create an IPv6 basic ACL
view and enter its view.
acl ipv6 number acl-number
[ name acl-name ] [ match-order
{ auto | config } ]
By default, no ACL exists.
IPv6 basic ACLs are numbered in
the range of 2000 to 2999.
You can use the acl ipv6 name
acl-name command to enter the
view of a named ACL.
3. (Optional.) Configure a
description for the IPv6 basic
ACL. description text By default, an IPv6 basic ACL has
no ACL description.
4. (Optional.) Set the rule
numbering step. step step-value The default setting is 5.
5. Create or edit a rule. rule [ rule-id ] { deny | permit } By default, an IPv6 basic ACL
5
Step Command Remarks
[ counting | fragment |logging |
routing [ type routing-type ] |
source { source-address
source-prefix |
source-address/source-prefix |
any } | time-range
time-range-name | vpn-instance
vpn-instance-name ] *
does not contain any rule.
The logging keyword takes effect
only when the module (for
example, packet filtering) that
uses the ACL supports logging.
If an ACL is for QoS traffic
classification or packet filtering:
•Do not specify the fragment
keyword.
•Do not specify the
vpn-instance or routing
keyword if the ACL is for
outbound application.
6. (Optional.) Add or edit a rule
comment. rule rule-id comment text By default, no rule comments are
configured.
Configuring an advanced ACL
This section describes procedures for configuring IPv4 and IPv6 advancedACLs.
Configuring an IPv4 advanced ACL
IPv4 advanced ACLs match packets based on the following criteria:
•Source IP addresses.
•Destination IP addresses.
•Packet priorities.
•Protocol numbers.
•Other protocol header information, such as TCP/UDP source and destination port numbers,
TCP flags, ICMP message types, and ICMP message codes.
Compared to IPv4 basic ACLs, IPv4 advanced ACLs allow more flexible and accurate filtering.
To configure an IPv4 advanced ACL:
Step Command Remarks
1. Enter system view. system-view N/A
2. Create an IPv4 advanced
ACL and enter its view.
acl number acl-number [ name
acl-name ] [ match-order { auto |
config } ]
By default, no ACL exists.
IPv4 advanced ACLs are
numbered in the range of 3000 to
3999.
You can use the acl name
acl-name command to enter the
view of a named ACL.
3. (Optional.) Configure a
description for the IPv4
advanced ACL. description text By default, an IPv4 advanced ACL
has no ACL description.
4. (Optional.) Set the rule
numbering step. step step-value The default setting is 5.
5. Create or edit a rule. rule [ rule-id ] { deny | permit }
protocol [ { { ack ack-value | fin By default, an IPv4 advanced ACL
does not contain any rule.
6
Step Command Remarks
fin-value | psh psh-value | rst
rst-value | syn syn-value | urg
urg-value } * | established } |
counting | destination
{ dest-address dest-wildcard |
any } | destination-port operator
port1 [ port2 ] | { dscp dscp |
{ precedence precedence | tos
tos } * } | fragment | icmp-type
{ icmp-type [ icmp-code ] |
icmp-message } | logging |
source { source-address
source-wildcard | any } |
source-port operator port1
[ port2 ] | time-range
time-range-name | vpn-instance
vpn-instance-name ] *
The logging keyword takes effect
only when the module (for
example, packet filtering) that
uses the ACL supports logging.
If an ACL is for QoS traffic
classification or packet filtering:
•Do not specify the
vpn-instance keyword if the
ACL is for outbound
application.
•Do not specify neq for the
operator argument.
6. (Optional.) Add or edit a rule
comment. rule rule-id comment text By default, no rule comments are
configured.
Configuring an IPv6 advanced ACL
IPv6 advanced ACLs match packets based on the following criteria:
•Source IPv6 addresses.
•Destination IPv6 addresses.
•Packet priorities.
•Protocol numbers.
•Other protocol header fields such as the TCP/UDP source port number, TCP/UDP destination
port number, ICMPv6 message type, and ICMPv6 message code.
Compared to IPv6 basic ACLs, IPv6 advanced ACLs allow more flexible and accurate filtering.
To configure an IPv6 advanced ACL:
Step Command Remarks
1. Enter system
view. system-view N/A
2. Create an IPv6
advanced ACL
and enter its
view.
acl ipv6 number acl-number
[ name acl-name ]
[ match-order { auto |
config } ]
By default, no ACL exists.
IPv6 advanced ACLs are numbered in the range of
3000 to 3999.
You can use the acl ipv6 name acl-name
command to enter the view of a named ACL.
3. (Optional.)
Configure a
description for
the IPv6
advanced ACL.
description text By default, an IPv6 advanced ACL has no ACL
description.
4. (Optional.) Set
the rule
numbering step. step step-value The default setting is 5.
5. Create or edit a
rule.
rule [ rule-id ] { deny |
permit } protocol [ { { ack
ack-value | fin fin-value | psh
psh-value | rst rst-value | syn
By default, IPv6 advanced ACL does not contain
any rule.
The logging keyword takes effect only when the
7
Step Command Remarks
syn-value | urg urg-value } * |
established } | counting |
destination { dest-address
dest-prefix |
dest-address/dest-prefix |
any } | destination-port
operator port1 [ port2 ] | dscp
dscp |flow-label
flow-label-value | fragment |
icmp6-type { icmp6-type
icmp6-code |
icmp6-message } | logging |
routing [ type routing-type ] |
hop-by-hop [ type hop-type ]
| source { source-address
source-prefix |
source-address/source-prefix
| any } | source-port operator
port1 [ port2 ] | time-range
time-range-name |
vpn-instance
vpn-instance-name ] *
module (for example, packet filtering) that uses the
ACL supports logging.
If an ACL is for QoS traffic classification or packet
filtering:
•Do not specify the fragment keyword.
•Do not specify neq for the operator argument.
•Do not specify the vpn-instance, routing,
hop-by-hop, or flow-label keyword if the ACL
is for outbound application.
•Do not specify ipv6-ah for the protocol
argument, nor set its value to 0, 43, 44, 51, or
60, if the ACL is for outbound application.
6. (Optional.) Add
or edit a rule
comment. rule rule-id comment text By default, no rule comments are configured.
NOTE:
If an ACL is to match information in the IPv6 packet payload, it can only match packets with one
extension header. It cannot match packets with two or more extension headers or with the
Encapsulating Security Payload Header.
Configuring an Ethernet frame header ACL
Ethernet frame header ACLs, also called "Layer 2 ACLs," match packets based on Layer 2 protocol
header fields, such as:
•Source MAC address.
•Destination MAC address.
•802.1p priority (VLAN priority).
•Link layer protocol type.
To configure an Ethernet frame headerACL:
Step Command Remarks
1. Enter system view. system-view N/A
2. Create an Ethernet frame
header ACL and enter its
view.
acl number acl-number [ name
acl-name ] [ match-order { auto |
config } ]
By default, no ACL exists.
Ethernet frame header ACLs are
numbered in the range of 4000 to
4999.
You can use the acl name
acl-name command to enter the
view of a named ACL.
3. (Optional.) Configure a
description for the Ethernet description text By default, an Ethernet frame
header ACL has no ACL
8
Step Command Remarks
frame header ACL. description.
4. (Optional.) Set the rule
numbering step. step step-value The default setting is 5.
5. Create or edit a rule.
rule [ rule-id ] { deny | permit }
[ cos vlan-pri | counting |
dest-mac dest-address
dest-mask | { lsap lsap-type
lsap-type-mask | type
protocol-type
protocol-type-mask } |
source-mac source-address
source-mask | time-range
time-range-name ] *
By default,an Ethernet frame
header ACL does not contain any
rule.
If an Ethernet frame header ACL
is used for packet filtering or QoS
traffic classification and the lsap
keyword is used, the lsap-type
argument value must be AAAA,
and the lsap-type-mask argument
value must be FFFF. Otherwise,
the ACL does not take effect.
6. (Optional.) Add or edit a rule
comment. rule rule-id comment text By default, no rule comments are
configured.
Copying an ACL
You can create an ACL by copying an existing ACL (source ACL). The new ACL (destination ACL)
has the same properties and content as the source ACL, but not the same ACL number and name.
To successfully copy an ACL, make sure:
•The destinationACL number is from the same category as the source ACL number.
•The source ACL already exists, but the destination ACL does not.
To copy an ACL:
Step Command
1. Enter system view. system-view
2. Copy an existing ACL to create a newACL. acl [ ipv6 ] copy { source-acl-number | name
source-acl-name } to { dest-acl-number | name
dest-acl-name }
Configuring packet filtering with ACLs
This section describes procedures for applying an ACL to filter incoming or outgoing IPv4 or IPv6
packets on the specified interface.
NOTE:
The ACL-based packet filter feature is available on Layer 2 and Layer 3 Ethernet interfaces, and
VLAN interfaces. The term "interface" in this section collectively refers to these types of interfaces.
You can use the port link-mode command to configure an Ethernet port as a Layer 2 or Layer 3
interface (see Layer 2—LAN Switching Configuration Guide).
9
Applying an ACL to an interface for packet filtering
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter interface view. interface interface-type
interface-number
N/A
3. Apply an ACLto the interface
to filter packets. packet-filter [ ipv6 ] { acl-number
| name acl-name } { inbound |
outbound } [ hardware-count ]
By default, an interface does not
filter packets.
You can apply only one ACL to the
same direction of an interface.
Configuring the applicable scope of packet filtering on a
VLAN interface
You can configure the packet filtering on a VLAN interface to filter the following packets:
•Packets forwarded at Layer 3 by the VLAN interface.
•All packets, including packets forwarded at Layer 3 by the VLAN interface and packets
forwarded at Layer 2 by the physical ports associated with the VLAN interface.
To configure the applicable scope of packet filtering on a VLAN interface:
Step Command Remarks
1. Enter system view. system-view N/A
2. Create a VLAN interface
and enter its view. interface vlan-interface
vlan-interface-id
If the VLAN interface already exists,
you directly enter its view.
By default, no VLAN interface exists.
3. Specify the applicable
scope of packet filtering on
the VLAN interface. packet-filter filter [ route | all ] By default, the packet filtering filters
packets forwarded at Layer 3.
Setting the interval for generating and outputting packet
filtering logs
After you set the interval, the device periodically generates and outputs the packet filtering logs to the
information center, including the number of matching packets and the matchedACL rules. For more
information about information center, see Network Management and Monitoring Configuration
Guide.
To set the interval for generating and outputting packet filtering logs:
Step Command Remarks
1. Enter system view. system-view N/A
2. Set the interval for
generating and outputting
packet filtering logs. acl [ ipv6 ] logging interval
interval The default setting is 0 minutes,
which mean that no packet
filtering logs are generated.
10
Setting the packet filtering default action
Step Command Remarks
1. Enter system view. system-view N/A
2. Set the packet filtering
default action to deny. packet-filter default deny By default, the packet filter
permits packets that do not match
any ACL rule to pass.
Displaying and maintaining ACLs
Execute display commands in any view and reset commands in user view.
Task Command
Display ACL configuration and match statistics. display acl [ ipv6 ] { acl-number | all | name
acl-name }
Display whether an ACL has been successfully
applied to an interface for packet filtering.
display packet-filter { interface [ interface-type
interface-number ] [ inbound | outbound ] |
interface vlan-interface vlan-interface-number
[ inbound | outbound ] [ slot slot-number ] }
Display match statistics for packet filtering ACLs.
display packet-filter statistics interface
interface-type interface-number { inbound |
outbound } [ [ ipv6 ] { acl-number | name
acl-name } ] [ brief ]
Display the accumulated statistics for packet filtering
ACLs.
display packet-filter statistics sum { inbound |
outbound } [ ipv6 ] { acl-number | name acl-name }
[ brief ]
Display detailed ACL packet filtering information.
display packet-filter verbose interface
interface-type interface-number { inbound |
outbound } [ [ ipv6 ] { acl-number | name
acl-name } ] [ slot slot-number ]
Display QoS and ACL resource usage. display qos-acl resource [ slot slot-number ]
Clear ACL statistics. reset acl [ ipv6 ] counter { acl-number | all | name
acl-name }
Clear match statistics (including the accumulated
statistics) for packet filtering ACLs.
reset packet-filter statistics interface
[ interface-type interface-number ] { inbound |
outbound } [ [ ipv6 ] { acl-number | name
acl-name } ]
ACL configuration example
Network requirements
A company interconnects its departments through DeviceA. Configure an ACL to:
•Permit access from the President's office at any time to the financial database server.
•Permit access from the Financial department to the database server only during working hours
(from 8:00 to 18:00) on working days.
•Deny access from any other department to the database server.
11
Figure 1 Network diagram
Configuration procedure
# Create a periodic time range from 8:00 to 18:00 on working days.
<DeviceA> system-view
[DeviceA] time-range work 08:0 to 18:00 working-day
# Create an IPv4 advanced ACL numbered 3000 and configure three rules in the ACL. One rule
permits access from the President's office to the financial database server, one rule permits access
from the Financial department to the database server during working hours, and one rule denies
access from any other department to the database server.
[DeviceA] acl number 3000
[DeviceA-acl-adv-3000] rule permit ip source 192.168.1.0 0.0.0.255 destination
192.168.0.100 0
[DeviceA-acl-adv-3000] rule permit ip source 192.168.2.0 0.0.0.255 destination
192.168.0.100 0 time-range work
[DeviceA-acl-adv-3000] rule deny ip source any destination 192.168.0.100 0
[DeviceA-acl-adv-3000] quit
# Apply IPv4 advanced ACL 3000 to filter outgoing packets on interface GigabitEthernet 1/0/1.
[DeviceA] interface gigabitethernet 1/0/1
[DeviceA-GigabitEthernet1/0/1] packet-filter 3000 outbound
[DeviceA-GigabitEthernet1/0/1] quit
Verifying the configuration
# Ping the database server from a PC in the Financial department during the working hours. (All PCs
in this example use Windows XP).
C:\> ping 192.168.0.100
Pinging 192.168.0.100 with 32 bytes of data:
Reply from 192.168.0.100: bytes=32 time=1ms TTL=255
Reply from 192.168.0.100: bytes=32 time<1ms TTL=255
President's office
192.168.1.0/24 Financial department
192.168.2.0/24 Marketing department
192.168.3.0/24
Device A
GE1/0/1
GE1/0/4GE1/0/2
GE1/0/3
Financial database server
192.168.0.100/24
12
Reply from 192.168.0.100: bytes=32 time<1ms TTL=255
Reply from 192.168.0.100: bytes=32 time<1ms TTL=255
Ping statistics for 192.168.0.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
The output shows that the database server can be pinged.
# Ping the database server from a PC in the Marketing department during the working hours.
C:\> ping 192.168.0.100
Pinging 192.168.0.100 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
The output shows the database server cannot be pinged.
# Display configuration and match statistics for IPv4 advanced ACL 3000 on Device A during the
working hours.
[DeviceA] display acl 3000
Advanced ACL 3000, named -none-, 3 rules,
ACL's step is 5
rule 0 permit ip source 192.168.1.0 0.0.0.255 destination 192.168.0.100 0
rule 5 permit ip source 192.168.2.0 0.0.0.255 destination 192.168.0.100 0 time-range work
(Active)
rule 10 deny ip destination 192.168.0.100 0
The output shows that rule 5 is active.
13
QoS overview
In data communications, Quality of Service (QoS) provides differentiated service guarantees for
diversified traffic in terms of bandwidth, delay, jitter, and drop rate, all of which can affect QoS.
Network resources are limited. When configuring a QoS scheme, you must consider the
characteristics of different applications. For example, when bandwidth is fixed, more bandwidth used
by one user leaves less bandwidth for others. QoS prioritizes traffic to balance the interests of users
and manages network resources.
The following section describes typical QoS service models and widely used QoS techniques.
QoS service models
This section describes several typical QoS service models.
Best-effort service model
The best-effort model is a single-service model.As the simplest service model, the best-effort model
is not as reliable as other models and does not guarantee delay-free delivery.
The best-effort service model is the default model for the Internet and applies to most network
applications. It uses the First In First Out (FIFO) queuing mechanism.
IntServ model
The integrated service (IntServ) model is a multiple-service model that can accommodate diverse
QoS requirements. This service model provides the most granularly differentiated QoS by identifying
and guaranteeing definite QoS for each data flow.
In the IntServ model, an application must request service from the network before it sends data.
IntServ signals the service request with the RSVP. All nodes receiving the request reserve resources
as requested and maintain state information for the application flow.
The IntServ model demands high storage and processing capabilities because it requires all nodes
along the transmission path to maintain resource state information for each flow. This model is
suitable for small-sized or edge networks, but not large-sized networks, for example, the core layer
of the Internet, where billions of flows are present.
DiffServ model
The differentiated service (DiffServ) model is a multiple-service model that can meet diverse QoS
requirements. It is easy to implement and extend. DiffServ does not signal the network to reserve
resources before sending data, as IntServ does.
QoS techniques overview
The QoS techniques include the following features:
•Traffic classification.
•Traffic policing.
•Traffic shaping.
•Rate limit.
14
•Congestion management.
•Congestion avoidance.
The following section briefly introduces these QoS techniques.
All QoS techniques in this document are based on the DiffServ model.
Deploying QoS in a network
Figure 2 Position of the QoS techniques in a network
As shown in Figure 2, traffic classification, traffic shaping, traffic policing, congestion management,
and congestion avoidance mainly implement the following features:
•Traffic classification—Uses match criteria to assign packets with the same characteristics to
a traffic class. Based on traffic classes, you can provide differentiated services.
•Traffic policing—Polices flows and imposes penalties to prevent aggressive use of network
resources. You can apply traffic policing to both incoming and outgoing traffic of a port.
•Traffic shaping—Adapts the output rate of traffic to the network resources available on the
downstream device to eliminate packet drops. Traffic shaping usually applies to the outgoing
traffic of a port.
•Congestion management—Provides a resource scheduling policy to determine the packet
forwarding sequence when congestion occurs. Congestion management usually applies to the
outgoing traffic of a port.
•Congestion avoidance—Monitors the network resource usage. It is usually applied to the
outgoing traffic of a port. When congestion worsens, congestion avoidance reduces the queue
length by dropping packets.
Other manuals for FlexNetwork 5510 HI Series
12
Table of contents
Other HPE Network Router manuals
HPE
HPE FlexFabric 5930 Series User manual
HPE
HPE FlexNetwork HSR6800 series User manual
HPE
HPE FlexNetwork VSR1000 User manual
HPE
HPE FlexNetwork 5130 HI SERIES User manual
HPE
HPE FlexNetwork MSR3012 Installation manual
HPE
HPE FlexNetwork MSR Series User manual
HPE
HPE FlexNetwork MSR Series User manual
HPE
HPE FlexNetwork MSR Series User manual
HPE
HPE FlexNetwork HSR6800 series User manual
HPE
HPE FlexNetwork 5510 HI Series User manual
HPE
HPE FlexNetwork MSR958 User manual
HPE
HPE FlexNetwork VSR1000 User manual
HPE
HPE FlexFabric 7900 Series User manual
HPE
HPE FlexNetwork HSR6800 series User manual
HPE
HPE FlexNetwork 5510 HI Series User manual
HPE
HPE FlexNetwork MSR Series User manual
HPE
HPE FlexNetwork HSR6600 User manual
HPE
HPE FlexNetwork HSR6800 series User manual
HPE
HPE FlexNetwork HSR6600 User manual
HPE
HPE SN2700M Instructions for use
Popular Network Router manuals by other brands
Titan
Titan UMAP 2110 Hardware installation and user's guide
Luxibel
Luxibel LX195 user manual
ZyXEL Communications
ZyXEL Communications Dimension ES-4124 L3 Support notes
TP-Link
TP-Link TL-WR840N Quick installation guide
D-Link
D-Link DIR-879 Quick install guide
Advantech
Advantech B&B SmartWorx ESWGP506-2SFP-T quick start guide
