Connectivity Guide

View monitor sessions
OS10(conf-if-eth1/1/1)# show monitor session all
S.Id Source Destination Dir SrcIP DstIP DSCP TTL State Reason
----------------------------------------------------------------------------
1 ethernet1/1/1 ethernet1/1/4 both N/A N/A N/A N/A true Is UP
ACL table proles
Ternary content-addressable memory (TCAM) space used for ACL rules is a limited ASIC hardware resource. The ACL table proles feature
allows you to manage the TCAM space depending on the feature that you deploy. You can increase the memory space allocated for
features that require more ACL rules and decrease the memory space allocated for features that use a lesser number of ACL rules. Using
this feature, your switch can support up to 2048 IPv4 or IPv6 user ACL entries.
NOTE: OS10 supports the ACL table proles feature starting from release 10.4.2.1. This feature is supported only on the S5148F-
ON platform.
The ACL table space is divided into six slices, of 512 entries each, corresponding to the six application groups. Out of the six slices, ve are
allocated for ingress application groups that are congurable, and one slice is allocated for egress application group that is xed and not
congurable. The application groups and features mapped to them are xed and are not congurable.
The application groups are predened and are mapped to a set of features. The following table lists the dierent application groups, the
stage (ingress or egress), the features mapped to the application groups, the default number of pools, the minimum number of pools that
you must maintain for each of the application groups, and the maximum number of pools supported by the dierent application groups.
The following terms are used in this section:
• Pool—The hardware space or slice allocated for an application group is called a pool. There are a total of 6 pools; 5 for ingress
application groups and 1 for egress application group.
– Hardware pool—Refers to the amount of hardware space allocated for an application group.
– Service pool—Refers to the amount of ACL table space used by each of the features within a hardware pool. The system creates
the service pool when you congure a feature for the rst time. For example, when you add L2 QOS ACLs, the system creates a
service pool for L2 QOS ACLs within ingress application group 2 (app-group-2).
• Entry—An entry refers to a single row in a pool. The amount of space required to store a single ACL rule in a pool depends on the key
width of the TCAM slice. For example, on an S5148F-ON platform, a single ACL rule takes up more than one row in the pool.
• Application group—The features that share a single hardware pool are grouped into an application group. By default, each application
group is allocated one pool.
Table 42. Application group and feature mapping
Application Group Stage Feature(s) Default number of
pools
Minimum number of
pools required
Maximum number of
pools supported
app-group-1 ingress SYSTEM-FLOW, VLT,
L2-USER-ACL
1 1 5
app-group-2 ingress L2-QOS-ACL 1 0 4
app-group-3 ingress IPV4-USER-ACL,
IPV6-USER-ACL
1 0 4
app-group-4 ingress ISCSI-SNOOPING-
ACL, IPV4-PBR-ACL,
IPV6-PBR-ACL
1 0 4
app-group-5 ingress IPV4-QOS-ACL,
IPV6-QOS-ACL,
ISCSI-COS-ACL
1 0 4
app-group-1 egress L2-EGR-USER-ACL,
IPV4-EGR-USER-
1 1 1
Access Control Lists 705