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 is supported on the Z9000 platform.
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]
Access Control Lists (ACLs)
125
Содержание Z9000
Страница 1: ...Dell Configuration Guide for the Z9000 System 9 7 0 0 ...
Страница 80: ...grub reboot 80 Management ...
Страница 128: ... 0 Te 1 1 Te 1 2 rx Flow N A N A 128 Access Control Lists ACLs ...
Страница 436: ...Figure 50 Inspecting Configuration of LAG 10 on ALPHA 436 Link Aggregation Control Protocol LACP ...
Страница 439: ...Figure 52 Inspecting a LAG Port on BRAVO Using the show interface Command Link Aggregation Control Protocol LACP 439 ...
Страница 440: ...Figure 53 Inspecting LAG 10 Using the show interfaces port channel Command 440 Link Aggregation Control Protocol LACP ...
Страница 491: ...Figure 70 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 491 ...
Страница 492: ...Figure 71 Configuring PIM in Multiple Routing Domains 492 Multicast Source Discovery Protocol MSDP ...
Страница 496: ...Figure 73 MSDP Default Peer Scenario 1 496 Multicast Source Discovery Protocol MSDP ...
Страница 497: ...Figure 74 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 497 ...
Страница 498: ...Figure 75 MSDP Default Peer Scenario 3 498 Multicast Source Discovery Protocol MSDP ...
Страница 760: ...Figure 100 Single and Double Tag TPID Match 760 Service Provider Bridging ...
Страница 761: ...Figure 101 Single and Double Tag First byte TPID Match Service Provider Bridging 761 ...