The available global pool of ingress internal CAM hardware resources can be allocated as per user needs for use with different features such as SAP ingress QoS policy, ingress ACLs, and so on. SAP ingress QoS can be allocated classification and meter resources for use from this pool. Further on, resources can be allocated for different SAP ingress QoS policy classification match criteria, based on the operator needs. Users can modify resources allocated to scale the number of entries available per match criteria or scale the number of SAPs. The resources from the global ingress internal CAM pool are allocated in slices with fixed number of entries.
The number of slices allotted for a SAP ingress QoS policy is specified using the configure system resource-profile ingress-internal-tcam qos-sap-ingress-resource command.
User can specify a limit for the amount of resources required for SAP ingress QoS policies and also an option to limit the amount of resources used per match criteria supported for SAP ingress QoS policies. A specific slice can be used for MAC criteria, IP criteria, or IPv6 criteria. Allocation of classification entries also allocates meter/policer resources, used to implement per FC per traffic type policing.
By default, the system allocates resources for SAP ingress QoS policies to maintain backward compatibility with Release 4.0 and allocates resources for MAC criteria and IP criteria (by setting it to 'max'). Setting the value to ‛max’ allows each match criterion to use the available SAP ingress QoS resources on a first-come-first-served model. By default, the software does not allocate resources for use by ingress IPv6 filters. Before associating an IPv6 SAP ingress policy to a SAP, resources must be allocated. Until resources are allocated for use by IPv6 filters, software fails all attempts to associate an IPv6 filter policy with a SAP.
When the user allocates resources for use by SAP ingress QoS policies using the configure system resource-profile qos-sap-ingress-resource command, the system allocates resources in slices of 256 entries. The following table describes the use of these entires by different types of match criteria.
See the 7210 SAS Release Notes for information about services supported on different 7210 SAS platforms. The references to services in the following table appear for completeness and do not imply support is available.
Type of match criteria |
Description |
|---|---|
mac-criteria (any) |
User needs to allocate resources for mac-criteria from the SAP ingress QoS resource pool by using the configure system resource-profile ingress-internal-tcam qos-sap-ingress-resource mac-match-enable command before using SAP ingress policies with mac-criteria. Every entry configured in the SAP ingress QoS policy using the mac-criteria uses one entry from the slices in the hardware. For example, assume a SAP-ingress QoS policy is configured to use mac-criteria with 25 entries and uses configure system resource-profile ingress-internal-tcam qos-sap-ingress-resource mac-match-enable 1, to configure one slice for use by mac-criteria (allowing a total of 256 entries for use by policies using mac-criteria). In this case, the user can have 10 SAPs using mac-criteria SAP ingress policy and consumes 250 entries. |
ipv4-criteria (any) |
The usage is same as the mac-criteria. Resources need to be allocated using the configure system resource-profile ingress-internal-tcam qos-sap-ingress-resource ipv4-match-enable command. Additionally, IPv4 criteria can share the entries allocated for IPv6 criteria. The software automatically allocates entries from an IPv6 criteria slice to IPv4 criteria policies, if there are no entries available in the allocated IPv4 criteria slices and there are no slices available for allocation to IPv4 criteria from the SAP ingress QoS resource pool. The number of hardware entries taken up by an IPv4 criteria entry when using the IPv6 criteria slices is the same as required by an entry using IPv6 criteria (see below for details). |
ipv6-criteria (any) |
User needs to allocate resources from the SAP ingress QoS resource pool for ipv6-criteria by using the configure system resource-profile ingress-internal-tcam qos-sap-ingress-resource ipv6-ipv4-match-enable command before using IPv6 criteria and num-qos-classifiers must specify the ipv6 keyword. Every ipv4 criteria match entry or ipv6 criteria match entry configured in the QoS policy using ipv6-criteria uses two entries from the slices allocated for use by ipv6-criteria (128-bit) in the hardware. Software allocates entries from the ipv6-criteria pool if the SAP ingress QoS policy uses both ipv6-criteria entries and ipv4-criteria (any or IPv4 DSCP) entries or if the SAP ingress QoS policy uses only IPv6 criteria any or if the SAP ingress QoS policy uses ipv4 criteria any and there are no resources available in the IPv4 criteria (as described above). For example, assume a QoS policy is configured to use ipv6-criteria with 25 entries and using configure system resource-profile ingress-internal-tcam qos-sap-ingress-resource ipv4-ipv6-128-match-enable 1, user configures one slice for use by ipv6-criteria. This allows for a total of 128 entries for use by SAPs using SAP ingress QoS policies with ipv6-critiera (as each IPv6 entry uses two entries in hardware). In this example, user can have five SAPs using this policy and consuming 125 entries in total. These resources can be shared with policies that use IPv4 criteria, though it consumes two entries in hardware consumed per IPv4 criteria entry. It allows user to make use of spare IPv6 resources for IPv4 criteria policies, though if user plans to have a larger number of IPv4 criteria policies they are better off allocating more resources for use with IPv4 criteria. Note when a slice is allocated to IPv6 criteria, software automatically adjusts the number of available entries in that slice to 128, instead of 256, because 2 entries are needed to match IPv6 fields. The number of meters available does not reduce though and 128 meters are available for use. |
dot1p-only, IPv4 dscp-only, IPv6 dscp-only, and default SAP ingress QoS policies |
User can use the option 'dot1p-only' or dscp-only', if they plan to use only dot1p bits or only DSCP bits for SAP ingress classification. This typically allows for efficient use of available hardware resources and better scaling. SAP ingress policies that use only dot1p bits or only IPv4/IPv6 DSCP and Default SAP ingress QoS policies can use the resources from slices currently allocated for use by either IP-criteria or MAC-criteria or IPv6 criteria. The following are some special cases noted below for allocation of resources for default, dot1p-only and dscp-only SAP ingress policies:
|
The SAP ingress resource slices described in this section are different from the resources that are configured using the num-qos-classifiers command. The num-qos-classifiers command sets the limit on the resources needed per SAP ingress QoS policy. The resources set the maximum limit on the resources available for use by all the SAP ingress policies that are in use simultaneously on the system. The SR OS manages the resource slices allocated to the SAP ingress QoS policy pool and allocates the entries in the slices when a SAP ingress QoS policy is associated with a SAP. This means that a SAP specifies the amount of QoS resources it needs, using the num-qos-resources command (in the SAP ingress policy) and the system allocates the resources required by a SAP from the slices, depending on whether the SAP ingress policy uses ip-criteria, mac-criteria, or ipv6-criteria.
On the 7210 SAS-D and 7210 SAS-Dxp, mac-criteria SAP ingress QoS policies can use an additional 128 classification entries with 64 meters. These entries are allocated to the mac-criteria SAP ingress QoS resource pool by default and cannot be reassigned to any another feature or any other match criteria.
Use the tools dump system-resources command to display information about the current usage and availability. One or more entries per slice are reserved for system use.