CONFIG-STD-NACL mode
seq
sequence-number
{deny | permit} {source [mask] | any | host
ip-address
} [log [threshold-
in-msgs
count
] ]
2
Specify the interval in minutes at which ACL logs must be generated. You can enter an interval in the range of 1-10 minutes. The
default frequency at which ACL logs are generated is 5 minutes. If ACL logging is stopped because the configured threshold has
exceeded, it is re-enabled after the logging interval period elapses. ACL logging is supported for standard and extended IPv4 ACLs,
IPv6 ACLs, and standard and extended MAC ACLs. Configure ACL logging only on ACLs that are applied to ingress interfaces; you
cannot enable logging for ACLs that are associated with egress interfaces.
CONFIG-STD-NACL mode
seq
sequence-number
{deny | permit} {source [mask] | any | host
ip-address
} [log [interval
minutes
]]
Flow-Based Monitoring Support for ACLs
Flow-based monitoring conserves bandwidth by monitoring only the specified traffic instead of all traffic on the interface. It is available for
Layer 2 and Layer 3 ingress traffic. You can specify traffic using standard or extended access-lists. This mechanism copies incoming
packets that matches the ACL rules applied on the ingress 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).
The port mirroring application maintains and performs all the monitoring operations on the chassis. ACL information is sent to the ACL
manager, which in turn notifies the ACL agent to add entries in the CAM area. Duplicate entries in the ACL are not saved.
When a packet arrives at a port that is being monitored, the packet is validated against the configured ACL rules. If the packet matches an
ACL rule, the system examines the corresponding flow processor to perform the action specified for that port. If the mirroring action is set
in the flow processor entry, the destination port details, to which the mirrored information must be sent, are sent to the destination port.
When a stack unit is reset or a stack unit undergoes a failure, the ACL agent registers with the port mirroring application. The port mirroring
utility downloads the monitoring configuration to the ACL agent. The interface manager notifies the port mirroring application about the
removal of an interface when an ACL entry associated with that interface to is deleted.
Behavior of Flow-Based Monitoring
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 interfaces are examined, and
appropriate ACLs can be applied in the ingress direction. By default, flow-based monitoring is not enabled.
You must specify the monitor option with the
permit, deny
, or
seq
command for ACLs that are assigned to the source or the
monitored port (MD) to enable the evaluation and replication of traffic that is traversing to the destination port. Enter the keyword
monitor
with the
seq
,
permit
, or
deny
command for the ACL rules to allow or drop IPv4, IPv6, ARP, UDP, EtherType, ICMP, and TCP
packets. The ACL rule describes the traffic that you want to monitor, and the ACL in which you are creating the rule will be applied to the
monitored interface. Flow monitoring is supported for standard and extended IPv4 ACLs, standard and extended IPv6 ACLs, and standard
and extended MAC ACLs.
CONFIG-STD-NACL mode
seq
sequence-number
{deny | permit} {source [mask] | any | host
ip-address
} [count [byte]]
[order] [fragments] [log [threshold-in-msgs count]] [monitor
session-ID
]
If the number of monitoring sessions increases, inter-process communication (IPC) bandwidth utilization will be high. The ACL manager
might require a large bandwidth when you assign an ACL, with many entries, to an interface.
Access Control Lists (ACLs)
137
Содержание S4048T-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 11 2 1 ...
Страница 148: ...Figure 10 BFD Three Way Handshake State Changes 148 Bidirectional Forwarding Detection BFD ...
Страница 251: ...Dell Control Plane Policing CoPP 251 ...
Страница 363: ... RPM Synchronization GARP VLAN Registration Protocol GVRP 363 ...
Страница 511: ...Figure 64 Inspecting the LAG Configuration Link Aggregation Control Protocol LACP 511 ...
Страница 512: ...Figure 65 Inspecting Configuration of LAG 10 on ALPHA 512 Link Aggregation Control Protocol LACP ...
Страница 515: ...Figure 67 Inspecting a LAG Port on BRAVO Using the show interface Command Link Aggregation Control Protocol LACP 515 ...
Страница 516: ...Figure 68 Inspecting LAG 10 Using the show interfaces port channel Command 516 Link Aggregation Control Protocol LACP ...
Страница 558: ...Figure 84 Configuring Interfaces for MSDP 558 Multicast Source Discovery Protocol MSDP ...
Страница 559: ...Figure 85 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 559 ...
Страница 560: ...Figure 86 Configuring PIM in Multiple Routing Domains 560 Multicast Source Discovery Protocol MSDP ...
Страница 564: ...Figure 88 MSDP Default Peer Scenario 2 564 Multicast Source Discovery Protocol MSDP ...
Страница 565: ...Figure 89 MSDP Default Peer Scenario 3 Multicast Source Discovery Protocol MSDP 565 ...
Страница 729: ...protocol spanning tree pvst no disable vlan 300 bridge priority 4096 Per VLAN Spanning Tree Plus PVST 729 ...
Страница 841: ...Figure 115 Single and Double Tag TPID Match Service Provider Bridging 841 ...
Страница 842: ...Figure 116 Single and Double Tag First byte TPID Match 842 Service Provider Bridging ...