Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

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

PDF

seq

Assign a sequence number to a deny or permit filter in an extended IP access list while creating the filter.

Syntax seq sequence-number {deny | permit} { ip-protocol-number | icmp | ip | tcp | udp} { source mask | any | host ip-address} { destination mask | any | host ip-address} [ operator port [ port]] [count [byte]] [dscp value] [order] [fragments] [log [interval minutes] [threshold-in-msgs [ count]] [monitor]
Parameters
sequence-number Enter a number from 0 to 4294967290. The range is from 1 to 65534.
deny Enter the keyword deny to configure a filter to drop packets meeting this condition.
permit Enter the keyword permit to configure a filter to forward packets meeting this criteria.
ip-protocol-number Enter a number from 0 to 255 to filter based on the protocol identified in the IP protocol header.
icmp Enter the keyword icmp to configure an ICMP access list filter.
ip Enter the keyword ip to configure a generic IP access list. The keyword ip specifies that the access list permits all IP protocols.
tcp Enter the keyword tcp to configure a TCP access list filter.
udp Enter the keyword udp to configure a UDP access list filter.
source Enter an IP address in dotted decimal format of the network from which the packet was received.
mask (OPTIONAL) Enter a network mask in /prefix format (/x) or A.B.C.D. The mask, when specified in A.B.C.D format, may be either contiguous or non-contiguous.
any Enter the keyword any to specify that all routes are subject to the filter.
host ip-address Enter the keyword host and then enter the IP address to specify a host IP address or hostname.
operator (OPTIONAL) Enter one of the following logical operands:
  • eq = equal to
  • neq = not equal to
  • gt = greater than
  • lt = less than
  • range = inclusive range of ports (you must specify two ports for the port parameter.)
port port (OPTIONAL) Enter the application layer port number. Enter two port numbers if you are using the range logical operand. The range is from 0 to 65535.
The following list includes some common TCP port numbers:
  • 23 = Telnet
  • 20 and 21 = FTP
  • 25 = SMTP
  • 169 = SNMP
destination Enter the IP address of the network or host to which the packets are sent.
count (OPTIONAL) Enter the keyword count to count packets the filter processes.
byte (OPTIONAL) Enter the keyword byte to count bytes the filter processes.
dscp (OPTIONAL) Enter the keyword dcsp to match to the IP DCSCP values.
order (OPTIONAL) Enter the keyword order to specify the QoS order for the ACL entry. The range is from 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).
fragments Enter the keyword fragments to use ACLs to control packet fragments.
log (OPTIONAL) Enter the keyword log to enable the triggering of ACL log messages.
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.
interval minutes (OPTIONAL) Enter the keyword interval followed by the time period in minutes at which the ACL logs must be generated. The interval range is from 1 to 10 minutes.
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.
Defaults By default 10 ACL logs are generated if you do not specify the threshold explicitly. The default frequency at which the ACL logs are generated is five minutes. By default, the flow-based monitoring is not enabled.
Command Modes CONFIGURATION-IP ACCESS-LIST-EXTENDED
Supported Modes Full–Switch
Command History
Version Description
9.9(0.0) Introduced on the FN IOM.
9.4(0.0) Added support for the flow-based monitoring on the MXL 10/40GbE Switch IO Module.
9.3(0.0) Added support for logging of ACLs on the MXL 10/40GbE Switch IO Module.
8.3.16.1 Introduced on the MXL 10/40GbE Switch IO Module.
Usage Information
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.

If you configure the sequence-number , the sequence-number is used as a tie breaker for rules with the same order.

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

Related Commands

deny — Configures a filter to drop packets.

permit — Configures a filter to forward packets.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\