Use this command to view summary information about all IP ACL (Access Control List)s configured on the switch. To view more detailed information about a specific access list, specify the ACL number or name that is used to identify the IP ACL. It displays committed rate, committed burst size, and ACL rule hit count of packets matching the configured ACL rule within an ACL. This counter value rolls-over on reaching the maximum value. There is a dedicated counter for each ACL rule. ACL counters do not interact with PBR counters.
For ACL with multiple rules, once a match occurs at any one specific rule, counters associated with this rule only get incremented for example, consider an ACL with three rules, after matching rule two, counters for rule three would not be incremented).
For ACL counters, if an ACL rule is configured without RATE-LIMIT, the counter value is count of forwarded/discarded packets (for example: If burst of 100 packets sent from IXIA, the Counter value is 100).
If an ACL rule is configured with RATE LIMIT, the counter value will be the MATCHED packet count. If the sent traffic rate exceeds the configured limit, counters will still display matched packet count (despite getting dropped beyond the configured limit since match criteria is met) that would equal the sent rate. For example, if rate limit is set to 10 kbps and ‘matching‘ traffic is sent at 100 kbps, counters would reflect 100 kbps value. If the sent traffic rate is less than the configured limit, counters would display only matched packet count. Either way, only matched packet count is reflected in the counters, irrespective of whether they get dropped or forwarded. ACL counters do not interact with diffserv policies.
| Format | show ip access-lists [accesslistnumber | name] |
| Mode | Privileged EXEC |
| ACL ID/Name | Identifies the configured ACL number or name. |
| Rules | Identifies the number of rules configured for the ACL. |
| Direction | Shows whether the ACL is applied to traffic coming into the interface (ingress) or leaving the interface (egress). |
| Interface(s) | Identifies the interface(s) to which the ACL is applied (ACL interface bindings). |
| VLAN(s) | Identifies the VLANs to which the ACL is applied (ACL VLAN bindings). |
If you specify an IP ACL number or name, the following information displays:
Note
Only the access list fields that you configure are displayed. Thus, the command output varies based on the match criteria configured within the rules of an ACL.| Rule Number | The number identifier for each rule that is defined for the IP ACL. |
| Action | The action associated with each rule. The possible values are Permit or Deny. |
| Match All | Whether this access list applies to every packet. Possible values are True or False. |
| Protocol | The protocol to filter for this rule. |
| ICMP Type | This is shown
only if the protocol is ICMP (Internet Control Message Protocol). The ICMP message type for this rule. |
| Starting Source L4 port | The starting source layer 4 port. |
| Ending Source L4 port | The ending source layer 4 port. |
| Starting Destination L4 port | The starting destination layer 4 port. |
| Ending Destination L4 port | The ending destination layer 4 port. |
| ICMP Code | This is shown
only if the protocol is ICMP. The ICMP message code for this rule. |
| Fragments | If the ACL rule matches on fragmented IP packets. |
| Committed Rate | The committed rate defined by the rate-limit attribute. |
| Committed Burst Size | The committed burst size defined by the rate-limit attribute. |
| Source IP Address | The source IP address for this rule. |
| Source IP Mask | The source IP Mask for this rule. |
| Source L4 Port Keyword | The source port for this rule. |
| Destination IP Address | The destination IP address for this rule. |
| Destination IP Mask | The destination IP Mask for this rule. |
| Destination L4 Port Keyword | The destination port for this rule. |
| IP DSCP | The value specified for IP DSCP. |
| IP Precedence | The value specified IP Precedence. |
| IP TOS | The value specified for IP TOS. |
| Fragments | Specifies whether the IP ACL rule matches on fragmented IP packets is enabled. |
| TTL Field Value | The value specified for the TTL. |
| Log | Displays when you enable logging for the rule. |
| Assign Queue | The queue identifier to which packets matching this rule are assigned. |
| Mirror Interface | The unit/slot/port to which packets matching this rule are copied. |
| Redirect Interface | The unit/slot/port to which packets matching this rule are forwarded. |
| Time Range Name | Displays the name of the time-range if the IP ACL rule has referenced a time range. |
| Rule Status | Status (Active/Inactive) of the IP ACL rule. |
| ACL Hit Count | The ACL rule hit count of packets matching the configured ACL rule within an ACL. |
| ACL Hit Count | The ACL rule hit count of packets matching the configured ACL rule within an ACL. This counter value rolls-over on reaching the maximum value. There is a dedicated counter for each ACL rule. ACL counters do not interact with PBR counters. For ACL with multiple rules, once a match occurs at any one specific rule, counters associated with this rule only get incremented, (for example consider an ACL with three rules, after matching rule 2, counters for rule 3 would not be incremented). For ACL counters, if an ACL rule is configured without RATE-LIMIT, the counter value is count of forwarded/discarded packets. (Example: If burst of 100 packets sent from IXIA, Counter value is 100). And if ACL rule is configured with RATE LIMIT, the counter value will be the MATCHED packet count. If the sent traffic rate exceeds the configured limit, counters would still display matched packet count (despite getting dropped beyond the configured limit since match criteria is met) which would equal the sent rate. For example, if rate limit is set to 10 kbps and ‘matching‘ traffic is sent at 100 kbps, counters would reflect 100 kbps value. If the sent traffic rate is less than the configured limit, counters display only matched packet count. Either way, only matched packet count is reflected in the counters, irrespective of whether they get dropped or forwarded. ACL counters do not interact with diffserv policies. |
The following example shows CLI display output for the command.
Print
this page
Email this topic
Feedback
View PDF
Download EPUB(Extreme 220) (Routing) #show ip access-lists ip1
ACL Name: ip1
Inbound Interface(s): 1/0/30
Sequence Number: 1
Action......................................... permit
Match All...................................... FALSE
Protocol....................................... 1(icmp)
ICMP Type.......................................3(Destination Unreachable)
Starting Source L4 port.........................80
Ending Source L4 port...........................85
Starting Destination L4 port....................180
Ending Destination L4 port......................185
ICMP Code.......................................0
Fragments.......................................FALSE
Committed Rate................................. 32
Committed Burst Size........................... 16
ACL hit count ..................................0