{deny | permit} udp {
source mask
| any | host
ip-address
}} [count [byte]] [order] [monitor
[
session-id
]] [fragments]
When you use the
log
keyword, the CP logs details about the packets that match. Depending on how many packets match the log entry
and at what rate, the CP may become busy as it has to log these packets’ details. The following example shows an extended IP ACL in
which the sequence numbers were assigned by the software. The filters were assigned sequence numbers based on the order in which
they were configured (for example, the first filter was given the lowest sequence number). The
show config
command in IP ACCESS
LIST mode displays the two filters with the sequence numbers 5 and 10.
Example of Viewing Filter Sequence for a Specified Extended ACL
Dell(config-ext-nacl)#deny tcp host 123.55.34.0 any
Dell(config-ext-nacl)#permit udp 154.44.123.34 0.0.255.255 host 34.6.0.0 monitor 111
Dell(config-ext-nacl)#show config
!
ip access-list extended nimule
seq 5 deny tcp host 123.55.34.0 any
seq 10 permit udp 154.44.0.0 0.0.255.255 host 34.6.0.0 monitor 111
Dell(config-ext-nacl)#
To view all configured IP ACLs and the number of packets processed through the ACL, use the
show ip accounting access-list
command in EXEC Privilege mode, as shown in the first example in
Configure a Standard IP ACL Filter
Configure Layer 2 and Layer 3 ACLs
Both Layer 2 and Layer 3 ACLs may be configured on an interface in Layer 2 mode.
If both L2 and L3 ACLs are applied to an interface, the following rules apply:
•
When Dell Networking OS routes the packets, only the L3 ACL governs them because they are not filtered against an L2 ACL.
•
When Dell Networking OS switches the packets, first the L3 ACL filters them, then the L2 ACL filters them.
•
When Dell Networking OS switches the packets, the egress L3 ACL filters the packet.
For the following features, if you enable counters on rules that have already been configured and a new rule is either inserted or prepended,
all the existing counters are reset:
•
L2 ingress access list
•
L3 egress access list
•
L2 egress access list
If a rule is simply appended, existing counters are not affected.
Table 7. L2 and L3 Filtering on Switched Packets
L2 ACL Behavior
L3 ACL Behavior
Decision on Targeted Traffic
Deny
Deny
L3 ACL denies.
Deny
Permit
L3 ACL permits.
Permit
Deny
L3 ACL denies.
Permit
Permit
L3 ACL permits.
NOTE:
If you configure an interface as a vlan-stack access port, only the L2 ACL filters the packets. The L3 ACL applied to such
a port does not affect traffic. That is, existing rules for other features (such as trace-list, policy-based routing [PBR], and QoS)
are applied to the permitted traffic.
For information about MAC ACLs, refer to
122
Access Control Lists (ACLs)
Summary of Contents for S3048-ON
Page 1: ...Dell Configuration Guide for the S3048 ON System 9 11 2 5 ...
Page 137: ...0 Gi 1 1 Gi 1 2 rx Flow N A N A 0 0 No N A N A yes Access Control Lists ACLs 137 ...
Page 142: ...Figure 10 BFD Three Way Handshake State Changes 142 Bidirectional Forwarding Detection BFD ...
Page 241: ...Dell Control Plane Policing CoPP 241 ...
Page 287: ... RPM Synchronization GARP VLAN Registration Protocol GVRP 287 ...
Page 428: ...Figure 53 Inspecting the LAG Configuration 428 Link Aggregation Control Protocol LACP ...
Page 477: ...Figure 73 Configuring Interfaces for MSDP Multicast Source Discovery Protocol MSDP 477 ...
Page 478: ...Figure 74 Configuring OSPF and BGP for MSDP 478 Multicast Source Discovery Protocol MSDP ...
Page 483: ...Figure 77 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 483 ...
Page 484: ...Figure 78 MSDP Default Peer Scenario 3 484 Multicast Source Discovery Protocol MSDP ...
Page 745: ...Figure 104 Single and Double Tag TPID Match Service Provider Bridging 745 ...
Page 746: ...Figure 105 Single and Double Tag First byte TPID Match 746 Service Provider Bridging ...