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

Configuring an IPv6 advanced ACL

Page 12 highlights

Step Command Remarks 2. Create an IPv4 advanced ACL acl number acl-number [ name and enter its view. acl-name ] [ match-order { auto | config } ] 3. (Optional.) Configure a description for the IPv4 advanced ACL. 4. (Optional.) Set the rule numbering step. description text step step-value 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. By default, an IPv4 advanced ACL has no ACL description. 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 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 ] * By default, an IPv4 advanced 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 IPv4 advanced ACL is for QoS traffic classification or packet filtering, do not specify the vpn-instance keyword or 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 source IPv6 addresses, destination IPv6 addresses, packet priorities, protocols carried over IPv6, and 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 1. Enter system view. Command system-view Remarks N/A 6

  • 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

6
Step
Command
Remarks
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
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
] *
By default, an IPv4 advanced 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 IPv4 advanced ACL is for QoS
traffic classification or packet
filtering, do not specify the
vpn-instance
keyword or 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 source IPv6 addresses, destination IPv6 addresses,
packet priorities, protocols carried over IPv6, and 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