
remark
8
this remark corresponds to permit ip any host 1.1.1.2
seq
8
permit ip any host 1.1.1.2
seq
10
permit ip any host 1.1.1.3
seq
12
permit ip any host 1.1.1.4
Remarks that do not have a corresponding rule are incremented as a rule. These two mechanisms allow remarks to retain their
original position in the list. The following example shows remark 10 corresponding to rule 10 and as such, they have the same number
before and after the command is entered. Remark 4 is incremented as a rule, and all rules have retained their original positions.
Dell(config-ext-nacl)# show config
!
ip access-list extended test
remark 4 XYZ
remark 5 this remark corresponds to permit any host 1.1.1.1
seq 5 permit ip any host 1.1.1.1
remark 9 ABC
remark 10 this remark corresponds to permit ip any host 1.1.1.2
seq 10 permit ip any host 1.1.1.2
seq 15 permit ip any host 1.1.1.3
seq 20 permit ip any host 1.1.1.4
Dell# end
Dell# resequence access-list ipv4 test 2 2
Dell# show running-config acl
!
ip access-list extended test
remark 2 XYZ
remark 4 this remark corresponds to permit any host 1.1.1.1
seq 4 permit ip any host 1.1.1.1
remark 6 this remark has no corresponding rule
remark 8 this remark corresponds to permit ip any host 1.1.1.2
seq 8 permit ip any host 1.1.1.2
seq 10 permit ip any host 1.1.1.3
seq 12 permit ip any host 1.1.1.4
Route Maps
Although route maps are similar to ACLs and prefix lists in that they consist of a series of commands that contain a matching
criterion and an action, route maps can modify parameters in matching packets.
Implementation Information
ACLs and prefix lists can only drop or forward the packet or traffic. Route maps process routes for route redistribution. For example,
a route map can be called to filter only specific routes and to add a metric.
Route maps also have an “implicit deny.” Unlike ACLs and prefix lists; however, where the packet or traffic is dropped, in route maps,
if a route does not match any of the route map conditions, the route is not redistributed.
The implementation of route maps allows route maps with the no match or no set commands. When there is no match command, all
traffic matches the route map and the set command applies.
Logging of ACL Processes
This functionality is supported on the platform.
To assist in the administration and management of traffic that traverses the device after being validated by the configured ACLs, you
can enable the generation of logs for access control list (ACL) processes. Although you can configure ACLs with the required permit
or deny filters to provide access to the incoming packet or disallow access to a particular user, it is also necessary to monitor and
examine the traffic that passes through the device. To evaluate network traffic that is subjected to ACLs, configure the logs to be
triggered for ACL operations. This functionality is primarily needed for network supervision and maintenance activities of the handled
subscriber traffic.
134
Access Control Lists (ACLs)
Содержание S4048-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Страница 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Страница 477: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 477 ...
Страница 480: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command 480 Link Aggregation Control Protocol LACP ...
Страница 481: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 481 ...
Страница 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Страница 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Страница 524: ...Figure 89 Configuring PIM in Multiple Routing Domains 524 Multicast Source Discovery Protocol MSDP ...
Страница 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Страница 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Страница 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Страница 633: ...Policy based Routing PBR 633 ...
Страница 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Страница 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...