Dell S3100 EMC Command Line Reference Guide for the Series 9.14.2.5 - Page 292

Version 9.4(0.0) 9.3.0.0 Description Added support for flow-based monitoring on the S4810, S4820T, S6000, and Z9000 platforms. 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 tcp (for IPv6 ACLs) Configure a filter to pass TCP packets that match the filter criteria. Syntax permit tcp {source address mask | any | host ipv6-address} [operator port [port]] {destination address | any | host ipv6-address} [bit] [operator port [port]] [ttl operator] [count [byte]] [log [interval minutes] [threshold-inmsgs [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 tcp {source address mask | any | host ipv6-address} {destination address | any | host ipv6-address} command. Parameters source address mask Enter a network mask in /prefix format (/x). any Enter the keyword any to specify that all routes are subject to the filter. host ipv6-address Enter the keyword host then the IP address to specify a host IP address. destination address Enter the IPv6 address of the network or host to which the packets are sent. bit Enter a flag or combination of bits: • ack: acknowledgement field • fin: finish (no more data from the user) • psh: push function • rst: reset the connection • syn: synchronize sequence numbers • urg: urgent field operator (OPTIONAL) Enter one of the following logical operand: • eq = equal to • neq = not equal to • gt = greater than 292 Access Control Lists (ACL)