resource-profile policy-id [create]
no resource-profile policy-id
configure>system
7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Sx/S 1/10GE: standalone-VC
Commands in this context configure resource profile parameters on the system.
1
Specifies a resource profile policy.
Keyword to create a resource profile instance.
resource-profile
no resource-profile
configure>system
7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE: standalone, and 7210 SAS-Sx 10/100GE
Commands in this context configure resource profile parameters on the system.
enable-bgp-3107-frr
no enable-bgp3107-frr
config>system>resource-profile
7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE
This command enables the allocation of MPLS FIB and protection group resources required for enabling uniform fast reroute (FRR) for BGP RFC 3107 LU routes resolved using RSVP-TE LSPs. This is a per-node configuration and enabling the command affects all BGP LU routes.
If the command is enabled, the amount of resources required is twice the amount required without uniform FRR, and the number of BGP LU routes that can be accommodated in the MPLS FIB is therefore halved if uniform FRR is enabled. Ensure that sufficient MPLS resources are available to accommodate all required BGP LU routes before using this command.
The no form of this command disables the use of uniform FRR for BGP LU routes.
no enable-bgp3107-frr
enable-ldporsvp-frr
no enable-ldporsvp-frr
config>system>resource-profile
7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE
This command enables the allocation of MPLS FIB and protection group resources required for enabling uniform FRR for LDP-over-RSVP LSPs (LDP FECs resolved using RSVP-TE LSPs). This is a per-node configuration and enabling the command affects all LDP-over-RSVP LSPs.
If the command is enabled, the amount of resources required is twice the amount required without uniform FRR, and the number of LDP-over-RSVP LSPs that can be accommodated in the MPLS FIB is therefore halved if uniform FRR is enabled. Ensure that sufficient MPLS resources are available to accommodate all required LDP-over-RSVP LSPs before using this command.
The no form of this command disables the use of uniform FRR for LDP-over-RSVP LSPs.
no enable-ldporsvp-frr
[no] g8032-fast-flood-enable
configure>system>resource-profile>ingress-internal-tcam
7210 SAS-T
This command configures the G.8032 fast-flood feature. When this command is executed, it is stored in the configuration file after admin save is executed. A system reboot is required for this command to take effect.
Nokia recommends enabling this command to improve service failover time due to failures in the ring path. When fast flood is enabled, on failure detection in one of the paths of the ETH-ring, along with MAC flush, the system starts to flood the traffic on-to the available path.
If this command is present in the configuration file, on reboot, the system allocates resources for G.8032, by reducing the amount of resources available for use with ACLs. When this command is used, G.8032 fastflood needs an entire chunk with ‟512” entries, therefore the amount of resources available for use with ACLs is reduced by ‟512”. The user needs to free up resources used by ACLs and make them available for use by G.8032, before enabling this command. The user should ensure that the resource usage of ACLs has been appropriately modified before reboot, to make way for use of this feature. The user can free up resources by either disabling the use of ACLs with a SAP or deleting a SAP, so that an entire chunk of 512 entries is available.
Before enabling the g8032-fast-flood-enable command, the user must check if sufficient resources are available. The tools dump system-resources command is available to check if sufficient resources are available. The 'Ingress Shared CAM Entries' field, shown in the output below tools dump system resources command, must be more than or equal to 512 (the ‛Free’ column in the following output).
| Total | Allocated | Free
-------------------------------+-----------+-----------+------------
Ingress Shared CAM Entries | 0 | 0 | 512
The no form of this command removes the allocated resources for use by G.8032.The entire resource pool is available for use by ACLs. The no form of this command takes affect only on reboot.
no g8032-fast-flood-enable
decommission
config>system>resource-profile
7210 SAS-T (network and access-uplink)
Commands in this context decommission a port. Ports which are decommissioned using this command are not available for provisioning services. The packet buffers are taken away from the decommissioned port and allocated to port(s) as specified by the entries configured under the decommission command. This command allocates more packet buffers to a certain port or group of ports and enables those ports to absorb larger bursts.
entry entry-id port port-range to port-range
no entry entry-id
config>system>resource-profile>decommission
7210 SAS-T (network and access-uplink)
This command decommissions a port or group of ports and allocates buffers to ports that need more packet buffers for absorbing larger bursts. It allows the user to configure the entries which list the ports to be decommissioned. Ports whose packet buffers are taken away are given on the left-hand of the to keyword, and ports to which buffers are allocated to are given on the right-hand side.
This command allows the user to specify either a port or a group of ports on both sides, using a list or range of ports. This allows the user to decommission a single port and allocate buffers to a single port or group of ports, or decommission a group of ports and allocate buffers to a single port or group of ports.
Packet buffers taken away from a port or group of ports specified on the left-hand side are distributed equally among the group of ports, if the right-hand side of the to keyword specifies a group of ports or to the configured port if the right-hand side specifies a single port. 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 and operational states of the port are not affected by configuring the port in a decommission entry.
Any changes to the command, example - 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 ports on the CES MDA cannot be specified in the decommission command.
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. In other words, if two entries specify the same port ID, the software errors out the last entry which has the same port ID.
A port appearing on the left-hand side of the to keyword in any entry cannot appear on the right-hand side of any other entries (including the same entry) and the converse also holds 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 or a list of port ID or port ID ranges can be specified on the left-hand side and the right hand-side of the ‛to’ keyword. 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.
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.
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, 1/2/1, 1/1/10 is allowed
1/1/10, 1/1/2, 1/1/9, 1/1/5 is allowed
Range of ports can be specified as:
1/1/2-1/1/5 is allowed
1/2/1-1/2/2 is allowed
1/1/10-1/1/2 is not allowed
1/1/1 – 1/2/2 is not allowed
A combination of list of ports and range of ports can be specified as:
1/1/5,1/1/6,1/1/10-1/1/15,1/1/25 is allowed
1/1/5,1/1/6,1/1/10-1/1/12,1/1/13-1/1/15 is allowed
1/1/5,1/1/6,1/1/10-1/1/12,1/2/1-1/2/2 is allowed
Specifies a number in the range 1 to 30. A maximum of 30 entries can be created by the user.
Specifies the port, list of ports, a port range, or a combination of these that are being decommissioned when they appear on the left-hand side of the to keyword. This parameter identifies the port or group of ports that receives the packet buffers from the decommissioned ports. 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 (in other words, the first port number specified in the range must be greater than the second port number in the range) and a single range cannot refer to ports on different MDA or different IMMs or different slots.
egress-internal-tcam
configure>system>resource-profile
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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 to features in chunks of fixed size; multiple features cannot share the same chunk. The users can allocate the available resources based on their feature scaling requirements. The system allocates resources to the feature from its allocated chunk until the chunk runs out of resources. The users can reallocate chunks of resources from features that do not need to be enabled.
To free up the resources for use by one or more features, modify the configuration to release the chunks of resources that are in use by other features. For example, to free up a chunk of resources allocated to egress ACLs MAC criteria and allocate it to IP criteria, perform the following steps.
Remove the association of SAPs with egress ACLs that use a MAC criteria policy.
Change the resource profile configuration to allocate the chunk to IP criteria.
Create and associate the SAPs with the IP criteria.
To free up a chunk of resources used by egress ACLs and allocate it to the SAP egress aggregate meter (on platforms that support this feature), perform the following steps.
Remove the association of SAPs with egress ACLs.
Change the resource profile configuration to reduce the chunk resources allocated to egress ACLs (and reduce the value of chunks in use by the egress ACLs match criteria).
Allocate the chunk of resources to the SAP egress aggregate meter feature (on platforms that support this feature).
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-T access-uplink mode
Egress ACLs (all of IPv4, IPv6, MAC match-criteria), Per SAP Egress Aggregate Meter, and MAC authentication
7210 SAS-T network mode
Per SAP Egress Aggregate meter, Egress ACLs (all of IPv4, IPv6, and MAC match-criteria), and MAC authentication
7210 SAS-Mxp mode
Egress ACLs (all of IPv4, IPv6, and MAC match-criteria) and MAC authentication
7210 SAS-Sx 1/10GE mode (standalone and standalone-VC)
Per SAP Egress Aggregate meter, Egress ACLs (all of IPv4, IPv6, and MAC match-criteria), and MAC authentication
7210 SAS-S 1/10GE mode (standalone and standalone-VC)
Per SAP Egress Aggregate meter, Egress ACLs (all of IPv4, IPv6, and MAC match-criteria), and MAC authentication
7210 SAS-Sx 10/100GE mode
Per SAP Egress Aggregate meter and Egress ACLs (all of IPv4, IPv6, and MAC match-criteria)
7210 SAS-R6 IMMv2 and IMM-c
Per SAP Egress Aggregate meter, Egress ACLs (all of IPv4, IPv6, and MAC match-criteria), Ethernet CFM (bidirectional MIP), and MAC authentication
7210 SAS-R12 IMMv2 and IMM-c
Per SAP Egress Aggregate meter and Egress ACLs (all of IPv4, IPv6, and MAC match-criteria), Ethernet CFM (bidirectional MIP)
In some scenarios, reassigning a chunk of resources among features may require the node to be rebooted. See the CLI description of the feature for more information.
The egress internal TCAM pool of resources is available per node on the 7210 SAS-T, 7210 SAS-Sx/S 1/10GE (standalone), 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp. On the 7210 SAS-Sx/S 1/10GE (standalone-VC), 7210 SAS-R6, and 7210 SAS-R12, it is available as a per-IMM pool of resources.
It is possible to configure a resource profile per node or per card in a virtual chassis.
The number of chunks and the number of resources per chunk varies for the 7210 SAS platforms. Contact your Nokia technical support representative for more information.
To be enabled, some features require the allocation of a specific number of chunks (greater than 1). If the minimum number of chunks is not assigned, the system cannot allocate the required resources to the feature, which causes the command associated with the feature to fail.
acl-sap-egress [num-resources]
no acl-sap-ingress
configure>system>resource-profile>egress-internal-tcam
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command enables the user to 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. In other words, the cumulative sum of chunks allocated to different match criteria supported by filter policies cannot exceed the value configured with 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 egress filter policies. 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 any of the match criteria.
Specifies the amount of resources that can be allocated for use by ACL policies.
[no] egress-sap-aggregate-meter num-resources
configure>system>resource-profile>egress-internal-tcam
7210 SAS-T (network and access-uplink), 7210 SAS-Sx 1/10GE: standalone and standalone-VC, 7210 SAS-Sx 10/100GE, 7210 SAS-R6 and 7210 SAS-R12
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 the num-resources parameter.
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 software does not allocate any resources for use by the SAP egress aggregate policer. If no resources are allocated for use, the software fails all attempts to enable the configuration of the sap-aggregate-meter command for a SAP.
no egress-sap-aggregate-meter
Specifies the maximum amount of resources for use by this filter match criteria.
[no] ipv6-128bit-match-enable num-resources
configure>system>resource-profile>egress-internal-tcam>acl-sap-egress
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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-Mxp, R6, R12, S, Sx, T 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, 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 use of SAP egress aggregate meter.
[no] mac-ipv4-match-enable num-resources
configure>system>resource-profile>egress-internal-tcam>acl-sap-egress
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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-Mxp, R6, R12, S, Sx, T 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, 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 will fail. It is mutually exclusive to use of SAP egress aggregate meter.
[no] mac-ipv6-64bit-match-enable num-resources
configure>system>resource-profile>egress-internal-tcam>acl-sap-egress
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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-Mxp, R6, R12, S, Sx, T 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, 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 use of SAP egress aggregate meter.
[no] mac-match-enable num-resources
configure>system>resource-profile>egress-internal-tcam>acl-sap-egress
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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 the use of all available resources exclusively by MAC criteria egress filter policies and provides 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-Mxp, R6, R12, S, Sx, T 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, 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.
eth-cfm [num-resources]
no eth-cfm
configure>system>resource-profile>egress-internal-tcam
7210 SAS-R6 (IMMv2 and IMM-c) and 7210 SAS-R12 (IMMv2 and IMM-c)
This command applies only to VPLS SAPs on IMMv2 and IMM-c.
Commands in this context allocate resources for CFM bidirectional MIPs in a VPLS service.
The no form of this command allows the MIPs to retain the Down MEP by de-allocating the resources.
On the 7210 SAS-R6 and 7210 SAS-R12, the system does not allocate any ETH-CFM resource slices by default. The user must allocate ETH-CFM resource slices manually. The default number of resource slices is 0 and a maximum of 1 slice can be allocated.
Specifies the maximum amount of resources for use by ETH-CFM. Entering a value of def allocates the default number of resource slices.
bidir-mip-egress [num-resources]
no bidir-mip-egress
configure>system>resource-profile>egress-internal-tcam>eth-cfm
7210 SAS-R6 (IMMv2 and IMM-c) and 7210 SAS-R12 (IMMv2 and IMM-c)
This command allocates resources for the VPLS bidirectional MIP (both ingress and egress directions) on SAPs only from the egress internal TCAM resource pool.
The resources in the egress internal TCAM resource pool are shared with other features.
To assign resources to a specific feature, resources can be reallocated from other features. For example, you can release resources by disabling the policies associated with a SAP.
Resources must be allocated from this pool before bidirectional MIPs can be configured on VPLS SAPs.
Bidirectional MIPs on VPLS SAPs can be enabled only when the bidir-mip-egress resource slice is allocated and vpls-sap-bidir is enabled in the configure>service>vpls>eth-cfm context.
The no form of this command allocates no resources to this feature.
no bidir-mip-egress
Specifies the number of resources to allocate.
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-Mxp (standalone), 7210 SAS-R6 (all IMMs), 7210 SAS-R12 (all IMMs), 7210 SAS-Sx/S 1/10GE (standalone), 7210 SAS-T (network and access-uplink operating modes)
This command configures the allocation of resources for MAC authentication from the ingress internal TCAM pool and egress internal TCAM pool. Resources must be allocated from both ingress and egress TCAM pools before MAC authentication can be used. If resources are not allocated from both pools, the system returns an error message and MAC authentication cannot be enabled.
The configured number of resources specifies the number of resource pool slices allocated for use by MAC authentication. One entry is used for each authenticated source MAC address. The maximum number of MAC addresses that can be authenticated is limited by the number of entries allocated to the feature using this command. The maximum number of MAC address entries is limited by the maximum number of entries available in the ingress internal TCAM pool and the egress internal TCAM pool.
The no form of this command removes all resources allocated to MAC authentication; further attempts to enable MAC authentication on an Ethernet port using the mac-auth command will fail unless resources are first reallocated using the mac-auth-res command. The no form of the mac-auth-res command cannot be executed when MAC authentication is enabled on at least one port.
no mac-auth-res
Specifies the number of resources to allocate for MAC authentication. Configuring a value of 0 is equivalent to configuring no mac-auth-res and effectively disables MAC authentication.
[no] g8032-control-sap-tags vlan-range
configure>system>resource-profile
7210 SAS-Sx 1/10GE: standalone and standalone-VC, 7210 SAS-R6, 7210 SAS-R12
This command configures the range of VLANs per IMM to be used internally with G8032 MEPs that support hardware CCM message processing.
Users must ensure that the VLANs configured for use with G8032 MEPs are not configured for any of the SAPs configured on the IMM.
Use one of the VLANs configured with this command to configure the VLAN for the G8032 MEP configure>eth-ring>path>eth-cfm>mep>control-sap-tag.
no g8032-control-sap-tags
Specifies the range of VLANs per IM.
qos-sap-egress-resource num-resources
no qos-sap-egress-resource
config>system>res-prof>ingress-internal-tcam
7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Mxp
This command configures resource allocation for SAP-based egress queuing from the ingress-internal-tcam resource pool. If port-based queuing is disabled, users must allocate resources for SAP-based egress queuing using this command. If no resources are allocated, SAPs cannot be created.
When port-based queuing is enabled, resources can be taken away from SAP-based egress queues and allocated to other features that share the ingress-internal-tcam pool (for example, SAP ingress QoS and Ingress ACLs).
This command is not supported on IMM-c cards. SAP functionality with per SAP egress queues is not supported on IMM-c cards.
The no form of this command reverts to the default value.
0
Specifies the amount of resources that are allocated towards SAP-based egress queues.
ingress-internal-tcam
configure>system>resource-profile
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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 size; multiple features cannot share the same chunk. The users can allocate the available resources based on their feature scaling requirements. The resource usage for different features is provided in the CLI description. The system allocates resources to the feature from its allocated chunk until the chunk runs out of resources. The users can reallocate chunks of resources from features that do not need to be enabled.
To free up the resources for use by one or more features, modify the configuration to release chunks of resources that are in use by other features. For example, to free up a chunk of resources allocated to ingress ACLs MAC criteria and allocate the chunk to IP criteria, perform the following steps.
Remove the association of all the SAPs with ingress ACLs that use a MAC criteria policy.
Change the resource profile configuration to allocate the chunk to IP criteria.
Create (can be done before hand) and associate the SAPs with IP criteria.
For another example, to free up a chunk of resources used by ingress ACLs and allocate it towards SAP ingress QoS classification, perform the following steps.
Remove the association of all the SAPs with ingress ACLs.
Change the resource profile configuration to reduce the chunk resources allocated to ingress ACLs (and also to reduce the amount configured for specific match-criteria).
Allocate the chunk of resources to SAP ingress QoS classification feature.
Configure the SAPs with the SAP ingress QoS policies.
The following table describes the sharing of the ingress internal TCAM resource pool among the features on different 7210 SAS platforms.
Platform |
Features sharing ingress internal TCAM resource pool |
|---|---|
7210 SAS-T access-uplink mode |
|
7210 SAS-T network mode |
|
7210 SAS-Mxp |
|
7210 SAS-R6 and 7210 SAS-R12 |
On the 7210 SAS-R6 and 7210 SAS-R12, the features that share the resource pool are different based on the IMM card type. On IMMv2 and IMM-c cards2, this resource pool is shared among the following features:
|
7210 SAS-Sx 1/10GE (standalone) |
|
7210 SAS-Sx 1/10GE (standalone-VC) |
|
7210 SAS-S 1/10GE (standalone) |
|
7210 SAS-S 1/10GE (standalone-VC) |
|
7210 SAS-Sx 10/100GE |
|
In some scenarios, reassigning a chunk of resources among features may require the node to be rebooted. See the CLI description of the specific feature for more information.
The ingress internal TCAM pool of resources is available per node on the 7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE. On the 7210 SAS-Sx/S 1/10GE (standalone-VC), 7210 SAS-R6, and 7210 SAS-R12, it is available as a per-IMM pool of resources.
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.
To be enabled, some features require the allocation of a specific number of chunks (greater than 1). If the minimum number of chunks is not assigned, the system cannot allocate the required resources to the feature, which causes the command associated with the feature to fail.
acl-sap-ingress [num-resources]
no acl-sap-ingress
configure>system>resource-profile>ingress-internal-tcam
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command allocates 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.
Ingress ACL resources are shared with SAP ingress aggregate meter. See the sap-aggregate-meter command for more information.
The no form of this command removes any allocated resources for use by filter policies. Consequently, the software fails all attempts to associate a service entity (for example, SAP and 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.
Some platforms include the value def. If the user specifies def, the software allocates the default amount of resources based on the 7210 SAS platform. On the 7210 SAS-R6 and 7210 SAS-R12, the amount of default resources allocated also varies based on the IMM plugged into the slot.
[no] ipv4-ipv6-128-match-enable
configure>system>resource-profile>ingress-internal-tcam>acl-sap-ingress
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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-Mxp, R6, R12, S, Sx, T 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 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 and IP interface) with an ingress filter policy using this match criteria.
Specifies the maximum amount of resources for use by this filter match criteria.
Some platforms include the value max. 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 an 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.
ip-dscp-port-if-match-enable num-resources
no ip-dscp-port-if-match-enable
configure>system>resource-profile>ingress-internal-tcam>qos-sap-ingress-resource
7210 SAS-Mxp, 7210 SAS-R6 and 7210 SAS-R12
This command allocates resources for use by SAP ingress QoS policies that use IP DSCP table-based classification.
The available resources are used by software to allocate policers for SAPs whose ingress policy uses the IP DSCP table-based classification policy. The users need to allocate resources from the ingress internal TCAM pool before DSCP classification can be used. This means users need to take away resources from other features such as mac-match criteria from the SAP ingress classification or ACL ingress to allocate resources for DSCP classification.
See the 7210 SAS-Mxp, R6, R12, S, Sx, T Quality of Service Guide for more information about resource allocation and fields available for use.
The no form of this command does not allocate any resources for use by SAP ingress QoS policies using a DSCP table-based classification policy. 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 the DSCP table-based classification policy.
Specifies the maximum amount of resources (slices) for use by the DSCP table-based classification policy. Each slice has a fixed number of entries. DSCP table-based classification requires exclusive use of the allocated resources.
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 an ingress filter policy using this criteria, provided that the total amount of resources allocated does not exceed the resources allocated to qos-sap-ingress-qos resource pool (configured with the config system resource-profile ingress-internal-tcam qos-sap-ingress-resource command) and chunks are available for use.
ipv4-mac-match-enable num-resources
no ipv4-mac-match-enable
configure>system>resource-profile>ingress-internal-tcam>qos-sap-ingress-resource
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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 available resources is used by software to allocate 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-Mxp, R6, R12, S, Sx, T Quality of Service Guide for more information about resource allocation.
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, then software fails all attempts to associate a service entity (for example, SAP and IP interface) with an ingress filter policy or SAP ingress QoS policy using this match criteria.
Specifies the maximum amount of resources for use by this 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 an 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.
ipv4-match-enable num-resources
no ipv4-match-enable
configure>system>resource-profile>ingress-internal-tcam>acl-sap-ingress
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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-Mxp, R6, R12, S, Sx, T Router Configuration Guide for more information about resource allocation and fields available for use.
Ingress ACL resources are shared with SAP ingress aggregate meter. See the sap-aggregate-meter command for more information.
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, the software fails all attempts to associate a service entity (for example, SAP and IP interface) with an 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 SAPs associated with an 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 us.
ipv4-match-enable num-resources
no ipv4-match-enable
configure>system>resource-profile>ingress-internal-tcam>qos-sap-ingress-resource
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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-Mxp, R6, R12, S, Sx, T 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 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 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 a SAP ingress QoS policy using this match criteria. It continues to allocate resources to SAPs associated with a SAP ingress QoS policy using this criteria, as long as the total amount of resources allocated does not exceed the resources allocated to SAP ingress QoS policies (configured with the config system resource-profile ingress-internal-tcam qos-sap-ingress- resource command) and chunks are available for use.
ipv6-64-only-match-enable num-resources
no ipv6-64-only-match-enable
configure>system>resource-profile>ingress-internal-tcam>acl-sap-ingress
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command allocates maximum resources for use by ingress filter policies using ipv6 criteria with 64-bit IPv6 addresses. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Router Configuration Guide for more information about resource allocation and fields available for use.
The resources cannot be shared with IPv4 filter policies or IPv6 filter policies specifying 128-bit addresses.
Ingress ACL resources are shared with SAP ingress aggregate meter. See the sap-aggregate-meter command for more information.
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, the software fails all attempts to associate a service entity (for example, SAP and IP interface) with an 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 SAPs associated with an 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.
mac-match-enable num-resources
no mac-match-enable
configure>system>resource-profile>ingress-internal-tcam>acl-sap-ingress
Supported on all 7210 SAS platforms as described in this document
This command allocates maximum resources for use by ingress filter policies using mac criteria.
The resources cannot be shared with policies that use either IPv4 or IPv6 match criteria. Refer the 7210 SAS-Mxp, R6, R12, S, Sx, T Router Configuration Guide for more information about the resource allocation for 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, the software fails all attempts to associate a service entity (for example, SAP and IP interface) with an ingress filter policy using this match criteria.
Ingress ACL resources are shared with SAP ingress aggregate meter. See the sap-aggregate-meter command for more information.
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 SAPs associated with an 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.
mac-match-enable num-resources
no mac-match-enable
configure>system>resource-profile>ingress-internal-tcam>qos-sap-ingress-resource
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command allocates maximum resources for use by SAP ingress QoS policies using MAC criteria (any).
The resources cannot be shared with policies that use either IPv4 or IPv6 match criteria. See the 7210 SAS-Mxp, R6, R12, S, Sx, T 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 SAPs associated with SAP ingress QoS policy using this criteria, as long as the total amount of resources allocated does not exceed the resources allocated to SAP ingress QoS policies (configured with the config system resource-profile ingress-internal-tcam qos-sap-ingress-resource command) and chunks are available for use.
cpu-protection [num-resources]
no cpu-protection
configure>system>resource-profile>ingress-internal-tcam
7210 SAS-R6 and 7210 SAS-R12
This command allocates CAM entries and meters for CPU protection rules and policies by removing entries from other features that share the ingress internal TCAM resource pool.
cpu-protection 0
Specifies the number of resources. Specifying the def keyword specifies the default number of resources.
dhcp-snooping-sdp-resource num-resources
no dhcp-snooping-sdp-resource
configure>system>resource-profile>ingress-internal-tcam
7210 SAS-Mxp and 7210 SAS-Sx/S 1/10GE (standalone)
This command configures the resources required to classify and intercept DHCPv6 messages received on SDP bindings (spoke SDP and mesh SDP in TLDP VPLS services).
The no form of this command specifies that the software does not allocate any resources to process DHCPv6 messages received on SDP bindings (spoke-SDP and mesh SDP).
no dhcp-snooping-sdp-resource
Specifies the maximum resource allocation required to process DHCPv6 messages.
eth-cfm num-resources
no eth-cfm
configure>system>resource-profile>ingress-internal-tcam
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command allocates resources for CFM Up MEPs, CFM Down MEPs, ingress MIPs, and bidirectional MIPs (ingress and egress MIPs).
On most 7210 SAS platforms, ingress MIPs and bidirectional MIP resources are allocated from the Down MEP and Up MEP resource pool. See the down-mep and up-mep commands for more information.
The no form of this command specifies that the software does not allocate any resources for use by CFM UP MEPs, and it will allocate the default amount of resources for CFM Down MEPs.
Specifies the maximum number of resources available for use by ETH-CFM.
down-mep num-resources
no down-mep
configure>system>resource-profile>ingress-internal-tcam>eth-cfm
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE
This command enables the user to allocate more resources and increase the number of CFM/Y.1731 Down MEPs. By default, the system allocates a single slice for use with Down MEP.
Resources from this pool are allocated towards the following:
down MEP on SDP binding
on the 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone), ingress and egress MIPs for Epipe SAPs and Epipe SDP bindings
on the 7210 SAS-R6 and 7210 SAS-R12, ingress and egress MIPs (that is, bidirectional MIPs) for Epipe SAPs and Epipe SDP bindings
On the 7210 SAS-R6 and 7210 SAS-R12, bidirectional MIPs also use the Up MEP resource pool.
On the 7210 SAS-R6 and 7210 SAS-R12, this is a per-IMM resource. For SAPs, the resources are required only on the IMM for which the SAP is allocated. For SDP bindings, resources are required on all IMMs because MPLS packets could be received on any network port.
Some entries are reserved for system internal use.
The no form of this command is not supported. At least a single slice must be allocated for use with Down MEPs because some of the resources are reserved for system internal use. The software enforces it and errors out an attempt to change it to a value less than 1.
Specifies the maximum amount of resources for use by down-mep.
sap-down-mep num-resources
no sap-down-mep
configure>system>resource-profile>ingress-internal-tcam>eth-cfm
7210 SAS-Sx/S 1/10GE: standalone-VC
This command configures resources for CFM/Y.1731 down MEPs on SAPs.
The no form of this command removes resources for down MEPs on SAPs.
1
Specifies the maximum amount of resources for use by down MEPs on SAPs.
sdp-down-mep-ing-mip num-resources
no sdp-down-mep-ing-mip
configure>system>resource-profile>ingress-internal-tcam>eth-cfm
7210 SAS-Sx/S 1/10GE: standalone-VC
This command configures resources for CFM/Y.1731 Down MEPs on SDPs and ingress MIPs on SAPs and SDP bindings. In addition, resources for bidirectional MIPs configured on an Epipe SAP and Epipe SDP binding are allocated from this pool.
On the 7210 SAS-Sx/S 1/10GE operating in standalone-VC mode, bidirectional MIPs configured on Epipe SAPs and Epipe SDP bindings also require resources from the Up MEP resource pool.
The no form of this command removes resources for Down MEPs on SDPs, ingress MIPs, and bidirectional MIPs.
sdp-down-mep-ing-mip 1
Specifies the maximum amount of resources for use by Down MEPs on SDPs and ingress MIPs.
up-mep num-resources
no up-mep
configure>system>resource-profile>ingress-internal-tcam>eth-cfm
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command allocates resources for CFM Up MEPs.
Resources for Up MEPs created on SAPs and SDP bindings are allocated from this pool.
On the 7210 SAS-R6 and 7210 SAS-R12, when an Up MEP on an SDP binding is created, resources are allocated for the Up MEP on all IMMs, and when an Up MEP on a SAP is created, resources are allocated only on the IMM for which the SAP is configured or on the set of IMMs if the SAP is configured over a LAG.
On the 7210 SAS-R6 and 7210 SAS-R12, resources from this pool are used only for Up MEPs configured in Epipe services. Up MEPs configured in a VPLS service use resources from a different pool.
On the 7210 SAS-R6 and 7210 SAS-R12, and on the 7210 SAS-Sx/S 1/10GE operating in standalone-VC mode, resources from this pool are also used for bidirectional MIPs configured on Epipe SAPs and Epipe SDP bindings.
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, the software fails all attempts to configure an Up MEP and bidirectional MIPs on applicable platforms (see preceding Note).
up-mep 0
Specifies the maximum number of resources available for use by CFM Up MEPs.
ipv6-ipv4-match-enable num-resources
no ipv6-ipv4-match-enable
configure>system>resource-profile>ingress-internal-tcam>qos-sap-ingress-resource
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
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-Mxp, R6, R12, S, Sx, T Router Configuration Guide for more information about the resource allocation for ingress filter policy and fields available for use with ingress filter policy.
See the 7210 SAS-Mxp, R6, R12, S, Sx, T 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 ingress SAP QoS policies 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 an 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 a SAP ingress QoS policy using this match criteria. It continues to allocate resources to SAPs associated with SAP ingress QoS policy using this criteria, as long as the total amount of resources allocated does not exceed the resources allocated to SAP ingress QoS policies (configured with the command config system resource-profile ingress-internal-tcam qos-sap-ingress-resource command) and chunks are available for use.
ip-mpls-protocols num-resources
no ip-mpls-protocols
config>system>resource-profile>ing-internal-tcam
7210 SAS-Mxp
This command configures an additional slice from the ingress-internal-tcam resource pool for use by the IP and MPLS protocols.
On boot up, by default, the software allocates a single slice of entries from the ingress-internal-tcam resource pool for use by the IP and MPLS control protocols. Entries from that slice are allocated to the following protocols on a first-come-first-serve basis when the user enables the protocol: OSPFv2, OSPFv3, BGP, IS-IS, LDP, RSVP, VRRP, MC-LAG, VRRPv3, PCEP, PIM, IGMP, DHCP, DHCPv6, and PTP.
However, the default single slice of entries is not sufficient if all IP and MPLS control-plane protocols are enabled simultaneously. To allocate an additional slice to IP and MPLS protocols, use this command to set the value of num-resources to 2.
The software allocates protocol entries when the protocol is enabled and deallocates the protocol entries when the protocol (and all instances of the protocol, if any) is disabled. See the relevant CLI command descriptions for more information about resource allocation for specific protocols. To display information about the utilization of resources allocated to IP and MPLS protocols, use the tools>dump>system-resources CLI command.
The no form of this command reverts to the default value.
ip-mpls-protocols 1
Specifies the number of slices to be allocated for IP and MPLS control-plane protocols.
qos-access-port-ingress-resource num-resources
no qos-access-port-ingress-resource
configure>system>res-profile>ing-internal-tcam
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)
This command allocates ingress internal TCAM resources to access-ingress port policies when the access port is configured in port mode. If adequate TCAM resources are not allocated, setting the access-ingress-qos-mode command to port-mode is not allowed.
If access ports are currently configured to use a port-based access ingress QoS policy, setting the qos-access-port-ingress-resource command to 0 (which will set the number of resources allocated to the access port ingress QoS policy to 0) is not allowed. Resources allocated to access ingress QoS policies are used to allocate meter resources for the port-based access ingress QoS policy.
On the 7210 SAS-Sx 10/100GE, the sum of resources, also called slices, allocated to SAP ingress policies using the config>system>resource-profile>ingress-internal-tcam>qos-sap-ingress-resource command and to access ingress policies using the config>system>resource-profile>ingress-internal-tcam>qos-access-port-ingress-resource command must not exceed 3.
The no form of this command reverts to the default value.
qos-access-port-ingress-resource 0
Specifies the amount of resources allocated to QoS access port ingress policies.
qos-network-ingress-resource num-resources
no qos-network-ingress-resource
config>system>res-prof>ing-internal-tcam
7210 SAS-R6 and 7210 SAS-R12
This command removes resources allocated to port-based and IP interface-based network ingress QoS policies associated with network and hybrid ports, and makes the resources available for other features that share the ingress-internal-tcam resource pool (for example, SAP ingress classification and ingress ACLs).
The minimum num-resources configurable is 0 and the maximum num-resources configurable is 2. The default num-resources is 2 for the default system resource profile and user-configured system resource profile. A value of 1 is not allowed.
If the user configures the value 2, one slice is allocated to the network QoS policy IP interface, and one slice is allocated to the network QoS policy port.
A reboot is not required after assigning a new value to the qos-network-ingress-resource command. That is, the value of this command can be changed from 0 to 2 if there are resources available in the ingress-internal-tcam pool. Similarly, the value can be changed from 2 to 0 if no network or hybrid ports are configured. If a network port or hybrid port is configured, changing the value from 2 to 0 is fails and the system sends an error message.
The no form of this command reverts to the default value.
qos-network-ingress-resource 0
Specifies the number of resources allocated to network ingress QoS policy queues.
qos-sap-ingress-resource num-resources
no qos-sap-ingress-resource
configure>system>resource-profile>ing-internal-tcam
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode
This command allocates 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. That is, the cumulative sum of chunks allocated to different match criteria supported by SAP ingress QoS policies cannot exceed the value configured with num-resources.
On the 7210 SAS-Sx 10/100GE, the sum of resources, also called slices, allocated to SAP ingress policies using the config>system>resource-profile>ingress-internal-tcam>qos-sap-ingress-resource command and to access ingress policies using the config>system>resource-profile>ingress-internal-tcam>qos-access-port-ingress-resource command must not exceed 3.
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 any of the match criteria. )
The no form of this command specifies that the software does not allocate any resources for use by SAP ingress QoS policies.
Specifies the amount of resources that can be allocated for use by SAP ingress QoS policies.
If the user specifies def, the software allocates the default amount of resources based on the 7210 SAS platform. On 7210 SAS-R6 and 7210 SAS-R12, the amount of default resources allocated also varies based on the IMM plugged into the slot.
qos-sap-egress-resource num-resources
no qos-sap-egress-resource
config>system>res-prof>ing-internal-tcam
7210 SAS-R6 and 7210 SAS-R12 (only supported on IMMv2 cards; not supported on IMM-c cards)
This command configures resource allocation for SAP-based egress queuing. If port-based queuing is disabled, then users must allocate resources for SAP-based egress queuing using this command. If no resources are allocated, SAPs cannot be created.
When port-based queuing is enabled, resources can be taken away from SAP-based egress queues and allocated to other features that share the ingress-internal-tcam pool (for example, SAP ingress qos and Ingress ACLs).
The no form of this command reverts to the default value.
0
Specifies the amount of resources that are allocated towards SAP-based egress queues.
sap-aggregate-meter num-resource
no sap-aggregate-meter
configure>system>resource-profile>ingress-internal-tcam
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode; not supported on the 7210 SAS-Sx 1/10GE and 7210 SAS-Sx 10/100GE
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. Before using the configure service sap ingress aggregate-meter-rate command, the user must ensure that resources are allocated to aggregate meters using this command.
For the command to take effect, the node must be restarted 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. Hence, 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 configures resources for SAP aggregate meter using this command, the software does the following.
It does not allocate any additional 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 the user has allocated 2 chunks of 512 entries each for ingress ACLs and then configures sap-aggregate-meter to use 2 chunks to use about 512 aggregate meters, the software will 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, then it allocates the difference from the available global ingress CAM resource pool. For example, if the user has allocated 1 chunk of 512 entries for ingress ACLs and then configures sap-aggregate-meter to use 2 chunks to use about 512 aggregate meters, the software will allocate 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 the user allocates resources for SAP aggregate meters using this command and then configures resources for ingress ACLs. 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 512 entries each for SAP aggregate meters and then configures ingress ACLs to use 2 chunks to use about 512 classification entries, the software will 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, then it allocates the difference from the available global ingress CAM resource pool. For example, if the user has allocated 1 chunk of 512 entries for SAP aggregate meters and then configures ingress ACLs to use 2 chunks, the software will allocate 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 need be.
See the 7210 SAS-Mxp, R6, R12, S, Sx, T Quality of Service Guide and the 7210 SAS-Mxp, R6, R12, S, Sx, T Router Configuration Guide for more information about use of SAP aggregate feature, ingress CAM resource allocation, and use of ACLs policies respectively.
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, 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.
If the user specifies def, the software allocates the default amount of resources based on the 7210 SAS platform. On 7210 SAS-R6 and 7210 SAS-R12, the amount of default resources allocated also varies based on the IMM plugged into the slot.
qos
configure>system>resource-profile
7210 SAS-T (network and access-uplink), 7210 SAS-Mxp
Commands in this context configure QoS parameters.
mbs-pool {node | port}
configure>system>resource-profile>qos
7210 SAS-T (network and access-uplink)
On 7210 SAS-T, the user has an option to configure the MBS pool per node or per port. This command allows the user to configure the MBS pool as per their requirement. A reboot is needed whenever the value of this parameter is changed for the new values to take effect.
If the users configure a per node MBS pool, then each of the 8 queues available on a port is allocated a CBS amount of committed buffers. The remaining amount of buffers is allocated towards the MBS pool that is available for sharing among all the queues across all the ports of the node. In other words the MBS pool is per node.
If the users configure a per port MBS pool, the available buffers are equally divided up among the all the ports of the node. With this scheme of allocation, each port gets some portion of the buffers for its exclusive use. Some of these buffers are allocated towards the CBS per queue and the rest is assigned to the per port MBS pool. To allow operators better control over which ports get larger portion of queue buffers, operator is provided with an option to decommission ports. The commands associated with decommissioning of ports are only allowed when the node is booted with the option to use per-port MBS pool. In other words, decommission entries are executed only if the mbs-pool parameter is set to port.
If the mbs-pool parameter is set to node and decommission entries are configured, then an error should be reported. All decommission entries must be removed if the mbs-pool parameter needs to be changed from port to node.
node
Keyword to use per-node MBS pool.
Keyword to use per-port MBS pool, along with an option to relocate buffers to ports that need better burst handling capability using the decommissioning commands.
port-scheduler-mode
no port-scheduler-mode
config>system>resource-profile>qos
7210 SAS-Mxp
This command configures the queuing mode to be used for SAPs configured on all the ports of the node.
When port-scheduler-mode is enabled, software allocates 8 egress queues per port and all the SAPs configured on the access port or hybrid port will share the 8 egress queues for traffic sent out of that port. In this mode, SAPs configured on hybrid port shares the egress queues with network port traffic. Enabling port-scheduler-mode affects the behavior for all the SAPs configured on all the access and hybrid port. In this mode, per SAP egress queues are not available.
In this mode, resources allocated towards SAP egress queues in the ingress-internal-tcam pool are not required by this feature and can be allocated towards other features. See the qos-sap-egress-resource command for more information.
The no form of this command disables port-scheduler-mode, causing per SAP egress queues to be available for use. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Quality of Service Guide for more information about the two modes.
Enabling or disabling port-scheduler-mode requires a reboot of the node.
no port-scheduler-mode
router
configure>system>resource-profile
configure>system>global-res-profile
Supported on all 7210 SAS platforms as described in this document
The configure>system>resource-profile context is supported on the 7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE: standalone, and 7210 SAS-Sx 10/100GE.
The configure>system>global-res-profile context is supported on the 7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Sx/S 1/10GE: standalone-VC.
Commands in this context configure router parameters that is applicable to the entire chassis (in other words it applies to all IMMs).
ecmp max-routes-dest
no ecmp
configure>system>resource-profile>router
configure>system>global-res-profile>router
Supported on all 7210 SAS platforms as described in this document
The configure>system>resource-profile context is supported on the 7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE: standalone, and 7210 SAS-Sx 10/100GE.
The configure>system>global-res-profile context is supported on the 7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Sx/S 1/10GE: standalone-VC.
This command configures the maximum amount of routes of same cost to the same IP destination/prefix when path sharing is enabled using IP ECMP. To enable optimum usage of hardware resources, software allocates hardware resources in groups of fixed number of entries. A group is a set of IP next-hop entries used by ECMP routes. The number of IP next-hop entries per group (which in turn dictates the maximum number of shared IP paths per IP destination/prefix) is also specified with commands. The software uses the same group if all the IP next-hop in use for the ECMP routes is the same.
This parameter also dictates the maximum number of paths that a single LDP FEC can use.
This command does not enable the use of IP ECMP. To enable IP ECMP, the user must use the config router ecmp command. The number of routes specified using the config router ecmp command cannot exceed the number of routes specified by this command, though it can be lesser. If its lesser, the software will use only the specified number routes. Specifying a lesser number of routes with config router ecmp will result in wastage of hardware resources. To enable LDP ECMP, see the configure system resource-profile router ldp-ecmp command.
This command is a boot-time parameter and any change will take effect only after a reboot.
On 7210 SAS-R6 and 7210 SAS-R12, the value specified with this command is used across all IMMs in the chassis.
1
Specifies the number of ECMP routes.
ldp-ecmp percent-value
no ldp-ecmp
configure>system>resource-profile>router
configure>system>global-res-profile>router
Supported on all 7210 SAS platforms as described in this document
The configure>system>resource-profile context is supported on the 7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE: standalone, and 7210 SAS-Sx 10/100GE.
The configure>system>global-res-profile context is supported on the 7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Sx/S 1/10GE: standalone-VC.
This command enables LDP ECMP and configures the percentage of the total amount of hardware ECMP resources to be allocated for use by LDP ECMP FECs.
The remaining amount of resources are allocated for use by IP ECMP. In other words, the hardware ECMP resources are shared by IP ECMP and LDP ECMP and this command allow user to allocate resources to them.
The no form disables LDP ECMP (by allocating zero resources to it) and the system installs only a single next-hop for every LDP FEC.
On 7210 SAS-R6 and 7210 SAS-R12, it is a system wide limit, applicable to all IMMs. If the user changes this value dynamically, the system adjusts the usage among IP and LDP ECMP as per the configuration.
The user can change the value of resources allocated towards IP ECMP routes and LDP ECMP FECs without requiring a reboot of the node as long as the following conditions are met. The configure system resource-profile router ldp-ecmp command cannot be modified until the value of the configure router ecmp command is set to 1. It is similar to the behavior available for the configure system resource-profile router ecmp command. The value cannot be changed until the value of the configure router ecmp command is set to 1.
no ldp-ecmp
Specifies the percentage of ECMP hardware resources to allocate to LDP ECMP. The rest is allocated towards IP ECMP.
max-ip-subnets number
no max-ip-subnets
configure>system>resource-profile>router
configure>system>global-res-profile>router
Supported on all 7210 SAS platforms as described in this document
The configure>system>resource-profile>router context is supported on the 7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE: standalone, and 7210 SAS-Sx 10/100GE.
The configure>system>global-res-profile>router context is supported on the 7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Sx/S 1/10GE: standalone-VC.
This command configures the number of directly connected IP interfaces and subnets (both IPv4 and IPv6) the user plans to use on the node, so that only the requisite number of entries in the L3 forwarding table are allocated. On the 7210 SAS platforms, the hardware L3 forwarding table (that is, the IP IFB) stores the IP routes (both IPv4 and IPv6) received from routing peers and also stores the IP address prefix for the directly connected interfaces. The rest are available for use by IP routes received from peers.
This command provides the flexibility to earmark resources based on the number of directly connected interfaces required on the node, allowing the user to decrease the number of resources for directly connected subnets and consequently increase the number of entries available for IP routes received from peers. See the description of the max-ipv6-routes command for more information about IP route allocation.
Each IPv4 subnet configured on the node requires 1 entry and each IPv6 subnet configured on the node requires 2 entries. Each IPv6 /64-bit address prefix requires twice the amount of space needed for an IPv4 address prefix. Additionally, the user must account for resources required for IPv6 primary and secondary addresses assigned to an IPv6 interface.
The number of entries available for IP routes received from a peer is equal to the total number of L3 forwarding entries supported for the platform subtracted by the number of entries specified by this command.
The software allocates entries from this pool on a FCFS (first come first serve) model based on the order of configuration of IP interfaces. An error is generated when the maximum limit is reached.
no max-ip-subnets (Software allocates a fixed number of entries towards this to maintain backward compatibility with releases prior to Release 7.0.R3).
Specifies the number of IP subnets for directly connected IP interfaces.
[no] max-ipv6-routes number
configure>system>resource-profile>router
configure>system>global-res-profile>router
Supported on all 7210 SAS platforms as described in this document
The configure>system>resource-profile>router context is supported on the 7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE.
The configure>system>global-res-profile>router context is supported on the 7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Sx/S 1/10GE (standalone-VC).
This command allocates route entries for /64-bit IPv6 prefix. Entries in the IPv4 forwarding table are shared among IPv4 and IPv6 routes. Before adding routes for IPv6 destinations, route entries in the route lookup table must be allocated for IPv6 addresses using this command. The remainder of the L3 forwarding table is used for IPv4 routing entries. The system does not allocate any IPv6 route entries by default for /64-bit prefix, and the user must allocate some resources before using IPv6.
Each IPv6 /64-bit route requires twice the amount of resources taken up by an IPv4 route. The number of hardware route entries allocated by the software for IPv6 /64-bit routes is equal to twice the amount of the value specified using this command.
For this command to take effect, reboot the node after making the change.
On the 7210 SAS-T, a separate route table is used for IPv6 /128-bit prefix route lookup. A limited amount of IPv6 /128-bit prefixes is supported. The software enables lookups in this table by default; no user configuration is required to enable IPv6 /128-bit route lookup.
On the 7210 SAS-R6 and 7210 SAS-R12 with IMMv2, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp, the IPv6 /128-bit prefixes are allocated by software on boot up. The resources are taken from the IP FIB shared with IPv4 and IPv6 /64-bit route entries. That is, unlike platforms like 7210 SAS-T and others, a separate route table is not available in hardware on these platforms. This affects the scaling of IPv4 routes when IPv6 /64-bit routes are allocated. See the following bullets for more information.
On the 7210 SAS-R6 and 7210 SAS-R12 IMMv2 card, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp, each IPv6 /128-bit route entry/address prefix requires 4 entries in the IP hardware route table, each IPv6 /64-bit address prefix requires 2 entries and each IPv4 route entry/address prefix requires 1 entry.
The creation of IPv6 IP interfaces without allocating IPv6 route entries is allowed. However, only IPv6 hosts on the same IPv6 subnet are reachable.
On the 7210 SAS-R6 and 7210 SAS-R12, the value configured using this command is used across all IMMs in the chassis.
The number of available IPv4 route entries in the L3 forwarding table is equal to the total L3 forwarding entries supported for the platform subtracted by the total number of entries reserved by this command and the number of entries reserved for IP subnets using the max-ip-subnets command. See the following bullets for more information.
On the 7210 SAS-T, the maximum number of IPv4 prefixes without any IPv6 interfaces configured and IPv6 /64-bit routes (that is, the max-ipv6-routes command is set to a value of zero) is equal to the maximum size of the route table supported for the platform. Contact a Nokia representative to learn more about the routing table scaling limits for each 7210 SAS platform.
(Continued)
On the 7210 SAS-R6 and 7210 SAS-R12 IMMv2 card, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), and 7210 SAS-Mxp, a pool of 4K IPv4 entries are allocated on system bootup primarily for use by about 256 /128-bit IPv6 addresses. The remaining entries can be shared with IPv4 prefix, if IPv6 is not enabled on the node. That is, without IPv6 enabled on the node, the maximum number of IPv4 prefixes possible is equal to the maximum size of the route table supported for the platform, reduced by 1K entries. The 1K entries correspond to those reserved by the system for allocation to IPv6 /128-bit addresses.
Note that the maximum number of IPv4 prefixes includes the amount of addresses allocated for directly connected IP subnets (the user has an option to reserve the amount required for directly connected IPv4 subnets by configuring the max-ip-subnets command) and IPv4 routes statically configured on the node or learned dynamically using a routing protocol.
For example, if the maximum size of the route table supported on the node is 32K, the total number of IPv4 prefixes (including both directly connected subnets and routes statically configured or dynamically learned using a routing protocol) is 31K (the 1K route entries are used to allocate up to 256 /128-bit IPv6 addresses). The maximum size of the route table quoted in the example is for illustration purposes only.
On the 7210 SAS-R6 and 7210 SAS-R12 IMMv2 card, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), and 7210 SAS-Mxp, the maximum number of IPv4 prefixes possible with IPv6 /64-bit routes configured is equal to the maximum size that the route table supports for the platform, reduced by the sum of the number of routes configured for IPv6 /64-bit prefixes and an amount of 4K entries (reserved for /128-bit IPv6 addresses). The user has an option to reserve resources used for IPv6 /64-bit prefix using the max-ipv6-routes command. When max-ipv6-routes is configured using a value greater than zero, the IPv4 prefixes can no longer use the space reserved for IPv6 /128-bit addresses. The software enforces the maximum number of IPv6 prefixes possible as less than the max-ipv6-routes value.
Using the preceding example, if the maximum size of the route table supported on the node is 32K, total number of IPv4 prefixes (only dynamically learned ones using a routing protocol) is about 25K, assuming max-ipv6-routes is set to 1000 and max-ip-subnets is set to 1000. That is, 32K – (4K + 2 * 1K + 1K) = 25K (recollect each IPv6 /64-bit route entry requires twice the space of IPv4 route entry). The maximum size of the route table quoted in the example is for illustration purposes only.
On the 7210 SAS-R6 and 7210 SAS-R12 IMMv2 card, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp, the maximum number of IPv6 /64-bit routes is equal to the number of routes configured using the max-ipv6-routes command.
Using the preceding example, if the maximum size of the route table supported on the node is 32K, maximum number of IPv6 /64-bit prefixes (including only dynamically learned ones, using a routing protocol) is about 13500, assuming max-ipv6-routes is set to 13K and max-ip-subnets is set to 1000. The number of IPv4 routes allowed is zero (32K – (4K + 2 * 13500 + 1K) = 0 (recollect each IPv6 /64-bit route entry requires twice the space of IPv4 route entry). The maximum size of the route table quoted in the example is for illustration purposes only.
The following is the allocation scheme implemented for 7210 SAS-R6 and 7210 SAS-R12 IMM-c cards.
Software partitions the hardware table into two - Partition #1 with 4k (4*1204) 32-bit entries and Partition #2 with 12k (12*1024) entries.
Partition #1 can fit 128-bit IPv6 address and takes 4 * 32-bit entries each, 32-bit IPv4 entries taking one entry each (1*32-bit entry), and 64-bit IPv6 address taking 4 * 32-bit entries each; Lets call this L3-FIB-P1.
Partition #2 can fit 32-bit IPv4 entries taking one entry each, and 64-bit IPv6 address taking 2 * 32-bit entries each; Lets call this L3-FIB-P2.
Software reserves space for 256 128-bit IPv6 addresses in partition #1 (L3-FIB-P1); taking away 1024 32-bit entries and leaving around 3072 32-bit entries for use by either IPv4 prefixes or IPv6 prefixes. In other words, a maximum of 3072 IPv4 prefixes can fit in the remaining space if all of them were to be allocated to IPv4 or a maximum of 768 IPv6 (64-bit) prefixes can fit in the remaining space if all of them were to be allocated to IPv6.; Lets call the remaining space L3-FIB-P1-R.
Software reserves max-ip-subnets 32-bit entries from partition #2 for use by directly connected IPv4 and IPv6 interfaces with IPv4/IPv6 address assigned. ‛max-ip-subnets’ is a configurable CLI parameter and allows user to reserve the amount of space required for directly connected IP interfaces. IPv6 directly connected interfaces are allocated space from this reserved only if the IPv6 address prefix is less than equal to 64-bit. They are allocated two entries each per IPv6 64-bit address prefix. IPv6 directly connected interfaces with IPv6 address prefix greater than 64-bit is allocated entries from partition #1. All IPv4 directly connected IP interfaces are allocated one entry each from this reserved space. The remaining space is used to store prefixes learned by the node. Lets call the remaining space L3-FIB-P2-R.
L3-FIB-P2-R and L3-FIB-P1-R is used for allocating entries towards routes learned by the node statically or dynamically using a routing protocol. The software starts to allocate entries from L3-FIB-P2-R for both IPv4 addresses and IPv6 64-bit addresses, until all the resources are used up. It then allocates entries from L3-FIB-P1-R for both IPv4 and IPv6 addresses, until all of it is used up.
If the user has configured max-ipv6-routes, the software reserves space for it in L3-FIB-P2-R for use by IPv6 routes. The amount of space reserved is equivalent to 2 * max-ipv6-routes. The remaining space in L3-FIB-P2-R and L3-FIB-P1-R is available for IPv4 routes. For example, if max-ipv6-routes is set to 1000, then 2000 /32-bit entries are allocated from L3-FIB-P2-R and reserved for IPv6 routes. The rest along with available entries in L3-FIB-P1-R are available for use by IPv4.
The no form of this command specifies that the software does not allocate any resources for use by IPv6 routes.
no max-ipv6-routes
Specifies the maximum amount of entries to be used for IPv6 routes. Maximum values can be achieved assuming all the resources are allocated to IPv6 routes.
sap-scale-mode mode
no sap-scale-mode
config>system>resource-profile (on the 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE)
config>system>global-res-profile (on the 7210 SAS-R6 and 7210 SAS-R12)
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE (standalone), and 7210 SAS-Sx 10/100GE (standalone)
This command enables or disables a higher number of SAPs and services for Epipe and VPLS services. There is no change in scaling for IES, VPRN, and RVPLS SAPs and services.
The low keyword is configured by default. The default SAP ingress policy ID 1 is used in this mode. On the 7210 SAS-Mxp, if the high keyword is configured, the default SAP ingress policy ID 65536 is used to differentiate the policy from the default SAP ingress policy ID 1. On the 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE, SAP ingress policy ID 1 is the default when sap-scale-mode is set to either low or high.
To switch between the low and high modes, the user must remove all SAP configurations, change the mode, reboot the node, and reconfigure the SAPs and services.
The mandatory QoS configurations required to achieve higher SAP and service scaling are as follows.
Access port-based egress queuing and shaping must be configured on all ports, including service delivery ports and uplinks.
On the 7210 SAS-Mxp, either access port-based ingress classification or SAP ingress table-based classification and table-based policing (service meters) can be configured on uplinks for higher SAP scaling.
On the 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE, access port-based ingress classification and policing must be configured for higher SAP scaling.
On the 7210 SAS-Mxp, Epipe and VPLS SAPs must use SAP ingress table-based classification and table-based policing on service delivery ports for higher SAP scaling. The 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE do not support table-based policing (service meters) for SAP ingress policing.
On the 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12, IES and VPRN SAPs can use table-based classification.
R-VPLS SAPs must use CAM-based classification and policing.
See the 7210 SAS-Mxp, S, Sx, T Services Guide and 7210 SAS-R6, R12 Services Guide for more information about high SAP scale mode and low SAP scale mode.
The no form of this command disables the use of high SAP and service scaling for Epipe and VPLS services.
no sap-scale-mode
Specifies the SAP scale mode.
Keyword to enable higher SAP and service scaling.
Keyword to disable higher SAP and service scaling.