1-5
z
Effective Period of an IPv6 ACL
IPv6 ACL Classification
IPv6 ACLs, identified by ACL numbers, fall into three categories, as shown in
Table 1-2
IPv6 ACL categories
Category
ACL number
Matching criteria
Basic IPv6 ACL
2000 to 2999
Source IPv6 address
Advanced IPv6 ACL
3000 to 3999
Source IPv6 address, destination IPv6 address,
protocol carried over IPv6, and other Layer 3 or Layer
4 protocol header information
IPv6 ACL Naming
When creating an IPv6 ACL, you can specify a unique name for it. Afterwards, you can identify the IPv6
ACL by its name.
An IPv6 ACL can have only one name. Whether to specify a name for an ACL is up to you. After creating
an ACL, you cannot specify a name for it, nor can you change or remove its name.
The name of an IPv6 ACL must be unique among IPv6 ACLs. However, an IPv6 ACL and an IPv4 ACL
can share the same name.
IPv6 ACL Match Order
Similar to IPv4 ACLs, an IPv6 ACL consists of multiple rules, each of which specifies different matching
criteria. These criteria may have overlapping or conflicting parts. The match order is for determining
how a packet should be matched against the rules.
Two match orders are available for IPv6 ACLs:
z
config
: Packets are compared against ACL rules in the order the rules are configured.
z
auto
: Packets are compared against ACL rules in the depth-first match order.
The term depth-first match has different meanings for different types of IPv6 ACLs:
Depth-first match for a basic IPv6 ACL
The following shows how your device performs depth-first match in a basic IPv6 ACL:
1) Sort rules by source IPv6 address prefix first and compare packets against the rule configured with
a longer prefix for the source IPv6 address.
2) In case of a tie, compare packets against the rule configured first.
Depth-first match for an advanced IPv6 ACL
The following shows how your device performs depth-first match in an advanced IPv6 ACL:
Summary of Contents for S5500-SI Series
Page 161: ...3 10 GigabitEthernet1 0 1 2 MANUAL...
Page 220: ...1 7 Clearing ARP entries from the ARP table may cause communication failures...
Page 331: ...1 7 1 1 ms 1 ms 1 ms 1 1 6 1 2 1 ms 1 ms 1 ms 1 1 4 1 3 1 ms 1 ms 1 ms 1 1 2 2 Trace complete...
Page 493: ...2 8...
Page 1111: ...1 10 Installing patches Installation completed and patches will continue to run after reboot...