The default frequency at which ACL logs are generated is five minutes. By default, flow-based monitoring is not
enabled.
Command Modes
CONFIGURATION-EXTENDED-ACCESS-LIST
Command History
This guide is platform-specific. For command information about other platforms, see the relevant
Dell Networking
OS Command Line Reference Guide
.
Version
Description
9.8(0.0P5)
Introduced on the S4048-ON.
9.8(0.0P2)
Introduced on the S3048-ON.
9.7(0.0)
Introduced on the S6000–ON.
9.4(0.0)
Added support for flow-based monitoring on the S4810, S4820T, S6000, and Z9000
platforms.
9.3(0.0)
Added support for logging of ACLs on the S4810, S4820T, and Z9000 platforms.
Usage Information
When the configured maximum threshold is exceeded, generation of logs is stopped. When the interval at which
ACL logs are configured to be recorded expires, the subsequent, fresh interval timer is started and the packet
count for that new interval commences from zero. If ACL logging was stopped previously because the configured
threshold is exceeded, it is re-enabled for this new interval.
If ACL logging is stopped because the configured threshold is exceeded, it is re-enabled after the logging interval
period elapses. ACL logging is supported for standard and extended IPv4 ACLs, IPv6 ACLs, and MAC ACLs. You
can configure ACL logging only on ACLs that are applied to ingress interfaces; you cannot enable logging for ACLs
that are associated with egress interfaces.
You can activate flow-based monitoring for a monitoring session by entering the
flow-based enable
command in the Monitor Session mode. When you enable this capability, traffic with particular flows that are
traversing through the ingress and egress interfaces are examined and, appropriate ACLs can be applied in both
the ingress and egress direction. Flow-based monitoring conserves bandwidth by monitoring only specified traffic
instead all traffic on the interface. This feature is particularly useful when looking for malicious traffic. It is available
for Layer 2 and Layer 3 ingress and egress traffic. You may specify traffic using standard or extended access-lists.
This mechanism copies all incoming or outgoing packets on one port and forwards (mirrors) them to another port.
The source port is the monitored port (MD) and the destination port is the monitoring port (MG).
permit ether-type (for Extended MAC ACLs)
Configure a filter that allows traffic with specified types of Ethernet packets. This command is supported only on 12-port GE line cards with
SFP optics. For specifications, refer to your line card documentation.
Syntax
permit ether-type
protocol-type-number
{
destination-mac-address mac-address-
mask
| any} vlan
vlan-id
{
source-mac-address mac-address-mask
| any} [count
[byte]] [order] [log [interval
minutes
] [threshold-in-msgs [
count
]] [monitor]
To remove this filter, you have two choices:
•
Use the
no seq
sequence-number
command if you know the filter’s sequence number.
•
Use the
no permit ether-type
protocol-type-number
{
destination-mac-address mac-
address-mask
| any} vlan
vlan-id
{
source-mac-address mac-address-mask
| any}
command.
Access Control Lists (ACL)
299
Содержание S6100
Страница 1: ...Dell Command Line Reference Guide for the S6100 ON System 9 11 2 0P1 ...
Страница 474: ...protocol list ttl0 ttl1 Dell 474 Control Plane Policing CoPP ...
Страница 979: ... show lldp neighbors display the LLDP neighbors Link Layer Discovery Protocol LLDP 979 ...
Страница 1627: ... uplink state group creates an uplink state group and enables the tracking of upstream links Uplink Failure Detection UFD 1627 ...