[no] resource-profile
config>system
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure resource-profile parameters on the system.
decommission
config>system>resource-profile
7210 SAS-Dxp
Commands in this context decommission a port. Ports that are decommissioned using this command are not available for provisioning services. The packet buffers are taken away from the decommissioned port and allocated to ports as specified by the entries configured under the decommission command. This command allows the user to allocate more packet buffers to a specific port or group of ports and enables those ports to absorb larger bursts.
On the 7210 SAS-Dxp 12p, the user can decommission up to two ports and allocate the freed buffers to another port, as required. The user can also decommission four ports and allocate buffers from two ports each to each of the other two ports. For example, the user can decommission ports 1/1/1 and 1/1/2 and allocate buffers to 1/1/3, and decommission ports 1/1/4 and 1/1/5 and allocate buffers to 1/1/6.
On the 7210 SAS-Dxp 16p and 7210 SAS-Dxp 24p, the user can decommission up to three ports and allocate freed buffers to another port, as required. The user can also decommission six ports and allocate buffers from three ports each to each of the other two ports. For example, the user can decommission ports 1/1/1, 1/1/2, and 1/1/3 and allocate buffers to 1/1/4, and decommission ports 1/1/5, 1/1/6, and 1/1/7 and allocate buffers to 1/1/8.
entry entry-id port port-range to port-range
no entry entry-id
config>system>resource-profile>decommission
7210 SAS-Dxp
This command allows the user to decommission a port or group of ports and allocate buffers to those ports which need more packet buffers for absorbing larger bursts. It allows user to configure the entries that list the ports to be decommissioned. Ports whose packet buffers are taken away are presented to the left of the to keyword, and ports to which buffers are allocated are presented to the right side.
This command allows users to specify either a port or a group of ports on the left side of the to keyword, and a single port on the right side of the to keyword. This allows the user to decommission up to two ports and allocate buffer to a single port.
Packet buffers taken away from a port or a group of ports specified on the left side are distributed to the configured port on the right side of the to keyword. Packet buffers are added to the MBS pool of the port (the MBS pool is shared by the 8 queues on the port) and the CBS portion of the queues is not modified.
The administrative state or the operational state of the port is not affected by configuring the port in a decommission entry.
Any changes to the command, such as modifying the list of ports in existing entries or execution of no entry command or addition of new entries, takes effect only after a reboot of the node. The user is allowed to make change when the node is up, but the changes does not happen until a reboot of the system.
The software maintains two lists of entries, one which is in effect currently and one which has been modified by the user and takes effect during the next reboot. These lists can be displayed using the show command. The configuration file always stores the list of entries as configured by the user so that upon reboot, the modified entries and new entries (if any) take effect.
The following guidelines are to be adhered while configuring the entry command:
A port cannot be specified more than once in any of the entries. If two entries specify the same port ID, the software cancels out the last entry that has the same port ID.
A port appearing on the left side of the to keyword in any entry cannot appear on the right side of any other entries (including the same entry) and the converse is also true.
If the user has specified a group of ports using a port range, the software expands the range to a list of ports and then makes the required checks (that is, checks listed in the first and second bullets) for each port in the list with the list of currently configured group of ports.
Either a port ID, a list of port IDs, or a port ID range can be specified on the left side of the to keyword. Please see the following description for port ID specification to know more about the restrictions that apply when configuring a port range and list of ports.
On the 7210 SAS-Dxp, only a single port can be specified on the right side of the to keyword.
The list of entries is processed in the ascending order of the entry IDs, that is, an entry with a lower entry ID is processed before entry with a higher entry ID.
A maximum of two ports can be specified on the left side of the to parameter. Buffers of no more than two ports can be reallocated to a single port.
The no form of this command removes the entry from the list of decommissioned ports.
The no form of this command requires a reboot to take effect.
The following examples show the list of ports, range of ports, and a combination of list of ports and range of ports that can be specified.
List of ports can be specified as:
1/1/1, 1/1/2 is allowed
1/1/10, 1/1/2 is allowed
Range of ports can be specified as:
1/1/2-1/1/3 is allowed
1/1/10-1/1/2 is not allowed
1/1/1 – 1/2/2 is not allowed
no default
Specifies the number in the range 1 to 30. A maximum of 30 entries can be created by the user.
Specifies the port or list of ports or a port range or a combination of these. Identifies the port or group of ports that are being decommissioned when it appears on the left side of the to keyword, and identifies the port that receives the packet buffers from the decommissioned ports when it appears on the right side of the to keyword. A group of ports can be specified as a list of ports or as a range of ports.
The list of ports can be specified in any order using a comma to separate the list of ports, while a port range must always be specified in the ascending order of port IDs.
egress-internal-tcam
config>system>resource-profile
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
Commands in this context allocate resources from the egress internal TCAM pool.
The egress-internal-tcam resource pool is shared by multiple features. The resources are allocated in chunks of fixed sizes. The user is provided an option to allocate the available resources based on their scaling requirements for the features. The resource usage for different features is provided in the CLI description. It is not possible for a chunk to be shared by multiple features. Software allocates resources from the chunk to the feature to which it is allocated until it runs out of all resources in the chunk. If available, the user can allocate more chunks to the feature by taking away chunks of resources from other features that do not need to be enabled.
To free up the resources for use by other features, the users need to modify the configuration such that the chunks of resources in use by other features are freed. For example, to free up a chunk of resources allocated to egress ACLs mac-criteria and allocate it to ip-criteria, the user must remove the association of all the SAPs with egress ACLs that use a MAC criteria policy, change the resource profile configuration to allocate the chunk to ip-criteria, and then create and associate the SAPs with ip-criteria. As another example, the user can free up a chunk of resources used by egress ACLs and allocate it toward a SAP egress aggregate meter (on platforms that support this feature). To do this, the user must remove the association of all the SAPs with egress ACLs, change the resource profile configuration to reduce the chunk of resources allocated to egress ACLs (and reduce the value of chunks in use by the egress ACLs match criteria), then allocate the chunk of resources to the SAP egress aggregate meter feature, and then configure the SAPs with the aggregate meter rate.
The egress-internal-tcam resource pool is shared among the following features on different platforms.
7210 SAS-D and 7210 SAS-Dxp
Egress ACLs (MAC, IPv4 and IPv6 criteria) and per-SAP egress aggregate meter.
7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
Egress ACLS (MAC, IPv4 and IPv6 criteria) and primary VLAN.
When reassigning chunks of resources among features, a reboot of the node may be required. See the CLI description of the specific feature for information.
The egress-internal-tcam pool of resources is allocated per node on the 7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C.
The number of chunks and the number of resources per chunk varies among the different platforms. Contact your Nokia technical support representative for more information.
For some features, a minimum number of chunks (greater than 1) must be allocated to enable the feature functionality. If this is not done, the software cannot allocate the required number of resources, and it fails the command associated with the feature.
acl-sap-egress [num-resources]
no acl-sap-egress
config>system>resource-profile>egress-internal-tcam
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
Commands in this context allocate maximum resources for use by egress filter policies using any of the supported match criteria. This command limits the total amount of chunks allocated for use by egress filter policies to the value specified by num-resources. The cumulative sum of chunks allocated to different match criteria supported by filter policies cannot exceed the value configured with num-resources.
On the 7210 SAS-D and 7210 SAS-Dxp, the resources in the egress-internal-tcam resource pool are shared with other features (for example, SAP egress aggregate meter). To assign resources to this feature, resources may be reallocated from other features by disabling the policy association with a SAP.
On the 7210 SAS-D and 7210 SAS-Dxp, some of the egress ACL match criteria require a minimum number of resources greater than 1 to be allocated before the match criteria can be used. Use of the SAP egress aggregate meter and the use of egress ACLs with the following match criteria: mac-ipv4 match, ipv6-128bit match, and mac-ipv6-64bit match, are mutually exclusive. All these match criteria require a minimum of two resources. SAP egress aggregate meter and egress ACLs MAC match criteria can be enabled simultaneously, with each feature sharing the available resources equally among them.
On the 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C, when resources are allocated to egress ACLs from the egress internal TCAM pool, these resources can be used by MAC criteria entries, IPv4 entries, and entries that use only IPv6 64-bit addresses.
When the user allocates resources for use by SAP egress ACL policies using this command, the system allocates resources in chunks of 128 entries for the 7210 SAS-D and 7210 SAS-Dxp, 510 entries for the 7210 SAS-K 2F1C2T, and 7210 SAS-K 2F6C4T, and 180 entries for the 7210 SAS-K 3SFP+ 8C. The resources are used only for filter entries configured under IPv4 criteria or MAC criteria.
For the 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C, if the user needs to use IPv6 criteria, resources must be allocated using the mac-ipv4-ipv6-128-match-enable command under this command context. The resources allocated using this command are used for filter entries configured under IPv6 criteria, IPv4 criteria, or MAC criteria. Each IPv6, IPv4, or MAC filter entry consumes two resources from this pool, reducing the number of filter entries that can be accommodated in a single chunk to 255 entries for the 7210 SAS-K 2F1C2T and 7210 SAS-K 2F6C4T, and 108 entries for the 7210 SAS-K 3SFP+ 8C. The user can choose to allocate all the chunks allocated for SAP egress ACL policies for IPv6 criteria or allocate only a portion of it.
For information about resource allocation for the match criteria used in egress filter policies, see the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Router Configuration Guide.
The no form of this command is blocked by the CLI and cannot be used on the 7210 SAS-K 3SFP+ 8C.
The no form of this command specifies that the software does not allocate any resources for use by egress filter policies on the 7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, and 7210 SAS-K 2F6C4T. If no resources are allocated for use, then the software fails all attempts to associate a service entity (for example, SAP, IP interface) with a filter policy using any of the match criteria.
Specifies the amount of resources that can be allocated for use by ACL policies. The max keyword allocates 2 slices in the current release. The following table lists the ACL SAP egress resource values.
egress-sap-aggregate-meter num-resources
no egress-sap-aggregate-meter
config>system>resource-profile>egress-internal-tcam
7210 SAS-D and 7210 SAS-Dxp
This command allocates resources for use by SAP egress aggregate policer from the egress-internal-tcam resource pool. This command limits the total amount of chunks allocated for use by SAP egress aggregate meter to the value specified by num-resources.
The resources in the egress-internal-tcam resource pool are shared with other features; for example, SAP egress aggregate meter. To assign resources to this feature, resources may be reallocated from other features by disabling the policies association with a SAP, and others.
On the 7210 SAS platforms, some of the Egress ACL match criteria require a minimum amount of resources greater than 1, to be allocated before the match criteria can be used. In other words, use of SAP egress aggregate meter is mutually exclusive to use of egress ACLs with the following match criteria - mac-ipv4 match, ipv6-128bit match, mac-ipv6-64bit match. All these match criteria require a minimum of 2 resources. SAP egress aggregate meter and egress ACLs MAC match criteria can be enabled simultaneously, with each feature sharing the available resources equally among them.
The no form of this command specifies that the software does not allocate any resources for use by SAP egress aggregate policer. If no resources are allocated for use, then the software fails all attempts to enable the configuration of the command for a SAP.
no egress-sap-aggregate-meter
Specifies the maximum amount of resources for use by this filter match criteria.
mac-auth-res num-resources
no mac-auth-res
config>system>resource-profile>egress-internal-tcam
config>system>resource-profile>ingress-internal-tcam
7210 SAS-Dxp
This command reserves a resource chunk for use by the MAC authentication feature.
The no form of this command releases any resource chunks that were previously reserved for use by the MAC authentication feature.
no mac-auth-res
Specifies the number of resource chunks to reserve for use by the MAC authentication feature.
[no] ipv6-128bit-match-enable num-resources
config>system>resource-profile>egress-internal-tcam>acl-sap-egress
7210 SAS-D and 7210 SAS-Dxp
This command allocates maximum resources for use by egress filter policies using IPv6 criteria with 128-bit IPv6 addresses.
The resources cannot be shared with any other egress filter policies that specify other match criteria. See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Router Configuration Guide for more information about resource allocation and fields available for use.
The no form of this command specifies that the software does not allocate any resources for use by egress filter policies using ipv6 criteria with 128-bit IPv6 addresses. If no resources are allocated for use, then the software fails all attempts to associate a service entity (for example, SAP and IP interface) with a filter policy using this match criteria.
no ipv6-128bit-match-enable
Specifies the maximum amount of resources for use by this filter match criteria. A minimum value of 2 (indicating two chunks of resources) must be allocated to use this match-criteria. If not, association of a policy with ipv6-128bit criteria to a SAP will fail. It is mutually exclusive to the use of SAP egress aggregate meter. The following table lists the IPv6 128-bit match resource values.
|
Platforms |
Min value (per node) |
Max value (per node) |
Default values |
|---|---|---|---|
|
7210 SAS-D (per node) |
0 |
2 |
0 |
|
7210 SAS-Dxp (per node) |
0 |
2 |
0 |
[no] eth-cfm-primary-vlan-enable
config>system>resource-profile>egress-internal-tcam
7210 SAS-K 2F1C2T and 7210 SAS-K 3SFP+ 8C
This command enables the context of resources for primary VLAN functionality for UP MEPs. There are 128 entries allocated in the egress ACL pool.
The user must ensure that sufficient resources are free before executing this command. The tools dump system-resources command is used to determine the amount of free resources in the egress ACL pool. The scaling of ACL entries reduces when resources are allocated to this feature using this command.
The no form of this command frees up the resources allocated to this feature.
no eth-cfm-primary-vlan-enable
mac-ipv4-ipv6-128-match-enable num-resources
no mac-ipv4-ipv6-128-match-enable
config>system>resource-profile>egress-internal-tcam>acl-sap-egress
7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
This command enables IPv6 128-bit address match.
When resources are allocated to egress ACLs from the egress internal TCAM pool using the config system resource-profile egress-internal-tcam acl-sap-egress command, these resources can be used by either MAC criteria entries or IPv4 entries. To enable IPv6 128-bit address match, the user must allocate resources using the mac-ipv4-ipv6-128-match-enable command.
The resources allocated can be shared by MAC criteria, IPv4 criteria, IPv6 64-bit address criteria and IPv6 128-bit address criteria. Each match entry (for all criteria) consumes two resources from this pool, reducing the number of filter entries that can be accommodated in a single chunk to 255 entries for the 7210 SAS-K 2F1C2T and 7210 SAS-K 2F6C4T, and 108 entries for the 7210 SAS-K 3SFP+ 8C.
The no form of this command specifies that the software does not allocate any resources for use by egress filter policies using IPv6 criteria with 128-bit IPv6 addresses. If no resources are allocated for use, then the software fails all attempts to associate a service entity (for example, SAP and IP interface) with a filter policy using this match criteria.
no mac-ipv4-ipv6-128-match-enable
Specifies the maximum amount of resources for use by this filter match criteria.
mac-ipv4-match-enable num-resources
no mac-ipv4-match-enable
config>system>resource-profile>egress-internal-tcam>acl-sap-egress
7210 SAS-D and 7210 SAS-Dxp
This command allocates maximum resources for use by egress filter policies using IPv4 criteria or MAC criteria. The resources allocated are allocated on a first-come-first-serve basis among service entities (for example, SAP and IP interface) using IPv4 and MAC criteria egress filter policies.
The resources cannot be shared with any other egress filter policies that specify other match criteria. See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Router Configuration Guide for more information about resource allocation and fields available for use.
The no form of this command specifies that the software does not allocate any resources for use by egress filter policies using MAC or IPv4 criteria. If no resources are allocated for use, then the software fails all attempts to associate a service entity (for example, SAP and IP interface) with a filter policy using this match criteria.
mac-ipv4-match-enable 2 (to maintain backward compatibility with earlier releases)
Specifies the maximum amount of resources for use by this filter match criteria. A minimum value of 2 (indicating two chunks of resources) must be allocated to use this match-criteria. If not, association of a policy with MAC and IPv4 criteria to a SAP fails. It is mutually exclusive to the use of SAP egress aggregate meter. The following table lists the MAC IPv4 match resource values.
|
Platforms |
Min value (per node) |
Max value (per node) |
Default values |
|---|---|---|---|
|
7210 SAS-D (per node) |
0 |
2 |
0 |
|
7210 SAS-Dxp (per node) |
0 |
2 |
0 |
mac-ipv6-64bit-match-enable num-resources
no mac-ipv6-64bit-match-enable
config>system>resource-profile>egress-internal-tcam>acl-sap-egress
7210 SAS-D and 7210 SAS-Dxp
This command allocates maximum resources for use by egress filter policies using MAC criteria or IPv6 criteria using only the upper 64-bits of the IPv6 addresses. The resources allocated are allocated on a first-come-first-serve basis among service entities (for example, SAP and IP interface) using IPv6 64-bit and MAC criteria egress filter policies.
The resources cannot be shared with any other egress filter policies that specify other match criteria. See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Router Configuration Guide for more information about resource allocation and fields available for use.
The no form of this command specifies that the software does not allocate any resources for use by egress filter policies using MAC or IPv6 64-bit criteria. If no resources are allocated for use, then the software fails all attempts to associate a service entity (for example, SAP and IP interface) with a filter policy using this match criteria.
no mac-ipv6-64bit-match-enable
Specifies the maximum amount of resources for use by this filter match criteria. A minimum value of 2 (indicating two chunks of resources) must be allocated to use this match-criteria. If not, association of a policy with mac and ipv6 64bit criteria to a SAP will fail. It is mutually exclusive to the use of SAP egress aggregate meter. The following table lists the MAC IPv6 64-bit match resource values.
|
Platforms |
Min value (per node) |
Max value (per node) |
Default values |
|---|---|---|---|
|
7210 SAS-D (per node) |
0 |
2 |
0 |
|
7210 SAS-Dxp (per node) |
0 |
2 |
0 |
mac-match-enable num-resources
no mac-match-enable
config>system>resource-profile>egress-internal-tcam>acl-sap-egress
7210 SAS-D and 7210 SAS-Dxp
This command allocates maximum resources for use by egress filter policies using MAC criteria. The resources allocated are allocated on a first-come-first-serve basis among service entities (for example, SAP and IP interface) using MAC criteria egress filter policies. This option provides for use of all available resources exclusively by MAC criteria egress filter policies and provide larger number of policies to be used.
The resources cannot be shared with any other egress filter policies that specify other match criteria. See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Router Configuration Guide for more information about resource allocation and fields available for use.
The no form of this command specifies that the software does not allocate any resources for use by egress filter policies using MAC criteria. If no resources are allocated for use, then the software fails all attempts to associate a service entity (for example, SAP and IP interface) with a filter policy using this match criteria.
It is possible to use MAC policies by allocating resources that are shared with other match criteria. This option allows for better scaling.
no mac-match-enable
Specifies the maximum amount of resources for use by this filter match criteria.
ingress-internal-tcam
config>system>resource-profile
Supported on all 7210 SAS platforms as described in this document
Commands in this context allocate ingress internal TCAM resources.
The ingress-internal-tcam resource pool is shared by multiple features. The resources are allocated in chunks of fixed sizes. The user is provided an option to allocate the available resources based on their scaling requirements for the features. The resource usage for different features is provided in the CLI description. It is not possible for a chunk to be shared by multiple features. Software allocates resources from the chunk to the feature to which it is allocated until it runs out of all resources in the chunk. If available, the user can allocate more chunks to the feature by taking away chunks of resources from other features that do not need to be enabled.
To free up the resources for use by other features, users must modify the configuration such that the chunks of resources in use by other features are freed. For example, to free up a chunk of resources allocated to ingress ACLs mac-criteria and allocate it to ip-criteria, the user must remove the association of all the SAPs with ingress ACLs that use a MAC criteria policy, then change the resource profile configuration to allocate the chunk to ip-criteria, and then create and associate the SAPs with ip-criteria. As another example, the user can free up a chunk of resources used by ingress ACLs and allocate it toward a SAP ingress QoS classification. To do this, the user must remove the association of all the SAPs with ingress ACLs, change the resource profile configuration to reduce the chunk of resources allocated to ingress ACLs (and reduce the value of chunks in use by the ingress ACLs match criteria), then allocate the chunk of resources to the SAP ingress QoS classification feature, and then configure the SAPs with the SAP ingress QoS policies.
The ingress-internal-tcam resource pool is shared among the following features on different platforms:
7210 SAS-D and 7210 SAS-Dxp
SAP ingress QoS classification (using IPv4, IPv6, and MAC match-criteria to match header fields), ingress ACLs (using IPv4, IPv6, and MAC match-criteria), Ethernet CFM UP MEP, SAP ingress aggregate meter
7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
SAP ingress QoS classification (using IPv4, IPv6, and MAC match-criteria to match header fields), ingress ACLs (using IPv4, IPv6 and MAC match-criteria)
When reassigning chunks of resources among features, a reboot of the node may be required. See the CLI description of the specific feature for information.
The ingress-internal-tcam pool of resources is allocated per node on the 7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C.
The number of chunks and the number of resources per chunk varies among the different platforms. Contact your Nokia technical support representative for more information.
For some features, a minimum number of chunks (greater than 1) must be allocated to enable the feature functionality. If this is not done, the software cannot allocate the required number of resources and it will fail the command associated with the feature.
acl-sap-ingress [num-resources]
no acl-sap-ingress
config>system>resource-profile>ingress-internal-tcam
Supported on all 7210 SAS platforms as described in this document
Commands in this context allocate maximum resources for use by ingress filter policies using any of the supported match criteria. This command limits the total amount of chunks allocated for use by ingress filter policies to the value specified by num-resources. In other words, the cumulative sum of chunks allocated to different match criteria supported by ingress filter policies cannot exceed the value configured with num-resources.
On the 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C, when resources are allocated to ingress ACLs from the ingress internal TCAM pool, these resources can be used by MAC criteria entries, IPv4 entries and entries that use only IPv6 64-bit addresses.
When the user allocates resources for use by SAP ingress ACL policies using this command, the system allocates resources in chunks of 256 entries for the 7210 SAS-D and 7210 SAS-Dxp, 510 entries for the 7210 SAS-K 2F1C2T and 7210 SAS-K 2F6C4T, and 192 entries for the 7210 SAS-K 3SFP+ 8C. The resources are used only for filter entries configured under IPv4 criteria or MAC criteria.
For the 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C, if the user needs to use IPv6 criteria, resources must be allocated using the mac-ipv4-ipv6-128-match-enable command under this command context. The resources allocated using this command are used for filter entries configured under IPv6 criteria, IPv4 criteria, or MAC criteria. Each IPv6, IPv4, or MAC filter entry consumes two resources from this pool, reducing the number of filter entries that can be accommodated in a single chunk to 255 entries for the 7210 SAS-K 2F1C2T and 7210 SAS-K 2F6C4T, and 96 entries for the 7210 SAS-K 3SFP+ 8C. The user can choose to allocate all the chunks allocated for SAP ingress ACL filters for IPv6 criteria or allocate only a portion of it.
See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Router Configuration Guide for more information about resource allocation for the match criteria used in ingress filter policies.
The no form of this command specifies that the software does not allocate any resources for use by ingress filter policies on the 7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, and 7210 SAS-K 2F6C4T. If no resources are allocated for use, the software fails all attempts to associate a service entity (for example, SAP, IP interface) with a filter policy using any of the match criteria.
The no form of this command is blocked in the CLI and cannot be used on the 7210 SAS-K 3SFP+ 8C.
Specifies the amount of resources that can be allocated for use by ACL policies. The following table ACL SAP ingress resource values.
|
Platforms |
Min value (per node) |
Max value (per node) |
Default values |
|---|---|---|---|
|
7210 SAS-D (per node) |
0 |
3 |
2 |
|
7210 SAS-Dxp (per node) |
0 |
3 |
2 |
|
7210 SAS-K 2F1C2T (per node) |
0 |
5 |
1 |
|
7210 SAS-K 2F6C4T (per node) |
0 |
5 |
1 |
[no] ipv4-ipv6-128-match-enable num-resource
config>system>resource-profile>ingress-internal-tcam>acl-sap-ingress
7210 SAS-D, 7210 SAS-Dxp
This command allocates maximum resources for use by ingress filter policies using ipv6 criteria with 128-bit IPv6 addresses.
The resources can be shared with IPv4 ingress filter policies. See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Router Configuration Guide for more information about how to allow filter policies using IPv4 criteria to share resources with filter policies that use IPv6 criteria with 128-bit address and resource allocation details and fields available for use.
The no form of this command specifies that the software does not allocate any resources for use by ingress filter policies using IPv6 criteria with 128-bit IPv6 addresses. If no resources are allocated for use, the software fails all attempts to associate a service entity (for example: SAP, IP interface) with a ingress filter policy using this match criteria.
Specifies the maximum amount of resources for use by this filter match criteria.
If the user specifies max, the software allocates one chunk when the first SAP is associated with an ingress filter policy using this match criteria. It continues to allocate resources to the service entity associated with a ingress filter policy using this criteria, as long as the total amount of resources allocated does not exceed the resources allocated to ingress filter policies (configured with the config system resource-profile ingress-internal-tcam acl-sap-ingress command) and chunks are available for use. The following table lists the IPv4 and IPv6 128-bit match resource values.
|
Platforms |
Min value (per node) |
Max value (per node) |
Default values |
|---|---|---|---|
|
7210 SAS-D (per node) |
0 |
3 |
0 |
|
7210 SAS-Dxp (per node) |
0 |
3 |
0 |
mac-ipv4-ipv6-128-match-enable num-resources
no mac-ipv4-ipv6-128-match-enable
config>system>resource-profile>ingress-internal-tcam>acl-sap-ingress
7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
This command enables IPv6 128-bit address match.
When resources are allocated to ingress ACLs from the ingress internal TCAM pool using the config system resource-profile ingress-internal-tcam acl-sap-ingress command, these resources can be used by MAC criteria entries, IPv4 entries and entries that use only IPv6 64-bit addresses. To enable IPv6 128-bit address match, the user must allocate resources using the mac-ipv4-ipv6-128-match-enable command.
The resources allocated can be shared by MAC criteria, IPv4 criteria, IPv6 64-bit address criteria and IPv6 128-bit address criteria. Each match entry (for all criteria) consumes two resources from this pool, reducing the number of filter entries that can be accommodated in a single chunk to 255 entries for the 7210 SAS-K 2F1C2T and 7210 SAS-K 2F6C4T, and 96 entries for the 7210 SAS-K 3SFP+ 8C.
The no form of this command specifies that the software does not allocate any resources for use by egress filter policies using IPv6 criteria with 128-bit IPv6 addresses. If no resources are allocated for use, the software fails all attempts to associate a service entity (for example, SAP and IP interface) with a filter policy using this match criteria.
no mac-ipv4-ipv6-128-match-enable
Specifies the maximum amount of resources for use by this filter match criteria.
ipv4-mac-match-enable num-resource
no ipv4-mac-match-enable
config>system>resource-profile>ingress-internal-tcam>qos-sap-ingress-resource
7210 SAS-D, 7210 SAS-Dxp
This command allocates maximum resources for use by SAP ingress QoS policies using both MAC (any) and IPv4 criteria (any) criteria in a policy.
The software allocates available resources for SAP ingress policies using the following criteria - either both IPv4 criteria any and MAC criteria any, only MAC criteria any, only ipv4 criteria, dot1p-only criteria, ipv4 dscp-only criteria and ipv6 dscp-only criteria. It is not used for SAP ingress policies that use ipv6 criteria any.
See the 7210 SAS-D, Dxp Quality of Service Guide for more information about resource allocation and fields available for use.
The no form of this command specifies that the software does not allocate any resources for use by SAP ingress QoS policies using both MAC and IPv4 criteria. If no resources are allocated for use, the software fails all attempts to associate a service entity (for example, SAP and IP interface) with a ingress filter policy or SAP ingress QoS policy using this match criteria.
Specifies the maximum amount of resources for use by this filter match criteria.
If the user specifies max, the software allocates one chunk when the first SAP is associated with an ingress filter policy using this match criteria. It continues to allocate resources to the service entity associated with a ingress filter policy using this criteria, as long as the total amount of resources allocated does not exceed the resources allocated to ingress filter policies (configured with the config system resource-profile ingress-internal-tcam qos-sap-ingress-resource command) and chunks are available for use. The following table lists the parameter values.
|
Platforms |
Min value (per node) |
Max value (per node) |
Default values |
|---|---|---|---|
|
7210 SAS-D (per node) |
0 |
3 |
0 |
|
7210 SAS-Dxp (per node) |
0 |
3 |
0 |
[no] mac-ipv4-ipv6-128-match-enable num-resources
config>system>resource-profile>ingress-internal-tcam>qos-sap-ingress-resource
7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
This command allocates maximum resources for use by SAP ingress QoS classification policies using IPv6 criteria with 128-bit IPv6 (source and destination IPv6) addresses.
When resources are allocated to SAP ingress classification from the ingress internal TCAM pool using the config system resource-profile ingress-internal-tcam qos-sap-ingress-resource command, these resources can be used by either MAC criteria entries or IPv4 criteria entries. To enable IPv6 128-bit address match, the user must allocate resources using this command.
The resources allocated can be shared by MAC criteria, IPv4 criteria, IPv6 64-bit address criteria and IPv6 128-bit address criteria. Each match entry (for all criteria) consumes two resources from this pool, reducing the number of classification entries that can be accommodated in a single chunk to 255 entries for the 7210 SAS-K 2F1C2T and 7210 SAS-K 2F6C4T, and 96 entries for the 7210 SAS-K 3SFP+ 8C.
The no form of this command specifies that the software does not allocate any resources for use by SAP ingress QoS classification rules using IPv6 criteria. If no resources are allocated for use, the software fails all attempts to associate a service entity (for example, SAP and IP interface) with a policy using the IPv6 match criteria.
no mac-ipv4-ipv6-128-match-enable
Specifies the maximum amount of resources for use by this match criteria.
[no] ipv4-match-enable num-resource
config>system>resource-profile>ingress-internal-tcam>acl-sap-ingress
7210 SAS-D, 7210 SAS-Dxp
This command allocates maximum resources for use by ingress filter policies using ipv4 criteria.
The resource cannot be shared with ingress filter policies using mac criteria or ipv6 criteria. See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Router Configuration Guide for more information about resource allocation details and fields available for use.
The no form of this command specifies that the software does not allocate any resources for use by ingress filter policies using ipv4 criteria. If no resources are allocated for use, then software fails all attempts to associate a service entity (for example, SAP and IP interface) with a ingress filter policy using this match criteria.
Specifies the maximum amount of resources for use by this filter match criteria.
If the user specifies max, the software allocates one chunk when the first SAP is associated with an ingress filter policy using this match criteria. It continues to allocate resources to the service entity associated with a ingress filter policy using this criteria, as long as the total amount of resources allocated does not exceed the resources allocated to ingress filter policies (configured with the config system resource-profile ingress-internal-tcam qos-sap-ingress-resource command) and chunks are available for use. The following table lists the parameter values.
|
Platforms |
Min value (per node) |
Max value (per node) |
Default values |
|---|---|---|---|
|
7210 SAS-D (per node) |
0 |
3 |
0 |
|
7210 SAS-Dxp (per node) |
0 |
3 |
0 |
ipv4-match-enable num-resource
no ipv4-match-enable
config>system>resource-profile>ingress-internal-tcam>qos-sap-ingress-resource
7210 SAS-D, 7210 SAS-Dxp
This command allocates maximum resources for use by SAP ingress QoS policies using IPv4 criteria (any).
The resource cannot be shared with SAP ingress QoS filter policies using MAC criteria or ipv6 criteria. See the 7210 SAS-K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Quality of Service Guide for more information about resource allocation details and fields available for use.
The no form of this command specifies that the software does not allocate any resources for use by SAP ingress QoS policies using ipv4 criteria. If no resources are allocated for use, then software fails all attempts to associate a service entity (for example, SAP and IP interface) with a SAP ingress QoS policy using this match criteria.
Specifies the maximum amount of resources for use by this filter match criteria.
If the user specifies max, the software allocates one chunk when the first SAP is associated with an ingress filter policy using this match criteria. It continues to allocate resources to the service entity associated with a ingress filter policy using this criteria, as long as the total amount of resources allocated does not exceed the resources allocated to ingress filter policies (configured with the config system resource-profile ingress-internal-tcam qos-sap-ingress-resource command) and chunks are available for use. The following table lists the parameter values.
|
Platforms |
Min value (per node) |
Max value (per node) |
Default values |
|---|---|---|---|
|
7210 SAS-D (per node) |
0 |
3 |
0 |
|
7210 SAS-Dxp (per node) |
0 |
3 |
0 |
[no] ipv6-64-only-match-enable num-resource
config>system>resource-profile>ingress-internal-tcam>acl-sap-ingress
7210 SAS-D, 7210 SAS-Dxp
This command allocates maximum resources for use by ingress filter policies using ipv6 criteria with 64-bit IPv6 addresses. See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Router Configuration Guide for more information about resource allocation details and fields available for use.
The resources cannot be shared with IPv4 filter policies or IPv6 filter policies specifying 128-bit addresses.
The no form of this command specifies that the software does not allocate any resources for use by filter policies using ipv6 criteria with 64-bit IPv6 addresses. If no resources are allocated for use, then software fails all attempts to associate a service entity (for example, SAP and IP interface) with a ingress filter policy using this match criteria.
Specifies the maximum amount of resources for use by this filter match criteria.
If the user specifies max, the software allocates one chunk when the first SAP is associated with an ingress filter policy using this match criteria. It continues to allocate resources to the service entity associated with a ingress filter policy using this criteria, as long as the total amount of resources allocated does not exceed the resources allocated to ingress filter policies (configured with the config system resource-profile ingress-internal-tcam qos-sap-ingress-resource command) and chunks are available for use. The following table lists the parameter values.
|
Platforms |
Min value (per node) |
Max value (per node) |
Default values |
|---|---|---|---|
|
7210 SAS-D (per node) |
0 |
3 |
0 |
|
7210 SAS-Dxp (per node) |
0 |
3 |
0 |
[no] mac-match-enable num-resource
config>system>resource-profile>ingress-internal-tcam>acl-sap-ingress
7210 SAS-D, 7210 SAS-Dxp
This command allocates maximum resources for use by ingress filter policies using MAC criteria.
See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Router Configuration Guide for more information about ingress filter policy and fields available for use with ingress filter policy.
The no form of this command specifies that the software does not allocate any resources for use by ingress filter policies using MAC criteria. If no resources are allocated for use, then software fails all attempts to associate a service entity (for example, SAP and IP interface) with a ingress filter policy using this match criteria.
Specifies the maximum amount of resources for use by this filter match criteria.
If the user specifies max, the software allocates one chunk when the first SAP is associated with an ingress filter policy using this match criteria. It continues to allocate resources to the service entity associated with a ingress filter policy using this criteria, as long as the total amount of resources allocated does not exceed the resources allocated to ingress filter policies (configured with the config system resource-profile ingress-internal-tcam qos-sap-ingress-resource command) and chunks are available for use. The following table lists the parameter values.
|
Platforms |
Min value (per node) |
Max value (per node) |
Default values |
|---|---|---|---|
|
7210 SAS-D (per node) |
0 |
3 |
0 |
|
7210 SAS-Dxp (per node) |
0 |
3 |
0 |
On the 7210 SAS-D and 7210 SAS-Dxp, mac-criteria SAP ingress QoS policies get to use an additional 128 classification entries with 64 meters. These entries are allocated to mac-criteria SAP ingress QoS resource pool by default and cannot be reassigned to any another feature or any other match criteria.
[no] mac-match-enable num-resource
config>system>resource-profile>ingress-internal-tcam>qos-sap-ingress-resource
7210 SAS-D, 7210 SAS-Dxp
This command allocates maximum resources for use by SAP ingress QoS policies using MAC criteria (any).
See the 7210 SAS-K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Quality of Service Guide for more information about the resource allocation for SAP ingress QoS policy.
The no form of this command specifies that the software does not allocate any resources for use by SAP ingress QoS policies using MAC criteria. If no resources are allocated for use, the software fails all attempts to associate a service entity (for example, SAP and IP interface) with a SAP ingress QoS policy using this match criteria.
Specifies the maximum amount of resources for use by this filter match criteria.
If the user specifies max, the software allocates one chunk when the first SAP is associated with an ingress filter policy using this match criteria. It continues to allocate resources to the service entity associated with a ingress filter policy using this criteria, as long as the total amount of resources allocated does not exceed the resources allocated to ingress filter policies (configured with the config system resource-profile ingress-internal-tcam qos-sap-ingress-resource command) and chunks are available for use. The following table lists the parameter values.
|
Platforms |
Min value (per node) |
Max value (per node) |
Default values |
|---|---|---|---|
|
7210 SAS-D (per node) |
0 |
3 |
0 |
|
7210 SAS-Dxp (per node) |
0 |
3 |
0 |
On the 7210 SAS-D and 7210 SAS-Dxp, mac-criteria SAP ingress QoS policies get to use an additional 128 classification entries with 64 meters. These entries are allocated to mac-criteria SAP ingress QoS resource pool by default and cannot be reassigned to any another feature or any other match criteria.
[no] eth-cfm num-resource
config>system>resource-profile>ingress-internal-tcam
7210 SAS-D and 7210 SAS-Dxp
Commands in this context allocate resources for CFM UP MEPs.
The no form of this command specifies that the software does not allocate any resources for use by CFM UP MEPs.
CFM Down MEPs do not require explicit resource allocation by the user.
Specifies the maximum amount of resources for use by eth-cfm.
The following table lists the parameter values.
|
Platforms |
Min value (per node) |
Max value (per node) |
Default |
|---|---|---|---|
|
7210 SAS-D (per node) |
0 |
1 |
0 |
|
7210 SAS-Dxp (per node) |
0 |
1 |
0 |
[no] up-mep num-resource
config>system>resource-profile>ingress-internal-tcam>eth-cfm
7210 SAS-D and 7210 SAS-Dxp
This command allocates resources for CFM UP MEPs.
Resources for UP MEPs created on SAP and SDP Bindings are allocated from this pool.
The no form of this command specifies that the software does not allocate any resources for use by CFM UP MEPs. If no resources are allocated for use, then software fails all attempts to configure an UP MEP.
CFM Down MEPs do not require explicit resource allocation by the user.
Resource allocation for UP MEPs is only supported on the 7210 SAS-D and 7210 SAS-Dxp.
0
Specifies the maximum amount of resources for use by up-mep.
ipv6-ipv4-match-enable num-resource
no ipv6-ipv4-match-enable
config>system>resource-profile>ingress-internal-tcam>qos-sap-ingress-resource
7210 SAS-D, 7210 SAS-Dxp
This command allocates resources from the SAP ingress QoS resource pool for ipv6-criteria. Users need to use this command before using IPv6 criteria SAP ingress QoS policies.
These resources can be shared with SAP ingress policies that use IPv4 criteria. See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Router Configuration Guide for more information about the resource allocation for SAP ingress QoS policy.
The no form of this command specifies that the software does not allocate any resources for use by ingress SAP QoS policies using IPv6 criteria. If no resources are allocated for use, then software fails all attempts to associate a service entity (for example, SAP and IP interface) with a ingress filter policy using this match criteria.
Specifies the maximum amount of resources for use by this SAP ingress Qos policy match criteria.
If the user specifies max, the software allocates one chunk when the first SAP is associated with an ingress filter policy using this match criteria. It continues to allocate resources to SAPs associated with a ingress filter policy using this criteria, as long as the total amount of resources allocated does not exceed the resources allocated to ingress filter policies (configured with the config system resource-profile ingress-internal-tcam qos-sap-ngress-resource command) and chunks are available for use. The following table lists the parameter values.
|
Platforms |
Min value (per node) |
Max value (per node) |
Default values |
|---|---|---|---|
|
7210 SAS-D (per node) |
0 |
6 |
max |
|
7210 SAS-Dxp (per node) |
0 |
6 |
max |
qos-sap-ingress-resource num-resource
no qos-sap-ingress-resource
config>system>resource-profile>ingress-internal-tcam
Supported on all 7210 SAS platforms as described in this document
Commands in this context allocate maximum resources for use by SAP ingress QoS policies using any of the supported match criteria. This command limits the total amount of chunks allocated for use by SAP ingress QoS policies to the value specified by num-resources. The cumulative sum of chunks allocated to different match criteria supported by SAP ingress QoS policies cannot exceed the value configured with num-resources.
If no resources are allocated for use, then the software fails all attempts to associate a service entity (for example, SAP and IP interface) with a SAP ingress QoS policy using any of the match criteria .
When the user allocates resources for use by SAP ingress QoS policies using this command, the system allocates resources in chunks of 256 entries for the 7210 SAS-D and 7210 SAS-Dxp, 510 entries for the 7210 SAS-K 2F1C2T and 7210 SAS-K 2F6C4T, and 192 entries for the 7210 SAS-K 3SFP+ 8C. The resources are used only for classification entries configured under IPv4 criteria or MAC criteria.
For the 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C, if the user needs to use IPv6 criteria, resources must be allocated using the CLI command mac-ipv4-ipv6-128-match-enable under this command context. The resources allocated using this command are used for classification entries configured under IPv6 criteria, IPv4 criteria, or MAC criteria. Each IPv6, IPv4, or MAC classification entry consumes two resources from this pool, reducing the number of classification entries that can be accommodated in a single chunk to 255 entries for the 7210 SAS-K 2F1C2T and 7210 SAS-K 2F6C4T, and 96 entries for the 7210 SAS-K 3SFP+ 8C. The user can choose to allocate all the chunks allocated for SAP ingress QoS classification for IPv6 criteria or allocate only a portion of it.
See the 7210 SAS-D, Dxp Quality of Service Guide and 7210 SAS-K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Quality of Service Guide for more information about resource allocation for the match criteria used in ingress filter policies.
The no form of this command specifies that the software does not allocate any resources for use by SAP ingress QoS policies on the 7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, and 7210 SAS-K 2F6C4T.
The no form of this command is blocked in the CLI and cannot be used on the 7210 SAS-K 3SFP+ 8C.
Specifies the amount of resources that can be allocated for use by SAP ingress QoS policies.
The following table lists the parameter values.
[no] sap-aggregate-meter num-resource
config>system>resource-profile>ingress-internal-tcam
7210 SAS-D and 7210 SAS-Dxp
This command allocates maximum resources for use by meters/policers used to implement SAP ingress aggregate meter functionality from the global pool of ingress CAM resources. The user must ensure that resources are allocated to aggregate meters using this command before using the config service sap ingress aggregate-meter-rate command.
For the command to take effect, the node must be rebooted after making the change.
This command allocates meter resources from the available global ingress CAM resource pool. By default, when resources are allocated to SAP ingress QoS policy, along with the CAM classification entries, meter resources are also allocated. If the user needs to use SAP aggregate meter functionality they cannot allocate all the available resources in the global resource pool to SAP ingress QoS policies and ETH-CFM UP MEP. They need to allocate some resources for use by SAP aggregate meter (or SAP ingress ACLs or G8032-fast-flood feature).
By default, when resources are allocated for ingress ACLs, only classification entries are used and meters resources are not used. SAP aggregate meter resources can use meters from this pool of meter resources. In other words, SAP aggregate meters are stolen from the unused meters in the resources allocated to ingress ACLs.
If the user allocates resources for ingress ACLs and then configures resources for SAP aggregate meter using this command, the software does the following.
It does not allocate any additional chunks or resources from the available global ingress CAM resource pool to SAP aggregate meter, if it can allocate the required number of meters from the chunks/resources allocated to ingress ACLs. For example, if user has allocated 2 chunks of 510 entries each for ingress ACLs and then configures sap-aggregate-meter to use 2 chunks to use about 510 aggregate meters, the software does not allocate any additional entries from the available global resource pool.
If the number of ingress ACL resources allocated by user is less than the number of resources assigned by the user to sap-aggregate-meter (or if no resources are allocated to G8032), the software allocates the difference from the available global ingress CAM resource pool. For example, if user has allocated 1 chunk of 510 entries for ingress ACLs and then configures sap-aggregate-meter to use 2 chunks to use about 510 aggregate meters, the software allocates 1 additional chunk (2 chunks required for SAP aggregate - 1 chunk alloted to ingress ACLs) for use with SAP aggregate meter. The classification entries associated with additional chunk alloted for SAP aggregate-meter can be used by the ingress ACLs policies. It cannot be used by SAP ingress QoS policies and eth-cfm UP MEP.
Similar checks as above are performed when user allocates resources for SAP aggregate meters using this command and then configures resources for ingress ACLs (or for G8032-fast-flood feature). That is, the software does the following.
It does not allocate any additional entries from the available global ingress CAM resource pool to ingress ACLs, if it can allocate the required number of classification entries from the chunks allocated to SAP aggregate meter feature. For example, if the user has allocated 2 chunks of 510 entries each for SAP aggregate meters, and then configures ingress ACLs to use 2 chunks to use about 510 classification entries, the software does not allocate any additional entries from the available global resource pool.
If the number of SAP aggregate meter resources allocated by user is less than the number of resources requested by the user for ingress ACLs, the software allocates the difference from the available global ingress CAM resource pool. For example, if the user has allocated 1 chunk of 510 entries for SAP aggregate meters, and then configures ingress ACLs to use 2 chunks, the software allocates 1 additional chunk (2 chunks required for ingress ACLs - 1 chunk alloted to SAP aggregate meter) for use with ingress ACLs. The meter resources associated with additional chunk alloted for ingress ACLs can be assigned to the SAP aggregate feature, if required.
See the 7210 SAS-D, Dxp Quality of Service Guide, 7210 SAS-K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Quality of Service Guide, and 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Router Configuration Guide for more information about the use of SAP aggregate feature, ingress CAM resource allocation and use of ACLs policies.
The no form of this command specifies that the software does not allocate any resources for use by SAP ingress aggregate meter. If no resources are allocated for use, then the software fails all attempts to associate an aggregate-meter with SAP ingress.
Specifies the maximum amount of resources for use by this filter match criteria.
The following table lists the parameter values.
|
Platforms |
Min value (per node) |
Max value (per node) |
Default values |
|---|---|---|---|
|
7210 SAS-D (per node) |
0 |
1 |
0 |
|
7210 SAS-Dxp (per node) |
0 |
1 |
0 |