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]
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.
The ACL agent module saves monitoring details in its local database and also in the CAM region to monitor
packets that match the specified criterion. The ACL agent maintains data on the source port, the destination
port, and the endpoint to which the packet must be forwarded when a match occurs with the ACL entry.
If you configure the
flow-based enable
command and do not apply an ACL on the source port or the
monitored port, both flow-based monitoring and port mirroring do not function. Flow-based monitoring is
supported only for ingress traffic and not for egress packets.
The port mirroring application maintains a database that contains all monitoring sessions (including port
monitor sessions). It has information regarding the sessions that are enabled for flow-based monitoring and
those sessions that are not enabled for flow-based monitoring. It downloads monitoring configuration to the
ACL agent whenever the ACL agent is registered with the port mirroring application or when flow-based
monitoring is enabled.
The
show monitor session
session-id
command has been enhanced to display the Type field in the
output, which indicates whether a particular session is enabled for flow-monitoring.
Example Output of the
show
Command
Dell(conf-mon-sess-0)#do show monitor session 0
SessID Source Destination Dir Mode Source IP Dest IP
------ ------ ----------- --- ---- --------- --------
0 Te 1/1 Te 1/2 rx Flow N/A N/
A
The
show config
command has been modified to display monitoring configuration in a particular session.
Example Output of the
show
Command
(conf-mon-sess-11)#show config
!
monitor session 11
flow-based enable
Access Control Lists (ACLs)
170
Содержание S4048T
Страница 1: ...Dell Configuration Guide for the S4048T ON System 9 10 0 1 ...
Страница 98: ... saveenv 7 Reload the system uBoot mode reset Management 98 ...
Страница 113: ...Total CFM Pkts 10303 CCM Pkts 0 LBM Pkts 0 LTM Pkts 3 LBR Pkts 0 LTR Pkts 0 802 1ag 113 ...
Страница 411: ...mode transit no disable Force10 Resilient Ring Protocol FRRP 411 ...
Страница 590: ...Figure 67 Inspecting the LAG Configuration Link Aggregation Control Protocol LACP 590 ...
Страница 591: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 591 ...
Страница 594: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command Link Aggregation Control Protocol LACP 594 ...
Страница 595: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 595 ...
Страница 646: ...Figure 87 Configuring Interfaces for MSDP Multicast Source Discovery Protocol MSDP 646 ...
Страница 647: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 647 ...
Страница 648: ...Figure 89 Configuring PIM in Multiple Routing Domains Multicast Source Discovery Protocol MSDP 648 ...
Страница 653: ...Figure 91 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 653 ...
Страница 654: ...Figure 92 MSDP Default Peer Scenario 3 Multicast Source Discovery Protocol MSDP 654 ...
Страница 955: ...Figure 119 Single and Double Tag First byte TPID Match Service Provider Bridging 955 ...
Страница 1179: ...Figure 147 Create Hypervisor Figure 148 Edit Hypervisor Figure 149 Create Transport Connector Virtual Extensible LAN VXLAN 1179 ...