HP 6125XLG R2306-HP 6125XLG Blade Switch ACL and QoS Configuration Guide - Page 11

Configuring an advanced ACL

Get HP 6125XLG PDF manuals and user guides View all HP 6125XLG manuals
Add to My Manuals
Save this manual to your list of manuals

Page 11 highlights

Step 1. Enter system view. Command system-view 2. Create an IPv6 basic ACL view and enter its view. acl ipv6 number acl-number [ name acl-name ] [ match-order { auto | config } ] 3. (Optional.) Configure a description for the IPv6 basic description text ACL. 4. (Optional.) Set the rule numbering step. step step-value 5. Create or edit a rule. rule [ rule-id ] { deny | permit } [ 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 ] * 6. (Optional.) Add or edit a rule comment. rule rule-id comment text Remarks N/A 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. By default, an IPv6 basic ACL has no ACL description. The default setting is 5. By default, an IPv6 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 IPv6 basic ACL is for QoS traffic classification or packet filtering, do not specify the vpn-instance or fragment keyword, and do not specify the routing keyword for outbound traffic. By default, no rule comments are configured. Configuring an advanced ACL This section describes procedures for configuring IPv4 and IPv6 advanced ACLs. Configuring an IPv4 advanced ACL IPv4 advanced ACLs match packets based on source IP addresses, destination IP addresses, packet priorities, protocols over IP, and 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 1. Enter system view. Command system-view Remarks N/A 5

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
5
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
}
[
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
] *
By default, an IPv6 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 IPv6 basic ACL is for QoS
traffic classification or packet
filtering, do not specify the
vpn-instance
or
fragment
keyword, and do not specify the
routing
keyword for outbound
traffic.
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 advanced ACLs.
Configuring an IPv4 advanced ACL
IPv4 advanced ACLs match packets based on source IP addresses, destination IP addresses, packet
priorities, protocols over IP, and 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