Dell PowerEdge FN I/O Module Command Line Reference Guide 9.10(0.0)

seq arp

Configure an egress filter with a sequence number that filters ARP packets meeting this criteria. This command is supported only on 12-port GE line cards with SFP optics. For specifications, refer to your line card documentation.

Syntax

seq sequence-number {deny | permit} arp { destination-mac-address mac-address-mask | any} vlan vlan-id { ip-address | any | opcode code- number} [count [byte] [order] [log [interval minutes] [threshold-in-msgs[ count]] [monitor]

To remove this filter, use the no seq sequence-number command.

Parameters

sequence-number	Enter a number from 0 to 4294967290.
deny	Enter the keyword `deny` to drop all traffic meeting the filter criteria..
permit	Enter the keyword `permit` to forward all traffic meeting the filter criteria.
destination-mac-address mac-address-mask	Enter a MAC address and mask in the nn:nn:nn:nn:nn format. For the MAC address mask, specify which bits in the MAC address must match. The MAC ACL supports an inverse mask; therefore, a mask of ff:ff:ff:ff:ff:ff allows entries that do not match and a mask of 00:00:00:00:00:00 only allows entries that match exactly.
any	Enter the keyword `any` to match and drop any ARP traffic on the interface.
vlan vlan-id	Enter the keyword `vlan` followed by the VLAN ID to filter traffic associated with a specific VLAN. The range is 1 to 4094 and 1 to 2094 for ExaScale (you can use IDs 1 to 4094). To filter all VLAN traffic specify `VLAN 1`.
ip-address	Enter an IP address in dotted decimal format (A.B.C.D) as the target IP address of the ARP.
opcode code-number	Enter the keyword `opcode` and then enter the number of the ARP opcode. The range is 1 to 16.
count	(OPTIONAL) Enter the keyword `count` to count packets the filter processes.
byte	(OPTIONAL) Enter the keyword `byte` to count bytes the filter processes.
order	(OPTIONAL) Enter the keyword `order` to specify the QoS priority for the ACL entry. The range is 0 to 254 (where 0 is the highest priority and 254 is the lowest; lower-order numbers have a higher priority). If you do not use the keyword `order`, the ACLs have the lowest order by default (255).
log	(OPTIONAL) Enter the keyword `log` to enable the triggering of ACL log messages.
interval minutes	(OPTIONAL) Enter the keyword `interval` followed by the time period in minutes at which ACL logs must be generated. The interval range is from 1 to 10 minutes.
threshold-in msgs count	(OPTIONAL) Enter the `threshold-in-msgs` keyword followed by a value to indicate the maximum number of ACL logs that can be generated, exceeding which the generation of ACL logs is terminated with the `seq`, `permit`, or `deny` commands. The threshold range is from 1 to 100.
monitor	(OPTIONAL) Enter the keyword `monitor` when the rule is describing the traffic that you want to monitor and the ACL in which you are creating the rule is applied to the monitored interface. NOTE: For more information, refer to the Flow-based Monitoring section in the Port Monitoring chapter of the Dell Networking OS Configuration Guide .

Defaults

By default, 10 ACL logs are generated if you do not specify the threshold explicitly. 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

Supported Modes

Full–Switch

Command History

Version	Description
9.9(0.0)	Introduced on the FN IOM.
9.4(0.0)	Added support for flow-based monitoring on the MXL 10/40GbE Switch IO Module platform.
9.3(0.0)	Added support for logging of ACLs on the MXL 10/40GbE Switch IO Module platform.
8.2.1.0	Allows ACL control of fragmented packets for IP (Layer 3) ACLs.
8.1.1.0	Introduced on the E-Series ExaScale.
7.4.1.0	Added the `monitor` option.
6.5.10	Expanded to include the optional QoS `order` priority for the ACL entry.

Usage Information

The monitor option is relevant in the context of flow-based monitoring only. For more information, refer to Port Monitoring.

The order option is relevant in the context of the Policy QoS feature only. The following applies:

The seq sequence-number command is applicable only in an ACL group.
The order option works across ACL groups that have been applied on an interface via the QoS policy framework.
The order option takes precedence over seq sequence-number.
If sequence-number is not configured, the rules with the same order value are ordered according to their configuration order.
If sequence-number is configured, the sequence-number is used as a tie breaker for rules with the same order.

When you use the log option, the CP processor logs details about the packets that match. Depending on how many packets match the log entry and at what rate, the CP may become busy as it has to log these packets’ details.

You cannot include IP, TCP, or UDP (Layer 3) filters in an ACL configured with ARP or Ether-type (Layer 2) filters. Apply Layer 2 ACLs to interfaces in Layer 2 mode.

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).

NOTE: When ACL logging and byte counters are configured simultaneously, byte counters may display an incorrect value. Configure packet counters with logging instead.

Welcome

Welcome to Dell

Dell PowerEdge FN I/O Module Command Line Reference Guide 9.10(0.0)

seq arp

Rate this content