Skip to main content
Sign Out

Welcome to Dell

My Account
  • 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.
Sign In Create an Account Premier Sign In Partner Program Sign In
Contact Us

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

PDF

permit icmp

Configure a filter to allow all or specific ICMP messages.

Syntax permit icmp { source mask | any | host ip-address} { destination mask | any | host ip-address} [dscp] [ message-type] [count [byte]] [order] [fragments][threshold-in-msgs [ count]]
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 icmp { source mask | any | host ip-address} { destination mask | any | host ip-address} command.
Parameters
source Enter the IP address of the network or host from which the packets were sent.
mask 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 noncontiguous.
any Enter the keyword any to match and drop specific Ethernet traffic on the interface.
host ip-address Enter the keyword host and then enter the IP address to specify a host IP address.
destination Enter the IP address of the network or host to which the packets are sent.
dscp Enter the keyword dscp to deny a packet based on the DSCP value. The range is 0 to 63.
message-type (OPTIONAL) Enter an ICMP message type, either with the type (and code, if necessary) numbers or with the name of the message type. The range is 0 to 255 for ICMP type and 0 to 255 for ICMP code.
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).
fragments Enter the keyword fragments to use ACLs to control packet fragments.
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.
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-IP ACCESS-LIST-STANDARD
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 the support for logging of ACLs on the MXL 10/40GbE Switch IO Module platform.
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. For more information, refer to the Quality of Service chapter of the Dell Networking OS Configuration Guide .

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

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: <>()\